1 |
I would follow that path - I did and it worked out fine. |
2 |
|
3 |
Unmerge all conflicting perl modules |
4 |
|
5 |
emerge world -1NuDv |
6 |
|
7 |
Dont forget perl-cleaner --all immediately afterwards |
8 |
|
9 |
and with the python updates that are probably there too - python-updater |
10 |
|
11 |
enjoy ... |
12 |
|
13 |
Note that some perl modules have disappeared in 5.18 but it didn't cause |
14 |
me any grief I know of. |
15 |
|
16 |
BillK |
17 |
|
18 |
On 11/08/14 00:04, Tanstaafl wrote: |
19 |
> On 8/10/2014 11:45 AM, Tanstaafl <tanstaafl@×××××××××××.org> wrote: |
20 |
>> I haven't updated in a little while, and am seeing a lot of big |
21 |
>> updates... |
22 |
>> |
23 |
>> The main ones that concern me are: |
24 |
>> |
25 |
>> perl (5.16 > 5.18) |
26 |
> |
27 |
> Ok, a little experimenting to see if I can stage these updates and just |
28 |
> update perl first, I get: |
29 |
> |
30 |
>> # emerge -pvuDN perl |
31 |
>> |
32 |
>> These are the packages that would be merged, in order: |
33 |
>> |
34 |
>> Calculating dependencies... done! |
35 |
>> [ebuild U ] virtual/libintl-0-r1 [0] ABI_X86="(64%*) -32% (-x32)" |
36 |
>> 0 kB |
37 |
>> [ebuild U ] sys-devel/gnuconfig-20140212 [20131128] 44 kB |
38 |
>> [ebuild U ] app-admin/perl-cleaner-2.16 [2.15] 6 kB |
39 |
>> [ebuild U ] sys-libs/db-4.8.30-r1:4.8 [4.8.30:4.8] USE="cxx -doc |
40 |
>> -examples -java -tcl {-test}" ABI_X86="(64%*) (-32) (-x32)" 22,351 kB |
41 |
>> [ebuild U ] dev-lang/perl-5.18.2-r1:0/5.18 [5.16.3:0/5.16] |
42 |
>> USE="berkdb gdbm -debug -doc -ithreads" 13,746 kB |
43 |
>> |
44 |
>> Total: 5 packages (5 upgrades), Size of downloads: 36,147 kB |
45 |
>> |
46 |
>> !!! Multiple package instances within a single package slot have been |
47 |
>> pulled |
48 |
>> !!! into the dependency graph, resulting in a slot conflict: |
49 |
>> |
50 |
>> dev-lang/perl:0 |
51 |
>> |
52 |
>> (dev-lang/perl-5.16.3::gentoo, installed) pulled in by |
53 |
>> =dev-lang/perl-5.16* required by |
54 |
>> (virtual/perl-Attribute-Handlers-0.930.0-r1::gentoo, installed) |
55 |
>> dev-lang/perl:0/5.16=[-build(-)] required by |
56 |
>> (dev-perl/Net-SSLeay-1.550::gentoo, installed) |
57 |
>> dev-lang/perl:0/5.16=[-build(-)] required by |
58 |
>> (dev-perl/IO-Socket-SSL-1.953.0::gentoo, installed) |
59 |
>> dev-lang/perl:0/5.16=[-build(-)] required by |
60 |
>> (dev-perl/Sub-Exporter-0.986.0::gentoo, installed) |
61 |
>> dev-lang/perl:0/5.16=[-build(-)] required by |
62 |
>> (dev-perl/PlRPC-0.202.0-r2::gentoo, installed) |
63 |
>> dev-lang/perl:0/5.16=[-build(-)] required by |
64 |
>> (dev-perl/Net-Daemon-0.480.0-r1::gentoo, installed) |
65 |
>> dev-lang/perl:0/5.16=[-build(-)] required by |
66 |
>> (dev-vcs/git-1.8.5.5::gentoo, installed) |
67 |
>> dev-lang/perl:0/5.16=[-build(-)] required by |
68 |
>> (dev-perl/log-dispatch-2.410.0::gentoo, installed) |
69 |
>> dev-lang/perl:0/5.16=[-build(-)] required by |
70 |
>> (dev-perl/Try-Tiny-0.180.0::gentoo, installed) |
71 |
>> dev-lang/perl:0/5.16=[-build(-)] required by |
72 |
>> (dev-perl/Error-0.170.210::gentoo, installed) |
73 |
>> dev-lang/perl:0/5.16=[-build(-)] required by |
74 |
>> (dev-perl/Package-Stash-XS-0.280.0::gentoo, installed) |
75 |
>> dev-lang/perl:0/5.16=[-build(-)] required by |
76 |
>> (net-analyzer/net-snmp-5.7.3_pre3::gentoo, installed) |
77 |
>> dev-lang/perl:0/5.16=[-build(-)] required by |
78 |
>> (dev-perl/Package-Stash-0.360.0::gentoo, installed) |
79 |
>> (and 1 more with the same problems) |
80 |
>> |
81 |
>> (dev-lang/perl-5.18.2-r1::gentoo, ebuild scheduled for merge) pulled |
82 |
>> in by |
83 |
>> =dev-lang/perl-5.18* required by |
84 |
>> (virtual/perl-MIME-Base64-3.130.0-r3::gentoo, installed) |
85 |
>> (and 3 more with the same problem) |
86 |
> |
87 |
> A little googling suggests that I could resolve this by a simple: |
88 |
> |
89 |
> emerge -C virtual/perl-Attribute-Handlers-0.930.0-r1 |
90 |
> & |
91 |
> emerge -C virtual/perl-MIME-Base64-3.130.0-r3 |
92 |
> |
93 |
> But even if this does resolve the conflicts, what would break |
94 |
> (temporarily) if I removed those? They're virtuals, so... maybe... |
95 |
> nothing? Any way to check? |
96 |
> |