Debian Bug report logs - #1107682
gdm3: ship sysusers.d config file

Display info messages

Message #5 received at submit@bugs.debian.org (full text, mbox, reply):

From: Luca Boccassi <bluca@debian.org>

To: Debian Bug Tracking System <submit@bugs.debian.org>

Subject: gdm3: ship sysusers.d config file

Date: Thu, 12 Jun 2025 01:06:33 +0100

Package: gdm3
Severity: wishlist
Tags: patch

Dear Maintainer(s),

In order to seamlessly support use cases such as usr-only images with
an ephemeral/factory reset/firstboot /etc/ it would be great to use a
sysusers.d file for the Debian-gdm user/group.

MR available at: https://salsa.debian.org/gnome-team/gdm/-/merge_requests/28

Message #8 received at 1107682-submitter@bugs.debian.org (full text, mbox, reply):

From: Simon McVittie <noreply@salsa.debian.org>

To: 1107682-submitter@bugs.debian.org

Subject: Bug#1107682 marked as pending in gdm3

Date: Thu, 14 Aug 2025 23:55:44 +0000

Control: tag -1 pending

Hello,

Bug #1107682 in gdm3 reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:

https://salsa.debian.org/gnome-team/gdm/-/commit/0dd7abb89bebe31f9013ca1312e7c4302a22cbef

------------------------------------------------------------------------
Use sysusers.d file for Debian-gdm

Leave the adduser dependency and the user/group deletion as-is
in the postrm, as it's pre-existing. It can be dropped later
if no longer needed.

Shipping a sysusers file allows to install usr-only images with
an ephemeral/factory reset/firstboot /etc/.

Closes: #1107682
------------------------------------------------------------------------

