The current stable version of dev-perl/libwww-perl depends on virtual/perl-Compress-Zlib. The current stable version of perl-core/IO-Compress blocks on this virtual (superseding it). Either IO-Compress should satisfy this virtual, or libwww-perl should have its dependencies updated. Updating the virtual would probably be a cleaner solution. Reproducible: Always
(In reply to comment #0) > The current stable version of dev-perl/libwww-perl depends on > virtual/perl-Compress-Zlib. The current stable version of > perl-core/IO-Compress blocks on this virtual (superseding it). That's not true. It blocks | !<virtual/perl-Compress-Zlib-2.017 A later version is stable for your arch. Please show us what you do and the failure. (It fails if you have one of the replaced packages listed in your world file.) > Either > IO-Compress should satisfy this virtual, or libwww-perl should have its > dependencies updated. Updating the virtual would probably be a cleaner > solution. I am waiting for the arch teams to do their job before i can do the cleaning of the tree.
perl-core/Compress-Zlib-2.015 installs the files: /usr/lib64/perl5/vendor_perl/5.8.8/Compress/Zlib.pm /usr/lib64/perl5/vendor_perl/5.8.8/auto/Compress/Zlib/autosplit.ix These are also installed by perl-core/IO-Compress-2.020. So, these packages should block each other. If the intent is that we still want Compress-Zlib installed then this collision should be addressed.
(In reply to comment #2) > perl-core/Compress-Zlib-2.015 installs the files: > > /usr/lib64/perl5/vendor_perl/5.8.8/Compress/Zlib.pm > /usr/lib64/perl5/vendor_perl/5.8.8/auto/Compress/Zlib/autosplit.ix > > These are also installed by perl-core/IO-Compress-2.020. So, these packages > should block each other. If the intent is that we still want Compress-Zlib > installed then this collision should be addressed. No, it's not intended. IO-Compress is the successor. And IO-Compress does block the old packages. So what exactly is your problem? It is intended that the old packages | perl-core/Compress-Zlib | perl-core/IO-Compress-Zlib | perl-core/IO-Compress-Bzip2 | perl-core/IO-Compress-Base are getting uninstalled if you emerge IO-Compress. And it works well, if none of them is listed in your world file.
That part works fine - I have IO-Compress installed fine after getting rid of Compress-Zlib. My issue is that the system wants to bring Compress-Zlib back. That is because I have libwww-perl installed (probably due to some world dependency), and it pulls in the virtual perl-Compress-Zlib, and I no longer have that virtual installed since Compress-Zlib was uninstalled and IO-Compress does not satisfy the virtual. It sounds like perl-Compress-Zlib should require either Compress-Zlib or IO-Compress. Then the virtual will be silently installed and the libwww-perl dependency will be resolved. Is that sufficiently confusing? :)
(In reply to comment #4) > That part works fine - I have IO-Compress installed fine after getting rid of > Compress-Zlib. > > My issue is that the system wants to bring Compress-Zlib back. That is because > I have libwww-perl installed (probably due to some world dependency), and it > pulls in the virtual perl-Compress-Zlib, and I no longer have that virtual > installed since Compress-Zlib was uninstalled and IO-Compress does not satisfy > the virtual. It sounds like perl-Compress-Zlib should require either > Compress-Zlib or IO-Compress. Then the virtual will be silently installed and > the libwww-perl dependency will be resolved. > > Is that sufficiently confusing? :) It just doesn't make sense. Please paste what you do and the output! libwww-perl depends on >=virtual/perl-Compress-Zlib-1.10 virtual/perl-Compress-Zlib-2.020 is stable on amd64 and depends on ~virtual/perl-IO-Compress-2.0.20 So what is: emerge -pvt libwww-perl and emerge -pvt IO-Compress
Marking resolved. Turns out the issue is that paludis uses the dependencies of a package at the time it was installed and not the dependencies stored in portage, so libwww-perl was still pulling in the old dependencies. Reinstalling it made it start pulling in the new dependencies. I'm sure this is really just a feature in disguise. :) Sorry for the wasted time...
