Bug 30240 – emerge /path/to/ebuild behaviour changed

• Status: RESOLVED FIXED
• Product: Gentoo Linux

[Description Adam Chodorowski 2003-10-03 05:00:52 UTC]

After having upgraded libsoup to 1.99.26 to satisfy the dependency libgtkhtml
3.0.9 has, I still can't emerge libgtkhtml 3.0.9. It seems like it doesn't
properly identify that I *do* in fact have the right version of libsoup
installed. Transcript:

root@tor[0] 13:55 portage/gnome-extra/libgtkhtml# emerge -up
libgtkhtml-3.0.9.ebuild    

These are the packages that I would merge, in order:

Calculating dependencies |
!!! all ebuilds that could satisfy ">=net-libs/libsoup-1.99.26" have been masked.
!!!    (dependency required by "gnome-extra/libgtkhtml-3.0.9" [ebuild])

!!! Error calculating dependencies. Please correct.
root@tor[1] 13:56 portage/gnome-extra/libgtkhtml# emerge -s libsoup
Searching...   
[ Results for search key : libsoup ]
[ Applications found : 1 ]
 
*  net-libs/libsoup
      Latest version available: 1.99.23
      Latest version installed: 1.99.26
      Size of downloaded files: 215 kB
      Homepage:    http://www.gnome.org/
      Description: Soup is a SOAP implementation


Reproducible: Always
Steps to Reproduce:
1. emerge -u /usr/portage/net-libs/libsoup/libsoup-1.99.26.ebuild
2. emerge -up /usr/portage/gnome-extra/libgtkhtml/libgtkhtml-3.0.9.ebuild


Actual Results:  
Emerge complains that it cannot satisfy the dependency on libsoup 1.99.26, while
in fact it is installed.

Expected Results:  
libgtkhtml should have been emerged.

Portage 2.0.49-r3 (default-x86-1.4, gcc-3.2.3, glibc-2.3.2-r1, 2.4.20-gentoo-r6)
=================================================================
System uname: 2.4.20-gentoo-r6 i686 AMD Duron(tm) Processor
ccache version 2.2 [enabled]
ACCEPT_KEYWORDS="x86"
AUTOCLEAN="yes"
CFLAGS="-march=athlon -O3 -fomit-frame-pointer -pipe"
CHOST="i686-pc-linux-gnu"
COMPILER="gcc3"
CONFIG_PROTECT="/etc /var/qmail/control /usr/share/config
/usr/kde/2/share/config /usr/kde/3/share/config /usr/X11R6/lib/X11/xkb
/usr/share/texmf/tex/generic/config/ /usr/share/texmf/tex/platex/config/"
CONFIG_PROTECT_MASK="/etc/gconf /etc/env.d"
CXXFLAGS="-march=athlon -O3 -fomit-frame-pointer -pipe"
DISTDIR="/usr/portage/distfiles"
FEATURES="sandbox ccache autoaddcvs"
GENTOO_MIRRORS="http://gentoo.linux.no/pub/gentoo/
http://trumpetti.atm.tut.fi/gentoo/ http://gentoo.oregonstate.edu
http://www.ibiblio.org/pub/Linux/distributions/gentoo"
MAKEOPTS="-j2"
PKGDIR="/usr/portage/packages"
PORTAGE_TMPDIR="/var/tmp"
PORTDIR="/usr/portage"
PORTDIR_OVERLAY="/usr/portage.local"
SYNC="rsync://rsync.gentoo.org/gentoo-portage"
USE="x86 oss avi cups encode foomaticdb gif jpeg libg++ mad mmx mpeg ncurses nls
pdflib png quicktime truetype xml2 zlib gdbm berkdb slang readline tetex tcltk X
tcpd pam libwww python esd imlib opengl cdr xv fbcon sdl oggvorbis apache2 gtk
gtk2 pda mikmod spell crypt ssl 3dnow sse -doc -xmms -java -perl -gnome -gnome2
-gpm -lame -perl -svga -arts -kde -motif -qt -aalib -alsa -apm -mozilla -xface"

[Comment 1 Alastair Tse (RETIRED) 2003-10-03 08:41:46 UTC]

it is because you don't have ~x86 in your keywords and both libgtkhtml-3.0.9
and libsoup-1.99.26 are marked ~x86 (eg. unstable).

you'll need to either use ~x86 or just use the current stable version and
wait until we mark those as stable.

[Comment 2 Adam Chodorowski 2003-10-04 13:04:16 UTC]

When did this behaviour change in emerge? It makes absolutely no sense. This
means that I cannot *selectively* emerge *some* unstable packages! If I put
~x86 in ACCEPT_KEYWORDS, I will get *all* unstable packages when I do 'emerge
-u world' (even just doing 'ACCEPT_KEYWORDS=2~x86" emerge -u libgtkhtml-3.0.9.ebuild'
would install/upgrade a lot of packages to unstable versions). This is worthless
to me, since I want to only install a couple of unstable packages, and their
(possibly unstable) dependencies.

Not long ago, this worked fine, AFAIR. If I emerged a unstable package, it
would satisfy dependencies fine even though I don't have ACCEPT_KEYWORDS="~x86".


Perhaps this is not a bug in the libsoup ebuild, but rather in emerge, but
in any case it is still a valid (and *VERY* annoying) bug.

[Comment 3 Alastair Tse (RETIRED) 2003-10-04 14:41:33 UTC]

well, i don't know because i've always used ACCEPT_KEYWORDS="~x86" to merge
packages in ~x86. i can't verify this because i don't have a box that is
still on stable x86.

dev-portage guys may know more about it.

[Comment 4 Marius Mauch (RETIRED) 2003-10-04 16:00:39 UTC]

maybe it's related to bug 27025

[Comment 5 Nicholas Jones (RETIRED) 2003-12-24 13:48:01 UTC]

package.keywords in cvs/recent portages is a solution the the first
problem stated. bug 27025 is different.

[Comment 6 Marius Mauch (RETIRED) 2004-02-08 17:55:27 UTC]

supposed to be fixed in 2.0.50 which is stable now. If this bug is not fixed please reopen.