Bug#904044: Fwd: openvpn3-client_21+dfsg-1_amd64.changes REJECTED

[Marc Leeman]

-- Forwarded message -
From: Bastian Blank 
Date: Tue, 9 Apr 2024 at 13:00
Subject: openvpn3-client_21+dfsg-1_amd64.changes REJECTED
To: Marc Leeman , 



Hi

There are two license inompatibilities:
(A)GPL-3 and BSD-4-Clause-UC are incompatible (yes, I saw the comment,
but this makes the license either a custom one or possibly a
BSD-3-Clause)
GPL-2 and AGPL-3 are incompatible

AGPL is not suitable for non-network code, so at least debian/* should
get something else.

Your lintian overrides don't match what ftp-master still expects, see
all the errors.

The polkit maintainer just asked to reject new packages for shipping
legacy polkit pkla files.  So please remove the stuff from
/var/lib/polkit-1 and convert to the new-style rules.

Please drop all autoconf/automake generated and vendored files.  We've
just seen what this produces as problems.

There is vendored code, but also a dependency on the same library
(libasio-dev).

Some other remarks:
- Please use dh_installtmpfiles (rename debian/openvpn3-client.conf to
  .tmpfiles I think), enabled in debhelper compat 13
- You could use debhelper compat 14 directly and avoid some of the
  overrides in debian/rules, as it calls dh_installsysusers
- Preemptive architecture limits are not the way to go, please remove
  this list
- It contains DSA keys in /etc/openvpn3/awscerts, which a current crypto
  policy should not really accept
- There seems to be two distinct was to start it,
  openvpn3-autoload.service and openvpn3-session@.service, is this
  necessary?
- /var is not really for user config, but for state.
- Is /var/lib/openvpn3 supposed to be in the package or created via
  systemd-tmpfiles?  Currently I see both.



===

Please feel free to respond to this email if you don't understand why
your files were rejected, or if you upload new files which address our
concerns.



-- 
g. Marc

GPG: 827C FD74 BA46 8152 A041 F3A0 7A6A 4F17 5995 A65B


noname
Description: PGP signature

Bug#1073513: upower: syscall architecture mismatch

[Marc Lehmann]

Package: upower
Version: 0.99.20-2
Severity: normal

Dear Maintainer,

when I install upower:i386 on my amd64 system, it just crashes.

The reason is thos bogus line in the service file:

   SystemCallArchitectures=native

This only allows syscalls of the same architecture as system, which is not
the correct architecture for for upower binary (in this case, upower is a
i386 binary, while systemd is amd64).

The line should either list the correct architecture for the package, or be 
removed.

-- System Information:
Debian Release: 12.5
  APT prefers stable-updates
  APT policy: (990, 'stable-updates'), (990, 'stable-security'), (990, 
'stable'), (500, 'unstable-debug'), (500, 'testing-debug'), (500, 
'oldstable-debug'), (500, 'unstable'), (500, 'testing'), (1, 
'experimental-debug'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386, x32

Kernel: Linux 6.1.0-21-amd64 (SMP w/28 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_USER, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
Locale: LANG=en_IE.UTF-8, LC_CTYPE=en_IE.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 upower depends on:
ii  dbus 1.14.10-1~deb12u1
ii  libc62.36-9+deb12u7
ii  libglib2.0-0 2.74.6-2+deb12u2
ii  libgudev-1.0-0   237-2
ii  libupower-glib3  0.99.20-2
ii  udev 252.22-1~deb12u1

Versions of packages upower recommends:
ii  polkitd  122-3

upower suggests no packages.

-- no debconf information

Bug#1071564: bookworm-pu: package aide/0.18.3-1+deb12u3

[Marc Haber]

On Sat, Jun 15, 2024 at 04:23:25PM +0100, Adam D. Barratt wrote:
> On Tue, 2024-05-21 at 12:00 +0200, Marc Haber wrote:
> > aide 0.18 has introduced some concurrency in processing. There is a
> > bug
> > that makes fail to concurrently read extended attributes (xattrs) due
> > to
> > variables shared between worker threads.
> 
> Please go ahead.

Uploaded!

Greetings
Marc

-- 
-----
Marc Haber | "I don't trust Computers. They | Mailadresse im Header
Leimen, Germany|  lose things."Winona Ryder | Fon: *49 6224 1600402
Nordisch by Nature |  How to make an American Quilt | Fax: *49 6224 1600421

Bug#1073291: Same issue reported in github

[Jean-Marc]

https://github.com/gnome-terminator/terminator/issues/920

--
Jean-Marc


OpenPGP_signature.asc
Description: OpenPGP digital signature

Bug#1073291: terminator: multiple "SyntaxWarning: invalid escape sequence" during upgrade

[Jean-Marc]

Package: terminator
Version: 2.1.4-1
Severity: normal
X-Debbugs-Cc: jean-m...@6jf.be

Dear Maintainer,

During today's upgrade from 2.1.3-1 to 2.1.4-1, I got multiple "SyntaxWarning: 
invalid escape
sequence" errors.

See details :

Paramétrage de terminator (2.1.4-1) ...
/usr/lib/python3/dist-packages/terminatorlib/plugins/maven.py:35: 
SyntaxWarning: invalid escape sequence '\-'
  maven_filters['apache_maven_plugin_artifact_id'] = 
'maven\-(%(apache_maven_plugin_shortname)s)\-plugin' % maven_filters
/usr/lib/python3/dist-packages/terminatorlib/plugins/maven.py:36: 
SyntaxWarning: invalid escape sequence '\-'
  maven_filters['codehaus_maven_plugin_artifact_id'] = 
'(%(codehaus_maven_plugin_shortname)s)\-maven\-plugin' % maven_filters
/usr/lib/python3/dist-packages/terminatorlib/plugins/maven.py:37: 
SyntaxWarning: invalid escape sequence '\.'
  maven_filters['maven_plugin_version'] = '[a-zA-Z0-9\.-]+'
/usr/lib/python3/dist-packages/terminatorlib/plugins/mousefree_url_handler.py:54:
 SyntaxWarning: invalid escape sequence '\:'
  searchtext  = "https?\:\/\/[^\s]+[\/\w]"
/usr/lib/python3/dist-packages/terminatorlib/plugins/url_handlers.py:16: 
SyntaxWarning: invalid escape sequence '\s'
  match = '\\b(lp|LP):?\s?#?[0-9]+(,\s*#?[0-9]+)*\\b'
/usr/lib/python3/dist-packages/terminatorlib/plugins/url_handlers.py:39: 
SyntaxWarning: invalid escape sequence '\+'
  match = 
'\\b((lp|LP):%(project)s(/%(series)s)?|(lp|LP):%(group)s/(%(project)s|\+junk)/%(branch)s)\\b'
 % lpfilters

Hope this will be helpfull.

Regards,

Jean-Marc


-- System Information:
Debian Release: trixie/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)

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

Versions of packages terminator depends on:
ii  gir1.2-glib-2.02.80.3-1
ii  gir1.2-gtk-3.0 3.24.42-1
ii  gir1.2-pango-1.0   1.54.0+ds-1
ii  gir1.2-vte-2.910.75.92-1
ii  gsettings-desktop-schemas  46.0-1
ii  python33.11.8-1
ii  python3-cairo  1.26.0-1
ii  python3-configobj  5.0.8-3
ii  python3-dbus   1.3.2-5+b2
ii  python3-gi 3.48.2-1
ii  python3-gi-cairo   3.48.2-1
ii  python3-psutil 5.9.8-2

Versions of packages terminator recommends:
ii  dbus-user-session [default-dbus-session-bus]  1.14.10-4+b1
ii  dbus-x11 [dbus-session-bus]   1.14.10-4+b1
ii  gir1.2-keybinder-3.0  0.3.2-1.1+b2
ii  gir1.2-notify-0.7 0.8.3-1+b1
ii  xdg-utils 1.1.3-4.1

terminator suggests no packages.

-- no debconf information

Bug#1029140: cron-apt refuses to run when RUNSLEEP is set

[Marc Haber]

On Tue, Jun 11, 2024 at 08:12:27PM +0200, Ola Lundqvist wrote:
> Certainly. If you know those I'm happy to fix them.
> 
> I thought I had fixed them all already.

The one that jumped to my mind is $RANDOM which doesnt work in dash.

I would recommend just using /bin/bash in the shebang line. At least
that's what I do since I'd rather not delve into those shell details too
deeply.

Greetings
Marc


-- 
-
Marc Haber | "I don't trust Computers. They | Mailadresse im Header
Leimen, Germany|  lose things."Winona Ryder | Fon: *49 6224 1600402
Nordisch by Nature |  How to make an American Quilt | Fax: *49 6224 1600421

Bug#1029140: cron-apt refuses to run when RUNSLEEP is set

[Marc Haber]

On Mon, Jun 10, 2024 at 11:02:30PM +0200, Ola Lundqvist wrote:
> Sorry, I meant to run with dash -x. Or do dash not have that option?

It has this option.

But I see a problem in cron-apt using bashisms while using the /bin/sh
shebang line. I don't know whether this have to do with this, bug, but
it should be fixed anyway.

Greetings
Marc

-- 
-----
Marc Haber | "I don't trust Computers. They | Mailadresse im Header
Leimen, Germany|  lose things."Winona Ryder | Fon: *49 6224 1600402
Nordisch by Nature |  How to make an American Quilt | Fax: *49 6224 1600421

Bug#1072568: exim4-config: Installation process of package exim4-config stop on error in post installation script. It complains about a error in config file. It reasons it by user mail not found.

[Marc Haber]

On Tue, Jun 04, 2024 at 02:51:45PM +0200, m.alfa...@gmail.com wrote:
> During the postintallation script the apt report that theres a error in
> config file /var/lib/exim4/config.autogenerated.tmp on line 681. Next message
> is that the "user mail was not found". Which result in exit status 1 of dpkg 
> in config phase.

The user mail should be present on ALL debian systems, by virtue of the
package base-passwd which is an essential package.

How did your user mail get removed?

Greetings
Marc


-- 
-
Marc Haber | "I don't trust Computers. They | Mailadresse im Header
Leimen, Germany|  lose things."Winona Ryder | Fon: *49 6224 1600402
Nordisch by Nature |  How to make an American Quilt | Fax: *49 6224 1600421

Bug#1026898: [External] Re: Bug#1026898: deprecate QUOTAUSER post-bookworm

[Marc Haber]

Hi,

On Wed, May 29, 2024 at 04:41:04PM +, Merlin Hansen wrote:
> Unfortunately I have no experience in creating test cases for a package 
> build. However, point me in a direction where I can learn and I'm willing to 
> look into the feasibility of contributing.

The current test cases are available as example in the source package.
Do apt source adduser and look in debian/tests/f.

Greetings
Marc

-- 
-
Marc Haber | "I don't trust Computers. They | Mailadresse im Header
Leimen, Germany|  lose things."Winona Ryder | Fon: *49 6224 1600402
Nordisch by Nature |  How to make an American Quilt | Fax: *49 6224 1600421

Bug#1072204: setupcon: race condition with systemd-tmpfiles

[Marc Leeman]

Package: console-setup
Version: 1.226
Severity: normal
Tags: patch

Dear Maintainer,

On occasion I have a situation where console-setup.service fails to
start up due to a race condition. After investigating this, it was
already reported in Ubuntu back in 2019 and I have verified that the
patch they have implemented resolves the issue for me:

admin@boxpc001-a8f7693fbff14940ade0e3247b1cea8e:~$ for s in $(systemctl 
list-units --type service --full --failed --plain --no-legend | cut -f 1 -d ' 
'); do journalctl --boot --no-pager --unit "${s}"; done
May 28 13:15:05 boxpc001 systemd[1]: Starting console-setup.service - Set 
console font and keymap...
May 28 13:15:05 boxpc001 console-setup.sh[588]: /usr/bin/setupcon: 999: cannot 
open /tmp/tmpkbd.hoHrPK: No such file
May 28 13:15:05 boxpc001 systemd[1]: console-setup.service: Main process 
exited, code=exited, status=1/FAILURE
May 28 13:15:05 boxpc001 systemd[1]: console-setup.service: Failed with result 
'exit-code'.
May 28 13:15:05 boxpc001 systemd[1]: Failed to start console-setup.service - 
Set console font and keymap.

-- System Information:
Debian Release: trixie/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable'), (400, 
'bookworm'), (1, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 6.7.12-amd64 (SMP w/8 CPU threads; PREEMPT)
Kernel taint flags: 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 console-setup depends on:
ii  console-setup-linux 1.226
ii  debconf [debconf-2.0]   1.5.86
ii  keyboard-configuration  1.226
ii  xkb-data2.41-2

console-setup recommends no packages.

Versions of packages console-setup suggests:
ii  locales2.38-11
ii  lsb-base   11.6
ii  sysvinit-utils [lsb-base]  3.09-1

Versions of packages keyboard-configuration depends on:
ii  debconf [debconf-2.0]   1.5.86
ii  liblocale-gettext-perl  1.07-7
ii  xkb-data2.41-2

Versions of packages console-setup-linux depends on:
ii  init-system-helpers 1.66
ii  kbd 2.6.4-2
ii  keyboard-configuration  1.226

console-setup-linux suggests no packages.

Versions of packages console-setup is related to:
pn  console-common
pn  console-data  
pn  console-tools 
ii  gnome-control-center  1:46.0.1-1
ii  kbd   2.6.4-2
ii  systemd   255.5-1

-- debconf information:
* keyboard-configuration/optionscode:
  console-setup/use_system_font:
  console-setup/store_defaults_in_debconf_db: true
  debian-installer/console-setup-udeb/title:
  keyboard-configuration/unsupported_config_layout: true
* keyboard-configuration/model: Generic 105-key PC
* keyboard-configuration/store_defaults_in_debconf_db: true
* keyboard-configuration/switch: No temporary switch
* keyboard-configuration/layout:
  keyboard-configuration/unsupported_layout: true
  console-setup/fontsize: 8x16
  console-setup/codeset47: # Latin1 and Latin5 - western Europe and Turkic 
languages
  console-setup/guess_font:
* keyboard-configuration/layoutcode: us
* keyboard-configuration/altgr: The default for the keyboard layout
  console-setup/fontsize-fb47: 8x16
* keyboard-configuration/xkb-keymap: us
* keyboard-configuration/variantcode:
* keyboard-configuration/toggle: No toggling
* keyboard-configuration/modelcode: pc105
* keyboard-configuration/compose: No compose key
  console-setup/fontface47: Fixed
  console-setup/framebuffer_only:
* keyboard-configuration/other:
  console-setup/fontsize-text47: 8x16
  console-setup/codesetcode: Lat15
* keyboard-configuration/variant: English (US)
  keyboard-configuration/unsupported_options: true
  console-setup/charmap47: UTF-8
  keyboard-configuration/ctrl_alt_bksp: false
  keyboard-configuration/unsupported_config_options: true
diff -Nru console-setup-1.108ubuntu15.4/debian/changelog 
console-setup-1.108ubuntu15.5/debian/changelog
--- console-setup-1.108ubuntu15.4/debian/changelog  2017-10-05 
19:36:07.0 +
+++ console-setup-1.108ubuntu15.5/debian/changelog  2019-04-10 
20:16:29.0 +
@@ -1,3 +1,13 @@
+console-setup (1.108ubuntu15.5) xenial; urgency=medium
+
+  * setupcon: use /run for tempfiles (and dump the various unnecessary
+fallback paths), since /run is always mountable rw at least as early as
+/tmp is and is guaranteed to be safe from tmpcleaners at boot.  Only keep
+/tmp as a fallback in case we have access to write to /tmp and to a
+console, but not to /run.  LP: #1824227.
+
+ -- Steve Langasek   Wed, 10 Apr 2019 13:16:29 -0700
+
 console-setup (1.108ubuntu15.4) xenial; urgency=medium
 
* Drop dependency from console-setup to initramfs-tools |
diff -Nru console-setup-1.108ubuntu15.4/setupcon 
console-setup-1.108ubuntu15.5/setupcon
--- 

Bug#690183:

[Marc Leeman]

https://salsa.debian.org/erpel/apt-fast
https://mentors.debian.net/packages/

-- 
g. Marc

GPG: 827C FD74 BA46 8152 A041 F3A0 7A6A 4F17 5995 A65B

Bug#1026898: deprecate QUOTAUSER post-bookworm

[Marc Haber]

On Tue, May 28, 2024 at 10:48:54PM +, Merlin Hansen wrote:
> Just ran across the notification of deprecation when upgrading Proxmox v2 to 
> v3. We also use QUOTAUSER in multi-user systems in a post-secondary 
> environment. While we can modify our account creation process to manually set 
> the quota using "edquota -p foo bar", having the QUOTAUSER option configured 
> ensures no accounts get created without a quota set (as another submitter 
> mentioned).

Would you be willing to submit test cases so that we can have QUOTAUSER
tested during package build? We would also appreciate code that has
adduser error out more nicely (preferably before doing any changes to
the system) of edquota isnt installed.

My main concern about QUOTAUSER is that we currently dont have tests and
know that it leaves half-setup users if edquota isnt there.

Greetings
Marc

-- 
-----
Marc Haber | "I don't trust Computers. They | Mailadresse im Header
Leimen, Germany|  lose things."Winona Ryder | Fon: *49 6224 1600402
Nordisch by Nature |  How to make an American Quilt | Fax: *49 6224 1600421

Bug#1025623: Deprecate GROUPHOMES and LETTERHOMES

[Marc Haber]

Hi Merlin,

thanks for your comments.

On Tue, May 28, 2024 at 10:56:48PM +, Merlin Hansen wrote:
> I know of at least one post secondary institution that does use heirarchy 
> similar to that set up via LETTERHOMES due to the large number of accounts. 
> I'm not aware of any that use GROUPHOMES though.

And they don't create users via some kind of automation or directory
service?

> I have considered switching to a similar hierarchy as LETTERHOMES for the 
> current institution that I am with, also due to the large number of user 
> accounts. However, there are other ways to achieve this so if it is 
> deprecated then I'll find a different way. 

Sites using a directory services are unlikely to use adduser in the
first place. Existing Automatisms using adduser can be adapted. I
acknowledge that poses an effort on the users of those automatisms
though.

Greetings
Marc

-- 
-
Marc Haber | "I don't trust Computers. They | Mailadresse im Header
Leimen, Germany|  lose things."Winona Ryder | Fon: *49 6224 1600402
Nordisch by Nature |  How to make an American Quilt | Fax: *49 6224 1600421

Bug#1053348: atop gets a segmentation fault

[Marc Haber]

Control: tags -1 unreproducible
thanks

On Sun, Jan 14, 2024 at 07:38:25PM +0100, Tiger!P wrote:
> I have not seen a segfault with 2.10.0-1 yet.
> I have updated atop to 2.10.0-1 on multiple system and will report when
> I see a crash again.

Are you fine with me marking this report as "closed with version
2.10.0-1"?

Greetings
Marc

Bug#1063698: atop FTBFS: hard codes the build architecture pkg-config

[Marc Haber]

Control: tags -1 upstream fixed-upstream patch confirmed
thanks

On Sat, Feb 10, 2024 at 09:53:28AM +0100, Helmut Grohne wrote:
> atop regressed cross building, because its upstream Makefile now hard
> codes a build architecture pkg-config. I'm attaching a patch to make it
> substitutable. Applying it restores the ability to cross build atop.

Upstream has accepted the patch. Currently waiting for them to comment
on whether they will do a release or if they want me to locally patch.
Will wait until first week of june.

Greetings
Marc

Bug#1053443: automount should not act if filesystem is already mounted

[Marc Haber]

On Sun, May 26, 2024 at 06:30:34PM +0100, Luca Boccassi wrote:
> This is not something that is appropriate to patch downstream, even if
> it was desirable.

Just for the record, I disagree. This is integration work and thus well
inside the authority of a cooperative package maintainer in a
distribution.

I appreciate your trying to be helpful.

-- 
-
Marc Haber | "I don't trust Computers. They | Mailadresse im Header
Leimen, Germany|  lose things."Winona Ryder | Fon: *49 6224 1600402
Nordisch by Nature |  How to make an American Quilt | Fax: *49 6224 1600421

Bug#1053443: automount should not act if filesystem is already mounted

[Marc Haber]

On Sun, May 26, 2024 at 05:53:01PM +0100, Luca Boccassi wrote:
> So yeah, not going to risk this for the benefit of a non-default
> package with 0.19% popcon, sorry. Feel free to document the workaround
> and link to this bug as you see fit. I'd recommend noting the FS
> corruption issues too, but that's up to you of course.

I just suggested the automounter to not try to mount a filesystem that
is already there. I am not a systemd expert, but that should be a
minimally invasive oneliner, not changing other system's behavior,
shouldn't it?

-- 
-----
Marc Haber | "I don't trust Computers. They | Mailadresse im Header
Leimen, Germany|  lose things."Winona Ryder | Fon: *49 6224 1600402
Nordisch by Nature |  How to make an American Quilt | Fax: *49 6224 1600421

Bug#1053443: automount should not act if filesystem is already mounted

[Marc Haber]

On Sun, May 26, 2024 at 04:57:10PM +0100, Luca Boccassi wrote:
> I am pretty sure this is working as intended, we do not want the ESP to
> be always mounted by default. You can disable this generator in
> multiple ways if you don't want this behaviour - via the cmdline as
> already mentioned, or by masking it with:
> 
> touch /etc/systemd/system-generators/systemd-gpt-auto-generator

Okay, this is then going as documentation into aide's systemd rule in
Debian with a link to this bug report.

Thanks for being a friendly neighbor to other packages.


-- 
-
Marc Haber | "I don't trust Computers. They | Mailadresse im Header
Leimen, Germany|  lose things."Winona Ryder | Fon: *49 6224 1600402
Nordisch by Nature |  How to make an American Quilt | Fax: *49 6224 1600421

Bug#1069859: atop: Fix atop for 64-bit time_t on arm

[Marc Haber]

Control: tags -1 confirmed
Control: forwarded -1 https://github.com/Atoptool/atop/issues/306
thanks

thanks for spotting and debugging this.

On Thu, Apr 25, 2024 at 02:16:33PM -0700, Steve Langasek wrote:
> Although atop currently builds successfully on armhf and armel, it is broken
> at runtime because it tries to use a time_t in a format string which now no
> longer uses the correct size for the data.  This was found in Ubuntu via
> autopkgtests (unfortunately, Debian does not run autopkgtests for binNMUs):

At least this superficial test did its job to uncover this issue. I'm
quite happy about that.

I can reproduce the issue and disagree with the classification as an RC
bug. THe normal atop usage doesn't seem affected, only the -P option is
broken. This doesnt make the package unustable for everbody.

My apologies for letting this lay for a month, I was busy elsewhere in
my life.

I am not too fond about the suggested patch since it breaks atop on
systems with 32bit time_t, which is not nice to backporters. I have
asked Upstream whether they would be up for a less invasive fix. I
intend to let this rest until the middle of the next week.

Greetings
Marc

Bug#1071721: [mosquitto] mosquittostart-stop-daemon: unable to open pidfile '/run/mosquitto/mosquitto.pid' for writing (No such file or directory)

[Jean-Marc LACROIX]

Package: mosquitto
Version: 2.0.11-1.2+deb12u1
Severity: grave

Is seems that on  package mosquitto (Debian 12.5  Bookworm), is is not
possible to install the package & start the daemon.

Please  note following  example are  done  on amd64  architecture, but
behaviour is the same on others architectures.

This bug is probably due to the directory created with the pid file.

ansible@hn-asusgl752-400:~$ LC_ALL=C dpkg -l |grep mosquitto
ii  libmosquitto1:amd64  2.0.11-1.2+deb12u1 
 amd64MQTT version 5.0/3.1.1/3.1 client library
ii  mosquitto-clients2.0.11-1.2+deb12u1 
 amd64Mosquitto command line MQTT clients

ansible@hn-asusgl752-400:~$

ansible@hn-asusgl752-400:~$ cat /etc/debian_version
12.5


ansible@hn-asusgl752-400:~$ LC_ALL=C apt policy mosquitto
mosquitto:
  Installed: (none)
  Candidate: 2.0.11-1.2+deb12u1
  Version table:
 2.0.18-1+b2 80
 80 http://ftp.de.debian.org/debian trixie/main amd64 Packages
 2.0.11-1.2+deb12u1 500
500 http://ftp.de.debian.org/debian bookworm/main amd64 Packages
500 https://security.debian.org bookworm-security/main amd64 
Packages

 2.0.11-1+deb11u1 90
 90 http://ftp.de.debian.org/debian bullseye/main amd64 Packages
ansible@hn-asusgl752-400:~$


ansible@hn-asusgl752-400:~$ LC_ALL=C sudo apt install mosquitto -y
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
The following NEW packages will be installed:
  mosquitto
0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded.
Need to get 0 B/409 kB of archives.
After this operation, 1063 kB of additional disk space will be used.
Selecting previously unselected package mosquitto.
(Reading database ... 289805 files and directories currently installed.)
Preparing to unpack .../mosquitto_2.0.11-1.2+deb12u1_amd64.deb ...
Unpacking mosquitto (2.0.11-1.2+deb12u1) ...
Setting up mosquitto (2.0.11-1.2+deb12u1) ...
Starting network daemon:: mosquittostart-stop-daemon: unable to open 
pidfile '/run/mosquitto/mosquitto.pid' for writing (No such file or 
directory)

start-stop-daemon: child returned error exit status 2
 failed!
invoke-rc.d: initscript mosquitto, action "start" failed.
dpkg: error processing package mosquitto (--configure):
 installed mosquitto package post-installation script subprocess 
returned error exit status 1

Processing triggers for man-db (2.11.2-2) ...
Processing triggers for libc-bin (2.36-9+deb12u7) ...
Errors were encountered while processing:
 mosquitto
E: Sub-process /usr/bin/dpkg returned an error code (1)
ansible@hn-asusgl752-400:~$

ansible@hn-asusgl752-400:~ mount |grep /run
tmpfs on /run type tmpfs 
(rw,nosuid,nodev,noexec,relatime,size=1165244k,mode=755,inode64)
tmpfs on /run/lock type tmpfs 
(rw,nosuid,nodev,noexec,relatime,size=5120k,inode64)
tmpfs on /run/user/998 type tmpfs 
(rw,nosuid,nodev,relatime,size=1165244k,nr_inodes=291311,mode=700,uid=998,gid=1004,inode64)

rpc_pipefs on /run/rpc_pipefs type rpc_pipefs (rw,relatime)
ansible@hn-asusgl752-400:~/git/ansible-jml.git/sources/environments/site_test_local$ 



It seems that following line can correct launching o daemon

   sed -i -e 
's#PIDFILE=/run/mosquitto/mosquitto.pid#PIDFILE=/run/mosquitto.pid#g' 
/etc/init.d/mosquitto


Best regards

--
  -- Jean-Marc LACROIX  --
-- mailto : jeanmarc.lacr...@free.fr   --

Bug#1059616: "wc -l" gives "illegal instruction"

[Marc Haber]

On Fri, Dec 29, 2023 at 03:38:32PM +, Pádraig Brady wrote:
> On 29/12/2023 09:52, gates.ocarina...@icloud.com wrote:
> > When I run command wc -l, it gives “illegal instruction”.

I can confirm this for at least one of my machines.

> https://github.com/coreutils/coreutils/commit/91a74d361.patch
> https://github.com/coreutils/coreutils/commit/7814596fa.patch

I can confirm that those two patches fix the issue for me on Debian
bookworm. They don't apply cleanly to the sources in bookworm, but the
result is still fine. I'll attach the new quilt patch file.

Since I am not using Debian's default kernel and the issue only happens
on one of my machines, I won't raise the severity, but if this also
happens with a Debian kernel, this would be an RC bug for me and warrant
a bookworm point release upload.

Greetings
Marc

--- a/configure.ac
+++ b/configure.ac
@@ -544,27 +544,6 @@ CFLAGS=$ac_save_CFLAGS
 LDFLAGS=$ac_save_LDFLAGS
 ac_c_werror_flag=$cu_save_c_werror_flag
 
-AC_MSG_CHECKING([if __get_cpuid available])
-AC_LINK_IFELSE(
-  [AC_LANG_SOURCE([[
-#include 
-
-int
-main (void)
-{
-  unsigned int eax, ebx, ecx, edx;
-  __get_cpuid (1, , , , );
-  return 1;
-}
-  ]])
-  ],[
-AC_MSG_RESULT([yes])
-AC_DEFINE([HAVE_CPUID], [1], [__get_cpuid available])
-cpuid_exists=yes
-  ],[
-AC_MSG_RESULT([no])
-  ])
-
 ac_save_CFLAGS=$CFLAGS
 CFLAGS="-mavx -mpclmul $CFLAGS"
 AC_MSG_CHECKING([if pclmul intrinsic exists])
@@ -628,23 +607,20 @@ AC_COMPILE_IFELSE(
 {
   __m256i a, b;
   a = _mm256_sad_epu8 (a, b);
-  return 1;
+  return __builtin_cpu_supports ("avx2");
 }
   ]])
   ],[
-AC_MSG_RESULT([yes])
-AC_DEFINE([HAVE_AVX2_INTRINSIC], [1], [avx2 intrinsics exists])
 avx2_intrinsic_exists=yes
   ],[
-AC_MSG_RESULT([no])
+avx2_intrinsic_exists=no
   ])
-if test "x$get_cpuid_count_exists" = "xyes" &&
-   test "x$avx2_intrinsic_exists" = "xyes"; then
+AC_MSG_RESULT([$avx2_intrinsic_exists])
+if test $avx2_intrinsic_exists = yes; then
   AC_DEFINE([USE_AVX2_WC_LINECOUNT], [1], [Counting lines with AVX2 enabled])
 fi
 AM_CONDITIONAL([USE_AVX2_WC_LINECOUNT],
-   [test "x$get_cpuid_count_exists" = "xyes" &&
-test "x$avx2_intrinsic_exists" = "xyes"])
+   [test $avx2_intrinsic_exists = yes])
 
 CFLAGS=$ac_save_CFLAGS
 
--- a/NEWS
+++ b/NEWS
@@ -42,6 +42,9 @@ GNU coreutils NEWS
   for B when A is a directory, possibly inflooping.
   [bug introduced in coreutils-6.3]
 
+  'wc -l' no longer crashes on x86 Linux kernels that disable XSAVE YMM.
+  [bug introduced in coreutils-9.0]
+
 ** Changes in behavior
 
   cat now uses the copy_file_range syscall if available, when doing
--- a/src/cksum.c
+++ b/src/cksum.c
@@ -159,29 +159,16 @@ static bool
 pclmul_supported (void)
 {
 # if USE_PCLMUL_CRC32
-  unsigned int eax = 0;
-  unsigned int ebx = 0;
-  unsigned int ecx = 0;
-  unsigned int edx = 0;
-
-  if (! __get_cpuid (1, , , , ))
-{
-  if (cksum_debug)
-error (0, 0, "%s", _("failed to get cpuid"));
-  return false;
-}
-
-  if (! (ecx & bit_PCLMUL) || ! (ecx & bit_AVX))
-{
-  if (cksum_debug)
-error (0, 0, "%s", _("pclmul support not detected"));
-  return false;
-}
+  bool pclmul_enabled = (0 < __builtin_cpu_supports ("pclmul")
+ && 0 < __builtin_cpu_supports ("avx"));
 
   if (cksum_debug)
-error (0, 0, "%s", _("using pclmul hardware support"));
+error (0, 0, "%s",
+   (pclmul_enabled
+? _("using pclmul hardware support")
+: _("pclmul support not detected")));
 
-  return true;
+  return pclmul_enabled;
 # else
   if (cksum_debug)
 error (0, 0, "%s", _("using generic hardware support"));
--- a/src/wc.c
+++ b/src/wc.c
@@ -132,52 +132,14 @@ static struct option const longopts[] =
 static bool
 avx2_supported (void)
 {
-  unsigned int eax = 0;
-  unsigned int ebx = 0;
-  unsigned int ecx = 0;
-  unsigned int edx = 0;
-  bool getcpuid_ok = false;
-  bool avx_enabled = false;
+  bool avx_enabled = 0 < __builtin_cpu_supports ("avx2");
 
-  if (__get_cpuid (1, , , , ))
-{
-  getcpuid_ok = true;
-  if (ecx & bit_OSXSAVE)
-avx_enabled = true;  /* Support is not disabled.  */
-}
+  if (debug)
+error (0, 0, (avx_enabled
+  ? _("using avx2 hardware support")
+  : _("avx2 support not detected")));
 
