Bug#1061421: Fails to start after an upgrade

[Arto Jantunen]

"Marc Dequènes (duck)"  writes:

> Quack,
>
> On 2024-05-08 09:40, Marc Dequènes wrote:
>
>> Not sure this is the same problem but I would say it's worth a try.
>> I'll prepare the package and let you know how it goes.
>
> I packaged and uploaded 0.5.0 and this bug is fixed for me now, but I'd like
> to hear from you all before closing this bug.

This version works for me.

-- 
Arto Jantunen

Bug#1070784: birdfont: unable to run

[Janusz S . Bień]

Package: birdfont
Version: 2.32.3-2
Severity: important
X-Debbugs-Cc: none, Janusz S. Bień 

Dear Maintainer,

I get

birdfont: symbol lookup error: /lib/x86_64-linux-gnu/libwebkit2gtk-4.0.so.37: 
undefined symbol: gst_transcoder_get_sync_signal_adapter

Yours

JSB

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

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

Versions of packages birdfont depends on:
ii  birdfont-common   2.32.3-2
ii  libc6 2.36-9+deb12u7
ii  libcairo-gobject2 1.16.0-7
ii  libcairo2 1.16.0-7
ii  libfontconfig12.14.1-4
ii  libfreetype6  2.12.1+dfsg-5
ii  libgdk-pixbuf-2.0-0   2.42.10+dfsg-1+b1
ii  libgee-0.8-2  0.20.6-1
ii  libglib2.0-0  2.74.6-2+deb12u1
ii  libgtk-3-03.24.38-2~deb12u1
ii  libnotify40.8.1-1
ii  libsqlite3-0  3.40.1-2
ii  libwebkit2gtk-4.0-37  2.42.5-1~deb12u1
ii  libxmlbird1   1.2.12-1

Versions of packages birdfont recommends:
ii  unicode-data  15.0.0-1

birdfont suggests no packages.

-- no debconf information

-- 
 ,   
Janusz S. Bien
emeryt (emeritus)
https://sites.google.com/view/jsbien

Bug#1070783: python3-gpumodules: fails to parse kernel version for +bpo debian backport kernels

[Tim Connors]

Package: python3-gpumodules
Version: 3.8.0-1
Severity: normal
Tags: patch

> uname -a
Linux dirac 6.6.13+bpo-amd64 #1 SMP PREEMPT_DYNAMIC Debian 6.6.13-1~bpo12+1 
(2024-02-15) x86_64 GNU/Linux

This seems to fix the problem and basic functionality appears to work:

--- /usr/lib/python3/dist-packages/GPUmodules/env.py.old2024-05-09 
13:07:32.387667230 +1000
+++ /usr/lib/python3/dist-packages/GPUmodules/env.py2024-05-09 
13:07:42.171546939 +1000
@@ -309,7 +309,7 @@
 
 # Check Linux Kernel version
 current_kversion_str = release()
