SEO

#1 (**permalink**) 02-21-2008, 09:38 AM

Hi,

A couple of days ago I sync'd, and the subsequent emerge --pretend -u world
came back with 162 package downgrades. This seems REALLY odd to me. I'm
not doing anything funny like permanently setting ACCEPT_KEYWORDS="~x86",
so it's not as if I have a bunch of masked packages installed. This crazy
amount of downgrades issue actually came up in the sync I performed the day
after I emerge'd KDE 3.4 (and the insane amount of package upgrades that
came along with it). I don't know if that has anything to do with it. I'm
wondering if anyone else is experiencing this. Attached is the output of
emerge --pretend -u world. Thanks.

Mark

#2 (**permalink**) 02-21-2008, 09:38 AM

Mark wrote:
> Hi,
>
> A couple of days ago I sync'd, and the subsequent emerge --pretend -u world
> came back with 162 package downgrades. This seems REALLY odd to me. I'm
> not doing anything funny like permanently setting ACCEPT_KEYWORDS="~x86",
> so it's not as if I have a bunch of masked packages installed. This crazy
> amount of downgrades issue actually came up in the sync I performed the day
> after I emerge'd KDE 3.4 (and the insane amount of package upgrades that
> came along with it). I don't know if that has anything to do with it. I'm
> wondering if anyone else is experiencing this. Attached is the output of
> emerge --pretend -u world. Thanks.

No, it's not KDE3.4's fault, you have most likly had the bad luck of syncing
against a server that isn't up to date itself, resync and it should fix for you.

//Aho

#3 (**permalink**) 02-21-2008, 09:38 AM

J.O. Aho wrote:

> Mark wrote:
>> Hi,
>>
>> A couple of days ago I sync'd, and the subsequent emerge --pretend -u
>> world
>> came back with 162 package downgrades. This seems REALLY odd to me. I'm
>> not doing anything funny like permanently setting ACCEPT_KEYWORDS="~x86",
>> so it's not as if I have a bunch of masked packages installed. This
>> crazy amount of downgrades issue actually came up in the sync I performed
>> the day after I emerge'd KDE 3.4 (and the insane amount of package
>> upgrades that
>> came along with it). I don't know if that has anything to do with it.
>> I'm wondering if anyone else is experiencing this. Attached is the output
>> of
>> emerge --pretend -u world. Thanks.
>
> No, it's not KDE3.4's fault, you have most likly had the bad luck of
> syncing against a server that isn't up to date itself, resync and it
> should fix for you.
>
>
> //Aho

Hmmm. I've sync'd a number of times, but still the same output. Honestly I
don't know if it's syncing with the same server. Is there a way to direct
emerge to sync with a specific server? Seems like there should be. Also,
where would I find a list of servers with which I could sync? Thanks.

Mark

#4 (**permalink**) 02-21-2008, 09:38 AM

Mark wrote:

> Hmmm. I've sync'd a number of times, but still the same output. Honestly I
> don't know if it's syncing with the same server. Is there a way to direct
> emerge to sync with a specific server? Seems like there should be. Also,
> where would I find a list of servers with which I could sync? Thanks.

In the /etc.make.conf you can have a line like:
SYNC="rsync://trumpetti.atm.tut.fi/gentoo-portage"

//Aho

#5 (**permalink**) 02-21-2008, 09:38 AM

J.O. Aho wrote:

> Mark wrote:
>> Hi,
>>
>> A couple of days ago I sync'd, and the subsequent emerge --pretend -u
>> world
>> came back with 162 package downgrades. This seems REALLY odd to me. I'm
>> not doing anything funny like permanently setting ACCEPT_KEYWORDS="~x86",
>> so it's not as if I have a bunch of masked packages installed. This
>> crazy amount of downgrades issue actually came up in the sync I performed
>> the day after I emerge'd KDE 3.4 (and the insane amount of package
>> upgrades that
>> came along with it). I don't know if that has anything to do with it.
>> I'm wondering if anyone else is experiencing this. Attached is the output
>> of
>> emerge --pretend -u world. Thanks.
>
> No, it's not KDE3.4's fault, you have most likly had the bad luck of
> syncing against a server that isn't up to date itself, resync and it
> should fix for you.

It's not even a bad rsync server, but the bad habit of emerging unstable
packages by setting ACCEPT_KEYWORDS on the command line. It's funny that
people still use this instead of /etc/portage/package.*

Downgrading packages would be an option now (might cause further screwups,
baselayout for example has many changes between the current stable und
unstable versions). Or put the affected versions of the packages
in /etc/portage/package.keywords to get back a stable system at some point
in the future.

#6 (**permalink**) 02-21-2008, 09:38 AM

Dennis, dude, thanks for the response...I think. But did you READ what I
said??? I said I'm NOT using ACCEPT_KEYWORDS. Perhaps you were unable to
see what I really wrote from high atop your soap box. Step down. Thanks.

Dennis Nienhüser wrote:

> J.O. Aho wrote:
>
>> Mark wrote:
>>> Hi,
>>>
>>> A couple of days ago I sync'd, and the subsequent emerge --pretend -u
>>> world
>>> came back with 162 package downgrades. This seems REALLY odd to me.
>>> I'm not doing anything funny like permanently setting
>>> ACCEPT_KEYWORDS="~x86",
>>> so it's not as if I have a bunch of masked packages installed. This
>>> crazy amount of downgrades issue actually came up in the sync I
>>> performed the day after I emerge'd KDE 3.4 (and the insane amount of
>>> package upgrades that
>>> came along with it). I don't know if that has anything to do with it.
>>> I'm wondering if anyone else is experiencing this. Attached is the
>>> output of
>>> emerge --pretend -u world. Thanks.
>>
>> No, it's not KDE3.4's fault, you have most likly had the bad luck of
>> syncing against a server that isn't up to date itself, resync and it
>> should fix for you.
>
> It's not even a bad rsync server, but the bad habit of emerging unstable
> packages by setting ACCEPT_KEYWORDS on the command line. It's funny that
> people still use this instead of /etc/portage/package.*
>
> Downgrading packages would be an option now (might cause further screwups,
> baselayout for example has many changes between the current stable und
> unstable versions). Or put the affected versions of the packages
> in /etc/portage/package.keywords to get back a stable system at some point
> in the future.

#7 (**permalink**) 02-21-2008, 09:38 AM

Mark wrote:

> Dennis, dude, thanks for the response...I think. But did you READ
> what I said??? I said I'm NOT using ACCEPT_KEYWORDS. Perhaps you were
> unable to see what I really wrote from high atop your soap box. Step
> down. Thanks.

The *only* way (short of a totally broken portage mirror, which is
highly unlikely) that what you experienced would happen is if you
temporarily set ACCEPT_KEYWORDS="~x86" in some way, when you upgraded to
the masked KDE. I don't care what you say, that's the only way that
would happen. You said you didn't permanently set ACCEPT_KEYWORDS, but
even if you set it temporarily (like on the emerge command line for
upgrading KDE), it would be a *very* BadThing(TM). I think you found
out why.

Now, the *correct* way would be to list all the KDE packages in
/etc/portage/package.keywords, with the syntax that is required there
(the portage manual page has more info).

--
PeKaJe

My other computer is your XP box.

Thread Tools
Show Printable Version Email this Page
Display Modes
Linear Mode Switch to Hybrid Mode Switch to Threaded Mode

SEO

emerge -u world -- large amount of downgrades