Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.debian.bugs.dist > #1111464 > unrolled thread
| Started by | Diederik de Haas <didi.debian@cknow.org> |
|---|---|
| First post | 2022-07-30 15:20 +0200 |
| Last post | 2022-07-30 22:20 +0200 |
| Articles | 3 — 2 participants |
Back to article view | Back to linux.debian.bugs.dist
Bug#1016372: uuid-runtime: post-install script gives warnings which seem incorrect Diederik de Haas <didi.debian@cknow.org> - 2022-07-30 15:20 +0200
Bug#1016372: uuid-runtime: post-install script gives warnings which seem incorrect Chris Hofstaedtler <zeha@debian.org> - 2022-07-30 17:00 +0200
Bug#1016372: uuid-runtime: post-install script gives warnings which seem incorrect Diederik de Haas <didi.debian@cknow.org> - 2022-07-30 22:20 +0200
| From | Diederik de Haas <didi.debian@cknow.org> |
|---|---|
| Date | 2022-07-30 15:20 +0200 |
| Subject | Bug#1016372: uuid-runtime: post-install script gives warnings which seem incorrect |
| Message-ID | <EOUxP-ePFc-1@gated-at.bofh.it> |
Package: uuid-runtime Version: 2.38-6 Severity: minor -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 I just installed uuid-runtime on a Rock64 device (arm64) and got several warnings/info messages which seem incorrect to me. root@cs21:~# aptitude install uuid-runtime The following NEW packages will be installed: uuid-runtime 0 packages upgraded, 1 newly installed, 0 to remove and 0 not upgraded. Need to get 108 kB of archives. After unpacking 334 kB will be used. Get: 1 http://deb.debian.org/debian bookworm/main arm64 uuid-runtime arm64 2.38-6 [108 kB] Fetched 108 kB in 0s (526 kB/s) Selecting previously unselected package uuid-runtime. (Reading database ... 47358 files and directories currently installed.) Preparing to unpack .../uuid-runtime_2.38-6_arm64.deb ... Unpacking uuid-runtime (2.38-6) ... Setting up uuid-runtime (2.38-6) ... Adding group `uuidd' (GID 120) ... Done. adduser: Warning: The home dir /run/uuidd you specified can't be accessed: No such file or directory Adding system user `uuidd' (UID 113) ... Adding new user `uuidd' (UID 113) with group `uuidd' ... Not creating home directory `/run/uuidd'. Created symlink /etc/systemd/system/sockets.target.wants/uuidd.socket → /lib/systemd/system/uuidd.socket. uuidd.service is a disabled or a static unit, not starting it. First adduser warns about a non-existing dir, /run/uuidd and then it mentions not creating /run/uuidd. But that is/seems inconsistent with what `ls` tells me: root@cs21:~# ls -lhd /run/uuidd/ drwxr-xr-x 2 root root 60 Jul 30 14:57 /run/uuidd/ - -- System Information: Debian Release: bookworm/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing') Architecture: arm64 (aarch64) Kernel: Linux 5.18.0-3-arm64 (SMP w/4 CPU threads) Kernel taint flags: TAINT_CRAP Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8), LANGUAGE=en_US:en Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages uuid-runtime depends on: ii adduser 3.123 ii init-system-helpers 1.64 ii libc6 2.33-8 ii libsmartcols1 2.38-6 ii libsystemd0 251.3-1 ii libuuid1 2.38-6 uuid-runtime recommends no packages. uuid-runtime suggests no packages. - -- no debconf information -----BEGIN PGP SIGNATURE----- iHUEARYIAB0WIQT1sUPBYsyGmi4usy/XblvOeH7bbgUCYuUtNgAKCRDXblvOeH7b bm7vAQD1G1O7ZumkFKy2c2eJzNKAqoMgyu36fMSD5he7Fo/8qQEAuWaLMzP2mCjA UlvVMNRb1yg+cb/zdL5YdsVxZFRYkQA= =L3yL -----END PGP SIGNATURE-----
[toc] | [next] | [standalone]
| From | Chris Hofstaedtler <zeha@debian.org> |
|---|---|
| Date | 2022-07-30 17:00 +0200 |
| Message-ID | <EOW6B-eQrf-9@gated-at.bofh.it> |
| In reply to | #1111464 |
Hi, thanks for the report. * Diederik de Haas <didi.debian@cknow.org> [220730 15:12]: [..] > adduser: Warning: The home dir /run/uuidd you specified can't be accessed: No such file or directory > Adding system user `uuidd' (UID 113) ... > Adding new user `uuidd' (UID 113) with group `uuidd' ... Right. Not sure if we can suppress the warning. [..] > First adduser warns about a non-existing dir, /run/uuidd and then it > mentions not creating /run/uuidd. > > But that is/seems inconsistent with what `ls` tells me: > > root@cs21:~# ls -lhd /run/uuidd/ > drwxr-xr-x 2 root root 60 Jul 30 14:57 /run/uuidd/ uuidd.socket listens on /run/uuidd/request, so thats automatically created by systemd. The warning is only shown on first install, as the user then remains on the system, even if uuid-runtime is purged. One way of fixing this would probably be switching to DynamicUser. Chris
[toc] | [prev] | [next] | [standalone]
| From | Diederik de Haas <didi.debian@cknow.org> |
|---|---|
| Date | 2022-07-30 22:20 +0200 |
| Message-ID | <EP16i-eTy2-3@gated-at.bofh.it> |
| In reply to | #1111478 |
[Multipart message — attachments visible in raw view] — view raw
Hi, On zaterdag 30 juli 2022 16:46:57 CEST Chris Hofstaedtler wrote: > * Diederik de Haas <didi.debian@cknow.org> [220730 15:12]: > > adduser: Warning: The home dir /run/uuidd you specified can't be accessed: > > No such file or directory Adding system user `uuidd' (UID 113) ... > > Adding new user `uuidd' (UID 113) with group `uuidd' ... > > Right. Not sure if we can suppress the warning. From https://wiki.debian.org/ReleaseGoals/RunDirectory: "/run is a new cross-distribution location for the storage of transient state files [...] which does not require preserving across reboots." My first thought was that /run/ was possibly an inappropriate directory for a home directory, till I found others do it too (and also remember a warning wrt pulseaudio about using /var/run instead of /run). I can create a directory in /run as root, so it doesn't seem to be a permission issue. Maybe it's a check within 'adduser' which generates the warning and prevents the creation of /run/uuidd ? Looking for other (system) user accounts with also a homedir in /run/ and found: https://salsa.debian.org/pulseaudio-team/pulseaudio/-/blob/master/debian/pulseaudio.postinst It uses a '--quiet' parameter, which may suppress the warning? > uuidd.socket listens on /run/uuidd/request, so thats automatically > created by systemd. > > The warning is only shown on first install, as the user then > remains on the system, even if uuid-runtime is purged. One way of > fixing this would probably be switching to DynamicUser. Not (very) knowledgeable about systemd, so can't comment on that. But if it can work also outside systemd, I'd prefer it. I'm fine if you want to close the bug as it is minor indeed :-) Cheers, Diederik
[toc] | [prev] | [standalone]
Back to top | Article view | linux.debian.bugs.dist
csiph-web