Bug#1041332: mrtg: modifies conffiles (policy 10.7.3): /etc/mrtg/mrtg.cfg

[Eriberto Mota]

> during a test with piuparts I noticed your package modifies conffiles.
> This is forbidden by the policy, see
> https://www.debian.org/doc/debian-policy/ch-files.html#configuration-files

Hi Andreas,

Thanks for your time and help.

I decided to change the current action from the debconf by a warning for
the final user. I will make it soon.

Regards,

Eriberto

Bug#1041836: root unable to write un-owned

[Paul Szabo]

Bummer. This last "echo x > /tmp/x" issue is probably the result of
protected_regular being set in kernel configs, see
https://docs.kernel.org/admin-guide/sysctl/fs.html#id12

Sorry about the noise. (Hangs head in shame.)

Cheers, Paul

Bug#1041836: root unable to write un-owned

[Paul Szabo]

Another oddity that should never happen: root cannot write file
that he does not own. Demonstration (root running bash):

  root# touch /tmp/x
  root# ls -l /tmp/x
  -rw-r--r-- 1 root root 0 Aug 10 09:39 /tmp/x
  root# echo a > /tmp/x
  root# chown 2:2 /tmp/x
  root# ls -l /tmp/x
  -rw-r--r-- 1 bin bin 2 Aug 10 09:39 /tmp/x
  root# echo b > /tmp/x
  -bash: /tmp/x: Permission denied
  root# chown 0:0 /tmp/x
  root# ls -l /tmp/x
  -rw-r--r-- 1 root root 2 Aug 10 09:39 /tmp/x
  root# echo c > /tmp/x

This issue seems to reproduce on all machines where I tried.
Quite possibly unrelated (so I may cop some flak) ... or maybe
these "impossible" happenings have a common cause?

Cheers, Paul

Bug#1041836: libc6 2.36-9+deb12u1 double free abort

[Paul Szabo]

Dear Aurelien,

I used LD_PRELOAD=libc_malloc_debug.so for MALLOC_CHECK_. With those
extra checks (tried all values of MALLOC_CHECK_ from 0 to 20), glibc
did not show any errors, suggesting that the bug is not in inetd.

The original poster said his issue shows on some hardware only.
I observed my issue on a wider range of CPUs: present on Xeon4309Y,
Xeon6326 and i7-8700, but not on i7-4790, i5-4570, i5-3470, N5105 or
x5-Z8350. Maybe the difference is in the RAM of the machine? Those
with my issue have 16GB or more, those without have 8GB or less. 

Cheers, Paul

Bug#1041118: marked as done (ska FTBFS with googletest 1.13.0)

[Debian Bug Tracking System]

Your message dated Wed, 09 Aug 2023 23:06:08 +
with message-id 
and subject line Bug#1041118: fixed in ska 1.0+dfsg-2.1
has caused the Debian Bug report #1041118,
regarding ska FTBFS with googletest 1.13.0
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.)


-- 
1041118: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1041118
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ska
Version: 1.0+dfsg-2
Severity: serious
Tags: ftbfs trixie sid

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/ska.html

...
In file included from googletest/include/gtest/gtest-message.h:57,
 from googletest/include/gtest/gtest-assertion-result.h:46,
 from googletest/include/gtest/gtest.h:64,
 from googletest/src/gtest-all.cc:38:
googletest/include/gtest/internal/gtest-port.h:270:2: error: #error C++ 
versions less than C++14 are not supported.
  270 | #error C++ versions less than C++14 are not supported.
  |  ^
...


This can be fixed by removing the -std=c++0x
in tests/Makefile
--- End Message ---
--- Begin Message ---
Source: ska
Source-Version: 1.0+dfsg-2.1
Done: Bastian Germann 

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

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

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

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

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Thu, 10 Aug 2023 00:11:51 +0200
Source: ska
Architecture: source
Version: 1.0+dfsg-2.1
Distribution: unstable
Urgency: medium
Maintainer: Debian Med Packaging Team 

Changed-By: Bastian Germann 
Closes: 1041118
Changes:
 ska (1.0+dfsg-2.1) unstable; urgency=medium
 .
   * Non-maintainer upload
   * Override CXXFLAGS to get rid of -std=c++0x (Closes: #1041118)
   * Clean googletest link
Checksums-Sha1:
 af11faefac93affab0329b9e5cc8c9b465462335 1768 ska_1.0+dfsg-2.1.dsc
 9ed9c33d5a4b39ca7b504b63ab96da4753a88e46 4300 ska_1.0+dfsg-2.1.debian.tar.xz
 471104c99ebf2f1c2af9d585b11214e4e3d4461f 5468 ska_1.0+dfsg-2.1_source.buildinfo
Checksums-Sha256:
 b2b6953bbaea0904d50ca35bc6012ea7ceca351375b22ce0ac900e4f4da1ee57 1768 
ska_1.0+dfsg-2.1.dsc
 bd17557e58ee7ff7adb19f27c9c7673373c8ccb5f67d60ab2b08a07255d7f07e 4300 
ska_1.0+dfsg-2.1.debian.tar.xz
 f9429ef316fe644c6ed0285d2c6f63a075863bdccbaa7fa7f5c5939a89210a31 5468 
ska_1.0+dfsg-2.1_source.buildinfo
Files:
 e173480176887874d1ffe93f51013772 1768 science optional ska_1.0+dfsg-2.1.dsc
 5271b9b121a87c72cf2ea74970335b2a 4300 science optional 
ska_1.0+dfsg-2.1.debian.tar.xz
 42e7c8c18562f6d331ef8197b55f3baf 5468 science optional 
ska_1.0+dfsg-2.1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQHEBAEBCgAuFiEEQGIgyLhVKAI3jM5BH1x6i0VWQxQFAmTUFeYQHGJhZ2VAZGVi
aWFuLm9yZwAKCRAfXHqLRVZDFJOTC/wPo0t7Csv85O5DI9JabqJIZ9N9otf7BGlo
6hapztAA90BrctJmNAHJDem36BJz6CUu6IgJ8zIEphoqd2v9RVL3wGiSyatmBxiY
PiYC11z2krpk3NXtd9SBuZhLtGapzrw/p9zqKAdt4v0RylwWiTOy8JGC9r4FXITn
P1v+tXJSfXc28SvVdgGtBwR2ZIyX98mpbTFviTkRByy7j3nw1QSvBtPOB15w1feS
dFxXZBuT8F7bhhKeJRYyf6FOu1nJp7pwofp6ijmlC/tndYTYk/mHYNQAxrn1JWAE
1SWxweN3grvRdVt5tL2UyGVSofaV0nXShQsVgafk7girzyyyXK83hqkM/1x+5Pio
KLgojirYqVV+5fQFJzWFUI4ePH/2nWo9NPxAguQcb+E5CnJGSKEIHNS0+GdcHrie
x/62X+pBctK4COByH8UNZHU0VFPAmcALXLI7KKTlqprx5jtJG02gqxh5r8ZoMPeG
KQIbNTYMvlvmZZBMNqhbrR8jEfkH3GY=
=bUBX
-END PGP SIGNATURE End Message ---

Bug#1037775: marked as done (mia: ftbfs with GCC-13)

[Debian Bug Tracking System]

Your message dated Wed, 09 Aug 2023 22:40:57 +
with message-id 
and subject line Bug#1037775: fixed in mia 2.4.7-12
has caused the Debian Bug report #1037775,
regarding mia: 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.)


-- 
1037775: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1037775
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:mia
Version: 2.4.7-11
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/mia_2.4.7-11_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

[...]
  |^~~~
