| View previous topic :: View next topic |
| Author |
Message |
dageyra
Apprentice
Joined: 22 Feb 2005
Posts: 186
Location: Terre Haute, IN
|
 Posted: Fri Apr 20, 2012 4:02 am Post subject: Slot conflict with perl [SOLVED] |
 |
|
I am (attempting to) upgrading a server, software-speaking and I am running into a slot conflict with perl. The installed version is perl-5.8.8-r5, upgrade is pulling perl-5.12.4-r1. When I try to do any kind of update, I get a slot conflict:
| Code: |
server ~ # emerge -av perl
* IMPORTANT: 3 news items need reading for repository 'gentoo'.
* Use eselect news to read news items.
These are the packages that would be merged, in order:
Calculating dependencies... done!
[ebuild N ] sys-devel/libperl-5.10.1 0 kB
[ebuild U ] dev-lang/perl-5.12.4-r1 [5.8.8-r5] USE="berkdb gdbm -build -debug -doc -ithreads (-perlsuid%)" 12,069 kB
[ebuild U ] app-admin/perl-cleaner-2.7 [1.04.3] 0 kB
Total: 3 packages (2 upgrades, 1 new), Size of downloads: 12,069 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.12.4-r1::gentoo, ebuild scheduled for merge) pulled in by
>=dev-lang/perl-5.10.1 required by (sys-devel/libperl-5.10.1::gentoo, ebuild scheduled for merge)
(dev-lang/perl-5.8.8-r5::gentoo, installed) pulled in by
~dev-lang/perl-5.8.8 required by (virtual/perl-MIME-Base64-3.07::gentoo, installed)
|
I'm thinking the best option is to temporarily unmerge perl, and then emerge a fresh installation to resolve the slot conflict as I don't know much about them. I would like input on whether this is the best technique or if another option should be used. I've run perl-cleaner and revdep-rebuild, they don't yield any results related to perl (revdep talks about GD library and PHP, "perl-cleaner all" does a lot of work but no emerging).
I can provide more information if necessary, but is the unmerge of perl, even temporarily, a bad idea? I don't mind doing a rebuild once the new version is installed, I just need to get past the slot conflict to get there.
Last edited by dageyra on Sun Apr 29, 2012 8:25 pm; edited 1 time in total |
|
| Back to top |
|
 |
cach0rr0
Moderator
Joined: 13 Nov 2008
Posts: 4117
Location: Houston, Republic of Texas
|
| Posted: Fri Apr 20, 2012 5:13 am Post subject: |
|
|
unmerge this virtual
| Code: |
virtual/perl-MIME-Base64-3.07
|
you may find that another perl package causes the issue to pop up yet again; if it does, unmerge that as well
repeat this with each new package until there are no blockers. no need to torpedo perl itself yet
NOTE: newer versions of that virtual rely on newer versions of perl. I just looked at the ebuild for 3.08 (3.07 is no longer in portage) and it does 5.10 or 5.12
_________________
Lost configuring your system?
dump lspci -n here | see Pappy's guide | Link Stash |
|
| Back to top |
|
|
dageyra
Apprentice
Joined: 22 Feb 2005
Posts: 186
Location: Terre Haute, IN
|
| Posted: Fri Apr 20, 2012 3:19 pm Post subject: |
|
|
| cach0rr0 wrote: | unmerge this virtual
| Code: |
virtual/perl-MIME-Base64-3.07
|
you may find that another perl package causes the issue to pop up yet again; if it does, unmerge that as well
repeat this with each new package until there are no blockers. no need to torpedo perl itself yet
NOTE: newer versions of that virtual rely on newer versions of perl. I just looked at the ebuild for 3.08 (3.07 is no longer in portage) and it does 5.10 or 5.12 |
Thanks for the reply, I had actually started that (so perl-MIME was not the first), then it seemed silly to me that I would need to unmerge all of these dependencies. So you think not every dependency of perl will cause the problem, just certain packages? I don't mind unmerging those, I feel much safer about than perl itself. My main concern is I had a look at the perl dependencies, it includes apache so that is one I will not be able to unmerge. I will give it a go and see how far I can get with the various perl packages. Thanks again. |
|
| Back to top |
|
|
cach0rr0
Moderator
Joined: 13 Nov 2008
Posts: 4117
Location: Houston, Republic of Texas
|
| Posted: Sat Apr 21, 2012 8:25 pm Post subject: |
|
|
| dageyra wrote: | | then it seemed silly to me that I would need to unmerge all of these dependencies. So you think not every dependency of perl will cause the problem, just certain packages? |
indeed i think it's just certain packages that are the issue; packages that are tied to an older version of perl, that for whatever reason dont seem to be upgradeable in the usual way
'course there's always another "torpedo" approach ive taken, based on zero logic and reasoning, that sometimes has yielded desired results, sometimes gets me nowhere:
| Code: |
qlist -CI dev-perl |xargs emerge
|
might be worth a try (qlist is part of portage-utils i believe), no promises, but that might get you past your current hiccup.
_________________
Lost configuring your system?
dump lspci -n here | see Pappy's guide | Link Stash |
|
| Back to top |
|
|
Hu
Watchman
Joined: 06 Mar 2007
Posts: 7678
|
| Posted: Sat Apr 21, 2012 9:21 pm Post subject: |
|
|
| cach0rr0: did you mean not to use --oneshot in the suggested command? As written, your suggestion will add all the discovered packages to the world file. |
|
| Back to top |
|
|
dageyra
Apprentice
Joined: 22 Feb 2005
Posts: 186
Location: Terre Haute, IN
|
| Posted: Sun Apr 29, 2012 8:25 pm Post subject: |
|
|
| Thanks guys, that took care of it (and nothing further after perl-MIME-base64 either). Just one step to cleaning up the system, but your help went a long way (and I learned something new), so thanks a lot. |
|
| Back to top |
|
|
|
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
Portage & Programming
