Bug#953648: bindgen: segfault on powerpc

2023-11-26 Thread Blair Noctis
Hi Daniel,

It this still relevant?

> https://gitlab.com/sequoia-pgp/nettle-sys/-/issues/8

The project owner closed it because a later version of rust-nettle-sys no longer
had this problem.

-- 
Sdrager,
Blair Noctis


OpenPGP_signature.asc
Description: OpenPGP digital signature


Bug#1055730: atropos ftbfs with Python 3.12

2023-11-26 Thread Andreas Tille
Hi Vladimir,

Am Mon, Nov 27, 2023 at 10:46:01AM +1300 schrieb Vladimir Petko:
>  Would it be possible to consider a MR[1] that resolves this issue?

MR applied, package building for uploading.

Thanks a lot for the MR
   Andreas.

-- 
http://fam-tille.de



Bug#1056940: smartmontools: Installs empty directory /lib/systemd/system/

2023-11-26 Thread Helmut Grohne
Control: user helm...@debian.org
Control: usertags -1 = dep17p9

Hi Dmitry and Chris,

On Mon, Nov 27, 2023 at 03:53:44PM +1100, Dmitry Smirnov wrote:
> On Monday, 27 November 2023 12:12:08 PM AEDT Chris Hofstaedtler wrote:
> > Severity: important
> > ...
> > your package smartmontools ships an empty directory
> > /lib/systemd/system:

First of all, I confirm that there is a problem. Thanks for filing it.
What that problem is precisely, is less obvious. A naive lookup using
DEP17 would result in P6 (empty directory loss), but since smartmontools
also ships /usr/lib/systemd/system, it cannot actually be lost and hence
dumat does not complain about it. It is not a P6 problem.

However, base-files will eventually install /lib as a symbolic link in
its data.tar. When that happens, smartmontools has an undeclared symlink
vs directory conflict with base-files. In the worst scenario, this could
be resolved by dpkg in favour of smartmontools breaking the entire
system. I note that base-files does not yet have this symbolic link, so
what is being reported here is a future problem aiming to make the
transition less broken in future.

> How installing empty directory could possibly warrant severity "important"??

Thanks for asking. I am inclined to agree that filing P9 problems at
normal severity now and later bumping them to higher severity is more
appropriate given that there is little urgency just yet. This filing has
now become the first instance of a P9 problem being reported in Debian
as far as I understand. Chris has been doing a lot of work on important
aspects of this transition. Please expect us to not get every detail
right on the first attempts. Still your feedback is valuable for
improving future filings.

Thanks for your understanding

Helmut



Bug#1042468: scrcpy: import version 2.1.1 into debian

2023-11-26 Thread martin f krafft
Hello,

Version 2.3 has been out for a while, and it's needed for Android 
14+, i.e. the current version in Debian doesn't work with Android 14 
anymore.

Is this package still maintained?

-- 
 .''`.   martin f. krafft 
: :'  :  proud Debian developer
`. `'`   http://people.debian.org/~madduck
  `-  Debian - when you have better things to do than fixing systems


Bug#921815: Extra information about /proc

2023-11-26 Thread Roland Clobus

Hello Thorsten,

On 27/11/2023 05:58, Thorsten Glaser wrote:

reopen 921815
thanks

But did you also test whether /proc was not umounted?


Before and after the debootstrap command, the output of mount inside the 
docker container is identical.


Then I exit the docker container, and in the host (running sid) /proc is 
still mounted. So all is as expected.


What did you see when you tested while reopening this bug report?

With kind regards,
Roland Clobus


OpenPGP_signature.asc
Description: OpenPGP digital signature


Bug#976601: rustc: version in buster fails to build Rust code, aborting with "undefined symbol: llvm.x86.subborrow.64"

2023-11-26 Thread Blair Noctis
Hi Sascha,

Since we now have bookworm as stable and rustc 1.63.0 in it, is this bug still
relevant?

-- 
Sdrager,
Blair Noctis


OpenPGP_signature.asc
Description: OpenPGP digital signature


Bug#1056951: ITP: elpa-lin -- Lin is a stylistic enhancement for Emacs’ built-in hl-line-mode

2023-11-26 Thread Dhavan Vaidya
Package: wnpp
Severity: wishlist
Owner: Dhavan Vaidya 

* Package name: elpa-lin
  Version : 1.0.0
  Upstream Author : Protesilaos Stavrou 
* URL : https://git.sr.ht/~protesilaos/lin
* License : GNU GPLV3
  Programming Lang: elisp
  Description : Lin is a stylistic enhancement for Emacs’ built-in 
hl-line-mode

Lin is a stylistic enhancement for Emacs’ built-in hl-line-mode. It
remaps the hl-line face (or equivalent) buffer-locally to a style that
is optimal for major modes where line selection is the primary mode of
interaction.



Bug#1056692: libhamlib4: Add protective diversion for udev rules shared file

2023-11-26 Thread tony mancill
On Fri, Nov 24, 2023 at 04:59:48PM +, MigueL Landaeta wrote:
> Package: libhamlib4
> Version: 4.5.5-2
> Severity: important
> Tags: patch
> User: helm...@debian.org
> Usertags: dep17p7
> X-Debbugs-Cc: helm...@debian.org

Hello Miguel,

Thank you for the patch.  I have applied it and tested locally and
everything appears to be working correctly.  I have an upload ready
prepared, but wanted to confirm with you that this lintian error is
expected after applying the patch:

E: libhamlib4: diversion-for-unknown-file lib/udev/rules.d/60-libhamlib4.rules 
[preinst:14]
N: 
N:   The named maintainer script adds a diversion for a file that is not being 
provided by this package.
N: 
N:   Visibility: error
N:   Show-Always: no
N:   Check: maintainer-scripts/diversion

Should I add a lintian-override for it?

Thank you,
tony



Bug#1056916: freeciv fails to load saved games

2023-11-26 Thread Marko Lindqvist
 This fix works at least in my tests.
 And it turned out to be a bit more complex than I thought, and it was on
the loading side after all.


 - ML
From 56d18b3c06e3c3b61908da30ab130d62f3e0e85d Mon Sep 17 00:00:00 2001
From: Marko Lindqvist 
Date: Mon, 27 Nov 2023 01:29:52 +0200
Subject: [PATCH] Reserve space for terminating NULL on astr_buffer

Growing the buffer was always considered a failure,
as it was one byte too small even after giving out
the requested size.

Reported by Giacomo Mulas

Debian Bug#1056916

Signed-off-by: Marko Lindqvist <
---
 utility/astring.c | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/utility/astring.c b/utility/astring.c
index 44d39f582c..cfcb67565f 100644
--- a/utility/astring.c
+++ b/utility/astring.c
@@ -234,8 +234,8 @@ static inline void astr_vadd_at(struct astring *astr, size_t at,
   va_copy(copy, ap);
 
   req_len = fc_vsnprintf(buffer, buffer_size, format, ap);
-  if (req_len > buffer_size) {
-buffer = astr_buffer_grow(req_len, _size);
+  if (req_len + 1 > buffer_size) {
+buffer = astr_buffer_grow(req_len + 1, _size);
 /* Even if buffer is *still* too small, we fill what we can */
 req_len = fc_vsnprintf(buffer, buffer_size, format, copy);
 if (req_len > buffer_size) {
-- 
2.42.0



Bug#924862: mpv with Vulkan without shaderc

2023-11-26 Thread Shmerl
I just noticed that mpv somehow managed to work with Vulkan without shaderc!

Here is my configuration in $HOME/.config/mpv/config

[gpu-vulkan]
vo=gpu-next
gpu-api=vulkan
hwdec=vaapi
gpu-context=waylandvk

[default]
profile=gpu-vulkan

Here is some of what I see when running with --msg-level=all=debug

[vo/gpu-next/vulkan] Initializing GPU context 'waylandvk'
...
[vo/gpu-next/libplacebo] Spent 2.067 ms creating vulkan instance
...
[vo/gpu-next/libplacebo] Requested alpha compositing mode:
VK_COMPOSITE_ALPHA_PRE_MULTIPLIED_BIT_KHR
[vo/gpu-next/libplacebo] Requested surface transform:
VK_SURFACE_TRANSFORM_IDENTITY_BIT_KHR
...
[vo/gpu-next] Loading hwdec driver 'vaapi'
...
[vo/gpu-next/libplacebo] vertex shader source:
[vo/gpu-next/libplacebo] [  1] #version 450
...
[vo/gpu-next/libplacebo] [ 38]
[vo/gpu-next/libplacebo] [ 39] void main() {
[vo/gpu-next/libplacebo] [ 40] out_color = _1();
[vo/gpu-next/libplacebo] [ 41] }
[vo/gpu-next/libplacebo] Spent 0.796 ms translating SPIR-V
[vo/gpu-next/libplacebo] Spent 0.802 ms translating SPIR-V
[vo/gpu-next/libplacebo] Spent 0.004 ms compiling shader
[vo/gpu-next/libplacebo] Spent 0.070 ms creating pipeline
[vo/gpu-next/libplacebo] Pass statistics: size 0, SPIR-V: vert 0 frag 0
comp 0
...

So it clearly somehow manages to compile shaders to SPIR-V without shaderc!
May be libplacebo has some built in compiler?

Just wanted to share if anyone was waiting to start using Vulkan with your
mpv.

Regards,
Shmerl.


Bug#1056950: ITP: elpa-denote -- simple note-taking tool for Emacs

2023-11-26 Thread Dhavan Vaidya
Package: wnpp
Severity: wishlist
Owner: Dhavan Vaidya 

* Package name: elpa-denote
  Version : 2.1.0
  Upstream Author : Protesilaos Stavrou 
* URL : https://git.sr.ht/~protesilaos/denote
* License : GNU GPLV3
  Programming Lang: elisp
  Description : Denote is a simple note-taking tool for Emacs.

Denote is a simple note-taking tool for Emacs. It is based on the idea
that notes should follow a predictable and descriptive file-naming
scheme. The file name must offer a clear indication of what the note is
about, without reference to any other metadata. Denote basically
streamlines the creation of such files while providing facilities to
link between them.
.
Denote's file-naming scheme is not limited to "notes". It can be used
for all types of file, including those that are not editable in Emacs,
such as videos. Naming files in a consistent way makes their filtering
and retrieval considerably easier. Denote provides relevant facilities
to rename files, regardless of file type.



Bug#1056949: dkms: conffiles not removed: /etc/kernel/install.d/dkms

2023-11-26 Thread Paul Wise
Package: dkms
Version: 3.0.12-1
Severity: normal
User: debian...@lists.debian.org
Usertags: obsolete-conffile adequate

The recent upgrade did not deal with obsolete conffiles properly.
Please use the dpkg-maintscript-helper support provided by
dh_installdeb to remove these obsolete conffiles on upgrade.

https://www.debian.org/doc/debian-policy/ch-files.html#s-config-files
https://manpages.debian.org/man/1/dh_installdeb

This bug report brought to you by adequate:

https://bonedaddy.net/pabs3/log/2013/02/23/inadequate-software/

   $ p=dkms ; adequate $p ; dpkg-query -W -f='${Conffiles}\n' $p | grep obsolete
   dkms: obsolete-conffile /etc/kernel/install.d/dkms
    /etc/kernel/install.d/dkms 7a52b8bdfe0ffa26b30be23adbf03d69 obsolete

-- System Information:
Debian Release: trixie/sid
  APT prefers testing-debug
  APT policy: (900, 'testing-debug'), (900, 'testing'), (800, 
'unstable-debug'), (800, 'unstable'), (790, 'buildd-unstable'), (700, 
'experimental-debug'), (700, 'experimental'), (690, 'buildd-experimental')
Architecture: amd64 (x86_64)

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

Versions of packages dkms depends on:
ii  build-essential    12.10
ii  clang-14 [c-compiler]  1:14.0.6-16
ii  clang-15 [c-compiler]  1:15.0.7-10
ii  clang-16 [c-compiler]  1:16.0.6-16
ii  dpkg-dev   1.22.1
ii  gcc [c-compiler]   4:13.2.0-1
ii  gcc-13 [c-compiler]    13.2.0-5
ii  kmod   30+20230601-2
ii  lsb-release    12.0-2
ii  make   4.3-4.1
ii  patch  2.7.6-7

Versions of packages dkms recommends:
ii  fakeroot   1.32.2-1
ii  linux-headers-amd64 [linux-headers-generi  6.5.10-1
    c]
ii  pseudo [fakeroot]  1.9.0+git20230301+ec6151a2b057-1
ii  sudo   1.9.14p2-1

Versions of packages dkms suggests:
hi  e2fsprogs  1.47.0-2+b1
ii  menu   2.1.50

-- no debconf information

-- 
bye,
pabs

https://wiki.debian.org/PaulWise


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


Bug#921815: Works in buster

2023-11-26 Thread Thorsten Glaser
reopen 921815
thanks

On Wed, 8 Nov 2023, Roland Clobus wrote:

> While triaging #919659, I found this bug report.
[…]
> It works, debootstrap reports:
> I: Base system installed successfully.

But did you also test whether /proc was not umounted?

bye,
//mirabilos
-- 
Infrastrukturexperte • Qvest Digital AG
Am Dickobskreuz 10, D-53121 Bonn • https://www.qvest-digital.com/
Telephon +49 228 54881-393 • Fax: +49 228 54881-235
HRB AG Bonn 18196 • USt-ID (VAT): DE274355441
Vorstand: Dr. Stefan Barth, Kai Ebenrett, Boris Esser, Alexander Steeg
Vorsitzender Aufsichtsrat: Peter Nöthen



Bug#1056940: smartmontools: Installs empty directory /lib/systemd/system/

2023-11-26 Thread Dmitry Smirnov
On Monday, 27 November 2023 12:12:08 PM AEDT Chris Hofstaedtler wrote:
> Severity: important
> ...
> your package smartmontools ships an empty directory
> /lib/systemd/system:

How installing empty directory could possibly warrant severity "important"??

-- 
Regards,
 Dmitry Smirnov
 GPG key : 4096R/52B6BBD953968D1B

---

Any "government" that had the consent of its subjects would not need, and
would not have, "law" enforcers. Enforcement happens only if someone does
not consent to something.
 -- Larken Rose, The Most Dangerous Superstition


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


Bug#1056948: coq-doc-html loads files from a CDN

2023-11-26 Thread Evgeny Kapun

Package: coq-doc-html

Version: 8.17.1-1


The HTML files in the coq-doc-html package contain the following line:

src="https://cdn.jsdelivr.net/npm/mathjax@3/es5/tex-mml-chtml.js";>


They should use a local library instead.



Bug#1056191: usrmerge: provide more documentation for Debian Developers and system administrators

> > Just create the chroot for the CI with --merged-usr and all will be
> > fine. Debootstrap in Buster is not going to be updated to do it
> > automatically, only in Bookworm/Bullseye.
>
> Thanks Luca for clarification. So seems we need to get bookworm
> removed from 
> https://github.com/debuerreotype/debuerreotype/blob/60b625d1ce31bd81525bb67fc3a33f9686bc3433/examples/debian.sh#L183
> so that the 'debuerreotype' will run debootstrap for both bookworm and
> bullseye with '--usr-merged'. Once that is done, we need to wait for
> to the code in 
> https://github.com/debuerreotype/docker-debian-artifacts/tree/dist-amd64
> to run to generate new images of official Debian Docker images at
> https://hub.docker.com/_/debian.
>
> This will fix upgrade testing from Bullseye to Bookworm if I
> understood correctly.

Turns out the usrmerge changes are has a bit of complexity in
debuerrotype (e.g.
https://github.com/debuerreotype/debuerreotype/blob/master/Dockerfile#L41-L78)
but based on comments in
https://salsa.debian.org/installer-team/debootstrap/-/merge_requests/63
and https://salsa.debian.org/installer-team/debootstrap/-/merge_requests/76
at least you Luca are already aware of them.

Seems that doing a drive-by-contribution to debyerrotype is too much
of a learning curve for me, so I will embark on finding other
workarounds to get CI systems working again past the
Buster-Bullseye-Bookworm upgrade.



Bug#1051402: Emacspeak Won't Compile

Since I may not be able to send bug reports through fastmail, incase it didn't 
go through, here is my copy

Subject: Re: emacspeak fails byte-compile during install or upgrade since emacs 
29
Followup-For: Bug #1051402
Package: emacspeak
Version: 53.0+dfsg-2

Dear Maintainer,
  * What led up to the situation?
   * What exactly did you do (or not do) that was effective (or
 ineffective)?
   * What was the outcome of this action?
   * What outcome did you expect instead?
Whether we make or run an "apt install emacspeak" same results
-- System Information:
Debian Release: trixie/sid
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)
I am in TCSH
Kernel: Linux 6.5.0-1-amd64 (SMP w/2 CPU threads; PREEMPT)
Kernel taint flags: TAINT_DIE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
I would like to use an emacspeak DecTalk server with Fenrir
Versions of packages emacspeak depends on:
ii  adduser3.137
ii  debconf [debconf-2.0]  1.5.82
ii  emacs  1:29.1+1-5
ii  emacs-gtk [emacs]  1:29.1+1-5
ii  make   4.3-4.1
ii  perl   5.36.0-10
ii  tcl8.6.13
ii  tclx8.48.4.1-4

Versions of packages emacspeak recommends:
ii  emacspeak-espeak-server  53.0+dfsg-2
ii  sox  14.4.2+git20190427-4

Versions of packages emacspeak suggests:
pn  eflite
pn  emacspeak-ss  
pn  espeak
pn  psgml 
pn  w3m-el
pn  xsltproc  

-- debconf information:
  shared/emacspeak/rootgroup:
  shared/emacspeak/groupies:
* shared/emacspeak/port: none
  shared/emacspeak/database:
  shared/emacspeak/tcl: tcl
  shared/emacspeak/program: dtk-mv
  shared/emacspeak/fake:
* shared/emacspeak/invalidport:
* shared/emacspeak/device: DECtalk Multivoice
  shared/emacspeak/invaliduser:
Here is a transcript of part of an install
Setting up emacspeak (53.0+dfsg-2) ...
Install emacspeak for emacs
/usr/lib/emacsen-common/packages/install/emacspeak running in /
Latest installed version: 53.0+dfsg-2
install/emacspeak: Handling install for emacsen flavor emacs
  Temporary log file is emacspeak.log.cnSRPD
  Byte-compiling  (~0.7 min) ...ERROR: install script from emacspeak package 
failed
dpkg: error processing package emacspeak (--configure):
 installed emacspeak package post-installation script subprocess returned error 
exit status 1
Processing triggers for man-db (2.12.0-1) ...
Processing triggers for libc-bin (2.37-12) ...
Errors were encountered while processing:
 emacspeak
E: Sub-process /usr/bin/dpkg returned an error code (1)
Thanks so much in advance for any fixes
Chime



Bug#1056748: [debian-mysql] Bug#1056748: mariadb: References obsolete tilegx architecture

Thanks Guillem!

Patch is now as one of the commits
athttps://salsa.debian.org/mariadb-team/mariadb-server/-/merge_requests/59/commits



Bug#1056947: RFS: python-scienceplots/2.1.1-1 -- Matplotlib styles for scientific figures

Package: sponsorship-requests
Severity: normal
X-Debbugs-Cc: kd8...@gmail.com

Dear mentors,

I am looking for a sponsor for my package "python-scienceplots":

 * Package name : python-scienceplots
   Version  : 2.1.1-1
   Upstream contact : John Garrett 
 * URL  : https://github.com/garrettj403/SciencePlots
 * License  : Expat
 * Vcs  : https://salsa.debian.org/yogu/python-scienceplots
   Section  : python

The source builds the following binary packages:

  python3-scienceplots - Matplotlib styles for scientific figures

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

  https://mentors.debian.net/package/python-scienceplots/

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

  dget -x 
https://mentors.debian.net/debian/pool/main/p/python-scienceplots/python-scienceplots_2.1.1-1.dsc

Changes since the last upload:

 python-scienceplots (2.1.1-1) unstable; urgency=medium
 .
   * New upstream version. (Closes: #1056943)
   * Included copyright license for debian/*.

Regards,
-- 
  Yogeswaran Umasankar



Bug#1056946: duperemove: new upstream version

Package: duperemove
Version: 0.11.2-3
Severity: wishlist

Hey

Debian’s 0.11.2 is older than 2 years. 0.14.1 is out with many changes.

Thanks,
Chris.


Bug#1056945: fake-hwclock: Move files from /sbin to /usr/sbin

Package: fake-hwclock
Version: 0.12+nmu1
Severity: normal
Tags: patch
User: helm...@debian.org
Usertags: dep17m2

Hello Steve,

as you surely know, fake-hwclock installs into /sbin. This needs to move
to /usr/sbin for UsrMerge [1]. Please find a (trivial) patch attached.

I imagine fake-hwclock does not get backports; if it does, note that the
change should be undone for bookworm (or earlier).

Please upload at your earliest convenience.

Thanks,
Chris
diff -Nru fake-hwclock-0.12+nmu1/debian/changelog 
fake-hwclock-0.12+nmu2/debian/changelog
--- fake-hwclock-0.12+nmu1/debian/changelog 2022-10-15 12:03:12.0 
+0200
+++ fake-hwclock-0.12+nmu2/debian/changelog 2023-11-27 02:40:52.0 
+0100
@@ -1,3 +1,10 @@
+fake-hwclock (0.12+nmu2) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Install into /usr/sbin instead of /sbin.
+
+ -- Chris Hofstaedtler   Mon, 27 Nov 2023 02:40:52 +0100
+
 fake-hwclock (0.12+nmu1) unstable; urgency=medium
 
   * Non-maintainer upload.
diff -Nru fake-hwclock-0.12+nmu1/debian/fake-hwclock.dirs 
fake-hwclock-0.12+nmu2/debian/fake-hwclock.dirs
--- fake-hwclock-0.12+nmu1/debian/fake-hwclock.dirs 2012-02-09 
21:35:20.0 +0100
+++ fake-hwclock-0.12+nmu2/debian/fake-hwclock.dirs 2023-11-27 
02:40:37.0 +0100
@@ -1 +1 @@
-/sbin
+/usr/sbin
diff -Nru fake-hwclock-0.12+nmu1/debian/fake-hwclock.install 
fake-hwclock-0.12+nmu2/debian/fake-hwclock.install
--- fake-hwclock-0.12+nmu1/debian/fake-hwclock.install  2012-03-05 
17:17:42.0 +0100
+++ fake-hwclock-0.12+nmu2/debian/fake-hwclock.install  2023-11-27 
02:40:03.0 +0100
@@ -1,3 +1,3 @@
-fake-hwclock sbin
+fake-hwclock usr/sbin
 etc/default/fake-hwclock etc/default
 
diff -Nru fake-hwclock-0.12+nmu1/debian/fake-hwclock.service 
fake-hwclock-0.12+nmu2/debian/fake-hwclock.service
--- fake-hwclock-0.12+nmu1/debian/fake-hwclock.service  2020-05-01 
17:31:23.0 +0200
+++ fake-hwclock-0.12+nmu2/debian/fake-hwclock.service  2023-11-27 
02:40:47.0 +0100
@@ -7,8 +7,8 @@
 
 [Service]
 EnvironmentFile=-/etc/default/fake-hwclock
-ExecStart=/sbin/fake-hwclock load $FORCE
-ExecStop=/sbin/fake-hwclock save
+ExecStart=/usr/sbin/fake-hwclock load $FORCE
+ExecStop=/usr/sbin/fake-hwclock save
 Type=oneshot
 RemainAfterExit=yes
 


Bug#1042845: libembperl-perl: FTBFS with Perl 5.38: test failures

Hi,

gregor herrmann wrote:
> On Tue, 01 Aug 2023 22:41:12 +0200, Axel Beckert wrote:
> > > I assume the diagnostics have changed again and it's just the tests that
> > > need adjusting, but I haven't checked properly.
> > Will look into it, but may take a while.
> 
> Now would be a good time :)

Yep. Got mail about the auto removal a week ago or so. (I'm subscribed
via rss2email to my Debian Maintainer Dashboard.)

> As the perl 5.38 transition is immanent, the bug's severity has been
> raised to serious; and bot dam and me failed to understand the test
> system so I guess this is now your turn :)

Upstream might have been faster this time than I am these days: 3.0.0
is out: https://metacpan.org/dist/Embperl

http://matrix.cpantesters.org/?dist=Embperl+3.0.0 doesn't look too
well for 5.38, though. I will see.

Most if not all our changes seem to have been merged according to the
changelog.

Regards, Axel
-- 
 ,''`.  |  Axel Beckert , https://people.debian.org/~abe/
