Hum, because of your post, I began to believe it is not only my
problem. And voila! A bug has been filed for it:
http://bugs.gentoo.org/show_bug.cgi?id=99823
It is caused by a change in behaviour in sandbox such that the file
/tmp/sandboxpids.tmp, which genlop uses to determine if a emerge is
g
On 18:59 Wed 03 Aug , Willie Wong wrote:
> On Thu, Aug 04, 2005 at 01:49:15AM +0300, Yuval Scharf wrote:
> > On Thursday 04 August 2005 01:29, A. Khattri wrote:
> > > On Thu, 4 Aug 2005, Yuval Scharf wrote:
> > > > Why when ever I execute
> > > >
> > > > cgext03 ~ # genlop --current
> > > >
> >
On Thu, Aug 04, 2005 at 01:49:15AM +0300, Yuval Scharf wrote:
> On Thursday 04 August 2005 01:29, A. Khattri wrote:
> > On Thu, 4 Aug 2005, Yuval Scharf wrote:
> > > Why when ever I execute
> > >
> > > cgext03 ~ # genlop --current
> > >
> > > I get...
> > >
> > > !!! Error: no working merge found.
On Thursday 04 August 2005 01:29, A. Khattri wrote:
> On Thu, 4 Aug 2005, Yuval Scharf wrote:
> > Why when ever I execute
> >
> > cgext03 ~ # genlop --current
> >
> > I get...
> >
> > !!! Error: no working merge found.
>
> That would be correct, --current reports on an emerge in currently in
> prog
On Thu, 4 Aug 2005, Yuval Scharf wrote:
> Why when ever I execute
>
> cgext03 ~ # genlop --current
>
> I get...
>
> !!! Error: no working merge found.
That would be correct, --current reports on an emerge in currently in
progress, so you see the above message when there's none in progress.
--
Hello,
Why when ever I execute
cgext03 ~ # genlop --current
I get...
!!! Error: no working merge found.
Thanks,
Yuval Scharf
--
gentoo-user@gentoo.org mailing list
6 matches
Mail list logo