-
-  if (avx_enabled)
-{
-  eax = ebx = ecx = edx = 0;
-  if (! __get_cpuid_count (7, 0, , , , ))
-getcpuid_ok = false;
-  else
-{
-  if (! (ebx & bit_AVX2))
-avx_enabled = fals

Bug#1071564: bookworm-pu: package aide/0.18.3-1+deb12u3

[Marc Haber]

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

This upload fixes #1070805. The reporter, Hannes, is upstream and a DD,
and thinks the issue warrants a stable update.

[ Reason ]
aide 0.18 has introduced some concurrency in processing. There is a bug
that makes fail to concurrently read extended attributes (xattrs) due to
variables shared between worker threads.

[ Impact ]
Incomplete aide checks

[ Tests ]
The fix is in productive use (in a git snapshot of HEAD) at upstream and
the Debian maintainer.

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

[ Changes ]
Upstream patch 732e7e2e
diff -Nru aide-0.18.3/debian/changelog aide-0.18.3/debian/changelog
--- aide-0.18.3/debian/changelog2023-07-01 14:37:51.0 +0200
+++ aide-0.18.3/debian/changelog2024-05-16 13:32:11.0 +0200
@@ -1,3 +1,10 @@
+aide (0.18.3-1+deb12u3) bookworm; urgency=medium
+
+  * Upstream patch to fix concurrent reading of extended
+attributes (xattrs) (Closes: #1070805)
+
+ -- Marc Haber   Thu, 16 May 2024 13:32:11 
+0200
+
 aide (0.18.3-1+deb12u2) bookworm; urgency=medium
 
   * Upstream patch to fix child directory processing on equal match
diff -Nru aide-0.18.3/debian/patches/debian-bug-1070805 
aide-0.18.3/debian/patches/debian-bug-1070805
--- aide-0.18.3/debian/patches/debian-bug-1070805   1970-01-01 
01:00:00.0 +0100
+++ aide-0.18.3/debian/patches/debian-bug-1070805   2024-05-16 
13:32:11.0 +0200
@@ -0,0 +1,47 @@
+Description: Fix concurrent reading of extended attributes (xattrs)
+Author: Hannes von Haugwitz 
+Origin: 732e7e2e7dc91bb614c508518c0abc6cab85565c
+Date: Mon May 16 13:30:00 2024 +0200
+Forwarded: not-needed
+--- a/src/do_md.c
 b/src/do_md.c
+@@ -478,14 +478,13 @@ static void xattr_add(xattrs_type *xattr
+ void xattrs2line(db_line *line) {
+ /* get all generic user xattrs. */
+ xattrs_type *xattrs = NULL;
+-static ssize_t xsz = 1024;
+-static char *xatrs = NULL;
+ ssize_t xret = -1;
+ 
+ if (!(ATTR(attr_xattrs)>attr))
+ return;
+ 
+-if (!xatrs) xatrs = checked_malloc(xsz);
++ssize_t xsz = 1024;
++char *xatrs = xatrs = checked_malloc(xsz);
+ 
+ while (((xret = llistxattr(line->fullpath, xatrs, xsz)) == -1) && (errno 
== ERANGE)) {
+ xsz <<= 1;
+@@ -498,10 +497,8 @@ void xattrs2line(db_line *line) {
+ log_msg(LOG_LEVEL_WARNING, "listxattrs failed for %s:%s", 
line->fullpath, strerror(errno));
+ } else if (xret) {
+ const char *attr = xatrs;
+-static ssize_t asz = 1024;
+-static char *val = NULL;
+-
+-if (!val) val = checked_malloc(asz);
++ssize_t asz = 1024;
++char *val = checked_malloc(asz);
+ 
+ xattrs = xattr_new();
+ 
+@@ -529,7 +526,9 @@ next_attr:
+ attr += len + 1;
+ xret -= len + 1;
+ }
++free(val);
+ }
++free(xatrs);
+ 
+ line->xattrs = xattrs;
+ }
diff -Nru aide-0.18.3/debian/patches/series aide-0.18.3/debian/patches/series
--- aide-0.18.3/debian/patches/series   2023-07-01 14:37:51.0 +0200
+++ aide-0.18.3/debian/patches/series   2024-05-16 13:32:11.0 +0200
@@ -1,3 +1,4 @@
 debian-bug-1039936
 debian-bug-1037436
 compare-logs
+debian-bug-1070805

Bug#1029140: cron-apt refuses to run when RUNSLEEP is set

[Marc Haber]

> Can you run it with bash -x from cron? Hopefully it tells where it breaks

Using bash will not help here, that's the problem. cron-apt is a /bin/sh
script, and on many systems /bin/sh is dash. And, $RANDOM doesn't exist
in dash.

Change cron-apt's shebang line to use /bin/bash and it should be fine.

Now we probably can move on to stage 6 of debugging "how did that
ever work?", since we're having /bin/sh point to dash for a while and
this issue just appeared on of my _stable_ systems.

Greetings
Marc

Bug#1071111: Create directory /var/lib/ampr-ripd

[Marc F. Clemente]

Package: ampr-ripd
Version: 2.4.1-1+b2

Please consider creating the directory /var/lib/ampr-ripd on installation.

This way, the encap.txt has a place to go.

Cheers,

Marc

Bug#491127: logcheck: please consider an option which will always check the entire log file

[Marc Haber]

On Sun, May 12, 2024 at 06:54:59PM +0100, R Lewis wrote:
> On Wed, 16 Jul 2008 23:15:51 +0200 Marc Haber
>  wrote:
> 
> > It would help with debugging to have an option that causes logcheck to
> > always look through the entire log file, ie not using logtail.
> 
> Looking at this old bug from 2008: does the -t option meet this need?

Not quite. Imagine: I have a system running logcheck hourly. At 11:00, I
get a mail with a log message from 10:55 that is not yet covered by the
rule. The stamp gets updated to 11:00.

I now fix the rule that should have filtered the message. logcheck -t
will still only start checking a 11:00, so the test run will not prove
that the change has actually filtered the message from 10:55.

Does this make the usecase clear?

Greetings
Marc

P.S. Thanks for doing bug triage.

-- 
-----
Marc Haber | "I don't trust Computers. They | Mailadresse im Header
Leimen, Germany|  lose things."Winona Ryder | Fon: *49 6224 1600402
Nordisch by Nature |  How to make an American Quilt | Fax: *49 6224 1600421

Bug#1063900: gstreamer1.0-plugins-good: missing Breaks+Replaces: gstreamer1.0-plugins-ugly (<< 1.23)

[Jean-Marc]

On Wed, 14 Feb 2024 14:58:16 +0100 Andreas Beckmann  wrote:

Package: gstreamer1.0-plugins-good
Version: 1.23.1-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,
[...]


Current version in sid are the following ones:

$ apt policy gstreamer1.0-plugins-good gstreamer1.0-plugins-ugly
gstreamer1.0-plugins-good:
 Table de version :
 1.24.2-1 500
500 https://deb.debian.org/debian unstable/main amd64 Packages

gstreamer1.0-plugins-ugly:
 Table de version :
 1.24.2-1+b1 500
500 https://deb.debian.org/debian unstable/main amd64 Packages


The following files are in conflict:

/usr/lib/x86_64-linux-gnu/gstreamer-1.0/libgstamrnb.so
/usr/lib/x86_64-linux-gnu/gstreamer-1.0/libgstamrwbdec.so
/usr/share/gstreamer-1.0/presets/GstAmrnbEnc.prs


Files mentioned here in the bug report are not present in 
gstreamer1.0-plugins-ugly:1.24.2-1+b1 anymore.


Can you confirm I am not wrong and update the bug report accordingly ?


cheers,


Regards,


Andreas


--
Jean-Marc

(*)
/usr/lib/x86_64-linux-gnu/gstreamer-1.0/libgstamrnb.so
/usr/lib/x86_64-linux-gnu/gstreamer-1.0/libgstamrwbdec.so
/usr/share/gstreamer-1.0/presets/GstAmrnbEnc.prs


OpenPGP_signature.asc
Description: OpenPGP digital signature

Bug#1068828: non-portable use of cp -n triggers warning at update-initramfs time

[Marc Haber]

Package: yubikey-luks
Version: 0.5.1+29.g5df2b95-6.2
Severity: minor
Tags: patch

Hi,

the use of "cp -pnL" in /usr/share/initramfs-tools/hooks/yubikey-luks
triggers a warning "cp: warning: behavior of -n is non-portable and may
change in future; use --update=none instead" when the initramfs is
rebuilt.

--- yubikey-luks2024-04-11 18:27:36.614656012 +0200
+++ /usr/share/initramfs-tools/hooks/yubikey-luks   2024-04-11 
18:28:05.614804445 +0200
@@ -23,7 +23,7 @@
 copy_exec /usr/bin/sha256sum
 cp /usr/share/yubikey-luks/ykluks-keyscript "${DESTDIR}/sbin/ykluks-keyscript"
 cp /etc/ykluks.cfg "${DESTDIR}/etc/ykluks.cfg"
-cp -pnL /usr/lib/yubikey-luks/initramfs-suspend "${DESTDIR}/suspend"
+cp -pL --update=none /usr/lib/yubikey-luks/initramfs-suspend 
"${DESTDIR}/suspend"
 chmod 755 "${DESTDIR}/suspend"
 
 exit 0

Makes the warning go away. I am not yet using the functionality so I
don't whether this introduces breakage.

Greetings
Marc


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

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

Versions of packages yubikey-luks depends on:
ii  cryptsetup   2:2.7.2-1
ii  initramfs-tools  0.142
ii  yubikey-personalization  1.20.0-3+b1

Versions of packages yubikey-luks recommends:
ii  cryptsetup-initramfs  2:2.7.2-1
ii  expect5.45.4-3

yubikey-luks suggests no packages.

-- no debconf information

-- debsums errors found:
debsums: changed file /usr/share/initramfs-tools/hooks/yubikey-luks (from 
yubikey-luks package)

Bug#1067845: adduser: Reserving uid/gid from the uid/gid pools

[Marc Haber]

On Mon, Apr 01, 2024 at 04:49:40PM +0300, Yair Yarom wrote:
> Attached is a patch to uidgidpool.t that tests several cases of the
> reserved uids.
> I'm not really proficient in these test tools, so I hope it works
> properly...

Thank you! I'll try those in the next weeks. Unfortunately, quite busy
at the moment.

Greetings
Marc

-- 
-----
Marc Haber | "I don't trust Computers. They | Mailadresse im Header
Leimen, Germany|  lose things."Winona Ryder | Fon: *49 6224 1600402
Nordisch by Nature |  How to make an American Quilt | Fax: *49 6224 1600421

Bug#1068636: lincity-ng: conflict with older lincity-ng-data

[Marc Glisse]

Package: lincity-ng
Version: 2.10.1-1
Severity: normal

Dear Maintainer,

`apt upgrade` failed with

Unpacking lincity-ng (2.10.1-1) over (2.9.0-1) ...
dpkg: error processing archive 
/tmp/apt-dpkg-install-msgcqU/39-lincity-ng_2.10.1-1_amd64.deb (--unpack):
 trying to overwrite '/usr/share/icons/hicolor/128x128/apps/lincity-ng.png', 
which is also in package lincity-ng-data 2.9.0-1

(a simple `apt -f install` fixes it)

If the file was really supposed to change package (was it?), you need to
declare suitable breaks/conflicts/replaces/etc control fields.

-- System Information:
Debian Release: trixie/sid
  APT prefers testing-debug
  APT policy: (500, 'testing-debug'), (500, 'stable-debug'), (500, 'testing'), 
(400, 'stable-security'), (400, 'stable'), (50, 'unstable-debug'), (50, 
'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386, arm64, ppc64el, mips64el, s390x, armhf

Kernel: Linux 6.6.15-amd64 (SMP w/16 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 lincity-ng depends on:
ii  libc62.37-15
ii  libgcc-s114-20240201-3
ii  libgl1   1.7.0-1
ii  libphysfs1   3.0.2-6
ii  libsdl2-2.0-02.30.0+dfsg-1
ii  libsdl2-gfx-1.0-01.0.4+dfsg-5
ii  libsdl2-image-2.0-0  2.8.2+dfsg-1
ii  libsdl2-mixer-2.0-0  2.8.0+dfsg-1
ii  libsdl2-ttf-2.0-02.22.0+dfsg-1
ii  libstdc++6   14-20240201-3
ii  libxml2  2.9.14+dfsg-1.3+b2
ii  lincity-ng-data  2.10.1-1
ii  zlib1g   1:1.3.dfsg-3+b1

lincity-ng recommends no packages.

lincity-ng suggests no packages.

-- no debconf information

Bug#1053497: salsa

[Marc Leeman]

See:

https://salsa.debian.org/televic-team/tcnopen

-- 
g. Marc

GPG: 827C FD74 BA46 8152 A041 F3A0 7A6A 4F17 5995 A65B

Bug#584865: policyrcd-script-zg2: please consider some sort of integration also with /etc/init.d/rc

[Marc Haber]

Control: tags -1 wontfix
thanks

On Mon, Jun 07, 2010 at 11:42:25AM +0300, Timo Juhani Lindfors wrote:
> < lindi-> Zugschlus: my /etc/policy-rc.d lookups
> /etc/policy-{white,black}list.conf and logs decisions to syslog. this
> works very nicely thanks to policyrcd-script-zg2. can you suggest a
> way to make this also work for services that are started during boot?
> 
> < lindi-> Zugschlus: I see two options 1) divert update-rc.d with my
> own version that will not add start links for blacklisted services 2)
> modify /etc/init.d/rcS to use invoke-rc.d

Influencing bootup behavior is beyond the scope of policyrcd-script-zg2.
If you don't want a service to start at bootup, disable it in systemd or
configure your non-systemd-init appropriately.

I am tagging this wontfix for the time being.

Greetings
Marc

Bug#1067845: adduser: Reserving uid/gid from the uid/gid pools

[Marc Haber]

On Wed, Mar 27, 2024 at 04:55:35PM +0200, Yair Yarom wrote:
> The UID_POOL (and GID_POOL) files contains UIDs that should be used for given
> name. It would be helpful to reserve the UIDs for the future, so that the 
> order
> of adding users to the system won't affect the usability of the UIDs/names.
> 
> I.e. if a UID is in the pool, it won't be used unless for the specific name in
> the pool.

That sounds sensible.

Would you mind to contribute test cases as well? The canoncal place for
those test cases would probably be debian/tests/f/uidgidpool.t

Greetings
Marc


-- 
-
Marc Haber | "I don't trust Computers. They | Mailadresse im Header
Leimen, Germany|  lose things."Winona Ryder | Fon: *49 6224 1600402
Nordisch by Nature |  How to make an American Quilt | Fax: *49 6224 1600421

Bug#1067411: sosreport: Debian Unstable version is running behind with 3 years (new release 4.7.0)

[Marc Leeman]

Package: sosreport
Version: 4.6.0-1~televic12+1
Severity: normal

Dear Maintainer,

I have been using sosreport on bullseye and bookworm and I notice that
the version in sid is not updated for 3 years.

I will upload an NMU and hope to find a sponsor. I will also open PRs on
salsa.

-- System Information:
Debian Release: trixie/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable'), (400, 
'bookworm'), (1, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 6.6.13-amd64 (SMP w/8 CPU threads; PREEMPT)
Kernel taint flags: TAINT_WARN, 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 sosreport depends on:
ii  python3  3.11.6-1
ii  python3-pexpect  4.9-1
ii  python3-yaml 6.0.1-2

Versions of packages sosreport recommends:
ii  e2fsprogs  1.47.0-2+b1
ii  lsof   4.95.0-1
ii  mount  2.39.3-6

sosreport suggests no packages.

-- no debconf information

Bug#1067228: linux-image-6.6.13+bpo-amd64-unsigned: _major_ cpu performance degradation from 6.1

[Marc Lehmann]

Package: linux-image-6.6.13+bpo-amd64-unsigned
Severity: important

Dear Maintainer,

Upgrading from bookroms 6.1 to 6.6 causes a major performance degradation.

   * What led up to the situation?

I semi-regularly stress-test systems with linpack-xtreme-1.1.5-amd64 to
see if there are thermal or stability problems. Typical output looks like
this. The GFlops performance varies somewhat due to thermal issues, but is
generally above 500 GFlops on this system:

   Size   LDAAlign. Time(s)GFlops   Residual Residual(norm) Check
   22611  22611  4  15.171 508.0650 4.907015e-10 3.410840e-02   pass
   22611  22611  4  14.935 516.0887 4.907015e-10 3.410840e-02   pass
   22611  22611  4  14.978 514.6037 4.907015e-10 3.410840e-02   pass
   22611  22611  4  15.260 505.0881 4.907015e-10 3.410840e-02   pass
   22611  22611  4  14.669 525.4384 4.907015e-10 3.410840e-02   pass

After upgrading from 6.1 to 6.6, I noticed some programs being
surprisingly slow, so I run the stress test,a nd got output like this:

   Size   LDAAlign. Time(s)GFlops   Residual Residual(norm) Check
   22611  22611  4  48.447 159.0972 5.357863e-10 3.724222e-02   pass

As you can see, the performance is seriously degraded. Moreso, it is all
over the place, sometimes it as 212 GFlops, sometimes only 44.

This is on an i7-14700k, but it happens with another system using a 13700k
in exactly the same way.

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

After some investigation, I noticed that rapl shows a power usage of about
50W instead of the more expected 200+. Turned out thermald set a power
limit of 65W. Thinking this to be some bug in thermald, I disabled it and
restored the power limit(s) too 300W.

Unfortunately, while this increased the power usage to almost 200W, it did
not improve performance at all (normal cpu power suage for linpack is up
to 275W).

I then tried various other things, and found that booting the old 6.1
linux kernel fixed this problem completely. Not quite believing it, I
built a special initrd with linpack inside, and found it happens in
there too, that is, linux-6.6 is slow, erratic, and linux-6.1 performs
as expected, and this is independent of any configuration or installed
software.

I tried booting with no kernel arguments as well to exclude any command
line arguments being the culprit, and found the same performance
degradation, leaving essentially only the kernel. (my default arguments
include mitigations=off, so it's not caused by any mitigation either).

I also tried this on another system with a 13700K cpu, and got exactly the
same results - 6.1 works fine, 6.6 only reaches 10-50% of the performance,
very erratically.

I do notice that processes seem to jump around widely between cpus when
this happens, but that might or might not be related.

   * What was the outcome of this action?

I did downgrade to 6.1 on all affected systems.

   * What outcome did you expect instead?

Obviously, 6.6 should perform more or less the same as 6.1.

This might not be an issue with debians kernel, as I can find a few other,
similar reports affecting manjaro and arch linux, e.g.

https://forum.manjaro.org/t/linux-kernel-6-6-lts-cpu-regression-on-i7-alderlake/157474/30

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

-- System Information:
Debian Release: 12.5
  APT prefers stable-updates
  APT policy: (990, 'stable-updates'), (990, 'stable-security'), (990, 
'stable'), (500, 'unstable-debug'), (500, 'testing-debug'), (500, 
'oldstable-debug'), (500, 'unstable'), (500, 'testing'), (1, 
'experimental-debug'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386, x32

Kernel: Linux 6.1.0-18-amd64 (SMP w/28 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_USER, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
Locale: LANG=en_IE.UTF-8, LC_CTYPE=en_IE.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-6.6.13+bpo-amd64-unsigned depends on:
ii  initramfs-tools [linux-initramfs-tool]  0.142
ii  kmod30+20221128-1
ii  linux-base  4.9

Versions of packages linux-image-6.6.13+bpo-amd64-unsigned recommends:
ii  apparmor 3.0.8-3
ii  firmware-linux-free  20200122-1

Versions of packages linux-image-6.6.13+bpo-amd64-unsigned suggests:
pn  debian-kernel-handbook  
ii  extlinux3:6.04~git20190206.bf6db5b4+dfsg1-3+b1
ii  grub-efi-amd64  2.06-13+deb12u1
pn  linux-doc-6.6   

Bug#1065411: dash: 'jobs' utility does not generate output in a pipe

[Marc Lehmann]

Package: dash
Version: 0.5.12-6
Severity: normal

Dear Maintainer,

I found that 'jobs' in dash is silent when stdout is a pipe:

   # dash -c 'sleep 1 1|wc -l'
   0

afaics, this is not documented behaviour, and other utilities (kill, alias) seem
to work fine.

bash does allow the output of jobs to be parsed:

   # bash -c 'sleep 1 1|wc -l'
   2

I think the bash behaviour is more useful for shell programming, and
probably correct, as the sus does not seem to indicate that jobs should
have no output in this case.

-- System Information:
Debian Release: 12.5
  APT prefers stable-updates
  APT policy: (990, 'stable-updates'), (990, 'stable-security'), (990, 
'stable'), (500, 'unstable-debug'), (500, 'testing-debug'), (500, 
'oldstable-debug'), (500, 'unstable'), (500, 'testing'), (1, 
'experimental-debug'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386, x32

Kernel: Linux 6.6.15-amd64 (SMP w/28 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_USER, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
Locale: LANG=en_IE.UTF-8, LC_CTYPE=en_IE.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 dash depends on:
ii  debianutils  5.7-0.5~deb12u1
ii  dpkg 1.21.22
ii  libc62.36-9+deb12u4

dash recommends no packages.

dash suggests no packages.

-- debconf information excluded

Bug#1064438: gnome-settings-daemon: gsd-xsettings crash with older gsettings-desktop-schemas

[Marc Glisse]

Package: gnome-settings-daemon
Version: 46~beta-1
Severity: important

Dear Maintainer,

since the update of gnome-settings-daemon to version 46 in testing,
gsd-xsettings crashes while reporting

(gsd-xsettings:5037): GLib-GIO-ERROR **: 08:45:13.336: Settings schema 
'org.gnome.desktop.a11y.interface' does not contain a key named 
'show-status-shapes'

The backtrace doesn't say much more

(gdb) bt
#0  g_log_structured_array (log_level=, fields=0x7fffdc20, 
n_fields=4) at ../../../glib/gmessages.c:556
#1  0x7732f9e2 in g_log_default_handler
(log_domain=log_domain@entry=0x77568ecb "GLib-GIO", 
log_level=log_level@entry=6, message=message@entry=0x7fffe4004c80 "Settings 
schema 'org.gnome.desktop.a11y.interface' does not contain a key named 
'show-status-shapes'", unused_data=unused_data@entry=0x0)
at ../../../glib/gmessages.c:3284
#2  0x7732fc50 in g_logv (log_domain=0x77568ecb "GLib-GIO", 
log_level=G_LOG_LEVEL_ERROR, format=, 
args=args@entry=0x7fffdd70) at ../../../glib/gmessages.c:1392
#3  0x7732ff03 in g_log (log_domain=log_domain@entry=0x77568ecb 
"GLib-GIO", log_level=log_level@entry=G_LOG_LEVEL_ERROR, 
format=format@entry=0x77580ed8 "Settings schema '%s' does not contain a key 
named '%s'") at ../../../glib/gmessages.c:1461
#4  0x7750d5b1 in g_settings_schema_get_value (key=, 
schema=) at ../../../gio/gsettingsschema.c:1015
#5  g_settings_schema_get_value (schema=0x55611220, key=0x55561ac5 
"show-status-shapes") at ../../../gio/gsettingsschema.c:1001
#6  0x7750dc37 in g_settings_schema_key_init 
(key=key@entry=0x7fffdee0, schema=0x55611220, 
name=name@entry=0x55561ac5 "show-status-shapes") at 
../../../gio/gsettingsschema.c:1295
#7  0x77511d07 in g_settings_get_value (settings=0x556108d0 
[GSettings], key=0x55561ac5 "show-status-shapes") at 
../../../gio/gsettings.c:1224
#8  0xe379 in gsd_xsettings_manager_start (manager=0x555ebbe0 
[GsdXSettingsManager], error=error@entry=0x7fffe090) at 
../plugins/xsettings/gsd-xsettings-manager.c:1519
#9  0xb0f0 in main (argc=, argv=) at 
../plugins/common/daemon-skeleton-gtk.h:277

The mention of "schema" led me to notice that gsettings-desktop-schemas has a 
newer version in unstable, and indeed upgrading that package (and the gir and 
dev packages that come with it) from 45.0-2 to 46~beta-3 seems to have fixed 
the issue.

My suggestion would be to tighten the dependency, which currently only says (>= 
42~). Maybe in the very short term you could also ask if the migration of 
gsettings-desktop-schemas to testing can be sped up?

-- System Information:
Debian Release: trixie/sid
  APT prefers testing-debug
  APT policy: (500, 'testing-debug'), (500, 'stable-security'), (500, 
'stable-debug'), (500, 'testing'), (500, 'stable'), (50, 'unstable-debug'), 
(50, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)

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

Versions of packages gnome-settings-daemon depends on:
ii  gnome-settings-daemon-common  46~beta-1
ii  gsettings-desktop-schemas 46~beta-3
ii  libasound21.2.10-3
ii  libc6 2.37-15
ii  libcairo2 1.18.0-1+b1
ii  libcanberra-gtk3-00.30-11
ii  libcanberra0  0.30-11
ii  libcolord21.4.7-1
ii  libcups2  2.4.7-1+b1
ii  libfontconfig12.14.2-6+b1
ii  libgck-1-03.41.1-4
ii  libgcr-base-3-1   3.41.1-4
ii  libgdk-pixbuf-2.0-0   2.42.10+dfsg-3+b1
ii  libgeoclue-2-02.7.1-2
ii  libgeocode-glib-2-0   3.26.3-6+b1
ii  libglib2.0-0  2.78.4-1
ii  libgnome-desktop-3-20 44.0-2+b1
ii  libgtk-3-03.24.41-1
ii  libgudev-1.0-0238-3
ii  libgweather-4-0   4.4.0-1
ii  libmm-glib0   1.22.0-3
ii  libnm01.44.2-7
ii  libnotify40.8.3-1
ii  libp11-kit0   0.25.3-4
ii  libpam-systemd [logind]   255.3-2
ii  libpango-1.0-01.51.0+ds-4
ii  libpangocairo-1.0-0   1.51.0+ds-4
ii  libpolkit-gobject-1-0 124-1
ii  libpulse-mainloop-glib0   16.1+dfsg1-3
ii  libpulse0 16.1+dfsg1-3
ii  libspa-0.2-bluetooth  1.0.3-1
ii  libsystemd0   255.3-2
ii  libupower-glib3   1.90.2-8
ii  libwacom9 2.9.0-2
ii  libwayland-client01.22.0-2.1+b1
ii  libx11-6  2:1.8.7-1
ii  libxext6  2:1.3.4-1+b1
ii  libxfixes31:6.0.0-2
ii  libxi6

Bug#1042411: closed by Thomas Lange (found problem)

[Marc Lehmann]

On Sat, Feb 17, 2024 at 08:54:03PM +, Debian Bug Tracking System 
 wrote:
> the problem is that on your computer you have a directory /usr/etc.

Interesting bug.

> Then rinse uses this wrong path because it thinks a local rinse
> installation is available. Please remove this /usr/etc, which is not a
> usual directory.

I am not sure what you mean or why you closed this bug - asking me to
delete any "unusual" directories does not fix the bug in rinse. It's
completely legal in debian to have this directorxy, and some software
requires it - I cannot delete it without breaking other software.

The bug here is clearly in rinse - /usr/etc is not a debian-mandated
directory, so rinse must not rely on it being preesent or absent (see the
debian filesysytem heirarchy standard for example).

Asking users to delete random directories to work around a bug in your
package without fixing it is not acceptable.

Bug#1064049: gnome: When using Debian/KDE and installing Gnome via apt, Gnome uses KDE decorations & mouse pointer

[Marc Fouquet]

Package: gnome
Version: 1:43+1
Severity: normal
Tags: d-i
X-Debbugs-Cc: marc.fouq...@gmx.de

Dear Maintainer,

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

   * What led up to the situation?

In installed Debian from the Image with KDE.

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

Changed my mind and used "apt install gnome".

   * What was the outcome of this action?

Gnome works, but windows have KDE decorations and the desktop uses the KDE 
mouse pointer. There is no immediately obvious way to change this.

   * What outcome did you expect instead?

That gnome looks like gnome.

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


-- 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-18-amd64 (SMP w/8 CPU threads; PREEMPT)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.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 gnome depends on:
ii  avahi-daemon 0.8-10
ii  cheese   43.0-1
ii  cups-pk-helper   0.2.6-1+b1
ii  desktop-base 12.0.6+nmu1~deb12u1
ii  evolution3.46.4-2
ii  evolution-plugins3.46.4-2
ii  file-roller  43.0-1
ii  gnome-calendar   43.1-2
ii  gnome-clocks 43.0-1
ii  gnome-color-manager  3.36.0-1+b1
ii  gnome-core   1:43+1
ii  gnome-maps   43.5-2~deb12u1
ii  gnome-music  42.1-1
ii  gnome-sound-recorder 43~beta-1
ii  gnome-tweaks 42~beta-4
ii  gnome-weather43.0-1
ii  gstreamer1.0-libav   1.22.0-2
ii  gstreamer1.0-plugins-ugly1.22.0-2+deb12u1
ii  libgsf-bin   1.14.50-1
ii  libproxy1-plugin-networkmanager  0.4.18-1.2
ii  libreoffice-calc 4:7.4.7-1+deb12u1
ii  libreoffice-gnome4:7.4.7-1+deb12u1
ii  libreoffice-impress  4:7.4.7-1+deb12u1
ii  libreoffice-writer   4:7.4.7-1+deb12u1
ii  network-manager-gnome1.30.0-2
ii  orca 43.1-1
ii  rhythmbox3.4.6-2+b1
ii  rhythmbox-plugin-cdrecorder  3.4.6-2+b1
ii  rhythmbox-plugins3.4.6-2+b1
ii  rygel-playbin0.42.1-1
ii  rygel-tracker0.42.1-1
ii  seahorse 43.0-1
ii  shotwell 0.30.17-1+b1
ii  simple-scan  42.5-2
ii  totem-plugins43.0-2
ii  xdg-user-dirs-gtk0.11-1

Versions of packages gnome recommends:
ii  gnome-games   1:43+1
ii  gnome-initial-setup   43.2-6
ii  gnome-remote-desktop  43.3-1
ii  transmission-gtk  3.00-2.1+deb12u1

Versions of packages gnome suggests:
pn  alacarte  
pn  empathy   
pn  firefox-esr-l10n-all | firefox-l10n-all   
pn  goobox | sound-juicer 
pn  polari
pn  vinagre   
pn  webext-ublock-origin-firefox | webext-ublock-origin-chromium  

Versions of packages gnome-core depends on:
ii  adwaita-icon-theme43-1
ii  at-spi2-core  2.46.0-5
ii  baobab43.0-1
ii  dconf-cli 0.40.0-4
ii  dconf-gsettings-backend   0.40.0-4
ii  eog   43.2-1
ii  evince43.1-2+b1
ii  evolution-data-server 3.46.4-2
ii  fonts-cantarell   0.303.1-1
ii  gdm3  43.0-3
ii  gkbd-capplet  3.28.1-1
ii  glib-networking   2.74.0-4
ii  gnome-backgrounds 43.1-1
ii  gnome-bluetooth-sendto42.5-3
ii  gnome-calculator  1:43.0.1-2
ii  gnome-characters  43.1-1+deb12u1
ii  gnome-contacts43.1-1
ii  gnome-control-center  1:43.6-2~deb12u1
ii  gnome-disk-utility43.0-1
ii  gnome-font-viewer 43.0-1
ii  gnome-keyring 42.1-1+b2
ii  gnome-logs43.0-1
ii  gnome-menus   3.36.0-1.1
ii  gnome-online-accounts 3.46.0-1
ii  gnome-session 43.0-1+deb12u1
ii  gnome-settings-daemon 43.0-4
ii  gnome-shell   43.9-0+deb12u1
ii  gnome-shell-extensions43.1-1
ii  gnome-software43.5-1~deb12u1
ii  gnome-sushi   43.0-2
ii  gnome-system-monitor  42.0-2
ii  gnome-terminal   

Bug#1064048: fcitx5: No german keyboard after fresh Debian/KDE install

[Marc Fouquet]

Package: fcitx5
Version: 5.0.21-3
Severity: important
Tags: l10n d-i
X-Debbugs-Cc: marc.fouq...@gmx.de

Dear Maintainer,

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

   * What led up to the situation?

A fresh install of Debian/KDE from the Live CD.

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

Selected german locale during the installation.

   * What was the outcome of this action?

KDE menu text was german, but the keyboard layout was not. The appropriate KDE 
setting dialog (region/language) complained about missing fcitx.
At the time I had no idea what this was. A non-technical user would have 
aborted the installation attempt at this point and switched back to windows.

To solve this, I dis the following:

> apt install fcitx5
- Add fcitx5 to KDE autorun.
> fcitx5-config

I am still not sure, if this was the intended way, the KDE settings page for 
the input method is still not functional (the error message is gone, but there 
are no options to select).
Only fcitx5-config works for changing keyboard options.

   * What outcome did you expect instead?

- Having a working german keyboard when selecting it in the installer.
- The keykoard selection (Regionaleinstellungen => Eingabemethode) in the KDE 
settings App should be functional.

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


-- Package-specific info:

--- Fcitx5 Diagnose output ---

# System Info:
1.  `uname -a`:

Linux kamino 6.1.0-18-amd64 #1 SMP PREEMPT_DYNAMIC Debian 6.1.76-1 
(2024-02-01) x86_64 GNU/Linux

2.  `lsb_release -a`:

Distributor ID: Debian
Description:Debian GNU/Linux 12 (bookworm)
Release:12
Codename:   bookworm

3.  `lsb_release -d`:

Description:Debian GNU/Linux 12 (bookworm)

4.  `/etc/lsb-release`:

`/etc/lsb-release` not found.

5.  `/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/;

6.  Desktop Environment:

Desktop environment is `kde`.

7.  XDG SESSION TYPE:

XDG_SESSION_TYPE='x11'

8.  Bash Version:

BASH_VERSION='5.2.15(1)-release'

# Environment:
1.  DISPLAY:

DISPLAY=':0'


WAYLAND_DISPLAY=''

2.  Keyboard Layout:

1.  `setxkbmap`:

xkb_keymap {
xkb_keycodes  { include "evdev+aliases(qwertz)" };
xkb_types { include "complete"  };
xkb_compat{ include "complete"  };
xkb_symbols   { include "pc+de+inet(evdev)" };
xkb_geometry  { include "pc(pc104)" };
};

2.  `xprop`:

_XKB_RULES_NAMES(STRING) = "evdev", "pc104", "de", "", ""

3.  Locale:

1.  All locales:

C
C.utf8
POSIX
de_DE.utf8

2.  Current locale:

LANG=de_DE.UTF-8
LANGUAGE=
LC_CTYPE="C"
LC_NUMERIC="C"
LC_TIME="C"
LC_COLLATE="C"
LC_MONETARY="C"
LC_MESSAGES="C"
LC_PAPER="C"
LC_NAME="C"
LC_ADDRESS="C"
LC_TELEPHONE="C"
LC_MEASUREMENT="C"
LC_IDENTIFICATION="C"
LC_ALL=C

4.  Directories:

1.  Home:

/home/fouquet

2.  `${XDG_CONFIG_HOME}`:

Environment variable `XDG_CONFIG_HOME` is not set.

Current value of `XDG_CONFIG_HOME` is `~/.config` 
(`/home/fouquet/.config`).

3.  Fcitx5 Settings Directory:

Current fcitx5 settings directory is `~/.config/fcitx5` 
(`/home/fouquet/.config/fcitx5`).

5.  Current user:

The script is run as fouquet (1000).

# Fcitx State:
1.  executable:

Found fcitx5 at `/usr/bin/fcitx5`.

2.  version:

Fcitx version: `5.0.21`

3.  process:

Found 2 fcitx5 processes:

   1913 fcitx5
  44115 fcitx5

4.  `fcitx5-remote`:

`fcitx5-remote` works properly.

5.  DBus interface:

Using `dbus-send` to check dbus.

Owner of DBus name `org.fcitx.Fcitx5` is `:1.62`.

PID of DBus name `org.fcitx.Fcitx5` owner is `1913`.

Debug information from dbus:

   Group [x11::0] has 47 InputContext(s)
  IC [18b56efa163542dea5eabc524a55315b] program: frontend:ibus cap:52 
focus:0
  IC [d29f070f0f274233a19f76ddb41d8df3] program: frontend:ibus cap:52 
focus:0
  IC [b5824b1e5a93484898286a3506e09689] program: frontend:ibus cap:52 
focus:0
  IC [e4ea6071605e40dba968e201f9dd9971] program: frontend:ibus cap:12 
focus:0
  IC [b79c3e929e06497797ba6cec2271592e] program: frontend:ibus cap:12 
focus:0
  IC [b2ec1c4d42a24eff8d122de5368e2dd4] program: 

Bug#1064000: unzip: Unzip fails on Microsoft ZIP64 files

[Marc Deslauriers]

Package: unzip
Severity: normal
Tags: patch
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu noble ubuntu-patch




*** /tmp/tmp5xum1hdh/bug_body

unzip rejects Microsoft OneDrive zip files. See the detailed explanation here:

https://www.bitsgalore.org/2020/03/11/does-microsoft-onedrive-export-large-ZIP-files-that-are-corrupt

tl;dr;
Microsoft mishandles the "Total number of disks" field when using the ZIP64 
extension. It should start at 1, they use 0, which isn't a valid value. Unzip 
doesn't properly handle the invalid value.


In Ubuntu, the attached patch was applied to achieve the following:


  * Properly handle Microsoft ZIP64 file (LP: #2051952)
- debian/patches/handle_windows_zip64.patch: ignore invalid "Total
  number of disks" field in process.c.


Thanks for considering the patch.


-- System Information:
Debian Release: bookworm/sid
  APT prefers jammy-updates
  APT policy: (500, 'jammy-updates'), (500, 'jammy-security'), (500, 'jammy'), 
(100, 'jammy-backports')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 6.1.0-1029-oem (SMP w/20 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
diff -Nru unzip-6.0/debian/patches/handle_windows_zip64.patch 
unzip-6.0/debian/patches/handle_windows_zip64.patch
--- unzip-6.0/debian/patches/handle_windows_zip64.patch 1969-12-31 
19:00:00.0 -0500
+++ unzip-6.0/debian/patches/handle_windows_zip64.patch 2024-02-01 
10:48:08.0 -0500
@@ -0,0 +1,18 @@
+Description: Properly handle Microsoft ZIP64 file by ignoring invalid
+ "Total number of disks" field
+Origin: https://sourceforge.net/p/infozip/bugs/42/
+Bug: https://sourceforge.net/p/infozip/bugs/42/
+Bug-Ubuntu: https://bugs.launchpad.net/ubuntu/+source/unzip/+bug/2051952
+Author: Roy Tam
+
+--- a/process.c
 b/process.c
+@@ -1281,7 +1281,7 @@ static int find_ecrec64(__G__ searchlen)
+ fprintf(stdout,"\nnumber of disks (ECR) %u, (ECLOC64) %lu\n",
+ G.ecrec.number_this_disk, ecloc64_total_disks); fflush(stdout);
+ #endif
+-if ((G.ecrec.number_this_disk != 0x) &&
++if ((G.ecrec.number_this_disk != 0x) && ecloc64_total_disks &&
+ (G.ecrec.number_this_disk != ecloc64_total_disks - 1)) {
+   /* Note: For some unknown reason, the developers at PKWARE decided to
+  store the "zip64 total disks" value as a counter starting from 1,
diff -Nru unzip-6.0/debian/patches/series unzip-6.0/debian/patches/series
--- unzip-6.0/debian/patches/series 2023-05-30 06:34:18.0 -0400
+++ unzip-6.0/debian/patches/series 2024-02-01 10:46:59.0 -0500
@@ -27,3 +27,4 @@
 26-cve-2019-13232-fix-bug-in-uzinflate.patch
 27-zipgrep-avoid-test-errors.patch
 28-cve-2022-0529-and-cve-2022-0530.patch
+handle_windows_zip64.patch

Bug#1063808: simple-scan: Unable to load items from the cursor theme adwaita-icon-theme

[Jean-Marc]

Package: simple-scan
Version: 44.0-1
Severity: normal
X-Debbugs-Cc: jean-m...@6jf.be

Dear Maintainer,

Since adwaita-icon-theme upgraded to 46~beta-1, I get issues when cropping a 
scanned document.

The mouse cursor does not change when trying to grap the crop-region-selector 
to resize it.


Logs from simple-scan:
$ LANG=C simple-scan
Gdk-Message: 17:42:28.355: Unable to load bottom_side from the cursor theme
Gdk-Message: 17:42:28.370: Unable to load hand1 from the cursor theme
Gdk-Message: 17:42:28.969: Unable to load bottom_side from the cursor theme
Gdk-Message: 17:42:29.021: Unable to load arrow from the cursor theme
Gdk-Message: 17:42:29.224: Unable to load bottom_left_corner from the cursor 
theme
Gdk-Message: 17:42:29.593: Unable to load left_side from the cursor theme
Gdk-Message: 17:42:29.719: Unable to load bottom_left_corner from the cursor 
theme
Gdk-Message: 17:42:30.253: Unable to load bottom_side from the cursor theme
Gdk-Message: 17:42:30.271: Unable to load hand1 from the cursor theme
Gdk-Message: 17:42:35.285: Unable to load bottom_side from the cursor theme
Gdk-Message: 17:42:35.398: Unable to load arrow from the cursor theme
Gdk-Message: 17:42:36.161: Unable to load bottom_side from the cursor theme
Gdk-Message: 17:42:36.507: Unable to load bottom_right_corner from the cursor 
theme
Gdk-Message: 17:42:42.130: Unable to load arrow from the cursor theme
Gdk-Message: 17:43:51.187: Unable to load hand1 from the cursor theme
Gdk-Message: 17:43:51.283: Unable to load top_side from the cursor theme
Gdk-Message: 17:43:51.312: Unable to load arrow from the cursor theme

Regards,

Jean-Marc


-- Package-specific info:

-- System Information:
Debian Release: trixie/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)

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

Versions of packages simple-scan depends on:
ii  dbus-user-session [default-dbus-session-bus]  1.14.10-4
ii  dbus-x11 [dbus-session-bus]   1.14.10-4
ii  dconf-gsettings-backend [gsettings-backend]   0.40.0-4+b1
ii  libc6 2.37-15
ii  libcairo2 1.18.0-1+b1
ii  libcolord21.4.6-5
ii  libgdk-pixbuf-2.0-0   2.42.10+dfsg-3+b1
ii  libglib2.0-0  2.78.3-2
ii  libgtk-3-03.24.41-1
ii  libgusb2  0.4.8-1
ii  libhandy-1-0  1.8.3-1
ii  libpackagekit-glib2-181.2.8-1+b1
ii  libsane1  1.2.1-7+b1
ii  libwebp7  1.3.2-0.3
ii  libwebpmux3   1.3.2-0.3
ii  xdg-utils 1.1.3-4.1
ii  zlib1g1:1.3.dfsg-3+b1

simple-scan recommends no packages.

simple-scan suggests no packages.

-- no debconf information

Bug#1063640: Processed: Re: Bug#1063640: adwaita-icon-theme: cursor theme not found

[Jean-Marc]

hi Jeremy,

Le 12/02/24 à 13:21, Debian Bug Tracking System a écrit :

Processing control commands:


found -1 45.3-2

Bug #1063640 {Done: Jeremy Bícha } [src:mutter] 
adwaita-icon-theme: cursor theme not found
Marked as found in versions mutter/45.3-2 and reopened.

fixed -1 44.8-3

Bug #1063640 [src:mutter] adwaita-icon-theme: cursor theme not found
Marked as fixed in versions mutter/44.8-3.


I think it is not fully fixed in mutter 44.8-3.

$ LANG=C apt policy mutter
mutter:
  Installed: 44.8-3

I got problems running the simple-scan application and trying to crop 
the scanned document.  The mouse cursor does not change when trying to 
grap the crop-region-selector to resize it.


$ LANG=C simple-scan
Gdk-Message: 17:42:28.355: Unable to load bottom_side from the cursor theme
Gdk-Message: 17:42:28.370: Unable to load hand1 from the cursor theme
Gdk-Message: 17:42:28.969: Unable to load bottom_side from the cursor theme
Gdk-Message: 17:42:29.021: Unable to load arrow from the cursor theme
Gdk-Message: 17:42:29.224: Unable to load bottom_left_corner from the 
cursor theme

Gdk-Message: 17:42:29.593: Unable to load left_side from the cursor theme
Gdk-Message: 17:42:29.719: Unable to load bottom_left_corner from the 
cursor theme

Gdk-Message: 17:42:30.253: Unable to load bottom_side from the cursor theme
Gdk-Message: 17:42:30.271: Unable to load hand1 from the cursor theme
Gdk-Message: 17:42:35.285: Unable to load bottom_side from the cursor theme
Gdk-Message: 17:42:35.398: Unable to load arrow from the cursor theme
Gdk-Message: 17:42:36.161: Unable to load bottom_side from the cursor theme
Gdk-Message: 17:42:36.507: Unable to load bottom_right_corner from the 
cursor theme

Gdk-Message: 17:42:42.130: Unable to load arrow from the cursor theme
Gdk-Message: 17:43:51.187: Unable to load hand1 from the cursor theme
Gdk-Message: 17:43:51.283: Unable to load top_side from the cursor theme
Gdk-Message: 17:43:51.312: Unable to load arrow from the cursor theme

Regards,

--
Jean-Marc


OpenPGP_signature.asc
Description: OpenPGP digital signature

Bug#1063640: adwaita-icon-theme: cursor theme not found

[Jean-Marc]

Hi Guy,

On Mon, 12 Feb 2024 09:45:26 +0200 Guy Rutenberg 
 wrote:

Package: mutter
Version: 44.8-3
Followup-For: Bug #1063640
X-Debbugs-Cc: guyrutenb...@gmail.com

Dear Maintainer,

I just experienced the same bug using mutter 44.8-3 and adwaita-icon-them
46~beta-1. Reverting back to adwaita-icon-theme 45.0-2 resolved the issue.


Did you upgrade your theme inside a running gnome session ?

Because in this case, you first need to log out/log in to really use 
mutter 44.8-3.


Meaning you will get this issue until you re-start a new session.


Guy


--
Jean-Marc


OpenPGP_signature.asc
Description: OpenPGP digital signature

Bug#1063369: aide: Don't require s-nail to send email, other setups (e.g. postfix+bsd-mailx) work as well

[Marc Haber]

Hi Timo,

On Thu, Feb 08, 2024 at 10:56:07PM +0100, Timo Sigurdsson wrote:
> Marc Haber schrieb am 07.02.2024 15:08 (GMT +01:00):
> > This is not correct, MAILCMD is honored.
> Yes, that's how I worked around it. But that wasn't needed before Bookworm.

Yes. It's a corollary of the changes we did to the package during the
bookworm cycle. Before, the aide processes were running as root and
everything was easier. Now, we're not running as root by default but
need special measures to be able to send mail.

> > Documentation says:
> > 
> > | The daily aide check will automatically select the method of sending
> > | mail according to the rules documented above.  The variable MAILCMD in
> > | /etc/default/aide can be used to override these rules.  If you know
> > | that your mail(1) works in a scenario where the automatism refuses to
> > | use mail(1), setting MAILCMD to the path to mail(1) manually will force
> > | the script to use mail(1).  If you need more flexibility and/or would
> > | prefer to have additional methods of delivering the report supported
> > | by the package, please file a wishlist bug.
> 
> I somehow did not fully read that paragraph. That is actually quite close to 
> what I proposed, except I'd prefer the script not trying to be too smart 
> here, but it's fair enough, I think.

Without the script being smart, the error messages that happen are
totally misleading. That's why I added so much smartness. I don't
remember the exact messages, but I remember that the error messages led
me into a totally wrong direction when I was developing the new
mechanisms.

> >> The downside is
> >> that my custom MAILSUBJ is ignored now since Debian Bookworm.
> > 
> > MAILSUBJ is honored in the code of dailyaidecheck:
> > if [ -n "${MAILCMD:-}" ]; then
> > eval "${MAILCMD} -s \"${MAILSUBJ}\" \"${MAILTO}\"" || RET=$?
> > 
> > mailx is documented to honor the -s parameter. Please verify that mailx
> > is called correctly by our code and file an appropriate bug either
> > against aide or mailx.
> 
> You are right. I actually confused the change of my MAILSUBJ - it is honored 
> - with the new sender name (since it's not root anymore that sends mail). So, 
> everything works as expected.

Would you mind elaborating about the sender name? Maybe it makes sense
to add more flexibility here?

> Sorry for the noise :(

No noise at all, you got me reflecting and thinking about those things
again. That's good.

Never having used Postfix, I wasn't aware that there are MTAs that can
work without /usr/lib/sendmail being suid. Is it worth re-wording the
docs? I'd rather not touch the actual code by finding out whether
/usr/lib/sendmail needs suid or not and adapting to that finding, but
maybe it would help to re-word the docs. Would you want to suggest
alternative wording?

Greetings
Marc

-- 
-
Marc Haber | "I don't trust Computers. They | Mailadresse im Header
Leimen, Germany|  lose things."Winona Ryder | Fon: *49 6224 1600402
Nordisch by Nature |  How to make an American Quilt | Fax: *49 6224 1600421

Bug#1063369: aide: Don't require s-nail to send email, other setups (e.g. postfix+bsd-mailx) work as well

[Marc Haber]

On Tue, Feb 06, 2024 at 10:22:35PM +0100, Timo Sigurdsson wrote:
> Package: aide
> Version: 0.18.3-1+deb12u2

Just for the record: Changing this in bookworm won't happen.

> since Debian Bookworm, aide refuses to send emails by default if
> s-nail is not installed.

This is not correct, MAILCMD is honored. Documentation says:

| The daily aide check will automatically select the method of sending
| mail according to the rules documented above.  The variable MAILCMD in
| /etc/default/aide can be used to override these rules.  If you know
| that your mail(1) works in a scenario where the automatism refuses to
| use mail(1), setting MAILCMD to the path to mail(1) manually will force
| the script to use mail(1).  If you need more flexibility and/or would
| prefer to have additional methods of delivering the report supported
| by the package, please file a wishlist bug.

> The documentation (README.Debian.gz in aide-common) falsely claims
> that /usr/lib/sendmail requires suid and that this affects bsd-mailx.

> Well, first of all, bsd-mailx doesn't even provide /usr/lib/sendmail,
> so this is misleading.

as far as I know, bsd-mailx invokes /usr/lib/sendmail.

> In addition, there are (popular) MTAs that don't install
> /usr/lib/sendmail with the suid bit set, e.g. postfix.

The default MTA does it this way.

> I have postfix configured to send out mail via a smarthost only,
> without any local mail delivery. I also disabled the smtpd daemon
> listening on port 25, so mail is sent via mailx/sendmail. And that
> works just fine with aide, even as non-root under systemd. I have set
> MAILCMD="/usr/bin/mailx" in /etc/default/aide in order to "convince"
> aide to send mail despite not having s-nail installed.

That is the way it is documented to work, yes.

> The downside is
> that my custom MAILSUBJ is ignored now since Debian Bookworm.

MAILSUBJ is honored in the code of dailyaidecheck:
if [ -n "${MAILCMD:-}" ]; then
eval "${MAILCMD} -s \"${MAILSUBJ}\" \"${MAILTO}\"" || RET=$?

mailx is documented to honor the -s parameter. Please verify that mailx
is called correctly by our code and file an appropriate bug either
against aide or mailx.

> I would suggest to not hardcode a (soft) dependency on s-nail into the
> script. I think it would be better to merely warn people upon
> upgrading that sending mail may not work as non-root under systemd if
> the MTA requries suid and that s-nail might solve that. But don't add
> artificial restrictions or checks. If mail delivery breaks for some,
> then they know they need s-nail, but the rest can just keep using
> their known MTA setup.

This is impossible to get right since there are millions of ways to
configure local mail. Setting MAILCMD to a non-empty version is the
documented way to tell the script "use this, I know it works". Does this
work, or does it not work?

Greetings
Marc

-- 
-
Marc Haber | "I don't trust Computers. They | Mailadresse im Header
Leimen, Germany|  lose things."Winona Ryder | Fon: *49 6224 1600402
Nordisch by Nature |  How to make an American Quilt | Fax: *49 6224 1600421

Bug#1062084: Wishlist: please package new upstream version 4.7.2

[Marc G.]

Package: texstudio
Version: 4.3.1+ds-3
Severity: wishlist
X-Debbugs-Cc: garbage_collec...@nym.hush.com

Dear Mr Jampen,

please refer to the latest developments in Texstudio. The current version on
debian is 1 year old w.r.t. the upstream version. Can you please package the
new version? It compiles fine on my sid machine with Qt5 and Qt6.

Regards,
Marc


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

Kernel: Linux 6.6.13-amd64 (SMP w/12 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
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 texstudio depends on:
ii  libc62.37-15
ii  libgcc-s114-20240127-1
ii  libhunspell-1.7-01.7.2+really1.7.2-10
ii  libphonon4qt5-4  4:4.12.0-3
ii  libpoppler-qt5-1 22.12.0-2+b1
ii  libqt5concurrent55.15.10+dfsg-6
ii  libqt5core5a 5.15.10+dfsg-6
ii  libqt5gui5   5.15.10+dfsg-6
ii  libqt5network5   5.15.10+dfsg-6
ii  libqt5printsupport5  5.15.10+dfsg-6
ii  libqt5qml5   5.15.10+dfsg-2
ii  libqt5svg5   5.15.10-2
ii  libqt5widgets5   5.15.10+dfsg-6
ii  libqt5xml5   5.15.10+dfsg-6
ii  libqtermwidget5-11.4.0-1
ii  libquazip5-1 0.9.1-3
ii  libstdc++6   14-20240127-1
ii  libx11-6 2:1.8.7-1
ii  phonon4qt5   4:4.12.0-3
ii  zlib1g   1:1.3.dfsg-3+b1

Versions of packages texstudio recommends:
ii  adwaita-qt 1.4.2-3+b1
ii  texlive-base   2023.20231207-1
ii  texlive-latex-base 2023.20231207-1
ii  texlive-latex-recommended  2023.20231207-1
ii  texstudio-doc  4.3.1+ds-3
ii  texstudio-l10n 4.3.1+ds-3

Versions of packages texstudio suggests:
ii  hunspell-ar [hunspell-dictionary]3.2-1.2
ii  hunspell-be [hunspell-dictionary]0.60-1
ii  hunspell-bg [hunspell-dictionary]1:7.5.0-1
ii  hunspell-bs [hunspell-dictionary]1:7.5.0-1
ii  hunspell-ca [hunspell-dictionary]3.0.8+repack1-1
ii  hunspell-cs [hunspell-dictionary]1:7.5.0-1
ii  hunspell-da [hunspell-dictionary]1:7.5.0-1
ii  hunspell-de-at [hunspell-dictionary] 20161207-11
ii  hunspell-de-ch [hunspell-dictionary] 20161207-11
ii  hunspell-de-de [hunspell-dictionary] 20161207-11
ii  hunspell-el [hunspell-dictionary]1:7.5.0-1
ii  hunspell-en-gb [hunspell-dictionary] 1:7.5.0-1
ii  hunspell-en-us [hunspell-dictionary] 1:2020.12.07-2
ii  hunspell-eu [hunspell-dictionary]5.4.10-1
ii  hunspell-fr-classical [hunspell-dictionary]  1:7.0-1
ii  hunspell-gl [hunspell-dictionary]1:7.5.0-1
ii  hunspell-gu [hunspell-dictionary]1:7.5.0-1
ii  hunspell-hi [hunspell-dictionary]1:7.5.0-1
ii  hunspell-hr [hunspell-dictionary]1:7.5.0-1
ii  hunspell-hu [hunspell-dictionary]1:7.5.0-1
ii  hunspell-id [hunspell-dictionary]1:7.5.0-1
ii  hunspell-is [hunspell-dictionary]1:7.5.0-1
ii  hunspell-it [hunspell-dictionary]1:7.5.0-1
ii  hunspell-kk [hunspell-dictionary]1.1-3
ii  hunspell-kmr [hunspell-dictionary]   1:7.5.0-1
ii  hunspell-ko [hunspell-dictionary]0.7.94-1
ii  hunspell-lt [hunspell-dictionary]1:7.5.0-1
ii  hunspell-lv [hunspell-dictionary]1.4.0-5
ii  hunspell-ne [hunspell-dictionary]1:7.5.0-1
ii  hunspell-nl [hunspell-dictionary]2:2.20.19-2
ii  hunspell-pl [hunspell-dictionary]1:7.5.0-1
ii  hunspell-pt-br [hunspell-dictionary] 1:7.5.0-1
ii  hunspell-pt-pt [hunspell-dictionary] 1:7.5.0-1
ii  hunspell-ro [hunspell-dictionary]1:7.5.0-1
ii  hunspell-ru [hunspell-dictionary]1:7.5.0-1
ii  hunspell-si [hunspell-dictionary]1:7.5.0-1
ii  hunspell-sl [hunspell-dictionary]1:7.5.0-1
ii  hunspell-sr [hunspell-dictionary]1:7.5.0-1
ii  hunspell-sv [hunspell-dictionary]1:7.5.0-1
ii  hunspell-te [hunspell-dictionary]1:7.5.0-1
ii  hunspell-th [hunspell-dictionary]1:7.5.0-1
ii  hunspell-vi [hunspell-dictionary]1:7.5.0-1
ii  myspell-eo [hunspell-dictionary] 2.1.2000.02.25-61
ii  myspell-es [hunspell-dictionary] 1.11-20
ii  myspell-et [hunspell-dictionary] 1:20030606-32
ii  mythes-cs [mythes-thesaurus] 1:7.5.0-1
ii  mythes-de [mythes-thesaurus] 20160424-4
ii  mythes-de-ch [mythes-thesaurus]  20160424-4
ii  mythes-en-us [mythes-thesaurus]  1:7.5.0-1
ii  mythes-fr [mythes-thesaurus] 1:7.5.0-1
ii  mythes-it [mythes-thesaurus

Bug#1061832: kitty keyboard shortcut is not delivered to kitty window in focus

[Marc Kleine-Budde]

Package: kitty
Version: 0.32.1-1
Severity: normal

Dear Maintainer,

   * What led up to the situation?
 updating from 0.21.2-2 to basically anything newer
   * What exactly did you do (or not do) that was effective (or
 ineffective)?

 I start several kitty windows with "kitty -1".
 kitty.conf contains "map kitty_mod+t new_tab".

 After a bit switching back and forth between several other programs,
 coming back to the 2nd kitty window the normal key presses are delivered
 to the shell as usual, but when pressing kitty_mod+t the new tab is not
 opened in the kitty window in focus, but in the other (I think the first)
 kitty window.

 Same behaviour for all other shortcuts, like move_tab_forward,
 move_tab_backward, etc...

   * What was the outcome of this action?

 New tab is opened in not in focus kitty window.

   * What outcome did you expect instead?

 New tab should open in the kitty window in focus.

regards,
Marc

-- System Information:
Debian Release: trixie/sid
  APT prefers testing-debug
  APT policy: (700, 'testing-debug'), (700, 'testing'), (500, 
'unstable-debug'), (500, 'stable-updates'), (500, 'stable-security'), (500, 
'stable-debug'), (500, 'proposed-updates-debug'), (500, 'proposed-updates'), 
(500, 'oldstable-updates'), (500, 'oldstable-security'), (500, 
'oldoldstable-updates'), (500, 'oldoldstable'), (500, 'unstable'), (500, 
'stable'), (500, 'oldstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386, armhf, arm64

Kernel: Linux 6.6.11-amd64 (SMP w/4 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 kitty depends on:
ii  kitty-shell-integration  0.32.1-1
ii  kitty-terminfo   0.32.1-1
ii  libc62.37-14
ii  libdbus-1-3  1.14.10-4
ii  libharfbuzz0b8.3.0-2
ii  liblcms2-2   2.14-2
ii  libpng16-16  1.6.40-3
ii  libpython3.113.11.7-2
ii  libssl3  3.1.4-2
ii  libwayland-client0   1.22.0-2.1
ii  libx11-6 2:1.8.7-1
ii  libx11-xcb1  2:1.8.7-1
ii  libxcursor1  1:1.2.1-1
ii  libxkbcommon-x11-0   1.6.0-1
ii  libxkbcommon01.6.0-1
ii  libxxhash0   0.8.2-2
ii  python3  3.11.6-1
ii  python3.11   3.11.7-2
ii  zlib1g   1:1.3.dfsg-3+b1

Versions of packages kitty recommends:
pn  kitty-doc 
ii  libcanberra0  0.30-11

Versions of packages kitty suggests:
ii  graphicsmagick-imagemagick-compat [imagemagick]  1.4+really1.3.42-1

-- no debconf information

Bug#1006945: please consider supporting wildcards

[Marc Haber]

On Fri, Oct 07, 2022 at 09:32:31PM +0200, Niels Thykier wrote:
> I appreciate that it is unwieldly to maintain that links file.  However, I
> also feel like it is a special case that could just as easily be solved by
> having an executable debhelper config file.

I was not aware of that feature. I have done this in adduser now.
Thanks.

Greetings
Marc

Bug#835565: mr list does not work

[Marc Haber]

 {
LANG=C bzr info | egrep -q '^Checkout'
}
lazy() {
if [ -d "$MR_REPO" ]; then
return 1
else
return 0
fi
}

<<
mr skip test: running skip test >>[ "$1" = update ] && ! hours_since "$1" 8<<

mr library now: >>

error() {
echo "mr: $@" >&2
exit 1
}
warning() {
echo "mr (warning): $@" >&2
}
info() {
echo "mr: $@" >&2
}
hours_since() {
if [ -z "$1" ] || [ -z "$2" ]; then
error "mr: usage: hours_since action num"
fi
for dir in .git .svn .bzr CVS .hg _darcs _FOSSIL_ .fslckout; do
if [ -e "$MR_REPO/$dir" ]; then
flagfile="$MR_REPO/$dir/.mr_last$1"
break
fi
done
if [ -z "$flagfile" ]; then
for dir in refs/heads; do
if [ -e "$MR_REPO/$dir" ]; then
flagfile="$MR_REPO/.mr_last$1"
break
fi
done
fi
if [ -z "$flagfile" ]; then
error "cannot determine flag filename"
fi
delta=`perl -wle 'print -f shift() ? int((-M _) * 24) : ' "$flagfile"`
if [ "$delta" -lt "$2" ]; then
return 1
else
touch "$flagfile"
return 0
fi
}
is_bzr_checkout() {
LANG=C bzr info | egrep -q '^Checkout'
}
lazy() {
if [ -d "$MR_REPO" ]; then
return 1
else
return 0
fi
}

<<
mr skip test: running skip test >>[ "$1" = update ] && ! hours_since "$1" 8<<
mr list: running list >>echo list<<
mr list: /home/mh/.config/vcsh/repo.d/mr.git
list

mr library now: >>

error() {
echo "mr: $@" >&2
exit 1
}
warning() {
echo "mr (warning): $@" >&2
}
info() {
echo "mr: $@" >&2
}
hours_since() {
if [ -z "$1" ] || [ -z "$2" ]; then
error "mr: usage: hours_since action num"
fi
for dir in .git .svn .bzr CVS .hg _darcs _FOSSIL_ .fslckout; do
if [ -e "$MR_REPO/$dir" ]; then
flagfile="$MR_REPO/$dir/.mr_last$1"
break
fi
done
if [ -z "$flagfile" ]; then
for dir in refs/heads; do
if [ -e "$MR_REPO/$dir" ]; then
flagfile="$MR_REPO/.mr_last$1"
break
fi
done
fi
if [ -z "$flagfile" ]; then
error "cannot determine flag filename"
fi
delta=`perl -wle 'print -f shift() ? int((-M _) * 24) : ' "$flagfile"`
if [ "$delta" -lt "$2" ]; then
return 1
else
touch "$flagfile"
return 0
fi
}
is_bzr_checkout() {
LANG=C bzr info | egrep -q '^Checkout'
}
lazy() {
if [ -d "$MR_REPO" ]; then
return 1
else
return 0
fi
}

<<
mr skip test: running skip test >>[ "$1" = update ] && ! hours_since "$1" 8<<

mr library now: >>

error() {
echo "mr: $@" >&2
exit 1
}
warning() {
echo "mr (warning): $@" >&2
}
info() {
echo "mr: $@" >&2
}
hours_since() {
if [ -z "$1" ] || [ -z "$2" ]; then
error "mr: usage: hours_since action num"
fi
for dir in .git .svn .bzr CVS .hg _darcs _FOSSIL_ .fslckout; do
if [ -e "$MR_REPO/$dir" ]; then
flagfile="$MR_REPO/$dir/.mr_last$1"
break
fi
done
if [ -z "$flagfile" ]; then
for dir in refs/heads; do
if [ -e "$MR_REPO/$dir" ]; then
flagfile="$MR_REPO/.mr_last$1"
break
fi
done
fi
if [ -z "$flagfile" ]; then
error "cannot determine flag filename"
fi
delta=`perl -wle 'print -f shift() ? int((-M _) * 24) : ' "$flagfile"`
if [ "$delta" -lt "$2" ]; then
return 1
else
touch "$flagfile"
return 0
fi
}
is_bzr_checkout() {
LANG=C bzr info | egrep -q '^Checkout'
}
lazy() {
if [ -d "$MR_REPO" ]; then
return 1
else
return 0
fi
}

<<
mr skip test: running skip test >>[ "$1" = update ] && ! hours_since "$1" 8<<

mr library now: >>

error() {
echo "mr: $@" >&2
exit 1
}
warning() {
echo "mr (warning): $@" >&2
}
info() {
echo "mr: $@" >&2
}
hours_since() {
if [ -z "$1" ] || [ -z "$2" ]; then
error "mr: usage: hours_since action num"
fi
for dir in .git .svn .bzr CVS .hg _darcs _FOSSIL_ .fslckout; do
if [ -e "$MR_REPO/$dir" ]; then
flagfile="$MR_REPO/$dir/.mr_last$1"
break
fi
done
if [ -z "$flagfile" ]; then
for dir in refs/heads; do
if [ -e "$MR_REPO/$dir" ]; then
flagfile="$MR_REPO/.mr_last$1"
break
fi
done
fi
if [ -z "$flagfile" ]; then
error "cannot determine flag filename"
fi
delta=`perl -wle 'print -f shift() ? int((-M _) * 24) : ' "$flagfile"`
if [ "$delta" -lt "$2" ]; then
return 1
else
touch "$flagfile"
return 0
fi
}
is_bzr_checkout() {
LANG=C bzr info | egrep -q '^Checkout'
}
lazy() {
if [ -d "$MR_REPO" ]; then
return 1
else
return 0
fi
}

<<
mr skip test: running skip test >>[ "$1" = update ] && ! hours_since "$1" 8<<

mr list: finished (8 ok)

> Could you try myrepos git master and report the results with both
> 'list = true' and 'list = echo list' with verbose mode turned on/off?

This is unfortunately currently beyond my resources. I havent been using
mr list quite often in the last years, so I would be fine with this
issue staying unhandled.

> In addition, lets eliminate some possibilities:
> 
>  * That something in your user account is causing this; please create a
>new user account, login to that from getty or your display manager,
>check out eight git repos, register each of them with myrepos and
>list the repositories.
>  * That something in your installation is causing this; please do the
>same test but do it after booting a Debian live image.
>  * That something in your hardware is causing this; please do the
>Debian live image test but do it on different hardware.

I see this on all systems I am using mr on. They, however, all have the
same set of repositories and they contain my dotfiles, so if this is
caused by one of my settings, it might be there everywhere.

I might debug more in depth in the next week, but don't hold your breath
about that.

Greetings
Marc

Bug#922533: please document location of accounting file

[Marc Haber]

On Sun, Feb 17, 2019 at 08:50:35PM +0100, Marc Haber wrote:
> my package atop needs to adapt itself to acct being installed or not. If
> acct is installed, atop reads from acct's log files, while establishing
> its own accounting interface it acct is not installed.

The situation seems to have settled down, and atop now seems to find the
accounting file okay. It has been like that for at least two stable
releases.

Feel free to close this bug report. Thanks for helping!

Greetings
Marc

Bug#864480: why is en_DK included but not en_DE?

[Marc Haber]

Control: tags -1 
thanks

On Fri, Jun 09, 2017 at 11:14:20AM +0200, Samuel Thibault wrote:
> So what you want is actually LC_LANG=de_DE LANGUAGE=en, right?

After revisiting some ancient things still maked as unsolved in my
notes, I have been running my system with that setting for a couple of
years now and it reasonably seems to do the thing I expect it to.

Maybe it is asking too much to have a setting to have T.M.D. date format
but english monthh names ;-)

For me this issue can be closed if you agree.

Greetings
Marc

Bug#1061170: sudo: sends mail when aborting

[Marc Haber]

Control: -1 wontfix upstream
thanks

On Sat, Jan 20, 2024 at 07:34:42AM +0100, Thorsten Glaser wrote:
> Package: sudo
> Version: 1.9.5p2-3+deb11u1

Just for the record: This is oldstable, and unlikely a security or an RC
issue. Flagging this as wontfix now.

> When typing “sudo somecommandwithatypo”, pressing Enter, and then
> realising you’d done a typo and hitting ^C to abort, sudo sends an
> eMail that “a password is required” nowadays.
> 
> This is a regression against older versions which did not send an
> eMail in those cases.

It is a behavior change that looks like it was intended by upstream.
sudo is unlikely to change this behavior, especially if we obviously had
two stable releases with the behavior that you are complaining about
now.

Please discuss this with upstream. If they decide to change, Debian
might follow along. I'd really like to see their arguments.

Greetings
Marc

-- 
-----
Marc Haber | "I don't trust Computers. They | Mailadresse im Header
Leimen, Germany|  lose things."Winona Ryder | Fon: *49 6224 1600402
Nordisch by Nature |  How to make an American Quilt | Fax: *49 6224 1600421

Bug#1053348: atop gets a segmentation fault

[Marc Haber]

On Mon, Oct 02, 2023 at 12:50:04PM +0200, Tiger!P wrote:
> I ran `atop 2` for some time and then it got a segmentation fault. Because it 
> didn't create a core file, I changed settings to get a core file and started 
> atop in the same way.

Does this still happen with the new atop version in sid?

Greeting
Marc

Bug#1060373: texstudio: segfault when changing any setting

[marc]

Package: texstudio
Version: 4.3.1+ds-3
Severity: important
X-Debbugs-Cc: mg-2...@nym.hush.com

Dear Maintainer,

on two debian sid systems I get a segmentation fault when changing any setting.
Actually even if I press cancel on the settings dialog I get a crash.

This is a bit of a moot point because the current upstream version is more than
a year ahead and doesn't have this problem.

Suggestion: update package to upstream stable version 4.72
Best regards,
Marc Graham


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

Kernel: Linux 6.6.9-amd64 (SMP w/8 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
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 texstudio depends on:
ii  libc62.37-13
ii  libgcc-s113.2.0-9
ii  libhunspell-1.7-01.7.2+really1.7.2-10
ii  libphonon4qt5-4  4:4.12.0-3
ii  libpoppler-qt5-1 22.12.0-2+b1
ii  libqt5concurrent55.15.10+dfsg-5
ii  libqt5core5a 5.15.10+dfsg-5
ii  libqt5gui5   5.15.10+dfsg-5
ii  libqt5network5   5.15.10+dfsg-5
ii  libqt5printsupport5  5.15.10+dfsg-5
ii  libqt5qml5   5.15.10+dfsg-2
ii  libqt5svg5   5.15.10-2
ii  libqt5widgets5   5.15.10+dfsg-5
ii  libqt5xml5   5.15.10+dfsg-5
ii  libqtermwidget5-11.4.0-1
ii  libquazip5-1 0.9.1-3
ii  libstdc++6   13.2.0-9
ii  libx11-6 2:1.8.7-1
ii  phonon4qt5   4:4.12.0-3
ii  zlib1g   1:1.3.dfsg-3

Versions of packages texstudio recommends:
ii  adwaita-qt 1.4.2-3
ii  texlive-base   2023.20231207-1
ii  texlive-latex-base 2023.20231207-1
ii  texlive-latex-recommended  2023.20231207-1
ii  texstudio-doc  4.3.1+ds-3
ii  texstudio-l10n 4.3.1+ds-3

Versions of packages texstudio suggests:
ii  hunspell-en-gb [hunspell-dictionary]  1:7.5.0-1
ii  hunspell-en-us [hunspell-dictionary]  1:2020.12.07-2
ii  mythes-en-us [mythes-thesaurus]   1:7.5.0-1
ii  texlive-fonts-recommended 2023.20231207-1
ii  texlive-latex-extra   2023.20231207-3

-- no debconf information

Bug#1060222: aide-common: 31_aide_php-fpm defines PHPVERSION 2.2 instead of 8.2

[Marc Haber]

Control: tag -1 confirmed

Hi,


On Sun, Jan 07, 2024 at 09:10:17PM +0100, Frederik Himpe wrote:
> The config file 31_aide_php-fpm defines PHPVERSION as 2.2 instead of 8.2.

thanks for spotting this. Pardon the stupid question, all PHP packages
in a Debian version us the same PHP version, right? Maybe it would be a
good idea to deliver PHPVERSION it its own config snippet just in case
that multiple PHP related rules have to refer to the versioN?

Greetings
Marc

-- 
-----
Marc Haber | "I don't trust Computers. They | Mailadresse im Header
Leimen, Germany|  lose things."Winona Ryder | Fon: *49 6224 1600402
Nordisch by Nature |  How to make an American Quilt | Fax: *49 6224 1600421

Bug#1058887: linux-image-6.5.0-5-amd64: impossible to switch off iwlwifi adaptor

[Jean-Marc]

Hi Salvatore,

Le 6/01/24 à 17:31, Salvatore Bonaccorso a écrit :

Hi Jean-Marc,

On Sat, Jan 06, 2024 at 03:01:10PM +0100, Salvatore Bonaccorso wrote:

Hi

The issue should be fixed with
https://git.kernel.org/linus/400f6ebbc175286576c7f7fddf3c347d09d12310
. Can you check that commit on top of the most current version in
unstable to confirm?


Let me be a bit more specific: This is about testing the attached
patch with help of
https://kernel-team.pages.debian.net/kernel-handbook/ch-common-tasks.html#id-1.6.6.4
to build a kernel image with the patch applied, to confirm if it fixes
the issue. Though I'm almost sure that this is the same issue.


I built a kernel image with the patch applied and it solves the issue.

Thank you so much for your help.

And it pushes me back in compiling kernel allowing to compare the 
current way of working with old ones.  Incredible progress making kernel 
building "child's play".


Building a kernel with the patch applied in 2 commands ...

Hats off to you all.


Regards,
Salvatore


Regards,

--
Jean-Marc


OpenPGP_signature.asc
Description: OpenPGP digital signature

Bug#1058887: issue also impacts Debian stable

[Jean-Marc]

The Debian stable having the issue runs linux-image-6.1.0-17 (6.1.69-1).

--
Jean-Marc


OpenPGP_signature.asc
Description: OpenPGP digital signature

Bug#1058887: issue also impacts Debian stable

[Jean-Marc]

Control: severity 1058887 serious
thanks

It also impact Debian stable.

I just installed Debian bookworm on a laptop and it gets the same issue.

Switching off the wi-fi hangs and impacts other softwares and the poweroff.

Raising the severity to serious.

--
Jean-Marc


OpenPGP_signature.asc
Description: OpenPGP digital signature

Bug#1058887: issue persists with kernel 6.6.8

[Jean-Marc]

Upgrading linux kernel to 6.6.9-1 does not solve the issue.

--
Jean-Marc

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

[Marc Haber]

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

So I should replace the Build-Depends: systemd with Build-Depends:
systemd-dev NOW and everything is fine?

Greetings
Marc

P.S.: I do not have the energy currently to engage in a new instance of
any systemd war. Just tell me what to do with the package.

-- 
-
Marc Haber | "I don't trust Computers. They | Mailadresse im Header
Leimen, Germany|  lose things."Winona Ryder | Fon: *49 6224 1600402
Nordisch by Nature |  How to make an American Quilt | Fax: *49 6224 1600421

Bug#1059942: ssh-agent started in KDE session via systemd user sesson doesn't work without restart

[Marc Haber]

Package: openssh-client
Version: 1:9.6p1-2
Severity: normal

Hi,

I must admit that's a weird one. I have a new notebook and decided not
to migrate my old installation but install anew. This made me end up
with KDE Plasma (intended) on Wayland (unintended). In this setup,
ssh-agent is started on login via system user session and doesn't work,
at least not with my Yubikey with PIV.

I can enter the PIN with ssh-add -t 7200 -c -s
/usr/lib/x86_64-linux-gnu/opensc-pkcs11.so. An incorrect PIN gets
rejected, so something correct is happening. ssh $HOST fails with "agent
refused".

I can start a new ssh-agent in a shell and use it - in this shell -
normally. And I can restart the session-based ssh-agent with systemctl
--user restart ssh-agent and that new instance works as well.

So there must be something different with the ssh-agent that gets
started on login.

I'm prepared to debug, just tell me what to do. I can live with an
occasional systemctl --user restart ssh-agent now that I know this
helps.

Greetings
Marc


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

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

Versions of packages openssh-client depends on:
ii  adduser   3.137
ii  libc6 2.37-13
ii  libedit2  3.1-20230828-1
ii  libfido2-11.14.0-1
ii  libgssapi-krb5-2  1.20.1-5
ii  libselinux1   3.5-1+b1
ii  libssl3   3.1.4-2
ii  passwd1:4.13+dfsg1-3
ii  zlib1g1:1.3.dfsg-3

Versions of packages openssh-client recommends:
ii  xauth  1:1.1.2-1

Versions of packages openssh-client suggests:
pn  keychain   
ii  ksshaskpass [ssh-askpass]  4:5.27.9-1
pn  libpam-ssh 
pn  monkeysphere   

-- no debconf information

Bug#1059896: sudo: Please add openssl support for sudo and sudo_logsrvd for secure transfer of sudo log files

[Marc Haber]

On Wed, Jan 03, 2024 at 07:10:46PM +0100, Alexander Reichle-Schmehl wrote:
> Yes, it is the daemon responsible to receive and store log files from
> other hosts running sudo.  As most people will need it, it makes sense
> to split it of.  However, if you do so, that package should IMHO use
> ssl.  Because I can't think of a scenario, were people would like to use
> the log deamon, without using ssl.  And here I think simplicity of
> direct ssl usage wins over extra package stunnel.

But that also brings us the burden of having OpenSSL in the sudo
package. I shudder at that thought. I have written things up a bit in
#1059924 just in case you want to chip in.

Greetings
Marc

-- 
-
Marc Haber | "I don't trust Computers. They | Mailadresse im Header
Leimen, Germany|  lose things."Winona Ryder | Fon: *49 6224 1600402
Nordisch by Nature |  How to make an American Quilt | Fax: *49 6224 1600421

Bug#1059935: doesnt work with ansible 2.14.13 (currently in unstable)

[Marc Haber]

Package: ansible-mitogen
Version: 0.3.4-2
Severity: important
Tags: upstream

Hi,

with ansible 2.14.13, ansible-mitogen fails with something like:

Unexpected failure during module execution: mitogen.core.StreamError: cannot 
unpickle 'ansible.utils.unsafe_proxy'/'AnsibleUnsafeText'\n  File \"\", 
line 3698, in _dispatch_one\n  File \"\", line 3681, in _parse_request\n 
 File \"\", line 966, in unpickle\n  File \"\", line 757, in 
find_class\n

Upstream Bug Report is https://github.com/mitogen-hq/mitogen/issues/1034

Possible upstream patch is 
https://github.com/AnatomicJC/mitogen/commit/88c0da39a4c869c46eb21b6b67310ad62785b36c

I didn't test it though.

Downgrading ansible to 2.14.11-2 fixed the issue for me.

Greetings
Marc

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

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

Versions of packages ansible-mitogen depends on:
ii  ansible  7.7.0+dfsg-3
ii  ansible-core 2.14.13-1
ii  python3  3.11.6-1
ii  python3-mitogen  0.3.4-2

ansible-mitogen recommends no packages.

ansible-mitogen suggests no packages.

-- no debconf information

Bug#1059924: should we actually ship sudo_logsrvd

[Marc Haber]

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

Dear Team,

it has recently come to my attention that the sudo package contains
sudo_logsrvd, a daemon which can collect event and "I/O logs" from sudo.
Judging from the SECURITY NOTES in sudo(8), this means logging the
complete input and output of a command invoked via sudo.

In #1059896, Tolimar suggests adding OpenSSL support so that the
input/output is not send unencrypted over the network. The more I think
about this the more we need to do. At the current state, the package
doesn't conform to what I expect of a Debian package.

Should we:

(1)
remove sudo_logsrvd from the package with no replacement?

(2)
move sudo_logsrvd to its own package with proper systemd unit etc bla
foo

(3)
continue shipping an unconfigured daemon without execution
infrastructure even to clients that will never run it

and (orthogonal to the upper options)

(a)
continue to ship things wihout OpenSSL

(b)
enable OpenSSL, pulling in an additional dependency also for sudo

That leaves us the choice (1), (2a), (2b), (3a), (3b)

I currently don't see myself in a position to provide proper support for
Options (2b) and (3b), and while (2a) is considerably easier it's
probably beyond my current personal limits as well. So, if things are
going to continue that I am the one doing the bulk of the work, we're
probably stuck with (1) or (2a).

An independent solution would be to continue shipping sudo.deb in a
minimal configuration, and having a new sudo-extended.deb that can
support plugins, SSL, bells and whistles, but just with supported sudo
=> sudo-extended migration path and explicitly not providing a migration
path back from sudo-extended to plain sudo. But all this can only be
done after sudo-ldap is gone as this is a horrible mess to package that
we NEED to get rid of.

I'd like to hear your comments.

Greetings
Marc

Bug#1059896: sudo: Please add openssl support for sudo and sudo_logsrvd for secure transfer of sudo log files

[Marc Haber]

Hi Alexander,

thanks for your patch. I am indeed reluctant to have OpenSSL added as a
dependency to sudo. This might open a can of worms; other team members
might give their opinion here as well.

And since we just are working on getting rid of sudo-ldap, having a
variant, sudo-ssl, would probably be too much as well.

I was not aware of sudo_logsrvd at all, since that's a daemon, it should
probably be in its own package (or disabled).

Would it be very unfriendly to indeed suggest using stunnel instead of
native SSL? What is a motivation to use sudo_logsrvd instead of normal
syslog?

Greetings
Marc

On Wed, Jan 03, 2024 at 09:49:37AM +0100, Alexander Reichle-Schmehl wrote:
> From: Alexander Reichle-Schmehl 
> Subject: Bug#1059896: sudo: Please add openssl support for sudo and
>  sudo_logsrvd for secure transfer of sudo log files
> To: Debian Bug Tracking System 
> Reply-To: Alexander Reichle-Schmehl ,
>  1059...@bugs.debian.org
> Date: Wed, 03 Jan 2024 09:49:37 +0100
> X-Mailer: reportbug 7.10.3+deb11u1
> 
> Package: sudo
> Version: 1.9.5p2-3+deb11u1
> Severity: wishlist
> Tags: patch
> 
> Dear Maintainer,
> 
> sudo 1.9 introduced the functionality to directly send log files (especially
> input/output logs) to a log server.  As these logs might contain private data,
> they should be transfered using ssl.  Both sudo as well as sudo_logsrvd
> support this, when the feature is enabled at compile time.
> 
> I send merge request on salsa to add this functionality, and verified, that
> it works for me.
> 
> However, I should also point out, that an alternative approach would be to use
> stunnel. If you prefer that instead of adding additional complexity to an
> security critical package, would you consider adding a Readme file explaining
> how that's doen?  I use it for sudo an other distribution anyway, and could
> write one for you, if you prefer it that way.
> 
> 
> Best regards,
>   Alexander
> 
> 
> 
> -- System Information:
> Debian Release: 11.8
>   APT prefers oldstable-security
>   APT policy: (500, 'oldstable-security'), (500, 'oldoldstable-updates'), 
> (500, 'oldstable')
> Architecture: amd64 (x86_64)
> 
> Kernel: Linux 5.10.0-26-cloud-amd64 (SMP w/2 CPU threads)
> Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
> LANGUAGE=en_US:en
> Shell: /bin/sh linked to /bin/dash
> Init: systemd (via /run/systemd/system)
> LSM: AppArmor: enabled
> 
> Versions of packages sudo depends on:
> ii  libaudit1   1:3.0-2
> ii  libc6   2.31-13+deb11u7
> ii  libpam-modules  1.4.0-9+deb11u1
> ii  libpam0g1.4.0-9+deb11u1
> ii  libselinux1 3.1-3
> ii  lsb-base11.1.0
> ii  zlib1g  1:1.2.11.dfsg-2+deb11u2
> 
> sudo recommends no packages.
> 
> sudo suggests no packages.
> 
> -- Configuration Files:
> /etc/pam.d/sudo changed [not included]
> /etc/sudoers [Errno 13] Permission denied: '/etc/sudoers'
> /etc/sudoers.d/README [Errno 13] Permission denied: '/etc/sudoers.d/README'
> 
> -- no debconf information

Bug#1059871: alsa-ucm-conf should be a required package by libasound2-data, it's essential on some sound hardware

[Marc MERLIN]

Package: libasound2-data
Version: 1.2.10-3

As per https://github.com/thesofproject/linux/issues/4758 ,
alsa-ucm-conf is absolutely required for any sound to come out on
speakers on a Dell 9730. Without it, you get sound on headphones, but
the speakers won't work, and there is nothing you can unmute with
alsamixer. I tried literally all alsamixer channels, nothing worked or
did anything for the speakers.

After may many hours (by that I mean over 10 hours over many days of
googling, building new kernels, diffing ubuntu where sound worked, and
debian 12 where sound did not work), I got notwhere until this bug and
being told about alsa-ucm-conf I had never heard about and was mentioned
nowhere in the copious pages I read (most talked about alsamixer,
pipewire and wireplumber that add their own levels of things that can go
wrong)

So the 2 bugs, I'd lke to file here
1) This should be a Requires, not Recommends
Package: libasound2-data
Source: alsa-lib
Version: 1.2.8-1
Installed-Size: 200
Maintainer: Debian ALSA Maintainers 
Architecture: all
Replaces: libasound2 (<< 1.2.8-1)
Recommends: alsa-ucm-conf, alsa-topology-conf

2) Package gives 0 clue that it is an absolutely essential pacakge for
some sound hardware.

Package: alsa-ucm-conf
Version: 1.2.10-1
Installed-Size: 828
Maintainer: Debian ALSA Maintainers 
Architecture: all
Depends: libasound2 (>= 1.2.7)
Description-en: ALSA Use Case Manager configuration files
 This package contains ALSA Use Case Manager configuration of audio
 input/output names and routing for specific audio hardware. They can be
 used with the alsaucm tool.

Thanks for making it more clear that this package is very essential for
some hardware that needs something close to half-secret knock code
before speakers will work.

Marc
-- 
"A mouse is a device used to point at the xterm you want to type in" - A.S.R.
 
Home page: http://marc.merlins.org/   | PGP 7F55D5F27AAF9D08

Bug#1059639: please give possibility for custom ssh-agent parameters

[Marc Haber]

On Sat, Dec 30, 2023 at 06:01:35PM +, Colin Watson wrote:
> I think the simplest approach would be to allow invoking something like
> "/usr/lib/openssh/agent-launch start -- -t 1200", and pass the extra
> arguments on to ssh-agent.  You could then write a drop-in unit like
> this:
> 
>   [Service]
>   ExecStart=
>   ExecStart=/usr/lib/openssh/agent-launch start -- -t 1200
> 
> Would that be acceptable?

Yes, that is absolutely fine. Thank you.

Greetings
Marc

-- 
-----
Marc Haber | "I don't trust Computers. They | Mailadresse im Header
Leimen, Germany|  lose things."Winona Ryder | Fon: *49 6224 1600402
Nordisch by Nature |  How to make an American Quilt | Fax: *49 6224 1600421

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

[Marc Haber]

On Sat, Dec 30, 2023 at 10:09:10AM +0200, Martin-Éric Racine wrote:
> Sorry, I'm not. Just go ahead and upload. I'll let you know whether
> that fixed it or not.

Okay, sure. I'll ask upstream whether they want to do a release first. A
new upload this year is unlikely, I's also like the current unstable
version to migrate to testing first.

Greetings
Marc

Bug#1059639: please give possibility for custom ssh-agent parameters

[Marc Haber]

Package: openssh-client
Version: 1:9.6p1-2
Severity: wishlist

Hi,

/usr/lib/openssh/agent-launch starts ssh-agent with a standard set of
parameters. I'd like to have -t 1200 added to that.

Please consider adding a possibility to control the parameters that the
ssh agent is being invoked, for example by having an override unit, or
having /usr/lib/openssh/agent-launch read a user-specific configuration
file.

Greetings
Marc


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

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

Versions of packages openssh-client depends on:
ii  adduser   3.137
ii  libc6 2.37-13
ii  libedit2  3.1-20230828-1
ii  libfido2-11.14.0-1
ii  libgssapi-krb5-2  1.20.1-5
ii  libselinux1   3.5-1+b1
ii  libssl3   3.1.4-2
ii  passwd1:4.13+dfsg1-3
ii  zlib1g1:1.3.dfsg-3

Versions of packages openssh-client recommends:
ii  xauth  1:1.1.2-1

Versions of packages openssh-client suggests:
pn  keychain   
ii  ksshaskpass [ssh-askpass]  4:5.27.9-1
pn  libpam-ssh 
pn  monkeysphere   

-- no debconf information

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

[Marc Haber]

On Sat, Dec 09, 2023 at 12:40:46PM +0200, Martin-Éric Racine wrote:
> Since the upgrade from 1.9.14p2 to 1.9.15p in unstable, sudo aborts with a 
> malloc error on Hurd i386.

Upstream has reproduced and fixed this in
https://www.sudo.ws/repos/sudo/rev/8917f7d6a464

Are you in a position to verify this before I apply and upload?

Greetings
Marc

Bug#1058887: issue persists with kernel 6.6.8

[Jean-Marc]

After today's upgrade bringing linux-image-6.6.8 to sid, issue persists.

Switching off my iwlwifi device makes nmcli unusable.

It also blocks firefox.

And "sudo any-command" hangs, impossible to break it.

Powering off/rebooting the system is also impossible.

--
Jean-Marc

Bug#1055024: cryptsetup-initramfs changes crypttab entries order when generating initramfs

[Marc Haber]

On Sun, Oct 29, 2023 at 03:10:18PM +0100, Nicolas Melot wrote:
> This is a repost of the same bug report I submitted to Ubuntu maintainers on
> https://bugs.launchpad.net/ubuntu/+source/cryptsetup/+bug/2031499 and that
> seems to have been left as is. I am now hitting the same issue on Debian
> Bookworm.

I have exactly the same problem with a setup where another crypt device
needs to be unlocked BEFORE the root file system because the other crypt
device holds part of the key.

And I came to the same solution independently.

Hence, this is not a totally exotic use case at least, since two users
came even to the same solution.

After taking a step back I also find the solution quite elegant: It
preserves the order of the crypt devices as given by the local admin, it
just adds the devices that the local admin didn't specify while the
system knows a device is needed. The admin has the option of taking
the complete crypttab in their own hands transparently.

Please consider implementing this.

Greetings
Marc

Bug#1058937: /usr-move: Do we support upgrades without apt?

[Marc Haber]

On Thu, Dec 21, 2023 at 11:19:48AM -0300, Antonio Terceiro wrote:
> On Thu, Dec 21, 2023 at 10:41:57AM +0100, Helmut Grohne wrote:
> > Is it ok to call upgrade scenarios failures that cannot be reproduced
> > using apt unsupported until we no longer deal with aliasing?
> 
> I think so, yes. I don't think it's likely that there are people doing
> upgrades on running systems not using apt.

Do those GUI frontends that work via packagekit or other frameworks
count as "using apt"? I now that WE recommend using apt in a text
console outside of X, but even many of our own users do what their
Desktop Environment does, and our downstreams like *b*nt* recommend
other ways to upgrade as well.

Greetings
Marc

-- 
-
Marc Haber | "I don't trust Computers. They | Mailadresse im Header
Leimen, Germany|  lose things."Winona Ryder | Fon: *49 6224 1600402
Nordisch by Nature |  How to make an American Quilt | Fax: *49 6224 1600421

Bug#1056279: Bug#1057220: Looks like the systemctl links are gone but not the pm-utils ones

[Marc Haber]

On Mon, Dec 18, 2023 at 10:09:10AM +0100, Marc Haber wrote:
> Thanks for the work, I was never able to fully grasp the issue and the
> inner workings of the solution, and thank you for allowing me to remain
> silent during the process of finding and implementing the solution.

I'd like to report that it Works For Me. I downgraded molly-guard and
systemd to trixie and then did an upgrade, which worked.

Greetings
Marc

-- 
-
Marc Haber | "I don't trust Computers. They | Mailadresse im Header
Leimen, Germany|  lose things."Winona Ryder | Fon: *49 6224 1600402
Nordisch by Nature |  How to make an American Quilt | Fax: *49 6224 1600421

Bug#1058887: downgrading firmware-iwlwifi does not help

[Jean-Marc]

I also downgraded firmware-iwlwifi from 20230625-2 to 20230210-5 but it 
does not help.


Switching off iwlwifi device hangs and blocks the system making it 
impossible to power off.



--
Jean-Marc


OpenPGP_signature.asc
Description: OpenPGP digital signature

Bug#1056279: Bug#1057220: Looks like the systemctl links are gone but not the pm-utils ones

[Marc Haber]

On Sun, Dec 17, 2023 at 09:55:13PM -0800, Francois Marier wrote:
> With respect to the presence of the real commands in the path, I'm not too
> worried about it personally.

Agreed. Molly-Guard is not a security tool, it provides basic safety
against things like "typed shutdown -r now in the wrong window". Most
people just give the same commands every time, for me it happens to be
shutdown -r now, and if molly-guard reliably catches that then its job
is done.

It was never designed to prevent fully deliberate shots in one's foot by
typing things like shutdown.someweirdsuffixthatnooneeverremembers -r
now.

Thanks for the work, I was never able to fully grasp the issue and the
inner workings of the solution, and thank you for allowing me to remain
silent during the process of finding and implementing the solution.

Greetings
Marc

-- 
-----
Marc Haber | "I don't trust Computers. They | Mailadresse im Header
Leimen, Germany|  lose things."Winona Ryder | Fon: *49 6224 1600402
Nordisch by Nature |  How to make an American Quilt | Fax: *49 6224 1600421

Bug#1058887: linux-image-6.5.0-5-amd64: impossible to switch off iwlwifi adaptor

[Jean-Marc]

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

Dear Maintainer,

When I try to switch off my Wi-Fi adaptor, it just blocks/hangs and
never goes down.

Trying to get info in cli also blocks:

$ env LANG=C nmcli 
Warning: nmcli (1.44.2) and NetworkManager (Unknown) versions don't match. 
Restarting NetworkManager is advised.
Error: NetworkManager is not running.

Even reboot/power-down hangs and the only way to recover is a hard-power
down.

I added at the end of this report some info from syslog (tail -f
/var/log/syslog) I ran at the moment I swithced off my Wi-Fi.

Last info, I tried with the previous kernel linux-image-6.5.0-4-amd64 
(6.5.10-1) and it
works like a charm.

Regards,

Jean-Marc



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

** Command line:
BOOT_IMAGE=/vmlinuz-6.5.0-5-amd64 root=/dev/mapper/gandalf--vg-root ro quiet

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

** Kernel log:
[   15.121367] hid-alps 0018:044E:120B.0001: input,hidraw0: I2C HID v1.00 Mouse 
[DLL07A0:01 044E:120B] on i2c-DLL07A0:01
[   15.160195] iwlwifi :02:00.0: Detected Intel(R) Dual Band Wireless AC 
8265, REV=0x230
[   15.160285] thermal thermal_zone7: failed to read out thermal zone (-61)
[   15.167411] iwlwifi :02:00.0: reporting RF_KILL (radio disabled)
[   15.224743] EXT4-fs (nvme0n1p2): mounting ext2 file system using the ext4 
subsystem
[   15.23] iwlwifi :02:00.0: base HW address: 00:28:f8:e3:43:f6, OTP 
minor version: 0x0
[   15.235653] EXT4-fs (nvme0n1p2): mounted filesystem 
24d75cff-3492-44c9-bb3b-b3cc1a47ff56 r/w without journal. Quota mode: none.
[   15.244767] ieee80211 phy0: Selected rate control algorithm 'iwl-mvm-rs'
[   15.247297] EXT4-fs (dm-3): mounted filesystem 
16ae5ebd-3b09-4b5a-a492-54848826a72c r/w with ordered data mode. Quota mode: 
none.
[   15.254994] snd_hda_codec_realtek hdaudioC0D0: autoconfig for ALC3246: 
line_outs=1 (0x14/0x0/0x0/0x0/0x0) type:speaker
[   15.254999] snd_hda_codec_realtek hdaudioC0D0:speaker_outs=0 
(0x0/0x0/0x0/0x0/0x0)
[   15.255002] snd_hda_codec_realtek hdaudioC0D0:hp_outs=1 
(0x21/0x0/0x0/0x0/0x0)
[   15.255004] snd_hda_codec_realtek hdaudioC0D0:mono: mono_out=0x0
[   15.255005] snd_hda_codec_realtek hdaudioC0D0:inputs:
[   15.255007] snd_hda_codec_realtek hdaudioC0D0:  Headset Mic=0x19
[   15.255009] snd_hda_codec_realtek hdaudioC0D0:  Headphone Mic=0x1a
[   15.255010] snd_hda_codec_realtek hdaudioC0D0:  Internal Mic=0x12
[   15.256746] iwlwifi :02:00.0 wlp2s0: renamed from wlan0
[   15.295867] usb 1-5: New USB device found, idVendor=0bda, idProduct=5650, 
bcdDevice=60.06
[   15.295871] usb 1-5: New USB device strings: Mfr=3, Product=1, SerialNumber=2
[   15.295873] usb 1-5: Product: Integrated Webcam_HD
[   15.295874] usb 1-5: Manufacturer: CN0K49W17248773OA6KAA00
[   15.295876] usb 1-5: SerialNumber: 200901010001
[   15.322123] input: HDA Digital PCBeep as 
/devices/pci:00/:00:1f.3/sound/card0/input12
[   15.38] input: HDA Intel PCH Headphone Mic as 
/devices/pci:00/:00:1f.3/sound/card0/input13
[   15.322338] input: HDA Intel PCH HDMI/DP,pcm=3 as 
/devices/pci:00/:00:1f.3/sound/card0/input14
[   15.322437] input: HDA Intel PCH HDMI/DP,pcm=7 as 
/devices/pci:00/:00:1f.3/sound/card0/input15
[   15.322533] input: HDA Intel PCH HDMI/DP,pcm=8 as 
/devices/pci:00/:00:1f.3/sound/card0/input16
[   15.390559] audit: type=1400 audit(1702826732.654:2): apparmor="STATUS" 
operation="profile_load" profile="unconfined" name="lsb_release" pid=655 
comm="apparmor_parser"
[   15.393865] audit: type=1400 audit(1702826732.654:3): apparmor="STATUS" 
operation="profile_load" profile="unconfined" name="system_tor" pid=658 
comm="apparmor_parser"
[   15.401016] audit: type=1400 audit(1702826732.662:4): apparmor="STATUS" 
operation="profile_load" profile="unconfined" name="nvidia_modprobe" pid=656 
comm="apparmor_parser"
[   15.401021] audit: type=1400 audit(1702826732.662:5): apparmor="STATUS" 
operation="profile_load" profile="unconfined" name="nvidia_modprobe//kmod" 
pid=656 comm="apparmor_parser"
[   15.404165] audit: type=1400 audit(1702826732.666:6): apparmor="STATUS" 
operation="profile_load" profile="unconfined" name="torbrowser_tor" pid=675 
comm="apparmor_parser"
[   15.406822] audit: type=1400 audit(1702826732.670:7): apparmor="STATUS" 
operation="profile_load" profile="unconfined" 
name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=657 
comm="apparmor_parser"
[   15.406827] audit: type=1400 audit

Bug#1058757: 90 days of log retention?

[Marc Haber]

Source: sniproxy
Version: 0.6.0
Severity: minor

Hi,

sniproxy's logrotate.conf specifies "rotate 90". I haven't seen a
package that holds its log that long in Debian ever.

Please consider shortening the default log retention period. Proxy logs
might contain IP addresses which might be problematic to log, especially
for such a long time, for data protection reasons.

Greetings
Marc

Bug#1058453: sudo-ldap will go away

[Marc Haber]

Package: release-notes
Severity: wishlist
Control: affects -1 1033728

Hi,

Paul suggested that I file this bug as a reminder.

The sudo team is considering to remove sudo-ldap after the trixie
release. A possible migration path would be to use libsss-sudo instead.

See also:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1033728
https://salsa.debian.org/sudo-team/sudo/-/blob/master/debian/NEWS

The version of sudo that currently ships in unstable has a corresponding
NEWS entry and displays a corresponding debconf message.

Me and the sudo team are not yet sure about what we're going to do with
sudo-ldap post-trixie. We can

(1) remove the package without replacement
(2) replace the package with a transitional package depending on
(2a) libsss-sudo or
(2b) sudo
(3) make sudo-ldap uninstallable so that an upgrade will error out
before breaking sudo-ldap
(4) keep sudo-ldap around
(5) a different method

I am open to suggestions.

I think this is worth mentioning in the trixie release notes. While
trixie will still have a fully functional sudo-ldap, users SHOULD use
the trixiecycle to migrate away from sudo-ldap so that their systems
won't break when sudo-ldap finally goes away in trixie+1.

The final wording for the trixie release notes depends on what we decide
to do post-trixie. Again, I am open to suggestions how to word things.
Feel free to remind me in case I don't keep this on my radar by myself.

Greetings
Marc

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

[Marc Haber]

On Sat, Dec 09, 2023 at 12:40:46PM +0200, Martin-Éric Racine wrote:
> Since the upgrade from 1.9.14p2 to 1.9.15p in unstable, sudo aborts with a 
> malloc error on Hurd i386.
> 
> $ LC_ALL=C sudo apt-get install acpi-support-base
> malloc(): invalid next size (unsorted)
> Keskeytetty

Does this also happen with other commands? Can you obtain a backtrace?

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

Greetings
Marc

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

What does that mean?

Greetings
Marc

Bug#1004905: sudo: FTBFS on non-linux architectures

[Marc Haber]

On Thu, Feb 03, 2022 at 11:39:37AM +0100, Laurent Bigonville wrote:
> sudo currently FTBFS on non-linux architectures
> 
> On hurd, it fails in the tests
> 
> On kfreebsd, the attached patch fixes the compilation (that should
> probably be reported upstream), but it still fails in the tests

Does this still happen?

Greetings
Marc

Bug#1057698: bugs.debian.org: The proposed kernel for Debian 12.3 breaks wlan

[Marc]

Indeed! So thank you so much Salvatore!

---
uname -a;dmesg | grep iwlw
Linux t490 6.1.0-14-amd64 #1 SMP PREEMPT_DYNAMIC Debian 6.1.64-1 
(2023-11-30) x86_64 GNU/Linux

[   16.115308] iwlwifi :00:14.3: enabling device ( -> 0002)
[   16.136583] iwlwifi :00:14.3: firmware: direct-loading firmware 
iwlwifi-9000-pu-b0-jf-b0-46.ucode

[   16.136607] iwlwifi :00:14.3: WRT: Overriding region id 0
[   16.136610] iwlwifi :00:14.3: WRT: Overriding region id 1
[   16.136611] iwlwifi :00:14.3: WRT: Overriding region id 2
[   16.136612] iwlwifi :00:14.3: WRT: Overriding region id 3
[   16.136613] iwlwifi :00:14.3: WRT: Overriding region id 4
[   16.136613] iwlwifi :00:14.3: WRT: Overriding region id 6
[   16.136614] iwlwifi :00:14.3: WRT: Overriding region id 8
[   16.136615] iwlwifi :00:14.3: WRT: Overriding region id 9
[   16.136616] iwlwifi :00:14.3: WRT: Overriding region id 10
[   16.136617] iwlwifi :00:14.3: WRT: Overriding region id 11
[   16.136618] iwlwifi :00:14.3: WRT: Overriding region id 15
[   16.136619] iwlwifi :00:14.3: WRT: Overriding region id 16
[   16.136619] iwlwifi :00:14.3: WRT: Overriding region id 18
[   16.136620] iwlwifi :00:14.3: WRT: Overriding region id 19
[   16.136621] iwlwifi :00:14.3: WRT: Overriding region id 20
[   16.136622] iwlwifi :00:14.3: WRT: Overriding region id 21
[   16.136623] iwlwifi :00:14.3: WRT: Overriding region id 28
[   16.136626] iwlwifi :00:14.3: WRT: Overriding region id 29
[   16.136934] iwlwifi :00:14.3: firmware: failed to load 
iwl-debug-yoyo.bin (-2)
[   16.136944] iwlwifi :00:14.3: firmware: failed to load 
iwl-debug-yoyo.bin (-2)
[   16.136946] iwlwifi :00:14.3: loaded firmware version 
46.ea3728ee.0 9000-pu-b0-jf-b0-46.ucode op_mode iwlmvm

[   16.317499] iwlwifi :00:14.3: BIOS contains WGDS but no WRDS
[   16.319451] iwlwifi :00:14.3: Detected Intel(R) Wireless-AC 9560 
160MHz, REV=0x312
[   16.377004] iwlwifi :00:14.3: base HW address: 50:eb:71:1d:88:cd, 
OTP minor version: 0x4

[   16.550372] iwlwifi :00:14.3 wlp0s20f3: renamed from wlan0
--


On 12/7/23 10:28, Salvatore Bonaccorso wrote:

Hi,

On Thu, Dec 07, 2023 at 09:46:47AM +0100, djw6g6b5...@temp.mailbox.org wrote:

Package: bugs.debian.org

There' s a bug in linux-image-amd64 version 6.1.64-1 for bookworm (in
proposed updates).
The updates breaks wlan on a Lenovo T490s. Current versions used to work
fine.

-
log:

uname -a;dmesg | grep iwlw
Linux t490 6.1.0-14-amd64 #1 SMP PREEMPT_DYNAMIC Debian 6.1.64-1
(2023-11-30) x86_64 GNU/Linux
[   16.900339] iwlwifi: `N' invalid for parameter `enable_ini'

modprobe
# modprobe iwlwifi
modprobe: ERROR: could not insert 'iwlwifi': Invalid argument

-
expected behaviour:
# uname -a;dmesg | grep iwlw
Linux t490 6.1.0-13-amd64 #1 SMP PREEMPT_DYNAMIC Debian 6.1.55-1
(2023-09-29) x86_64 GNU/Linux
[   17.994429] iwlwifi :00:14.3: enabling device ( -> 0002)
[   18.013920] iwlwifi :00:14.3: firmware: direct-loading firmware
iwlwifi-9000-pu-b0-jf-b0-46.ucode
[   18.014248] iwlwifi :00:14.3: loaded firmware version 46.ea3728ee.0
9000-pu-b0-jf-b0-46.ucode op_mode iwlmvm
[   18.200836] iwlwifi :00:14.3: BIOS contains WGDS but no WRDS
[   18.201012] iwlwifi :00:14.3: Detected Intel(R) Wireless-AC 9560
160MHz, REV=0x312
[   18.266178] iwlwifi :00:14.3: base HW address: 50:eb:71:1d:88:cd, OTP
minor version: 0x4
[   18.352070] iwlwifi :00:14.3 wlp0s20f3: renamed from wlan0

Sidenote: the backport kernel works fine also.


Thanks for the report.

Since upstream e0c1ca236e28 ("wifi: iwlwifi: honor the enable_ini
value") in 6.7-rc1 and backported to 6.6.2, 6.5.12 and 6.1.63 the
values of enable_ini are honoured.

Please have a look where in /etc/modprobe.d/*.conf you have
enable_ini=N. I suspect it is a customized own file. The value is not
correct and should be either 1 or 0 here.

Regards,
Salvatore

Bug#1057535: python3-fonttools: upgrading package gave a SyntaxWarning: invalid escape sequence '\_'

[Jean-Marc]

Package: python3-fonttools
Version: 4.38.0-1+b2
Severity: normal
X-Debbugs-Cc: jean-m...@6jf.be

Dear Maintainer,

Upgrading the package today in my debian sid from 4.38.0-1+b1 to 4.38.0-1+b2 
gave a warning message:

Paramétrage de python3-fonttools (4.38.0-1+b2) ...
/usr/lib/python3/dist-packages/fontTools/cffLib/specializer.py:40: 
SyntaxWarning: invalid escape sequence '\_'
  """Takes a T2CharString program list and returns list of commands.

I guess this is not really important.

But, please, take a look at it.

Regards,

JM

-- System Information:
Debian Release: trixie/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)

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

Versions of packages python3-fonttools depends on:
ii  libc6  2.37-13
ii  python33.11.6-1
ii  python3-all3.11.6-1
ii  python3-brotli 1.1.0-2+b1
ii  python3-fs 2.4.16-2
ii  python3-lxml   4.9.3-1+b1
ii  python3-lz44.0.2+dfsg-1+b3
ii  python3-pkg-resources  68.1.2-2
ii  python3-scipy  1.10.1-6
ii  python3-sympy  1.12-6
ii  python3-ufolib20.16.0+dfsg1-1
ii  python3-unicodedata2   15.1.0+ds-1+b1
ii  unicode-data   15.1.0-1

python3-fonttools recommends no packages.

python3-fonttools suggests no packages.

-- no debconf information

Bug#1057480: e2fsprogs: -E mount_opts contradicting documentation

[Marc Lehmann]

Package: e2fsprogs
Version: 1.47.0-2
Severity: normal

Dear Maintainer,

tune2fs documents the -E switch as:

   Extended options are comma separated, and may take an  argu‐ ment using the 
equals ('=') sign.

and the mount_opts sub-option:

   mount_opts=mount_option_string
  mount_option_string is an arbitrary string with a maximum length  of  63  
bytes...

The problem is that mount options are also comma-separated and tune2fs
does not seem to support this (instead assuming the comma separates
-E options), therefore, the string is not arbitrary, or at least, its
impossible to specify arbitrary contents, or, if it is possible, its
undocumented how to do so.

I don't know if this is a documentation problem or not, but it would be
nice if one could actually specify an arbitrary mount_option_string with
tune2fs.

-- System Information:
Debian Release: 12.2
  APT prefers stable-updates
  APT policy: (990, 'stable-updates'), (990, 'stable-security'), (990, 
'stable'), (500, 'unstable-debug'), (500, 'testing-debug'), (500, 
'oldstable-debug'), (500, 'unstable'), (500, 'testing'), (1, 
'experimental-debug'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386, x32

Kernel: Linux 6.1.0-13-amd64 (SMP w/24 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_USER, TAINT_WARN, 
TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=en_IE.UTF-8, LC_CTYPE=en_IE.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 e2fsprogs depends on:
ii  libblkid12.38.1-5+b1
ii  libc62.36-9+deb12u3
ii  libcom-err2  1.47.0-2
ii  libext2fs2   1.47.0-2
ii  libss2   1.47.0-2
ii  libuuid1 2.38.1-5+b1
ii  logsave  1.47.0-2

Versions of packages e2fsprogs recommends:
pn  e2fsprogs-l10n  

Versions of packages e2fsprogs suggests:
pn  e2fsck-static  
pn  fuse2fs
ii  gpart  1:0.3-10
ii  parted 3.5-3

-- Configuration Files:
/etc/cron.d/e2scrub_all changed [not included]

-- no debconf information

Bug#1053565: RFS: openvpn3-client/20+dfsg-1 [ITP] -- virtual private network daemon (version 3)

[Marc Leeman]

>>   * Package name : openvpn3-client
> BTW, why it is named this way?
> Is it client-only now, without the server part?
> Previous package is named just "openvpn", it acts
> as both client or server (actually the two roles are
> symmetric, it can be both).  If new openvpn is like
> this, I suggest naming it just "openvpn3", without
> the -client part, since it is quite confusing.

> Or is there also -daemon (or -server) part?

Sorry, missed your e-mail.

This is not the same as the openvpn packages, this is a different
implementation from the same company.

At the moment, they have only released the client part.

This implementation has functionality for 2-factor authentication that
openvpn2 does not have.

The package that upstream releases is openvpn3-linux (source) or
openvpn3 (package). I have named it

openvpn3-client to

1. Make it clear that this is only the client part
2. Prepare for future releases that include a server part

There internal software structure is already split into different
parts; but they release a collapsed archive for the client only.

--
g. Marc

GPG: 827C FD74 BA46 8152 A041 F3A0 7A6A 4F17 5995 A65B

Bug#1026898: deprecate QUOTAUSER post-bookworm

[Marc Haber]

On Mon, Nov 27, 2023 at 09:57:22AM +0100, Sylvain Beucler wrote:
> On 26/11/2023 11:32, Marc Haber wrote:
> > On Sun, Nov 26, 2023 at 10:00:27AM +0100, Sylvain Beucler wrote:
> > > I use QUOTAUSER on a multi-user remote system, for a non-profit, where
> > > people tend to forget about disk space, to ensure any new 'adduser' sets a
> > > reasonable quota.
> > > 
> > > If there's an alternative please let me know.
> > 
> > The alternative would be to use edquota -p (quota) (username) after
> > creating the user. At least that's what adduser does when the quotauser
> > configuration option is set.
> 
> I use QUOTAUSER so I can be sure that when me or a co-admin creates a user,
> the quota is set, and there's no way to forget about it (iow I know how to
> do it manually).  By alternative, I mean a way to ensure that the quota is
> always set for new users :)

How about having a wrapper around adduser? Or a cronjob that iterates
through the users and installs the quota even for users that had it
removed?

This could also be an application for #36019, hooks.

Greetings
Marc

-- 
-
Marc Haber | "I don't trust Computers. They | Mailadresse im Header
Leimen, Germany|  lose things."Winona Ryder | Fon: *49 6224 1600402
Nordisch by Nature |  How to make an American Quilt | Fax: *49 6224 1600421

Bug#1057013: Regression: addgroup user group no longer works and should have been documented instead of removed

[Marc Haber]

Control: severity -1 wishlist
Control: tags -1 wontfix
thanks

On Mon, Nov 27, 2023 at 05:27:11PM -0500, theofficialgman wrote:
> A regression was caused with the unnecessary commit
> https://salsa.debian.org/debian/adduser/-/commit/8d42193438f6c1500fb36cd5c24bf682888a611c
> to close https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=664869
> 
> This undocumented syntax was known in use in scripting (such as nvidia
> tegra debian based distros). Instead of disabling two argument syntax
> this should instead be reverted and the manpage should be fixed to
> advertise this syntax since it is functional and in use.

#664869 was open undisputed for ten years, nobody cared.

I am tagging this bug wontfix and will close it with the trixie+1
release. Please point me to the place where this accidental misfeature
was ever documented, I might revisit my decision then.

If this actually was never documented, please refer this issue to the
technical committee.

Greetings
Marc

-- 
-----
Marc Haber | "I don't trust Computers. They | Mailadresse im Header
Leimen, Germany|  lose things."Winona Ryder | Fon: *49 6224 1600402
Nordisch by Nature |  How to make an American Quilt | Fax: *49 6224 1600421

Bug#1026898: deprecate QUOTAUSER post-bookworm

[Marc Haber]

On Sun, Nov 26, 2023 at 10:00:27AM +0100, Sylvain Beucler wrote:
> I use QUOTAUSER on a multi-user remote system, for a non-profit, where
> people tend to forget about disk space, to ensure any new 'adduser' sets a
> reasonable quota.
> 
> If there's an alternative please let me know.

The alternative would be to use edquota -p (quota) (username) after
creating the user. At least that's what adduser does when the quotauser
configuration option is set.

> I might contribute some tests but probably not soon.

It would be nice if adduser would give a clear error message if
quotauser is given and edquota is not present on the system, suggesting
that the quota package be installed, and exit RET_MORE_PACKAGES,
analogous to deluser's handling of perl not being present in line 198++
(probably easier than that because the existing code has to handle a
failed use).

An autopkgtest would mainly need to check the error handling and whether
setting quotauser will actually have a result if quota is installed. I
am not sure whether this also needs to run on a quota-enabled filesystem
which might be hard to do in an autopkgtest.

Greetings
Marc

-- 
-
Marc Haber | "I don't trust Computers. They | Mailadresse im Header
Leimen, Germany|  lose things."Winona Ryder | Fon: *49 6224 1600402
Nordisch by Nature |  How to make an American Quilt | Fax: *49 6224 1600421

Bug#1053565: RFS: openvpn3-client/20+dfsg-1 [ITP] -- virtual private network daemon (version 3)

[Marc Leeman]

> The issue and ITP talks about there being two packages, a library part
> and the client part. Has this changed (I cannot find the library part.)

I did start out to have different packages (client, library, dev); but
after discussing with upstream, I decided to mirror the upstream
(tarball) release since they release their client as a single tarball
and there is no other software that uses the library. For the moment,
I would have to use the git tarballs from github instead of what they
release as a tested client (integrated tarball of client and library).

I thought it would be best to follow the upstream lead on this.

> - changelog for an initial release should be only the first line, (as there
> are no changes to the debian package on the initial upload)

ack

> - you are creating an user. [1]
>   - As per Debian polic 9.3, the username shouldbe an invalid user and start 
> with an "_"
>   - If I am not mistaken, you can use tmpfiles.d to specify the
> directory /var/lib/openvpn to be owned by openvpn:openvpn, so that
> snipped in postinst might not be needed. (please verify)

I followed the user name lead on this one, but I'll adjust to match
the policy. Thanks.

> [1] https://wiki.debian.org/AccountHandlingInMaintainerScripts

> - unicode-impl.hpp
> I'm not convinced that this (license) issue is a non-issue. It might be
> solved in later versions of the file, but the version in the tarball
> does not allow modification.
> As you are anyway dfsg repacking (at least the version indicates this,
> see also below), hows' about removing the file and then reintroducing a
> fine one with a patch?

This is a difficult one (at least to me). I started investigating this
and asking around on #debian-mentors. Therre it was concluded that it
was a false positive. But since the licence seems to have changed for
this file (the different copies included in Debian indicate this), I
can do that, solves your concern.

The DFSG was needed because the library used a random binary for
testing without sources (some sparc binary iirc).

> - files installed in /usr/include
>   --> you want a -dev package.

I'll re-investigate this: since this client is standalone at the
moment (cf supra); it should not install any header at all.

> - d/copyright
>   - is not DEP-5 format.
>   - There is no indication why it is dfsg, and there id no
> Files-Exluded section.. so are you repacking at all?

The re-packaging was documented in debian/README.source

>   - For praticality reasons, it is recommended to keep the license of
> the debian the same as upstream. Otherwise, package upstreaming
> might get more difficult than needed. (GPL2 is anyway incompatibel
> with Affero GPL 3; your "or later" safes the day.)
>   - There is license text for the Gnu Affero General Public License 3,
> and it should be probably "AGPL-3" abbreviated.
>   - Note: I did not do a license review of the source files.

Inspired by the openvpn team, I'll review.

> - lintian overrides
>   - you need to comment the overrides WHY you overrode them.

ack

> - postinst
>   - remove the useless comment about utf-8, or let me know what you want
> to say with it.

my bad

> - the python part - I think this should be in a dedicated python module 
> package?
>
> - S-V could be updated.
>
> - There is no watch file.

This is in discussion with upstream to have a standard download
location that can be scanned. At the moment, the download location
does not allow indexing.

> - The package is in a team namespace on salsa, but d/control does not
>   indicate that it is team maintained.

As the ITP mentioned, part of the work was company sponsored, hence
the (default) teamspace. But since I seem to be the only one working
on it, I'll move it to a personal space.

> As usual, remove moreinfo when you are done updating your package.

ack


-- 
g. Marc

GPG: 827C FD74 BA46 8152 A041 F3A0 7A6A 4F17 5995 A65B

Bug#1055536: dpkg-dev: dpkg-shlibdeps refuses to print version number in the absence of ./debian/control

[Marc Jeanmougin]

Package: dpkg-dev
Version: 1.22.1
Severity: important

Dear Maintainer,

Since 1.22 (does happen in 1.22.1, did not happen in 1.21.21), running "dpkg-
shlibdeps --version" prints

---
dpkg-shlibdeps: error: cannot read debian/control: No such file or directory
---

instead of the version string (which can be obtained after a "mkdir debian;
touch debian/control")

---
Debian dpkg-shlibdeps version 1.22.1.

This is free software; see the GNU General Public License version 2 or
later for copying conditions. There is NO warranty.
---

This has downstream effects in tools that attempt to check the version of dpkg-
shlibdeps, as they can no longer work, e.g. "cpack -G DEB" (the .deb cmake
generator) does not work anymore.

Thanks a lot,


-- Package-specific info:
This system uses merged-usr-via-aliased-dirs, going behind dpkg's
back, breaking its core assumptions. This can cause silent file
overwrites and disappearances, and its general tools misbehavior.
See .

-- System Information:
Debian Release: trixie/sid
  APT prefers testing
  APT policy: (650, 'testing'), (600, 'unstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

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

Versions of packages dpkg-dev depends on:
ii  binutils  2.41-6
ii  bzip2 1.0.8-5+b1
ii  libdpkg-perl  1.22.1
ii  make  4.3-4.1
ii  patch 2.7.6-7
ii  perl  5.36.0-9
ii  tar   1.34+dfsg-1.2
ii  xz-utils  5.4.4-0.1

Versions of packages dpkg-dev recommends:
ii  build-essential  12.10
ii  clang-11 [c-compiler]1:11.1.0-6+b2
ii  clang-16 [c-compiler]1:16.0.6-16
ii  clang-9 [c-compiler] 1:9.0.1-20+b1
ii  fakeroot 1.32.1-1
ii  gcc [c-compiler] 4:13.2.0-1
ii  gcc-11 [c-compiler]  11.4.0-4
ii  gcc-12 [c-compiler]  12.3.0-10
ii  gcc-13 [c-compiler]  13.2.0-5
ii  gcc-8 [c-compiler]   8.4.0-7
ii  gcc-9 [c-compiler]   9.5.0-4
ii  gnupg2.2.40-1.1
ii  gpgv 2.2.40-1.1
ii  libalgorithm-merge-perl  0.08-5

Versions of packages dpkg-dev suggests:
ii  debian-keyring  2023.09.24

-- no debconf information

Bug#1055312: adduser: "addgroup user group" is mentioned in man page but does not work anymore (ex bug 664869)

[Marc Haber]

On Fri, Nov 03, 2023 at 11:27:43PM +0100, boffi wrote:
> $ man addgroup # says
> ...
> 
>Add an existing user to an existing group
>If called with two non-option arguments, adduser will add  an  existing
>user to an existing group.

adduser and addgroup share a man page, and the two-argument form is only
supported for adduser, not for addgroup, see SYNOPSIS in the manual
page.

And the text you quoted explicitly says that it is add_user_ that will
add an existing user to an existing group.

> but when I try to add a user to a group, this is what it happens
> 
> $ sudo addgroup donald ducks
> [sudo] password for boffi: 
> fatal: addgroup with two arguments is an unspecified operation.
> $ 

The message is correct, it is an unspecified operation according to the
SYNOPSIS.

Let me know what we can improve, but I think that everything is fine
here.

Greetings
Marc

-- 
-----
Marc Haber | "I don't trust Computers. They | Mailadresse im Header
Leimen, Germany|  lose things."Winona Ryder | Fon: *49 6224 1600402
Nordisch by Nature |  How to make an American Quilt | Fax: *49 6224 1600421

Bug#1055065: doesnt find useradd

[Marc Haber]

Package: debspawn
Version: 0.6.2-1
Severity: important

Important because this breaks debspawn create

debspawn create sid errors out because the tool cannot find useradd. I
have added adduser manually to "include_pkgs" in osbase.py and this
allows debspawn create sid to finish.

Greetings
Marc


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

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

Versions of packages debspawn depends on:
ii  debootstrap1.0.133
ii  python33.11.4-5+b1
ii  python3-tomlkit0.12.1-1
ii  systemd-container  254.5-1
ii  zstd   1.5.5+dfsg2-2

Versions of packages debspawn recommends:
ii  devscripts  2.23.6
ii  dpkg-dev1.22.0

Versions of packages debspawn suggests:
ii  build-essential  12.10
ii  sudo 1.9.14p2-1

-- no debconf information

Bug#1033548: 02:00 timers dont run in DST transition night

[Marc Haber]

On Sun, Oct 29, 2023 at 11:24:54PM +0100, Michael Biebl wrote:
> I think the above upstream issue pretty much describes what you are seeing,
> so marking as forwarded accordingly.

It does. It also nicely reflects upstream's attitude "Yes, you're holding
it wrong, and we don't care how ugly your workarounds might be as long
as we don't have to code anything".

Greetings
Marc, who will probably just avoid 1.59-3.01 am for the rest of life


-- 
-----
Marc Haber | "I don't trust Computers. They | Mailadresse im Header
Leimen, Germany|  lose things."Winona Ryder | Fon: *49 6224 1600402
Nordisch by Nature |  How to make an American Quilt | Fax: *49 6224 1600421

Bug#1054558: iotop: crashes on non-utf8 characters

[Marc Lehmann]

Package: iotop
Version: 0.6-42-ga14256a-0.1+b2
Severity: normal

Dear Maintainer,

independent of locale (or the fatc that locales are per-process), if
iotop finds a command line argument that is not utf-8 encoded, it simply
crashes. regardless of how it handles encodings it does not understand, it
should not simply crash:

   File "/usr/lib/python3/dist-packages/iotop/data.py", line 311, in get_cmdline
   cmdline = proc_cmdline.read(4096)
 ^^^
 File "", line 322, in decode
   UnicodeDecodeError: 'utf-8' codec can't decode byte 0xe9 in position 2259: 
invalid continuation byte

-- System Information:
Debian Release: 12.2
  APT prefers stable-updates
  APT policy: (990, 'stable-updates'), (990, 'stable-security'), (990, 
'stable'), (500, 'unstable-debug'), (500, 'testing-debug'), (500, 
'oldstable-debug'), (500, 'unstable'), (500, 'testing'), (1, 
'experimental-debug'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386, x32

Kernel: Linux 6.1.55-schmorp (SMP w/24 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_USER, TAINT_WARN, 
TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=en_IE.UTF-8, LC_CTYPE=en_IE.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 iotop depends on:
ii  python3  3.11.2-1+b1

iotop recommends no packages.

iotop suggests no packages.

-- no debconf information

Bug#1040138: changelog-file-missing-explicit-entry needs exception for bookworm

[Marc Haber]

On Mon, Oct 09, 2023 at 02:06:58AM +0200, Cyril Brulebois wrote:
> That exception only hides the root of the bug, which includes (at least)
> a messed up version sorting.

What is the recommended way to get rid of this? Re-sorting
changelog entries? Adding an override?

> Adding another exception for bookworm will only lead to more
> whack-a-mole down the line (see #1051140).

I don't see the connection here.

Greetings
Marc

-- 
-----
Marc Haber | "I don't trust Computers. They | Mailadresse im Header
Leimen, Germany|  lose things."Winona Ryder | Fon: *49 6224 1600402
Nordisch by Nature |  How to make an American Quilt | Fax: *49 6224 1600421

Bug#1053565: RFS: openvpn3-client/20+dfsg-1 [ITP] -- virtual private network daemon (version 3)

[Marc Leeman]

Package: sponsorship-requests
Severity: wishlist

Dear Maintainer,


Dear mentors,

I am looking for a sponsor for my package "openvpn3-client":

 * Package name : openvpn3-client
   Version  : 20+dfsg-1
   Upstream contact : OpenVPN Solutions LLC 
 * URL  : https://openvpn.net/
 * License  : Gnu Affero General Public License 3
 * Vcs  : https://salsa.debian.org/televic-team/openvpn3-client
   Section  : net

The source builds the following binary packages:

  openvpn3-client - virtual private network daemon (version 3)

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

  https://mentors.debian.net/package/openvpn3-client/

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

  dget -x 
https://mentors.debian.net/debian/pool/main/o/openvpn3-client/openvpn3-client_20+dfsg-1.dsc

Changes for the initial release:

 openvpn3-client (20+dfsg-1) unstable; urgency=medium
 .
   * Initial release. (Closes: #904044)
   * d/control: do not depend on openvpn2 dev headers
   * d/postinst: create user before chown
   * d/README: add comment on lintian-warning unicode-impl.hpp
   * d/README: update dfsg motivation
   * remove sum files (see d/README.source)

Regards,

Additional discussion on the packaging with upstream can be found here:
https://github.com/OpenVPN/openvpn3-linux/issues/193

--
  Marc Leeman

Bug#1053498: ITP: amqp-cpp -- CPP RabbitMQ communication library

[Marc Leeman]

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

* Package name: amqp-cpp
  Version : 4.3.26
  Upstream Contact: https://github.com/CopernicaMarketingSoftware/AMQP-CPP/wiki
* URL : https://github.com/CopernicaMarketingSoftware/AMQP-CPP
* License : Apache-2.0
  Programming Lang: C++
  Description : CPP RabbitMQ communication library

 AMQP-CPP is a C++ library for communicating with a RabbitMQ message
 broker. The library can be used to parse incoming data from a RabbitMQ
 server, and to generate frames that can be sent to a RabbitMQ server.

Bug#1053497: ITP: tcnopen -- TCNOpen Library for IEC61375 standardised communication

[Marc Leeman]

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

* Package name: tcnopen
  Version : 2.1.0.0
  Upstream Contact: https://sourceforge.net/p/tcnopen/wiki/Home/
* URL : https://www.tcnopen.org/
* License : MPL-2.0, GPL-3.0+
  Programming Lang: C
  Description : TCNOpen Library for IEC61375 standardised communication

  TCN (Train Communication Network) is a series of international standards
 (IEC61375) developed by Working Group 43 of the IEC, specifying a
 communication system for the data communication within and between vehicles
 of a train. It is currently in use on many thousands of trains in the world
 in order to allow electronic devices to exchange information while operating
 aboard the same train.
 .
 TCNOpen is an open source initiative which the partner railway industries
 created with the aim to build in collaboration some key parts of new or
 upcoming railway standards, commonly known under the name TCN.

Bug#1053443: automount should not act if filesystem is already mounted

[Marc Haber]

On Wed, Oct 04, 2023 at 08:41:10PM +0200, Michael Biebl wrote:
> Do you both /efi *and* /boot/efi
> 
> The automount unit is for efi.automount

No, just /boot/efi, but the aide run triggers the automount, which
affects for some strange reason /boot/efi and makes the inode numbers
change.

Greetings
Marc

-- 
-
Marc Haber | "I don't trust Computers. They | Mailadresse im Header
Leimen, Germany|  lose things."Winona Ryder | Fon: *49 6224 1600402
Nordisch by Nature |  How to make an American Quilt | Fax: *49 6224 1600421

Bug#1052487: aide-common: please recommend canonical "cron | cron-daemon"

[Marc Haber]

On Tue, Oct 03, 2023 at 11:26:51PM +0200, Alexandre Detiste wrote:
> BTW: to make systemd-cron life easier, the .service/.timer
> name has to exactly match the cron job name.

Is that a recommendation to rename /etc/cron.daily/aide to
/etc/cron.daily/dailyaidecheck because timer and service are
dailyaidechck as well?

Greetings
Marc

-- 
-
Marc Haber | "I don't trust Computers. They | Mailadresse im Header
Leimen, Germany|  lose things."Winona Ryder | Fon: *49 6224 1600402
Nordisch by Nature |  How to make an American Quilt | Fax: *49 6224 1600421