When I try to update my world: # emerge -u -p world These are the packages that I would merge, in order: Calculating world dependencies / !!! all ebuilds that could satisfy "dev-lang/perl" have been masked. !!! (dependency required by "sys-apps/xinetd-2.3.11" [ebuild]) !!! Problem with ebuild sys-apps/xinetd-2.3.11 !!! Possibly a DEPEND/*DEPEND problem. !!! Depgraph creation failed. And of course, when I try to simply install perl itself: perl # emerge perl-5.8.0-r10.ebuild Calculating dependencies | !!! all ebuilds that could satisfy ">=dev-lang/perl-5.8.0" have been masked. !!! Error calculating dependencies. Please correct. The silly thing is, of course I _do_ have perl installed: * dev-lang/perl [ Masked ] Latest version available: 5.8.0-r10 Latest version installed: 5.6.1-r10 Size of downloaded files: 10,800 kB Homepage: http://www.perl.org Description: Larry Wall's Practical Extraction and Reporting Language Except that its still version 5.6.1 since 5.8.0 was always masked or something like that. Now someone was smart enough to entirely remove the 5.6.1-ebuilds and therefore I'm probably unable to update any package that requires perl...
When I copied the file perl-5.6.1-r10.ebuild back to my system, from another machine which I hadn't updated yet, it's working again. Why did the file perl-5.6.1-r10.ebuild get deleted anyway? Perl-5.6.1-r10 is *installed* on my system...
perl-5.8 is masked for default-1.0 profile. perl-5.6.1 has to be put back in asap
i've just put perl-5.6.1 back into portage. also assigning this directly to rac. maybe rac needs to make sure why 5.8 was masked for the default-1.0 profile.
Apart from that, it might be nice if portage was able to determine which packages are installed, before allowing the removal of the necessary files :) I have no clue how that could be achieved, but it might prevent errors like these in the future. I had a similar thing with apache2, when it was still called apache2. After a while it got merged into apache, and the apache2 setup was gone.. I couldn't emerge unmerge it anymore, etc :/
Now that perl 5.6.1 is back in the tree and the default 1.0 profile is "trapped" at 5.6.1, is it safe to close this out?
Closing out based on comments from liquidX on irc
