Processed: tagging 995600

[Debian Bug Tracking System]

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

> tags 995600 + pending
Bug #995600 [src:omega-rpg] FTBFS: error: format not a string literal and no 
format arguments
Added tag(s) pending.
> thanks
Stopping processing here.

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

Processed: tagging 995480

[Debian Bug Tracking System]

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

> tags 995480 + pending
Bug #995480 [src:ytree] FTBFS: error: format not a string literal and no format 
arguments
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#998156: contains non-DFSG-free files

[Ryan Kavanagh]

Package: mlton
Version: 20100608-5.1
Severity: serious
Tags: upstream
X-Debbugs-Cc: r...@debian.org

Since at least oldoldoldstable, the mlton sources have included non-free files.
In particular, the tarball lib/ckit-lib/ckit.tgz contains the files
ckit/src/parser/util/error.sml and ckit/src/parser/util/error-sig.sml.  These
files are:

(*
 * Copyright (c) 1996 by Satish Chandra, Brad Richards, Mark D. Hill,
 * James R. Larus, and David A. Wood.
 *
 * Teapot is distributed under the following conditions:
 *
 * You may make copies of Teapot for your own use and modify those copies.
 *
 * All copies of Teapot must retain our names and copyright notice.
 *
 * You may not sell Teapot or distributed Teapot in conjunction with a
 * commercial product or service without the expressed written consent of
 * the copyright holders.
 *
 * THIS SOFTWARE IS PROVIDED ``AS IS'' AND WITHOUT ANY EXPRESS OR IMPLIED
 * WARRANTIES, INCLUDING, WITHOUT LIMITATION, THE IMPLIED WARRANTIES OF
 * MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE.
 *
 *)

The restriction on distribution in conjunction with a commercial product
or service is in violation of point 6 of the DFSG.

See also the related bug against SML/NJ:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=998154

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

Kernel: Linux 5.14.0-1-amd64 (SMP w/4 CPU threads)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
Locale: LANG=en_CA.UTF-8, LC_CTYPE=en_CA.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 mlton depends on:
ii  mlton-compiler  20130715-3
ii  mlton-doc   20130715-3
ii  mlton-tools 20130715-3

mlton recommends no packages.

mlton suggests no packages.

-- no debconf information

-- 
|)|/  Ryan Kavanagh  | 4E46 9519 ED67 7734 268F
|\|\  https://rak.ac | BD95 8F7B F8FC 4A11 C97A


signature.asc
Description: PGP signature

Bug#998154: contains non-DSFG-free files

[Ryan Kavanagh]

Package: smlnj
Version: 110.76-2
Severity: serious
Tags: upstream

Since at least oldoldoldstable, the SML/NJ sources have included
non-free files. In 110.76-2, these non-free files include at least
ckit.tgz, which contains the files ckit/src/parser/util/error.sml and
ckit/src/parser/util/error.sml and ckit/src/parser/util/error-sig.sml.
These files are:

(*
 * Copyright (c) 1996 by Satish Chandra, Brad Richards, Mark D. Hill,
 * James R. Larus, and David A. Wood.
 *
 * Teapot is distributed under the following conditions:
 *
 * You may make copies of Teapot for your own use and modify those copies.
 *
 * All copies of Teapot must retain our names and copyright notice.
 *
 * You may not sell Teapot or distributed Teapot in conjunction with a
 * commercial product or service without the expressed written consent of
 * the copyright holders.
 *
 * THIS SOFTWARE IS PROVIDED ``AS IS'' AND WITHOUT ANY EXPRESS OR IMPLIED
 * WARRANTIES, INCLUDING, WITHOUT LIMITATION, THE IMPLIED WARRANTIES OF
 * MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE.
 *
 *)

In the sources for 110.79-6 (unstable), they can be found in extracted
form at the same location

The restriction on distribution in conjunction with a commercial product
or service is in violation of point 6 of the DFSG.

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

Kernel: Linux 5.14.0-1-amd64 (SMP w/4 CPU threads)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
Locale: LANG=en_CA.UTF-8, LC_CTYPE=en_CA.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 smlnj depends on:
ii  smlnj-runtime  110.79-6

Versions of packages smlnj recommends:
ii  libsmlnj-smlnj  110.79-6

Versions of packages smlnj suggests:
pn  smlnj-doc  

-- no debconf information

-- 
|)|/  Ryan Kavanagh  | 4E46 9519 ED67 7734 268F
|\|\  https://rak.ac | BD95 8F7B F8FC 4A11 C97A


signature.asc
Description: PGP signature

Bug#997820: marked as done (python3-trezor: Depends: python3-click (< 8) but 8.0.2-1 is to be installed)

[Debian Bug Tracking System]

Your message dated Sun, 31 Oct 2021 02:35:53 +
with message-id 
and subject line Bug#997820: fixed in python-trezor 0.12.4-1
has caused the Debian Bug report #997820,
regarding python3-trezor: Depends: python3-click (< 8) but 8.0.2-1 is to be 
installed
to be marked as done.

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

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


-- 
997820: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997820
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: python3-trezor
Version: 0.12.2-2
Severity: serious
Tags: bookworm sid

The following packages have unmet dependencies:
 python3-trezor : Depends: python3-click (< 8) but 8.0.2-1 is to be installed
--- End Message ---
--- Begin Message ---
Source: python-trezor
Source-Version: 0.12.4-1
Done: Sandro Tosi 

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

Debian distribution maintenance software
pp.
Sandro Tosi  (supplier of updated python-trezor package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sat, 30 Oct 2021 21:39:20 -0400
Source: python-trezor
Architecture: source
Version: 0.12.4-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Team 
Changed-By: Sandro Tosi 
Closes: 997820
Changes:
 python-trezor (0.12.4-1) unstable; urgency=medium
 .
   [ Ondřej Nový ]
   * d/control: Update Maintainer field with new Debian Python Team
 contact address.
   * d/control: Update Vcs-* fields with new Debian Python Team Salsa
 layout.
 .
   [ Sandro Tosi ]
   * New upstream release; Closes: #997820
   * debian/copyright
 - update for new upstream code
Checksums-Sha1:
 69041a932c7ab5411dd71f6f4e5265dae512ed9f 2419 python-trezor_0.12.4-1.dsc
 c38ccfbc9a984be68d0e92c63c30c4d06b7eb607 119984 
python-trezor_0.12.4.orig.tar.xz
 c68398e307084ef621eb1e70ffe7d4f0c7f80944 5356 
python-trezor_0.12.4-1.debian.tar.xz
 e53e51740059e588a21ab381aa6fb891748d0faf 8845 
python-trezor_0.12.4-1_source.buildinfo
Checksums-Sha256:
 f4c812c9b2da569392b4478f3727b8344b32440e064200596e018873d6063604 2419 
python-trezor_0.12.4-1.dsc
 0f3e41b832a4c24895176529c450d768f76a83290819c2cb8f4db97ea2c7d5f0 119984 
python-trezor_0.12.4.orig.tar.xz
 2942e5bb380d6f3320291bf5fcb2a6f2658fc340b756bb11bd29ebb2bc36b55f 5356 
python-trezor_0.12.4-1.debian.tar.xz
 2a9a7eb56c6d34e73c4a4f07a3ffdf392eab6fbe336656ac5babb5888bbd1a5a 8845 
python-trezor_0.12.4-1_source.buildinfo
Files:
 cb247c49aaf83ee836e8dc3409ffca22 2419 python optional 
python-trezor_0.12.4-1.dsc
 ff98a9408ea726ef64b6db82bebaeede 119984 python optional 
python-trezor_0.12.4.orig.tar.xz
 7db2e7846ffd4119e191b2f6b57e51a8 5356 python optional 
python-trezor_0.12.4-1.debian.tar.xz
 6fd6790cf132780c3ddb057c9f188941 8845 python optional 
python-trezor_0.12.4-1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEufrTGSrz5KUwnZ05h588mTgBqU8FAmF98/IACgkQh588mTgB
qU8SAQ/9Fxc6JnYi29RIUP6ZxyOXQnv+04rOwhtpczxNzArPS9e0KEguNtoPyiC3
vRUtEEXWTuYhtO8nZ7KOIy8Y1a9slMybC2+PZKWdlVdbDfOtPbkfSyyId2PNd8SS
mF1/OpnznI1QgTASOouiLTWg8ixY6a65FMqkJ+yWRXHad9Cfz0Vr7woDB2+UW+SR
bItM8lO+p494gfZFOiAgwUu8KqB0uA/0qUA7zTQKcw6NRpzu8pycb4FQsSop3ikl
NbN2NKJ6QMZvxzJdjtnLWViyyci1SlBegasBxzEd9uxappaADIo/sgQcxemHcMyR
rmo40WXCbiJUeG9vxgOsKk/SntAxmF8MWkK27g+KrAUsHHbENP7T7uzrztwwEwGZ
+hPRo2ja2JizXgUp988f2mImue6M//OYtQtTkggA0Qqn10I1YWQ2fU+B39B2KfCD
Tn5kC5abZfuYXNhTgnCTttZqiGdmqPCSf3SnOpZqYsZ8M9oVjjZwfLnOuwEG2A0f
99wfwW3RPmJDuTXNpjtL1oxJPmn595muhR1GvsWX8/aLQBLrbEeU62o8g6cR9osE
2Mg2cwyD9gr4v7DKnXUpWHsxNwDtHSlllVRa10ecQ9JPYx3rSviB2iSQHHFPfNwz
H1GITCXAkZYqVF/HmDQzHtEF8ckVGqGNYucT16lMyVOM3sX8ixE=
=8ZuU
-END PGP SIGNATURE End Message ---

Bug#997820: marked as pending in python-trezor

[Sandro Tosi]

Control: tag -1 pending

Hello,

Bug #997820 in python-trezor 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/python-trezor/-/commit/895dc7bcbf3dbcbdf00269811f1d2d105866e145


New upstream release; Closes: #997820


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/997820

Processed: Bug#997820 marked as pending in python-trezor

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #997820 [python3-trezor] python3-trezor: Depends: python3-click (< 8) but 
8.0.2-1 is to be installed
Added tag(s) pending.

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

Bug#997461: marked as done (target-factory: FTBFS: dpkg-gensymbols: error: some symbols or patterns disappeared in the symbols file: see diff output below)

[Debian Bug Tracking System]

Your message dated Sun, 31 Oct 2021 00:19:09 +
with message-id 
and subject line Bug#997461: fixed in target-factory 1.4-2
has caused the Debian Bug report #997461,
regarding target-factory: FTBFS: dpkg-gensymbols: error: some symbols or 
patterns disappeared in the symbols file: see diff output below
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.)


-- 
997461: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997461
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: target-factory
Version: 1.4-1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20211023 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_missing --list-missing
> make[1]: Leaving directory '/<>'
>dh_dwz -a
>   dwz -- 
> debian/libtarget-factory1/usr/lib/x86_64-linux-gnu/libtarget-factory.so.1.4.0
>dh_strip -a
>   install -d 
> debian/.debhelper/libtarget-factory1/dbgsym-root/usr/lib/debug/.build-id/0c
>   objcopy --only-keep-debug --compress-debug-sections 
> debian/libtarget-factory1/usr/lib/x86_64-linux-gnu/libtarget-factory.so.1.4.0 
> debian/.debhelper/libtarget-factory1/dbgsym-root/usr/lib/debug/.build-id/0c/49f2dc11a1596ff4b22e2c310c0b9f83558687.debug
>   chmod 0644 -- 
> debian/.debhelper/libtarget-factory1/dbgsym-root/usr/lib/debug/.build-id/0c/49f2dc11a1596ff4b22e2c310c0b9f83558687.debug
>   strip --remove-section=.comment --remove-section=.note --strip-unneeded 
> debian/libtarget-factory1/usr/lib/x86_64-linux-gnu/libtarget-factory.so.1.4.0
>   objcopy --add-gnu-debuglink 
> debian/.debhelper/libtarget-factory1/dbgsym-root/usr/lib/debug/.build-id/0c/49f2dc11a1596ff4b22e2c310c0b9f83558687.debug
>  debian/libtarget-factory1/usr/lib/x86_64-linux-gnu/libtarget-factory.so.1.4.0
>   install -d 
> debian/.debhelper/libtarget-factory1/dbgsym-root/usr/share/doc
>   ln -s libtarget-factory1 
> debian/.debhelper/libtarget-factory1/dbgsym-root/usr/share/doc/libtarget-factory1-dbgsym
>dh_makeshlibs -a
>   rm -f debian/libtarget-factory1/DEBIAN/shlibs
>   install -d debian/libtarget-factory1/DEBIAN
>   echo "libtarget-factory 1 libtarget-factory1 (>= 1.4)" >> 
> debian/libtarget-factory1/DEBIAN/shlibs
>   chmod 0644 -- debian/libtarget-factory1/DEBIAN/shlibs
>   dpkg-gensymbols -plibtarget-factory1 
> -Idebian/libtarget-factory1.symbols -Pdebian/libtarget-factory1 
> -edebian/libtarget-factory1/usr/lib/x86_64-linux-gnu/libtarget-factory.so.1.4.0
> dpkg-gensymbols: warning: some new symbols appeared in the symbols file: see 
> diff output below
> dpkg-gensymbols: error: some symbols or patterns disappeared in the symbols 
> file: see diff output below
> dpkg-gensymbols: warning: debian/libtarget-factory1/DEBIAN/symbols doesn't 
> match completely debian/libtarget-factory1.symbols
> --- debian/libtarget-factory1.symbols (libtarget-factory1_1.4-1_amd64)
> +++ dpkg-gensymbolsMdT3U4 2021-10-23 06:30:18.671214432 +
> @@ -6,6 +6,27 @@
>   _ZN16ErrorCodeFactoryD1Ev@Base 1.4
>   _ZN16ErrorCodeFactoryD2Ev@Base 1.4
>   _ZN26TableStruct_target_2eproto7offsetsE@Base 1.4
> + _ZN3fLB16FLAGS_log_prefixE@Base 1.4-1
> + _ZN3fLB17FLAGS_logtostderrE@Base 1.4-1
> + _ZN3fLB21FLAGS_alsologtostderrE@Base 1.4-1
> + _ZN3fLB21FLAGS_drop_log_memoryE@Base 1.4-1
> + _ZN3fLB22FLAGS_colorlogtostderrE@Base 1.4-1
> + _ZN3fLB26FLAGS_symbolize_stacktraceE@Base 1.4-1
> + _ZN3fLB31FLAGS_stop_logging_if_full_diskE@Base 1.4-1
> + _ZN3fLI16FLAGS_logbufsecsE@Base 1.4-1
> + _ZN3fLI17FLAGS_logbuflevelE@Base 1.4-1
> + _ZN3fLI17FLAGS_minloglevelE@Base 1.4-1
> + _ZN3fLI18FLAGS_logfile_modeE@Base 1.4-1
> + _ZN3fLI18FLAGS_max_log_sizeE@Base 1.4-1
> + _ZN3fLI19FLAGS_logemaillevelE@Base 1.4-1
> + _ZN3fLI21FLAGS_stderrthresholdE@Base 1.4-1
> + _ZN3fLI7FLAGS_vE@Base 1.4-1
> + _ZN3fLS13FLAGS_log_dirB5cxx11E@Base 1.4-1
> + _ZN3fLS13FLAGS_vmoduleB5cxx11E@Base 1.4-1
> + _ZN3fLS14FLAGS_log_linkB5cxx11E@Base 1.4-1
> + _ZN3fLS15FLAGS_logmailerB5cxx11E@Base 1.4-1
> + _ZN3fLS20FLAGS_alsologtoemailB5cxx11E@Base 1.4-1
> + _ZN3fLS22FLAGS_log_backtrace_atB5cxx11E@Base 1.4-1
>   _ZN5vitis2ai10Target_Alu10SharedCtorEv@Base 1.4
>   _ZN5vitis2ai10Target_Alu10SharedDtorEv@Base 1.4
>   _ZN5vitis2ai10Target_Alu10leaky_reluE@Base 1.4
> @@ -995,9 +1016,140 @@
>   _ZN5vitis2ai6TargetD1Ev@Base 1.4
>   _ZN5vitis2ai6TargetD2Ev@Base 1.4
>   
> _ZN5vitis2ai9to_stringERKSt3mapINSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEEmSt4lessIS7_ESaISt4pairIKS7_mEEE

Bug#984279: marked as done (openzwave: ftbfs with GCC-11)

[Debian Bug Tracking System]

Your message dated Sat, 30 Oct 2021 21:49:42 +
with message-id 
and subject line Bug#984279: fixed in openzwave 1.6.1914+ds-1
has caused the Debian Bug report #984279,
regarding openzwave: ftbfs with GCC-11
to be marked as done.

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

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


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

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

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

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

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

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

  apt-get -t=experimental install g++ 

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

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

[...]
dh_clean
rm -f debian/debhelper-build-stamp
rm -rf debian/.debhelper/
rm -f -- debian/libopenzwave1.6.substvars 
debian/libopenzwave1.6-dev.substvars debian/libopenzwave-doc.substvars 
debian/openzwave.substvars debian/files
rm -fr -- debian/libopenzwave1.6/ debian/tmp/ 
debian/libopenzwave1.6-dev/ debian/libopenzwave-doc/ debian/openzwave/
find .  \( \( \
\( -path .\*/.git -o -path .\*/.svn -o -path .\*/.bzr -o -path 
.\*/.hg -o -path .\*/CVS -o -path .\*/.pc -o -path .\*/_darcs \) -prune -o 
-type f -a \
\( -name '#*#' -o -name '.*~' -o -name '*~' -o -name DEADJOE \
 -o -name '*.orig' -o -name '*.rej' -o -name '*.bak' \
 -o -name '.*.orig' -o -name .*.rej -o -name '.SUMS' \
 -o -name TAGS -o \( -path '*/.deps/*' -a -name '*.P' \) \
\) -exec rm -f {} + \) -o \
\( -type d -a -name autom4te.cache -prune -exec rm -rf {} + \) 
\)
make[1]: Leaving directory '/<>'
 debian/rules binary
dh binary
   dh_update_autotools_config
   dh_autoreconf
   dh_auto_configure
install -d 
/<>/openzwave-1.6.1545\+ds/debian/.debhelper/generated/_source/home
   debian/rules override_dh_auto_build
make[1]: Entering directory '/<>'
echo "Build version: >1.6.1545<"
Build version: >1.6.1545<
LDFLAGS="-Wl,-z,relro -Wl,-z,now" CPPFLAGS="-Wdate-time -D_FORTIFY_SOURCE=2 -g 
-O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security" VERSION_MAJ=1 VERSION_MIN=6 VERSION_REV=1545 
PREFIX=/usr sysconfdir=/etc/openzwave instlibdir=/usr/lib/x86_64-linux-gnu/ make
make[2]: Entering directory '/<>'
make[3]: Entering directory '/<>/cpp/build'
Building OpenZWave Version  - 1.6.1545
Building tinyxml/tinystr.cpp
Building tinyxml/tinyxml.cpp
Building tinyxml/tinyxmlerror.cpp
Building tinyxml/tinyxmlparser.cpp
Building aes/aes_modes.c
Building aes/aescrypt.c
Building aes/aeskey.c
Building aes/aestab.c
Building src/command_classes/Alarm.cpp
Building src/command_classes/ApplicationStatus.cpp
Building src/command_classes/Association.cpp
Building src/command_classes/AssociationCommandConfiguration.cpp
/<>/cpp/src/command_classes/AssociationCommandConfiguration.cpp: 
In member function ‘virtual bool 
OpenZWave::Internal::CC::AssociationCommandConfiguration::HandleMsg(const 
uint8*, uint32, uint32)’:
/<>/cpp/src/command_classes/AssociationCommandConfiguration.cpp:191:85:
 error: ‘this’ pointer is null [-Werror=nonnull]
  191 | 
group

Bug#995123: marked as done (cyrus-sasl2 FTBFS: sphinx: AttributeError: 'CyrusManualPageBuilder' object has no attribute 'settings')

[Debian Bug Tracking System]

Your message dated Sat, 30 Oct 2021 21:33:31 +
with message-id 
and subject line Bug#995123: fixed in cyrus-sasl2 2.1.27+dfsg-2.2
has caused the Debian Bug report #995123,
regarding cyrus-sasl2 FTBFS: sphinx: AttributeError: 'CyrusManualPageBuilder' 
object has no attribute 'settings'
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.)


-- 
995123: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=995123
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: cyrus-sasl2
Version: 2.1.27+dfsg-2.1
Severity: serious
Tags: ftbfs
X-Debbugs-Cc: Dmitry Shachnev 

I'm reporting this bug on behalf of Alexey Brodkin as the original
reporter on irc.

cyrus-sasl2 fails to build from source in unstable on amd64. A build
ends as follows:

| /usr/bin/sphinx-build -d docsrc/.doctrees -n -q -b cyrman ./docsrc ./man
| 
/<>/build-heimdal/docsrc/sasl/reference/manpages/library/sasl_auxprop_add_plugin.rst:22:
 WARNING: Error in declarator or parameters
| Invalid C declaration: Expected identifier in nested name. [error at 49]
|   int sasl_auxprop_add_plugin(const char *plugname,
|   -^
| 
/<>/build-heimdal/docsrc/sasl/reference/manpages/library/sasl_auxprop_add_plugin.rst:22:
 WARNING: Error in declarator or parameters
| Invalid C declaration: Expecting "(" in parameters. [error at 35]
|   sasl_auxprop_plug_init_t *cplugfunc);
|   ---^
| 
/<>/build-heimdal/docsrc/sasl/reference/manpages/library/sasl_canon_user_t.rst:23:
 WARNING: Error in declarator or parameters
