1 |
On Sat, 2006-10-28 at 12:31 +0200, Bo Ørsted Andresen wrote: |
2 |
> On Saturday 28 October 2006 03:37, Meino Christian Cramer wrote: |
3 |
> > I do an |
4 |
> > |
5 |
> > eix-sync && emerge --pretend --tree --verbose --update --deep world |
6 |
> > |
7 |
> > on a regular basis. |
8 |
> > |
9 |
> > Each time the alsa-headers are offered for update. |
10 |
> > |
11 |
> > If alsa-headers 1.0.13 are installed, alsa-headers 1.0.12 are offered |
12 |
> > for update. |
13 |
> > |
14 |
> > If alsa-headers 1.0.12 are installed, alsa-headers 1.0.13 are offered |
15 |
> > for update. |
16 |
> > |
17 |
> > Seems to be an endless story. |
18 |
> > |
19 |
> > How can I stop them ? |
20 |
> |
21 |
> You should know about now, that we need to see the output of the above command |
22 |
> in order answer that one. Preferably show it when you have |
23 |
> alsa-headers-1.0.13 and emerge wants to downgrade. Also alsa-headers |
24 |
> don't "want" anything. Something else is pulling in the lower version... |
25 |
> |
26 |
|
27 |
I had a similar problem. alsa-utils=1.0.13 was pulling in alsa-header. |
28 |
I found a temporary workaround for the problem by putting alsa-utils, |
29 |
alsa-headers, and alsa-driver above 1.0.11 in /etc/portage/package.mask. |
30 |
I couldn't get alsa-driver-1.0.12 to build anyway... |
31 |
|
32 |
-- |
33 |
gentoo-user@g.o mailing list |