Bug#1036448: debhelper: please add helper for autoconf 2.71 autoupdate

[Martin-Éric Racine]

Fair enough.

Could the dh-autoreconf maintainer acknowledge this bug and tell us
his intentions?

Martin-Éric

On Mon, 22 May 2023 09:30:55 +0200 Niels Thykier  wrote:
> Control: reassign -1 dh-autoreconf
>
> The dh-autoreconf tool is maintained in a separate package; re-assigning.
>
> Best regards,
> Niels
>
> Martin-Éric Racine:
> > Package: debhelper
> > Version: 13.11.4
> > Severity: wishlist
> >
> > Possibly related to dh_autoreconf:
> >
> > Since autoconf 2.71 has entered the archive, it often complains about 
> > outdated macros, asking for 'autoupdate' to be run. Example:
> >
> > dh binary --builddirectory=build/
> > dh_update_autotools_config -O--builddirectory=build/
> > dh_autoreconf -O--builddirectory=build/
> > libtoolize: putting auxiliary files in AC_CONFIG_AUX_DIR, 'build-aux'.
> > libtoolize: copying file 'build-aux/ltmain.sh'
> > libtoolize: putting macros in AC_CONFIG_MACRO_DIRS, 'm4'.
> > libtoolize: copying file 'm4/libtool.m4'
> > libtoolize: copying file 'm4/ltoptions.m4'
> > libtoolize: copying file 'm4/ltsugar.m4'
> > libtoolize: copying file 'm4/ltversion.m4'
> > libtoolize: copying file 'm4/lt~obsolete.m4'
> > configure.ac:42: warning: The macro `AC_PROG_LIBTOOL' is obsolete.
> > configure.ac:42: You should run autoupdate.
> > m4/libtool.m4:100: AC_PROG_LIBTOOL is expanded from...
> > configure.ac:42: the top level
> > configure.ac:48: warning: The macro `AC_PROG_CC_C99' is obsolete.
> > configure.ac:48: You should run autoupdate.
> > ./lib/autoconf/c.m4:1659: AC_PROG_CC_C99 is expanded from...
> > aclocal.m4:1899: XORG_COMPILER_BRAND is expanded from...
> > aclocal.m4:2018: XORG_COMPILER_FLAGS is expanded from...
> > aclocal.m4:2190: XORG_DEFAULT_OPTIONS is expanded from...
> > configure.ac:48: the top level
> > configure.ac:52: warning: The macro `AC_PROG_LIBTOOL' is obsolete.
> > configure.ac:52: You should run autoupdate.
> > m4/libtool.m4:100: AC_PROG_LIBTOOL is expanded from...
> > configure.ac:52: the top level
> >
> > Running 'autoupdate' indeed makes autoconf stop complaining, but it also 
> > results in dpkg forcing us to create a patch against autoconf.ac, which is 
> > IMHO the wrong approach.
> >
> > Unless I'm mistaken, this is a case similar to updating config.guess and 
> > config.sub, so there should be a way to tell dh_autoreconf to run 
> > 'autoupdate' without making dkpg complain.
> >
> > Martin-Éric
> >
> > [...]
> >
>
>

Bug#1072857: dput: Incorrect delayed argument: ValueError: delayed days value must be a decimal integer:

[Martin-Éric Racine]

Package: dput
Version: 1.2
Severity: normal

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

$ dput mentors ../xserver-xorg-video-geode_2.11.21-4_source.changes
Checking signature on .changes
gpg: ../xserver-xorg-video-geode_2.11.21-4_source.changes: Valid signature from 
AE1F8277C4B4D7B6
Checking signature on .dsc
gpg: ../xserver-xorg-video-geode_2.11.21-4.dsc: Valid signature from 
AE1F8277C4B4D7B6
Incorrect delayed argument: ValueError: delayed days value must be a decimal 
integer:

I did not specify any delayed queue, so I am perplexed as to what produced this.

Martin-Éric

- -- Package-specific info:

- -- /etc/dput.cf --
# Example dput.cf that defines the host that can be used
# with dput for uploading.

[DEFAULT]
login   = *
method  = ftp
hash= md5
allow_unsigned_uploads  = 0
allow_dcut  = 0
run_lintian = 0
run_dinstall= 0
check_version   = 0
scp_compress= 0
post_upload_command =
pre_upload_command  =
passive_ftp = 1
default_host_main   =
allowed_distributions   = (?!UNRELEASED)

[ftp-master]
fqdn= ftp.upload.debian.org
incoming= /pub/UploadQueue/
login   = anonymous
allow_dcut  = 1
method  = ftp
# Please, upload your package to the proper archive
# 
https://www.debian.org/doc/manuals/developers-reference/pkgs.html#bug-security-upload
allowed_distributions   = (?!UNRELEASED|.*-security)

# https://lists.debian.org/debian-project/2009/05/msg00036.html
[ftp-eu]
fqdn= ftp.eu.upload.debian.org
method  = ftp
incoming= /pub/UploadQueue/
login   = anonymous
allow_dcut  = 1
# Please, upload your package to the proper archive
# 
https://www.debian.org/doc/manuals/developers-reference/pkgs.html#bug-security-upload
allowed_distributions   = (?!UNRELEASED|.*-security)

# https://lists.debian.org/debian-devel-announce/2008/09/msg7.html
[ssh-upload]
login   = *
# login = another_username
fqdn= ssh.upload.debian.org
method  = scp
incoming= /srv/upload.debian.org/UploadQueue/
allow_dcut  = 1
# Please, upload your package to the proper archive
# 
https://www.debian.org/doc/manuals/developers-reference/pkgs.html#bug-security-upload
allowed_distributions   = (?!UNRELEASED|.*-security)

# And if you want to override one of the defaults, add it here.
# For example, comment out the next line
# post_upload_command   = /path/to/some/script
# pre_upload_command= /path/to/some/script

[security-master]
fqdn= ftp.security.upload.debian.org
method  = ftp
incoming= /pub/SecurityUploadQueue
login   = anonymous
allow_dcut  = 1
# This has been added at the request of the security team.
# Please be sure to know what you are doing before taking it out.
pre_upload_command  = /usr/share/dput/helper/security-warning

[security-master-unembargoed]
fqdn= ftp.security.upload.debian.org
method  = ftp
incoming= /pub/OpenSecurityUploadQueue
login   = anonymous
allow_dcut  = 1
# This has been added at the request of the security team.
# Please be sure to know what you are doing before taking it out.
pre_upload_command  = /usr/share/dput/helper/security-warning

[ubuntu]
fqdn= upload.ubuntu.com
method  = ftp
incoming= /
login   = anonymous

[ppa]
fqdn= ppa.launchpad.net
method  = ftp
# replace  with your Launchpad ID
incoming= ~/ubuntu
login   = anonymous

[mentors]
method  = ftp
fqdn= mentors.debian.net
incoming= /pub/UploadQueue
login   = anonymous

[local]
method  = local
incoming= ~/public_html/debian/mini-dinstall/incoming
run_dinstall= 0
post_upload_command = /usr/bin/mini-dinstall --batch


# Local variables:
# coding: utf-8
# mode: conf
# End:
# vim: fileencoding=utf-8 filetype=config :

- -- /home/perkelix/.config/dput/dput.cf --

- -- /home/perkelix/.dput.cf --
[mentors-ftp]
fqdn = mentors.debian.net
incoming = /pub/UploadQueue/
method = ftp
allow_unsigned_uploads = 0
run_lintian = 1
passive_ftp = 1
login = anonymous

[mentors-https]
fqdn = mentors.debian.net
incoming = /upload
method = https
allow_unsigned_uploads = 0
run_lintian = 1

[ppa]
fqdn = ppa.launchpad.net
incoming = ~q-funk/ppa/ubuntu/
method = ftp
allow_unsigned_uploads = 0
run_lintian = 1
login = anonymous

[esteid]
fqdn = ppa.launchpad.net
incoming = ~esteid/ppa/ubuntu/
method = ftp
allow_unsigned_uploads = 0
run_lintian = 1
login = anonymous

[x-swat]
fqdn = 

Bug#1072066: systemd: upgrade to 256~rc3-3: legacy.conf:13: Duplicate line for path "/run/lock", ignoring.

[Martin-Éric Racine]

Package: systemd
Version: 256~rc3-3
Severity: normal

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Setting up systemd (256~rc3-3) ...
/usr/lib/tmpfiles.d/legacy.conf:13: Duplicate line for path "/run/lock", 
ignoring.


- -- Package-specific info:

- -- System Information:
Debian Release: trixie/sid
  APT prefers unstable
  APT policy: (900, 'unstable')
Architecture: i386 (x86_64)

Kernel: Linux 6.1.0-21-amd64 (SMP w/4 CPU threads; PREEMPT)
Locale: LANG=fi_FI.UTF-8, LC_CTYPE=fi_FI.UTF-8 (charmap=UTF-8), LANGUAGE=fi:en
Shell: /bin/sh linked to /usr/bin/dash
Init: unable to detect

Versions of packages systemd depends on:
ii  libacl12.3.2-2
ii  libapparmor1   3.0.13-2
ii  libaudit1  1:3.1.2-2.1
ii  libblkid1  2.40.1-2
ii  libc6  2.38-11
ii  libcap21:2.66-5
ii  libcryptsetup122:2.7.2-2
ii  libfdisk1  2.40.1-2
ii  libmount1  2.40.1-2
ii  libpam0g   1.5.3-7
ii  libseccomp22.5.5-1
ii  libselinux13.5-2+b2
ii  libssl3t64 3.2.1-3
ii  libsystemd-shared  256~rc3-3
ii  libsystemd0256~rc3-3
ii  mount  2.40.1-2

Versions of packages systemd recommends:
ii  dbus [default-dbus-system-bus]   1.14.10-4+b1
ii  libzstd1 1.5.5+dfsg2-2
ii  systemd-timesyncd [time-daemon]  256~rc3-3

Versions of packages systemd suggests:
ii  libgcrypt20   1.10.3-3
ii  libidn2-0 2.3.7-2
ii  liblz4-1  1.9.4-2
ii  liblzma5  5.6.1+really5.4.5-1
pn  libtss2-rc0t64
pn  libtss2-tcti-device0  
pn  polkitd   
pn  systemd-boot  
pn  systemd-container 
pn  systemd-homed 
pn  systemd-resolved  
pn  systemd-userdbd   

Versions of packages systemd is related to:
ii  dbus-user-session  1.14.10-4+b1
pn  dracut 
pn  initramfs-tools
ii  libnss-systemd 256~rc3-3
ii  libpam-systemd 256~rc3-3
pn  udev   

- -- no debconf information

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEyJACx3qL7GpObXOQrh+Cd8S017YFAmZVThMACgkQrh+Cd8S0
17Yj1w//TvIy5IYO9yHe1FPWTzerSTwgIeSjkaYD9Ch0yHzz0vtKWFW0EaQq4b/s
QzELfhVMDVhfwIKWCIiOB0LSk5i6MXkWIwmUU2c5uXRaRfirRG5jS8ItG+ZEibbr
MGh2JtOYIxpKPnScubx/lprjeWJDVehQJ6P6xEjZ2bE4n7+Y9MLWt/Nx1dk4a1Ix
dpN45g1iSybbs/KKvg0Fx8KI46gdn+K8hf9dp06khiQTgOYwIuMnU5p1hvNgHlyu
z3ezNOw4jKlugyJPnYYTTyrGk89rFJTA+omGh6Z4dhf/v8j0flZRnj31DPkeICKo
hNk2h0u0moD01D5E/OXpwvHdMIwmFH0A7bqUEieYAAcls7mZCHgX7hMRiE/8qOFv
DfTy9STAJO0Xm9Y5mvRCovCmrEmJ5AePZavm8ymdmA/m1ApIMAUz/+nk0CyLwnL4
/7Oa+kektmgG4Dp+XxK2lOjVd40duQ7HRNs2mpFcJ9yBWya1+gv3Lf/utt9uuGk2
VqVetoLl/0AYlP9g0PSdFxdqXZ7cbCVAC8TzLTPXu3UOlhBXziAxi/fQgCAYtDow
8Dj0MVv5uzd43m+4AGL7q7SaPkZMH2/Isl/VbnaJuirfpOXAq6/b85JALGd10Jg2
fkKwxphsZT4UjAfYsSUOLumLfe/3s8KuiVCLsJ4SL6jbpcIeJoM=
=M99n
-END PGP SIGNATURE-

Bug#1019922: debian-archive-keyring: Machine-readable copyright conversion

[Martin-Éric Racine]

Package: debian-archive-keyring
Version: 2023.4
Followup-For: Bug #1019922

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Alternately, please find attached this other version of a DEP-5 copyright.

Also included in the diff are automated improvements by 'routine-update'.

You're welcome to further edit as desired before merging.

Martin-Éric

- -- System Information:
Debian Release: trixie/sid
  APT prefers unstable
  APT policy: (900, 'unstable')
Architecture: i386 (x86_64)

Kernel: Linux 6.1.0-21-amd64 (SMP w/4 CPU threads; PREEMPT)
Locale: LANG=fi_FI.UTF-8, LC_CTYPE=fi_FI.UTF-8 (charmap=UTF-8), LANGUAGE=fi:en
Shell: /bin/sh linked to /usr/bin/dash
Init: unable to detect

- -- no debconf information

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEyJACx3qL7GpObXOQrh+Cd8S017YFAmZS27wACgkQrh+Cd8S0
17ZM2g/+KUeBgou27VU2K37JxGAcpCifgKlWVN2rFaGBkqYzxp/xg9eh1WKA8HVC
9M9xT3EBR1qhSgcckOmzySnEETVR1ItWeYqpi6MlpCCOZTmiBECn8M4XNEPxwbvA
CsX4WCA8Qkrw3aBmS28IthKukmexHRVktIoDPc2/xdxTG8LlHJ5wSlaOJLd8vqYm
90S7kHAbSNquk2SC1bB2Nn9KMNAjkI55wkqPxoXZiqC5Ue+dZwhdzRQc9W2iUS71
qFc7np2BdIZVz3Nv9IbgpT6BYq7y8HfHBnljSIib0T8HsYW/C1VlXzL3/4+PUO+G
tt4lOUp4u6IfB+02XCGQGhUjj0rUbNWTyINlkx9ZQEqDdEuwqnes0udRMXQRZWcR
QjtvQsMFvnjunEYQn5NncHtJAxgJ1jBZIomf3bviUTACn9d6pLv5zonLj7irozdJ
rKEFIEpta7STBKmVcrk9KiobFgX1By7+X+/iPEM/rkIs4NWOxGGHWNEj7ZAAzW/4
5+vGVSxihs9zgJIxcgz4aQjHAFSdyglCBSVBXmLRh76xANptfIIZHfP1uw3eNvbR
O4KwKJ5LESRnEP4xs3rVySWTfp9BDlBdJaEkapygTYBmrK1NBcqoYzqUaCaVfavx
6Zmsl/Qd2QjstGMX5N31oSSG1+xQ97htAGFc0pqqtGHiUihm9SQ=
=65gg
-END PGP SIGNATURE-
diff --git a/debian/changelog b/debian/changelog
index a3dd09e..86e4967 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,14 @@
+debian-archive-keyring (2023.4+nmu1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Standards-Version: 4.7.0 (routine-update).
+  * debhelper-compat 13 (routine-update).
+  * Remove trailing whitespace in debian/copyright (routine-update).
+  * Remove 7 obsolete maintscript entries in 1 files (routine-update).
+  * Migrated debian/copyright to DEP-5.
+
+ -- Martin-Éric Racine   Sun, 26 May 2024 09:36:32 
+0300
+
 debian-archive-keyring (2023.4) unstable; urgency=medium
 
   * Clean up leftover keyrings in trusted.gpg.d
diff --git a/debian/compat b/debian/compat
deleted file mode 100644
index f599e28..000
--- a/debian/compat
+++ /dev/null
@@ -1 +0,0 @@
-10
diff --git a/debian/control b/debian/control
index 6af283a..b5450d5 100644
--- a/debian/control
+++ b/debian/control
@@ -3,10 +3,10 @@ Priority: important
 Section: misc
 Maintainer: Debian Release Team 
 Uploaders: Niels Thykier ,
- Jonathan Wiltshire ,
-Build-Depends: debhelper (>= 10), jetring, gnupg
+   Jonathan Wiltshire 
+Build-Depends: debhelper-compat (= 13), gnupg, jetring
 Rules-Requires-Root: no
-Standards-Version: 4.6.0
+Standards-Version: 4.7.0
 Vcs-Browser: https://salsa.debian.org/release-team/debian-archive-keyring
 Vcs-Git: https://salsa.debian.org/release-team/debian-archive-keyring.git
 
diff --git a/debian/copyright b/debian/copyright
index d934ced..e2c7a1b 100644
--- a/debian/copyright
+++ b/debian/copyright
@@ -1,27 +1,19 @@
-This is Debian GNU's GnuPG keyrings of archive keys.
-
-This package was originally put together by Michael Vogt
- 
-
-The keys in the keyrings don't fall under any copyright.  Everything
-else in the package is covered by the GNU GPL.
-
-Debian support files Copyright (C) 2006 Michael Vogt  
-based on the debian-keyring package maintained by James Troup 
-
-Debian support files for debian-archive-keyring are free software; you
-can redistribute them and/or modify them under the terms of the GNU
-General Public License as published by the Free Software Foundation;
-either version 2, or (at your option) any later version.
-
-Debian support files for debian-archive-keyring are distributed in the
-hope that they will be useful, but WITHOUT ANY WARRANTY; without even
-the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR
-PURPOSE.  See the GNU General Public License for more details.
-
-You should have received a copy of the GNU General Public License with
-your Debian system, in /usr/share/common-licenses/GPL, or with the
-Debian GNU debian-archive-keyring source package as the file COPYING.
-If not, write to the Free Software Foundation, Inc., 51 Franklin Street,
-Fifth Floor, Boston, MA 02110-1301 USA.
+Format: https://www.debian.org/doc/packaging-manuals/copyright-format/1.0/
+Source: https://salsa.debian.org/release-team/debian-archive-keyring
+Upstream-Name: debian-archive-keyring
+Upstream-Contact: Debian Release Team 
 
+Files: *
+Copyright: © 2024 Martin-Éric Racine 
+   © 2021-2023 Jonathan Wiltshire 
+   © 2017-2018 Niels Thykier 
+   © 2014-2017 Adam D. Barratt 
+   © 2010-2014 Philipp Kern 
+   © 2008 Bastian Blank 
+   © 2008-2009 Luk Claes 
+   © 2007 Joey Hess 
+   © 2006 Anthony Towns 
+   © 2006-2007 Michael Vogt 
+License: GP

Bug#1071823: console-setup: [Hurd i386] debconf: lsmod: not found

[Martin-Éric Racine]

Package: console-setup
Version: 1.223
Severity: important

While upgrading from 1.223 to 1.226 on Hurd i386:

Fetched 32.4 MB in 23s (1429 kB/s)  

   
Extracting templates from packages: 100%
Preconfiguring packages ...
/var/cache/debconf/tmp.ci/console-setup.config.otOVsK: 1196: lsmod: not found

-- System Information:
Debian Release: trixie/sid
  APT prefers unreleased
  APT policy: (500, 'unreleased'), (500, 'unstable')
Architecture: hurd-i386 (i686-AT386)

Kernel: GNU-Mach 1.8+git20231217-486/Hurd-0.9
Locale: LANG=fi_FI.UTF-8, LC_CTYPE=fi_FI.UTF-8 (charmap=UTF-8), LANGUAGE=fi:en
Shell: /bin/sh linked to /usr/bin/dash
Init: sysvinit (via /sbin/init)

Versions of packages console-setup depends on:
ii  debconf [debconf-2.0]   1.5.85
ii  hurd1:0.9.git20231217-1
ii  keyboard-configuration  1.223
ii  xkb-data2.38-2

console-setup recommends no packages.

Versions of packages console-setup suggests:
iu  locales2.38-11
ii  sysvinit-utils [lsb-base]  3.08-6

Versions of packages keyboard-configuration depends on:
ii  debconf [debconf-2.0]   1.5.85
ii  liblocale-gettext-perl  1.07-6+b1
ii  xkb-data2.38-2

Versions of packages console-setup is related to:
pn  console-common
pn  console-data  
pn  console-tools 
pn  gnome-control-center  
pn  kbd   
pn  systemd   

-- debconf information:
* keyboard-configuration/variant: Finnish
* keyboard-configuration/optionscode:
* keyboard-configuration/modelcode: pc105
* console-setup/codesetcode: guess
* console-setup/charmap47: UTF-8
* keyboard-configuration/compose: No compose key
* keyboard-configuration/model: Generic 105-key PC
* console-setup/store_defaults_in_debconf_db: false
* keyboard-configuration/store_defaults_in_debconf_db: false
* keyboard-configuration/toggle: No toggling
  console-setup/guess_font:
* console-setup/fontface47: Fixed
  debian-installer/console-setup-udeb/title:
* keyboard-configuration/other:
  console-setup/framebuffer_only:
* keyboard-configuration/altgr: The default for the keyboard layout
* console-setup/fontsize-text47: 8x16
* keyboard-configuration/layout:
  keyboard-configuration/unsupported_options: true
* console-setup/fontsize: 8x16
  keyboard-configuration/unsupported_config_layout: true
* keyboard-configuration/ctrl_alt_bksp: false
* console-setup/codeset47: Guess optimal character set
  console-setup/use_system_font:
  keyboard-configuration/unsupported_layout: true
* keyboard-configuration/switch: No temporary switch
* keyboard-configuration/layoutcode: fi
* keyboard-configuration/xkb-keymap: fi
  keyboard-configuration/unsupported_config_options: true
* keyboard-configuration/variantcode:
* console-setup/fontsize-fb47: 8x16

Bug#1071489: tracker.debian.org: please upgrade Lintian to the latest

[Martin-Éric Racine]

ma 20. toukok. 2024 klo 18.09 Lucas Nussbaum (lu...@debian.org) kirjoitti:
> On 20/05/24 at 08:39 +0300, Martin-Éric Racine wrote:
> > Package: tracker.debian.org
> > Severity: important
> >
> > The Lintian on tracker.debian.org complains that 4.7.0 is 
> > newer-standards-version.
> >
> > Can you please upgrade it to the latest version?
>
> I think that tracker.d.o gets its lintian information from UDD (so the
> data is the same as one available from
> https://udd.debian.org/lintian/?email1=martin-eric.racine%40iki.fi=html_error=on_warning=on_tag=#all
> )
>
> As you can see in the footer of that page, UDD runs lintian 2.117.0.
> That's the latest lintian version.
>
> So the real problem is that the lintian version in the archive doesn't
> know about the debian-policy version in the archive...

Noted. This really needs to become a streamlined process i.e. whenever
a new policy is published, debian-policy and lintian get pushed into
Unstable at the same time, and Lintian immediately updated on all
applicable hosts. Otherwise, Lintian generates false positives on
newer-standards-version and also misses new things it should check to
match compliance with the new standard, all of which needlessly
complicates package maintainers' job.

Martin-Éric

Bug#1071489: tracker.debian.org: please upgrade Lintian to the latest

[Martin-Éric Racine]

Package: tracker.debian.org
Severity: important

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

The Lintian on tracker.debian.org complains that 4.7.0 is 
newer-standards-version.

Can you please upgrade it to the latest version?

Thanks!
Martin-Éric


-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEyJACx3qL7GpObXOQrh+Cd8S017YFAmZK4hAACgkQrh+Cd8S0
17ZFURAAp9KXen+WQbxVK+guJxZGlyounwk1mUh/Y1wU1nTNkYZUc4FiUmUbboo+
suzPRjMaovnsXZtDkhBWaz0jLRf/F4ZleLW2WoEgd9t61+PnAOJ2J3GR4kfoYTT0
Dh/jBX6IWVGfhcT7U7rcrfIZHrn7Vi1+58T9mN4WnW6ja19M5ruBbmOik9Bt+zol
pBKEdSFdlNORt+b1yO7Kvz/vQOaOUZrtOUfEBl8L23LPJPger1P0BVcl1410hHXs
I1kq3fHT7+2wzpEaiziTbVH/eLWaOEAZCIkvqbKXfQbS5n8GvaIXFhcYN3PtEJJO
qfcrSZth7fMH0YOd9klkQ4i4C8SFI5R6FqPUIkifTb4xKfAa6GBU8tG7WxGz8Sja
rqSWr1A4uw+Q8A1MAjlLOVZGNYx71tN25nGcYdWtwnW0sYxTouAbsl+c7iLSIPu5
MIuNtnPb4kB1iSVJdF4vgfZ5DVk9THh72neCUe40tiq3IlPA1qjFs8Gzstr7V6UX
m9wbqxHAAhVwQt/fIlRd0cFcWkq2/1de3Fpi4BabC6M8RtiXvD7tDG4eBv/m7gfc
OFLqhzHIcA72rLs4SoIiaFkMO1YiHgnP1Ko301crS92gfZdTgLBG8ofbaE9PbkuY
8MNjLtPPBrQUWuj6w/7cGsK6u7he0qCEjK7+fP4b6dXz49axuIw=
=hj3T
-END PGP SIGNATURE-

Bug#1071093: libc6: [adequate] undefined-symbol

[Martin-Éric Racine]

Package: libc6
Version: 2.38-11
Severity: important

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

$ adequate --all --tags -py-file-not-bytecompiled
libc6:i386: undefined-symbol /lib/i386-linux-gnu/libthread_db.so.1 => ps_pdwrite
libc6:i386: undefined-symbol /lib/i386-linux-gnu/libthread_db.so.1 => 
ps_pglobal_lookup
libc6:i386: undefined-symbol /lib/i386-linux-gnu/libthread_db.so.1 => 
ps_lsetregs
libc6:i386: undefined-symbol /lib/i386-linux-gnu/libthread_db.so.1 => ps_getpid
libc6:i386: undefined-symbol /lib/i386-linux-gnu/libthread_db.so.1 => 
ps_lgetfpregs
libc6:i386: undefined-symbol /lib/i386-linux-gnu/libthread_db.so.1 => 
ps_lsetfpregs
libc6:i386: undefined-symbol /lib/i386-linux-gnu/libthread_db.so.1 => 
ps_lgetregs
libc6:i386: undefined-symbol /lib/i386-linux-gnu/libthread_db.so.1 => ps_pdread


- -- System Information:
Debian Release: trixie/sid
  APT prefers unstable
  APT policy: (900, 'unstable')
Architecture: i386 (x86_64)

Kernel: Linux 6.1.0-21-amd64 (SMP w/4 CPU threads; PREEMPT)
Locale: LANG=fi_FI.UTF-8, LC_CTYPE=fi_FI.UTF-8 (charmap=UTF-8), LANGUAGE=fi:en
Shell: /bin/sh linked to /usr/bin/dash
Init: unable to detect

Versions of packages libc6 depends on:
ii  libgcc-s1  14-20240429-1

Versions of packages libc6 recommends:
ii  libidn2-0  2.3.7-2

Versions of packages libc6 suggests:
ii  debconf [debconf-2.0]  1.5.86
pn  glibc-doc  
ii  libc-l10n  2.38-11
pn  libnss-nis 
pn  libnss-nisplus 
ii  locales2.38-11

- -- debconf information excluded

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEyJACx3qL7GpObXOQrh+Cd8S017YFAmZDD1wACgkQrh+Cd8S0
17ZR7w/+OsMP7IW5GyIghTc+CkaIYuD6qT0a4v8SeNtfER5h1Y5THEx7Nylp02yz
fkS3RdsDa+GK3kMxOLK/OgNJ5Xv46ULX0/Dov+2OSHXcSMIuq3GwBwy4IZWN22WU
TDLwTl9+CPY3yX6v+03CpyoJTvb7dT2g4tgCamR1lOTwpmwg2gO9O5QBhB3gYGCb
i9+LatQMKWTnPc3MOKiVR3ABSGRGvoUB0Re51qdRyojq1w8cgzzCQeHsZYsM7ovX
oLMcMBXlvyL4/nQYkI+CMZwHabCM0RLCrUsb2lowcHi3bs66nK/p4LkiO68Za2vH
/kp7vykd5Sd+M08PatNxHQSUujmXPj+fQb6DwQtRVI85BlrSnUcuAOis/OUnk8uM
fjloB0svB47BFH4RGcggYGn5lTKKDoLRo1qxx1f3PLdvxyFqhliBL5ZJDu5ETi94
1QRmV8MfnSpGA1I1VSSPlmTjs9NiNMK0hJMGHVmQVzq/xmAt+m4ITbc6iyxs4mzu
bRdNRmkfhaJid+RZhkzwkIX77SlgvQXnN/ujvo/T2Q/xIgXoTCGgRnVf9IkglfmK
AcrH8CrkEr0KxDnlHWidSx5kiEmdUYavslAxROnDrSLTSk/Dnx8qSv65l6oBfr2f
Eq+83yv7BGHzjuu0T0tsIyGhYB+M0zgKD5nTCoUWTDtaWH/MEt0=
=xNVU
-END PGP SIGNATURE-

Bug#1071091: systemd: installs broken symbolic links

[Martin-Éric Racine]

Package: systemd
Version: 255.5-1
Severity: important

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

$ adequate --all --tags -py-file-not-bytecompiled
systemd: broken-symlink /etc/modules-load.d/modules.conf -> ../modules


- -- Package-specific info:

- -- System Information:
Debian Release: trixie/sid
  APT prefers unstable
  APT policy: (900, 'unstable')
Architecture: i386 (x86_64)

Kernel: Linux 6.1.0-21-amd64 (SMP w/4 CPU threads; PREEMPT)
Locale: LANG=fi_FI.UTF-8, LC_CTYPE=fi_FI.UTF-8 (charmap=UTF-8), LANGUAGE=fi:en
Shell: /bin/sh linked to /usr/bin/dash
Init: unable to detect

Versions of packages systemd depends on:
ii  libacl12.3.2-2
ii  libapparmor1   3.0.13-2
ii  libaudit1  1:3.1.2-2.1
ii  libblkid1  2.40-8
ii  libc6  2.38-11
ii  libcap21:2.66-5
ii  libcryptsetup122:2.7.2-2
ii  libfdisk1  2.40-8
ii  libgcrypt201.10.3-2+b1
ii  libkmod2   32-1
ii  liblz4-1   1.9.4-2
ii  liblzma5   5.6.1+really5.4.5-1
ii  libmount1  2.40-8
ii  libpam0g   1.5.3-7
ii  libseccomp22.5.5-1
ii  libselinux13.5-2+b2
ii  libssl3t64 3.2.1-3
ii  libsystemd-shared  255.5-1
ii  libsystemd0255.5-1
ii  libzstd1   1.5.5+dfsg2-2
ii  mount  2.40-8
ii  systemd-dev255.5-1

Versions of packages systemd recommends:
ii  dbus [default-dbus-system-bus]   1.14.10-4+b1
ii  systemd-timesyncd [time-daemon]  255.5-1

Versions of packages systemd suggests:
ii  libbpf1   1:1.4.1-1
ii  libfido2-11.14.0-1+b2
ii  libip4tc2 1.8.10-3
ii  libp11-kit0   0.25.3-5
pn  libpwquality1 
pn  libqrencode4  
pn  libtss2-esys-3.0.2-0  
pn  libtss2-mu-4.0.1-0
pn  libtss2-rc0   
pn  libtss2-tcti-device0  
pn  polkitd   
pn  systemd-boot  
pn  systemd-container 
pn  systemd-homed 
pn  systemd-resolved  
pn  systemd-userdbd   

Versions of packages systemd is related to:
ii  dbus-user-session  1.14.10-4+b1
pn  dracut 
pn  initramfs-tools
ii  libnss-systemd 255.5-1
ii  libpam-systemd 255.5-1
pn  udev   

- -- no debconf information

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEyJACx3qL7GpObXOQrh+Cd8S017YFAmZDDsEACgkQrh+Cd8S0
17ashA//VRcFHX1hLvzXIS1nF3+EnHkKgtllDpQwQbyjtSYZqcfyQ33LAPWdLAQB
cqyUhc8+Swm5vksaBQPv2tGt2wrCft8UAhFiBWLTsrC2vD4R6bRr8+CcNboj3AWH
7XOpQf/h8Ow9NIjhhy97gF3njBBrsl4g5zhrgWweL9QTlQCvfxwaYEt3dv11+dJq
x2EfXTf5jpKHnHXHTIA51rqzrlDOLBwpchQ123Pmw1Wo6QXYNkfyQqbhjFW0Ne9+
PB/dHsiq9hkBOuhQYjdQ75RfuYqoGN+QK5tVpBTotOu4z+t0sDwOsvlbz/Q5uBMn
UXlORLWb/LYahGO1+HCEgGKif0pb8HL69MA/GC6qSF/rRyDlr7JE7yLeqb2ac2z8
HmHwAfG5CVEI7PuOwCN9b+YBz5d798KkuEJRdP64pczxAr9Bk2QA/nnjWz+SQlLZ
FJ0N30mqi1/4kQPu9KHChBR0vzTt1vUYtY+qun6kWvb2poScfyfMSbQo1rN8/B4B
Ls89uAzUmj03LKOisXeWLDgBoqKg/Nvj4/P8Ydoluy4lvY9BqK/4OWwVwXBwoXHi
IwV57IAveVx9/Mgqg/Rcik5l+9iiEdnXgHv1N6jTmTTA2+JMTnEqN8ihAeo3otmW
UwFBnsIPn4zbKBr2cjw3+l86oR/txkGtDUbGcHYvhjh5tBwjne4=
=Zkx7
-END PGP SIGNATURE-

Bug#1071090: iso-codes: installs broken symbolic links

[Martin-Éric Racine]

Package: iso-codes
Version: 4.16.0-1
Severity: important

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

$ adequate --all --tags -py-file-not-bytecompiled
iso-codes: broken-symlink /usr/share/locale/fil/LC_MESSAGES/iso_3166.mo -> 
iso_3166-1.mo
iso-codes: broken-symlink /usr/share/locale/fil/LC_MESSAGES/iso_3166_2.mo -> 
iso_3166-2.mo


- -- System Information:
Debian Release: trixie/sid
  APT prefers unstable
  APT policy: (900, 'unstable')
Architecture: i386 (x86_64)

Kernel: Linux 6.1.0-21-amd64 (SMP w/4 CPU threads; PREEMPT)
Locale: LANG=fi_FI.UTF-8, LC_CTYPE=fi_FI.UTF-8 (charmap=UTF-8), LANGUAGE=fi:en
Shell: /bin/sh linked to /usr/bin/dash
Init: unable to detect

iso-codes depends on no packages.

iso-codes recommends no packages.

Versions of packages iso-codes suggests:
pn  isoquery  

- -- no debconf information

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEyJACx3qL7GpObXOQrh+Cd8S017YFAmZDDl8ACgkQrh+Cd8S0
17ZYLhAAsnzBthGEae4tlpZAjIy6yZ9LDDo4Pgujlz7br1cqKm19fHqd3Di/7W0N
qaNS5zFG86hEvDe5UClmTVIx40yI6r+LsKc6tHMLfVZc25cSYEkKG/RhquNF7H5X
eDXfPwXDhv85CrvHjW4fA1DlRK5lcjEie7WjVK9p2sl+BzmkCbARiopRnD2YIqzs
sp0lzWz0w6Lryv8COJOJ6PV3i27WHL4WZVPedSyOkHkHEb4rrpAja59Xr3s37cas
VV1zrjtnreQU7hbQsQjMUeLlC2v0I+/pQNIArFrz8dXxBuYr63xCZE7TPU3j9ANt
jC2UrmPGgrm0JuXtcwoeLPbhR7rVhXLhfw64hl21IAVOHJg4E6QkhdvrYO8MIKLk
9m9Sc9KiSU4TodrXDdaNoY/vBqhGNnUakZA2O5+LQTGCcagaOv0nni8D3h8YbKng
5HzDcn2dz+qbtrCGFlm7sjn7Pb3oydXzVJgr9EpRDljzps2+/00wg2RG9XSGTC4e
nHhOHnODQlropYkT46kCUD40bFvAgwZ41iykYHAHAJW1/C8dDvPH7OyzFDB3296Q
Rpx9YY0CLVRj9otwrcj9Si2ZPx9SD6JXExt0PQ51dFD/VoZIq9hVtnJyV4Te3y6o
Brofp0caZHJt7XBwHAtGe1nRk/9iKc+pGA37FKIWY8X5E0S7xZ0=
=bqAZ
-END PGP SIGNATURE-

Bug#1070735: micro-httpd: debian/copyright update attached

[Martin-Éric Racine]

Source: micro-httpd
Version: 20140814-3
Severity: normal

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Authors for the Debian folder content are updated. See attachment.

Martin-Éric

- -- System Information:
Debian Release: trixie/sid
  APT prefers unstable
  APT policy: (900, 'unstable')
Architecture: i386 (x86_64)

Kernel: Linux 6.1.0-21-amd64 (SMP w/4 CPU threads; PREEMPT)
Locale: LANG=fi_FI.UTF-8, LC_CTYPE=fi_FI.UTF-8 (charmap=UTF-8), LANGUAGE=fi:en
Shell: /bin/sh linked to /usr/bin/dash
Init: unable to detect

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEyJACx3qL7GpObXOQrh+Cd8S017YFAmY7HcoACgkQrh+Cd8S0
17aT7A//QBnHF7BnwdrluacAzTnY+0GY5sNFTG42RRnL/s3VU3aNetQLQCJGz1ow
RZ/je9Jr8JzMtR6usv/eoRyH3YhrDwzu8ZjDm5/395tVNAgJPEBzl1NtDfGMujMT
JRY04EtdcSvj0rSXF0jxHauI+tARvtGyiNTS95cUEB9Tyb0dEz5F+II41aEJwjN6
8YjMYBzTgQxAho/vDFVUzazinFCmBJiHMoqxHz85wNXaG2tdckwI6L4zI+UWoW9P
2BaT6nDcwkahiUZ/Ry1QnNdK5e720dshfaFE22+5Rem4U1zmxz8v/vzFGWelB4+8
6c8IU19aiVLNnQbGp7zlFukB2jkyqHdO9veBmxZfzP0cdaECbhdUGwSPWLuySiTD
ZCHjiiCBsLMEx+1gIwGiPvKx1L0Dhc3m1hIrB3KHBo51ZIV/9ZfyOCJDvJ0VDNWC
5gJrkKT6LDSYXGOeIkmpAh1hFe1LqNtAW8ovQhh+EWh0gjeqS2GxHaC+C3RDDCFn
26Fb2oXg4UjEd0LrH2sJKTZQrdzhjuuHim3qkVJOgjyCKYmv6H3VRI/9AW23EB7L
xbyNKpmFysZlfsIMExBzPyLB4wf9Z5C18oA+9n0vo9TPDzRwtLpkif+zIaZfYt66
UTF1Kr0jTu9r+70P5eOxx2RMjkwAToy9iBwPjyc0k1bHNkgl8W4=
=/kLu
-END PGP SIGNATURE-
--- a/debian/copyright  2024-05-04 14:01:59.0 +0300
+++ b/debian/copyright  2024-05-08 09:34:55.977467089 +0300
@@ -10,6 +10,9 @@ License: BSD-2-Clause
 
 Files: debian/*
 Copyright:
+  2021-2024 Martin-Éric Racine 
+  2019-2024 Sudip Mukherjee 
+  2016 Christian Hofstaedtler 
   2009-2012 Jari Aalto 
   2004-2007 Daniel Baumann 
 License: BSD-2-Clause

Bug#1070734: micro-httpd: Lintian-brush fixes attached

[Martin-Éric Racine]

Source: micro-httpd
Version: 20140814-3
Severity: normal

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Please find attached some minor fixes performed by Lintian-brish.

Martin-Éric

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEyJACx3qL7GpObXOQrh+Cd8S017YFAmY7Gj0ACgkQrh+Cd8S0
17b09g/8CSJpwhTaLIQryL66OUUV2GaAzkr6Q+aTDFH7jhLG+gB3vEAkzJAEetgg
NiNGRQ0eDeYef1EGvAQmnmDbVCiNQPQYAHyHgnivFnawk5bGrHGqS83d3yuSO9rw
6ayFDuameg4gAZ+IXdWm9xjk9U/AXc7cOyVyg+vpG+gq2VworPjAg1smCCXcfw/Y
8O24SxIR0NekVW3i936Tov7/VfN2pnMEJICiAnagIS6f/OITrl0BW9bYWi0YGoYN
22siaPW2Ha6VQOkgeRQotDsXFig0KRHNfAfu18rvCOzoZIlYF99G/2VnbJj0c+VX
xKeABJBoZcsl/aCNOx/3ljRLdrMgsUg4ejXgGqzlql2+UkROGWfraVUkZ/XYfKHC
1HntIh7JOO2fvbaa+S6dzC25Wc9imTD6fS+1hX7nsy9N0i7W1E3GkqwG9r94NJll
mLhnHNAf3KR7UCeNE4m07F9f0zwHtFbhC0zkbI9uFbH2zf+LyQ/s2+HOl+YHixvj
srKlZWxGYCOZazdn0JTp8fCszgc8hbuHHKfX1NUBgvdK27ePaTy/BRKFQ9Bc+QTB
LjioSER1B0Il+zWAZ8B1yo/85xHxui1G/f1ft6+tyrPTv4nRhKQbTC8JUkE5PASJ
BVssPL6+4Vg5T/4+Go5abFHx8vfiHJNpHQff8HYGhIt+s+q7sVE=
=Q5j4
-END PGP SIGNATURE-
diff --git a/debian/changelog b/debian/changelog
index 40bbe2b..1a9fcf6 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,11 @@
+micro-httpd (20140814-4) unstable; urgency=low
+
+  [ Debian Janitor ]
+  * Update watch file format version to 4.
+  * Avoid explicitly specifying -Wl,--as-needed linker flag.
+
+ -- Sudip Mukherjee   Mon, 06 May 2024 16:34:16 
+0300
+
 micro-httpd (20140814-3) unstable; urgency=medium
 
   [ Martin-Éric Racine ]
diff --git a/debian/rules b/debian/rules
index 14be6bb..9f3b272 100755
--- a/debian/rules
+++ b/debian/rules
@@ -8,7 +8,6 @@ include debian/debian-vars.mk
 
 export DEB_BUILD_MAINT_OPTIONS = hardening=+all
 export DEB_CFLAGS_MAINT_APPEND = -Wall -pedantic
-export DEB_LDFLAGS_MAINT_APPEND = -Wl,--as-needed
 
 man:
# target: man -- convert *.pod to manual page
diff --git a/debian/watch b/debian/watch
index 77f22e8..65061e7 100644
--- a/debian/watch
+++ b/debian/watch
@@ -1,2 +1,2 @@
-version=3
+version=4
 https://www.acme.com/software/micro_httpd/ .*micro_httpd_(.+).tar.gz

Bug#1027978: micro-httpd: sends invalid HTTP when listing unreadable directories

[Martin-Éric Racine]

ma 29. huhtik. 2024 klo 20.59 Sudip Mukherjee
(sudipm.mukher...@gmail.com) kirjoitti:
>
> On Mon, 29 Apr 2024 at 09:00, Martin-Éric Racine
>  wrote:
> >
> > On Thu, 05 Jan 2023 13:08:45 + Vincent Duvert  
> > wrote:
> > > Package: micro-httpd
> > > Version: 20140814-2.1+b2
> > > Severity: normal
> > > Tags: patch
> > > X-Debbugs-Cc: report...@duvert.net
> >
> > I have an NMU ready to cover this, debdiff attached.
>
> Thanks for the debdiff. But the diff is removing few of the Depends:
>
> micro-inetd | netcat-traditional | systemd-sysv
>
> Was that intentional or did you miss them? If intentional, then can
> you please explain why those are not needed now.

What is currently there is exactly what Lintian wants to see for any
package that updates any variant of inetd. Any additional alternative
makes Lintian barf, and overriding this particular one would not make
sense.

Meanwhile, systemd-sysv has a priority:important so it comes installed
by default on Linux-based hosts. If the Depends was only there because
you ship a systemd unit, it's not needed.

Martin-Éric

Bug#1027978: micro-httpd: sends invalid HTTP when listing unreadable directories

[Martin-Éric Racine]

On Thu, 05 Jan 2023 13:08:45 + Vincent Duvert  wrote:
> Package: micro-httpd
> Version: 20140814-2.1+b2
> Severity: normal
> Tags: patch
> X-Debbugs-Cc: report...@duvert.net

I have an NMU ready to cover this, debdiff attached.

Martin-Éric
diff -Nru micro-httpd-20140814/debian/changelog 
micro-httpd-20140814/debian/changelog
--- micro-httpd-20140814/debian/changelog   2021-10-14 16:02:47.0 
+0300
+++ micro-httpd-20140814/debian/changelog   2024-04-29 10:01:57.0 
+0300
@@ -1,3 +1,15 @@
+micro-httpd (20140814-2.2) unstable; urgency=medium
+
+  * Non-Maintainer Upload.
+  * Bump debhelper-compat to 13.
+  * Fix Lintian override syntax.
+  * Fix "Lintian: W: missing Depends on update-inetd" (Closes: #997691).
+  * Fix "sends invalid HTTP when listing unreadable dirs" (Closes: #1027978).
+Implemented the first alternative proposed in the bug report i.e.
+redirect standard error to systemd journal.
+
+ -- Martin-Éric Racine   Mon, 29 Apr 2024 10:01:57 
+0300
+
 micro-httpd (20140814-2.1) unstable; urgency=medium
 
   * Non-Maintainer Upload.
diff -Nru micro-httpd-20140814/debian/control 
micro-httpd-20140814/debian/control
--- micro-httpd-20140814/debian/control 2020-02-06 01:14:09.0 +0200
+++ micro-httpd-20140814/debian/control 2024-04-29 10:01:15.0 +0300
@@ -2,7 +2,7 @@
 Section: httpd
 Priority: optional
 Maintainer: Sudip Mukherjee 
-Build-Depends: debhelper-compat (= 12)
+Build-Depends: debhelper-compat (= 13)
 Standards-Version: 4.5.0
 Rules-Requires-Root: no
 Vcs-Browser: https://github.com/sudipm-mukherjee/micro-httpd.git
@@ -11,7 +11,7 @@
 
 Package: micro-httpd
 Architecture: any
-Depends: ${misc:Depends}, ${shlibs:Depends}, openbsd-inetd | inet-superserver 
| micro-inetd | netcat-traditional | systemd-sysv
+Depends: update-inetd | inet-superserver | openbsd-inetd | inetutils-inetd | 
rlinetd | xinetd, ${misc:Depends}, ${shlibs:Depends}
 Suggests: micro-proxy
 Provides: httpd
 Description: really small HTTP server
diff -Nru micro-httpd-20140814/debian/micro-httpd.lintian-overrides 
micro-httpd-20140814/debian/micro-httpd.lintian-overrides
--- micro-httpd-20140814/debian/micro-httpd.lintian-overrides   2020-02-06 
01:14:09.0 +0200
+++ micro-httpd-20140814/debian/micro-httpd.lintian-overrides   2024-04-29 
09:59:40.0 +0300
@@ -1,3 +1,3 @@
 # Using var/www/html/ as a new default document root
 # See #730372 and https://lists.debian.org/debian-devel/2012/04/msg00301.html
-micro-httpd: dir-or-file-in-var-www var/www/html/
+dir-or-file-in-var-www *var/www/html/*
diff -Nru micro-httpd-20140814/debian/micro-httpd@.service 
micro-httpd-20140814/debian/micro-httpd@.service
--- micro-httpd-20140814/debian/micro-httpd@.service2021-10-14 
16:02:47.0 +0300
+++ micro-httpd-20140814/debian/micro-httpd@.service2024-04-29 
09:38:36.0 +0300
@@ -7,3 +7,4 @@
 Group=www-data
 ExecStart=-/usr/sbin/micro-httpd /var/www/html
 StandardInput=socket
+StandardError=journal

Bug#1027978: micro-httpd: sends invalid HTTP when listing unreadable directories

[Martin-Éric Racine]

On Thu, 05 Jan 2023 13:08:45 + Vincent Duvert  wrote:
> When micro-httpd tries to list the contents of a directory but fails (if the
> directory is not readable, for instance), an invalid HTTP response is 
> returned:
>
> > GET /.well-known/ HTTP/1.0
> >
> < scandir: Permission denied
> < HTTP/1.0 200 Ok
> < Server: micro_httpd
> < ...
>
> Looking at the source code, micro-httpd calls perror( "scandir" ); after
> sending the HTTP headers, but due to standard output buffering, the error
> message ends up being sent first.
>
> An easy fix is to change micro-httpd@.service so micro-httpd's standard error
> is sent to the logs instead of the connection socket:
>
> [Service]
> StandardError=journal

I can implement this in an NMU.

> A more complete fix would be to move the call to scandir (line 119) just 
> before
> the call to send_headers(200, ...) (line 108), and to call send_error if 
> scandir
> fails.

This one needs to be sent to upstream.

If you do so, please take the opportunity to ask him to consider using
e.g. micro-httpd_2024-04-29.tar.xz as his tarball name. Tracking dates
in ISO format is a lot easier to implement than e.g. 14Aug2014.

Martin-Éric

Bug#1038882: proposal: dhcpcd-base as standard DHCP client starting with Trixie

[Martin-Éric Racine]

ma 11. maalisk. 2024 klo 7.02 Martin-Éric Racine
(martin-eric.rac...@iki.fi) kirjoitti:
>
> ma 11. maalisk. 2024 klo 1.29 Bernd Zeimetz (be...@bzed.de) kirjoitti:
> > On Mon, 2023-06-19 at 13:54 +0300, Martin-Éric Racine wrote:
> > > I hereby propose bin:dhcpcd-base:
> > >
> > > 1) already supported by ifupdown.
> > > 2) dual stack (DHCPv4, Bonjour, RA, DHCPv6 with PD) with privilege
> > > separation.
> > > 3) writes both IPv4 and IPv6 name servers to /etc/resolv.conf
> > > 4) supports /etc/resolv.conf.head and /etc/resolv.conf.tail
> > > 5) a mere inet line in /etc/network/interfaces is sufficient to
> > > configure both stacks.
> > >
> >
> > why not switch to systemd-networkd + networkmanager for gui installs?
>
> NM already is pulled by most desktop environments.
>
> Meanwhile a bare minimal system needs a non-GUI solution and swaping
> which DHCP client gets pulled by ifupdown is the simplest, least
> disruptive way of accomplishing this.

This bug is almost one year old. Are we going ahead with this or not?

Martin-Éric

Bug#1069870: linux-image-6.7.7-686-pae: please enable i915 mtl_* modules

[Martin-Éric Racine]

Package: src:linux
Version: 6.7.7-1
Severity: normal


W: Possible missing firmware /lib/firmware/i915/mtl_gsc_1.bin for module i915
W: Possible missing firmware /lib/firmware/i915/mtl_huc_gsc.bin for module i915
W: Possible missing firmware /lib/firmware/i915/mtl_guc_70.bin for module i915


-- System Information:
Debian Release: trixie/sid
  APT prefers testing-debug
  APT policy: (500, 'testing-debug'), (500, 'testing')
Architecture: i386 (i686)

Kernel: Linux 6.7.7-686-pae (SMP w/1 CPU thread; PREEMPT)
Kernel taint flags: TAINT_WARN
Locale: LANG=fi_FI.UTF-8, LC_CTYPE=fi_FI.UTF-8 (charmap=UTF-8), LANGUAGE=fi:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages linux-image-6.7.7-686-pae depends on:
ih  initramfs-tools [linux-initramfs-tool]  0.142
ii  kmod31+20240202-2
ii  linux-base  4.9

Versions of packages linux-image-6.7.7-686-pae recommends:
ii  apparmor 3.0.13-2
ii  firmware-linux-free  20200122-4

Versions of packages linux-image-6.7.7-686-pae suggests:
pn  debian-kernel-handbook  
ii  grub-pc 2.12-2~deb13u1
pn  linux-doc-6.7   

Versions of packages linux-image-6.7.7-686-pae is related to:
ii  firmware-amd-graphics 20230625-2
pn  firmware-atheros  
pn  firmware-bnx2 
pn  firmware-bnx2x
pn  firmware-brcm80211
pn  firmware-cavium   
pn  firmware-intel-sound  
pn  firmware-intelwimax   
pn  firmware-ipw2x00  
pn  firmware-ivtv 
ii  firmware-iwlwifi  20230625-2
pn  firmware-libertas 
ii  firmware-linux-nonfree20230625-2
ii  firmware-misc-nonfree 20230625-2
pn  firmware-myricom  
pn  firmware-netxen   
pn  firmware-qlogic   
ii  firmware-realtek  20230625-2
pn  firmware-samsung  
pn  firmware-siano
pn  firmware-ti-connectivity  
pn  xen-hypervisor

-- no debconf information

Bug#1069599: dhcpcd: isolation-machine autopkgtest fails: Unit systemd-timesyncd.service not found.

[Martin-Éric Racine]

su 21. huhtik. 2024 klo 14.59 Martin-Éric Racine
(martin-eric.rac...@iki.fi) kirjoitti:
>
> su 21. huhtik. 2024 klo 14.12 Paul Gevers (elb...@debian.org) kirjoitti:
> >
> > Source: dhcpcd
> > Version: 1:10.0.6-1
> > Severity: important
> > User: debian...@lists.debian.org
> > Usertags: isolation-machine
> >
> > Dear maintainer(s),
> >
> > Your package has an autopkgtest, great. I recently added support for
> > isolation-machine tests on ci.debian.net for amd64 and added your
> > package to the list to use that. However, it fails. Can you please
> > investigate the situation and fix it? I copied some of the output at the
> > bottom of this report.
>
> [...]
>
> >   29s autopkgtest [11:03:42]: test timesyncd-ntp-servers-from-dhcp:
> > [---
> >   30s Preparing virtual interfaces...
> >   30s Actual changes:
> >   30s tx-checksum-ip-generic: off
> >   30s tx-tcp-segmentation: off [not requested]
> >   30s tx-tcp-ecn-segmentation: off [not requested]
> >   30s tx-tcp-mangleid-segmentation: off [not requested]
> >   30s tx-tcp6-segmentation: off [not requested]
> >   30s tx-checksum-sctp: off
> >   30s Preparing dnsmasq configuration...
> >   35s Obtaining network configuration for veth1 via dhcp...
> >   37s RA from non local address fdae:9322:f1cc::1
> >   43s Failed to reload-or-try-restart systemd-timesyncd.service: Unit
> > systemd-timesyncd.service not found.
> >   43s Failed to reload-or-try-restart systemd-timesyncd.service: Unit
> > systemd-timesyncd.service not found.
> >   48s Check if the NTP server is made available to daemon...Failed to
> > parse bus message: No route to host
> >   49s autopkgtest [11:04:02]: test timesyncd-ntp-servers-from-dhcp:
> > ---]
>
> That service unit is provided by systemd-timesyncd, which systemd
> recommends. Basically, unless your testing environment explicitly
> installs another package providing time-daemon, this shouldn't happen,
> since systemd would have pulled systemd-timesyncd by default.

Anyhow, no harm done. The following commit should fix it:

https://salsa.debian.org/debian/dhcpcd/-/commit/55e588b0d7561c697f3fedfddef3feeb6c8b34b9

Martin-Éric

Bug#1069599: dhcpcd: isolation-machine autopkgtest fails: Unit systemd-timesyncd.service not found.

[Martin-Éric Racine]

su 21. huhtik. 2024 klo 14.12 Paul Gevers (elb...@debian.org) kirjoitti:
>
> Source: dhcpcd
> Version: 1:10.0.6-1
> Severity: important
> User: debian...@lists.debian.org
> Usertags: isolation-machine
>
> Dear maintainer(s),
>
> Your package has an autopkgtest, great. I recently added support for
> isolation-machine tests on ci.debian.net for amd64 and added your
> package to the list to use that. However, it fails. Can you please
> investigate the situation and fix it? I copied some of the output at the
> bottom of this report.

[...]

>   29s autopkgtest [11:03:42]: test timesyncd-ntp-servers-from-dhcp:
> [---
>   30s Preparing virtual interfaces...
>   30s Actual changes:
>   30s tx-checksum-ip-generic: off
>   30s tx-tcp-segmentation: off [not requested]
>   30s tx-tcp-ecn-segmentation: off [not requested]
>   30s tx-tcp-mangleid-segmentation: off [not requested]
>   30s tx-tcp6-segmentation: off [not requested]
>   30s tx-checksum-sctp: off
>   30s Preparing dnsmasq configuration...
>   35s Obtaining network configuration for veth1 via dhcp...
>   37s RA from non local address fdae:9322:f1cc::1
>   43s Failed to reload-or-try-restart systemd-timesyncd.service: Unit
> systemd-timesyncd.service not found.
>   43s Failed to reload-or-try-restart systemd-timesyncd.service: Unit
> systemd-timesyncd.service not found.
>   48s Check if the NTP server is made available to daemon...Failed to
> parse bus message: No route to host
>   49s autopkgtest [11:04:02]: test timesyncd-ntp-servers-from-dhcp:
> ---]

That service unit is provided by systemd-timesyncd, which systemd
recommends. Basically, unless your testing environment explicitly
installs another package providing time-daemon, this shouldn't happen,
since systemd would have pulled systemd-timesyncd by default.

Martin-Éric

Bug#1068293: flowblade: 2.14 fails to launch due to missing app.py

[Martin-Éric Racine]

Solving this requires adding Depends: python3-libusb1

Bug#1068293: flowblade: 2.14 fails to launch due to missing app.py

[Martin-Éric Racine]

As see in 
:

"Distro packagers, please see info on the needed configuration file
addition (/etc/udev/rules.d/90-flowblade.rules) described in the link
to docs above."

Martin-Éric

Bug#1068293: flowblade: 2.14 fails to launch due to missing app.py

[Martin-Éric Racine]

Package: flowblade
Version: 2.14.0.1-1
Severity: important

$ flowblade 
FLOWBLADE MOVIE EDITOR 2.14.0.1
---
Launch script dir: /usr/bin
Running from installation...
modules path: /usr/share/flowblade/Flowblade
MLT found, version: 7.12.0
Failed to import module app.py to launch Flowblade!
ERROR: No module named 'usb1'
Installation was assumed to be at: /usr/share/flowblade/Flowblade


-- System Information:
Debian Release: 12.5
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 
'stable-debug'), (500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 6.1.0-18-amd64 (SMP w/4 CPU threads; PREEMPT)
Locale: LANG=fi_FI.UTF-8, LC_CTYPE=fi_FI.UTF-8 (charmap=UTF-8), LANGUAGE=fi:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages flowblade depends on:
ii  ffmpeg7:5.1.4-0+deb12u1
ii  frei0r-plugins1.8.0-1+b1
ii  gir1.2-gdkpixbuf-2.0  2.42.10+dfsg-1+b1
ii  gir1.2-glib-2.0   1.74.0-3
ii  gir1.2-gtk-3.03.24.38-2~deb12u1
ii  gir1.2-pango-1.0  1.50.12+ds-1
ii  gmic  2.9.4-4+b4
ii  libmlt-data   7.12.0-1
ii  librsvg2-common   2.54.7+dfsg-1~deb12u1
ii  python3   3.11.2-1+b1
ii  python3-cairo 1.20.1-5+b1
ii  python3-dbus  1.3.2-4+b1
ii  python3-distutils 3.11.2-3
ii  python3-gi3.42.2-3+b1
ii  python3-gi-cairo  3.42.2-3+b1
ii  python3-mlt   7.12.0-1+b1
ii  python3-numpy 1:1.24.2-1
ii  python3-opencv4.6.0+dfsg-12
ii  python3-pil   9.4.0-1.1+b1
ii  swh-plugins   0.4.17-2

flowblade recommends no packages.

flowblade suggests no packages.

-- no debconf information

Bug#1067909: libc-devtools: please relax Depends on libgd3

[Martin-Éric Racine]

pe 29. maalisk. 2024 klo 1.01 Aurelien Jarno (aure...@debian.org) kirjoitti:
>
> On 2024-03-28 20:35, Martin-Éric Racine wrote:
> > Package: libc-devtools
> > Severity: normal
> >
> > libgd3 pulls an excessive amount of dependencies, including fonts. It would 
> > thus be desirable to downgrade it to a mere Recommends.
> >
>
> The /usr/bin/memusagestat binary is linked against libgd3, so we can't just
> changes the Depends to a Recommends.

Noted.

Alternately, dropping libc-dev-bin's Recommends on libc-devtools to a
mere Suggests would accomplish the same thing. The key idea here is to
avoid pulling fonts and tons of graphics libraries in.

Martin-Éric

Bug#1067909: libc-devtools: please relax Depends on libgd3

[Martin-Éric Racine]

Package: libc-devtools
Severity: normal

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

libgd3 pulls an excessive amount of dependencies, including fonts. It would 
thus be desirable to downgrade it to a mere Recommends.

Martin-Éric

- -- System Information:
Debian Release: trixie/sid
  APT prefers unstable
  APT policy: (900, 'unstable')
Architecture: i386 (x86_64)

Kernel: Linux 6.1.0-18-amd64 (SMP w/4 CPU threads; PREEMPT)
Locale: LANG=fi_FI.UTF-8, LC_CTYPE=fi_FI.UTF-8 (charmap=UTF-8), LANGUAGE=fi:en
Shell: /bin/sh linked to /usr/bin/dash
Init: unable to detect

Versions of packages libc-devtools depends on:
ii  libc6   2.37-15.1
pn  libgd3  

Versions of packages libc-devtools recommends:
ii  manpages  6.05.01-1
ii  manpages-dev  6.05.01-1

libc-devtools suggests no packages.

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEyJACx3qL7GpObXOQrh+Cd8S017YFAmYFuH0ACgkQrh+Cd8S0
17ayNw/+KowbskIoaRqYApa3kOPNWPtLD/rvbEOISdjvJKBz9chs7cYImdtQdd7h
9Z+R6U9AGnxrOTUXxO2a1lfGtpgxVFMemiHIN361zV3kA7IdqX62e1kvAT2dympy
Gselwg1Jr5PULghzDAdBcYlZ82S7roYnbh7lhd0vcS90xjCatL4Hk7+/bwCgISvB
2wgICAeXV5YrYxx4pX8FfeLUfGbsCRxzW0sKnG61a+RxGRykP5p+hiccSG2IACyL
Wks1Jymf5jLO3Qk3hzYykN3iCikx/dM6wMscDXp36olD+kliD+0I6YDAFHXFIcrb
FeL97pqFvNhoz8Q81IbML2BfZfMAEoAlSp5ROqqxyGuqo9BYzc9tDUkwaacPEJCY
9R2sAB1SHgwObOITueTRynfm1kIbemwi/ydiOBT7jjnYNTV3I52DdAdRaqqhSeUM
hbCxk960xqF/v2IcMjc92wNepwI8dj4FGmQPgGwJ3JYuVa4y5IncFhf3N93KK00V
bduJya6sT/2vR0PtsLnXnAQzh71SyEnqPGGvgQ8031JJ5zivqHZuLx0Huf/ZcjWY
CMBmTI2WRByOwqGgA3kpSh5fc7gozb2to/XHTuS7vWFS03KNwZTe+oacHJaVEYTW
rL04tKeCZD5t4e4rvrjKABFgheH/Q+TQPS0VfA2NrSYk76qfIeY=
=mkEr
-END PGP SIGNATURE-

Bug#1067900: e2fsprogs: incorrect dependencies on 32-bit archs

[Martin-Éric Racine]

Package: e2fsprogs
Version: 1.47.0-2.4
Severity: important
X-Debbugs-Cc: Helmut Grohne 

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

The following packages have unmet dependencies:
 e2fsprogs : PreDepends: libcom-err2 (>= 1.43.9)
 PreDepends: libss2 (>= 1.38)
E: Error, pkgProblemResolver::Resolve generated breaks, this may be caused by 
held packages.

The cause:

Pre-Depends: libblkid1 (>= 2.36), libc6 (>= 2.34), libcom-err2 (>= 1.43.9), 
libext2fs2t64 (= 1.47.0-2.4), libss2 (>= 1.38), libuuid1 (>= 2.16)

Basically, 32-bit builds incorrectly depend on libcom-err2 instead of 
libcom-err2t64.

Martin-Éric

- -- System Information:
Debian Release: trixie/sid
  APT prefers unstable
  APT policy: (900, 'unstable')
Architecture: i386 (x86_64)

Kernel: Linux 6.1.0-18-amd64 (SMP w/4 CPU threads; PREEMPT)
Locale: LANG=fi_FI.UTF-8, LC_CTYPE=fi_FI.UTF-8 (charmap=UTF-8), LANGUAGE=fi:en
Shell: /bin/sh linked to /usr/bin/dash
Init: unable to detect

Versions of packages e2fsprogs depends on:
ii  libblkid1 2.39.3-11
ii  libc6 2.37-15.1
ii  libcom-err2t64 [libcom-err2]  1.47.0-2.3+b1
ii  libext2fs2t64 1.47.0-2.4
ii  libss21.47.0-2.4
ii  libuuid1  2.39.3-11
ii  logsave   1.47.0-2.4

Versions of packages e2fsprogs recommends:
ii  e2fsprogs-l10n  1.47.0-2.4

Versions of packages e2fsprogs suggests:
pn  e2fsck-static  
pn  fuse2fs
pn  gpart  
pn  parted 

- -- no debconf information

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEyJACx3qL7GpObXOQrh+Cd8S017YFAmYFkZUACgkQrh+Cd8S0
17bK/BAAjBS9k79q6TuzUgdlHN9D3aITCJntMIXcgGMK887+z9SZvVZGvXLbCO0b
OsfItwEVcy3KpJXek731jHH2FGDfsOC+UQ4zTsDtujHHCB5qzJL2l8ZvzTUX0Vih
kXQOsQ53BZil32dYOXf/fc8m9FPca9sJkHGLBuw1N2drD7Za320B3T9aLmE0bbg+
TZN+BBDA1q8Pket9a515L6hdam8Kyb0MQdru4QxbNlq5pcpiUEBNO6DCeBS+/42w
FMNVqiXHs37dTErWmPJk6lA44MANdYPTcpKWZpHtE85AwlRFk11fxPROFyxQOSVp
mtDVThnEwlNKTbXaNjxH8fOMY6MqR78VoRv/rETQ8xh3z1PMJZtwC0Rp9bQ2JDG/
WHrNgQgbUVbTqVD2kZEPTTwRavu43pnv1QFhlBiksHpwbBi7tbBqCtizPYcVX5Hf
fQoBZgl2AcZgY8W4+Eto5wjP7p+R3kJr7VtBZ28d5rGdqYq4uSeV6rLJEK5LuUby
/mu4UhWgtSvGv0aMsPujpXGhrLfn2xoBOld/G5hsciwZd7vzF4uGlV/w2JZzJ+QR
+LcqdW1CJ4/6XetmSv2XL/W5olFhgpq9kZ1pdj8gbFNPBkjySH2T6s2Aj1wjankw
EAWAK5Jaguuc3lEwguidioHSh6WPDbjINwE7ESIDH/WvoYV3Ovk=
=yREi
-END PGP SIGNATURE-

Bug#872587: Document the Protected field

[Martin-Éric Racine]

ke 27. maalisk. 2024 klo 14.00 Andrey Rakhmatullin (w...@debian.org) kirjoitti:
>
> On Wed, Mar 27, 2024 at 01:29:50PM +0200, Martin-Éric Racine wrote:
> > > The documentation from deb-control(5) is:
> > >
> > > Protected: yes|no
> > > This field is usually only needed when the answer is yes.  It denotes
> > > a package that is required mostly for proper booting of the system or
> > > used for custom system-local meta-packages.  dpkg(1) or any other
> > > installation tool will not allow a Protected package to be removed (at
> > > least not without using one of the force options).
> > >
> > > It's probably also worth noting the parenthetical comment in the
> > > documentation of Essential:
> > >
> > > Essential: yes|no
> > > This field is usually only needed when the answer is yes.  It denotes
> > > a package that is required for the packaging system, for proper
> > > operation of the system in general or during boot (although the latter
> > > should be converted to Protected field instead).  dpkg(1) or any other
> > > installation tool will not allow an Essential package to be removed
> > > (at least not without using one of the force options).
> >
> > I'm still not sure that I inderstand the difference between those two.
> > They seem to accomplish the same thing. Did I miss something?
> Per my understanding which may be flawed:
>
> "Essential: yes" are always installed. Tools and dependencies assume they
> are installed.  Bootstrapping tools install them implicitly. Package
> management tools refuse to remove them.
>
> "Protected: yes" are nothing like that. Package management tools refuse to
> remove them and that's all.

Thanks. This sounds much clearer already. In that case, the above
deb-control(5) needs a much better phrasing. Something like:

Protected: yes|no
This field prevents a package from getting auto-removed by dpkg
without using one of the force options. It is intended for custom
local packages not meant for upload to the Debian repository.

Essential: yes|no
This field prevents a package from getting auto-removed by dpkg
without using one of the force options. It also makes debootstrap and
other similar tools force-install them. Maintainers must request
approval from the debian-devel mailing list before uploading any
package with the Essential field set to the Debian repository. See
Essential packages (Section 3.8) in the Debian Policy Manual for
details.

Martin-Éric

Bug#872587: Document the Protected field

[Martin-Éric Racine]

On Mon, 11 Sep 2023 21:27:09 -0700 Russ Allbery  wrote:
> Control: retitle -1 Document the Protected field
>
> Adam Borowski  writes:
> > On Fri, Aug 18, 2017 at 02:28:22PM -0700, Sean Whitton wrote:
>
> >> Do you have any idea how long we can expect to wait until dpkg supports
> >> the field?  I would suggest that we wait until dpkg has defined
> >> behaviour for the field, as it will make documenting it much easier.
> >> It will also allow us to be more confident that there is no serious
> >> disagreement about the purpose of the field.
>
> > Right, let's have dpkg maintainers tell us what they think.
>
> >> I couldn't find a bug against dpkg, but if there is one, it should
> >> probably be set to block this bug.
>
> > 872587 < 872589, I filed the Policy one first.  Block added.
>
> Per the resolution of #872589, this was implemented as the Protected field
> instead.  Retitling the bug accordingly.
>
> The documentation from deb-control(5) is:
>
> Protected: yes|no
> This field is usually only needed when the answer is yes.  It denotes
> a package that is required mostly for proper booting of the system or
> used for custom system-local meta-packages.  dpkg(1) or any other
> installation tool will not allow a Protected package to be removed (at
> least not without using one of the force options).
>
> It's probably also worth noting the parenthetical comment in the
> documentation of Essential:
>
> Essential: yes|no
> This field is usually only needed when the answer is yes.  It denotes
> a package that is required for the packaging system, for proper
> operation of the system in general or during boot (although the latter
> should be converted to Protected field instead).  dpkg(1) or any other
> installation tool will not allow an Essential package to be removed
> (at least not without using one of the force options).

I'm still not sure that I inderstand the difference between those two.
They seem to accomplish the same thing. Did I miss something?

It should also be noted that, as of version 2.117.0, Lintian still
gives a warning whenever a binary target has the Protected field set.

Martin-Éric

Bug#1065312: RM: deborphan -- ROM; missing too many dpkg features, thus broken and unreliable

[Martin-Éric Racine]

On Tue, 12 Mar 2024 10:22:25 +0200
=?UTF-8?Q?Martin=2D=C3=89ric_Racine?= 
wrote:
> On Mon, 11 Mar 2024 15:18:44 +0100 Chris Hofstaedtler  wrote:
> > On Sat, Mar 02, 2024 at 03:16:22PM +0100, Chris Hofstaedtler wrote:
> > > Given the C codebase and lack of any patches so far I do not see that
> > > deborphan will ever get these features, and we have other tools
> > > available that work, do not mess with dpkg internals and are actually
> > > maintained.
> >
> > As people have asked so nicely, and not at all demanding, entitled
> > or otherwise bossy in this bug report, I've checked around a bit how
> > APT provides deborphan's functionality today.
> >
> > As you all know, apt keeps track of when a package was installed
> > manually or automatically. This is mostly equivalent to manually
> > maintaining a deborphan keep file, but automated. apt-mark can be
> > used to manipulate the manually-installed state.
> >
> > On top of that, apt-patterns(7) documents how to select packages,
> > including on sections, installed status, manually-installed status.
> > It can also used to select based on package names and regexes.
> >
> > Thus, a good approximation of the default deborphan functionality
> > (no additional options passed) is:
> >
> > $ apt-mark auto '~i !~M 
> > (~slibs|~soldlibs|~slibdevel|~sintrospection|~sdebug)'
> > possibly followed by
> > $ apt autoremove
> >
> > If you're using --guess- or --guess-section with
> > deborphan, you can copy the regex lists from deborphans source. A
> > lot of them are however outdated and wrong, so you were already in
> > "living dangerously" territory there.
> >
> > And that's it. deborphan does not do any magic and you can do all of
> > it with apt.
>
> Thanks for making the effort to investigate possible substitutes.
>
> However, those are all approximations, not a direct substitute. All of
> these methods essentially require whitelisting, blacklisting or
> auto-marking packages for future processing. Meanwhile, deborphan
> makes good guesses on the fly. Yes, its methods are kinda outdated,
> its misses support for some of the recent dpkg bells and whistles, but
> it still does a good enough job for most cases, as attested by its
> popularity contest rating just below 10k.
>
> Sorry, I really think that the correct action is to orphan the
> package, not remove it.

Another issue I've run into to try and replace deborphan with some
apt-mark recipe: apt-mark's regex syntax is not documented. The man
page merely lists the commands and options available.

For instance, I have no idea how you came up with the above regex
recipe, or how I would tell apt-mark to never mark as "auto" anything
with a priority important or higher. At best, I can tell that whatever
follows each |s lists in the above recipe is a Debian repository
section.

Martin-Éric

Bug#1066809: e2fsprogs: dependency loop libss2t64 versus libss2

[Martin-Éric Racine]

Package: e2fsprogs
Version: 1.47.0-2.4
Severity: important

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

The latest upload introduces a dependency loop between libss2t64 versus libss2 
which also results in the removal of e2fsprogs-l10n.

Martin-Éric

- -- System Information:
Debian Release: trixie/sid
  APT prefers unstable
  APT policy: (900, 'unstable')
Architecture: i386 (x86_64)

Kernel: Linux 6.1.0-18-amd64 (SMP w/4 CPU threads; PREEMPT)
Locale: LANG=fi_FI.UTF-8, LC_CTYPE=fi_FI.UTF-8 (charmap=UTF-8), LANGUAGE=fi:en
Shell: /bin/sh linked to /usr/bin/dash
Init: unable to detect

Versions of packages e2fsprogs depends on:
ii  libblkid1 2.39.3-10
ii  libc6 2.37-15.1
ii  libcom-err2t64 [libcom-err2]  1.47.0-2.3+b1
ii  libext2fs2t64 1.47.0-2.4
ii  libss21.47.0-2.4
ii  libuuid1  2.39.3-10
ii  logsave   1.47.0-2.4

Versions of packages e2fsprogs recommends:
pn  e2fsprogs-l10n  

Versions of packages e2fsprogs suggests:
pn  e2fsck-static  
pn  fuse2fs
pn  gpart  
pn  parted 

- -- no debconf information

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEyJACx3qL7GpObXOQrh+Cd8S017YFAmXx+lwACgkQrh+Cd8S0
17aasA//e73csg+hxm7SWDyHbEzkxrLP7WSrul3cUJitfJg/TgMBV4f7s2fLMzQo
4793rIOa7mS7eWuzUo9KmzC9o24koe6pG99cPv+C/MJwArrGEhDD9UeHVxs7J15I
5tjGkv1wELAu9nxEHTxXAU5ItNtkOjJiYyjb5JbYJq44yXySIkYTaixAvfYH/v1S
QHg7W1c39/nWv+PBgxXMKfGOSB9zWbi8mSlq/tvAYKv+r1hsACfE4P/BPQ05r6YB
8w9i/MFq092AI6S3+sCJrVo+1ru1YhGwr+Fg4UcXV6hLlFLogA8AtNLCIQNmwLcs
H8xZgbxEa3aybjY18sQGVgxEdbX7y+dGqFdE5mUCP7hykI6da2JiLZnN3dyJ/k8Y
H5Ubbh8euA0awC351OyCGC+QUIrgMojOJ5qFoWxnx3iuqQeSC5lULKDbjN6K2bpR
Ks7I2mUaw9UvonXaWJGMQtnAlXa0oISGrDYQMqavUy2us6mgrbfgC5IhBuL9fIu7
2ysaBK6ljK5i58oVRcjeJaJ1iAWZBEa3SIfbyakLYW8pIi8H7Y1D0Mp3mXfuZFAX
XKoCenJZmJaKIqGjDNR/+Nr62B/dCEqpuB/F6V1ptqd+vuYyMWveG2BC9rsL5Is9
3xGYDucM0+KogEsyA6vDuWeSCLoBMnvPR8Qd1nGwQowN3QhRLuY=
=1zKm
-END PGP SIGNATURE-

Bug#1065312: RM: deborphan -- ROM; missing too many dpkg features, thus broken and unreliable

[Martin-Éric Racine]

On Mon, 11 Mar 2024 15:18:44 +0100 Chris Hofstaedtler  wrote:
> On Sat, Mar 02, 2024 at 03:16:22PM +0100, Chris Hofstaedtler wrote:
> > Given the C codebase and lack of any patches so far I do not see that
> > deborphan will ever get these features, and we have other tools
> > available that work, do not mess with dpkg internals and are actually
> > maintained.
>
> As people have asked so nicely, and not at all demanding, entitled
> or otherwise bossy in this bug report, I've checked around a bit how
> APT provides deborphan's functionality today.
>
> As you all know, apt keeps track of when a package was installed
> manually or automatically. This is mostly equivalent to manually
> maintaining a deborphan keep file, but automated. apt-mark can be
> used to manipulate the manually-installed state.
>
> On top of that, apt-patterns(7) documents how to select packages,
> including on sections, installed status, manually-installed status.
> It can also used to select based on package names and regexes.
>
> Thus, a good approximation of the default deborphan functionality
> (no additional options passed) is:
>
> $ apt-mark auto '~i !~M (~slibs|~soldlibs|~slibdevel|~sintrospection|~sdebug)'
> possibly followed by
> $ apt autoremove
>
> If you're using --guess- or --guess-section with
> deborphan, you can copy the regex lists from deborphans source. A
> lot of them are however outdated and wrong, so you were already in
> "living dangerously" territory there.
>
> And that's it. deborphan does not do any magic and you can do all of
> it with apt.

Thanks for making the effort to investigate possible substitutes.

However, those are all approximations, not a direct substitute. All of
these methods essentially require whitelisting, blacklisting or
auto-marking packages for future processing. Meanwhile, deborphan
makes good guesses on the fly. Yes, its methods are kinda outdated,
its misses support for some of the recent dpkg bells and whistles, but
it still does a good enough job for most cases, as attested by its
popularity contest rating just below 10k.

Sorry, I really think that the correct action is to orphan the
package, not remove it.

Martin-Éric

Bug#1065312: Re: Bug#1065312: RM: deborphan -- ROM; missing too many dpkg features, thus broken and unreliable

[Martin-Éric Racine]

On Sun, 10 Mar 2024 15:27:21 + Scott Kitterman  wrote:
>
>
> On March 10, 2024 3:23:32 PM UTC, "Martin-Éric Racine" 
>  wrote:
> >On Sat, 2 Mar 2024 18:40:13 +0100 Chris Hofstaedtler  wrote:
> >> * Christoph Biedl  [240302 17:02]:
> >> > Chris Hofstaedtler wrote...
> >> >
> >> > > please remove deborphan. It is stuck, featurewise, in a very old time
> >> > > and does not support many currently available dpkg features properly
> >> > > (multi-arch, versioned provides, etc).
> >> >
> >> > FWIW, deborphan is part of my regular workflow, and while you claim
> >> > it has defects, it works for me pretty well.
> >>
> >> It works "well" if you use it in very limited usecases, yes (like I
> >> did). It doesn't seem to work well for a lot of people using more of
> >> the "features" it has.
> >
> >Just because it doesn't work for everyone is not a remotely good
> >enough reason to ask for its removal. It works for most people. don't
> >break it for them.
> >
> >> The t64 transition will apparently make deborphan mostly useless in
> >> trixie.
> >>
> >> > [..]
> >> > So: What are the alternatives? How do they work? Are they a drop-in
> >> > replacment or do they introduce new dependencies? Are there feature that
> >> > will be no longer supported?
> >>
> >> release-notes recommends:
> >> https://www.debian.org/releases/stable/amd64/release-notes/ch-upgrading.en.html#removing-non-debian-packages
> >
> >Which has nothing to do with what was asked.
> >
> >> Some people seem to recommend debfoster.
> >
> >Which really doesn't provide similar functionality.
> >
> >> > Leaving users in the void about this is just bad style.
> >
> >I totally agree. Not wanting to maintain it is a shitty reason for
> >asking for its removal. If you don't wanna maintain is, just orphan
> >it.
>
>
> It's really a maintainer call if that's appropriate.  So far no one has 
> jumped up to ask if they can take over the package.

Please. It's not like anyone was ever given the opportunity by
noticing a recently orphaned package or a blog post about it either.

Martin-Éric

Bug#1038882: proposal: dhcpcd-base as standard DHCP client starting with Trixie

[Martin-Éric Racine]

ma 11. maalisk. 2024 klo 1.29 Bernd Zeimetz (be...@bzed.de) kirjoitti:
> On Mon, 2023-06-19 at 13:54 +0300, Martin-Éric Racine wrote:
> > I hereby propose bin:dhcpcd-base:
> >
> > 1) already supported by ifupdown.
> > 2) dual stack (DHCPv4, Bonjour, RA, DHCPv6 with PD) with privilege
> > separation.
> > 3) writes both IPv4 and IPv6 name servers to /etc/resolv.conf
> > 4) supports /etc/resolv.conf.head and /etc/resolv.conf.tail
> > 5) a mere inet line in /etc/network/interfaces is sufficient to
> > configure both stacks.
> >
>
> why not switch to systemd-networkd + networkmanager for gui installs?

NM already is pulled by most desktop environments.

Meanwhile a bare minimal system needs a non-GUI solution and swaping
which DHCP client gets pulled by ifupdown is the simplest, least
disruptive way of accomplishing this.

Martin-Éric

Bug#1058451: ntpsec: FTBFS [Hurd] change Build-Depends: systemd to [linux-any]

[Martin-Éric Racine]

ma 11. maalisk. 2024 klo 5.44 Richard Laager (rlaa...@debian.org) kirjoitti:
>
> I think, but am not sure, that this is now functionally a duplicate of
> #1060506. That one tells me to change it from systemd to systemd-dev
> because:
>
>  Since systemd_253-2 [1], these two pkgconfig files have been split
>  into a separate package named systemd-dev. This package is arch:all,
>  so even available on non-Linux architectures, which will simplify
>  the installation of upstream provided service files / udev rules.
>
> I have made that change. If that is NOT sufficient, please let me know
> and I'll adjust again.

Yes, this probably accomplished the same. We'll know for sure once the
buildd's have caught up with the upload.

Thanks!
Martin-Éric

Bug#1065892: gthumb: please package upstream 3.12.6

[Martin-Éric Racine]

Package: gthumb
Version: 3:3.12.4-1~bpo12+1
Severity: wishlist

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Upstream just released 3.12.6 which contains a few important bugfixes.
Could you please package it?
Thanks!

Martin-Éric

- -- System Information:
Debian Release: 12.5
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 
'stable-debug'), (500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 6.1.0-18-amd64 (SMP w/4 CPU threads; PREEMPT)
Locale: LANG=fi_FI.utf8, LC_CTYPE=fi_FI.utf8 (charmap=UTF-8), LANGUAGE=fi:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages gthumb depends on:
ii  gsettings-desktop-schemas   43.0-1
ii  gthumb-data 3:3.12.4-1~bpo12+1
ii  libbrasero-media3-1 3.12.3-2
ii  libc6   2.36-9+deb12u4
ii  libcairo2   1.16.0-7
ii  libcolord2  1.4.6-2.2
ii  libexiv2-27 0.27.6-1
ii  libgcc-s1   12.2.0-14
ii  libgdk-pixbuf-2.0-0 2.42.10+dfsg-1+b1
ii  libgl1-mesa-dri 22.3.6-1+deb12u1
ii  libglib2.0-02.74.6-2
ii  libgstreamer-plugins-base1.0-0  1.22.0-3+deb12u1
ii  libgstreamer1.0-0   1.22.0-2
ii  libgtk-3-0  3.24.38-2~deb12u1
ii  libheif11.15.1-1
ii  libjpeg62-turbo 1:2.1.5-2
ii  libjxl0.7   0.7.0-10
ii  liblcms2-2  2.14-2
ii  libpango-1.0-0  1.50.12+ds-1
ii  libpangocairo-1.0-0 1.50.12+ds-1
ii  libpng16-16 1.6.39-2
ii  libraw200.20.2-2.1
ii  librsvg2-2  2.54.7+dfsg-1~deb12u1
ii  libstdc++6  12.2.0-14
ii  libtiff64.5.0-6+deb12u1
ii  libwebp71.2.4-0.2+deb12u1
ii  libx11-62:1.8.4-2+deb12u2
ii  zlib1g  1:1.2.13.dfsg-1

gthumb recommends no packages.

gthumb suggests no packages.

- -- no debconf information

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEyJACx3qL7GpObXOQrh+Cd8S017YFAmXt8mwACgkQrh+Cd8S0
17bRQQ//Yx2q51W10c9jG7+f535sHjevAJJoXgL3bVKXXbihTBl4fvur2rk2m0kF
4Qo1jaoHX6xGiOcIzMSP1lNhKUlgnFGPQGESSKe4LQV6y//ERNLOL+KfEeed+NMy
yx3kTyXS+kAT3SHdmiuEV3IYWTI5IkUoQ9o2teU/fOCfUqH8MQYb5oFvz6vNIl5P
IxLKErlv/w01RO3PHNbKvXwbOMj2/xUWi3VxLxQ7e63szGNyEj/OoLFDnR6ilpJY
2DzbthAU8ITKwT9Tkccmz/f+yZAgA61eznjC1JUsNXusiK3+jMq9Sdp0kk+o8xpN
M/WDyQxaxgVVmGvaJnqqyrwnmofVg34K35txExvOCYEFY0c5hhKoS81pYHjqcEGc
jk3hRfbJtUVcuvnrgGQhFpuGxMtAvOh7dOaJOPkQBdfl/lwIjCwyPz29tsybXK3l
7HpGe+EYNtaxXZzeLd5S+vVHQURD1aI5PwIZ80WH80BkukSARe2kkBBoWHKETvuN
bxUSRHqvEh93K/2m/TXElPO9dDjYUeO/yYv6ASTesoxZQf1UgnhAQvKbWpLIOSJ3
JH7co/pjDWIMaPptPEXxEl3JP1uDNsqukfm+8692ld1wE2mlflNIGORgee62Sqre
stRqi/aNel4pezhyTKCMfjmbGtVtzdy42KwvOkkMNNZNpGCqdqQ=
=LO30
-END PGP SIGNATURE-

Bug#1038882: proposal: dhcpcd-base as standard DHCP client starting with Trixie

[Martin-Éric Racine]

su 10. maalisk. 2024 klo 18.54 Santiago Ruano Rincón
(santiag...@riseup.net) kirjoitti:
>
> Hi there,
>
> El 20/11/23 a las 19:44, Martin-Éric Racine escribió:
> > (non-subscriber - please keep me in CC)
> > On Sat, Nov 18, 2023 at 4:26 PM Martin-Éric Racine
> >  wrote:
> > >
> > > On Sat, Jul 22, 2023 at 2:55 PM Martin-Éric Racine
> > >  wrote:
> > > >
> > > > On Fri, Jul 7, 2023 at 12:55 PM Martin-Éric Racine
> > > >  wrote:
> > > > >
> > > > > On Thu, Jul 6, 2023 at 3:06 AM Santiago Ruano Rincón
> > > > >  wrote:
> > > > > >
> > > > > > El 22/06/23 a las 09:57, Santiago Ruano Rincón escribió:
> > > > > > > El 20/06/23 a las 08:29, Martin-Éric Racine escribió:
> > > > > > > > On Mon, Jun 19, 2023 at 9:11 PM Santiago Ruano Rincón
> > > > > > > >  wrote:
> > > > > > > > > El 19/06/23 a las 13:54, Martin-Éric Racine escribió:
> > > > > > > > > > Greetings,
> > > > > > > > > >
> > > > > > > > > > Seeing how the ISC DHCP suite has reached EOL upstream, now 
> > > > > > > > > > might be a
> > > > > > > > > > good time to re-visit Debian's choice of standard DHCP 
> > > > > > > > > > client shipping
> > > > > > > > > > with priority:important.
> > > > > > > > > >
> > > > > > > > > > I hereby propose bin:dhcpcd-base:
> > > > > > > > > >
> > > > > > > > > > 1) already supported by ifupdown.
> > > > > > > > > > 2) dual stack (DHCPv4, Bonjour, RA, DHCPv6 with PD) with 
> > > > > > > > > > privilege separation.
> > > > > > > > > > 3) writes both IPv4 and IPv6 name servers to 
> > > > > > > > > > /etc/resolv.conf
> > > > > > > > > > 4) supports /etc/resolv.conf.head and /etc/resolv.conf.tail
> > > > > > > > > > 5) a mere inet line in /etc/network/interfaces is 
> > > > > > > > > > sufficient to
> > > > > > > > > > configure both stacks.
> > > > > > > > > ...
> > > > > > > > >
> > > > > > > > > I agree that dhcpcd seems the best alternative to 
> > > > > > > > > isc-dhcp-client for
> > > > > > > > > the moment, and I'll make the relevant changes in ifupdown as 
> > > > > > > > > soon as I
> > > > > > > > > can. Josué, any thoughts?
> > > > > > > >
> > > > > > > > 1) As someone pointed out in the thread, the reason why
> > > > > > > > isc-dhcp-client had priority:important probably was to ensure 
> > > > > > > > that
> > > > > > > > debootstrap would pull it, since debootstrap ignores Recommends 
> > > > > > > > and
> > > > > > > > packages with a priority lower than standard.
> > > > > > > >
> > > > > > > > 2) However, as long as ifupdown explictly depends on a package, 
> > > > > > > > it can
> > > > > > > > also pull dependencies with a lower priority. Right now ifupdown
> > > > > > > > Recommends "isc-dhcp-client | dhcp-client" which debootstrap 
> > > > > > > > would
> > > > > > > > ignore. It would have to Depends "dhcpcd-base | dhcp-client" 
> > > > > > > > instead.
> > > > > > > >
> > > > > > > > 3) At that point, swapping the priority of isc-dhcp-client and
> > > > > > > > dhcpcd-base merely becomes "nice to have". Heck, the priority 
> > > > > > > > of both
> > > > > > > > could, in principle, be optional, just as long as ifupdown 
> > > > > > > > explicitly
> > > > > > > > Depends on a DHCP client, and the first alternative is a real 
> > > > > > > > package.
> > > > > > >
> > > > > > > I was about to bump dhcpcd-base as ifupdown dependency, but... if
> > > > > 

Bug#1065312: RM: deborphan -- ROM; missing too many dpkg features, thus broken and unreliable

[Martin-Éric Racine]

On Sat, 2 Mar 2024 18:40:13 +0100 Chris Hofstaedtler  wrote:
> * Christoph Biedl  [240302 17:02]:
> > Chris Hofstaedtler wrote...
> >
> > > please remove deborphan. It is stuck, featurewise, in a very old time
> > > and does not support many currently available dpkg features properly
> > > (multi-arch, versioned provides, etc).
> >
> > FWIW, deborphan is part of my regular workflow, and while you claim
> > it has defects, it works for me pretty well.
>
> It works "well" if you use it in very limited usecases, yes (like I
> did). It doesn't seem to work well for a lot of people using more of
> the "features" it has.

Just because it doesn't work for everyone is not a remotely good
enough reason to ask for its removal. It works for most people. don't
break it for them.

> The t64 transition will apparently make deborphan mostly useless in
> trixie.
>
> > [..]
> > So: What are the alternatives? How do they work? Are they a drop-in
> > replacment or do they introduce new dependencies? Are there feature that
> > will be no longer supported?
>
> release-notes recommends:
> https://www.debian.org/releases/stable/amd64/release-notes/ch-upgrading.en.html#removing-non-debian-packages

Which has nothing to do with what was asked.

> Some people seem to recommend debfoster.

Which really doesn't provide similar functionality.

> > Leaving users in the void about this is just bad style.

I totally agree. Not wanting to maintain it is a shitty reason for
asking for its removal. If you don't wanna maintain is, just orphan
it.

Martin-Éric

Bug#1065087: e2fsprogs: incorrect Pre-Depends on libext2fs2, should be libext2fs2t64

[Martin-Éric Racine]

Package: e2fsprogs
Version: 1.47.0-2.2
Severity: normal

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

As per Subject, this e2fsprogs upload missed two of the t64-versions of its 
pre-dependencies (see below), which creates a dependency loop.

Martin-Éric

- -- System Information:
Debian Release: trixie/sid
  APT prefers unstable
  APT policy: (900, 'unstable')
Architecture: i386 (x86_64)

Kernel: Linux 6.1.0-18-amd64 (SMP w/4 CPU threads; PREEMPT)
Locale: LANG=fi_FI.UTF-8, LC_CTYPE=fi_FI.UTF-8 (charmap=UTF-8), LANGUAGE=fi:en
Shell: /bin/sh linked to /usr/bin/dash
Init: unable to detect

Versions of packages e2fsprogs depends on:
ii  libblkid1   2.39.3-6.1
ii  libc6   2.37-15
ii  libcom-err2t64  1.47.0-2.2
ii  libext2fs2t64 [libext2fs2]  1.47.0-2.2
ii  libss2t64   1.47.0-2.2
ii  libuuid1t64 [libuuid1]  2.39.3-6.1
ii  logsave 1.47.0-2.2

Versions of packages e2fsprogs recommends:
ii  e2fsprogs-l10n  1.47.0-2.2

Versions of packages e2fsprogs suggests:
pn  e2fsck-static  
pn  fuse2fs
pn  gpart  
pn  parted 

- -- no debconf information

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEyJACx3qL7GpObXOQrh+Cd8S017YFAmXgq+UACgkQrh+Cd8S0
17bNVg//d1Nsnoy5Mh/px6bmwJp2uMR+EalPxusVQJ1lSe0k6K/GeoHZ0Vjh5mBd
VitJqWAb3iZTfXrXCfU8VGkm5t4MvUdpxKgJJxevVzH9ygSgMd4amWlEoCNdFNFR
bzkgJzK5qkBXHIu5ypLJSJbHAqb2exrtkdByl3icsAKUesc1cWEctjcXGuHetZE7
BUp1wMpUiNKrelaO1/DeCEtlfBQ9oKh53XXZ6qIa+MBAuCBimvcriwJcjpS4RCnU
y46IBmQiVseqGqVcV11eIbTUDuwQBUfeSd2jtuNNA/AMGxnGhVay6A0aT10iG9yU
LHNtLqtEjkEYRtlibXr9Rwqlp8I1eqevGbRCJR3vJBHhfq1iE/yiBYrWjmuerH9l
4ZAtnRnKuzMADXbBOVh/BABTYSA2tnUN0RL2e8AgcNXUChqStXK5qoBJ8Y7f9tZv
wpY/VcNaAPsqa/pN0qkdY4LP5PUKg74szRcfEldC4upuOqEPcH1FAVTfGRmkR5wQ
8G6AK1IdpRFfU1ngttoCnJHVxwApPSSJvSV1PNxTDSsO8J/NUIOryIJoMXZHenMY
faFyWyFsKMwj3PPPY+dmXpvTnvefw9c3duVijTuV6ycIo1UiTQEwfyc43kNJ2e4j
bxifBkLsboUcZkR1k9DUfU1u8bDBhBNMykjW2Bmn6DESksm0Ixg=
=6INB
-END PGP SIGNATURE-

Bug#1064435: gthumb: please package new upstream 3.12.5

[Martin-Éric Racine]

Package: gthumb
Version: 3:3.12.4-1~bpo12+1
Severity: normal

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Upstream released 3.12.5 on Februrary 18th 2024. Could you please package it?

Martin-Éric

PS: a backport to Bookworm would also be appreciated. :)

- -- System Information:
Debian Release: 12.5
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 
'stable-debug'), (500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 6.1.0-18-amd64 (SMP w/4 CPU threads; PREEMPT)
Locale: LANG=fi_FI.utf8, LC_CTYPE=fi_FI.utf8 (charmap=UTF-8), LANGUAGE=fi:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages gthumb depends on:
ii  gsettings-desktop-schemas   43.0-1
ii  gthumb-data 3:3.12.4-1~bpo12+1
ii  libbrasero-media3-1 3.12.3-2
ii  libc6   2.36-9+deb12u4
ii  libcairo2   1.16.0-7
ii  libcolord2  1.4.6-2.2
ii  libexiv2-27 0.27.6-1
ii  libgcc-s1   12.2.0-14
ii  libgdk-pixbuf-2.0-0 2.42.10+dfsg-1+b1
ii  libgl1-mesa-dri 22.3.6-1+deb12u1
ii  libglib2.0-02.74.6-2
ii  libgstreamer-plugins-base1.0-0  1.22.0-3+deb12u1
ii  libgstreamer1.0-0   1.22.0-2
ii  libgtk-3-0  3.24.38-2~deb12u1
ii  libheif11.15.1-1
ii  libjpeg62-turbo 1:2.1.5-2
ii  libjxl0.7   0.7.0-10
ii  liblcms2-2  2.14-2
ii  libpango-1.0-0  1.50.12+ds-1
ii  libpangocairo-1.0-0 1.50.12+ds-1
ii  libpng16-16 1.6.39-2
ii  libraw200.20.2-2.1
ii  librsvg2-2  2.54.7+dfsg-1~deb12u1
ii  libstdc++6  12.2.0-14
ii  libtiff64.5.0-6+deb12u1
ii  libwebp71.2.4-0.2+deb12u1
ii  libx11-62:1.8.4-2+deb12u2
ii  zlib1g  1:1.2.13.dfsg-1

gthumb recommends no packages.

gthumb suggests no packages.

- -- no debconf information

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEyJACx3qL7GpObXOQrh+Cd8S017YFAmXW9k4ACgkQrh+Cd8S0
17akgg//VWGfr+4sS/UuNHNKr/KHMAEq2EV1Cv00HzNq5yHl8Zokn8gpvy3Iyd4S
G0glnLly5gaLocdmOFX2+hHV/N80eA7luIOrT3uKdoVwGeJNWU5TJRGBaPetWgCv
SBkAVo8cfGHuMK0fwbZq5ENxBU/MITFDmpUl3pPI/ktdInXu13GpC3cjW8gJVgP5
xiXFq1/Rht0vb2dkccz6dV7rrkIO8n7WA8b8WRieIZXcApSZ16gNoimFYvtyjL3c
ifgtT17xXL7fHq4/1Nyg9QnvyCpGBsAswyux2TUDRBiMvPJ3BB1S8lLnze9tZgTm
hniG2xgd4EICNnX8sICNfxtmfwJ3xFcXvYwxb6+4dKQ+wos/juh0YOnKmZqS1GMQ
qcP6oI55UsRsSRYp6KFXRhnjUnPra/ATY/4RNNwiGzALOqWkXp1kUQ6qpfb4HPdn
YVG+tkw1C5/wBnrNR1r2TLgyi4wCPTSEG4qBzHAX+RmVOcT8w6iD/4cjRghvE5S+
6CKzy5+IryC2nAyhRkU/XMrPNRXehqwjKPz92V1G0lD1+O2U+7INLYJaBTrIH/XM
oPYyXDHVx5pjJfU0ERvncMp38CGTdGHXFjLmQItYL0r1LR5g0wi5xWnpCUQvWQ5e
brUa9dXEQ0ADDRQyFTjlAC0TAHI6kxZy6eH+fvrClCvjb2QTHQI=
=kvh7
-END PGP SIGNATURE-

Bug#1061519: shim: all CVEs fixed in upstream 15.8, please package

[Martin-Éric Racine]

Package: shim
Followup-For: Bug #1061519

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

shim 15.8 @vathpela vathpela released this 23 Jan 19:01

What's New

* Various CVE fixes:
  CVE-2023-40546 mok: fix LogError() invocation
  CVE-2023-40547 - avoid incorrectly trusting HTTP headers
  CVE-2023-40548 Fix integer overflow on SBAT section size on 32-bit system
  CVE-2023-40549 Authenticode: verify that the signature header is in bounds.
  CVE-2023-40550 pe: Fix an out-of-bound read in verify_buffer_sbat()
  CVE-2023-40551: pe-relocate: Fix bounds check for MZ binaries

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEyJACx3qL7GpObXOQrh+Cd8S017YFAmXIZ50ACgkQrh+Cd8S0
17ZHWhAAge996R8VG8WR1eoqM13HYsAvDh/ITPOHEAInuAvxnxW2f77RQuAdh/lL
SK0++9aR6P2yQu1j+JjfRz7vBt4FQ1j08RkjYj3kpKq8nHdA6C0fg1OvqXKs5+lc
44noX5AfKGyYDu/EhNkmAdFmE98sRVRqLlu8Ilfg1r8/voYFLOeyplW1T5Pk9xqW
Uv+wvLFNyj5mxMakPRyuZWD0bjkw33GYHKHMG5uB1ElwKws8cS/Lh9ZjaDk0GBy+
m4v0mhsIghPCcrNSfNcxvBT7fzR0dsD/wO21rBLcJc3ExdCeA39U4+jO86TS2/39
cfJhaY5FO72F8kX5qDKsNJzvl8Bhq4gH7YtEqyZC9aYdQgSpUdAuU6RQu9zDvpZm
EKuJVmXlgc+4IhgYLzJDHH2rL9gI2IctMNPwlKPI89SVs5J+Ha11t8V6oC36Chgq
nWrJeWnAhgHiDoTwHwqsj2j3YAVE7lHrAcxqgN1Sl5knmO26qxf8ZgrjB3iR/lVR
ufjBnkN+MJaN5oSV4XUTOlOk8uDswtQ1b6ycJAHbA+XhyHcHLRFY4bLVuDviJFsd
c3HGcsjzEwepvkg5mmKBm9renLxyUkqhiXQ7JSr5nKWlkaz5DR/4t74sfPjm1qK2
jsugjusiKZG4D895vQ3QcDafL4hdpqgpfi8k4O/Xbq5ncFIjs4Y=
=bM7B
-END PGP SIGNATURE-

Bug#1063662: bleachbit: Depends on transitional policykit-1

[Martin-Éric Racine]

Package: bleachbit
Version: 4.4.2-1
Severity: important

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Bleachbit version 4.4.2-1 depends on policykit-1 which is a transitional 
package that pulls pkexec and polkitd. Dependencies should be upgraded 
accordingly.

- -- System Information:
Debian Release: 12.5
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 
'stable-debug'), (500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 6.1.0-18-amd64 (SMP w/4 CPU threads; PREEMPT)
Locale: LANG=fi_FI.utf8, LC_CTYPE=fi_FI.utf8 (charmap=UTF-8), LANGUAGE=fi:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages bleachbit depends on:
ii  gir1.2-gtk-3.0 3.24.38-2~deb12u1
ii  gir1.2-notify-0.7  0.8.1-1
ii  libgtk-3-0 3.24.38-2~deb12u1
ii  pkexec 122-3
ii  policykit-1122-3
ii  python33.11.2-1+b1
ii  python3-chardet5.1.0+dfsg-2
ii  python3-gi 3.42.2-3+b1
ii  python3-requests   2.28.1+dfsg-1

bleachbit recommends no packages.

bleachbit suggests no packages.

- -- no debconf information

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEyJACx3qL7GpObXOQrh+Cd8S017YFAmXHtEEACgkQrh+Cd8S0
17ZKABAAm3UPEs3tiBO/ozbVddGWR9IsaIm0+uspQL+kYqG5EYda71GcrxTbA4lf
IJzYOEv9/0o7h4yvs70z9Fsp7q1o4UBMGksnGh1M7NUCZvPmMpBdtj6dOm/pktVE
7QLhPeGN/6hIa3pl+kw0J1ccCWvmWf1jPdxZ00eGsorwj6RX/uNF4zlYDhcXtPWr
adIQ4prkirPCLo5DC4H4NEag2fbqft9nwutyuLV69anQDZWRjetPz37W04EHlarR
qvuKQgjGKoezhIpYA84ao2+B22FWG6lWBZ0ouGw+bqRQZKobojlkjrIMSA891HXB
AiVLGy+EcjFJ7Z33tkQWJ9f47JW55tHARlWa6Z6U48kO1NpV4rfFqtAGAh/T872n
oYBxU8moE2kaHBVQ36GFpqX3Jh0vB8G/1oApTFkPDraG2D+Ed74CEuGMAqn9NvjK
OPuoqw8WwHO5dLpC8A4LSnbBTg1qAkHNIy6/ClwOMONLS+zHsO3CX8X97d+om8i3
YV8EwGKYqYDJMgSgjhyxftxDD5sPUF09rIeQ3X4Xsp4IjYgjbt/p97OKDJkDuPLK
g/yn986uoHVl8W8pfmeb+jfEf1OpSxxkoKY9zx7rK8o+ZZBLVeqQGFE2lHJ+6837
HqdwlotUN0yLwC70EE/AW6/if5+3WZf3N/+XZmys8utJTE1hx40=
=48oq
-END PGP SIGNATURE-

Bug#1062357: systemd-cron: broken result mailing implementation

[Martin-Éric Racine]

pe 2. helmik. 2024 klo 8.30 Alexandre Detiste
(alexandre.deti...@gmail.com) kirjoitti:
>
> Le jeu. 1 févr. 2024 à 09:11, Martin-Éric Racine
>  a écrit :
> > > 1)
> > >
> > > MAILFROM= is supported for a long time, is it enough ?
> > >
> > > v1.5.18 : 2020-12-26
> >
> > Thanks. Good to know. It's not documented in the crontab(5) man page.
>
> I added it now.
> It matches cronie alternative implementation roughly at the same time
> https://github.com/cronie-crond/cronie/commit/6181605fafe6aaedc0c19a8bdc85a335403b42d8

Cheers!

> > Also, can this variable be configured in a file that is dropped into
> > some directory, to avoid editing the global /etc/crontab? e.g.
> > /etc/crontab.d/ or something similar?
>
> /etc/crontab _is_ the main config file which other jobs
> (like in /etc/cron.{d,hourly,daily,...}/ will inherit mailing settings from.
> ("std::optional fallback_mailto;" in code)
>
> /etc/sysconfig/crond & /etc/default/PACKAGE are old Redhat & Debian
> things, mostly deprecated by systemd config drop-ins.

A systemd drop-in would work too. It just needs to be documented.
Which file? Which configuration key? Just as long as there's somewhere
I can drop a file to configure the MAILFROM on all my hosts, I'm good
to go.

> Maybe you'd want to read from /etc/aliases ?
> I think this one is only for receiving email, not sending.
>
> > > 2) _cron-failure should had been (re-)created by systemd-sysusers:
> >
> > helmi 01 06:20:08 p8h61 nullmailer-send[1286]: From:
> > <_cron-fail...@iki.fi> to: 
> >
> > _cron-failure does not exist as a user on iki.fi (a public e-mail
> > account e.g. gmail.com, hotmail.com), and therefore bounces.
>
> _cron-failure is a technical user, it should never leaks into e-mail 
> envelopes.
> I'm using nullmailer myself but I can't reproduce it.

It does if delivery of the cron job report fails.

Martin-Éric

Bug#1062366: nullmailer: adminaddr should also set From on mails from root@localhost

[Martin-Éric Racine]

To 1. helmik. 2024 klo 14.00 David Bremner (da...@tethera.net) kirjoitti:
>
> Martin-Éric Racine  writes:
> >
> > The /etc/nullmailer/adminaddr address should also define the From for
> > messages sent BY root, not just TO root, and use it to make nullmailer
> > overwrite any outgoing root@defaultdomain message.
> >
>
> Just to confirm, this seems like an upstream issue that I should
> forward?

Yes, indeed. I'm simply not aware of any upstream tracker.

Martin-Éric

Bug#1062421: linux-image-6.5.0-5-686-pae: [iwlegacy] kernel oops

[Martin-Éric Racine]

Package: src:linux
Version: 6.5.13-1
Severity: important

0c:00.0 Network controller: Intel Corporation PRO/Wireless 4965 AG or AGN 
[Kedron] Network Connection (rev 61)

-- Package-specific info:
** Version:
Linux version 6.5.0-5-686-pae (debian-ker...@lists.debian.org) (gcc-13 (Debian 
13.2.0-7) 13.2.0, GNU ld (GNU Binutils for Debian) 2.41) #1 SMP PREEMPT_DYNAMIC 
Debian 6.5.13-1 (2023-11-29)

** Command line:
BOOT_IMAGE=/boot/vmlinuz-6.5.0-5-686-pae 
root=UUID=24bd6387-2e4e-4eb3-96dd-69817428d656 ro panic=15 noquiet loglevel=5 
nosplash

** Tainted: W (512)
 * kernel issued warning

** Kernel log:
[   43.903258]  excluding 0x3f0-0x3ff 0x4d0-0x4d7
[   43.908023] pcmcia_socket pcmcia_socket0: cs: IO port probe 0x820-0x8ff:
[   43.908763]  clean
[   43.918791] pcmcia_socket pcmcia_socket0: cs: IO port probe 0xc00-0xcf7:
[   43.919335]  excluding 0xc80-0xcbf
[   43.926704] pcmcia_socket pcmcia_socket0: cs: memory probe 0x0c-0x0f:
[   43.926723]  excluding 0xc-0xc7fff 0xcc000-0xc 0xf-0xf
[   43.929834] pcmcia_socket pcmcia_socket0: cs: memory probe 
0xa000-0xa0ff:
[   43.929869]  clean
[   43.935724] pcmcia_socket pcmcia_socket0: cs: memory probe 
0x6000-0x60ff:
[   43.935755]  excluding 0x6000-0x60ff
[   43.938809] pcmcia_socket pcmcia_socket0: cs: IO port probe 0xa00-0xaff:
[   43.939652]  clean
[   44.156484] warning: `iwconfig' uses wireless extensions which will stop 
working for Wi-Fi 7 hardware; use nl80211
[   44.405062] usbcore: registered new interface driver btusb
[   44.419090] Bluetooth: hci0: unexpected event for opcode 0x
[   44.735638] input: HDA Intel Mic as 
/devices/pci:00/:00:1b.0/sound/card0/input9
[   44.736164] input: HDA Intel Headphone as 
/devices/pci:00/:00:1b.0/sound/card0/input10
[   46.527355] 8021q: 802.1Q VLAN Support v1.8
[   47.697077] Adding 2421756k swap on /dev/sda5.  Priority:-2 extents:1 
across:2421756k FS
[   49.569763] [ cut here ]
[   49.569771] memcpy: detected field-spanning write (size 1014) of single 
field "_cmd->cmd.payload" at 
drivers/net/wireless/intel/iwlegacy/common.c:3170 (size 320)
[   49.569831] WARNING: CPU: 0 PID: 608 at 
drivers/net/wireless/intel/iwlegacy/common.c:3170 il_enqueue_hcmd+0x34f/0x41c 
[iwlegacy]
[   49.569856] Modules linked in: 8021q garp stp mrp llc snd_hda_codec_hdmi 
btusb btrtl btbcm snd_hda_codec_idt ppdev btintel snd_hda_codec_generic btmtk 
dell_rbtn iwl4965 bluetooth iwlegacy dell_laptop snd_hda_intel ledtrig_audio 
sha3_generic snd_intel_dspcfg mac80211 dell_smm_hwmon snd_intel_sdw_acpi 
jitterentropy_rng snd_hda_codec sha512_generic pcmcia ctr libarc4 dell_wmi 
snd_hda_core drbg iTCO_wdt ansi_cprng cfg80211 intel_pmc_bxt dell_smbios 
snd_hwdep yenta_socket ecdh_generic sparse_keymap pcmcia_rsrc dcdbas 
iTCO_vendor_support watchdog dell_wmi_descriptor rfkill snd_pcm pcmcia_core 
wmi_bmof snd_timer ecc acpi_cpufreq snd at24 soundcore parport_pc button ac 
parport evdev joydev sg serio_raw binfmt_misc msr ecryptfs dm_mod fuse loop 
efi_pstore dax configfs nfnetlink ip_tables x_tables autofs4 drivetemp ext4 
crc16 mbcache jbd2 btrfs blake2b_generic sr_mod cdrom xor raid6_pq libcrc32c 
crc32c_generic uas usb_storage i915 sd_mod t10_pi crc64_rocksoft crc64 
crc_t10dif i2c_algo_bit crct10dif_generic crct10dif_common
[   49.570042]  drm_buddy ata_generic drm_display_helper ata_piix 
drm_kms_helper cec rc_core libata sdhci_pci ttm uhci_hcd ehci_pci ehci_hcd 
cqhci firewire_ohci scsi_mod drm tg3 firewire_core coretemp sdhci i2c_i801 
usbcore psmouse libphy mmc_core lpc_ich i2c_smbus crc_itu_t scsi_common 
usb_common battery video wmi
[   49.570105] CPU: 0 PID: 608 Comm: wpa_supplicant Not tainted 6.5.0-5-686-pae 
#1  Debian 6.5.13-1
[   49.570112] Hardware name: Dell Inc. Latitude D430   
/07, BIOS A01 06/20/2007
[   49.570115] EIP: il_enqueue_hcmd+0x34f/0x41c [iwlegacy]
[   49.570129] Code: f8 00 0f 85 62 fe ff ff 89 45 d0 c6 05 6a a1 f0 f8 01 68 
40 01 00 00 68 08 ec f0 f8 51 89 4d d4 68 5c ec f0 f8 e8 51 5c 17 dc <0f> 0b 8b 
45 d0 8b 4d d4 83 c4 10 e9 30 fe ff ff 90 8b 7d f0 ba 28
[   49.570135] EAX: 0099 EBX: c4016cf0 ECX: f5bdbf44 EDX: f5bdbf40
[   49.570139] ESI: c44b4f00 EDI: c13c1a88 EBP: c13c1a28 ESP: c13c19e8
[   49.570144] DS: 007b ES: 007b FS: 00d8 GS: 0033 SS: 0068 EFLAGS: 00010082
[   49.570149] CR0: 80050033 CR2: b7ee89a0 CR3: 0475c000 CR4: 06f0
[   49.570155] Call Trace:
[   49.570161]  ? show_regs+0x4f/0x58
[   49.570173]  ? il_enqueue_hcmd+0x34f/0x41c [iwlegacy]
[   49.570185]  ? __warn+0x74/0x128
[   49.570192]  ? il_enqueue_hcmd+0x34f/0x41c [iwlegacy]
[   49.570204]  ? report_bug+0x170/0x194
[   49.570213]  ? exc_overflow+0x38/0x38
[   49.570221]  ? handle_bug+0x2d/0x58
[   49.570228]  ? exc_invalid_op+0x18/0x54
[   49.570234]  ? handle_exception+0x133/0x133
[   49.570242]  ? exc_overflow+0x38/0x38
[   49.570249]  ? il_enqueue_hcmd+0x34f/0x41c [iwlegacy]
[   49.570262]  ? exc_overflow+0x38/0x38

