El lun, 01-06-2009 a las 10:31 -0700, Vagrant Cascadian escribió: > tags 530586 -unreproduceable > retitle 530586 debian-edu-artwork: upgrade fails to run update-gconf-defaults > reassign 530586 gconf2 2.26.0-1 > thanks > > On Mon, Jun 01, 2009 at 01:07:08PM +0200, Arthur de Jong wrote: > > On Mon, 2009-06-01 at 12:54 +0200, Holger Levsen wrote: > > > did you really run into this bug with 0.0.30-2? Because, the gconf > > > keys were removed in that upload?! > > only the keys referencing iceweasel were removed from debian-edu-artwork. > > though this appears to be a bug in gconf2... > > > This is the history from the terminal: > > > > # apt-get upgrade > > [...] > > (Reading database ... 280572 files and directories currently installed.) > > Preparing to replace debian-edu-artwork 0.0.28 (using > > .../debian-edu-artwork_0.0.30-2_all.deb) ... > > Unpacking replacement debian-edu-artwork ... > > /tmp/gconf-cQtqkW/temp.entries:4: parser error : error parsing attribute > > name > > <key><list</key> > > ^ > > gconf2 needs to be installed for update-gconf-defaults from postinst/postrm to > get triggered. >
Not, debhelper takes care of this: if it is not installed it doesn't do
that in the postinst:
# Automatically added by dh_gconf
if [ "$1" = "configure" ] && which update-gconf-defaults >/dev/null
2>&1; then
update-gconf-defaults
fi
So, if gconf2 is not installed, the bug should not raise.
The problem must be in some other place.
> i can reproduce this behavior in a clean sid chroot by first installing
> gconf2,
> installing debian-edu-artwork 0.0.28, and then upgrading to 0.0.30-2.
>
> the same process in a clean lenny chroot actually works fine, so i'm thinking
> this is a bug in recent versions of gconf2.
>
> live well,
> vagrant
>
>
>
signature.asc
Description: Esta parte del mensaje está firmada digitalmente
