Date: Mon, 11 Aug 2014 19:58:18 -0400 From: Adam McDougall <mcdouga9@egr.msu.edu> To: svn-ports-all@freebsd.org Subject: Re: svn commit: r364287 - head/ports-mgmt/pkg-devel Message-ID: <53E9589A.1010408@egr.msu.edu> In-Reply-To: <88dcf721a5ea4bccfb3cf424da694c72@shatow.net> References: <53e39939.55bc.4ca5432c@svn.freebsd.org> <20140807172841.58633e63@kalimero.tijl.coosemans.org> <53E3A468.5050603@FreeBSD.org> <53E3AC0C.5020904@gmx.de> <53E3AD09.2050000@FreeBSD.org> <53E3B3B5.9000104@gmx.de> <53E3B6D8.9080101@FreeBSD.org> <53E590AC.4020105@FreeBSD.org> <53E7A512.8050008@FreeBSD.org> <b1c74ebef13a04a7198ed4a34134d63a@shatow.net> <53E7D193.3090305@FreeBSD.org> <88dcf721a5ea4bccfb3cf424da694c72@shatow.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On 08/11/2014 11:33, Bryan Drewery wrote: > On 2014-08-10 15:09, Vsevolod Stakhov wrote: >> Nonetheless, doesn't our ports policy defines to bump PORTREVISION in >> all cases that modifies a resulting package? Shlib provides/requires >> changing is definitely such a change. So you blame now pkg that it >> follows the current policy, don't you? > > I explained this in private to someone else as well... > > Yes it is the policy, but it is a different thing with packages. If a > bump is missed for ports users it is not a big problem as they can > remedy it with portmaster by rebuilding ports depending on the changed > shlib. Package users have no way to fix their packages, so the remote > must have rebuilt them to link to the new library so the user can have a > working system without needing to checkout ports every time a committer > is lazy about chases. Without a bump, or pkg handling it, it would > result in the user being forced to reinstall packages one by one or with I don't intend to detract from a proper solution, but just to make a point, I can't even easily force individual packages to reinstall right now. pkg upgrade -f p5-Geo-IP-1.43 ignores me, so I have to pkg remove -f p5-Geo-IP-1.43 then install it back and it fetches the fixed package. I filed a bug report to get a proper version bump almost 2 weeks ago and no response: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=192240 The port does not have an individual maintainer, just perl@FreeBSD.org. Could someone jog it along please? Evidence of trouble: Aug 11 19:38:51 hostname spamd[14880]: Can't load '/usr/local/lib/perl5/site_perl/5.16/mach/auto/Geo/IP/IP.so' for module Geo::IP: Shared object "libGeoIP.so.5" not found, required by "IP.so" at /usr/local/lib/perl5/5.16/mach/DynaLoader.pm line 190. Aug 11 19:38:51 hostname spamd[14880]: at /usr/local/lib/perl5/site_perl/5.16/mach/Geo/IP.pm line 21. # ldd /usr/local/lib/perl5/site_perl/5.16/mach/auto/Geo/IP/IP.so /usr/local/lib/perl5/site_perl/5.16/mach/auto/Geo/IP/IP.so: libGeoIP.so.5 => not found (0) # pkg -v 1.3.5.1 # pkg which /usr/local/lib/libGeoIP.so.7 /usr/local/lib/libGeoIP.so.7 was installed by package GeoIP-1.6.0 # pkg which /usr/local/lib/perl5/site_perl/5.16/mach/auto/Geo/IP/IP.so /usr/local/lib/perl5/site_perl/5.16/mach/auto/Geo/IP/IP.so was installed by package p5-Geo-IP-1.43 # pkg upgrade -f p5-Geo-IP-1.43 Updating repository catalogue pkg-egr repository is up-to-date All repositories are up-to-date Checking integrity... done (0 conflicting) Your packages are up to date (force removing and re-installing the package works) > upgrade -f, or saving all shlibs in /usr/local/lib/compat/pkg. It's an > ugly situation. > > I dislike how it is all handled honestly. It destroys the idea of a > reproducible package. >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?53E9589A.1010408>