Bug#1016750: sbcl breaks cl-ironclad autopkgtest on armhf: Heap exhausted, game over.

[Paul Gevers]

Hi Sean,

On 09-08-2022 05:08, Sean Whitton wrote:

It looks like Lisp just ran out of memory.


Yes, but it does so systematically.


Indeed, I can't see this
failure on debci.debian.org at present,


Huh? Did you check 
https://ci.debian.net/packages/c/cl-ironclad/testing/armhf/ or 
https://ci.debian.net/packages/c/cl-ironclad/testing/armel/ You'll see 
there that cl-ironclad was retried with sbcl about 11 + 10 times and 
every time it failed (and never succeeded).



which makes sense if it's a
random OOM problem on weaker architectures like armhf -- so, not the
fault of the new sbcl upload.


This isn't random. And, our armhf box has 255 GB of RAM (and armel VM 
has 26 GB), so running out of memory isn't likely. What can happen is 
that threads use too much resources for the address space, but that's 
something under control of the packages in question if I'm correct (but 
please correct me if I misunderstand). I'm not saying it's (easily) 
fixable, just that it systematically runs out of reachable memory during 
the particular test.



Is it possible to label the tests as
flaky on only a single architecture?


Yes [1], but I'm not seeing flaky behavior.

Paul

[1] add the skippable restriction to the test you want to be able to 
ignore and exit with exit code 77 when the failure happens on the 
architecture you want to ignore. If you want to skip the test on armhf 
and armel altogether, I rather suggest you use an "Architecture: !armel 
!armhf" line in the d/t/control section of the test.


OpenPGP_signature
Description: OpenPGP digital signature

Bug#1016750: sbcl breaks cl-ironclad autopkgtest on armhf: Heap exhausted, game over.

[Sean Whitton]

Hello Paul,

On Sat 06 Aug 2022 at 04:19PM +02, Paul Gevers wrote:

> With a recent upload of sbcl the autopkgtest of cl-ironclad fails in testing
> when that autopkgtest is run with the binary packages of sbcl from
> unstable. It passes when run with only packages from testing.
> 
> ; wrote
>   
> /tmp/autopkgtest-lxc.d2c27h4h/downtmp/autopkgtest_tmp/usr/share/common-lisp/source/ironclad/src/ciphers/tea-tmp93OFNPHA.fasl
> ; compilation finished in 0:00:00.160
> ; compiling file
>   "/usr/share/common-lisp/source/ironclad/src/ciphers/threefish.lisp" (written
>  18 FEB 2022 01:39:10 PM):
> Heap exhausted during garbage collection: 16 bytes available, 48 requested.
> Immobile Object Counts
>  Gen   GF type  fdefn symbol   code  Boxed   ConsRaw   Code  SmMix   Mixed
>  LgRaw LgCode  LgMix Waste%   AllocTrig   Dirty GCs Mem-age
>   1 00  0  0  0   7121939   9668  5273 827
>   0  0 17   19.96186748032499253   18850   1   1.1503
>   2 00  0  0  0  19865   2766  12586 848361681
>   10 34127   11.7   137430448 5368709   23089   0   0.9496
>   3 00  0  0  0  45116   7190   7447604   35521673
>   2394673311.0   270091288 2007806   0   0.4559
>   4 00  0  0  0  0  0  0  0  0   0
>   0  0  00.0   0 200   0   0   0.
>   5 00  0  0  0  0  0  0  0  0   0
>   0  0  00.0   0 200   0   0   0.
>   6 00  0  0  0   1370471   1242   3507314  40
>   2551342811.930584464 200 251   0   0.
> Tot 00  0  0  0  73472  11366  30943   4200   4975   4221
> 5046357566.9   499973680 [93.1% of 536870912 max]
> GC control variables:
>*GC-INHIBIT* = true
>*GC-PENDING* = true
> fatal error encountered in SBCL pid 1357:
> Heap exhausted, game over.

It looks like Lisp just ran out of memory.  Indeed, I can't see this
failure on debci.debian.org at present, which makes sense if it's a
random OOM problem on weaker architectures like armhf -- so, not the
fault of the new sbcl upload.  Is it possible to label the tests as
flaky on only a single architecture?

-- 
Sean Whitton

Bug#1016746: marked as done (sbcl breaks cffi autopkgtest: /usr/bin/ld: cannot find -lzstd: No such file or directory)

[Debian Bug Tracking System]

Your message dated Tue, 09 Aug 2022 03:03:47 +
with message-id 
and subject line Bug#1016746: fixed in cffi 1:0.24.1-3
has caused the Debian Bug report #1016746,
regarding sbcl breaks cffi autopkgtest: /usr/bin/ld: cannot find -lzstd: No 
such file or directory
to be marked as done.

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

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


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

Source: sbcl, cffi
Control: found -1 sbcl/2:2.2.6-2
Control: found -1 cffi/1:0.24.1-2
Severity: serious
Tags: sid bookworm
User: debian...@lists.debian.org
Usertags: breaks needs-update

Dear maintainer(s),

With a recent upload of sbcl the autopkgtest of cffi fails in testing 
when that autopkgtest is run with the binary packages of sbcl from 
unstable. It passes when run with only packages from testing. In tabular 
form:


   passfail
sbcl   from testing2:2.2.6-2
cffi   from testing1:0.24.1-2
all others from testingfrom testing

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

Currently this regression is blocking the migration of sbcl to testing 
[1]. Due to the nature of this issue, I filed this bug report against 
both packages. Can you please investigate the situation and reassign the 
bug to the right package?


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

Paul

[1] https://qa.debian.org/excuses.php?package=sbcl

https://ci.debian.net/data/autopkgtest/testing/amd64/c/cffi/24381426/log.gz

; wrote 
/tmp/autopkgtest-lxc.qpgu5j9b/downtmp/autopkgtest_tmp/usr/share/common-lisp/source/cl-cffi/tests/grovel-tmpFNKDE5XP.fasl

; compilation finished in 0:00:00.015
;;; running tests (uncompiled)
Doing 332 pending tests of 332 tests total.
 LOAD-CORE-FOUNDATION FUNCALL.CHAR FUNCALL.INT.1 FUNCALL.INT.2 FUNCALL.LONG
 FUNCALL.LONG-LONG FUNCALL.UNSIGNED-LONG-LONG FUNCALL.FLOAT FUNCALL.DOUBLE
 FUNCALL.STRING.1 FUNCALL.STRING.2 FUNCALL.STRING.3 
FUNCALL.VARARGS.NOSTDLIB

 FUNCALL.VARARGS.CHAR FUNCALL.VARARGS.INT FUNCALL.VARARGS.LONG
 FUNCALL.VARARGS.DOUBLE FUNCALL.VARARGS.STRING FUNCALL.DOUBLE26 
FUNCALL.FLOAT26

 FUNCALL.F-S-P.1 FUNCALL.NIL-SKIP FUNCALL.POINTER-NOT-NIL
 DEFCFUN.PARSE-NAME-AND-OPTIONS.1 DEFCFUN.PARSE-NAME-AND-OPTIONS.2
 DEFCFUN.PARSE-NAME-AND-OPTIONS.3 DEFCFUN.PARSE-NAME-AND-OPTIONS.4
 DEFCFUN.PARSE-NAME-AND-OPTIONS.5 DEFCFUN.PARSE-NAME-AND-OPTIONS.6
 DEFCFUN.PARSE-NAME-AND-OPTIONS.7 DEFCFUN.PARSE-NAME-AND-OPTIONS.8
 TRANSLATE-UNDERSCORE-SEPARATED-NAME.TO-SYMBOL
 TRANSLATE-UNDERSCORE-SEPARATED-NAME.TO-STRING
 TRANSLATE-CAMELCASE-NAME.TO-SYMBOL TRANSLATE-CAMELCASE-NAME.TO-STRING
 TRANSLATE-CAMELCASE-NAME.TO-STRING-UPPER
 TRANSLATE-CAMELCASE-NAME.TO-SYMBOL-SPECIAL
 TRANSLATE-CAMELCASE-NAME.TO-STRING-SPECIAL 
TRANSLATE-NAME-FROM-FOREIGN.FUNCTION

 TRANSLATE-NAME-FROM-FOREIGN.VAR TRANSLATE-NAME-TO-FOREIGN.FUNCTION
 TRANSLATE-NAME-TO-FOREIGN.VAR DEFCFUN.CHAR DEFCFUN.DOCSTRING DEFCFUN.INT
 DEFCFUN.LONG DEFCFUN.LONG-LONG DEFCFUN.UNSIGNED-LONG-LONG DEFCFUN.FLOAT
 DEFCFUN.DOUBLE DEFCFUN.STRING.1 DEFCFUN.STRING.2 DEFCFUN.STRING.3
 DEFCFUN.NOARGS DEFCFUN.NOOP DEFCFUN.VARARGS.NOSTDLIB 
DEFCFUN.VARARGS.DOCSTRINGS

 DEFCFUN.VARARGS.CHAR DEFCFUN.VARARGS.SHORT DEFCFUN.VARARGS.INT
 DEFCFUN.VARARGS.LONG DEFCFUN.VARARGS.FLOAT DEFCFUN.VARARGS.DOUBLE
 DEFCFUN.VARARGS.STRING DEFCFUN.BFF.1 DEFCFUN.BFF.2 DEFCFUN.UNDEFINED
 DEFCFUN.DOUBLE26 DEFCFUN.FLOAT26 CALLBACKS.CHAR CALLBACKS.UNSIGNED-CHAR
 CALLBACKS.SHORT CALLBACKS.UNSIGNED-SHORT CALLBACKS.INT 
CALLBACKS.UNSIGNED-INT

 CALLBACKS.LONG CALLBACKS.UNSIGNED-LONG CALLBACKS.LONG-LONG
 CALLBACKS.UNSIGNED-LONG-LONG CALLBACKS.FLOAT CALLBACKS.DOUBLE 
CALLBACKS.POINTER

 CALLBACKS.STRING CALLBACKS.STRING-NOT-DOCSTRING CALLBACKS.NIL-FOR-NULL
 CALLBACKS.QSORT CALLBACKS.VOID CALLBACKS.FUNCALL.1 CALLBACKS.FUNCALL.2
 CALLBACKS.BFF.1 CALLBACKS.BFF.2 CALLBACKS.NON-EXISTANT CALLBACKS.DOUBLE26
 CALLBACKS.DOUBLE26.FUNCALL CALLBACKS.FLOAT26 CALLBACKS.FLOAT26.FUNCALL
 CALLBACKS.UNINTERNED FOREIGN-GLOBALS.REF.CHAR 
FOREIGN-GLOBALS.REF.UNSIGNED-CHAR

 FOREIGN-GLOBALS.REF.SHORT FOREIGN-GLOBALS.REF.UNSIGNED-SHORT
 FOREIGN-GLOBALS.REF.INT FOREIGN-GLOBALS.REF.UNSIGNED-INT
 FOREIGN-GLOBALS.REF.LONG FOREIGN-GLOBALS.REF.UNSIGNED-LONG
 FOREIGN-GLOBALS.REF.FLOAT FOREIGN-GLOBALS.REF.DOUBLE
 FOREIGN-GLOBALS.REF.POINTER FOREIGN-GLOBALS.REF.STRING
 FOREIGN-GLOBALS.REF.LONG-LONG FOREIGN-GLOBALS.REF.UNSIGNED-LONG-LONG
 FOREIGN-GLOBALS.SET.INT 

Processed: reassign 1016746 to src:cffi

[Debian Bug Tracking System]

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

> reassign 1016746 src:cffi
Bug #1016746 [src:sbcl, src:cffi] sbcl breaks cffi autopkgtest: /usr/bin/ld: 
cannot find -lzstd: No such file or directory
Bug reassigned from package 'src:sbcl, src:cffi' to 'src:cffi'.
No longer marked as found in versions cffi/1:0.24.1-2 and sbcl/2:2.2.6-2.
Ignoring request to alter fixed versions of bug #1016746 to the same values 
previously set
> thanks
Stopping processing here.

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

Bug#1016884: heimdal: FTBFS with glibc >= 2.34

[Samuel Thibault]

Source: heimdal
Version: 1.6~rc2+dfsg-9+deb8u1
Severity: serious
Justification: FTBFS

Hello,

Now that glibc provides a closefrom function, heimdal doesn't build its
own rk_closefrom function any more, and thus the
libroken18-heimdal.symbols check complains:

- rk_closefrom@HEIMDAL_ROKEN_1.0 1.4.0+git20110226
+#MISSING: 7.7.0+dfsg-4+b1# rk_closefrom@HEIMDAL_ROKEN_1.0 1.4.0+git20110226

Samuel

