On 18:20 Wed 14 Mar     , Pete Morris wrote:
> On Wed, Mar 14, 2007 at 03:13:19PM -0500, Aaron Griffin wrote:
> > On 3/14/07, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
> > > On Wed, 14 Mar 2007 20:19:10 +0100, Jaroslaw Swierczynski
> > > <[EMAIL PROTECTED]> wrote:
> > >
> > > > 2007/3/14, Aaron Griffin <[EMAIL PROTECTED]>:
> > > >>
> > > >> Hmmm, rather silent this time.  I'm assuming that means everything is
> > > >> OK?
> > > >
> > > > It is, however I once again experienced the sudden exit soon after
> > > > answering "yes" to the "Proceed with upgrade?" question with the lock
> > > > file not having been removed. When I reran, it worked ok. I didn't use
> > > > the --debug flag. I guess I will just do alias pacman='pacman --debug'
> > > > and hope to run across this bug again.
> > > >
> > >
> > > I had that bug with the previous RC too! it only happened the very first
> > > time i ran pacman.
> > >
> > > This RC I have had no problems with :) (but not tested testing yet)
> > 
> > This one is irritating, because it's hard to reproduce... if anyone
> > can figure out WHEN this happens, that'd be great.  For me, it's only
> > happened once or twice, but, again, I can't figure out when or why it
> > did...
> 
> This happened to me this morning when  I ran pacman -Syu and then went 
> away for awhile (20 minutes or so).  I had an update, said "yes" to 
> "Proceed with upgrade?", and the bug happened just as described above.  
> I have no idea if the wait had anything to do with the bug, just wanted 
> to let you know.

This happened to me too days ago when I waited much time before answering 
the same question.

-- 
Alessio 'mOLOk' Bolognino
Arch Linux Trusted User
http://www.archlinux.org


_______________________________________________
arch mailing list
[email protected]
http://www.archlinux.org/mailman/listinfo/arch

Reply via email to