Bug#909348: gdm3 upgrade from 3.28 to 3.30 tried to remove /usr/lib/udev/rules.d

[Simon McVittie]

On Sat, 22 Sep 2018 at 08:07:40 +0200, Jean-Marc wrote:
> Today, upgrading my system, I got a message when gdm3 upgraded saying (sorry, it's in french):
> Dépaquetage de gdm3 (3.30.0-1) sur (3.28.2-4) ...
> dpkg: avertissement: impossible de supprimer l'ancien répertoire  « /usr/lib/udev/rules.d » : Le dossier n'est pas vide
> dpkg: avertissement: impossible de supprimer l'ancien répertoire  « /usr/lib/udev » : Le dossier n'est pas vide
> 
> Impossible to remove the directory /usr/lib/udev/rules.d because it is not empty.

This message does not indicate a real problem, and you can safely ignore
it, unless it coincides with something breaking.

> I noticed the file /usr/lib/udev/rules.d/61-gdm.rules being present
> in this directory and the package contains the same but not in the same
> location anymore apparently moved to /lib/udev/rules.d.

Yes. It was a bug that it was in /usr/lib/udev/rules.d: it should always
have been in /lib/udev/rules.d.

Is this a "merged /usr" system, where /lib is a symbolic link to /usr/lib?

> Is it possible the gdm3 upgrade tried to remove the directory instead
> of removing only this file ?

Yes, if a package contains a file /foo/bar/baz then it also "owns"
the directories /foo/bar and /foo, and dpkg will try to remove any
directory at the transition between "owned by >= 1 packages" and "owned
by 0 packages".

     smcv