-current_kversion = tuple([int(x) for x in re.sub('-.*', '', 
current_kversion_str).split('.')])
+current_kversion = tuple([int(x) for x in re.sub('[-+].*', '', 
current_kversion_str).split('.')])
 LOGGER.debug('Using Linux Kernel: %s', current_kversion_str)
 if current_kversion < __required_kversion__:
 print('Using Linux Kernel {}, but {} requires > {}.{}.'.format(



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

Kernel: Linux 6.6.13+bpo-amd64 (SMP w/16 CPU threads; PREEMPT)
Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.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-gpumodules depends on:
ii  lshw02.19.git.2021.06.19.996aaad9c7-2+b1
ii  python3 3.11.2-1+b1
ii  python3-matplotlib  3.6.3-1+b1
ii  python3-pandas  1.5.3+dfsg-2

python3-gpumodules recommends no packages.

Versions of packages python3-gpumodules suggests:
ii  ricks-amdgpu-utils  3.8.0-1

-- no debconf information

-- debsums errors found:
debsums: changed file /usr/lib/python3/dist-packages/GPUmodules/env.py (from 
python3-gpumodules package)

Bug#1056120: a different workaround

[McIntyre, Vincent (S, Marsfield)]

I found Sebastian's patch did not fix this for me.

A simpler change seems to have sorted it out though:

--- debian.cnf.orig 2024-05-09 12:02:59.845494238 +1000
+++ debian.cnf  2024-05-09 12:03:10.213564938 +1000
@@ -3,10 +3,12 @@
  host = localhost
  user = root
  password = 
+protocol = socket
  socket   = /var/run/mysqld/mysqld.sock
  [mysql_upgrade]
  host = localhost
  user = root
  password = 
+protocol = socket
  socket   = /var/run/mysqld/mysqld.sock
  basedir  = /usr

Kind regards
Vince

Bug#1069908: elpa-debian-el: X-Debbugs-Cc: is weirdly overpopulated with duplicate or broken entries

[Xiyue Deng]

Control: tags -1 +moreinfo +pending

Hi Daniel,

Daniel Kahn Gillmor  writes:

> Package: elpa-debian-el
> Version: 37.11
> Severity: normal
> X-Debbugs-Cc: none, d...@fifthhorseman.net, Daniel Kahn Gillmor 
> 
>
> When i do "M-x debian-bug P elpa-debian-el RET" i get the template you
> see here.
>
> Weirdly, X-Debbugs-Cc is pre-populated in this way.
>
> There are at least two things wrong with X-Debbugs-Cc here:
>
>  - the string "none" shouldn't be present.  This smells like a bug,
>where the empty string is somehow being misinterpreted as the string
>"none", but i odn't know where it's happening.
>
>

For this issue, it looks like debian-bug.el is passing "--list-cc=none"
to reportbug which then becomes part of the message.  This is fixed in
[1] and pending sponsoring.

>  - the two additional addresses are duplicative. Even if there is code
>that tries to re-add a duplicate address, it should notice that the
>e-mail address parts are identical, and coalesce them into a single
>address.
>

I cannot seem to reproduce this.  debian-bug.el tries to get full name
and email from several sources, such as user-full-name,
user-mail-address, envvars like DEBFULLNAME, DEBNAME, NAME, DEBEMAIL,
EMAIL, REPORTBUGEMAIL, etc.  So there may be something unconventional
that triggered this.  Can you check if your configuration set those info
in multiple places?  What happens if you clear some of them?

> I don't understand the codebase well enough to be able to see how these
> things are happening, but if you want me to test some changes, or report
> on any other config, please let me know.
>
>--dkg
>

[1] 
https://salsa.debian.org/emacsen-team/debian-el/-/commit/116b3e7c839bf52fa01adba0758487a47cade87a

-- 
Xiyue Deng


signature.asc
Description: PGP signature

Bug#1070782: nmu: gtk4_4.12.5+dfsg-6

[plugwash]

Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: binnmu

As discussed in bug 1070706 gtk4 was built against a version of libpng1.6
suffering from bug 1066069, which resulted in libgtk-4-1-udeb depending on
libpng16-16t64-udeb which does not exist. This prevents gtk4 migrating to
testing, which leaves a bunch of packages uninstallable in testing on time64
architectures.

Please can you schedule a rebuild.

nmu gtk4_4.12.5+dfsg-6 . ANY . unstable . -m "rebuild with #1066069 fixed"

-- System Information:
Debian Release: 10.13
  APT prefers oldoldstable-updates
  APT policy: (500, 'oldoldstable-updates'), (500, 'oldoldstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386, arm64

Kernel: Linux 4.19.0-18-amd64 (SMP w/4 CPU cores)
Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_GB:en (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Bug#1070781: No beep after a (hot) reboot

[Bjarni Ingi Gislason]

Package: beep
Version: 1.4.9-1.1
Severity: normal

Dear Maintainer,

   * What led up to the situation?

  Issuing 'beep' after a reboot, either after 'fsck' found
something to be corrected or after a reboot with 'shutdown -r
now'

   * What was the outcome of this action?

  No beep (sound)

   * What outcome did you expect instead?

  The sound of a beep

  This was originally sent as a bug report #1015004 to
'linux-source' 15th July 2022.

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

Kernel: Linux 6.7.12-amd64 (SMP w/2 CPU threads; PREEMPT)
Locale: LANG=is_IS.iso88591, LC_CTYPE=is_IS.iso88591 (charmap=ISO-8859-1), 
LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: sysvinit (via /sbin/init)

Versions of packages beep depends on:
ii  libc6  2.38-7

beep recommends no packages.

beep suggests no packages.

-- no debconf information

Bug#1070778: [Debian-astro-maintainers] Bug#1070778: indi-armadillo-platypus: Add Appstream metainfo announcing HW support

[Thorsten Alteholz]

Hi Petter,

thanks a lot for this patch, the Appstream stuff is like a book of seven 
seals for me.


On Thu, 9 May 2024, Petter Reinholdtsen wrote:

+
+  com.github.indilib.indi-3rdparty


There are lots of drivers in this repository, distributed over several 
packages. Shouldn't there be a unique id for each package?


  Thorsten

Bug#1070780: adduser: Warnung: Auf das von Ihnen angegebene Home-Verzeichnis /run/inadyn kann nicht zugegriffen werden: No such file or directory

[Al Ma]

Package: inadyn
Version: 2.10.0-1
$ sudo aptitude install inadyn
[sudo] Passwort für username:
Die folgenden NEUEN Pakete werden zusätzlich installiert:
inadyn libconfuse-common{a} libconfuse2{a}
0 Pakete aktualisiert, 3 zusätzlich installiert, 0 werden entfernt und 4 nicht 
aktualisiert.
126 kB an Archiven müssen heruntergeladen werden. Nach dem Entpacken werden 338 
kB zusätzlich belegt sein.
Möchten Sie fortsetzen? [Y/n/?] Y
Holen: 1 http://debian.mirror.lrz.de/debian stable/main amd64 libconfuse-common 
all 3.3-3 [13,4 kB]
Holen: 2 http://debian.mirror.lrz.de/debian stable/main amd64 libconfuse2 amd64 
3.3-3 [33,3 kB]
Holen: 3 http://debian.mirror.lrz.de/debian stable/main amd64 inadyn amd64 
2.10.0-1 [79,0 kB]
126 kB wurden in 0 s heruntergeladen (328 kB/s)
Vormals nicht ausgewähltes Paket libconfuse-common wird gewählt.
(Lese Datenbank ... 516782 Dateien und Verzeichnisse sind derzeit installiert.)
Vorbereitung zum Entpacken von .../libconfuse-common_3.3-3_all.deb ...
Entpacken von libconfuse-common (3.3-3) ...
Vormals nicht ausgewähltes Paket libconfuse2:amd64 wird gewählt.
Vorbereitung zum Entpacken von .../libconfuse2_3.3-3_amd64.deb ...
Entpacken von libconfuse2:amd64 (3.3-3) ...
Vormals nicht ausgewähltes Paket inadyn wird gewählt.
Vorbereitung zum Entpacken von .../inadyn_2.10.0-1_amd64.deb ...
Entpacken von inadyn (2.10.0-1) ...
libconfuse-common (3.3-3) wird eingerichtet ...
libconfuse2:amd64 (3.3-3) wird eingerichtet ...
inadyn (2.10.0-1) wird eingerichtet ...
adduser: Warnung: Auf das von Ihnen angegebene Home-Verzeichnis /run/inadyn 
kann nicht zugegriffen werden: No such file or directory
Trigger für man-db (2.11.2-2) werden verarbeitet ...
Trigger für libc-bin (2.36-9+deb12u7) werden verarbeitet ...
$ sudo ls /run/inadyn
ls: Zugriff auf '/run/inadyn' nicht möglich: Datei oder Verzeichnis nicht 
gefunden
«No such file or directory» doesn't sound good. Any error anywhere?

Bug#1070779: boomaga: does not send printjob to real printer

[Michael Schmitt]

Package: boomaga
Version: 3.0.0-1+b1
Severity: normal
X-Debbugs-Cc: ms.b...@web.de

Dear Maintainer,

* What led up to the situation?
moved from Xubuntu 20.04 to debian bookworm (XFCE). Fresh install. boomaga does
not print to attached real printer. The same hardware worked with Xubuntu
20.04.

* What exactly did you do (or not do) that was effective (or ineffective)?
nothing. Worked in XUbuntu out of the box. No idea, whats going wrong. Printing
to boomage leads to 'boomaga starts and shows document'. Printer is configured.
Pressing 'Print and Close' closes the window and nothing gets printed. Nothing
appears in real printers printing queue. (Printing directly to the printer
instead via boomaga works.)

* What was the outcome of this action?
no print output

* What outcome did you expect instead?
the attached and configured printer should print the document and boomaga
window should close.



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

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

Versions of packages boomaga depends on:
ii  cups 2.4.2-3+deb12u5
ii  libc62.36-9+deb12u7
ii  libcups2 2.4.2-3+deb12u5
ii  libgcc-s1 [libgcc1]  12.2.0-14
ii  libpoppler-cpp0v522.12.0-2+b1
ii  libqt5core5a 5.15.8+dfsg-11
ii  libqt5dbus5  5.15.8+dfsg-11
ii  libqt5gui5   5.15.8+dfsg-11
ii  libqt5printsupport5  5.15.8+dfsg-11
ii  libqt5widgets5   5.15.8+dfsg-11
ii  libstdc++6   12.2.0-14
ii  zlib1g   1:1.2.13.dfsg-1

boomaga recommends no packages.

boomaga suggests no packages.

-- no debconf information

Bug#1070773: libglib2.0-dev: dependency on python seems broken for multi-arch?

[Simon McVittie]

On Wed, 08 May 2024 at 23:24:57 +0200, Christian Klein wrote:
> I install both the i386 and amd64 version for multi-arch support.
> 
> With the newest versions, a dependency to python was added.
> 
> Unfortunately, the package has two dependencies for python:
> "python3:any"
> and
> "python3 | qemu-user | qemu-user-static".
> 
> While python3:any is satisfied by the amd64 version of python, the second the
> second dependency  resolves to "python3:i386", which is not co-installable 
> with
> python:amd64.
> So, I now have to install qemu-user as dependency, which comes with a few 
> other
> heavy dependencies. Is this really needed, and how does that help at all?

Yes this is really needed, and it was not added just to spite you.

In general, qemu is required to be able to run GObject-Introspection tools
on cross-compiling architectures (which were packaged separately in older
versions of GLib, but are part of GLib itself in 2.80.x). Some of the
GObject-Introspection tools are required to be of the same architecture
as the typelib they are handling, and using an amd64 tool to load a
non-amd64 typelib will cause bugs.

The dependency on python3 | qemu-user is to avoid needing to pull in
qemu-user in the common case where only one architecture is relevant
(libglib2.0-dev:amd64 on amd64).

For the special case of i386 on an amd64 system, qemu is usually not
actually needed because amd64 systems can nearly always run i386 binaries
directly (although I believe there are kernel configurations that will
not allow that), but it's not obvious how to express that conditional
dependency in apt syntax.

Tested patches welcome, but my understanding is that all
the obvious ideas like
"Depends: python3 | python3:amd64 [i386] | qemu-user | qemu-user-static"
are not suitable, because explicit cross-architecture dependencies like
that one are not supported by the multiarch specification or the Debian
archive software.

If someone designs and implements the can-run-arch or cross-exe-wrapper
interfaces sketched in
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1030223#37 then I
believe that would give libglib2.0-dev:i386 a way to be installable on
amd64 without needing qemu-user. If you are interested in doing this,
please talk to the debian-cross team to make sure that the design is
sound. Until something like that happens, I am not aware of a better
approach.

smcv

Bug#1070778: indi-armadillo-platypus: Add Appstream metainfo announcing HW support

[Petter Reinholdtsen]

Package: indi-armadillo-platypus
Version: 1.0+20221226082641-2
Tags: patch

Here is a patch for indi-armadillo-platypus to add Appstream metainfo
XML announcing the hardware handled by this package.

Including this information in the package will ensure programs mapping
hardware to packages using Appstream information, like the isenkram
package, will know that this package is useful on machines where the USB
IDs are discovered.  It will also solve the
appstream-metadata-missing-modalias-provide lintian issue.

diff --git a/debian/com.github.indilib.indi-3rdparty.metainfo.xml 
b/debian/com.github.indilib.indi-3rdparty.metainfo.xml
new file mode 100644
index 000..48bfdf6
--- /dev/null
+++ b/debian/com.github.indilib.indi-3rdparty.metainfo.xml
@@ -0,0 +1,16 @@
+
+
+  com.github.indilib.indi-3rdparty
+  MIT
+  indi-armadillo-platypus
+  INDI driver for Lunatico Astronomia Armadillo and Platypus
+  
+This package contains the INDI driver for Armadillo and
+Playtypus from Lunatico Astronomia.
+This driver is compatible with any INDI client such as KStars
+or Xephem.
+  
+  
+usb:v16C0p09B1d*
+  
+
diff --git a/debian/indi-armadillo-platypus.install 
b/debian/indi-armadillo-platypus.install
new file mode 100644
index 000..ee3cc69
--- /dev/null
+++ b/debian/indi-armadillo-platypus.install
@@ -0,0 +1 @@
+debian/com.github.indilib.indi-3rdparty.metainfo.xml usr/share/metainfo

Bug#1070775: gnome-shell: Update gnome-shell from testing to unstable looses umlauts

[Simon McVittie]

Control: reassign -1 libglib2.0-0 2.80.0-10
Control: affects -1 + gnome-shell
Control: fixed -1 2.80.1-1

On Wed, 08 May 2024 at 23:10:19 +0200, Thomas Renard wrote:
> updating from testing version of gnome-shell to unstable version (44.9-2) 
> looses the
> umlauts of a german keyboard.

This is not a gnome-shell bug, this is a regression in the libglib2.0-0
security fix that you installed at the same time. Specifically, it's the
same bug as #1070730, #1070736, #1070743, #1070745, #1070749 and #1070752.
Please upgrade libglib2.0-0 to 2.80.1-1 which should become available
on your mirror soon.

smcv

Bug#1070777: onscripter: Please use the same build dependencies on all architectures

[Adrian Bunk]

Package: onscripter
Version: 20220816-1
Severity: normal

Build-Depends: ...
   libvorbis-dev [!arm64 !armel !armhf !mips !mipsel],
   libvorbisidec-dev [arm64 armel armhf mips mipsel],
   libsmpeg-dev [!arm64 !armel !armhf !mips !mipsel],
   libmad0-dev [arm64 armel armhf mips mipsel],
...


mips and mipsel are no longer built in unstable.

Using libvorbisidec on armhf or arm64 sounds wrong, these
architectures do have an FPU in their baseline.

Using libvorbisidec on armel sounds justifiable since there
is not FPU in the baseline, but since it's unlikely that there
are actual users of this package (left) on armel it might be
an option to also use libvorbis there.

I don't see a good justification for libmad0 instead of libsmpeg,
especially on arm64 which has quite powerful processors
(e.g. in some Lenovo laptops).

Bug#1070776: android-sdk: Update Appstream metainfo XML modalias list

[Petter Reinholdtsen]

Package: android-sdk
Version: 28.0.2+10
Tags: patch

The list of hardware handled in the udev rule has been extended, but the
list of handled USB devices listed in the Appstream metainfo XML has not
been similarly updated.

This patch bring the two files in sync.  Please apply to a future upload
to solve the appstream-metadata-missing-modalias-provide lintian issue.

diff --git a/debian/android-sdk.metainfo.xml b/debian/android-sdk.metainfo.xml
index 346b2a0..3709402 100644
--- a/debian/android-sdk.metainfo.xml
+++ b/debian/android-sdk.metainfo.xml
@@ -22,42 +22,181 @@
 USB
   
   
+usb:v0409p0300d*
 usb:v0451pD00Fd*
 usb:v0451pD010d*
+usb:v045Ep0C26d*
 usb:v0489pC001d*
+usb:v04E8p6601d*
+usb:v04E8p6640d*
+usb:v04E8p681Cd*
+usb:v04E8p685Dd*
+usb:v04E8p685Ed*
+usb:v04E8p6860d*
+usb:v04E8p6864d*
+usb:v04E8p6866d*
+usb:v04E8p686Cd*
+usb:v04E8p6877d*
+usb:v04E8p689Ed*
+usb:v04E8p68A9d*
+usb:v04E8p68C3d*
 usb:v0502p3202d*
 usb:v0502p3203d*
 usb:v0502p3325d*
+usb:v0502p33CBd*
 usb:v0502p3604d*
+usb:v05C6p0001d*
+usb:v05C6p6765d*
 usb:v05C6p6769d*
+usb:v05C6p676Cd*
+usb:v05C6p900Ed*
+usb:v05C6p9011d*
 usb:v05C6p901Dd*
 usb:v05C6p9025d*
+usb:v05C6p9091d*
+usb:v05C6p90BBd*
+usb:v05C6p90DCd*
+usb:v05C6pF003d*
 usb:v05E0p2101d*
+usb:v05E0p2106d*
+usb:v0955p7000d*
+usb:v0955p7100d*
+usb:v0955pB442d*
+usb:v0955pCF05d*
+usb:v0955pCF09d*
+usb:v0A5CpE681d*
 usb:v0B05p179Ed*
 usb:v0B05p179Fd*
 usb:v0B05p17A1d*
 usb:v0B05p4C80d*
+usb:v0B05p4C81d*
 usb:v0B05p4C90d*
 usb:v0B05p4C91d*
 usb:v0B05p4CA0d*
 usb:v0B05p4CA1d*
+usb:v0B05p4CC1d*
+usb:v0B05p4CD1d*
+usb:v0B05p4CE1d*
 usb:v0B05p4D00d*
 usb:v0B05p4D01d*
 usb:v0B05p4DAFd*
+usb:v0B05p4E1Fd*
 usb:v0B05p5410d*
 usb:v0B05p5412d*
 usb:v0B05p550Fd*
+usb:v0B05p581Fd*
+usb:v0B05p583Fd*
+usb:v0B05p5F03d*
+usb:v0B05p5F05d*
+usb:v0B05p5F07d*
+usb:v0B05p7030d*
+usb:v0B05p7770d*
+usb:v0B05p7771d*
 usb:v0B05p7772d*
 usb:v0B05p7773d*
 usb:v0B05p7774d*
 usb:v0B05p7775d*
 usb:v0B05p7776d*
 usb:v0B05pd*
+usb:v0B05p7781d*
+usb:v0BB4p0001d*
+usb:v0BB4p05FDd*
+usb:v0BB4p060Bd*
+usb:v0BB4p061Ad*
+usb:v0BB4p0C01d*
+usb:v0BB4p0C02d*
+usb:v0BB4p0C03d*
+usb:v0BB4p0C86d*
+usb:v0BB4p0C87d*
+usb:v0BB4p0C8Bd*
+usb:v0BB4p0C8Dd*
+usb:v0BB4p0C91d*
+usb:v0BB4p0C93d*
+usb:v0BB4p0C96d*
+usb:v0BB4p0C99d*
+usb:v0BB4p0C9Ad*
+usb:v0BB4p0C9Ed*
+usb:v0BB4p0CA2d*
+usb:v0BB4p0CA5d*
+usb:v0BB4p0CABd*
+usb:v0BB4p0CB2d*
+usb:v0BB4p0CD6d*
+usb:v0BB4p0CE5d*
+usb:v0BB4p0DEAd*
+usb:v0BB4p0DFFd*
+usb:v0BB4p0E03d*
+usb:v0BB4p0E31d*
+usb:v0BB4p0E32d*
+usb:v0BB4p0EBDd*
+usb:v0BB4p0F25d*
+usb:v0BB4p0F5Fd*
+usb:v0BB4p0F60d*
+usb:v0BB4p0F63d*
+usb:v0BB4p0F64d*
+usb:v0BB4p0F87d*
+usb:v0BB4p0FB4d*
+usb:v0BB4p0FB5d*
+usb:v0BB4p0FF0d*
+usb:v0BB4p0FF9d*
+usb:v0BB4p0FFFd*
+usb:v0BB4p2008d*
+usb:v0BB4p200Bd*
+usb:v0BB4p6860d*
 usb:v0C2Ep0BA3d*
+usb:v0CA6pA051d*
+usb:v0DA4p000Bd*
+usb:v0DA4p0010d*
 usb:v0E79p1411d*
 usb:v0E79p1417d*
 usb:v0E79p1549d*
+usb:v0E8Dp2005d*
+usb:v0E8Dp200Ad*
+usb:v0E8Dp200Cd*
+usb:v0E8Dp201Cd*
+usb:v0E8Dp201Dd*
+usb:v0E8Dp2048d*
 usb:v0FCAp8042d*
+usb:v0FCEp0166d*
+usb:v0FCEp0186d*
+usb:v0FCEp01AFd*
+usb:v0FCEp01BBd*
+usb:v0FCEp01F4d*
+usb:v0FCEp020Dd*
+usb:v0FCEp0DDEd*
+usb:v0FCEp2137d*
+usb:v0FCEp2138d*
+usb:v0FCEp2149d*
+usb:v0FCEp414Fd*
+usb:v0FCEp5169d*
+usb:v0FCEp5176d*
+usb:v0FCEp5192d*
+usb:v0FCEp519Cd*
+usb:v0FCEp51A7d*
+usb:v0FCEp51BAd*
+usb:v0FCEp51C9d*
+usb:v0FCEp51E7d*
+usb:v0FCEp614Fd*
+usb:v0FCEp6156d*
+usb:v0FCEp6195d*
+usb:v0FCEpB00Bd*
+usb:v1004p618Cd*
+usb:v1004p618Ed*
+usb:v1004p618Fd*
+usb:v1004p61A6d*
+usb:v1004p61B4d*
+usb:v1004p61F1d*
+usb:v1004p61F9d*
+usb:v1004p627Fd*
+usb:v1004p6300d*
+usb:v1004p6315d*
+usb:v1004p631Cd*
+usb:v1004p631Dd*
+usb:v1004p631Ed*
+usb:v1004p631Fd*
+usb:v1004p633Ed*
+usb:v1004p6344d*
+usb:v1004p6348d*
+usb:v10D6p0C02d*
 usb:v12D1p1021d*
 usb:v12D1p1038d*
 usb:v12D1p103Ad*
@@ -68,17 +207,94 @@
 usb:v12D1p107Dd*
 usb:v12D1p107Ed*
 usb:v12D1p1C2Cd*
+usb:v1532p9050d*
+usb:v1532p9051d*
+usb:v1768p0007d*
+usb:v1768p000Ed*
+usb:v1768p0011d*
+usb:v1768p0013d*
+usb:v1768p4EE7d*
+usb:v1782p4002d*
+usb:v1782p4003d*
+usb:v18D1p0D02d*
+usb:v18D1p0FFFd*
+usb:v18D1p2C11d*
+usb:v18D1p2D00d*
+usb:v18D1p2D01d*
+usb:v18D1p2D03d*
+usb:v18D1p2D05d*
+usb:v18D1p4E11d*
+usb:v18D1p4E12d*
+

Bug#1070774: hamexam: update question pool

[John Nogatch]

The latest version hamexam 1.11 is available at:
https://launchpad.net/~jnogatch/+archive/ubuntu/hamexam

On Wed, May 8, 2024 at 9:33 PM Austen, Jeffrey  wrote:
>
> Package: hamexam
> Version: 1.10.1-1
> Severity: wishlist
>
> Please update the extra class question pool. The new pool takes effect
> July 1, 2024.
> https://www.ncvec.org/index.php/2024-2028-extra-class-question-pool-release

Bug#1070775: gnome-shell: Update gnome-shell from testing to unstable looses umlauts

[Thomas Renard]

Package: gnome-shell
Version: 44.9-1+b1
Severity: normal

Dear Maintainer,

updating from testing version of gnome-shell to unstable version (44.9-2) 
looses the
umlauts of a german keyboard.

- you are in testing with gnome-shell - 44.9-1 - and install unstable
version.
- Reboot
- Log into gnome session (though umlauts do not work in gdm too!)
- type uiopüöälß with the german keyboard e.g. in a shell

expected:

uiopüöälß is shown

actual:

uiopl is shown. All umlaut keys are ignored

Downgrading to the actual testing packages let the umlauts work again.

From apt/history:

Start-Date: 2024-05-08  20:53:41
Commandline: apt install -t unstable gnome-shell
Requested-By: baer (1000)
Install: libgirepository-2.0-0:arm64 (2.80.0-10, automatic)
Upgrade: libglib2.0-dev-bin:arm64 (2.78.4-7, 2.80.0-10), libglib2.0-bin:arm64 
(2.78.4-7, 2.80.0-10), libglib2.0-dev:arm64 (2.78.4-7, 2.80.0-10), 
gir1.2-glib-2.0:arm64 (1.78.1-15, 2.80.0-10), libglib2.0-data:arm64 (2.78.4-7, 
2.80.0-10), gnome-shell:arm64 (44.9-1+b1, 44.9-2), gir1.2-glib-2.0-dev:arm64 
(1.78.1-15, 2.80.0-10), gnome-shell-common:arm64 (44.9-1, 44.9-2), 
gnome-shell-extension-prefs:arm64 (44.9-1+b1, 44.9-2), libglib2.0-0t64:arm64 
(2.78.4-7, 2.80.0-10)
End-Date: 2024-05-08  20:53:47

-- System Information:
Debian Release: trixie/sid
  APT prefers testing
  APT policy: (900, 'testing')
Architecture: arm64 (aarch64)

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

Versions of packages gnome-shell depends on:
ii  dconf-gsettings-backend [gsettings-backend]  0.40.0-4+b2
ii  gir1.2-accountsservice-1.0   23.13.9-6.1
ii  gir1.2-adw-1 1.5.0-1
ii  gir1.2-atk-1.0   2.52.0-1
ii  gir1.2-atspi-2.0 2.52.0-1
ii  gir1.2-freedesktop   1.78.1-15
ii  gir1.2-gcr-4 4.2.0-5
ii  gir1.2-gdesktopenums-3.0 46.0-1
ii  gir1.2-gdkpixbuf-2.0 2.42.10+dfsg-3+b3
ii  gir1.2-gdm-1.0   46.0-2+b3
ii  gir1.2-geoclue-2.0   2.7.1-2+b1
ii  gir1.2-glib-2.0  1.78.1-15
ii  gir1.2-gnomebg-4.0 3   44.0-5
ii  gir1.2-gnomebluetooth-3.046.0-1
ii  gir1.2-gnomedesktop-4.0  44.0-5
ii  gir1.2-graphene-1.0  1.10.8-3+b1
ii  gir1.2-gstreamer-1.0 1.24.3-1
ii  gir1.2-gtk-4.0   4.12.5+ds-3
ii  gir1.2-gweather-4.0  4.4.2-1
ii  gir1.2-ibus-1.0  1.5.29-2
ii  gir1.2-mutter-12 44.8-3.1+b3
ii  gir1.2-nm-1.01.46.0-2
ii  gir1.2-nma4-1.0  1.10.6-3
ii  gir1.2-pango-1.0 1.52.2+ds-1
ii  gir1.2-polkit-1.0124-2
ii  gir1.2-rsvg-2.0  2.58.0+dfsg-1
ii  gir1.2-soup-3.0  3.4.4-5+b1
ii  gir1.2-upowerglib-1.01.90.3-1
ii  gir1.2-webkit2-4.1   2.44.1-1+b1
ii  gnome-backgrounds45.0-1
ii  gnome-settings-daemon46.0-1+b3
ii  gnome-shell-common   44.9-1
ii  gsettings-desktop-schemas46.0-1
ii  gstreamer1.0-pipewire1.0.5-1+b3
ii  libatk-bridge2.0-0t642.52.0-1
ii  libatk1.0-0t64   2.52.0-1
ii  libc62.38-7
ii  libcairo21.18.0-3+b1
ii  libecal-2.0-2t64 3.50.3-2.2+b3
ii  libedataserver-1.2-27t64 3.50.3-2.2+b3
ii  libgcr-4-4   4.2.0-5
ii  libgdk-pixbuf-2.0-0  2.42.10+dfsg-3+b3
ii  libgirepository-1.0-11.78.1-15
ii  libgjs0g 1.80.2-1
ii  libgles2 1.7.0-1+b1
ii  libglib2.0-0t64  2.78.4-7
ii  libglib2.0-bin   2.78.4-7
ii  libgnome-autoar-0-0  0.4.4-2+b2
ii  libgnome-desktop-4-2t64  44.0-5
ii  libgraphene-1.0-01.10.8-3+b1
ii  libgtk-3-0t643.24.41-4
ii  libgtk-4-1   4.12.5+ds-3
ii  libical3t64  3.0.17-1.1+b1
ii  libjson-glib-1.0-0   1.8.0-2+b1
ii  libmutter-12-0t6444.8-3.1+b3
ii  libnm0  

Bug#1070774: hamexam: update question pool

[Austen, Jeffrey]

Package: hamexam
Version: 1.10.1-1
Severity: wishlist

Please update the extra class question pool. The new pool takes effect 
July 1, 2024.
https://www.ncvec.org/index.php/2024-2028-extra-class-question-pool-release

Bug#1070773: libglib2.0-dev: dependency on python seems broken for multi-arch?

[Christian Klein]

Package: libglib2.0-dev
Version: 2.80.0-10
Severity: normal
X-Debbugs-Cc: dvl...@gmail.com

I install both the i386 and amd64 version for multi-arch support.

With the newest versions, a dependency to python was added.

Unfortunately, the package has two dependencies for python:
"python3:any"
and
"python3 | qemu-user | qemu-user-static".

While python3:any is satisfied by the amd64 version of python, the second the
second dependency  resolves to "python3:i386", which is not co-installable with
python:amd64.
So, I now have to install qemu-user as dependency, which comes with a few other
heavy dependencies. Is this really needed, and how does that help at all?


-- System Information:
Debian Release: trixie/sid
  APT prefers unstable
  APT policy: (999, 'unstable'), (998, 'testing'), (990, 'stable'), (500, 
'unstable-debug'), (500, 'testing-debug'), (500, 'proposed-updates'), (350, 
'experimental'), (1, 'experimental-debug')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

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

Versions of packages libglib2.0-dev depends on:
ii  libc6  2.38-8
ii  libffi-dev 3.4.6-1
ii  libffi83.4.6-1
ii  libgirepository-2.0-0  2.80.0-10
ii  libglib2.0-0t642.80.0-10
ii  libglib2.0-bin 2.80.0-10
ii  libglib2.0-dev-bin [libglib2.0-dev-bin-linux]  2.80.0-10
ii  libmount-dev   2.40-8
ii  libpcre2-dev   10.42-4+b1
ii  libselinux1-dev3.5-2+b2
ii  libsysprof-capture-4-dev   46.0-1
ii  pkgconf1.8.1-1+b2
ii  python33.11.8-1
ii  qemu-user  1:8.2.3+ds-2
ii  zlib1g-dev 1:1.3.dfsg-3.1

libglib2.0-dev recommends no packages.

Versions of packages libglib2.0-dev suggests:
ii  gir1.2-glib-2.0-dev  2.80.0-10
pn  libglib2.0-doc   

-- no debconf information

Bug#1062761: transition: libfm-qt

[Sebastian Ramacher]

Control: tags -1 confirmed

On 2024-02-03 09:57:00 +0800, ChangZhuo Chen wrote:
> Package: release.debian.org
> Severity: normal
> User: release.debian@packages.debian.org
> Usertags: transition
> X-Debbugs-Cc: libfm...@packages.debian.org
> Control: affects -1 + src:libfm-qt
> 
> libfm-qt has bumped its soversion from 13 to 14, so we need a
> transition.
> 
> All affected packages listed in 
> https://release.debian.org/transitions/html/auto-libfm-qt.html
> are good in experimental.

Please go ahead.

Cheers
-- 
Sebastian Ramacher

Bug#1062666: transition: openmm

[Sebastian Ramacher]

Control: tags -1 confirmed

On 2024-02-02 16:57:16 +0200, Andrius Merkys wrote:
> Package: release.debian.org
> Severity: normal
> User: release.debian@packages.debian.org
> Usertags: transition
> 
> Hello,
> 
> I would like to request a transition slot for openmm
> (experimental -> unstable) due to soname bump. Current ben tracker [1]
> is OK.
> 
> All reverse dependencies rebuild fine, except for cpptraj which is not in
> testing.

Please go ahead.

Cheers
-- 
Sebastian Ramacher

Bug#1070462: transition: evolution-data-server 3.52

[Sebastian Ramacher]

Control: tags -1 confirmed

On 2024-05-05 13:00:06 -0400, Jeremy Bícha wrote:
> Package: release.debian.org
> User: release.debian@packages.debian.org
> Usertags: transition
> X-Debbugs-Cc: evolution-data-ser...@packages.debain.org
> 
> One of the evolution-data-server libraries had a soname bump. I
> believe everything should be binNMUable without issue.

Please go ahead

Cheers
-- 
Sebastian Ramacher

Bug#1068684: For arm64 -ffp-contract=off helps

[Steve Capper]

Hello,
FWIW, adding -ffp-contract=off to CFLAGS and CXXFLAGS appears to fix the build 
s.t the unit tests on arm64 pass and the package builds successfully.

Cheers,
--
Steve Capper

Bug#1070772: ITP: python-mutf8 -- encoders and decoders for the MUTF-8 character encoding

[Alexandre Detiste]

Package: wnpp
Severity: wishlist
Owner: Alexandre Detiste 
X-Debbugs-Cc: debian-de...@lists.debian.org, debian-pyt...@lists.debian.org

* Package name: python-mutf8
  Version : 1.0.0
  Upstream Contact: Tyler Kennedy
* URL : https://pypi.org/project/mutf8/
* License : MIT
  Programming Lang: Python
  Description : encoders and decoders for the MUTF-8 character encoding

This package contains simple pure-python as well as C encoders
and decoders for the MUTF-8 character encoding.
In most cases, it can also parse the even-rarer CESU-8.

These days, you'll most likely encounter MUTF-8
when working on files or protocols related to the JVM.
Strings in a Java .class file are encoded using MUTF-8,
strings passed by the JNI, as well as strings exported by the object serializer.

This library was extracted from Lawu,
a Python library for working with JVM class files.



I will maintain this inside DPT.

This is a new dependency of androguard

Bug#1070771: upgrade-reports: After updating with apt upgrade, writing dead keys in Portuguese stopped working

[Eduardo Rolim]

Package: upgrade-reports
Severity: important
X-Debbugs-Cc: ens.ro...@gmail.com

(Please provide enough information to help the Debian
maintainers evaluate the report efficiently - e.g., by filling
in the sections below.)

My previous release is: Debian Bookworm 12.5.0
I am upgrading to: 12.5.0
Archive date: 2024-02-10 12:07 UTC
Upgrade date: 2024-05-08 09:08
uname -a before upgrade: Linux fantasma 6.1.0-18-amd64 #1 SMP PREEMPT_DYNAMIC
Debian 6.1.76-1 (2024-02-01) x86_64 GNU/Linux
uname -a after upgrade: Linux fantasma 6.1.0-21-amd64 #1 SMP PREEMPT_DYNAMIC
Debian 6.1.90-1 (2024-05-03) x86_64 GNU/Linux
Method: apt update | apt list --upgradable | apt upgrade

Contents of /etc/apt/sources.list:

# See https://wiki.debian.org/SourcesList for more information.
deb http://deb.debian.org/debian bookworm main non-free-firmware
deb-src http://deb.debian.org/debian bookworm main non-free-firmware

deb http://deb.debian.org/debian bookworm-updates main non-free-firmware
deb-src http://deb.debian.org/debian bookworm-updates main non-free-firmware

deb http://security.debian.org/debian-security/ bookworm-security main non-
free-firmware
deb-src http://security.debian.org/debian-security/ bookworm-security main non-
free-firmware

# Backports allow you to install newer versions of software made available for
this release
deb http://deb.debian.org/debian bookworm-backports main non-free-firmware
deb-src http://deb.debian.org/debian bookworm-backports main non-free-firmware


- Were there any non-Debian packages installed before the upgrade? No

- Was the system pre-update a 'pure' system only containing packages
  from the previous release? Yes

- Did any packages fail to upgrade? No

- Were there any problems with the system after upgrading? Yes


Further Comments/Problems:

Please attach the output of "COLUMNS=200 dpkg -l" (or "env COLUMNS ...",
depending on your shell) from before and after the upgrade so that we
know what packages were installed on your system.

I compile them here:
https://gist.github.com/vndmtrx/78d3cef4a7d3f0fb5ebab6c9cdb8eb2e

## Bug Report

After upgrading Debian Bookworm with apt upgrade, the system stopped
recognizing Portuguese accents, making it impossible to type accents again.
Upon individually updating each package, especially the locale packages, I
noticed a new language option appeared, called Japones (Mozc). This option,
when accessed through settings, does not show a keyboard layout visualization.
The issue can be replicated by installing the system from scratch in Brazilian
Portuguese and choosing to update the system, after which, on the next system
boot, accent typing will no longer work. Additionally, I couldn't identify the
specific package causing the problem; I suspect the updated locale packages.

## Steps to Reproduce

- Install Debian Bookworm in Brazilian Portuguese.
- Upgrade the system using apt upgrade.
- Reboot the system.
- Attempt to type Portuguese accents.

## Expected Behavior

After the upgrade, the system should continue to recognize Portuguese accents,
allowing users to type them as before.

## Actual Behavior

After the upgrade, the system no longer recognizes Portuguese accents,
rendering typing of accents impossible.

Bug#1065309: transition: gnat (12 -> 13 + time_t64)

[Rafael Laboissière]

* Graham Inggs  [2024-05-08 10:25]:


It looks like the last blocker for this transition is plplot 
5.15.0+dfsg2-10 failing its own autopkgtests [1].


I will soon upload version 5.15.0+dfsg2-11, with the fix proposed by 
Nicolas in Bug#1070746.


Best,

Rafael

Bug#1070770: lintian: check for testing presence of "nodocs" in DEB_BUILD_OPTIONS

[Julian Gilbey]

Package: lintian
Version: 2.117.0
Severity: wishlist

I have come across a number of packages with a line in their
debian/rules like:

ifeq (,$(findstring nodocs, $(DEB_BUILD_OPTIONS)))

This should be "nodoc", according to the "nodoc" entry in
https://wiki.debian.org/BuildProfileSpec#Registered_profile_names

It would be good to check for this error.

Bug#1070480: deap: FTBFS with Python 3.12 as default

[Emmanuel Arias]

Hi,

In version 1.4.1-1 lib2to3 is installed. But I will apply your
suggestion, to avoid this issue in the future.

Cheers!
-- 
cheers,
Emmanuel Arias

 ⢀⣴⠾⠻⢶⣦⠀
 ⣾⠁⢠⠒⠀⣿⡁  eam...@debian.org
 ⢿⡄⠘⠷⠚⠋⠀  OpenPGP: 13796755BBC72BB8ABE2AEB5 FA9DEC5DE11C63F1
 
 ⠈⠳⣄


signature.asc
Description: PGP signature

Bug#1070769: nbdkit: BD-Uninstallable on armel: linux-image-marvell

[Sebastian Ramacher]

Source: nbdkit
Version: 1.38.2-1
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)
X-Debbugs-Cc: sramac...@debian.org

>From https://buildd.debian.org/status/package.php?p=nbdkit:

Dependency installability problem for nbdkit on armel:

nbdkit build-depends on missing:
- linux-image-marvell:armel

Cheers
-- 
Sebastian Ramacher

Bug#1069370: shasta: FTBFS: dpkg-shlibdeps: error: cannot continue due to the error above

[Étienne Mollier]

Hi,

With the error rewrapped to facilitate readability:
> dpkg-shlibdeps: error:
> cannot find library shasta.cpython-311-aarch64-linux-gnu.so
> needed by debian/shasta/usr/bin/shasta
> (ELF format: 'elf64-littleaarch64'
>  abi: 'ELF:64:l:arm64:0';
>  RPATH: '/usr/lib/python3/dist-packages')

The problem seems to stem from the shasta binary having its
DT_RUNPATH set to /usr/lib/python3/dist-packages.  This is
prompting dpkg-shlibdeps to scan the cython shared object to
derive from which package obtaining the library, and fail.

Now to mitigate properly, it might be helpful to see whether
other options than setting the RPATH are acceptable.  Otherwise
dpkg-shlibdeps may have to be instructed to ignore shasta, which
in turn will lead to manual maintenance of library dependencies
in the package.  I see if I can get somewhere…

In hope this helps,
-- 
  .''`.  Étienne Mollier 
 : :' :  pgp: 8f91 b227 c7d6 f2b1 948c  8236 793c f67e 8f0d 11da
 `. `'   sent from /dev/pts/3, please excuse my verbosity
   `-on air: Saga - Framed


signature.asc
Description: PGP signature

Bug#1070768: bpfcc: ftbfs on ppc64el

[Luca Boccassi]

Source: bpfcc
Version: 0.29.1+ds-1
Severity: serious
Tags: ftbfs

Hi,

bpfcc has been failing to build on ppc64el for a long time, and this is
keeping it out of testing.

If you don't have time to fix it, could you please consider at least a
quick upload to remove ppc64el from the list of architectures, so that
it can go back to testing?

Thanks!

-- 
Kind regards,
Luca Boccassi


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

Bug#1070767: bug report install partman-crypto

[Cyril Brulebois]

Hi,

Edson Wolf  (2024-05-08):
> The package partman-crypto which apparently expects libgcc_s.so.1 to be an
> installed library in the installer but lacks dependency to ensure that.

It doesn't need to, debian-installer's build/Makefile ensures it's there.

> Specifically, it does depend on libc6-udeb rather than libc6 with the
> significant difference that it lacks the dependency on libgcc_s.so.1. The
> partman-crypto developer(s) need to decide how to handle that.
> ralph.ronnquist
> 
> Attached images

I'm not seeing anything related to libgcc_s.so.1 in those images.


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


signature.asc
Description: PGP signature

Bug#1070767: bug report install partman-crypto

[Edson Wolf]

Package: partman-crypto
Version: testing

The package partman-crypto which apparently expects libgcc_s.so.1 to be 
an installed library in the installer but lacks dependency to ensure 
that. Specifically, it does depend on libc6-udeb rather than libc6 with 
the significant difference that it lacks the dependency on 
libgcc_s.so.1. The partman-crypto developer(s) need to decide how to 
handle that.

ralph.ronnquist

Attached images

--
A persistência é o caminho do êxito.
Charles Chaplin

Bug#1070766: gcc-13: Please add sparc64 to gcc-as-needed.diff

[Adrian Bunk]

Package: gcc-13
Severity: normal
Tags: patch
X-Debbugs-Cc: debian-sp...@lists.debian.org

sparc64 has some spurios library dependencies due to gcc-as-needed.diff
currently only adding --as-needed to 32bit-only sparc builds, please
append the attached patch to gcc-as-needed.diff

Thanks in advance
--- a/src/gcc/config/sparc/linux64.h
+++ b/src/gcc/config/sparc/linux64.h
@@ -90,7 +90,7 @@ along with GCC; see the file COPYING3.  If not see
   { "link_arch_default", LINK_ARCH_DEFAULT_SPEC },   \
   { "link_arch",LINK_ARCH_SPEC },
 
-#define LINK_ARCH32_SPEC "-m elf32_sparc %{shared:-shared} \
+#define LINK_ARCH32_SPEC "-m elf32_sparc %{shared:-shared} 
%{!fsanitize=*:--as-needed} \
   %{!shared: \
 %{!static: \
   %{rdynamic:-export-dynamic} \
@@ -98,7 +98,7 @@ along with GCC; see the file COPYING3.  If not see
   %{static:-static}} \
 "
 
-#define LINK_ARCH64_SPEC "-m elf64_sparc %{shared:-shared} \
+#define LINK_ARCH64_SPEC "-m elf64_sparc %{shared:-shared} 
%{!fsanitize=*:--as-needed} \
   %{!shared: \
 %{!static: \
   %{rdynamic:-export-dynamic} \

Bug#1070765: paramiko: FTBFS randomly: failing tests

[Santiago Vila]

Package: src:paramiko
Version: 3.4.0-1
Severity: important
Tags: ftbfs

Dear maintainer:

During a rebuild of all packages in unstable, your package failed to build:


[...]
 debian/rules binary
dh binary --with python3 --buildsystem=pybuild
   dh_update_autotools_config -O--buildsystem=pybuild
   dh_autoreconf -O--buildsystem=pybuild
   dh_auto_configure -O--buildsystem=pybuild
I: pybuild base:311: python3.12 setup.py config
running config
I: pybuild base:311: python3.11 setup.py config
running config
   dh_auto_build -O--buildsystem=pybuild
I: pybuild base:311: /usr/bin/python3.12 setup.py build
running build
running build_py
creating /<>/.pybuild/cpython3_3.12_paramiko/build/paramiko
copying paramiko/hostkeys.py -> 
/<>/.pybuild/cpython3_3.12_paramiko/build/paramiko
copying paramiko/transport.py -> 
/<>/.pybuild/cpython3_3.12_paramiko/build/paramiko
copying paramiko/kex_gss.py -> 
/<>/.pybuild/cpython3_3.12_paramiko/build/paramiko
copying paramiko/kex_curve25519.py -> 
/<>/.pybuild/cpython3_3.12_paramiko/build/paramiko
copying paramiko/auth_handler.py -> 
/<>/.pybuild/cpython3_3.12_paramiko/build/paramiko
copying paramiko/__init__.py -> 
/<>/.pybuild/cpython3_3.12_paramiko/build/paramiko
copying paramiko/agent.py -> 
/<>/.pybuild/cpython3_3.12_paramiko/build/paramiko
copying paramiko/server.py -> 
/<>/.pybuild/cpython3_3.12_paramiko/build/paramiko
copying paramiko/ber.py -> 
/<>/.pybuild/cpython3_3.12_paramiko/build/paramiko
copying paramiko/pipe.py -> 
/<>/.pybuild/cpython3_3.12_paramiko/build/paramiko
copying paramiko/rsakey.py -> 
/<>/.pybuild/cpython3_3.12_paramiko/build/paramiko
copying paramiko/proxy.py -> 
/<>/.pybuild/cpython3_3.12_paramiko/build/paramiko
copying paramiko/message.py -> 
/<>/.pybuild/cpython3_3.12_paramiko/build/paramiko
copying paramiko/win_pageant.py -> 
/<>/.pybuild/cpython3_3.12_paramiko/build/paramiko
copying paramiko/sftp_attr.py -> 
/<>/.pybuild/cpython3_3.12_paramiko/build/paramiko
copying paramiko/sftp.py -> 
/<>/.pybuild/cpython3_3.12_paramiko/build/paramiko
copying paramiko/_version.py -> 
/<>/.pybuild/cpython3_3.12_paramiko/build/paramiko
copying paramiko/kex_group1.py -> 
/<>/.pybuild/cpython3_3.12_paramiko/build/paramiko
copying paramiko/util.py -> 
/<>/.pybuild/cpython3_3.12_paramiko/build/paramiko
copying paramiko/sftp_si.py -> 
/<>/.pybuild/cpython3_3.12_paramiko/build/paramiko
copying paramiko/pkey.py -> 
/<>/.pybuild/cpython3_3.12_paramiko/build/paramiko
copying paramiko/_winapi.py -> 
/<>/.pybuild/cpython3_3.12_paramiko/build/paramiko
copying paramiko/kex_group14.py -> 
/<>/.pybuild/cpython3_3.12_paramiko/build/paramiko
copying paramiko/compress.py -> 
/<>/.pybuild/cpython3_3.12_paramiko/build/paramiko
copying paramiko/ecdsakey.py -> 
/<>/.pybuild/cpython3_3.12_paramiko/build/paramiko
copying paramiko/primes.py -> 
/<>/.pybuild/cpython3_3.12_paramiko/build/paramiko
copying paramiko/win_openssh.py -> 
/<>/.pybuild/cpython3_3.12_paramiko/build/paramiko
copying paramiko/dsskey.py -> 
/<>/.pybuild/cpython3_3.12_paramiko/build/paramiko
copying paramiko/ssh_gss.py -> 
/<>/.pybuild/cpython3_3.12_paramiko/build/paramiko
copying paramiko/sftp_client.py -> 
/<>/.pybuild/cpython3_3.12_paramiko/build/paramiko
copying paramiko/sftp_server.py -> 
/<>/.pybuild/cpython3_3.12_paramiko/build/paramiko
copying paramiko/kex_group16.py -> 
/<>/.pybuild/cpython3_3.12_paramiko/build/paramiko
copying paramiko/channel.py -> 
/<>/.pybuild/cpython3_3.12_paramiko/build/paramiko
copying paramiko/auth_strategy.py -> 
/<>/.pybuild/cpython3_3.12_paramiko/build/paramiko
copying paramiko/common.py -> 
/<>/.pybuild/cpython3_3.12_paramiko/build/paramiko
copying paramiko/ssh_exception.py -> 
/<>/.pybuild/cpython3_3.12_paramiko/build/paramiko
copying paramiko/sftp_file.py -> 
/<>/.pybuild/cpython3_3.12_paramiko/build/paramiko
copying paramiko/packet.py -> 
/<>/.pybuild/cpython3_3.12_paramiko/build/paramiko
copying paramiko/kex_ecdh_nist.py -> 
/<>/.pybuild/cpython3_3.12_paramiko/build/paramiko
copying paramiko/client.py -> 
/<>/.pybuild/cpython3_3.12_paramiko/build/paramiko
copying paramiko/file.py -> 
/<>/.pybuild/cpython3_3.12_paramiko/build/paramiko
copying paramiko/buffered_pipe.py -> 
/<>/.pybuild/cpython3_3.12_paramiko/build/paramiko
copying paramiko/sftp_handle.py -> 
/<>/.pybuild/cpython3_3.12_paramiko/build/paramiko
copying paramiko/kex_gex.py -> 
/<>/.pybuild/cpython3_3.12_paramiko/build/paramiko
copying paramiko/ed25519key.py -> 
/<>/.pybuild/cpython3_3.12_paramiko/build/paramiko
copying paramiko/config.py -> 
/<>/.pybuild/cpython3_3.12_paramiko/build/paramiko
I: pybuild base:311: /usr/bin/python3 setup.py build
running build
running build_py
creating /<>/.pybuild/cpython3_3.11_paramiko/build/paramiko
copying paramiko/hostkeys.py -> 
/<>/.pybuild/cpython3_3.11_paramiko/build/paramiko
copying paramiko/transport.py -> 
/<>/.pybuild/cpython3_3.11_paramiko/build/paramiko
copying paramiko/kex_gss.py -> 

Bug#1070688: [pkg-gnupg-maint] Bug#1070688: gnupg: PINENTRY_USER_DATA not passed to pinentry

[Daniel Kahn Gillmor]

Control: affects 1070688 + gpg-from-sq apt

Hi Farblos, all--

Thanks for this detailed bug report (https://bugs.debian.org/1070688).
I'm a bit confused about the following:

On Wed 2024-05-08 11:07:28 +0200, Farblos wrote:
> Never mind.  During one of the last t64 upgrade orgies package gpg-sq got
> installed on my system and succeeded to install the diversion to /usr/bin/gpg.
> And the sequoia replacement is not very feature complete, as they continue
> to stress themselfes.

gpg-sq doesn't install any diversions to my knowledge.  the only
diversions that might be installed are in gpg-from-sq or gpgv-from-sq.

If those packages were on your system, then they could indeed have
installed a diversion.  But nothing explicitly depends on those packages
(try running "apt rdepends gpg{,v}-from-sq") so i'm not sure how they
got installed during an upgrade.

Perhaps it has something to do with the fact that the packages use the
Provides field?  If you didn't deliberately install either of the
*-from-sq packages, and they ended up on your system, is there some way
that you can replicate the upgrade path?  I'd like to understand that
better, as i don't think it should have happened by accident.

Perhaps there is some signal either package can give to apt to help it
avoid that problem in the future?

> For example, referencing a recipient by exact name with "="
> does not work in gpg-sq, either.

Thanks, i've reported this part upstream:
https://gitlab.com/sequoia-pgp/sequoia-chameleon-gnupg/-/issues/74

--dkg


signature.asc
Description: PGP signature

Bug#1070660: shim 15.8-1~deb12u1 flagged for acceptance

[Adam D Barratt]

package release.debian.org
tags 1070660 = bookworm pending
thanks

Hi,

The upload referenced by this bug report has been flagged for acceptance into 
the proposed-updates queue for Debian bookworm.

Thanks for your contribution!

Upload details
==

Package: shim
Version: 15.8-1~deb12u1

Explanation: new upstream release

Bug#1070670: shim 15.8-1~deb11u1 flagged for acceptance

[Adam D Barratt]

package release.debian.org
tags 1070670 = bullseye pending
thanks

Hi,

The upload referenced by this bug report has been flagged for acceptance into 
the proposed-updates queue for Debian bullseye.

Thanks for your contribution!

Upload details
==

Package: shim
Version: 15.8-1~deb11u1

Explanation: new upstream release

Bug#1065013: nvidia-graphics-drivers 470.239.06-1 flagged for acceptance

[Adam D. Barratt]

On Wed, 2024-05-08 at 19:18 +0200, Andreas Beckmann wrote:
> On 05/05/2024 20.52, Adam D Barratt wrote:
> > Package: nvidia-graphics-drivers
> > Version: 470.239.06-1
> 
> > Explanation: upstream security fixes [CVE-2022-42265 CVE-2024-0074
> > CVE-2024-0078]
> 
> Can we push these packages to bullseye-updates?
> The kernel change that recently caused problems for the nvidia
> modules 
> in bookworm has now reached bullseye, too: #1070726, but the new 
> upstream already sitting in bullseye-pu is sufficient to fix that.

Would wording similar to
https://lists.debian.org/debian-stable-announce/2024/02/msg2.html
be accurate / suitable? (With the 12.5 reference changed to the
relevant DSA number.)

Regards,

Adam

Bug#1065013: nvidia-graphics-drivers 470.239.06-1 flagged for acceptance

[Andreas Beckmann]

On 05/05/2024 20.52, Adam D Barratt wrote:

Package: nvidia-graphics-drivers
Version: 470.239.06-1



Explanation: upstream security fixes [CVE-2022-42265 CVE-2024-0074 
CVE-2024-0078]


Can we push these packages to bullseye-updates?
The kernel change that recently caused problems for the nvidia modules 
in bookworm has now reached bullseye, too: #1070726, but the new 
upstream already sitting in bullseye-pu is sufficient to fix that.


Therefore I'd recommend to push these packages to bullseye-updates:

nvidia-graphics-drivers | 470.239.06-1
nvidia-settings | 470.239.06-1
nvidia-graphics-drivers-tesla-470 | 470.239.06-1~deb11u1

(tha would imply that temporarily the version of 
nvidia-graphics-drivers-tesla-470 in bullseye-updates is higher than the 
one in bookworm-updates)



Andreas

Bug#1070764: nvidia-alternative: Is nvidia-alternative missing conflicts nvidia-tesla-470-alternative

[Diane Trout]

Package: nvidia-alternative
Version: 525.147.05-4~deb12u1
Severity: normal
X-Debbugs-Cc: none, Diane Trout 

Dear Maintainer,

I have a system with an older NVidia tesla card in it and nvidia-detect
recommended the tesla-470 driver.

unfortunately for me I'm having a bunch of trouble getting the right mix
of nvidia driver and libraris installed. I've been having trouble
keeping the 525 version uninstalled while getting the 470 version
installed.

One thing I noticed on nvidia-alternative was a long list of conflicts
that skips over nvidia-tesla-470-alternative. I was wondering if that
was an oversight (and if maybe there were some more conflicts missing.

Here's the output of apt show nvidia-alternative. This is on a system that
was just upgraded from 11 to 12.

Package: nvidia-alternative
Version: 525.147.05-4~deb12u1
Priority: optional
Section: non-free/libs
Source: nvidia-graphics-drivers
Maintainer: Debian NVIDIA Maintainers 
Installed-Size: 188 kB
Provides: nvidia-alternative--kmod-alias, nvidia-alternative-525.147.05, 
nvidia-alternative-any
Pre-Depends: dpkg (>= 1.17.21), nvidia-legacy-check (>= 495)
Depends: glx-alternative-nvidia (>= 1.2)
Conflicts: libegl1-glvnd-nvidia, libgl1-glvnd-nvidia-glx, 
libgles1-glvnd-nvidia, libgles2-glvnd-nvidia, libglvnd0-nvidia, 
libglx0-glvnd-nvidia, libopengl0-glvnd-nvidia, nvidia-legacy-304xx-alternative, 
nvidia-legacy-340xx-alternative, nvidia-legacy-390xx-alternative, 
nvidia-tesla-418-alternative, nvidia-tesla-450-alternative, 
nvidia-tesla-460-alternative, nvidia-tesla-510-alternative

Thanks,
Diane

Bug#1066671: geki3

[Alexandre Detiste]

Please push your changes to Salsa.

You can also nmu it,
I absolutely don't mind

Or I'll do the upload

Thanks

Bug#1067651: mapserver fails to build on armhf in Ubuntu due to implicit declaration of strlcpy

[Santiago Vila]

severity 1067651 serious
retitle 1067651 mapserver: FTBFS: error: implicit declaration of function 
‘strlcpy’
thanks

El 25/3/24 a las 9:25, Vladimir Petko escribió:

  strlcpy and strlcat were introduced in glibc 2.38[1]. At the moment
Ubuntu noble has 2.39  and Debian unstable  - 2.37.
  The issue will become relevant for Debian once glibc 2.38 is
introduced to unstable.


Indeed. Right now we have 2.38-7 in testing and 2.38-8 in unstable,
so this is now happening in Debian. I'm adjusting the metadata
(now RC, no longer just Ubuntu, and no longer just armhf).

Thanks.

Bug#1069127: python-idna: CVE-2024-3651

[Guilhem Moulin]

Hi,

On Tue, 16 Apr 2024 at 21:35:22 +0200, Salvatore Bonaccorso wrote:
> The following vulnerability was published for python-idna.
>
> CVE-2024-3651[0]:
> | potential DoS via resource consumption via specially crafted inputs to
> | idna.encode()

I'm preparing an update for this issue for Buster LTS, would you like me
to propose debdiffs for (o)s-pu and sid too?

Cheers,
-- 
Guilhem.


signature.asc
Description: PGP signature

Bug#1070753: (no subject)

[Steven Maddox]

With the help of pham of #debian-boot on OFTC...

Problems found so far with /var/lib/dpkg/info/ppp-udeb.postinst

- Some lines call 'ps' with a -A argument which this build of busybox 
doesn't understand (so it doesn't record the process number correctly to 
try and kill it later)


- The '-A' argument passed to pppoe-discovery doesn't seem to exist and 
so it doesn't run properly


- With *some* (but not all) PPPoE concentrators... if pppoe-discovery 
finds the concentrator... it'll output the details and just sit there 
without exiting indefinably... so grep never has a chance to process the 
contents of stdin and find the string 'AC'.  This wouldn't be an issue 
if the busybox version of grep has --line-buffered but it doesn't :)


- Ultimately if -Q is used (instead of grepping for 'AC') then you'll 
get errcode 1 if one isn't found and errcode 0 if one is found... by 
default this'll take 15 seconds to try (unless you set -t and/or -a). 
But since the script runs this twice (once without -U and once with -U) 
then this means a wait of up to 30 seconds, which d-i has to be patient 
for and allow to happen.


- Ultimately if we're happy that pppoe-discovery will time itself out... 
then does d-i need to kill anything and thus knowing the process ID 
isn't needed?


--
Steven Maddox
Lantizia

Bug#1070763: libyang2-dev needs move of header file for multi-arch compatibility

[David Lamparter]

Package: libyang2-dev
Version: 2.1.148-0.1
Severity: wishlist
Tags: patch

Hi all,


the libyang2-dev package currently can't be installed in parallel for
multi-arch build environments with mixed 32-bit and 64-bit
architectures.  The reason for this is that the content of
/usr/include/libyang/config.h depends on the sizes of some types.

Attached is a patch to move that file to /usr/include//libyang.
This enables cross-compiling setups where libyang is needed on both
build and host architectures.

Cheers,


equi
diff -ur libyang2-2.1.148/debian/libyang2-dev.install 
libyang2-2.1.148/debian/libyang2-dev.install
--- libyang2-2.1.148/debian/libyang2-dev.install2023-02-01 
10:12:00.0 +0100
+++ libyang2-2.1.148/debian/libyang2-dev.install2024-05-08 
17:25:49.081859201 +0200
@@ -1,3 +1,4 @@
 usr/include/libyang/*.h
+usr/include/*/libyang/*.h
 usr/lib/*/*.so
 usr/lib/*/pkgconfig/*.pc
diff -ur libyang2-2.1.148/debian/rules libyang2-2.1.148.new/debian/rules
--- libyang2-2.1.148/debian/rules   2023-02-01 10:12:00.0 +0100
+++ libyang2-2.1.148/debian/rules   2024-05-08 17:44:20.504783204 +0200
@@ -11,3 +11,11 @@
dh_auto_configure -- \
-DCMAKE_BUILD_TYPE:String="Release" \
-DENABLE_TESTS=ON
+
+override_dh_auto_install:
+   dh_auto_install
+   mkdir -p debian/tmp/usr/include/$(DEB_HOST_MULTIARCH)/libyang
+   mv  debian/tmp/usr/include/libyang/config.h \
+   debian/tmp/usr/include/$(DEB_HOST_MULTIARCH)/libyang
+   sed -e 's%#include "config\.h"%#include %' -i \
+   debian/tmp/usr/include/libyang/*.h

Bug#1070762: debos: unhelpful error message "Modules path couldn't be determined"

[Helmut Grohne]

Package: debos
Version: 1.1.1-2.1+b1

Hi,

I was trying to use debos and all that it told me was:

| Modules path couldn't be determined

This is not helpful. After digging into code I eventually figured that
when it says "modules" it measn "Linux kernel modules". This is not
evident from the context. Moreoever, it eventually became clear that the
module it was missing was 9pnet_virtio. If that name had been included
in the error message, it would have been immediately obvious to me that
the cause was using a -cloud kernel as -cloud kernels lack 9p
functionality (see #955232). While debos recommends a non-cloud kernel
and the non-cloud kernel even got installed, the additional presence of
a -cloud kernel image meant that grub would prefer booting that.

I hope this is sufficient reason to improve the error message. Thanks
for considering.

Helmut

Bug#1070739: bookworm-pu: package python-glance-store/4.1.0-4

[Salvatore Bonaccorso]

Hi,

On Wed, May 08, 2024 at 09:52:01AM +0200, Thomas Goirand wrote:
> Package: release.debian.org
> Severity: normal
> Tags: bookworm
> User: release.debian@packages.debian.org
> Usertags: pu
> X-Debbugs-Cc: python-glance-st...@packages.debian.org
> Control: affects -1 + src:python-glance-store
> 
> [ Reason ]
> I would like to update python-glance-store/4.1.0-4 to
> python-glance-store/4.1.1-1+deb12u1 to address CVE-2024-1141
> (aka: #1063795).

Should that be 4.1.1-0+deb12u1 instead? (I do know that 4.1.1-1 was
never in the archive ,but that makes sure it sorts before 4.1.1-1).

Regards,
Salvatore

Bug#1068112: Accepted pcp 6.2.1-1 (source arm64 all) into unstable

[Salvatore Bonaccorso]

Source: pcp
Source-Version: 6.2.1-1

On Tue, May 07, 2024 at 06:03:03PM +, Debian FTP Masters wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA512
> 
> Format: 1.8
> Date: Wed, 10 Apr 2024 09:14:46 +1100
> Source: pcp
> Binary: libpcp-archive1 libpcp-archive1-dev libpcp-gui2 libpcp-gui2-dev 
> libpcp-import-perl libpcp-import1 libpcp-import1-dev libpcp-logsummary-perl 
> libpcp-mmv-perl libpcp-mmv1 libpcp-mmv1-dev libpcp-pmda-perl libpcp-pmda3 
> libpcp-pmda3-dev libpcp-trace2 libpcp-trace2-dev libpcp-web1 libpcp-web1-dev 
> libpcp3 libpcp3-dev pcp pcp-conf pcp-doc pcp-export-pcp2elasticsearch 
> pcp-export-pcp2graphite pcp-export-pcp2influxdb pcp-export-pcp2json 
> pcp-export-pcp2spark pcp-export-pcp2xlsx pcp-export-pcp2xml 
> pcp-export-pcp2zabbix pcp-export-zabbix-agent pcp-gui pcp-import-collectl2pcp 
> pcp-import-ganglia2pcp pcp-import-iostat2pcp pcp-import-mrtg2pcp 
> pcp-import-sar2pcp pcp-import-sheet2pcp pcp-pmda-infiniband pcp-testsuite 
> pcp-zeroconf python3-pcp
> Architecture: source arm64 all
> Version: 6.2.1-1
> Distribution: unstable
> Urgency: low
> Maintainer: PCP Development Team 
> Changed-By: Nathan Scott 
> Description:
>  libpcp-archive1 - Performance Co-Pilot archive writing library
>  libpcp-archive1-dev - Performance Co-Pilot archive writing library and 
> headers
>  libpcp-gui2 - Performance Co-Pilot graphical client tools library
>  libpcp-gui2-dev - Performance Co-Pilot graphical client tools library and 
> headers
>  libpcp-import-perl - Performance Co-Pilot log import Perl module
>  libpcp-import1 - Performance Co-Pilot data import library
>  libpcp-import1-dev - Performance Co-Pilot data import library and headers
>  libpcp-logsummary-perl - Performance Co-Pilot historical log summary module
>  libpcp-mmv-perl - Performance Co-Pilot Memory Mapped Value Perl module
>  libpcp-mmv1 - Performance Co-Pilot Memory Mapped Value client library
>  libpcp-mmv1-dev - Performance Co-Pilot Memory Mapped Value library and 
> headers
>  libpcp-pmda-perl - Performance Co-Pilot Domain Agent Perl module
>  libpcp-pmda3 - Performance Co-Pilot Domain Agent library
>  libpcp-pmda3-dev - Performance Co-Pilot Domain Agent library and headers
>  libpcp-trace2 - Performance Co-Pilot application tracing library
>  libpcp-trace2-dev - Performance Co-Pilot application tracing library and 
> headers
>  libpcp-web1 - Performance Co-Pilot data import library
>  libpcp-web1-dev - Performance Co-Pilot web tooling
>  libpcp3- Performance Co-Pilot library
>  libpcp3-dev - Performance Co-Pilot library and headers
>  pcp- System level performance monitoring and performance management
>  pcp-conf   - Performance Co-Pilot runtime configuration
>  pcp-doc- Documentation and tutorial for the Performance Co-Pilot
>  pcp-export-pcp2elasticsearch - Tool for exporting data from PCP to 
> Elasticsearch
>  pcp-export-pcp2graphite - Tool for exporting data from PCP to Graphite
>  pcp-export-pcp2influxdb - Tool for exporting data from PCP to InfluxDB
>  pcp-export-pcp2json - Tool for exporting data from PCP to JSON
>  pcp-export-pcp2spark - Tool for exporting data from PCP to Apache Spark
>  pcp-export-pcp2xlsx - Tool for exporting data from PCP to Excel spreadsheets
>  pcp-export-pcp2xml - Tool for exporting data from PCP to XML
>  pcp-export-pcp2zabbix - Tool for exporting data from PCP to Zabbix
>  pcp-export-zabbix-agent - Module for exporting PCP metrics to Zabbix agent
>  pcp-gui- Visualisation tools for the Performance Co-Pilot toolkit
>  pcp-import-collectl2pcp - Tool for importing data from collectl into PCP 
> archive logs
>  pcp-import-ganglia2pcp - Tool for importing data from ganglia into PCP 
> archive logs
>  pcp-import-iostat2pcp - Tool for importing data from iostat into PCP archive 
> logs
>  pcp-import-mrtg2pcp - Tool for importing data from MRTG into PCP archive logs
>  pcp-import-sar2pcp - Tool for importing data from sar into PCP archive logs
>  pcp-import-sheet2pcp - Tool for importing data from a spreadsheet into PCP 
> archive logs
>  pcp-pmda-infiniband - Infiniband performance metrics domain agent (PMDA)
>  pcp-testsuite - Performance Co-Pilot (PCP) Test Suite
>  pcp-zeroconf - Performance Co-Pilot (PCP) Zeroconf Package
>  python3-pcp - Performance Co-Pilot Python3 PMAPI module
> Closes: 1068389
> Changes:
>  pcp (6.2.1-1) unstable; urgency=low
>  .
>* New release (full details in CHANGELOG).
>* Drop BCC metrics as python3-bpfcc is no more (closes: #1068389)
> Checksums-Sha1:
>  637cc70fcadc359ed918ad06782105b07a4a49d3 5167 pcp_6.2.1-1.dsc
>  0937cbb81aa51d58f88a655051139b187bfe40a6 52262174 pcp_6.2.1.orig.tar.gz
>  4169185a601ba722e120739099ef540c604d3fcc 26832 pcp_6.2.1-1.debian.tar.xz
>  f7137a18c5eb173c8ac2d5f388229ec8fcd5f6f0 136968 
> libpcp-archive1-dev_6.2.1-1_arm64.deb
>  5b243d0c7aee81c85db0e5c6e67f0acf50cabcd0 123776 
> libpcp-archive1_6.2.1-1_arm64.deb
>  fe81f37f52d4b2624c42ef2876d5b3578612f2aa 126244 
> libpcp-gui2-dev_6.2.1-1_arm64.deb
>  

Bug#1070756: ibus-hangul does not work after installing debian-security updates.

[NoWook Kee]

consult to 
https://salsa.debian.org/gnome-team/glib/-/commit/73615de44ff0fba7a76dc5fed7d2559b0f7f4a65


glib2.0 (2.74.6-2+deb12u2) bookworm-security; urgency=high

  * 
d/p/CVE-2024-34397/gdbusconnection-Allow-name-owners-to-have-the-syntax-of-a.patch:
Relax name owner checks to avoid a regression in ibus.
Fixing CVE-2024-34397 caused a regression in ibus affecting text entry
with non-trivial input methods.
(Closes: #1070730, #1070736, #1070743, #1070745)
(Closes: #1070730, #1070736, #1070743, #1070745, #1070749, #1070752)


On Wed, May 8, 2024 at 11:21 PM Kee, No-Wook  wrote:

> Package: ibus-hangul
> Version: 1.5.4-2
> Severity: normal
> Tags: l10n
> X-Debbugs-Cc: lusc...@gmail.com
>
> ibus-hangul does not work after installing debian-security updates.
> The packages updated today are as follows.
> I found the same issue on two different machines and submitted a bug
> report.
>
> The package update details are below.
>
> # apt update
> # apt upgrade
>
> After this operation, 408 MB of additional disk space will be used.
> Do you want to continue? [Y/n]
> Get:1 http://security.debian.org/debian-security bookworm-security/main
> amd64
> libc6-i386 amd64 2.36-9+deb12u7 [2,460 kB]
> Get:2 https://deb.nodesource.com/node_20.x nodistro/main amd64 nodejs
> amd64
> 20.13.0-1nodesource1 [31.6 MB]
> Get:3 http://security.debian.org/debian-security bookworm-security/main
> amd64
> libc-devtools amd64 2.36-9+deb12u7 [53.4 kB]
> Get:4 http://security.debian.org/debian-security bookworm-security/main
> amd64
> libc6-dev amd64 2.36-9+deb12u7 [1,899 kB]
> Get:5 https://dl.google.com/linux/chrome/deb stable/main amd64
> google-chrome-
> stable amd64 124.0.6367.155-1 [107 MB]
> Get:6 http://security.debian.org/debian-security bookworm-security/main
> amd64
> libc-dev-bin amd64 2.36-9+deb12u7 [45.8 kB]
> Get:7 http://security.debian.org/debian-security bookworm-security/main
> amd64
> linux-libc-dev amd64 6.1.90-1 [1,976 kB]
> Get:8 http://security.debian.org/debian-security bookworm-security/main
> amd64
> libc6-dbg amd64 2.36-9+deb12u7 [7,462 kB]
> Get:9 http://security.debian.org/debian-security bookworm-security/main
> amd64
> libc6 amd64 2.36-9+deb12u7 [2,758 kB]
> Get:10 http://security.debian.org/debian-security bookworm-security/main
> amd64
> libc-bin amd64 2.36-9+deb12u7 [607 kB]
> Get:11 http://security.debian.org/debian-security bookworm-security/main
> amd64
> libglib2.0-data all 2.74.6-2+deb12u1 [1,209 kB]
> Get:12 http://security.debian.org/debian-security bookworm-security/main
> amd64
> libglib2.0-bin amd64 2.74.6-2+deb12u1 [110 kB]
> Get:13 http://security.debian.org/debian-security bookworm-security/main
> amd64
> libglib2.0-0 amd64 2.74.6-2+deb12u1 [1,401 kB]
> Get:14 http://security.debian.org/debian-security bookworm-security/main
> amd64
> less amd64 590-2.1~deb12u2 [132 kB]
> Get:15 http://security.debian.org/debian-security bookworm-security/main
> amd64
> libc-l10n all 2.36-9+deb12u7 [675 kB]
> Get:16 http://security.debian.org/debian-security bookworm-security/main
> amd64
> locales all 2.36-9+deb12u7 [3,902 kB]
> Get:17 http://security.debian.org/debian-security bookworm-security/main
> amd64
> glibc-doc all 2.36-9+deb12u7 [3,476 kB]
> Get:18 http://security.debian.org/debian-security bookworm-security/main
> amd64
> gnome-shell-extension-prefs amd64 43.9-0+deb12u2 [28.3 kB]
> Get:19 http://security.debian.org/debian-security bookworm-security/main
> amd64
> gnome-shell amd64 43.9-0+deb12u2 [856 kB]
> Get:20 http://security.debian.org/debian-security bookworm-security/main
> amd64
> gnome-shell-common all 43.9-0+deb12u2 [799 kB]
> Get:21 http://security.debian.org/debian-security bookworm-security/main
> amd64
> libruby3.1 amd64 3.1.2-7+deb12u1 [5,400 kB]
> Get:22 http://security.debian.org/debian-security bookworm-security/main
> amd64
> linux-image-6.1.0-21-amd64 amd64 6.1.90-1 [68.8 MB]
> Get:23 http://security.debian.org/debian-security bookworm-security/main
> amd64
> linux-image-amd64 amd64 6.1.90-1 [1,476 B]
> Get:24 http://security.debian.org/debian-security bookworm-security/main
> amd64
> ruby3.1 amd64 3.1.2-7+deb12u1 [663 kB]
> Fetched 243 MB in 22s (11.2 MB/s)
>
>
> -- Package-specific info:
> XMODIFIERS=@im=ibus
> CLUTTER_IM_MODULE=
> GTK_IM_MODULE=
> QT_IM_MODULE=ibus
> WAYLAND_DISPLAY=wayland-0
> XDG_CURRENT_DESKTOP=GNOME
> XDG_MENU_PREFIX=gnome-
> XDG_RUNTIME_DIR=/run/user/1000
> XDG_SEAT=
> XDG_SESSION_CLASS=user
> XDG_SESSION_DESKTOP=gnome
> XDG_SESSION_ID=
> XDG_SESSION_TYPE=wayland
>
> === gsettings list-recursively org.gnome.desktop.input-sources ===
> org.gnome.desktop.input-sources current uint32 0
> org.gnome.desktop.input-sources mru-sources @a(ss) []
> org.gnome.desktop.input-sources per-window false
> org.gnome.desktop.input-sources show-all-sources false
> org.gnome.desktop.input-sources sources [('ibus', 'hangul')]
> org.gnome.desktop.input-sources xkb-options @as []
>
> === gsettings list-recursively org.freedesktop.ibus.engine.hangul ===
> 

Bug#1070761: bullseye-pu: package bart-cuda/0.6.00-1+deb11u1

[Santiago Vila]

Package: release.debian.org
Severity: normal
Tags: bullseye
User: release.debian@packages.debian.org
Usertags: pu
X-Debbugs-Cc: bart-c...@packages.debian.org, sanv...@debian.org
Control: affects -1 + src:bart-cuda

[ Reason ]
This upload fixes Bug #1070757 FTBFS in bullseye.
Note: A similar request for a similar bug has been made for package "bart".

[ Impact ]
Anybody who try to build the package from source may find
that the package FTBFS unexpectedly.

[ Tests ]
I've tested the fixed package in the AWS instances where it
used to fail, and it does not fail anymore.

[ Risks ]
Very low risk, as the change merely increases the tolerance for
a floating point comparison in the tests. The program itself
does not really 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 (old)stable
  [X] the issue is verified as fixed in unstable

[ Changes ]
See debdiff.

[ Other info ]
I'm going to upload the package after sending this report,
but I'll wait for approval before pushing changes to salsa.diff -Nru bart-cuda-0.6.00/debian/changelog bart-cuda-0.6.00/debian/changelog
--- bart-cuda-0.6.00/debian/changelog   2020-12-18 21:23:31.0 +0100
+++ bart-cuda-0.6.00/debian/changelog   2024-05-08 16:40:00.0 +0200
@@ -1,3 +1,11 @@
+bart-cuda (0.6.00-1+deb11u1) bullseye; urgency=medium
+
+  * Team upload.
+  * Cherry-pick relax-failing-unit-test.patch from release 0.7.00-1.
+Fixes FTBFS bug. Closes: #1070757.
+
+ -- Santiago Vila   Wed, 08 May 2024 16:40:00 +0200
+
 bart-cuda (0.6.00-1) unstable; urgency=medium
 
   * Initial upload of this cuda enabled bart version
diff -Nru bart-cuda-0.6.00/debian/patches/0005-relax-failing-unit-test.patch 
bart-cuda-0.6.00/debian/patches/0005-relax-failing-unit-test.patch
--- bart-cuda-0.6.00/debian/patches/0005-relax-failing-unit-test.patch  
1970-01-01 01:00:00.0 +0100
+++ bart-cuda-0.6.00/debian/patches/0005-relax-failing-unit-test.patch  
2024-05-08 16:40:00.0 +0200
@@ -0,0 +1,19 @@
+From: Martin Uecker 
+Date: Mon, 25 Oct 2021 18:59:03 +0200
+Subject: relax failing unit test
+
+---
+ utests/test_nufft.c | 2 +-
+ 1 file changed, 1 insertion(+), 1 deletion(-)
+
+--- a/utests/test_nufft.c
 b/utests/test_nufft.c
+@@ -114,7 +114,7 @@
+ 
+   debug_printf(DP_DEBUG1, "adjoint diff: %f\n", diff);
+ 
+-  bool ret = (diff < 1.E-6f);
++  bool ret = (diff < 1.E-5f);
+ 
+   linop_free(op);
+ 
diff -Nru bart-cuda-0.6.00/debian/patches/series 
bart-cuda-0.6.00/debian/patches/series
--- bart-cuda-0.6.00/debian/patches/series  2020-12-18 21:23:31.0 
+0100
+++ bart-cuda-0.6.00/debian/patches/series  2024-05-08 16:40:00.0 
+0200
@@ -2,3 +2,4 @@
 0002-remove-empty-directory.patch
 0003-deactivate-ode-unit-tests.patch
 0004-change-cuda-library.patch
+0005-relax-failing-unit-test.patch

Bug#1070760: ITP: buteo-syncfw -- Buteo Synchronization Framework

[Mike Gabriel]

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

* Package name: buteo-syncfw
  Version : 0.11.3
  Upstream Contact: https://sailfishos.org/contact/
* URL : https://github.com/sailfishos/buteo-syncfw
* License : LGPL-2.1
  Programming Lang: C++
  Description : Buteo Synchronization Framework

 In Lomiri, Buteo Sync Framework will be the new backend daemon for
 syncing groupware data between a local device and remote services.
 .
 This package will be maintained by the Debian UBports Packaging Team.

Bug#1070759: new upstream release

[Antoine Beaupre]

Package: fabric
Version: 2.6.0-1
Severity: wishlist
X-Debbugs-Cc: debian-pyt...@lists.debian.org

A new upstream release is available for Fabric (3.2.2 at the time of
writing).

It depends on the new pytest-relaxed package, missing from Debian,
itself blocked on upstream upgrading their pytest support (#1008768).

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

Kernel: Linux 6.6.13+bpo-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 fabric depends on:
ii  libjs-sphinxdoc5.3.0-4
ii  python33.11.2-1+b1
ii  python3-fabric 2.6.0-1
ii  python3-pkg-resources  66.1.1-1

fabric recommends no packages.

fabric suggests no packages.

-- no debconf information

Bug#1070758: new upstream release (2.2.0)

[Antoine Beaupre]

Package: python3-invoke
Version: 2.0.0-1
Severity: wishlist
X-Debbugs-Cc: debian-pyt...@lists.debian.org, Alexandre Detiste 


Invoke has had several releases that are not included yet in Debian. I
had started working on updating to 2.2.0 but got blocked on
pytest-relaxed missing from Debian, itself blocked on upstream
upgrading their pytest support (#1008768).

Right now, the git repository is in bad shape, as it has some blobs
from 2.2.0 but not the latest changes from unstable, so that needs to
be fixed first. I tried to do it myself but failed, so I'm hoping the
uploader (tchet, in cc) can handle this first.

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

Kernel: Linux 6.6.13+bpo-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-invoke depends on:
ii  python33.11.2-1+b1
ii  python3-pkg-resources  66.1.1-1
ii  python3-six1.16.0-4
ii  python3-yaml   6.0-3+b2

python3-invoke recommends no packages.

Versions of packages python3-invoke suggests:
pn  python-invoke-doc  

-- no debconf information

Bug#1070745: Bug#1070730 etc.: libglib2.0-0: ibus input regression

[Jérôme Charaoui]

On Wed, 8 May 2024 13:03:51 +0100 Simon McVittie  wrote:

On Wed, 08 May 2024 at 03:48:21 +, unfathomabl...@protonmail.com wrote:
> Latest upgrade from 2.74.6-2 to 2.74.6-2+deb12u1 broke input of Japanese
> characters GTK programs (such as firefox, gedit etc).

For users of testing/unstable, this will be fixed as soon as I can,
probably by version 2.80.1-1. Each GLib build takes around an hour,
plus the time required for testing, so it is not possible to fix this
instantaneously.

For users of Debian 12 'bookworm', a test-build of a fix for this
regression is available here: https://people.debian.org/~smcv/bug1070730/
(amd64 + i386 + source)


I can confirm these builds fix the input issues reported here on my system.

Thank you for moving so fast on this,

-- Jérôme

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

[Richard B]

Hello.

Upgrading gstreamer1.0-plugins-ugly to 1.24.3-1 on Trixie didn't produce 
the error that was originally reported.  Here's my output:


   Retrieving bug reports... Done
   Parsing Found/Fixed information... Done
   serious bugs of gstreamer1.0-plugins-good (1.22.10-1 → 1.24.3-1)
   
 b1 - #1063900 - gstreamer1.0-plugins-good: missing
   Breaks+Replaces: gstreamer1.0-plugins-ugly (<< 1.23)
   Merged with: 1063921
   Summary:
 gstreamer1.0-plugins-good(1 bug)
   Are you sure you want to install/upgrade the above packages?
   [Y/n/?/...] y
   Reading changelogs... Done
   ...
   Preparing to unpack .../gstreamer1.0-plugins-good_1.24.3-1_amd64.deb ...
   Unpacking gstreamer1.0-plugins-good:amd64 (1.24.3-1) over
   (1.22.10-1) ...
   Preparing to unpack .../gstreamer1.0-plugins-bad_1.24.3-1_amd64.deb ...
   Unpacking gstreamer1.0-plugins-bad:amd64 (1.24.3-1) over (1.22.10-1) ...
   ...
   Preparing to unpack
   .../04-libgstreamer-plugins-bad1.0-0_1.24.3-1_amd64.deb ...
   Unpacking libgstreamer-plugins-bad1.0-0:amd64 (1.24.3-1) over
   (1.22.10-1) ...
   Preparing to unpack
   .../05-gir1.2-gst-plugins-bad-1.0_1.24.3-1_amd64.deb ...
   Unpacking gir1.2-gst-plugins-bad-1.0:amd64 (1.24.3-1) over
   (1.22.10-1) ...
   ...
   Setting up libgstreamer-plugins-bad1.0-0:amd64 (1.24.3-1) ...
   Setting up gir1.2-gst-plugins-bad-1.0:amd64 (1.24.3-1) ...
   Setting up gstreamer1.0-plugins-good:amd64 (1.24.3-1) ...
   Setting up gstreamer1.0-plugins-bad:amd64 (1.24.3-1) ...
   Processing triggers for libc-bin (2.38-7) ...

I see that the conflicting files mentioned are on my system, but that 
didn't seem to impact my upgrade:


   -rw-r--r-- 1 root root 27K Apr 30 04:18
   /usr/lib/x86_64-linux-gnu/gstreamer-1.0/libgstamrnb.so
   -rw-r--r-- 1 root root 19K Apr 30 04:18
   /usr/lib/x86_64-linux-gnu/gstreamer-1.0/libgstamrwbdec.so
   -rw-r--r-- 1 root root 208 Apr 29 18:15
   /usr/share/gstreamer-1.0/presets/GstAmrnbEnc.prs

gstreamer1.0-plugins-ugly was upgraded to a matching version before 
this.  Here's what dpkg reports:


   ii  gstreamer1.0-plugins-ugly:amd64
   1.24.3-1 amd64    GStreamer plugins
   from the "ugly" set

Best.

Richard

Bug#1070751: transition: libxlsxwriter

[Emilio Pozuelo Monfort]

Control: tags -1 confirmed

On 08/05/2024 15:40, Boyuan Yang wrote:

Package: release.debian.org
Control: affects -1 + src:libxlsxwriter
X-Debbugs-Cc: libxlsxwri...@packages.debian.org
User: release.debian@packages.debian.org
Usertags: transition
X-Debbugs-Cc: by...@debian.org
Severity: normal

I would like to launch the transition as listed below:

* https://release.debian.org/transitions/html/auto-libxlsxwriter.html

The transition is triggered by the SONAME bump.

List of all affected packages:

* src:deepin-log-viewer (OK)
* src:readstat (OK)

All reverse build-dependencies can be successfully rebuilt with the
new libxlsxwriter.


Go ahead.

Emilio

Bug#1070757: bart-cuda: FTBFS in bullseye: failing tests

[Santiago Vila]

Package: src:bart-cuda
Version: 0.6.00-1
Severity: serious
Tags: ftbfs patch
Control: fixed -1 0.8.00-2
Control: owner -1 sanv...@debian.org

Dear maintainer:

During a rebuild of all packages in bullseye, your package failed to build:


[...]
 debian/rules binary
dh binary
   dh_update_autotools_config
   dh_autoreconf
   dh_auto_configure
   dh_auto_build
make -j2 "INSTALL=install --strip-program=true"
make[1]: Entering directory '/<>'
make MAKESTAGE=2
make[2]: Entering directory '/<>'
make[2]: warning: jobserver unavailable: using -j1.  Add '+' to parent make 
rule.
gcc -Wdate-time -D_FORTIFY_SOURCE=2 -MMD -MF /<>/src/.bart.d -iquote /<>/src/ -DUSE_CUDA 
-I/usr//include -I/usr//include/ -I/usr//include -DFFTWTHREADS -DMAIN_LIST="avg, bench, bin, bitmask, cabs, caldir, calmat, carg, casorati, cc, 
ccapply, cdf97, circshift, conj, conv, copy, cpyphs, creal, crop, delta, ecalib, ecaltwo, estdelay, estdims, estshift, estvar, extract, fakeksp, fft, 
fftmod, fftrot, fftshift, filter, flatten, flip, fmac, homodyne, index, invert, itsense, join, looklocker, lrmatrix, mandelbrot, mip, moba, nlinv, 
noise, normalize, nrmse, nufft, ones, pattern, phantom, pics, pocsense, poisson, poly, repmat, reshape, resize, rmfreq, rof, rss, rtnlinv, sake, 
saxpy, scale, sdot, show, slice, spow, sqpics, squeeze, ssa, std, svd, tgv, threshold, toimg, traj, transpose, twixread, upat, var, vec, version, 
walsh, wave, wavelet, wavepsf, whiten, window, wshfl, zeros, zexp, ()" -include src/main.h -g -O2 
-ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -std=gnu11 -fopenmp -c -o 
/<>/src/bart.o /<>/src/bart.c
gcc -Wdate-time -D_FORTIFY_SOURCE=2 -MMD -MF src/.show.d -iquote /<>/src/ -DUSE_CUDA 
-I/usr//include -I/usr//include/ -I/usr//include -DFFTWTHREADS -DMAIN_LIST="avg, bench, bin, bitmask, cabs, 
caldir, calmat, carg, casorati, cc, ccapply, cdf97, circshift, conj, conv, copy, cpyphs, creal, crop, delta, 
ecalib, ecaltwo, estdelay, estdims, estshift, estvar, extract, fakeksp, fft, fftmod, fftrot, fftshift, filter, 
flatten, flip, fmac, homodyne, index, invert, itsense, join, looklocker, lrmatrix, mandelbrot, mip, moba, nlinv, 
noise, normalize, nrmse, nufft, ones, pattern, phantom, pics, pocsense, poisson, poly, repmat, reshape, resize, 
rmfreq, rof, rss, rtnlinv, sake, saxpy, scale, sdot, show, slice, spow, sqpics, squeeze, ssa, std, svd, tgv, 
threshold, toimg, traj, transpose, twixread, upat, var, vec, version, walsh, wave, wavelet, wavepsf, whiten, 
window, wshfl, zeros, zexp, ()" -include src/main.h -g -O2 -ffile-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -std=gnu11 -fopenmp -c -o src/show.o src/show.c
./ar_lock.sh rsU lib/libbox.a src/show.o
ar: creating lib/libbox.a
gcc -Wdate-time -D_FORTIFY_SOURCE=2 -MMD -MF src/.slice.d -iquote /<>/src/ -DUSE_CUDA 
-I/usr//include -I/usr//include/ -I/usr//include -DFFTWTHREADS -DMAIN_LIST="avg, bench, bin, bitmask, cabs, 
caldir, calmat, carg, casorati, cc, ccapply, cdf97, circshift, conj, conv, copy, cpyphs, creal, crop, delta, 
ecalib, ecaltwo, estdelay, estdims, estshift, estvar, extract, fakeksp, fft, fftmod, fftrot, fftshift, filter, 
flatten, flip, fmac, homodyne, index, invert, itsense, join, looklocker, lrmatrix, mandelbrot, mip, moba, nlinv, 
noise, normalize, nrmse, nufft, ones, pattern, phantom, pics, pocsense, poisson, poly, repmat, reshape, resize, 
rmfreq, rof, rss, rtnlinv, sake, saxpy, scale, sdot, show, slice, spow, sqpics, squeeze, ssa, std, svd, tgv, 
threshold, toimg, traj, transpose, twixread, upat, var, vec, version, walsh, wave, wavelet, wavepsf, whiten, 
window, wshfl, zeros, zexp, ()" -include src/main.h -g -O2 -ffile-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -std=gnu11 -fopenmp -c -o src/slice.o src/slice.c
./ar_lock.sh rsU lib/libbox.a src/slice.o
[...]
gcc -Wl,-z,relro -Wl,-z,now -rdynamic -rdynamic -g -O2 -ffile-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -std=gnu11 -fopenmp -Wdate-time -D_FORTIFY_SOURCE=2 
-MMD -MF ./.test_prox.d -iquote /<>/src/ -DUSE_CUDA -I/usr//include -I/usr//include/ 
-I/usr//include -DFFTWTHREADS -DUTESTS="call_test_thresh, call_test_auto_norm," -o test_prox 
utests/utest.c utests/test_prox.o lib/libiter.a lib/liblinops.a lib/libnum.a lib/libmisc.a lib/libnum.a 
lib/libmisc.a -L/usr//lib -lfftw3f -lfftw3f_threads -L/usr//lib -lcufft -lcudart -lcublas -lstdc++ -Wl,-rpath 
/usr//lib -L/usr//lib -llapacke -lblas  -lm
./test_linop_matrix
 ./test_linop_matrix:  4/ 4 passed.
./test_linop
./test_linop:  3/ 3 passed.
./test_batchsvd
 ./test_batchsvd:  2/ 2 passed.
./test_pattern
  ./test_pattern:  1/ 1 passed.
./test_types
./test_types:  2/ 2 passed.
./test_misc
 ./test_misc:  2/ 2 passed.
./test_moba
 ./test_moba:  1/ 1 passed.
./test_nlop
 ./test_nlop: 15/15 passed.

Bug#1069322: diffoscope crashes when trying to compare unreproducible src:dasel build artifacts

[Chris Lamb]

Holger Levsen wrote:

> I'm attaching the crashing artifacts now to this bug report, however minus
> the orig.tar.gz files, though I suppose that the .deb files are enough to
> crash diffoscope anyway...

Hm, I can't seem to reproduce the crash with these files. In the first
instance, can you paste a traceback or similar of the crash in
question? Maybe it is fixable just from that without having to find
and upload more files, etc.


Best wishes,

-- 
  ,''`.
 : :'  : Chris Lamb
 `. `'`  la...@debian.org  chris-lamb.co.uk
   `-

Bug#1070756: ibus-hangul does not work after installing debian-security updates.

[Kee, No-Wook]

Package: ibus-hangul
Version: 1.5.4-2
Severity: normal
Tags: l10n
X-Debbugs-Cc: lusc...@gmail.com

ibus-hangul does not work after installing debian-security updates.
The packages updated today are as follows.
I found the same issue on two different machines and submitted a bug report.

The package update details are below.

# apt update
# apt upgrade

After this operation, 408 MB of additional disk space will be used.
Do you want to continue? [Y/n]
Get:1 http://security.debian.org/debian-security bookworm-security/main amd64
libc6-i386 amd64 2.36-9+deb12u7 [2,460 kB]
Get:2 https://deb.nodesource.com/node_20.x nodistro/main amd64 nodejs amd64
20.13.0-1nodesource1 [31.6 MB]
Get:3 http://security.debian.org/debian-security bookworm-security/main amd64
libc-devtools amd64 2.36-9+deb12u7 [53.4 kB]
Get:4 http://security.debian.org/debian-security bookworm-security/main amd64
libc6-dev amd64 2.36-9+deb12u7 [1,899 kB]
Get:5 https://dl.google.com/linux/chrome/deb stable/main amd64 google-chrome-
stable amd64 124.0.6367.155-1 [107 MB]
Get:6 http://security.debian.org/debian-security bookworm-security/main amd64
libc-dev-bin amd64 2.36-9+deb12u7 [45.8 kB]
Get:7 http://security.debian.org/debian-security bookworm-security/main amd64
linux-libc-dev amd64 6.1.90-1 [1,976 kB]
Get:8 http://security.debian.org/debian-security bookworm-security/main amd64
libc6-dbg amd64 2.36-9+deb12u7 [7,462 kB]
Get:9 http://security.debian.org/debian-security bookworm-security/main amd64
libc6 amd64 2.36-9+deb12u7 [2,758 kB]
Get:10 http://security.debian.org/debian-security bookworm-security/main amd64
libc-bin amd64 2.36-9+deb12u7 [607 kB]
Get:11 http://security.debian.org/debian-security bookworm-security/main amd64
libglib2.0-data all 2.74.6-2+deb12u1 [1,209 kB]
Get:12 http://security.debian.org/debian-security bookworm-security/main amd64
libglib2.0-bin amd64 2.74.6-2+deb12u1 [110 kB]
Get:13 http://security.debian.org/debian-security bookworm-security/main amd64
libglib2.0-0 amd64 2.74.6-2+deb12u1 [1,401 kB]
Get:14 http://security.debian.org/debian-security bookworm-security/main amd64
less amd64 590-2.1~deb12u2 [132 kB]
Get:15 http://security.debian.org/debian-security bookworm-security/main amd64
libc-l10n all 2.36-9+deb12u7 [675 kB]
Get:16 http://security.debian.org/debian-security bookworm-security/main amd64
locales all 2.36-9+deb12u7 [3,902 kB]
Get:17 http://security.debian.org/debian-security bookworm-security/main amd64
glibc-doc all 2.36-9+deb12u7 [3,476 kB]
Get:18 http://security.debian.org/debian-security bookworm-security/main amd64
gnome-shell-extension-prefs amd64 43.9-0+deb12u2 [28.3 kB]
Get:19 http://security.debian.org/debian-security bookworm-security/main amd64
gnome-shell amd64 43.9-0+deb12u2 [856 kB]
Get:20 http://security.debian.org/debian-security bookworm-security/main amd64
gnome-shell-common all 43.9-0+deb12u2 [799 kB]
Get:21 http://security.debian.org/debian-security bookworm-security/main amd64
libruby3.1 amd64 3.1.2-7+deb12u1 [5,400 kB]
Get:22 http://security.debian.org/debian-security bookworm-security/main amd64
linux-image-6.1.0-21-amd64 amd64 6.1.90-1 [68.8 MB]
Get:23 http://security.debian.org/debian-security bookworm-security/main amd64
linux-image-amd64 amd64 6.1.90-1 [1,476 B]
Get:24 http://security.debian.org/debian-security bookworm-security/main amd64
ruby3.1 amd64 3.1.2-7+deb12u1 [663 kB]
Fetched 243 MB in 22s (11.2 MB/s)


-- Package-specific info:
XMODIFIERS=@im=ibus
CLUTTER_IM_MODULE=
GTK_IM_MODULE=
QT_IM_MODULE=ibus
WAYLAND_DISPLAY=wayland-0
XDG_CURRENT_DESKTOP=GNOME
XDG_MENU_PREFIX=gnome-
XDG_RUNTIME_DIR=/run/user/1000
XDG_SEAT=
XDG_SESSION_CLASS=user
XDG_SESSION_DESKTOP=gnome
XDG_SESSION_ID=
XDG_SESSION_TYPE=wayland

=== gsettings list-recursively org.gnome.desktop.input-sources ===
org.gnome.desktop.input-sources current uint32 0
org.gnome.desktop.input-sources mru-sources @a(ss) []
org.gnome.desktop.input-sources per-window false
org.gnome.desktop.input-sources show-all-sources false
org.gnome.desktop.input-sources sources [('ibus', 'hangul')]
org.gnome.desktop.input-sources xkb-options @as []

=== gsettings list-recursively org.freedesktop.ibus.engine.hangul ===
org.freedesktop.ibus.engine.hangul auto-reorder true
org.freedesktop.ibus.engine.hangul disable-latin-mode false
org.freedesktop.ibus.engine.hangul hangul-keyboard '2'
org.freedesktop.ibus.engine.hangul hanja-keys 'Hangul_Hanja,F9'
org.freedesktop.ibus.engine.hangul initial-input-mode 'latin'
org.freedesktop.ibus.engine.hangul off-keys 'Escape'
org.freedesktop.ibus.engine.hangul on-keys ''
org.freedesktop.ibus.engine.hangul preedit-mode 'syllable'
org.freedesktop.ibus.engine.hangul switch-keys 'Hangul'
org.freedesktop.ibus.engine.hangul use-event-forwarding true
org.freedesktop.ibus.engine.hangul word-commit false


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

Kernel: Linux 6.1.0-21-amd64 

Bug#1070752: Symbols missing - glib2.0 update - Bookworm+Gnome

[Simon McVittie]

Control: forwarded -1 https://gitlab.gnome.org/GNOME/glib/-/merge_requests/4053
Control: tags -1 + pending

On Wed, 08 May 2024 at 10:42:21 -0300, Pedro Carvalho wrote:
> After upgrading to version 2.74.6-2+deb12u1, I have noticed the following
> symbols are missing for some applications:
> 
> ´ ` ^ ~

This is the same issue as #1070730, #1070736, #1070743, #1070745 and
#1070749. We do not need any more reports of this regression, and I am
fixing it as fast as I can. Each GLib build takes around an hour,
plus the time required for testing, so it is not possible to fix this
instantaneously.

For users of Debian 12 'bookworm', a test-build of a fix for this
regression is available here: https://people.debian.org/~smcv/bug1070730/
(amd64 + i386 + source).

I've contacted the security team about releasing this regression fix
officially as 2.74.6-2+deb12u2, but that cannot be done without their
permission.

Debian 11 'bullseye' is in the same situation as Debian 12 'bookworm'.
A test-build for that release is not yet available. I'll upload one when
available, if the security team doesn't get back to me first.

smcv

Bug#1070742: firefox: No characters after ~ (0x7f) in text zones

[Nicolas Patrois]

Package: firefox
Version: 125.0.3-1
Followup-For: Bug #1070742

Dear Maintainer,

In fact, the bug is caused by the latest libglib2.0-* update.
See https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1070736

Yours,
nicolas patrois


-- Package-specific info:


-- Addons package information

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

Kernel: Linux 5.16.0-6-686-pae (SMP w/3 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), 
LANGUAGE=fr_FR:fr:en_GB:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages firefox depends on:
ii  debianutils  5.17
ii  fontconfig   2.15.0-1.1
ii  libasound2t641.2.11-1+b1
ii  libatk1.0-0t64   2.52.0-1
ii  libc62.38-8
ii  libcairo-gobject21.18.0-3+b1
ii  libcairo21.18.0-3+b1
ii  libdbus-1-3  1.14.10-4+b1
ii  libevent-2.1-7t642.1.12-stable-8.1+b3
ii  libffi8  3.4.6-1
ii  libfontconfig1   2.15.0-1.1
ii  libfreetype6 2.13.2+dfsg-1+b4
ii  libgcc-s114-20240429-1
ii  libgdk-pixbuf-2.0-0  2.42.10+dfsg-3+b3
ii  libglib2.0-0t64  2.80.0-10
ii  libgtk-3-0t643.24.41-4
ii  libnspr4 2:4.35-1.1+b1
ii  libnss3  2:3.99-1
ii  libpango-1.0-0   1.52.2+ds-1
ii  libstdc++6   14-20240429-1
ii  libvpx8  1.13.1-2+b1
ii  libx11-6 2:1.8.7-1+b1
ii  libx11-xcb1  2:1.8.7-1+b1
ii  libxcb-shm0  1.17.0-1
ii  libxcb1  1.17.0-1
ii  libxcomposite1   1:0.4.5-1+b1
ii  libxdamage1  1:1.1.6-1+b1
ii  libxext6 2:1.3.4-1+b1
ii  libxfixes3   1:6.0.0-2+b1
ii  libxrandr2   2:1.5.4-1
ii  procps   2:4.0.4-4
ii  zlib1g   1:1.3.dfsg-3.1

Versions of packages firefox recommends:
ii  libavcodec53  7:0.10.3-dmo1
ii  libavcodec54  10:1.2.6-dmo4
ii  libavcodec55  10:2.3.3-dmo3
ii  libavcodec56  10:2.8.6-dmo2
ii  libavcodec57  10:3.4.2-dmo3
ii  libavcodec60  10:6.1.1-dmo4

Versions of packages firefox suggests:
ii  fonts-lmodern  2.005-1
ii  fonts-stix [otf-stix]  1.1.1-5
ii  libcanberra0   0.30-17
ii  libgssapi-krb5-2   1.20.1-6+b1
ii  otf-stix   1.1.1-1
ii  pulseaudio 16.1+dfsg1-5

-- no debconf information

Bug#1070754: gensio: please make the build reproducible

[Chris Lamb]

Source: gensio
Version: 2.8.2-6.1
Severity: wishlist
Tags: patch
User: reproducible-bui...@lists.alioth.debian.org
Usertags: environment buildpath
X-Debbugs-Cc: reproducible-b...@lists.alioth.debian.org

Hi,

Whilst working on the Reproducible Builds effort [0], we noticed that
gensio could not be built reproducibly.

This is because some shell script wrappers for some files shipped
under examples/ were not reproducible. A patch is attached — I think
that we were simply missing a couple of files to remove.

An alternative might be something like:

 find debian/**/examples/ -type f -executable -delete

 [0] https://reproducible-builds.org/


Regards,

-- 
  ,''`.
 : :'  : Chris Lamb
 `. `'`  la...@debian.org / chris-lamb.co.uk
   ` a/debian/rules  2024-05-08 14:35:03.861131982 +0100
--- b/debian/rules  2024-05-08 14:46:45.619810890 +0100
@@ -41,7 +41,9 @@
  
debian/libgensio-dev/usr/share/doc/libgensio-dev/examples/basic_client \
  
debian/libgensio-dev/usr/share/doc/libgensio-dev/examples/basic_server \
  
debian/libgensio-dev/usr/share/doc/libgensio-dev/examples/basic_server_sync \
- 
debian/libgensio-dev/usr/share/doc/libgensio-dev/examples/basic_server_sync_fork
+ 
debian/libgensio-dev/usr/share/doc/libgensio-dev/examples/basic_server_sync_fork
 \
+ 
debian/libgensio-dev/usr/share/doc/libgensio-dev/examples/poll_and_gensio \
+ debian/libgensio-dev/usr/share/doc/libgensio-dev/examples/use_iods
mkdir debian/libgensio-dev/usr/share/doc/libgensio-dev/examples/c++
cp c++/examples/* 
debian/libgensio-dev/usr/share/doc/libgensio-dev/examples/c++
rm -rf \

Bug#962508: switch libcurl to openssl by default

[Fabian Grünbichler]

On Mon, 08 Jun 2020 19:16:27 -0400 Harlan Lieberman-Berg  wrote:
> Package: cargo
> Version: 0.43.1-3
> Severity: wishlist
> 
> Hello fellow Rustaceans!
> 
> Because cargo has a direct dependency on OpenSSL, it seems logical that we
> should switch the priority of openssl and gnutls so Cargo, at least by 
> default,
> isn't building against two different TLS implementations.
> 
> This is especially important considering GnuTLS has had some painful security
> incidents recently: CVE-2020-13777 in particular.
> 
> Should just require switching the order of the libcurl dep in d/control.

Hi,

took a look at this while going through bug backlog. Unfortunately it's not as 
easy - switching the direct cargo->gnutls dep around to use the openssl variant 
works, but
- libgit2 pulls in mbedtls
- curl itself pulls in gnutls and nettle (via librtmp1), even in the openssl 
variant

if those are fixed at some point, switching over seems sensible. 

libgit2 is in the process of being replaced upstream with gix, but I suspect 
that will still take a while to be completed.

Bug#1070753: Can't see PPPoE concentrators via d-i but pppoe-discovery can

[Steven Maddox]

Package: ppp-deb

To recreate this issue... boot the latest Debian 12 netinst ISO and at 
the boot menu hit escape then at the boot: prompt type in...


installgui modules=ppp-udeb

Then d-i will start and after choosing language etc... it'll try to find 
any see PPPoE concentrators and say they're not detected.


After you can go to 'Execute a shell' and you'll find that they're 
actually there and it shouldn't be a problem...


~ # ip link set ens192 up
~ # pppoe-discover -I ens192
   Service-Name: datasuite12.13
Access-Concentrator: datasuite12.13
AC-Ethernet-Address: 00:03:97:40:00:3e
--
   Service-Name: datasuite12.13
Access-Concentrator: datasuite12.13
AC-Ethernet-Address: 00:03:97:3d:80:2b
--

I even made a stupid animated GIF to show these steps in action...

https://5r.tf/temp-bugging-me-files/debian-pppoe-broke.gif

It seems someone else 14 years ago wrote about this in bug #587850 but 
nothing was resolved and he was told to talk to his ISP.


In this case I work for the ISP, so I'm pretty confident in the fact 
that the PPPoE concentrator is there.


I can do more tests if you've got idea where to go from here.

--
Steven Maddox
Lantizia

Bug#1070752: Symbols missing - glib2.0 update - Bookworm+Gnome

[Pedro Carvalho]

Package: glib2.0

Version: 2.74.6-2+deb12u1


After upgrading to version 2.74.6-2+deb12u1, I have noticed the 
following symbols are missing for some applications:


´ ` ^ ~

There is no output for the correspondent key in Gnome text editor and 
LibreOffice. But there is no issue with Mozilla Firefox and Thundebird.


I have donwgraded the package to version 2.74.6-2 and found no issue for 
any application.


My configuration for the input method is:

* Default mode defined in /etc/default/im-config: 'auto'

* Active configuration: 'default' (normally missing)

* Normal automatic choice: 'ibus' (normally ibus or fcitx5)

* Override rule: 'zh_CN,fcitx5:zh_TW,fcitx5:zh_HK,fcitx5:zh_SG,fcitx5'

* Current override choice: '' (Locale='pt_BR')

* Current automatic choice: 'ibus'

* Number of valid choices: 1 (normally 1)

* Desktop environment: 'GNOME'


I am using Debian GNU/Linux 12, kernel 6.1.0-21-amd64 and libc6 
2.36-9+deb12u7.

Bug#1070751: transition: libxlsxwriter

[Boyuan Yang]

Package: release.debian.org
Control: affects -1 + src:libxlsxwriter
X-Debbugs-Cc: libxlsxwri...@packages.debian.org
User: release.debian@packages.debian.org
Usertags: transition
X-Debbugs-Cc: by...@debian.org
Severity: normal

I would like to launch the transition as listed below:

* https://release.debian.org/transitions/html/auto-libxlsxwriter.html

The transition is triggered by the SONAME bump.

List of all affected packages:

* src:deepin-log-viewer (OK)
* src:readstat (OK)

All reverse build-dependencies can be successfully rebuilt with the
new libxlsxwriter.

Ben file:

(please reuse the auto-libxlsxwriter tracker.)


Thanks,
Boyuan Yang


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

Bug#1064516: Debdifffs for ruby-rack DSA

[Adrian Bunk]

Hi,

attached are debdiffs for a ruby-rack DSA,
with the same fixes as in sid and buster.

cu
Adrian
diffstat for ruby-rack-2.1.4 ruby-rack-2.1.4

 changelog  |   10 +
 patches/0001-Avoid-2nd-degree-polynomial-regexp-in-MediaType.patch |   51 
++
 patches/0002-Return-an-empty-array-when-ranges-are-too-large.patch |   46 
+
 patches/0003-Fixing-ReDoS-in-header-parsing.patch  |   30 +
 patches/series |3 
 5 files changed, 140 insertions(+)

diff -Nru ruby-rack-2.1.4/debian/changelog ruby-rack-2.1.4/debian/changelog
--- ruby-rack-2.1.4/debian/changelog2023-06-08 00:52:23.0 +0300
+++ ruby-rack-2.1.4/debian/changelog2024-05-02 23:46:12.0 +0300
@@ -1,3 +1,13 @@
+ruby-rack (2.1.4-3+deb11u2) bullseye-security; urgency=medium
+
+  * Non-maintainer upload.
+  * CVE-2024-25126: ReDoS in Content Type header parsing
+  * CVE-2024-26141: Reject Range headers which are too large
+  * CVE-2024-26146: ReDoS in Accept header parsing
+  * Closes: #1064516
+
+ -- Adrian Bunk   Thu, 02 May 2024 23:46:12 +0300
+
 ruby-rack (2.1.4-3+deb11u1) bullseye-security; urgency=high
 
   * Add patch to restrict broken mime parsing.
diff -Nru 
ruby-rack-2.1.4/debian/patches/0001-Avoid-2nd-degree-polynomial-regexp-in-MediaType.patch
 
ruby-rack-2.1.4/debian/patches/0001-Avoid-2nd-degree-polynomial-regexp-in-MediaType.patch
--- 
ruby-rack-2.1.4/debian/patches/0001-Avoid-2nd-degree-polynomial-regexp-in-MediaType.patch
   1970-01-01 02:00:00.0 +0200
+++ 
ruby-rack-2.1.4/debian/patches/0001-Avoid-2nd-degree-polynomial-regexp-in-MediaType.patch
   2024-05-02 23:46:12.0 +0300
@@ -0,0 +1,51 @@
+From bad2b5be29349b285e08d343f060f7c18065d416 Mon Sep 17 00:00:00 2001
+From: Jean Boussier 
+Date: Wed, 6 Dec 2023 18:32:19 +0100
+Subject: Avoid 2nd degree polynomial regexp in MediaType
+
+---
+ lib/rack/media_type.rb | 13 +
+ 1 file changed, 9 insertions(+), 4 deletions(-)
+
+diff --git a/lib/rack/media_type.rb b/lib/rack/media_type.rb
+index 41937c99..7fc1e39d 100644
+--- a/lib/rack/media_type.rb
 b/lib/rack/media_type.rb
+@@ -4,7 +4,7 @@ module Rack
+   # Rack::MediaType parse media type and parameters out of content_type string
+ 
+   class MediaType
+-SPLIT_PATTERN = %r{\s*[;,]\s*}
++SPLIT_PATTERN = /[;,]/
+ 
+ class << self
+   # The media type (type/subtype) portion of the CONTENT_TYPE header
+@@ -15,7 +15,11 @@ module Rack
+   # http://www.w3.org/Protocols/rfc2616/rfc2616-sec3.html#sec3.7
+   def type(content_type)
+ return nil unless content_type
+-content_type.split(SPLIT_PATTERN, 2).first.tap &:downcase!
++if type = content_type.split(SPLIT_PATTERN, 2).first
++  type.rstrip!
++  type.downcase!
++  type
++end
+   end
+ 
+   # The media type parameters provided in CONTENT_TYPE as a Hash, or
+@@ -27,9 +31,10 @@ module Rack
+ return {} if content_type.nil?
+ 
+ content_type.split(SPLIT_PATTERN)[1..-1].each_with_object({}) do |s, 
hsh|
++  s.strip!
+   k, v = s.split('=', 2)
+-
+-  hsh[k.tap(&:downcase!)] = strip_doublequotes(v)
++  k.downcase!
++  hsh[k] = strip_doublequotes(v)
+ end
+   end
+ 
+-- 
+2.30.2
+
diff -Nru 
ruby-rack-2.1.4/debian/patches/0002-Return-an-empty-array-when-ranges-are-too-large.patch
 
ruby-rack-2.1.4/debian/patches/0002-Return-an-empty-array-when-ranges-are-too-large.patch
--- 
ruby-rack-2.1.4/debian/patches/0002-Return-an-empty-array-when-ranges-are-too-large.patch
   1970-01-01 02:00:00.0 +0200
+++ 
ruby-rack-2.1.4/debian/patches/0002-Return-an-empty-array-when-ranges-are-too-large.patch
   2024-05-02 23:46:12.0 +0300
@@ -0,0 +1,46 @@
+From ef52af28b6ac43789fd8fc05df098b56f220f0fa Mon Sep 17 00:00:00 2001
+From: Aaron Patterson 
+Date: Tue, 13 Feb 2024 13:34:34 -0800
+Subject: Return an empty array when ranges are too large
+
+If the sum of the requested ranges is larger than the file itself,
+return an empty array. In other words, refuse to respond with any bytes.
+
+[CVE-2024-26141]
+---
+ lib/rack/utils.rb  | 3 +++
+ test/spec_utils.rb | 4 
+ 2 files changed, 7 insertions(+)
+
+diff --git a/lib/rack/utils.rb b/lib/rack/utils.rb
+index 16457f90..87c2a946 100644
+--- a/lib/rack/utils.rb
 b/lib/rack/utils.rb
+@@ -382,6 +382,9 @@ module Rack
+ end
+ ranges << (r0..r1)  if r0 <= r1
+   end
++
++  return [] if ranges.map(&:size).sum > size
++
+   ranges
+ end
+ module_function :get_byte_ranges
+diff --git a/test/spec_utils.rb b/test/spec_utils.rb
+index 5fd92241..67b77b0d 100644
+--- a/test/spec_utils.rb
 b/test/spec_utils.rb
+@@ -548,6 +548,10 @@ describe Rack::Utils, "cookies" do
+ end
+ 
+ describe Rack::Utils, "byte_range" do
++  it "returns an empty list if the sum of the ranges is too large" do
++

Bug#1037084: bookworm: When using gdm3 to start non-GNOME wayland sessions, PATH may be set differently

[Sam Hartman]

> "Santiago" == Santiago Vila  writes:

Santiago> Hello.  My plan for base-files is to stop overriding the
Santiago> PATH in /etc/profile.

Santiago> Ubuntu did that a long time ago and it's probably the
Santiago> right thing to do.

I'd be happy to pick up the Ubuntu patch to include PATH in
/etc/environment for libpam-modules.


signature.asc
Description: PGP signature

Bug#1070749: libglib2.0-0t64: Update 2.80.0-9 to 2.80.0-10 breaks compose

[Simon McVittie]

Control: forwarded -1 https://gitlab.gnome.org/GNOME/glib/-/merge_requests/4053
Control: tags -1 + pending

On Wed, 08 May 2024 at 14:11:32 +0200, Hannah Stern wrote:
>  Set the "<>" key (German keyboard) to compose (xmodmap), in combination
>  with an US keyboard layout. Type compose " a in order to insert
> a-umlaut,
>  in programs like gvim, thunderbird, firefox. (In xterm it works.)

This is the same issue as #1070730, #1070736, #1070743, #1070745. I'm
fixing this as fast as I can, please be patient.

smcv

Bug#1070723: bullseye-pu: package bart/0.6.00-3+deb11u1

[Andreas Tille]

Am Wed, May 08, 2024 at 01:18:44AM +0200 schrieb Santiago Vila:
> Package: release.debian.org
> Severity: normal
> Tags: bullseye
> User: release.debian@packages.debian.org
> Usertags: pu
> X-Debbugs-Cc: b...@packages.debian.org, sanv...@debian.org
> Control: affects -1 + src:bart
> 
> [ Reason ]
> This upload fixes Bug #1026061 FTBFS randomly in bullseye.

Thanks a lot Santiago for your great QA work

Andreas.

-- 
https://fam-tille.de

Bug#1070704: More info

[Luca Boccassi]

On Wed, 8 May 2024 12:00:34 +0200 Roderich Schupp
 wrote:
> I just saw that the missing libkmod (dlopen'ed by udevadm) is already
taken
> care of by /usr/share/initramfs-tools/hooks/udev.
> 
> In case you're wondering what caused libsystemd.so.0 to be included
> in my initrd-img: it's linked by /usr/sbin/lvm which gets added by
> /usr/share/initramfs-tools/hooks/lvm2
> 
> Cheers, Roderich

Again, what was the issue exactly? kmod is already taken care of, that
leaves gcrypt or lz4 which are only used for the journal, why would the
abscence of those cause issues for cryptsetup? What was the actual
error and what actually fixed it, precisely?

-- 
Kind regards,
Luca Boccassi

Bug#1070750: eza not built with git support

[kernelb00t]

Package: eza
Version: 0.18.14
Severity: important

When running eza with eza --git:

eza: Options --git and --git-ignore can't be used because `git` feature was 
disabled in this build of exa

This prevents eza to list the directories, and so affects aliases redirecting 
ls.
For info, I have oh-my-zsh with git and eza plugins, with other ones unrelated.

-- System Information:
Debian Release: 12.5
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 'stable')
Architecture: arm64 (aarch64)
Foreign Architectures: armhf

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

Versions of packages eza depends on:
ii  libc6  2.36-9+rpt2+deb12u7

eza recommends no packages.

eza suggests no packages.

-- no debconf information

Bug#1062105: should not block migration to testing

[Hans-Christoph Steiner]

control: severity -1 normal

Thanks for reporting!  In the Android Tools case, the shared libs and packages 
that use them are packaged together, often from the same source package, so I 
can't see why we'd need special versions of it. And when we need to, we can use 
strictly versioned depends, so it should be fine. I'm going to set the bug to 
normal for now.

Bug#1070749: libglib2.0-0t64: Update 2.80.0-9 to 2.80.0-10 breaks compose

[Hannah Stern]

Package: libglib2.0-0t64
Version: 2.80.0-10
Severity: important
X-Debbugs-Cc: hannah.st...@1und1.de

Dear Maintainer,


   * What led up to the situation?
 - Upgrading 2.80.0-9 to -10 (using aptitude -t unstable)
 - (Downgrade of libglib2.0-0t64 and gir1.2-glib-2.0 to -9 fixes 
the issue)

   * What exactly did you do (or not do) that was effective (or
 ineffective)?
 Set the "<>" key (German keyboard) to compose (xmodmap), in 
combination
 with an US keyboard layout. Type compose " a in order to insert 
a-umlaut,

 in programs like gvim, thunderbird, firefox. (In xterm it works.)
   * What was the outcome of this action?
 Nothing happens
   * What outcome did you expect instead?
 Insert a-umlaut

-- System Information:
Debian Release: trixie/sid
  APT prefers stable-security
  APT policy: (550, 'stable-security'), (550, 'stable'), (500, 
'stable-updates'), (500, 'oldstable'), (99, 'unstable'), (98, 
'testing'), (50, 'experimental')

Architecture: amd64 (x86_64)

Kernel: Linux 6.7.12-amd64 (SMP w/16 CPU threads; PREEMPT)
Kernel taint flags: TAINT_WARN, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
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 libglib2.0-0t64 depends on:
ii  libc6 2.38-8
ii  libffi8   3.4.6-1
ii  libmount1 2.40-8
ii  libpcre2-8-0  10.42-4+b1
ii  libselinux1   3.5-2+b2
ii  zlib1g1:1.3.dfsg-3.1

Versions of packages libglib2.0-0t64 recommends:
pn  libglib2.0-data   
ii  shared-mime-info  2.4-4
ii  xdg-user-dirs 0.18-1

Versions of packages libglib2.0-0t64 suggests:
pn  low-memory-monitor  

-- no debconf information

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

[Mark Hindley]

Control: tags -1 moreinfo

Michael and Steve,

I would appreciate some help here.

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

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

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

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

is empty.

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

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

I am reluctant to implement this change unnecessarily.

I would appreciate you expertise and guidance.

Many thanks

Mark

Bug#1070730: etc.: libglib2.0-0: ibus input regression

[Simon McVittie]

On Wed, 08 May 2024 at 03:48:21 +, unfathomabl...@protonmail.com wrote:
> Latest upgrade from 2.74.6-2 to 2.74.6-2+deb12u1 broke input of Japanese
> characters GTK programs (such as firefox, gedit etc).

For users of testing/unstable, this will be fixed as soon as I can,
probably by version 2.80.1-1. Each GLib build takes around an hour,
plus the time required for testing, so it is not possible to fix this
instantaneously.

For users of Debian 12 'bookworm', a test-build of a fix for this
regression is available here: https://people.debian.org/~smcv/bug1070730/
(amd64 + i386 + source)

I've contacted the security team about releasing this regression fix
officially as 2.74.6-2+deb12u2, but that cannot be done without their
permission.

Debian 11 'bullseye' is in the same situation as Debian 12 'bookworm'.
A test-build for that release is not yet available. I'll upload one when
available, if the security team doesn't get back to me first.

On Wed, 08 May 2024 at 10:10:48 +0200, Arne Nordmark wrote:
> Another thing that might well be the same underlying problem:
> 
> Using version 2.74.6-2+deb12u1, a Compose sequence like 'Compose " a' enters
> nothing in gnome-terminal and emacs.
> 
> Using version 2.74.6-2, the same sequence enters an "ä".

All non-trivial input methods in GNOME involve ibus, so the Compose key
and dead keys will also be affected by this regression.

smcv

Bug#1068170: re: 'rust-apr: FTBFS on non-amd64/mips64el: error[E0308]: arguments to this function are incorrect'

[Steve Capper]

Hello,
For info…
The signed-ness of char issues have been fixed upstream here:
https://github.com/jelmer/apr-rs/commit/9ac891f205cb27a907b52860ce1741e1a5347135

By utilising std::ffi::c_char.

Cheers,
--
Steve Capper

Bug#1070748: gqrx-sdr: it does not start

[Renzo Davoli]

Package: gqrx-sdr
Version: 2.17.5-1+b1
Severity: important
X-Debbugs-Cc: re...@cs.unibo.it

Dear Maintainer,

* What led up to the situation?
update to  2.17.5-1
* What exactly did you do (or not do) that was effective (or ineffective)?
I just tried to run it
* What was the outcome of this action?
It returns the following error:

terminate called after throwing an instance of 'std::runtime_error'
  what():  rpcmanager: Aggregator not in use, and a rpc booter is already 
registered
Aborted

thank yoy,
 renzo

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

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

Versions of packages gqrx-sdr depends on:
ii  libc62.38-8
ii  libgcc-s114-20240429-1
ii  libgnuradio-analog3.10.103.10.10.0-1
ii  libgnuradio-blocks3.10.103.10.10.0-1
ii  libgnuradio-digital3.10.10   3.10.10.0-1
ii  libgnuradio-fft3.10.10   3.10.10.0-1
ii  libgnuradio-filter3.10.103.10.10.0-1
ii  libgnuradio-network3.10.10   3.10.10.0-1
ii  libgnuradio-osmosdr0.2.0t64  0.2.5-2.1+b2
ii  libgnuradio-pmt3.10.10   3.10.10.0-1
ii  libgnuradio-runtime3.10.10   3.10.10.0-1
ii  libpulse016.1+dfsg1-5
ii  libqt6core6t64   6.4.2+dfsg-21.1+b1
ii  libqt6gui6t646.4.2+dfsg-21.1+b1
ii  libqt6network6t646.4.2+dfsg-21.1+b1
ii  libqt6svgwidgets66.4.2-4+b2
ii  libqt6widgets6t646.4.2+dfsg-21.1+b1
ii  libstdc++6   14-20240429-1
ii  libvolk3.1t643.1.2-1.1

gqrx-sdr recommends no packages.

gqrx-sdr suggests no packages.

-- no debconf information

Bug#1037084: bookworm: When using gdm3 to start non-GNOME wayland sessions, PATH may be set differently

[Yves-Alexis Perez]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

On Tue, 2024-05-07 at 01:28 +0200, Santiago Vila wrote:
> My plan for base-files is to stop overriding the PATH in /etc/profile.

Note that /etc/profile is a configuration file for bourne shells. While it's a
common path, it's not especially for other shells (I think zsh still uses it
but not all I think) and not graphical sessions.

Regards,
- -- 
Yves-Alexis
-BEGIN PGP SIGNATURE-

iQEzBAEBCAAdFiEE8vi34Qgfo83x35gF3rYcyPpXRFsFAmY7YGgACgkQ3rYcyPpX
RFvbsAf/dKuiRbySXE4iYEONIt3Exw4ZqeECQGovA/cCq7fSVpPN/qAtAM4oBFLD
oKXhS+UjePwkpST2JusYsWWwlaHgNOLixC+GbNEj8eNkylQve5SM+I+VMeWly63+
Zki3Lvfvr/JasaCzWBKLcsGcb/XdRfAOvco0D7YKZuHotTOI2/XaLgyjvCcnxXqT
Sp6z6/QzzbVSQYO1SL7MaghUGGpCqUuP5oHXqHjsR9bIOytg7rZoZfz/3dOmt/JI
gmktQjMppVED10He/h5TtsVpOOoatHmLkD9F0DqmfssEW2HPlPgK3OLcQnoWcPH1
G5m8rjNDZtt3+87L5wewE1Cc9bLz3A==
=Ravt
-END PGP SIGNATURE-

Bug#1070747: c-blosc2: FTBFS on ppc64el: error: implicit declaration of function ‘malloc’

[Sebastian Ramacher]

Source: c-blosc2
Version: 2.13.1+ds-3
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)
X-Debbugs-Cc: sramac...@debian.org

https://buildd.debian.org/status/fetch.php?pkg=c-blosc2=ppc64el=2.13.1%2Bds-3=1714853092=0

cd /<>/obj-powerpc64le-linux-gnu/blosc && /usr/bin/cc 
-DUSING_CMAKE -I/<>/obj-powerpc64le-linux-gnu/blosc 
-I/<>/include -I/<>/plugins/codecs/zfp/include 
-I/<>/blosc -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 
-Werror=implicit-function-declaration -ffile-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
-D_FORTIFY_SOURCE=2 -Wdate-time -D_FORTIFY_SOURCE=2  -std=gnu99 -O2 -g -DNDEBUG 
-fPIC -fvisibility=hidden -Wall -Wextra -MD -MT 
blosc/CMakeFiles/blosc2_static.dir/directories.c.o -MF 
CMakeFiles/blosc2_static.dir/directories.c.o.d -o 
CMakeFiles/blosc2_static.dir/directories.c.o -c 
/<>/blosc/directories.c
[ 37%] Building C object 
blosc/CMakeFiles/blosc_testing.dir/bitshuffle-altivec.c.o
cd /<>/obj-powerpc64le-linux-gnu/blosc && /usr/bin/cc 
-DBLOSC_SHARED_LIBRARY -DBLOSC_TESTING -DUSING_CMAKE 
-I/<>/obj-powerpc64le-linux-gnu/blosc -I/<>/include 
-I/<>/plugins/codecs/zfp/include -I/<>/blosc 
-Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 -Werror=implicit-function-declaration 
-ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -Wdate-time 
-D_FORTIFY_SOURCE=2  -std=gnu99 -O2 -g -DNDEBUG -Wall -Wextra 
-DNO_WARN_X86_INTRINSICS -MD -MT 
blosc/CMakeFiles/blosc_testing.dir/bitshuffle-altivec.c.o -MF 
CMakeFiles/blosc_testing.dir/bitshuffle-altivec.c.o.d -o 
CMakeFiles/blosc_testing.dir/bitshuffle-altivec.c.o -c 
/<>/blosc/bitshuffle-altivec.c
/<>/blosc/bitshuffle-altivec.c: In function 
‘bshuf_trans_bit_elem_altivec’:
/<>/blosc/bitshuffle-altivec.c:370:19: error: implicit declaration 
of function ‘malloc’ [-Werror=implicit-function-declaration]
  370 |   void* tmp_buf = malloc(size * elem_size);
  |   ^~
/<>/blosc/bitshuffle-altivec.c:32:1: note: include ‘’ or 
provide a declaration of ‘malloc’
   31 | #include "transpose-altivec.h"
  +++ |+#include 
   32 | 
/<>/blosc/bitshuffle-altivec.c:370:19: warning: incompatible 
implicit declaration of built-in function ‘malloc’ 
[-Wbuiltin-declaration-mismatch]
  370 |   void* tmp_buf = malloc(size * elem_size);
  |   ^~
/<>/blosc/bitshuffle-altivec.c:370:19: note: include ‘’ 
or provide a declaration of ‘malloc’
/<>/blosc/bitshuffle-altivec.c:380:3: error: implicit declaration 
of function ‘free’ [-Werror=implicit-function-declaration]
  380 |   free(tmp_buf);
  |   ^~~~
/<>/blosc/bitshuffle-altivec.c:380:3: note: include ‘’ 
or provide a declaration of ‘free’
/<>/blosc/bitshuffle-altivec.c:380:3: warning: incompatible 
implicit declaration of built-in function ‘free’ 
[-Wbuiltin-declaration-mismatch]
/<>/blosc/bitshuffle-altivec.c:380:3: note: include ‘’ 
or provide a declaration of ‘free’
/<>/blosc/bitshuffle-altivec.c: In function 
‘bshuf_untrans_bit_elem_altivec’:
/<>/blosc/bitshuffle-altivec.c:583:19: warning: incompatible 
implicit declaration of built-in function ‘malloc’ 
[-Wbuiltin-declaration-mismatch]
  583 |   void* tmp_buf = malloc(size * elem_size);
  |   ^~
/<>/blosc/bitshuffle-altivec.c:583:19: note: include ‘’ 
or provide a declaration of ‘malloc’
/<>/blosc/bitshuffle-altivec.c:590:3: warning: incompatible 
implicit declaration of built-in function ‘free’ 
[-Wbuiltin-declaration-mismatch]
  590 |   free(tmp_buf);
  |   ^~~~
/<>/blosc/bitshuffle-altivec.c:590:3: note: include ‘’ 
or provide a declaration of ‘free’

Cheers
-- 
Sebastian Ramacher

Bug#1056785: Removed package(s) from unstable

[Erlend Egeberg Aasland]

FYI, CPython is currently in the process of unvendoring libmpdecimal.
See https://github.com/python/cpython/issues/115119 for more info.
Starting with Python 3.13, configure will default to the system installed
libmpdecimal. The vendored copy is scheduled for removal in Python 3.15.


Erlend Aasland, CPython core dev

Bug#1070745: Re: Bug#1070745: Bug on Debian 12 Bookworm - Gnome-Shell / After today's upgrade, the dead keys on my keyboard no longer work

[pham...@bluewin.ch]

Thank you a thousand times Simon for your extremely quick response :)

I'm looking forward to the fix...

Good day to you.

Philippe


Message d'origine
De : s...@debian.org
Date : 08/05/2024 - 12:41 (E)
À : pham...@bluewin.ch, 1070...@bugs.debian.org
Objet : Re: Bug#1070745: Bug on Debian 12 Bookworm - Gnome-Shell / After 
today's upgrade, the dead keys on my keyboard no longer work

Control: reassign -1 libglib2.0-0 2.74.6-2+deb12u1
Control: affects -1 + gnome-shell

On Wed, 08 May 2024 at 11:42:10 +0200, pham...@bluewin.ch wrote:
> After today's update, the dead keys on my keyboard no longer work

This is a regression in GLib triggered by fixing CVE-2024-34397. I'm
testing a possible fix as rapidly as I can, but each GLib build takes
about an hour, so please be patient.

smcv

Bug#1070745: Bug on Debian 12 Bookworm - Gnome-Shell / After today's upgrade, the dead keys on my keyboard no longer work

[Simon McVittie]

Control: reassign -1 libglib2.0-0 2.74.6-2+deb12u1
Control: affects -1 + gnome-shell

On Wed, 08 May 2024 at 11:42:10 +0200, pham...@bluewin.ch wrote:
> After today's update, the dead keys on my keyboard no longer work

This is a regression in GLib triggered by fixing CVE-2024-34397. I'm
testing a possible fix as rapidly as I can, but each GLib build takes
about an hour, so please be patient.

smcv

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

[Bo YU]

Hi,
On Fri, May 05, 2023 at 10:15:01PM +0800, 李程 wrote:

  Package: wnpp
  Severity: wishlist
  Owner: Cheng Li <[1]ship...@gmail.com>
  X-Debbugs-Cc: [2]debian-de...@lists.debian.org
  * Package name: gl4es
Version : 1.1.4
Upstream Author : ptitSeb
  * URL : [3]https://github.com/ptitSeb/gl4es
  * License : MIT
Programming Lang: c


Many thanks for your upstream work and initail package!
As we have talked about it some days ago I have packaged
it based on your work(and I have ownered it now):

https://salsa.debian.org/vimerbf-guest/gl4es

Please review it if you have free time.:)

--
Regards,
--
  Bo YU



signature.asc
Description: PGP signature

Bug#1070745: Bug on Debian 12 Bookworm - Gnome-Shell / After today's upgrade, the dead keys on my keyboard no longer work

[pham...@bluewin.ch]

Post Scriptum
I use Swiss French/German/Italian keyboard.
We have a unique keyboard for these 3 languages.
I have tested all existing keyboard profiles without success. They all pose 
this problem.
If I enter for exemple : être 
The result displayed is : tre
The keyboard option without dead keys works but is unusable on a daily basis.
Regards.

Bug#1070746: libplplotada-dev: breaks tests, must Depend: libplplot-dev

[nicolas . boulenguez]

Source: plplot
Severity: normal
Tags: patch
X-Debbugs-Cc: Graham Inggs 

Hello.
The autopkgtests are failing with
  ...gcc... -lplplotada -lplplot ...
  /usr/bin/ld: cannot find -lplplot: No such file or directory
The linker is searching for the /usr/lib/MULTIARCH/libplplot.so symbolic 
link,

but does not find it because libplplot-dev is not installed.
This was hidden before 
https://salsa.debian.org/science-team/plplot/-/commit/e62a3beaf7e3e7e6856dc4ca45f8d20df36a1671

because the test dependencies were not minimal.
So libplplotada-dev must
  Depend: libplplot-dev (= ${binary:Version})
instead of
  Depending: libplplot17 (= ${binary:Version})
  Recommending: libplplot-dev
All the best.

Bug#1065309: transition: gnat (12 -> 13 + time_t64)

[Graham Inggs]

Hi Nicolas and Rafael

It looks like the last blocker for this transition is plplot
5.15.0+dfsg2-10 failing its own autopkgtests [1].

Regards
Graham


[1] https://ci.debian.net/packages/p/plplot/

Bug#1070416: src:diffoscope: unsatisfied build dependency in testing: aapt

[Chris Lamb]

Paul Gevers wrote:

> Dose [1] is reporting a build issue with your package, it's missing a
> build dependency. Obviously your build dependencies shouldn't be
> removed from testing, but unfortunately there are multiple scenarios
> where that can happen nevertheless.

Looks like this happened due to these RC bugs:

  https://bugs.debian.org/1062206
  https://bugs.debian.org/1062110
  https://bugs.debian.org/1062209

i.e. it wasn't that aapt was removed or barred from testing for some
reason specific to aapt's code or license, etc. It is, as I understand
it, not impossible that it might return to testing without further
intervention on our part..?

Otherwise, we can very cleanly remove this build dependency, even
keeping the .arsc file support in diffoscope itself.


Regards,

-- 
  ,''`.
 : :'  : Chris Lamb
 `. `'`  la...@debian.org  chris-lamb.co.uk
   `-

Bug#1070724: tmux: take flock on socket file/dir in /tmp/

[Luca Boccassi]

On Wed, 8 May 2024 at 10:45, Luca Boccassi  wrote:
>
> On Wed, 8 May 2024 at 08:20, Romain Francoise  wrote:
> >
> > Hi Luca,
> >
> > Thanks for the heads up! Appreciate it.
> >
> > On Wed, May 8, 2024 at 1:33 AM Luca Boccassi  wrote:
> > > In order to avoid the /tmp/tmux-UID/default socket being deleted while
> > > in use (e.g.: long term session), please patch tmux to take a flock(2)
> > > on the directory while it's running, as per documentation:
> > >
> > > https://www.freedesktop.org/software/systemd/man/latest/tmpfiles.d.html#Age
> >
> > I'd rather ship a tmpfiles config snippet with an 'x' directive to
> > skip the tmux directories.
> > Will that continue to work?
>
> Yes. Please ship it under /usr/lib/tmpfiles.d, and give it a clear
> prefix that identifies the package (eg: tmux-something.conf). Also
> please understand that any user can define any cleanup rule they want
> locally, and they will override what packages ship (this is by
> design), so the flock solution would be safer. But it is up to you
> what you choose of course.

Also note that you can start shipping this drop-in immediately, no
need to wait or coordinate

Bug#1070704: More info

[Roderich Schupp]

I just saw that the missing libkmod (dlopen'ed by udevadm) is already taken
care of by /usr/share/initramfs-tools/hooks/udev.

In case you're wondering what caused libsystemd.so.0 to be included
in my initrd-img: it's linked by /usr/sbin/lvm which gets added by
/usr/share/initramfs-tools/hooks/lvm2

Cheers, Roderich

Bug#1065652: Needed by python-memcache

[Thomas Goirand]

Hi,

This package is needed by latest version of python-memcache. So I'm 
therefore doing an ITP instead of the original RFS for this package.


Cheers,

Thomas Goirand (zigo)

Bug#1070745: Bug on Debian 12 Bookworm - Gnome-Shell / After today's upgrade, the dead keys on my keyboard no longer work

[pham...@bluewin.ch]

Package:  Gnome-Shell
Version: 43.9-0+deb12u2
Severity: critical

Bug Description:
After today's update, the dead keys on my keyboard no longer work, neither on 
my workstation or on my laptop ?!?
I noticed this problem on my station this morning after the proposed update.
I checked that it worked well on my laptop everything was ok, I applied the 
update and after a reboot it no longer worked on my laptop either.
- Station update log :
Start-Date: 2024-05-08  09:17:44
Commandline: apt dist-upgrade
Upgrade: libglib2.0-bin:amd64 (2.74.6-2, 2.74.6-2+deb12u1), 
libglib2.0-data:amd64 (2.74.6-2, 2.74.6-2+deb12u1), gnome-shell:amd64 
(43.9-0+deb12u1, 43.9-0+deb12u2), gnome-shell-common:amd64 (43.9-0+deb12u1, 
43.9-0+deb12u2), libglib2.0-0:amd64 (2.74.6-2, 2.74.6-2+deb12u1), 
libglib2.0-0:i386 (2.74.6-2, 2.74.6-2+deb12u1), 
gnome-shell-extension-prefs:amd64 (43.9-0+deb12u1, 43.9-0+deb12u2)
Remove: linux-image-6.1.0-18-amd64:amd64 (6.1.76-1)
End-Date: 2024-05-08  09:17:52
- Laptop update log :
Start-Date: 2024-05-08  11:07:48
Commandline: apt dist-upgrade -y
Install: linux-headers-6.1.0-21-amd64:amd64 (6.1.90-1, automatic), 
linux-headers-6.1.0-21-common:amd64 (6.1.90-1, automatic), 
linux-image-6.1.0-21-amd64:amd64 (6.1.90-1, automatic)
Upgrade: libglib2.0-bin:amd64 (2.74.6-2, 2.74.6-2+deb12u1), 
linux-compiler-gcc-12-x86:amd64 (6.1.85-1, 6.1.90-1), linux-headers-amd64:amd64 
(6.1.85-1, 6.1.90-1), libglib2.0-data:amd64 (2.74.6-2, 2.74.6-2+deb12u1), 
gnome-shell:amd64 (43.9-0+deb12u1, 43.9-0+deb12u2), linux-kbuild-6.1:amd64 
(6.1.85-1, 6.1.90-1), linux-image-amd64:amd64 (6.1.85-1, 6.1.90-1), 
gnome-shell-common:amd64 (43.9-0+deb12u1, 43.9-0+deb12u2), libglib2.0-0:amd64 
(2.74.6-2, 2.74.6-2+deb12u1), libglib2.0-0:i386 (2.74.6-2, 2.74.6-2+deb12u1), 
gnome-shell-extension-prefs:amd64 (43.9-0+deb12u1, 43.9-0+deb12u2), 
linux-libc-dev:amd64 (6.1.85-1, 6.1.90-1)
End-Date: 2024-05-08  11:08:10
Thank you for urgently returning to previous versions, we can no longer work 
properly since...
Regards.

Bug#1070724: tmux: take flock on socket file/dir in /tmp/

[Luca Boccassi]

On Wed, 8 May 2024 at 08:20, Romain Francoise  wrote:
>
> Hi Luca,
>
> Thanks for the heads up! Appreciate it.
>
> On Wed, May 8, 2024 at 1:33 AM Luca Boccassi  wrote:
> > In order to avoid the /tmp/tmux-UID/default socket being deleted while
> > in use (e.g.: long term session), please patch tmux to take a flock(2)
> > on the directory while it's running, as per documentation:
> >
> > https://www.freedesktop.org/software/systemd/man/latest/tmpfiles.d.html#Age
>
> I'd rather ship a tmpfiles config snippet with an 'x' directive to
> skip the tmux directories.
> Will that continue to work?

Yes. Please ship it under /usr/lib/tmpfiles.d, and give it a clear
prefix that identifies the package (eg: tmux-something.conf). Also
please understand that any user can define any cleanup rule they want
locally, and they will override what packages ship (this is by
design), so the flock solution would be safer. But it is up to you
what you choose of course.

> > Aside from this, it would be better to switch the location to
> > XDG_RUNTIME_DIR (/run/user/UID), as a predictable name such as the one
> > used by tmux can be easily hijacked by anything that manages to run
> > before tmux is started, given /tmp is world writable by default. screen
> > already switched some time ago to /run/.
>
> That's not something that I feel would be appropriate as a
> Debian-specific change, but I can discuss it with the upstream author.
> Not much chance of it happening though.

Yes understood, that is something appropriate to do upstream and not
downstream, I agree. I'd suggest to mention 'screen' as a factual
example for this pattern, it might help.

Bug#1070744: /usr/bin/puppet: puts non-regeneratable data in /var/cache

[Hendrik Jaeger]

Package: puppet-agent
Version: 7.23.0-1
Severity: minor
File: /usr/bin/puppet
X-Debbugs-Cc: debian-b...@henk.geekmail.org

Dear Maintainer,

   * What led up to the situation?

I was trying to build an exclude list for my backups and went through the 
content of my filesystems.

   * What was the outcome of this action?

I noticed that there are reports of puppet runs in /var/cache/puppet/reports.

   * What outcome did you expect instead?

I did expect all data in /var/cache and its subdirectories to be regeneratable 
and not contain any information one might want to backup.
According to the FHS in 
https://refspecs.linuxfoundation.org/FHS_3.0/fhs/ch05s05.
> /var/cache is intended for cached data from applications. Such data is 
> locally generated as a result of time-consuming I/O or calculation. The 
> application must be able to regenerate or restore the data.

This is not the case for reports:
Puppet can not regenerate the report for a specific run.
Also "cache" usually refers to data that will be reused which is not the case 
for these reports.
/var/log seems a better fit for those.

In my concrete case, it seems suboptimal that these reports are in a directory 
that I would like to exclude from backups because it should not contain 
anything worth backing up anyway as all data in there is supposed to be 
regeneratable and these reports clearly are not.
Under the "Rationale" this use case is even mentioned explicitly:
> The existence of a separate directory for cached data allows system 
> administrators to set different disk and backup policies from other 
> directories in /var.

The argument has been made on IRC that usually reports are not stored locally 
anyway, but it seemed implied that the server would also store the reports in a 
directory named "cache", but outside the FHS in 
/opt/puppetlabs/puppet/cache/reports in the case of a non-debian installation. 
I have no puppetserver installation with debian on hand, so I don’t know how 
the debian package would behave.

Another argument has been made that the reports are stored in puppetdb and the 
reports are thus only stored temporarily as files on a disk. IMHO that still 
wouldn’t make them "cache" data. "temporary" data maybe, so in that case they 
should probably go to /var/tmp or /tmp.
Or, as https://refspecs.linuxfoundation.org/FHS_3.0/fhs/ch05s14.html mentions:
> /var/spool contains data which is awaiting some kind of later processing. 
> Data in /var/spool represents work to be done in the future (by a program, 
> user, or administrator); often data is deleted after it has been processed.

Both of these arguments are kind of OK for a certain set of circumstances but 
not everybody is running a puppetdb or even a puppetserver. I am running puppet 
standalone, i.e. with `puppet apply`, so the reports will not be transferred to 
the server and will not be consumed into/by puppetdb.

In any case, treating reports as "cached" data seems quite clearly wrong.
In the case of standalone puppet (i.e. `puppet apply`) IMHO they are "logs" and 
should go to /var/log.
In the case of a puppet-agent (i.e. a puppet client/agent connecting to a 
puppet server _without_ a puppetdb), they should probably not be saved on the 
client at all but if so, they are also "logs" IMHO and should be treated like 
mentioned above. On the server, they should also be treated like "logs" but not 
necessarily go to /var/log like machine-local log data. I don’t think I have a 
concrete sensible suggestion for this case. Maybe /var/lib.
In the case of a puppetserver with a puppetdb, they should probably not be 
saved as files at all on the server. Unless they are sent directly to the 
puppetdb from the puppedserver, but consumed later, they are probably "spool" 
data.


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

Kernel: Linux 6.1.0-20-amd64 (SMP w/4 CPU threads; PREEMPT)
Locale: LANG=en_US.UTF-8, LC_CTYPE=de_CH.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US:en
Shell: /bin/sh linked to /usr/bin/dash
Init: sysvinit (via /sbin/init)
LSM: AppArmor: enabled

Versions of packages puppet-agent depends on:
ii  adduser3.134
ii  debconf [debconf-2.0]  1.5.82
ii  facter 4.3.0-2
ii  hiera  3.10.0-1
ii  init-system-helpers1.65.2
ii  ruby   1:3.1
ii  ruby-augeas1:0.5.0+gem-1
ii  ruby-concurrent1.1.6+dfsg-5
ii  ruby-deep-merge1.1.1-2
ii  ruby-semantic-puppet   1.0.4-1
ii  ruby-shadow2.5.1-1
ii  ruby-sorted-set1.0.3-3

Versions of packages puppet-agent recommends:
pn  augeas-tools   
ii  debconf-utils  1.5.82
ii  lsb-release12.0-1
pn  ruby-selinux   

Versions of packages puppet-agent suggests:
pn  hiera-eyaml
pn  puppet-module-puppetlabs-augeas-core   

Bug#1070138: RFS: django-anymail/10.3-1 [ITA] -- Django email backend for multiple ESPs (Python 3)

[Jeroen Ploemen]

On Wed, 1 May 2024 00:29:49 +0530
Akash Doppalapudi  wrote:

> I am looking for a sponsor for my package "django-anymail":

hi Akash,

I granted you maintainer level access to the package's git repo
on salsa, please push your changes there.

Took a quick look at the package, it seems to be in very good shape
overall. You might want to point the watch file to upstream's github
though, as the tarballs there include tests and documentation missing
from the releases on pypi. And then of course put that stuff to use :)


pgp2sxpfik2v7.pgp
Description: OpenPGP digital signature

Bug#1061421: Fails to start after an upgrade

[duck]

Quack,

On 2024-05-08 09:40, Marc Dequènes wrote:


Not sure this is the same problem but I would say it's worth a try.
I'll prepare the package and let you know how it goes.


I packaged and uploaded 0.5.0 and this bug is fixed for me now, but I'd 
like to hear from you all before closing this bug.


I'm still not sure 0.5.0 fixes this bug and I do not have time to 
explore all possibilities. As Peter found in #1065506 building with 
newer wayland and smithay versions can cause problems because there's 
important changes in newer versions and that may be the real source of 
this problem. Until upstream works on bumping the deps they are now 
locked. It's annoying to keep multiple versions around but there's no 
way around it at the moment.


I'm using greetd 0.10.0 as upstream bumped the requirement for the 
greetd_ipc component. I don't think that's necessary to have such 
combination according to what changed in 0.10 and I left the link 
between both packages loose as before. Tell me if you encounter any 
problem.


Regards.
\_o<

--
Marc Dequènes

Bug#1070688: gnupg: PINENTRY_USER_DATA not passed to pinentry

[Farblos]

Never mind.  During one of the last t64 upgrade orgies package gpg-sq got
installed on my system and succeeded to install the diversion to /usr/bin/gpg.
And the sequoia replacement is not very feature complete, as they continue
to stress themselfes.

For example, referencing a recipient by exact name with "=" does
not work in gpg-sq, either.

I just purged gpg-sq and its dependencies and now I'm back to normal.

Feel free to close this issue.

Bug#1068017: Y2038-safe replacements for utmp/wtmp and lastlog

[Jun MO]

On Wed, 8 May 2024 at 09:21:35 +1000, Craig Small  wrote:

> I can only speak for w.  It currently prefers what it gets from 
systemd or

> elogind, effectively
> iterating over the sessions coming from sd_get_sessions() if sd_booted()
> returns true.
>
> If sd_booted() returns false, then it uses the old utmp/utmpx files for
> now. Besides the Y2038
> issue, the utmp "API" is pretty awful with things like errors pretty much
> undetectable. There is also
> the problem about who (e.g. which process) should be writing to those 
files

> as you have pointed out
> in your email.
>
> For now w/uptime will use utmp as a fallback, but I'll be happy if this
> gets updated to something better; it's a low-priority
> for me because systemd/elogind do what I need most of the time.

Thanks for explaining.

For last(1) my concern is that it will be helped to keep the original
last(1) for back-compatibility to read old wtmp files. For w(1), utmp
is only about current sessions, so there is no need to keep years-old
utmp files. Unlike last(1), there is no something like `w -f /run/utmp'.
Actually, one can run `last -f /run/utmp', and it provides output
similar to w(1)'s except missing something like process and CPU times
for each user. And as pointed out by you, w(1) currently already prefer
using infos from systemd/elogind instead of reading from utmp.

So I now think w(1) may be little need to keep the ability to read from
utmp and am also happy to it can change to use something better.

Regards,
Jun MO

Bug#1018336: deap: build-depends on python3-nose or uses it for autopkgtest

[Graham Inggs]

Control: reopen -1
Control: severity -1 serious

deap 1.4.1-1 still depends on python3-nose for its autopkgtests.
However, these are currently failing, preventing migration to testing.

debian/tests/control contains:

Depends: python3-all, python3-deap, python3-numpy, python3-nose

At least python3-nose should probably be replaced by python3-pytest