Bug#1035604: progress-linux-container: fails to upgrade from 'bullseye': diversion conflict

[Andreas Beckmann]

Package: progress-linux-container
Version: 20221002-8
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package fails to upgrade from
'bullseye'.
It installed fine in 'bullseye', then the upgrade to 'bookworm' fails.

>From the attached log (scroll to the bottom...):

  Preparing to unpack .../112-progress-linux-container_20221002-8_all.deb ...
  dpkg-divert: error: 'diversion of /sbin/halt to 
/lib/container/divert/halt.orig by progress-linux-container' clashes with 
'diversion of /sbin/halt to /lib/open-infrastructure/container/divert/halt.orig 
by progress-linux-container'
  dpkg: error processing archive 
/tmp/apt-dpkg-install-ujBXu1/112-progress-linux-container_20221002-8_all.deb 
(--unpack):
   new progress-linux-container package pre-installation script subprocess 
returned error exit status 2
  Preparing to unpack .../113-sysstat_12.6.1-1_amd64.deb ...
  Unpacking sysstat (12.6.1-1) over (12.5.2-2) ...
  Errors were encountered while processing:
   /tmp/apt-dpkg-install-ujBXu1/112-progress-linux-container_20221002-8_all.deb


cheers,

Andreas


progress-linux-container_20221002-8.log.gz
Description: application/gzip

Bug#1035603: mpdscribble: prompting due to modified conffiles which were not modified by the user: /etc/mpdscribble.conf

[Andreas Beckmann]

Package: mpdscribble
Version: 0.24-2
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package failed the piuparts
upgrade test because dpkg detected a conffile as being modified and then
prompted the user for an action. As there is no user input, this fails.
But this is not the real problem, the real problem is that this prompt
shows up in the first place, as there was nobody modifying this conffile
at all, the package has just been installed and upgraded...

This is a violation of policy 10.7.3, see
https://www.debian.org/doc/debian-policy/ch-files.html#behavior,
which says "[These scripts handling conffiles] must not ask unnecessary
questions (particularly during upgrades), and must otherwise be good
citizens."

https://wiki.debian.org/DpkgConffileHandling should help with figuring
out how to do this properly.

In https://lists.debian.org/debian-devel/2009/08/msg00675.html and
followups it has been agreed that these bugs are to be filed with
severity serious.

>From the attached log (scroll to the bottom...):

  Setting up mpdscribble (0.24-2+b1) ...
  
  Configuration file '/etc/mpdscribble.conf'
   ==> File on system created by you or by a script.
   ==> File also in package provided by package maintainer.
 What would you like to do about it ?  Your options are:
  Y or I  : install the package maintainer's version
  N or O  : keep your currently-installed version
D : show the differences between the versions
Z : start a shell to examine the situation
   The default action is to keep your current version.
  *** mpdscribble.conf (Y/I/N/O/D/Z) [default=N] ? dpkg: error processing 
package mpdscribble (--configure):
   end of file on stdin at conffile prompt


cheers,

Andreas


mpdscribble_0.24-2+b1.log.gz
Description: application/gzip

Bug#1035092: gnome-shell: Nautilus doesn't gain focus when launched from directory search

[Chandra Sekar Srinivasan]

While I observed this first with Nautilus, the issue is not limited to it.
Any application started by opening a file searched in Activities starts
without focus.

Bug#1035602: tracker.debian.org parts of page not updating.

[Peter Green]

package: tracker.debian.org

The "news" on the tracker pages seems to be updating, but the information
on package versions does not. This is most noticable for new Packages
where the page still says "Package is gone" over a week after the
package was first uploaded.

https://tracker.debian.org/pkg/rust-virtiofsd

Bug#1035601: lprint: uninstallable together with altos

[Marc Lehmann]

Package: lprint
Version: 1.1.0-2
Severity: normal

Dear Maintainer,

I don't know if this is a problem with this package or altos, but lrpint cannot 
be installed even though apt thinks they should not conflict:

Preparing to unpack lprint_1.1.0-2_amd64.deb ...
Unpacking lprint (1.1.0-2) ...
dpkg: error processing archive lprint_1.1.0-2_amd64.deb (--install):
 trying to overwrite directory '/usr/lib/x86_64-linux-gnu/systemd/system' in 
package altos 1.9.15-1+b1 with nondirectory

I am not sure either package should contain 
/usr/lib/x86_64-linux-gnu/systemd/system, and I am also not sure that this is 
the rght place for service files :)

-- System Information:
Debian Release: 12.0
  APT prefers testing-security
  APT policy: (500, 'testing-security'), (500, 'testing')
Architecture: amd64 (x86_64)

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

Versions of packages lprint depends on:
ii  libc6  2.36-9
ii  libcups2   2.4.2-3
ii  libpappl1  1.3.1-2

lprint recommends no packages.

lprint suggests no packages.

Bug#1035515: [pre-approval] unblock: gdb/13.1-2.1

[Cyril Brulebois]

Control: tag -1 confirmed

Hi,

On Thu, May 04, 2023 at 05:53:24PM +0200, Hector Oron wrote:
>   While I agree we should get this fixed on bookworm, I believe to be
> able to unblock a package, the package should exist in the archive.

Sure, but it's fine to ask for a pre-approval. :)

Emanuele Rocca  (2023-05-04):
> On Thu, May 04, 2023 at 05:53:24PM +0200, Hector Oron wrote:
> >   Since you have not uploaded the package yet, are you fine if I do a
> > regular upload with the patch, then use this unblock request to add
> > the package to bookworm.
> 
> Of course, please go ahead.

The proposed, targeted fix seems very much appropriate; please let us
know once it's in the archive. I don't anticipate the maintainer upload
to be less suitable. :)


Cheers,
-- 
Cyril Brulebois (k...@debian.org)
D-I release manager -- Release team member -- Freelance Consultant


signature.asc
Description: PGP signature

Bug#1034428: unblock: vmdb2/0.27-1

[Cyril Brulebois]

Hi,

Cyril Brulebois  (2023-05-05):
> Gunnar Wolf  (2023-04-14):
> > vmdb2 is a leaf package. The code changes are quite minor. While there
> > are several alternatives to vmdb2 in Debian, switching from one image
> > generating system to another might be quite heavy for the users.
> 
> Spotted by Helmut (cc-ed): that's not true (in either stable or unstable),
> since autopkgtest depends on it… and it seems that update would break it.
> 
> I'll let Helmut expand, and possibly formulate a plan.

OK, so much fail on my part here, my bad.

First, fixing Helmut's mail address.

Second, I hadn't spotted both unblock requests had been merged (didn't
show up in my debian-release folder while looking at vmdb2 mails), I
only meant to close one of them as a duplicate of the other one.


That being said, it seems pretty clear to me at this point that the
proposed update isn't reasonable: it would break autopkgtest (and
possibly parts of ci.debian.net?), and it contains a bunch of
irrelevant changes.