Bug#1062357: systemd-cron: broken result mailing implementation

[Martin-Éric Racine]

to 1. helmik. 2024 klo 9.33 Alexandre Detiste
(alexandre.deti...@gmail.com) kirjoitti:
> 1)
>
> MAILFROM= is supported for a long time, is it enough ?
>
> v1.5.18 : 2020-12-26
>
>Various improvements to email on error:
>* Revert "Use DynamicUser=yes for error email generator"
>* Use sysusers.d snippet instead
>* Support for MAILFROM variable [thanks MarcoCLA]

Thanks. Good to know. It's not documented in the crontab(5) man page.

Also, can this variable be configured in a file that is dropped into
some directory, to avoid editing the global /etc/crontab? e.g.
/etc/crontab.d/ or something similar?

> 2) _cron-failure should had been (re-)created by systemd-sysusers:
>
> $ cat debian/systemd-cron.sysusers
> u _cron-failure -:systemd-journal - /nonexistent /usr/sbin/nologin
>
> $ cat debian/rules
> execute_after_dh_auto_install:
> # automatic with DebHelper >= 14
> dh_installsysusers

helmi 01 06:20:08 p8h61 nullmailer-send[1286]: From:
<_cron-fail...@iki.fi> to: 

_cron-failure does not exist as a user on iki.fi (a public e-mail
account e.g. gmail.com, hotmail.com), and therefore bounces.

