1. Emerges on AMD64. 2. No collisions. 3. Test phase ok. 4. Multilib-strict ok. 5. Works (rdeps: app-crypt/dirmngr app-crypt/gnupg). Portage 2.1.2.7 (default-linux/amd64/2007.0/desktop, gcc-4.1.2, glibc-2.5-r3, 2.6.20-gentoo-r8 x86_64) ================================================================= System uname: 2.6.20-gentoo-r8 x86_64 Intel(R) Pentium(R) D CPU 3.00GHz Gentoo Base System release 1.12.9 Timestamp of tree: Wed, 27 Jun 2007 04:20:01 +0000 ccache version 2.4 [enabled] dev-java/java-config: 1.3.7, 2.0.33-r1 dev-lang/python: 2.4.4-r4 dev-python/pycrypto: 2.0.1-r5 dev-util/ccache: 2.4-r7 sys-apps/sandbox: 1.2.17 sys-devel/autoconf: 2.13, 2.61 sys-devel/automake: 1.4_p6, 1.5, 1.6.3, 1.7.9-r1, 1.8.5-r3, 1.9.6-r2, 1.10 sys-devel/binutils: 2.17 sys-devel/gcc-config: 1.3.16 sys-devel/libtool: 1.5.23b virtual/os-headers: 2.6.17-r2 ACCEPT_KEYWORDS="amd64" AUTOCLEAN="yes" CBUILD="x86_64-pc-linux-gnu" CFLAGS="-O2 -march=nocona -pipe" CHOST="x86_64-pc-linux-gnu" CONFIG_PROTECT="/etc /usr/kde/3.5/env /usr/kde/3.5/share/config /usr/kde/3.5/shutdown /usr/share/X11/xkb /usr/share/config" CONFIG_PROTECT_MASK="/etc/env.d /etc/env.d/java/ /etc/gconf /etc/init.d /etc/php/apache2-php5/ext-active/ /etc/php/cgi-php5/ext-active/ /etc/php/cli-php5/ext-active/ /etc/revdep-rebuild /etc/terminfo" CXXFLAGS="-O2 -march=nocona -pipe" DISTDIR="/usr/portage/distfiles" EMERGE_DEFAULT_OPTS="-akv" FEATURES="buildpkg ccache collision-protect distlocks fixpackages metadata-transfer multilib-strict parallel-fetch sandbox sfperms strict test userfetch userpriv usersandbox" GENTOO_MIRRORS="ftp://mirrors1.netvisao.pt/gentoo http://darkstar.ist.utl.pt/pub/gentoo http://distfiles.gentoo.org http://www.ibiblio.org/pub/Linux/distributions/gentoo" MAKEOPTS="-j3" PKGDIR="/usr/portage/packages" PORTAGE_RSYNC_OPTS="--recursive --links --safe-links --perms --times --compress --force --whole-file --delete --delete-after --stats --timeout=180 --exclude=/distfiles --exclude=/local --exclude=/packages --filter=H_**/files/digest-*" PORTAGE_TMPDIR="/var/tmp" PORTDIR="/usr/portage" SYNC="rsync://rsync.europe.gentoo.org/gentoo-portage" USE="X acl acpi alsa amd64 apache2 arts bash-completion bitmap-fonts cairo cdr cli cracklib crypt dbus dri dts dvd dvdr dvdread eds emboss encode evo fam firefox flac fortran gif gpm hal iconv ipv6 isdnlog jpeg kde kdeenablefinal kdehiddenvisibility libg++ mad midi mikmod mmx mp3 mpeg mudflap musepack musicbrainz mysql ncurses nptl nptlonly offensive ogg opengl openmp pam pcre pdf perl png postgres pppd python qt3 qt3support qt4 quicktime readline reflection sdl session spell spl sse sse2 ssl svg tcpd test tiff truetype truetype-fonts type1-fonts unicode vorbis xcomposite xml xorg xscreensaver xv zlib" ALSA_CARDS="ali5451 als4000 atiixp atiixp-modem bt87x ca0106 cmipci emu10k1x ens1370 ens1371 es1938 es1968 fm801 hda-intel intel8x0 intel8x0m maestro3 trident usb-audio via82xx via82xx-modem ymfpci" ALSA_PCM_PLUGINS="adpcm alaw asym copy dmix dshare dsnoop empty extplug file hooks iec958 ioplug ladspa lfloat linear meter mulaw multi null plug rate route share shm softvol" ELIBC="glibc" INPUT_DEVICES="keyboard mouse" KERNEL="linux" LCD_DEVICES="bayrad cfontz cfontz633 glk hd44780 lb216 lcdm001 mtxorb ncurses text" USERLAND="GNU" VIDEO_CARDS="i810" Unset: CTARGET, INSTALL_MASK, LANG, LC_ALL, LDFLAGS, LINGUAS, PORTAGE_COMPRESS, PORTAGE_COMPRESS_FLAGS, PORTAGE_RSYNC_EXTRA_OPTS, PORTDIR_OVERLAY
amd64 stable, thanks Tiago CCing other possibly interested archs
@Tiago, please: 1) The keyword is wrong (should be STABLEREQ, not STABLE). 2) Calling a package stable in Gentoo lingo means it has stable arch keywords. In a bug requesting stabilisation, the description should probably be a future perfect, as in "dev-libs/libksba-1.0.0 should be stabilised", not "dev-libs/libksba-1.0.0 is stable" (because it isn't now, and should be according to you). @Cristoph: 1) Package maintainers, in this case crypto, should normally make the call whether a package/version is OK to be stabilised. The bug should therefore have been re-assigned to crypto, and someone from that team should give the OK on the bug, or you should have added some evidence of an informal OK given through another medium, say IRC or private mail. 2) You left the bug assigned to amd64.
Well... As far as crypto is concerned, there is no point in making individual gnupg components stable as we all waiting for gnupg-2 to be stable. The affected component is the current stable gnupg-1.9.21, which is not maintained by upstream, so if we have problem we have to revert. Tiago: Any special reason why you requested this?
Jeroen: Thank you. I just followed the instructions from the AMD64 AT procedures page - http://www.gentoo.org/proj/en/base/amd64/at/procedures.xml Alon: No. But since it was in the imlate report, and it was keyworded ~amd64 since October 2006, and no bugs open in the last 30 days I decided to open a bug.
Well... I don't understand the keywording of this package... It seems to have a life of its own... mips, sparc, x86 stabilized this without any request, but at least they put some change log entries, ia64 arm sh sparc s390 had done so without any reference.
> 1) Package maintainers, in this case crypto, should normally make the call > whether a package/version is OK to be stabilised. This is afaik not the case if it's already stabilized on other archs (arm, s390, x86, sparc, mips, ia64 and sh in this case). > 2) You left the bug assigned to amd64. I know, I forgot to reassign it ;)
Sorry, I did not reload between cvs commit and editing the bug-report. So, ppc is now stable as well.
