Bug#1037747: marked as done (libwebsockets: ftbfs with GCC-13)

[Debian Bug Tracking System]

Your message dated Sun, 23 Jul 2023 06:51:50 +
with message-id 
and subject line Bug#1037747: fixed in libwebsockets 4.3.2-2
has caused the Debian Bug report #1037747,
regarding libwebsockets: ftbfs with GCC-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.)


-- 
1037747: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1037747
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:libwebsockets
Version: 4.1.6-3
Severity: normal
Tags: sid trixie
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-13

[This bug is targeted to the upcoming trixie 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-13/g++-13, but succeeds to build with gcc-12/g++-12. The
severity of this report will be raised before the trixie release.

The full build log can be found at:
http://qa-logs.debian.net/2023/05/22/logs/libwebsockets_4.1.6-3_unstable_gccexp.log
The last lines of the build log are at the end of this report.

To build with GCC 13, either set CC=gcc-13 CXX=g++-13 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-13/porting_to.html

[...]
[ 26%] Building C object lib/CMakeFiles/websockets_shared.dir/tls/tls-client.c.o
cd /<>/obj-x86_64-linux-gnu/lib && /usr/bin/cc 
-Dwebsockets_shared_EXPORTS -I/<>/include 
-I/<>/obj-x86_64-linux-gnu -I/<>/lib 
-I/<>/lib/. -I/<>/lib/plat/unix/. 
-I/<>/lib/tls/. -I/<>/lib/core/. 
-I/<>/lib/misc/. -I/<>/lib/system/./async-dns 
-I/<>/lib/system/smd/. -I/<>/lib/core-net/. 
-I/<>/lib/roles/. -I/<>/lib/roles/http/. 
-I/<>/lib/roles/http/./compression 
-I/<>/lib/roles/h1/. -I/<>/lib/roles/h2/. 
-I/<>/lib/roles/ws/. -I/<>/lib/roles/raw-skt/. 
-I/<>/lib/roles/raw-file/. -I/<>/lib/roles/listen/. 
-I/<>/lib/event-libs/. 
-I/<>/lib/event-libs/poll/../poll 
-I/<>/lib/event-libs/libuv/. 
-I/<>/lib/event-libs/glib/. -I/usr/include/glib-2.0 
-I/usr/lib/x86_64-linux-gnu/glib-2.
 0/include -I/<>/lib/event-libs/libev/. -Wall -Wsign-compare 
-Wstrict-aliasing -fvisibility=hidden -Wundef  -Wuninitialized -Wtype-limits 
-Wignored-qualifiers -g -O2 -ffile-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security 
-Wno-error=deprecated-declarations -fno-strict-aliasing -Wdate-time 
-D_FORTIFY_SOURCE=2  -Werror -pthread -fPIC -MD -MT 
lib/CMakeFiles/websockets_shared.dir/tls/tls-client.c.o -MF 
CMakeFiles/websockets_shared.dir/tls/tls-client.c.o.d -o 
CMakeFiles/websockets_shared.dir/tls/tls-client.c.o -c 
/<>/lib/tls/tls-client.c
[ 26%] Building C object 
lib/CMakeFiles/websockets_shared.dir/tls/openssl/openssl-client.c.o
cd /<>/obj-x86_64-linux-gnu/lib && /usr/bin/cc 
-Dwebsockets_shared_EXPORTS -I/<>/include 
-I/<>/obj-x86_64-linux-gnu -I/<>/lib 
-I/<>/lib/. -I/<>/lib/plat/unix/. 
-I/<>/lib/tls/. -I/<>/lib/core/. 
-I/<>/lib/misc/. -I/<>/lib/system/./async-dns 
-I/<>/lib/system/smd/. -I/<>/lib/core-net/. 
-I/<>/lib/roles/. -I/<>/lib/roles/http/. 
-I/<>/lib/roles/http/./compression 
-I/<>/lib/roles/h1/. -I/<>/lib/roles/h2/. 
-I/<>/lib/roles/ws/. -I/<>/lib/roles/raw-skt/. 
-I/<>/lib/roles/raw-file/. -I/<>/lib/roles/listen/. 
-I/<>/lib/event-libs/. 
-I/<>/lib/event-libs/poll/../poll 
-I/<>/lib/event-libs/libuv/. 
-I/<>/lib/event-libs/glib/. -I/usr/include/glib-2.0 
-I/usr/lib/x86_64-linux-gnu/glib-2.
 0/include -I/<>/lib/event-libs/libev/. -Wall -Wsign-compare 
-Wstrict-aliasing -fvisibility=hidden -Wundef  -Wuninitialized -Wtype-limits 
-Wignored-qualifiers -g -O2 -ffile-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security 
-Wno-error=deprecated-declarations -fno-strict-aliasing -Wdate-time 
-D_FORTIFY_SOURCE=2  -Werror -pthread -fPIC -MD -MT 
lib/CMakeFiles/websockets_shared.dir/tls/openssl/openssl-client.c.o -MF 
CMakeFiles/websockets_shared.dir/tls/openssl/openssl-client.c.o.d -o 
CMakeFiles/websockets_shared.dir/tls/openssl/openssl-client.c.o -c 
/<>/lib/tls/openssl/openssl-client.c
make[3]: Leaving directory '/<>/obj-x86_64-linux-gnu'
make[2]: *** [CMakeFiles/Makefile2:1323: lib/CMakeFiles/websockets.dir/all] 
Error 2
make[2]: 

Bug#1041758: libcudf-dev is not installable due to bogus janitor change

[Adrian Bunk]

Package: libcudf-dev
Version: 0.10-1
Severity: serious
X-Debbugs-Cc: team+jani...@tracker.debian.org

The following packages have unmet dependencies:
 libcudf-dev : Depends: libtinfo6 (= 6.1+20181013-2+deb10u2) but 6.4+20230625-1 
is to be installed
   Depends: libncurses-dev (= 6.1+20181013-2+deb10u2) but 
6.4+20230625-1 is to be installed

This is due to:

https://salsa.debian.org/ocaml-team/cudf/-/merge_requests/2

cudf (0.10-1) unstable; urgency=medium
...
  [ Debian Janitor ]
...
   * Remove constraints unnecessary since buster (oldstable):
 + libcudf-dev: Replace dependency on transitional package libncurses5-dev
   with replacement libtinfo6 (= 6.1+20181013-2+deb10u2), libncurses-dev (=
   6.1+20181013-2+deb10u2) in Depends.
...


I haven't checked whether the replacement package names are correct,
but the = dependences hardcoded in debian/control are clearly wrong.

Bug#1038422: ntpsec: ntpd segmentation fault in libcrypto.so[7f6d3ecc5000+278000]

[Richard Laager]

Some questions from upstream, with my commentary added...


How busy is this sustem? Is it just a simple client or also a server? If 
server, how busy?

From the stack trace, the server side is trying to decode a NTS cookie. Is this 
box setup as a NTS server? That needs a certificate and key so it takes more 
than just upgrading from bullseye to bookworm.


It's not, right? We previously established that this is using the stock 
ntp.conf?



What are the chances that a valid NTP request with NTS arrived at this system? 
ntpq -c ntsinfo will show counters.


It would be good if you could check this. But if an NTS request is 
crashing ntpd, you might never see non-zero counters.



The log file from starting up might be helpful.

--
Richard

Bug#1037576: marked as done (android-platform-tools: ftbfs with GCC-13)

[Debian Bug Tracking System]

Your message dated Sun, 23 Jul 2023 05:05:17 +
with message-id 
and subject line Bug#1037576: fixed in android-platform-tools 33.0.3-2
has caused the Debian Bug report #1037576,
regarding android-platform-tools: ftbfs with GCC-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.)


-- 
1037576: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1037576
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:android-platform-tools
Version: 29.0.6-28
Severity: normal
Tags: sid trixie
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-13

[This bug is targeted to the upcoming trixie 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-13/g++-13, but succeeds to build with gcc-12/g++-12. The
severity of this report will be raised before the trixie release.

The full build log can be found at:
http://qa-logs.debian.net/2023/05/22/logs/android-platform-tools_29.0.6-28_unstable_gccexp.log
The last lines of the build log are at the end of this report.

To build with GCC 13, either set CC=gcc-13 CXX=g++-13 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-13/porting_to.html

[...]
# define _GLIBCXX11_DEPRECATED _GLIBCXX_DEPRECATED
   ^
/usr/bin/../lib/gcc/x86_64-linux-gnu/13/../../../../include/x86_64-linux-gnu/c++/13/bits/c++config.h:96:46:
 note: expanded from macro '_GLIBCXX_DEPRECATED'
# define _GLIBCXX_DEPRECATED __attribute__ ((__deprecated__))
 ^
system/core/liblog/event_tag_map.cpp:101:40: warning: 'unary_function &, unsigned long>' is deprecated 
[-Wdeprecated-declarations]
struct std::hash : public std::unary_function {
   ^
/usr/bin/../lib/gcc/x86_64-linux-gnu/13/../../../../include/c++/13/bits/stl_function.h:124:7:
 note: 'unary_function &, unsigned long>' 
has been explicitly marked deprecated here
} _GLIBCXX11_DEPRECATED;
  ^
/usr/bin/../lib/gcc/x86_64-linux-gnu/13/../../../../include/x86_64-linux-gnu/c++/13/bits/c++config.h:105:32:
 note: expanded from macro '_GLIBCXX11_DEPRECATED'
# define _GLIBCXX11_DEPRECATED _GLIBCXX_DEPRECATED
   ^
/usr/bin/../lib/gcc/x86_64-linux-gnu/13/../../../../include/x86_64-linux-gnu/c++/13/bits/c++config.h:96:46:
 note: expanded from macro '_GLIBCXX_DEPRECATED'
# define _GLIBCXX_DEPRECATED __attribute__ ((__deprecated__))
 ^
2 warnings generated.
mkdir -p debian/out/system/core
clang++ system/core/liblog/log_event_list.o 
system/core/liblog/log_event_write.o system/core/liblog/logger_name.o 
system/core/liblog/logger_read.o system/core/liblog/logger_write.o 
system/core/liblog/logprint.o system/core/liblog/properties.o 
system/core/liblog/event_tag_map.o -o debian/out/system/core/liblog.so.0 
-Wl,-z,relro -Wl,-z,now -fPIC -fuse-ld=lld -Wl,--build-id=sha1 
-Ldebian/out/system/core -Wl,-rpath=/usr/lib/x86_64-linux-gnu/android 
-Wl,-soname,liblog.so.0 -lpthread -shared
ln -sf liblog.so.0 debian/out/system/core/liblog.so
make[2]: Leaving directory '/<>'
dh_auto_build --buildsystem=makefile -- --file=debian/system/core/libbase.mk
make -j8 "INSTALL=install --strip-program=true" 
--file=debian/system/core/libbase.mk
make[2]: Entering directory '/<>'
clang++ -c -o system/core/base/abi_compatibility.o 
system/core/base/abi_compatibility.cpp -g -O2 
-ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -fPIC -gdwarf-4 -std=gnu++2a -Wdate-time 
-D_FORTIFY_SOURCE=2 -DNDEBUG -UDEBUG -fmessage-length=0 -fno-exceptions 
-fno-strict-aliasing -no-canonical-prefixes  -Wno-c99-designator 
-Wno-gnu-designator -Wno-gnu-folding-constant  -D_FILE_OFFSET_BITS=64 
-Isystem/core/base/include -Isystem/core/include 
clang++ -c -o system/core/base/chrono_utils.o system/core/base/chrono_utils.cpp 
-g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -fPIC -gdwarf-4 -std=gnu++2a -Wdate-time 
-D_FORTIFY_SOURCE=2 -

Bug#1041592: marked as done (bugs.debian.org: unattended-upgrades removed bind9 and other packages)

[Debian Bug Tracking System]

Your message dated Sat, 22 Jul 2023 21:45:41 -0700
with message-id <20230723044541.4w673zz63nvmh...@qor.donarmstrong.com>
and subject line Re: Bug#1041592: bugs.debian.org: unattended-upgrades removed 
bind9 and other packages
has caused the Debian Bug report #1041592,
regarding bugs.debian.org: unattended-upgrades removed bind9 and other packages
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.)


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

Dear Maintainer,

today I found DNS in my Network to be degraded.
I quickly figured out that the bind9 service was not running on this debain 
host. In fact the service was masked and the binary missing.

I installed the package via apt and everything worked again.
I found that unattended-upgrades remnoved bind9 and some other packages during 
its autoremove step.
That probably shouldn't happen however I am not sure if this was a bug in 
unattended-upgrades or the dependencies of some of the involved packages.

unattended-upgrade.log:

2023-07-21 06:17:23,880 INFO Starting unattended upgrades script
2023-07-21 06:17:23,881 INFO Allowed origins are: 
origin=Debian,codename=buster,label=Debian, 
origin=Debian,codename=buster,label=Debian-Security
2023-07-21 06:17:29,731 INFO Packages that will be upgraded: bind9 bind9-host 
bind9utils dnsutils libbind9-161 libdns-export1104 libdns1104 libirs-export161 
libirs161 libisc-export1100 libisc1100 libisccc161 libisccfg-export163 
libisccfg163 liblwres161
2023-07-21 06:17:29,732 INFO Writing dpkg log to 
/var/log/unattended-upgrades/unattended-upgrades-dpkg.log
2023-07-21 06:17:30,712 WARNING Keeping auto-removable libnss-mdns package(s) 
because it would also remove the following packages which should be kept in 
this step: bind9utils
2023-07-21 06:17:36,767 WARNING Keeping auto-removable liblwres161 package(s) 
because it would also remove the following packages which should be kept in 
this step: bind9utils libbind9-161 libdns1104 libisc1100 libisccc161 
libisccfg163
2023-07-21 06:17:45,067 WARNING Keeping auto-removable net-tools package(s) 
because it would also remove the following packages which should be kept in 
this step: bind9utils libbind9-161 libdns1104 libisc1100 libisccc161 
libisccfg163
2023-07-21 06:17:56,056 INFO Packages that were successfully auto-removed: 
avahi-daemon avahi-utils bind9 bind9-host dnsutils host libavahi-core7 
libdaemon0 libirs161 libnss-mdns
2023-07-21 06:17:56,057 INFO Packages that are kept back: liblwres161 
libnss-mdns net-tools


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

