Bug#1030529: /etc/needrestart/restart.d/dbus.service: incorrect output about pauses before dbus restart

[Adam Dinwoodie]

Package: needrestart
Version: 3.6-3
Severity: minor
File: /etc/needrestart/restart.d/dbus.service

Dear Maintainer,

If dbus needs restarting, the output from needrestart includes the
following output:

Service restarts being deferred:
 /etc/needrestart/restart.d/dbus.service

This implies that the user can run this script to restart dbus.
Running the script produces output including the following line:

!!! In  seconds dbus restart will be performed !!!

This is because the variable `$PAUSE` is used without being initialized
in the script.  The message also seems to be clearly incorrect: there is
no `sleep` or similar later in the script before the `systemd-run`
command to restart the services.

Kind regards,

Adam

-- Package-specific info:
needrestart output:
Your outdated processes:
systemd[887]



-- System Information:
Debian Release: bookworm/sid
  APT prefers testing
  APT policy: (990, 'testing'), (850, 'stable'), (500, 'stable-updates'), (500, 
'stable-security'), (500, 'unstable')
Architecture: arm64 (aarch64)
Foreign Architectures: armhf

Kernel: Linux 5.15.84-v8+ (SMP w/4 CPU threads; PREEMPT)
Kernel taint flags: TAINT_CRAP
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)

Versions of packages needrestart depends on:
ii  binutils   2.40-2
ii  dpkg   1.21.19
ii  gettext-base   0.21-10
ii  libintl-perl   1.33-1
ii  libmodule-find-perl0.16-2
ii  libmodule-scandeps-perl1.31-2
ii  libproc-processtable-perl  0.634-1+b2
ii  libsort-naturally-perl 1.03-4
ii  libterm-readkey-perl   2.38-2+b1
ii  perl   5.36.0-7
ii  xz-utils   5.4.1-0.0

Versions of packages needrestart recommends:
ii  libpam-systemd  252.4-2
ii  systemd 252.4-2

Versions of packages needrestart suggests:
pn  iucode-tool
ii  libnotify-bin  0.8.1-1

-- Configuration Files:
/etc/needrestart/needrestart.conf changed [not included]

-- no debconf information

Bug#1018094: offlineimap3: Entire sync fails if one email has an invalid Date header

[Adam Dinwoodie]

Package: offlineimap3
Version: 0.0~git20210225.1e7ef9e+dfsg-4
Severity: normal
Tags: patch upstream

Dear Maintainer,

When syncing a mail directory that contained an email with a clearly
bogus Date header, OfflineIMAP would fail because, while handling the
exception raised due to the duff header, it would attempt to parse the
header again.

This is reported upstream at
https://github.com/OfflineIMAP/offlineimap3/issues/134

I've written a patch, which I've attached, and also offered upstream at
https://github.com/OfflineIMAP/offlineimap3/pull/135

-- System Information:
Debian Release: 11.4
  APT prefers stable-updates
  APT policy: (990, 'stable-updates'), (990, 'stable-security'), (990, 
'stable'), (850, 'testing'), (500, 'unstable')
Architecture: arm64 (aarch64)
Foreign Architectures: armhf

Kernel: Linux 5.15.56-v8+ (SMP w/4 CPU threads; PREEMPT)
Kernel taint flags: TAINT_CRAP
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages offlineimap3 depends on:
ii  python3   3.9.2-3
ii  python3-distro1.5.0-1
ii  python3-imaplib2  2.57-5.2

offlineimap3 recommends no packages.

offlineimap3 suggests no packages.

-- no debconf information
>From 416df5d7c2327a9d50946cf29d6548812dde6018 Mon Sep 17 00:00:00 2001
From: Adam Dinwoodie 
Date: Thu, 25 Aug 2022 16:12:13 +0100
Subject: [PATCH] Skip parsing date after failing to parse the date

When file_use_mail_timestamp or utime_from_header are enabled,
OfflineIMAP tries to parse the Date header in the email.  If the header
is present but invalid -- it doesn't contain a valid date -- this will
cause email.message to raise an exception.  This is all fine.  However
when handling that exception, OfflineIMAP can't try to extract the date
again: it's clearly invalid, and raising the same exception a second
time while handling the first exception just causes the entire sync to
fail.

To avoid that happening, don't try to provide the invalid date string in
the error message.  Instead, just give the user the UID of the email
that triggered the exception, and the exception text.

Ideally we'd instead fix the code to actually extract the header value
and provide it in the error message, but Python's email.message module
doesn't provide an easy way to get the raw text of the Date header from
an EmailMessage object; it's possible using private variables like
EmailMessage._headers, or by parsing the email using a custom
email.policy.EmailPolicy object that disables the module's attempts to
coerce the header value to a DateTime.  However, a user should be able
to get the problematic Date header from the message directly anyway, so
it's not worth adding all that complexity for something that should be
rare and provides little value.

Fixes #134

Signed-off-by: Adam Dinwoodie 
---
 offlineimap/folder/Maildir.py | 18 --
 1 file changed, 8 insertions(+), 10 deletions(-)

diff --git a/offlineimap/folder/Maildir.py b/offlineimap/folder/Maildir.py
index f319b66..4237cee 100644
--- a/offlineimap/folder/Maildir.py
+++ b/offlineimap/folder/Maildir.py
@@ -396,32 +396,30 @@ class MaildirFolder(BaseFolder):
 message_timestamp = self.get_message_date(
 msg, 'Delivery-date')
 except Exception as e:
-# This should never happen.
+# Extracting the date has failed for some reason, such as it
+# being in an invalid format.
 from offlineimap.ui import getglobalui
-datestr = self.get_message_date(msg)
 ui = getglobalui()
-ui.warn("UID %d has invalid date %s: %s\n"
-"Not using message timestamp as file prefix" %
-(uid, datestr, e))
+ui.warn("UID %d has invalid date: %s\n"
+"Not using message timestamp as file prefix" % (uid, 
e))
 # No need to check if message_timestamp is None here since it
 # would be overridden by _gettimeseq.
 messagename = self.new_message_filename(uid, flags, 
date=message_timestamp)
 tmpname = self.save_to_tmp_file(messagename, msg)
 
 if self._utime_from_header is True:
 try:
 date = self.get_message_date(msg, 'Date')
 if date is not None:
 os.utime(os.path.join(self.getfullname(), tmpname),
  (date, date))
-# In case date is wrongly so far into the future as to be > max
-# int32.
 except Exception as e:
+# Extracting the date has failed for some reason, such as it
+# being in an invalid format.
 from offlineimap.ui import getglobalui
-datestr = self.get_messa

Bug#1018089: rclone should list fuse3 as a dependency

