Bug#1072108: linux-image-amd64: Enable CONFIG_PINCTRL_METEORLAKE

[Mark Pearson]

On Tue, May 28, 2024, at 2:33 PM, Diederik de Haas wrote:
> Control: forcemerge -1 1071551
>
> On Tuesday, 28 May 2024 20:20:11 CEST Mark Pearson wrote:
>> Package: src:linux
>> Version: 6.8.11-1
>> Severity: important
>> X-Debbugs-Cc: mpearson-len...@squebb.ca
>> 
>> Dear Maintainer,
>> 
>> Please enable the CONFIG_PINCTRL_METEORLAKE kernel option. This is needed to
>> support Meteorlake based platforms.
>
> That was already requested in bug #1071551 with the following header:
>
> On Mon, 20 May 2024 22:19:16 -0300 Facundo Gaich  wrote:
>> Package: src:linux
>> Version: 6.8.9-1
>> Severity: important
>> X-Debbugs-Cc: mpearson-len...@squebb.ca
>
> ...
>
> The MR for it (1062) has just been merged into master.
> Attachments:
> * signature.asc

Awesome - thanks! I did scan the bugs before submitting but missed that one. 
Apologies.
Should I close this issue then as it's a duplicate?

Mark

Bug#1072108: linux-image-amd64: Enable CONFIG_PINCTRL_METEORLAKE

[Mark Pearson]

Package: src:linux
Version: 6.8.11-1
Severity: important
X-Debbugs-Cc: mpearson-len...@squebb.ca

Dear Maintainer,

Please enable the CONFIG_PINCTRL_METEORLAKE kernel option. This is needed to 
support Meteorlake based platforms.

-- Package-specific info:
** Version:
Linux version 6.8.11-amd64 (debian-ker...@lists.debian.org) 
(x86_64-linux-gnu-gcc-13 (Debian 13.2.0-25) 13.2.0, GNU ld (GNU Binutils for 
Debian) 2.42) #1 SMP PREEMPT_DYNAMIC Debian 6.8.11-1 (2024-05-26)

** Command line:
BOOT_IMAGE=/boot/vmlinuz-6.8.11-amd64 
root=UUID=53f1bc6e-77b2-4354-88ed-77234d21b754 ro quiet

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

** Kernel log:
[  123.271676] usb 1-1: Manufacturer: Generic
[  123.275591] hub 1-1:1.0: USB hub found
[  123.278788] hub 1-1:1.0: 4 ports detected
[  137.469932] usb 1-1: USB disconnect, device number 6
[  143.071167] usb 1-1: new high-speed USB device number 7 using xhci_hcd
[  143.236634] usb 1-1: New USB device found, idVendor=0bda, idProduct=5411, 
bcdDevice= 1.18
[  143.236646] usb 1-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[  143.236651] usb 1-1: Product: 4-Port USB 2.1 Hub
[  143.236654] usb 1-1: Manufacturer: Generic
[  143.238802] hub 1-1:1.0: USB hub found
[  143.240015] hub 1-1:1.0: 4 ports detected
[  529.376067] wlp0s20f3: deauthenticating from bc:df:58:fe:b8:be by local 
choice (Reason: 3=DEAUTH_LEAVING)
[  529.874359] PM: suspend entry (s2idle)
[  529.880533] Filesystems sync: 0.006 seconds
[  529.880730] (NULL device *): firmware: direct-loading firmware 
iwlwifi-ma-b0-gf-a0.pnvm
[  529.880847] (NULL device *): firmware: direct-loading firmware regulatory.db
[  529.880882] (NULL device *): firmware: direct-loading firmware 
regulatory.db.p7s
[  529.880926] (NULL device *): firmware: direct-loading firmware 
intel/ibt-0180-0041.ddc
[  529.880957] (NULL device *): firmware: direct-loading firmware 
intel/sof-ace-tplg/sof-hda-generic-2ch.tplg
[  529.881093] (NULL device *): firmware: direct-loading firmware 
iwlwifi-ma-b0-gf-a0-86.ucode
[  529.881127] (NULL device *): firmware: direct-loading firmware 
intel/ibt-0180-0041.sfi
[  529.881144] (NULL device *): firmware: direct-loading firmware 
i915/mtl_dmc.bin
[  529.883884] Freezing user space processes
[  529.914435] Freezing user space processes completed (elapsed 0.030 seconds)
[  529.914439] OOM killer disabled.
[  529.914440] Freezing remaining freezable tasks
[  529.915793] Freezing remaining freezable tasks completed (elapsed 0.001 
seconds)
[  529.915796] printk: Suspending console(s) (use no_console_suspend to debug)
[  530.095825] ACPI: EC: interrupt blocked
[  739.865047] ACPI: EC: interrupt unblocked
[  739.943016] pci :00:08.0: Setting to D3hot
[  739.955306] pci :00:0b.0: Setting to D3hot
[  739.999154] iwlwifi :00:14.3: WRT: Invalid buffer destination
[  740.041638] nvme nvme0: Shutdown timeout set to 10 seconds
[  740.048976] nvme nvme0: 22/0/0 default/read/poll queues
[  740.154423] iwlwifi :00:14.3: Not valid error log pointer 0x0027B0C0 for 
RT uCode
[  740.154578] iwlwifi :00:14.3: WFPM_UMAC_PD_NOTIFICATION: 0x1f
[  740.154597] iwlwifi :00:14.3: WFPM_LMAC2_PD_NOTIFICATION: 0x1f
[  740.154604] iwlwifi :00:14.3: WFPM_AUTH_KEY_0: 0x80
[  740.154611] iwlwifi :00:14.3: CNVI_SCU_SEQ_DATA_DW9: 0x0
[  740.155001] iwlwifi :00:14.3: RFIm is deactivated, reason = 4
[  740.262685] OOM killer enabled.
[  740.262687] Restarting tasks ... done.
[  740.264043] random: crng reseeded on system resumption
[  740.346752] PM: suspend exit
[  744.330519] wlp0s20f3: authenticate with bc:df:58:fe:b8:ba (local 
address=d4:e9:8a:28:29:5e)
[  744.331181] wlp0s20f3: send auth to bc:df:58:fe:b8:ba (try 1/3)
[  744.365025] wlp0s20f3: authenticated
[  744.367345] wlp0s20f3: associate with bc:df:58:fe:b8:ba (try 1/3)
[  744.379466] wlp0s20f3: RX AssocResp from bc:df:58:fe:b8:ba (capab=0x 
status=0 aid=2)
[  744.381167] wlp0s20f3: associated
[  744.400403] wlp0s20f3: Limiting TX power to 30 (30 - 0) dBm as advertised by 
bc:df:58:fe:b8:ba
[  749.728812] wlp0s20f3: disconnect from AP bc:df:58:fe:b8:ba for new auth to 
bc:df:58:fe:b8:be
[  749.772632] wlp0s20f3: authenticate with bc:df:58:fe:b8:be (local 
address=d4:e9:8a:28:29:5e)
[  749.773041] wlp0s20f3: send auth to bc:df:58:fe:b8:be (try 1/3)
[  749.827021] wlp0s20f3: authenticate with bc:df:58:fe:b8:be (local 
address=d4:e9:8a:28:29:5e)
[  749.827587] wlp0s20f3: send auth to bc:df:58:fe:b8:be (try 1/3)
[  749.843441] wlp0s20f3: authenticated
[  749.847478] wlp0s20f3: associate with bc:df:58:fe:b8:be (try 1/3)
[  749.854108] wlp0s20f3: RX ReassocResp from bc:df:58:fe:b8:be (capab=0x 
status=0 aid=2)
[  749.856761] wlp0s20f3: associated
[ 1055.998967] wlp0s20f3: disconnect from AP bc:df:58:fe:b8:be for new auth to 
bc:df:58:fe:b8:ba
[ 1056.130402] wlp0s20f3: authenticate with bc:df:58:fe:b8:ba (local 
address=d4:e9:8a:28:29:5e)
[ 1056.135259] wlp0s20f3: send auth to bc:df:58:fe:b8:ba (try 1/3)
[ 1056.173137] wlp0s20f3: 

Bug#1072011: bootlogd: typo in /etc/init.d/bootlogd on trixie/testing

[Mark Hindley]

Control: tags -1 pending

On Mon, May 27, 2024 at 03:57:46PM +0200, Jin-Woo wrote:
> Package: bootlogd
> Version: 3.09-1
> Severity: normal
> X-Debbugs-Cc: saesor...@420blaze.it
> 
> /etc/init.d/bootlogd contains a check for whether the system boots with 
> systemd:
> 
> if [ -d /run/system/system ]; then
> 
> this should probably spell:
> 
> if [ -d /run/systemd/system ]; then

Thanks -- well spotted!

I have queued this for the next upload.

Mark

Bug#1071964: Elogind defaults to s2idle

[Mark Hindley]

Control: forwarded -1 https://github.com/elogind/elogind/issues/285
Control: tags -1 upstream

On Sun, May 26, 2024 at 05:14:55PM +0200, Juliusz Chroboczek wrote:
> Filed upstream at https://github.com/elogind/elogind/issues/285.

Thanks. I think that is the right place to discuss this further. You would need
to present a persuasive argument for Debian to deviate from the upstream
default.

FTR, the change in behaviour is documented with a workaround in debian/NEWS[1]

Mark

[1]  https://git.devuan.org/devuan/elogind/src/branch/debian/debian/NEWS

Bug#942314: RFP: gst-plugins-rs -- GStreamer plugins written in Rust

[Mark Van den Borre]

Hello Matthias, debconf-video@, FOSDEM video,

Fyi, at https://fosdem.org , we are very interested in getting the
gstreamer rust plugins or at least the fallbackswitch/fallbacksrc
plugin packaged inside Debian.

Our use case is simple: make voctomix 2.0 more resilient on
disconnected sources, like voctomix 1.x.

See also https://github.com/FOSDEM/video/issues/247 .

Cc-ing debconf-video@ since this might also be of interest to the
debconf video team...

Kind regards,

Mark
FOSDEM vzw

Bug#1071596: apache2: envvars evaluates string in conditional instead of testing for empty string

[Mark Hedges]

Weird.  I'll have to reinstall apache2.  Maybe I edited it long ago to
debug it, forgot a space, and it got stuck by debconf picking my
version on upgrades instead of the package maintainer's.  Thanks.


On Wed, May 22, 2024 at 12:38 PM Stefan Fritsch  wrote:
>
> Hi Mark,
>
> Am 21.05.24 um 22:30 schrieb Mark Hedges:
> > Package: apache2
> > Version: 2.4.59-1~deb12u1
> > Severity: normal
> >
> > Dear Maintainer,
> >
> > `envvars` evaluates string in conditional instead of testing for empty 
> > string.
> >
> > `apachectl` calls `envvars` which shows a syntax error despite working:
> >
> >   root@nodeo:/etc/letsencrypt# apachectl configtest
> >   /usr/sbin/apachectl: 6: [: /etc/apache2: unexpected operator
> >   Syntax OK
> >
> > If I change this line in `envvars`:
> >
> >   if [ "${APACHE_CONFDIR}" == "" ]; then
> >export APACHE_CONFDIR=/etc/apache2
> >   fi
>
> This snippet is not in the original file from the apache2 package.
> Compare to
> https://salsa.debian.org/apache-team/apache2/-/blob/master/debian/config-dir/envvars?ref_type=heads
>
> Either you or some package or script has changed the file. If you have
> etckeeper you could dig in the logs.
>
> Cheers,
> Stefan
>
> >
> > to this:
> >
> >   if [ -z ${APACHE_CONFDIR} ]; then
> >export APACHE_CONFDIR=/etc/apache2
> >   fi
> >
> > ... then it works.
> >
> > It's trying to evaluate `/etc/apache2` as a command?  Weird.
> >
> > PATH seems totally normal.
> >
> > Mark
> >
> > -- Package-specific info:
> >
> > -- System Information:
> > Debian Release: 12.5
> >APT prefers stable-updates
> >APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 
> > 'stable')
> > Architecture: amd64 (x86_64)
> >
> > Kernel: Linux 6.1.0-21-amd64 (SMP w/1 CPU thread; PREEMPT)
> > Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE 
> > not set
> > Shell: /bin/sh linked to /usr/bin/dash
> > Init: systemd (via /run/systemd/system)
> > LSM: AppArmor: enabled
> >
> > Versions of packages apache2 depends on:
> > ii  apache2-bin2.4.59-1~deb12u1
> > ii  apache2-data   2.4.59-1~deb12u1
> > ii  apache2-utils  2.4.59-1~deb12u1
> > ii  init-system-helpers1.65.2
> > ii  lsb-base   11.6
> > ii  media-types10.0.0
> > ii  perl   5.36.0-7+deb12u1
> > ii  procps 2:4.0.2-3
> > ii  sysvinit-utils [lsb-base]  3.06-4
> >
> > Versions of packages apache2 recommends:
> > ii  ssl-cert  1.1.2
> >
> > Versions of packages apache2 suggests:
> > pn  apache2-doc  
> > pn  apache2-suexec-pristine | apache2-suexec-custom  
> > ii  chromium [www-browser]   125.0.6422.60-1~deb12u1
> >
> > Versions of packages apache2-bin depends on:
> > ii  libapr1  1.7.2-3
> > ii  libaprutil1  1.6.3-1
> > ii  libaprutil1-dbd-sqlite3  1.6.3-1
> > ii  libaprutil1-ldap 1.6.3-1
> > ii  libbrotli1   1.0.9-2+b6
> > ii  libc62.36-9+deb12u7
> > ii  libcrypt11:4.4.33-2
> > ii  libcurl4 7.88.1-10+deb12u5
> > ii  libjansson4  2.14-2
> > ii  libldap-2.5-02.5.13+dfsg-5
> > ii  liblua5.3-0  5.3.6-2
> > ii  libnghttp2-141.52.0-1+deb12u1
> > ii  libpcre2-8-0 10.42-1
> > ii  libssl3  3.0.11-1~deb12u2
> > ii  libxml2  2.9.14+dfsg-1.3~deb12u1
> > ii  perl 5.36.0-7+deb12u1
> > ii  zlib1g   1:1.2.13.dfsg-1
> >
> > Versions of packages apache2-bin suggests:
> > pn  apache2-doc  
> > pn  apache2-suexec-pristine | apache2-suexec-custom  
> > ii  chromium [www-browser]   125.0.6422.60-1~deb12u1
> >
> > Versions of packages apache2 is related to:
> > ii  apache2  2.4.59-1~deb12u1
> > ii  apache2-bin  2.4.59-1~deb12u1
> >
> > -- Configuration Files:
> > /etc/apache2/apache2.conf changed:
> > DefaultRuntimeDir ${APACHE_RUN_DIR}
> > PidFile ${APACHE_PID_FILE}
> > Timeout 300
> > KeepAlive On
> > MaxKeepAliveRequests 100
> > KeepAliveTimeout 5
> > User ${APACHE_RUN_USER}
> > Group ${APACHE_RUN_GROUP}
> > HostnameLookups Of

Bug#1071596: apache2: envvars evaluates string in conditional instead of testing for empty string

[Mark Hedges]

Package: apache2
Version: 2.4.59-1~deb12u1
Severity: normal

Dear Maintainer,

`envvars` evaluates string in conditional instead of testing for empty string.

