Bug#568908: FWD: Re: btrfs issues
joeyh at debian.org
Tue Apr 6 19:20:17 UTC 2010
----- Forwarded message from cwillu <cwillu at cwillu.com> -----
Date: Tue, 6 Apr 2010 12:42:15 -0600
From: cwillu <cwillu at cwillu.com>
To: Joey Hess <joey at kitenet.net>
Subject: Re: btrfs issues
On Tue, Apr 6, 2010 at 12:38 PM, cwillu <cwillu at cwillu.com> wrote:
> On Tue, Apr 6, 2010 at 12:33 PM, Joey Hess <joey at kitenet.net> wrote:
>> cwillu wrote:
>>> New information on http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=575891
>>> Turns out to have been an unsafe assumption on dpkg's part with
>>> apparently astronomic odds of being triggered on most filesystems.
>>> Putting /var/lib/dpkg on an ext3 mount (I used a bind mount from my
>>> /boot) works around it until the problem can be fixed in dpkg.
>> Cwillu, thanks for following up.
>> That does seem to explain #569058, closing that bug.
>> At the moment, my other two problems, #567135 and #568908, do not
>> seem likely to be caused by the dpkg bug.
> #567135 is definitely caused by triggers and postinst scripts going
> missing from /var/lib/dpkg/info, that's the behaviour that got me
> looking at dpkg in the first place. I wouldn't be surprised if #568908
> also had similar roots.
And having looked into that, gconf schema corruption is another issue
I've run into which can be traced back to a failure to run the
postinst script which registers it;
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=568908#30 refers to
such corruption as a likely cause.
----- End forwarded message -----
see shy jo
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Size: 828 bytes
Desc: Digital signature
More information about the pkg-gnome-maintainers