Date: Fri, 08 Mar 2013 11:52:48 +0400 From: Ruslan Makhmatkhanov <cvs-src@yandex.ru> To: Bryan Drewery <bdrewery@FreeBSD.org> Cc: svn-ports-head@freebsd.org, svn-ports-all@freebsd.org, ports-committers@freebsd.org Subject: Re: svn commit: r313614 - head Message-ID: <513998D0.1070401@yandex.ru> In-Reply-To: <513978B7.9000107@FreeBSD.org> References: <201303080349.r283nfQl036658@svn.freebsd.org> <513977E5.9060605@yandex.ru> <513978B7.9000107@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
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 instructions >> as in previous UPDATING entries. >> > > The package py27-distribute that is replacing py27-setuptools is *older* > 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. 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 without a problem. > > 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. -- Regards, Ruslan Tinderboxing kills... the drives.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?513998D0.1070401>