For some weird reason, the rpm-4.2.1 ebuild is keyworded with -x86: KEYWORDS="alpha amd64 arm hppa ia64 ppc s390 sparc -x86" The ebuild is not in package.mask though and there is no explanation in the ChangeLog: 23 Oct 2004; Stefan Jones <cretin@gentoo.org> rpm-4.2.ebuild: Use the rpm source code from rpm.org not some random RedHat snapshot. Mark stable on x86 and mask 4.2.1 on x86 for proper testing! 11 Apr 2004; Stefan Jones <cretin@gentoo.org> rpm-4.2.1.ebuild: Mark as stable for all archs 07 Apr 2004; Aron Griffis <agriffis@gentoo.org> rpm-4.0.4-r5.ebuild, rpm-4.2_pre069.ebuild: Versions of rpm prior to 4.2.1 need to conflict with beecrypt, fixes bug 45577 "Proper testing" would be ~x86 (or package.mask) in my eyes, but not -x86. Especially as <rpm4.2.1 conflicts with beecrypt (and the other way round) as noted in the ChangeLog. Reproducible: Always Steps to Reproduce: Portage 2.0.51-r3 (default-linux/x86/2004.3, gcc-3.3.4, glibc-2.3.4.20040808-r1, 2.6.7-gentoo-r11 i686) ================================================================= System uname: 2.6.7-gentoo-r11 i686 mobile AMD Athlon(tm) XP 1900+ Gentoo Base System version 1.4.16 distcc 2.16 i686-pc-linux-gnu (protocols 1 and 2) (default port 3632) [disabled] ccache version 2.3 [enabled] Autoconf: sys-devel/autoconf-2.59-r5 Automake: sys-devel/automake-1.8.5-r1 Binutils: sys-devel/binutils-2.15.90.0.1.1-r3 Headers: sys-kernel/linux26-headers-2.6.8.1-r1 Libtools: sys-devel/libtool-1.5.2-r7 ACCEPT_KEYWORDS="x86" AUTOCLEAN="yes" CFLAGS="-pipe -mcpu=athlon-xp -O2 -fstack-protector" CHOST="i686-pc-linux-gnu" COMPILER="" CONFIG_PROTECT="/etc /usr/X11R6/lib/X11/xkb /usr/kde/2/share/config /usr/kde/3/share/config /usr/kde/cvs/share/config /usr/share/config /usr/share/texmf/dvipdfm/config/ /usr/share/texmf/dvips/config/ /usr/share/texmf/tex/generic/config/ /usr/share/texmf/tex/platex/config/ /usr/share/texmf/xdvi/ /var/qmail/control" CONFIG_PROTECT_MASK="/etc/gconf /etc/terminfo /etc/env.d" CXXFLAGS="-pipe -mcpu=athlon-xp -O2 -fstack-protector" DISTDIR="/var/cache/portage/sources" FEATURES="autoaddcvs autoconfig ccache distlocks sandbox sfperms" GENTOO_MIRRORS="http://mirrors.sec.informatik.tu-darmstadt.de/gentoo http://gentoo.inode.at/" MAKEOPTS="-j2" PKGDIR="/var/cache/portage/packages" PORTAGE_TMPDIR="/var/tmp" PORTDIR="/usr/portage" PORTDIR_OVERLAY="/usr/local/portage/kde-cvs /usr/local/portage/misc /home/mss/.portage/mortage" SYNC="rsync://10.10.10.10/gentoo-portage" USE="3dnow 3dnowex X aalib aavm acl acpi acpi4linux alsa apm arts avi berkdb bitmap-fonts cdr crypt cscope cups curl directfb dnd dvd encodeethereal f77 faad fam fbcon flac foomaticdb freetype gcj gdbm geoip gif gphoto2 gpm gps gtk gtk2 guile imagemagick imap imlib ipv6 jabber java jikes jpeg kde ldap libg++ libwww lzw-tiff mad maildir mmx mng moznocompose moznoirc mpeg nas ncurses odbc oggvorbis opengl pam pcap pcmcia pdflib perl png pnp python qt quicktime readline samba sasl scanner sdl slang slp socks5 speex spell sse ssl stroke svga tcltk tcpd tetex tiff transcode truetype trusted type1 uml usagi usb wmf x86 xchattext xinerama xml xml2 xmms xv zlib"
Ah, I should explain myself. Unfortunatly some time ago I bumped rpm to a unstable redhat homebrew version from rawhide to fix some issues about it not working on newer systems. Unfortanatly that rpm was buggy, but this was only found out long after it was marked as stable. I did not have time or want to fix up the source code so I decided the downgrade rpm the the last official version from rpm.org. I did this by masking 4.2.1 (the bugy version from rawhide) -x86 and adding 4.2 from rpm.org as x86. And thus it stands as it is. I want 4.2.1 masked (prefably on all arch, but I only play with x86 as I do not have any other machines)
Wow. Do I understand rpm.org right in that there was no official release of RPM (aka the LSB package management tool) since May 2003? Any chance the issues with beecrypt can be fixed?
The info on the rpm website is all I know of. What issue about beecrypt are you talking about? (what happened in later versions of rpm is that they split beecrypt from rpm into a seperate package)
There was some package (I can't even remember which) which depended on beecrypt which conflicted with rpm. I grepped the tree and it seems like the dependency on beecrypt is gone so everything is fine.