[Adam Dinwoodie]

Package: rclone
Version: 1.53.3-1+b6
Severity: normal

Dear Maintainer,

rclone has a single dependency, libc6.  However using `rclone mount`
requires having something that provides fusermount in the path.

Lots of rclone function works without this package, but it is a key
rclone feature, so rclone should have a dependency (I think
"Recommends", but "Suggests" would suffice) on either the fuse or fuse3
packages.

-- System Information:
Debian Release: 11.4
  APT prefers stable-updates
  APT policy: (990, 'stable-updates'), (990, 'stable-security'), (990, 
'stable'), (850, 'testing'), (500, 'unstable')
Architecture: amd64 (x86_64)

Kernel: Linux 5.10.0-16-cloud-amd64 (SMP w/2 CPU threads)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.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 rclone depends on:
ii  libc6  2.34-3

rclone recommends no packages.

rclone suggests no packages.

-- no debconf information

Bug#1014616: extrepo update fails with "uninitialized value" error

[Adam Dinwoodie]

Package: extrepo
Version: 0.10~bpo11+1
Severity: normal

Dear Maintainer,

The `update` command for extrepo appears to be broken.  I see the
following output from running it:

```
$ sudo extrepo update jellyfin
Use of uninitialized value in join or string at 
/usr/share/perl5/Debian/ExtRepo/Data.pm line 22.
Use of uninitialized value in join or string at 
/usr/share/perl5/Debian/ExtRepo/Data.pm line 22.
Use of uninitialized value in join or string at 
/usr/share/perl5/Debian/ExtRepo/Data.pm line 22.
Could not download index YAML file:
400 URL must be absolute at /usr/share/perl5/Debian/ExtRepo/Data.pm line 27.
...propagated at /usr/bin/extrepo line 187.
```

I got half-way to offering a patch -- it looks like the immediate issue
is simply that the `run` function in Update.pm doesn't pass all the
necessary variables when it calls the corresponding function in
Update.pm -- but looking a bit closer, it looks like the function is
more fundamentally broken than that.  As best I can tell from code
reading, the only thing the `update` command does is disable the warning
about nothing actually being updated!

-- System Information:
Debian Release: 11.3
  APT prefers stable-updates
  APT policy: (990, 'stable-updates'), (990, 'stable-security'), (990, 
'stable'), (850, 'testing'), (500, 'unstable')
Architecture: arm64 (aarch64)
Foreign Architectures: armhf

Kernel: Linux 5.15.32-v8+ (SMP w/4 CPU threads; PREEMPT)
Kernel taint flags: TAINT_CRAP
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages extrepo depends on:
ii  gpgv  2.2.27-2+deb11u2
ii  libcryptx-perl0.069-1+b1
ii  libdpkg-perl  1.20.10
ii  libwww-perl   6.52-1
ii  libyaml-libyaml-perl  0.82+repack-1+b1
ii  perl  5.32.1-4+deb11u2

Versions of packages extrepo recommends:
ii  apt [apt-transport-https]  2.2.4

extrepo suggests no packages.

-- Configuration Files:
/etc/extrepo/config.yaml changed:
---
url: https://extrepo-team.pages.debian.net/extrepo-data
dist: debian
version: bullseye
enabled_policies:
- main
- contrib
- non-free


-- no debconf information

Bug#1014446: dhcpcd5: dhcpcd-run-hooks fails to skip editor backup files

[Adam Dinwoodie]

Package: dhcpcd5
Version: 9.4.1-3
Severity: normal
Tags: patch, upstream

Dear Maintainer,

The script dhcpcd-run-hooks has code to skip hook scripts that should
not be run, either because the file name ends in "~" or because they're
listed in $skip_hooks.  However, if $skip_hooks is undefined or null,
the tests are not run at all, which means files with names ending with
"~" will be unexpectedly run.

This was reported to me privately by another Debian user, who had
attempted to manually apply my patch for 1008059, but found it wasn't
working as expected, as they had used an editor which left the old file
as a backup with that ~ extension.  The hook script is clearly intended
to skip over such files, but the skip doesn't take effect in the
mainline case.

I've attached a patch that fixes this on Debian.  This bug also seems to
be present in the upstream package, and I've provided the same patch at
.

-- System Information:
Debian Release: 11.3
  APT prefers stable-updates
  APT policy: (990, 'stable-updates'), (990, 'stable-security'), (990, 
'stable'), (850, 'testing'), (500, 'unstable')
Architecture: arm64 (aarch64)
Foreign Architectures: armhf

Kernel: Linux 5.15.32-v8+ (SMP w/4 CPU threads; PREEMPT)
Kernel taint flags: TAINT_CRAP
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages dhcpcd5 depends on:
ii  dhcpcd-base  9.4.1-3
ii  lsb-base 11.1.0

dhcpcd5 recommends no packages.

Versions of packages dhcpcd5 suggests:
pn  dhcpcd-gtk   
pn  openresolv | resolvconf  

-- no debconf information
diff --git a/hooks/dhcpcd-run-hooks.in b/hooks/dhcpcd-run-hooks.in
index a237f6af..84465361 100644
--- a/hooks/dhcpcd-run-hooks.in
+++ b/hooks/dhcpcd-run-hooks.in
@@ -338,9 +338,11 @@ for hook in \
 	@HOOKDIR@/* \
 	@SYSCONFDIR@/dhcpcd.exit-hook
 do
+	case "$hook" in
+		*/*~)	continue;;
+	esac
 	for skip in $skip_hooks; do
 		case "$hook" in
-			*/*~)continue 2;;
 			*/"$skip")			continue 2;;
 			*/[0-9][0-9]"-$skip")		continue 2;;
 			*/[0-9][0-9]"-$skip.sh")	continue 2;;

Bug#1011028: Wishlist: add GitHub CLI repo

[Adam Dinwoodie]

Package: extrepo
Version: 0.10
Severity: wishlist

Dear Maintainer,

GitHub CLI is provided for Debian through a repository of the sort that
extrepo seems designed for; could it please be added to the list of
repositories that extrepo offers?

The documentation pointing at the repository URL and key and so forth is
available at https://github.com/cli/cli/blob/trunk/docs/install_linux.md

Thank you!

-- System Information:
Debian Release: 11.3
  APT prefers stable-updates
  APT policy: (990, 'stable-updates'), (990, 'stable-security'), (990, 
'stable'), (850, 'testing'), (500, 'unstable')
Architecture: arm64 (aarch64)
Foreign Architectures: armhf

