Catalyst 1.1.10.10 can't handle 2007.0's .spec files on amd64 while Catalyst 2.0.4 processes them just fine. Ironically, 1.1.10.10 is marked as stable even thou it's broken while 2.0.4 is marked as testing while it's actually working. Can we mark 2.0.4 as stable or at least remove 1.1.10.10's stable status? # catalyst -f installcd-stage1-minimal.spec Gentoo Catalyst, version 1.1.10.10 Copyright 2003-2005 The Gentoo Foundation Distributed under the GNU General Public License version 2 Using default Catalyst configuration file, /etc/catalyst/catalyst.conf Setting storedir to config file value "/var/tmp/catalyst" Setting portdir to default value "/usr/portage" Setting distdir to config file value "/usr/portage/distfiles" Setting options to config file value "pkgcache kerncache" Setting sharedir to config file value "/usr/lib/catalyst" Package cache support enabled. Kernel cache support enabled. Building natively for amd64 Checking for processes running in chroot and killing them. Running command "/bin/bash /usr/lib/catalyst/targets/support/kill-chroot-pids.sh" Running action sequence: dir_setup Setting up directories... Running command "rm -rf /var/tmp/catalyst/tmp/default/livecd-stage1-amd64-2007.0" Running action sequence: unpack_and_bind Unpacking stage tarball... Running command "/bin/tar xjpf /var/tmp/catalyst/builds/default/stage3-amd64-2007.0.tar.bz2 -C /var/tmp/catalyst/tmp/default/livecd-stage1-amd64-2007.0" Unpacking portage tree snapshot... Running command "/bin/tar xjpf /var/tmp/catalyst/snapshots/portage-2007.0.tar.bz2 -C /var/tmp/catalyst/tmp/default/livecd-stage1-amd64-2007.0/usr" Configuring profile link... Running command "rm -f /var/tmp/catalyst/tmp/default/livecd-stage1-amd64-2007.0/etc/make.profile" Running command "ln -sf ../usr/portage/profiles/default-linux/amd64/2007.0 /var/tmp/catalyst/tmp/default/livecd-stage1-amd64-2007.0/etc/make.profile" Running action sequence: chroot_setup Setting up chroot... Running command "cp /etc/resolv.conf /var/tmp/catalyst/tmp/default/livecd-stage1-amd64-2007.0/etc" Running command "mv /var/tmp/catalyst/tmp/default/livecd-stage1-amd64-2007.0/etc/hosts /var/tmp/catalyst/tmp/default/livecd-stage1-amd64-2007.0/etc/hosts.bck" Running command "cp /etc/hosts /var/tmp/catalyst/tmp/default/livecd-stage1-amd64-2007.0/etc/hosts" Running command "rm -f /var/tmp/catalyst/tmp/default/livecd-stage1-amd64-2007.0/etc/make.conf" Running action sequence: setup_environment Running action sequence: run_local Running command "/bin/bash /usr/lib/catalyst/targets/livecd-stage1/livecd-stage1.sh run 'app-admin/passook' 'app-admin/pwgen' 'app-admin/syslog-ng' 'app-arch/unzip' 'app-editors/vim' 'app-misc/livecd-tools' 'app-misc/screen' 'app-misc/vlock' 'app-portage/mirrorselect' 'dev-lang/python' 'media-gfx/fbgrab' 'net-analyzer/tcptraceroute' 'net-analyzer/traceroute' 'net-dialup/bpalogin' 'net-dialup/mingetty' 'net-dialup/pptpclient' 'net-dialup/rp-pppoe' 'net-fs/nfs-utils' 'net-irc/irssi' 'net-misc/dhcpcd' 'net-misc/iputils' 'net-misc/rdate' 'net-misc/vconfig' 'net-wireless/prism54-firmware' 'net-wireless/wireless-tools' 'net-wireless/wpa_supplicant' 'net-wireless/zd1211-firmware' 'sys-apps/apmd' 'sys-apps/eject' 'sys-apps/ethtool' 'sys-apps/fxload' 'sys-apps/hdparm' 'sys-apps/hwsetup' 'sys-apps/iproute2' 'sys-apps/memtester' 'sys-apps/netplug' 'sys-apps/parted' 'sys-apps/sdparm' 'sys-fs/dosfstools' 'sys-fs/e2fsprogs' 'sys-fs/evms' 'sys-fs/jfsutils' 'sys-fs/lsscsi' 'sys-fs/lvm2' 'sys-fs/mdadm' 'sys-fs/ntfsprogs' 'sys-fs/reiserfsprogs' 'sys-fs/xfsprogs' 'sys-libs/gpm' 'sys-power/acpid' 'www-client/links'" ERROR: Your portage version is too low in your seed stage. Portage version 2.0.51 or greater is required. Traceback (most recent call last): File "modules/livecd_stage1_target.py", line 21, in run_local cmd("/bin/bash "+self.settings["sharedir"]+\ File "/usr/lib/catalyst/modules/catalyst_support.py", line 102, in cmd raise CatalystError,myexc CatalystError: <unprintable instance object> None !!! catalyst: LiveCD stage1 build aborting due to error. Reproducible: Always
We quit using 1.x over a year ago for releases. The reason 1.x is still even available is the documentation for 2.x hasn't been finished and I promised to have the documentation done before 2.x goes stable. I'm not marking 1.x unstable because it doesn't work with our specs. We never said it *would* work with our specs and 1.x works perfectly fine with specs written for 1.x, so there's no need to remove its stable status. It *is* stable in pretty much every sense of the word. Anyway, at some point in the near future, 1.x will go away completely and 2.x will be stabilized.
