Hi, /usr/portage/profiles/package.mask contains >=media-sound/amarok-1.4.10_p20090130-r3 since today and thus masks amarok 2, which is out now and unmasked for 7 months. Is this really intended? Reproducible: Always
Noted here as well on ~x86, it was trying to pull in most of the KDE 3.5.10 stuff I'd got rid of that k3b doesn't need. Commenting out the mask on >=media-sound/amarok-1.4.10_p20090130-r3 solved it. Brutal mask sans sanity check = head scratching.
(In reply to comment #1) > Commenting out the mask on >=media-sound/amarok-1.4.10_p20090130-r3 solved it. > You should use /etc/portage/package.unmask to do this, not edit the stuff in /usr/portage.
Rather only >=media-sound/amarok-1.4.10_p20090130-r3:3.5 should be masked. media-sound/amarok:4 doesn't use media-libs/libmp4v2.
Sorry everyone. This one was my fault entirely - that's what you get for using >= when you want to use =. Fixed in the tree. Please wait a few hours and sync again.
(In reply to comment #2) > (In reply to comment #1) > > Commenting out the mask on >=media-sound/amarok-1.4.10_p20090130-r3 solved it. > > > > You should use /etc/portage/package.unmask to do this, not edit the stuff in > /usr/portage. > Yes, unless you specifically want it to be temporary and overwritten at the next sync... Anyway, it's been fixed.
Yeah, sorry from me too since I saw the mask soon as it was added but missed the > in it. I've unmasked the entire libmp4v2 mask into ~arch now, while it was fixed even before that by jmbsvicetto. Closing as FIXED.