Bug#1064809: libhipsparse0-tests: csr2bsr test failures

[Christian Kastner]

On 2024-02-26 07:23, Cordell Bloor wrote:
> The update of rocsparse 5.5.1 to 5.7.1 seems to have caused a regression
> in hipsparse. Although, it's also possible that this problem was because
> rocsparse was therefore rebuilt with the updated rocprim 5.7.1.

Interestingly, this passed on gfx900 [1].

(I checked a small sample of tests to check that they weren't just
being skipped)

[1]: https://ci.rocm.debian.net/packages/h/hipsparse/unstable/amd64+gfx900/

Bug#1062822: omnievents: NMU diff for 64-bit time_t transition

[Steve Langasek]

The previous patch overlooked some necessary changes in debian/rules that
resulted in file mismatches.  Please find attached a corrected patch.

-- 
Steve Langasek   Give me a lever long enough and a Free OS
Debian Developer   to set it on, and I can move the world.
Ubuntu Developer   https://www.debian.org/
slanga...@ubuntu.com vor...@debian.org
diff -Nru omnievents-2.6.2/debian/changelog omnievents-2.6.2/debian/changelog
--- omnievents-2.6.2/debian/changelog   2022-11-17 11:01:16.0 +
+++ omnievents-2.6.2/debian/changelog   2024-02-26 07:18:08.0 +
@@ -1,3 +1,16 @@
+omnievents (1:2.6.2-6.1~exp2) experimental; urgency=medium
+
+  * Fix package name references in debian/rules
+
+ -- Steve Langasek   Mon, 26 Feb 2024 07:18:08 +
+
+omnievents (1:2.6.2-6.1~exp1) experimental; urgency=medium
+
+  * Non-maintainer upload.
+  * Rename libraries for 64-bit time_t transition.
+
+ -- Lucas Kanashiro   Sat, 03 Feb 2024 14:44:06 -0300
+
 omnievents (1:2.6.2-6) unstable; urgency=medium
 
   * QA upload.
diff -Nru omnievents-2.6.2/debian/control omnievents-2.6.2/debian/control
--- omnievents-2.6.2/debian/control 2022-11-17 11:01:16.0 +
+++ omnievents-2.6.2/debian/control 2024-02-03 17:44:05.0 +
@@ -36,7 +36,10 @@
  This package contains the CORBA Event Service daemon as a standalone
  executable, and the associated tools.
 
-Package: libomnievents2
+Package: libomnievents2t64
+Provides: ${t64:Provides}
+Replaces: libomnievents2
+Breaks: libomnievents2 (<< ${source:Version})
 Architecture: any
 Section: libs
 Depends: ${misc:Depends},
@@ -49,7 +52,7 @@
 Package: libomnievents-dev
 Architecture: any
 Section: libdevel
-Depends: libomnievents2 (= ${binary:Version}),
+Depends: libomnievents2t64 (= ${binary:Version}),
  ${misc:Depends}
 Recommends: pkg-config
 Suggests: omnievents-doc
diff -Nru omnievents-2.6.2/debian/libomnievents2.install 
omnievents-2.6.2/debian/libomnievents2.install
--- omnievents-2.6.2/debian/libomnievents2.install  2022-11-17 
11:01:16.0 +
+++ omnievents-2.6.2/debian/libomnievents2.install  1970-01-01 
00:00:00.0 +
@@ -1 +0,0 @@
-debian/tmp/usr/lib/*.so.*
diff -Nru omnievents-2.6.2/debian/libomnievents2t64.install 
omnievents-2.6.2/debian/libomnievents2t64.install
--- omnievents-2.6.2/debian/libomnievents2t64.install   1970-01-01 
00:00:00.0 +
+++ omnievents-2.6.2/debian/libomnievents2t64.install   2024-02-03 
17:44:05.0 +
@@ -0,0 +1 @@
+debian/tmp/usr/lib/*.so.*
diff -Nru omnievents-2.6.2/debian/libomnievents2t64.lintian-overrides 
omnievents-2.6.2/debian/libomnievents2t64.lintian-overrides
--- omnievents-2.6.2/debian/libomnievents2t64.lintian-overrides 1970-01-01 
00:00:00.0 +
+++ omnievents-2.6.2/debian/libomnievents2t64.lintian-overrides 2024-02-03 
17:44:05.0 +
@@ -0,0 +1 @@
+libomnievents2t64: package-name-doesnt-match-sonames libomnievents2
diff -Nru omnievents-2.6.2/debian/rules omnievents-2.6.2/debian/rules
--- omnievents-2.6.2/debian/rules   2022-11-17 11:01:16.0 +
+++ omnievents-2.6.2/debian/rules   2024-02-26 07:18:05.0 +
@@ -29,8 +29,8 @@
 binary-post-install/omnievents::
cp -f src/oelite $(CURDIR)/debian/omnievents/usr/sbin/omniEvents
 
-binary-post-install/libomnievents2::
-   cd $(CURDIR)/debian/libomnievents2/usr/lib/ && \
+binary-post-install/libomnievents2t64::
+   cd $(CURDIR)/debian/libomnievents2t64/usr/lib/ && \
rm -f libomniEvents.so.2.6 && \
ln -sf libomniEvents.so.2.6.2 libomniEvents.so.2
 


signature.asc
Description: PGP signature

Bug#1064160: pngcrush FTBFS with libpng 1.6.42

[Andreas Tille]

Control: tags -1 patch
Control: tags -1 pending

Hi Marga,

I've pushed the patch used in ArchLinux to Git[1].  I could do another
NMU but I would prefer to move the package to Debian Phototools team
and I'd volunteer to do that move.

Kind regards
Andreas.


[1] 
https://salsa.debian.org/debian/pngcrush/-/blob/master/debian/patches/ignore_PNG_IGNORE_ADLER32.patch?ref_type=heads

-- 
http://fam-tille.de

Bug#1062464: ivtools: NMU diff for 64-bit time_t transition

[Steve Langasek]

The previous patch overlooked some necessary changes in debian/rules that
resulted in missing libraries.  Please find attached a corrected patch.

-- 
Steve Langasek   Give me a lever long enough and a Free OS
Debian Developer   to set it on, and I can move the world.
Ubuntu Developer   https://www.debian.org/
slanga...@ubuntu.com vor...@debian.org
diff -Nru ivtools-2.0.11d.a1/debian/changelog 
ivtools-2.0.11d.a1/debian/changelog
--- ivtools-2.0.11d.a1/debian/changelog 2022-01-06 22:06:00.0 +
+++ ivtools-2.0.11d.a1/debian/changelog 2024-02-26 07:04:24.0 +
@@ -1,3 +1,17 @@
+ivtools (2.0.11d.a1-1.1~exp2) experimental; urgency=medium
+
+  * Non-maintainer upload.
+  * Fix package name references in debian/rules
+
+ -- Steve Langasek   Mon, 26 Feb 2024 07:04:24 +
+
+ivtools (2.0.11d.a1-1.1~exp1) experimental; urgency=medium
+
+  * Non-maintainer upload.
+  * Rename libraries for 64-bit time_t transition.
+
+ -- Graham Inggs   Thu, 01 Feb 2024 16:00:24 +
+
 ivtools (2.0.11d.a1-1) unstable; urgency=medium
 
   * new upstream release
diff -Nru ivtools-2.0.11d.a1/debian/control ivtools-2.0.11d.a1/debian/control
--- ivtools-2.0.11d.a1/debian/control   2022-01-06 10:41:49.0 +
+++ ivtools-2.0.11d.a1/debian/control   2024-02-01 16:00:24.0 +
@@ -34,8 +34,8 @@
 Package: ivtools-dev
 Section: devel
 Architecture: any
-Depends: libiv2 (= ${binary:Version}),
-libiv-unidraw2 (= ${binary:Version}),
+Depends: libiv2t64 (= ${binary:Version}),
+libiv-unidraw2t64 (= ${binary:Version}),
 libc6-dev, libtiff-dev, zlib1g-dev, libace-dev,
 ${shlibs:Depends}, ${misc:Depends}
 Description: Development files for the InterViews library
@@ -47,7 +47,10 @@
  applications with the ivtools library, along with appropriate dynamic
  library links and static libraries.
 
-Package: libiv2
+Package: libiv2t64
+Provides: ${t64:Provides}
+Replaces: libiv2
+Breaks: libiv2 (<< ${source:Version})
 Architecture: any
 Multi-Arch: same
 Pre-Depends: ${misc:Pre-Depends}
@@ -59,7 +62,10 @@
  provide a special "Look and Feel", such as SGI-Motif and normal Motif.
  This package contains the InterViews dynamic library.
 
-Package: libiv-unidraw2
+Package: libiv-unidraw2t64
+Provides: ${t64:Provides}
+Replaces: libiv-unidraw2
+Breaks: libiv-unidraw2 (<< ${source:Version})
 Architecture: any
 Multi-Arch: same
 Pre-Depends: ${misc:Pre-Depends}
diff -Nru ivtools-2.0.11d.a1/debian/libiv-unidraw2.install 
ivtools-2.0.11d.a1/debian/libiv-unidraw2.install
--- ivtools-2.0.11d.a1/debian/libiv-unidraw2.install2022-01-06 
10:37:22.0 +
+++ ivtools-2.0.11d.a1/debian/libiv-unidraw2.install1970-01-01 
00:00:00.0 +
@@ -1 +0,0 @@
-usr/lib/*/lib*.so.*
diff -Nru ivtools-2.0.11d.a1/debian/libiv-unidraw2t64.install 
ivtools-2.0.11d.a1/debian/libiv-unidraw2t64.install
--- ivtools-2.0.11d.a1/debian/libiv-unidraw2t64.install 1970-01-01 
00:00:00.0 +
+++ ivtools-2.0.11d.a1/debian/libiv-unidraw2t64.install 2024-02-01 
16:00:24.0 +
@@ -0,0 +1 @@
+usr/lib/*/lib*.so.*
diff -Nru ivtools-2.0.11d.a1/debian/libiv-unidraw2t64.lintian-overrides 
ivtools-2.0.11d.a1/debian/libiv-unidraw2t64.lintian-overrides
--- ivtools-2.0.11d.a1/debian/libiv-unidraw2t64.lintian-overrides   
1970-01-01 00:00:00.0 +
+++ ivtools-2.0.11d.a1/debian/libiv-unidraw2t64.lintian-overrides   
2024-02-01 16:00:24.0 +
@@ -0,0 +1 @@
+libiv-unidraw2t64: package-name-doesnt-match-sonames libiv-unidraw2
diff -Nru ivtools-2.0.11d.a1/debian/libiv2.install 
ivtools-2.0.11d.a1/debian/libiv2.install
--- ivtools-2.0.11d.a1/debian/libiv2.install2022-01-06 10:37:22.0 
+
+++ ivtools-2.0.11d.a1/debian/libiv2.install1970-01-01 00:00:00.0 
+
@@ -1 +0,0 @@
-usr/lib/*/libIV.so.*
diff -Nru ivtools-2.0.11d.a1/debian/libiv2t64.install 
ivtools-2.0.11d.a1/debian/libiv2t64.install
--- ivtools-2.0.11d.a1/debian/libiv2t64.install 1970-01-01 00:00:00.0 
+
+++ ivtools-2.0.11d.a1/debian/libiv2t64.install 2024-02-01 16:00:24.0 
+
@@ -0,0 +1 @@
+usr/lib/*/libIV.so.*
diff -Nru ivtools-2.0.11d.a1/debian/libiv2t64.lintian-overrides 
ivtools-2.0.11d.a1/debian/libiv2t64.lintian-overrides
--- ivtools-2.0.11d.a1/debian/libiv2t64.lintian-overrides   1970-01-01 
00:00:00.0 +
+++ ivtools-2.0.11d.a1/debian/libiv2t64.lintian-overrides   2024-02-01 
16:00:24.0 +
@@ -0,0 +1 @@
+libiv2t64: package-name-doesnt-match-sonames libiv2
diff -Nru ivtools-2.0.11d.a1/debian/rules ivtools-2.0.11d.a1/debian/rules
--- ivtools-2.0.11d.a1/debian/rules 2022-01-06 10:37:22.0 +
+++ ivtools-2.0.11d.a1/debian/rules 2024-02-26 07:04:00.0 +
@@ -16,8 +16,8 @@
 
 execute_after_dh_install:
@echo prevent library files in libiv2 from being duplicated in 
libiv-unidraw2
-   find 

Bug#1064734: libhx/hxtools: FTBFS: ./smath/./smath/graph-fanout.c:263:(.text.startup+0x139): undefined reference to `BUILD_BUG_ON_EXPR'

[Jochen Sprickerhof]

Control: reassign -1 src:libhx 4.19-1
Control: retitle -1 Please include upstream patch
Control: affects -1 src:hxtools

Hi Jörg,

can you please upload a new libhx either containing this upstream patch 
or the new upstream release to unbreak hxtools?


https://codeberg.org/jengelh/libhx/commit/e55e06348d1e5b531c8bffe435bddc31e2010ab1

Thanks!

Jochen

* Lucas Nussbaum  [2024-02-25 20:27]:

Source: hxtools
Version: 20231224-2
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20240224 ftbfs-trixie

Hi,

During a rebuild of all packages in sid, your package failed to build
on amd64.


Relevant part (hopefully):

/usr/bin/ld: graph-fanout.o: in function `fanout_get_options':
./smath/./smath/graph-fanout.c:263:(.text.startup+0x139): undefined reference 
to `BUILD_BUG_ON_EXPR'
collect2: error: ld returned 1 exit status



The full build log is available from:
http://qa-logs.debian.net/2024/02/24/hxtools_20231224-2_unstable.log

All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20240224;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20240224=lu...@debian.org=1=1=1=1#results

A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!

If you reassign this bug to another package, please mark it as 'affects'-ing
this package. See https://www.debian.org/Bugs/server-control#affects

If you fail to reproduce this, please provide a build log and diff it with mine
so that we can identify if something relevant changed in the meantime.



signature.asc
Description: PGP signature

Bug#1061208: Please upgrade to llvm-toolchain-17

[Christian Kastner]

Hi Sebastian,

writing to you as you bumped the severity to 'serious': could the rT
please give us an extension on the autoremoval for this particular bug.

The transition from first-filing-to-serious was unusually short notice,
and caught us in the middle of our own update of the stack.

This affects a key package of our stack, so it's not just about testing
this particular package, but the entire stack, and everything else in
the archive that depends on it.

A fix is in progress.

Best,
Christian

On 2024-01-20 21:59, Sylvestre Ledru wrote:
> Source: rocm-hipamd
> Severity: important
> 
> Dear Maintainer,
> 
> As part of the effort to limit the number of llvm packages in the
> archive, it would be great if you could upgrade to -17.
> 
> This package depends on 15.

Bug#1062674: lua-compat53: NMU diff for 64-bit time_t transition

[Steve Langasek]

Control: tags -1 - pending

Seeing that '53' is not an soname, I don't think we should NMU this to
unstable.  Untagging.

-- 
Steve Langasek   Give me a lever long enough and a Free OS
Debian Developer   to set it on, and I can move the world.
Ubuntu Developer   https://www.debian.org/
slanga...@ubuntu.com vor...@debian.org


signature.asc
Description: PGP signature

Bug#1064629: libamd-comgr2: segfault in rocfft,version graph

[Cordell Bloor]

The segfault on the very first rocfft test (and in no other library) is 
probably a good indication that HIP runtime compilation (RTC) is broken. 
That is a feature that is used for every rocFFT function, but not used 
by any other ROCm library.


Whether this bug is because the HIP stack is currently built on a mix of 
clang-15 and clang-17, or if this bug is inherent to the clang-17 
version of comgr is an open question. My priority at the moment is to 
complete the move to clang-17 so we can at least eliminate the clang-15 
variable and re-stabilize the ROCm stack on clang-17.

Bug#1064810: transition: mpi-defaults

[Alastair McKinstry]

Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: transition
X-Debbugs-Cc: mpi-defau...@packages.debian.org, debian-scie...@lists.debian.org
Control: affects -1 + src:mpi-defaults

OpenMPI 5.0 drops 32-bit support, so we need to move those archs to MPICH.

notes = "https://lists.debian.org/debian-release/2023/11/msg00379.html;;

Ben file:

title = "mpi-defaults";
is_affected = .build-depends ~ /mpi-default-dev/;
is_good = .depends ~ /libmpich.*/;
is_bad = .depends ~ /libopenmpi.*/;
architectures = [ "armhf","armel","i386" ];
ignored = [ ];

Bug#1064785: brltty: installs same filename to both bin and sbin

[Paul Gevers]

Hi Cacin,

On 25-02-2024 10:47 p.m., ca...@allfreemail.net wrote:

your package installs the filename brltty to both bin and sbin as opposed to 
just one of those locations.


I haven't checked yet, but are these two versions of file:brltty 
actually the same?



This causes a problem on a filesystem layout where bin and sbin are merged into 
a single real directory, typically by sbin being a symlink to bin. Such a 
filesystem layout has become standard on some distributions now, and others are 
moving onto in their next releases.


Sure. But in Debian we're not there yet. And given the merged-/usr mess 
[1], we'll might not adventure there soon. And hopefully not with a symlink.



Please pick one location and install it only there. /usr/bin is preferred over 
any other location.


Suggesting a move from /bin to /usr/bin is not without danger, exactly 
because of the very similar merged-/usr transition that's currently 
being clean-up. There's the danger that files get lost upon upgrade (P1 
in [1]) if this is done incorrectly.


Paul

[1] https://subdivi.de/~helmut/dep17.html


OpenPGP_signature.asc
Description: OpenPGP digital signature

Bug#1064809: libhipsparse0-tests: csr2bsr test failures

[Cordell Bloor]

Package: libhipsparse0-tests
Version: 5.5.1-1
Severity: normal
X-Debbugs-Cc: c...@slerp.xyz

Dear Maintainer,

The update of rocsparse 5.5.1 to 5.7.1 seems to have caused a regression
in hipsparse. Although, it's also possible that this problem was because
rocsparse was therefore rebuilt with the updated rocprim 5.7.1.

The failing tests are:

[  FAILED  ] 128 tests, listed below:
[  FAILED  ] csr2bsr/parameterized_csr2bsr.csr2bsr_float/86, where GetParam() = 
(0, 0, 0, 0, 1, 0)
[  FAILED  ] csr2bsr/parameterized_csr2bsr.csr2bsr_float/87, where GetParam() = 
(0, 0, 0, 0, 1, 1)
[  FAILED  ] csr2bsr/parameterized_csr2bsr.csr2bsr_float/100, where GetParam() 
= (0, 623, 0, 0, 1, 0)
[  FAILED  ] csr2bsr/parameterized_csr2bsr.csr2bsr_float/101, where GetParam() 
= (0, 623, 0, 0, 1, 1)
[  FAILED  ] csr2bsr/parameterized_csr2bsr.csr2bsr_float/114, where GetParam() 
= (0, 12766, 0, 0, 1, 0)
[  FAILED  ] csr2bsr/parameterized_csr2bsr.csr2bsr_float/115, where GetParam() 
= (0, 12766, 0, 0, 1, 1)
[  FAILED  ] csr2bsr/parameterized_csr2bsr.csr2bsr_float/128, where GetParam() 
= (0, 29285, 0, 0, 1, 0)
[  FAILED  ] csr2bsr/parameterized_csr2bsr.csr2bsr_float/129, where GetParam() 
= (0, 29285, 0, 0, 1, 1)
[  FAILED  ] csr2bsr/parameterized_csr2bsr.csr2bsr_float/156, where GetParam() 
= (872, 0, 0, 0, 1, 0)
[  FAILED  ] csr2bsr/parameterized_csr2bsr.csr2bsr_float/157, where GetParam() 
= (872, 0, 0, 0, 1, 1)
[  FAILED  ] csr2bsr/parameterized_csr2bsr.csr2bsr_float/170, where GetParam() 
= (872, 623, 0, 0, 1, 0)
[  FAILED  ] csr2bsr/parameterized_csr2bsr.csr2bsr_float/171, where GetParam() 
= (872, 623, 0, 0, 1, 1)
[  FAILED  ] csr2bsr/parameterized_csr2bsr.csr2bsr_float/184, where GetParam() 
= (872, 12766, 0, 0, 1, 0)
[  FAILED  ] csr2bsr/parameterized_csr2bsr.csr2bsr_float/185, where GetParam() 
= (872, 12766, 0, 0, 1, 1)
[  FAILED  ] csr2bsr/parameterized_csr2bsr.csr2bsr_float/198, where GetParam() 
= (872, 29285, 0, 0, 1, 0)
[  FAILED  ] csr2bsr/parameterized_csr2bsr.csr2bsr_float/199, where GetParam() 
= (872, 29285, 0, 0, 1, 1)
[  FAILED  ] csr2bsr/parameterized_csr2bsr.csr2bsr_float/226, where GetParam() 
= (13095, 0, 0, 0, 1, 0)
[  FAILED  ] csr2bsr/parameterized_csr2bsr.csr2bsr_float/227, where GetParam() 
= (13095, 0, 0, 0, 1, 1)
[  FAILED  ] csr2bsr/parameterized_csr2bsr.csr2bsr_float/240, where GetParam() 
= (13095, 623, 0, 0, 1, 0)
[  FAILED  ] csr2bsr/parameterized_csr2bsr.csr2bsr_float/241, where GetParam() 
= (13095, 623, 0, 0, 1, 1)
[  FAILED  ] csr2bsr/parameterized_csr2bsr.csr2bsr_float/254, where GetParam() 
= (13095, 12766, 0, 0, 1, 0)
[  FAILED  ] csr2bsr/parameterized_csr2bsr.csr2bsr_float/255, where GetParam() 
= (13095, 12766, 0, 0, 1, 1)
[  FAILED  ] csr2bsr/parameterized_csr2bsr.csr2bsr_float/268, where GetParam() 
= (13095, 29285, 0, 0, 1, 0)
[  FAILED  ] csr2bsr/parameterized_csr2bsr.csr2bsr_float/269, where GetParam() 
= (13095, 29285, 0, 0, 1, 1)
[  FAILED  ] csr2bsr/parameterized_csr2bsr.csr2bsr_float/296, where GetParam() 
= (21453, 0, 0, 0, 1, 0)
[  FAILED  ] csr2bsr/parameterized_csr2bsr.csr2bsr_float/297, where GetParam() 
= (21453, 0, 0, 0, 1, 1)
[  FAILED  ] csr2bsr/parameterized_csr2bsr.csr2bsr_float/310, where GetParam() 
= (21453, 623, 0, 0, 1, 0)
[  FAILED  ] csr2bsr/parameterized_csr2bsr.csr2bsr_float/311, where GetParam() 
= (21453, 623, 0, 0, 1, 1)
[  FAILED  ] csr2bsr/parameterized_csr2bsr.csr2bsr_float/324, where GetParam() 
= (21453, 12766, 0, 0, 1, 0)
[  FAILED  ] csr2bsr/parameterized_csr2bsr.csr2bsr_float/325, where GetParam() 
= (21453, 12766, 0, 0, 1, 1)
[  FAILED  ] csr2bsr/parameterized_csr2bsr.csr2bsr_float/338, where GetParam() 
= (21453, 29285, 0, 0, 1, 0)
[  FAILED  ] csr2bsr/parameterized_csr2bsr.csr2bsr_float/339, where GetParam() 
= (21453, 29285, 0, 0, 1, 1)
[  FAILED  ] csr2bsr/parameterized_csr2bsr.csr2bsr_double/86, where GetParam() 
= (0, 0, 0, 0, 1, 0)
[  FAILED  ] csr2bsr/parameterized_csr2bsr.csr2bsr_double/87, where GetParam() 
= (0, 0, 0, 0, 1, 1)
[  FAILED  ] csr2bsr/parameterized_csr2bsr.csr2bsr_double/100, where GetParam() 
= (0, 623, 0, 0, 1, 0)
[  FAILED  ] csr2bsr/parameterized_csr2bsr.csr2bsr_double/101, where GetParam() 
= (0, 623, 0, 0, 1, 1)
[  FAILED  ] csr2bsr/parameterized_csr2bsr.csr2bsr_double/114, where GetParam() 
= (0, 12766, 0, 0, 1, 0)
[  FAILED  ] csr2bsr/parameterized_csr2bsr.csr2bsr_double/115, where GetParam() 
= (0, 12766, 0, 0, 1, 1)
[  FAILED  ] csr2bsr/parameterized_csr2bsr.csr2bsr_double/128, where GetParam() 
= (0, 29285, 0, 0, 1, 0)
[  FAILED  ] csr2bsr/parameterized_csr2bsr.csr2bsr_double/129, where GetParam() 
= (0, 29285, 0, 0, 1, 1)
[  FAILED  ] csr2bsr/parameterized_csr2bsr.csr2bsr_double/156, where GetParam() 
= (872, 0, 0, 0, 1, 0)
[  FAILED  ] csr2bsr/parameterized_csr2bsr.csr2bsr_double/157, where GetParam() 
= (872, 0, 0, 0, 1, 1)
[  FAILED  ] csr2bsr/parameterized_csr2bsr.csr2bsr_double/170, where GetParam() 
= (872, 623, 0, 0, 1, 0)
[  FAILED  ] csr2bsr/parameterized_csr2bsr.csr2bsr_double/171, where 

Bug#1064807: [SOLVED] Just use default Debian MOK keys instead.

[RobotoSkunk Contact]

After trying and failing, I just gave up and reconfigured everything to 
use Debian's MOK keys instead, then purged and installed the 
nvidia-driver via APT again with Secure Boot enabled to make DKMS use 
the new MOK keys and it worked.


Sorry for the inconvenience.

Bug#1064807: [SOLVED] A small update

[RobotoSkunk]

I've replaced the user generated MOK keys and instead I just switched to 
Debian's default keys, then just purged and reinstalled nvidia-driver in 
order to make DKMS build the modules with the key and then it worked.

Bug#1064808: node-sanitize-html: CVE-2024-21501

[Salvatore Bonaccorso]

Source: node-sanitize-html
Version: 2.8.0+~2.6.2-1
Severity: important
Tags: security upstream
Forwarded: https://github.com/apostrophecms/sanitize-html/pull/650
X-Debbugs-Cc: car...@debian.org, Debian Security Team 

Hi,

The following vulnerability was published for node-sanitize-html.

CVE-2024-21501[0]:
| Versions of the package sanitize-html before 2.12.1 are vulnerable
| to Information Exposure when used on the backend and with the style
| attribute allowed, allowing enumeration of files in the system
| (including project dependencies). An attacker could exploit this
| vulnerability to gather details about the file system structure and
| dependencies of the targeted server.


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-2024-21501
https://www.cve.org/CVERecord?id=CVE-2024-21501
[1] https://github.com/apostrophecms/sanitize-html/pull/650
[2] 
https://github.com/apostrophecms/sanitize-html/commit/075499d1b98c387f4200fd59972ca9b15796b51b

Regards,
Salvatore

Bug#1061806: lamassemble fails its autopkg tests with Python 3.12

[Frith, Martin]

Hi Nilesh,

thank you for reporting this issue. I've just made an update to
lamassemble, which may solve it, but I'm not certain.

The output of lamassemble's tests changes when using MAFFT version >=
7.514. So I updated the test outputs to fit the latest MAFFT.

I hope that does it...
Martin


On Sat, Feb 24, 2024 at 10:42 PM Nilesh Patra  wrote:

> Hi Martin,
>
> doko:
> > Control: reopen -1
> >
> > please see the tests triggered by python3-defaults. Not pasting these
> > here in the bug report.
> >
> > https://autopkgtest.ubuntu.com/packages/l/lamassemble/noble/amd64
>
> Would you be able to assist with this bug report?
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1061806
>
> Here's the test script we use for lamassemble
>
> https://salsa.debian.org/med-team/lamassemble/-/blob/master/debian/tests/run-unit-test?ref_type=heads
>
> Best,
> Nilesh
>

Bug#1064806: python3.11: NMU diff for 64-bit time_t transition

[mwhudson]

