From owner-freebsd-pkg@FreeBSD.ORG Sun Feb 22 19:40:00 2015 Return-Path: Delivered-To: freebsd-pkg@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id CBF7BE9D for ; Sun, 22 Feb 2015 19:40:00 +0000 (UTC) Received: from mx5.roble.com (mx5.roble.com [206.40.34.5]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mx5.roble.com", Issuer "mx5.roble.com" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id BD39EB8C for ; Sun, 22 Feb 2015 19:40:00 +0000 (UTC) Date: Sun, 22 Feb 2015 11:32:04 -0800 (PST) From: Roger Marquis To: freebsd-pkg@freebsd.org Subject: Did "pkg add -f" change? User-Agent: Alpine 2.11 (BSF 23 2013-08-11) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; format=flowed; charset=US-ASCII X-BeenThere: freebsd-pkg@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Binary package management and package tools discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 22 Feb 2015 19:40:00 -0000 Don't have an earlier version to test but IIRC "pkg add -f" used to ignore dependencies. Now it fails if there are any uninstalled dependencies. Is there a workaround? Roger Marquis From owner-freebsd-pkg@FreeBSD.ORG Mon Feb 23 15:15:15 2015 Return-Path: Delivered-To: freebsd-pkg@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 4DE8A288 for ; Mon, 23 Feb 2015 15:15:15 +0000 (UTC) Received: from mail.kapsi.fi (mx1.kapsi.fi [IPv6:2001:1bc8:1004::1:25]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 06311C2 for ; Mon, 23 Feb 2015 15:15:14 +0000 (UTC) Received: from 91-158-78-126.elisa-laajakaista.fi ([91.158.78.126] helo=[192.168.255.112]) by mail.kapsi.fi with esmtpsa (TLS1.0:DHE_RSA_AES_128_CBC_SHA1:16) (Exim 4.72) (envelope-from ) id 1YPuj1-0000qB-6Q for freebsd-pkg@freebsd.org; Mon, 23 Feb 2015 17:15:11 +0200 Message-ID: <54EB43FB.1080902@kapsi.fi> Date: Mon, 23 Feb 2015 17:15:07 +0200 From: Arto Pekkanen User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:31.0) Gecko/20100101 Thunderbird/31.4.0 MIME-Version: 1.0 To: freebsd-pkg@freebsd.org Subject: Re: System lockup during Poudriere build References: <1205568033.41967.1424207587254.JavaMail.zimbra@norse-corp.com> In-Reply-To: <1205568033.41967.1424207587254.JavaMail.zimbra@norse-corp.com> Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="7T8s07Kb1m17OEb58XGNc1S0DVC5DbRVo" X-SA-Exim-Connect-IP: 91.158.78.126 X-SA-Exim-Mail-From: isoa@kapsi.fi X-SA-Exim-Scanned: No (on mail.kapsi.fi); SAEximRunCond expanded to false X-BeenThere: freebsd-pkg@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Binary package management and package tools discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 23 Feb 2015 15:15:15 -0000 This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --7T8s07Kb1m17OEb58XGNc1S0DVC5DbRVo Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: quoted-printable This is not related to pkg, but swap on ZFS is a really bad idea. I just = does not work reliably. On 17.2.2015 23:13, James Koenig wrote: > Dear FreeBSD-PKG email list, = =20 > = =20 > Have any of you had a successful poudriere build of the entire port= s =20 > tree using ZFS as a primary RAID manager, including swap? If so, what = =20 > kind of hardware or configurations did you use, in terms of RAM, number= of=20 > CPUS, etc? When we've tried to run a poudriere bulk build on our entir= e =20 > ports tree, we've experienced the build server totally locking up over = =20 > file locks. These lockups happen consistently during the build (poudrie= re =20 > bulk -a) process, whenever ZFS's swap is enabled, and no longer occur w= hen=20 > ZFS's swap is disabled. = =20 > = =20 > a crash filesystem's core.txt from the described lockup is attached as = =20 > zfs_lockup.core.txt.gz > =20 > Regards, = =20 > James Koenig > _______________________________________________ > freebsd-pkg@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-pkg > To unsubscribe, send any mail to "freebsd-pkg-unsubscribe@freebsd.org" >=20 --7T8s07Kb1m17OEb58XGNc1S0DVC5DbRVo Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (MingW32) iF4EAREIAAYFAlTrQ/4ACgkQTBivhqtJa27jFAEAqxGMxqu0A3xtxGn3b5jFIrg/ qKouJXqVovxXfb6yoOYA/inTEwMSg9uzbWMtK3a5yAa4M0s/4XO01fhyQCdC2VIx =1QD+ -----END PGP SIGNATURE----- --7T8s07Kb1m17OEb58XGNc1S0DVC5DbRVo-- From owner-freebsd-pkg@FreeBSD.ORG Mon Feb 23 16:49:28 2015 Return-Path: Delivered-To: freebsd-pkg@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id DCFB7FF6 for ; Mon, 23 Feb 2015 16:49:27 +0000 (UTC) Received: from mail-oi0-x22e.google.com (mail-oi0-x22e.google.com [IPv6:2607:f8b0:4003:c06::22e]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 9F82CD85 for ; Mon, 23 Feb 2015 16:49:27 +0000 (UTC) Received: by mail-oi0-f46.google.com with SMTP id x69so14491983oia.5 for ; Mon, 23 Feb 2015 08:49:27 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:from:date:message-id:subject:to:content-type; bh=/dAi2dKEvZtskaRco96+Gwpoq0taFlEjhT5K6oC+jKs=; b=xMZ4zK259mf7BdSHvgNTc5M6tdQUhCwMF64Pdl99SJjm1IsDZUUMkyr3jwVxDjFiOU 29GfZUrpt45zQvtsRYdlAjrUQMGQ54kinhUhpIL+Fw5vyW92nOylqQx4i9fuIeaO5m6o Yt1Xj0BNxHubdELyw2Jxef87GUxsx2FCpZNZ3Dze8aFdfOK03gSQIKxhqQjNbrzS7fwt iR65XqSFcrNpX0VJ+D31jmDEPMkuidoHTWoPtO7woS3Cy0d34lPsyovTbtwy2HGit2Wb gDcSS2E83SdvSRxVZ9Dl8hxSVp6wKocUO/SDyRfakf/5xkMNc5/4iTpUzXWgUaEELeXu embA== X-Received: by 10.60.45.200 with SMTP id p8mr8009245oem.46.1424710166946; Mon, 23 Feb 2015 08:49:26 -0800 (PST) MIME-Version: 1.0 Sender: ivoras@gmail.com Received: by 10.202.227.194 with HTTP; Mon, 23 Feb 2015 08:48:46 -0800 (PST) From: Ivan Voras Date: Mon, 23 Feb 2015 17:48:46 +0100 X-Google-Sender-Auth: SPduS0X8myHR2ytGJQfpzMLUMLQ Message-ID: Subject: Upgrading php with pkg To: freebsd-pkg@freebsd.org Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.18-1 X-BeenThere: freebsd-pkg@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Binary package management and package tools discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 23 Feb 2015 16:49:28 -0000 Hi, It's time for my yearly rant about pkg seemingly not being able to upgrade whole sets of dependencies while installing or upgrading packages. In short, if we have this: package A depends on package B, which depends on package C ...upgrading package B *must always* result in an upgrade to package A, and *must* cause an upgrade of package C *iff* the new version of package B is linked with a different version of package C (e.g. if it depends on a newer version of package C). Using heuristics such as checking versions encoded in .so filenames are rarely enough because (upstream) developers are lazy. I can give examples from the PHP-Apache-PostgreSQL stack at request. If this is not done, we have the situation described here: http://ivoras.net/blog/tree/2015/Feb-why-freebsds-pkg-sucks.html The post is somewhat strongly worded, and I believe it will be even more strongly worded a year from now ;) From owner-freebsd-pkg@FreeBSD.ORG Mon Feb 23 17:46:28 2015 Return-Path: Delivered-To: freebsd-pkg@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 55017D9E; Mon, 23 Feb 2015 17:46:28 +0000 (UTC) Received: from mail-wg0-x233.google.com (mail-wg0-x233.google.com [IPv6:2a00:1450:400c:c00::233]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id D5A64608; Mon, 23 Feb 2015 17:46:27 +0000 (UTC) Received: by wggz12 with SMTP id z12so266142wgg.2; Mon, 23 Feb 2015 09:46:26 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=sender:date:from:to:cc:subject:message-id:references:mime-version :content-type:content-disposition:in-reply-to:user-agent; bh=u9umvsVKdwb/iYJAU9eWA01rKV2Wum0rZxfZZIxc4c0=; b=QASQsSVEG+2lh/tSo9rSzsF2KqjIPxQVkdOmmms6/OJ+S33M7HbbaDwM/ak/v0wi0t 1OQjgJ0PNV9XpXFpGL1w1auIspzW986z+4MyLBaTIxY2ngAjmc0p/BcYAYyL9OxXVyNN jy+WX24D1f1lll1PqY6uAKfrjCBJGAt6TvZXJ3ERIsxP9RX28miOisyhgYwEmQla/zdO 1Rcz+e0+foaKrW4IlOsqiLSS7OA/yncUmF/ES2Qedpqa4lSVLEQNh+qMzBXNPLn5GL8m AId8Bnc25gfA3gR4JdY1RrA7zbbuEJcmLlz48ilJBprEsv7iPjo/u0Y8unOIaDUKP4qG KSeQ== X-Received: by 10.194.201.103 with SMTP id jz7mr25330396wjc.14.1424713586157; Mon, 23 Feb 2015 09:46:26 -0800 (PST) Received: from ivaldir.etoilebsd.net ([2001:41d0:8:db4c::1]) by mx.google.com with ESMTPSA id dj4sm56545301wjc.13.2015.02.23.09.46.24 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 23 Feb 2015 09:46:25 -0800 (PST) Sender: Baptiste Daroussin Date: Mon, 23 Feb 2015 18:46:22 +0100 From: Baptiste Daroussin To: Ivan Voras Subject: Re: Upgrading php with pkg Message-ID: <20150223174622.GD34473@ivaldir.etoilebsd.net> References: MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="mJm6k4Vb/yFcL9ZU" Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.23 (2014-03-12) Cc: freebsd-pkg@freebsd.org X-BeenThere: freebsd-pkg@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Binary package management and package tools discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 23 Feb 2015 17:46:28 -0000 --mJm6k4Vb/yFcL9ZU Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Mon, Feb 23, 2015 at 05:48:46PM +0100, Ivan Voras wrote: > Hi, >=20 > It's time for my yearly rant about pkg seemingly not being able to upgrade > whole sets of dependencies while installing or upgrading packages. >=20 > In short, if we have this: >=20 > package A depends on package B, which depends on package C >=20 > ...upgrading package B *must always* result in an upgrade to package A, a= nd > *must* cause an upgrade of package C *iff* the new version of package B is > linked with a different version of package C (e.g. if it depends on a new= er > version of package C). >=20 > Using heuristics such as checking versions encoded in .so filenames are > rarely enough because (upstream) developers are lazy. I can give examples > from the PHP-Apache-PostgreSQL stack at request. >=20 > If this is not done, we have the situation described here: > http://ivoras.net/blog/tree/2015/Feb-why-freebsds-pkg-sucks.html >=20 > The post is somewhat strongly worded, and I believe it will be even more > strongly worded a year from now ;) The only problem here is the lack of developers and of time, btw this is not interdependency this is cherry-picking, interdependency works well when upgrading all at one. Beside what some people would like the ports tree and packages is a whole thing. Either you upgrade everything or you do not... This is what non frozen packages gives you, you may like it or not this is = how it is, and it is mostly impossible to prevent that without an important wor= k on both the port side and the pkg side. BTW: using strong words might sound fun, but the only reaction achieved with that is demotivation... We are doing what we can with very few resources, i= f one want to see this fixed and/or properly handled this is clearly not with str= ong words... Bapt --mJm6k4Vb/yFcL9ZU Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iEYEARECAAYFAlTrZ24ACgkQ8kTtMUmk6EyYxQCeLitStxwOPbFShdB9Zx9l4OkK +7sAoMLX3kt/fMjXXi6HQ0sNlOWHpKzX =rjG0 -----END PGP SIGNATURE----- --mJm6k4Vb/yFcL9ZU-- From owner-freebsd-pkg@FreeBSD.ORG Mon Feb 23 17:47:26 2015 Return-Path: Delivered-To: freebsd-pkg@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 8751DDF0 for ; Mon, 23 Feb 2015 17:47:26 +0000 (UTC) Received: from out4-smtp.messagingengine.com (out4-smtp.messagingengine.com [66.111.4.28]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 57DDF622 for ; Mon, 23 Feb 2015 17:47:25 +0000 (UTC) Received: from compute4.internal (compute4.nyi.internal [10.202.2.44]) by mailout.nyi.internal (Postfix) with ESMTP id D627D20A76 for ; Mon, 23 Feb 2015 12:47:23 -0500 (EST) Received: from web3 ([10.202.2.213]) by compute4.internal (MEProxy); Mon, 23 Feb 2015 12:47:24 -0500 DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d= messagingengine.com; h=message-id:x-sasl-enc:from:to :mime-version:content-transfer-encoding:content-type:subject :date:in-reply-to:references; s=smtpout; bh=XaLbibJZqFhCWA3XbrYO rCJ9YCg=; b=h10Jnx2zjzr8UWUV+hhcvt1f0HdusylbRtpiJ6724sEAte/XykKd nML0ixkNEj/Z1p+l8LcXzC/9tNyPu7DndVKVXq2XpY3jho9JT4OUik70tDN4woNF Z1SMPaExPr6qV/w7w7KuBhSPXX74ZTSBr8BgI8Urm+BB30N5IXMx+F4= Received: by web3.nyi.internal (Postfix, from userid 99) id 6EEBE10E5B5; Mon, 23 Feb 2015 12:47:24 -0500 (EST) Message-Id: <1424713644.2437211.231310185.721AACDF@webmail.messagingengine.com> X-Sasl-Enc: gKSeLqKkrQRufGIwbC41qivZss7ebj/l/7Ss5oYLls1A 1424713644 From: Mark Felder To: freebsd-pkg@freebsd.org MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain X-Mailer: MessagingEngine.com Webmail Interface - ajax-4ba7306c Subject: Re: Upgrading php with pkg Date: Mon, 23 Feb 2015 11:47:24 -0600 In-Reply-To: References: X-BeenThere: freebsd-pkg@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Binary package management and package tools discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 23 Feb 2015 17:47:26 -0000 On Mon, Feb 23, 2015, at 10:48, Ivan Voras wrote: > Hi, > > It's time for my yearly rant about pkg seemingly not being able to > upgrade > whole sets of dependencies while installing or upgrading packages. > > In short, if we have this: > > package A depends on package B, which depends on package C > > ...upgrading package B *must always* result in an upgrade to package A, > and > *must* cause an upgrade of package C *iff* the new version of package B > is > linked with a different version of package C (e.g. if it depends on a > newer > version of package C). > > Using heuristics such as checking versions encoded in .so filenames are > rarely enough because (upstream) developers are lazy. I can give examples > from the PHP-Apache-PostgreSQL stack at request. > > If this is not done, we have the situation described here: > http://ivoras.net/blog/tree/2015/Feb-why-freebsds-pkg-sucks.html > > The post is somewhat strongly worded, and I believe it will be even more > strongly worded a year from now ;) > While I do agree that # pkg install php53-fileinfo should list more packages that need to be upgraded, you're walking on thin ice by installing new packages related to existing ones without upgrading all of your packages first. The following is absolutely unsupported last I checked: # pkg upgrade php53 Upgrade all of your packages or none. The stability of the packages are very much reliant on all packages being from the exact same package set / SVN revision. Mixing packages when packages/ports is a rolling release has always been a dangerous game to play. If you require a stable set of package like that you should be using the quarterly package sets. In that situation you wouldn't have received php53-fileinfo-5.3.29; it would have been the exact same as the existing packages from that quarterly set. From owner-freebsd-pkg@FreeBSD.ORG Mon Feb 23 20:43:17 2015 Return-Path: Delivered-To: freebsd-pkg@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 166E8D7F for ; Mon, 23 Feb 2015 20:43:17 +0000 (UTC) Received: from internal.electricembers.net (internal.electricembers.net [208.90.215.71]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "*.electricembers.net", Issuer "DigiCert High Assurance CA-3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 01BF8C4F for ; Mon, 23 Feb 2015 20:43:16 +0000 (UTC) Received: from mail.electricembers.net (npomail1 [208.90.215.73]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: ben) by internal.electricembers.net (Postfix) with ESMTPSA id B54B827397 for ; Mon, 23 Feb 2015 12:36:01 -0800 (PST) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII; format=flowed Content-Transfer-Encoding: 7bit Date: Mon, 23 Feb 2015 12:36:01 -0800 From: Benjamin Connelly To: freebsd-pkg@freebsd.org Subject: segfault when package locked Message-ID: <45c872096d431d2df3f66d3546383517@mail.electricembers.net> X-Sender: ben@electricembers.coop User-Agent: Roundcube Webmail/1.0.2 X-BeenThere: freebsd-pkg@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Binary package management and package tools discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 23 Feb 2015 20:43:17 -0000 If we lock any packages, and then try to run 'pkg upgrade -f' it segfaults. We can work around by deleting the package first instead of locking it, but it seems like a bug? Ben From owner-freebsd-pkg@FreeBSD.ORG Mon Feb 23 21:19:16 2015 Return-Path: Delivered-To: freebsd-pkg@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 25D459F1 for ; Mon, 23 Feb 2015 21:19:16 +0000 (UTC) Received: from mail-wi0-x22a.google.com (mail-wi0-x22a.google.com [IPv6:2a00:1450:400c:c05::22a]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id C3FA5FAA for ; Mon, 23 Feb 2015 21:19:15 +0000 (UTC) Received: by mail-wi0-f170.google.com with SMTP id ex7so439775wid.1 for ; Mon, 23 Feb 2015 13:19:14 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=sender:date:from:to:cc:subject:message-id:references:mime-version :content-type:content-disposition:in-reply-to:user-agent; bh=ya4MGz1KS7ClpaxnKYFZ9vYnEYX2Qtqe5PtPoYH6XAs=; b=xIrSZsp7Gn+wUfO0xX++sTvOViqJ2oMkFxt1N9MiCidEhi4nxQh9Fhoj7ugOlNaybA GmEHLB5MU9X2FKQna5rLc6HJw+YmCmT9KghADWzMfhT0dK7pcrCD2XD0QlVxcYY4n2EX ulaMNF6MJWYqGMe/DxS1CSUjK7Wnx9XLqYLRe1mkwIsG7c1/kMOCxcJWWjmunAAfAtTY sGesbSPiynXq6kH4UIBHAglipvDe8T1zorrDOuIBZwuT/5KyogepqGzq3lkgc0TqXI5Q CGPW4nvfdjPNm/wumz2mfL3jRxlCYaMGXF296YLe/E6csf7d0JxIe1KTTm08+K6F756r iaQg== X-Received: by 10.180.79.232 with SMTP id m8mr24774388wix.81.1424726354051; Mon, 23 Feb 2015 13:19:14 -0800 (PST) Received: from ivaldir.etoilebsd.net ([2001:41d0:8:db4c::1]) by mx.google.com with ESMTPSA id m4sm57255144wjb.25.2015.02.23.13.19.12 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 23 Feb 2015 13:19:12 -0800 (PST) Sender: Baptiste Daroussin Date: Mon, 23 Feb 2015 22:19:10 +0100 From: Baptiste Daroussin To: Benjamin Connelly Subject: Re: segfault when package locked Message-ID: <20150223211909.GE34473@ivaldir.etoilebsd.net> References: <45c872096d431d2df3f66d3546383517@mail.electricembers.net> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="10jrOL3x2xqLmOsH" Content-Disposition: inline In-Reply-To: <45c872096d431d2df3f66d3546383517@mail.electricembers.net> User-Agent: Mutt/1.5.23 (2014-03-12) Cc: freebsd-pkg@freebsd.org X-BeenThere: freebsd-pkg@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Binary package management and package tools discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 23 Feb 2015 21:19:16 -0000 --10jrOL3x2xqLmOsH Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Mon, Feb 23, 2015 at 12:36:01PM -0800, Benjamin Connelly wrote: > If we lock any packages, and then try to run 'pkg upgrade -f' it=20 > segfaults. We can work around by deleting the package first instead of=20 > locking it, but it seems like a bug? You sounds like a bug, can you give more details? The output might be good (do you hit an assert?) Best regards, Bapt --10jrOL3x2xqLmOsH Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iEYEARECAAYFAlTrmU0ACgkQ8kTtMUmk6EyGGQCfYdgWNzAanXvs2kUkNvpUWyC6 jZgAni85h92y4HzU1j3mS+vaYuD+Zekv =ITvp -----END PGP SIGNATURE----- --10jrOL3x2xqLmOsH-- From owner-freebsd-pkg@FreeBSD.ORG Fri Feb 27 19:20:41 2015 Return-Path: Delivered-To: freebsd-pkg@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 11B77AA3 for ; Fri, 27 Feb 2015 19:20:41 +0000 (UTC) Received: from internal.electricembers.net (internal.electricembers.net [208.90.215.71]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "*.electricembers.net", Issuer "DigiCert High Assurance CA-3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id EE435C73 for ; Fri, 27 Feb 2015 19:20:40 +0000 (UTC) Received: from mail.electricembers.net (npomail1 [208.90.215.73]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: ben) by internal.electricembers.net (Postfix) with ESMTPSA id 94A9C27333 for ; Fri, 27 Feb 2015 11:20:39 -0800 (PST) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII; format=flowed Content-Transfer-Encoding: 7bit Date: Fri, 27 Feb 2015 11:20:39 -0800 From: Benjamin Connelly To: freebsd-pkg@freebsd.org Subject: Re: segfault when package locked In-Reply-To: <20150223211909.GE34473@ivaldir.etoilebsd.net> References: <45c872096d431d2df3f66d3546383517@mail.electricembers.net> <20150223211909.GE34473@ivaldir.etoilebsd.net> Message-ID: <7b07bfb13ba43cfeb2142d30ab748315@mail.electricembers.net> X-Sender: ben@electricembers.coop User-Agent: Roundcube Webmail/1.0.2 X-BeenThere: freebsd-pkg@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Binary package management and package tools discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 27 Feb 2015 19:20:41 -0000 >> If we lock any packages, and then try to run 'pkg upgrade -f' it >> segfaults. We can work around by deleting the package first instead of >> locking it, but it seems like a bug? > > You sounds like a bug, can you give more details? > > The output might be good (do you hit an assert?) > > Best regards, > Bapt Sorry, I'm having trouble recreating the problem. (Maybe it's already been fixed!) If we ever do run into it again, we'll collect all output ;) Ben From owner-freebsd-pkg@FreeBSD.ORG Sat Feb 28 11:32:09 2015 Return-Path: Delivered-To: pkg@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 84939D85 for ; Sat, 28 Feb 2015 11:32:09 +0000 (UTC) Received: from nm39-vm5.bullet.mail.bf1.yahoo.com (nm39-vm5.bullet.mail.bf1.yahoo.com [72.30.239.149]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 352219BD for ; Sat, 28 Feb 2015 11:32:09 +0000 (UTC) Received: from [66.196.81.173] by nm39.bullet.mail.bf1.yahoo.com with NNFMP; 28 Feb 2015 11:29:52 -0000 Received: from [98.139.212.209] by tm19.bullet.mail.bf1.yahoo.com with NNFMP; 28 Feb 2015 11:29:52 -0000 Received: from [127.0.0.1] by omp1018.mail.bf1.yahoo.com with NNFMP; 28 Feb 2015 11:29:40 -0000 X-Yahoo-Newman-Property: ymail-3 X-Yahoo-Newman-Id: 733423.99862.bm@omp1018.mail.bf1.yahoo.com Received: (qmail 24915 invoked by uid 60001); 28 Feb 2015 11:29:40 -0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s1024; t=1425122980; bh=2Ad+u2BiKFyOG9H9vkGs2ly6HI2zf99lfUQ2KCIoruY=; h=Message-ID:Date:From:Subject:To:Cc:MIME-Version:Content-Type; b=XSQkB/JFrbCIW2eyOMXCSJ5nt2kUQlXO3mqSbeIWFf17EZVmOBQZzSutV2t57tp4p6IElNKuwfSmeaHXZmOh3wYor6fJ4jyBKj0BuTzVdU5n3PM4e0s9YgnpuIGrGGC3EAzGD/D2Tf2EVGuYCXYGjOsb89UHulrrMuEFMpgMbZY= X-YMail-OSG: 0JoGsoEVM1lkGOP2QVPfZ0bT6Q2t.hDT4T57.iNaikc08ue a5a0HGhlM4hxyYUEA.Kii5xZEYIriXJYiUHy.AlxKCklpDx4Oqys2EVkZVVE .WyYLKg1ZhPqSEIb7ifUYyCaG_HC.4bYS1hIGB8eF4Sjg8X5ia1sC5mpU3xw TSM.1b1uqoDFiFwfE40pbek7UdxkPOu6UKO5ENGOJ19MGUQ913J8HIsRgd6Z q1LJLOCghBD5j6qqB.LmEpYNqZi5h4QLXL0yGJ5Dutc_h6v1uPjUIu6mnohf eaVDGpDiwEfKUJyWKeocXXA9_4mD5zhX9xUWCnCBJtqlM_CBJ2ucqO6dwkid QzFEpnQSZLuiqbXKiQywdb41zP7mkZs0tWRVoDoUbxnL87EdUiB7tBL4yqTB AQtyGPxWAX4.db0ccoMHbWyeHXqu1X.h278RhRcLExdc9HHXJkC6VhcQWbQX Hy4wgIc61Lyr8_cMkdP93stMEVv7Hv7WL0I7GSYtZ5sPDjfXx8AAY8gWIJ5h 7gy0QJiM7lCFCtjY6C9E.058viWQ7gIMHZzwjUDV5XVAZ2spts3mz5WYV3Ix LrI0d9DDBun8- Received: from [66.92.43.99] by web140906.mail.bf1.yahoo.com via HTTP; Sat, 28 Feb 2015 03:29:40 PST X-Rocket-MIMEInfo: 002.001, Tm8gcGtnIGZhaWx1cmVzICwgYnV0IHF1aXJrczoNCi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uDQoxLg0KDQpCYWNraW5nIHVwIHBrZ25nIGRhdGFiYXNlOg0KcGtnOiBJZ25vcmluZyBiYWQgY29uZmlndXJhdGlvbiBlbnRyeSBpbiAvZXRjL3BrZy9wa2cuY29uZjogIi91c3IvY2FjaGUvcGtnIg0KcGtnOiBJZ25vcmluZyBiYWQgY29uZmlndXJhdGlvbiBlbnRyeSBpbiAvZXRjL3BrZy9wa2cuY29uZjogIklOREVYLTEwIg0KcGtnOiBJZ25vcmluZyBiYWQgY29uZmlndXJhdGlvbiBlbnRyeSBpbiAvZXQBMAEBAQE- X-Mailer: YahooMailClassic/383 YahooMailWebService/0.8.203.740 Message-ID: <1425122980.77683.YahooMailBasic@web140906.mail.bf1.yahoo.com> Date: Sat, 28 Feb 2015 03:29:40 -0800 From: Jeffrey Bouquet Subject: pkg wondering... To: pkg@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: ports@freebsd.org X-BeenThere: freebsd-pkg@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Binary package management and package tools discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 28 Feb 2015 11:32:09 -0000 No pkg failures , but quirks: ............................. 1. Backing up pkgng database: pkg: Ignoring bad configuration entry in /etc/pkg/pkg.conf: "/usr/cache/pkg" pkg: Ignoring bad configuration entry in /etc/pkg/pkg.conf: "INDEX-10" pkg: Ignoring bad configuration entry in /etc/pkg/pkg.conf: "freebsd:10:x86:32" Can pkg be smarter and suggest a proper configuration upon error, test a new one locally before suggesting it, or have one firmly tested as working... hesitant to remove the improper entries because then oftentimes, IIRC, what remains causes, or has caused, pkg-* failures with not solution suggested... BTW that series of messages obscures day to day portupgrade updates locally... ten or so lines to each one of the upgrade by portupgrade ... leaving the latter not in context. Something like a sysinstall for pkg (all its files) parsing each one for errors... would be useful for new installs as well as existing ones maybe? .............................. 2. Another feature maybe missng in pkg-install and pkg-upgrade is the "skip this upgrade? new dependencies" ; for instance audio/mous is qt4 so I do upgrades with ... | grep -v mous | ... an xargs pipe... However the particular port has to be tested locally of all the list passing through the pipe to xargs. Slows it down some. 3. 4. Less relevant, do not remember them right now... ............................... A. Don't know if this should fit in this email, but every boot "libexpect.so.1" not found required by dbus-daemon ... and another (uuid* ) ... persists even after reinstall of everything known relevant. Ignorable here, but... ..............................