| Invalid C declaration: Expected identifier in nested name. [error at 40]
|   int sasl_canon_user_t(sasl_conn_t *conn,
|   ^
| 
/<>/build-heimdal/docsrc/sasl/reference/manpages/library/sasl_canon_user_t.rst:23:
 WARNING: Error in declarator or parameters
| Invalid C declaration: Expecting "(" in parameters. [error at 13]
|   void *context,
|   -^
| 
/<>/build-heimdal/docsrc/sasl/reference/manpages/library/sasl_canon_user_t.rst:23:
 WARNING: Error in declarator or parameters
| Invalid C declaration: Expecting "(" in parameters. [error at 16]
|   const char *user,
|   ^
| 
/<>/build-heimdal/docsrc/sasl/reference/manpages/library/sasl_canon_user_t.rst:23:
 WARNING: Error in declarator or parameters
| Invalid C declaration: Expecting "(" in parameters. [error at 13]
|   unsigned ulen,
|   -^
| 
/<>/build-heimdal/docsrc/sasl/reference/manpages/library/sasl_canon_user_t.rst:23:
 WARNING: Error in declarator or parameters
| Invalid C declaration: Expecting "(" in parameters. [error at 14]
|   unsigned flags,
|   --^
| 
/<>/build-heimdal/docsrc/sasl/reference/manpages/library/sasl_canon_user_t.rst:23:
 WARNING: Error in declarator or parameters
| Invalid C declaration: Expecting "(" in parameters. [error at 22]
|   const char *user_realm,
|   --^
| 
/<>/build-heimdal/docsrc/sasl/reference/manpages/library/sasl_canon_user_t.rst:23:
 WARNING: Error in declarator or parameters
| Invalid C declaration: Expecting "(" in parameters. [error at 14]
|   char *out_user,
|   --^
| 
/<>/build-heimdal/docsrc/sasl/reference/manpages/library/sasl_canon_user_t.rst:23:
 WARNING: Error in declarator or parameters
| Invalid C declaration: Expecting "(" in parameters. [error at 17]
|   unsigned out_umax,
|   -^
| 
/<>/build-heimdal/docsrc/sasl/reference/manpages/library/sasl_canon_user_t.rst:23:
 WARNING: Error in declarator or parameters
| Invalid C declaration: Expecting "(" in parameters. [error at 18]
|   unsigned *out_ulen)
|   --^
| 
/<>/build-heimdal/docsrc/sasl/reference/manpages/library/sasl_canonuser_add_plugin.rst:22:
 WARNING: Error in declarator or parameters
| Invalid C declaration: Expected identifier in nested name. [error at 51]
|   int sasl_canonuser_add_plugin(const char *plugname,
|   ---^
| 
/<>/build-heimdal/docsrc/sasl/reference/manpages/library/sasl_canonuser_add_plugin.rst:22:
 WARNING: Error in declarator or parameters
| Invalid C declaration: Expecting "(" in parameters. [error at 37]
|   sasl_canonuser_plug_init_t *cplugfunc);
|   -^
| 
/<>/build-heimdal/docsrc/sasl/reference/manpages/library/sasl_chalprompt_t.rst:24:
 WARNING: Error in declarator or parameters
| Invalid C declaration: Expected identifier in nested name. [error at 36]
|   int sasl_chalprompt_t(void *context,
|   ^
| 
/<>/build-heimdal/

Bug#997471: marked as done (loguru: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p 3.9 returned exit code 13)

[Debian Bug Tracking System]

Your message dated Sat, 30 Oct 2021 21:06:42 +
with message-id 
and subject line Bug#997471: fixed in loguru 0.5.3-4
has caused the Debian Bug report #997471,
regarding loguru: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i 
python{version} -p 3.9 returned exit code 13
to be marked as done.

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

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


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

Hi,

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


Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> dh_auto_test
>   pybuild --test --test-pytest -i python{version} -p 3.9
> I: pybuild pybuild:285: rm -f tests/test_exceptions_formatting.py
> I: pybuild base:232: cd /<>/.pybuild/cpython3_3.9_loguru/build; 
> python3.9 -m pytest tests
> = test session starts 
> ==
> platform linux -- Python 3.9.7, pytest-6.2.5, py-1.10.0, pluggy-0.13.0
> rootdir: /<>, configfile: tox.ini
> plugins: cov-3.0.0
> collected 1283 items
> 
> tests/test_activation.py ..  [  
> 2%]
> tests/test_add_option_backtrace.py . [  
> 2%]
> tests/test_add_option_catch.py ...   [  
> 3%]
> tests/test_add_option_colorize.py .. [  
> 6%]
>  [  
> 7%]
> tests/test_add_option_diagnose.py .  [  
> 7%]
> tests/test_add_option_enqueue.py ..FF... [  
> 8%]
> tests/test_add_option_filter.py  [ 
> 11%]
> ...  [ 
> 12%]
> tests/test_add_option_format.py  [ 
> 13%]
> tests/test_add_option_kwargs.py ...  [ 
> 14%]
> tests/test_add_option_level.py ..[ 
> 15%]
> tests/test_add_option_serialize.py   [ 
> 15%]
> tests/test_add_sinks.py  [ 
> 19%]
> ..   [ 
> 20%]
> tests/test_ansimarkup_basic.py . [ 
> 23%]
> ...  [ 
> 26%]
> tests/test_ansimarkup_extended.py .. [ 
> 29%]
> ..   [ 
> 34%]
> tests/test_bind.py . [ 
> 34%]
> tests/test_configure.py  [ 
> 36%]
> tests/test_contextualize.py .[ 
> 37%]
> tests/test_coroutine_sink.py ... [ 
> 39%]
> tests/test_datetime.py ..[ 
> 42%]
> tests/test_deepcopy.py   [ 
> 42%]
> tests/test_defaults.py . [ 
> 43%]
> tests/test_exceptions_catch.py . [ 
> 46%]
> ..   [ 
> 47%]
> tests/test_filesink_compression.py . [ 
> 50%]
> .[ 
> 51%]
> tests/test_filesink_delay.py ..  [ 
> 52%]
> tests/test_filesink_retention.py ... [ 
> 55%]
> ..   [ 
> 56%]
> tests/test_filesink_rotation.py  [ 
> 59%]
> ...ss..  [ 
> 63%]
> tests/test_formatting.py ... [ 
> 67%]
>  [ 
> 69%]
> tests/test_get_frame.py ...  [ 
> 70%]
> tests/test_interception.py   [ 
> 71%]
> tests/test_l

Processed: bug 995356 is forwarded to https://github.com/wolever/parameterized/issues/122

[Debian Bug Tracking System]

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

> forwarded 995356 https://github.com/wolever/parameterized/issues/122
Bug #995356 [src:python-parameterized] python-parameterized: autopkgtest 
regression: AssertionError in tearDownModule
Set Bug forwarded-to-address to 
'https://github.com/wolever/parameterized/issues/122'.
> thanks
Stopping processing here.

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

Bug#998143: gatb-core breaks discosnp autopkgtest: Segmentation fault

[Paul Gevers]

Source: gatb-core, discosnp
Control: found -1 gatb-core/1.4.2+dfsg-7
Control: found -1 discosnp/4.4.4-2
Severity: serious
Tags: sid bookworm
X-Debbugs-CC: debian...@lists.debian.org
User: debian...@lists.debian.org
Usertags: breaks needs-update

Dear maintainer(s),

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

   passfail
gatb-core  from testing1.4.2+dfsg-7
discosnp   from testing4.4.4-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 gatb-core 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=gatb-core

https://ci.debian.net/data/autopkgtest/testing/amd64/d/discosnp/16314588/log.gz

tput: No value for $TERM and no -T specified
tput: No value for $TERM and no -T specified
tput: No value for $TERM and no -T specified
tput: No value for $TERM and no -T specified
tput: No value for $TERM and no -T specified
tput: No value for $TERM and no -T specified


 Running discoSnp++ 2.3.X, in directory /usr with following parameters:
 read_sets=fof.txt
 prefix=discoRes_k_31_c_3
 c=3
 C=2147483647
 k=31
 b=0
 d=1
 D=100
 s=
 P=3
 p=discoRes
 G=
 e=
 starting date=Sat Oct 30 11:09:22 UTC 2021


 
  GRAPH CREATION  ###
 
/usr/bin/dbgh5 -in
fof.txt_discoRes_k_31_c_3_D_100_P_3_b_0_removemeplease -out
discoRes_k_31_c_3 -kmer-size 31 -abundance-min 3 -abundance-max
2147483647 -solidity-kind one -verbose 1 -skip-bcalm -skip-bglue -no-mphf

[DSK: counting kmers ]  0%   elapsed:   0 min 0
 sec   remaining:   0 min 0  sec   cpu:  -1.0 %   mem: [  25,   25,
58] MB [DSK: Pass 1/1, Step 1: partitioning ]  0%   elapsed:   0
min 0  sec   remaining:   0 min 0  sec   cpu:  -1.0 %   mem: [  53,
53,   58] MB [DSK: Pass 1/1, Step 2: counting kmers   ]  2.24 %
elapsed:   0 min 2  sec   remaining:   1 min 8  sec   cpu: 108.3 %
mem: [1902, 1902, 1902] MB [DSK: Pass 1/1, Step 2: counting kmers   ]
2.24 %   elapsed:   0 min 2  sec   remaining:   1 min 8  sec   cpu:
108.3 %   mem: [1904, 1904, 1904] MB [DSK: Pass 1/1, Step 2: counting
kmers   ]  3.72 %   elapsed:   0 min 2  sec   remaining:   0 min 41 sec
  cpu: 109.6 %   mem: [1904, 1904, 1904] MB [DSK: Pass 1/1, Step 2:
counting kmers   ]  5.27 %   elapsed:   0 min 2  sec   remaining:   0
min 28 sec   cpu: 109.6 %   mem: [1904, 1904, 1904] MB [DSK: Pass 1/1,
Step 2: counting kmers   ]  5.27 %   elapsed:   0 min 2  sec
remaining:   0 min 28 sec   cpu: 109.6 %   mem: [1905, 1905, 1905] MB
[DSK: Pass 1/1, Step 2: counting kmers   ]  6.52 %   elapsed:   0 min 2
 sec   remaining:   0 min 22 sec   cpu: 109.6 %   mem: [1909, 1909,
1909] MB [DSK: Pass 1/1, Step 2: counting kmers   ]  8%   elapsed:
 0 min 2  sec   remaining:   0 min 18 sec   cpu: 110.8 %   mem: [1912,
1912, 1912] MB [DSK: Pass 1/1, Step 2: counting kmers   ]  8.81 %
elapsed:   0 min 2  sec   remaining:   0 min 16 sec   cpu: 111.5 %
mem: [1912, 1912, 1912] MB [DSK: Pass 1/1, Step 2: counting kmers   ]
10.1 %   elapsed:   0 min 2  sec   remaining:   0 min 14 sec   cpu:
111.5 %   mem: [1913, 1913, 1913] MB [DSK: Pass 1/1, Step 2: counting
kmers   ]  10.1 %   elapsed:   0 min 2  sec   remaining:   0 min 14 sec
  cpu: 111.5 %   mem: [1913, 1913, 1914] MB [DSK: Pass 1/1, Step 2:
counting kmers   ]  12.2 %   elapsed:   0 min 2  sec   remaining:   0
min 11 sec   cpu: 112.1 %   mem: [1917, 1917, 1917] MB [DSK: Pass 1/1,
Step 2: counting kmers   ]  12.2 %   elapsed:   0 min 2  sec
remaining:   0 min 11 sec   cpu: 112.1 %   mem: [1918, 1918, 1918] MB
[DSK: Pass 1/1, Step 2: counting kmers   ]  13.3 %   elapsed:   0 min 2
 sec   remaining:   0 min 10 sec   cpu: 112.1 %   mem: [1918, 1918,
1918] MB [DSK: Pass 1/1, Step 2: counting kmers   ]  14.3 %   elapsed:
 0 min 2  sec   remaining:   0 min 9  sec   cpu: 112.1 %   mem: [1920,
1920, 1920] MB [DSK: Pass 1/1, Step 2: counting kmers   ]  15.6 %
elapsed:   0 min 2  sec   remaining:   0 min 9  sec   cpu: 113.4 %
mem: [1925, 1925, 1925] MB [DSK: Pass 1/1, Step 2: counting kmers   ]
16.9 %   elapsed:   0 min 2  sec   remaining:   0 min 8  sec   cpu:
114.0 %   mem: [1928, 1928, 1928] MB [DSK: Pass 1/1, Step 2: co

Processed: gatb-core breaks discosnp autopkgtest: Segmentation fault

[Debian Bug Tracking System]

Processing control commands:

> found -1 gatb-core/1.4.2+dfsg-7
Bug #998143 [src:gatb-core, src:discosnp] gatb-core breaks discosnp 
autopkgtest: Segmentation fault
Marked as found in versions gatb-core/1.4.2+dfsg-7.
> found -1 discosnp/4.4.4-2
Bug #998143 [src:gatb-core, src:discosnp] gatb-core breaks discosnp 
autopkgtest: Segmentation fault
Marked as found in versions discosnp/4.4.4-2.

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

Bug#998142: opencv breaks node-opencv autopkgtest: c++ Exception processing resize

[Paul Gevers]

Source: opencv, node-opencv
Control: found -1 opencv/4.5.4+dfsg-1
Control: found -1 node-opencv/7.0.0+git20200310.6c13234-3
Severity: serious
Tags: sid bookworm
X-Debbugs-CC: debian...@lists.debian.org
User: debian...@lists.debian.org
Usertags: breaks needs-update

Dear maintainer(s),

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

   passfail
opencv from testing4.5.4+dfsg-1
node-opencvfrom testing7.0.0+git20200310.6c13234-3
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 opencv 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=opencv

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

dpkg-architecture: warning: cannot determine CC system type, falling
back to default (native compilation)
TAP version 13
# Smoke tests / Can Import
ok 1 imported fine
ok 2 version is there:4.5
ok 3 point is there
ok 4 matrix is there
# importing library multiple times is ok
ok 5 null
ok 6 null
# Point
ok 7 should be truthy
ok 8 cannot call without new
ok 9 should be strictly equal
ok 10 should be strictly equal
ok 11 should be strictly equal
ok 12 should be strictly equal
ok 13 Points are immutable
ok 14 Points are immutable
ok 15 should be truthy
ok 16 should be strictly equal
# Matrix constructor
ok 17 should be truthy
ok 18 should be truthy
ok 19 should be truthy
ok 20 should be truthy
ok 21 should be truthy
# Matrix accessors
ok 22 should be deeply equivalent
ok 23 should be strictly equal
ok 24 should be strictly equal
ok 25 should be strictly equal
ok 26 should be strictly equal
ok 27 should be deeply equivalent
ok 28 should be strictly equal
/tmp/autopkgtest-lxc.9lc6u5xq/downtmp/autopkgtest_tmp/unittest0svMmN/test/unit.js:83
  mat.resize(8,9);
  ^

Error: c++ Exception processing resize
at Test.
(/tmp/autopkgtest-lxc.9lc6u5xq/downtmp/autopkgtest_tmp/unittest0svMmN/test/unit.js:83:7)
at Test.bound [as _cb] (/usr/share/nodejs/tape/lib/test.js:96:32)
at Test.run (/usr/share/nodejs/tape/lib/test.js:114:31)
at Test.bound [as run] (/usr/share/nodejs/tape/lib/test.js:96:32)
at Immediate.next (/usr/share/nodejs/tape/lib/results.js:88:19)
at processImmediate (internal/timers.js:461:21)
autopkgtest [23:11:08]: test unittest




OpenPGP_signature
Description: OpenPGP digital signature

Processed: opencv breaks node-opencv autopkgtest: c++ Exception processing resize

[Debian Bug Tracking System]

Processing control commands:

> found -1 opencv/4.5.4+dfsg-1
Bug #998142 [src:opencv, src:node-opencv] opencv breaks node-opencv 
autopkgtest: c++ Exception processing resize
Marked as found in versions opencv/4.5.4+dfsg-1.
> found -1 node-opencv/7.0.0+git20200310.6c13234-3
Bug #998142 [src:opencv, src:node-opencv] opencv breaks node-opencv 
autopkgtest: c++ Exception processing resize
Marked as found in versions node-opencv/7.0.0+git20200310.6c13234-3.

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

Bug#998141: opencv breaks auto-multiple-choice autopkgtest

[Paul Gevers]

Source: opencv, auto-multiple-choice
Control: found -1 opencv/4.5.4+dfsg-1
Control: found -1 auto-multiple-choice/1.5.1-2
Severity: serious
Tags: sid bookworm
X-Debbugs-CC: debian...@lists.debian.org
User: debian...@lists.debian.org
Usertags: breaks needs-update

Dear maintainer(s),

With a recent upload of opencv the autopkgtest of auto-multiple-choice
fails in testing when that autopkgtest is run with the binary packages
of opencv from unstable. It passes when run with only packages from
testing. In tabular form:

   passfail
opencv from testing4.5.4+dfsg-1
auto-multiple-choice   from testing1.5.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 opencv 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=opencv

https://ci.debian.net/data/autopkgtest/testing/amd64/a/auto-multiple-choice/16302653/log.gz

[>] Installed in /tmp/Sva1UUZmVK
[I] Provided scans: 1
[*] auto-multiple-choice prepare --filter  --with pdflatex --mode s[sc]
--epoch 946684800 --n-copies 1 --prefix /tmp/Sva1UUZmVK/
/tmp/Sva1UUZmVK/source.tex --data /tmp/Sva1UUZmVK/data --debug
/tmp/Sva1UUZmVK/debug.log
[*] auto-multiple-choice meptex --src /tmp/Sva1UUZmVK/calage.xy --data
/tmp/Sva1UUZmVK/data --debug /tmp/Sva1UUZmVK/debug.log
[*] auto-multiple-choice prepare --filter  --with pdflatex --mode b
--n-copies 1 --data /tmp/Sva1UUZmVK/data /tmp/Sva1UUZmVK/source.tex
--debug /tmp/Sva1UUZmVK/debug.log
[T] No layout defects
[*] auto-multiple-choice prepare --filter  --with pdflatex --mode k
--epoch 946684800 --n-copies 1 --prefix /tmp/Sva1UUZmVK/
/tmp/Sva1UUZmVK/source.tex --debug /tmp/Sva1UUZmVK/debug.log
[*] auto-multiple-choice imprime --sujet /tmp/Sva1UUZmVK/corrige.pdf
--methode file --output /tmp/Sva1UUZmVK/xx-copie-%e.pdf --fich-numeros
/tmp/Sva1UUZmVK/num --data /tmp/Sva1UUZmVK/data --extract-with qpdf
--password  --password-key password --students-list
/tmp/Sva1UUZmVK/names.csv --list-key id --debug /tmp/Sva1UUZmVK/debug.log
[*] auto-multiple-choice read-pdfform --list
/tmp/Sva1UUZmVK/scans-list.txt --data /tmp/Sva1UUZmVK/data --password
--no-multiple --debug /tmp/Sva1UUZmVK/debug.log
[*] auto-multiple-choice getimages --list /tmp/Sva1UUZmVK/scans-list.txt
--copy-to /tmp/Sva1UUZmVK/scans --orientation portrait --password
--no-force-convert --no-use-pdftk --debug /tmp/Sva1UUZmVK/debug.log
[*] auto-multiple-choice analyse --no-multiple --bw-threshold 0.6
--pre-allocate 0 --tol-marque 0.4 --no-ignore-red --projet
/tmp/Sva1UUZmVK --data /tmp/Sva1UUZmVK/data --debug-image-dir
/tmp/Sva1UUZmVK/cr --liste-fichiers /tmp/Sva1UUZmVK/scans-list.txt
--debug /tmp/Sva1UUZmVK/debug.log
[*] auto-multiple-choice analyse --no-multiple --bw-threshold 0.6
--pre-allocate 0 --tol-marque 0.4 --no-ignore-red --debug-pixels
--projet /tmp/Sva1UUZmVK --data /tmp/Sva1UUZmVK/data --liste-fichiers
/tmp/Sva1UUZmVK/scans-list.txt --debug /tmp/Sva1UUZmVK/debug.log
[*] auto-multiple-choice note --data /tmp/Sva1UUZmVK/data --seuil 0.5
--seuil-up 1 --grain 0.01 --arrondi i --notemax 20 --postcorrect-student
 --postcorrect-copy  --debug /tmp/Sva1UUZmVK/debug.log
[*] auto-multiple-choice association-auto --liste
/tmp/Sva1UUZmVK/names.csv --liste-key id --pre-association --data
/tmp/Sva1UUZmVK/data --debug /tmp/Sva1UUZmVK/debug.log
[I] Marks:
[T] Perfect copies test: [T] Association test: 2
[E] Uncorrect association: 2
autopkgtest [23:14:10]: test simple




OpenPGP_signature
Description: OpenPGP digital signature

Processed: opencv breaks auto-multiple-choice autopkgtest

[Debian Bug Tracking System]

Processing control commands:

> found -1 opencv/4.5.4+dfsg-1
Bug #998141 [src:opencv, src:auto-multiple-choice] opencv breaks 
auto-multiple-choice autopkgtest
Marked as found in versions opencv/4.5.4+dfsg-1.
> found -1 auto-multiple-choice/1.5.1-2
Bug #998141 [src:opencv, src:auto-multiple-choice] opencv breaks 
auto-multiple-choice autopkgtest
Marked as found in versions auto-multiple-choice/1.5.1-2.

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

Processed: opencv breaks caffe autopkgtest: (-4:Insufficient memory) Failed to allocate 160708409713560 bytes in function 'OutOfMemoryError'

[Debian Bug Tracking System]

Processing control commands:

> found -1 opencv/4.5.4+dfsg-1
Bug #998140 [src:opencv, src:caffe] opencv breaks caffe autopkgtest: 
(-4:Insufficient memory) Failed to allocate 160708409713560 bytes in function 
'OutOfMemoryError'
Marked as found in versions opencv/4.5.4+dfsg-1.
> found -1 caffe/1.0.0+git20180821.99bd997-8
Bug #998140 [src:opencv, src:caffe] opencv breaks caffe autopkgtest: 
(-4:Insufficient memory) Failed to allocate 160708409713560 bytes in function 
'OutOfMemoryError'
Marked as found in versions caffe/1.0.0+git20180821.99bd997-8.

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

Processed: src:browser-request: fails to migrate to testing for too long: uploader built arch:all binaries

[Debian Bug Tracking System]

Processing control commands:

> close -1 0.3.3-4
Bug #998139 [src:browser-request] src:browser-request: fails to migrate to 
testing for too long: uploader built arch:all binaries
Marked as fixed in versions browser-request/0.3.3-4.
Bug #998139 [src:browser-request] src:browser-request: fails to migrate to 
testing for too long: uploader built arch:all binaries
Marked Bug as done

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

Bug#998139: src:browser-request: fails to migrate to testing for too long: uploader built arch:all binaries

[Paul Gevers]

Source: browser-request
Version: 0.3.3-2
Severity: serious
Control: close -1 0.3.3-4
X-Debbugs-CC: jel...@debian.org
Tags: sid bookworm pending
User: release.debian@packages.debian.org
Usertags: out-of-sync

Dear maintainer(s),

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

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

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

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

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

Paul

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




OpenPGP_signature
Description: OpenPGP digital signature

Processed: src:rust-utf-8: fails to migrate to testing for too long: autopkgtest regression

[Debian Bug Tracking System]

Processing control commands:

> close -1 0.7.6-1
Bug #998138 [src:rust-utf-8] src:rust-utf-8: fails to migrate to testing for 
too long: autopkgtest regression
Marked as fixed in versions rust-utf-8/0.7.6-1.
Bug #998138 [src:rust-utf-8] src:rust-utf-8: fails to migrate to testing for 
too long: autopkgtest regression
Marked Bug as done
> block -1 by 995419
Bug #998138 {Done: Paul Gevers } [src:rust-utf-8] 
src:rust-utf-8: fails to migrate to testing for too long: autopkgtest regression
998138 was not blocked by any bugs.
998138 was not blocking any bugs.
Added blocking bug(s) of 998138: 995419

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

Bug#998138: src:rust-utf-8: fails to migrate to testing for too long: autopkgtest regression

[Paul Gevers]

Source: rust-utf-8
Version: 0.7.5-1
Severity: serious
Control: close -1 0.7.6-1
Tags: sid bookworm
User: release.debian@packages.debian.org
Usertags: out-of-sync
Control: block -1 by 995419

Dear maintainer(s),

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

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

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

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

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

Paul

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




OpenPGP_signature
Description: OpenPGP digital signature

Processed: src:python-parameterized: fails to migrate to testing for too long: autopkgtest regression

[Debian Bug Tracking System]

Processing control commands:

> close -1 0.8.1-1
Bug #998137 [src:python-parameterized] src:python-parameterized: fails to 
migrate to testing for too long: autopkgtest regression
Marked as fixed in versions python-parameterized/0.8.1-1.
Bug #998137 [src:python-parameterized] src:python-parameterized: fails to 
migrate to testing for too long: autopkgtest regression
Marked Bug as done
> block -1 by 995356
Bug #998137 {Done: Paul Gevers } [src:python-parameterized] 
src:python-parameterized: fails to migrate to testing for too long: autopkgtest 
regression
998137 was not blocked by any bugs.
998137 was not blocking any bugs.
Added blocking bug(s) of 998137: 995356

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

Bug#998137: src:python-parameterized: fails to migrate to testing for too long: autopkgtest regression

[Paul Gevers]

Source: python-parameterized
Version: 0.7.0-2
Severity: serious
Control: close -1 0.8.1-1
Tags: sid bookworm
User: release.debian@packages.debian.org
Usertags: out-of-sync
Control: block -1 by 995356

Dear maintainer(s),

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

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

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

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

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

Paul

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




OpenPGP_signature
Description: OpenPGP digital signature

Bug#997758: marked as done (nose: FTBFS: There is a syntax error in your configuration file: invalid syntax (conf.py, line 220))

[Debian Bug Tracking System]

Your message dated Sat, 30 Oct 2021 20:34:51 +
with message-id 
and subject line Bug#997758: fixed in nose 1.3.7-8
has caused the Debian Bug report #997758,
regarding nose: FTBFS: There is a syntax error in your configuration file: 
invalid syntax (conf.py, line 220)
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.)


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

Hi,

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


Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> dh_auto_build
> I: pybuild base:232: /usr/bin/python3 setup.py build 
> running build
> running build_py
> creating /<>/.pybuild/cpython3_3.9_nose/build/nose
> copying nose/proxy.py -> 
> /<>/.pybuild/cpython3_3.9_nose/build/nose
> copying nose/case.py -> /<>/.pybuild/cpython3_3.9_nose/build/nose
> copying nose/core.py -> /<>/.pybuild/cpython3_3.9_nose/build/nose
> copying nose/__init__.py -> 
> /<>/.pybuild/cpython3_3.9_nose/build/nose
> copying nose/__main__.py -> 
> /<>/.pybuild/cpython3_3.9_nose/build/nose
> copying nose/selector.py -> 
> /<>/.pybuild/cpython3_3.9_nose/build/nose
> copying nose/inspector.py -> 
> /<>/.pybuild/cpython3_3.9_nose/build/nose
> copying nose/loader.py -> 
> /<>/.pybuild/cpython3_3.9_nose/build/nose
> copying nose/result.py -> 
> /<>/.pybuild/cpython3_3.9_nose/build/nose
> copying nose/util.py -> /<>/.pybuild/cpython3_3.9_nose/build/nose
> copying nose/suite.py -> 
> /<>/.pybuild/cpython3_3.9_nose/build/nose
> copying nose/config.py -> 
> /<>/.pybuild/cpython3_3.9_nose/build/nose
> copying nose/failure.py -> 
> /<>/.pybuild/cpython3_3.9_nose/build/nose
> copying nose/importer.py -> 
> /<>/.pybuild/cpython3_3.9_nose/build/nose
> copying nose/exc.py -> /<>/.pybuild/cpython3_3.9_nose/build/nose
> copying nose/twistedtools.py -> 
> /<>/.pybuild/cpython3_3.9_nose/build/nose
> copying nose/pyversion.py -> 
> /<>/.pybuild/cpython3_3.9_nose/build/nose
> copying nose/commands.py -> 
> /<>/.pybuild/cpython3_3.9_nose/build/nose
> creating /<>/.pybuild/cpython3_3.9_nose/build/nose/ext
> copying nose/ext/__init__.py -> 
> /<>/.pybuild/cpython3_3.9_nose/build/nose/ext
> copying nose/ext/dtcompat.py -> 
> /<>/.pybuild/cpython3_3.9_nose/build/nose/ext
> creating /<>/.pybuild/cpython3_3.9_nose/build/nose/plugins
> copying nose/plugins/skip.py -> 
> /<>/.pybuild/cpython3_3.9_nose/build/nose/plugins
> copying nose/plugins/__init__.py -> 
> /<>/.pybuild/cpython3_3.9_nose/build/nose/plugins
> copying nose/plugins/cover.py -> 
> /<>/.pybuild/cpython3_3.9_nose/build/nose/plugins
> copying nose/plugins/logcapture.py -> 
> /<>/.pybuild/cpython3_3.9_nose/build/nose/plugins
> copying nose/plugins/debug.py -> 
> /<>/.pybuild/cpython3_3.9_nose/build/nose/plugins
> copying nose/plugins/testid.py -> 
> /<>/.pybuild/cpython3_3.9_nose/build/nose/plugins
> copying nose/plugins/prof.py -> 
> /<>/.pybuild/cpython3_3.9_nose/build/nose/plugins
> copying nose/plugins/doctests.py -> 
> /<>/.pybuild/cpython3_3.9_nose/build/nose/plugins
> copying nose/plugins/deprecated.py -> 
> /<>/.pybuild/cpython3_3.9_nose/build/nose/plugins
> copying nose/plugins/builtin.py -> 
> /<>/.pybuild/cpython3_3.9_nose/build/nose/plugins
> copying nose/plugins/failuredetail.py -> 
> /<>/.pybuild/cpython3_3.9_nose/build/nose/plugins
> copying nose/plugins/isolate.py -> 
> /<>/.pybuild/cpython3_3.9_nose/build/nose/plugins
> copying nose/plugins/multiprocess.py -> 
> /<>/.pybuild/cpython3_3.9_nose/build/nose/plugins
> copying nose/plugins/plugintest.py -> 
> /<>/.pybuild/cpython3_3.9_nose/build/nose/plugins
> copying nose/plugins/errorclass.py -> 
> /<>/.pybuild/cpython3_3.9_nose/build/nose/plugins
> copying nose/plugins/xunit.py -> 
> /<>/.pybuild/cpython3_3.9_nose/build/nose/plugins
> copying nose/plugins/manager.py -> 
> /<>/.pybuild/cpython3_3.9_nose/build/nose/plugins
> copying nose/plugins/attrib.py -> 
> /<>/.pybuild/cpython3_3.9_nose/build/nose/plugins
> copying nose/plugins/allmodules.py -> 
> /<>/.pybuild/cpython3_3.9_nose/build/nose/plugins
> copying nose/plugins/base.py -> 
> /<>/.pybuild/cpython3_3.9_nose/build/nose/plugins
> copying nose/plugins/capture.py -> 
> /<>/.pybuild/cpython3_3.9_nose/build/nose/plugins
> copying nose/plugins/collect.py -> 
> /<>/.pybuild/cpython3_3.9_nose/build/nose/plugins
> creating /<>/.pybuild/cpython3_3.9_nose/build/nose/sphinx
> copying nose/sphin

Processed: src:node-toidentifier: fails to migrate to testing for too long: uploader built arch:all binaries

[Debian Bug Tracking System]

Processing control commands:

> close -1 1.0.0-4
Bug #998136 [src:node-toidentifier] src:node-toidentifier: fails to migrate to 
testing for too long: uploader built arch:all binaries
Marked as fixed in versions node-toidentifier/1.0.0-4.
Bug #998136 [src:node-toidentifier] src:node-toidentifier: fails to migrate to 
testing for too long: uploader built arch:all binaries
Marked Bug as done

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

Bug#997521: freedict: FTBFS: Failed to create secure directory (/sbuild-nonexistent/.config/pulse): No such file or directory

[Lucas Nussbaum]

On 29/10/21 at 16:17 +0200, Sebastian Humenda wrote:
> Hi
> 
> Due to the way the FreeDict stylesheets are written, a lot of memory is used.
> Could you provide the amount of RAM that is used for the failed build? If it
> is below 16G, could it be increased, somehow?

Hi Sebastian,

I use AWS EC2 m5.xlarge instances. so it's 16 GB of RAM. I could use
larger instances, yes. However, the resources requirements for freedict
are a bit unusual. I wonder if they should be documented in a bug
(without release critical severity). Given the time it takes to build
freedict, I might just exclude it from my regular rebuilds.

Lucas

Bug#998136: src:node-toidentifier: fails to migrate to testing for too long: uploader built arch:all binaries

[Paul Gevers]

Source: node-toidentifier
Version: 1.0.0-2
Severity: serious
Control: close -1 1.0.0-4
X-Debbugs-CC: jel...@debian.org
Tags: sid bookworm pending
User: release.debian@packages.debian.org
Usertags: out-of-sync

Dear maintainer(s),

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

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

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

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

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

Paul

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




OpenPGP_signature
Description: OpenPGP digital signature

Processed: src:node-xdg-basedir: fails to migrate to testing for too long: uploader built arch:all binaries

[Debian Bug Tracking System]

Processing control commands:

> close -1 3.0.0-2
Bug #998135 [src:node-xdg-basedir] src:node-xdg-basedir: fails to migrate to 
testing for too long: uploader built arch:all binaries
Marked as fixed in versions node-xdg-basedir/3.0.0-2.
Bug #998135 [src:node-xdg-basedir] src:node-xdg-basedir: fails to migrate to 
testing for too long: uploader built arch:all binaries
Marked Bug as done

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

Bug#998135: src:node-xdg-basedir: fails to migrate to testing for too long: uploader built arch:all binaries

[Paul Gevers]

Source: node-xdg-basedir
Version: 3.0.0-1
Severity: serious
Control: close -1 3.0.0-2
X-Debbugs-CC: jel...@debian.org
Tags: sid bookworm
User: release.debian@packages.debian.org
Usertags: out-of-sync

Dear maintainer(s),

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

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

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

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

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

Paul

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




OpenPGP_signature
Description: OpenPGP digital signature

Bug#997122: marked as done (assembly-stats: FTBFS: fastq_unittest.cpp:53:78: error: taking address of rvalue [-fpermissive])

[Debian Bug Tracking System]

Your message dated Sat, 30 Oct 2021 20:33:47 +
with message-id 
and subject line Bug#997122: fixed in assembly-stats 1.0.1+ds-5
has caused the Debian Bug report #997122,
regarding assembly-stats: FTBFS: fastq_unittest.cpp:53:78: error: taking 
address of rvalue [-fpermissive]
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.)