Martin-Éric

Bug#1062366: nullmailer: adminaddr should also set From on mails from root@localhost

[Martin-Éric Racine]

Package: nullmailer
Version: 1:2.2-4
Severity: normal

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

The /etc/nullmailer/adminaddr address should also define the From for messages 
sent BY root, not just TO root, and use it to make nullmailer overwrite any 
outgoing root@defaultdomain message.

Martin-Éric


- -- System Information:
Debian Release: 12.4
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 
'stable-debug'), (500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 6.1.0-17-amd64 (SMP w/4 CPU threads; PREEMPT)
Locale: LANG=fi_FI.utf8, LC_CTYPE=fi_FI.utf8 (charmap=UTF-8), LANGUAGE=fi:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages nullmailer depends on:
ii  debconf [debconf-2.0]  1.5.82
ii  libc6  2.36-9+deb12u4
ii  libgnutls303.7.9-2+deb12u1
ii  libstdc++6 12.2.0-14

nullmailer recommends no packages.

nullmailer suggests no packages.

- -- debconf information excluded

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEyJACx3qL7GpObXOQrh+Cd8S017YFAmW7RzkACgkQrh+Cd8S0
17b7OBAAinUVi2AvdyEwYsYbpP95nD2nmTAnsFCRJCykK87DSUBArtXlul13npkP
KLP1E5Z1r3LbK10BcHuxSjoJV+UwrpLMe88oMSZTET56EJHAo7NnrKj4z3+QqlPG
9Dy6Amgu0/3VR9vkyOkEPKr4mt47HiDL9W+Iqi9jcXQ9NyUcFusvhZzSJLvC6qIy
sn7ynNz3GF0uDIqsrKGvHCjTcvNLZE6Q/9chcnfadaDD5qeHf4qTPCU4TKhb3aU1
Nq1TftpeI2a9KjrCNrbwgksQT5g7v2rePj7MJQsXJM2P5yK/6MvSnjNKosuE5Qh5
+T4ecOVYliApeEh5Poz0QSGf8rXjXtMmSoKjE5zOGb3GhfvsME45zU+c2PGNIhBN
8accIPXXrcwS7FfqZ7q3FiRWvixAORqL8oOrzb4ri7RWolI5/igpM6rXDHa1ilr0
xekqn6iZfaZBlEZCaCHSjfPSghOLyrj6M0GUNsMBTBfH5mHNJ5VPD/HN/uRN9MB9
EOLQKjKH+jGq9To2Y+1Jhyy47usz85KrEinsQ7nzXRBODWgYBUfoON9tRNjCPWos
NzHHz+8hhPHxNp4O/d+WWR630250X2YEQESkJHaskAVSEiNQNiUW6KlPzNY4fiG+
gIo8JCb5IVMyn8gJo6LXtaLR3KsOW8klbgT/3/ULIxODPDNcAh8=
=y2Mi
-END PGP SIGNATURE-

Bug#1062357: systemd-cron: broken result mailing implementation

[Martin-Éric Racine]

Package: systemd-cron
Version: 2.3.0-1~bpo12+1
Severity: important

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

1) In its current form, systemd-cron mails the result of global cron jobs from 
root@fqdn, which fails since we aren't FQDN's administrator.

