Processed: severity of 1019504 is serious

[Debian Bug Tracking System]

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

> severity 1019504 serious
Bug #1019504 [librust-log-dev] librust-log-dev: provided virtual package 
librust-log+kv-unstable-dev is unusable
Severity set to 'serious' from 'important'
> thanks
Stopping processing here.

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

Bug#1020652: [Pkg-openssl-devel] Bug#1020652: openssl: tls_process_key_exchange:internal error:../ssl/statem/statem_clnt.c:2254:

[Kurt Roeckx]

On Sun, Sep 25, 2022 at 02:16:00AM +, Thorsten Glaser wrote:
> Kurt Roeckx dixit:
> 
> >On Sat, Sep 24, 2022 at 10:34:19PM +0200, Thorsten Glaser wrote:
> >> $ openssl s_client -CApath /etc/ssl/certs -connect www.mirbsd.org:443 
> >> -legacy_renegotiation -tls1
> >
> >TLS 1.0 is not supported by default because it's insecure. You need
> >to change the security level to 0, for instance by using the cipher
> >string DEFAULT@SECLEVEL=0
>^ +colon
> 
> Hey, this used to work at @SECLEVEL=2 even, with just MinProtocol
> changed. Also openssl ciphers shows the same, independent of the
> number used for @SECLEVEL. How can I find out, for any installed
> OpenSSL, which settings this mysterious @SECLEVEL influences and
> which are available? Where is this documented?

There is /usr/share/doc/openssl/NEWS.md.gz, which says:
  * SSL 3, TLS 1.0, TLS 1.1, and DTLS 1.0 only work at security level 0,
except when RSA key exchange without SHA1 is used.

So this also works:
openssl s_client -connect www.mirbsd.org:443 -cipher AES256-SHA 
-legacy_renegotiation -tls1

That's the only cipher you have with RSA key exchange. Your server
doesn't have a preference for ciphers, so picks the first offered by the
client, so the order is important.

Security levels are documented in SSL_CTX_set_security_level(3):
https://www.openssl.org/docs/man3.0/man3/SSL_CTX_set_security_level.html

SHA1 have been moved to security level 0 because it no longer
provides enough security, even when combined with MD5.


Kurt

Bug#1020208: singularity-container: FTBFS: make[2]: *** [Makefile:181: singularity] Error 2

[Nilesh Patra]

On Sun, Sep 25, 2022 at 01:19:38PM +0800, Shengjing Zhu wrote:
> Control: notfound -1 umoci/0.4.7+ds-3
> 
> On Sun, Sep 25, 2022 at 11:34 AM Nilesh Patra  wrote:
> >
> > Control: found -1 singularity-container/3.10.2+ds2-3
> > Control: found -1 umoci/0.4.7+ds-3
> > Control: retitle -1 umoci makes singularity-container FTBFS
> >
> > I tried with golang-github-opensuse-umoci-dev version 0.4.7+ds-2
> > in my schroot, and it builds fine there.
> > On upgrading and building, it chokes. This and rootless-containers-proto-dev
> > are the only two packages that changed in chroot.
> >
> > The failing code in the question does not stem from singularity-container.
> 
> You vendor a copy of github.com/rootless-containers/proto, there's
> nothing we can do in the umoci package.
> Please fix the code in the singularity-container.

Aw, crap, oops!
Looks like it is not a good idea to do debian work at late hours in the night.

Thanks for catching this!

-- 
Best,
Nilesh


signature.asc
Description: PGP signature

Processed: src:valijson: fails to migrate to testing for too long: upload built arch:all binary

[Debian Bug Tracking System]

Processing control commands:

> close -1 0.7+repack-1
Bug #1020680 [src:valijson] src:valijson: fails to migrate to testing for too 
long: upload built arch:all binary
Marked as fixed in versions valijson/0.7+repack-1.
Bug #1020680 [src:valijson] src:valijson: fails to migrate to testing for too 
long: upload built arch:all binary
Marked Bug as done

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

Bug#1020680: src:valijson: fails to migrate to testing for too long: upload built arch:all binary

[Paul Gevers]

Source: valijson
Version: 0.6+repack-2
Severity: serious
Control: close -1 0.7+repack-1
Tags: sid bookworm pending
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 60 days as having a Release Critical bug in 
testing [1]. Your package src:valijson has been trying to migrate for 61 
days [2]. Hence, I am filing this bug.


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 bookworm, so 
it doesn't affect (old-)stable.


Your package is only blocked because the arch:all binary package(s) 
aren't built on a buildd. Unfortunately the Debian infrastructure 
doesn't allow arch:all packages to be properly binNMU'ed. Hence, I will 
shortly do a no-changes source-only upload to DELAYED/15, closing this 
bug. Please let me know if I should delay or cancel that upload.


Paul

[1] https://lists.debian.org/debian-devel-announce/2020/02/msg5.html
[2] https://qa.debian.org/excuses.php?package=valijson



OpenPGP_signature
Description: OpenPGP digital signature

Bug#1017148: marked as done (soci: FTBFS: catch.hpp:6490:33: error: size of array ‘altStackMem’ is not an integral constant-expression)

[Debian Bug Tracking System]

Your message dated Sun, 25 Sep 2022 05:48:33 +
with message-id 
and subject line Bug#1017148: fixed in soci 4.0.3-1
has caused the Debian Bug report #1017148,
regarding soci: FTBFS: catch.hpp:6490:33: error: size of array ‘altStackMem’ is 
not an integral constant-expression
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.)


-- 
1017148: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1017148
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: soci
Version: 4.0.1-5
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20220813 ftbfs-bookworm

Hi,

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


Relevant part (hopefully):
> cd /<>/obj-x86_64-linux-gnu/src/backends/mysql && /usr/bin/c++ 
> -DBOOST_ALL_NO_LIB -DBOOST_DATE_TIME_DYN_LINK -DHAVE_DL=1 
> -DSOCI_ABI_VERSION=\"4.0\" -Dsoci_mysql_EXPORTS 
> -I/<>/obj-x86_64-linux-gnu -I/<>/include 
> -I/<>/obj-x86_64-linux-gnu/include 
> -I/<>/include/private -I/usr/include/mysql 
> -I/<>/src/core/../../include -g -O2 
> -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat 
> -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -pedantic  
> -Wno-error=parentheses -Wall -Wextra -Wpointer-arith -Wcast-align -Wcast-qual 
> -Wfloat-equal -Woverloaded-virtual -Wredundant-decls -Wno-long-long 
> -std=c++11  -Wno-variadic-macros -fPIC -std=gnu++11 -MD -MT 
> src/backends/mysql/CMakeFiles/soci_mysql.dir/standard-into-type.cpp.o -MF 
> CMakeFiles/soci_mysql.dir/standard-into-type.cpp.o.d -o 
> CMakeFiles/soci_mysql.dir/standard-into-type.cpp.o -c 
> /<>/src/backends/mysql/standard-into-type.cpp
> In file included from /usr/include/signal.h:328,
>  from /<>/tests/catch.hpp:6467,
>  from /<>/tests/common-tests.h:29,
>  from /<>/tests/firebird/test-firebird.cpp:14:
> /<>/tests/catch.hpp:6490:33: error: size of array ‘altStackMem’ 
> is not an integral constant-expression
>  6490 | static char altStackMem[SIGSTKSZ];
>   | ^~~~
> /<>/tests/catch.hpp:6541:45: error: size of array ‘altStackMem’ 
> is not an integral constant-expression
>  6541 | char FatalConditionHandler::altStackMem[SIGSTKSZ] = {};
>   | ^~~~
> [ 74%] Building CXX object 
> src/backends/sqlite3/CMakeFiles/soci_sqlite3.dir/standard-use-type.cpp.o
> cd /<>/obj-x86_64-linux-gnu/src/backends/sqlite3 && /usr/bin/c++ 
> -DBOOST_ALL_NO_LIB -DBOOST_DATE_TIME_DYN_LINK -DHAVE_DL=1 
> -DSOCI_ABI_VERSION=\"4.0\" -Dsoci_sqlite3_EXPORTS 
> -I/<>/obj-x86_64-linux-gnu -I/<>/include 
> -I/<>/obj-x86_64-linux-gnu/include 
> -I/<>/include/private -I/<>/src/core/../../include 
> -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat 
> -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -pedantic  
> -Wno-error=parentheses -Wall -Wextra -Wpointer-arith -Wcast-align -Wcast-qual 
> -Wfloat-equal -Woverloaded-virtual -Wredundant-decls -Wno-long-long 
> -std=c++11  -Wno-variadic-macros -fPIC -std=gnu++11 -MD -MT 
> src/backends/sqlite3/CMakeFiles/soci_sqlite3.dir/standard-use-type.cpp.o -MF 
> CMakeFiles/soci_sqlite3.dir/standard-use-type.cpp.o.d -o 
> CMakeFiles/soci_sqlite3.dir/standard-use-type.cpp.o -c 
> /<>/src/backends/sqlite3/standard-use-type.cpp
> In file included from /usr/include/signal.h:328,
>  from /<>/tests/catch.hpp:6467,
>  from /<>/tests/common-tests.h:29,
>  from /<>/tests/mysql/test-mysql.h:4,
>  from /<>/tests/mysql/test-mysql.cpp:11:
> /<>/tests/catch.hpp:6490:33: error: size of array ‘altStackMem’ 
> is not an integral constant-expression
>  6490 | static char altStackMem[SIGSTKSZ];
>   | ^~~~
> /<>/tests/catch.hpp:6541:45: error: size of array ‘altStackMem’ 
> is not an integral constant-expression
>  6541 | char FatalConditionHandler::altStackMem[SIGSTKSZ] = {};
>   | ^~~~
> [ 75%] Building CXX object 
> src/backends/postgresql/CMakeFiles/soci_postgresql.dir/standard-into-type.cpp.o
> cd /<>/obj-x86_64-linux-gnu/src/backends/postgresql && 
> /usr/bin/c++ -DBOOST_ALL_NO_LIB -DBOOST_DATE_TIME_DYN_LINK -DHAVE_DL=1 
> -DSOCI_ABI_VERSION=\"4.0\" -Dsoci_postgresql_EXPORTS 
> -I/<>/obj-x86_64-linux-gnu -I/<>/include 
> -I/<>/obj-x86_64-linux-gnu/include 
> -I/<>/include/private -I/usr/include/postgresql 
> -I/<>/src/core/../../include -g -O2 
> -ffile-prefix-map=/<>=. -fstack-

Bug#1020679: notfound 1020679 in 0.4.7+ds-3, closing 1020679

[Shengjing Zhu]

notfound 1020679 0.4.7+ds-3
close 1020679 
thanks

Processed: notfound 1020679 in 0.4.7+ds-3, closing 1020679

[Debian Bug Tracking System]

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

> notfound 1020679 0.4.7+ds-3
Bug #1020679 [golang-github-opensuse-umoci-dev] umoci makes 
singularity-container FTBFS
No longer marked as found in versions umoci/0.4.7+ds-3.
> close 1020679
Bug #1020679 [golang-github-opensuse-umoci-dev] umoci makes 
singularity-container FTBFS
Marked Bug as done
> thanks
Stopping processing here.

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

Processed: Re: singularity-container: FTBFS: make[2]: *** [Makefile:181: singularity] Error 2

[Debian Bug Tracking System]

Processing control commands:

> notfound -1 umoci/0.4.7+ds-3
Bug #1020208 [singularity-container] umoci makes singularity-container FTBFS
No longer marked as found in versions umoci/0.4.7+ds-3.

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

Bug#1020208: singularity-container: FTBFS: make[2]: *** [Makefile:181: singularity] Error 2

[Shengjing Zhu]

Control: notfound -1 umoci/0.4.7+ds-3

On Sun, Sep 25, 2022 at 11:34 AM Nilesh Patra  wrote:
>
> Control: found -1 singularity-container/3.10.2+ds2-3
> Control: found -1 umoci/0.4.7+ds-3
> Control: retitle -1 umoci makes singularity-container FTBFS
>
> I tried with golang-github-opensuse-umoci-dev version 0.4.7+ds-2
> in my schroot, and it builds fine there.
> On upgrading and building, it chokes. This and rootless-containers-proto-dev
> are the only two packages that changed in chroot.
>
> The failing code in the question does not stem from singularity-container.

You vendor a copy of github.com/rootless-containers/proto, there's
nothing we can do in the umoci package.
Please fix the code in the singularity-container.

-- 
Shengjing Zhu

Processed: Reassign

[Debian Bug Tracking System]

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

> clone 1020208 -1
Bug #1020208 [singularity-container] umoci makes singularity-container FTBFS
Bug 1020208 cloned as bug 1020679
> reassign -1 golang-github-opensuse-umoci-dev 0.4.7+ds-3
Bug #1020679 [singularity-container] umoci makes singularity-container FTBFS
Bug reassigned from package 'singularity-container' to 
'golang-github-opensuse-umoci-dev'.
No longer marked as found in versions umoci.
Ignoring request to alter fixed versions of bug #1020679 to the same values 
previously set
Bug #1020679 [golang-github-opensuse-umoci-dev] umoci makes 
singularity-container FTBFS
Marked as found in versions umoci/0.4.7+ds-3.
> found 1020208 singularity-container/3.10.2+ds2-3
Bug #1020208 [singularity-container] umoci makes singularity-container FTBFS
Marked as found in versions singularity-container/3.10.2+ds2-3.
> found 1020208 umoci/0.4.7+ds-3
Bug #1020208 [singularity-container] umoci makes singularity-container FTBFS
Marked as found in versions umoci/0.4.7+ds-3.
> thanks
Stopping processing here.

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

Bug#1020677: httraqt: Segfault upon mirroring initiation

[Calum McConnell]

Package: httraqt
Version: 1.4.9-5
Severity: grave
Justification: renders package unusable

As written: I cannot use the package to complete any mirroring operation.
The program crashes a seccond after you start the mirroring, before any
of the download statistics are displayed (though the locations they will
appear in are)

My first attempt to run it printed out the following messages on STDOUT 
when the mirroring started:

Warning: Ignoring XDG_SESSION_TYPE=wayland on Gnome. Use 
QT_QPA_PLATFORM=wayland to run on Wayland anyway.
QObject::connect: No such signal QThread::terminated ()
QObject::connect:  (receiver name: 'MainWindow')
Segmentation fault

My second attempt to run (resuming the first download, only adjusting it to a 
debug-level log) printed the following
STDOUT message

