From owner-svn-ports-head@FreeBSD.ORG Fri Mar 8 12:25:28 2013 Return-Path: Delivered-To: svn-ports-head@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 3ABF6D09 for ; Fri, 8 Mar 2013 12:25:28 +0000 (UTC) (envelope-from bdrewery@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:1900:2254:206c::16:87]) by mx1.freebsd.org (Postfix) with ESMTP id 0F8F6DCD for ; Fri, 8 Mar 2013 12:25:28 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.6/8.14.6) with ESMTP id r28CPRaM050501 for ; Fri, 8 Mar 2013 12:25:27 GMT (envelope-from bdrewery@freefall.freebsd.org) Received: (from bdrewery@localhost) by freefall.freebsd.org (8.14.6/8.14.6/Submit) id r28CPR2B050495 for svn-ports-head@freebsd.org; Fri, 8 Mar 2013 12:25:27 GMT (envelope-from bdrewery) Received: (qmail 453 invoked from network); 8 Mar 2013 06:25:25 -0600 Received: from unknown (HELO ?10.10.0.24?) (freebsd@shatow.net@10.10.0.24) by sweb.xzibition.com with ESMTPA; 8 Mar 2013 06:25:25 -0600 Message-ID: <5139D8AF.9060208@FreeBSD.org> Date: Fri, 08 Mar 2013 06:25:19 -0600 From: Bryan Drewery Organization: FreeBSD User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130215 Thunderbird/17.0.3 MIME-Version: 1.0 To: Ruslan Makhmatkhanov Subject: Re: svn commit: r313614 - head References: <201303080349.r283nfQl036658@svn.freebsd.org> <513977E5.9060605@yandex.ru> <513978B7.9000107@FreeBSD.org> <513998D0.1070401@yandex.ru> In-Reply-To: <513998D0.1070401@yandex.ru> X-Enigmail-Version: 1.5.1 OpenPGP: id=3C9B0CF9; url=http://www.shatow.net/bryan/bryan.asc Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="----enig2LEPEFTXKAIEPLVAGONBO" Cc: svn-ports-head@freebsd.org, svn-ports-all@freebsd.org, ports-committers@freebsd.org X-BeenThere: svn-ports-head@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: SVN commit messages for the ports tree for head List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 08 Mar 2013 12:25:28 -0000 This is an OpenPGP/MIME signed message (RFC 4880 and 3156) ------enig2LEPEFTXKAIEPLVAGONBO Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable On 3/8/2013 1:52 AM, Ruslan Makhmatkhanov wrote: > Bryan Drewery wrote on 08.03.2013 09:35: >> On 3/7/2013 11:32 PM, Ruslan Makhmatkhanov wrote: >>> Bryan Drewery wrote on 08.03.2013 07:49: >>>> Author: bdrewery >>>> Date: Fri Mar 8 03:49:41 2013 >>>> New Revision: 313614 >>>> URL: http://svnweb.freebsd.org/changeset/ports/313614 >>>> >>>> Log: >>>> - Must force reinstall py-distribute-0.6.35 as it is seen as a >>>> downgrade from py-setuptools-0.6c11_3 >>> >>> Thanks. Would you provide more details on this? I still not using pkg= , >>> so I don't understand what the problem. Just used the same instructio= ns >>> as in previous UPDATING entries. >>> >> >> The package py27-distribute that is replacing py27-setuptools is *olde= r* >> in version from the old package. So a force install is needed. Same as= >> the -f flag for portupgrade. This is due to them not wanting to >> downgrade ports by default. Even when "replacing" or "moving" origins,= >> they will not downgrade without being forced. >=20 > Yes, but they are different applications. Isn't this a bug? I believe > the version should only be checked withing the same application > handling, not different ones... At least portmaster handled this withou= t > a problem. Probably. Portmaster can only handle 1 "-o" at a time. It re-executes itself in an ugly hack to replace the package. So it simply just removes the old and installs the new. Portupgrade and pkg(8) act on jobs/transactions of a set of packages to upgrade. It does seem reasonable that if the origin AND pkgname have changed then a downgrade should not have to be forced. It's just more complexity to put into the transaction calculation since (for both) it is now mostly a "remove all versions older than the current". I actually think I may have fixed this case in portupgrade already, but am not sure. For pkg(8) I've entered this at https://github.com/pkgng/pkgng/issues/464= >=20 >> >> This also happened in devel/pkgconf update in 20120726. >> >> An ugly way to avoid this would be to use a PORTEPOCH higher than the >> old in the new port. >=20 --=20 Regards, Bryan Drewery bdrewery@freenode/EFNet ------enig2LEPEFTXKAIEPLVAGONBO Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (MingW32) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQIcBAEBAgAGBQJROdivAAoJEG54KsA8mwz5nZ4QAJNiYUbbEXFDWgwjD43EKgX5 7equpEVXSEh1eQ0+ujXqEMqUjNXGlgzq5mxbUMdFvz0X7RVN+vpTEaZOMCE/68As usCmv2wKwZJlG2ieTWo6rUdZruO0gczXQt84QxKKt2U70XirddyvH3ZJ5UFNkFqj 8Xb1ahRBCNJz7bQxz055CsHDpOGfLTE4HeA56iq+BS3fC7IxPlCtN0YP7kF/RCed qMilCKBinGEDwQDp/Ee7hQCPRph0aCsBD03sUcjt89Ix4JXFnnSEJ6b2f2pyze76 2J41oYdOVyyS01ToeLayvWvfoccXScLaz1QK1nyzSZjx2+mEOwBAtPtIsIsNzOeR kS4XVHWq2sE6sKr/GAsynuLUKh1x1x8XstHi3CDhc6HVGWGL6+ebVaVre29udDm4 FTDhqL+8FhV1S0sLk668e4lf9hXRTGaOq7UUE6tVwzUONq2y/m7D4MnwAN9VOHaB oUdv4tJg4DwPT8ILqWWtppIiLbtLFq3uwoGATR+/qcEodTPU2eBiKUGD43Awbej0 bAZ4pAA9rxoldzXO3xRa165ipzQWVced9zCV+QlNccJQwDn0RHfzngbkskjAYJ7R 7JK0gUIoRuVGyoXYv4fqhGkPpM5EAupAiydLYvCVXQeIo4BXEG09rAfccWj/3UBL 4boR+5f+BpcIqLULdjZ4 =dcRK -----END PGP SIGNATURE----- ------enig2LEPEFTXKAIEPLVAGONBO--