-- 
997122: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997122
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: assembly-stats
Version: 1.0.1+ds-4
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs

Hi,

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


Relevant part (hopefully):
> /usr/bin/c++  -I/usr/include/gtest -Wall -g -O3 -pthread -MD -MT 
> CMakeFiles/runUnitTests.dir/stats_unittest.cpp.o -MF 
> CMakeFiles/runUnitTests.dir/stats_unittest.cpp.o.d -o 
> CMakeFiles/runUnitTests.dir/stats_unittest.cpp.o -c 
> /<>/stats_unittest.cpp
> /<>/fastq_unittest.cpp: In member function ‘virtual void 
> Fastq_ReadFromFile_Test::TestBody()’:
> /<>/fastq_unittest.cpp:53:78: error: taking address of rvalue 
> [-fpermissive]
>53 | string expectedName = static_cast( 
> &(ostringstream() << counter) )->str();
>   | 
> ~^~~
> /<>/fasta_unittest.cpp: In member function ‘virtual void 
> Fasta_ReadFromFile_Test::TestBody()’:
> /<>/fasta_unittest.cpp:97:78: error: taking address of rvalue 
> [-fpermissive]
>97 | string expectedName = static_cast( 
> &(ostringstream() << counter) )->str();
>   | 
> ~^~~
> make[3]: *** [CMakeFiles/runUnitTests.dir/build.make:93: 
> CMakeFiles/runUnitTests.dir/fastq_unittest.cpp.o] Error 1


The full build log is available from:
http://qa-logs.debian.net/2021/10/23/assembly-stats_1.0.1+ds-4_unstable.log

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

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

If you fail to reproduce this, please provide a build log and diff it with mine
so that we can identify if something relevant changed in the meantime.
--- End Message ---
--- Begin Message ---
Source: assembly-stats
Source-Version: 1.0.1+ds-5
Done: Nilesh Patra 

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