Kernel: Linux 4.19.0-24-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US:en (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
--- End Message ---
--- Begin Message ---

First, you filed this package against bugs.debian.org, which is for
issues with the bug tracking system itself, not generic issues with
Debian. Because this issue isn't actionable, I'm closing it. See below
for more information on what likely happened here.

On Fri, 21 Jul 2023, Marco Drummer wrote:
> That probably shouldn't happen however I am not sure if this was a bug
> in unattended-upgrades or the dependencies of some of the involved
> packages.

[...]

> unattended-upgrade.log:
> 
> 2023-07-21 06:17:23,880 INFO Starting unattended upgrades script

[...]

> 2023-07-21 06:17:56,056 INFO Packages that were successfully auto-removed: 
> avahi-daemon avahi-utils bind9 bind9-host dnsutils host libavahi-core7 
> libdaemon0 libirs161 libnss-mdns
> 2023-07-21 06:17:56,057 INFO Packages that are kept back: liblwres161 
> libnss-mdns net-tools

bind9 was removed because whatever you had that depended on it was
removed or you somehow marked it as being automatically installed.

Without seeing the complete details of what `apt show -a bind9` would
return, it's not possible to debug. [Also, you're running a Debian
release which is two stable releases behind.]

-- 
Don Armstrong  https://www.donarmstrong.com

Let the victors, when they come,
When the forts of folly fall
Find thy body by the wall!
 -- Matthew Arnold--- End Message ---

Bug#1040850: marked as done (python-coverage autopkg test fail with setuptools 68)

[Debian Bug Tracking System]

Your message dated Sun, 23 Jul 2023 04:49:41 +
with message-id 
and subject line Bug#1040850: fixed in python-coverage 7.2.7+dfsg1-1
has caused the Debian Bug report #1040850,
regarding python-coverage autopkg test fail with setuptools 68
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.)


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

Package: src:python-coverage
Version: 6.5.0+dfsg1-2
Severity: serious
Tags: sid trixie

see
https://ci.debian.net/data/autopkgtest/testing/amd64/p/python-coverage/35654868/log.gz

[...]
133s autopkgtest [23:40:57]:  summary
133s smoke-python3FAIL stderr: 
/tmp/autopkgtest-lxc.4ecm41xc/downtmp/build.Kvx/src/debian/tests/smoke_test.py:24: 
DeprecationWarning: pkg_resources is deprecated as an API. See 
https://setuptools.pypa.io/en/latest/pkg_resources.html
--- End Message ---
--- Begin Message ---
Source: python-coverage
Source-Version: 7.2.7+dfsg1-1
Done: Ben Finney 

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

Debian distribution maintenance software
pp.
Ben Finney  (supplier of updated python-coverage package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sun, 23 Jul 2023 13:49:58 +1000
Source: python-coverage
Architecture: source
Version: 7.2.7+dfsg1-1
Distribution: unstable
Urgency: medium
Maintainer: Ben Finney 
Changed-By: Ben Finney 
Closes: 1040850
Changes:
 python-coverage (7.2.7+dfsg1-1) unstable; urgency=medium
 .
   * The “Adele Puglisi” release.
   * Note that release 6.5.0+dfsg1-3 Closes: bug#1040850.
 The previous changelog entry gave the incorrect bug report number.
   * New upstream version.
 Highlights since previous release:
 * Changes to filename pattern matching and path remapping.
   These might require changing configuration for Coverage.py.
   See the “Migrating between versions” section of the documentation.
 * New output formats for ‘report’.
 * Empty source file no longer fails with ‘--fail-under’.
 * Filename parameters in API now also accept a ‘pathlib.Path’ object.
   * Refresh patches for new upstream version.
Checksums-Sha1:
 575b036419c90dadd921ff8457c35f170163b29a 2305 python-coverage_7.2.7+dfsg1-1.dsc
 5cde0aa7f6549d86a5e3b4a3264601834e3178b5 590940 
python-coverage_7.2.7+dfsg1.orig.tar.xz
 9a02e2dd3d9ba85f6679ceb535a1848effedb748 2 
python-coverage_7.2.7+dfsg1-1.debian.tar.xz
 77cda3110f83417f41cee1b24aaf9c45007a89b9 9650 
python-coverage_7.2.7+dfsg1-1_amd64.buildinfo
Checksums-Sha256:
 709c13073ac84efc97b044f9fb2bd4798a073e986667bd001db0e2da07b38ea4 2305 
python-coverage_7.2.7+dfsg1-1.dsc
 a24250e63947390a5cdb82ee0e5257c0d1907b41f1db7f562f8f2dcdf9920a2e 590940 
python-coverage_7.2.7+dfsg1.orig.tar.xz
 308fd614cb465a3d0dee07e58b9e02636137730203959de1946258ae62348226 2 
python-coverage_7.2.7+dfsg1-1.debian.tar.xz
 8e9767549895391a586cf2f641abb270cf8343f834fa455c83da17f8e1c97287 9650 
python-coverage_7.2.7+dfsg1-1_amd64.buildinfo
Files:
 9be230abce0a639e1fa5479276047e84 2305 python optional 
python-coverage_7.2.7+dfsg1-1.dsc
 c7c33b39fab35256298297b583dc808d 590940 python optional 
python-coverage_7.2.7+dfsg1.orig.tar.xz
 e64eb4d492f6e135fbb689218fd9c05d 2 python optional 
python-coverage_7.2.7+dfsg1-1.debian.tar.xz
 0d31053b4c0a1f2e77c0b6a742d7a252 9650 python optional 
python-coverage_7.2.7+dfsg1-1_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEYVng8p4vpBLgeVxz+bRqrIRCDIIFAmS8rkgACgkQ+bRqrIRC
DIKzQg/+MIfZTY9ZFRbL+lCrUZB0KfsXD2VdtdaXQ6HmPV+qfpNFSH/vv0OXA+zK
eVVBUm2NododMNSwjKOODYyvY/t4v9wW3HgfGmlMTb8cTdF8XhOu/GHy4JQMFF22
aOfhqe4j8otgOc1fvRBU2RavJ8MGSP9KacJ3ZqBO0YePUJ4ppDrBkijCmIrXuoO+
leH4N5O33TFlXOEAzPEkBuIPDQMc3REkGt8qWfDkV28hl0kGghcT3oemwbrgUkQE
rA7i1XhflcHnBAhKbUFVntLtKu3XKdVEUCcOTyWly3FjOzB0q15dUe+jZCx8X0eG
JfkJR/UNHWLsQ6TT9PkkKDb3CiCee51FhKAbDLEUwOCl9O93LQEbzvesURevsz0i
wp2JCA2JkvlqEFI9NcYdzz9uBX4GLQvbar6XLxiEClmEbLtjgazu/fLsI71xg2sk
s3oYUw4fLGutxlunrX+0QFY1E4D5dqrwi1ma/F

Processed: libxml-light-ocaml-dev: undeclared file conflict with libxml-light-ocaml (<= 2.4-1+b4) on /usr/lib/ocaml/xml-light/META

[Debian Bug Tracking System]

Processing control commands:

> affects -1 + libxml-light-ocaml
Bug #1041751 [libxml-light-ocaml-dev] libxml-light-ocaml-dev: undeclared file 
conflict with libxml-light-ocaml (<= 2.4-1+b4) on /usr/lib/ocaml/xml-light/META
Added indication that 1041751 affects libxml-light-ocaml

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

Bug#1041751: libxml-light-ocaml-dev: undeclared file conflict with libxml-light-ocaml (<= 2.4-1+b4) on /usr/lib/ocaml/xml-light/META

[Helmut Grohne]

Package: libxml-light-ocaml-dev
Version: 2.5-1
Severity: serious
Control: affects -1 + libxml-light-ocaml

libxml-light-ocaml-dev introduces an undeclared file conflict with
libxml-light-ocaml up to version 2.4-1+b4 on the file
/lib/ocaml/xml-light/META. This may result in an unpack error at package
extraction time. Do you miss Breaks + Replaces here?

Helmut

Bug#1037575: marked as done (android-platform-external-boringssl: ftbfs with GCC-13)

[Debian Bug Tracking System]

Your message dated Sun, 23 Jul 2023 04:19:05 +
with message-id 
and subject line Bug#1037575: fixed in android-platform-external-boringssl 
13.0.0+r24-3
has caused the Debian Bug report #1037575,
regarding android-platform-external-boringssl: ftbfs with GCC-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.)


-- 
1037575: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1037575
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:android-platform-external-boringssl
Version: 13.0.0+r24-2
Severity: normal
Tags: sid trixie
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-13

[This bug is targeted to the upcoming trixie 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-13/g++-13, but succeeds to build with gcc-12/g++-12. The
severity of this report will be raised before the trixie release.

The full build log can be found at:
http://qa-logs.debian.net/2023/05/22/logs/android-platform-external-boringssl_13.0.0+r24-2_unstable_gccexp.log
The last lines of the build log are at the end of this report.

To build with GCC 13, either set CC=gcc-13 CXX=g++-13 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-13/porting_to.html

[...]
clang++ -c -o src/crypto/blake2/blake2_test.o src/crypto/blake2/blake2_test.cc 
-g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -fPIC -gdwarf-4 -std=gnu++2a -Wdate-time 
-D_FORTIFY_SOURCE=2 -DNDEBUG -UDEBUG -DBORINGSSL_ANDROID_SYSTEM 
-DBORINGSSL_IMPLEMENTATION -DBORINGSSL_SHARED_LIBRARY -DOPENSSL_SMALL 
-fmessage-length=0 -fno-exceptions -fno-strict-aliasing -no-canonical-prefixes  
-Isrc/include 
clang++ -c -o src/crypto/buf/buf_test.o src/crypto/buf/buf_test.cc -g -O2 
-ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -fPIC -gdwarf-4 -std=gnu++2a -Wdate-time 
-D_FORTIFY_SOURCE=2 -DNDEBUG -UDEBUG -DBORINGSSL_ANDROID_SYSTEM 
-DBORINGSSL_IMPLEMENTATION -DBORINGSSL_SHARED_LIBRARY -DOPENSSL_SMALL 
-fmessage-length=0 -fno-exceptions -fno-strict-aliasing -no-canonical-prefixes  
-Isrc/include 
clang++ -c -o src/crypto/bytestring/bytestring_test.o 
src/crypto/bytestring/bytestring_test.cc -g -O2 
-ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -fPIC -gdwarf-4 -std=gnu++2a -Wdate-time 
-D_FORTIFY_SOURCE=2 -DNDEBUG -UDEBUG -DBORINGSSL_ANDROID_SYSTEM 
-DBORINGSSL_IMPLEMENTATION -DBORINGSSL_SHARED_LIBRARY -DOPENSSL_SMALL 
-fmessage-length=0 -fno-exceptions -fno-strict-aliasing -no-canonical-prefixes  
-Isrc/include 
clang++ -c -o src/crypto/chacha/chacha_test.o src/crypto/chacha/chacha_test.cc 
-g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -fPIC -gdwarf-4 -std=gnu++2a -Wdate-time 
-D_FORTIFY_SOURCE=2 -DNDEBUG -UDEBUG -DBORINGSSL_ANDROID_SYSTEM 
-DBORINGSSL_IMPLEMENTATION -DBORINGSSL_SHARED_LIBRARY -DOPENSSL_SMALL 
-fmessage-length=0 -fno-exceptions -fno-strict-aliasing -no-canonical-prefixes  
-Isrc/include 
clang++ -c -o src/crypto/cipher_extra/aead_test.o 
src/crypto/cipher_extra/aead_test.cc -g -O2 
-ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -fPIC -gdwarf-4 -std=gnu++2a -Wdate-time 
-D_FORTIFY_SOURCE=2 -DNDEBUG -UDEBUG -DBORINGSSL_ANDROID_SYSTEM 
-DBORINGSSL_IMPLEMENTATION -DBORINGSSL_SHARED_LIBRARY -DOPENSSL_SMALL 
-fmessage-length=0 -fno-exceptions -fno-strict-aliasing -no-canonical-prefixes  
-Isrc/include 
clang++ -c -o src/crypto/cipher_extra/cipher_test.o 
src/crypto/cipher_extra/cipher_test.cc -g -O2 
-ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -fPIC -gdwarf-4 -std=gnu++2a -Wdate-time 
-D_FORTIFY_SOURCE=2 -DNDEBUG -UDEBUG -DBORINGSSL_ANDROID_SYSTEM 
-DBORINGSSL_IMPLEMENTATION -DBORINGSSL_SHARED_LIBRARY -DOPENSSL_SMALL 
-fmessage-length=0 -fno-exceptions -fno-strict-aliasing -no-canonical-prefixes  
-Isrc/include 
clang++ -c -o src/crypto/conf/conf_test.o src/crypto/conf/conf_test.cc -g -O2 
-ffile-prefix-map=/<>=. -

Processed: tagging 1037568

[Debian Bug Tracking System]

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

> tags 1037568 + experimental
Bug #1037568 [src:actor-framework] actor-framework: ftbfs with GCC-13
Added tag(s) experimental.
> thanks
Stopping processing here.

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

Processed: found 1037568 in 0.18.6-1

[Debian Bug Tracking System]

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

> found 1037568 0.18.6-1
Bug #1037568 [src:actor-framework] actor-framework: ftbfs with GCC-13
Marked as found in versions actor-framework/0.18.6-1.
> thanks
Stopping processing here.

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

Bug#1038603: libisl23 0.25-1: amd64/i386 baseline violation: uses BMI instructions)

[Roman Lebedev]

Package: libisl23
Followup-For: Bug #1038603
X-Debbugs-Cc: Debian GCC Maintainers , 
debian-rele...@lists.debian.org

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

While the issue has been resolved in isl 0.26-3,
which was uploaded to unstable on 2023-06-19,
nothing has been done for the stable release,
and Debian 12.1 still comes with a "miscompiled" isl 0.25-1,
and thus gcc is still somewhat unusable(*) on older hardware(**)

This occasionally manifests as spurious failures
on e.g. https://build.opensuse.org/

* As long as no graphite optimizations are enabled it's perfectly usable.
** Older than the one on which it was built,
   roughly anything pre-Ryzen / pre-Haswell.

Roman.

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

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

Versions of packages libisl23 depends on:
ii  libc6 2.37-6
ii  libgmp10  2:6.2.1+dfsg1-1.1

libisl23 recommends no packages.

libisl23 suggests no packages.

- -- no debconf information

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEE+UikBxeiu50LOdFYgbqkFMWfZdAFAmS8Z4MACgkQgbqkFMWf
ZdA8tQ/8DU/KIBQIMCSGOOGioxM8Bo/bHpUjMiurfKJsTKu26qaR5puhsvNUCGoE
PzyJYZFJgHeGNi0/vbbGVIbu4+1NcfaWngwEVynJj2vK7Naf2fm2FYVzRoYA4obD
KpLz9viwdkjdp10Dgstvike8RYGw3g5MOD56Qk6ct6kaI3yiOciyTxzRTHU6csN2
WMCEzdSUI9T530NeXOyTZriYS17WathHqQHgugnQUbrEJsGoe7OYMHqOfC01F2Gr
+VmElssLIp669+VHADPyFgSdwbcgSjpXCHN2+qfC2s4MrIsPfdZzL2XrF2Qz5AJY
wAknMa0dV7YVSI5c8nAje77cAvGkGxuEXu9eN61B4KuzBjRih9trAQS9J3Zucq2g
VSCVYcquDsttGRDV5Nblb2X+iTFP37LNNnCl72QM35lnQneMHW3B8Ggw8vdl8ysq
1rsERMHjGVivdczQO2QeM4e+joSHw8ExjbBeHr7E1HV3rqcm/XpUoieZodBT0KuX
gszv6a3dLD1n4WfuleYNsEeWJl/rZnHsdOo6JXOTyR2jesDMV6uxxWzz8eR2Un4H
k6mrSi4S6Ysf6KyJ3rT7DwSb9VBRIO/z+yRykUrUyrSiLD2U/WyXVfnZQNQANtFm
V3GQTQM3I48IydJUHuzjtxGdTDIGDhZ6Z5SLqvNGyIV6QpYeIO4=
=2jT8
-END PGP SIGNATURE-

Bug#1041738: src:lme4: fails to migrate to testing for too long: causes timeout in autopkgtests on i386

[Dirk Eddelbuettel]

On 22 July 2023 at 21:45, Paul Gevers wrote:
| Source: lme4
| Version: 1.1-31-1
| Severity: serious
| Control: close -1 1.1-34-1
| X-Debbugs-CC: debia...@lists.debian.org
| Tags: sid trixie
| User: release.debian@packages.debian.org
| Usertags: out-of-sync
| 
| Dear maintainer(s),
| 
| The Release Team considers packages that are out-of-sync between testing 
| and unstable for more than 30 days as having a Release Critical bug in 
| testing [1]. Your package src:lme4 has been trying to migrate for 32 
| days [2]. Hence, I am filing this bug.
| 
| The version in unstable causes 3 autopkgtest failures when tested in 
| testing, all on i386. The failures are due to autopkgtest timeout after 
| 2:47 h, while normally these tests run in minutes, so this suggests the 
| tests hang. In unstable, r-cran-afex and r-cran-mertools pass (so this 
| is probably a (set of) package(s) in unstable that also needs to migrate 
| together with lme4), but r-cran-mlmrev also times out in unstable.
| 
| If a package is out of sync between unstable and testing for a longer 
| period, this usually means that bugs in the package in testing cannot be 
| fixed via unstable. Additionally, blocked packages can have impact on 
| other packages, which makes preparing for the release more difficult. 
| Finally, it often exposes issues with the package and/or
| its (reverse-)dependencies. We expect maintainers to fix issues that 
| hamper the migration of their package in a timely manner.
| 
| This bug will trigger auto-removal when appropriate. As with all new 
| bugs, there will be at least 30 days before the package is auto-removed.
| 
| I have immediately closed this bug with the version in unstable, so if 
| that version or a later version migrates, this bug will no longer affect 
| testing. I have also tagged this bug to only affect sid and trixie, so 
| it doesn't affect (old-)stable.
| 
| If you believe your package is unable to migrate to testing due to 
| issues beyond your control, don't hesitate to contact the Release Team.

The lme4 package is in fine standing at CRAN
  https://cloud.r-project.org/web/checks/check_results_lme4.html
and build everywhere on Debian (see this and other links)
  https://cloud.r-project.org/web/checks/check_results_lme4.html

If three other packages (that I have nothing to do with) fail in _their
autopkgtests_ may I suggest you talk to the maintainers of _those packages_?

lme4 is _core_ package, written and maintained by current and former R Core
members. It is one of the most widely used and watched packages around.

This is most likely an issue of shooting the messenger as the root cause with
be with those other packages.  It could be an issue as simple as CRAN (and
upstream) no longer checking on i386 though it usually does not fail there.

Dirk


| Paul
| 
| [1] https://lists.debian.org/debian-devel-announce/2023/06/msg1.html
| [2] https://qa.debian.org/excuses.php?package=lme4
| x[DELETED ATTACHMENT OpenPGP_signature, application/pgp-signature]

-- 
dirk.eddelbuettel.com | @eddelbuettel | e...@debian.org

Bug#1037827: marked as done (qscintilla2: ftbfs with GCC-13)

[Debian Bug Tracking System]

Your message dated Sat, 22 Jul 2023 20:56:25 +
with message-id 
and subject line Bug#1037827: fixed in qscintilla2 2.14.1+dfsg-1
has caused the Debian Bug report #1037827,
regarding qscintilla2: ftbfs with GCC-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.)


