Hi, you could try adding -D perl-core/IO parameter in resolve command, so that whatever depends on that package is reinstalled and possibly gets its dependencies updated. That usually gets me through most perl/python updates or similar blocks where some package requires something else to be installed at very specific version.
Do similarily for other packages that are blocked this way. 2014-08-03 21:59 GMT+02:00 Martin Sekera <seker...@gmail.com>: > I can't tell if there were any restarts involved because I have already > rebuilt them both as per hasufell's reply. > > About Perl - what is the correct (user) way of handling the current > situation? That is, =perl-5.18* has been stabilized along with several > virtuals, and these depend on || ( =perl-5.18* perl-core/whatever ). The > correct resolution is to remove the old perl-core modules and install > perl-5.18, right? Paludis however doesn't present this in a very > understandable way, e.g.: > > ! perl-core/IO > Reasons: !<perl-core/IO-1.280.0 from > virtual/perl-IO-1.280.0-r1:0::gentoo, !>perl-core/IO-1.280.0-r999 from > virtual/perl-IO-1.280.0-r1:0::gentoo > Unsuitable candidates: > * perl-core/IO-1.25-r1:0::gentoo > Did not meet !<perl-core/IO-1.280.0, use existing if possible, > installing to / (nothing is fine too) from !<perl-core/IO-1.280.0 from > virtual/perl-IO-1.280.0-r1:0::gentoo > > How do I continue with the upgrade? Right now I'm installing =perl-5.18 > using cave perform install and then manually uninstalling the perl-core/* > modules, followed by a forced (cave perform install) rebuild of the virtual > in question (because regular cave resolve wouldn't let me continue due to a > dependency on perl-5.16 in ::installed). It's a tedious and rather > ridiculous task for a human to do. What am I doing wrong? > > On Sat, Aug 2, 2014 at 4:58 PM, Ciaran McCreesh < > ciaran.mccre...@googlemail.com> wrote: > >> On Fri, 1 Aug 2014 22:14:43 +0200 >> Martin Sekera <seker...@gmail.com> wrote: >> > I've been having unusual blockers lately, especially surrounding the >> > =perl-5.18 upgrade, but not exclusive to it. >> >> Unfortunately Gentoo doesn't follow its own policies for perl, so these >> tend to be messy... >> >> > The ::installed one is marked unsuitable without any explanation, and >> > =dev-libs/redland-1.0.16:0::gentoo is rejected because it claims >> > "ssl" is not set. This USE flag, however, is globally set (and even >> > the ::installed one has it set, as confirmed by cave show). >> >> Were there any restarts involved? --dump-restarts might help. >> >> -- >> Ciaran McCreesh >> >> _______________________________________________ >> paludis-user mailing list >> paludis-user@lists.exherbo.org >> http://lists.exherbo.org/mailman/listinfo/paludis-user >> >> > > _______________________________________________ > paludis-user mailing list > paludis-user@lists.exherbo.org > http://lists.exherbo.org/mailman/listinfo/paludis-user > >
_______________________________________________ paludis-user mailing list paludis-user@lists.exherbo.org http://lists.exherbo.org/mailman/listinfo/paludis-user