/<>/mia/core/typedescr.hh:60:41: note: in definition of macro 
‘DECLARE_TYPE_DESCR’
   60 | struct EXPORT_CORE __type_descr { \
  | ^~~~
/<>/mia/core/typedescr.hh:101:40: error: template argument 1 is 
invalid
  101 | DECLARE_TYPE_DESCR(std::vector);
  |^
/<>/mia/core/typedescr.hh:60:41: note: in definition of macro 
‘DECLARE_TYPE_DESCR’
   60 | struct EXPORT_CORE __type_descr { \
  | ^~~~
/<>/mia/core/typedescr.hh:101:40: error: template argument 2 is 
invalid
  101 | DECLARE_TYPE_DESCR(std::vector);
  |^
/<>/mia/core/typedescr.hh:60:41: note: in definition of macro 
‘DECLARE_TYPE_DESCR’
   60 | struct EXPORT_CORE __type_descr { \
  | ^~~~
/<>/mia/core/typedescr.hh:60:45: error: template argument 1 is 
invalid
   60 | struct EXPORT_CORE __type_descr { \
  | ^
/<>/mia/core/typedescr.hh:101:1: note: in expansion of macro 
‘DECLARE_TYPE_DESCR’
  101 | DECLARE_TYPE_DESCR(std::vector);
  | ^~
/<>/mia/core/typedescr.hh:102:32: error: ‘uint64_t’ was not 
declared in this scope
  102 | DECLARE_TYPE_DESCR(std::vector);
  |^~~~
/<>/mia/core/typedescr.hh:60:41: note: in definition of macro 
‘DECLARE_TYPE_DESCR’
   60 | struct EXPORT_CORE __type_descr { \
  | ^~~~
/<>/mia/core/typedescr.hh:102:32: note: ‘uint64_t’ is defined in 
header ‘’; did you forget to ‘#include ’?
  102 | DECLARE_TYPE_DESCR(std::vector);
  |^~~~
/<>/mia/core/typedescr.hh:60:41: note: in definition of macro 
‘DECLARE_TYPE_DESCR’
   60 | struct EXPORT_CORE __type_descr { \
  | ^~~~
/<>/mia/core/typedescr.hh:102:40: error: template argument 1 is 
invalid
  102 | DECLARE_TYPE_DESCR(std::vector);
  |^
/<>/mia/core/typedescr.hh:60:41: note: in definition of macro 
‘DECLARE_TYPE_DESCR’
   60 | struct EXPORT_CORE __type_descr { \
  | ^~~~
/<>/mia/core/typedescr.hh:102:40: error: template argument 2 is 
invalid
  102 | DECLARE_TYPE_DESCR(std::vector);
  |^
/<>/mia/core/typedescr.hh:60:41: note: in definition of macro 
‘DECLARE_TYPE_DESCR’
   60 | struct EXPORT_CORE __type_descr { \
  | ^~~~
/<>/mia/core/typedescr.hh:60:45: error: template argument 1 is 
invalid
   60 | struct EXPORT_CORE __type_descr { \
  |   

Bug#1037776: marked as done (miaviewit: ftbfs with GCC-13)

[Debian Bug Tracking System]

Your message dated Wed, 09 Aug 2023 22:40:57 +
with message-id 
and subject line Bug#1037775: fixed in mia 2.4.7-12
has caused the Debian Bug report #1037775,
regarding miaviewit: 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.)


-- 
1037775: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1037775
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:miaviewit
Version: 1.0.5-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/miaviewit_1.0.5-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

[...]
/usr/include/mia-2.4/mia/3d/transform.hh:327:27: note: declared here
  327 |virtual C3DFVector apply(const C3DFVector& x) const  
__attribute__((deprecated));
  |   ^
trajects.cc:245:41: warning: ‘virtual mia::C3DFVector 
mia::C3DTransformation::apply(const mia::C3DFVector&) const’ is deprecated 
[-Wdeprecated-declarations]
  245 | direction = field->apply(Current.location);
  | ^~
/usr/include/mia-2.4/mia/3d/transform.hh:327:27: note: declared here
  327 |virtual C3DFVector apply(const C3DFVector& x) const  
__attribute__((deprecated));
  |   ^
trajects.cc: In member function ‘void TFieldTracerData::collect_result()’:
trajects.cc:435:47: warning: ‘virtual mia::C3DFVector 
mia::C3DTransformation::apply(const mia::C3DFVector&) const’ is deprecated 
[-Wdeprecated-declarations]
  435 | C3DFVector dir = field_->apply(ts.loc);
  |  ~^~~~
/usr/include/mia-2.4/mia/3d/transform.hh:327:27: note: declared here
  327 |virtual C3DFVector apply(const C3DFVector& x) const  
__attribute__((deprecated));
  |   ^
trajects.cc:448:47: warning: ‘virtual mia::C3DFVector 
mia::C3DTransformation::apply(const mia::C3DFVector&) const’ is deprecated 
[-Wdeprecated-declarations]
  448 | l.norm = field_->apply(l.loc).norm();
  |  ~^~~
/usr/include/mia-2.4/mia/3d/transform.hh:327:27: note: declared here
  327 |virtual C3DFVector apply(const C3DFVector& x) const  
__attribute__((deprecated));
  |   ^
trajects.cc:456:47: warning: ‘virtual mia::C3DFVector 
mia::C3DTransformation::apply(const mia::C3DFVector&) const’ is deprecated 
[-Wdeprecated-declarations]
  456 | l.norm = field_->apply(l.loc).norm();
  |  ~^~~
/usr/include/mia-2.4/mia/3d/transform.hh:327:27: note: declared here
  327 |virtual C3DFVector apply(const C3DFVector& x) const  
__attribute__((deprecated));
  |   ^
glvector.cc: In constructor ‘TGLVectorList::TGLVectorList(const std::string&, 
const TColor&, const TColor&, const TVertexList&, const 
mia::C3DTransformation&, GL2DHTexture*)’:
glvector.cc:34:44: warning: ‘virtual mia::C3DFVector 
mia::C3DTransformation::apply(const mia::C3DFVector&) const’ is deprecated 
[-Wdeprecated-declarations]
   34 | C3DFVector v = deform.apply(*i);
  |^~~~
In file included from /usr/include/mia-2.4/mia/3d/fullcost.hh:24,
 from /usr/include/mia-2.4/mia/3d.hh:30,
 from /usr/include/mia-2.4/mia.hh:26,
 from 

Bug#1041118: ska FTBFS with googletest 1.13.0

[Bastian Germann]

I am uploading a NMU to fix this. The debdiff is attached.diff -Nru ska-1.0+dfsg/debian/changelog ska-1.0+dfsg/debian/changelog
--- ska-1.0+dfsg/debian/changelog   2022-10-03 07:39:45.0 +0200
+++ ska-1.0+dfsg/debian/changelog   2023-08-10 00:11:51.0 +0200
@@ -1,3 +1,11 @@
+ska (1.0+dfsg-2.1) unstable; urgency=medium
+
+  * Non-maintainer upload
+  * Override CXXFLAGS to get rid of -std=c++0x (Closes: #1041118)
+  * Clean googletest link
+
+ -- Bastian Germann   Thu, 10 Aug 2023 00:11:51 +0200
+
 ska (1.0+dfsg-2) unstable; urgency=medium
 
   * Packaging update
diff -Nru ska-1.0+dfsg/debian/clean ska-1.0+dfsg/debian/clean
--- ska-1.0+dfsg/debian/clean   1970-01-01 01:00:00.0 +0100
+++ ska-1.0+dfsg/debian/clean   2023-08-10 00:11:51.0 +0200
@@ -0,0 +1 @@
+tests/googletest
diff -Nru ska-1.0+dfsg/debian/rules ska-1.0+dfsg/debian/rules
--- ska-1.0+dfsg/debian/rules   2022-10-03 07:39:45.0 +0200
+++ ska-1.0+dfsg/debian/rules   2023-08-10 00:11:51.0 +0200
@@ -1,16 +1,23 @@
 #!/usr/bin/make -f
 
 # DH_VERBOSE := 1
+DPKG_EXPORT_BUILDFLAGS = 1
+include /usr/share/dpkg/buildflags.mk
+
 export LC_ALL=C.UTF-8
 
 %:
dh $@
 
+override_dh_auto_build:
+   dh_auto_build -- CXXFLAGS+=-std=c++17
+
 override_dh_auto_install:
# do not use broken Makefile which forces /usr/local/bin
 
 override_dh_auto_test:
 ifeq (,$(filter nocheck,$(DEB_BUILD_OPTIONS)))
-   cd tests && ln -s /usr/src/googletest/googletest && make && \
+   cd tests && ln -s /usr/src/googletest/googletest && \
+   $(MAKE) CXXFLAGS+=-std=c++17 && \
./general_unittest && ./kmers_unittest && ./DNA_unittest
 endif

Processed: Re: [request-tracker-maintainers] Bug#1042530

[Debian Bug Tracking System]

Processing control commands:

> tags -1 +upstream
Bug #1042530 [src:request-tracker4] request-tracker5: Include ckeditor 
minimified
Added tag(s) upstream.
> severity -1 normal
Bug #1042530 [src:request-tracker4] request-tracker5: Include ckeditor 
minimified
Severity set to 'normal' from 'serious'

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

Bug#1042530: [request-tracker-maintainers] Bug#1042530

[Ángel]

Control: tags -1 +upstream
Control: severity -1 normal

Resetting severity to normal, as it was a result of the FTBFS. There's
an old ckeditor version bundled by upstream. It's not confirmed if the
CVE can be exploited in RT.
Should be fixed, but not a release-critical issue.

> 

Processed: Re: [request-tracker-maintainers] Bug#1042527: request-tracker5: Include ckeditor minimified

[Debian Bug Tracking System]

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

> tags 1042527 +upstream
Bug #1042527 [src:request-tracker5] request-tracker5: Include ckeditor 
minimified
Added tag(s) upstream.
> severity 1042527 normal
Bug #1042527 [src:request-tracker5] request-tracker5: Include ckeditor 
minimified
Severity set to 'normal' from 'serious'
>
End of message, stopping processing here.

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

Bug#1042527: [request-tracker-maintainers] Bug#1042527: request-tracker5: Include ckeditor minimified

[Ángel]

Control: tags +upstream
Control: severity normal

Resetting severity to normal, as it was a result of the FTBFS. There's
an old ckeditor version bundled by upstream. It's not confirmed if the
CVE can be exploited in RT.
Should be fixed, but not a release-critical issue.

Bug#1043250: marked as done (tzdata: bring back top-level UTC)

[Debian Bug Tracking System]

Your message dated Wed, 09 Aug 2023 21:53:46 +
with message-id 
and subject line Bug#1043250: fixed in tzdata 2023c-10
has caused the Debian Bug report #1043250,
regarding tzdata: bring back top-level UTC
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.)


-- 
1043250: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1043250
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: tzdata
Version: 2023c-8
Severity: important
X-Debbugs-Cc: t...@mirbsd.de

Please bring back at the *very* least the top-level UTC symlink,
as TZ=UTC is used in *so* many places to get UTC it’s not funny.

A second candidate, although less used recently, is the top-level
GMT symlink.

These are bound to be hardcoded in so many places, and Etc/UTC is
*not* a substitute, nor is running that without the files (in some
corner cases).


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

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

Versions of packages tzdata depends on:
ii  debconf [debconf-2.0]  1.5.82

tzdata recommends no packages.

tzdata suggests no packages.

-- debconf information:
* tzdata/Zones/Etc: UTC
* tzdata/Areas: Europe
  tzdata/Zones/Antarctica:
  tzdata/Zones/Arctic:
  tzdata/Zones/Australia:
  tzdata/Zones/US:
  tzdata/Zones/Pacific:
  tzdata/Zones/America:
  tzdata/Zones/Asia:
* tzdata/Zones/Europe: Berlin
  tzdata/Zones/SystemV:
  tzdata/Zones/Africa:
  tzdata/Zones/Atlantic:
  tzdata/Zones/Indian:
--- End Message ---
--- Begin Message ---
Source: tzdata
Source-Version: 2023c-10
Done: Benjamin Drung 

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

Debian distribution maintenance software
pp.
Benjamin Drung  (supplier of updated tzdata 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: Wed, 09 Aug 2023 23:10:14 +0200
Source: tzdata
Architecture: source
Version: 2023c-10
Distribution: unstable
Urgency: medium
Maintainer: GNU Libc Maintainers 
Changed-By: Benjamin Drung 
Closes: 1043250
Changes:
 tzdata (2023c-10) unstable; urgency=medium
 .
   * Partially revert 2023c-8: Move top-level timezones like UTC and CET back to
 tzdata. Only the old or merged timezones mentioned in the upstream backward
 file stay in tzdata-legacy (Closes: #1043250, LP: #2030684)
Checksums-Sha1:
 a2c0aea229b7392739bdf2d88164cf86e75fc74b 2259 tzdata_2023c-10.dsc
 5dfba627d1d2840b07e57e9f2a6658814a96abfc 121516 tzdata_2023c-10.debian.tar.xz
 9209e1de3a4f92e9c426abd330e35eaee8fcdcba 6579 tzdata_2023c-10_amd64.buildinfo
Checksums-Sha256:
 534f36efe6ec80a8dafb2a779a88d8c2f033befb794cbb168747269a0095f388 2259 
tzdata_2023c-10.dsc
 5e82cd0a328f665b95c5456a024164f255b12b460c5b1c6f10702cba155f75f7 121516 
tzdata_2023c-10.debian.tar.xz
 54f15cd0c301c779081a4052d822b90836fafffeec9d51c2713b7da47643ab28 6579 
tzdata_2023c-10_amd64.buildinfo
Files:
 91b19df3ba93a7706d505e5048c92868 2259 localization required tzdata_2023c-10.dsc
 34eb3c55c050864f476d96723c63b11f 121516 localization required 
tzdata_2023c-10.debian.tar.xz
 8fd42435a32a7c6855ca56a3604aa779 6579 localization required 
tzdata_2023c-10_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQGzBAEBCgAdFiEEJvtDgpxjkjCIVtam+C8H+466LVkFAmTUAsoACgkQ+C8H+466
LVnb2wwAvRlGfXGIQpChaBQuS84Jj4wk6Whb/gGtz9TsyLKED3VQSvPZQoZWZkDW
2uIY5AL5QVzWncUVzaticOkchpqgA8y/J4j4lirceCfcFUFJuqAfiX4kVuj1WJnd
rNt2OnBiUMx9w6nE+qqk6LzrxBF770lg1xwEsSz2pqydcp5bgSt695CzUpVB0536
HBT1oYz7/sIvBLChXU+cvPHHfTHa1kgOOAXZkPpSwJM+6VZQyCZ9RydmOxx9pf1S
Qgz7uAuCFNrUelkRinQ95FLFJe1MUWLH06HCCrbT3l70yRfw92SmhLVKUUZcHngJ
Zy3joslJ68iQLGtl9VJ48CclRkpTQitOCJZo7ZJj4pF4n0oGDbFCXuW6FCI013eE
+wv7Aq5rS9kcinlTUl8LbCNJkgP1ELUgkwX+SlY3OJaxWnRejRYhSRAQPJNsfiB7

Bug#1041836: libc6 2.36-9+deb12u1 double free abort

[Aurelien Jarno]

Hi,

What you reported seems unrelated to the original issue. It's better to
open a new bug if you believe there is in issue in glibc.

On 2023-08-09 10:46, Paul Szabo wrote:
> Maybe related: seems that the default for "mcheck" or MALLOC_CHECK_ has
> changed.
> 
> I observe an oddity. I only noticed this recently, with libc6 version
> 2.36-9+deb12u1; reverting to previous 2.36-9 did not seem to help.
> 
> The issue. Sending SIGHUP to the inetd(8) process should cause it to
> re-load its configuration, but instead it elicits
> 
>   free(): double free detected in tcache 2
> 
> and an abort. This is easiest seen (after "systemctl stop inetd") with
> 
>   root# inetd -d -i & sleep 1; kill -HUP $!; sleep 1; jobs
>   [1] 2431
>   ADD: ident proto=tcp4, wait.max=1.256 user:group=identd:(default) builtin=0 
> server=/usr/sbin/identd
>   free(): double free detected in tcache 2
>   [1]+  Aborted inetd -d -i
>   root# 

This is very likely a bug in inetd. There is no default value in
MALLOC_CHECK_, by default a fast memory allocator which is not tolerant
against simple errors is used, and thus just aborts in that case.

> Sanity(?) is restored by using MALLOC_CHECK_=0 (needs LD_PRELOAD):
> 
>   root# LD_PRELOAD=libc_malloc_debug.so MALLOC_CHECK_=0 inetd -d -i & sleep 
> 1; kill -HUP $!; sleep 1; jobs; kill $!; sleep 1; jobs
>   [1] 2437
>   ADD: ident proto=tcp4, wait.max=1.256 user:group=identd:(default) builtin=0 
> server=/usr/sbin/identd
>   REDO: ident proto=tcp4, wait.max=1.256 user:group=identd:(default) 
> builtin=0 server=/usr/sbin/identd
>   [1]+  Running LD_PRELOAD=libc_malloc_debug.so 
> MALLOC_CHECK_=0 inetd -d -i &
>   [1]+  DoneLD_PRELOAD=libc_malloc_debug.so 
> MALLOC_CHECK_=0 inetd -d -i
>   root# 
> 
> To compound the oddity, the value of MALLOC_CHECK_ or even its presence
> seems ignored, just the LD_PRELOAD=libc_malloc_debug.so "fixes" the
> issue.

Since glibc 2.34, the debugging features in malloc such as the
MALLOC_CHECK_ environment variable are not built-in anymore and require
to preload the libc_malloc_debug.so library. This allows one to change
the level of checks through the MALLOC_CHECK_ environment variable.

Regards
Aurelien

-- 
Aurelien Jarno  GPG: 4096R/1DDD8C9B
aurel...@aurel32.net http://aurel32.net

Bug#1043250: marked as done (tzdata: bring back top-level UTC)

[Debian Bug Tracking System]

Your message dated Wed, 09 Aug 2023 20:59:01 +
with message-id 
and subject line Bug#1043250: fixed in tzdata 2023c-9
has caused the Debian Bug report #1043250,
regarding tzdata: bring back top-level UTC
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.)


-- 
1043250: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1043250
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: tzdata
Version: 2023c-8
Severity: important
X-Debbugs-Cc: t...@mirbsd.de

Please bring back at the *very* least the top-level UTC symlink,
as TZ=UTC is used in *so* many places to get UTC it’s not funny.

A second candidate, although less used recently, is the top-level
GMT symlink.

These are bound to be hardcoded in so many places, and Etc/UTC is
*not* a substitute, nor is running that without the files (in some
corner cases).


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

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

Versions of packages tzdata depends on:
ii  debconf [debconf-2.0]  1.5.82

tzdata recommends no packages.

tzdata suggests no packages.

-- debconf information:
* tzdata/Zones/Etc: UTC
* tzdata/Areas: Europe
  tzdata/Zones/Antarctica:
  tzdata/Zones/Arctic:
  tzdata/Zones/Australia:
  tzdata/Zones/US:
  tzdata/Zones/Pacific:
  tzdata/Zones/America:
  tzdata/Zones/Asia:
* tzdata/Zones/Europe: Berlin
  tzdata/Zones/SystemV:
  tzdata/Zones/Africa:
  tzdata/Zones/Atlantic:
  tzdata/Zones/Indian:
--- End Message ---
--- Begin Message ---
Source: tzdata
Source-Version: 2023c-9
Done: Benjamin Drung 

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

Debian distribution maintenance software
pp.
Benjamin Drung  (supplier of updated tzdata package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Tue, 08 Aug 2023 12:00:00 +0200
Source: tzdata
Architecture: source
Version: 2023c-9
Distribution: unstable
Urgency: medium
Maintainer: GNU Libc Maintainers 
Changed-By: Benjamin Drung 
Closes: 1043250
Changes:
 tzdata (2023c-9) unstable; urgency=medium
 .
   * Move top-level UTC timezone back to tzdata (Closes: #1043250, LP: #2030684)
Checksums-Sha1:
 6ebbc061fbb096598b378361744302c66a6c13ba 2255 tzdata_2023c-9.dsc
 d455f131f27a6171dd5576313765495eba5583e6 121284 tzdata_2023c-9.debian.tar.xz
 23db91ee449e3e92b6c6dd51e58b4803a49f011b 6569 tzdata_2023c-9_amd64.buildinfo
Checksums-Sha256:
 09931281eb57e3a66ab19a4e596c5d0295a9bbf2132eeff76ee3c68090005659 2255 
tzdata_2023c-9.dsc
 039af005e57161506e9550d2e0e4ca1376da6376d2f3f270da607ac24b6e7c82 121284 
tzdata_2023c-9.debian.tar.xz
 15201d47b9f29704134028320203eddcba8399d335479f7565119635cac33c6a 6569 
tzdata_2023c-9_amd64.buildinfo
Files:
 a38a9bb5f09238dfcf7ac7b48d700139 2255 localization required tzdata_2023c-9.dsc
 ad514823d4fa2c2ec5626244cb0b9601 121284 localization required 
tzdata_2023c-9.debian.tar.xz
 ac8ccfa1aad298c621fe853350d4b2d3 6569 localization required 
tzdata_2023c-9_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQGzBAEBCgAdFiEEJvtDgpxjkjCIVtam+C8H+466LVkFAmTT8dAACgkQ+C8H+466
LVkE0wv+MyWt/X8bP0t4iz6oQZ8uiogMtDWifq2WbMWzugMMybOGqvXFHO5Lz3ZZ
mAd0FuJrlVsLENGsEzc28X9CN0d+gMzE79L7dZKQuuEtv3Isio/rRyUpZwEGdxbc
aFa35jC8m+UKjeCstOqt12Q8LLbiiy5OcfcfbJ56V5rRt2isc66WXapWJp4nH8Af
VdOVWknNOrTn4GAY+Jbx/xuXumPCK8somiQO2TZOAnp2IUkP4+rET8AsknoEKz7X
+GQOMxjwXltMN4inWTkdAsJkgsMWbYVaASuldwTHLNHUG7PiG8sHfQ4xuyCPBDc5
jNUqMX1zFE2WXlIQnJW8pWr9oHSGKSJNbQjIvKwnQ9jCJYA5cQ2vJeSyXNLNYNFs
nvFp00KmI5xZ+vzKk/SjGbOWGxEamNG9F7PHJUGVdBElax8QNgBIpXlqHZNVZ3Mf
u6IqmxDKMLDlefzj7PfAFP6JJKCxb+Bg4KqFO7Z5y1SLHfp+ujWog782MKXX8Mc0
gs+r/dIQ
=kZwA
-END PGP SIGNATURE End Message ---

Processed: src:rust-log: fails to migrate to testing for too long: unresolved RC issue

[Debian Bug Tracking System]

Processing control commands:

> close -1 0.4.19-2
Bug #1043386 [src:rust-log] src:rust-log: fails to migrate to testing for too 
long: unresolved RC issue
Marked as fixed in versions rust-log/0.4.19-2.
Bug #1043386 [src:rust-log] src:rust-log: fails to migrate to testing for too 
long: unresolved RC issue
Marked Bug as done
> block -1 by 1040835
Bug #1043386 {Done: Paul Gevers } [src:rust-log] 
src:rust-log: fails to migrate to testing for too long: unresolved RC issue
1043386 was not blocked by any bugs.
1043386 was not blocking any bugs.
Added blocking bug(s) of 1043386: 1040995, 1040837, and 1040835

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

Bug#1043386: src:rust-log: fails to migrate to testing for too long: unresolved RC issue

[Paul Gevers]

Source: rust-log
Version: 0.4.17-3
Severity: serious
Control: close -1 0.4.19-2
Tags: sid trixie
User: release.debian@packages.debian.org
Usertags: out-of-sync
Control: block -1 by 1040835

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:rust-log has been trying to migrate for 31 
days [2]. Hence, I am filing this bug. The package is blocked by bug 
1040835 and the associated (I guess) autopkgtest regressions and 
uninstallability it causes.


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=rust-log



OpenPGP_signature
Description: OpenPGP digital signature

Bug#1043383: python-pcre: depends on obsolete pcre3 library

[Bastian Germann]

Source: python-pcre
Severity: serious
Version: 0.7-1
User: matthew-pcre...@debian.org
Usertags: obsolete-pcre3

Dear maintainer,

When the pcre3 -> pcre2 mass bug was filed, python-pcre had not yet been 
in the archive. I am filing this (edited copy) after the fact:


Your package still depends on the old, obsolete PCRE3 libraries
(i.e. libpcre3-dev). This has been end of life for a while now, and
upstream do not intend to fix any further bugs in it. Accordingly, we
would like to remove the pcre3 libraries from Debian.

The newer PCRE2 library was first released in 2015, and has been in
Debian since stretch. Upstream's documentation for PCRE2 is available
here: https://pcre.org/current/doc/html/

Many large projects that use PCRE have made the switch now (e.g. git,
php); it does involve some work, but we are now at the stage where
PCRE3 should not be used, particularly if it might ever be exposed to
untrusted input.

This mass bug filing was discussed on debian-devel@ in
https://lists.debian.org/debian-devel/2021/11/msg00176.html

A possible replacement for your package is at
https://github.com/grtetrault/pcre2.py

Thanks,
Bastian

Processed: Bug#1043250 marked as pending in tzdata

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1043250 [tzdata] tzdata: bring back top-level UTC
Ignoring request to alter tags of bug #1043250 to the same tags previously set

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

Bug#1043250: marked as pending in tzdata

[Benjamin Drung]

Control: tag -1 pending

Hello,

Bug #1043250 in tzdata 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/glibc-team/tzdata/-/commit/ac74776a7550d4ea4af8252e50c0017da9cc79a5


Move all timezones back that are not in backward file

In addition to moving UTC back from `tzdata-legacy` to `tzdata` also
move those timezones back that are not in the `backward` file. Only the
old or merged timezone names mentioned in `backward` should have been
moved to tzdata-legacy.

Closes: #1043250
LP: #2030684
Signed-off-by: Benjamin Drung 


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1043250

Bug#1042025: thrift: FTBFS: dh_auto_test: error: make -j1 check "TESTSUITEFLAGS=-j1 --verbose" VERBOSE=1 returned exit code 2

[GCS]

Control: forwarded -1 https://issues.apache.org/jira/browse/THRIFT-5680

Hi Christoph,

On Wed, Aug 9, 2023 at 8:27 PM Christoph Berg  wrote:
> > > (./testapplicationexception:892843): GLib-CRITICAL **: 07:16:59.134: Did 
> > > not see expected message GLib-GObject-WARNING **: value*out of range*type*
> > > not ok /testapplicationexception/Properties/test - 
> > > GLib-GObject-FATAL-CRITICAL: value "-1" of type 'gint' is invalid or out 
> > > of range for property 'type' of type 'gint'
> > > Bail out!
[...]
> Fwiw, there is a new 0.18.1 upstream version. Perhaps that works
> better.
 It is already packaged for experimental and has the same build
problem. Upstream knows this bug [1], assigned major priority to it
but has not touched the issue since february.

Regards,
Laszlo/GCS
[1] https://issues.apache.org/jira/browse/THRIFT-5680

Processed: Re: Bug#1042025: thrift: FTBFS: dh_auto_test: error: make -j1 check "TESTSUITEFLAGS=-j1 --verbose" VERBOSE=1 returned exit code 2

[Debian Bug Tracking System]

Processing control commands:

> forwarded -1 https://issues.apache.org/jira/browse/THRIFT-5680
Bug #1042025 [src:thrift] thrift: FTBFS: dh_auto_test: error: make -j1 check 
"TESTSUITEFLAGS=-j1 --verbose" VERBOSE=1 returned exit code 2
Set Bug forwarded-to-address to 
'https://issues.apache.org/jira/browse/THRIFT-5680'.

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

Processed: amd64-microcode: Followups for 4th Gen AMD EPYC processors for CVE-2023-20569 / AMD Inception

[Debian Bug Tracking System]

Processing control commands:

> found -1 3.20230414.1
Bug #1043381 [src:amd64-microcode] amd64-microcode: Followups for 4th Gen AMD 
EPYC processors for CVE-2023-20569 / AMD Inception
Marked as found in versions amd64-microcode/3.20230414.1.
> found -1 3.20230719.1~deb12u1
Bug #1043381 [src:amd64-microcode] amd64-microcode: Followups for 4th Gen AMD 
EPYC processors for CVE-2023-20569 / AMD Inception
Marked as found in versions amd64-microcode/3.20230719.1~deb12u1.
> found -1 3.20191218.1
Bug #1043381 [src:amd64-microcode] amd64-microcode: Followups for 4th Gen AMD 
EPYC processors for CVE-2023-20569 / AMD Inception
Marked as found in versions amd64-microcode/3.20191218.1.
> found -1 3.20230719.1~deb11u1
Bug #1043381 [src:amd64-microcode] amd64-microcode: Followups for 4th Gen AMD 
EPYC processors for CVE-2023-20569 / AMD Inception
Marked as found in versions amd64-microcode/3.20230719.1~deb11u1.

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

Bug#1043381: amd64-microcode: Followups for 4th Gen AMD EPYC processors for CVE-2023-20569 / AMD Inception

[Salvatore Bonaccorso]

Source: amd64-microcode
Version: 3.20230719.1
Severity: grave
Tags: security upstream
X-Debbugs-Cc: car...@debian.org, Debian Security Team 
Control: found -1 3.20230414.1
Control: found -1 3.20230719.1~deb12u1  
Control: found -1 3.20191218.1
Control: found -1 3.20230719.1~deb11u1

Hi Henrique,

From
https://www.amd.com/en/resources/product-security/bulletin/amd-sb-7005.html
we did fortunately covered the 3rd Gen AMD EPYC processors microcode
updates for CVE-2023-20569 already with the previous done update:

amd64-microcode (3.20230719.1) unstable; urgency=high

  * Update package data from linux-firmware 20230625-39-g59fbffa9:
* Fixes for CVE-2023-20593 "Zenbleed" on AMD Zen2 processors
  (closes: #1041863)
* New Microcode patches:
  + Family=0x17 Model=0xa0 Stepping=0x00: Patch=0x08a8
* Updated Microcode patches:
  + Family=0x17 Model=0x31 Stepping=0x00: Patch=0x0830107a
  + Family=0x19 Model=0x01 Stepping=0x00: Patch=0x0a001079
  + Family=0x19 Model=0x01 Stepping=0x01: Patch=0x0a0011d1
  + Family=0x19 Model=0x01 Stepping=0x02: Patch=0x0a001234
  * README: update for new release

 -- Henrique de Moraes Holschuh   Mon, 24 Jul 2023 13:07:34 
-0300

(and so in {bookworm,bullseye,buster}-security as well).

There was a microcode followup today as
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/?id=f2eb058afc57348cde66852272d6bf11da1eef8f
which followups for the 4th Gen AMD EPYC processors, Genoa
(Family=0x19 Model=0x11) and Bergamo (Family=0x19 Model=0xa0).

Regards,
Salvatore

Bug#1042025: thrift: FTBFS: dh_auto_test: error: make -j1 check "TESTSUITEFLAGS=-j1 --verbose" VERBOSE=1 returned exit code 2

[Christoph Berg]

Re: Lucas Nussbaum
> Version: 0.17.0-2

> > (./testapplicationexception:892843): GLib-CRITICAL **: 07:16:59.134: Did 
> > not see expected message GLib-GObject-WARNING **: value*out of range*type*
> > not ok /testapplicationexception/Properties/test - 
> > GLib-GObject-FATAL-CRITICAL: value "-1" of type 'gint' is invalid or out of 
> > range for property 'type' of type 'gint'
> > Bail out!
> > /bin/bash: line 6: 892843 Trace/breakpoint trap   ${dir}$tst
> > FAIL: testapplicationexception
> > TAP version 13
> > # random seed: R02Sdadbad636988fc61fb41629b59ecfdd6

Fwiw, there is a new 0.18.1 upstream version. Perhaps that works
better.

Christoph

Bug#1041131: marked as done (prometheus-cpp FTBFS with googletest 1.13.0)

[Debian Bug Tracking System]

Your message dated Wed, 9 Aug 2023 19:51:20 +0200
with message-id 
and subject line FTBFS issue is fixed
has caused the Debian Bug report #1041131,
regarding prometheus-cpp FTBFS with googletest 1.13.0
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.)


-- 
1041131: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1041131
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: prometheus-cpp
Version: 1.0.1-1
Severity: serious
Tags: ftbfs trixie sid

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/prometheus-cpp.html

...
CMakeFiles/gmock_main.dir/usr/src/googletest/googlemock/src/gmock_main.cc.o -MF 
CMakeFiles/gmock_main.dir/usr/src/googletest/googlemock/src/gmock_main.cc.o.d 
-o CMakeFiles/gmock_main.dir/usr/src/googletest/googlemock/src/gmock_main.cc.o 
-c /usr/src/googletest/googlemock/src/gmock_main.cc
In file included from 
/usr/src/googletest/googlemock/include/gmock/internal/gmock-port.h:57,
 from 
/usr/src/googletest/googlemock/include/gmock/internal/gmock-internal-utils.h:49,
 from 
/usr/src/googletest/googlemock/include/gmock/gmock-actions.h:145,
 from /usr/src/googletest/googlemock/include/gmock/gmock.h:56,
 from /usr/src/googletest/googlemock/src/gmock_main.cc:32:
/usr/src/googletest/googletest/include/gtest/internal/gtest-port.h:270:2: 
error: #error C++ versions less than C++14 are not supported.
  270 | #error C++ versions less than C++14 are not supported.
  |  ^
...


This can be fixed by configuring with -DOVERRIDE_CXX_STANDARD_FLAGS=OFF
--- End Message ---
--- Begin Message ---

Package: prometheus-cpp
Version: 1.0.2-1

I had some trouble with the upload because the package missed a 
pristine-tar config.


The build issue now fixed in sid and testing.

Thanks,
Gregor--- End Message ---

Bug#1043377: sopt: FTBFS during tests on mips64el -- communicator (SEGFAULT)

[Bastian Germann]

Source: sopt
Version: 3.0.1+dfsg-2
Severity: serious

On mips64el, a test fails due to a segfault:

test 19
  Start 19: communicator

19: Test command: /usr/bin/mpiexec "-n" "1" 
"/<>/obj-mips64el-linux-gnuabi64/cpp/tests/test_communicator"
19: Working Directory: 
/<>/obj-mips64el-linux-gnuabi64/cpp/tests

19: Test timeout computed to be: 1000
17: [2023-08-09 15:28:13.169] [sopt] [debug] Starting bisection method 
over x ∈ [-1.5, 0], to estimate f(x) = 1
17: [2023-08-09 15:28:13.170] [sopt] [debug] Starting bisection method 
over x ∈ [0, 1.5], to estimate f(x) = 1
17: [2023-08-09 15:28:13.258] [sopt] [debug] Starting calculation of 
credible interval: 8 x 8 grid.
17: [2023-08-09 15:28:13.258] [sopt] [debug] Grid pixel (0, 0): [0, 16) 
x [0, 16)
17: [2023-08-09 15:28:13.266] [sopt] [debug] Starting bisection method 
over x ∈ [-16384, 0], to estimate f(x) = 1

19: [mipsel-osuosl-03:2434331] *** Process received signal ***
19: [mipsel-osuosl-03:2434331] Signal: Segmentation fault (11)
19: [mipsel-osuosl-03:2434331] Signal code: Address not mapped (1)
19: [mipsel-osuosl-03:2434331] Failing at address: (nil)
19: [mipsel-osuosl-03:2434331] *** End of error message ***
16/22 Test #19: communicator .***Exception: SegFault 
 0.23 sec

[mipsel-osuosl-03:2434331] *** Process received signal ***
[mipsel-osuosl-03:2434331] Signal: Segmentation fault (11)
[mipsel-osuosl-03:2434331] Signal code: Address not mapped (1)
[mipsel-osuosl-03:2434331] Failing at address: (nil)
[mipsel-osuosl-03:2434331] *** End of error message ***

Bug#1043061: marked as done (fenics-dolfinx: requires source-only upload for testing migration)

[Debian Bug Tracking System]

Your message dated Wed, 09 Aug 2023 16:34:37 +
with message-id 
and subject line Bug#1043061: fixed in fenics-dolfinx 1:0.6.0-7
has caused the Debian Bug report #1043061,
regarding fenics-dolfinx: requires source-only upload for testing migration
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.)


-- 
1043061: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1043061
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: fenics-dolfinx
Version: 1:0.6.0-6
Severity: serious
X-Debbugs-Cc: sramac...@debian.org

Issues preventing migration:
∙ ∙ Not built on buildd: arch all binaries uploaded by dparsons, a new 
source-only upload is needed to allow migration

Cheers
-- 
Sebastian Ramacher
--- End Message ---
--- Begin Message ---
Source: fenics-dolfinx
Source-Version: 1:0.6.0-7
Done: Drew Parsons 

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

Debian distribution maintenance software
pp.
Drew Parsons  (supplier of updated fenics-dolfinx 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: Wed, 09 Aug 2023 17:45:04 +0200
Source: fenics-dolfinx
Architecture: source
Version: 1:0.6.0-7
Distribution: unstable
Urgency: medium
Maintainer: Debian Science Team 

Changed-By: Drew Parsons 
Closes: 1043061
Changes:
 fenics-dolfinx (1:0.6.0-7) unstable; urgency=medium
 .
   * source-only upload for migrating to testing. Closes: #1043061.
Checksums-Sha1:
 bdbb2cd100f2e72f9f587215439e01f42ed4bf29 3894 fenics-dolfinx_0.6.0-7.dsc
 d4adb988501fb647a8b6a8f2ed45037add918fe4 45700 
fenics-dolfinx_0.6.0-7.debian.tar.xz
 11566d24514248342df6957093b496216a5cb38c 18905 
fenics-dolfinx_0.6.0-7_source.buildinfo
Checksums-Sha256:
 8ad71e3a46f1cb4bec5d88e20e1ad1310ec4e86b4db548c51b7434f06576ce66 3894 
fenics-dolfinx_0.6.0-7.dsc
 617416ddc77e041767e872db85e4f833873f68cf17dc0f6a957e131493894261 45700 
fenics-dolfinx_0.6.0-7.debian.tar.xz
 f7a97b0022b5f648bdd3b7d526aebc8dcf96ee7958718d16bc0e0e9ab71af1e8 18905 
fenics-dolfinx_0.6.0-7_source.buildinfo
Files:
 26e57a5e71be9b59fedd070a03dddfcf 3894 math optional fenics-dolfinx_0.6.0-7.dsc
 a371fde22cd8a274106e9f14959ee9d7 45700 math optional 
fenics-dolfinx_0.6.0-7.debian.tar.xz
 3e2fa237959cdba24c33402461064cf5 18905 math optional 
fenics-dolfinx_0.6.0-7_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJIBAEBCgAyFiEEI8mpPlhYGekSbQo2Vz7x5L1aAfoFAmTTtLwUHGRwYXJzb25z
QGRlYmlhbi5vcmcACgkQVz7x5L1aAfoyTRAAitnSiSbCf/WCLJwYSH6oXqBydceY
7Nh+DBpKQfD7nJzlvBy4J1YKsH3TzN40yvPDtE/YxD95c2nxAO/pyVSUxqppQ60r
jZ1UKpekQCRzJ7chdAa/JDJZdQUBzcfjjm0xeK8K1boJ/AuFdHYKZ4otLkLE6ftW
R+soknDtvnQAKoGF/RCSOps5/A2iDfUzAgmPTPuWWG+lBFxA5iS2krmyB02QTZuJ
CImYz8kDq5X7LX0GFMkbQrb7XwLfpJirMEqZ6cLIJVNdJbg4M6zRl7zTO6rt3mLY
ds9WBYuxaHhZTeOu4rK0dwJVcYnN1lsJKoYXv+GxumxbO7OBRuKFVYIZn4GM8+30
cjoOnyV9Ya6YQw5FuNYEaDmywPfhJ7aeLJ2yqhkLNthEZDr9IKQ6Tg/1LfM7/68Q
pqB/psfPmLLtlk+rCMVdJdbtNicfAwnqk3yf30JinmwUvGXLz6eBCV4JaFCxGh+Y
vnn+6dk+IAxq3ep/JzQ5L856qBi1jLbuhflpL1sKuJWaNyTEA6+KozqM2qZa+dQO
uUB/9PS68rs9xcIawf+xShlfgLElYjyTL7o5EJbZmz3BwtVlbJsOO0OTuKzRCeXm
xY3Hwzin6EdRTZT9HEQI5nWGgGrV/RnVcu6F337S4H16eP4etN8uWfK+toE6tTK6
dcNJUY2eQnsXh0U=
=uvS+
-END PGP SIGNATURE End Message ---

Bug#1037855: marked as done (seqan-needle: ftbfs with GCC-13)

[Debian Bug Tracking System]

Your message dated Wed, 09 Aug 2023 16:13:51 +
with message-id 
and subject line Bug#1037855: fixed in seqan-needle 1.0.1.0.1.git.439eeab+ds-1
has caused the Debian Bug report #1037855,
regarding seqan-needle: 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.)


-- 
1037855: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1037855
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:seqan-needle
Version: 1.0.1.0.0.git.3011926+ds-4
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/seqan-needle_1.0.1.0.0.git.3011926+ds-4_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

[...]
  int main() {}

Performing C++ SOURCE FILE Test CONCEPTS_FLAG_BUILTIN failed with the following 
output:
Change Dir: 
/<>/obj-x86_64-linux-gnu/CMakeFiles/CMakeScratch/TryCompile-Gc8K82

Run Build Command(s):/usr/bin/gmake -f Makefile cmTC_ed4a1/fast && gmake[2]: 
Entering directory 
'/<>/obj-x86_64-linux-gnu/CMakeFiles/CMakeScratch/TryCompile-Gc8K82'
/usr/bin/gmake  -f CMakeFiles/cmTC_ed4a1.dir/build.make 
CMakeFiles/cmTC_ed4a1.dir/build
gmake[3]: Entering directory 
'/<>/obj-x86_64-linux-gnu/CMakeFiles/CMakeScratch/TryCompile-Gc8K82'
Building CXX object CMakeFiles/cmTC_ed4a1.dir/src.cxx.o
/usr/bin/c++ -DCONCEPTS_FLAG_BUILTIN 
-I/usr/include/seqan3/submodules/sdsl-lite/include -g -O2 
-ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 
-ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -o 
CMakeFiles/cmTC_ed4a1.dir/src.cxx.o -c 
/<>/obj-x86_64-linux-gnu/CMakeFiles/CMakeScratch/TryCompile-Gc8K82/src.cxx
/<>/obj-x86_64-linux-gnu/CMakeFiles/CMakeScratch/TryCompile-Gc8K82/src.cxx:1:16:
 error: ‘__cpp_concepts’ was not declared in this scope
1 | static_assert (__cpp_concepts >= 201507); int 
main() {}
  |^~
gmake[3]: *** [CMakeFiles/cmTC_ed4a1.dir/build.make:78: 
CMakeFiles/cmTC_ed4a1.dir/src.cxx.o] Error 1
gmake[3]: Leaving directory 
'/<>/obj-x86_64-linux-gnu/CMakeFiles/CMakeScratch/TryCompile-Gc8K82'
gmake[2]: *** [Makefile:127: cmTC_ed4a1/fast] Error 2
gmake[2]: Leaving directory 
'/<>/obj-x86_64-linux-gnu/CMakeFiles/CMakeScratch/TryCompile-Gc8K82'


Source file was:
static_assert (__cpp_concepts >= 201507); int main() {}

Determining if the include file sdsl/version.hpp exists failed with the 
following output:
Change Dir: 
/<>/obj-x86_64-linux-gnu/CMakeFiles/CMakeScratch/TryCompile-psxKzT

Run Build Command(s):/usr/bin/gmake -f Makefile cmTC_e0d12/fast && gmake[2]: 
Entering directory 
'/<>/obj-x86_64-linux-gnu/CMakeFiles/CMakeScratch/TryCompile-psxKzT'
/usr/bin/gmake  -f CMakeFiles/cmTC_e0d12.dir/build.make 
CMakeFiles/cmTC_e0d12.dir/build
gmake[3]: Entering directory 
'/<>/obj-x86_64-linux-gnu/CMakeFiles/CMakeScratch/TryCompile-psxKzT'
Building CXX object CMakeFiles/cmTC_e0d12.dir/CheckIncludeFile.cxx.o
/usr/bin/c++  -I/usr/include/seqan3/submodules/sdsl-lite/include -g -O2 
-ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 
-ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -o 
CMakeFiles/cmTC_e0d12.dir/CheckIncludeFile.cxx.o -c 
/<>/obj-x86_64-linux-gnu/CMakeFiles/CMakeScratch/TryCompile-psxKzT/CheckIncludeFile.cxx
In file included from 

Bug#999324: marked as done (libapache-mod-auth-kerb: missing required debian/rules targets build-arch and/or build-indep)

[Debian Bug Tracking System]

Your message dated Wed, 09 Aug 2023 15:52:49 +
with message-id 
and subject line Bug#999324: fixed in libapache-mod-auth-kerb 5.4-3
has caused the Debian Bug report #999324,
regarding libapache-mod-auth-kerb: missing required debian/rules targets 
build-arch and/or build-indep
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.)


-- 
999324: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=999324
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libapache-mod-auth-kerb
Version: 5.4-2.5
Severity: important
Justification: Debian Policy section 4.9
Tags: bookworm sid
User: debian...@lists.debian.org
Usertags: missing-build-arch-indep

Dear maintainer,

Your package does not include build-arch and/or build-indep targets in
debian/rules. This is required by Debian Policy section 4.9, since 2012.
https://www.debian.org/doc/debian-policy/ch-source.html#main-building-script-debian-rules

Please note that this is also a sign that the packaging of this software
could benefit from a refresh. For example, packages using 'dh' cannot be
affected by this issue.

This mass bug filing was discussed on debian-devel@ in
https://lists.debian.org/debian-devel/2021/11/msg00052.html .
The severity of this bug will be changed to 'serious' after a month.

Best,

Lucas
--- End Message ---
--- Begin Message ---
Source: libapache-mod-auth-kerb
Source-Version: 5.4-3
Done: Bastian Germann 

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

Debian distribution maintenance software
pp.
Bastian Germann  (supplier of updated libapache-mod-auth-kerb 
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: Wed, 09 Aug 2023 17:10:56 +0200
Source: libapache-mod-auth-kerb
Architecture: source
Version: 5.4-3
Distribution: unstable
Urgency: medium
Maintainer: Debian QA Group 
Changed-By: Bastian Germann 
Closes: 999324
Changes:
 libapache-mod-auth-kerb (5.4-3) unstable; urgency=medium
 .
   * QA upload.
   * Convert to source format 3.0.
   * d/rules: Add build-arch and build-indep. (Closes: #999324)
Checksums-Sha1:
 264dfde9d48b12da6fc0d8f99bd8dee1d462fcd2 1723 libapache-mod-auth-kerb_5.4-3.dsc
 a6a31a2c9b87c8fa0862c272372ba97e41707068 15888 
libapache-mod-auth-kerb_5.4-3.debian.tar.xz
 d22b271849705809308a8a8e449d96b248815d11 6782 
libapache-mod-auth-kerb_5.4-3_source.buildinfo
Checksums-Sha256:
 bf84ec112281b0741b52b811a12fdd00c0cae006cbcd8cf0dc56948be5e8dde1 1723 
libapache-mod-auth-kerb_5.4-3.dsc
 2c6a20936895b0f82022dbc222808a02f93dfa5eaac15abe399bb0b8d616fb81 15888 
libapache-mod-auth-kerb_5.4-3.debian.tar.xz
 c79b1e793364232c6355c4a8297d9ae06b87247ef01b105c45ae9202c4c735bc 6782 
libapache-mod-auth-kerb_5.4-3_source.buildinfo
Files:
 dc0c913dc625da3c467b2686739cf95b 1723 net optional 
libapache-mod-auth-kerb_5.4-3.dsc
 6794cc93b946cbacefb792a45f0cbfc5 15888 net optional 
libapache-mod-auth-kerb_5.4-3.debian.tar.xz
 a0feb4ddae1ef421777ddc9ef93fa8bb 6782 net optional 
libapache-mod-auth-kerb_5.4-3_source.buildinfo

-BEGIN PGP SIGNATURE-

iQHEBAEBCgAuFiEEQGIgyLhVKAI3jM5BH1x6i0VWQxQFAmTTrjMQHGJhZ2VAZGVi
aWFuLm9yZwAKCRAfXHqLRVZDFOQBC/wPwQvQbNRuM7MT0U5D3Sho0eMj88zjbtJm
Z8dc4QWde79/Ie5BAPOcqxsXRu1a7SC4HPwdE80UvcSrT3R0ja80n6gFlxvVN7m/
g8yhTiblhR+3OqPmHi0vkK4sb8KY9H8bfCuac9LNfl+tVXqhDfdmHRijQCMZM5pW
YnMaKhWfIGTbYkBsmlFHJD8gA+DYgTJpWF8nHWHZMOubnY3S+BmA30xWiyUrLFpE
Wg5UPBfcojfrGi4Y4BtOrUqgLEgQI4Uk603d7KPZ5AjCnPV0sKYRW2wBuul53B+3
NGJzG2kdnML01H8Qz98j43Yq5dlyz9i7JzDGMcVnp2O2Hfhsqm+qViyN5QeP8WHv
Z2YUlDK7Noxi3IB6apWjoYW7e15wKJEaN6ZGDPMu2XY/wWOgBhoDz1fLrQ8EKTUt
TLEYc0NMEdXxmrRK6hY5nY/PYKP+WlBgH/dCYoxGhQwpJXutzM3GcQSRPFTIHKNh
8PFvGIhPSVUJKN7OF2jwKVA6HyirQ9c=
=yUl6
-END PGP SIGNATURE End Message ---

Bug#1043368: kokkos FTBFS with gcc 13

[Adrian Bunk]

Source: kokkos
Version: 3.7.01-2
Severity: serious
Tags: ftbfs

https://buildd.debian.org/status/fetch.php?pkg=kokkos=riscv64=3.7.01-2=1691576293=0
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/kokkos.html

...
/<>/core/src/impl/Kokkos_MemoryPool.cpp:116:48: error: ‘uint32_t’ 
has not been declared
  116 | void _print_memory_pool_state(std::ostream& s, uint32_t const* 
sb_state_ptr,
  |^~~~
/<>/core/src/impl/Kokkos_MemoryPool.cpp:117:49: error: ‘uint32_t’ 
has not been declared
  117 |   int32_t sb_count, uint32_t sb_size_lg2,
  | ^~~~
/<>/core/src/impl/Kokkos_MemoryPool.cpp:118:31: error: ‘uint32_t’ 
has not been declared
  118 |   uint32_t sb_state_size, uint32_t 
state_shift,
  |   ^~~~
/<>/core/src/impl/Kokkos_MemoryPool.cpp:118:55: error: ‘uint32_t’ 
has not been declared
  118 |   uint32_t sb_state_size, uint32_t 
state_shift,
  |   ^~~~
/<>/core/src/impl/Kokkos_MemoryPool.cpp:119:31: error: ‘uint32_t’ 
has not been declared
  119 |   uint32_t state_used_mask) {
  |   ^~~~
...

Bug#1037862: marked as done (sopt: ftbfs with GCC-13)

[Debian Bug Tracking System]

Your message dated Wed, 09 Aug 2023 15:07:26 +
with message-id 
and subject line Bug#1037862: fixed in sopt 3.0.1+dfsg-2
has caused the Debian Bug report #1037862,
regarding sopt: 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.)


-- 
1037862: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1037862
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:sopt
Version: 3.0.1+dfsg-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/sopt_3.0.1+dfsg-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

[...]
   51 |   uint32 *raster = (uint32 *)_TIFFmalloc(width * height * 
sizeof(uint32));
  |   ^~
/usr/include/x86_64-linux-gnu/tiff.h:86:38: note: declared here
   86 | typedef TIFF_MSC_DEPRECATED uint32_t uint32 TIFF_GCC_DEPRECATED;
  |  ^~
/<>/cpp/sopt/utilities.cc:51:28: warning: ‘uint32’ is deprecated 
[-Wdeprecated-declarations]
   51 |   uint32 *raster = (uint32 *)_TIFFmalloc(width * height * 
sizeof(uint32));
  |^
/usr/include/x86_64-linux-gnu/tiff.h:86:38: note: declared here
   86 | typedef TIFF_MSC_DEPRECATED uint32_t uint32 TIFF_GCC_DEPRECATED;
  |  ^~
/<>/cpp/sopt/utilities.cc:51:66: warning: ‘uint32’ is deprecated 
[-Wdeprecated-declarations]
   51 |   uint32 *raster = (uint32 *)_TIFFmalloc(width * height * 
sizeof(uint32));
  |  ^~
/usr/include/x86_64-linux-gnu/tiff.h:86:38: note: declared here
   86 | typedef TIFF_MSC_DEPRECATED uint32_t uint32 TIFF_GCC_DEPRECATED;
  |  ^~
/<>/cpp/sopt/utilities.cc:57:16: warning: ‘uint32’ is deprecated 
[-Wdeprecated-declarations]
   57 |   for (uint32 i(0); i < height; ++i)
  |^
/usr/include/x86_64-linux-gnu/tiff.h:86:38: note: declared here
   86 | typedef TIFF_MSC_DEPRECATED uint32_t uint32 TIFF_GCC_DEPRECATED;
  |  ^~
/<>/cpp/sopt/utilities.cc:58:18: warning: ‘uint32’ is deprecated 
[-Wdeprecated-declarations]
   58 | for (uint32 j(0); j < width; ++j, ++pixel) result(i, j) = 
convert_to_greyscale(*pixel);
  |  ^
/usr/include/x86_64-linux-gnu/tiff.h:86:38: note: declared here
   86 | typedef TIFF_MSC_DEPRECATED uint32_t uint32 TIFF_GCC_DEPRECATED;
  |  ^~
/<>/cpp/sopt/utilities.cc: In function ‘void 
sopt::utilities::write_tiff(sopt::Image<>&, const std::string&)’:
/<>/cpp/sopt/utilities.cc:72:16: warning: ‘uint32’ is deprecated 
[-Wdeprecated-declarations]
   72 |   uint32 const width = image.cols();
  |^
/usr/include/x86_64-linux-gnu/tiff.h:86:38: note: declared here
   86 | typedef TIFF_MSC_DEPRECATED uint32_t uint32 TIFF_GCC_DEPRECATED;
  |  ^~
/<>/cpp/sopt/utilities.cc:73:16: warning: ‘uint32’ is deprecated 
[-Wdeprecated-declarations]
   73 |   uint32 const height = image.rows();
  |^~
/usr/include/x86_64-linux-gnu/tiff.h:86:38: note: declared here
   86 | typedef TIFF_MSC_DEPRECATED uint32_t uint32 TIFF_GCC_DEPRECATED;
  |  ^~
/<>/cpp/sopt/utilities.cc:90:16: warning: ‘uint32’ is deprecated 
[-Wdeprecated-declarations]
   90 |   for (uint32 i(0); i < height; ++i)
  |^

Bug#1041443: issue at meson-python

[Jerome Kieffer]

Hi,

Apparently this bug comes from the tool used to build the source package: 
"meson-python" ... it does not set properly timestamps in the source archive.
https://github.com/mesonbuild/meson-python/issues/450

Cheers,

Jerome

Processed: severity of 1031402 is grave

[Debian Bug Tracking System]

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

> # "unusable or mostly so": cannot be used without significant reworking of 
> shipped and generated config files.
> severity 1031402 grave
Bug #1031402 [mutt-wizard] mutt-wizard: ships and generates invalid neomutt rc 
files
Severity set to 'grave' from 'important'
> thanks
Stopping processing here.

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

Bug#1017898: marked as done (Ships autogenerated files that can't be renegerated with the code in Debian main)

[Debian Bug Tracking System]

Your message dated Wed, 09 Aug 2023 13:21:57 +
with message-id 
and subject line Bug#1043342: Removed package(s) from unstable
has caused the Debian Bug report #1017898,
regarding Ships autogenerated files that can't be renegerated with the code in 
Debian main
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.)


-- 
1017898: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1017898
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: appindicator3-sharp
Version: 12.10.0+git20151221-5.1
Severity: serious
Tags: upstream

See the discussion on the Debian Rust maintainers list for background:
https://alioth-lists.debian.net/pipermail/pkg-rust-maintainers/2022-August/022857.html

While that discussion is about Rust packages that were rejected, the same
situation also applies to appindicator3-sharp unfortunately. For more details 
how to solve
this in a way that makes ftp-masters happy, please refer to them.


Affected file is sources/appindicator3-sharp-api.raw. This file were
autogenerated from specific versions of the underlying C libraries and it's
not clear which versions were used.

Debian ships these C libraries but certainly in different versions so it's not
possible to regenerate these files with what is available in Debian.

It will be necessary to either include the source code of the C libraries in
the exact version, or regenerate the files at build time with whatever is
available in Debian.

The latter will probably generate different bindings, potentially even with
different API, so is probably not a useful solution.


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

Kernel: Linux 5.18.0-4-amd64 (SMP w/8 CPU threads; PREEMPT)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_GB:en
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
--- End Message ---
--- Begin Message ---
Version: 12.10.0+git20151221-5.1+rm

Dear submitter,

as the package appindicator3-sharp has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/1043342

The version of this package that was in Debian prior to this removal
can still be found using https://snapshot.debian.org/.

Please note that the changes have been done on the master archive and
will not propagate to any mirrors until the next dinstall run at the
earliest.

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

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---

Bug#983991: marked as done (bist: ftbfs with GCC-11)

[Debian Bug Tracking System]

Your message dated Wed, 09 Aug 2023 13:18:05 +
with message-id 
and subject line Bug#1043302: Removed package(s) from unstable
has caused the Debian Bug report #983991,
regarding bist: ftbfs with GCC-11
to be marked as done.

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

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


-- 
983991: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=983991
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:bist
Version: 0.5.2-1.2
Severity: normal
Tags: sid bookworm
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-11

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

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

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

The full build log can be found at:
http://people.debian.org/~doko/logs/20210228/filtered/gcc11/bist_0.5.2-1.2_unstable_gcc11.log
The last lines of the build log are at the end of this report.

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

  apt-get -t=experimental install g++ 

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

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

[...]
183 translated messages, 1 untranslated message.
make[4]: Leaving directory '/<>/po'
touch stamp-po
make[3]: Leaving directory '/<>/po'
Making all in .
make[3]: Entering directory '/<>'
/bin/bash ./libtool  --tag=CXX   --mode=compile g++ -DHAVE_CONFIG_H -I. 
-I./include   -I./pluginclude -I. -I./include -I../images -pedantic 
-I/usr/include/cairo -I/usr/include/glib-2.0 
-I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/include/pixman-1 
-I/usr/include/uuid -I/usr/include/freetype2 -I/usr/include/libpng16 
-I/usr/include/uuid -I/usr/include/freetype2 -I/usr/include/libpng16 
-I/usr/include/cairo -I/usr/include/glib-2.0 
-I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/include/pixman-1 
-I/usr/include/uuid -I/usr/include/freetype2 -I/usr/include/libpng16  
-I/usr/include/cairo -I/usr/include/glib-2.0 
-I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/include/pixman-1 
-I/usr/include/uuid -I/usr/include/freetype2 -I/usr/include/libpng16 -pthread 
-I/usr/include/pango-1.0 -I/usr/include/libmount -I/usr/include/blkid 
-I/usr/include/fribidi -I/usr/include/harfbuzz -I/usr/include/cairo 
-I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include 
-I/usr/include/pixman-1
  -I/usr/include/uuid -I/usr/include/freetype2 -I/usr/include/libpng16 -Wall 
-Werror=format-security  -g -O2 -rdynamic -c -o 
align_elements_la-align_elements.lo `test -f 'pluginsrc/align_elements.cpp' || 
echo './'`pluginsrc/align_elements.cpp
libtool: compile:  g++ -DHAVE_CONFIG_H -I. -I./include -I./pluginclude -I. 
-I./include -I../images -pedantic -I/usr/include/cairo -I/usr/include/glib-2.0 
-I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/include/pixman-1 
-I/usr/include/uuid -I/usr/include/freetype2 -I/usr/include/libpng16 
-I/usr/include/uuid -I/usr/include/freetype2 -I/usr/include/libpng16 
-I/usr/include/cairo -I/usr/include/glib-2.0 
-I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/include/pixman-1 
-I/usr/include/uuid -I/usr/include/freetype2 -I/usr/include/libpng16 
-I/usr/include/cairo -I/usr/include/glib-2.0 
-I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/include/pixman-1 
-I/usr/include/uuid -I/usr/include/freetype2 -I/usr/include/libpng16 -pthread 
-I/usr/include/pango-1.0 -I/usr/include/libmount -I/usr/include/blkid 
-I/usr/include/fribidi -I/usr/include/harfbuzz -I/usr/include/cairo 
-I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include 
-I/usr/include/pixman-1 -I/usr/include/uuid -I/usr/incl
 ude/freetype2 -I/usr/include/libpng16 -Wall -Werror=format-security -g -O2 
-rdynamic -c pluginsrc/align_elements.cpp  -fPIC -DPIC -o 

Bug#1017903: marked as done (Ships autogenerated files that can't be renegerated with the code in Debian main)

[Debian Bug Tracking System]

Your message dated Wed, 09 Aug 2023 13:21:08 +
with message-id 
and subject line Bug#1043345: Removed package(s) from unstable
has caused the Debian Bug report #1017903,
regarding Ships autogenerated files that can't be renegerated with the code in 
Debian main
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.)


-- 
1017903: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1017903
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: soup-sharp
Version: 2.42.2+git20151219-3.1
Severity: serious
Tags: upstream


See the discussion on the Debian Rust maintainers list for background:
https://alioth-lists.debian.net/pipermail/pkg-rust-maintainers/2022-August/022857.html

While that discussion is about Rust packages that were rejected, the same
situation also applies to gtk-sharp unfortunately. For more details how to solve
this in a way that makes ftp-masters happy, please refer to them.


Affected file is soup/soup-sharp-api.raw. This file was autogenerated from
specific versions of the underlying C libraries and it's not clear which
versions were used.

Debian ships these C libraries but certainly in different versions so it's not
possible to regenerate these files with what is available in Debian.

It will be necessary to either include the source code of the C libraries in
the exact version, or regenerate the files at build time with whatever is
available in Debian.

The latter will probably generate different bindings, potentially even with
different API, so is probably not a useful solution.


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

Kernel: Linux 5.18.0-4-amd64 (SMP w/8 CPU threads; PREEMPT)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_GB:en
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
--- End Message ---
--- Begin Message ---
Version: 2.42.2+git20151219-3.1+rm

Dear submitter,

as the package soup-sharp has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/1043345

The version of this package that was in Debian prior to this removal
can still be found using https://snapshot.debian.org/.

Please note that the changes have been done on the master archive and
will not propagate to any mirrors until the next dinstall run at the
earliest.

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

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---

Bug#1017904: marked as done (Ships autogenerated files that can't be renegerated with the code in Debian main)

[Debian Bug Tracking System]

Your message dated Wed, 09 Aug 2023 13:20:39 +
with message-id 
and subject line Bug#1043343: Removed package(s) from unstable
has caused the Debian Bug report #1017904,
regarding Ships autogenerated files that can't be renegerated with the code in 
Debian main
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.)


-- 
1017904: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1017904
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: webkit2-sharp
Version: 2.10.9+git20160917-1.1
Severity: serious
Tags: upstream

See the discussion on the Debian Rust maintainers list for background:
https://alioth-lists.debian.net/pipermail/pkg-rust-maintainers/2022-August/022857.html

While that discussion is about Rust packages that were rejected, the same
situation also applies to gtk-sharp unfortunately. For more details how to solve
this in a way that makes ftp-masters happy, please refer to them.


Affected file is sources/webkit2-sharp-api.raw. This file was autogenerated
from specific versions of the underlying C libraries and it's not clear which
versions were used.

Debian ships these C libraries but certainly in different versions so it's not
possible to regenerate these files with what is available in Debian.

It will be necessary to either include the source code of the C libraries in
the exact version, or regenerate the files at build time with whatever is
available in Debian.

The latter will probably generate different bindings, potentially even with
different API, so is probably not a useful solution.


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

Kernel: Linux 5.18.0-4-amd64 (SMP w/8 CPU threads; PREEMPT)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_GB:en
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
--- End Message ---
--- Begin Message ---
Version: 2.10.9+git20160917-1.1+rm

Dear submitter,

as the package webkit2-sharp has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/1043343

The version of this package that was in Debian prior to this removal
can still be found using https://snapshot.debian.org/.

Please note that the changes have been done on the master archive and
will not propagate to any mirrors until the next dinstall run at the
earliest.

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

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---

Bug#1021970: marked as done (crossbar FTBFS: test failures)

[Debian Bug Tracking System]

Your message dated Wed, 09 Aug 2023 13:18:59 +
with message-id 
and subject line Bug#1043341: Removed package(s) from unstable
has caused the Debian Bug report #1021970,
regarding crossbar FTBFS: test failures
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.)


-- 
1021970: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1021970
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: crossbar
Version: 21.3.1+dfsg-3
Severity: serious
Tags: ftbfs

https://tests.reproducible-builds.org/debian/rb-pkg/bookworm/amd64/crossbar.html
https://buildd.debian.org/status/fetch.php?pkg=crossbar=all=21.3.1%2Bdfsg-4=1664558948=0

...
==
ERROR: test_basic_web (crossbar.bridge.rest.test.test_callee.CalleeTestCase)
Plain request, no params.
--
Traceback (most recent call last):
  File 
"/<>/.pybuild/cpython3_3.10_crossbar/build/crossbar/bridge/rest/test/test_callee.py",
 line 58, in test_basic_web
res = yield c.call("io.crossbar.testrest", method="GET", url="baz.html")
autobahn.wamp.exception.ApplicationError: 
ApplicationError(error=, args=[], kwargs={}, 
enc_algo=None, callee=None, callee_authid=None, callee_authrole=None, 
forward_for=None)

==
ERROR: test_basic_web (crossbar.bridge.rest.test.test_callee.CalleeTestCase)
Plain request, no params.
--
Traceback (most recent call last):
  File "/usr/lib/python3/dist-packages/twisted/internet/defer.py", line 857, in 
_runCallbacks
current.result = callback(  # type: ignore[misc]
  File "/usr/lib/python3/dist-packages/autobahn/wamp/protocol.py", line 605, in 
success
transport=self._transport.transport_details,
AttributeError: 'MockTransport' object has no attribute 'transport_details'

==
ERROR: test_slightlymorecomplex_web 
(crossbar.bridge.rest.test.test_callee.CalleeTestCase)
Giving headers, params, a body.
--
Traceback (most recent call last):
  File 
"/<>/.pybuild/cpython3_3.10_crossbar/build/crossbar/bridge/rest/test/test_callee.py",
 line 86, in test_slightlymorecomplex_web
res = yield c.call("io.crossbar.testrest", method="POST",
autobahn.wamp.exception.ApplicationError: 
ApplicationError(error=, args=[], kwargs={}, 
enc_algo=None, callee=None, callee_authid=None, callee_authrole=None, 
forward_for=None)

==
ERROR: test_slightlymorecomplex_web 
(crossbar.bridge.rest.test.test_callee.CalleeTestCase)
Giving headers, params, a body.
--
Traceback (most recent call last):
  File "/usr/lib/python3/dist-packages/twisted/internet/defer.py", line 857, in 
_runCallbacks
current.result = callback(  # type: ignore[misc]
  File "/usr/lib/python3/dist-packages/autobahn/wamp/protocol.py", line 605, in 
success
transport=self._transport.transport_details,
AttributeError: 'MockTransport' object has no attribute 'transport_details'

==
ERROR: test_basic_web 
(crossbar.bridge.rest.test.test_subscriber.MessageForwarderTestCase)
Plain request, no params.
--
Traceback (most recent call last):
  File 
"/<>/.pybuild/cpython3_3.10_crossbar/build/crossbar/bridge/rest/test/test_subscriber.py",
 line 64, in test_basic_web
res = yield c.publish("io.crossbar.forward1", "hi",
autobahn.wamp.exception.ApplicationError: 
ApplicationError(error=, args=[], kwargs={}, 
enc_algo=None, callee=None, callee_authid=None, callee_authrole=None, 
forward_for=None)

==
ERROR: test_basic_web 
(crossbar.bridge.rest.test.test_subscriber.MessageForwarderTestCase)
Plain request, no params.
--
Traceback (most recent call last):
  File "/usr/lib/python3/dist-packages/twisted/internet/defer.py", line 857, in 
_runCallbacks
current.result = callback(  # type: ignore[misc]
  File "/usr/lib/python3/dist-packages/autobahn/wamp/protocol.py", line 605, in 
success
transport=self._transport.transport_details,
AttributeError: 'MockTransport' object has no attribute 

Bug#1042187: marked as done (gnocchi: FTBFS: AttributeError: module 'setuptools.command.easy_install' has no attribute 'get_script_header')

[Debian Bug Tracking System]

Your message dated Wed, 09 Aug 2023 13:04:17 +
with message-id 
and subject line Bug#1042187: fixed in gnocchi 4.5.0-4
has caused the Debian Bug report #1042187,
regarding gnocchi: FTBFS: AttributeError: module 
'setuptools.command.easy_install' has no attribute 'get_script_header'
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.)


-- 
1042187: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1042187
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: gnocchi
Version: 4.5.0-3
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20230726 ftbfs-trixie

Hi,

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


Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> make[1]: pyversions: No such file or directory
> py3versions: no X-Python3-Version in control file, using supported versions
> set -e ; for pyvers in 3.11; do \
>   python$pyvers setup.py install --install-layout=deb --root 
> /<>/debian/tmp; \
> done
> running install
> /usr/lib/python3/dist-packages/setuptools/_distutils/cmd.py:66: 
> SetuptoolsDeprecationWarning: setup.py install is deprecated.
> !!
> 
> 
> 
> Please avoid running ``setup.py`` directly.
> Instead, use pypa/build, pypa/installer or other
> standards-based tools.
> 
> See https://blog.ganssle.io/articles/2021/10/setup-py-deprecated.html 
> for details.
> 
> 
> 
> !!
>   self.initialize_options()
> running build
> running build_py
> creating build
> creating build/lib
> creating build/lib/gnocchi
> copying gnocchi/calendar.py -> build/lib/gnocchi
> copying gnocchi/utils.py -> build/lib/gnocchi
> copying gnocchi/chef.py -> build/lib/gnocchi
> copying gnocchi/archive_policy.py -> build/lib/gnocchi
> copying gnocchi/__init__.py -> build/lib/gnocchi
> copying gnocchi/amqp1d.py -> build/lib/gnocchi
> copying gnocchi/json.py -> build/lib/gnocchi
> copying gnocchi/gendoc.py -> build/lib/gnocchi
> copying gnocchi/exceptions.py -> build/lib/gnocchi
> copying gnocchi/statsd.py -> build/lib/gnocchi
> copying gnocchi/carbonara.py -> build/lib/gnocchi
> copying gnocchi/service.py -> build/lib/gnocchi
> copying gnocchi/opts.py -> build/lib/gnocchi
> copying gnocchi/resource_type.py -> build/lib/gnocchi
> running egg_info
> creating gnocchi.egg-info
> writing gnocchi.egg-info/PKG-INFO
> writing dependency_links to gnocchi.egg-info/dependency_links.txt
> writing entry points to gnocchi.egg-info/entry_points.txt
> writing requirements to gnocchi.egg-info/requires.txt
> writing top-level names to gnocchi.egg-info/top_level.txt
> writing manifest file 'gnocchi.egg-info/SOURCES.txt'
> reading manifest file 'gnocchi.egg-info/SOURCES.txt'
> reading manifest template 'MANIFEST.in'
> warning: no previously-included files found matching '.gitignore'
> warning: no previously-included files found matching '.github'
> adding license file 'LICENSE'
> writing manifest file 'gnocchi.egg-info/SOURCES.txt'
> /usr/lib/python3/dist-packages/setuptools/command/build_py.py:201: _Warning: 
> Package 'gnocchi.cli' is absent from the `packages` configuration.
> !!
> 
> 
> 
> 
> # Package would be ignored #
> 
> Python recognizes 'gnocchi.cli' as an importable package[^1],
> but it is absent from setuptools' `packages` configuration.
> 
> This leads to an ambiguous overall configuration. If you want to 
> distribute this
> package, please make sure that 'gnocchi.cli' is explicitly added
> to the `packages` configuration field.
> 
> Alternatively, you can also rely on setuptools' discovery methods
> (for example by using `find_namespace_packages(...)`/`find_namespace:`
> instead of `find_packages(...)`/`find:`).
> 
> You can read more about "package discovery" on setuptools 
> documentation page:
> 
> - 
> https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
> 
> If you don't want 'gnocchi.cli' to be distributed and are
> already explicitly excluding 'gnocchi.cli' via
> `find_namespace_packages(...)/find_namespace` or 
> `find_packages(...)/find`,
> you can try to use `exclude_package_data`, or 
> 

Bug#1042407: marked as done (rtpengine FTBFS with FFmpeg 6.0)

[Debian Bug Tracking System]

Your message dated Wed, 09 Aug 2023 13:04:55 +
with message-id 
and subject line Bug#1042407: fixed in rtpengine 10.5.5.2-1
has caused the Debian Bug report #1042407,
regarding rtpengine FTBFS with FFmpeg 6.0
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.)


-- 
1042407: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1042407
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: rtpengine
Version: 10.5.4.3-1
Severity: serious
Tags: ftbfs

https://buildd.debian.org/status/logs.php?pkg=rtpengine=10.5.4.3-1%2Bb2

...
running test test-transcode.c:518
send RTP SSRC 4d2 seq 0 TS 0 PT 0
send packet contents: 
\x01\x00\x01\x00\x01\x00\x01\x00\x01\x00\x01\x00\x01\x00\x01\x00\x01\x00\x01\x00\x01\x00\x01\x00\x01\x00\x01\x00\x01\x00\x01\x00\x01\x00\x01\x00\x01\x00\x01\x00\x01\x00\x01\x00\x01\x00\x01\x00\x01\x00\x01\x00\x01\x00\x01\x00\x01\x00\x01\x00\x01\x00\x01\x00\x01\x00\x01\x00\x01\x00\x01\x00\x01\x00\x01\x00\x01\x00\x01\x00\x01\x00\x01\x00\x01\x00\x01\x00\x01\x00\x01\x00\x01\x00\x01\x00\x01\x00\x01\x00\x01\x00\x01\x00\x01\x00\x01\x00\x01\x00\x01\x00\x01\x00\x01\x00\x01\x00\x01\x00\x01\x00\x01\x00\x01\x00\x01\x00\x01\x00\x01\x00\x01\x00\x01\x00\x01\x00\x01\x00\x01\x00\x01\x00\x01\x00\x01\x00\x01\x00\x01\x00\x01\x00\x01\x00\x01\x00\x01\x00
recv packet contents: 
\x2b\x2a\x2b\x2a\x2b\x2a\x2b\x2a\x2b\x2a\x2b\x2a\x2b\x2a\x2b\x2a\x2b\x2a\x2b\x2a\x2b\x2a\x2b\x2a\x2b\x2a\x2b\x2a\x2b\x2a\x2b\x2a\x2b\x2a\x2b\x2a\x2b\x2a\x2b\x2a\x2b\x2a\x2b\x2a\x2b\x2a\x2b\x2a\x2b\x2a\x2b\x2a\x2b\x2a\x2b\x2a\x2b\x2a\x2b\x2a\x2b\x2a\x2b\x2a\x2b\x2a\x2b\x2a\x2b\x2a\x2b\x2a\x2b\x2a\x2b\x2a\x2b\x2a\x2b\x2a\x2b\x2a\x2b\x2a\x2b\x2a\x2b\x2a\x2b\x2a\x2b\x2a\x2b\x2a\x2b\x2a\x2b\x2a\x2b\x2a\x2b\x2a\x2b\x2a\x2b\x2a\x2b\x2a\x2b\x2a\x2b\x2a\x2b\x2a\x2b\x2a\x2b\x2a\x2b\x2a\x2b\x2a\x2b\x2a\x2b\x2a\x2b\x2a\x2b\x2a\x2b\x2a\x2b\x2a\x2b\x2a\x2b\x2a\x2b\x2a\x2b\x2a\x2b\x2a\x2b\x2a\x2b\x2a\x2b\x2a\[transcoding]
 Received RTP packet: SSRC 2909, PT 8, seq 0, TS 0, len 160
[internals] returning in-sequence packet (seq 0)
[transcoding] Processing RTP packet: seq 0, TS 0
[transcoding] Decoding RTP packet now
[internals] 0x55e6cbedc700 dec pts 18446744073709551615 rtp_ts 
18446744073709551615 incoming ts 0
[internals] send packet ret 0
[internals] receive frame ret 0
[internals] raw frame from decoder pts 0 samples 160
[internals] receive frame ret -11
[transcoding] RTP media successfully decoded: TS 0, samples 160
[internals] output fifo pts 0
[internals] send frame ret 0
[internals] receive packet ret 0
[internals] output avpkt size is 160
[internals] output pkt pts/dts is 0/0
[transcoding] RTP media successfully encoded: TS 0, len 160
[transcoding] Adding 160 bytes to packetizer
[transcoding] Received packet of 160 bytes from packetizer
[transcoding] Scheduling to send RTP packet (seq 0 TS 0) in 0.0 ms (at 0.00)
[internals] receive packet ret -11
[internals] packet queue empty
[internals] receive packet ret -11
[internals] receive packet ret -11
[internals] Adding codec 'PCMA'/'PCMA/8000'/'PCMA/8000/1' at pos (nil)
[codec] Updating codecs for offerer tag_A #0
[codec] Adding codec PCMA/8000 (8)
[internals] Adding codec 'PCMA'/'PCMA/8000'/'PCMA/8000/1' at pos (nil)
[codec] Codec G722 not present for offering
[codec] Updating codecs for answerer tag_B #0
[codec] Adding codec PCMA/8000 (8)
[internals] Adding codec 'PCMA'/'PCMA/8000'/'PCMA/8000/1' at pos (nil)
[codec] Adding codec G722 for transcoding
[codec] Codec G722/8000 added for transcoding with payload type 9
[internals] Adding codec 'G722'/'G722/8000'/'G722/8000/1' at pos (nil)
[codec] Updating supplemental codecs for tag_B #0
[codec] Setting up codec handlers for (null)tag_B(null) #0 -> (null)tag_A(null) 
#0
[codec] Default sink codec is PCMA/8000
[codec] Checking receiver codec PCMA/8000/1 (8)
[codec] Creating codec handler for PCMA/8000 (8)
[codec] Sink codec is PCMA/8000/1 (8)
[codec] Sink supports codec PCMA/8000 for passthrough
[codec] Using passthrough handler for PCMA/8000 with DTMF -1, CN -1
[codec] Checking receiver codec G722/8000/1 (9)
[codec] Creating codec handler for G722/8000 (9)
[codec] Sink codec is PCMA/8000/1 (8)
[codec] Created transcode context for G722/8000 (9) -> PCMA/8000 (8) with DTMF 
output -1 and CN output -1
[codec] Creating SSRC transcoder from G722/8000/1 to PCMA/8000/1
[internals] supported sample format for output codec pcm_alaw: s16
[internals] using output sample format s16 for codec pcm_alaw
[core] Initialized encoder with frame size 160 samples
[codec] Encoder created with clockrate 8000, 1 channels, using sample format 1 
(ptime 20 for 160 

Bug#1042128: marked as done (designate: FTBFS: AssertionError: len(context) = 6)

[Debian Bug Tracking System]

Your message dated Wed, 09 Aug 2023 12:51:51 +
with message-id 
and subject line Bug#1042128: fixed in designate 1:16.0.0-4
has caused the Debian Bug report #1042128,
regarding designate: FTBFS: AssertionError: len(context) = 6
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.)


-- 
1042128: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1042128
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: designate
Version: 1:16.0.0-3
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20230726 ftbfs-trixie

Hi,

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


Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> make[1]: pyversions: No such file or directory
> py3versions: no X-Python3-Version in control file, using supported versions
> if ! PYTHONPATH=. PYTHON=python3 python3 -m sphinx -b html doc/source 
> /<>/debian/designate-doc/usr/share/doc/designate-doc/html ; then 
> \
>   cat /tmp/sphinx-err-* ; \
>   exit 1 ; \
> fi
> Running Sphinx v5.3.0
> connecting events for openstackdocstheme
> making output directory... done
> Using openstackdocstheme Sphinx theme from 
> /usr/lib/python3/dist-packages/openstackdocstheme/theme
> [oslo_config.sphinxconfiggen] reading config generator instructions from 
> /<>/doc/source/../../etc/designate/designate-config-generator.conf
> [oslo_config.sphinxconfiggen] writing sample configuration to 
> /<>/doc/source/_static/designate.conf.sample
> [oslo_policy.sphinxpolicygen] reading config generator instructions from 
> /<>/doc/source/../../etc/designate/designate-policy-generator.conf
> [oslo_policy.sphinxpolicygen] writing sample policy to 
> /<>/doc/source/_static/designate.policy.yaml.sample
> building [mo]: targets for 0 po files that are out of date
> building [html]: targets for 76 source files that are out of date
> updating environment: [new config] 76 added, 0 changed, 0 removed
> reading sources... [  1%] admin/backends/agent
> reading sources... [  2%] admin/backends/akamai_v2
> reading sources... [  3%] admin/backends/bind9
> reading sources... [  5%] admin/backends/djbdns_agent
> reading sources... [  6%] admin/backends/gdnsd_agent
> reading sources... [  7%] admin/backends/index
> reading sources... [  9%] admin/backends/infoblox
> reading sources... [ 10%] admin/backends/knot2_agent
> reading sources... [ 11%] admin/backends/msdns_agent
> reading sources... [ 13%] admin/backends/ns1
> reading sources... [ 14%] admin/backends/pdns4
> reading sources... [ 15%] admin/blacklists
> reading sources... [ 17%] admin/config
> loading config file etc/designate/designate-config-generator.conf
> reading sources... [ 18%] admin/ha
> reading sources... [ 19%] admin/index
> reading sources... [ 21%] admin/multiple-pools
> reading sources... [ 22%] admin/notifications
> reading sources... [ 23%] admin/policy
> reading sources... [ 25%] admin/pool-scheduler
> reading sources... [ 26%] admin/pools
> reading sources... [ 27%] admin/production-guidelines
> reading sources... [ 28%] admin/quotas
> reading sources... [ 30%] admin/samples/config
> reading sources... [ 31%] admin/samples/index
> reading sources... [ 32%] admin/samples/policy-yaml
> reading sources... [ 34%] admin/support-matrix
> reading sources... [ 35%] admin/tlds
> reading sources... [ 36%] admin/troubleshooting
> reading sources... [ 38%] admin/upgrades/index
> reading sources... [ 39%] admin/upgrades/kilo
> reading sources... [ 40%] admin/upgrades/mitaka
> reading sources... [ 42%] admin/upgrades/newton
> reading sources... [ 43%] admin/upgrades/ocata
> reading sources... [ 44%] cli/designate-manage
> reading sources... [ 46%] cli/designate-status
> reading sources... [ 47%] cli/index
> reading sources... [ 48%] configuration/index
> reading sources... [ 50%] contributor/architecture
> reading sources... [ 51%] contributor/devstack
> reading sources... [ 52%] contributor/getting-involved
> reading sources... [ 53%] contributor/gmr
> reading sources... [ 55%] contributor/index
> reading sources... [ 56%] contributor/integrations
> reading sources... [ 57%] contributor/sourcedoc/api
> reading sources... [ 59%] contributor/sourcedoc/backend
> reading sources... [ 60%] contributor/sourcedoc/central
> reading sources... [ 61%] contributor/sourcedoc/index
> reading sources... [ 63%] contributor/sourcedoc/mdns
> reading sources... [ 64%] contributor/sourcedoc/objects
> reading sources... [ 65%] contributor/sourcedoc/quota
> reading sources... [ 67%] contributor/sourcedoc/sink
> reading sources... 

Processed: Bug#1042187 marked as pending in gnocchi

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1042187 [src:gnocchi] gnocchi: FTBFS: AttributeError: module 
'setuptools.command.easy_install' has no attribute 'get_script_header'
Added tag(s) pending.

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

Bug#1042187: marked as pending in gnocchi

[Thomas Goirand]

Control: tag -1 pending

Hello,

Bug #1042187 in gnocchi 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/openstack-team/services/gnocchi/-/commit/80be08a7bd6838fa256ce8829ce63e3599a6d0c7


* Add setup-fix-usage-of-deprecated-get_script_header.patch
(Closes: #1042187).


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1042187

Processed: found 1040049 in 0.70.3-1

[Debian Bug Tracking System]

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

> found 1040049 0.70.3-1
Bug #1040049 {Done: Jeremy Bícha } [libvte-2.91-0] 
gnome-terminal: crash with assertion failure on mouseover: row < m_start + m_len
Marked as found in versions vte2.91/0.70.3-1.
> thanks
Stopping processing here.

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

Bug#1042170: marked as done (python-oslo.vmware: FTBFS: ModuleNotFoundError: No module named 'cryptography')

[Debian Bug Tracking System]

Your message dated Wed, 9 Aug 2023 14:28:58 +0200
with message-id <6d07295c-60c0-88cf-11ea-1c44a17d7...@debian.org>
and subject line Not reproducible anymore
has caused the Debian Bug report #1042170,
regarding python-oslo.vmware: FTBFS: ModuleNotFoundError: No module named 
'cryptography'
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.)


-- 
1042170: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1042170
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-oslo.vmware
Version: 4.1.1-2
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20230726 ftbfs-trixie

Hi,

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


Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> make[1]: pyversions: No such file or directory
> py3versions: no X-Python3-Version in control file, using supported versions
> pkgos-dh_auto_test --no-py2 
> 'oslo_vmware\.tests\.(?!(.*test_service\.MemoryCacheTest\.test_shared_cache.*|.*test_exceptions\.ExceptionsTest\.test_vim_fault_exception_with_cause_and_details.*|.*test_exceptions\.ExceptionsTest\.test_vim_fault_exception.*))'
> + PKGOS_TEST_PARALLEL=yes
> + PKGOS_TEST_SERIAL=no
> + PYTHONS=disabled
> + PYTHON3S=disabled
> + TEST_PARALLEL_OPT=--parallel
> + TEST_SERIAL_OPT=
> + echo WARNING: --no-py2 is deprecated, and always on.
> WARNING: --no-py2 is deprecated, and always on.
> + shift
> + py3versions -vr
> + PYTHON3S=3.11
> + [ yes = no ]
> + [ no = yes ]
> + [ 3.11 = disabled ]
> + echo 3.11
> + cut -d. -f1
> + PYMAJOR=3
> + echo ===> Testing with python (python3)
> ===> Testing with python (python3)
> + pwd
> + [ -d /<>/debian/tmp/usr/lib/python3/dist-packages ]
> + [ -e .stestr.conf ]
> + [ -x /usr/bin/python3-stestr ]
> + STESTR=stestr
> + rm -rf .stestr
> + PYTHON=python3.11 stestr run --parallel --subunit 
> oslo_vmware\.tests\.(?!(.*test_service\.MemoryCacheTest\.test_shared_cache.*|.*test_exceptions\.ExceptionsTest\.test_vim_fault_exception_with_cause_and_details.*|.*test_exceptions\.ExceptionsTest\.test_vim_fault_exception.*))
> + subunit2pyunit
> 
> =
> Failures during discovery
> =
> --- import errors ---
> Failed to import test module: oslo_vmware.tests.test_api
> Traceback (most recent call last):
>   File "/usr/lib/python3.11/unittest/loader.py", line 407, in _find_test_path
> module = self._get_module_from_name(name)
>  
>   File "/usr/lib/python3.11/unittest/loader.py", line 350, in 
> _get_module_from_name
> __import__(name)
>   File "/<>/oslo_vmware/tests/test_api.py", line 22, in 
> from eventlet import greenthread
>   File "/usr/lib/python3/dist-packages/eventlet/__init__.py", line 17, in 
> 
> from eventlet import convenience
>   File "/usr/lib/python3/dist-packages/eventlet/convenience.py", line 7, in 
> 
> from eventlet.green import socket
>   File "/usr/lib/python3/dist-packages/eventlet/green/socket.py", line 21, in 
> 
> from eventlet.support import greendns
>   File "/usr/lib/python3/dist-packages/eventlet/support/greendns.py", line 
> 79, in 
> setattr(dns, pkg, import_patched('dns.' + pkg))
>   
>   File "/usr/lib/python3/dist-packages/eventlet/support/greendns.py", line 
> 61, in import_patched
> return patcher.import_patched(module_name, **modules)
>^^
>   File "/usr/lib/python3/dist-packages/eventlet/patcher.py", line 132, in 
> import_patched
> return inject(
>^^^
>   File "/usr/lib/python3/dist-packages/eventlet/patcher.py", line 109, in 
> inject
> module = __import__(module_name, {}, {}, module_name.split('.')[:-1])
>  
>   File "/usr/lib/python3/dist-packages/dns/dnssecalgs/__init__.py", line 5, 
> in 
> from dns.dnssecalgs.dsa import PrivateDSA, PrivateDSANSEC3SHA1
>   File "/usr/lib/python3/dist-packages/dns/dnssecalgs/dsa.py", line 3, in 
> 
> from cryptography.hazmat.backends import default_backend
> ModuleNotFoundError: No module named 'cryptography'
> 
> Failed to import test module: oslo_vmware.tests.test_image_transfer
> Traceback (most recent call last):
>   File "/usr/lib/python3.11/unittest/loader.py", line 407, in _find_test_path
> module = self._get_module_from_name(name)
>  
>   File "/usr/lib/python3.11/unittest/loader.py", line 350, in 
> 

Processed: Bug#1042128 marked as pending in designate

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1042128 [src:designate] designate: FTBFS: AssertionError: len(context) = 6
Added tag(s) pending.

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

Bug#1042128: marked as pending in designate

[Thomas Goirand]

Control: tag -1 pending

Hello,

Bug #1042128 in designate 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/openstack-team/services/designate/-/commit/2a9d81436b4e640474cb4c60f4c61d459f79d692


Add remove-blockdiag-from-admin-ha-doc.patch (Closes: #1042128).


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1042128

Processed: found 1040049 in 0.70.6-1

[Debian Bug Tracking System]

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

> found 1040049 0.70.6-1
Bug #1040049 {Done: Jeremy Bícha } [libvte-2.91-0] 
gnome-terminal: crash with assertion failure on mouseover: row < m_start + m_len
Marked as found in versions vte2.91/0.70.6-1.
> thanks
Stopping processing here.

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

Bug#1042050: marked as done (meson: FTBFS: ./b 52a78b9866/../test cases/failing build/2 hidden symbol/bobuser.c:4:(.text.startup+0x3): undefined reference to `hidden_function')

[Debian Bug Tracking System]

Your message dated Wed, 09 Aug 2023 11:35:49 +
with message-id 
and subject line Bug#1042050: fixed in gobject-introspection 1.76.1-5
has caused the Debian Bug report #1042050,
regarding meson: FTBFS: ./b 52a78b9866/../test cases/failing build/2 hidden 
symbol/bobuser.c:4:(.text.startup+0x3): undefined reference to `hidden_function'
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.)


-- 
1042050: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1042050
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: meson
Version: 1.2.0-1
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs

Hi,

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


Relevant part (hopefully):
> /usr/bin/ld: bobuser.p/bobuser.c.o: in function `main':
> ./b 52a78b9866/../test cases/failing build/2 hidden 
> symbol/bobuser.c:4:(.text.startup+0x3): undefined reference to 
> `hidden_function'
> collect2: error: ld returned 1 exit status


The full build log is available from:
http://qa-logs.debian.net/2023/07/24/meson_1.2.0-1_unstable.log

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

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

If you fail to reproduce this, please provide a build log and diff it with mine
so that we can identify if something relevant changed in the meantime.
--- End Message ---
--- Begin Message ---
Source: gobject-introspection
Source-Version: 1.76.1-5
Done: Simon McVittie 

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

Debian distribution maintenance software
pp.
Simon McVittie  (supplier of updated gobject-introspection 
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: Wed, 09 Aug 2023 11:26:45 +0100
Source: gobject-introspection
Architecture: source
Version: 1.76.1-5
Distribution: unstable
Urgency: medium
Maintainer: Debian GNOME Maintainers 

Changed-By: Simon McVittie 
Closes: 1042050
Changes:
 gobject-introspection (1.76.1-5) unstable; urgency=medium
 .
   * Team upload
 .
   [ Jeremy Bicha ]
   * Revert workaround for #1041499. Meson 1.2.1 fixed the underlying issue.
 .
   [ Simon McVittie ]
   * d/p/gdump-Fix-leaked-io-streams.patch:
 Add patch from upstream to fix some memory leaks.
 The leaks indirectly caused Meson's test suite to fail, because that
 test suite builds GObject projects with both GObject-Introspection and
 AddressSanitizer enabled. (Closes: #1042050)
Checksums-Sha1:
 fa13e3a268ca27e66aa8c6f97e5f75173e69172a 3520 
gobject-introspection_1.76.1-5.dsc
 64d8cf69a5f0c92bac5d7a6197aad82df717db23 49656 
gobject-introspection_1.76.1-5.debian.tar.xz
 0a54b7dbd0c1e729fcdc35ab40ea69488c61b948 9076 
gobject-introspection_1.76.1-5_source.buildinfo
Checksums-Sha256:
 1b26e264dbddf7f7d56e5864e1ee86776f44f3c7f6ca9b64fe2100ed80610d17 3520 
gobject-introspection_1.76.1-5.dsc
 3170ec6ea7696c9bf9024f09a920a97f632de47db25e4668bd3ef38da47a3f36 49656 
gobject-introspection_1.76.1-5.debian.tar.xz
 d9a7604c28a2c055ef7083faa0f0f8e6c9966543edf918c196b0dfa0671e2ba8 9076 
gobject-introspection_1.76.1-5_source.buildinfo
Files:
 859142275de16b3ef1fbc78031e61d3a 3520 devel optional 
gobject-introspection_1.76.1-5.dsc
 39d2f547757cc2110058b7e6e00bdc30 49656 devel optional 
gobject-introspection_1.76.1-5.debian.tar.xz
 1a8eb505380aa45dceb115016ceffb85 9076 devel optional 
gobject-introspection_1.76.1-5_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEENuxaZEik9e95vv6Y4FrhR4+BTE8FAmTTePwACgkQ4FrhR4+B
TE+vWRAAsc5VsXU4dhU6kM5mpyPl3OIKS0gskhEMTQn4e3IuX/yBMLYhGsJq8rK0
1+kTuMW7OPh11bTW1wfkol/DRqq7V4q3DdpaObo/LqCXgEfgf5onlP3zhRB2dS3m
Nx9fhgqJ50BjKw7vCQAzwXkpvs38CCCesivz+dlLEz1uBIKP/N7m43cTOKaK1zfZ
WFoytqinbVBLEe7qVf5PJ8vfrawQaWk1gyeWvw4ck6LNyd8dsnCSCV7uHmbj0aZt
zyz8iiW3/PDwePjOj79tYlusx36vRzmmkB9CslM4y0sujjDL/9CBnAt4SrBVrFXb

Processed: Bug#1042050 marked as pending in gobject-introspection

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1042050 [gobject-introspection] meson: FTBFS: ./b 52a78b9866/../test 
cases/failing build/2 hidden symbol/bobuser.c:4:(.text.startup+0x3): undefined 
reference to `hidden_function'
Added tag(s) pending.

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

Bug#1042050: marked as pending in gobject-introspection

[Simon McVittie]

Control: tag -1 pending

Hello,

Bug #1042050 in gobject-introspection 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/gnome-team/gobject-introspection/-/commit/47c538cb63225afd8689be1bb120a706526ace9d


Add patch from upstream to fix some memory leaks

This indirectly causes Meson's test suite to fail, because that test
suite builds GObject projects with both GObject-Introspection and
AddressSanitizer enabled.

Closes: #1042050


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1042050

Bug#1041203: marked as done (FTBFS: InvalidRequirement: Expected end or semicolon)

[Debian Bug Tracking System]

Your message dated Wed, 09 Aug 2023 10:49:15 +
with message-id 
and subject line Bug#1042180: fixed in macs 2.2.9.1-1
has caused the Debian Bug report #1042180,
regarding FTBFS: InvalidRequirement: Expected end or semicolon
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.)


-- 
1042180: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1042180
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: macs
Version: 2.2.7.1-6
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)

Hi!
I'm afraid your package fails to build, with:
pkg_resources.extern.packaging._tokenizer.ParserSyntaxError: Expected end or 
semicolon (after name and no valid version specifier)
numpy>=>=1.17

Full log attached.


Meow!
-- System Information:
Debian Release: trixie/sid
  APT prefers unstable-debug
  APT policy: (500, 'unstable-debug'), (500, 'unstable'), (500, 'stable'), 
(120, 'experimental'), (1, 'experimental-debug')
merged-usr: no
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 6.5.0-rc1-00036-gc493f11e457d (SMP w/64 CPU threads; PREEMPT)
Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)
sbuild (Debian sbuild) 0.85.2 (11 March 2023) on valinor.angband.pl

+==+
| macs (amd64) Sat, 15 Jul 2023 15:59:52 + |
+==+

Package: macs
Distribution: unstable
Machine Architecture: amd64
Host Architecture: amd64
Build Architecture: amd64
Build Type: binary

I: NOTICE: Log filtering will replace 
'var/run/schroot/mount/unstable-amd64-sbuild-6c3ec2b5-ebd2-4821-9c2c-b590aa40ebd9'
 with '<>'
I: NOTICE: Log filtering will replace 'build/macs-QwMUa0/resolver-kV6wWG' with 
'<>'

+--+
| Update chroot|
+--+

Get:1 http://apt-rosy.angband.pl:3142/debian unstable InRelease [199 kB]
Get:2 http://apt-rosy.angband.pl:3142/debian unstable/main Sources.diff/Index 
[63.6 kB]
Get:3 http://apt-rosy.angband.pl:3142/debian unstable/main amd64 
Packages.diff/Index [63.6 kB]
Get:4 http://apt-rosy.angband.pl:3142/debian unstable/main Sources 
T-2023-07-15-1409.27-F-2023-07-15-1409.27.pdiff [38.2 kB]
Get:4 http://apt-rosy.angband.pl:3142/debian unstable/main Sources 
T-2023-07-15-1409.27-F-2023-07-15-1409.27.pdiff [38.2 kB]
Get:5 http://apt-rosy.angband.pl:3142/debian unstable/main amd64 Packages 
T-2023-07-15-1409.27-F-2023-07-15-1409.27.pdiff [14.4 kB]
Get:5 http://apt-rosy.angband.pl:3142/debian unstable/main amd64 Packages 
T-2023-07-15-1409.27-F-2023-07-15-1409.27.pdiff [14.4 kB]
Fetched 379 kB in 1s (275 kB/s)
Reading package lists...
Reading package lists...
Building dependency tree...
Reading state information...
Calculating upgrade...
The following packages will be upgraded:
  libtool
1 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
Need to get 517 kB of archives.
After this operation, 0 B of additional disk space will be used.
Get:1 http://apt-rosy.angband.pl:3142/debian unstable/main amd64 libtool all 
2.4.7-6 [517 kB]
debconf: delaying package configuration, since apt-utils is not installed
Fetched 517 kB in 0s (16.6 MB/s)
(Reading database ... 
(Reading database ... 5%
(Reading database ... 10%
(Reading database ... 15%
(Reading database ... 20%
(Reading database ... 25%
(Reading database ... 30%
(Reading database ... 35%
(Reading database ... 40%
(Reading database ... 45%
(Reading database ... 50%
(Reading database ... 55%
(Reading database ... 60%
(Reading database ... 65%
(Reading database ... 70%
(Reading database ... 75%
(Reading database ... 80%
(Reading database ... 85%
(Reading database ... 90%
(Reading database ... 95%
(Reading database ... 100%
(Reading database ... 14595 files and directories currently installed.)
Preparing to unpack .../libtool_2.4.7-6_all.deb ...
Unpacking libtool (2.4.7-6) over (2.4.7-5) ...
Setting up libtool (2.4.7-6) ...
Processing triggers for man-db (2.11.2-2) ...

+--+
| Fetch source files   |
+--+


Check APT

Bug#1042180: marked as done (macs: FTBFS: dpkg-buildpackage: error: dpkg-source -b . subprocess returned exit status 2)

[Debian Bug Tracking System]

Your message dated Wed, 09 Aug 2023 10:49:15 +
with message-id 
and subject line Bug#1042180: fixed in macs 2.2.9.1-1
has caused the Debian Bug report #1042180,
regarding macs: FTBFS: dpkg-buildpackage: error: dpkg-source -b . subprocess 
returned exit status 2
to be marked as done.

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

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


-- 
1042180: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1042180
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: macs
Version: 2.2.7.1-6
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20230726 ftbfs-trixie

Hi,

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


Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> dh_auto_clean || true
> I: pybuild base:240: python3.11 setup.py clean 
> /usr/lib/python3/dist-packages/setuptools/__init__.py:84: 
> _DeprecatedInstaller: setuptools.installer and fetch_build_eggs are 
> deprecated.
> !!
> 
> 
> 
> Requirements should be satisfied by a PEP 517 installer.
> If you are using pip, you can try `pip install --use-pep517`.
> 
> 
> 
> !!
>   dist.fetch_build_eggs(dist.setup_requires)
> Traceback (most recent call last):
>   File 
> "/usr/lib/python3/dist-packages/pkg_resources/_vendor/packaging/requirements.py",
>  line 35, in __init__
> parsed = _parse_requirement(requirement_string)
>  ^^
>   File 
> "/usr/lib/python3/dist-packages/pkg_resources/_vendor/packaging/_parser.py", 
> line 64, in parse_requirement
> return _parse_requirement(Tokenizer(source, rules=DEFAULT_RULES))
>^^
>   File 
> "/usr/lib/python3/dist-packages/pkg_resources/_vendor/packaging/_parser.py", 
> line 82, in _parse_requirement
> url, specifier, marker = _parse_requirement_details(tokenizer)
>  ^
>   File 
> "/usr/lib/python3/dist-packages/pkg_resources/_vendor/packaging/_parser.py", 
> line 126, in _parse_requirement_details
> marker = _parse_requirement_marker(
>  ^^
>   File 
> "/usr/lib/python3/dist-packages/pkg_resources/_vendor/packaging/_parser.py", 
> line 147, in _parse_requirement_marker
> tokenizer.raise_syntax_error(
>   File 
> "/usr/lib/python3/dist-packages/pkg_resources/_vendor/packaging/_tokenizer.py",
>  line 165, in raise_syntax_error
> raise ParserSyntaxError(
> pkg_resources.extern.packaging._tokenizer.ParserSyntaxError: Expected end or 
> semicolon (after name and no valid version specifier)
> numpy>=>=1.17
>  ^
> 
> The above exception was the direct cause of the following exception:
> 
> Traceback (most recent call last):
>   File "/<>/setup.py", line 84, in 
> main()
>   File "/<>/setup.py", line 51, in main
> setup(name="MACS2",
>   File "/usr/lib/python3/dist-packages/setuptools/__init__.py", line 106, in 
> setup
> _install_setup_requires(attrs)
>   File "/usr/lib/python3/dist-packages/setuptools/__init__.py", line 79, in 
> _install_setup_requires
> _fetch_build_eggs(dist)
>   File "/usr/lib/python3/dist-packages/setuptools/__init__.py", line 84, in 
> _fetch_build_eggs
> dist.fetch_build_eggs(dist.setup_requires)
>   File "/usr/lib/python3/dist-packages/setuptools/dist.py", line 907, in 
> fetch_build_eggs
> return _fetch_build_eggs(self, requires)
>^
>   File "/usr/lib/python3/dist-packages/setuptools/installer.py", line 38, in 
> _fetch_build_eggs
> resolved_dists = pkg_resources.working_set.resolve(
>  ^^
>   File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 806, 
> in resolve
> requirements = list(requirements)[::-1]
>^^
>   File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 3174, 
> in __init__
> super(Requirement, self).__init__(requirement_string)
>   File 
> "/usr/lib/python3/dist-packages/pkg_resources/_vendor/packaging/requirements.py",
>  line 37, in __init__
> raise InvalidRequirement(str(e)) from e
> pkg_resources.extern.packaging.requirements.InvalidRequirement: Expected end 
> or semicolon (after name and no valid version specifier)
> numpy>=>=1.17
>  ^
> E: 

Bug#1041203: marked as done (FTBFS: InvalidRequirement: Expected end or semicolon)

[Debian Bug Tracking System]

Your message dated Wed, 09 Aug 2023 10:49:15 +
with message-id 
and subject line Bug#1041203: fixed in macs 2.2.9.1-1
has caused the Debian Bug report #1041203,
regarding FTBFS: InvalidRequirement: Expected end or semicolon
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.)


-- 
1041203: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1041203
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: macs
Version: 2.2.7.1-6
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)

Hi!
I'm afraid your package fails to build, with:
pkg_resources.extern.packaging._tokenizer.ParserSyntaxError: Expected end or 
semicolon (after name and no valid version specifier)
numpy>=>=1.17

Full log attached.


Meow!
-- System Information:
Debian Release: trixie/sid
  APT prefers unstable-debug
  APT policy: (500, 'unstable-debug'), (500, 'unstable'), (500, 'stable'), 
(120, 'experimental'), (1, 'experimental-debug')
merged-usr: no
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 6.5.0-rc1-00036-gc493f11e457d (SMP w/64 CPU threads; PREEMPT)
Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)
sbuild (Debian sbuild) 0.85.2 (11 March 2023) on valinor.angband.pl

+==+
| macs (amd64) Sat, 15 Jul 2023 15:59:52 + |
+==+

Package: macs
Distribution: unstable
Machine Architecture: amd64
Host Architecture: amd64
Build Architecture: amd64
Build Type: binary

I: NOTICE: Log filtering will replace 
'var/run/schroot/mount/unstable-amd64-sbuild-6c3ec2b5-ebd2-4821-9c2c-b590aa40ebd9'
 with '<>'
I: NOTICE: Log filtering will replace 'build/macs-QwMUa0/resolver-kV6wWG' with 
'<>'

+--+
| Update chroot|
+--+

Get:1 http://apt-rosy.angband.pl:3142/debian unstable InRelease [199 kB]
Get:2 http://apt-rosy.angband.pl:3142/debian unstable/main Sources.diff/Index 
[63.6 kB]
Get:3 http://apt-rosy.angband.pl:3142/debian unstable/main amd64 
Packages.diff/Index [63.6 kB]
Get:4 http://apt-rosy.angband.pl:3142/debian unstable/main Sources 
T-2023-07-15-1409.27-F-2023-07-15-1409.27.pdiff [38.2 kB]
Get:4 http://apt-rosy.angband.pl:3142/debian unstable/main Sources 
T-2023-07-15-1409.27-F-2023-07-15-1409.27.pdiff [38.2 kB]
Get:5 http://apt-rosy.angband.pl:3142/debian unstable/main amd64 Packages 
T-2023-07-15-1409.27-F-2023-07-15-1409.27.pdiff [14.4 kB]
Get:5 http://apt-rosy.angband.pl:3142/debian unstable/main amd64 Packages 
T-2023-07-15-1409.27-F-2023-07-15-1409.27.pdiff [14.4 kB]
Fetched 379 kB in 1s (275 kB/s)
Reading package lists...
Reading package lists...
Building dependency tree...
Reading state information...
Calculating upgrade...
The following packages will be upgraded:
  libtool
1 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
Need to get 517 kB of archives.
After this operation, 0 B of additional disk space will be used.
Get:1 http://apt-rosy.angband.pl:3142/debian unstable/main amd64 libtool all 
2.4.7-6 [517 kB]
debconf: delaying package configuration, since apt-utils is not installed
Fetched 517 kB in 0s (16.6 MB/s)
(Reading database ... 
(Reading database ... 5%
(Reading database ... 10%
(Reading database ... 15%
(Reading database ... 20%
(Reading database ... 25%
(Reading database ... 30%
(Reading database ... 35%
(Reading database ... 40%
(Reading database ... 45%
(Reading database ... 50%
(Reading database ... 55%
(Reading database ... 60%
(Reading database ... 65%
(Reading database ... 70%
(Reading database ... 75%
(Reading database ... 80%
(Reading database ... 85%
(Reading database ... 90%
(Reading database ... 95%
(Reading database ... 100%
(Reading database ... 14595 files and directories currently installed.)
Preparing to unpack .../libtool_2.4.7-6_all.deb ...
Unpacking libtool (2.4.7-6) over (2.4.7-5) ...
Setting up libtool (2.4.7-6) ...
Processing triggers for man-db (2.11.2-2) ...

+--+
| Fetch source files   |
+--+


Check APT

Bug#1042180: marked as done (macs: FTBFS: dpkg-buildpackage: error: dpkg-source -b . subprocess returned exit status 2)

[Debian Bug Tracking System]

Your message dated Wed, 09 Aug 2023 10:49:15 +
with message-id 
and subject line Bug#1041203: fixed in macs 2.2.9.1-1
has caused the Debian Bug report #1041203,
regarding macs: FTBFS: dpkg-buildpackage: error: dpkg-source -b . subprocess 
returned exit status 2
to be marked as done.

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

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


-- 
1041203: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1041203
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: macs
Version: 2.2.7.1-6
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20230726 ftbfs-trixie

Hi,

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


Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> dh_auto_clean || true
> I: pybuild base:240: python3.11 setup.py clean 
> /usr/lib/python3/dist-packages/setuptools/__init__.py:84: 
> _DeprecatedInstaller: setuptools.installer and fetch_build_eggs are 
> deprecated.
> !!
> 
> 
> 
> Requirements should be satisfied by a PEP 517 installer.
> If you are using pip, you can try `pip install --use-pep517`.
> 
> 
> 
> !!
>   dist.fetch_build_eggs(dist.setup_requires)
> Traceback (most recent call last):
>   File 
> "/usr/lib/python3/dist-packages/pkg_resources/_vendor/packaging/requirements.py",
>  line 35, in __init__
> parsed = _parse_requirement(requirement_string)
>  ^^
>   File 
> "/usr/lib/python3/dist-packages/pkg_resources/_vendor/packaging/_parser.py", 
> line 64, in parse_requirement
> return _parse_requirement(Tokenizer(source, rules=DEFAULT_RULES))
>^^
>   File 
> "/usr/lib/python3/dist-packages/pkg_resources/_vendor/packaging/_parser.py", 
> line 82, in _parse_requirement
> url, specifier, marker = _parse_requirement_details(tokenizer)
>  ^
>   File 
> "/usr/lib/python3/dist-packages/pkg_resources/_vendor/packaging/_parser.py", 
> line 126, in _parse_requirement_details
> marker = _parse_requirement_marker(
>  ^^
>   File 
> "/usr/lib/python3/dist-packages/pkg_resources/_vendor/packaging/_parser.py", 
> line 147, in _parse_requirement_marker
> tokenizer.raise_syntax_error(
>   File 
> "/usr/lib/python3/dist-packages/pkg_resources/_vendor/packaging/_tokenizer.py",
>  line 165, in raise_syntax_error
> raise ParserSyntaxError(
> pkg_resources.extern.packaging._tokenizer.ParserSyntaxError: Expected end or 
> semicolon (after name and no valid version specifier)
> numpy>=>=1.17
>  ^
> 
> The above exception was the direct cause of the following exception:
> 
> Traceback (most recent call last):
>   File "/<>/setup.py", line 84, in 
> main()
>   File "/<>/setup.py", line 51, in main
> setup(name="MACS2",
>   File "/usr/lib/python3/dist-packages/setuptools/__init__.py", line 106, in 
> setup
> _install_setup_requires(attrs)
>   File "/usr/lib/python3/dist-packages/setuptools/__init__.py", line 79, in 
> _install_setup_requires
> _fetch_build_eggs(dist)
>   File "/usr/lib/python3/dist-packages/setuptools/__init__.py", line 84, in 
> _fetch_build_eggs
> dist.fetch_build_eggs(dist.setup_requires)
>   File "/usr/lib/python3/dist-packages/setuptools/dist.py", line 907, in 
> fetch_build_eggs
> return _fetch_build_eggs(self, requires)
>^
>   File "/usr/lib/python3/dist-packages/setuptools/installer.py", line 38, in 
> _fetch_build_eggs
> resolved_dists = pkg_resources.working_set.resolve(
>  ^^
>   File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 806, 
> in resolve
> requirements = list(requirements)[::-1]
>^^
>   File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 3174, 
> in __init__
> super(Requirement, self).__init__(requirement_string)
>   File 
> "/usr/lib/python3/dist-packages/pkg_resources/_vendor/packaging/requirements.py",
>  line 37, in __init__
> raise InvalidRequirement(str(e)) from e
> pkg_resources.extern.packaging.requirements.InvalidRequirement: Expected end 
> or semicolon (after name and no valid version specifier)
> numpy>=>=1.17
>  ^
> E: 

Bug#1031751: marked as done (rust-ahash: autopkgtest failure)

[Debian Bug Tracking System]

Your message dated Wed, 09 Aug 2023 10:50:14 +
with message-id 
and subject line Bug#1031751: fixed in rust-ahash 0.8.3-5
has caused the Debian Bug report #1031751,
regarding rust-ahash: autopkgtest failure
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.)


-- 
1031751: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1031751
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: rust-ahash
Version: 0.8.3-2
Severity: serious

https://ci.debian.net/data/autopkgtest/testing/amd64/r/rust-ahash/31558299/log.gz

...
Testing map/aHash-alias
thread 'main' panicked at 'attempt to add with overflow', 
/usr/src/rustc-1.63.0/library/core/src/ops/arith.rs:786:1
stack backtrace:
   0: rust_begin_unwind
 at /usr/src/rustc-1.63.0/library/std/src/panicking.rs:584:5
   1: core::panicking::panic_fmt
 at /usr/src/rustc-1.63.0/library/core/src/panicking.rs:142:14
   2: core::panicking::panic
 at /usr/src/rustc-1.63.0/library/core/src/panicking.rs:48:5
   3: ::add_assign
 at /usr/src/rustc-1.63.0/library/core/src/ops/arith.rs:779:51
   4: >::add_assign
 at /usr/src/rustc-1.63.0/library/core/src/internal_macros.rs:127:17
   5: ahash::bench_map::{{closure}}::{{closure}}
 at ./tests/bench.rs:124:25
   6: criterion::bencher::Bencher::iter
 at /usr/share/cargo/registry/criterion-0.3.6/src/bencher.rs:88:23
   7: ahash::bench_map::{{closure}}
 at ./tests/bench.rs:119:13
   8: criterion::benchmark_group::BenchmarkGroup::bench_function::{{closure}}
 at 
/usr/share/cargo/registry/criterion-0.3.6/src/benchmark_group.rs:254:60
   9:  as 
criterion::routine::Routine>::bench::{{closure}}
 at /usr/share/cargo/registry/criterion-0.3.6/src/routine.rs:209:17
  10: core::iter::adapters::map::map_fold::{{closure}}
 at 
/usr/src/rustc-1.63.0/library/core/src/iter/adapters/map.rs:84:28
  11: core::iter::traits::iterator::Iterator::fold
 at 
/usr/src/rustc-1.63.0/library/core/src/iter/traits/iterator.rs:2370:21
  12:  as 
core::iter::traits::iterator::Iterator>::fold
 at 
/usr/src/rustc-1.63.0/library/core/src/iter/adapters/map.rs:124:9
  13: core::iter::traits::iterator::Iterator::for_each
 at 
/usr/src/rustc-1.63.0/library/core/src/iter/traits/iterator.rs:787:9
  14:  as 
alloc::vec::spec_extend::SpecExtend>::spec_extend
 at /usr/src/rustc-1.63.0/library/alloc/src/vec/spec_extend.rs:40:17
  15:  as 
alloc::vec::spec_from_iter_nested::SpecFromIterNested>::from_iter
 at 
/usr/src/rustc-1.63.0/library/alloc/src/vec/spec_from_iter_nested.rs:62:9
  16:  as 
alloc::vec::spec_from_iter::SpecFromIter>::from_iter
 at 
/usr/src/rustc-1.63.0/library/alloc/src/vec/spec_from_iter.rs:33:9
  17:  as 
core::iter::traits::collect::FromIterator>::from_iter
 at /usr/src/rustc-1.63.0/library/alloc/src/vec/mod.rs:2645:9
  18: core::iter::traits::iterator::Iterator::collect
 at 
/usr/src/rustc-1.63.0/library/core/src/iter/traits/iterator.rs:1792:9
  19:  as 
criterion::routine::Routine>::bench
 at /usr/share/cargo/registry/criterion-0.3.6/src/routine.rs:205:9
  20: criterion::routine::Routine::test
 at /usr/share/cargo/registry/criterion-0.3.6/src/routine.rs:18:9
  21: criterion::benchmark_group::BenchmarkGroup::run_bench
 at 
/usr/share/cargo/registry/criterion-0.3.6/src/benchmark_group.rs:339:21
  22: criterion::benchmark_group::BenchmarkGroup::bench_function
 at 
/usr/share/cargo/registry/criterion-0.3.6/src/benchmark_group.rs:254:9
  23: ahash::bench_map
 at ./tests/bench.rs:118:9
  24: ahash::benches
 at /usr/share/cargo/registry/criterion-0.3.6/src/macros.rs:71:17
  25: ahash::main
 at /usr/share/cargo/registry/criterion-0.3.6/src/macros.rs:127:17
  26: core::ops::function::FnOnce::call_once
 at /usr/src/rustc-1.63.0/library/core/src/ops/function.rs:248:5
note: Some details are omitted, run with `RUST_BACKTRACE=full` for a verbose 
backtrace.

error: test failed, to rerun pass `--bench ahash`
autopkgtest [13:15:47]: test rust-ahash-0.8:@: ---]
autopkgtest [13:15:47]: test rust-ahash-0.8:@:  - - - - - - - - - - results - - 
- - - - - - - -
rust-ahash-0.8:@ FAIL non-zero exit status 101
...
autopkgtest [13:31:10]:  summary
rust-ahash-0.8:@ FAIL non-zero exit status 101
rust-ahash-0.8:default FAIL non-zero exit status 101
rust-ahash-0.8:std   FAIL non-zero exit status 101

Bug#1043336: collectd: Recommends unavailable package "libgps28"

[Debian/GNU]

Package: collectd
Version: 5.12.0-14
Severity: serious
Justification: Policy 2.2.1

Dear Maintainer,


collectd Recommens the binary package "libgps28".
However, "libgps28" has been superseded by "libgps30" after the bookworm
release and is no longer available.

Since this is contradition with the debian policy [2.2.1], would
you be so kind and remove the offending "Recommends" line?

I guess this should have been caught by some gpsd-transition, dunno why
this didn't trigger a binNMU...

cheers

[2.2.1] 
https://www.debian.org/doc/debian-policy/ch-archive.html#the-main-archive-area

Bug#1043062: marked as done (fenics-basix: requires source-only upload for testing migration)

[Debian Bug Tracking System]

Your message dated Wed, 09 Aug 2023 09:19:00 +
with message-id 
and subject line Bug#1043062: fixed in fenics-basix 0.6.0-6
has caused the Debian Bug report #1043062,
regarding fenics-basix: requires source-only upload for testing migration
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.)


-- 
1043062: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1043062
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: fenics-basix
Version: 0.6.0-5
Severity: serious
X-Debbugs-Cc: sramac...@debian.org

Issues preventing migration:
∙ ∙ Not built on buildd: arch all binaries uploaded by dparsons, a new 
source-only upload is needed to allow migration

Cheers
-- 
Sebastian Ramacher
--- End Message ---
--- Begin Message ---
Source: fenics-basix
Source-Version: 0.6.0-6
Done: Drew Parsons 

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

Debian distribution maintenance software
pp.
Drew Parsons  (supplier of updated fenics-basix 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: Wed, 09 Aug 2023 10:15:34 +0200
Source: fenics-basix
Architecture: source
Version: 0.6.0-6
Distribution: unstable
Urgency: medium
Maintainer: Debian Science Team 

Changed-By: Drew Parsons 
Closes: 1043062
Changes:
 fenics-basix (0.6.0-6) unstable; urgency=medium
 .
   * source-only upload for migration to testing. Closes: #1043062.
Checksums-Sha1:
 6051a43bd8c8887baf546662ab1605567f525c45 2780 fenics-basix_0.6.0-6.dsc
 8f3c6ea06587fd5477c0c709d5170ed8a3c37163 9376 
fenics-basix_0.6.0-6.debian.tar.xz
Checksums-Sha256:
 7620794f718f5be172960655a43e98e5fa10b616f6645d1a77cdc9b1d11bab40 2780 
fenics-basix_0.6.0-6.dsc
 26fad59621b464c94084a9b5c44e3857b4652d6ed5714ebd730810a5d6aa13a0 9376 
fenics-basix_0.6.0-6.debian.tar.xz
Files:
 ce4c5dc7b970b973eb3af5dbe245e3d7 2780 python optional fenics-basix_0.6.0-6.dsc
 509448b2fd60d53678dff9832a7c407d 9376 python optional 
fenics-basix_0.6.0-6.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEI8mpPlhYGekSbQo2Vz7x5L1aAfoFAmTTUIkACgkQVz7x5L1a
AfrB7hAArpf1d2rddKWSos0+yR4XLk6IyTDX9MaSYdGW+F7EjCfgCbLUo9z2PV+y
gq1TedoDGDTHE3jrar7UI4lJzn7R6U4LiYyOGOAiWUtiPmyGRH6XMq/M4wql/4Zp
9xFaQ85Wa71rL9EFwF8Oza/ixcFu+39RMDiDZ68LBuImhmNwmY9yLdgqJ65+u13y
RfrtqgxkUSOHckbeeQc48FnRsp0yKrnA8H4Fe24T37v52QaBlGmUUNzL5abcQmJX
S7kTJoR0tApdnW32QC+N91YQV+9ZL36UdgA3U5OX+23GMRY3J2W/3tHobZSFot32
paGni2IJZeNqN4+8Fdu8ZqD6J8Rbdd4HEx+MDFaZOCzbS6b3w2uh2lO3f3aTIXXv
lgfe2NQWhCfDvsuFtxU67OD6XkIiomuhje6tR2U6z6IRlmWG9PLgUljMcWh7KmIw
KV/oxXKLb7u2KTLkOTkEAojcuO6LH9jM4sGhh93mtHXgKuX2YwUdk/3tIVPZLKqi
JY94fueoNmxeDfILzSgqjcY7ZgMENEgCvs04LtyBfvkgiKYBHYWSBH2VlyivWhOf
7YTRiDYJRQaSDXOhzc93VG55xrMFeuxFGXXbrQzTTmnQT74SzzZ7W30MWT8mVcyD
K/YdmRkdkS5nLUdBlsAwNxCQvCsKLGQrIsdpv5Cg8tn9O2YTNKQ=
=54v9
-END PGP SIGNATURE End Message ---

Bug#1043333: python3-sugar3: Recommends unavailable package 'telepathy-salut'

[Debian/GNU]

Package: python3-sugar3
Version: 0.120-1
Severity: serious
Justification: Policy 2.2.1

Dear Maintainer,

python3-sugar3 Recommens the binary package "telepathy-salut".
However, "telepathy-salut" has been removed in 2022-12 from both
unstable and testing (bookworm, thus now stable).
See bug [938645]

Since this is contradition with the debian policy [2.2.1], would
you be so kind and remove the offending "Recommends" line?

cheers

[938645] https://bugs.debian.org/938645
[2.2.1] 
https://www.debian.org/doc/debian-policy/ch-archive.html#the-main-archive-area

Processed: Re: Bug#1039724: gpgme: building underbookworm fails with no matches in python3-gpg.install

[Debian Bug Tracking System]

Processing control commands:

> notfound -1 gpgme1.0/1.18.0-3
Bug #1039724 [src:gpgme1.0] gpgme: building underbookworm fails with no matches 
in python3-gpg.install
No longer marked as found in versions gpgme1.0/1.18.0-3.
> tags -1 wontfix - ftbfs moreinfo
Bug #1039724 [src:gpgme1.0] gpgme: building underbookworm fails with no matches 
in python3-gpg.install
Added tag(s) wontfix.
Bug #1039724 [src:gpgme1.0] gpgme: building underbookworm fails with no matches 
in python3-gpg.install
Removed tag(s) moreinfo and ftbfs.
> severity -1 minor
Bug #1039724 [src:gpgme1.0] gpgme: building underbookworm fails with no matches 
in python3-gpg.install
Severity set to 'minor' from 'serious'

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

Bug#1039724: gpgme: building underbookworm fails with no matches in python3-gpg.install

[Bastian Germann]

Control: notfound -1 gpgme1.0/1.18.0-3
Control: tags -1 wontfix - ftbfs moreinfo
Control: severity -1 minor

Tagging this according to the conversation.

Bug#1041270: dynarmic: broke ABI without SONAME bump

[Andrea Pappacoda]

Hi all, I've uploaded a fixed Dynarmic package a while back on mentors, if 
somebody could upload it for me it'd be great.

I'm currently on vacation, so I don't have access to a computer and won't be 
able to make changes to it, but it should be fine.

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

Thanks!

Il 21 luglio 2023 16:50:01 CEST, Andrea Pappacoda  ha 
scritto:
>> Hi Sebastian, thanks for your report. I've uploaded a new version with 
>> a possible fix on Mentors, you can find it at 
>> . I've also attached a 
>> debdiff for your convenience.
>> 
>> Feel free to upload it to unstable if you find this solution 
>> reasonable. Since this is only a soname change, without any actual 
>> library change, I believe that uploading to experimental first is 
>> unnecessary.
>> 
>> If it doesn't look right to you, I'll be happy to hear your feedback :)
>
>My previous solution was broken since it introduced a new package with
>the same contents as the older libdynarmic6 package, causing an unpack
>error. Luckly upstream has merged my patch and tagged a new release,
>so I simply updated to the new upstream version, getting rid of the file
>conflict and bumping the ABI.
>
>I don't have access to my private OpenPGP keys right now, so I can't upload
>the new release on Mentors, but I'll attach a debdiff nonetheless containing
>the 6.5.0-1 release. You can also find it on Salsa at
>.

Bug#1042200: marked as done (freesasa: FTBFS: ./src/./src/cif.cc:276:(.text+0x86a4): undefined reference to `gemmi::make_structure_from_block(gemmi::cif::Block const&)')

[Debian Bug Tracking System]

Your message dated Wed, 09 Aug 2023 06:19:21 +
with message-id 
and subject line Bug#1042200: fixed in freesasa 2.1.2-2
has caused the Debian Bug report #1042200,
regarding freesasa: FTBFS: ./src/./src/cif.cc:276:(.text+0x86a4): undefined 
reference to `gemmi::make_structure_from_block(gemmi::cif::Block const&)'
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.)


-- 
1042200: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1042200
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: freesasa
Version: 2.1.2-1
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20230726 ftbfs-trixie

Hi,

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


Relevant part (hopefully):
> /usr/bin/ld: cif.o: in function `freesasa_cif_structure_array(_IO_FILE*, 
> int*, freesasa_classifier const*, int)':
> ./src/./src/cif.cc:276:(.text+0x86a4): undefined reference to 
> `gemmi::make_structure_from_block(gemmi::cif::Block const&)'
> collect2: error: ld returned 1 exit status


The full build log is available from:
http://qa-logs.debian.net/2023/07/26/freesasa_2.1.2-1_unstable.log

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

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

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

If you fail to reproduce this, please provide a build log and diff it with mine
so that we can identify if something relevant changed in the meantime.
--- End Message ---
--- Begin Message ---
Source: freesasa
Source-Version: 2.1.2-2
Done: Andrius Merkys 

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

Debian distribution maintenance software
pp.
Andrius Merkys  (supplier of updated freesasa 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: Wed, 09 Aug 2023 01:59:45 -0400
Source: freesasa
Architecture: source
Version: 2.1.2-2
Distribution: unstable
Urgency: medium
Maintainer: Debichem Team 
Changed-By: Andrius Merkys 
Closes: 1042200
Changes:
 freesasa (2.1.2-2) unstable; urgency=medium
 .
   * Link against libgemmi_cpp.a (Closes: #1042200)
   * Drop no-lc++.patch: fix moved to debian/rules.
   * Update standards version to 4.6.2, no changes needed.
   * Bump copyright years.
Checksums-Sha1:
 21092884b785e7f8886ab622a0f5515ab1c4351f 2016 freesasa_2.1.2-2.dsc
 6b151bbe64cc4523c2748f0ebe91f1a9b6e6cb63 3324 freesasa_2.1.2-2.debian.tar.xz
 582444eda54e3c75a244fdd785ed03f7460adc6b 6939 freesasa_2.1.2-2_source.buildinfo
Checksums-Sha256:
 efb52a02affeec0b5c7c30ca9d4f40e9299f9e055b3fd65016f51e778128a5b0 2016 
freesasa_2.1.2-2.dsc
 ad523cef1f592c79fbc872fe6b8a5d75676f02ac9ddf34ef40271dd4b52f740b 3324 
freesasa_2.1.2-2.debian.tar.xz
 00dd3fd26f404ed4e7ce989c50e66aeba79d45509ea49939acbfdd8d0522680f 6939 
freesasa_2.1.2-2_source.buildinfo
Files:
 695b8c8d5732c73a9e93a20c25e57fcf 2016 science optional freesasa_2.1.2-2.dsc
 2206ab46aaf32a411f849fa81837b51f 3324 science optional 
freesasa_2.1.2-2.debian.tar.xz
 6caa5771d5c09b8db056ebe61755e1c2 6939 science optional 
freesasa_2.1.2-2_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJGBAEBCgAwFiEEdyKS9veshfrgQdQe5fQ/nCc08ocFAmTTK3oSHG1lcmt5c0Bk
ZWJpYW4ub3JnAAoJEOX0P5wnNPKHBjMP/295B7EDoar0Cpyf1YBA+eUrWGxw03PS
cglYv53Larp0ElFZy8LG48ScVUFwsJl7jKTquGpIiu/+K4V/PP3/lnatpkFHHH99
6lEs1PHg2BApfRqSlxJi2eyrKbqig+18HzzpoaSCeFbgWwHHdGLEB8bkg4bHqYgF
x35TbK51SrlExvRAPmcl3oWOL0PFqrvN17X97mn7UzuVoDjSGIHogRVpEhIK9okw
GdcbzuV9Nlgo8k4WvNTlGPZXW4264EwmfxB5bBrfsmfMoFfYL/wL5zS3gCDD3EtX
OJez/CEt38d3P6A8RjdTISBTjFfHrobrrsy2m+uNGea3NnLsStcA/0sOx473Aozi
yQwbcl5/RpVzau63fOto0QLoDsIjah0+wmm1/iVes+m7kL4/OOIoICUCnEQ6YJzA