Can't emerge -UD, some problem with alsa*-0.9.8 that I installed (needed to for my gs-sources kernel otherwise sound wouldn't work) # emerge -puUDv world These are the packages that I would merge, in order: Calculating world dependencies | !!! all ebuilds that could satisfy ">=media-libs/alsa-lib-0.9.8" have been masked. !!! (dependency required by "media-sound/alsa-utils-0.9.8" [ebuild]) !!! Problem with ebuild media-sound/alsa-utils-0.9.8 !!! Possibly a DEPEND/*DEPEND problem. !!! Depgraph creation failed. # etcat -v alsa-utils [ Results for search key : alsa-utils ] [ Applications found : 1 ] * media-sound/alsa-utils : [ ] media-sound/alsa-utils-0.5.10-r8 (0.5) [ ] media-sound/alsa-utils-0.9.0_rc2 (0.9) [ ] media-sound/alsa-utils-0.9.2 (0.9) [M~ ] media-sound/alsa-utils-0.9.3 (0.9) [M~ ] media-sound/alsa-utils-0.9.4 (0.9) [M~ ] media-sound/alsa-utils-0.9.5 (0.9) [M~ ] media-sound/alsa-utils-0.9.6 (0.9) [M~ ] media-sound/alsa-utils-0.9.6-r1 (0.9) [M~ ] media-sound/alsa-utils-0.9.7 (0.9) [M~I] media-sound/alsa-utils-0.9.8 (0.9) # etcat -v alsa-lib [ Results for search key : alsa-lib ] [ Applications found : 1 ] * media-libs/alsa-lib : [ ] media-libs/alsa-lib-0.5.10b (0) [ ] media-libs/alsa-lib-0.9.0_rc2 (0) [ ] media-libs/alsa-lib-0.9.2 (0) [M~ ] media-libs/alsa-lib-0.9.6 (0) [M~ ] media-libs/alsa-lib-0.9.7 (0) [M~I] media-libs/alsa-lib-0.9.8 (0) Reproducible: Always Steps to Reproduce: 1.emerge -puUDv world Actual Results: emer Portage 2.0.49-r15 (default-x86-1.4, gcc-3.2.3, glibc-2.3.2-r1, 2.4.23_pre8-gss) ================================================================= System uname: 2.4.23_pre8-gss i686 Intel(R) Pentium(R) 4 CPU 2.40GHz Gentoo Base System version 1.4.3.10 ccache version 2.3 [enabled] ACCEPT_KEYWORDS="x86" AUTOCLEAN="yes" CFLAGS="-O3 -march=pentium4 -funroll-loops -fprefetch-loop-arrays -pipe" CHOST="i686-pc-linux-gnu" COMPILER="gcc3" CONFIG_PROTECT="/etc /var/qmail/control /usr/kde/2/share/config /usr/kde/3/share /config /var/bind /usr/X11R6/lib/X11/xkb /usr/kde/3.1/share/config /usr/share/co nfig" CONFIG_PROTECT_MASK="/etc/gconf /etc/env.d" CXXFLAGS="-O3 -march=pentium4 -funroll-loops -fprefetch-loop-arrays -pipe" DISTDIR="/usr/portage/distfiles" FEATURES="autoaddcvs sandbox ccache userpriv usersandbox cvs" GENTOO_MIRRORS="http://oss.redundant.com/pub/gentoo http://gentoo.ccccom.com http://gentoo.noved.org/ http://mirror.tucdemonic.org/gentoo/" MAKEOPTS="-j2" PKGDIR="/usr/portage/packages" PORTAGE_TMPDIR="/var/tmp" PORTDIR="/usr/portage" PORTDIR_OVERLAY="/usr/local/portage" SYNC="rsync://rsync.gentoo.org/gentoo-portage" USE="x86 oss apm avi crypt cups encode foomaticdb gif jpeg gnome libg++ mad mikmod mpeg ncurses nls pdflib png quicktime spell truetype xml2 xmms xv zlib gdbm berkdb slang readline arts aalib svga java X sdl gpm tcpd pam libwww ssl perl python esd imlib oggvorbis gtk qt kde motif opengl mozilla apache xml tcltk imap maildir gnupg alsa"
*** This bug has been marked as a duplicate of 13616 ***
I read the bug 13616 and I don't quite see how this problem is a duplicate of that feature request ? Would you mind explaining, it may help someone else ? Also; is there a workaround: ie, how can I emerge -uUD world now ? (the only I found for now is doing emerge -puDv first and then manually emerging all the packages that wouldn't be downgrades... or am I supposed somehow to indicate in some config files the packages for which I want the ACCEPT_KEYWORDS="~x86" so portage remembers those and I don't need the "U" option anymore ?)
you use a stable system you want to use an unstable package ... you dont want to use the stable version of it ... thus you want 'per package settings' hence the dupe
I have a number of other packages that were masked, those one (alsa-* 0.9.8) are they only one which started preventing me from emerge'ing -uUD ; so it sounds like there is a bug in those ebuilds ? Also the FR is about USE which wouldn't solve my "per package" ACCEPT_KEYWORDS need, would it ?
allowing for an unmasked package in a stable system is the same idea ... per package settings, not just USE ... if you do ACCEPT_KEYWORDS="~x86" can you run the emerge world ? if so, remove alsa-utils from your world file /var/cache/edb/world ... i dont know how you emerged your previous packages but it could be that they werent placed in your world file before thus you didnt get errors with them ...
ACCEPT_KEYWORDS="~x86" emerge -puUDv does complete without errors but wouldn't be at all what I need: I want stable packages for everything but a handful of package where I need the bleeding edge The other packages where I have a masked version (fetchmail, snort, ecasound, tightvnc) are in my world file; when I remove alsa-utils from my world file, it then start complaining about: Calculating world dependencies - !!! all ebuilds that could satisfy "~media-sound/madplay-0.15.0b" have been masked. !!! (dependency required by "media-sound/mad-0.15.0b" [ebuild]) !!! Problem with ebuild media-sound/audacity-1.1.3 !!! Possibly a DEPEND/*DEPEND problem. removing audacity, it complains about alsa-tools, alsamixergui then finally -puUDv completes with: [ebuild N ] media-sound/alsa-driver-0.9.2 which I think is the root problem, some packages requires that one and is not satisfied with the -0.9.8 I already have installed ?
I think I know why: # etcat -v alsa-driver [ Results for search key : alsa-driver ] [ Applications found : 1 ] * media-sound/alsa-driver : [ ] media-sound/alsa-driver-0.5.12a (0.5) [ ] media-sound/alsa-driver-0.9.0_rc2 (0.9) [ ] media-sound/alsa-driver-0.9.2 (0.9) [M~ ] media-sound/alsa-driver-0.9.6 (0.9) [M~ ] media-sound/alsa-driver-0.9.7-r3 (0.9) [M~ ] media-sound/alsa-driver-0.9.7-r4 (0.9) [M~I] media-sound/alsa-driver-0.9.8 (2.4.20) IE: 0.9.8 is saying "2.4.20" and not "0.9" is there a way to make 0.9.8 be both ? or is that "2.4.20" a (the) bug ? looking at the ebuild: SLOT="${KV}" while up to 0.9.7 it used to say SLOT="0.9" Shouldn't it be set to 0.9 for upgrades to work ? (or is there a way to set it to both, sorry if this is a silly question, I'm not that familiar with the ebuilds)
> I want stable packages for everything but a handful > of package where I need the bleeding edge exactly, that is why this is Bug 13616 *** This bug has been marked as a duplicate of 13616 ***
the SLOT's are correct also ... kernel module packages use ${KV} as their SLOT
> the SLOT's are correct also ... kernel module packages use ${KV} > as their SLOT well they must have been incorrect before then (as it is 0.9 up to but not including alsa-driver-0.9.8) I still believe there is something wrong with the alsa ebuilds specificically, but I don't want to keep reopening the bug either...
alright, well if you feel the matter is still unresolved we can let the sound team take a crack at it ;)
Thanks SpanKY. I tried changing locally the slot to 0.9 and that does not help or isn't enough; I still get: # emerge -puUDv world These are the packages that I would merge, in order: Calculating world dependencies - !!! all ebuilds that could satisfy ">=media-libs/alsa-lib-0.9.8" have been masked. !!! (dependency required by "media-sound/alsa-utils-0.9.8" [ebuild]) !!! Problem with ebuild media-sound/alsa-utils-0.9.8 !!! Possibly a DEPEND/*DEPEND problem. !!! Depgraph creation failed. so I'm updating the summary accordingly
this is not a sound problem, this is a portage problem
Pending changes/improvements in portage (which I'm not sure would actually solve my problem); it seems that whoever wrote the ebuilds for the recent alsa-* packages must have set things up things in a way that breaks, so that makes it a sound (ebuild writer) bug ? Maybe it will all go away if 0.9.8 is unmasked... :-)
any news ? does it work ?
no :-(, no change : # emerge -puUDv world These are the packages that I would merge, in order: Calculating world dependencies \ !!! all ebuilds that could satisfy "~media-sound/madplay-0.15.0b" have been masked. !!! (dependency required by "media-sound/mad-0.15.0b" [ebuild]) !!! Problem with ebuild media-sound/audacity-1.1.3 !!! Possibly a DEPEND/*DEPEND problem. !!! Depgraph creation failed.
you have an other problem mixing your system with stabel & unstable doesn't work with emerge upgrade you have to merge some packages manually or just switch to unstable
this isn't really a bug... closing due to inactivity...
I agree that is bug report is not a bug. Comment #17 led me to believe that "mixing your system with stable & unstable doesn't work with emerge upgrade". I kept looking and finally found a method that works for me. I add it here so others can use emerge upgrade with stable and unstable packages. I did not write this, I just found it. Change the contents of "/etc/portage/package.keywords" to list the masked packages you want to use. ------------------------------------------------ From: Mike Williams <mike <at> gaima.co.uk> Subject: Re: stable and unstable Newsgroups: gmane.linux.gentoo.user Date: Wed, 05 May 2004 21:51:34 +0100 On Wednesday 05 May 2004 21:39, Jesper Fruergaard Andersen wrote: > I am running stable version of packages, without the ~. I have chosen to > install kde 3.2.2 which is masked with ~ in the ebuild. Problem is that now > I can't update because when I try it about as below. How can I fix that. > Shouldn't it be possible to run most packages from stable and selected from > unstable? Yes /etc/portage/package.keywords (if the directory isn't there, create it) kde-base/arts ~x86 kde-base/kde ~x86 kde-base/kde-i18n ~x86 kde-base/kdeaccessibility ~x86 kde-base/kdeaddons ~x86 etc, etc, etc -- Mike Williams