-- 
1037827: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1037827
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:qscintilla2
Version: 2.13.3+dfsg-3
Severity: normal
Tags: sid trixie
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-13

[This bug is targeted to the upcoming trixie 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-13/g++-13, but succeeds to build with gcc-12/g++-12. The
severity of this report will be raised before the trixie release.

The full build log can be found at:
http://qa-logs.debian.net/2023/05/22/logs/qscintilla2_2.13.3+dfsg-3_unstable_gccexp.log
The last lines of the build log are at the end of this report.

To build with GCC 13, either set CC=gcc-13 CXX=g++-13 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-13/porting_to.html

[...]
  
(optional=templinst)_ZNSt8__detail9_CompilerINSt7__cxx1112regex_traitsIwEEE18_M_expression_termILb0ELb0EEEbRNS4_13_BracketStateERNS_15_BracketMatcherIS3_XT_EXT0_EEE@Base
 2.13.3
  
(optional=templinst)_ZNSt8__detail9_CompilerINSt7__cxx1112regex_traitsIwEEE18_M_expression_termILb0ELb1EEEbRNS4_13_BracketStateERNS_15_BracketMatcherIS3_XT_EXT0_EEE@Base
 2.13.3
  
(optional=templinst)_ZNSt8__detail9_CompilerINSt7__cxx1112regex_traitsIwEEE18_M_expression_termILb1ELb0EEEbRNS4_13_BracketStateERNS_15_BracketMatcherIS3_XT_EXT0_EEE@Base
 2.13.3
@@ -1743,7 +1744,7 @@
  
(optional=templinst)_ZNSt8__detail9_StateSeqINSt7__cxx1112regex_traitsIwEEE8_M_cloneEv@Base
 2.13.3
  
(optional=templinst)_ZSt13binary_searchIN9__gnu_cxx17__normal_iteratorIPKcSt6vectorIcSaIccEbT_S8_RKT0_@Base
 2.13.3
  
(optional=templinst)_ZSt13binary_searchIN9__gnu_cxx17__normal_iteratorIPKwSt6vectorIwSaIwwEbT_S8_RKT0_@Base
 2.13.3
- _ZSt19piecewise_construct@Base 2.13.3
+#MISSING: 2.13.3+dfsg-3# _ZSt19piecewise_construct@Base 2.13.3
  _ZTI10QsciLexerD@Base 2.13.3
  _ZTI11QsciLexerPO@Base 2.13.3
  _ZTI11QsciPrinter@Base 2.13.3
@@ -1976,26 +1977,26 @@
  (optional=templinst|arch=!armel 
!riscv64)_ZTVSt23_Sp_counted_ptr_inplaceINSt8__detail4_NFAINSt7__cxx1112regex_traitsIcSaIvELN9__gnu_cxx12_Lock_policyE2EE@Base
 2.13.3
  (arch=armel 
riscv64)_ZTVSt23_Sp_counted_ptr_inplaceINSt8__detail4_NFAINSt7__cxx1112regex_traitsIwSaIvELN9__gnu_cxx12_Lock_policyE1EE@Base
 2.13.3
  (optional=templinst|arch=!armel 
!riscv64)_ZTVSt23_Sp_counted_ptr_inplaceINSt8__detail4_NFAINSt7__cxx1112regex_traitsIwSaIvELN9__gnu_cxx12_Lock_policyE2EE@Base
 2.13.3
- 
(optional=templinst)_ZZN9QtPrivate16QMetaTypeForTypeI4QUrlE10getCopyCtrEvENUlPKNS_18QMetaTypeInterfaceEPvPKvE_4_FUNES5_S6_S8_@Base
 2.13.3
- 
(optional=templinst)_ZZN9QtPrivate16QMetaTypeForTypeI4QUrlE10getMoveCtrEvENUlPKNS_18QMetaTypeInterfaceEPvS6_E_4_FUNES5_S6_S6_@Base
 2.13.3
- 
(optional=templinst)_ZZN9QtPrivate16QMetaTypeForTypeI4QUrlE13getDefaultCtrEvENUlPKNS_18QMetaTypeInterfaceEPvE_4_FUNES5_S6_@Base
 2.13.3
- 
(optional=templinst)_ZZN9QtPrivate16QMetaTypeForTypeI4QUrlE7getDtorEvENUlPKNS_18QMetaTypeInterfaceEPvE_4_FUNES5_S6_@Base
 2.13.3
- 
(optional=templinst)_ZZN9QtPrivate16QMetaTypeForTypeI7QStringE10getCopyCtrEvENUlPKNS_18QMetaTypeInterfaceEPvPKvE_4_FUNES5_S6_S8_@Base
 2.13.3
- 
(optional=templinst)_ZZN9QtPrivate16QMetaTypeForTypeI7QStringE10getMoveCtrEvENUlPKNS_18QMetaTypeInterfaceEPvS6_E_4_FUNES5_S6_S6_@Base
 2.13.3
- 
(optional=templinst)_ZZN9QtPrivate16QMetaTypeForTypeI7QStringE13getDefaultCtrEvENUlPKNS_18QMetaTypeInterfaceEPvE_4_FUNES5_S6_@Base
 2.13.3
- 
(optional=templinst)_ZZN9QtPrivate16QMetaTypeForTypeI7QStringE7getDtorEvENUlPKNS_18QMetaTypeInterfaceEPvE_4_FUNES5_S6_@Base
 2.13.3
- 
(optional=templinst)_ZZN9QtPrivate16QMetaTypeForTypeIbE10getCopyCtrEvENUlPKNS_18QMetaTypeInterfaceEPvPKvE_4_FUNES4_S5_S7_@Base

Processed: Bug#1041341 marked as pending in html5lib

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1041341 [src:html5lib] html5lib: FTBFS on unstable
Added tag(s) pending.

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

Bug#1041341: marked as pending in html5lib

[Timo Röhling]

Control: tag -1 pending

Hello,

Bug #1041341 in html5lib reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:

https://salsa.debian.org/python-team/packages/html5lib/-/commit/94f8d19c81da2e18854fa335b72243ae031e278d


Fix FTBFS with pytest 7.4

Closes: #1041341


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1041341

Processed: Re: Bug#1038422: ntpsec: ntpd segmentation fault in libcrypto.so[7f6d3ecc5000+278000]

[Debian Bug Tracking System]

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

> forwarded 1038422 https://gitlab.com/NTPsec/ntpsec/-/issues/794
Bug #1038422 [ntpsec] ntpsec: ntpd segmentation fault in 
libcrypto.so[7f6d3ecc5000+278000]
Set Bug forwarded-to-address to 'https://gitlab.com/NTPsec/ntpsec/-/issues/794'.
>
End of message, stopping processing here.

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

Bug#1041738: src:lme4: fails to migrate to testing for too long: causes timeout in autopkgtests on i386

[Paul Gevers]

Source: lme4
Version: 1.1-31-1
Severity: serious
Control: close -1 1.1-34-1
X-Debbugs-CC: debia...@lists.debian.org
Tags: sid trixie
User: release.debian@packages.debian.org
Usertags: out-of-sync

Dear maintainer(s),

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


The version in unstable causes 3 autopkgtest failures when tested in 
testing, all on i386. The failures are due to autopkgtest timeout after 
2:47 h, while normally these tests run in minutes, so this suggests the 
tests hang. In unstable, r-cran-afex and r-cran-mertools pass (so this 
is probably a (set of) package(s) in unstable that also needs to migrate 
together with lme4), but r-cran-mlmrev also times out in unstable.


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


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


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


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


Paul

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


OpenPGP_signature
Description: OpenPGP digital signature

Processed: src:lme4: fails to migrate to testing for too long: causes timeout in autopkgtests on i386

[Debian Bug Tracking System]

Processing control commands:

> close -1 1.1-34-1
Bug #1041738 [src:lme4] src:lme4: fails to migrate to testing for too long: 
causes timeout in autopkgtests on i386
Marked as fixed in versions lme4/1.1-34-1.
Bug #1041738 [src:lme4] src:lme4: fails to migrate to testing for too long: 
causes timeout in autopkgtests on i386
Marked Bug as done

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

Bug#1041388: marked as done (libclang-rt-17-dev: ships /usr/lib/llvm-17/lib/clang/17/lib/wasi/libclang_rt.builtins-wasm*.a, already in libclang-rt-17-dev-wasm*)

[Debian Bug Tracking System]

Your message dated Sat, 22 Jul 2023 19:43:31 +
with message-id 
and subject line Bug#1041388: fixed in llvm-toolchain-snapshot 
1:17~++20230721092305+2ce662c5d596-1~exp1
has caused the Debian Bug report #1041388,
regarding libclang-rt-17-dev: ships 
/usr/lib/llvm-17/lib/clang/17/lib/wasi/libclang_rt.builtins-wasm*.a, already in 
libclang-rt-17-dev-wasm*
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.)


-- 
1041388: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1041388
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libclang-rt-17-dev
Version: 1:17~++20230709044550+c54ff51be9c1-1~exp1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package failed to install
because it tries to overwrite other packages files.