2) As a result, systemd-cron tries to notify the administrator of the failed 
delivery, but does so from a non-existent mail account _cron-failure, which 
thus also fails.

Fixing this requires systemd-cron to support the SENDFROM variable.

- -- Package-specific info:

- -- System Information:
Debian Release: 12.4
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 
'stable-debug'), (500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 6.1.0-17-amd64 (SMP w/4 CPU threads; PREEMPT)
Locale: LANG=fi_FI.utf8, LC_CTYPE=fi_FI.utf8 (charmap=UTF-8), LANGUAGE=fi:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages systemd-cron depends on:
ii  cron-daemon-common  3.0pl1-162
ii  libc6   2.36-9+deb12u4
ii  libssl3 3.0.11-1~deb12u2
ii  libstdc++6  12.2.0-14
ii  systemd [systemd-sysusers]  252.19-1~deb12u1
ii  systemd-sysv252.19-1~deb12u1

systemd-cron recommends no packages.

Versions of packages systemd-cron suggests:
ii  nullmailer [mail-transport-agent]  1:2.2-4

- -- no debconf information

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEyJACx3qL7GpObXOQrh+Cd8S017YFAmW7QzMACgkQrh+Cd8S0
17bN9A//bzMRtMlJqd2WplMmaKQAoTPxzOa/atj8etNtNcuukBqz/UrEXOpN0mIY
8PX6gtMjbqDbXjmkkkGHNIwgQhmjn+XOfQBm7emHQ0dbbIbILE5nL6NBSe9mLjW4
8nQp3ayAKmgS3BCdtWyyoWaY5K9ifdeM4rK5gphshC2nQ9sZ/++VtzG1x8uBfnBc
HW4ixPxrm2yhz2WLP3tzSGW6wV0Xs4QnJtwXhQROJZFH+6scV/n9KVeoqB+q/xBB
JaAnfk7s8GH9P6oU+Y6t3fglEAPudT7Rrwty47mL4CXzDdJU/LWFo5ykTy7BNPW/
8f7qDlb2Yj+/y6EYMqz6Wsu80rg4SQA4Xm+I/8Kd6BiqZqSgCaXbioR6A4U3u76V
vBooi6+oT/StVk8n6xXh6xU1vkya/JV30nJMeyCixEJRsuVy48zah68mgcNLqKUu
CoYhgzRV0XnCnT8Jww1qdY3uZdLqbTvE8ezkH8BHZb1aDj6I24deS6a4eFJqQaSP
nAuI5IJsgyMc5RMocI6LETtxEpf420upllXd6VfajrAU9dA68EzemxoBkGaDpPqm
hYj5xyz3VuOMz2Z+eXrK/W30Lo98jXxrijDYPvbEJCqlApSC0VATKze/IdXgjaal
xPUmkQlFZGBNfF7hsWQhQXCP0rQ/t8qkWTKL2jFsJlG3t6bWtrM=
=B0xd
-END PGP SIGNATURE-

Bug#1057833: sudo: [Hurd i386] upgrade from 1.9.14p2 to 1.9.15p2 dies with malloc error

[Martin-Éric Racine]

On Fri, Dec 29, 2023 at 3:33 PM Marc Haber
 wrote:
> On Sat, Dec 09, 2023 at 12:40:46PM +0200, Martin-Éric Racine wrote:
> > Since the upgrade from 1.9.14p2 to 1.9.15p in unstable, sudo aborts with a 
> > malloc error on Hurd i386.
>
> Upstream has reproduced and fixed this in
> https://www.sudo.ws/repos/sudo/rev/8917f7d6a464
>
> Are you in a position to verify this before I apply and upload?

This seems fixed as of 1.9.15p5-2.

Thanks!
Martin-Éric

Bug#1060011: ERROR: Clamonacc: at least one of OnAccessExcludeUID, OnAccessExcludeUname, or OnAccessExcludeRootUID must be specified

[Martin-Éric Racine]

Package: clamav-daemon
Version: 1.0.3+dfsg-1~deb12u1
Severity: important

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

$ systemctl status clamav-clamonacc.service
× clamav-clamonacc.service - ClamAV On-Access Scanner
 Loaded: loaded (/lib/systemd/system/clamav-clamonacc.service; enabled; 
preset: enabled)
 Active: failed (Result: exit-code) since Thu 2024-01-04 20:11:38 EET; 3min 
11s ago
   Duration: 11ms
   Docs: man:clamonacc(8)
 man:clamd.conf(5)
 https://docs.clamav.net/
Process: 13031 ExecStartPre=/bin/bash -c while [ ! -S /run/clamav/clamd.ctl 
]; do sleep 1; done (code=exited, status=0/SUCCESS)
Process: 13032 ExecStart=/usr/sbin/clamonacc -F 
--log=/var/log/clamav/clamonacc.log --move=/root/quarantine (code=exited, 
status=2)
   Main PID: 13032 (code=exited, status=2)
CPU: 12ms

tammi 04 20:11:38 p8h61 systemd[1]: Starting clamav-clamonacc.service - ClamAV 
On-Access Scanner...
tammi 04 20:11:38 p8h61 systemd[1]: Started clamav-clamonacc.service - ClamAV 
On-Access Scanner.
tammi 04 20:11:38 p8h61 clamonacc[13032]: --
tammi 04 20:11:38 p8h61 clamonacc[13032]: ERROR: Clamonacc: at least one of 
OnAccessExcludeUID, OnAccessExcludeUname, or OnAccessExcludeRootUID must be 
specified ... it is recommended>
tammi 04 20:11:38 p8h61 systemd[1]: clamav-clamonacc.service: Main process 
exited, code=exited, status=2/INVALIDARGUMENT
tammi 04 20:11:38 p8h61 systemd[1]: clamav-clamonacc.service: Failed with 
result 'exit-code'.



- -- Package-specific info:
- --- configuration ---
Checking configuration files in /etc/clamav

Config file: clamd.conf
- ---
AlertExceedsMax disabled
PreludeEnable disabled
PreludeAnalyzerName = "ClamAV"
LogFile = "/var/log/clamav/clamav.log"
LogFileUnlock disabled
LogFileMaxSize = "4294967295"
LogTime = "yes"
LogClean disabled
LogSyslog disabled
LogFacility = "LOG_LOCAL6"
LogVerbose disabled
LogRotate = "yes"
ExtendedDetectionInfo = "yes"
PidFile disabled
TemporaryDirectory disabled
DatabaseDirectory = "/var/lib/clamav"
OfficialDatabaseOnly disabled
LocalSocket = "/var/run/clamav/clamd.ctl"
LocalSocketGroup = "clamav"
LocalSocketMode = "666"
FixStaleSocket = "yes"
TCPSocket disabled
TCPAddr disabled
MaxConnectionQueueLength = "15"
StreamMaxLength = "26214400"
StreamMinPort = "1024"
StreamMaxPort = "2048"
MaxThreads = "12"
ReadTimeout = "180"
CommandReadTimeout = "30"
SendBufTimeout = "200"
MaxQueue = "100"
IdleTimeout = "30"
ExcludePath disabled
MaxDirectoryRecursion = "15"
FollowDirectorySymlinks disabled
FollowFileSymlinks disabled
CrossFilesystems = "yes"
SelfCheck = "3600"
ConcurrentDatabaseReload = "yes"
DisableCache disabled
VirusEvent disabled
ExitOnOOM disabled
AllowAllMatchScan = "yes"
Foreground disabled
Debug disabled
LeaveTemporaryFiles disabled
GenerateMetadataJson disabled
User = "clamav"
Bytecode = "yes"
BytecodeSecurity = "TrustSigned"
BytecodeTimeout = "6"
BytecodeUnsigned disabled
BytecodeMode = "Auto"
DetectPUA disabled
ExcludePUA disabled
IncludePUA disabled
ScanPE = "yes"
ScanELF = "yes"
ScanMail = "yes"
ScanPartialMessages disabled
PhishingSignatures = "yes"
PhishingScanURLs = "yes"
HeuristicAlerts = "yes"
HeuristicScanPrecedence disabled
StructuredDataDetection disabled
StructuredMinCreditCardCount = "3"
StructuredMinSSNCount = "3"
StructuredSSNFormatNormal = "yes"
StructuredSSNFormatStripped disabled
ScanHTML = "yes"
ScanOLE2 = "yes"
AlertBrokenExecutables disabled
AlertBrokenMedia disabled
AlertEncrypted disabled
StructuredCCOnly disabled
AlertEncryptedArchive disabled
AlertEncryptedDoc disabled
AlertOLE2Macros disabled
AlertPhishingSSLMismatch disabled
AlertPhishingCloak disabled
AlertPartitionIntersection disabled
ScanPDF = "yes"
ScanSWF = "yes"
ScanXMLDOCS = "yes"
ScanHWP3 = "yes"
ScanArchive = "yes"
ForceToDisk disabled
MaxScanTime = "12"
MaxScanSize = "104857600"
MaxFileSize = "26214400"
MaxRecursion = "16"
MaxFiles = "1"
MaxEmbeddedPE = "10485760"
MaxHTMLNormalize = "10485760"
MaxHTMLNoTags = "2097152"
MaxScriptNormalize = "5242880"
MaxZipTypeRcg = "1048576"
MaxPartitions = "50"
MaxIconsPE = "100"
MaxRecHWP3 = "16"
PCREMatchLimit = "1"
PCRERecMatchLimit = "5000"
PCREMaxFileSize = "26214400"
OnAccessMountPath disabled
OnAccessIncludePath disabled
OnAccessExcludePath disabled
OnAccessExcludeRootUID disabled
OnAccessExcludeUID disabled
OnAccessExcludeUname disabled
OnAccessMaxFileSize = "5242880"
OnAccessDisableDDD disabled
OnAccessPrevention disabled
OnAccessExtraScanning disabled
OnAccessCurlTimeout = "5000"
OnAccessMaxThreads = "5"
OnAccessRetryAttempts disabled
OnAccessDenyOnError disabled
DevACOnly disabled
DevACDepth disabled
DevPerformance disabled
DevLiblog disabled
DisableCertCheck disabled
AlgorithmicDetection = "yes"
BlockMax disabled
PhishingAlwaysBlockSSLMismatch disabled
PhishingAlwaysBlockCloak disabled
PartitionIntersection disabled
OLE2BlockMacros disabled
ArchiveBlockEncrypted disabled

Config file: 

Bug#1059063: sudo: use systemd.pc to place systemd unit mask

[Martin-Éric Racine]

Hello Helmut,
On Thu, Jan 4, 2024 at 1:07 PM Helmut Grohne  wrote:
> On Thu, Jan 04, 2024 at 08:32:55AM +0200, Martin-Éric Racine wrote:
> > This patch includes a Build-Depends on systemd. Without [linux-any],
> > it will prevent building on non-Linux ports.
>
> You raise an important matter. Basically, the only remaining non-linux
> port is hurd at this time, so I'm adding them to the loop.
>
> While the general question is non-trivial to resolve, I think this
> instance has a relatively straight forward answer. What we need here is
> not systemd, but systemd-dev and that latter one is an Arch:all package
> that doesn't have any dependencies, so systemd-dev actually should be
> installable on hurd and is the right thing to depend on anyway.

https://buildd.debian.org/status/package.php?p=sudo

Martin-Éric

Bug#1059063: sudo: use systemd.pc to place systemd unit mask

[Martin-Éric Racine]

On Tue, 19 Dec 2023 23:13:54 +0100 Chris Hofstaedtler  wrote:
> Source: sudo
> Version: 1.9.15p3-1
> Severity: normal
> Tags: patch
> User: helm...@debian.org
> Usertags: dep17m2
>
> Dear Maintainer,
>
> your package installs a systemd system unit mask (symlink to
> /dev/null), currently into /lib.  This symlink needs to be moved to
> /usr/lib as part of Debian's usr-merge effort [1].
>
> Attached you will find a patch using systemd.pc to place it
> (using pkg-config).  This works for unstable today, and also for
> bookworm-backports, and is safe to do now.
>
> Later during the trixie cycle I expect this bug class to raise in
> priority.
>
> If during the trixie cycle your package will undergo structural
> changes or any other file moves, please see the wiki and upload
> to experimental first when these changes are done.
>
> Thank you for considering,
> Chris
>
> [1] https://wiki.debian.org/UsrMerge

This patch includes a Build-Depends on systemd. Without [linux-any],
it will prevent building on non-Linux ports.

Martin-Éric

Bug#1057833: not quite fixed

[Martin-Éric Racine]

This is not quite fixed.

The Build-Depends on systemd must be [linux-any] otherwise the build
cannot proceed.

Bug#1059739: ssh-audit: please package 3.1.0

[Martin-Éric Racine]

Package: ssh-audit
Version: 3.0.0-1
Severity: normal

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

3.1.0 was released 2 weeks ago. Can you please package it?

Thanks!

Martin-Éric

- -- System Information:
Debian Release: trixie/sid
  APT prefers unstable
  APT policy: (900, 'unstable')
Architecture: i386 (x86_64)

Kernel: Linux 6.1.0-16-amd64 (SMP w/4 CPU threads; PREEMPT)
Locale: LANG=fi_FI.UTF-8, LC_CTYPE=fi_FI.UTF-8 (charmap=UTF-8), LANGUAGE=fi:en
Shell: /bin/sh linked to /usr/bin/dash
Init: unable to detect

Versions of packages ssh-audit depends on:
ii  python3  3.11.6-1

ssh-audit recommends no packages.

ssh-audit suggests no packages.

- -- no debconf information

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEyJACx3qL7GpObXOQrh+Cd8S017YFAmWRIkcACgkQrh+Cd8S0
17Zk5Q//Z/A8hEs0Tung+tiMGGKdF8T329GCKN8QM0MOFy9Yir1bEy9JGURYUk9X
qAesH91x6R7hlcUUQDyZkxVo8xDgOMZ6hEcPbm6gKcI+Hr3OZE6SYNqTy21ziqoU
zjqeL88XlBHAi5cIt7hnKw/Az1eKAG3SuLJ4WJEPmwuNoFpaLe/0339FhZypbGEB
7QJiED5c8wO5ce9iCeRGmFuWzKM3M3NNIA5RWj7l3g8yRBtEmZjPoOqf7Jfa8mCI
7e4LnaR8EV1qERlyMucQSwbObQXRJolYH2e5kF2cUYuVWau2WyXTdrkUur6kq72/
nRREXWkuf31JL4yVR6MxRI0nMF9xwxgXDEdnSAydn2xuwJfn5wSWlle3d0gEN8rz
TKWSZ4NYZlhhzLDvCpxFTIdp9tqEx3Gge21ZWaCLYkIZOwqQefkW4OKKzqs9w38Q
o4nUt3k/Lt3fVkpCi3J5QnlJTWlEhWJ88tLSouAKnqDN0WWHYgx3ci8G62piDieh
tI5s4G+lx35gdyzcxiLbwXpSLwKdkAC/E1S9O6/GKa1vSOB5RQbI0akYKOldAjqx
kg+YbsB7F7cNYtSRfg1FJ/Xa4OMwTkYr6oVL7yOlWMp6tPks+P6e/xDbmTml9sQt
BCpFuoNga19DWyWsZQNfXK7PSRnbzHW1k+66gnV5/4rvxO9Ymp4=
=rm64
-END PGP SIGNATURE-

Bug#1057833: sudo: [Hurd i386] upgrade from 1.9.14p2 to 1.9.15p2 dies with malloc error

[Martin-Éric Racine]

On Fri, Dec 29, 2023 at 3:33 PM Marc Haber
 wrote:
>
> On Sat, Dec 09, 2023 at 12:40:46PM +0200, Martin-Éric Racine wrote:
> > Since the upgrade from 1.9.14p2 to 1.9.15p in unstable, sudo aborts with a 
> > malloc error on Hurd i386.
>
> Upstream has reproduced and fixed this in
> https://www.sudo.ws/repos/sudo/rev/8917f7d6a464
>
> Are you in a position to verify this before I apply and upload?

Sorry, I'm not. Just go ahead and upload. I'll let you know whether
that fixed it or not.

Martin-Éric

Bug#1058451: ntpsec: FTBFS [Hurd] change Build-Depends: systemd to [linux-any]

[Martin-Éric Racine]

On Wed, Dec 27, 2023 at 5:54 AM Richard Laager  wrote:
>
> On 2023-12-26 21:43, Martin-Éric Racine wrote:
> > Looking at the diff for the Hurd port
>
> What Hurd port?

https://deb.debian.org/debian-ports/pool-hurd-i386/main/n/ntp/

Martin-Éric

Bug#1058451: ntpsec: FTBFS [Hurd] change Build-Depends: systemd to [linux-any]

[Martin-Éric Racine]

On Wed, Dec 27, 2023 at 12:04 AM Richard Laager  wrote:
>
> On 2023-12-26 02:38, Martin-Éric Racine wrote:
> > On Mon, Dec 25, 2023 at 12:20 AM Richard Laager  wrote:
> >> If past me was correct, without systemd at build-time, waf will not
> >> install the systemd units. Then we will end up with other failures in
> >> debian/rules or from the .install files.
> >
> > Not installing them on platforms where systemd has not been ported is
> > the correct action.
>
> Agreed. My point was that additional work would be required, during the
> package building process, to not blow up when those files are missing
> from `waf install`.

Looking at the diff for the Hurd port would tell you what's needed.
Anything else is speculation.

> > It built enough to have ntpdate.
> bin:ntpdate is just a transitional package to transition uses of the old
> src:ntp's bin:ntpdate to src:ntpsec's bin:ntpsec-ntpdate. It is
> Architecture: all, which is why it is available on Hurd.
>
> In ntpsec, the ntpdate executable is just a thin wrapper around ntpdig,
> which ships in the bin:ntpsec-ntpdig package (formerly, it was in
> bin:ntpsec-ntpdate). While ntpdig is Python, so it doesn't actually
> require compilation, it is presumably going to require some build steps
> happen.

Noted.

> >> ifeq (hurd, $(DEB_HOST_ARCH_OS))
> >>   # hurd does not provided the system calls needed for ntpd to work.
> >>   exit 1
> >> endif
> >>
> >> I see a couple of ways forward here:
> >>
> >> A) I properly indicate this package does not support HURD.
> >>
> >>  I think I would just replace the "Architecture: any" with
> >>  "Architecture: linux-any" on binary packages in debian/control, but
> >>  I would love confirmation on that.
> >
> > Which is what this bug requested
>
> I'm confused.
>
> What you asked for was for me to limit "Build-Depends: systemd" to
> [linux-any].