`apachectl` calls `envvars` which shows a syntax error despite working:

 root@nodeo:/etc/letsencrypt# apachectl configtest
 /usr/sbin/apachectl: 6: [: /etc/apache2: unexpected operator
 Syntax OK

If I change this line in `envvars`:

 if [ "${APACHE_CONFDIR}" == "" ]; then
 export APACHE_CONFDIR=/etc/apache2
 fi

to this:

 if [ -z ${APACHE_CONFDIR} ]; then
 export APACHE_CONFDIR=/etc/apache2
 fi

... then it works.

It's trying to evaluate `/etc/apache2` as a command?  Weird.

PATH seems totally normal.

Mark

-- Package-specific info:

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

Kernel: Linux 6.1.0-21-amd64 (SMP w/1 CPU thread; PREEMPT)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages apache2 depends on:
ii  apache2-bin2.4.59-1~deb12u1
ii  apache2-data   2.4.59-1~deb12u1
ii  apache2-utils  2.4.59-1~deb12u1
ii  init-system-helpers1.65.2
ii  lsb-base   11.6
ii  media-types10.0.0
ii  perl   5.36.0-7+deb12u1
ii  procps 2:4.0.2-3
ii  sysvinit-utils [lsb-base]  3.06-4

Versions of packages apache2 recommends:
ii  ssl-cert  1.1.2

Versions of packages apache2 suggests:
pn  apache2-doc  
pn  apache2-suexec-pristine | apache2-suexec-custom  
ii  chromium [www-browser]   125.0.6422.60-1~deb12u1

Versions of packages apache2-bin depends on:
ii  libapr1  1.7.2-3
ii  libaprutil1  1.6.3-1
ii  libaprutil1-dbd-sqlite3  1.6.3-1
ii  libaprutil1-ldap 1.6.3-1
ii  libbrotli1   1.0.9-2+b6
ii  libc62.36-9+deb12u7
ii  libcrypt11:4.4.33-2
ii  libcurl4 7.88.1-10+deb12u5
ii  libjansson4  2.14-2
ii  libldap-2.5-02.5.13+dfsg-5
ii  liblua5.3-0  5.3.6-2
ii  libnghttp2-141.52.0-1+deb12u1
ii  libpcre2-8-0 10.42-1
ii  libssl3  3.0.11-1~deb12u2
ii  libxml2  2.9.14+dfsg-1.3~deb12u1
ii  perl 5.36.0-7+deb12u1
ii  zlib1g   1:1.2.13.dfsg-1

Versions of packages apache2-bin suggests:
pn  apache2-doc  
pn  apache2-suexec-pristine | apache2-suexec-custom  
ii  chromium [www-browser]   125.0.6422.60-1~deb12u1

Versions of packages apache2 is related to:
ii  apache2  2.4.59-1~deb12u1
ii  apache2-bin  2.4.59-1~deb12u1

-- Configuration Files:
/etc/apache2/apache2.conf changed:
DefaultRuntimeDir ${APACHE_RUN_DIR}
PidFile ${APACHE_PID_FILE}
Timeout 300
KeepAlive On
MaxKeepAliveRequests 100
KeepAliveTimeout 5
User ${APACHE_RUN_USER}
Group ${APACHE_RUN_GROUP}
HostnameLookups Off
ErrorLog ${APACHE_LOG_DIR}/error.log
LogLevel warn
IncludeOptional mods-enabled/*.load
IncludeOptional mods-enabled/*.conf
Include ports.conf

Options FollowSymLinks
AllowOverride None
Require all denied


AllowOverride None
Require all granted


Options Indexes FollowSymLinks
AllowOverride None
Require all granted

AccessFileName .htaccess

Require all denied

LogFormat "%v:%p %h %l %u %t \"%r\" %>s %O \"%{Referer}i\" \"%{User-Agent}i\"" 
vhost_combined
LogFormat "%h %l %u %t \"%r\" %>s %O \"%{Referer}i\" \"%{User-Agent}i\"" 
combined
LogFormat "%h %l %u %t \"%r\" %>s %O" common
LogFormat "%{Referer}i -> %U" referer
LogFormat "%{User-agent}i" agent
IncludeOptional conf-enabled/*.conf
IncludeOptional sites-enabled/*.conf

/etc/apache2/envvars changed:
unset HOME
if [ -z "${APACHE_CONFDIR}" ]; then
export APACHE_CONFDIR=/etc/apache2
fi
if [ "${APACHE_CONFDIR##/etc/apache2-}" != "${APACHE_CONFDIR}" ] ; then
SUFFIX="-${APACHE_CONFDIR##/etc/apache2-}"
else
SUFFIX=
fi
export APACHE_RUN_USER=www-data
export APACHE_RUN_GROUP=www-data
export APACHE_PID_FILE=/var/run/apache2$SUFFIX/apache2.pid
export APACHE_RUN_DIR=/var/run/apache2$SUFFIX
export APACHE_LOCK_DIR=/var/lock/apache2$SUFFIX
export APACHE_LOG_DIR=/var/log/apache2$SUFFIX
export LANG=C
export LANG


-- no debconf information

Bug#1071276: Is 1:1.2.13.dfsg-1 affected by CVE-2023-45853, and if it is, will 1:1.3.dfsg-3.1 be backported to bookworm?

[Mark Brown]

On Fri, May 17, 2024 at 10:56:53AM -0400, John Waffle wrote:
> Hi Mark,
> 
> How do I get in contact with them, should I just send a message to
> secur...@debian.org?

Yes.


signature.asc
Description: PGP signature

Bug#1071276: Is 1:1.2.13.dfsg-1 affected by CVE-2023-45853, and if it is, will 1:1.3.dfsg-3.1 be backported to bookworm?

[Mark Brown]

On Fri, May 17, 2024 at 10:43:26AM -0400, John Waffle wrote:

> - The zlib package page https://tracker.debian.org/pkg/zlib says that
> CVE-2023-45853 
> is ignored, what is the basis for ignoring this CVE?
> - Is there a plan to backport zlib 1:1.3.dfsg-3.1 to bookworm? It looks
> like it's currently in trixie

Please direct any questions about security updates to the security team.


signature.asc
Description: PGP signature

Bug#1061902: consolekit2: NMU diff for 64-bit time_t transition

[Mark Hindley]

On Wed, May 08, 2024 at 01:09:59PM +0100, Mark Hindley wrote:
> Michael and Steve,
> 
> I would appreciate some help here.

Bump to reset autoremove timer.

Mark

Bug#1035630: clc-intercal: Update packaging to dh and new upstream version (fixes reproducibility issues!)

[Mark Brown]

reopen 1035630
kthxbye

The BTS really is user hostile...

On Sat, May 06, 2023 at 02:24:24PM -0700, Vagrant Cascadian wrote:
> Package: clc-intercal
> Severity: wishlist
> Tags: patch
> User: reproducible-bui...@lists.alioth.debian.org
> Usertags: timestamps
> X-Debbugs-Cc: reproducible-b...@lists.alioth.debian.org
> 
> I baited myself into testing upstream claims that the new clc-intercal
> builds reproducibly... and it indeed fixes the timestamps issues!
> 
> In order to test it, this required making some changes to the debian
> packaging, and it seemed easier to just update to a more recent style...
> So, attached is a patch updating to the new upstream version, as well as
> updating to dh style debian/rules.
> 
> I have not tested that this actually works, only that it builds (there
> may be an unresolved test suite failure...) and any changes to the
> resulting .deb appear roughly reasonable, addressed a few lintian
> issues, and that it builds reproducibly (at least with my local
> testing)!
> 
> There might be a few other rough edges, but this is a start and figured
> I would share what I had so far...
> 
> live well,
>   vagrant

> diff --git a/debian/README.debian b/debian/README.debian
> index dbef811..9bebdde 100644
> --- a/debian/README.debian
> +++ b/debian/README.debian
> @@ -2,7 +2,7 @@ clc-intercal for Debian
>  ---
>  
>  Some sample programs have been included in the package.  Further
> -reference material and more sample INTERCAL programs are avalible with
> +reference material and more sample INTERCAL programs are available with
>  the C-INTERCAL compiler in the intercal package.
>  
>   -- Mark Brown , Fri,  5 Nov 1999 16:18:20 +
> diff --git a/debian/build-fix b/debian/build-fix
> deleted file mode 100644
> index a7cf9b0..000
> --- a/debian/build-fix
> +++ /dev/null
> @@ -1,12 +0,0 @@
> -diff -up 
> CLC-INTERCAL-1.-94.-2/CLC-INTERCAL-Base-1.-94.-2/INTERCAL/Sick.pm.orig 
> CLC-INTERCAL-1.-94.-2/CLC-INTERCAL-Base-1.-94.-2/INTERCAL/Sick.pm
>  CLC-INTERCAL-1.-94.-2/CLC-INTERCAL-Base-1.-94.-2/INTERCAL/Sick.pm.orig 
> 2008-03-29 11:09:06.0 -0600
> -+++ CLC-INTERCAL-1.-94.-2/CLC-INTERCAL-Base-1.-94.-2/INTERCAL/Sick.pm 
> 2013-08-02 13:55:41.952276530 -0600
> -@@ -709,7 +709,7 @@ sub _guess_charset {
> - my $count = 0;
> - while ((my $line = $fh->write_binary(4096)) ne '') {
> - my $cl = &$cnv($line);
> --$count++ while $line =~ /DO|PLEASE/ig;
> -+$count++ while $cl =~ /DO|PLEASE/ig;
> - }
> - $counts{$name} = $count;
> - };
> diff --git a/debian/changelog b/debian/changelog
> index c905658..eb20b8c 100644
> --- a/debian/changelog
> +++ b/debian/changelog
> @@ -1,3 +1,10 @@
> +clc-intercal (1:1.-94.-2.1-1~0) UNRELEASED; urgency=medium
> +
> +  * Non-maintainer upload.
> +  * 1.-94.-2.1
> +
> + -- Vagrant Cascadian   Sat, 06 May 2023 12:19:54 -0700
> +
>  clc-intercal (1:1.0~4pre1.-94.-2-5.1) unstable; urgency=medium
>  
>* Non maintainer upload by the Reproducible Builds team.
> @@ -133,8 +140,8 @@ clc-intercal (0.05-3) unstable; urgency=low
>  clc-intercal (0.05-2) unstable; urgency=low
>  
>* Don't install oo, ick man page.  This means oo, ick is undocumented,
> -but works around the fact that the cache building in man-db dies 
> -horribly when confronted with a man page with a space in the name, 
> +but works around the fact that the cache building in man-db dies
> +horribly when confronted with a man page with a space in the name,
>  rendering man-db useless (fixes: #50455).
>  
>   -- Mark Brown   Thu, 18 Nov 1999 19:32:18 +
> diff --git a/debian/clc-intercal.dirs b/debian/clc-intercal.dirs
> deleted file mode 100644
> index de8a730..000
> --- a/debian/clc-intercal.dirs
> +++ /dev/null
> @@ -1,2 +0,0 @@
> -usr/bin
> -usr/share/doc/clc-intercal/examples
> diff --git a/debian/clc-intercal.docs b/debian/clc-intercal.docs
> index cf935a6..9184aa6 100644
> --- a/debian/clc-intercal.docs
> +++ b/debian/clc-intercal.docs
> @@ -1,4 +1,4 @@
> -README 
> -CLC-INTERCAL-Base-1.-94.-2/MISSING
> -CLC-INTERCAL-Docs-1.-94.-2/doc/html
> -CLC-INTERCAL-Docs-1.-94.-2/doc/INTERNET
> +README.md
> +CLC-INTERCAL-Base/MISSING
> +CLC-INTERCAL-Docs/doc/html
> +CLC-INTERCAL-Docs/doc/INTERNET
> diff --git a/debian/clc-intercal.examples b/debian/clc-intercal.examples
> index ed410a6..def9c9a 100644
> --- a/debian/clc-intercal.examples
> +++ b/debian/clc-intercal.examples
> @@ -1,30 +1,30 @@
> -CLC-INTERCAL-Docs-1.-94.-2/doc/examples/gcd.i
> -CLC-INTERCAL-Docs-1.-94.-2/doc/examples/hello.i
> -CLC-INTERCAL-Docs-

Bug#1070854: clc-intercal FTBFS: dpkg-genbuildinfo: error: binary build with no binary artifacts found

[Mark Brown]

On Fri, May 10, 2024 at 05:25:35PM +0300, Adrian Bunk wrote:

> chmod +x `pwd`/debian/clc-intercal/usr/bin/*
>  dpkg-genbuildinfo --build=any 
> -O../clc-intercal_1.00-1_ppc64el-buildd.buildinfo
> dpkg-genbuildinfo: error: binary build with no binary artifacts found; 
> .buildinfo is meaningless
> dpkg-buildpackage: error: dpkg-genbuildinfo --build=any 
> -O../clc-intercal_1.00-1_ppc64el-buildd.buildinfo subprocess returned exit 
> status 25

I can't reproduce this, and nothing about the build I'm seeing in the
log looks meaningfully different to what I get when I build locally.
AFAICT there are .so files being installed among the various perl things
and dpkg-genbuildinfo runs happily.


signature.asc
Description: PGP signature

Bug#1071071: python3-poetry: depends on packaging

[Mark A. Hershberger]

Package: python3-poetry
Version: 1.8.2+dfsg-1
Severity: normal

$ sudo apt install -t testing python3-poetry
...
Setting up python3-poetry (1.8.2+dfsg-1)
...
$ poetry run python

No module named 'packaging.metadata'

$ sudo apt install -t testing python3-packaging
...
Setting up python3-packaging (24.0-1) ...
$ poetry run python
Creating virtualenv devops-fabric-MXLzDq5t-py3.12 in 
/home/mah/.cache/pypoetry/virtualenvs
Python 3.11.2 (main, Mar 13 2023, 12:18:29) [GCC 12.2.0] on linux
Type "help", "copyright", "credits" or "license" for more information.
>>> 

-- System Information
Debian Release: 12.5
Kernel Version: Linux gabriel 6.1.0-20-amd64 #1 SMP PREEMPT_DYNAMIC Debian 
6.1.85-1 (2024-04-11) x86_64 GNU/Linux

Bug#1061902: consolekit2: NMU diff for 64-bit time_t transition

[Mark Hindley]

Control: tags -1 moreinfo

Michael and Steve,

I would appreciate some help here.

On Tue, Mar 05, 2024 at 07:33:40AM +, Mark Hindley wrote:
> Control: severity -1 normal
> 
> On Tue, Feb 06, 2024 at 05:43:41PM +0000, Mark Hindley wrote:
> > Whilst I am not an expert on this transition or the abi-compliance-checker, 
> > a
> > quick look at the logs[1] suggests this is a tool configuration issue and
> > src:consolekit2 may not require t64 migration.
> > 
> > Can you clarify?

I am still not convinced that consolekit2 requires this. As identified above, it
looks to me that the abi-compliance-checker tool failed and that failure flagged
consolekit2 as requiring t64 migration.

I may be looking for the wrong thing (in which case, please tell me the correct
thing to look for), but there are no references to time_t in either library and
the output from:

$ git -C /home/mark/src/devuan/consolekit2/ grep time_t libconsolekit/ 
libck-connector/

is empty.

The only references to time_t are in src/ck-tty-idle-monitor.c (used in
/usr/sbin/console-kit-daemon) and tools/ck-history.c (/usr/bin/ck-history).

$ git -C /home/mark/src/devuan/consolekit2/ grep time_t
src/ck-tty-idle-monitor.c:time_t  now;
src/ck-tty-idle-monitor.c:time_t  idletime;
src/ck-tty-idle-monitor.c:time_t  last_access;
tools/ck-history.c:time_t secs;
tools/ck-history.c:time_t  added_t, removed_t;
tools/ck-history.c:time_t  oldest_e;
tools/ck-history.c:time_t  oldest_e;

I am reluctant to implement this change unnecessarily.

I would appreciate you expertise and guidance.

Many thanks

Mark

Bug#1070650: linux-image-6.7.7-amd64: Updates needed for 2024 Platform support - graphics, wifi, CPU, audio

[Mark Pearson]

Package: src:linux
Version: 6.7.7-1
Severity: important
X-Debbugs-Cc: mpearson-len...@squebb.ca

I realise this bug is overly broad, but testing Debian on the 2024 platforms 
and updated kernel is needed for a better user experience

 - Meteorlake support is a bit limited before 6.8. Need updated kernel for 
graphic, audio, power support.
 - Intel AX211 driver is in newer kernel.
 - AMD graphics drivers have seen significant improvements in 6.8

This also links to #1070647 and #1070648 where FW updates are required.

Very happy to help if any tested needed. I've had users trying to run Debian on 
their systems and would like to be able to help them get up and runninng.

Note - kernel logs below are with updated FW that I manually installed myself. 
Without these I don't have functional graphics of wifi :)

Thanks
Mark

-- Package-specific info:
** Version:
Linux version 6.7.7-amd64 (debian-ker...@lists.debian.org) 
(x86_64-linux-gnu-gcc-13 (Debian 13.2.0-16.1) 13.2.0, GNU ld (GNU Binutils for 
Debian) 2.42) #1 SMP PREEMPT_DYNAMIC Debian 6.7.7-1 (2024-03-02)

** Command line:
BOOT_IMAGE=/boot/vmlinuz-6.7.7-amd64 
root=UUID=864f906b-6c9a-49b9-bdbe-78e4b4a88d9d ro quiet

** Not tainted

** Kernel log:
[5.157952] cryptd: max_cpu_qlen set to 1000
[5.164733] ACPI Warning: \_SB.PC00.XHCI.RHUB.HS10._DSM: Argument #4 type 
mismatch - Found [Integer], ACPI requires [Package] (20230628/nsarguments-61)
[5.165165] Bluetooth: hci0: DSM reset method type: 0x00
[5.165836] iwlwifi :00:14.3: Detected Intel(R) Wi-Fi 6E AX211 160MHz, 
REV=0x441
[5.165896] thermal thermal_zone8: failed to read out thermal zone (-61)
[5.169658] bluetooth hci0: firmware: direct-loading firmware 
intel/ibt-0180-0041.sfi
[5.174253] Bluetooth: hci0: Found device firmware: intel/ibt-0180-0041.sfi
[5.174303] Bluetooth: hci0: Boot Address: 0x100800
[5.174304] Bluetooth: hci0: Firmware Version: 132-8.24
[5.176650] AVX2 version of gcm_enc/dec engaged.
[5.176706] AES CTR mode by8 optimization enabled
[5.177586] iwlwifi :00:14.3: WRT: Invalid buffer destination
[5.183424] sof-audio-pci-intel-mtl :00:1f.3: DSP detected with PCI 
class/subclass/prog-if info 0x040380
[5.184986] sof-audio-pci-intel-mtl :00:1f.3: Digital mics found on 
Skylake+ platform, using SOF driver
[5.185540] sof-audio-pci-intel-mtl :00:1f.3: DSP detected with PCI 
class/subclass/prog-if 0x040380
[5.185595] sof-audio-pci-intel-mtl :00:1f.3: bound :00:02.0 (ops 
i915_audio_component_bind_ops [i915])
[5.192677] sof-audio-pci-intel-mtl :00:1f.3: use msi interrupt mode
[5.239977] typec port0: bound usb1-port3 (ops connector_ops [usbcore])
[5.240002] typec port0: bound usb4-port1 (ops connector_ops [usbcore])
[5.254026] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[5.254028] Bluetooth: BNEP filters: protocol multicast
[5.254032] Bluetooth: BNEP socket layer initialized
[5.258126] Btrfs loaded, zoned=yes, fsverity=yes
[5.273296] sof-audio-pci-intel-mtl :00:1f.3: hda codecs found, mask 5
[5.273298] sof-audio-pci-intel-mtl :00:1f.3: using HDA machine driver 
skl_hda_dsp_generic now
[5.273301] sof-audio-pci-intel-mtl :00:1f.3: DMICs detected in NHLT 
tables: 2
[5.274536] sof-audio-pci-intel-mtl :00:1f.3: firmware: direct-loading 
firmware intel/sof-ipc4/mtl/sof-mtl.ri
[5.274976] sof-audio-pci-intel-mtl :00:1f.3: Loaded firmware library: 
ADSPFW, version: 2.8.1.1
[5.342774] iwlwifi :00:14.3: Not valid error log pointer 0x0027B0C0 for 
RT uCode
[5.342847] iwlwifi :00:14.3: WFPM_UMAC_PD_NOTIFICATION: 0x1f
[5.342866] iwlwifi :00:14.3: WFPM_LMAC2_PD_NOTIFICATION: 0x1f
[5.342873] iwlwifi :00:14.3: WFPM_AUTH_KEY_0: 0x80
[5.342882] iwlwifi :00:14.3: CNVI_SCU_SEQ_DATA_DW9: 0x0
[5.343634] iwlwifi :00:14.3: RFIm is deactivated, reason = 4
[5.343711] iwlwifi :00:14.3: firmware: direct-loading firmware 
iwlwifi-ma-b0-gf-a0.pnvm
[5.343796] iwlwifi :00:14.3: loaded PNVM version ce1a5094
[5.353058] NET: Registered PF_QIPCRTR protocol family
[5.359195] iwlwifi :00:14.3: Detected RF GF, rfid=0x2010d000
[5.382188] sof-audio-pci-intel-mtl :00:1f.3: Booted firmware version: 
2.8.1.1
[5.389778] sof-audio-pci-intel-mtl :00:1f.3: firmware: direct-loading 
firmware intel/sof-ace-tplg/sof-hda-generic-2ch.tplg
[5.389812] sof-audio-pci-intel-mtl :00:1f.3: Topology: ABI 3:29:0 
Kernel ABI 3:23:0
[5.389997] skl_hda_dsp_generic skl_hda_dsp_generic: ASoC: Parent card not 
yet available, widget card binding deferred
[5.413768] snd_hda_codec_realtek ehdaudio0D0: autoconfig for ALC287: 
line_outs=1 (0x17/0x0/0x0/0x0/0x0) type:speaker
[5.413772] snd_hda_codec_realtek ehdaudio0D0:speaker_outs=0 
(0x0/0x0/0x0/0x0/0x0)
[5.413773] snd_hda_codec_realtek ehdaudio0D0:hp_outs=1 
(0x21/0x0/0x0/0x0/0x0)
[5.413774] snd_hda_codec_realtek ehdaudio0D0

Bug#1070648: firmware-iwlwifi: Update needed for Intel AX211 Wifi support

[Mark Pearson]

Package: firmware-iwlwifi
Version: 20230625-2
Severity: important
X-Debbugs-Cc: mpearson-len...@squebb.ca

I've been testing Debian on the new Lenovo Meteorlake based platforms with 
AX211 Intel wifi, and seeing lots of problems related to out of date kernel and 
firmware support.

This bug is being raised to specifically track getting the iwlwifi firmware 
packages updated

Please let me know how I can help. Happy to do any testing, and I have some 
limited experience with packaging from maintaining the firmware-sof-signed 
packag>

Thanks
Mark



-- System Information:
Debian Release: trixie/sid
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 
'testing')
Architecture: amd64 (x86_64)

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

firmware-iwlwifi depends on no packages.

firmware-iwlwifi recommends no packages.

Versions of packages firmware-iwlwifi suggests:
ii  initramfs-tools  0.142

-- no debconf information

Bug#1070647: firmware-misc-nonfree: Update needed to support Meteorlake graphics

[Mark Pearson]

Package: firmware-misc-nonfree
Version: 20230625-2
Severity: important
X-Debbugs-Cc: mpearson-len...@squebb.ca

I've been testing Debian on the new Lenovo Meteorlake based platforms and 
seeing lots of problems related to out of date kernel and firmware support.

This bug is being raised to specifically track getting the graphics firmware 
packages updated - /lib/firmware/i915

Please let me know how I can help. Happy to do any testing, and I have some 
limited experience with packaging from maintaining the firmware-sof-signed 
packag>

As a note - iwlwifi and kernel itself need updating too, but I will do separate 
bugs for those
Thanks
Mark

-- System Information:
Debian Release: trixie/sid
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 
'testing')
Architecture: amd64 (x86_64)

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

firmware-misc-nonfree depends on no packages.

firmware-misc-nonfree recommends no packages.

Versions of packages firmware-misc-nonfree suggests:
ii  initramfs-tools  0.142

-- no debconf information

Bug#1070295: cgroupfs-mount: Fails to upgrade or remove if elogind is running: "umount: /sys/fs/cgroup/elogind: target is busy."

[Mark Hindley]

Lorenzo,

Thanks for the reminder.

On Fri, May 03, 2024 at 03:10:57PM +0200, Lorenzo wrote:
> Is this is a duplicate of #950986?
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=950986
> I bet the patch there would fix this bug too

Embarrassingly, that is my patch which I clearly have no recollection of! :-|

Now I look, we have been shipping a variation on it in Devuan since 2020[1].

Mark

[1]  
https://git.devuan.org/devuan/cgroupfs-mount/commit/ff91abfaf3a5c5633744ea552084125ec6c68ce5

Bug#1070295: cgroupfs-mount: Fails to upgrade or remove if elogind is running: "umount: /sys/fs/cgroup/elogind: target is busy."

[Mark Hindley]

Axel,

On Fri, May 03, 2024 at 01:05:15PM +0200, Axel Beckert wrote:
> P.S.: Given that Christian's NMU doesn't even touch the maintainer
> scripts, I suspect that this issue is also present in version 1.4. I
> though didn't notice it before then, so it might be related to recent
> elogind changes, hence Cc'ing the Debian Init System Diversity Team,
> too.

Since this is the first cgroupfs-mount update since 2017 (which predates
elogind's arrival in Debian) I suspect it has always been there, just uncovered
by the cgroupfs-mount NMU.

My gut reaction is that cgroupfs-mount shouldn't be unmounting and remounting
cgroups on upgrade and it needs some dh_installinit magic in d/rules.

Mark

Bug#1070167: openrc: postinst fails with not executable script in /etc/init.d/

[Mark Hindley]

Lorenzo,

I think this issue is sufficiently significant to fix in bookworm. I'll wait
until the fix is well tested first.

Mark

Bug#1070167: openrc: postinst fails with not executable script in /etc/init.d/

[Mark Hindley]

On Wed, May 01, 2024 at 07:10:29PM +0200, Lorenzo wrote:
> > Thanks. Does the attached patch help?
> 
> yes, it seems it works

Good.

As small refinement to avoid emitting inappropriate dangling symlink warnings.

Mark
>From 07d2dd72221e961637ea7a9cd2143b6c8a411373 Mon Sep 17 00:00:00 2001
From: Mark Hindley 
Date: Wed, 1 May 2024 18:33:39 +0100
Subject: [PATCH] Don't emit dangling symlink warning for non-executable
 scripts.

---
 debian/openrc.postinst | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/debian/openrc.postinst b/debian/openrc.postinst
index 3b62f026..e53be30c 100644
--- a/debian/openrc.postinst
+++ b/debian/openrc.postinst
@@ -37,8 +37,8 @@ if [ "${1}" = "configure" ] ; then
 echo "*** WARNING: skipping non-executable $rclink"
 			else
 echo "*** WARNING: dangling link $rclink"
+				echo $dsvcs|grep -qw ${svc} || dsvcs="$dsvcs ${svc}"
 			fi
-			echo $dsvcs|grep -qw ${svc} || dsvcs="$dsvcs ${svc}"
 			fi
 		done
 	done
-- 
2.39.2

Bug#1070167: openrc: postinst fails with not executable script in /etc/init.d/

[Mark Hindley]

Control: tags -1 patch

Lorenzo,

On Wed, May 01, 2024 at 10:59:36AM +0200, Lorenzo Puliti wrote:
> Package: openrc
> Version: 0.45.2-2
> Severity: normal
> X-Debbugs-Cc: plore...@disroot.org
> 
> Hi,
> 
> it appears that, at least under certain conditions, openrc postinstall
> script fails if a sysvinit script in /etc/init.d/ is not executable.
> 
> Note that recently debhelper started to chmod -x initscripts when a package is
> removed but not purged, so openrc should deal whit non executebles files under
> /etc/init.d/

Thanks. Does the attached patch help?

Mark
>From 7d20e19bf392869853fb7df884030c669d7ff641 Mon Sep 17 00:00:00 2001
From: Mark Hindley 
Date: Wed, 1 May 2024 11:16:44 +0100
Subject: [PATCH] d/openrc.postinst: ignore non-executable scripts in
 /etc/init.d

Closes: #1070167
---
 debian/openrc.postinst | 8 ++--
 1 file changed, 6 insertions(+), 2 deletions(-)

diff --git a/debian/openrc.postinst b/debian/openrc.postinst
index 6e5cd7ae..3b62f026 100644
--- a/debian/openrc.postinst
+++ b/debian/openrc.postinst
@@ -25,7 +25,7 @@ if [ "${1}" = "configure" ] ; then
 			rclink=/etc/rc${rl}.d/${f}
 			initsh=$(readlink -f ${rclink})
 			svc=$(basename ${initsh})
-			if [ -f ${initsh} ]; then
+			if [ -x ${initsh} ]; then
 case ${rl} in
 1) orl="recovery" ;;
 2) orl="default" ;;
@@ -33,8 +33,12 @@ if [ "${1}" = "configure" ] ; then
 esac
 rc-update add ${svc} ${orl}
 			else
+			if [ -f ${initsh} ]; then
+echo "*** WARNING: skipping non-executable $rclink"
+			else
 echo "*** WARNING: dangling link $rclink"
-echo $dsvcs|grep -qw ${svc} || dsvcs="$dsvcs ${svc}"
+			fi
+			echo $dsvcs|grep -qw ${svc} || dsvcs="$dsvcs ${svc}"
 			fi
 		done
 	done
-- 
2.39.2

Bug#1070032: elogind: add NEWS for 255.4.1, suspend now default to s2idle instead of s2ram

[Mark Hindley]

On Mon, Apr 29, 2024 at 01:11:11AM +0200, Lorenzo Puliti wrote:
> I think this change is worth a NEWS entry, with an example
> that explains how to revert to the previous default.

Sounds a good idea. Thanks.

I'll queue your suggestion for the next upload.

Best wishes,

Mark

Bug#1069787: debootstrap: autopkgtest fails since t64 migration

[Mark Hindley]

Actually, the situation has deteriorated further. In addition to gnupg, the
systemd pre-depends on libssl3 is no longer satisfiable:

dpkg: regarding .../systemd_255.4-1_amd64.deb containing systemd, 
pre-dependency problem:
 systemd pre-depends on libssl3 (>= 3.0.0)
  libssl3 is not installed.

$ rmadison -s trixie libssl3 libssl3t64
libssl3t64 | 3.2.1-3   | testing| amd64, arm64, armel, armhf, i386, 
mips64el, ppc64el, s390x
libssl3| 3.1.5-1   | testing| armel, armhf

Mark

Bug#1069787: debootstrap: autopkgtest fails since t64 migration

[Mark Hindley]

Package: debootstrap
Version: 1.0.134
Severity: important
Tags: patch


Dear Maintainer,

The debian/tests/debian-testing autopkgtest has been broken on 64bit archs by
the t64 transition in trixie. Specifically the test includes gnupg as an
additional package.  Gnupg depends on gpg-agent which depends on
libnpth0. However, in trixie, libnpth0 is now provided by libnpth0t64 which
debootstrap doesn't handle.

I suggest changing the test to include gpgv which avoids the t64 transition
whilst providing similar functional coverage.

Patch attached.

Mark



-- System Information:
Debian Release: 12.0
merged-usr: no
Architecture: amd64 (x86_64)

Kernel: Linux 6.1.0-19-amd64 (SMP w/2 CPU threads; PREEMPT)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_GB:en
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)

Versions of packages debootstrap depends on:
ii  wget  1.21.3-1+b2

Versions of packages debootstrap recommends:
ii  arch-test   0.21-1
ii  gnupg   2.2.40-1.1
ii  mount   2.38.1-5+deb12u1

Versions of packages debootstrap suggests:
ii  debian-archive-keyring  2023.3+deb12u1
pn  squid-deb-proxy-client  
pn  ubuntu-archive-keyring  

-- no debconf information
>From 1a79250dc45375032f4758204ec3234fd4ed006a Mon Sep 17 00:00:00 2001
From: Mark Hindley 
Date: Wed, 24 Apr 2024 10:01:53 +0100
Subject: [PATCH] d/t/debian-testing: change from gnupg to gpgv;  debootstrap
 with gnupg is broken by libnpth0t64 Provides libnpth0.

---
 debian/tests/debian-testing | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/debian/tests/debian-testing b/debian/tests/debian-testing
index 7c3e323..89a04fe 100755
--- a/debian/tests/debian-testing
+++ b/debian/tests/debian-testing
@@ -340,7 +340,7 @@ my $testing = $distro_info->testing;
 
 # Should specify multiple components for checking (see Bug#898738)
 if (!verbose_run([length($ENV{DEBOOTSTRAP_SCRIPT}) ? $ENV{DEBOOTSTRAP_SCRIPT} 
: 'debootstrap',
-'--include=debootstrap,debian-archive-keyring,gnupg,hello,systemd',
+'--include=debootstrap,debian-archive-keyring,gpgv,hello,systemd',
 '--variant=minbase',
 '--components=main,contrib,non-free',
 $testing, 'chroot.d', $mirror], '>&2')) {
-- 
2.39.2

Bug#1069102: linux-image-6.1.0-20-amd64 and cifs mount problem on some folders which get hidden on shares

[Mark Ullmann]

Package: src:linux
Version: 6.1.85-1
Followup-For: Bug #1069102
X-Debbugs-Cc: email4deb...@gmx.net

Dear Maintainer,

I noticed the same issue.

I have a mount:
mount -t cifs //XXX/Backups/borg-backup /mnt/backups -o
noserverino,credentials=/etc/xxx,file_mode=0777,dir_mode=0777  -vvv

In the mounted directory, a folder is missing. I can see the folder
when I connect to the share via Dolphin.
(This is a backup-drive and I noticed because borg-backup threw errors.)

This is reproducible: after a reboot and mounting the share again, the same
folder is missing and the other folders are shown.


I build a kernel with the patch from #26, which I am running right now. The
problem seems to be gone: borg-backup now runs cleanly. So I assume the mount
is fine with the patch from #26.

I could probably test a kernel if it installs on stable.

Best, Mark.


*** Reporter, please consider answering these questions, where appropriate ***

   * What led up to the situation?
   * What exactly did you do (or not do) that was effective (or
 ineffective)?
   * What was the outcome of this action?
   * What outcome did you expect instead?

*** End of the template - remove these template lines ***


-- Package-specific info:
** Kernel log: boot messages should be attached

** Model information
sys_vendor: TUXEDO
product_name: N24_25BU
product_version: Not Applicable  
chassis_vendor: TUXEDO
chassis_version: N/A 
bios_vendor: American Megatrends Inc.
bios_version: 5.12
board_vendor: TUXEDO
board_name: N24_25BU
board_version: Not Applicable  

** Network interface configuration:
*** /etc/network/interfaces:

source /etc/network/interfaces.d/*

auto lo
iface lo inet loopback

** PCI devices:
00:00.0 Host bridge [0600]: Intel Corporation Xeon E3-1200 v6/7th Gen Core 
Processor Host Bridge/DRAM Registers [8086:5904] (rev 02)
Subsystem: CLEVO/KAPOK Computer Xeon E3-1200 v6/7th Gen Core Processor 
Host Bridge/DRAM Registers [1558:2410]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- 
Kernel driver in use: skl_uncore

00:02.0 VGA compatible controller [0300]: Intel Corporation HD Graphics 620 
[8086:5916] (rev 02) (prog-if 00 [VGA controller])
Subsystem: CLEVO/KAPOK Computer HD Graphics 620 [1558:2410]
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- 
Kernel driver in use: i915
Kernel modules: i915

00:08.0 System peripheral [0880]: Intel Corporation Xeon E3-1200 v5/v6 / 
E3-1500 v5 / 6th/7th/8th Gen Core Processor Gaussian Mixture Model [8086:1911]
Subsystem: CLEVO/KAPOK Computer Xeon E3-1200 v5/v6 / E3-1500 v5 / 
6th/7th/8th Gen Core Processor Gaussian Mixture Model [1558:2410]
Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- 

00:14.0 USB controller [0c03]: Intel Corporation Sunrise Point-LP USB 3.0 xHCI 
Controller [8086:9d2f] (rev 21) (prog-if 30 [XHCI])
Subsystem: CLEVO/KAPOK Computer Sunrise Point-LP USB 3.0 xHCI 
Controller [1558:2410]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- 
SERR- 
Kernel driver in use: xhci_hcd
Kernel modules: xhci_pci

00:14.2 Signal processing controller [1180]: Intel Corporation Sunrise Point-LP 
Thermal subsystem [8086:9d31] (rev 21)
Subsystem: CLEVO/KAPOK Computer Sunrise Point-LP Thermal subsystem 
[1558:2410]
Control: I/O- Mem+ BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- 
Kernel driver in use: intel_pch_thermal
Kernel modules: intel_pch_thermal

00:16.0 Communication controller [0780]: Intel Corporation Sunrise Point-LP 
CSME HECI #1 [8086:9d3a] (rev 21)
Subsystem: CLEVO/KAPOK Computer Sunrise Point-LP CSME HECI [1558:2410]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- 
Kernel driver in use: mei_me
Kernel modules: mei_me

00:17.0 SATA controller [0106]: Intel Corporation Sunrise Point-LP SATA 
Controller [AHCI mode] [8086:9d03] (rev 21) (prog-if 01 [AHCI 1.0])
Subsystem: CLEVO/KAPOK Computer Sunrise Point-LP SATA Controller [AHCI 
mode] [1558:2410]
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 6

Bug#1069182: Reassign lvm2

[Mark Hindley]

Control: reassign -1 lvm2

On Thu, Apr 18, 2024 at 02:24:06PM +0500, Alex Volkov wrote:
> On четверг, 18 апреля 2024 г. 11:38:18 +05 Mark Hindley wrote:
> 
> >   udevadm: info --cleanup-db
> >   "db_persist=" -> "db_persist"
> >   require explicit "db_persist" to exclude device info from --db-cleanup
> 
> Wow. I knew there's something in this transition to --db-cleanup.
> 
> > Does this mean that dm mapper should set db_persist in the initramfs?
> 
> More like it's actually needs to be set by the corresponding udev rule in lvm2
> package (which does all that device-mapper devices detection). I tried adding
> the corresponding OPTIONS+="db_persist" line into 55-dm.rules file and it
> worked as intended. I will report the bug to lvm2.

I think we can just reassign this one.

Dear lvm2 maintainers,

We have been investigating why devices discovered by the initramfs were being
cleaned by /etc/init.d/udev. The udev initscript runs

 udevadm info --cleanup-db.

It appears to be the responsibility of devices that should not be cleaned to set
db_persist in their setup rule.

There appears to be a recent upstream lvm2 commit to address this[1].

Thanks

Mark

[1]  
https://gitlab.com/lvmteam/lvm2/-/commit/eb4f744820832aff3d6da1bba14f12e91a5b3535

Bug#1069182: More background

[Mark Hindley]

> Does this mean that dm mapper should set db_persist in the initramfs?

Or the initramfs generator. AFAICS dracut already does this[1], but I don't
immediately see an equivalent for initramfs-tools.

Are you using initramfs-tools? Does switching to dracut improve the situation?

Mark

[1]  https://codesearch.debian.net/search?q=db_persist+package%3A%5CQdracut%5CE

Bug#1069182: More background

[Mark Hindley]

Alex,

Thanks for your continued research into this.

The upstream 168 changelog is informative (edited for relevant parts):

Summary of changes from v167 to v168


Kay Sievers (35):
  udevadm: info --cleanup-db
  "db_persist=" -> "db_persist"
  require explicit "db_persist" to exclude device info from --db-cleanup

It is somewaht opaque, but the relevant commits appear to be in the current
systemd git[1].

Does this mean that dm mapper should set db_persist in the initramfs?

Mark

[1]  
https://github.com/search?q=repo%3Asystemd%2Fsystemd+db_persist=commits

Bug#1069182: initscripts: udev initscript SHOULD NOT clear the udev database at startup

[Mark Hindley]

Boian,

On Wed, Apr 17, 2024 at 02:53:08PM +0100, Mark Hindley wrote:
> On Wed, Apr 17, 2024 at 05:25:08PM +0500, Alex Volkov wrote:
> > Now, /etc/init.d/udev for some reason does this in its start clause:
> > 
> > ===
> >135  # clean up parts of the database created by the initramfs udev
> >136  udevadm info --cleanup-db
> > ===

I notice Devuan's eudev initscript contains the same[1], presumably with the
same origin. Do you have any thoughts on its purpose or necessity?

Thanks

Mark

[1]  
https://git.devuan.org/devuan/eudev/src/branch/suites/unstable/debian/eudev.init#L160

Bug#1069182: initscripts: udev initscript SHOULD NOT clear the udev database at startup

[Mark Hindley]

Control: tags -1 moreinfo help

Alex,

Many thanks for this and your detailed analysis.

On Wed, Apr 17, 2024 at 05:25:08PM +0500, Alex Volkov wrote:
> Now, /etc/init.d/udev for some reason does this in its start clause:
> 
> ===
>135  # clean up parts of the database created by the initramfs udev
>136  udevadm info --cleanup-db
> ===

 [...] 

> Note that systemd-based systems are not affected, as they seemingly don't 
> relate to the initrd scripts for starting udev.

I suspect the original reason for this will be hard to track down. Git blaming
d/udev.init from systemd 254.1-3 shows those lines as being merged in 2013 from
udev 175-7[1].

> If there is a valid reason for cleaning the database, the issue needs to be
> researched further, of course.

Quite.

Dear systemd maintainers,

Do you have any insight into why clearing the initramfs udev db might have been
or might still be required? Or any unanticipated effects of not doing so?

Thanks

Mark

[1]  
https://salsa.debian.org/systemd-team/systemd/-/commit/b56f8637a1e03ac6a45af7820287159df9b506b9

Bug#1069177: sysvinit-utils: wording mistake in description

[Mark Hindley]

Control: tags -1 pending

Maytham,

On Wed, Apr 17, 2024 at 02:33:29PM +0300, Maytham Alsudany wrote:
> Package: sysvinit-utils
> Version: 3.08-7
> Severity: minor
> 
> Found this while translating; do you mean "formerly"?

Yes, of course. Thanks for pointing it out.

Queued for the next upload.

Mark

Bug#1062445: yq: Replace with alternative yq app

[Sheppard, Mark]

I second the original request.  I installed yq on my Mac using “brew install 
yq”, wrote a script and then deployed it to a Debian machine on which I’d run 
“apt install yq".  But when I ran the script on the Debian machine I got a 
syntax error in the “yq” command.  It was then that I realised Homebrew had 
installed the mikefarah version but Debian had installed the kislyuk version.  
Looking at the GitHub pages for the two projects the mikefarah one has over 
four times the number of stars of the kislyuk one so is the more popular of the 
two.  It’s also a separate fully-featured program rather than just being a 
wrapper round jq.

Bug#1068653: close

[Mark A. Hershberger]

close #1068653

Restarting laptop after upgrading to unstable (from stable) worked.

Bug#1068653: evolution: Can't use google accounts

[Mark A. Hershberger]

Package: evolution
Version: 3.50.3-1+b1
Severity: grave

I have two accounts (personal and work) and both of them are returning
“Timeout was reached”.  I have tried removing the accounts and re-adding
them without success.

personal account is @gmail.com

work account is @EMPLOYER'S-DOMAIN

-- System Information
Debian Release: 12.5
Kernel Version: Linux gabriel 6.1.0-18-amd64 #1 SMP PREEMPT_DYNAMIC Debian 
6.1.76-1 (2024-02-01) x86_64 GNU/Linux

-- 
http://hexmode.com/

Don't ask me who's influenced me. A lion is made up of the
lambs he's digested, and I've been reading all my life.
-- Giorgos Seferis

Bug#1068245: ITP: iwgtk -- lightweight graphical frontend to iwd

[Mark Hindley]

Package: wnpp
Severity: wishlist
Owner: Mark Hindley 
X-Debbugs-Cc: debian-de...@lists.debian.org

* Package name: iwgtk
  Version : 0.9
  Upstream Contact: Jesse Lentz 
* URL : https://github.com/J-Lentz/iwgtk
* License : GPL3+
  Programming Lang: C
  Description : Lightweight graphical frontend to iwd

iwgtk is a lightweight gtk4 frontend to iwd which provides similar
functionality to that of iwctl.
 
Features include viewing and connecting to available networks, managing known
networks, provisioning new networks via WPS or Wi-Fi Easy Connect and an
indicator (tray) icon displaying connection status and signal strength.

Mark

Bug#1068024: revert to version that does not contain changes by bad actor

[Mark-Oliver Wolter]

On Fri, 29 Mar 2024 22:32:23 +0100 Aurelien Jarno  
wrote:

> Having dpkg in that list means that such downgrade has to be planned
> carefully.

Might be easier overall to spend that effort on a hard switch to zstd 
instead.


mfG mow

Bug#1061493: consolekit: install PAM module and udev files into /usr

[Mark Hindley]

Control: notfound -1 1.2.6-3

On Wed, Mar 13, 2024 at 10:40:40PM +0100, Andreas Beckmann wrote:
> Followup-For: Bug #1061493
> Control: found -1 1.2.6-3.1~exp1
> Control: severity -1 serious
> Control: tag -1 ftbfs
> 
> This change causes consolekit2 to to FTBFS in experimental:

Indeed. As it was an NMU, I think the etiquette is for the NMUer to fix.

In sid consolekit2 still builds cleanly. Therefore, marking notfound there.

Michael, perhaps you would fix your NMU, or provide a better patch?

Thanks

Mark

Bug#1063099: openrc: NMU diff for 64-bit time_t transition

[Mark Hindley]

Control: severity -1 normal

Preventing autoremoval due to uninstallable dpkg-dev version in testing.

Mark

Bug#1066531: policykit-1: FTBFS: ../subprojects/mocklibc-1.0/src/netgroup-debug.c:25:3: error: implicit declaration of function ‘print_indent’ [-Werror=implicit-function-declaration]

[Mark Hindley]

Control: tags -1 patch

I also bumped into this whilst rebuilding src:policykit-1 yesterday.

There is an upstream patch[1], but it doesn't fix the build for me; I think it
is patching the wrong files.The problem appears to be multiple copies of
mocklibc. AFAICS ./test/mocklibc is not used in favour of a meson subproject.

The pkla-compat tarball also has mocklibc, but that is also patched already.

Getting the multiple layers of quilt and meson patches to work was
unpleasant. So the attached patch may save you some time.

HTH

Mark

[1]  
https://github.com/polkit-org/polkit/commit/0d78d1e4bf5ab3ce11678005b220aac0cfc5bee5

>From f50131bcb98802a66dcc1ee4cc952ca1cc9f8ff4 Mon Sep 17 00:00:00 2001
From: Mark Hindley 
Date: Wed, 13 Mar 2024 09:13:27 +
Subject: [PATCH] Import upstream patch to fix embedded mocklibc subproject
 FTBFS with gcc 14.

---
 ...e-print_indent-function-to-the-file-.patch | 91 +++
 debian/patches/series |  1 +
 2 files changed, 92 insertions(+)
 create mode 100644 debian/patches/06-embedded-mocklibc-move-the-print_indent-function-to-the-file-.patch

diff --git a/debian/patches/06-embedded-mocklibc-move-the-print_indent-function-to-the-file-.patch b/debian/patches/06-embedded-mocklibc-move-the-print_indent-function-to-the-file-.patch
new file mode 100644
index ..184161b7
--- /dev/null
+++ b/debian/patches/06-embedded-mocklibc-move-the-print_indent-function-to-the-file-.patch
@@ -0,0 +1,91 @@
+--- a/subprojects/mocklibc.wrap
 b/subprojects/mocklibc.wrap
+@@ -8,3 +8,5 @@
+ patch_url = https://wrapdb.mesonbuild.com/v1/projects/mocklibc/1.0/2/get_zip
+ patch_filename = mocklibc-1.0-2-wrap.zip
+ patch_hash = 0280f96a2eeb3c023e5acf4e00cef03d362868218d4a85347ea45137c0ef6c56
++diff_files = mocklibc-move-the-print_indent-function-to-the-file.patch
++
+--- /dev/null
 b/subprojects/packagefiles/mocklibc-move-the-print_indent-function-to-the-file.patch
+@@ -0,0 +1,69 @@
++From 0d78d1e4bf5ab3ce11678005b220aac0cfc5bee5 Mon Sep 17 00:00:00 2001
++From: Vincent Mihalkovic 
++Date: Fri, 8 Mar 2024 14:04:33 +0100
++Subject: [PATCH] mocklibc: move the print_indent function to the file where it
++ is used
++MIME-Version: 1.0
++Content-Type: text/plain; charset=UTF-8
++Content-Transfer-Encoding: 8bit
++
++This fixes build error with GCC >= 14 and clang >= 17,
++failing on:
++```
++../subprojects/mocklibc-1.0/src/netgroup-debug.c:25:3: error: implicit declaration of function ‘print_indent’ [-Wimplicit-function-declaration]
++   25 |   print_indent(stream, indent);
++  |   ^~~~
++```
++
++Closes: #6
++---
++ src/netgroup-debug.c | 11 +++
++ src/netgroup.c   | 11 ---
++ 2 files changed, 11 insertions(+), 11 deletions(-)
++
++diff --git a/src/netgroup-debug.c b/src/netgroup-debug.c
++index 81d6e728..46e5b25f 100644
++--- a/src/netgroup-debug.c
+ b/src/netgroup-debug.c
++@@ -21,6 +21,17 @@
++ #include 
++ #include 
++
+++/**
+++ * Print a varaible indentation to the stream.
+++ * @param stream Stream to print to
+++ * @param indent Number of indents to use
+++ */
+++static void print_indent(FILE *stream, unsigned int indent) {
+++  int i;
+++  for (i = 0; i < indent; i++)
+++fprintf(stream, "  ");
+++}
+++
++ void netgroup_debug_print_entry(struct entry *entry, FILE *stream, unsigned int indent) {
++   print_indent(stream, indent);
++
++diff --git a/src/netgroup.c b/src/netgroup.c
++index 06a8a894..e16e4519 100644
++--- a/src/netgroup.c
+ b/src/netgroup.c
++@@ -71,17 +71,6 @@ static char *parser_copy_word(char **cur) {
++   return result;
++ }
++
++-/**
++- * Print a varaible indentation to the stream.
++- * @param stream Stream to print to
++- * @param indent Number of indents to use
++- */
++-void print_indent(FILE *stream, unsigned int indent) {
++-  int i;
++-  for (i = 0; i < indent; i++)
++-fprintf(stream, "  ");
++-}
++-
++ /**
++  * Connect entries with 'child' type to their child entries.
++  * @param headentry Head of list of entries that need to be connected
++--
++2.39.2
+--- a/meson.build
 b/meson.build
+@@ -7,7 +7,7 @@
+ 'prefix=/usr',
+ 'cpp_std=c++17',
+   ],
+-  meson_version: '>= 0.50.0',
++  meson_version: '>= 0.63.0',
+ )
+ 
+ pk_version = meson.project_version()
diff --git a/debian/patches/series b/debian/patches/series
index ddbec3c1..24156d33 100644
--- a/debian/patches/series
+++ b/debian/patches/series
@@ -1,3 +1,4 @@
+06-embedded-mocklibc-move-the-print_indent-function-to-the-file-.patch
 04-fix-pkexec-fails-with-GDBus.Error-org.freedesktop.Po.patch
 01_devuan-pkexec-pass-gtk-vars.patch
 02_gettext.patch
-- 
2.39.2

Bug#1061902: consolekit2: NMU diff for 64-bit time_t transition

[Mark Hindley]

Control: severity -1 normal

On Tue, Feb 06, 2024 at 05:43:41PM +, Mark Hindley wrote:
> Whilst I am not an expert on this transition or the abi-compliance-checker, a
> quick look at the logs[1] suggests this is a tool configuration issue and
> src:consolekit2 may not require t64 migration.
> 
> Can you clarify?

I would appreciate some help here. Your patch FTBFS and I need to be convinced
it is actually required before spending time on it.

In the meantime, downgrading severity to prevent autoremoval.

Thanks

Mark

Bug#1063911: davmail-server.service fails in a LXC container

[Mark Gardner]

.Properties member=PropertiesChanged
cookie=6126 reply_cookie=0 signature=sa{sv}as error-name=n/a
error-message=n/a
Feb 15 07:41:23 davmail systemd[1]: Sent message type=signal
sender=org.freedesktop.systemd1 destination=n/a
path=/org/freedesktop/systemd1/unit/tmp_2emount
interface=org.freedesktop.DBus.Properties member=PropertiesChanged
cookie=18 reply_cookie=0 signature=sa{sv}as error-name=n/a error-message=n/a
Feb 15 07:41:23 davmail systemd[1]: Sent message type=signal
sender=org.freedesktop.systemd1 destination=n/a
path=/org/freedesktop/systemd1/unit/tmp_2emount
interface=org.freedesktop.DBus.Properties member=PropertiesChanged
cookie=19 reply_cookie=0 signature=sa{sv}as error-name=n/a error-message=n/a
Feb 15 07:41:23 davmail systemd[1]: Sent message type=signal sender=n/a
destination=n/a path=/org/freedesktop/systemd1/unit/tmp_2emount
interface=org.freedesktop.DBus.Properties member=PropertiesChanged
cookie=6127 reply_cookie=0 signature=sa{sv}as error-name=n/a
error-message=n/a
Feb 15 07:41:23 davmail systemd[1]: Sent message type=signal sender=n/a
destination=n/a path=/org/freedesktop/systemd1/unit/tmp_2emount
interface=org.freedesktop.DBus.Properties member=PropertiesChanged
cookie=6128 reply_cookie=0 signature=sa{sv}as error-name=n/a
error-message=n/a
Feb 15 07:41:23 davmail systemd[1]:
run-rd2fa855982314217b00729153ec6dd8b.service: Will spawn child
(service_enter_start): /usr/bin/true
Feb 15 07:41:23 davmail systemd[1]:
run-rd2fa855982314217b00729153ec6dd8b.service: Failed to set
'trusted.invocation_id' xattr on control group
/system.slice/run-rd2fa855982314217b00729153ec6dd8b.service, ignoring:
Operation not permitted
Feb 15 07:41:23 davmail systemd[1]:
run-rd2fa855982314217b00729153ec6dd8b.service: Failed to remove
'trusted.delegate' xattr flag on control group
/system.slice/run-rd2fa855982314217b00729153ec6dd8b.service, ignoring:
Operation not permitted
Feb 15 07:41:23 davmail systemd[1]:
run-rd2fa855982314217b00729153ec6dd8b.service: Passing 0 fds to service
Feb 15 07:41:23 davmail systemd[1]:
run-rd2fa855982314217b00729153ec6dd8b.service: About to execute
/usr/bin/true
Feb 15 07:41:23 davmail systemd[1]:
run-rd2fa855982314217b00729153ec6dd8b.service: Forked /usr/bin/true as 4719
Feb 15 07:41:23 davmail (true)[4719]: PR_SET_MM_ARG_START failed: Operation
not permitted
Feb 15 07:41:23 davmail (true)[4719]:
run-rd2fa855982314217b00729153ec6dd8b.service: Failed to update dynamic
user credentials: Permission denied
Feb 15 07:41:23 davmail (true)[4719]:
run-rd2fa855982314217b00729153ec6dd8b.service: Failed at step USER spawning
/usr/bin/true: Permission denied
░░ Subject: Process /usr/bin/true could not be executed
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░
░░ The process /usr/bin/true could not be executed and failed.
░░
░░ The error number returned by this process is ERRNO.
Feb 15 07:41:23 davmail systemd[1]: Sent message type=signal
sender=org.freedesktop.systemd1 destination=n/a
path=/org/freedesktop/systemd1/unit/run_2drd2fa855982314217b00729153ec6dd8b_2eservice
interface=org.freedesktop.DBus.Properties member=PropertiesChanged
cookie=20 reply_cookie=0 signature=sa{sv}as error-name=n/a error-message=n/a
Feb 15 07:41:23 davmail systemd[1]: Sent message type=signal
sender=org.freedesktop.systemd1 destination=n/a
path=/org/freedesktop/systemd1/unit/run_2drd2fa855982314217b00729153ec6dd8b_2eservice
interface=org.freedesktop.DBus.Properties member=PropertiesChanged
cookie=21 reply_cookie=0 signature=sa{sv}as error-name=n/a error-message=n/a
Feb 15 07:41:23 davmail systemd[1]: Sent message type=signal sender=n/a
destination=n/a
path=/org/freedesktop/systemd1/unit/run_2drd2fa855982314217b00729153ec6dd8b_2eservice
interface=org.freedesktop.DBus.Properties member=PropertiesChanged
cookie=6129 reply_cookie=0 signature=sa{sv}as error-name=n/a
error-message=n/a
Feb 15 07:41:23 davmail systemd[1]: Sent message type=signal sender=n/a
destination=n/a
path=/org/freedesktop/systemd1/unit/run_2drd2fa855982314217b00729153ec6dd8b_2eservice
interface=org.freedesktop.DBus.Properties member=PropertiesChanged
cookie=6130 reply_cookie=0 signature=sa{sv}as error-name=n/a
error-message=n/a

Mark
-- 
Mark Gardner
--

Bug#1063911: davmail-server.service fails in a LXC container

[Mark Gardner]

Package: davmail-server
Version: 6.0.1.3390-7
Severity: wishlist
X-Debbugs-Cc: none, m...@vt.edu

Dear Maintainer,

The issue is repeatable with a fresh install of a Debian 12 LXC container:

$ lxc launch images:debian/12 davmail-bug
$ lxc exec davmail-bug bash

# cat /etc/os-release
PRETTY_NAME="Debian GNU/Linux 12 (bookworm)"
NAME="Debian GNU/Linux"
VERSION_ID="12"
VERSION="12 (bookworm)"
VERSION_CODENAME=bookworm
ID=debian
HOME_URL="https://www.debian.org/;
SUPPORT_URL="https://www.debian.org/support;
BUG_REPORT_URL="https://bugs.debian.org/;

# apt-get install less man zile curl reportbug ca-certificates
openjdk-17-jre-headless davmail-server
# cp -p /etc/davmail/davmail.properties /etc/davmail/davmail.properties.orig
# patch 

Bug#1063656: linux-image-6.1.0-18-amd64: Incomapabile module nvida.ko

[Mark Knutson]

Package: src:linux
Followup-For: Bug #1063656
X-Debbugs-Cc: deb...@mlkenterprises.com

Dear Maintainer,

   * What led up to the situation?
When upgrading from kernel 6.1.0-17-amd64 to 6.1.0-18-amd64 I get the 
error message of incompatible module nivida.ko

   * What exactly did you do (or not do) that was effective (or
 ineffective)?
as root ran "apt update" then "apt upgrade"

   * What was the outcome of this action?
an error message saying the new kernel is partially installed

   * What outcome did you expect instead?
An upgrade as normal

-- Package-specific info:
** Kernel log: boot messages should be attached

** Model information
sys_vendor: LENOVO
product_name: 90GV0004US
product_version: ideacentre 510A-15IKL
chassis_vendor: LENOVO
chassis_version: None
bios_vendor: LENOVO
bios_version: O2TKT34A
board_vendor: LENOVO
board_name: 36C5
board_version: SDK0J40700 WIN 3258084057140

** PCI devices:
00:00.0 Host bridge [0600]: Intel Corporation Xeon E3-1200 v6/7th Gen Core 
Processor Host Bridge/DRAM Registers [8086:591f] (rev 05)
Subsystem: Lenovo Xeon E3-1200 v6/7th Gen Core Processor Host 
Bridge/DRAM Registers [17aa:36c5]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- 
Kernel driver in use: skl_uncore

00:02.0 VGA compatible controller [0300]: Intel Corporation HD Graphics 630 
[8086:5912] (rev 04) (prog-if 00 [VGA controller])
DeviceName:  Onboard IGD
Subsystem: Lenovo HD Graphics 630 [17aa:36c5]
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- 
Kernel driver in use: i915
Kernel modules: i915

00:14.0 USB controller [0c03]: Intel Corporation 200 Series/Z370 Chipset Family 
USB 3.0 xHCI Controller [8086:a2af] (prog-if 30 [XHCI])
Subsystem: Lenovo 200 Series/Z370 Chipset Family USB 3.0 xHCI 
Controller [17aa:36c5]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- 
SERR- 
Kernel driver in use: xhci_hcd
Kernel modules: xhci_pci

00:14.2 Signal processing controller [1180]: Intel Corporation 200 Series PCH 
Thermal Subsystem [8086:a2b1]
Subsystem: Lenovo 200 Series PCH Thermal Subsystem [17aa:36c5]
Control: I/O- Mem+ BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- 

00:16.0 Communication controller [0780]: Intel Corporation 200 Series PCH CSME 
HECI #1 [8086:a2ba]
Subsystem: Lenovo 200 Series PCH CSME HECI [17aa:36c5]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- 
Kernel driver in use: mei_me
Kernel modules: mei_me

00:17.0 SATA controller [0106]: Intel Corporation 200 Series PCH SATA 
controller [AHCI mode] [8086:a282] (prog-if 01 [AHCI 1.0])
Subsystem: Lenovo 200 Series PCH SATA controller [AHCI mode] [17aa:36c5]
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- 
SERR- 
Kernel driver in use: ahci
Kernel modules: ahci

00:1c.0 PCI bridge [0604]: Intel Corporation 200 Series PCH PCI Express Root 
Port #5 [8086:a294] (rev f0) (prog-if 00 [Normal decode])
Subsystem: Lenovo 200 Series PCH PCI Express Root Port [17aa:36c5]
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- Reset- FastB2B-
PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn-
Capabilities: 
Kernel driver in use: pcieport

00:1d.0 PCI bridge [0604]: Intel Corporation 200 Series PCH PCI Express Root 
Port #11 [8086:a29a] (rev f0) (prog-if 00 [Normal decode])
Subsystem: Lenovo 200 Series PCH PCI Express Root Port [17aa:36c5]
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- Reset- FastB2B-
PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn-
Capabilities: 
Kernel driver in use: pcieport

00:1f.0 ISA bridge [0601]: Intel Corporation 200 Series PCH LPC Controller 
(B250) [8086:a2c8]
Subsystem: Lenovo 200 Series PCH LPC Controller (B250) [17aa:36c5]
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- 

Bug#1063474: insserv messages about loops are too obtuse

[Mark Hindley]

Control: tags -1 upstream

Jakob,

Many thanks for this.

Jesse,

What are your thoughts? Is this something you can improve or address upstream?

Thanks

Mark

Bug#1061902: consolekit2: NMU diff for 64-bit time_t transition

[Mark Hindley]

Whilst I am not an expert on this transition or the abi-compliance-checker, a
quick look at the logs[1] suggests this is a tool configuration issue and
src:consolekit2 may not require t64 migration.

Can you clarify?

Thanks

Mark

[1]  
https://adrien.dcln.fr/misc/armhf-time_t/2024-02-03T09:18:00/logs/libconsolekit-dev/time_t/log.txt

Bug#1061902: consolekit2: NMU diff for 64-bit time_t transition

[Mark Hindley]

Michael,

On Tue, Jan 30, 2024 at 01:24:19AM +, mwhud...@debian.org wrote:
> Source: consolekit2
> Version: 1.2.6-3
> Severity: serious
> Tags: patch pending
> Justification: library ABI skew on upgrade
> User: debian-...@lists.debian.org
> Usertags: time-t

This patch appears to be broken and all the experimental builds FTBFS[1].

In addition, the bug severity is triggering autoremoval[2]

That seems a sub-optimal combination. I am minded to reduce the bug
severity. But I will wait for your response if you have a better suggestion.

Thanks

Mark

[1]  
https://buildd.debian.org/status/package.php?p=consolekit2=experimental

[2]  https://udd.debian.org/cgi-bin/autoremovals.cgi

Bug#1061280: sysvinit crashes podman container on install

[Mark Hindley]

Control: tags -1 patch

On Mon, Jan 22, 2024 at 02:37:39PM -0700, Sam Hartman wrote:
> >>>>> "Mark" == Mark Hindley  writes:
> 
> Mark> Can you confirm?
> 
> I agree that should work.
> I have enough confidence and am busy enough today that I don't want to
> build just to apply the patch.

Thanks.

Mark

Bug#1061280: sysvinit crashes podman container on install

[Mark Hindley]

Sam,

Thanks for this.

A quick look at sysvinit-core postinst reveals:

restart=yes

if ischroot --default-true ; then
restart=no
fi
if [ -n "${DPKG_ROOT:-}" ]; then
restart=no
fi

# If systemd is running, don't restart init or doing any initctl
# migration.
if [ -d "$DPKG_ROOT/run/systemd/system" ]; then
restart=no
fi
if [ "$(uname -s)" = "GNU" ]; then
restart=no
fi

if [ "$restart" = "yes" ]; then
do_restart
else
echo "Not restarting sysvinit"
fi

My initial thought is that restart should really be 'no' if it is a new
sysvinit-core installation. The attached patch fixes sysvinit-core installation
within a podman container for me. I need to do more testing to check that it
doesn't cause breakage elsewhere.

Can you confirm?

Thanks

Mark
>From a14a542cf08db3ef53a154d0366e873375662f4a Mon Sep 17 00:00:00 2001
From: Mark Hindley 
Date: Mon, 22 Jan 2024 16:45:11 +
Subject: [PATCH] d/sysvinit-core.postinst: don't do_restart() for new
 installations.

Closes: #1061280
---
 debian/sysvinit-core.postinst | 3 +++
 1 file changed, 3 insertions(+)

diff --git a/debian/sysvinit-core.postinst b/debian/sysvinit-core.postinst
index ecb27a5b..d0ac5841 100755
--- a/debian/sysvinit-core.postinst
+++ b/debian/sysvinit-core.postinst
@@ -112,6 +112,9 @@ fi
 
 restart=yes
 
+if [ -z "${oldver}" ]; then
+restart=no
+fi
 if ischroot --default-true ; then
 	restart=no
 fi
-- 
2.39.2

Bug#1061297: libelogind0: does not implement all ABI required by important packages like procps

[Mark Hindley]

Simon,

Thanks for this.

On Mon, Jan 22, 2024 at 10:47:08AM +, Simon McVittie wrote:
> Package: libelogind0
> Version: 252.9-1debian3
> Severity: important
> Tags: trixie sid
> 
> Steps to reproduce: attempt to install a Debian unstable virtual machine
> (I used amd64) with sysvinit-core, libpam-elogind, dbus-x11, and a small
> X11 system (I used xdm and openbox).
> 
> Expected result: libelogind0 is a drop-in replacement for libsystemd0 in
> this scenario,

This used to be the case, but in sid/trixie to resolve[1] the lag in upstream
elogind releases[2], we now have a patch for elogind which enables it to use
libsystemd0 directly[3].  That means that the expected dependencies are now

 libpam-elogind -> elogind -> libsystemd0

with procps installable and libelogind0 not installed.

So, I am curious why libelogind0 was being installed in your VM. Did you request
it specifically? Bin:libelogind0 is still built by src:elogind and available in
the archive. I hesitated to remove it before being certain that the elogind
cgroups patch to use libsystemd0 was reliable. But maybe libelogind0 should
become a dependency package to smooth upgrades? Or is there another detail in
the dependency chain I have missed?

Mark



[1]  https://bugs.debian.org/1052064

[2]  Upstream has still not released 254

[3]  
https://git.devuan.org/devuan/elogind/src/branch/debian/debian/patches/Use-libsystemd0-compatible-cgroups-layout.patch

Bug#1060768: pdudaemon: Missing dependency on python3-aiohttp

[Mark Brown]

Package: pdudaemon
Version: 0.0.8.58.g597052b-1
Severity: serious

Attempting to use pdudaemon without python3-aiohttp installed results in
a traceback:

# pdudaemon
Traceback (most recent call last):
  File "/usr/sbin/pdudaemon", line 33, in 
sys.exit(load_entry_point('pdudaemon==0.1', 'console_scripts', 
'pdudaemon')())
 ^^
  File "/usr/sbin/pdudaemon", line 25, in importlib_load_entry_point
return next(matches).load()
   
  File "/usr/lib/python3.11/importlib/metadata/__init__.py", line 202, in load
module = import_module(match.group('module'))
 
  File "/usr/lib/python3.11/importlib/__init__.py", line 126, in import_module
return _bootstrap._gcd_import(name[level:], package, level)
   
  File "", line 1206, in _gcd_import
  File "", line 1178, in _find_and_load
  File "", line 1149, in _find_and_load_unlocked
  File "", line 690, in _load_unlocked
  File "", line 940, in exec_module
  File "", line 241, in _call_with_frames_removed
  File "/usr/lib/python3/dist-packages/pdudaemon/__init__.py", line 32, in 

from pdudaemon.httplistener import HTTPListener
  File "/usr/lib/python3/dist-packages/pdudaemon/httplistener.py", line 24, in 

from aiohttp import web
ModuleNotFoundError: No module named 'aiohttp'

but there is no dependency declared in the package.  Installing the
python3-aiohttp resolves this issue.

-- System Information:
Debian Release: 12.1
  APT prefers stable-security
  APT policy: (500, 'stable-security'), (500, 'stable')
Architecture: amd64 (x86_64)
Foreign Architectures: arm64

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

Versions of packages pdudaemon depends on:
ii  python3   3.11.2-1+b1
pn  python3-hid   
pn  python3-paramiko  
ii  python3-pexpect   4.8.0-4
ii  python3-pyasn10.4.8-3
ii  python3-pysnmp4   4.4.12-2
ii  python3-requests  2.28.1+dfsg-1
ii  python3-serial3.5-1.1
pn  python3-systemd   
pn  python3-usb   

Versions of packages pdudaemon recommends:
ii  inetutils-telnet [telnet]  2:2.4-2
ii  openssh-client 1:9.2p1-2

pdudaemon suggests no packages.

Bug#1050547: Info received (Similar stacktrace for this issue.)

[Mark Bryars]

This seems to be the same issue as this one upstream:
https://gitlab.gnome.org/GNOME/mutter/-/issues/2815

The latest debian update made wayland work for me again, and I found the
accessibility zoom feature was somehow active for my greeter session, some
curious kids may have clicked on things. Turning it off and then disabling
wayland has fixed it for me.

I suspect this might be mitigated for other broken users with:
mv
/var/lib/gdm3/greeter-dconf-defaults /var/lib/gdm3/greeter-dconf-defaults.old

On Sat, 25 Nov 2023 at 23:51, Debian Bug Tracking System <
ow...@bugs.debian.org> wrote:

> Thank you for the additional information you have supplied regarding
> this Bug report.
>
> This is an automatically generated reply to let you know your message
> has been received.
>
> Your message is being forwarded to the package maintainers and other
> interested parties for their attention; they will reply in due course.
>
> Your message has been sent to the package maintainer(s):
>  Debian GNOME Maintainers 
>
> If you wish to submit further information on this problem, please
> send it to 1050...@bugs.debian.org.
>
> Please do not send mail to ow...@bugs.debian.org unless you wish
> to report a problem with the Bug-tracking system.
>
> --
> 1050547: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1050547
> Debian Bug Tracking System
> Contact ow...@bugs.debian.org with problems
>

>

Bug#1059163: cpio: Path traversal vulnerability

[Mark Esler]

Please refer to this path traversal vulnerability as CVE-2023-7207.

https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2023-7207

Bug#1059165: [Pkg-javascript-devel] Bug#1059165: src:zlib: fails to migrate to testing for too long: triggers autopkgtest issues

[Mark Brown]

On Wed, Dec 20, 2023 at 10:14:44PM +0100, Jérémy Lal wrote:

> BURP wrong zlib version check in the failing test - this could be NMUed

> DOLFIN has a single test failure, that is odd and unrelated as well - this
> could be NMUed

For non-technical reasons I can't do these NMUs myself if they're
warranted/needed.


signature.asc
Description: PGP signature

Bug#1059165: src:zlib: fails to migrate to testing for too long: triggers autopkgtest issues

[Mark Brown]

clone 1059165 -1
reassign -1 nodejs
retitle -1 autopkgtest failures on i386
found -1 18.19.0+dfsg-6
block 1059165 by -1
kthxbye

On Wed, Dec 20, 2023 at 08:15:31PM +0100, Paul Gevers wrote:

> The Release Team considers packages that are out-of-sync between testing and
> unstable for more than 30 days as having a Release Critical bug in testing
> [1]. Your package src:zlib has been trying to migrate for 32 days [2].
> Hence, I am filing this bug. The version in unstable triggers autopkgtest
> failures in multiple packages (although I suspect that the current dolfin
> issues are due to it being flaky). The failure for burp has already a bug
> report against that package, which leaves nodejs on i386.

...

> This bug will trigger auto-removal when appropriate. As with all new bugs,
> there will be at least 30 days before the package is auto-removed.

Not sure that's likely in the case of zlib?

> If you believe your package is unable to migrate to testing due to issues
> beyond your control, don't hesitate to contact the Release Team.

There are non-technical issues with me doing active work on nodejs
package but from a quick glance the log does not seem particularly
plausibly related to zlib, and I note that the failures are

   not ok 498 parallel/test-debugger-heap-profiler
   not ok 962 parallel/test-fs-utimes-y2K38 # TODO : Fix flaky test 

the second of which especially doesn't inspire confidence that this is
due to zlib rather than general updates to unstable setting off an
already flaky test (eg, the kernel changed timing?).  Full log is:

   https://ci.debian.net/packages/n/nodejs/testing/i386/41176091/

and looking at:

   https://ci.debian.net/packages/n/nodejs/testing/i386/

there seem to be a number of packages triggering what from spot checks
look to be the same or similar issues in nodejs in testing.

I frankly don't really know what I'm supposed to do with this, the test
results look like noise as far as zlib is concerned so I don't see
anything to fix or investigate in the package itself.  AFAICT bugs don't
get filed for autopkgtest failures like they do for build failures so
perhaps this was just missed up until now?


signature.asc
Description: PGP signature

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

[Mark Hindley]

Chris,

Thanks

On Wed, Dec 06, 2023 at 05:57:55PM +0100, Chris Hofstaedtler wrote:
> * Mark Hindley :
> > On Wed, Dec 06, 2023 at 06:06:41PM +0200, Martin-Éric Racine wrote:
> > > 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.
> > 
> > Hmmm, udev is linux only, so I imagine udev rules are cruft on Hurd.
> 
> That would be my understanding as well.
> 
> However on linux, the file should be named 85-hwclock.rules again.
> Maybe this could be fixed too?

Of course, queued and pending.

> For hurd (and maybe linux), the big question remains, _if_ updating
> the hwclock should be done by hwclock.sh by default.
> I don't know the answer to this design question for hurd, or for
> linux-with-sysvinit systems.

I don't have a definitive answer either, but either way the script should not
fail on Hurd and by downgrading the Depends to Recommends it is easy to change
the behaviour if it is not to your liking.

Mark

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

[Mark Hindley]

Martin,

On Wed, Dec 06, 2023 at 06:06:41PM +0200, Martin-Éric Racine wrote:
> 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.

Hmmm, udev is linux only, so I imagine udev rules are cruft on Hurd.

> 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

Thanks. Looks OK to me.

Mark

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

[Mark Hindley]

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}"

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

[Mark Hindley]

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?

Mark

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

[Mark Hindley]

Control: tags -1 moreinfo

Martin,

Thanks for this

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.

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

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

Mark

[1]  
https://salsa.debian.org/debian/util-linux/-/blob/master/debian/util-linux-extra.install

Bug#1057419: consolekit2 FTCBFS: configures twice - once for the build architecture and fails

[Mark Hindley]

Control: tags -1 pending

Helmut,

Many thanks for spotting this.

Queued for next upload.

Mark

Bug#1055645: orphan-sysvinit-scripts: Please take over mdadm init script

[Mark Hindley]

On Sat, Dec 02, 2023 at 01:02:48AM +0100, Lorenzo wrote:
> > 
> > The cronjob that will be removed soon is still a problem as it checks
> > the arrays periodically
> 
> I'm not saying that it's not a problem, but I think it's a separate bug.
> Also, before doing any attempts on this, Matthew has to say if he's ok
> with maintaining cronjobs in this package and if yes, how this should
> be done.

I think he has already said he isn't happy with that.

I have already submitted a bug with patch to reinstate the cron jobs[1]
alongside the systemd timers.

Mark

[1]  https://bugs.debian.org/1055994

Bug#1057122: initscripts has an undeclared file conflict on /usr/lib/udev/hwclock-set

[Mark Hindley]

Helmut,

Thanks for this

On Tue, Nov 28, 2023 at 10:27:41AM +0100, Helmut Grohne wrote:
> Package: initscripts
> Version: 3.08-3~bpo12+1
> Severity: serious
> User: debian...@lists.debian.org
> Usertags: fileconflict
> Control: affects -1 + util-linux
> Tags: bookworm
> 
> initscripts has an undeclared file conflict. This may result in an
> unpack error from dpkg.
> 
> The file /usr/lib/udev/hwclock-set is contained in the packages
>  * initscripts/3.08-3~bpo12+1 as present in bookworm-backports
>  * util-linux/2.36.1-8+deb11u1 as present in bullseye|bullseye-security

Are the suites and versions reported here really the problematic ones?

I agree there is a conflict, but I think it is between
initscripts/3.08-3~bpo12+1 in bookworm-backports and util-linux-extra/2.38.1-5
in bookworm.

My proposed fix is attached. It reverts the transition of the hwclock machinery
to initscripts, since this is still present in bookworm src:util-linux.

Or, have I misunderstood?

Best wishes,

Mark

diff --git a/debian/control b/debian/control
index 551b7abc..02bfe1b5 100644
--- a/debian/control
+++ b/debian/control
@@ -99,15 +99,12 @@ Multi-Arch: foreign
 Depends:
  sysvinit-utils (>= 3.05-1),
  sysv-rc | file-rc | openrc,
- util-linux-extra,
  ${misc:Depends},
 Recommends:
  e2fsprogs,
  psmisc,
 Breaks: udev (<<  254.3-1),
-   util-linux-extra (<< 2.39.2-2.1~)
 Replaces: udev (<<  254.3-1),
- util-linux-extra (<< 2.39.2-2.1~)
 Description: scripts for initializing and shutting down the system
  The scripts in this package initialize a standard Debian
  system at boot time and shut it down at halt or reboot time.
diff --git a/debian/initscripts.postinst b/debian/initscripts.postinst
index 0074f2a3..eb126710 100755
--- a/debian/initscripts.postinst
+++ b/debian/initscripts.postinst
@@ -42,7 +42,7 @@ INITSCRIPTS="mountkernfs.sh mount-configfs brightness 
hostname.sh mountdevsubfs.
checkroot-bootclean.sh checkfs.sh mountall.sh mountall-bootclean.sh \
mountnfs.sh mountnfs-bootclean.sh bootmisc.sh urandom halt reboot \
udev umountroot umountfs umountnfs.sh sendsigs killprocs single motd \
-   bootlogs rc.local rmnologin hwclock.sh"
+   bootlogs rc.local rmnologin"
 
 for F in $INITSCRIPTS; do
if [ -x /etc/init.d/$F ]; then
diff --git a/debian/initscripts.postrm b/debian/initscripts.postrm
index 25bbb932..e53672dc 100755
--- a/debian/initscripts.postrm
+++ b/debian/initscripts.postrm
@@ -9,7 +9,7 @@ INITSCRIPTS="mountkernfs.sh mount-configfs brightness 
hostname.sh mountdevsubfs.
checkroot-bootclean.sh checkfs.sh mountall.sh mountall-bootclean.sh \
mountnfs.sh mountnfs-bootclean.sh bootmisc.sh urandom halt reboot \
udev umountroot umountfs umountnfs.sh sendsigs killprocs single motd \
-   bootlogs rc.local rmnologin hwclock.sh"
+   bootlogs rc.local rmnologin"
 
 case "$1" in
   purge)
diff --git a/debian/src/initscripts/Makefile b/debian/src/initscripts/Makefile
index 5da80089..b13eafa3 100644
--- a/debian/src/initscripts/Makefile
+++ b/debian/src/initscripts/Makefile
@@ -34,9 +34,6 @@ install:
$(INSTALL) -d $(DESTDIR)$(sbindir)/.
$(INSTALL) sbin/fsck.nfs $(DESTDIR)$(sbindir)/fsck.nfs
 
-   $(INSTALL_DATA) -Dt $(DESTDIR)/usr/lib/udev/rules.d 
usr/lib/udev/rules.d/hwclock.rules
-   $(INSTALL) usr/lib/udev/hwclock-set $(DESTDIR)/usr/lib/udev/hwclock-set
-
$(INSTALL) -d $(DESTDIR)/usr/share/man/man8
$(INSTALL_DATA) man/fsck.nfs.8 \
$(DESTDIR)/usr/share/man/man8/fsck.nfs.8
diff --git a/debian/src/initscripts/etc/default/hwclock 
b/debian/src/initscripts/etc/default/hwclock
deleted file mode 100644
index 44b04312..
--- a/debian/src/initscripts/etc/default/hwclock
+++ /dev/null
@@ -1,2 +0,0 @@
-# Settings for the hwclock init script.
-# See hwclock(5) for supported settings.
diff --git a/debian/src/initscripts/etc/init.d/hwclock.sh 
b/debian/src/initscripts/etc/init.d/hwclock.sh
deleted file mode 100644
index a9872b64..
--- a/debian/src/initscripts/etc/init.d/hwclock.sh
+++ /dev/null
@@ -1,57 +0,0 @@
-#!/bin/sh
-
-### BEGIN INIT INFO
-# Provides:  hwclock
-# Required-Start:
-# Required-Stop: mountdevsubfs
-# Should-Stop:   umountfs
-# Default-Start: S
-# Default-Stop:  0 6
-# Short-Description: Save system clock to hardware on shutdown.
-### END INIT INFO
-
-# Note: this init script and related code is only useful if you
-# run a sysvinit system, without NTP synchronization.
-
-if [ -e /run/systemd/system ] ; then
-exit 0
-fi
-
-unset TZ
-
-hwclocksh()
-{
-HCTOSYS_DEVICE=rtc0
-[ ! -x /sbin/hwclock ] && return 0
-[ ! -r /etc/default/rcS ] || . /etc/default/rcS
-[ ! -r /etc/default/hwclock ] || . /etc/default/hwclock
-
-. /lib/lsb/init-functions
-verbose_log_action_msg() { [ "$VERBOSE" = no ] || log_a

Bug#1050547: Similar stacktrace for this issue.

[Mark Bryars]

I've not been able to start gdm3 for quite a while now.

I've tried upgrading to the latest nvidia driver in experimental
(535.43.02-1) ,
and WaylandEnable=false in /etc/gdm3/daemon.conf

Swapping to the nouveau driver didn't seem to fix it, but then I removed
the WaylandEnable=false and it started to work. I sadly have reasons to use
the Nvidia drivers.


systemd-coredump[101602]: Process 101572 (gnome-shell) of user 112 dumped
core.

Module libzstd.so.1
from deb libzstd-1.5.5+dfsg2-2.amd64
Module libudev.so.1
from deb systemd-255~rc3-2.amd64
Module libsystemd.so.0
from deb systemd-255~rc3-2.amd64
Stack trace of thread
101572:
#0  0x7fa966eced34
meta_display_get_x11_display (libmutter-12.so.0 + 0xced34)
#1  0x7fa966ef9aeb
meta_cursor_sprite_xfixes_initable_init (libmutter-12.so.0 + 0xf9aeb)
#2  0x7fa9674923f3
g_initable_new_valist (libgio-2.0.so.0 + 0x7f3f3)
#3  0x7fa9674924dd
g_initable_new (libgio-2.0.so.0 + 0x7f4dd)
#4  0x7fa966ef9e8a
meta_cursor_sprite_xfixes_new (libmutter-12.so.0 + 0xf9e8a)
#5  0x7fa966efd69e
ensure_xfixes_cursor (libmutter-12.so.0 + 0xfd69e)
#6  0x7fa966efd6fd
meta_cursor_tracker_x11_get_sprite (libmutter-12.so.0 + 0xfd6fd)
#7  0x7fa966e8b05e
meta_cursor_tracker_get_sprite (libmutter-12.so.0 + 0x8b05e)
#8  0x7fa96706640e
ffi_call_unix64 (libffi.so.8 + 0x740e)
#9  0x7fa96706571d
ffi_call_int (libffi.so.8 + 0x671d)
#10 0x7fa967065ef3
ffi_call (libffi.so.8 + 0x6ef3)
#11 0x7fa9671d46c7
_ZN3Gjs8Function6invokeEP9JSContextRKN2JS8CallArgsENS3_6HandleIP8JSObjectEEP11_GIArgument
(libgjs.so.0 + 0x4c6c7)
#12 0x7fa9671d4f87
_ZN3Gjs8Function4callEP9JSContextjPN2JS5ValueE (libgjs.so.0 + 0x4cf87)
#13 0x7fa96437eb0e
_Z12CallJSNativeP9JSContextPFbS0_jPN2JS5ValueEEN2js10CallReasonERKNS1_8CallArgsE
(libmozjs-115.so.0 + 0x17eb0e)
#14 0x7fa964370860
InternalCall (libmozjs-115.so.0 + 0x170860)
#15 0x7fa96437e843
MaybeEnterInterpreterTrampoline (libmozjs-115.so.0 + 0x17e843)
#16 0x7fa964380c81
_ZN2js13ExecuteKernelEP9JSContextN2JS6HandleIP8JSScriptEENS3_IP8JSObjectEENS_16AbstractFramePtrENS2_13MutableHand
leINS2_5ValueEEE (libmozjs-115.so.0 + 0x180c81)
#17 0x7fa9643e013d
_ZN2js12ModuleObject7executeEP9JSContextN2JS6HandleIPS0_EE
(libmozjs-115.so.0 + 0x1e013d)
#18 0x7fa9644c1deb
InnerModuleEvaluation (libmozjs-115.so.0 + 0x2c1deb)
#19 0x7fa9644c21a3
_ZN2js14ModuleEvaluateEP9JSContextN2JS6HandleIPNS_12ModuleObjectEEENS2_13MutableHandleINS2_5ValueEEE
(libmozjs-11
5.so.0 + 0x2c21a3)
#20 0x7fa96720ae08
_ZN17GjsContextPrivate11eval_moduleEPKcPhPP7_GError (libgjs.so.0 + 0x82e08)
#21 0x7fa96720b2e2
gjs_context_eval_module (libgjs.so.0 + 0x832e2)
#22 0x7fa96720b401
gjs_context_eval_module_file (libgjs.so.0 + 0x83401)
#23 0x7fa96761f7c9
n/a (libshell-12.so + 0x1f7c9)
#24 0x7fa966eaf048
meta_compositor_do_manage (libmutter-12.so.0 + 0xaf048)
#25 0x7fa966ece606
meta_display_new (libmutter-12.so.0 + 0xce606)
#26 0x7fa966ed9f60
meta_context_start (libmutter-12.so.0 + 0xd9f60)
#27 0x55ed5de2298e
n/a (gnome-shell + 0x398e)
#28 0x7fa966c456ca
__libc_start_call_main (libc.so.6 + 0x276ca)
#29 0x7fa966c45785
__libc_start_main_impl (libc.so.6 + 0x27785)

Bug#1056363: initscripts: Backport 3.08 to stable (bookworm) for udev init script

[Mark Hindley]

Control: tags -1 pending

On Wed, Nov 22, 2023 at 02:08:58AM +0800, Chen-Yu Tsai wrote:
> Package: initscripts
> Version: 3.08-3
> Severity: important
> 
> Dear Maintainer,
> 
> initscripts 3.08 needs to be backported to bookworm, as the systemd version
> that removed the udev init script and forced initscripts to take over it was
> already backported.

I have uploaded src:sysvinit 3.08-3~bpo12+1. It is waiting in backports-new[1]

Mark

[1]  https://ftp-master.debian.org/new/sysvinit_3.08-3~bpo12%2B1.html

Bug#1056321: elogind conflicts with same version libelogind0

[Mark Hindley]

Hi Thorsten,

On Tue, Nov 21, 2023 at 12:58:40AM +0100, Thorsten Glaser wrote:
> Did you forget to not build the libelogind0 binary package any more
> then?

It was a conscious decision on my part to keep it for now. I see 2 benefits:-

 1. If we need to revert this approach, it will save a trip through NEW

 2. I suppose somebody may have a use for libelogind0 or libelogind-dev, and I
didn't want to remove that option.

Is that reasonable?

Thanks and best wishes

Mark

Bug#1056176: insserv: please support DPKG_ROOT

[Mark Hindley]

Control: tags -1 pending

Thanks.

Queued for the next upload.

Mark

Bug#1056049: consolekit2: Not buildable on hurd-i386

[Mark Hindley]

Control: tags -1 pending

Svante,

Many thanks for this. Queued for upload.

Best wishes

Mark

Bug#1055994: mdadm: Please restore cron scripts for use when systemd timers are not available

[Mark Hindley]

Package: mdadm
Version: 4.2+20230508-7
Severity: normal
Tags: patch

Dear Daniel,

As was discussed in #1037496, the removal of cron scripts from mdadm means that
no mdamd housekeeping is performed when systemd timers are not available.

I attach a patch which restores the cron scripts in mdadm, but protects them
with a test for running systemd. This should mean that housekeeping tasks are
performed an all systems, but that there is no duplication when systemd timers
are available.

I hope this is an acceptable compromise and I look forward to your comments.

With best wishes

Mark
>From 1f4b2370e6ffaab0b6352b893f268e0fa39df55b Mon Sep 17 00:00:00 2001
From: Mark Hindley 
Date: Tue, 14 Nov 2023 19:52:52 +
Subject: [PATCH] Restore cron fragments, but prefer systemd timers.

---
 debian/mdadm.cron.d  | 12 
 debian/mdadm.cron.daily  | 23 +++
 debian/mdadm.maintscript |  2 --
 debian/mdadm.postinst|  3 ++-
 4 files changed, 37 insertions(+), 3 deletions(-)
 create mode 100644 debian/mdadm.cron.d
 create mode 100644 debian/mdadm.cron.daily

diff --git a/debian/mdadm.cron.d b/debian/mdadm.cron.d
new file mode 100644
index 000..63f186d
--- /dev/null
+++ b/debian/mdadm.cron.d
@@ -0,0 +1,12 @@
+#
+# cron.d/mdadm -- schedules periodic redundancy checks of MD devices
+#
+# Copyright © martin f. krafft 
+# distributed under the terms of the Artistic Licence 2.0
+#
+
+# By default, run at 00:57 on every Sunday, but do nothing unless the day of
+# the month is less than or equal to 7. Thus, only run on the first Sunday of
+# each month. crontab(5) sucks, unfortunately, in this regard; therefore this
+# hack (see #380425).
+57 0 * * 0 root if [ -x /usr/share/mdadm/checkarray ] && [ ! -d /run/systemd/system ] && [ $(date +\%d) -le 7 ]; then /usr/share/mdadm/checkarray --cron --all --idle --quiet; fi
diff --git a/debian/mdadm.cron.daily b/debian/mdadm.cron.daily
new file mode 100644
index 000..8d1bfeb
--- /dev/null
+++ b/debian/mdadm.cron.daily
@@ -0,0 +1,23 @@
+#!/bin/sh
+#
+# cron.daily/mdadm -- daily check that MD devices are functional
+#
+# Copyright © 2008 Paul Slootman 
+# distributed under the terms of the Artistic Licence 2.0
+
+# As recommended by the manpage, run
+#  mdadm --monitor --scan --oneshot
+# every day to ensure that any degraded MD devices don't go unnoticed.
+# Email will go to the address specified in /etc/mdadm/mdadm.conf .
+#
+set -eu
+
+MDADM=/sbin/mdadm
+[ -x $MDADM ] || exit 0 # package may be removed but not purged
+
+[ -d /run/systemd/system ] || exit 0 # Defer to systemd timers if possible
+
+[ -e /etc/default/mdadm ] && . /etc/default/mdadm
+[ $AUTOSCAN = false ] && exit 0
+
+exec $MDADM --monitor --scan --oneshot
diff --git a/debian/mdadm.maintscript b/debian/mdadm.maintscript
index 17b5e28..1298978 100644
--- a/debian/mdadm.maintscript
+++ b/debian/mdadm.maintscript
@@ -1,4 +1,2 @@
-rm_conffile /etc/cron.d/mdadm 4.2+20230227-1~
-rm_conffile /etc/cron.daily/mdadm 4.2+20230227-1~
 rm_conffile /etc/init.d/mdadm 4.2+20230227-1~
 rm_conffile /etc/init.d/mdadm-waitidle 4.2+20230227-1~
diff --git a/debian/mdadm.postinst b/debian/mdadm.postinst
index c8a3420..021912a 100755
--- a/debian/mdadm.postinst
+++ b/debian/mdadm.postinst
@@ -76,7 +76,8 @@ AUTOCHECK=$AUTOCHECK
 
 # AUTOSCAN:
 #   should mdadm check once a day for degraded arrays? See
-#   /lib/systemd/system/mdmonitor-oneshot.service
+#   /lib/systemd/system/mdmonitor-oneshot.service and
+#   /etc/cron.daily/mdadm.
 AUTOSCAN=$AUTOSCAN
 
 # START_DAEMON:
-- 
2.39.2

Bug#1055938: zlib1g: move libz.so.* to /usr

[Mark Brown]

On Tue, Nov 14, 2023 at 03:33:00PM +0100, Helmut Grohne wrote:

> > debootstrap is already broken by the /usr merge, which is something of
> > an annoyance for anyone who uses pbuilder to actually build packages...

> I suspect you are using a bulleye or bookworm system with pbuilder to
> build for unstable. Please update your debootstrap package from the
> relevant -updates suite and it'll work again. The debootstrap update
> will be part of the next point release. I'm sorry for the inconvenience,
> but the ordering has been beyond my control.

I already managed to bodge it in the end, but trying to work around the
unannounced breakage did burn all the time I'd allocated to spend on
package updates last week.


signature.asc
Description: PGP signature

Bug#1055938: zlib1g: move libz.so.* to /usr

[Mark Brown]

On Tue, Nov 14, 2023 at 11:45:35AM +0100, Helmut Grohne wrote:

> fortunately. We do not break the debian-installer (P10), because even
> unmerged chroots have /usr/lib/ on their library search
> paths. I locally verified that we do not break debootstrap (P8) and
> since the affected filename is architecture-dependent, the multi-arch
> file loss scenario (P7) also does not apply.

debootstrap is already broken by the /usr merge, which is something of
an annoyance for anyone who uses pbuilder to actually build packages...


signature.asc
Description: PGP signature

Bug#810018: Bug #810018: Consider shipping pidof with procps

[Mark Hindley]

Craig,

Thanks for this.

On Mon, Nov 13, 2023 at 08:08:37PM +1100, Craig Small wrote:
>  I'll need the assistance of the sysvinit-utils maintainers (CC'ed) as
>well, as pidof will be moving from that package.

IIUC, the proposal[1] was to create a new Essential procps-base just containing
pidof. Otherwise bin:procps would have to become Essential itself. Its installed
size is about 20 times larger than sysvinit-util and that wouldn't contribute to
shrinking the Essential set.

I think this approach would also require a debian-devel email announcing the
addition to the Essential set and I suppose the new src:procps will need a trip
through NEW.

>So I'm looking at https://wiki.debian.org/PackageTransition
>and assuming procps is 2:4.0.4-2 and sysvinit-utils is 3.08-3
>I would create procps 2:4.0.4-3 with pidof and Breaks: sysvinit-utils
>(<< 3.0.8-4) and Replaces: sysvinit-utils (<< 3.0.8-4)
>sysvinit-utils maintainers create 3.08-4 without pidof and have Breaks:
>procps (<< 2:4.0.4-3)

The dependencies would then be:-

procps-base:
 Breaks: sysvinit-utils (<< 3.0.8-4)
 Replaces: sysvinit-utils (<< 3.0.8-4)

sysvinit-utils without pidof:
 Breaks: procps-base (<< 2:4.0.4-3)

I hope I have understood the previous discussions correctly . I am not trying to
stand in the way at all, just ensure that this transition is worthwhile and done
correctly.

With best wishes

Mark

[1]  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=810018#10

Bug#1055484: libpam-elogind-compat has ineffective replaces for libpam-systemd due to /usr-merge

[Mark Hindley]

Control: block -1  1055562

Helmut,

On Tue, Nov 07, 2023 at 08:39:23AM +, Mark Hindley wrote:
> I think all suitable dependencies now use default-logind | logind. I will
> check that is correct. If it is, libpam-elogind-compat could just be
> removed. It was never available outside experimental.

AFAICS, all supported cases now use Depends: default-logind | logind or have
demoted the Depends to Recommends.

I have filed a RM request[1].

Mark

[1]  https://bugs.debian.org/1055562

Bug#1055562: RM: libpam-elogind-compat/experimental -- ROM; Not required anymore.

[Mark Hindley]

Package: ftp.debian.org
Severity: normal
User: ftp.debian@packages.debian.org
Usertags: remove

Hello,

Please remove src:libpam-elogind-compat from experimental. It has served its
purpose and is no longer required now the virtual packages default-logind and
logind are used in all Depends.

Thanks

Mark

Bug#1055484: libpam-elogind-compat has ineffective replaces for libpam-systemd due to /usr-merge

[Mark Hindley]

Helmut,

Thanks for this.

libpam-elogind-compat was used when elogind was first introduced as a 
hack to circumvent missing dependencies and allow testing. I think all 
suitable dependencies now use default-logind | logind. I will check that 
is correct. If it is, libpam-elogind-compat could just be removed. It 
was never available outside experimental.

Mark

Bug#1052942: insserv: FTBFS: insserv: Could not read script nolsbheader: No such file or directory

[Mark Hindley]

Control: tags -1 upstream
Control: retitle -1 Upstream testsuite fails to produce deterministic results

Santiago,

On Sun, Oct 29, 2023 at 02:39:44PM +0100, Santiago Vila wrote:
> However, I can create a machine for you to reproduce the problem.

Thanks. I have reproduced on your provided machine, but still not locally and I
can't identify the underlying difference between the builds.

In the failure case the problem is in the upstream testsuite, specifically the
test for #491391 in tests/run-testsuite which produces

init.d:
bootchart
four
one
rmnologin
three
two

insserv:
override

rc0.d:

rc1.d:

rc2.d:
S01one
S01three
S01two
S02four
S98rmnologin
S99bootchart

rc3.d:
S01one
S01three
S01two
S02four
S98rmnologin
S99bootchart

rc4.d:
S01one
S01three
S01two
S02four
S98rmnologin
S99bootchart

rc5.d:
S01one
S01three
S01two
S02four
S98rmnologin
S99bootchart

rc6.d:

rcS.d:
error: incorrect 5 sequence bootchart not before rmnologin

The same failure mode appears to be responsible for armel and armhf autopkgtest
failures logged on ci.debian.net[1]

As Ian pointed out[2], there are significant and surprising changes in looping
order and behaviour between the successful and failing testsuites. The diff is 
attached.

Having said that, I still can't reproduce locally or determine a good fix.
Hopefully Jesse will have a useful contribution

Mark

[1]  
https://ci.debian.net/data/autopkgtest/unstable/armel/i/insserv/38435862/log.gz

[2]  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1052942#15

diff -u --label /sshx\:atlas\:/tmp/build.log --label /home/mark/src/debian/insserv/build.log /tmp/tramp.mDUEXG.log /home/mark/src/debian/insserv/build.log
--- /sshx:atlas:/tmp/build.log
+++ /home/mark/src/debian/insserv/build.log
@@ -4,8 +4,15 @@
 dpkg-buildpackage: info: source changed by Mark Hindley 
  dpkg-source --before-build .
 dpkg-buildpackage: info: host architecture amd64
- fakeroot debian/rules clean
-echo -g -O2 -ffile-prefix-map=/home/mark/insserv-1.24.0=. -fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection
+dpkg-source: info: using patch list from debian/patches/series
+dpkg-source: info: applying install-binaries-ignore-PREFIX.patch
+dpkg-source: info: applying 11_debian_conf.patch
+dpkg-source: info: applying 110_portmap.patch
+dpkg-source: info: applying warn_in_ignore_mode.patch
+dpkg-source: info: applying 0004-Fix-spurious-warnings-about-unknown-virtual-dependen.patch
+dpkg-source: info: applying 0005-Fix-spelling-error-in-manpage.patch
+ debian/rules clean
+echo -g -O2 -ffile-prefix-map=/home/mark/insserv-1.24.0=. -fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection 
 -g -O2 -ffile-prefix-map=/home/mark/insserv-1.24.0=. -fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection
 dh clean --with=bash-completion
dh_auto_clean
@@ -18,7 +25,7 @@
 make[1]: Leaving directory '/home/mark/insserv-1.24.0'
dh_clean
  debian/rules build
-echo -g -O2 -ffile-prefix-map=/home/mark/insserv-1.24.0=. -fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection
+echo -g -O2 -ffile-prefix-map=/home/mark/insserv-1.24.0=. -fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection 
 -g -O2 -ffile-prefix-map=/home/mark/insserv-1.24.0=. -fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection
 dh build --with=bash-completion
dh_update_autotools_config
@@ -31,14 +31,14 @@
 cc -W -Wall -Wunreachable-code -g -O2 -ffile-prefix-map=/home/mark/insserv-1.24.0=. -fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -Wdate-time -D_FORTIFY_SOURCE=2   -D_GNU_SOURCE -D_FILE_OFFSET_BITS=64  -DINITDIR=\"/etc/init.d\" -DINSCONF=\"/etc/insserv.conf\" -pipe   -c map.c
 cc -W -Wall -Wunreachable-code -g -O2 -ffile-prefix-map=/home/mark/insserv-1.24.0=. -fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -Wdate-time -D_FORTIFY_SOURCE=2   -D_GNU_SOURCE -D_FILE_OFFSET_BITS=64  -DINITDIR=\"/etc/init.d\" -DINSCONF=\"/etc/insserv.conf\" -pipe   -c listing.c
 cc -W -Wall -Wunreachable-code -g -O2 -ffile-prefix-map=/home/mark/insserv-1.24.0=. -fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -Wdate-time -D_FORTIFY_SOURCE=2   -D_GNU_SOURCE -D_FILE_OFFSET_BITS=64  -DINITDIR=\"/etc/init.d\" -DINSCONF=\"/etc/insserv.conf\" -pipe   insserv.c -c 
-insserv.c: In function ‘main’:
-insserv.c:2923:20: warning: ignoring return value of ‘asprintf’ declared with attribute ‘warn_unused_result’ [-Wunused-result]
+insserv.c: In function 'main':
+insserv.c:2923:20: warning: ignoring return value of 'asprintf' declared with attribute 'warn_unused_result' [-Wunused-res

Bug#1052942: insserv: FTBFS: insserv: Could not read script nolsbheader: No such file or directory

[Mark Hindley]

Lucas,

I am afraid I still cannot reproduce this.

I attach my successful .buildinfo. What are the differences to yours?

Thanks

Mark
Format: 1.0
Source: insserv
Binary: insserv insserv-dbgsym
Architecture: amd64
Version: 1.24.0-1
Checksums-Md5:
 3c928ff0990c2942950fa368b3978086 79480 insserv-dbgsym_1.24.0-1_amd64.deb
 9bffd1e3395d57a5979030bc472dc80c 50572 insserv_1.24.0-1_amd64.deb
Checksums-Sha1:
 aa26018adc027c1af58704991d3339c1a43dccf2 79480 
insserv-dbgsym_1.24.0-1_amd64.deb
 1d1a7b8f6e5b5ea864a7661f34e767b9a93e4b77 50572 insserv_1.24.0-1_amd64.deb
Checksums-Sha256:
 39912ad2e18538a91ae397467a6cd96519dd948fee2ed90b39c40b4477352bc1 79480 
insserv-dbgsym_1.24.0-1_amd64.deb
 e4e58a1a6a3cb6a68e205341606b1702ef10dd5bd6d43af03e123b536b4cc8f8 50572 
insserv_1.24.0-1_amd64.deb
Build-Origin: Debian
Build-Architecture: amd64
Build-Date: Sun, 29 Oct 2023 13:16:40 +
Build-Path: /build/insserv-1.24.0
Build-Tainted-By:
 merged-usr-via-aliased-dirs
Installed-Build-Depends:
 autoconf (= 2.71-3),
 automake (= 1:1.16.5-1.3),
 autopoint (= 0.21-12),
 autotools-dev (= 20220109.1),
 base-files (= 13),
 base-passwd (= 3.6.1),
 bash (= 5.2.15-2+b2),
 bash-completion (= 1:2.11-8),
 binutils (= 2.40.50.20230625-1),
 binutils-common (= 2.40.50.20230625-1),
 binutils-x86-64-linux-gnu (= 2.40.50.20230625-1),
 bsdextrautils (= 2.38.1-5+b1),
 bsdutils (= 1:2.38.1-5+b1),
 build-essential (= 12.10),
 bzip2 (= 1.0.8-5+b1),
 coreutils (= 9.1-1),
 cpp (= 4:12.3.0-1),
 cpp-10 (= 10.4.0-9),
 cpp-11 (= 11.4.0-1),
 cpp-12 (= 12.3.0-5),
 cpp-6 (= 6.5.0-2),
 cpp-8 (= 8.4.0-4),
 cpp-9 (= 9.5.0-3),
 dash (= 0.5.12-6),
 debconf (= 1.5.82),
 debhelper (= 13.11.4),
 debianutils (= 5.7-0.4),
 dh-autoreconf (= 20),
 dh-strip-nondeterminism (= 1.13.1-1),
 diffutils (= 1:3.8-4),
 dpkg (= 1.21.22),
 dpkg-dev (= 1.21.22),
 dwz (= 0.15-1),
 file (= 1:5.44-3),
 findutils (= 4.9.0-4),
 g++ (= 4:12.3.0-1),
 g++-12 (= 12.3.0-5),
 gcc (= 4:12.3.0-1),
 gcc-10 (= 10.4.0-9),
 gcc-10-base (= 10.4.0-9),
 gcc-11 (= 11.4.0-1),
 gcc-11-base (= 11.4.0-1),
 gcc-12 (= 12.3.0-5),
 gcc-12-base (= 12.3.0-5),
 gcc-13-base (= 13.1.0-7),
 gcc-6 (= 6.5.0-2),
 gcc-6-base (= 6.5.0-2),
 gcc-7-base (= 7.4.0-14),
 gcc-8 (= 8.4.0-4),
 gcc-8-base (= 8.4.0-4),
 gcc-9 (= 9.5.0-3),
 gcc-9-base (= 9.5.0-3),
 gettext (= 0.21-12),
 gettext-base (= 0.21-12),
 grep (= 3.8-5),
 groff-base (= 1.22.4-10),
 gzip (= 1.12-1),
 hostname (= 3.23+nmu1),
 init-system-helpers (= 1.65.2),
 intltool-debian (= 0.35.0+20060710.6),
 libacl1 (= 2.3.1-3),
 libarchive-zip-perl (= 1.68-1),
 libasan3 (= 6.5.0-2),
 libasan5 (= 9.5.0-3),
 libasan6 (= 11.4.0-1),
 libasan8 (= 13.1.0-7),
 libatomic1 (= 13.1.0-7),
 libattr1 (= 1:2.5.1-4),
 libaudit-common (= 1:3.0.9-1),
 libaudit1 (= 1:3.0.9-1),
 libbinutils (= 2.40.50.20230625-1),
 libblkid1 (= 2.38.1-5+b1),
 libbz2-1.0 (= 1.0.8-5+b1),
 libc-bin (= 2.36-9),
 libc-dev-bin (= 2.36-9),
 libc6 (= 2.36-9),
 libc6-dev (= 2.36-9),
 libcap-ng0 (= 0.8.3-1+b3),
 libcap2 (= 1:2.66-4),
 libcc1-0 (= 13.1.0-7),
 libcilkrts5 (= 7.4.0-14),
 libcom-err2 (= 1.47.0-2),
 libcrypt-dev (= 1:4.4.35-1),
 libcrypt1 (= 1:4.4.35-1),
 libctf-nobfd0 (= 2.40.50.20230625-1),
 libctf0 (= 2.40.50.20230625-1),
 libdb5.3 (= 5.3.28+dfsg2-1),
 libdebconfclient0 (= 0.270),
 libdebhelper-perl (= 13.11.4),
 libdpkg-perl (= 1.21.22),
 libelf1 (= 0.188-2.1),
 libfile-find-rule-perl (= 0.34-3),
 libfile-stripnondeterminism-perl (= 1.13.1-1),
 libgcc-10-dev (= 10.4.0-9),
 libgcc-11-dev (= 11.4.0-1),
 libgcc-12-dev (= 12.3.0-5),
 libgcc-6-dev (= 6.5.0-2),
 libgcc-8-dev (= 8.4.0-4),
 libgcc-9-dev (= 9.5.0-3),
 libgcc-s1 (= 13.1.0-7),
 libgcrypt20 (= 1.10.2-2),
 libgdbm-compat4 (= 1.23-3),
 libgdbm6 (= 1.23-3),
 libgmp10 (= 2:6.2.1+dfsg1-1.1),
 libgomp1 (= 13.1.0-7),
 libgpg-error0 (= 1.46-1),
 libgprofng0 (= 2.40.50.20230625-1),
 libgssapi-krb5-2 (= 1.20.1-2),
 libicu72 (= 72.1-3),
 libisl19 (= 0.20-2),
 libisl22 (= 0.22.1-1),
 libisl23 (= 0.26-3),
 libitm1 (= 13.1.0-7),
 libjansson4 (= 2.14-2),
 libk5crypto3 (= 1.20.1-2),
 libkeyutils1 (= 1.6.3-2),
 libkrb5-3 (= 1.20.1-2),
 libkrb5support0 (= 1.20.1-2),
 liblsan0 (= 13.1.0-7),
 liblz4-1 (= 1.9.4-1),
 liblzma5 (= 5.4.1-0.2),
 libmagic-mgc (= 1:5.44-3),
 libmagic1 (= 1:5.44-3),
 libmd0 (= 1.1.0-1),
 libmount1 (= 2.38.1-5+b1),
 libmpc3 (= 1.3.1-1),
 libmpfr6 (= 4.2.0-1),
 libmpx2 (= 8.4.0-4),
 libnsl-dev (= 1.3.0-2),
 libnsl2 (= 1.3.0-2),
 libnumber-compare-perl (= 0.03-3),
 libpam-modules (= 1.5.2-6),
 libpam-modules-bin (= 1.5.2-6),
 libpam-runtime (= 1.5.2-6),
 libpam0g (= 1.5.2-6),
 libpcre2-8-0 (= 10.42-1),
 libperl5.36 (= 5.36.0-7),
 libpipeline1 (= 1.5.7-1),
 libquadmath0 (= 13.1.0-7),
 libseccomp2 (= 2.5.4-1+b3),
 libselinux1 (= 3.4-1+b6),
 libsmartcols1 (= 2.38.1-5+b1),
 libssl3 (= 3.0.9-1),
 libstdc++-12-dev (= 12.3.0-5),
 libstdc++6 (= 13.1.0-7),
 libsub-override-perl (= 0.09-4),
 libsystemd0 (= 253-4),
 libtext-glob-perl (= 0.11-3),
 libtinfo6 (= 6.4-4),
 libtirpc-common (= 1.3.3+ds-1),
 libtirpc-dev (= 1.3.3+ds-1),
 libtirpc3 (= 1.3.3+ds-1

Bug#1053929: linux-image-amd64: kernel fails to find all nvme SSDs

[Jeffrey Mark Siskind]

Supermicro provided a workaround: boot with the kernel command line
parameter pci=realloc=off.

As an side, Rocky 9.2 does not have this issue even though it boots
without that kernel command line parameter.

Jeff (http: //engineering.purdue.edu/~qobi)

Bug#1053929: linux-image-amd64: kernel fails to find all nvme SSDs

[Jeffrey Mark Siskind]

Package: linux-image-amd64
Version: 6.4.4-3~bpo12+1
Severity: important

Dear Maintainer,

   * What led up to the situation?

I purchased a new server: Supermicro AS-8125GS-TNHR. It has 17 NVME
drives installed:

1x Micron 7450
   12x Micron 9300
4x Micron 9400

Upon boot, /dev/nvme* only shows 10 drives: the Micron 7450, 8 of the
Micron 9300s, and 1 of the Micron 9400s. Before I plugged in the 12x
Micron 9300, /dev/nvme* only showed 2 drives: the Micron 7450 and 1 of
the Micron 9400s.

I run bookworm stable. Upon first install, it ran kernel
6.1.0-12. After an apt upgrade it ran 6.1.0-13. I also installed
6.4.0-0-deb12.2 from bookworm backports. All 3 exhibit the same
issue. the only difference is that under 6.1.0-13 the 10 drives that do
appear appear as /de/nvme{0,1,2,3,4,5,6,7,8,9} while under 6.4.0-0-deb12.2
the 10 drives that do appear appear as different numbers with some missing.

The 1x 7450 has 3 partitions: EFI, / formatted as btrfs, and swap.
The 12x 9300s are all formatted with 1 partition. There are 6 pairs of
2, Each pair has a btrfs raid1 file system. The 9400s are not yet formatted.

   * What exactly did you do (or not do) that was effective (or
 ineffective)?

I tried 3 kernels: 6.1.0-12, 6.1.0-13, and 6.4.0-0-deb12.2.
I tried with and without the 12x 9300.
I enclose the output of ls /dev/nvme*, lspci -k, and hwinfo --disks below.

   * What was the outcome of this action?

All exhibit the same issue.

   * What outcome did you expect instead?

I had hoped that I would be able to access all 17 drives (and format
the 4x 9400s as a single btrfs raid1 filesystem).

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

Kernel: Linux 6.4.0-0.deb12.2-amd64 (SMP w/383 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages linux-image-amd64 depends on:
ii  linux-image-6.4.0-0.deb12.2-amd64  6.4.4-3~bpo12+1

linux-image-amd64 recommends no packages.

linux-image-amd64 suggests no packages.

-- no debconf information

Thanks,
Jeff (http: //engineering.purdue.edu/~qobi)

qobi@poto>ls /dev/nvme*
/dev/nvme1   /dev/nvme12n1/dev/nvme15n1/dev/nvme5n1
/dev/nvme10  /dev/nvme12n1p1  /dev/nvme15n1p1  /dev/nvme5n1p1
/dev/nvme10n1/dev/nvme14  /dev/nvme1n1 /dev/nvme6
/dev/nvme10n1p1  /dev/nvme14n1/dev/nvme1n1p1   /dev/nvme6n1
/dev/nvme11  /dev/nvme14n1p1  /dev/nvme3   /dev/nvme8
/dev/nvme11n1/dev/nvme14n1p2  /dev/nvme3n1 /dev/nvme8n1
/dev/nvme11n1p1  /dev/nvme14n1p3  /dev/nvme3n1p1   /dev/nvme8n1p1
/dev/nvme12  /dev/nvme15  /dev/nvme5
qobi@poto>
-
qobi@poto>lspci -k
00:00.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Device 14a4 (rev 01)
   Subsystem: Super Micro Computer Inc Device 1d1c
00:00.2 IOMMU: Advanced Micro Devices, Inc. [AMD] Device 149e (rev 01)
   Subsystem: Advanced Micro Devices, Inc. [AMD] Device 149e
00:00.3 Generic system peripheral [0807]: Advanced Micro Devices, Inc. [AMD] 
Device 14a6
   Subsystem: Advanced Micro Devices, Inc. [AMD] Device 14a6
   Kernel driver in use: pcieport
00:01.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Device 149f (rev 01)
00:01.1 PCI bridge: Advanced Micro Devices, Inc. [AMD] Device 14ab (rev 01)
   Subsystem: Advanced Micro Devices, Inc. [AMD] Device 1234
   Kernel driver in use: pcieport
00:02.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Device 149f (rev 01)
00:03.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Device 149f (rev 01)
00:04.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Device 149f (rev 01)
00:05.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Device 149f (rev 01)
00:05.1 PCI bridge: Advanced Micro Devices, Inc. [AMD] Device 14aa (rev 01)
   Subsystem: Advanced Micro Devices, Inc. [AMD] Device 1234
   Kernel driver in use: pcieport
00:07.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Device 149f (rev 01)
00:07.1 PCI bridge: Advanced Micro Devices, Inc. [AMD] Device 14a7 (rev 01)
   Subsystem: Advanced Micro Devices, Inc. [AMD] Device 14a4
   Kernel driver in use: pcieport
00:07.2 PCI bridge: Advanced Micro Devices, Inc. [AMD] Device 14a7 (rev 01)
   Subsystem: Advanced Micro Devices, Inc. [AMD] Device 14a4
   Kernel driver in use: pcieport
00:14.0 SMBus: Advanced Micro Devices, Inc. [AMD] FCH SMBus Controller (rev 71)
   Subsystem: Super Micro Computer Inc FCH SMBus Controller
Kernel driver in use: piix4_smbus
   Kernel modules: i2c_piix4, sp5100_tco
00:14.3 ISA 

Bug#1053760: util-linux-extra: obsolete conffiles left behind

[Mark Hindley]

Sven,

It was a conscious decision (on my part) not to remove the conffiles at this
stage. Whilst I accept this leaves cruft on systems that don't have 
bin:initscripts
installed, it has the benefit that user modified conffiles are preserved during
the transition to initscripts, as required by the Policy.

I think this cleanup can happen saftely in the Forky release cycle.

For reference, the udev maintainers have recently tried this cleanup at an
earlier stage and it has not been straightforward.

Mark

Bug#1053760: util-linux-extra: obsolete conffiles left behind

[Mark Hindley]

Sven,

It was a conscious decision (on my part) not to remove the conffiles at this
stage. Whilst I accept this leaves cruft on systems that don't have initscripts
installed, it has the benefit that user modified conffiles are preserved during
the transition to bin:initscripts, as required by the Policy.

I think this cleanup can happen saftely in the Forky release cycle.

For reference, the udev maintainers have recently tried this cleanup at an
earlier stage and it has not been straightforward.

Mark

Bug#1053718: python3-xarray: xarray reports version 999 because the importlib.metadata is using the fallback version

[Mark Harfouche]

Package: python3-xarray
Version: 2023.08.0-1ubuntu5
Severity: normal
X-Debbugs-Cc: mark.harfou...@gmail.com

Dear Maintainer,

   * What led up to the situation?
 apt install python3-xarray (on ubuntu 23.10). Then

 python3 -c "import xarray; assert(xarray.__version__.startswith('201')"

   * What exactly did you do (or not do) that was effective (or
 ineffective)?

 python3 -c "from importlib.metadata import version as _version; 
print(_version('xarray'))"

   * What was the outcome of this action?

 wrong version reported. In fact, the fallback version in the
 setup.py is reported.

   * What outcome did you expect instead?

 The version of xarray to be correctly reported.


I feel like a build tool is missing since conda-forge doesn't do much
special during the build phase.

We do have `setuptoos-scm` installed.

https://github.com/conda-forge/xarray-feedstock/blob/main/recipe/meta.yaml#L21


-- System Information:
Debian Release: trixie/sid
  APT prefers mantic
  APT policy: (500, 'mantic')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 6.5.1-060501-generic (SMP w/8 CPU threads; PREEMPT)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages python3-xarray depends on:
ii  python33.11.4-5
ii  python3-jinja2 3.1.2-1
ii  python3-numpy  1:1.24.2-1
ii  python3-packaging  23.1-1
ii  python3-pandas 1.5.3+dfsg-6

Versions of packages python3-xarray recommends:
ii  python3-bottleneck  1.3.5+ds1-2build1
ii  python3-cftime  1.6.2-3build1
ii  python3-dask2023.8.0+dfsg-2
ii  python3-h5netcdf1.2.0-1
ii  python3-netcdf4 1.6.4-1
ii  python3-rasterio1.3.8-1
ii  python3-sparse  0.13.0-1
ii  python3-zarr2.16.0+ds-1

Versions of packages python3-xarray suggests:
pn  python-xarray-doc   
pn  python3-cartopy 
ii  python3-matplotlib  3.6.3-1ubuntu2
pn  python3-pydap   
ii  python3-scipy   1.10.1-2
pn  python3-seaborn 
ii  python3-toolz   0.12.0-1

-- no debconf information

Bug#1053716: python3-json-tricks: Please update to the latest version (3.17.3) the latest version is more than 5 years old

[Mark Harfouche]

Package: python3-json-tricks
Version: 3.11.0-4
Severity: normal
X-Debbugs-Cc: mark.harfou...@gmail.com

Dear Maintainer,

   * What led up to the situation? I was trying to use ubuntu provided
   * packages to test my application using the GDB debugger.
   * What exactly did you do (or not do) that was effective (or
 ineffective)?
 Tried to install json-tricks from apt, they follow your packages.
   * What was the outcome of this action?
 I had to write compatibility code between json-tricks 3.17 and
 3.11
   * What outcome did you expect instead?
 I wanted a modern version of json-tricks to be installed.

I am happy to make a merge request directly to

https://salsa.debian.org/python-team/packages/json-tricks

but I don't know if you prefer to rebase or merge when updating your
source.

Thanks!

Mark

-- System Information:
Debian Release: trixie/sid
  APT prefers mantic
  APT policy: (500, 'mantic')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 6.5.1-060501-generic (SMP w/8 CPU threads; PREEMPT)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages python3-json-tricks depends on:
ii  python3  3.11.4-5

python3-json-tricks recommends no packages.

python3-json-tricks suggests no packages.

-- no debconf information

Bug#1053301: udev.postinst removes valid /etc/rc*.d/ symlinks

[Mark Hindley]

Control: tags -1 patch
Control: affects -1 initscripts
Control: severity -1 serious
Justification: Breaks unrelated packages, breaks non-systemd boot

Michael,

Please find a patch below that addresses this issue in my test setup. I can
offer to NMU if you would like?

I have provided an easy means to reproduce the bug and a clear justfication for
why I think this is an RC bug. If you disagree, please explain why, rather than
just changing the severity. Thanks.

Best wishes

Mark

diff --git a/debian/changelog b/debian/changelog
index fe1f4bc..ec8a75a 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,12 @@
+systemd (254.5-1.1) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * d/udev.postinst: Correct version number test for dropping
+/etc/init.d/udev and only remove /etc/rc?.d/symlinks if
+/etc/init.d/udev doesn't exist.  (Closes: #1053301)
+
+ -- Mark Hindley   Wed, 04 Oct 2023 18:30:36 +0100
+
 systemd (254.5-1) unstable; urgency=medium
 
   * New upstream version 254.5
diff --git a/debian/udev.postinst b/debian/udev.postinst
index 84ff782..04bafa2 100644
--- a/debian/udev.postinst
+++ b/debian/udev.postinst
@@ -11,7 +11,8 @@ case "$1" in
 # update/create hwdb before we (re)start udev
 update_hwdb
 
-if dpkg --compare-versions "$2" lt-nl "254.1-4~"; then
+if dpkg --compare-versions "$2" lt-nl "254.3-1~" &&
+[ ! -f /etc/init.d/udev ] ; then
 update-rc.d udev remove || true
 fi
 ;;

Bug#1052942: insserv: FTBFS: insserv: Could not read script nolsbheader: No such file or directory

[Mark Hindley]

Control: tags -1 moreinfo

Ian

On Wed, Sep 27, 2023 at 10:33:32PM +0100, Ian Jackson wrote:
> Mark Hindley writes ("Bug#1052942: insserv: FTBFS: insserv: Could not read 
> script nolsbheader: No such file or directory"):
> > Thanks for this. However, I am currently unable to repoduce this
> > failure in my customary pbuilder setup. And it doesn't appear at
> > reproducible builds either[1]
> 
> I just tried this myself with my usual sbuild setup and it succeeded
> there too[1].


Thanks for your confirmation.

> Lucas, I think something from your rebuild environment
> (a chroot of some kind I presume) must be triggering this failure.  Is
> there some way we can reproduce it more precisely (eg, a buildinfo
> file?)

Yes, I agree a buildinfo file might give a hint.

> I looked at the build log
>  http://qa-logs.debian.net/2023/09/25/insserv_1.24.0-1_unstable.log
> and compared it to the one from my sbuild, using diff.  There are a
> lot of changes to the "furniture" but also there are noise changes to
> the output of the insserv test suite, including ordring changes of
> passing tests.  This seemed surprising to me.
> 
> Mark, is the insserv test suite supposed to produce deterministic
> output ?

I have never had the need to look at the testsuite since I started looking after
the package. A quick look now doesn't immediately reveal something that would
obviously change the order of the tests.

I tried again locally with make -j8 and still could not reproduce any failure.

Mark

Bug#1053301: udev.postinst removes valid /etc/rc*.d/ symlinks

[Mark Hindley]

s and is not owned
by bin:udev.

 2) There appears to be a typo: the version of src:systemd which dropped
/etc/init.d/udev was 254.3-1[1]. AFAICS 254.1-4 was never released.

With best wishes,

Mark

[1]  https://tracker.debian.org/media/packages/s/systemd/changelog-254.4-1

Bug#1042082: Please take over udev SysV init script

[Mark Hindley]

Control: clone -1 -2
Control: retitle -2 udev.postinst removes valid /etc/rc*.d/ symlinks

Bill

On Fri, Sep 29, 2023 at 09:51:21PM -0700, Bill Brelsford wrote:
> When upgrading (with aptitude), initscripts (3.08-1) is set up
> before udev (254.4-1). Udev claims to remove the "obsolete
> conffile /etc/init.d/udev", but it's still there. However, the
> rc*.d symlinks are not -- "update-rc.d udev defaults" fixes it.

This is a new issue. Cloning.

Mark

Bug#1053092: initscripts: cannot upgrade to 3.08-1: APT dependency loop

[Mark Hindley]

Martin,

Thanks for this.

On Wed, Sep 27, 2023 at 08:22:33AM +0200, Lorenzo wrote:
> Control: severity -1 whishlist
> 
> Hi,
> 
> On Wed, 27 Sep 2023 08:14:19 +0300
> Martin-Éric Racine  wrote:
> 
> > Kernel: Linux 6.5.0-1-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)
> 
> I guess this is the effect of
> 
> https://salsa.debian.org/systemd-team/systemd/-/commit/eecd735541c9d5deb9cebd5f2512e7da8b4368a9
> 
> that adds a conflicts with initscripts. You can remove initscripts or
> reassign to systemd as whishlist, explaining why you need both
> initscripts and systemd-sysv installed.
> 
> Regards,
> Lorenzo
> 
> > Package: initscripts
> > Version: 3.07-1
> > Severity: important
> > 
> > $ LC_ALL=C sudo apt-get --option Debug::pkgDepCache::AutoInstall=true
> > install initscripts Reading package lists... Done
> > Building dependency tree... Done
> > Reading state information... Done
> >Removing: udev:i386 as upgrade is not an option for
> > initscripts:i386 (3.08-1)

I am not sure there is a bug here anyway. there is an ongoing migration of
/etc/init.d/udev from bin:udev to bin:initscripts. src:sysvinit 3.08-1 (which
has taken over the file and breaks/replaces udev << 254.3-1 ) has migrated to
testing[1], however the migration of src:systemd 254.4-1 is blocked by
autopkgtest regressions[2].

Once a suitable version of src:systemd migrates to testing, I think apt will be
able to resolve the dependencies.

Mark

[1]  https://tracker.debian.org/news/1465552/sysvinit-308-1-migrated-to-testing/

[2]  https://qa.debian.org/excuses.php?package=systemd

Bug#1052942: insserv: FTBFS: insserv: Could not read script nolsbheader: No such file or directory

[Mark Hindley]

Control: tags -1 unreproducible

Lucas,

Thanks for this. However, I am currently unable to repoduce this failure in my
customary pbuilder setup. And it doesn't appear at reproducible builds either[1]

On Tue, Sep 26, 2023 at 03:45:26PM +0200, Lucas Nussbaum wrote:
> If you fail to reproduce this, please provide a build log and diff it with 
> mine
> so that we can identify if something relevant changed in the meantime.

My successful pbuilder log is attached.

Mark


[1]  
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/insserv.html

dpkg-checkbuilddeps: error: Unmet build dependencies: debhelper-compat (= 13) 
po-debconf
W: Unmet build-dependency in source
dpkg-source: info: using patch list from debian/patches/series
dpkg-source: info: applying install-binaries-ignore-PREFIX.patch
dpkg-source: info: applying 11_debian_conf.patch
dpkg-source: info: applying 110_portmap.patch
dpkg-source: info: applying warn_in_ignore_mode.patch
dpkg-source: info: applying 
0004-Fix-spurious-warnings-about-unknown-virtual-dependen.patch
dpkg-source: info: applying 0005-Fix-spelling-error-in-manpage.patch
dpkg-source: info: using source format '3.0 (quilt)'
dpkg-source: info: building insserv using existing ./insserv_1.24.0.orig.tar.gz
dpkg-source: info: using patch list from debian/patches/series
dpkg-source: info: building insserv in insserv_1.24.0-1.debian.tar.xz
dpkg-source: info: building insserv in insserv_1.24.0-1.dsc
I: Generated dsc will be overwritten by build result; not generating changes 
file
dpkg-source: info: unapplying 0005-Fix-spelling-error-in-manpage.patch
dpkg-source: info: unapplying 
0004-Fix-spurious-warnings-about-unknown-virtual-dependen.patch
dpkg-source: info: unapplying warn_in_ignore_mode.patch
dpkg-source: info: unapplying 110_portmap.patch
dpkg-source: info: unapplying 11_debian_conf.patch
dpkg-source: info: unapplying install-binaries-ignore-PREFIX.patch
I: Copying COW directory
I: forking: rm -rf /var/cache/pbuilder/build/cow.20068
I: forking: cp -al /var/cache/pbuilder/base-sid.cow 
/var/cache/pbuilder/build/cow.20068
I: removed stale ilistfile /var/cache/pbuilder/build/cow.20068/.ilist
I: forking: chroot /var/cache/pbuilder/build/cow.20068 cowdancer-ilistcreate 
/.ilist 'find . -xdev -path ./home -prune -o \( \( -type l -o -type f \) -a 
-links +1 -print0 \) | xargs -0 stat --format '%d %i ''
I: Invoking pbuilder
I: forking: pbuilder build --debbuildopts  --debbuildopts '  '--no-pre-clean'' 
--buildplace /var/cache/pbuilder/build/cow.20068 --buildresult 
/home/mark/src/debian/build --mirror http://deb.debian.org/debian 
--distribution sid --no-targz --internal-chrootexec 'chroot 
/var/cache/pbuilder/build/cow.20068 cow-shell' 
/home/mark/src/debian/build/insserv_1.24.0-1.dsc
I: Running in no-targz mode
I: pbuilder: network access will be disabled during build
I: Current time: Tue Sep 26 17:05:48 BST 2023
I: pbuilder-time-stamp: 1695744348
I: copying local configuration
W: --override-config is not set; not updating apt.conf Read the manpage for 
details.
I: mounting /proc filesystem
I: mounting /sys filesystem
I: creating /{dev,run}/shm
I: mounting /dev/pts filesystem
I: redirecting /dev/ptmx to /dev/pts/ptmx
I: policy-rc.d already exists
I: Obtaining the cached apt archive contents
I: Copying source file
I: copying [/home/mark/src/debian/build/insserv_1.24.0-1.dsc]
I: copying [/home/mark/src/debian/build/insserv_1.24.0.orig.tar.gz]
I: copying [/home/mark/src/debian/build/insserv_1.24.0-1.debian.tar.xz]
I: Extracting source
dpkg-source: warning: extracting unsigned source package (insserv_1.24.0-1.dsc)
dpkg-source: info: extracting insserv in insserv-1.24.0
dpkg-source: info: unpacking insserv_1.24.0.orig.tar.gz
dpkg-source: info: unpacking insserv_1.24.0-1.debian.tar.xz
dpkg-source: info: using patch list from debian/patches/series
dpkg-source: info: applying install-binaries-ignore-PREFIX.patch
dpkg-source: info: applying 11_debian_conf.patch
dpkg-source: info: applying 110_portmap.patch
dpkg-source: info: applying warn_in_ignore_mode.patch
dpkg-source: info: applying 
0004-Fix-spurious-warnings-about-unknown-virtual-dependen.patch
dpkg-source: info: applying 0005-Fix-spelling-error-in-manpage.patch
I: using fakeroot in build.
I: Installing the build-deps
I: user script /var/cache/pbuilder/build/cow.20068/tmp/hooks/D04add-backports 
starting
I: user script /var/cache/pbuilder/build/cow.20068/tmp/hooks/D04add-backports 
finished
I: user script /var/cache/pbuilder/build/cow.20068/tmp/hooks/D05apt-update 
starting

WARNING: apt does not have a stable CLI interface. Use with caution in scripts.

Get:1 http://deb.debian.org/debian unstable InRelease [195 kB]
Get:2 http://deb.debian.org/debian unstable/main amd64 Packages.diff/Index 
[63.6 kB]
Ign:2 http://deb.debian.org/debian unstable/main amd64 Packages.diff/Index
Get:3 http://deb.debian.org/debian unstable/main Translation-en.diff/Index 
[63.6 kB]
Ign:3 http://deb.debian.org/debian unstable/main Translatio

Bug#1050375: Invalid command name "pg_connect"

[Mark Hindley]

Control: reassign -1 libpgtcl
Control: retitle -1 libpgtcl not installed in default Tcl search path.

On Wed, Aug 23, 2023 at 08:09:48PM +0200, Christoph Berg wrote:
> Package: pfm
> Version: 2.0.8-3
> Severity: grave
> 
> pfm doesn't do anything useful here, it just produces a message popup
> saying
> 
> Connection to database foo has failed:
> 
> invalid command name "pg_connect"

Thanks. I believe this needs fixing in libpgtcl.

Reassigning.

Mark

Bug#1052316: udev postinst uses update-rc.d -f remove which breaks /etc.init.d/udev transition and non-systemd boot

[Mark Hindley]

Package: udev
Version: 254.3-1
Severity: serious
Justification: Breaks unrelated software, causes boot failure on some systems

Dear systemd Maintainers,

As reported in the follow-up to #1052116[1], udev's postinst uses update-rc.d's
-f option which breaks the transition of /etc/init.d/udev to bin:initscripts and
causes non-systemd systems to fail to boot.

Michael, as discussed yesterday on #debian-systemd, I am very grateful for your
quick commit of a fix[2].

This bug is to prevent unintended migration of the broken udev to trixie.

With thanks and best wishes

Mark

[1]  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1052116#17
[2]  
https://salsa.debian.org/systemd-team/systemd/-/commit/12e2c67612f958148f0a4ca165cfb9ca1ed9d3c3


-- System Information:
Debian Release: 12.0
merged-usr: no
Architecture: amd64 (x86_64)

Kernel: Linux 6.1.0-9-amd64 (SMP w/2 CPU threads; PREEMPT)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_GB:en
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)

Bug#1052116: initscripts: /etc/rcX.d symlinks not created

[Mark Hindley]

Kevin,

On Wed, Sep 20, 2023 at 02:07:48AM +, Kevin Ruml wrote:
>I know you sent subsequent messages about a fix, but since you asked me
>to test this and it was easy enough for me to do it, I did.
>Downgrading then upgrading again left the system without the symlinks.
>Running "dpkg-reconfigure initscripts" did generate the symlinks.

Thanks, that is really useful confirmation that we aren't missing something
else.

Much appreciated.

Mark

Bug#1052116: initscripts: /etc/rcX.d symlinks not created

[Mark Hindley]

On Tue, Sep 19, 2023 at 08:36:05AM +0100, Mark Hindley wrote:
> Yes. I think the real issue is the udev.postinst using update-rc.d -f remove
> udev. Without the -f option, I think the symlinks would be left intact.

The fix for this has been queued in src:systemd[1].

Mark

[1]  
https://salsa.debian.org/systemd-team/systemd/-/commit/12e2c67612f958148f0a4ca165cfb9ca1ed9d3c3

Bug#1052116: initscripts: /etc/rcX.d symlinks not created

[Mark Hindley]

On Tue, Sep 19, 2023 at 09:33:29AM +0200, Lorenzo wrote:
> One solution could be that udev does the cleanup only if initscripts
> is not installed in the system; otherwise assume a take over from
> initscripts package.
> The removal bits in udev package could be guarded by something like
> 
> If ! dpkg -s initscripts >/dev/null ; then
>   #remove udev 's sysv bits
> fi

Yes. I think the real issue is the udev.postinst using update-rc.d -f remove
udev. Without the -f option, I think the symlinks would be left intact.

Mark

Bug#1052116: initscripts: /etc/rcX.d symlinks not created

[Mark Hindley]

On Tue, Sep 19, 2023 at 07:29:45AM +0100, Mark Hindley wrote:
> > Setting up initscripts (3.08-1) ...
> > Setting up udev (254.3-1) ...
> 
> The udev postinst, which removes the update-rc.d symlinks is  run after the
> initscripts postinst which has created them.

Just so I can be sure that there isn't a bug in the initscripts postinst, having
upgraded to initscripts 3.08-1, can you run

 dpkg-reconfigure initscripts

and verify that the symlinks are recreated?

Thanks

Mark

Bug#1052116: initscripts: /etc/rcX.d symlinks not created

[Mark Hindley]

Kevin,

Many thanks for reporting this.

I think this is an ordering issue.

On Mon, Sep 18, 2023 at 09:07:59PM -0500, Kevin Ruml wrote:
[..]

> Setting up libudev1:i386 (254.3-1) ...
> Setting up sysv-rc (3.08-1) ...
> Setting up initscripts (3.08-1) ...
> Setting up udev (254.3-1) ...

The udev postinst, which removes the update-rc.d symlinks is  run after the
initscripts postinst which has created them.

Hmmm...

Mark

Bug#1050561: libelogind-dev-doc: sd_listen_fds(3) manual damaged

[Mark Hindley]

Control: tags -1 upstream
Control: forwarded -1 https://github.com/elogind/elogind/issues/263

On Sat, Aug 26, 2023 at 12:03:02PM +0200, наб wrote:
> Package: libelogind-dev-doc
> Version: 246.10-1debian1
> Severity: normal

Thanks. Forwarded upstream.

Mark

Bug#1051743: debhelper: dh_installsystemd --name documentation doesn't match actual behavior

[Mark Eichin]

Subject: debhelper: dh_installsystemd --name documentation doesn't match actual 
behavior
Package: debhelper
Version: 13.11.6
Severity: normal

Dear Debhelper Maintainers,

The dh_installsystemd documentation says that

   As an example, B will look for
   F<<< IB<< I >>I<.service> >>> instead of
   F<< I >>).  

after building a handful of packages and having this silently not work
(the silence isn't a problem per-se, it's just supposed to look for a
correctly named file and use it if present) I eventually figured out
that it would instead install the file F<< I >>,
ie. it would drop I entirely and just use the --name
argument.

There is also a lengthy comment in the source where the work happens
that matches the POD documentation, but the code itself at that point
simply does

   my $name = $dh{NAME} // $package;

which doesn't concatenate anything, it just uses --name if defined, and
package if not.

A quick glance through git history shows that it's behaved this way
since at least 2018 and it looks like that was just an accurate
refactoring of the previous code - I haven't dug further, but perhaps
that is enough to suggest that 5 years is long enough that the
documentation should change to match the behaviour rather than changing
the code (possibly across debhelper's famously well-managed
compatibility levels.)

(If you agree with my assessment, I would be happy to contribute a
documentation patch, though it would be US/English only, I haven't
worked with translations before.)

Bug#934463: initscripts: consider taking over hwclock policy machinery

[Mark Hindley]

Andreas,

Thanks for your thoughts on this.

On Thu, Aug 24, 2023 at 06:16:08PM +0200, Andreas Henriksson wrote:
> Since initscripts will need (and has) Breaks/Replaces: util-linux-extra
> the circular nature of util-linux-extra having the same makes me think
> this is something which might be useful to think about a second time.
> Additionally, util-linux-extra might not even be installed on users
> system now that it's no longer pseudo-essential If we want to
> prevent (sysvinit) users from partially upgrading util-linux-extra
> and lack the hwclock machinery, then we likely also want to prevent
> them from deinstalling util-linux-extra which would have the same
> result.

I don't think the hwclock machinery is universally required on non-systemd init
systems: all of my systems are non-systemd and none have util-linux-extra
installed but run one of the time-daemon providers.

Bin:initscripts is installed on all non-systemd systems by being a dependency of
sysvinit-core and runit-init and itself depending on sysv-rc | openrc.

I see 2 scenarios we need to enforce with the dependencies:-

 1) Avoid dpkg attempting installation of packages with conflicting files

 2) Ensure users who might use the hwclock machinery (i.e. currently have
 util-linux-extra installed) continue to have it available

I think 1) is covered by the Breaks/Replaces. 2) is addressed by apt's
preference to upgrade rather than remove packages.

Despite the circular nature of both util-linux-extra and initscripts having
reciprocal breaks that you identify, it is the recommendation in the Package
Transition Wiki[1]. I think we are dealing with scenario #9.

With best wishes.

Mark

[1]  https://wiki.debian.org/PackageTransition

Bug#1051627: units: The temperature conversion between Fahrenheit and Celcius is wrong

[Mark Grieveson]

Package: units
Version: 2.22-2
Severity: normal
X-Debbugs-Cc: markgrieve...@yahoo.ca

Dear Maintainer,

*** Reporter, please consider answering these questions, where appropriate ***

   * What led up to the situation?

I was trying to convert a temperature from degrees Celcius ("degC") to degrees 
Fahrenheit ("degF")

   * What exactly did you do (or not do) that was effective (or
 ineffective)?

I typed "0 degC" as the unit I had, and I typed "degF" as the unit I wanted.

   * What was the outcome of this action?

You have: 0 degC
You want: degF
* 0
/ inf

   * What outcome did you expect instead?

Zero degrees Celcius equals 32 degrees Fahrenheit.  So, I expected the 
following:

You have: 0 degC
You want: degF
* 32


*** End of the template - remove these template lines ***


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

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

Versions of packages units depends on:
ii  libc6 2.36-9+deb12u1
ii  libreadline8  8.2-1.3

Versions of packages units recommends:
ii  python3   3.11.2-1+b1
ii  python3-requests  2.28.1+dfsg-1

units suggests no packages.

-- no debconf information