>From the attached log (scroll to the bottom...):

  Selecting previously unselected package libclang-rt-17-dev:amd64.
  Preparing to unpack 
.../libclang-rt-17-dev_1%3a17~++20230709044550+c54ff51be9c1-1~exp1_amd64.deb ...
  Unpacking libclang-rt-17-dev:amd64 
(1:17~++20230709044550+c54ff51be9c1-1~exp1) ...
  dpkg: error processing archive 
/var/cache/apt/archives/libclang-rt-17-dev_1%3a17~++20230709044550+c54ff51be9c1-1~exp1_amd64.deb
 (--unpack):
   trying to overwrite 
'/usr/lib/llvm-17/lib/clang/17/lib/wasi/libclang_rt.builtins-wasm64.a', which 
is also in package libclang-rt-17-dev-wasm64 
1:17~++20230709044550+c54ff51be9c1-1~exp1
  Errors were encountered while processing:
   
/var/cache/apt/archives/libclang-rt-17-dev_1%3a17~++20230709044550+c54ff51be9c1-1~exp1_amd64.deb

  Selecting previously unselected package libclang-rt-17-dev:amd64.
  Preparing to unpack 
.../libclang-rt-17-dev_1%3a17~++20230709044550+c54ff51be9c1-1~exp1_amd64.deb ...
  Unpacking libclang-rt-17-dev:amd64 
(1:17~++20230709044550+c54ff51be9c1-1~exp1) ...
  dpkg: error processing archive 
/var/cache/apt/archives/libclang-rt-17-dev_1%3a17~++20230709044550+c54ff51be9c1-1~exp1_amd64.deb
 (--unpack):
   trying to overwrite 
'/usr/lib/llvm-17/lib/clang/17/lib/wasi/libclang_rt.builtins-wasm32.a', which 
is also in package libclang-rt-17-dev-wasm32 
1:17~++20230709044550+c54ff51be9c1-1~exp1
  Errors were encountered while processing:
   
/var/cache/apt/archives/libclang-rt-17-dev_1%3a17~++20230709044550+c54ff51be9c1-1~exp1_amd64.deb


cheers,

Andreas


libclang-rt-17-dev-wasm64=1:17~++20230709044550+c54ff51be9c1-1~exp1_libclang-rt-17-dev=1:17~++20230709044550+c54ff51be9c1-1~exp1.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: llvm-toolchain-snapshot
Source-Version: 1:17~++20230721092305+2ce662c5d596-1~exp1
Done: Sylvestre Ledru 

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

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

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

Debian distribution maintenance software
pp.
Sylvestre Ledru  (supplier of updated 
llvm-toolchain-snapshot package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Fri, 21 Jul 2023 09:26:43 +0200
Source: llvm-toolchain-snapshot
Architecture: source
Version: 1:17~++20230721092305+2ce662c5d596-1~exp1
Distribution: experimental
Urgency: medium
Maintainer: LLVM Packaging Team 
Changed-By: Sylvestre Ledru 
Closes: 1041388
Changes:
 llvm-toolchain-snapshot (1:17~++20230721092305+2ce662c5d596-1~exp1) 
experimental; urgency=medium
 .
   * New snapshot release:
   * Fix the libclang-rt-17-dev: ships
 /usr/lib[...]/wasi/libclang_rt.builtins-wasm*.a, already in
 libclang-rt-17-dev-wasm* (closes: #1041388)
   * Also install llvm-debuginfod in llvm-X.Y
Checksums-Sha1:
 2abe3df9cf360ce797c1095836c93601abbcb34c 8345 
llvm-toolchain-snapshot_17~++20230721092305+2ce662c5d596-1~exp1.dsc
 917c1c5fa8d407a8567ac183388e189384e7eda8 148530988 
llvm-toolchain-snapshot_17~++20230721092305+2ce662c5d596.orig.tar.xz
 e3d0fef08b40f6d40bbdcc1f8ba08acf01c649ef 165148 
llvm-toolchain-snapshot_17~++20230721092305+2ce662c5d596-1~exp1.debian.tar.xz
 f18364832b358081dbea07903bacfbebc9405df3 41863 
llvm-toolchain-snapshot_17~++20230721092305+2ce662c5d596-1~e

Bug#932501: [pkg-apparmor] BTS housekeeping and severity adjustments

[Christian Boltz]

Hello,

Am Freitag, 21. Juli 2023, 15:05:52 CEST schrieb Stefano Rivera:
> > severity 932501 serious
> 
> I'm wondering if this bug should really be serious. Squid's apparmor
> config is shipped disabled, so one has to manually enable it to
> trigger this bug.
> 
> I would have gone for normal/important.
> 
> I don't know what the correct solution to this bug is. Presumably one
> has to get the squid profile to include the abstraction that
> squid-deb-proxy provides. I don't know how this is usually done in a
> Debian package. Maybe one of the apparmor team can comment.

The interesting part is that the abstraction is shipped in squid-deb-
proxy, while the squid profile comes from another package (I didn't check 
which one).

I guess the best you can have is to add
include if exists 
in the squid profile so that it will include the abstraction if it 
exists, and doesn't complain if it doesn't.

Note that the AppArmor profile cache is only timestamp-based [1], so if 
you install squid-deb-proxy (and had the squid AppArmor profile loaded 
before), it might happen that the cache file is never than the squid-deb-
proxy abstraction, with the result that the cache doesn't get updated.
(Workaround: delete the cache file, then reload the profile.)


The alternative is to add the rules needed for squid-deb-proxy directly 
to the squid profile. This adds some "superfluous" rules for people who 
don't use squid-deb-proxy, but on the positive side it avoids the cache 
issue.


BTW: https://packages.debian.org/sid/all/squid-deb-proxy/filelist says 
the abstraction is packaged as
/etc/apparmor.d/abstractions/squid-deb-proxy/squid-deb-proxy
which looks slightly wrong ;-)  It should just be
/etc/apparmor.d/abstractions/squid-deb-proxy
(assuming no other files get deployed to
/etc/apparmor.d/abstractions/squid-deb-proxy/ )

Bonus points if you add
include if exists 
to the abstraction ;-)


For the records:   include if exists   needs AppArmor >= 3.0 userspace.


Regards,

Christian Boltz

[1] Using a better cache validation method like checking the checksum of 
the text profile is on the TODO list upstream, but not implemented 
yet.
-- 
[SuSE vs. SUSE] As a friend of mine elsewhere remarked, the picky
spelling capitalization scheme reinforces the idea that Linux is
case-sensitive, so these are "sensitive" issues and certainly worth
discussing (for us, at least)! :)   [Shriramana Sharma in opensuse]


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

Processed: reopen #1037603 closed by error

[Debian Bug Tracking System]

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

> reopen 1037603
Bug #1037603 {Done: Sebastien Jodogne } [src:civetweb] 
civetweb: ftbfs with GCC-13
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
No longer marked as fixed in versions orthanc-postgresql/5.0+dfsg-1.
> --
Stopping processing here.

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

Bug#999977: qxw: depends on obsolete pcre3 library

[Stephen Kitt]

On Sat, 22 Jul 2023 16:14:06 +0200, Bastian Germann  wrote:
> I suggest to remove the package. I do not think upstream will deal with 
> this.

qxw’s usage of pcre seems simple enough, I’ll try to come up with a patch.

Regards,

Stephen


pgpJ5rnX7z89K.pgp
Description: OpenPGP digital signature

Processed: bug 1041722 is forwarded to https://github.com/ValveSoftware/steam-for-linux/issues/9805

[Debian Bug Tracking System]

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

> forwarded 1041722 https://github.com/ValveSoftware/steam-for-linux/issues/9805
Bug #1041722 [steam-installer] steam is incompatible with libgudev 238-2
Set Bug forwarded-to-address to 
'https://github.com/ValveSoftware/steam-for-linux/issues/9805'.
> thanks
Stopping processing here.

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

Bug#1041722: steam is incompatible with libgudev 238-2

[Felix Zielcke]

forwarded -1 https://github.com/ValveSoftware/steam-for-linux/issues/9805
thanks

Am Samstag, dem 22.07.2023 um 18:46 +0100 schrieb Simon McVittie:
> On Sat, 22 Jul 2023 at 17:43:56 +0200, Felix Zielcke wrote:
> > Steam crashes on startup with libgudev 238-2 currently in unstable.
> 
> Debian has no control over what's in the proprietary Steam client, so
> please report this sort of thing to
> .
> 
> Thanks,
>     smcv

Hi,

this seems to have been already reported upstream 2 weeks ago.
I guess even if on Debian side, nothing can be changed, it's still
useful to have the problem at least known. Which was mainly my
motivation.
As soon as it enters testing more people are affected

Processed: Re: Bug#1041511: ntfs-3g: Undocumented dependency on libbrotli-dev

[Debian Bug Tracking System]

Processing control commands:

> tags -1 +unreproducible +wontfix
Bug #1041511 [src:ntfs-3g] ntfs-3g: Undocumented dependency on libbrotli-dev
Added tag(s) unreproducible.
Bug #1041511 [src:ntfs-3g] ntfs-3g: Undocumented dependency on libbrotli-dev
Added tag(s) wontfix.
> severity -1 normal
Bug #1041511 [src:ntfs-3g] ntfs-3g: Undocumented dependency on libbrotli-dev
Severity set to 'normal' from 'serious'

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

Bug#1041511: ntfs-3g: Undocumented dependency on libbrotli-dev

[GCS]

Control: tags -1 +unreproducible +wontfix
Control: severity -1 normal

On Thu, Jul 20, 2023 at 3:57 AM Theodoric Stier  wrote:
> Source: ntfs-3g
> Severity: serious
> Tags: ftbfs
> Justification: fails to build from source (but built successfully in the past)
[...]
> This package build fails during the configure step if libbrotli-dev is not 
> installed.
> It appears to be missing from BuildDep.
 It has nothing to do with ntfs-3g. I see three things:
1) You are changing the package to be non-official:
-- cut --
dpkg-buildpackage: info: source package ntfs-3g
dpkg-buildpackage: info: source version 1:2022.10.3-2
dpkg-buildpackage: info: source distribution unstable
dpkg-buildpackage: info: source changed by Theodoric Stier 
-- cut --

2) The package does not need and doesn't check for brotli. Your build
log clearly show this:
-- cut --
configure:14736: checking for gnutls >= 1.4.
configure:14743: $PKG_CONFIG --exists --print-errors "gnutls >= 1.4.4"
Package libbrotlienc was not found in the pkg-config search path.
Perhaps you should add the directory containing `libbrotlienc.pc'
to the PKG_CONFIG_PATH environment variable
Package 'libbrotlienc', required by 'gnutls', not found
Package 'libbrotlidec', required by 'gnutls', not found
Package 'libzstd', required by 'gnutls', not found
configure:14746: $? = 1
configure:14760: $PKG_CONFIG --exists --print-errors "gnutls >= 1.4.4"
Package libbrotlienc was not found in the pkg-config search path.
Perhaps you should add the directory containing `libbrotlienc.pc'
to the PKG_CONFIG_PATH environment variable
Package 'libbrotlienc', required by 'gnutls', not found
Package 'libbrotlidec', required by 'gnutls', not found
-- cut --

It is gnutls which needs brotli, not ntfs-3g.

3) Official gnutls28 packages don't build with brotli so it seems you
have an unofficial one or you tampered with that as well.

Regards,
Laszlo/GCS

Bug#1037827: marked as pending in qscintilla2

[Dmitry Shachnev]

Control: tag -1 pending

Hello,

Bug #1037827 in qscintilla2 reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:

https://salsa.debian.org/python-team/packages/qscintilla2/-/commit/91e16749c09fbd2a0e8d70ba8b2263ba756d0ac3


Update symbols files for GCC 13.

Closes: #1037827.


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1037827

Processed: Bug#1037827 marked as pending in qscintilla2

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1037827 [src:qscintilla2] qscintilla2: ftbfs with GCC-13
Added tag(s) pending.

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

Processed: Re: r-cran-clock: autopkgtest failure on 32bit

[Debian Bug Tracking System]

Processing control commands:

> severity -1 serious
Bug #1028111 [src:r-cran-clock] r-cran-clock: autopkgtest failure on 32bit
Severity set to 'serious' from 'important'

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

Bug#1037623: marked as done (dolfinx-mpc: ftbfs with GCC-13)

[Debian Bug Tracking System]

Your message dated Sat, 22 Jul 2023 17:49:01 +
with message-id 
and subject line Bug#1037623: fixed in dolfinx-mpc 0.6.1-3
has caused the Debian Bug report #1037623,
regarding dolfinx-mpc: ftbfs with GCC-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.)


-- 
1037623: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1037623
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:dolfinx-mpc
Version: 0.5.0.post0-2
Severity: normal
Tags: sid trixie
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-13

[This bug is targeted to the upcoming trixie 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-13/g++-13, but succeeds to build with gcc-12/g++-12. The
severity of this report will be raised before the trixie release.

The full build log can be found at:
http://qa-logs.debian.net/2023/05/22/logs/dolfinx-mpc_0.5.0.post0-2_unstable_gccexp.log
The last lines of the build log are at the end of this report.

To build with GCC 13, either set CC=gcc-13 CXX=g++-13 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-13/porting_to.html

[...]
FAILED test_linear_problem.py::test_pipeline[True] - TypeError: create_period...
FAILED test_linear_problem.py::test_pipeline[False] - TypeError: create_perio...
FAILED test_matrix_assembly.py::test_mpc_assembly[celltype0-1-master_point0-C++]
FAILED test_matrix_assembly.py::test_mpc_assembly[celltype0-1-master_point1-C++]
FAILED test_matrix_assembly.py::test_mpc_assembly[celltype0-2-master_point0-C++]
FAILED test_matrix_assembly.py::test_mpc_assembly[celltype0-2-master_point1-C++]
FAILED test_matrix_assembly.py::test_mpc_assembly[celltype0-3-master_point0-C++]
FAILED test_matrix_assembly.py::test_mpc_assembly[celltype0-3-master_point1-C++]
FAILED test_matrix_assembly.py::test_mpc_assembly[celltype1-1-master_point0-C++]
FAILED test_matrix_assembly.py::test_mpc_assembly[celltype1-1-master_point1-C++]
FAILED test_matrix_assembly.py::test_mpc_assembly[celltype1-2-master_point0-C++]
FAILED test_matrix_assembly.py::test_mpc_assembly[celltype1-2-master_point1-C++]
FAILED test_matrix_assembly.py::test_mpc_assembly[celltype1-3-master_point0-C++]
FAILED test_matrix_assembly.py::test_mpc_assembly[celltype1-3-master_point1-C++]
FAILED 
test_matrix_assembly.py::test_slave_on_same_cell[celltype0-1-master_point0-C++]
FAILED 
test_matrix_assembly.py::test_slave_on_same_cell[celltype0-1-master_point1-C++]
FAILED 
test_matrix_assembly.py::test_slave_on_same_cell[celltype0-2-master_point0-C++]
FAILED 
test_matrix_assembly.py::test_slave_on_same_cell[celltype0-2-master_point1-C++]
FAILED 
test_matrix_assembly.py::test_slave_on_same_cell[celltype0-3-master_point0-C++]
FAILED 
test_matrix_assembly.py::test_slave_on_same_cell[celltype0-3-master_point1-C++]
FAILED 
test_matrix_assembly.py::test_slave_on_same_cell[celltype1-1-master_point0-C++]
FAILED 
test_matrix_assembly.py::test_slave_on_same_cell[celltype1-1-master_point1-C++]
FAILED 
test_matrix_assembly.py::test_slave_on_same_cell[celltype1-2-master_point0-C++]
FAILED 
test_matrix_assembly.py::test_slave_on_same_cell[celltype1-2-master_point1-C++]
FAILED 
test_matrix_assembly.py::test_slave_on_same_cell[celltype1-3-master_point0-C++]
FAILED 
test_matrix_assembly.py::test_slave_on_same_cell[celltype1-3-master_point1-C++]
FAILED test_mpc_pipeline.py::test_pipeline[master_point0-C++] - TypeError: __...
FAILED test_mpc_pipeline.py::test_pipeline[master_point1-C++] - TypeError: __...
FAILED test_mpc_pipeline.py::test_linearproblem[master_point0] - TypeError: _...
FAILED test_mpc_pipeline.py::test_linearproblem[master_point1] - TypeError: _...
FAILED test_nonlinear_assembly.py::test_nonlinear_possion[1] - TypeError: cre...
FAILED test_nonlinear_assembly.py::test_nonlinear_possion[2] - TypeError: cre...
FAILED test_nonlinear_assembly.py::test_nonlinear_possion[3] - TypeError: cre...
FAILED test_nonlinear_assembly.py::test_homogenize[1-FiniteElement] - TypeErr...
FAILED test_nonlinear_assembly.py::test_homogenize[1-Vect

Bug#1041722: steam is incompatible with libgudev 238-2

[Simon McVittie]

On Sat, 22 Jul 2023 at 17:43:56 +0200, Felix Zielcke wrote:
> Steam crashes on startup with libgudev 238-2 currently in unstable.

Debian has no control over what's in the proprietary Steam client, so
please report this sort of thing to
.

Thanks,
smcv

Bug#1040830: marked as done (iperf3: CVE-2023-38403: ESNET-SECADV-2023-0001: iperf3 memory allocation hazard and crash)

[Debian Bug Tracking System]

Your message dated Sat, 22 Jul 2023 17:17:38 +
with message-id 
and subject line Bug#1040830: fixed in iperf3 3.9-1+deb11u1
has caused the Debian Bug report #1040830,
regarding iperf3: CVE-2023-38403: ESNET-SECADV-2023-0001: iperf3 memory 
allocation hazard and crash
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.)


-- 
1040830: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1040830
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: iperf3
Version: 3.13-2
Severity: serious
Tags: security upstream
X-Debbugs-Cc: Debian Security Team 

A security advisory for iperf3 has been issued.

https://downloads.es.net/pub/iperf/esnet-secadv-2023-0001.txt.asc

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

ESnet Software Security Advisory
ESNET-SECADV-2023-0001

Topic:  iperf3 memory allocation hazard and crash
Issued: 7 July 2023
Credits:@someusername123 via GitHub
Affects:iperf-3.13 and earlier
Corrected:  iperf-3.14
Cross-references:   esnet/iperf#1542 on GitHub

I.  Background

iperf3 is a utility for testing network performance using TCP, UDP,
and SCTP, running over IPv4 and IPv6.  It uses a client/server model,
where a client and server communicate the parameters of a test,
coordinate the start and end of the test, and exchange results.  This
message exchange takes place over a TCP "control connection".

II.  Problem Description

The iperf3 server and client will, at various times, exchange
JSON-formatted messages containing parameters and test results. By
convention, the actual JSON representation is preceded by a four-byte
integer that gives the length of the JSON message.

iperf3 uses the length to determine the size of a dynamically
allocated memory buffer in which to store the incoming message. If the
length equals 0x, an integer overflow can be triggered in the
receiving iperf3 process (typically the server), which can in turn
cause heap corruption and an abort/crash. While this is unlikely to
happen during normal iperf3 operation, a suitably crafted client
program could send a sequence of bytes on the iperf3 control channel
to cause an iperf3 server to crash.

III.  Impact

A malicious process can connect to an iperf3 server and, by sending a
malformed message on the control channel, cause the server process to
abort due to heap corruption. A malicious iperf3 server could
potentially mount a similar attack on an iperf3 client.

Among the officially supported platforms, this problem has only been
observed on Linux. So far, it has not been reproduced with iperf3
running under Linux or macOS.

iperf2, an older version of the iperf utility, uses a different model
of interaction between client and server, and is not affected by this
issue.

IV.  Workaround

There is no workaround for this issue, however as best practice
dictates, iperf3 should not be run with root privileges, to minimize
possible impact.

V.  Solution

Update iperf3 to a version containing the fix (i.e. iperf-3.14 or
later).

VI.  Correction details

The bug causing this vulnerability has been fixed by the following
commit in the esnet/iperf Github repository:

master  0ef151550d96cc4460f98832df84b4a1e87c65e9

All released versions of iperf3 issued on or after the date of this
advisory incorporate the fix.
-BEGIN PGP SIGNATURE-

iQEzBAEBCgAdFiEE+Fo4IENp9xo01E6DSYSRCoyq7ooFAmSogHEACgkQSYSRCoyq
7orOGwgAwoF1S8ta/be1y90NYif36DnXDLjEvgcPwnFy4YadG4bI5Rx3btO73NGH
Xp/T/PXROtU40Qu3TaQsmEGFn46I+hgbGyzd11oxX1mysK6n0U3BUPCdgn7+JA5A
vpFfL4mo1efYe5cBEEUy6fnY7PipC4ltYv6I0jb4zprQalKZaPaP4TVm4si+vNKT
TViLgOZzvelIatKPl0SY7SEEQj7vkJDNw89kxQG9jZExeS1qLgPwRsmyR0b4TTDc
MMtUjn4Zl/uR2vCPeEmxTmh+QutY35vOw4N6vaqaUcHspNGJrWy5XW4QuIGEsbBq
KLsKmkzHa/fYp+1SesgNMrJkutOo2g==
=puru
-END PGP SIGNATURE-
--- End Message ---
--- Begin Message ---
Source: iperf3
Source-Version: 3.9-1+deb11u1
Done: Aron Xu 

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

Debian distribution maintenance software
pp.
Aron Xu  (supplier of updated iperf3 package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
admini

Bug#1040830: marked as done (iperf3: CVE-2023-38403: ESNET-SECADV-2023-0001: iperf3 memory allocation hazard and crash)

[Debian Bug Tracking System]

Your message dated Sat, 22 Jul 2023 17:17:08 +
with message-id 
and subject line Bug#1040830: fixed in iperf3 3.12-1+deb12u1
has caused the Debian Bug report #1040830,
regarding iperf3: CVE-2023-38403: ESNET-SECADV-2023-0001: iperf3 memory 
allocation hazard and crash
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.)


-- 
1040830: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1040830
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: iperf3
Version: 3.13-2
Severity: serious
Tags: security upstream
X-Debbugs-Cc: Debian Security Team 

A security advisory for iperf3 has been issued.

https://downloads.es.net/pub/iperf/esnet-secadv-2023-0001.txt.asc

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

ESnet Software Security Advisory
ESNET-SECADV-2023-0001

Topic:  iperf3 memory allocation hazard and crash
Issued: 7 July 2023
Credits:@someusername123 via GitHub
Affects:iperf-3.13 and earlier
Corrected:  iperf-3.14
Cross-references:   esnet/iperf#1542 on GitHub

I.  Background

iperf3 is a utility for testing network performance using TCP, UDP,
and SCTP, running over IPv4 and IPv6.  It uses a client/server model,
where a client and server communicate the parameters of a test,
coordinate the start and end of the test, and exchange results.  This
message exchange takes place over a TCP "control connection".

II.  Problem Description

The iperf3 server and client will, at various times, exchange
JSON-formatted messages containing parameters and test results. By
convention, the actual JSON representation is preceded by a four-byte
integer that gives the length of the JSON message.

iperf3 uses the length to determine the size of a dynamically
allocated memory buffer in which to store the incoming message. If the
length equals 0x, an integer overflow can be triggered in the
receiving iperf3 process (typically the server), which can in turn
cause heap corruption and an abort/crash. While this is unlikely to
happen during normal iperf3 operation, a suitably crafted client
program could send a sequence of bytes on the iperf3 control channel
to cause an iperf3 server to crash.

III.  Impact

A malicious process can connect to an iperf3 server and, by sending a
malformed message on the control channel, cause the server process to
abort due to heap corruption. A malicious iperf3 server could
potentially mount a similar attack on an iperf3 client.

Among the officially supported platforms, this problem has only been
observed on Linux. So far, it has not been reproduced with iperf3
running under Linux or macOS.

iperf2, an older version of the iperf utility, uses a different model
of interaction between client and server, and is not affected by this
issue.

IV.  Workaround

There is no workaround for this issue, however as best practice
dictates, iperf3 should not be run with root privileges, to minimize
possible impact.

V.  Solution

Update iperf3 to a version containing the fix (i.e. iperf-3.14 or
later).

VI.  Correction details

The bug causing this vulnerability has been fixed by the following
commit in the esnet/iperf Github repository:

master  0ef151550d96cc4460f98832df84b4a1e87c65e9

All released versions of iperf3 issued on or after the date of this
advisory incorporate the fix.
-BEGIN PGP SIGNATURE-

iQEzBAEBCgAdFiEE+Fo4IENp9xo01E6DSYSRCoyq7ooFAmSogHEACgkQSYSRCoyq
7orOGwgAwoF1S8ta/be1y90NYif36DnXDLjEvgcPwnFy4YadG4bI5Rx3btO73NGH
Xp/T/PXROtU40Qu3TaQsmEGFn46I+hgbGyzd11oxX1mysK6n0U3BUPCdgn7+JA5A
vpFfL4mo1efYe5cBEEUy6fnY7PipC4ltYv6I0jb4zprQalKZaPaP4TVm4si+vNKT
TViLgOZzvelIatKPl0SY7SEEQj7vkJDNw89kxQG9jZExeS1qLgPwRsmyR0b4TTDc
MMtUjn4Zl/uR2vCPeEmxTmh+QutY35vOw4N6vaqaUcHspNGJrWy5XW4QuIGEsbBq
KLsKmkzHa/fYp+1SesgNMrJkutOo2g==
=puru
-END PGP SIGNATURE-
--- End Message ---
--- Begin Message ---
Source: iperf3
Source-Version: 3.12-1+deb12u1
Done: Aron Xu 

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

Debian distribution maintenance software
pp.
Aron Xu  (supplier of updated iperf3 package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
admi

Bug#1040179: marked as done (rmlint-gui: invalid Python version number breaks other packages)

[Debian Bug Tracking System]

Your message dated Sat, 22 Jul 2023 16:02:11 +
with message-id 
and subject line Bug#1040179: fixed in rmlint 2.9.0-2.3+deb12u1
has caused the Debian Bug report #1040179,
regarding rmlint-gui: invalid Python version number breaks other packages
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.)


-- 
1040179: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1040179
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: spyder
Version: 5.4.2+ds-5
Severity: normal
X-Debbugs-Cc: mhaag85...@gmail.com

Dear Maintainer,

Ran $spyder --reset but, still get the missing dependency message.


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

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

Versions of packages spyder depends on:
ii  python3 3.11.2-1+b1
ii  python3-spyder  5.4.2+ds-5

spyder recommends no packages.

Versions of packages spyder suggests:
pn  python3-spyder-unittest  

Versions of packages python3-spyder depends on:
ii  ipython3   8.5.0-4
ii  libjs-jquery   3.6.1+dfsg+~3.5.14-1
ii  libjs-mathjax  2.7.9+dfsg-1
ii  pyflakes3  2.5.0-1
ii  pylint 2.16.2-2
ii  python33.11.2-1+b1
ii  python3-atomicwrites   1.4.1-1
ii  python3-autopep8   2.0.1-1
ii  python3-chardet5.1.0+dfsg-2
ii  python3-cloudpickle2.2.0-1
ii  python3-cookiecutter   1.7.3-3
ii  python3-diff-match-patch   20200713-2
ii  python3-docutils   0.19+dfsg-6
ii  python3-flake8 5.0.4-4
ii  python3-intervaltree   3.0.2-1.1
ii  python3-ipython8.5.0-4
ii  python3-jedi   0.18.2-1
ii  python3-jellyfish  0.8.9-1+b4
ii  python3-jsonschema 4.10.3-1
ii  python3-keyring23.9.3-2
ii  python3-mccabe 0.7.0-1
ii  python3-nbconvert  6.5.3-3
ii  python3-numpydoc   1.5.0-1
ii  python3-parso  0.8.3-1
ii  python3-pexpect4.8.0-4
ii  python3-pickleshare0.7.5-5
ii  python3-pkg-resources  66.1.1-1
ii  python3-psutil 5.9.4-1+b1
ii  python3-pycodestyle2.10.0-1
ii  python3-pydocstyle 6.2.3-3
ii  python3-pygments   2.14.0+dfsg-1
ii  python3-pylint-venv2.3.0-2
ii  python3-pyls-spyder0.4.0-2
ii  python3-pylsp  1.7.1-1
ii  python3-pylsp-black1.2.1-2
ii  python3-pyqt5  5.15.9+dfsg-1
ii  python3-pyqt5.qtwebengine  5.15.6-1
ii  python3-qdarkstyle 3.1+ds1-1
ii  python3-qstylizer  0.2.2-1
ii  python3-qtawesome  1.2.2+dfsg-1
ii  python3-qtconsole  5.4.0-1
ii  python3-qtpy   2.3.0-1
ii  python3-rope   1.7.0-1
ii  python3-rtree  1.0.1-1
ii  python3-setuptools 66.1.1-1
ii  python3-sphinx 5.3.0-4
ii  python3-spyder-kernels 2.4.2-1
ii  python3-textdistance   4.5.0-1
ii  python3-three-merge0.1.1-4
ii  python3-watchdog   2.2.1-1
ii  python3-xdg0.28-2
ii  python3-zmq24.0.1-4+b1
ii  spyder-common  5.4.2+ds-5
ii  yapf3  0.32.0-1

python3-spyder recommends no packages.

Versions of packages python3-spyder suggests:
pn  cython3 
ii  python3-matplotlib  3.6.3-1+b1
ii  python3-numpy   1:1.24.2-1
ii  python3-pandas  1.5.3+dfsg-2
ii  python3-pil 9.4.0-1.1+b1
ii  python3-scipy   1.10.1-2
ii  python3-sympy   1.11.1-1

Versions of packages python3-pyqt5 depends on:
ii  libc6 2.36-9
ii  libgcc-s1 12.2.0-14
ii  libpython3.11 3.11.2-6
ii  libqt5core5a [qtbase-abi-5-15-8]  5.15.8+dfsg-11
ii  libqt5dbus5   5.15.8+dfsg-11
ii  libqt5designer5   5.15.8-2
ii  libqt5gui55.15.8+dfsg-11
ii  libqt5help5   5.15.8-2
ii  libqt5network55.15.8+dfsg-11
ii  libqt5printsupport5   5.15.8+dfsg-11
ii  libqt5test5   5.15.8+dfsg-11
ii  libqt5widgets55.15.8+dfsg-11
ii  libqt5xml55.15.8+dfsg-11
ii  libstdc++612.2.0-14
ii  python3   3.11.2-1+b1
ii  python3-pyqt5.

Bug#1041722: steam is incompatible with libgudev 238-2

[Felix Zielcke]

Package: steam-installer
Version: 1:1.0.0.78~ds-2
Severity: grave

Steam crashes on startup with libgudev 238-2 currently in unstable.
libgudev 237-2 from testing works fine with Steam.

Console only shows this for the crash:

Assertion 'device' failed at src/libsystemd/sd-device/device-private.c:103, 
function device_get_tags_generation(). Aborting.
crash_20230722173957_25.dmp[26236]: Uploading dump (out-of-process)

No stack trace or anything else which differs between working and crashing 
steam.


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

Kernel: Linux 6.3.0-2-amd64 (SMP w/12 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages steam-installer depends on:
ii  debconf [debconf-2.0]  1.5.82
ii  steam-libs 1:1.0.0.78~ds-2
ii  steam-libs-i3861:1.0.0.78
ii  yad0.40.0-1+b1
ii  zenity 3.44.0-3

steam-installer recommends no packages.

steam-installer suggests no packages.

Versions of packages steam-libs depends on:
ii  ca-certificates  20230311
ii  curl 7.88.1-10
ii  file 1:5.44-3
ii  libc62.37-6
ii  libcrypt11:4.4.35-1
ii  libgcc-s1 [libgcc1]  13.1.0-9
ii  libgl1   1.6.0-1
ii  libgl1-mesa-dri  23.1.3-1
ii  libgpg-error01.46-1
ii  libstdc++6   13.1.0-9
ii  libudev1 254~rc2-3
ii  libva-x11-2  2.19.0-1
ii  libva2   2.19.0-1
ii  libxcb-dri3-01.15-1
ii  libxcb1  1.15-1
ii  libxi6   2:1.8-1+b1
ii  libxinerama1 2:1.1.4-3
ii  xz-utils 5.4.1-0.2

Versions of packages steam-libs recommends:
ii  fontconfig   2.14.1-4
ii  fonts-liberation 1:2.1.5-3
ii  libasound2-plugins   1.2.7.1-1
ii  libegl1  1.6.0-1
ii  libexpat12.5.0-2
ii  libfontconfig1   2.14.1-4
ii  libgbm1  23.1.3-1
ii  libsdl2-2.0-02.28.1+dfsg-1
ii  libva-drm2   2.19.0-1
ii  libva-glx2   2.19.0-1
ii  libx11-6 2:1.8.6-1
ii  libx11-xcb1  2:1.8.6-1
ii  libxau6  1:1.0.9-1
ii  libxcb-dri2-01.15-1
ii  libxcb-glx0  1.15-1
ii  libxcb-present0  1.15-1
ii  libxcb-sync1 1.15-1
ii  libxdamage1  1:1.1.6-1
ii  libxdmcp61:1.1.2-3
ii  libxext6 2:1.3.4-1+b1
ii  libxfixes3   1:6.0.0-2
ii  libxss1  1:1.2.3-1
ii  libxxf86vm1  1:1.1.4-1+b2
ii  mate-terminal [x-terminal-emulator]  1.26.1-1
pn  mesa-vulkan-drivers  
pn  steam-devices
pn  va-driver-all | va-driver
ii  xdg-desktop-portal   1.16.0-2
ii  xdg-desktop-portal-gtk [xdg-desktop-portal-backend]  1.14.1-1
ii  xdg-utils1.1.3-4.1
ii  xterm [x-terminal-emulator]  384-1
ii  zenity   3.44.0-3

Versions of packages steam-libs suggests:
ii  libudev0200-1
ii  nvidia-driver-libs  525.125.06-1
ii  nvidia-vulkan-icd   525.125.06-1
ii  pipewire0.3.74-1

Versions of packages steam-libs-i386 depends on:
ii  libc62.37-6
ii  libcrypt11:4.4.35-1
ii  libegl1  1.6.0-1
ii  libgbm1  23.1.3-1
ii  libgcc-s1 [libgcc1]  13.1.0-9
ii  libgl1   1.6.0-1
ii  libgl1-mesa-dri  23.1.3-1
ii  libgpg-error01.46-1
ii  libstdc++6   13.1.0-9
ii  libudev0 200-1
ii  libudev1 254~rc2-3
ii  libx11-6 2:1.8.6-1
ii  libxcb-dri3-01.15-1
ii  libxcb1  1.15-1
ii  libxinerama1 2:1.1.4-3

Versions of packages steam-libs-i386 recommends:
ii  libasound2-plugins 1.2.7.1-1
ii  libfontconfig1 2.14.1-4

Bug#1041674: with attachment

[Rudi Heitbaum]

with attachment

--- a/Makefile.am	2023-07-21 22:53:36.152522891 +
+++ b/Makefile.am	2023-07-22 00:12:21.796916350 +
@@ -58,6 +58,8 @@
 
 libfakeroot.lo:libfakeroot.c wrapdef.h wrapstruct.h wraptmpf.h
 
+libfakeroot_time64.c:wrapped.h
+
 fakerootconfig.h: ./config.status
 	CONFIG_FILES= CONFIG_HEADERS= /bin/sh ./config.status
 

Bug#999977: qxw: depends on obsolete pcre3 library

[Bastian Germann]

I suggest to remove the package. I do not think upstream will deal with 
this.

Processed: Re: Broken due to missed udev dependencies

[Debian Bug Tracking System]

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

> severity 1041703 important
Bug #1041703 [libgudev-1.0-0] Broken due to missed udev dependencies
Severity set to 'important' from 'grave'
> thanks
Stopping processing here.

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

Bug#1041703: Broken due to missed udev dependencies

[Martin Steigerwald]

severity 1041703 important
thanks

Martin Steigerwald - 22.07.23, 15:41:41 CEST:
> severity 1041703 grave
> thanks
> 
> Justification: Renders X unusable, renders fwupdmgr unusable

On the other hand Sid should have libudev1 254~rc2-3. Even testing 
should have 253.5-1 already.

Ah and I see Klaus is using eudev. Thus lowering bug severity again.

-- 
Martin

Bug#1041703: Broken due to missed udev dependencies

[Martin Steigerwald]

Working package for AMD64:

https://ftp.debian.org/debian/pool/main/libg/libgudev/libgudev-1.0-0_237-2_amd64.deb

-- 
Martin

Processed: Re: Broken due to missed udev dependencies

[Debian Bug Tracking System]

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

> severity 1041703 grave
Bug #1041703 [libgudev-1.0-0] Broken due to missed udev dependencies
Severity set to 'grave' from 'important'
> thanks
Stopping processing here.

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

Processed: dolfin: libdolfin needs ABI bump

[Debian Bug Tracking System]

Processing control commands:

> affects -1 python3-mshr
Bug #1041705 [src:dolfin] dolfin: libdolfin needs ABI bump
Added indication that 1041705 affects python3-mshr

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

Bug#1041705: dolfin: libdolfin needs ABI bump

[Drew Parsons]

Source: dolfin
Version: 2019.2.0~legacy20230609.8b85e9d.ar-2
Severity: serious
Justification: Policy 8.6.2
Control: affects -1 python3-mshr

The accumulation of git changes and gcc-13 fixes has apparently
introduced an ABI inconsistency in libdolfin.so, such that mshr can no
longer be imported in python, and mshr tests fails.
see
https://ci.debian.net/data/autopkgtest/testing/amd64/f/fenics/36044020/log.gz
https://ci.debian.net/data/autopkgtest/testing/amd64/m/mshr/36044021/log.gz

A rebuild of mshr fixes the issue, but really dolfin shouldn't migrate
to testing if it's doing this, so marking severity: serious.
A new upstream release is expected soon which we'll treat as an ABI
upgrade to resolve the issue.

Bug#1041674: simple dependancy between wrapped.h and libfakeroot_time64.c fixes the build issue

[Rudi Heitbaum]

as per the attached patch, a simple dependancy on wrapped.h against 
libfakeroot_time64.c fixes the issue.

Bug#1041683: marked as done (undeclared file conflict between fabio-viewer and python3-fabio)

[Debian Bug Tracking System]

Your message dated Sat, 22 Jul 2023 12:27:30 +
with message-id 
and subject line Bug#1041683: fixed in python-fabio 2023.6.0-3
has caused the Debian Bug report #1041683,
regarding undeclared file conflict between fabio-viewer and python3-fabio
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.)


-- 
1041683: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1041683
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: python3-fabio,fabio-viewer
Severity: serious

Since very recently, there is an undeclared file conflict between
fabio-viewer and python3-fabio about programs such as
/usr/bin/fabio-convert. It is not clear to me how this is to be
resolved. Is this an attempt to restructure the package?

Helmut
--- End Message ---
--- Begin Message ---
Source: python-fabio
Source-Version: 2023.6.0-3
Done: Picca Frédéric-Emmanuel 

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

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

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

Debian distribution maintenance software
pp.
Picca Frédéric-Emmanuel  (supplier of updated python-fabio 
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, 22 Jul 2023 13:07:18 +0200
Source: python-fabio
Architecture: source
Version: 2023.6.0-3
Distribution: unstable
Urgency: medium
Maintainer: Debian PaN Maintainers 

Changed-By: Picca Frédéric-Emmanuel 
Closes: 1041683
Changes:
 python-fabio (2023.6.0-3) unstable; urgency=medium
 .
   * Bug fix: "undeclared file conflict between fabio-viewer and
 python3-fabio", thanks to Helmut Grohne (Closes: #1041683).
Checksums-Sha1:
 f7a0ca10ba4766e7e77516f61f5a44a5eed4acf3 3069 python-fabio_2023.6.0-3.dsc
 6036c35d216c7032a5ce5e139f7de38b535a5515 8588 
python-fabio_2023.6.0-3.debian.tar.xz
Checksums-Sha256:
 004ef33dab232c2a0d773d6958fa2b2965acfc49895a0953e5e380b6ac446a88 3069 
python-fabio_2023.6.0-3.dsc
 b0fff61a07c3010eabb03a4c60bf2a4ce459245c8496a33d39465a59b3907796 8588 
python-fabio_2023.6.0-3.debian.tar.xz
Files:
 2e62762a7c5eb7161525e6a8028bb49e 3069 science optional 
python-fabio_2023.6.0-3.dsc
 162c25b2eb82947f3011d3dd6d5965cc 8588 science optional 
python-fabio_2023.6.0-3.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQJFBAEBCgAvFiEE2bRTt5m4gw2UXmoKW/VOXhK5ALsFAmS7uRwRHHBpY2NhQGRl
Ymlhbi5vcmcACgkQW/VOXhK5ALtcCBAAkjgDZimRt6SUBPeLQ1tkKev29/QZCYPV
NbNzADjcSNaMK1Rzcmgq7rso6xFuYQkQQRubJ+gwO/CO1MoXOr1WLMHZlIiwa/22
g8rxP/Q2ZzrXvx7nKpWntGQXaCpPI+QpZ50NLpTBY9/EZmN8c92uBsZVr2joSSbq
H7gc3ZnonjyvWrzymbVBhpz18NdhcZY4wMvzNJAfb3FbGdeXWY1Wv6oJDBb48qGF
ZyngGoGWEjyO8QfmGRsOomNTp2supaCVyebKONlLWQq0LBnPQEjhluXiDa5RcG8z
S17cEiMqTacekyVZJ0A/M0BwVYF8IaSdLQT9GohJOZPDGzVS3vgcEXJZfW/4h/vD
rchiiB7kNl2S6iEkizm+AShUozLNmXaBnyJSpxxbVLYEAn0fqikjv277YcpaDJ9J
azAlISFRTH07BY7eITumGLESLCmK2awHPzj7Sv70GhgfrS/bbBYFzwfsZNMYGv/z
zz59X/g7Z05lNOjimXWO/leXFf/bp3sAM9oGvTQKJricw+OKzpRM0Z4aBT7GIIaY
mSXg0cgdAzsS/5AO1QUnpXL4WzqgwKxqXH0/AG0BPUP4vyhz9Pbh+PFQ0WgNtxUF
pKDH5QXDHaoIIT96eJXIDD8zpXMbmoSdAU5EeiwMlsPg7vbUaK02oBeW6+CGQzNT
wOqW/Mh5rdE=
=/MHf
-END PGP SIGNATURE End Message ---

Bug#1039635: marked as done (r-bioc-biomart: autopkgtest failure with r-base (4.3.1-1))

[Debian Bug Tracking System]

Your message dated Sat, 22 Jul 2023 12:28:00 +
with message-id 
and subject line Bug#1039635: fixed in r-bioc-biomart 2.56.1+dfsg-1
has caused the Debian Bug report #1039635,
regarding r-bioc-biomart: autopkgtest failure with r-base (4.3.1-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.)


-- 
1039635: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1039635
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: r-bioc-biomart
Version: 2.54.0+dfsg-1
Severity: serious
Justification: autopkgtest failure

Dear Maintainer,

The autopkgtest of your package fails with r-base (4.3.1-1):

 154s [ FAIL 1 | WARN 0 | SKIP 1 | PASS 146 ]
 154s 
 154s ══ Skipped tests 
═══
 154s • On Linux (1)
 154s 
 154s ══ Failed tests 

 154s ── Failure ('test_ensembl_ssl_settings.R:71'): SSL settings are stored in 
the cache ──
 154s `httr_config <- .getEnsemblSSL()` produced messages.
 154s 
 154s [ FAIL 1 | WARN 0 | SKIP 1 | PASS 146 ]

https://ci.debian.net/data/autopkgtest/testing/s390x/r/r-bioc-biomart/34906431/log.gz
--- End Message ---
--- Begin Message ---
Source: r-bioc-biomart
Source-Version: 2.56.1+dfsg-1
Done: Andreas Tille 

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

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

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sat, 22 Jul 2023 12:44:47 +0200
Source: r-bioc-biomart
Architecture: source
Version: 2.56.1+dfsg-1
Distribution: unstable
Urgency: medium
Maintainer: Debian R Packages Maintainers 
Changed-By: Andreas Tille 
Closes: 1039501 1039635
Changes:
 r-bioc-biomart (2.56.1+dfsg-1) unstable; urgency=medium
 .
   * Rebuild against latest r-base
 Closes: #1039635
   * New upstream version
 Closes: #1039501
   * Standards-Version: 4.6.2 (routine-update)
   * Reorder sequence of d/control fields by cme (routine-update)
   * Set upstream metadata fields: Bug-Database, Bug-Submit, Repository-Browse.
Checksums-Sha1:
 1c4b45a3b15aca3ce2c5450c44983a3c1a7292f8 2242 r-bioc-biomart_2.56.1+dfsg-1.dsc
 29a5fc8d0ea56f44fd985c5240c861997c79db58 117104 
r-bioc-biomart_2.56.1+dfsg.orig.tar.xz
 e6328d87bfe54f631b66de119e02a7c65213d944 6044 
r-bioc-biomart_2.56.1+dfsg-1.debian.tar.xz
 41981f75a6037b061b2cc8fe1de3034fa6bf316d 12429 
r-bioc-biomart_2.56.1+dfsg-1_amd64.buildinfo
Checksums-Sha256:
 a78d0bb5025b56716d94205d0416c5b62a2bbc7d707e6312bcd4b78f67c69f37 2242 
r-bioc-biomart_2.56.1+dfsg-1.dsc
 af39849c3b9e01af2e47e83c840790cba45eab4e3d7b91a982118ac2b06296ff 117104 
r-bioc-biomart_2.56.1+dfsg.orig.tar.xz
 7b0a0b5d52f7596e6d69c5fd34a17a00f89a2e822e1336e8f94037757c4ad55b 6044 
r-bioc-biomart_2.56.1+dfsg-1.debian.tar.xz
 695cdea9e046932d29b3e4e407b13a9e00ab7c10eea4192c9b85886801229f51 12429 
r-bioc-biomart_2.56.1+dfsg-1_amd64.buildinfo
Files:
 b48c2f9e2d6e9c842ebc0aed34c58ed5 2242 gnu-r optional 
r-bioc-biomart_2.56.1+dfsg-1.dsc
 8801aecb5b2b2f20aff5d8c4f4b7f864 117104 gnu-r optional 
r-bioc-biomart_2.56.1+dfsg.orig.tar.xz
 23a69b2cb2bf394387fd78e885c04783 6044 gnu-r optional 
r-bioc-biomart_2.56.1+dfsg-1.debian.tar.xz
 74bd050993bf150f5c46ae997730e333 12429 gnu-r optional 
r-bioc-biomart_2.56.1+dfsg-1_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQJFBAEBCAAvFiEE8fAHMgoDVUHwpmPKV4oElNHGRtEFAmS7wlERHHRpbGxlQGRl
Ymlhbi5vcmcACgkQV4oElNHGRtH76A//YjXiuWK8/Zn/05PrOvov/fPlJ2MrzGRq
NqD7ZH0nu/6n+OC6Ib+7bdWjoYgeF1Sufgk3mH3Ku6mDsLGeC1pj5+ttsrpFLAB1
Ri1Q/n6GHQo72QY+WgBCgnVpsZnUJ+eXrrUEESOw4WKka8zflAuN/E1+6XvWQg4Z
4X4RwlVmU6AS1fh2VCz3VFJWkPDc6S3hhT1VuwVFHb0TjNovcn9PhwtuNLErEFm4
hNfySpX6Ggc+EfVRZkHT7YWj9WpESX3Kip+dHAMeaW3BewHz68zzZl2GTxHOGaha
EVcbEGddcGl33i79veZvLHsxQU4lE4purxcEFGBUnK86P++05ucUCmF0DmgWqEjX
lpto8xOwhal2aLEMCEGL1K9NdhVNb88PjgFZiwf872d96y2xHGhb8dDx22Z/rL9K
uhYBguag+DyIxVo+1LGh9sqHucB5z4MisSA77W8pk6kguyhpHcJQgaFIC8ceLuOz
m22rVCeD6GqvHR4SryPzLwMlQV2nA3vpcAu2LQhoD8/L1MaLLYea5xiERqETjAWS
h5fmIEfbmh

Bug#1039501: marked as done (r-bioc-biomart: autopkgtest regression: Failure ('test_ensembl_ssl_settings.R:71'))

[Debian Bug Tracking System]

Your message dated Sat, 22 Jul 2023 12:28:00 +
with message-id 
and subject line Bug#1039501: fixed in r-bioc-biomart 2.56.1+dfsg-1
has caused the Debian Bug report #1039501,
regarding r-bioc-biomart: autopkgtest regression: Failure 
('test_ensembl_ssl_settings.R:71')
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.)


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

Source: r-bioc-biomart
Version: 2.54.0+dfsg-1
Severity: serious
User: debian...@lists.debian.org
Usertags: regression

Dear maintainer(s),

Your package has an autopkgtest, great. However, it fails since end of 
May 2023 in unstable, testing and stable. Can you please investigate the 
situation and fix it? I copied some of the output at the bottom of this 
report.


The release team has announced [1] that failing autopkgtest on amd64 and 
arm64 are considered RC in testing.


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


Paul

[1] https://lists.debian.org/debian-devel-announce/2019/07/msg2.html

https://ci.debian.net/data/autopkgtest/testing/amd64/r/r-bioc-biomart/34804623/log.gz

102s ══ Failed tests 

102s ── Failure ('test_ensembl_ssl_settings.R:71'): SSL settings are 
stored in the cache ──

102s `httr_config <- .getEnsemblSSL()` produced messages.
102s
102s [ FAIL 1 | WARN 0 | SKIP 1 | PASS 146 ]


OpenPGP_signature
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Source: r-bioc-biomart
Source-Version: 2.56.1+dfsg-1
Done: Andreas Tille 

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

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

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sat, 22 Jul 2023 12:44:47 +0200
Source: r-bioc-biomart
Architecture: source
Version: 2.56.1+dfsg-1
Distribution: unstable
Urgency: medium
Maintainer: Debian R Packages Maintainers 
Changed-By: Andreas Tille 
Closes: 1039501 1039635
Changes:
 r-bioc-biomart (2.56.1+dfsg-1) unstable; urgency=medium
 .
   * Rebuild against latest r-base
 Closes: #1039635
   * New upstream version
 Closes: #1039501
   * Standards-Version: 4.6.2 (routine-update)
   * Reorder sequence of d/control fields by cme (routine-update)
   * Set upstream metadata fields: Bug-Database, Bug-Submit, Repository-Browse.
Checksums-Sha1:
 1c4b45a3b15aca3ce2c5450c44983a3c1a7292f8 2242 r-bioc-biomart_2.56.1+dfsg-1.dsc
 29a5fc8d0ea56f44fd985c5240c861997c79db58 117104 
r-bioc-biomart_2.56.1+dfsg.orig.tar.xz
 e6328d87bfe54f631b66de119e02a7c65213d944 6044 
r-bioc-biomart_2.56.1+dfsg-1.debian.tar.xz
 41981f75a6037b061b2cc8fe1de3034fa6bf316d 12429 
r-bioc-biomart_2.56.1+dfsg-1_amd64.buildinfo
Checksums-Sha256:
 a78d0bb5025b56716d94205d0416c5b62a2bbc7d707e6312bcd4b78f67c69f37 2242 
r-bioc-biomart_2.56.1+dfsg-1.dsc
 af39849c3b9e01af2e47e83c840790cba45eab4e3d7b91a982118ac2b06296ff 117104 
r-bioc-biomart_2.56.1+dfsg.orig.tar.xz
 7b0a0b5d52f7596e6d69c5fd34a17a00f89a2e822e1336e8f94037757c4ad55b 6044 
r-bioc-biomart_2.56.1+dfsg-1.debian.tar.xz
 695cdea9e046932d29b3e4e407b13a9e00ab7c10eea4192c9b85886801229f51 12429 
r-bioc-biomart_2.56.1+dfsg-1_amd64.buildinfo
Files:
 b48c2f9e2d6e9c842ebc0aed34c58ed5 2242 gnu-r optional 
r-bioc-biomart_2.56.1+dfsg-1.dsc
 8801aecb5b2b2f20aff5d8c4f4b7f864 117104 gnu-r optional 
r-bioc-biomart_2.56.1+dfsg.orig.tar.xz
 23a69b2cb2bf394387fd78e885c04783 6044 gnu-r optional 
r-bioc-biomart_2.56.1+dfsg-1.debian.tar.xz
 74bd050993bf150f5c46ae997730e333 12429 gnu-r optional 
r-bioc-biomart_2.56.1+dfsg-1_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQJFBAEBCAAvFiEE8fAHMgoDVUHwpmPKV4oElNHGRtEFAmS7wlERHHRpbGxlQGRl
Ymlhbi5vcmcACgkQV4oElNHGRtH76A//YjXiuWK8/Zn/05PrOvov/fPlJ2MrzGRq
NqD7ZH0nu/6n+OC6Ib+7bdWjoYgeF1Sufgk3mH3Ku6mDsLGeC1pj5+ttsrpFLAB1
Ri1Q/n6GHQo72QY+Wg

Bug#1037851: marked as done (rumur: ftbfs with GCC-13)

[Debian Bug Tracking System]

Your message dated Sat, 22 Jul 2023 12:28:24 +
with message-id 
and subject line Bug#1037851: fixed in rumur 2023.05.21-1
has caused the Debian Bug report #1037851,
regarding rumur: ftbfs with GCC-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.)