Kernel: Linux 5.15.32-v8+ (SMP w/4 CPU threads; PREEMPT)
Kernel taint flags: TAINT_CRAP
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages extrepo depends on:
ii  gpgv  2.2.27-2+deb11u1
ii  libcryptx-perl0.069-1+b1
ii  libdpkg-perl  1.20.9
ii  libwww-perl   6.52-1
ii  libyaml-libyaml-perl  0.82+repack-1+b1
ii  perl  5.32.1-4+deb11u2

Versions of packages extrepo recommends:
ii  apt [apt-transport-https]  2.2.4

extrepo suggests no packages.

-- no debconf information

Bug#1011027: extrepo: "Use of uninitialized value" error on failing search

[Adam Dinwoodie]

Package: extrepo
Version: 0.10
Severity: minor

Dear Maintainer,

When running `extrepo search` to search for a repository that doesn't
exist, as well as correctly reporting "No matches found", there is
unexpected error output reporting "Use of uninitialized value":

```
Use of uninitialized value in pattern match (m//) at 
/usr/share/perl5/Debian/ExtRepo/Commands/Search.pm line 17.
No matches found for github
```


-- System Information:
Debian Release: 11.3
  APT prefers stable-updates
  APT policy: (990, 'stable-updates'), (990, 'stable-security'), (990, 
'stable'), (850, 'testing'), (500, 'unstable')
Architecture: arm64 (aarch64)
Foreign Architectures: armhf

Kernel: Linux 5.15.32-v8+ (SMP w/4 CPU threads; PREEMPT)
Kernel taint flags: TAINT_CRAP
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages extrepo depends on:
ii  gpgv  2.2.27-2+deb11u1
ii  libcryptx-perl0.069-1+b1
ii  libdpkg-perl  1.20.9
ii  libwww-perl   6.52-1
ii  libyaml-libyaml-perl  0.82+repack-1+b1
ii  perl  5.32.1-4+deb11u2

Versions of packages extrepo recommends:
ii  apt [apt-transport-https]  2.2.4

extrepo suggests no packages.

-- no debconf information

Bug#1009307: xfce4-goodies: Package description incorrectly asserts xfce4-artwork will be installed

[Adam Dinwoodie]

On Mon, Apr 11, 2022 at 12:34:32PM +0100, Adam Dinwoodie wrote:
> Package: xfce4-goodies
> Version: 4.14.0
> Severity: minor
> 
> Dear Maintainer,
> 
> The description for xfce4-goodies asserts that installing the package
> will install xfce4-artwork, however this is not listed as a dependency,
> and does not seem to be available in the Debian package repositories at
> all.
> 
> I suspect this is just a change that was not propagated to the package
> description, and the fix is simply to update the package description.

And indeed it looks like there are some other similar errors; I've not
tried to check comprehensively, but I also noticed:

- xfce4-notes-plugin is a Suggested dependency, not a Required one,
  despite the package description saying it's Required.
- The mentioned thunnar-* packages do not exist and are not listed as
  Required.

Adam

Bug#1009307: xfce4-goodies: Package description incorrectly asserts xfce4-artwork will be installed

[Adam Dinwoodie]

Package: xfce4-goodies
Version: 4.14.0
Severity: minor

Dear Maintainer,

The description for xfce4-goodies asserts that installing the package
will install xfce4-artwork, however this is not listed as a dependency,
and does not seem to be available in the Debian package repositories at
all.

I suspect this is just a change that was not propagated to the package
description, and the fix is simply to update the package description.

Kind regards,

Adam Dinwoodie

-- System Information:
Debian Release: 11.3
  APT prefers stable-updates
  APT policy: (990, 'stable-updates'), (990, 'stable-security'), (990, 
'stable'), (850, 'testing'), (500, 'unstable')
Architecture: amd64 (x86_64)

Kernel: Linux 5.10.0-13-amd64 (SMP w/4 CPU threads)
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 xfce4-goodies depends on:
ii  mousepad 0.5.2-1
ii  notification-daemon  3.20.0-4
ii  ristretto0.10.0-1
ii  thunar-archive-plugin0.4.0-2
ii  thunar-media-tags-plugin 0.3.0-2
ii  xfburn   0.6.2-1
ii  xfce4-battery-plugin 1.1.3-1
ii  xfce4-clipman-plugin 2:1.6.1-1
ii  xfce4-cpufreq-plugin 1.2.4-1
ii  xfce4-cpugraph-plugin1.2.1-1
ii  xfce4-datetime-plugin0.8.1-1
ii  xfce4-dict   0.8.4-1
ii  xfce4-diskperf-plugin2.6.3-1
ii  xfce4-fsguard-plugin 1.1.2-1
ii  xfce4-genmon-plugin  4.1.1-1
ii  xfce4-mailwatch-plugin   1.3.0-1
ii  xfce4-netload-plugin 1.3.2-1
ii  xfce4-notifyd [notification-daemon]  0.6.2-1
ii  xfce4-places-plugin  1.8.1-1
ii  xfce4-screenshooter  1.9.8-1
ii  xfce4-sensors-plugin 1.3.0-3
ii  xfce4-smartbookmark-plugin   0.5.2-1
ii  xfce4-systemload-plugin  1.2.4-1
ii  xfce4-taskmanager1.4.0-1
ii  xfce4-terminal   0.8.10-1
ii  xfce4-timer-plugin   1.7.1-1
ii  xfce4-verve-plugin   2.0.1-1
ii  xfce4-wavelan-plugin 0.6.2-1
ii  xfce4-weather-plugin 0.11.0-1
ii  xfce4-whiskermenu-plugin 2.5.3-1
ii  xfce4-xkb-plugin 1:0.8.2-1

Versions of packages xfce4-goodies recommends:
ii  xfce4-power-manager  4.16.0-1

Versions of packages xfce4-goodies suggests:
pn  gigolo  
pn  parole  
pn  xfce4-indicator-plugin  
pn  xfce4-mpc-plugin
pn  xfce4-notes-plugin  
pn  xfce4-radio-plugin  

-- no debconf information

Bug#1008059: systemd-timesyncd restarted on every router advertisment

[Adam Dinwoodie]