Which is the correct course of action. Puposely limiting binary targets isn't.

Martin-Éric

Bug#1058451: ntpsec: FTBFS [Hurd] change Build-Depends: systemd to [linux-any]

[Martin-Éric Racine]

On Tue, Dec 26, 2023 at 10:38 AM Martin-Éric Racine
 wrote:
>
> On Mon, Dec 25, 2023 at 12:20 AM Richard Laager  wrote:
> >
> > On 2023-12-12 04:52, Martin-Éric Racine wrote:
> > > Build-Depends: systemd must be changed to systemd [linux-any], since 
> > > systemd has not been powerted to non-Linux platforms.
> >
> > I suspect that change would be necessary, but not sufficient.
> >
> > In commit 7f969a0ecab4ef3ab50defd4fe9d7e7a47817dbe, I wrote:
> >Build-Depend on systemd
> >
> >This is required for the pkg-config file, so that waf will detect
> >systemd and install the systemd units.
>
> Only on linux-any.
>
> > If past me was correct, without systemd at build-time, waf will not
> > install the systemd units. Then we will end up with other failures in
> > debian/rules or from the .install files.
>
> Not installing them on platforms where systemd has not been ported is
> the correct action.
>
> > HURD is the only non-Linux platform that Debian supports these days,
> > right? kFreeBSD is gone, IIRC.
> >
> > The ntpsec package (like ntp before it, IIRC) does not build on HURD
> > anyway. From debian/rules:
>
> It built enough to have ntpdate. The Hurd patch was even updated just
> a few days before the version that added the build-depends on systemd.

$ LC_ALL=C apt policy ntpdate
ntpdate:
  Installed: 1:4.2.8p15+dfsg-2~1.2.2+dfsg1-2+hurd.1
  Candidate: 1:4.2.8p15+dfsg-2~1.2.2+dfsg1-4
  Version table:
 1:4.2.8p15+dfsg-2~1.2.2+dfsg1-4 500
500 https://deb.debian.org/debian-ports unstable/main hurd-i386 Packages
 1:4.2.8p15+dfsg-2~1.2.2+dfsg1-3 500
500 https://deb.debian.org/debian-ports unstable/main hurd-i386 Packages
 *** 1:4.2.8p15+dfsg-2~1.2.2+dfsg1-2+hurd.1 500
500 https://deb.debian.org/debian-ports unreleased/main
hurd-i386 Packages
100 /var/lib/dpkg/status

Martin-Éric

Bug#1058451: ntpsec: FTBFS [Hurd] change Build-Depends: systemd to [linux-any]

[Martin-Éric Racine]

On Mon, Dec 25, 2023 at 12:20 AM Richard Laager  wrote:
>
> On 2023-12-12 04:52, Martin-Éric Racine wrote:
> > Build-Depends: systemd must be changed to systemd [linux-any], since 
> > systemd has not been powerted to non-Linux platforms.
>
> I suspect that change would be necessary, but not sufficient.
>
> In commit 7f969a0ecab4ef3ab50defd4fe9d7e7a47817dbe, I wrote:
>Build-Depend on systemd
>
>This is required for the pkg-config file, so that waf will detect
>systemd and install the systemd units.

Only on linux-any.

> If past me was correct, without systemd at build-time, waf will not
> install the systemd units. Then we will end up with other failures in
> debian/rules or from the .install files.

Not installing them on platforms where systemd has not been ported is
the correct action.

> HURD is the only non-Linux platform that Debian supports these days,
> right? kFreeBSD is gone, IIRC.
>
> The ntpsec package (like ntp before it, IIRC) does not build on HURD
> anyway. From debian/rules:

It built enough to have ntpdate. The Hurd patch was even updated just
a few days before the version that added the build-depends on systemd.

> ifeq (hurd, $(DEB_HOST_ARCH_OS))
>  # hurd does not provided the system calls needed for ntpd to work.
>  exit 1
> endif
>
> I see a couple of ways forward here:
>
> A) I properly indicate this package does not support HURD.
>
> I think I would just replace the "Architecture: any" with
> "Architecture: linux-any" on binary packages in debian/control, but
> I would love confirmation on that.

Which is what this bug requested.

Martin-Éric

Bug#1057959: dhcpcd gets stopped during upgrade but never started again

[Martin-Éric Racine]

On Tue, 12 Dec 2023 00:18:57 +0100 Maximilian Engelhardt
 wrote:
> On Montag, 11. Dezember 2023 08:51:36 CET Martin-Éric Racine wrote:
> [...]
> >
> > Unless I misunderstood, this is due to a change of debhelper behavior
> > since compatibility level 10. This leaves me with two possible
> > solutions:
> >
> > 1) No dh_install option. This will restart after upgrade (default since dh
> > 10).
> >
> > 2) Add --no-stop-on-upgrade --no-restart-after-upgrade options. This
> > will explicitely disable stop and restart actions.
> >
> > Maximilian, which one of these two would make the most sense to you?
> >
> > Here, I only use the binaries via ifupdown (i.e. only dhcpcd-base), so
> > I have no preference.
> >
> > Martin-Éric
>
> Hi Martin-Éric,
>
> I think for me both options should work. I guess for maximising uptime it
> would make sense to not restart dhcpcd and if it is important enough (e.g. due
> a security bug) inform the user (e.g. via NEWS) that a manual restart should
> happen as soon as possible.
>
> Now that I think more about it, not stopping and starting automatically is
> probably the better option, because if something goes wrong during the update
> or the update is just stuck at a prompt it could else leave the system without
> network connectivity.
> Better that stopping and starting again some time later would probably be just
> doing an restart once (stop and directly start again without delay) if that's
> possible.
>
> Thanks,
> Maxi

I've uploaded the fix to unstable.

Since this is not the sort of urgent issue that would warrant a
separate update to Bookworm, I won't upload it there for now. However,
I'll definitely include it if there ever is a security issue that
requires an upload to Bookworm.

Martin-Éric

Bug#1058585: RFS: dhcpcd/1:10.0.5-5 -- DHCPv4 and DHCPv6 dual-stack client

[Martin-Éric Racine]

Package: sponsorship-requests
Severity: normal

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Dear mentors,

I am looking for a sponsor for my package "dhcpcd":

 * Package name : dhcpcd
   Version  : 1:10.0.5-5
   Upstream contact : Roy Marples 
 * URL  : https://roy.marples.name/projects/dhcpcd
 * License  : Expat, public-domain, ISC, BSD-3-Clause, 
BSD-2-Clause-NETBSD, GPL-3+, BSD-2
 * Vcs  : https://salsa.debian.org/debian/dhcpcd
   Section  : net

The source builds the following binary packages:

  dhcpcd-base - DHCPv4 and DHCPv6 dual-stack client (binaries and exit hooks)
  dhcpcd - DHCPv4 and DHCPv6 dual-stack client (init.d script & systemd unit)
  dhcpcd5 - DHCPv4 and DHCPv6 dual-stack client (dummy transitional package)

To access further information about this package, please visit the following 
URL:

  https://mentors.debian.net/package/dhcpcd/

Alternatively, you can download the package with 'dget' using this command:

  dget -x 
https://mentors.debian.net/debian/pool/main/d/dhcpcd/dhcpcd_10.0.5-5.dsc

Changes since the last upload:

 dhcpcd (1:10.0.5-5) unstable; urgency=medium
 .
   * [patches]
 - Remove all GNU/Hurd patches. Let Hurd porters handle that.
   * [control]
 = Breaks/Replaces: dhcpcd5 using (<< ${binary:Version}) variable.
   * [rules]
 + Add --no-stop-on-upgrade --no-restart-after-upgrade (Closes: #1057959).

Regards,
- -- 
Martin-Éric Racine


-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEyJACx3qL7GpObXOQrh+Cd8S017YFAmV5nqUACgkQrh+Cd8S0
17Z45Q//WTG+shwktJ5kduMQYjxEKK0UPe4XzClTRi7EWiwiaiRa1Og83Z3Zmpa9
B4rSJVDj++kkjqwBoD8kTDfmOIWlrpKRFTzXnJbi9XTtAOlB8MfVPhg4jWcVKhEp
vwtK8yKG41bPZOFdjkOy9ocTokoEn4+zG5kThazYQcauytnfL/QeOVd0ZtMl7yMq
Jdh9rBKxl0L+dOu50YJ+j6Jj2p2fkvFNk8NR0JljB+MRjuGJOl6HOmIlswt+Azly
M9XP0QE/iaV1i8Z2Anzm5wnAuw3y7dGGPjnesG3LB+DX7qIibWa1uBQCEWUguSPL
vjH7o7R90CxKqdW7uUTWAiV2an4fW5KNVpJIki6a2YjXbxkurnbmxU1FFTTHlyYe
Vm3X0Z2raHgTl36Mhp3MzbtMLHZ+uo6J9IcNosGCUXcIGhpjbomiIDt7tVG5gabL
AXZ2yrwgE3whdVWsyeEBN9uurQ4CrfoDJT4/ODgwTGG2bKrRIB03N02hT5gcRyGq
s4tbu/ehsqcfl+bc/PW8esN3Jo6NNymbmqO/DKdWGjcH9+hmKAQjRv5M6x3oYC4z
I8Ym0jPWuwdPOVXxDl2t1uKGnJ7oiXoiYU8QL7MpbTKpVtB7N9SlSwTuYvh73XBa
57x+cIOXSBo/YiaUONE+Qr9XNkycjDt/RaILL+QcoAEcxIrCls0=
=H3cY
-END PGP SIGNATURE-

Bug#1058451: ntpsec: FTBFS [Hurd] change Build-Depends: systemd to [linux-any]

[Martin-Éric Racine]

Source: ntpsec
Severity: important

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Build-Depends: systemd must be changed to systemd [linux-any], since systemd 
has not been powerted to non-Linux platforms.

Martin-Éric

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEyJACx3qL7GpObXOQrh+Cd8S017YFAmV4O3QACgkQrh+Cd8S0
17YJMA//dN97bYQU+07sobISsqryypzDaO6i/Ioci96Nbzq7ZXtv2ezsCVsVa7KG
aKFV1TD9vh4fXlVf5KorJg/qNS2RP7pK7G71lHMU0k8KVwAoPvONRWQw/5GfEkO3
4mjYIHIqoC7jUzW0W6g626CDxWRkzvaKlKzL7/IFbO77XXPixOU3uup1+4jL1O6T
6TDZRH9CNQNGUlocd6JeE9TH3v9tGELXlPMSJsif9H+aSXy7GbBiaCTvS/0Wunis
yzirO5hIGJA2PNMVnzCboh6HIWMAUITrPpt2l/y52RnEalDfPcbPytPJlT1/iUPE
vMfXeVeD3jFu5fzfSzXViOLZEAz+nM3Cjs1uawaxR1sdugtzkpp9GktB4bUwV+xK
Bmc6XJ45X/uRZCZFNho97Bo1z8PIaoFwEEF58sUR3PbcVC+RQ177Uc0uyaTPYvJM
DSXk5Y0jG6BxWZJC1sbb2URqWChXYKg3CtEFyZUKksIZixoeBIrC1MvB7ehKgMc0
r2Gtm9xw/u1uiDYTNy2sMVUjFS1Fl8N0H0UmwSBHlujIxrA92jAMZFwxu9f48aR9
f+LFPIfEXM6nrK27royUNCbU0qJ+7LzfhFLTxcRQFl3+rCsjQMrqAJ7PG+jUJ/9h
RkGmkIdqLpjck8knVzMql39VYnyrLhFSd+xDJBWCtTVZBxxTVnA=
=RgXH
-END PGP SIGNATURE-

Bug#1057959: dhcpcd gets stopped during upgrade but never started again

[Martin-Éric Racine]

On Mon, 11 Dec 2023 08:29:35 +0200
=?UTF-8?Q?Martin=2D=C3=89ric_Racine?= 
wrote:
> On Mon, 11 Dec 2023 07:52:53 +0200
> =?UTF-8?Q?Martin=2D=C3=89ric_Racine?= 
> wrote:
> > On Mon, 11 Dec 2023 00:25:45 +0100 Maximilian Engelhardt
> >  wrote:
> > > Package: dhcpcd
> > > Version: 1:9.4.1-24~deb12u3
> > > Severity: normal
> > > X-Debbugs-Cc: m...@daemonizer.de
> > >
> > > Examining dhcpcd.preinst and dhcpcd.postinst scripts indeed shows that 
> > > dhcpcd
> > > gets stopped in the preinst script, but never started again anywhere.
> >
> > These are added by dh_installinit and dh_installsystemd. Reassigning.
>
> Looking at debian/rules, I currently install the package with the
> following overrides:
>
> # Avoid starting the unconfigured service as it may break connectivity.
> override_dh_installinit:
> dh_installinit --name=dhcpcd --no-start
>
> override_dh_installsystemd:
> dh_installsystemd --name=dhcpcd --no-start
> dh_installsystemd --name=dhcpcd@ --no-start
>
> The manual for both dh_scripts says that --no-start will update the
> files but neither stop or start the services (which is expected for a
> DHCP client: the connection must remain during the upgrade). This is
> apparently not the case. The additions made by the helpers stop the
> service (oops!) and never restart it (oops again!).

Unless I misunderstood, this is due to a change of debhelper behavior
since compatibility level 10. This leaves me with two possible
solutions:

1) No dh_install option. This will restart after upgrade (default since dh 10).

2) Add --no-stop-on-upgrade --no-restart-after-upgrade options. This
will explicitely disable stop and restart actions.

Maximilian, which one of these two would make the most sense to you?

Here, I only use the binaries via ifupdown (i.e. only dhcpcd-base), so
I have no preference.

Martin-Éric

Bug#1057959: dhcpcd gets stopped during upgrade but never started again

[Martin-Éric Racine]

On Mon, 11 Dec 2023 07:52:53 +0200
=?UTF-8?Q?Martin=2D=C3=89ric_Racine?= 
wrote:
> On Mon, 11 Dec 2023 00:25:45 +0100 Maximilian Engelhardt
>  wrote:
> > Package: dhcpcd
> > Version: 1:9.4.1-24~deb12u3
> > Severity: normal
> > X-Debbugs-Cc: m...@daemonizer.de
> >
> > Examining dhcpcd.preinst and dhcpcd.postinst scripts indeed shows that 
> > dhcpcd
> > gets stopped in the preinst script, but never started again anywhere.
>
> These are added by dh_installinit and dh_installsystemd. Reassigning.

Looking at debian/rules, I currently install the package with the
following overrides:

# Avoid starting the unconfigured service as it may break connectivity.
override_dh_installinit:
dh_installinit --name=dhcpcd --no-start

override_dh_installsystemd:
dh_installsystemd --name=dhcpcd --no-start
dh_installsystemd --name=dhcpcd@ --no-start

The manual for both dh_scripts says that --no-start will update the
files but neither stop or start the services (which is expected for a
DHCP client: the connection must remain during the upgrade). This is
apparently not the case. The additions made by the helpers stop the
service (oops!) and never restart it (oops again!).

Martin-Éric

Bug#1057959: dhcpcd gets stopped during upgrade but never started again

[Martin-Éric Racine]

reassign 1057959 debhelper
done

On Mon, 11 Dec 2023 00:25:45 +0100 Maximilian Engelhardt
 wrote:
> Package: dhcpcd
> Version: 1:9.4.1-24~deb12u3
> Severity: normal
> X-Debbugs-Cc: m...@daemonizer.de
>
> Hi,
> during the recent point release I noticed that during the unattended-upgrades
> run dhcpcd was stopped but never started again. This is undesired as it breaks
> internet connection for me and I need to manually start it again.
>
> Examining dhcpcd.preinst and dhcpcd.postinst scripts indeed shows that dhcpcd
> gets stopped in the preinst script, but never started again anywhere.

These are added by dh_installinit and dh_installsystemd. Reassigning.

Martin-Éric

Bug#1057833: sudo: [Hurd i386] upgrade from 1.9.14p2 to 1.9.15p2 dies with malloc error

[Martin-Éric Racine]

On Sat, Dec 9, 2023 at 2:41 PM Marc Haber
 wrote:
>
> On Sat, Dec 09, 2023 at 12:40:46PM +0200, Martin-Éric Racine wrote:
> > Since the upgrade from 1.9.14p2 to 1.9.15p in unstable, sudo aborts with a 
> > malloc error on Hurd i386.
> >
> > $ LC_ALL=C sudo apt-get install acpi-support-base
> > malloc(): invalid next size (unsorted)
> > Keskeytetty
>
> Does this also happen with other commands? Can you obtain a backtrace?

Only with sudo.  Cannot obtain a backtrace because gdb reports
problems when trying to run it on sudo 1.9.15.

> Does this also happen when you take the old sudo source package from
> trixie and build locally with current unstable?

Locally-built 1.9.14p2-1 on this host running unstable works as expected.

> > -- Configuration Files:
> > /etc/sudoers [Errno 1073741837] Lupa evätty: '/etc/sudoers'
> > /etc/sudoers.d/README [Errno 1073741837] Lupa evätty: 
> > '/etc/sudoers.d/README'

Permission denied: /path/to/file

Martin-Éric

Bug#1057833: sudo: [Hurd i386] upgrade from 1.9.14p2 to 1.9.15p2 dies with malloc error

[Martin-Éric Racine]

Package: sudo
Version: 1.9.15p2-2
Severity: important

Since the upgrade from 1.9.14p2 to 1.9.15p in unstable, sudo aborts with a 
malloc error on Hurd i386.

$ LC_ALL=C sudo apt-get install acpi-support-base
malloc(): invalid next size (unsorted)
Keskeytetty

-- System Information:
Debian Release: trixie/sid
  APT prefers unreleased
  APT policy: (500, 'unreleased'), (500, 'unstable')
Architecture: hurd-i386 (i686-AT386)

Kernel: GNU-Mach 1.8+git20230830-486/Hurd-0.9
Locale: LANG=fi_FI.UTF-8, LC_CTYPE=fi_FI.UTF-8 (charmap=UTF-8), LANGUAGE=fi:en
Shell: /bin/sh linked to /usr/bin/dash
Init: sysvinit (via /sbin/init)

Versions of packages sudo depends on:
ii  init-system-helpers  1.66
ii  libc0.3  2.37-13
ii  libpam-modules   1.4.0-10
ii  libpam0g 1.4.0-10
ii  libssl3  3.1.4-2
ii  zlib1g   1:1.3.dfsg-3

sudo recommends no packages.

sudo suggests no packages.

-- Configuration Files:
/etc/sudoers [Errno 1073741837] Lupa evätty: '/etc/sudoers'
/etc/sudoers.d/README [Errno 1073741837] Lupa evätty: '/etc/sudoers.d/README'

-- no debconf information

Bug#1053436: dhcpcd-base: dhcpcd stops listening on port 68 after several days

[Martin-Éric Racine]

Excellent.  Closing the bug then.

Martin-Éric

On Wed, Dec 6, 2023 at 6:36 PM Ron Murray  wrote:
>
> Sorry, forgot to let you know. It's been happily running on 10.0.3-1 for a 
> couple of weeks now, with no errors. I have a script that checks all daemons 
> running every night, so if there had been any errors, it would have notified 
> me.
>
> Thanks,
>
>  .Ron
>
> --
> Ron Murray 
> PGP Fingerprint: 4D99 70E3 2317 334B 141E  7B63 12F7 E865 B5E2 E761
>
> Martin-Éric Racine wrote:
>
>
> On Wed, Oct 25, 2023 at 3:35 AM Ron Murray  wrote:
>
>>
> OK. Now running version 10.0.3-1. I'll let you know how it goes.
>
> Testing now has 10.0.4-1, while unstable has 10.0.5-2. Does either one
> fix the issue for you?
>
>
> Martin-Éric

Bug#1057634: /sbin/hwclock: unrecognized option '--rtc=/dev/rtc0'

[Martin-Éric Racine]

On Wed, Dec 6, 2023 at 4:57 PM Mark Hindley  wrote:
> I also propose downgrading the initscripts Depends: util-linux-extra to
> Recommends. Even on non-systemd systems, hwclock.sh is far from essential as
> many now use NTP and hwclock.sh already handles a missing /sbin/hwclock
> gracefully.

The dependency currently is a mere Suggests. What causes extra to get
installed is that it currently has priority Standard.  That makes
debian-installer pull it on default installs, since it pulls
everything Standard or higher, unless explicitly told not to do so.

Martin-Éric

Bug#1057634: /sbin/hwclock: unrecognized option '--rtc=/dev/rtc0'

[Martin-Éric Racine]

On Wed, Dec 6, 2023 at 4:57 PM Mark Hindley  wrote:
>
> Control: tags -1 = patch
>
> Svante,
>
> On Wed, Dec 06, 2023 at 02:20:09PM +0100, Svante Signell wrote:
> > On a qemu Hurd image:
> >
> > /sbin/hwclock --help | grep rtc
> > --directisa use the ISA bus instead of /dev/rtc0 access
> >
> > /sbin/hwclock --directisa --show
> > 2023-12-06 14:17:54.949951+01:00
>
> Many thanks, that is a great help.
>
> Could you and Martin test this patch, please?
>
> I also propose downgrading the initscripts Depends: util-linux-extra to
> Recommends. Even on non-systemd systems, hwclock.sh is far from essential as
> many now use NTP and hwclock.sh already handles a missing /sbin/hwclock
> gracefully.
>
> Mark
>
> commit acdbb98f05db8f24ddc9e72adb2b6a0982e69748
> Author: Mark Hindley 
> Date:   Wed Dec 6 10:20:41 2023 +
>
> hwclock.sh: support HURD direct ISA I/O.
>
> Closes: #1057634
>
> diff --git a/debian/src/initscripts/etc/init.d/hwclock.sh 
> b/debian/src/initscripts/etc/init.d/hwclock.sh
> index a9872b64..055508e7 100644
> --- a/debian/src/initscripts/etc/init.d/hwclock.sh
> +++ b/debian/src/initscripts/etc/init.d/hwclock.sh
> @@ -38,13 +38,24 @@ hwclocksh()
>  # Updates the Hardware Clock with the System Clock time.
>  # This will *override* any changes made to the Hardware Clock,
>  # for example by the Linux kernel when NTP is in use.
> -log_action_msg "Saving the system clock to /dev/$HCTOSYS_DEVICE"
> -if /sbin/hwclock --rtc=/dev/$HCTOSYS_DEVICE --systohc; then
> -verbose_log_action_msg "Hardware Clock updated to `date`"
> -fi
> +   if [ "$(uname -s)" = GNU ]; then
> +   log_action_msg "Saving the system clock to CMOS"
> +   /sbin/hwclock --directisa --systohc
> +   else
> +   log_action_msg "Saving the system clock to 
> /dev/$HCTOSYS_DEVICE"
> +   /sbin/hwclock --rtc=/dev/$HCTOSYS_DEVICE --systohc
> +   fi
> +if [ $? -eq 0 ]; then
> +   verbose_log_action_msg "Hardware Clock updated to `date`"
> +   fi
> +
>  ;;
>  show)
> -/sbin/hwclock --rtc=/dev/$HCTOSYS_DEVICE --show
> +   if [ "$(uname -s)" = GNU ]; then
> +   /sbin/hwclock --directisa --show
> +   else
> +   /sbin/hwclock --rtc=/dev/$HCTOSYS_DEVICE --show
> +   fi
>  ;;
>  *)
>  log_success_msg "Usage: hwclock.sh 
> {stop|reload|force-reload|show}"

Please note that the start target refers to a non-existing
/usr/lib/udev/rules.d/85-hwclock.rules.  The correct file is
/usr/lib/udev/rules.d/hwclock.rules instead. That file contains a
reference to rtc0 that probably needs fixing for Hurd as well.

Anyhow, what I get with the patched init script:

[2023-12-06 18:04](HURD i386)perkelix@pxeth:~$ LC_ALL=C sudo
/etc/init.d/hwclock.sh start
[2023-12-06 18:04](HURD i386)perkelix@pxeth:~$ LC_ALL=C sudo
/etc/init.d/hwclock.sh restart
Saving the system clock to CMOS.
Hardware Clock updated to Wed Dec  6 18:05:05 EET 2023.
[2023-12-06 18:05](HURD i386)perkelix@pxeth:~$ LC_ALL=C sudo
/etc/init.d/hwclock.sh stop
Saving the system clock to CMOS.
Hardware Clock updated to Wed Dec  6 18:05:12 EET 2023.
[2023-12-06 18:05](HURD i386)perkelix@pxeth:~$ LC_ALL=C sudo
/etc/init.d/hwclock.sh show
2023-12-06 18:05:18.129566+02:00

Martin-Éric

Bug#1057634: Re: Bug#1057634: /sbin/hwclock: unrecognized option '--rtc=/dev/rtc0'

[Martin-Éric Racine]

On Wed, Dec 6, 2023 at 3:46 PM Svante Signell  wrote:
> -- Forwarded message --
> From: Svante Signell 
> To: debian-init-divers...@chiark.greenend.org.uk
> Cc:
> Bcc:
> Date: Wed, 06 Dec 2023 14:20:09 +0100
> Subject: Re: Bug#1057634: /sbin/hwclock: unrecognized option '--rtc=/dev/rtc0'
> On Wed, 2023-12-06 at 12:07 +, Mark Hindley wrote:
> > Chris,
> >
> > Thanks for your input.
> >
> > On Wed, Dec 06, 2023 at 11:56:56AM +0100, Chris Hofstaedtler wrote:
> > > * Mark Hindley  [231206 11:42]:
> > > > Is hwclock actually useful on Hurd? I (naively) expected it to be linux
> > > > only. But src:util-linux still ships it[1]. Or is the HCTOSYS_DEVICE 
> > > > used
> > > > in the
> > > > initscripts just wrong on Hurd?
> > >
> > > I have zero knowledge about hurd, but it looks like[1] hwclock is built
> > > with CMOS support on hurd.  So maybe it could work?
> > >
> > > It certainly is built without the RTC support, so --rtc=... doesn't
> > > work.
> >
> > A superficial attempt on exodar.debian.net isn't particularly encouraging:
> >
> > leepen@exodar:~$ /sbin/hwclock --test
> > hwclock from util-linux 2.39.2
> > System Time: 1701863851.810595
> > No usable clock interface found.
> > hwclock: Cannot access the Hardware Clock via any known method.
> >
> > I suggest we wait for a response from the Hurd experts. But maybe
> > util-linux-extra should be arch:linux-any?
> >
>
> On a qemu Hurd image:
>
> /sbin/hwclock --help | grep rtc
> --directisa use the ISA bus instead of /dev/rtc0 access
>
> /sbin/hwclock --directisa --show
> 2023-12-06 14:17:54.949951+01:00

That works on my Hurd-i386 host, and it shows the correct time.

Init scripts therefore need to use "--rtc=/dev/rtc0" on Linux hosts
and "--directisa" on Hurd hosts.

Martin-Éric

Bug#1057634: /sbin/hwclock: unrecognized option '--rtc=/dev/rtc0'

[Martin-Éric Racine]

On Wed, Dec 6, 2023 at 12:42 PM Mark Hindley  wrote:
> On Wed, Dec 06, 2023 at 11:16:57AM +0200, Martin-Éric Racine wrote:
> > Package: initscripts
> > Version: 3.08-3
> > Severity: important
> >
> > $ LC_ALL=C sudo invoke-rc.d hwclock.sh restart
> > Saving the system clock to /dev/rtc0.
> > /sbin/hwclock: unrecognized option '--rtc=/dev/rtc0'
> >
> >   APT prefers unreleased
> >   APT policy: (500, 'unreleased'), (500, 'unstable')
> > Architecture: hurd-i386 (i686-AT386)
> >
> > Kernel: GNU-Mach 1.8+git20230830-486/Hurd-0.9
>
> So you are running Hurd. I have very little experience of that arch, so would
> appreciate some more information from you.

I just barely got around installing Hurd on a spare host, but I'll try
answering them anyway.

> > Locale: LANG=fi_FI.UTF-8, LC_CTYPE=fi_FI.UTF-8 (charmap=UTF-8), 
> > LANGUAGE=fi:en
> > Shell: /bin/sh linked to /usr/bin/dash
> > Init: sysvinit (via /sbin/init)
> >
> > Versions of packages initscripts depends on:
> > ii  sysv-rc   3.08-3
> > ii  sysvinit-utils3.08-3
> > ii  util-linux-extra  2.39.3-2
>
> Is hwclock actually useful on Hurd? I (naively) expected it to be linux
> only. But src:util-linux still ships it[1]. Or is the HCTOSYS_DEVICE used in 
> the
> initscripts just wrong on Hurd?

Hurd mailing list in CC might be able to answer that one.

> Does your Hurd system usually have util-linux-extra installed or was it only
> pulled in by the initscript dependency?

$ dpkg -l | grep linux
ii  util-linux  2.39.3-2
hurd-i386miscellaneous system utilities
ii  util-linux-extra2.39.3-2
hurd-i386interactive login tools

It was probably pulled-in due to having priority Standard.

Martin-Éric

Bug#1057634: /sbin/hwclock: unrecognized option '--rtc=/dev/rtc0'

[Martin-Éric Racine]

Package: initscripts
Version: 3.08-3
Severity: important

$ LC_ALL=C sudo invoke-rc.d hwclock.sh restart
Saving the system clock to /dev/rtc0.
/sbin/hwclock: unrecognized option '--rtc=/dev/rtc0'

  APT prefers unreleased
  APT policy: (500, 'unreleased'), (500, 'unstable')
Architecture: hurd-i386 (i686-AT386)

Kernel: GNU-Mach 1.8+git20230830-486/Hurd-0.9
Locale: LANG=fi_FI.UTF-8, LC_CTYPE=fi_FI.UTF-8 (charmap=UTF-8), LANGUAGE=fi:en
Shell: /bin/sh linked to /usr/bin/dash
Init: sysvinit (via /sbin/init)

Versions of packages initscripts depends on:
ii  sysv-rc   3.08-3
ii  sysvinit-utils3.08-3
ii  util-linux-extra  2.39.3-2

Versions of packages initscripts recommends:
ii  e2fsprogs  1.46.6-1
ii  psmisc 23.5-1

initscripts suggests no packages.

-- no debconf information

Bug#1057397: rsyslog: [Hurd i386] start fails with Could not load module imklog

[Martin-Éric Racine]

Package: rsyslog
Version: 8.39.0-1+hurd.1
Severity: important
Usertags: hurd

As per Subject, rsyslog fails to start with the above error on hurd-i386.

Martin-Éric

-- System Information:
Debian Release: trixie/sid
  APT prefers unreleased
  APT policy: (500, 'unreleased'), (500, 'unstable')
Architecture: hurd-i386 (i686-AT386)

Kernel: GNU-Mach 1.8+git20230830-486/Hurd-0.9
Locale: LANG=C, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: sysvinit (via /sbin/init)

Versions of packages rsyslog depends on:
ii  libc0.32.37-13
ii  libestr0   0.1.11-1
ii  libfastjson4   1.2304.0-1
ii  liblognorm52.0.6-4
ii  libuuid1   2.39.2-6
ii  lsb-base   11.6
ii  sysvinit-utils [lsb-base]  3.08-3
ii  zlib1g 1:1.3.dfsg-3

Versions of packages rsyslog recommends:
ii  logrotate  3.21.0-1

Versions of packages rsyslog suggests:
pn  rsyslog-doc
pn  rsyslog-gnutls 
pn  rsyslog-gssapi 
pn  rsyslog-mongodb
pn  rsyslog-mysql | rsyslog-pgsql  
pn  rsyslog-relp   

-- no debconf information

Bug#1056565: dhcpcd-base: fails to write multiple search domains to /etc/resolv.conf

[Martin-Éric Racine]

On Sat, Dec 2, 2023 at 8:20 PM Francesco Poli  wrote:
>
> On Mon, 27 Nov 2023 11:12:45 +0200 Martin-Éric Racine wrote:
>
> > On Sat, 25 Nov 2023 00:38:25 +0100 Francesco Poli
> >  wrote:
> > > On Thu, 23 Nov 2023 14:00:12 +0200 Martin-Éric Racine wrote:
> [...]
> > > > You might wanna check whether Rocky Linux has patched their DHCP
> > > > clients or altered their default dhcpcd.conf to make this succeed. If
> > > > that's the case, please point me to the relevant changes.
> > >
> > > AFAICT, the Rocky Linux machine has the ISC DHCP client
> > > and /etc/resolv.conf is written by a script /usr/sbin/dhclient-script,
> > > which obtains data from the ISC DHCP client.
> >
> > That's not what I asked.
>
> I am sorry, if I misunderstood your request.
> I thought you were asking to be pointed to changes relevant to dhcpcd.

To dhcpcd, not ISC dhclient.

> What I am sure is that dhcpcd (but also isc-dhcp-client) in Debian
> failed to get the two search domains provided by the DHCP server in the
> domain search list (DHCP option 119), while a Rocky Linux ISC DHCP
> client and a Windows client correctly got the two search domains.

That was already understood.

> As far as I understand, isc-dhcp-client is EOL and will be removed from
> Debian in the near future.

Which is completely irrelevant to this bug.

Martin-Éric

Bug#1056565: dhcpcd-base: fails to write multiple search domains to /etc/resolv.conf

[Martin-Éric Racine]

On Sat, 2 Dec 2023 19:19:05 +0100 Francesco Poli
 wrote:
> On Mon, 27 Nov 2023 11:12:45 +0200 Martin-Éric Racine wrote:
>
> > On Sat, 25 Nov 2023 00:38:25 +0100 Francesco Poli
> >  wrote:
> > > On Thu, 23 Nov 2023 14:00:12 +0200 Martin-Éric Racine wrote:
> [...]
> > > > You might wanna check whether Rocky Linux has patched their DHCP
> > > > clients or altered their default dhcpcd.conf to make this succeed. If
> > > > that's the case, please point me to the relevant changes.
> > >
> > > AFAICT, the Rocky Linux machine has the ISC DHCP client
> > > and /etc/resolv.conf is written by a script /usr/sbin/dhclient-script,
> > > which obtains data from the ISC DHCP client.
> >
> > That's not what I asked.
>
> I am sorry, if I misunderstood your request.
> I thought you were asking to be pointed to changes relevant to dhcpcd.
> Since the DHCP client I tested on Rocky Linux is the ISC DHCP client, I
> considered any patches for that client as irrelevant to dhcpcd (which
> is not a fork of the ISC DHCP client, is it?).
>
> Anyway, I tried to search for the Rocky Linux ISC DHCP client source
> package.

This is the dhcpcd package. Looking for Rocky changes to ISC is irrelevant.

If you experience issue with dhclient, reassign this bug to isc-dhcp-client.

Martin-Éric

Bug#1053436: dhcpcd-base: dhcpcd stops listening on port 68 after several days

[Martin-Éric Racine]

On Sat, 18 Nov 2023 15:55:20 +0200
=?UTF-8?Q?Martin=2D=C3=89ric_Racine?= 
wrote:
> On Wed, Oct 25, 2023 at 3:35 AM Ron Murray  wrote:
> > OK. Now running version 10.0.3-1. I'll let you know how it goes.
>
> Testing now has 10.0.4-1, while unstable has 10.0.5-2. Does either one
> fix the issue for you?

Any news on this?

Martin-Éric

Bug#1057262: RFS: upgrade-system/1.9.2.0 -- command for upgrading and sanitizing a Debian system

[Martin-Éric Racine]

Package: sponsorship-requests
Severity: normal

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Dear mentors,

I am looking for a sponsor for my package "upgrade-system":

 * Package name : upgrade-system
   Version  : 1.9.2.0
   Upstream contact : Martin-Éric Racine 
 * License  : GPL-2+
   Section  : admin

The source builds the following binary packages:

  upgrade-system - command for upgrading and sanitizing a Debian system

To access further information about this package, please visit the following 
URL:

  https://mentors.debian.net/package/upgrade-system/

Alternatively, you can download the package with 'dget' using this command:

  dget -x 
https://mentors.debian.net/debian/pool/main/u/upgrade-system/upgrade-system_1.9.2.0.dsc

Changes since the last upload:

 upgrade-system (1.9.2.0) unstable; urgency=medium
 .
   * [upgrade-system]
 + Added test for setterm. Not available on Hurd.
   * [control]
 = Bumped Standards-Version to 4.6.2 (no change required).

Regards,
- -- 
Martin-Éric Racine


-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEyJACx3qL7GpObXOQrh+Cd8S017YFAmVrAcIACgkQrh+Cd8S0
17ZQAg/+JPG4ZnezG+1DWv0jSWXm54z38OETNG4T6/Frej9YOr26DKu1RiGPwEO+
mdo1qzEhv/f7DBCAH3aDFWLxcBhncq3ItkD95ncZKTGz+ebGoeehQ0CWc88WGjL3
a7EQHd1zVK4mL7fZmxm3gEd0EqWbgtjm9BEZTecWBrkK07AyXp1dqI85JOqTpdcD
T7vLvJZjqFQpsmO1MPh2vNvHz15z+VkFdgqpKneiRUB9h+1R72mbw1YurMTthws8
5Tfm5L7pzLRU3Xy5kSQKmoqow1RlBtaIjPygD9ZkIvVstW2+pTj7WdhfOtfj+gvO
o/acofRjr4k7SdbyP6F6+bmGuGRkVCmFyc/KOwRWSHS/VO5PGQcmgQWpbTrr23y0
vuNvliwEN7sIEQWexWrm6zSRZ5cnaNX5BDuI/EqqLNkPOiTYNZaCPU1Nhoercze0
zzh9invI4m9OAT95jUTv+3Cf9ErrVgHDtOrmKSp0CkldMP4VCFBCQUZtiHsRthax
Fw0rTQfh38jzVwSkQsGexIzsFEyf+u58822WmvALzIpkO+VF14Lzz9jAn9DLIn/C
/b6Pwp915rmRcoovaxPOF8gTjj4eCn6wp2skree7hLFCD+47HH11YvQGk8YjaeLY
5NfGwirwAgietA++Of8sxu3D4neUmeAfrjKswrR3xeKbTpVAKzQ=
=BzGo
-END PGP SIGNATURE-

Bug#1057259: flowblade: please package 2.12

[Martin-Éric Racine]

Package: flowblade
Severity: normal

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Upstream released 2.12 a few days ago. Could you please package it?

Thanks!
Martin-Éric

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEyJACx3qL7GpObXOQrh+Cd8S017YFAmVq/aUACgkQrh+Cd8S0
17ZsiRAAoq1l/hhox8aPfLbBvkBl+o0Wihr+cV4Kv0S7UcXp6noEEZOdvSPjx+dq
DpQOrOQp6NiIX83dyFIALOtSkT926W46iSCe2jkaGQ8BEGk8lIOpohzff2BCkXx8
Mg7oTn5ObgEnyFJqfeVsXgqw8cuqxu8Y214Lm4N5slEiGbAgrlojpTK03yUwcrbp
aFcQrrsaMANJkgppl0GTAzgMz9HvLL2HW5733zbPptY7iRSu7mOZes6RltHoWihx
Q/QCoQR6rFJ+0vmmniH00G/8zmqQGJG6VoMEBmS6xpYhi43tgCVMST8RowYFUqdG
cQYo0j35ZDP49Hbtrw/Ri7s1mNDnDZuhUlha8pXIavdHMV0zbd4O1VlSl8u2yFCy
ScTOmqm8jYV4zrcGGaV0HYDxtYWSY/Lf366OirJMVQL1wl9Oa1+aXeo59BaTU04P
1Xoi6OnztiWVneQyrDd87TSFv8fvsP2Tuk/qdk3BcRk/IniOe3yR8lqD6vil5BgY
9CSdIc6bIjF8pbCui1NeBejN0M8APUvR9eUW0i2mheiNQEng/nzd0WplW1o/JI3s
tY6keDRhZ/Zw9Eo3qjlf3aO0yVfxgQGAC0SOmxe+8NKuXoC79ouUlE96k88bqBS1
NBn9NgKWBCSC5p3bO/mIgT6mizD5RQYVX+etGMdhbS2HJlp0084=
=GATC
-END PGP SIGNATURE-

Bug#1056690: RFS: dhcpcd/1:10.0.5-4 -- DHCPv4 and DHCPv6 dual-stack client

[Martin-Éric Racine]

On Tue, Nov 28, 2023 at 10:05 AM Santiago Ruano Rincón
 wrote:
>
> El 26/11/23 a las 10:53, Tobias Frost escribió:
> > Control: tags -1 moreinfo
> >
> > As Daniel said, this should be done on a VM, or if the hardware is
> > important, on a porter box.
> >
> > See https://dsa.debian.org/doc/guest-account/
> > and then go to https://nm.debian.org/wizard to request an account.
>
> Just to give a +1 to this. Having access to exodar.debian.net should be
> quite easy.
>
> And thanks a lot for your work.

Hurd porter Svante Signell recently mentioned that he had already
ported an earlier release and offered to look into updating his port.
I'll let him take care of that part.

Martin-Éric

Bug#1057023: devscripts: 'debclean --cleandebs' should also remove .buildinfo

[Martin-Éric Racine]

Package: devscripts
Version: 2.23.6
Severity: normal

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

In its current form, 'debclean --cleandebs' leaves .buildinfo files. It would 
be desirable to remove these too.

Martin-Éric

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEyJACx3qL7GpObXOQrh+Cd8S017YFAmVlkdsACgkQrh+Cd8S0
17ZezQ/+P2rIV0yOf+2NMpboTXI3dvHlLggHKGYxLRCzA4e/oAMMoaKDD9S+KcMH
02trR564dBs/RbUq9veEenHVQGFWGWJjKNqK9Cpk742qXEoFIzdBm9poT2/ScV7Y
qYtabYft5n74yW9b1cOYcWMaYizRw2eXD/dBQOZL5hrDLTbcIvjcs9Oj1qBnFZ+f
ed9MyugxMAOkOj2rwTUNqJdaH7A5e2GUVHpNDuzk7PzeYP0Vk+GdLWlOOYdUpmm/
rJk6+1xHT5/ivmZyt6QpoJR+kyn4WLo5OveI7tdz5hiJaOL7q81IAaZ6KuT7JZSQ
RuS6f9fczA1aW0vBGCU60179YPqzrQy4UixgvzKtdGZnGXBsWM3tjMZK0fSL+27U
+tCDWM9OgM9JU6tVkPniSQxYjHWJIcYnE4xlpXh7/KyLf651Ro0NPhJCtY3NHyCq
hLGoD0/hSRfZZLW5MCl8EaTLX1b2TXG9U4W02VUZbwCVGx2+bmfCph8r4giTnzoC
loUySiMMM98t8a9gRLr4a3obYdp5BqRqw2Z6u+haCV7xCynB9XYD0MXTrHSPP+kp
7rBBtgLJER0LNsiHft7N0TTQPezsC2nfnpWFgciRrj8CAPV17/zHwEwjiNKs1vii
0id8N7g0sc4rfJBzScDtktTtebxJ0XBwXI0QxDyDeu/qtk/DU3s=
=bwjk
-END PGP SIGNATURE-

Bug#1056565: dhcpcd-base: fails to write multiple search domains to /etc/resolv.conf

[Martin-Éric Racine]

On Sat, 25 Nov 2023 00:38:25 +0100 Francesco Poli
 wrote:
> On Thu, 23 Nov 2023 14:00:12 +0200 Martin-Éric Racine wrote:
>
> > On Thu, 23 Nov 2023 09:01:34 +0100 "Francesco Poli (wintermute)"
> >  wrote:
> [...]
> > > When I use dhcpcd-base as a DHCP client
> [...]
> > > This lacks the two search domains I was expecting.
> > > To be honest, the isc-dhcp-client Debian package
> > > behaves similarly (somehow failing to write OTHERDOMAIN as
> > > second search domain).
> > >
> > > But Rocky Linux clients (on the same network, with the ISC
> > > DHCP client and ifup/ifdown mechanism) correctly set the
> > > resolv.conf with the two search domains
> [...]
> > > Even Windows clients (on the same network) correctly obtain
> > > the two search domains...
> >
> > You might wanna check whether Rocky Linux has patched their DHCP
> > clients or altered their default dhcpcd.conf to make this succeed. If
> > that's the case, please point me to the relevant changes.
>
> AFAICT, the Rocky Linux machine has the ISC DHCP client
> and /etc/resolv.conf is written by a script /usr/sbin/dhclient-script,
> which obtains data from the ISC DHCP client.

That's not what I asked.

Martin-Éric

Bug#1056690: RFS: dhcpcd/1:10.0.5-4 -- DHCPv4 and DHCPv6 dual-stack client

[Martin-Éric Racine]

On Fri, Nov 24, 2023 at 9:30 PM Daniel Gröber  wrote:
> On Fri, Nov 24, 2023 at 09:03:37PM +0200, Martin-Éric Racine wrote:
> > On Fri, Nov 24, 2023 at 8:59 PM Daniel Gröber  wrote:
> > > On Fri, Nov 24, 2023 at 06:55:44PM +0200, Martin-Éric Racine wrote:
> > > > dhcpcd (1:10.0.5-4) unstable; urgency=medium
> > > > .
> > > >* Attempt to fix the GNU/Hurd build.
> > > >  + 003_fix_FTBFS_on_Hurd.patch
> > >
> > > Does upstream even support hurd? Looking at ./configure:
> > >
> > > gnu*) OS=hurd;; # No HURD support as yet
> >
> > Upstream never attempted to support it. I am.
>
> Looking the last your three dhcpcd revisions I wonder if you shouldn't be
> debugging these fundamental build issues on a porterbox or in a VM rather
> than through the buildds?

I don't have access to the former and am not in a position to setup the later.
Anyhow, doing this via the buildd has the advantage of ensuring that I
don't break anything for existing ports.

Martin-Éric

Bug#1056690: RFS: dhcpcd/1:10.0.5-4 -- DHCPv4 and DHCPv6 dual-stack client

[Martin-Éric Racine]

On Fri, Nov 24, 2023 at 8:59 PM Daniel Gröber  wrote:
> On Fri, Nov 24, 2023 at 06:55:44PM +0200, Martin-Éric Racine wrote:
> > dhcpcd (1:10.0.5-4) unstable; urgency=medium
> > .
> >* Attempt to fix the GNU/Hurd build.
> >  + 003_fix_FTBFS_on_Hurd.patch
>
> Does upstream even support hurd? Looking at ./configure:
>
> gnu*) OS=hurd;; # No HURD support as yet

Upstream never attempted to support it. I am.

Martin-Éric

Bug#1056690: RFS: dhcpcd/1:10.0.5-4 -- DHCPv4 and DHCPv6 dual-stack client

[Martin-Éric Racine]

Package: sponsorship-requests
Severity: important
Tags: ftbfs patch

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Dear mentors,

I am looking for a sponsor for my package "dhcpcd":

* Package name : dhcpcd
   Version  : 1:10.0.5-4
   Upstream contact : Roy Marples 
* URL  : https://roy.marples.name/projects/dhcpcd
* License  : Expat, public-domain, ISC, BSD-3-Clause, 
BSD-2-Clause-NETBSD, GPL-3+, BSD-2
* Vcs  : https://salsa.debian.org/debian/dhcpcd
   Section  : net

The source builds the following binary packages:

  dhcpcd-base - DHCPv4 and DHCPv6 dual-stack client (binaries and exit hooks)
  dhcpcd - DHCPv4 and DHCPv6 dual-stack client (init.d script & systemd unit)
  dhcpcd5 - DHCPv4 and DHCPv6 dual-stack client (dummy transitional package)

To access further information about this package, please visit the following 
URL:

  https://mentors.debian.net/package/dhcpcd/

Alternatively, you can download the package with 'dget' using this command:

  dget -x 
https://mentors.debian.net/debian/pool/main/d/dhcpcd/dhcpcd_10.0.5-4.dsc

Changes since the last upload:

dhcpcd (1:10.0.5-4) unstable; urgency=medium
.
   * Attempt to fix the GNU/Hurd build.
 + 003_fix_FTBFS_on_Hurd.patch

Regards,
Martin-Éric


-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEyJACx3qL7GpObXOQrh+Cd8S017YFAmVg1ZAACgkQrh+Cd8S0
17b/7RAAoa1y2n29K6JsaI0Hnq+iFo0GEu638+AFl3tMfUwUgZt4s9hpqsrzkOcz
T2LtEGtTmPCNairmC/KWMN/tqSuLR/P9l8snD04DJi6aSYQahqVOSEqb/Jdah+C9
f2E5BxLwXY2CAfSPsl+7hb5VudLfB0zu2J4Xb6Olfyn2FpJ5HyLFjo7i4cFWrZ4c
feDpRzXpp87sJrvKQJbQRWMqMGbCYcDoYi0c93PxS7V0xJn6dQFpg0xOreH+CaW0
v18nKw6HdCJJAuiBJlngFqsdcEVrot4prDEUf5/eejnFvHcS1IEmdLfsFmKUOpUN
t4vwX3VW5JOflSTWSOSDHnidNG5lIBpKYP2ryYEl74GyysTYX2DSsugtDpDfyiDD
MIFcXPy8X3DFRZNaAZxs66pSo2SGBkDMTLKlvv/1GK7RQnl9iS24EGK7kAmwGXVN
NJg5JPUKJytT4DOz2f3no4I2hYRvewoJXydWnOugk/LBFTHRqwf13d0s4pC3mXDl
UWzQuU2Moqv/vt15Z2v/CgVk1CDseddjE40hVJK2JMhwBJcMzuYcgEv2kfGAPeJi
WLTZgmsgH3dfK0itCY7xPJtMhuyCAueo5hsp/bDLkT/3cTFtzhxknb8yeWZ57sX2
Nwucl7sfsyV3Ilhyz2mM//wfh+X0/ACR1tRvnZDQz+reKYxUQio=
=+eLR
-END PGP SIGNATURE-

Bug#1056565: dhcpcd-base: fails to write multiple search domains to /etc/resolv.conf

[Martin-Éric Racine]

On Thu, 23 Nov 2023 09:01:34 +0100 "Francesco Poli (wintermute)"
 wrote:
> Package: dhcpcd-base
> Version: 1:10.0.5-2
> Severity: normal
>
> It seems to work pretty well, just like isc-dhcp-client, but
> I noticed an issue in a network where the DHCP server sends
> two domains as "search domains" (let's call them MYDOMAIN
> and OTHERDOMAIN).
>
> When I use dhcpcd-base as a DHCP client, I get the following
> resolv.conf file:
>
>   $ cat /etc/resolv.conf
>   # Generated by dhcpcd from enp0s3.dhcp
>   # /etc/resolv.conf.head can replace this line
>   domain MYDOMAIN
>   nameserver 192.168.0.1
>   # /etc/resolv.conf.tail can replace this line
>
> This lacks the two search domains I was expecting.
> To be honest, the isc-dhcp-client Debian package
> behaves similarly (somehow failing to write OTHERDOMAIN as
> second search domain).
>
> But Rocky Linux clients (on the same network, with the ISC
> DHCP client and ifup/ifdown mechanism) correctly set the
> resolv.conf with the two search domains:
>
>   $ cat /etc/resolv.conf
>   ; generated by /usr/sbin/dhclient-script
>   search MYDOMAIN. OTHERDOMAIN.
>   nameserver 192.168.0.1
>
> Even Windows clients (on the same network) correctly obtain
> the two search domains...

You might wanna check whether Rocky Linux has patched their DHCP
clients or altered their default dhcpcd.conf to make this succeed. If
that's the case, please point me to the relevant changes.

> Why cannot I have the two search domains on Debian?

The dhcpcd client shipped by Debian is, except for recent patches
towards fixing the build on Hurd (missing includes, etc.), whatever
upstream ships. If that fails to set more than one search domain, I
would suspect an upstream issue.

https://github.com/NetworkConfiguration/dhcpcd/issues

Martin-Éric

Bug#1006263: ifupdown: outdated DHCP client support

[Martin-Éric Racine]

Package: ifupdown
Version: 0.8.41
Followup-For: Bug #1006263

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

As discussed in bug #1038882, ifupdown needs to change its precedence order for 
DHCP clients. The new order of precedence should be: dhcpcd, dhclient, others 
(see above). This is necessary to ensure that dhcpcd-base will become the new 
default DHCP client after upgrades.

Martin-Éric

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEyJACx3qL7GpObXOQrh+Cd8S017YFAmVbnr4ACgkQrh+Cd8S0
17YtvxAAtY6xRzY+T628fW9mtCR3jcC01aPNhSJNNUDzwGyGvh6CWha3Tp4HJfPF
AQh/Hdc+4j+HPo+EKOvO5zm58DHsGTKSFrm72QTwLJmhmXHig1ZNjDcSY+TUno3Y
mPoEhWKDkPxqeO8tDOCV2m9ydRk9AEYNO2TgoGarIj+EeIOzKzNdWZCPDnb+HC4U
7MJJjjtAyBbt1OFFX1QhMcSJAiJU8uIEQyjhrztvAYHLnxMV/hov92sf82RsXR2G
QTjf0rNSdOtcYnyJW612HzDsWuHAIRbp9qBpSn6cwLvz1OP+ZwRVWKk7xcuN0xj2
/t5Gw2IOX6KZ4KFB1jPTjYItb4XBmtu4jV9/IBUCLMImFLN1lYShUZ1z5EJ6mWY/
eEn5mWqiibF2ttW6VbMoTCFTLew2ETY6RDTcKFvK7PbDmruUhU54h50Egpeo46yA
eQuVbH+Rvz29su8+NtXH2KzLnKcS+sAXSNYw+KkiHg+HfkebA7sLvNbnQIy18Mej
CnnEAV5JsU63EXbELAMDYtOuE1RDTdFvRBftJXjAWJPw3yOl1k9T2kSju0yBLuFd
bxxlciIlSM0Xx4WVFiA62hAuU4rukPp+f4nqQXfE+kPeMEfX0ma2wGAof36kjgLP
IXKkIRlj+386j02SXxrv5iojobm04Gj7UIokEsCEMQZMSb7fAhU=
=/jHu
-END PGP SIGNATURE-

Bug#1038882: proposal: dhcpcd-base as standard DHCP client starting with Trixie

[Martin-Éric Racine]

(non-subscriber - please keep me in CC)
On Sat, Nov 18, 2023 at 4:26 PM Martin-Éric Racine
 wrote:
>
> On Sat, Jul 22, 2023 at 2:55 PM Martin-Éric Racine
>  wrote:
> >
> > On Fri, Jul 7, 2023 at 12:55 PM Martin-Éric Racine
> >  wrote:
> > >
> > > On Thu, Jul 6, 2023 at 3:06 AM Santiago Ruano Rincón
> > >  wrote:
> > > >
> > > > El 22/06/23 a las 09:57, Santiago Ruano Rincón escribió:
> > > > > El 20/06/23 a las 08:29, Martin-Éric Racine escribió:
> > > > > > On Mon, Jun 19, 2023 at 9:11 PM Santiago Ruano Rincón
> > > > > >  wrote:
> > > > > > > El 19/06/23 a las 13:54, Martin-Éric Racine escribió:
> > > > > > > > Greetings,
> > > > > > > >
> > > > > > > > Seeing how the ISC DHCP suite has reached EOL upstream, now 
> > > > > > > > might be a
> > > > > > > > good time to re-visit Debian's choice of standard DHCP client 
> > > > > > > > shipping
> > > > > > > > with priority:important.
> > > > > > > >
> > > > > > > > I hereby propose bin:dhcpcd-base:
> > > > > > > >
> > > > > > > > 1) already supported by ifupdown.
> > > > > > > > 2) dual stack (DHCPv4, Bonjour, RA, DHCPv6 with PD) with 
> > > > > > > > privilege separation.
> > > > > > > > 3) writes both IPv4 and IPv6 name servers to /etc/resolv.conf
> > > > > > > > 4) supports /etc/resolv.conf.head and /etc/resolv.conf.tail
> > > > > > > > 5) a mere inet line in /etc/network/interfaces is sufficient to
> > > > > > > > configure both stacks.
> > > > > > > ...
> > > > > > >
> > > > > > > I agree that dhcpcd seems the best alternative to isc-dhcp-client 
> > > > > > > for
> > > > > > > the moment, and I'll make the relevant changes in ifupdown as 
> > > > > > > soon as I
> > > > > > > can. Josué, any thoughts?
> > > > > >
> > > > > > 1) As someone pointed out in the thread, the reason why
> > > > > > isc-dhcp-client had priority:important probably was to ensure that
> > > > > > debootstrap would pull it, since debootstrap ignores Recommends and
> > > > > > packages with a priority lower than standard.
> > > > > >
> > > > > > 2) However, as long as ifupdown explictly depends on a package, it 
> > > > > > can
> > > > > > also pull dependencies with a lower priority. Right now ifupdown
> > > > > > Recommends "isc-dhcp-client | dhcp-client" which debootstrap would
> > > > > > ignore. It would have to Depends "dhcpcd-base | dhcp-client" 
> > > > > > instead.
> > > > > >
> > > > > > 3) At that point, swapping the priority of isc-dhcp-client and
> > > > > > dhcpcd-base merely becomes "nice to have". Heck, the priority of 
> > > > > > both
> > > > > > could, in principle, be optional, just as long as ifupdown 
> > > > > > explicitly
> > > > > > Depends on a DHCP client, and the first alternative is a real 
> > > > > > package.
> > > > >
> > > > > I was about to bump dhcpcd-base as ifupdown dependency, but... if
> > > > > isc-client-dhcp is a Recommends, is because not all users want a dhcp
> > > > > client installed, where all the ipv4 is handled statically, and ipv6 
> > > > > is
> > > > > done via SLAAC. As a user, I don't want/need to pull in dhcpcd-base 
> > > > > the
> > > > > next upgrade.
> > > > >
> > > > > So I'd prefer to go forward with the steps proposed by Simon, and
> > > > > s/isc-dhcp-client/dhcpcd-base in ifupdown's Recommends:
> > > > > Unless there is a strong objection, I'll file the override bug report.
> > > >
> > > > (sorry for taking so long to come back to this)
> > > >
> > > > For the moment, ifupdown is still installed by the debian-installer as
> > > > default network interfaces manager. And after sleeping over it, and
> > > > discussing with debian fellows, I would like to call for consensus to
> > > > r

Bug#1056318: bookworm-pu: package dhcpcd5/9.4.1-24~deb12u3

[Martin-Éric Racine]

Package: release.debian.org
Severity: normal
Tags: bookworm
User: release.debian@packages.debian.org
Usertags: pu
X-Debbugs-Cc: dhcp...@packages.debian.org
Control: affects -1 + src:dhcpcd5

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

[ Reason ]
As per bug #1053657, files moved between binary targets and between /lib and 
/usr/lib may cause problems when upgrading from Bullseye due to the 
introduction of usrmerge.

[ Impact ]
As per bug report, the issue is not trivially reproducible and probably does 
not affect the majority of users. However, given how moving files between /lib 
and /usr/lib was considered an RC issue during the transition to usrmerge, 
mitigation is desirable just to be safe.

[ Tests ]
Manual upgrade tested in chroot and confirmed to work as expected.

[ Risks ]
None.

[ Checklist ]
  [x] *all* changes are documented in the d/changelog
  [x] I reviewed all changes and I approve them
  [x] attach debdiff against the package in (old)stable
  [x] the issue is verified as fixed in unstable

[ Changes ]
1) Migrate Breaks/Replaces dhcpcd5 (<< 9.4.1-2) to Conflicts (Closes: #1053657).
2) Update dhcpcd.preinst version check for previous bookworm-pu fix.

[ Other info ]

diff -Nru dhcpcd5-9.4.1/debian/changelog dhcpcd5-9.4.1/debian/changelog
- --- dhcpcd5-9.4.1/debian/changelog2023-07-22 17:56:49.0 +0300
+++ dhcpcd5-9.4.1/debian/changelog  2023-10-20 11:12:13.0 +0300
@@ -1,3 +1,10 @@
+dhcpcd5 (9.4.1-24~deb12u3) bookworm; urgency=medium
+
+  * Move Breaks/Replaces dhcpcd5 (<< 9.4.1-2) to Conflicts (Closes: #1053657).
+  * Update dhcpcd.preinst version check.
+
+ -- Martin-Éric Racine   Fri, 20 Oct 2023 11:12:13 
+0300
+
 dhcpcd5 (9.4.1-24~deb12u2) bookworm; urgency=medium
 
   * Fixed dhcpcd.preinst with the tilde version.
diff -Nru dhcpcd5-9.4.1/debian/control dhcpcd5-9.4.1/debian/control
- --- dhcpcd5-9.4.1/debian/control  2023-05-28 05:57:38.0 +0300
+++ dhcpcd5-9.4.1/debian/control2023-10-20 11:11:34.0 +0300
@@ -14,8 +14,7 @@
 Package: dhcpcd-base
 Architecture: any
 Provides: dhcp-client
- -Replaces: dhcpcd5 (<< 9.4.1-2)
- -Breaks: dhcpcd5 (<< 9.4.1-2)
+Conflicts: dhcpcd5 (<< 9.4.1-2)
 Depends: adduser,
  ${misc:Depends},
  ${shlibs:Depends}
diff -Nru dhcpcd5-9.4.1/debian/dhcpcd.preinst 
dhcpcd5-9.4.1/debian/dhcpcd.preinst
- --- dhcpcd5-9.4.1/debian/dhcpcd.preinst   2023-07-22 17:56:40.0 
+0300
+++ dhcpcd5-9.4.1/debian/dhcpcd.preinst 2023-10-20 11:12:08.0 +0300
@@ -2,7 +2,7 @@
 # As per Debian bug #1037190.
 # Copyright 2023 Andreas Beckmann 
 set -e
- -if dpkg --compare-versions "$2" lt-nl "1:9.4.1-24~deb12u2~" ; then
+if dpkg --compare-versions "$2" lt-nl "1:9.4.1-24~deb12u3~" ; then
   # Cleanup leftovers from dhcpcd 1:3.* in Wheezy.
   # Can be removed after Trixie is released.
   update-alternatives --remove dhcpcd /sbin/dhcpcd3

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEyJACx3qL7GpObXOQrh+Cd8S017YFAmVbgpUACgkQrh+Cd8S0
17bfkw/+NBPz3yOtdFHOzIDzD7DGvAQOFgtxJ2FDSu6nEvwTqc1Mlfv35x2Dqu/T
6Q9m9z2d655vuDkmVQIEbSFh5weATtCbpqLM29cZZFho5SUO7yHqB5vTqA4kQMJk
FD1FlkTjA0qFn/f8nkzCnljG2Vt3BQhLnoz70dzGV044ohKowm9q1sVXIgHADhxr
wL7mRCS3zTQe6SVvkLK9nUvmItCnn03/C3jadzZOVepowu6im5SnVULO/YFEelmA
JYsG9Oa9v0eeTv68BR0ybGG5kpVhGIF71BvELVJaZWu9VLfivXJwFug/mecq9nGO
AWqDL8bVyRfIPs8xpLXH7T5dWBVaMAA2UaYHPy4yZcFB1xwY+E01AGDTf8vFIOVP
mos75buvypjESkPetNeam1AleH2f2RM1t/mtusdJ3y3oFId5mg1S6tyEANws7VZM
TJwY7UFFA48z1Ua1/6AoFEjm0qu1eeKWEPc0hrL3L9MFZrmXTIp/mDTbjfN9vBG1
RvkxaWsBQQCoT/mLOKm68MWy7nCM9OXPJhZwBVceAQudtbIsNDcPmZM2OrmytKUw
n2Uuy+KS/Grb3seXkXjy0DWKheSaaFMrVlM3/rigWzSHxrhWfFuZ2sphiOybZbKW
zxNlwCG1fl3mWMspY8W4WTtVcSXIOaGmFT//3H2ZOg6KL31qJ/o=
=HavW
-END PGP SIGNATURE-

Bug#1038882: proposal: dhcpcd-base as standard DHCP client starting with Trixie

[Martin-Éric Racine]

On Sat, Jul 22, 2023 at 2:55 PM Martin-Éric Racine
 wrote:
>
> On Fri, Jul 7, 2023 at 12:55 PM Martin-Éric Racine
>  wrote:
> >
> > On Thu, Jul 6, 2023 at 3:06 AM Santiago Ruano Rincón
> >  wrote:
> > >
> > > El 22/06/23 a las 09:57, Santiago Ruano Rincón escribió:
> > > > El 20/06/23 a las 08:29, Martin-Éric Racine escribió:
> > > > > On Mon, Jun 19, 2023 at 9:11 PM Santiago Ruano Rincón
> > > > >  wrote:
> > > > > > El 19/06/23 a las 13:54, Martin-Éric Racine escribió:
> > > > > > > Greetings,
> > > > > > >
> > > > > > > Seeing how the ISC DHCP suite has reached EOL upstream, now might 
> > > > > > > be a
> > > > > > > good time to re-visit Debian's choice of standard DHCP client 
> > > > > > > shipping
> > > > > > > with priority:important.
> > > > > > >
> > > > > > > I hereby propose bin:dhcpcd-base:
> > > > > > >
> > > > > > > 1) already supported by ifupdown.
> > > > > > > 2) dual stack (DHCPv4, Bonjour, RA, DHCPv6 with PD) with 
> > > > > > > privilege separation.
> > > > > > > 3) writes both IPv4 and IPv6 name servers to /etc/resolv.conf
> > > > > > > 4) supports /etc/resolv.conf.head and /etc/resolv.conf.tail
> > > > > > > 5) a mere inet line in /etc/network/interfaces is sufficient to
> > > > > > > configure both stacks.
> > > > > > ...
> > > > > >
> > > > > > I agree that dhcpcd seems the best alternative to isc-dhcp-client 
> > > > > > for
> > > > > > the moment, and I'll make the relevant changes in ifupdown as soon 
> > > > > > as I
> > > > > > can. Josué, any thoughts?
> > > > >
> > > > > 1) As someone pointed out in the thread, the reason why
> > > > > isc-dhcp-client had priority:important probably was to ensure that
> > > > > debootstrap would pull it, since debootstrap ignores Recommends and
> > > > > packages with a priority lower than standard.
> > > > >
> > > > > 2) However, as long as ifupdown explictly depends on a package, it can
> > > > > also pull dependencies with a lower priority. Right now ifupdown
> > > > > Recommends "isc-dhcp-client | dhcp-client" which debootstrap would
> > > > > ignore. It would have to Depends "dhcpcd-base | dhcp-client" instead.
> > > > >
> > > > > 3) At that point, swapping the priority of isc-dhcp-client and
> > > > > dhcpcd-base merely becomes "nice to have". Heck, the priority of both
> > > > > could, in principle, be optional, just as long as ifupdown explicitly
> > > > > Depends on a DHCP client, and the first alternative is a real package.
> > > >
> > > > I was about to bump dhcpcd-base as ifupdown dependency, but... if
> > > > isc-client-dhcp is a Recommends, is because not all users want a dhcp
> > > > client installed, where all the ipv4 is handled statically, and ipv6 is
> > > > done via SLAAC. As a user, I don't want/need to pull in dhcpcd-base the
> > > > next upgrade.
> > > >
> > > > So I'd prefer to go forward with the steps proposed by Simon, and
> > > > s/isc-dhcp-client/dhcpcd-base in ifupdown's Recommends:
> > > > Unless there is a strong objection, I'll file the override bug report.
> > >
> > > (sorry for taking so long to come back to this)
> > >
> > > For the moment, ifupdown is still installed by the debian-installer as
> > > default network interfaces manager. And after sleeping over it, and
> > > discussing with debian fellows, I would like to call for consensus to
> > > rise Priority: Important to dhcpcd-base (as initially requested in
> > > #1038882), and switch to Recommends: dhcpcd-base | dhcp-client.
> > >
> > > This addresses two scenarios: keep some systems as small as possible
> > > (ifupdown users can remove dhcpcd if they want) and having a useful dhcp
> > > client available after installing/bootstrapping.
> > >
> > > So I would like to retitle #1038882 back as originally reported. (Sorry
> > > for going back and forth) Objections?
> > >
> > > The situation regarding the default network interfaces manager could
> > > change, even in the short term. But that could be discussed in another
> > > thread.
> >
> > No objection. Raising the priority of dhcpcd-base to important works for me.
>
> Have we reached a conclusion? Are we moving ahead with this or not?

What is the current situation?

Martin-Éric

Bug#1053436: dhcpcd-base: dhcpcd stops listening on port 68 after several days

[Martin-Éric Racine]

On Wed, Oct 25, 2023 at 3:35 AM Ron Murray  wrote:
> OK. Now running version 10.0.3-1. I'll let you know how it goes.

Testing now has 10.0.4-1, while unstable has 10.0.5-2. Does either one
fix the issue for you?

Martin-Éric

Bug#1053436: dhcpcd-base: dhcpcd stops listening on port 68 after several days

[Martin-Éric Racine]

Any progress on this?

On Thu, Oct 26, 2023 at 7:16 PM Ron Murray  wrote:
>
> I went to do that, but the "debug" line is already there. I didn't see 
> anything in the logs, but perhaps I missed it. I will check if it fails again.
>
> --
> Ron Murray 
> PGP Fingerprint: 4D99 70E3 2317 334B 141E  7B63 12F7 E865 B5E2 E761
>
> Martin-Éric Racine wrote:
>
>
> It might also help to add a line with the "debug" statement in
> /etc/dhcpcd.conf and check whether the log files tell anything useful
> when it stops listening.
>
> On Wed, Oct 25, 2023 at 3:35 AM Ron Murray  wrote:
>
>>
>> OK. Now running version 10.0.3-1. I'll let you know how it goes.
>>
>> --
>> Ron Murray 
>> PGP Fingerprint: 4D99 70E3 2317 334B 141E  7B63 12F7 E865 B5E2 E761
>>
>> Ron Murray wrote:
>>
>>
>> I’ll try that later tonight.
>> --
>> Ron Murray 
>> PGP Fingerprint: 4D99 70E3 2317 334B 141E  7B63 12F7 E865 B5E2 E761
>>
>> On 24 Oct 2023, at 15:28, Martin-Éric Racine  
>> wrote:
>>
>> Next, try what's in Testing.
>>
>> On Tue, Oct 24, 2023 at 10:15 PM Ron Murray  wrote:
>>
>>
>> It’s still happening. Currently running version 1:9.4.1-24~deb12u2.
>>
>>
>> …..Ron
>>
>>
>> --
>>
>> Ron Murray 
>>
>> PGP Fingerprint: 4D99 70E3 2317 334B 141E  7B63 12F7 E865 B5E2 E761
>>
>>
>> On 9 Oct 2023, at 10:02, Martin-Éric Racine  
>> wrote:
>>
>>
>> 
>>
>> Noted. If that still doesn't fix it, the next step is to try what's in 
>> Testing.
>>
>>
>> Martin-Éric
>>
>>
>> su 8. lokak. 2023 klo 20.57 Ron Murray  kirjoitti:
>>
>>
>> I've only just updated to that version. I'll let you know how it goes in a 
>> few days.
>>
>>
>> --
>>
>> Ron Murray 
>>
>> PGP Fingerprint: 4D99 70E3 2317 334B 141E  7B63 12F7 E865 B5E2 E761
>>
>>
>> Martin-Éric Racine wrote:
>>
>>
>>
>> On Tue, 03 Oct 2023 20:28:25 -0400 Ron Murray  wrote:
>>
>>
>> Package: dhcpcd-base
>>
>> Version: 9.4.1-22
>>
>> Severity: normal
>>
>>
>> Dear Maintainer,
>>
>>
>> dhcpcd stops listening on udp port 68 after several days. Still
>>
>> listening on raw port 17. I've tried re-installing the package and I
>>
>>
>> still get the same result.
>>
>>
>> Does this still apply to the package that just entered Stable via updates?
>>
>>
>>
>>
> Martin-Éric

Bug#1055275: dhcpcd: Version 10.0.4 fails to fork in the background

[Martin-Éric Racine]

On Fri, 03 Nov 2023 12:46:21 +0100 Skibbi  wrote:
> Package: dhcpcd
> Version: 1:10.0.4-1
> Severity: critical
> Justification: breaks the whole system
>
> Dear Maintainer,
> I'm using dhcpcd on my raspbian os and it was updated on 31 October to
> latest version 10.0.4. Since then, my raspberrypi started loosing network
> every 24h. After some investigation I found out that my dhcpcd daemon is
> not working in the background.

It would be a good idea to familiarize yourself with Debian's bug
severity levels. One particular feature (daemon mode) no longer
working as expected does not qualify as a critical bug.

Meanwhile, using dhcpcd as a DHCP backend via /etc/network/interfaces
still works as expected. I suggest using that until upstream has
figured out what causes daemon mode to no longer fork since the 10.0.4
release.

Martin-Éric

Bug#1053657: dhcpcd-base has ineffective Replaces due to /usr-merge and looses files in upgrade

[Martin-Éric Racine]

On Mon, Oct 9, 2023 at 10:00 AM Emilio Pozuelo Monfort  wrote:
>
> On 08/10/2023 08:15, Helmut Grohne wrote:
> > I'm sorry for not having spotted this before the point release and will
> > now monitor stable p-u suites for similar problems to raise this
> > earlier.
>
> Great, thanks.

I highly doubt that this was intoduced by the point release.

> > Can I assume that a package sits in p-u for at least three days
> > before migrating to a stable release?
>
> Yes, p-u is frozen about 5 or 6 days before the release. Exceptions can 
> happen,
> but excluding those you can assume that.

debdiff attached via previous message. If this looks good, I'll upload
and file the unblock request.

Martin-Éric

Bug#1053436: dhcpcd-base: dhcpcd stops listening on port 68 after several days

[Martin-Éric Racine]

It might also help to add a line with the "debug" statement in
/etc/dhcpcd.conf and check whether the log files tell anything useful
when it stops listening.

On Wed, Oct 25, 2023 at 3:35 AM Ron Murray  wrote:
>
> OK. Now running version 10.0.3-1. I'll let you know how it goes.
>
> --
> Ron Murray 
> PGP Fingerprint: 4D99 70E3 2317 334B 141E  7B63 12F7 E865 B5E2 E761
>
> Ron Murray wrote:
>
>
> I’ll try that later tonight.
> --
> Ron Murray 
> PGP Fingerprint: 4D99 70E3 2317 334B 141E  7B63 12F7 E865 B5E2 E761
>
> On 24 Oct 2023, at 15:28, Martin-Éric Racine  
> wrote:
>
> Next, try what's in Testing.
>
> On Tue, Oct 24, 2023 at 10:15 PM Ron Murray  wrote:
>
>
> It’s still happening. Currently running version 1:9.4.1-24~deb12u2.
>
>
> …..Ron
>
>
> --
>
> Ron Murray 
>
> PGP Fingerprint: 4D99 70E3 2317 334B 141E  7B63 12F7 E865 B5E2 E761
>
>
> On 9 Oct 2023, at 10:02, Martin-Éric Racine  wrote:
>
>
> 
>
> Noted. If that still doesn't fix it, the next step is to try what's in 
> Testing.
>
>
> Martin-Éric
>
>
> su 8. lokak. 2023 klo 20.57 Ron Murray  kirjoitti:
>
>
> I've only just updated to that version. I'll let you know how it goes in a 
> few days.
>
>
> --
>
> Ron Murray 
>
> PGP Fingerprint: 4D99 70E3 2317 334B 141E  7B63 12F7 E865 B5E2 E761
>
>
> Martin-Éric Racine wrote:
>
>
>
> On Tue, 03 Oct 2023 20:28:25 -0400 Ron Murray  wrote:
>
>
> Package: dhcpcd-base
>
> Version: 9.4.1-22
>
> Severity: normal
>
>
> Dear Maintainer,
>
>
>  dhcpcd stops listening on udp port 68 after several days. Still
>
> listening on raw port 17. I've tried re-installing the package and I
>
>
> still get the same result.
>
>
> Does this still apply to the package that just entered Stable via updates?
>
>
>
> Martin-Éric

Bug#1053436: dhcpcd-base: dhcpcd stops listening on port 68 after several days

[Martin-Éric Racine]

Next, try what's in Testing.

On Tue, Oct 24, 2023 at 10:15 PM Ron Murray  wrote:
>
> It’s still happening. Currently running version 1:9.4.1-24~deb12u2.
>
>  …..Ron
>
> --
> Ron Murray 
> PGP Fingerprint: 4D99 70E3 2317 334B 141E  7B63 12F7 E865 B5E2 E761
>
> On 9 Oct 2023, at 10:02, Martin-Éric Racine  wrote:
>
> 
> Noted. If that still doesn't fix it, the next step is to try what's in 
> Testing.
>
> Martin-Éric
>
> su 8. lokak. 2023 klo 20.57 Ron Murray  kirjoitti:
>>
>> I've only just updated to that version. I'll let you know how it goes in a 
>> few days.
>>
>> --
>> Ron Murray 
>> PGP Fingerprint: 4D99 70E3 2317 334B 141E  7B63 12F7 E865 B5E2 E761
>>
>> Martin-Éric Racine wrote:
>>
>>
>> On Tue, 03 Oct 2023 20:28:25 -0400 Ron Murray  wrote:
>>
>>> Package: dhcpcd-base
>>> Version: 9.4.1-22
>>> Severity: normal
>>>
>>> Dear Maintainer,
>>>
>>>   dhcpcd stops listening on udp port 68 after several days. Still
>>> listening on raw port 17. I've tried re-installing the package and I
>>>
>> still get the same result.
>>
>> Does this still apply to the package that just entered Stable via updates?
>>
>>
>> Martin-Éric

Bug#1053657: dhcpcd-base has ineffective Replaces due to /usr-merge and looses files in upgrade

[Martin-Éric Racine]

On Fri, 20 Oct 2023 09:12:47 +0300
=?UTF-8?Q?Martin=2D=C3=89ric_Racine?= 
wrote:
> On Sun, 8 Oct 2023 14:13:46 +0200 Helmut Grohne  wrote:
> > On Sun, Oct 08, 2023 at 01:42:05PM +0300, Martin-Éric Racine wrote:
> > > Thus changing fields from what to what?
> >
> > -Replaces: dhcpcd5 (<< 9.4.1-2)
> > -Breaks: dhcpcd5 (<< 9.4.1-2)
> > +Conflicts: dhcpcd5 (<< 9.4.1-2)
> >
> > The conflict implies a break and since it also prevents concurrent
> > unpack, no replacement can ever happen.
>
> Done for Sid (pending upload).
>
> For bookworm-pu, I'll have to check if there's any other fix I can
> cherry-pick from upstream, before I perform the upload and file the
> unblock request.

debdiff for bookworm-pu attached.

Martin-Éric
diff -Nru dhcpcd5-9.4.1/debian/changelog dhcpcd5-9.4.1/debian/changelog
--- dhcpcd5-9.4.1/debian/changelog  2023-07-22 17:56:49.0 +0300
+++ dhcpcd5-9.4.1/debian/changelog  2023-10-20 11:12:13.0 +0300
@@ -1,3 +1,10 @@
+dhcpcd5 (9.4.1-24~deb12u3) bookworm; urgency=medium
+
+  * Move Breaks/Replaces dhcpcd5 (<< 9.4.1-2) to Conflicts (Closes: #1053657).
+  * Update dhcpcd.preinst version check.
+
+ -- Martin-Éric Racine   Fri, 20 Oct 2023 11:12:13 
+0300
+
 dhcpcd5 (9.4.1-24~deb12u2) bookworm; urgency=medium
 
   * Fixed dhcpcd.preinst with the tilde version.
diff -Nru dhcpcd5-9.4.1/debian/control dhcpcd5-9.4.1/debian/control
--- dhcpcd5-9.4.1/debian/control2023-05-28 05:57:38.0 +0300
+++ dhcpcd5-9.4.1/debian/control2023-10-20 11:11:34.0 +0300
@@ -14,8 +14,7 @@
 Package: dhcpcd-base
 Architecture: any
 Provides: dhcp-client
-Replaces: dhcpcd5 (<< 9.4.1-2)
-Breaks: dhcpcd5 (<< 9.4.1-2)
+Conflicts: dhcpcd5 (<< 9.4.1-2)
 Depends: adduser,
  ${misc:Depends},
  ${shlibs:Depends}
diff -Nru dhcpcd5-9.4.1/debian/dhcpcd.preinst 
dhcpcd5-9.4.1/debian/dhcpcd.preinst
--- dhcpcd5-9.4.1/debian/dhcpcd.preinst 2023-07-22 17:56:40.0 +0300
+++ dhcpcd5-9.4.1/debian/dhcpcd.preinst 2023-10-20 11:12:08.0 +0300
@@ -2,7 +2,7 @@
 # As per Debian bug #1037190.
 # Copyright 2023 Andreas Beckmann 
 set -e
-if dpkg --compare-versions "$2" lt-nl "1:9.4.1-24~deb12u2~" ; then
+if dpkg --compare-versions "$2" lt-nl "1:9.4.1-24~deb12u3~" ; then
   # Cleanup leftovers from dhcpcd 1:3.* in Wheezy.
   # Can be removed after Trixie is released.
   update-alternatives --remove dhcpcd /sbin/dhcpcd3

Bug#1053657: dhcpcd-base has ineffective Replaces due to /usr-merge and looses files in upgrade

[Martin-Éric Racine]

On Sun, 8 Oct 2023 14:13:46 +0200 Helmut Grohne  wrote:
> On Sun, Oct 08, 2023 at 01:42:05PM +0300, Martin-Éric Racine wrote:
> > Thus changing fields from what to what?
>
> -Replaces: dhcpcd5 (<< 9.4.1-2)
> -Breaks: dhcpcd5 (<< 9.4.1-2)
> +Conflicts: dhcpcd5 (<< 9.4.1-2)
>
> The conflict implies a break and since it also prevents concurrent
> unpack, no replacement can ever happen.

Done for Sid (pending upload).

For bookworm-pu, I'll have to check if there's any other fix I can
cherry-pick from upstream, before I perform the upload and file the
unblock request.

Martin-Éric

Bug#1053436: dhcpcd-base: dhcpcd stops listening on port 68 after several days

[Martin-Éric Racine]

Noted. If that still doesn't fix it, the next step is to try what's in
Testing.

Martin-Éric

su 8. lokak. 2023 klo 20.57 Ron Murray  kirjoitti:

> I've only just updated to that version. I'll let you know how it goes in a
> few days.
>
> --
> Ron Murray 
> PGP Fingerprint: 4D99 70E3 2317 334B 141E  7B63 12F7 E865 B5E2 E761
>
> Martin-Éric Racine wrote:
>
>
> On Tue, 03 Oct 2023 20:28:25 -0400 Ron Murray  wrote:
>
> Package: dhcpcd-base
>> Version: 9.4.1-22
>> Severity: normal
>>
>> Dear Maintainer,
>>
>>   dhcpcd stops listening on udp port 68 after several days. Still
>> listening on raw port 17. I've tried re-installing the package and I
>>
>> still get the same result.
>
> Does this still apply to the package that just entered Stable via updates?
>
>
> Martin-Éric
>
>

Bug#1053436: dhcpcd-base: dhcpcd stops listening on port 68 after several days

[Martin-Éric Racine]

On Tue, 03 Oct 2023 20:28:25 -0400 Ron Murray  wrote:
> Package: dhcpcd-base
> Version: 9.4.1-22
> Severity: normal
>
> Dear Maintainer,
>
>dhcpcd stops listening on udp port 68 after several days. Still
> listening on raw port 17. I've tried re-installing the package and I
> still get the same result.

Does this still apply to the package that just entered Stable via updates?

Martin-Éric

Bug#1053657: dhcpcd-base has ineffective Replaces due to /usr-merge and looses files in upgrade

[Martin-Éric Racine]

On Sun, 8 Oct 2023 08:15:40 +0200 Helmut Grohne  wrote:
> Package: dhcpcd-base
> Version: 9.4.1-24~deb12u2
> Severity: serious
> Justification: file loss during upgrade
> X-Debbugs-Cc: debian-rele...@lists.debian.org
> User: helm...@debian.org
> Usertags: dep17p1
>
> Unfortunately, the stable update of dhcpcd5 introduced a regression
> relevant to upgrades from bullseye. The bullseye dhcpcd5 package
> contained the files
>  - /lib/dhcpcd/dhcpcd-hooks/01-test
>  - /lib/dhcpcd/dhcpcd-hooks/20-resolv.conf
>  - /lib/dhcpcd/dhcpcd-hooks/30-hostname
>  - /lib/dhcpcd/dhcpcd-hooks/60-ntp-common.conf
>  - /lib/dhcpcd/dhcpcd-hooks/62-chrony.conf
>  - /lib/dhcpcd/dhcpcd-hooks/64-timesyncd.conf
>  - /lib/dhcpcd/dhcpcd-hooks/68-openntpd.conf
>  - /lib/dhcpcd/dhcpcd-run-hooks
> and these have been moved into dhcpcd-base in that particular stable
> update. The update correctly declares Replaces for this. Unfortunately,
> it also moves these files from /lib to /usr/lib. Therefore, the declared
> Replaces have no effect (regarding these files) and as a consequence, an
> upgrade may delete the affected files.

That doesn't hold water. Moving files to the base package doesn't delete them.

> mmdebstrap bullseye /dev/null --variant=apt --include dhcpcd5 
> --chrooted-customize-hook='sed -i -e s/bullseye/bookworm/ 
> /etc/apt/sources.list && apt update && apt-get install -y libc6 usrmerge && 
> apt-get download dhcpcd-base && dpkg --auto-deconfigure --unpack 
> ./dhcpcd-base_*.deb && dpkg -r dhcpcd5 && ls /usr/lib/dhcpcd/dhcpcd-hooks'
>
> If you run this, it ends with:
>
> | Selecting previously unselected package dhcpcd-base.
> | dpkg: considering deconfiguration of dhcpcd5, which would be broken by 
> installation of dhcpcd-base ...
> | dpkg: yes, will deconfigure dhcpcd5 (broken by dhcpcd-base)
> | (Reading database ... 6731 files and directories currently installed.)
> | Preparing to unpack .../dhcpcd-base_9.4.1-24~deb12u2_amd64.deb ...
> | De-configuring dhcpcd5 (7.1.0-2+b1) ...
> | Unpacking dhcpcd-base (9.4.1-24~deb12u2) ...
> | Replacing files in old package dhcpcd5 (7.1.0-2+b1) ...
> | (Reading database ... 6752 files and directories currently installed.)
> | Removing dhcpcd5 (7.1.0-2+b1) ...
> | ls: cannot access '/usr/lib/dhcpcd/dhcpcd-hooks': No such file or directory
>
> This kind of problem has been categorized in the
> https://subdivi.de/~helmut/dep17.html as P1 and the recommended
> mitigation M7 is changing Breaks+Replaces to Conflicts. I think this
> mitigation is fully applicable here, because apt will by default unpack
> the updated dhcpcd5 package first and then the conflict is resolved. The
> additional constraint is satisfied by the default solution of apt.

Thus changing fields from what to what?

Martin-Éric

Bug#1053585: lintian-brush: many scripts fail

[Martin-Éric Racine]

Package: lintian-brush
Version: 0.151
Severity: normal

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Some fixer scripts failed to run: ["debian-tests-control-autodep8-is-obsolete", 
"unused-override", "common-license", "vcs-field-mismatch", 
"invalid-standards-version", "upstream-metadata-invalid", "pkg-perl-vcs", 
"no-section-field", "initial-upload-closes-no-bugs", 
"debian-control-has-unusual-field-spacing", 
"debian-source-options-has-custom-compression-settings", 
"package-uses-deprecated-debhelper-compat-version", "unnecessary-team-upload", 
"wrong-section-according-to-package-name", "package-has-no-description", 
"public-upstream-key-binary", "no-maintainer-field", "upstream-metadata-file", 
"new-package-uses-date-based-version-number", "vcs-field-invalid-branch", 
"debian-rules-sets-dpkg-architecture-variable", 
"debian-rules-missing-recommended-target", 
"public-upstream-keys-in-multiple-locations", "pkg-perl-testsuite", 
"public-upstream-key-in-native-package", "no-copyright-file", 
"debian-watch-uses-insecure-uri", "built-using-for-golang", 
"binary-control-field-duplicates-source", "no-priority-field", "source-format", 
"rules-requires-root-missing", "uses-debhelper-compat-file", 
"dep5-file-paragraph-references-header-paragraph", 
"license-file-listed-in-debian-copyright", "no-homepage-field", 
"missing-prerequisite-for-pyproject-backend", "pubkey", 
"upstream-metadata-in-native-source", "debian-watch-file-is-missing", 
"vcs-field-bitrotted", "old-override-info-format", 
"package-needs-versioned-debhelper-build-depends", 
"debian-control-has-obsolete-dbg-package"]. Run with --verbose for details.

- -- System Information:
Debian Release: trixie/sid
  APT prefers unstable
  APT policy: (900, 'unstable')
Architecture: i386 (x86_64)

Kernel: Linux 6.1.0-12-amd64 (SMP w/4 CPU threads; PREEMPT)
Locale: LANG=fi_FI.UTF-8, LC_CTYPE=fi_FI.UTF-8 (charmap=UTF-8), LANGUAGE=fi:en
Shell: /bin/sh linked to /usr/bin/dash
Init: unable to detect

Versions of packages lintian-brush depends on:
ii  devscripts   2.23.6
ii  libc62.37-12
ii  libgcc-s113.2.0-4
ii  liblzma5 5.4.4-0.1
ii  libpython3.113.11.6-1
ii  libssl3  3.0.11-1
ii  python3  3.11.4-5+b1
ii  python3-breezy   3.3.4-1
ii  python3-debian   0.1.49
ii  python3-debmutate0.68
ii  python3-distro-info  1.5
ii  python3-dulwich  0.21.6-1
ii  python3-iniparse 0.5-1
ii  python3-iso8601  1.0.2-1
ii  python3-levenshtein  0.12.2-2+b4
ii  python3-psycopg2 2.9.6-3
ii  python3-pyinotify0.9.6-2
ii  python3-ruamel.yaml  0.17.21-1
ii  python3-semver   2.10.2-3
ii  python3-tomlkit  0.12.1-1
ii  python3-tqdm 4.64.1-1
ii  python3-upstream-ontologist  0.1.35-1

Versions of packages lintian-brush recommends:
ii  debhelper  13.11.6
pn  decopy 
pn  dos2unix   
ii  gpg2.2.40-1.1
ii  lintian2.116.3
pn  ognibuild  
ii  python3-bs44.12.2-2
ii  python3-debianbts  4.0.1
pn  python3-docutils   
ii  python3-lxml   4.9.3-1
pn  python3-markdown   

Versions of packages lintian-brush suggests:
pn  brz-debian 
ii  git-buildpackage   0.9.32
pn  gnome-pkg-tools
ii  po-debconf 1.0.21+nmu1
pn  postgresql-common  

- -- no debconf information

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEyJACx3qL7GpObXOQrh+Cd8S017YFAmUg7ZcACgkQrh+Cd8S0
17a/0BAAum+tydrJmkvY9g/iE6WbSVgRbps5RVpOQ2XbDGvajMlM3JuhcRXObhR4
aIaaDX6zmlp9fIlnpZWyhLo9W+8X61x6Jef+/Qa07mA58wWB0XJOdgAwFaXxmoQ2
T2JFb7zYCLZXU9rAFjiHTXsHAMkSiCHpfq+XgIfdQYkHrthb+FFYZ/VKOmym+CbX
zkOmxthi4jyOGpo7eAMBJQdwTMszHkzr93mcbVtLwdawF3S5NjPKLbsVf6l2cA3B
+1Ak8PnDsUvV6N2B6amSvuErPUIgRMCh7a8y9eCKPftqryAmX94fr08D9/cJ6ka3
IsfyDCOeER6x8iMTnR8Jhjya0/0xsEIaN3NBpjQwvr1aDvYTmsOno3Ik31vX2G8F
SICI/cwgboUMKxhiysB/tz9ybzEQU6oFIdPNcbG8Uu2XPHUW3Ni8lEyfN/V+aaKh
KLNBT6WjnAlngBa2gr19/RjSPb31BQJRoG8ni+zILHEunh9XQ3YXCCyJDfMbqBOr
tFWVDwxswaagTubVxrdzIokouo0MGBmb2kp8LNof+C+fmmR9ey+E8pTbTnz5UwNB
9b4xFcyZ7pIdaRbE5cwVTZmq2pPLEYN6KYLBZp3eH95+TXypKUrQq/nAz0CJaHsz
9zWn9uvrq7gBh9o9dMXAg7HMPhqdzqf2oNR5qi58pGzLyR4TaBg=
=hhiS
-END PGP SIGNATURE-