(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1107682

Message #15 received at 1107682-close@bugs.debian.org (full text, mbox, reply):

From: Debian FTP Masters <ftpmaster@ftp-master.debian.org>

To: 1107682-close@bugs.debian.org

Subject: Bug#1107682: fixed in gdm3 48.0-3

Date: Fri, 15 Aug 2025 12:07:22 +0000

[Message part 1 (text/plain, inline)]

Source: gdm3
Source-Version: 48.0-3
Done: Simon McVittie <smcv@debian.org>

We believe that the bug you reported is fixed in the latest version of
gdm3, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 1107682@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Simon McVittie <smcv@debian.org> (supplier of updated gdm3 package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmaster@ftp-master.debian.org)


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

Format: 1.8
Date: Fri, 15 Aug 2025 10:53:47 +0100
Source: gdm3
Architecture: source
Version: 48.0-3
Distribution: unstable
Urgency: medium
Maintainer: Debian GNOME Maintainers <pkg-gnome-maintainers@lists.alioth.debian.org>
Changed-By: Simon McVittie <smcv@debian.org>
Closes: 1107682
Changes:
 gdm3 (48.0-3) unstable; urgency=medium
 .
   * Team upload
 .
   [ Luca Boccassi ]
   * Use a sysusers.d file to create the Debian-gdm user.
     This allows /usr-only images with an ephemeral/factory reset/firstboot
     /etc/. (Closes: #1107682)
 .
   [ Simon McVittie ]
   * Activate dh_installsysusers declaratively rather than imperatively.
     This lets debhelper choose a good point in the sequence for it.
   * d/gdm3.postrm, d/control: Don't delete system user/group during purge.
     In previous discussions like #1006912 there seems to be consensus
     that removing uids is dangerous because there might still be files
     owned by that uid on the filesystem, causing unintended access to be
     granted if the uid is subsequently reused for a different system user.
     This also means we can drop the adduser dependency.
   * Build-depend on gir1.2-*-dev instead of libgirepository1.0-dev.
     libgirepository1.0-dev is not Multi-Arch co-installable and should be
     phased out during the forky release cycle.
   * d/control, d/rules: Let the package be cross-compiled.
     debhelper currently uses debcrossgen which does not support cross
     GObject-Introspection, so for now we need to opt-in to using
     `meson env2mfile` instead.
     We need to run dconf-cli from the build architecture, since we will
     be unable to run it from the host architecture in general.
   * d/copyright: Don't quote the FSF's former postal address
   * Standards-Version: 4.7.2 (no changes required)
Checksums-Sha1:
 b8643045c10154ea0070302ee43a01d272243dc5 3420 gdm3_48.0-3.dsc
 f166c2899cf0f53fb7c6e87a51ae6fc930a2c10a 87208 gdm3_48.0-3.debian.tar.xz
 333ef426a2488fcb2c6fc68c6bc2937e5a7e51b6 3286484 gdm3_48.0-3.git.tar.xz
 62ffcf5a625aa07c338fd82443815eac74c3863f 18038 gdm3_48.0-3_source.buildinfo
Checksums-Sha256:
 dc30d0317db2f6031a3b8a6f97805223af94285f89b26db0001d2779915d03dd 3420 gdm3_48.0-3.dsc
 b2bb0ee408702d215d1ff6e98084f34a551ec74118a59ccabb24a61f69b384db 87208 gdm3_48.0-3.debian.tar.xz
 040557517cd6b3e7e10f5d20ccfc47b30c66f4f980f167a332f57b0e6967e27e 3286484 gdm3_48.0-3.git.tar.xz
 820f83b5854486e06b2b8bd1a2ac53cfdaf2168ac97c722ac0164016151766c9 18038 gdm3_48.0-3_source.buildinfo
Files:
 83a2b0f30413e5971a49ab31e5eb5e21 3420 gnome optional gdm3_48.0-3.dsc
 4bf057d435034f5fb374a14dc5422685 87208 gnome optional gdm3_48.0-3.debian.tar.xz
 ce0472d6ed5c1033b9b9cf57c3d02cc3 3286484 gnome optional gdm3_48.0-3.git.tar.xz
 73c0fb2dae84bea46e46f956e6e78c91 18038 gnome optional gdm3_48.0-3_source.buildinfo
Git-Tag-Info: tag=126185576e7d7244f36f05533c52792c63aa8758 fp=7a073ad1ae694fa25bff62e5235c099d3eb33076
Git-Tag-Tagger: Simon McVittie <smcv@debian.org>

-----BEGIN PGP SIGNATURE-----

iQIzBAEBCgAdFiEEN02M5NuW6cvUwJcqYG0ITkaDwHkFAmifGogACgkQYG0ITkaD
wHmMHw//Qo78M3dOay9Di9CIET+ZLYOTvKjCCnGaSxI7j4qkOK7o9zIXx/4wOVDf
4M7N9ofg88RE7JVUTR5wYZg0LJWeln0DTE8h9CsilmgCLEQu2RXRH0IWRQyeF2hN
Oc4TvANNIFc7lkglZ17Aq5vXfloEG8L7W/1Y4d9OvtgJaBN5zp4WX7jvP6iQGV/j
j8IBH6ouc0Dez2z4FrIMo01LUtQdrzKu7BurM3HMiXdIMLRqQFK3Saws1zVuqTUw
HglE4M29PI5MfvaWjUuQdYbgMBASE+Ix7dHt1cMGszPIcm1u9nKL4ipCmYDUOxnM
ZrhgtCl3uQcooPjkwMrNSsnJX3cPIgBPlmmb5yXAN3mj0kIvmAhN15njbpb2uE9n
DowEuJ7lNwjnwEF3ZuVbfdAlckSRI/L6B+G2um2OFz+jXHgmSWmE3iRQnhuOVF52
POw4k63HddFWdeBzHSia9I16Z5lLWbfhTTPw07UClgkbBIRyupKkMcJnLFt6yL+T
T2tH6t433HrOuJnfbLEiJR4HY2cN50uDarSjDzy2yf0LfCxBbf7z38JWuUK5KgJa
+IYWsNr6mR1XfoaGaX/8p/3uG2jXc+gPg75TovkixFnZeq9yDhYjx0AbenD5enIf
c+jaD63CufHWuhuN2pYfvUHG8ubsx+HQFQC4dvoUDUPXyEEh60A=
=RfAn
-----END PGP SIGNATURE-----

[Message part 2 (application/pgp-signature, inline)]

Send a report that this bug log contains spam.