-- 
1037851: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1037851
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:rumur
Version: 2022.08.20-1
Severity: normal
Tags: sid trixie
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-13

[This bug is targeted to the upcoming trixie 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-13/g++-13, but succeeds to build with gcc-12/g++-12. The
severity of this report will be raised before the trixie release.

The full build log can be found at:
http://qa-logs.debian.net/2023/05/22/logs/rumur_2022.08.20-1_unstable_gccexp.log
The last lines of the build log are at the end of this report.

To build with GCC 13, either set CC=gcc-13 CXX=g++-13 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-13/porting_to.html

[...]
cd /<>/librumur && /usr/bin/flex --noline 
-o/<>/obj-x86_64-linux-gnu/librumur/lexer.l.cc src/lexer.l
make[3]: Leaving directory '/<>/obj-x86_64-linux-gnu'
make  -f rumur/CMakeFiles/man-rumur.dir/build.make 
rumur/CMakeFiles/man-rumur.dir/build
src/parser.yy: warning: 4 shift/reduce conflicts [-Wconflicts-sr]
src/parser.yy: note: rerun with option '-Wcounterexamples' to generate conflict 
counterexamples
make[3]: Entering directory '/<>/obj-x86_64-linux-gnu'
[  4%] Generating murphi2uclid.1.gz
cd /<>/murphi2uclid && gzip -9 --no-name --to-stdout 
doc/murphi2uclid.1 
>"/<>/obj-x86_64-linux-gnu/murphi2uclid/murphi2uclid.1.gz"
[  5%] Generating murphi2c.1.gz
[  6%] Generating murphi2murphi.1.gz
cd /<>/murphi2c && gzip -9 --no-name --to-stdout doc/murphi2c.1 
>"/<>/obj-x86_64-linux-gnu/murphi2c/murphi2c.1.gz"
cd /<>/murphi2murphi && gzip -9 --no-name --to-stdout 
doc/murphi2murphi.1 
>"/<>/obj-x86_64-linux-gnu/murphi2murphi/murphi2murphi.1.gz"
[  7%] Generating murphi2xml.1.gz
make[3]: Leaving directory '/<>/obj-x86_64-linux-gnu'
cd /<>/murphi2xml && gzip -9 --no-name --to-stdout 
doc/murphi2xml.1 
>"/<>/obj-x86_64-linux-gnu/murphi2xml/murphi2xml.1.gz"
make[3]: Leaving directory '/<>/obj-x86_64-linux-gnu'
make[3]: Leaving directory '/<>/obj-x86_64-linux-gnu'
make[3]: Leaving directory '/<>/obj-x86_64-linux-gnu'
[  7%] Generating rumur.1.gz
cd /<>/rumur && gzip -9 --no-name --to-stdout doc/rumur.1 
>"/<>/obj-x86_64-linux-gnu/rumur/rumur.1.gz"
[  7%] Generating rumur-get-version.h
cd /<>/librumur && src/make-version.py 
/<>/obj-x86_64-linux-gnu/librumur/rumur-get-version.h
[  7%] Built target man-murphi2uclid
[  8%] Generating rumur-run.1.gz
[  8%] Built target man-murphi2murphi
cd /<>/rumur && gzip -9 --no-name --to-stdout doc/rumur-run.1 
>"/<>/obj-x86_64-linux-gnu/rumur/rumur-run.1.gz"
[  8%] Built target man-murphi2xml
[  8%] Built target man-murphi2c
make[3]: Leaving directory '/<>/obj-x86_64-linux-gnu'
[  8%] Built target man-rumur
cd /<>/obj-x86_64-linux-gnu && /usr/bin/cmake -E cmake_depends 
"Unix Makefiles" /<> /<>/librumur 
/<>/obj-x86_64-linux-gnu 
/<>/obj-x86_64-linux-gnu/librumur 
/<>/obj-x86_64-linux-gnu/librumur/CMakeFiles/librumur.dir/DependInfo.cmake
 --color=
make[3]: Leaving directory '/<>/obj-x86_64-linux-gnu'
make  -f librumur/CMakeFiles/librumur.dir/build.make 
librumur/CMakeFiles/librumur.dir/build
make[3]: Entering directory '/<>/obj-x86_64-linux-gnu'
[ 11%] Building CXX object librumur/CMakeFiles/librumur.dir/src/Comment.cc.o
[ 11%] Building CXX object librumur/CMakeFiles/librumur.dir/src/except.cc.o
[ 11%] Building CXX object librumur/CMakeFiles/librumur.dir/src/Decl.cc.o
[ 11%] Building CXX object librumur/CMakeFiles/librumur.dir/src/Boolean.cc.o
[ 12%] Building CXX object librumur/CMakeFiles/librumur.dir/src/Expr.cc.o
[ 13%] Building CXX object librumur/CMakeFiles/librumur.dir/src/Function.cc.o
[ 15%] Building CXX object librumur/CMakeFiles/

Bug#1034852: marked as done (r-bioc-annotationhub: autopkgtest regression: download failed)

[Debian Bug Tracking System]

Your message dated Sat, 22 Jul 2023 12:27:51 +
with message-id 
and subject line Bug#1034852: fixed in r-bioc-annotationhub 3.8.0+dfsg-1
has caused the Debian Bug report #1034852,
regarding r-bioc-annotationhub: autopkgtest regression: download failed
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.)


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

Source: r-bioc-annotationhub
Version: 3.6.0+dfsg-1
Severity: serious
Control: tags -1 bookworm-ignore
User: debian...@lists.debian.org
Usertags: regression

Dear maintainer(s),

Your package has an autopkgtest, great. However, it fails since April 
2023. Can you please investigate the situation and fix it? I copied some 
of the output at the bottom of this report.


The release team has announced [1] that failing autopkgtest on amd64 and 
arm64 are considered RC in testing. [Release Team member hat on] Because 
we're currently in the hard freeze for bookworm, I have marked this bug 
as bookworm-ignore. Targeted fixes are still welcome.


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


Paul

[1] https://lists.debian.org/debian-devel-announce/2019/07/msg2.html

https://ci.debian.net/data/autopkgtest/testing/amd64/r/r-bioc-annotationhub/33053151/log.gz

RUNIT TEST PROTOCOL -- Fri Apr 21 23:47:54 2023
***
Number of test functions: 19
Number of errors: 0
Number of failures: 2


1 Test Suite :
AnnotationHub RUnit Tests - 19 test functions, 0 errors, 2 failures
FAILURE in test_accessors_setters: Error in 
checkIdentical(dates[length(dates)], hubDate(ah)) : FALSE


FAILURE in test_db_connections: Error in checkIdentical(ids2, 
AnnotationHub:::.db_uid(hub)) : FALSE



