← Back to team overview

desktop-packages team mailing list archive

[Bug 884979] Re: purging a package for different architecture may delete files needed for the actual architecture

 

This is a bug of libglib2.0-0 because its postrm purge removes it
unconditionnaly even if the package is still installed on another
architecture.

Cf the extract below of /var/lib/dpkg/info/libglib2.0-0:i386.postrm
if [ "$1" = purge ] && [ -d /usr/share/glib-2.0/schemas ]; then
    # Purge the compiled schemas
    rm -f /usr/share/glib-2.0/schemas/gschemas.compiled
    rmdir -p --ignore-fail-on-non-empty /usr/share/glib-2.0/schemas
fi

** Package changed: dpkg (Ubuntu) => glib2.0 (Ubuntu)

** Tags added: multiarch

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to glib2.0 in Ubuntu.
https://bugs.launchpad.net/bugs/884979

Title:
  purging a package for different architecture may delete files needed
  for the actual architecture

Status in “glib2.0” package in Ubuntu:
  New

Bug description:
  After installing adobe-flashplugin on my 64-bit system (11.10) I removed all the packages for i386 architecture. Then I purged them. After restarting the machine, the default Ubuntu session stopped working. I found that when I purged package libglib2.0-0:i386, dpkg deleted the file /usr/share/glib-2.0/schemas/gschemas.compiled. However it also belongs to  libglib2.0-0. I supposed that the library missed this file, because after copying it back, my box started to work again.
  I do not know, if it is a serious problem, but dpkg should handle these cases, when there are packages installed for different architectures. May hard linking the same files prevent  unwanted deletion?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/884979/+subscriptions


Follow ups