| 1 |
On Mon, 2009-04-20 at 20:54 -0700, Steven Noonan wrote: |
| 2 |
> Whoops, correcting mduft's email address. |
| 3 |
> |
| 4 |
> On Mon, Apr 20, 2009 at 8:52 PM, Steven Noonan <steven@××××××××××.net> wrote: |
| 5 |
> > Hi folks, |
| 6 |
> > |
| 7 |
> > I'm running a recent build of Windows 7 with SUA 6.1 installed. I got |
| 8 |
> > "GeNToo" installed with only minor changes to the scripts so they use |
| 9 |
> > the SUA 6.0 tarball. |
| 10 |
> > |
| 11 |
> > Unfortunately, I can't do any emerges: |
| 12 |
> > |
| 13 |
> > |
| 14 |
> > |
| 15 |
[snip] |
| 16 |
> > |
| 17 |
> > I also tried 'emerge --nodeps -1 portage' but got the same failure. |
| 18 |
> > It's not just sys-apps/portage that gets this error, either, it's |
| 19 |
> > every package. |
| 20 |
> > |
| 21 |
> > Any ideas? |
| 22 |
|
| 23 |
just to get the list informed: solved this on IRC: |
| 24 |
|
| 25 |
emerge -av1 --nodeps "=sys-apps/portage-2.2.00.13286-r1" |
| 26 |
|
| 27 |
is required to get portage back up and working... current interix CD |
| 28 |
image portage refuses to do anythin wrt dependency resolution, or even |
| 29 |
parsing of EAPI=prefix ebuild (so he doesn't mask them but bails out - |
| 30 |
argh..) |
| 31 |
|
| 32 |
Cheers, Markus |
| 33 |
|
| 34 |
> > |
| 35 |
> > - Steven |
| 36 |
> > |
Archives