We would need something much more targeted. I'm not commenting on
whether the changes are even needed given the e2fsprogs package has
dropped the new options (there are probably some combinations of
source and destination environments that could benefit from a vmdb2
update, but I'd like to avoid thinking about that again…).


Cheers,
-- 
Cyril Brulebois (k...@debian.org)
D-I release manager -- Release team member -- Freelance Consultant


signature.asc
Description: PGP signature

Bug#1035600: coreutils: pr: columnation just doesn't work? at all?

[наб]

Package: coreutils
Version: 9.1-1
Severity: normal

  Dear Maintainer,

$ cat > /tmp/q
Not picky about patches — inline, attachment
zupa tusta zupa tusta zupa tusta zupa tusta
zupka tłuściutka zupka tłuściutka zupka tłuś
$ pr -Fm /tmp/q /tmp/q


2023-05-06 03:12  Page 1


Not picky about patches — inline, at Not picky about patches — inline, at
zupa tusta zupa tusta zupa tusta zu zupa tusta zupa tusta zupa tusta zu
zupka tłuściutka zupka tłuściutka zupka zupka tłuściutka zupka tłuściutka zupka

  why. how. what's the point of pr then?
  FTR, the correct output is

$ out/cmd/pr -Fm /tmp/q /tmp/q


2023-05-06 03:12Page 1


Not picky about patches — inline, a Not picky about patches — inline, a
zupa tusta zupa tusta zupa tusta zu zupa tusta zupa tusta zupa tusta zu
zupka tłuściutka zupka tłuściutka z zupka tłuściutka zupka tłuściutka z

  I didn't even try to see what happens with double-wide characters,
  because that would kill me instantly.

  Best,
  наб

-- System Information:
Debian Release: 12.0
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: x32 (x86_64)
Foreign Architectures: amd64, i386

Kernel: Linux 6.1.0-2-amd64 (SMP w/2 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 coreutils depends on:
ii  libacl1  2.3.1-3
ii  libattr1 1:2.5.1-4
ii  libc62.36-9
ii  libgmp10 2:6.2.1+dfsg1-1.1
ii  libselinux1  3.4-1+b5

coreutils recommends no packages.

coreutils suggests no packages.

-- no debconf information


signature.asc
Description: PGP signature

Bug#1035599: coreutils: pr: taking +0 to be a file-name is inconsistent with refusing +99999999999999999999, diverges from SysVr4

[наб]

Package: coreutils
Version: 8.32-4+b1
Version: 9.1-1
Severity: normal

Dear Maintainer,

  $ pr +0
  pr: +0: No such file or directory
  $ pr +
  pr: + argument '' too large
this is inconsistent.

Issue 8 Draft 3 says
  110734  The following options shall be supported. In the following option 
descriptions, column, lines,
  110735  offset, page, and width are positive decimal integers; gap is a 
non-negative decimal integer.

  110736  +page Begin output at page number page of the formatted input.
so this is strictly-speaking legal, but still weird:
+0 is a file, but all other +[0-9][0-9]* combinations are numbers.

As literature review:
  SysVr4 accepts +0 as a number (and doesn't check overflow), and
  NetBSD refuses +0 (likewise).

Best,
наб

-- System Information:
Debian Release: 12.0
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: x32 (x86_64)
Foreign Architectures: amd64, i386

Kernel: Linux 6.1.0-2-amd64 (SMP w/2 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 coreutils depends on:
ii  libacl1  2.3.1-3
ii  libattr1 1:2.5.1-4
ii  libc62.36-9
ii  libgmp10 2:6.2.1+dfsg1-1.1
ii  libselinux1  3.4-1+b5

coreutils recommends no packages.

coreutils suggests no packages.

-- no debconf information


signature.asc
Description: PGP signature

Bug#1035598: /var/lib/dpkg/info/kanboard.postinst: 24: lighty-enable-mod: not found

[James Valleroy]

Package: kanboard
Version: 1.2.26+ds-1
Severity: important
X-Debbugs-Cc: jvalle...@mailbox.org

Dear Maintainer,

   * What led up to the situation?

I tried to install kanboard on a Debian bookworm VPS.

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

# apt install kanboard

   * What was the outcome of this action?

Setting up kanboard (1.2.26+ds-1) ...
/var/lib/dpkg/info/kanboard.postinst: 24: lighty-enable-mod: not found
dpkg: error processing package kanboard (--configure):
 installed kanboard package post-installation script subprocess returned error e
xit status 1

   * What outcome did you expect instead?

Should not cause an error when lighttpd is not installed.


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

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

Versions of packages kanboard depends on:
ii  apache2 [httpd-cgi] 2.4.57-2
ii  architecture-properties [architecture-is-64-bi  0.1.1
t]
ii  composer2.5.5-1
ii  fonts-font-awesome  5.0.10+really4.7.0~dfsg-4.1
ii  php-christianriesen-otp 1.4.3-2
pn  php-cli 
ii  php-common  2:93
ii  php-eluceo-ical 0.16.1-2
ii  php-gd  2:8.2+93
ii  php-gregwar-captcha 1.1.9+ds-2
ii  php-matthiasmullie-minify   1.3.68-3
ii  php-mbstring2:8.2+93
ii  php-parsedown   1.7.4-1
ii  php-pimple  3.5.0-1
ii  php-psr-log 1.1.4-2
ii  php-sqlite3 2:8.2+93
ii  php-swiftmailer 6.3.0-3
ii  php-symfony-console 5.4.22+dfsg-2
ii  php-symfony-event-dispatcher5.4.22+dfsg-2
ii  php-symfony-finder  5.4.22+dfsg-2
ii  php-xml 2:8.2+93
ii  php8.2-cli [php-json]   8.2.5-2
ii  php8.2-fpm [php-json]   8.2.5-2
ii  php8.2-gd [php-gd]  8.2.5-2
ii  php8.2-mbstring [php-mbstring]  8.2.5-2
ii  php8.2-sqlite3 [php-sqlite3]8.2.5-2
ii  php8.2-xml [php-xml]8.2.5-2

Versions of packages kanboard recommends:
ii  exim4-daemon-light [mail-transport-agent]  4.96-14
ii  php-curl   2:8.2+93
ii  php-fpm2:8.2+93
ii  php-ldap   2:8.2+93
ii  php-zip2:8.2+93
ii  php8.2-curl [php-curl] 8.2.5-2
ii  php8.2-fpm [php-fpm]   8.2.5-2
ii  php8.2-ldap [php-ldap] 8.2.5-2
ii  php8.2-zip [php-zip]   8.2.5-2

kanboard suggests no packages.

-- no debconf information

Bug#1035587: linux: broken AHCI controller on MIPS Loongson 3 (regression from 5.10.162-1)

[YunQiang Su]

Aurelien Jarno  于2023年5月6日周六 04:30写道：
>
> Source: linux
> Version: 5.10.178-3
> Severity: important
> X-Debbugs-Cc: d...@debian.org, debian-m...@lists.debian.org, s...@debian.org
>
> Following the point release, the buildd mipsel-osuosl-03.d.o does not
> boot anymore, with errors in the AHCI controller:
>
> [   35.912147] ata4.00: exception Emask 0x0 SAct 0x2000 SErr 0x0 action 
> 0x6 frozen
> [   35.919769] ata4.00: failed command: WRITE FPDMA QUEUED
> [   35.924968] ata4.00: cmd 61/20:e8:00:f0:e1/00:00:00:00:00/40 tag 29 ncq 
> dma 16384 out
> [   35.924968]  res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 
> (timeout)
> [   35.940097] ata4.00: status: { DRDY }
> [   35.943743] ata4: hard resetting link
>
> While that initially looks like a hardware issue, it appears that
> reverting the kernel to 5.10.162-1 (from 5.10.178-3) fixes the issue.
> Strangely mipsel.osuosl-05.d.o, which seems to be similar hardware (CPU,
> motherboard and SATA drive), does not exhibit the same issue.
>

Maybe the different firmwares are used for them...
CCed Huacai and Jiaxun.

> You'll find attached the output of /proc/cpuinfo, lspci and the full
> boot log.



-- 
YunQiang Su

Bug#1034650: debian-installer: bookworm d-i rc1: apt-get clean breaks bash-completion

[Cyril Brulebois]

Control: clone -1 -2
Control: reassign -2 debian-installer
Control: retitle -2 debian-installer: investigate setting 
APT::Keep-Downloaded-Packages=false

Hi again,

Cyril Brulebois  (2023-05-04):
> David Kalnischkies  (2023-05-04):

[…]

> Entirely fair, thanks. Putting debian-boot@ in copy since currently
> the bug is assigned to apt… and others might have some feedback about
> my proposal(s).

No feedback in either direction at the moment, I'm going ahead as the
Bookworm clock is ticking.

> > Is it perhaps just wanting to remove /var/cache/apt/archives/*.deb ?
> > If so, could you switch to: -o APT::Keep-Downloaded-Packages=false
> > (well, probably in a conf file rather than on each command line).
> 
> There are various apt-get (not clean) calls, some of them wrapped, and
> I have no idea what the consequences of tweaking them could be. In any
> case, while deplying a conf file during the installation process could
> be attempted, it's far too late to try toying with that…
> 
> We can probably keep track of the suggestion via some bug report
> against debian-installer, so that someone can investigate that
> post-Bookworm (probably removing the possible tweak discussed below).

Doing so via the control commands above.

> For Bookworm, I'm tempted to add `apt-cache gencaches` after `apt-get
> clean` in finish-install, restoring the files bash-completion relies
> on.

I'll do that in finish-install and add a pointer to this bug report; I
won't add a Closes statement though, as I'm not sure what other users
will be implementing (for Docker etc.)… I'll leave it up to you to
decide what's best regarding this bug report (the -1 one).


Cheers,
-- 
Cyril Brulebois (k...@debian.org)
D-I release manager -- Release team member -- Freelance Consultant


signature.asc
Description: PGP signature

Bug#1028507: digikam: downloads binary blobs from the internet

[Steven Robbins]

forwarded 1028507 https://bugs.kde.org/show_bug.cgi?id=438317
thanks

On Thu, 12 Jan 2023 06:24:07 +0100 Christoph Anton Mitterer 
 wrote:

> Every time when starting digikam, a dialog pops up asking to download
> some engines for redeye removal and face detection from the internet,
> which would cause them to be stored in /home/calestyo/.local/share/digikam/ 
> 
> Could that please be disabled?

It's coming in version 8.

> a) It's a security risk. It's aboslutely unclear who controls these files
>(at least not debian).

I hear your concerns.  These files are data that used to be shipped as part of 
digikam and were later unbundled, which led to the download prompt.  You can 
read through the upstream bug for a full discussion. 

-Steve


signature.asc
Description: This is a digitally signed message part.

Bug#1035587: linux: broken AHCI controller on MIPS Loongson 3 (regression from 5.10.162-1)

[Cyril Brulebois]

Hi,

Knowing nothing about HW, MIPS, etc. as usual…

Aurelien Jarno  (2023-05-05):
> Following the point release, the buildd mipsel-osuosl-03.d.o does not
> boot anymore, with errors in the AHCI controller:
> 
> [   35.912147] ata4.00: exception Emask 0x0 SAct 0x2000 SErr 0x0 action 
> 0x6 frozen
> [   35.919769] ata4.00: failed command: WRITE FPDMA QUEUED
> [   35.924968] ata4.00: cmd 61/20:e8:00:f0:e1/00:00:00:00:00/40 tag 29 ncq 
> dma 16384 out
> [   35.924968]  res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 
> (timeout)
> [   35.940097] ata4.00: status: { DRDY }
> [   35.943743] ata4: hard resetting link
> 
> While that initially looks like a hardware issue, it appears that
> reverting the kernel to 5.10.162-1 (from 5.10.178-3) fixes the issue.
> Strangely mipsel.osuosl-05.d.o, which seems to be similar hardware
> (CPU, motherboard and SATA drive), does not exhibit the same issue.

A quick search between both versions suggests 1 AHCI commit, and 2
Loongson ones, both in the PCI layer.

- ab711f3eda7a62c800b41997e818b675812f53a9 is AHCI, apparently
  Intel-only, so not interesting.
- 654ae539254d10042869fdc77ad04c09e7eff1fd and
  faa050d2ff8820f450b69b84645e74b6934ed5ad are abouts quirks, the first
  one adding them for LS7A, the second one extending that to more LS7A
  ports, and to LS2K.

Glancing at bootlog.txt, it seems both AHCI and PCI work together, and
that LS7A is involved, so maybe those two PCI commits are relevant? Why
the other similar machine isn't impacted, I don't know.

Direct links for commits in the linux-5.10.y branch:
 - 
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=654ae539254d10042869fdc77ad04c09e7eff1fd
 - 
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=faa050d2ff8820f450b69b84645e74b6934ed5ad


Cheers,
-- 
Cyril Brulebois (k...@debian.org)
D-I release manager -- Release team member -- Freelance Consultant


signature.asc
Description: PGP signature

Bug#1035596: coreutils: pr: --number-lines= yields "extra characters or invalid number in the argument: ‘SHELL=/bin/bash’: ERANGE"

[наб]

Package: coreutils
Version: 8.32-4+b1
Version: 9.1-1
Severity: normal

Dear Maintainer,

:v

наб

-- System Information:
Debian Release: 12.0
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: x32 (x86_64)
Foreign Architectures: amd64, i386

Kernel: Linux 6.1.0-2-amd64 (SMP w/2 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 coreutils depends on:
ii  libacl1  2.3.1-3
ii  libattr1 1:2.5.1-4
ii  libc62.36-9
ii  libgmp10 2:6.2.1+dfsg1-1.1
ii  libselinux1  3.4-1+b5

coreutils recommends no packages.

coreutils suggests no packages.

-- no debconf information


signature.asc
Description: PGP signature

Bug#1035595: gl-117: Crash on exit

[Nils Dagsson Moskopp]

Package: gl-117
Version: 1.3.2-3+b1
Severity: normal
X-Debbugs-Cc: nils+debian-report...@dieweltistgarnichtso.net

Dear Maintainer,

after the gl-117 main menu had loaded, Ipressed ESCAPE and Y, gl-117 crashed.
The last log message was “corrupted double-linked list”, followed by “abort”.

My screen was set to 1024x768 (gl-117 resolution) instead of a previous one –
so I had to manually set it back with: xrandr --output LVDS1 --mode 1400x1050

So I immediately tried it again; I got a different error message. Here it is:

> malloc(): unsorted double linked list corrupted
> abort

The last “regular” message that the program printed to the terminal was this:

> Info: Pilots saved

-- System Information:
Debian Release: 11.7
  APT prefers stable
  APT policy: (900, 'stable'), (500, 'oldoldstable')
Architecture: i386 (i686)

Kernel: Linux 5.10.0-10-686 (SMP w/2 CPU threads)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages gl-117 depends on:
ii  freeglut3   2.8.1-6
ii  gl-117-data 1.3.2-3
ii  libc6   2.31-13+deb11u6
ii  libgcc-s1 [libgcc1] 10.2.1-6
ii  libgcc1 1:8.3.0-6
ii  libgl1  1.3.2-1
ii  libgl1-mesa-glx 20.3.5-1
ii  libglu1-mesa [libglu1]  9.0.1-1
ii  libsdl-mixer1.2 1.2.12-16+b1
ii  libsdl1.2debian 1.2.15+dfsg2-6
ii  libstdc++6  10.2.1-6

gl-117 recommends no packages.

gl-117 suggests no packages.

-- no debconf information

Bug#1035594: eclipse-tracecompass: depends on no longer available libeclipse-osgi-util-java,libequinox-p2-ui-sdk-java

[Andreas Beckmann]

Package: eclipse-tracecompass
Version: 7.0.0+repack-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package is no longer
installable in sid:

  The following packages have unmet dependencies:
   eclipse-tracecompass : Depends: libeclipse-osgi-util-java but it is not 
installable
  Depends: libequinox-p2-ui-sdk-java but it is not 
installable


Cheers,

Andreas

Bug#1034689: gl-117: Moving mouse creates lag (workaround: use software rendering)

[Nils Dagsson Moskopp]

Package: gl-117
Version: 1.3.2-3+b1
Followup-For: Bug #1034689
X-Debbugs-Cc: nils+debian-report...@dieweltistgarnichtso.net

Dear Maintainer,

I tested gl-117 on a Thinkpad T60 and found the lag does not to occur on it;
I actually did get 60 fps almost consistently, sometimes dropping to 45 fps.

I have no idea what could make gl-117 work so much worse on newer hardware …

Here is the terminal output of “glxinfo |grep -i ' version'” on that laptop:

server glx version string: 1.4
client glx version string: 1.4
GLX version: 1.4
Version: 20.3.5
Max core profile version: 0.0
Max compat profile version: 1.4
Max GLES1 profile version: 1.1
Max GLES[23] profile version: 2.0
OpenGL version string: 1.4 Mesa 20.3.5
OpenGL ES profile version string: OpenGL ES 2.0 Mesa 20.3.5
OpenGL ES profile shading language version string: OpenGL ES GLSL ES 1.0.16

-- System Information:
Debian Release: 11.7
  APT prefers stable
  APT policy: (900, 'stable'), (500, 'oldoldstable')
Architecture: i386 (i686)

Kernel: Linux 5.10.0-10-686 (SMP w/2 CPU threads)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages gl-117 depends on:
ii  freeglut3   2.8.1-6
ii  gl-117-data 1.3.2-3
ii  libc6   2.31-13+deb11u6
ii  libgcc-s1 [libgcc1] 10.2.1-6
ii  libgcc1 1:8.3.0-6
ii  libgl1  1.3.2-1
ii  libgl1-mesa-glx 20.3.5-1
ii  libglu1-mesa [libglu1]  9.0.1-1
ii  libsdl-mixer1.2 1.2.12-16+b1
ii  libsdl1.2debian 1.2.15+dfsg2-6
ii  libstdc++6  10.2.1-6

gl-117 recommends no packages.

gl-117 suggests no packages.

-- no debconf information

Bug#1034672: check your grub.cfg

[Thomas Lange]

Hi,

you did not say which FAI version you are using and how you did create
the bookworm image. I wonder why you still have
  gfxpayload=$resolution
in the grub.cfg? This was removed in FAI 5.9.1.
Also insmod all_video is used since a long time.


Please also check if this ISO does not work with Ventoy
https://fai-project.org/fai-cd/faicd64-large_6.0.iso

-- 
reagrds Thomas

Bug#1035503: [Debian-iot-maintainers] Bug#1035503: glewlwyd-common: prompting due to modified conffiles which were not modified by the user: /etc/glewlwyd/config.json

[Nicolas Mora]

Hello,

I'm having a hard-time fixing this issue.
I've read [1] and related documentation, and I still make anything work.
For some reason, the commands I add in the glewlwyd-common package seems 
not to be executed when I upgrade from bullseye to bookworm and I can't 
figure out why...


- I've added the rm_conffile and al in a new set of 
glewlwyd-common.{postinst,preinst,prerm} scripts


- I've used dpkg-maintscript-helper command instead:
  dpkg-maintscript-helper rm_conffile /etc/glewlwyd/config.json 2.5.2 
glewlwyd-common -- "$@"


- I've added a glewlwyd-common.maintscript, same no result

- I've tried with a conffiles too, no luck

Does anyone has an idea on how to fix this issue?

/Nicolas

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

Bug#1035593: unblock: kwin/4:5.27.2-2

[Hefee]

Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
X-Debbugs-Cc: k...@packages.debian.org, he...@debian.org
Control: affects -1 + src:kwin

Please unblock package kwin

[ Reason ]
Fix 1033212. For limba phones kwin is not usable at all, with that fix
it is usable again.

[ Impact ]
Plasma mobile is not usable on limba phones.

[ Tests ]
Marco Mattiolo, the author of the patch for kwin, tested it on their
devices.

[ Risks ]
The patch is very simple and straightforward. For me it seems not very
likly that it has bad outcome for other users. On experimental there is
also kwin 5.27.3 with that patch included and that is also tested be a
bunch of people.

[ 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 testing

[ Other info ]
You do a great work and you are very fast responding ;)

unblock kwin/4:5.27.2-2
diff -Nru kwin-5.27.2/debian/changelog kwin-5.27.2/debian/changelog
--- kwin-5.27.2/debian/changelog2023-02-28 15:01:10.0 +0100
+++ kwin-5.27.2/debian/changelog2023-05-05 14:22:35.0 +0200
@@ -1,3 +1,12 @@
+kwin (4:5.27.2-2) unstable; urgency=medium
+
+  * Team upload.
+
+  [ Marco Mattiolo ]
+  * Backport patch to fix kwin for Lima (Pinephone) (Closes: #1033212)
+
+ -- Sandro Knauß   Fri, 05 May 2023 14:22:35 +0200
+
 kwin (4:5.27.2-1) unstable; urgency=medium
 
   [ Aurélien COUDERC ]
diff -Nru kwin-5.27.2/debian/patches/fix-for-Lima-disabling-GLSL.patch 
kwin-5.27.2/debian/patches/fix-for-Lima-disabling-GLSL.patch
--- kwin-5.27.2/debian/patches/fix-for-Lima-disabling-GLSL.patch
1970-01-01 01:00:00.0 +0100
+++ kwin-5.27.2/debian/patches/fix-for-Lima-disabling-GLSL.patch
2023-05-05 14:16:46.0 +0200
@@ -0,0 +1,47 @@
+From 64d682a646d111a0250bbe3bff77ef0cead91403 Mon Sep 17 00:00:00 2001
+From: Hannah Kiekens 
+Date: Tue, 28 Feb 2023 21:04:37 +
+Subject: [PATCH] Enable GLSL for Mali (Lima) / PinePhone devices
+
+Commit 88cf8355 changed the behaviour of Mali (Lima) / PinePhone devices by 
disabling GLSL
+88cf8355 got backported in 5.27.1 and broke PinePhone devices (White rectangle 
on topright quarter of a black screen)
+
+This patch restores the behaviour of 5.27.0
+
+
+(cherry picked from commit 0543949df709c69c99c46c9abad483250b01c288)
+---
+ .../libkwineffects/data/glplatform/lima-mali400-desktop-3.0| 2 +-
+ src/libkwineffects/kwinglplatform.cpp  | 3 +--
+ 2 files changed, 2 insertions(+), 3 deletions(-)
+
+diff --git a/autotests/libkwineffects/data/glplatform/lima-mali400-desktop-3.0 
b/autotests/libkwineffects/data/glplatform/lima-mali400-desktop-3.0
+index 8e32a85af81..cf83810fd8b 100644
+--- a/autotests/libkwineffects/data/glplatform/lima-mali400-desktop-3.0
 b/autotests/libkwineffects/data/glplatform/lima-mali400-desktop-3.0
+@@ -6,7 +6,7 @@ ShadingLanguageVersion=1.30
+ 
+ [Settings]
+ LooseBinding=true
+-GLSL=false
++GLSL=true
+ TextureNPOT=true
+ Mesa=true
+ Lima=true
+diff --git a/src/libkwineffects/kwinglplatform.cpp 
b/src/libkwineffects/kwinglplatform.cpp
+index 82554ca755b..aa0f5b105a5 100644
+--- a/src/libkwineffects/kwinglplatform.cpp
 b/src/libkwineffects/kwinglplatform.cpp
+@@ -1138,8 +1138,7 @@ void GLPlatform::detect(OpenGLPlatformInterface 
platformInterface)
+ 
+ if (isLima()) {
+ m_recommendedCompositor = OpenGLCompositing;
+-// GLSL works but causes dramatic FPS drop on this GPU
+-m_supportsGLSL = false;
++m_supportsGLSL = true;
+ }
+ 
+ if (isVideoCore4()) {
+-- 
+GitLab
+
diff -Nru kwin-5.27.2/debian/patches/series kwin-5.27.2/debian/patches/series
--- kwin-5.27.2/debian/patches/series   2022-10-02 18:15:15.0 +0200
+++ kwin-5.27.2/debian/patches/series   2023-05-05 14:16:46.0 +0200
@@ -1 +1,2 @@
 uninitialized-yuvformat.patch
+fix-for-Lima-disabling-GLSL.patch

Bug#1035592: openbox: Openbox does not present a desktop

[bud]

Package: openbox
Version: 3.6.1-10
Severity: grave
Justification: renders package unusable
X-Debbugs-Cc: budheal...@gmail.com

Dear Maintainer,

   * What led up to the situation?
Install release candidate 2 and select openbox, then login.
   * What exactly did you do (or not do) that was effective (or
 ineffective)?
The login appears stalled. Openbox worked in earlier weekly builds. Perhaps 
using sddm here makes a difference.
   * What was the outcome of this action?
I logged in with ssh and killed the sddm-helper process. Killing the first 
openbox process had no effect.
   * What outcome did you expect instead?
Either openbox should start or there should be a way to return to the login 
dialog.

-- System Information:
Debian Release: 12.0
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: amd64 (x86_64)

Kernel: Linux 6.1.0-7-amd64 (SMP w/20 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 openbox depends on:
ii  libc6 2.36-9
ii  libglib2.0-0  2.74.6-2
ii  libice6   2:1.0.10-1
ii  libobrender32v5   3.6.1-10
ii  libobt2v5 3.6.1-10
ii  libsm62:1.2.3-1
ii  libstartup-notification0  0.12-6+b1
ii  libx11-6  2:1.8.4-2
ii  libxau6   1:1.0.9-1
ii  libxcursor1   1:1.2.1-1
ii  libxext6  2:1.3.4-1+b1
ii  libxi62:1.8-1+b1
ii  libxinerama1  2:1.1.4-3
ii  libxrandr22:1.5.2-2+b1
ii  python3   3.11.2-1+b1

Versions of packages openbox recommends:
ii  obconf  1:2.0.4+git20150213-2+b1
ii  scrot   1.8.1-1

Versions of packages openbox suggests:
ii  fonts-dejavu   2.37-6
ii  libxml2-dev2.9.14+dfsg-1.2
pn  openbox-gnome-session  
pn  openbox-kde-session
pn  tint2  

-- no debconf information

Bug#1035588: installation-reports: Installation of GNOME desktop fails (in openQA)

[Roland Clobus]

On 05/05/2023 22:26, Roland Clobus wrote:

Sorry, I mixed up KDE and GNOME reports...

Fixing the URLs to point to the GNOME issue


Boot method: CD
Image version: daily netinst 20230505_1104 from
https://get.debian.org/images/daily-builds/daily/current/amd64/iso-cd/
Date: 2023-05-05T15:57:23

Machine: qemu running on AMD64 server osuosl3.debian.net

See: https://openqa.debian.net/tests/144876

Partitions:

https://openqa.debian.net/tests/144876/logfile?filename=complete_install-gdisk.txt 


--
GPT fdisk (gdisk) version 1.0.9

Partition table scan:
  MBR: MBR only
  BSD: not present
  APM: not present
  GPT: not present


***
Found invalid GPT and valid MBR; converting MBR to GPT format
in memory.
***

Disk /dev/vda: 20971520 sectors, 10.0 GiB
Sector size (logical/physical): 512/512 bytes
Disk identifier (GUID): 2E91D03B-B669-42AF-9A53-D4DD7C273F31
Partition table holds up to 128 entries
Main partition table begins at sector 2 and ends at sector 33
First usable sector is 34, last usable sector is 20971486
Partitions will be aligned on 2048-sector boundaries
Total free space is 6077 sectors (3.0 MiB)

Number  Start (sector)End (sector)  Size   Code  Name
   1204818970623   9.0 GiB 8300  Linux filesystem
   51897267220969471   975.0 MiB   8200  Linux swap
--


Base System Installation Checklist:
[O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it

Initial boot:   [O]
Detect network card:[O]
Configure network:  [O]
Detect media:   [O]
Load installer modules: [O]
Clock/timezone setup:   [O]
User/password setup:[O]
Detect hard drives: [O]
Partition hard drives:  [O]
Install base system:[O]
Install tasks:  [O]
Install boot loader:[O]
Overall install:[E]


Comments/Problems:

After the reboot the GNOME login screen is not shown, instead the screen 
shows 'Oh no! Something has gone wrong'.


This is a suspicious parts from `journalctl -b`:
https://openqa.debian.net/tests/144876/logfile?filename=_graphical_wait_login-journal.txt

May 05 13:59:35 debian org.gnome.Shell.desktop[610]: LLVM ERROR: 64-bit 
code requested on a subtarget that doesn't support it!
May 05 13:59:35 debian org.gnome.Shell.desktop[610]: == Stack trace for 
context 0x5560643b27d0 ==


I've used the same ISO file on my Intel-based computer, that worked fine.

With kind regards,
Roland Clobus


OpenPGP_signature
Description: OpenPGP digital signature

Bug#1035591: coreutils: pr: -n width explodes sometimes?

[наб]

Package: coreutils
Version: 8.32-4+b1
Version: 9.1-1
Severity: normal

Dear Maintainer,

-- >8 --
$ pr -w22 -2 -n american.med+.mwl | head


2023-05-05 18:58 american.med+.mwl Page 1


1   a/57   Ab
2   A'58   ab
3   AA59   ab
4   Aa60   ab
5   Aa61   ab
$ pr -w22 -3 -n american.med+.mwl | head


2023-05-05 18:58 american.med+.mwl Page 1


1   a 57   A113   a
2   A 58   a114   a
3   A 59   a115   a
4   A 60   a116   a
5   A 61   a117   a
$ pr -w22 -4 -n american.med+.mwl | head


2023-05-05 18:58 american.med+.mwl Page 1


1   a57  A113 a169 a
2   A58  a114 a170 a
3   A59  a115 a171 a
4   A60  a116 a172 a
5   A61  a117 a173 a
$ pr -w22 -5 -n american.med+.mwl | head


2023-05-05 18:58 american.med+.mwl Page 1


1   a57 A113a169a225a
2   A58 a114a170a226a
3   A59 a115a171a227a
4   A60 a116a172a228a
5   A61 a117a173a229a
-- >8 --
(same with explicit -n5).

I don't think I need to tell you this is wrong,
and in a truly amazing fashion at that.

наб

-- System Information:
Debian Release: 12.0
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: x32 (x86_64)
Foreign Architectures: amd64, i386

Kernel: Linux 6.1.0-2-amd64 (SMP w/2 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 coreutils depends on:
ii  libacl1  2.3.1-3
ii  libattr1 1:2.5.1-4
ii  libc62.36-9
ii  libgmp10 2:6.2.1+dfsg1-1.1
ii  libselinux1  3.4-1+b5

coreutils recommends no packages.

coreutils suggests no packages.

-- no debconf information


signature.asc
Description: PGP signature

Bug#1035590: unblock: chromium/113.0.5672.63-2

[Andres Salomon]

Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
X-Debbugs-Cc: chrom...@packages.debian.org
Control: affects -1 + src:chromium

It's that magical time of the year again! The birds are chirping, the 
sun is shining, and the chromium CVEs are just emerging, famished, from 
their burrows after a long winter.


Please unblock package chromium so that it migrates to bookworm after 5 
days. The upload to unstable fixes another set of 10 CVEs.


Thanks,
Andres

Bug#1035381: osinfo-db: does not autodetect OS of Debian Installer RC ISOs and live ISOs

[Roland Clobus]

Hello Emanuele,


The version 20230308 in sid works fine for me for detecting the installer RC >> 
ISO images:

That is not the case for me. Which ISO are you using exactly? The one > not 
being recognized here is debian-bookworm-DI-rc2-amd64-netinst.iso.

Ah... I see my error. I was using the daily images from [1].
With the attached patch, the RC version from [2] (I've added only the 
amd64,iso-cd version) will be identified as Debian 12 (i.e. bookworm).


See also my mail to debian-boot [3].

With kind regards,
Roland

[1] https://get.debian.org/images/daily-builds/daily
[2] https://get.debian.org/images/bookworm_di_rc2/
[3] https://lists.debian.org/debian-boot/2023/05/msg00091.html
--- a/data/os/debian.org/debian-12.xml.in
+++ b/data/os/debian.org/debian-12.xml.in
@@ -39,7 +39,7 @@
 
   
   
-Debian 12.\d+.\d+ amd64 n
+Debian (12.\d+.\d+|bookworm-DI-rc\d+) amd64 n
   
   install.amd/vmlinuz
   install.amd/initrd.gz


OpenPGP_signature
Description: OpenPGP digital signature

Bug#1035588: installation-reports: Installation of GNOME desktop fails (in openQA)

[Roland Clobus]

Package: installation-reports
Severity: normal
User: debian...@lists.debian.org
X-Debbugs-Cc: p...@hands.com

Boot method: CD
Image version: daily netinst 20230505_1104 from
https://get.debian.org/images/daily-builds/daily/current/amd64/iso-cd/
Date: 2023-05-05T15:57:23

Machine: qemu running on AMD64 server osuosl3.debian.net
See: https://openqa.debian.net/tests/144783
Partitions:

https://openqa.debian.net/tests/144783/logfile?filename=complete_install-
gdisk.txt

--
GPT fdisk (gdisk) version 1.0.9

Partition table scan:
  MBR: MBR only
  BSD: not present
  APM: not present
  GPT: not present


***
Found invalid GPT and valid MBR; converting MBR to GPT format
in memory.
***

Disk /dev/vda: 31457280 sectors, 15.0 GiB
Sector size (logical/physical): 512/512 bytes
Disk identifier (GUID): 71C86CFF-DC9F-4BC4-B99D-DB5CF15F1DB3
Partition table holds up to 128 entries
Main partition table begins at sector 2 and ends at sector 33
First usable sector is 34, last usable sector is 31457246
Partitions will be aligned on 2048-sector boundaries
Total free space is 6077 sectors (3.0 MiB)

Number  Start (sector)End (sector)  Size   Code  Name
   1204829456383   14.0 GiB8300  Linux filesystem
   52945843231455231   975.0 MiB   8200  Linux swap
--

Base System Installation Checklist:
[O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it

Initial boot:   [O]
Detect network card:[O]
Configure network:  [O]
Detect media:   [O]
Load installer modules: [O]
Clock/timezone setup:   [O]
User/password setup:[O]
Detect hard drives: [O]
Partition hard drives:  [O]
Install base system:[O]
Install tasks:  [O]
Install boot loader:[O]
Overall install:[E]

Comments/Problems:

After the reboot the GNOME login screen is not shown, instead the screen stays
black.

Judging from the output of `journalctl -b`, sddm-greeter causes a core dump
https://openqa.debian.net/tests/144783/logfile?filename=_graphical_wait_login-
journal.txt
systemd-coredump[917]: Process 873 (sddm-greeter) of user 113 dumped core.

I've used the same ISO file on my Intel-based hardware, with a similar
invocation of qemu, and there the ISO images worked fine.

With kind regards,
Roland Clobus

PS: The netinst-RC2 image has the same issue


-- Package-specific info:

==
Installer lsb-release:
==
DISTRIB_ID=Debian
DISTRIB_DESCRIPTION="Debian GNU/Linux installer"
DISTRIB_RELEASE="7 (wheezy) - installer build 20130613+deb7u2+b1"
X_INSTALLATION_MEDIUM=netboot

==
Installer hardware-summary:
==
uname -a: Linux silent 3.2.0-4-amd64 #1 SMP Debian 3.2.57-3 x86_64 GNU/Linux
lspci -knn: 00:00.0 Host bridge [0600]: Intel Corporation Haswell DRAM 
Controller [8086:0c00] (rev 06)
lspci -knn: Subsystem: Giga-byte Technology Device [1458:5000]
lspci -knn: 00:02.0 VGA compatible controller [0300]: Intel Corporation Haswell 
Integrated Graphics Controller [8086:0412] (rev 06)
lspci -knn: Subsystem: Giga-byte Technology Device [1458:d000]
lspci -knn: 00:03.0 Audio device [0403]: Intel Corporation Haswell HD Audio 
Controller [8086:0c0c] (rev 06)
lspci -knn: Subsystem: Intel Corporation Device [8086:2010]
lspci -knn: 00:14.0 USB controller [0c03]: Intel Corporation Lynx Point USB 
xHCI Host Controller [8086:8c31] (rev 04)
lspci -knn: Subsystem: Giga-byte Technology Device [1458:5007]
lspci -knn: Kernel driver in use: xhci_hcd
lspci -knn: 00:16.0 Communication controller [0780]: Intel Corporation Lynx 
Point MEI Controller #1 [8086:8c3a] (rev 04)
lspci -knn: Subsystem: Giga-byte Technology Device [1458:1c3a]
lspci -knn: 00:16.3 Serial controller [0700]: Intel Corporation Lynx Point KT 
Controller [8086:8c3d] (rev 04)
lspci -knn: Subsystem: Giga-byte Technology Device [1458:1c3a]
lspci -knn: Kernel driver in use: serial
lspci -knn: 00:19.0 Ethernet controller [0200]: Intel Corporation Ethernet 
Connection I217-V [8086:153b] (rev 04)
lspci -knn: Subsystem: Giga-byte Technology Device [1458:e000]
lspci -knn: Kernel driver in use: e1000e
lspci -knn: 00:1a.0 USB controller [0c03]: Intel Corporation Lynx Point USB 
Enhanced Host Controller #2 [8086:8c2d] (rev 04)
lspci -knn: Subsystem: Giga-byte Technology Device [1458:5006]
lspci -knn: Kernel driver in use: ehci_hcd
lspci -knn: 00:1b.0 Audio device [0403]: Intel Corporation Lynx Point High 
Definition Audio Controller [8086:8c20] (rev 04)
lspci -knn: Subsystem: Giga-byte Technology Device [1458:a002]
lspci -knn: 00:1c.0 PCI bridge [0604]: Intel Corporation Lynx Point PCI Express 
Root Port #1 [8086:8c10] (rev d4)
lspci -knn: Kernel driver in use: pcieport
lspci -knn: 00:1c.3 PCI bridge 

Bug#1035587: linux: broken AHCI controller on MIPS Loongson 3 (regression from 5.10.162-1)

[Aurelien Jarno]

Source: linux
Version: 5.10.178-3
Severity: important
X-Debbugs-Cc: d...@debian.org, debian-m...@lists.debian.org, s...@debian.org

Following the point release, the buildd mipsel-osuosl-03.d.o does not
boot anymore, with errors in the AHCI controller:

[   35.912147] ata4.00: exception Emask 0x0 SAct 0x2000 SErr 0x0 action 0x6 
frozen
[   35.919769] ata4.00: failed command: WRITE FPDMA QUEUED
[   35.924968] ata4.00: cmd 61/20:e8:00:f0:e1/00:00:00:00:00/40 tag 29 ncq dma 
16384 out
[   35.924968]  res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 
(timeout)
[   35.940097] ata4.00: status: { DRDY }
[   35.943743] ata4: hard resetting link

While that initially looks like a hardware issue, it appears that
reverting the kernel to 5.10.162-1 (from 5.10.178-3) fixes the issue.
Strangely mipsel.osuosl-05.d.o, which seems to be similar hardware (CPU,
motherboard and SATA drive), does not exhibit the same issue.

You'll find attached the output of /proc/cpuinfo, lspci and the full
boot log.
PMON2000 MIPS Initializing. Standby...

node 0 N Voltage  write :
v ctrl err

node 0 N Voltage  read :
00080760uV 

node 0 P Voltage write :

0xbfe00190  : 5282a9b7b7a7
CPU CLK SEL : 0002
MEM CLK SEL : 0014
HT CLK SEL : 0014
Disable HT0 clock
Change the scale of HT1 clock
Change the scale of LS132 clock

BBGEN start  :
BBGEN config value  :00ff6431
Soft CLK SEL adjust begin
CORE & NODE:
Miku MAGIC Mismtach
04110c85
MEM   :0909017b
fdcoefficient  :0004
HT:
SYS_LOOPC:0012

DDR_LOOPC:0024
NO TLB cache init ...
Jump to 9fc
32 bit PCI space translate to 64 bit HT space

Check HT bus up.
01110020
set LS7A MISC and confbus base address done.
3A HT in soft freq cfg mode...ok
7A HT in soft freq cfg mode...ok

PLL check success.
Wait HT bus up.01110020>
01110020
Set 7A side HT:
Set width
0020
Set Freq
82251060
Set soft config
008a810a
Set Gen3 mode
81237008
Set retry mode
0081
Enable scrambling
0078
set buffer num
0fff
Set CPU side HT:
Set width
0020
Set Freq
82250060
Set soft config
0087c10a
Set GEN3 mode
81237008
Set retry mode
0081
Enable scrambling
0078
Reset Node 0 HT1-lo bus
0040
Wait HT bus down.>
0010

Dereset Node 0 HT1 bus

Wait HT bus up.>
0020

After reconnect, PLL check success.
Checking Node 0 HT1 CRC error.>
Checking Bridge HT CRC error bit.>
LS3A-7A linkup.
Disable ht regs.

Start Init Memory, wait a while..
NODE 0 MEMORY CONFIG BEGIN

Lock Scache
Lock Scache Done.

Probing DDR MC0 SLOT: 
Slot 0: s1 = 0x00114008__c3004000

Slot 1: s1 = 0x__

 T5 s1 = 00114008__c3005f00

 t0 = 0x__

Enable register space of MEMORY

init start
908:000f0f0300e1e1c1
 begin Reset MC 
init start
908:000f0f0300e1e1c1
 begin Reset MC 
init start
908:000f200300e1e1c1
 begin Reset MC 
init start
908:0016050a00e1e1c1
 begin Reset MC 
init start
908:001e0ce1e1c1
 begin Reset MC 
init start
908:001b0a0f00e1e1c1
 begin Reset MC 
init start
908:000f0f0200e1e1c1
 begin Reset MC 
init start
908:00200f1400e1e1c1
 begin Reset MC 
init start
908:0007070c00e1e1c1
 begin Reset MC 
init start
908:000f200300e1e1c1
 begin Reset MC 
init start
908:00200f0200e1e1c1
 begin Reset MC 
init start
908:0016160a00e1e1c1
 begin Reset MC 
init start
908:000c0c1100e1e1c1
 begin Reset MC 
init start
908:000f200200e1e1c1
 begin Reset MC 
init start
908:000c0ce1e1c1
 begin Reset MC 
init start
908:000f0f1300e1e1c1
 begin Reset MC 
init start
908:000c1e0100e1e1c1
 begin Reset MC 
init start
908:000c0ce1e1c1
 begin Reset MC 
init start
908:000a0a0f00e1e1c1
 begin Reset MC 
init start
908:0005050a00e1e1c1
init done
Start Hard Leveling...
Enable register space of MEMORY

start training of tPHY_WR

tPHY_WRLAT training successThe MC param after leveling is:
PHY:
:  0011
0008:  0037
0010:  0103
0018:  
0020:  0001
0028:  
0030:  0052010100040510
0038:  0144
0040:  0008002a
0048:  02041c3801010100
0050:  0008002a
0058:  02041c38
0060:  0008002a
0068:  02041c38
0070:  0008002a
0078:  03041c3800010100
0080:  0008002a
0088:  02041c38
0090:  0008002a
0098:  02041c38
00a0:  0008002a
00a8:  02041c38
00b0:  0008002a
00b8:  03041c3800010100
00c0:  0008002a
00c8:  02041c38
00d0:  0008002a
00d8:  02041c38
00e0:  0001ff000f00
00e8:  0001ff000f00
00f0:  0001ff000f00
00f8:  0001ff000f00
0100:  16002016
0108:  001c1918
0110:  820400880080
0118:  00140003
0120:  
0128:  
0130:  
0138:  
0140:  
0148:  
0150:  

Bug#1035586: coreutils: pr: -n overly narrows the text in the columns? and eats the separator?

[наб]

Package: coreutils
Version: 8.32-4+b1
Version: 9.1-1
Severity: normal

Dear Maintainer,

Given
  % pr -2 -w22 -n american.med+.mwl | cat -A
what do you expect the first bit to be?

We know that (per POSIX) -n is equivalent to -n5;
we know therefore, that each column looks like
  Ndata
since we know we want two columns,
and the minimal separator between them is one blank,
those will be
  Ndata Ndata
  50x   150x
(remember that  is !print),
so given -w22 we can say that
  2*(5+0+x)+1=22
thus
  x=5.5
or, indeed, 5.

So, were we to emulate this, we would expect
  % out/cmd/pr -2 -w22 -n american.med+.mwl  | cat -A
  $
  $
  2023-05-05 22:02 american.med+.mwl Page 1$
  $
  $
  1^Ia/S  57^IAbern$
  2^IA's/I58^Iaberr$
  3^IAAC  59^Iaberr$
  4^IAache60^Iabet/$
  5^IAaliy61^Iabett$
  6^Iaardv62^Iabett$
  7^IAaron63^Iabett$
  8^Iabaci64^Iabett$
  9^Iaback65^Iabeya$
 10^Iabacu66^Iabeya$
 11^Iabaft67^Iabhor$
 12^Iabalo68^Iabhor$
 13^Iaband69^Iabhor$
 14^Iaband70^Iabhor$
 15^Iaband71^Iabhor$
 16^Iabase72^Iabhor$
 17^Iabase73^Iabide$
so what in the world happened to
  % pr -2 -w22 -n american.med+.mwl | cat -A
  $
  $
  2023-05-05 18:58 american.med+.mwl Page 1$
  $
  $
  1^Ia/57   Ab$
  2^IA'58   ab$
  3^IAA59   ab$
  4^IAa60   ab$
  5^IAa61   ab$
  6^Iaa62   ab$
  7^IAa63   ab$
  8^Iab64   ab$
  9^Iab65   ab$
 10^Iab66   ab$
 11^Iab67   ab$
 12^Iab68   ab$
 13^Iab69   ab$
 14^Iab70   ab$
 15^Iab71   ab$
 16^Iab72   ab$
 17^Iab73   ab$
?

Best,
наб

-- System Information:
Debian Release: 12.0
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: x32 (x86_64)
Foreign Architectures: amd64, i386

Kernel: Linux 6.1.0-2-amd64 (SMP w/2 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 coreutils depends on:
ii  libacl1  2.3.1-3
ii  libattr1 1:2.5.1-4
ii  libc62.36-9
ii  libgmp10 2:6.2.1+dfsg1-1.1
ii  libselinux1  3.4-1+b5

coreutils recommends no packages.

coreutils suggests no packages.

-- no debconf information


signature.asc
Description: PGP signature

Bug#1035332: grub-efi-arm64: "error: failed to install/update FDT." after bullseye upgrade

[Steve McIntyre]

On Mon, May 01, 2023 at 12:08:38PM -0700, Vagrant Cascadian wrote:
>On 2023-04-30, Vagrant Cascadian wrote:
>> After updating to the latest point release, these apm mustang systems
>> fail to boot the kernel, all I see is:
>>
>> error: failed to install/update FDT.
>> Loading Linux 5.10.0-22-arm64 ...
>> Loading initial ramdisk ...
>>
>> Press any key to continue...
>
>The workaround was to uninstall shim-signed and re-install grub
>(grub-install /dev/sda ; grub-install /dev/sdb).
>
>Worked for three of three machines so far... I tested re-installing
>shim-signed on one machine and re-installing grub and the problem came
>back.
>
>No idea why this started happening just now, as shim-signed and related
>packages were all installed before the bullseye point release, but did
>not have this problem...

As described in IRC, I can reproduce this on a mustang here. The grub
binary itself is fine, and boots ok when started directly from the
firmware. But put shim in first and things break. I've turned debug up
to see what's happening.

On a working boot, I can see:

...
kern/efi/fdt.c:38: found registered FDT @ 0x43fd2c3000
loader/efi/fdt.c:63: allocating 26028 bytes for fdt
loader/arm64/linux.c:90: Initrd @ 0x43924fc000-0x4393fff69a
loader/efi/fdt.c:98: Installed/updated FDT configuration table @ 0x43f8b7
...

On a failing boot:
...
kern/efi/fdt.c:38: found registered FDT @ 0x43fd2c4000
loader/efi/fdt.c:63: allocating 26028 bytes for fdt
error: failed to install/update FDT.
...

Digging further...

-- 
Steve McIntyre, Cambridge, UK.st...@einval.com
  Armed with "Valor": "Centurion" represents quality of Discipline,
  Honor, Integrity and Loyalty. Now you don't have to be a Caesar to
  concord the digital world while feeling safe and proud.

Bug#1035055: ITP: firmware-imx -- Firmware binary blobs needed on NXP i.MX platforms

[Johannes Schauer Marin Rodrigues]

Hi,

Quoting Manuel Traut (2023-04-28 14:59:50)
> * Package name: firmware-imx
>   Version : 8.19
>   Upstream Contact: NXP
> * URL : https://www.nxp.com/
> * License : LA_OPT_NXP_Software_License_v42
>   Description : Firmware binary blobs needed on NXP i.MX platforms
> 
> i.MX Firmware including firmware for VPU, DDR, EPDC, HDMI, DP
> (Display Port), and SDMA
> 
> To build a working u-boot for i.MX8* at least the DDR train binaries
> from NXP are needed.
> 
> More details are available in this document:
> https://www.nxp.com/docs/en/release-note/IMX_LINUX_RELEASE_NOTES.pdf
> 
> The package shall provide the files from firmware-imx-8.19.bin:

thank you for intending to package this!

Do you also have some packaging done that we could test? We need these blobs to
build working u-boot binaries.

Do you plan to upload this to non-free-firmware?

Thanks!

cheers, josch

signature.asc
Description: signature

Bug#1035585: RM: gip -- RoQA; orphaned; depends on gtk2; low popcon

[Bastian Germann]

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

Please remove gip. Its upstream is dead and the package is orphaned.
It depends on gtk2, has a low popcon and no reverse dependencies.
Alternatives are available.

Bug#1035584: RM: fbxkb -- RoQA; orphaned; depends on gtk2; low popcon

[Bastian Germann]

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

Please remove fbxkb. It is unmaintained upstream and orphaned.
It depends on gtk2, has a low popcon and no reverse dependencies.
Alternatives are available.

Bug#1035583: RM: xnecview -- RoQA; orphaned; depends on gtk2; low popcon

[Bastian Germann]

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

Please remove xnecview. It is unmaintained upstream and orphaned.
It depends on gtk2, has a low popcon and no reverse dependencies.
Alternative xnec2c is available.

Bug#1035582: RM: dlume -- RoQA; orphaned; depends on gtk2; low popcon

[Bastian Germann]

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

Please remove dlume. It is very old software, unmaintained upstream and 
orphaned.
It depends on gtk2, has a low popcon and no reverse dependencies.

Bug#1035580: node-yaml: CVE-2023-2251

[Salvatore Bonaccorso]

Source: node-yaml
Version: 2.1.3-1
Severity: important
Tags: security upstream
X-Debbugs-Cc: car...@debian.org, Debian Security Team 

Hi,

The following vulnerability was published for node-yaml.

CVE-2023-2251[0]:
| Uncaught Exception in GitHub repository eemeli/yaml.


If you fix the vulnerability please also make sure to include the
CVE (Common Vulnerabilities & Exposures) id in your changelog entry.

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2023-2251
https://www.cve.org/CVERecord?id=CVE-2023-2251
[1] https://huntr.dev/bounties/4b494e99-5a3e-40d9-8678-277f3060e96c
[2] 
https://www.github.com/eemeli/yaml/commit/984f5781ffd807e58cad3b5c8da1f940dab75fba

Regards,
Salvatore

Bug#1035578: fails to write image with TypeError: write() argument must be str, not bytes

[Antoine Beaupre]

Package: python3-matplotlib
Version: 3.6.3-1+b1
Severity: important

I have this tiny script which generates a silly graph of cryptographic
primitives here:

https://gitlab.com/anarcat/crypto-bench/-/blob/master/benchdiceware.py

The details are rather irrelevant here, but it eventually does this:

plt.savefig(args.output,
format=args.output.name[-3:])

... which is basically:

plt.savefig("foo.png", "png")

This used to work fine in Python 2. Now that we switched to Python 3,
this explodes with:

anarcat@angela:crypto-bench$ ./benchpasswords.py -o benchdiceware.png 
Traceback (most recent call last):
  File "/home/anarcat/src/crypto-bench/./benchpasswords.py", line 102, in 

render_graph(args.output)
  File "/home/anarcat/src/crypto-bench/./benchpasswords.py", line 90, in 
render_graph
plt.savefig(args.output,
  File "/usr/lib/python3/dist-packages/matplotlib/pyplot.py", line 959, in 
savefig
res = fig.savefig(*args, **kwargs)
  
  File "/usr/lib/python3/dist-packages/matplotlib/figure.py", line 3285, in 
savefig
self.canvas.print_figure(fname, **kwargs)
  File "/usr/lib/python3/dist-packages/matplotlib/backend_bases.py", line 2338, 
in print_figure
result = print_method(
 ^
  File "/usr/lib/python3/dist-packages/matplotlib/backend_bases.py", line 2204, 
in 
print_method = functools.wraps(meth)(lambda *args, **kwargs: meth(
 ^
  File "/usr/lib/python3/dist-packages/matplotlib/_api/deprecation.py", line 
410, in wrapper
return func(*inner_args, **inner_kwargs)
   ^
  File "/usr/lib/python3/dist-packages/matplotlib/backends/backend_agg.py", 
line 517, in print_png
self._print_pil(filename_or_obj, "png", pil_kwargs, metadata)
  File "/usr/lib/python3/dist-packages/matplotlib/backends/backend_agg.py", 
line 464, in _print_pil
mpl.image.imsave(
  File "/usr/lib/python3/dist-packages/matplotlib/image.py", line 1667, in 
imsave
image.save(fname, **pil_kwargs)
  File "/usr/lib/python3/dist-packages/PIL/Image.py", line 2431, in save
save_handler(self, fp, filename)
  File "/usr/lib/python3/dist-packages/PIL/PngImagePlugin.py", line 1307, in 
_save
fp.write(_MAGIC)
TypeError: write() argument must be str, not bytes
anarcat@angela:crypto-bench[1]$ 

It looks like matplotlib is calling PIL wrong. Or PIL is wrong itself,
I'm not sure where to lay the blame here...

a.

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

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

Versions of packages python3-matplotlib depends on:
ii  libc6   2.36-9
ii  libfreetype62.12.1+dfsg-5
ii  libgcc-s1   12.2.0-14
ii  libjs-jquery3.6.1+dfsg+~3.5.14-1
ii  libjs-jquery-ui 1.13.2+dfsg-1
ii  libqhull-r8.0   2020.2-5
ii  libstdc++6  12.2.0-14
ii  python-matplotlib-data  3.6.3-1
ii  python3 3.11.2-1+b1
ii  python3-contourpy   1.0.7-1+b1
ii  python3-cycler  0.11.0-1
ii  python3-dateutil2.8.2-2
ii  python3-fonttools   4.38.0-1+b1
ii  python3-kiwisolver  1.4.4-1+b1
ii  python3-numpy [python3-numpy-abi9]  1:1.24.2-1
ii  python3-packaging   23.0-1
ii  python3-pil 9.4.0-1.1+b1
ii  python3-pil.imagetk 9.4.0-1.1+b1
ii  python3-pyparsing   3.0.9-1
ii  python3-six 1.16.0-4

Versions of packages python3-matplotlib recommends:
ii  python3-tk  3.10.8-1

Versions of packages python3-matplotlib suggests:
ii  cm-super-minimal 0.3.4-17
pn  dvipng   
ii  ffmpeg   7:5.1.2-3
pn  fonts-staypuft   
ii  ghostscript  10.0.0~dfsg-11
ii  gir1.2-gtk-3.0   3.24.37-2
ii  inkscape 1.2.2-2+b1
ii  ipython3 8.5.0-4
ii  librsvg2-common  2.54.5+dfsg-1
pn  python3-cairocffi
ii  python3-gi   3.42.2-3+b1
ii  python3-gi-cairo 3.42.2-3+b1
pn  python3-gobject  
ii  python3-pyqt55.15.9+dfsg-1
ii  python3-scipy1.10.1-2
ii  python3-sip  4.19.25+dfsg-5+b1
ii  python3-tornado  6.2.0-3
pn  texlive-extra-utils  
ii  texlive-latex-extra  2022.20230122-3

-- no debconf information

Bug#1035579: RM: cellwriter -- RoQA; orphaned; depends on gtk2; low popcon

[Bastian Germann]

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

Please remove cellwriter. It is very old software, unmaintained upstream and 
orphaned.
It depends on gtk2, has a low popcon and no reverse dependencies.

Bug#1035573: unblock: telegram-desktop/4.6.5+ds-2, libtgowt/0~git20230105.5098730+dfsg-2

[Nicholas Guriev]

Control: unblock 1032927 by -1
Control: block 1032953 by -1

On Fri, 05 May 2023 19:37:56 +0300 Nicholas Guriev  wrote:
> The updates fix an important issue with group calls and live streams. See
> detailed description in Bug#1032927, Bug#1035518, and in an upstream bug
> report.

So sorry, I mixed up the bug number in my previous message. Instead wrong
Bug#1032927, correct number was Bug#1032953. The attached debdiff was OK.

You can also look at the diffs in Git.

https://salsa.debian.org/debian/telegram-desktop/-/compare/09b363ed5a4fcd8ecc3282b9bfede5fbb83f97ef...cb0a75574b4fe980f8b3c0bdfd6b13aa9a0f3b8e
https://salsa.debian.org/debian/libtgowt/-/compare/83e0c19744cd49b02f6975346f9097fec10299cd...0b62e0fba1c7d81c2a70c18f8085b4714b44667d


signature.asc
Description: This is a digitally signed message part.

Bug#967754: spacefm: depends on deprecated GTK 2

[Bastian Germann]

Please drop the gtk2 dependencies and make spacefm a transitional package for 
spacefm-gtk3.

Bug#1035577: New upstream Dovecot stable version 2.3.20

[Robert L Mathews]

Package: dovecot-core
Version: 1:2.3.19.1+dfsg1-2.1
Severity: wishlist

The current upstream version of dovecot is 2.3.20, which fixes several 
problems in 2.3.19 while adding almost no features. It's been remarkably 
problem-free on the Dovecot mailing list, compared to 2.3.19 that had 
numerous problem reports.


If possible, it would be great to see 2.3.20 in Debian rather than 2.3.19.

--
Robert L Mathews

Bug#1034650: debian-installer: bookworm d-i rc1: apt-get clean breaks bash-completion

[Askar Safin]

On Fri, May 5, 2023 at 8:53 PM Tianon Gravi  wrote:
> To be clear, there was nothing _certain_ in my response, merely that
> my first impression matched Cyril's for the very similar issue on d-i.
Okay, sorry for misunderstanding.

-- 
Askar Safin

Bug#1035576: plasma-settings: OpenDesktop in SystemSettings->OnlineAccounts doesn't work!

[Arthur Maurer]

Package: plasma-settings
Version: systemsettings
Severity: normal
X-Debbugs-Cc: arthurmau...@posteo.de

Dear Maintainer,

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

   * Tried to open the OpenDesktop-Button under Online-Accounts in
SystemSettings
   * Just tried to click on it's button (of OpenDesktop).
   * ...I'd think it's self-explaining...
   * I expected to open some Login+Password window as it worked instantly and
w/o problems as it worked for own-/Nextcloud and Google-accounts.


-- System Information:
Debian Release: 12.0
  APT prefers testing-security
  APT policy: (500, 'testing-security'), (500, 'testing')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 6.1.0-7-amd64 (SMP w/12 CPU threads; PREEMPT)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=locale: Cannot set 
LC_CTYPE to default locale: No such file or directory
locale: Cannot set LC_MESSAGES to default locale: No such file or directory
locale: Cannot set LC_ALL to default locale: No such file or directory
ANSI_X3.4-1968) (ignored: LC_ALL set to en_US.UTF-8), LANGUAGE=en_US
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages plasma-settings depends on:
ii  kpackagetool5   5.103.0-1
ii  libc6   2.36-9
ii  libglib2.0-02.74.6-2
ii  libkf5configcore5   5.103.0-1
ii  libkf5coreaddons5   5.103.0-1
ii  libkf5dbusaddons5   5.103.0-1
ii  libkf5i18n5 5.103.0-1
ii  libkf5modemmanagerqt6   5.103.0-1
ii  libkf5networkmanagerqt6 5.103.0-1
ii  libkf5package5  5.103.0-1
ii  libkf5quickaddons5  5.103.0-1
ii  libkf5solid55.103.0-1
ii  libqt5core5a5.15.8+dfsg-7
ii  libqt5dbus5 5.15.8+dfsg-7
ii  libqt5gui5  5.15.8+dfsg-7
ii  libqt5qml5  5.15.8+dfsg-3
ii  libqt5widgets5  5.15.8+dfsg-7
ii  libqt5xml5  5.15.8+dfsg-7
ii  libstdc++6  12.2.0-14
ii  plasma-framework5.103.0-1
ii  qml-module-org-kde-kcm  5.103.0-1
ii  qml-module-org-kde-kirigami-addons-labs-mobileform  0.7.0-2
ii  qml-module-org-kde-kirigami25.103.0-1

plasma-settings recommends no packages.

Versions of packages plasma-settings suggests:
ii  kaccounts-integration  4:22.12.3-1
ii  kaccounts-providers4:22.12.3-1

Bug#1034650: debian-installer: bookworm d-i rc1: apt-get clean breaks bash-completion

[Askar Safin]

David Kalnischkies:
> The completion script explicitly disables the recreation on-the-fly as
> creating the files takes a while robbing users for many seconds of their
> interactivity. So, we can't just "fix" the completion script as that has
> a(nother?) set of users complain as well.

Deleting /var/cache/apt/*.bin and then running "apt-cache gencaches"
takes 0.22 on my (loaded) system.

I propose regenerate caches in completion scripts only if they are not
present. This will change situation from "not working at all" (in
default d-i install and in official docker image) to "working slowly".
Also, "working slowly" is just minor annoyance. But "not working"
means that the user doesn't know how to fix. Yes, merely calling
"apt-get install apt" will regenerate caches (in d-i case, not in
docker case), but how the user should know this? The solution is not
discoverable

-- 
Askar Safin

Bug#1035569: installation-reports: failed to detect Realtek RTL8852BE WiFi 6 802.11ax PCIe adapter

[Cyril Brulebois]

Control: reassign -1 src:linux
Control: retitle -1 please enable CONFIG_RTW89_8852BE
Control: affects -1 installation-reports

Hi,

Fabian Greffrath  (2023-05-05):
> Today I attempted to install Debian bookworm on a brand new Lenovo
> IdeaPad 5 14IAL7 with an i5-1235U CPU, 16GB RAM and 512GB SDD.
> 
> The installation failed to proceed at the network card detection
> stage. Apparently, the machine has a Realtek RTL8852BE adapter, which
> *should* be supported by recent kernels.

As mentioned in follow-ups (by Diederik and me), that module only appeared
in v6.2-rc1 (v6.2-rc1~99^2~345^2~3), so no it's not available in Bookworm.

Reassigning to the kernel accordingly, so that it gets enabled in some
future upload.


Cheers,
-- 
Cyril Brulebois (k...@debian.org)
D-I release manager -- Release team member -- Freelance Consultant


signature.asc
Description: PGP signature

Bug#1034650: debian-installer: bookworm d-i rc1: apt-get clean breaks bash-completion

[Tianon Gravi]

On Fri, 5 May 2023 at 10:06, Askar Safin  wrote:
> Current apt behavior also breaks official debian docker images, I
> reported this here:
> https://github.com/debuerreotype/debuerreotype/pull/153 . The images'
> developer said this is apt completion scripts' problem

To be clear, there was nothing _certain_ in my response, merely that
my first impression matched Cyril's for the very similar issue on d-i.

I'd be very happy to spend some time with APT folks to figure out a
better configuration for the Docker images (both specifically on this
issue and in general!), especially as there seems to be some tension
around our current configuration that was unintentional and I'm sorry
for. 

(Having APT maintainers say "you should do X to accomplish what you're
looking for" is a much more defensible change than anything I could
possibly make up alone! )

♥,
- Tianon
  4096R / B42F 6819 007F 00F8 8E36  4FD4 036A 9C25 BF35 7DD4

Bug#1035569: installation-reports: failed to detect Realtek RTL8852BE WiFi 6 802.11ax PCIe adapter

[Cyril Brulebois]

fab...@greffrath.com  (2023-05-05):
> When will be the earliest chance for a D-I image with kernel >= 6.2?

One prerequisite is having said kernel in unstable/testing.


Cheers,
-- 
Cyril Brulebois (k...@debian.org)
D-I release manager -- Release team member -- Freelance Consultant


signature.asc
Description: PGP signature

Bug#1035569: installation-reports: failed to detect Realtek RTL8852BE WiFi 6 802.11ax PCIe adapter

[fabian]

Am 05.05.2023 18:23, schrieb Cyril Brulebois:

Right, initial support seems to have been merged in time for v6.2-rc1
only.


Oh, no!

When will be the earliest chance for a D-I image with kernel >= 6.2?

Cheers,

 - Fabian

Bug#1034650: debian-installer: bookworm d-i rc1: apt-get clean breaks bash-completion

[Askar Safin]

Current apt behavior also breaks official debian docker images, I
reported this here:
https://github.com/debuerreotype/debuerreotype/pull/153 . The images'
developer said this is apt completion scripts' problem

-- 
Askar Safin

Bug#1034428: unblock: vmdb2/0.27-1

[Cyril Brulebois]

Hi,

Gunnar Wolf  (2023-04-14):
> vmdb2 is a leaf package. The code changes are quite minor. While there
> are several alternatives to vmdb2 in Debian, switching from one image
> generating system to another might be quite heavy for the users.

Spotted by Helmut (cc-ed): that's not true (in either stable or unstable),
since autopkgtest depends on it… and it seems that update would break it.

I'll let Helmut expand, and possibly formulate a plan.


Cheers,
-- 
Cyril Brulebois (k...@debian.org)
D-I release manager -- Release team member -- Freelance Consultant


signature.asc
Description: PGP signature

Bug#1035575: RM: ams.lv2 -- RoQA; unmaintained; reverse dependency of lvtk

[Bastian Germann]

Source: ams.lv2
Severity: important
Version: 1.2.2-2
Control: block 107 by -1

Please consider removing ams.lv2 (reassign to ftp.debian.org.
I do not think it is justified to keep it in the archive any longer.
This will help with lvtk removal.

Bug#1035574: ams.lv2: FTBFS because of 'U' mode

[Bastian Germann]

Source: ams.lv2
Severity: serious
Version: 1.2.2-2

The build faails with:

Traceback (most recent call last):
  File "/home/bage/ams.lv2-1.2.2/waflib/Scripting.py", line 141, in 
waf_entry_point
set_main_module(wscript)
  File "/home/bage/ams.lv2-1.2.2/waflib/Scripting.py", line 191, in 
set_main_module
Context.g_module = Context.load_module(file_path)
   ^^
  File "/home/bage/ams.lv2-1.2.2/waflib/Context.py", line 665, in load_module
code = Utils.readf(path, m='rU', encoding=encoding)
   
  File "/home/bage/ams.lv2-1.2.2/waflib/Utils.py", line 231, in readf
with open(fname, m) as f:
 ^^
ValueError: invalid mode: 'rUb'

Bug#1035573: unblock: telegram-desktop/4.6.5+ds-2, libtgowt/0~git20230105.5098730+dfsg-2

[Nicholas Guriev]

Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
Control: block 1032927 by -1
Control: block 1035518 by -1

Please unblock package telegram-desktop as well as libtgowt, an ancillary VoIP
library for Telegram.

[ Reason ]
The updates fix an important issue with group calls and live streams. See
detailed description in Bug#1032927, Bug#1035518, and in an upstream bug
report.

[ Impact ]
The features do not work without updating libSRTP from the libsrtp2-1 package.

[ Tests ]
A manual test. See the test case in Bug#1035518.

[ Risks ]
Almost none. Telegram Desktop is leaf package, libtgowt has only one 
dependant.

[ Checklist ]
  [x] all changes are documented in the d/changelog
  [x] I reviewed all changes and I approve them
  [x] attach debdiff against the packages in testing

[ Other info ]
The libtgowt package carries a static library and needs to be build before
telegram-desktop, or the update will not have effect.

unblock telegram-desktop/4.6.5+ds-2
unblock libtgowt/0~git20230105.5098730+dfsg-2
diffstat for telegram-desktop-4.6.5+ds telegram-desktop-4.6.5+ds

 changelog|9 
 patches/Always-use-std-to_string-to-serialize-ints.patch |  232 +++
 patches/series   |1 
 3 files changed, 242 insertions(+)

diff -Nru telegram-desktop-4.6.5+ds/debian/changelog 
telegram-desktop-4.6.5+ds/debian/changelog
--- telegram-desktop-4.6.5+ds/debian/changelog  2023-02-27 17:58:07.0 
+0300
+++ telegram-desktop-4.6.5+ds/debian/changelog  2023-05-05 12:01:43.0 
+0300
@@ -1,3 +1,12 @@
+telegram-desktop (4.6.5+ds-2) unstable; urgency=medium
+
+  * Rebuild against libtgowt-dev (>= 0~git20230105.5098730+dfsg-2). This
+closes: #1032953, #1035518.
+  * New Always-use-std-to_string-to-serialize-ints.patch fixes an assert
+violation in video chats (also known as group calls).
+
+ -- Nicholas Guriev   Fri, 05 May 2023 12:01:43 +0300
+
 telegram-desktop (4.6.5+ds-1) unstable; urgency=medium
 
   * New upstream release.
diff -Nru 
telegram-desktop-4.6.5+ds/debian/patches/Always-use-std-to_string-to-serialize-ints.patch
 
telegram-desktop-4.6.5+ds/debian/patches/Always-use-std-to_string-to-serialize-ints.patch
--- 
telegram-desktop-4.6.5+ds/debian/patches/Always-use-std-to_string-to-serialize-ints.patch
   1970-01-01 03:00:00.0 +0300
+++ 
telegram-desktop-4.6.5+ds/debian/patches/Always-use-std-to_string-to-serialize-ints.patch
   2023-05-04 12:44:16.0 +0300
@@ -0,0 +1,232 @@
+Description: Always use std::to_string to serialize ints
+Origin: 
https://github.com/TelegramMessenger/tgcalls/commit/fecf542a74b0eb2c15ec7820d16653c57f4db27e
+
https://github.com/TelegramMessenger/tgcalls/commit/012f7a75ba7e20e1790203d02aedf573e3551d2f
+Author: John Preston 
+Acked-By: Nicholas Guriev 
+Last-Update: Thu, 04 May 2023 12:44:16 +0300
+
+--- a/Telegram/ThirdParty/tgcalls/tgcalls/group/GroupInstanceCustomImpl.cpp
 b/Telegram/ThirdParty/tgcalls/tgcalls/group/GroupInstanceCustomImpl.cpp
+@@ -102,15 +102,11 @@ static int stringToInt(std::string const ) {
+ }
+ 
+ static std::string intToString(int value) {
+-std::ostringstream stringStream;
+-stringStream << value;
+-return stringStream.str();
++return std::to_string(value);
+ }
+ 
+ static std::string uint32ToString(uint32_t value) {
+-std::ostringstream stringStream;
+-stringStream << value;
+-return stringStream.str();
++return std::to_string(value);
+ }
+ 
+ static uint32_t stringToUInt32(std::string const ) {
+@@ -129,6 +125,7 @@ static uint16_t stringToUInt16(std::string const ) {
+ 
+ static std::string formatTimestampMillis(int64_t timestamp) {
+ std::ostringstream stringStream;
++stringStream.imbue(std::locale::classic());
+ stringStream << std::fixed << std::setprecision(3) << (double)timestamp / 
1000.0;
+ return stringStream.str();
+ }
+--- a/Telegram/ThirdParty/tgcalls/tgcalls/v2/ContentNegotiation.cpp
 b/Telegram/ThirdParty/tgcalls/tgcalls/v2/ContentNegotiation.cpp
+@@ -187,11 +187,7 @@ cricket::ContentInfo 
createInactiveContentInfo(std::string const ) {
+ }
+ 
+ std::string contentIdBySsrc(uint32_t ssrc) {
+-std::ostringstream contentIdString;
+-
+-contentIdString << ssrc;
+-
+-return contentIdString.str();
++return std::to_string(ssrc);
+ }
+ 
+ }
+@@ -639,11 +635,10 @@ void 
ContentNegotiationContext::setAnswer(std::unique_ptr 
ContentNegotiationContext::coordinatedState() const {
+--- a/Telegram/ThirdParty/tgcalls/tgcalls/v2/InstanceV2Impl.cpp
 b/Telegram/ThirdParty/tgcalls/tgcalls/v2/InstanceV2Impl.cpp
+@@ -136,13 +136,12 @@ public:
+ audioOptions.noise_suppression = true;
+ }
+ 
+-std::ostringstream contentId;
+-contentId << _ssrc;
++const auto contentId = std::to_string(_ssrc);
+ 
+ std::vector streamIds;
+-

Bug#1035572: geany crashes often when clicking to switch focus

[Arthur de Jong]

Package: geany
Version: 1.38-1+b1
Severity: important

Geany crashes for me on a regular basis. After some experimenting I've
found a way to reproduce this:

- start geany
- from a new terminal open a not-yet-existing file:
geany /tmp/some-file.txt
- click a bit between geany and the terminal window

I think I've seen this also with files that do exist but the above
triggers the crash for me after a couple of clicks.

This is running under Gnome desktop with reasonably default settings.

Attached is a gdb backtrace.

Thanks

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

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

Versions of packages geany depends on:
ii  geany-common 1.38-1
ii  libatk1.0-0  2.46.0-5
ii  libc62.36-9
ii  libcairo21.16.0-7
ii  libgcc-s112.2.0-14
ii  libgdk-pixbuf-2.0-0  2.42.10+dfsg-1+b1
ii  libglib2.0-0 2.74.6-2
ii  libgtk-3-0   3.24.37-2
ii  libpango-1.0-0   1.50.12+ds-1
ii  libpangocairo-1.0-0  1.50.12+ds-1
ii  libstdc++6   12.2.0-14

Versions of packages geany recommends:
ii  sensible-utils  0.0.17+nmu1

Versions of packages geany suggests:
pn  doc-base  
pn  libvte9   

-- no debconf information

-- 
-- arthur - adej...@debian.org - https://people.debian.org/~adejong --

$ gdb geany
GNU gdb (Debian 13.1-2) 13.1
Copyright (C) 2023 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later 
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.
Type "show copying" and "show warranty" for details.
This GDB was configured as "x86_64-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
.
Find the GDB manual and other documentation resources online at:
.

For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from geany...

This GDB supports auto-downloading debuginfo from the following URLs:
  
Enable debuginfod for this session? (y or [n]) y
Debuginfod has been enabled.
To make this setting permanent, add 'set debuginfod enabled on' to .gdbinit.
Reading symbols from 
/local/arthur/.cache/debuginfod_client/30eed5a4b099db1e2e8e0382edabca21dc748da0/debuginfo...
  
(gdb) r
Starting program: /usr/bin/geany 
Downloading separate debug info for system-supplied DSO at 0x77fc9000
[Thread debugging using libthread_db enabled]   
   
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[New Thread 0x72fbe6c0 (LWP 15639)] 
   
[New Thread 0x727bd6c0 (LWP 15640)]
[New Thread 0x71e516c0 (LWP 15641)] 
   
[Thread 0x71e516c0 (LWP 15641) exited]
[New Thread 0x71e516c0 (LWP 15642)]
[New Thread 0x70fba6c0 (LWP 15643)]
[Thread 0x71e516c0 (LWP 15642) exited]
[Thread 0x70fba6c0 (LWP 15643) exited]  
   
[New Thread 0x70fba6c0 (LWP 15644)] 
   
[New Thread 0x71e516c0 (LWP 15645)]
[New Thread 0x7fffe3fff6c0 (LWP 15647)]
[Thread 0x71e516c0 (LWP 15645) exited]  
   
[Thread 0x70fba6c0 (LWP 15644) exited]
[New Thread 0x71e516c0 (LWP 15661)] 
   
[New Thread 0x70fba6c0 (LWP 15662)]
[New Thread 0x7fff86ff16c0 (LWP 15663)]
[New Thread 0x7fff867f06c0 (LWP 15664)]
[Detaching after vfork from child process 15665]
[New Thread 0x7fff85bff6c0 (LWP 15670)] 
   
[New Thread 0x7fff853fe6c0 (LWP 15671)]
[Thread 0x7fff85bff6c0 (LWP 15670) exited]
[New Thread 0x7fff85bff6c0 (LWP 15672)]
[New Thread 0x7fff84b036c0 (LWP 15673)]
[Thread 0x7fff85bff6c0 (LWP 15672) exited]
[Thread 0x7fff84b036c0 (LWP 15673) exited]
[Thread 0x7fff853fe6c0 (LWP 15671) exited]
[New Thread 0x7fff853fe6c0 (LWP 15674)]
[New Thread 0x7fff84b036c0 (LWP 15675)]
[Thread 0x7fff853fe6c0 

Bug#1035571: RM: see -- RoQA; orphaned; depends on gtk2; low popcon

[Bastian Germann]

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

Please remove see. It is very old software, unmaintained upstream and orphaned. It depends on gtk2, has a very low 
popcon and no reverse dependencies.

Bug#1035569: installation-reports: failed to detect Realtek RTL8852BE WiFi 6 802.11ax PCIe adapter

[Cyril Brulebois]

Diederik de Haas  (2023-05-05):
> Too recent for Bookworm as it appears that it was added in 6.2, while
> Bookworm has 6.1.

Right, initial support seems to have been merged in time for v6.2-rc1
only.


Cheers,
-- 
Cyril Brulebois (k...@debian.org)
D-I release manager -- Release team member -- Freelance Consultant


signature.asc
Description: PGP signature

Bug#1034378: Allow Percentage Formatting in apt

[Emir SARI]

Hello,I'm attaching a patch that enables translations, and fixes an issue that creates extra spaces when the percentage sign is prepended to the "Progress: [100%]" string, due to the fixed layout.Awaiting reviews.Thanks in advance.EmirFrom 091f902682c7cb7b3a4c5340df3fb0bbcd910aaa Mon Sep 17 00:00:00 2001
From: Emir SARI 
Date: Fri, 5 May 2023 18:58:03 +0300
Subject: [PATCH] Apply i18n to percentage display

Languages like Turkish and French (and some other more), use a
custom percentage format, other than the standard 100%. Allowing
i18n to these values, make the apt interface a lot coherent with
the rest of the output, since they mostly appear next to translated
strings.

This commit also fixes the issue of "Progress: [100%]" to have
extra blank characters when the percentage sign is prepended to the
number; e.g. "Progress: [  %1]". Previously, it output [%  1] due
to the absolute placeholder format.
---
 apt-pkg/install-progress.cc | 10 +-
 apt-private/acqprogress.cc  |  9 ++---
 2 files changed, 15 insertions(+), 4 deletions(-)

diff --git a/apt-pkg/install-progress.cc b/apt-pkg/install-progress.cc
index c7f7573..e7c5e55 100644
--- a/apt-pkg/install-progress.cc
+++ b/apt-pkg/install-progress.cc
@@ -56,7 +56,15 @@ bool PackageManager::StatusChanged(std::string /*PackageName*/,
 {
int reporting_steps = _config->FindI("DpkgPM::Reporting-Steps", 1);
percentage = StepsDone/(double)TotalSteps * 100.0;
-   strprintf(progress_str, _("Progress: [%3li%%]"), std::lround(percentage));
+   // Progress percentage, localize according to your locale settings
+   progress_str = strprintf(_("Progress: [%d%%]"), std::lround(percentage));
+
+   if (percentage < 10)
+  progress_str.insert(11, "  ");
+   else if (percentage < 100) {
+  progress_str.insert(11, " ");
+
+   std::printf("%s", progress_str.c_str());
 
if(percentage < (last_reported_progress + reporting_steps))
   return false;
diff --git a/apt-private/acqprogress.cc b/apt-private/acqprogress.cc
index fa7edfc..bbb15ae 100644
--- a/apt-private/acqprogress.cc
+++ b/apt-private/acqprogress.cc
@@ -232,9 +232,11 @@ bool AcqTextStatus::Pulse(pkgAcquire *Owner)
 	 if (I->CurrentItem->TotalSize > 0 && I->CurrentItem->Owner->Complete == false)
 	 {
 	if (Mode == Short)
-	   ioprintf(S, " %.0f%%", (I->CurrentItem->CurrentSize*100.0)/I->CurrentItem->TotalSize);
+   // Progress percentage, localize according to your locale settings
+	   ioprintf(S, _(" %.0f%%"), (I->CurrentItem->CurrentSize*100.0)/I->CurrentItem->TotalSize);
 	else
-	   ioprintf(S, "/%sB %.0f%%", SizeToStr(I->CurrentItem->TotalSize).c_str(),
+   // Progress percentage, localize according to your locale settings
+	   ioprintf(S, _("/%sB %.0f%%"), SizeToStr(I->CurrentItem->TotalSize).c_str(),
 		 (I->CurrentItem->CurrentSize*100.0)/I->CurrentItem->TotalSize);
 	 }
 	 S << "]";
@@ -249,7 +251,8 @@ bool AcqTextStatus::Pulse(pkgAcquire *Owner)
// Put in the percent done
{
   std::stringstream S;
-  ioprintf(S, "%.0f%%", Percent);
+  // Progress percentage, localize according to your locale settings
+  ioprintf(S, _("%.0f%%"), Percent);
   S << Line;
   Line = S.str();
   S.clear();
-- 
2.34.1

Bug#1034836: {Spam?} Bug#1034836: initramfs-tools: After bullseye -> bookworm upgrade boot stuck in the initramfs shell

[Dennis Filder]

X-Debbugs-CC: Pásztor János 

On Wed, May 03, 2023 at 11:20:07PM +0200, Pásztor János wrote:
> I have checked #902943 and the fine print from
> /usr/share/doc/cryptsetup-initramfs/README.initramfs.gz
> Based on that I have made an attempt to replace the UUIDs with
> `traditional` disk device paths.
>
> [...]
>
> However this fails spectacularly, as during the boot process the
> ordering is not stable, sometimes it is sdb1 or sda1 instead of sdc1
> :/

If your device order is not stable during boot you need to use
PARTUUID instead of UUID.  You might argue that you should be able to
use UUID because it worked before Bookworm if you overwrote the
crypttab.  However, it might be that your LUKS containers were created
with an old version of cryptsetup that did not wipe the start of the
partition properly.  libblkid has had "behavioural changes" in the
past under such circumstances wrt. to block device probing and making
decisions [1].  It might be that whatever component is used to create
/dev/disk/by-* symlinks in the initramfs has changed behaviour, too.
According to your initramfs.debug log it's systemd-udevd.

+ /scripts/init-top/udev
Starting systemd-udevd version 252.6-1

You'd have to try to get access to its log output.

You should also take copies of the first 1 MiB of your partitions that
hold the LUKS containers so libblkid (or whatever the culprit) can be
debugged with before you overwrite anything.  You'll have to provide
copies of some sort if you want someone else to debug this for you --
no idea how to sanitize/dekey them.  "cryptsetup luksErase" might
render the LUKS header unrecognizable.  You'll have to try it out.

If you feel like it you can investigate further with:

  LIBBLKID_DEBUG=all blkid -p
  lsblk -o NAME,SIZE,TYPE,UUID,PARTUUID

The next-heavier cannons would be ltrace/strace and gdb.

> But with this I am back at the original issue.
>
> During this I have spotted an interesting thing.  Even tough I put
> `traditional` disk device paths into /etc/crypttab, the generated
> initramfs has the UUID version of it, even after multiple
> regeneration!
>
> Going even forward, I have seen this in the source code of
> `/usr/share/initramfs-tools/hooks/cryptroot`: 
> https://salsa.debian.org/cryptsetup-team/cryptsetup/-/blob/debian/latest/debian/initramfs/hooks/cryptroot#L43
> That contradicts with your previous statement of no UUID shall be present in
> crypttab

Oops, I was looking at a wrong version of the file.

Regards.

1: https://bugs.launchpad.net/ubuntu/+source/cryptsetup/+bug/428435

Bug#1035570: ITP: omemo-dr -- OMEMO double ratchet for Python

[Martin]

Package: wnpp
Owner: deba...@debian.org
Severity: wishlist
X-Debbugs-Cc: debian-de...@lists.debian.org, 
pkg-xmpp-de...@lists.alioth.debian.org

* Package name: omemo-dr
  Version : 0.99.1
  Upstream Author : Philipp Hörist 
* URL or Web page : https://dev.gajim.org/gajim/omemo-dr/
* License : GPL3
  Programming Lang: Python
  Description : OMEMO double ratchet for Python

Initial codebase was forked from python-axolotl, which is a Python 3
port of libaxolotol-android. The library is defined as a ratcheting
forward secrecy protocol that works in synchronous and asynchronous
messaging environments.

This is a new dependency of Gajim >= 1.8.

Bug#1035569: installation-reports: failed to detect Realtek RTL8852BE WiFi 6 802.11ax PCIe adapter

[Diederik de Haas]

On Friday, 5 May 2023 17:45:34 CEST Fabian Greffrath wrote:
> Today I attempted to install Debian bookworm on a brand new Lenovo
> IdeaPad 5 14IAL7 with an i5-1235U CPU, 16GB RAM and 512GB SDD.
> 
> The installation failed to proceed at the network card detection
> stage. Apparently, the machine has a Realtek RTL8852BE adapter, which
> *should* be supported by recent kernels.

Too recent for Bookworm as it appears that it was added in 6.2,
while Bookworm has 6.1.

signature.asc
Description: This is a digitally signed message part.

Bug#1035569: installation-reports: failed to detect Realtek RTL8852BE WiFi 6 802.11ax PCIe adapter

[Fabian Greffrath]

Package: installation-reports
Severity: normal

Boot method: USB
Image version: debian-bookworm-DI-rc2-amd64-netinst.iso from 2023-05-05
Date: 2023-05-05 12:00

Machine: Lenovo IdeaPad 5 14IAL7
Partitions: 


Base System Installation Checklist:
[O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it

Initial boot:   [O]
Detect network card:[E]
Configure network:  [ ]
Detect media:   [ ]
Load installer modules: [ ]
Clock/timezone setup:   [ ]
User/password setup:[ ]
Detect hard drives: [ ]
Partition hard drives:  [ ]
Install base system:[ ]
Install tasks:  [ ]
Install boot loader:[ ]
Overall install:[E]

Comments/Problems:

Thi shappened on a different machine than the one I write this report
from (obviously, thus removed the logs below).

Today I attempted to install Debian bookworm on a brand new Lenovo
IdeaPad 5 14IAL7 with an i5-1235U CPU, 16GB RAM and 512GB SDD.

The installation failed to proceed at the network card detection
stage. Apparently, the machine has a Realtek RTL8852BE adapter, which
*should* be supported by recent kernels. However, the installer
presented me with a list of kernel modules to choose from. I went
through the list and selected anything that even remotely matched the
adapter name, but without success. Since I only had downloaded the
netinst image, I had to quit the installation proess at this point.

Cheers,

 - Fabian

Bug#849399: Acknowledgement (ITP: rmilter - another sendmail milter for different mail checks)

[Fioddor Superconcentrado]

rspamd was accepted and has been maintained since 2019 [1]. I believe this
ITP can be closed.

[1] https://tracker.debian.org/pkg/rspamd

Bug#1032428: firefox: Menu handling with the mouse is broken

[Vincent Lefevre]

Control: tags -1 - fixed-upstream

Actually not completely fixed. I can still see issues with
the menu bar.

-- 
Vincent Lefèvre  - Web: 
100% accessible validated (X)HTML - Blog: 
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)

Bug#1035568: dnsmasq is broken on new bookworm installations

[Jens Meißner]

Package: dnsmasq
Version: 2.89-1
Severity: grave
Justification: renders package unusable
X-Debbugs-Cc: heptal...@gmx.de

Hello,

dnsmasq on bookworm fails to start after installation because the dns port 53 
is already is use by systemd-resolved.
After stopping systemd-resolved dnsmasq will start but refuses all dns queries 
with the Extended DNS Error Code 14 "Not Ready".
This error is reproducible on new installation.

Setting severity to grave because it affects clean installs. 

Regards,
Jens


Steps to reproduce to problem:

1. Create a new instance from the generic bookworm image: 
https://cdimage.debian.org/images/cloud/bookworm/daily/20230505-1371/debian-12-generic-amd64-daily-20230505-1371.qcow2
2. Update package cache and install dnsmasq: apt update && apt install -y 
dnsmasq
3. dnsmasq will fail to start:

May 05 13:57:17 bookworm systemd[1]: Starting dnsmasq.service - dnsmasq - A 
lightweight DHCP and caching DNS server...
May 05 13:57:17 bookworm dnsmasq[1078]: dnsmasq: failed to create listening 
socket for port 53: Address already in use
May 05 13:57:17 bookworm dnsmasq[1078]: failed to create listening socket for 
port 53: Address already in use
May 05 13:57:17 bookworm dnsmasq[1078]: FAILED to start up
May 05 13:57:17 bookworm systemd[1]: dnsmasq.service: Control process exited, 
code=exited, status=2/INVALIDARGUMENT
May 05 13:57:17 bookworm systemd[1]: dnsmasq.service: Failed with result 
'exit-code'.
May 05 13:57:17 bookworm systemd[1]: Failed to start dnsmasq.service - dnsmasq 
- A lightweight DHCP and caching DNS server.

4. This first problem can be solved by disabling systemd-resolved: systemctl 
disable --now systemd-resolved.service

5. Now dnsmasq can be started (systemctl start dnsmasq.service), but it logs an 
error:

May 05 13:58:51 bookworm systemd[1]: Starting dnsmasq.service - dnsmasq - A 
lightweight DHCP and caching DNS server...
May 05 13:58:51 bookworm dnsmasq[1184]: started, version 2.89 cachesize 150
May 05 13:58:51 bookworm dnsmasq[1184]: DNS service limited to local subnets
May 05 13:58:51 bookworm dnsmasq[1184]: compile time options: IPv6 GNU-getopt 
DBus no-UBus i18n IDN2 DHCP DHCPv6 no-Lua TFTP conntrack ipset nftset auth 
cryptohash DNSSEC loop-detect inotify dumpfile
May 05 13:58:51 bookworm dnsmasq[1184]: read /etc/hosts - 8 names
May 05 13:58:51 bookworm resolvconf[1193]: Dropped protocol specifier 
'.dnsmasq' from 'lo.dnsmasq'. Using 'lo' (ifindex=1).
May 05 13:58:51 bookworm resolvconf[1193]: Failed to set DNS configuration: 
Unit dbus-org.freedesktop.resolve1.service not found.
May 05 13:58:51 bookworm systemd[1]: Started dnsmasq.service - dnsmasq - A 
lightweight DHCP and caching DNS server.

6. Install dnsutils: apt install -y dnsutils

7. Try to query the local nameserver. It will refuse to respond:

$ dig @127.0.0.1 debian.org

; <<>> DiG 9.18.12-1-Debian <<>> @127.0.0.1 debian.org
; (1 server found)
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: REFUSED, id: 14242
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 4096
; EDE: 14 (Not Ready)
;; QUESTION SECTION:
;debian.org.IN  A

;; Query time: 0 msec
;; SERVER: 127.0.0.1#53(127.0.0.1) (UDP)
;; WHEN: Fri May 05 14:00:51 UTC 2023
;; MSG SIZE  rcvd: 45


-- System Information:
Debian Release: 12.0
  APT prefers testing-security
  APT policy: (500, 'testing-security'), (500, 'testing')
Architecture: amd64 (x86_64)

Kernel: Linux 6.1.0-7-amd64 (SMP w/2 CPU threads; PREEMPT)
Locale: LANG=C.UTF-8, LC_CTYPE=C.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 dnsmasq depends on:
ii  dnsmasq-base [dnsmasq-base]  2.89-1
ii  init-system-helpers  1.65.2
ii  netbase  6.4
ii  runit-helper 2.15.2
ii  sysvinit-utils [lsb-base]3.06-4

dnsmasq recommends no packages.

Versions of packages dnsmasq suggests:
ii  systemd-resolved [resolvconf]  252.6-1

-- no debconf information

Bug#1021948: libsdl2-net-dev: dangling symlink libSDL2_net-2.0.so

[Andreas Beckmann]

On 05/05/2023 16.31, Simon McVittie wrote:

I don't think this is a RC bug unless other packages are relying on the
dangling symlink to point to something useful, which it appears they are
not (see ).
The canonical name of this library for linking purposes is SDL2_net,
as in `cc -otest test.o -lSDL2_net`, which results in linking to either
libSDL2_net.so or libSDL2_net.a (and there is no libSDL2_net-2.0.a).

The libSDL2_net-2.0.so symlink would only be required if someone is
linking dependent programs or libraries with "-lSDL2_net-2.0", and it
seems nothing in Debian does that.


Thanks for this analysis showing this is a cruft symlink. Usually a 
broken .so symlink means a missing dependency, missing packaged library 
or renamed target (without updating the link), which are RC, as one 
cannot link to the library (via the intended name).


Andreas

Bug#1035567: debootstrap: Does not support APT repositories with modern split arch:all support

[Matthias Klumpp]

Package: debootstrap
X-Debbugs-Cc: m...@debian.org
Version: 1.0.128+nmu2
Severity: normal
Tags: patch

Dear Maintainer,
currently debootstrap fails to work with APT repositories that have
arch:all split out exclusively into a separate Packages file, instead
of having arch:all merged into every arch:any Packages file in archive
metadata.
APT has already been supporting the new scheme for multiple releases,
so it would be nice if debootstrap supported it too (so far, it is the
only tool I found that doesn't do that). This would enable us in
PureOS to use the new APT repository style, as well as potentially
other derivatives and Debian itself in future as well.

The APT repository format (for both styles and the current
"compatibility mode" that the Debian archive runs on) is described
here: https://wiki.debian.org/DebianRepository/Format#Architectures

I attached a patch which implements support for this feature in
debootstrap. So far it has been working find for bootstrapping both
Debian (with the "compatibility" archive metadata mode) as well as a
PureOS scratch repository which uses the newer-style APT repository
mode.

You can also review this patch as MR @ Salsa:
https://salsa.debian.org/installer-team/debootstrap/-/merge_requests/92

Thank you for considering!
I've set this bug as "normal", since I do consider bringing
debootstrap on-par with what features APT supports for a while as
important, but feel free to reduce it to "whishlist" priority if you
think that is more appropriate for a feature request like this.

With kind regards,
Matthias Klumpp

-- 
I welcome VSRE emails. See http://vsre.info/
From 5dd4cef1a5a03dc180eb2ec1d2bfc97023f74d2b Mon Sep 17 00:00:00 2001
From: Matthias Klumpp 
Date: Sun, 23 Apr 2023 22:30:02 +0200
Subject: [PATCH] Implement support for repos with modern-style arch:all
 support

This implements support for modern APT repositories which have arch:any
and arch:all packages in separate Packages files, as outlined in the
Debian
repository documentation:
https://wiki.debian.org/DebianRepository/Format#Architectures
---
 functions | 274 +-
 1 file changed, 168 insertions(+), 106 deletions(-)

diff --git a/functions b/functions
index 0ff5379..8bffbc6 100644
--- a/functions
+++ b/functions
@@ -557,6 +557,24 @@ extract_release_components () {
 	fi
 }
 
+repo_supports_arch_all () {
+	local a no_arch_all_support
+	local reldest="$1"; shift
+	TMPARCHS="$(sed -n 's/Architectures: *//p' "$reldest")"
+	ARCH_ALL_SUPPORTED=0
+	for a in $TMPARCHS ; do
+		if [ "$a" = "all" ]; then
+			ARCH_ALL_SUPPORTED=1
+			break
+		fi
+	done
+
+	no_arch_all_support=$(grep "^No-Support-for-Architecture-all: Packages$" "$reldest" || true)
+	if [ "$no_arch_all_support" != "" ]; then
+		ARCH_ALL_SUPPORTED=0
+	fi
+}
+
 CODENAME=""
 validate_suite () {
 	local reldest suite s
@@ -667,7 +685,7 @@ download_release_sig () {
 download_release_indices () {
 	local m1 inreldest reldest relsigdest totalpkgs \
 	  subpath xzi bz2i gzi normi i ext \
-	  donepkgs pkgdest acquirebyhash s c m
+	  donepkgs pkgdest acquirebyhash archs s c a m
 	m1="${MIRRORS%% *}"
 	for s in $SUITE $EXTRA_SUITES; do
 		inreldest="$TARGET/$($DLDEST rel "$s" "$m1" "dists/$s/InRelease")"
@@ -680,70 +698,80 @@ download_release_indices () {
 
 		extract_release_components "$reldest"
 
+		repo_supports_arch_all "$reldest"
+
+		archs="$ARCH"
+		if [ $ARCH_ALL_SUPPORTED -eq 1 ]; then
+			archs="all $ARCH"
+		fi
+
 		acquirebyhash=$(grep "^Acquire-By-Hash: yes$" "$reldest" || true)
-		totalpkgs=0
-		for c in $COMPONENTS; do
-			subpath="$c/binary-$ARCH/Packages"
-			xzi="$(get_release_checksum "$reldest" "$subpath.xz")"
-			bz2i="$(get_release_checksum "$reldest" "$subpath.bz2")"
-			gzi="$(get_release_checksum "$reldest" "$subpath.gz")"
-			normi="$(get_release_checksum "$reldest" "$subpath")"
-			if [ "$normi" != "" ]; then
-i="$normi"
-			elif in_path bunzip2 && [ "$bz2i" != "" ]; then
-i="$bz2i"
-			elif in_path unxz && [ "$xzi" != "" ]; then
-i="$xzi"
-			elif in_path gunzip && [ "$gzi" != "" ]; then
-i="$gzi"
-			fi
-			if [ "$i" != "" ]; then
-totalpkgs=$(( $totalpkgs + ${i#* } ))
-			else
-mv "$reldest" "$reldest.malformed"
-error 1 MISSINGRELENTRY "Invalid Release file, no entry for %s" "$subpath"
-			fi
-		done
 
-		donepkgs=0
-		progress 0 $totalpkgs DOWNPKGS "Downloading Packages files"
-		for c in $COMPONENTS; do
-			subpath="$c/binary-$ARCH/Packages"
-			path="dists/$s/$subpath"
-			xzi="$(get_release_checksum "$reldest" "$subpath.xz")"
-			bz2i="$(get_release_checksum "$reldest" "$subpath.bz2")"
-			gzi="$(get_release_checksum "$reldest" "$subpath.gz")"
-			normi="$(get_release_checksum "$reldest" "$subpath")"
-			ext=""
-			if [ "$acquirebyhash" != "" ]; then
-ext="$ext byhash"
-			fi
-			if [ "$normi" != "" ]; then
-ext="$ext $normi ."
-i="$normi"
-			fi
-			if in_path unxz && [ "$xzi" != "" ]; then
-ext="$ext $xzi xz"
-			

Bug#1021948: libsdl2-net-dev: dangling symlink libSDL2_net-2.0.so

[Simon McVittie]

Control: severity -1 normal

On Mon, 17 Oct 2022 at 21:54:35 +0200, Sven Joachim wrote:
> Package: libsdl2-net-dev
> Version: 2.2.0+dfsg-1
[note lack of RC severity]
> 
> Your package contains a dangling symlink:
> 
> ,
> | $ file /usr/lib/x86_64-linux-gnu/libSDL2_net-2.0.so
> | /usr/lib/x86_64-linux-gnu/libSDL2_net-2.0.so: broken symbolic link to 
> libSDL2_net-2.0.so.0.0.1
> `
> 
> This symlink is created via dh_link in debian/rules with a comment that
> it exists to fix a dev-pkg-without-shlib-symlink lintian warning.  It
> seems that this warning does no longer trigger, though.

On Wed, 03 May 2023 at 19:19:39 +0200, Andreas Beckmann wrote:
> usertags 1021948 piuparts
> severity 1021948 serious

I don't think this is a RC bug unless other packages are relying on the
dangling symlink to point to something useful, which it appears they are
not (see ).
The canonical name of this library for linking purposes is SDL2_net,
as in `cc -otest test.o -lSDL2_net`, which results in linking to either
libSDL2_net.so or libSDL2_net.a (and there is no libSDL2_net-2.0.a).

The libSDL2_net-2.0.so symlink would only be required if someone is
linking dependent programs or libraries with "-lSDL2_net-2.0", and it
seems nothing in Debian does that.

Unless there is a reason why this needs to be considered release-critical
that isn't obvious to me?

When elevating a bug report to release-critical, please mention why you
believe it's a release-critical problem in a mail to the bug, otherwise
the maintainer has no context for it (and might not even be aware that
its severity has been raised).

I agree that the dangling symlink is a bug, and libSDL2_net-2.0.so should
either not exist, or point to a file that exists (the easiest would be
libSDL2_net-2.0.so.0, matching what happens in the rest of the libsdl2
family).

The libsdl3 prerelease in experimental has removed this weird
historical versioning thing, and just ships libSDL3.so, libSDL3.so.0
and libSDL3.so.0.0.0, as is conventional; the extra names with -2.0 in them
are a historical quirk of the upstream build system for the libsdl2 family,
which used `libtool -release`, apparently due to a misunderstanding.

smcv

Bug#1035558: Acknowledgement (libxml2-utils: xmllint ignores --output option and writes to stdout)

[Tj]

Apologies - email client didn't fill the correct address. This was a 
reply to bug #1035554


https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1035554

This can be closed!

Bug#1035554: libxml2-utils: xmllint ignores --output option and writes to stdout

[Tj]

I've done some follow-up debugging (on upstream git) to be sure the 
problem seems to exist upstream - unless I'm severely misunderstanding 
what --output is supposed to do. Anyhow; the trace shows it reaches 
doXPathDump(). Note that 'buf' is hard-coded to use stdout. The call to 
xmlOutputBufferClose(buf) causes the output to be sent. In gdb I confirm 
'output' is set immediately after that:


$ gdb -directory /srv/NAS/Sunny/SourceCode/libxml2/libxml2 -args 
/srv/NAS/Sunny/SourceCode/libxml2/libxml2/.libs/xmllint --output 
test.txt --html --xpath '//div[contains(@class, 
'\''test'\'')]/div/ul/li/a/@href' xmllint-test.html


2038break;
(gdb) p output
$1 = 0x7fffe1d5 "test.txt"

xmllint.c:

static void doXPathDump(xmlXPathObjectPtr cur) {
switch(cur->type) {
case XPATH_NODESET: {
int i;
xmlNodePtr node;
#ifdef LIBXML_OUTPUT_ENABLED
xmlOutputBufferPtr buf;

if ((cur->nodesetval == NULL) || (cur->nodesetval->nodeNr 
<= 0)) {

if (!quiet) {
fprintf(stderr, "XPath set is empty\n");
}
break;
}
buf = xmlOutputBufferCreateFile(stdout, NULL);
if (buf == NULL) {
fprintf(stderr, "Out of memory for XPath\n");
progresult = XMLLINT_ERR_MEM;
return;
}
for (i = 0;i < cur->nodesetval->nodeNr;i++) {
node = cur->nodesetval->nodeTab[i];
xmlNodeDumpOutput(buf, NULL, node, 0, 0, NULL);
xmlOutputBufferWrite(buf, 1, "\n");
}
xmlOutputBufferClose(buf);

Bug#1003862: Some news about a fix ?

[Jérôme Bardot]

thx …

Le ven. 5 mai 2023 à 16:16, Holger Levsen  a écrit :
>
> control: tags -1 + wontfix
> thanks
>
> On Fri, May 05, 2023 at 03:49:44PM +0200, Jérôme Bardot wrote:
> > That bug is currently blocking from using munin on not systemd systems.
>
> I'm not planning on supporting legacy initscripts myself. And despite tagging
> this bug 'wontfix' for the time being I will accept patches, so IOW I'm just
> tagging this 'wontfix' to set expectations right.
>
> In the long term I think munin's initscripts should be moved to
> src:orphan-sysvinit-scripts and be maintained there by those who care.
>
>
> --
> cheers,
> Holger
>
>  ⢀⣴⠾⠻⢶⣦⠀
>  ⣾⠁⢠⠒⠀⣿⡁  holger@(debian|reproducible-builds|layer-acht).org
>  ⢿⡄⠘⠷⠚⠋⠀  OpenPGP: B8BF54137B09D35CF026FE9D 091AB856069AAA1C
>  ⠈⠳⣄
>
> "A developed country is not a place where the poor have cars. It's where the
> rich use public transportation." (quote attributed to several people)

Bug#1022043: apt-cacher-ng: sometimes fails to download some index files - maybe a race condition

[Koen Roggemans]

I can confirm this behaviour on Ubuntu 22.04.

I see the creation of an Inrelease.timestamp also with 1 client.

My apt-cacher-ng installation is upgraded from 3.3.1 to the version 
mentioned in this report.


Unfortunately I couldn't find any helpfull extra information. I tried 
making some changes to the config file, which don't seem to help.



MaxConThreads: 300
DlMaxRetries: 4
PrecacheFor: uburep/dists/jammy/InRelease
KeepExtraVersions: 1
FreshIndexMaxAge: 300
VfileUseRangeOps: -1
PassThroughPattern: ^(.*):443$
ResponseFreezeDetectTime: 30

--
Koen Roggemans
ICT-Coördinator Sint-Rita Campus CollegeBEGIN:VCARD
VERSION:4.0
EMAIL;PREF=1:koen.roggem...@ritacollege.be
FN:Koen Roggemans
ORG:Sint-Ritacollege;
TITLE:ICT-Coördinator
N:Roggemans;Koen;;;
ADR:;;Pierstraat 1;Kontich;Antwerpen;2550;België
URL;VALUE=URL:https://www.ritacollege.be
UID:be5a736b-c36d-49a5-b5ef-8db11335b5f2
END:VCARD

Bug#1003862: Some news about a fix ?

[Holger Levsen]

control: tags -1 + wontfix
thanks

On Fri, May 05, 2023 at 03:49:44PM +0200, Jérôme Bardot wrote:
> That bug is currently blocking from using munin on not systemd systems.

I'm not planning on supporting legacy initscripts myself. And despite tagging
this bug 'wontfix' for the time being I will accept patches, so IOW I'm just
tagging this 'wontfix' to set expectations right.

In the long term I think munin's initscripts should be moved to 
src:orphan-sysvinit-scripts and be maintained there by those who care.


-- 
cheers,
Holger

 ⢀⣴⠾⠻⢶⣦⠀
 ⣾⠁⢠⠒⠀⣿⡁  holger@(debian|reproducible-builds|layer-acht).org
 ⢿⡄⠘⠷⠚⠋⠀  OpenPGP: B8BF54137B09D35CF026FE9D 091AB856069AAA1C
 ⠈⠳⣄

"A developed country is not a place where the poor have cars. It's where the
rich use public transportation." (quote attributed to several people)


signature.asc
Description: PGP signature

Bug#1035566: ITP: gl4es -- OpenGL 2.1/1.5 to GLES 2.0/1.1 translation library title

[李程]

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

* Package name: gl4es
  Version : 1.1.4
  Upstream Author : ptitSeb
* URL : https://github.com/ptitSeb/gl4es
* License : MIT
  Programming Lang: c
  Description : OpenGL 2.1/1.5 to GLES 2.0/1.1 translation library

 This is a library provide OpenGL 2.x functionality for GLES2.0 accelerated
Hardware
 (and of course also support OpenGL 1.5 function, so metimes better than
when using
 GLES 1.1 backend) There is also support for GLES 1.1 Hardware, emulating
OpenGL 1.5,
 and some OpenGL 2.x + extensions.
 This package contains the shared libraries

Bug#1035565: /usr/src/evdi-1.12.0+dfsg/evdi_debug.c: Error fatal error: drm.h: No such file or directory when updating kernel

[John Breland]

Subject: /usr/src/evdi-1.12.0+dfsg/evdi_debug.c: Error fatal error: drm.h: No 
such file or directory when updating kernel
Package: evdi-dkms
Version: 1.12.0+dfsg-0.3
Severity: important
File: /usr/src/evdi-1.12.0+dfsg/evdi_debug.c

Dear Maintainer,

Good Day, I am having an issue with evdi-dkms when attempting to update to the 
latest kernel 6.1.0-8.
I get the error
 /var/lib/dkms/evdi/1.13.1/build/evdi_drm.h:19:10: fatal error: drm.h: No such 
file or directory
in the make.log file when the system attempts to update the initramfs for it.
I have attempted to update the initramfs in a few different ways and I get the 
same error. I also get
 have attempted to update the dkms directly but no luck. I know that evdi 1.13 
is out upstream but don't
think that would cause this. If you have any questions let me know.


-- System Information:
Debian Release: 12.0
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 6.1.0-7-amd64 (SMP w/8 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)
Subject: /usr/src/evdi-1.12.0+dfsg/evdi_debug.c: Error fatal error: drm.h: No 
such file or directory when updating Kernal
Package: evdi-dkms
Version: 1.12.0+dfsg-0.3
Severity: important
File: /usr/src/evdi-1.12.0+dfsg/evdi_debug.c

Dear Maintainer,

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

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

*** End of the template - remove these template lines ***
Good Day, I am having an issue with evdi-dkms when updating to the latest 
kernel 6.1.0-8.
I get the error "/var/lib/dkms/evdi/1.13.1/build/evdi_drm.h:19:10: fatal error: 
drm.h: No such file or directory"
in the make.log file  when the system attempts to update the initramfs for it.
I have attempted to update the initramfs in a few different ways and I get the 
same error and
 have attempted to update the dkms directly but no luck. I know that evdi 1.13 
is out upstream but don't
think that would cause this. If you would like the reports and terminal 
information please let me know.




-- System Information:
Debian Release: 12.0
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 6.1.0-7-amd64 (SMP w/8 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)

Versions of packages evdi-dkms depends on:
ii  dkms  3.0.10-8

Versions of packages evdi-dkms recommends:
pn  libevdi0  

evdi-dkms suggests no packages.

-- no debconf information

Versions of packages evdi-dkms depends on:
ii  dkms  3.0.10-8

Versions of packages evdi-dkms recommends:
pn  libevdi0  

evdi-dkms suggests no packages.

-- no debconf information

Bug#1003862: Some news about a fix ?

[Jérôme Bardot]

That bug is currently blocking from using munin on not systemd systems.

Bug#1035564: unblock: lxd/5.0.2-5

[Mathias Gibbens]

Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
Control: affects -1 + src:lxd

Please unblock package lxd

[ Reason ]
Added a missing Replaces in d/control for bin:lxd-client to address an
upgrade edge case from bullseye where lxc was already installed and
some other package being upgraded Depends/Recommends lxd which could
potentially result in a dpkg error (see #1034971).

lxd has autopkgtests, but as we're now within 20 days of the full
freeze, a manual unblock is required.

[ Impact ]
There's a chance that an upgrade from bullseye to bookworm might fail.

Additionally, this upload of lxd to unstable reset the migration
counter before lxd 5.0.2-4 was able to migrate with a fix for running
with the version of qemu in testing.

[ Tests ]
I manually tested installing lxd-client on a bullseye system with lxc
installed:

> Preparing to unpack lxd-client_5.0.2-3_amd64.deb ...
> Unpacking lxd-client (5.0.2-3) ...
> dpkg: error processing archive lxd-client_5.0.2-3_amd64.deb (--install):
>  trying to overwrite '/usr/share/bash-completion/completions/lxc', which is 
> also in package lxc 1:4.0.6-2+deb11u2
> dpkg-deb: error: paste subprocess was killed by signal (Broken pipe)

With the fix:

> Preparing to unpack .../lxd-client_5.0.2-5_amd64.deb ...
> Unpacking lxd-client (5.0.2-5) ...
> Replacing files in old package lxc (1:4.0.6-2+deb11u2) ...

[ Risks ]
I don't believe there are any risks with this change.

[ 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 testing

[ Other info ]
As mentioned, lxd 5.0.2-4 had been on track to automatically migrate
around May 14 with a fix for use with the version of qemu in testing
(see #1030365). Since the requested debdiff is against the version of
lxd in testing, it contains changes from both -4 and -5.

unblock lxd/5.0.2-5
diff -Nru lxd-5.0.2/debian/changelog lxd-5.0.2/debian/changelog
--- lxd-5.0.2/debian/changelog	2023-03-08 02:27:33.0 +
+++ lxd-5.0.2/debian/changelog	2023-05-05 12:42:21.0 +
@@ -1,3 +1,16 @@
+lxd (5.0.2-5) unstable; urgency=medium
+
+  * Add missing Replaces in d/control for lxd-client to fix potential bullseye
+upgrade issue (Closes: #1034971)
+
+ -- Mathias Gibbens   Fri, 05 May 2023 12:42:21 +
+
+lxd (5.0.2-4) unstable; urgency=medium
+
+  * Cherry-pick upstream fix for qemu >= 7.2 (Closes: #1030365)
+
+ -- Mathias Gibbens   Sun, 23 Apr 2023 17:50:08 +
+
 lxd (5.0.2-3) unstable; urgency=medium
 
   * Cherry-pick upstream commit to fix issue with btrfs-progs >= 6.0
diff -Nru lxd-5.0.2/debian/control lxd-5.0.2/debian/control
--- lxd-5.0.2/debian/control	2023-03-08 02:27:33.0 +
+++ lxd-5.0.2/debian/control	2023-05-05 12:42:21.0 +
@@ -99,8 +99,9 @@
 Package: lxd-client
 # The lxc binary doesn't depend on liblxc1, so it can be built for any architecture
 Architecture: any
-# lxc prior to 5.0.0 shipped a file that conflicts with LXD (see #1010843)
-Breaks: lxc (<< 1:5.0.0)
+# lxc prior to 5.0.1 shipped a file that conflicts with LXD (see #1010843, #1034971)
+Breaks: lxc (<< 1:5.0.1)
+Replaces: lxc (<< 1:5.0.1)
 Depends: ${misc:Depends},
  ${shlibs:Depends}
 Built-Using: ${misc:Built-Using}
diff -Nru lxd-5.0.2/debian/patches/006-cherry-pick-btrfs-fix.patch lxd-5.0.2/debian/patches/006-cherry-pick-btrfs-fix.patch
--- lxd-5.0.2/debian/patches/006-cherry-pick-btrfs-fix.patch	2023-03-08 02:27:33.0 +
+++ lxd-5.0.2/debian/patches/006-cherry-pick-btrfs-fix.patch	2023-05-05 12:42:21.0 +
@@ -1,3 +1,6 @@
+From: Mathias Gibbens 
+Description: Cherry-pick upstream commit to fix issue with btrfs-progs >= 6.0
+Origin: https://github.com/lxc/lxd/pull/11333
 From e7c852e43c0479060e630adb50342d2552a6cdad Mon Sep 17 00:00:00 2001
 From: Thomas Parrott 
 Date: Tue, 7 Feb 2023 10:04:27 +
diff -Nru lxd-5.0.2/debian/patches/007-cherry-pick-qemu-fix.patch lxd-5.0.2/debian/patches/007-cherry-pick-qemu-fix.patch
--- lxd-5.0.2/debian/patches/007-cherry-pick-qemu-fix.patch	1970-01-01 00:00:00.0 +
+++ lxd-5.0.2/debian/patches/007-cherry-pick-qemu-fix.patch	2023-05-05 12:42:21.0 +
@@ -0,0 +1,90 @@
+From: Mathias Gibbens 
+Description: Cherry-pick upstream fix for qemu >= 7.2, rebase, and drop SEV features not in current LTS release
+Origin: https://github.com/lxc/lxd/pull/11594
+diff --git a/lxd/instance/drivers/driver_qemu.go b/lxd/instance/drivers/driver_qemu.go
+index 9dcdd9da7..08211b034 100644
+--- a/lxd/instance/drivers/driver_qemu.go
 b/lxd/instance/drivers/driver_qemu.go
+@@ -2878,17 +2878,11 @@ func (d *qemu) generateQemuConfigFile(mountInfo *storagePools.MountInfo, busName
+ // addCPUMemoryConfig adds the qemu config required for setting the number of virtualised CPUs and memory.
+ // If sb is nil then no config is written.
+ func (d *qemu) addCPUMemoryConfig(cfg *[]cfgSection) error {
+-	

Bug#1035517: evolution: Text display of mails a narrow strip

[Nathan A. Stine]

On Thu, 04 May 2023 17:39:46 +0200 nullproblemo
 wrote:
> Package: evolution
> Version: 3.38.3-1+deb11u1
> Severity: important
> 
> Dear Maintainer,
> 
> 
> starting Evolution:
> In Evolution the text display of the mails is only a narrow strip
since 4 May
> 2023 so nothing nothing can be read. This is identical in the preview
and in
> the large view. The same situation on 3 computers. The problem is
known in the
> german forum:
https://debianforum.de/forum/viewtopic.php?p=1326471#p1326471
> 
> 

This appears to be a duplicate of #1035469. I experienced the same
problem, but an upgrade to 3.38.3-1+deb11u2 fixed the issue.

Nathan A. Stine

Bug#1035497: ufw: Deny forwarding but still forward ping requests

[Jamie Strandboge]

Hi,

Thank you for your report.

By default, ufw adds rules for icmp echo-request to the host *before*
'user rules' in /etc/ufw/before.rules and /etc/ufw/before6.rules. This
is why the 'ufw route deny' rules aren't affecting the ping request
behavior. This is expected behavior.

However, modifying the default behavior and adding icmp rules is
supported via the ufw framework, by modifying /etc/ufw/before.rules,
/etc/ufw/before6.rules, /etc/ufw/after.rules and/or
/etc/ufw/after6.rules as desired (see 'man ufw-framework').

In your case, you mention adding '-A ufw-before-forward' rules (so it
seems like you are familiar with the ufw framework), which is one way to
modify the default behavior. Another option is to instead remove the
default echo-request rules in the /etc/ufw/before* files and then add a
'user rule' (ie, one added via the ufw cli) that doesn't specify a
protocol or port.


On Thu, 04 May 2023, Marek Küthe wrote:

> Package: ufw
> Version: 0.36-7.1
> Severity: normal
> 
> Dear Maintainer,
> 
> *** Reporter, please consider answering these questions, where
> appropriate ***
> 
> Hello,
> 
> I use my server as a kind of VPN server, but I only want my client to
> use a specific IP address. So I used the following rules: ```
> ufw route deny out on client09 from any to any comment 'vpn client09'
> ufw route deny in on client09 from any to any comment 'vpn client09'
> ufw route prepend allow in on client09 from 172.22.149.116 comment 'vpn
> client09' ufw route prepend allow in on client09 from
> fd04:234e:fc31:e::9 comment 'vpn client09' ```
> 
> However, I can send ping requests without 'ufw route prepend allow' and
> get a response, whereas the rule clearly says Deny. Apparently ping
> requests are always allowed through.
> 
> As a workaround I can add the following manually:
> ```
> -A ufw-before-forward -i client09 -p icmp -s 172.22.149.116 -j ACCEPT
> -A ufw-before-forward -i client09 -p icmp -j DROP
> 
> -A ufw6-before-forward -i client09 -p ipv6-icmp -s fd92:58b6:2b2:e::9
> -j ACCEPT -A ufw6-before-forward -i client09 -p ipv6-icmp -j DROP
> ```
> 
> I have set `DEFAULT_FORWARD_POLICY="ACCEPT"`.
> 
> However, I think (and hope) that this behavior is not intentional.
> Hence this bug report. If I forbid a forwarding it has a good reason
> and then I also want this to be forbidden.
> 
> *** End of the template - remove these template lines ***
> 
> 
> -- System Information:
> Debian Release: 11.7
>   APT prefers stable-updates
>   APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500,
> 'stable') Architecture: amd64 (x86_64)
> 
> Kernel: Linux 5.10.0-22-amd64 (SMP w/4 CPU threads)
> Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=locale: Cannot
> set LC_ALL to default locale: No such file or directory 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 ufw depends on:
> ii  debconf [debconf-2.0]  1.5.77
> ii  iptables   1.8.7-1
> ii  lsb-base   11.1.0
> ii  python33.9.2-3
> ii  ucf3.0043
> 
> ufw recommends no packages.
> 
> Versions of packages ufw suggests:
> ii  rsyslog  8.2102.0-2+deb11u1
> 
> -- debconf information excluded
> 
> -- debsums errors found:
> perl: warning: Setting locale failed.
> perl: warning: Please check that your locale settings:
>   LANGUAGE = "en_US:en",
>   LC_ALL = (unset),
>   LC_TIME = "de_DE.UTF-8",
>   LC_MONETARY = "de_DE.UTF-8",
>   LC_ADDRESS = "de_DE.UTF-8",
>   LC_TELEPHONE = "de_DE.UTF-8",
>   LC_NAME = "de_DE.UTF-8",
>   LC_MEASUREMENT = "de_DE.UTF-8",
>   LC_IDENTIFICATION = "de_DE.UTF-8",
>   LC_NUMERIC = "de_DE.UTF-8",
>   LC_PAPER = "de_DE.UTF-8",
>   LANG = "en_US.UTF-8"
> are supported and installed on your system.
> perl: warning: Falling back to a fallback locale ("en_US.UTF-8").


-- 
Email: ja...@strandboge.com
IRC:   jdstrand

Bug#1034785: Version string

[Martin Dosch]

Dear all,

after consulting #debian-devel again I changed the version string to 
0.8.3+really0.8.1-0.1 which makes lintian happy (thanks again).

I'm going to upload it and hope it will be applicable for an unblock.

Best regards,
Martin
diff -Nru gummi-0.8.1/debian/changelog gummi-0.8.3+really0.8.1/debian/changelog
--- gummi-0.8.1/debian/changelog2020-03-25 19:27:44.0 +0100
+++ gummi-0.8.3+really0.8.1/debian/changelog2023-05-05 14:36:08.0 
+0200
@@ -1,3 +1,17 @@
+gummi (0.8.3+really0.8.1-0.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Apply patch to fix typesetter parsing (Closes: #1012150)
+
+ -- Martin Dosch   Fri, 05 May 2023 12:36:08 +
+
+gummi (0.8.3-1) unstable; urgency=high
+
+  * Team Upload
+  * New upstream version 0.8.3 (Closes: #1030293, #1012150)
+
+ -- Martin Dosch   Fri, 21 Apr 2023 05:15:00 +
+
 gummi (0.8.1-1) unstable; urgency=medium
 
   * Team Upload
diff -Nru gummi-0.8.1/debian/patches/0002-fix-typesetter-parsing 
gummi-0.8.3+really0.8.1/debian/patches/0002-fix-typesetter-parsing
--- gummi-0.8.1/debian/patches/0002-fix-typesetter-parsing  1970-01-01 
01:00:00.0 +0100
+++ gummi-0.8.3+really0.8.1/debian/patches/0002-fix-typesetter-parsing  
2023-05-02 10:08:58.0 +0200
@@ -0,0 +1,85 @@
+Description: fix typesetter parsing bug
+Origin: upstream, 
https://github.com/alexandervdm/gummi/commit/99a64220ad51308b1bd3e1c938743ff08c9b769b
+Bug: https://github.com/alexandervdm/gummi/issues/169
+---
+This patch header follows DEP-3: http://dep.debian.net/deps/dep3/
+--- a/src/external.c
 b/src/external.c
+@@ -34,8 +34,8 @@
+ 
+ /* local functions */
+ static gchar* get_version_output (const gchar* command, int linenr);
+-static gchar* version_latexmk (const gchar* output);
+-static gchar* version_rubber (const gchar* output);
++static gchar* version_latexmk (gchar* output);
++static gchar* version_rubber (gchar* output);
+ 
+ 
+ static gdouble get_texlive_version (void);
+@@ -80,16 +80,19 @@
+ }
+ 
+ gchar* external_version (const gchar* program) {
+-const gchar* getversion = g_strdup_printf("%s --version", program);
+-Tuple2 cmdgetv = utils_popen_r (getversion, NULL);
+-gchar* output = (gchar*)cmdgetv.second;
++gchar* version_output;
++gchar* result;
+ 
+-gchar* result = g_strdup ("Unknown, please report a bug");
++const gchar* version_cmd = g_strdup_printf("%s --version", program);
++Tuple2 cmdgetv = utils_popen_r (version_cmd, NULL);
++version_output = (gchar*)cmdgetv.second;
+ 
+-if (output == NULL) return result;
+-
+-gchar** lines = g_strsplit(output, "\n", BUFSIZ);
+-result = lines[0];
++if (version_output == NULL || g_str_equal (version_output, "")) {
++return g_strdup_printf("Unknown, please report a bug");
++}
++else {
++result = g_strstrip (version_output);
++}
+ 
+ /* pdfTeX 3.1415926-1.40.10 (TeX Live 2009)
+pdfTeX 3.1415926-1.40.11-2.2 (TeX Live 2010)
+@@ -101,7 +104,7 @@
+ result = version_rubber (result);
+ }
+ else if (STR_EQU (program, C_LATEXMK)) {
+-result = version_latexmk (lines[1]);
++result = version_latexmk (result);
+ }
+ 
+ return result;
+@@ -145,16 +148,20 @@
+ return version;
+ }
+ 
+-static gchar* version_rubber (const gchar* output) {
+-/* format: Rubber version: 1.1 */
+-gchar** version = g_strsplit (output, " ", BUFSIZ);
+-return version[2];
++static gchar* version_rubber (gchar* output) {
++// format: Rubber version: 1.1
++gchar** outarr = g_strsplit (output, " ", BUFSIZ);
++gchar* version = g_strdup (outarr [g_strv_length(outarr) - 1]);
++
++g_strfreev (outarr);
++return version;
+ }
+ 
+-static gchar* version_latexmk (const gchar* output) {
+-/* latexmk --version seems to print the requested information after a \n
+-   format: Latexmk, John Collins, 24 March 2011. Version 4.23a */
++static gchar* version_latexmk (gchar* output) {
++// format: Latexmk, John Collins, 24 March 2011. Version 4.23a
++gchar** outarr = g_strsplit (output, " ", BUFSIZ);
++gchar* version = g_strdup (outarr [g_strv_length(outarr) - 1]);
+ 
+-gchar** version = g_strsplit (output, " ", BUFSIZ);
+-return version[7];
++g_strfreev (outarr);
++return version;
+ }
diff -Nru gummi-0.8.1/debian/patches/series 
gummi-0.8.3+really0.8.1/debian/patches/series
--- gummi-0.8.1/debian/patches/series   2020-03-25 19:27:44.0 +0100
+++ gummi-0.8.3+really0.8.1/debian/patches/series   2023-05-02 
10:09:26.0 +0200
@@ -1 +1,2 @@
 0001-spellings.patch
+0002-fix-typesetter-parsing


signature.asc
Description: PGP signature

Bug#1034785: Version

[Martin Dosch]

Dear all,

ok after asking in #debian-devel I know now that this version string 
does not work and I changed it to 0.8.3+really0.8.1-1.1.

But there is still this lintian warning:
W: gummi source: changelog-file-missing-explicit-entry 0.8.3-1 -> 
0.8.3+really0.8.1-1 (missing) -> 0.8.3+really0.8.1-1.1 
[debian/changelog:1]


Any feedback is welcome.

Best regards,
Martin
diff -Nru gummi-0.8.1/debian/changelog gummi-0.8.3+really0.8.1/debian/changelog
--- gummi-0.8.1/debian/changelog2020-03-25 19:27:44.0 +0100
+++ gummi-0.8.3+really0.8.1/debian/changelog2023-05-05 14:36:08.0 
+0200
@@ -1,3 +1,17 @@
+gummi (0.8.3+really0.8.1-1.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Apply patch to fix typesetter parsing (Closes: #1012150)
+
+ -- Martin Dosch   Fri, 05 May 2023 12:36:08 +
+
+gummi (0.8.3-1) unstable; urgency=high
+
+  * Team Upload
+  * New upstream version 0.8.3 (Closes: #1030293, #1012150)
+
+ -- Martin Dosch   Fri, 21 Apr 2023 05:15:00 +
+
 gummi (0.8.1-1) unstable; urgency=medium
 
   * Team Upload
diff -Nru gummi-0.8.1/debian/patches/0002-fix-typesetter-parsing 
gummi-0.8.3+really0.8.1/debian/patches/0002-fix-typesetter-parsing
--- gummi-0.8.1/debian/patches/0002-fix-typesetter-parsing  1970-01-01 
01:00:00.0 +0100
+++ gummi-0.8.3+really0.8.1/debian/patches/0002-fix-typesetter-parsing  
2023-05-02 10:08:58.0 +0200
@@ -0,0 +1,85 @@
+Description: fix typesetter parsing bug
+Origin: upstream, 
https://github.com/alexandervdm/gummi/commit/99a64220ad51308b1bd3e1c938743ff08c9b769b
+Bug: https://github.com/alexandervdm/gummi/issues/169
+---
+This patch header follows DEP-3: http://dep.debian.net/deps/dep3/
+--- a/src/external.c
 b/src/external.c
+@@ -34,8 +34,8 @@
+ 
+ /* local functions */
+ static gchar* get_version_output (const gchar* command, int linenr);
+-static gchar* version_latexmk (const gchar* output);
+-static gchar* version_rubber (const gchar* output);
++static gchar* version_latexmk (gchar* output);
++static gchar* version_rubber (gchar* output);
+ 
+ 
+ static gdouble get_texlive_version (void);
+@@ -80,16 +80,19 @@
+ }
+ 
+ gchar* external_version (const gchar* program) {
+-const gchar* getversion = g_strdup_printf("%s --version", program);
+-Tuple2 cmdgetv = utils_popen_r (getversion, NULL);
+-gchar* output = (gchar*)cmdgetv.second;
++gchar* version_output;
++gchar* result;
+ 
+-gchar* result = g_strdup ("Unknown, please report a bug");
++const gchar* version_cmd = g_strdup_printf("%s --version", program);
++Tuple2 cmdgetv = utils_popen_r (version_cmd, NULL);
++version_output = (gchar*)cmdgetv.second;
+ 
+-if (output == NULL) return result;
+-
+-gchar** lines = g_strsplit(output, "\n", BUFSIZ);
+-result = lines[0];
++if (version_output == NULL || g_str_equal (version_output, "")) {
++return g_strdup_printf("Unknown, please report a bug");
++}
++else {
++result = g_strstrip (version_output);
++}
+ 
+ /* pdfTeX 3.1415926-1.40.10 (TeX Live 2009)
+pdfTeX 3.1415926-1.40.11-2.2 (TeX Live 2010)
+@@ -101,7 +104,7 @@
+ result = version_rubber (result);
+ }
+ else if (STR_EQU (program, C_LATEXMK)) {
+-result = version_latexmk (lines[1]);
++result = version_latexmk (result);
+ }
+ 
+ return result;
+@@ -145,16 +148,20 @@
+ return version;
+ }
+ 
+-static gchar* version_rubber (const gchar* output) {
+-/* format: Rubber version: 1.1 */
+-gchar** version = g_strsplit (output, " ", BUFSIZ);
+-return version[2];
++static gchar* version_rubber (gchar* output) {
++// format: Rubber version: 1.1
++gchar** outarr = g_strsplit (output, " ", BUFSIZ);
++gchar* version = g_strdup (outarr [g_strv_length(outarr) - 1]);
++
++g_strfreev (outarr);
++return version;
+ }
+ 
+-static gchar* version_latexmk (const gchar* output) {
+-/* latexmk --version seems to print the requested information after a \n
+-   format: Latexmk, John Collins, 24 March 2011. Version 4.23a */
++static gchar* version_latexmk (gchar* output) {
++// format: Latexmk, John Collins, 24 March 2011. Version 4.23a
++gchar** outarr = g_strsplit (output, " ", BUFSIZ);
++gchar* version = g_strdup (outarr [g_strv_length(outarr) - 1]);
+ 
+-gchar** version = g_strsplit (output, " ", BUFSIZ);
+-return version[7];
++g_strfreev (outarr);
++return version;
+ }
diff -Nru gummi-0.8.1/debian/patches/series 
gummi-0.8.3+really0.8.1/debian/patches/series
--- gummi-0.8.1/debian/patches/series   2020-03-25 19:27:44.0 +0100
+++ gummi-0.8.3+really0.8.1/debian/patches/series   2023-05-02 
10:09:26.0 +0200
@@ -1 +1,2 @@
 0001-spellings.patch
+0002-fix-typesetter-parsing


signature.asc
Description: PGP signature

Bug#1023844: nftables: firewalld segfaults in libnftables.so rule.c cache_init_objects()

[Tjeu Kayim]

It has been a few months, and we still experience the issue.
Today, we started an experiment updating one of the computers to the following 
newer packages:
libnftables1_1.0.6-2_amd64.deb  libnftnl11_1.2.4-2_amd64.deb  
nftables_1.0.6-2_amd64.deb  python3-nftables_1.0.6-2_amd64.deb,
compiled from source because the pre-built binaries from debian unstable 
repositories depend on an incompatible libc6.
I'll let this run for a few weeks to see if it resolves the segfault issue.

If it does not help, I could try Bernhard's suggestion of rr-debugger.

Greetings, Tjeu

Bug#1035563: New upstream version 1.22.0

[Guido Günther]

Source: wayland
Version: 1.21.0-1
Severity: wishlist


Hi,
wayland 1.22.0 has been released:

   https://gitlab.freedesktop.org/wayland/wayland/-/tags/1.22.0

Would be great to have that in experimental. I've made an MR to update
here:

   https://salsa.debian.org/xorg-team/wayland/wayland/-/merge_requests/5

Happy to NMU if that looks o.k.

Cheers,
 -- Guido


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

Kernel: Linux 6.1.0-7-amd64 (SMP w/12 CPU threads; PREEMPT)
Kernel taint flags: TAINT_WARN, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.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

Bug#1035103: re : ITP: grimripper -- Graphical audio CD ripper and encoder

[Peter B]

Upstream have now renamed the project to GrimRipper

https://gitlab.gnome.org/Salamandar/GrimRipper

Bug#1034796: kio-gdrive: Does not work. Network account create does not propose gogle drive

[Eric Valette]

On 30/04/2023 00:48, Nicholas D Steeves wrote:

Control: severity -1 important
Control: tag -1 moreinfo

Justification: Package is not unusable for everyone.  See the following
for further info: https://www.debian.org/Bugs/Developer#severities


It is hard to know if it is broken for you or for many others. As I saw 
exactly the same reports on other distrib I assume this is a general 
problem.





Using dolphin for network, you can select gdrive but it does not propose to add
a google account.



That's odd, mine shows a "New account" button.



I tested on another computer with exactly the same setup unstable + 
experimental, nearly same package set (well execpt I use a generic 
debian kernel on this one). And there it kinda works:


1)I cannot access an old account,
2) but I can create a new one
3) and relaucching kdeinit5 I can even access the content,

So this is probably incompatible left over in the .config or similar. I 
will try to search for gdrive or kio there.




Kernel: Linux 5.15.108 (SMP w/8 CPU threads; PREEMPT)


Neat, I track this branch too :)


It is my own kernel that I use for years on my machin just updating it 
to official long term stable...



Are you able to reproduce this bug with a pure testing/bookworm or
sid/unstable system?  If so, please provide steps to reproduce, and
remove the moreinfo tag from this bug at that time.


Well the package are now in testing I guess due to the hard freeze.

Thnaks for replying. More later when I can put my hands back on the 
problematic config.


--eric

Bug#1035561: rust-kvm-bindings: don't build on armhf

[Gianfranco Costamagna]

Source: rust-kvm-bindings
Severity: serious
tags: patch
Version: 0.5.0-1.1

Hello, the package is missing a build dependency on librust-vmm-sys-util-dev.
Without it, it runtime-depend on the package and becames uninstallable on armhf,
where that package is not available.
Better to not build a deb that can't be installed.


diff -Nru rust-kvm-bindings-0.5.0/debian/changelog 
rust-kvm-bindings-0.5.0/debian/changelog
--- rust-kvm-bindings-0.5.0/debian/changelog2023-03-10 07:31:53.0 
+0100
+++ rust-kvm-bindings-0.5.0/debian/changelog2023-05-05 14:01:30.0 
+0200
@@ -1,3 +1,10 @@
+rust-kvm-bindings (0.5.0-1.2) unstable; urgency=medium
+
+  * Add BD on librust-vmm-sys-util-dev to make sure it builds only
+where that package is installable (Closes: #-1).
+
+ -- Gianfranco Costamagna   Fri, 05 May 2023 
14:01:30 +0200
+
 rust-kvm-bindings (0.5.0-1.1) unstable; urgency=medium
 
   * Non-maintainer upload.

diff -Nru rust-kvm-bindings-0.5.0/debian/control 
rust-kvm-bindings-0.5.0/debian/control
--- rust-kvm-bindings-0.5.0/debian/control  2022-09-27 02:22:22.0 
+0200
+++ rust-kvm-bindings-0.5.0/debian/control  2023-05-05 14:01:29.0 
+0200
@@ -5,7 +5,8 @@
  dh-cargo (>= 25),
  cargo:native ,
  rustc:native ,
- libstd-rust-dev 
+ libstd-rust-dev ,
+ librust-vmm-sys-util-dev (>= 0.11.1)
 Maintainer: Debian Rust Maintainers 

 Uploaders:
  nicoo 

G.


OpenPGP_signature
Description: OpenPGP digital signature

Bug#1035562: slurm-wlm: Package slurm-wlm-basic-plugins does not include /etc/slurm/plugstack.conf since commit e9e3e521

[Pierre-Emmanuel Le Roux]

Package: slurm-wlm
Version: slurm-wlm-basic-plugins
Severity: normal

Dear Maintainer,

since commit e9e3e521 
(https://salsa.debian.org/hpc-team/slurm-wlm/-/commit/e9e3e5211c76bacded1c0b55695f21545a2f48fa),
 package slurm-wlm-basic-plugins does not include /etc/slurm/plugstack.conf 
consequently files in /etc/slurm/plugstack.conf.d are ignored.

Thank you.

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

Kernel: Linux 5.15.0-70-generic (SMP w/128 CPU threads)
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 slurm-wlm depends on:
pn  slurm-client  
pn  slurmctld 
ii  slurmd22.05.8-3.1

slurm-wlm recommends no packages.

slurm-wlm suggests no packages.

Bug#1035560: unblock: calamares-settings-debian/12.0.9-1

[Jonathan Carter]

Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
X-Debbugs-Cc: calamares-settings-deb...@packages.debian.org, k...@debian.org
Control: affects -1 + src:calamares-settings-debian

Please unblock package calamares-settings-debian

[ Reason ]
The method that LUKS encryption tools (cryptsetup, cryptset-initramfs,
keyutils) have changed. Prior to bookworm, these were included in the squashfs
system, so it was installed whether or not it was required, resulting in a
warning on unencrypted systems when update-initramfs were run.

By some happy accident due to updates in the live build system, these aren't
included in the squashfs image anymore, so we've added it to the media package
pool so that it could be installed only when required. This Calamares change
will install the required package only when LUKS have been configured.

[ Impact ]
If this isn't accepted, users who installed via the Calamares installer on
live media will not be able to boot their systems until they install 
cryptsetup-initramfs (and potentially keyutils, depending on configuration)
from rescue media.

[ Tests ]
This package was tested manually on the latest live test build.

[ Risks ]
The fixes are trivial and has been tested, and once migrated, we'll test it
yet again asap on the latest installation media. We're also adding luks tests
to our standard live smoke testing to help catch a bug like this sooner in the
future.

[ 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 testing

[ DebDiff ]

"""
diff -Nru calamares-settings-debian-12.0.8/CHANGELOG 
calamares-settings-debian-12.0.9/CHANGELOG
--- calamares-settings-debian-12.0.8/CHANGELOG  2023-04-26 14:23:37.0 
+0200
+++ calamares-settings-debian-12.0.9/CHANGELOG  2023-05-04 20:34:51.0 
+0200
@@ -1,8 +1,15 @@
-[ 10.0.8 ]
+[ 12.0.9 ]
+
+ * Fix typos in version numbers for last two changelog entries
+ * Install cryptsetup-initramfs, cryptsetup and keyutils (only) when needed
+   (required due to these packages only now existing on package pool,
+not on the squashfs filesystem)
+
+[ 12.0.8 ]

  * Do grub work within the chroot

-[ 10.0.7 ]
+[ 12.0.7 ]

  * Enable os-prober /after/ grub has been installed.

diff -Nru calamares-settings-debian-12.0.8/debian/changelog 
calamares-settings-debian-12.0.9/debian/changelog
--- calamares-settings-debian-12.0.8/debian/changelog   2023-04-26 
14:25:34.0 +0200
+++ calamares-settings-debian-12.0.9/debian/changelog   2023-05-04 
20:47:17.0 +0200
@@ -1,3 +1,10 @@
+calamares-settings-debian (12.0.9-1) unstable; urgency=medium
+
+  * New upstream release
+- Deal with changes in how luks tools are installed from live media
+
+ -- Jonathan Carter   Thu, 04 May 2023 20:47:17 +0200
+
 calamares-settings-debian (12.0.8-1) unstable; urgency=medium

   * New upstream release
diff -Nru calamares-settings-debian-12.0.8/scripts/bootloader-config 
calamares-settings-debian-12.0.9/scripts/bootloader-config
--- calamares-settings-debian-12.0.8/scripts/bootloader-config  2023-04-26 
14:23:37.0 +0200
+++ calamares-settings-debian-12.0.9/scripts/bootloader-config  2023-05-04 
20:34:51.0 +0200
@@ -2,22 +2,24 @@

 CHROOT=$(mount | grep proc | grep calamares | awk '{print $3}' | sed -e 
"s#/proc##g")

-# Set secure permissions for the initramfs if we're configuring
+# Install luks utilities if needed.
+# Also, set secure permissions for the initramfs if we're configuring
 # full-disk-encryption. The initramfs is re-generated later in the
 # installation process so we only set the permissions snippet without
 # regenerating the initramfs right now:
 if [ "$(mount | grep $CHROOT" " | cut -c -16)" = "/dev/mapper/luks" ]; then
 echo "UMASK=0077" > 
$CHROOT/etc/initramfs-tools/conf.d/initramfs-permissions
+chroot $CHROOT apt-get -y install cryptsetup-initramfs cryptsetup keyutils
 fi

 echo "Running bootloader-config..."

 if [ -d /sys/firmware/efi/efivars ]; then
 echo " * Installing grub-efi (uefi)..."
-DEBIAN_FRONTEND=noninteractive chroot $CHROOT apt-get -y install 
grub-efi-amd64 cryptsetup keyutils
+DEBIAN_FRONTEND=noninteractive chroot $CHROOT apt-get -y install 
grub-efi-amd64
 else
 echo " * install grub... (bios)"
-DEBIAN_FRONTEND=noninteractive chroot $CHROOT apt-get -y install grub-pc 
cryptsetup keyutils
+DEBIAN_FRONTEND=noninteractive chroot $CHROOT apt-get -y install grub-pc
 fi

 # Re-enable os-prober:
"""

thanks,

-Jonathan

unblock calamares-settings-debian/12.0.9-1

Bug#1035559: rustc: Install cargo & rustc suggests wasi-libc but fails with 'Hash Sum mismatch'

[bud]

Package: rustc
Version: 1.63.0+dfsg1-2
Severity: normal
X-Debbugs-Cc: budheal...@gmail.com

Dear Maintainer,

   * What led up to the situation?
apt-get install cargo rust
suggested further packages (cargo-doc icu-doc ncurses-doc pkg-config 
llvm-14-doc python-pygments-doc ttf-bitstream-vera lld-14 clang-14)
and adding those apt-get suggested two more (clang-14-doc wasi-libc)
   * What exactly did you do (or not do) that was effective (or
 ineffective)?
Trying installing that passel fails on a hash error.
Trying installing everything except wasi-libc completed.
   * What was the outcome of this action?
An error message was printed:
Err:43 file:/mnt/RC2-1 bookworm/main amd64 wasi-libc all 
0.0~git20220510.9886d3d-2
  Hash Sum mismatch
  Hashes of expected file:
   - SHA256:513e25eeca77f7e31adf928b684714dd656cc6bc70c2970abfe3b4117e3b736f
   - MD5Sum:f030f748f6def3da7201064b66f3353f [weak]
   - Filesize:833952 [weak]
  Hashes of received file:
   - SHA256:735be269519fe9a359ea2c36a58423c4b7cf57b609dc0c6e77d0f54840df1e24
   - MD5Sum:1dc410fd478fd2d714e407580424454f [weak]
   - Filesize:833952 [weak]
  Last modification reported: Wed, 07 Dec 2022 20:13:53 +
E: Failed to fetch 
file:/mnt/RC2-1/pool/main/w/wasi-libc/wasi-libc_0.0%7egit20220510.9886d3d-2_all.deb
  Hash Sum mismatch
   Hashes of expected file:
- SHA256:513e25eeca77f7e31adf928b684714dd656cc6bc70c2970abfe3b4117e3b736f
- MD5Sum:f030f748f6def3da7201064b66f3353f [weak]
- Filesize:833952 [weak]
   Hashes of received file:
- SHA256:735be269519fe9a359ea2c36a58423c4b7cf57b609dc0c6e77d0f54840df1e24
- MD5Sum:1dc410fd478fd2d714e407580424454f [weak]
- Filesize:833952 [weak]
   Last modification reported: Wed, 07 Dec 2022 20:13:53 +
   * What outcome did you expect instead?
As shown above, I copied RC2 (DLBD using jigdo) into local storage for fast 
access
I did not try to compile or build the file.
I use the MIT mirror if it makes a difference.
-- System Information:
Debian Release: 12.0
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: amd64 (x86_64)

Kernel: Linux 6.1.0-7-amd64 (SMP w/20 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 rustc depends on:
ii  binutils  2.40-2
ii  gcc   4:12.2.0-3
ii  libc6 2.36-9
ii  libc6-dev [libc-dev]  2.36-9
ii  libgcc-s1 12.2.0-14
ii  libstd-rust-dev   1.63.0+dfsg1-2

Versions of packages rustc recommends:
ii  cargo0.66.0+ds1-1
ii  llvm-14  1:14.0.6-12

Versions of packages rustc suggests:
ii  clang-14  1:14.0.6-12
ii  lld-141:14.0.6-12

-- no debconf information

Bug#817285: Allow releasing security updates via PGP-signed control messages

[Emilio Pozuelo Monfort]

Control: forwarded -1 https://salsa.debian.org/ftp-team/dak/-/merge_requests/270

Hi,

On Wed, 09 Mar 2016 19:36:02 +0100 Moritz Muehlenhoff  wrote:

Package: ftp.debian.org
Severity: wishlist

This was discussed at one of the past security team meetings, but
there was never a bug for that:

(This is a first high level view, the exact requirements can be hashed
out later.)

Right now to release a security update one needs shell access on
security-master. It would be great to allow the release of a security
update via a PGP-signed control message (similar to how changes files
need to be signed to allow uploads).

The next step would then be an ACL mechanism where trusted DDs can be
granted the possibility to release DSAs on their own (after the
security team having acked the debdiff). (This also needs some tweaks
for the debian-security-announce moderation script, but that's
unrelated to this task.


There's now a MR at [1] that should address the ACL for dak. Feel free to 
comment if you have any feedback.


Cheers,
Emilio

[1] https://salsa.debian.org/ftp-team/dak/-/merge_requests/270

Bug#1035068: linux-image-6.1.0-7-amd64: occasionally no trackpad/trackpoint on resume from hibernate

[Rusty Grove]

Package: src:linux
Version: 6.1.25-1
Followup-For: Bug #1035068
X-Debbugs-Cc: rgr...@rsu20.org

I get mixed results in removing the systemd script. The trackpad looks good on
multiple resumes, but I've lost the trackpoint on both of my test machines, the
other running linux-image-6.1.0-7-amd64.
Thanks


-- Package-specific info:
** Version:
Linux version 6.1.0-8-amd64 (debian-ker...@lists.debian.org) (gcc-12 (Debian 
12.2.0-14) 12.2.0, GNU ld (GNU Binutils for Debian) 2.40) #1 SMP 
PREEMPT_DYNAMIC Debian 6.1.25-1 (2023-04-22)

** Command line:
root=LABEL=root rw quiet splash loglevel=1 rootfstype=btrfs add_efi_memmap 
workqueue.power_efficient=true initrd=\EFI\Debian\initrd.img

** Not tainted

** Kernel log:
[179995.203190] elan_i2c 14-0015: failed to read report data: -71
[179995.216999] elan_i2c 14-0015: failed to read report data: -71
[179995.223936] elan_i2c 14-0015: failed to read report data: -71
[179995.238153] elan_i2c 14-0015: failed to read report data: -71
[179995.244699] elan_i2c 14-0015: failed to read report data: -71
[179995.258890] elan_i2c 14-0015: failed to read report data: -71
[179995.265548] elan_i2c 14-0015: failed to read report data: -71
[179995.270830] IPv6: ADDRCONF(NETDEV_CHANGE): wlp0s20f3: link becomes ready
[179995.285774] wlp0s20f3: Limiting TX power to 36 (36 - 0) dBm as advertised 
by c8:b5:ad:5f:f9:f5
[179995.292975] elan_i2c 14-0015: failed to read report data: -71
[179995.307069] elan_i2c 14-0015: failed to read report data: -71
[179995.729556] elan_i2c 14-0015: failed to read report data: -71
[179995.874426] elan_i2c 14-0015: failed to read report data: -71
[179995.901949] elan_i2c 14-0015: failed to read report data: -71
[179996.033861] elan_i2c 14-0015: failed to read report data: -71
[17.723244] elan_i2c 14-0015: failed to read report data: -71
[17.737332] elan_i2c 14-0015: failed to read report data: -71
[17.744196] elan_i2c 14-0015: failed to read report data: -71
[17.751903] elan_i2c 14-0015: failed to read report data: -71
[17.771699] elan_i2c 14-0015: failed to read report data: -71
[180003.960083] elan_i2c 14-0015: failed to read report data: -71
[180003.994728] elan_i2c 14-0015: failed to read report data: -71
[180004.029347] elan_i2c 14-0015: failed to read report data: -71
[180004.063917] elan_i2c 14-0015: failed to read report data: -71
[180004.223466] elan_i2c 14-0015: failed to read report data: -71
[180004.230065] elan_i2c 14-0015: failed to read report data: -71
[180004.237131] elan_i2c 14-0015: failed to read report data: -71
[180004.250980] elan_i2c 14-0015: failed to read report data: -71
[180004.257827] elan_i2c 14-0015: failed to read report data: -71
[180004.271878] elan_i2c 14-0015: failed to read report data: -71
[180004.279561] elan_i2c 14-0015: failed to read report data: -71
[180004.286533] elan_i2c 14-0015: failed to read report data: -71
[180004.300450] elan_i2c 14-0015: failed to read report data: -71
[180004.307244] elan_i2c 14-0015: failed to read report data: -71
[180004.321301] elan_i2c 14-0015: failed to read report data: -71
[180004.328015] elan_i2c 14-0015: failed to read report data: -71
[180004.342220] elan_i2c 14-0015: failed to read report data: -71
[180004.348783] elan_i2c 14-0015: failed to read report data: -71
[180004.355784] elan_i2c 14-0015: failed to read report data: -71
[180004.369854] elan_i2c 14-0015: failed to read report data: -71
[180004.376599] elan_i2c 14-0015: failed to read report data: -71
[180004.390575] elan_i2c 14-0015: failed to read report data: -71
[180004.397392] elan_i2c 14-0015: failed to read report data: -71
[180004.404876] elan_i2c 14-0015: failed to read report data: -71
[180004.438931] elan_i2c 14-0015: failed to read report data: -71
[180004.445696] elan_i2c 14-0015: failed to read report data: -71
[180004.459539] elan_i2c 14-0015: failed to read report data: -71
[180004.487179] elan_i2c 14-0015: failed to read report data: -71
[180004.494323] elan_i2c 14-0015: failed to read report data: -71
[180004.508116] elan_i2c 14-0015: failed to read report data: -71
[180004.514950] elan_i2c 14-0015: failed to read report data: -71
[180004.528986] elan_i2c 14-0015: failed to read report data: -71
[180004.535680] elan_i2c 14-0015: failed to read report data: -71
[180004.549791] elan_i2c 14-0015: failed to read report data: -71
[180004.556494] elan_i2c 14-0015: failed to read report data: -71
[180004.563459] elan_i2c 14-0015: failed to read report data: -71
[180004.577342] elan_i2c 14-0015: failed to read report data: -71
[180004.584190] elan_i2c 14-0015: failed to read report data: -71
[180004.598268] elan_i2c 14-0015: failed to read report data: -71
[180004.604940] elan_i2c 14-0015: failed to read report data: -71
[180004.619025] elan_i2c 14-0015: failed to read report data: -71
[180004.625772] elan_i2c 14-0015: failed to read report data: -71
[180004.632765] elan_i2c 14-0015: failed to read report data: -71
[180004.646608] elan_i2c 14-0015: failed to read report data: -71

Bug#1034938: libocsigenserver-ocaml: missing Breaks+Replaces for libocsigenserver-ocaml-dev when upgrading from bullseye

[Stéphane Glondu]

Hi,

Le 27/04/2023 à 14:59, Helmut Grohne a écrit :

Attempting to unpack libocsigenserver-ocaml/5.0.1-1+b12 from Debian bookworm
on a minimal Debian bullseye with libocsigenserver-ocaml-dev/2.16.1-1+b3
installed, causes an unpack error from dpkg due to
/usr/lib/ocaml/ocsigenserver/ocsigenserver.cma being contained in both packages.

| (Reading database ... 12625 files and directories currently installed.)
| Preparing to unpack .../libocsigenserver-ocaml_5.0.1-1+b12_amd64.deb ...
| Unpacking libocsigenserver-ocaml (5.0.1-1+b12) over (2.16.1-1+b3) ...
| dpkg: error processing archive ./libocsigenserver-ocaml_5.0.1-1+b12_amd64.deb 
(--unpack):
|  trying to overwrite '/usr/lib/ocaml/ocsigenserver/ocsigenserver.cma', which 
is also in package libocsigenserver-ocaml-dev 2.16.1-1+b3
| dpkg-deb: error: paste subprocess was killed by signal (Broken pipe)
| Errors were encountered while processing:
|  ./libocsigenserver-ocaml_5.0.1-1+b12_amd64.deb


Please ensure that libocsigenserver-ocaml has sufficient Breaks and Replaces 
declarations.


I agree that doctrine says Breaks+Replaces are missing here, and I will 
fix that. However, I wonder how one would get the aforementioned error 
in practice.


In a minimal bullseye chroot with libocsigenserver-ocaml-dev installed, 
after adding bookworm to sources.list:

- "apt upgrade" does not attempt to upgrade libocsigenserver-ocaml
- "apt dist-upgrade" upgrades libocsigenserver-ocaml along with 
libocsigenserver-ocaml-dev, with no errors


This is the same outcome with the "fixed" libocsigenserver-ocaml.

Installing with "dpkg -i" does produce the error, but installing the 
fixed package with "dpkg -i" also produces an error.



Cheers,

--
Stéphane

Bug#1035558: libxml2-utils: xmllint ignores --output option and writes to stdout

[Tj]

Package: libxml2-utils

I've done some follow-up debugging (on upstream git) to be sure the 
problem seems to exist upstream - unless I'm severely misunderstanding 
what --output is supposed to do. Anyhow; the trace shows it reaches 
doXPathDump(). Note that 'buf' is hard-coded to use stdout. The call to 
xmlOutputBufferClose(buf) causes the output to be sent. In gdb I confirm 
'output' is set immediately after that:


$ gdb -directory /srv/NAS/Sunny/SourceCode/libxml2/libxml2 -args 
/srv/NAS/Sunny/SourceCode/libxml2/libxml2/.libs/xmllint --output 
test.txt --html --xpath '//div[contains(@class, 
'\''test'\'')]/div/ul/li/a/@href' xmllint-test.html


2038break;
(gdb) p output
$1 = 0x7fffe1d5 "test.txt"

xmllint.c:

static void doXPathDump(xmlXPathObjectPtr cur) {
switch(cur->type) {
case XPATH_NODESET: {
int i;
xmlNodePtr node;
#ifdef LIBXML_OUTPUT_ENABLED
xmlOutputBufferPtr buf;

if ((cur->nodesetval == NULL) || (cur->nodesetval->nodeNr 
<= 0)) {

if (!quiet) {
fprintf(stderr, "XPath set is empty\n");
}
break;
}
buf = xmlOutputBufferCreateFile(stdout, NULL);
if (buf == NULL) {
fprintf(stderr, "Out of memory for XPath\n");
progresult = XMLLINT_ERR_MEM;
return;
}
for (i = 0;i < cur->nodesetval->nodeNr;i++) {
node = cur->nodesetval->nodeTab[i];
xmlNodeDumpOutput(buf, NULL, node, 0, 0, NULL);
xmlOutputBufferWrite(buf, 1, "\n");
}
xmlOutputBufferClose(buf);

Bug#1035557: git-man: git-diff(1) man page: the three dots (...) are confusing

[Vincent Lefevre]

Package: git-man
Version: 1:2.40.1-1
Severity: normal

In the synopsis:

   git diff [] ... [--] [...]

In this line, three dots (...) appear twice, but with 2 completely
different meanings: the first one is a literal one, the second one
meaning one or more. Ditto at other places.

A different style should be used to differentiate them. A possibility,
now that Unicode is common, would be to use U+2026 HORIZONTAL ELLIPSIS
(…) to mean one or more.

-- System Information:
Debian Release: 12.0
  APT prefers unstable-debug
  APT policy: (500, 'unstable-debug'), (500, 'testing-security'), (500, 
'stable-updates'), (500, 'stable-security'), (500, 'unstable'), (500, 
'testing'), (500, 'stable'), (1, 'experimental')
merged-usr: no
Architecture: amd64 (x86_64)
Foreign Architectures: i386

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

-- no debconf information

-- 
Vincent Lefèvre  - Web: 
100% accessible validated (X)HTML - Blog: 
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)

Bug#1035543: init-system-helpers: bla bla

[Michael Biebl]

Am 05.05.23 um 11:14 schrieb Luca Boccassi:

On Fri, 05 May 2023 11:04:29 +0200 Andreas Beckmann 



This is a new systemd unit in package e2fsprogs.


It's not, both bullseye and bookworm ship this file in e2fsprogs. The 
difference is this


bullseye:
cat /lib/systemd/system/e2scrub_reap.service | tail -n 2
[Install]
WantedBy=default.target

bookworm
# cat /lib/systemd/system/e2scrub_reap.service | tail -n 2
[Install]
WantedBy=multi-user.target


I.e. it changed the target from default.target to multi-user.target.
i-s-h does not have support for removing obsolete enablement symlinks in 
such a case.



 If this failure is

actually e2fsprogs's fault by incorrectly using the helpers, please
reassign the bug there (with instructions how to do it correctly).


Isn't this a variation of
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1031695 ?



Doesn't look like it.


OpenPGP_signature
Description: OpenPGP digital signature

Bug#1021112:

[Marcus Werner]

Dear maintainer,

I've the same bug in debian bullseye, evolution 3.38.3-1+deb11u1 ,
Workaround to read my mails : Open it as "Als neue Nachricht
bearbeiten" (Edit as new message)

kind regards
M.WER

Bug#1035555: FAI examples do not manage non-free-firmware section

[Thomas Lange]

Package: fai-doc
Severity: important


The examples of the configuration scripts do not add the
non-free-firmware section into sources.list for bookworm and later
releases.

-- 
regards Thomas

Bug#1035546: python3-pip: pip install ignores explicit --prefix=/usr (even with --root)

[Martin Pitt]

Hello again,

I just locally reverted [1], and it's still the same, so that Debian patch
actually isn't to blame.

I also tried --prefix=/opt which then gets me /opt/local/{bin,lib}. So this
behaviour directly contradicts the --help documentation:

>  --prefix   Installation prefix where lib, bin and other
>  top-level folders are placed

It's also not about my local wheel --

rm -rf /tmp/i; python3 -m pip install --root=/tmp/i --prefix=/opt 
small-timer
find /tmp/i

again gives /tmp/i/opt/local/lib/python3.11/dist-packages/small_timer

So this "/local" thing is both sticky and hard to avoid..

Martin

[1] 
https://salsa.debian.org/python-team/packages/python-pip/-/blob/master/debian/patches/hands-off-system-packages.patch

Bug#1035553: evince does not store setting "Select page size using document page size"

[Simon IJskes]

Package: evince
Version: 42.3

https://bugs.launchpad.net/ubuntu/+source/evince/+bug/2018583

I reported it against ubuntu, but i saw it is also in the debian git HEAD.

Fix is included, should be easy to apply

Greetings,

Simon

--
create firmware without programming https://www.bendyroad.com

Bug#1035554: libxml2-utils: xmllint ignores --output option and writes to stdout

[Tj]

Package: libxml2-utils
Version: 2.9.10+dfsg-6.7+deb11u4
Severity: normal
Tags: upstream

xmllint is ignoring --output FILE option. I've done a debug run with gdb and it 
correctly reads the option and assigns its value to the 'output' variable but 
doesn't read that variable before writing the output. Confirmed with gdb's 
hardware watch `awatch output`. The final trace before the output is written to 
stdout is:

3701if (repeat) {   

   
(gdb) n 

   
3724nbregister = 0; 

   
(gdb) n 

   
3727if (stream != 0)

   
(gdb) n 

   
3731if (sax) {  

   
(gdb) n 

   
3734parseAndPrintFile(argv[i], NULL);



$ xmllint --output test.txt --html --xpath '//div[contains(@class, 
'\''test'\'')]/div/ul/li/a/@href' xmllint-test.html 
 href="test0.html"
 href="test1.html"
 href="test2.html"
 href="test3.html"
 href="test4.html"
 href="test5.html"
 href="test6.html"
 href="test7.html"
 href="test8.html"
 href="test9.html"

$ cat xmllint-test.html 


 
  
  xmllint test --output
 
 
  xmllint test --output
  
   

 test0
 test1
 test2
 test3
 test4
 test5
 test6
 test7
 test8
 test9

   
  
 


-- System Information:
Debian Release: 11.7
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 
'stable-debug'), (500, 'proposed-updates-debug'), (500, 'stable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Versions of packages libxml2-utils depends on:
ii  libc62.31-13+deb11u6
ii  libxml2  2.9.10+dfsg-6.7+deb11u4

libxml2-utils recommends no packages.

libxml2-utils suggests no packages.

Bug#1035546: python3-pip: pip install ignores explicit --prefix=/usr (even with --root)

[Martin Pitt]

Hello all,

Is that patch even necessary still? In Fedora with python3-pip 2.22.3,
`sudo pip install python-dbusmock` installs into
/usr/local/lib/python3.11/site-packages/dbusmock/ , i.e. does not conflict
with /usr any more. They do have a more targetted protection of /usr [1], but
no general path mangling in their other patches [2].

Thanks,

Martin

[1] 
https://src.fedoraproject.org/rpms/python-pip/blob/rawhide/f/remove-existing-dist-only-if-path-conflicts.patch
[2] https://src.fedoraproject.org/rpms/python-pip/tree/rawhide