| View previous topic :: View next topic |
| Author |
Message |
eyoung100
Veteran
Joined: 23 Jan 2004
Posts: 1428
|
 Posted: Thu Jan 08, 2015 10:23 pm Post subject: What's the Deal with Perl Virtuals?? |
 |
|
I could leave this post blank, and still get a valid range of answers, but for sanity's sake, I'll narrow the scope a bit. I have Gentoo Packages - Perl marked as unstable in my accept_keywords file. Earlier this week, during a late after Christmas emerge update world, dev-lang/perl-5.20.1-r4 was sync'ed into my tree, which resulted in Perl 5.18/5.20 upgrade problems. Using the method described there, I was able to resolve the problem. While attempting the fix in the post, and being the old school type that I am, I added packages to my accept_keywords file to accept testing versions of modules in the perl-core category and their corresponding virtuals in the virtuals/perl-* category using the old format to accept the latest version that is in testing. | Code: | virtual/perl-package-name ~arch
perl-core/package-name ~arch |
Notice that I do not let portage modify my portage files by adding the specific version.
This solved most of my issues, but I kept getting the dreaded:
| Code: | * perl-cleaner is stopping here:
* Fix the problem and start perl-cleaner again.
*
* If you encounter blockers involving virtuals and perl-core, here are
* some things to try:
* Remove all perl-core packages from your world file
* emerge --deselect --ask $(qlist -IC 'perl-core/*')
* Update all the installed Perl virtuals
* emerge -uD1a $(qlist -IC 'virtual/perl-*')
* Afterwards re-run perl-cleaner
*
* Note that upgrading Perl with emerge option --ignore-built-slot-operator-deps=y is not supported. |
with a list of about 8 Blockers in the format:
| Code: | | <perl-core/package-name-1.0.0-r1 is blocking virtual/perl-package-name-1.0.11 |
Using | Code: | | eix perl-core/package-name |
and | Code: | | eix virtual/perl-package-name |
I came to the conclusion that some of the perl virtual versions were greater than the versions available in the tree for their corresponding real packages in perl-core. My Question is this:
Why do we/the perl maintainer's group allow perl virtuals in the tree that are greater than their corresponding items in perl core?
It would be so much easier on those of us running perl in ~arch if the higher level virtuals/cores were masked. In the end, I had to mask either the virtual or the perl-core module in package.mask until the version numbers of both the virtual and the core module matched.
_________________
The Birth and Growth of Science is the Death and Atrophy of Art -- Unknown
Registerd Linux User #363735
Adopt a Post | Strip Comments| Emerge Wrapper |
|
| Back to top |
|
 |
khayyam
Watchman
Joined: 07 Jun 2012
Posts: 6227
Location: Room 101
|
| Posted: Thu Jan 08, 2015 11:17 pm Post subject: |
|
|
eyoung100 ...
Briefly, 5.20.1-r4 is a stablization candidate ... you should probably read delfridge's recent blog post on the subject. From that post, and looking at the output above, you're probably using <app-admin/perl-cleaner-2.19 ... though you should probably do as that post suggests WRT package.accept_keywords (so that any uninstalled virtual/perl-* or perl-core/* are similarly keyworded).
best ... khay |
|
| Back to top |
|
|
dilfridge
Developer
Joined: 18 Sep 2010
Posts: 120
Location: Regensburg, Germany
|
| Posted: Thu Jan 08, 2015 11:35 pm Post subject: Re: What's the Deal with Perl Virtuals?? |
|
|
| eyoung100 wrote: | ...
This solved most of my issues, but I kept getting the dreaded:
| Code: | * perl-cleaner is stopping here:
* Fix the problem and start perl-cleaner again.
*
* If you encounter blockers involving virtuals and perl-core, here are
* some things to try:
* Remove all perl-core packages from your world file
* emerge --deselect --ask $(qlist -IC 'perl-core/*')
* Update all the installed Perl virtuals
* emerge -uD1a $(qlist -IC 'virtual/perl-*')
* Afterwards re-run perl-cleaner
*
* Note that upgrading Perl with emerge option --ignore-built-slot-operator-deps=y is not supported. |
with a list of about 8 Blockers in the format...
|
Did you actually try the two commands suggested by perl-cleaner? 
| eyoung100 wrote: |
Why do we/the perl maintainer's group allow perl virtuals in the tree that are greater than their corresponding items in perl core?
It would be so much easier on those of us running perl in ~arch if the higher level virtuals/cores were masked. In the end, I had to mask either the virtual or the perl-core module in package.mask until the version numbers of both the virtual and the core module matched. |
Congratulations, you just managed to downgrade your Perl to a really weird mix of versions... The point is that most perl-core packages should get uninstalled by emerge, because they are not needed!
Here are about 5 blog posts for more information:
http://dilfridge.blogspot.de/search/label/perl
Cheers! |
|
| Back to top |
|
|
eyoung100
Veteran
Joined: 23 Jan 2004
Posts: 1428
|
| Posted: Fri Jan 09, 2015 12:03 am Post subject: Re: What's the Deal with Perl Virtuals?? |
|
|
| dilfridge wrote: | | eyoung100 wrote: | ...
Did you actually try the two commands suggested by perl-cleaner?
| eyoung100 wrote: |
Why do we/the perl maintainer's group allow perl virtuals in the tree that are greater than their corresponding items in perl core?
It would be so much easier on those of us running perl in ~arch if the higher level virtuals/cores were masked. In the end, I had to mask either the virtual or the perl-core module in package.mask until the version numbers of both the virtual and the core module matched. |
Congratulations, you just managed to downgrade your Perl to a really weird mix of versions... The point is that most perl-core packages should get uninstalled by emerge, because they are not needed!
Here are about 5 blog posts for more information:
http://dilfridge.blogspot.de/search/label/perl
Cheers! |
|
Of course I did the commands, I kept repeating perl-cleaner until I had all the offenders in package.mask. All the higher packages that were masked were uninstalled by emerge, and I am using <app-perl/perl-cleaner-2.19. I'll read up tonight and straighten it all out 
UPDATE
I did this properly, cleaning out my package.mask and package.accept_keywords, and followed the blog post. After doing so, I only have one item returning the error I noted above, which is:
virtual/perl-Parse-CPAN-Meta-1.441.400. Making this note so I can file a bug tomorrow. Off to get some much needed sleep.
UPDATE 2
Bug filed under virtual/perl-Parse-CPAN-Meta-1.441.400 is Blocked by perl-core/Parse-CPAN-Meta-1.440.900-r1
_________________
The Birth and Growth of Science is the Death and Atrophy of Art -- Unknown
Registerd Linux User #363735
Adopt a Post | Strip Comments| Emerge Wrapper |
|
| 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