Debian distribution maintenance software
pp.
Nilesh Patra  (supplier of updated assembly-stats package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sun, 31 Oct 2021 01:26:55 +0530
Source: assembly-stats
Architecture: source
Version: 1.0.1+ds-5
Distribution: unstable
Urgency: medium
Maintainer: Debian Med Packaging Team 

Changed-By: Nilesh Patra 
Closes: 997122
Changes:
 assembly-stats (1.0.1+ds-5) unstable; urgency=medium
 .
   * Team Upload.
   * Add patch to fix FTBFS with gcc-11 (Closes: #997122)
   * Update d/u/metadata
Checksums-Sha1:
 766ee5e2d2ec018ddd7a1a5b2e37a2d618c1a3da 2091 assembly-stats_1.0.1+ds-5.dsc
 371dee535d28f0aae7a9ee939f5155a7fc3d65cd 4564 
assembly-stats_1.0.1+ds-5.debian.tar.xz
 d35eba09bedb1abaec7331451061d5c1faf82df1 6821 
assembly-stats_1.0.1+ds-5_amd64.buildinfo
Checksums-Sha256:
 3a00938962190e9bffda11dbad05ad2b8208b9c4956f52776c0d9cbe65dbe630 2091 
assembly-stats_1.0.1+ds-5.dsc
 08b4ac456cba2dbe8f19595d9400f0dad5107a71a997ebfcda2584eece2410b4 4564 
assembly-stats_1.0.1+ds-5.debian.tar.xz
 4981d71fa623deada778ff4b8903c894e2c34f162b07a9f39d177f79a00c6530 6821 
assembly-stats_1.0.1+ds-5_amd64.buildinfo
Files:
 0744f7377f75b216ccc2a19499692f6f 2091 science optional 
assembly-stats_1.0.1+ds-5.dsc
 2e831f270314da661f67cd8fd3e0124f 4564 science optional 
assembly-stats_1.0.1+ds-5.debian.tar.xz
 8b210c115d64202b8adfa84a1837bb3f 6821 science optional 
assembly-stats_1.0.1+ds-5_amd64.buildinfo

---

Bug#997940: view3dscene: FTBFS with fpc 3.2.2

[Paul Gevers]

Hi Abou,

Our messages crossed.

On 30-10-2021 22:09, Abou Al Montacir wrote:
> On Sat, 2021-10-30 at 15:21 +0200, Paul Gevers wrote:
>>  In that way, the Debian
>> infrastructure knows that a rebuild (or potentially manual action) is
>> needed. We don't want it to be too tight.
> I don't know exactly hos Debian infrastructure decides to rebuild or not
> a package,

It doesn't decide to do that automatically, but for some forms there are
processes in place to warn the release team. And if necessary, they'll
trigger the required rebuilds. But only if they notice. I just realized
that our fpc-abi-* doesn't trigger any of the existing processes except
the 60-days-out-of-sync process (manually by me). So fpc will be stalled
to migrate until the release team is made aware (by the Free Pascal
Team). Technically this is a transition, so we *should* request a
transition slot: https://wiki.debian.org/Teams/ReleaseTeam/Transitions
but because of the low number of packages and the fact that they are all
team maintained, that's a bit overkill. But we should be more aware of
it ourselves.

> but what I can imagine is that view3dscene build depends on
> castle-engine (which depends on fp-units-rtl-3.2.0)

I don't see that last fact, but maybe I'm overlooking.
fp-units-castle-game-engine doesn't depend on any src:fpc binary AFAICT.
A, wait, looking at the source, I think we *INTENDED* to have that
dependency, but apparently it doesn't get added:
https://salsa.debian.org/pascal-team/castle-game-engine/-/blob/master/debian/control#L44
We probably forgot to fill that variable.

Paul



OpenPGP_signature
Description: OpenPGP digital signature

Bug#997940: [Pkg-pascal-devel] Bug#997940: view3dscene: FTBFS with fpc 3.2.2

[Paul Gevers]

Hi,

On 30-10-2021 15:21, Paul Gevers wrote:
> Hi Abou,
> 
> On 30-10-2021 12:46, Abou Al Montacir wrote:
>>> "Just" rebuilding is not the solution to paper over such an issue, we'd
>>> need to prevent it from going unnoticed next time. It should show up on
>>> https://release.debian.org/transitions/
>>>  with an auto-upperlimit-fpc
>>> transition such that the release team is automatically warned that
>>> rebuilds are needed and to prevent fpc from migrating until the rebuild
>>> happened and is ready to migrate too.
>> I don't know for now how to handle this efficiently. but the easiest way
>> is to say, each new upload of FPC triggers all libraries (not programs)
>> rebuild.
> 
> So all libraries need a Depends on a binary from src:fpc with an upper
> limit (generated during the build). In that way, the Debian
> infrastructure knows that a rebuild (or potentially manual action) is
> needed. We don't want it to be too tight. When you said "any new version
> of FPC" do you mean each patch level too, or on only minor level? How
> about Debian new uploads?

Wait, I think we already fixed this in the past. We have
"fpc-abi-3.2.2", which is provided by fp-units-rtl-3.2.2. So the
relation with lazarus is correctly glued together. But I think
fp-units-castle-game-engine is missing that Depends. Do you agree we
should add it there similar as we do in src:lazarus?

Paul



OpenPGP_signature
Description: OpenPGP digital signature

Bug#997940: view3dscene: FTBFS with fpc 3.2.2

[Abou Al Montacir]

Hi Paul,

On Sat, 2021-10-30 at 15:21 +0200, Paul Gevers wrote:
> So all libraries need a Depends on a binary from src:fpc with an upper
> limit (generated during the build).
In some sense, this is done as any FPC library should depend on RTL package fp-
units-rtl-${UPSTREAM_VERSION} with >= condition.
This implies that if 3.2.2 is introduced instead of 3.2.0 then the library in
the repository is not usable anymore.
However in practice, the upgrade of FPC will leave old version installed and
thus users will be able to continue using old library with old compiler.
>  In that way, the Debian
> infrastructure knows that a rebuild (or potentially manual action) is
> needed. We don't want it to be too tight.
I don't know exactly hos Debian infrastructure decides to rebuild or not a
package, but what I can imagine is that view3dscene build depends on castle-
engine (which depends on fp-units-rtl-3.2.0) and on fp-compiler.
In this case fp-compiler will be pulled as 3.2.2 and will drag fp-units-rt-3.2.2
while fp-units-rtl-3.2.0 will be dragged by direct dependency.
In this case, the build system thinks it has got all dependencies but in
reality, ppu files of castle-engine, that are compiled with fp-compiler 3.2.0
will net be usable by 3.2.2 compiler.
>  When you said "any new version
> of FPC" do you mean each patch level too, or on only minor level? How
> about Debian new uploads?
For a ppu to be used by the compiler is should:
   1. have the same ppu version as the one supported by the compiler. This may
  not be the case between different upstream releases.
   2. be compiled with an RTL version that have the very same interface for used
  units. If any unit from RTL changed interface, then the compiler will fail
  to use it and will ask for recompiling the library unit that is using it.
  It is important to note that changes of the code of any inline function is
  considered as an interface change (think as in C inlines functions are in
  .h files).
   3. be compiled using -Ur flag to avoid the compiler to try to recompile it if
  implementation is changed (this happens usually after a bug fix).

When we upload a new Debian version, we are generally changing implementation.
This is falls under the case number 3. We should be safe and would not need to
recompile anything.

I hope this makes the situation clearer.
-- 
Cheers, Abou Al Montacir


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

Processed: Bug#997122 marked as pending in assembly-stats

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #997122 [src:assembly-stats] assembly-stats: FTBFS: 
fastq_unittest.cpp:53:78: error: taking address of rvalue [-fpermissive]
Added tag(s) pending.

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

Bug#997122: marked as pending in assembly-stats

[Nilesh Patra]

Control: tag -1 pending

Hello,

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

https://salsa.debian.org/med-team/assembly-stats/-/commit/f17fb8b611b07cdbdf92866e920a45b96c1fd912


Add patch to fix FTBFS with gcc-11 (Closes: #997122)


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/997122

Processed: reassign 998126 to src:pipewire, severity of 998126 is serious

[Debian Bug Tracking System]

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

> reassign 998126 src:pipewire 0.3.39-3
Bug #998126 [pipewire-pulse-dbgsym] pipewire-pulse-dbgsym: dbgsym files overlap 
between packages
Warning: Unknown package 'pipewire-pulse-dbgsym'
Bug reassigned from package 'pipewire-pulse-dbgsym' to 'src:pipewire'.
No longer marked as found in versions pipewire/0.3.39-3.
Ignoring request to alter fixed versions of bug #998126 to the same values 
previously set
Bug #998126 [src:pipewire] pipewire-pulse-dbgsym: dbgsym files overlap between 
packages
Marked as found in versions pipewire/0.3.39-3.
> severity 998126 serious
Bug #998126 [src:pipewire] pipewire-pulse-dbgsym: dbgsym files overlap between 
packages
Severity set to 'serious' from 'important'
> thanks
Stopping processing here.

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

Bug#996569: getmail6 naming issues

[Remco Rijnders]

I'd like to strongly object to the removal of this package from Debian.

As per the Debian social contract: "4. Our priorities are our users and free
software. We will be guided by the needs of our users and the free software
community. *We will place their interests first in our priorities*".

It is my understanding that the needs of our users was the main reason that
Charles' getmail was replaced by the getmail6 fork. What has changed since then?

Also, per the same social contract: "4. Integrity of the Author's Source Code
(...) The license may require derived works to carry a different name or version
number from the original software. (This is a compromise. The Debian group
encourages all authors not to restrict any files, source or binary, from being
modified)".

As far as I am aware, the license under which getmail is distributed does not
have this requirement other than that "(y)ou must cause the the modified files
to carry prominent notices stating that you changed the files and the date of
any change."

I believe getmail6 sufficiently meets this requirement. If it doesn't, please
point out how and where it doesn't so this can be addressed.

Bug#998131: src:node-yamlish: fails to migrate to testing for too long: uploader built arch:all binaries

[Paul Gevers]

Source: node-yamlish
Version: 0.0.7-1
Severity: serious
Control: close -1 0.0.7-3
X-Debbugs-CC: jel...@debian.org
Tags: sid bookworm pending
User: release.debian@packages.debian.org
Usertags: out-of-sync

Dear maintainer(s),

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

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

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

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

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

Paul

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




OpenPGP_signature
Description: OpenPGP digital signature

Processed: src:node-yamlish: fails to migrate to testing for too long: uploader built arch:all binaries

[Debian Bug Tracking System]

Processing control commands:

> close -1 0.0.7-3
Bug #998131 [src:node-yamlish] src:node-yamlish: fails to migrate to testing 
for too long: uploader built arch:all binaries
Marked as fixed in versions node-yamlish/0.0.7-3.
Bug #998131 [src:node-yamlish] src:node-yamlish: fails to migrate to testing 
for too long: uploader built arch:all binaries
Marked Bug as done

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

Processed: severity of 996170 is important

[Debian Bug Tracking System]

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

> severity 996170 important
Bug #996170 [src:linux] linux: FTBFS if bpftool detects clang-bpf-co-re
Severity set to 'important' from 'serious'
> thanks
Stopping processing here.

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

Bug#997258: marked as done (tiddit: FTBFS: Translocation.cpp:13:74: error: taking address of rvalue [-fpermissive])

[Debian Bug Tracking System]

Your message dated Sat, 30 Oct 2021 19:35:12 +
with message-id 
and subject line Bug#997258: fixed in tiddit 2.12.1+dfsg-2
has caused the Debian Bug report #997258,
regarding tiddit: FTBFS: Translocation.cpp:13:74: error: taking address of 
rvalue [-fpermissive]
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.)


-- 
997258: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997258
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: tiddit
Version: 2.12.1+dfsg-1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs

Hi,

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


Relevant part (hopefully):
> /usr/bin/c++  -I/<>/src -I/usr/include/bamtools -g -O2 
> -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat 
> -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -O3 -DNDEBUG   
> -Wno-deprecated -MD -MT 
> CMakeFiles/TIDDIT.dir/src/data_structures/findTranslocationsOnTheFly.cpp.o 
> -MF 
> CMakeFiles/TIDDIT.dir/src/data_structures/findTranslocationsOnTheFly.cpp.o.d 
> -o CMakeFiles/TIDDIT.dir/src/data_structures/findTranslocationsOnTheFly.cpp.o 
> -c /<>/src/data_structures/findTranslocationsOnTheFly.cpp
> /<>/src/data_structures/Translocation.cpp: In function 
> ‘std::string int2str(int)’:
> /<>/src/data_structures/Translocation.cpp:13:74: error: taking 
> address of rvalue [-fpermissive]
>13 | string converted= static_cast( 
> &(ostringstream() << to_be_converted) )->str();
>   | 
> ~^~~
> make[4]: *** [CMakeFiles/TIDDIT.dir/build.make:107: 
> CMakeFiles/TIDDIT.dir/src/data_structures/Translocation.cpp.o] Error 1


The full build log is available from:
http://qa-logs.debian.net/2021/10/23/tiddit_2.12.1+dfsg-1_unstable.log

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

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

If you fail to reproduce this, please provide a build log and diff it with mine
so that we can identify if something relevant changed in the meantime.
--- End Message ---
--- Begin Message ---
Source: tiddit
Source-Version: 2.12.1+dfsg-2
Done: Nilesh Patra 

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

Debian distribution maintenance software
pp.
Nilesh Patra  (supplier of updated tiddit package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sun, 31 Oct 2021 00:24:32 +0530
Source: tiddit
Architecture: source
Version: 2.12.1+dfsg-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Med Packaging Team 

Changed-By: Nilesh Patra 
Closes: 997258
Changes:
 tiddit (2.12.1+dfsg-2) unstable; urgency=medium
 .
   * Team Upload.
   * Add patch to fix FTBFS (Closes: #997258)
Checksums-Sha1:
 5379a7720b0f5ba0a97ed7eba18b4b293f77a5b5 2118 tiddit_2.12.1+dfsg-2.dsc
 689310c262bb43023547801f171f2e15d1be49cd 1733100 
tiddit_2.12.1+dfsg-2.debian.tar.xz
 6cd0be988900be1a67b1d0f37aad89afc1b88c0f 7561 
tiddit_2.12.1+dfsg-2_amd64.buildinfo
Checksums-Sha256:
 1a39aaf22db358d82149dcb121c5682a6177bd18252b244e91ac8bbf0fc35b15 2118 
tiddit_2.12.1+dfsg-2.dsc
 9417aaffc00db39c3e47585b07ff9b1db840cc76b9165984b867e3624c485d93 1733100 
tiddit_2.12.1+dfsg-2.debian.tar.xz
 c684730e8826b938f78b097a1b768d5755809a65c129c7c32ffdf109dccd1527 7561 
tiddit_2.12.1+dfsg-2_amd64.buildinfo
Files:
 49d70ecd9e5aa1d66308b84f52a413f7 2118 science optional tiddit_2.12.1+dfsg-2.dsc
 8073479d8d9d27b9d801916ff88ed397 1733100 science optional 
tiddit_2.12.1+dfsg-2.debian.tar.xz
 82f5ed97f6d4a179e6712f167345f3d7 7561 science optional 
tiddit_2.12.1+dfsg-2_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQJGBAEBCgAwFiEEPpmlJvXcwMu/HO6mALrnSzQzafEFAmF9m8ESHG5pbGVzaEBk
ZWJpYW4ub3JnAAoJEAC650s0M2nxiLIQALneKrnwjfJIitDtJ+aGJja3AZL5szDB
SYU7GD1SOO5cQHIK5zAU7Hrh2UgzpQZIgUce1E/J+ALnYA+lbHckDbz6TdpEP5k

Processed: Bug#997258 marked as pending in tiddit

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #997258 [src:tiddit] tiddit: FTBFS: Translocation.cpp:13:74: error: taking 
address of rvalue [-fpermissive]
Added tag(s) pending.

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

Bug#997258: marked as pending in tiddit

[Nilesh Patra]

Control: tag -1 pending

Hello,

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

https://salsa.debian.org/med-team/tiddit/-/commit/6c81f76b4646ed94a34e1e822b21502cd6904b2d


Add patch to fix FTBFS (Closes: #997258)


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/997258

Bug#997758: marked as pending in nose

[Dmitry Shachnev]

Control: tag -1 pending

Hello,

Bug #997758 in nose 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/nose/-/commit/639224803dc9c3d00da68163cf73344196dee6e1


Adapt to setuptools 58 removing support for 2to3 during builds.

- Add a patch to fix syntax in doc/conf.py for Python 3.
- Add a patch to remove code that relied on setuptools calling 2to3.
- Run 2to3 manually after build and before running tests.
- Update the commands to run tests.

Closes: #997758.

Thanks to Jakub Wilk for the suggestions!


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/997758

Processed: Bug#997758 marked as pending in nose

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #997758 [src:nose] nose: FTBFS: There is a syntax error in your 
configuration file: invalid syntax (conf.py, line 220)
Added tag(s) pending.

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

Bug#998114: Missing egg info directory prevents asciidoc cli tools from running

[Carsten Schoenert]

Hi Leon,

Am Sat, Oct 30, 2021 at 06:45:28PM +0200 schrieb Leon Marz:
> Thank you very much for finding the problem. I was quite confused since
> everything was installed in the right place. As you already mentioned,
> lintian doesn't like the egg-info directory and neither do I, so I wrote
> custom scripts which call 'python3 -m asciidoc "$@"'. It seems to be
> working according to autopkgtest and my own tests.
> I uploaded the new version to https://mentors.debian.net/package/asciidoc/

adding the used autopkgtest to the package at all would help to detect
failures like this reported one early by ci.d.n.
So please consider to extend the current autopkgtests within the
packaging.

Regards
Carsten

Bug#995421: rust-bumpalo: autopkgtest armhf regression: oom_instead_of_bump_pointer_overflow

[peter green]

It passes when run with only packages from testing.


no it doesn't, it's skipped due to unsatisfiable dependencies.
However manual testing shows that the underlying failure does
affect the version in testing, so this is not *really* a
regression it just looks like one to debci.



I copied some of the output at the bottom of this report. Looking at the
name of the test *and* the resources of our armhf worker (250GB RAM) I
wonder if the test is assuming stuff that's not true.


The failure seems to be related to the behavior of the memory allocator.
In particular if the allocator makes the initial small allocation
in the top half of the address space then the follow-up allocation will
be small enough that it could in-principle succeed. In particular it's
likely to suceed on machines big enough that they will run out of address
space before they run out of ram.

I have successfully reproduced the issue on systems with both 32-bit and
64-bit kernels.

The failure won't happen on arm64 or amd64 because those architectures
reserve the top half of the address space for the kernel.

The failure doesn't seem to happen on i386, I don't know why perhaps the
memory allocator behaves differently there.

Having read the code I am pretty sure this is just a borked test and not
an actual issue in the code, but I have opened an upstream bug report
asking them to check by analysis.

https://github.com/fitzgen/bumpalo/issues/128

Separately alloc_slice_fill_zero is failing on i386, that failure is a
result of a wrong assumption about alignment in the test, I have
fixed that and opened an upstream PR.

https://github.com/fitzgen/bumpalo/pull/129

If noone (either in upstream or Debian) responds with any objections or better
solutions I will likely disable the oom_instead_of_bump_pointer_overflow
test and apply the fix for. I may or may not update to the new upstream version
of rust-bumpalo at the same time (I have not yet checked what that would 
involve).

Bug#998125: libasound2-plugins: Config file for a52 plugin (60-a52-encoder.conf) produces no/garbled sound via optical digital out (S/PDIF)

[Jens Schmidt]

Package: libasound2-plugins
Version: 1.2.2-2
Severity: grave
Justification: renders package unusable

Dear Maintainer,

* What led up to the situation?
Fresh Debian 11 install.
I want to output 5.1 sound via toslink.
Used KDE settings to switch from analog output to digital out 5.1.
This produced no or garbled sound and Youtube videos would
play back way to fast without sound.
Then I switched to digital out stereo, this worked as expected but only
stereo.

I could trace back the error to the shipped config file for alsa's a52
plugin: 60-a52-encoder.conf.

When I replaced that file with a much simpler one (see below) 5.1
digital out worked as expedted.

I tried with onboard sound (PCH9) and dedicated card (Audigy Z) with the same 
result, the inlcuded a52 config file does not work.

== Start a52.conf
pcm.a52 {
  @args [CARD]
  @args.CARD {
type string
  }
  type rate
  slave {
pcm {
  type a52
  bitrate 448
  channels 6
  card $CARD
}
  rate 48000
  }
}
== End a52.conf

Therefore I assume the shipped config file with debian has an error somewhere. 
Please fix this.

Best reagards
Jens



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

Kernel: Linux 5.14.0-0.bpo.2-amd64 (SMP w/4 CPU threads)
Kernel taint flags: TAINT_UNSIGNED_MODULE
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 libasound2-plugins depends on:
ii  libasound2 1.2.4-1.1
ii  libavcodec-extra58 [libavcodec58]  7:4.3.2-0+deb11u2
ii  libavresample4 7:4.3.2-0+deb11u2
ii  libavutil567:4.3.2-0+deb11u2
ii  libc6  2.31-13+deb11u2
ii  libjack0 [libjack-0.125]   1:0.125.0-3+b1
ii  libpulse0  14.2-2
ii  libsamplerate0 0.2.1+ds0-1

libasound2-plugins recommends no packages.

libasound2-plugins suggests no packages.

-- no debconf information

Bug#998108: firefox freezes shortly after start

[Olivier Allard-Jacquin]

Hi,

same issue here:
- AMD64 install
- Debian testing + firefox from unstable


After 93.0-1+b1 install, firefox freeze on some web sites, specially 
when new tab open a new link.


According to "strace" command, this is look faulted tab open nvidia 
library, so maybe issue is linker to video acceleration.


According to upper Philipp Huebner's reply, downgrading to 93.0-1 from 
snapshot.debian.org has fix issue.


Finally, using latest firefox nightly version from 
https://www.mozilla.org/fr/firefox/channel/desktop/#nightly (today this 
is 95.0a1) also fix issue.


Best regards,
Olivier

Bug#998124: meson: gnome module missing install_dir fix for c_template

[Samuel Thibault]

Package: meson
Version: 0.60.0-1
Severity: serious
Justification: Makes gedit FTBFS

Hello,

In addition to the issue raised in #997936, we have this happening when
building the gedit package:

dh_auto_configure -- -Dgtk_doc=true
cd obj-x86_64-linux-gnu && LC_ALL=C.UTF-8 meson .. 
--wrap-mode=nodownload --buildtype=plain --prefix=/usr --sysconfdir=/etc 
--localstatedir=/var --libdir=lib/x86_64-linux-gnu -Dgtk_doc=true
Traceback (most recent call last):
  File "/usr/lib/python3/dist-packages/mesonbuild/mesonmain.py", line 138, in 
run
return options.run_func(options)
  File "/usr/lib/python3/dist-packages/mesonbuild/msetup.py", line 294, in run
app.generate()
  File "/usr/lib/python3/dist-packages/mesonbuild/msetup.py", line 185, in 
generate
self._generate(env)
  File "/usr/lib/python3/dist-packages/mesonbuild/msetup.py", line 229, in 
_generate
intr.run()
  File "/usr/lib/python3/dist-packages/mesonbuild/interpreter/interpreter.py", 
line 2484, in run
super().run()
  File 
"/usr/lib/python3/dist-packages/mesonbuild/interpreterbase/interpreterbase.py", 
line 150, in run
self.evaluate_codeblock(self.ast, start=1)
  File 
"/usr/lib/python3/dist-packages/mesonbuild/interpreterbase/interpreterbase.py", 
line 175, in evaluate_codeblock
raise e
  File 
"/usr/lib/python3/dist-packages/mesonbuild/interpreterbase/interpreterbase.py", 
line 168, in evaluate_codeblock
self.evaluate_statement(cur)
  File 
"/usr/lib/python3/dist-packages/mesonbuild/interpreterbase/interpreterbase.py", 
line 181, in evaluate_statement
return self.function_call(cur)
  File 
"/usr/lib/python3/dist-packages/mesonbuild/interpreterbase/interpreterbase.py", 
line 456, in function_call
res = func(node, func_args, kwargs)
  File 
"/usr/lib/python3/dist-packages/mesonbuild/interpreterbase/decorators.py", line 
713, in wrapped
return f(*wrapped_args, **wrapped_kwargs)
  File 
"/usr/lib/python3/dist-packages/mesonbuild/interpreterbase/decorators.py", line 
115, in wrapped
return f(*wrapped_args, **wrapped_kwargs)
  File 
"/usr/lib/python3/dist-packages/mesonbuild/interpreterbase/decorators.py", line 
276, in wrapper
return f(*nargs, **wrapped_kwargs)
  File "/usr/lib/python3/dist-packages/mesonbuild/interpreter/interpreter.py", 
line 1969, in func_subdir
self.evaluate_codeblock(codeblock)
  File 
"/usr/lib/python3/dist-packages/mesonbuild/interpreterbase/interpreterbase.py", 
line 175, in evaluate_codeblock
raise e
  File 
"/usr/lib/python3/dist-packages/mesonbuild/interpreterbase/interpreterbase.py", 
line 168, in evaluate_codeblock
self.evaluate_statement(cur)
  File 
"/usr/lib/python3/dist-packages/mesonbuild/interpreterbase/interpreterbase.py", 
line 181, in evaluate_statement
return self.function_call(cur)
  File 
"/usr/lib/python3/dist-packages/mesonbuild/interpreterbase/interpreterbase.py", 
line 456, in function_call
res = func(node, func_args, kwargs)
  File 
"/usr/lib/python3/dist-packages/mesonbuild/interpreterbase/decorators.py", line 
713, in wrapped
return f(*wrapped_args, **wrapped_kwargs)
  File 
"/usr/lib/python3/dist-packages/mesonbuild/interpreterbase/decorators.py", line 
115, in wrapped
return f(*wrapped_args, **wrapped_kwargs)
  File 
"/usr/lib/python3/dist-packages/mesonbuild/interpreterbase/decorators.py", line 
276, in wrapper
return f(*nargs, **wrapped_kwargs)
  File "/usr/lib/python3/dist-packages/mesonbuild/interpreter/interpreter.py", 
line 1969, in func_subdir
self.evaluate_codeblock(codeblock)
  File 
"/usr/lib/python3/dist-packages/mesonbuild/interpreterbase/interpreterbase.py", 
line 175, in evaluate_codeblock
raise e
  File 
"/usr/lib/python3/dist-packages/mesonbuild/interpreterbase/interpreterbase.py", 
line 168, in evaluate_codeblock
self.evaluate_statement(cur)
  File 
"/usr/lib/python3/dist-packages/mesonbuild/interpreterbase/interpreterbase.py", 
line 183, in evaluate_statement
self.assignment(cur)
  File 
"/usr/lib/python3/dist-packages/mesonbuild/interpreterbase/interpreterbase.py", 
line 568, in assignment
value = self.evaluate_statement(node.value)
  File 
"/usr/lib/python3/dist-packages/mesonbuild/interpreterbase/interpreterbase.py", 
line 185, in evaluate_statement
return self.method_call(cur)
  File 
"/usr/lib/python3/dist-packages/mesonbuild/interpreterbase/interpreterbase.py", 
line 484, in method_call
res = obj.method_call(method_name, args, kwargs)
  File 
"/usr/lib/python3/dist-packages/mesonbuild/interpreter/interpreterobjects.py", 
line 754, in method_call
ret = method(state, args, kwargs)
  File 
"/usr/lib/python3/dist-packages/mesonbuild/interpreterbase/decorators.py", line 
115, in wrapped
return f(*wrapped_args, **wrapped_kwargs)
  File "/usr/lib/python3/dist-packages/mesonbuild/modules/gnome.py", line 1459, 
in mkenums
c_target = self._make_mkenum_custom_target(state, c_sources,
  File "/usr/lib/python3/dist-packages/mesonbuild/modules/gnome.py", line 1596, 
in

Bug#984200: marked as done (libpdb-redo: ftbfs with GCC-11)

[Debian Bug Tracking System]

Your message dated Sat, 30 Oct 2021 18:00:13 +
with message-id 
and subject line Bug#984093: fixed in libcifpp 1.0.1-4
has caused the Debian Bug report #984093,
regarding libpdb-redo: ftbfs with GCC-11
to be marked as done.

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

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


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

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

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

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

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

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

  apt-get -t=experimental install g++ 

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

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

[...]
/usr/include/cif++/Cif++.hpp:461:50: error: ‘optional’ is not a member of ‘std’
  461 | struct ItemReference::item_value_as>
  |  ^~~~
/usr/include/cif++/Cif++.hpp:41:1: note: ‘std::optional’ is defined in header 
‘’; did you forget to ‘#include ’?
   40 | #include "cif++/CifUtils.hpp"
  +++ |+#include 
   41 | 
/usr/include/cif++/Cif++.hpp:461:59: error: template argument 1 is invalid
  461 | struct ItemReference::item_value_as>
  |   ^
/usr/include/cif++/Cif++.hpp:461:60: error: expected unqualified-id before ‘>’ 
token
  461 | struct ItemReference::item_value_as>
  |^~
In file included from /usr/include/cif++/Compound.hpp:35,
 from /usr/include/cif++/Structure.hpp:33,
 from include/pdb-redo/ClipperWrapper.hpp:30,
 from src/ClipperWrapper.cpp:29:
/usr/include/cif++/Cif++.hpp:461:50: error: ‘optional’ is not a member of ‘std’
  461 | struct ItemReference::item_value_as>
  |  ^~~~
/usr/include/cif++/Cif++.hpp:41:1: note: ‘std::optional’ is defined in header 
‘’; did you forget to ‘#include ’?
   40 | #include "cif++/CifUtils.hpp"
  +++ |+#include 
   41 | 
/usr/include/cif++/Cif++.hpp:461:59: error: template argument 1 is invalid
  461 | struct ItemReference::item_value_as>
  |   ^
/usr/include/cif++/Cif++.hpp:461:60: error: expected unqualified-id before ‘>’ 
token
  461 | struct ItemReference::item_value_as>
  |^~
In file included from src/BondMap.cpp:37:
/usr/include/cif++/Cif++.hpp:461:50: error: ‘optional’ is not a member of ‘std’
  461 | struct ItemReference::item_value_as>
  |  ^~~~
/usr/include/cif++/Cif++.hpp:41:1: note: ‘std::optional’ is defined in header 
‘’; did you forget to ‘#include ’?
   40 | #include "cif++/CifUtils.hpp"
  +++ |+#include 
   41 | 
/usr/include/cif++/Cif++.hpp:461:59: error: template argument 1 is invalid
  461 | struct ItemReference::item_value_as>
  |   ^
/usr/include/cif++/Cif++.hpp:461:60: error: expected unqualified-id before ‘>’ 
token
  461 | struct ItemReference::item_value_as>
  |

Bug#993324: marked as done (libgsl25: ABI breakage: removed symbol gsl_linalg_QR_TR_decomp)

[Debian Bug Tracking System]

Your message dated Sat, 30 Oct 2021 18:00:11 +
with message-id 
and subject line Bug#993324: fixed in gsl 2.7+dfsg-3
has caused the Debian Bug report #993324,
regarding libgsl25: ABI breakage: removed symbol gsl_linalg_QR_TR_decomp
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.)


-- 
993324: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=993324
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libgsl25
Version: 2.7+dfsg-2
Control: affects -1 libmath-gsl-perl
Severity: serious

gsl 2.7 broke libmath-gsl-perl on runtime, as seen in the autopkgtest 
regressions:

   not ok 7 - use Math::GSL::Matrix;
   
   #   Failed test 'use Math::GSL::Matrix;'
   #   at t/00-load.t line 14.
   # Tried to use 'Math::GSL::Matrix'.
   # Error:  Can't load 
'/usr/lib/x86_64-linux-gnu/perl5/5.32/auto/Math/GSL/Linalg/Linalg.so' for 
module Math::GSL::Linalg: 
/usr/lib/x86_64-linux-gnu/perl5/5.32/auto/Math/GSL/Linalg/Linalg.so: undefined 
symbol: gsl_linalg_QR_TR_decomp at 
/usr/lib/x86_64-linux-gnu/perl-base/DynaLoader.pm line 187.
   # � at /usr/lib/x86_64-linux-gnu/perl5/5.32/Math/GSL/Linalg.pm line 11.
   # Compilation failed in require at 
/usr/lib/x86_64-linux-gnu/perl5/5.32/Math/GSL/Matrix.pm line 1210.
   # BEGIN failed--compilation aborted at 
/usr/lib/x86_64-linux-gnu/perl5/5.32/Math/GSL/Matrix.pm line 1210.
   # Compilation failed in require at t/00-load.t line 14.
   # BEGIN failed--compilation aborted at t/00-load.t line 14.
   ok 8 - use Math::GSL::Poly;
   not ok 9 - use Math::GSL::MatrixComplex;

It seems that the 2.7 upload broke the ABI of libgsl25 by removing
the gsl_linalg_QR_TR_decomp symbol. src:gsl is currently blocked from
entering testing because of this regression in libmath-gsl-perl_0.42-1.

Looks like upstream Math-GSL-0.43 probably no longer references this
symbol, but it's not in Debian yet and I haven't built and verified that.

Clearly at least something must be done on the libgsl side. Not sure if
it needs to restore the symbol or bump its SONAME, or if just a Breaks
on older libmath-gsl-perl versions is enough. (See policy 8.6.2)

I've also filed the separate bug #993323 about libmath-gsl-perl failing to
build with GSL 2.7. That should be fixed just by upgrading it to 0.43.
-- 
Niko Tyni nt...@debian.org
--- End Message ---
--- Begin Message ---
Source: gsl
Source-Version: 2.7+dfsg-3
Done: Dirk Eddelbuettel 

We believe that the bug you reported is fixed in the latest version of
gsl, 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.
Dirk Eddelbuettel  (supplier of updated gsl package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sat, 23 Oct 2021 19:21:13 -0500
Source: gsl
Binary: gsl-bin libgsl-dbg libgsl-dev libgsl26 libgslcblas0
Architecture: source amd64
Version: 2.7+dfsg-3
Distribution: experimental
Urgency: medium
Maintainer: Dirk Eddelbuettel 
Changed-By: Dirk Eddelbuettel 
Description:
 gsl-bin- GNU Scientific Library (GSL) -- binary package
 libgsl-dbg - GNU Scientific Library (GSL) -- debug symbols package
 libgsl-dev - GNU Scientific Library (GSL) -- development package
 libgsl26   - GNU Scientific Library (GSL) -- library package
 libgslcblas0 - GNU Scientific Library (GSL) -- blas library package
Closes: 993324
Changes:
 gsl (2.7+dfsg-3) experimental; urgency=medium
 .
   * configure.ac: Correct the GSL_AGE value to 0 to force a new sonumber
 (thanks to Sebastian Ramacher for the help)(Closes: 
#993324)
 .
   * debian/*: Renamed files reflecting so25 to so26, update to 2.7
   * debian/libgslcblas0.shlibs: Increase minimum version to 2.7
Checksums-Sha1:
 8de3f6fa872f1e23ee3d45c820b75533fc30c3f9 2018 gsl_2.7+dfsg-3.dsc
 126d2164fef4915cb2567634a23da0d3cdbc01a5 6911262 gsl_2.7+dfsg.orig.tar.gz
 7b51a8c0c9ab91712d5de05b764ad5c97d5f4d18 20652 gsl_2.7+dfsg-3.debian.tar.xz
 beff59c5ecc1ba5610197064513f2a7506120d96 29580 gsl-bin_2.7+dfsg-3_amd64.deb
 c642ca9572a82b1b3b34d6d7ab26dbf6acc8b686 6617 gsl_2.7+dfsg-3_amd64.buildinfo
 0cf320087c3b7e024dbf0e3aa114d215d2ecb0f7 3460492 
libgsl-dbg_2.7+d

Bug#984369: marked as done (tortoize: ftbfs with GCC-11)

[Debian Bug Tracking System]

Your message dated Sat, 30 Oct 2021 18:00:13 +
with message-id 
and subject line Bug#984093: fixed in libcifpp 1.0.1-4
has caused the Debian Bug report #984093,
regarding tortoize: ftbfs with GCC-11
to be marked as done.

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

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


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

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

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

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

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

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

  apt-get -t=experimental install g++ 

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

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

[...]
checking for sys/types.h... yes
checking for sys/stat.h... yes
checking for stdlib.h... yes
checking for string.h... yes
checking for memory.h... yes
checking for strings.h... yes
checking for inttypes.h... yes
checking for stdint.h... yes
checking for unistd.h... yes
checking filesystem usability... yes
checking filesystem presence... yes
checking for filesystem... yes
checking for boostlib >= 1.65.1 (106501)... yes
checking whether the Boost::IOStreams library is available... yes
checking for exit in -lboost_iostreams... yes
checking whether the Boost::Program_Options library is available... yes
checking for exit in -lboost_program_options... yes
checking whether the Boost::Date_Time library is available... yes
checking for exit in -lboost_date_time... yes
checking for pkg-config... /usr/bin/pkg-config
checking pkg-config is at least version 0.9.0... yes
checking for pkg-config... /usr/bin/pkg-config
checking for CIFPP... yes
checking for ZEEP... yes
configure: creating ./config.status
config.status: creating GNUmakefile
config.status: creating src/config.hpp
make[1]: Leaving directory '/<>'
   dh_auto_build
make -j4
make[1]: Entering directory '/<>'
mkdir -p obj
/usr/bin/mrc --header > src/mrsrc.hpp
/usr/bin/mrc -o obj/tortoize_rsrc.o rsrc/rama-data.bin rsrc/torsion-data.bin
>> src/tortoize.cpp
In file included from src/tortoize.cpp:42:
/usr/include/cif++/Cif++.hpp:461:50: error: ‘optional’ is not a member of ‘std’
  461 | struct ItemReference::item_value_as>
  |  ^~~~
/usr/include/cif++/Cif++.hpp:34:1: note: ‘std::optional’ is defined in header 
‘’; did you forget to ‘#include ’?
   33 | #include 
  +++ |+#include 
   34 | #include 
/usr/include/cif++/Cif++.hpp:461:59: error: template argument 1 is invalid
  461 | struct ItemReference::item_value_as>
  |   ^
/usr/include/cif++/Cif++.hpp:461:60: error: expected unqualified-id before ‘>’ 
token
  461 | struct ItemReference::item_value_as>
  |^~
In file included from /usr/include/zeep/json/element.hpp:15,
 from src/tortoize.cpp:45:
/usr/include/zeep/json/to_element.hpp:133:40: error: ‘optional’ in namespace 
‘std’ does not name a template type
  133 | void to_element(element& j, const std::optional& v)
  |^~~~
/usr/include/zeep/json/to_element.hpp:14:1: note: ‘std::optional’ is defined in 
header ‘’; did you forget to ‘#include ’

Bug#984042: marked as done (dssp: ftbfs with GCC-11)

[Debian Bug Tracking System]

Your message dated Sat, 30 Oct 2021 18:00:13 +
with message-id 
and subject line Bug#984093: fixed in libcifpp 1.0.1-4
has caused the Debian Bug report #984093,
regarding dssp: ftbfs with GCC-11
to be marked as done.

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

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


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

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

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

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

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

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

  apt-get -t=experimental install g++ 

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

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

[...]
checking for mrc... no
configure: WARNING: The mrc application was not found, not using resources.
checking build system type... x86_64-pc-linux-gnu
checking host system type... x86_64-pc-linux-gnu
checking for gcc... gcc
checking whether we are using the GNU C compiler... yes
checking whether gcc accepts -g... yes
checking for gcc option to accept ISO C89... none needed
checking for a sed that does not truncate output... /bin/sed
checking how to run the C preprocessor... gcc -E
checking for grep that handles long lines and -e... /bin/grep
checking for egrep... /bin/grep -E
checking whether gcc is Clang... no
checking whether pthreads work with -pthread... yes
checking for joinable pthread attribute... PTHREAD_CREATE_JOINABLE
checking whether more special flags are required for pthreads... no
checking for PTHREAD_PRIO_INHERIT... yes
checking how to run the C++ preprocessor... g++ -std=c++17 -E
checking for ANSI C header files... yes
checking for sys/types.h... yes
checking for sys/stat.h... yes
checking for stdlib.h... yes
checking for string.h... yes
checking for memory.h... yes
checking for strings.h... yes
checking for inttypes.h... yes
checking for stdint.h... yes
checking for unistd.h... yes
checking filesystem usability... yes
checking filesystem presence... yes
checking for filesystem... yes
checking for boostlib >= 1.65.1 (106501)... yes
checking whether the Boost::IOStreams library is available... yes
checking for exit in -lboost_iostreams... yes
checking whether the Boost::Program_Options library is available... yes
checking for exit in -lboost_program_options... yes
checking for pkg-config... /usr/bin/pkg-config
checking pkg-config is at least version 0.9.0... yes
checking for pkg-config... /usr/bin/pkg-config
checking for libcifpp ... yes
configure: creating ./config.status
config.status: creating GNUmakefile
config.status: creating src/config.hpp
make[1]: Leaving directory '/<>'
   dh_auto_build
make -j4
make[1]: Entering directory '/<>'
mkdir -p obj
>> src/dssp.cpp
In file included from /usr/include/cif++/Compound.hpp:35,
 from /usr/include/cif++/Structure.hpp:33,
 from src/dssp.cpp:38:
/usr/include/cif++/Cif++.hpp:461:50: error: ‘optional’ is not a member of ‘std’
  461 | struct ItemReference::item_value_as>
  |  ^~~~
/usr/include/cif++/Cif++.hpp:41:1: note: ‘std::optional’ is defined in header 
‘’; did you forget to ‘#include ’?
   40 | #include "cif++/CifUtils.hpp"
  +++ |+#include 
   41 | 
/usr/include/cif++/Cif++.hpp:461:59: error: template 

Bug#984093: marked as done (libcifpp: ftbfs with GCC-11)

[Debian Bug Tracking System]

Your message dated Sat, 30 Oct 2021 18:00:13 +
with message-id 
and subject line Bug#984093: fixed in libcifpp 1.0.1-4
has caused the Debian Bug report #984093,
regarding libcifpp: ftbfs with GCC-11
to be marked as done.

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

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


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

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

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

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

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

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

  apt-get -t=experimental install g++ 

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

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

[...]
>> src/AtomType.cpp
>> src/Cif2PDB.cpp
>> src/Cif++.cpp
>> src/CifParser.cpp
In file included from src/AtomType.cpp:30:
include/cif++/Cif++.hpp:461:50: error: ‘optional’ is not a member of ‘std’
  461 | struct ItemReference::item_value_as>
  |  ^~~~
include/cif++/Cif++.hpp:41:1: note: ‘std::optional’ is defined in header 
‘’; did you forget to ‘#include ’?
   40 | #include "cif++/CifUtils.hpp"
  +++ |+#include 
   41 | 
include/cif++/Cif++.hpp:461:59: error: template argument 1 is invalid
  461 | struct ItemReference::item_value_as>
  |   ^
include/cif++/Cif++.hpp:461:60: error: expected unqualified-id before ‘>’ token
  461 | struct ItemReference::item_value_as>
  |^~
In file included from src/CifParser.cpp:31:
include/cif++/Cif++.hpp:461:50: error: ‘optional’ is not a member of ‘std’
  461 | struct ItemReference::item_value_as>
  |  ^~~~
include/cif++/Cif++.hpp:41:1: note: ‘std::optional’ is defined in header 
‘’; did you forget to ‘#include ’?
   40 | #include "cif++/CifUtils.hpp"
  +++ |+#include 
   41 | 
include/cif++/Cif++.hpp:461:59: error: template argument 1 is invalid
  461 | struct ItemReference::item_value_as>
  |   ^
include/cif++/Cif++.hpp:461:60: error: expected unqualified-id before ‘>’ token
  461 | struct ItemReference::item_value_as>
  |^~
make[1]: *** [GNUmakefile:188: obj/AtomType.lo] Error 1
make[1]: *** Waiting for unfinished jobs
In file included from src/Cif++.cpp:45:
include/cif++/Cif++.hpp:461:50: error: ‘optional’ is not a member of ‘std’
  461 | struct ItemReference::item_value_as>
  |  ^~~~
include/cif++/Cif++.hpp:41:1: note: ‘std::optional’ is defined in header 
‘’; did you forget to ‘#include ’?
   40 | #include "cif++/CifUtils.hpp"
  +++ |+#include 
   41 | 
include/cif++/Cif++.hpp:461:59: error: template argument 1 is invalid
  461 | struct ItemReference::item_value_as>
  |   ^
include/cif++/Cif++.hpp:461:60: error: expected unqualified-id before ‘>’ token
  461 | struct ItemReference::item_value_as>
  |^~
In fil

Bug#974793: marked as done (oclgrind: Please upgrade to llvm-toolchain-11)

[Debian Bug Tracking System]

Your message dated Sat, 30 Oct 2021 18:00:15 +
with message-id 
and subject line Bug#974793: fixed in oclgrind 21.10-1
has caused the Debian Bug report #974793,
regarding oclgrind: Please upgrade to llvm-toolchain-11
to be marked as done.

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

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


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

Dear Maintainer,

As part of the effort to limit the number of llvm packages in the 
archive, please upgrade to -11.

Thanks,
Sylvestre
--- End Message ---
--- Begin Message ---
Source: oclgrind
Source-Version: 21.10-1
Done: James Price 

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

Debian distribution maintenance software
pp.
James Price  (supplier of updated oclgrind package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sat, 23 Oct 2021 13:08:28 +
Source: oclgrind
Binary: liboclgrind-21.10 liboclgrind-21.10-dbgsym liboclgrind-dev oclgrind 
oclgrind-dbgsym
Architecture: source amd64
Version: 21.10-1
Distribution: unstable
Urgency: medium
Maintainer: Debian OpenCL Maintainers 
Changed-By: James Price 
Description:
 liboclgrind-21.10 - core library for Oclgrind
 liboclgrind-dev - development files for Oclgrind
 oclgrind   - OpenCL device simulator
Closes: 974793
Changes:
 oclgrind (21.10-1) unstable; urgency=medium
 .
   * New upstream release
   * Refresh patches
   * Switch to LLVM/Clang 13 (Closes: #974793)
   * Bump Standards-Version to 4.6.0. No changes needed.
Checksums-Sha1:
 940f6a11a6a517139d028551a3e1f7a7a4ef8e64 2236 oclgrind_21.10-1.dsc
 f348b597fc131f1658c768fa894b31aedbfa4232 219855 oclgrind_21.10.orig.tar.gz
 0a26fc20a74073f1d16e43b8e934ca8fae6da3f7 7552 oclgrind_21.10-1.debian.tar.xz
 21f87a3a3f228cf37ffa29e869a11696451618ce 6900624 
liboclgrind-21.10-dbgsym_21.10-1_amd64.deb
 5f073adc4c2591fc4ea088c1ab2502338a310bbf 11793208 
liboclgrind-21.10_21.10-1_amd64.deb
 3904823045f198eb40e705d45b5e16e8b077ebd6 14024 
liboclgrind-dev_21.10-1_amd64.deb
 55e366d3f1e970ae09dd4a882a79223abfeacabb 1624052 
oclgrind-dbgsym_21.10-1_amd64.deb
 36bc270c60db2f0ffd3062d668587cf4ea05c8e6 9411 oclgrind_21.10-1_amd64.buildinfo
 b9ef89a0c61462e1164cba756fb09fed1ea44b3f 123036 oclgrind_21.10-1_amd64.deb
Checksums-Sha256:
 e488e0d3e51301716e487f736a1d600ad98593e072097afe4cad667a4e50a9c3 2236 
oclgrind_21.10-1.dsc
 b40ea81fcf64e9012d63c3128640fde9785ef4f304f9f876f53496595b8e62cc 219855 
oclgrind_21.10.orig.tar.gz
 bfe0dab7f6cbdbdf7b6330fce7499d6cc85e9e118373c141a0907f22e709a968 7552 
oclgrind_21.10-1.debian.tar.xz
 5a9421447c7514392634bb39b048b13e7837b2d6e567abfb282206bc734f382c 6900624 
liboclgrind-21.10-dbgsym_21.10-1_amd64.deb
 83f6f30203c625272f38625d829b482c02ab0d81048c4c3af7a062af2b4d2557 11793208 
liboclgrind-21.10_21.10-1_amd64.deb
 8c77d31efb0970ef8ee4c30123292b4f54df81571e5bf115a5541156cb2499ae 14024 
liboclgrind-dev_21.10-1_amd64.deb
 7bc85e9bb4ca8881f2a66ab345b8bac2c542531a0ca458fb68212287b025be96 1624052 
oclgrind-dbgsym_21.10-1_amd64.deb
 31dfc7580bf7c643d93c1308039aa76d894472b7f107ca2c690ee73beca482f6 9411 
oclgrind_21.10-1_amd64.buildinfo
 4f42d1ea59adad25e19fe382de45a17b2b36470d788ec4aae1f6c7654cfedd5b 123036 
oclgrind_21.10-1_amd64.deb
Files:
 4515c58f144babb573a2104166946bfd 2236 devel optional oclgrind_21.10-1.dsc
 1ca412b713c0980ba414014184af66f4 219855 devel optional 
oclgrind_21.10.orig.tar.gz
 9d3585be5bf6555872456b1529646859 7552 devel optional 
oclgrind_21.10-1.debian.tar.xz
 b1d9b666dce80a409d7d3933d9c5f72e 6900624 debug optional 
liboclgrind-21.10-dbgsym_21.10-1_amd64.deb
 4e35d34d868191f8874ddf1951f6aeda 11793208 libs optional 
liboclgrind-21.10_21.10-1_amd64.deb
 df77fb26ae7f95899eb0f1e45ceef7b1 14024 libdevel optional 
liboclgrind-dev_21.10-1_amd64.deb
 e994bf09ae3fc70aeb2ff1ea48468b9f 1624052 debug optional 
oclgrind-dbgsym_21.10-1_amd64.deb
 ff64473452927f89fbdc2e94520a2e57 9411 devel optional 
oclgrind_21.10-1_amd64.buildinfo
 c94e198544eb9ef01b573402447759ad 123036 dev

Bug#974813: marked as done (oclgrind: Please upgrade to llvm-toolchain-11)

[Debian Bug Tracking System]

Your message dated Sat, 30 Oct 2021 18:00:15 +
with message-id 
and subject line Bug#974793: fixed in oclgrind 21.10-1
has caused the Debian Bug report #974793,
regarding oclgrind: Please upgrade to llvm-toolchain-11
to be marked as done.

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

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


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

Dear Maintainer,

As part of the effort to limit the number of llvm packages in the
archive, please upgrade to -11.

Thanks,
Sylvestre
--- End Message ---
--- Begin Message ---
Source: oclgrind
Source-Version: 21.10-1
Done: James Price 

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

Debian distribution maintenance software
pp.
James Price  (supplier of updated oclgrind package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sat, 23 Oct 2021 13:08:28 +
Source: oclgrind
Binary: liboclgrind-21.10 liboclgrind-21.10-dbgsym liboclgrind-dev oclgrind 
oclgrind-dbgsym
Architecture: source amd64
Version: 21.10-1
Distribution: unstable
Urgency: medium
Maintainer: Debian OpenCL Maintainers 
Changed-By: James Price 
Description:
 liboclgrind-21.10 - core library for Oclgrind
 liboclgrind-dev - development files for Oclgrind
 oclgrind   - OpenCL device simulator
Closes: 974793
Changes:
 oclgrind (21.10-1) unstable; urgency=medium
 .
   * New upstream release
   * Refresh patches
   * Switch to LLVM/Clang 13 (Closes: #974793)
   * Bump Standards-Version to 4.6.0. No changes needed.
Checksums-Sha1:
 940f6a11a6a517139d028551a3e1f7a7a4ef8e64 2236 oclgrind_21.10-1.dsc
 f348b597fc131f1658c768fa894b31aedbfa4232 219855 oclgrind_21.10.orig.tar.gz
 0a26fc20a74073f1d16e43b8e934ca8fae6da3f7 7552 oclgrind_21.10-1.debian.tar.xz
 21f87a3a3f228cf37ffa29e869a11696451618ce 6900624 
liboclgrind-21.10-dbgsym_21.10-1_amd64.deb
 5f073adc4c2591fc4ea088c1ab2502338a310bbf 11793208 
liboclgrind-21.10_21.10-1_amd64.deb
 3904823045f198eb40e705d45b5e16e8b077ebd6 14024 
liboclgrind-dev_21.10-1_amd64.deb
 55e366d3f1e970ae09dd4a882a79223abfeacabb 1624052 
oclgrind-dbgsym_21.10-1_amd64.deb
 36bc270c60db2f0ffd3062d668587cf4ea05c8e6 9411 oclgrind_21.10-1_amd64.buildinfo
 b9ef89a0c61462e1164cba756fb09fed1ea44b3f 123036 oclgrind_21.10-1_amd64.deb
Checksums-Sha256:
 e488e0d3e51301716e487f736a1d600ad98593e072097afe4cad667a4e50a9c3 2236 
oclgrind_21.10-1.dsc
 b40ea81fcf64e9012d63c3128640fde9785ef4f304f9f876f53496595b8e62cc 219855 
oclgrind_21.10.orig.tar.gz
 bfe0dab7f6cbdbdf7b6330fce7499d6cc85e9e118373c141a0907f22e709a968 7552 
oclgrind_21.10-1.debian.tar.xz
 5a9421447c7514392634bb39b048b13e7837b2d6e567abfb282206bc734f382c 6900624 
liboclgrind-21.10-dbgsym_21.10-1_amd64.deb
 83f6f30203c625272f38625d829b482c02ab0d81048c4c3af7a062af2b4d2557 11793208 
liboclgrind-21.10_21.10-1_amd64.deb
 8c77d31efb0970ef8ee4c30123292b4f54df81571e5bf115a5541156cb2499ae 14024 
liboclgrind-dev_21.10-1_amd64.deb
 7bc85e9bb4ca8881f2a66ab345b8bac2c542531a0ca458fb68212287b025be96 1624052 
oclgrind-dbgsym_21.10-1_amd64.deb
 31dfc7580bf7c643d93c1308039aa76d894472b7f107ca2c690ee73beca482f6 9411 
oclgrind_21.10-1_amd64.buildinfo
 4f42d1ea59adad25e19fe382de45a17b2b36470d788ec4aae1f6c7654cfedd5b 123036 
oclgrind_21.10-1_amd64.deb
Files:
 4515c58f144babb573a2104166946bfd 2236 devel optional oclgrind_21.10-1.dsc
 1ca412b713c0980ba414014184af66f4 219855 devel optional 
oclgrind_21.10.orig.tar.gz
 9d3585be5bf6555872456b1529646859 7552 devel optional 
oclgrind_21.10-1.debian.tar.xz
 b1d9b666dce80a409d7d3933d9c5f72e 6900624 debug optional 
liboclgrind-21.10-dbgsym_21.10-1_amd64.deb
 4e35d34d868191f8874ddf1951f6aeda 11793208 libs optional 
liboclgrind-21.10_21.10-1_amd64.deb
 df77fb26ae7f95899eb0f1e45ceef7b1 14024 libdevel optional 
liboclgrind-dev_21.10-1_amd64.deb
 e994bf09ae3fc70aeb2ff1ea48468b9f 1624052 debug optional 
oclgrind-dbgsym_21.10-1_amd64.deb
 ff64473452927f89fbdc2e94520a2e57 9411 devel optional 
oclgrind_21.10-1_amd64.buildinfo
 c94e198544eb9ef01b573402447759ad 123036 deve

Bug#984157: closed by Debian FTP Masters (reply to bott...@debian.org (A. Maitland Bottoms)) (Bug#984157: fixed in uhd 3.15.0.0-5)

[Adrian Bunk]

Control: retitle -1 libuhd-dev does not support C++20
Control: severity -1 normal

On Fri, Oct 29, 2021 at 10:32:07PM +0300, Adrian Bunk wrote:
> On Fri, Oct 22, 2021 at 06:06:06AM +, Debian Bug Tracking System wrote:
> >...
> > /usr/include/uhd/property_tree.ipp:26:50: error: expected ‘)’ before ‘mode’
> >26 | property_impl(property_tree::coerce_mode_t mode) : 
> > _coerce_mode(mode)
> >   | ~^
> >   |  )
> > /usr/include/uhd/property_tree.ipp:33:5: error: template-id not allowed for 
> > destructor
> >33 | ~property_impl(void)
> >   | ^
> >...
> 
> This part appears to still need fixing:
> https://buildd.debian.org/status/logs.php?pkg=gnss-sdr&ver=0.0.15-1%2Bb1

After looking at [1] the remaining problem appears to have been 
partially the fault of gnss-sdr by requesting a C++ version even
higher than the default.

cu
Adrian

[1] 
https://salsa.debian.org/debian-hamradio-team/gnss-sdr/-/commit/04063e534f6decf743e05ec712c9b3e3f803fae4

Processed: Re: Bug#984157: closed by Debian FTP Masters (reply to bott...@debian.org (A. Maitland Bottoms)) (Bug#984157: fixed in uhd 3.15.0.0-5)

[Debian Bug Tracking System]

Processing control commands:

> retitle -1 libuhd-dev does not support C++20
Bug #984157 [src:uhd] gnss-sdr: ftbfs with GCC-11
Changed Bug title to 'libuhd-dev does not support C++20' from 'gnss-sdr: ftbfs 
with GCC-11'.
> severity -1 normal
Bug #984157 [src:uhd] libuhd-dev does not support C++20
Severity set to 'normal' from 'serious'

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

Bug#913159: marked as done (task-kannada-desktop: uninstallable on mips and mipsel)

[Debian Bug Tracking System]

Your message dated Sat, 30 Oct 2021 18:14:21 +0200
with message-id <20211030181421.dca8b82f05e51092b9950...@mailbox.org>
and subject line Re: Bug#913159: task-kannada-desktop: uninstallable on mips 
and mipsel
has caused the Debian Bug report #913159,
regarding task-kannada-desktop: uninstallable on mips and mipsel
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.)


-- 
913159: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=913159
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
package: task-kannada-desktop
version: 3.47
severity: serious

Hi,

task-kannada-desktop depends on 'firefox-esr-l10n-kn | firefox-l10n-kn', which
is not installable on mips and mipsel, because the latest firefox doesn't
build there (yet).

Please move this dependency to recommends, as is done with (most) other
language tasks.

Thanks,

Ivo
--- End Message ---
--- Begin Message ---
Hi,

Holger Wansing  wrote (Sat, 9 Feb 2019 16:15:58 +0100):
> 
> With yesterday's upload of tasksel, this has been fixed for Buster.
> Tagging accordingly.
> 
> Should we leave this bug open for Stretch?

This is long over; closing this bug.

Holger


-- 
Holger Wansing 
PGP-Fingerprint: 496A C6E8 1442 4B34 8508  3529 59F1 87CA 156E B076--- End Message ---

Processed: Re: Bug#997359: Inkscape crashes when running as batch without X11

[Debian Bug Tracking System]

Processing control commands:

> forwarded -1 https://gitlab.com/inkscape/inkscape/-/issues/2899
Bug #997359 [inkscape] Inkscape crashes when running as batch without X11
Set Bug forwarded-to-address to 
'https://gitlab.com/inkscape/inkscape/-/issues/2899'.

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

Bug#997359: Inkscape crashes when running as batch without X11

[Mattia Rizzolo]

Control: forwarded -1 https://gitlab.com/inkscape/inkscape/-/issues/2899

On Sun, Oct 24, 2021 at 06:57:14PM +0200, Ole Streicher wrote:
> On 24.10.21 18:29, Mattia Rizzolo wrote:
> > Since you managed to reproduce it and all, could you perhaps consider
> > forwarding it yourself on https://gitlab.com/inkscape/inbox ?
> 
> I would prefer if you could do it. I am not very familar with inkscape, and
> the icon creation here is almost the only case where I use it.
> 
> You did not use the "--batch-process" option. If you add this, you get the
> crash. From the man page, this option is mandatory for batch processing.

Oh!

Indeed, with that I could reliably reproduce it!  Sent upstream.

Thank you!

-- 
regards,
Mattia Rizzolo

GPG Key: 66AE 2B4A FCCF 3F52 DA18  4D18 4B04 3FCD B944 4540  .''`.
More about me:  https://mapreri.org : :'  :
Launchpad user: https://launchpad.net/~mapreri  `. `'`
Debian QA page: https://qa.debian.org/developer.php?login=mattia  `-


signature.asc
Description: PGP signature

Bug#998108: firefox freezes shortly after start

[Philipp Huebner]

Hi,

I am affected by the same problem.

After downgrading to firefox=93.0-1 from snapshot.debian.org the problem
is gone.

Regards,
-- 
 .''`.   Philipp Huebner 
: :'  :  pgp fp: 6719 25C5 B8CD E74A 5225  3DF9 E5CA 8C49 25E4 205F
`. `'`
  `-


OpenPGP_signature
Description: OpenPGP digital signature

Processed: forwarded 997486

[Debian Bug Tracking System]

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

> forwarded 997486 https://github.com/pytroll/pycoast/issues/57
Bug #997486 [src:pycoast] pycoast: FTBFS: dh_auto_test: error: pybuild --test 
--test-pytest -i python{version} -p 3.9 returned exit code 13
Set Bug forwarded-to-address to 'https://github.com/pytroll/pycoast/issues/57'.
> --
Stopping processing here.

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

Bug#997119: marked as done (symfony: FTBFS: tests failed variable (T_VARIABLE))

[Debian Bug Tracking System]

Your message dated Sat, 30 Oct 2021 14:50:32 +
with message-id 
and subject line Bug#997119: fixed in php-psr-link 1.1.0+really1.0.0-1
has caused the Debian Bug report #997119,
regarding symfony: FTBFS: tests failed variable (T_VARIABLE)
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.)


-- 
997119: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997119
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: symfony
Version: 4.4.19+dfsg-2
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs

Hi,

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


Relevant part (hopefully):
> There were 2 errors:
> 
> 1) 
> Symfony\Bundle\FrameworkBundle\Tests\Controller\AbstractControllerTest::testAddLink
> ParseError: syntax error, unexpected '|', expecting variable (T_VARIABLE)
> 
> /usr/share/php/Psr/Link/EvolvableLinkInterface.php:27
> /<>/src/Symfony/Component/ErrorHandler/DebugClassLoader.php:350
> /<>/src/Symfony/Component/WebLink/Link.php:16
> /<>/src/Symfony/Component/WebLink/autoload.php:26
> /<>/src/Symfony/Component/ErrorHandler/DebugClassLoader.php:350
> /<>/src/Symfony/Bundle/FrameworkBundle/Tests/Controller/ControllerTraitTest.php:550
> 
> 2) Symfony\Bundle\FrameworkBundle\Tests\Controller\ControllerTest::testAddLink
> ParseError: syntax error, unexpected '|', expecting variable (T_VARIABLE)
> 
> /usr/share/php/Psr/Link/EvolvableLinkInterface.php:27
> /<>/src/Symfony/Component/ErrorHandler/DebugClassLoader.php:350
> /<>/src/Symfony/Component/WebLink/Link.php:16
> /<>/src/Symfony/Component/WebLink/autoload.php:26
> /<>/src/Symfony/Component/ErrorHandler/DebugClassLoader.php:350
> /<>/src/Symfony/Bundle/FrameworkBundle/Tests/Controller/ControllerTraitTest.php:550


The full build log is available from:
http://qa-logs.debian.net/2021/10/23/symfony_4.4.19+dfsg-2_unstable.log

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

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

If you fail to reproduce this, please provide a build log and diff it with mine
so that we can identify if something relevant changed in the meantime.
--- End Message ---
--- Begin Message ---
Source: php-psr-link
Source-Version: 1.1.0+really1.0.0-1
Done: David Prévot 

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

Debian distribution maintenance software
pp.
David Prévot  (supplier of updated php-psr-link package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sat, 30 Oct 2021 10:24:28 -0400
Source: php-psr-link
Architecture: source
Version: 1.1.0+really1.0.0-1
Distribution: unstable
Urgency: medium
Maintainer: Debian PHP PEAR Maintainers 
Changed-By: David Prévot 
Closes: 997119
Changes:
 php-psr-link (1.1.0+really1.0.0-1) unstable; urgency=medium
 .
   * Fix d/watch after hosting change
   * Track 1.0 to stay compatible with PHP 7 (Closes: #997119)
Checksums-Sha1:
 10a5662c9a5d663a585d75568db1bc22abed6a7d 1760 
php-psr-link_1.1.0+really1.0.0-1.dsc
 95de39f4807da44c0e46cfa2304df8a76386d03c 2984 
php-psr-link_1.1.0+really1.0.0.orig.tar.gz
 c74a5c04a84e0b84f0b1b66792068387518ef57f 2628 
php-psr-link_1.1.0+really1.0.0-1.debian.tar.xz
 47e9b2d01e0fc25a92bd9865aa1b4d652556fc1d 6281 
php-psr-link_1.1.0+really1.0.0-1_amd64.buildinfo
Checksums-Sha256:
 1430437c6ed5b852ee8c3ab4dcd7a5960fb71c56c6f356fbe1955a94e24447e0 1760 
php-psr-link_1.1.0+really1.0.0-1.dsc
 14258c19682d1118b46c369eddbda2473517affca4cc64a030a7dd85ad50387b 2984 
php-psr-link_1.1.0+really1.0.0.orig.tar.gz
 885b79f8b1c4f404a13fc19485bab2dce163eb4e23aaa2d7c286877642ac1ab4 2628 
php-psr-link_1.1.0+really1.0.0-1.debian.tar.xz
 25bc097926f9b4647337cd2a3964d8bb19d4f78c4bbe26b2ce4e264b0c1d335b 6281 
php-psr-link_1.1.0+really1.0.0-1_amd64.buildinfo
Files:
 3db40bca51c9b6d4872f2561b29b34a4 1760 php optional 
php-psr-link_1.1.0+really1.0.0-1.dsc
 4ae4a6c0f

Processed: limit source to php-psr-link, tagging 997119

[Debian Bug Tracking System]

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

> limit source php-psr-link
Limiting to bugs with field 'source' containing at least one of 'php-psr-link'
Limit currently set to 'source':'php-psr-link'

> tags 997119 + pending
Bug #997119 [php-psr-link] symfony: FTBFS: tests failed variable (T_VARIABLE)
Added tag(s) pending.
> thanks
Stopping processing here.

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

Processed: reassign 997119 to php-psr-link, affects 997119

[Debian Bug Tracking System]

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

> reassign 997119 php-psr-link 1.1.0-1
Bug #997119 [src:symfony] symfony: FTBFS: tests failed variable (T_VARIABLE)
Bug reassigned from package 'src:symfony' to 'php-psr-link'.
No longer marked as found in versions symfony/4.4.19+dfsg-2.
Ignoring request to alter fixed versions of bug #997119 to the same values 
previously set
Bug #997119 [php-psr-link] symfony: FTBFS: tests failed variable (T_VARIABLE)
Marked as found in versions php-psr-link/1.1.0-1.
> affects 997119 symfony
Bug #997119 [php-psr-link] symfony: FTBFS: tests failed variable (T_VARIABLE)
Added indication that 997119 affects symfony
> thanks
Stopping processing here.

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

Processed: your mail

[Debian Bug Tracking System]

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

> forwarded 997933 https://github.com/OfflineIMAP/offlineimap/issues/706
Bug #997933 [offlineimap3] offlineimap3: 'int' object is not subscriptable when 
connecting to outlook.office365.com
Set Bug forwarded-to-address to 
'https://github.com/OfflineIMAP/offlineimap/issues/706'.
> --
Stopping processing here.

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

Bug#998114: Missing egg info directory prevents asciidoc cli tools from running

[Jakob Haufe]

Source: asciidoc
Version: 10.0.1-1
Severity: grave
Justification: Causes builds of packages using asciidoc to build documentation 
to fail
Tags: patch
X-Debbugs-Cc: su...@debian.org

/usr/bin/asciidoc and /usr/bin/a2x rely on python distribution info to
locate the entry point. These files are deleted by d/rules, however, so
the CLI tools are unable to run:

$ asciidoc
Traceback (most recent call last):
  File "/usr/bin/asciidoc", line 33, in 
sys.exit(load_entry_point('asciidoc==10.0.1', 'console_scripts', 
'asciidoc')())
  File "/usr/bin/asciidoc", line 22, in importlib_load_entry_point
for entry_point in distribution(dist_name).entry_points
  File "/usr/lib/python3.9/importlib/metadata.py", line 524, in distribution
return Distribution.from_name(distribution_name)
  File "/usr/lib/python3.9/importlib/metadata.py", line 187, in from_name
raise PackageNotFoundError(name)
importlib.metadata.PackageNotFoundError: asciidoc

I did a local rebuild with the attached patch applied which resulted in
a working asciidoc CLI tool.

Given the package-contains-python-dot-directory lintian tag it results
in, I am unsure if that's the correct fix as I'm no python expert.

-- 
ceterum censeo microsoftem esse delendam.
diff -Nru asciidoc-10.0.1/debian/rules asciidoc-10.0.1/debian/rules
--- asciidoc-10.0.1/debian/rules	2021-10-29 16:29:00.0 +
+++ asciidoc-10.0.1/debian/rules	2021-10-30 13:00:52.0 +
@@ -11,7 +11,6 @@
 	mv debian/asciidoc-tests/usr/bin/testasciidoc.py debian/asciidoc-tests/usr/bin/testasciidoc
 	find debian -type d -name __pycache__ -prune -exec rm -rf {} \;
 	rm -rf debian/asciidoc-base/usr/lib/python*/dist-packages/asciidoc/resources
-	rm -rf debian/asciidoc-base/usr/lib/python*/dist-packages/asciidoc-*.egg-info
 	rm -rf debian/asciidoc-common/etc/asciidoc/dblatex
 	rm -rf debian/asciidoc-common/etc/asciidoc/icons
 	rm -rf debian/asciidoc-common/etc/asciidoc/javascripts


pgphiarRo67Bt.pgp
Description: OpenPGP digital signature

Bug#997188: marked as done (irqbalance: FTBFS: ui/ui.c:28:24: error: format not a string literal and no format arguments [-Werror=format-security])

[Debian Bug Tracking System]

Your message dated Sat, 30 Oct 2021 13:35:34 +
with message-id 
and subject line Bug#997188: fixed in irqbalance 1.8.0-1
has caused the Debian Bug report #997188,
regarding irqbalance: FTBFS: ui/ui.c:28:24: error: format not a string literal 
and no format arguments [-Werror=format-security]
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.)


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

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. -W -Wall -Wshadow -Wformat -Wundef -D_GNU_SOURCE 
> -Wdate-time -D_FORTIFY_SOURCE=2  -I/usr/include/glib-2.0 
> -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -g -O2 
> -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat 
> -Werror=format-security -c -o ui/ui.o ui/ui.c
> ui/irqbalance-ui.c: In function ‘main’:
> ui/irqbalance-ui.c:419:41: warning: ignoring return value of ‘fgets’ declared 
> with attribute ‘warn_unused_result’ [-Wunused-result]
>   419 | fgets(cmdstring, 255, f);
>   | ^~~~
> ui/ui.c: In function ‘show_frame’:
> ui/ui.c:28:24: error: format not a string literal and no format arguments 
> [-Werror=format-security]
>28 | mvprintw(0, 0, top);
>   |^~~
> ui/ui.c: In function ‘show_footer’:
> ui/ui.c:44:32: error: format not a string literal and no format arguments 
> [-Werror=format-security]
>44 | mvprintw(LINES - 1, 0, footer);
>   |^~
> ui/ui.c: In function ‘print_assigned_objects_string’:
> ui/ui.c:333:36: error: format not a string literal and no format arguments 
> [-Werror=format-security]
>   333 | mvprintw(*line_offset, 36, assigned_to);
>   |^~~
> ui/ui.c: In function ‘settings’:
> ui/ui.c:568:24: error: format not a string literal and no format arguments 
> [-Werror=format-security]
>   568 | mvprintw(2, 3, info);
>   |^~~~
> ui/ui.c: In function ‘display_tree_node_irqs’:
> ui/ui.c:666:25: warning: format ‘%lu’ expects argument of type ‘long unsigned 
> int’, but argument 3 has type ‘int’ [-Wformat=]
>   666 | printw("%sIRQ %lu, IRQs since last rebalance %lu\n",
>   |   ~~^
>   | |
>   | long unsigned int
>   |   %u
>   667 | indent, irq->vector, irq->diff);
>   | ~~~
>   ||
>   |int
> ui/ui.c: In function ‘display_tree_node’:
> ui/ui.c:713:16: error: format not a string literal and no format arguments 
> [-Werror=format-security]
>   713 | printw(copy_to);
>   |^~~
> /bin/bash ./libtool  --tag=CC   --mode=link gcc  -I/usr/include/glib-2.0 
> -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -g -O2 
> -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat 
> -Werror=format-security  -Wl,-z,relro -Wl,-z,now -o irqbalance activate.o 
> bitmap.o classify.o cputree.o irqbalance.o irqlist.o numa.o placement.o 
> procinterrupts.o -lcap-ng -lglib-2.0 -lsystemd -lsystemd -lm -lnuma  
> -lncursesw -ltinfo
> libtool: link: gcc -I/usr/include/glib-2.0 
> -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -g -O2 
> -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat 
> -Werror=format-security -Wl,-z -Wl,relro -Wl,-z -Wl,now -o irqbalance 
> activate.o bitmap.o classify.o cputree.o irqbalance.o irqlist.o numa.o 
> placement.o procinterrupts.o  -lcap-ng -lglib-2.0 -lsystemd -lm -lnuma 
> -lncursesw -ltinfo
> cc1: some warnings being treated as errors
> make[3]: *** [Makefile:583: ui/ui.o] Error 1


The full build log is available from:
http://qa-logs.debian.net/2021/10/23/irqbalance_1.7.0-1_unstable.log

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

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

If you fail to reproduce this, please provide a build log and diff it with mine
so that we can identify if something re

Bug#998108: Acknowledgement (firefox freezes shortly after start)

[Christoph Anton Mitterer]

Sometimes it seems that firefox doesn't freeze "immediatly" but some
sites continue to work (and e.g. the address bar still allows input).
But new sites (especially with JS stuff) don't load correctly or just
freeze.

Eventually whole firefox freezes and one cannot event select the
address bar anymore or switch between tabs.

Bug#998113: src:osmnx: fails to migrate to testing for too long: autopkgtest regression

[Paul Gevers]

Source: osmnx
Version: 1.0.1+ds-1
Severity: serious
Control: close -1 1.1.1+ds-4
Tags: sid bookworm
User: release.debian@packages.debian.org
Usertags: out-of-sync
Control: block -1 by 995021

Dear maintainer(s),

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

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

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

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

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

Paul

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




OpenPGP_signature
Description: OpenPGP digital signature

Processed: src:osmnx: fails to migrate to testing for too long: autopkgtest regression

[Debian Bug Tracking System]

Processing control commands:

> close -1 1.1.1+ds-4
Bug #998113 [src:osmnx] src:osmnx: fails to migrate to testing for too long: 
autopkgtest regression
Marked as fixed in versions osmnx/1.1.1+ds-4.
Bug #998113 [src:osmnx] src:osmnx: fails to migrate to testing for too long: 
autopkgtest regression
Marked Bug as done
> block -1 by 995021
Bug #998113 {Done: Paul Gevers } [src:osmnx] src:osmnx: 
fails to migrate to testing for too long: autopkgtest regression
998113 was not blocked by any bugs.
998113 was not blocking any bugs.
Added blocking bug(s) of 998113: 995021

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

Processed: src:rust-bumpalo: fails to migrate to testing for too long: autopkgtest regression

[Debian Bug Tracking System]

Processing control commands:

> close -1 3.7.0-2
Bug #998111 [src:rust-bumpalo] src:rust-bumpalo: fails to migrate to testing 
for too long: autopkgtest regression
Marked as fixed in versions rust-bumpalo/3.7.0-2.
Bug #998111 [src:rust-bumpalo] src:rust-bumpalo: fails to migrate to testing 
for too long: autopkgtest regression
Marked Bug as done

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

Bug#998112: src:reqwest: fails to migrate to testing for too long: upload built arch:all binaries

[Paul Gevers]

Source: reqwest
Version: 0.6.0-2
Severity: serious
Control: close -1 0.6.0-3
Tags: sid bookworm pending
X-Debbugs-CC: jel...@debian.org
User: release.debian@packages.debian.org
Usertags: out-of-sync

Dear maintainer(s),

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

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

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

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

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

Paul

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




OpenPGP_signature
Description: OpenPGP digital signature

Processed: src:reqwest: fails to migrate to testing for too long: upload built arch:all binaries

[Debian Bug Tracking System]

Processing control commands:

> close -1 0.6.0-3
Bug #998112 [src:reqwest] src:reqwest: fails to migrate to testing for too 
long: upload built arch:all binaries
Marked as fixed in versions reqwest/0.6.0-3.
Bug #998112 [src:reqwest] src:reqwest: fails to migrate to testing for too 
long: upload built arch:all binaries
Marked Bug as done

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

Bug#998111: src:rust-bumpalo: fails to migrate to testing for too long: autopkgtest regression

[Paul Gevers]

Source: rust-bumpalo
Version: 3.4.0-1
Severity: serious
Control: close -1 3.7.0-2
Tags: sid bookworm
User: release.debian@packages.debian.org
Usertags: out-of-sync

Dear maintainer(s),

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

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

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

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

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

Paul

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




OpenPGP_signature
Description: OpenPGP digital signature

Bug#997940: [Pkg-pascal-devel] Bug#997940: view3dscene: FTBFS with fpc 3.2.2

[Paul Gevers]

Hi Abou,

On 30-10-2021 12:46, Abou Al Montacir wrote:
>> "Just" rebuilding is not the solution to paper over such an issue, we'd
>> need to prevent it from going unnoticed next time. It should show up on
>> https://release.debian.org/transitions/
>>  with an auto-upperlimit-fpc
>> transition such that the release team is automatically warned that
>> rebuilds are needed and to prevent fpc from migrating until the rebuild
>> happened and is ready to migrate too.
> I don't know for now how to handle this efficiently. but the easiest way
> is to say, each new upload of FPC triggers all libraries (not programs)
> rebuild.

So all libraries need a Depends on a binary from src:fpc with an upper
limit (generated during the build). In that way, the Debian
infrastructure knows that a rebuild (or potentially manual action) is
needed. We don't want it to be too tight. When you said "any new version
of FPC" do you mean each patch level too, or on only minor level? How
about Debian new uploads?

Paul



OpenPGP_signature
Description: OpenPGP digital signature

Processed: reopening 997119

[Debian Bug Tracking System]

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

> reopen 997119
Bug #997119 {Done: David Prévot } [src:symfony] symfony: 
FTBFS: tests failed variable (T_VARIABLE)
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
No longer marked as fixed in versions symfony/5.3.9+dfsg-1.
> thanks
Stopping processing here.

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

Bug#998108: firefox freezes shortly after start

[Christoph Anton Mitterer]

Package: firefox
Version: 93.0-1+b1
Severity: grave
Justification: renders package unusable

Hey.

Since about yesterday (possibly since the rebuilt package came in)
firefox freezes shortly after being started.
There is no high CPU activity then, it just takes no input anymore
(no keyboard, no mouse clicks).
This also happens in --safe-mode.

Any ideas?

Chris.




-- Package-specific info:

-- Extensions information
Name: Amazon.co.uk
Location: /usr/lib/firefox/browser/omni.ja
Package: firefox
Status: enabled

Name: Bing
Location: /usr/lib/firefox/browser/omni.ja
Package: firefox
Status: enabled

Name: Dark theme
Location: /usr/lib/firefox/browser/omni.ja
Package: firefox
Status: user-disabled

Name: Debian queries
Location: /usr/share/webext/debian-buttons
Package: webext-debianbuttons
Status: user-disabled

Name: DoH Roll-Out
Location: /usr/lib/firefox/browser/features/doh-roll...@mozilla.org.xpi
Package: firefox
Status: enabled

Name: DuckDuckGo
Location: /usr/lib/firefox/browser/omni.ja
Package: firefox
Status: enabled

Name: eBay
Location: /usr/lib/firefox/browser/omni.ja
Package: firefox
Status: enabled

Name: Firefox Alpenglow theme
Location: /usr/lib/firefox/browser/omni.ja
Package: firefox
Status: user-disabled

Name: Firefox Screenshots
Location: /usr/lib/firefox/browser/features/screensh...@mozilla.org.xpi
Package: firefox
Status: enabled

Name: Form Autofill
Location: /usr/lib/firefox/browser/features/formautof...@mozilla.org.xpi
Package: firefox
Status: enabled

Name: FoxyProxy Standard
Location: /usr/share/webext/foxyproxy
Package: webext-foxyproxy
Status: enabled

Name: Google
Location: /usr/lib/firefox/browser/omni.ja
Package: firefox
Status: enabled

Name: Light theme
Location: /usr/lib/firefox/browser/omni.ja
Package: firefox
Status: user-disabled

Name: Lightbeam 3.0
Location: /usr/share/webext/lightbeam
Package: webext-lightbeam
Status: user-disabled

Name: NoScript
Location: /usr/share/webext/noscript
Package: webext-noscript
Status: enabled

Name: Picture-In-Picture
Location: /usr/lib/firefox/browser/features/pictureinpict...@mozilla.org.xpi
Package: firefox
Status: enabled

Name: System theme theme
Location: /usr/lib/firefox/omni.ja
Package: firefox
Status: enabled

Name: uBlock Origin
Location: 
/usr/share/mozilla/extensions/{ec8030f7-c20a-464f-9b0e-13a3a9e97384}/ublo...@raymondhill.net
Package: webext-ublock-origin-firefox
Status: enabled

Name: Web Compatibility Interventions
Location: /usr/lib/firefox/browser/features/webcom...@mozilla.org.xpi
Package: firefox
Status: enabled

Name: WebCompat Reporter
Location: /usr/lib/firefox/browser/features/webcompat-repor...@mozilla.org.xpi
Package: firefox
Status: user-disabled

Name: Wikipedia (en)
Location: /usr/lib/firefox/browser/omni.ja
Package: firefox
Status: enabled


-- Addons package information
ii  firefox  93.0-1+b1 amd64Mozilla Firefox web 
browser
ii  webext-debianbuttons 2.3-2 all  Buttons for 
querying Debian-related pages with Firefox
ii  webext-foxyproxy 7.5.1+dfsg-2  all  Advanced proxy 
management for Firefox
ii  webext-lightbeam 3.0.1-1   all  visualize sites 
that may be tracking you around the internet
ii  webext-noscript  10.1.9.6-2all  permissions manager 
for Firefox
ii  webext-ublock-origin-firefox 1.37.0+dfsg-1 all  lightweight and 
efficient ads, malware, trackers blocker (Firefox)

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

Kernel: Linux 5.14.0-3-amd64 (SMP w/4 CPU threads)
Locale: LANG=en_DE.UTF-8, LC_CTYPE=en_DE.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages firefox depends on:
ii  debianutils  5.5-1
ii  fontconfig   2.13.1-4.2
ii  libatk1.0-0  2.36.0-2
ii  libc62.32-4
ii  libcairo-gobject21.16.0-5
ii  libcairo21.16.0-5
ii  libdbus-1-3  1.12.20-3
ii  libdbus-glib-1-2 0.112-2
ii  libevent-2.1-7   2.1.12-stable-1
ii  libffi8  3.4.2-3
ii  libfontconfig1   2.13.1-4.2
ii  libfreetype6 2.11.0+dfsg-1
ii  libgcc-s111.2.0-10
ii  libgdk-pixbuf-2.0-0  2.42.6+dfsg-2
ii  libglib2.0-0 2.70.0-3
ii  libgtk-3-0   3.24.30-3
ii  libnspr4 2:4.32-1
ii  libnss3  2:3.70-1
ii  libpango-1.0-0   1.48.10+ds1-1
ii  libstdc++6   11.2.0-10
ii  libvpx7  1.11.0-2
ii  libx11-6 2:1.7.2-2+b1
ii  libx11-xcb1  2:1.7.2-2+b1
ii  libxcb-shm0  1.14-3
ii  libxcb1  1.14-3
ii  libxcomposite1   1:0.4.5-1
ii  libxdamage1  1:1.1.5-2
ii  libxext6 2:1.3.4-1
ii  libxfixes3   1:5.0.3-2
ii  libxrender1  1:0.9.10-1
ii  procps 

Bug#998107: src:simile-timeline: fails to migrate to testing for too long: uploader built arch:all binaries

[Paul Gevers]

Source: simile-timeline
Version: 2.3.0+dfsg1-4
Severity: serious
Control: close -1 2.3.0+dfsg1-6
X-Debbugs-CC: jel...@debian.org
Tags: sid bookworm pending
User: release.debian@packages.debian.org
Usertags: out-of-sync

Dear maintainer(s),

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

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

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

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

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

Paul

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




OpenPGP_signature
Description: OpenPGP digital signature

Processed: src:simile-timeline: fails to migrate to testing for too long: uploader built arch:all binaries

[Debian Bug Tracking System]

Processing control commands:

> close -1 2.3.0+dfsg1-6
Bug #998107 [src:simile-timeline] src:simile-timeline: fails to migrate to 
testing for too long: uploader built arch:all binaries
Marked as fixed in versions simile-timeline/2.3.0+dfsg1-6.
Bug #998107 [src:simile-timeline] src:simile-timeline: fails to migrate to 
testing for too long: uploader built arch:all binaries
Marked Bug as done

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

Processed: mpi4py: test_io.TestIOSelf failures on i386

[Debian Bug Tracking System]

Processing control commands:

> forwarded -1 https://github.com/mpi4py/mpi4py/issues/105
Bug #998106 [src:mpi4py] mpi4py: test_io.TestIOSelf failures on i386
Set Bug forwarded-to-address to 'https://github.com/mpi4py/mpi4py/issues/105'.

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

Bug#998106: mpi4py: test_io.TestIOSelf failures on i386

[Drew Parsons]

Source: mpi4py
Version: 3.1.1-8
Severity: serious
Justification: debci
Control: forwarded -1 https://github.com/mpi4py/mpi4py/issues/105

mpi4py tests are failing on i386 debci.
e.g.
https://ci.debian.net/data/autopkgtest/unstable/i386/m/mpi4py/16315322/log.gz

The failing tests are file IO tests (test_io.TestIOSelf and test_io.TestIOWorld)
e.g.

==
ERROR: testIReadIWrite (test_io.TestIOSelf)
--
Traceback (most recent call last):
  File "/tmp/autopkgtest-lxc.ktqusnzb/downtmp/build.ZLO/src/test/test_io.py", 
line 124, in testIReadIWrite
fh.Set_view(0, etype)
  File "mpi4py/MPI/File.pyx", line 215, in mpi4py.MPI.File.Set_view
mpi4py.MPI.Exception: MPI_ERR_ARG: invalid argument of some other kind

==
ERROR: testIReadIWriteAll (test_io.TestIOSelf)
--
Traceback (most recent call last):
  File "/tmp/autopkgtest-lxc.ktqusnzb/downtmp/build.ZLO/src/test/test_io.py", 
line 302, in testIReadIWriteAll
fh.Set_view(0, etype)
  File "mpi4py/MPI/File.pyx", line 215, in mpi4py.MPI.File.Set_view
mpi4py.MPI.Exception: MPI_ERR_ARG: invalid argument of some other kind

==
ERROR: testIReadIWriteAt (test_io.TestIOSelf)
-
Traceback (most recent call last):
  File "/tmp/autopkgtest-lxc.ktqusnzb/downtmp/build.ZLO/src/test/test_io.py", 
line 75, in testIReadIWriteAt
fh.Set_view(0, etype)
  File "mpi4py/MPI/File.pyx", line 215, in mpi4py.MPI.File.Set_view
mpi4py.MPI.Exception: MPI_ERR_ARG: invalid argument of some other kind

==
ERROR: testIReadIWriteAtAll (test_io.TestIOSelf)
--
Traceback (most recent call last):
  File "/tmp/autopkgtest-lxc.ktqusnzb/downtmp/build.ZLO/src/test/test_io.py", 
line 227, in testIReadIWriteAtAll
fh.Set_view(0, etype)
  File "mpi4py/MPI/File.pyx", line 215, in mpi4py.MPI.File.Set_view
mpi4py.MPI.Exception: MPI_ERR_ARG: invalid argument of some other kind

The problem was already reported upstream, 
https://github.com/mpi4py/mpi4py/issues/105
It's affecting Redhat, not just Debian.


This is not a general 32-bit failure.  armhf is passing tests.


Probably severity: serious is overkill for this problem. The test
failure can be ignored for the purpose of package management by simply
skipping test_io.TestIOSelf and test_io.TestIOWorld on i386.  The
other 1172 mpi4py tests are passing on i386.

Patient: Doctor, it hurts when I do this.
Doctor: Then don't do that.

Bug#997233: marked as done (loudgain: FTBFS: ld: cannot find -lz)

[Debian Bug Tracking System]

Your message dated Sat, 30 Oct 2021 12:03:50 +
with message-id 
and subject line Bug#997233: fixed in loudgain 0.6.8+ds-2
has caused the Debian Bug report #997233,
regarding loudgain: FTBFS: ld: cannot find -lz
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.)


-- 
997233: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997233
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: loudgain
Version: 0.6.8+ds-1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs

Hi,

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


Relevant part (hopefully):
> /usr/bin/c++ -std=gnu++11 -D_GNU_SOURCE -Wl,-z,relro -Wl,-z,now -rdynamic 
> CMakeFiles/loudgain.dir/src/loudgain.c.o 
> CMakeFiles/loudgain.dir/src/printf.c.o CMakeFiles/loudgain.dir/src/scan.c.o 
> CMakeFiles/loudgain.dir/src/tag.cc.o -o loudgain  -lebur128 -lavcodec 
> -lavformat -lswresample -lavutil -ltag -lz 
> /usr/bin/ld: cannot find -lz
> collect2: error: ld returned 1 exit status


The full build log is available from:
http://qa-logs.debian.net/2021/10/23/loudgain_0.6.8+ds-1_unstable.log

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

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

If you fail to reproduce this, please provide a build log and diff it with mine
so that we can identify if something relevant changed in the meantime.
--- End Message ---
--- Begin Message ---
Source: loudgain
Source-Version: 0.6.8+ds-2
Done: Hugh McMaster 

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

Debian distribution maintenance software
pp.
Hugh McMaster  (supplier of updated loudgain package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sat, 30 Oct 2021 20:11:44 +1100
Source: loudgain
Architecture: source
Version: 0.6.8+ds-2
Distribution: unstable
Urgency: medium
Maintainer: Hugh McMaster 
Changed-By: Hugh McMaster 
Closes: 997233
Changes:
 loudgain (0.6.8+ds-2) unstable; urgency=medium
 .
   [ Debian Janitor ]
   * Remove version constraints on build-dependencies unnecessary since Buster.
 .
   [ Hugh McMaster ]
   * debian/gbp.conf: Use DEP-14 branch naming.
   * debian/control:
 - Build-Depend on zlib1g-dev | libz-dev (Closes: #997233).
 - Raise Standards-Version to 4.6.0 from 4.5.0 (no changes needed).
   * debian/source/lintian-overrides: Silence a line-length warning in the
 upstream README.md file.
Checksums-Sha1:
 b035ab904a20e8715fbfe2c715a1279bddac42c0 1825 loudgain_0.6.8+ds-2.dsc
 d5f8e0cfff1a7557139bb43e35fe6f9a67c65e2c 4864 loudgain_0.6.8+ds-2.debian.tar.xz
 0644c719fd037b9b9e2cb18b49c6bfa12e208225 9100 
loudgain_0.6.8+ds-2_source.buildinfo
Checksums-Sha256:
 67f48c561433eb645c2bc7c1b41b08bfef3dbe03980c17b2e8f20ef238dce43b 1825 
loudgain_0.6.8+ds-2.dsc
 28958132fd57f715316a664750dd60ed29e03b379f9a31775c538b88536efa69 4864 
loudgain_0.6.8+ds-2.debian.tar.xz
 384c3d9f22bcf89c0fe69458716b14bb3a2dd327f84f24e4e3ba4ceb4bfc91d6 9100 
loudgain_0.6.8+ds-2_source.buildinfo
Files:
 e672fa42b27c263e7dd48ee9466d2da3 1825 sound optional loudgain_0.6.8+ds-2.dsc
 cc3be3059a9a48fc8e12aa3a50899275 4864 sound optional 
loudgain_0.6.8+ds-2.debian.tar.xz
 ddad732b24ddb3611d191dd438d6ea15 9100 sound optional 
loudgain_0.6.8+ds-2_source.buildinfo

-BEGIN PGP SIGNATURE-

iQGzBAEBCgAdFiEEQGIgyLhVKAI3jM5BH1x6i0VWQxQFAmF9Lo4ACgkQH1x6i0VW
QxRfMAwApMcghfcMmWHiSZU6hhTKPkoXYjyvGq1ytrp8/YWp15XVrTap07GM+aZC
Pdq9T7g8ROvHgdRHdEpU8t80JUaNqGBrt+qgh6EJHUQkCyScjGXDssfISconS55o
f53yJCpmNCfkwLarw1ccXiXMC5Nxj4BdvUVeasCvEBAZKtbIifyz2ePDOAgTy9B0
6cjsdicDgetnTyI0GAfzxdmxocXuIol3HdOm4zJ2a6CRyvJ71USthHqOnzgJiEt5
MImHdlONWNaxJi9cJhHpPum4gonSv9ubRV7rogTH8KYu2NGJbX+R21ctn7Zynqz6
p8BoCUHzSSnN1OOSJrPL1DkXb1HBPRAZV1gFlY2gLwz2efQg/K/yCCN3mdBnoWmU
HWFkQ0LYuXc1tZVPyeydv4jTjwi4qwEQzFQEX8pOcqJUNR2pQNIUuvCa7FJvOZAs
Bg29RgK8WNqCnheW2KKyHOu2ZoCyEuHRrZ86aHWz

Bug#995317: marked as done (apertium broken on s390x due to missing endianness definition)

[Debian Bug Tracking System]

Your message dated Sat, 30 Oct 2021 12:03:35 +
with message-id 
and subject line Bug#995317: fixed in apertium 3.7.2-1
has caused the Debian Bug report #995317,
regarding apertium broken on s390x due to missing endianness definition
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.)


-- 
995317: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=995317
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: apertium
Version: 3.7.1-1
Severity: grave
Tags: patch
Justification: ships a binary package that's effectively unusable on an 
architecture
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu impish ubuntu-patch

Dear maintainers,

The apertium-br-fr autopkgtests have been failing on s390x in Debian and
Ubuntu.  Although this is not considered a regression in Debian because
there was never a test that passed, and therefore apertium-br-fr 0.5.1-1 is
in Debian testing (and stable), in Ubuntu the tests were previously run with
apertium-br-fr 0.5.0~r61325-4 which passed, so the new apertium-br-fr has
been blocked from reaching an Ubuntu release.

Digging into the failure, the apertium invocation of pcre is failing with
the error:
  Error: Unknown error matching regexp (code -29)

-29 in pcre maps to PCRE_ERROR_BADENDIANNESS.

There is code in apertium to detect the host endianness and set the correct
option to the pcre engine, but a missing header include means that the code
in question doesn't know the host endianness, so doesn't set it.

The attached patch fixes the omission, and when rebuilt with this flag, the
apertium-br-fr autopkgtest now passes with both 0.5.1-1 and 0.5.0~r61325-4
versions of the data files.

I'm marking this bug as grave because to my understanding this makes
apertium completely unusable on s390x with any current data files - it's
just that only 3 of the apertium dictionary packages have autopkgtests.

-- 
Steve Langasek   Give me a lever long enough and a Free OS
Debian Developer   to set it on, and I can move the world.
Ubuntu Developer   https://www.debian.org/
slanga...@ubuntu.com vor...@debian.org
diff -Nru apertium-3.7.1/debian/patches/endianness.patch 
apertium-3.7.1/debian/patches/endianness.patch
--- apertium-3.7.1/debian/patches/endianness.patch  1969-12-31 
16:00:00.0 -0800
+++ apertium-3.7.1/debian/patches/endianness.patch  2021-09-29 
08:12:26.0 -0700
@@ -0,0 +1,20 @@
+Description: include the necessary header to configure the code for endianness
+ This source file has code to configure the regexp engine for the correct
+ host endianness, however, it is missing the include that allows the code to
+ know what the host endianness is.  Correct this omission.
+Author: Steve Langasek 
+Last-Update: 2021-09-29
+Forwarded: no
+
+Index: apertium-3.7.1/apertium/apertium_re.cc
+===
+--- apertium-3.7.1.orig/apertium/apertium_re.cc
 apertium-3.7.1/apertium/apertium_re.cc
+@@ -14,6 +14,7 @@
+  * You should have received a copy of the GNU General Public License
+  * along with this program; if not, see .
+  */
++#include "apertium/apertium_config.h"
+ #include 
+ #include 
+ #include 
diff -Nru apertium-3.7.1/debian/patches/series 
apertium-3.7.1/debian/patches/series
--- apertium-3.7.1/debian/patches/series1969-12-31 16:00:00.0 
-0800
+++ apertium-3.7.1/debian/patches/series2021-09-29 08:07:34.0 
-0700
@@ -0,0 +1 @@
+endianness.patch
--- End Message ---
--- Begin Message ---
Source: apertium
Source-Version: 3.7.2-1
Done: Kartik Mistry 

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

Debian distribution maintenance software
pp.
Kartik Mistry  (supplier of updated apertium package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Fri, 29 Oct 2021 17:23:51 +0530
Source: apertium
Architecture: source
Version: 3.7.2-1
Distribution: unstable

Processed: your mail

[Debian Bug Tracking System]

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

> tags 997233 + pending
Bug #997233 [src:loudgain] loudgain: FTBFS: ld: cannot find -lz
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#997940: view3dscene: FTBFS with fpc 3.2.2

[Abou Al Montacir]

Hi Paul,

> So, where should this tight dependency be recorded? Should we teach some
> binary from castle-game-engine to be strict about some src:fpc counterpart?
Normally, any new version of FPC should trigger a rebuild of the entire
libraries (not programs) packaged for FPC.
The reason is that FPC keeps units interface information in a ppu file that is
compiler version depended, but also RTL dependent (each ppu will hold a kind of
checksum on used unit files).
This is both an advantage and a drawback against C were interface is distributed
in a source (header) file. The advantage is that is will be faster, the drawback
is that you need a __potential__ rebuild after each compiler/RTL upgrade.
> 
> "Just" rebuilding is not the solution to paper over such an issue, we'd
> need to prevent it from going unnoticed next time. It should show up on
> https://release.debian.org/transitions/ with an auto-upperlimit-fpc
> transition such that the release team is automatically warned that
> rebuilds are needed and to prevent fpc from migrating until the rebuild
> happened and is ready to migrate too.
I don't know for now how to handle this efficiently. but the easiest way is to
say, each new upload of FPC triggers all libraries (not programs) rebuild.
-- 
Cheers,
Abou Al Montacir



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

Bug#990224: [Pkg-pascal-devel] Bug#990224: lazarus-src-2.0: leaves diversion after upgrade from sid to experimental

[Abou Al Montacir]

The issue here is that LPK files are needed by binary libs (pascal units / ppu)
and source packages.
The right solution would be probably to move them into a separate packages that
is used by both source and binaries.
However, that ppu files are distributed not as a unique packages but split into
several ones. So this solution will require to double the number or packages
required to install full Lazarus installation.

Another easier solution would be to make sources depend on binary or binary
depend on sources, but this is not something I like, even if, it is true, that
in order for Lazarus to show its all power, it needs the sources to be
installed.
-- 
Cheers,
Abou Al Montacir


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

Processed: bug 984083 is forwarded to https://sourceforge.net/p/lasi/bugs/9/

[Debian Bug Tracking System]

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

> forwarded 984083 https://sourceforge.net/p/lasi/bugs/9/
Bug #984083 [src:lasi] lasi: ftbfs with GCC-11
Set Bug forwarded-to-address to 'https://sourceforge.net/p/lasi/bugs/9/'.
> thanks
Stopping processing here.

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

Bug#997170: nmon: FTBFS: lmon16m.c:5478:45: error: format not a string literal and no format arguments [-Werror=format-security]

[Salvatore Bonaccorso]

Hi,

On Sat, Oct 23, 2021 at 09:07:29PM +0200, Lucas Nussbaum wrote:
> Source: nmon
> Version: 16m+debian-1
> Severity: serious
> Justification: FTBFS
> Tags: bookworm sid ftbfs
> 
> Hi,
> 
> During a rebuild of all packages in sid, your package failed to build
> on amd64.
> 
> 
> Relevant part (hopefully):
> > x86_64-linux-gnu-gcc -o nmon lmon16m.c -Wdate-time -D_FORTIFY_SOURCE=2 -g 
> > -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat 
> > -Werror=format-security -Wall -D DEBIAN -Wl,-z,relro -Wl,-z,now -lncurses  
> > -lm
> > lmon16m.c: In function ‘main’:
> > lmon16m.c:5478:45: error: format not a string literal and no format 
> > arguments [-Werror=format-security]
> >  5478 | mvwprintw(padsmp, 1, 0, cpu_line);
> >   | ^~~~
> > lmon16m.c:5600:51: error: format not a string literal and no format 
> > arguments [-Werror=format-security]
> >  5600 | CURSE mvwprintw(padsmp, i + 3, 0, cpu_line);
> >   |   ^~~~
> > lmon16m.c:5676:55: error: format not a string literal and no format 
> > arguments [-Werror=format-security]
> >  5676 | CURSE mvwprintw(padsmp, i + 5, 0, cpu_line);
> >   |   ^~~~
> > lmon16m.c:5707:21: error: format not a string literal and no format 
> > arguments [-Werror=format-security]
> >  5707 | mvwprintw(padwide, 1, 0, wide1);
> >   | ^
> > lmon16m.c:5708:21: error: format not a string literal and no format 
> > arguments [-Werror=format-security]
> >  5708 | mvwprintw(padwide, 2, 0, wide2);
> >   | ^
> > lmon16m.c:5709:21: error: format not a string literal and no format 
> > arguments [-Werror=format-security]
> >  5709 | mvwprintw(padwide, 3, 0, wide3);
> >   | ^
> > lmon16m.c:5710:21: error: format not a string literal and no format 
> > arguments [-Werror=format-security]
> >  5710 | mvwprintw(padwide, 4, 0, wide4);
> >   | ^
> > lmon16m.c:5711:21: error: format not a string literal and no format 
> > arguments [-Werror=format-security]
> >  5711 | mvwprintw(padwide, 5, 0, wide5);
> >   | ^
> > lmon16m.c:5712:21: error: format not a string literal and no format 
> > arguments [-Werror=format-security]
> >  5712 | mvwprintw(padwide, 6, 0, wide6);
> >   | ^
> > lmon16m.c:5713:21: error: format not a string literal and no format 
> > arguments [-Werror=format-security]
> >  5713 | mvwprintw(padwide, 7, 0, wide7);
> >   | ^
> > lmon16m.c:5714:21: error: format not a string literal and no format 
> > arguments [-Werror=format-security]
> >  5714 | mvwprintw(padwide, 8, 0, wide8);
> >   | ^
> > lmon16m.c:5715:21: error: format not a string literal and no format 
> > arguments [-Werror=format-security]
> >  5715 | mvwprintw(padwide, 9, 0, wide9);
> >   | ^
> > lmon16m.c:5716:21: error: format not a string literal and no format 
> > arguments [-Werror=format-security]
> >  5716 | mvwprintw(padwide, 10, 0, wide10);
> >   | ^
> > lmon16m.c:5758:25: error: format not a string literal and no format 
> > arguments [-Werror=format-security]
> >  5758 | mvwprintw(padwide, rows + 0, 0, wide1);
> >   | ^
> > lmon16m.c:5759:25: error: format not a string literal and no format 
> > arguments [-Werror=format-security]
> >  5759 | mvwprintw(padwide, rows + 1, 0, wide2);
> >   | ^
> > lmon16m.c:5760:25: error: format not a string literal and no format 
> > arguments [-Werror=format-security]
> >  5760 | mvwprintw(padwide, rows + 2, 0, wide3);
> >   | ^
> > lmon16m.c:5761:25: error: format not a string literal and no format 
> > arguments [-Werror=format-security]
> >  5761 | mvwprintw(padwide, rows + 3, 0, wide4);
> >   | ^
> > lmon16m.c:5762:25: error: format not a string literal and no format 
> > arguments [-Werror=format-security]
> >  5762 | mvwprintw(padwide, rows + 4, 0, wide5);
> >   | ^
> > lmon16m.c:5763:25: error: format not a string literal and no format 
> > arguments [-Werror=format-security]
> >  5763 | mvwprintw(padwide, rows + 5, 0, wide6);
> >   | ^
> > lmon16m.c:5764:25: error: format not a

Bug#997502: marked as done (pyresample: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p 3.9 returned exit code 13)

[Debian Bug Tracking System]

Your message dated Sat, 30 Oct 2021 09:48:40 +
with message-id 
and subject line Bug#997502: fixed in pyresample 1.22.0-1
has caused the Debian Bug report #997502,
regarding pyresample: FTBFS: dh_auto_test: error: pybuild --test --test-pytest 
-i python{version} -p 3.9 returned exit code 13
to be marked as done.

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

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


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

Hi,

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


Relevant part (hopefully):
> make[2]: Entering directory '/<>/docs'
> sphinx-build -b html -d build/doctrees  -a source build/html
> Running Sphinx v4.2.0
> making output directory... done
> loading intersphinx inventory from https://docs.python.org/3/objects.inv...
> loading intersphinx inventory from 
> https://docs.scipy.org/doc/numpy/objects.inv...
> loading intersphinx inventory from 
> https://docs.scipy.org/doc/scipy/reference/objects.inv...
> loading intersphinx inventory from 
> https://xarray.pydata.org/en/stable/objects.inv...
> loading intersphinx inventory from 
> https://docs.dask.org/en/latest/objects.inv...
> loading intersphinx inventory from 
> https://pandas.pydata.org/docs/objects.inv...
> loading intersphinx inventory from 
> https://pyresample.readthedocs.io/en/stable/objects.inv...
> loading intersphinx inventory from 
> https://trollsift.readthedocs.io/en/stable/objects.inv...
> loading intersphinx inventory from 
> https://trollimage.readthedocs.io/en/stable/objects.inv...
> intersphinx inventory has moved: https://docs.scipy.org/doc/numpy/objects.inv 
> -> https://numpy.org/doc/stable/objects.inv
> loading intersphinx inventory from 
> https://pyproj4.github.io/pyproj/dev/objects.inv...
> loading intersphinx inventory from https://proj.org/objects.inv...
> building [mo]: all of 0 po files
> building [html]: all source files
> updating environment: [new config] 21 added, 0 changed, 0 removed
> reading sources... [  4%] api/pyresample
> reading sources... [  9%] api/pyresample.bilinear
> reading sources... [ 14%] api/pyresample.bucket
> reading sources... [ 19%] api/pyresample.ewa
> reading sources... [ 23%] api/pyresample.gradient
> reading sources... [ 28%] api/pyresample.utils
> reading sources... [ 33%] data_reduce
> reading sources... [ 38%] geo_def
> reading sources... [ 42%] geo_filter
> reading sources... [ 47%] geometry_utils
> reading sources... [ 52%] grid
> reading sources... [ 57%] index
> reading sources... [ 61%] installation
> reading sources... [ 66%] multi
> reading sources... [ 71%] plot
> reading sources... [ 76%] plot_cartopy_basemap
> reading sources... [ 80%] plot_projections
> reading sources... [ 85%] preproc
> reading sources... [ 90%] roadmap
> reading sources... [ 95%] spherical_geometry
> reading sources... [100%] swath
> 
> /<>/pyresample/geometry.py:docstring of 
> pyresample.geometry.AreaDefinition.area_extent:1: WARNING: duplicate object 
> description of pyresample.geometry.AreaDefinition.area_extent, other instance 
> in api/pyresample, use :noindex: for one of them
> /<>/pyresample/geometry.py:docstring of 
> pyresample.geometry.DynamicAreaDefinition.pixel_size_x:1: WARNING: duplicate 
> object description of pyresample.geometry.DynamicAreaDefinition.pixel_size_x, 
> other instance in api/pyresample, use :noindex: for one of them
> /<>/pyresample/geometry.py:docstring of 
> pyresample.geometry.DynamicAreaDefinition.pixel_size_y:1: WARNING: duplicate 
> object description of pyresample.geometry.DynamicAreaDefinition.pixel_size_y, 
> other instance in api/pyresample, use :noindex: for one of them
> /<>/pyresample/bucket/__init__.py:docstring of 
> pyresample.bucket.BucketResampler.get_average:12: WARNING: Definition list 
> ends without a blank line; unexpected unindent.
> /<>/pyresample/bucket/__init__.py:docstring of 
> pyresample.bucket.BucketResampler.get_max:15: WARNING: Definition list ends 
> without a blank line; unexpected unindent.
> /<>/pyresample/bucket/__init__.py:docstring of 
> pyresample.bucket.BucketResampler.get_min:15: WARNING: Definition list ends 
> without a blank line; unexpected unindent.
> /<>/pyresample/bucket/__init__.py:docstring of 
> pyresample.bucket.BucketResampler.get_sum:10: WARNING: Definition list ends 
> without a blank line; unexpected unindent.
> WARNING: autodoc: failed to import module 'ewa' f

Processed: tagging 998026

[Debian Bug Tracking System]

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

> tags 998026 + sid bookworm
Bug #998026 {Done: Peter Pentchev } [libmodulemd] libmodulemd: 
autopkgtest fails with meson 0.60
Added tag(s) sid and bookworm.
> thanks
Stopping processing here.

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

Bug#998100: ruby-libxml: FTBFS on armhf and ppc64el

[Sebastian Ramacher]

Source: ruby-libxml
Version: 3.2.1-2
Severity: serious
Tags: ftbfs sid bookworm
Justification: fails to build from source (but built successfully in the past)
X-Debbugs-Cc: sramac...@debian.org

| TestNS#test_duplicate_ns = /<>/test/test_namespace.rb:41: [BUG] 
Segmentation fault at 0x0018
| ruby 3.0.2p107 (2021-07-07 revision 0db68f0233) [arm-linux-gnueabihf]

https://buildd.debian.org/status/fetch.php?pkg=ruby-libxml&arch=armhf&ver=3.2.1-2%2Bb1&stamp=1635545703&raw=0

| TestReader#test_invalid_file = /<>/test/test_reader.rb:64: [BUG] 
Segmentation fault at 0x0100287b53ef
| ruby 3.0.2p107 (2021-07-07 revision 0db68f0233) [powerpc64le-linux-gnu]

https://buildd.debian.org/status/fetch.php?pkg=ruby-libxml&arch=ppc64el&ver=3.2.1-2%2Bb1&stamp=1635548022&raw=0

Cheers
-- 
Sebastian Ramacher


signature.asc
Description: PGP signature

Bug#998099: ruby-hitimes: FTBFS on s390x

[Sebastian Ramacher]

Source: ruby-hitimes
Version: 1.2.1-4
Severity: serious
Tags: ftbfs sid bookworm
Justification: fails to build from source (but built successfully in the past)
X-Debbugs-Cc: sramac...@debian.org

| Failures:
|
|   1) Hitimes::Interval can time a block of code
|  Failure/Error: d.should be_within(0.02).of(0.2)
|expected 0.248421501 to be within 0.02 of 0.2
|  # ./spec/interval_spec.rb:43:in `block (2 levels) in '

https://buildd.debian.org/status/fetch.php?pkg=ruby-hitimes&arch=s390x&ver=1.2.1-4%2Bb1&stamp=1635543917&raw=0

Cheers
-- 
Sebastian Ramacher


signature.asc
Description: PGP signature

Bug#987379: llvm-toolchain-11 autopkgtest segfaults on armhf

[Sebastian Ramacher]

Control: reassign -1 binutils 2.37-7
Control: affects -1 src:lvm-toolchain-12

On 2021-10-28 15:50:35 +0200, Julien Cristau wrote:
> On Tue, Oct 26, 2021 at 04:14:35PM +0200, Paul Gevers wrote:
> > Hi Diederik, all,
> > 
> > On 26-10-2021 08:34, Diederik de Haas wrote:
> > > Therefor it may be worth trying whether this bug is resolved as well.
> > 
> > Well, it's not fixed in the Debian archive:
> > https://ci.debian.net/data/autopkgtest/unstable/armhf/l/llvm-toolchain-12/16229260/log.gz
> > 
> Should this be reassigned to binutils then?

It should.

Cheers
-- 
Sebastian Ramacher


signature.asc
Description: PGP signature

Bug#997186: marked as done (nast: FTBFS: ncurses/n_nast.c:686:46: error: format not a string literal and no format arguments [-Werror=format-security])

[Debian Bug Tracking System]

Your message dated Sat, 30 Oct 2021 09:03:29 +
with message-id 
and subject line Bug#997186: fixed in nast 0.2.0-9
has caused the Debian Bug report #997186,
regarding nast: FTBFS: ncurses/n_nast.c:686:46: error: format not a string 
literal and no format arguments [-Werror=format-security]
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.)


-- 
997186: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997186
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: nast
Version: 0.2.0-8
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs

Hi,

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


Relevant part (hopefully):
> gcc -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong 
> -Wformat -Werror=format-security -Wall -O2 -Wdate-time -D_FORTIFY_SOURCE=2 -c 
> ncurses/n_nast.c -o ncurses/n_nast.o
> ncurses/n_nast.c: In function ‘title’:
> ncurses/n_nast.c:686:46: error: format not a string literal and no format 
> arguments [-Werror=format-security]
>   686 |mvwprintw(title,1,(COLS-sizeof(TITLE))/2, TITLE);
>   |  ^
> ncurses/n_nast.c: In function ‘pop_up_win’:
> ncurses/n_nast.c:793:48: error: format not a string literal and no format 
> arguments [-Werror=format-security]
>   793 |mvwprintw(pop_up,0,(55 -strlen(message))/2, message);
>   |^~~
> ncurses/n_nast.c: In function ‘help_win’:
> ncurses/n_nast.c:804:46: error: format not a string literal and no format 
> arguments [-Werror=format-security]
>   804 |mvwprintw(help,0,(67 -strlen(message))/2, message);
>   |  ^~~
> cc1: some warnings being treated as errors
> make[1]: *** [Makefile:37: ncurses/n_nast.o] Error 1


The full build log is available from:
http://qa-logs.debian.net/2021/10/23/nast_0.2.0-8_unstable.log

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

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

If you fail to reproduce this, please provide a build log and diff it with mine
so that we can identify if something relevant changed in the meantime.
--- End Message ---
--- Begin Message ---
Source: nast
Source-Version: 0.2.0-9
Done: Andreas Beckmann 

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

Debian distribution maintenance software
pp.
Andreas Beckmann  (supplier of updated nast package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sat, 30 Oct 2021 10:47:58 +0200
Source: nast
Architecture: source
Version: 0.2.0-9
Distribution: unstable
Urgency: medium
Maintainer: Debian QA Group 
Changed-By: Andreas Beckmann 
Closes: 997186
Changes:
 nast (0.2.0-9) unstable; urgency=medium
 .
   * QA upload.
   * Use string literals for the format argument of mvwprintw calls.
 (Closes: #997186)
   * Switch to debhelper-compat (= 10).
   * Set Rules-Requires-Root: binary-targets.
Checksums-Sha1:
 8fff9bbe1777693bc0594a8c857768df06f468a6 1846 nast_0.2.0-9.dsc
 8c40d8d3d9f9cbfdda9e5c06e10e51bed0ab9504 22284 nast_0.2.0-9.debian.tar.xz
 db356d84a6aedca11267de53cf0776999035ef69 5994 nast_0.2.0-9_source.buildinfo
Checksums-Sha256:
 8ddb3bf863355b5019b9ba8f9edf4179da79fa4261e756d607aaf350cc476ce4 1846 
nast_0.2.0-9.dsc
 3cafeb6a226b4b807d0c4a7563eef64b96e8f917343d5961aea81ddf602ead0d 22284 
nast_0.2.0-9.debian.tar.xz
 b90cdf1967390456a86ab8757f8df0ce07026ca4a80377d37b24e0346bd3f4a8 5994 
nast_0.2.0-9_source.buildinfo
Files:
 493ff1db27ccfd56c1d71bd2c00e3854 1846 net optional nast_0.2.0-9.dsc
 7a1e6ecce1c93fe935e2c791029b10c9 22284 net optional nast_0.2.0-9.debian.tar.xz
 986379689550887b0013f8d1a1055347 5994 net optional 
nast_0.2.0-9_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJEBAEBCAAuFiEE6/MKMKjZxjvaRMaUX7M/k1np7QgFAmF9BxIQHGFuYmVAZGVi
aWFuLm9yZ

Bug#998097: ruby-eventmachine FTBFS on IPV6-only buildds and accesses the internet during the build

[Adrian Bunk]

Source: ruby-eventmachine
Severity: serious
Tags: ftbfs

FTBFS on IPV6-only buildds:

https://buildd.debian.org/status/fetch.php?pkg=ruby-eventmachine&arch=amd64&ver=1.3~pre20201020-b50c135-3&stamp=1633500476&raw=0
https://buildd.debian.org/status/fetch.php?pkg=ruby-eventmachine&arch=i386&ver=1.3~pre20201020-b50c135-4%2Bb1&stamp=1635578996&raw=0

FTBFS due to attempted DNS:

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

...
===
Failure: test_nameserver(TestResolver):
   was expected to be kind_of?
   but was
  .
/build/1st/ruby-eventmachine-1.3~pre20201020-b50c135/tests/test_resolver.rb:19:in
 `test_nameserver'
 16:   end
 17: 
 18:   def test_nameserver
  => 19: assert_kind_of(String, EM::DNS::Resolver.nameserver)
 20:   end
 21: 
 22:   def test_nameservers
===
...