Your message dated Fri, 20 Jun 2008 09:41:49 +0100
with message-id <[EMAIL PROTECTED]>
and subject line Re: Bug#485089: Reopening.
has caused the Debian Bug report #485089,
regarding apt-cacher: 1.6.3: Checksum database recovery locking broken
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [EMAIL PROTECTED]
immediately.)
--
485089: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=485089
Debian Bug Tracking System
Contact [EMAIL PROTECTED] with problems
--- Begin Message ---
Package: apt-cacher
Version: 1.6.3
Severity: serious
Tags: pending
Locking of checksum database recovery is broken in 1.6.3 causing a hang.
Serverity to prevent Testing migration.
Fix upload is pending
Mark
--- End Message ---
--- Begin Message ---
On Wed, Jun 18, 2008 at 11:16:04PM +0200, Raúl Sánchez Siles wrote:
> reopen 485089
> thanks
>
> Hello:
>
> I'm experiencing this problem still on 1.6.4. When I start 2 aptitude
> sessions: one for a real system and one for a chroot; and they concurrently
> run update and/or upgrade I got this message on dmesg.
> apt-cacher[8117]: segfault at 7f87f70b8e18 ip 7f87f7c37b56 sp 7fff05122448
> error 6 in libdb-4.6.so[7f87f7b9d000+145000]
OK this is a different Issue. I have not sen this mentioned before. The
locking problem that 485089 refers to causes a complete lockup when
trying to recover the database.
I want to close this as it is RC and will prevent 1.6.4 from replacing
1.6.3 in testing.
As to the segfault, can you open a fresh, complete report. When did it
start?
Mark
--- End Message ---
