While trying to build private ppc64 stages I ran into the following problem: [...] sys-apps/portage selected: 2.1.2.2 protected: 2.1.4.4 omitted: none >>> Unmerging sys-apps/portage-2.1.2.2... emerge --quiet --usepkg --buildpkg --newuse --oneshot --nodeps virtual/baselayout emerge: there are no ebuilds to satisfy "virtual/baselayout". !!! catalyst: run script failed. Traceback (most recent call last): File "modules/generic_stage_target.py", line 1250, in run_local "run script failed.",env=self.env) File "/usr/lib64/catalyst/modules/catalyst_support.py", line 539, in cmd raise CatalystError,myexc CatalystError: <unprintable instance object> None !!! catalyst: Stage build aborting due to error. !!! catalyst: Error encountered during run of target stage1 Catalyst aborting.... lockfile does not exist '/var/tmp/catalyst/tmp/default/stage1-ppc64-64ul-20080330/.catalyst_lock' This began with snapshot from 20080330. Snapshots from the days before build with success. CC'ing vapier as this seems related to this change in sys-apps/baselayout: 31 Mar 2008; Mike Frysinger <vapier@gentoo.org> baselayout-1.11.15-r3.ebuild, baselayout-1.12.11.1.ebuild, baselayout-1.12.12.ebuild: Cleanup unquoted warnings and drop virtual/baselayout PROVIDE.
whoops.. forgot to mention my catalyst version: it's svn checkout 1384.
Created attachment 147992 [details, diff] virtual -> sys-apps mhh.. seems like virtual/baselayout is gone? this patch lets catalyst use sys-apps/baselayout instead of virtual/baselayout
yes ... the virtual existed for forked versions of baselayout which were not really supported ... openrc folds it all back
OK, but OpenRC is not stable anywhere, yet. Neither is baselayout-2*. It *really* would have been nice to have known about this before it was dropped from the tree, considering most of the switch from sys-apps/baselayout to virtual/baselayout is actually quite new in catalyst.
openrc status doesnt really matter. the virtual wasnt really usable for stage building beyond sys-apps/baselayout.
OK, this has been fixed in the latest catalyst. I'll close it once 2.0.6 final is out, since the _pre versions are masked in the tree.
I have a similar error when running an update: === $ sudo emerge --update --deep --newuse world !!! The following installed packages are masked: - dev-util/jam-2.5-r3 (masked by: package.mask) /usr/portage/profiles/package.mask: # Ryan Hill <dirtyepic@gentoo.org> (16 Mar 2008) # Mask for removal on 16 Apr 2008 # upstream unresponsive, replaced by dev-util/ftjam # Bug #173703 For more information, see the MASKED PACKAGES section in the emerge man page or refer to the Gentoo Handbook. emerge: there are no ebuilds to satisfy "virtual/baselayout". (dependency required by "net-misc/bridge-utils-1.0.6-r3" [installed]) === I take it the first error message is irrelevant, I am on arch ~ppc64. Strangely, bridge-utils is installed at the latest version, so I cannot see why emerge can't just ignore this problem and move on...
sorry for the bug spam, I should add that I have bridge-utils in my package.keywords file, so I must be running a ~ppc64 version. also of note is that other architectures are on bridge-utils version 1.2, whereas this one is on 1.0.6-r3
Ehh, this was a catalyst-specific error/bug. Your problem is with a specific package. You'll need to file a bug about that package to the maintainer.
ok reposted #220064 .. seems like a bit bigger underlying change, looking around the bugtracker.
(In reply to comment #6) > OK, this has been fixed in the latest catalyst. I'll close it once 2.0.6 final > is out, since the _pre versions are masked in the tree. > catalyst 2.0.6 final is out and stable. closing this bug.
