Bug#1057168: marked as done (jdeb: FTBFS with bouncycastle 1.77)

[Debian Bug Tracking System]

Your message dated Mon, 04 Dec 2023 06:34:31 +
with message-id 
and subject line Bug#1057168: fixed in jdeb 1.10-1
has caused the Debian Bug report #1057168,
regarding jdeb: FTBFS with bouncycastle 1.77
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
1057168: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1057168
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: jdeb
Version: 1.9-1
Severity: serious
Tags: ftbfs sid
User: a...@debian.org
Usertags: bouncycastle-1.77
X-Debbugs-Cc: a...@debian.org

Dear maintainer,

jdeb fails to build from source with bouncycastle 1.77. The reason
is the removal of long deprecated methods. The (hopefully) relevant
error message from the build log.

ERROR] Failures: 
[ERROR]   PGPSignerTestCase.testClearSign:79->Assert.assertEquals:146-
>Assert.assertEquals:117 expected:<...[]
-END PGP SIGNAT...> but was:<...[Sek]
-END PGP SIGNAT...>
[INFO] 
[ERROR] Tests run: 90, Failures: 1, Errors: 0, Skipped: 0
[INFO] 
[INFO] 
[INFO] BUILD FAILURE
[INFO] 
[INFO] Total time:  14.039 s
[INFO] Finished at: 2023-11-30T13:32:26+01:00
[INFO] 
[ERROR] Failed to execute goal org.apache.maven.plugins:maven-surefire-
plugin:2.22.3:test (default-test) on project jdeb: There are test failures.
[ERROR] 
[ERROR] Please refer to /<>/target/surefire-reports for the
individual test results.
[ERROR] Please refer to dump files (if any exist) [date].dump, [date]-
jvmRun[N].dump and [date].dumpstream.
[ERROR] -> [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/MojoFailureException
dh_auto_test: 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 test returned
exit code 1
make: *** [debian/rules:6: build] Error 25
dpkg-buildpackage: error: debian/rules build subprocess returned exit status 2


signature.asc
Description: This is a digitally signed message part
--- End Message ---
--- Begin Message ---
Source: jdeb
Source-Version: 1.10-1
Done: tony mancill 

We believe that the bug you reported is fixed in the latest version of
jdeb, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 1057...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
tony mancill  (supplier of updated jdeb package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sun, 03 Dec 2023 21:59:59 -0800
Source: jdeb
Architecture: source
Version: 1.10-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Java Maintainers 

Changed-By: tony mancill 
Closes: 1047353 1057168
Changes:
 jdeb (1.10-1) unstable; urgency=medium
 .
   * Team upload.
 .
   [ Markus Koschany ]
   * Ignore org.apache.maven.plugins:maven-enforcer-plugin
 .
   [ tony mancill ]
   * debian/watch: scan tags instead of releases
   * New upstream version 1.10
   * Refresh patches to build with BC 1.77 (Closes: #1057168)
   * Fix FTBFS twice in a row (Closes: #1047353)
   * Freshen debian/copyright
   * Bump Standards-Version to 4.6.2
   * Set Rules-Requires-Root: no in debian/control
Checksums-Sha1:
 862177fa2309dd0773914ec5c0829328073ab004 2198 jdeb_1.10-1.dsc
 ea4381a29e90a1176bfb12b137faa7fa374881ec 72748 jdeb_1.10.orig.tar.xz
 0261c193dae8ab31689a254baf5f1aff30bb21a7 4380 jdeb_1.10-1.debian.tar.xz
 321bdce019a15373d7d

Processed: Re: Bug#1000044: ccze: depends on obsolete pcre3 library

[Debian Bug Tracking System]

Processing control commands:

> tag -1 - pending
Bug #144 [src:ccze] ccze: depends on obsolete pcre3 library
Removed tag(s) pending.

-- 
144: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=144
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#1000044: ccze: depends on obsolete pcre3 library

[Axel Beckert]

Control: tag -1 - pending

Hi Yavor,

Yavor Doganov wrote:
> Please find a patch attached (I was not able to test all plugins).

Thanks again for that huge patch. I've pushed it and several other
changes to Salsa.

A local test on my /var/log/syslog immediately ran into a segfault,
though, so I guess, that's one of the plugins you couldn't test.

Culprit is this line, actually the first line in my current /var/log/syslog:

  Dec  3 06:38:28 c6 syslog-ng[26651]: Configuration reload request received, 
reloading configuration;

Example for a minimal reproducer:

  $ echo 'Dec  3 06:38:28 c6 syslog-ng[26651]: Configuration reload request 
received, reloading configuration;' | ccze -A
  free(): invalid pointer
  [1]17679 done   echo  |
 17680 IOT instruction (core dumped)  ccze -A

A backtrace of the core dump gave the following output:

  #0  __pthread_kill_implementation (threadid=, 
signo=signo@entry=6, no_tid=no_tid@entry=0) at ./nptl/pthread_kill.c:44
  #1  0x77d1c15f in __pthread_kill_internal (signo=6, 
threadid=) at ./nptl/pthread_kill.c:78
  #2  0x77cce472 in __GI_raise (sig=sig@entry=6) at 
../sysdeps/posix/raise.c:26
  #3  0x77cb84b2 in __GI_abort () at ./stdlib/abort.c:79
  #4  0x77cb91ed in __libc_message (fmt=fmt@entry=0x77e2b78c 
"%s\n") at ../sysdeps/posix/libc_fatal.c:150
  #5  0x77d25a75 in malloc_printerr (str=str@entry=0x77e2922c 
"free(): invalid pointer") at ./malloc/malloc.c:5658
  #6  0x77d277f4 in _int_free (av=, p=, 
have_lock=have_lock@entry=0) at ./malloc/malloc.c:4432
  #7  0x77d2a16f in __GI___libc_free (mem=mem@entry=0x55566c08) at 
./malloc/malloc.c:3367
  #8  0x77c7b393 in ccze_syslog_process (offsets=0x5556e170) at 
./src/mod_syslog.c:63
  #9  ccze_syslog_handle (str=, length=, 
rest=0x7fffd9a8) at ./src/mod_syslog.c:126
  #10 0xaa1f in ccze_plugin_run 
(pluginset=pluginset@entry=0x5556ad30, subject=subject@entry=0x555609c0 
"Dec  3 06:38:28 c6 syslog-ng[26651]: Configuration reload request received, 
reloading configuration;", subjlen=100, rest=rest@entry=0x7fffd9a8, 
type=type@entry=CCZE_PLUGIN_TYPE_FULL, 
  handled=handled@entry=0x7fffd984, status=0x7fffd988) at 
./src/ccze-plugin.c:327
  #11 0x8696 in ccze_main () at ./src/ccze.c:706
  #12 main (argc=, argv=) at ./src/ccze.c:753

Seems to be the "free(process)" in line 63 of src/mod_syslog.c. But
neither commenting it out (which might have caused a memory leak) nor
replacing it with "pcre2_substring_free(process)" (as present
elsewhere shortly afterwards is this file) did fix the segfault. It
just started to look different, so the latter might be part of the
fix, but in that case it's is not the complete fix .

I currently assume that any line starting with a date and then a
process name with process id in brackets will trigger this as it's the
parsing of the process id inside the brackets where the crash happens.

So in case you have an idea how to fix this, I'd be happy.

(As mentioned elsewhere already, this migration is a huge PCRE
upstream mess and I'm glad about any help as this is not my only
package affected.)

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

Processed: tagging 1000044

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> tags 144 + pending
Bug #144 [src:ccze] ccze: depends on obsolete pcre3 library
Added tag(s) pending.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
144: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=144
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#1056897: [3dprinter-general] Bug#1056897: FTBFS: Plater.cpp:5313: error: call of overloaded ‘load_files?=()=?UTF-8?Q?’ is ambiguous

[Gregor Riepl]

Gah, looks like some arch-dependent glitch. Which explains why it didn't 
happen to either of us (we probably both used amd64 machines, I 
definitely did) and then the failure did happen upon publishing.


Thanks for your help, I'll try to help get the next fix in once it's ready.


Ok, so I have a preliminary status report.

I debugged the issue on i386 first, because that's the easiest to do 
with standard PC hardware.
In contrast with the other architectures, the value reported by the 
failed unit test is off by several orders of magnitude on i386, while it 
seems to be "only" a sign issue on other architectures.


I've isolated the issue to make debugging easier, and that revealed 
incomplete initialization of the Slic3r::arr2::GravityKernel object - 
this object is allocated on the stack by the unit test, and while the 
constructors of all fields are called, the field active_sink remains 
uninitialized.


This is apparently by design, as stated in the Eigen documentation (the 
LA library used by Slicer):

https://eigen.tuxfamily.org/dox/group__TutorialMatrixClass.html

> A default constructor is always available, never performs any dynamic 
memory allocation, and **never initializes the matrix coefficients**.


So, this is most definitely a bug in PrusaSlicer, because it doesn't 
explicitly assign an initial value to 
Slic3r::arr2::GravityKernel.active_sink - but uses it later anyway.


I don't know why this only causes issues on i386, but it's certainly 
dangerous on all architectures.


The fix quite easy, though.
Modify line 20 and 21 in 
src/libslic3r/Arrange/Core/NFP/Kernels/GravityKernel.hpp as follows:


-GravityKernel(Vec2crd gravity_center) : sink{gravity_center} {}
-GravityKernel() = default;
+GravityKernel(Vec2crd gravity_center) : sink{gravity_center}, 
active_sink{0, 0} {}

+GravityKernel() : active_sink{0, 0} {};

I'll file separate bug report + corresponding upstream report later.

Now, I don't know if this will fix the issues on the other 
architectures, but I'll try to reproduce them on an arm64 device at 
least. It's very likely that the issue is the same everywhere.

Bug#1000035: RC: ezquake: depends on obsolete pcre3 library

[Alexandre Detiste]

control: tag -1 +fixed-upstream

I've import 3.6.4 on Salsa

Processed: RC: ezquake: depends on obsolete pcre3 library

[Debian Bug Tracking System]

Processing control commands:

> tag -1 +fixed-upstream
Bug #135 [src:ezquake] ezquake: depends on obsolete pcre3 library
Ignoring request to alter tags of bug #135 to the same tags previously set

-- 
135: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=135
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#1057155: marked as done (vonsh REJECT on amd64)

[Debian Bug Tracking System]

Your message dated Mon, 04 Dec 2023 00:22:44 +
with message-id 
and subject line Bug#1057155: fixed in vonsh 1.0+ds-0.1
has caused the Debian Bug report #1057155,
regarding vonsh REJECT on amd64
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
1057155: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1057155
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: vonsh
Version: 1.0-0.1
Severity: serious
X-Debbugs-Cc: b...@debian.org

Reason:
Version check failed:
Your upload included the binary package vonsh, version 1.0-0.1, for amd64,
however testing already has version 1.0+b1.
Uploads to unstable must have a higher version than present in testing.

REJECT
--- End Message ---
--- Begin Message ---
Source: vonsh
Source-Version: 1.0+ds-0.1
Done: Bastian Germann 

