From owner-freebsd-pkg@FreeBSD.ORG Sun Jul 20 14:08:55 2014 Return-Path: Delivered-To: pkg@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 7C525CFD for ; Sun, 20 Jul 2014 14:08:55 +0000 (UTC) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 64ABD2661 for ; Sun, 20 Jul 2014 14:08:55 +0000 (UTC) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.14.8/8.14.8) with ESMTP id s6KE8tVV018232 for ; Sun, 20 Jul 2014 14:08:55 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: pkg@FreeBSD.org Subject: [Bug 191982] ports-mgmt/pkg: -1.2.7_2 does not build: no -lbsdxml Date: Sun, 20 Jul 2014 14:08:55 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Ports Tree X-Bugzilla-Component: Individual Port(s) X-Bugzilla-Version: Latest X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: marino@FreeBSD.org X-Bugzilla-Status: Open X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: pkg@FreeBSD.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_status cc assigned_to Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-pkg@freebsd.org X-Mailman-Version: 2.1.18 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, 20 Jul 2014 14:08:55 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=191982 John Marino changed: What |Removed |Added ---------------------------------------------------------------------------- Status|Needs Triage |Open CC| |marino@FreeBSD.org Assignee|freebsd-ports-bugs@FreeBSD. |pkg@FreeBSD.org |org | --- Comment #1 from John Marino --- over to maintainer -- You are receiving this mail because: You are the assignee for the bug. From owner-freebsd-pkg@FreeBSD.ORG Wed Jul 23 15:13:20 2014 Return-Path: Delivered-To: pkg@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id DE26445B for ; Wed, 23 Jul 2014 15:13:19 +0000 (UTC) Received: from mail-we0-x234.google.com (mail-we0-x234.google.com [IPv6:2a00:1450:400c:c03::234]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 76225284E for ; Wed, 23 Jul 2014 15:13:19 +0000 (UTC) Received: by mail-we0-f180.google.com with SMTP id w61so1333795wes.11 for ; Wed, 23 Jul 2014 08:13:16 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=sender:date:from:to:subject:message-id:mime-version:content-type :content-disposition:user-agent; bh=AL5BNf9EWSa4okfKcoZCK/nXS91jLoa8Ia5i5/N+r2U=; b=IFINH3SC4mUfqodQUmgytawgf20rudZDn4yqtF6M6xcQrinqGNhlovt8s7lzDlPrXD /h9hjg5y3r5sXtmYmA5CNdMapVZOoaiGHQKkNw1f4rDyvuZswzkV78UsXfIaKinkjmMy TVmvYMoBXaotbM1QsJohynkysxT5qZDFouI9gD54e5c4MAsacUxkBVC4am+tIFgTdj1Q xm+AAOF15VzO6str6fuW9scvxlO9s1Yt2jpcTtaKOkxYbtRNNBkKGjqunjwHS38UpCsR Yd8IaPgzmKy0ZzweOUFiyJubl4lhtmCHxLX5CA3CahPSsItKiBkAZeIgNBhVuimIOYY+ yPzg== X-Received: by 10.194.62.140 with SMTP id y12mr2767871wjr.27.1406128396568; Wed, 23 Jul 2014 08:13:16 -0700 (PDT) Received: from ivaldir.etoilebsd.net ([2001:41d0:8:db4c::1]) by mx.google.com with ESMTPSA id de5sm10240747wib.18.2014.07.23.08.13.15 for (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 23 Jul 2014 08:13:15 -0700 (PDT) Sender: Baptiste Daroussin Date: Wed, 23 Jul 2014 17:13:13 +0200 From: Baptiste Daroussin To: pkg@FreeBSD.org Subject: [ANNOUNCEMENT] pkg 1.3.0 out! Message-ID: <20140723151313.GA55770@ivaldir.etoilebsd.net> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="M9NhX3UHpAaciwkO" Content-Disposition: inline User-Agent: Mutt/1.5.23 (2014-03-12) X-BeenThere: freebsd-pkg@freebsd.org X-Mailman-Version: 2.1.18 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: Wed, 23 Jul 2014 15:13:20 -0000 --M9NhX3UHpAaciwkO Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Hi all, I'm very please to announce the release of pkg 1.3.0 This version is the result of almost 9 month of hard work Here are the statistics for the version: - 373 files changed, 66973 insertions(+), 38512 deletions(-) - 29 different contributors Please not that for the first time I'm not the main contributor, and I would like to particularly thanks Vsevold Stakhov for all the hard work he has do= ne to allow us to get this release out. I would like also to give a special thank= s to Andrej Zverev for the tons of hours spending on testing and cleaning the bug tracker! So much has happened that it is hard to summarize so I'll try to highlight = the major points: - New solver, now pkg has a real SAT solver able to automatically handle conflicts and dynamically discover them. (yes pkg set -o is deprecated no= w) - pkg install now able to install local files as well and resolve their dependencies from the remote repositories - Lots of parts of the code has been sandboxed - Lots of rework to improve portability - Package installation process has been reworked to be safer and handle pro= perly the schg flags - Important modification of the locking system for finer grain locks - Massive usage of libucl - Simplification of the API - Lots of improvements on the UI to provide a better user experience. - Lots of improvements in multi repository mode - pkg audit code has been moved into the library - pkg -o A=3DB that will overwrite configuration file from cli - The ui now support long options - The unicity of a package is not anymore origin - Tons of bug fixes - Tons of behaviours fixes - Way more! Thank you to all contributors: Alberto Villa, Alexandre Perrin, Andrej Zverev, Antoine Brodin, Brad Davis, Bryan Drewery, Dag-Erling Sm=F8rgrav, Dmitry Marakasov, Elvira Khabirova, J= amie Landeg Jones, Jilles Tjoelker, John Marino, Julien Laffaye, Mathieu Arnold, Matthew Seaman, Maximilian Ga=DF, Michael Gehring, Michael Gmelin, Nicolas = Szalay, Rodrigo Osorio, Roman Naumann, Rui Paulo, Sean Channel, Stanislav E. Putrya, Vsevolod Stakhov, Xin Li, coctic Regards, Bapt on behalf of the pkg@ --M9NhX3UHpAaciwkO Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iEYEARECAAYFAlPP0QkACgkQ8kTtMUmk6EwtfACaAj+0moz/300yRmXu8Lbgcli2 GuIAnRqtzrBw+CQOTpXGcQ8B+rr8DUjc =0CrD -----END PGP SIGNATURE----- --M9NhX3UHpAaciwkO-- From owner-freebsd-pkg@FreeBSD.ORG Thu Jul 24 16:03:43 2014 Return-Path: Delivered-To: freebsd-pkg@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id E147F85B for ; Thu, 24 Jul 2014 16:03:43 +0000 (UTC) Received: from relay2.tomsk.ru (mail.sibptus.tomsk.ru [212.73.124.5]) by mx1.freebsd.org (Postfix) with ESMTP id 52A832F93 for ; Thu, 24 Jul 2014 16:03:42 +0000 (UTC) X-Virus-Scanned: by clamd daemon 0.98.1 for FreeBSD at relay2.tomsk.ru Received: from admin.sibptus.tomsk.ru (account sudakov@sibptus.tomsk.ru [212.73.125.240] verified) by relay2.tomsk.ru (CommuniGate Pro SMTP 5.1.16) with ESMTPSA id 36110650 for freebsd-pkg@freebsd.org; Thu, 24 Jul 2014 23:03:40 +0700 Received: from admin.sibptus.tomsk.ru (sudakov@localhost [127.0.0.1]) by admin.sibptus.tomsk.ru (8.14.7/8.14.7) with ESMTP id s6OG3eJu023058 for ; Thu, 24 Jul 2014 23:03:40 +0700 (NOVT) (envelope-from vas@mpeks.tomsk.su) Received: (from sudakov@localhost) by admin.sibptus.tomsk.ru (8.14.7/8.14.7/Submit) id s6OG3eWh023057 for freebsd-pkg@freebsd.org; Thu, 24 Jul 2014 23:03:40 +0700 (NOVT) (envelope-from vas@mpeks.tomsk.su) X-Authentication-Warning: admin.sibptus.tomsk.ru: sudakov set sender to vas@mpeks.tomsk.su using -f Date: Thu, 24 Jul 2014 23:03:40 +0700 From: Victor Sudakov To: freebsd-pkg@freebsd.org Subject: poudriere web page: recover after after a crash? Message-ID: <20140724160339.GA22950@admin.sibptus.tomsk.ru> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Organization: AO "Svyaztransneft", SibPTUS X-PGP-Key: http://www.dreamwidth.org/pubkey?user=victor_sudakov X-PGP-Fingerprint: 10E3 1171 1273 E007 C2E9 3532 0DA4 F259 9B5E C634 User-Agent: Mutt/1.5.21 (2010-09-15) X-BeenThere: freebsd-pkg@freebsd.org X-Mailman-Version: 2.1.18 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: Thu, 24 Jul 2014 16:03:44 -0000 Colleagues, There was an HDD problem (virtual SCSI drive was lost) during a poudriere build session. I had to poweroff the host. After fixing the problem, I ran "poudriere bulk -c" to rebuild everything. The build seems to be a success, however poudriere's nice Web page seems corrupt: it just says "Invalid request or no data available yet". Maybe some JSON files have become corrupt? Is there a way to recover from this, or should I just remove ${BASEFS} and start from scratch? -- Victor Sudakov, VAS4-RIPE, VAS47-RIPN sip:sudakov@sibptus.tomsk.ru From owner-freebsd-pkg@FreeBSD.ORG Fri Jul 25 04:41:00 2014 Return-Path: Delivered-To: freebsd-pkg@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id AF29E95C for ; Fri, 25 Jul 2014 04:41:00 +0000 (UTC) Received: from relay2.tomsk.ru (mail.sibptus.tomsk.ru [212.73.124.5]) by mx1.freebsd.org (Postfix) with ESMTP id 1F6FF2FBA for ; Fri, 25 Jul 2014 04:40:59 +0000 (UTC) X-Virus-Scanned: by clamd daemon 0.98.1 for FreeBSD at relay2.tomsk.ru Received: from admin.sibptus.tomsk.ru (account sudakov@sibptus.tomsk.ru [212.73.125.240] verified) by relay2.tomsk.ru (CommuniGate Pro SMTP 5.1.16) with ESMTPSA id 36115642 for freebsd-pkg@freebsd.org; Fri, 25 Jul 2014 11:40:57 +0700 Received: from admin.sibptus.tomsk.ru (sudakov@localhost [127.0.0.1]) by admin.sibptus.tomsk.ru (8.14.7/8.14.7) with ESMTP id s6P4euI4044349 for ; Fri, 25 Jul 2014 11:40:56 +0700 (NOVT) (envelope-from vas@mpeks.tomsk.su) Received: (from sudakov@localhost) by admin.sibptus.tomsk.ru (8.14.7/8.14.7/Submit) id s6P4euoD044348 for freebsd-pkg@freebsd.org; Fri, 25 Jul 2014 11:40:56 +0700 (NOVT) (envelope-from vas@mpeks.tomsk.su) X-Authentication-Warning: admin.sibptus.tomsk.ru: sudakov set sender to vas@mpeks.tomsk.su using -f Date: Fri, 25 Jul 2014 11:40:56 +0700 From: Victor Sudakov To: freebsd-pkg@freebsd.org Subject: Re: poudriere web page: recover after after a crash? Message-ID: <20140725044056.GA44244@admin.sibptus.tomsk.ru> References: <20140724160339.GA22950@admin.sibptus.tomsk.ru> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20140724160339.GA22950@admin.sibptus.tomsk.ru> Organization: AO "Svyaztransneft", SibPTUS X-PGP-Key: http://www.dreamwidth.org/pubkey?user=victor_sudakov X-PGP-Fingerprint: 10E3 1171 1273 E007 C2E9 3532 0DA4 F259 9B5E C634 User-Agent: Mutt/1.5.21 (2010-09-15) X-BeenThere: freebsd-pkg@freebsd.org X-Mailman-Version: 2.1.18 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, 25 Jul 2014 04:41:00 -0000 Forget it, I just scrapped ${BASEFS} for who knows what else could be corrupt there. Victor Sudakov wrote: > Colleagues, > > There was an HDD problem (virtual SCSI drive was lost) during > a poudriere build session. I had to poweroff the host. > > After fixing the problem, I ran "poudriere bulk -c" to rebuild > everything. The build seems to be a success, however poudriere's nice > Web page seems corrupt: it just says "Invalid request or no data > available yet". Maybe some JSON files have become corrupt? > > Is there a way to recover from this, or should I just remove ${BASEFS} > and start from scratch? > > -- > Victor Sudakov, VAS4-RIPE, VAS47-RIPN > sip:sudakov@sibptus.tomsk.ru > _______________________________________________ > 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" -- Victor Sudakov, VAS4-RIPE, VAS47-RIPN sip:sudakov@sibptus.tomsk.ru From owner-freebsd-pkg@FreeBSD.ORG Fri Jul 25 18:53:40 2014 Return-Path: Delivered-To: freebsd-pkg@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id E47F1523 for ; Fri, 25 Jul 2014 18:53:39 +0000 (UTC) Received: from gromit.dlib.vt.edu (gromit.dlib.vt.edu [128.173.49.29]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "gromit.dlib.vt.edu", Issuer "Chumby Certificate Authority" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id B98AF2176 for ; Fri, 25 Jul 2014 18:53:39 +0000 (UTC) Received: from pmather.tower.lib.vt.edu (pmather.tower.lib.vt.edu [128.173.51.28]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by gromit.dlib.vt.edu (Postfix) with ESMTPSA id E5F3C612 for ; Fri, 25 Jul 2014 14:53:37 -0400 (EDT) From: Paul Mather Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Subject: pkg-1.3.0 fails to detect updated package (and other problems) Message-Id: <61A4A5AC-947F-47F3-97C5-8EA38A65D871@gromit.dlib.vt.edu> Date: Fri, 25 Jul 2014 14:53:37 -0400 To: freebsd-pkg@freebsd.org Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\)) X-Mailer: Apple Mail (2.1878.6) X-BeenThere: freebsd-pkg@freebsd.org X-Mailman-Version: 2.1.18 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, 25 Jul 2014 18:53:40 -0000 (Please Cc: any replies to me directly because I am not subscribed to=20 this list.) I've been using pkgng for quite a while now, largely in tandem with=20 poudriere. I build custom pkgng repositories for several systems and=20 have been very, very happy with the setup. The recent upgrade of pkg to 1.3 has caused a few problems. I've also=20= had to get used to a few new behaviours (like "pkg delete" offering to=20= delete dependent packages rather than just refusing to do so unless you=20= force it with "-f" or use "-R"). A minor problem I encountered is that "ENABLED: NO" in my repository=20 .conf file no longer appears to disable the repository as it had done=20 under pkg 1.2. It wasn't until I used "enabled: no" that pkg 1.3=20 considered the repository disabled. The biggest problem I've encountered, however, is that "pkg upgrade"=20 does not seem to recognise all the updates that are available. I'm not=20= sure whether this is a pkg problem or a poudriere problem. (I'm=20 currently running pkg 1.3.0 and poudriere 3.0.16.) When I did a "pkg=20 upgrade" on the client machine, it upgraded pkg from 1.2.7_4 to 1.3.0. =20= For some reason, it complained about an "internal solver error" and=20 also went through two rounds of updates (are the multiple rounds of=20 updates to be expected with pkg 1.3?): =3D=3D=3D=3D=3D # pkg upgrade Updating repository catalogue digests.txz = 100% 7760 7.6KB/s 7.6KB/s 00:00 =20 packagesite.txz = 100% 43KB 43.2KB/s 43.2KB/s 00:00 =20 Incremental update completed, 152 packages processed: 151 packages updated, 1 removed and 1 added. New version of pkg detected; it needs to be installed first. Upgrades have been requested for the following 1 packages: Upgrading pkg: 1.2.7_4 -> 1.3.0 [releng_9_3] The upgrade will require 823 kB more space 1 MB to be downloaded Proceed with upgrading packages [y/N]: y pkg-1.3.0.txz = 100% 1936KB 1.9MB/s 1.9MB/s 00:00 =20 Checking integrity... done [1/1] Upgrading pkg from 1.2.7_4 to 1.3.0... done If you are upgrading from the old package format, first run: # pkg2ng Updating repository catalogue pkg: Repo "releng_9_3" upgrade schema 2006 to 2007: Add conflicts and = provides pkg: Repo "releng_9_3" upgrade schema 2007 to 2008: Add FTS index pkg: Repo "releng_9_3" upgrade schema 2008 to 2009: Optimize indicies pkg: Repo "releng_9_3" upgrade schema 2009 to 2010: Add legacy digest = field releng_9_3 repository catalogue is up-to-date, no need to fetch fresh = copy pkg: Repo "releng_9_2" upgrade schema 2006 to 2007: Add conflicts and = provides pkg: Repo "releng_9_2" upgrade schema 2007 to 2008: Add FTS index pkg: Repo "releng_9_2" upgrade schema 2008 to 2009: Optimize indicies pkg: Repo "releng_9_2" upgrade schema 2009 to 2010: Add legacy digest = field Fetching meta.txz: 100% of 292 B = =20 Fetching digests.txz: 100% of 7 kB = =20 Fetching packagesite.txz: 100% of 42 kB = =20 Removing expired entries: 100% Adding new entries: 100% Incremental update completed, 152 packages processed: 151 packages updated, 3 removed and 1 added. Updating database digests format: 100% Checking for upgrades: 100% pkg: internal solver error: more than two packages to install(2) from = the same uid: apache22~www/apache22 The following 14 packages will be affected (of 96 checked): New packages to be INSTALLED: libevent2: 2.0.21_2 [releng_9_3] Installed packages to be UPGRADED: tmux: 1.9.a_1 -> 1.9.a_2 [releng_9_3] sudo: 1.8.10.p3 -> 1.8.10.p3_1 [releng_9_3] postfix: 2.11.1_1,1 -> 2.11.1_2,1 [releng_9_3] pam_ldap: 1.8.6_2 -> 1.8.6_3 [releng_9_3] openldap-client: 2.4.39 -> 2.4.39_1 [releng_9_3] git: 2.0.1 -> 2.0.2 [releng_9_3] curl: 7.37.0 -> 7.37.1_2 [releng_9_3] apr: 1.5.1.1.5.3_2 -> 1.5.1.1.5.3_3 [releng_9_3] Installed packages to be REINSTALLED: pcre-8.34_1 [releng_9_2] (options changed) ImageMagick-nox11-6.8.9.4_1,1 [releng_9_3] (options changed) fontconfig-2.11.0_3,1 [releng_9_3] (options changed) tiff-4.0.3_4 [releng_9_2] (options changed) libwmf-nox11-0.2.8.4_11 [releng_9_2] (options changed) The process will require 5 MB more space 12 MB to be downloaded Proceed with this action [y/N]: y Fetching tmux-1.9.a_2.txz: 100% of 173 kB = =20 Fetching libevent2-2.0.21_2.txz: 100% of 267 kB = =20 Fetching sudo-1.8.10.p3_1.txz: 100% of 440 kB = =20 Fetching postfix-2.11.1_2,1.txz: 100% of 1 MB = =20 Fetching pcre-8.34_1.txz: 100% of 1 MB = =20 Fetching pam_ldap-1.8.6_3.txz: 100% of 27 kB = =20 Fetching openldap-client-2.4.39_1.txz: 100% of 1 MB = =20 Fetching git-2.0.2.txz: 100% of 2 MB = =20 Fetching curl-7.37.1_2.txz: 100% of 727 kB = =20 Fetching apr-1.5.1.1.5.3_3.txz: 100% of 400 kB = =20 Fetching ImageMagick-nox11-6.8.9.4_1,1.txz: 100% of 2 MB = =20 Fetching fontconfig-2.11.0_3,1.txz: 100% of 190 kB = =20 Fetching tiff-4.0.3_4.txz: 100% of 795 kB = =20 Fetching libwmf-nox11-0.2.8.4_11.txz: 100% of 989 kB = =20 Checking integrity... done (1 conflicting) pkg: internal solver error: more than two packages to install(2) from = the same uid: apache22~www/apache22 Checking integrity... done (0 conflicting) pkg: internal solver error: more than two packages to install(2) from = the same uid: apache22~www/apache22 Conflicts with the existing packages have been found. One more solver iteration is needed to resolve them. The following 15 packages will be affected (of 96 checked): Installed packages to be REMOVED: libevent-1.4.14b_3 New packages to be INSTALLED: libevent2: 2.0.21_2 [releng_9_3] Installed packages to be UPGRADED: openldap-client: 2.4.39 -> 2.4.39_1 [releng_9_3] curl: 7.37.0 -> 7.37.1_2 [releng_9_3] tmux: 1.9.a_1 -> 1.9.a_2 [releng_9_3] sudo: 1.8.10.p3 -> 1.8.10.p3_1 [releng_9_3] postfix: 2.11.1_1,1 -> 2.11.1_2,1 [releng_9_3] pam_ldap: 1.8.6_2 -> 1.8.6_3 [releng_9_3] git: 2.0.1 -> 2.0.2 [releng_9_3] apr: 1.5.1.1.5.3_2 -> 1.5.1.1.5.3_3 [releng_9_3] Installed packages to be REINSTALLED: pcre-8.34_1 [releng_9_2] (options changed) tiff-4.0.3_4 [releng_9_2] (options changed) fontconfig-2.11.0_3,1 [releng_9_3] (options changed) libwmf-nox11-0.2.8.4_11 [releng_9_2] (options changed) ImageMagick-nox11-6.8.9.4_1,1 [releng_9_3] (options changed) The process will require 4 MB more space Proceed with this action [y/N]: y [1/15] Reinstalling pcre-8.34_1: 100% [2/15] Deleting libevent-1.4.14b_3: 100% [3/15] Reinstalling tiff-4.0.3_4: 100% [4/15] Installing libevent2-2.0.21_2: 100% [5/15] Upgrading openldap-client from 2.4.39 to 2.4.39_1: 100% [6/15] Upgrading curl from 7.37.0 to 7.37.1_2: 100% [7/15] Reinstalling fontconfig-2.11.0_3,1: 100% Running fc-cache to build fontconfig cache... /usr/local/share/fonts: skipping, no such directory /usr/local/lib/X11/fonts: caching, new cache contents: 0 fonts, 1 dirs /usr/local/lib/X11/fonts/local: caching, new cache contents: 0 fonts, 0 = dirs /root/.local/share/fonts: skipping, no such directory /root/.fonts: skipping, no such directory /usr/local/share/fonts: skipping, no such directory /usr/local/lib/X11/fonts: caching, new cache contents: 0 fonts, 1 dirs /root/.local/share/fonts: skipping, no such directory /root/.fonts: skipping, no such directory /var/db/fontconfig: cleaning cache directory /root/.cache/fontconfig: not cleaning non-existent cache directory /root/.fontconfig: not cleaning non-existent cache directory fc-cache: succeeded [8/15] Reinstalling libwmf-nox11-0.2.8.4_11: 100% [9/15] Upgrading tmux from 1.9.a_1 to 1.9.a_2: 100% [10/15] Upgrading sudo from 1.8.10.p3 to 1.8.10.p3_1: 100% =3D=3D=3D> Creating users and/or groups. Using existing group 'mail'. Using existing group 'maildrop'. Using existing group 'postfix'. Using existing user 'postfix'. [11/15] Upgrading postfix from 2.11.1_1,1 to 2.11.1_2,1: 100% Postfix already activated in /etc/mail/mailer.conf [12/15] Upgrading pam_ldap from 1.8.6_2 to 1.8.6_3: 100% =3D=3D=3D> Creating users and/or groups. Using existing group 'git_daemon'. Using existing user 'git_daemon'. [13/15] Upgrading git from 2.0.1 to 2.0.2: 100% Updating /etc/shells [14/15] Upgrading apr from 1.5.1.1.5.3_2 to 1.5.1.1.5.3_3: 100% [15/15] Reinstalling ImageMagick-nox11-6.8.9.4_1,1: 100% # =3D=3D=3D=3D=3D Note that the two "Updating repository catalogue" sections clued me in=20= to the fact that my "releng_9_2" repository was no longer being=20 disabled (see above). I fixed that problem, and now only the=20 "releng_9_3" repository is being used. I was puzzled that www/apache22 was not updated because one of the=20 reasons for doing the "pkg upgrade" was to apply the apache22-2.2.27_6=20= update due to "pkg audit" flagging "apache22-2.2.27_5 is vulnerable". =20= I'd done another poudriere run and seen apache22-2.2.27_6 built. Doing a "pkg upgrade" resulted in being told "Your packages are up to=20 date", however, a "pkg install -f apache22" informs me that it is to be=20= "UPGRADED": =3D=3D=3D=3D=3D # pkg clean -ay Nothing to do. # pkg upgrade Updating repository catalogue releng_9_3 repository catalogue is up-to-date, no need to fetch fresh = copy Checking for upgrades: 100% Checking integrity... done (0 conflicting) Your packages are up to date # pkg update -f Updating repository catalogue Fetching meta.txz: 100% of 292 B = =20 Fetching digests.txz: 100% of 7 kB = =20 Fetching packagesite.txz: 100% of 43 kB = =20 Adding new entries: 100% Incremental update completed, 152 packages processed: 0 packages updated, 0 removed and 152 added. # pkg upgrade Updating repository catalogue releng_9_3 repository catalogue is up-to-date, no need to fetch fresh = copy Checking for upgrades: 100% Checking integrity... done (0 conflicting) Your packages are up to date # pkg install -f apache22 = =20 Updating repository catalogue releng_9_3 repository catalogue is up-to-date, no need to fetch fresh = copy The following 1 packages will be affected (of 76 checked): Installed packages to be UPGRADED: apache22: 2.2.27_5 -> 2.2.27_6 The process will require 3 kB more space 2 MB to be downloaded Proceed with this action [y/N]: y Fetching apache22-2.2.27_6.txz: 100% of 2 MB = =20 Checking integrity... done (0 conflicting) =3D=3D=3D> Creating users and/or groups. Using existing group 'www'. Using existing user 'www'. [1/1] Upgrading apache22 from 2.2.27_5 to 2.2.27_6: 100% # =3D=3D=3D=3D=3D So, "pkg upgrade" doesn't see there's a new version of www/apache22 to=20= install but "pkg install -f" does. This doesn't seem correct to me. I've updated pkg on the poudriere system building the repositories and=20= rebuilt all my repositories from scratch via "poudriere bulk -c -f ..."=20= to clear out the previous packages. The reason why I wondered earlier whether this might be a poudriere=20 problem is that when I last did a "poudriere bulk" I got some output=20 about /packages/meta.txz not being a valid package near the end of the=20= build: =3D=3D=3D=3D=3D [[...]] =3D=3D=3D=3D>> Stopping 2 builders =3D=3D=3D=3D>> Creating pkgng repository pkg-static: /packages/meta.txz is not a valid package: no manifest found Creating repository in /packages: 100% Packing files for repository: 100% =3D=3D=3D=3D>> Cleaning up =3D=3D=3D=3D>> Umounting file systems [[...]] =3D=3D=3D=3D=3D Is pkg 1.3.0 compatible with poudriere 3.0.16? Is there something I need to do poudriere-wise when moving from pkg=20 1.2.27_4 to pkg 1.3.0 on the poudriere repository-building system? The pkg and poudriere combination was working like a champ, but since=20 upgrading pkg to 1.3 I don't know if I can trust it. :-( Cheers, Paul.= From owner-freebsd-pkg@FreeBSD.ORG Fri Jul 25 18:56:31 2014 Return-Path: Delivered-To: freebsd-pkg@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 88390580 for ; Fri, 25 Jul 2014 18:56:31 +0000 (UTC) Received: from mail-we0-x22d.google.com (mail-we0-x22d.google.com [IPv6:2a00:1450:400c:c03::22d]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 0EC7D2190 for ; Fri, 25 Jul 2014 18:56:30 +0000 (UTC) Received: by mail-we0-f173.google.com with SMTP id q58so4607894wes.18 for ; Fri, 25 Jul 2014 11:56:29 -0700 (PDT) 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=TwiyMUa4LYdnFOENnvnE7gEZmX1hKVuA/E9Qh+tOYkM=; b=L+5NOdBRvrM1GnSQyfdmlqQIQY5E3O+kjrbA2a0EJxUoZHVW5SuDQE+PnLOCZ7iSMX Ydzr5pqFQ9qtgH4by/N81CQ7ptK2fukFKriRT9qAXUpXLNCupuRdgRBQtHCEzEiIqZ+M nNl3xg0hlhVlE68K6sL9ijB2Pcma22duM8zE3KzopkBs55WfcVJ8LKCOy4rzuIWbUAqh pLxxEYuCl1Rs95p7/ecytWyUKNAO0bM6QlsB75Is6gKBGKt4rwjQkD3G6GgCWRiQaEUV vhMruNa2Cb2aJTVAEHq5Q2sA8jN2F6Z36i0wqj6ppEWlp/fUm8qsYjVmEW4B/ziVXUxg h0dg== X-Received: by 10.180.149.161 with SMTP id ub1mr7719146wib.32.1406314589268; Fri, 25 Jul 2014 11:56:29 -0700 (PDT) Received: from ivaldir.etoilebsd.net ([2001:41d0:8:db4c::1]) by mx.google.com with ESMTPSA id m8sm19163829wjy.35.2014.07.25.11.56.27 for (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 25 Jul 2014 11:56:27 -0700 (PDT) Sender: Baptiste Daroussin Date: Fri, 25 Jul 2014 20:56:25 +0200 From: Baptiste Daroussin To: Paul Mather Subject: Re: pkg-1.3.0 fails to detect updated package (and other problems) Message-ID: <20140725185625.GF46674@ivaldir.etoilebsd.net> References: <61A4A5AC-947F-47F3-97C5-8EA38A65D871@gromit.dlib.vt.edu> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="+1TulI7fc0PCHNy3" Content-Disposition: inline In-Reply-To: <61A4A5AC-947F-47F3-97C5-8EA38A65D871@gromit.dlib.vt.edu> 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 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, 25 Jul 2014 18:56:31 -0000 --+1TulI7fc0PCHNy3 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Fri, Jul 25, 2014 at 02:53:37PM -0400, Paul Mather wrote: > (Please Cc: any replies to me directly because I am not subscribed to=20 > this list.) >=20 > I've been using pkgng for quite a while now, largely in tandem with=20 > poudriere. I build custom pkgng repositories for several systems and=20 > have been very, very happy with the setup. >=20 > The recent upgrade of pkg to 1.3 has caused a few problems. I've also=20 > had to get used to a few new behaviours (like "pkg delete" offering to=20 > delete dependent packages rather than just refusing to do so unless you= =20 > force it with "-f" or use "-R"). >=20 > A minor problem I encountered is that "ENABLED: NO" in my repository=20 > .conf file no longer appears to disable the repository as it had done=20 > under pkg 1.2. It wasn't until I used "enabled: no" that pkg 1.3=20 > considered the repository disabled. >=20 > The biggest problem I've encountered, however, is that "pkg upgrade"=20 > does not seem to recognise all the updates that are available. I'm not= =20 > sure whether this is a pkg problem or a poudriere problem. (I'm=20 > currently running pkg 1.3.0 and poudriere 3.0.16.) When I did a "pkg=20 > upgrade" on the client machine, it upgraded pkg from 1.2.7_4 to 1.3.0. = =20 > For some reason, it complained about an "internal solver error" and=20 > also went through two rounds of updates (are the multiple rounds of=20 > updates to be expected with pkg 1.3?): >=20 > =3D=3D=3D=3D=3D > # pkg upgrade > Updating repository catalogue > digests.txz = 100% 7760 7.6KB/s 7.6KB/s 00:00 =20 > packagesite.txz = 100% 43KB 43.2KB/s 43.2KB/s 00:00 =20 > Incremental update completed, 152 packages processed: > 151 packages updated, 1 removed and 1 added. > New version of pkg detected; it needs to be installed first. > Upgrades have been requested for the following 1 packages: >=20 > Upgrading pkg: 1.2.7_4 -> 1.3.0 [releng_9_3] >=20 > The upgrade will require 823 kB more space >=20 > 1 MB to be downloaded >=20 > Proceed with upgrading packages [y/N]: y > pkg-1.3.0.txz = 100% 1936KB 1.9MB/s 1.9MB/s 00:00 =20 > Checking integrity... done > [1/1] Upgrading pkg from 1.2.7_4 to 1.3.0... done > If you are upgrading from the old package format, first run: >=20 > # pkg2ng > Updating repository catalogue > pkg: Repo "releng_9_3" upgrade schema 2006 to 2007: Add conflicts and pro= vides > pkg: Repo "releng_9_3" upgrade schema 2007 to 2008: Add FTS index > pkg: Repo "releng_9_3" upgrade schema 2008 to 2009: Optimize indicies > pkg: Repo "releng_9_3" upgrade schema 2009 to 2010: Add legacy digest fie= ld > releng_9_3 repository catalogue is up-to-date, no need to fetch fresh copy > pkg: Repo "releng_9_2" upgrade schema 2006 to 2007: Add conflicts and pro= vides > pkg: Repo "releng_9_2" upgrade schema 2007 to 2008: Add FTS index > pkg: Repo "releng_9_2" upgrade schema 2008 to 2009: Optimize indicies > pkg: Repo "releng_9_2" upgrade schema 2009 to 2010: Add legacy digest fie= ld > Fetching meta.txz: 100% of 292 B = =20 > Fetching digests.txz: 100% of 7 kB = =20 > Fetching packagesite.txz: 100% of 42 kB = =20 > Removing expired entries: 100% > Adding new entries: 100% > Incremental update completed, 152 packages processed: > 151 packages updated, 3 removed and 1 added. > Updating database digests format: 100% > Checking for upgrades: 100% > pkg: internal solver error: more than two packages to install(2) from the= same uid: apache22~www/apache22 > The following 14 packages will be affected (of 96 checked): >=20 > New packages to be INSTALLED: > libevent2: 2.0.21_2 [releng_9_3] >=20 > Installed packages to be UPGRADED: > tmux: 1.9.a_1 -> 1.9.a_2 [releng_9_3] > sudo: 1.8.10.p3 -> 1.8.10.p3_1 [releng_9_3] > postfix: 2.11.1_1,1 -> 2.11.1_2,1 [releng_9_3] > pam_ldap: 1.8.6_2 -> 1.8.6_3 [releng_9_3] > openldap-client: 2.4.39 -> 2.4.39_1 [releng_9_3] > git: 2.0.1 -> 2.0.2 [releng_9_3] > curl: 7.37.0 -> 7.37.1_2 [releng_9_3] > apr: 1.5.1.1.5.3_2 -> 1.5.1.1.5.3_3 [releng_9_3] >=20 > Installed packages to be REINSTALLED: > pcre-8.34_1 [releng_9_2] (options changed) > ImageMagick-nox11-6.8.9.4_1,1 [releng_9_3] (options changed) > fontconfig-2.11.0_3,1 [releng_9_3] (options changed) > tiff-4.0.3_4 [releng_9_2] (options changed) > libwmf-nox11-0.2.8.4_11 [releng_9_2] (options changed) >=20 > The process will require 5 MB more space > 12 MB to be downloaded >=20 > Proceed with this action [y/N]: y > Fetching tmux-1.9.a_2.txz: 100% of 173 kB = =20 > Fetching libevent2-2.0.21_2.txz: 100% of 267 kB = =20 > Fetching sudo-1.8.10.p3_1.txz: 100% of 440 kB = =20 > Fetching postfix-2.11.1_2,1.txz: 100% of 1 MB = =20 > Fetching pcre-8.34_1.txz: 100% of 1 MB = =20 > Fetching pam_ldap-1.8.6_3.txz: 100% of 27 kB = =20 > Fetching openldap-client-2.4.39_1.txz: 100% of 1 MB = =20 > Fetching git-2.0.2.txz: 100% of 2 MB = =20 > Fetching curl-7.37.1_2.txz: 100% of 727 kB = =20 > Fetching apr-1.5.1.1.5.3_3.txz: 100% of 400 kB = =20 > Fetching ImageMagick-nox11-6.8.9.4_1,1.txz: 100% of 2 MB = =20 > Fetching fontconfig-2.11.0_3,1.txz: 100% of 190 kB = =20 > Fetching tiff-4.0.3_4.txz: 100% of 795 kB = =20 > Fetching libwmf-nox11-0.2.8.4_11.txz: 100% of 989 kB = =20 > Checking integrity... done (1 conflicting) > pkg: internal solver error: more than two packages to install(2) from the= same uid: apache22~www/apache22 > Checking integrity... done (0 conflicting) > pkg: internal solver error: more than two packages to install(2) from the= same uid: apache22~www/apache22 > Conflicts with the existing packages have been found. > One more solver iteration is needed to resolve them. > The following 15 packages will be affected (of 96 checked): >=20 > Installed packages to be REMOVED: > libevent-1.4.14b_3 >=20 > New packages to be INSTALLED: > libevent2: 2.0.21_2 [releng_9_3] >=20 > Installed packages to be UPGRADED: > openldap-client: 2.4.39 -> 2.4.39_1 [releng_9_3] > curl: 7.37.0 -> 7.37.1_2 [releng_9_3] > tmux: 1.9.a_1 -> 1.9.a_2 [releng_9_3] > sudo: 1.8.10.p3 -> 1.8.10.p3_1 [releng_9_3] > postfix: 2.11.1_1,1 -> 2.11.1_2,1 [releng_9_3] > pam_ldap: 1.8.6_2 -> 1.8.6_3 [releng_9_3] > git: 2.0.1 -> 2.0.2 [releng_9_3] > apr: 1.5.1.1.5.3_2 -> 1.5.1.1.5.3_3 [releng_9_3] >=20 > Installed packages to be REINSTALLED: > pcre-8.34_1 [releng_9_2] (options changed) > tiff-4.0.3_4 [releng_9_2] (options changed) > fontconfig-2.11.0_3,1 [releng_9_3] (options changed) > libwmf-nox11-0.2.8.4_11 [releng_9_2] (options changed) > ImageMagick-nox11-6.8.9.4_1,1 [releng_9_3] (options changed) >=20 > The process will require 4 MB more space >=20 > Proceed with this action [y/N]: y > [1/15] Reinstalling pcre-8.34_1: 100% > [2/15] Deleting libevent-1.4.14b_3: 100% > [3/15] Reinstalling tiff-4.0.3_4: 100% > [4/15] Installing libevent2-2.0.21_2: 100% > [5/15] Upgrading openldap-client from 2.4.39 to 2.4.39_1: 100% > [6/15] Upgrading curl from 7.37.0 to 7.37.1_2: 100% > [7/15] Reinstalling fontconfig-2.11.0_3,1: 100% > Running fc-cache to build fontconfig cache... > /usr/local/share/fonts: skipping, no such directory > /usr/local/lib/X11/fonts: caching, new cache contents: 0 fonts, 1 dirs > /usr/local/lib/X11/fonts/local: caching, new cache contents: 0 fonts, 0 d= irs > /root/.local/share/fonts: skipping, no such directory > /root/.fonts: skipping, no such directory > /usr/local/share/fonts: skipping, no such directory > /usr/local/lib/X11/fonts: caching, new cache contents: 0 fonts, 1 dirs > /root/.local/share/fonts: skipping, no such directory > /root/.fonts: skipping, no such directory > /var/db/fontconfig: cleaning cache directory > /root/.cache/fontconfig: not cleaning non-existent cache directory > /root/.fontconfig: not cleaning non-existent cache directory > fc-cache: succeeded > [8/15] Reinstalling libwmf-nox11-0.2.8.4_11: 100% > [9/15] Upgrading tmux from 1.9.a_1 to 1.9.a_2: 100% > [10/15] Upgrading sudo from 1.8.10.p3 to 1.8.10.p3_1: 100% > =3D=3D=3D> Creating users and/or groups. > Using existing group 'mail'. > Using existing group 'maildrop'. > Using existing group 'postfix'. > Using existing user 'postfix'. > [11/15] Upgrading postfix from 2.11.1_1,1 to 2.11.1_2,1: 100% > Postfix already activated in /etc/mail/mailer.conf > [12/15] Upgrading pam_ldap from 1.8.6_2 to 1.8.6_3: 100% > =3D=3D=3D> Creating users and/or groups. > Using existing group 'git_daemon'. > Using existing user 'git_daemon'. > [13/15] Upgrading git from 2.0.1 to 2.0.2: 100% > Updating /etc/shells > [14/15] Upgrading apr from 1.5.1.1.5.3_2 to 1.5.1.1.5.3_3: 100% > [15/15] Reinstalling ImageMagick-nox11-6.8.9.4_1,1: 100% > # > =3D=3D=3D=3D=3D >=20 > Note that the two "Updating repository catalogue" sections clued me in=20 > to the fact that my "releng_9_2" repository was no longer being=20 > disabled (see above). I fixed that problem, and now only the=20 > "releng_9_3" repository is being used. >=20 > I was puzzled that www/apache22 was not updated because one of the=20 > reasons for doing the "pkg upgrade" was to apply the apache22-2.2.27_6=20 > update due to "pkg audit" flagging "apache22-2.2.27_5 is vulnerable". =20 > I'd done another poudriere run and seen apache22-2.2.27_6 built. >=20 > Doing a "pkg upgrade" resulted in being told "Your packages are up to=20 > date", however, a "pkg install -f apache22" informs me that it is to be= =20 > "UPGRADED": >=20 > =3D=3D=3D=3D=3D > # pkg clean -ay > Nothing to do. > # pkg upgrade > Updating repository catalogue > releng_9_3 repository catalogue is up-to-date, no need to fetch fresh copy > Checking for upgrades: 100% > Checking integrity... done (0 conflicting) > Your packages are up to date > # pkg update -f > Updating repository catalogue > Fetching meta.txz: 100% of 292 B = =20 > Fetching digests.txz: 100% of 7 kB = =20 > Fetching packagesite.txz: 100% of 43 kB = =20 >=20 > Adding new entries: 100% > Incremental update completed, 152 packages processed: > 0 packages updated, 0 removed and 152 added. > # pkg upgrade > Updating repository catalogue > releng_9_3 repository catalogue is up-to-date, no need to fetch fresh copy > Checking for upgrades: 100% > Checking integrity... done (0 conflicting) > Your packages are up to date > # pkg install -f apache22 = =20 > Updating repository catalogue > releng_9_3 repository catalogue is up-to-date, no need to fetch fresh copy > The following 1 packages will be affected (of 76 checked): >=20 > Installed packages to be UPGRADED: > apache22: 2.2.27_5 -> 2.2.27_6 >=20 > The process will require 3 kB more space > 2 MB to be downloaded >=20 > Proceed with this action [y/N]: y > Fetching apache22-2.2.27_6.txz: 100% of 2 MB = =20 > Checking integrity... done (0 conflicting) > =3D=3D=3D> Creating users and/or groups. > Using existing group 'www'. > Using existing user 'www'. > [1/1] Upgrading apache22 from 2.2.27_5 to 2.2.27_6: 100% > # > =3D=3D=3D=3D=3D >=20 > So, "pkg upgrade" doesn't see there's a new version of www/apache22 to=20 > install but "pkg install -f" does. This doesn't seem correct to me. >=20 > I've updated pkg on the poudriere system building the repositories and=20 > rebuilt all my repositories from scratch via "poudriere bulk -c -f ..."= =20 > to clear out the previous packages. >=20 > The reason why I wondered earlier whether this might be a poudriere=20 > problem is that when I last did a "poudriere bulk" I got some output=20 > about /packages/meta.txz not being a valid package near the end of the=20 > build: >=20 > =3D=3D=3D=3D=3D > [[...]] > =3D=3D=3D=3D>> Stopping 2 builders > =3D=3D=3D=3D>> Creating pkgng repository >=20 > pkg-static: /packages/meta.txz is not a valid package: no manifest found > Creating repository in /packages: 100% > Packing files for repository: 100% > =3D=3D=3D=3D>> Cleaning up > =3D=3D=3D=3D>> Umounting file systems > [[...]] > =3D=3D=3D=3D=3D >=20 > Is pkg 1.3.0 compatible with poudriere 3.0.16? >=20 > Is there something I need to do poudriere-wise when moving from pkg=20 > 1.2.27_4 to pkg 1.3.0 on the poudriere repository-building system? >=20 > The pkg and poudriere combination was working like a champ, but since=20 > upgrading pkg to 1.3 I don't know if I can trust it. :-( >=20 pkg 1.3.1 is on the way to get released and fixes all the issues you are reporting (we hope so :)) I'm tracking a last bug (and yes this is compatible with poudriere 3.0.16 regards, bapt --+1TulI7fc0PCHNy3 Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iEYEARECAAYFAlPSqFkACgkQ8kTtMUmk6EzEMwCfY71lycK/eUYtZUyc4Pkt4/Dw vrQAoLdzZbk8UANJtpYTbLoj2e4GRLpC =LGF2 -----END PGP SIGNATURE----- --+1TulI7fc0PCHNy3-- From owner-freebsd-pkg@FreeBSD.ORG Fri Jul 25 19:04:21 2014 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 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 6A109B7E; Fri, 25 Jul 2014 19:04:21 +0000 (UTC) Received: from gromit.dlib.vt.edu (gromit.dlib.vt.edu [128.173.49.29]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "gromit.dlib.vt.edu", Issuer "Chumby Certificate Authority" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 32EE422A7; Fri, 25 Jul 2014 19:04:21 +0000 (UTC) Received: from pmather.tower.lib.vt.edu (pmather.tower.lib.vt.edu [128.173.51.28]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by gromit.dlib.vt.edu (Postfix) with ESMTPSA id D5412614; Fri, 25 Jul 2014 15:04:19 -0400 (EDT) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\)) Subject: Re: pkg-1.3.0 fails to detect updated package (and other problems) From: Paul Mather In-Reply-To: <20140725185625.GF46674@ivaldir.etoilebsd.net> Date: Fri, 25 Jul 2014 15:04:19 -0400 Content-Transfer-Encoding: 7bit Message-Id: <8AB08BC4-CE9E-47B5-8DF8-17737FC99111@gromit.dlib.vt.edu> References: <61A4A5AC-947F-47F3-97C5-8EA38A65D871@gromit.dlib.vt.edu> <20140725185625.GF46674@ivaldir.etoilebsd.net> To: Baptiste Daroussin X-Mailer: Apple Mail (2.1878.6) Cc: freebsd-pkg@freebsd.org X-BeenThere: freebsd-pkg@freebsd.org X-Mailman-Version: 2.1.18 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, 25 Jul 2014 19:04:21 -0000 On Jul 25, 2014, at 2:56 PM, Baptiste Daroussin wrote: > On Fri, Jul 25, 2014 at 02:53:37PM -0400, Paul Mather wrote: >> (Please Cc: any replies to me directly because I am not subscribed to >> this list.) >> >> I've been using pkgng for quite a while now, largely in tandem with >> poudriere. I build custom pkgng repositories for several systems and >> have been very, very happy with the setup. >> >> The recent upgrade of pkg to 1.3 has caused a few problems. I've also >> had to get used to a few new behaviours (like "pkg delete" offering to >> delete dependent packages rather than just refusing to do so unless you >> force it with "-f" or use "-R"). >> >> A minor problem I encountered is that "ENABLED: NO" in my repository >> .conf file no longer appears to disable the repository as it had done >> under pkg 1.2. It wasn't until I used "enabled: no" that pkg 1.3 >> considered the repository disabled. >> >> The biggest problem I've encountered, however, is that "pkg upgrade" >> does not seem to recognise all the updates that are available. I'm not >> sure whether this is a pkg problem or a poudriere problem. (I'm >> currently running pkg 1.3.0 and poudriere 3.0.16.) When I did a "pkg >> upgrade" on the client machine, it upgraded pkg from 1.2.7_4 to 1.3.0. >> For some reason, it complained about an "internal solver error" and >> also went through two rounds of updates (are the multiple rounds of >> updates to be expected with pkg 1.3?): > [[... etc. ...]] > pkg 1.3.1 is on the way to get released and fixes all the issues you are > reporting (we hope so :)) > > I'm tracking a last bug (and yes this is compatible with poudriere 3.0.16 Thank you, that is great news! I really appreciate pkg + poudriere, as it makes local package management and updating so much easier. I also greatly appreciate how responsive pkgng development has been for those of us who have followed it from early on. Thanks again! Cheers, Paul.