Warning: Ignoring XDG_SESSION_TYPE=wayland on Gnome. Use 
QT_QPA_PLATFORM=wayland to run on Wayland anyway.
QObject::connect: No such signal QThread::terminated ()
QObject::connect:  (receiver name: 'MainWindow')
Mirror launched on Sun, 25 Sep 2022 00:03:56 by HTTrack Website 
Copier/3.49-2+libhtsjava.so.2 [XR&CO'2014]
mirroring https://tomlehrersongs.com/ +*.bmp +*.tif +*.ico +*.jpeg +*.7z +*.exe 
+*.rar +*.gz +*.tgz +*.tar +*.zip +*.ps +*.txt +*.rtf +*.docx +*.doc +*.pdf 
+*.tex +*.odt +*.wmv +*.wma +*.ac3 +*.vid +*.swf +*.qt +*.mkv +*.vob +*.wav 
+*.rm +*.mp2 +*.asf +*.avi +*.mpeg +*.mpg +*.mov +*.png +*.gif +*.jpg +*.css 
+*.js +*.mp3 -ad.doubleclick.net/* with the wizard help..
Segmentation faulthrersongs.com/robots.txt (119 bytes) - OK

Attached is the debug-level log file produced on the second run



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

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

Versions of packages httraqt depends on:
ii  libc6   2.34-8
ii  libhttrack2 3.49.2-1.1+b1
ii  libqt5core5a5.15.4+dfsg-5
ii  libqt5dbus5 5.15.4+dfsg-5
ii  libqt5gui5  5.15.4+dfsg-5
ii  libqt5widgets5  5.15.4+dfsg-5
ii  libstdc++6  12.2.0-3

httraqt recommends no packages.

httraqt suggests no packages.

-- no debconf information
HTTrack3.49-2+libhtsjava.so.2 launched on Sun, 25 Sep 2022 00:03:56 at 
https://tomlehrersongs.com/ +*.bmp +*.tif +*.ico +*.jpeg +*.7z +*.exe +*.rar 
+*.gz +*.tgz +*.tar +*.zip +*.ps +*.txt +*.rtf +*.docx +*.doc +*.pdf +*.tex 
+*.odt +*.wmv +*.wma +*.ac3 +*.vid +*.swf +*.qt +*.mkv +*.vob +*.wav +*.rm 
+*.mp2 +*.asf +*.avi +*.mpeg +*.mpg +*.mov +*.png +*.gif +*.jpg +*.css +*.js 
+*.mp3 -ad.doubleclick.net/*
(httraqt -q -%i -i https://tomlehrersongs.com/ -%e0 -C1 -%P -n -x -s2 -Z -%s 
-%u -N0 -p7 -D -a -K0 -m0,0 -c8 -%k -f2 -A0 -F "Mozilla/5.0 (X11; U; Linux 
x86_64; rv:33.0) Gecko/20100101 Firefox/33.0" -%F "" -%l ua,en -O 
"/home/calum/My Web Sites/Tom Lehner/" +*.bmp +*.tif +*.ico +*.jpeg +*.7z 
+*.exe +*.rar +*.gz +*.tgz +*.tar +*.zip +*.ps +*.txt +*.rtf +*.docx +*.doc 
+*.pdf +*.tex +*.odt +*.wmv +*.wma +*.ac3 +*.vid +*.swf +*.qt +*.mkv +*.vob 
+*.wav +*.rm +*.mp2 +*.asf +*.avi +*.mpeg +*.mpg +*.mov +*.png +*.gif +*.jpg 
+*.css +*.js +*.mp3 -ad.doubleclick.net/* )

Information, Warnings and Errors reported for this mirror:
note:   the hts-log.txt file, and hts-cache folder, may contain sensitive 
information,
such as username/password authentication for websites mirrored in this 
project
do not share these files/folders if you want these information to 
remain private

00:03:56Warning:* security warning: maximum bandwidth limited 
to 25 to avoid server overload
00:03:56Debug:  engine: init
00:03:56Debug:  reallocated 256 new link placeholders
00:03:56Debug:  reallocated 32768 new bytes of strings room
00:03:56Debug:  Cache: enabled=1, base=/home/calum/My Web Sites/Tom 
Lehner/hts-cache/, ro=0
00:03:56Debug:  Cache: rename /home/calum/My Web Sites/Tom 
Lehner/hts-cache/new.zip -> /home/calum/My Web Sites/Tom 
Lehner/hts-cache/old.zip (0x7fa61c081974 0x7fa61c07f974)
00:03:56Debug:  Cache: successfully renamed
00:03:56Debug:  Cache: size 0
00:03:56Debug:  Cache: no cache found in /home/calum/My Web Sites/Tom 
Lehner/hts-cache/
00:03:56Info:   engine: start
00:03:56Debug:  Wait get: primary/primary
00:03:56Info:   Warning: could not detect encoding for: primary/primary
00:03:56Info:   engine: check-html: primary/primary
00:03:56Debug:  engine: preprocess-html: primary/primary
00:03:56Debug:  scanning file primary/primary (/home/calum/My Web 
Sites/Tom Lehner/index.html)..
00:03:56Debug:  link detected in html (tag): https://tomlehrersongs.com/
00:03:56Debug:  engine: save-name: 'iso

Processed: Reassign

[Debian Bug Tracking System]

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

> reassign 1020208 singularity-container umoci
Bug #1020208 [src:singularity-container] umoci makes singularity-container FTBFS
Bug reassigned from package 'src:singularity-container' to 
'singularity-container'.
No longer marked as found in versions singularity-container/3.10.2+ds2-3 and 
umoci/0.4.7+ds-3.
Ignoring request to alter fixed versions of bug #1020208 to the same values 
previously set
Bug #1020208 [singularity-container] umoci makes singularity-container FTBFS
There is no source info for the package 'singularity-container' at version 
'umoci' with architecture ''
Unable to make a source version for version 'umoci'
Marked as found in versions umoci.
> thanks
Stopping processing here.

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

Bug#1020208: singularity-container: FTBFS: make[2]: *** [Makefile:181: singularity] Error 2

[Nilesh Patra]

Control: found -1 singularity-container/3.10.2+ds2-3
Control: found -1 umoci/0.4.7+ds-3
Control: retitle -1 umoci makes singularity-container FTBFS

I tried with golang-github-opensuse-umoci-dev version 0.4.7+ds-2
in my schroot, and it builds fine there.
On upgrading and building, it chokes. This and rootless-containers-proto-dev
are the only two packages that changed in chroot.

The failing code in the question does not stem from singularity-container.

--
Best,
Nilesh


signature.asc
Description: PGP signature

Processed: Re: Bug#1017979: mozjs91: FTBFS on armel with gcc 12: multiple definition of `__sync_fetch_and_add_4' etc.

[Debian Bug Tracking System]

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

> affects 1017979 - src:mozjs102
Bug #1017979 [src:mozjs91] mozjs91: FTBFS on armel with gcc 12: multiple 
definition of `__sync_fetch_and_add_4' etc.
Removed indication that 1017979 affects src:mozjs102
>
End of message, stopping processing here.

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

Processed: Re: singularity-container: FTBFS: make[2]: *** [Makefile:181: singularity] Error 2

[Debian Bug Tracking System]

Processing control commands:

> found -1 singularity-container/3.10.2+ds2-3
Bug #1020208 [src:singularity-container] singularity-container: FTBFS: make[2]: 
*** [Makefile:181: singularity] Error 2
Ignoring request to alter found versions of bug #1020208 to the same values 
previously set
> found -1 umoci/0.4.7+ds-3
Bug #1020208 [src:singularity-container] singularity-container: FTBFS: make[2]: 
*** [Makefile:181: singularity] Error 2
Marked as found in versions umoci/0.4.7+ds-3.
> retitle -1 umoci makes singularity-container FTBFS
Bug #1020208 [src:singularity-container] singularity-container: FTBFS: make[2]: 
*** [Makefile:181: singularity] Error 2
Changed Bug title to 'umoci makes singularity-container FTBFS' from 
'singularity-container: FTBFS: make[2]: *** [Makefile:181: singularity] Error 
2'.

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

Bug#1020652: [Pkg-openssl-devel] Bug#1020652: openssl: tls_process_key_exchange:internal error:../ssl/statem/statem_clnt.c:2254:

[Thorsten Glaser]

Also, where’s the NEWS entry apt-listchanges would have mailed me
to document this change in behaviour?

(Might as well place the documentation I requested in the previous
eMail there, so others will also find it.)

bye,
//mirabilos
-- 
22:20⎜ The crazy that persists in his craziness becomes a master
22:21⎜ And the distance between the craziness and geniality is
only measured by the success 18:35⎜ "Psychotics are consistently
inconsistent. The essence of sanity is to be inconsistently inconsistent

Bug#1020652: [Pkg-openssl-devel] Bug#1020652: openssl: tls_process_key_exchange:internal error:../ssl/statem/statem_clnt.c:2254:

[Thorsten Glaser]

Kurt Roeckx dixit:

>On Sat, Sep 24, 2022 at 10:34:19PM +0200, Thorsten Glaser wrote:
>> $ openssl s_client -CApath /etc/ssl/certs -connect www.mirbsd.org:443 
>> -legacy_renegotiation -tls1
>
>TLS 1.0 is not supported by default because it's insecure. You need
>to change the security level to 0, for instance by using the cipher
>string DEFAULT@SECLEVEL=0
   ^ +colon

Hey, this used to work at @SECLEVEL=2 even, with just MinProtocol
changed. Also openssl ciphers shows the same, independent of the
number used for @SECLEVEL. How can I find out, for any installed
OpenSSL, which settings this mysterious @SECLEVEL influences and
which are available? Where is this documented?

bye,
//mirabilos
-- 
Yay for having to rewrite other people's Bash scripts because bash
suddenly stopped supporting the bash extensions they make use of
-- Tonnerre Lombard in #nosec

Bug#1019855: Fwd: libc6: immediately crashes with SIGILL on 4th gen Intel Core CPUs (seems related to AVX2 instructions), bricking the whole system

[debian-bug-report]

I can confirm updating the microcode by installing the intel-microcode 
package and rebooting does indeed mitigate this issue. An LXC container 
that was previously bricked due to update now starts and seems to behave 
fully normally.


[0.00] microcode: microcode updated early to revision 0x28, date 
= 2019-11-12


But as microcode update needs to be loaded every time on boot (unless I 
presumably updated the UEFI), while it technically solves my problem on 
this installation, the concern of people with the same family of 
processors and outdated microcode running into this issue and having no 
idea why any Linux does not want to boot anymore still probably 
remains... (is there even any easy way to load updated microcode while 
installing Debian? I can most certainly bet its ISO does not include 
those due to non-free constraints)

Bug#1020652: marked as done (openssl: tls_process_key_exchange:internal error:../ssl/statem/statem_clnt.c:2254:)

[Debian Bug Tracking System]

Your message dated Sun, 25 Sep 2022 02:08:31 +0200
with message-id 
and subject line Re: [Pkg-openssl-devel] Bug#1020652: openssl: 
tls_process_key_exchange:internal error:../ssl/statem/statem_clnt.c:2254:
has caused the Debian Bug report #1020652,
regarding openssl: tls_process_key_exchange:internal 
error:../ssl/statem/statem_clnt.c:2254:
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.)


-- 
1020652: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1020652
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: openssl
Version: 3.0.5-4
Severity: serious
Justification: does not work any more
X-Debbugs-Cc: t...@mirbsd.de

$ openssl s_client -CApath /etc/ssl/certs -connect www.mirbsd.org:443 
-legacy_renegotiation -tls1
CONNECTED(0003)
depth=2 C = US, O = Internet Security Research Group, CN = ISRG Root X1
verify return:1
depth=1 C = US, O = Let's Encrypt, CN = R3
verify return:1
depth=0 CN = fish.mirbsd.org
verify return:1
00B093C1B27F:error:0A0C0103:SSL routines:tls_process_key_exchange:internal 
error:../ssl/statem/statem_clnt.c:2254:
---
Certificate chain
 0 s:CN = fish.mirbsd.org
   i:C = US, O = Let's Encrypt, CN = R3
   a:PKEY: rsaEncryption, 4096 (bit); sigalg: RSA-SHA256
   v:NotBefore: Aug 14 07:16:16 2022 GMT; NotAfter: Nov 12 07:16:15 2022 GMT
 1 s:C = US, O = Let's Encrypt, CN = R3
   i:C = US, O = Internet Security Research Group, CN = ISRG Root X1
   a:PKEY: rsaEncryption, 2048 (bit); sigalg: RSA-SHA256
   v:NotBefore: Sep  4 00:00:00 2020 GMT; NotAfter: Sep 15 16:00:00 2025 GMT
---
Server certificate
-BEGIN CERTIFICATE-
MIIGMjCCBRqgAwIBAgISA933/gWwGzwPvGuCEliwTrbPMA0GCSqGSIb3DQEBCwUA
MDIxCzAJBgNVBAYTAlVTMRYwFAYDVQQKEw1MZXQncyBFbmNyeXB0MQswCQYDVQQD
EwJSMzAeFw0yMjA4MTQwNzE2MTZaFw0yMjExMTIwNzE2MTVaMBoxGDAWBgNVBAMT
D2Zpc2gubWlyYnNkLm9yZzCCAiIwDQYJKoZIhvcNAQEBBQADggIPADCCAgoCggIB
AMZcYzruTphJh0thHN1SrUba1XNcIDWKBytnd1GSEvAyRHPZPrpbBY4kEFRztdZg
iIUuRSQffmmEgdCNpstXkPSZkZ7HPveTQV2oXK/T1EaoZP4PKWbO3sKZX2wMEr0x
FmDPeQfcfo3UOPWWwQYeV5ac8De9NPnEXuKafoMBNFPVtDwbJuTMmXUFjm6uxCWb
g4UIhGCKywMGhTmP6oxYCNBLi6PCZ3jByRLq/nemkKHl/YOsr9r/oP4LeDay6mDJ
xWJ9aX1V6PpbV4J4O6F0VWCNjMSV+KK0FUxny1s6w7ILzubSkGisE2cISIr8lWg+
0NB+M0sDSV4+GAPTH0bq04Yt3j2btnuH0oG0StZZLjNkRl3BFmnGRzTpEOG6SeEN
+M9VF+A7mZY/JagSaFfZlfHYFvPO96jbIAa4Bn8RjhhtW8bKWeLaVi0OG9saahCn
VXMXeTm3alET3lOGp+diAl2IrbQk80IUy9bM5eie4gluHkirM5xqO1Xv0rZ5jfJ4
1O5xRhkm71ZT8c8abe2/p0YPhGq2tLHXtDjMdJAYleic+c4iOXPTN3VOOl4Iucz5
F8il7edioa0bf/6Wgz61DpeRFjv85cYX5I2UbWOC7D219A8fJrB9NQTresI/BSz9
THRRydxSiLQmVkb6Ao55FuO7TbEvBIeSCE6OT33bZsBPAgMBAAGjggJYMIICVDAO
BgNVHQ8BAf8EBAMCBaAwHQYDVR0lBBYwFAYIKwYBBQUHAwEGCCsGAQUFBwMCMAwG
A1UdEwEB/wQCMAAwHQYDVR0OBBYEFCQz8IT0s7sJrskFItZ5nrA3XELqMB8GA1Ud
IwQYMBaAFBQusxe3WFbLrlAJQOYfr52LFMLGMFUGCCsGAQUFBwEBBEkwRzAhBggr
BgEFBQcwAYYVaHR0cDovL3IzLm8ubGVuY3Iub3JnMCIGCCsGAQUFBzAChhZodHRw
Oi8vcjMuaS5sZW5jci5vcmcvMCoGA1UdEQQjMCGCD2Zpc2gubWlyYnNkLm9yZ4IO
d3d3Lm1pcmJzZC5vcmcwTAYDVR0gBEUwQzAIBgZngQwBAgEwNwYLKwYBBAGC3xMB
AQEwKDAmBggrBgEFBQcCARYaaHR0cDovL2Nwcy5sZXRzZW5jcnlwdC5vcmcwggEC
BgorBgEEAdZ5AgQCBIHzBIHwAO4AdQApeb7wnjk5IfBWc59jpXflvld9nGAK+PlN
XSZcJV3HhYKbbND5AAAEAwBGMEQCIB3PMPGlppnMneCfwDxozkJzKTwhys8Z
DhUvU6WDD2KQAiA6sfxnk72LGLxEv7qWjyPBbA9o7/QZKAq34QmMg63KiAB1AEHI
yrHfIkZKEMahOglCh15OMYsbA+vrS8do8JBilgb2AAABgpts0wYAAAQDAEYwRAIg
Ob+e77xpbe10RPB9sp1IwRc7Bk/Oe1RP5YDmOgk2BVQCIG74jX2VsC6Hhe3hlilr
DmlYh3mWRqC/CPKx3N8ymdVxMA0GCSqGSIb3DQEBCwUAA4IBAQCfEGT2fDCjRlTO
weYlN8UUc/S2SXHUet+eDQNRBA/+w9HCggLd/Iw0nX+7EEFKP8fXHrYFwTtDwCjG
v1qFpEvQFMEfmcRVEQWdvt8VSjBhRxYXFcxWazBfOqo5ZmRVdQChytx7PHwbl1jW
CELQ41COfNw9TS8i4VixGxauEIx6YDWuA0cFfe+3UaANosW7y2gPJqGjA1PZaV3E
Dn9wTPJGN2F+XkvNxdohqCQLh9N69mR4DMnQ39gd7uhGszobx5u7Y6Ih5zVEqsFF
kHrxG9/h69tMCRKhtgmLZwVk/ZZ/dXDKFPDFJbnpwD+FB2O7f+bcBA3uw2809nBo
DkHfZ0Rc
-END CERTIFICATE-
subject=CN = fish.mirbsd.org
issuer=C = US, O = Let's Encrypt, CN = R3
---
No client certificate CA names sent
Server Temp Key: DH, 2048 bits
---
SSL handshake has read 4035 bytes and written 134 bytes
Verification: OK
---
New, (NONE), Cipher is (NONE)
Server public key is 4096 bit
Secure Renegotiation IS NOT supported
Compression: NONE
Expansion: NONE
No ALPN negotiated
SSL-Session:
Protocol  : TLSv1
Cipher: 
Session-ID: 0B21021F7E84628356DF05BD801681058EB87148083C224017E4AA4DEC59B243
Session-ID-ctx:
Master-Key:
PSK identity: None
PSK identity hint: None
SRP username: None
Start Time: 1664051609
Timeout   : 7200 (sec)
Verify return code: 0 (ok)
Extended master secret: no
---
$ _

So it opens the connection but cannot use it. (Note that, while
-legacy

Bug#1020013: marked as done (wine: FTBFS: unsatisfiable build-dependency: unicode-data (< 15) but 15.0.0-1 is to be installed)

[Debian Bug Tracking System]

Your message dated Sat, 24 Sep 2022 23:56:02 +
with message-id 
and subject line Bug#1020013: fixed in wine 7.0~repack-8
has caused the Debian Bug report #1020013,
regarding wine: FTBFS: unsatisfiable build-dependency: unicode-data (< 15) but 
15.0.0-1 is to be installed
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.)


-- 
1020013: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1020013
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: wine
Version: 7.0~repack-7
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20220917 ftbfs-bookworm

Hi,

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


Relevant part (hopefully):
> +--+
> | Install package build dependencies  
>  |
> +--+
> 
> 
> Setup apt archive
> -
> 
> Merged Build-Depends: dpkg (>= 1.21.0), debhelper-compat (= 13), 
> gcc-mingw-w64-x86-64, libz-mingw-w64-dev, lzma, flex, bison, quilt, unzip, 
> gettext, icoutils, sharutils, pkg-config, dctrl-tools, imagemagick, 
> librsvg2-bin, fontforge-nox, khronos-api (>= 4.6), unicode-data (>= 14), 
> unicode-data (<< 15), libxi-dev, libxt-dev, libxmu-dev, libx11-dev, 
> libxext-dev, libxfixes-dev, libxrandr-dev, libxcursor-dev, libxrender-dev, 
> libxkbfile-dev, libxxf86vm-dev, libxxf86dga-dev, libxinerama-dev, 
> libgl1-mesa-dev, libglu1-mesa-dev, libxcomposite-dev, libxml-simple-perl, 
> libxml-parser-perl, libjxr-dev, libpng-dev, libssl-dev, libv4l-dev, 
> libsdl2-dev, libxml2-dev, libgsm1-dev, libjpeg-dev, libkrb5-dev, libtiff-dev, 
> libudev-dev, libpulse-dev, liblcms2-dev, libldap2-dev, libxslt1-dev, 
> unixodbc-dev, libcups2-dev, libvkd3d-dev (>= 1.2), libcapi20-dev, 
> libvulkan-dev, libfaudio-dev (>= 19.06.07), libopenal-dev, libdbus-1-dev, 
> freeglut3-dev, libmpg123-dev, libunwind-dev, libasound2-dev, libgphoto2-dev, 
> libosmesa6-dev, libpcap0.8-dev, libgnutls28-dev, libncurses5-dev, 
> libusb-1.0-0-dev, libgettextpo-dev, libfreetype6-dev (>= 2.6.2), 
> libfontconfig1-dev, ocl-icd-opencl-dev, libgstreamer-plugins-base1.0-dev, 
> build-essential, fakeroot
> Filtered Build-Depends: dpkg (>= 1.21.0), debhelper-compat (= 13), 
> gcc-mingw-w64-x86-64, libz-mingw-w64-dev, lzma, flex, bison, quilt, unzip, 
> gettext, icoutils, sharutils, pkg-config, dctrl-tools, imagemagick, 
> librsvg2-bin, fontforge-nox, khronos-api (>= 4.6), unicode-data (>= 14), 
> unicode-data (<< 15), libxi-dev, libxt-dev, libxmu-dev, libx11-dev, 
> libxext-dev, libxfixes-dev, libxrandr-dev, libxcursor-dev, libxrender-dev, 
> libxkbfile-dev, libxxf86vm-dev, libxxf86dga-dev, libxinerama-dev, 
> libgl1-mesa-dev, libglu1-mesa-dev, libxcomposite-dev, libxml-simple-perl, 
> libxml-parser-perl, libjxr-dev, libpng-dev, libssl-dev, libv4l-dev, 
> libsdl2-dev, libxml2-dev, libgsm1-dev, libjpeg-dev, libkrb5-dev, libtiff-dev, 
> libudev-dev, libpulse-dev, liblcms2-dev, libldap2-dev, libxslt1-dev, 
> unixodbc-dev, libcups2-dev, libvkd3d-dev (>= 1.2), libcapi20-dev, 
> libvulkan-dev, libfaudio-dev (>= 19.06.07), libopenal-dev, libdbus-1-dev, 
> freeglut3-dev, libmpg123-dev, libunwind-dev, libasound2-dev, libgphoto2-dev, 
> libosmesa6-dev, libpcap0.8-dev, libgnutls28-dev, libncurses5-dev, 
> libusb-1.0-0-dev, libgettextpo-dev, libfreetype6-dev (>= 2.6.2), 
> libfontconfig1-dev, ocl-icd-opencl-dev, libgstreamer-plugins-base1.0-dev, 
> build-essential, fakeroot
> dpkg-deb: building package 'sbuild-build-depends-main-dummy' in 
> '/<>/apt_archive/sbuild-build-depends-main-dummy.deb'.
> Ign:1 copy:/<>/apt_archive ./ InRelease
> Get:2 copy:/<>/apt_archive ./ Release [963 B]
> Ign:3 copy:/<>/apt_archive ./ Release.gpg
> Get:4 copy:/<>/apt_archive ./ Sources [864 B]
> Get:5 copy:/<>/apt_archive ./ Packages [931 B]
> Fetched 2758 B in 0s (231 kB/s)
> Reading package lists...
> Reading package lists...
> 
> Install main build dependencies (apt-based resolver)
> 
> 
> Installing build dependencies
> Reading package lists...
> Building dependency tree...
> Some packages could not be installed. This may mean that you have
> requested an impossible situation or if you are using the unstable
> distribution that some required packages have not yet been created
> or been moved out of Incoming.
> The following information may help to resolve the situation:
> 
> The following packages have unmet de

Bug#1017106: marked as done (vkd3d: build depends on strictly versioned arch:all binary of itself)

[Debian Bug Tracking System]

Your message dated Sat, 24 Sep 2022 23:55:05 +
with message-id 
and subject line Bug#1017106: fixed in vkd3d 1.2-15
has caused the Debian Bug report #1017106,
regarding vkd3d: build depends on strictly versioned arch:all binary of itself
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.)


-- 
1017106: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1017106
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: vkd3d
Version: 1.2-13
Severity: serious
Justification: ftbfs

Dear maintainer,

Your package currently doesn't get build on ppc64el because it
build-depends on the to-be-build version of libvkd3d-headers, but the
version available on ppc64el is the previously built version.

Your trick seems to have worked on other architectures, but it's a
race condition (and doesn't work elsewhere).

I just discussed this on #debian-ftp

 does anybody have a clue where to look why libvkd3d-headers (arch:all) 
isn't available on ppc64el causing ppc64el to not build vkd3d
-*- elbrus stares at https://buildd.debian.org/status/package.php?p=vkd3d
 because -13 is the current version on ppc64el, but it wants -14
 how can this work?=
 it can't
 of course
 but it's an interesting idea: build-depending on itself, just another 
architecture
 sorry, I should have spotted that
-*- elbrus will file a bug
 thx
 worked elsewhere
 dak is supposed to export only arch-all packages of the matching 
version. maybe this does not work always or what
 aka if a source got arch-any with version 1 and arch-all with version 1 
and 2, only the version 1 should be available in the Packages files
 maybe that doesn't extend to incoming?
 ie there's a ~6h window where you *can* pull in the arch:all version
 the header dependency is !i386 !amd64 and the arm64 build picked it up 
from incoming
 right, incoming. yes that makes sense then

Paul
--- End Message ---
--- Begin Message ---
Source: vkd3d
Source-Version: 1.2-15
Done: Michael Gilbert 

We believe that the bug you reported is fixed in the latest version of
vkd3d, 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 1017...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Michael Gilbert  (supplier of updated vkd3d 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: Sat, 24 Sep 2022 22:45:33 +
Source: vkd3d
Architecture: source
Version: 1.2-15
Distribution: unstable
Urgency: medium
Maintainer: Debian Wine Party 
Changed-By: Michael Gilbert 
Closes: 1017106
Changes:
 vkd3d (1.2-15) unstable; urgency=medium
 .
   * Fix lintian warnings.
   * Enable link time optimization.
   * Build headers on any architecture (closes: #1017106).
Checksums-Sha1:
 3bd7228b4e6ad7b7785e4f2cc38340661d1f6d6f 3908 vkd3d_1.2-15.dsc
 99373e9090deb8a956594da771c7b0307953f0b5 11800 vkd3d_1.2-15.debian.tar.xz
 0cedba3fe11de38e40ea6ba6aa8349e7428f91b2 7542 vkd3d_1.2-15_source.buildinfo
Checksums-Sha256:
 fbf648b649dd16fabf76949821f0b61bd485ac743bc4f30424b01f2dcfc0 3908 
vkd3d_1.2-15.dsc
 1dabe845331c9fd4e22461cf60203141e422de081f3bf550e2b6d413941983c0 11800 
vkd3d_1.2-15.debian.tar.xz
 4b0b57845d3d8c2ad3dc7ce74afe3a2827616692ca3562a4328d37fca4cf86ae 7542 
vkd3d_1.2-15_source.buildinfo
Files:
 25ee4c54bc376db942065d67af490d68 3908 libs optional vkd3d_1.2-15.dsc
 ad87bb84bfbeb0d88726238bb7f2ff5f 11800 libs optional vkd3d_1.2-15.debian.tar.xz
 b2a61b6d957ece7da6460900b0432794 7542 libs optional 
vkd3d_1.2-15_source.buildinfo

-BEGIN PGP SIGNATURE-

iQQzBAEBCgAdFiEEIwTlZiOEpzUxIyp4mD40ZYkUaygFAmMvidMACgkQmD40ZYkU
ayh9cx/+JjeJZ0EiCb2lhm85zz1o01oby39xrJEuDQumVftJyFnuZPhOja13a06t
ReanOxHfyDBXVF5EwpXIVejszFGI7b9cyU3dGuvT8skKU2ALDq+KPniPM4gYzlgH
4gX3gQhLPVyHSJZVQQC2hoG+95ibFsGEgl5rHLAA3HuRJWfNQi8bAcuCVeWfqLEE
ao3psAEMi290Kkl9c/wGb7CBelOBdoGSeWb0SCPdqdgSgeabnxs8uO9hGHhNA0nc
9eu14EMHt8INpEyDv0VM3e7X2oK+S+piSFM+SQW8Z2iwLNaMf3jCppEDK6+VPFho
RsApGOK40tcVPaickTlXoxGva5qIF6DHKc+auXAl9YaB/qO0uFpmYQgKHP6ZeaNM
mckCCQOpBf83n8clDzkvSuT45+ZhT6vEEjhohcigHXbTIGgnACXFI7aNr+ZFyEDX
6t82DZRUt1UngUwU/bUuk6UOTdjJHMDg1DKqaBRVZBp57Ej8TFL7Yvs36ZvG8Vez
i9K4um0YCujraF1rXNop4RuSkInOxWyafMKxEt/lb9Y2CwlA4oa40VKER6fDcVZA
WqNnUBqQe2TrhDXDt1sco

Processed: bug 1017313 is forwarded to https://www.postfix.org/announcements/postfix-3.6.5.html

[Debian Bug Tracking System]

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

> forwarded 1017313 https://www.postfix.org/announcements/postfix-3.6.5.html
Bug #1017313 [src:postfix] postfix: FTBFS: unistd.h:363:13: error: conflicting 
types for ‘closefrom’; have ‘void(int)’
Set Bug forwarded-to-address to 
'https://www.postfix.org/announcements/postfix-3.6.5.html'.
> thanks
Stopping processing here.

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

Bug#1019855: Fwd: libc6: immediately crashes with SIGILL on 4th gen Intel Core CPUs (seems related to AVX2 instructions), bricking the whole system

[debian-bug-report]

Hello, sorry for delayed response, I've managed to collect and analyze a 
few coredump files with valid symbols (I installed libc6-dbg and 
dpkg-dev, and pointed gdb at Debian's debuginfod server, also used 
apt-get source to get the sources for libc6).


It seems there are at least 3-4 distinct places it crashes at, two 
places at memchr-avx2.S, one at strlen-avx2.S, and potentially one at 
syscall-template.S, although that last one may be just some kind of kill 
signal redirect.


Pasting all below:

Core was generated by `apt'.
Program terminated with signal SIGILL, Illegal instruction.
#0  __memchr_avx2 () at ../sysdeps/x86_64/multiarch/memchr-avx2.S:400
Download failed: Invalid argument.  Continuing without source file 
./string/../sysdeps/x86_64/multiarch/memchr-avx2.S.
400 ../sysdeps/x86_64/multiarch/memchr-avx2.S: No such file or 
directory.

(gdb)

###

Core was generated by `dpkg'.
Program terminated with signal SIGILL, Illegal instruction.
#0  __strlen_avx2 () at ../sysdeps/x86_64/multiarch/strlen-avx2.S:514
Download failed: Invalid argument.  Continuing without source file 
./string/../sysdeps/x86_64/multiarch/strlen-avx2.S.
514 ../sysdeps/x86_64/multiarch/strlen-avx2.S: No such file or 
directory.

(gdb)

###

Core was generated by `/usr/bin/perl /usr/sbin/adduser'.
Program terminated with signal SIGILL, Illegal instruction.
#0  __memchr_avx2 () at ../sysdeps/x86_64/multiarch/memchr-avx2.S:135
Download failed: Invalid argument.  Continuing without source file 
./string/../sysdeps/x86_64/multiarch/memchr-avx2.S.
135 ../sysdeps/x86_64/multiarch/memchr-avx2.S: No such file or 
directory.

(gdb)

###

Core was generated by `useradd'.
Program terminated with signal SIGILL, Illegal instruction.
#0  __memchr_avx2 () at ../sysdeps/x86_64/multiarch/memchr-avx2.S:135
Download failed: Invalid argument.  Continuing without source file 
./string/../sysdeps/x86_64/multiarch/memchr-avx2.S.
135 ../sysdeps/x86_64/multiarch/memchr-avx2.S: No such file or 
directory.

(gdb)

###

Core was generated by `passwd'.
Program terminated with signal SIGILL, Illegal instruction.
#0  __strlen_avx2 () at ../sysdeps/x86_64/multiarch/strlen-avx2.S:514
Download failed: Invalid argument.  Continuing without source file 
./string/../sysdeps/x86_64/multiarch/strlen-avx2.S.
514 ../sysdeps/x86_64/multiarch/strlen-avx2.S: No such file or 
directory.

(gdb)

###

Core was generated by `bash'.
Program terminated with signal SIGILL, Illegal instruction.
#0  0x7f2006faf087 in kill () at ../sysdeps/unix/syscall-template.S:120
Download failed: Invalid argument.  Continuing without source file 
./signal/../sysdeps/unix/syscall-template.S.

120 ../sysdeps/unix/syscall-template.S: No such file or directory.
(gdb)

###

Core was generated by `su'.
Program terminated with signal SIGILL, Illegal instruction.
#0  __memchr_avx2 () at ../sysdeps/x86_64/multiarch/memchr-avx2.S:135
Download failed: Invalid argument.  Continuing without source file 
./string/../sysdeps/x86_64/multiarch/memchr-avx2.S.
135 ../sysdeps/x86_64/multiarch/memchr-avx2.S: No such file or 
directory.

(gdb)

###

It does seem in case of this SIGILL there's no additional stack trace, 
also the path containing ".." seems to cause the source code resolution 
to fail, but still the debug symbols seem to show the file source and 
line, so it should hopefully help see what exactly fails.


I'm yet to try rebooting with microcode package installed though (I'll 
soon check it and update on whether it helps, but even if it does, one 
without bootable system first won't get a chance to install it; I'm a 
bit curious how these changes did trigger this, given all these years it 
didn't happen to occur before)

Bug#1020642: webkit2gtk: FTBFS on mipsel: virtual memory exhausted

[Alberto Garcia]

On Sat, Sep 24, 2022 at 06:39:25PM +0100, Simon McVittie wrote:

> webkit2gtk repeatedly failed to compile on the mipsel buildds:
> 
> :
> > FAILED: 
> > Source/WebCore/CMakeFiles/WebCore.dir/__/__/WebCore/DerivedSources/unified-sources/UnifiedSource-3a52ce78-32.cpp.o
> >  
> > /usr/bin/ccache /usr/bin/c++ [long command-line removed]
> > virtual memory exhausted: Cannot allocate memory
> 
> Can we perhaps disable the use of "unified" sources (fewer, larger
> translation units) for architectures where address space is
> limited?  Or maybe tell the compiler not to attempt memory-hungry
> optimizations, or something like that?

I was talking to Adrian Bunk about this a couple of days ago, he
was trying to build webkit in a mipsel buildd using different
alternatives.

Adrian, did you figure something out?

> I see this unreleased commit is available in git:
> https://salsa.debian.org/webkit-team/webkit/-/commit/e92e4c4654e6fd116ef30c5cc767cc25b675ed1f
> which might also help.

According to Adrian it probably won't (I didn't test it yet).

Berto

Bug#1014868: python3-pyaudio: needs patch for python 3.10

[Hubert Pham]

Thanks Thomas. Indeed, upstream PyAudio 0.2.12 fixes the issue with Python 
3.10. I have also updated the packaging, and I am working with Felipe Sateler 
to get it uploaded.

Thanks,
Hubert

Bug#1020652: openssl: tls_process_key_exchange:internal error:../ssl/statem/statem_clnt.c:2254:

[Thorsten Glaser]

Package: openssl
Version: 3.0.5-4
Severity: serious
Justification: does not work any more
X-Debbugs-Cc: t...@mirbsd.de

$ openssl s_client -CApath /etc/ssl/certs -connect www.mirbsd.org:443 
-legacy_renegotiation -tls1
CONNECTED(0003)
depth=2 C = US, O = Internet Security Research Group, CN = ISRG Root X1
verify return:1
depth=1 C = US, O = Let's Encrypt, CN = R3
verify return:1
depth=0 CN = fish.mirbsd.org
verify return:1
00B093C1B27F:error:0A0C0103:SSL routines:tls_process_key_exchange:internal 
error:../ssl/statem/statem_clnt.c:2254:
---
Certificate chain
 0 s:CN = fish.mirbsd.org
   i:C = US, O = Let's Encrypt, CN = R3
   a:PKEY: rsaEncryption, 4096 (bit); sigalg: RSA-SHA256
   v:NotBefore: Aug 14 07:16:16 2022 GMT; NotAfter: Nov 12 07:16:15 2022 GMT
 1 s:C = US, O = Let's Encrypt, CN = R3
   i:C = US, O = Internet Security Research Group, CN = ISRG Root X1
   a:PKEY: rsaEncryption, 2048 (bit); sigalg: RSA-SHA256
   v:NotBefore: Sep  4 00:00:00 2020 GMT; NotAfter: Sep 15 16:00:00 2025 GMT
---
Server certificate
-BEGIN CERTIFICATE-
MIIGMjCCBRqgAwIBAgISA933/gWwGzwPvGuCEliwTrbPMA0GCSqGSIb3DQEBCwUA
MDIxCzAJBgNVBAYTAlVTMRYwFAYDVQQKEw1MZXQncyBFbmNyeXB0MQswCQYDVQQD
EwJSMzAeFw0yMjA4MTQwNzE2MTZaFw0yMjExMTIwNzE2MTVaMBoxGDAWBgNVBAMT
D2Zpc2gubWlyYnNkLm9yZzCCAiIwDQYJKoZIhvcNAQEBBQADggIPADCCAgoCggIB
AMZcYzruTphJh0thHN1SrUba1XNcIDWKBytnd1GSEvAyRHPZPrpbBY4kEFRztdZg
iIUuRSQffmmEgdCNpstXkPSZkZ7HPveTQV2oXK/T1EaoZP4PKWbO3sKZX2wMEr0x
FmDPeQfcfo3UOPWWwQYeV5ac8De9NPnEXuKafoMBNFPVtDwbJuTMmXUFjm6uxCWb
g4UIhGCKywMGhTmP6oxYCNBLi6PCZ3jByRLq/nemkKHl/YOsr9r/oP4LeDay6mDJ
xWJ9aX1V6PpbV4J4O6F0VWCNjMSV+KK0FUxny1s6w7ILzubSkGisE2cISIr8lWg+
0NB+M0sDSV4+GAPTH0bq04Yt3j2btnuH0oG0StZZLjNkRl3BFmnGRzTpEOG6SeEN
+M9VF+A7mZY/JagSaFfZlfHYFvPO96jbIAa4Bn8RjhhtW8bKWeLaVi0OG9saahCn
VXMXeTm3alET3lOGp+diAl2IrbQk80IUy9bM5eie4gluHkirM5xqO1Xv0rZ5jfJ4
1O5xRhkm71ZT8c8abe2/p0YPhGq2tLHXtDjMdJAYleic+c4iOXPTN3VOOl4Iucz5
F8il7edioa0bf/6Wgz61DpeRFjv85cYX5I2UbWOC7D219A8fJrB9NQTresI/BSz9
THRRydxSiLQmVkb6Ao55FuO7TbEvBIeSCE6OT33bZsBPAgMBAAGjggJYMIICVDAO
BgNVHQ8BAf8EBAMCBaAwHQYDVR0lBBYwFAYIKwYBBQUHAwEGCCsGAQUFBwMCMAwG
A1UdEwEB/wQCMAAwHQYDVR0OBBYEFCQz8IT0s7sJrskFItZ5nrA3XELqMB8GA1Ud
IwQYMBaAFBQusxe3WFbLrlAJQOYfr52LFMLGMFUGCCsGAQUFBwEBBEkwRzAhBggr
BgEFBQcwAYYVaHR0cDovL3IzLm8ubGVuY3Iub3JnMCIGCCsGAQUFBzAChhZodHRw
Oi8vcjMuaS5sZW5jci5vcmcvMCoGA1UdEQQjMCGCD2Zpc2gubWlyYnNkLm9yZ4IO
d3d3Lm1pcmJzZC5vcmcwTAYDVR0gBEUwQzAIBgZngQwBAgEwNwYLKwYBBAGC3xMB
AQEwKDAmBggrBgEFBQcCARYaaHR0cDovL2Nwcy5sZXRzZW5jcnlwdC5vcmcwggEC
BgorBgEEAdZ5AgQCBIHzBIHwAO4AdQApeb7wnjk5IfBWc59jpXflvld9nGAK+PlN
XSZcJV3HhYKbbND5AAAEAwBGMEQCIB3PMPGlppnMneCfwDxozkJzKTwhys8Z
DhUvU6WDD2KQAiA6sfxnk72LGLxEv7qWjyPBbA9o7/QZKAq34QmMg63KiAB1AEHI
yrHfIkZKEMahOglCh15OMYsbA+vrS8do8JBilgb2AAABgpts0wYAAAQDAEYwRAIg
Ob+e77xpbe10RPB9sp1IwRc7Bk/Oe1RP5YDmOgk2BVQCIG74jX2VsC6Hhe3hlilr
DmlYh3mWRqC/CPKx3N8ymdVxMA0GCSqGSIb3DQEBCwUAA4IBAQCfEGT2fDCjRlTO
weYlN8UUc/S2SXHUet+eDQNRBA/+w9HCggLd/Iw0nX+7EEFKP8fXHrYFwTtDwCjG
v1qFpEvQFMEfmcRVEQWdvt8VSjBhRxYXFcxWazBfOqo5ZmRVdQChytx7PHwbl1jW
CELQ41COfNw9TS8i4VixGxauEIx6YDWuA0cFfe+3UaANosW7y2gPJqGjA1PZaV3E
Dn9wTPJGN2F+XkvNxdohqCQLh9N69mR4DMnQ39gd7uhGszobx5u7Y6Ih5zVEqsFF
kHrxG9/h69tMCRKhtgmLZwVk/ZZ/dXDKFPDFJbnpwD+FB2O7f+bcBA3uw2809nBo
DkHfZ0Rc
-END CERTIFICATE-
subject=CN = fish.mirbsd.org
issuer=C = US, O = Let's Encrypt, CN = R3
---
No client certificate CA names sent
Server Temp Key: DH, 2048 bits
---
SSL handshake has read 4035 bytes and written 134 bytes
Verification: OK
---
New, (NONE), Cipher is (NONE)
Server public key is 4096 bit
Secure Renegotiation IS NOT supported
Compression: NONE
Expansion: NONE
No ALPN negotiated
SSL-Session:
Protocol  : TLSv1
Cipher: 
Session-ID: 0B21021F7E84628356DF05BD801681058EB87148083C224017E4AA4DEC59B243
Session-ID-ctx:
Master-Key:
PSK identity: None
PSK identity hint: None
SRP username: None
Start Time: 1664051609
Timeout   : 7200 (sec)
Verify return code: 0 (ok)
Extended master secret: no
---
$ _

So it opens the connection but cannot use it. (Note that, while
-legacy_renegotiation seems to be required now, the server has
renegotiation disabled, it just doesn’t have the TLS extension
to signal so yet.)


-- System Information:
Debian Release: bookworm/sid
  APT prefers unstable-debug
  APT policy: (500, 'unstable-debug'), (500, 'buildd-unstable'), (500, 
'unstable'), (1, 'experimental')
merged-usr: no
Architecture: amd64 (x86_64)

Kernel: Linux 5.10.0-10-amd64 (SMP w/4 CPU threads)
Kernel taint flags: TAINT_FIRMWARE_WORKAROUND
Locale: LANG=C, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /bin/lksh
Init: sysvinit (via /sbin/init)

Versions of packages openssl depends on:
ii  libc62.35-1
ii  libssl3  3.0.5-4

openssl recommends no packages.

Versions of packages openssl suggests:
ii  ca-bundle [ca-certificates]  20190604tarent1

-- Configuration Files:
/etc/ssl/openssl.cnf changed:
HOME= .
 # Use this in order to automatically load p

Bug#1013876: Please close if fixed to migrate to testing

[Guillem Jover]

Hi!

On Fri, 2022-09-23 at 13:27:31 +, Amr Ibrahim wrote:
> On Mon, 27 Jun 2022 07:21:33 +0200 Bruno Kleinert 
> wrote:
> > thanks for the report. Something else in 1.8.0 is bugging me that may
> > be related to upstream's jQuery removal. I'm expecting upstream may
> > release 1.8.1 soonish.

> Please close this bug if fixed in unstable to migrate the package to
> testing.

I've kept the package on hold since, but try to upgrade from time to
time to see whether its fixed. Last time I did with the latest version
currently in sid, it seemed to be still broken.

Thanks,
Guillem

Bug#1020125: marked as done (apscheduler: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p 3.10 --system=custom "--test-args={interpreter} setup.py test" returned exit co

[Debian Bug Tracking System]

Your message dated Sat, 24 Sep 2022 18:34:52 +
with message-id 
and subject line Bug#1020125: fixed in apscheduler 3.9.1-2
has caused the Debian Bug report #1020125,
regarding apscheduler: FTBFS: dh_auto_test: error: pybuild --test --test-pytest 
-i python{version} -p 3.10 --system=custom "--test-args={interpreter} setup.py 
test" returned exit code 13
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.)


-- 
1020125: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1020125
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: apscheduler
Version: 3.9.1-1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20220917 ftbfs-bookworm

Hi,

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


Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> dh_auto_test -- --system=custom --test-args="{interpreter} setup.py test"
> I: pybuild base:240: python3.10 setup.py test
> /usr/lib/python3/dist-packages/setuptools/dist.py:771: UserWarning: Usage of 
> dash-separated 'upload-dir' will not be supported in future versions. Please 
> use the underscore name 'upload_dir' instead
>   warnings.warn(
> running test
> WARNING: Testing via this command is deprecated and will be removed in a 
> future version. Users looking for a generic test entry point independent of 
> test runner are encouraged to use tox.
> /usr/lib/python3/dist-packages/setuptools/installer.py:27: 
> SetuptoolsDeprecationWarning: setuptools.installer is deprecated. 
> Requirements should be satisfied by a PEP 517 installer.
>   warnings.warn(
> WARNING: The wheel package is not available.
> /usr/bin/python3.10: No module named pip
> error: Command '['/usr/bin/python3.10', '-m', 'pip', 
> '--disable-pip-version-check', 'wheel', '--no-deps', '-w', 
> '/tmp/tmpjsi4wket', '--quiet', 'pytz']' returned non-zero exit status 1.
> E: pybuild pybuild:379: test: plugin custom failed with: exit code=1: 
> python3.10 setup.py test
> dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p 3.10 
> --system=custom "--test-args={interpreter} setup.py test" returned exit code 
> 13


The full build log is available from:
http://qa-logs.debian.net/2022/09/17/apscheduler_3.9.1-1_unstable.log

All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20220917;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na&merged=ign&fnewerval=7&flastmodval=7&fusertag=only&fusertagtag=ftbfs-20220917&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 to reproduce this, please provide a build log and diff it with mine
so that we can identify if something relevant changed in the meantime.
--- End Message ---
--- Begin Message ---
Source: apscheduler
Source-Version: 3.9.1-2
Done: Laszlo Boszormenyi (GCS) 

We believe that the bug you reported is fixed in the latest version of
apscheduler, 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 1020...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Laszlo Boszormenyi (GCS)  (supplier of updated apscheduler 
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: Sat, 24 Sep 2022 19:50:49 +0200
Source: apscheduler
Architecture: source
Version: 3.9.1-2
Distribution: unstable
Urgency: medium
Maintainer: Laszlo Boszormenyi (GCS) 
Changed-By: Laszlo Boszormenyi (GCS) 
Closes: 1020125
Changes:
 apscheduler (3.9.1-2) unstable; urgency=medium
 .
   * Add python3-tz build dependency for self-testing (closes: #1020125).
Checksums-Sha1:
 5c198408856b63cf14be8a338deee0266b01ffb6 2066 apscheduler_3.9.1-2.dsc
 60cf6820399067fada881b6ea72ec683946fcd59 3848 apscheduler_3.9.1-2.debian.tar.xz
Checksums-Sha256:
 e20a7bbd525a2c39688feaa73da648410e30b0808dca5

Processed: Python 3.10 incompatibility should be severe

[Debian Bug Tracking System]

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

> severity 1014868 grave
Bug #1014868 [python3-pyaudio] python3-pyaudio: needs patch for python 3.10
Severity set to 'grave' from 'normal'
> thanks
Stopping processing here.

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

Bug#1020642: webkit2gtk: FTBFS on mipsel: virtual memory exhausted

[Simon McVittie]

Source: webkit2gtk
Version: 2.38.0-1
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)
X-Debbugs-Cc: debian-m...@lists.debian.org
User: debian-m...@lists.debian.org
Usertags: mipsel

webkit2gtk repeatedly failed to compile on the mipsel buildds:

:
> FAILED: 
> Source/WebCore/CMakeFiles/WebCore.dir/__/__/WebCore/DerivedSources/unified-sources/UnifiedSource-3a52ce78-32.cpp.o
>  
> /usr/bin/ccache /usr/bin/c++ [long command-line removed]
> virtual memory exhausted: Cannot allocate memory

Can we perhaps disable the use of "unified" sources (fewer, larger
translation units) for architectures where address space is limited?
Or maybe tell the compiler not to attempt memory-hungry optimizations,
or something like that?

I see this unreleased commit is available in git:
https://salsa.debian.org/webkit-team/webkit/-/commit/e92e4c4654e6fd116ef30c5cc767cc25b675ed1f
which might also help.

jbicha says this is stalling several unstable -> testing transitions, so it
would be good for the release process to get this resolved soon.

smcv

Bug#1017618: marked as done (nautilus-share: Incompatible with Nautilus 43)

[Debian Bug Tracking System]

Your message dated Sat, 24 Sep 2022 17:13:32 +
with message-id 
and subject line Bug#1017618: fixed in nautilus-share 0.7.5-0.1
has caused the Debian Bug report #1017618,
regarding nautilus-share: Incompatible with Nautilus 43
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.)


-- 
1017618: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1017618
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: nautilus-share
Version: 0.7.3-2
Severity: important
Tags: sid bookworm


The newest release of Nautilus, version 43, has switched to GTK4 and
includes major changes in the extensions API. Similarly, there is a
new release of nautilus-python, 4.0 which also makes changes.

Both nautilus 43 and nautilus-python 4 are available in Debian
Experimental. If you install python3-nautilus3, it includes
documentation that you can view with the devhelp app. The
documentation includes a page with some details to help port your
extension.

When we upload nautilus 43 to Debian Unstable, we will need to remove
nautilus-share from Testing unless this bug is fixed, because the
extension will no longer work.

nautilus-share has been archived upstream which means bug reports and
fixes are no longer accepted:
https://gitlab.gnome.org/GNOME/nautilus-share

Thank you,
Jeremy Bicha
--- End Message ---
--- Begin Message ---
Source: nautilus-share
Source-Version: 0.7.5-0.1
Done: Jeremy Bicha 

We believe that the bug you reported is fixed in the latest version of
nautilus-share, 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 1017...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Jeremy Bicha  (supplier of updated nautilus-share 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: Sat, 24 Sep 2022 12:02:03 -0400
Source: nautilus-share
Built-For-Profiles: noudeb
Architecture: source
Version: 0.7.5-0.1
Distribution: unstable
Urgency: high
Maintainer: Chow Loong Jin 
Changed-By: Jeremy Bicha 
Closes: 760342 1008974 1017618
Changes:
 nautilus-share (0.7.5-0.1) unstable; urgency=high
 .
   * Non-maintainer upload
   * New upstream release (Closes: #1017618)
 - Includes support for samba 4.15 (Closes: #1008974)
   * Update debian/watch for new upstream location
   * Build with meson
   * Build with nautilus 43 and gtk4
   * Build with debhelper-compat 13
   * Update the packaging a bit while we're here
   * Bump Standards-Version to 4.6.1
   * Drop 02_install_missing_samba.patch:
 - This used an undeclared dependency on Synaptic to attempt to
   install samba and libpam-smbpass (which hasn't existed for years).
   Also, this would have needed to be ported to GTK4. (Closes: #760342)
   * Drop all other patches: obsolete or applied in new release
   * Depend on samba. Drop unused dependency on gnome-session-bin
Checksums-Sha1:
 a11ca0a819be24f899067930d260e88537324f20 1804 nautilus-share_0.7.5-0.1.dsc
 b74b43a663dabdd36459acc9ec983ebf50f98e6a 76021 
nautilus-share_0.7.5.orig.tar.bz2
 cc965a9b44a0ae74f1a7391879896fce46fc6c7a 5092 
nautilus-share_0.7.5-0.1.debian.tar.xz
 1fe75dc3be6602e1804f8f8f1208b882ebabf65c 15541 
nautilus-share_0.7.5-0.1_source.buildinfo
Checksums-Sha256:
 6a1390584739bac93cbba42d598fe5b177e1eb5a0b33ff645a4a0fd17a5665e2 1804 
nautilus-share_0.7.5-0.1.dsc
 708e10e379e09907802ec4afbcffa310d03877d0bc167d01d9d0a5eb3b4f9cbc 76021 
nautilus-share_0.7.5.orig.tar.bz2
 fbcbe931fb5fa6a5e5c34086b62734fdb24191c31dac7240b10a7024e21cf583 5092 
nautilus-share_0.7.5-0.1.debian.tar.xz
 6eb60af04c1c9a73945df2fb3b6ad9f418b37562c3253dd28f66bda2b54623c2 15541 
nautilus-share_0.7.5-0.1_source.buildinfo
Files:
 e5ef98d3adb072c94723f6ac892e1598 1804 gnome optional 
nautilus-share_0.7.5-0.1.dsc
 c010163e8dc90717f340e9d70088902d 76021 gnome optional 
nautilus-share_0.7.5.orig.tar.bz2
 b6401fc22efbdea24c084ce49ce0a943 5092 gnome optional 
nautilus-share_0.7.5-0.1.debian.tar.xz
 955c42a2ef9cd77c2c9e790d4d22d670 15541 gnome optional 
nautilus-share_0.7.5-0.1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEETQvhLw5HdtiqzpaW5mx3Wuv+bH0FAmMvMRcACgkQ5mx3Wuv+
bH31HQ/8CUmLSzHj2CESWmf2uPk0C39xPbrGksWvXqlGrkC8pQenr8CvNUM

Bug#1020031: marked as done (khmer: FTBFS: ld: cannot find build/temp.linux-x86_64-3.10/src/khmer/_cpy_khmer.o: No such file or directory)

[Debian Bug Tracking System]

Your message dated Sat, 24 Sep 2022 17:09:32 +
with message-id 
and subject line Bug#1020031: fixed in khmer 3.0.0~a3+dfsg-4
has caused the Debian Bug report #1020031,
regarding khmer: FTBFS: ld: cannot find 
build/temp.linux-x86_64-3.10/src/khmer/_cpy_khmer.o: No such file or directory
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.)


-- 
1020031: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1020031
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: khmer
Version: 3.0.0~a3+dfsg-3
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20220917 ftbfs-bookworm

Hi,

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


Relevant part (hopefully):
> x86_64-linux-gnu-g++ -shared -Wl,-O1 -Wl,-Bsymbolic-functions -g -fwrapv -O2 
> -Wl,-z,relro -Wl,-z,now -g -O2 -ffile-prefix-map=/<>=. 
> -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
> -D_FORTIFY_SOURCE=2 
> build/temp.linux-x86_64-cpython-310/khmer/_oxli/oxli_exception_convert.o 
> build/temp.linux-x86_64-cpython-310/khmer/_oxli/readaligner.o 
> build/temp.linux-x86_64-3.10/src/khmer/_cpy_khmer.o 
> build/temp.linux-x86_64-3.10/src/khmer/_cpy_utils.o 
> build/temp.linux-x86_64-3.10/src/khmer/_cpy_readparsers.o 
> build/temp.linux-x86_64-3.10/src/oxli/read_parsers.o 
> build/temp.linux-x86_64-3.10/src/oxli/kmer_hash.o 
> build/temp.linux-x86_64-3.10/src/oxli/hashtable.o 
> build/temp.linux-x86_64-3.10/src/oxli/hashgraph.o 
> build/temp.linux-x86_64-3.10/src/oxli/labelhash.o 
> build/temp.linux-x86_64-3.10/src/oxli/subset.o 
> build/temp.linux-x86_64-3.10/src/oxli/read_aligner.o 
> build/temp.linux-x86_64-3.10/src/oxli/hllcounter.o 
> build/temp.linux-x86_64-3.10/src/oxli/traversal.o 
> build/temp.linux-x86_64-3.10/src/oxli/kmer_filters.o 
> build/temp.linux-x86_64-3.10/src/oxli/assembler.o 
> build/temp.linux-x86_64-3.10/src/oxli/alphabets.o 
> build/temp.linux-x86_64-3.10/src/oxli/storage.o 
> build/temp.linux-x86_64-3.10/third-party/smhasher/MurmurHash3.o 
> third-party/cqf/gqf.o -L/usr/lib/x86_64-linux-gnu -lz -lbz2 -o 
> /<>/.pybuild/cpython3_3.10_khmer/build/khmer/_oxli/readaligner.cpython-310-x86_64-linux-gnu.so
>  -fopenmp
> /usr/bin/ld: cannot find build/temp.linux-x86_64-3.10/src/khmer/_cpy_khmer.o: 
> No such file or directory
> /usr/bin/ld: cannot find build/temp.linux-x86_64-3.10/src/khmer/_cpy_utils.o: 
> No such file or directory
> /usr/bin/ld: cannot find 
> build/temp.linux-x86_64-3.10/src/khmer/_cpy_readparsers.o: No such file or 
> directory
> /usr/bin/ld: cannot find 
> build/temp.linux-x86_64-3.10/src/oxli/read_parsers.o: No such file or 
> directory
> /usr/bin/ld: cannot find build/temp.linux-x86_64-3.10/src/oxli/kmer_hash.o: 
> No such file or directory
> /usr/bin/ld: cannot find build/temp.linux-x86_64-3.10/src/oxli/hashtable.o: 
> No such file or directory
> /usr/bin/ld: cannot find build/temp.linux-x86_64-3.10/src/oxli/hashgraph.o: 
> No such file or directory
> /usr/bin/ld: cannot find build/temp.linux-x86_64-3.10/src/oxli/labelhash.o: 
> No such file or directory
> /usr/bin/ld: cannot find build/temp.linux-x86_64-3.10/src/oxli/subset.o: No 
> such file or directory
> /usr/bin/ld: cannot find 
> build/temp.linux-x86_64-3.10/src/oxli/read_aligner.o: No such file or 
> directory
> /usr/bin/ld: cannot find build/temp.linux-x86_64-3.10/src/oxli/hllcounter.o: 
> No such file or directory
> /usr/bin/ld: cannot find build/temp.linux-x86_64-3.10/src/oxli/traversal.o: 
> No such file or directory
> /usr/bin/ld: cannot find 
> build/temp.linux-x86_64-3.10/src/oxli/kmer_filters.o: No such file or 
> directory
> /usr/bin/ld: cannot find build/temp.linux-x86_64-3.10/src/oxli/assembler.o: 
> No such file or directory
> /usr/bin/ld: cannot find build/temp.linux-x86_64-3.10/src/oxli/alphabets.o: 
> No such file or directory
> /usr/bin/ld: cannot find build/temp.linux-x86_64-3.10/src/oxli/storage.o: No 
> such file or directory
> /usr/bin/ld: cannot find 
> build/temp.linux-x86_64-3.10/third-party/smhasher/MurmurHash3.o: No such file 
> or directory
> collect2: error: ld returned 1 exit status


The full build log is available from:
http://qa-logs.debian.net/2022/09/17/khmer_3.0.0~a3+dfsg-3_unstable.log

All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20220917;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na&merged=ign&fnewerval=7&flastmodval=7&fusertag=only&fusertagtag=ftbfs-20220917&fusertaguser=lu...@debian.org&allbugs=1&cseverity=1&ctags=1&c

Bug#1020447: marked as done (src:aircrack-ng: fails to migrate to testing for too long: not build on s390x)

[Debian Bug Tracking System]

Your message dated Sat, 24 Sep 2022 17:04:55 +
with message-id 
and subject line Bug#1020447: fixed in aircrack-ng 1:1.7-5
has caused the Debian Bug report #1020447,
regarding src:aircrack-ng: fails to migrate to testing for too long: not build 
on s390x
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.)


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

Source: aircrack-ng
Version: 1:1.6+git20210130.91820bc-2
Severity: serious
Control: close -1 1:1.7-3
Tags: sid bookworm
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 60 days as having a Release Critical bug in 
testing [1]. Your package src:aircrack-ng has been trying to migrate for 
69 days [2]. Hence, I am filing this bug. Your package stopped building 
on s390x, because it FTBFS there, but the binaries are still lingering 
around. The s390x situation needs to be resolved somehow.


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 bookworm, 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/2020/02/msg5.html
[2] https://qa.debian.org/excuses.php?package=aircrack-ng



OpenPGP_signature
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Source: aircrack-ng
Source-Version: 1:1.7-5
Done: Samuel Henrique 

We believe that the bug you reported is fixed in the latest version of
aircrack-ng, 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 1020...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Samuel Henrique  (supplier of updated aircrack-ng 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: Sat, 24 Sep 2022 15:56:42 +0100
Source: aircrack-ng
Architecture: source
Version: 1:1.7-5
Distribution: unstable
Urgency: medium
Maintainer: Debian Security Tools 
Changed-By: Samuel Henrique 
Closes: 1017993 1020447
Changes:
 aircrack-ng (1:1.7-5) unstable; urgency=medium
 .
   * Upload to unstable:
 - d/p/s390x_ftbfs.patch: New patch suggested by upstream to address s390x
   FTBFS (closes: #1017993, #1020447)
Checksums-Sha1:
 6cfbb3bed73a10d79edcb0582b33eefefb4f1711 2268 aircrack-ng_1.7-5.dsc
 9efc39c8855cac0a6e1a8e447c0941340e7c8204 15688 aircrack-ng_1.7-5.debian.tar.xz
 4fc3572257d437fc9f95af601a636fd666e77cb3 8137 aircrack-ng_1.7-5_amd64.buildinfo
Checksums-Sha256:
 7387e6617899f4b5ed4588922d3140bd330feb0c05c818c3708a23cd7b08a585 2268 
aircrack-ng_1.7-5.dsc
 835f0cc9224ddffd83bd636f8f6636dcfa5c4a146c20481d9b0c578372169059 15688 
aircrack-ng_1.7-5.debian.tar.xz
 ec5154562ebe57b34ad2cac50cb1c12ca5d11a6064372fe9b1931371131ff94e 8137 
aircrack-ng_1.7-5_amd64.buildinfo
Files:
 c1665f4655fc2be4eb830795105e6ddd 2268 net optional aircrack-ng_1.7-5.dsc
 ef6fd06e2b4f73abd7bb5415ae595e2b 15688 net optional 
aircrack-ng_1.7-5.debian.tar.xz
 ae68306d84b3bada648a46b47c869867 8137 net optional 
aircrack-ng_1.7-5_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEBdtqg34QX0sdAsVfu6n6rcz7RwcFAmMvGz4ACgkQu6n6rcz7
Rwd9pg/8Dwx2NDyD1ZcKMSTD+m5E05j4D1Dx9qGIslxjIjAlQk2CA1nF7XL

Bug#1019579: marked as done (Missing pre-compiled file in dependency packages lead to 'trying to overwrite file' errors)

[Debian Bug Tracking System]

Your message dated Sat, 24 Sep 2022 17:07:19 +
with message-id 
and subject line Bug#1019579: fixed in dh-raku 0.13
has caused the Debian Bug report #1019579,
regarding Missing pre-compiled file in dependency packages lead to 'trying to 
overwrite file' errors
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.)


-- 
1019579: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1019579
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: raku-json-unmarshal
Version: 0.10-1
Severity: serious
Tags: ftbfs
Control: affects -1 raku-json-marshal src:raku-json-class

https://buildd.debian.org/status/logs.php?pkg=raku-json-class&ver=0.0.18-1

...
Unpacking raku-json-unmarshal (0.10-1) ...
dpkg: error processing archive 
/tmp/apt-dpkg-install-Kxnez1/92-raku-json-unmarshal_0.10-1_arm64.deb (--unpack):
 trying to overwrite 
'/usr/lib/perl6/vendor/precomp/C847F303DB03DE97DCB92EFEE90C0526E0D4FDF0/C1/C1DA909DAD9BF713751A74EBF038C545A1EA6ECC',
 which is also in package raku-json-marshal 0.0.23-1
...


This issue might not be present on amd64.
--- End Message ---
--- Begin Message ---
Source: dh-raku
Source-Version: 0.13
Done: Dominique Dumont 

We believe that the bug you reported is fixed in the latest version of
dh-raku, 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 1019...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Dominique Dumont  (supplier of updated dh-raku 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: Sat, 24 Sep 2022 18:16:51 +0200
Source: dh-raku
Architecture: source
Version: 0.13
Distribution: unstable
Urgency: medium
Maintainer: Debian Rakudo Maintainers 
Changed-By: Dominique Dumont 
Closes: 1019579
Changes:
 dh-raku (0.13) unstable; urgency=medium
 .
   * dh_raku_build:
 * set RAKULIB variable to debian tmp dir (Closes: 1019579)
 * remove $HOME setup
 * set RAKUDO_MODULE_DEBUG to 1
Checksums-Sha1:
 6650209d7c1c1dd435c6c0ce17674651168873bc 1588 dh-raku_0.13.dsc
 91e8dc8ef9c533993e2d5f7e8b90829d729ea989 7448 dh-raku_0.13.tar.xz
 63ea5ce71206344a6c17871c814ec3145b42a6b6 7305 dh-raku_0.13_source.buildinfo
Checksums-Sha256:
 7502b17b3d169d66ac8064668e544c44cbb139ee163cc3e8069924fdd750ecaf 1588 
dh-raku_0.13.dsc
 5ca3e4fe1fe086ad1e192b590bda5085839d198c5151fc4dbad448ddee493724 7448 
dh-raku_0.13.tar.xz
 50682b23d7337ce4faeb3c30ee1e767c344fb94a25588e0a6cdfead748bfb4a7 7305 
dh-raku_0.13_source.buildinfo
Files:
 217602796abbe897be13d8c0f49fc26e 1588 interpreters optional dh-raku_0.13.dsc
 468104f054fee66906cb62c369ebfe20 7448 interpreters optional dh-raku_0.13.tar.xz
 58e2446328df06743d8c76c7357c57e9 7305 interpreters optional 
dh-raku_0.13_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEn3I5/LZk8Qsz6dwDwx9P2UmrK2wFAmMvLjQACgkQwx9P2Umr
K2wwKBAAhqWDgoL+hq/fEY1YxXY+FS+dLmoruUnATpCRo6LoHv5LhiCzJvkQ1uP2
JPcKu7Fpq9E2Dvg2sQwmN429LOrm1YnRAfuJSrmDN8VAvhS8AZldXY5hTxQEskq1
t66M0OBOhcqeU3kp68p2VaqOCZeRdAeDz09iJyrd1OsZlG1Dr6KeoSoUdXfyEq9i
bM/PTTrlgsvKAKhIjtD7vqYb3nHFub3zklNK9aiAy3VNPnSPW0/ldVCFlEWpKaui
fKPclPHAuEnpWk0OExdHuIem4532qBa3L4fbB3w0rpZBc8O1YpLKOTHmzipZzX+s
jrgUTaR9/qkWZhAvSMbP5dCCBqZLZ6x26mJdJJdlKgH41M1xcldtR5l/H2xawVNS
rqbTDjKrQDxEK1CRp6t/tDFIdogze1bX+UvVX8aeE/o/NTA/jabZBdlWmwlnjERX
5kvCPI9PSAIzw+ct2RcMp4/50i61eyG/Z+eTH7h7TBuNBSWkLlyj4NE7QZHfFOhb
kLq5C22Q8pQOAwmChS44UjoazUcSUodM5TstlVDj86yQkR5vfDdikHSadiNwhIP6
I8XF4sRXGyYuC9GmxOeMF7vjCkTAjjUVdLKRAuFtO4jK7VWMiJ4dwegEqAs0IQjf
UjdH+tojWQcCZomKDqc79mR5Oh3C/XmsQ5n5X8D/dqvcblXWbac=
=ItUs
-END PGP SIGNATURE End Message ---

Bug#983982: marked as done (bazel-bootstrap: ftbfs with GCC-11)

[Debian Bug Tracking System]

Your message dated Sat, 24 Sep 2022 17:00:13 +
with message-id 
and subject line Bug#983982: fixed in bazel-bootstrap 3.5.1+ds-5~exp2
has caused the Debian Bug report #983982,
regarding bazel-bootstrap: ftbfs with GCC-11
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.)


-- 
983982: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=983982
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:bazel-bootstrap
Version: 3.5.1+ds-3
Severity: normal
Tags: sid bookworm
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-11

[This bug is not targeted to the upcoming bullseye release]

Please keep this issue open in the bug tracker for the package it
was filed for.  If a fix in another package is required, please
file a bug for the other package (or clone), and add a block in this
package. Please keep the issue open until the package can be built in
a follow-up test rebuild.

The package fails to build in a test rebuild on at least amd64 with
gcc-11/g++-11, but succeeds to build with gcc-10/g++-10. The
severity of this report will be raised before the bookworm release,
so nothing has to be done for the bullseye release.

The full build log can be found at:
http://people.debian.org/~doko/logs/20210228/filtered/gcc11/bazel-bootstrap_3.5.1+ds-3_unstable_gcc11.log
The last lines of the build log are at the end of this report.

To build with GCC 11, either set CC=gcc-11 CXX=g++-11 explicitly,
or install the gcc, g++, gfortran, ... packages from experimental.

  apt-get -t=experimental install g++ 

Common build failures are new warnings resulting in build failures with
-Werror turned on, or new/dropped symbols in Debian symbols files.
For other C/C++ related build failures see the porting guide at
http://gcc.gnu.org/gcc-11/porting_to.html

GCC 11 defaults to the GNU++17 standard.  If your package installs
header files in /usr/include, please don't work around C++17 issues
by choosing a lower C++ standard for the package build, but fix these
issues to build with the C++17 standard.

[...]




[121 / 1,598] 4 actions running
JavacBootstrap .../devtools/build/buildjar/libskylark-deps.jar; 47s local
@debian_proto_deps//:descriptor_proto; 37s local
Compiling src/main/protobuf/failure_details.pb.cc; 27s local
Compiling third_party/ijar/mapped_file_unix.cc; 0s local





ERROR: /<>/third_party/ijar/BUILD:10:11: C++ 
compilation of rule '//third_party/ijar:zip' failed (Exit 1): gcc failed: error 
executing command 
  (cd /tmp/bazel_iK5QSBRe/out/execroot/io_bazel && \
  exec env - \
CCACHE_DISABLE=1 \
CCACHE_TEMPDIR=/<>/debian/ccachetmp \

PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games \
PWD=/proc/self/cwd \
  /usr/bin/gcc -U_FORTIFY_SOURCE -fstack-protector -Wall 
-Wunused-but-set-parameter -Wno-free-nonheap-object -fno-omit-frame-pointer -g 
'-std=c++0x' -Wdate-time '-D_FORTIFY_SOURCE=2' -g -O2 
'-ffile-prefix-map=/<>=.' -fstack-protector-strong -Wformat 
'-Werror=format-security' -MD -MF 
bazel-out/k8-dbg/bin/third_party/ijar/_objs/zip/mapped_file_unix.pic.d 
'-frandom-seed=bazel-out/k8-dbg/bin/third_party/ijar/_objs/zip/mapped_file_unix.pic.o'
 -fPIC -DBLAZE_OPENSOURCE -iquote . -iquote bazel-out/k8-dbg/bin -iquote 
external/debian_cc_deps -iquote bazel-out/k8-dbg/bin/external/debian_cc_deps 
-fno-canonical-system-headers -Wno-builtin-macro-redefined 
'-D__DATE__="redacted"' '-D__TIMESTAMP__="redacted"' '-D__TIME__="redacted"' -c 
third_party/ijar/mapped_file_unix.cc -o 
bazel-out/k8-dbg/bin/third_party/ijar/_objs/zip/mapped_file_unix.pic.o)
Execution platform: //:default_host_platform
[122 / 1,598] 3 actions running
JavacBootstrap .../devtools/build/buildjar/libskylark-deps.jar; 47s local
@debian_proto_deps//:descriptor_proto; 37s local
Compiling src/main/protobuf/failure_details.pb.cc; 27s local




third_party/ijar/mapped_file_unix.cc: In constructor 
'devtools_ijar::MappedOutputFile::MappedOutputFile(const char*, size_t)':
third_party/ijar/mapped_file_unix.cc:115:21: error: 'numeric_limits' is not a 
member of 'std'
  115 |std::numeric_limits::max());
  | ^~
third_party/ijar/mapped_file_unix.cc:115:42: error: expected primary-expression 
before '>' token
  115 |std::numeric_limits::max());
  |  ^
third_party/ijar/mapped_file_unix.cc:115:45: error: '::max' has not been 
declared; did yo

Bug#1019891: marked as done (mycli: Always crashes at runtime because the module 'sqlglot' is missing)

[Debian Bug Tracking System]

Your message dated Sat, 24 Sep 2022 17:00:43 +
with message-id 
and subject line Bug#1019891: fixed in sqlglot 6.0.4-1
has caused the Debian Bug report #1019891,
regarding mycli: Always crashes at runtime because the module 'sqlglot' is 
missing
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.)


-- 
1019891: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1019891
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: mycli
Version: 1.26.1-1
Severity: grave
Justification: renders package unusable

Dear Maintainer,

after upgrading the package `mycli`, the command fails to run.

❯ mycli
Traceback (most recent call last):
  File "/usr/bin/mycli", line 33, in 
sys.exit(load_entry_point('mycli==1.26.1', 'console_scripts',
'mycli')()) File "/usr/bin/mycli", line 25, in importlib_load_entry_point
return next(matches).load()
  File "/usr/lib/python3.10/importlib/metadata/__init__.py", line 171, in
load module = import_module(match.group('module'))
  File "/usr/lib/python3.10/importlib/__init__.py", line 126, in
import_module return _bootstrap._gcd_import(name[level:], package, level)
  File "", line 1050, in _gcd_import
  File "", line 1027, in _find_and_load
  File "", line 1006, in
_find_and_load_unlocked File "", line 688,
in _load_unlocked File "", line
883, in exec_module File "", line 241, in
_call_with_frames_removed File
"/usr/lib/python3/dist-packages/mycli/main.py", line 27, in 
import sqlglot ModuleNotFoundError: No module named 'sqlglot'

Here is the upstream commit that added this dependency:
https://github.com/dbcli/mycli/commit/b8411836350923528ecdb0c92f22d26d012c1c89

I couldn't find 'sqlglot' anywhere among the Debian packages, so I
suppose there is no easy workaround for this missing dependency.

Thank you for maintaining this.
Regards,

-- System Information:
Debian Release: bookworm/sid
  APT prefers testing
  APT policy: (800, 'testing'), (600, 'stable'), (50, 'unstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 5.19.0-1-amd64 (SMP w/6 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE,
TAINT_UNSIGNED_MODULE Locale: LANG=fr_FR.utf8, 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)

Versions of packages mycli depends on:
ii  python3 3.10.6-1
ii  python3-cli-helpers 2.2.1-1
ii  python3-click   8.0.3-1
ii  python3-configobj   5.0.6-5
ii  python3-cryptography3.4.8-2
ii  python3-pkg-resources   59.6.0-1.2
ii  python3-prompt-toolkit  3.0.31-1
ii  python3-pyaes   1.6.1-4
ii  python3-pygments2.12.0+dfsg-2
ii  python3-pymysql 1.0.2-2
ii  python3-pyperclip   1.8.2-2
ii  python3-sqlparse0.4.2-1
ii  python3-tabulate0.8.9-1
ii  python3-terminaltables  3.1.0-4

mycli recommends no packages.

mycli suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: sqlglot
Source-Version: 6.0.4-1
Done: Daniel Baumann 

We believe that the bug you reported is fixed in the latest version of
sqlglot, 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 1019...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Daniel Baumann  (supplier of updated sqlglot 
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, 15 Sep 2022 18:48:01 +0200
Source: sqlglot
Binary: python3-sqlglot
Architecture: source all
Version: 6.0.4-1
Distribution: sid
Urgency: medium
Maintainer: Daniel Baumann 
Changed-By: Daniel Baumann 
Description:
 python3-sqlglot - SQL parser, transpiler, and optimizer for Python
Closes: 1019891
Changes:
 sqlglot (6.0.4-1) sid; urgency=medium
 .
   * Initial upload to sid (Closes: #1019891),
 required for mycli.
Checksums-Sha1:
 afb0efcc7fdb6eef3dea0dc993da179555630b9d 1970 sqlglot_6.0.4-1.dsc
 4cec5c3466bee5364a72b80982e8dc6b4c84f396 2645912 sqlglot_6.0.4.orig.tar.xz
 4496c253cb11e58cbbf54f7d43d3cc3a69eade31 1788 sqlglot_6.0.4-1.debian.tar.xz
 114f6a8f77f32302a119243804271ac89c8adb46 74692 python3-sqlglot_6.0.4-1_all.deb
 2329eaeeb3e7d4f

Bug#1020441: marked as done (linux: autopkgtest needs update for new version of gcc-11)

[Debian Bug Tracking System]

Your message dated Sat, 24 Sep 2022 17:00:17 +
with message-id 
and subject line Bug#1019749: fixed in linux 5.19.11-1
has caused the Debian Bug report #1019749,
regarding linux: autopkgtest needs update for new version of gcc-11
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.)


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

Source: linux
Version: 5.19.6-1
Severity: serious
X-Debbugs-CC: gcc...@packages.debian.org
Tags: sid bookworm
User: debian...@lists.debian.org
Usertags: needs-update
Control: affects -1 src:gcc-11

Dear maintainer(s),

With a recent upload of gcc-11 the autopkgtest of linux fails in testing 
when that autopkgtest is run with the binary packages of gcc-11 from 
unstable. It passes when run with only packages from testing (it also 
fails in testing). In tabular form:


   passfail
gcc-11 from testing11.3.0-6
linux  from testing5.19.6-1
all others from testingfrom testing

I copied some of the output at the bottom of this report.

Currently this regression is blocking the migration of gcc-11 to testing 
[1]. Of course, gcc-11 shouldn't just break your autopkgtest (or even 
worse, your package), but it seems to me that the test "only" fails on 
"Unexpected warning" and your package needs to update to the new situation.


If this is a real problem in your package (and not only in your 
autopkgtest), the right binary package(s) from gcc-11 should really add 
a versioned Breaks on the unfixed version of (one of your) package(s). 
Note: the Breaks is nice even if the issue is only in the autopkgtest as 
it helps the migration software to figure out the right versions to 
combine in the tests.


More information about this bug and the reason for filing it can be found on
https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation

Paul

[1] https://qa.debian.org/excuses.php?package=gcc-11

https://ci.debian.net/data/autopkgtest/testing/amd64/l/linux/26272813/log.gz

I: Found quick flavour cloud-amd64
I: Build for 5.19.0-1-cloud-amd64
make: Entering directory '/usr/src/linux-headers-5.19.0-1-cloud-amd64'
test -e include/generated/autoconf.h -a -e include/config/auto.conf || (
\
echo >&2;\
echo >&2 "  ERROR: Kernel configuration is invalid.";  \
echo >&2 " include/generated/autoconf.h or 
include/config/auto.conf are missing.";\
echo >&2 " Run 'make oldconfig && make prepare' on kernel src to 
fix it.";	\

echo >&2 ;   \
/bin/false)
warning: the compiler differs from the one used to build the kernel
  The kernel was built by: gcc-11 (Debian 11.3.0-5) 11.3.0
  You are using:   gcc-11 (Debian 11.3.0-6) 11.3.0
make -f /usr/src/linux-headers-5.19.0-1-common/scripts/Makefile.build 
obj=/tmp/autopkgtest-lxc.8_h2xh0q/downtmp/autopkgtest_tmp/foo \

single-build= \
need-builtin=1 need-modorder=1
   gcc-11 
-Wp,-MMD,/tmp/autopkgtest-lxc.8_h2xh0q/downtmp/autopkgtest_tmp/foo/.foo.o.d 
-nostdinc -I/usr/src/linux-headers-5.19.0-1-common/arch/x86/include 
-I./arch/x86/include/generated 
-I/usr/src/linux-headers-5.19.0-1-common/include -I./include 
-I/usr/src/linux-headers-5.19.0-1-common/arch/x86/include/uapi 
-I./arch/x86/include/generated/uapi 
-I/usr/src/linux-headers-5.19.0-1-common/include/uapi 
-I./include/generated/uapi -include 
/usr/src/linux-headers-5.19.0-1-common/include/linux/compiler-version.h 
-include /usr/src/linux-headers-5.19.0-1-common/include/linux/kconfig.h 
-include 
/usr/src/linux-headers-5.19.0-1-common/include/linux/compiler_types.h 
-D__KERNEL__ -fmacro-prefix-map=/usr/src/linux-headers-5.19.0-1-common/= 
-Wall -Wundef -Werror=strict-prototypes -Wno-trigraphs 
-fno-strict-aliasing -fno-common -fshort-wchar -fno-PIE 
-Werror=implicit-function-declaration -Werror=implicit-int 
-Werror=return-type -Wno-format-security -std=gnu11 -mno-sse -mno-mmx 
-mno-sse2 -mno-3dnow -mno-avx -fcf-protection=none -m64 -falign-jumps=1 
-falign-loops=1 -mno-80387 -mno-fp-ret-in-387 
-mpreferred-stack-boundary=3 -mskip-rax-setup -mtune=generic 
-mno-red-zone -mcmodel=kernel -Wno-sign-compare 
-fno-asynchronous-unwind-tables -mindirect-branch=thunk-extern 
-mindirect-branch-register -mindirect-branch-cs-prefix 
-mfunction-return=thunk-extern -fno-jump-tables -mharden-sls=all 
-fno-delete-null-pointer-checks -Wno-frame-address 
-Wno-format-truncation -Wno-format-ove

Bug#1019749: marked as done (linux autopkg tests fail with stderr output, blocking gcc-11)

[Debian Bug Tracking System]

Your message dated Sat, 24 Sep 2022 17:00:17 +
with message-id 
and subject line Bug#1019749: fixed in linux 5.19.11-1
has caused the Debian Bug report #1019749,
regarding linux autopkg tests fail with stderr output, blocking gcc-11
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.)


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

Package: src:linux
Version: 5.19.6-1
Severity: serious
Tags: sid bookworm

linux autopkg tests fail with stderr output, blocking gcc-11

[...]
E: Unexpected warning/error messages
autopkgtest [14:13:45]:  summary
selftestsSKIP Test restriction "isolation-machine" requires testbed 
capability "isolation-machine"
selftestsSKIP Test restriction "isolation-machine" requires testbed 
capability "isolation-machine"

python   PASS (superficial)
kbuild   FAIL stderr: E: Unexpected warning/error messages
--- End Message ---
--- Begin Message ---
Source: linux
Source-Version: 5.19.11-1
Done: Salvatore Bonaccorso 

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 1019...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Salvatore Bonaccorso  (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: SHA512

Format: 1.8
Date: Sat, 24 Sep 2022 13:05:59 +0200
Source: linux
Architecture: source
Version: 5.19.11-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Kernel Team 
Changed-By: Salvatore Bonaccorso 
Closes: 1019143 1019248 1019749
Changes:
 linux (5.19.11-1) unstable; urgency=medium
 .
   * New upstream stable update:
 https://www.kernel.org/pub/linux/kernel/v5.x/ChangeLog-5.19.7
 - [arm*] drm/vc4: hdmi: Rework power up
 - [arm*] drm/vc4: hdmi: Depends on CONFIG_PM
 - crypto: lib - remove unneeded selection of XOR_BLOCKS
 - docs: kerneldoc-preamble: Test xeCJK.sty before loading
 - [arm64] errata: Add Cortex-A510 to the repeat tlbi list
 - Bluetooth: L2CAP: Fix build errors in some archs
 - Revert "PCI/portdrv: Don't disable AER reporting in
   get_port_device_capability()"
 - HID: steam: Prevent NULL pointer dereference in steam_{recv,send}_report
 - media: pvrusb2: fix memory leak in pvr_probe
 - USB: gadget: Fix use-after-free Read in usb_udc_uevent()
 - HID: hidraw: fix memory leak in hidraw_release()
 - net: fix refcount bug in sk_psock_get (2)
 - fbdev: fb_pm2fb: Avoid potential divide by zero error
 - ftrace: Fix NULL pointer dereference in is_ftrace_trampoline when ftrace
   is dead
 - bpf: Don't redirect packets with invalid pkt_len
 - mm/rmap: Fix anon_vma->degree ambiguity leading to double-reuse
 - ALSA: usb-audio: Add quirk for LH Labs Geek Out HD Audio 1V5
 - HID: input: fix uclogic tablets
 - HID: add Lenovo Yoga C630 battery quirk
 - [amd64] HID: AMD_SFH: Add a DMI quirk entry for Chromebooks
 - HID: Add Apple Touchbar on T2 Macs in hid_have_special_driver list
 - HID: asus: ROG NKey: Ignore portion of 0x5a report
 - HID: nintendo: fix rumble worker null pointer deref
 - HID: thrustmaster: Add sparco wheel and fix array length
 - [amd64] HID: intel-ish-hid: ipc: Add Meteor Lake PCI device ID
 - ASoC: rt5640: Fix the JD voltage dropping issue
 - rtla: Fix tracer name
 - drm/amd/display: Add a missing register field for HPO DP stream encoder
 - drm/amd/display: Device flash garbage before get in OS
 - drm/amd/display: Avoid MPC infinite loop
 - drm/amd/display: Fix HDMI VSIF V3 incorrect issue
 - drm/amd/display: For stereo keep "FLIP_ANY_FRAME"
 - drm/amd/display: clear optc underflow before turn off odm clock
 - drm/amd/display: Fix TDR eDP and USB4 display light up issue
 - drm/amd/pm: skip pptable override for smu_v13_0_7
 - drm/amd/pm: Fix a potential gpu_metrics_table memory leak
 - ksmbd: return STATUS_BAD_NETWORK_NAME error status if share is not
   configured
 - neigh: fix possib

Bug#1020437: clisp FTBFS with PARI 2.15.0

[Bill Allombert]

On Wed, Sep 21, 2022 at 09:23:00PM +0300, Adrian Bunk wrote:
> Source: clisp
> Version: 1:2.49.20210628.gitde01f0f-2
> Severity: serious
> Tags: ftbfs
> 
> https://buildd.debian.org/status/logs.php?pkg=clisp&ver=1%3A2.49.20210628.gitde01f0f-2%2Bb1

To build with PARI 2.15.0-2, please apply the attached patch.

Cheers,
-- 
Bill. 

Imagine a large red swirl here. 
Index: clisp-2.49.20210628.gitde01f0f/modules/pari/pari.lisp
===
--- clisp-2.49.20210628.gitde01f0f.orig/modules/pari/pari.lisp
+++ clisp-2.49.20210628.gitde01f0f/modules/pari/pari.lisp
@@ -218,8 +218,7 @@ t.e., this is the memory size for the re
 ;; extern int factor_add_primes;
 (def-c-var factor_add_primes (:type int))
 
-;; extern ulong DEBUGFILES, DEBUGLEVEL, DEBUGMEM
-(def-c-var debugfiles (:name "DEBUGFILES") (:type ulong))
+;; extern ulong DEBUGLEVEL, DEBUGMEM
 (def-c-var debuglevel (:name "DEBUGLEVEL") (:type ulong))
 (def-c-var debugmem (:name "DEBUGMEM") (:type ulong))
 

Processed (with 1 error): your mail

[Debian Bug Tracking System]

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

> severity 1020639 important
Bug #1020639 [pdfarranger] pdfarranger: libqpdf 11 require pdfarranger 1.9.1
Severity set to 'important' from 'grave'
> Lowering serverity because pdfarranger as NOT YET been removed from testing
Unknown command or malformed arguments to command.
>
End of message, stopping processing here.

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

Bug#1017313: postfix: FTBFS: unistd.h:363:13: error: conflicting types for ‘closefrom’; have ‘void(int)’

[Scott Kitterman]

On Saturday, September 24, 2022 5:40:20 AM EDT Christian Göttsche wrote:
> control: tags -1 fixed-upstream
> 
> The issue is fixed upstream in version 3.6.5[1].
> 
> [1]: https://www.postfix.org/announcements/postfix-3.6.5.html

Thanks.  I'm way behind on updating postfix.  I'll try to find the time.

Scott K

Bug#1020639: (no subject)

[Jerome Robert]

severity 1020639 important

Lowering serverity because pdfarranger as NOT YET been removed from testing

Bug#1020639: pdfarranger: libqpdf 11 require pdfarranger 1.9.1

[Jérôme Robert]

Package: pdfarranger
Version: 1.8.2-1
Severity: grave
Tags: upstream
Justification: renders package unusable
X-Debbugs-Cc: jeromerob...@gmx.com

Dear Maintainer,

pdfarranger depends on pikepdf. pikepdf 5.1.1 FTBS with libqpdf 11:

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

According to Salsa pikepdf 6 is about to be uploaded. Once done
pdfarranger will stop working because of:

https://github.com/pdfarranger/pdfarranger/issues/716

So pdfarranger should be updated to 1.9.1.

Tagging as grave because pdfarranger has already been removed from
testing because pikepdf was removed from testing because of 1019694.
Once pikepdf will be back in version 6 pdfarranger will be unusable.

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

Kernel: Linux 5.19.0-1-amd64 (SMP w/4 CPU threads; PREEMPT)
Kernel taint flags: TAINT_FIRMWARE_WORKAROUND
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 pdfarranger depends on:
ii  gir1.2-glib-2.01.73.0+ds-1
ii  gir1.2-gtk-3.0 3.24.34-3
ii  gir1.2-poppler-0.1822.08.0-2.1
ii  python33.10.6-1
ii  python3-cairo  1.20.1-3+b1
ii  python3-dateutil   2.8.1-6
ii  python3-gi 3.42.2-2
ii  python3-gi-cairo   3.42.2-2
ii  python3-pikepdf5.1.1+dfsg-1+b1
ii  python3-pkg-resources  65.3.0-1.1

Versions of packages pdfarranger recommends:
ii  python3-img2pdf  0.4.4-2

pdfarranger suggests no packages.

-- no debconf information

Processed (with 1 error): reassign 1019687 to dh-raku, merging 1019579 1019687, affects 1019687

[Debian Bug Tracking System]

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

> reassign 1019687 dh-raku
Bug #1019687 [raku-meta6] raku-meta6: trying to overwrite 
'/usr/lib/perl6/vendor/precomp/A234FA60C249CF61DEFEC1FD7D434DF2D0D597D5/0F/0F5CCC81E3EDCF1EE7139F2E5E72A089F34C3091',
 which is also in package raku-license-spdx 3.17.0-1
Bug reassigned from package 'raku-meta6' to 'dh-raku'.
No longer marked as found in versions raku-meta6/0.0.29-1.
Ignoring request to alter fixed versions of bug #1019687 to the same values 
previously set
> merge 1019579 1019687
Bug #1019579 [dh-raku] Missing pre-compiled file in dependency packages lead to 
'trying to overwrite file' errors
Unable to merge bugs because:
affects of #1019687 is 'raku-license-spdx' not 
'raku-json-marshal,raku-json-unmarshal,src:raku-json-class'
Failed to merge 1019579: Did not alter merged bugs.

> affects 1019687 raku-meta6
Bug #1019687 [dh-raku] raku-meta6: trying to overwrite 
'/usr/lib/perl6/vendor/precomp/A234FA60C249CF61DEFEC1FD7D434DF2D0D597D5/0F/0F5CCC81E3EDCF1EE7139F2E5E72A089F34C3091',
 which is also in package raku-license-spdx 3.17.0-1
Added indication that 1019687 affects raku-meta6
> thanks
Stopping processing here.

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

Processed: reassign 1019579 to dh-raku ..., affects 1019579

[Debian Bug Tracking System]

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

> reassign 1019579 dh-raku
Bug #1019579 [raku-json-unmarshal] raku-json-unmarshal: trying to overwrite 
'/usr/lib/perl6/vendor/precomp/C847F303DB03DE97DCB92EFEE90C0526E0D4FDF0/C1/C1DA909DAD9BF713751A74EBF038C545A1EA6ECC',
 which is also in package raku-json-marshal 0.0.23-1
Bug reassigned from package 'raku-json-unmarshal' to 'dh-raku'.
No longer marked as found in versions raku-json-unmarshal/0.10-1.
Ignoring request to alter fixed versions of bug #1019579 to the same values 
previously set
> retitle 1019579 Missing pre-compiled file in dependency packages lead to 
> 'trying to overwrite file' errors
Bug #1019579 [dh-raku] raku-json-unmarshal: trying to overwrite 
'/usr/lib/perl6/vendor/precomp/C847F303DB03DE97DCB92EFEE90C0526E0D4FDF0/C1/C1DA909DAD9BF713751A74EBF038C545A1EA6ECC',
 which is also in package raku-json-marshal 0.0.23-1
Changed Bug title to 'Missing pre-compiled file in dependency packages lead to 
'trying to overwrite file' errors' from 'raku-json-unmarshal: trying to 
overwrite 
'/usr/lib/perl6/vendor/precomp/C847F303DB03DE97DCB92EFEE90C0526E0D4FDF0/C1/C1DA909DAD9BF713751A74EBF038C545A1EA6ECC',
 which is also in package raku-json-marshal 0.0.23-1'.
> affects 1019579 raku-json-unmarshal raku-json-marshal
Bug #1019579 [dh-raku] Missing pre-compiled file in dependency packages lead to 
'trying to overwrite file' errors
Added indication that 1019579 affects raku-json-unmarshal
> thanks
Stopping processing here.

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

Processed: Bug#1020031 marked as pending in khmer

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1020031 [src:khmer] khmer: FTBFS: ld: cannot find 
build/temp.linux-x86_64-3.10/src/khmer/_cpy_khmer.o: No such file or directory
Added tag(s) pending.

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

Bug#1020031: marked as pending in khmer

[Nilesh Patra]

Control: tag -1 pending

Hello,

Bug #1020031 in khmer 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/med-team/khmer/-/commit/e6df1517f6d4cd9fc8a459eab6f17f43b5bd6372


Add patch to find object files at the right location (Closes: #1020031)


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1020031

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

[Debian Bug Tracking System]

Your message dated Sat, 24 Sep 2022 13:49:05 +
with message-id 
and subject line Bug#1020102: fixed in golang-github-mattn-go-runewidth 0.0.13-3
has caused the Debian Bug report #1020102,
regarding golang-github-mattn-go-runewidth: FTBFS: dh_auto_test: error: cd 
_build && go test -vet=off -v -p 8 github.com/mattn/go-runewidth 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.)


-- 
1020102: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1020102
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: golang-github-mattn-go-runewidth
Version: 0.0.13-2
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20220917 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 --buildsystem=golang --with=golang --builddirectory=_build
>dh_update_autotools_config -O--buildsystem=golang -O--builddirectory=_build
>dh_autoreconf -O--buildsystem=golang -O--builddirectory=_build
>dh_auto_configure -O--buildsystem=golang -O--builddirectory=_build
>dh_auto_build -O--buildsystem=golang -O--builddirectory=_build
>   cd _build && go generate -v github.com/mattn/go-runewidth
> src/github.com/mattn/go-runewidth/benchmark_test.go
> src/github.com/mattn/go-runewidth/runewidth.go
> src/github.com/mattn/go-runewidth/runewidth_posix.go
> src/github.com/mattn/go-runewidth/runewidth_posix_test.go
> src/github.com/mattn/go-runewidth/runewidth_test.go
>   cd _build && go install -trimpath -v -p 8 github.com/mattn/go-runewidth
> internal/goarch
> unicode/utf8
> internal/goos
> internal/unsafeheader
> internal/goexperiment
> runtime/internal/syscall
> internal/cpu
> runtime/internal/atomic
> internal/itoa
> sync/atomic
> internal/race
> internal/abi
> runtime/internal/math
> github.com/rivo/uniseg
> runtime/internal/sys
> math/bits
> unicode
> internal/bytealg
> math
> runtime
> internal/reflectlite
> sync
> internal/testlog
> errors
> sort
> internal/oserror
> io
> path
> strconv
> syscall
> strings
> bytes
> regexp/syntax
> time
> internal/syscall/execenv
> internal/syscall/unix
> regexp
> io/fs
> internal/poll
> os
> github.com/mattn/go-runewidth
>dh_auto_test -O--buildsystem=golang -O--builddirectory=_build
>   cd _build && go test -vet=off -v -p 8 github.com/mattn/go-runewidth
> === RUN   TestIsEastAsian
> --- PASS: TestIsEastAsian (0.00s)
> === RUN   TestIsEastAsianLCCTYPE
> --- PASS: TestIsEastAsianLCCTYPE (0.00s)
> === RUN   TestIsEastAsianLANG
> --- PASS: TestIsEastAsianLANG (0.00s)
> === RUN   TestTableChecksums
> runewidth_test.go:63: table = combining,
>   n = 555 want 553,
>   sha256 = 
> bf1cafd5aa2c3734b07a609ffd4d981cd3184e322a1b261431ff746031305cb4 want 
> fa7081e945e5b57ba6ac9e9fd20cac122cb68c6ae269a7c78da5b3b1ae559379
> runewidth_test.go:63: table = doublewidth,
>   n = 182516 want 182494,
>   sha256 = 
> 9ac302bb04ce3d81f05e5448637ec500b0e9446db57eed406bac81b933b51d57 want 
> 28d3d696c4c3e4567c43a2271dc8bcd9606bfd5d97b0ddf00f5a1e869fc48ab7
> --- FAIL: TestTableChecksums (0.05s)
> panic: runtime error: index out of range [0] with length 0 [recovered]
>   panic: runtime error: index out of range [0] with length 0
> 
> goroutine 21 [running]:
> testing.tRunner.func1.2({0x520040, 0xc20270})
>   /usr/lib/go-1.19/src/testing/testing.go:1396 +0x24e
> testing.tRunner.func1()
>   /usr/lib/go-1.19/src/testing/testing.go:1399 +0x39f
> panic({0x520040, 0xc20270})
>   /usr/lib/go-1.19/src/runtime/panic.go:884 +0x212
> github.com/mattn/go-runewidth.inTable(...)
>   
> /<>/_build/src/github.com/mattn/go-runewidth/runewidth.go:57
> github.com/mattn/go-runewidth.TestTableChecksums(0xc831e0)
>   
> /<>/_build/src/github.com/mattn/go-runewidth/runewidth_test.go:56
>  +0x38f
> testing.tRunner(0xc831e0, 0x537970)
>   /usr/lib/go-1.19/src/testing/testing.go:1446 +0x10b
> created by testing.(*T).Run
>   /usr/lib/go-1.19/src/testing/testing.go:1493 +0x35f
> FAIL  github.com/mattn/go-runewidth   0.061s
> FAIL
> dh_auto_test: error: cd _build && go test -vet=off -v -p 8 
> github.com/mattn/go-runewidth returned exit code 1


The full build log is available from:
http://qa-logs.debian.net/2022/09/17/golang-github-mattn-go-runewidth_0.0.13-2_unstable.log

All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20220917;users=lu...@debian.org
or:
https://udd.debi

Processed: found 1014982 in 3.17.0-3

[Debian Bug Tracking System]

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

> found 1014982 3.17.0-3
Bug #1014982 {Done: Markus Koschany } [src:apache-jena] 
apache-jena: CVE-2021-33192 CVE-2021-39239 CVE-2022-28890
Marked as found in versions apache-jena/3.17.0-3.
> thanks
Stopping processing here.

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

Processed: bug 1020161 is forwarded to https://github.com/golang/go/issues/55849

[Debian Bug Tracking System]

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

> forwarded 1020161 https://github.com/golang/go/issues/55849
Bug #1020161 [src:golang-golang-x-net] golang-golang-x-net: FTBFS: make: *** 
[debian/rules:11: binary] Error 25
Set Bug forwarded-to-address to 'https://github.com/golang/go/issues/55849'.
> thanks
Stopping processing here.

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

Bug#1014982: marked as done (apache-jena: CVE-2021-33192 CVE-2021-39239 CVE-2022-28890)

[Debian Bug Tracking System]

Your message dated Sat, 24 Sep 2022 12:50:55 +
with message-id 
and subject line Bug#1014982: fixed in apache-jena 4.5.0-1
has caused the Debian Bug report #1014982,
regarding apache-jena: CVE-2021-33192 CVE-2021-39239 CVE-2022-28890
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.)


-- 
1014982: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1014982
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: apache-jena
X-Debbugs-CC: t...@security.debian.org
Severity: grave
Tags: security

Hi,

The following vulnerabilities were published for apache-jena.

Unfortunately the Apache security process is quite poor and limited
information gets made available, so it might be needed to reach out
to upstream to get more detailed information.

CVE-2021-33192[0]:
| A vulnerability in the HTML pages of Apache Jena Fuseki allows an
| attacker to execute arbitrary javascript on certain page views. This
| issue affects Apache Jena Fuseki from version 2.0.0 to version 4.0.0
| (inclusive).

https://lists.apache.org/thread/sq6q94q0prqwr9vdm2wptglcq1kv98k8

CVE-2021-39239[1]:
| A vulnerability in XML processing in Apache Jena, in versions up to
| 4.1.0, may allow an attacker to execute XML External Entities (XXE),
| including exposing the contents of local files to a remote server.

https://lists.apache.org/thread/qpbfrdty7jt3yfm39hx4p9dp151sd6gm

CVE-2022-28890[2]:
| A vulnerability in the RDF/XML parser of Apache Jena allows an
| attacker to cause an external DTD to be retrieved. This issue affects
| Apache Jena version 4.4.0 and prior versions. Apache Jena 4.2.x and
| 4.3.x do not allow external entities.

https://www.openwall.com/lists/oss-security/2022/05/04/1

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

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2021-33192
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-33192
[1] https://security-tracker.debian.org/tracker/CVE-2021-39239
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-39239
[2] https://security-tracker.debian.org/tracker/CVE-2022-28890
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-28890

Please adjust the affected versions in the BTS as needed.
--- End Message ---
--- Begin Message ---
Source: apache-jena
Source-Version: 4.5.0-1
Done: Markus Koschany 

We believe that the bug you reported is fixed in the latest version of
apache-jena, 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 1014...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Markus Koschany  (supplier of updated apache-jena 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: Sat, 24 Sep 2022 13:59:54 +0200
Source: apache-jena
Architecture: source
Version: 4.5.0-1
Distribution: unstable
Urgency: high
Maintainer: Debian Java Maintainers 

Changed-By: Markus Koschany 
Closes: 1014982
Changes:
 apache-jena (4.5.0-1) unstable; urgency=high
 .
   * New upstream version 4.5.0.
 - Fix CVE-2021-33192, CVE-2021-39239 and CVE-2022-28890. Thanks to Moritz
   Mühlenhoff for the report. (Closes: #1014982)
   * Refresh the patches.
   * Add libprotobuf-java, libtitanium-json-ld-java and libjsonp2-java to
 Build-Depends.
   * Tighten dependency on libthrift-java.
   * Declare compliance with Debian Policy 4.6.1.
Checksums-Sha1:
 72550c3240b9b043c533ed8a27f413ae8a279663 2551 apache-jena_4.5.0-1.dsc
 83966a00776162e2fe2f2cba6bf00389235982ed 7814853 apache-jena_4.5.0.orig.tar.gz
 d311cdec64d028a1fd2f4783715a9a22b235298a 20992 
apache-jena_4.5.0-1.debian.tar.xz
 ebe592155d44d8a845df0afdc3f24310bd98c5b4 14248 
apache-jena_4.5.0-1_amd64.buildinfo
Checksums-Sha256:
 15538875088d36899227764b9a2aca510a45ca70b8972f9828e824e34a3a8f47 2551 
apache-jena_4.5.0-1.dsc
 8aa33419153394598d90edcc339eef814f2f2e45bac384be3ba199fb62607b08 7814853 
apache-jena_4.5.0.orig.tar.gz
 06e786cbb5c68405ad65420ed32df0aef50cbd24d79d2d1454bc9e549f0837de 20992 
apache-jena_4.5.0-1.debian.tar.xz
 249439537c2a826d0d1441859400413eaf552c2d8b31ae539e77ed0f61db40ca 14248 
a

Bug#1019994: marked as done (wheel: FTBFS: error: invalid command 'bdist_wheel')

[Debian Bug Tracking System]

Your message dated Sat, 24 Sep 2022 12:05:16 +
with message-id 
and subject line Bug#1019994: fixed in wheel 0.37.1-3
has caused the Debian Bug report #1019994,
regarding wheel: FTBFS: error: invalid command 'bdist_wheel'
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.)


-- 
1019994: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1019994
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: wheel
Version: 0.37.1-2
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20220917 ftbfs-bookworm

Hi,

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


Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> mkdir -p debian/python3-wheel-whl/usr/share/python-wheels
> python3 setup.py bdist_wheel --universal \
> -d debian/python3-wheel-whl/usr/share/python-wheels
> usage: setup.py [global_opts] cmd1 [cmd1_opts] [cmd2 [cmd2_opts] ...]
>or: setup.py --help [cmd1 cmd2 ...]
>or: setup.py --help-commands
>or: setup.py cmd --help
> 
> error: invalid command 'bdist_wheel'
> make[1]: *** [debian/rules:16: override_dh_install] Error 1


The full build log is available from:
http://qa-logs.debian.net/2022/09/17/wheel_0.37.1-2_unstable.log

All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20220917;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na&merged=ign&fnewerval=7&flastmodval=7&fusertag=only&fusertagtag=ftbfs-20220917&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 to reproduce this, please provide a build log and diff it with mine
so that we can identify if something relevant changed in the meantime.
--- End Message ---
--- Begin Message ---
Source: wheel
Source-Version: 0.37.1-3
Done: Emanuele Rocca 

We believe that the bug you reported is fixed in the latest version of
wheel, 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 1019...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Emanuele Rocca  (supplier of updated wheel 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: Sat, 24 Sep 2022 13:33:06 +0200
Source: wheel
Architecture: source
Version: 0.37.1-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Team 
Changed-By: Emanuele Rocca 
Closes: 1019994
Changes:
 wheel (0.37.1-3) unstable; urgency=medium
 .
   * Team upload
 .
   [ Scott Kitterman ]
   * Add d/s/lintian-overrides for build-depends-on-python-dev-with-no-arch-any
 since -dev packages are needed for tests
 .
   [ Emanuele Rocca ]
   * Add PYTHONPATH to `python3 setup.py bdist_wheel` in d/rules to fix FTBFS
 (Closes: #1019994)
   * Update Standards-Version to 4.6.1
Checksums-Sha1:
 7221268dfa0a7a5365a900da6c0c7adf72e1d38d 2285 wheel_0.37.1-3.dsc
 bfb6871a1ab84f21579860cb24f45c7e3b097c0e 7000 wheel_0.37.1-3.debian.tar.xz
 0277588713b9045fbea69e22df2c7150d5f43143 9290 wheel_0.37.1-3_amd64.buildinfo
Checksums-Sha256:
 67568237da267b17ca14e1857f9872e02284ede0bcfad2232cd4a47e799065ba 2285 
wheel_0.37.1-3.dsc
 fdd30359fe715174ed2d28c9c382049b07a1976b29f175eb2a0cdcf4e4b500e7 7000 
wheel_0.37.1-3.debian.tar.xz
 2f3e926fdd9b863b2e88d644e550a48b44413a6bb67dd43040b3d3989f32cccd 9290 
wheel_0.37.1-3_amd64.buildinfo
Files:
 1c424ee8d24447ea7c0ff4ce969f15b3 2285 python optional wheel_0.37.1-3.dsc
 f73a6a368671f82bcc71fe641ff812bc 7000 python optional 
wheel_0.37.1-3.debian.tar.xz
 e663de8d06daf51658eb03a8e444bfaf 9290 python optional 
wheel_0.37.1-3_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEElUWWlhkoHBf/rFiR1QhaB1D9t6MFAmMu7AUACgkQ1QhaB1D9
t6M2OA//UaKudDwQi+QVQRQLC1Lw5c/C0u4dvjhVbBYoGobrzeB3U0CWUhRd8GNp
XU0dKSTNBwfvp4L2oTwpJJyvAVjZHnXar3xe8MJVhPWCLCp5tPj2XFndy75YSgVa
6pTVCI9CSxhbiYxLERgu

Bug#1020095: marked as done (emacs-buttercup: FTBFS: make[1]: *** [Makefile:16: test-docs] Error 255)

[Debian Bug Tracking System]

Your message dated Sat, 24 Sep 2022 11:49:37 +
with message-id 
and subject line Bug#1020095: fixed in emacs-buttercup 1.26-1
has caused the Debian Bug report #1020095,
regarding emacs-buttercup: FTBFS: make[1]: *** [Makefile:16: test-docs] Error 
255
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.)


-- 
1020095: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1020095
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: emacs-buttercup
Version: 1.24-1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20220917 ftbfs-bookworm

Hi,

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


Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> emacs -batch -L . -f batch-byte-compile buttercup-compat.el
> emacs -batch -L . -f batch-byte-compile buttercup.el
> Loading /etc/emacs/site-start.d/00debian.el (source)...
> Loading /etc/emacs/site-start.d/00debian.el (source)...
> Loading /etc/emacs/site-start.d/50autoconf.el (source)...
> Loading /etc/emacs/site-start.d/50autoconf.el (source)...
> ./bin/buttercup -L . tests 
> emacs -batch -L . -l buttercup.el -f buttercup-run-markdown 
> docs/writing-tests.md
> Loading /etc/emacs/site-start.d/00debian.el (source)...
> Loading /etc/emacs/site-start.d/50autoconf.el (source)...
> Loading /etc/emacs/site-start.d/00debian.el (source)...
> Loading /etc/emacs/site-start.d/50autoconf.el (source)...
> Running 58 out of 61 specs.
> 
> A suite
>   contains a spec with an expectation
>   contains a spec with an expectationRunning 212 specs.
> 
>  (50.36ms)
> The buttercup-failed signal
>   can be raised
> A suite is just a function
>   and so is a spec
>   and so is a spec (0.14ms)
> 
> The :to-be matcher compares with `eq'
>   and has a positive case
>   and has a positive case (0.12ms)
>   and can have a negative case
>   and can have a negative case (0.17ms)
> 
> Included matchers:
>   The :to-be matcher compares with `eq'
>   The :to-be matcher compares with `eq' (0.18ms)
>   The :to-equal matcher
> works for simple literals and variables
> works for simple literals and variables (0.11ms)
> should work for compound objects
> should work for compound objects (0.21ms)
>   The :to-have-same-items-as matcher compares two lists as sets
>   The :to-have-same-items-as matcher compares two lists as sets 
> (0.47ms)
>   The :to-match matcher is for regular expressions
>   The :to-match matcher is for regular expressions (0.28ms)
>   The :to-be-truthy matcher is for boolean casting testing
>   The :to-be-truthy matcher is for boolean casting testing (0.14ms)
>   The :to-contain matcher is for finding an item in a list
>   The :to-contain matcher is for finding an item in a list (0.18ms)
>   The :to-be-less-than matcher is for mathematical comparisons
>   The :to-be-less-than matcher is for mathematical comparisons 
> (0.19ms)
>   The :to-be-greater-than matcher is for mathematical comparisons
>   The :to-be-greater-than matcher is for mathematical comparisons 
> (0.20ms)
>   The :to-be-close-to matcher is for precision math comparison
>   The :to-be-close-to matcher is for precision math comparison 
> (0.22ms)
>   The :to-throw matcher
> is for testing if an expression throws an exception
> is for testing if an expression throws an exception (0.22ms)
> accepts a symbol to check for the signal thrown
> accepts a symbol to check for the signal thrown (0.26ms)
> optionally matches arguments to signals
> optionally matches arguments to signals (0.27ms)
> 
> ERT support
>   allows you to use ERT macros in tests
>   allows you to use ERT macros in tests (0.07ms)
> 
> A spec
>   is just a function, so it can contain any code
>   is just a function, so it can contain any code (0.12ms)
>   can have more than one expectation
>   can have more than one expectation (0.21ms)
> 
> A spec using :VAR
>   has access to the variables bound in :VAR
>   has access to the variables bound in :VAR (0.13ms)
> 
> A spec using :VAR*
>   has access to the variables bound in :VAR* which can refer to symbols 
> already bound
>   has access to the variables bound in :VAR* which can refer to symbols 
> already bound (0.11ms)
> 
> A spec using `before-each' and `after-each'
>   is just a function, so it can contain any code
>   is just a function, so it can contain an

Bug#1020110: marked as done (kaptive: FTBFS: make[1]: *** [debian/rules:12: override_dh_auto_clean] Error 25)

[Debian Bug Tracking System]

Your message dated Sat, 24 Sep 2022 11:49:54 +
with message-id 
and subject line Bug#1020110: fixed in kaptive 2.0.3-2
has caused the Debian Bug report #1020110,
regarding kaptive: FTBFS: make[1]: *** [debian/rules:12: 
override_dh_auto_clean] Error 25
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.)


-- 
1020110: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1020110
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: kaptive
Version: 2.0.3-1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20220917 ftbfs-bookworm

Hi,

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


Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> dh_auto_clean
> I: pybuild base:240: python3.10 setup.py clean 
> error: Multiple top-level packages discovered in a flat-layout: ['debian', 
> 'extras', 'sample_data', 'reference_database'].
> 
> To avoid accidental inclusion of unwanted files or directories,
> setuptools will not proceed with this build.
> 
> If you are trying to create a single distribution with multiple packages
> on purpose, you should not rely on automatic discovery.
> Instead, consider the following options:
> 
> 1. set up custom discovery (`find` directive with `include` or `exclude`)
> 2. use a `src-layout`
> 3. explicitly set `py_modules` or `packages` with a list of names
> 
> To find more information, look for "package discovery" on setuptools docs.
> E: pybuild pybuild:379: clean: plugin distutils failed with: exit code=1: 
> python3.10 setup.py clean 
> dh_auto_clean: error: pybuild --clean -i python{version} -p 3.10 returned 
> exit code 13
> make[1]: *** [debian/rules:12: override_dh_auto_clean] Error 25


The full build log is available from:
http://qa-logs.debian.net/2022/09/17/kaptive_2.0.3-1_unstable.log

All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20220917;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na&merged=ign&fnewerval=7&flastmodval=7&fusertag=only&fusertagtag=ftbfs-20220917&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 to reproduce this, please provide a build log and diff it with mine
so that we can identify if something relevant changed in the meantime.
--- End Message ---
--- Begin Message ---
Source: kaptive
Source-Version: 2.0.3-2
Done: Nilesh Patra 

We believe that the bug you reported is fixed in the latest version of
kaptive, 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 1020...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Nilesh Patra  (supplier of updated kaptive 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: Sat, 24 Sep 2022 11:19:10 +
Source: kaptive
Architecture: source
Version: 2.0.3-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Med Packaging Team 

Changed-By: Nilesh Patra 
Closes: 1020110
Changes:
 kaptive (2.0.3-2) unstable; urgency=medium
 .
   * Team Upload.
   * Set packages field explicitly (Closes: #1020110)
Checksums-Sha1:
 bd95c48b76606423e1db80d52d284cc926c014d1 2161 kaptive_2.0.3-2.dsc
 dd767e6a9094844ecff8e78d12c9dd2296907745 6572 kaptive_2.0.3-2.debian.tar.xz
 ced267d7db8b00f921a758bf27cdcd38f2528013 8055 kaptive_2.0.3-2_amd64.buildinfo
Checksums-Sha256:
 0a00339b541ea77a622bb27c0e66d51aac804d98d6d3a99ce7d18d14c158878b 2161 
kaptive_2.0.3-2.dsc
 9e8fda5f9adcdf74b279f78e48fee944cdf1d81e11e7308f0113b756de506ede 6572 
kaptive_2.0.3-2.debian.tar.xz
 e441ce8794321c1abf33bdfb3e23752e0fdedc41ad84cde003012171d13e5226 8055 
kaptive_2.0.3-2_amd64.buildinfo
Files:
 40fdac69d302107399c14508de519bde 2161 science optional kaptive_2.0.3-2.dsc
 567b51d0886d582378134d294dd1f4a4 6572 science optional 
kaptive_2.0.3-2.de

Bug#1020375: closing 1020375

[Adrian Bunk]

On Fri, Sep 23, 2022 at 10:18:22PM -0700, Dima Kogan wrote:
> close 1020375 
> thanks
> 
> I uploaded 1.0+1git91f4b1-4 that explicitly state that no arch-indep
> tests are defined. This appears to have made the arch-indep builds
> happy

The arch-indep build is happy due to the binary you uploaded.

You will anyway need a source-only upload for testing migration,
this will also show whether it builds on the buildds.

cu
Adrian

Bug#1020147: marked as done (ueberzug: FTBFS: make[1]: *** [debian/rules:19: override_dh_auto_build] Error 25)

[Debian Bug Tracking System]

Your message dated Sat, 24 Sep 2022 11:34:40 +
with message-id 
and subject line Bug#1020147: fixed in ueberzug 18.1.9-3
has caused the Debian Bug report #1020147,
regarding ueberzug: FTBFS: make[1]: *** [debian/rules:19: 
override_dh_auto_build] Error 25
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.)


-- 
1020147: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1020147
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ueberzug
Version: 18.1.9-2
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20220917 ftbfs-bookworm

Hi,

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


Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> dh_auto_build
> I: pybuild base:240: /usr/bin/python3 setup.py build 
> /<>/setup.py:2: DeprecationWarning: The distutils package is 
> deprecated and slated for removal in Python 3.12. Use setuptools or check PEP 
> 632 for potential alternatives
>   import distutils.core
> /usr/lib/python3/dist-packages/_distutils_hack/__init__.py:18: UserWarning: 
> Distutils was imported before Setuptools, but importing Setuptools also 
> replaces the `distutils` module in `sys.modules`. This may lead to 
> undesirable behaviors or errors. To avoid these issues, avoid using distutils 
> directly, ensure that setuptools is installed in the traditional way (e.g. 
> not an editable install), and/or make sure that setuptools is always imported 
> before distutils.
>   warnings.warn(
> /usr/lib/python3/dist-packages/_distutils_hack/__init__.py:33: UserWarning: 
> Setuptools is replacing distutils.
>   warnings.warn("Setuptools is replacing distutils.")
> running build
> running build_py
> creating /<>/.pybuild/cpython3_3.10/build/ueberzug
> copying ueberzug/__init__.py -> 
> /<>/.pybuild/cpython3_3.10/build/ueberzug
> copying ueberzug/tmux_util.py -> 
> /<>/.pybuild/cpython3_3.10/build/ueberzug
> copying ueberzug/parser.py -> 
> /<>/.pybuild/cpython3_3.10/build/ueberzug
> copying ueberzug/conversion.py -> 
> /<>/.pybuild/cpython3_3.10/build/ueberzug
> copying ueberzug/__main__.py -> 
> /<>/.pybuild/cpython3_3.10/build/ueberzug
> copying ueberzug/action.py -> 
> /<>/.pybuild/cpython3_3.10/build/ueberzug
> copying ueberzug/ui.py -> 
> /<>/.pybuild/cpython3_3.10/build/ueberzug
> copying ueberzug/geometry.py -> 
> /<>/.pybuild/cpython3_3.10/build/ueberzug
> copying ueberzug/loading.py -> 
> /<>/.pybuild/cpython3_3.10/build/ueberzug
> copying ueberzug/xutil.py -> 
> /<>/.pybuild/cpython3_3.10/build/ueberzug
> copying ueberzug/files.py -> 
> /<>/.pybuild/cpython3_3.10/build/ueberzug
> copying ueberzug/process.py -> 
> /<>/.pybuild/cpython3_3.10/build/ueberzug
> copying ueberzug/pattern.py -> 
> /<>/.pybuild/cpython3_3.10/build/ueberzug
> copying ueberzug/batch.py -> 
> /<>/.pybuild/cpython3_3.10/build/ueberzug
> copying ueberzug/thread.py -> 
> /<>/.pybuild/cpython3_3.10/build/ueberzug
> copying ueberzug/query_windows.py -> 
> /<>/.pybuild/cpython3_3.10/build/ueberzug
> copying ueberzug/library.py -> 
> /<>/.pybuild/cpython3_3.10/build/ueberzug
> copying ueberzug/terminal.py -> 
> /<>/.pybuild/cpython3_3.10/build/ueberzug
> copying ueberzug/scaling.py -> 
> /<>/.pybuild/cpython3_3.10/build/ueberzug
> copying ueberzug/version.py -> 
> /<>/.pybuild/cpython3_3.10/build/ueberzug
> copying ueberzug/layer.py -> 
> /<>/.pybuild/cpython3_3.10/build/ueberzug
> creating /<>/.pybuild/cpython3_3.10/build/ueberzug/lib
> copying ueberzug/lib/__init__.py -> 
> /<>/.pybuild/cpython3_3.10/build/ueberzug/lib
> creating /<>/.pybuild/cpython3_3.10/build/ueberzug/lib/v0
> copying ueberzug/lib/v0/__init__.py -> 
> /<>/.pybuild/cpython3_3.10/build/ueberzug/lib/v0
> running egg_info
> creating ueberzug.egg-info
> writing ueberzug.egg-info/PKG-INFO
> writing dependency_links to ueberzug.egg-info/dependency_links.txt
> writing entry points to ueberzug.egg-info/entry_points.txt
> writing requirements to ueberzug.egg-info/requires.txt
> writing top-level names to ueberzug.egg-info/top_level.txt
> writing manifest file 'ueberzug.egg-info/SOURCES.txt'
> error: each element of 'ext_modules' option must be an Extension instance or 
> 2-tuple
> E: pybuild pybuild:379: build: plugin distutils failed with: exit code=1: 
> /usr/bin/python3 setup.py build 
> dh_auto_build: error: pybuild --build -i python{version} -p 3.10 returned 
> exit code 13
> make[1]: *** [debian/rules:19: override_dh_auto_build] Error 25


The full build log is available from:
http://qa-logs.debian.net/2022/09/17/ueberzug_18.1.9-2_unstable.log

All

Bug#1020619: libstdc++-arm-none-eabi-newlib: Fails to install because of incorrect versioned depency on gcc-arm-none-eabi

[Guus Sliepen]

Package: libstdc++-arm-none-eabi-newlib
Version: 15:10.3-2021.07-4+20
Severity: serious
Justification: Policy 2.2.1

This package depends on gcc-arm-none-eabi (= 15:10.3-2021.07-4), however
the latter version does not exist in main because there has been a
binNMU, so the version present is 15:10.3-2021.07-4+b1.


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

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

Versions of packages libstdc++-arm-none-eabi-newlib depends on:
ii  gcc-arm-none-eabi15:10.3-2021.07-4+b1
ii  libnewlib-arm-none-eabi  3.3.0-1.3
ii  libnewlib-dev3.3.0-1.3
pn  libstdc++-arm-none-eabi-dev  

Versions of packages libstdc++-arm-none-eabi-newlib recommends:
ii  binutils-arm-none-eabi  2.38.90.20220713-2+17
ii  gcc-arm-none-eabi   15:10.3-2021.07-4+b1

libstdc++-arm-none-eabi-newlib suggests no packages.

Processed: src:openlibm: fails to migrate to testing for too long: FTBFS on armhf and mips64el

[Debian Bug Tracking System]

Processing control commands:

> close -1 0.8.1+dfsg-2
Bug #1020617 [src:openlibm] src:openlibm: fails to migrate to testing for too 
long: FTBFS on armhf and mips64el
Marked as fixed in versions openlibm/0.8.1+dfsg-2.
Bug #1020617 [src:openlibm] src:openlibm: fails to migrate to testing for too 
long: FTBFS on armhf and mips64el
Marked Bug as done

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

Bug#1020617: src:openlibm: fails to migrate to testing for too long: FTBFS on armhf and mips64el

[Paul Gevers]

Source: openlibm
Version: 0.7.0+dfsg-2
Severity: serious
Control: close -1 0.8.1+dfsg-2
Tags: sid bookworm
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 60 days as having a Release Critical bug in 
testing [1]. Your package src:openlibm has been trying to migrate for 61 
days [2]. Hence, I am filing this bug. Your package failed to build from 
source on armhf and mips64el while it built successfully there before.


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 bookworm, 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/2020/02/msg5.html
[2] https://qa.debian.org/excuses.php?package=openlibm



OpenPGP_signature
Description: OpenPGP digital signature

Bug#1017313: postfix: FTBFS: unistd.h:363:13: error: conflicting types for ‘closefrom’; have ‘void(int)’

[Christian Göttsche]

control: tags -1 fixed-upstream

The issue is fixed upstream in version 3.6.5[1].

[1]: https://www.postfix.org/announcements/postfix-3.6.5.html

Processed: Re: Bug#1017313: postfix: FTBFS: unistd.h:363:13: error: conflicting types for ‘closefrom’; have ‘void(int)’

[Debian Bug Tracking System]

Processing control commands:

> tags -1 fixed-upstream
Bug #1017313 [src:postfix] postfix: FTBFS: unistd.h:363:13: error: conflicting 
types for ‘closefrom’; have ‘void(int)’
Added tag(s) fixed-upstream.

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

Processed: incorrect formatting in /usr/share/pari/pari.desc

[Debian Bug Tracking System]

Processing control commands:

> block 1020437 by -1
Bug #1020437 [src:clisp] clisp FTBFS with PARI 2.15.0
1020437 was not blocked by any bugs.
1020437 was not blocking any bugs.
Added blocking bug(s) of 1020437: 1020613

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

Bug#1020082: marked as done (scons: FTBFS: make: *** [debian/rules:10: binary] Error 25)

[Debian Bug Tracking System]

Your message dated Sat, 24 Sep 2022 07:50:48 +
with message-id 
and subject line Bug#1020082: fixed in scons 4.4.0+dfsg-1
has caused the Debian Bug report #1020082,
regarding scons: FTBFS: make: *** [debian/rules:10: binary] Error 25
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.)


-- 
1020082: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1020082
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: scons
Version: 4.0.1+dfsg-2
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20220917 ftbfs-bookworm

Hi,

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


Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> dh_installchangelogs CHANGES.txt
> make[1]: Leaving directory '/<>'
>dh_installman
>dh_python3
>dh_perl
>dh_usrlocal
> dh_usrlocal: error: debian/scons/usr/local/bin/scons is not a directory
> make: *** [debian/rules:10: binary] Error 25


The full build log is available from:
http://qa-logs.debian.net/2022/09/17/scons_4.0.1+dfsg-2_unstable.log

All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20220917;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na&merged=ign&fnewerval=7&flastmodval=7&fusertag=only&fusertagtag=ftbfs-20220917&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 to reproduce this, please provide a build log and diff it with mine
so that we can identify if something relevant changed in the meantime.
--- End Message ---
--- Begin Message ---
Source: scons
Source-Version: 4.4.0+dfsg-1
Done: Laszlo Boszormenyi (GCS) 

We believe that the bug you reported is fixed in the latest version of
scons, 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 1020...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Laszlo Boszormenyi (GCS)  (supplier of updated scons 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: Tue, 20 Sep 2022 17:35:41 +0200
Source: scons
Architecture: source
Version: 4.4.0+dfsg-1
Distribution: unstable
Urgency: medium
Maintainer: Laszlo Boszormenyi (GCS) 
Changed-By: Laszlo Boszormenyi (GCS) 
Closes: 973301 981584 1020082
Changes:
 scons (4.4.0+dfsg-1) unstable; urgency=medium
 .
   * New upstream release:
 - fix content-timestamp decider for symlinks (closes: #981584).
   * Move binaries back to /usr (closes: #1020082).
   * Handle man pages correctly.
   * Suggest scons-doc on scons package (closes: #973301).
   * Update Standards-Version to 4.6.1 .
Checksums-Sha1:
 0d57953ad3fd0fbf41e168a00bf873b5ddd4acbb 2051 scons_4.4.0+dfsg-1.dsc
 b3dc276fa364afa1595b922845eb868650c214d5 2994640 scons_4.4.0+dfsg.orig.tar.xz
 a8a869e060f2685168bee9c2d7bffdd457d91dcf 15552 scons_4.4.0+dfsg-1.debian.tar.xz
Checksums-Sha256:
 32e22db1553747f7ea84cf4a2c3bbb55f91e3298fb043e82ae2dee79028698a0 2051 
scons_4.4.0+dfsg-1.dsc
 a767c6ee2b6ffc08202f064ea5b94e2c2cfd4d35965cc434ff4ea959a9e1db91 2994640 
scons_4.4.0+dfsg.orig.tar.xz
 1c5cea75bbade4955512fd3382e86be5a1cc1122c686ada7b92538c9889b344f 15552 
scons_4.4.0+dfsg-1.debian.tar.xz
Files:
 ab095764d44c233cef77437398750bb1 2051 devel optional scons_4.4.0+dfsg-1.dsc
 c5435dac08f27587d274b7a4894889bb 2994640 devel optional 
scons_4.4.0+dfsg.orig.tar.xz
 41546fbfae892f8da450bd871d385fd1 15552 devel optional 
scons_4.4.0+dfsg-1.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEfYh9yLp7u6e4NeO63OMQ54ZMyL8FAmMusTkACgkQ3OMQ54ZM
yL/PEA/+M731dzrvDQ9ruSryP3mDnQgv6+GAqZGSs/PfhN+yExbS2MgM06KVTlGO
qvLh5cshlINTC4cjlfhH0qavzCHilMqq9VCoYysDwudSX3uESW4eaDPkQ0CwWzLx
0pXd/mbviW6NdrxxXeCTTLb4+lw9WzIOph7xpj+2BH0H+nThdtDTbaUEzRA3ycKu
kw2FCHPFEtW7++KL8WycuaAcVQICZ+peY3QJ+rlRLVmxv/7NK1axL86LGk7vPLFu
zu3hHgvkz1P781QpLIF3qEcjxw

Bug#1020009: marked as done (jupyter-server: FTBFS: ModuleNotFoundError: No module named 'setuptools')

[Debian Bug Tracking System]

Your message dated Sat, 24 Sep 2022 07:50:22 +
with message-id 
and subject line Bug#1020009: fixed in jupyter-server 1.18.1-2
has caused the Debian Bug report #1020009,
regarding jupyter-server: FTBFS: ModuleNotFoundError: No module named 
'setuptools'
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.)


-- 
1020009: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1020009
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: jupyter-server
Version: 1.18.1-1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20220917 ftbfs-bookworm

Hi,

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


Relevant part (hopefully):
>  debian/rules clean
> dh clean --with python3 --buildsystem=pybuild
>dh_auto_clean -O--buildsystem=pybuild
> I: pybuild base:240: python3.10 setup.py clean 
> Traceback (most recent call last):
>   File "/<>/setup.py", line 4, in 
> from setuptools import setup
> ModuleNotFoundError: No module named 'setuptools'
> E: pybuild pybuild:379: clean: plugin distutils failed with: exit code=1: 
> python3.10 setup.py clean 
> dh_auto_clean: error: pybuild --clean -i python{version} -p 3.10 returned 
> exit code 13
> make: *** [debian/rules:6: clean] Error 25


The full build log is available from:
http://qa-logs.debian.net/2022/09/17/jupyter-server_1.18.1-1_unstable.log

All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20220917;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na&merged=ign&fnewerval=7&flastmodval=7&fusertag=only&fusertagtag=ftbfs-20220917&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 to reproduce this, please provide a build log and diff it with mine
so that we can identify if something relevant changed in the meantime.
--- End Message ---
--- Begin Message ---
Source: jupyter-server
Source-Version: 1.18.1-2
Done: Julien Puydt 

We believe that the bug you reported is fixed in the latest version of
jupyter-server, 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 1020...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Julien Puydt  (supplier of updated jupyter-server 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: Sat, 24 Sep 2022 09:24:21 +0200
Source: jupyter-server
Architecture: source
Version: 1.18.1-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Team 
Changed-By: Julien Puydt 
Closes: 1020009
Changes:
 jupyter-server (1.18.1-2) unstable; urgency=medium
 .
   * Add missing b-dep on setuptools (Closes: #1020009).
Checksums-Sha1:
 3a703e62d507d58bd1a52491fdd98f0f46fa447f 2441 jupyter-server_1.18.1-2.dsc
 40dfc0824914665318fabfa90f51936b772d11df 4340 
jupyter-server_1.18.1-2.debian.tar.xz
 4777d6de69eacf6b04cfde83ad7c80ce82e92be0 9097 
jupyter-server_1.18.1-2_source.buildinfo
Checksums-Sha256:
 7739b1a879f53015fc3724bf9a2af97a67df84c4722d7fbfee284c948fbb83c6 2441 
jupyter-server_1.18.1-2.dsc
 346b685204878ad0c10f4b92d862b149986f9cec91e3998e66e823e296a23d7b 4340 
jupyter-server_1.18.1-2.debian.tar.xz
 5229d97510cbe2cfb31b49dd19b0c4d983bde32888c41ccc7d64bd0d1516cb8d 9097 
jupyter-server_1.18.1-2_source.buildinfo
Files:
 c3a5fb2087c879bb55c6a9d0a02fc955 2441 python optional 
jupyter-server_1.18.1-2.dsc
 d5e074918845b9d6091da2ddc39609e4 4340 python optional 
jupyter-server_1.18.1-2.debian.tar.xz
 04530f86fbbf3aab79cbd5411ac1161f 9097 python optional 
jupyter-server_1.18.1-2_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJGBAEBCgAwFiEEgS7v2KP7pKzk3xFLBMU71/4DBVEFAmMusM0SHGpwdXlkdEBk
ZWJpYW4ub3JnAAoJEATFO9f+AwVR/pwP/1uCQ03lUJ7QU8AQyqHgyJYpwzBmoDlB
gGqwV6/uROMkwA4AelSBDEUKHatWgZNWv4n04QEgy7F5geCQfAvJ9jw1z2XguBmW
ztIvXBFaVu0D1pHfMeNjN1xE61Y7T4WLo/3BTI

Bug#1015733: marked as done (ghc: ABI reproducibility broken in 9.0.2)

[Debian Bug Tracking System]

Your message dated Sat, 24 Sep 2022 07:50:11 +
with message-id 
and subject line Bug#1015733: fixed in ghc 9.0.2-4
has caused the Debian Bug report #1015733,
regarding ghc: ABI reproducibility broken in 9.0.2
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.)


-- 
1015733: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1015733
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: ghc
Version: 9.0.2-3
Severity: serious
Justification: Policy 4.15

Haskell ABI reproducibility is broken in ghc 9.0.2.  If you rebuild the
ghc-9.0.2-3 package repeatedly, the library packages that it provides (e.g.,
libghc-array-dev, libghc-base-dev, etc.) will have different hashes.

Making this RC because it makes it impossible to rebuild the ghc package
without rebuilding all 1000+ Haskell packages at the same time.
--- End Message ---
--- Begin Message ---
Source: ghc
Source-Version: 9.0.2-4
Done: Ilias Tsitsimpis 

We believe that the bug you reported is fixed in the latest version of
ghc, 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 1015...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Ilias Tsitsimpis  (supplier of updated ghc 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: Sat, 24 Sep 2022 10:06:11 +0300
Source: ghc
Architecture: source
Version: 9.0.2-4
Distribution: unstable
Urgency: medium
Maintainer: Debian Haskell Group 

Changed-By: Ilias Tsitsimpis 
Closes: 1015733
Changes:
 ghc (9.0.2-4) unstable; urgency=medium
 .
   * Backport patch to fix ABI reproducibility (Closes: #1015733)
Checksums-Sha1:
 fe98958f982b37c508332820da6b9146b867c1dc 2597 ghc_9.0.2-4.dsc
 4e0c1e3cdabdbc4b22ba6f741199e890da4d870f 56948 ghc_9.0.2-4.debian.tar.xz
 9bcdebdb84c4a8c06f5d21b5f33b48b24b842c29 12942 ghc_9.0.2-4_amd64.buildinfo
Checksums-Sha256:
 5e3d88fa1af515ca6015867315f54d9a72d9f0f48adc9993e2c8b0d8a37b68d8 2597 
ghc_9.0.2-4.dsc
 859e9069277a2f8554370398f5eacfb6a9f89c062969f7cd1d1df221351826b7 56948 
ghc_9.0.2-4.debian.tar.xz
 f2c42dbd64860d30067d3871247053920adca1c4e58841dc125cfc29810221ce 12942 
ghc_9.0.2-4_amd64.buildinfo
Files:
 ed9f87a53865666ceb33832c97a1de0f 2597 haskell optional ghc_9.0.2-4.dsc
 c2137b5c64a8941f79e2ea074f14b5f5 56948 haskell optional 
ghc_9.0.2-4.debian.tar.xz
 5e37ee3bcaf9ac92c86ece0e4bbe1446 12942 haskell optional 
ghc_9.0.2-4_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQJIBAEBCgAyFiEEJ9c8pfW11+AaUTb116hngMxkQDwFAmMutccUHGlsaWFzdHNp
QGRlYmlhbi5vcmcACgkQ16hngMxkQDxmVQ//Xb8PthqEsZSFQDf0hze3AVGFVtbz
h3LVGZCAqGzsw0d/1VJCUw8nI/bXLfaBKB95SzYHY6c5XlIVeHVcxDFRHBlKdTI0
zgogKYJhBMdCgWtCNq+evn6G6C/bm/AAXoipLA5pqwAvgOD7HgGrixm7NgGCzbH4
67wc880yTuOyCqCqiOdemP6Q8EuQF0/f18JQgmyRYAwHULFM4iHLAsn2RW+gLv/V
xahcVBykYgcLbj8NhyYrIhsx7u896o140LEwKxbowRcQRIuz6FJfUBMpBpsLWJge
ASFUSBRLnIFm1xTWraZ1EAt9CiJPuU+Ad0a1RleXWZq7ho7/wLNhLDdVRYyROGei
g8sU1WJbkIlEpENQZmv8oBGYPl4vuUPjI2mlyJyL3/dyhuROt01nE3T/y6bJ7Hd5
0muRzebGDhxecRNOtMR/UKjB8HrUb0zfJ2YOgaPQ4hAl+uHk4QXWFq0mqC8cR587
YSSHPcoYeCrhEUTRFGC5diCuqke+nVPmpOuemcvyAZEiCUbt+H8oyDMpXo+1I+9y
cGR21ABUKuihRPWaN5yjNIxjPGslTEsVjxVsDkhDIRaLwt8xYAG8QTotkP2Kabpq
D95kb8hsDN7dfRLNuto9I3yF85/IC5YJp53DeXcl9L3dKcnaskjhTwZImEs83fff
kHWwG5TqwjknWeM=
=6/XM
-END PGP SIGNATURE End Message ---

Bug#1020061: marked as done (mkdocs-material-extensions: FTBFS: ModuleNotFoundError: No module named 'setuptools')

[Debian Bug Tracking System]

Your message dated Sat, 24 Sep 2022 07:19:07 +
with message-id 
and subject line Bug#1020061: fixed in mkdocs-material-extensions 1.0.3-2
has caused the Debian Bug report #1020061,
regarding mkdocs-material-extensions: FTBFS: ModuleNotFoundError: No module 
named 'setuptools'
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.)


-- 
1020061: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1020061
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: mkdocs-material-extensions
Version: 1.0.3-1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20220917 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 --with python3 --buildsystem=pybuild
>dh_update_autotools_config -O--buildsystem=pybuild
>dh_autoreconf -O--buildsystem=pybuild
>dh_auto_configure -O--buildsystem=pybuild
>dh_auto_build -O--buildsystem=pybuild
> I: pybuild plugin_pyproject:107: Building wheel for python3.10 with "build" 
> module
> I: pybuild base:240: python3.10 -m build --skip-dependency-check 
> --no-isolation --wheel --outdir 
> /<>/.pybuild/cpython3_3.10_materialx 
> * Building wheel...
> 
> Traceback (most recent call last):
>   File "/usr/lib/python3/dist-packages/pep517/wrappers.py", line 332, in 
> _call_hook
> raise BackendUnavailable(data.get('traceback', ''))
> pep517.wrappers.BackendUnavailable: Traceback (most recent call last):
>   File "/usr/lib/python3/dist-packages/pep517/in_process/_in_process.py", 
> line 89, in _build_backend
> obj = import_module(mod_path)
>   File "/usr/lib/python3.10/importlib/__init__.py", line 126, in import_module
> return _bootstrap._gcd_import(name[level:], package, level)
>   File "", line 1050, in _gcd_import
>   File "", line 1027, in _find_and_load
>   File "", line 992, in _find_and_load_unlocked
>   File "", line 241, in _call_with_frames_removed
>   File "", line 1050, in _gcd_import
>   File "", line 1027, in _find_and_load
>   File "", line 1004, in _find_and_load_unlocked
> ModuleNotFoundError: No module named 'setuptools'
> 
> ERROR Backend 'setuptools.build_meta' is not available.
> E: pybuild pybuild:379: build: plugin pyproject failed with: exit code=1: 
> python3.10 -m build --skip-dependency-check --no-isolation --wheel --outdir 
> /<>/.pybuild/cpython3_3.10_materialx 
> dh_auto_build: error: pybuild --build -i python{version} -p 3.10 returned 
> exit code 13
> make: *** [debian/rules:13: binary] Error 25


The full build log is available from:
http://qa-logs.debian.net/2022/09/17/mkdocs-material-extensions_1.0.3-1_unstable.log

All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20220917;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na&merged=ign&fnewerval=7&flastmodval=7&fusertag=only&fusertagtag=ftbfs-20220917&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 to reproduce this, please provide a build log and diff it with mine
so that we can identify if something relevant changed in the meantime.
--- End Message ---
--- Begin Message ---
Source: mkdocs-material-extensions
Source-Version: 1.0.3-2
Done: Carsten Schoenert 

We believe that the bug you reported is fixed in the latest version of
mkdocs-material-extensions, 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 1020...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Carsten Schoenert  (supplier of updated 
mkdocs-material-extensions 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: Sat, 24 Sep 2022 09:00:00 +0200
Source: mkdocs-material-extensions
Architecture: source
Version: 1.0.3-2
Distribution: unstable
Urg