Your message dated Mon, 09 Mar 2020 18:34:18 +0000 with message-id <e1jbnei-0002sv...@fasolo.debian.org> and subject line Bug#950836: fixed in gnupg2 2.2.19-3 has caused the Debian Bug report #950836, regarding gpg-agent: generator 90gpg-agent and user with no home crontask generate annoying logs to be marked as done.
This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 950836: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=950836 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
--- Begin Message ---Package: gpg-agent Version: 2.2.12-1+deb10u1 Severity: normal Dear Maintainer, Every day I receive some logs after cron.daily execution like these systemd[2626]: gpgconf: running /usr/bin/gpg-agent failed (exitcode=2): General error systemd[2626]: gpgconf: fatal error (exit status 1) Some cron tasks are executed as «nobody» user, which have no home. When executing the script «/usr/lib/systemd/user-environment-generators/90gpg-agent» as nobody, gpgconf break with these lines. To reproduce, you can also as root sudo -u nobody gpgconf --list-options gpg-agent Is it possible to update the user-environment-generator ? Redirect stderr would be sufficient ? if [ -n "$(gpgconf --list-options gpg-agent | \ => if [ -n "$(gpgconf --list-options gpg-agent 2>/dev/null | \ Masking globally all gpg services/socket as suggested in /usr/share/doc/gpg-agent/README.Debian is ineffective as generator executed on each new session. Regards, L.Wafflard -- System Information: Debian Release: 10.2 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 4.19.0-6-amd64 (SMP w/1 CPU core) Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), LANGUAGE=fr_FR.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages gpg-agent depends on: ii gpgconf 2.2.12-1+deb10u1 ii libassuan0 2.5.2-1 ii libc6 2.28-10 ii libgcrypt20 1.8.4-5 ii libgpg-error0 1.35-1 ii libnpth0 1.6-1 ii pinentry-curses [pinentry] 1.1.0-2 Versions of packages gpg-agent recommends: ii gnupg 2.2.12-1+deb10u1 Versions of packages gpg-agent suggests: pn dbus-user-session <none> ii libpam-systemd 241-7~deb10u2 pn pinentry-gnome3 <none> pn scdaemon <none> -- no debconf information
--- End Message ---
--- Begin Message ---Source: gnupg2 Source-Version: 2.2.19-3 Done: Daniel Kahn Gillmor <d...@fifthhorseman.net> We believe that the bug you reported is fixed in the latest version of gnupg2, 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 950...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Daniel Kahn Gillmor <d...@fifthhorseman.net> (supplier of updated gnupg2 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 ftpmas...@ftp-master.debian.org) -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 Format: 1.8 Date: Mon, 09 Mar 2020 14:27:42 -0400 Source: gnupg2 Architecture: source Version: 2.2.19-3 Distribution: unstable Urgency: medium Maintainer: Debian GnuPG Maintainers <pkg-gnupg-ma...@lists.alioth.debian.org> Changed-By: Daniel Kahn Gillmor <d...@fifthhorseman.net> Closes: 950836 Changes: gnupg2 (2.2.19-3) unstable; urgency=medium . * d/copyright update years * Avoid errors in systemd environment generator (Closes: #950836) Checksums-Sha1: f7672ad08dad54bf497b71f90ec9e56622617463 3238 gnupg2_2.2.19-3.dsc 6ac90ef2810cbc0c83a673498a69e4af9d8ed82d 62708 gnupg2_2.2.19-3.debian.tar.xz 953693e457ff22b0adaae48410c1929bae064468 10351 gnupg2_2.2.19-3_source.buildinfo Checksums-Sha256: cb7863566295d74c18a4ecdc02d9e06bfcebabf43b94b9246c43fb2a9874e881 3238 gnupg2_2.2.19-3.dsc c21812b36b7da7ebf748fdd02bbaee376060f95ed2b897332887cc240650a89f 62708 gnupg2_2.2.19-3.debian.tar.xz 4a5f77d4f98d0021e6d12992c24050dc8f3cc6cf93b14bfb84235c1dca4dbf46 10351 gnupg2_2.2.19-3_source.buildinfo Files: 5d86b38468b9184a4015199b64c0eaca 3238 utils optional gnupg2_2.2.19-3.dsc 51d83ecee290b06271a6587f0eceffd9 62708 utils optional gnupg2_2.2.19-3.debian.tar.xz d94943dbd0e6487270abb671021b6442 10351 utils optional gnupg2_2.2.19-3_source.buildinfo -----BEGIN PGP SIGNATURE----- iHUEARYIAB0WIQQsv6x2UaqQJzY+dXHEDyVUMvKBDwUCXmaKuwAKCRDEDyVUMvKB DynFAQCkqmoBwDfSTwUk9FuMaukSr0g1z4/P3nGUmvmIKrtBnwD/ShpVi7AOjjaH xk80uZnfwY03ghjZNyE09qG5ofpXyw4= =dJi0 -----END PGP SIGNATURE-----
--- End Message ---
