From owner-freebsd-questions@FreeBSD.ORG Wed Sep 24 18:16:45 2014 Return-Path: Delivered-To: freebsd-questions@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 D9C961E2 for ; Wed, 24 Sep 2014 18:16:45 +0000 (UTC) Received: from be-well.ilk.org (be-well.ilk.org [23.30.133.173]) by mx1.freebsd.org (Postfix) with ESMTP id B2BEE653 for ; Wed, 24 Sep 2014 18:16:45 +0000 (UTC) Received: by be-well.ilk.org (Postfix, from userid 1147) id E011F33C46; Wed, 24 Sep 2014 14:16:38 -0400 (EDT) From: Lowell Gilbert To: "William A. Mahaffey III" Subject: Re: pkg must be version 1.3.8 or greater References: <5422B1C5.1030400@hiwaay.net> Reply-To: freebsd-questions@freebsd.org Date: Wed, 24 Sep 2014 14:16:38 -0400 In-Reply-To: <5422B1C5.1030400@hiwaay.net> (William A. Mahaffey, III's message of "Wed, 24 Sep 2014 06:57:57 -0500") Message-ID: <44vbocyjcp.fsf@be-well.ilk.org> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.3 (berkeley-unix) MIME-Version: 1.0 Content-Type: text/plain Cc: freebsd-questions@freebsd.org X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 24 Sep 2014 18:16:45 -0000 "William A. Mahaffey III" writes: > The portsnap messes with pkg's logic about what needs upgrading & what > doesn't, there have been other posts on this topic over the last > several weeks (notably from me) Aside from the fact that the package repositories lag behind the ports tree (which is unavoidable until someone manages to procure some infinitely fast computers on which the build clusters can run), I can't tell which posts are in question. > .... Ports & Pkg's are usually updated > by the maintainers about weekly, ports often/usually on Wednesday, > Pkg's on Saturday. Maintainers make changes whenever they want (except when a release is being prepared, in which case major changes are discouraged, a process often referred to as a "slush"). Packages are being built continuously, and a full set seems to be taking three or four days at the moment. > My experience is that if you wait until Saturday, > your 'pkg-upgrade' will work as desired & you will be off to the > races. If your particular ports updates happen to be getting committed mid-week, that sounds about right. The build cluster will be fairly certain to have built them into packages three days later. But, again, there's no actual schedule. > Alternatively, you can 'pkg install -yf ....' your pkg & move > on immediately .... In general, for me, you should do any pkg-upgrades > *before* you mess w/ ports. I would expect that to be less annoying than the other way around.