1 |
On Thu, 2004-07-01 at 14:54 -0700, Joshua J. Berry wrote: |
2 |
> On Thu, Jul 01, 2004 at 12:44:45PM -0400, KrispyKringle wrote: |
3 |
> > | Same problem here. It hangs at the same line: |
4 |
> > | |
5 |
> > | * genpatches-2.6-7.38-base.tar.bz2 unpacked |
6 |
> > |
7 |
> > I haven't tried it yet myself, but in case CondorDes isn't reading this |
8 |
> > thread (Hi, CondorDes!), |
9 |
> |
10 |
> Hi! :) |
11 |
> |
12 |
> > I'll just report that he claimed the same |
13 |
> > problem, and said that an "rm" in the ebuild was locked, and that if he |
14 |
> > rm'ed whatever the target was manually and killed the process, it went |
15 |
> > along fine from there. |
16 |
> |
17 |
> Yeah ... I mentioned it in response to tseng earlier, although I forget which |
18 |
> file it was. |
19 |
> |
20 |
> FWIW, I've been running 2.6.7 since last night (PST) and it hasn't given me any |
21 |
> trouble. It's just the emerge that's being screwy. |
22 |
> |
23 |
> > So this sounds like a bug, and it sounds like |
24 |
> > someone ought to file a bug report on bugs.gentoo.org and in the |
25 |
> > meantime, try tracking down the errant processess with ps :) |
26 |
|
27 |
Hi, I had the very first person to hit this report a proper bug, and it |
28 |
looks like someone |
29 |
has tracked down the meat of the issue close enough to give us a good |
30 |
clue as to whats |
31 |
going on. |
32 |
|
33 |
http://bugs.gentoo.org/show_bug.cgi?id=55671 |