| 1 |
Hum, because of your post, I began to believe it is not only my |
| 2 |
problem. And voila! A bug has been filed for it: |
| 3 |
|
| 4 |
http://bugs.gentoo.org/show_bug.cgi?id=99823 |
| 5 |
|
| 6 |
It is caused by a change in behaviour in sandbox such that the file |
| 7 |
/tmp/sandboxpids.tmp, which genlop uses to determine if a emerge is |
| 8 |
going on, is no longer used, resulting in genlop never catching a |
| 9 |
emerge. |
| 10 |
|
| 11 |
It is allegedly fixed in 0.30.4 |
| 12 |
|
| 13 |
There is a patch in the bugzilla thread if you really want the fix |
| 14 |
now. |
| 15 |
|
| 16 |
W |
| 17 |
|
| 18 |
On Thu, Aug 04, 2005 at 01:49:15AM +0300, Yuval Scharf wrote: |
| 19 |
> On Thursday 04 August 2005 01:29, A. Khattri wrote: |
| 20 |
> > On Thu, 4 Aug 2005, Yuval Scharf wrote: |
| 21 |
> > > Why when ever I execute |
| 22 |
> > > |
| 23 |
> > > cgext03 ~ # genlop --current |
| 24 |
> > > |
| 25 |
> > > I get... |
| 26 |
> > > |
| 27 |
> > > !!! Error: no working merge found. |
| 28 |
> > |
| 29 |
> > That would be correct, --current reports on an emerge in currently in |
| 30 |
> > progress, so you see the above message when there's none in progress. |
| 31 |
> > |
| 32 |
> > |
| 33 |
> > -- |
| 34 |
> |
| 35 |
> Hello, |
| 36 |
> |
| 37 |
> I meant "whenever there is a merge going on...". |
| 38 |
> |
| 39 |
> Yuval Scharf |
| 40 |
> -- |
| 41 |
> gentoo-user@g.o mailing list |
| 42 |
|
| 43 |
-- |
| 44 |
Gualtieri's Law of inertia: |
| 45 |
Where there's a will, there's a won't. |
| 46 |
Sortir en Pantoufles: up 3 days, 6:25 |
| 47 |
-- |
| 48 |
gentoo-user@g.o mailing list |
Archives