We believe that the bug you reported is fixed in the latest version of
vonsh, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 1057...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Bastian Germann  (supplier of updated vonsh package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sun, 03 Dec 2023 22:34:55 +0100
Source: vonsh
Architecture: source
Version: 1.0+ds-0.1
Distribution: unstable
Urgency: medium
Maintainer: Andrzej Urbaniak 
Changed-By: Bastian Germann 
Closes: 1057155
Changes:
 vonsh (1.0+ds-0.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Drop unnecessary version constraints for Build-Dependencies.
   * debian/copyright: Align license names with Debian requirements.
   * Add version suffix +ds to make the version greater than bookworm's.
 (Closes: #1057155)
Checksums-Sha1:
 73bbb648c5d3c402f6b2d4e63953bac33c53bb5b 1601 vonsh_1.0+ds-0.1.dsc
 f17dd10627c962bbef59252f64c2109ed20e9bd7 2176573 vonsh_1.0+ds.orig.tar.gz
 02eec464f9fd2d5fe8af56003208c55bdd4e4711 8272 vonsh_1.0+ds-0.1.debian.tar.xz
 600f150147ccefe4f6d90f15ea3d4f2ad6e5af7d 5532 vonsh_1.0+ds-0.1_source.buildinfo
Checksums-Sha256:
 4e2aa60dd44a7cf1f4b2f3d886d64a8d0e62fbb6afd1d24e1620f04226e48e56 1601 
vonsh_1.0+ds-0.1.dsc
 03b417ec607528313174bad9fa9df9b3627af967a78c6c11e8f26d8acc354a7a 2176573 
vonsh_1.0+ds.orig.tar.gz
 ccd5ec21cd130facd3e52de5b79834c831d007a01d6d2d35e0c44976b71e5598 8272 
vonsh_1.0+ds-0.1.debian.tar.xz
 3b9db28f8aeca3708c51c5ad880a33359d06753df4d55005175e46c395510169 5532 
vonsh_1.0+ds-0.1_source.buildinfo
Files:
 8d9beb68418446ba1ee76a1c81b4d8fc 1601 games optional vonsh_1.0+ds-0.1.dsc
 75a1e3d86182fc9909fd2bc0727db039 2176573 games optional 
vonsh_1.0+ds.orig.tar.gz
 048e19693d6a07ae696c424042caef2e 8272 games optional 
vonsh_1.0+ds-0.1.debian.tar.xz
 4fa8dff0ea43c8de1f5caa6ce587210e 5532 games optional 
vonsh_1.0+ds-0.1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQHEBAEBCgAuFiEEQGIgyLhVKAI3jM5BH1x6i0VWQxQFAmVtDWwQHGJhZ2VAZGVi
aWFuLm9yZwAKCRAfXHqLRVZDFCRIC/kBfG/pD2iW9eHPK0OiSXUdoovSgRTbXZHS
FAdIonV/+bbg2QoRrmgUiW8ftx8JJSLk5BZHHhyifYxnL0Q4PoOIczW1M2Ip3aWk
ztyepBe+lfvtAEH6h/mJvXay5h3FkDIaj7ooPuh2uU/Mq1nbbHedejUfPI0xm3xg
Xea4GekMDI/u5Uz9UoyfZyqWNashcTM33Lbpl1gPg7ySvKCwcVntWCdhRN3k1hZy
l0s1XlQed7hYpumPaHDCUqviqKDyZPTjRrr0Laqsp/ZJ3zZk3q6nw+j5qJny2s4W
EVD/7vee73bcQP5yh0JOW3kN/3lun98PyTxtpVi7/0aHWKydsLuPcSF+2o3ciOAq
0EWrbWJ5NK4td9KydsD9X12rGTu6DMQdQGkPKdnR199f3/szcBua94MDiJeMcNuR
6hTwe+SdYosLp84oieqU5Hvy0v+EyBzqT4MmZveDrI7E3ED5mxDlPZaegq3xm8ax
AOshvZryFP68EKiUZzL1mpm71RSCgHM=
=pTaN
-END PGP SIGNATURE End Message ---

Bug#1057362: lives: depends on libavutil56 which is not available in stable or unstable anymore

[Alban Browaeys]

Package: lives
Version: 3.0.2-1.2
Severity: grave
Justification: renders package unusable

Dear Maintainer,
I cannot install lives on a bookworm system as it depends on libvutil56
which is not anymore in Debian stable or unstable repositories.

Cheers,
Alban

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

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

Versions of packages lives depends on:
ii  imagemagick   8:6.9.12.98+dfsg1-4
ii  imagemagick-6.q16 [imagemagick]   8:6.9.12.98+dfsg1-4
ii  libasound21.2.10-1
ii  libatk1.0-0   2.50.0-1
ii  libavc1394-0  0.5.4-5
ii  libavutil56   7:4.3.6-0+deb11u1
ii  libc6 2.37-12
ii  libcairo-gobject2 1.18.0-1
ii  libcairo2 1.18.0-1
ii  libgdk-pixbuf-2.0-0   2.42.10+dfsg-3
ii  libgdk-pixbuf2.0-02.40.2-3
ii  libglib2.0-0  2.78.1-4
ii  libgtk-3-03.24.38-6
ii  libjack-jackd2-0 [libjack-0.125]  1.9.21~dfsg-3
ii  libmjpegutils-2.1-0   1:2.1.0+debian-8
ii  libpango-1.0-01.51.0+ds-3
ii  libpangocairo-1.0-0   1.51.0+ds-3
ii  libpng16-16   1.6.40-2
ii  libpulse0 16.1+dfsg1-2+b1
ii  libraw1394-11 2.1.2-2
ii  libswscale5   7:4.3.6-0+deb11u1
pn  libunicap2
pn  libweed0  
ii  libx11-6  2:1.8.7-1
pn  lives-data
pn  lives-plugins 
ii  mplayer   2:1.5+svn38423-2+b1
ii  mpv   0.36.0-1+b1
pn  ogmtools  
ii  perl  5.36.0-10
ii  procps2:4.0.4-2
ii  sox   14.4.2+git20190427-4
ii  zlib1g1:1.2.13.dfsg-3

Versions of packages lives recommends:
ii  dvgrab  3.5+git20160707.1.e46042e-1+b1
ii  ffmpeg  7:6.1-3
ii  frei0r-plugins  1.8.0-1+b1
pn  icedax  
pn  libtheora-bin   
ii  mencoder2:1.5+svn38423-2+b1
ii  mkvtoolnix  80.0-1
pn  pulseaudio  
ii  x11-utils   7.7+6
pn  youtube-dl  

Versions of packages lives suggests:
pn  libdv-bin   
pn  mjpegtools  

Bug#1013554: marked as done (golang-github-valyala-tcplisten: FTBFS: dh_auto_test: error: cd _build && go test -vet=off -v -p 8 github.com/valyala/tcplisten returned exit code 1)

[Debian Bug Tracking System]

Your message dated Mon, 4 Dec 2023 00:22:53 +0100
with message-id <4b955e0f-91ae-4c94-ad59-0ebcde90d...@debian.org>
and subject line Re: Fixing in bullseye
has caused the Debian Bug report #1013554,
regarding golang-github-valyala-tcplisten: FTBFS: dh_auto_test: error: cd 
_build && go test -vet=off -v -p 8 github.com/valyala/tcplisten returned exit 
code 1
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
1013554: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1013554
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: golang-github-valyala-tcplisten
Version: 0.0~git20210309.652d3b4-1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20220624 ftbfs-bookworm

Hi,

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


Relevant part (hopefully):
>  debian/rules binary
> dh binary --builddirectory=_build --buildsystem=golang --with=golang
>dh_update_autotools_config -O--builddirectory=_build -O--buildsystem=golang
>dh_autoreconf -O--builddirectory=_build -O--buildsystem=golang
>dh_auto_configure -O--builddirectory=_build -O--buildsystem=golang
>dh_auto_build -O--builddirectory=_build -O--buildsystem=golang
>   cd _build && go install -trimpath -v -p 8 github.com/valyala/tcplisten
> internal/goarch
> internal/unsafeheader
> internal/goos
> internal/goexperiment
> internal/cpu
> runtime/internal/syscall
> internal/itoa
> runtime/internal/atomic
> math/bits
> unicode/utf8
> internal/abi
> runtime/internal/math
> runtime/internal/sys
> internal/race
> sync/atomic
> unicode
> internal/nettrace
> internal/bytealg
> math
> runtime
> sync
> internal/reflectlite
> internal/singleflight
> internal/testlog
> runtime/cgo
> errors
> sort
> io
> internal/oserror
> path
> strconv
> vendor/golang.org/x/net/dns/dnsmessage
> syscall
> strings
> reflect
> internal/syscall/unix
> internal/syscall/execenv
> time
> context
> io/fs
> internal/poll
> os
> internal/fmtsort
> io/ioutil
> internal/godebug
> fmt
> internal/intern
> net/netip
> net
> github.com/valyala/tcplisten
>dh_auto_test -O--builddirectory=_build -O--buildsystem=golang
>   cd _build && go test -vet=off -v -p 8 github.com/valyala/tcplisten
> === RUN   TestConfigDeferAccept
> tcplisten_test.go:56: cannot create listener 0 using Config 
> &tcplisten.Config{ReusePort:false, DeferAccept:true, FastOpen:false, 
> Backlog:0}: address ip6-localhost: no suitable address found
> --- FAIL: TestConfigDeferAccept (0.13s)
> === RUN   TestConfigReusePort
> tcplisten_test.go:56: cannot create listener 0 using Config 
> &tcplisten.Config{ReusePort:true, DeferAccept:false, FastOpen:false, 
> Backlog:0}: address ip6-localhost: no suitable address found
> --- FAIL: TestConfigReusePort (0.14s)
> === RUN   TestConfigFastOpen
> tcplisten_test.go:56: cannot create listener 0 using Config 
> &tcplisten.Config{ReusePort:false, DeferAccept:false, FastOpen:true, 
> Backlog:0}: address ip6-localhost: no suitable address found
> --- FAIL: TestConfigFastOpen (0.13s)
> === RUN   TestConfigAll
> tcplisten_test.go:56: cannot create listener 0 using Config 
> &tcplisten.Config{ReusePort:true, DeferAccept:true, FastOpen:true, 
> Backlog:0}: address ip6-localhost: no suitable address found
> --- FAIL: TestConfigAll (0.12s)
> === RUN   TestConfigBacklog
> tcplisten_test.go:56: cannot create listener 0 using Config 
> &tcplisten.Config{ReusePort:false, DeferAccept:false, FastOpen:false, 
> Backlog:32}: address ip6-localhost: no suitable address found
> --- FAIL: TestConfigBacklog (0.13s)
> FAIL
> FAIL  github.com/valyala/tcplisten0.646s
> FAIL
> dh_auto_test: error: cd _build && go test -vet=off -v -p 8 
> github.com/valyala/tcplisten returned exit code 1


The full build log is available from:
http://qa-logs.debian.net/2022/06/24/golang-github-valyala-tcplisten_0.0~git20210309.652d3b4-1_unstable.log

All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20220624;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na&merged=ign&fnewerval=7&flastmodval=7&fusertag=only&fusertagtag=ftbfs-20220624&fusertaguser=lu...@debian.org&allbugs=1&cseverity=1&ctags=1&caffected=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 marking it as 'affects'-ing
this package. See https://www.debian.org/Bugs/server-control#affects

If you fail 

Processed: tags

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> tags 1013554 - trixie sid
Bug #1013554 [src:golang-github-valyala-tcplisten] 
golang-github-valyala-tcplisten: FTBFS: dh_auto_test: error: cd _build && go 
test -vet=off -v -p 8 github.com/valyala/tcplisten returned exit code 1
Removed tag(s) trixie and sid.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
1013554: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1013554
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#1057155: vonsh REJECT on amd64

[Bastian Germann]

I am uploading a NMU in order to fix this.
The debdiff is attached.diff -Nru vonsh-1.0/debian/changelog vonsh-1.0+ds/debian/changelog
--- vonsh-1.0/debian/changelog  2023-10-23 00:25:29.0 +0200
+++ vonsh-1.0+ds/debian/changelog   2023-12-03 22:34:55.0 +0100
@@ -1,3 +1,13 @@
+vonsh (1.0+ds-0.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Drop unnecessary version constraints for Build-Dependencies.
+  * debian/copyright: Align license names with Debian requirements.
+  * Add version suffix +ds to make the version greater than bookworm's.
+(Closes: #1057155)
+
+ -- Bastian Germann   Sun, 03 Dec 2023 22:34:55 +0100
+
 vonsh (1.0-0.1) unstable; urgency=medium
 
   * Non-maintainer upload.
diff -Nru vonsh-1.0/debian/control vonsh-1.0+ds/debian/control
--- vonsh-1.0/debian/control2023-10-23 00:25:26.0 +0200
+++ vonsh-1.0+ds/debian/control 2023-12-03 22:34:41.0 +0100
@@ -2,7 +2,7 @@
 Section: games
 Priority: optional
 Maintainer: Andrzej Urbaniak 
-Build-Depends: debhelper (>= 12), libsdl2-dev (>=2.0.9), libsdl2-image-dev 
(>=2.0.4), libsdl2-mixer-dev (>=2.0.4)
+Build-Depends: debhelper (>= 12), libsdl2-dev, libsdl2-image-dev, 
libsdl2-mixer-dev
 Standards-Version: 4.3.0
 Homepage: https://github.com/aurb/vonsh/
 
diff -Nru vonsh-1.0/debian/copyright vonsh-1.0+ds/debian/copyright
--- vonsh-1.0/debian/copyright  2019-08-25 10:40:07.0 +0200
+++ vonsh-1.0+ds/debian/copyright   2023-12-03 22:34:55.0 +0100
@@ -5,7 +5,7 @@
 
 Files: *
 Copyright: 2019 Andrzej Urbaniak
-License: MIT
+License: Expat
  Permission is hereby granted, free of charge, to any person obtaining a copy
  of this software and associated documentation files (the "Software"), to deal
  in the Software without restriction, including without limitation the rights
@@ -26,7 +26,7 @@
 
 Files: inc/pcg_basic.h src/pcg_basic.c
 Copyright: 2014 Melissa O'Neill 
-License: Apache-License-Version-2.0
+License: Apache-2.0
  /usr/share/common-licenses/Apache-2.0
 
 Files: usr/share/games/vonsh/board_tiles.png

Bug#1013554: Fixing in bullseye

[Santiago Vila]

Version: 0.0~git20210309.652d3b4-2

Hello.

For a long time, I was doing archive rebuilds using an absolutely
minimal /etc/hosts file with only two lines: one for localhost
and another one for the hostname.

After I added the IPv6 lines that debian-installer creates
by default, several packages which mysteriously FTBFS for me
for unknown reasons (like this one) suddenly started to build ok.

This allowed me to remove those packages from my "list of packages
which FTBFS", without even reporting the problem as a bug and of course
without making any upload.

I think this is the optimal thing to do in this particular case,
so I no longer see the need to make any upload for bullseye.

The package effectively builds ok in bullseye for me, and I believe
it would also build ok in the setup used by Lucas these days.

Thanks.

Processed: tagging 1056253

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> tags 1056253 + ftbfs
Bug #1056253 [rust-ripasso-cursive] rust-ripasso-cursive - FTBFS with 
rust-ripasso 0.6.4
Added tag(s) ftbfs.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
1056253: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1056253
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: severity of 1055570 is serious

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> severity 1055570 serious
Bug #1055570 [src:lazy-object-proxy] lazy-object-proxy fails tests with Python 
3.12
Severity set to 'serious' from 'important'
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
1055570: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1055570
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: severity of 1055571 is serious

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> severity 1055571 serious
Bug #1055571 [src:cracklib2] cracklib2 tests fail with Python 3.12
Severity set to 'serious' from 'important'
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
1055571: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1055571
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#1057357: qtremoteobjects-everywhere-src: FTBFS in bullseye and bookworm because of expired SSL certificates, will also FTBFS in trixie/sid eventually

[Santiago Vila]

Package: src:qtremoteobjects-everywhere-src
Version: 5.15.2-2
Severity: serious
Tags: ftbfs patch bullseye bookworm upstream

Dear maintainer:

During an archive rebuild of all packages in bookworm,
this package failed to build:

make[4]: Entering directory 
'/<>/tests/auto/external_IODevice/tst_client'
/<>/tests/auto/external_IODevice/tst_client/target_wrapper.sh  
./tst_external_IODevice
* Start testing of tst_clientSSL *
Config: Using QtTest library 5.15.8, Qt 5.15.8 (x86_64-little_endian-lp64 
shared (dynamic) release build; by GCC 12.2.0), debian 12
PASS   : tst_clientSSL::initTestCase()
FAIL!  : tst_clientSSL::testRun() 'socketClient->waitForEncrypted(-1)' returned 
FALSE. ()
   Loc: [tst_client.cpp(77)]
QWARN  : tst_clientSSL::testRun() QProcess: Destroyed while process 
("/<>/tests/auto/external_IODevice/sslTestServer/sslTestServer") 
is still running.
PASS   : tst_clientSSL::cleanupTestCase()
Totals: 2 passed, 1 failed, 0 skipped, 0 blacklisted, 267ms
* Finished testing of tst_clientSSL *
make[4]: *** [Makefile:356: check] Error 1
make[4]: Leaving directory 
'/<>/tests/auto/external_IODevice/tst_client'
make[3]: *** [Makefile:431: sub-tst_client-check_ordered] Error 2
make[3]: Leaving directory '/<>/tests/auto/external_IODevice'
make[2]: *** [Makefile:1329: sub-external_IODevice-check] Error 2
make[2]: Leaving directory '/<>/tests/auto'
dh_auto_test: error: make -j1 check -Ctests/auto LD_LIBRARY_PATH=/<>/lib 
QML2_IMPORT_PATH=/<>/test_root/usr/lib/x86_64-linux-gnu/qt5/qml returned exit 
code 2
make[1]: *** [debian/rules:31: override_dh_auto_test-arch] Error 25
make[1]: Leaving directory '/<>'
make: *** [debian/rules:11: build-arch] Error 2
dpkg-buildpackage: error: debian/rules build-arch subprocess returned exit 
status 2

You can get a full build log from reproducible builds:

https://tests.reproducible-builds.org/debian/rb-pkg/bookworm/amd64/qtremoteobjects-everywhere-src.html

This happens because the SSL certificates in the tests have expired.
This can be checked by doing this:

cd tests/auto/external_IODevice/cert
for a in *; do openssl x509 -noout -enddate -in $a; done

The output from bookworm contains this:

notAfter=May 30 11:33:55 2023 GMT
notAfter=Jun 10 11:33:55 2023 GMT
notAfter=May 30 11:33:55 2023 GMT

and the output for bullseye (where it also fails) contains this:

notAfter=Jul  2 09:32:51 2023 GMT
notAfter=Jul  2 09:32:50 2023 GMT
notAfter=Jul  2 09:32:51 2023 GMT

I'm attaching two patches to fix this.

The first one modifies the script tests/auto/external_IODevice/cert/generate.sh
so that certificates expire in ten years.

The second patch is merely the result of running the script.

Note: The patches are relative to the version in trixie/sid,
where this problem should be fixed first.

Thanks.commit 6699c65d1b7a891d16cab082e4e0c7d083568f34
Author: Santiago Vila 
Date:   Sun Dec 3 22:36:00 2023 +0100

generate.sh: Create SSL certificates with a more realistic expiration date.

Ten years will cover the lifetime of this release as stable, oldstable,
LTS, and some additional extra time (there is really no need for the tests
to fail just the day after LTS ends).

diff --git a/tests/auto/external_IODevice/cert/generate.sh b/tests/auto/external_IODevice/cert/generate.sh
index b79c862..2de1651 100644
--- a/tests/auto/external_IODevice/cert/generate.sh
+++ b/tests/auto/external_IODevice/cert/generate.sh
@@ -30,7 +30,7 @@
 # Generate the CA key
 openssl genrsa -out rootCA.key 2048
 # Generate the CA cert
-openssl req -x509 -key rootCA.key -out rootCA.pem -sha256 -nodes -subj "/CN=QtRO CA" -days 836
+openssl req -x509 -key rootCA.key -out rootCA.pem -sha256 -nodes -subj "/CN=QtRO CA" -days 3651
 
 # genFiles stem [extra args to signing]
 genFiles () {
@@ -42,7 +42,7 @@ genFiles () {
 openssl req -new -key $stem.key -out $stem.csr -subj "/CN=127.0.0.1"
 # Generate and sign the certificate
 openssl x509 -req -in $stem.csr -out $stem.crt \
- -CA rootCA.pem -CAkey rootCA.key -CAcreateserial -days 825 -sha256 "$@"
+ -CA rootCA.pem -CAkey rootCA.key -CAcreateserial -days 3650 -sha256 "$@"
 # Delete the signing request, no longer needed
 rm $stem.csr
 }
commit d9da85818f9bf50a72a371eb1453979432902065
Author: Santiago Vila 
Date:   Sun Dec 3 22:44:00 2023 +0100

Regenerate SSL certificates using the updated generate.sh script.

diff --git a/examples/remoteobjects/ssl/sslserver/cert/client.crt b/examples/remoteobjects/ssl/sslserver/cert/client.crt
index ec85263..4622c5d 100644
--- a/examples/remoteobjects/ssl/sslserver/cert/client.crt
+++ b/examples/remoteobjects/ssl/sslserver/cert/client.crt
@@ -1,17 +1,17 @@
 -BEGIN CERTIFICATE-
-MIICrTCCAZUCFHOQggvUf1o8c5i3yNyiGLNcLC4tMA0GCSqGSIb3DQEBCwUAMBIx
-EDAOBgNVBAMMB1F0Uk8gQ0EwHhcNMjMxMjAzMjAwMTQ5WhcNMjYwMzA3MjAwMTQ5
+MIICrTCCAZUCFHOQggvUf1o8c5i3yNyiGLNcLC4vMA0GCSqGSIb3DQEBCwUAMBIx
+EDAOBgNVBAMMB1F0Uk8gQ0EwHhcNMjMxMjAzMjE0NDM4WhcNMzMxMTMw

Processed: severity of 1055545 is serious

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> severity 1055545 serious
Bug #1055545 [src:zfec] zfec ftbfs with Python 3.12
Severity set to 'serious' from 'important'
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
1055545: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1055545
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: severity of 1055568 is serious

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> severity 1055568 serious
Bug #1055568 [src:m2crypto] m2crypto ftbfs with Python 3.12
Severity set to 'serious' from 'important'
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
1055568: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1055568
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: severity of 1055547 is serious

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> severity 1055547 serious
Bug #1055547 [src:urwid] urwid fails one test with Python 3.12
Severity set to 'serious' from 'important'
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
1055547: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1055547
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: severity of 1055546 is serious

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> severity 1055546 serious
Bug #1055546 [src:swiglpk] swiglpk ftbfs with Python 3.12
Severity set to 'serious' from 'important'
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
1055546: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1055546
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#1057356: pyjunitxml: FTBFS with Python 3.12

[Bastian Germann]

Source: pyjunitxml
Version: 0.7-2
Severity: serious
X-Debbugs-Cc: rosesecurityresea...@proton.me

The unit tests fail with Python 3.12:

test_xml_output (junitxml.tests.test_runner.TestXMLTestRunner.test_xml_output)
Tests that runner properly gives XML output. ... FAIL

==
FAIL: test_console_output_fail 
(junitxml.tests.test_runner.TestXMLTestRunner.test_console_output_fail)
Tests that failure is reported properly on stderr.
--
Traceback (most recent call last):
  File ".pybuild/cpython3_3.12/build/junitxml/tests/test_runner.py", line 89, in 
test_console_output_fail

self.assertTrue('Ran %d tests in ' % (num_tests,) in value,
AssertionError: False is not true : Output was:
Ran 5 tests in 0.002s

FAILED (failures=1, errors=1, skipped=1, expected failures=1, unexpected 
successes=1)


==
FAIL: test_xml_output 
(junitxml.tests.test_runner.TestXMLTestRunner.test_xml_output)
Tests that runner properly gives XML output.
--
Traceback (most recent call last):
  File ".pybuild/cpython3_3.12/build/junitxml/tests/test_runner.py", line 75, 
in test_xml_output
self.assertEqual(document.documentElement.getAttribute('tests'),
AssertionError: '5' != '6'
- 5
+ 6

Processed: forcibly merging 1055550 1056518

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> forcemerge 100 1056518
Bug #100 [src:redland-bindings] redland-bindings ftbfs with Python 3.12
Bug #1056518 [src:redland-bindings] redland-bindings autopkg tests fail with 
Python 3.12
Severity set to 'serious' from 'important'
Added tag(s) ftbfs.
Merged 100 1056518
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
100: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=100
1056518: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1056518
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: severity of 1055550 is serious

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> severity 100 serious
Bug #100 [src:redland-bindings] redland-bindings ftbfs with Python 3.12
Severity set to 'serious' from 'important'
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
100: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=100
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: fixed 1035043 in 1.1-10, found 1035043 in 1.1-1

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> fixed 1035043 1.1-10
Bug #1035043 {Done: Alexandre Detiste } [src:alex4] 
alex4-data: please request assets be explictly licensed
Marked as fixed in versions alex4/1.1-10.
> found 1035043 1.1-1
Bug #1035043 {Done: Alexandre Detiste } [src:alex4] 
alex4-data: please request assets be explictly licensed
Marked as found in versions alex4/1.1-1.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
1035043: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1035043
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#1057355: libmpfr6: major formatted output function bugs with %c and the value 0

[Vincent Lefevre]

Package: libmpfr6
Version: 4.2.0-1
Severity: grave
Tags: security upstream
Justification: user security hole
Forwarded: https://sympa.inria.fr/sympa/arc/mpfr/2023-12/msg0.html
X-Debbugs-Cc: Debian Security Team 

I've reported the following bug in the MPFR mailing-list. I think
I've fixed the issues on the MPFR side in master, but MPFR is still
affected by the bug on the GMP side (gmp_vasprintf):

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

The vasprintf.c code (for the formatted output functions) does not
handle null characters correctly. These characters can occur by
using %c with the value 0.

This is shown by the check_null tsprintf.c test:

  
https://gitlab.inria.fr/mpfr/mpfr/-/commit/78e72e6538fabc1b720d97e862ec45354e5c9c3f

The possible consequences are:
  - possible memory corruption with custom memory allocators that
do not ignore the size parameter of the "free" function;
  - a part of the buffer fails to be overwritten (with possible
security issues if the buffer contains sensitive data that
were expected to be overwritten);
  - an assertion failure when GNU MPFR has been configured with
assertion checking (--enable-assert).

Note that some of these issues partly come from a bug in gmp_vasprintf
(such as the incorrect return value), which I've reported here:

  https://gmplib.org/list-archives/gmp-bugs/2023-December/005420.html

I think that I have fixed these issues on the MPFR side with

  
https://gitlab.inria.fr/mpfr/mpfr/-/commit/390e51ef8570da4e338e9806ecaf2d022210d951

but the first two consequences remain due to the gmp_vasprintf bug.

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

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

Versions of packages libmpfr6 depends on:
ii  libc6 2.36-9+deb12u3
ii  libgmp10  2:6.2.1+dfsg1-1.1

libmpfr6 recommends no packages.

libmpfr6 suggests no packages.

-- no debconf information

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

Bug#1057354: src:r-cran-dbplyr: fails to migrate to testing for too long: triggers autopkgtest regression

[Paul Gevers]

Source: r-cran-dbplyr
Version: 2.3.4+dfsg-1
Severity: serious
Control: close -1 2.4.0+dfsg-1
Tags: sid trixie
User: release.debian@packages.debian.org
Usertags: out-of-sync

Dear maintainer(s),

The Release Team considers packages that are out-of-sync between testing 
and unstable for more than 30 days as having a Release Critical bug in 
testing [1]. Your package src:r-cran-dbplyr has been trying to migrate 
for 31 days [2]. Hence, I am filing this bug. The version in unstable 
triggers autopkgtest failures in src:r-bioc-biocfilecache.


If a package is out of sync between unstable and testing for a longer 
period, this usually means that bugs in the package in testing cannot be 
fixed via unstable. Additionally, blocked packages can have impact on 
other packages, which makes preparing for the release more difficult. 
Finally, it often exposes issues with the package and/or
its (reverse-)dependencies. We expect maintainers to fix issues that 
hamper the migration of their package in a timely manner.


This bug will trigger auto-removal when appropriate. As with all new 
bugs, there will be at least 30 days before the package is auto-removed.


I have immediately closed this bug with the version in unstable, so if 
that version or a later version migrates, this bug will no longer affect 
testing. I have also tagged this bug to only affect sid and trixie, so 
it doesn't affect (old-)stable.


If you believe your package is unable to migrate to testing due to 
issues beyond your control, don't hesitate to contact the Release Team.


Paul

[1] https://lists.debian.org/debian-devel-announce/2023/06/msg1.html
[2] https://qa.debian.org/excuses.php?package=r-cran-dbplyr



OpenPGP_signature.asc
Description: OpenPGP digital signature

Processed: src:r-cran-dbplyr: fails to migrate to testing for too long: triggers autopkgtest regression

[Debian Bug Tracking System]

Processing control commands:

> close -1 2.4.0+dfsg-1
Bug #1057354 [src:r-cran-dbplyr] src:r-cran-dbplyr: fails to migrate to testing 
for too long: triggers autopkgtest regression
Marked as fixed in versions r-cran-dbplyr/2.4.0+dfsg-1.
Bug #1057354 [src:r-cran-dbplyr] src:r-cran-dbplyr: fails to migrate to testing 
for too long: triggers autopkgtest regression
Marked Bug as done

-- 
1057354: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1057354
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#1057353: src:unyt: fails to migrate to testing for too long: triggers autopkgtest failures

[Paul Gevers]

Source: unyt
Version: 2.9.5-1
Severity: serious
Control: close -1 3.0.1-1
Tags: sid trixie
User: release.debian@packages.debian.org
Usertags: out-of-sync

Dear maintainer(s),

The Release Team considers packages that are out-of-sync between testing 
and unstable for more than 30 days as having a Release Critical bug in 
testing [1]. Your package src:unyt has been trying to migrate for 31 
days [2]. Hence, I am filing this bug. The version in unstable triggers 
autopkgtest failure in src:yt.


If a package is out of sync between unstable and testing for a longer 
period, this usually means that bugs in the package in testing cannot be 
fixed via unstable. Additionally, blocked packages can have impact on 
other packages, which makes preparing for the release more difficult. 
Finally, it often exposes issues with the package and/or
its (reverse-)dependencies. We expect maintainers to fix issues that 
hamper the migration of their package in a timely manner.


This bug will trigger auto-removal when appropriate. As with all new 
bugs, there will be at least 30 days before the package is auto-removed.


I have immediately closed this bug with the version in unstable, so if 
that version or a later version migrates, this bug will no longer affect 
testing. I have also tagged this bug to only affect sid and trixie, so 
it doesn't affect (old-)stable.


If you believe your package is unable to migrate to testing due to 
issues beyond your control, don't hesitate to contact the Release Team.


Paul

[1] https://lists.debian.org/debian-devel-announce/2023/06/msg1.html
[2] https://qa.debian.org/excuses.php?package=unyt



OpenPGP_signature.asc
Description: OpenPGP digital signature

Processed: src:unyt: fails to migrate to testing for too long: triggers autopkgtest failures

[Debian Bug Tracking System]

Processing control commands:

> close -1 3.0.1-1
Bug #1057353 [src:unyt] src:unyt: fails to migrate to testing for too long: 
triggers autopkgtest failures
Marked as fixed in versions unyt/3.0.1-1.
Bug #1057353 [src:unyt] src:unyt: fails to migrate to testing for too long: 
triggers autopkgtest failures
Marked Bug as done

-- 
1057353: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1057353
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: found 1057309 in 2.17.1.1-3, tagging 1051877, tagging 1057307, tagging 1052820, tagging 1056926 ...

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> found 1057309 2.17.1.1-3
Bug #1057309 [src:pandoc] src:haskell-pandoc binary package names conflict with 
src:pandoc binary packages
Marked as found in versions pandoc/2.17.1.1-3.
> tags 1051877 + sid trixie
Bug #1051877 {Done: Peter Michael Green } 
[src:rust-libgit2-sys] rust-libgit2-sys: please prepare for libgit2 transition
Added tag(s) trixie and sid.
> tags 1057307 + sid trixie
Bug #1057307 [sioyek] sioyek: FTBFS with mupdf 0.23
Added tag(s) sid and trixie.
> tags 1052820 + experimental
Bug #1052820 {Done: Adrian Bunk } [src:cargo] cargo: FTBFS: 
make[1]: *** [debian/rules:48: override_dh_auto_test-arch] Error 101
Added tag(s) experimental.
> tags 1056926 + experimental
Bug #1056926 {Done: A. Maitland Bottoms } [src:hackrf] 
FTBFS: rm: cannot remove 'underscore.js': No such file or directory
Added tag(s) experimental.
> reassign 1035043 src:alex4
Bug #1035043 {Done: Alexandre Detiste } [alex4-data] 
alex4-data: please request assets be explictly licensed
Bug reassigned from package 'alex4-data' to 'src:alex4'.
Ignoring request to alter found versions of bug #1035043 to the same values 
previously set
No longer marked as fixed in versions alex4/1.1-10.
> tags 1052106 - sid trixie
Bug #1052106 {Done: Jeremy Bícha } 
[gnome-shell-extension-runcat] gnome-shell-extension-runcat: needs update for 
GNOME Shell 45
Removed tag(s) sid and trixie.
> tags 1052107 - sid trixie
Bug #1052107 {Done: Kyle Robbertze } 
[gnome-shell-extension-shortcuts] gnome-shell-extension-shortcuts: needs update 
for GNOME Shell 45
Removed tag(s) trixie and sid.
> fixed 1054228 1.5.2-9.1
Bug #1054228 {Done: Helmut Grohne } [src:pam] pam FTBFS: No 
series file found
Marked as fixed in versions pam/1.5.2-9.1.
> notfixed 1054228 1.5.2-8
Bug #1054228 {Done: Helmut Grohne } [src:pam] pam FTBFS: No 
series file found
No longer marked as fixed in versions pam/1.5.2-8.
> tags 1053204 + sid trixie
Bug #1053204 {Done: Georg Faerber } [onionprobe] onionprobe: 
Tor warns when generating hashed passwords
Added tag(s) trixie and sid.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
1035043: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1035043
1051877: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1051877
1052106: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1052106
1052107: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1052107
1052820: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1052820
1053204: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1053204
1054228: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1054228
1056926: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1056926
1057307: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1057307
1057309: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1057309
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#1057352: src:vonsh: fails to migrate to testing for too long: unresolved RC bug

[Paul Gevers]

Source: vonsh
Version: 1.0
Severity: serious
Control: close -1 1.0-0.1
X-Debbugs-CC: b...@debian.org
Tags: sid trixie
User: release.debian@packages.debian.org
Usertags: out-of-sync
Control: block -1 by 1057155

Dear maintainer(s),

The Release Team considers packages that are out-of-sync between testing 
and unstable for more than 30 days as having a Release Critical bug in 
testing [1]. Your package src:vonsh has been trying to migrate for 31 
days [2]. Hence, I am filing this bug. The version in unstable is 
blocked by RC bug 1057155.


If a package is out of sync between unstable and testing for a longer 
period, this usually means that bugs in the package in testing cannot be 
fixed via unstable. Additionally, blocked packages can have impact on 
other packages, which makes preparing for the release more difficult. 
Finally, it often exposes issues with the package and/or
its (reverse-)dependencies. We expect maintainers to fix issues that 
hamper the migration of their package in a timely manner.


This bug will trigger auto-removal when appropriate. As with all new 
bugs, there will be at least 30 days before the package is auto-removed.


I have immediately closed this bug with the version in unstable, so if 
that version or a later version migrates, this bug will no longer affect 
testing. I have also tagged this bug to only affect sid and trixie, so 
it doesn't affect (old-)stable.


If you believe your package is unable to migrate to testing due to 
issues beyond your control, don't hesitate to contact the Release Team.


Paul

[1] https://lists.debian.org/debian-devel-announce/2023/06/msg1.html
[2] https://qa.debian.org/excuses.php?package=vonsh



OpenPGP_signature.asc
Description: OpenPGP digital signature

Processed: src:vonsh: fails to migrate to testing for too long: unresolved RC bug

[Debian Bug Tracking System]

Processing control commands:

> close -1 1.0-0.1
Bug #1057352 [src:vonsh] src:vonsh: fails to migrate to testing for too long: 
unresolved RC bug
Marked as fixed in versions vonsh/1.0-0.1.
Bug #1057352 [src:vonsh] src:vonsh: fails to migrate to testing for too long: 
unresolved RC bug
Marked Bug as done
> block -1 by 1057155
Bug #1057352 {Done: Paul Gevers } [src:vonsh] src:vonsh: 
fails to migrate to testing for too long: unresolved RC bug
1057352 was not blocked by any bugs.
1057352 was not blocking any bugs.
Added blocking bug(s) of 1057352: 1057155

-- 
1057352: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1057352
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: src:hypercorn: fails to migrate to testing for too long: new Dependency not in testing

[Debian Bug Tracking System]

Processing control commands:

> close -1 0.15.0-1
Bug #1057351 [src:hypercorn] src:hypercorn: fails to migrate to testing for too 
long: new Dependency not in testing
Marked as fixed in versions hypercorn/0.15.0-1.
Bug #1057351 [src:hypercorn] src:hypercorn: fails to migrate to testing for too 
long: new Dependency not in testing
Marked Bug as done

-- 
1057351: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1057351
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#1057351: src:hypercorn: fails to migrate to testing for too long: new Dependency not in testing

[Paul Gevers]

Source: hypercorn
Version: 0.14.4-1
Severity: serious
Control: close -1 0.15.0-1
Tags: sid trixie
User: release.debian@packages.debian.org
Usertags: out-of-sync

Dear maintainer(s),

The Release Team considers packages that are out-of-sync between testing 
and unstable for more than 30 days as having a Release Critical bug in 
testing [1]. Your package src:hypercorn has been trying to migrate for 
33 days [2]. Hence, I am filing this bug. The version in unstable has a 
Depends on an RC buggy package: node-mermaid.


If a package is out of sync between unstable and testing for a longer 
period, this usually means that bugs in the package in testing cannot be 
fixed via unstable. Additionally, blocked packages can have impact on 
other packages, which makes preparing for the release more difficult. 
Finally, it often exposes issues with the package and/or
its (reverse-)dependencies. We expect maintainers to fix issues that 
hamper the migration of their package in a timely manner.


This bug will trigger auto-removal when appropriate. As with all new 
bugs, there will be at least 30 days before the package is auto-removed.


I have immediately closed this bug with the version in unstable, so if 
that version or a later version migrates, this bug will no longer affect 
testing. I have also tagged this bug to only affect sid and trixie, so 
it doesn't affect (old-)stable.


If you believe your package is unable to migrate to testing due to 
issues beyond your control, don't hesitate to contact the Release Team.


Paul

[1] https://lists.debian.org/debian-devel-announce/2023/06/msg1.html
[2] https://qa.debian.org/excuses.php?package=hypercorn



OpenPGP_signature.asc
Description: OpenPGP digital signature

Bug#1057350: src:secsipidx: fails to migrate to testing for too long: FTBFS on 32 bit archs

[Paul Gevers]

Source: secsipidx
Version: 1.2.0-2
Severity: serious
Control: close -1 1.3.2-1
Tags: sid trixie ftbfs
User: release.debian@packages.debian.org
Usertags: out-of-sync

Dear maintainer(s),

The Release Team considers packages that are out-of-sync between testing 
and unstable for more than 30 days as having a Release Critical bug in 
testing [1]. Your package src:secsipidx has been trying to migrate for 
33 days [2]. Hence, I am filing this bug. The version in unstable failed 
to build on armel, armhf and i386.


If a package is out of sync between unstable and testing for a longer 
period, this usually means that bugs in the package in testing cannot be 
fixed via unstable. Additionally, blocked packages can have impact on 
other packages, which makes preparing for the release more difficult. 
Finally, it often exposes issues with the package and/or
its (reverse-)dependencies. We expect maintainers to fix issues that 
hamper the migration of their package in a timely manner.


This bug will trigger auto-removal when appropriate. As with all new 
bugs, there will be at least 30 days before the package is auto-removed.


I have immediately closed this bug with the version in unstable, so if 
that version or a later version migrates, this bug will no longer affect 
testing. I have also tagged this bug to only affect sid and trixie, so 
it doesn't affect (old-)stable.


If you believe your package is unable to migrate to testing due to 
issues beyond your control, don't hesitate to contact the Release Team.


Paul

[1] https://lists.debian.org/debian-devel-announce/2023/06/msg1.html
[2] https://qa.debian.org/excuses.php?package=secsipidx



OpenPGP_signature.asc
Description: OpenPGP digital signature

Processed: src:gdcm: fails to migrate to testing for too long: unresolved RC bug

[Debian Bug Tracking System]

Processing control commands:

> close -1 3.0.22-1
Bug #1057349 [src:gdcm] src:gdcm: fails to migrate to testing for too long: 
unresolved RC bug
Marked as fixed in versions gdcm/3.0.22-1.
Bug #1057349 [src:gdcm] src:gdcm: fails to migrate to testing for too long: 
unresolved RC bug
Marked Bug as done

-- 
1057349: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1057349
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: src:secsipidx: fails to migrate to testing for too long: FTBFS on 32 bit archs

[Debian Bug Tracking System]

Processing control commands:

> close -1 1.3.2-1
Bug #1057350 [src:secsipidx] src:secsipidx: fails to migrate to testing for too 
long: FTBFS on 32 bit archs
Marked as fixed in versions secsipidx/1.3.2-1.
Bug #1057350 [src:secsipidx] src:secsipidx: fails to migrate to testing for too 
long: FTBFS on 32 bit archs
Marked Bug as done

-- 
1057350: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1057350
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#1057349: src:gdcm: fails to migrate to testing for too long: unresolved RC bug

[Paul Gevers]

Source: gdcm
Version: 3.0.21-2
Severity: serious
Control: close -1 3.0.22-1
Tags: sid trixie
User: release.debian@packages.debian.org
Usertags: out-of-sync

Dear maintainer(s),

The Release Team considers packages that are out-of-sync between testing 
and unstable for more than 30 days as having a Release Critical bug in 
testing [1]. Your package src:gdcm has been trying to migrate for 34 
days [2]. Hence, I am filing this bug. The version in unstable has an 
unresolved RC bug (#1056953).


If a package is out of sync between unstable and testing for a longer 
period, this usually means that bugs in the package in testing cannot be 
fixed via unstable. Additionally, blocked packages can have impact on 
other packages, which makes preparing for the release more difficult. 
Finally, it often exposes issues with the package and/or
its (reverse-)dependencies. We expect maintainers to fix issues that 
hamper the migration of their package in a timely manner.


This bug will trigger auto-removal when appropriate. As with all new 
bugs, there will be at least 30 days before the package is auto-removed.


I have immediately closed this bug with the version in unstable, so if 
that version or a later version migrates, this bug will no longer affect 
testing. I have also tagged this bug to only affect sid and trixie, so 
it doesn't affect (old-)stable.


If you believe your package is unable to migrate to testing due to 
issues beyond your control, don't hesitate to contact the Release Team.


Paul

[1] https://lists.debian.org/debian-devel-announce/2023/06/msg1.html
[2] https://qa.debian.org/excuses.php?package=gdcm



OpenPGP_signature.asc
Description: OpenPGP digital signature

Processed: src:takari-polyglot-maven: fails to migrate to testing for too long: unresolved RC bug and B-D not ready to migrate

[Debian Bug Tracking System]

Processing control commands:

> close -1 0.4.11-2
Bug #1057348 [src:takari-polyglot-maven] src:takari-polyglot-maven: fails to 
migrate to testing for too long: unresolved RC bug and B-D not ready to migrate
Marked as fixed in versions takari-polyglot-maven/0.4.11-2.
Bug #1057348 [src:takari-polyglot-maven] src:takari-polyglot-maven: fails to 
migrate to testing for too long: unresolved RC bug and B-D not ready to migrate
Marked Bug as done

-- 
1057348: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1057348
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#1057348: src:takari-polyglot-maven: fails to migrate to testing for too long: unresolved RC bug and B-D not ready to migrate

[Paul Gevers]

Source: takari-polyglot-maven
Version: 0.4.11-1
Severity: serious
Control: close -1 0.4.11-2
Tags: sid trixie
User: release.debian@packages.debian.org
Usertags: out-of-sync

Dear maintainer(s),

The Release Team considers packages that are out-of-sync between testing 
and unstable for more than 30 days as having a Release Critical bug in 
testing [1]. Your package src:takari-polyglot-maven has been trying to 
migrate for 36 days [2]. Hence, I am filing this bug. The version in 
unstable has an unresolved RC bug. On top of that it Build-Depends on 
several jruby* packages which aren't in testing.


If a package is out of sync between unstable and testing for a longer 
period, this usually means that bugs in the package in testing cannot be 
fixed via unstable. Additionally, blocked packages can have impact on 
other packages, which makes preparing for the release more difficult. 
Finally, it often exposes issues with the package and/or
its (reverse-)dependencies. We expect maintainers to fix issues that 
hamper the migration of their package in a timely manner.


This bug will trigger auto-removal when appropriate. As with all new 
bugs, there will be at least 30 days before the package is auto-removed.


I have immediately closed this bug with the version in unstable, so if 
that version or a later version migrates, this bug will no longer affect 
testing. I have also tagged this bug to only affect sid and trixie, so 
it doesn't affect (old-)stable.


If you believe your package is unable to migrate to testing due to 
issues beyond your control, don't hesitate to contact the Release Team.


Paul

[1] https://lists.debian.org/debian-devel-announce/2023/06/msg1.html
[2] https://qa.debian.org/excuses.php?package=takari-polyglot-maven



OpenPGP_signature.asc
Description: OpenPGP digital signature

Processed: severity of 1051876 is serious

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> severity 1051876 serious
Bug #1051876 {Done: Cédric Boutillier } [src:ruby-rugged] 
ruby-rugged: please prepare for libgit2 transition
Severity set to 'serious' from 'normal'
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
1051876: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1051876
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#1032104: marked as done (linux: ppc64el iouring corrupted read)

[Debian Bug Tracking System]

Your message dated Sun, 03 Dec 2023 20:48:02 +
with message-id 
and subject line Bug#1032104: fixed in linux 6.6.4-1~exp1
has caused the Debian Bug report #1032104,
regarding linux: ppc64el iouring corrupted read
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
1032104: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1032104
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: linux
Version: 5.10.0-21-powerpc64le
Severity: grave
Justification: causes non-serious data loss
X-Debbugs-Cc: dan...@mariadb.org

Dear Maintainer,

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

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

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

>From https://jira.mariadb.org/browse/MDEV-30728

MariaDB's mtr tests on a number of specific tests depend on the correct
kernel operation.

As observed in these tests, there is a ~1/5 chance the
encryption.innodb_encryption test will read zeros on the later part of
the 16k pages that InnoDB uses by default.

This affects MariaDB-10.6+ packages where there is a liburing in the
distribution.

This has been observed in the CI of Debian
(https://ci.debian.net/packages/m/mariadb/testing/ppc64el/)
and upstreams https://buildbot.mariadb.org/#/builders/318.
The one ppc64le worker that has the Debian 5.10.0-21 kernel,
the same as the Debian CI, has the prefix ppc64le-db-bbw1-*.

Test faults occur on all MariaDB 10.6+ builds in containers on this kernel.
There a no faults on non-ppc64le or RHEL7/8 based ppc64le kernels.

To reproduce:

apt-get install mariadb-test
cd /usr/share/mysql/mysql-test
./mtr --mysqld=--innodb-flush-method=fsync --mysqld=--innodb-use-native-aio=1 
--vardir=/var/lib/mysql  --force encryption.innodb_encryption,innodb,undo0 
--repeat=12 

A test will frequenty fail.

2023-02-28  1:41:01 0 [ERROR] InnoDB: Database page corruption on disk or a 
failed read of file './ibdata1' page [page id: space=0, page number=282]. You 
may have to recover from a backup.

(the page number isn't predictable)

The complete mtr error log of mariadb server is $PWD/var/log/mysqld.1.err

I tested on tmpfs. This is a different fault from bug #1020831 as:
* there is no iouring error, just a bunch of zeros where data was
  expected.
* this is ppc64le only.

Note, more serious faults exist on overlayfs (MDEV-28751) and remote
filesystems so sticking to local xfs, ext4, btrfs is recommended.

-- System Information:
Debian Release: bullseye
  APT prefers jammy-updates
  APT policy: (500, 'jammy-updates'), (500, 'jammy-security'), (500, 'jammy'), 
(100, 'jammy-backports')
Architecture: ppc64el (ppc64le)

Kernel: Linux 5.10.0-21-powerpc64le (SMP w/128 CPU threads)
Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: unable to detect
--- End Message ---
--- Begin Message ---
Source: linux
Source-Version: 6.6.4-1~exp1
Done: Bastian Blank 

We believe that the bug you reported is fixed in the latest version of
linux, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 1032...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Bastian Blank  (supplier of updated linux package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sun, 03 Dec 2023 20:57:56 +0100
Source: linux
Architecture: source
Version: 6.6.4-1~exp1
Distribution: experimental
Urgency: medium
Maintainer: Debian Kernel Team 
Changed-By: Bastian Blank 
Closes: 1032104 1037938
Changes:
 linux (6.6.4-1~exp1) experimental; urgency=medium
 .
   * New upstream stable update:
 https://www.kernel.org/pub/linux/kernel/v6.x/ChangeLog-6.6.4
 - nvmet: nul-terminate the NQNs passed in the connect command
   (CVE-2023-6121)
 .
   [ Bastian Blank ]
   * Fix build dependency on rsync.
   * Fix build dependency on kernel-wedge.
   * udeb: Make i2c-hid modules optional.
 .
   [ Timothy Pearson ]
   * [powerpc] Don't clobber f0/vs0 during fp|altivec r

Bug#1057347: vips: increase the timeout further and make it unconditional

[Adrian Bunk]

Source: vips
Version: 8.14.1-1
Severity: serious
Tags: ftbfs patch

1. Make the timeout much larger

The current timeout is not sufficient on all MIPS buildds:
https://buildd.debian.org/status/package.php?p=vips

A generous timeout is cheap, since it only has any negative
effect in the rare case where the test actually hangs.

For passing tests and even for test failures a timeout has no effect.


2. Make the timeout unconditional

As noted above a more generous timeout is cheap,
an unconditional increase is less hassle than manually
tracking buildd speed for every architecture
(e.g. Alpha also has slow qemu buildds where the tests
currently time out).


--- vips-8.15.0/debian/rules.old2023-12-03 20:32:41.049820544 +
+++ vips-8.15.0/debian/rules2023-12-03 20:05:30.918121415 +
@@ -12,11 +12,7 @@
 DESTDIR = $(CURDIR)/debian/tmp
 
 override_dh_auto_test:
-ifeq (, $(filter hppa hurd-i386 mips64el mipsel sparc64, $(DEB_BUILD_ARCH)))
-   LD_LIBRARY_PATH=$(CURDIR)/obj-$(DEB_BUILD_GNU_TYPE)/libvips dh_auto_test
-else
-   LD_LIBRARY_PATH=$(CURDIR)/obj-$(DEB_BUILD_GNU_TYPE)/libvips 
dh_auto_test -- --timeout-multiplier=3
-endif
+   LD_LIBRARY_PATH=$(CURDIR)/obj-$(DEB_BUILD_GNU_TYPE)/libvips 
dh_auto_test -- --timeout-multiplier=10
 
 override_dh_auto_configure:
dh_auto_configure -- \

Bug#1054747: ruby-octokit: FTBFS: ERROR: Test "ruby3.1" failed: Failure/Error: require 'pry-byebug'

[Miguel Landaeta]

On Fri, Oct 27, 2023 at 09:20:42PM +0200, Lucas Nussbaum wrote:
> Source: ruby-octokit
> Version: 4.20.0-1
> Severity: serious
> Justification: FTBFS
> Tags: trixie sid ftbfs
> User: lu...@debian.org
> Usertags: ftbfs-20231027 ftbfs-trixie
> 
> Hi,
> 
> During a rebuild of all packages in sid, your package failed to build
> on amd64.
> 
> 
> Relevant part (hopefully):
> > Failure/Error: require 'pry-byebug'
> > 
> > Gem::MissingSpecError:
> >   Could not find 'pry' (~> 0.13.0) among 122 total gem(s)


A possible fix for this issue could be to just update pry-byebug package to a
more recent release.

https://github.com/deivid-rodriguez/pry-byebug/commit/a915f21fc63aa94473bbe7cb752c0fabacc3e567

pry-byebug 3.10.1 depends on a pry version that's in the archive.

https://packages.debian.org/source/unstable/pry

Processed: severity of 1055552 is serious

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> severity 102 serious
Bug #102 [src:python-nss] python-nss ftbfs with Python 3.12
Severity set to 'serious' from 'important'
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
102: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=102
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: severity of 1055555 is serious

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> severity 105 serious
Bug #105 [src:python-jellyfish] python-jellyfish fails tests with Python 
3.12
Severity set to 'serious' from 'important'
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
105: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=105
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: severity of 1055554 is serious

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> severity 104 serious
Bug #104 [src:python-libais] python-libais ftbfs with Python 3.12
Severity set to 'serious' from 'important'
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
104: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=104
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#1000044: ccze: depends on obsolete pcre3 library

[Axel Beckert]

Hi Yavor,

Yavor Doganov wrote:
> Please find a patch attached

Thanks a lot!

> (I was not able to test all plugins).

Better than nothing.

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

Processed: severity of 1055557 is serious

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> severity 107 serious
Bug #107 [src:python-hiredis] python-hiredis ftbfs with Python 3.12
Severity set to 'serious' from 'important'
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
107: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=107
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: severity of 1055560 is serious

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> severity 1055560 serious
Bug #1055560 [src:pysmbc] pysmbc ftbfs with Python 3.12
Severity set to 'serious' from 'important'
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
1055560: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1055560
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: severity of 1055561 is serious

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> severity 1055561 serious
Bug #1055561 [src:pyodbc] pyodbc ftbfs with Python 3.12
Severity set to 'serious' from 'important'
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
1055561: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1055561
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#1057344: libgmp10: major formatted output function bug with %c and the value 0

[Vincent Lefevre]

Package: libgmp10
Version: 2:6.2.1+dfsg1-1.1
Severity: grave
Tags: security upstream
Justification: user security hole
Forwarded: https://gmplib.org/list-archives/gmp-bugs/2023-December/005420.html
X-Debbugs-Cc: Debian Security Team 

I've reported the following bug upstream. Debian/stable is affected
(at least on the testcase below, but the various issues are probably
related).

With GMP 6.3.0, the formatted output functions do not handle %c
with the value 0 correctly. For gmp_sprintf, the return value is
incorrect. For gmp_asprintf and gmp_vasprintf, this is either a
buffer overflow (according to the GMP manual: "The block will be
the size of the string and null-terminator.") or, in case this
is an error in the GMP manual, possible memory corruption when
freeing the allocated memory, if the custom memory allocation
function cares about the size parameter.

Testcase for gmp_sprintf:


#include 
#include 

static void test (int flag)
{
  char s[3] = { 1, 1, 1 };
  int r;

  r = (flag ? sprintf : gmp_sprintf) (s, "%c", 0);
  printf ("%4s: r = %d, s = { %d %d %d }\n",
  flag ? "libc" : "gmp", r, s[0], s[1], s[2]);
}

int main (void)
{
  test (0);
  test (1);
  return 0;
}


which currently gives:

 gmp: r = 0, s = { 0 0 1 }
libc: r = 1, s = { 0 0 1 }

MPFR has various issues concerning %c with the value 0, but an
attempt to fix them fails due to

  length = gmp_vasprintf (...);
[...]
  mpfr_free_str (s);

which is similar to GMP's tests/misc/t-printf.c file, which contains

  got_len = gmp_vasprintf (&got, fmt, ap);
[...]
  (*__gmp_free_func) (got, strlen(got)+1);

But replacing

  mpfr_free_str (s);

by

  mpfr_free_func (s, length + 1);

i.e. using the return value length instead of strlen(s), also fails.
I suppose that this is related to the incorrect return value.

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

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

Versions of packages libgmp10 depends on:
ii  libc6  2.36-9+deb12u3

libgmp10 recommends no packages.

libgmp10 suggests no packages.

-- no debconf information

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

Processed: Re: Bug#1057205: systemtap: version 5.0-1 FTBFS on i386, ppc64el, riscv64

[Debian Bug Tracking System]

Processing control commands:

> retitle -1 systemtap: FTBFS with g++-13 on i386, ppc64el, riscv64
Bug #1057205 [systemtap] systemtap: version 5.0-1 FTBFS on i386, ppc64el, 
riscv64
Changed Bug title to 'systemtap: FTBFS with g++-13 on i386, ppc64el, riscv64' 
from 'systemtap: version 5.0-1 FTBFS on i386, ppc64el, riscv64'.

-- 
1057205: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1057205
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#1057205: systemtap: version 5.0-1 FTBFS on i386, ppc64el, riscv64

[Emanuele Rocca]

Control: retitle -1 systemtap: FTBFS with g++-13 on i386, ppc64el, riscv64

On 2023-12-01 04:53, Emanuele Rocca wrote:
> In constructor ‘symresolution_info::symresolution_info(systemtap_session&, 
> bool)’,
> inlined from ‘int semantic_pass_symbols(systemtap_session&)’ at 
> elaborate.cxx:1872:28:
> elaborate.cxx:2659:21: error: storing the address of local variable ‘sym’ in 
> ‘*s.systemtap_session::symbol_resolver’ [-Werror=dangling-pointer=]
>  2659 |   s.symbol_resolver = this; // save resolver for early PR25841 
> function resolution
>   |   ~~^~
> elaborate.cxx: In function ‘int semantic_pass_symbols(systemtap_session&)’:
> elaborate.cxx:1872:22: note: ‘sym’ declared here
>  1872 |   symresolution_info sym (s);
>   |  ^~~
> elaborate.cxx:1870:43: note: ‘s’ declared here
>  1870 | semantic_pass_symbols (systemtap_session& s)
>   |~~~^

This is happening only with g++-13. With CXX=g++-12 systemtap builds
fine.

Processed: unblock 1057240 with 1057241 1057242 1057243 1057245 1057246 1057247 1057319 1057231 1056995 ...

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> unblock 1057240 with 1057241 1057242 1057243 1057245 1057246 1057247 1057319 
> 1057231 1056995
Bug #1057240 [src:alsa-utils] alsa-utils: will FTBFS when udev.pc changes 
udevdir
1057240 was blocked by: 1057246 1057243 1056995 1057319 1057231 1057247 1057245 
1057241 1057242
1057240 was not blocking any bugs.
Removed blocking bug(s) of 1057240: 1057247, 1057246, 1057243, 1057245, 
1057231, 1057242, 1056995, 1057241, and 1057319
> block 1057333 with 1057240 1057241 1057242 1057243 1057245 1057246 1057247 
> 1057319 1057231 1056995
Bug #1057333 [udev] udev: change udevdir to /usr/lib/udev - NOT YET
1057333 was blocked by: 1056922 1056725 1056938 1054411 1056692 1056670
1057333 was not blocking any bugs.
Added blocking bug(s) of 1057333: 1057240, 1057241, 1057319, 1057242, 1056995, 
1057243, 1057245, 1057231, 1057247, and 1057246
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
1057240: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1057240
1057333: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1057333
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#1041491: marked as done (yuzu: FTBFS: Unmet build dependencies: glslang-tools:native)

[Debian Bug Tracking System]

Your message dated Sun, 03 Dec 2023 19:47:09 +
with message-id 
and subject line Bug#1041491: fixed in yuzu 0-1335+ds-1+deb12u1
has caused the Debian Bug report #1041491,
regarding yuzu: FTBFS: Unmet build dependencies: glslang-tools:native
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
1041491: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1041491
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: yuzu
Version: 0-1335+ds-1
Severity: serious
Tags: ftbfs sid trixie
Justification: fails to build from source (but built successfully in the past)
X-Debbugs-Cc: sramac...@debian.org

https://buildd.debian.org/status/fetch.php?pkg=yuzu&arch=amd64&ver=0-1335%2Bds-1%2Bb1&stamp=1689519069&raw=0

dpkg-buildpackage: info: host architecture amd64
dpkg-checkbuilddeps: error: Unmet build dependencies: glslang-tools:native
dpkg-buildpackage: warning: build dependencies/conflicts unsatisfied; aborting

Cheers
-- 
Sebastian Ramacher
--- End Message ---
--- Begin Message ---
Source: yuzu
Source-Version: 0-1335+ds-1+deb12u1
Done: Bastian Germann 

We believe that the bug you reported is fixed in the latest version of
yuzu, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 1041...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Bastian Germann  (supplier of updated yuzu package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Thu, 02 Nov 2023 13:48:32 +0100
Source: yuzu
Architecture: source
Version: 0-1335+ds-1+deb12u1
Distribution: bookworm
Urgency: medium
Maintainer: Andrea Pappacoda 
Changed-By: Bastian Germann 
Closes: 1041491
Changes:
 yuzu (0-1335+ds-1+deb12u1) bookworm; urgency=medium
 .
   * strip :native from glslang-tools build dependency (Closes: #1041491)
Checksums-Sha1:
 11f95d57671357063d253f57ea2de4aa671da8a7 2393 yuzu_0-1335+ds-1+deb12u1.dsc
 89d8dc80cddba260fa27c137764a00b3aa537e2b 22872 
yuzu_0-1335+ds-1+deb12u1.debian.tar.xz
 033eb08da9a65777cc02e21e49ef8b92ae731b61 5474 
yuzu_0-1335+ds-1+deb12u1_source.buildinfo
Checksums-Sha256:
 539dd4d90276dbdd39779b342ffe4093509e4305d72781ad692024cdb83dc427 2393 
yuzu_0-1335+ds-1+deb12u1.dsc
 da880b20b0da826ab760f6b8fd7f78aa79a42ff847895bea4532780bd55ccf52 22872 
yuzu_0-1335+ds-1+deb12u1.debian.tar.xz
 c37d219148bd92af3ad0babcb2923d01ba7376022f8ed003244f9cec95c4fcfb 5474 
yuzu_0-1335+ds-1+deb12u1_source.buildinfo
Files:
 ed0354e82d27a99ddc1a1bcb231055eb 2393 games optional 
yuzu_0-1335+ds-1+deb12u1.dsc
 c5b57320449114415e45392e06c6ec83 22872 games optional 
yuzu_0-1335+ds-1+deb12u1.debian.tar.xz
 834ebee21d05e52c816014853baf77fc 5474 games optional 
yuzu_0-1335+ds-1+deb12u1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQHEBAEBCgAuFiEEQGIgyLhVKAI3jM5BH1x6i0VWQxQFAmVsyKoQHGJhZ2VAZGVi
aWFuLm9yZwAKCRAfXHqLRVZDFENEC/9hX9WRfgsOK5ivNs7RGuobpEDhl47fMrsZ
edmCy59FSBdr49amN0IX3x9Bu30T6kxhXu1lEqWUN08xpo23JhdClIBk4ooMIh3h
dwOspRJ2AAekZv/Swz6whd0j+79qY7HKEhZXYGEohLLGD/2cCO4LDa1qZvFT9yHF
zy2/lOZyKxu7jDZWkF5odq4+KIez0s9QhkVVxPWqVqeDBXSjo3uR7Fp2RsdDaVyQ
7w2mHfksfotFzvNv/IdHcVchp21yCBA94BS8gHn7qipZvb59OfGZJ99Ju7cHBZrI
Fvq312liV+OCxntRLqpP8vPKE3QqA3EdC02ugFEU21HANBTfkf/+ZrRMPKk8yMLN
CErJ2TGEHc3cfpgsP+JhVQJEa5i+j+yECr6eQ2ev+s/u2aycszWOQqwT45nb5w6B
Ikd6G9oDDD9GJRRvgyMzvatmp9Gp8KiLcJYtm7Jtc+LkDITXwIrKRmsv+qjb0YpY
yuuoQlm4F/W77xDrRUWsknqjEMsg50c=
=0jck
-END PGP SIGNATURE End Message ---

Processed: severity of 1055563 is serious

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> severity 1055563 serious
Bug #1055563 [src:pycdio] pycdio ftbfs with Python 3.12
Severity set to 'serious' from 'important'
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
1055563: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1055563
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: severity of 1055564 is serious

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> severity 1055564 serious
Bug #1055564 [src:pyalsaaudio] pyalsaaudio ftbfs with Python 3.12
Severity set to 'serious' from 'important'
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
1055564: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1055564
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: your mail

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> reassign 1057309 src:pandoc
Bug #1057309 [src:haskell-pandoc] src:haskell-pandoc binary package names 
conflict with src:pandoc binary packages
Bug reassigned from package 'src:haskell-pandoc' to 'src:pandoc'.
No longer marked as found in versions haskell-pandoc/3.0.1-2.
Ignoring request to alter fixed versions of bug #1057309 to the same values 
previously set
> affects 1057309 src:haskell-pandoc
Bug #1057309 [src:pandoc] src:haskell-pandoc binary package names conflict with 
src:pandoc binary packages
Added indication that 1057309 affects src:haskell-pandoc
>
End of message, stopping processing here.

Please contact me if you need assistance.
-- 
1057309: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1057309
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: severity of 1055566 is serious

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> severity 1055566 serious
Bug #1055566 [src:mod-wsgi] mod-wsgi ftbfs with Python 3.12
Severity set to 'serious' from 'important'
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
1055566: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1055566
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: severity of 1055551 is serious

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> severity 101 serious
Bug #101 [src:python-ptrace] python-ptrace ftbfs with Python 3.12
Severity set to 'serious' from 'important'
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
101: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=101
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: affects

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> # This is already fixed, but for completeness:
> # Package androguard FTBFS in debian 12.2 because of this bug
> affects 1055598 src:androguard
Bug #1055598 {Done: Santiago Vila } [src:oscrypto] 
oscrypto: FTBFS in bookworm (Error detecting the version of libcrypto)
Added indication that 1055598 affects src:androguard
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
1055598: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1055598
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#1057309: src:haskell-pandoc binary package names conflict with src:pandoc binary packages

[Scott Talbert]

reassign -1 src:pandoc
affects -1 src:haskell-pandoc

On Sun, 3 Dec 2023, Hannes von Haugwitz wrote:


Source: haskell-pandoc
Version: 3.0.1-2
Severity: serious
Control: affects -1 src:pandoc

Hi,

The binary packages provided by src:haskell-pandoc conflict with the
binary packages of src:pandoc; violationg Debian Policy 3.1 ("Every
package must have a name that’s unique within the Debian archive.").

This also makes the pandoc binary package from src:pandoc uninstallable
in unstable:


# apt policy pandoc pandoc-data
pandoc:
 Installed: (none)
 Candidate: 2.17.1.1-3
 Version table:
2.17.1.1-3 500
   500 mirror+file:/etc/apt/mirrors/debian.list unstable/main amd64 Packages
pandoc-data:
 Installed: (none)
 Candidate: 3.0.1-2
 Version table:
3.0.1-2 500
   500 mirror+file:/etc/apt/mirrors/debian.list unstable/main amd64 Packages
2.17.1.1-3 500
   500 mirror+file:/etc/apt/mirrors/debian.list unstable/main amd64 Packages

# apt install pandoc
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
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:
pandoc : Depends: pandoc-data (< 2.17.1.1-3.~) but 3.0.1-2 is to be installed
E: Unable to correct problems, you have held broken packages.


As a workaround you can specify the matching version of pandoc-data:

# apt install pandoc pandoc-data=2.17.1.1-3


Yes, this is expected (temporarily).  pandoc has been refactored upstream 
and has been separated into a library and a cli package. 
src:haskell-pandoc will now provide the library and data packages, while 
src:pandoc needs to be updated to just provide the cli package.


Regards,
Scott

Processed: Re: Bug#1000044: ccze: depends on obsolete pcre3 library

[Debian Bug Tracking System]

Processing control commands:

> tags -1 + patch
Bug #144 [src:ccze] ccze: depends on obsolete pcre3 library
Added tag(s) patch.

-- 
144: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=144
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#1000044: ccze: depends on obsolete pcre3 library

[Yavor Doganov]

Control: tags -1 + patch

Please find a patch attached (I was not able to test all plugins).
>From 1b55bb243cb69c8f1ce006f237187eca7fb47793 Mon Sep 17 00:00:00 2001
From: Yavor Doganov 
Date: Sun, 3 Dec 2023 20:13:33 +0200
Subject: [PATCH] Port to PCRE2 (#144)

---
 debian/changelog   |7 +
 debian/control |2 +-
 debian/patches/pcre2.patch | 2807 
 debian/patches/series  |1 +
 4 files changed, 2816 insertions(+), 1 deletion(-)
 create mode 100644 debian/patches/pcre2.patch

diff --git a/debian/changelog b/debian/changelog
index 9e9de97..95eb7a5 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,10 @@
+ccze (0.2.1-8) UNRELEASED; urgency=medium
+
+  * debian/patches/pcre2.patch: New; port to PCRE2 (Closes: #144).
+  * debian/control (Build-Depends): Replace libpcre3-dev with libpcre2-dev.
+
+ -- Yavor Doganov   Sun, 03 Dec 2023 20:00:06 +0200
+
 ccze (0.2.1-7) unstable; urgency=medium
 
   * Update debian/watch AGAIN with regards to Github changes.
diff --git a/debian/control b/debian/control
index 895d45e..2b67dd6 100644
--- a/debian/control
+++ b/debian/control
@@ -5,7 +5,7 @@ Maintainer: Axel Beckert 
 Standards-Version: 4.6.0
 Build-Depends: debhelper-compat (= 13),
libncurses5-dev,
-   libpcre3-dev
+   libpcre2-dev
 Vcs-Git: https://salsa.debian.org/debian/ccze.git
 Vcs-Browser: https://salsa.debian.org/debian/ccze
 Homepage: https://github.com/madhouse/ccze
diff --git a/debian/patches/pcre2.patch b/debian/patches/pcre2.patch
new file mode 100644
index 000..6b60dc8
--- /dev/null
+++ b/debian/patches/pcre2.patch
@@ -0,0 +1,2807 @@
+Description: Port to PCRE2.
+Bug-Debian: https://bugs.debian.org/144
+Author: Yavor Doganov 
+Forwarded: no
+Last-Update: 2023-12-03
+---
+
+--- ccze.orig/configure.ac
 ccze/configure.ac
+@@ -102,14 +102,14 @@
+ AC_CHECK_FUNC(getopt_long, [], [AC_CHECK_LIB(gnugetopt, getopt_long)])
+ 
+ if test -z "${PCRE_CONFIG}"; then
+-	AC_PATH_PROG(PCRE_CONFIG, pcre-config, no)
++	AC_PATH_PROG(PCRE_CONFIG, pcre2-config, no)
+ fi
+ AC_MSG_CHECKING(for PCRE)
+ if test "${PCRE_CONFIG}" = "no"; then
+ 	AC_ERROR(PCRE not found)
+ fi
+ PCRE_CFLAGS=$($PCRE_CONFIG --cflags)
+-PCRE_LIBS=$($PCRE_CONFIG --libs)
++PCRE_LIBS=$($PCRE_CONFIG --libs8)
+ AC_SUBST(PCRE_CFLAGS)
+ AC_SUBST(PCRE_LIBS)
+ AC_MSG_RESULT(found)
+--- ccze.orig/src/ccze-wordcolor.c
 ccze/src/ccze-wordcolor.c
+@@ -29,9 +29,9 @@
+ #include "ccze-private.h"
+ #include "ccze-compat.h"
+ 
+-static pcre *reg_pre, *reg_post, *reg_host, *reg_mac, *reg_email;
+-static pcre *reg_uri, *reg_size, *reg_ver, *reg_time, *reg_addr;
+-static pcre *reg_num, *reg_sig, *reg_email2, *reg_hostip, *reg_msgid;
++static pcre2_code *reg_pre, *reg_post, *reg_host, *reg_mac, *reg_email;
++static pcre2_code *reg_uri, *reg_size, *reg_ver, *reg_time, *reg_addr;
++static pcre2_code *reg_num, *reg_sig, *reg_email2, *reg_hostip, *reg_msgid;
+ 
+ static char *words_bad[] = {
+   "warn", "restart", "exit", "stop", "end", "shutting", "down", "close",
+@@ -71,33 +71,31 @@
+ void
+ ccze_wordcolor_process_one (char *word, int slookup)
+ {
+-  size_t wlen;
+-  int offsets[99];
++  size_t wlen, l;
+   ccze_color_t col;
+-  int match, printed = 0;
++  int printed = 0;
+   char *pre = NULL, *post = NULL, *tmp, *lword;
++  pcre2_match_data *offsets;
+ 
+   col = CCZE_COLOR_DEFAULT;
+ 
++  offsets = pcre2_match_data_create (99, NULL);
++
+   /** prefix **/
+-  if ((match = pcre_exec (reg_pre, NULL, word, strlen (word), 0, 0,
+-			  offsets, 99)) >= 0)
++  if (pcre2_match (reg_pre, word, strlen (word), 0, 0, offsets, NULL) >= 0)
+ {
+-  pcre_get_substring (word, offsets, match, 1, (const char **)&pre);
+-  pcre_get_substring (word, offsets, match, 2, (const char **)&tmp);
+-  free (word);
++  pcre2_substring_get_bynumber (offsets, 1, (unsigned char **)&pre, &l);
++  pcre2_substring_get_bynumber (offsets, 2, (unsigned char **)&tmp, &l);
+   word = tmp;
+ }
+   else
+ pre = NULL;
+ 
+   /** postfix **/
+-  if ((match = pcre_exec (reg_post, NULL, word, strlen (word), 0, 0,
+-			  offsets, 99)) >= 0)
++  if (pcre2_match (reg_post, word, strlen (word), 0, 0, offsets, NULL) >= 0)
+ {
+-  pcre_get_substring (word, offsets, match, 1, (const char **)&tmp);
+-  pcre_get_substring (word, offsets, match, 2, (const char **)&post);
+-  free (word);
++  pcre2_substring_get_bynumber (offsets, 1, (unsigned char **)&tmp, &l);
++  pcre2_substring_get_bynumber (offsets, 2, (unsigned char **)&post, &l);
+   word = tmp;
+ }
+   else
+@@ -107,45 +105,45 @@
+   lword = _stolower (word);
+   
+   /** Host **/
+-  if (pcre_exec (reg_host, NULL, lword, wlen, 0, 0, offsets, 99) >= 0)
++  if (pcre2_match (reg_host, lword, wlen, 0, 0, offsets, NULL) >= 0)
+ col = CCZE_COLOR_HOST;
+   /** MAC address **/
+-  else if (pcre_exec (reg_mac, NULL, lword, wlen, 0, 0, offsets, 99) >= 0)
++  else 

Bug#1057190: libhackrf0: udev rules file lost in upgrade

[Helmut Grohne]

Hi Maitland,

On Sat, Dec 02, 2023 at 10:57:40AM -0500, Maitland Bottoms wrote:
> Helmut Grohne  writes:
> 
> > Then when you retry it, please go for experimental first. Then have
> > Chris or me check your upload is ok and only then proceed with uploading
> > to unstable.
> 
> hackrf_2023.01.1-6 now in experimental is the retry with upstream
> updates and the udev rules handling.

This is the earlier reproducer adapted for experimental:

mmdebstrap trixie /dev/null http://deb.debian.org/debian --architectures 
amd64,i386 --include=libhackrf0:amd64,libhackrf0:i386 --customize-hook='sed -i 
-e s/trixie/experimental/ "$1/etc/apt/sources.list"' 
--chrooted-customize-hook="apt update" --chrooted-customize-hook="apt-get 
download -t experimental libhackrf0" --chrooted-customize-hook="dpkg 
--auto-deconfigure --unpack /*.deb" --chrooted-customize-hook="dpkg -r 
libhackrf0:i386" --chrooted-customize-hook="dpkg --configure -a" 
--customize-hook='test -e "$1/lib/udev/rules.d/60-libhackrf0.rules"'

It now succeeds. If you run it, you also see the protective diversion
being created and removed now:

| I: running --chrooted-customize-hook in shell: sh -c 'apt-get download -t 
experimental libhackrf0'
| Get:1 http://deb.debian.org/debian experimental/main amd64 libhackrf0 amd64 
2023.01.1-6 [17.5 kB]
| Fetched 17.5 kB in 0s (197 kB/s)  
| W: Download is performed unsandboxed as root as file 
'//libhackrf0_2023.01.1-6_amd64.deb' couldn't be accessed by user '_apt'. - 
pkgAcquire::Run (13: Permission denied)
| I: running --chrooted-customize-hook in shell: sh -c 'dpkg --auto-deconfigure 
--unpack /*.deb'
| (Reading database ... 10384 files and directories currently installed.)
| Preparing to unpack .../libhackrf0_2023.01.1-6_amd64.deb ...
| De-configuring libhackrf0:i386 (2023.01.1-2), to allow configuration of 
libhackrf0:amd64 (2023.01.1-6) ...
| Adding 'diversion of /lib/udev/rules.d/60-libhackrf0.rules to 
/lib/udev/rules.d/60-libhackrf0.rules.usr-is-merged by usr-is-merged'
| Unpacking libhackrf0:amd64 (2023.01.1-6) over (2023.01.1-2) ...
| Processing triggers for libc-bin (2.37-12) ...
| I: running --chrooted-customize-hook in shell: sh -c 'dpkg -r libhackrf0:i386'
| (Reading database ... 10389 files and directories currently installed.)
| Removing libhackrf0:i386 (2023.01.1-2) ...
| Processing triggers for libc-bin (2.37-12) ...
| I: running --chrooted-customize-hook in shell: sh -c 'dpkg --configure -a'
| Setting up libhackrf0:amd64 (2023.01.1-6) ...
| Removing 'diversion of /lib/udev/rules.d/60-libhackrf0.rules to 
/lib/udev/rules.d/60-libhackrf0.rules.usr-is-merged by usr-is-merged'
| Processing triggers for libc-bin (2.37-12) ...
| I: running --customize-hook in shell: sh -c 'test -e 
"$1/lib/udev/rules.d/60-libhackrf0.rules"' exec /tmp/mmdebstrap.NH48tKvp88

Also dumat (Debain Usr Merge Analysis Tool) noticed the
package without reporting any issues.

> Thanks for your attention on this, indeed my lack of attention before
> making uploads is the problem. I am happier with -6 though.

Shit happens. Thanks for quickly resolving the issue. Please go ahead
for unstable.

Helmut

Bug#1057338: sddm FTBFS: systemd.pc moved the upstream unit to /usr

[Helmut Grohne]

Source: sddm
Version: 0.20.0-1
Severity: serious
Tags: ftbfs patch
User: helm...@debian.org
Usertags: dep17m2

Hi,

I'm sorry for having noticed this late. When we changed the way
systemd.pc places systemd units, we did a partial archive rebuild and
missed out on sddm. On Nov 30th, the changed systemd was uploaded and
ssdm FTBFS since. The upstream unit is now installed to /usr, which
makes debian/rules fail to delete it and this trips up dh_missing. I've
got a patch for you to delete both locations for now. You may delete the
old location once you are sure that you don't want to backport to
bookworm anymore.

Helmut
diff --minimal -Nru sddm-0.20.0/debian/changelog sddm-0.20.0/debian/changelog
--- sddm-0.20.0/debian/changelog2023-06-24 08:38:52.0 +0200
+++ sddm-0.20.0/debian/changelog2023-12-03 07:36:33.0 +0100
@@ -1,3 +1,10 @@
+sddm (0.20.0-1.1) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Fix FTBFS: Also ignore /usr-moved upstream systemd unit. (Closes: #-1)
+
+ -- Helmut Grohne   Sun, 03 Dec 2023 07:36:33 +0100
+
 sddm (0.20.0-1) unstable; urgency=medium
 
   [ Aurélien COUDERC ]
diff --minimal -Nru sddm-0.20.0/debian/rules sddm-0.20.0/debian/rules
--- sddm-0.20.0/debian/rules2023-02-20 22:44:19.0 +0100
+++ sddm-0.20.0/debian/rules2023-12-03 07:36:31.0 +0100
@@ -30,7 +30,7 @@
 
 execute_after_dh_auto_install:
# not installed, as the Debian version is used instead
-   rm -f $(CURDIR)/debian/tmp/lib/systemd/system/sddm.service
+   rm -f $(CURDIR)/debian/tmp/lib/systemd/system/sddm.service 
$(CURDIR)/debian/tmp/usr/lib/systemd/system/sddm.service
 
 execute_after_dh_fixperms-arch:
# ensure script is marked as executable

Bug#1051877: marked as done (rust-libgit2-sys: please prepare for libgit2 transition)

[Debian Bug Tracking System]

Your message dated Sun, 03 Dec 2023 18:26:15 +
with message-id 
and subject line Bug#1051877: fixed in rust-libgit2-sys 0.16.1-1
has caused the Debian Bug report #1051877,
regarding rust-libgit2-sys: please prepare for libgit2 transition
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
1051877: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1051877
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: rust-libgit2-sys
Version: 0.14.1-1
Severity: normal

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Dear maintainer,

I have uploaded libgit2 1.7.1 to experimental and want to start the
transition for unstable soon. Like many other language bindings for
libgit2, the rust-libgit2-sys package needs to be upgraded in lock-step.

I suggest you upload version 0.16.1+1.7.1 to experimental first, so we can
check for potential regressions, but we can skip that step if you think
it is not necessary. I will start the transition once all language
bindings are ready.


Cheers
Timo


-BEGIN PGP SIGNATURE-

iQGzBAEBCgAdFiEEJvtDgpxjkjCIVtam+C8H+466LVkFAmUCG+4ACgkQ+C8H+466
LVmf+AwA0iNOBlUtNTVlSQXsnqfo1WnluQcI/RPJT0kPhtC4Zf3s6xncUSDnEmZc
1RTS6kalw64my9iq6usa9hnJxgl8NcZ3jPUQq1AOGgTnh6YmRBhlRIeci/7Z8Ivf
fL6iWeCrHevXBPL/lu9nLcSrUhJDkgmpqfjYMnXAVkvkSrfTJ0H3l6GF5EE2GbE9
SLq92UhqhHeqGLuozPJYMSHx4ySPDIa/p0IHYpBk9X1QONhMtTT07YQZ2JZKN2bo
OJg6MyQH7A/TOgKHJlk7lLcIzmQemim7badOBpbTe5a1157eRaBKIUC36cSx35fS
YZJbrx/7DdQO2CaT7urbaQtzF8tfRKH8JdpNfDAm5PmTFDZUzQcreVqW9BYlp/YR
svl9YZqnjhHzK0TpiXVdqBOLtwFwL4pZF5JvrmqQuI4uLxVCB4ZtR27uLmZMSERv
0FptK2JS5flvfI1j0kxzu1bzXzNTQdBohNYLUN6pbONvuOjrNVFQvDZ5KvCSKXv6
XB4xvEjK
=hYqx
-END PGP SIGNATURE-
--- End Message ---
--- Begin Message ---
Source: rust-libgit2-sys
Source-Version: 0.16.1-1
Done: Peter Michael Green 

We believe that the bug you reported is fixed in the latest version of
rust-libgit2-sys, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 1051...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Peter Michael Green  (supplier of updated rust-libgit2-sys 
package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sun, 03 Dec 2023 12:43:37 +
Source: rust-libgit2-sys
Architecture: source
Version: 0.16.1-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Rust Maintainers 

Changed-By: Peter Michael Green 
Closes: 1051877
Changes:
 rust-libgit2-sys (0.16.1-1) unstable; urgency=medium
 .
   * Team upload.
   * Package libgit2-sys 0.16.1+1.7.1 from crates.io using debcargo 2.6.1
   * Update Debian dependencies on libgit2 library (Closes: #1051877)
   * Update patches for new upstream.
Checksums-Sha1:
 facde4615a22ec9e9c0263bdf14207121a5b6cc7 2513 rust-libgit2-sys_0.16.1-1.dsc
 c8a7d75f871457b67d95dde92b4c3fe12b3a803f 32003 
rust-libgit2-sys_0.16.1.orig.tar.gz
 1cca60da46b618a9f7771d587c0914eeaeb7caf9 4220 
rust-libgit2-sys_0.16.1-1.debian.tar.xz
 c1281c473eb642a9e9aef004b523dcdc9a4ce2b4 8387 
rust-libgit2-sys_0.16.1-1_source.buildinfo
Checksums-Sha256:
 e0d749cb73fcd92bfb9a1702e40d2ce9969b56940d83017235bb22fe3badf914 2513 
rust-libgit2-sys_0.16.1-1.dsc
 9d2cc75108462f30973ccc20a54e7e13bd51cea9bc43a383f2562fb5b248d1a5 32003 
rust-libgit2-sys_0.16.1.orig.tar.gz
 45cc0d4e15c1b3f79f6d3053d802636814ac65a88214ec56c576b2c70c1a27ef 4220 
rust-libgit2-sys_0.16.1-1.debian.tar.xz
 f8fbd5a08e32bb74d6d67c20043fa6b3ada25c672f4f2179b3d3cb3a3ff8c9b8 8387 
rust-libgit2-sys_0.16.1-1_source.buildinfo
Files:
 b8cc981b90db7dcd97070101dc2cce4b 2513 rust optional 
rust-libgit2-sys_0.16.1-1.dsc
 cebf1893fb98f9d9032c09aa4715a0c4 32003 rust optional 
rust-libgit2-sys_0.16.1.orig.tar.gz
 73dccc1e9b21d38ed46a647e19d5a707 4220 rust optional 
rust-libgit2-sys_0.16.1-1.debian.tar.xz
 30b70eedae9dfedfadac9891fb720b45 8387 rust optional 
rust-libgit2-sys_0.16.1-1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJIBAEBCAAyFiEEU0DQATYMplbjSX63DEjqKnqP/XsFAmVswiEUHHBsdWd3YXNo
QGRlYmlhbi5vcmcACgkQDEjqKnqP/XsLsg//UotFK2FV1xKsKy9R7H3aXvc2fwvc
uuHZeFher4HJEJd10fiw0b7jYjI2apG74tnhx0tilNjonI3IIIS5ntrnv6nI4stm
lyC+ZXAPi81uiYekkbelx1o/enS0ifyxiJ0loD3XKd4kA1EfB5+g9s2wAo1xFgOJ
4rdtX/ie32WJaeocPMtGVFyTiUMh

Bug#1055253: amanda: diff for NMU version 1:3.5.1-11.1

[Jose M Calhariz]

Thank you for your work.  No need for the delay. 

Kind regards.
Jose M Calhariz


On December 3, 2023 1:14:09 PM GMT+00:00, Tobias Frost  wrote:
>Control: tags 1055253 + patch
>Control: tags 1055253 + pending
>
>Dear maintainer,
>
>I've prepared an NMU for amanda (versioned as 1:3.5.1-11.1) and
>uploaded it to DELAYED/5. Please feel free to tell me if I
>should delay it longer.
>
>Regards.
>

Processed: Bug#1042609 marked as pending in sphinxcontrib-mermaid

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1042609 {Done: Carsten Schoenert } 
[src:sphinxcontrib-mermaid] sphinxcontrib-mermaid: FTBFS with Sphinx 7.1, 
docutils 0.20: Could not import sphinx.util.SphinxParallelError (exception: No 
module named 'sphinx.util.SphinxParallelError')
Added tag(s) pending.

-- 
1042609: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1042609
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#1042609: marked as pending in sphinxcontrib-mermaid

[Carsten Schoenert]

Control: tag -1 pending

Hello,

Bug #1042609 in sphinxcontrib-mermaid 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/python-team/packages/sphinxcontrib-mermaid/-/commit/13670cdee62562c3fd74643f81639fa0dd449c1a


Rebuild patches from patch queue branch

Added patches:
README.rst-Adopt-autoclasstree-examples-to-Sphinx-7.2.patch
autoclassdiag.py-Use-sphinx.errors-for-importing.patch

Closes: #1042609


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1042609

Bug#1042609: marked as done (sphinxcontrib-mermaid: FTBFS with Sphinx 7.1, docutils 0.20: Could not import sphinx.util.SphinxParallelError (exception: No module named 'sphinx.util.SphinxParallelError'

[Debian Bug Tracking System]

Your message dated Sun, 03 Dec 2023 18:07:16 +
with message-id 
and subject line Bug#1042609: fixed in sphinxcontrib-mermaid 0.9.2-2
has caused the Debian Bug report #1042609,
regarding sphinxcontrib-mermaid: FTBFS with Sphinx 7.1, docutils 0.20: Could 
not import sphinx.util.SphinxParallelError (exception: No module named 
'sphinx.util.SphinxParallelError')
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
1042609: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1042609
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: sphinxcontrib-mermaid
Version: 0.9.2-1
Severity: important
Tags: ftbfs
User: python-modules-t...@lists.alioth.debian.org
Usertags: sphinx7.1

Hi,

sphinxcontrib-mermaid fails to build with Sphinx 7.1 and docutils 0.20, both of 
which
are currently available in experimental.

Relevant part (hopefully):
>  debian/rules binary
> dh binary --buildsystem=pybuild
>dh_update_autotools_config -O--buildsystem=pybuild
>dh_autoreconf -O--buildsystem=pybuild
>dh_auto_configure -O--buildsystem=pybuild
> I: pybuild base:240: python3.11 setup.py config 
> /usr/lib/python3/dist-packages/setuptools/dist.py:945: 
> SetuptoolsDeprecationWarning: The namespace_packages parameter is deprecated.
> !!
> 
> 
> 
> Please replace its usage with implicit namespaces (PEP 420).
> 
> See 
> https://setuptools.pypa.io/en/latest/references/keywords.html#keyword-namespace-packages
>  for details.
> 
> 
> 
> !!
>   ep.load()(self, ep.name, value)
> running config
>dh_auto_build -O--buildsystem=pybuild
> I: pybuild base:240: /usr/bin/python3 setup.py build 
> /usr/lib/python3/dist-packages/setuptools/dist.py:945: 
> SetuptoolsDeprecationWarning: The namespace_packages parameter is deprecated.
> !!
> 
> 
> 
> Please replace its usage with implicit namespaces (PEP 420).
> 
> See 
> https://setuptools.pypa.io/en/latest/references/keywords.html#keyword-namespace-packages
>  for details.
> 
> 
> 
> !!
>   ep.load()(self, ep.name, value)
> running build
> running build_py
> creating /<>/.pybuild/cpython3_3.11/build/sphinxcontrib
> copying sphinxcontrib/mermaid.py -> 
> /<>/.pybuild/cpython3_3.11/build/sphinxcontrib
> copying sphinxcontrib/__init__.py -> 
> /<>/.pybuild/cpython3_3.11/build/sphinxcontrib
> copying sphinxcontrib/exceptions.py -> 
> /<>/.pybuild/cpython3_3.11/build/sphinxcontrib
> copying sphinxcontrib/autoclassdiag.py -> 
> /<>/.pybuild/cpython3_3.11/build/sphinxcontrib
> running egg_info
> creating sphinxcontrib_mermaid.egg-info
> writing sphinxcontrib_mermaid.egg-info/PKG-INFO
> writing dependency_links to 
> sphinxcontrib_mermaid.egg-info/dependency_links.txt
> writing namespace_packages to 
> sphinxcontrib_mermaid.egg-info/namespace_packages.txt
> writing top-level names to sphinxcontrib_mermaid.egg-info/top_level.txt
> writing manifest file 'sphinxcontrib_mermaid.egg-info/SOURCES.txt'
> reading manifest file 'sphinxcontrib_mermaid.egg-info/SOURCES.txt'
> reading manifest template 'MANIFEST.in'
> warning: no previously-included files matching '*.pyc' found anywhere in 
> distribution
> warning: no previously-included files found matching '.gitignore'
> adding license file 'LICENSE.rst'
> writing manifest file 'sphinxcontrib_mermaid.egg-info/SOURCES.txt'
> I: pybuild pybuild:333: PYTHONPATH=/<>/.pybuild/cpython3_3.11 
> python3 -m sphinx -b html -N -D html_last_updated_fmt="11 June 2023" docs/ 
> build/html; PYTHONPATH=/<>/.pybuild/cpython3_3.11 python3 -m 
> sphinx -b man -N -D html_last_updated_fmt="11 June 2023" docs/ build/man; cp 
> debian/external-graphics/directive.gif build/html
> Running Sphinx v7.1.1
> making output directory... done
> building [mo]: targets for 0 po files that are out of date
> writing output... 
> building [html]: targets for 2 source files that are out of date
> updating environment: [new config] 2 added, 0 changed, 0 removed
> reading sources... [ 50%] index
> 
> Mermaid error:
> Could not import sphinx.util.SphinxParallelError (exception: No module named 
> 'sphinx.util.SphinxParallelError')
> Running Sphinx v7.1.1
> making output directory... done
> building [mo]: targets for 0 po files that are out of date
> writing output... 
> building [man]: all manpa

Bug#1055147: seahorse-adventures: No keypress recognised

[Markus Koschany]

Hi Francesco,

Am Sonntag, dem 03.12.2023 um 17:42 +0100 schrieb Francesco Ariis:
> Il 03 dicembre 2023 alle 17:14 Markus Koschany ha scritto:
> > I spoke too soon. Tested the wrong Debian release. So it appears the
> > underlying
> > problem is in python3-pygame which changed significantly between Bullseye
> > and
> > Bookworm but I'm not sure how I can fix this in seahorse-adventures right
> > now. 
> 
> I managed to get keydown working like this:
> - in /usr/share/games/seahorse-adventures/lib/menu.py
> - go to line 119
> - substitute
>     if e.type is USEREVENT and e.action == 'down':
>   with
>     if e.type == USEREVENT and e.action == 'down':
> - keydown will work again

Thanks a lot for the report and your proposed patch. As soon as I'm back home
tomorrow, I'll give it a try. Thanks for mentioning the other seahorse-
adventures fork. Maybe there are even more improvements. I'll check that too.

Best,

Markus



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

Bug#1055253: marked as done (amanda: CVE-2023-30577)

[Debian Bug Tracking System]

Your message dated Sun, 03 Dec 2023 17:02:08 +
with message-id 
and subject line Bug#1055253: fixed in amanda 1:3.5.1-11+deb12u1
has caused the Debian Bug report #1055253,
regarding amanda: CVE-2023-30577
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
1055253: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1055253
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: amanda
Version: 1:3.5.1-11
Severity: grave
Tags: security upstream
Forwarded: https://github.com/zmanda/amanda/pull/228
X-Debbugs-Cc: car...@debian.org, Debian Security Team 
Control: found -1 1:3.5.1-7

Hi,

The following vulnerability was published for amanda.

CVE-2023-30577[0]:
| AMANDA (Advanced Maryland Automatic Network Disk Archiver) before
| tag-community-3.5.4 mishandles argument checking for runtar.c, a
| different vulnerability than CVE-2022-37705.


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

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2023-30577
https://www.cve.org/CVERecord?id=CVE-2023-30577
[1] https://github.com/zmanda/amanda/security/advisories/GHSA-crrw-v393-h5q3
[2] https://github.com/zmanda/amanda/pull/228

Regards,
Salvatore
--- End Message ---
--- Begin Message ---
Source: amanda
Source-Version: 1:3.5.1-11+deb12u1
Done: Tobias Frost 

We believe that the bug you reported is fixed in the latest version of
amanda, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 1055...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Tobias Frost  (supplier of updated amanda package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sun, 03 Dec 2023 14:17:07 +0100
Source: amanda
Architecture: source
Version: 1:3.5.1-11+deb12u1
Distribution: bookworm
Urgency: high
Maintainer: Jose M Calhariz 
Changed-By: Tobias Frost 
Closes: 1055253
Changes:
 amanda (1:3.5.1-11+deb12u1) bookworm; urgency=high
 .
   * Non-maintainer upload by the Security Team.
   * Apply upstream fix for CVE-2023-30577 (Closes: #1055253)
Checksums-Sha1:
 40a5a6f5c4bb2d41ff90f9593b03e1b2e04bc724 2248 amanda_3.5.1-11+deb12u1.dsc
 a92fa595ad525e3cc86565a81353220c146a0ac4 5239952 amanda_3.5.1.orig.tar.gz
 ccc40ea5ce937f5cb87557f5ec5b795ad399d9d4 59616 
amanda_3.5.1-11+deb12u1.debian.tar.xz
 d8371c3607e6d86c260efc7680b2d931c56d1b90 15803 
amanda_3.5.1-11+deb12u1_amd64.buildinfo
Checksums-Sha256:
 8d90cf85be217e721566b9d1deca7899966598203a1554dc75bf17a48bc5d1b4 2248 
amanda_3.5.1-11+deb12u1.dsc
 6cb9a13fb7a09970d288ddb2c380e7165c5fe38b85bc761ca7ffe334bc5c534b 5239952 
amanda_3.5.1.orig.tar.gz
 c05e264b27f28ab9903554619ecec29109deaac6983f3923251bfa424a5e008d 59616 
amanda_3.5.1-11+deb12u1.debian.tar.xz
 09d761eb6f8086ec18a427b275e4c236ba631492bc7c5e8496296df73ca0cd4f 15803 
amanda_3.5.1-11+deb12u1_amd64.buildinfo
Files:
 d0da15ca741d7e567d71dd86d2b1d50c 2248 utils optional 
amanda_3.5.1-11+deb12u1.dsc
 a780f158cbbacfb017ce4a519120b772 5239952 utils optional 
amanda_3.5.1.orig.tar.gz
 0477dbf456a5fec4f1c540330d49a08c 59616 utils optional 
amanda_3.5.1-11+deb12u1.debian.tar.xz
 3322511674fd8f15f38a8538f37a9ed5 15803 utils optional 
amanda_3.5.1-11+deb12u1_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEE/d0M/zhkJ3YwohhskWT6HRe9XTYFAmVsg+AACgkQkWT6HRe9
XTYE3BAAlFF01XhEq0bbgAerLJCG4llVbjRGGORS30GbWTgVnPBsTGXmeUEzUlQf
z7f215uZijIg385ybRXfdKSYbKyYVjpX7+ccpWd2hT+qXNBxJ0qdwqAesZc7qbYq
udZHmBd0Sv3N1c0oGI0Sx9D5JPiKn7UuFFoZceRtVmGCEBoMC2d1OLM3/1ty3w15
6IjNhQeSZQvV6f551yR2MkcnCTdsJeHjf5YpPEiZO0Dor7Yu8MG1U9MicfC/y/+W
SBVDj4vJS+vVHru43L6KksdPtdQJNYVLYYBKs7s8K70EBRGbjGUcYfSK0s4Q7N4r
qYCLAsIdS9ocTei+zIE64f65ycV79IzrZP4xa1DGDZY46c02OGvOhU6FakV26hRB
30nGWk4AL/E4T2gghE0E/hhNHi3jpyXEHghy1hakfDB656Ha7dktBqDuCbaRRQzK
EYVFSomEEtoXBb0NSTG4YbcMLtiPlfVq0xNB4SpRYT7Pe1BRTQ+mxGDeDmYrVbmA
cY1l6FxVhIKP7QVIiQGu427zsEq1FgQPsfXIycvhWTa0gbRCmfSqwrF/iyIbPd8b
eeurDGrg6Wl/Qw1ItVcQGuKAy+z9G1MQenpWOe0r+RumWBzEAGUsxW8Mj8lIc0HI
1/OZfRmrYJ2Wh3CwAqeyAhRxxDA47qPN9VlOHDh58p7j3WKN684=
=uR7h
-END PGP SIGNATURE End Message ---

Bug#1055144: marked as done (nvidia-open-gpu-kernel-modules: CVE-2023-31022)

[Debian Bug Tracking System]

Your message dated Sun, 03 Dec 2023 17:02:09 +
with message-id 
and subject line Bug#1055144: fixed in nvidia-open-gpu-kernel-modules 
525.147.05-1~deb12u1
has caused the Debian Bug report #1055144,
regarding nvidia-open-gpu-kernel-modules: CVE-2023-31022
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
1055144: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1055144
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: nvidia-graphics-drivers
Severity: normal
Tags: security
X-Debbugs-Cc: Debian Security Team 
Control: clone -1 -2 -3 -4 -5 -6 -7 -8 -9
Control: reassign -2 src:nvidia-graphics-drivers-legacy-340xx 340.76-6
Control: retitle -2 nvidia-graphics-drivers-legacy-340xx: CVE-2023-31022
Control: tag -2 + wontfix
Control: reassign -3 src:nvidia-graphics-drivers-legacy-390xx 390.48-4
Control: retitle -3 nvidia-graphics-drivers-legacy-390xx: CVE-2023-31022
Control: tag -3 + wontfix
Control: reassign -4 src:nvidia-graphics-drivers-tesla-418 418.87.01-1
Control: retitle -4 nvidia-graphics-drivers-tesla-418: CVE-2023-31022
Control: tag -4 + wontfix
Control: reassign -5 src:nvidia-graphics-drivers-tesla-450 450.51.05-1
Control: retitle -5 nvidia-graphics-drivers-tesla-450: CVE-2023-31022
Control: tag -5 + wontfix
Control: reassign -6 src:nvidia-graphics-drivers-tesla-460 460.32.03-1
Control: retitle -6 nvidia-graphics-drivers-tesla-460: CVE-2023-31022
Control: tag -6 + wontfix
Control: close -6 460.106.00-3
Control: reassign -7 src:nvidia-graphics-drivers-tesla-470 470.57.02-1
Control: retitle -7 nvidia-graphics-drivers-tesla-470: CVE-2023-31022
Control: reassign -8 src:nvidia-graphics-drivers-tesla 510.85.02-1
Control: retitle -8 nvidia-graphics-drivers-tesla: CVE-2023-31022
Control: found -8 515.48.07-1
Control: found -8 525.60.13-1
Control: found -8 535.54.03-1
Control: reassign -9 src:nvidia-open-gpu-kernel-modules 515.43.04-1
Control: retitle -9 nvidia-open-gpu-kernel-modules: CVE-2023-31022
Control: found -9 520.56.06-1
Control: found -9 525.85.12-1
Control: found -9 530.30.02-1
Control: found -9 535.43.02-1
Control: found -9 545.23.06-1
Control: found -1 340.24-1
Control: found -1 343.22-1
Control: found -1 396.18-1
Control: found -1 430.14-1
Control: found -1 455.23.04-1
Control: found -1 465.24.02-1
Control: found -1 495.44-1
Control: found -1 515.48.07-1
Control: found -1 520.56.06-1
Control: found -1 525.53-1
Control: found -1 530.30.02-1
Control: found -1 535.43.02-1
Control: found -1 545.23.06-1

https://nvidia.custhelp.com/app/answers/detail/a_id/5491

CVE-2023-31022  NVIDIA GPU Display Driver for Windows and Linux contains
a vulnerability in the kernel mode layer, where a NULL-pointer
dereference may lead to denial of service.

Linux Driver Branch CVE IDs Addressed
R545, R535, R525, R470  CVE-2023-31022

Driver Branch   Affected Driver VersionsUpdated Driver 
Version
R545All driver versions prior to 545.29.02  545.29.02
R535All driver versions prior to 535.129.03 535.129.03
R525All driver versions prior to 525.147.05 525.147.05
R470All driver versions prior to 470.223.02 470.223.02


Andreas
--- End Message ---
--- Begin Message ---
Source: nvidia-open-gpu-kernel-modules
Source-Version: 525.147.05-1~deb12u1
Done: Andreas Beckmann 

We believe that the bug you reported is fixed in the latest version of
nvidia-open-gpu-kernel-modules, which is due to be installed in the Debian FTP 
archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 1055...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Andreas Beckmann  (supplier of updated 
nvidia-open-gpu-kernel-modules package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sun, 03 Dec 2023 12:31:14 +0100
Source: nvidia-open-gpu-kernel-modules
Architecture: source
Version: 525.147.05-1~deb12u1
Distribution: bookworm
Urgency: medium
Maintainer: Debian NVIDIA Maintainers 
Changed-By: Andreas Beckmann 
Closes: 1055144
Changes:
 nvidia-open-gpu-kernel-modules (525.147.05-1~deb12u1) bookworm; urgency=medium
 .
   * Rebuild for bookworm.
 .
 nvidia-open-gpu-kernel-modules (525.147.05-1) unstab

Bug#1037478: marked as done (ca-certificates-java: Loop in the execution of the trigger)

[Debian Bug Tracking System]

Your message dated Sun, 03 Dec 2023 17:02:09 +
with message-id 
and subject line Bug#1037478: fixed in ca-certificates-java 20230710~deb12u1
has caused the Debian Bug report #1037478,
regarding ca-certificates-java: Loop in the execution of the trigger
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
1037478: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1037478
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: ca-certificates-java
Version: 20230103
Severity: serious

Hello,

While updating today, I got the following error:

dpkg: boucle détectée durant le traitement des actions différées :
 listes des paquets qui en sont responsables (normalement) :
  ca-certificates-java -> ca-certificates-java
 paquets bloqués par le traitement impossible d'actions différées requises :
  ca-certificates-java: update-ca-certificates-java: /usr/lib/jvm
  libc-bin: ldconfig
  dictionaries-common: aspell-autobuildhash

There seems to be a loop in the trigger execution

Kind regards
Laurent Bigonville


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

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

Versions of packages ca-certificates-java depends on:
ii  ca-certificates   20230311
ii  openjdk-11-jre-headless [java8-runtime-headless]  11.0.19+7-1

ca-certificates-java recommends no packages.

ca-certificates-java suggests no packages.

-- Configuration Files:
/etc/default/cacerts [Errno 13] Permission non accordée: '/etc/default/cacerts'

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: ca-certificates-java
Source-Version: 20230710~deb12u1
Done: Andreas Beckmann 

We believe that the bug you reported is fixed in the latest version of
ca-certificates-java, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 1037...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Andreas Beckmann  (supplier of updated ca-certificates-java 
package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sun, 03 Dec 2023 13:04:00 +0100
Source: ca-certificates-java
Architecture: source
Version: 20230710~deb12u1
Distribution: bookworm
Urgency: medium
Maintainer: Debian Java Maintainers 

Changed-By: Andreas Beckmann 
Closes: 929685 1037478 1041419
Changes:
 ca-certificates-java (20230710~deb12u1) bookworm; urgency=medium
 .
   * Non-maintainer upload.
   * Rebuild for bookworm.  (Closes: #1041419, #1037478, #929685)
 .
 ca-certificates-java (20230710) unstable; urgency=medium
 .
   * Add apt-utils to the test dependencies.
 .
 ca-certificates-java (20230707) unstable; urgency=medium
 .
   [ Vladimir Petko ]
   * Resolve circular JRE dependency:
 - debian/ca-certificates-java.postinst: remove setup_path from "configure"
   stage.
 - debian/ca-certificates-java.postinst: do "fresh" update if cacerts file 
is
   not found. Certificates are refreshed only in response to the trigger
   activated by OpenJDK packages.
 - debian/ca-certificates-java.postinst: fix cacert enumeration command for
   Java 8.
 - debian/control: remove JRE dependency.
 - debian/control: add Breaks condition.
 - debian/tests: add smoke tests.
 - debian/ca-certificates-java.triggers: remove file trigger /usr/jvm,
   explicitly declare triggers as -await.
 .
   [ Matthias Klose ]
   * Adjust the breaks for Debian versions.
Checksums-Sha1:
 b0afb8371f70d001c7ad22988c396b2845b09cb8 1930 
ca-certificates-java_20230710~deb12u1.dsc
 3635f3e76b4e1eb7c147e7ad7c0664aa946a124c 18464 
ca-certificates-java_20230710~deb12u1.tar.xz
 f29171a22ce7c4183a34d1a5b3254315311cda78 9456 
ca-certificates-java_20230710~deb12u1_source.buildinfo
Checksums-Sha256:
 57a9912fef237a20f73f86abc348f36

Bug#1037192: marked as done (sd: version is lower than in squeeze)

[Debian Bug Tracking System]

Your message dated Sun, 03 Dec 2023 17:02:10 +
with message-id 
and subject line Bug#1037192: fixed in rust-sd 0.7.6-1+deb12u1
has caused the Debian Bug report #1037192,
regarding sd: version is lower than in squeeze
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
1037192: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1037192
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: sd
Version: 0.7.6-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

squeeze had a sd binary package built from (unrelated) src:sd at
version 0.74-1 while bookworm has one built from src:rust-sd at
version 0.7.6-1 which is lower, violating the archive property of
monotonically increasing version numbers.

The highest version of src:sd ever seen in the archive seems to be
0.75-1.

Andreas
--- End Message ---
--- Begin Message ---
Source: rust-sd
Source-Version: 0.7.6-1+deb12u1
Done: Andreas Beckmann 

We believe that the bug you reported is fixed in the latest version of
rust-sd, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 1037...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Andreas Beckmann  (supplier of updated rust-sd package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sun, 03 Dec 2023 13:09:59 +0100
Source: rust-sd
Architecture: source
Version: 0.7.6-1+deb12u1
Distribution: bookworm
Urgency: medium
Maintainer: Debian Rust Maintainers 

Changed-By: Andreas Beckmann 
Closes: 1037192
Changes:
 rust-sd (0.7.6-1+deb12u1) bookworm; urgency=medium
 .
   * Non-maintainer upload.
   * Prefix the version of the binary package with '0.80.really.' to sort
 between 0.74-1 in squeeze (from unrelated src:sd) and 1.0.0-1 in sid.
 (Closes: #1037192)
Checksums-Sha1:
 932709159ee6a1ce7a9b33fe976f332dee5b6444 2350 rust-sd_0.7.6-1+deb12u1.dsc
 e211d4aef2464a62c0c70b21ead39e332bb6ad11 3012 
rust-sd_0.7.6-1+deb12u1.debian.tar.xz
 e89ad98f67655939dcc66fc1f24ab4aeadc8a6c2 5 
rust-sd_0.7.6-1+deb12u1_source.buildinfo
Checksums-Sha256:
 d16e16b6339d749ae4e939817cfd80e033d6836fef2f54f4a236bc64b1d5e432 2350 
rust-sd_0.7.6-1+deb12u1.dsc
 e9c2b9cdfe241c94b93c95c269da4dc20d86fd8440df56c9edb9fa7b245f4127 3012 
rust-sd_0.7.6-1+deb12u1.debian.tar.xz
 c8d31fc3cfee033bd463c71d4b8dafd4d12dc5623b63445699f38425f99dda5d 5 
rust-sd_0.7.6-1+deb12u1_source.buildinfo
Files:
 5051560b53cbe5f546bc2d1b5ef5285e 2350 utils optional 
rust-sd_0.7.6-1+deb12u1.dsc
 4de5d95c76cb9611ffcab03434c105cf 3012 utils optional 
rust-sd_0.7.6-1+deb12u1.debian.tar.xz
 2fa3616668830a0008765c230e5babdf 5 utils optional 
rust-sd_0.7.6-1+deb12u1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJEBAEBCAAuFiEE6/MKMKjZxjvaRMaUX7M/k1np7QgFAmVscKAQHGFuYmVAZGVi
aWFuLm9yZwAKCRBfsz+TWentCKTZD/45dGFFEm7KL5lEaO8eWZUFuOtlC55/x60G
s8QNITylkysSthF8yaqfXzz2gcZDDMWGzm4/z/a4sd4g2IQAIogSDBmQmO4KTAYn
6GhbCMmy/nw8uyI6cN8kAgdl4HgL5sPQCM0zuhKWmXH6WZE9imcgK2nfbPEx9+ja
gE0NHCxCpaUjwCQS7ZQWXYhb1M09aAMkazUoxx/KA1fiIrwDv8W/cB08b1TcrKKb
7zuYtmXjt2AtFbMnpeB50lJvRVfzhqGEpPotF78u7A/OIEYMkEbqv7yGkbVM/H4O
NS4aMGRdd+bYVK0OgVlAPm0ymQx2hPnOcsUgaCadzAUaIU6IcOfjzdmatBsPs4t5
xLgIlu/y3WfdzJWuMIxNONcOf28MZspgUIePIUeWYaEMEmunPhmQ3+WA082ALLl9
KgoI2TS12WcKKNWpJuQQAQssUMhgeZD9Nyrow0Ch4o1rzXkiLysuXnfr0VTy9NDQ
uwRUmoeWyTUc6YNWjOf/C7tXkbNi9XPC44Zi521aznzjkX+pNtqK6XCuuBBF/iwO
1ii5qCSmCvvSxKQMeXizKj6D5FuBjnuMT2pfuSg8eV+pz+fYhyEqsWh/v9+3yjVo
E8nDbMv6F9N+EOKq3kDX1Vgu7DuGEXHHWy9nkDClK+o9G7QrKvdQXRr4KG42Cbpa
ciVNCYPH/w==
=w30G
-END PGP SIGNATURE End Message ---

Bug#1055147: seahorse-adventures: No keypress recognised

[Francesco Ariis]

Dear Markus,

Il 03 dicembre 2023 alle 15:31 Markus Koschany ha scritto:
> I could not reproduce your problem. The keys work as expected and I can
> navigate the menu and the game without any problems.

Before submitting the bug report I was also able to reproduce the bug
with another person in libera.chat/#debian (alas I forgot the handle
and the channel is not logged).
See also [1].

[1] https://bugs.launchpad.net/ubuntu/+source/seahorse-adventures/+bug/2038853

I don’t know what to do to help debug, but this fork [2] works on my machine
with `python3 run_game.py -full -scale2x`.

[2] https://github.com/dulsi/seahorse-adventures

Bug#1055147: seahorse-adventures: No keypress recognised

[Francesco Ariis]

Il 03 dicembre 2023 alle 17:14 Markus Koschany ha scritto:
> I spoke too soon. Tested the wrong Debian release. So it appears the 
> underlying
> problem is in python3-pygame which changed significantly between Bullseye and
> Bookworm but I'm not sure how I can fix this in seahorse-adventures right 
> now. 

I managed to get keydown working like this:
- in /usr/share/games/seahorse-adventures/lib/menu.py
- go to line 119
- substitute
if e.type is USEREVENT and e.action == 'down':
  with
if e.type == USEREVENT and e.action == 'down':
- keydown will work again

Processed: block 1057240 with 1057241 1057242 1057243 1057245 1057246 1057247 1057319 1057231 1056995

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> block 1057240 with 1057241 1057242 1057243 1057245 1057246 1057247 1057319 
> 1057231 1056995
Bug #1057240 [src:alsa-utils] alsa-utils: will FTBFS when udev.pc changes 
udevdir
1057240 was not blocked by any bugs.
1057240 was not blocking any bugs.
Added blocking bug(s) of 1057240: 1057246, 1057241, 1057242, 1057243, 1056995, 
1057319, 1057231, 1057247, and 1057245
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
1057240: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1057240
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: Re: Bug#1057318: libgit-raw-perl: FTBFS: Failed 2/42 test programs. 15/1768 subtests failed.

[Debian Bug Tracking System]

Processing control commands:

> tag -1 + confirmed
Bug #1057318 [src:libgit-raw-perl] libgit-raw-perl: FTBFS: Failed 2/42 test 
programs. 15/1768 subtests failed.
Added tag(s) confirmed.

-- 
1057318: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1057318
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#1057318: libgit-raw-perl: FTBFS: Failed 2/42 test programs. 15/1768 subtests failed.

[gregor herrmann]

Control: tag -1 + confirmed

On Sun, 03 Dec 2023 12:24:10 +0100, Sebastian Ramacher wrote:

> Source: libgit-raw-perl
> Version: 0.90+ds-1
> Severity: serious
> Tags: ftbfs sid trixie
> Justification: fails to build from source (but built successfully in the past)
> X-Debbugs-Cc: sramac...@debian.org
> 
> https://buildd.debian.org/status/fetch.php?pkg=libgit-raw-perl&arch=amd64&ver=0.90%2Bds-1%2Bb1&stamp=1701602200&raw=0
> 
> Test Summary Report
> ---
> t/08-branch.t (Wstat: 256 (exited 1) Tests: 34 Failed: 1)
>   Failed test:  17
>   Non-zero exit status: 1
> t/19-push.t   (Wstat: 3584 (exited 14) Tests: 80 Failed: 14)
>   Failed tests:  7, 10, 13, 16, 19, 22, 25, 28, 31, 52, 55
> 58, 61, 64
>   Non-zero exit status: 14
> Files=42, Tests=1768,  9 wallclock secs ( 0.32 usr  0.10 sys +  7.37 cusr  
> 1.78 csys =  9.57 CPU)

Yay, libgit2 1.7.1 broke Git-Raw again …


Some investigation:

1) t/08-branch.t is probably broken by this upstream change in libgit2:

* Fixes #6344: git_branch_move now renames the reflog instead of deleting
  by @arroz in https://github.com/libgit2/libgit2/pull/6345

t/08-branch.t ... 
ok 1 - An object of class 'Git::Raw::Commit' isa 'Git::Raw::Commit'
ok 2
ok 3
ok 4
ok 5
ok 6
ok 7
ok 8
ok 9
ok 10
ok 11
ok 12 - An object of class 'Git::Raw::Commit' isa 'Git::Raw::Commit'
ok 13
ok 14
ok 15
ok 16
not ok 17

#   Failed test at t/08-branch.t line 54.
#  got: '2'
# expected: '1'
ok 18
ok 19
ok 20 - An object of class 'Git::Raw::Signature' isa 'Git::Raw::Signature'
ok 21
ok 22
ok 23
ok 24
ok 25
ok 26
ok 27
ok 28
ok 29
ok 30
ok 31
ok 32
ok 33
ok 34
1..34
# Looks like you failed 1 test of 34.
Dubious, test returned 1 (wstat 256, 0x100)
Failed 1/34 subtests 

I checked that `git reflog some_branch' in t/test_repo has indeed 2
entries in sid (libgit2 1.7.1) and 1 entry in trixie (libgit 1.5.1).



2) t/19-push.t is a bit weird, I've seen varying counts of failing
tests, between 0 (!) and the 14 quoted above and just now 28, with
all kinds of numbers in the `got' output; e.g.:

t/19-push.t . 
ok 1
ok 2 - An object of class 'Git::Raw::Remote' isa 'Git::Raw::Remote'
ok 3
ok 4
ok 5
ok 6
not ok 7

#   Failed test at t/19-push.t line 34.
#  got: '2'
# expected: '1'
ok 8
ok 9
not ok 10

#   Failed test at t/19-push.t line 34.
#  got: '3'
# expected: '1'
ok 11
ok 12
not ok 13

#   Failed test at t/19-push.t line 34.
#  got: '4'
# expected: '1'
ok 14
ok 15
not ok 16

#   Failed test at t/19-push.t line 34.
#  got: '16'
# expected: '1'
ok 17
ok 18
ok 19
ok 20
ok 21
ok 22
ok 23
ok 24
ok 25
ok 26
ok 27
ok 28
ok 29
ok 30
ok 31
ok 32
ok 33
not ok 34

#   Failed test at t/19-push.t line 73.
#  got: '2'
# expected: '1'
ok 35
ok 36
not ok 37

#   Failed test at t/19-push.t line 73.
#  got: '12'
# expected: '1'
ok 38
ok 39
ok 40
ok 41
ok 42
ok 43
ok 44
ok 45
ok 46
ok 47
ok 48
ok 49
ok 50
ok 51
ok 52
ok 53
# remote push tests require network
1..53
# Looks like you failed 6 tests of 53.
Dubious, test returned 6 (wstat 1536, 0x600)
Failed 6/53 subtests 


Maybe this is a timing issue?


What the test does is

#v+
24  my $total_packed = 0;
25  is $remote -> upload(['refs/heads/main:refs/heads/main'], {
26  'callbacks' => {
27  'pack_progress' => sub {
28  my ($stage, $current, $total) = @_;
29  
30  ok ($stage == 
Git::Raw::Packbuilder->ADDING_OBJECTS ||
31  $stage == 
Git::Raw::Packbuilder->DELTAFICATION);
32  if ($stage == 
Git::Raw::Packbuilder->ADDING_OBJECTS)
33  {
34  is $current, 1;
35  is $total, 0;
36  }
37  else
38  {
39  ok ($current <= $total);
40  ok ($total > 0);
41  }
42  $total_packed++;
43  }
44  }
45  }), 1;
46  ok ($total_packed > 0);
#v-

and pack_progress is a callback which does

   pack_progress
   During the packing of new data, this will regularly be called
   with the progress of the pack operation. Be aware that this is
   called inline with pack building operations, so performance
   may be affected. The callback receives the following integers:
   $stage, $current and $total.


With some `diag()' sprinkled in I get:

t/19-push.t . 
ok 1
ok 2 - An object of class 'Git::Raw::Remote' isa 'Git::Raw::Remote'
# pack_progress: stage 0, cu

Processed: Re: Bug#1055147: seahorse-adventures: No keypress recognised

[Debian Bug Tracking System]

Processing control commands:

> severity -1 grave
Bug #1055147 [seahorse-adventures] seahorse-adventures: No keypress recognised
Severity set to 'grave' from 'normal'

-- 
1055147: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1055147
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#1002789: (No Subject)

[Dale Richards]

Right, I've gone down a rabbit hole with this. I don't have a fix yet,
but I'll post what I've found here in case it makes sense to anyone.

The problem manifests when the internal_check_dot_dir_record() and
internal_check_dotdot_dir_record() functions from
tests/integration/test_common.py are run. In particular the tests are
comparing the posix_file_links attribute of the Rock Ridge PX record to
an expected value. In this case posix_file_links corresponds to the
st_nlink member as defined in POSIX:5.6.1 (i.e. the number of links to
the file/inode), and allows Rock Ridge to store this extended POSIX
information within an ISO9660 CD file system.

For both the . (dot) and .. (dotdot) directory entries within the
generated .iso file, the tests are expecting the number of links to be
3, although in my build tests it it actually appears to be 2 for 
and 3 for .

Curiously, when I extract the failing tests from the package and run
them in isolation, the posix_file_links value is 3 for both the . and
.. directory entries, and the tests pass as expected. I did, however,
have to make a tweak to the test logic...

At test_hybrid.py:784, the source package is creating its temporary
directory with:

indir = tmpdir.mkdir('rronefileonedir')

When I tried this in isolation, the mkdir() method was not found, so I
substituted it with:

indir = os.path.join(tmpdir, 'rronefileonedir')
os.mkdir(indir)

Presumably I missed an import or type definition somewhere when
isolating the tests, but the tests run successfully with this code.

On my test system, creating a directory with os.mkdir() from Python
gives st_nlink==2 for . and st_nlink==3 for .., and I get the same
results when creating the directory directly with the mkdir command.

My first thought was that my build chroot was somehow messing with the
st_nlinks value of the created directories, but I can reproduce the
same test failures when building directly on my test machine without a
chroot.

Perhaps there's something odd about the tmpdir.mkdir() method called in
the original code, or the way Python's os module creates directories
during the Debian build sequence?

At this point my head started to hurt, so I've stopped looking for now,
but I thought I'd braindump here in case this rings a bell for anyone
with more POSIX/Rock Ridge/Debian/Python experience than me.

Best regards,
Dale Richards

Processed: limit source to linux, tagging 1032104

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> limit source linux
Limiting to bugs with field 'source' containing at least one of 'linux'
Limit currently set to 'source':'linux'

> tags 1032104 + pending
Bug #1032104 [src:linux] linux: ppc64el iouring corrupted read
Added tag(s) pending.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
1032104: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1032104
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#1057190: libhackrf0: udev rules file lost in upgrade

[Chris Hofstaedtler]

Hello Maitland,

* Maitland Bottoms  [231203 14:57]:
> Helmut Grohne  writes:
> 
> > Then when you retry it, please go for experimental first. Then have
> > Chris or me check your upload is ok and only then proceed with uploading
> > to unstable.
> 
> hackrf_2023.01.1-6 now in experimental is the retry with upstream
> updates and the udev rules handling.
> 
> Thanks for your attention on this, indeed my lack of attention before
> making uploads is the problem. I am happier with -6 though.

Thank you! -6 is looking good at first glance. Lets give the dumat
tool a bit more time to check it though.

Do you think you could upload the other packages (rtl-sdr,
bladerf, libmirisdr, libiio, libosmosdr) to experimental soon, too?

Best,
Chris

Bug#1057307: sioyek: FTBFS with mupdf 0.23

[Kan-Ru Chen]

Hi,

On Sun, Dec 3, 2023, at 11:10 AM, Victor Westerhuis wrote:
>> @mupdf maintainers: Could you test if reverse dependencies still build
>> before pushing a new version in the future?

Thanks for let me know. Can you suggest some way to automate the testing step,
either that I can run it locally reasonably fast, or I can use buildd resource 
to
do that?

And, what is the best course of action to take it finds breaking change?

-- 
Kan-Ru Chen
Debian Developer

Processed: Re: seahorse-adventures: No keypress recognised

[Debian Bug Tracking System]

Processing control commands:

> severity -1 normal
Bug #1055147 [seahorse-adventures] seahorse-adventures: No keypress recognised
Severity set to 'normal' from 'grave'

-- 
1055147: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1055147
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#1055147: seahorse-adventures: No keypress recognised

[Markus Koschany]

Control: severity -1 normal

On Wed, 01 Nov 2023 09:25:19 +0100 Francesco Ariis  wrote:
> Package: seahorse-adventures
> Version: 1.1+dfsg-6
> Severity: grave
> Justification: renders package unusable
> X-Debbugs-Cc: fa...@ariis.it
> 
> Dear Maintainer,
> 
> to replicate:
> 
> 1. Launch `seahorse-adventures`
> 2. Now you are in the menu.
> 3. Press any direction key
> 3. The grey indicator in the menu does not move. It seems that keypresses
>    are not recognised. The game is thus unplayable.


I could not reproduce your problem. The keys work as expected and I can
navigate the menu and the game without any problems.


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

Bug#1057329: rust-rlp: autopkgtest failure on 32bit

[Adrian Bunk]

Source: rust-rlp
Version: 0.5.2-1
Severity: serious

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

Issues preventing migration:
∙ ∙ autopkgtest for rust-rlp/0.5.2-1: amd64: Pass, arm64: Pass, armel: 
Regression ♻ , armhf: Regression ♻ , i386: Regression ♻ , ppc64el: Pass, s390x: 
Pass


...
843s failures:
4478
843s 
4479
843s  length_overflow stdout 
4480
843s thread 'length_overflow' panicked at 'assertion failed: `(left == right)`
4481
843s   left: `Err(RlpInvalidLength)`,
4482
843s  right: `Err(RlpIsTooBig)`', tests/tests.rs:27:5
4483
843s stack backtrace:
4484
843s0: rust_begin_unwind
4485
843s  at /usr/src/rustc-1.70.0/library/std/src/panicking.rs:578:5
4486
843s1: core::panicking::panic_fmt
4487
843s  at /usr/src/rustc-1.70.0/library/core/src/panicking.rs:67:14
4488
843s2: core::panicking::assert_failed_inner
4489
843s3: core::panicking::assert_failed
4490
843s  at /usr/src/rustc-1.70.0/library/core/src/panicking.rs:228:5
4491
843s4: tests::length_overflow
4492
843s  at ./tests/tests.rs:27:2
4493
843s5: tests::length_overflow::{{closure}}
4494
843s  at ./tests/tests.rs:23:22
4495
843s6: core::ops::function::FnOnce::call_once
4496
843s  at 
/usr/src/rustc-1.70.0/library/core/src/ops/function.rs:250:5
4497
843s7: core::ops::function::FnOnce::call_once
4498
843s  at 
/usr/src/rustc-1.70.0/library/core/src/ops/function.rs:250:5
4499
843s note: Some details are omitted, run with `RUST_BACKTRACE=full` for a 
verbose backtrace.
4500
843s 
4501
843s  test_rlp_list_length_overflow stdout 
4502
843s thread 'test_rlp_list_length_overflow' panicked at 'assertion failed: 
`(left == right)`
4503
843s   left: `Err(RlpIsTooShort)`,
4504
843s  right: `Err(RlpIsTooBig)`', tests/tests.rs:592:5
4505
843s stack backtrace:
4506
843s0: rust_begin_unwind
4507
843s  at /usr/src/rustc-1.70.0/library/std/src/panicking.rs:578:5
4508
843s1: core::panicking::panic_fmt
4509
843s  at /usr/src/rustc-1.70.0/library/core/src/panicking.rs:67:14
4510
843s2: core::panicking::assert_failed_inner
4511
843s3: core::panicking::assert_failed
4512
843s  at /usr/src/rustc-1.70.0/library/core/src/panicking.rs:228:5
4513
843s4: tests::test_rlp_list_length_overflow
4514
843s  at ./tests/tests.rs:592:2
4515
843s5: tests::test_rlp_list_length_overflow::{{closure}}
4516
843s  at ./tests/tests.rs:588:36
4517
843s6: core::ops::function::FnOnce::call_once
4518
843s  at 
/usr/src/rustc-1.70.0/library/core/src/ops/function.rs:250:5
4519
843s7: core::ops::function::FnOnce::call_once
4520
843s  at 
/usr/src/rustc-1.70.0/library/core/src/ops/function.rs:250:5
4521
843s note: Some details are omitted, run with `RUST_BACKTRACE=full` for a 
verbose backtrace.
4522
843s 
4523
843s 
4524
843s failures:
4525
843s length_overflow
4526
843s test_rlp_list_length_overflow
4527
843s 
4528
843s test result: FAILED. 42 passed; 2 failed; 0 ignored; 0 measured; 0 
filtered out; finished in 0.03s
4529
843s 
4530
843s error: test failed, to rerun pass `--test tests`
4531
844s autopkgtest [22:13:26]: test librust-rlp-dev:: ---]
▾ test librust-rlp-dev:: test results
4532
844s autopkgtest [22:13:26]: test librust-rlp-dev::  - - - - - - - - - - 
results - - - - - - - - - -
4533
844s librust-rlp-dev: FAIL non-zero exit status 101
▾ summary
4534
844s autopkgtest [22:13:26]:  summary
4535
844s rust-rlp:@   FAIL non-zero exit status 101
4536
844s librust-rlp-dev:default FAIL non-zero exit status 101
4537
844s librust-rlp-dev:derive FAIL non-zero exit status 101
4538
844s librust-rlp-dev:rlp-derive FAIL non-zero exit status 101
4539
844s librust-rlp-dev:std  FAIL non-zero exit status 101
4540
844s librust-rlp-dev: FAIL non-zero exit status 101

Bug#1053686: pandoc: cannot fulfill the build dependencies

[Chris Hofstaedtler]

Hello Jonas,

* Scott Talbert  [231203 14:06]:
> haskell-pandoc has been accepted into unstable, so I think you should be
> able to update src:pandoc to now build from the pandoc-cli hackage package.
[..]

Sorry for nudging here, but pandoc is used as a build dependency on
quite a few libraries needing intrusive packaging patches for
UsrMerge. The earlier we can have them fixed in (at least)
experimental, the better.
But for that they need their build-deps, obviously :-)

Thanks to everyone here for their work!

Best,
Chris

Bug#1042967: nheko crashes on first launch in arm64 (librem 5)

[Marco Mattiolo]

Hi,

as I've just reported in the upstream issue, I've tested there's an 
upstream commit fixing this issue.


Please note (mainly for Hubert): the commit does not apply cleanly on 
top of 0.11.3 due to other upstream changes to CMakeLists.txt, then you 
will have to rework the patch a bit.


Kind regards

Marco

Bug#1057296: marked as done (src:r-cran-data.table: fails to migrate to testing for too long: autopkgtest failure on 32 bits)

[Debian Bug Tracking System]

Your message dated Sun, 03 Dec 2023 13:36:54 +
with message-id 
and subject line Bug#1057296: fixed in r-cran-data.table 1.14.8+dfsg2-2
has caused the Debian Bug report #1057296,
regarding src:r-cran-data.table: fails to migrate to testing for too long: 
autopkgtest failure on 32 bits
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
1057296: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1057296
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---

Source: r-cran-data.table
Version: 1.14.8+dfsg-1
Severity: serious
Control: close -1 1.14.8+dfsg2-1
Tags: sid trixie
User: release.debian@packages.debian.org
Usertags: out-of-sync

Dear maintainer(s),

The Release Team considers packages that are out-of-sync between testing 
and unstable for more than 30 days as having a Release Critical bug in 
testing [1]. Your package src:r-cran-data.table has been trying to 
migrate for 40 days [2]. Hence, I am filing this bug. The version in 
unstable fails its autopkgtest on 32 bit architectures.


If a package is out of sync between unstable and testing for a longer 
period, this usually means that bugs in the package in testing cannot be 
fixed via unstable. Additionally, blocked packages can have impact on 
other packages, which makes preparing for the release more difficult. 
Finally, it often exposes issues with the package and/or
its (reverse-)dependencies. We expect maintainers to fix issues that 
hamper the migration of their package in a timely manner.


This bug will trigger auto-removal when appropriate. As with all new 
bugs, there will be at least 30 days before the package is auto-removed.


I have immediately closed this bug with the version in unstable, so if 
that version or a later version migrates, this bug will no longer affect 
testing. I have also tagged this bug to only affect sid and trixie, so 
it doesn't affect (old-)stable.


If you believe your package is unable to migrate to testing due to 
issues beyond your control, don't hesitate to contact the Release Team.


Paul

[1] https://lists.debian.org/debian-devel-announce/2023/06/msg1.html
[2] https://qa.debian.org/excuses.php?package=r-cran-data.table



OpenPGP_signature.asc
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Source: r-cran-data.table
Source-Version: 1.14.8+dfsg2-2
Done: Andreas Tille 

We believe that the bug you reported is fixed in the latest version of
r-cran-data.table, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 1057...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Andreas Tille  (supplier of updated r-cran-data.table package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sun, 03 Dec 2023 11:17:46 +0100
Source: r-cran-data.table
Architecture: source
Version: 1.14.8+dfsg2-2
Distribution: unstable
Urgency: medium
Maintainer: Debian R Packages Maintainers 
Changed-By: Andreas Tille 
Closes: 1057296
Changes:
 r-cran-data.table (1.14.8+dfsg2-2) unstable; urgency=medium
 .
   * Add patch from upstream to pass tests on 32bit archs
 Closes: #1057296
Checksums-Sha1:
 f842117a0c81a773a6c673492fff796a16fb65c2 2353 
r-cran-data.table_1.14.8+dfsg2-2.dsc
 5bc8f0a10e6c4eb6d27925236076ffb7dffebb14 4268 
r-cran-data.table_1.14.8+dfsg2-2.debian.tar.xz
 cf4f38a061b3bff9cf6d400d47995d9843f31cd3 19451 
r-cran-data.table_1.14.8+dfsg2-2_source.buildinfo
Checksums-Sha256:
 e0eceaea88dae06a5dfc7f3e883506624b0d68f401a6129f32331ba773ffa933 2353 
r-cran-data.table_1.14.8+dfsg2-2.dsc
 baba14d22c9d2b9edc15fe62a4828008971061b92acf0cfd78e32019608f2da1 4268 
r-cran-data.table_1.14.8+dfsg2-2.debian.tar.xz
 5d787e59060ff9f9b1107905384a971893015af0e4f4054628ae463c44053b53 19451 
r-cran-data.table_1.14.8+dfsg2-2_source.buildinfo
Files:
 6a52ed79d7afa667020411769c060761 2353 gnu-r optional 
r-cran-data.table_1.14.8+dfsg2-2.dsc
 401f00ea7c00b6ea6184d6ac49d42c32 4268 gnu-r optional 
r-cran-data.table_1.14.8+dfsg2-2.debian.tar.xz
 1e60817bef159daed61e714712faa178 19451 gnu-r optional 
r-cran-data.table_1.14.8+dfsg2-2_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJCBAEBCgAsFiEE8fAHMgoDVUHwpmPKV4oElNHGRtEF

Bug#1057203: marked as done (r-bioc-rhdf5filters: missing build-dependency on big-endian architectures)

[Debian Bug Tracking System]

Your message dated Sun, 03 Dec 2023 13:36:42 +
with message-id 
and subject line Bug#1057203: fixed in r-bioc-rhdf5filters 1.14.1+dfsg-2
has caused the Debian Bug report #1057203,
regarding r-bioc-rhdf5filters: missing build-dependency on big-endian 
architectures
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
1057203: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1057203
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: r-bioc-rhdf5filters
Version: 1.12.1+dfsg2-1
Severity: serious
Tags: ftbfs
X-Debbugs-Cc: debian-s...@lists.debian.org

Hi Maintainer

A commit on 2023-08-01 [1] added a build-dependency on
libvbz-hdf-plugin-dev, which is not available on big-endian
architectures, and prevents r-bioc-rhdf5filters from building on s390x
[2], where it built previously, thus blocking migration.

The package libvbz-hdf-plugin does not build on big-endian
architectures [3] due to a missing build-dependency on
libstreamvbyte-dev, and libstreamvbyte itself FTBFS on big-endian
architectures [4].

According to:
reverse-depends --release sid --recursive r-bioc-rhdf5filters

r-bioc-rhdf5filters has many reverse-dependencies on s390x, so rather
than dealing with all of these, it may be simplest to fix
libstreamvbyte.

Regards
Graham


[1] 
https://salsa.debian.org/r-pkg-team/r-bioc-rhdf5filters/-/commit/78ced3f3c70fe29db3ba16bc2b57da5ab0e4fa6c
[2] https://buildd.debian.org/status/package.php?p=r-bioc-rhdf5filters
[3] https://buildd.debian.org/status/package.php?p=libvbz-hdf-plugin
[4] https://buildd.debian.org/status/package.php?p=libstreamvbyte
--- End Message ---
--- Begin Message ---
Source: r-bioc-rhdf5filters
Source-Version: 1.14.1+dfsg-2
Done: Andreas Tille 

We believe that the bug you reported is fixed in the latest version of
r-bioc-rhdf5filters, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 1057...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Andreas Tille  (supplier of updated r-bioc-rhdf5filters 
package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sun, 03 Dec 2023 14:07:30 +0100
Source: r-bioc-rhdf5filters
Architecture: source
Version: 1.14.1+dfsg-2
Distribution: unstable
Urgency: medium
Maintainer: Debian R Packages Maintainers 
Changed-By: Andreas Tille 
Closes: 1057203
Changes:
 r-bioc-rhdf5filters (1.14.1+dfsg-2) unstable; urgency=medium
 .
   [ Graham Inggs ]
   * Disable libvbz-hdf-plugin-dev Build-Depends for those architectures
 that do not implement vbz compression
 Closes: #1057203
Checksums-Sha1:
 69d43966f3af1cccde5c8ccaf4c872355c1b5668 2304 
r-bioc-rhdf5filters_1.14.1+dfsg-2.dsc
 40a4868d44d32c415084235587d1932ac85b36e9 5500 
r-bioc-rhdf5filters_1.14.1+dfsg-2.debian.tar.xz
 c6c731a3e1a6ea2057707dddade5273b5515d0a7 19932 
r-bioc-rhdf5filters_1.14.1+dfsg-2_source.buildinfo
Checksums-Sha256:
 fde3384310ed9a9ca52042b1a9cbd02485406756306accfd953574ce79f7ef80 2304 
r-bioc-rhdf5filters_1.14.1+dfsg-2.dsc
 6f617ca355a8cdd65e919742d37fa897876db416d825a9e890341bfc2e5f4464 5500 
r-bioc-rhdf5filters_1.14.1+dfsg-2.debian.tar.xz
 acc3340b35e40f020207aad3abff6ff066e4ccfd608ad70a565c64c4c46507db 19932 
r-bioc-rhdf5filters_1.14.1+dfsg-2_source.buildinfo
Files:
 81c884af361c849f9a7acfdb26e587f4 2304 gnu-r optional 
r-bioc-rhdf5filters_1.14.1+dfsg-2.dsc
 a5f551e578e0e035603e7b2f262240fc 5500 gnu-r optional 
r-bioc-rhdf5filters_1.14.1+dfsg-2.debian.tar.xz
 3e6275a3a9fd4ad6d3c836e35ed11de1 19932 gnu-r optional 
r-bioc-rhdf5filters_1.14.1+dfsg-2_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJCBAEBCgAsFiEE8fAHMgoDVUHwpmPKV4oElNHGRtEFAmVsgMsOHHRpbGxlYUBy
a2kuZGUACgkQV4oElNHGRtEMzw/+JRLHCtoCb5rMKz5MUFcUWkoW/ytr0HkmVEjI
i1GVL8uMhKGbj7Qx7gRVa+mln9NjgFlSEekoghfuZ+2e5f8/i2D7aaM53N5ZZUOR
yQk6vKqK3Rx6n9m5OCTcQ/OSqHPV7I4gxMNDxBomqsgd+1ZIiUgcnPL8u8d9rsM3
B1jD5bOaANGAKJ/dJ9OWPYhyg6LFUH9KaVy5sQdKV/kDQwSOftbinowO8w0CZaTo
92xFYLGRWhnjkeJSDgnDkBZqjuPRH/E/QuurcNp1T1rGZ7KUSTiPhR9ueLPLqloc
Se9CSeSQZF5+eHX9OSZnjow+XlH/TiFYVC1J0UjuP0mBLhiINJNSJSQdoAj1pa+j
QZxgOMjJ4MI6UoMFjh7orxC52Sj5ERxgCsmDSSA8INB/LJCCx5Y7WqB7VW27CbaI
tdGRXP5Zc/gJafnng+br94rnxS6ILVeQQBZOSASn92uxjmnKTtlHWtkNxQFECWN4
oQdETBEwuZrZi

Bug#1057203: marked as done (r-bioc-rhdf5filters: missing build-dependency on big-endian architectures)

[Debian Bug Tracking System]

Your message dated Sun, 3 Dec 2023 14:18:29 +0100
with message-id 
and subject line Re: Bug#1057203: r-bioc-rhdf5filters: missing build-dependency 
on big-endian architectures
has caused the Debian Bug report #1057203,
regarding r-bioc-rhdf5filters: missing build-dependency on big-endian 
architectures
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
1057203: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1057203
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: r-bioc-rhdf5filters
Version: 1.12.1+dfsg2-1
Severity: serious
Tags: ftbfs
X-Debbugs-Cc: debian-s...@lists.debian.org

Hi Maintainer

A commit on 2023-08-01 [1] added a build-dependency on
libvbz-hdf-plugin-dev, which is not available on big-endian
architectures, and prevents r-bioc-rhdf5filters from building on s390x
[2], where it built previously, thus blocking migration.

The package libvbz-hdf-plugin does not build on big-endian
architectures [3] due to a missing build-dependency on
libstreamvbyte-dev, and libstreamvbyte itself FTBFS on big-endian
architectures [4].

According to:
reverse-depends --release sid --recursive r-bioc-rhdf5filters

r-bioc-rhdf5filters has many reverse-dependencies on s390x, so rather
than dealing with all of these, it may be simplest to fix
libstreamvbyte.

Regards
Graham


[1] 
https://salsa.debian.org/r-pkg-team/r-bioc-rhdf5filters/-/commit/78ced3f3c70fe29db3ba16bc2b57da5ab0e4fa6c
[2] https://buildd.debian.org/status/package.php?p=r-bioc-rhdf5filters
[3] https://buildd.debian.org/status/package.php?p=libvbz-hdf-plugin
[4] https://buildd.debian.org/status/package.php?p=libstreamvbyte
--- End Message ---
--- Begin Message ---
Hi Graham,

Am Sun, Dec 03, 2023 at 11:33:59AM -0100 schrieb Graham Inggs:
> I think the vbz compression is not actually enabled by upstream for
> all architectures (amd64 and arm64 only?).
> So restricting the architectures of the build-dependency on
> libvbz-hdf-plugin-dev might be sufficient.
> At least, the patch below was enough to get r-bioc-rhdf5filters
> building on s390x for me, and it does not seem to be affected by the
> pandoc/haskell-pandoc issue.

Thanks for the patch.  Just uploaded and closed the bug with this mail
since I forgot in changelog.

BTW, feel free to do a team upload in cases like these.

Kind regards
Andreas. 

-- 
http://fam-tille.de--- End Message ---

Processed: block 1055955 with 1057318

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> block 1055955 with 1057318
Bug #1055955 [release.debian.org] transition: perl 5.38
1055955 was blocked by: 1054793 1050451 1042844 1042853 1042845 1057270 1054776 
1040396 1042521 1042525
1055955 was not blocking any bugs.
Added blocking bug(s) of 1055955: 1057318
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
1055955: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1055955
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#1055253: amanda: diff for NMU version 1:3.5.1-11.1

[Tobias Frost]

Control: tags 1055253 + patch
Control: tags 1055253 + pending

Dear maintainer,

I've prepared an NMU for amanda (versioned as 1:3.5.1-11.1) and
uploaded it to DELAYED/5. Please feel free to tell me if I
should delay it longer.

Regards.

diff -Nru amanda-3.5.1/debian/changelog amanda-3.5.1/debian/changelog
--- amanda-3.5.1/debian/changelog	2023-03-21 18:35:47.0 +0100
+++ amanda-3.5.1/debian/changelog	2023-12-03 14:09:23.0 +0100
@@ -1,3 +1,10 @@
+amanda (1:3.5.1-11.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Apply upstream fix for CVE-2023-30577 (Closes: #1055253)
+
+ -- Tobias Frost   Sun, 03 Dec 2023 14:09:23 +0100
+
 amanda (1:3.5.1-11) unstable; urgency=medium
 
   * d/p/49-fix-CVE-2022-37705_part_2: 48-fix-CVE-2022-37705 broken one use
diff -Nru amanda-3.5.1/debian/patches/57-CVE-2023-30577.patch amanda-3.5.1/debian/patches/57-CVE-2023-30577.patch
--- amanda-3.5.1/debian/patches/57-CVE-2023-30577.patch	1970-01-01 01:00:00.0 +0100
+++ amanda-3.5.1/debian/patches/57-CVE-2023-30577.patch	2023-12-03 13:55:48.0 +0100
@@ -0,0 +1,83 @@
+Description: CVE-2023-30577 - Local privilege escalation.
+Origin: https://github.com/zmanda/amanda/pull/228
+Bug: https://github.com/zmanda/amanda/security/advisories/GHSA-crrw-v393-h5q3
+Bug-Debian: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1055253
+--- a/client-src/runtar.c
 b/client-src/runtar.c
+@@ -39,6 +39,11 @@
+ #include "amutil.h"
+ #include "conffile.h"
+ #include "client_util.h"
++#include 
++
++static const char *whitelisted_args[] = {"--blocking-factor", "--file", "--directory", "--exclude", "--transform", "--listed-incremental", "--newer", "--exclude-from", "--files-from", NULL};
++
++bool check_whitelist(char* option);
+ 
+ int main(int argc, char **argv);
+ 
+@@ -49,6 +54,7 @@
+ {
+ #ifdef GNUTAR
+ int i;
++char **j;
+ char *e;
+ char *dbf;
+ char *cmdline;
+@@ -182,20 +188,23 @@
+ 		g_str_has_prefix(argv[i],"--verbose")) {
+ 		/* Accept theses options */
+ 		good_option++;
+-	} else if (g_str_has_prefix(argv[i],"--blocking-factor") ||
+-		g_str_has_prefix(argv[i],"--file") ||
+-		g_str_has_prefix(argv[i],"--directory") ||
+-		g_str_has_prefix(argv[i],"--exclude") ||
+-		g_str_has_prefix(argv[i],"--transform") ||
+-		g_str_has_prefix(argv[i],"--listed-incremental") ||
+-		g_str_has_prefix(argv[i],"--newer") ||
+-		g_str_has_prefix(argv[i],"--exclude-from") ||
+-		g_str_has_prefix(argv[i],"--files-from")) {
++	} else if (check_whitelist(argv[i])) {
+ 		if (strchr(argv[i], '=')) {
+ 		good_option++;
+ 		} else {
+ 		/* Accept theses options with the following argument */
+ 		good_option += 2;
++
++/* Whitelisting only the allowed arguments*/
++for(j=whitelisted_args; *j; j++) {
++if (strcmp(argv[i], *j) == 0) {
++break;
++}
++}
++
++if (!*j) {
++good_option = 0; // not allowing arguments absent in the whitelist
++}
+ 		}
+ } else if (argv[i][0] != '-') {
+ 		good_option++;
+@@ -239,3 +248,23 @@
+ return 1;
+ #endif
+ }
++
++bool
++check_whitelist(
++gchar* option)
++{
++bool result = TRUE;
++char** i;
++
++for(i=whitelisted_args; *i; i++) {
++if (g_str_has_prefix(option, *i)) {
++break;
++}
++}
++
++if (!*i) {
++result = FALSE; // not allowing arguments absent in the whitelist
++}
++
++return result;
++}
diff -Nru amanda-3.5.1/debian/patches/series amanda-3.5.1/debian/patches/series
--- amanda-3.5.1/debian/patches/series	2023-03-21 18:35:47.0 +0100
+++ amanda-3.5.1/debian/patches/series	2023-12-03 14:09:19.0 +0100
@@ -49,3 +49,4 @@
 50-fix-CVE-2022-37704
 52-fix-CVE-2022-37704_part_2
 56-fix-CVE-2022-37703
+57-CVE-2023-30577.patch


signature.asc
Description: PGP signature

Processed: amanda: diff for NMU version 1:3.5.1-11.1

[Debian Bug Tracking System]

Processing control commands:

> tags 1055253 + patch
Bug #1055253 [src:amanda] amanda: CVE-2023-30577
Added tag(s) patch.
> tags 1055253 + pending
Bug #1055253 [src:amanda] amanda: CVE-2023-30577
Added tag(s) pending.

-- 
1055253: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1055253
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#1057270: libimager-perl: FTBFS: t/t10tiff.t failure

[Niko Tyni]

On Sun, Dec 03, 2023 at 01:31:19AM +0100, gregor herrmann wrote:
> On Sun, 03 Dec 2023 10:46:50 +1100, Tony Cook wrote:
> 
> > >   https://github.com/tonycoz/imager/issues/522
> > Fixed in 1.022, please let me know if you have any more problems.
> 
> Thank you!
> 1.022 builds fine in Debian unstable, so I've uploaded it.

Thanks!

> > d54ea521f63ec1ed7d8c0fd11c23507600d51143 should be safe to cherry pick
> > back to 1.020 if you don't want all of the 1.021 TIFF changes in
> > the debian stable libimager-perl.
> 
> Hm, Debian stable (which has 1.019) is a good question. If libtiff is
> updated there too [0] we might see the same issue there.

While the stable update tiff_4.5.0-6+deb12u1 has security fixes, it does
not include the change for CVE-2023-6277. The security tracker mentions
it as a minor issue. I also checked earlier that stable is not affected.

> So I guess we don't have to do anything here, and if reality is
> different than my tests, we can pull in
> d54ea521f63ec1ed7d8c0fd11c23507600d51143 -- thanks for the pointer!

Agreed & thanks again :)
-- 
Niko