portage-2.1 is under heavy development and probably will continue to be for a while so it would be wise for us to get a new 2.0.XX stable out there till such time as 2.1 is ready for prime time. Bugs have not been getting fixed in the stable tree and devs are/were assuming it's safe to use some features that only existed in 2.1 on our gentoo-x86 tree while 2.0 is stable portage ( such as bug #125554 ) splitdebug was added ( bug #112907 ) RPATH problems are auto corrected solving ( bug #81745 ) portage-2.0.54-r1 was pushed to the tree to address these problems with a few backports from the 2.1 series. The following files changed from 2.0.54 to 2.0.54-r1 bin/ebuild.sh bin/emerge bin/fowners bin/fperms bin/prepallstrip bin/prepstrip man/ebuild.5 man/portage.5 At this time please start testing portage-2.0.54-r1 as a target for the next stable portage release.
I have not hit any issues on ppc64 yet.
Well, portage-2.0.54-r1 depends on >=app-misc/pax-utils-0.1.11 0.1.11 isn't in the tree anymore (presumably because of bug 28247 (pax-utils-0.1.11 hangs in prepallstrip)), and -r1 is ~x86 and has only been in the tree for about 10 days. (FWIW, portage-2.0.54-r1 has stood up to a limited amount of testing here)
yes. hppa ia64 m68k ppc ppc64 s390 sh sparc will need to mark pax-utils-0.1.11-r1 stable along the way.
sparc looks good so far.
portage-2.0.54-r1 [-build -doc (-selinux)] seems to work fine on x86. for testing i've installed/uninstalled/(up/down)graded a few packages, verified with 'emerge -uavDN world' that my system is up to date, with 'emerge depclean' that there are no unnecessary packages on my system, and even tried 'emerge -s' again for a long time (since i use eix normally). However, look closly at this one (!! Portage 2203-svn !!): Portage 2203-svn (default-linux/x86/2006.0, gcc-3.4.5, glibc-2.3.5-r3, 2.6.16-gentoo-r3 i686) ================================================================= System uname: 2.6.16-gentoo-r3 i686 AMD Athlon(tm) XP 2400+ Gentoo Base System version 1.6.14 dev-lang/python: 2.3.5-r2, 2.4.2 sys-apps/sandbox: 1.2.12 sys-devel/autoconf: 2.13, 2.59-r7 sys-devel/automake: 1.4_p6, 1.5, 1.6.3, 1.7.9-r1, 1.8.5-r3, 1.9.6-r1 sys-devel/binutils: 2.16.1 sys-devel/libtool: 1.5.22 virtual/os-headers: 2.6.11-r2 ACCEPT_KEYWORDS="x86" AUTOCLEAN="yes" CBUILD="i686-pc-linux-gnu" CFLAGS="-O2 -march=athlon-xp -pipe" CHOST="i686-pc-linux-gnu" CONFIG_PROTECT="/etc /usr/kde/2/share/config /usr/kde/3.4/env /usr/kde/3.4/share/config /usr/kde/3.4/shutdown /usr/kde/3/share/config /usr/lib/X11/xkb /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/eselect/compiler /etc/gconf /etc/terminfo /etc/env.d" CXXFLAGS="-O2 -march=athlon-xp -pipe" DISTDIR="/usr/portage/distfiles" FEATURES="autoconfig collision-protect distlocks sandbox sfperms strict" GENTOO_MIRRORS="http://gentoo.inode.at/ " LANG="en_US.utf8" LC_ALL="en_US.utf8" LINGUAS="en de" MAKEOPTS="-j2" PKGDIR="/usr/portage/packages" PORTAGE_TMPDIR="/var/tmp" PORTDIR="/usr/portage" PORTDIR_OVERLAY="/usr/local/portage" SYNC="rsync://192.168.0.1/gentoo-portage" USE="x86 3dnow 3dnowext X a52 aalib alsa apm audiofile avi berkdb bitmap-fonts bonobo bzip2 bzlib cairo cdr cli crypt css cups curl dbus divx4linux dri dts dv dvd dvdr dvdread emboss encode evo exif expat fam fame ffmpeg firefox flac foomaticdb fortran gd gdbm gif glut gmp gnome gphoto2 gpm gstreamer gtk gtk2 gtkhtml guile hal idn imagemagick imlib ipv6 isdnlog java jpeg junit lcms libg++ libwww mad mikmod mmx mmxext mng motif mp3 mpeg nautilus ncurses nls nptl nsplugin nvidia ogg oggvorbis openal opengl pam pcre pdflib perl plotutils png pppd python quicktime readline real reflection ruby sdl session slang speex spell spl sqlite sse ssl subtitles svga tcltk tcpd tetex theora tiff truetype truetype-fonts type1-fonts udev unicode usb vcd video_cards_nvidia vorbis win32codecs wma xine xml xml2 xmms xorg xv xvid zlib linguas_en linguas_de userland_GNU kernel_linux elibc_glibc" Unset: ASFLAGS, CTARGET, INSTALL_MASK, LDFLAGS
Stable on mips.
sparc stable.
x86 done
Just a headsup, 2.0.54-r1 has a regression in the form of bug #131207 which makes emerge -e world loop forever, which breaks stage3 building in catalyst.
(In reply to comment #9) > Just a headsup, 2.0.54-r1 has a regression in the form of bug #131207 which > makes emerge -e world loop forever, which breaks stage3 building in catalyst. It should not be a regression vs how 2.0.x behaved. This was fixed in a later portage-2.1 and we will probably include the patch in the next 2.0.54-r2 along with the version update.
ppc has already marked the required pax-utils version stable. Was this actually a stable marking request for portage or just a test request? I'll mark it ppc stable if we should, since it seems fine here and other arches have already marked it stable.
Marked ppc stable after speaking in #gentoo-portage.
(In reply to comment #10) > (In reply to comment #9) > > Just a headsup, 2.0.54-r1 has a regression in the form of bug #131207 which > > makes emerge -e world loop forever, which breaks stage3 building in catalyst. > > It should not be a regression vs how 2.0.x behaved. > This was fixed in a later portage-2.1 and we will probably include > the patch in the next 2.0.54-r2 along with the version update. > So 2.0.54-r2 isn't stable because it's required that a package have no open bugs for at least 30 days before it's made stable. On the other hand, 2.0.54-r1 isn't really stable either as it is still affected by that bug.
(In reply to comment #13) > (In reply to comment #10) > > (In reply to comment #9) > > > Just a headsup, 2.0.54-r1 has a regression in the form of bug #131207 which > > > makes emerge -e world loop forever, which breaks stage3 building in catalyst. > > > > It should not be a regression vs how 2.0.x behaved. > > This was fixed in a later portage-2.1 and we will probably include > > the patch in the next 2.0.54-r2 along with the version update. > > > > So 2.0.54-r2 isn't stable because it's required that a package have no open > bugs for at least 30 days before it's made stable. > > On the other hand, 2.0.54-r1 isn't really stable either as it is still affected > by that bug. No idea what point your trying to make here. To say 2.0.54-r1 is not stable is the same as saying 2.0.54 is not stable which is the same as saying any 2.0 branch is not stable. What are you saying? Or rather why?
2.0.54-r2 hppa & sparc stable.
Other arches are free/encouraged to mark -r2 stable. I do expect an -r3 in a week or a few however.
stable on ppc64
-r2 looks good on x86 here (syncing, emerging, unmerging, depclean all work fine, and the dependency bug is fixed).
portage didn't get squished crossing the road to x86 stableland ^.^;;
ppc was not on the CC:
Marked -r2 ppc stable, feel free to add us again when -r3 is added.
amd64 is more than happy to stablize this. Stable on amd64.
Alpha stable.
ia64 stable.
Bug no longer valid. 2.1 is the current stable.
