| 1 |
Duncan wrote: |
| 2 |
> "Mark Haney" <mhaney@××××××××××××.org> posted |
| 3 |
> 4951001C.10602@××××××××××××.org, excerpted below, on Tue, 23 Dec 2008 |
| 4 |
> 10:13:32 -0500: |
| 5 |
> |
| 6 |
>> Duncan wrote: |
| 7 |
>>> "Mark Haney" <mhaney@××××××××××××.org> posted |
| 8 |
>>> 494FE6D7.2060408@××××××××××××.org, excerpted below, on Mon, 22 Dec |
| 9 |
>>> 2008 14:13:27 -0500: |
| 10 |
>>> |
| 11 |
>>>> I've been updating my system after having some surgery and taking time |
| 12 |
>>>> off from everything and I've noticed a funny thing. Certain packages |
| 13 |
>>>> are requiring that I install v2.1.4.5 or portage (I'm running 2.1.6.2 |
| 14 |
>>>> now) before updating the other packages. Why is that? |
| 15 |
>>> So you're saying they're asking you to downgrade? Do you have an |
| 16 |
>>> example and is it in the main tree or some overlay (which)? |
| 17 |
> |
| 18 |
>>> What I suspect is happening is that it's depending on a specific |
| 19 |
>>> portage version, say =2.1.4*, instead of a slot, which portage should |
| 20 |
>>> support everything at least in the main tree. |
| 21 |
> |
| 22 |
>> It seems anything java related and mplayer as well. |
| 23 |
> |
| 24 |
>> octavian ~ # emerge -uav ant-core |
| 25 |
>> |
| 26 |
>> These are the packages that would be merged, in order: |
| 27 |
>> |
| 28 |
>> Calculating dependencies... done! |
| 29 |
>> [ebuild UD] sys-apps/portage-2.1.4.5 [2.1.6.2] USE="-build -doc |
| 30 |
>> -epydoc (-selinux)" LINGUAS="-pl" 0 kB *** Portage will stop merging at |
| 31 |
>> this point and reload itself, |
| 32 |
>> then resume the merge. |
| 33 |
>> [ebuild U ] dev-java/ant-core-1.7.1-r2 [1.7.0-r1] USE="-doc -source" |
| 34 |
>> 6,828 kB |
| 35 |
>> |
| 36 |
>> --- |
| 37 |
>> Calculating dependencies... done! |
| 38 |
>> [ebuild UD] sys-apps/portage-2.1.4.5 [2.1.6.2] USE="-build -doc |
| 39 |
>> -epydoc (-selinux)" LINGUAS="-pl" 0 kB [ebuild U ] |
| 40 |
>> dev-java/sun-jre-bin-1.6.0.11 [1.6.0.07] USE="X alsa (-nsplugin) -odbc" |
| 41 |
>> 0 kB |
| 42 |
>> |
| 43 |
>> ---- |
| 44 |
>> [ebuild UD] sys-apps/portage-2.1.4.5 [2.1.6.2] USE="-build -doc |
| 45 |
>> -epydoc (-selinux)" LINGUAS="-pl" 0 kB [ebuild U ] |
| 46 |
>> media-video/mplayer-1.0_rc2_p28058-r1 [1.0_rc2_p27725-r1] USE="X a52 aac |
| 47 |
>> alsa arts ass%* dvd encode iconv ipv6 jpeg mad mmx mp3opengl png |
| 48 |
> |
| 49 |
> Hmm... I'm running the portage-2.2-rcs, unmasked as I had started using |
| 50 |
> the set dependencies before it was masked to get more ~arch testing for |
| 51 |
> 2.1.6*, and I don't see it trying to downgrade portage when I emerge -p |
| 52 |
> any of those here. So it's not a direct portage version issue. |
| 53 |
> |
| 54 |
> Do you happen to have a version of portage in either package.unmask or |
| 55 |
> package.keyword? You're normally running stable, right? Portage-2.1.6* |
| 56 |
> is keyworded ~arch, so if you're normally running stable but had 2.1.6* |
| 57 |
> for some reason and don't have it in package.keywords, that's why it's |
| 58 |
> trying to downgrade. |
| 59 |
> |
| 60 |
|
| 61 |
Well, I had the 2.2_rc series for a while so I could upgrade to KDE |
| 62 |
4.1.3. Then, I moved to 2.1.6.2 when the 2.2 series was pulled from |
| 63 |
~arch. I don't see anything in portage in particular in |
| 64 |
package.keywords or package.unmask about portage. I just manually |
| 65 |
updated to the ~arch version of portage (using ACCEPT_KEYWORDS from the |
| 66 |
CLI). Should I add portage to package.keywords to make this go away? |
| 67 |
|
| 68 |
|
| 69 |
-- |
| 70 |
Frustra laborant quotquot se calculationibus fatigant pro inventione |
| 71 |
quadraturae circuli |
| 72 |
|
| 73 |
Mark Haney |
| 74 |
Sr. Systems Administrator |
| 75 |
ERC Broadband |
| 76 |
(828) 350-2415 |
| 77 |
|
| 78 |
Call (866) ERC-7110 for after hours support |
Archives