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

2018-09-22 Thread Jean-Marc
Sat, 22 Sep 2018 12:37:40 +0100
Simon McVittie  écrivait :

> 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?

Indeed.  My fault.

$ ls -l /
[...]
lrwxrwxrwx   1 root root 7 jan 22  2017 lib -> usr/lib
lrwxrwxrwx   1 root root 9 jan 22  2017 lib32 -> usr/lib32
lrwxrwxrwx   1 root root 9 jan 22  2017 lib64 -> usr/lib64
lrwxrwxrwx   1 root root10 jan 22  2017 libx32 -> usr/libx32

Please, close this bug.

Sorry for this.

The good part of it: I read doc about "merged /usr":
https://wiki.debian.org/UsrMerge
https://salsa.debian.org/md/usrmerge/raw/master/debian/README.Debian
https://www.freedesktop.org/wiki/Software/systemd/TheCaseForTheUsrMerge/

And I got a question: regarding the fact Debain seems adopting "merged /usr" 
(it has been the default since debootstrap 1.0.85 in Oct 2016), why did you say 
your file should always have been in /lib/udev ?

Regards,

Jean-Marc 
https://6jf.be/keys/ED863AD1.txt


pgplInjwc9nUn.pgp
Description: PGP signature


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

2018-09-22 Thread 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



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

2018-09-21 Thread Jean-Marc
Package: gdm3
Version: 3.30.0-1
Severity: normal

Dear Maintainer,

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.

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.

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

Anyway, one of the upgraded package tried it.
Here is the list of package included into my morning upgrade:
Start-Date: 2018-09-22  07:45:26
Commandline: apt full-upgrade
Requested-By: jim (1000)
Upgrade: fonts-lyx:amd64 (2.3.0-3, 2.3.1-2-1), libiptcdata0:amd64 (1.0.4-6+b1, 
1.0.5-2), libproxy1v5:amd64 (0.4.15-1, 0.4.15-2), 
foomatic-db-compressed-ppds:amd64 (20180604-1, 20180917-1), 
libproxy1-plugin-gsettings:amd64 (0.4.15-1, 0.4.15-2), gdm3:amd64 (3.28.2-4, 
3.30.0-1), libgsf-1-114:amd64 (1.14.43-1, 1.14.44-1), gir1.2-gdm-1.0:amd64 
(3.28.2-4, 3.30.0-1), libgdm1:amd64 (3.28.2-4, 3.30.0-1), whiptail:amd64 
(0.52.20-6, 0.52.20-7), libnewt0.52:amd64 (0.52.20-6, 0.52.20-7), 
libproxy-tools:amd64 (0.4.15-1, 0.4.15-2), libgsf-1-common:amd64 (1.14.43-1, 
1.14.44-1), libproxy1-plugin-networkmanager:amd64 (0.4.15-1, 0.4.15-2), 
openprinting-ppds:amd64 (20180604-1, 20180917-1), gstreamer1.0-libav:amd64 
(1.15.0.1+git20180723+db823502-1, 1.15.0.1+git20180723+db823502-2), 
libsgutils2-2:amd64 (1.42-3, 1.44-1), gir1.2-gstreamer-1.0:amd64 (1.14.2-2, 
1.14.3-1), libgsf-bin:amd64 (1.14.43-1, 1.14.44-1), libgstreamer1.0-0:amd64 
(1.14.2-2, 1.14.3-1), wfrench:amd64 (1.2.3-11, 1.2.4-1), 
libdouble-conversion1:amd64 (2.0.1-5, 3.1.0-2)
End-Date: 2018-09-22  07:45:43


I hope this will be helpfull.

Regards,

Jean-Marc

-- System Information:
Debian Release: buster/sid
  APT prefers testing
  APT policy: (500, 'testing'), (100, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 4.18.0-1-amd64 (SMP w/8 CPU cores)
Locale: LANG=fr_BE.UTF-8, LC_CTYPE=fr_BE.UTF-8 (charmap=UTF-8), 
LANGUAGE=fr_BE:fr (charmap=UTF-8)
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages gdm3 depends on:
ii  accountsservice   0.6.45-1
ii  adduser   3.117
ii  dconf-cli 0.30.0-1
ii  dconf-gsettings-backend   0.30.0-1
ii  debconf [debconf-2.0] 1.5.69
ii  gir1.2-gdm-1.03.30.0-1
ii  gnome-session [x-session-manager] 3.28.1-1
ii  gnome-session-bin 3.28.1-1
ii  gnome-settings-daemon 3.30.0-1
ii  gnome-shell   3.30.0-1
ii  gnome-terminal [x-terminal-emulator]  3.30.0-1
ii  gsettings-desktop-schemas 3.28.0-1
ii  libaccountsservice0   0.6.45-1
ii  libaudit1 1:2.8.4-2
ii  libc6 2.27-6
ii  libcanberra-gtk3-00.30-6
ii  libcanberra0  0.30-6
ii  libgdk-pixbuf2.0-02.38.0+dfsg-6
ii  libgdm1   3.30.0-1
ii  libglib2.0-0  2.58.0-4
ii  libglib2.0-bin2.58.0-4
ii  libgtk-3-03.24.0-3
ii  libkeyutils1  1.5.9-9.3
ii  libpam-modules1.1.8-3.8
ii  libpam-runtime1.1.8-3.8
ii  libpam-systemd239-9
ii  libpam0g  1.1.8-3.8
ii  librsvg2-common   2.40.20-3
ii  libselinux1   2.8-1+b1
ii  libsystemd0   239-9
ii  libwrap0  7.6.q-27
ii  libx11-6  2:1.6.6-1
ii  libxau6   1:1.0.8-1+b2
ii  libxcb1   1.13-3
ii  libxdmcp6 1:1.1.2-3
ii  lsb-base  9.20170808
ii  mutter [x-window-manager] 3.30.0-1
ii  policykit-1   0.105-21
ii  terminator [x-terminal-emulator]  1.91-1
ii  ucf   3.0038
ii  x11-common1:7.7+19
ii  x11-xserver-utils 7.7+8
ii  xfce4-session [x-session-manager] 4.12.1-6
ii  xfwm4 [x-window-manager]  4.12.5-1
ii  xterm [x-terminal-emulator]   335-1

Versions of packages gdm3 recommends:
ii  at-spi2-core2.30.0-2
ii  desktop-base9.0.7
ii