Test files with failing tests

   test_AnnotationHub-class.R
 test_accessors_setters

   test_db_utils.R
 test_db_connections


Error in BiocGenerics:::testPackage("AnnotationHub") :
  unit tests failed for package AnnotationHub
In addition: Warning message:
download failed
  hub path: ‘bogus/url’
  cache resource: ‘AHInvalid : 5012’
  reason: all(rtype == "web" | file.exists(fpath)) is not TRUE
Execution halted


OpenPGP_signature
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Source: r-bioc-annotationhub
Source-Version: 3.8.0+dfsg-1
Done: Andreas Tille 

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

Debian distribution maintenance software
pp.
Andreas Tille  (supplier of updated r-bioc-annotationhub 
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, 22 Jul 2023 12:39:15 +0200
Source: r-bioc-annotationhub
Architecture: source
Version: 3.8.0+dfsg-1
Distribution: unstable
Urgency: medium
Maintainer: Debian R Packages Maintainers 
Changed-By: Andreas Tille 
Closes: 1034852
Changes:
 r-bioc-annotationhub (3.8.0+dfsg-1) unstable; urgency=medium
 .
   * Rebuild against latest r-base
 Closes: #1034852
   * New upstream version
   * Standards-Version: 4.6.2 (routine-update)
   * dh-update-R to update Build-Depends (routine-update)
Checksums-Sha1:
 d261b59953cbd155ce8536e7b79795cf43964cd0 2396 
r-bioc-annotationhub_3.8.0+dfsg-1.dsc
 807ee9c96bda5ebf97f8af403930e249cf78469d 169996 
r-bioc-annotationhub_3.8.0+dfsg.orig.tar.xz
 1fd1becc3afd5290f217250e2adceb57d9ac3893 5548 
r-bioc-annotationhub_3.8.0+dfsg-1.debian.tar.xz
 5d3fe269436f37a4eb7932ae84d976c34bd6d342 23232 
r-bioc-annotationhub_3.8.0+dfsg-1_source.buildinfo
Checksums-Sha256:
 495fa333ebbead2b304522b4937f4a105e3b4176f20c5dbcbe5a2d86d8820050 2396 
r-bioc-annotationhub_3.8.0+dfsg-1.dsc
 d5159f0e4b8ae51516dfbb04fe003acf2a769fba794407f647548d3b7aeeb9a4 169996 
r-bioc-annotationhub_3.8.0+dfsg.orig.tar.xz
 2e2bdf93f8670721ed574ffb3c570ad544dbcd9eb73698cdb468aee83bc742c2 5548 
r-bioc-annotationhub_3.8.0+dfsg-1.debian.tar.xz
 2a85ada76f38f74955ce60a588910994d993d2733e8b09377e4fd51

Bug#1041499: meson: glib2.0 FTBFS on mips64el: "native build" but then "Can not run test applications in this cross environment"

[Simon McVittie]

On Wed, 19 Jul 2023 at 20:12:08 +0100, Simon McVittie wrote:
> On mips64el, Meson seems confused about whether this is a native or
> cross build. At first, it correctly reports that this is a native build:
...
> but then later, cc.run() fails:
> 
> > ../../../meson.build:1127:14: ERROR: Can not run test applications in this 
> > cross environment.

A workaround that seems generally-applicable, if you have a package
that needs to migrate before this is fixed, is to give `meson setup`
a --native-file with "needs_exe_wrapper = false" for native builds,
either on mips64el or always:
https://salsa.debian.org/gnome-team/gjs/-/commit/0e64684a809fb2c3996bde8b92d61c4f4aa9b4e0

(glib2.0 and gobject-introspection in unstable also have this workaround.)

smcv

Bug#1039714: fixed in gobject-introspection 1.76.1-3

[Thomas Uhle]

Hello Simon,

thanks for your support!

Cheers,

Thomas

Processed: affects 1041633

[Debian Bug Tracking System]

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

> affects 1041633 src:qgis
Bug #1041633 [src:cmake] cmake: FindPython.cmake returns 
/usr/local/lib/python3.11/dist-packages for Python_SITEARCH
Added indication that 1041633 affects src:qgis
> thanks
Stopping processing here.

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

Bug#1037851: Your mail

[Bastian Germann]

On Sat, 22 Jul 2023 11:36:10 +1000 Matthew Fernandez wrote:
Btw, why does this bug not appear when searching for bugs against the 
package? https://bugs.debian.org/cgi-bin/pkgreport.cgi?pkg=rumur


Because it is reported for the source package (replace ?pkg=rumur with 
?src=rumur).

Processed: src:libchemistry-opensmiles-perl: fails to migrate to testing for too long: causes autopkgtest regression

[Debian Bug Tracking System]

Processing control commands:

> close -1 0.8.6-1
Bug #1041691 [src:libchemistry-opensmiles-perl] 
src:libchemistry-opensmiles-perl: fails to migrate to testing for too long: 
causes autopkgtest regression
Marked as fixed in versions libchemistry-opensmiles-perl/0.8.6-1.
Bug #1041691 [src:libchemistry-opensmiles-perl] 
src:libchemistry-opensmiles-perl: fails to migrate to testing for too long: 
causes autopkgtest regression
Marked Bug as done

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

Bug#1041691: src:libchemistry-opensmiles-perl: fails to migrate to testing for too long: causes autopkgtest regression

[Paul Gevers]

Source: libchemistry-opensmiles-perl
Version: 0.8.5-1
Severity: serious
Control: close -1 0.8.6-1
Tags: sid trixie
User: release.debian@packages.debian.org
Usertags: out-of-sync

Dear maintainer(s),

The Release Team considers packages that are out-of-sync between testing 
and unstable for more than 30 days as having a Release Critical bug in 
testing [1]. Your package src:libchemistry-opensmiles-perl has been 
trying to migrate for 32 days [2]. Hence, I am filing this bug. The 
version in unstable breaks the (autopkg)test of smiles-scripts.


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


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


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


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


Paul

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



OpenPGP_signature
Description: OpenPGP digital signature

Bug#1037593: binutils-avr: ftbfs with GCC-13

[Gregor Riepl]

Upstream has fixed this via
https://sourceware.org/git/?p=binutils-gdb.git;a=commitdiff;h=5b429b870767e2107bcc7d5d849e04d6901b5912


Thanks for uploading the fix.

Unfortunately, it looks like the buildds are still choking on it:
https://buildd.debian.org/status/package.php?p=binutils-avr


# Convert hardlinks to softlinks
cd debian/binutils-avr/usr/lib/avr/bin && for f in *; do \
rm ../../../bin/avr-$f; \
ln -s ../lib/avr/bin/$f ../../../bin/avr-$f; \
done
/bin/sh: 1: cd: can't cd to debian/binutils-avr/usr/lib/avr/bin
make: *** [debian/rules:88: install] Error 2
dpkg-buildpackage: error: fakeroot debian/rules binary-arch subprocess 
returned exit status 2



Could you take a look?
Thanks!

Processed: src:golang-github-grpc-ecosystem-grpc-gateway: fails to migrate to testing for too long: FTBFS & autopkgtest regression

[Debian Bug Tracking System]

Processing control commands:

> close -1 1.16.0-2
Bug #1041688 [src:golang-github-grpc-ecosystem-grpc-gateway] 
src:golang-github-grpc-ecosystem-grpc-gateway: fails to migrate to testing for 
too long: FTBFS & autopkgtest regression
Marked as fixed in versions golang-github-grpc-ecosystem-grpc-gateway/1.16.0-2.
Bug #1041688 [src:golang-github-grpc-ecosystem-grpc-gateway] 
src:golang-github-grpc-ecosystem-grpc-gateway: fails to migrate to testing for 
too long: FTBFS & autopkgtest regression
Marked Bug as done
> block -1 by 1038870
Bug #1041688 {Done: Paul Gevers } 
[src:golang-github-grpc-ecosystem-grpc-gateway] 
src:golang-github-grpc-ecosystem-grpc-gateway: fails to migrate to testing for 
too long: FTBFS & autopkgtest regression
1041688 was not blocked by any bugs.
1041688 was not blocking any bugs.
Added blocking bug(s) of 1041688: 1038870

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

Bug#1041688: src:golang-github-grpc-ecosystem-grpc-gateway: fails to migrate to testing for too long: FTBFS & autopkgtest regression

[Paul Gevers]

Source: golang-github-grpc-ecosystem-grpc-gateway
Version: 1.6.4-2
Severity: serious
Control: close -1 1.16.0-2
Tags: sid trixie
User: release.debian@packages.debian.org
Usertags: out-of-sync
Control: block -1 by 1038870

Dear maintainer(s),

The Release Team considers packages that are out-of-sync between testing 
and unstable for more than 30 days as having a Release Critical bug in 
testing [1]. Your package src:golang-github-grpc-ecosystem-grpc-gateway 
has been trying to migrate for 31 days [2]. Hence, I am filing this bug. 
The version in unstable fails to build on 32 bit (bug #1038870) and 
fails its own autopkgtest.


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


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


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


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


Paul

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




OpenPGP_signature
Description: OpenPGP digital signature

Processed: src:accountsservice: fails to migrate to testing for too long: FTBFS

[Debian Bug Tracking System]

Processing control commands:

> close -1 23.13.9-2
Bug #1041687 [src:accountsservice] src:accountsservice: fails to migrate to 
testing for too long: FTBFS
The source 'accountsservice' and version '23.13.9-2' do not appear to match any 
binary packages
Marked as fixed in versions accountsservice/23.13.9-2.
Bug #1041687 [src:accountsservice] src:accountsservice: fails to migrate to 
testing for too long: FTBFS
Marked Bug as done
> block -1 by 1038865
Bug #1041687 {Done: Paul Gevers } [src:accountsservice] 
src:accountsservice: fails to migrate to testing for too long: FTBFS
1041687 was not blocked by any bugs.
1041687 was not blocking any bugs.
Added blocking bug(s) of 1041687: 1038865

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

Bug#1041687: src:accountsservice: fails to migrate to testing for too long: FTBFS

[Paul Gevers]

Source: accountsservice
Version: 22.08.8-6
Severity: serious
Control: close -1 23.13.9-2
Tags: sid trixie
User: release.debian@packages.debian.org
Usertags: out-of-sync
Control: block -1 by 1038865

Dear maintainer(s),

The Release Team considers packages that are out-of-sync between testing 
and unstable for more than 30 days as having a Release Critical bug in 
testing [1]. Your package src:accountsservice has been trying to migrate 
for 31 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 trixie, so 
it doesn't affect (old-)stable.


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


Paul

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



OpenPGP_signature
Description: OpenPGP digital signature