Re: [gentoo-user] alsa-headers dont know what they want...

2006-10-28 Thread Bo Ørsted Andresen
On Saturday 28 October 2006 03:37, Meino Christian Cramer wrote:
  I do an

eix-sync  emerge --pretend --tree --verbose --update --deep world

  on a regular basis.

  Each time the alsa-headers are offered for update.

  If alsa-headers 1.0.13 are installed, alsa-headers 1.0.12 are offered
  for update.

  If alsa-headers 1.0.12 are installed, alsa-headers 1.0.13 are offered
  for update.

  Seems to be an endless story.

  How can I stop them ?

You should know about now, that we need to see the output of the above command 
in order answer that one. Preferably show it when you have 
alsa-headers-1.0.13 and emerge wants to downgrade. Also alsa-headers 
don't want anything. Something else is pulling in the lower version...

-- 
Bo Andresen


pgpMJs9OFZ7IJ.pgp
Description: PGP signature


Re: [gentoo-user] alsa-headers dont know what they want...

2006-10-28 Thread Daniel Barkalow
On Sat, 28 Oct 2006, Meino Christian Cramer wrote:

 Hi,
 
  I do an
 
eix-sync  emerge --pretend --tree --verbose --update --deep world
 
  on a regular basis.
 
  Each time the alsa-headers are offered for update.
 
  If alsa-headers 1.0.13 are installed, alsa-headers 1.0.12 are offered
  for update.
 
  If alsa-headers 1.0.12 are installed, alsa-headers 1.0.13 are offered
  for update.
  
  Seems to be an endless story.

I think what's going on is that alsa-headers, alsa-lib, and alsa-driver 
have a sort of incorrect set of dependancies between them. AFAICT, 
alsa-driver shouldn't depend on alsa-headers at all, because it seems to 
be fine to build ALSA userspace against a newer version of the headers 
than your kernel actually supports (which happens automatically and 
silently if you're not using alsa-driver; the kernel source has an older 
version of ALSA than is the default version of alsa-headers, and no 
dependancy on it).

In any case, alsa-lib and alsa-driver don't have dependancies between 
them, but each depends on having a matching verison of the headers, and 
only alsa-lib permits a newer version of the headers, and alsa-driver is 
currently behind, and emerge doesn't back-propagate dependancy 
information, but nothing bad actually seems to happen.

-Daniel
*This .sig left intentionally blank*
-- 
gentoo-user@gentoo.org mailing list



Re: [gentoo-user] alsa-headers dont know what they want...

2006-10-28 Thread Meino Christian Cramer
From: Bo Ørsted Andresen [EMAIL PROTECTED]
Subject: Re: [gentoo-user] alsa-headers dont know what they want...
Date: Sat, 28 Oct 2006 12:31:56 +0200

 On Saturday 28 October 2006 03:37, Meino Christian Cramer wrote:
   I do an
 
 eix-sync  emerge --pretend --tree --verbose --update --deep world
 
   on a regular basis.
 
   Each time the alsa-headers are offered for update.
 
   If alsa-headers 1.0.13 are installed, alsa-headers 1.0.12 are offered
   for update.
 
   If alsa-headers 1.0.12 are installed, alsa-headers 1.0.13 are offered
   for update.
 
   Seems to be an endless story.
 
   How can I stop them ?
 
 You should know about now, that we need to see the output of the above 
 command 
 in order answer that one. Preferably show it when you have 
 alsa-headers-1.0.13 and emerge wants to downgrade. Also alsa-headers 
 don't want anything. Something else is pulling in the lower version...
 
 -- 
 Bo Andresen

Hi Bo!

 I have looked through all my logs and found the following:

Script started on Wed Oct 25 13:54:08 2006
These are the packages that would be merged, in reverse order:

These are the packages that would be merged, in reverse order:

Calculating world dependencies... done!
[ebuild U ] x11-libs/qt-4.1.4-r2 [4.1.4] USE=cups gif jpeg opengl png zlib 
-accessibility -debug -doc -examples -firebird -mng -mysql -nas -nis -odbc 
-postgres -sqlite -xinerama 0 kB
[nomerge  ] media-sound/alsa-driver-1.0.12  USE=oss -debug -doc
[ebuild UD]  media-sound/alsa-headers-1.0.12 [1.0.13] 0 kB

Then, next time:

These are the packages that would be merged, in reverse order:

Calculating world dependencies... done!
[nomerge  ] media-plugins/gst-plugins-alsa-0.10.4
[nomerge  ]  media-libs/alsa-lib-1.0.13  USE=-debug -doc
[ebuild U ]   media-sound/alsa-headers-1.0.13 [1.0.12] 0 kB

Then, next time:

These are the packages that would be merged, in reverse order:

Calculating world dependencies... done!
[nomerge  ] media-sound/alsa-driver-1.0.12  USE=oss -debug -doc
[ebuild UD]  media-sound/alsa-headers-1.0.12 [1.0.13] 0 kB

Then next time:

These are the packages that would be merged, in reverse order:

