On Sun, Nov 23, 2008 at 2:24 PM, Duncan <[EMAIL PROTECTED]> wrote: > "Mark Knecht" <[EMAIL PROTECTED]> posted > [EMAIL PROTECTED], excerpted > below, on Sun, 23 Nov 2008 13:31:53 -0800: > >> * The ebuild phase 'unpack' has exited unexpectedly. This >> * type of behavior is known to be triggered by things such >> * as failed variable assignments (bug #190128) or bad >> * substitution errors (bug #200313). > > I don't believe it was this specific ebuild, but I recognize the error > "This type of behavior..." from some bug reported somewhere that I read > recently. Unfortunately I don't remember what it was from, but it's > likely related, so there has indeed been some similar problems recently. > > I know that doesn't help much... maybe after work I'll be able to trace > it down if nobody else has a better reply by then. > > -- > Duncan - List replies preferred. No HTML msgs. > "Every nonfree program has a lord, a master -- > and if you use the program, he is your master." Richard Stallman
Thanks Duncan. Don't put too much effort into it. I poked around in Bugzilla, couldn't find anything real specific so I filed a bug report. Probably it will get worked out over the next couple of days anyway. The root cause of this is I wanted to emerge the newest version of Ardour from the pro-audio overlay and ran into a new message about it being masked by something called EAPI 2 which according to the message requires a 'newer' version of portage. (No revision given.) That's all this was about, and there's absoutely no rush to fix it as I'm not likely to really use Ardour. Just wanted to take a look at what sort of headway they are making with their feature set so it's really nothing but pure curiosity. Cheers, Mark
