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.