On Tue, 2008-12-23 at 14:40 -0500, Mark Haney wrote: > Duncan wrote: > > "Mark Haney" <[email protected]> posted > > [email protected], excerpted below, on Tue, 23 Dec 2008 > > 10:13:32 -0500: > > > >> Duncan wrote: > >>> "Mark Haney" <[email protected]> posted > >>> [email protected], excerpted below, on Mon, 22 Dec > >>> 2008 14:13:27 -0500: > >>> > >>>> I've been updating my system after having some surgery and taking time > >>>> off from everything and I've noticed a funny thing. Certain packages > >>>> are requiring that I install v2.1.4.5 or portage (I'm running 2.1.6.2 > >>>> now) before updating the other packages. Why is that? > >>> So you're saying they're asking you to downgrade? Do you have an > >>> example and is it in the main tree or some overlay (which)? > > > >>> What I suspect is happening is that it's depending on a specific > >>> portage version, say =2.1.4*, instead of a slot, which portage should > >>> support everything at least in the main tree. > > > >> It seems anything java related and mplayer as well. > > > >> octavian ~ # emerge -uav ant-core > >> > >> These are the packages that would be merged, in order: > >> > >> Calculating dependencies... done! > >> [ebuild UD] sys-apps/portage-2.1.4.5 [2.1.6.2] USE="-build -doc > >> -epydoc (-selinux)" LINGUAS="-pl" 0 kB *** Portage will stop merging at > >> this point and reload itself, > >> then resume the merge. > >> [ebuild U ] dev-java/ant-core-1.7.1-r2 [1.7.0-r1] USE="-doc -source" > >> 6,828 kB > >> > >> --- > >> Calculating dependencies... done! > >> [ebuild UD] sys-apps/portage-2.1.4.5 [2.1.6.2] USE="-build -doc > >> -epydoc (-selinux)" LINGUAS="-pl" 0 kB [ebuild U ] > >> dev-java/sun-jre-bin-1.6.0.11 [1.6.0.07] USE="X alsa (-nsplugin) -odbc" > >> 0 kB > >> > >> ---- > >> [ebuild UD] sys-apps/portage-2.1.4.5 [2.1.6.2] USE="-build -doc > >> -epydoc (-selinux)" LINGUAS="-pl" 0 kB [ebuild U ] > >> media-video/mplayer-1.0_rc2_p28058-r1 [1.0_rc2_p27725-r1] USE="X a52 aac > >> alsa arts ass%* dvd encode iconv ipv6 jpeg mad mmx mp3opengl png > > > > Hmm... I'm running the portage-2.2-rcs, unmasked as I had started using > > the set dependencies before it was masked to get more ~arch testing for > > 2.1.6*, and I don't see it trying to downgrade portage when I emerge -p > > any of those here. So it's not a direct portage version issue. > > > > Do you happen to have a version of portage in either package.unmask or > > package.keyword? You're normally running stable, right? Portage-2.1.6* > > is keyworded ~arch, so if you're normally running stable but had 2.1.6* > > for some reason and don't have it in package.keywords, that's why it's > > trying to downgrade. > > > > Well, I had the 2.2_rc series for a while so I could upgrade to KDE > 4.1.3. Then, I moved to 2.1.6.2 when the 2.2 series was pulled from > ~arch. I don't see anything in portage in particular in > package.keywords or package.unmask about portage. I just manually > updated to the ~arch version of portage (using ACCEPT_KEYWORDS from the > CLI). Should I add portage to package.keywords to make this go away? > Probably. I've seen things like that with other packages.
Regards, Ferris -- Ferris McCormick (P44646, MI) <[email protected]> Developer, Gentoo Linux (Sparc, Userrel, Trustees)
signature.asc
Description: This is a digitally signed message part