: :' :  |  Debian Developer, ftp.ch.debian.org Admin
`. `'   |  4096R: 2517 B724 C5F6 CA99 5329  6E61 2FF9 CD59 6126 16B5
  `-|  1024D: F067 EA27 26B9 C3FC 1486  202E C09E 1D89 9593 0EDE



Bug#1056944: RM: dmraid -- RoQA; obsolete; dead upstream

Package: ftp.debian.org
Severity: normal
User: ftp.debian@packages.debian.org
Usertags: remove
X-Debbugs-Cc: dmr...@packages.debian.org, László Böszörményi (GCS) 

Control: affects -1 + src:dmraid

Dear ftpmasters,

as discussed in bugs #864423 and #1034188, dmraid is obsolete and shall
not be shipped in trixie.

Please remove it.

Thanks,
Chris


Bug#1056933: [Pkg-raspi-maintainers] Bug#1056933: raspi-firmware: CMA=0 not working as intended

Cyril Brulebois dixit:
>Thorsten Glaser  (2023-11-27):
>> It’s not. The file documents:
>>
>> # To disable CMA allocation entirely, f.e. for a headless setup, set
>> # CMA=0
>
>Well, that's still the intent behind the commit that introduced support
>for that.

But it totally mismatches the documentation!

>And since that went into a stable release, I don't see how we
>could safely move away from CMA=0 means no cma= settings at all.

Granted, but…

>expressed, I suppose this bug report can be closed?

… definitely not.

Currently, CMA=0 is documented as “disable CMA allocation entirely”,
but it DOES NOT DO THAT. Instead it removes the cma= parameter from
the kernel command line INSTEAD of disabling CMA, which makes the
kernel use its default NONZERO allocation.

At the *very* leaast, that comment must be changed to e.g.

# To disable CMA allocation entirely, e.g. for a headless setup,
# set CMA=0M; setting CMA=0 makes the kernel use the default CMA
# size by omitting the cma parameter from the command line.

bye,
//mirabilos
-- 
21:41⎜«Tonnerre:#nosec» Do at least one thing every day which makes
 ⎜inspirational quotes lovers sad



Bug#1056943: python-scienceplots: New upstream version available

Source: python-scienceplots
Version: 2.1.0-3
Severity: normal
X-Debbugs-Cc: kd8...@gmail.com

There is a new upstream version available.

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

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



Bug#1056942: python-qmix: New upstream version available

Source: python-qmix
Version: 1.0.6-2
Severity: normal
X-Debbugs-Cc: kd8...@gmail.com

There is a new upstream version available.

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

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



Bug#1056941: amiga-fdisk: Move files from /sbin to /usr/sbin

Source: amiga-fdisk
Version: 0.04-16
Severity: important
User: helm...@debian.org
Usertags: dep17m2

Dear Maintainer,

your package installs files into /sbin. Please move them to /usr/sbin,
and ensure no empty directories are still installed by your package.

To achieve this, a patch is attached. Please upload at your earliest
convenience, to further the UsrMerge effort [1].

Thanks,
Chris
diff -Nru amiga-fdisk-0.04/debian/amiga-fdisk-bf.dirs 
amiga-fdisk-0.04/debian/amiga-fdisk-bf.dirs
--- amiga-fdisk-0.04/debian/amiga-fdisk-bf.dirs 2023-01-06 18:16:48.0 
+0100
+++ amiga-fdisk-0.04/debian/amiga-fdisk-bf.dirs 1970-01-01 01:00:00.0 
+0100
@@ -1 +0,0 @@
-/sbin
diff -Nru amiga-fdisk-0.04/debian/amiga-fdisk-cross.dirs 
amiga-fdisk-0.04/debian/amiga-fdisk-cross.dirs
--- amiga-fdisk-0.04/debian/amiga-fdisk-cross.dirs  2023-01-06 
18:16:48.0 +0100
+++ amiga-fdisk-0.04/debian/amiga-fdisk-cross.dirs  1970-01-01 
01:00:00.0 +0100
@@ -1 +0,0 @@
-/sbin
diff -Nru amiga-fdisk-0.04/debian/changelog amiga-fdisk-0.04/debian/changelog
--- amiga-fdisk-0.04/debian/changelog   2023-01-29 15:50:36.0 +0100
+++ amiga-fdisk-0.04/debian/changelog   2023-11-27 02:22:11.0 +0100
@@ -1,3 +1,10 @@
+amiga-fdisk (0.04-16.1) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Install programs into /usr/sbin instead of /sbin. (Closes: #-1)
+
+ -- Chris Hofstaedtler   Mon, 27 Nov 2023 02:22:11 +0100
+
 amiga-fdisk (0.04-16) unstable; urgency=medium
 
   * update Standards-Version to 4.6.2 (no changes)
diff -Nru amiga-fdisk-0.04/debian/dirs amiga-fdisk-0.04/debian/dirs
--- amiga-fdisk-0.04/debian/dirs2023-01-06 18:16:48.0 +0100
+++ amiga-fdisk-0.04/debian/dirs1970-01-01 01:00:00.0 +0100
@@ -1 +0,0 @@
-/sbin
diff -Nru amiga-fdisk-0.04/debian/patches/0003_makefile 
amiga-fdisk-0.04/debian/patches/0003_makefile
--- amiga-fdisk-0.04/debian/patches/0003_makefile   2023-01-20 
10:56:56.0 +0100
+++ amiga-fdisk-0.04/debian/patches/0003_makefile   2023-11-27 
02:22:11.0 +0100
@@ -1,9 +1,11 @@
 Description: allow one to override flags in Makefile
 Author: Christian T. Steigies 
 Last-Update: 2018-05-15
 a/Makefile
-+++ b/Makefile
-@@ -5,14 +5,14 @@
+Index: amiga-fdisk-0.04/Makefile
+===
+--- amiga-fdisk-0.04.orig/Makefile
 amiga-fdisk-0.04/Makefile
+@@ -5,21 +5,21 @@
  
  CC= gcc
  ifeq ($(USE_READLINE),no)
@@ -23,3 +25,19 @@
  endif
  
  # Where to put binaries?
+ # See the "install" rule for the links. . .
+ 
+ INSTALL=  install
+-INSTALLDIR=   /sbin
++INSTALLDIR=   /usr/sbin
+ SBIN= amiga-fdisk
+ 
+ # Where to put datebase files?
+@@ -30,6 +30,7 @@ amiga-fdisk: amigastuff.o fdisk.o
+   $(CC) $(LDFLAGS) $^ $(LIBS) -o $@
+ 
+ install: all
++  $(INSTALL) -d $(DESTDIR)$(INSTALLDIR)
+   $(INSTALL) $(SBIN) $(DESTDIR)$(INSTALLDIR)
+ 
+ clean:


Bug#1056940: smartmontools: Installs empty directory /lib/systemd/system/

Package: smartmontools
Version: 7.4-1
Severity: important
User: helm...@debian.org
Usertags: dep17m2
X-Debbugs-Cc: helm...@debian.org

Dear Maintainer,

your package smartmontools ships an empty directory
/lib/systemd/system:

pool/main/s/smartmontools/smartmontools_7.4-1_arm64.deb
drwxr-xr-x root/root 0 2023-11-25 01:15 ./lib/
drwxr-xr-x root/root 0 2023-11-25 01:15 ./lib/systemd/
drwxr-xr-x root/root 0 2023-11-25 01:15 ./lib/systemd/system/

This will probably become a problem in the near future for the final
usr-merge steps [1].

Please remove the empty directory (and its empty parents).

The systemd units are already correctly installed into
/usr/lib/systemd/system.

Thanks,
Chris

1. https://wiki.debian.org/UsrMerge



Bug#1056780: openmsx: Source-less Windows binary in source package (and other packaging issues)

Alright, I have fully rebuilt the copyright file. I also ended up adding 
the source code for several releases of C-BIOS into the packaging. As 
this code is in the form of zipped files for the sake of size, it's not 
exactly practical to provide the new source package changes as a debdiff 
since debdiffs don't communicate binary file changes very well. So 
here's a .tar.gz of the new source package tree, detach-signed with my 
GPG key. https://github.com/ArrayBolt3/openmsx-packaging (I put it on 
GitHub since Gmail didn't want to let me send the package as a file 
attachment.)


(You probably will notice some superfluous-file-pattern warnings from 
Lintian when you build this - I do not understand why these are 
occurring as the file patterns it's griping about are *not* superfluous 
and don't appear to be overridden by any later statements in the 
copyright file. I suspect a Lintian bug here.)


--
Aaron Rainbolt
Lubuntu Developer
Matrix: @arraybolt3:matrix.org
IRC: arraybolt3 on irc.libera.chat
GitHub: https://github.com/ArrayBolt3



Bug#1056939: auctex: auctex is incompatible with use-package/elpa

Package: auctex
Severity: normal
X-Debbugs-Cc: none, Xiyue Deng 

Hi,

auctex is not compatible use-package / elpa handling.  As a use-package
user, after installing auctex from Debian, it will try to install auctex
from elpa.gnu.org nonetheless.  This is because the current auctex
layout doesn't follow elpa convention so that it cannot be detected by
use-package.  It would be great to make it compatible so that
use-package users don't have to install auctex twice.

I have attempted to convert auctex to use dh-elpa and prepared a MR[1],
please review.  Thanks in advance for considering!

[1] https://salsa.debian.org/salve/auctex/-/merge_requests/3


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

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



Bug#1053686: pandoc: cannot fulfill the build dependencies


On Sat, 25 Nov 2023, Jonas Smedegaard wrote:


Quoting Scott Talbert (2023-11-25 19:09:39)

On Thu, 23 Nov 2023, Jonas Smedegaard wrote:


Quoting Ilias Tsitsimpis (2023-11-23 21:10:36)

On Fri, Nov 17, 2023 at 09:28AM, Ilias Tsitsimpis wrote:

On Thu, Nov 16, 2023 at 10:16PM, Jonas Smedegaard wrote:

Quoting John MacFarlane (2023-11-16 19:25:17)

Removing lua support would be most unfortunate!  If you need help from upstream 
in getting things to work, let me know.


I agree: Pandoc with its core scripting language disabled is a severely
crippled Pandoc.


Understood, but I am not really sure how to move forward, since Pandoc
doesn't fully support the latest Stackage LTS. I can help with
packaging/upgrade libraries if you can provide the right set of
libraries we need.


I uploaded the following packages:

* haskell-hslua-cli_v1.3.0-1,
* haskell-hslua-module-doclayout_v1.1.0-1
* haskell-hslua-module-zip_v1.1.0-1

I believe the next step is to update pandoc to 3.0.1, so we can then
package pandoc-lua-engine, pandoc-server and eventually pandoc-cli.

Jonas, how can I help move this forward? Pandoc is the last blocker to
finish the Haskell transition.


I think this will be the best way forward:

Haskell team introduces new source package haskell-pandoc.

When available, I can build package pandoc depending on it.

I really don't like breaking upstream project pandoc into two Debian
source packages like that, but I don't have the energy at the moment to
try fix dh-haskell (which I suspect will be similar work as I am doing
to dh-cargo currently).


I'm working on this (packaging haskell-pandoc).


And it's been uploaded, headed to NEW.

Regards,
Scott



Bug#1056938: rear: Move files into /usr (incl. DEP17 P7 mitigation)

Package: rear
Version: 2.7+dfsg-1
Severity: important
Tags: patch
User: helm...@debian.org
Usertags: dep17p7
X-Debbugs-Cc: helm...@debian.org

Dear Maintainer,

rear contains udev files which are installed to /lib; these files need
to be moved to /usr/lib as part of Debian's usr-merge effort.
Because your package is Multi-Arch: same, an unfortunate corner-case
can occur whereby shared files (such as the udev files) may be
erroneously removed on upgrades (please see DEP17[1] P7: Shared
multiarch file loss).

You will find a patch attached to move the udev files, including the
mitigation for the file loss scenario.

Please consider applying this patch at your earliest convenience. This
bug will be upgraded to release critical soon, as it blocks the overall
usr-merge effort which is being undertaken for the trixie release.


Many thanks,
Chris

1. https://subdivi.de/~helmut/dep17.html
diff -Nru rear-2.7+dfsg/debian/changelog rear-2.7+dfsg/debian/changelog
--- rear-2.7+dfsg/debian/changelog  2023-01-11 15:33:42.0 +0100
+++ rear-2.7+dfsg/debian/changelog  2023-11-27 01:36:54.0 +0100
@@ -1,3 +1,11 @@
+rear (2.7+dfsg-1.1) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Move udev files from /lib to /usr/lib, including protective diversion
+against Multi-Arch: same file loss scenario (DEP17 P7 M10). (Closes: #-1)
+
+ -- Chris Hofstaedtler   Mon, 27 Nov 2023 01:36:54 +0100
+
 rear (2.7+dfsg-1) unstable; urgency=medium
 
   * Update to new upstream version 2.7.
diff -Nru rear-2.7+dfsg/debian/rear.lintian-overrides 
rear-2.7+dfsg/debian/rear.lintian-overrides
--- rear-2.7+dfsg/debian/rear.lintian-overrides 2023-01-11 15:33:42.0 
+0100
+++ rear-2.7+dfsg/debian/rear.lintian-overrides 2023-11-27 01:36:54.0 
+0100
@@ -7,6 +7,10 @@
 rear: package-contains-documentation-outside-usr-share-doc 
usr/share/rear/restore/readme
 rear: package-contains-documentation-outside-usr-share-doc 
usr/share/rear/wrapup/readme
 
+# begin-remove-after: released:forky
+rear: diversion-for-unknown-file lib/udev/rules.d/60-rear.rules [*]
+# end-remove-after
+
 package-contains-empty-directory
 package-supports-alternative-init-but-no-init.d-script
 systemd-service-file-missing-documentation-key
diff -Nru rear-2.7+dfsg/debian/rear.postinst rear-2.7+dfsg/debian/rear.postinst
--- rear-2.7+dfsg/debian/rear.postinst  2023-01-11 15:33:42.0 +0100
+++ rear-2.7+dfsg/debian/rear.postinst  2023-11-27 01:34:11.0 +0100
@@ -10,6 +10,16 @@
chmod 0600 /etc/rear/local.conf
 echo "[Done]"
 fi
+
+# begin-remove-after: released:forky
+# protective diversion of files moved from / to /usr, to avoid file 
loss.
+# Only for upgrades.
+# At this point, the package will have installed the same file in 
*/usr*.
+dpkg-divert --package usr-is-merged --no-rename \
+--divert /lib/udev/rules.d/60-rear.rules.usr-is-merged \
+--remove /lib/udev/rules.d/60-rear.rules
+# end-remove-after
+
 ;;
 
 abort-upgrade|abort-remove|abort-deconfigure)
diff -Nru rear-2.7+dfsg/debian/rear.postrm rear-2.7+dfsg/debian/rear.postrm
--- rear-2.7+dfsg/debian/rear.postrm1970-01-01 01:00:00.0 +0100
+++ rear-2.7+dfsg/debian/rear.postrm2023-11-27 01:33:01.0 +0100
@@ -0,0 +1,16 @@
+#!/bin/sh
+set -e
+
+# begin-remove-after: released:forky
+# protective diversion of files moved from / to /usr, to avoid file loss.
+# Only for upgrades.
+if [ "$1" = "remove" ] && [ "$DPKG_MAINTSCRIPT_PACKAGE_REFCOUNT" = "1" ]; then
+# Cleanup in case package is removed before upgrade is finished (postinst 
ran).
+dpkg-divert --package usr-is-merged --no-rename \
+--divert /lib/udev/rules.d/60-rear.rules.usr-is-merged \
+--remove /lib/udev/rules.d/60-rear.rules
+fi
+# end-remove-after
+
+#DEBHELPER#
+
diff -Nru rear-2.7+dfsg/debian/rear.preinst rear-2.7+dfsg/debian/rear.preinst
--- rear-2.7+dfsg/debian/rear.preinst   1970-01-01 01:00:00.0 +0100
+++ rear-2.7+dfsg/debian/rear.preinst   2023-11-27 01:33:01.0 +0100
@@ -0,0 +1,15 @@
+#!/bin/sh
+set -e
+
+# begin-remove-after: released:forky
+# protective diversion of files moved from / to /usr, to avoid file loss.
+# Only for upgrades.
+if [ "$1" = "upgrade" ]; then
+dpkg-divert --package usr-is-merged --no-rename \
+--divert /lib/udev/rules.d/60-rear.rules.usr-is-merged \
+--add /lib/udev/rules.d/60-rear.rules
+fi
+# end-remove-after
+
+#DEBHELPER#
+
diff -Nru rear-2.7+dfsg/debian/rules rear-2.7+dfsg/debian/rules
--- rear-2.7+dfsg/debian/rules  2023-01-11 15:33:42.0 +0100
+++ rear-2.7+dfsg/debian/rules  2023-11-27 01:36:37.0 +0100
@@ -22,6 +22,12 @@
rm -fr debian/tmp/usr/share/rear/conf/examples
dh_install
 
+override_dh_installudev:
+   dh_installudev
+   # This should become harmless when dh_installudev changes the install 
location.
+   set -e; if test -d 

Bug#1056933: [Pkg-raspi-maintainers] Bug#1056933: raspi-firmware: CMA=0 not working as intended

Thorsten Glaser  (2023-11-27):
> It’s not. The file documents:
> 
> # To disable CMA allocation entirely, f.e. for a headless setup, set
> # CMA=0

Well, that's still the intent behind the commit that introduced support
for that. And since that went into a stable release, I don't see how we
could safely move away from CMA=0 means no cma= settings at all.

> But CMA=0 in the file leads to no cma=0 on the kernel command line,
> which makes the kernel use the default CMA allocation of 64 MiB.
> 
> >Sounds like you want CMA=0M then?
> 
> Perhaps, I just threw it here for now:
> 
> $ cat /etc/default/raspi-extra-cmdline
> TZ=:Europe/Berlin nofb nomodeset cma=0

If you don't want to verify a proposed solution to the needs you
expressed, I suppose this bug report can be closed?
-- 
Cyril Brulebois -- Debian Consultant @ DEBAMAX -- https://debamax.com/


signature.asc
Description: PGP signature


Bug#1056937: RFS: allegro5/2:5.2.9.0+dfsg-1 -- portable library for cross-platform game and multimedia development

Package: sponsorship-requests
Severity: normal

Dear mentors,

I am looking for a sponsor for my package "allegro5":
(Still without a gpg key that I can use for uploads of my own, so still
forced to go through mentors). - changes also pushed to the salsa git
repository.

 * Package name : allegro5
   Version  : 2:5.2.9.0+dfsg-1
   Upstream contact : allegro-develop...@lists.liballeg.org
 * URL  : https://liballeg.org/
 * License  : Zlib, BitstreamVera, BSD-3-clause, BSD-3-clause or GPL-2
 * Vcs  : https://salsa.debian.org/games-team/allegro5
   Section  : libs

The source builds the following binary packages:

  liballegro-image5.2 - image addon for the Allegro 5 library
  liballegro-image5-dev - header files for the Allegro 5 image addon
  liballegro-physfs5.2 - physfs addon for the Allegro 5 library
  liballegro-physfs5-dev - header files for the Allegro 5 physfs addon
  liballegro-ttf5.2 - ttf addon for the Allegro 5 library
  liballegro-ttf5-dev - header files for the Allegro 5 ttf addon
  liballegro-video5.2 - video addon for the Allegro 5 library
  liballegro-video5-dev - header files for the Allegro 5 video addon
  allegro5-doc - documentation for the Allegro 5 library
  liballegro5.2 - portable library for cross-platform game and multimedia 
development
  liballegro5-dev - development files for the Allegro 5 library
  liballegro-acodec5.2 - audio codec addon for the Allegro 5 library
  liballegro-acodec5-dev - header files for the Allegro 5 audio codec addon
  liballegro-audio5.2 - audio addon for the Allegro 5 library
  liballegro-audio5-dev - header files for the Allegro 5 audio addon
  liballegro-dialog5.2 - dialog addon for the Allegro 5 library
  liballegro-dialog5-dev - header files for the Allegro 5 dialog addon

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

  https://mentors.debian.net/package/allegro5/

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

  dget -x 
https://mentors.debian.net/debian/pool/main/a/allegro5/allegro5_5.2.9.0+dfsg-1.dsc

Changes since the last upload:

 allegro5 (2:5.2.9.0+dfsg-1) unstable; urgency=medium
 .
   * New upstream version 5.2.9.0+dfsg
   * Fix watchfile
   * Remove patch 0004-Use-CLOCK_REALTIME-instead-of-CLOCK_MONOTONIC.patch,
 applied upstream
   * Add cmake Config-mode files
   * Update symbol files
   * Remove lintian-overrides file, not needed

Regards,
-- 
  Andreas Rönnquist
gus...@debian.org



Bug#1055290: libevent: Fix libc-dev build-dep


Le 2023-11-26 à 12 h 05, Samuel Thibault a écrit :


Once glibc 2.38 enters testing, that makes sense indeed. But don't hold
your breath :)



That's ok, I can hold my breath for a long time, I'm half-frog! ;)



Bug#1056936: bookworm-pu: package glewlwyd/2.7.5-3


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

(Please provide enough information to help the release team
to judge the request efficiently. E.g. by filling in the
sections below.)

[ Reason ]
Fix possible buffer overflow in webauthn attestation (CVE-2023-49208)

[ Risks ]
If a crafted webauthn assertion is executed, could
result in denial of service or the execution of arbitrary code

[ 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 ]
The change checks the length of a parameter before copying it into a
fixed size array.diff -Nru glewlwyd-2.7.5/debian/changelog glewlwyd-2.7.5/debian/changelog
--- glewlwyd-2.7.5/debian/changelog	2023-05-04 07:21:27.0 -0400
+++ glewlwyd-2.7.5/debian/changelog	2023-11-23 17:12:13.0 -0500
@@ -1,3 +1,9 @@
+glewlwyd (2.7.5-3+deb12u1) bookworm; urgency=medium
+
+  * d/patches: Fix CVE-2023-49208
+
+ -- Nicolas Mora   Thu, 23 Nov 2023 17:12:13 -0500
+
 glewlwyd (2.7.5-3) unstable; urgency=medium
 
   * Install config.json as config-2.7.json (Closes: #1035503)
diff -Nru glewlwyd-2.7.5/debian/patches/CVE-2023-49208.patch glewlwyd-2.7.5/debian/patches/CVE-2023-49208.patch
--- glewlwyd-2.7.5/debian/patches/CVE-2023-49208.patch	1969-12-31 19:00:00.0 -0500
+++ glewlwyd-2.7.5/debian/patches/CVE-2023-49208.patch	2023-11-23 17:12:13.0 -0500
@@ -0,0 +1,21 @@
+Description: Fix CVE-2023-49208 for bookworm
+Author: Nicolas Mora 
+Forwarded: not-needed
+--- a/src/scheme/webauthn.c
 b/src/scheme/webauthn.c
+@@ -2260,13 +2260,13 @@
+ for (i=0; i

Bug#1055644: linux: amd driver not loaded since 6.4.x



Further test using mainline kernel from Ubuntu 
(https://kernel.ubuntu.com/mainline/v6.7-rc2/amd64/) still can't boot 
sddm. I suspect there are misconfig exists, will need more suggestions.

Bug#1053351: Confirming bug with filelight


Just to add to this bug report:

Filelight: 4:23.04.2-1
Debian Testing trixie/si

Same issue.

Just to make sure no dependency got removed, did: apt reinstall filelight

No change, doesn't open, and from CLI, same error:

$ filelight
QApplication: invalid style override 'gtk' passed, ignoring it.
Available styles: Windows, Fusion
kf.kirigami: Failed to find a Kirigami platform plugin
Segmentation fault
d

System:
  Kernel: 6.5.11-4-liquorix-amd64 arch: x86_64 bits: 64
  Desktop: Xfce v: 4.18.1 Distro: Debian GNU/Linux trixie/sid
Graphics:
  Device-1: AMD Cedar [Radeon HD 5000/6000/7350/8350 Series] driver: radeon
v: kernel
  Display: x11 server: X.Org v: 1.21.1.9 with: Xwayland v: 23.2.2 driver: X:
loaded: modesetting dri: r600 gpu: radeon resolution: 1: 1280x1024~60Hz
2: 1280x1024~60Hz
  API: EGL v: 1.5 drivers: kms_swrast,r600,swrast
platforms: gbm,x11,surfaceless,device
  API: OpenGL v: 4.5 vendor: mesa v: 23.2.1-1 renderer: AMD CEDAR (DRM
2.50.0 / 6.5.11-4-liquorix-amd64 LLVM 16.0.6)
  API: Vulkan v: 1.3.268 drivers: llvmpipe surfaces: xcb,xlib



Bug#1056933: [Pkg-raspi-maintainers] Bug#1056933: raspi-firmware: CMA=0 not working as intended

Cyril Brulebois dixit:

>Thorsten Glaser  (2023-11-26):
>> Package: raspi-firmware
>> Version: 1.20230405+ds-2
>>
>> When I set CMA=0 the cma=… argument in cmdline.txt is omitted.
>
>This is consistent with the documentation in that file.

It’s not. The file documents:

# To disable CMA allocation entirely, f.e. for a headless setup, set
# CMA=0

But CMA=0 in the file leads to no cma=0 on the kernel command line,
which makes the kernel use the default CMA allocation of 64 MiB.

>Sounds like you want CMA=0M then?

Perhaps, I just threw it here for now:

$ cat /etc/default/raspi-extra-cmdline
TZ=:Europe/Berlin nofb nomodeset cma=0

Meow,
//mirabilos
-- 
15:39⎜«mika:#grml» mira|AO: "mit XFree86® wär’ das nicht passiert" - muhaha
15:48⎜ also warum machen die xorg Jungs eigentlich alles
kaputt? :)15:49⎜ thkoehler: weil sie als Kinder nie den
gebauten Turm selber umschmeissen durften?  -- ~/.Xmodmap wonders…



Bug#1056587: texlive-latex-base: some math characters get replaced as of Debian's TeX Live 2023

Hi Vincent,

Since I am not using Debian, nor developing for Debian, I think I stop
arguing here. No need to discuss my opinion on that matter further.
Feel free to bring it up to the TC, or d-d, or whereever you feel is the
correct place.

Norbert

--
PREINING Norbert  https://www.preining.info
Mercari Inc. + IFMGA Guide + TU Wien + TeX Live
GPG: 0x860CDC13   fp: F7D8 A928 26E3 16A1 9FA0 ACF0 6CAC A448 860C DC13



Bug#1056933: [Pkg-raspi-maintainers] Bug#1056933: raspi-firmware: CMA=0 not working as intended

Thorsten Glaser  (2023-11-26):
> Package: raspi-firmware
> Version: 1.20230405+ds-2
> 
> When I set CMA=0 the cma=… argument in cmdline.txt is omitted.

This is consistent with the documentation in that file.

> However, when I manually add cma=0 to cmdline.txt I get this instead:
> 
> [0.00] Memory: 479104K/507904K available (8192K kernel code, 990K 
> rwdata
> , 2024K rodata, 1024K init, 252K bss, 28800K reserved, 0K cma-reserved)

Sounds like you want CMA=0M then?


Cheers,
-- 
Cyril Brulebois -- Debian Consultant @ DEBAMAX -- https://debamax.com/


signature.asc
Description: PGP signature


Bug#1056587: texlive-latex-base: some math characters get replaced as of Debian's TeX Live 2023

On 2023-11-27 07:50:40 +0900, Norbert Preining wrote:
> On Sun, 26 Nov 2023, Vincent Lefevre wrote:
> > Could you cite documentation saying that root must not set
> > arbitrary environment variables?
> 
> I never said that. But if they are set, root must be aware of the
> consequences,

This is not documented at all. So, in doubt, root must not set *any*
environment variable, except those clearly documented. Note that root
may not know which packages will be installed (for instance, texlive
may be brought by a dependency). So, really, any environment variable
that is non standard and unrelated to the package installation system
could be problematic, even though the user could have thought it
would be private.

> and the envvars might have effect on how packages work.

Here, this is not how packages work, but how packages are installed.

> > was actually there on purpose). But this could have been done
> > really on purpose. And this would have broken the package
> > installation.
> 
> root can make / ro and break installation.

I would expect installation to fail, not to silently yield an
incorrect installation. Note that there may be reasons that /
may be ro, such as disk errors at mount time.

> root can set their own shell to fish with probably interesting
> consequences.

You could have cited zsh, which is not a POSIX shell either.
AFAIK, various users use zsh as their root shell.

If chsh allows non-POSIX shells to be selected, this should
really be supported.

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



Bug#1056934: bookworm-pu: libde265/1.0.11-1+deb12u1


Package: release.debian.org
Severity: normal
Tags: bookworm
User: release.debian@packages.debian.org
Usertags: pu


The attached debdiff for libde265 fixes CVE-2023-27102, CVE-2023-27103, 
CVE-2023-43887 and CVE-2023-47471 in Bookworm.
Except CVE-2023-43887 all others are marked as no-dsa by the security team 
(CVE-2023-43887 appeared recently and was not evaluated yet).


The fix was already uploaded to Stretch and nobody complained up to now.

  Thorsten
diff -Nru libde265-1.0.11/debian/changelog libde265-1.0.11/debian/changelog
--- libde265-1.0.11/debian/changelog2023-02-02 16:06:20.0 +0100
+++ libde265-1.0.11/debian/changelog2023-11-26 13:03:02.0 +0100
@@ -1,3 +1,19 @@
+libde265 (1.0.11-1+deb12u1) bookworm; urgency=medium
+
+  * Non-maintainer upload by the LTS Team.
+  * CVE-2023-27102 (Closes: #1033257)
+fix segmentation violation in the
+function decoder_context::process_slice_segment_header
+  * CVE-2023-27103
+fix heap buffer overflow in the
+function derive_collocated_motion_vectors
+  * CVE-2023-43887
+fix buffer over-read in pic_parameter_set::dump
+  * CVE-2023-47471 (Closes: #1056187)
+fix buffer overflow in the slice_segment_header function
+
+ -- Thorsten Alteholz   Sun, 26 Nov 2023 13:03:02 +0100
+
 libde265 (1.0.11-1) unstable; urgency=medium
 
   [ Tobias Frost ]
diff -Nru libde265-1.0.11/debian/patches/CVE-2023-27102.patch 
libde265-1.0.11/debian/patches/CVE-2023-27102.patch
--- libde265-1.0.11/debian/patches/CVE-2023-27102.patch 1970-01-01 
01:00:00.0 +0100
+++ libde265-1.0.11/debian/patches/CVE-2023-27102.patch 2023-11-21 
14:10:17.0 +0100
@@ -0,0 +1,23 @@
+commit 0b1752abff97cb542941d317a0d18aa50cb199b1
+Author: Dirk Farin 
+Date:   Sat Mar 4 10:32:43 2023 +0100
+
+check whether referenced PPS exists (fixes #393)
+
+Index: libde265-1.0.11/libde265/decctx.cc
+===
+--- libde265-1.0.11.orig/libde265/decctx.cc2023-11-19 19:08:18.703219858 
+0100
 libde265-1.0.11/libde265/decctx.cc 2023-11-19 19:08:18.703219858 +0100
+@@ -2276,9 +2276,10 @@
+   // get PPS and SPS for this slice
+ 
+   int pps_id = hdr->slice_pic_parameter_set_id;
+-  if (pps[pps_id]->pps_read==false) {
++  if (pps[pps_id]==nullptr || pps[pps_id]->pps_read==false) {
+ logerror(LogHeaders, "PPS %d has not been read\n", pps_id);
+-assert(false); // TODO
++img->decctx->add_warning(DE265_WARNING_NONEXISTING_PPS_REFERENCED, false);
++return false;
+   }
+ 
+   current_pps = pps[pps_id];
diff -Nru libde265-1.0.11/debian/patches/CVE-2023-27103.patch 
libde265-1.0.11/debian/patches/CVE-2023-27103.patch
--- libde265-1.0.11/debian/patches/CVE-2023-27103.patch 1970-01-01 
01:00:00.0 +0100
+++ libde265-1.0.11/debian/patches/CVE-2023-27103.patch 2023-11-21 
14:10:17.0 +0100
@@ -0,0 +1,54 @@
+commit d6bf73e765b7a23627bfd7a8645c143fd9097995
+Author: Dirk Farin 
+Date:   Sat Mar 4 10:27:59 2023 +0100
+
+check for valid slice header index access (fixes #394)
+
+Index: libde265-1.0.11/libde265/de265.cc
+===
+--- libde265-1.0.11.orig/libde265/de265.cc 2023-11-19 19:08:22.851224558 
+0100
 libde265-1.0.11/libde265/de265.cc  2023-11-19 19:08:22.847224554 +0100
+@@ -174,6 +174,8 @@
+ return "Bit-depth of current image does not match SPS";
+   case DE265_WARNING_REFERENCE_IMAGE_CHROMA_FORMAT_DOES_NOT_MATCH:
+ return "Chroma format of reference image does not match current image";
++  case DE265_WARNING_INVALID_SLICE_HEADER_INDEX_ACCESS:
++return "Access with invalid slice header index";
+ 
+   default: return "unknown error";
+   }
+Index: libde265-1.0.11/libde265/de265.h
+===
+--- libde265-1.0.11.orig/libde265/de265.h  2023-11-19 19:08:22.851224558 
+0100
 libde265-1.0.11/libde265/de265.h   2023-11-19 19:08:22.847224554 +0100
+@@ -145,7 +145,8 @@
+   DE265_WARNING_REFERENCE_IMAGE_SIZE_DOES_NOT_MATCH_SPS=1029,
+   DE265_WARNING_CHROMA_OF_CURRENT_IMAGE_DOES_NOT_MATCH_SPS=1030,
+   DE265_WARNING_BIT_DEPTH_OF_CURRENT_IMAGE_DOES_NOT_MATCH_SPS=1031,
+-  DE265_WARNING_REFERENCE_IMAGE_CHROMA_FORMAT_DOES_NOT_MATCH=1032
++  DE265_WARNING_REFERENCE_IMAGE_CHROMA_FORMAT_DOES_NOT_MATCH=1032,
++  DE265_WARNING_INVALID_SLICE_HEADER_INDEX_ACCESS=1033
+ } de265_error;
+ 
+ LIBDE265_API const char* de265_get_error_text(de265_error err);
+Index: libde265-1.0.11/libde265/motion.cc
+===
+--- libde265-1.0.11.orig/libde265/motion.cc2023-11-19 19:08:22.851224558 
+0100
 libde265-1.0.11/libde265/motion.cc 2023-11-19 19:08:22.847224554 +0100
+@@ -1266,6 +1266,16 @@
+ 
+ 
+ 
++  int slice_hdr_idx = colImg->get_SliceHeaderIndex(xColPb,yColPb);
++  if (slice_hdr_idx >= colImg->slices.size()) {
++ctx->add_warning(DE265_WARNING_INVALID_SLICE_HEADER_INDEX_ACCESS, false);

Bug#1056935: bullseye-pu: libde265/1.0.11-0+deb11u2


Package: release.debian.org
Severity: normal
Tags: bullseye
User: release.debian@packages.debian.org
Usertags: pu


The attached debdiff for libde265 fixes CVE-2023-27102, CVE-2023-27103, 
CVE-2023-43887 and CVE-2023-47471 in Bullseye.
Except CVE-2023-43887 all others are marked as no-dsa by the security 
team (CVE-2023-43887 appeared recently and was not evaluated yet).


The fix was already uploaded to Stretch and nobody complained up to now.

  Thorsten
diff -Nru libde265-1.0.11/debian/changelog libde265-1.0.11/debian/changelog
--- libde265-1.0.11/debian/changelog2023-02-04 17:18:48.0 +0100
+++ libde265-1.0.11/debian/changelog2023-11-26 13:03:02.0 +0100
@@ -1,3 +1,19 @@
+libde265 (1.0.11-0+deb11u2) bullseye; urgency=high
+
+  * Non-maintainer upload by the LTS Team.
+  * CVE-2023-27102 (Closes: #1033257)
+fix segmentation violation in the
+function decoder_context::process_slice_segment_header
+  * CVE-2023-27103
+fix heap buffer overflow in the
+function derive_collocated_motion_vectors
+  * CVE-2023-43887
+fix buffer over-read in pic_parameter_set::dump
+  * CVE-2023-47471 (Closes: #1056187)
+fix buffer overflow in the slice_segment_header function
+
+ -- Thorsten Alteholz   Sun, 26 Nov 2023 13:03:02 +0100
+
 libde265 (1.0.11-0+deb11u1) bullseye-security; urgency=high
 
   * Non-maintainer upload by the Security Team.
diff -Nru libde265-1.0.11/debian/patches/CVE-2023-27102.patch 
libde265-1.0.11/debian/patches/CVE-2023-27102.patch
--- libde265-1.0.11/debian/patches/CVE-2023-27102.patch 1970-01-01 
01:00:00.0 +0100
+++ libde265-1.0.11/debian/patches/CVE-2023-27102.patch 2023-11-21 
14:07:48.0 +0100
@@ -0,0 +1,23 @@
+commit 0b1752abff97cb542941d317a0d18aa50cb199b1
+Author: Dirk Farin 
+Date:   Sat Mar 4 10:32:43 2023 +0100
+
+check whether referenced PPS exists (fixes #393)
+
+Index: libde265-1.0.11/libde265/decctx.cc
+===
+--- libde265-1.0.11.orig/libde265/decctx.cc2023-11-19 19:08:18.703219858 
+0100
 libde265-1.0.11/libde265/decctx.cc 2023-11-19 19:08:18.703219858 +0100
+@@ -2276,9 +2276,10 @@
+   // get PPS and SPS for this slice
+ 
+   int pps_id = hdr->slice_pic_parameter_set_id;
+-  if (pps[pps_id]->pps_read==false) {
++  if (pps[pps_id]==nullptr || pps[pps_id]->pps_read==false) {
+ logerror(LogHeaders, "PPS %d has not been read\n", pps_id);
+-assert(false); // TODO
++img->decctx->add_warning(DE265_WARNING_NONEXISTING_PPS_REFERENCED, false);
++return false;
+   }
+ 
+   current_pps = pps[pps_id];
diff -Nru libde265-1.0.11/debian/patches/CVE-2023-27103.patch 
libde265-1.0.11/debian/patches/CVE-2023-27103.patch
--- libde265-1.0.11/debian/patches/CVE-2023-27103.patch 1970-01-01 
01:00:00.0 +0100
+++ libde265-1.0.11/debian/patches/CVE-2023-27103.patch 2023-11-21 
14:07:48.0 +0100
@@ -0,0 +1,54 @@
+commit d6bf73e765b7a23627bfd7a8645c143fd9097995
+Author: Dirk Farin 
+Date:   Sat Mar 4 10:27:59 2023 +0100
+
+check for valid slice header index access (fixes #394)
+
+Index: libde265-1.0.11/libde265/de265.cc
+===
+--- libde265-1.0.11.orig/libde265/de265.cc 2023-11-19 19:08:22.851224558 
+0100
 libde265-1.0.11/libde265/de265.cc  2023-11-19 19:08:22.847224554 +0100
+@@ -174,6 +174,8 @@
+ return "Bit-depth of current image does not match SPS";
+   case DE265_WARNING_REFERENCE_IMAGE_CHROMA_FORMAT_DOES_NOT_MATCH:
+ return "Chroma format of reference image does not match current image";
++  case DE265_WARNING_INVALID_SLICE_HEADER_INDEX_ACCESS:
++return "Access with invalid slice header index";
+ 
+   default: return "unknown error";
+   }
+Index: libde265-1.0.11/libde265/de265.h
+===
+--- libde265-1.0.11.orig/libde265/de265.h  2023-11-19 19:08:22.851224558 
+0100
 libde265-1.0.11/libde265/de265.h   2023-11-19 19:08:22.847224554 +0100
+@@ -145,7 +145,8 @@
+   DE265_WARNING_REFERENCE_IMAGE_SIZE_DOES_NOT_MATCH_SPS=1029,
+   DE265_WARNING_CHROMA_OF_CURRENT_IMAGE_DOES_NOT_MATCH_SPS=1030,
+   DE265_WARNING_BIT_DEPTH_OF_CURRENT_IMAGE_DOES_NOT_MATCH_SPS=1031,
+-  DE265_WARNING_REFERENCE_IMAGE_CHROMA_FORMAT_DOES_NOT_MATCH=1032
++  DE265_WARNING_REFERENCE_IMAGE_CHROMA_FORMAT_DOES_NOT_MATCH=1032,
++  DE265_WARNING_INVALID_SLICE_HEADER_INDEX_ACCESS=1033
+ } de265_error;
+ 
+ LIBDE265_API const char* de265_get_error_text(de265_error err);
+Index: libde265-1.0.11/libde265/motion.cc
+===
+--- libde265-1.0.11.orig/libde265/motion.cc2023-11-19 19:08:22.851224558 
+0100
 libde265-1.0.11/libde265/motion.cc 2023-11-19 19:08:22.847224554 +0100
+@@ -1266,6 +1266,16 @@
+ 
+ 
+ 
++  int slice_hdr_idx = colImg->get_SliceHeaderIndex(xColPb,yColPb);
++  if (slice_hdr_idx >= colImg->slices.size()) {
++

Bug#1056933: raspi-firmware: CMA=0 not working as intended

Package: raspi-firmware
Version: 1.20230405+ds-2

When I set CMA=0 the cma=… argument in cmdline.txt is omitted. This
leads to:

[0.00] Memory: 413440K/507904K available (8192K kernel code, 990K rwdata
, 2024K rodata, 1024K init, 252K bss, 28928K reserved, 65536K cma-reserved)


However, when I manually add cma=0 to cmdline.txt I get this instead:

[0.00] Memory: 479104K/507904K available (8192K kernel code, 990K rwdata
, 2024K rodata, 1024K init, 252K bss, 28800K reserved, 0K cma-reserved)


This is Debian bullseye/armel (with raspi-firmware from sid)
on an RPi B+ (rev. 1.2).

bye,
//mirabilos



Bug#1056587: texlive-latex-base: some math characters get replaced as of Debian's TeX Live 2023

On Sun, 26 Nov 2023, Vincent Lefevre wrote:
> Could you cite documentation saying that root must not set
> arbitrary environment variables?

I never said that. But if they are set, root must be aware of the
consequences, and the envvars might have effect on how packages work.

> was actually there on purpose). But this could have been done
> really on purpose. And this would have broken the package
> installation.

root can make / ro and break installation.
root can set their own shell to fish with probably interesting
consequences.
root can do soo many things to break package installation

Best regards

Norbert

--
PREINING Norbert  https://www.preining.info
Mercari Inc. + IFMGA Guide + TU Wien + TeX Live
GPG: 0x860CDC13   fp: F7D8 A928 26E3 16A1 9FA0 ACF0 6CAC A448 860C DC13



Bug#1055889: RFS: urlview/1b-1 [ITA] -- Extracts URLs from text

Hi!

On Sun, Nov 26, 2023 at 06:10:05PM +0100, Tobias Frost wrote:
> - d/copyright misses a few files/has inaccuracies, e.g enter.h
>   please review & update.
Indeed, fixed in
  
https://git.sr.ht/~nabijaczleweli/urlview.deb/commit/e975623d2973b8555065eae89424c2c15aa8858b
thanks.

Uploaded a fixed 1b-1 to mentors.d.n.

Best,
наб


signature.asc
Description: PGP signature


Bug#1055730: atropos ftbfs with Python 3.12

Dear Maintainers,

 Would it be possible to consider a MR[1] that resolves this issue?

Best Regards,
 Vladimir.

[1] https://salsa.debian.org/med-team/atropos/-/merge_requests/1


Bug#1056932: kakasi: Packaged version breaks transliteration to hiragana, doesn't happen with vanilla source build

Package: kakasi
Version: 2.3.6-4.1
Severity: important
X-Debbugs-Cc: eseeseha...@yahoo.es

Dear Maintainer,

When using the prepackaged version of Kakasi in Debian 12, some texts are not
correctly transliterated from kanji to hiragana. Some characters just are
discarded. I think it did not happen in previous Debian releases but I'm not
fully sure. What I can certify is that:

- It works when building Kakasi from source in Debian 12, such as:

  $ apt-get source kakasi; rm -rf kakasi-2.3.6; tar xf kakasi-2.3.6.orig.tar.xz
  $ cd kakasi-2.3.6 ; ./configure ; make
  $ su -c "make install"

- It also works even when building Kakasi on Windows using MSVC (!)

To test the bug, execute the following command:

$ kakasi -iutf8 -s -JH

Then input the following text (the word "subetteru", "it's slipping"):

  滑ってる!?

The correct (expected) result should be:

  すべって る !?

The current (broken) result is:

  て る !?

Some transliterations are fine, some others are not. I don't know if it's a
build flag or what is exactly happening, but as I have managed to reproduce,
building Kakasi from source even in weird architectures (Android and Windows)
does not exhibit this behavior.

I am using the Kakasi dictionaries from Debian, just rebuilding the executable
/ library.

Thank you,
Miguel


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

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

Versions of packages kakasi depends on:
ii  kakasi-dic  2.3.6-4.1
ii  libc6   2.36-9+deb12u3

kakasi recommends no packages.

kakasi suggests no packages.

-- no debconf information


Bug#1056916: freeciv fails to load saved games


On Sun, 26 Nov 2023, Marko Lindqvist wrote:


 I confirmed the issue upstream. Our bugtracker is currently down, so
there's no upstream ticket to link to yet.

 The problem is on the saving side, not loading. Unfortunately this means
that some information is permanently lost, i.e., one will not be able to
load those saved games even after the bug gets fixed.


well, it's not like it's crucial data of strategic world importance, at
least in my case :) 
I will be more than happy if it gets fixed, I don't care that much if I will

not be able to load specific old saved games written before the fix.  Let me
know if I can help with testing.

Bye
Giacomo

--
_

Giacomo Mulas 
_

INAF - Osservatorio Astronomico di Cagliari
via della scienza 5 - 09047 Selargius (CA)

tel.   +39 070 71180255
mob. : +39 329  6603810
_

"every year keeps getting shorter, never seem to find the time
 plans that either come to naught, or half a page of scribbled lines
 the time is gone, the song is over, thought I'd something more to say"
 (Pink Floyd)
_

Bug#1056916: freeciv fails to load saved games

 I confirmed the issue upstream. Our bugtracker is currently down, so
there's no upstream ticket to link to yet.

 The problem is on the saving side, not loading. Unfortunately this means
that some information is permanently lost, i.e., one will not be able to
load those saved games even after the bug gets fixed.


Bug#1056931: libgphoto2-6: Move files into /usr (incl. DEP17 P7 mitigation)

Package: libgphoto2-6
Version: 2.5.31-1
Severity: important
Tags: patch
User: helm...@debian.org
Usertags: dep17p7
X-Debbugs-Cc: helm...@debian.org

Dear Maintainer,

libgphoto2-6 contains udev files which are installed to /lib; these
files need to be moved to /usr/lib as part of Debian's usr-merge effort.
Because your package is Multi-Arch: same, an unfortunate corner-case
can occur whereby shared files (such as the udev files) may be
erroneously removed on upgrades (please see DEP17[1] P7: Shared
multiarch file loss).

You will find a patch attached to move the udev files, including the
mitigation for the file loss scenario. Alternatively, you can also use the
salsa merge request I've opened[2].

Please consider applying this patch at your earliest convenience. This
bug will be upgraded to release critical soon, as it blocks the overall
usr-merge effort which is being undertaken for the trixie release.

Note on the patch, esp. the debian/rules part: this tries to be
compatible with dh_installudev changing its default install path, and
then not break on binNMUs. It's ugly, I know.


Many thanks,
Chris

1. https://subdivi.de/~helmut/dep17.html
2. https://salsa.debian.org/debian-phototools-team/libgphoto2/-/merge_requests/6
>From 314bf4fae75d2823fc4445a84b53aefdd4290dc1 Mon Sep 17 00:00:00 2001
From: Chris Hofstaedtler 
Date: Sun, 26 Nov 2023 21:32:25 +0100
Subject: [PATCH] Move udev files from /lib to /usr/lib

Including protective diversion against Multi-Arch: same file loss scenario
(DEP17 P7 M10).
---
 debian/changelog  |  8 
 debian/libgphoto2-6.lintian-overrides |  6 ++
 debian/libgphoto2-6.postinst  | 19 +++
 debian/libgphoto2-6.postrm| 19 +++
 debian/libgphoto2-6.preinst   | 18 ++
 debian/rules  |  8 ++--
 6 files changed, 76 insertions(+), 2 deletions(-)
 create mode 100644 debian/libgphoto2-6.postinst
 create mode 100644 debian/libgphoto2-6.postrm
 create mode 100644 debian/libgphoto2-6.preinst

diff --git a/debian/changelog b/debian/changelog
index b835d5f57..d666f2a66 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,11 @@
+libgphoto2 (2.5.31-1.1) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Move udev files from /lib to /usr/lib, including protective diversion
+against Multi-Arch: same file loss scenario (DEP17 P7 M10). (Closes: #-1)
+
+ -- Chris Hofstaedtler   Sun, 26 Nov 2023 21:27:28 +0100
+
 libgphoto2 (2.5.31-1) unstable; urgency=medium
 
   * [33c8d67] The kFreeBSD port has been removed
diff --git a/debian/libgphoto2-6.lintian-overrides 
b/debian/libgphoto2-6.lintian-overrides
index dd6d57455..e1ae1f513 100644
--- a/debian/libgphoto2-6.lintian-overrides
+++ b/debian/libgphoto2-6.lintian-overrides
@@ -5,3 +5,9 @@ libgphoto2-6: spelling-error-in-binary Optio Option 
[usr/lib/*/libgphoto2/*/sier
 # strcpy(id->text, "Lumix Wifi") using immediate values.  The letter
 # "H" is part of the next machine instruction, "ifi\0" follows shortly.
 libgphoto2-6: spelling-error-in-binary WiH With 
[usr/lib/*/libgphoto2/*/lumix.so]
+
+# begin-remove-after: released:forky
+# protective diversion for upgrades of files moved from / to /usr
+libgphoto2-6: diversion-for-unknown-file lib/udev/hwdb.d/20-libgphoto2-6.hwdb 
[preinst:*]
+libgphoto2-6: diversion-for-unknown-file 
lib/udev/rules.d/60-libgphoto2-6.rules [preinst:*]
+# end-remove-after
diff --git a/debian/libgphoto2-6.postinst b/debian/libgphoto2-6.postinst
new file mode 100644
index 0..d8269e6cb
--- /dev/null
+++ b/debian/libgphoto2-6.postinst
@@ -0,0 +1,19 @@
+#! /bin/sh
+
+set -e
+
+# begin-remove-after: released:forky
+# protective diversion of files moved from / to /usr, to avoid file loss.
+# Only for upgrades.
+if [ "$1" = "configure" ]; then
+# At this point, the package will have installed the same file in */usr*.
+dpkg-divert --package usr-is-merged --no-rename \
+--divert /lib/udev/hwdb.d/20-libgphoto2-6.hwdb.usr-is-merged \
+--remove /lib/udev/hwdb.d/20-libgphoto2-6.hwdb
+dpkg-divert --package usr-is-merged --no-rename \
+--divert /lib/udev/rules.d/60-libgphoto2-6.rules.usr-is-merged \
+--remove /lib/udev/rules.d/60-libgphoto2-6.rules
+fi
+# end-remove-after
+
+#DEBHELPER#
diff --git a/debian/libgphoto2-6.postrm b/debian/libgphoto2-6.postrm
new file mode 100644
index 0..7584525c3
--- /dev/null
+++ b/debian/libgphoto2-6.postrm
@@ -0,0 +1,19 @@
+#!/bin/sh
+set -e
+
+# begin-remove-after: released:forky
+# protective diversion of files moved from / to /usr, to avoid file loss.
+# Only for upgrades.
+if [ "$1" = "remove" ] && [ "$DPKG_MAINTSCRIPT_PACKAGE_REFCOUNT" = "1" ]; then
+# Cleanup in case package is removed before upgrade is finished (postinst 
ran).
+dpkg-divert --package usr-is-merged --no-rename \
+--divert /lib/udev/hwdb.d/20-libgphoto2-6.hwdb.usr-is-merged \
+--remove 

Bug#1056930: radare2: CVE-2023-47016

Source: radare2
Version: 5.5.0+dfsg-1
Severity: important
Tags: security upstream
Forwarded: https://github.com/radareorg/radare2/issues/22349
X-Debbugs-Cc: car...@debian.org, Debian Security Team 

Hi,

The following vulnerability was published for radare2.

CVE-2023-47016[0]:
| radare2 5.8.9 has an out-of-bounds read in r_bin_object_set_items in
| libr/bin/bobj.c, causing a crash in r_read_le32 in
| libr/include/r_endian.h.


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

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2023-47016
https://www.cve.org/CVERecord?id=CVE-2023-47016
[1] https://github.com/radareorg/radare2/issues/22349
[2] 
https://github.com/radareorg/radare2/commit/40c9f50e127be80b9d816bce2ab2ee790831aefd

Regards,
Salvatore



Bug#1056929: libmirisdr0: Move files into /usr (incl. DEP17 P7 mitigation)

Package: libmirisdr0
Version: 0.0.4.59ba37-5
Severity: important
Tags: patch
User: helm...@debian.org
Usertags: dep17p7
X-Debbugs-Cc: helm...@debian.org

Dear Maintainer,

libmirisdr0 contains udev files which are installed to /lib; these files
need to be moved to /usr/lib as part of Debian's usr-merge effort.
Because your package is Multi-Arch: same, an unfortunate corner-case can
occur whereby shared files (such as the udev rules) may be erroneously
removed on upgrades (please see DEP17[1] P7: Shared multiarch file
loss).

You will find a patch attached to move the udev files, including the
mitigation for the file loss scenario. Alternatively you can find the
changes in a salsa MR[2].

Please consider applying this patch at your earliest convenience. This
bug will be upgraded to release critical soon, as it blocks the overall
usr-merge effort which is being undertaken for the trixie release.


Many thanks,
Chris


[1] https://wiki.debian.org/UsrMerge
diff -Nru libmirisdr-0.0.4.59ba37/debian/changelog 
libmirisdr-0.0.4.59ba37/debian/changelog
--- libmirisdr-0.0.4.59ba37/debian/changelog2016-04-27 03:14:13.0 
+0200
+++ libmirisdr-0.0.4.59ba37/debian/changelog2023-11-26 21:16:08.0 
+0100
@@ -1,3 +1,13 @@
+libmirisdr (0.0.4.59ba37-5.1) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Move udev files from /lib to /usr/lib, including protective diversion
+against Multi-Arch: same file loss scenario (DEP17 P7 M10). (Closes: #-1)
+  * Remove obsolete postinst tasks (ldconfig, udev reload), now handled by
+triggers.
+
+ -- Chris Hofstaedtler   Sun, 26 Nov 2023 21:16:08 +0100
+
 libmirisdr (0.0.4.59ba37-5) unstable; urgency=medium
 
   * swap short descriptions. Thanks Daniele! (Closes: #813996)
diff -Nru libmirisdr-0.0.4.59ba37/debian/libmirisdr0.lintian-overrides 
libmirisdr-0.0.4.59ba37/debian/libmirisdr0.lintian-overrides
--- libmirisdr-0.0.4.59ba37/debian/libmirisdr0.lintian-overrides
1970-01-01 01:00:00.0 +0100
+++ libmirisdr-0.0.4.59ba37/debian/libmirisdr0.lintian-overrides
2023-11-26 21:16:01.0 +0100
@@ -0,0 +1,4 @@
+# begin-remove-after: released:forky
+# protective diversion for upgrades of files moved from / to /usr
+libmirisdr0: diversion-for-unknown-file lib/udev/rules.d/60-libmirisdr0.rules 
[preinst:*]
+# end-remove-after
diff -Nru libmirisdr-0.0.4.59ba37/debian/libmirisdr0.postinst 
libmirisdr-0.0.4.59ba37/debian/libmirisdr0.postinst
--- libmirisdr-0.0.4.59ba37/debian/libmirisdr0.postinst 2013-10-01 
19:39:33.0 +0200
+++ libmirisdr-0.0.4.59ba37/debian/libmirisdr0.postinst 2023-11-26 
21:16:08.0 +0100
@@ -2,28 +2,15 @@
 
 set -e
 
-#DEBHELPER#
-
+# begin-remove-after: released:forky
+# protective diversion of files moved from / to /usr, to avoid file loss.
+# Only for upgrades.
 if [ "$1" = "configure" ]; then
-ldconfig
+# At this point, the package will have installed the same file in */usr*.
+dpkg-divert --package usr-is-merged --no-rename \
+--divert /lib/udev/rules.d/60-libmirisdr0.rules.usr-is-merged \
+--remove /lib/udev/rules.d/60-libmirisdr0.rules
 fi
+# end-remove-after
 
-# same test as udev postinst...
-chrooted() {
-  if [ "$(stat -c %d/%i /)" = "$(stat -Lc %d/%i /proc/1/root 2>/dev/null)" ];
-  then
-# the devicenumber/inode pair of / is the same as that of /sbin/init's
-# root, so we're *not* in a chroot and hence return false.
-return 1
-  fi
-  return 0
-}
-
-if [ "$1" = "configure" ]; then
-  if ! chrooted ; then
-# try to update udev now
-udevadm control --reload-rules || true ;
-  fi
-fi
-
-exit 0
+#DEBHELPER#
diff -Nru libmirisdr-0.0.4.59ba37/debian/libmirisdr0.postrm 
libmirisdr-0.0.4.59ba37/debian/libmirisdr0.postrm
--- libmirisdr-0.0.4.59ba37/debian/libmirisdr0.postrm   1970-01-01 
01:00:00.0 +0100
+++ libmirisdr-0.0.4.59ba37/debian/libmirisdr0.postrm   2023-11-26 
21:16:01.0 +0100
@@ -0,0 +1,16 @@
+#!/bin/sh
+set -e
+
+# begin-remove-after: released:forky
+# protective diversion of files moved from / to /usr, to avoid file loss.
+# Only for upgrades.
+if [ "$1" = "remove" ] && [ "$DPKG_MAINTSCRIPT_PACKAGE_REFCOUNT" = "1" ]; then
+# Cleanup in case package is removed before upgrade is finished (postinst 
ran).
+dpkg-divert --package usr-is-merged --no-rename \
+--divert /lib/udev/rules.d/60-libmirisdr0.rules.usr-is-merged \
+--remove /lib/udev/rules.d/60-libmirisdr0.rules
+fi
+# end-remove-after
+
+#DEBHELPER#
+
diff -Nru libmirisdr-0.0.4.59ba37/debian/libmirisdr0.preinst 
libmirisdr-0.0.4.59ba37/debian/libmirisdr0.preinst
--- libmirisdr-0.0.4.59ba37/debian/libmirisdr0.preinst  1970-01-01 
01:00:00.0 +0100
+++ libmirisdr-0.0.4.59ba37/debian/libmirisdr0.preinst  2023-11-26 
21:16:01.0 +0100
@@ -0,0 +1,15 @@
+#!/bin/sh
+set -e
+
+# begin-remove-after: released:forky
+# protective diversion of files moved from / to /usr, to avoid file loss.
+# Only for upgrades.
+if [ "$1" = 

Bug#1056928: xen: CVE-2023-46835 CVE-2023-46836

Source: xen
Version: 4.17.2+55-g0b56bed864-1
Severity: important
Tags: security upstream
X-Debbugs-Cc: car...@debian.org, Debian Security Team 

Hi,

The following vulnerabilities were published for xen.

CVE-2023-46835[0]:
| x86/AMD: mismatch in IOMMU quarantine page table levels


CVE-2023-46836[1]:
| x86: BTC/SRSO fixes not fully effective


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

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2023-46835
https://www.cve.org/CVERecord?id=CVE-2023-46835
https://xenbits.xen.org/xsa/advisory-445.html
[1] https://security-tracker.debian.org/tracker/CVE-2023-46836
https://www.cve.org/CVERecord?id=CVE-2023-46836
https://xenbits.xen.org/xsa/advisory-446.html

Regards,
Salvatore



Bug#1056927: libhackrf0: Move files into /usr (incl. DEP17 P7 mitigation)

Package: libhackrf0
Version: 2023.01.1-2
Severity: important
Tags: patch
User: helm...@debian.org
Usertags: dep17p7
X-Debbugs-Cc: helm...@debian.org

Dear Maintainer,

libhackrf0 contains udev files which are installed to /lib; these files
need to be moved to /usr/lib as part of Debian's usr-merge effort.
Because your package is Multi-Arch: same, an unfortunate corner-case can
occur whereby shared files (such as the udev rules) may be erroneously
removed on upgrades (please see DEP17[1] P7: Shared multiarch file
loss).

You will find a patch attached to move the udev files, including the
mitigation for the file loss scenario.

Please consider applying this patch at your earliest convenience. This
bug will be upgraded to release critical soon, as it blocks the overall
usr-merge effort which is being undertaken for the trixie release.


Many thanks,
Chris


[1] https://wiki.debian.org/UsrMerge
diff -Nru hackrf-2023.01.1/debian/changelog hackrf-2023.01.1/debian/changelog
--- hackrf-2023.01.1/debian/changelog   2023-10-15 02:26:21.0 +0200
+++ hackrf-2023.01.1/debian/changelog   2023-11-26 20:37:03.0 +0100
@@ -1,3 +1,11 @@
+hackrf (2023.01.1-2.1) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Move udev files from /lib to /usr/lib, including protective diversion
+against Multi-Arch: same file loss scenario (DEP17 P7 M10). (Closes: #-1)
+
+ -- Chris Hofstaedtler   Sun, 26 Nov 2023 20:37:03 +0100
+
 hackrf (2023.01.1-2) unstable; urgency=medium
 
   * update to v2023.01.1-15-g1fd67f66 (Closes: #1036862)
diff -Nru hackrf-2023.01.1/debian/libhackrf0.lintian-overrides 
hackrf-2023.01.1/debian/libhackrf0.lintian-overrides
--- hackrf-2023.01.1/debian/libhackrf0.lintian-overrides1970-01-01 
01:00:00.0 +0100
+++ hackrf-2023.01.1/debian/libhackrf0.lintian-overrides2023-11-26 
20:36:59.0 +0100
@@ -0,0 +1,4 @@
+# begin-remove-after: released:forky
+# protective diversion for upgrades of files moved from / to /usr
+libhackrf0: diversion-for-unknown-file lib/udev/rules.d/60-libhackrf0.rules 
[preinst:*]
+# end-remove-after
diff -Nru hackrf-2023.01.1/debian/libhackrf0.postinst 
hackrf-2023.01.1/debian/libhackrf0.postinst
--- hackrf-2023.01.1/debian/libhackrf0.postinst 1970-01-01 01:00:00.0 
+0100
+++ hackrf-2023.01.1/debian/libhackrf0.postinst 2023-11-26 20:36:59.0 
+0100
@@ -0,0 +1,16 @@
+#! /bin/sh
+
+set -e
+
+# begin-remove-after: released:forky
+# protective diversion of files moved from / to /usr, to avoid file loss.
+# Only for upgrades.
+if [ "$1" = "configure" ]; then
+# At this point, the package will have installed the same file in */usr*.
+dpkg-divert --package usr-is-merged --no-rename \
+--divert /lib/udev/rules.d/60-libhackrf0.rules.usr-is-merged \
+--remove /lib/udev/rules.d/60-libhackrf0.rules
+fi
+# end-remove-after
+
+#DEBHELPER#
diff -Nru hackrf-2023.01.1/debian/libhackrf0.postrm 
hackrf-2023.01.1/debian/libhackrf0.postrm
--- hackrf-2023.01.1/debian/libhackrf0.postrm   1970-01-01 01:00:00.0 
+0100
+++ hackrf-2023.01.1/debian/libhackrf0.postrm   2023-11-26 20:36:59.0 
+0100
@@ -0,0 +1,16 @@
+#!/bin/sh
+set -e
+
+# begin-remove-after: released:forky
+# protective diversion of files moved from / to /usr, to avoid file loss.
+# Only for upgrades.
+if [ "$1" = "remove" ] && [ "$DPKG_MAINTSCRIPT_PACKAGE_REFCOUNT" = "1" ]; then
+# Cleanup in case package is removed before upgrade is finished (postinst 
ran).
+dpkg-divert --package usr-is-merged --no-rename \
+--divert /lib/udev/rules.d/60-libhackrf0.rules.usr-is-merged \
+--remove /lib/udev/rules.d/60-libhackrf0.rules
+fi
+# end-remove-after
+
+#DEBHELPER#
+
diff -Nru hackrf-2023.01.1/debian/libhackrf0.preinst 
hackrf-2023.01.1/debian/libhackrf0.preinst
--- hackrf-2023.01.1/debian/libhackrf0.preinst  1970-01-01 01:00:00.0 
+0100
+++ hackrf-2023.01.1/debian/libhackrf0.preinst  2023-11-26 20:36:59.0 
+0100
@@ -0,0 +1,15 @@
+#!/bin/sh
+set -e
+
+# begin-remove-after: released:forky
+# protective diversion of files moved from / to /usr, to avoid file loss.
+# Only for upgrades.
+if [ "$1" = "upgrade" ]; then
+dpkg-divert --package usr-is-merged --no-rename \
+--divert /lib/udev/rules.d/60-libhackrf0.rules.usr-is-merged \
+--add /lib/udev/rules.d/60-libhackrf0.rules
+fi
+# end-remove-after
+
+#DEBHELPER#
+
diff -Nru hackrf-2023.01.1/debian/rules hackrf-2023.01.1/debian/rules
--- hackrf-2023.01.1/debian/rules   2023-10-15 02:26:21.0 +0200
+++ hackrf-2023.01.1/debian/rules   2023-11-26 20:37:03.0 +0100
@@ -43,3 +45,9 @@
 
 override_dh_installdocs-indep:
dh_installdocs --indep
+
+override_dh_installudev:
+   dh_installudev
+   # This should be harmless for indep builds or after dh_installudev 
changes the install path.
+   set -e; if test -d debian/libhackrf0/lib/udev/rules.d; then mv 
debian/libhackrf0/lib/udev debian/libhackrf0/usr/lib; fi
+  

Bug#1056926: FTBFS: rm: cannot remove 'underscore.js': No such file or directory

Control: tags -1 + patch

* Chris Hofstaedtler  [231126 20:11]:
> your package apparently FTBFS, probably caused by the newer version of
> sphinx.

Please find a patch attached.

Chris

diff -Nru hackrf-2023.01.1/debian/rules hackrf-2023.01.1/debian/rules
--- hackrf-2023.01.1/debian/rules	2023-10-15 02:26:21.0 +0200
+++ hackrf-2023.01.1/debian/rules	2023-11-26 20:37:03.0 +0100
@@ -15,14 +15,16 @@
 	cd docs && make latexpdf
 	cd docs/build/html/_static && rm jquery.js
 	cd docs/build/html/_static && ln -s /usr/share/javascript/jquery/jquery.js jquery.js
-	cd docs/build/html/_static && rm underscore.js
-	cd docs/build/html/_static && ln -s /usr/share/javascript/underscore/underscore.js underscore.js
+	cd docs/build/html/_static && rm _sphinx_javascript_frameworks_compat.js
+	cd docs/build/html/_static && ln -s /usr/share/sphinx/themes/basic/static/_sphinx_javascript_frameworks_compat.js _sphinx_javascript_frameworks_compat.js
 	cd docs/build/html/_static && rm doctools.js
 	cd docs/build/html/_static && ln -s /usr/share/sphinx/themes/basic/static/doctools.js doctools.js
 	cd docs/build/html/_static && rm language_data.js
 	cd docs/build/html/_static && ln -s /usr/share/sphinx/themes/basic/static/language_data.js_t language_data.js
 	cd docs/build/html/_static && rm searchtools.js
 	cd docs/build/html/_static && ln -s /usr/share/sphinx/themes/basic/static/searchtools.js searchtools.js
+	cd docs/build/html/_static && rm sphinx_highlight.js
+	cd docs/build/html/_static && ln -s /usr/share/sphinx/themes/basic/static/sphinx_highlight.js sphinx_highlight.js
 	rm -rf docs/build/html/_static/fonts
 #	cp -p -r firmware-libopencm3/* firmware/libopencm3/
 #	cd firmware && CFLAGS=-Wall CXXFLAGS=-Wall cmake -DCMAKE_VERBOSE_MAKEFILE=ON -DBOARD=HACKRF_ONE -B build_hackrf


Bug#1055090: rust-backtrace: please update to v0.3.69


> Please update to (at least) newer upstream release v0.3.69.

Backtrace itself is not semver breaking, but some of it's dependencies
are.

backtrace 0.3.68 -> 0.3.69
addr2line 0.20.0 -> 0.21.0
fallible-iterator 0.2.0 -> 0.3.0
gimli 0.27.3 -> 0.28.1
object 0.31.1 -> 0.32.1

I've uploaded these to experimental.

Checking out the reverse dependencies:

dwarf2sources - builds ok against new packages, dependency tweak 
required, no autopkgtests
rust-cargo-auditable - builds ok against new packages, dependency tweak 
required, no autopkgtests
rust-elfx86exts - new version builds ok against new packages, no 
autopkgtests.
rust-framehop - needs a patch 
https://github.com/mstange/framehop/issues/12 no rdeps
pdb - has a pre-existing test issue, after dealing with that builds and 
tests fine with dependency bumped.

postgres-protocol - builds and tests ok after dependency bump.
postgres-types - builds and tests ok after dependency bump
tokio-postgres - builds ok after dependency bump, but tests are already 
broken (and marked as such)
postgres - builds ok after dependency bump, but tests are already broken 
(and marked as such)
rusqlite - builds and tests ok after dependency bump, upstream bumped 
with no code changes.
rust-wasmtime (librust-cranelift-dev) - jonas package, builds and 
autopkgtests ok with dependency bumped. 
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1056924

sccache - jonas package, already broken and not in testing.

I've uploaded this to experimental, now waiting to see what
(if-any) responses I get to the bug reports.



Bug#1055687: khmer ftbfs with Python 3.12

Package: khmer
Followup-For: Bug #1055687
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu noble ubuntu-patch
Control: tags -1 patch

Dear Maintainer,

My previous patch was unfortunately very incomplete. I am submitting
another patch that fixes the remaining issues when building with Python
3.12. Both debdiffs should be applied for the build to succeed.

Additional fixes that were needed for the build to succeed:

 * Python 3.12 dropped the "imp" module. Updated to use importlib
instead.
 * Python 3.12 is much less forgiving when a script opens a file for
writing and forgets to close it. Most Python scripts in scripts/ failed
to do so or did so inconsistently. This resulted in the test suite
either hanging or failing. I went through all invocations of open() /
get_file_writer() and ensured that the resources are cleaned up. The
resulting patch is sadly difficult to read though.

I submitted all changes upstream, although I doubt somebody will pick
them up:

https://github.com/dib-lab/khmer/pull/1922

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

  * Fix build against Python 3.12 (LP: #2044383).

Thanks for considering the patch.


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

Kernel: Linux 6.1.0-16-generic (SMP w/8 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
diff -Nru khmer-3.0.0~a3+dfsg/debian/control khmer-3.0.0~a3+dfsg/debian/control
--- khmer-3.0.0~a3+dfsg/debian/control  2023-11-25 17:44:28.0 +0100
+++ khmer-3.0.0~a3+dfsg/debian/control  2023-11-26 02:28:32.0 +0100
@@ -1,6 +1,5 @@
 Source: khmer
-Maintainer: Ubuntu Developers 
-XSBC-Original-Maintainer: Debian Med Packaging Team 

+Maintainer: Debian Med Packaging Team 

 Uploaders: Michael R. Crusoe ,
Kevin Murray 
 Section: science
diff -Nru khmer-3.0.0~a3+dfsg/debian/patches/close-opened-files.patch 
khmer-3.0.0~a3+dfsg/debian/patches/close-opened-files.patch
--- khmer-3.0.0~a3+dfsg/debian/patches/close-opened-files.patch 1970-01-01 
01:00:00.0 +0100
+++ khmer-3.0.0~a3+dfsg/debian/patches/close-opened-files.patch 2023-11-26 
02:28:32.0 +0100
@@ -0,0 +1,1124 @@
+Description: ensure that Python scripts close files that they open for writing 
+ Python scripts under scripts/ in the source tree do not consistently close
+ files that they open for writing. While some of the scripts use context
+ managers, most of them do not (or do so inconsistently).
+ In previous releases of Ubuntu, this apparently was not much of a concern.
+ However, Python 3.12 seems to be much less forgiving when files are not
+ properly closed. When running the test suite, many of the files that are not
+ explicitly closed appear truncated. This leads to various tests failing or
+ hanging and causing FTBFS when the test suite runs at build time.
+ .
+ Furthermore, khmer defines the get_file_writer() function, but it cannot be
+ consistently used as a context manager because it sometimes closes the
+ underlying file descriptor ; and sometimes does not depending on the
+ arguments.
+ .
+ Fixed by defining a new FileWriter context manager and ensuring that
+ each call to open() / get_file_writer() frees up resources properly.
+Author: Olivier Gayot 
+Bug-Ubuntu: https://launchpad.net/bugs/2044383
+Bug-Debian: https://bugs.debian.org/1055687
+Forwarded: https://github.com/dib-lab/khmer/pull/1922
+Last-Update: 2023-11-26
+---
+This patch header follows DEP-3: http://dep.debian.net/deps/dep3/
+Index: khmer-3.0.0~a3+dfsg/scripts/abundance-dist.py
+===
+--- khmer-3.0.0~a3+dfsg.orig/scripts/abundance-dist.py 2023-11-26 
20:23:39.915485717 +0100
 khmer-3.0.0~a3+dfsg/scripts/abundance-dist.py  2023-11-26 
20:23:39.911485747 +0100
+@@ -42,6 +42,7 @@
+ Use '-h' for parameter help.
+ """
+ 
++import contextlib
+ import sys
+ import csv
+ import khmer
+@@ -143,26 +144,28 @@
+ sys.exit(1)
+ 
+ if args.output_histogram_filename in ('-', '/dev/stdout'):
+-countgraph_fp = sys.stdout
++countgraph_ctx = contextlib.nullcontext(enter_result=sys.stdout)
+ else:
+-countgraph_fp = open(args.output_histogram_filename, 'w')
+-countgraph_fp_csv = csv.writer(countgraph_fp)
+-# write headers:
+-countgraph_fp_csv.writerow(['abundance', 'count', 'cumulative',
+-'cumulative_fraction'])
+-
+-sofar = 0
+-for _, i in enumerate(abundances):
+-if i == 0 and not args.output_zero:
+-continue
++countgraph_ctx = open(args.output_histogram_filename, 'w')
+ 
+-

Bug#1056926: FTBFS: rm: cannot remove 'underscore.js': No such file or directory

Source: hackrf
Version: 2022.09.1-3
Severity: serious
Tags: ftbfs

Dear Maintainer,

your package apparently FTBFS, probably caused by the newer version of
sphinx.

Last few lines from the build log:

make[3]: Leaving directory '/<>/docs/build/latex'
make[2]: Leaving directory '/<>/docs'
cd docs/build/html/_static && rm jquery.js
cd docs/build/html/_static && ln -s /usr/share/javascript/jquery/jquery.js 
jquery.js
cd docs/build/html/_static && rm underscore.js
rm: cannot remove 'underscore.js': No such file or directory
make[1]: *** [debian/rules:18: override_dh_auto_build-indep] Error 1
make[1]: Leaving directory '/<>'
make: *** [debian/rules:6: binary] Error 2
dpkg-buildpackage: error: debian/rules binary subprocess returned exit status 2


Thanks,
Chris


Package versions: apt_2.7.6 autoconf_2.71-3 automake_1:1.16.5-1.3 
autopoint_0.21-13 autotools-dev_20220109.1 base-files_13 base-passwd_3.6.2 
bash_5.2.15-2+b6 binutils_2.41-6 binutils-aarch64-linux-gnu_2.41-6 
binutils-common_2.41-6 bsdextrautils_2.39.2-6 bsdutils_1:2.39.2-6 
build-essential_12.10 bzip2_1.0.8-5+b1 ca-certificates_20230311 cmake_3.27.8-1 
cmake-data_3.27.8-1 coreutils_9.1-1 cpp_4:13.2.0-1 cpp-13_13.2.0-5 
dash_0.5.12-6 debconf_1.5.82 debhelper_13.11.8 debian-archive-keyring_2023.4 
debianutils_5.14 dfu-util_0.11-1 dh-autoreconf_20 
dh-strip-nondeterminism_1.13.1-1 diffutils_1:3.10-1 
docutils-common_0.20.1+dfsg-2 dpkg_1.22.1 dpkg-dev_1.22.1 dwz_0.15-1 
e2fsprogs_1.47.0-2+b1 fakeroot_1.32.2-1 file_1:5.45-2 findutils_4.9.0-5 
fontconfig-config_2.14.2-6 fonts-dejavu-core_2.37-8 fonts-dejavu-mono_2.37-8 
fonts-font-awesome_5.0.10+really4.7.0~dfsg-4.1 fonts-lato_2.015-1 
fonts-lmodern_2.005-1 g++_4:13.2.0-1 g++-13_13.2.0-5 gcc_4:13.2.0-1 
gcc-13_13.2.0-5 gcc-13-base_13.2.0-5 gettext_0.21-13+b1 gettext-base_0.21-13+b1 
gpgv_2.2.40-1.1 grep_3.11-3 groff-base_1.23.0-3 gzip_1.12-1 hostname_3.23+nmu1 
init-system-helpers_1.65.2 intltool-debian_0.35.0+20060710.6 latexmk_1:4.80-1 
libacl1_2.3.1-3 libapache-pom-java_29-2 libapt-pkg6.0_2.7.6 
libarchive-zip-perl_1.68-1 libarchive13_3.7.2-1 libasan8_13.2.0-5 
libatomic1_13.2.0-5 libattr1_1:2.5.1-4 libaudit-common_1:3.1.1-1 
libaudit1_1:3.1.1-1 libbinutils_2.41-6 libblkid1_2.39.2-6 libbrotli1_1.1.0-2 
libbsd0_0.11.7-4 libbz2-1.0_1.0.8-5+b1 libc-bin_2.37-12 libc-dev-bin_2.37-12 
libc6_2.37-12 libc6-dev_2.37-12 libcairo2_1.18.0-1 libcap-ng0_0.8.3-1+b3 
libcap2_1:2.66-4 libcc1-0_13.2.0-5 libcom-err2_1.47.0-2+b1 
libcommons-logging-java_1.2-4 libcommons-parent-java_56-1 
libcrypt-dev_1:4.4.36-2 libcrypt1_1:4.4.36-2 libctf-nobfd0_2.41-6 
libctf0_2.41-6 libcurl4_8.4.0-2 libdb5.3_5.3.28+dfsg2-4 libdebconfclient0_0.271 
libdebhelper-perl_13.11.8 libdpkg-perl_1.22.1 libelf1_0.190-1 libexpat1_2.5.0-2 
libext2fs2_1.47.0-2+b1 libfakeroot_1.32.2-1 libffi8_3.4.4-1 
libfftw3-bin_3.3.10-1 libfftw3-dev_3.3.10-1 libfftw3-double3_3.3.10-1 
libfftw3-long3_3.3.10-1 libfftw3-single3_3.3.10-1 libfile-find-rule-perl_0.34-3 
libfile-stripnondeterminism-perl_1.13.1-1 libfontbox-java_1:1.8.16-4 
libfontconfig1_2.14.2-6 libfontenc1_1:1.1.4-1 libfreetype6_2.13.2+dfsg-1 
libgcc-13-dev_13.2.0-5 libgcc-s1_13.2.0-5 libgcrypt20_1.10.2-3 
libgdbm-compat4_1.23-3 libgdbm6_1.23-3 libglib2.0-0_2.78.1-4 
libgmp10_2:6.3.0+dfsg-2 libgnutls30_3.8.1-4+b1 libgomp1_13.2.0-5 
libgpg-error0_1.47-3 libgprofng0_2.41-6 libgraphite2-3_1.3.14-1 
libgssapi-krb5-2_1.20.1-5 libharfbuzz0b_8.0.1-1 libhogweed6_3.9.1-2 
libhwasan0_13.2.0-5 libice6_2:1.0.10-1 libicu72_72.1-4 libidn2-0_2.3.4-1+b1 
libisl23_0.26-3 libitm1_13.2.0-5 libjansson4_2.14-2 
libjs-jquery_3.6.1+dfsg+~3.5.14-1 libjs-sphinxdoc_7.2.6-2 
libjs-underscore_1.13.4~dfsg+~1.11.4-3 libjson-perl_4.1-1 
libjsoncpp25_1.9.5-6 libk5crypto3_1.20.1-5 libkeyutils1_1.6.3-2 
libkpathsea6_2023.20230311.66589-8 libkrb5-3_1.20.1-5 libkrb5support0_1.20.1-5 
libldap-2.5-0_2.5.13+dfsg-5 liblsan0_13.2.0-5 liblz4-1_1.9.4-1 
liblzma5_5.4.5-0.1 libmagic-mgc_1:5.45-2 libmagic1_1:5.45-2 libmd0_1.1.0-1 
libmount1_2.39.2-6 libmpc3_1.3.1-1 libmpfr6_4.2.1-1 libncursesw6_6.4+20231016-1 
libnettle8_3.9.1-2 libnghttp2-14_1.58.0-1 libnsl-dev_1.3.0-3 libnsl2_1.3.0-3 
libnumber-compare-perl_0.03-3 libp11-kit0_0.25.0-5 libpam-modules_1.5.2-9.1 
libpam-modules-bin_1.5.2-9.1 libpam-runtime_1.5.2-9.1 libpam0g_1.5.2-9.1 
libpaper-utils_1.1.29 libpaper1_1.1.29 libpcre2-8-0_10.42-4 
libpdfbox-java_1:1.8.16-4 libperl5.36_5.36.0-9 libpipeline1_1.5.7-1 
libpixman-1-0_0.42.2-1 libpkgconf3_1.8.1-1 libpng16-16_1.6.40-2 
libpotrace0_1.16-2 libproc2-0_2:4.0.4-2 libpsl5_0.21.2-1+b1 
libptexenc1_2023.20230311.66589-8 libpython3-stdlib_3.11.4-5+b1 
libpython3.11-minimal_3.11.6-3 libpython3.11-stdlib_3.11.6-3 
libreadline8_8.2-1.3 librhash0_1.4.3-3 librtmp1_2.4+20151223.gitfa8646d.1-2+b2 
libsasl2-2_2.1.28+dfsg1-4 libsasl2-modules-db_2.1.28+dfsg1-4 
libseccomp2_2.5.4-2 libselinux1_3.5-1 libsemanage-common_3.5-1 
libsemanage2_3.5-1 libsepol2_3.5-1 libsframe1_2.41-6 libsm6_2:1.2.3-1 
libsmartcols1_2.39.2-6 libsqlite3-0_3.44.0-1 

Bug#1056925: libxtrxl0: Move files into /usr (incl. DEP17 P7 mitigation)

Package: libxtrxl0
Version: 0.0.1+git20201202.1b6eddf-1
Severity: important
Tags: patch
User: helm...@debian.org
Usertags: dep17p7
X-Debbugs-Cc: helm...@debian.org

Dear Maintainer,

libxtrxl0 contains udev files which are installed to /lib; these files
need to be moved to /usr/lib as part of Debian's usr-merge effort.
Because your package is Multi-Arch: same, an unfortunate corner-case can
occur whereby shared files (such as the udev rules) may be erroneously
removed on upgrades (please see DEP17[1] P7: Shared multiarch file
loss).

You will find a patch attached to move the udev files, including the
mitigation for the file loss scenario.

Please consider applying this patch at your earliest convenience. This
bug will be upgraded to release critical soon, as it blocks the overall
usr-merge effort which is being undertaken for the trixie release.


Many thanks,
Chris


[1] https://wiki.debian.org/UsrMerge
diff -Nru libxtrxll-0.0.1+git20201202.1b6eddf/debian/changelog 
libxtrxll-0.0.1+git20201202.1b6eddf/debian/changelog
--- libxtrxll-0.0.1+git20201202.1b6eddf/debian/changelog2022-11-09 
10:26:52.0 +0100
+++ libxtrxll-0.0.1+git20201202.1b6eddf/debian/changelog2023-11-26 
20:43:51.0 +0100
@@ -1,3 +1,11 @@
+libxtrxll (0.0.1+git20201202.1b6eddf-1.1) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Move udev files from /lib to /usr/lib, including protective diversion
+against Multi-Arch: same file loss scenario (DEP17 P7 M10). (Closes: #-1)
+
+ -- Chris Hofstaedtler   Sun, 26 Nov 2023 20:43:51 +0100
+
 libxtrxll (0.0.1+git20201202.1b6eddf-1) unstable; urgency=low
 
   * Team upload.
diff -Nru 
libxtrxll-0.0.1+git20201202.1b6eddf/debian/libxtrxll0.lintian-overrides 
libxtrxll-0.0.1+git20201202.1b6eddf/debian/libxtrxll0.lintian-overrides
--- libxtrxll-0.0.1+git20201202.1b6eddf/debian/libxtrxll0.lintian-overrides 
1970-01-01 01:00:00.0 +0100
+++ libxtrxll-0.0.1+git20201202.1b6eddf/debian/libxtrxll0.lintian-overrides 
2023-11-26 20:43:34.0 +0100
@@ -0,0 +1,4 @@
+# begin-remove-after: released:forky
+# protective diversion for upgrades of files moved from / to /usr
+libxtrxll0: diversion-for-unknown-file lib/udev/rules.d/50-libxtrxll0.rules 
[preinst:*]
+# end-remove-after
diff -Nru libxtrxll-0.0.1+git20201202.1b6eddf/debian/libxtrxll0.postinst 
libxtrxll-0.0.1+git20201202.1b6eddf/debian/libxtrxll0.postinst
--- libxtrxll-0.0.1+git20201202.1b6eddf/debian/libxtrxll0.postinst  
1970-01-01 01:00:00.0 +0100
+++ libxtrxll-0.0.1+git20201202.1b6eddf/debian/libxtrxll0.postinst  
2023-11-26 20:43:34.0 +0100
@@ -0,0 +1,16 @@
+#! /bin/sh
+
+set -e
+
+# begin-remove-after: released:forky
+# protective diversion of files moved from / to /usr, to avoid file loss.
+# Only for upgrades.
+if [ "$1" = "configure" ]; then
+# At this point, the package will have installed the same file in */usr*.
+dpkg-divert --package usr-is-merged --no-rename \
+--divert /lib/udev/rules.d/50-libxtrxll0.rules.usr-is-merged \
+--remove /lib/udev/rules.d/50-libxtrxll0.rules
+fi
+# end-remove-after
+
+#DEBHELPER#
diff -Nru libxtrxll-0.0.1+git20201202.1b6eddf/debian/libxtrxll0.postrm 
libxtrxll-0.0.1+git20201202.1b6eddf/debian/libxtrxll0.postrm
--- libxtrxll-0.0.1+git20201202.1b6eddf/debian/libxtrxll0.postrm
1970-01-01 01:00:00.0 +0100
+++ libxtrxll-0.0.1+git20201202.1b6eddf/debian/libxtrxll0.postrm
2023-11-26 20:43:34.0 +0100
@@ -0,0 +1,16 @@
+#!/bin/sh
+set -e
+
+# begin-remove-after: released:forky
+# protective diversion of files moved from / to /usr, to avoid file loss.
+# Only for upgrades.
+if [ "$1" = "remove" ] && [ "$DPKG_MAINTSCRIPT_PACKAGE_REFCOUNT" = "1" ]; then
+# Cleanup in case package is removed before upgrade is finished (postinst 
ran).
+dpkg-divert --package usr-is-merged --no-rename \
+--divert /lib/udev/rules.d/50-libxtrxll0.rules.usr-is-merged \
+--remove /lib/udev/rules.d/50-libxtrxll0.rules
+fi
+# end-remove-after
+
+#DEBHELPER#
+
diff -Nru libxtrxll-0.0.1+git20201202.1b6eddf/debian/libxtrxll0.preinst 
libxtrxll-0.0.1+git20201202.1b6eddf/debian/libxtrxll0.preinst
--- libxtrxll-0.0.1+git20201202.1b6eddf/debian/libxtrxll0.preinst   
1970-01-01 01:00:00.0 +0100
+++ libxtrxll-0.0.1+git20201202.1b6eddf/debian/libxtrxll0.preinst   
2023-11-26 20:43:34.0 +0100
@@ -0,0 +1,15 @@
+#!/bin/sh
+set -e
+
+# begin-remove-after: released:forky
+# protective diversion of files moved from / to /usr, to avoid file loss.
+# Only for upgrades.
+if [ "$1" = "upgrade" ]; then
+dpkg-divert --package usr-is-merged --no-rename \
+--divert /lib/udev/rules.d/50-libxtrxll0.rules.usr-is-merged \
+--add /lib/udev/rules.d/50-libxtrxll0.rules
+fi
+# end-remove-after
+
+#DEBHELPER#
+
diff -Nru libxtrxll-0.0.1+git20201202.1b6eddf/debian/rules 
libxtrxll-0.0.1+git20201202.1b6eddf/debian/rules
--- libxtrxll-0.0.1+git20201202.1b6eddf/debian/rules

Bug#1049995: Openssh catalán translation

Reviewed and changed versión of catalan translation

-- 



ca.pot
Description: MS-Powerpoint presentation


Bug#1056924: rust-wasmtime - upcoming rust-object update.


Package: rust-wasmtime
Version: 10.0.1+dfsg-7

I currently working on an update of rust-backtrace and it's
dependencies, backtrace itself is not semver breaking, but
several of it's dependencies are.

backtrace 0.3.68 -> 0.3.69
addr2line 0.20.0 -> 0.21.0
fallible-iterator 0.2.0 -> 0.3.0
gimli 0.27.3 -> 0.28.1
object 0.31.1 -> 0.32.1

Your package depends on gimli, I have looked at the
upstream changelog and didn't see anything too scary
and I've built your package with the dependency bumped
and run it's autopkgtests successfully.

If you want to do further testing the new version of
the packages are available in experimental.



Bug#1056909: cachefilesd: Installs files into /sbin

Control: tags -1 + patch

* Chris Hofstaedtler  [231126 19:33]:
> your package installs files directly into /sbin. Please move them into
> /usr/sbin during the trixie development cycle.

Here is a trivial patch:

diff --git a/debian/rules b/debian/rules
index 1dd2b01..4d4453a 100755
--- a/debian/rules
+++ b/debian/rules
@@ -3,7 +3,7 @@
 include /usr/share/cdbs/1/rules/debhelper.mk
 include /usr/share/cdbs/1/class/makefile.mk

-DEB_MAKE_INSTALL_TARGET = install DESTDIR=$(DEB_DESTDIR)
+DEB_MAKE_INSTALL_TARGET = install DESTDIR=$(DEB_DESTDIR) SBINDIR=/usr/sbin

 #binary-fixup/cachefilesd::
 #  chmod o-rwx $(DEB_DESTDIR)/var/cache/fscache



Bug#1055737: gpodder don't start , claim abandon

On Fri, Nov 10, 2023 at 12:23:13PM +0100, GT wrote:
> Package: gpodder
> Version: 3.11.3-1
> Severity: important
> 
>  'gpodder.plugins.soundcloud.SoundcloudFavFeed'>>
> Abandon
> 
> 
>* What outcome did you expect instead?
> The GUI should appear

Hello and thank you for the bug report.  I have not yet been able to
reproduce this behavior on my system - including after removing
recommended and suggested dependencies to match the bug report.  And the
only difference between the Settings.json you shared and mine is that
"state" has been initialized with window geometries, but even if I use
your Settings.json, gPodder starts up normally for me.

All of the output logging you shared looks like normal startup output,
up until the string "Abandon," which doesn't appear in the gPodder
sources.  So I'm not sure how to start triaging the problem you're
seeing.  Is it correct to assume that other Python GTK applications are
working as expected?  

Thanks,
tony


signature.asc
Description: PGP signature


Bug#1056780: Fwd: Bug#1056780: openmsx: Source-less Windows binary in source package (and other packaging issues)

Failed to reply to the right address, so forwarding.

-- Forwarded message -
From: Aaron Rainbolt 
Date: Sun, Nov 26, 2023 at 1:30 PM
Subject: Re: Bug#1056780: openmsx: Source-less Windows binary in
source package (and other packaging issues)
To: Manuel Bilderbeek 


Thanks! I was able to find the code for all ROMs and get it included,
so C-BIOS is now no longer an issue. I still have quite a bit more
code to look through so I'll probably take a while longer to get this
done, but it's coming along nicely.

On Sun, Nov 26, 2023 at 1:22 PM Manuel Bilderbeek
 wrote:
>
> On 26-11-2023 18:39, Aaron Rainbolt wrote:
>
> Further investigation trying to rebuild the copyright file has revealed more 
> binaries without source code (the C-BIOS ROMs for instance). So I'll have to 
> find the sources for those also. Thanks for your patience.
>
> The C-BIOS ROMs have their source code, see e.g. the cbios package in Debian, 
> which contains all info to the upstream sources. (As they're packaged 
> separately, they are not part of the openMSX (source) packages in Debian.)
>
> --
> Kind regards,
>
> Manuel Bilderbeek



Bug#1056923: libbladerf2: Move files into /usr (incl. DEP17 P7 mitigation)

Package: libbladerf2
Version: 0.2023.02-2
Severity: important
Tags: patch
User: helm...@debian.org
Usertags: dep17p7
X-Debbugs-Cc: helm...@debian.org

Dear Maintainer,

libbladerf2 contains udev files which are installed to /lib; these
files need to be moved to /usr/lib as part of Debian's usr-merge effort.
Because your package is Multi-Arch: same, an unfortunate corner-case can
occur whereby shared files (such as the udev rules) may be erroneously
removed on upgrades (please see DEP17[1] P7: Shared multiarch file
loss).

You will find a patch attached to move the udev files, including the
mitigation for the file loss scenario.

Please consider applying this patch at your earliest convenience. This
bug will be upgraded to release critical soon, as it blocks the overall
usr-merge effort which is being undertaken for the trixie release.


Many thanks,
Chris


[1] https://wiki.debian.org/UsrMerge
diff -Nru bladerf-0.2023.02/debian/changelog bladerf-0.2023.02/debian/changelog
--- bladerf-0.2023.02/debian/changelog  2023-09-24 04:34:49.0 +0200
+++ bladerf-0.2023.02/debian/changelog  2023-11-26 20:11:52.0 +0100
@@ -1,3 +1,11 @@
+bladerf (0.2023.02-2.1) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Move udev files from /lib to /usr/lib, including protective diversion
+against Multi-Arch: same file loss scenario (DEP17 P7 M10). (Closes: #-1)
+
+ -- Chris Hofstaedtler   Sun, 26 Nov 2023 20:11:52 +0100
+
 bladerf (0.2023.02-2) unstable; urgency=medium
 
   * Use pybuild for building the Python3 bindings to avoid Internet access
diff -Nru bladerf-0.2023.02/debian/libbladerf2.install 
bladerf-0.2023.02/debian/libbladerf2.install
--- bladerf-0.2023.02/debian/libbladerf2.install2022-10-31 
02:13:52.0 +0100
+++ bladerf-0.2023.02/debian/libbladerf2.install2023-11-26 
20:11:10.0 +0100
@@ -1,3 +1,3 @@
 debian/libbladerf2.metainfo.xml usr/share/metainfo
-lib/udev/rules.d/*
+usr/lib/udev/rules.d/*
 usr/lib/*/lib*.so.*
diff -Nru bladerf-0.2023.02/debian/libbladerf2.lintian-overrides 
bladerf-0.2023.02/debian/libbladerf2.lintian-overrides
--- bladerf-0.2023.02/debian/libbladerf2.lintian-overrides  1970-01-01 
01:00:00.0 +0100
+++ bladerf-0.2023.02/debian/libbladerf2.lintian-overrides  2023-11-26 
20:11:52.0 +0100
@@ -0,0 +1,6 @@
+# begin-remove-after: released:forky
+# protective diversion for upgrades of files moved from / to /usr
+libbladerf2: diversion-for-unknown-file 
lib/udev/rules.d/88-nuand-bladerf1.rules [preinst:*]
+libbladerf2: diversion-for-unknown-file 
lib/udev/rules.d/88-nuand-bladerf2.rules [preinst:*]
+libbladerf2: diversion-for-unknown-file 
lib/udev/rules.d/88-nuand-bootloader.rules [preinst:*]
+# end-remove-after
diff -Nru bladerf-0.2023.02/debian/libbladerf2.postinst 
bladerf-0.2023.02/debian/libbladerf2.postinst
--- bladerf-0.2023.02/debian/libbladerf2.postinst   1970-01-01 
01:00:00.0 +0100
+++ bladerf-0.2023.02/debian/libbladerf2.postinst   2023-11-26 
20:11:52.0 +0100
@@ -0,0 +1,22 @@
+#! /bin/sh
+
+set -e
+
+# begin-remove-after: released:forky
+# protective diversion of files moved from / to /usr, to avoid file loss.
+# Only for upgrades.
+if [ "$1" = "configure" ]; then
+# At this point, the package will have installed the same file in */usr*.
+dpkg-divert --package usr-is-merged --no-rename \
+--divert /lib/udev/rules.d/88-nuand-bladerf1.rules.usr-is-merged \
+--remove /lib/udev/rules.d/88-nuand-bladerf1.rules
+dpkg-divert --package usr-is-merged --no-rename \
+--divert /lib/udev/rules.d/88-nuand-bladerf2.rules.usr-is-merged \
+--remove /lib/udev/rules.d/88-nuand-bladerf2.rules
+dpkg-divert --package usr-is-merged --no-rename \
+--divert /lib/udev/rules.d/88-nuand-bootloader.rules.usr-is-merged \
+--remove /lib/udev/rules.d/88-nuand-bootloader.rules
+fi
+# end-remove-after
+
+#DEBHELPER#
diff -Nru bladerf-0.2023.02/debian/libbladerf2.postrm 
bladerf-0.2023.02/debian/libbladerf2.postrm
--- bladerf-0.2023.02/debian/libbladerf2.postrm 1970-01-01 01:00:00.0 
+0100
+++ bladerf-0.2023.02/debian/libbladerf2.postrm 2023-11-26 20:11:52.0 
+0100
@@ -0,0 +1,22 @@
+#!/bin/sh
+set -e
+
+# begin-remove-after: released:forky
+# protective diversion of files moved from / to /usr, to avoid file loss.
+# Only for upgrades.
+if [ "$1" = "remove" ] && [ "$DPKG_MAINTSCRIPT_PACKAGE_REFCOUNT" = "1" ]; then
+# Cleanup in case package is removed before upgrade is finished (postinst 
ran).
+dpkg-divert --package usr-is-merged --no-rename \
+--divert /lib/udev/rules.d/88-nuand-bladerf1.rules.usr-is-merged \
+--remove /lib/udev/rules.d/88-nuand-bladerf1.rules
+dpkg-divert --package usr-is-merged --no-rename \
+--divert /lib/udev/rules.d/88-nuand-bladerf2.rules.usr-is-merged \
+--remove /lib/udev/rules.d/88-nuand-bladerf2.rules
+dpkg-divert --package usr-is-merged --no-rename \
+

Bug#1056922: libairspyhf1: Move files into /usr (incl. DEP17 P7 mitigation)

Package: libairspyhf1
Version: 1.6.8-3
Severity: important
Tags: patch
User: helm...@debian.org
Usertags: dep17p7
X-Debbugs-Cc: helm...@debian.org

Dear Maintainer,

libairspyhf1 contains udev files which are installed to /lib; these
files need to be moved to /usr/lib as part of Debian's usr-merge effort.
Because your package is Multi-Arch: same, an unfortunate corner-case can
occur whereby shared files (such as the udev rules) may be erroneously
removed on upgrades (please see DEP17[1] P7: Shared multiarch file
loss).

You will find a patch attached to move the udev files, including the
mitigation for the file loss scenario.

Please consider applying this patch at your earliest convenience. This
bug will be upgraded to release critical soon, as it blocks the overall
usr-merge effort which is being undertaken for the trixie release.


Many thanks,
Chris


[1] https://wiki.debian.org/UsrMerge
diff -Nru airspyhf-1.6.8/debian/changelog airspyhf-1.6.8/debian/changelog
--- airspyhf-1.6.8/debian/changelog 2020-12-18 02:01:46.0 +0100
+++ airspyhf-1.6.8/debian/changelog 2023-11-26 20:07:43.0 +0100
@@ -1,3 +1,11 @@
+airspyhf (1.6.8-3.1) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Move udev files from /lib to /usr/lib, including protective diversion
+against Multi-Arch: same file loss scenario (DEP17 P7 M10). (Closes: #-1)
+
+ -- Chris Hofstaedtler   Sun, 26 Nov 2023 20:07:43 +0100
+
 airspyhf (1.6.8-3) unstable; urgency=medium
 
   [ Debian Janitor ]
diff -Nru airspyhf-1.6.8/debian/libairspyhf1.lintian-overrides 
airspyhf-1.6.8/debian/libairspyhf1.lintian-overrides
--- airspyhf-1.6.8/debian/libairspyhf1.lintian-overrides1970-01-01 
01:00:00.0 +0100
+++ airspyhf-1.6.8/debian/libairspyhf1.lintian-overrides2023-11-26 
20:07:31.0 +0100
@@ -0,0 +1,4 @@
+# begin-remove-after: released:forky
+# protective diversion for upgrades of files moved from / to /usr
+libairspyhf1: diversion-for-unknown-file 
lib/udev/rules.d/60-libairspyhf1.rules [preinst:*]
+# end-remove-after
diff -Nru airspyhf-1.6.8/debian/libairspyhf1.postinst 
airspyhf-1.6.8/debian/libairspyhf1.postinst
--- airspyhf-1.6.8/debian/libairspyhf1.postinst 1970-01-01 01:00:00.0 
+0100
+++ airspyhf-1.6.8/debian/libairspyhf1.postinst 2023-11-26 20:07:31.0 
+0100
@@ -0,0 +1,16 @@
+#! /bin/sh
+
+set -e
+
+# begin-remove-after: released:forky
+# protective diversion of files moved from / to /usr, to avoid file loss.
+# Only for upgrades.
+if [ "$1" = "configure" ]; then
+# At this point, the package will have installed the same file in */usr*.
+dpkg-divert --package usr-is-merged --no-rename \
+--divert /lib/udev/rules.d/60-libairspyhf1.rules.usr-is-merged \
+--remove /lib/udev/rules.d/60-libairspyhf1.rules
+fi
+# end-remove-after
+
+#DEBHELPER#
diff -Nru airspyhf-1.6.8/debian/libairspyhf1.postrm 
airspyhf-1.6.8/debian/libairspyhf1.postrm
--- airspyhf-1.6.8/debian/libairspyhf1.postrm   1970-01-01 01:00:00.0 
+0100
+++ airspyhf-1.6.8/debian/libairspyhf1.postrm   2023-11-26 20:07:31.0 
+0100
@@ -0,0 +1,16 @@
+#!/bin/sh
+set -e
+
+# begin-remove-after: released:forky
+# protective diversion of files moved from / to /usr, to avoid file loss.
+# Only for upgrades.
+if [ "$1" = "remove" ] && [ "$DPKG_MAINTSCRIPT_PACKAGE_REFCOUNT" = "1" ]; then
+# Cleanup in case package is removed before upgrade is finished (postinst 
ran).
+dpkg-divert --package usr-is-merged --no-rename \
+--divert /lib/udev/rules.d/60-libairspyhf1.rules.usr-is-merged \
+--remove /lib/udev/rules.d/60-libairspyhf1.rules
+fi
+# end-remove-after
+
+#DEBHELPER#
+
diff -Nru airspyhf-1.6.8/debian/libairspyhf1.preinst 
airspyhf-1.6.8/debian/libairspyhf1.preinst
--- airspyhf-1.6.8/debian/libairspyhf1.preinst  1970-01-01 01:00:00.0 
+0100
+++ airspyhf-1.6.8/debian/libairspyhf1.preinst  2023-11-26 20:07:31.0 
+0100
@@ -0,0 +1,15 @@
+#!/bin/sh
+set -e
+
+# begin-remove-after: released:forky
+# protective diversion of files moved from / to /usr, to avoid file loss.
+# Only for upgrades.
+if [ "$1" = "upgrade" ]; then
+dpkg-divert --package usr-is-merged --no-rename \
+--divert /lib/udev/rules.d/60-libairspyhf1.rules.usr-is-merged \
+--add /lib/udev/rules.d/60-libairspyhf1.rules
+fi
+# end-remove-after
+
+#DEBHELPER#
+
diff -Nru airspyhf-1.6.8/debian/rules airspyhf-1.6.8/debian/rules
--- airspyhf-1.6.8/debian/rules 2020-08-11 04:59:21.0 +0200
+++ airspyhf-1.6.8/debian/rules 2023-11-26 20:07:43.0 +0100
@@ -11,3 +11,9 @@
 
 override_dh_auto_configure:
dh_auto_configure $@ -- -DLIB_SUFFIX=/$(DEB_HOST_MULTIARCH)
+
+override_dh_installudev:
+   dh_installudev
+   # This should be harmless when dh_installudev automatically installs to 
/usr/lib/udev/rules.d.
+   set -e; if test -d debian/libairspyhf1/lib/udev/rules.d; then mv 
debian/libairspyhf1/lib/udev debian/libairspyhf1/usr/lib; fi
+   set 

Bug#1056780: openmsx: Source-less Windows binary in source package (and other packaging issues)


On 26-11-2023 18:39, Aaron Rainbolt wrote:
Further investigation trying to rebuild the copyright file has 
revealed more binaries without source code (the C-BIOS ROMs for 
instance). So I'll have to find the sources for those also. Thanks for 
your patience.


The C-BIOS ROMs have their source code, see e.g. the cbios package in 
Debian, which contains all info to the upstream sources. (As they're 
packaged separately, they are not part of the openMSX (source) packages 
in Debian.)


--
Kind regards,

Manuel Bilderbeek


Bug#1056911: libfreenect0.5: Move files into /usr (incl. DEP17 P7 mitigation)

* Chris Hofstaedtler  [231126 19:17]:
> You will find a patch attached to move the udev files, including the
> mitigation for the file loss scenario.

Please find the patch attached.

Chris

>From 1ebec5c13e777a9ebf08a23082ddb29f5abf40f1 Mon Sep 17 00:00:00 2001
From: Chris Hofstaedtler 
Date: Sun, 26 Nov 2023 15:58:01 +0100
Subject: [PATCH] Move udev files from /lib to /usr/lib

Including protective diversion against Multi-Arch: same file loss scenario
(DEP17 P7 M10).

Closes: #-1
---
 debian/changelog|  8 
 debian/libfreenect0.5.lintian-overrides |  4 
 debian/libfreenect0.5.postinst  | 16 
 debian/libfreenect0.5.postrm| 16 
 debian/libfreenect0.5.preinst   | 15 +++
 debian/rules|  5 +
 6 files changed, 64 insertions(+)
 create mode 100644 debian/libfreenect0.5.lintian-overrides
 create mode 100644 debian/libfreenect0.5.postinst
 create mode 100644 debian/libfreenect0.5.postrm
 create mode 100644 debian/libfreenect0.5.preinst

diff --git a/debian/changelog b/debian/changelog
index c522c56..8a4be24 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,11 @@
+libfreenect (1:0.5.3-3.1) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Move udev files from /lib to /usr/lib, including protective diversion
+against Multi-Arch: same file loss scenario (DEP17 P7 M10). (Closes: #-1)
+
+ -- Chris Hofstaedtler   Sun, 26 Nov 2023 15:57:36 +0100
+
 libfreenect (1:0.5.3-3) unstable; urgency=medium
 
   * debian/control
diff --git a/debian/libfreenect0.5.lintian-overrides b/debian/libfreenect0.5.lintian-overrides
new file mode 100644
index 000..da45f8d
--- /dev/null
+++ b/debian/libfreenect0.5.lintian-overrides
@@ -0,0 +1,4 @@
+# begin-remove-after: released:forky
+# protective diversion for upgrades of files moved from / to /usr
+libfreenect0.5: diversion-for-unknown-file lib/udev/rules.d/60-libfreenect0.5.rules [preinst:*]
+# end-remove-after
diff --git a/debian/libfreenect0.5.postinst b/debian/libfreenect0.5.postinst
new file mode 100644
index 000..40074e3
--- /dev/null
+++ b/debian/libfreenect0.5.postinst
@@ -0,0 +1,16 @@
+#! /bin/sh
+
+set -e
+
+# begin-remove-after: released:forky
+# protective diversion of files moved from / to /usr, to avoid file loss.
+# Only for upgrades.
+if [ "$1" = "configure" ]; then
+# At this point, the package will have installed the same file in */usr*.
+dpkg-divert --package usr-is-merged --no-rename \
+--divert /lib/udev/rules.d/60-libfreenect0.5.rules.usr-is-merged \
+--remove /lib/udev/rules.d/60-libfreenect0.5.rules
+fi
+# end-remove-after
+
+#DEBHELPER#
diff --git a/debian/libfreenect0.5.postrm b/debian/libfreenect0.5.postrm
new file mode 100644
index 000..20645b8
--- /dev/null
+++ b/debian/libfreenect0.5.postrm
@@ -0,0 +1,16 @@
+#!/bin/sh
+set -e
+
+# begin-remove-after: released:forky
+# protective diversion of files moved from / to /usr, to avoid file loss.
+# Only for upgrades.
+if [ "$1" = "remove" ] && [ "$DPKG_MAINTSCRIPT_PACKAGE_REFCOUNT" = "1" ]; then
+# Cleanup in case package is removed before upgrade is finished (postinst ran).
+dpkg-divert --package usr-is-merged --no-rename \
+--divert /lib/udev/rules.d/60-libfreenect0.5.rules.usr-is-merged \
+--remove /lib/udev/rules.d/60-libfreenect0.5.rules
+fi
+# end-remove-after
+
+#DEBHELPER#
+
diff --git a/debian/libfreenect0.5.preinst b/debian/libfreenect0.5.preinst
new file mode 100644
index 000..896e975
--- /dev/null
+++ b/debian/libfreenect0.5.preinst
@@ -0,0 +1,15 @@
+#!/bin/sh
+set -e
+
+# begin-remove-after: released:forky
+# protective diversion of files moved from / to /usr, to avoid file loss.
+# Only for upgrades.
+if [ "$1" = "upgrade" ]; then
+dpkg-divert --package usr-is-merged --no-rename \
+--divert /lib/udev/rules.d/60-libfreenect0.5.rules.usr-is-merged \
+--add /lib/udev/rules.d/60-libfreenect0.5.rules
+fi
+# end-remove-after
+
+#DEBHELPER#
+
diff --git a/debian/rules b/debian/rules
index d5ba96d..8809d11 100755
--- a/debian/rules
+++ b/debian/rules
@@ -23,6 +23,11 @@ endif
 override_dh_installdocs:
 	dh_installdocs --all CONTRIB
 
+override_dh_installudev:
+	dh_installudev
+	set -e; if test -d debian/libfreenect0.5/lib/udev/rules.d; then mv debian/libfreenect0.5/lib/udev debian/libfreenect0.5/usr/lib; fi
+	set -e; if test -d debian/libfreenect0.5/lib; then rmdir debian/libfreenect0.5/lib; fi
+
 override_dh_makeshlibs:
 	dh_makeshlibs -Xfakenect
 
-- 
2.39.2



Bug#1055646: gdb: extremely slow response to basic commands


Hello,

I have found the root cause of this problem:
It doesn't matter if the gdb is compiled with sbuild, debuild or 
dpkg-buildpackage. It's slow, because it reads BFDs from a *hidden* 
directory "/usr/lib/debug/.build-id/"
The gdb compiled using "configure" script had different prefix, so its 
"relocatable" paths were pointing to an empty "debug" directory - that's 
why it was "fast".


But, this is not the end of problems:
When the gdb is started, it reads symbols from target program and from 
libraries which are loaded by the target program. In my test case 
(2.5MiB executable with debug symbols included + wxWidgets library with 
dbgsym package installed) the symbol table size is ~8MiB, and the gdb 
process is using ~50MiB.
This is sufficient to debug the program, but after issuing the "run" 
command, the BFDs from "/usr/lib/debug/.build-id/" are read - and gdb 
creates a Monster Symbol Table with size over 200MiB (~280Mib used in 
total).
Then things are getting only worse - any gdb command for displaying type 
or value of target program' variables causes the the memory consumption 
to double, in my case from ~280MiB to ~570MiB and the response times 
become deadly slow.


But, this is not the end of problems: (2)
In all test cases the gdb was compiled with --enable-threading - and 
indeed, gdb creates (num_CPU +1) threads on startup (in my case it's 17 
for 16-core CPU). But the threading support in gdb is an illusion - 
those additional threads are *never* used, with a single exception - 
they are used only after the "run" command is issued, probably to read 
the BFDs. For any other gdb command only the main thread is consuming 
CPU time.


I thought that this BUG should be easy to eliminate - but it turns out 
that there are several serious BUGs in the gdb, and the only way to 
eliminate them is to debug the gdb first ;)


Regards



Bug#1056784: ITP: bankstown -- barebones, fast LV2 bass enhancement plugin

Hi Andreas,

Quoting Andreas Henriksson (2023-11-26 16:41:46)
> On Sun, Nov 26, 2023 at 04:18:33PM +0100, Andreas Henriksson wrote:
> > Hello Jonas,
> > 
> [...]
> > I've now renamed the *binary* package to bankstown-lv2,
> [...] 
> 
> Oh well, I'm renaming the source as well. I guess we can always
> rename our git repo to match and pretent like everything is
> bankstown-lv2.
> 
> Just for comparison, I downloaded all sources for binary packages called
> '*-lv2' and 5 of 15 had -lv2 suffix in the orig tarball name (so 1/3).

Thanks for your detailed reflections and arguments - I admire that,
regardless of the outcome.

 - Jonas

-- 
 * Jonas Smedegaard - idealist & Internet-arkitekt
 * Tlf.: +45 40843136  Website: http://dr.jones.dk/
 * Sponsorship: https://ko-fi.com/drjones

 [x] quote me freely  [ ] ask before reusing  [ ] keep private

signature.asc
Description: signature


Bug#1056921: kernsmooth: [L10N,DE] kernsmooth_2.23-22-1_R: german translation

Source: kernsmooth
Version: 2.23-20-1
Severity: wishlist

Dear Maintainer,

please find attached the po file with the german translation.
It is an update to the current po template.
The file has been accepted upstream already and should appear
in the next release.

Kind regards,
Christoph Brinkhaus

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

Kernel: Linux 6.1.0-13-amd64 (SMP w/4 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
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
# Translation of kernsmooth to German
# Copyright (C) 2009 The R Foundation
# This file is distributed under the same license as the kernsmooth package.
# Chris Leick , 2009.
# Christoph Brinkhaus , 2023.
#
msgid ""
msgstr ""
"Project-Id-Version: kernsmooth 2.23-22-1_R-de\n"
"Report-Msgid-Bugs-To: b...@r-project.org\n"
"POT-Creation-Date: 2021-02-12 09:20\n"
"PO-Revision-Date: 2023-11-20 17:10+0100\n"
"Last-Translator: Christoph Brinkhaus \n"
"Language-Team: German \n"
"Language: de\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
"Plural-Forms: nplurals=2; plural=(n != 1);\n"

msgid "'bandwidth' must be strictly positive"
msgstr "»bandwidth« muss streng positiv sein"

msgid "'canonical' must be a length-1 logical vector"
msgstr "»canonical« muss ein Logik-Vektor der Länge 1 sein"

msgid ""
"Binning grid too coarse for current (small) bandwidth: consider increasing "
"'gridsize'"
msgstr ""
"Klasseneinteilungsgitter zu grob für derzeitige (kleine) Bandbreite: Erwägen "
"Sie, »gridsize« zu erhöhen."

msgid "Level should be between 0 and 5"
msgstr "Level sollte zwischen 0 und 5 sein"

msgid "scale estimate is zero for input data"
msgstr "Skalenabschätzung ist für Eingabedaten Null"

msgid "'bandwidth' must be a scalar or an array of length 'gridsize'"
msgstr "»bandwidth« muss ein Skalar oder ein Array der Länge »gridsize« sein"

msgid ""
"KernSmooth 2.23 loaded\n"
"Copyright M. P. Wand 1997-2009"
msgstr ""
"KernSmooth 2.23 geladen\n"
"Copyright M.P. Wand 1997-2009"

#~ msgid "x data has zero standard deviation"
#~ msgstr "x-Daten haben Standardabweichung Null"

#~ msgid "y data has zero standard deviation"
#~ msgstr "y-Daten haben Standardabweichung Null"


Bug#1056919: ardour: Appears in menus as Ardour7


Hi and thanks for the report.

I've already fixed that the 29 october but didn't ask for a new build 
since it's only a small thing that can wait for the next upload.
In other words, next time something will be done on the build (probably 
next version if nothing important comes up before), it will be there.


All the best,
Olivier

--
Site web : https://librazik.tuxfamily.org/
Donation : https://liberapay.com/LibraZiK/
Diaspora : 
https://framasphere.org/people/8c184af0c9450134f6682a053625

Mastodon : https://mastodon.xyz/@LibraZiK



Bug#1056587: texlive-latex-base: some math characters get replaced as of Debian's TeX Live 2023

On 2023-11-25 12:28:05 +0900, Norbert Preining wrote:
> On Sat, 25 Nov 2023, Vincent Lefevre wrote:
> > I didn't break anything. Any user, including root, may have his own
> > environment variables for his own use. This should never interfer
> 
> No. That is simply not true. Not root.

Could you cite documentation saying that root must not set
arbitrary environment variables?

> > Why not unsetting TEXINPUTS in the postinst script?
> 
> I told you this already, please read.
> Because root might set TEXINPUTS on *purpose*.

This contradicts what you said above.

Note: The setting of TEXINPUTS in my case was not on purpose
(well, actually keeping the usual settings, such as LS_COLORS,
was actually there on purpose). But this could have been done
really on purpose. And this would have broken the package
installation.

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



Bug#1056616: firefox: Firefox tab freeze when using BigBlueButton

Package: firefox
Version: 120.0-2
Followup-For: Bug #1056616

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Hi,

I'm having the same issue. Each time this happens, one of the following message 
is logged:

$ journalctl --no-hostname -b -t firefox.desktop --grep="signal 15"
nov. 25 00:06:16 firefox.desktop[4109]: [Parent 4109, IPC I/O Parent] WARNING: 
process 5019 exited on signal 15: file 
./ipc/chromium/src/base/process_util_posix.cc:265
nov. 25 00:06:21 firefox.desktop[4109]: [Parent 4109, IPC I/O Parent] WARNING: 
process 5121 exited on signal 15: file 
./ipc/chromium/src/base/process_util_posix.cc:265
nov. 25 00:09:39 firefox.desktop[4109]: [Parent 4109, IPC I/O Parent] WARNING: 
process 5450 exited on signal 15: file 
./ipc/chromium/src/base/process_util_posix.cc:265
nov. 25 00:11:20 firefox.desktop[4109]: [Parent 4109, IPC I/O Parent] WARNING: 
process 5612 exited on signal 15: file 
./ipc/chromium/src/base/process_util_posix.cc:265
nov. 25 00:13:54 firefox.desktop[4109]: [Parent 4109, IPC I/O Parent] WARNING: 
process 5773 exited on signal 15: file 
./ipc/chromium/src/base/process_util_posix.cc:265
nov. 25 11:39:03 firefox.desktop[4109]: [Parent 4109, IPC I/O Parent] WARNING: 
process 7242 exited on signal 15: file 
./ipc/chromium/src/base/process_util_posix.cc:265
nov. 25 11:40:22 firefox.desktop[4109]: [Parent 4109, IPC I/O Parent] WARNING: 
process 10185 exited on signal 15: file 
./ipc/chromium/src/base/process_util_posix.cc:265
nov. 25 11:40:59 firefox.desktop[4109]: [Parent 4109, IPC I/O Parent] WARNING: 
process 10684 exited on signal 15: file 
./ipc/chromium/src/base/process_util_posix.cc:265
nov. 25 11:41:30 firefox.desktop[4109]: [Parent 4109, IPC I/O Parent] WARNING: 
process 10963 exited on signal 15: file 
./ipc/chromium/src/base/process_util_posix.cc:265
nov. 25 12:03:33 firefox.desktop[4109]: [Parent 4109, IPC I/O Parent] WARNING: 
process 12228 exited on signal 15: file 
./ipc/chromium/src/base/process_util_posix.cc:265
nov. 25 12:06:15 firefox.desktop[4109]: [Parent 4109, IPC I/O Parent] WARNING: 
process 12399 exited on signal 15: file 
./ipc/chromium/src/base/process_util_posix.cc:265
nov. 25 12:08:04 firefox.desktop[13293]: [Parent 13293, IPC I/O Parent] 
WARNING: process 13505 exited on signal 15: file 
./ipc/chromium/src/base/process_util_posix.cc:265
nov. 26 14:14:58 firefox.desktop[13293]: [Parent 13293, IPC I/O Parent] 
WARNING: process 20426 exited on signal 15: file 
./ipc/chromium/src/base/process_util_posix.cc:265
nov. 26 15:06:39 firefox.desktop[13293]: [Parent 13293, IPC I/O Parent] 
WARNING: process 42403 exited on signal 15: file 
./ipc/chromium/src/base/process_util_posix.cc:265
nov. 26 15:35:09 firefox.desktop[13293]: [Parent 13293, IPC I/O Parent] 
WARNING: process 44221 exited on signal 15: file 
./ipc/chromium/src/base/process_util_posix.cc:265
nov. 26 15:54:05 firefox.desktop[13293]: [Parent 13293, IPC I/O Parent] 
WARNING: process 45807 exited on signal 15: file 
./ipc/chromium/src/base/process_util_posix.cc:265
nov. 26 16:14:30 firefox.desktop[13293]: [Parent 13293, IPC I/O Parent] 
WARNING: process 48716 exited on signal 15: file 
./ipc/chromium/src/base/process_util_posix.cc:265
nov. 26 16:16:40 firefox.desktop[13293]: [Parent 13293, IPC I/O Parent] 
WARNING: process 13854 exited on signal 15: file 
./ipc/chromium/src/base/process_util_posix.cc:265
nov. 26 17:15:39 firefox.desktop[13293]: [Parent 13293, IPC I/O Parent] 
WARNING: process 53954 exited on signal 15: file 
./ipc/chromium/src/base/process_util_posix.cc:265
nov. 26 17:16:29 firefox.desktop[13293]: [Parent 13293, IPC I/O Parent] 
WARNING: process 54021 exited on signal 15: file 
./ipc/chromium/src/base/process_util_posix.cc:265
nov. 26 18:50:27 firefox.desktop[13293]: [Parent 13293, IPC I/O Parent] 
WARNING: process 58308 exited on signal 15: file 
./ipc/chromium/src/base/process_util_posix.cc:265

-BEGIN PGP SIGNATURE-

iHUEARYKAB0WIQSRJQjHKbAUfuoc+DAQn1qAt/bgAQUCZWOMYAAKCRAQn1qAt/bg
AVa/AQD1zDrGPrQJLIJtNiJZNIOM2HC0Iymdw58xvS0Ix86XegD/YOsGj62Druym
exqd/CDAENB7cKK1GSpVG2oACRHJkgo=
=YP0B
-END PGP SIGNATURE-



Bug#1056362: RFS: ruby-mdl/0.13.0-4 -- Markdown lint tool - transitional dummy package

Also uploaded ruby-mdl_0.13.0-4~bpo12+1.dsc:
Uploading to ftp-master [DELAYED/6-day] (via ftp to ftp.upload.debian.org):

DELAYED/6 so that -4 it will be in testing when it enters the backport NEW 
queue.
(as per backports policy the same version needs to be in testing first.)

--
tobi



Bug#1056906: debuild: cannot disable lintian

Il giorno dom 26 nov 2023 alle ore 14:37 Adam D. Barratt
 ha scritto:
>
> Control: tags -1 + moreinfo
>
> On Sun, 2023-11-26 at 14:06 +0100, Fabio Pedretti wrote:
> > when I add --no-lintian (as found in debuild man page) option
> > to debuild, I get the following error:
> >
> > ...
> >  dpkg-buildpackage -us -uc -ui -S -sd -d --no-lintian
> > dpkg-buildpackage: error: unknown option or argument --no-lintian
>
> That suggests you've added it in the wrong part of the command line.
> https://manpages.debian.org/bookworm/devscripts/debuild.1.en.html
> clearly shows in the synopsis that all debuild-specific options must
> come _before_ any dpkg-buildpackage-specific options, and that --(no-
> )lintian affects the behaviour of debuild itself, so falls into the
> former set.
>
> What *exactly* does your debuild invocation look like?

You are right, I was calling it this way:
debuild -S -sd -d -kMYKEY --no-lintian
while this way it works:
debuild --no-lintian -S -sd -d -kMYKEY

About the man page, it says:
debuild [debuild options] [dpkg‐buildpackage options] [--lintian‐opts
lintian options]
which let me suppose lintian options have to be called at last. But it
is just for the specific --lintian‐opts, not --(no-)lintian, OK.

> > I also tried setting:
> > export DEBUILD_LINTIAN=no
> > but it still uses lintian.
> >
>
> If you've added that to your shell, or a file like .profile, then
> that's not particularly surprising, given that the same manpage also
> says that DEBUILD_LINTIAN is a configuration variable, which is read
> from one of two files, and "[e]nvironment variable settings are ignored
> when these configuration files are read". (In common with almost every
> variable any script in devscripts uses.)

/etc/devscripts.conf says "This file is sourced by /bin/bash ...",
however, as you says, there is that note in debuild man page.

Thanks for the quick reply, I suppose we could close this issue.



Bug#1056780: openmsx: Source-less Windows binary in source package (and other packaging issues)

Further investigation trying to rebuild the copyright file has revealed 
more binaries without source code (the C-BIOS ROMs for instance). So 
I'll have to find the sources for those also. Thanks for your patience.


--
Aaron Rainbolt
Lubuntu Developer
Matrix: @arraybolt3:matrix.org
IRC: arraybolt3 on irc.libera.chat
GitHub: https://github.com/ArrayBolt3



Bug#1056920: linux-image-6.1.0-13-amd64: With kernel linux-image-6.1.0-13-amd64 the computer crashes when suspending/rebooting/halting

Package: src:linux
Version: 6.1.55-1
Severity: important
X-Debbugs-Cc: nicolas.demengel+deb...@gmail.com

Dear Maintainer,

   * What led up to the situation?

Upgrading kernel from linux-image-6.1.0-11-amd64 to linux-image-6.1.0-13-amd64

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

I suspended my computer to RAM.
I rebooted my computer.
I shut down my computer.

   * What was the outcome of this action?

In all the situations above, my computer hangs forever, with a black screen in 
case of suspending to RAM, or with the Debian shutdown screen in case of a 
reboot or shutdown.

   * What outcome did you expect instead?

I expected my computer to actually suspend to RAM (and then be resumable), or 
restart, or shut down.

   * More details

I could not find any seemingly related information to explain the issue when 
running journalctl.
I reconfigured grub to use the previous kernel (linux-image-6.1.0-11-amd64) and 
the problem went away.


I thank you in advance for investigating and fixing the issue if possible in 
next versions.

Best regards,
Nicolas Grisey Demengel

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

** Model information
sys_vendor: Apple Inc.
product_name: MacBookPro6,2
product_version: 1.0
chassis_vendor: Apple Inc.
chassis_version: Mac-F22586C8
bios_vendor: Apple Inc.
bios_version: 99.0.0.0.0
board_vendor: Apple Inc.
board_name: Mac-F22586C8
board_version: MacBookPro6,2

** PCI devices:
00:00.0 Host bridge [0600]: Intel Corporation Core Processor DRAM Controller 
[8086:0044] (rev 18)
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- 

00:01.0 PCI bridge [0604]: Intel Corporation Core Processor PCI Express x16 
Root Port [8086:0045] (rev 18) (prog-if 00 [Normal decode])
Subsystem: Intel Corporation Core Processor PCI Express x16 Root Port 
[8086:]
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- Reset- FastB2B-
PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn-
Capabilities: 
Kernel driver in use: pcieport

00:02.0 VGA compatible controller [0300]: Intel Corporation Core Processor 
Integrated Graphics Controller [8086:0046] (rev 18) (prog-if 00 [VGA 
controller])
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- 
Kernel driver in use: i915
Kernel modules: i915

00:1a.0 USB controller [0c03]: Intel Corporation 5 Series/3400 Series Chipset 
USB Universal Host Controller [8086:3b3b] (rev 06) (prog-if 00 [UHCI])
Subsystem: Intel Corporation 5 Series/3400 Series Chipset USB Universal 
Host Controller [8086:7270]
Control: I/O+ Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- 
SERR- 
Kernel modules: uhci_hcd

00:1a.7 USB controller [0c03]: Intel Corporation 5 Series/3400 Series Chipset 
USB2 Enhanced Host Controller [8086:3b3c] (rev 06) (prog-if 20 [EHCI])
Subsystem: Intel Corporation 5 Series/3400 Series Chipset USB2 Enhanced 
Host Controller [8086:7270]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- 
SERR- 
Kernel driver in use: ehci-pci
Kernel modules: ehci_pci

00:1b.0 Audio device [0403]: Intel Corporation 5 Series/3400 Series Chipset 
High Definition Audio [8086:3b56] (rev 06)
Subsystem: Intel Corporation 5 Series/3400 Series Chipset High 
Definition Audio [8086:7270]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- 
Kernel driver in use: snd_hda_intel
Kernel modules: snd_hda_intel

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

00:1c.1 PCI bridge [0604]: Intel Corporation 5 Series/3400 Series Chipset PCI 
Express Root Port 2 [8086:3b44] (rev 06) (prog-if 

Bug#1056919: ardour: Appears in menus as Ardour7

Package: ardour
Version: 1:8.1.0+ds-1
Severity: minor


/usr/share/applications/ardour.desktop hasn't been updated to reflect
the version number:

[Desktop Entry]
Version=1.0
Name=Ardour7
GenericName=Ardour Digital Audio Workstation 7
Comment=Record, mix and master multi-track audio
GenericName[fr]=Station de travail audionumérique Ardour 7
...


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

Kernel: Linux 6.5.0-4-amd64 (SMP w/4 CPU threads; PREEMPT)
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
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages ardour depends on:
ii  ardour-data  1:8.1.0+ds-1
ii  ardour-lv2-plugins   1:8.1.0+ds-1
ii  libarchive13 3.7.2-1
ii  libasound2   1.2.10-1
ii  libatkmm-1.6-1v5 2.28.3-2
ii  libaubio50.4.9-4.3+b2
ii  libc62.37-12
ii  libcairo21.18.0-1
ii  libcairomm-1.0-1v5   1.14.4-2
ii  libcurl3-gnutls  8.4.0-2
ii  libcwiid10.6.91-5
ii  libdbus-1-3  1.14.10-3
ii  libfftw3-single3 3.3.10-1
ii  libfluidsynth3   2.3.4-1
ii  libfontconfig1   2.14.2-6
ii  libgcc-s113.2.0-6
ii  libgdk-pixbuf-2.0-0  2.42.10+dfsg-3
ii  libglib2.0-0 2.78.1-4
ii  libglibmm-2.4-1v52.66.6-2
ii  libgtk2.0-0  2.24.33-2
ii  libgtkmm-2.4-1v5 1:2.24.5-4+b1
ii  liblilv-0-0  0.24.22-1
ii  liblo7   0.31-1
ii  liblrdf0 0.6.1-4
ii  libltc11 1.3.2-1
ii  libpango-1.0-0   1.51.0+ds-3
ii  libpangocairo-1.0-0  1.51.0+ds-3
ii  libpangoft2-1.0-01.51.0+ds-3
ii  libpangomm-1.4-1v5   2.46.3-1
ii  libpulse016.1+dfsg1-2+b1
ii  libqm-dsp0   1.7.1-6
ii  libreadline8 8.2-1.3
ii  librubberband2   3.3.0+dfsg-2
ii  libsamplerate0   0.2.2-4
ii  libsigc++-2.0-0v52.12.1-1
ii  libsndfile1  1.2.2-1
ii  libstdc++6   13.2.0-6
ii  libsuil-0-0  0.10.20-1
ii  libtag1v51.13.1-1
ii  libusb-1.0-0 2:1.0.26-1
ii  libvamp-hostsdk3v5   2.10.0-4
ii  libvamp-sdk2v5   2.10.0-4
ii  libwebsockets19  4.3.2-4
ii  libx11-6 2:1.8.7-1
ii  libxml2  2.9.14+dfsg-1.3

Versions of packages ardour recommends:
pn  ardour-video-timeline  

ardour suggests no packages.

-- no debconf information


Bug#1056918: bullseye-pu: package perl/5.32.1-4+deb11u3

Package: release.debian.org
Severity: normal
Tags: bullseye
User: release.debian@packages.debian.org
Usertags: pu
X-Debbugs-Cc: p...@packages.debian.org, Salvatore Bonaccorso 
Control: affects -1 + src:perl

[ Reason ]
I'd like to fix #1056746 / CVE-2023-47038 in perl for bullseye.  It's a
non-DSA security issue that was made public yesterday and fixed upstream
in 5.34.2.

[ Impact ]
CVE-2023-47038 has security impact for applications that use untrusted
regular expressions to match input.

[ Tests ]
The fix augments the test suite to check for this issue. I have also
checked manually that the crash is gone with the patch. I reviewed amd64
binary debdiffs too and did some installation tests.

[ Risks ]
The fix is minimal and was trivially backported from the upstream fix in
5.34.1. It only differs from the one in sid / 5.36.0-10 by some fuzz. I
don't expect any fallout, but obviously I'll report here if any problems
are found in the 5.36.0-10 testing migration checks.

[ 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 ]
The only change is a patch to the regexp engine in regcomp.c
and the associated new tests. The patch description has
a long explanation of the issue.

[ Other info ]
I'm uploading right away as I don't expect any of this to be
controversial. Hope that's fine by you.

Thanks for your work on Debian.
diff -Nru perl-5.32.1/debian/changelog perl-5.32.1/debian/changelog
--- perl-5.32.1/debian/changelog2021-09-24 19:10:58.0 +0300
+++ perl-5.32.1/debian/changelog2023-11-25 23:03:14.0 +0200
@@ -1,3 +1,10 @@
+perl (5.32.1-4+deb11u3) bullseye; urgency=medium
+
+  * [SECURITY] CVE-2023-47038: Write past buffer end via illegal
+user-defined Unicode property. (Closes: #1056746)
+
+ -- Niko Tyni   Sat, 25 Nov 2023 23:03:14 +0200
+
 perl (5.32.1-4+deb11u2) bullseye; urgency=medium
 
   * Apply upstream patch fixing a regexp memory leak. (Closes: #994834)
diff -Nru perl-5.32.1/debian/patches/fixes/CVE-2023-47038.diff 
perl-5.32.1/debian/patches/fixes/CVE-2023-47038.diff
--- perl-5.32.1/debian/patches/fixes/CVE-2023-47038.diff1970-01-01 
02:00:00.0 +0200
+++ perl-5.32.1/debian/patches/fixes/CVE-2023-47038.diff2023-11-25 
23:03:14.0 +0200
@@ -0,0 +1,119 @@
+From: Karl Williamson 
+Date: Sat, 9 Sep 2023 11:59:09 -0600
+Subject: Fix read/write past buffer end: perl-security#140
+
+A package name may be specified in a \p{...} regular expression
+construct.  If unspecified, "utf8::" is assumed, which is the package
+all official Unicode properties are in.  By specifying a different
+package, one can create a user-defined property with the same
+unqualified name as a Unicode one.  Such a property is defined by a sub
+whose name begins with "Is" or "In", and if the sub wishes to refer to
+an official Unicode property, it must explicitly specify the "utf8::".
+S_parse_uniprop_string() is used to parse the interior of both \p{} and
+the user-defined sub lines.
+
+In S_parse_uniprop_string(), it parses the input "name" parameter,
+creating a modified copy, "lookup_name", malloc'ed with the same size as
+"name".  The modifications are essentially to create a canonicalized
+version of the input, with such things as extraneous white-space
+stripped off.  I found it convenient to strip off the package specifier
+"utf8::".  To to so, the code simply pretends "lookup_name" begins just
+after the "utf8::", and adjusts various other values to compensate.
+However, it missed the adjustment of one required one.
+
+This is only a problem when the property name begins with "perl" and
+isn't "perlspace" nor "perlword".  All such ones are undocumented
+internal properties.
+
+What happens in this case is that the input is reparsed with slightly
+different rules in effect as to what is legal versus illegal.  The
+problem is that "lookup_name" no longer is pointing to its initial
+value, but "name" is.  Thus the space allocated for filling "lookup_name"
+is now shorter than "name", and as this shortened "lookup_name" is
+filled by copying suitable portions of "name", the write can be to
+unallocated space.
+
+The solution is to skip the "utf8::" when reparsing "name".  Then both
+"lookup_name" and "name" are effectively shortened by the same amount,
+and there is no going off the end.
+
+This commit also does white-space adjustment so that things align
+vertically for readability.
+
+This can be easily backported to earlier Perl releases.
+
+Bug-Debian: https://bugs.debian.org/1056746
+Origin: backport, 
https://github.com/Perl/perl5/commit/12c313ce49b36160a7ca2e9b07ad5bd92ee4a010
+---
+ regcomp.c   | 17 +++--
+ t/re/pat_advanced.t |  8 
+ 2 files changed, 19 insertions(+), 6 deletions(-)
+
+diff --git a/regcomp.c b/regcomp.c
+index 5c72ff7..d282ebc 100644

Bug#1055600: transition: suitesparse-7.3

Le vendredi 17 novembre 2023 à 07:43 +0100, Sebastian Ramacher a
écrit :
> On 2023-11-08 18:00:20 +0100, Sébastien Villemot wrote:
> > Package: release.debian.org
> > Severity: normal
> > User: release.debian@packages.debian.org
> > Usertags: transition
> > Control: forwarded -1 
> > https://release.debian.org/transitions/html/auto-suitesparse.html

> > Please schedule a transition for suitesparse 7.3, which currently sits in
> > experimental.
> > 
> > One the shared libraries got a SOVERSION bump (libcholmod4 → libcholmod5). 
> > The
> > ABI change is minor and I’m therefore fairly confident that there won’t be 
> > any
> > issue.
> 
> Please go ahead.

The transition is mostly complete.

The only remaining issue is an autopkgtest failure of octave in
testing, reported as #1056392.

I’ve argued there that this issue only affects partial upgrades, and
that I’m not sure how to fix it (if fixing is needed at all). Please
advise.

-- 
⢀⣴⠾⠻⢶⣦⠀  Sébastien Villemot
⣾⠁⢠⠒⠀⣿⡁  Debian Developer
⢿⡄⠘⠷⠚⠋⠀  https://sebastien.villemot.name
⠈⠳⣄  https://www.debian.org



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


Bug#1053241: glibc: please apply upstream patch to fix slow fstat

Il giorno dom 26 nov 2023 alle ore 16:28 Aurelien Jarno
 ha scritto:
>
> Hi,
>
> On 2023-09-29 21:52, Fabio Pedretti wrote:
> > Package: glibc
> > Version: 2.36-9+deb12u1
> > Severity: normal
> > X-Debbugs-Cc: pedretti.fa...@gmail.com
> >
> > Dear Maintainer,
> >
> > glibc uses a slow version of fstat. Details are documented
> > here: https://lwn.net/Articles/944214/
> >
> > A patch to fix this was merged in glibc:
> > https://sourceware.org/git/?p=glibc.git;a=commitdiff;h=551101e8240b7514fc646d1722f8b79c90362b8f
> >
> > The patch applies cleanly and builds fine also on bookworm glibc.
> > Please consider apply it to fix slow fstat.
>
> This patch changes the syscall used by binaries, so it has to be
> considered with a lot of care in a stable release, it could break
> existing seccomp filters. In any case it has to live a few months in
> testing/unstable first.
>
> Note that the kernel patch that improves the performance of fstatat, has
> not been merge to the upstream stable tree, nor to bookworm.
>
> In order to better understand the need for this patch in bookworm, could
> you please give some details about your workload and the performance
> impact it has?

I did some test with my use case, borg backup with many unchanged
files, see https://github.com/borgbackup/borg/issues/4498 for some
background and system calls impact, where borg 1.2 slow downs a lot
vs. borg 1.1.

I checked using strace the patch, it did the job (newfstatat calls
were replaced with fstat), and I'd hoped that it would improve
performance, however my use case improved just marginally (difficult
to have reproducible data in my case, but it was like 5%).

I didn't notice any other regression, however.

I see the glibc patch is still only on 2.39, while even Debian
experimental has just 2.38.

The alternative kernel patch is in 6.6 (as you say, still not in Debian).

Given all of this, I agree we can wait to land it on trixie and leave
bookworm as is, so feel free to just close the issue in this case.

Thanks for your time.



Bug#1056917: bookworm-pu: package perl/5.36.0-7+deb12u1

Package: release.debian.org
Severity: normal
Tags: bookworm
User: release.debian@packages.debian.org
Usertags: pu
X-Debbugs-Cc: p...@packages.debian.org, Salvatore Bonaccorso 
Control: affects -1 + src:perl

[ Reason ]
I'd like to fix #1056746 / CVE-2023-47038 in perl for bookworm.  It's a
non-DSA security issue that was made public yesterday and fixed upstream
in 5.36.2.

[ Impact ]
CVE-2023-47038 has security impact for applications that use untrusted
regular expressions to match input.

[ Tests ]
The fix augments the test suite to check for this issue. I have also
checked manually that the crash is gone with the patch. I reviewed amd64
binary debdiffs too and did some installation tests.

[ Risks ]
The fix is minimal and identical to the one in sid / 5.36.0-10.  I don't
expect any fallout, but obviously I'll report here if any problems are
found in the testing migration checks.

[ 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 ]
The only change is a patch to the regexp engine in regcomp.c
and the associated new tests. The patch description has
a long explanation of the issue.

[ Other info ]
I'm uploading right away as I don't expect any of this to be
controversial. Hope that's fine by you.

Thanks for your work on Debian.
diff -Nru perl-5.36.0/debian/changelog perl-5.36.0/debian/changelog
--- perl-5.36.0/debian/changelog2023-01-08 23:28:47.0 +0200
+++ perl-5.36.0/debian/changelog2023-11-25 22:59:54.0 +0200
@@ -1,3 +1,10 @@
+perl (5.36.0-7+deb12u1) bookworm; urgency=medium
+
+  * [SECURITY] CVE-2023-47038: Write past buffer end via illegal
+user-defined Unicode property. (Closes: #1056746)
+
+ -- Niko Tyni   Sat, 25 Nov 2023 22:59:54 +0200
+
 perl (5.36.0-7) unstable; urgency=medium
 
   * Break backuppc (<< 4.4.0-7~) due to Data::Dumper changes in 5.36
diff -Nru perl-5.36.0/debian/patches/fixes/CVE-2023-47038.diff 
perl-5.36.0/debian/patches/fixes/CVE-2023-47038.diff
--- perl-5.36.0/debian/patches/fixes/CVE-2023-47038.diff1970-01-01 
02:00:00.0 +0200
+++ perl-5.36.0/debian/patches/fixes/CVE-2023-47038.diff2023-11-25 
22:59:54.0 +0200
@@ -0,0 +1,119 @@
+From: Karl Williamson 
+Date: Sat, 9 Sep 2023 11:59:09 -0600
+Subject: Fix read/write past buffer end: perl-security#140
+
+A package name may be specified in a \p{...} regular expression
+construct.  If unspecified, "utf8::" is assumed, which is the package
+all official Unicode properties are in.  By specifying a different
+package, one can create a user-defined property with the same
+unqualified name as a Unicode one.  Such a property is defined by a sub
+whose name begins with "Is" or "In", and if the sub wishes to refer to
+an official Unicode property, it must explicitly specify the "utf8::".
+S_parse_uniprop_string() is used to parse the interior of both \p{} and
+the user-defined sub lines.
+
+In S_parse_uniprop_string(), it parses the input "name" parameter,
+creating a modified copy, "lookup_name", malloc'ed with the same size as
+"name".  The modifications are essentially to create a canonicalized
+version of the input, with such things as extraneous white-space
+stripped off.  I found it convenient to strip off the package specifier
+"utf8::".  To to so, the code simply pretends "lookup_name" begins just
+after the "utf8::", and adjusts various other values to compensate.
+However, it missed the adjustment of one required one.
+
+This is only a problem when the property name begins with "perl" and
+isn't "perlspace" nor "perlword".  All such ones are undocumented
+internal properties.
+
+What happens in this case is that the input is reparsed with slightly
+different rules in effect as to what is legal versus illegal.  The
+problem is that "lookup_name" no longer is pointing to its initial
+value, but "name" is.  Thus the space allocated for filling "lookup_name"
+is now shorter than "name", and as this shortened "lookup_name" is
+filled by copying suitable portions of "name", the write can be to
+unallocated space.
+
+The solution is to skip the "utf8::" when reparsing "name".  Then both
+"lookup_name" and "name" are effectively shortened by the same amount,
+and there is no going off the end.
+
+This commit also does white-space adjustment so that things align
+vertically for readability.
+
+This can be easily backported to earlier Perl releases.
+
+Bug-Debian: https://bugs.debian.org/1056746
+Origin: backport, 
https://github.com/Perl/perl5/commit/7047915eef37fccd93e7cd985c29fe6be54650b6
+---
+ regcomp.c   | 17 +++--
+ t/re/pat_advanced.t |  8 
+ 2 files changed, 19 insertions(+), 6 deletions(-)
+
+diff --git a/regcomp.c b/regcomp.c
+index 4051333..9c0338c 100644
+--- a/regcomp.c
 b/regcomp.c
+@@ -24178,7 +24178,7 @@ S_parse_uniprop_string(pTHX_
+  * 

Bug#1055889: RFS: urlview/1b-1 [ITA] -- Extracts URLs from text

Control: tags -1 moreinfo

Hi,

a short review:
- d/copyright misses a few files/has inaccuracies, e.g enter.h
  please review & update.

Otherwise it looks good, thanks for taking care of urlview and your
contributions to Debian!

Cheers,
--
tobi



Bug#1055290: libevent: Fix libc-dev build-dep

Hello,

Nicolas Mora, le dim. 26 nov. 2023 10:35:22 -0500, a ecrit:
> However, I'm wondering if the fix is required when the package will be
> re-uploaded to unstable, because the Build-Depends to libc6-dev was added to
> check the build against glibc 2.38 (#1043108)
> 
> When glibc 2.38 will be uploded to unstable, I expect do the same for
> libevent, without the builddep to libc6-dev.

Once glibc 2.38 enters testing, that makes sense indeed. But don't hold
your breath :)

Samuel



Bug#1056915: libffado2: Move files into /usr (incl. DEP17 P7 mitigation)

Please find the patch attached.

Chris

>From ac698d36e0ee4bbe082d40d786e9a906610ae42d Mon Sep 17 00:00:00 2001
From: Chris Hofstaedtler 
Date: Sun, 26 Nov 2023 17:32:36 +0100
Subject: [PATCH] Move udev files from /lib to /usr/lib

Including protective diversion against Multi-Arch: same file loss scenario
(DEP17 P7 M10).
---
 debian/changelog   |  8 
 debian/libffado2.install   |  2 +-
 debian/libffado2.lintian-overrides |  4 
 debian/libffado2.postinst  | 16 
 debian/libffado2.postrm| 16 
 debian/libffado2.preinst   | 15 +++
 debian/rules   |  1 +
 7 files changed, 61 insertions(+), 1 deletion(-)
 create mode 100644 debian/libffado2.lintian-overrides
 create mode 100644 debian/libffado2.postinst
 create mode 100644 debian/libffado2.postrm
 create mode 100644 debian/libffado2.preinst

diff --git a/debian/changelog b/debian/changelog
index 028b0e8..ace26e2 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,11 @@
+libffado (2.4.7-1.1) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Move udev files from /lib to /usr/lib, including protective diversion
+against Multi-Arch: same file loss scenario (DEP17 P7 M10). (Closes: #-1)
+
+ -- Chris Hofstaedtler   Sun, 26 Nov 2023 17:31:51 +0100
+
 libffado (2.4.7-1) unstable; urgency=medium
 
   * New upstream version 2.4.7
diff --git a/debian/libffado2.install b/debian/libffado2.install
index 42cc806..0ac4e1c 100644
--- a/debian/libffado2.install
+++ b/debian/libffado2.install
@@ -1,3 +1,3 @@
-lib/udev
+usr/lib/udev
 usr/lib/*/libffado.so.*
 usr/share/libffado2/configuration
diff --git a/debian/libffado2.lintian-overrides 
b/debian/libffado2.lintian-overrides
new file mode 100644
index 000..7d6e5c5
--- /dev/null
+++ b/debian/libffado2.lintian-overrides
@@ -0,0 +1,4 @@
+# begin-remove-after: released:forky
+# protective diversion for upgrades of files moved from / to /usr
+libffado2: diversion-for-unknown-file lib/udev/rules.d/60-ffado.rules 
[preinst:*]
+# end-remove-after
diff --git a/debian/libffado2.postinst b/debian/libffado2.postinst
new file mode 100644
index 000..da321c3
--- /dev/null
+++ b/debian/libffado2.postinst
@@ -0,0 +1,16 @@
+#! /bin/sh
+
+set -e
+
+# begin-remove-after: released:forky
+# protective diversion of files moved from / to /usr, to avoid file loss.
+# Only for upgrades.
+if [ "$1" = "configure" ]; then
+# At this point, the package will have installed the same file in */usr*.
+dpkg-divert --package usr-is-merged --no-rename \
+--divert /lib/udev/rules.d/60-ffado.rules.usr-is-merged \
+--remove /lib/udev/rules.d/60-ffado.rules
+fi
+# end-remove-after
+
+#DEBHELPER#
diff --git a/debian/libffado2.postrm b/debian/libffado2.postrm
new file mode 100644
index 000..468eed6
--- /dev/null
+++ b/debian/libffado2.postrm
@@ -0,0 +1,16 @@
+#!/bin/sh
+set -e
+
+# begin-remove-after: released:forky
+# protective diversion of files moved from / to /usr, to avoid file loss.
+# Only for upgrades.
+if [ "$1" = "remove" ] && [ "$DPKG_MAINTSCRIPT_PACKAGE_REFCOUNT" = "1" ]; then
+# Cleanup in case package is removed before upgrade is finished (postinst 
ran).
+dpkg-divert --package usr-is-merged --no-rename \
+--divert /lib/udev/rules.d/60-ffado.rules.usr-is-merged \
+--remove /lib/udev/rules.d/60-ffado.rules
+fi
+# end-remove-after
+
+#DEBHELPER#
+
diff --git a/debian/libffado2.preinst b/debian/libffado2.preinst
new file mode 100644
index 000..7c88026
--- /dev/null
+++ b/debian/libffado2.preinst
@@ -0,0 +1,15 @@
+#!/bin/sh
+set -e
+
+# begin-remove-after: released:forky
+# protective diversion of files moved from / to /usr, to avoid file loss.
+# Only for upgrades.
+if [ "$1" = "upgrade" ]; then
+dpkg-divert --package usr-is-merged --no-rename \
+--divert /lib/udev/rules.d/60-ffado.rules.usr-is-merged \
+--add /lib/udev/rules.d/60-ffado.rules
+fi
+# end-remove-after
+
+#DEBHELPER#
+
diff --git a/debian/rules b/debian/rules
index 57c831f..f5c2218 100755
--- a/debian/rules
+++ b/debian/rules
@@ -10,6 +10,7 @@ FLAGS= \
PREFIX=/usr \
DESTDIR=$(CURDIR)/debian/tmp \
LIBDIR=/usr/lib/$(DEB_HOST_MULTIARCH) \
+   UDEVDIR=/usr/lib/udev/rules.d/ \
SHAREDIR=/usr/share/libffado2/ \
MANDIR=/usr/share/man/ \
PYPKGDIR=/usr/share/ffado-mixer-qt4/ \
-- 
2.39.2



Bug#1056780: openmsx: Source-less Windows binary in source package (and other packaging issues)

My reasoning here is that the openMSX code specifies "Some source
files contain a license notice; all other source files are licensed
under the GNU Public License (GPL), of which you can find a copy in
the file 'GPL.txt'." That file contains a GPL-2 license, so the
repository-wide license is GPL-2. To me specifying it as such seemed
reasonable, and Lintian was complaining that the package pointed to
the /usr/share/common-licenses/GPL symlink, which insinuates that all
of the source code is licensed as GPL version 3 and will be relicensed
to a newer
version of the GPL when that license is published and Debian
introduces it. This is at least *more* accurate than what was there
before.

I do not disagree that this is only partially accurate as it places a
blanket licensing statement over the entirety of the source code that
individual files may override. Ideally the copyright file should be
rebuilt from scratch by auditing the entirety of the openMSX source
code licenses. I can do that if it would be helpful.

--
Aaron Rainbolt
Lubuntu Developer
Matrix: @arraybolt3:matrix.org
IRC: arraybolt3 on irc.libera.chat
GitHub: https://github.com/ArrayBolt3



Bug#1056916: freeciv fails to load saved games

Package: freeciv
Version: 3.0.8-1
Severity: normal

Dear Maintainer,

When playing a game in a large scenario (earth, giant), games saved after some 
turn do not get reloaded correctly. I attach here the last save that reloads 
correctly and the first that does not, to help debugging this. Let me know if 
there is some test I can do to help.

Best regards,
Giacomo Mulas


-- System Information:
Debian Release: trixie/sid
  APT prefers unstable
  APT policy: (401, 'unstable'), (10, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 6.5.0-4-amd64 (SMP w/12 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
Locale: LANG=it_IT.UTF-8, LC_CTYPE=it_IT.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 freeciv depends on:
ii  freeciv-client-gtk3  3.0.8-1
ii  freeciv-data 3.0.8-1

freeciv recommends no packages.

freeciv suggests no packages.

-- no debconf information



Bug#1056915: libffado2: Move files into /usr (incl. DEP17 P7 mitigation)

Package: libffado2
Version: 2.4.7-1
Severity: important
Tags: patch
User: helm...@debian.org
Usertags: dep17p7
X-Debbugs-Cc: helm...@debian.org

Dear Maintainer,

libffado2 contains udev files which are installed to /lib; these files
need to be moved to /usr/lib as part of Debian's usr-merge effort.
Because your package is Multi-Arch: same, an unfortunate corner-case can
occur whereby shared files (such as the udev rules) may be erroneously
removed on upgrades (please see DEP17[1] P7: Shared multiarch file
loss).

You will find a patch attached to move the udev files, including the
mitigation for the file loss scenario. Alternatively you can find the
changes in a salsa MR[2].

Please consider applying this patch at your earliest convenience. This
bug will be upgraded to release critical soon, as it blocks the overall
usr-merge effort which is being undertaken for the trixie release.


Many thanks,
Chris


[1] https://wiki.debian.org/UsrMerge
[2] https://salsa.debian.org/multimedia-team/ffado/-/merge_requests/4



Bug#1056914: libiio0: Move files into /usr (incl. DEP17 P7 mitigation)

Package: libiio0
Version: 0.25-1
Severity: important
Tags: patch
User: helm...@debian.org
Usertags: dep17p7
X-Debbugs-Cc: helm...@debian.org

Dear Maintainer,

libiio0 contains udev files which are installed to /lib; these files
need to be moved to /usr/lib as part of Debian's usr-merge effort.
Because your package is Multi-Arch: same, an unfortunate corner-case can
occur whereby shared files (such as the udev rules) may be erroneously
removed on upgrades (please see DEP17[1] P7: Shared multiarch file
loss).

You will find a patch attached to move the udev files, including the
mitigation for the file loss scenario. 

Please consider applying this patch at your earliest convenience. This
bug will be upgraded to release critical soon, as it blocks the overall
usr-merge effort which is being undertaken for the trixie release.


Many thanks,
Chris


[1] https://wiki.debian.org/UsrMerge
diff -Nru libiio-0.25/debian/changelog libiio-0.25/debian/changelog
--- libiio-0.25/debian/changelog2023-08-11 01:28:57.0 +0200
+++ libiio-0.25/debian/changelog2023-11-26 16:29:08.0 +0100
@@ -1,3 +1,11 @@
+libiio (0.25-1.1) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Move udev files from /lib to /usr/lib, including protective diversion
+against Multi-Arch: same file loss scenario (DEP17 P7 M10). (Closes: #-1)
+
+ -- Chris Hofstaedtler   Sun, 26 Nov 2023 16:29:08 +0100
+
 libiio (0.25-1) unstable; urgency=medium
 
   * New upstream release
diff -Nru libiio-0.25/debian/libiio0.install libiio-0.25/debian/libiio0.install
--- libiio-0.25/debian/libiio0.install  2022-07-10 18:20:01.0 +0200
+++ libiio-0.25/debian/libiio0.install  2023-11-26 16:29:08.0 +0100
@@ -1,2 +1,2 @@
 usr/lib/*/libiio.so.0*
-lib/udev/rules.d/90-libiio0.rules
+usr/lib/udev/rules.d/90-libiio0.rules
diff -Nru libiio-0.25/debian/libiio0.lintian-overrides 
libiio-0.25/debian/libiio0.lintian-overrides
--- libiio-0.25/debian/libiio0.lintian-overrides1970-01-01 
01:00:00.0 +0100
+++ libiio-0.25/debian/libiio0.lintian-overrides2023-11-26 
16:29:08.0 +0100
@@ -0,0 +1,4 @@
+# begin-remove-after: released:forky
+# protective diversion for upgrades of files moved from / to /usr
+libiio0: diversion-for-unknown-file lib/udev/rules.d/90-libiio0.rules 
[preinst:*]
+# end-remove-after
diff -Nru libiio-0.25/debian/libiio0.postinst 
libiio-0.25/debian/libiio0.postinst
--- libiio-0.25/debian/libiio0.postinst 1970-01-01 01:00:00.0 +0100
+++ libiio-0.25/debian/libiio0.postinst 2023-11-26 16:29:08.0 +0100
@@ -0,0 +1,16 @@
+#! /bin/sh
+
+set -e
+
+# begin-remove-after: released:forky
+# protective diversion of files moved from / to /usr, to avoid file loss.
+# Only for upgrades.
+if [ "$1" = "configure" ]; then
+# At this point, the package will have installed the same file in */usr*.
+dpkg-divert --package usr-is-merged --no-rename \
+--divert /lib/udev/rules.d/90-libiio0.rules.usr-is-merged \
+--remove /lib/udev/rules.d/90-libiio0.rules
+fi
+# end-remove-after
+
+#DEBHELPER#
diff -Nru libiio-0.25/debian/libiio0.postrm libiio-0.25/debian/libiio0.postrm
--- libiio-0.25/debian/libiio0.postrm   1970-01-01 01:00:00.0 +0100
+++ libiio-0.25/debian/libiio0.postrm   2023-11-26 16:29:08.0 +0100
@@ -0,0 +1,16 @@
+#!/bin/sh
+set -e
+
+# begin-remove-after: released:forky
+# protective diversion of files moved from / to /usr, to avoid file loss.
+# Only for upgrades.
+if [ "$1" = "remove" ] && [ "$DPKG_MAINTSCRIPT_PACKAGE_REFCOUNT" = "1" ]; then
+# Cleanup in case package is removed before upgrade is finished (postinst 
ran).
+dpkg-divert --package usr-is-merged --no-rename \
+--divert /lib/udev/rules.d/90-libiio0.rules.usr-is-merged \
+--remove /lib/udev/rules.d/90-libiio0.rules
+fi
+# end-remove-after
+
+#DEBHELPER#
+
diff -Nru libiio-0.25/debian/libiio0.preinst libiio-0.25/debian/libiio0.preinst
--- libiio-0.25/debian/libiio0.preinst  1970-01-01 01:00:00.0 +0100
+++ libiio-0.25/debian/libiio0.preinst  2023-11-26 16:29:08.0 +0100
@@ -0,0 +1,15 @@
+#!/bin/sh
+set -e
+
+# begin-remove-after: released:forky
+# protective diversion of files moved from / to /usr, to avoid file loss.
+# Only for upgrades.
+if [ "$1" = "upgrade" ]; then
+dpkg-divert --package usr-is-merged --no-rename \
+--divert /lib/udev/rules.d/90-libiio0.rules.usr-is-merged \
+--add /lib/udev/rules.d/90-libiio0.rules
+fi
+# end-remove-after
+
+#DEBHELPER#
+
diff -Nru libiio-0.25/debian/rules libiio-0.25/debian/rules
--- libiio-0.25/debian/rules2023-08-10 21:39:04.0 +0200
+++ libiio-0.25/debian/rules2023-11-26 16:29:08.0 +0100
@@ -6,7 +6,8 @@
 
 override_dh_auto_configure:
dh_auto_configure -- -DCMAKE_SKIP_INSTALL_RPATH=On -DWITH_SYSTEMD=On 
-DWITH_SYSVINIT=On \
-   -DPYTHON_BINDINGS=ON -DWITH_DOC=ON -DWITH_MAN=ON
+   -DPYTHON_BINDINGS=ON -DWITH_DOC=ON 

Bug#1054657: Transition issue for r-cran-rstanarm (Was: Bug#1055922: rmatrix: ABI change in Matrix 1.6-2)

Hi Graham,

Am Fri, Nov 24, 2023 at 10:20:38PM +0100 schrieb Andreas Tille:
> > Closing now because there's nothing to be done in rmatrix.
> > 
> > The remaining regressions seen are caused by unrelated uploads of
> > r-cran-seurat/r-cran-seuratobject on 2023-11-01 and

r-cran-seuratobject 5.0.1-1 has migrated to testing today.
r-cran-seurat had not passed waiting time.

> > r-cran-rstan/r-cran-rstanarm on 2023-10-27 which have not yet
> > migrated.

I've asked ftpmaster for removal (see bug #1056913) of some architecture
builds for r-cran-rstan which is preventing the migration of this
package.

There is another issue for r-cran-rstan which affects a regression
for r-cran-projpred for ppc64el architecture[1] which boils down to:

 53s Unpacking pandoc (2.17.1.1-3) ...
 54s dpkg-deb: error:  subprocess was killed by signal (Killed)
 54s dpkg: error processing archive 
/tmp/apt-dpkg-install-geka0F/120-pandoc_2.17.1.1-3_ppc64el.deb (--unpack):
 54s  cannot copy extracted data for './usr/bin/pandoc' to 
'/usr/bin/pandoc.dpkg-new': unexpected end of file or stream
 ...
 71s Errors were encountered while processing:
 71s  /tmp/apt-dpkg-install-geka0F/120-pandoc_2.17.1.1-3_ppc64el.deb
 72s E: Sub-process /usr/bin/dpkg returned an error code (1)

It seems something on this architecture is broken I can't do anything
about.  Could you provide help here?

Kind regards
 Andreas.

[1] 
https://ci.debian.net/data/autopkgtest/testing/ppc64el/r/r-cran-projpred/40151666/log.gz

-- 
http://fam-tille.de



Bug#1056581: confirmed


Thanks for filing this! The problem affects me, too.

Found this report and fixed printers.conf manually by deleting the line


Option print-color-mode monochrome


from it. Hope this gets fixed soon.



Bug#1056913: RM: r-cran-rstan [armel m68k mips64el x32 hurd-i386 powerpc] -- ROM; Build-Depends missing on some architectures

Package: ftp.debian.org
Severity: normal
User: ftp.debian@packages.debian.org
Usertags: remove
X-Debbugs-Cc: r-cran-rs...@packages.debian.org, 1054...@bugs.debian.org
Control: affects -1 + src:r-cran-rstan

Hi ftpmasters,

currently the testing migration of r-cran-rstan is a blocker to start
the the Bioconductor transition.  As far as I can see r-cran-rstan is
not building on some architectures due to the lack of Build-Depends.
This lack exists on architectures that are not relevant in practical use
cases.  That's why it would help if the package will be removed from
those architectures to enable testing migration.  Once all Build-Depends
might be available the issue will be cured (or not and than should that
package not exist on those architectures.

Kind regards and thanks for your work as ftpmaster
Andreas.



Bug#1056557: libcuda1:amd64 seems cause graphic dead on testing

On Sat, 25 Nov 2023 10:48:44 +0100 Andreas Beckmann  wrote:
> On 23/11/2023 03.00, fl...@outlook.com wrote:
> > Package: libcuda1:amd64
> > Version: 525.125.06-3
> > 
> > When I try to perform a system upgrade, my Debian testing's graphic seems
> > dead. The display lost connection to my Nvidia GPU, the system are still
> > running so I can type on keyboard but the system didn't reply. Force 
shutdown
> > and reboot doesn't helps, it cant boot. Thankfully I have timeshift 
snapshot
> > backuped, so I booted into live-cd ,copied the log, and restored snapshot.
> 
> I believe that was related to the newly introduced nvidia-suspend-common 
> package and the new suspend/hibernate/resume related services getting 
> activated (all three at the same time) during installation/upgrade.
> 
> This should be solved with nvidia-suspend-common 525.147.05-3 in sid.
> 
> Andreas
> 
> 
=
 

It works! The problem was solved. Thank you so much!



Bug#1056574: transition: ppp

Hi,
And maybe then reversing this in openfortivpn package:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1056235#27


Thanks!



Bug#1056784: ITP: bankstown -- barebones, fast LV2 bass enhancement plugin

On Sun, Nov 26, 2023 at 04:18:33PM +0100, Andreas Henriksson wrote:
> Hello Jonas,
> 
[...]
> I've now renamed the *binary* package to bankstown-lv2,
[...] 

Oh well, I'm renaming the source as well. I guess we can always
rename our git repo to match and pretent like everything is
bankstown-lv2.

Just for comparison, I downloaded all sources for binary packages called
'*-lv2' and 5 of 15 had -lv2 suffix in the orig tarball name (so 1/3).

Regards,
Andreas Henriksson



Bug#1055290: libevent: Fix libc-dev build-dep


Hello,

Thanks for the patch!

However, I'm wondering if the fix is required when the package will be 
re-uploaded to unstable, because the Build-Depends to libc6-dev was 
added to check the build against glibc 2.38 (#1043108)


When glibc 2.38 will be uploded to unstable, I expect do the same for 
libevent, without the builddep to libc6-dev.


Is that ok with you?

/Nicolas



Bug#1056912: initramfs-tools: update-initramfs - can't generate initramfs

Package: initramfs-tools
Version: 0.142
Severity: normal
X-Debbugs-Cc: stigma...@gmail.com

Dear Maintainer,

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

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

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

When i try to regenerate file initramfs by command sudo update-initramfs -u it
shows long output like in post bellow:
update-initramfs: Generating /boot/initrd.img-6.5.0-4-amd64
(nie zastępuje it means: does not replace)
cp: nie zastępuje '/var/tmp/mkinitramfs_4rdF3V/bin/cat'
cp: nie zastępuje '/var/tmp/mkinitramfs_4rdF3V/bin/cpio'
cp: nie zastępuje '/var/tmp/mkinitramfs_4rdF3V/bin/dd'
cp: nie zastępuje '/var/tmp/mkinitramfs_4rdF3V/bin/dmesg'
cp: nie zastępuje '/var/tmp/mkinitramfs_4rdF3V/bin/false'
cp: nie zastępuje '/var/tmp/mkinitramfs_4rdF3V/bin/gunzip'
cp: nie zastępuje '/var/tmp/mkinitramfs_4rdF3V/bin/kill'
cp: nie zastępuje '/var/tmp/mkinitramfs_4rdF3V/bin/ln'
cp: nie zastępuje '/var/tmp/mkinitramfs_4rdF3V/bin/ls'
cp: nie zastępuje '/var/tmp/mkinitramfs_4rdF3V/bin/mkdir'
cp: nie zastępuje '/var/tmp/mkinitramfs_4rdF3V/bin/mkfifo'
cp: nie zastępuje '/var/tmp/mkinitramfs_4rdF3V/bin/mknod'
cp: nie zastępuje '/var/tmp/mkinitramfs_4rdF3V/bin/mount'
cp: nie zastępuje '/var/tmp/mkinitramfs_4rdF3V/bin/mv'
cp: nie zastępuje '/var/tmp/mkinitramfs_4rdF3V/bin/nuke'
cp: nie zastępuje '/var/tmp/mkinitramfs_4rdF3V/bin/readlink'
cp: nie zastępuje '/var/tmp/mkinitramfs_4rdF3V/bin/resume'
cp: nie zastępuje '/var/tmp/mkinitramfs_4rdF3V/bin/sh'
cp: nie zastępuje '/var/tmp/mkinitramfs_4rdF3V/bin/sleep'
cp: nie zastępuje '/var/tmp/mkinitramfs_4rdF3V/bin/sync'
cp: nie zastępuje '/var/tmp/mkinitramfs_4rdF3V/bin/true'
cp: nie zastępuje '/var/tmp/mkinitramfs_4rdF3V/bin/umount'
cp: nie zastępuje '/var/tmp/mkinitramfs_4rdF3V/bin/uname'

I dont have seperate partitions for /var/tmp or /boot. Everything is in one
partition except /boot/efi (512mb). Main drive has 1tb and there is still 580gb
of free storage. I tried to remove /var/tmp/* and regenerate file but still i
have the same output. Any solution? how to fix this? im open to fix this and
send more information which i can forget


-- Package-specific info:
-- initramfs sizes
-rw-r--r-- 1 root root 81M Nov 26 02:57 /boot/initrd.img-6.5.0-4-amd64
-- /proc/cmdline
BOOT_IMAGE=/@rootfs/boot/vmlinuz-6.5.0-4-amd64 
root=UUID=e70c45f2-2d63-4890-afa2-c5a756a2c861 ro rootflags=subvol=@rootfs 
nvidia-drm.modeset=1 quiet

-- resume
RESUME=none
-- /proc/filesystems
btrfs
fuseblk
vfat

-- lsmod
Module  Size  Used by
uhid   16384  1
ccm20480  6
nvidia_modeset   1478656  1
rfcomm102400  4
cmac   12288  3
algif_hash 12288  1
algif_skcipher 12288  1
af_alg 36864  6 algif_hash,algif_skcipher
snd_seq_dummy  12288  0
snd_hrtimer12288  1
snd_seq   114688  7 snd_seq_dummy
snd_seq_device 16384  1 snd_seq
nvidia  62263296  42 nvidia_modeset
nft_fib_inet   12288  1
nft_fib_ipv4   12288  1 nft_fib_inet
nft_fib_ipv6   12288  1 nft_fib_inet
nft_fib12288  3 nft_fib_ipv6,nft_fib_ipv4,nft_fib_inet
nft_reject_inet12288  10
nf_reject_ipv4 16384  1 nft_reject_inet
nf_reject_ipv6 24576  1 nft_reject_inet
nft_reject 12288  1 nft_reject_inet
nft_ct 28672  7
nft_chain_nat  12288  3
nf_nat 65536  1 nft_chain_nat
nf_conntrack  212992  2 nf_nat,nft_ct
nf_defrag_ipv6 24576  1 nf_conntrack
nf_defrag_ipv4 12288  1 nf_conntrack
ip_set 65536  0
nf_tables 372736  253 
nft_ct,nft_reject_inet,nft_fib_ipv6,nft_fib_ipv4,nft_chain_nat,nft_reject,nft_fib,nft_fib_inet
bnep   36864  2
qrtr   57344  4
zstd   12288  8
zram   40960  2
zsmalloc   36864  1 zram
bbswitch   16384  0
x86_pkg_temp_thermal16384  0
intel_powerclamp   16384  0
coretemp   16384  0
iwlmvm589824  0
kvm_intel 413696  0
btusb  81920  0
btrtl  28672  1 btusb
btbcm  24576  1 btusb
btintel57344  1 btusb
snd_sof_pci_intel_tgl12288  0
btmtk  12288  1 btusb
kvm  1359872  1 kvm_intel
bluetooth1126400  36 btrtl,btmtk,btintel,btbcm,bnep,btusb,rfcomm
snd_sof_intel_hda_common   204800  1 snd_sof_pci_intel_tgl
mac80211 1392640  1 iwlmvm
soundwire_intel61440  1 snd_sof_intel_hda_common
soundwire_generic_allocation12288  1 soundwire_intel
snd_sof_intel_hda_mlink40960  2 

  1   2   >