On 10/08/2014 18:04, Tanstaafl wrote: > On 8/10/2014 11:45 AM, Tanstaafl <[email protected]> wrote: >> I haven't updated in a little while, and am seeing a lot of big >> updates... >> >> The main ones that concern me are: >> >> perl (5.16 > 5.18) > > Ok, a little experimenting to see if I can stage these updates and just > update perl first, I get: > >> # emerge -pvuDN perl >> >> These are the packages that would be merged, in order: >> >> Calculating dependencies... done! >> [ebuild U ] virtual/libintl-0-r1 [0] ABI_X86="(64%*) -32% (-x32)" >> 0 kB >> [ebuild U ] sys-devel/gnuconfig-20140212 [20131128] 44 kB >> [ebuild U ] app-admin/perl-cleaner-2.16 [2.15] 6 kB >> [ebuild U ] sys-libs/db-4.8.30-r1:4.8 [4.8.30:4.8] USE="cxx -doc >> -examples -java -tcl {-test}" ABI_X86="(64%*) (-32) (-x32)" 22,351 kB >> [ebuild U ] dev-lang/perl-5.18.2-r1:0/5.18 [5.16.3:0/5.16] >> USE="berkdb gdbm -debug -doc -ithreads" 13,746 kB >> >> Total: 5 packages (5 upgrades), Size of downloads: 36,147 kB >> >> !!! Multiple package instances within a single package slot have been >> pulled >> !!! into the dependency graph, resulting in a slot conflict: >> >> dev-lang/perl:0 >> >> (dev-lang/perl-5.16.3::gentoo, installed) pulled in by >> =dev-lang/perl-5.16* required by >> (virtual/perl-Attribute-Handlers-0.930.0-r1::gentoo, installed) >> dev-lang/perl:0/5.16=[-build(-)] required by >> (dev-perl/Net-SSLeay-1.550::gentoo, installed) >> dev-lang/perl:0/5.16=[-build(-)] required by >> (dev-perl/IO-Socket-SSL-1.953.0::gentoo, installed) >> dev-lang/perl:0/5.16=[-build(-)] required by >> (dev-perl/Sub-Exporter-0.986.0::gentoo, installed) >> dev-lang/perl:0/5.16=[-build(-)] required by >> (dev-perl/PlRPC-0.202.0-r2::gentoo, installed) >> dev-lang/perl:0/5.16=[-build(-)] required by >> (dev-perl/Net-Daemon-0.480.0-r1::gentoo, installed) >> dev-lang/perl:0/5.16=[-build(-)] required by >> (dev-vcs/git-1.8.5.5::gentoo, installed) >> dev-lang/perl:0/5.16=[-build(-)] required by >> (dev-perl/log-dispatch-2.410.0::gentoo, installed) >> dev-lang/perl:0/5.16=[-build(-)] required by >> (dev-perl/Try-Tiny-0.180.0::gentoo, installed) >> dev-lang/perl:0/5.16=[-build(-)] required by >> (dev-perl/Error-0.170.210::gentoo, installed) >> dev-lang/perl:0/5.16=[-build(-)] required by >> (dev-perl/Package-Stash-XS-0.280.0::gentoo, installed) >> dev-lang/perl:0/5.16=[-build(-)] required by >> (net-analyzer/net-snmp-5.7.3_pre3::gentoo, installed) >> dev-lang/perl:0/5.16=[-build(-)] required by >> (dev-perl/Package-Stash-0.360.0::gentoo, installed) >> (and 1 more with the same problems) >> >> (dev-lang/perl-5.18.2-r1::gentoo, ebuild scheduled for merge) pulled >> in by >> =dev-lang/perl-5.18* required by >> (virtual/perl-MIME-Base64-3.130.0-r3::gentoo, installed) >> (and 3 more with the same problem) > > A little googling suggests that I could resolve this by a simple: > > emerge -C virtual/perl-Attribute-Handlers-0.930.0-r1 > & > emerge -C virtual/perl-MIME-Base64-3.130.0-r3 > > But even if this does resolve the conflicts, what would break > (temporarily) if I removed those? They're virtuals, so... maybe... > nothing? Any way to check?
Nothing will break. Like you say they are virtual and contain no code and deploy nothing. So your system will continue to function as it currently does, and Portage will sort itself out when you next emerge world. Unless of course portage wants to unmerge any of the providers that satisfy the virtuals, and you say "yes" ... :-) -- Alan McKinnon [email protected]