On Mon, Mar 21, 2022 at 07:24:54PM +, Adam Dinwoodie wrote:
> On Mon, Mar 21, 2022 at 05:57:10PM +0100, Michael Biebl wrote:
> > Control: reassign dhcpcd5
> > 
> > Am 21.03.22 um 17:39 schrieb Michael Biebl:
> > > 
> > > Am 21.03.22 um 17:36 schrieb Michael Biebl:
> > > 
> > > > Is that a result of /etc/dhcp/dhclient-exit-hooks.d/timesyncd ?
> > > > 
> > > > What happens if you remove that dhclient hook
> > > 
> > > 
> > > Actually, I think it might be
> > > dhcpcd5: /lib/dhcpcd/dhcpcd-hooks/64-timesyncd.conf
> > > 
> > > which triggers the service restart, i.e. it would be a dhcpcd5 issue.
> > 
> > Reassigning accordingly.
> > 
> > # cat /lib/dhcpcd/dhcpcd-hooks/64-timesyncd.conf
> > # vi: ft=sh
> > 
> > SERVERFILE_IPV4="/run/systemd/timesyncd.conf.d/01-dhcpcd.ipv4.$interface.conf"
> > SERVERFILE_IPV6="/run/systemd/timesyncd.conf.d/01-dhcpcd.ipv6.$interface.conf"
> > 
> > reload_config() {
> > systemctl try-restart systemd-timesyncd.service || :
> > }
> 
> Fantastic, thank you!  I've confirmed that replacing that line with a
> simple `:` stops this behaviour.

And I think I've found the bug: the `add_servers` function in
60-ntp-common.conf attempts to work out if it needs to rebuild the
server file, and only actually rebuild and reload the configuration if
it's necessary.  But the test it uses doesn't work when there are no
configured NTP servers, such as because someone is using SNTP with
systemd-timesyncd and the default Debian time server.

I think the patch below should resolve this:

diff -ur old/60-ntp-common.conf new/60-ntp-common.conf
--- old/debian/hooks/60-ntp-common.conf 2022-03-21 19:49:03.518699860 +
+++ new/debian/hooks/60-ntp-common.conf 2022-03-21 19:51:32.216039388 +
@@ -3,6 +3,8 @@
 add_servers() {
if [ -f "$SERVERFILE" ] && [ "$new_ntp_servers" = "$old_ntp_servers" ]; 
then
return
+   elif [ ! -f "$SERVERFILE" ] && [ -z "$new_ntp_servers" ]; then
+   return
fi
 
rm -f "$SERVERFILE"

Bug#1008059: systemd-timesyncd restarted on every router advertisment

[Adam Dinwoodie]

On Mon, Mar 21, 2022 at 05:57:10PM +0100, Michael Biebl wrote:
> Control: reassign dhcpcd5
> 
> Am 21.03.22 um 17:39 schrieb Michael Biebl:
> > 
> > Am 21.03.22 um 17:36 schrieb Michael Biebl:
> > 
> > > Is that a result of /etc/dhcp/dhclient-exit-hooks.d/timesyncd ?
> > > 
> > > What happens if you remove that dhclient hook
> > 
> > 
> > Actually, I think it might be
> > dhcpcd5: /lib/dhcpcd/dhcpcd-hooks/64-timesyncd.conf
> > 
> > which triggers the service restart, i.e. it would be a dhcpcd5 issue.
> 
> Reassigning accordingly.
> 
> # cat /lib/dhcpcd/dhcpcd-hooks/64-timesyncd.conf
> # vi: ft=sh
> 
> SERVERFILE_IPV4="/run/systemd/timesyncd.conf.d/01-dhcpcd.ipv4.$interface.conf"
> SERVERFILE_IPV6="/run/systemd/timesyncd.conf.d/01-dhcpcd.ipv6.$interface.conf"
> 
> reload_config() {
>   systemctl try-restart systemd-timesyncd.service || :
> }

Fantastic, thank you!  I've confirmed that replacing that line with a
simple `:` stops this behaviour.

Bug#1008059: systemd-timesyncd restarted on every router advertisment

[Adam Dinwoodie]

Package: systemd-timesyncd
Version: 250.4-1
Severity: normal
Tags: ipv6

Dear Maintainer,

I'm seeing systemd restart systemd-timesyncd.service approximately every
10 seconds, lining up with when I see a log showing that my router has
advertised its IPv6 address.

If I run `journalctl -f`, the output is full of lines like the
following:

```
Mar 21 15:53:56 lucy.dinwoodie.org dhcpcd[452]: eth0: Router Advertisement from 
fe80::be99:11ff:fe69:4300
Mar 21 15:53:57 lucy.dinwoodie.org systemd[1]: Stopping Network Time 
Synchronization...
Mar 21 15:53:57 lucy.dinwoodie.org systemd[1]: systemd-timesyncd.service: 
Deactivated successfully.
Mar 21 15:53:57 lucy.dinwoodie.org systemd[1]: Stopped Network Time 
Synchronization.
Mar 21 15:53:57 lucy.dinwoodie.org systemd[1]: Starting Network Time 
Synchronization...
Mar 21 15:53:57 lucy.dinwoodie.org systemd[1]: Started Network Time 
Synchronization.
Mar 21 15:53:57 lucy.dinwoodie.org systemd-timesyncd[6426]: Initial 
synchronization to time server 162.159.200.1:123 (0.debian.pool.ntp.org).
Mar 21 15:54:06 lucy.dinwoodie.org dhcpcd[452]: eth0: Router Advertisement from 
fe80::be99:11ff:fe69:4300
Mar 21 15:54:07 lucy.dinwoodie.org systemd[1]: Stopping Network Time 
Synchronization...
Mar 21 15:54:07 lucy.dinwoodie.org systemd[1]: systemd-timesyncd.service: 
Deactivated successfully.
Mar 21 15:54:07 lucy.dinwoodie.org systemd[1]: Stopped Network Time 
Synchronization.
Mar 21 15:54:07 lucy.dinwoodie.org systemd[1]: Starting Network Time 
Synchronization...
Mar 21 15:54:07 lucy.dinwoodie.org systemd[1]: Started Network Time 
Synchronization.
Mar 21 15:54:07 lucy.dinwoodie.org systemd-timesyncd[6463]: Initial 
synchronization to time server 178.62.18.76:123 (0.debian.pool.ntp.org).
```

There's no great immediate impact, but it seems like this shouldn't be
happening.  And there is clearly some impact in terms of unnecessary
disk churn, unnecessary network usage, unnecessary load on NTP servers,
and -- still minor, but most relevant to my immediate interests --
ability to spot interesting logs in journald.

Some searching online led me to a very old systemd bug[0], but that was
apparently resolved in systemd 219, so definitely shouldn't be relevant
now.

[0]: https://bugs.freedesktop.org/show_bug.cgi?id=87505

Other searches pointed me to other people reporting similar
problems[1][2] with no resolution. It's possibly of interest is that
they're all folk (like me) running on a Raspberry Pi.  At least in my
case, however, I understand the only difference between what I'm running
and a regular arm64 Debian installation is that there are a few driver
and firmware packages shipped from the Raspberry Pi Foundation.
Certainly all the systemd packages I'm using have come straight from
deb.debian.org repositories.

[1]: https://raspberrypi.stackexchange.com/q/133605/145463
[2]: https://forums.raspberrypi.com/viewtopic.php?t=324473

Given that, I suspect whatever the issue is may be due to one or more of
(a) folks using Raspberry Pis are going to be running an arm-based
architecture, or (b) folks using Pis are more likely to be running very
minimal Debian installations, so are more likely to have not installed
packages that might not be listed as dependencies but whose absence
causes non-obvious problems.

Admittedly there's also (c) there's something up with the config that's
used on Raspberry Pis by default, but I've done my best to rule that
out: I can't see anything in the documentation for dhcpcd,
systemd-networkd or systemd-timesyncd that would cause this behaviour,
nor anything in any of the configuration in /etc/systemd/.

I'm seeing this behaviour on /bullseye (247.3-6), /bullseye-backports
(250.4-1~bpoll+1), and /sid (250.4-1).

-- System Information:
Debian Release: 11.2
  APT prefers stable-updates
  APT policy: (990, 'stable-updates'), (990, 'stable-security'), (990, 
'stable'), (850, 'testing'), (500, 'unstable')
Architecture: arm64 (aarch64)
Foreign Architectures: armhf

Kernel: Linux 5.10.103-v8+ (SMP w/4 CPU threads; PREEMPT)
Kernel taint flags: TAINT_CRAP
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages systemd-timesyncd depends on:
ii  adduser  3.118
ii  libc62.33-7
ii  systemd  250.4-1

systemd-timesyncd recommends no packages.

systemd-timesyncd suggests no packages.

-- no debconf information

Bug#1007990: rsync: Cosmetic bug in rsync man page --stop-after and --stop-at options

[Adam Dinwoodie]

Package: rsync
Version: 3.2.3-8
Severity: minor

Dear Maintainer,

There seems to be a cosmetic error in the full description of the
--stop-after and --stop-at options in the rsync man page, where the
options are prepended by backticks and aren't shown in bold.

For a simple reproduction, you can run the following line:

man rsync | sed -n '/^OPTIONS/,${/--stop-after/,/--only-write-batch/p}'

On my system, this shows as follows (extraneous bits trimmed):

   `--stop-after=MINS
  This option tells rsync to ...


   `--stop-at=y-m-dTh:m
  This option tells rsync to ...

   --write-batch=FILE
  Record a file that can later ...

Note the first two options have backticks at the front, where the third
doesn't.  The third format is what I would expect, and is how all the
other options in this manpage are shown too.

Kind regards,

Adam

-- System Information:
Debian Release: 11.2
  APT prefers stable-updates
  APT policy: (990, 'stable-updates'), (990, 'stable-security'), (990, 
'stable'), (850, 'testing'), (500, 'unstable')
Architecture: arm64 (aarch64)
Foreign Architectures: armhf

Kernel: Linux 5.10.103-v8+ (SMP w/4 CPU threads; PREEMPT)
Kernel taint flags: TAINT_CRAP
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages rsync depends on:
ii  init-system-helpers  1.60
ii  libacl1  2.2.53-10
ii  libc62.33-7
ii  liblz4-1 1.9.3-2
ii  libpopt0 1.18-2
ii  libssl1.11.1.1k-1+deb11u2+rpt1
ii  libxxhash0   0.8.0-2
ii  libzstd1 1.4.8+dfsg-2.1
ii  lsb-base 11.1.0
ii  zlib1g   1:1.2.11.dfsg-2

rsync recommends no packages.

Versions of packages rsync suggests:
ii  openssh-client  1:8.4p1-5
ii  openssh-server  1:8.4p1-5
ii  python3 3.9.2-3

-- no debconf information

Bug#1004382: /usr/bin/reportbug: Bogus "please wait to receive the bug tracking number" when not sending in paranoid mode

[Adam Dinwoodie]

Package: reportbug
Version: 11.3.0
Severity: minor
File: /usr/bin/reportbug

Dear Maintainer,

When using reportbug in paranoid mode (or at least with "ui urwid" and
"paranoid" specified in ~/.reportbugrc), reportbug correctly displays
the email to the user before sending it, and asks the user if the report
is satisfactory.  If the user objects to the message, as well as
accurately reporting that the message has been saved to a temporary
file, reportbug also tells the user:

> If you want to provide additional information, please wait to receive
> the bug tracking number via email; you may then send any extra
> information to ...

This implies -- incorrectly -- that the bug report has been sent and
that the user should expect to receive a bug tracking number.  In this
circumstance, reportbug should not show this message.

Kind regards,

Adam


-- Package-specific info:
** Environment settings:
EDITOR="vim"
VISUAL="vim"
INTERFACE="urwid"

** /home/adam/.reportbugrc:
reportbug_version "7.10.3+deb11u1"
mode standard
ui urwid
email "debian-report...@post.dinwoodie.org"
paranoid

-- System Information:
Debian Release: 11.2
  APT prefers stable
  APT policy: (990, 'stable'), (500, 'unstable'), (500, 'testing'), (1, 
'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 5.10.0-10-cloud-amd64 (SMP w/2 CPU threads)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.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 reportbug depends on:
ii  apt2.2.4
ii  python33.9.2-3
ii  python3-reportbug  11.3.0
ii  sensible-utils 0.0.14

reportbug recommends no packages.

Versions of packages reportbug suggests:
pn  claws-mail 
ii  debconf1.5.77
ii  debsums3.0.2
ii  dlocate1.07+nmu1
pn  emacs-bin-common   
ii  exim4-daemon-light [mail-transport-agent]  4.94.2-7
ii  file   1:5.39-3
pn  gnupg | pgp
ii  python3-urwid  2.1.2-1
pn  reportbug-gtk  
ii  xdg-utils  1.1.3-4.1

Versions of packages python3-reportbug depends on:
ii  apt2.2.4
ii  file   1:5.39-3
ii  python33.9.2-3
ii  python3-apt2.2.1
ii  python3-debian 0.1.43
ii  python3-debianbts  3.2.0
ii  python3-requests   2.25.1+dfsg-2
ii  sensible-utils 0.0.14

python3-reportbug suggests no packages.

-- no debconf information

Bug#1004339: /usr/bin/systemctl: `systemctl start --user --wait` fails with "Failed to connect to bus: No such file or directory"

[Adam Dinwoodie]

On Tue, Jan 25, 2022 at 06:04:37PM +0100, Michael Biebl wrote:
> 
> Control: tags -1 + moreinfo unreproducible
> 
> Am 25.01.22 um 13:13 schrieb Adam Dinwoodie:
> 
> > 
> >  Failed to connect to bus: No such file or directory
> > 
> 
> Thanks for the reproducer.
> I can't reproduce the issue with the instructions you provided (with v250
> from sid).
> 
> Your problem seems to be related to a missing dbus (user) bus in your ssh
> session and the failing --wait is just a symptom.
> 
> Can you run busctl --user, systemctl --user status dbus.socket dbus.service
> ?
> 
> Is dbus-user-session installed? Is libpam-systemd enabled?

That was it: I'm running a fairly minimal headless system, and didn't
have dbus-user-session installed.  After installing that package, my
reproduction script behaves as expected.

Mea culpa.  Thank you for the help!

Bug#1004339: /usr/bin/systemctl: `systemctl start --user --wait` fails with "Failed to connect to bus: No such file or directory"

[Adam Dinwoodie]

Package: systemd
Version: 250.3-1
Severity: normal
File: /usr/bin/systemctl

Dear Maintainer,

According to the systemctl.1 man page, it should be possible to specify
`--wait` to systemctl commands that will start units, to have the
systemctl command block until the units terminate again.  This seems to
work as expected for system units, but not for user units.

The attached short script provides a simple test case: given appropriate
ssh configuration, when run with `sudo bash test.sh` it will create a
new user called "test" with a simple example service template unit, then
log in through using ssh to start that unit twice, once without
`--wait`, and once with.  Expected behaviour is for this script to
start both unit instances, with the second one sleeping before the
script finishes.  Actual behaviour is that the first unit starts as
expected, but the second unit is never started, and the attempt gives a
return code of 1 and the following error printed to the terminal:

Failed to connect to bus: No such file or directory

As I say, the `--wait` function works as expected for system units; it's
only with user units that it seems to fail.

Kind regards,

Adam

-- Package-specific info:

-- System Information:
Debian Release: 11.2
  APT prefers stable
  APT policy: (990, 'stable'), (500, 'unstable'), (500, 'testing'), (1, 
'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 5.10.0-10-cloud-amd64 (SMP w/2 CPU threads)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.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 systemd depends on:
ii  adduser  3.118
ii  libacl1  2.2.53-10
ii  libapparmor1 2.13.6-10
ii  libaudit11:3.0-2
ii  libblkid12.36.1-8
ii  libc62.33-3
ii  libcap2  1:2.44-1
ii  libcrypt11:4.4.18-4
ii  libcryptsetup12  2:2.4.3-1
ii  libfdisk12.36.1-8
ii  libgcrypt20  1.9.4-5
ii  libgnutls30  3.7.2-5
ii  libgpg-error01.38-2
ii  libip4tc21.8.7-1
ii  libkmod2 28-1
ii  liblz4-1 1.9.3-2
ii  liblzma5 5.2.5-2
ii  libmount12.36.1-8
ii  libpam0g 1.4.0-9+deb11u1
ii  libseccomp2  2.5.1-1+deb11u1
ii  libselinux1  3.1-3
ii  libsystemd0  250.3-1
ii  libzstd1 1.4.8+dfsg-2.1
ii  mount2.36.1-8
ii  util-linux   2.36.1-8

Versions of packages systemd recommends:
ii  dbus [default-dbus-system-bus]   1.12.20-2
ii  systemd-timesyncd [time-daemon]  250.3-1

Versions of packages systemd suggests:
ii  libfido2-11.6.0-2
pn  libtss2-esys-3.0.2-0  
pn  libtss2-mu0   
pn  libtss2-rc0   
pn  policykit-1   
pn  systemd-container 

Versions of packages systemd is related to:
pn  dracut   
ii  initramfs-tools  0.140
pn  libnss-systemd   
ii  libpam-systemd   250.3-1
ii  udev 247.3-6

-- no debconf information
set -eu
useradd test
mkdir -p ~test/.config/systemd/user
cat <<'EOF' >~test/.config/systemd/user/sleep@.service
[Service]
ExecStart=sleep %I
EOF
mkdir -p ~test/.ssh
cp ~/.ssh/id_rsa.pub ~test/.ssh/authorized_keys
chown -R test:test ~test
ssh test@localhost 'systemctl --user start sleep@5.service'
ssh test@localhost 'systemctl --user status sleep@5.service'
ssh test@localhost 'systemctl --user start --wait sleep@6.service' || echo 
"Error: rc=$?"
ssh test@localhost 'systemctl --user status sleep@6.service'

Bug#1004217: /bin/systemctl: Cannot enable units where the Install section is in a truncated override file

[Adam Dinwoodie]

On Sun, Jan 23, 2022 at 09:38:17AM +0100, Michael Biebl wrote:
> 
> Control: tags -1 + upstream
> 
> Am 23.01.22 um 00:04 schrieb Adam Dinwoodie:
> > Package: systemd
> > Version: 249.7-1+rpi1
> > Severity: normal
> > File: /bin/systemctl
> > 
> > Dear Maintainer,
> > 
> > If one creates a unit with a name like `test-test.service`, one can put
> > override files in the drop-in directory with the truncated name
> > `test-.service.d`, and have them be picked up by systemd, at least for
> > the most part.  However, it appears that `systemctl enable` does not
> > respect these files.
> 
> Seems like a valid issue.
> As we do not ship any Debian specific modifications in that regard, it would
> be great if you can file this issue upstream at
> https://github.com/systemd/systemd/issues
> as it should be handled there.

Now reported at https://github.com/systemd/systemd/issues/22230.  Thank
you!

Bug#1004217: /bin/systemctl: Cannot enable units where the Install section is in a truncated override file

[Adam Dinwoodie]

Package: systemd
Version: 249.7-1+rpi1
Severity: normal
File: /bin/systemctl

Dear Maintainer,

If one creates a unit with a name like `test-test.service`, one can put
override files in the drop-in directory with the truncated name
`test-.service.d`, and have them be picked up by systemd, at least for
the most part.  However, it appears that `systemctl enable` does not
respect these files.

See the below simple test case, with a unit file and override file:

```
$ systemctl --user cat test-test.service
# /home/test/.config/systemd/user/test-test.service
[Service]
ExecStart=sleep 5000d

# /home/test/.config/systemd/user/test-.service.d/override.conf
[Install]
WantedBy=default.target

$ systemctl --user status test-test.service
○ test-test.service
 Loaded: loaded (/home/test/.config/systemd/user/test-test.service; static)
Drop-In: /home/test/.config/systemd/user/test-.service.d
 └─override.conf
 Active: inactive (dead)

$ systemctl --user enable test-test.service
The unit files have no installation config (WantedBy=, RequiredBy=, Also=,
Alias= settings in the [Install] section, and DefaultInstance= for template
units). This means they are not meant to be enabled using systemctl.

Possible reasons for having this kind of units are: 
```

Clearly `systemctl cat` was able to locate the override file above, and
therefore I had expected `systemctl enable` to take note of the override
file's [Install] section.  That would mean that `systemctl enable` would
actually create a symlink from default.target.wants/test-test.service to
test-test.service.

At the very least, if this were expected behaviour (and it doesn't seem
grossly unreasonable; I know I was doing something unusual to hit
this!), I would have expected to see it mentioned in the paragraph about
drop-in directories, and/or the section on "[Install] Section Options"
in the systemd.unit(5) man page.

Kind regards,

Adam

-- Package-specific info:

-- System Information:
Distributor ID: Raspbian
Description:Raspbian GNU/Linux 11 (bullseye)
Release:11
Codename:   bullseye
Architecture: armv7l

Kernel: Linux 5.10.92-v7l+ (SMP w/4 CPU threads)
Kernel taint flags: TAINT_CRAP
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages systemd depends on:
ii  adduser  3.118
ii  libacl1  2.2.53-10
ii  libapparmor1 2.13.6-10
ii  libaudit11:3.0-2
ii  libblkid12.36.1-8
ii  libc62.32-4+rpi1
ii  libcap2  1:2.44-1
ii  libcrypt11:4.4.18-4
ii  libcryptsetup12  2:2.4.3-1
ii  libgcrypt20  1.9.4-5
ii  libgnutls30  3.7.2-5
ii  libgpg-error01.38-2
ii  libip4tc21.8.7-1
ii  libkmod2 28-1
ii  liblz4-1 1.9.3-2
ii  liblzma5 5.2.5-2
ii  libmount12.36.1-8
ii  libpam0g 1.4.0-9+deb11u1
ii  libseccomp2  2.5.1-1+rpi1+deb11u1
ii  libselinux1  3.1-3
ii  libsystemd0  249.7-1+rpi1
ii  libzstd1 1.4.8+dfsg-2.1+rpi1
ii  mount2.36.1-8
ii  util-linux   2.36.1-8

Versions of packages systemd recommends:
ii  dbus [default-dbus-system-bus]   1.12.20-2
ii  systemd-timesyncd [time-daemon]  249.7-1+rpi1

Versions of packages systemd suggests:
pn  policykit-1
pn  systemd-container  

Versions of packages systemd is related to:
pn  dracut   
ii  initramfs-tools  0.140
ii  libnss-systemd   249.7-1+rpi1
ii  libpam-systemd   249.7-1+rpi1
ii  udev 247.3-6+rpi1

-- no debconf information

Bug#1004129: /usr/bin/gcalcli: Multi-day event not shown for all days in `gcalcli calm`

[Adam Dinwoodie]

Package: gcalcli
Version: 4.3.0-1
Severity: normal
File: /usr/bin/gcalcli

Dear Maintainer,

I have found that multi-day events do not reliably show up on all days
when running `gcalcli calm` or `gcalcli calw`.

As a simple example, the attached `calm.out` file was generated by running
`gcalcli --nocache --calendar=Test calm August >calm`.  This should show
a single event running 8-15 August 2022, but as you can see from the
attached output files, the event is shown as being present on 8-13
August and 15 August, but not on Sunday 14 August.

Because the attached `calm.out` output contains escape sequences, I've
also attached `calm.txt`, which contains a copy-paste of the displayed
content from my terminal, and therefore no escape codes.

The "Test" calendar referenced only has a single event, a multi-day, all
day event titled "Test event".  It is publically available (at least at
time of writing) at [0].  I've also attached the output of `gcalcli
--nocolor --nocache --calendar=Test agenda --details=calendar
--details=length --details=url 2022-08-01 2022-08-31`, which I believe
should have all the details necessary for someone else to create an
identical test calendar and event.

[0]: 
https://calendar.google.com/calendar/embed?src=c_701nljt1vjvj5vattsc0q8b264%40group.calendar.google.com=Europe%2FLondon

-- System Information:
Distributor ID: Raspbian
Description:Raspbian GNU/Linux 11 (bullseye)
Release:11
Codename:   bullseye
Architecture: armv7l

Kernel: Linux 5.10.63-v7l+ (SMP w/4 CPU threads)
Kernel taint flags: TAINT_CRAP
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages gcalcli depends on:
ii  python33.9.2-3
ii  python3-dateutil   2.8.1-6
ii  python3-googleapi  1.7.11-4
ii  python3-httplib2   0.18.1-3
ii  python3-oauth2client   4.1.2-7
ii  python3-parsedatetime  2.6-1
ii  python3-six1.16.0-2

Versions of packages gcalcli recommends:
ii  python3-vobject  0.9.6.1-0.2

gcalcli suggests no packages.

-- no debconf information


calm.out
Description: Binary data
┌┐
│August 2022 │
├──┬──┬──┬──┬──┬──┬──┤
│Sunday│Monday│Tuesday   │Wednesday │Thursday  │Friday│Saturday  │
├──┼──┼──┼──┼──┼──┼──┤
│  │01│02│03│04│05│06│
│  │  │  │  │  │  │  │
├──┼──┼──┼──┼──┼──┼──┤
│07│08│09│10│11│12│13│
│  │  │  │  │  │  │  │
│  │Test event│Test event│Test event│Test event│Test event│Test event│
│  │  │  │  │  │  │  │
├──┼──┼──┼──┼──┼──┼──┤
│14│15│16│17│18│19│20│
│  │  │  │  │  │  │  │
│  │Test event│  │  │  │  │  │
│  │  │  │  │  │  │  │
├──┼──┼──┼──┼──┼──┼──┤
│21│22│23│24│25│26│27│
│  │  │  │  │  │  │  │
├──┼──┼──┼──┼──┼──┼──┤
│28│29│30│31│  │  │  │
│  │  │  │  │  │  │  │
└──┴──┴──┴──┴──┴──┴──┘

Mon Aug 08 Test event
 Calendar: Test
 Link: 
https://www.google.com/calendar/event?eid=NjlwZDI4OHNqc3ZtbTRqY2E3YzlzdGMwa2sgY183MDFubGp0MXZqdmo1dmF0dHNjMHE4YjI2NEBn
 Length: 8 days, 0:00:00

Bug#1003954: keepassxc: Break out keepassxc-cli into a separate package

[Adam Dinwoodie]

Package: keepassxc
Severity: wishlist

Dear Maintainer,

The keepassxc package includes a significant number of dependencies to
allow using the windowed password manager.  This seems unnecessary for
folk (like me) who want to use keepassxc-cli on a machine that normally
only provides SSH CLI access and doesn't have any desktop environment.

As such, I'd like to request that keepassxc-cli be broken out into a
separate package that can be installed without pulling in any of the
graphical package requirements.

Kind regards,

Adam

-- System Information:
Distributor ID: Raspbian
Description:Raspbian GNU/Linux 11 (bullseye)
Release:11
Codename:   bullseye
Architecture: armv7l

Kernel: Linux 5.10.63-v7l+ (SMP w/4 CPU threads)
Kernel taint flags: TAINT_CRAP
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages keepassxc depends on:
ii  libargon2-1   0~20171227-0.2
ii  libc6 2.32-4+rpi1
ii  libgcc-s1 10.2.1-6+rpi1
ii  libgcrypt20   1.8.7-6
pn  libqrencode4  
pn  libqt5concurrent5 
pn  libqt5core5a  
pn  libqt5dbus5   
pn  libqt5gui5 | libqt5gui5-gles  
pn  libqt5network5
pn  libqt5svg5
pn  libqt5widgets5
pn  libqt5x11extras5  
pn  libquazip5-1  
pn  libsodium23   
ii  libstdc++610.2.1-6+rpi1
pn  libx11-6  
pn  libxi6
pn  libxtst6  
pn  libykpers-1-1 
pn  libzxcvbn0
ii  zlib1g1:1.2.11.dfsg-2

Versions of packages keepassxc recommends:
pn  fonts-font-awesome  

Versions of packages keepassxc suggests:
pn  webext-keepassxc-browser  
pn  xclip 

Bug#1003774: bind9-host: Incorrect formatting in host.1 man page

[Adam Dinwoodie]

Package: bind9-host
Version: 1:9.17.21-1
Severity: minor
Tags: patch

Dear Maintainer,

The man page at host.1 in this package has an error in the formatting
for the description of the `-l` option; for me it renders as below (I've
added *s to indicate the bits in bright white):

This option tells *named` to list the zone, meaning the ``host*
command performs a zone ...

I rather suspect it should instead be rendered as below:

This option tells *named* to list the zone, meaning the *host*
command performs a zone ...

I've verified that the attached patch resolves this.

-- System Information:
Distributor ID: Raspbian
Description:Raspbian GNU/Linux 11 (bullseye)
Release:11
Codename:   bullseye
Architecture: armv7l

Kernel: Linux 5.10.63-v7l+ (SMP w/4 CPU threads)
Kernel taint flags: TAINT_CRAP
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages bind9-host depends on:
ii  bind9-libs  1:9.17.21-1
ii  libc6   2.32-4+rpi1
ii  libidn2-0   2.3.0-5

bind9-host recommends no packages.

bind9-host suggests no packages.

-- no debconf information
diff --git a/doc/man/host.1in b/doc/man/host.1in
index 4d419423e..a94f12ae0 100644
--- a/doc/man/host.1in
+++ b/doc/man/host.1in
@@ -77,7 +77,7 @@ found for the zone.
 This option prints debugging traces, and is equivalent to the \fB\-v\fP 
verbose option.
 .TP
 .B \fB\-l\fP
-This option tells \fBnamed\(ga to list the zone, meaning the \(ga\(gahost\fP 
command performs a zone transfer of zone
+This option tells \fBnamed\fP to list the zone, meaning the \fBhost\fP command 
performs a zone transfer of zone
 \fBname\fP and prints out the NS, PTR, and address records (A/).
 .sp
 Together, the \fB\-l \-a\fP options print all records in the zone.

Bug#1003220: at: Cannot create job to run at a time in the past

[Adam Dinwoodie]

Package: at
Version: 3.2.2-1
Severity: normal

Dear Maintainer,

According to the man page, "If you specify a job to absolutely run at a
specific time and date in the past, the job will run as soon as
possible.  For example, if it is 8pm and you do a `at 6pm today`, it
will run more likely at 8:05pm."

However, when one attempts to do this in practice, the command fails
with an error "refusing to create job destined in the past":

```
$ date; echo echo test | at '13:00 today'
Thu  6 Jan 13:49:42 GMT 2022
at: refusing to create job destined in the past
```

I had expected the above commands to successfully create a job, run the
command "echo test" immediately, then immediately email me the output
(i.e. an email that just contains the word "test").

-- System Information:
Debian Release: 11.2
  APT prefers stable
  APT policy: (990, 'stable'), (500, 'unstable'), (500, 'testing'), (1, 
'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 5.10.0-10-cloud-amd64 (SMP w/2 CPU threads)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.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 at depends on:
ii  libc6   2.33-1
ii  libpam-runtime  1.4.0-9+deb11u1
ii  libpam0g1.4.0-9+deb11u1
ii  libselinux1 3.1-3
ii  lsb-base11.1.0

Versions of packages at recommends:
ii  exim4-daemon-light [mail-transport-agent]  4.94.2-7

at suggests no packages.

-- Configuration Files:
/etc/at.deny [Errno 13] Permission denied: '/etc/at.deny'

-- no debconf information

Bug#1001863: adduser: EXCLUDE_FSTYPES not respected with --remove-all-files

[Adam Dinwoodie]

Package: adduser
Version: 3.118
Severity: normal

Dear Maintainer,

When deleting a user with `--remove-all-files`, I have seen the script
take an inordinately long time, and investigating with `lsof` I found it
was descending into rclone mounts, despite having disable this in the
deluser.conf file, because I had expected traversing those mounts to be
both pointless and slow.

Looking at the perl script, it looks like the set of mounts to descend
or not descend into is built as `@mountpoints`, and a bit of
print-debugging indicated that these mounts weren't being added to the
array, as expected.  However, it looks like `@mountpoints` is only
actually referenced in the block for `sub home_match`; it's not used in
`sub find_match`, which is the one that's invoked when removing all
files rather than just home directories.

At least by my reading of deluser.conf, this isn't expected, and the
`EXCLUDE_FSTYPES` configuration should affect both runs with
`--remove-home` and `--remove-all-files`.

-- System Information:
Distributor ID: Raspbian
Description:Raspbian GNU/Linux 11 (bullseye)
Release:11
Codename:   bullseye
Architecture: armv7l

Kernel: Linux 5.10.63-v7l+ (SMP w/4 CPU threads)
Kernel taint flags: TAINT_CRAP
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages adduser depends on:
ii  debconf [debconf-2.0]  1.5.77
ii  passwd 1:4.8.1-1

adduser recommends no packages.

Versions of packages adduser suggests:
ii  liblocale-gettext-perl  1.07-4+b1
ii  perl5.32.1-4+deb11u2

-- Configuration Files:
/etc/deluser.conf changed:
REMOVE_HOME = 0
REMOVE_ALL_FILES = 0
BACKUP = 0
BACKUP_TO = "."
ONLY_IF_EMPTY = 0
EXCLUDE_FSTYPES = "(proc|sysfs|usbfs|devpts|tmpfs|afs|fuse.rclone)"


-- debconf information:
* adduser/homedir-permission: true
  adduser/title: