Am 24.04.2013 23:49, schrieb Michael Biebl: > Registering gconf schemas has been triggerized, that's why the > libgnome2-common package in wheezy no longer has any maintainer scripts > which call gconf-schemas. > > What's really weird though: In both squeeze and wheezy, libgnome2-common > (actually any package shipping gconf schemas) has a Depends: gconf2 > (which provides the gconf-schemas tool). > > So during the upgrade gconf2 is in an uninstalled state while packages > still depend on it. Isn't this a bug in apt? I know that preinst > dependencies require Pre-Depends and calling tools in postrm require > explicit checks for the existence of the tools. I wasn't aware that > prerm was problematic too?
According to jwilk, this is a issue in the python package: <jwilk> mbiebl: I'm pretty sure it's not /usr/sbin/gconf-schemas that is missing, but /usr/bin/python (which is is -schema's shebang). <jwilk> Or more precisely, /usr/bin/python is there, but it's dangling. <jwilk> I looked at the build log and yeah, this is what happend: python is upgraded from 2.6 to 2.7, making /usr/bin/python dangling, because python2.7 is not unpacked yet. <jwilk> Then libgnome2-common is unpacked, which doesn't work without working /usr/bin/python. <jwilk> s/unpacked/prerm'ed/ in the last sentence. -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth?
signature.asc
Description: OpenPGP digital signature