Calculating world dependencies... done!
[ebuild U ] app-misc/screen-4.0.3 [4.0.2-r5] USE=pam -debug -multiuser 
-nethack (-selinux) 820 kB
[ebuild U ] sys-apps/net-tools-1.60-r12 [1.60-r11] USE=nls -static 102 kB
[nomerge  ] media-plugins/gst-plugins-alsa-0.10.4
[nomerge  ]  media-libs/alsa-lib-1.0.13  USE=-debug -doc
[ebuild U ]   media-sound/alsa-headers-1.0.13 [1.0.12] 0 kB

Then next time:

These are the packages that would be merged, in reverse order:

These are the packages that would be merged, in reverse order:

Calculating world dependencies... done!
[nomerge  ] media-sound/alsa-driver-1.0.12  USE=oss -debug -doc
[ebuild UD]  media-sound/alsa-headers-1.0.12 [1.0.13] 0 kB

Then next time:

These are the packages that would be merged, in reverse order:

Calculating world dependencies... done!
[nomerge  ] dev-dotnet/gtk-sharp-2.8.0  USE=-doc
[ebuild U ]  dev-lang/mono-1.1.13.8.1 [1.1.13.6] USE=X nptl 17,342 kB
[ebuild U ] app-arch/unrar-3.6.8 [3.6.7] 122 kB
[nomerge  ] media-plugins/gst-plugins-alsa-0.10.4
[nomerge  ]  media-libs/alsa-lib-1.0.13  USE=-debug -doc
[ebuild U ]   media-sound/alsa-headers-1.0.13 [1.0.12] 0 kB
[nomerge  ]  media-libs/gst-plugins-base-0.10.8  USE=X alsa esd oss xv 
-debug
[nomerge  ]   dev-libs/glib-2.10.3  USE=-debug -doc -hardened
[nomerge  ]sys-libs/glibc-2.4-r3  USE=nls nptl nptlonly -build 
-glibc-compat20 -glibc-omitfp -hardened (-multilib) -profile (-selinux)
[ebuild U ] sys-libs/timezone-data-2006n [2006g] 336 kB

Then next time:

These are the packages that would be merged, in reverse order:

Calculating world dependencies... done!
[nomerge  ] dev-util/gtk-doc-1.6-r1  USE=-debug -doc -emacs
[nomerge  ]  app-text/openjade-1.3.2-r1
[ebuild U ]   app-text/opensp-1.5.2-r1 [1.5.1] USE=nls -doc% 1,485 kB
[ebuild U ] media-sound/alsa-driver-1.0.13 [1.0.12] USE=oss -debug -doc 0 
kB
[nomerge  ] x11-terms/xterm-218  USE=truetype -Xaw3d -paste64 -toolbar 
-unicode
[nomerge  ]  sys-libs/libutempter-1.1.4.1
[nomerge  ]   app-arch/rpm2targz-9.0-r3
[nomerge  ]x11-apps/xinit-1.0.2-r6  USE=-debug -minimal
[nomerge  ] x11-apps/xsm-1.0.1  USE=-debug -xprint
[ebuild U ]  net-misc/netkit-rsh-0.17-r7 [0.17-r6] USE=pam 0 kB

(last was included for the sake of completeness)



Each time I submitted the command:

eix-sync  emerge --pretend --tree --verbose --update --deep world

and, after checking the the output the command:

emerge -1 --verbose --update --deep world

(yes, I know, there are more efficient ways to do that tasks...)


Sorry for my german English which generates thing like ...headers
wants... and such. My English is far from perfect.

Kind regards,
mcc



-- 
gentoo-user@gentoo.org mailing list



Re: [gentoo-user] alsa-headers dont know what they want...

2006-10-28 Thread Bo Ørsted Andresen
On Sunday 29 October 2006 03:21, Meino Christian Cramer wrote:
[SNIP]
 [nomerge  ] media-sound/alsa-driver-1.0.12  USE=oss -debug -doc
 [ebuild UD]   media-sound/alsa-headers-1.0.12 [1.0.13] 0 kB

So alsa-driver-1.0.12 was pulling in the lower version of alsa-headers.

[SNIP]
 [ebuild U ] media-sound/alsa-driver-1.0.13 [1.0.12] USE=oss -debug
 -doc 0 kB
[SNIP]

And here alsa-driver is upgraded theryby resolving your issue. Congrats!

 Sorry for my german English which generates thing like ...headers
 wants... and such. My English is far from perfect.

If only that was your only problem. Am I the only who is quite pissed by 
Meino's custom to reply to every mail off-list?

-- 
Bo Andresen


pgpuYiHx5le87.pgp
Description: PGP signature


[gentoo-user] alsa-headers dont know what they want...

2006-10-27 Thread Meino Christian Cramer
Hi,

 I do an

   eix-sync  emerge --pretend --tree --verbose --update --deep world

 on a regular basis.

 Each time the alsa-headers are offered for update.

 If alsa-headers 1.0.13 are installed, alsa-headers 1.0.12 are offered
 for update.

 If alsa-headers 1.0.12 are installed, alsa-headers 1.0.13 are offered
 for update.
 
 Seems to be an endless story.

 How can I stop them ?
 
 Keep hacking!
 mcc

-- 
gentoo-user@gentoo.org mailing list