Source: python3.11
Version: 3.11.8-1
Severity: important
Tags: patch pending sid trixie
User: debian-...@lists.debian.org
Usertags: time-t

NOTICE: these changes must not be uploaded to unstable yet!

Dear maintainer,

As part of the 64-bit time_t transition required to support 32-bit
architectures in 2038 and beyond
(https://wiki.debian.org/ReleaseGoals/64bit-time), we have identified
python3.11 as a source package shipping runtime libraries whose ABI
either is affected by the change in size of time_t, or could not be
analyzed via abi-compliance-checker (and therefore to be on the safe
side we assume is affected).

To ensure that inconsistent combinations of libraries with their
reverse-dependencies are never installed together, it is necessary to
have a library transition, which is most easily done by renaming the
runtime library package.

Since turning on 64-bit time_t is being handled centrally through a change
to the default dpkg-buildflags (https://bugs.debian.org/1037136), it is
important that libraries affected by this ABI change all be uploaded close
together in time.  Therefore I have prepared a 0-day NMU for python3.11
which will initially be uploaded to experimental if possible, then to
unstable after packages have cleared binary NEW.

Please find the patch for this NMU attached.

If you have any concerns about this patch, please reach out ASAP.  Although
this package will be uploaded to experimental immediately, there will be a
period of several days before we begin uploads to unstable; so if information
becomes available that your package should not be included in the transition,
there is time for us to amend the planned uploads.



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

Kernel: Linux 6.5.0-21-generic (SMP w/16 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
diff -Nru python3.11-3.11.8/debian/changelog python3.11-3.11.8/debian/changelog
--- python3.11-3.11.8/debian/changelog  2024-02-08 10:52:08.0 +1300
+++ python3.11-3.11.8/debian/changelog  2024-02-26 14:17:51.0 +1300
@@ -1,3 +1,10 @@
+python3.11 (3.11.8-1.1) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Rename libraries for 64-bit time_t transition.
+
+ -- Michael Hudson-Doyle   Mon, 26 Feb 2024 
14:17:51 +1300
+
 python3.11 (3.11.8-1) unstable; urgency=medium
 
   * New upstream release.
diff -Nru python3.11-3.11.8/debian/control python3.11-3.11.8/debian/control
--- python3.11-3.11.8/debian/control2023-12-09 08:27:08.0 +1300
+++ python3.11-3.11.8/debian/control2024-02-26 14:14:52.0 +1300
@@ -116,7 +116,10 @@
  This package contains some essential modules. It is normally not
  used on it's own, but as a dependency of python3.11-minimal.
 
-Package: libpython3.11
+Package: libpython3.11t64
+Provides: ${t64:Provides}
+Replaces: libpython3.11
+Breaks: libpython3.11 (<< ${source:Version})
 Architecture: any
 Multi-Arch: same
 Section: libs
@@ -234,14 +237,15 @@
  .
  See the README.debug for more information.
 
-Package: libpython3.11-dbg
+Package: libpython3.11t64-dbg
+Provides: ${t64:Provides}
 Section: debug
 Architecture: any
 Multi-Arch: same
 Pre-Depends: ${misc:Pre-Depends}
 Depends: libpython3.11-stdlib (= ${binary:Version}), ${shlibs:Depends}, 
${misc:Depends}
-Breaks: python3-gdbm-dbg (<< 3.9.9-1~)
-Replaces: python3-gdbm-dbg (<< 3.9.9-1~)
+Breaks: libpython3.11-dbg (<< ${source:Version}), python3-gdbm-dbg (<< 
3.9.9-1~)
+Replaces: libpython3.11-dbg, python3-gdbm-dbg (<< 3.9.9-1~)
 Description: Debug Build of the Python Interpreter (version 3.11)
  The package holds two things:
  .
diff -Nru python3.11-3.11.8/debian/control.in 
python3.11-3.11.8/debian/control.in
--- python3.11-3.11.8/debian/control.in 2023-12-09 08:25:58.0 +1300
+++ python3.11-3.11.8/debian/control.in 2024-02-26 14:13:44.0 +1300
@@ -116,7 +116,10 @@
  This package contains some essential modules. It is normally not
  used on it's own, but as a dependency of @PVER@-minimal.
 
-Package: lib@PVER@
+Package: lib@PVER@t64
+Provides: ${t64:Provides}
+Replaces: lib@PVER@
+Breaks: lib@PVER@ (<< ${source:Version})
 Architecture: any
 Multi-Arch: same
 Section: libs
@@ -234,14 +237,15 @@
  .
  See the README.debug for more information.
 
-Package: lib@PVER@-dbg
+Package: lib@PVER@t64-dbg
+Provides: ${t64:Provides}
 Section: debug
 Architecture: any
 Multi-Arch: same
 Pre-Depends: ${misc:Pre-Depends}
 Depends: lib@PVER@-stdlib (= ${binary:Version}), ${shlibs:Depends}, 
${misc:Depends}
-Breaks: python3-gdbm-dbg (<< 3.9.9-1~)
-Replaces: python3-gdbm-dbg (<< 3.9.9-1~)
+Breaks: lib@PVER@-dbg (<< ${source:Version}), python3-gdbm-dbg (<< 3.9.9-1~)
+Replaces: lib@PVER@-dbg, python3-gdbm-dbg (<< 3.9.9-1~)

Bug#1032449: sparse: support building sparse with LLVM 15

[Vladimir Petko]

Dear Maintainer,

 Would it be possible to consider upstream patch[1] for this issue?
 This would resolve[2] without disabling LLVM support.

Best Regards,
 Vladimir.

[1] 
https://git.kernel.org/pub/scm/devel/sparse/sparse.git/patch/?id=c991e5c68b48158410ebda9cd0ae0fde065faec7
[2] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1051864

Bug#1062456: ipset: NMU diff for 64-bit time_t transition

[Steve Langasek]

Control: reopen -1
Control: tags -1 + pending
Control: severity -1 serious

This was not meant to be uploaded to unstable yet.  The toolchain has not
been changed to turn on 64-bit time_t by default.  As a result, ipset now
has the new package names in unstable, but the old ABI.

The toolchain changes are expected to land by Wednesday, so a reupload of
ipset then with no source changes is sufficient to resolve the issue.  Or,
you can manually set DEB_BUILD_MAINT_OPTIONS=abi=+time64 now to make the ABI
of your library match the name.

-- 
Steve Langasek   Give me a lever long enough and a Free OS
Debian Developer   to set it on, and I can move the world.
Ubuntu Developer   https://www.debian.org/
slanga...@ubuntu.com vor...@debian.org


signature.asc
Description: PGP signature

Bug#1055067: isc-dhcp-client: network-manager 1.44.2-3 changed path to nm-dhcp-helper, apparmor need update

[Vincent Lefevre]

On 2024-02-26 00:22:01 +0100, Sven-Haegar Koch wrote:
> While installing your test package I lost wifi connection, but I think 
> that was not from your package but from updating network-manager from 
> unstable at the same time (did dist-upgrade), which always breaks my 
> network.

With the future stable upgrade, it would be very bad to lose the
network connection (not just wifi is concerned) during the upgrade.
I suppose that once the new isc-dhcp-client package is available,
network-manager should break the old versions (something like that...
I don't know whether this is sufficient).

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

Bug#1064339: marked as pending in qtscript

[宋鼎]

Thank you.

On Sun, 25 Feb 2024 20:52:43 + Dmitry Shachnev wrote:

> Control: tag -1 pending
>
> Hello,
>
> Bug #1064339 in qtscript reported by you has been fixed in the
> Git repository and is awaiting an upload. You can see the commit
> message below and you can check the diff of the fix at:
>
> 
https://salsa.debian.org/qt-kde-team/qt/qtscript/-/commit/c8bb0856492fa12796a5018eb48f792390da34a5

>
> 
> Add a patch to support loongarch64.
>
> Closes: #1064339.
> Thanks Ding Song!
> 
>
> (this message was generated automatically)
> --
> Greetings
>
> https://bugs.debian.org/1064339
>
>

Bug#1064575: python-pyswarms-doc: please make the build reproducible.

[James Addison]

Followup-For: Bug #1064575

On Mon, 26 Feb 2024 00:22:44 +, I wrote:
> On Sat, 24 Feb 2024 12:33:50 +, I wrote:
> > Part of the documentation rendering process - I have not determined exactly
> > what yet - adds an 'alt' attribute when it does not exist, and generates a
> > randomized hex string to use as the value of the attribute.  This causes the
> > resulting python-pyswarms-doc package to vary on each build.
>
> Part of the reason for this appears to be the nbsphinx component; when it
> encounters HTML  elements, it emits reStructuredText markdown containing
> an alt attribute if one was found on the element, and defines an rST
> substitution[1] named by a UUID4-generated value converted to hexadecimal.
>
> Next question: where is that substitution name used when the ':alt:' option
> is not found on the image directive?

The answer is that the alt attribute/option is created by docutils here:

  
https://sources.debian.org/src/python-docutils/0.20.1%2Bdfsg-3/docutils/parsers/rst/states.py/#L2689-L2690

...and that is only relevant when an existing alt attribute is _not_ found from
the node here:

  
https://sources.debian.org/src/python-docutils/0.20.1%2Bdfsg-3/docutils/writers/_html_base.py/#L1084


The reason I'd like to know this is to determine the feasibility of a fix that
would apply across multiple buildsites (not only python-pyswarms-doc).

A naive fix idea would be to modify nbsphinx to emit an empty-string alt option
in cases where no existing alt attribute was found on the HTML  element.

However: I'm not yet sure about the implicit contracts/conventions are between
these components (nbsphinx, docutils), so I may need to investigate/discuss
further.

Bug#1064786: jruby: mri-extra - flaky TestOpen3 pipe tests

[Vladimir Petko]

This failure is probably caused by [1]


[1] https://github.com/jruby/jruby/issues/8069

Bug#1063186: rpm: NMU diff for 64-bit time_t transition

[Steve Langasek]

Attached is an updated patch rebased against current unstable.

-- 
Steve Langasek   Give me a lever long enough and a Free OS
Debian Developer   to set it on, and I can move the world.
Ubuntu Developer   https://www.debian.org/
slanga...@ubuntu.com vor...@debian.org
diff -Nru rpm-4.18.2+dfsg/debian/changelog rpm-4.18.2+dfsg/debian/changelog
--- rpm-4.18.2+dfsg/debian/changelog2024-02-25 13:29:45.0 +
+++ rpm-4.18.2+dfsg/debian/changelog2024-02-26 00:41:38.0 +
@@ -1,3 +1,10 @@
+rpm (4.18.2+dfsg-2.1~exp1) experimental; urgency=medium
+
+  * Non-maintainer upload.
+  * Rename libraries for 64-bit time_t transition.
+
+ -- Steve Langasek   Mon, 26 Feb 2024 00:41:38 +
+
 rpm (4.18.2+dfsg-2) unstable; urgency=medium
 
   * Team upload.
diff -Nru rpm-4.18.2+dfsg/debian/control rpm-4.18.2+dfsg/debian/control
--- rpm-4.18.2+dfsg/debian/control  2024-02-25 13:12:25.0 +
+++ rpm-4.18.2+dfsg/debian/control  2024-02-26 00:40:33.0 +
@@ -104,12 +104,15 @@
  .
  This package contains localization of rpm and localized man pages.
 
-Package: librpm9
+Package: librpm9t64
+Provides: ${t64:Provides}
+Replaces: librpm9
+Breaks: librpm9 (<< ${source:Version})
 Architecture: any
 Section: libs
 Depends: ${shlibs:Depends},
  ${misc:Depends},
- librpmio9 (= ${binary:Version})
+ librpmio9t64 (= ${binary:Version})
 Recommends: rpm-common (= ${binary:Version})
 Description: RPM shared library
  The RPM Package Manager (RPM) is a command-line driven package
@@ -119,7 +122,10 @@
  This library allows programs to make use of an RPM database or RPM packages
  without going through the program rpm.
 
-Package: librpmio9
+Package: librpmio9t64
+Provides: ${t64:Provides}
+Replaces: librpmio9
+Breaks: librpmio9 (<< ${source:Version})
 Architecture: any
 Section: libs
 Depends: ${shlibs:Depends},
@@ -131,13 +137,16 @@
  .
  This library provides basic IO functionality which is used by librpm.
 
-Package: librpmbuild9
+Package: librpmbuild9t64
+Provides: ${t64:Provides}
+Replaces: librpmbuild9
+Breaks: librpmbuild9 (<< ${source:Version})
 Architecture: any
 Section: libs
 Depends: ${shlibs:Depends},
  ${misc:Depends},
- librpm9 (= ${binary:Version}),
- librpmio9 (= ${binary:Version})
+ librpm9t64 (= ${binary:Version}),
+ librpmio9t64 (= ${binary:Version})
 Description: RPM build shared library
  The RPM Package Manager (RPM) is a command-line driven package
  management system capable of installing, uninstalling, verifying,
@@ -145,13 +154,16 @@
  .
  This library provides an interface for building RPM packages.
 
-Package: librpmsign9
+Package: librpmsign9t64
+Provides: ${t64:Provides}
+Replaces: librpmsign9
+Breaks: librpmsign9 (<< ${source:Version})
 Architecture: any
 Section: libs
 Depends: ${shlibs:Depends},
  ${misc:Depends},
- librpm9 (= ${binary:Version}),
- librpmio9 (= ${binary:Version})
+ librpm9t64 (= ${binary:Version}),
+ librpmio9t64 (= ${binary:Version})
 Description: RPM signing shared library
  The RPM Package Manager (RPM) is a command-line driven package
  management system capable of installing, uninstalling, verifying,
@@ -162,10 +174,10 @@
 Package: librpm-dev
 Architecture: any
 Section: libdevel
-Depends: librpm9 (= ${binary:Version}),
- librpmio9 (= ${binary:Version}),
- librpmbuild9 (= ${binary:Version}),
- librpmsign9 (= ${binary:Version}),
+Depends: librpm9t64 (= ${binary:Version}),
+ librpmio9t64 (= ${binary:Version}),
+ librpmbuild9t64 (= ${binary:Version}),
+ librpmsign9t64 (= ${binary:Version}),
  libpopt-dev,
  libbz2-dev,
  zlib1g-dev,
@@ -193,10 +205,10 @@
 Depends: ${misc:Depends},
  ${shlibs:Depends},
  ${python3:Depends},
- librpm9 (= ${binary:Version}),
- librpmio9 (= ${binary:Version}),
- librpmbuild9 (= ${binary:Version}),
- librpmsign9 (= ${binary:Version}),
+ librpm9t64 (= ${binary:Version}),
+ librpmio9t64 (= ${binary:Version}),
+ librpmbuild9t64 (= ${binary:Version}),
+ librpmsign9t64 (= ${binary:Version}),
  rpm-common (= ${binary:Version})
 Breaks: ${python3:Breaks}
 Provides: ${python3:Provides}
diff -Nru rpm-4.18.2+dfsg/debian/librpm9.install 
rpm-4.18.2+dfsg/debian/librpm9.install
--- rpm-4.18.2+dfsg/debian/librpm9.install  2023-09-04 16:06:55.0 
+
+++ rpm-4.18.2+dfsg/debian/librpm9.install  1970-01-01 00:00:00.0 
+
@@ -1 +0,0 @@
-usr/lib/*/librpm.so.*
diff -Nru rpm-4.18.2+dfsg/debian/librpm9.symbols 
rpm-4.18.2+dfsg/debian/librpm9.symbols
--- rpm-4.18.2+dfsg/debian/librpm9.symbols  2024-02-25 13:12:25.0 
+
+++ rpm-4.18.2+dfsg/debian/librpm9.symbols  1970-01-01 00:00:00.0 
+
@@ -1,526 +0,0 @@
-librpm.so.9 

Bug#721137: ghostscript: ps2pdf produces bad pdf on x86_64 (unreadeable text)

[Steven Robbins]

I've just tested with ghostscript 10.02.1 and found the situation remains as 
described in 2015, below.  Specifically, I checked that:

* the four files attached in message #15 all render without issues using evince

* tp2A_scilab_N1.pdf renders fine with xpdf, but many warning are emitted on 
the console S(yntax Warning: Bad bounding box in Type 3 glyph)

* ps2pdf 10.02.1 produces a pdf file that again renders fine, but shows the 
same 
syntax warnings as noted above

* rendering to png (as below) works fine

-Steve

On Thu, 29 Oct 2015 17:17:50 +0100 (CET) whoami...@free.fr wrote:

> Secondly, the pdf viewers available in Jessie are doing a better job
> at displaying this test.pdf:
>   - Evince (or actually the underlying poppler library) is now displaying 
correctly
> this problematic pdf. Try for instance 'pdftocairo -png test.pdf 
test.png'.
>   - Xpdf is still displaying correctly these pdf, but still with the warning
> about "Bad bounding box in Type 3 glyph".
>   - I tried to use directly gs for rendering to png, and it works fine:
>  gs -dSAFER -dNOPAUSE -sDEVICE=png16m -dTextAlphaBits=4 -dBATCH -
dGraphicsAlphaBits=4 -dQUIET -r100 -sOutputFile=test.png test.pdf
>   - The only issue left is with the mupdf viewer (or its command-line tool 
mudraw).
> I've attached the png obtained from the original test.pdf via:
>  mudraw -o test.png test.pdf
> It looks exactly as the earlier faulty display (three black dots instead 
of
> the expected text) that was obtained via Wheezy's evince.
> 
> Anyway, I still think that ps2pdf is producing an erroneous pdf, and that 
the various
> pdf viewers are doing there best to overcome this issue. Indeed, as hinted 
by the
> xpdf warnings, the /FontBBox [0 0 1 -1] in test.pdf looks quite wrong.
> 


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

Bug#1064779: Error message

[no . snip]

Error message:
E919: Répertoire introuvable dans 'packpath' : "pack/*/opt/python-jedi"
-- 
 Envoyé avec Tuta, la messagerie sécurisée & sans publicité. 
 https://tuta.com

Bug#1063137: libtabixpp: NMU diff for 64-bit time_t transition

[Steve Langasek]

Hello,

The package that was previously uploaded to experimental was unfortunately
broken because we did not notice that the package uses d-shlibs and
therefore needs additional changes.

Please find a fixed patch attached.
-- 
Steve Langasek   Give me a lever long enough and a Free OS
Debian Developer   to set it on, and I can move the world.
Ubuntu Developer   https://www.debian.org/
slanga...@ubuntu.com vor...@debian.org
diff -Nru libtabixpp-1.1.2/debian/changelog libtabixpp-1.1.2/debian/changelog
--- libtabixpp-1.1.2/debian/changelog   2024-02-17 14:40:37.0 +
+++ libtabixpp-1.1.2/debian/changelog   2024-02-26 00:29:00.0 +
@@ -1,3 +1,16 @@
+libtabixpp (1.1.2-2.1~exp2) experimental; urgency=medium
+
+  * Bump build-dependency on d-shlibs for --t64 support.
+
+ -- Steve Langasek   Mon, 26 Feb 2024 00:29:00 +
+
+libtabixpp (1.1.2-2.1~exp1) experimental; urgency=medium
+
+  * Non-maintainer upload.
+  * Rename libraries for 64-bit time_t transition.
+
+ -- Steve Langasek   Sat, 24 Feb 2024 08:07:05 +
+
 libtabixpp (1.1.2-2) unstable; urgency=medium
 
   * Enable building twice in a row.
diff -Nru libtabixpp-1.1.2/debian/control libtabixpp-1.1.2/debian/control
--- libtabixpp-1.1.2/debian/control 2024-02-17 14:35:24.0 +
+++ libtabixpp-1.1.2/debian/control 2024-02-26 00:29:00.0 +
@@ -8,14 +8,17 @@
libhts-dev,
zlib1g-dev,
libbz2-dev,
-   d-shlibs
+   d-shlibs (>= 0.106~)
 Standards-Version: 4.6.2
 Vcs-Browser: https://salsa.debian.org/med-team/libtabixpp
 Vcs-Git: https://salsa.debian.org/med-team/libtabixpp.git
 Homepage: https://github.com/ekg/tabixpp
 Rules-Requires-Root: no
 
-Package: libtabixpp0
+Package: libtabixpp0t64
+Provides: ${t64:Provides}
+Replaces: libtabixpp0
+Conflicts: libtabixpp0 (<< ${source:Version})
 Architecture: any
 Multi-Arch: same
 Section: libs
@@ -35,7 +38,7 @@
 Multi-Arch: same
 Section: libdevel
 Depends: ${misc:Depends},
- libtabixpp0 (= ${binary:Version}),
+ libtabixpp0t64 (= ${binary:Version}),
  libhts-dev,
  zlib1g-dev,
  ${devlibs:Depends}
diff -Nru libtabixpp-1.1.2/debian/libtabixpp0.symbols 
libtabixpp-1.1.2/debian/libtabixpp0.symbols
--- libtabixpp-1.1.2/debian/libtabixpp0.symbols 2024-02-17 14:40:37.0 
+
+++ libtabixpp-1.1.2/debian/libtabixpp0.symbols 1970-01-01 00:00:00.0 
+
@@ -1,13 +0,0 @@
-libtabixpp.so.0 libtabixpp0 #MINVER#
-* Build-Depends-Package: libtabixpp-dev
- 
_ZN5Tabix11getNextLineERNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEE@Base
 1.0.0
- _ZN5Tabix13getKstringPtrEv@Base 1.1.0
- _ZN5Tabix13getNextLineKSEv@Base 1.1.0
- 
_ZN5Tabix9getHeaderERNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEE@Base 
1.0.0
- 
_ZN5Tabix9setRegionERNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEE@Base 
1.0.0
- _ZN5TabixC1ERNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEE@Base 1.0.0
- _ZN5TabixC1Ev@Base 1.0.0
- _ZN5TabixC2ERNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEE@Base 1.0.0
- _ZN5TabixC2Ev@Base 1.0.0
- _ZN5TabixD1Ev@Base 1.0.0
- _ZN5TabixD2Ev@Base 1.0.0
diff -Nru libtabixpp-1.1.2/debian/libtabixpp0t64.lintian-overrides 
libtabixpp-1.1.2/debian/libtabixpp0t64.lintian-overrides
--- libtabixpp-1.1.2/debian/libtabixpp0t64.lintian-overrides1970-01-01 
00:00:00.0 +
+++ libtabixpp-1.1.2/debian/libtabixpp0t64.lintian-overrides2024-02-24 
08:06:27.0 +
@@ -0,0 +1 @@
+libtabixpp0t64: package-name-doesnt-match-sonames libtabixpp0
diff -Nru libtabixpp-1.1.2/debian/libtabixpp0t64.symbols 
libtabixpp-1.1.2/debian/libtabixpp0t64.symbols
--- libtabixpp-1.1.2/debian/libtabixpp0t64.symbols  1970-01-01 
00:00:00.0 +
+++ libtabixpp-1.1.2/debian/libtabixpp0t64.symbols  2024-02-24 
08:06:48.0 +
@@ -0,0 +1,13 @@
+libtabixpp.so.0 libtabixpp0t64 #MINVER#
+* Build-Depends-Package: libtabixpp-dev
+ 
_ZN5Tabix11getNextLineERNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEE@Base
 1.0.0
+ _ZN5Tabix13getKstringPtrEv@Base 1.1.0
+ _ZN5Tabix13getNextLineKSEv@Base 1.1.0
+ 
_ZN5Tabix9getHeaderERNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEE@Base 
1.0.0
+ 
_ZN5Tabix9setRegionERNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEE@Base 
1.0.0
+ _ZN5TabixC1ERNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEE@Base 1.0.0
+ _ZN5TabixC1Ev@Base 1.0.0
+ _ZN5TabixC2ERNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEE@Base 1.0.0
+ _ZN5TabixC2Ev@Base 1.0.0
+ _ZN5TabixD1Ev@Base 1.0.0
+ _ZN5TabixD2Ev@Base 1.0.0
diff -Nru libtabixpp-1.1.2/debian/rules libtabixpp-1.1.2/debian/rules
--- libtabixpp-1.1.2/debian/rules   2024-02-17 14:40:37.0 +
+++ libtabixpp-1.1.2/debian/rules   2024-02-26 00:29:00.0 +
@@ -14,6 +14,7 @@
ln -s libtabixpp.so.* libtabixpp.so
cp tabix.hpp debian/tabix.hpp

Bug#1064805: postfix: installs same filename to both bin and sbin

[cacin]

Package: postfix
Severity: normal

Dear Maintainer,

your package installs the filename `rmail` to both bin and sbin as opposed to 
just one of those locations.

This causes a problem on a filesystem layout where bin and sbin are merged into 
a single real directory, typically by sbin being a symlink to bin. Such a 
filesystem layout has become standard on some distributions now, and others are 
moving onto in their next releases.

Please pick one location and install it only there. /usr/bin is preferred over 
any other location.

Thank you for maintaining software in debian.

Bug#1064575: python-pyswarms-doc: please make the build reproducible.

[James Addison]

Followup-For: Bug #1064575

On Sat, 24 Feb 2024 12:33:50 +, I wrote:
> Part of the documentation rendering process - I have not determined exactly
> what yet - adds an 'alt' attribute when it does not exist, and generates a
> randomized hex string to use as the value of the attribute.  This causes the
> resulting python-pyswarms-doc package to vary on each build.

Part of the reason for this appears to be the nbsphinx component; when it
encounters HTML  elements, it emits reStructuredText markdown containing
an alt attribute if one was found on the element, and defines an rST
substitution[1] named by a UUID4-generated value converted to hexadecimal.

Next question: where is that substitution name used when the ':alt:' option
is not found on the image directive?

[1] - 
https://sources.debian.org/src/nbsphinx/0.8.11%2Bds-1/src/nbsphinx.py/#L1398-L1399

Bug#1063136: libslow5lib: NMU diff for 64-bit time_t transition

[Steve Langasek]

Hello,

The package that was previously uploaded to experimental was unfortunately
broken because we did not notice that the package uses d-shlibs and
therefore needs additional changes.

Please find a fixed patch attached.
-- 
Steve Langasek   Give me a lever long enough and a Free OS
Debian Developer   to set it on, and I can move the world.
Ubuntu Developer   https://www.debian.org/
slanga...@ubuntu.com vor...@debian.org
diff -Nru libslow5lib-0.7.0+dfsg/debian/changelog 
libslow5lib-0.7.0+dfsg/debian/changelog
--- libslow5lib-0.7.0+dfsg/debian/changelog 2023-01-14 21:58:31.0 
+
+++ libslow5lib-0.7.0+dfsg/debian/changelog 2024-02-26 00:18:12.0 
+
@@ -1,3 +1,16 @@
+libslow5lib (0.7.0+dfsg-2.1~exp2) experimental; urgency=medium
+
+  * Bump build-dependency on d-shlibs for --t64 support.
+
+ -- Steve Langasek   Mon, 26 Feb 2024 00:18:12 +
+
+libslow5lib (0.7.0+dfsg-2.1~exp1) experimental; urgency=medium
+
+  * Non-maintainer upload.
+  * Rename libraries for 64-bit time_t transition.
+
+ -- Steve Langasek   Mon, 05 Feb 2024 08:28:40 +
+
 libslow5lib (0.7.0+dfsg-2) unstable; urgency=medium
 
   * Team Upload.
diff -Nru libslow5lib-0.7.0+dfsg/debian/control 
libslow5lib-0.7.0+dfsg/debian/control
--- libslow5lib-0.7.0+dfsg/debian/control   2023-01-14 21:58:26.0 
+
+++ libslow5lib-0.7.0+dfsg/debian/control   2024-02-26 00:17:14.0 
+
@@ -5,7 +5,7 @@
 Priority: optional
 Build-Depends: debhelper-compat (= 13),
cmake,
-   d-shlibs,
+   d-shlibs (>= 0.106~),
dh-python,
python3-all-dev,
libstreamvbyte-dev,
@@ -21,7 +21,10 @@
 Homepage: https://github.com/hasindu2008/slow5lib
 Rules-Requires-Root: no
 
-Package: libslow5-0
+Package: libslow5-0t64
+Provides: ${t64:Provides}
+Replaces: libslow5-0
+Conflicts: libslow5-0 (<< ${source:Version})
 Architecture: any
 Section: libs
 Depends: ${shlibs:Depends},
@@ -49,7 +52,7 @@
 Package: libslow5-dev
 Architecture: any
 Section: libdevel
-Depends: libslow5-0 (= ${binary:Version}),
+Depends: libslow5-0t64 (= ${binary:Version}),
  ${shlibs:Depends},
  ${misc:Depends}
 Multi-Arch: same
@@ -77,7 +80,7 @@
 Package: python3-slow5
 Architecture: any
 Section: python
-Depends: libslow5-0 (= ${binary:Version}),
+Depends: libslow5-0t64 (= ${binary:Version}),
  ${shlibs:Depends},
  ${python3:Depends},
  ${misc:Depends}
diff -Nru libslow5lib-0.7.0+dfsg/debian/libslow5-0.symbols 
libslow5lib-0.7.0+dfsg/debian/libslow5-0.symbols
--- libslow5lib-0.7.0+dfsg/debian/libslow5-0.symbols2023-01-14 
20:35:31.0 +
+++ libslow5lib-0.7.0+dfsg/debian/libslow5-0.symbols1970-01-01 
00:00:00.0 +
@@ -1,155 +0,0 @@
-libslow5.so.0 libslow5-0 #MINVER#
- __slow5_press_free@Base 0.5.1
- __slow5_press_init@Base 0.5.1
- ks_combsort_str_slow5@Base 0.5.1
- ks_heapadjust_str_slow5@Base 0.5.1
- ks_heapmake_str_slow5@Base 0.5.1
- ks_heapsort_str_slow5@Base 0.5.1
- ks_introsort_str_slow5@Base 0.5.1
- ks_ksmall_str_slow5@Base 0.5.1
- ks_mergesort_str_slow5@Base 0.5.1
- ks_shuffle_str_slow5@Base 0.5.1
- slow5_add_rec@Base 0.5.1
- slow5_asprintf@Base 0.5.1
- slow5_ato_int16@Base 0.5.1
- slow5_ato_int32@Base 0.5.1
- slow5_ato_int64@Base 0.5.1
- slow5_ato_int8@Base 0.5.1
- slow5_ato_uint16@Base 0.5.1
- slow5_ato_uint32@Base 0.5.1
- slow5_ato_uint64@Base 0.5.1
- slow5_ato_uint8@Base 0.5.1
- slow5_aux_add@Base 0.6.0
- slow5_aux_get_char@Base 0.5.1
- slow5_aux_get_double@Base 0.5.1
- slow5_aux_get_double_array@Base 0.5.1
- slow5_aux_get_enum@Base 0.5.1
- slow5_aux_get_enum_array@Base 0.5.1
- slow5_aux_get_float@Base 0.5.1
- slow5_aux_get_float_array@Base 0.5.1
- slow5_aux_get_int16@Base 0.5.1
- slow5_aux_get_int16_array@Base 0.5.1
- slow5_aux_get_int32@Base 0.5.1
- slow5_aux_get_int32_array@Base 0.5.1
- slow5_aux_get_int64@Base 0.5.1
- slow5_aux_get_int64_array@Base 0.5.1
- slow5_aux_get_int8@Base 0.5.1
- slow5_aux_get_int8_array@Base 0.5.1
- slow5_aux_get_string@Base 0.5.1
- slow5_aux_get_uint16@Base 0.5.1
- slow5_aux_get_uint16_array@Base 0.5.1
- slow5_aux_get_uint32@Base 0.5.1
- slow5_aux_get_uint32_array@Base 0.5.1
- slow5_aux_get_uint64@Base 0.5.1
- slow5_aux_get_uint64_array@Base 0.5.1
- slow5_aux_get_uint8@Base 0.5.1
- slow5_aux_get_uint8_array@Base 0.5.1
- slow5_aux_meta_add@Base 0.5.1
- slow5_aux_meta_add_enum@Base 0.5.1
- slow5_aux_meta_enum_parse@Base 0.5.1
- slow5_aux_meta_free@Base 0.5.1
- slow5_aux_meta_init@Base 0.5.1
- slow5_aux_meta_init_empty@Base 0.5.1
- slow5_aux_set@Base 0.6.0
- slow5_aux_set_string@Base 0.6.0
- slow5_close@Base 0.5.1
- slow5_compress_footer_next@Base 0.5.1
- slow5_convert@Base 0.5.1
- slow5_data_to_str@Base 0.5.1
- slow5_decode@Base 0.7.0
- slow5_decode_record_press@Base 0.5.1
- slow5_decode_signal_press@Base 0.5.1
- slow5_double_to_str@Base 0.5.1
- 

Bug#1064804: policycoreutils: installs same filename to both bin and sbin

[cacin]

Package: policycoreutils
Severity: normal

Dear Maintainer,

your package installs the filename `sestatus` to both bin and sbin as opposed 
to just one of those locations.

This causes a problem on a filesystem layout where bin and sbin are merged into 
a single real directory, typically by sbin being a symlink to bin. Such a 
filesystem layout has become standard on some distributions now, and others are 
moving onto in their next releases.

Please pick one location and install it only there. /usr/bin is preferred over 
any other location.

Thank you for maintaining software in debian.

Bug#1064798: kmod: installs same filename to both bin and sbin

[Marco d'Itri]

On Feb 26, ca...@allfreemail.net wrote:

> This causes a problem on a filesystem layout where bin and sbin are 
> merged into a single real directory, typically by sbin being a symlink 
> to bin. Such a filesystem layout has become standard on some 
> distributions now, and others are moving onto in their next releases.
This is not supported by Debian and we have no such plans.
But obviously it is still a bug, and I will fix in whenever I will do 
a new upload.

-- 
ciao,
Marco


signature.asc
Description: PGP signature

Bug#1064624: Hard to short-stroke an encrypted drive

[Matthew Wilcox]

On Mon, Feb 26, 2024 at 12:34:50AM +0100, Pascal Hambourg wrote:
> Not if you do not write anything to them, or if you TRIM them.

You can stop explaining to me how TRIM works.

commit 0c659b82d11e
Author: Matthew Wilcox 
Date:   Thu Apr 2 10:37:25 2009 -0400

ata: Add TRIM infrastructure

> You may either
> - tell the installer not to erase (=write) the encrypted partition (if
> guided partitioning prompts it, not sure)
> or
> - enable "discard" in /etc/crypttab (should be the default)
> - create a logical volume in the free VG space
> - blkdiscard the logical volume

Last time I checked, dm-crypt did not pass DISCARD requests through to
the underlying device because it's a security hazard.

Bug#1064803: open-iscsi: installs same filename to both bin and sbin

[cacin]

Package: open-iscsi
Severity: normal

Dear Maintainer,

your package installs the filename `iscsiadm` to both bin and sbin as opposed 
to just one of those locations.

This causes a problem on a filesystem layout where bin and sbin are merged into 
a single real directory, typically by sbin being a symlink to bin. Such a 
filesystem layout has become standard on some distributions now, and others are 
moving onto in their next releases.

Please pick one location and install it only there. /usr/bin is preferred over 
any other location.

Thank you for maintaining software in debian.

Bug#1064802: oggvideotools: installs same filename to both bin and sbin

[cacin]

Source: oggvideotools
Version: 0.9.1-6
Severity: normal

Dear Maintainer,

your package installs the filename `mkThumbs` to both bin and sbin as opposed 
to just one of those locations.

This causes a problem on a filesystem layout where bin and sbin are merged into 
a single real directory, typically by sbin being a symlink to bin. Such a 
filesystem layout has become standard on some distributions now, and others are 
moving onto in their next releases.

Please pick one location and install it only there. /usr/bin is preferred over 
any other location.

Thank you for maintaining software in debian.

Bug#1064624: Hard to short-stroke an encrypted drive

[Pascal Hambourg]

On 25/02/2024 at 23:55, Matthew Wilcox wrote:


I want "use largest contiguous space and set up encrypted LVM".
That would let me reserve 200GB of my SSD as unencrypted free space,
which will improve the write endurance of my SSD.


Alternatively, the installer allows to reserve free space in the encrypted
volume group.


That does not accomplish my goal of extending the life of my SSD.  The
SSD will see those blocks as "in use" because they have encrypted data
written to them


Not if you do not write anything to them, or if you TRIM them.

You may either
- tell the installer not to erase (=write) the encrypted partition (if 
guided partitioning prompts it, not sure)

or
- enable "discard" in /etc/crypttab (should be the default)
- create a logical volume in the free VG space
- blkdiscard the logical volume


(it cannot tell that they are encrypted blocks of zeroes
because, well, they're encrypted).


Irrelevant. Once written, even with plaintext zeroes, a block is 
considered used until it is TRIMmed.

Bug#1064801: nsscache: installs same filename to both bin and sbin

[cacin]

Source: nsscache
Version: 0.49-2
Severity: normal

Dear Maintainer,

your package installs the filename `nsscache` to both bin and sbin as opposed 
to just one of those locations.

This causes a problem on a filesystem layout where bin and sbin are merged into 
a single real directory, typically by sbin being a symlink to bin. Such a 
filesystem layout has become standard on some distributions now, and others are 
moving onto in their next releases.

Please pick one location and install it only there. /usr/bin is preferred over 
any other location.

Thank you for maintaining software in debian.

Bug#1064126: libvirt: install NSS modules into /usr

[Andrea Bolognani]

On Sun, Feb 25, 2024 at 08:05:36PM +0100, Michael Biebl wrote:
> Am 25.02.24 um 19:30 schrieb Andrea Bolognani:
> > So what I'm wondering right now is, how much does libvirt shipping
> > these files outside of /usr for a while longer negatively impact the
> > overall transition plans? I'd be happy to get out of your way as soon
> > as possible, but at the same time I'm wary of potentially introducing
> > issues due to the unforeseen interactions between these changes.
> 
> It depends on what you understand with "a while longer".
> A couple more weeks/months/years/Debian releases?

Definitely not a couple of years or releases! My aim is to make
modular daemons available in trixie.

> Obviously I think the sooner we get the usrmerge transition finished in
> trixie, the better, to be able to iron out any unforeseen issues.

Right there with you. I just don't want to rush things, especially
since AFAIK some really problematic scenarios can be triggered when
paths are canonicalized at the same time as they are moved across
binary packages.

Going forward, I will focus all the time I can spend on Debian on
reorganizing the libvirt package to enable modular daemons. I hope to
have at least a rough implementation ready within a few weeks.

-- 
Andrea Bolognani 
Resistance is futile, you will be garbage collected.


signature.asc
Description: PGP signature

Bug#1055067: isc-dhcp-client: network-manager 1.44.2-3 changed path to nm-dhcp-helper, apparmor need update

[Sven-Haegar Koch]

On Fri, 23 Feb 2024, Santiago Ruano Rincón wrote:

> Really sorry, this has fallen through the cracks.

Thanks - no problem, happens.

> Could you please confirm the version available in this repo fixes the
> issue:
> 
> https://debian.pages.debian.net/-/isc-dhcp/-/jobs/5350735/artifacts/aptly/index.html

It seems to work fine using 4.4.3-P1-6~1.gbpcd0ae3+salsaci+20240223+56, 
but I had to manually remove /etc/apparmor.d/sbin.dhclient and execute 
"systemctl restart apparmor" to really use your version - the package 
created a new /etc/apparmor.d/usr.sbin.dhclient, but left the old 
configfile around.

While installing your test package I lost wifi connection, but I think 
that was not from your package but from updating network-manager from 
unstable at the same time (did dist-upgrade), which always breaks my 
network.

c'ya
sven-haegar

-- 
Three may keep a secret, if two of them are dead.
- Ben F.

Bug#1064800: menu: installs same filename to both bin and sbin

[cacin]

Source: menu
Version: 2.1.50
Severity: normal

Dear Maintainer,

your package installs the filenames `install-menu` and `su-to-root` to both bin 
and sbin as opposed to just one of those locations.

This causes a problem on a filesystem layout where bin and sbin are merged into 
a single real directory, typically by sbin being a symlink to bin. Such a 
filesystem layout has become standard on some distributions now, and others are 
moving onto in their next releases.

Please pick one location and install it only there. /usr/bin is preferred over 
any other location.

Thank you for maintaining software in debian.

Bug#1064624: Hard to short-stroke an encrypted drive

[Matthew Wilcox]

On Sun, Feb 25, 2024 at 11:42:37PM +0100, Pascal Hambourg wrote:
> On 25/02/2024 at 05:40, Matthew Wilcox wrote:
> > 
> > The partitioner "guided partitioning" offers me:
> > 
> >   - use the largest continuous free space
> >   - use entire disk
> >   - use entire disk and set up LVM
> >   - use entire disk and set up encrypted LVM
> > 
> > I want "use largest contiguous space and set up encrypted LVM".
> > That would let me reserve 200GB of my SSD as unencrypted free space,
> > which will improve the write endurance of my SSD.
> 
> Alternatively, the installer allows to reserve free space in the encrypted
> volume group.

That does not accomplish my goal of extending the life of my SSD.  The
SSD will see those blocks as "in use" because they have encrypted data
written to them (it cannot tell that they are encrypted blocks of zeroes
because, well, they're encrypted).

The unused area has to be part of the unencrypted disk.  And then I have
to call TRIM on it.

> > Also once I start partitioning, eg, "and set up LVM", I can't delete the
> > partitions again.
> 
> The installer allows to delete logical volumes, volume groups and
> unencrypted partitions formerly used as physical volumes, but not encrypted
> volumes nor their underlying partitions.

Yes.  This is a poor experience.

Bug#1064799: dvdbackup: Vcs-* fields (and perhaps Homepage) outdated

[Christoph Anton Mitterer]

Source: dvdbackup
Version: 0.4.2-4.1
Severity: minor


Hey.

The Vcs-* package fields and perhaps also Homepage (the SF site and
repo there seems even more outdated compared to launchpad) may be
outdated.

Cheers,
Chris.

Bug#1064796:

[Michael Hudson-Doyle]

Note that this diff includes the changes attached to bug 1053111.

Bug#1064783: apt-listbugs: installs same filename to both bin and sbin

[Francesco Poli]

Control: tags -1 + moreinfo


On Sun, 25 Feb 2024 21:36:44 + ca...@allfreemail.net wrote:

[...]
> Dear Maintainer,
> 
> your package installs the filename apt-listbugs to both bin and sbin as 
> opposed to just one of those locations.

Hello,
thanks for your bug report.

The command 'apt-listbugs' is installed to /usr/bin and a symbolic link
to it is installed to /usr/sbin .

A long time ago, the package used to only install the command
to /usr/sbin , but apt-listbugs may be useful for unprivileged users
too (for some of its functionalities), hence it was moved to /usr/bin ,
with a symlink from /usr/sbin for backward compatibility (to avoid
breaking possible custom scripts with the full path hardcoded...).

> 
> This causes a problem on a filesystem layout where bin and sbin are merged 
> into a single real directory, typically by sbin being a symlink to bin.

This layout is not currently supported by Debian, as far as I can tell.

> Such a filesystem layout has become standard on some distributions now, and 
> others are moving onto in their next releases.

Which distributions?

I am not aware of any plans in Debian to move in that direction.

See the [usrmerge FAQ], which includes, in part:

[...]
| Is this about merging /usr/bin/ and /usr/sbin/?
|
| No, there are no plans to do that.
[...]

[usrmerge FAQ]: 


Could you please elaborate a bit more on why you think this feature of
the apt-listbugs Debian package could be an issue?

Which other distributions (Debian-derivatives or otherwise) include
apt-listbugs?
Without massive modifications, apt-listbugs can only be useful for
APT-based distributions with a debbugs-based bug tracking system.
As far as I know, there are no other such distributions beyond Debian.
Do you happen to know any?

> 
> Please pick one location and install it only there. /usr/bin is preferred 
> over any other location.

I am a bit hesitant to do so (risking to break random custom scripts),
unless there's a good reason.

If you explain which distributions are or could be affected by this
feature of apt-listbugs, I will think about it.
Otherwise, I can close this bug report, since what you are reporting
does not seem to be an actual issue for Debian.

> 
> Thank you for maintaining software in debian.

You're welcome.
Thanks to you for caring about apt-listbugs!



-- 
 http://www.inventati.org/frx/
 There's not a second to spare! To the laboratory!
. Francesco Poli .
 GnuPG key fpr == CA01 1147 9CD2 EFDF FB82  3925 3E1C 27E1 1F69 BFFE


pgpWZUaklR6aJ.pgp
Description: PGP signature

Bug#1064798: kmod: installs same filename to both bin and sbin

[cacin]

Package: kmod
Version: 31+20240202-2
Severity: normal

Dear Maintainer,

your package installs the filename `lsmod` to both bin and sbin as opposed to 
just one of those locations.

This causes a problem on a filesystem layout where bin and sbin are merged into 
a single real directory, typically by sbin being a symlink to bin. Such a 
filesystem layout has become standard on some distributions now, and others are 
moving onto in their next releases.

Please pick one location and install it only there. /usr/bin is preferred over 
any other location.

Thank you for maintaining software in debian.

Bug#1064797: Mediawiki ships with .htaccess files containing outdated access control configuration

[Alain Knaff]

Package: mediawiki
Version: 1:1.39.5-1~deb12u1

Hi,

Mediawiki ships with .htaccess files which contain outdated access
control directives.

for instance, /usr/share/mediawiki/vendor/.htaccess contains:

  Deny from all

rather than the more current

  Require all denied


The new syntax was introduced in Apache 2.4, shipping since at least
Jessie, April 2015.

Wouldn't it be time to go with the new syntax, as less and less people
now continue to use the access_compat module?

Thanks,

Alain

Bug#989706: Now it works for me too (Was: [...] DeprecationWarning from csvclean)

[Kingsley G. Morse Jr.]

Hi Tony,

Thanks.

I'm happy to report

I just retested

$ echo -e "1,2,3\n4,5,6\n7,8" | csvclean

and got no DeprecationWarning with version

1.0.7-1 of csvkit and

3.11.4-5+b1 of python3.

Kind regards,
Kingsley

On 02/25/2024 22:39, Debian Bug Tracking System wrote:
> This is an automatic notification regarding your Bug report
> which was filed against the csvkit package:
> 
> #989706: csvkit: DeprecationWarning from csvclean
> 
> It has been closed by tony mancill .
> 
> Their explanation is attached below along with your original report.
> If this explanation is unsatisfactory and you have not received a
> better one in a separate message then please contact tony mancill 
>  by
> replying to this email.
> 
> 
> -- 
> 989706: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=989706
> Debian Bug Tracking System
> Contact ow...@bugs.debian.org with problems

> Date: Sun, 25 Feb 2024 14:37:14 -0800
> From: tony mancill 
> To: 989706-d...@bugs.debian.org
> Subject: Re: Bug#989706: csvkit: DeprecationWarning from csvclean
> 
> On Thu, Jun 10, 2021 at 04:08:09PM -0700, Kingsley G. Morse Jr. wrote:
> > Here's a one-liner that causes its "csvclean"
> > command to complain, at least on my computer.
> > 
> > bash$ echo -e "1,2,3\n4,5,6\n7,8" | csvclean 
> > /usr/lib/python3/dist-packages/unittest2/compatibility.py:143: 
> > DeprecationWarning: Using or importing the ABCs from 'collections' instead 
> > of from 'collections.abc' is deprecated since Python 3.3, and in 3.10 it 
> > will stop working
> > 1 error logged to stdin_err.csv
> 
> I can't reproduce the reported behavior on Debian bullseye, bookwork, 
> trixie, or unstable.  I suspect it was resolved during the bullseye
> release cycle.
> 
> Therefore, I am closing the bug.  Feel free to either reopen or file a
> new bug if you detect any problems with csvkit.
> 
> Thank you,
> tony

> Date: Thu, 10 Jun 2021 16:08:09 -0700
> From: "Kingsley G. Morse Jr." 
> To: Debian Bug Tracking System 
> Subject: csvkit: DeprecationWarning from csvclean
> X-Mailer: reportbug 6.6.6
> 
> Package: csvkit
> Version: 1.0.5-2
> Severity: normal
> 
> Dear Maintainer,
> 
> Thank you very much for sharing your valuable time
> and skill to maintain Debian's csvkit package.
> 
> Here's a one-liner that causes its "csvclean"
> command to complain, at least on my computer.
> 
> bash$ echo -e "1,2,3\n4,5,6\n7,8" | csvclean 
> /usr/lib/python3/dist-packages/unittest2/compatibility.py:143: 
> DeprecationWarning: Using or importing the ABCs from 'collections' instead of 
> from 'collections.abc' is deprecated since Python 3.3, and in 3.10 it will 
> stop working
> 1 error logged to stdin_err.csv
> 
> I'd like to think eliminating the warning is as
> easy as importing the ABCs from 'collections.abc'.
> 
> Maybe you'd like to use my little one liner to
> test fixes for csvkit and python3-csvkit.
> 
> Thanks again,
> Kingsley
> 
> -- System Information:
> Debian Release: bullseye/sid
>   APT prefers unstable-debug
>   APT policy: (500, 'unstable-debug'), (500, 'unstable')
> Architecture: i386 (i686)
> 
> Kernel: Linux 4.4.0-1-686-pae (SMP w/2 CPU cores)
> Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
> Shell: /bin/sh linked to /bin/bash
> Init: systemd (via /run/systemd/system)
> 
> Versions of packages csvkit depends on:
> ii  python3-csvkit  1.0.5-2
> pn  python3:any 
> 
> csvkit recommends no packages.
> 
> Versions of packages csvkit suggests:
> ii  csvkit-doc  1.0.2-1
> 
> -- no debconf information


-- 
Time is the fire in which we all burn.

Bug#1064796: e2fsprogs: NMU diff for 64-bit time_t transition

[mwhudson]

Source: e2fsprogs
Version: 1.47.0-2
Severity: important
Tags: patch pending sid trixie
User: debian-...@lists.debian.org
Usertags: time-t

NOTICE: these changes must not be uploaded to unstable yet!

Dear maintainer,

As part of the 64-bit time_t transition required to support 32-bit
architectures in 2038 and beyond
(https://wiki.debian.org/ReleaseGoals/64bit-time), we have identified
e2fsprogs as a source package shipping runtime libraries whose ABI
either is affected by the change in size of time_t, or could not be
analyzed via abi-compliance-checker (and therefore to be on the safe
side we assume is affected).

To ensure that inconsistent combinations of libraries with their
reverse-dependencies are never installed together, it is necessary to
have a library transition, which is most easily done by renaming the
runtime library package.

Since turning on 64-bit time_t is being handled centrally through a change
to the default dpkg-buildflags (https://bugs.debian.org/1037136), it is
important that libraries affected by this ABI change all be uploaded close
together in time.  Therefore I have prepared a 0-day NMU for e2fsprogs
which will initially be uploaded to experimental if possible, then to
unstable after packages have cleared binary NEW.

Please find the patch for this NMU attached.

If you have any concerns about this patch, please reach out ASAP.  Although
this package will be uploaded to experimental immediately, there will be a
period of several days before we begin uploads to unstable; so if information
becomes available that your package should not be included in the transition,
there is time for us to amend the planned uploads.



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

Kernel: Linux 6.5.0-21-generic (SMP w/16 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
diff -Nru e2fsprogs-1.47.0/debian/changelog e2fsprogs-1.47.0/debian/changelog
--- e2fsprogs-1.47.0/debian/changelog   2023-03-05 03:16:08.0 +
+++ e2fsprogs-1.47.0/debian/changelog   2024-02-25 22:57:50.0 +
@@ -1,3 +1,16 @@
+e2fsprogs (1.47.0-2.1) experimental; urgency=medium
+
+  * Non-maintainer upload.
+
+  [ Helmut Grohne ]
+  * Fix FTBFS when systemd.pc changes systemdsystemunitdir. (Closes: #1053111)
+
+  [ Michael Hudson-Doyle ]
+  * Account for changes in udevudevdir as well.
+  * Rename libraries for 64-bit time_t transition.
+
+ -- Michael Hudson-Doyle   Sun, 25 Feb 2024 22:57:50 +
+
 e2fsprogs (1.47.0-2) unstable; urgency=medium
 
   * Don't enable metadata_csum_seed and orhpan_file by default (Closes:
diff -Nru e2fsprogs-1.47.0/debian/control e2fsprogs-1.47.0/debian/control
--- e2fsprogs-1.47.0/debian/control 2023-03-05 03:16:08.0 +
+++ e2fsprogs-1.47.0/debian/control 2024-02-25 22:57:50.0 +
@@ -2,7 +2,7 @@
 Section: admin
 Priority: required
 Maintainer: Theodore Y. Ts'o 
-Build-Depends: gettext, texinfo, pkg-config, libfuse-dev [linux-any 
kfreebsd-any] , debhelper-compat (= 12), dh-exec, 
libblkid-dev, uuid-dev, m4, udev [linux-any], systemd [linux-any], cron 
[linux-any]
+Build-Depends: gettext, texinfo, pkg-config, libfuse-dev [linux-any 
kfreebsd-any] , debhelper-compat (= 12), dh-exec, 
libblkid-dev, uuid-dev, m4, udev [linux-any], systemd [linux-any], systemd-dev 
[linux-any], cron [linux-any]
 Rules-Requires-Root: no
 Standards-Version: 4.6.2
 Homepage: http://e2fsprogs.sourceforge.net
@@ -64,13 +64,13 @@
  This package provides translations for messages for programs found in
  the 'e2fsprogs' package.
 
-Package: libcom-err2
+Package: libcom-err2t64
 Section: libs
 Priority: optional
 Depends: ${shlibs:Depends}, ${misc:Depends}
-Replaces: libcomerr2 (<< 1.43.9-1~)
-Breaks: libcomerr2 (<< 1.43.9-1~)
-Provides: libcomerr2 (= ${binary:Version})
+Replaces: libcom-err2, libcomerr2 (<< 1.43.9-1~)
+Breaks: libcom-err2 (<< ${source:Version}), libcomerr2 (<< 1.43.9-1~)
+Provides: ${t64:Provides}, libcomerr2 (= ${binary:Version})
 Architecture: any
 Multi-Arch: same
 Pre-Depends: ${misc:Pre-Depends}
@@ -82,7 +82,7 @@
 Package: comerr-dev
 Section: libdevel
 Priority: optional
-Depends: libc6-dev | libc-dev, libcom-err2 (= ${mainBinary}), ${misc:Depends}
+Depends: libc6-dev | libc-dev, libcom-err2t64 (= ${mainBinary}), 
${misc:Depends}
 Suggests: doc-base
 Replaces: e2fslibs-dev (<< 1.33-2), libkrb5-dev (<< 1.3)
 Architecture: any
@@ -94,11 +94,13 @@
  .
  This package contains the development environment for the com_err library.
 
-Package: libss2
+Package: libss2t64
+Provides: ${t64:Provides}
+Breaks: libss2 (<< ${source:Version})
 Section: libs
 Priority: optional
-Depends: libcom-err2, ${shlibs:Depends}, ${misc:Depends}
-Replaces: e2fsprogs (<< 1.34-1)

Bug#1064780: pgpainless: fails to build from source with Java 21 due to SecurityManager UnsupportedException

[tony mancill]

On Mon, Feb 26, 2024 at 09:47:15AM +1300, Vladimir Petko wrote:
>  [1] https://salsa.debian.org/java-team/pgpainless/-/merge_requests/2

Merged and uploaded.

Thank you for the patch,
tony

Bug#1064636: libpcsclite-dev: The i386 libpcsclite-dev 2.0.1-1+b1 package conflicts with the amd64 one

[Francois Gouget]

On Sun, 25 Feb 2024, Ludovic Rousseau wrote:
[...]
> Fixed upstream in
> https://github.com/LudovicRousseau/PCSC/commit/e3bfa449df5283cd7389d505399cc57d2065e637

That's great. Thanks.


-- 
Francois Gouget   http://fgouget.free.fr/
You don't liberate a people. A people liberates itself.
   Youssoupha

Bug#1064624: Hard to short-stroke an encrypted drive

[Pascal Hambourg]

On 25/02/2024 at 05:40, Matthew Wilcox wrote:


The partitioner "guided partitioning" offers me:

  - use the largest continuous free space
  - use entire disk
  - use entire disk and set up LVM
  - use entire disk and set up encrypted LVM

I want "use largest contiguous space and set up encrypted LVM".
That would let me reserve 200GB of my SSD as unencrypted free space,
which will improve the write endurance of my SSD.


Alternatively, the installer allows to reserve free space in the 
encrypted volume group.



Also once I start partitioning, eg, "and set up LVM", I can't delete the
partitions again.


The installer allows to delete logical volumes, volume groups and 
unencrypted partitions formerly used as physical volumes, but not 
encrypted volumes nor their underlying partitions.

Bug#1064795: iproute2: installs same filename to both bin and sbin

[cacin]

Package: iproute2
Version: 6.7.0-2
Severity: normal

Dear Maintainer,

your package installs the filename `ip` to both bin and sbin as opposed to just 
one of those locations.

This causes a problem on a filesystem layout where bin and sbin are merged into 
a single real directory, typically by sbin being a symlink to bin. Such a 
filesystem layout has become standard on some distributions now, and others are 
moving onto in their next releases.

Please pick one location and install it only there. /usr/bin is preferred over 
any other location.

Thank you for maintaining software in debian.

Bug#1064789: pgpool2: autopkgtests fail with Java 21 due to the deprecation warnings

[Vladimir Petko]

Dear Maintainers,

  Would it be possible to consider a merge request[1] that addresses this issue?

Best Regards,
 Vladimir.

 [1] https://salsa.debian.org/postgresql/pgpool2/-/merge_requests/4

Bug#1064617: Passwords should not be changed frequently

[Pascal Hambourg]

On 25/02/2024 at 01:17, Matthew Wilcox wrote:


I just did an installation with the 2024-02-24
debian-testing-amd64-netinst.iso image.  I forget the exact wording
used, but when setting up a user, d-i printed advice that user passwords
should be changed frequently.  This is no longer current good advice
(since 2017):


This topic has some history, see

Bug#1064794: inadyn: installs same filename to both bin and sbin

[cacin]

Source: inadyn
Version: 2.11.0-1
Severity: normal

Dear Maintainer,

your package installs the filename inadyn to both bin and sbin as opposed to 
just one of those locations.

This causes a problem on a filesystem layout where bin and sbin are merged into 
a single real directory, typically by sbin being a symlink to bin. Such a 
filesystem layout has become standard on some distributions now, and others are 
moving onto in their next releases.

Please pick one location and install it only there. /usr/bin is preferred over 
any other location.

Thank you for maintaining software in debian.

Bug#1060000:

[Michael Hudson-Doyle]

It seems that changes are needed to account for the change in `pkg-config
--variable=udevdir udev` as well. Attaching an updated diff that does that
too.

We are going to need e2fsprogs building very soon for the time_t
transition. I wonder if I should just upload this to DELAYED/1 or something.
diff -Nru e2fsprogs-1.47.0/debian/changelog e2fsprogs-1.47.0/debian/changelog
--- e2fsprogs-1.47.0/debian/changelog	2023-03-05 16:16:08.0 +1300
+++ e2fsprogs-1.47.0/debian/changelog	2023-09-27 07:57:57.0 +1300
@@ -1,3 +1,14 @@
+e2fsprogs (1.47.0-2.1) UNRELEASED; urgency=medium
+
+  [ Helmut Grohne ]
+  * Non-maintainer upload.
+  * Fix FTBFS when systemd.pc changes systemdsystemunitdir. (Closes: #-1)
+
+  [ Michael Hudson-Doyle ]
+  * Account for changes in udevudevdir as well.
+
+ -- Helmut Grohne   Tue, 26 Sep 2023 20:57:57 +0200
+
 e2fsprogs (1.47.0-2) unstable; urgency=medium
 
   * Don't enable metadata_csum_seed and orhpan_file by default (Closes:
diff -Nru e2fsprogs-1.47.0/debian/control e2fsprogs-1.47.0/debian/control
--- e2fsprogs-1.47.0/debian/control	2023-03-05 16:16:08.0 +1300
+++ e2fsprogs-1.47.0/debian/control	2023-09-27 07:57:57.0 +1300
@@ -2,7 +2,7 @@
 Section: admin
 Priority: required
 Maintainer: Theodore Y. Ts'o 
-Build-Depends: gettext, texinfo, pkg-config, libfuse-dev [linux-any kfreebsd-any] , debhelper-compat (= 12), dh-exec, libblkid-dev, uuid-dev, m4, udev [linux-any], systemd [linux-any], cron [linux-any]
+Build-Depends: gettext, texinfo, pkg-config, libfuse-dev [linux-any kfreebsd-any] , debhelper-compat (= 12), dh-exec, libblkid-dev, uuid-dev, m4, udev [linux-any], systemd [linux-any], systemd-dev [linux-any], cron [linux-any]
 Rules-Requires-Root: no
 Standards-Version: 4.6.2
 Homepage: http://e2fsprogs.sourceforge.net
diff -Nru e2fsprogs-1.47.0/debian/e2fsprogs.install e2fsprogs-1.47.0/debian/e2fsprogs.install
--- e2fsprogs-1.47.0/debian/e2fsprogs.install	2023-03-05 16:16:08.0 +1300
+++ e2fsprogs-1.47.0/debian/e2fsprogs.install	2023-09-27 07:57:57.0 +1300
@@ -49,5 +49,5 @@
 usr/share/man/man8/resize2fs.8
 usr/share/man/man8/tune2fs.8
 etc
-[linux-any] lib/udev/rules.d
-[linux-any] lib/systemd/system
+[linux-any] ${deb_udevudevdir}/rules.d
+[linux-any] ${deb_systemdsystemunitdir}
diff -Nru e2fsprogs-1.47.0/debian/.gitignore e2fsprogs-1.47.0/debian/.gitignore
--- e2fsprogs-1.47.0/debian/.gitignore	2023-03-05 16:16:08.0 +1300
+++ e2fsprogs-1.47.0/debian/.gitignore	1970-01-01 12:00:00.0 +1200
@@ -1 +0,0 @@
-!patches
diff -Nru e2fsprogs-1.47.0/debian/rules e2fsprogs-1.47.0/debian/rules
--- e2fsprogs-1.47.0/debian/rules	2023-03-05 16:16:08.0 +1300
+++ e2fsprogs-1.47.0/debian/rules	2023-09-27 07:57:57.0 +1300
@@ -14,6 +14,11 @@
 SKIP_FUSE2FS=yes
 endif
 
+ifeq ($(DEB_HOST_ARCH_OS), linux)
+export deb_systemdsystemunitdir = $(shell pkg-config --variable=systemdsystemunitdir systemd | sed s,^/,,)
+export deb_udevudevdir = $(shell pkg-config pkg-config --variable=udevdir udev | sed s,^/,,)
+endif
+
 ifneq ($(filter pkg.e2fsprogs.no-fuse2fs,$(DEB_BUILD_PROFILES)),)
 SKIP_FUSE2FS=yes
 endif

Bug#1064793: i2pd: installs same filename to both bin and sbin

[cacin]

Source: i2pd
Severity: normal

Dear Maintainer,

your package installs the filename i2pd to both bin and sbin as opposed to just 
one of those locations.

This causes a problem on a filesystem layout where bin and sbin are merged into 
a single real directory, typically by sbin being a symlink to bin. Such a 
filesystem layout has become standard on some distributions now, and others are 
moving onto in their next releases.

Please pick one location and install it only there. /usr/bin is preferred over 
any other location.

Thank you for maintaining software in debian.

Bug#1064792: hylafax-client: installs same filename to both bin and sbin

[cacin]

Package: hylafax-client
Severity: normal

Dear Maintainer,

your package installs the filename textfmt to both bin and sbin as opposed to 
just one of those locations.

This causes a problem on a filesystem layout where bin and sbin are merged into 
a single real directory, typically by sbin being a symlink to bin. Such a 
filesystem layout has become standard on some distributions now, and others are 
moving onto in their next releases.

Please pick one location and install it only there. /usr/bin is preferred over 
any other location.

Thank you for maintaining software in debian.

Bug#1064791: No ethernet card in a laptop

[Matthew Wilcox]

Package: debian-installer

On my new laptop, d-i prints "No Ethernet card was detected.  If you know
the name of the driver (etc)".  This confused me, as I thought it _also_
couldn't find the wifi driver (since it's a new laptop, it's possible
the d-i kernel doesn't know about the wifi device).

I suggest that if d-i can find a wifi device, it skips the step where
it gives me a long inscrutable list of module names and asks me to
choose one to make the network work.

Bug#1064377: tcl-expect: identified for time_t transition but no ABI in shlibs

[Steve Langasek]

Control: severity -1 normal

Note that there are no reverse-dependencies in the archive that link against
libexpect, so I think we can downgrade this bug (or close wontfix, at the
maintainer's discretion).

-- 
Steve Langasek   Give me a lever long enough and a Free OS
Debian Developer   to set it on, and I can move the world.
Ubuntu Developer   https://www.debian.org/
slanga...@ubuntu.com vor...@debian.org


signature.asc
Description: PGP signature

Bug#1064790: reportbug: regression when max reports per hour reached

[cacin]

Package: reportbug
Version: 13.0.0
Severity: normal

Dear Maintainer,

reportbug crashes when maximum number of reports per hour is reached. This is a 
regression from previous version where reportbug instead offered to try again 
instead of crashing. Traceback attached.

Connecting to reportbug.debian.org via SMTP...
Traceback (most recent call last):
  File "/usr/lib/python3/dist-packages/reportbug/submit.py", line 484, in 
send_report
refused = conn.sendmail(fromaddr, toaddrs, message)
  ^
  File "/usr/lib/python3.11/smtplib.py", line 901, in sendmail
raise SMTPRecipientsRefused(senderrs)
smtplib.SMTPRecipientsRefused: {'sub...@bugs.debian.org': (451, b'sorry, only 5 
reports per hour for submission')}

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/usr/bin/reportbug", line 2386, in 
main()
  File "/usr/bin/reportbug", line 1094, in main
return iface.user_interface()
   ^^
  File "/usr/bin/reportbug", line 2369, in user_interface
submit.send_report(
  File "/usr/lib/python3/dist-packages/reportbug/submit.py", line 499, in 
send_report
if ui.yes_no(f'SMTP send failure: {x}. You can retry, or save the report 
and exit. Do you want to retry?',
   ^
UnboundLocalError: cannot access local variable 'x' where it is not associated 
with a value

Bug#1064789: pgpool2: autopkgtests fail with Java 21 due to the deprecation warnings

[Vladimir Petko]

Source: pgpool2
Version: 4.3.7-1
Severity: normal

Dear Maintainer,

pgpool2 autopkgtests fail with Java 21 due to the deprecation warnings:

1102s jdbc-tests FAIL stderr: Note: Some input files use or override a
deprecated API.

See[1]

[1]
https://objectstorage.prodstack5.canonical.com/swift/v1/AUTH_0f9aae918d5b4744bf7b827671c86842/autopkgtest-
noble/noble/amd64/p/pgpool2/20240225_000737_342e4@/log.gz


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

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

Bug#1063040: uw-imap: NMU diff for 64-bit time_t transition

[Steve Langasek]

FWIW another option would be to just do a straight library transition on all
archs, bumping the soname to libc-client2007f and not bothering to try to
provide binary compatibility.  There are only 5 reverse-dependencies on
libc-client2007e in the archive, so forcing an ABI transition on all archs
wouldn't be particularly disruptive.  But this should still be left to the
maintainers to decide how to handle it.

On Sun, Feb 25, 2024 at 01:44:27PM -0800, Steve Langasek wrote:
> Control: tags -1 - pending patch
> 
> And that package built but resulted in a change to the soname of the
> library.  And my attempts to fix this have also failed, because d-shlibs
> --t64 support has a strict expectation of 't64' appended to the full name of
> the runtime lib package as deduced from the soname, so wants
> 'libc-client2007et64' when we were trying for 'libc-client2007t64'.
> 
> At this point I'm bailing on trying to fix this package.  cdbs and d-shlibs
> should both have been put down in favor of dh long ago.  Please find
> attached my work in progress for a patch, maybe it's useful to you; but as I
> can't find a solution for this that works with your tooling of choice, I am
> not planning to NMU this package for the time_t transition.
> 
> If you decide that the package name 'libc-client2007et64' is acceptable, I
> can update the override map for the ftp team so that the package passes the
> NEW queue and we can NMU it.
> 
> Or if you work with the d-shlibs maintainer to have sensible behavior for
> your package when being named 'libc-client2007t64', then this patch should
> be sufficient.
> 
> But for now, dropping the pending+patch tags.
> 
> On Sat, Feb 24, 2024 at 02:40:23AM -0800, Steve Langasek wrote:
> > Hello,
> > 
> > The package that was previously uploaded to experimental was unfortunately
> > broken because we did not notice that additional changes were needed to
> > debian/control.in.in.
> > 
> > Please find a fixed patch attached.
> 
> -- 
> Steve Langasek   Give me a lever long enough and a Free OS
> Debian Developer   to set it on, and I can move the world.
> Ubuntu Developer   https://www.debian.org/
> slanga...@ubuntu.com vor...@debian.org

> diff -Nru uw-imap-2007f~dfsg/debian/changelog 
> uw-imap-2007f~dfsg/debian/changelog
> --- uw-imap-2007f~dfsg/debian/changelog   2019-08-26 20:52:52.0 
> +
> +++ uw-imap-2007f~dfsg/debian/changelog   2024-02-25 21:19:39.0 
> +
> @@ -1,3 +1,23 @@
> +uw-imap (8:2007f~dfsg-7.1~exp3) experimental; urgency=medium
> +
> +  * Fix debian/rules to not change the upstream soname.
> +  * Bump build-dependency on d-shlibs for t64 support.
> +
> + -- Steve Langasek   Sun, 25 Feb 2024 21:19:39 +
> +
> +uw-imap (8:2007f~dfsg-7.1~exp2) experimental; urgency=medium
> +
> +  * Update debian/control.in.in, not just debian/control.in.
> +
> + -- Steve Langasek   Sat, 24 Feb 2024 10:23:12 +
> +
> +uw-imap (8:2007f~dfsg-7.1~exp1) experimental; urgency=medium
> +
> +  * Non-maintainer upload.
> +  * Rename libraries for 64-bit time_t transition.
> +
> + -- Steve Langasek   Mon, 05 Feb 2024 20:18:10 +
> +
>  uw-imap (8:2007f~dfsg-7) unstable; urgency=low
>  
>* 2014_openssl1.1.1_sni.patch (new, from Ubuntu): Use SNI when building
> diff -Nru uw-imap-2007f~dfsg/debian/control uw-imap-2007f~dfsg/debian/control
> --- uw-imap-2007f~dfsg/debian/control 2019-08-26 20:52:52.0 +
> +++ uw-imap-2007f~dfsg/debian/control 2024-02-24 10:19:59.0 +
> @@ -16,15 +16,15 @@
>  Vcs-Browser: https://salsa.debian.org/holmgren/uw-imap
>  Homepage: http://www.washington.edu/imap/
>  
> -Package: libc-client2007e-dev
> +Package: libc-client2007t64-dev
>  Section: libdevel
>  Architecture: any
>  Depends: ${devlibs:Depends},
>   ${misc:Depends},
> - libc-client2007e (= ${binary:Version})
> + libc-client2007t64 (= ${binary:Version})
>  Conflicts: libc-client-dev
>  Replaces: libc-client-dev
> -Provides: libc-client-dev
> +Provides: libc-client-dev, libc-client-2007e-dev (= ${binary:Version})
>  Description: c-client library for mail protocols - development files
>   IMAP (Internet Message Access Protocol) is a method of accessing
>   electronic messages kept on a (possibly shared) mail server.
> @@ -37,7 +37,10 @@
>   This package contains the static c-client library and development
>   headers.
>  
> -Package: libc-client2007e
> +Package: libc-client2007t64
> +Provides: ${t64:Provides}
> +Breaks: libc-client2007e (<< ${source:Version})
> +Replaces: libc-client2007e
>  Section: libs
>  Architecture: any
>  Depends: ${cdbs:Depends},
> diff -Nru uw-imap-2007f~dfsg/debian/control.in 
> uw-imap-2007f~dfsg/debian/control.in
> --- uw-imap-2007f~dfsg/debian/control.in  2019-08-26 20:52:52.0 
> +
> +++ uw-imap-2007f~dfsg/debian/control.in  2024-02-25 21:19:39.0 
> +
> @@ -2,22 +2,21 @@
>  Priority: optional
>  

Bug#1064788: haproxy: installs same filename to both bin and sbin

[cacin]

Package: haproxy
Severity: normal

Dear Maintainer,

your package installs the filename halog to both bin and sbin as opposed to 
just one of those locations.

This causes a problem on a filesystem layout where bin and sbin are merged into 
a single real directory, typically by sbin being a symlink to bin. Such a 
filesystem layout has become standard on some distributions now, and others are 
moving onto in their next releases.

Please pick one location and install it only there. /usr/bin is preferred over 
any other location.

Thank you for maintaining software in debian.

Bug#1064787: courier-imap: installs same filename to both bin and sbin

[cacin]

Package: courier-imap
Severity: normal

Dear Maintainer,

your package installs the filename imapd to both bin and sbin as opposed to 
just one of those locations.

This causes a problem on a filesystem layout where bin and sbin are merged into 
a single real directory, typically by sbin being a symlink to bin. Such a 
filesystem layout has become standard on some distributions now, and others are 
moving onto in their next releases.

Please pick one location and install it only there. /usr/bin is preferred over 
any other location.

Thank you for maintaining software in debian.

Bug#1064786: jruby: mri-extra - flaky TestOpen3 pipe tests

[Vladimir Petko]

Source: jruby
Version: 9.4.5.0+ds-1
Severity: normal
X-Debbugs-Cc: vladimir.pe...@canonical.com

Dear Maintainer,

The autopkgtests for jruby fail `mri-extra` with the following errors:

  1) Failure:
TestOpen3#test_pipeline_start
[/tmp/autopkgtest.Dz4xQk/autopkgtest_tmp/test/mri/test_open3.rb:303]:
Failed assertion, no message given.

  2) Failure:
TestOpen3#test_pipeline_w
[/tmp/autopkgtest.Dz4xQk/autopkgtest_tmp/test/mri/test_open3.rb:288]:
 expected but was
.

  3) Failure:
TestOpen3#test_capture3_flip
[/tmp/autopkgtest.Dz4xQk/autopkgtest_tmp/test/mri/test_open3.rb:190]:

The minimal reproducer of those:

require 'open3'

RUBY = 'jruby'
Open3.pipeline_r([RUBY, '-e', 'print "1"'],
 [RUBY, '-e', 'print STDIN.read + "2"']) {|o,ts|
  print(o.read)
}
---

executing the above sample results in the following output:
# jruby test.rb
12# jruby test.rb
12# jruby test.rb
12# jruby test.rb
12# jruby test.rb
2# jruby test.rb
12# jruby test.rb
2# jruby test.rb
12# jruby test.rb
2# jruby test.rb
2# jruby test.rb
2# jruby test.rb
2# jruby test.rb
12# jruby test.rb
12# jruby test.rb
2Errno::EPIPE: Broken pipe - 
   write at org/jruby/RubyIO.java:1569
   write at org/jruby/RubyIO.java:1458
   write at org/jruby/RubyIO.java:2829
   print at org/jruby/RubyIO.java:1831
   print at org/jruby/RubyKernel.java:649
   at -e:1

Note: the failure occurs both with Java 17 and Java 21


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

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

Bug#1064680: subversion: FTBFS: :86:in `require': /<>/BUILD/subversion/bindings/swig/ruby/libsvn_swig_ruby/.libs/li

[James McCoy]

Control: reassign -1 swig/4.2.0-1
Control: affects -1 src:subversion
Control: forwarded -1 https://github.com/swig/swig/issues/2751
Control: retitle -1 SWIG_snprintf not defined for ruby/tcl bindings

On Sun, Feb 25, 2024 at 08:33:47PM +0100, Lucas Nussbaum wrote:
> Relevant part (hopefully):
> > make[3]: Entering directory '/<>'
> > make[3]: warning: jobserver unavailable: using -j1.  Add '+' to parent make 
> > rule.
> > if [ "LD_LIBRARY_PATH" = "DYLD_LIBRARY_PATH" ]; then for d in 
> > /<>/BUILD/subversion/bindings/swig/ruby/libsvn_swig_ruby 
> > /<>/BUILD/subversion/bindings/swig/ruby/../../../libsvn_*; do 
> > if [ -n "$DYLD_LIBRARY_PATH" ]; then 
> > LD_LIBRARY_PATH="$LD_LIBRARY_PATH:$d/.libs"; else 
> > LD_LIBRARY_PATH="$d/.libs"; fi; done; export LD_LIBRARY_PATH; fi; \
> > cd /<>/BUILD/subversion/bindings/swig/ruby; \
> >   check_rb() { \
> > /usr/bin/ruby -I 
> > /<>/BUILD/../subversion/bindings/swig/ruby 
> > /<>/BUILD/../subversion/bindings/swig/ruby/test/run-test.rb 
> > "$@"; \
> >   }; \
> >   if check_rb --help 2>&1 | grep -q -- --collector; then \
> > check_rb --collector=dir --verbose=normal; \
> >   elif [ "3" -eq 1 -a "1" -lt 9 ] ; then \
> > check_rb --verbose=normal; \
> >   else \
> > check_rb; \
> >   fi
> > :86:in
> >  `require': 
> > /<>/BUILD/subversion/bindings/swig/ruby/libsvn_swig_ruby/.libs/libsvn_swig_ruby-1.so.1:
> >  undefined symbol: SWIG_snprintf - 
> > /<>/BUILD/subversion/bindings/swig/ruby/.ext/svn/ext/core.so 
> > (LoadError)

This is a bug in the bindings generated by SWIG, which is fixed in 4.2.1
but not yet uploaded.  Reassigning.

Cheers,
-- 
James
GPG Key: 4096R/91BF BF4D 6956 BD5D F7B7  2D23 DFE6 91AE 331B A3DB

Bug#1063717: NVIDIA packages in stable-updates fix module compilation for linux 6.1.76-1

[matte . mb2006 . 9990]

On Mon, 19 Feb 2024 16:06:33 +0100 matte.mb2006.9...@gmail.com wrote:
> On Mon, 19 Feb 2024 00:18:29 +0100 Andreas Beckmann 
> wrote:
> > On 18/02/2024 17.06, matte.mb2006.9...@gmail.com wrote:
> > >>
> https://lists.debian.org/debian-stable-announce/2024/02/msg2.html
> > 
> > > The update is not yet available on my PC. I live in Italy.
> > 
> > Do you have bookworm-updates (or stable-updates) enabled in your 
> > sources.list(.d/)?
> > See detailed instructions in the announcement email linked above.
> > 
> > 
> > Andreas
> > 
> > 
> Yes.

Today I started Debian, I checked for updates and I finally got the
update.

Bug#1064785: brltty: installs same filename to both bin and sbin

[cacin]

Source: brltty
Severity: normal

Dear Maintainer,

your package installs the filename brltty to both bin and sbin as opposed to 
just one of those locations.

This causes a problem on a filesystem layout where bin and sbin are merged into 
a single real directory, typically by sbin being a symlink to bin. Such a 
filesystem layout has become standard on some distributions now, and others are 
moving onto in their next releases.

Please pick one location and install it only there. /usr/bin is preferred over 
any other location.

Thank you for maintaining software in debian.

Bug#1063040: uw-imap: NMU diff for 64-bit time_t transition

[Steve Langasek]

Control: tags -1 - pending patch

And that package built but resulted in a change to the soname of the
library.  And my attempts to fix this have also failed, because d-shlibs
--t64 support has a strict expectation of 't64' appended to the full name of
the runtime lib package as deduced from the soname, so wants
'libc-client2007et64' when we were trying for 'libc-client2007t64'.

At this point I'm bailing on trying to fix this package.  cdbs and d-shlibs
should both have been put down in favor of dh long ago.  Please find
attached my work in progress for a patch, maybe it's useful to you; but as I
can't find a solution for this that works with your tooling of choice, I am
not planning to NMU this package for the time_t transition.

If you decide that the package name 'libc-client2007et64' is acceptable, I
can update the override map for the ftp team so that the package passes the
NEW queue and we can NMU it.

Or if you work with the d-shlibs maintainer to have sensible behavior for
your package when being named 'libc-client2007t64', then this patch should
be sufficient.

But for now, dropping the pending+patch tags.

On Sat, Feb 24, 2024 at 02:40:23AM -0800, Steve Langasek wrote:
> Hello,
> 
> The package that was previously uploaded to experimental was unfortunately
> broken because we did not notice that additional changes were needed to
> debian/control.in.in.
> 
> Please find a fixed patch attached.

-- 
Steve Langasek   Give me a lever long enough and a Free OS
Debian Developer   to set it on, and I can move the world.
Ubuntu Developer   https://www.debian.org/
slanga...@ubuntu.com vor...@debian.org
diff -Nru uw-imap-2007f~dfsg/debian/changelog 
uw-imap-2007f~dfsg/debian/changelog
--- uw-imap-2007f~dfsg/debian/changelog 2019-08-26 20:52:52.0 +
+++ uw-imap-2007f~dfsg/debian/changelog 2024-02-25 21:19:39.0 +
@@ -1,3 +1,23 @@
+uw-imap (8:2007f~dfsg-7.1~exp3) experimental; urgency=medium
+
+  * Fix debian/rules to not change the upstream soname.
+  * Bump build-dependency on d-shlibs for t64 support.
+
+ -- Steve Langasek   Sun, 25 Feb 2024 21:19:39 +
+
+uw-imap (8:2007f~dfsg-7.1~exp2) experimental; urgency=medium
+
+  * Update debian/control.in.in, not just debian/control.in.
+
+ -- Steve Langasek   Sat, 24 Feb 2024 10:23:12 +
+
+uw-imap (8:2007f~dfsg-7.1~exp1) experimental; urgency=medium
+
+  * Non-maintainer upload.
+  * Rename libraries for 64-bit time_t transition.
+
+ -- Steve Langasek   Mon, 05 Feb 2024 20:18:10 +
+
 uw-imap (8:2007f~dfsg-7) unstable; urgency=low
 
   * 2014_openssl1.1.1_sni.patch (new, from Ubuntu): Use SNI when building
diff -Nru uw-imap-2007f~dfsg/debian/control uw-imap-2007f~dfsg/debian/control
--- uw-imap-2007f~dfsg/debian/control   2019-08-26 20:52:52.0 +
+++ uw-imap-2007f~dfsg/debian/control   2024-02-24 10:19:59.0 +
@@ -16,15 +16,15 @@
 Vcs-Browser: https://salsa.debian.org/holmgren/uw-imap
 Homepage: http://www.washington.edu/imap/
 
-Package: libc-client2007e-dev
+Package: libc-client2007t64-dev
 Section: libdevel
 Architecture: any
 Depends: ${devlibs:Depends},
  ${misc:Depends},
- libc-client2007e (= ${binary:Version})
+ libc-client2007t64 (= ${binary:Version})
 Conflicts: libc-client-dev
 Replaces: libc-client-dev
-Provides: libc-client-dev
+Provides: libc-client-dev, libc-client-2007e-dev (= ${binary:Version})
 Description: c-client library for mail protocols - development files
  IMAP (Internet Message Access Protocol) is a method of accessing
  electronic messages kept on a (possibly shared) mail server.
@@ -37,7 +37,10 @@
  This package contains the static c-client library and development
  headers.
 
-Package: libc-client2007e
+Package: libc-client2007t64
+Provides: ${t64:Provides}
+Breaks: libc-client2007e (<< ${source:Version})
+Replaces: libc-client2007e
 Section: libs
 Architecture: any
 Depends: ${cdbs:Depends},
diff -Nru uw-imap-2007f~dfsg/debian/control.in 
uw-imap-2007f~dfsg/debian/control.in
--- uw-imap-2007f~dfsg/debian/control.in2019-08-26 20:52:52.0 
+
+++ uw-imap-2007f~dfsg/debian/control.in2024-02-25 21:19:39.0 
+
@@ -2,22 +2,21 @@
 Priority: optional
 Section: mail
 Maintainer: Magnus Holmgren 
-Standards-Version: 3.9.8
+Standards-Version: 4.4.0
 Build-Depends: @cdbs@
-Vcs-Git: git://git.debian.org/git/collab-maint/uw-imap.git
-Vcs-Browser: http://anonscm.debian.org/gitweb/?p=collab-maint/uw-imap.git
+Vcs-Git: https://salsa.debian.org/holmgren/uw-imap.git
+Vcs-Browser: https://salsa.debian.org/holmgren/uw-imap
 Homepage: http://www.washington.edu/imap/
 
-Package: libc-client2007e-dev
+Package: libc-client2007t64-dev
 Section: libdevel
 Architecture: any
-Priority: extra
 Depends: ${devlibs:Depends},
  ${misc:Depends},
- libc-client2007e (= ${binary:Version})
+ libc-client2007t64 (= ${binary:Version})
 Conflicts: libc-client-dev
 Replaces: 

Bug#1064784: backup2l: installs same filename to both bin and sbin

[cacin]

Source: backup2l
Version: 1.6-6
Severity: normal

Dear Maintainer,

your package installs the filename backup2l to both bin and sbin as opposed to 
just one of those locations.

This causes a problem on a filesystem layout where bin and sbin are merged into 
a single real directory, typically by sbin being a symlink to bin. Such a 
filesystem layout has become standard on some distributions now, and others are 
moving onto in their next releases.

Please pick one location and install it only there. /usr/bin is preferred over 
any other location.

Thank you for maintaining software in debian.

Bug#1064782: bind9-doc: please output tags in the documentation in deterministic order.

[James Addison]

Package: bind9-doc
Version: 1:9.19.21-1
Severity: wishlist
Tags: patch upstream
User: reproducible-bui...@lists.alioth.debian.org
Usertags: randomness

Dear Maintainer,

I'm an occasional volunteer contributor to the Reproducible Builds[1] project,
and noticed recently that the bind9-doc package failed[2] an automated Debian
package build test.

>From inspecting the differences in the generated documentation, it appears that
some tag annotations (example[3]) in the source documentation are de-duplicated
in a non-deterministic manner during Sphinx documentation builds.

The cause is that the de-duplication is performed using a non-order-preserving
Python set[4] object, meaning that the resulting output documentation package
can vary at build-time.

Please find attached a patch that implements order-preserving de-duplication
of these tags.  I've confirmed that the package compiles with it applied, and
believe that it should produce deterministic tag output in the built package.

Regards,
James

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

[2] - 
https://tests.reproducible-builds.org/debian/rb-pkg/bookworm/amd64/diffoscope-results/bind9.html

[3] - 
https://sources.debian.org/src/bind9/1%3A9.18.19-1~deb12u1/doc/arm/reference.rst/#L5648

[4] - https://docs.python.org/3/library/stdtypes.html#set-types-set-frozenset
diff --git a/doc/arm/_ext/iscconf.py b/doc/arm/_ext/iscconf.py
index b5bd966e2..0b96d7bd3 100644
--- a/doc/arm/_ext/iscconf.py
+++ b/doc/arm/_ext/iscconf.py
@@ -41,12 +41,18 @@ logger = logging.getLogger(__name__)
 
 def split_csv(argument, required):
 argument = argument or ""
-outlist = list(filter(len, (s.strip() for s in argument.split(","
-if required and not outlist:
+values = list(filter(len, (s.strip() for s in argument.split(","
+if required and not values:
 raise ValueError(
 "a non-empty list required; provide at least one value or remove"
 " this option"
 )
+# Order-preserving de-duplication
+outlist, seen = list(), set()
+for value in values:
+if value not in seen:
+seen.add(value)
+outlist.append(value)
 return outlist
 
 
@@ -73,10 +79,8 @@ def domain_factory(domainname, domainlabel, todolist, 
grammar):
 
 def run(self):
 placeholder = todolist("")
-placeholder["isc_filter_tags"] = 
set(self.options.get("filter_tags", []))
-placeholder["isc_filter_blocks"] = set(
-self.options.get("filter_blocks", [])
-)
+placeholder["isc_filter_tags"] = self.options.get("filter_tags", 
[])
+placeholder["isc_filter_blocks"] = 
self.options.get("filter_blocks", [])
 return [placeholder]
 
 class ISCConfDomain(Domain):
@@ -127,7 +131,7 @@ def domain_factory(domainname, domainlabel, todolist, 
grammar):
 
 @property
 def isc_tags(self):
-return set(self.options.get("tags", []))
+return self.options.get("tags", [])
 
 @property
 def isc_short(self):

Bug#1064783: apt-listbugs: installs same filename to both bin and sbin

[cacin]

Source: apt-listbugs
Version: 0.1.41
Severity: normal

Dear Maintainer,

your package installs the filename apt-listbugs to both bin and sbin as opposed 
to just one of those locations.

This causes a problem on a filesystem layout where bin and sbin are merged into 
a single real directory, typically by sbin being a symlink to bin. Such a 
filesystem layout has become standard on some distributions now, and others are 
moving onto in their next releases.

Please pick one location and install it only there. /usr/bin is preferred over 
any other location.

Thank you for maintaining software in debian.

Bug#910605: ghostscript ships dangling symlink /usr/share/ghostscript/X.Y/Resource/CIDFSubst/DroidSansFallback.ttf

[Steven Robbins]

Hello,

I've recently adopted ghostscript, so I can't answer the direct question of 
why libgsN-common ships a dangling symlink.  I am curious what folks think of 
this.

It's not clear to me whether there are bad consequences of a dangling symlink.  
For example is it treated differently than a completely missing file?

The target of the link is shipped in package fonts-droid-fallback -- should 
the symlink be created there instead?

Other options?

Thanks,
-Steve


On Mon, 08 Oct 2018 17:59:12 +0200 Michael Prokop  wrote:
> Package: libgs9-common
> Version: 9.25~dfsg-2
> Severity: normal
> 
> Hi,
> 
> is there any specific reason why libgs9-common ships a symlink which
> is a dangling one/dead end until the fonts-droid-fallback package is
> installed?
> 
> , [ demo ]
> | root@buster-demo:~# ls -la /usr/share/ghostscript/9.25/Resource/CIDFSubst/
> | total 8
> | drwxr-xr-x  2 root root 4096 Oct  8 17:21 .
> | drwxr-xr-x 11 root root 4096 Oct  8 17:21 ..
> | lrwxrwxrwx  1 root root   58 Sep 15 14:18 DroidSansFallback.ttf -> 
../../../../fonts/truetype/droid/DroidSansFallbackFull.ttf
> | root@buster-demo:~# ls -la /usr/share/ghostscript/9.25/Resource/CIDFSubst/
DroidSansFallback.ttf
> | lrwxrwxrwx 1 root root 58 Sep 15 14:18 /usr/share/ghostscript/9.25/
Resource/CIDFSubst/DroidSansFallback.ttf -> ../../../../fonts/truetype/droid/
DroidSansFallbackFull.ttf
> | root@buster-demo:~# readlink -f /usr/share/ghostscript/9.25/Resource/
CIDFSubst/DroidSansFallback.ttf
> | root@buster-demo:~#
> |
> | root@buster-demo:~# apt-cache show libgs9-common | grep fonts-droid-
fallback
> | Recommends: fonts-droid-fallback
> `
> 
> JFTR, #613912 might be related.
> 
> regards,
> -mika-
> 
> 


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

Bug#1050677: RE: chromium: VAAPI acceleration not working on Chromium 116

[Leandro Cunha]

Hi,

On Sun, Feb 25, 2024 at 5:59 PM Andres Salomon  wrote:
>
> Hi,
>
> Can you please verify that this has been fixed since Chromium >= 118? We
> currently have Chromium 122 in unstable/testing/stable.
>
> Thanks,
> Andres
>
> On Wed, 27 Sep 2023 00:55:04 -0300 Leandro Cunha
>  wrote:
> > Hi,
> >
> > It's a problem that persists in 117 on unstable, although on the
> > Chrome unstable channel (version 118.x) it seems to be resolved.
> >
> > Graphics Feature Status
> > ===
> > *   Canvas: Hardware accelerated
> > *   Canvas out-of-process rasterization: Disabled
> > *   Direct Rendering Display Compositor: Disabled
> > *   Compositing: Hardware accelerated
> > *   Multiple Raster Threads: Enabled
> > *   OpenGL: Enabled
> > *   Rasterization: Hardware accelerated
> > *   Raw Draw: Disabled
> > *   Skia Graphite: Disabled
> > *   Video Decode: Software only. Hardware acceleration disabled
> > *   Video Encode: Software only. Hardware acceleration disabled
> > *   Vulkan: Enabled
> > *   WebGL: Hardware accelerated
> > *   WebGL2: Hardware accelerated
> > *   WebGPU: Disabled
> >
> > Driver Bug Workarounds
> > ==
> > *   adjust_src_dst_region_for_blitframebuffer
> > *   clear_uniforms_before_first_program_use
> > *   count_all_in_varyings_packing
> > *   disable_post_sub_buffers_for_onscreen_surfaces
> > *   enable_webgl_timer_query_extensions
> > *   exit_on_context_lost
> > *   msaa_is_slow
> > *   rely_on_implicit_sync_for_swap_buffers
> > *   disabled_extension_GL_KHR_blend_equation_advanced
> > *   disabled_extension_GL_KHR_blend_equation_advanced_coherent
> > *   disabled_extension_GL_MESA_framebuffer_flip_y
> >
> > Problems Detected
> > =
> > *   WebGPU has been disabled via blocklist or the command line.
> > Disabled Features: webgpu
> >
> > *   Accelerated video encode has been disabled, either via blocklist,
> > about:flags or the command line.
> > Disabled Features: video_encode
> >
> > *   Accelerated video decode has been disabled, either via blocklist,
> > about:flags or the command line.
> > Disabled Features: video_decode
> >
> > *   Clear uniforms before first program use on all platforms:
> > (http://crbug.com/124764), (http://crbug.com/349137)
> > Applied Workarounds: clear_uniforms_before_first_program_use
> >
> > *   Mesa drivers in Linux handle varyings without static use incorrectly:
> > (http://crbug.com/333885)
> > Applied Workarounds: count_all_in_varyings_packing
> >
> > *   On Intel GPUs MSAA performance is not acceptable for GPU rasterization:
> > (http://crbug.com/527565), (http://crbug.com/1298585)

This issue has been solved!

I tested a website here that needed it and it opened normally. I'm
going to close the bug, if anyone finds a problem they can reopen it
and remove it from the debbugs arquive
(https://en.wikipedia.org/wiki/Debbugs).

*   Canvas: Hardware accelerated
*   Canvas out-of-process rasterization: Disabled
*   Direct Rendering Display Compositor: Disabled
*   Compositing: Hardware accelerated
*   Multiple Raster Threads: Enabled
*   OpenGL: Enabled
*   Rasterization: Hardware accelerated on all pages
*   Raw Draw: Disabled
*   Skia Graphite: Disabled
*   Video Decode: Hardware accelerated
*   Video Encode: Software only. Hardware acceleration disabled
*   Vulkan: Disabled
*   WebGL: Hardware accelerated
*   WebGL2: Hardware accelerated
*   WebGPU: Disabled

-- 
Cheers,
Leandro Cunha
-BEGIN PGP PUBLIC KEY BLOCK-

mQINBF/gQ8gBEADHVKgoWsUWNGVvR6sMhBPUdBUEH+QALpr1QYXhetBfRwaY0HWN
pKgejHdxKO8H+kIhRMoh89CCKg3hAJ9LmOOTXkX7U5/Cya/zRMKk5zBD3rKIaugh
0XYT15Nz1jwL7TIDG25yPSloDtVgVXTep0ZzKsNYJjb4OAqa88cvUEJEhhqrldlR
gpNbkixEh5ituO8pMShEBWqLs3yt4Hr1VFWnTIm4dl/JLBHpexzubDOw/mKCTpNd
A1JGHTvce1wtJ2fMzCVzhEjd5pyjLZV/o8hVw2/ON/yXvpJuz0lV/hiW0M+cDcas
sKftErtsZpRy3wwXdkBcJt6soYuqfCHwgMfL2iC6mPviE8xWAHMOmhdC3wDskZpb
RcLfH5IMYajJAGRO/GCMcKKbq7WkEOeloivtg64xBlYuJf9aOcHKP/8R3EObiNp7
ubQAJtV3pEGD4mx1mhutFxDHB+CfnxE3dWvxZSV9y1n4UOzkDJ3kDx5Ee0MbRvJD
w6aXKc6dhYREgh7hLDcMFz+3LcBiZDLxI3g+SHe3Bl61vdsnPno+0HhCzvB+fL4S
eoy7Myfiunz9BrB2HPN+wNCT0YgV+Kv8QoDGzBwos5H1vUJSY4t59w6xoXAYUsAm
hjAM8s+rUtG40mcUWePd8kZtgE9IV1eQ+Qt8/SNpSdRnUunmIGl3JjHvEwARAQAB
tClMZWFuZHJvIEN1bmhhIDxsZWFuZHJvY3VuaGEwMTZAZ21haWwuY29tPokCTgQT
AQoAOBYhBLT5oBCvKN3HzFEPK8LZ4zKUW9A8BQJf4EPIAhsDBQsJCAcCBhUKCQgL
AgQWAgMBAh4BAheAAAoJEMLZ4zKUW9A8FjAQAKWYqiLpLUD+DLB+NSy3DI3rf9z3
k0vE7TLaEjdEM5CQWN+j4vBqMnAckdcARvSWPndTjp8K+mtFF4PyfhNbS64z/a7L
F3DdhmX73n7LKFG8Ow9NZwcrkmPwH5WcP7mXTh6R+6/+OSL/K85NB8MLlxQTJOni
julVax9JEZjwBaP2HLCu53Zq9gZcvJlXoAoTHyTxKdp8Mh8V+Qit26E78o9c6SQD
Dq9eyMRG8hYCRfreDjKceRkYHjECySlk+VoI1ssVs07Dqvxg6qSyP4RnW+1+W74C
s0yIyuC/eRJpMAf1PBQEOOrVcTfRfpN+go955t21yIAvT58vqotTM5eaqXYIQn/y
sC4lThZai/ZBZHxl5Mbv42WkkYdjisLQOCALIMBpj5nq4oh2C+kvMupcuBKfERgV
dguU51MzfQktKb6d5y777zYnDaFMQDD2IfiD/C7ln5A9LP/L54ixlA3uRmWx/yAx
/m+Zusws98j4Eq/jw5T54XW655m6lMCTE9WXLJkgxrRcEonHSllbgRSsToEmWq0Z

Bug#1050677: RE: chromium: VAAPI acceleration not working on Chromium 116

[Andres Salomon]

Hi,

Can you please verify that this has been fixed since Chromium >= 118? We 
currently have Chromium 122 in unstable/testing/stable.


Thanks,
Andres

On Wed, 27 Sep 2023 00:55:04 -0300 Leandro Cunha 
 wrote:

Hi,

It's a problem that persists in 117 on unstable, although on the
Chrome unstable channel (version 118.x) it seems to be resolved.

Graphics Feature Status
===
*   Canvas: Hardware accelerated
*   Canvas out-of-process rasterization: Disabled
*   Direct Rendering Display Compositor: Disabled
*   Compositing: Hardware accelerated
*   Multiple Raster Threads: Enabled
*   OpenGL: Enabled
*   Rasterization: Hardware accelerated
*   Raw Draw: Disabled
*   Skia Graphite: Disabled
*   Video Decode: Software only. Hardware acceleration disabled
*   Video Encode: Software only. Hardware acceleration disabled
*   Vulkan: Enabled
*   WebGL: Hardware accelerated
*   WebGL2: Hardware accelerated
*   WebGPU: Disabled

Driver Bug Workarounds
==
*   adjust_src_dst_region_for_blitframebuffer
*   clear_uniforms_before_first_program_use
*   count_all_in_varyings_packing
*   disable_post_sub_buffers_for_onscreen_surfaces
*   enable_webgl_timer_query_extensions
*   exit_on_context_lost
*   msaa_is_slow
*   rely_on_implicit_sync_for_swap_buffers
*   disabled_extension_GL_KHR_blend_equation_advanced
*   disabled_extension_GL_KHR_blend_equation_advanced_coherent
*   disabled_extension_GL_MESA_framebuffer_flip_y

Problems Detected
=
*   WebGPU has been disabled via blocklist or the command line.
Disabled Features: webgpu

*   Accelerated video encode has been disabled, either via blocklist,
about:flags or the command line.
Disabled Features: video_encode

*   Accelerated video decode has been disabled, either via blocklist,
about:flags or the command line.
Disabled Features: video_decode

*   Clear uniforms before first program use on all platforms:
(http://crbug.com/124764), (http://crbug.com/349137)
Applied Workarounds: clear_uniforms_before_first_program_use

*   Mesa drivers in Linux handle varyings without static use incorrectly:
(http://crbug.com/333885)
Applied Workarounds: count_all_in_varyings_packing

*   On Intel GPUs MSAA performance is not acceptable for GPU rasterization:
(http://crbug.com/527565), (http://crbug.com/1298585)


OpenPGP_0x645D0247C36E7637.asc
Description: OpenPGP public key


OpenPGP_signature.asc
Description: OpenPGP digital signature

Bug#1062926: stdgpu: NMU diff for 64-bit time_t transition

[Steve Langasek]

The previous patch overlooked that the variable in debian/rules affected not
only the package name, but the soname produced for the .so file.  Please
find a corrected patch attached.

Unfortunately, based on a local test stdgpu appears to have regressed in
buildability in the past 7 days.  So while I am uploading this package to
experimental, it's not clear what is required to get it building.

-- 
Steve Langasek   Give me a lever long enough and a Free OS
Debian Developer   to set it on, and I can move the world.
Ubuntu Developer   https://www.debian.org/
slanga...@ubuntu.com vor...@debian.org
diff -Nru stdgpu-1.3.0+git20220507.32e0517/debian/changelog 
stdgpu-1.3.0+git20220507.32e0517/debian/changelog
--- stdgpu-1.3.0+git20220507.32e0517/debian/changelog   2023-07-01 
21:13:20.0 +
+++ stdgpu-1.3.0+git20220507.32e0517/debian/changelog   2024-02-25 
20:41:43.0 +
@@ -1,3 +1,17 @@
+stdgpu (1.3.0+git20220507.32e0517-5.1~exp3) experimental; urgency=medium
+
+  * Fix debian/rules to not change the upstream soname.
+
+ -- Steve Langasek   Sun, 25 Feb 2024 20:41:43 +
+
+stdgpu (1.3.0+git20220507.32e0517-5.1~exp2) experimental; urgency=medium
+
+  * Non-maintainer upload.
+  * Rename libraries for 64-bit time_t transition.
+  * Fix wrong debian/control handling in previous upload.  Closes: #1063069.
+
+ -- Steve Langasek   Sun, 18 Feb 2024 00:39:25 +
+
 stdgpu (1.3.0+git20220507.32e0517-5) unstable; urgency=medium
 
   * Fix wrong alignment test to actually provoke wrong alignment
diff -Nru stdgpu-1.3.0+git20220507.32e0517/debian/control 
stdgpu-1.3.0+git20220507.32e0517/debian/control
--- stdgpu-1.3.0+git20220507.32e0517/debian/control 2023-07-01 
21:13:11.0 +
+++ stdgpu-1.3.0+git20220507.32e0517/debian/control 2024-02-18 
00:39:25.0 +
@@ -21,7 +21,11 @@
  agnostic and native algorithms that look like sequential CPU code but are
  executed in parallel on the GPU.
 
-Package: libstdgpu-openmp0d
+Package: libstdgpu-openmp0t64
+Provides: ${t64:Provides}
+X-Time64-Compat: libstdgpu-openmp0d
+Replaces: libstdgpu-openmp0d
+Breaks: libstdgpu-openmp0d (<< ${source:Version})
 Architecture: any
 Multi-Arch: same
 Depends:
@@ -40,7 +44,7 @@
 Provides: libstdgpu-dev
 Depends:
  ${misc:Depends},
- libstdgpu-openmp0d (= ${binary:Version}),
+ libstdgpu-openmp0t64 (= ${binary:Version}),
  libthrust-dev,
 Description: ${source:Synopsis} (OpenMP development headers)
  ${source:Extended-Description}
diff -Nru stdgpu-1.3.0+git20220507.32e0517/debian/libstdgpu-openmp0d.install 
stdgpu-1.3.0+git20220507.32e0517/debian/libstdgpu-openmp0d.install
--- stdgpu-1.3.0+git20220507.32e0517/debian/libstdgpu-openmp0d.install  
2023-07-01 21:13:11.0 +
+++ stdgpu-1.3.0+git20220507.32e0517/debian/libstdgpu-openmp0d.install  
1970-01-01 00:00:00.0 +
@@ -1 +0,0 @@
-usr/lib/*/lib*.so.*
diff -Nru stdgpu-1.3.0+git20220507.32e0517/debian/libstdgpu-openmp0t64.install 
stdgpu-1.3.0+git20220507.32e0517/debian/libstdgpu-openmp0t64.install
--- stdgpu-1.3.0+git20220507.32e0517/debian/libstdgpu-openmp0t64.install
1970-01-01 00:00:00.0 +
+++ stdgpu-1.3.0+git20220507.32e0517/debian/libstdgpu-openmp0t64.install
2024-02-18 00:39:25.0 +
@@ -0,0 +1 @@
+usr/lib/*/lib*.so.*
diff -Nru 
stdgpu-1.3.0+git20220507.32e0517/debian/libstdgpu-openmp0t64.lintian-overrides 
stdgpu-1.3.0+git20220507.32e0517/debian/libstdgpu-openmp0t64.lintian-overrides
--- 
stdgpu-1.3.0+git20220507.32e0517/debian/libstdgpu-openmp0t64.lintian-overrides  
1970-01-01 00:00:00.0 +
+++ 
stdgpu-1.3.0+git20220507.32e0517/debian/libstdgpu-openmp0t64.lintian-overrides  
2024-02-18 00:39:25.0 +
@@ -0,0 +1 @@
+libstdgpu-openmp0t64: package-name-doesnt-match-sonames libstdgpu-openmp0d
diff -Nru stdgpu-1.3.0+git20220507.32e0517/debian/rules 
stdgpu-1.3.0+git20220507.32e0517/debian/rules
--- stdgpu-1.3.0+git20220507.32e0517/debian/rules   2023-07-01 
21:13:11.0 +
+++ stdgpu-1.3.0+git20220507.32e0517/debian/rules   2024-02-25 
20:40:41.0 +
@@ -5,6 +5,8 @@
 BUILD_TESTS := $(if $(filter nocheck,$(DEB_BUILD_OPTIONS)),OFF,ON)
 BUILD_HIP := $(if $(filter amd64 arm64 ppc64el,$(DEB_HOST_ARCH)),ON,OFF)
 SOVERSION := 0d
+SOVERSION_ISH := 0t64
+SOVERSION_HIP := 0d
 
 %:
dh $@ --buildsystem=cmake
@@ -28,7 +30,7 @@
-DSTDGPU_BUILD_SHARED_LIBS=ON \
-DSTDGPU_BACKEND=STDGPU_BACKEND_HIP \
-DCMAKE_HIP_ARCHITECTURES=OFF \
-   -DSTDGPU_SOVERSION=$(SOVERSION) \
+   -DSTDGPU_SOVERSION=$(SOVERSION_HIP) \
-DSTDGPU_OUTPUT_NAME=stdgpu_hip
 endif
 
@@ -51,8 +53,8 @@
 endif
 
 override_dh_install:
-   dh_install --package=libstdgpu-openmp$(SOVERSION) 
--package=libstdgpu-openmp-dev --sourcedir=debian/tmp-openmp
+   dh_install 

Bug#1064780: pgpainless: fails to build from source with Java 21 due to SecurityManager UnsupportedException

[Vladimir Petko]

Dear Maintainers,

  Would it be possible to consider a merge request[1] that addresses this issue?

Best Regards,
 Vladimir.

 [1] https://salsa.debian.org/java-team/pgpainless/-/merge_requests/2

Bug#1064736: urlwatch: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p "3.12 3.11" returned exit code 13

[Maxime Werlen]

Owner: max...@werlen.fr
Control: forwarded -1 https://github.com/thp/urlwatch/pull/786

Hi,

The bug is linked to lxml > 5 where the evaluate function disappeared.
The bug is already known upstream: https://github.com/thp/urlwatch/issues/783

The fix is easy to backport, while waiting for a new upstream release. I will 
publish a new version with the patch as soon as possible.

Thanks for reporting !

Maxime

signature.asc
Description: PGP signature

Bug#1064336: python3.12: NMU diff for 64-bit time_t transition

[Steve Langasek]

Please find an updated patch.  The previous patch overlooked some
dependencies on libpython3.12 which made the packages uninstallable.  (It
also was missing Provides: on libpython3.12t64-dbg, which was the reason I
was revisiting the package.)

-- 
Steve Langasek   Give me a lever long enough and a Free OS
Debian Developer   to set it on, and I can move the world.
Ubuntu Developer   https://www.debian.org/
slanga...@ubuntu.com vor...@debian.org
diff -Nru python3.12-3.12.2/debian/changelog python3.12-3.12.2/debian/changelog
--- python3.12-3.12.2/debian/changelog  2024-02-07 20:47:03.0 +
+++ python3.12-3.12.2/debian/changelog  2024-02-25 17:51:42.0 +
@@ -1,3 +1,17 @@
+python3.12 (3.12.2-1.1~exp2) experimental; urgency=medium
+
+  * Declare X-Time64-Compat to get proper Provides:
+  * Fix overlooked dependencies that make packages uninstallable
+
+ -- Steve Langasek   Sun, 25 Feb 2024 17:51:42 +
+
+python3.12 (3.12.2-1.1~exp1) experimental; urgency=medium
+
+  * Non-maintainer upload.
+  * Rename libraries for 64-bit time_t transition.
+
+ -- Steve Langasek   Tue, 20 Feb 2024 06:20:39 +
+
 python3.12 (3.12.2-1) unstable; urgency=medium
 
   * Python 3.12.2 release.
diff -Nru python3.12-3.12.2/debian/control python3.12-3.12.2/debian/control
--- python3.12-3.12.2/debian/control2023-12-08 19:28:58.0 +
+++ python3.12-3.12.2/debian/control2024-02-25 17:51:42.0 +
@@ -116,7 +116,10 @@
  This package contains some essential modules. It is normally not
  used on it's own, but as a dependency of python3.12-minimal.
 
-Package: libpython3.12
+Package: libpython3.12t64
+Provides: ${t64:Provides}
+Replaces: libpython3.12
+Breaks: libpython3.12 (<< ${source:Version})
 Architecture: any
 Multi-Arch: same
 Section: libs
@@ -143,7 +146,7 @@
 Multi-Arch: allowed
 Depends: python3.12 (= ${binary:Version}),
   libpython3.12-dev (= ${binary:Version}),
-  libpython3.12 (= ${binary:Version}),
+  libpython3.12t64 (= ${binary:Version}),
   ${shlibs:Depends}, ${misc:Depends}
 Recommends: libc6-dev | libc-dev
 Description: Header files and a static library for Python (v3.12)
@@ -159,7 +162,7 @@
 Multi-Arch: same
 Pre-Depends: ${misc:Pre-Depends}
 Depends: libpython3.12-stdlib (= ${binary:Version}),
-  libpython3.12 (= ${binary:Version}),
+  libpython3.12t64 (= ${binary:Version}),
   libexpat1-dev, zlib1g-dev,
   ${shlibs:Depends}, ${misc:Depends}
 Recommends: libc6-dev | libc-dev
@@ -221,7 +224,7 @@
 Section: debug
 Architecture: any
 Multi-Arch: allowed
-Depends: python3.12 (= ${binary:Version}), libpython3.12-dbg (= 
${binary:Version}), ${shlibs:Depends}, ${misc:Depends}
+Depends: python3.12 (= ${binary:Version}), libpython3.12t64-dbg (= 
${binary:Version}), ${shlibs:Depends}, ${misc:Depends}
 Recommends: gdb
 Suggests: python3-gdbm-dbg, python3-tk-dbg
 Description: Debug Build of the Python Interpreter (version 3.12)
@@ -234,14 +237,16 @@
  .
  See the README.debug for more information.
 
-Package: libpython3.12-dbg
+Package: libpython3.12t64-dbg
+X-Time64-Compat: libpython3.12-dbg
+Provides: ${t64:Provides}
 Section: debug
 Architecture: any
 Multi-Arch: same
 Pre-Depends: ${misc:Pre-Depends}
 Depends: libpython3.12-stdlib (= ${binary:Version}), ${shlibs:Depends}, 
${misc:Depends}
-Breaks: python3-gdbm-dbg (<< 3.9.9-1~)
-Replaces: python3-gdbm-dbg (<< 3.9.9-1~)
+Breaks: libpython3.12-dbg (<< ${source:Version}), python3-gdbm-dbg (<< 
3.9.9-1~)
+Replaces: libpython3.12-dbg, python3-gdbm-dbg (<< 3.9.9-1~)
 Description: Debug Build of the Python Interpreter (version 3.12)
  The package holds two things:
  .
diff -Nru python3.12-3.12.2/debian/control.in 
python3.12-3.12.2/debian/control.in
--- python3.12-3.12.2/debian/control.in 2023-12-08 19:28:48.0 +
+++ python3.12-3.12.2/debian/control.in 2024-02-25 17:51:27.0 +
@@ -116,7 +116,10 @@
  This package contains some essential modules. It is normally not
  used on it's own, but as a dependency of @PVER@-minimal.
 
-Package: lib@PVER@
+Package: lib@PVER@t64
+Provides: ${t64:Provides}
+Replaces: lib@PVER@
+Breaks: lib@PVER@ (<< ${source:Version})
 Architecture: any
 Multi-Arch: same
 Section: libs
@@ -143,7 +146,7 @@
 Multi-Arch: allowed
 Depends: @PVER@ (= ${binary:Version}),
   lib@PVER@-dev (= ${binary:Version}),
-  lib@PVER@ (= ${binary:Version}),
+  lib@PVER@t64 (= ${binary:Version}),
   ${shlibs:Depends}, ${misc:Depends}
 Recommends: libc6-dev | libc-dev
 Description: Header files and a static library for Python (v@VER@)
@@ -159,7 +162,7 @@
 Multi-Arch: same
 Pre-Depends: ${misc:Pre-Depends}
 Depends: lib@PVER@-stdlib (= ${binary:Version}),
-  lib@PVER@ (= ${binary:Version}),
+  lib@PVER@t64 (= ${binary:Version}),
   libexpat1-dev, zlib1g-dev,
   ${shlibs:Depends}, ${misc:Depends}
 Recommends: libc6-dev | libc-dev
@@ -221,7 +224,7 @@
 Section: debug
 Architecture: any
 Multi-Arch: allowed
-Depends: 

Bug#1064781: php-dompdf-svg-lib: CVE-2024-25117

[Salvatore Bonaccorso]

Source: php-dompdf-svg-lib
Version: 0.5.1-1
Severity: important
Tags: security upstream
X-Debbugs-Cc: car...@debian.org, Debian Security Team 

Hi,

The following vulnerability was published for php-dompdf-svg-lib.

CVE-2024-25117[0]:
| php-svg-lib is a scalable vector graphics (SVG) file
| parsing/rendering library. Prior to version 0.5.2, php-svg-lib fails
| to validate that font-family doesn't contain a PHAR url, which might
| leads to RCE on PHP < 8.0, and doesn't validate if external
| references are allowed. This might leads to bypass of restrictions
| or RCE on projects that are using it, if they do not strictly
| revalidate the fontName that is passed by php-svg-lib. The
| `Style::fromAttributes(`), or the `Style::parseCssStyle()` should
| check the content of the `font-family` and prevents it to use a PHAR
| url, to avoid passing an invalid and dangerous `fontName` value to
| other libraries. The same check as done in the
| `Style::fromStyleSheets` might be reused. Libraries using this
| library as a dependency might be vulnerable to some bypass of
| restrictions, or even remote code execution, if they do not double
| check the value of the `fontName` that is passed by php-svg-lib.
| Version 0.5.2 contains a fix for this issue.


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-2024-25117
https://www.cve.org/CVERecord?id=CVE-2024-25117
[1] 
https://github.com/dompdf/php-svg-lib/security/advisories/GHSA-f3qr-qr4x-j273
[2] 
https://github.com/dompdf/php-svg-lib/commit/732faa9fb4309221e2bd9b2fda5de44f947133aa
[3] 
https://github.com/dompdf/php-svg-lib/commit/8ffcc41bbde39f09f94b9760768086f12bbdce42

Please adjust the affected versions in the BTS as needed.

Regards,
Salvatore

Bug#1064780: pgpainless: fails to build from source with Java 21 due to SecurityManager UnsupportedException

[Vladimir Petko]

Source: pgpainless
Version: 1.6.6-1
Severity: important
Tags: ftbfs
User: debian-j...@lists.debian.org
Usertags: default-java21
X-Debbugs-Cc: vladimir.pe...@canonical.com

Dear Maintainer,

The package fails to build from source due to the exception during tests:

   JUnit
Jupiter:SignUsingPublicKeyBehaviorTest:testSignatureCreationAndVerification()
 MethodSource [className =
'org.pgpainless.cli.misc.SignUsingPublicKeyBehaviorTest', methodName =
'testSignatureCreationAndVerification', methodParameterTypes = '']
 => java.lang.UnsupportedOperationException: The Security Manager is
deprecated and will be removed in a future release
java.base/java.lang.System.setSecurityManager(System.java:430)
com.ginsberg.junit.exit.SystemExitExtension.beforeEach(SystemExitExtension.java:95)
java.base/java.util.ArrayList.forEach(ArrayList.java:1596)
java.base/java.util.ArrayList.forEach(ArrayList.java:1596)
Suppressed: org.opentest4j.AssertionFailedError: Expected
System.exit(79) to be called, but it was not. ==> expected: <79> but was:

com.ginsberg.junit.exit.SystemExitExtension.afterEach(SystemExitExtension.java:67)
  [...]

The tests need to run with -Djava.security.manager=allow for the junit
SystemExit extension to work.




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

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

Bug#1064779: Package: vim-python-jedi

[jean pierre pinson]

Package: vim-python-jedi
Version: 0.18.2-1

Apparently there's a bug when the directory

/usr/share/vim/vimfiles/pack/dist-bundle doesn't exist,

i have installed vim-python-jedi (0.18.2-1).

Bug#1059995: pdns: flaky autopkgtest (host dependent): pdns.service: Failed to set up IPC namespacing: Resource temporarily unavailable

[Paul Gevers]

Hi,

On Fri, 26 Jan 2024 11:31:37 +0100 Chris Hofstaedtler  
wrote:

Paul Gevers noted that src:pdns's autopkgtests fail every so often
on a large amd64 debci worker and on s390x workers. Apparently a
similar problem can be seen in src:pdns-recursor's debci runs.


The issue (or at least some issue) seems to be kernel related. Due to 
issues with the backports kernel on arm64, we had to revert to the 
bookworm kernel and now pdns fails on arm64 too. On ppc64el and riscv64 
the test passes for the last two months, both run a newer kernel 
(backports or even sid). However, s390x also runs a backports kernel and 
the issue still exists there.


Paul
By the way, if you want to use "exit 77" when conditions are not met, 
you also need to set the skippable restriction on those tests, otherwise 
the exit code is used like any other.


OpenPGP_signature.asc
Description: OpenPGP digital signature

Bug#1064778: python-cryptography: CVE-2024-26130

[Salvatore Bonaccorso]

Source: python-cryptography
Version: 41.0.7-3
Severity: important
Tags: security upstream
Forwarded: https://github.com/pyca/cryptography/pull/10423
X-Debbugs-Cc: car...@debian.org, Debian Security Team 

Hi,

The following vulnerability was published for python-cryptography.

CVE-2024-26130[0]:
| cryptography is a package designed to expose cryptographic
| primitives and recipes to Python developers. Starting in version
| 38.0.0 and prior to version 42.0.4, if
| `pkcs12.serialize_key_and_certificates` is called with both a
| certificate whose public key did not match the provided private key
| and an `encryption_algorithm` with `hmac_hash` set (via
| `PrivateFormat.PKCS12.encryption_builder().hmac_hash(...)`, then a
| NULL pointer dereference would occur, crashing the Python process.
| This has been resolved in version 42.0.4, the first version in which
| a `ValueError` is properly raised.


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-2024-26130
https://www.cve.org/CVERecord?id=CVE-2024-26130
[1] https://github.com/pyca/cryptography/pull/10423
[2] https://github.com/pyca/cryptography/security/advisories/GHSA-6vqw-3v5j-54x4

Please adjust the affected versions in the BTS as needed.

Regards,
Salvatore

Bug#1064775: python-pycdlib: FTBFS: failed tests

[Lucas Nussbaum]

Source: python-pycdlib
Version: 1.12.0+ds1-5
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20240224 ftbfs-trixie

Hi,

During a rebuild of all packages in sid, your package failed to build
on amd64.


Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> make[1]: pyversions: No such file or directory
> py3versions: no X-Python3-Version in control file, using supported versions
> pkgos-dh_auto_install --no-py2 --in-tmp
> + PKGOS_IN_TMP=no
> + echo WARNING: --no-py2 is deprecated and always on.
> WARNING: --no-py2 is deprecated and always on.
> + shift
> + PKGOS_IN_TMP=yes
> + shift
> + dpkg-parsechangelog -SSource
> + SRC_PKG_NAME=python-pycdlib
> + + sed s/python-//
> echo python-pycdlib
> + PY_MODULE_NAME=pycdlib
> + py3versions -vr
> + PYTHON3S=3.12 3.11
> + [ yes = yes ]
> + TARGET_DIR=tmp
> + pwd
> + python3.12 setup.py install --install-layout=deb --root 
> /<>/debian/tmp
> running install
> /usr/lib/python3/dist-packages/setuptools/_distutils/cmd.py:66: 
> SetuptoolsDeprecationWarning: setup.py install is deprecated.
> !!
> 
> 
> 
> Please avoid running ``setup.py`` directly.
> Instead, use pypa/build, pypa/installer or other
> standards-based tools.
> 
> See https://blog.ganssle.io/articles/2021/10/setup-py-deprecated.html 
> for details.
> 
> 
> 
> !!
>   self.initialize_options()
> running build
> running build_py
> creating build
> creating build/lib
> creating build/lib/pycdlib
> copying pycdlib/utils.py -> build/lib/pycdlib
> copying pycdlib/__init__.py -> build/lib/pycdlib
> copying pycdlib/rockridge.py -> build/lib/pycdlib
> copying pycdlib/backport_functools.py -> build/lib/pycdlib
> copying pycdlib/path_table_record.py -> build/lib/pycdlib
> copying pycdlib/eltorito.py -> build/lib/pycdlib
> copying pycdlib/pycdlibexception.py -> build/lib/pycdlib
> copying pycdlib/inode.py -> build/lib/pycdlib
> copying pycdlib/dates.py -> build/lib/pycdlib
> copying pycdlib/pycdlib.py -> build/lib/pycdlib
> copying pycdlib/isohybrid.py -> build/lib/pycdlib
> copying pycdlib/udf.py -> build/lib/pycdlib
> copying pycdlib/facade.py -> build/lib/pycdlib
> copying pycdlib/pycdlibio.py -> build/lib/pycdlib
> copying pycdlib/headervd.py -> build/lib/pycdlib
> copying pycdlib/dr.py -> build/lib/pycdlib
> running build_scripts
> creating build/scripts-3.12
> copying and adjusting tools/pycdlib-explorer -> build/scripts-3.12
> copying and adjusting tools/pycdlib-extract-files -> build/scripts-3.12
> copying and adjusting tools/pycdlib-genisoimage -> build/scripts-3.12
> changing mode of build/scripts-3.12/pycdlib-explorer from 644 to 755
> changing mode of build/scripts-3.12/pycdlib-extract-files from 644 to 755
> changing mode of build/scripts-3.12/pycdlib-genisoimage from 644 to 755
> running install_lib
> creating /<>/debian/tmp
> creating /<>/debian/tmp/usr
> creating /<>/debian/tmp/usr/lib
> creating /<>/debian/tmp/usr/lib/python3
> creating /<>/debian/tmp/usr/lib/python3/dist-packages
> creating /<>/debian/tmp/usr/lib/python3/dist-packages/pycdlib
> copying build/lib/pycdlib/utils.py -> 
> /<>/debian/tmp/usr/lib/python3/dist-packages/pycdlib
> copying build/lib/pycdlib/__init__.py -> 
> /<>/debian/tmp/usr/lib/python3/dist-packages/pycdlib
> copying build/lib/pycdlib/rockridge.py -> 
> /<>/debian/tmp/usr/lib/python3/dist-packages/pycdlib
> copying build/lib/pycdlib/backport_functools.py -> 
> /<>/debian/tmp/usr/lib/python3/dist-packages/pycdlib
> copying build/lib/pycdlib/path_table_record.py -> 
> /<>/debian/tmp/usr/lib/python3/dist-packages/pycdlib
> copying build/lib/pycdlib/eltorito.py -> 
> /<>/debian/tmp/usr/lib/python3/dist-packages/pycdlib
> copying build/lib/pycdlib/pycdlibexception.py -> 
> /<>/debian/tmp/usr/lib/python3/dist-packages/pycdlib
> copying build/lib/pycdlib/inode.py -> 
> /<>/debian/tmp/usr/lib/python3/dist-packages/pycdlib
> copying build/lib/pycdlib/dates.py -> 
> /<>/debian/tmp/usr/lib/python3/dist-packages/pycdlib
> copying build/lib/pycdlib/pycdlib.py -> 
> /<>/debian/tmp/usr/lib/python3/dist-packages/pycdlib
> copying build/lib/pycdlib/isohybrid.py -> 
> /<>/debian/tmp/usr/lib/python3/dist-packages/pycdlib
> copying build/lib/pycdlib/udf.py -> 
> /<>/debian/tmp/usr/lib/python3/dist-packages/pycdlib
> copying build/lib/pycdlib/facade.py -> 
> /<>/debian/tmp/usr/lib/python3/dist-packages/pycdlib
> copying build/lib/pycdlib/pycdlibio.py -> 
> /<>/debian/tmp/usr/lib/python3/dist-packages/pycdlib
> copying build/lib/pycdlib/headervd.py -> 
> /<>/debian/tmp/usr/lib/python3/dist-packages/pycdlib
> copying build/lib/pycdlib/dr.py -> 
> /<>/debian/tmp/usr/lib/python3/dist-packages/pycdlib
> byte-compiling 
> /<>/debian/tmp/usr/lib/python3/dist-packages/pycdlib/utils.py to 
> utils.cpython-312.pyc
> byte-compiling 
> 

Bug#1064776: bogusly redirects Bugs to debian-openoff...@lists.debian.org instead of the BTS

[Rene Engelhard]

Source: libreoffice

Version: 4:24.2.0-1

Severity: serious

Control: close -1 4:24.2.0-3


Am 23.02.24 um 17:14 schrieb Rene Engelhard:

Hi,

Am 23.02.24 um 08:02 schrieb HIGUCHI Daisuke (VDR dai):

Sorry, resending to BTS, not to debian-openoffice.


No problem, that -1 redirects the bug reports to debian-openoffice is 
a bug.


(Fixed in later versions but those are stuck after the t64 transition.)


Making a (RC) bug out of this.


Regards,


Rene

Bug#1064774: jenkins-job-builder: FTBFS: stestr fails directory

[Lucas Nussbaum]

Source: jenkins-job-builder
Version: 3.11.0-6
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20240224 ftbfs-trixie

Hi,

During a rebuild of all packages in sid, your package failed to build
on amd64.


Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> make[1]: pyversions: No such file or directory
> py3versions: no X-Python3-Version in control file, using supported versions
> PYBUILD_SYSTEM=custom dh_auto_test
> I: pybuild base:305: PYTHON=python3.12 stestr run --subunit 
> 'tests\.(?!cmd\.test_config\.TestConfigs\.test_use_global_config|cmd\.test_config\.TestConfigs\.test_use_config_in_user_home|moduleregistry\.test_moduleregistry\.ModuleRegistryPluginInfoTestsWithScenarios\.test_plugin_version_comparison)'
> stestr: 'run --subunit 
> tests\.(?!cmd\.test_config\.TestConfigs\.test_use_global_config|cmd\.test_config\.TestConfigs\.test_use_config_in_user_home|moduleregistry\.test_moduleregistry\.ModuleRegistryPluginInfoTestsWithScenarios\.test_plugin_version_comparison)'
>  is not a stestr command. See 'stestr --help'.
> Did you mean one of these?
>   help
> E: pybuild pybuild:391: test: plugin custom failed with: exit code=2: 
> PYTHON=python3.12 stestr run --subunit 
> 'tests\.(?!cmd\.test_config\.TestConfigs\.test_use_global_config|cmd\.test_config\.TestConfigs\.test_use_config_in_user_home|moduleregistry\.test_moduleregistry\.ModuleRegistryPluginInfoTestsWithScenarios\.test_plugin_version_comparison)'
> I: pybuild base:305: PYTHON=python3.11 stestr run --subunit 
> 'tests\.(?!cmd\.test_config\.TestConfigs\.test_use_global_config|cmd\.test_config\.TestConfigs\.test_use_config_in_user_home|moduleregistry\.test_moduleregistry\.ModuleRegistryPluginInfoTestsWithScenarios\.test_plugin_version_comparison)'
> stestr: 'run --subunit 
> tests\.(?!cmd\.test_config\.TestConfigs\.test_use_global_config|cmd\.test_config\.TestConfigs\.test_use_config_in_user_home|moduleregistry\.test_moduleregistry\.ModuleRegistryPluginInfoTestsWithScenarios\.test_plugin_version_comparison)'
>  is not a stestr command. See 'stestr --help'.
> Did you mean one of these?
>   help
> E: pybuild pybuild:391: test: plugin custom failed with: exit code=2: 
> PYTHON=python3.11 stestr run --subunit 
> 'tests\.(?!cmd\.test_config\.TestConfigs\.test_use_global_config|cmd\.test_config\.TestConfigs\.test_use_config_in_user_home|moduleregistry\.test_moduleregistry\.ModuleRegistryPluginInfoTestsWithScenarios\.test_plugin_version_comparison)'
> dh_auto_test: error: pybuild --test -i python{version} -p "3.12 3.11" 
> returned exit code 13


The full build log is available from:
http://qa-logs.debian.net/2024/02/24/jenkins-job-builder_3.11.0-6_unstable.log

All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20240224;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20240224=lu...@debian.org=1=1=1=1#results

A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!

If you reassign this bug to another package, please mark it as 'affects'-ing
this package. See https://www.debian.org/Bugs/server-control#affects

If you fail to reproduce this, please provide a build log and diff it with mine
so that we can identify if something relevant changed in the meantime.

Bug#1064773: chemicaltagger: FTBFS: [ERROR] Plugin org.antlr:antlr4-maven-plugin:4.7.2 or one of its dependencies could not be resolved: Cannot access central (https://repo.maven.apache.org/maven2) in

[Lucas Nussbaum]

Source: chemicaltagger
Version: 1.6.2-2
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20240224 ftbfs-trixie

Hi,

During a rebuild of all packages in sid, your package failed to build
on amd64.


Relevant part (hopefully):
>  debian/rules binary
> dh binary
>dh_update_autotools_config
>dh_autoreconf
>dh_auto_configure
>   mh_patchpoms -plibchemicaltagger-java --debian-build --keep-pom-version 
> --maven-repo=/<>/debian/maven-repo
>dh_auto_build
>   /usr/lib/jvm/default-java/bin/java -noverify -cp 
> /usr/share/maven/boot/plexus-classworlds-2.x.jar 
> -Dmaven.home=/usr/share/maven 
> -Dmaven.multiModuleProjectDirectory=/<> 
> -Dclassworlds.conf=/etc/maven/m2-debian.conf 
> -Dproperties.file.manual=/<>/debian/maven.properties 
> org.codehaus.plexus.classworlds.launcher.Launcher 
> -s/etc/maven/settings-debian.xml -Ddebian.dir=/<>/debian 
> -Dmaven.repo.local=/<>/debian/maven-repo --batch-mode package 
> -DskipTests -Dnotimestamp=true -Dlocale=en_US
> OpenJDK 64-Bit Server VM warning: Options -Xverify:none and -noverify were 
> deprecated in JDK 13 and will likely be removed in a future release.
> [INFO] Scanning for projects...
> [INFO] 
> [INFO] --< uk.ac.cam.ch.wwmm:chemicalTagger 
> >--
> [INFO] Building chemicalTagger 1.6.2
> [INFO] [ jar 
> ]-
> [WARNING] The POM for org.antlr:antlr4-maven-plugin:jar:4.7.2 is missing, no 
> dependency information available
> [INFO] 
> 
> [INFO] BUILD FAILURE
> [INFO] 
> 
> [INFO] Total time:  0.105 s
> [INFO] Finished at: 2024-02-24T22:51:03Z
> [INFO] 
> 
> [ERROR] Plugin org.antlr:antlr4-maven-plugin:4.7.2 or one of its dependencies 
> could not be resolved: Cannot access central 
> (https://repo.maven.apache.org/maven2) in offline mode and the artifact 
> org.antlr:antlr4-maven-plugin:jar:4.7.2 has not been downloaded from it 
> before. -> [Help 1]
> [ERROR] 
> [ERROR] To see the full stack trace of the errors, re-run Maven with the -e 
> switch.
> [ERROR] Re-run Maven using the -X switch to enable full debug logging.
> [ERROR] 
> [ERROR] For more information about the errors and possible solutions, please 
> read the following articles:
> [ERROR] [Help 1] 
> http://cwiki.apache.org/confluence/display/MAVEN/PluginResolutionException
> dh_auto_build: error: /usr/lib/jvm/default-java/bin/java -noverify -cp 
> /usr/share/maven/boot/plexus-classworlds-2.x.jar 
> -Dmaven.home=/usr/share/maven 
> -Dmaven.multiModuleProjectDirectory=/<> 
> -Dclassworlds.conf=/etc/maven/m2-debian.conf 
> -Dproperties.file.manual=/<>/debian/maven.properties 
> org.codehaus.plexus.classworlds.launcher.Launcher 
> -s/etc/maven/settings-debian.xml -Ddebian.dir=/<>/debian 
> -Dmaven.repo.local=/<>/debian/maven-repo --batch-mode package 
> -DskipTests -Dnotimestamp=true -Dlocale=en_US returned exit code 1
> make: *** [debian/rules:4: binary] Error 25


The full build log is available from:
http://qa-logs.debian.net/2024/02/24/chemicaltagger_1.6.2-2_unstable.log

All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20240224;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20240224=lu...@debian.org=1=1=1=1#results

A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!

If you reassign this bug to another package, please mark it as 'affects'-ing
this package. See https://www.debian.org/Bugs/server-control#affects

If you fail to reproduce this, please provide a build log and diff it with mine
so that we can identify if something relevant changed in the meantime.

Bug#1064772: pymupdf: FTBFS: fitz.i.c:3343:5: error: conflicting types for ‘fz_pixmap_size’; have ‘int(fz_context *, fz_pixmap *)’

[Lucas Nussbaum]

Source: pymupdf
Version: 1.23.7+ds1-1
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20240224 ftbfs-trixie

Hi,

During a rebuild of all packages in sid, your package failed to build
on amd64.


Relevant part (hopefully):
>  debian/rules binary
> dh binary --buildsystem=pybuild --with python3
>dh_update_autotools_config -O--buildsystem=pybuild
>dh_autoreconf -O--buildsystem=pybuild
>dh_auto_configure -O--buildsystem=pybuild
>dh_auto_build -O--buildsystem=pybuild
> I: pybuild plugin_pyproject:129: Building wheel for python3.12 with "build" 
> module
> I: pybuild base:305: python3.12 -m build --skip-dependency-check 
> --no-isolation --wheel --outdir /<>/.pybuild/cpython3_3.12  
> * Building wheel...
> /<>/wdev.py:15: SyntaxWarning: invalid escape sequence '\P'
>   '''
> pymupdf-1.23.7+ds1/setup.py: ### Starting.
> pymupdf-1.23.7+ds1/setup.py: __name__: 'setup'
> pymupdf-1.23.7+ds1/setup.py: platform.platform(): 
> 'Linux-6.1.0-13-cloud-amd64-x86_64-with-glibc2.37'
> pymupdf-1.23.7+ds1/setup.py: platform.python_version(): '3.12.2'
> pymupdf-1.23.7+ds1/setup.py: sys.executable: '/usr/bin/python3.12'
> pymupdf-1.23.7+ds1/setup.py: CPU bits: 64 sys.maxsize=9223372036854775807
> pymupdf-1.23.7+ds1/setup.py: __file__: '/<>/setup.py'
> pymupdf-1.23.7+ds1/setup.py: os.getcwd(): '/<>'
> pymupdf-1.23.7+ds1/setup.py: sys.argv (3):
> pymupdf-1.23.7+ds1/setup.py: 0: 
> '/usr/lib/python3/dist-packages/pyproject_hooks/_in_process/_in_process.py'
> pymupdf-1.23.7+ds1/setup.py: 1: 'build_wheel'
> pymupdf-1.23.7+ds1/setup.py: 2: '/tmp/tmpylrv9ok9'
> pymupdf-1.23.7+ds1/setup.py: os.environ (92):
> pymupdf-1.23.7+ds1/setup.py: APT_CONFIG: '/var/lib/sbuild/apt.conf'
> pymupdf-1.23.7+ds1/setup.py: ASFLAGS: ''
> pymupdf-1.23.7+ds1/setup.py: ASFLAGS_FOR_BUILD: ''
> pymupdf-1.23.7+ds1/setup.py: CCACHE_DIR: 
> '/<>/.pybuild/ccache'
> pymupdf-1.23.7+ds1/setup.py: CFLAGS: '-g -O2 
> -ffile-prefix-map=/<>=. -fstack-protector-strong 
> -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection'
> pymupdf-1.23.7+ds1/setup.py: CFLAGS_FOR_BUILD: '-g -O2'
> pymupdf-1.23.7+ds1/setup.py: CPPFLAGS: '-Wdate-time -D_FORTIFY_SOURCE=2'
> pymupdf-1.23.7+ds1/setup.py: CPPFLAGS_FOR_BUILD: ''
> pymupdf-1.23.7+ds1/setup.py: CXXFLAGS: '-g -O2 
> -ffile-prefix-map=/<>=. -fstack-protector-strong 
> -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection'
> pymupdf-1.23.7+ds1/setup.py: CXXFLAGS_FOR_BUILD: '-g -O2'
> pymupdf-1.23.7+ds1/setup.py: DEB_BUILD_ARCH: 'amd64'
> pymupdf-1.23.7+ds1/setup.py: DEB_BUILD_ARCH_ABI: 'base'
> pymupdf-1.23.7+ds1/setup.py: DEB_BUILD_ARCH_BITS: '64'
> pymupdf-1.23.7+ds1/setup.py: DEB_BUILD_ARCH_CPU: 'amd64'
> pymupdf-1.23.7+ds1/setup.py: DEB_BUILD_ARCH_ENDIAN: 'little'
> pymupdf-1.23.7+ds1/setup.py: DEB_BUILD_ARCH_LIBC: 'gnu'
> pymupdf-1.23.7+ds1/setup.py: DEB_BUILD_ARCH_OS: 'linux'
> pymupdf-1.23.7+ds1/setup.py: DEB_BUILD_GNU_CPU: 'x86_64'
> pymupdf-1.23.7+ds1/setup.py: DEB_BUILD_GNU_SYSTEM: 'linux-gnu'
> pymupdf-1.23.7+ds1/setup.py: DEB_BUILD_GNU_TYPE: 'x86_64-linux-gnu'
> pymupdf-1.23.7+ds1/setup.py: DEB_BUILD_MAINT_OPTIONS: 'hardening=+all'
> pymupdf-1.23.7+ds1/setup.py: DEB_BUILD_MULTIARCH: 'x86_64-linux-gnu'
> pymupdf-1.23.7+ds1/setup.py: DEB_BUILD_OPTIONS: 'parallel=8'
> pymupdf-1.23.7+ds1/setup.py: DEB_HOST_ARCH: 'amd64'
> pymupdf-1.23.7+ds1/setup.py: DEB_HOST_ARCH_ABI: 'base'
> pymupdf-1.23.7+ds1/setup.py: DEB_HOST_ARCH_BITS: '64'
> pymupdf-1.23.7+ds1/setup.py: DEB_HOST_ARCH_CPU: 'amd64'
> pymupdf-1.23.7+ds1/setup.py: DEB_HOST_ARCH_ENDIAN: 'little'
> pymupdf-1.23.7+ds1/setup.py: DEB_HOST_ARCH_LIBC: 'gnu'
> pymupdf-1.23.7+ds1/setup.py: DEB_HOST_ARCH_OS: 'linux'
> pymupdf-1.23.7+ds1/setup.py: DEB_HOST_GNU_CPU: 'x86_64'
> pymupdf-1.23.7+ds1/setup.py: DEB_HOST_GNU_SYSTEM: 'linux-gnu'
> pymupdf-1.23.7+ds1/setup.py: DEB_HOST_GNU_TYPE: 'x86_64-linux-gnu'
> pymupdf-1.23.7+ds1/setup.py: DEB_HOST_MULTIARCH: 'x86_64-linux-gnu'
> pymupdf-1.23.7+ds1/setup.py: DEB_PYTHON_INSTALL_LAYOUT: 'deb'
> pymupdf-1.23.7+ds1/setup.py: DEB_RULES_REQUIRES_ROOT: 'no'
> pymupdf-1.23.7+ds1/setup.py: DEB_TARGET_ARCH: 'amd64'
> pymupdf-1.23.7+ds1/setup.py: DEB_TARGET_ARCH_ABI: 'base'
> pymupdf-1.23.7+ds1/setup.py: DEB_TARGET_ARCH_BITS: '64'
> pymupdf-1.23.7+ds1/setup.py: DEB_TARGET_ARCH_CPU: 'amd64'
> pymupdf-1.23.7+ds1/setup.py: DEB_TARGET_ARCH_ENDIAN: 'little'
> pymupdf-1.23.7+ds1/setup.py: DEB_TARGET_ARCH_LIBC: 'gnu'
> pymupdf-1.23.7+ds1/setup.py: DEB_TARGET_ARCH_OS: 'linux'
> pymupdf-1.23.7+ds1/setup.py: DEB_TARGET_GNU_CPU: 'x86_64'
> pymupdf-1.23.7+ds1/setup.py: DEB_TARGET_GNU_SYSTEM: 'linux-gnu'
> pymupdf-1.23.7+ds1/setup.py: DEB_TARGET_GNU_TYPE: 'x86_64-linux-gnu'
> pymupdf-1.23.7+ds1/setup.py: DEB_TARGET_MULTIARCH: 'x86_64-linux-gnu'
> 

Bug#1064770: hugo: FTBFS: make[1]: *** [debian/rules:89: override_dh_auto_build] Error 25

[Lucas Nussbaum]

Source: hugo
Version: 0.122.0-1
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20240224 ftbfs-trixie

Hi,

During a rebuild of all packages in sid, your package failed to build
on amd64.


Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> go is /usr/bin/go
> go version go1.21.7 linux/amd64
> dh_auto_build -- -ldflags '-X 
> "github.com/gohugoio/hugo/common/hugo.buildDate=2024-02-04T14:35:47Z" -X 
> "github.com/gohugoio/hugo/common/hugo.vendorInfo=debian:0.122.0-1"' -tags 
> 'dev extended'
>   cd _build && go install -trimpath -v -p 8 -ldflags "-X 
> \"github.com/gohugoio/hugo/common/hugo.buildDate=2024-02-04T14:35:47Z\" -X 
> \"github.com/gohugoio/hugo/common/hugo.vendorInfo=debian:0.122.0-1\"" -tags 
> "dev extended" github.com/gohugoio/hugo github.com/gohugoio/hugo/bufferpool 
> github.com/gohugoio/hugo/cache github.com/gohugoio/hugo/cache/filecache 
> github.com/gohugoio/hugo/cache/namedmemcache github.com/gohugoio/hugo/codegen 
> github.com/gohugoio/hugo/commands github.com/gohugoio/hugo/common 
> github.com/gohugoio/hugo/common/collections 
> github.com/gohugoio/hugo/common/constants 
> github.com/gohugoio/hugo/common/herrors github.com/gohugoio/hugo/common/hexec 
> github.com/gohugoio/hugo/common/hreflect 
> github.com/gohugoio/hugo/common/hstrings 
> github.com/gohugoio/hugo/common/htime github.com/gohugoio/hugo/common/hugio 
> github.com/gohugoio/hugo/common/hugo github.com/gohugoio/hugo/common/loggers 
> github.com/gohugoio/hugo/common/maps github.com/gohugoio/hugo/common/math 
> github.com/gohugoio/hugo/common/para github.com/gohugoio/hugo/common/paths 
> github.com/gohugoio/hugo/common/terminal github.com/gohugoio/hugo/common/text 
> github.com/gohugoio/hugo/common/types 
> github.com/gohugoio/hugo/common/types/css 
> github.com/gohugoio/hugo/common/types/hstring 
> github.com/gohugoio/hugo/common/urls github.com/gohugoio/hugo/compare 
> github.com/gohugoio/hugo/config github.com/gohugoio/hugo/config/allconfig 
> github.com/gohugoio/hugo/config/privacy 
> github.com/gohugoio/hugo/config/security 
> github.com/gohugoio/hugo/config/services 
> github.com/gohugoio/hugo/config/testconfig github.com/gohugoio/hugo/create 
> github.com/gohugoio/hugo/create/skeletons github.com/gohugoio/hugo/deploy 
> github.com/gohugoio/hugo/deps github.com/gohugoio/hugo/docshelper 
> github.com/gohugoio/hugo/helpers github.com/gohugoio/hugo/htesting 
> github.com/gohugoio/hugo/htesting/hqt github.com/gohugoio/hugo/hugofs 
> github.com/gohugoio/hugo/hugofs/files github.com/gohugoio/hugo/hugofs/glob 
> github.com/gohugoio/hugo/hugolib github.com/gohugoio/hugo/hugolib/filesystems 
> github.com/gohugoio/hugo/hugolib/paths github.com/gohugoio/hugo/identity 
> github.com/gohugoio/hugo/langs github.com/gohugoio/hugo/langs/i18n 
> github.com/gohugoio/hugo/lazy github.com/gohugoio/hugo/livereload 
> github.com/gohugoio/hugo/markup github.com/gohugoio/hugo/markup/asciidocext 
> github.com/gohugoio/hugo/markup/asciidocext/asciidocext_config 
> github.com/gohugoio/hugo/markup/asciidocext/internal 
> github.com/gohugoio/hugo/markup/blackfriday 
> github.com/gohugoio/hugo/markup/converter 
> github.com/gohugoio/hugo/markup/converter/hooks 
> github.com/gohugoio/hugo/markup/goldmark 
> github.com/gohugoio/hugo/markup/goldmark/codeblocks 
> github.com/gohugoio/hugo/markup/goldmark/goldmark_config 
> github.com/gohugoio/hugo/markup/goldmark/images 
> github.com/gohugoio/hugo/markup/goldmark/internal/extensions/attributes 
> github.com/gohugoio/hugo/markup/goldmark/internal/render 
> github.com/gohugoio/hugo/markup/goldmark/links 
> github.com/gohugoio/hugo/markup/highlight 
> github.com/gohugoio/hugo/markup/highlight/chromalexers 
> github.com/gohugoio/hugo/markup/internal 
> github.com/gohugoio/hugo/markup/internal/attributes 
> github.com/gohugoio/hugo/markup/markup_config 
> github.com/gohugoio/hugo/markup/org github.com/gohugoio/hugo/markup/pandoc 
> github.com/gohugoio/hugo/markup/rst 
> github.com/gohugoio/hugo/markup/tableofcontents 
> github.com/gohugoio/hugo/media github.com/gohugoio/hugo/metrics 
> github.com/gohugoio/hugo/minifiers github.com/gohugoio/hugo/modules 
> github.com/gohugoio/hugo/modules/npm github.com/gohugoio/hugo/navigation 
> github.com/gohugoio/hugo/output github.com/gohugoio/hugo/output/layouts 
> github.com/gohugoio/hugo/parser github.com/gohugoio/hugo/parser/metadecoders 
> github.com/gohugoio/hugo/parser/pageparser github.com/gohugoio/hugo/publisher 
> github.com/gohugoio/hugo/related github.com/gohugoio/hugo/releaser 
> github.com/gohugoio/hugo/resources github.com/gohugoio/hugo/resources/images 
> github.com/gohugoio/hugo/resources/images/exif 
> github.com/gohugoio/hugo/resources/images/webp 
> github.com/gohugoio/hugo/resources/internal 
> github.com/gohugoio/hugo/resources/jsconfig 
> github.com/gohugoio/hugo/resources/kinds 
> github.com/gohugoio/hugo/resources/page 
> github.com/gohugoio/hugo/resources/page/page_generate 
> 

Bug#1064769: minexpert2: FTBFS: unsatisfiable build-dependencies: libpappsomspp-dev (>= 0.9.24), libpappsomspp-widget-dev (>= 0.9.24)

[Lucas Nussbaum]

Source: minexpert2
Version: 9.3.2-1
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20240224 ftbfs-trixie

Hi,

During a rebuild of all packages in sid, your package failed to build
on amd64.


Relevant part (hopefully):
> +--+
> | Install package build dependencies  
>  |
> +--+
> 
> 
> Setup apt archive
> -
> 
> Merged Build-Depends: debhelper (>= 13.3.4), dpkg-dev (>= 1.21.22), inkscape, 
> libgomp1, qt6-base-dev, libqt6svg6-dev, libqt6core5compat6-dev, 
> libxkbcommon-x11-dev, cmake, daps, libjs-jquery, libjs-highlight.js, 
> texlive-fonts-extra, fonts-ebgaramond-extra, fonts-urw-base35, 
> libqcustomplot-dev, libisospec++-dev, libquazip1-qt6-dev, zlib1g-dev, 
> libpappsomspp-dev (>= 0.9.24), libpappsomspp-widget-dev (>= 0.9.24), 
> docbook-xml, docbook-to-man, build-essential, fakeroot
> Filtered Build-Depends: debhelper (>= 13.3.4), dpkg-dev (>= 1.21.22), 
> inkscape, libgomp1, qt6-base-dev, libqt6svg6-dev, libqt6core5compat6-dev, 
> libxkbcommon-x11-dev, cmake, daps, libjs-jquery, libjs-highlight.js, 
> texlive-fonts-extra, fonts-ebgaramond-extra, fonts-urw-base35, 
> libqcustomplot-dev, libisospec++-dev, libquazip1-qt6-dev, zlib1g-dev, 
> libpappsomspp-dev (>= 0.9.24), libpappsomspp-widget-dev (>= 0.9.24), 
> docbook-xml, docbook-to-man, build-essential, fakeroot
> dpkg-deb: building package 'sbuild-build-depends-main-dummy' in 
> '/<>/apt_archive/sbuild-build-depends-main-dummy.deb'.
> Ign:1 copy:/<>/apt_archive ./ InRelease
> Get:2 copy:/<>/apt_archive ./ Release [615 B]
> Ign:3 copy:/<>/apt_archive ./ Release.gpg
> Get:4 copy:/<>/apt_archive ./ Sources [1012 B]
> Get:5 copy:/<>/apt_archive ./ Packages [1045 B]
> Fetched 2672 B in 0s (0 B/s)
> Reading package lists...
> Reading package lists...
> 
> Install main build dependencies (apt-based resolver)
> 
> 
> Installing build dependencies
> Reading package lists...
> Building dependency tree...
> Some packages could not be installed. This may mean that you have
> requested an impossible situation or if you are using the unstable
> distribution that some required packages have not yet been created
> or been moved out of Incoming.
> The following information may help to resolve the situation:
> 
> The following packages have unmet dependencies:
>  sbuild-build-depends-main-dummy : Depends: libpappsomspp-dev (>= 0.9.24) but 
> it is not going to be installed
>Depends: libpappsomspp-widget-dev (>= 
> 0.9.24) but it is not going to be installed
> E: Unable to correct problems, you have held broken packages.
> apt-get failed.


The full build log is available from:
http://qa-logs.debian.net/2024/02/24/minexpert2_9.3.2-1_unstable.log

All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20240224;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20240224=lu...@debian.org=1=1=1=1#results

A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!

If you reassign this bug to another package, please mark it as 'affects'-ing
this package. See https://www.debian.org/Bugs/server-control#affects

If you fail to reproduce this, please provide a build log and diff it with mine
so that we can identify if something relevant changed in the meantime.

Bug#1064768: tox-delay: FTBFS: AttributeError: 'Version' object has no attribute 'startswith'

[Lucas Nussbaum]

Source: tox-delay
Version: 0.1.2-2
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20240224 ftbfs-trixie

Hi,

During a rebuild of all packages in sid, your package failed to build
on amd64.


Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> python3 tests/functional.py -e '/<>/shell/tox-delay'
> Using UTF-8 settings: LC_ALL 'C.utf8' LANGUAGE ''
> Trying to find the absolute path to the python3 Python interpreter
> Apparently there is no need to set PYTHONPATH at all
> Using /tmp/tmpkwu0shca as a temporary directory
> Got a tox-delay feature version Version(value='0.1.2', 
> components=[VersionComponent(num=0, rest=''), VersionComponent(num=1, 
> rest=''), VersionComponent(num=2, rest='')])
> Traceback (most recent call last):
>   File "/<>/tests/functional.py", line 344, in 
> main()
>   File "/<>/tests/functional.py", line 332, in main
> check_tox_delay_features(cfg, tempd)
>   File "/<>/tests/functional.py", line 190, in 
> check_tox_delay_features
> if not tdver.startswith("0.1."):
>
> AttributeError: 'Version' object has no attribute 'startswith'
> make[1]: *** [debian/rules:7: override_dh_auto_test] Error 1


The full build log is available from:
http://qa-logs.debian.net/2024/02/24/tox-delay_0.1.2-2_unstable.log

All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20240224;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20240224=lu...@debian.org=1=1=1=1#results

A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!

If you reassign this bug to another package, please mark it as 'affects'-ing
this package. See https://www.debian.org/Bugs/server-control#affects

If you fail to reproduce this, please provide a build log and diff it with mine
so that we can identify if something relevant changed in the meantime.

Bug#1064767: ruby-faraday-middleware-multi-json: FTBFS: ERROR: Test "ruby3.1" failed: NoMethodError:

[Lucas Nussbaum]

Source: ruby-faraday-middleware-multi-json
Version: 0.0.6-2.1
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20240224 ftbfs-trixie

Hi,

During a rebuild of all packages in sid, your package failed to build
on amd64.


Relevant part (hopefully):
> NoMethodError:
>   undefined method `dependency' for FaradayMiddleware::EncodeJson:Class
> 
>   dependency do
>   ^^
> # ./lib/faraday_middleware/multi_json.rb:2:in `'
> # ./spec/spec_helper.rb:19:in `'
> # ./spec/faraday_middleware/multi_json_spec.rb:1:in `'
> Run options: include {:focus=>true}
> 
> All examples were filtered out; ignoring {:focus=>true}
> No examples found.
> 
> 1 deprecation warning total
> 
> Finished in 0.5 seconds (files took 0.29548 seconds to load)
> 0 examples, 0 failures, 1 error occurred outside of examples
> 
> /usr/bin/ruby3.1 
> -I/usr/share/rubygems-integration/all/gems/rspec-support-3.12.0/lib:/usr/share/rubygems-integration/all/gems/rspec-core-3.12.0/lib
>  /usr/share/rubygems-integration/all/gems/rspec-core-3.12.0/exe/rspec 
> --pattern ./spec/\*\*/\*_spec.rb --format documentation failed
> ERROR: Test "ruby3.1" failed: 


The full build log is available from:
http://qa-logs.debian.net/2024/02/24/ruby-faraday-middleware-multi-json_0.0.6-2.1_unstable.log

All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20240224;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20240224=lu...@debian.org=1=1=1=1#results

A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!

If you reassign this bug to another package, please mark it as 'affects'-ing
this package. See https://www.debian.org/Bugs/server-control#affects

If you fail to reproduce this, please provide a build log and diff it with mine
so that we can identify if something relevant changed in the meantime.

Bug#1064766: gir-rust-code-generator: FTBFS: dh_auto_test: error: /usr/share/cargo/bin/cargo build returned exit code 101

[Lucas Nussbaum]

Source: gir-rust-code-generator
Version: 0.18.3-1
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20240224 ftbfs-trixie

Hi,

During a rebuild of all packages in sid, your package failed to build
on amd64.


Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> /usr/share/cargo/bin/cargo prepare-debian debian/cargo_registry 
> --link-from-system
> debian cargo wrapper: options, profiles, parallel, lto: ['parallel=8'] [] 
> ['-j8'] 0
> debian cargo wrapper: rust_type, gnu_type: x86_64-unknown-linux-gnu, 
> x86_64-linux-gnu
> debian cargo wrapper: linking /usr/share/cargo/registry/* into 
> /<>/debian/cargo_registry/
> rm -f Cargo.lock
> touch debian/cargo-checksum.json
> dh_auto_configure
> debian cargo wrapper: options, profiles, parallel, lto: ['parallel=8'] [] 
> ['-j8'] 0
> debian cargo wrapper: rust_type, gnu_type: x86_64-unknown-linux-gnu, 
> x86_64-linux-gnu
> debian cargo wrapper: linking /usr/share/cargo/registry/* into 
> /<>/debian/cargo_registry/
> make[1]: Leaving directory '/<>'
>dh_auto_build -O--buildsystem=cargo
>dh_auto_test -O--buildsystem=cargo
> debian cargo wrapper: options, profiles, parallel, lto: ['parallel=8'] [] 
> ['-j8'] 0
> debian cargo wrapper: rust_type, gnu_type: x86_64-unknown-linux-gnu, 
> x86_64-linux-gnu
> debian cargo wrapper: running subprocess (['env', 'RUST_BACKTRACE=1', 
> '/usr/bin/cargo', '-Zavoid-dev-deps', 'build', '--verbose', '--verbose', 
> '-j8', '--target', 'x86_64-unknown-linux-gnu'],) {}
> error: failed to select a version for the requirement `toml = "^0.7"`
> candidate versions found which didn't match: 0.8.8
> location searched: directory source `/<>/debian/cargo_registry` 
> (which is replacing registry `crates-io`)
> required by package `gir v0.0.1 (/<>)`
> perhaps a crate was updated and forgotten to be re-vendored?
> dh_auto_test: error: /usr/share/cargo/bin/cargo build returned exit code 101


The full build log is available from:
http://qa-logs.debian.net/2024/02/24/gir-rust-code-generator_0.18.3-1_unstable.log

All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20240224;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20240224=lu...@debian.org=1=1=1=1#results

A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!

If you reassign this bug to another package, please mark it as 'affects'-ing
this package. See https://www.debian.org/Bugs/server-control#affects

If you fail to reproduce this, please provide a build log and diff it with mine
so that we can identify if something relevant changed in the meantime.

Bug#1064763: cairo-dock-plug-ins: FTBFS: dh_install: error: missing files, aborting

[Lucas Nussbaum]

Source: cairo-dock-plug-ins
Version: 3.4.1+git20201022.a0d3415c-1.1
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20240224 ftbfs-trixie

Hi,

During a rebuild of all packages in sid, your package failed to build
on amd64.


Relevant part (hopefully):
> make[2]: Entering directory '/<>/obj-x86_64-linux-gnu'
> make[2]: Nothing to be done for 'preinstall'.
> make[2]: Leaving directory '/<>/obj-x86_64-linux-gnu'
> Install the project...
> /usr/bin/cmake -P cmake_install.cmake
> -- Install configuration: ""
> -- Installing: 
> /<>/debian/tmp/usr/share/cairo-dock/plug-ins/shared-files/images/expose-desktops.svg
> -- Installing: 
> /<>/debian/tmp/usr/share/cairo-dock/plug-ins/shared-files/images/expose-windows.svg
> -- Installing: 
> /<>/debian/tmp/usr/share/cairo-dock/plug-ins/shared-files/images/show-desktop.svg
> -- Installing: 
> /<>/debian/tmp/usr/share/cairo-dock/plug-ins/shared-files/images/widget-layer.svg
> -- Installing: 
> /<>/debian/tmp/usr/share/cairo-dock/plug-ins/shared-files/images/icon-gauge.png
> -- Installing: 
> /<>/debian/tmp/usr/share/cairo-dock/plug-ins/shared-files/images/icon-graph.png
> -- Installing: 
> /<>/debian/tmp/usr/share/cairo-dock/plug-ins/shared-files/scripts/lock-screen.sh
> -- Installing: 
> /<>/debian/tmp/usr/lib/x86_64-linux-gnu/cairo-dock/libcd-AlsaMixer.so
> -- Installing: 
> /<>/debian/tmp/usr/share/cairo-dock/plug-ins/AlsaMixer/AlsaMixer.conf
> -- Installing: 
> /<>/debian/tmp/usr/share/cairo-dock/plug-ins/AlsaMixer/default.svg
> -- Installing: 
> /<>/debian/tmp/usr/share/cairo-dock/plug-ins/AlsaMixer/mute.svg
> -- Installing: 
> /<>/debian/tmp/usr/share/cairo-dock/plug-ins/AlsaMixer/emblem-mute.svg
> -- Installing: 
> /<>/debian/tmp/usr/share/cairo-dock/plug-ins/AlsaMixer/broken.svg
> -- Installing: 
> /<>/debian/tmp/usr/share/cairo-dock/plug-ins/AlsaMixer/preview.jpg
> -- Installing: 
> /<>/debian/tmp/usr/share/cairo-dock/plug-ins/AlsaMixer/icon.png
> -- Installing: 
> /<>/debian/tmp/usr/share/cairo-dock/gauges/Sound-Mono/0.svg
> -- Installing: 
> /<>/debian/tmp/usr/share/cairo-dock/gauges/Sound-Mono/1.svg
> -- Installing: 
> /<>/debian/tmp/usr/share/cairo-dock/gauges/Sound-Mono/2.svg
> -- Installing: 
> /<>/debian/tmp/usr/share/cairo-dock/gauges/Sound-Mono/3.svg
> -- Installing: 
> /<>/debian/tmp/usr/share/cairo-dock/gauges/Sound-Mono/preview
> -- Installing: 
> /<>/debian/tmp/usr/share/cairo-dock/gauges/Sound-Mono/readme
> -- Installing: 
> /<>/debian/tmp/usr/share/cairo-dock/gauges/Sound-Mono/theme.xml
> -- Installing: 
> /<>/debian/tmp/usr/share/cairo-dock/gauges/Sound-Mono/undef.svg
> -- Installing: 
> /<>/debian/tmp/usr/share/cairo-dock/gauges/Sound-Mono/version
> -- Installing: 
> /<>/debian/tmp/usr/lib/x86_64-linux-gnu/cairo-dock/libcd-Animated-icons.so
> -- Installing: 
> /<>/debian/tmp/usr/share/cairo-dock/plug-ins/Animated-icons/Animated-icons.conf
> -- Installing: 
> /<>/debian/tmp/usr/share/cairo-dock/plug-ins/Animated-icons/preview.jpg
> -- Installing: 
> /<>/debian/tmp/usr/share/cairo-dock/plug-ins/Animated-icons/icon.svg
> -- Installing: 
> /<>/debian/tmp/usr/share/cairo-dock/plug-ins/Animated-icons/texture-chrome.png
> -- Installing: 
> /<>/debian/tmp/usr/share/cairo-dock/plug-ins/Animated-icons/icon-rotation.png
> -- Installing: 
> /<>/debian/tmp/usr/share/cairo-dock/plug-ins/Animated-icons/spot.png
> -- Installing: 
> /<>/debian/tmp/usr/share/cairo-dock/plug-ins/Animated-icons/halo.png
> -- Installing: 
> /<>/debian/tmp/usr/share/cairo-dock/plug-ins/Animated-icons/ray.png
> -- Installing: 
> /<>/debian/tmp/usr/share/cairo-dock/plug-ins/Animated-icons/icon-wave.png
> -- Installing: 
> /<>/debian/tmp/usr/share/cairo-dock/plug-ins/Animated-icons/icon-busy.png
> -- Installing: 
> /<>/debian/tmp/usr/share/cairo-dock/plug-ins/Animated-icons/busy.svg
> -- Installing: 
> /<>/debian/tmp/usr/lib/x86_64-linux-gnu/cairo-dock/libcd-Cairo-Penguin.so
> -- Installing: 
> /<>/debian/tmp/usr/share/cairo-dock/plug-ins/Cairo-Penguin/Cairo-Penguin.conf
> -- Installing: 
> /<>/debian/tmp/usr/share/cairo-dock/plug-ins/Cairo-Penguin/preview.jpg
> -- Installing: 
> /<>/debian/tmp/usr/share/cairo-dock/plug-ins/Cairo-Penguin/icon.png
> -- Installing: 
> /<>/debian/tmp/usr/share/cairo-dock/plug-ins/Cairo-Penguin/themes/Classic/theme.conf
> -- Installing: 
> /<>/debian/tmp/usr/share/cairo-dock/plug-ins/Cairo-Penguin/themes/Classic/readme
> -- Installing: 
> /<>/debian/tmp/usr/share/cairo-dock/plug-ins/Cairo-Penguin/themes/Classic/basher.png
> -- Installing: 
> /<>/debian/tmp/usr/share/cairo-dock/plug-ins/Cairo-Penguin/themes/Classic/blocker.png
> -- Installing: 
> /<>/debian/tmp/usr/share/cairo-dock/plug-ins/Cairo-Penguin/themes/Classic/boarder.png
> -- Installing: 
> /<>/debian/tmp/usr/share/cairo-dock/plug-ins/Cairo-Penguin/themes/Classic/bomber.png
> -- Installing: 
> /<>/debian/tmp/usr/share/cairo-dock/plug-ins/Cairo-Penguin/themes/Classic/bridger.png
> -- Installing: 
> 

Bug#1064764: flask-basicauth: FTBFS: AssertionError: b'' != b'This view always requires authentication.'

[Lucas Nussbaum]

Source: flask-basicauth
Version: 0.2.0-3
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20240224 ftbfs-trixie

Hi,

During a rebuild of all packages in sid, your package failed to build
on amd64.


Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> python3.12 -m unittest -v test_basicauth.py;  python3.11 -m unittest -v 
> test_basicauth.py;
> test_asks_for_authentication 
> (test_basicauth.BasicAuthTestCase.test_asks_for_authentication) ... ok
> test_asks_for_authentication_with_custom_realm 
> (test_basicauth.BasicAuthTestCase.test_asks_for_authentication_with_custom_realm)
>  ... ok
> test_check_credentials_with_correct_credentials 
> (test_basicauth.BasicAuthTestCase.test_check_credentials_with_correct_credentials)
>  ... ok
> test_check_credentials_with_incorrect_credentials 
> (test_basicauth.BasicAuthTestCase.test_check_credentials_with_incorrect_credentials)
>  ... ok
> test_requires_authentication_for_all_views_when_forced 
> (test_basicauth.BasicAuthTestCase.test_requires_authentication_for_all_views_when_forced)
>  ... ok
> test_responds_with_200_with_correct_credentials 
> (test_basicauth.BasicAuthTestCase.test_responds_with_200_with_correct_credentials)
>  ... FAIL
> test_responds_with_200_with_correct_credentials_containing_colon 
> (test_basicauth.BasicAuthTestCase.test_responds_with_200_with_correct_credentials_containing_colon)
>  ... FAIL
> test_responds_with_401_with_incorrect_credentials 
> (test_basicauth.BasicAuthTestCase.test_responds_with_401_with_incorrect_credentials)
>  ... ok
> test_responds_with_401_without_authorization 
> (test_basicauth.BasicAuthTestCase.test_responds_with_401_without_authorization)
>  ... ok
> test_runs_decorated_view_after_authentication 
> (test_basicauth.BasicAuthTestCase.test_runs_decorated_view_after_authentication)
>  ... FAIL
> test_sets_default_values_for_configuration 
> (test_basicauth.BasicAuthTestCase.test_sets_default_values_for_configuration) 
> ... ok
> test_views_without_basic_auth_decorator_respond_with_200 
> (test_basicauth.BasicAuthTestCase.test_views_without_basic_auth_decorator_respond_with_200)
>  ... ok
> 
> ==
> FAIL: test_responds_with_200_with_correct_credentials 
> (test_basicauth.BasicAuthTestCase.test_responds_with_200_with_correct_credentials)
> --
> Traceback (most recent call last):
>   File "/<>/test_basicauth.py", line 96, in 
> test_responds_with_200_with_correct_credentials
> self.assertEqual(response.status_code, 200)
> AssertionError: 401 != 200
> 
> ==
> FAIL: test_responds_with_200_with_correct_credentials_containing_colon 
> (test_basicauth.BasicAuthTestCase.test_responds_with_200_with_correct_credentials_containing_colon)
> --
> Traceback (most recent call last):
>   File "/<>/test_basicauth.py", line 104, in 
> test_responds_with_200_with_correct_credentials_containing_colon
> self.assertEqual(response.status_code, 200)
> AssertionError: 401 != 200
> 
> ==
> FAIL: test_runs_decorated_view_after_authentication 
> (test_basicauth.BasicAuthTestCase.test_runs_decorated_view_after_authentication)
> --
> Traceback (most recent call last):
>   File "/<>/test_basicauth.py", line 111, in 
> test_runs_decorated_view_after_authentication
> self.assertEqual(
> AssertionError: b'' != b'This view always requires authentication.'
> 
> --
> Ran 12 tests in 0.026s
> 
> FAILED (failures=3)
> test_asks_for_authentication 
> (test_basicauth.BasicAuthTestCase.test_asks_for_authentication) ... ok
> test_asks_for_authentication_with_custom_realm 
> (test_basicauth.BasicAuthTestCase.test_asks_for_authentication_with_custom_realm)
>  ... ok
> test_check_credentials_with_correct_credentials 
> (test_basicauth.BasicAuthTestCase.test_check_credentials_with_correct_credentials)
>  ... ok
> test_check_credentials_with_incorrect_credentials 
> (test_basicauth.BasicAuthTestCase.test_check_credentials_with_incorrect_credentials)
>  ... ok
> test_requires_authentication_for_all_views_when_forced 
> (test_basicauth.BasicAuthTestCase.test_requires_authentication_for_all_views_when_forced)
>  ... ok
> test_responds_with_200_with_correct_credentials 
> (test_basicauth.BasicAuthTestCase.test_responds_with_200_with_correct_credentials)
>  ... FAIL
> test_responds_with_200_with_correct_credentials_containing_colon 
> (test_basicauth.BasicAuthTestCase.test_responds_with_200_with_correct_credentials_containing_colon)
>  ... FAIL
> test_responds_with_401_with_incorrect_credentials 
> 

Bug#1064762: dune-grid: FTBFS: make[1]: *** [/usr/share/dune/dune-debian.mk:39: override_dh_auto_test] Error 1

[Lucas Nussbaum]

Source: dune-grid
Version: 2.9.0-2
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20240224 ftbfs-trixie

Hi,

During a rebuild of all packages in sid, your package failed to build
on amd64.


Relevant part (hopefully):
> make[5]: Entering directory '/<>/build'
> make[5]: Nothing to be done for 'CMakeFiles/build_tests.dir/build'.
> make[5]: Leaving directory '/<>/build'
> [100%] Built target build_tests
> make[4]: Leaving directory '/<>/build'
> /usr/bin/cmake -E cmake_progress_start /<>/build/CMakeFiles 0
> make[3]: Leaving directory '/<>/build'
> make[2]: Leaving directory '/<>/build'
> cd build; PATH=/<>/debian/tmp-test:$PATH /usr/bin/dune-ctest 
>Site: ip-10-84-234-62
>Build name: Linux-c++
> Create new tag: 20240224-2301 - Experimental
> Test project /<>/build
>   Start  1: test-alberta3d-refine
>  1/66 Test  #1: test-alberta3d-refine .   
> Passed0.01 sec
>   Start  2: scsgmappertest
>  2/66 Test  #2: scsgmappertest    
> Passed0.34 sec
>   Start  3: mcmgmappertest
>  3/66 Test  #3: mcmgmappertest    
> Passed0.57 sec
>   Start  4: conformvolumevtktest
>  4/66 Test  #4: conformvolumevtktest ..   
> Passed0.37 sec
>   Start  5: gnuplottest
>  5/66 Test  #5: gnuplottest ...   
> Passed0.35 sec
>   Start  6: nonconformboundaryvtktest
>  6/66 Test  #6: nonconformboundaryvtktest .   
> Passed0.42 sec
>   Start  7: printgridtest
>  7/66 Test  #7: printgridtest 
> .***Skipped   0.01 sec
>   Start  8: subsamplingvtktest
>  8/66 Test  #8: subsamplingvtktest 
> ***Failed6.23 sec
> subsamplingvtktest: MPI_Comm_size == 1
> 
> subsamplingVTKCheck dim=1
> 
> 
> subsamplingVTKCheck dim=2
> 
> 
> subsamplingVTKCheck dim=3
> 
> 2024-02-24 23:01:11.490 (   0.295s) [C08C7040]   
> vtkXMLParser.cxx:375ERR| vtkXMLDataParser (0x31c9ca0): Error parsing XML 
> in stream at line 23, column 0, byte index 1092: not well-formed (invalid 
> token)
> 2024-02-24 23:01:11.490 (   0.295s) [C08C7040]   
> vtkXMLReader.cxx:521ERR| vtkXMLUnstructuredGridReader (0x31c9950): Error 
> parsing input file.  ReadXMLInformation aborting.
> 2024-02-24 23:01:11.490 (   0.295s) [C08C7040]   
> vtkExecutive.cxx:752ERR| vtkCompositeDataPipeline (0x31c5c70): Algorithm 
> vtkXMLUnstructuredGridReader(0x31c9950) returned failure for request: 
> vtkInformation (0x31c7790)
>   Debug: Off
>   Modified Time: 8910
>   Reference Count: 1
>   Registered Events: (none)
>   Request: REQUEST_INFORMATION
>   ALGORITHM_AFTER_FORWARD: 1
>   FORWARD_DIRECTION: 0
> 
> 
> 2024-02-24 23:01:11.492 (   0.297s) [C08C7040]   
> vtkXMLParser.cxx:375ERR| vtkXMLDataParser (0x31c9ca0): Error parsing XML 
> in stream at line 23, column 0, byte index 1089: not well-formed (invalid 
> token)
> 2024-02-24 23:01:11.492 (   0.297s) [C08C7040]   
> vtkXMLReader.cxx:521ERR| vtkXMLUnstructuredGridReader (0x31c9950): Error 
> parsing input file.  ReadXMLInformation aborting.
> 2024-02-24 23:01:11.492 (   0.297s) [C08C7040]   
> vtkExecutive.cxx:752ERR| vtkCompositeDataPipeline (0x31ca430): Algorithm 
> vtkXMLUnstructuredGridReader(0x31c9950) returned failure for request: 
> vtkInformation (0x31cc950)
>   Debug: Off
>   Modified Time: 9448
>   Reference Count: 1
>   Registered Events: (none)
>   Request: REQUEST_INFORMATION
>   ALGORITHM_AFTER_FORWARD: 1
>   FORWARD_DIRECTION: 0
> 
> 
> 2024-02-24 23:01:11.493 (   0.298s) [C08C7040]   
> vtkXMLParser.cxx:375ERR| vtkXMLDataParser (0x31c9ca0): Error parsing XML 
> in stream at line 23, column 0, byte index 1093: junk after document element
> 2024-02-24 23:01:11.493 (   0.298s) [C08C7040]   
> vtkXMLReader.cxx:521ERR| vtkXMLUnstructuredGridReader (0x31c9950): Error 
> parsing input file.  ReadXMLInformation aborting.
> 2024-02-24 23:01:11.493 (   0.298s) [C08C7040]   
> vtkExecutive.cxx:752ERR| vtkCompositeDataPipeline (0x31ca430): Algorithm 
> vtkXMLUnstructuredGridReader(0x31c9950) returned failure for request: 
> vtkInformation (0x31c9810)
>   Debug: Off
>   Modified Time: 9985
>   Reference Count: 1
>   Registered Events: (none)
>   Request: REQUEST_INFORMATION
>   ALGORITHM_AFTER_FORWARD: 1
>   FORWARD_DIRECTION: 0
> 
> 
> 2024-02-24 23:01:11.495 (   0.300s) [C08C7040]   
> vtkXMLParser.cxx:375ERR| vtkXMLDataParser (0x31c9ca0): Error parsing XML 
> in stream at line 23, column 0, byte index 1091: not well-formed (invalid 
> token)
> 2024-02-24 23:01:11.495 (   0.300s) [C08C7040]   
> vtkXMLReader.cxx:521ERR| vtkXMLUnstructuredGridReader (0x31c9950): Error 
> 

Bug#1064760: tailspin: FTBFS: dh_auto_test: error: env DEB_BUILDDIR= /<>/tailspin-3.0.0\+dfsg/debian/dh-cargo/bin/cargo test returned exit code 101

[Lucas Nussbaum]

Source: tailspin
Version: 3.0.0+dfsg-2
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20240224 ftbfs-trixie

Hi,

During a rebuild of all packages in sid, your package failed to build
on amd64.


Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> cmark-gfm README.md > README.html
> cmark-gfm --to plaintext README.md > README.txt
> cmark-gfm CHANGELOG.md > CHANGELOG.html
> cmark-gfm --to plaintext CHANGELOG.md > CHANGELOG.txt
> dh execute_after_dh_auto_build --buildsystem cargo
> make[1]: Leaving directory '/<>'
>dh_auto_test -O--buildsystem=cargo
> debian cargo wrapper: WARNING: falling back to simply calling upstream cargo, 
> because CARGO_HOME does not end with debian/cargo_home:  
> Use of uninitialized value in concatenation (.) or string at 
> /<>/debian/dh-cargo/lib/Debian/Debhelper/Buildsystem/cargo.pm 
> line 296,  line 2.
>   env DEB_BUILDDIR= 
> /<>/tailspin-3.0.0\+dfsg/debian/dh-cargo/bin/cargo test
> debian cargo wrapper: options, profiles, parallel, lto: ['parallel=8'] [] 
> ['-j8'] 0
> debian cargo wrapper: rust_type, gnu_type: x86_64-unknown-linux-gnu, 
> x86_64-linux-gnu
> debian cargo wrapper: running subprocess (['env', 'RUST_BACKTRACE=1', 
> '/usr/bin/cargo', '-Zavoid-dev-deps', 'test', '--verbose', '--verbose', 
> '-j8', '--target', 'x86_64-unknown-linux-gnu', '--release'],) {}
>Fresh unicode-ident v1.0.12
>Fresh autocfg v1.1.0
>Fresh cfg-if v1.0.0
>Fresh once_cell v1.19.0
>Fresh pin-project-lite v0.2.13
>Fresh memchr v2.7.1
>Fresh tracing-core v0.1.32
>Fresh proc-macro2 v1.0.76
>Fresh crossbeam-utils v0.8.19
>Fresh libc v0.2.152
>Fresh bitflags v1.3.2
>Fresh lazy_static v1.4.0
>Fresh quote v1.0.35
>Fresh utf8parse v0.2.1
>Fresh sharded-slab v0.1.4
>Fresh cc v1.0.83
>Fresh thread_local v1.1.4
>Fresh syn v2.0.48
>Fresh anstyle-parse v0.2.1
>Fresh anstyle-query v1.0.0
>Fresh anstyle v1.0.4
>Fresh smallvec v1.11.2
>Fresh colorchoice v1.0.0
>Fresh serde_derive v1.0.195
>Fresh log v0.4.20
>Fresh scopeguard v1.1.0
>Fresh anstream v0.6.7
>Fresh parking_lot_core v0.9.9
>Fresh serde v1.0.195
>Fresh lock_api v0.4.11
>Fresh mio v0.8.10
>Fresh tracing-subscriber v0.3.18
> warning: method `bold` is never used
> --> 
> /<>/debian/cargo_registry/tracing-subscriber-0.3.18/src/fmt/format/mod.rs:1403:8
>  |
> 1398 | impl Style {
>  | -- method in this implementation
> ...
> 1403 | fn bold(self) -> Self {
>  |
>  |
> note: the lint level is defined here
> --> 
> /<>/debian/cargo_registry/tracing-subscriber-0.3.18/src/lib.rs:191:5
>  |
> 191  | unused,
>  | ^^
>  = note: `#[warn(dead_code)]` implied by `#[warn(unused)]`
> 
>Fresh crossbeam-epoch v0.9.18
>Fresh getrandom v0.2.10
>Fresh tracing v0.1.40
> warning: `tracing-subscriber` (lib) generated 1 warning
>Fresh inotify-sys v0.1.5
>Fresh adler v1.0.2
>Fresh strsim v0.10.0
>Fresh gimli v0.28.1
>Fresh heck v0.4.1
>Fresh linux-raw-sys v0.4.12
>Fresh clap_lex v0.6.0
>Fresh option-ext v0.2.0
>Fresh hashbrown v0.12.3
>Fresh bitflags v2.4.2
>Fresh same-file v1.0.6
>Fresh miniz_oxide v0.7.1
>Fresh inotify v0.9.6
>Fresh addr2line v0.21.0
>Fresh dirs-sys v0.4.1
>Fresh clap_builder v4.4.18
>Fresh indexmap v1.9.3
>Fresh rustix v0.38.30
>Fresh walkdir v2.4.0
>Fresh clap_derive v4.4.7
>Fresh tracing-error v0.2.0
> warning: lint `const_err` has been removed: converted into hard error, see 
> issue #71800  for more 
> information
>--> 
> /<>/debian/cargo_registry/tracing-error-0.2.0/src/lib.rs:200:5
> |
> 200 | const_err,
> | ^
> |
> = note: `#[warn(renamed_and_removed_lints)]` on by default
> 
>Fresh parking_lot v0.12.1
>Fresh crossbeam-deque v0.8.5
>Fresh rand_core v0.6.4
>Fresh serde_spanned v0.6.4
>Fresh slab v0.4.9
>Fresh toml_datetime v0.6.5
> warning: `tracing-error` (lib) generated 1 warning
>Fresh tokio-macros v2.2.0
>Fresh crossbeam-channel v0.5.11
>Fresh signal-hook-registry v1.4.0
>Fresh aho-corasick v1.1.2
>Fresh object v0.32.2
>Fresh socket2 v0.5.5
>Fresh filetime v0.2.22
>Fresh num_cpus v1.16.0
>Fresh owo-colors v3.5.0
>Fresh static_assertions v1.1.0
>Fresh futures-core v0.3.30
>Fresh winnow v0.5.15
>Fresh bytes v1.5.0
>Fresh regex-syntax v0.8.2
>Fresh ppv-lite86 v0.2.16
>Fresh futures-task v0.3.30
>Fresh 

Bug#1064759: libhttp-nio-java: FTBFS: dh_auto_test: error: gradle --info --console plain --offline --stacktrace --no-daemon --refresh-dependencies --gradle-user-home .gradle -Duser.home=. -Duser.name=

[Lucas Nussbaum]

Source: libhttp-nio-java
Version: 1.1.0+dfsg-2
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20240224 ftbfs-trixie

Hi,

During a rebuild of all packages in sid, your package failed to build
on amd64.


Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> # Putting the version number in the custom pom
> sed 's/\(VERSION_PACKAGE\)/\11.1.0+dfsg/; 
> s/VERSION_PACKAGE\(.*\)+dfsg[0-9]*/\1/' debian/pom.xml.in > debian/pom.xml
> dh_auto_configure
> make[1]: Leaving directory '/<>'
>jh_linkjars
>dh_auto_build
>   mkdir -p .gradle/init.d
>   cp /usr/share/gradle-debian-helper/init.gradle .gradle/init.d/
>   gradle --info --console plain --offline --stacktrace --no-daemon 
> --refresh-dependencies --gradle-user-home .gradle -Duser.home=. 
> -Duser.name=debian -Ddebian.package=libhttp-nio-java -Dfile.encoding=UTF-8 
> --parallel --max-workers=8 jar
> openjdk version "17.0.10" 2024-01-16
> OpenJDK Runtime Environment (build 17.0.10+7-Debian-1)
> OpenJDK 64-Bit Server VM (build 17.0.10+7-Debian-1, mixed mode, sharing)
> Initialized native services in: /<>/.gradle/native
> To honour the JVM settings for this build a new JVM will be forked. Please 
> consider using the daemon: 
> https://docs.gradle.org/4.4.1/userguide/gradle_daemon.html.
> Starting process 'Gradle build daemon'. Working directory: 
> /<>/.gradle/daemon/4.4.1 Command: 
> /usr/lib/jvm/java-17-openjdk-amd64/bin/java --add-opens 
> java.base/java.lang=ALL-UNNAMED 
> -Xbootclasspath/a:/usr/share/java/gradle-helper-hook.jar:/usr/share/java/maven-repo-helper.jar
>  -Dfile.encoding=UTF-8 -Duser.country -Duser.language=en -Duser.variant -cp 
> /usr/share/gradle/lib/gradle-launcher-4.4.1.jar 
> org.gradle.launcher.daemon.bootstrap.GradleDaemon 4.4.1
> Successfully started process 'Gradle build daemon'
> An attempt to start the daemon took 1.052 secs.
> The client will now receive all logging from the daemon (pid: 924327). The 
> daemon log file: /<>/.gradle/daemon/4.4.1/daemon-924327.out.log
> Daemon will be stopped at the end of the build stopping after processing
> Closing daemon's stdin at end of input.
> The daemon will no longer process any standard input.
> Using 8 worker leases.
> Creating new cache for fileHashes, path 
> /<>/.gradle/caches/4.4.1/fileHashes/fileHashes.bin, access 
> org.gradle.cache.internal.DefaultCacheAccess@70b8209a
> Creating new cache for resourceHashesCache, path 
> /<>/.gradle/caches/4.4.1/fileHashes/resourceHashesCache.bin, 
> access org.gradle.cache.internal.DefaultCacheAccess@70b8209a
> Creating new cache for fileHashes, path 
> /<>/.gradle/4.4.1/fileHashes/fileHashes.bin, access 
> org.gradle.cache.internal.DefaultCacheAccess@18d58a43
> Starting Build
> Compiling initialization script '/<>/.gradle/init.d/init.gradle' 
> using SubsetScriptTransformer.
> Creating new cache for metadata-1.1/results, path 
> /<>/.gradle/caches/transforms-1/metadata-1.1/results.bin, access 
> org.gradle.cache.internal.DefaultCacheAccess@1aedad95
> Compiling initialization script '/<>/.gradle/init.d/init.gradle' 
> using BuildScriptTransformer.
> Compiling settings file '/<>/settings.gradle' using 
> SubsetScriptTransformer.
> Compiling settings file '/<>/settings.gradle' using 
> BuildScriptTransformer.
> Settings evaluated using settings file '/<>/settings.gradle'.
> Projects loaded. Root project using build file 
> '/<>/build.gradle'.
> Included projects: [root project 'http-nio']
>   Keep-alive timer started
>   Adding Debian repository to project 'http-nio'
> Parallel execution is an incubating feature.
> Evaluating root project 'http-nio' using build file 
> '/<>/build.gradle'.
> Compiling build file '/<>/build.gradle' using 
> SubsetScriptTransformer.
> Compiling build file '/<>/build.gradle' using 
> BuildScriptTransformer.
>   Adding Maven pom generation to project 'http-nio'
>   Linking the generated javadoc to the system JDK API documentation
> All projects evaluated.
> Selected primary task 'jar' from project :
> Creating new cache for annotation-processors, path 
> /<>/.gradle/4.4.1/fileContent/annotation-processors.bin, access 
> org.gradle.cache.internal.DefaultCacheAccess@33dafac7
> Tasks to be executed: [task ':compileJava', task ':processResources', task 
> ':classes', task ':debianMavenPom', task ':jar']
> Creating new cache for resourceHashesCache, path 
> /<>/.gradle/4.4.1/fileHashes/resourceHashesCache.bin, access 
> org.gradle.cache.internal.DefaultCacheAccess@18d58a43
> Creating new cache for taskHistory, path 
> /<>/.gradle/4.4.1/taskHistory/taskHistory.bin, access 
> org.gradle.cache.internal.DefaultCacheAccess@120c4a83
> Creating new cache for outputFiles, path 
> /<>/.gradle/buildOutputCleanup/outputFiles.bin, access 
> org.gradle.cache.internal.DefaultCacheAccess@4c1a7b9e
> :compileJava (Thread[Task worker for ':',5,main]) started.
> :compileJava
> Putting task artifact state for task ':compileJava' into context took 

Bug#1064756: xelb: FTBFS: make[1]: *** [Makefile:16: xcb-screensaver.el] Error 255

[Lucas Nussbaum]

Source: xelb
Version: 0.18-4
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20240224 ftbfs-trixie

Hi,

During a rebuild of all packages in sid, your package failed to build
on amd64.


Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> 
> Generating xcb-xproto.el...xcb-types.el: Warning: Non-symbol arguments to 
> cl-defgeneric: (obj xcb:connection)
> 
> Using vacuous schema
> 
> Generating xcb-bigreq.el...
> Generating xcb-render.el...
> Generating xcb-shape.el...
> Generating xcb-dpms.el...
> Generating xcb-dri2.el...
> Generating xcb-dri3.el...
> Generating xcb-ge.el...
> Generating xcb-glx.el...xcb-types.el: Warning: Non-symbol arguments to 
> cl-defgeneric: (obj xcb:connection)
> xcb-types.el: Warning: Non-symbol arguments to cl-defgeneric: (obj 
> xcb:connection)
> xcb-types.el: Warning: Non-symbol arguments to cl-defgeneric: (obj 
> xcb:connection)
> xcb-types.el: Warning: Non-symbol arguments to cl-defgeneric: (obj 
> xcb:connection)
> xcb-types.el: Warning: Non-symbol arguments to cl-defgeneric: (obj 
> xcb:connection)
> xcb-types.el: Warning: Non-symbol arguments to cl-defgeneric: (obj 
> xcb:connection)
> xcb-types.el: Warning: Non-symbol arguments to cl-defgeneric: (obj 
> xcb:connection)
> xcb-types.el: Warning: Non-symbol arguments to cl-defgeneric: (obj 
> xcb:connection)
> 
> Using vacuous schema
> 
> Using vacuous schema
> 
> Generating xcb-sync.el...
> Generating xcb-record.el...
> Using vacuous schema
> 
> Generating xcb-res.el...
> Using vacuous schema
> 
> Using vacuous schema
> 
> Generating xcb-screensaver.el...
> Generating xcb-shm.el...
> Using vacuous schema
> 
> Generating xcb-xc_misc.el...
> Using vacuous schema
> xcb-types.el: Warning: Non-symbol arguments to cl-defgeneric: (obj 
> xcb:connection)
> xcb-types.el: Warning: Non-symbol arguments to cl-defgeneric: (obj 
> xcb:connection)
> 
> Generating xcb-xevie.el...xcb-types.el: Warning: Non-symbol arguments to 
> cl-defgeneric: (obj xcb:connection)
> 
> Using vacuous schema
> 
> Generating xcb-xf86dri.el...xcb-types.el: Warning: Non-symbol arguments to 
> cl-defgeneric: (obj xcb:connection)
> xcb-types.el: Warning: Non-symbol arguments to cl-defgeneric: (obj 
> xcb:connection)
> xcb-types.el: Warning: Non-symbol arguments to cl-defgeneric: (obj 
> xcb:connection)
> 
> Using vacuous schema
> 
> Generating xcb-xf86vidmode.el...xcb-types.el: Warning: Non-symbol arguments 
> to cl-defgeneric: (obj xcb:connection)
> 
> Using vacuous schema
> 
> Generating xcb-xinerama.el...
> Using vacuous schema
> 
> Generating xcb-xkb.el...
> Using vacuous schema
> xcb-types.el: Warning: Non-symbol arguments to cl-defgeneric: (obj 
> xcb:connection)
> 
> Generating xcb-xprint.el...
> Using vacuous schema
> 
> Using vacuous schema
> 
> Generating xcb-xselinux.el...xcb-types.el: Warning: Non-symbol arguments to 
> cl-defgeneric: (obj xcb:connection)
> 
> Generating xcb-xtest.el...xcb-types.el: Warning: Non-symbol arguments to 
> cl-defgeneric: (obj xcb:connection)
> 
> Using vacuous schema
> 
> Generating xcb-xv.el...xcb-types.el: Warning: Non-symbol arguments to 
> cl-defgeneric: (obj xcb:connection)
> 
> Debugger entered--Lisp error: (void-variable 
> xcb:screensaver:xproto:CW:BackPixmap)
>   symbol-value(xcb:screensaver:xproto:CW:BackPixmap)
>   (let ((name (concat (xelb-node-attr node 'ref) ":" (xelb-node-subnode 
> node (symbol-value (or (intern-soft (concat xelb-prefix name)) 
> (intern-soft (concat "xcb:" name)) (intern (concat xelb-prefix name)
>   xelb-parse-enumref((enumref ((ref . "xproto:CW")) "BackPixmap"))
>   (list (xelb-parse-enumref j))
>   (nconc condition (list (xelb-parse-enumref j)))
>   (setq condition (nconc condition (list (xelb-parse-enumref j
>   (let nil (setq condition (nconc condition (list (xelb-parse-enumref j)
>   (if (eq val 'enumref) (let nil (setq condition (nconc condition (list 
> (xelb-parse-enumref j) (let nil (setq tmp (xelb-parse-structure-content 
> j)) (setq fields (nconc fields tmp)) (setq name-list (nconc name-list (list 
> (car (car tmp)))
>   (let* ((val (xelb-node-name j))) (if (eq val 'enumref) (let nil (setq 
> condition (nconc condition (list (xelb-parse-enumref j) (let nil (setq 
> tmp (xelb-parse-structure-content j)) (setq fields (nconc fields tmp)) (setq 
> name-list (nconc name-list (list (car (car tmp
>   (let ((j (car tail))) (let* ((val (xelb-node-name j))) (if (eq val 
> 'enumref) (let nil (setq condition (nconc condition (list (xelb-parse-enumref 
> j) (let nil (setq tmp (xelb-parse-structure-content j)) (setq fields 
> (nconc fields tmp)) (setq name-list (nconc name-list (list (car ...))) 
> (setq tail (cdr tail)))
>   (while tail (let ((j (car tail))) (let* ((val (xelb-node-name j))) (if (eq 
> val 'enumref) (let nil (setq condition (nconc condition (list ... (let 
> nil (setq tmp (xelb-parse-structure-content j)) (setq fields (nconc fields 
> tmp)) (setq name-list (nconc