-- System Information:
Debian Release: bookworm/sid
  APT prefers testing
  APT policy: (990, 'testing'), (500, 'unstable-debug'), (500, 
'testing-debug'), (500, 'stable-security'), (500, 'stable-debug'), (500, 
'proposed-updates-debug'), (500, 'proposed-updates'), (500, 
'oldstable-proposed-updates-debug'), (500, 'oldstable-proposed-updates'), (500, 
'oldoldstable'), (500, 'buildd-unstable'), (500, 'unstable'), (500, 'stable'), 
(500, 'oldstable'), (1, 'experimental-debug'), (1, 'buildd-experimental'), (1, 
'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386, arm64

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

-- 
Samuel
---
Pour une évaluation indépendante, transparente et rigoureuse !
Je soutiens la Commission d'Évaluation de l'Inria.

Processed (with 6 errors): Re: xpra: FTBFS with ffmpeg 5.0

[Debian Bug Tracking System]

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

> tags 1004797 patch thanks
Unknown tag/s: thanks.
Recognized are: patch wontfix moreinfo unreproducible help security upstream 
pending confirmed ipv6 lfs d-i l10n newcomer a11y ftbfs fixed-upstream fixed 
fixed-in-experimental sid experimental potato woody sarge sarge-ignore etch 
etch-ignore lenny lenny-ignore squeeze squeeze-ignore wheezy wheezy-ignore 
jessie jessie-ignore stretch stretch-ignore buster buster-ignore bullseye 
bullseye-ignore bookworm bookworm-ignore trixie trixie-ignore.

Bug #1004797 [src:xpra] xpra: FTBFS with ffmpeg 5.0
Added tag(s) patch.
> On Wed, 20 Jul 2022 13:58:14 -0600 Dan Bungert
Unknown command or malformed arguments to command.
>  wrote:
Unknown command or malformed arguments to command.
> > Dear Maintainer,
Unknown command or malformed arguments to command.
> >
Unknown command or malformed arguments to command.
> > I backported the work done by upstream around ffmpeg 5.  Please see 
> > attached.
Unknown command or malformed arguments to command.
Too many unknown commands, stopping here.

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

Bug#1012898: assimp: diff for NMU version 5.2.4~ds0-1.1

[Timo Röhling]

I've prepared an NMU for assimp (versioned as 5.2.4~ds0-1.1) and
uploaded it to DELAYED/2, going with the minimally invasive patch
proposed by Pino Toscano.

Cheers

--
⢀⣴⠾⠻⢶⣦⠀   ╭╮
⣾⠁⢠⠒⠀⣿⡁   │ Timo Röhling   │
⢿⡄⠘⠷⠚⠋⠀   │ 9B03 EBB9 8300 DF97 C2B1  23BF CC8C 6BDD 1403 F4CA │
⠈⠳⣄   ╰╯
diff -Nru assimp-5.2.4~ds0/debian/changelog assimp-5.2.4~ds0/debian/changelog
--- assimp-5.2.4~ds0/debian/changelog	2022-05-14 23:07:16.0 +0200
+++ assimp-5.2.4~ds0/debian/changelog	2022-08-08 23:24:46.0 +0200
@@ -1,3 +1,11 @@
+assimp (5.2.4~ds0-1.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Disable -Werror for the build.
+Thanks to Pino Toscano for the patch (Closes: #1012898)
+
+ -- Timo Röhling   Mon, 08 Aug 2022 23:24:46 +0200
+
 assimp (5.2.4~ds0-1) unstable; urgency=medium
 
   * New upstream version 5.2.4~ds0
diff -Nru assimp-5.2.4~ds0/debian/.gitattributes assimp-5.2.4~ds0/debian/.gitattributes
--- assimp-5.2.4~ds0/debian/.gitattributes	2022-05-14 23:07:16.0 +0200
+++ assimp-5.2.4~ds0/debian/.gitattributes	1970-01-01 01:00:00.0 +0100
@@ -1 +0,0 @@
-changelog merge=dpkg-mergechangelogs
diff -Nru assimp-5.2.4~ds0/debian/rules assimp-5.2.4~ds0/debian/rules
--- assimp-5.2.4~ds0/debian/rules	2022-05-14 23:07:16.0 +0200
+++ assimp-5.2.4~ds0/debian/rules	2022-08-08 23:23:43.0 +0200
@@ -45,6 +45,7 @@
 		-DASSIMP_BUILD_TESTS=OFF \
 		-DASSIMP_BUILD_ZLIB=OFF \
 		-DASSIMP_LIB_INSTALL_DIR=lib/$(DEB_HOST_MULTIARCH) \
+		-DASSIMP_WARNINGS_AS_ERRORS=OFF \
 		-DCMAKE_SHARED_LINKER_FLAGS="-Wl,--version-script=$(CURDIR)/debian/libassimp.ver $(LDFLAGS)" \
 		-DCMAKE_EXE_LINKER_FLAGS="$(LDFLAGS)" \
 		-DCMAKE_BUILD_RPATH_USE_ORIGIN=ON \


signature.asc
Description: PGP signature

Bug#1016363: fix for fvwm

[Matthieu Herrb]

XCheckIfEvent() holds the X display lock and the predicate
function it calls is not allowed to call any Xlib function that
would re-enter the lock.
libX11 1.8.1 enables X display locks unconditionnaly (it was only
enabled by XInitThreads() when called explicitely before) and
thus exposes the issue.

So don't process events in the FCheckPeekIfEvent() predicate, but
instead use a separate handler that is called for the returned event
out of the lock.
---
 fvwm/events.c |  9 -
 libs/FEvent.c | 22 ++
 libs/FEvent.h |  8 
 3 files changed, 38 insertions(+), 1 deletion(-)

diff --git a/fvwm/events.c b/fvwm/events.c
index ae179d62..72d85707 100644
--- a/fvwm/events.c
+++ b/fvwm/events.c
@@ -267,6 +267,12 @@ static int _pred_weed_accumulate_expose(
return 1;
 }
 
+static int _pred_weed_is_expose(
+   Display *display, XEvent *event, XPointer arg)
+{
+   return (event->type == Expose);
+}
+
 static int _pred_weed_handle_expose(
Display *display, XEvent *event, XPointer arg)
 {
@@ -4546,7 +4552,8 @@ void handle_all_expose(void)
 
saved_event = fev_save_event();
FPending(dpy);
-   FWeedIfEvents(dpy, _pred_weed_handle_expose, NULL);
+   FWeedAndHandleIfEvents(dpy, _pred_weed_is_expose,
+  _pred_weed_handle_expose, NULL);
fev_restore_event(saved_event);
 
return;
diff --git a/libs/FEvent.c b/libs/FEvent.c
index f3bf54d3..7e062118 100644
--- a/libs/FEvent.c
+++ b/libs/FEvent.c
@@ -534,6 +534,28 @@ int FWeedIfEvents(
return weed_args.count;
 }
 
+int FWeedAndHandleIfEvents(
+   Display *display,
+   int (*weed_predicate) (Display *display, XEvent *event, XPointer arg),
+   int (*handler) (Display *display, XEvent *event, XPointer arg),
+   XPointer arg)
+{
+   _fev_weed_args weed_args;
+   XEvent e;
+
+   assert(fev_is_invalid_event_type_set);
+   memset(_args, 0, sizeof(weed_args));
+   weed_args.weed_predicate = weed_predicate;
+   weed_args.arg = arg;
+   if (FCheckPeekIfEvent(display, , _fev_pred_weed_if,
+ (XPointer)_args)) {
+   handler(display, , arg);
+   }
+   _fev_pred_weed_if_finish(_args);
+
+   return weed_args.count;
+}
+
 int FWeedIfWindowEvents(
Display *display, Window window,
int (*weed_predicate) (
diff --git a/libs/FEvent.h b/libs/FEvent.h
index ecfb164c..f17ac5e9 100644
--- a/libs/FEvent.h
+++ b/libs/FEvent.h
@@ -114,6 +114,14 @@ int FWeedIfEvents(
Display *display, XEvent *current_event, XPointer arg),
XPointer arg);
 
+/* Same as FWeedIfEvents but with a second callback out of XLockDisplay()
+ * to handle events in a lock-safe manner */
+int FWeedAndHandleIfEvents(
+   Display *display,
+   int (*weed_predicate) (Display *display, XEvent *event, XPointer arg),
+   int (*handler) (Display *display, XEvent *event, XPointer arg),
+   XPointer arg);
+
 /* Same as FWeedIfEvents but weeds only events for the given window.  The
  * weed_predicate is only called for events with a matching window.  */
 int FWeedIfWindowEvents(
-- 
2.37.1

This is: https://github.com/fvwmorg/fvwm3/pull/683
-- 
Matthieu Herrb

Bug#1013028: marked as done (rdkit: ftbfs with GCC-12)

[Debian Bug Tracking System]

Your message dated Mon, 08 Aug 2022 21:07:57 +
with message-id 
and subject line Bug#1013028: fixed in rdkit 202203.2-2
has caused the Debian Bug report #1013028,
regarding rdkit: ftbfs with GCC-12
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.)


-- 
1013028: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1013028
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:rdkit
Version: 202203.2-1
Severity: normal
Tags: sid bookworm
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-12

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

The full build log can be found at:
http://qa-logs.debian.net/2022/06/09/gcc12/rdkit_202203.2-1_unstable_gcc12.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.

[...]
cd /<>/obj-x86_64-linux-gnu/Code/GraphMol/FileParsers && 
/usr/bin/cmake -E cmake_link_script 
CMakeFiles/testMultithreadedMolSupplier.dir/link.txt --verbose=1
/usr/bin/c++ -g -O2 -ffile-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
-D_FORTIFY_SOURCE=2 -Wdate-time -D_FORTIFY_SOURCE=2 -Wno-deprecated 
-Wno-unused-function -fno-strict-aliasing -Wall -Wextra -fPIC -Wl,-z,relro 
-Wl,-z,now 
CMakeFiles/testMultithreadedMolSupplier.dir/testMultithreadedMolSupplier.cpp.o 
-o testMultithreadedMolSupplier  
../../../lib/libRDKitFileParsers.so.1.2022.03.2 
../../../lib/libRDKitFingerprints.so.1.2022.03.2 
../../../lib/libRDKitRDStreams.so.1.2022.03.2 
../../../lib/libRDKitDepictor.so.1.2022.03.2 
../../../lib/libRDKitMolAlign.so.1.2022.03.2 
../../../lib/libRDKitAlignment.so.1.2022.03.2 
/usr/lib/x86_64-linux-gnu/libcoordgen.so 
../../../lib/libRDKitMolTransforms.so.1.2022.03.2 
../../../lib/libRDKitEigenSolvers.so.1.2022.03.2 
/usr/lib/x86_64-linux-gnu/libmaeparser.so 
/usr/lib/x86_64-linux-gnu/libboost_system.so 
/usr/lib/x86_64-linux-gnu/libboost_iostreams.so 
/usr/lib/x86_64-linux-gnu/libboost_regex.so /usr/li
 b/x86_64-linux-gnu/libboost_system.so 
/usr/lib/x86_64-linux-gnu/libboost_iostreams.so 
/usr/lib/x86_64-linux-gnu/libboost_regex.so /usr/lib/x86_64-linux-gnu/libz.so 
../../../lib/libRDKitSmilesParse.so.1.2022.03.2 
../../../lib/libRDKitSubgraphs.so.1.2022.03.2 
../../../lib/libRDKitSubstructMatch.so.1.2022.03.2 
../../../lib/libRDKitGenericGroups.so.1.2022.03.2 
../../../lib/libRDKitGraphMol.so.1.2022.03.2 
../../../lib/libRDKitRDGeometryLib.so.1.2022.03.2 
../../../lib/libRDKitDataStructs.so.1.2022.03.2 
../../../lib/libRDKitRDGeneral.so.1.2022.03.2 -ldl -lpthread 
/usr/lib/x86_64-linux-gnu/libboost_iostreams.so 
/usr/lib/x86_64-linux-gnu/libboost_regex.so 
/usr/bin/ld: make[4]: Leaving directory '/<>/obj-x86_64-linux-gnu'
[ 54%] Built target graphmolTestsCatch
make  -f Code/GraphMol/FileParsers/CMakeFiles/testMol2ToMol.dir/build.make 
Code/GraphMol/FileParsers/CMakeFiles/testMol2ToMol.dir/depend
make[4]: Entering directory '/<>/obj-x86_64-linux-gnu'
cd /<>/obj-x86_64-linux-gnu && /usr/bin/cmake -E cmake_depends 
"Unix Makefiles" /<> /<>/Code/GraphMol/FileParsers 
/<>/obj-x86_64-linux-gnu 
/<>/obj-x86_64-linux-gnu/Code/GraphMol/FileParsers 
/<>/obj-x86_64-linux-gnu/Code/GraphMol/FileParsers/CMakeFiles/testMol2ToMol.dir/DependInfo.cmake
 --color=
make[4]: Leaving directory '/<>/obj-x86_64-linux-gnu'
make  -f Code/GraphMol/FileParsers/CMakeFiles/testMol2ToMol.dir/build.make 
Code/GraphMol/FileParsers/CMakeFiles/testMol2ToMol.dir/build
make[4]: Entering directory 

Bug#1016842: marked as done (vim-youcompleteme: vim-tests-gopls fails with gopls/1:0.1.12+ds-1)

[Debian Bug Tracking System]

Your message dated Mon, 08 Aug 2022 21:08:06 +
with message-id 
and subject line Bug#1016842: fixed in vim-youcompleteme 
0+20220402+git3ededae+ds-4
has caused the Debian Bug report #1016842,
regarding vim-youcompleteme: vim-tests-gopls fails with gopls/1:0.1.12+ds-1
to be marked as done.

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

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


-- 
1016842: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1016842
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: vim-youcompleteme
Version: 0+20220402+git3ededae+ds-3
Severity: serious
X-Debbugs-Cc: z...@debian.org

The test is wrong to assume the fixtures provided by gopls are always same.
The failed test blocks gopls migrating to testing.
--- End Message ---
--- Begin Message ---
Source: vim-youcompleteme
Source-Version: 0+20220402+git3ededae+ds-4
Done: David Kalnischkies 

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

Debian distribution maintenance software
pp.
David Kalnischkies  (supplier of updated vim-youcompleteme 
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: Mon, 08 Aug 2022 21:55:47 +0200
Source: vim-youcompleteme
Architecture: source
Version: 0+20220402+git3ededae+ds-4
Distribution: unstable
Urgency: medium
Maintainer: David Kalnischkies 
Changed-By: David Kalnischkies 
Closes: 1016842
Changes:
 vim-youcompleteme (0+20220402+git3ededae+ds-4) unstable; urgency=medium
 .
   * Import upstream 0+20220706+gitd35df61 as patch series
 - Support ycmds experimental semantic highlighting
   * Do not require semantic highlighting support in ycmd
   * Run gopls test with gccgo and golang-go
   * Use first option in gopls fixit test dialog (Closes: #1016842)
   * Avoid testing with unavailable nodejs on armel
Checksums-Sha1:
 79c3a8119b2dc22e06b5351ab4f6cf3f81a40d3e 2366 
vim-youcompleteme_0+20220402+git3ededae+ds-4.dsc
 0c0cc6e6a22f3d77acd2f3a127bc7bcd3489da4a 28344 
vim-youcompleteme_0+20220402+git3ededae+ds-4.debian.tar.xz
 e2364d7a1dc315f059c840e857b30f8e23cc9059 7435 
vim-youcompleteme_0+20220402+git3ededae+ds-4_amd64.buildinfo
Checksums-Sha256:
 94ad820d859e2af1a93a7ad91a99116b213c6b1375d7edbadd219a10305d44f6 2366 
vim-youcompleteme_0+20220402+git3ededae+ds-4.dsc
 8470eb247976b05ed608b73bd17febfa6f6887dc1e6e090bc6d952fff70a303e 28344 
vim-youcompleteme_0+20220402+git3ededae+ds-4.debian.tar.xz
 7fa34279c0b87fa0d20dc429d2dbf9d7677eebf30aed52d97892980742514f7c 7435 
vim-youcompleteme_0+20220402+git3ededae+ds-4_amd64.buildinfo
Files:
 03b46265b4ea0ed85d16d2e9a47b971b 2366 editors optional 
vim-youcompleteme_0+20220402+git3ededae+ds-4.dsc
 08a5a1bab405532c344e792981e358ca 28344 editors optional 
vim-youcompleteme_0+20220402+git3ededae+ds-4.debian.tar.xz
 81952ab1115ea1ae8f07771442565d91 7435 editors optional 
vim-youcompleteme_0+20220402+git3ededae+ds-4_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQJHBAEBCgAxFiEE5sn+Q4uCja/tn0GrMRvlz3HQeIMFAmLxcswTHGRvbmt1bHRA
ZGViaWFuLm9yZwAKCRAxG+XPcdB4g2iZEACRif/DcET9zUGGTzTnWWMXt+1/JfDe
+8e3XROQ2U0TAtnH3pB/wdTet3nhXekhX3bqQor0dVLphJoeOp5eQjz/4HtNcb7u
I3b9UChb/600Dv+9318ybAbYjvi/uDeYmBqd8A8azSUMxTxrUgEiSMkgex15l0+y
ubivylGj4G9GiU410D2Iwru8EgxmaoOS63hZOaeNkAInMlkFe32T3laiSALYDEyu
TC4m/yIwN9OCGrgDcpwLaWAiYOwuFkseIDbiZPlX0NZg33w2/a4iEkpL5SPoSWEw
xmtiE9rDPLgGZlLbuKgbYhml1kOg111hk/92KGL4ljcHFVQGAmAfpLw700jH/Rbs
nfSlCRg240C5+ZXMVtXlpxNq5Mcb5ra9+3xO+L5UkKBETertLTsixiF7Bg/JqDbw
7TjSGEatzm+IFKMQINXRWDleDGNU1w5yCuwnS8QHUnPCBmIsdiSx5GzGawZrtSKE
7qVlraGFw0GeJLWqrbQRcoGKgO5f5VxSW/WPIuvzjMgOP7AjhmFHVktB3m8zAEgW
dmDjqDFIM09xo6KueWvOSxQ/JFTNacDh7h0vRu7qCMKXZHpDkssK+cyA0MIaARXB
RN31U5Fq/aWYsT7zUmL2H9jd+1QCkNEgPjRYzQLTtlh0y+kiWxpPWEdWCO3J258O
9cy154qzwLHjrA==
=eEuQ
-END PGP SIGNATURE End Message ---

Processed: severity of 1015049 is important

[Debian Bug Tracking System]

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

> severity 1015049 important
Bug #1015049 [src:thrift] thrift: FTBFS: dh_auto_test: error: make -j1 check 
"TESTSUITEFLAGS=-j1 --verbose" VERBOSE=1 returned exit code 2
Severity set to 'important' from 'serious'
> thanks
Stopping processing here.

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

Bug#1016283: onetbb: FTBFS: _segment_table.h:63:63: error: member ‘tbb::detail::d1::segment_table, 128>, tbb::detail::d1::cache_aligned_alloc

[Richard B. Kreckel]

I am unable to reproduce the above compile-time error.

Bug#1016812: marked as done (nodex-expat: autopkgtest failure with nodejs 18.6)

[Debian Bug Tracking System]

Your message dated Mon, 08 Aug 2022 20:40:13 +
with message-id 
and subject line Bug#1016812: fixed in node-expat 2.4.0+ds-2
has caused the Debian Bug report #1016812,
regarding nodex-expat: autopkgtest failure with nodejs 18.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.)


-- 
1016812: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1016812
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: node-expat
Version: 2.4.0+ds-1
Severity: serious
X-Debbugs-Cc: sramac...@debian.org

https://ci.debian.net/data/autopkgtest/testing/amd64/n/node-expat/24419068/log.gz


autopkgtest [20:11:40]: test command2: vows --spec ./test/**/*.js
autopkgtest [20:11:40]: test command2: [---
/usr/share/nodejs/bindings/bindings.js:121
throw e;
^

Error: The module 
'/usr/lib/x86_64-linux-gnu/nodejs/node-expat/build/Release/node_expat.node'
was compiled against a different Node.js version using
NODE_MODULE_VERSION 93. This version of Node.js requires
NODE_MODULE_VERSION 108. Please try re-compiling or re-installing
the module (for instance, using `npm rebuild` or `npm install`).
at Module._extensions..node (node:internal/modules/cjs/loader:1204:18)
at Module.load (node:internal/modules/cjs/loader:998:32)
at Module._load (node:internal/modules/cjs/loader:839:12)
at Module.require (node:internal/modules/cjs/loader:1022:19)
at require (node:internal/modules/cjs/helpers:102:18)
at bindings (/usr/share/nodejs/bindings/bindings.js:112:48)
at Object. 
(/usr/lib/x86_64-linux-gnu/nodejs/node-expat/lib/node-expat.js:4:34)
at Module._compile (node:internal/modules/cjs/loader:1120:14)
at Module._extensions..js (node:internal/modules/cjs/loader:1174:10)
at Module.load (node:internal/modules/cjs/loader:998:32) {
  code: 'ERR_DLOPEN_FAILED'
}

Node.js v18.6.0
bash: line 1:  1832 Aborted bash -ec 'vows --spec 
./test/**/*.js' 2> >(tee -a 
/tmp/autopkgtest-lxc.ny14wys2/downtmp/command2-stderr >&2) > >(tee -a 
/tmp/autopkgtest-lxc.ny14wys2/downtmp/command2-stdout)
autopkgtest [20:11:40]: test command2: ---]
autopkgtest [20:11:40]: test command2:  - - - - - - - - - - results - - - - - - 
- - - -
command2 FAIL non-zero exit status 134
autopkgtest [20:11:40]: test command2:  - - - - - - - - - - stderr - - - - - - 
- - - -
/usr/share/nodejs/bindings/bindings.js:121
throw e;
^

Error: The module 
'/usr/lib/x86_64-linux-gnu/nodejs/node-expat/build/Release/node_expat.node'
was compiled against a different Node.js version using
NODE_MODULE_VERSION 93. This version of Node.js requires
NODE_MODULE_VERSION 108. Please try re-compiling or re-installing
the module (for instance, using `npm rebuild` or `npm install`).
at Module._extensions..node (node:internal/modules/cjs/loader:1204:18)
at Module.load (node:internal/modules/cjs/loader:998:32)
at Module._load (node:internal/modules/cjs/loader:839:12)
at Module.require (node:internal/modules/cjs/loader:1022:19)
at require (node:internal/modules/cjs/helpers:102:18)
at bindings (/usr/share/nodejs/bindings/bindings.js:112:48)
at Object. 
(/usr/lib/x86_64-linux-gnu/nodejs/node-expat/lib/node-expat.js:4:34)
at Module._compile (node:internal/modules/cjs/loader:1120:14)
at Module._extensions..js (node:internal/modules/cjs/loader:1174:10)
at Module.load (node:internal/modules/cjs/loader:998:32) {
  code: 'ERR_DLOPEN_FAILED'
}

Node.js v18.6.0
autopkgtest [20:11:41]:  summary
command1 FAIL non-zero exit status 134
command2 FAIL non-zero exit status 134


Cheers
-- 
Sebastian Ramacher
--- End Message ---
--- Begin Message ---
Source: node-expat
Source-Version: 2.4.0+ds-2
Done: Yadd 

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

Debian distribution maintenance software
pp.
Yadd  (supplier of updated node-expat 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: Mon, 08 Aug 2022 21:57:34 +0200

Bug#1016511: marked as done (python3-pydevd: missing Breaks+Replaces: python3-omegaconf (<< ???))

[Debian Bug Tracking System]

Your message dated Mon, 08 Aug 2022 19:50:46 +
with message-id 
and subject line Bug#1016511: fixed in pydevd 2.8.0+git20220714.32dee0b+dfsg-6
has caused the Debian Bug report #1016511,
regarding python3-pydevd: missing Breaks+Replaces: python3-omegaconf (<< ???)
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.)


-- 
1016511: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1016511
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: python3-pydevd
Version: 2.8.0+git20220714.32dee0b+dfsg-2
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Control: block -1 with 1016510

Hi,

during a test with piuparts I noticed your package failed to install
because it tries to overwrite other packages files without declaring a
Breaks+Replaces relation.

See policy 7.6 at
https://www.debian.org/doc/debian-policy/ch-relationships.html#overwriting-files-and-replacing-packages-replaces

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

  Selecting previously unselected package python3-pydevd.
  Preparing to unpack 
.../python3-pydevd_2.8.0+git20220714.32dee0b+dfsg-2_amd64.deb ...
  Unpacking python3-pydevd (2.8.0+git20220714.32dee0b+dfsg-2) ...
  dpkg: error processing archive 
/var/cache/apt/archives/python3-pydevd_2.8.0+git20220714.32dee0b+dfsg-2_amd64.deb
 (--unpack):
   trying to overwrite 
'/usr/lib/python3/dist-packages/pydevd_plugins/__init__.py', which is also in 
package python3-omegaconf 2.1.0~rc1-3
  Errors were encountered while processing:
   
/var/cache/apt/archives/python3-pydevd_2.8.0+git20220714.32dee0b+dfsg-2_amd64.deb

python3-omegaconf still needs to drop the conflicting files (#1016510),
so my guess would be that you need to add

  Breaks+Replaces: python3-omegaconf (<< 2.1.0~rc1-4~)


cheers,

Andreas


python3-omegaconf=2.1.0~rc1-3_python3-pydevd=2.8.0+git20220714.32dee0b+dfsg-2.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: pydevd
Source-Version: 2.8.0+git20220714.32dee0b+dfsg-6
Done: Julian Gilbey 

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

Debian distribution maintenance software
pp.
Julian Gilbey  (supplier of updated pydevd 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: Mon, 08 Aug 2022 20:07:18 +0100
Source: pydevd
Architecture: source
Version: 2.8.0+git20220714.32dee0b+dfsg-6
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Team 
Changed-By: Julian Gilbey 
Closes: 1016511
Changes:
 pydevd (2.8.0+git20220714.32dee0b+dfsg-6) unstable; urgency=medium
 .
   * Add Breaks+Replaces python3-omegaconf (Closes: #1016511)
Checksums-Sha1:
 2d2906ba0b2e2e189a76e1d5e954a3cd683cc3a8 3229 
pydevd_2.8.0+git20220714.32dee0b+dfsg-6.dsc
 243e93ed1992feef2733f674a43fc78bfd2f4cca 18676 
pydevd_2.8.0+git20220714.32dee0b+dfsg-6.debian.tar.xz
 6db333b57c72f0db9ef1cb5ce00f399e2693d26d 16160 
pydevd_2.8.0+git20220714.32dee0b+dfsg-6_amd64.buildinfo
Checksums-Sha256:
 8e17e43eef80115e2684e24c1c138d507430884c2ec718e14287faac21b8f4d1 3229 
pydevd_2.8.0+git20220714.32dee0b+dfsg-6.dsc
 298bea29cefbd5e02b15d77f50d4442890b65ac5f71b3356c4f15501e24a796a 18676 
pydevd_2.8.0+git20220714.32dee0b+dfsg-6.debian.tar.xz
 a9908b186010cf8b930217ca9cff61eabdefa77d368145a27af44c80ad32496a 16160 
pydevd_2.8.0+git20220714.32dee0b+dfsg-6_amd64.buildinfo
Files:
 dd42c6a9613d0021bec8d992ab17ca4e 3229 python optional 
pydevd_2.8.0+git20220714.32dee0b+dfsg-6.dsc
 f27616c1af91a76bd5a2352d2954069e 18676 python optional 
pydevd_2.8.0+git20220714.32dee0b+dfsg-6.debian.tar.xz
 f3493ff32d1af6160451636be80e1599 16160 python optional 
pydevd_2.8.0+git20220714.32dee0b+dfsg-6_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQJDBAEBCAAtFiEEfhrD+iemSShMMj72aVxCkxbAe/4FAmLxYhgPHGpkZ0BkZWJp
YW4ub3JnAAoJEGlcQpMWwHv++DcQAK0BC2Cad4xQGWXv9Ku+eBjy2Pu4jCFmznLb
KUQsOq1ujQlnMIphnM4xEANMSaRsntPBJOpMU0BevuxfW4Md1+pXMGXJp0tsx+8x
6fjBXPpk2zCbXavjXFhAo1vZ1Ut0ypfxmdbtAzyceg3DNIpe/vExISp+29WJi8Ky
QyuheIoxAOesYnt/JnpAsWa95ytX9as+MI5rsE4nm5piYH2VQb79yzpplLGlOC/n

Processed: glibc transition affects castle-game-engine

[Debian Bug Tracking System]

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

> affects 1016556 src:castle-game-engine
Bug #1016556 [src:fpc] fpc: glibc 2.34 breaks fpc autopkgtest on arm64: 
undefined reference to `__libc_csu_init'
Added indication that 1016556 affects src:castle-game-engine
> severity 1016556 serious
Bug #1016556 [src:fpc] fpc: glibc 2.34 breaks fpc autopkgtest on arm64: 
undefined reference to `__libc_csu_init'
Severity set to 'serious' from 'important'
> thanks
Stopping processing here.

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

Processed: Bug#1016511 marked as pending in pydevd

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1016511 [python3-pydevd] python3-pydevd: missing Breaks+Replaces: 
python3-omegaconf (<< ???)
Added tag(s) pending.

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

Bug#1016511: marked as pending in pydevd

[Julian Gilbey]

Control: tag -1 pending

Hello,

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

https://salsa.debian.org/python-team/packages/pydevd/-/commit/8b002a564a405816e342761ef4642dab01d92695


Add Breaks+Replaces python3-omegaconf (Closes: #1016511)


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1016511

Bug#1016511: python3-pydevd: missing Breaks+Replaces: python3-omegaconf (<< ???)

[Julian Gilbey]

On Tue, Aug 02, 2022 at 07:41:51AM +0200, Andreas Beckmann wrote:
> Package: python3-pydevd
> Version: 2.8.0+git20220714.32dee0b+dfsg-2
> Severity: serious
> User: debian...@lists.debian.org
> Usertags: piuparts
> Control: block -1 with 1016510
> 
> Hi,
> 
> during a test with piuparts I noticed your package failed to install
> because it tries to overwrite other packages files without declaring a
> Breaks+Replaces relation.
> [...]

> python3-omegaconf still needs to drop the conflicting files (#1016510),
> so my guess would be that you need to add
> 
>   Breaks+Replaces: python3-omegaconf (<< 2.1.0~rc1-4~)

Thanks Andreas!  I had no idea any other packages were using the
pydevd namespace - I hadn't even thought to check.  Thomas has now
fixed python3-omegaconf (thanks Thomas!), so the new version of pydevd
that I'm just building and uploading should solve this one.

Best wishes,

   Julian

Processed: Re: freecad: FTBFS on armel and armhf: error: ‘GL_PROJECTION’ was not declared in this scope;

[Debian Bug Tracking System]

Processing control commands:

> tags -1 +patch
Bug #1014875 [freecad] freecad: FTBFS on armel and armhf: error: 
‘GL_PROJECTION’ was not declared in this scope;
Added tag(s) patch.

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

Bug#1014875: freecad: FTBFS on armel and armhf: error: ‘GL_PROJECTION’ was not declared in this scope;

[Tobias Frost]

Package: freecad
Version: 0.20+dfsg1-2
Followup-For: Bug #1014875

(Attaching patch)
Description: Fix FTBFS on armhf/armel, undefined GL_PROJECTION
 This define is defined in GL/gl.h, so there  must be some missing include
 somewhere. This patch just adds the include…
Author: t...@debian.org
Bug-Debian: https://bugs.debian.org/1014875
Forwarded: no
Last-Update: 2022-08-08 
---
This patch header follows DEP-3: http://dep.debian.net/deps/dep3/
--- a/src/Gui/Quarter/QuarterWidget.cpp
+++ b/src/Gui/Quarter/QuarterWidget.cpp
@@ -54,6 +54,11 @@
 
 #include 
 
+#include "config.h"
+#ifdef  HAVE_GL_GL_H
+#include 
+#endif
+
 #include 
 #include 
 #include 

Bug#1014875: freecad: FTBFS on armel and armhf: error: ‘GL_PROJECTION’ was not declared in this scope;

[Tobias Frost]

Package: freecad
Version: 0.20+dfsg1-2
Followup-For: Bug #1014875
Control: tags -1 +patch

Dear Maintainer,

with attached patch makes I could compile FreeCAD on the amdahl armhf porterbox.

-- 
Cheer,
tobi

-- System Information:
Debian Release: bookworm/sid
  APT prefers stable-security
  APT policy: (500, 'stable-security'), (500, 'unstable'), (500, 'testing'), 
(500, 'stable'), (100, 'bullseye-fasttrack'), (100, 
'bullseye-backports-staging')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

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

Versions of packages freecad depends on:
ii  freecad-python3  0.20+dfsg1-2

Versions of packages freecad recommends:
ii  calculix-ccx  2.19-1
ii  graphviz  2.42.2-7

Versions of packages freecad suggests:
ii  povray  1:3.7.0.10-2

-- no debconf information

Bug#1015132: meson: FTBFS: ./b 52a78b9866/../test cases/failing build/2 hidden symbol/bobuser.c:4: undefined reference to `hidden_function'

[Eli Schwartz]

On Sat, 16 Jul 2022 20:55:02 +0200 Lucas Nussbaum  wrote:
> Hi,
> 
> The script I use to extract the failure from the log might have guessed
> badly indeed, however the build still fails, as shown by the full log
> linked in the bug:
> http://qa-logs.debian.net/2022/07/16/meson_0.63.0-1_unstable.log
> SO I wouldn't call that a "spurious failure".
> 
> However looking at the log I don't really understand why the
> override_dh_auto_test target fails. Can you explain? Maybe I can improve
> my script.
> 
> Lucas


The testsuite has two parts. The first part (that actually fails in this
case) is a standard python-unittest run, and presumably you have
heuristics that can catch that.

The second part is a very custom setup, you'll undoubtedly need to
manually code support for it. Since Debian includes the environment
variable $MESON_PRINT_TEST_OUTPUT for extra extra extra debug spew, it
logs full configure/build/test/install output for all tests, not just
the ones that represent test failures... including, as stated above,
passing tests that attempt to assert that certain things aren't expected
to work.

Let's take a look at run_project_tests.py which is driving these very
verbose tests:

class TestStatus(Enum):
OK = normal_green(' [SUCCESS] ')
SKIP = yellow(' [SKIPPED] ')
ERROR = red('  [ERROR]  ')
UNEXSKIP = red('[UNEXSKIP] ')
UNEXRUN = red(' [UNEXRUN] ')
CANCELED = cyan('[CANCELED] ')
RUNNING = blue(' [RUNNING] ')  # Should never be actually printed
LOG = bold('   [LOG]   ')  # Should never be actually printed


Individual test logs are always separated by lines beginning with the
string " [XXX]".

error, unexskip, and unexrun are the only failure states.

unexskip and unexrun can only happen in Meson's internal CI
($MESON_CI_JOBNAME is set and isn't "thirdparty").



So you can just filter for:

- any python-unittest matching logs (e.g. in between "===" and
  "\nRan  tests in s")

- anything in between " [ERROR]" and " []"



-- 
Eli Schwartz

Bug#1013069: marked as done (wreport: ftbfs with GCC-12)

[Debian Bug Tracking System]

Your message dated Mon, 08 Aug 2022 18:14:47 +
with message-id 
and subject line Bug#1013069: fixed in wreport 3.34-1
has caused the Debian Bug report #1013069,
regarding wreport: ftbfs with GCC-12
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.)


-- 
1013069: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1013069
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:wreport
Version: 3.23-2
Severity: normal
Tags: sid bookworm
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-12

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

The full build log can be found at:
http://qa-logs.debian.net/2022/06/09/gcc12/wreport_3.23-2_unstable_gcc12.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.

[...]
  191 | ss << "value '" << actual << "' is different than the expected '" 
<< expected << "'";
  | ^
/usr/include/c++/12/bits/ostream.tcc:302:5: note: candidate: ‘template std::basic_ostream<_CharT, _Traits>& 
std::operator<<(basic_ostream<_CharT, _Traits>&, const char*)’
  302 | operator<<(basic_ostream<_CharT, _Traits>& __out, const char* __s)
  | ^~~~
/usr/include/c++/12/bits/ostream.tcc:302:5: note:   template argument 
deduction/substitution failed:
../wreport/utils/tests.h:191:21: note:   cannot convert ‘actual’ (type ‘const 
wreport::Vartype’) to type ‘const char*’
  191 | ss << "value '" << actual << "' is different than the expected '" 
<< expected << "'";
  | ^
/usr/include/c++/12/ostream:615:5: note: candidate: ‘template 
std::basic_ostream& std::operator<<(basic_ostream&, const char*)’
  615 | operator<<(basic_ostream& __out, const char* __s)
  | ^~~~
/usr/include/c++/12/ostream:615:5: note:   template argument 
deduction/substitution failed:
../wreport/utils/tests.h:191:21: note:   cannot convert ‘actual’ (type ‘const 
wreport::Vartype’) to type ‘const char*’
  191 | ss << "value '" << actual << "' is different than the expected '" 
<< expected << "'";
  | ^
/usr/include/c++/12/ostream:628:5: note: candidate: ‘template 
std::basic_ostream& std::operator<<(basic_ostream&, const signed char*)’
  628 | operator<<(basic_ostream& __out, const signed char* 
__s)
  | ^~~~
/usr/include/c++/12/ostream:628:5: note:   template argument 
deduction/substitution failed:
../wreport/utils/tests.h:191:21: note:   cannot convert ‘actual’ (type ‘const 
wreport::Vartype’) to type ‘const signed char*’
  191 | ss << "value '" << actual << "' is different than the expected '" 
<< expected << "'";
  | ^
/usr/include/c++/12/ostream:633:5: note: candidate: ‘template 
std::basic_ostream& std::operator<<(basic_ostream&, const unsigned char*)’
  633 | operator<<(basic_ostream& __out, const unsigned 
char* __s)
  | ^~~~
/usr/include/c++/12/ostream:633:5: note:   template argument 
deduction/substitution failed:
../wreport/utils/tests.h:191:21: note:   cannot convert ‘actual’ (type ‘const 
wreport::Vartype’) to type ‘const unsigned char*’
  191 | ss << "value '" << actual << "' is different than the expected '" 
<< expected << "'";
  | ^
/usr/include/c++/12/ostream:754:5: note: candidate: ‘template _Ostream&& std::operator<<(_Ostream&&, const _Tp&)’
  754 | operator<<(_Ostream&& __os, const _Tp& 

Bug#1016878: mozjs91: no longer needed

[Simon McVittie]

Control: severity -1 important

On Mon, 08 Aug 2022 at 13:55:35 -0400, Jeremy Bicha wrote:
> gjs 1.73.2 has switched from mozjs91 to mozjs102. Once we update our
> gjs packaging, there won't be anything in Debian using mozjs91.

This seems a little premature. Let's not make mozjs91 (and gjs, and GNOME)
RC-buggy until we're actually using mozjs102, which as far as I can see
isn't in NEW yet.

smcv

Processed: Re: Bug#1016878: mozjs91: no longer needed

[Debian Bug Tracking System]

Processing control commands:

> severity -1 important
Bug #1016878 [src:mozjs91] mozjs91: no longer needed
Severity set to 'important' from 'serious'

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

Bug#1016878: mozjs91: no longer needed

[Jeremy Bicha]

Source: mozjs91
Severity: serious
Version: 91.10.0-1

gjs 1.73.2 has switched from mozjs91 to mozjs102. Once we update our
gjs packaging, there won't be anything in Debian using mozjs91.

However, maybe Cinnamon will switch from mozjs78?

Thank you,
Jeremy Bicha

Bug#1016838: marked as done (ycmd.tests.go.subcommands_test.SubcommandsTest fails with gopls/1:0.1.12+ds-1)

[Debian Bug Tracking System]

Your message dated Mon, 08 Aug 2022 17:50:39 +
with message-id 
and subject line Bug#1016838: fixed in ycmd 0+20220401+gitdbe806f+ds-3
has caused the Debian Bug report #1016838,
regarding ycmd.tests.go.subcommands_test.SubcommandsTest fails with 
gopls/1:0.1.12+ds-1
to be marked as done.

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

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


-- 
1016838: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1016838
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ycmd
Version: 0+20220401+gitdbe806f+ds-2
Severity: serious
X-Debbugs-Cc: z...@debian.org


Go 1.19 changes the code format, so the test fails now.
Please exclude this test, as it prevents gopls migrating to testing.

Log:

==
FAIL: test_Subcommands_Format_WholeFile 
(ycmd.tests.go.subcommands_test.SubcommandsTest)
--
Traceback (most recent call last):
  File "/tmp/autopkgtest.nAXNu0/build.RqO/src/ycmd/tests/go/__init__.py", line 
59, in Wrapper
return test( test_case_instance, shared_app, *args, **kwargs )
  File 
"/tmp/autopkgtest.nAXNu0/build.RqO/src/ycmd/tests/go/subcommands_test.py", line 
213, in test_Subcommands_Format_WholeFile
RunTest( app, {
  File 
"/tmp/autopkgtest.nAXNu0/build.RqO/src/ycmd/tests/go/subcommands_test.py", line 
86, in RunTest
assert_that( response.json, test[ 'expect' ][ 'data' ] )
AssertionError: 
Expected: a dictionary containing {'fixits': a sequence containing [a 
dictionary containing {'chunks': a sequence containing [a dictionary containing 
{'range': a dictionary containing {'end': a dictionary containing 
{'column_num': <5>, 'filepath': 
'/tmp/autopkgtest.nAXNu0/build.RqO/src/ycmd/tests/go/go_module/goto.go', 
'line_num': <8>}, 'start': a dictionary containing {'column_num': <1>, 
'filepath': 
'/tmp/autopkgtest.nAXNu0/build.RqO/src/ycmd/tests/go/go_module/goto.go', 
'line_num': <8>}}, 'replacement_text': ''}, a dictionary containing {'range': a 
dictionary containing {'end': a dictionary containing {'column_num': <5>, 
'filepath': 
'/tmp/autopkgtest.nAXNu0/build.RqO/src/ycmd/tests/go/go_module/goto.go', 
'line_num': <8>}, 'start': a dictionary containing {'column_num': <5>, 
'filepath': 
'/tmp/autopkgtest.nAXNu0/build.RqO/src/ycmd/tests/go/go_module/goto.go', 
'line_num': <8>}}, 'replacement_text': '\t'}, a dictionary containing {'range': 
a dictionary containing {'end': a dictionary containing {'column_num': <5>, 
'filepath': 
'/tmp/autopkgtest.nAXNu0/build.RqO/src/ycmd/tests/go/go_module/goto.go', 
'line_num': <12>}, 'start': a dictionary containing {'column_num': <1>, 
'filepath': 
'/tmp/autopkgtest.nAXNu0/build.RqO/src/ycmd/tests/go/go_module/goto.go', 
'line_num': <12>}}, 'replacement_text': ''}, a dictionary containing {'range': 
a dictionary containing {'end': a dictionary containing {'column_num': <5>, 
'filepath': 
'/tmp/autopkgtest.nAXNu0/build.RqO/src/ycmd/tests/go/go_module/goto.go', 
'line_num': <12>}, 'start': a dictionary containing {'column_num': <5>, 
'filepath': 
'/tmp/autopkgtest.nAXNu0/build.RqO/src/ycmd/tests/go/go_module/goto.go', 
'line_num': <12>}}, 'replacement_text': '\t'}]}]}
 but: value for 'fixits' item 0: value for 'chunks' item 0: value for 
'replacement_text' was '\t'
--- End Message ---
--- Begin Message ---
Source: ycmd
Source-Version: 0+20220401+gitdbe806f+ds-3
Done: David Kalnischkies 

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

Debian distribution maintenance software
pp.
David Kalnischkies  (supplier of updated ycmd 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: Mon, 08 Aug 2022 19:17:59 +0200
Source: ycmd
Architecture: source
Version: 0+20220401+gitdbe806f+ds-3
Distribution: unstable
Urgency: medium
Maintainer: David Kalnischkies 
Changed-By: David Kalnischkies 
Closes: 1016838
Changes:
 ycmd (0+20220401+gitdbe806f+ds-3) unstable; urgency=medium
 .
   * Import upstream 0+20220609+git20bfbbf as patch series
 - Support for semantic 

Bug#1016868: marked as done (libc6-udeb: dangling ld-linux symlink)

[Debian Bug Tracking System]

Your message dated Mon, 08 Aug 2022 17:50:16 +
with message-id 
and subject line Bug#1016868: fixed in glibc 2.34-3
has caused the Debian Bug report #1016868,
regarding libc6-udeb: dangling ld-linux symlink
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.)


-- 
1016868: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1016868
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libc6-udeb
Version: 2.34-1
Severity: grave
Justification: renders package unusable
X-Debbugs-Cc: debian-b...@lists.debian.org

Hi,

Checking fil's report regarding runtime issues related to libc6-udeb,
which I thought to be a major version mismatch (d-i built against
unstable from a few hours ago = 2.33, but running against current
unstable = 2.34), I ended up with a fresh build that doesn't boot:
failure to execute /init.

Smallest bisection ever:
 - Building d-i against testing's udebs fixes it.
 - There are only a handful of differences… picking one “at random”.
 - Building d-i against testing's udebs except libc6-udeb from unstable
   generates the problem.

To get the booting issue out of the way, I've verified that I was able
to start busybox from the build tree after a netboot build against
testing's udebs, using this:

cd build/tmp/netboot/tree
sudo chroot . /bin/busybox sh

That's not the case after a build against unstable's udebs. Of course,
strace cannot report much:

chroot(".") = 0
chdir("/")  = 0
execve("bin/busybox", […])  = -1 ENOENT (No such file or 
directory)

Looking at the contents of the udebs before/after, a number of files and
symlinks are different, and there's one missing piece:

 - before:

./lib/x86_64-linux-gnu/ld-linux-x86-64.so.2 -> ld-2.33.so
./lib64/ld-linux-x86-64.so.2 -> /lib/x86_64-linux-gnu/ld-2.33.so

 - after:

./lib64/ld-linux-x86-64.so.2 -> /lib/x86_64-linux-gnu/ld-linux-x86-64.so.2

Thanks to Aurélien for investigating at the same time as I did, and for
the upcoming fix!


Cheers,
-- 
Cyril Brulebois (k...@debian.org)
D-I release manager -- Release team member -- Freelance Consultant
--- End Message ---
--- Begin Message ---
Source: glibc
Source-Version: 2.34-3
Done: Aurelien Jarno 

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

Debian distribution maintenance software
pp.
Aurelien Jarno  (supplier of updated glibc 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: Mon, 08 Aug 2022 19:38:30 +0200
Source: glibc
Architecture: source
Version: 2.34-3
Distribution: unstable
Urgency: medium
Maintainer: GNU Libc Maintainers 
Changed-By: Aurelien Jarno 
Closes: 1016868
Changes:
 glibc (2.34-3) unstable; urgency=medium
 .
   [ Aurelien Jarno ]
   * debian/rules.d/debhelper.mk: make libc.so and ld.so executable also for
 libc6-udeb.  Closes: #1016868.
Checksums-Sha1:
 487f8f11b6ab852eee443df91c549c3b28eb78cc 9673 glibc_2.34-3.dsc
 cef261ad7254d5675572abb6e40da4414631072d 995252 glibc_2.34-3.debian.tar.xz
 b9601ede3b326d76b40c0dd7bc240b8efee661ae 9470 glibc_2.34-3_source.buildinfo
Checksums-Sha256:
 6e6641424381d7593124f2ffb5b2a19bbcc24ecbcbdba59731980935318195c2 9673 
glibc_2.34-3.dsc
 464eb5482bfe62d66a4529937a7fdb08fecebf5d822aa9dd063b6c34c7aca761 995252 
glibc_2.34-3.debian.tar.xz
 d1a473fae60b69ceec0dee793d3ef0d04ada5ac008a27bfca2d53f81ce26b374 9470 
glibc_2.34-3_source.buildinfo
Files:
 6e394d7f296129260d25aa2855fddbc3 9673 libs required glibc_2.34-3.dsc
 5c591bbd62153095285ed590b743dee0 995252 libs required 
glibc_2.34-3.debian.tar.xz
 c2a0207d97622bac9c702adecda3e294 9470 libs required 
glibc_2.34-3_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEUryGlb40+QrX1Ay4E4jA+JnoM2sFAmLxSqAACgkQE4jA+Jno
M2u5MA/+LmgpiD1M22kNbnD/7t2SlRKKuRYMtCfgXp1zFUBM+w9dC/6G6aAamJqI
1QA0emfEqc1I0jJzVQeOH/tUzNfNHT+H0zME58uvGXtl9OoAn8SVIDJbJxiDQzb6
3MIcXywpBB40ssgzUNwoOzRCVuwOGETm76fqbS+u9WrHDmAE4zmzfMCArWLF3nJv

Bug#1016868: marked as pending in glibc

[Aurelien Jarno]

Control: tag -1 pending

Hello,

Bug #1016868 in glibc 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/glibc/-/commit/5a55ada45e43a6591dc0e8def944fadf6738a64b


debian/rules.d/debhelper.mk: make libc.so and ld.so executable also for 
libc6-udeb.  Closes: #1016868.


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1016868

Processed: Bug#1016868 marked as pending in glibc

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1016868 [libc6-udeb] libc6-udeb: dangling ld-linux symlink
Added tag(s) pending.

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

Bug#1016876: netkit-telnetd: missing Conflicts: telnetd-ssl

[Andreas Beckmann]

Package: netkit-telnetd
Version: 0.17-46
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package fails to upgrade from
'sid' to 'experimental'.
It installed fine in 'sid', then the upgrade to 'experimental' fails
because it tries to overwrite other packages files without declaring a
Breaks+Replaces relation.
This error may also be triggered by having a predecessor package from
'sid 'installed while installing the package from 'experimental'.

See policy 7.6 at
https://www.debian.org/doc/debian-policy/ch-relationships.html#overwriting-files-and-replacing-packages-replaces

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

  Preparing to unpack .../netkit-telnetd_0.17-46_amd64.deb ...
  Unpacking netkit-telnetd (0.17-46) ...
  dpkg: error processing archive 
/var/cache/apt/archives/netkit-telnetd_0.17-46_amd64.deb (--unpack):
   trying to overwrite '/usr/lib/telnetlogin', which is also in package 
telnetd-ssl 0.17.41+0.2-3.3+b1
  Errors were encountered while processing:
   /var/cache/apt/archives/netkit-telnetd_0.17-46_amd64.deb

These files are in conflict:
usr/lib/telnetlogin
usr/sbin/in.telnetd
usr/share/man/man5/issue.net.5.gz
usr/share/man/man8/in.telnetd.8.gz
usr/share/man/man8/telnetlogin.8.gz

telnetd-ssl has a 'Conflicts: telnetd', but that is no longer effective
after the rename to netkit-telnetd.


cheers,

Andreas


telnetd-ssl=0.17.41+0.2-3.3+b1_netkit-telnetd=0.17-46.log.gz
Description: application/gzip

Processed: [bts-link] source package src:meson

[Debian Bug Tracking System]

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

> #
> # bts-link upstream status pull for source package src:meson
> # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html
> # https://bts-link-team.pages.debian.net/bts-link/
> #
> user debian-bts-l...@lists.debian.org
Setting user to debian-bts-l...@lists.debian.org (was 
debian-bts-l...@lists.debian.org).
> # remote status report for #1014417 (http://bugs.debian.org/1014417)
> # Bug title: meson: test changes causes FTBFS
> #  * https://github.com/mesonbuild/meson/issues/10577
> #  * remote status changed: open -> closed
> #  * closed upstream
> tags 1014417 + fixed-upstream
Bug #1014417 [src:meson] meson: test changes causes FTBFS
Added tag(s) fixed-upstream.
> usertags 1014417 - status-open
Usertags were: status-open.
There are now no usertags set.
> usertags 1014417 + status-closed
There were no usertags set.
Usertags are now: status-closed.
> thanks
Stopping processing here.

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

Processed: Pending renpy issues

[Debian Bug Tracking System]

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

> tags 1006540 pending
Bug #1006540 [renpy] renpy: Move package to experimental while porting is still 
in progress
Added tag(s) pending.
> tags 938351 pending
Bug #938351 [src:renpy] renpy: Python2 removal in sid/bullseye
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#1012112: marked as done (FTBFS: : commitBuffer: invalid argument (invalid character))

[Debian Bug Tracking System]

Your message dated Mon, 8 Aug 2022 12:55:43 -0400 (EDT)
with message-id 
and subject line Fixed in haskell-devscripts 0.16.26
has caused the Debian Bug report #1012112,
regarding FTBFS: : commitBuffer: invalid argument (invalid character)
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.)


-- 
1012112: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1012112
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: haskell-hslua
Version: 1.0.3.2-1
Severity: serious
Tags: ftbfs, experimental
Justification: FTBFS

haskell-hslua fails to build from source:

> Non-zero exit code 1.
> /usr/bin/ghc --abi-hash -fbuilding-cabal-package -O -outputdir dist-
> ghc/build -odir dist-ghc/build -hidir dist-ghc/build -stubdir dist-
> ghc/build -i -idist-ghc/build -isrc -idist-ghc/build/autogen -idist-
> ghc/build/global-autogen -Idist-ghc/build/autogen -Idist-
> ghc/build/global-autogen -Idist-ghc/build -Icbits/error-conversion -
> Icbits/lua-5.3.5 -Idist-ghc/build/cbits/error-conversion -Idist-
> ghc/build/cbits/lua-5.3.5 -optP-DALLOW_UNSAFE_GC -optP-include -
> optPdist-ghc/build/autogen/cabal_macros.h -this-unit-id hslua-
> 1.0.3.2-1rNAq5opTyE8C0t4pf60eS -hide-all-packages -Wmissing-home-
> modules -no-user-package-db -XHaskell2010 -XCApiFFI -
> XForeignFunctionInterface -XLambdaCase Foreign.Lua Foreign.Lua.Core
> Foreign.Lua.Core.Constants Foreign.Lua.Core.Error
> Foreign.Lua.Core.RawBindings Foreign.Lua.Core.Types
> Foreign.Lua.FunctionCalling Foreign.Lua.Module Foreign.Lua.Types
> Foreign.Lua.Types.Peekable Foreign.Lua.Types.Pushable
> Foreign.Lua.Userdata Foreign.Lua.Util -Wall -optl-Wl,-z,relro
> name: hslua
> version:  1.0.3.2
> visibility:   public
> id:   hslua-1.0.3.2-1rNAq5opTyE8C0t4pf60eS
> key:  hslua-1.0.3.2-1rNAq5opTyE8C0t4pf60eS
> license:  MIT
> copyright:
> : commitBuffer: invalid argument (invalid character)
> make: *** [/usr/share/cdbs/1/class/hlibrary.mk:172: install/libghc-
> hslua-dev] Error 25
> 

This is because the locale is not set to a UTF-8 locale.

-- 
Robert



signature.asc
Description: This is a digitally signed message part
--- End Message ---
--- Begin Message ---

haskell-hslua 2.1.0-1 now building fine on reproducibility:
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/haskell-hslua.html--- End Message ---

Bug#1014720: marked as done (FTBFS: test failure in t/update_mirror.t)

[Debian Bug Tracking System]

Your message dated Mon, 08 Aug 2022 17:04:06 +
with message-id 
and subject line Bug#1014720: fixed in libcpan-mini-inject-perl 0.35-5
has caused the Debian Bug report #1014720,
regarding FTBFS: test failure in t/update_mirror.t
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.)


-- 
1014720: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1014720
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libcpan-mini-inject-perl
Version: 0.33-2
Severity: serious
Tags: ftbfs
Justification: fails to build from source

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

As also seen by the autopkgtests on ci.debian.net,
this package has recently started to fail its tests, which also
causes a build failure:

unable to contact the remote mirror at t/update_mirror.t line 35.
# Looks like your test exited with 111 just after 1.
t/update_mirror.t .. 
1..8
CPANServer: You can connect to your server at http://localhost:45571/
ok 1 - HTTP Server started
Dubious, test returned 111 (wstat 28416, 0x6f00)
Failed 7/8 subtests 

Cf. 
https://ci.debian.net/data/autopkgtest/unstable/amd64/libc/libcpan-mini-inject-perl/23466863/log.gz


Cheers,
gregor

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

Kernel: Linux 5.15.0-3-amd64 (SMP w/4 CPU threads)
Kernel taint flags: TAINT_WARN, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=C, LC_CTYPE=de_AT.utf8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)
LSM: AppArmor: enabled

-BEGIN PGP SIGNATURE-

iQKTBAEBCgB9FiEE0eExbpOnYKgQTYX6uzpoAYZJqgYFAmLLM01fFIAALgAo
aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldEQx
RTEzMTZFOTNBNzYwQTgxMDREODVGQUJCM0E2ODAxODY0OUFBMDYACgkQuzpoAYZJ
qgZv3hAAkEKQ4wLSaPQLra7K6jujHVY3z8HnSZaNoLlWeqPf5x/Gs4q586At6I2g
uyukFGYpFB8jRdZEqplX6Tc+iJ42m7LcCbkmBT1VNwpzo8lKtvMuiv1qWvUzCawP
/AiFBS817x/MIEVWQfzq1uMPzf7BY25Pd/7eQXKOMmA/tljRcMD5QE51suYymxw2
N4gJ/gslDqNzd25yd+AZNK6AdrxpkfBR8h59OjsyYuR9vauaRiOYxZcqawSkKAXI
ZT03Zb56Ov0vLMBK/wUu/qk/Lm+zEhjNY3x3JOhVuY2UQyLPrEDyFK7q6r5aNqaE
rPJi+5DIHzikw1SwA18ye2RYwYWd0Af6iTcHh5tXR/dWUXxeB5V/5j2iVgUvPZk5
QUwoJMz9CK1S3ctoxUH7uf2vVFibF7/83LB5GJJaaqFn2ArC32EjcFjzXiDLBtIo
kqlSUi01z26AP/BsEneYPUWOo9DU/+GjsofD3cbY+u34O0pY257XINCOMjZjIAPq
hit4RXHTRuN1EVdaSV/RLFSb0r2Ge/Mf/MQWjdaQ6gR/pLSWuiyPuPd23tSxKNdG
k7PXEGmRBgRCS22uQTYQv3yMpPWdPjfj9s2cipFj2+YaH/XvhiGCVH3+XbGZityJ
igKtJwz933wJU8cFF7NvQV4t/DH93ii8sl/4qc0Lm2hDfldtge0=
=3zuR
-END PGP SIGNATURE-
--- End Message ---
--- Begin Message ---
Source: libcpan-mini-inject-perl
Source-Version: 0.35-5
Done: gregor herrmann 

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

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

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

Debian distribution maintenance software
pp.
gregor herrmann  (supplier of updated 
libcpan-mini-inject-perl 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: Mon, 08 Aug 2022 18:48:28 +0200
Source: libcpan-mini-inject-perl
Architecture: source
Version: 0.35-5
Distribution: unstable
Urgency: medium
Maintainer: Debian Perl Group 
Changed-By: gregor herrmann 
Closes: 1014720
Changes:
 libcpan-mini-inject-perl (0.35-5) unstable; urgency=medium
 .
   [ Lukas Märdian ]
   * d/p/ignore-die-in-eval.patch:
 Fix test failure if Regexp::IPv6 is missing
 (LP: #1981608) (Closes: #1014720)
 .
   [ gregor herrmann ]
   * Revert "(Build-)Depend on working liburi-perl versions."
 Depending on specific liburi-perl versions (and forcing
 libregexp-ipv6-perl in) was hiding the actual problem.
 Thanks to Lukas Märdian.
Checksums-Sha1:
 f6df950169cdb4b629d325c15e4b8a057dd28c99 2804 
libcpan-mini-inject-perl_0.35-5.dsc
 9412156662647646105d6f54ad140cd0e1cd5e9c 3080 
libcpan-mini-inject-perl_0.35-5.debian.tar.xz
Checksums-Sha256:
 

Bug#1016620: marked as done (nvidia-graphics-drivers-tesla-470: CVE-2022-31607, CVE-2022-31608, CVE-2022-31615)

[Debian Bug Tracking System]

Your message dated Mon, 08 Aug 2022 16:50:04 +
with message-id 
and subject line Bug#1016620: fixed in nvidia-graphics-drivers-tesla-470 
470.141.03-1
has caused the Debian Bug report #1016620,
regarding nvidia-graphics-drivers-tesla-470: CVE-2022-31607, CVE-2022-31608, 
CVE-2022-31615
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.)


-- 
1016620: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1016620
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: nvidia-graphics-drivers
Severity: serious
Tags: security upstream
Control: clone -1 -2 -3 -4 -5 -6 -7 -8
Control: reassign -2 src:nvidia-graphics-drivers-legacy-340xx 340.76-6
Control: retitle -2 nvidia-graphics-drivers-legacy-340xx: CVE-2022-31607, 
CVE-2022-31608, CVE-2022-31615
Control: tag -2 + wontfix
Control: reassign -3 src:nvidia-graphics-drivers-legacy-390xx 390.48-4
Control: retitle -3 nvidia-graphics-drivers-legacy-390xx: CVE-2022-31607, 
CVE-2022-31608, CVE-2022-31615
Control: reassign -4 src:nvidia-graphics-drivers-tesla-418 418.87.01-1
Control: retitle -4 nvidia-graphics-drivers-tesla-418: CVE-2022-31607, 
CVE-2022-31608, CVE-2022-31615
Control: tag -4 + wontfix
Control: reassign -5 src:nvidia-graphics-drivers-tesla-450 450.51.05-1
Control: retitle -5 nvidia-graphics-drivers-tesla-450: CVE-2022-31607, 
CVE-2022-31608, CVE-2022-31615
Control: reassign -6 src:nvidia-graphics-drivers-tesla-460 460.32.03-1
Control: retitle -6 nvidia-graphics-drivers-tesla-460: CVE-2022-31607, 
CVE-2022-31608, CVE-2022-31615
Control: tag -6 + wontfix
Control: close -6 460.106.00-3
Control: reassign -7 src:nvidia-graphics-drivers-tesla-470 470.57.02-1
Control: retitle -7 nvidia-graphics-drivers-tesla-470: CVE-2022-31607, 
CVE-2022-31608, CVE-2022-31615
Control: reassign -8 src:nvidia-graphics-drivers-tesla-510 510.47.03-1
Control: retitle -8 nvidia-graphics-drivers-tesla-510: CVE-2022-31607, 
CVE-2022-31608, CVE-2022-31615
Control: found -1 340.24-1
Control: found -1 343.22-1
Control: found -1 396.18-1
Control: found -1 430.14-1
Control: found -1 455.23.04-1
Control: found -1 465.24.02-1
Control: found -1 495.44-1

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

CVE-2022-31607  NVIDIA GPU Display Driver for Linux contains a
vulnerability in the kernel mode layer (nvidia.ko), where a local user
with basic capabilities can cause improper input validation, which may
lead to denial of service, escalation of privileges, data tampering, and
limited information disclosure.

CVE-2022-31608  NVIDIA GPU Display Driver for Linux contains a
vulnerability in an optional D-Bus configuration file, where a local
user with basic capabilities can impact protected D-Bus endpoints, which
may lead to code execution, denial of service, escalation of privileges,
information disclosure, and data tampering.

CVE-2022-31615  NVIDIA GPU Display Driver for Linux contains a
vulnerability in the kernel mode layer, where a local user with basic
capabilities can cause a null-pointer dereference, which may lead to
denial of service.

Linux Driver Branch CVE IDs Addressed
R515, R510, R470, R450, R390CVE-2022-31607, CVE-2022-31608, CVE-2022-31615


Andreas
--- End Message ---
--- Begin Message ---
Source: nvidia-graphics-drivers-tesla-470
Source-Version: 470.141.03-1
Done: Andreas Beckmann 

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

Debian distribution maintenance software
pp.
Andreas Beckmann  (supplier of updated 
nvidia-graphics-drivers-tesla-470 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: Mon, 08 Aug 2022 18:22:03 +0200
Source: nvidia-graphics-drivers-tesla-470
Architecture: source
Version: 470.141.03-1
Distribution: unstable
Urgency: medium
Maintainer: Debian NVIDIA Maintainers 
Changed-By: Andreas Beckmann 
Closes: 1016620
Changes:
 nvidia-graphics-drivers-tesla-470 (470.141.03-1) unstable; urgency=medium
 .
   * New upstream Tesla release 470.141.03 (2022-08-02).
 * Fixed CVE-2022-31607, CVE-2022-31608, CVE-2022-31615. 

Bug#1014720: FTBFS: test failure in t/update_mirror.t

[gregor herrmann]

On Mon, 08 Aug 2022 18:12:44 +0200, Lukas Märdian wrote:

> I think using the newer version of liburi-perl (using libregexp-ipv6-perl
> dependency) is just hiding the actuall issue.

[…]

Thanks!

Applied and uploaded.
 

Cheers,
gregor

-- 
 .''`.  https://info.comodo.priv.at -- Debian Developer https://www.debian.org
 : :' : OpenPGP fingerprint D1E1 316E 93A7 60A8 104D  85FA BB3A 6801 8649 AA06
 `. `'  Member VIBE!AT & SPI Inc. -- Supporter Free Software Foundation Europe
   `-   


signature.asc
Description: Digital Signature

Bug#1016307: marked as done (gtk4: FTBFS: make[1]: *** [debian/rules:264: override_dh_auto_test] Error 1)

[Debian Bug Tracking System]

Your message dated Mon, 8 Aug 2022 17:47:03 +0100
with message-id 
and subject line Re: Bug#1015039: gtk4 memorytexture test-case regresses with 
Mesa 22.1
has caused the Debian Bug report #1015039,
regarding gtk4: FTBFS: make[1]: *** [debian/rules:264: override_dh_auto_test] 
Error 1
to be marked as done.

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

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


-- 
1015039: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1015039
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: gtk4
Version: 4.6.6+ds-1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20220728 ftbfs-bookworm

Hi,

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


Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> env \
>   BUILDDIR=debian/build/deb \
>   FUZZY_GSK_COMPARE="" \
>   FUZZY_REFTESTS="border-image-url label-attribute-preference 
> label-wrap-justify pseudoclass-on-box quit-mnemonic " \
>   IGNORE_GSK_COMPARE="unaligned-offscreen " \
>   IGNORE_REFTESTS="" \
>   XFAIL_GSK_COMPARE="" \
>   XFAIL_REFTESTS="label-sizing sizegroups-evolution-identity-page " \
>   BACKENDS="x11 wayland" \
> debian/run-tests.sh -t 1 \
>\
>   
> + BUILDDIR=debian/build/deb
> + BACKENDS=x11 wayland
> + FUZZY_GSK_COMPARE=
> + IGNORE_GSK_COMPARE=unaligned-offscreen 
> + XFAIL_GSK_COMPARE=
> + FUZZY_REFTESTS=border-image-url label-attribute-preference 
> label-wrap-justify pseudoclass-on-box quit-mnemonic 
> + IGNORE_REFTESTS=
> + XFAIL_REFTESTS=label-sizing sizegroups-evolution-identity-page 
> + mktemp -d -t debian-test-data-
> + test_data=/tmp/debian-test-data-12vpDUZV
> + mkdir -p /tmp/debian-test-data-12vpDUZV
> + trap cleanup EXIT INT
> + [ ! -d /sbuild-nonexistent ]
> + export HOME=/tmp/debian-test-data-12vpDUZV/home
> + mkdir -p /tmp/debian-test-data-12vpDUZV/home
> + [ ! -d  ]
> + export XDG_RUNTIME_DIR=/tmp/debian-test-data-12vpDUZV/xdg-runtime
> + mkdir -p /tmp/debian-test-data-12vpDUZV/xdg-runtime
> + cp debian/close-enough.keyfile testsuite/reftests/border-image-url.keyfile
> + cp debian/close-enough.keyfile 
> testsuite/reftests/label-attribute-preference.keyfile
> + cp debian/close-enough.keyfile testsuite/reftests/label-wrap-justify.keyfile
> + cp debian/close-enough.keyfile testsuite/reftests/pseudoclass-on-box.keyfile
> + cp debian/close-enough.keyfile testsuite/reftests/quit-mnemonic.keyfile
> + cp debian/ignore.keyfile testsuite/gsk/compare/unaligned-offscreen.keyfile
> + mkdir -p /tmp/debian-test-data-12vpDUZV/glib-2.0/schemas/
> + cp gtk/org.gtk.gtk4.Settings.ColorChooser.gschema.xml 
> gtk/org.gtk.gtk4.Settings.Debug.gschema.xml 
> gtk/org.gtk.gtk4.Settings.EmojiChooser.gschema.xml 
> gtk/org.gtk.gtk4.Settings.FileChooser.gschema.xml 
> /tmp/debian-test-data-12vpDUZV/glib-2.0/schemas/
> + glib-compile-schemas /tmp/debian-test-data-12vpDUZV/glib-2.0/schemas/
> + env -u LD_PRELOAD GIO_MODULE_DIR=/nonexistent GIO_USE_VFS=local 
> GIO_USE_VOLUME_MONITOR=unix dbus-run-session -- debian/tests/run-with-display 
> x11 debian/tests/run-with-locales --generate de_DE.UTF-8 --generate 
> en_GB.UTF-8 --generate en_US.UTF-8 --generate sv_SE=ISO-8859-1 -- meson test 
> -C debian/build/deb --print-errorlogs --setup=x11 -t 1
> run-with-locales: de_DE.UTF-8...
>   Character set: UTF-8
>   Source file: de_DE
>   Output: /tmp/tmp.LgDE3IW30E/de_DE.utf8
> run-with-locales: en_GB.UTF-8...
>   Character set: UTF-8
>   Source file: en_GB
>   Output: /tmp/tmp.LgDE3IW30E/en_GB.utf8
> run-with-locales: en_US.UTF-8...
>   Character set: UTF-8
>   Source file: en_US
>   Output: /tmp/tmp.LgDE3IW30E/en_US.utf8
> run-with-locales: sv_SE=ISO-8859-1...
>   Character set: ISO-8859-1
>   Source file: sv_SE
>   Output: /tmp/tmp.LgDE3IW30E/sv_SE
> ninja: Entering directory `/<>/debian/build/deb'
> ninja: no work to do.
>   1/681 gtk:gdk / array   
>   OK  0.01s   16 subtests passed
>   2/681 gtk:gdk / cairo   
>   OK  0.08s   1 subtests passed
>   3/681 gtk:gdk / contentformats  
>   OK  0.09s   4 subtests passed
>   4/681 gtk:gdk / contentserializer   
>   OK  0.09s   8 subtests passed
>   5/681 gtk:gdk / cursor  
>

Bug#1011132: marked as done (metakernel: please s/python2-doc/python3-doc/)

[Debian Bug Tracking System]

Your message dated Mon, 08 Aug 2022 16:19:44 +
with message-id 
and subject line Bug#1011132: fixed in metakernel 0.27.5-4
has caused the Debian Bug report #1011132,
regarding metakernel: please s/python2-doc/python3-doc/
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.)


-- 
1011132: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1011132
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: metakernel
Version: 0.27.5-3
Severity: important

Hi!
This package Build-Depends on python2-doc which blocks py2 removal, yet it
appears that it builds correctly with python3-doc.  Thus, please bump the
dependency so we can continue.


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

Kernel: Linux 5.18.0-rc7-00017-gb98e4da6cb5a (SMP w/64 CPU threads)
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)
--- End Message ---
--- Begin Message ---
Source: metakernel
Source-Version: 0.27.5-4
Done: Boyuan Yang 

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

Debian distribution maintenance software
pp.
Boyuan Yang  (supplier of updated metakernel 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: Mon, 08 Aug 2022 11:53:04 -0400
Source: metakernel
Architecture: source
Version: 0.27.5-4
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Team 
Changed-By: Boyuan Yang 
Closes: 1011132
Changes:
 metakernel (0.27.5-4) unstable; urgency=medium
 .
   * Team upload.
 .
   [ Debian Janitor ]
   * Set upstream metadata fields: Bug-Database, Bug-Submit, Repository,
 Repository-Browse.
 .
   [ Boyuan Yang ]
   * debian/control: s/python2-doc/python3-doc. (Closes: #1011132)
   * debian/control: Bump Standards-Version to 4.6.1.
Checksums-Sha1:
 0c1d11f4085b6d97515aff1afb872f33cf5cef8f 2703 metakernel_0.27.5-4.dsc
 6458d2ea13ab855dc05064ba6f3d71473948ba49 289100 metakernel_0.27.5.orig.tar.gz
 52b4aed840ade8042a25401fd2825bfa909a511e 6020 metakernel_0.27.5-4.debian.tar.xz
 b606792d1cc278b96bbfa335d964134f1f57a642 11179 
metakernel_0.27.5-4_amd64.buildinfo
Checksums-Sha256:
 43880e077edb6d9e3b60d943c1d0f3a57fb48286d6c3b916cb0baf9ba113fb36 2703 
metakernel_0.27.5-4.dsc
 57e17012a673d14778b725df738be4b1e8aa4d7f5c6cbf9061abef7cfac9771c 289100 
metakernel_0.27.5.orig.tar.gz
 f8cfb36e147c33f5d55b4054505ccdec37426dcfd3b701b74201ad57bab9c490 6020 
metakernel_0.27.5-4.debian.tar.xz
 c16e039933394febbdc8effd8012e51273f70c985dbf9575f0dd808a2fb4ebe7 11179 
metakernel_0.27.5-4_amd64.buildinfo
Files:
 624f65654a76ab8980a5f994ff1b5922 2703 python optional metakernel_0.27.5-4.dsc
 b75dd8c48b6317581f1a909794532197 289100 python optional 
metakernel_0.27.5.orig.tar.gz
 458c42c05b324c79cf943190c61b12b0 6020 python optional 
metakernel_0.27.5-4.debian.tar.xz
 033cb4dc84170abc9b859d735587cc8d 11179 python optional 
metakernel_0.27.5-4_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEfncpR22H1vEdkazLwpPntGGCWs4FAmLxMwQACgkQwpPntGGC
Ws7ILw//a5tyu6g08q7NAGaQniOcw1pGQaiDP6jXXKfd/L891yP7IVWswX2qv59Z
zk+zwbcQTX2R+/zq6f7U4kSJYrgeyPXO+sWPr1nUa4RRsZoHRox52MoOO1MtBTJM
lwwm723MHjbms6MVO84ghsQhFQTSaHGbd+200nGpeaYK6uOxoQrBF2SK0hHG36fY
H8zcm2pCwLa0Uf24sEn1be3dWOHrpdUugMqmX4+xBHeH7WTuxP10Icb95S1wOgKt
bKBlfkVoz36jKob2t8rdm6zorNHHu0cBigbCHUwAUjsa1D3pbRQY9qetdWB8s0bo
Sv8ZIdjLspDLm27/4Nw6DZ072UJsB9awBzMkz8hqk7rwlEYGP4PX7nxCHPMl9yTP
2bQzYo5mRBtb38zPmgENuWDa+oK7rOFvEDAUFyt/qYM377BWywbxmW2Aiunb4KBt
uUS7iU0Wj/eOjJDVJGJtTln1JF1u7r0cdKIRP0WxpLaM414Ksutrtyv7GmYsGEJP
Ik34Z7yxxyr0lavKU0sBliuuw+S4ljQd70YvAxg6yN/YaGGwBIukoRFkfn6bzePo
CfVgi7JLk4erKwaIL2c14W9y2p0CcZ3L774/bAbwzAS6h0TolpDsebyWEJVz2rRs
nNrmUGA6KvZz9efWkef2WQIm1/I9jhYvXv9+qV/tUFjyXE49D/k=
=N/VV
-END PGP SIGNATURE End Message ---

Processed: Re: FTBFS: test failure in t/update_mirror.t

[Debian Bug Tracking System]

Processing control commands:

> tags -1 patch
Bug #1014720 {Done: gregor herrmann } 
[src:libcpan-mini-inject-perl] FTBFS: test failure in t/update_mirror.t
Added tag(s) patch.

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

Bug#1014720: FTBFS: test failure in t/update_mirror.t

[Lukas Märdian]

Package: libcpan-mini-inject-perl
Version: 0.35-4
Followup-For: Bug #1014720
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu kinetic ubuntu-patch
X-Debbugs-Cc: sl...@ubuntu.com
Control: tags -1 patch

Hi Gregor,

I think using the newer version of liburi-perl (using libregexp-ipv6-perl
dependency) is just hiding the actuall issue.

In Ubuntu we dropped liburi-perl's libregexp-ipv6-perl dependency back to a
Suggests and this issue reappeared. After some investigation, I found an error
in the DIE signal handling of libcpan-mini-inject-perl (in t/update_mirror.t).

See https://github.com/AndyA/CPAN--Mini--Inject/pull/26 for more details.

In Ubuntu, the attached patch was applied to achieve the following:

  * d/p/ignore-die-in-eval.patch: Fix test failure if Regexp::IPv6 is missing
(LP: #1981608)

Thanks for considering the patch.


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

Kernel: Linux 5.15.0-40-generic (SMP w/4 CPU threads)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_WARN, TAINT_OOT_MODULE
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
diff -Nru libcpan-mini-inject-perl-0.35/debian/patches/ignore-die-in-eval.patch 
libcpan-mini-inject-perl-0.35/debian/patches/ignore-die-in-eval.patch
--- libcpan-mini-inject-perl-0.35/debian/patches/ignore-die-in-eval.patch   
1970-01-01 01:00:00.0 +0100
+++ libcpan-mini-inject-perl-0.35/debian/patches/ignore-die-in-eval.patch   
2022-08-08 17:37:52.0 +0200
@@ -0,0 +1,20 @@
+Description: Ignore DIE signal inside eval blocks
+ The process will still be running and the error handled.
+ See: https://www.perlmonks.org/?node_id=1173708
+Author: Lukas Märdian 
+Forwarded: https://github.com/AndyA/CPAN--Mini--Inject/pull/26
+---
+--- libcpan-mini-inject-perl-0.35.orig/t/update_mirror.t
 libcpan-mini-inject-perl-0.35/t/update_mirror.t
+@@ -24,7 +24,10 @@ my $pid= $server->background;
+ ok( $pid, 'HTTP Server started' );
+ sleep 1;
+ 
+-$SIG{__DIE__} = sub { kill( 9, $pid ) };
++$SIG{__DIE__} = sub {
++  return if $^S; # ignore die in an eval block, while process is still running
++  kill( 9, $pid )
++};
+ 
+ my $mcpi = CPAN::Mini::Inject->new;
+ $mcpi->parsecfg( 't/.mcpani/config' );
diff -Nru libcpan-mini-inject-perl-0.35/debian/patches/series 
libcpan-mini-inject-perl-0.35/debian/patches/series
--- libcpan-mini-inject-perl-0.35/debian/patches/series 1970-01-01 
01:00:00.0 +0100
+++ libcpan-mini-inject-perl-0.35/debian/patches/series 2022-08-08 
17:37:52.0 +0200
@@ -0,0 +1 @@
+ignore-die-in-eval.patch

Bug#1012148: closing 1012148

[Ilias Tsitsimpis]

close 1012148 1.0.2-1
thanks

Bug#1012146: closing 1012146

[Ilias Tsitsimpis]

close 1012146 1.0.2-1
thanks

Bug#1011992: closing 1011992

[Ilias Tsitsimpis]

close 1011992 1.0.2-1
thanks

Bug#1015132: meson: FTBFS: test_junit_valid_gtest: Element 'testcase', attribute 'file': The attribute 'file' is not allowed

[Simon McVittie]

Control: retitle -1 meson: FTBFS: test_junit_valid_gtest: Element 'testcase', 
attribute 'file': The attribute 'file' is not allowed
Control: forwarded -1 https://github.com/mesonbuild/meson/pull/10634
Control: tags -1 + patch upstream

On Sat, 16 Jul 2022 at 20:55:02 +0200, Lucas Nussbaum wrote:
> The script I use to extract the failure from the log might have guessed
> badly indeed, however the build still fails
...
> However looking at the log I don't really understand why the
> override_dh_auto_test target fails.

I think it's probably this:

>debian/rules override_dh_auto_test
> make[1]: Entering directory '/<>'
> ./run_tests.py
...
> FAIL: test_junit_valid_gtest (unittests.allplatformstests.AllPlatformTests)
> --
> Traceback (most recent call last):
>   File "/<>/unittests/allplatformstests.py", line 3382, in 
> _test_junit
> schema.assertValid(junit)
>   File "src/lxml/etree.pyx", line 3638, in lxml.etree._Validator.assertValid
> lxml.etree.DocumentInvalid: Element 'testcase', attribute 'file': The 
> attribute 'file' is not allowed., line 3
> 
> During handling of the above exception, another exception occurred:
> 
> Traceback (most recent call last):
>   File "/<>/unittests/allplatformstests.py", line 3393, in 
> test_junit_valid_gtest
> self._test_junit(os.path.join(self.framework_test_dir, '2 gtest'))
>   File "/<>/unittests/allplatformstests.py", line 3384, in 
> _test_junit
> self.fail(e.error_log)
> AssertionError: 
> /<>/tmp30xzcj0v/meson-logs/testlog.junit.xml:3:0:ERROR:SCHEMASV:SCHEMAV_CVC_COMPLEX_TYPE_3_2_1:
>  Element 'testcase', attribute 'file': The attribute 'file' is not allowed.
> /<>/tmp30xzcj0v/meson-logs/testlog.junit.xml:3:0:ERROR:SCHEMASV:SCHEMAV_CVC_COMPLEX_TYPE_3_2_1:
>  Element 'testcase', attribute 'line': The attribute 'line' is not allowed.
> /<>/tmp30xzcj0v/meson-logs/testlog.junit.xml:4:0:ERROR:SCHEMASV:SCHEMAV_CVC_COMPLEX_TYPE_3_2_1:
>  Element 'testcase', attribute 'file': The attribute 'file' is not allowed.
> /<>/tmp30xzcj0v/meson-logs/testlog.junit.xml:4:0:ERROR:SCHEMASV:SCHEMAV_CVC_COMPLEX_TYPE_3_2_1:
>  Element 'testcase', attribute 'line': The attribute 'line' is not allowed.
> /<>/tmp30xzcj0v/meson-logs/testlog.junit.xml:7:0:ERROR:SCHEMASV:SCHEMAV_CVC_COMPLEX_TYPE_3_2_1:
>  Element 'testcase', attribute 'file': The attribute 'file' is not allowed.
> /<>/tmp30xzcj0v/meson-logs/testlog.junit.xml:7:0:ERROR:SCHEMASV:SCHEMAV_CVC_COMPLEX_TYPE_3_2_1:
>  Element 'testcase', attribute 'line': The attribute 'line' is not allowed.
> /<>/tmp30xzcj0v/meson-logs/testlog.junit.xml:8:0:ERROR:SCHEMASV:SCHEMAV_CVC_COMPLEX_TYPE_3_2_1:
>  Element 'testcase', attribute 'file': The attribute 'file' is not allowed.
> /<>/tmp30xzcj0v/meson-logs/testlog.junit.xml:8:0:ERROR:SCHEMASV:SCHEMAV_CVC_COMPLEX_TYPE_3_2_1:
>  Element 'testcase', attribute 'line': The attribute 'line' is not allowed.
...
> Ran 471 tests in 629.165s
> 
> FAILED (failures=1, skipped=59)

Ubuntu's meson package has this change vs. Debian which is probably the
solution:

  * googletest 1.12.1 started to emit additional JUnit4 schema invalid
testcase attributes, delete them when generating meson junit test
result. Fixing FTBFS with new googletest.

which seems to be the same change they sent upstream as
.

Ubuntu's meson package also applies patches to fix the regression #1014417.
http://launchpadlibrarian.net/614996822/meson_0.63.0-1_0.63.0-1ubuntu3.diff.gz

smcv

Processed: Re: Bug#1015132: meson: FTBFS: test_junit_valid_gtest: Element 'testcase', attribute 'file': The attribute 'file' is not allowed

[Debian Bug Tracking System]

Processing control commands:

> retitle -1 meson: FTBFS: test_junit_valid_gtest: Element 'testcase', 
> attribute 'file': The attribute 'file' is not allowed
Bug #1015132 [src:meson] meson: FTBFS: ./b 52a78b9866/../test cases/failing 
build/2 hidden symbol/bobuser.c:4: undefined reference to `hidden_function'
Changed Bug title to 'meson: FTBFS: test_junit_valid_gtest: Element 'testcase', 
attribute 'file': The attribute 'file' is not allowed' from 'meson: FTBFS: ./b 
52a78b9866/../test cases/failing build/2 hidden symbol/bobuser.c:4: undefined 
reference to `hidden_function''.
> forwarded -1 https://github.com/mesonbuild/meson/pull/10634
Bug #1015132 [src:meson] meson: FTBFS: test_junit_valid_gtest: Element 
'testcase', attribute 'file': The attribute 'file' is not allowed
Set Bug forwarded-to-address to 
'https://github.com/mesonbuild/meson/pull/10634'.
> tags -1 + patch upstream
Bug #1015132 [src:meson] meson: FTBFS: test_junit_valid_gtest: Element 
'testcase', attribute 'file': The attribute 'file' is not allowed
Added tag(s) patch and upstream.

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

Processed: Bug#1011132 marked as pending in metakernel

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1011132 [src:metakernel] metakernel: please s/python2-doc/python3-doc/
Added tag(s) pending.

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

Bug#1011132: marked as pending in metakernel

[Boyuan Yang]

Control: tag -1 pending

Hello,

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

https://salsa.debian.org/python-team/packages/metakernel/-/commit/a1ff4d2a97b13932b6480b6e743949c8a9d515dd


debian/control: s/python2-doc/python3-doc. (Closes: #1011132)


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1011132

Processed: closing 1012148

[Debian Bug Tracking System]

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

> close 1012148 1.0.2-1
Bug #1012148 [src:haskell-hslua-module-text] 
haskell-hslua-module-text_0.2.1-2.1_mips64el-buildd.changes REJECTED
The source 'haskell-hslua-module-text' and version '1.0.2-1' do not appear to 
match any binary packages
Marked as fixed in versions haskell-hslua-module-text/1.0.2-1.
Bug #1012148 [src:haskell-hslua-module-text] 
haskell-hslua-module-text_0.2.1-2.1_mips64el-buildd.changes REJECTED
Marked Bug as done
> thanks
Stopping processing here.

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

Processed: closing 1011992

[Debian Bug Tracking System]

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

> close 1011992 1.0.2-1
Bug #1011992 [src:haskell-hslua-module-text] ftbfs: : commitBuffer: 
invalid argument (invalid character)
The source 'haskell-hslua-module-text' and version '1.0.2-1' do not appear to 
match any binary packages
Marked as fixed in versions haskell-hslua-module-text/1.0.2-1.
Bug #1011992 [src:haskell-hslua-module-text] ftbfs: : commitBuffer: 
invalid argument (invalid character)
Marked Bug as done
> thanks
Stopping processing here.

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

Processed: closing 1012146

[Debian Bug Tracking System]

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

> close 1012146 1.0.2-1
Bug #1012146 [src:haskell-hslua-module-system] 
haskell-hslua-module-system_0.2.1-2.1_mips64el-buildd.changes REJECTED
Marked as fixed in versions haskell-hslua-module-system/1.0.2-1.
Bug #1012146 [src:haskell-hslua-module-system] 
haskell-hslua-module-system_0.2.1-2.1_mips64el-buildd.changes REJECTED
Marked Bug as done
> thanks
Stopping processing here.

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

Bug#1011989: closing 1011989

[Ilias Tsitsimpis]

close 1011989 1.0.2-1
thanks

Bug#1016868: libc6-udeb: dangling ld-linux symlink

[Cyril Brulebois]

Package: libc6-udeb
Version: 2.34-1
Severity: grave
Justification: renders package unusable
X-Debbugs-Cc: debian-b...@lists.debian.org

Hi,

Checking fil's report regarding runtime issues related to libc6-udeb,
which I thought to be a major version mismatch (d-i built against
unstable from a few hours ago = 2.33, but running against current
unstable = 2.34), I ended up with a fresh build that doesn't boot:
failure to execute /init.

Smallest bisection ever:
 - Building d-i against testing's udebs fixes it.
 - There are only a handful of differences… picking one “at random”.
 - Building d-i against testing's udebs except libc6-udeb from unstable
   generates the problem.

To get the booting issue out of the way, I've verified that I was able
to start busybox from the build tree after a netboot build against
testing's udebs, using this:

cd build/tmp/netboot/tree
sudo chroot . /bin/busybox sh

That's not the case after a build against unstable's udebs. Of course,
strace cannot report much:

chroot(".") = 0
chdir("/")  = 0
execve("bin/busybox", […])  = -1 ENOENT (No such file or 
directory)

Looking at the contents of the udebs before/after, a number of files and
symlinks are different, and there's one missing piece:

 - before:

./lib/x86_64-linux-gnu/ld-linux-x86-64.so.2 -> ld-2.33.so
./lib64/ld-linux-x86-64.so.2 -> /lib/x86_64-linux-gnu/ld-2.33.so

 - after:

./lib64/ld-linux-x86-64.so.2 -> /lib/x86_64-linux-gnu/ld-linux-x86-64.so.2

Thanks to Aurélien for investigating at the same time as I did, and for
the upcoming fix!


Cheers,
-- 
Cyril Brulebois (k...@debian.org)
D-I release manager -- Release team member -- Freelance Consultant

Bug#1016848: librecast: unknown section 'unknown'

[Vagrant Cascadian]

Control: tags 1016848 pending

On 2022-08-08, Graham Inggs wrote:
> Source: librecast
> Version: 0.5.1-2
> Severity: serious
>
> Hi Maintainer
>
> debian/control contains:
>
> Section: unknown

This was fixed in git a couple days ago:

  
https://salsa.debian.org/vagrant/librecast/-/commit/3d1f704693c1bdefc8bc440ee360de5a10932fcf

live well,
  vagrant


signature.asc
Description: PGP signature

Processed: Re: Bug#1016848: librecast: unknown section 'unknown'

[Debian Bug Tracking System]

Processing control commands:

> tags 1016848 pending
Bug #1016848 [src:librecast] librecast: unknown section 'unknown'
Added tag(s) pending.

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

Processed: closing 1011989

[Debian Bug Tracking System]

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

> close 1011989 1.0.2-1
Bug #1011989 [src:haskell-tasty-lua] FTBFS: : commitBuffer: invalid 
argument (invalid character)
The source 'haskell-tasty-lua' and version '1.0.2-1' do not appear to match any 
binary packages
Marked as fixed in versions haskell-tasty-lua/1.0.2-1.
Bug #1011989 [src:haskell-tasty-lua] FTBFS: : commitBuffer: invalid 
argument (invalid character)
Marked Bug as done
> thanks
Stopping processing here.

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

Bug#1014306: marked as done (crun - seriously out of date)

[Debian Bug Tracking System]

Your message dated Mon, 08 Aug 2022 13:49:13 +
with message-id 
and subject line Bug#1014306: fixed in crun 1.5+dfsg-1
has caused the Debian Bug report #1014306,
regarding crun - seriously out of date
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.)


-- 
1014306: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1014306
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: crun
Version: 0.17+dfsg-1.1+b1
Severity: serious

Moin

crun was not uploaded since before the release of Debian 11.  It is now
seriously out of date and even fails hard as root, see #1012053.

Bastian

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

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

Versions of packages crun depends on:
ii  libc62.33-7
ii  libcap2  1:2.44-1
ii  libseccomp2  2.5.4-1
ii  libsystemd0  251.2-7
ii  libyajl2 2.1.0-3

crun recommends no packages.

crun suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: crun
Source-Version: 1.5+dfsg-1
Done: Faidon Liambotis 

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

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

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

Debian distribution maintenance software
pp.
Faidon Liambotis  (supplier of updated crun 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: Mon, 08 Aug 2022 13:42:27 +0300
Source: crun
Architecture: source
Version: 1.5+dfsg-1
Distribution: unstable
Urgency: medium
Maintainer: Dmitry Smirnov 
Changed-By: Faidon Liambotis 
Closes: 1009881 1014306
Changes:
 crun (1.5+dfsg-1) unstable; urgency=medium
 .
   * New upstream release. (Closes: #1014306)
 - Includes a fix for CVE-2022-27650 (Closes: #1009881)
 - Remove patch zos.patch, was an upstream backport.
   * Replace invalid field Homepage by field Repository-Browse in upstream
 metadata. Also add Repository and Changelog fields.
   * Install crun.1 from the installed path in /usr/share/man, rather than the
 source tree, silencing a dh_missing warning.
   * Bump build-dep of golang-github-opencontainers-specs-dev to
 >= v1.0.2.102.ga8106e9, which includes commit 2792412 for cpu.idle.
   * Bump Standards-Version to 4.6.1, no changes needed.
   * Add myself to Uploaders.
Checksums-Sha1:
 fe3ff02ba811b844cbe6ebc19dc811c6b791db24 2072 crun_1.5+dfsg-1.dsc
 d055b36f37cfbdbddb3feb29358cd7f542e88dda 508168 crun_1.5+dfsg.orig.tar.xz
 dffb13a8eaea389489658ae999f80f7e30ca6df2 14844 crun_1.5+dfsg-1.debian.tar.xz
 204acb7f1254363cd90336c05aacf73e9572fdbc 6902 crun_1.5+dfsg-1_source.buildinfo
Checksums-Sha256:
 cf10591c2b36becf9ddcfe93683d72a4f43f28df2a20b119dc95343796b9f831 2072 
crun_1.5+dfsg-1.dsc
 bbae173f049876f69a9ec43e4ce332ef9dcfddfb4af88ce2926540f668c70594 508168 
crun_1.5+dfsg.orig.tar.xz
 1e7959c488e21902971c8f7bc88e007a786a2004448ae8498496741f72dee5a1 14844 
crun_1.5+dfsg-1.debian.tar.xz
 f6fb812d83341202cd3d93a5a9aec7dcacef5b1cbed41d1e9dd34ccebd774427 6902 
crun_1.5+dfsg-1_source.buildinfo
Files:
 d37bf23d3ec29e9d035c3dd811400ec2 2072 admin optional crun_1.5+dfsg-1.dsc
 0498a411563cd82fc23145da1b119d2a 508168 admin optional 
crun_1.5+dfsg.orig.tar.xz
 a418cebe404789e920d896cb8446618a 14844 admin optional 
crun_1.5+dfsg-1.debian.tar.xz
 c0abf28ee76691fef5f5d328d42d21eb 6902 admin optional 
crun_1.5+dfsg-1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEqVksUhy5BAd9ZZgAnQteWx7sjw4FAmLxEKsACgkQnQteWx7s
jw5o4BAAm+zFGNt/jrHGNIGyEF4B01NXG2WM9ELHwJpkaTJN65So7tjErKv6bbyB
xUj/fjIg56Gpb+lESO55LPWWXPsOjNbN6yDMp4//ROirO5lXYTxdq/nICv9YBmFR
BnDgx1aGOaW93GJ3HWV6rYSD2fQeRJuuMEtsoZue4kEaGPK3Pyrsz+a9PtTqgs8d
HqGcPlCOELmYrFk1XrvfWC5FxoaTz8vN597jQDnRxrgAgJwQ77Ypb54PB9dCIGvA
rNMnyYYO4ufZX9UJQKjKAEeE5ndLIFq6RF7VUjTKebU94kuRseIHgjKVFekjHSRf

Bug#1016614: marked as done (nvidia-graphics-drivers: CVE-2022-31607, CVE-2022-31608, CVE-2022-31615)

[Debian Bug Tracking System]

Your message dated Mon, 08 Aug 2022 13:36:55 +
with message-id 
and subject line Bug#1016614: fixed in nvidia-graphics-drivers 470.141.03-1
has caused the Debian Bug report #1016614,
regarding nvidia-graphics-drivers: CVE-2022-31607, CVE-2022-31608, 
CVE-2022-31615
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.)


-- 
1016614: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1016614
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: nvidia-graphics-drivers
Severity: serious
Tags: security upstream
Control: clone -1 -2 -3 -4 -5 -6 -7 -8
Control: reassign -2 src:nvidia-graphics-drivers-legacy-340xx 340.76-6
Control: retitle -2 nvidia-graphics-drivers-legacy-340xx: CVE-2022-31607, 
CVE-2022-31608, CVE-2022-31615
Control: tag -2 + wontfix
Control: reassign -3 src:nvidia-graphics-drivers-legacy-390xx 390.48-4
Control: retitle -3 nvidia-graphics-drivers-legacy-390xx: CVE-2022-31607, 
CVE-2022-31608, CVE-2022-31615
Control: reassign -4 src:nvidia-graphics-drivers-tesla-418 418.87.01-1
Control: retitle -4 nvidia-graphics-drivers-tesla-418: CVE-2022-31607, 
CVE-2022-31608, CVE-2022-31615
Control: tag -4 + wontfix
Control: reassign -5 src:nvidia-graphics-drivers-tesla-450 450.51.05-1
Control: retitle -5 nvidia-graphics-drivers-tesla-450: CVE-2022-31607, 
CVE-2022-31608, CVE-2022-31615
Control: reassign -6 src:nvidia-graphics-drivers-tesla-460 460.32.03-1
Control: retitle -6 nvidia-graphics-drivers-tesla-460: CVE-2022-31607, 
CVE-2022-31608, CVE-2022-31615
Control: tag -6 + wontfix
Control: close -6 460.106.00-3
Control: reassign -7 src:nvidia-graphics-drivers-tesla-470 470.57.02-1
Control: retitle -7 nvidia-graphics-drivers-tesla-470: CVE-2022-31607, 
CVE-2022-31608, CVE-2022-31615
Control: reassign -8 src:nvidia-graphics-drivers-tesla-510 510.47.03-1
Control: retitle -8 nvidia-graphics-drivers-tesla-510: CVE-2022-31607, 
CVE-2022-31608, CVE-2022-31615
Control: found -1 340.24-1
Control: found -1 343.22-1
Control: found -1 396.18-1
Control: found -1 430.14-1
Control: found -1 455.23.04-1
Control: found -1 465.24.02-1
Control: found -1 495.44-1

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

CVE-2022-31607  NVIDIA GPU Display Driver for Linux contains a
vulnerability in the kernel mode layer (nvidia.ko), where a local user
with basic capabilities can cause improper input validation, which may
lead to denial of service, escalation of privileges, data tampering, and
limited information disclosure.

CVE-2022-31608  NVIDIA GPU Display Driver for Linux contains a
vulnerability in an optional D-Bus configuration file, where a local
user with basic capabilities can impact protected D-Bus endpoints, which
may lead to code execution, denial of service, escalation of privileges,
information disclosure, and data tampering.

CVE-2022-31615  NVIDIA GPU Display Driver for Linux contains a
vulnerability in the kernel mode layer, where a local user with basic
capabilities can cause a null-pointer dereference, which may lead to
denial of service.

Linux Driver Branch CVE IDs Addressed
R515, R510, R470, R450, R390CVE-2022-31607, CVE-2022-31608, CVE-2022-31615


Andreas
--- End Message ---
--- Begin Message ---
Source: nvidia-graphics-drivers
Source-Version: 470.141.03-1
Done: Andreas Beckmann 

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

Debian distribution maintenance software
pp.
Andreas Beckmann  (supplier of updated nvidia-graphics-drivers 
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: Mon, 08 Aug 2022 14:52:56 +0200
Source: nvidia-graphics-drivers
Architecture: source
Version: 470.141.03-1
Distribution: unstable
Urgency: medium
Maintainer: Debian NVIDIA Maintainers 
Changed-By: Andreas Beckmann 
Closes: 1016614 1016736
Changes:
 nvidia-graphics-drivers (470.141.03-1) unstable; urgency=medium
 .
   * New upstream production branch release 470.141.03 (2022-08-02).
 * Fixed CVE-2022-31607, CVE-2022-31608, CVE-2022-31615. (Closes: #1016614)
   

Bug#1016402: marked as done (switch build depends on libnetpbm10-dev to libnetpbm-dev)

[Debian Bug Tracking System]

Your message dated Mon, 08 Aug 2022 12:05:14 +
with message-id 
and subject line Bug#1016402: fixed in pfstools 2.2.0-4
has caused the Debian Bug report #1016402,
regarding switch build depends on libnetpbm10-dev to libnetpbm-dev
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.)


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

Source: astrometry.net
Severity: serious
Control: clone -1 -2 -3 -4 -5
Control: reassign -2 src:ncview
Control: reassign -3 src:pfstools
Control: reassign -4 src:xjig
Control: reassign -5 src:xplanet

Dear maintainers,

Your package build depends on libnetpbm10-dev, but that binary isn't 
built anymore. Please build depend on the developement package without 
version in the name: libnetpbm-dev (currently provided by 
libnetpbm11-dev but hopefully in some future as a stand alone binary, 
bug #1007984).


Paul


OpenPGP_signature
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Source: pfstools
Source-Version: 2.2.0-4
Done: Andreas Metzler 

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

Debian distribution maintenance software
pp.
Andreas Metzler  (supplier of updated pfstools 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: Mon, 08 Aug 2022 13:24:50 +0200
Source: pfstools
Architecture: source
Version: 2.2.0-4
Distribution: unstable
Urgency: medium
Maintainer: Debian PhotoTools Maintainers 

Changed-By: Andreas Metzler 
Closes: 1014141 1016402
Changes:
 pfstools (2.2.0-4) unstable; urgency=medium
 .
   * Build-depend on octave-dev instead of transitional package liboctave-dev.
 Closes: #1014141
   * Build-depend on libnetpbm11-dev|libnetpbm-dev. Closes: #1016402
   * Migrate lintian overrides with lintian-migrate-overrides-to-pointed-hints.
Checksums-Sha1: 
 19a43390d55f8231b52a7a86570e4ac8ab2e2ed3 2465 pfstools_2.2.0-4.dsc
 df3f1f73d902ae6496caa975c9860e7e38f8 37588 pfstools_2.2.0-4.debian.tar.xz
Checksums-Sha256: 
 bd4303061fb8321e8bc1e8caec26dba7dd9627fece62a5728b680e560283a44e 2465 
pfstools_2.2.0-4.dsc
 003fbd28fa207faa26d92b68c505ae52983b4211559e0213ec977eebdac72ec4 37588 
pfstools_2.2.0-4.debian.tar.xz
Files: 
 b38a08035972d5761521e0d34b45f518 2465 graphics optional pfstools_2.2.0-4.dsc
 34135e60792c760f9bb4417a862ec417 37588 graphics optional 
pfstools_2.2.0-4.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEE0uCSA5741Jbt9PpepU8BhUOCFIQFAmLw91cACgkQpU8BhUOC
FITLsw//dfPr/+w3JEfQffUAyN/FZMpCHTVSfWMNzWSdNfdhyRDCXlKzBInyr4/i
TVSodi18UK29Bj+/L1uOsGwTMRBcYOwqvHSB+B9Q4g3yVMEjVEX/A3ZNj/gRwRQC
J7ebif06TazmZGmaCnHHghe8IJjs3FHPrf9ButK0N6OIV6O/n08grgBPYLjd07xg
eLL5LQ1+9ULKDymq1UmL5547ZZ5WW1vmWN+VI0O5xkBDoHlX9P4tjO0DAMJ+ndit
H1iYMdJfIkktYIN5XM8y+pu1Mv8jP8f84b86SjIJwhaZSZDusWq6qMUegRCJobL5
W/VQu2lEe26P3MTO2hKNqk0MZTxkycjsk+5Nd9ZY09bBg/UET8Fq9fu3RUYYQQ+K
2j2yQ4Yif9HHuCd4+PP+4BYQmrXdb3B21O1KIyhurJZsGkTcR+IiTC+jQvguThCI
2H9QnnNZYbzyMWHs9Ae1duG+gEnidA71W4I3kzyJ6qV7JvmjEwRdbK1RLMB+cqCm
nt59SzRUxNed4XKThrCo1XxkregIEYrqNQQe2/ekERMwSL1mwOy+lOVL3gAJdcol
UZttanw3fgVDdA8GFlxLYpeA+hpnTrGf8+dIUlqfHRNHdWZBL3rqyxghB17KAjFr
42eMXRBrA9rVpSOLYcpHpXjVPW6S9ff3F3kX34X/flO/VnqMqN4=
=95o0
-END PGP SIGNATURE End Message ---

Bug#1016848: librecast: unknown section 'unknown'

[Graham Inggs]

Source: librecast
Version: 0.5.1-2
Severity: serious

Hi Maintainer

debian/control contains:

Section: unknown

Regards
Graham

Bug#1016842: vim-youcompleteme: vim-tests-gopls fails with gopls/1:0.1.12+ds-1

[Shengjing Zhu]

Source: vim-youcompleteme
Version: 0+20220402+git3ededae+ds-3
Severity: serious
X-Debbugs-Cc: z...@debian.org

The test is wrong to assume the fixtures provided by gopls are always same.
The failed test blocks gopls migrating to testing.

Bug#1016820: marked as done (libnss-db: FTBFS with glibc 2.34)

[Debian Bug Tracking System]

Your message dated Mon, 08 Aug 2022 10:49:08 +
with message-id 
and subject line Bug#1016820: fixed in libnss-db 2.2.3pre1-7
has caused the Debian Bug report #1016820,
regarding libnss-db: FTBFS with glibc 2.34
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.)


-- 
1016820: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1016820
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libnss-db
Version: 2.2.3pre1-6
Severity: serious
Tags: ftbfs sid bookworm
Justification: fails to build from source (but built successfully in the past)
X-Debbugs-Cc: sramac...@debian.org

https://buildd.debian.org/status/fetch.php?pkg=libnss-db=arm64=2.2.3pre1-6%2Bb13=1659914807=0

/bin/bash ../libtool  --tag=CC   --mode=link gcc  -g -O2 
-ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -version-info 2 
-Wl,--version-script=../../src/libnss_db.map -Wl,-z,relro -o libnss_db.la 
-rpath /lib/aarch64-linux-gnu db-alias.lo db-ethers.lo db-netgrp.lo db-grp.lo 
db-proto.lo db-pwd.lo db-rpc.lo db-service.lo db-spwd.lo db-compat.lo 
db-open.lo -lnss_files -ldb 
libtool: link: gcc -shared  -fPIC -DPIC  .libs/db-alias.o .libs/db-ethers.o 
.libs/db-netgrp.o .libs/db-grp.o .libs/db-proto.o .libs/db-pwd.o .libs/db-rpc.o 
.libs/db-service.o .libs/db-spwd.o .libs/db-compat.o .libs/db-open.o   
-lnss_files -ldb  -g -O2 -fstack-protector-strong 
-Wl,--version-script=../../src/libnss_db.map -Wl,-z -Wl,relro   -Wl,-soname 
-Wl,libnss_db.so.2 -o .libs/libnss_db.so.2.0.0
/usr/bin/ld: cannot find -lnss_files: No such file or directory
collect2: error: ld returned 1 exit status
make[4]: *** [Makefile:516: libnss_db.la] Error 1
make[4]: Leaving directory '/<>/build/src'


Cheers
-- 
Sebastian Ramacher
--- End Message ---
--- Begin Message ---
Source: libnss-db
Source-Version: 2.2.3pre1-7
Done: Aurelien Jarno 

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

Debian distribution maintenance software
pp.
Aurelien Jarno  (supplier of updated libnss-db 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: Mon, 08 Aug 2022 12:40:08 +0200
Source: libnss-db
Architecture: source
Version: 2.2.3pre1-7
Distribution: unstable
Urgency: medium
Maintainer: Debian QA Group 
Changed-By: Aurelien Jarno 
Closes: 1016820
Changes:
 libnss-db (2.2.3pre1-7) unstable; urgency=medium
 .
   * QA upload.
   * debian/patches/400-nss-files.patch: stop linking against libnss_files.
 Closes: #1016820.
   * debian/control: build-depends on libc-dev-bin (>= 2.34)
Checksums-Sha1:
 f1c6caf78eec0fe49d38a2cefb317208fc4e73ff 2018 libnss-db_2.2.3pre1-7.dsc
 0353e786e0c0f17c573a47beb9acfe5c6e5e2cbc 15228 
libnss-db_2.2.3pre1-7.debian.tar.xz
 618957472c37bc3bbef7b9c2e4f8d4c2fe9dee21 6001 
libnss-db_2.2.3pre1-7_source.buildinfo
Checksums-Sha256:
 26f23bb41bf8ec9ff154fcd6337d9bba43f09a194d675a213033215d24629883 2018 
libnss-db_2.2.3pre1-7.dsc
 919fb17d8e9a0fd05f6f4a21c5cab740aad721fc61e371096735f29c47fdc7ad 15228 
libnss-db_2.2.3pre1-7.debian.tar.xz
 fb8be57ef0d3c7110dbf0c0d73c43d694b5ed9ee74b92568a04dfca1057b85b3 6001 
libnss-db_2.2.3pre1-7_source.buildinfo
Files:
 c3378352432bf12de8c6da6341cbb6af 2018 admin standard libnss-db_2.2.3pre1-7.dsc
 e0d751ff205123c45cb0c7d0c132f047 15228 admin standard 
libnss-db_2.2.3pre1-7.debian.tar.xz
 26ef31eaf9e1bcbc5f1f9baaf0f1a3d6 6001 admin standard 
libnss-db_2.2.3pre1-7_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEUryGlb40+QrX1Ay4E4jA+JnoM2sFAmLw6CcACgkQE4jA+Jno
M2vyqQ/+KZZ5MWuHCsLcNWzvnssJ37KXgfb+floRZdmcd+k2Jttgocgl2XCKDaup
Y9yv+hzwJp0KadpnrAUmnx5PLhy9oITdBVw4Y108NTp5F9C1ggsvrdzSCXOr0OvM
3GeUOPYdadTnhYQrp1b2iUjP+dvnvWziwrqZmXSbTshAfmX1QtrexJWO+kuN7jhQ
VXZXRtSC5oxpduOLRrLZby5eFkHpibD1SuJ+Kw8au6o7arUoMp0GEeSpAG8S/Mit
YRlQ6FUXMibVUjrDzA/U2C5lb2fmptN9C8GUUYS6zF5wk6TOYzpDr53AOgrAwn3R
JcibMm29gBGKWlrwryWIQ9/SMn+Y6Y0pOxgjGMGXlpHkJAI2CtXi/Wj+9Qigh6U5
AiKEgqhBIFOE6dCkUIdezwUzxqql0KL9+KMxLXWs8TcUPUec3S4eqmK63Z00zmaJ
BfA64DaDI5uiPi1jo3kUNHNyYB1RQO6v2CWaYRmXtqzoziaJM7xbabzSFPI6mVjz

Processed: limit source to xprobe, tagging 1016241

[Debian Bug Tracking System]

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

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

> tags 1016241 + pending
Bug #1016241 [src:xprobe] xprobe: FTBFS: tcp.cc:31:15: error: ‘time’ was not 
declared in this scope
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#1016838: ycmd.tests.go.subcommands_test.SubcommandsTest fails with gopls/1:0.1.12+ds-1

[Shengjing Zhu]

Source: ycmd
Version: 0+20220401+gitdbe806f+ds-2
Severity: serious
X-Debbugs-Cc: z...@debian.org


Go 1.19 changes the code format, so the test fails now.
Please exclude this test, as it prevents gopls migrating to testing.

Log:

==
FAIL: test_Subcommands_Format_WholeFile 
(ycmd.tests.go.subcommands_test.SubcommandsTest)
--
Traceback (most recent call last):
  File "/tmp/autopkgtest.nAXNu0/build.RqO/src/ycmd/tests/go/__init__.py", line 
59, in Wrapper
return test( test_case_instance, shared_app, *args, **kwargs )
  File 
"/tmp/autopkgtest.nAXNu0/build.RqO/src/ycmd/tests/go/subcommands_test.py", line 
213, in test_Subcommands_Format_WholeFile
RunTest( app, {
  File 
"/tmp/autopkgtest.nAXNu0/build.RqO/src/ycmd/tests/go/subcommands_test.py", line 
86, in RunTest
assert_that( response.json, test[ 'expect' ][ 'data' ] )
AssertionError: 
Expected: a dictionary containing {'fixits': a sequence containing [a 
dictionary containing {'chunks': a sequence containing [a dictionary containing 
{'range': a dictionary containing {'end': a dictionary containing 
{'column_num': <5>, 'filepath': 
'/tmp/autopkgtest.nAXNu0/build.RqO/src/ycmd/tests/go/go_module/goto.go', 
'line_num': <8>}, 'start': a dictionary containing {'column_num': <1>, 
'filepath': 
'/tmp/autopkgtest.nAXNu0/build.RqO/src/ycmd/tests/go/go_module/goto.go', 
'line_num': <8>}}, 'replacement_text': ''}, a dictionary containing {'range': a 
dictionary containing {'end': a dictionary containing {'column_num': <5>, 
'filepath': 
'/tmp/autopkgtest.nAXNu0/build.RqO/src/ycmd/tests/go/go_module/goto.go', 
'line_num': <8>}, 'start': a dictionary containing {'column_num': <5>, 
'filepath': 
'/tmp/autopkgtest.nAXNu0/build.RqO/src/ycmd/tests/go/go_module/goto.go', 
'line_num': <8>}}, 'replacement_text': '\t'}, a dictionary containing {'range': 
a dictionary containing {'end': a dictionary containing {'column_num': <5>, 
'filepath': 
'/tmp/autopkgtest.nAXNu0/build.RqO/src/ycmd/tests/go/go_module/goto.go', 
'line_num': <12>}, 'start': a dictionary containing {'column_num': <1>, 
'filepath': 
'/tmp/autopkgtest.nAXNu0/build.RqO/src/ycmd/tests/go/go_module/goto.go', 
'line_num': <12>}}, 'replacement_text': ''}, a dictionary containing {'range': 
a dictionary containing {'end': a dictionary containing {'column_num': <5>, 
'filepath': 
'/tmp/autopkgtest.nAXNu0/build.RqO/src/ycmd/tests/go/go_module/goto.go', 
'line_num': <12>}, 'start': a dictionary containing {'column_num': <5>, 
'filepath': 
'/tmp/autopkgtest.nAXNu0/build.RqO/src/ycmd/tests/go/go_module/goto.go', 
'line_num': <12>}}, 'replacement_text': '\t'}]}]}
 but: value for 'fixits' item 0: value for 'chunks' item 0: value for 
'replacement_text' was '\t'

Bug#993515: marked as done (catch: FTBFS with glibc 2.34)

[Debian Bug Tracking System]

Your message dated Mon, 08 Aug 2022 10:03:56 +
with message-id 
and subject line Bug#993515: fixed in catch 1.12.2-0.1
has caused the Debian Bug report #993515,
regarding catch: FTBFS with glibc 2.34
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.)


-- 
993515: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=993515
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: catch
Version: 1.12.1-1.1
Severity: important

Hi Maintainer

Catch will FTBFS once glibc is upgraded to 2.34 due to MINSIGSTKSZ and
SIGSTKSZ no longer being defined.

This was fixed Catch2's upstream [1].  I'm not sure if this can be
adapted for Catch(1).
Another approach is to simply replace SIGSTKSZ with a constant, as
done in Fedora [2].

Regards
Graham


[1] https://github.com/catchorg/Catch2/issues/2178
[2] 
https://src.fedoraproject.org/rpms/catch1/c/059104ba87494c0b5ebe16844ec190f253e51cac
--- End Message ---
--- Begin Message ---
Source: catch
Source-Version: 1.12.2-0.1
Done: Timo Röhling 

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

Debian distribution maintenance software
pp.
Timo Röhling  (supplier of updated catch 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: Mon, 08 Aug 2022 10:38:49 +0200
Source: catch
Architecture: source
Version: 1.12.2-0.1
Distribution: unstable
Urgency: medium
Maintainer: Jérémy Lal 
Changed-By: Timo Röhling 
Closes: 993515
Changes:
 catch (1.12.2-0.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
 .
   [ Jérémy Lal ]
   * New upstream version 1.12.2
   * Fix Python 3 build
 .
   [ Ondřej Nový ]
   * d/copyright: Use https protocol in Format field
   * d/changelog: Remove trailing whitespaces
 .
   [ Timo Röhling ]
   * Work around missing SIGSTKSZ with glib 2.34 (Closes: #993515)
 Thanks to Drew Parsons for the patch.
   * Bump Standards-Version to 4.6.1
Checksums-Sha1:
 7a62b4f5b273f325074b2ee55a78a329c70aa320 1696 catch_1.12.2-0.1.dsc
 742d0f5c5607037112a655c28853639263ad770d 377265 catch_1.12.2.orig.tar.gz
 ee147be5f55e5a4d2dc75c0ac4e0d59b3db0d03f 4404 catch_1.12.2-0.1.debian.tar.xz
Checksums-Sha256:
 8d4791ba445a08fe57486f1e54352e907ec35ce0c5a0dd5e98092633f0902747 1696 
catch_1.12.2-0.1.dsc
 27bf01d20692e534a8963f96c6ca797df2b4ba6551db0379510c376558d75e3c 377265 
catch_1.12.2.orig.tar.gz
 bd745ef6bdc0a8a63fcf293ffca0c9ef4ec07add0fe10fa696a839b0872c8854 4404 
catch_1.12.2-0.1.debian.tar.xz
Files:
 737c4bfbe71bbe96a88840bdd06d9597 1696 devel optional catch_1.12.2-0.1.dsc
 3df9c4c56d76c61d82a3bda395fbd492 377265 devel optional catch_1.12.2.orig.tar.gz
 afd27fc22d2ebcd1f79fff358136c987 4404 devel optional 
catch_1.12.2-0.1.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQHIBAEBCgAyFiEEJvtDgpxjkjCIVtam+C8H+466LVkFAmLw3asUHHJvZWhsaW5n
QGRlYmlhbi5vcmcACgkQ+C8H+466LVmjWQwAktFZaTCwvVImd7bGj1r3cNAARek+
glCqF8IxIoCbjcjXTANRxDt/18MG1E8XxmZF5RZkkGSy2IVGwztGuvGgjZooE4Qw
A9uLeOnSn8rtW+rbjt+UR4muzpWSw/uOuIOpGIxpT3J1VKWHwBXn6IAAWizUX+5x
GR/lPSfC4gI9UeWqZcvKxfMbEBmkDFPvYaCAT4pDDgXs/Ll1eNTqj6e5Lfmj2pMP
mErhPQdlnGfIYSWxtc203i6cS7a+E+pqsD5FNQxWK5hiK+sWjYxIyZCBnvSxWR1n
jdcZSX9J4JcPiftBLBz+QrLvhv9ReMAEC0CHz0J4F7SRMssdIJ4foNplx2tXmgZT
v2B4IwY2uA53ZzuE+YS2GfNoK4o7+pTL3jJWceR+U56t7Z6ySYCpg3b5F9KDvxum
TGP0TzfwXHYIvxlEP5TluO0pDTNG/V2gfnq8ZD9bVuXg68GdeX8hpQW2X6+BQl3h
JjEpQ3nUceOPcenAIFRSTmNGEOXqH4NObSJ7
=llBB
-END PGP SIGNATURE End Message ---

Bug#993515: catch: FTBFS with glibc 2.34 - are Tags: fixed-upstream, patch correct and if yes any chance to upload this soon?

[Timo Röhling]

Hi Andreas,

On Mon, 25 Jul 2022 11:34:49 +0200 Andreas Tille  wrote:

set since a long time but there is no actual upload.  I intend to fix
bug #1013269 by making terraphast depend from catch but I would prefer
if this bug would have been fixed first.

I have prepared an NMU and will upload it shortly.


Cheers
Timo

--
⢀⣴⠾⠻⢶⣦⠀   ╭╮
⣾⠁⢠⠒⠀⣿⡁   │ Timo Röhling   │
⢿⡄⠘⠷⠚⠋⠀   │ 9B03 EBB9 8300 DF97 C2B1  23BF CC8C 6BDD 1403 F4CA │
⠈⠳⣄   ╰╯


signature.asc
Description: PGP signature

Bug#1016258: marked as done (binutils-m68hc1x: FTBFS: stdlib.h:134:10: error: argument 1 is null but the corresponding size argument 3 value is [128, 9223372036854775807] [-Werror=nonnull])

[Debian Bug Tracking System]

Your message dated Mon, 08 Aug 2022 08:34:36 +
with message-id 
and subject line Bug#1016258: fixed in binutils-m68hc1x 1:3.1
has caused the Debian Bug report #1016258,
regarding binutils-m68hc1x: FTBFS: stdlib.h:134:10: error: argument 1 is null 
but the corresponding size argument 3 value is [128, 9223372036854775807] 
[-Werror=nonnull]
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.)


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

Hi,

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


Relevant part (hopefully):
> gcc -DHAVE_CONFIG_H -I. -I../../src/gas  -I. -I../../src/gas -I../bfd 
> -I../../src/gas/config -I../../src/gas/../include -I../../src/gas/.. 
> -I../../src/gas/../bfd -DLOCALEDIR="\"/usr/share/locale\"" -Wdate-time 
> -D_FORTIFY_SOURCE=2 -W -Wall -Wstrict-prototypes -Wmissing-prototypes 
> -Wshadow -Wstack-usage=262144 -Werror -Wwrite-strings  -g -O2 
> -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat 
> -Werror=format-security -c -o config/tc-m68hc11.o 
> ../../src/gas/config/tc-m68hc11.c
> GNU/Linux ld.so
> checking how to hardcode library paths into programs... immediate
> checking whether stripping libraries is possible... yes
> checking if libtool supports shared libraries... yes
> checking whether to build shared libraries... no
> checking whether to build static libraries... yes
> checking for special C compiler options needed for large files... no
> checking for _FILE_OFFSET_BITS value needed for large files... gcc 
> -DHAVE_CONFIG_H -I. -I../../src/gas  -I. -I../../src/gas -I../bfd 
> -I../../src/gas/config -I../../src/gas/../include -I../../src/gas/.. 
> -I../../src/gas/../bfd -DLOCALEDIR="\"/usr/share/locale\"" -Wdate-time 
> -D_FORTIFY_SOURCE=2 -W -Wall -Wstrict-prototypes -Wmissing-prototypes 
> -Wshadow -Wstack-usage=262144 -Werror -Wwrite-strings  -g -O2 
> -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat 
> -Werror=format-security -c -o config/obj-elf.o 
> ../../src/gas/config/obj-elf.c
> no
> checking for aclocal... ${SHELL} '/<>/src/missing' aclocal-1.16
> checking for autoconf... ${SHELL} '/<>/src/missing' autoconf
> checking for autoheader... ${SHELL} '/<>/src/missing' autoheader
> checking whether gcc supports -W... yes
> checking whether gcc supports -Wall... gcc -DHAVE_CONFIG_H -I. 
> -I../../src/gas  -I. -I../../src/gas -I../bfd -I../../src/gas/config 
> -I../../src/gas/../include -I../../src/gas/.. -I../../src/gas/../bfd 
> -DLOCALEDIR="\"/usr/share/locale\"" -Wdate-time -D_FORTIFY_SOURCE=2 -W -Wall 
> -Wstrict-prototypes -Wmissing-prototypes -Wshadow -Wstack-usage=262144 
> -Werror -Wwrite-strings  -g -O2 -ffile-prefix-map=/<>=. 
> -fstack-protector-strong -Wformat -Werror=format-security -c -o 
> config/atof-ieee.o ../../src/gas/config/atof-ieee.c
> yes
> checking whether gcc supports -Wnarrowing... yes
> checking whether gcc supports -Wwrite-strings... yes
> checking whether gcc supports -Wmissing-format-attribute... yes
> checking whether gcc supports -Wstrict-prototypes... yes
> touch doc/as.1
> checking whether gcc supports -Wmissing-prototypes... perl 
> ../../src/gas/../etc/texi2pod.pl -I "../../src/gas/doc" -I doc -I 
> "../../src/gas/../libiberty" -I "../../src/gas/../bfd/doc" -I ../bfd/doc 
> --no-split -Dman < ../../src/gas/doc/as.texi > doc/as.pod
> yes
> checking whether gcc supports -Wold-style-definition... yes
> checking whether gcc supports -pedantic -Wlong-long... (pod2man --center="GNU 
> Development Tools" --release="binutils-2.38.90" --section=1 doc/as.pod | \
> sed -e '/^.if n .na/d' > doc/as.1.T$$ && \
> mv -f doc/as.1.T$$ doc/as.1) || \
> (rm -f doc/as.1.T$$ && exit 1)
> restore=: && backupdir=".am$$" && \
> rm -rf $backupdir && mkdir $backupdir && \
> if (makeinfo --split-size=500 --split-size=500 --version) >/dev/null 
> 2>&1; then \
>   for f in doc/as.info doc/as.info-[0-9] doc/as.info-[0-9][0-9] doc/as.i[0-9] 
> doc/as.i[0-9][0-9]; do \
> if test -f $f; then mv $f $backupdir; restore=mv; else :; fi; \
>   done; \
> else :; fi && \
> if makeinfo --split-size=500 --split-size=500 -I "../../src/gas/doc" 
> -I doc -I "../../src/gas/../libiberty" -I "../../src/gas/../bfd/doc" -I 
> ../bfd/doc --no-split  -I doc -I ../../src/gas/doc \
>  -o doc/as.info `test -f 'doc/as.texi' || echo 

Bug#1015128: marked as done (apt: FTBFS: po4a::chooser: Module loading error: Can't locate Syntax/Keyword/Try.pm in @INC)

[Debian Bug Tracking System]

Your message dated Mon, 8 Aug 2022 10:20:37 +0200
with message-id <20220808082037.ngke6cquxtid6cuy@crossbow>
and subject line Re: FTBFS probably already resolved
has caused the Debian Bug report #1015128,
regarding apt: FTBFS: po4a::chooser: Module loading error: Can't locate 
Syntax/Keyword/Try.pm in @INC
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.)


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

Hi,

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


Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> dh_auto_configure -- -DCMAKE_BUILD_RPATH_USE_ORIGIN=ON -DWITH_DOC=ON 
>   cd obj-x86_64-linux-gnu && cmake -DCMAKE_INSTALL_PREFIX=/usr 
> -DCMAKE_BUILD_TYPE=None -DCMAKE_INSTALL_SYSCONFDIR=/etc 
> -DCMAKE_INSTALL_LOCALSTATEDIR=/var -DCMAKE_EXPORT_NO_PACKAGE_REGISTRY=ON 
> -DCMAKE_FIND_USE_PACKAGE_REGISTRY=OFF 
> -DCMAKE_FIND_PACKAGE_NO_PACKAGE_REGISTRY=ON 
> -DFETCHCONTENT_FULLY_DISCONNECTED=ON -DCMAKE_INSTALL_RUNSTATEDIR=/run -GNinja 
> -DCMAKE_VERBOSE_MAKEFILE=ON -DCMAKE_INSTALL_LIBDIR=lib/x86_64-linux-gnu 
> -DCMAKE_BUILD_RPATH_USE_ORIGIN=ON -DWITH_DOC=ON ..
> -- Detected vendor: debian (cached)
> -- Building libapt-pkg 6.0 (release 0)
> -- Found Doxygen: /usr/bin/doxygen (found version "1.9.1") found components: 
> doxygen dot 
> -- Could NOT find GTest (missing: GTEST_LIBRARY GTEST_MAIN_LIBRARY) 
> -- Found GTest at /usr/src/googletest/googletest, headers at 
> /usr/src/googletest/googletest/include
> -- Configuring done
> -- Generating done
> -- Build files have been written to: /<>/obj-x86_64-linux-gnu
> make[1]: Leaving directory '/<>'
>dh_auto_build -O--buildsystem=cmake\+ninja
>   cd obj-x86_64-linux-gnu && LC_ALL=C.UTF-8 ninja -j8 -v
> [1/1085] cd /<>/obj-x86_64-linux-gnu/apt-pkg && echo "APTPKG_6.0 
> {global: *; };" > 
> /<>/obj-x86_64-linux-gnu/apt-pkg/apt-pkg.versionscript
> [2/1085] cd /<>/obj-x86_64-linux-gnu/apt-private && echo 
> "APTPRIVATE_0.0 {global: *; };" > 
> /<>/obj-x86_64-linux-gnu/apt-private/apt-private.versionscript
> [3/1085] cd /<>/obj-x86_64-linux-gnu/cmdline && /usr/bin/cmake 
> -E create_symlink ../solvers/dump 
> /<>/obj-x86_64-linux-gnu/cmdline/planners/dump
> [4/1085] cd /<>/obj-x86_64-linux-gnu/vendor && /usr/bin/cmake 
> -DPROJECT_SOURCE_DIR=/<> 
> "-DVARS=sourceslist-list-format;debian-stable-codename;debian-oldstable-codename;debian-testing-codename;ubuntu-codename;current-codename"
>  -DCURRENT_VENDOR=debian -DIN=/<>/vendor/debian/sources.list.in 
> -DOUT=/<>/obj-x86_64-linux-gnu/vendor/sources.list -P 
> /<>/CMake/vendor_substitute.cmake && chmod 644 
> /<>/obj-x86_64-linux-gnu/vendor/sources.list
> [5/1085] cd /<>/obj-x86_64-linux-gnu/cmdline && /usr/bin/cmake 
> -DPROJECT_SOURCE_DIR=/<> 
> "-DVARS=keyring-filename;keyring-removed-filename;keyring-master-filename;keyring-uri;keyring-package"
>  -DCURRENT_VENDOR=debian -DIN=/<>/cmdline/apt-key.in 
> -DOUT=/<>/obj-x86_64-linux-gnu/cmdline/apt-key -P 
> /<>/CMake/vendor_substitute.cmake && chmod 755 
> /<>/obj-x86_64-linux-gnu/cmdline/apt-key
> [6/1085] cd /<>/obj-x86_64-linux-gnu/doc && 
> /<>/CMake/run_if_exists.sh /<>/doc/guide.dbk 
> xsltproc --nonet --xinclude --stringparam chunk.quietly yes --stringparam 
> man.output.quietly yes --path /<>/vendor/debian/ --path 
> /<>/doc/ --stringparam base.dir 
> /<>/obj-x86_64-linux-gnu/doc/guide.text -o 
> /<>/obj-x86_64-linux-gnu/doc/guide.text.html 
> /<>/obj-x86_64-linux-gnu/doc/docbook-text-style.xsl 
> /<>/doc/guide.dbk && /usr/bin/cmake -E touch 
> /<>/obj-x86_64-linux-gnu/doc/guide.text.html.xsltproc-stamp
> [7/1085] cd /<>/obj-x86_64-linux-gnu/doc && 
> /<>/CMake/run_if_exists.sh /<>/doc/offline.dbk 
> xsltproc --nonet --xinclude --stringparam chunk.quietly yes --stringparam 
> man.output.quietly yes --path /<>/vendor/debian/ --path 
> /<>/doc/ --stringparam base.dir 
> /<>/obj-x86_64-linux-gnu/doc/offline.html -o 
> /<>/obj-x86_64-linux-gnu/doc/offline.html 
> /<>/obj-x86_64-linux-gnu/doc/docbook-html-style.xsl 
> /<>/doc/offline.dbk && /usr/bin/cmake -E touch 
> /<>/obj-x86_64-linux-gnu/doc/offline.html.xsltproc-stamp
> [8/1085] cd /<>/obj-x86_64-linux-gnu/doc && 
> /<>/CMake/run_if_exists.sh /<>/doc/guide.dbk 
> xsltproc --nonet --xinclude --stringparam chunk.quietly yes --stringparam 
> man.output.quietly yes --path /<>/vendor/debian/ --path 
> /<>/doc/ 

Processed: tagging 1015925

[Debian Bug Tracking System]

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

> tags 1015925 + sid bookworm
Bug #1015925 {Done: Axel Beckert } [libcwidget-dev] 
libcwidget-dev: causes aptitude FTBFS due to missing #include 
Added tag(s) bookworm and sid.
> thanks
Stopping processing here.

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

Bug#1016831: libminc: FTBFS on mipsel, mips64el

[Sebastian Ramacher]

Source: libminc
Version: 2.4.03-5
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)
X-Debbugs-Cc: sramac...@debian.org


1: Test command: 
/<>/obj-mips64el-linux-gnuabi64/ezminc/tests/ezminc_rw_test 
"/<>/obj-mips64el-linux-gnuabi64/ezminc/tests"
1: Working Directory: /<>/obj-mips64el-linux-gnuabi64/ezminc/tests
1: Test timeout computed to be: 1500
 1/52 Test  #1: ezminc_rw_test ...   Passed0.09 sec
test 2
  Start  2: minc_types-1

2: Test command: /<>/testdir/run_test_cmake.sh 
"/<>/obj-mips64el-linux-gnuabi64/testdir/minc_types" 
"/<>/testdir/minc_types.out"
2: Working Directory: /<>/obj-mips64el-linux-gnuabi64/testdir
2: Test timeout computed to be: 1500
2: 364c364
2: image[1] = 0
2: 373c373
2: image[1] = -128
2: 382c382
2: image[1] = 0
2: 391c391
2: image[1] = -32768
2: 400c400
2: image[1] = 0
2: 409c409
2: image[1] = -2.14748e+09
2: 418c418
2: image[1] = -2.14748e+09
2: 427c427
2: image[1] = -2.14748e+09
2: 481c481
2: image[1] = -2.14748e+09
2: 553c553
2: image[1] = -2.14748e+09
 2/52 Test  #2: minc_types-1 .***Failed0.09 sec
364c364
image[1] = 0
373c373
image[1] = -128
382c382
image[1] = 0
391c391
image[1] = -32768
400c400
image[1] = 0
409c409
image[1] = -2.14748e+09
418c418
image[1] = -2.14748e+09
427c427
image[1] = -2.14748e+09
481c481
image[1] = -2.14748e+09
553c553
image[1] = -2.14748e+09

test 3
  Start  3: minc_types-2

3: Test command: /<>/testdir/run_test2_cmake.sh 
"/<>/obj-mips64el-linux-gnuabi64/testdir/minc_types" 
"/<>/testdir/minc_types.out"
3: Working Directory: /<>/obj-mips64el-linux-gnuabi64/testdir
3: Test timeout computed to be: 1500
3: 364c364
3: image[1] = 0
3: 373c373
3: image[1] = -128
3: 382c382
3: image[1] = 0
3: 391c391
3: image[1] = -32768
3: 400c400
3: image[1] = 0
3: 409c409
3: image[1] = -2.14748e+09
3: 418c418
3: image[1] = -2.14748e+09
3: 427c427
3: image[1] = -2.14748e+09
3: 481c481
3: image[1] = -2.14748e+09
3: 553c553
3: image[1] = -2.14748e+09
 3/52 Test  #3: minc_types-2 .***Failed0.27 sec
364c364
image[1] = 0
373c373
image[1] = -128
382c382
image[1] = 0
391c391
image[1] = -32768
400c400
image[1] = 0
409c409
image[1] = -2.14748e+09
418c418
image[1] = -2.14748e+09
427c427
image[1] = -2.14748e+09
481c481
image[1] = -2.14748e+09
553c553
image[1] = -2.14748e+09

...

96% tests passed, 2 tests failed out of 52

Total Test time (real) = 126.06 sec

The following tests FAILED:
  2 - minc_types-1 (Failed)
  3 - minc_types-2 (Failed)
Errors while running CTest
make[2]: *** [Makefile:94: test] Error 8

https://buildd.debian.org/status/fetch.php?pkg=libminc=mips64el=2.4.03-5%2Bb1=1659928672=0

Cheers
-- 
Sebastian Ramacher

Bug#1016830: insighttoolkit5: FTBFS on amd64

[Sebastian Ramacher]

Source: insighttoolkit5
Version: 5.2.1-5
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)
X-Debbugs-Cc: sramac...@debian.org

https://buildd.debian.org/status/fetch.php?pkg=insighttoolkit5=amd64=5.2.1-5%2Bb2=1659928626=0


ITKPolynomials =   0.03 sec*proc

ITKQuadEdgeMesh =   1.34 sec*proc

ITKQuadEdgeMeshFiltering =  26.18 sec*proc

ITKRegionGrowing =   0.53 sec*proc

ITKRegistrationCommon =  87.72 sec*proc

ITKRegistrationMethodsv4 =  70.63 sec*proc

ITKReview =  48.79 sec*proc

ITKSignedDistanceFunction =   0.08 sec*proc

ITKSmoothing =   1.09 sec*proc

ITKSpatialFunction =   0.04 sec*proc

ITKSpatialObjects =   1.25 sec*proc

ITKStatistics =   7.16 sec*proc

ITKSuperPixel =   1.24 sec*proc

ITKTestKernel =   0.17 sec*proc

ITKThresholding =   4.59 sec*proc

ITKTransform =  20.72 sec*proc

ITKTransformFactory =   0.10 sec*proc

ITKVideoCore =   0.30 sec*proc

ITKVideoFiltering =   0.40 sec*proc

ITKVideoIO =   0.33 sec*proc

ITKVoronoi =   0.57 sec*proc

ITKWatersheds =   2.08 sec*proc

RUNS_LONG = 517.95 sec*proc

Test log end =:
make[1]: *** [debian/rules:93: override_dh_auto_test] Error 1
make[1]: Leaving directory '/<>'
make: *** [debian/rules:77: binary-arch] Error 2
dpkg-buildpackage: error: debian/rules binary-arch subprocess returned exit 
status 2


Cheers
-- 
Sebastian Ramacher

Bug#1016829: cross-toolchain-base: autopkgtest hardcodes glibc version which is transitioning now

[Paul Gevers]

Source: cross-toolchain-base
Version: 59
Severity: serious

Dear all,

The glibc 2.34 transition started yesterday. However, the autopkgtest
of cross-toolchain-base fails because it hardcodes:
glibc-source (>= 2.33-1~), glibc-source (<< 2.34)
which isn't available anymore.

Please adapt your test for the new (and ideally future) glibc.

Paul