On Tue, 05 Jan 2010 18:53:13 +0100, Zeerak Waseem wrote: > >> 3) With set files in /usr/portage/sets and running "emerge -u @foo" > >> portage yields that @foo isn't a valid package atom, any idea why > >> this is? > > > > Your portage is too old? In case of an error, you should get an > > "emerge: There are no sets to satisfy 'foo'" message, and a list of > > known sets.
> Ah well, having the sets in the wrong place would give me an error. Yes, but that would be a "set not found" error, not a "WTF is this @" error. > And regarding portage version, weren't sets included in v. 2.x.x? My > portage version is 2.1.7.16, anything above seems to be hardmasked... Sets need portage 2.2, you'll have to unmask it. -- Neil Bothwick Q: How many builders does it take to change a light bulb? A: "If only it was just the light bulb......we'll have to replace the ceiling and..........."
signature.asc
Description: PGP signature
