Processed: Re: case: FTBFS with Sphinx 7.1, docutils 0.20: make[1]: *** [debian/rules:13: override_dh_auto_build] Error 2

2023-11-04 Thread Debian Bug Tracking System 
Processing control commands:

> tags -1 + unreproducible
Bug #1042628 [src:case] case: FTBFS with Sphinx 7.1, docutils 0.20: make[1]: 
*** [debian/rules:13: override_dh_auto_build] Error 2
Added tag(s) unreproducible.

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

Bug#1042628: case: FTBFS with Sphinx 7.1, docutils 0.20: make[1]: *** [debian/rules:13: override_dh_auto_build] Error 2

2023-11-04 Thread Paul Wise 
Control: tags -1 + unreproducible

On Sun, 30 Jul 2023 20:30:36 +0200 Lucas Nussbaum wrote:

> case fails to build with Sphinx 7.1 and docutils 0.20, both of which
> are currently available in experimental.

I am unable to reproduce this when building case 1.5.3+dfsg-5 with
experimental python3-sphinx 7.2.6-1 and python3-docutils 0.20.1+dfsg-1.

Could you recheck this build failure and close it if it is fixed?

-- 
bye,
pabs

https://wiki.debian.org/PaulWise


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

Processed: tagging 1052852 ...

2023-11-04 Thread Debian Bug Tracking System 
Processing commands for cont...@bugs.debian.org:

> tags 1052852 + patch
Bug #1052852 [src:python-django-crispy-forms] python-django-crispy-forms: 
FTBFS: make[1]: *** [debian/rules:17: override_dh_auto_test] Error 1
Added tag(s) patch.
> forwarded 1052852 
> https://github.com/django-crispy-forms/django-crispy-forms/pull/1257
Bug #1052852 [src:python-django-crispy-forms] python-django-crispy-forms: 
FTBFS: make[1]: *** [debian/rules:17: override_dh_auto_test] Error 1
Set Bug forwarded-to-address to 
'https://github.com/django-crispy-forms/django-crispy-forms/pull/1257'.
> thanks
Stopping processing here.

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

Bug#1041491: (no subject)

2023-11-04 Thread Don Armstrong 
I'm just reiterating the conversation I had with Santiago for
transparency and to explain what happened here:

This bug was originally tagged with "sid trixie". This means that the
for the purposes of archival, the BTS only needs to care if the bug has
been fixed in sid and trixie, and it should ignore whether it should be
fixed in bookworm. When the bug was fixed in sid and trixie, the BTS
archived it.

You rarely want to tag a bug with any of the distribution tags. [The
major exception is where a bug is present in a distribution because of
the versions of other packages in that distribution, not latently
present in the package itself, for example when an interface is
deprecated/removed.]

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

This isn't life in the fast lane, it's life in the oncoming traffic
 -- Terry Pratchett

Bug#1054678: marked as done (netgen: FTBFS: main.cpp:3:10: fatal error: catch.hpp: No such file or directory)

2023-11-04 Thread Debian Bug Tracking System 
Your message dated Sun, 05 Nov 2023 01:49:04 +
with message-id 
and subject line Bug#1054678: fixed in netgen 6.2.2006+really6.2.1905+dfsg-6
has caused the Debian Bug report #1054678,
regarding netgen: FTBFS: main.cpp:3:10: fatal error: catch.hpp: No such file or 
directory
to be marked as done.

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

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


-- 
1054678: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1054678
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: netgen
Version: 6.2.2006+really6.2.1905+dfsg-5.1
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20231027 ftbfs-trixie

Hi,

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


Relevant part (hopefully):
> cd /<>/obj-x86_64-linux-gnu/libsrc/core && /usr/bin/c++ 
> -DHAVE_DLFCN_H -DMETIS -DNETGEN_PYTHON -DNETGEN_VERSION=\"6.2-dev\" 
> -DNGCORE_EXPORTS -DNG_PYTHON -DOCCGEOMETRY -DOPENGL -DPARALLEL -DTCL 
> -DTOGL_X11 -DUSE_TOGL_2 -D_OCC64 -Dngcore_EXPORTS 
> -I/<>/obj-x86_64-linux-gnu/libsrc/core 
> -I/<>/libsrc/core -I/<>/obj-x86_64-linux-gnu 
> -I/<>/include -I/<>/libsrc/include 
> -I/usr/include/tcl -I/usr/include/python3.11 
> -I/usr/lib/x86_64-linux-gnu/openmpi/include 
> -I/usr/lib/x86_64-linux-gnu/openmpi/include/openmpi 
> -I/usr/include/opencascade -DMPICH_SKIP_MPICXX -lmpi -fPIC -Wall -g -O2 
> -ffile-prefix-map=/<>=. -fstack-protector-strong 
> -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -O2 
> -g -DNDEBUG -std=gnu++14 -fPIC -fvisibility=hidden -MD -MT 
> libsrc/core/CMakeFiles/ngcore.dir/utils.cpp.o -MF 
> CMakeFiles/ngcore.dir/utils.cpp.o.d -o CMakeFiles/ngcore.dir/utils.cpp.o -c 
> /<>/libsrc/core/utils.cpp
> /<>/tests/catch/main.cpp:3:10: fatal error: catch.hpp: No such 
> file or directory
> 3 | #include 
>   |  ^~~
> compilation terminated.
> make[3]: *** [tests/catch/CMakeFiles/catch_main.dir/build.make:79: 
> tests/catch/CMakeFiles/catch_main.dir/main.cpp.o] Error 1


The full build log is available from:
http://qa-logs.debian.net/2023/10/27/netgen_6.2.2006+really6.2.1905+dfsg-5.1_unstable.log

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

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

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

If you fail to reproduce this, please provide a build log and diff it with mine
so that we can identify if something relevant changed in the meantime.
--- End Message ---
--- Begin Message ---
Source: netgen
Source-Version: 6.2.2006+really6.2.1905+dfsg-6
Done: Drew Parsons 

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

Debian distribution maintenance software
pp.
Drew Parsons  (supplier of updated netgen package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sun, 05 Nov 2023 02:03:32 +0100
Source: netgen
Architecture: source
Version: 6.2.2006+really6.2.1905+dfsg-6
Distribution: unstable
Urgency: medium
Maintainer: Debian Science Maintainers 

Changed-By: Drew Parsons 
Closes: 1048629 1054678
Changes:
 netgen (6.2.2006+really6.2.1905+dfsg-6) unstable; urgency=medium
 .
   * Team upload.
   * debian patch catch2_v3.patch enables test build with catch2 v3
 Closes: #1054678.
   * dh_clean removes python test cache files. Closes: #1048629.
   * debian patch test_runtime.patch enables runtime test configuration
   * debian/tests/netgen-test builds and runs runtime tests
 (without rebuilding netgen libraries)
Checksums-Sha1:
 d3f615dc1342e5ca7d1c0d1528bc60b3543dd474 2843 
netgen_6.2.2006+real

Bug#1054738: marked as done (python-gffutils: FTBFS: make: *** [debian/rules:14: clean] Error 25)

2023-11-04 Thread Debian Bug Tracking System 
Your message dated Sun, 05 Nov 2023 01:19:21 +
with message-id 
and subject line Bug#1054738: fixed in python-gffutils 0.12-2
has caused the Debian Bug report #1054738,
regarding python-gffutils: FTBFS: make: *** [debian/rules:14: clean] Error 25
to be marked as done.

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

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


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

Hi,

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


Relevant part (hopefully):
>  debian/rules clean
> dh clean --with python3 --buildsystem=pybuild
>dh_auto_clean -O--buildsystem=pybuild
> I: pybuild base:310: python3.11 setup.py clean 
> Traceback (most recent call last):
>   File "/usr/lib/python3/dist-packages/setuptools/_normalization.py", line 
> 59, in safe_version
> return str(packaging.version.Version(v))
>
>   File 
> "/usr/lib/python3/dist-packages/setuptools/_vendor/packaging/version.py", 
> line 198, in __init__
> raise InvalidVersion(f"Invalid version: '{version}'")
> setuptools.extern.packaging.version.InvalidVersion: Invalid version: '.0.12'
> 
> During handling of the above exception, another exception occurred:
> 
> Traceback (most recent call last):
>   File "/<>/setup.py", line 9, in 
> setup(
>   File "/usr/lib/python3/dist-packages/setuptools/__init__.py", line 107, in 
> setup
> return distutils.core.setup(**attrs)
>^
>   File "/usr/lib/python3/dist-packages/setuptools/_distutils/core.py", line 
> 147, in setup
> _setup_distribution = dist = klass(attrs)
>  
>   File "/usr/lib/python3/dist-packages/setuptools/dist.py", line 480, in 
> __init__
> self.patch_missing_pkg_info(attrs)
>   File "/usr/lib/python3/dist-packages/setuptools/dist.py", line 469, in 
> patch_missing_pkg_info
> dist._version = _normalization.safe_version(str(attrs['version']))
> ^^
>   File "/usr/lib/python3/dist-packages/setuptools/_normalization.py", line 
> 62, in safe_version
> return str(packaging.version.Version(attempt))
>^^
>   File 
> "/usr/lib/python3/dist-packages/setuptools/_vendor/packaging/version.py", 
> line 198, in __init__
> raise InvalidVersion(f"Invalid version: '{version}'")
> setuptools.extern.packaging.version.InvalidVersion: Invalid version: '.0.12'
> E: pybuild pybuild:395: clean: plugin distutils failed with: exit code=1: 
> python3.11 setup.py clean 
> dh_auto_clean: error: pybuild --clean -i python{version} -p 3.11 returned 
> exit code 13
> make: *** [debian/rules:14: clean] Error 25


The full build log is available from:
http://qa-logs.debian.net/2023/10/27/python-gffutils_0.12-1_unstable.log

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

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

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

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

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

Debian distribution maintenance software
pp.
Nilesh Patra  (supplier of updated python-gffutils package)

(This message was generated automatically at their request; if you
believe that t

Processed: upstream issue

2023-11-04 Thread Debian Bug Tracking System 
Processing commands for cont...@bugs.debian.org:

> limit package src:shaarli
Limiting to bugs with field 'package' containing at least one of 'src:shaarli'
Limit currently set to 'package':'src:shaarli'

> tags 1055002 + upstream
Bug #1055002 [src:shaarli] shaarli: FTBFS: dh_auto_test: error: make -j8 test 
returned exit code 2
Added tag(s) upstream.
> forwarded 1055002 https://github.com/shaarli/Shaarli/issues/2029
Bug #1055002 [src:shaarli] shaarli: FTBFS: dh_auto_test: error: make -j8 test 
returned exit code 2
Set Bug forwarded-to-address to 
'https://github.com/shaarli/Shaarli/issues/2029'.
> thanks
Stopping processing here.

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

Processed: Bug#1054738 marked as pending in python-gffutils

2023-11-04 Thread Debian Bug Tracking System 
Processing control commands:

> tag -1 pending
Bug #1054738 [src:python-gffutils] python-gffutils: FTBFS: make: *** 
[debian/rules:14: clean] Error 25
Added tag(s) pending.

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

Bug#1042687: marked as done (ycm-cmake-modules: FTBFS with Sphinx 7.1, docutils 0.20: TypeError: not all arguments converted during string formatting)

2023-11-04 Thread Debian Bug Tracking System 
Your message dated Sun, 05 Nov 2023 01:04:05 +
with message-id 
and subject line Bug#1042687: fixed in ycm-cmake-modules 0.13.0-3
has caused the Debian Bug report #1042687,
regarding ycm-cmake-modules: FTBFS with Sphinx 7.1, docutils 0.20: TypeError: 
not all arguments converted during string formatting
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.)


-- 
1042687: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1042687
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ycm-cmake-modules
Version: 0.13.0-2
Severity: important
Tags: ftbfs
User: python-modules-t...@lists.alioth.debian.org
Usertags: sphinx7.1

Hi,

ycm-cmake-modules fails to build with Sphinx 7.1 and docutils 0.20, both of 
which
are currently available in experimental.

Relevant part (hopefully):
> make[4]: Entering directory '/<>/obj-x86_64-linux-gnu'
> [ 87%] Files from KDE Extra CMake Modules git repository (ref v5.79.0) 
> downloaded
> cd /<>/obj-x86_64-linux-gnu/find-modules && /usr/bin/cmake -E 
> touch 
> /<>/obj-x86_64-linux-gnu/find-modules/CMakeFiles/find-modules.dir/ycm_localinstall-complete
> cd /<>/obj-x86_64-linux-gnu/build-modules && /usr/bin/cmake -E 
> echo_append
> cd /<>/3rdparty && /usr/bin/cmake -E touch 
> /<>/obj-x86_64-linux-gnu/3rdparty/CMakeFiles/3rdparty-ecm.dir/ycm_target-complete
> cd /<>/obj-x86_64-linux-gnu/build-modules && /usr/bin/cmake -E 
> echo_append
> cd /<>/obj-x86_64-linux-gnu/style-modules && /usr/bin/cmake -E 
> echo_append
> [ 87%] Built target deprecated
> cd /<>/obj-x86_64-linux-gnu/build-modules && /usr/bin/cmake -E 
> echo_append
> cd /<>/obj-x86_64-linux-gnu/style-modules && /usr/bin/cmake -E 
> echo_append
> [ 89%] sphinx-build html: see 
> /<>/obj-x86_64-linux-gnu/docs/docs/build-html.log
> cd /<>/obj-x86_64-linux-gnu/style-modules && /usr/bin/cmake -E 
> echo_append
> cd /<>/obj-x86_64-linux-gnu/build-modules && /usr/bin/cmake -E 
> echo_append
> cd /<>/obj-x86_64-linux-gnu/docs && /usr/bin/sphinx-build -c 
> /<>/obj-x86_64-linux-gnu/docs -d 
> /<>/obj-x86_64-linux-gnu/docs/doctrees -b html 
> /<>/help /<>/obj-x86_64-linux-gnu/docs/html > 
> build-html.log
> cd /<>/obj-x86_64-linux-gnu/build-modules && /usr/bin/cmake -E 
> echo_append
> make[4]: Leaving directory '/<>/obj-x86_64-linux-gnu'
> cd /<>/obj-x86_64-linux-gnu/style-modules && /usr/bin/cmake -E 
> echo_append
> cd /<>/obj-x86_64-linux-gnu/style-modules && /usr/bin/cmake -E 
> echo_append
> [ 89%] Built target 3rdparty-ecm
> cd /<>/obj-x86_64-linux-gnu/style-modules && /usr/bin/cmake -E 
> echo_append
> cd /<>/obj-x86_64-linux-gnu/style-modules && /usr/bin/cmake -E 
> echo_append
> cd /<>/build-modules && /usr/bin/cmake -P 
> /<>/obj-x86_64-linux-gnu/build-modules/CMakeFiles/build-modules.dir/ycm_localinstall__ee93a30a_11_files.cmake
> [ 92%] Files from find-modules installed in CMake build directory
> cd /<>/find-modules && /usr/bin/cmake -E touch 
> /<>/obj-x86_64-linux-gnu/find-modules/CMakeFiles/find-modules.dir/ycm_target-complete
> cd /<>/style-modules && /usr/bin/cmake -P 
> /<>/obj-x86_64-linux-gnu/style-modules/CMakeFiles/style-modules.dir/ycm_localinstall__a4831d43_8_files.cmake
> cd /<>/obj-x86_64-linux-gnu/build-modules && /usr/bin/cmake -E 
> touch 
> /<>/obj-x86_64-linux-gnu/build-modules/CMakeFiles/build-modules.dir/ycm_localinstall-complete
> make[4]: Leaving directory '/<>/obj-x86_64-linux-gnu'
> cd /<>/obj-x86_64-linux-gnu/style-modules && /usr/bin/cmake -E 
> touch 
> /<>/obj-x86_64-linux-gnu/style-modules/CMakeFiles/style-modules.dir/ycm_localinstall-complete
> [ 92%] Built target find-modules
> [ 94%] Files from build-modules installed in CMake build directory
> cd /<>/build-modules && /usr/bin/cmake -E touch 
> /<>/obj-x86_64-linux-gnu/build-modules/CMakeFiles/build-modules.dir/ycm_target-complete
> make[4]: Leaving directory '/<>/obj-x86_64-linux-gnu'
> [ 97%] Files from style-modules installed in CMake build directory
> cd /<>/style-modules && /usr/bin/cmake -E touch 
> /<>/obj-x86_64-linux-gnu/style-modules/CMakeFiles/style-modules.dir/ycm_target-complete
> [ 97%] Built target build-modules
> make[4]: Leaving directory '/<>/obj-x86_64-linux-gnu'
> [ 97%] Built target style-modules
> WARNING: favicon file 'ycm-favicon.ico' does not exist
> 
> Exception occurred:
>   File "/usr/lib/python3/dist-packages/sphinx/ext/extlinks.py", line 103, in 
> role
> title = caption % part
> ^~
> TypeError: not all arguments converted during string formatting
> The full traceback has been saved in /tmp/sphinx-err-o3geempv.log, if you 
> want to report the issue to the develop

Bug#1054738: marked as pending in python-gffutils

2023-11-04 Thread Nilesh Patra 
Control: tag -1 pending

Hello,

Bug #1054738 in python-gffutils 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/python-gffutils/-/commit/72da5f97d5f9948ca9f751a8f299f3664d9e9714


Add patch to fixup faulty version parsing (Closes: #1054738)


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1054738

Bug#1054949: marked as done (haskell-lambdabot-trusted: FTBFS: unsatisfiable build-dependencies: libghc-base-dev-4.15.1.0-6a406, libghc-http-dev-4000.3.16-b345c, libghc-network-dev-3.1.2.7-bb8a0, libg

2023-11-04 Thread Debian Bug Tracking System 
Your message dated Sat, 04 Nov 2023 21:34:57 +
with message-id 
and subject line Bug#1054949: fixed in haskell-lambdabot-trusted 5.3.1.1-1
has caused the Debian Bug report #1054949,
regarding haskell-lambdabot-trusted: FTBFS: unsatisfiable build-dependencies: 
libghc-base-dev-4.15.1.0-6a406, libghc-http-dev-4000.3.16-b345c, 
libghc-network-dev-3.1.2.7-bb8a0, libghc-network-uri-dev-2.6.4.1-35b94, 
haddock-interface-38, libghc-base-prof-4.15.1.0-6a406, 
libghc-http-prof-4000.3.16-b345c, libghc-network-prof-3.1.2.7-bb8a0, 
libghc-network-uri-prof-2.6.4.1-35b94
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.)


-- 
1054949: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1054949
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: haskell-lambdabot-trusted
Version: 5.3.1-1
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20231028 ftbfs-trixie

Hi,

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


Relevant part (hopefully):
> +--+
> | Install package build dependencies  
>  |
> +--+
> 
> 
> Setup apt archive
> -
> 
> Merged Build-Depends: cdbs, debhelper (>= 10), ghc (>= 8), ghc-prof, 
> haskell-devscripts (>= 0.13), libghc-oeis-dev (>= 0.3.1), libghc-oeis-prof, 
> libghc-quickcheck-safe-dev (>= 0.1), libghc-quickcheck-safe-prof, 
> libghc-quickcheck2-dev (>= 2), libghc-quickcheck2-prof (>= 2), 
> build-essential, fakeroot, ghc-doc, libghc-oeis-doc, 
> libghc-quickcheck-safe-doc, libghc-quickcheck2-doc (>= 2)
> Filtered Build-Depends: cdbs, debhelper (>= 10), ghc (>= 8), ghc-prof, 
> haskell-devscripts (>= 0.13), libghc-oeis-dev (>= 0.3.1), libghc-oeis-prof, 
> libghc-quickcheck-safe-dev (>= 0.1), libghc-quickcheck-safe-prof, 
> libghc-quickcheck2-dev (>= 2), libghc-quickcheck2-prof (>= 2), 
> build-essential, fakeroot, ghc-doc, libghc-oeis-doc, 
> libghc-quickcheck-safe-doc, libghc-quickcheck2-doc (>= 2)
> dpkg-deb: building package 'sbuild-build-depends-main-dummy' in 
> '/<>/apt_archive/sbuild-build-depends-main-dummy.deb'.
> Ign:1 copy:/<>/apt_archive ./ InRelease
> Get:2 copy:/<>/apt_archive ./ Release [609 B]
> Ign:3 copy:/<>/apt_archive ./ Release.gpg
> Get:4 copy:/<>/apt_archive ./ Sources [949 B]
> Get:5 copy:/<>/apt_archive ./ Packages [961 B]
> Fetched 2519 B in 0s (0 B/s)
> Reading package lists...
> Reading package lists...
> 
> Install main build dependencies (apt-based resolver)
> 
> 
> Installing build dependencies
> Reading package lists...
> Building dependency tree...
> Reading state information...
> Some packages could not be installed. This may mean that you have
> requested an impossible situation or if you are using the unstable
> distribution that some required packages have not yet been created
> or been moved out of Incoming.
> The following information may help to resolve the situation:
> 
> The following packages have unmet dependencies:
>  libghc-oeis-dev : Depends: libghc-base-dev-4.15.1.0-6a406 but it is not 
> installable
>Depends: libghc-http-dev-4000.3.16-b345c but it is not 
> installable
>Depends: libghc-network-dev-3.1.2.7-bb8a0 but it is not 
> installable
>Depends: libghc-network-uri-dev-2.6.4.1-35b94 but it is 
> not installable
>  libghc-oeis-doc : Depends: haddock-interface-38 but it is not installable
>  libghc-oeis-prof : Depends: libghc-base-prof-4.15.1.0-6a406 but it is not 
> installable
> Depends: libghc-http-prof-4000.3.16-b345c but it is not 
> installable
> Depends: libghc-network-prof-3.1.2.7-bb8a0 but it is not 
> installable
> Depends: libghc-network-uri-prof-2.6.4.1-35b94 but it is 
> not installable
> E: Unable to correct problems, you have held broken packages.
> apt-get failed.


The full build log is available from:
http://qa-logs.debian.net/2023/10/28/haskell-lambdabot-trusted_5.3.1-1_unstable.log

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

A list of current common problems

Bug#1054983: marked as done (haskell-copilot-prettyprinter: FTBFS: build-dependency not installable: haddock-interface-38)

2023-11-04 Thread Debian Bug Tracking System 
Your message dated Sat, 04 Nov 2023 21:34:40 +
with message-id 
and subject line Bug#1054983: fixed in haskell-copilot-prettyprinter 3.16.1-1
has caused the Debian Bug report #1054983,
regarding haskell-copilot-prettyprinter: FTBFS: build-dependency not 
installable: haddock-interface-38
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.)


-- 
1054983: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1054983
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: haskell-copilot-prettyprinter
Version: 3.13-1
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20231028 ftbfs-trixie

Hi,

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


Relevant part (hopefully):
> +--+
> | Install package build dependencies  
>  |
> +--+
> 
> 
> Setup apt archive
> -
> 
> Merged Build-Depends: debhelper (>= 10), haskell-devscripts-minimal | 
> haskell-devscripts (>= 0.13), cdbs, ghc, ghc-prof, libghc-copilot-core-dev 
> (>= 3.13), libghc-copilot-core-dev (<< 3.14), libghc-copilot-core-prof, 
> build-essential, fakeroot, ghc-doc, libghc-copilot-core-doc
> Filtered Build-Depends: debhelper (>= 10), haskell-devscripts-minimal, cdbs, 
> ghc, ghc-prof, libghc-copilot-core-dev (>= 3.13), libghc-copilot-core-dev (<< 
> 3.14), libghc-copilot-core-prof, build-essential, fakeroot, ghc-doc, 
> libghc-copilot-core-doc
> dpkg-deb: building package 'sbuild-build-depends-main-dummy' in 
> '/<>/apt_archive/sbuild-build-depends-main-dummy.deb'.
> Ign:1 copy:/<>/apt_archive ./ InRelease
> Get:2 copy:/<>/apt_archive ./ Release [609 B]
> Ign:3 copy:/<>/apt_archive ./ Release.gpg
> Get:4 copy:/<>/apt_archive ./ Sources [841 B]
> Get:5 copy:/<>/apt_archive ./ Packages [822 B]
> Fetched 2272 B in 0s (0 B/s)
> Reading package lists...
> Reading package lists...
> 
> Install main build dependencies (apt-based resolver)
> 
> 
> Installing build dependencies
> Reading package lists...
> Building dependency tree...
> Reading state information...
> Some packages could not be installed. This may mean that you have
> requested an impossible situation or if you are using the unstable
> distribution that some required packages have not yet been created
> or been moved out of Incoming.
> The following information may help to resolve the situation:
> 
> The following packages have unmet dependencies:
>  libghc-copilot-core-doc : Depends: haddock-interface-38 but it is not 
> installable
> E: Unable to correct problems, you have held broken packages.
> apt-get failed.


The full build log is available from:
http://qa-logs.debian.net/2023/10/28/haskell-copilot-prettyprinter_3.13-1_unstable.log

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

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

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

If you fail to reproduce this, please provide a build log and diff it with mine
so that we can identify if something relevant changed in the meantime.
--- End Message ---
--- Begin Message ---
Source: haskell-copilot-prettyprinter
Source-Version: 3.16.1-1
Done: Ilias Tsitsimpis 

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

Debian distribution maintenance software
pp.
Ilias Tsitsimpis  (supplier of updated 
haskell-copilot-prettyprinter 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 m

Bug#1054924: marked as done (haskell-lambdabot-reference-plugins: FTBFS: unsatisfiable build-dependencies: libghc-base-dev-4.15.1.0-6a406, libghc-binary-dev-0.8.8.0-507cc, libghc-bytestring-dev-0.10.1

2023-11-04 Thread Debian Bug Tracking System 
Your message dated Sat, 04 Nov 2023 21:34:48 +
with message-id 
and subject line Bug#1054924: fixed in haskell-lambdabot-reference-plugins 
5.3.1.1-1
has caused the Debian Bug report #1054924,
regarding haskell-lambdabot-reference-plugins: FTBFS: unsatisfiable 
build-dependencies: libghc-base-dev-4.15.1.0-6a406, 
libghc-binary-dev-0.8.8.0-507cc, libghc-bytestring-dev-0.10.12.1-ced9a, 
libghc-containers-dev-0.6.4.1-31c3b, libghc-dependent-map-dev-0.4.0.0-f824e, 
libghc-dependent-sum-dev-0.7.1.0-2fd03, 
libghc-dependent-sum-template-dev-0.1.1.1-62abf, 
libghc-directory-dev-1.3.6.2-311c9, libghc-edit-distance-dev-0.2.2.1-cc475, 
libghc-exceptions-dev-0.10.4-c14ff, libghc-filepath-dev-1.4.2.1-4459f, 
libghc-haskeline-dev-0.8.2-83f75, libghc-hslogger-dev-1.3.1.0-d393e, 
libghc-http-dev-4000.3.16-b345c, libghc-lifted-base-dev-0.2.3.12-e0695, 
libghc-monad-control-dev-1.0.3.1-20361, libghc-mtl-dev-2.2.2-e3bae, 
libghc-network-bsd-dev-2.8.1.0-726d3, libghc-network-dev-3.1.2.7-bb8a0, 
libghc-parsec-dev-3.1.14.0-377f0, libghc-prim-uniq-dev-0.2-b082a, 
libghc-random-dev-1.2.1.1-f840d, libghc-random-fu-dev-0.3.0.0-f7738, 
libghc-regex-tdfa-dev-1.3.2-1c748, libghc-safesemaphore-dev-0.10.1-b4f2a, 
libghc-split-dev-0.2.3.5-0c13f, libghc-syb-dev-0.7.2.2-ec1fd, 
libghc-template-haskell-dev-2.17.0.0-7274a, libghc-time-dev-1.9.3-bda76, 
libghc-transformers-base-dev-0.4.6-a0a78, 
libghc-transformers-dev-0.5.6.2-fc6f3, libghc-unix-dev-2.7.2.2-bdab4, 
libghc-utf8-string-dev-1.0.2-a50cd, libghc-zlib-dev-0.6.3.0-57e0e, 
haddock-interface-38, libghc-base-prof-4.15.1.0-6a406, 
libghc-binary-prof-0.8.8.0-507cc, libghc-bytestring-prof-0.10.12.1-ced9a, 
libghc-containers-prof-0.6.4.1-31c3b, libghc-dependent-map-prof-0.4.0.0-f824e, 
libghc-dependent-sum-prof-0.7.1.0-2fd03, 
libghc-dependent-sum-template-prof-0.1.1.1-62abf, 
libghc-directory-prof-1.3.6.2-311c9, libghc-edit-distance-prof-0.2.2.1-cc475, 
libghc-exceptions-prof-0.10.4-c14ff, libghc-filepath-prof-1.4.2.1-4459f, 
libghc-haskeline-prof-0.8.2-83f75, libghc-hslogger-prof-1.3.1.0-d393e, 
libghc-http-prof-4000.3.16-b345c, libghc-lifted-base-prof-0.2.3.12-e0695, 
libghc-monad-control-prof-1.0.3.1-20361, libghc-mtl-prof-2.2.2-e3bae, 
libghc-network-bsd-prof-2.8.1.0-726d3, libghc-network-prof-3.1.2.7-bb8a0, 
libghc-parsec-prof-3.1.14.0-377f0, libghc-prim-uniq-prof-0.2-b082a, 
libghc-random-fu-prof-0.3.0.0-f7738, libghc-random-prof-1.2.1.1-f840d, 
libghc-regex-tdfa-prof-1.3.2-1c748, libghc-safesemaphore-prof-0.10.1-b4f2a, 
libghc-split-prof-0.2.3.5-0c13f, libghc-syb-prof-0.7.2.2-ec1fd, 
libghc-template-haskell-prof-2.17.0.0-7274a, libghc-time-prof-1.9.3-bda76, 
libghc-transformers-base-prof-0.4.6-a0a78, 
libghc-transformers-prof-0.5.6.2-fc6f3, libghc-unix-prof-2.7.2.2-bdab4, 
libghc-utf8-string-prof-1.0.2-a50cd, libghc-zlib-prof-0.6.3.0-57e0e, 
libghc-base-dev-4.15.1.0-6a406, libghc-http-dev-4000.3.16-b345c, 
libghc-network-dev-3.1.2.7-bb8a0, libghc-network-uri-dev-2.6.4.1-35b94, 
haddock-interface-38, libghc-base-prof-4.15.1.0-6a406, 
libghc-http-prof-4000.3.16-b345c, libghc-network-prof-3.1.2.7-bb8a0, 
libghc-network-uri-prof-2.6.4.1-35b94
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.)


-- 
1054924: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1054924
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: haskell-lambdabot-reference-plugins
Version: 5.3.1-1
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20231028 ftbfs-trixie

Hi,

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


Relevant part (hopefully):
> +--+
> | Install package build dependencies  
>  |
> +--+
> 
> 
> Setup apt archive
> -
> 
> Merged Build-Depends: cdbs, debhelper (>= 10), ghc (>= 8.4.3), ghc-prof, 
> haskell-devscripts (>= 0.13), libghc-http-dev (>= 1:4000), libghc-http-prof, 
> libghc-lambdabot-core-dev (>= 5.3), libghc-lambdabot-core-dev (<< 5.4), 
> libghc-lambdabot-core-prof, libghc-network-dev (>= 2.7), libghc-network-dev 
> (<< 3.2), libghc-network-prof, libghc-network-uri-dev (>= 2.6), 
> libghc-network-uri-dev (<< 2.7), libghc-network-uri-prof, libghc-oeis-dev (>= 
> 0.3.1), libghc-oeis-prof, libghc-regex-tdfa-dev (>= 1.1), 
> libghc-regex-tdfa-prof, libghc-split-dev (>= 0.2), libghc-split-prof, 
> libghc-tagsoup-dev (>= 0.12), libghc-tagsoup-prof, libghc-utf8-string-dev (>= 
> 0.3), l

Bug#1054717: marked as done (haskell-copilot-c99: FTBFS: build-dependency not installable: haddock-interface-38)

2023-11-04 Thread Debian Bug Tracking System 
Your message dated Sat, 04 Nov 2023 21:34:31 +
with message-id 
and subject line Bug#1054717: fixed in haskell-copilot-c99 3.16.1-1
has caused the Debian Bug report #1054717,
regarding haskell-copilot-c99: FTBFS: build-dependency not installable: 
haddock-interface-38
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.)


-- 
1054717: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1054717
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: haskell-copilot-c99
Version: 3.13-1
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20231027 ftbfs-trixie

Hi,

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


Relevant part (hopefully):
> +--+
> | Install package build dependencies  
>  |
> +--+
> 
> 
> Setup apt archive
> -
> 
> Merged Build-Depends: debhelper (>= 10), haskell-devscripts-minimal | 
> haskell-devscripts (>= 0.13), cdbs, ghc, ghc-prof, libghc-copilot-core-dev 
> (>= 3.13), libghc-copilot-core-dev (<< 3.14), libghc-copilot-core-prof, 
> libghc-language-c99-dev (>= 0.2.0), libghc-language-c99-dev (<< 0.3), 
> libghc-language-c99-prof, libghc-language-c99-simple-dev (>= 0.2.2), 
> libghc-language-c99-simple-dev (<< 0.3), libghc-language-c99-simple-prof, 
> build-essential, fakeroot, ghc-doc, libghc-copilot-core-doc, 
> libghc-language-c99-doc, libghc-language-c99-simple-doc
> Filtered Build-Depends: debhelper (>= 10), haskell-devscripts-minimal, cdbs, 
> ghc, ghc-prof, libghc-copilot-core-dev (>= 3.13), libghc-copilot-core-dev (<< 
> 3.14), libghc-copilot-core-prof, libghc-language-c99-dev (>= 0.2.0), 
> libghc-language-c99-dev (<< 0.3), libghc-language-c99-prof, 
> libghc-language-c99-simple-dev (>= 0.2.2), libghc-language-c99-simple-dev (<< 
> 0.3), libghc-language-c99-simple-prof, build-essential, fakeroot, ghc-doc, 
> libghc-copilot-core-doc, libghc-language-c99-doc, 
> libghc-language-c99-simple-doc
> dpkg-deb: building package 'sbuild-build-depends-main-dummy' in 
> '/<>/apt_archive/sbuild-build-depends-main-dummy.deb'.
> Ign:1 copy:/<>/apt_archive ./ InRelease
> Get:2 copy:/<>/apt_archive ./ Release [615 B]
> Ign:3 copy:/<>/apt_archive ./ Release.gpg
> Get:4 copy:/<>/apt_archive ./ Sources [ B]
> Get:5 copy:/<>/apt_archive ./ Packages [1092 B]
> Fetched 2818 B in 0s (0 B/s)
> Reading package lists...
> Reading package lists...
> 
> Install main build dependencies (apt-based resolver)
> 
> 
> Installing build dependencies
> Reading package lists...
> Building dependency tree...
> Some packages could not be installed. This may mean that you have
> requested an impossible situation or if you are using the unstable
> distribution that some required packages have not yet been created
> or been moved out of Incoming.
> The following information may help to resolve the situation:
> 
> The following packages have unmet dependencies:
>  libghc-copilot-core-doc : Depends: haddock-interface-38 but it is not 
> installable
> E: Unable to correct problems, you have held broken packages.
> apt-get failed.


The full build log is available from:
http://qa-logs.debian.net/2023/10/27/haskell-copilot-c99_3.13-1_unstable.log

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

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

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

If you fail to reproduce this, please provide a build log and diff it with mine
so that we can identify if something relevant changed in the meantime.
--- End Message ---
--- Begin Message ---
Source: haskell-copilot-c99
Source-Version: 3.16.1-1
Done: Ilias Tsitsimpis 

We believe that the bug you reported is fixed in the latest version of
haskell-copilot-c99, 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.

Than

Bug#1052852: python-django-crispy-forms: FTBFS: make[1]: *** [debian/rules:17: override_dh_auto_test] Error 1

2023-11-04 Thread s3v 
Dear Maintainer

After applying this commit [1], I was able to build successfully your
package in a sid chroot environment.
I've also tried to build against sphinx 7.2.6-1 + python-docutils
0.20.1+dfsg-1 in experimental and no problems were spotted.

Kind Regards

[1] https://github.com/django-crispy-forms/django-crispy-forms/pull/1257

Bug#1051901: 1.2.10 breaks ability to play audio using i386 binaries on amd64 host

2023-11-04 Thread Dirk Griesbach 

Am Mo, 23. Okt 2023 um 18:31:26 -0400 schrieb Stefan Monnier:

I'd go so far to think that this is not constrained to i386 binaries on
amd64 hosts. `aplay /dev/zero` segfaults on a plain i386 host with asound
1.2.10. Downgrading to 1.2.9 helps.


Is this the same as https://github.com/alsa-project/alsa-lib/issues/352 ?


Seems to be the case. Sound is working again with the patches applied.

Thanks,
Dirk

Bug#1055255: marked as done (matrix-synapse: CVE-2023-43796)

2023-11-04 Thread Debian Bug Tracking System 
Your message dated Sat, 04 Nov 2023 20:37:48 +
with message-id 
and subject line Bug#1055255: fixed in matrix-synapse 1.95.1-1
has caused the Debian Bug report #1055255,
regarding matrix-synapse: CVE-2023-43796
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.)


-- 
1055255: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1055255
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: matrix-synapse
Version: 1.95.0-1
Severity: grave
Tags: security upstream
X-Debbugs-Cc: car...@debian.org, Debian Security Team 

Hi,

The following vulnerability was published for matrix-synapse.

CVE-2023-43796[0]:
| Synapse is an open-source Matrix homeserver Prior to versions 1.95.1
| and 1.96.0rc1, cached device information of remote users can be
| queried from Synapse. This can be used to enumerate the remote users
| known to a homeserver. System administrators are encouraged to
| upgrade to Synapse 1.95.1 or 1.96.0rc1 to receive a patch. As a
| workaround, the `federation_domain_whitelist` can be used to limit
| federation traffic with a homeserver.


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

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2023-43796
https://www.cve.org/CVERecord?id=CVE-2023-43796
[1] 
https://github.com/matrix-org/synapse/security/advisories/GHSA-mp92-3jfm-3575
[2] 
https://github.com/matrix-org/synapse/commit/daec55e1fe120c564240c5386e77941372bf458f
 

Regards,
Salvatore
--- End Message ---
--- Begin Message ---
Source: matrix-synapse
Source-Version: 1.95.1-1
Done: Andrej Shadura 

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

Debian distribution maintenance software
pp.
Andrej Shadura  (supplier of updated 
matrix-synapse 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, 04 Nov 2023 21:12:29 +0100
Source: matrix-synapse
Architecture: source
Version: 1.95.1-1
Distribution: unstable
Urgency: high
Maintainer: Matrix Packaging Team 

Changed-By: Andrej Shadura 
Closes: 1055255
Changes:
 matrix-synapse (1.95.1-1) unstable; urgency=high
 .
   * New upstream release (CVE-2023-43796, Closes: #1055255).
Checksums-Sha1:
 81cf22ffc36f0ea9e40a15d8da904ee8aaa3e2d9 3216 matrix-synapse_1.95.1-1.dsc
 f9955b09a05842714210ad2ed5744b22b2df8fe4 8404523 
matrix-synapse_1.95.1.orig.tar.gz
 299977100afd8e532ca7f3ea21d7110d83664bb7 114988 
matrix-synapse_1.95.1-1.debian.tar.xz
Checksums-Sha256:
 4fcba3df608ab2de48d5f6a6d74c8663873abe2c337f9574f0dbe0330cf2981a 3216 
matrix-synapse_1.95.1-1.dsc
 72eb37eda94e4dad276f81d5a20c31782ba120fada0d6ac4d3efe0e8dfe642be 8404523 
matrix-synapse_1.95.1.orig.tar.gz
 4108a60948af9f79e774ccd860df082dd226986af6958bcb93a7054a5665b009 114988 
matrix-synapse_1.95.1-1.debian.tar.xz
Files:
 925e07c34c5e581c8b2454254e5b44d0 3216 net optional matrix-synapse_1.95.1-1.dsc
 7ff0626e16c0707df294b70eb3336522 8404523 net optional 
matrix-synapse_1.95.1.orig.tar.gz
 e90e17d1f43c447dc0337abd05903e05 114988 net optional 
matrix-synapse_1.95.1-1.debian.tar.xz

-BEGIN PGP SIGNATURE-

iHUEARYIAB0WIQSD3NF/RLIsyDZW7aHoRGtKyMdyYQUCZUamOQAKCRDoRGtKyMdy
YdvLAQDUWPhSmKeoLilMa4Q0NrXloBe1dGtxAFUIdCKAR4W3ogEAs2Qqmy7PaS1l
5LGh97l0flsZ79zaKpKElSGnwNI4tAg=
=tD+v
-END PGP SIGNATURE End Message ---

Bug#1055348: jetty9: Update from DLA 3641 breaks puppetdb ("Exception in thread "main" java.lang.IllegalStateException: KeyStores with multiple certificates are not supported on the base class org.ecl

2023-11-04 Thread Markus Koschany 
Hello,

Am Samstag, dem 04.11.2023 um 17:03 + schrieb Adam D. Barratt:
> Source: jetty9
> Version: 9.4.50-4+deb10u1
> Severity: serious
> X-Debbugs-Cc: d...@debian.org
> 
> Hi,
> 
> Upgrading libjetty9-java and libjetty9-extra-java to the version from
> DLA 3641-1 reliably causes PuppetDB to fail to start, with the
> stacktrace shown below. Downgrading resolves the issue.
> 
> I'm not sure which keystore is being referred to, but none of the files
> listed in /etc/puppetdb/conf.d/jetty.ini appear to contain more than a
> single certificate.

thanks for the report. This looks like a bug in trapperkeeper-webserver-jetty9-
clojure to me. Upstream commit

https://github.com/puppetlabs/trapperkeeper-webserver-jetty9/commit/3ee6a410436c1a236ca33d511c5373c3328054ef

appears to address the problem. The version in Buster lacks the
InternalSslContextFactory class though. Instead the deprecated
SslContextFactory class is referenced in jetty9_config.clj and
jetty9_core.clj. 

My first idea is to change SslContextFactory occurrences to
SslContextFactory.Server.

Backporting the version of trapperkeeper-webserver-jetty9-clojure from Bullseye
to Buster is the second one. AFAICS puppetdb and puppetserver are the only
consumers.

Could you install the version of trapperkeeper-webserver-jetty9-clojure from
Bullseye and reinstall the jetty9 security update and report back if this
solves your problem?

Regards,

Markus


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

Bug#1054706: marked as done (e-antic: FTBFS: ../../../libeantic/test/main.cpp:4:10: fatal error: catch2/catch.hpp: No such file or directory)

2023-11-04 Thread Debian Bug Tracking System 
Your message dated Sat, 04 Nov 2023 19:04:06 +
with message-id 
and subject line Bug#1054706: fixed in e-antic 1.3.0+ds1-1
has caused the Debian Bug report #1054706,
regarding e-antic: FTBFS: ../../../libeantic/test/main.cpp:4:10: fatal error: 
catch2/catch.hpp: No such file or directory
to be marked as done.

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

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


-- 
1054706: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1054706
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: e-antic
Version: 1.3.0+ds-1
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20231027 ftbfs-trixie

Hi,

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


Relevant part (hopefully):
> g++ -DHAVE_CONFIG_H -I. -I../../../libeantic/test -I../e-antic  -isystem 
> "/<>/_BUILD/libeantic/../../libeantic/test/external/cereal/include"
>  -I./.. -Wdate-time -D_FORTIFY_SOURCE=2  -g -O2 
> -ffile-prefix-map=/<>=. -fstack-protector-strong 
> -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -c 
> -o renfxx/t-assignment.o ../../../libeantic/test/renfxx/t-assignment.cpp
> ../../../libeantic/test/main.cpp:4:10: fatal error: catch2/catch.hpp: No such 
> file or directory
> 4 | #include 
>   |  ^~
> compilation terminated.
> make[5]: *** [Makefile:1495: main.o] Error 1


The full build log is available from:
http://qa-logs.debian.net/2023/10/27/e-antic_1.3.0+ds-1_unstable.log

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

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

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

If you fail to reproduce this, please provide a build log and diff it with mine
so that we can identify if something relevant changed in the meantime.
--- End Message ---
--- Begin Message ---
Source: e-antic
Source-Version: 1.3.0+ds1-1
Done: Jerome Benoit 

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

Debian distribution maintenance software
pp.
Jerome Benoit  (supplier of updated e-antic 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, 04 Nov 2023 18:57:20 +
Source: e-antic
Architecture: source
Version: 1.3.0+ds1-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Math Team 
Changed-By: Jerome Benoit 
Closes: 1054706
Changes:
 e-antic (1.3.0+ds1-1) unstable; urgency=medium
 .
   * FTBFS fix release, migration to catch v3 has not yet been performed.
   * Debianization:
 - d/{copyright,control}, now use catch2 material as provided by
 the e-antic upstream team (Closes: #1054706);
 - d/watch, allow Debian Source suffix with a numerical index;
 - d/p/debianization-no_external.patch, obsoleted;
 - d/control:
   - Standards-Version, bump to version 4.6.2 (no change).
Checksums-Sha1:
 aea5a0d61b48b76685829eda47c2fcabcc043bd6 2842 e-antic_1.3.0+ds1-1.dsc
 14890e5c7be116a8693b9036370d30b94e77c226 206404 e-antic_1.3.0+ds1.orig.tar.xz
 98655fc0675eb17bfb676927fc6334d33c8cb272 8740 e-antic_1.3.0+ds1-1.debian.tar.xz
 fc04558f46102dc3505d9ef6f3f39ee443b6ea0b 7171 
e-antic_1.3.0+ds1-1_source.buildinfo
Checksums-Sha256:
 724b1fba96cda4b0ba61b2d8d21ec650db107880145a95614f9049447a9eb99a 2842 
e-antic_1.3.0+ds1-1.dsc
 0bac83d1b63a488f20e34d2d1158e3650eb5527412dceeba23cd6fac11643b6c 206404 
e-antic_1.3.0+ds1.orig.tar.xz
 234f590f6d94e965a505e8b3d7b6f2a56721dab33696cfdcab389b56715f7988 8740 
e-antic_1.3.0+ds1-1.debian.tar.xz
 2c0c5382872fd40fcd0818bab24c7346f4b62a94758229c9c730bce6b83279a1 7171

Bug#1054706: e-antic: FTBFS: ../../../libeantic/test/main.cpp:4:10: fatal error: catch2/catch.hpp: No such file or directory

2023-11-04 Thread Jerome BENOIT 

Hello,
as the migration to catch2 v3 appeared not simple,
I finally used the catch2 material provided by the e-antic upstream team.
Best wishes, Jerome
--
Jerome BENOIT | calculus+at-rezozer^dot*net
https://qa.debian.org/developer.php?login=calcu...@rezozer.net
AE28 AE15 710D FF1D 87E5  A762 3F92 19A6 7F36 C68B


OpenPGP_signature
Description: OpenPGP digital signature

Bug#1042585: marked as done (python-i3ipc: FTBFS with Sphinx 7.1, docutils 0.20: TypeError: Python directive method get_signature_prefix() must return a list of nodes. Return value was 'coroutine '.)

2023-11-04 Thread Debian Bug Tracking System 
Your message dated Sat, 04 Nov 2023 18:54:18 +
with message-id 
and subject line Bug#1042585: fixed in python-i3ipc 2.2.1-3
has caused the Debian Bug report #1042585,
regarding python-i3ipc: FTBFS with Sphinx 7.1, docutils 0.20: TypeError: Python 
directive method get_signature_prefix() must return a list of nodes. Return 
value was 'coroutine '.
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.)


-- 
1042585: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1042585
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-i3ipc
Version: 2.2.1-2
Severity: important
Tags: ftbfs
User: python-modules-t...@lists.alioth.debian.org
Usertags: sphinx7.1

Hi,

python-i3ipc fails to build with Sphinx 7.1 and docutils 0.20, both of which
are currently available in experimental.

Relevant part (hopefully):
> make[2]: Entering directory '/<>/docs'
> sphinx-build -b html -d _build/doctrees   . _build/html
> Running Sphinx v7.1.1
> WARNING: Invalid configuration value found: 'language = None'. Update your 
> configuration to a valid language code. Falling back to 'en' (English).
> making output directory... done
> building [mo]: targets for 0 po files that are out of date
> writing output... 
> building [html]: targets for 7 source files that are out of date
> updating environment: [new config] 7 added, 0 changed, 0 removed
> reading sources... [ 14%] aio-con
> 
> Exception occurred:
>   File "/usr/lib/python3/dist-packages/sphinx/domains/python.py", line 774, 
> in handle_signature
> raise TypeError(
> TypeError: Python directive method get_signature_prefix() must return a list 
> of nodes. Return value was 'coroutine '.
> The full traceback has been saved in /tmp/sphinx-err-h3j0blvn.log, if you 
> want to report the issue to the developers.
> Please also report this if it was a user error, so that a better error 
> message can be provided next time.
> A bug report can be filed in the tracker at 
> . Thanks!
> make[2]: *** [Makefile:54: html] Error 2


The full build log is available from:
http://qa-logs.debian.net/2023/07/30/exp/python-i3ipc_2.2.1-2_unstable_sphinx-exp.log

Please see [1] for Sphinx changelog and [2] for Docutils changelog.

Also see [3] for the list of deprecated/removed APIs in Sphinx and possible
alternatives to them.

Some notable changes in Sphinx 6 and Sphinx 7:

- Sphinx no longer includes jquery.js and underscore.js by default.
  Please use python3-sphinxcontrib.jquery package if you are using a custom
  template and it still needs jquery.

- The setup.py build_sphinx command was removed. Please instead call
  sphinx-build or "python3 -m sphinx" directly.

- For packages using the extlinks extension, the caption should contain
  exactly one "%s" placeholder (if caption is not None).

In case you have questions, please Cc sph...@packages.debian.org on reply.

[1]: https://www.sphinx-doc.org/en/master/changes.html
[2]: 
https://repo.or.cz/docutils.git/blob/refs/tags/docutils-0.20.1:/RELEASE-NOTES.txt
[3]: 
https://www.sphinx-doc.org/en/master/extdev/deprecated.html#dev-deprecated-apis

All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=sphinx7.1;users=python-modules-t...@lists.alioth.debian.org
or:
https://udd.debian.org/bugs/?release=na&merged=ign&fnewerval=7&flastmodval=7&fusertag=only&fusertagtag=sphinx7.1&fusertaguser=python-modules-t...@lists.alioth.debian.org&allbugs=1&cseverity=1&ctags=1&caffected=1#results

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
--- End Message ---
--- Begin Message ---
Source: python-i3ipc
Source-Version: 2.2.1-3
Done: Birger Schacht 

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

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

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

Debian distribution maintenance software
pp.
Birger Schacht  (supplier of updated python-i3ipc 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, 04 Nov 2023 19:19

Bug#1052347: src:canu: fails to migrate to testing for too long: unresolved RC issue

2023-11-04 Thread Paul Gevers 

Hi,

On 04-11-2023 14:11, Nilesh Patra wrote:

The upstream needs the *.out files of the failing tests, as they said at [1]. 
Since it does not work on porter box, and chokes on the CI infra, could you 
please provide these files?


At least two .out files are found in the artifacts tar ball, also 
attached to the upstream bug report by Michael. If those are not what 
you need, please be explicit which one you need. Also, you're in control 
of what goes into the artifacts tar ball, so you could also do it 
yourself. (But please be aware of bug #1050388 and don't put everything 
in the tar ball again).


Paul


OpenPGP_signature.asc
Description: OpenPGP digital signature

Bug#1042698: python-vispy: FTBFS with Sphinx 7.1, docutils 0.20: AttributeError: 'container' object has no attribute 'html5tagname'

2023-11-04 Thread Nilesh Patra 
Hi Lucas,

On Sun, 30 Jul 2023 20:33:09 +0200 Lucas Nussbaum  wrote:
> Source: python-vispy
> Version: 0.6.6-3
> Severity: important
> Tags: ftbfs

This seems to be an older version of vispy and the latest one in
bookworm no longer FTBFS with newer sphinx for me locally.

Could you please trigger a job on the latest vispy version as well so we
could close this?

Thanks!


signature.asc
Description: PGP signature

Bug#1054951: marked as done (haskell-lambdabot-irc-plugins: FTBFS: unsatisfiable build-dependencies: libghc-base-dev-4.15.1.0-6a406, libghc-binary-dev-0.8.8.0-507cc, libghc-bytestring-dev-0.10.12.1-ce

2023-11-04 Thread Debian Bug Tracking System 
Your message dated Sat, 04 Nov 2023 18:20:07 +
with message-id 
and subject line Bug#1054951: fixed in haskell-lambdabot-irc-plugins 5.3.1.1-1
has caused the Debian Bug report #1054951,
regarding haskell-lambdabot-irc-plugins: FTBFS: unsatisfiable 
build-dependencies: libghc-base-dev-4.15.1.0-6a406, 
libghc-binary-dev-0.8.8.0-507cc, libghc-bytestring-dev-0.10.12.1-ced9a, 
libghc-containers-dev-0.6.4.1-31c3b, libghc-dependent-map-dev-0.4.0.0-f824e, 
libghc-dependent-sum-dev-0.7.1.0-2fd03, 
libghc-dependent-sum-template-dev-0.1.1.1-62abf, 
libghc-directory-dev-1.3.6.2-311c9, libghc-edit-distance-dev-0.2.2.1-cc475, 
libghc-exceptions-dev-0.10.4-c14ff, libghc-filepath-dev-1.4.2.1-4459f, 
libghc-haskeline-dev-0.8.2-83f75, libghc-hslogger-dev-1.3.1.0-d393e, 
libghc-http-dev-4000.3.16-b345c, libghc-lifted-base-dev-0.2.3.12-e0695, 
libghc-monad-control-dev-1.0.3.1-20361, libghc-mtl-dev-2.2.2-e3bae, 
libghc-network-bsd-dev-2.8.1.0-726d3, libghc-network-dev-3.1.2.7-bb8a0, 
libghc-parsec-dev-3.1.14.0-377f0, libghc-prim-uniq-dev-0.2-b082a, 
libghc-random-dev-1.2.1.1-f840d, libghc-random-fu-dev-0.3.0.0-f7738, 
libghc-regex-tdfa-dev-1.3.2-1c748, libghc-safesemaphore-dev-0.10.1-b4f2a, 
libghc-split-dev-0.2.3.5-0c13f, libghc-syb-dev-0.7.2.2-ec1fd, 
libghc-template-haskell-dev-2.17.0.0-7274a, libghc-time-dev-1.9.3-bda76, 
libghc-transformers-base-dev-0.4.6-a0a78, 
libghc-transformers-dev-0.5.6.2-fc6f3, libghc-unix-dev-2.7.2.2-bdab4, 
libghc-utf8-string-dev-1.0.2-a50cd, libghc-zlib-dev-0.6.3.0-57e0e, 
haddock-interface-38, libghc-base-prof-4.15.1.0-6a406, 
libghc-binary-prof-0.8.8.0-507cc, libghc-bytestring-prof-0.10.12.1-ced9a, 
libghc-containers-prof-0.6.4.1-31c3b, libghc-dependent-map-prof-0.4.0.0-f824e, 
libghc-dependent-sum-prof-0.7.1.0-2fd03, 
libghc-dependent-sum-template-prof-0.1.1.1-62abf, 
libghc-directory-prof-1.3.6.2-311c9, libghc-edit-distance-prof-0.2.2.1-cc475, 
libghc-exceptions-prof-0.10.4-c14ff, libghc-filepath-prof-1.4.2.1-4459f, 
libghc-haskeline-prof-0.8.2-83f75, libghc-hslogger-prof-1.3.1.0-d393e, 
libghc-http-prof-4000.3.16-b345c, libghc-lifted-base-prof-0.2.3.12-e0695, 
libghc-monad-control-prof-1.0.3.1-20361, libghc-mtl-prof-2.2.2-e3bae, 
libghc-network-bsd-prof-2.8.1.0-726d3, libghc-network-prof-3.1.2.7-bb8a0, 
libghc-parsec-prof-3.1.14.0-377f0, libghc-prim-uniq-prof-0.2-b082a, 
libghc-random-fu-prof-0.3.0.0-f7738, libghc-random-prof-1.2.1.1-f840d, 
libghc-regex-tdfa-prof-1.3.2-1c748, libghc-safesemaphore-prof-0.10.1-b4f2a, 
libghc-split-prof-0.2.3.5-0c13f, libghc-syb-prof-0.7.2.2-ec1fd, 
libghc-template-haskell-prof-2.17.0.0-7274a, libghc-time-prof-1.9.3-bda76, 
libghc-transformers-base-prof-0.4.6-a0a78, 
libghc-transformers-prof-0.5.6.2-fc6f3, libghc-unix-prof-2.7.2.2-bdab4, 
libghc-utf8-string-prof-1.0.2-a50cd, libghc-zlib-prof-0.6.3.0-57e0e
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.)


-- 
1054951: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1054951
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: haskell-lambdabot-irc-plugins
Version: 5.3.1-1
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20231028 ftbfs-trixie

Hi,

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


Relevant part (hopefully):
> +--+
> | Install package build dependencies  
>  |
> +--+
> 
> 
> Setup apt archive
> -
> 
> Merged Build-Depends: cdbs, debhelper (>= 10), haskell-devscripts (>= 0.13), 
> ghc (>= 8.4.3), ghc-prof, libghc-safesemaphore-dev (>= 0.9), 
> libghc-safesemaphore-prof, libghc-lambdabot-core-dev (>= 5.3), 
> libghc-lambdabot-core-dev (<< 5.4), libghc-lambdabot-core-prof, 
> libghc-lifted-base-dev (>= 0.2), libghc-lifted-base-prof, libghc-network-dev 
> (>= 2.7), libghc-network-dev (<< 3.2), libghc-network-prof, libghc-split-dev 
> (>= 0.2), libghc-split-prof, build-essential, fakeroot, ghc-doc, 
> libghc-lambdabot-core-doc, libghc-lifted-base-doc, libghc-network-doc, 
> libghc-safesemaphore-doc, libghc-split-doc
> Filtered Build-Depends: cdbs, debhelper (>= 10), haskell-devscripts (>= 
> 0.13), ghc (>= 8.4.3), ghc-prof, libghc-safesemaphore-dev (>= 0.9), 
> libghc-safesemaphore-prof, libghc-lambdabot-core-dev (>= 5.3), 
> libghc-lambdabot-core-dev (<< 5.4), libghc-lambdabot-core-prof, 
> libghc-lifted-base-dev (>= 0.2), libghc-lifted-base-prof, libghc-network-dev 
> (>= 2.7), libghc-netw

Bug#1054948: marked as done (haskell-oeis: FTBFS: unsatisfiable build-dependency: libghc-http-dev (< 1:4000.4) but 1:4000.4.1-1+b1 is to be installed)

2023-11-04 Thread Debian Bug Tracking System 
Your message dated Sat, 04 Nov 2023 18:20:39 +
with message-id 
and subject line Bug#1054948: fixed in haskell-oeis 0.3.10-3
has caused the Debian Bug report #1054948,
regarding haskell-oeis: FTBFS: unsatisfiable build-dependency: libghc-http-dev 
(< 1:4000.4) but 1:4000.4.1-1+b1 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.)


-- 
1054948: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1054948
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: haskell-oeis
Version: 0.3.10-2
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20231028 ftbfs-trixie

Hi,

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


Relevant part (hopefully):
> +--+
> | Install package build dependencies  
>  |
> +--+
> 
> 
> Setup apt archive
> -
> 
> Merged Build-Depends: cdbs, debhelper (>= 10), ghc (>= 8), ghc-prof, 
> haskell-devscripts (>= 0.13), libghc-http-dev (<< 1:4000.4), libghc-http-dev 
> (>= 1:4000.2), libghc-http-prof, libghc-network-dev (>= 2.6), 
> libghc-network-prof, libghc-network-uri-dev (>= 2.6), 
> libghc-network-uri-prof, build-essential, fakeroot, ghc-doc, libghc-http-doc, 
> libghc-network-doc, libghc-network-uri-doc
> Filtered Build-Depends: cdbs, debhelper (>= 10), ghc (>= 8), ghc-prof, 
> haskell-devscripts (>= 0.13), libghc-http-dev (<< 1:4000.4), libghc-http-dev 
> (>= 1:4000.2), libghc-http-prof, libghc-network-dev (>= 2.6), 
> libghc-network-prof, libghc-network-uri-dev (>= 2.6), 
> libghc-network-uri-prof, build-essential, fakeroot, ghc-doc, libghc-http-doc, 
> libghc-network-doc, libghc-network-uri-doc
> dpkg-deb: building package 'sbuild-build-depends-main-dummy' in 
> '/<>/apt_archive/sbuild-build-depends-main-dummy.deb'.
> Ign:1 copy:/<>/apt_archive ./ InRelease
> Get:2 copy:/<>/apt_archive ./ Release [609 B]
> Ign:3 copy:/<>/apt_archive ./ Release.gpg
> Get:4 copy:/<>/apt_archive ./ Sources [947 B]
> Get:5 copy:/<>/apt_archive ./ Packages [959 B]
> Fetched 2515 B in 0s (0 B/s)
> Reading package lists...
> Reading package lists...
> 
> Install main build dependencies (apt-based resolver)
> 
> 
> Installing build dependencies
> Reading package lists...
> Building dependency tree...
> Reading state information...
> Some packages could not be installed. This may mean that you have
> requested an impossible situation or if you are using the unstable
> distribution that some required packages have not yet been created
> or been moved out of Incoming.
> The following information may help to resolve the situation:
> 
> The following packages have unmet dependencies:
>  sbuild-build-depends-main-dummy : Depends: libghc-http-dev (< 1:4000.4) but 
> 1:4000.4.1-1+b1 is to be installed
> E: Unable to correct problems, you have held broken packages.
> apt-get failed.


The full build log is available from:
http://qa-logs.debian.net/2023/10/28/haskell-oeis_0.3.10-2_unstable.log

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

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

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

If you fail to reproduce this, please provide a build log and diff it with mine
so that we can identify if something relevant changed in the meantime.
--- End Message ---
--- Begin Message ---
Source: haskell-oeis
Source-Version: 0.3.10-3
Done: Ilias Tsitsimpis 

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

Debian distribution maintenance software
pp.
Ili

Bug#1054964: marked as done (haskell-lambdabot-novelty-plugins: FTBFS: unsatisfiable build-dependencies: libghc-base-dev-4.15.1.0-6a406, libghc-binary-dev-0.8.8.0-507cc, libghc-bytestring-dev-0.10.12.

2023-11-04 Thread Debian Bug Tracking System 
Your message dated Sat, 04 Nov 2023 18:20:24 +
with message-id 
and subject line Bug#1054964: fixed in haskell-lambdabot-novelty-plugins 
5.3.1.1-1
has caused the Debian Bug report #1054964,
regarding haskell-lambdabot-novelty-plugins: FTBFS: unsatisfiable 
build-dependencies: libghc-base-dev-4.15.1.0-6a406, 
libghc-binary-dev-0.8.8.0-507cc, libghc-bytestring-dev-0.10.12.1-ced9a, 
libghc-containers-dev-0.6.4.1-31c3b, libghc-dependent-map-dev-0.4.0.0-f824e, 
libghc-dependent-sum-dev-0.7.1.0-2fd03, 
libghc-dependent-sum-template-dev-0.1.1.1-62abf, 
libghc-directory-dev-1.3.6.2-311c9, libghc-edit-distance-dev-0.2.2.1-cc475, 
libghc-exceptions-dev-0.10.4-c14ff, libghc-filepath-dev-1.4.2.1-4459f, 
libghc-haskeline-dev-0.8.2-83f75, libghc-hslogger-dev-1.3.1.0-d393e, 
libghc-http-dev-4000.3.16-b345c, libghc-lifted-base-dev-0.2.3.12-e0695, 
libghc-monad-control-dev-1.0.3.1-20361, libghc-mtl-dev-2.2.2-e3bae, 
libghc-network-bsd-dev-2.8.1.0-726d3, libghc-network-dev-3.1.2.7-bb8a0, 
libghc-parsec-dev-3.1.14.0-377f0, libghc-prim-uniq-dev-0.2-b082a, 
libghc-random-dev-1.2.1.1-f840d, libghc-random-fu-dev-0.3.0.0-f7738, 
libghc-regex-tdfa-dev-1.3.2-1c748, libghc-safesemaphore-dev-0.10.1-b4f2a, 
libghc-split-dev-0.2.3.5-0c13f, libghc-syb-dev-0.7.2.2-ec1fd, 
libghc-template-haskell-dev-2.17.0.0-7274a, libghc-time-dev-1.9.3-bda76, 
libghc-transformers-base-dev-0.4.6-a0a78, 
libghc-transformers-dev-0.5.6.2-fc6f3, libghc-unix-dev-2.7.2.2-bdab4, 
libghc-utf8-string-dev-1.0.2-a50cd, libghc-zlib-dev-0.6.3.0-57e0e, 
haddock-interface-38, libghc-base-prof-4.15.1.0-6a406, 
libghc-binary-prof-0.8.8.0-507cc, libghc-bytestring-prof-0.10.12.1-ced9a, 
libghc-containers-prof-0.6.4.1-31c3b, libghc-dependent-map-prof-0.4.0.0-f824e, 
libghc-dependent-sum-prof-0.7.1.0-2fd03, 
libghc-dependent-sum-template-prof-0.1.1.1-62abf, 
libghc-directory-prof-1.3.6.2-311c9, libghc-edit-distance-prof-0.2.2.1-cc475, 
libghc-exceptions-prof-0.10.4-c14ff, libghc-filepath-prof-1.4.2.1-4459f, 
libghc-haskeline-prof-0.8.2-83f75, libghc-hslogger-prof-1.3.1.0-d393e, 
libghc-http-prof-4000.3.16-b345c, libghc-lifted-base-prof-0.2.3.12-e0695, 
libghc-monad-control-prof-1.0.3.1-20361, libghc-mtl-prof-2.2.2-e3bae, 
libghc-network-bsd-prof-2.8.1.0-726d3, libghc-network-prof-3.1.2.7-bb8a0, 
libghc-parsec-prof-3.1.14.0-377f0, libghc-prim-uniq-prof-0.2-b082a, 
libghc-random-fu-prof-0.3.0.0-f7738, libghc-random-prof-1.2.1.1-f840d, 
libghc-regex-tdfa-prof-1.3.2-1c748, libghc-safesemaphore-prof-0.10.1-b4f2a, 
libghc-split-prof-0.2.3.5-0c13f, libghc-syb-prof-0.7.2.2-ec1fd, 
libghc-template-haskell-prof-2.17.0.0-7274a, libghc-time-prof-1.9.3-bda76, 
libghc-transformers-base-prof-0.4.6-a0a78, 
libghc-transformers-prof-0.5.6.2-fc6f3, libghc-unix-prof-2.7.2.2-bdab4, 
libghc-utf8-string-prof-1.0.2-a50cd, libghc-zlib-prof-0.6.3.0-57e0e
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.)


-- 
1054964: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1054964
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: haskell-lambdabot-novelty-plugins
Version: 5.3.1-1
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20231028 ftbfs-trixie

Hi,

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


Relevant part (hopefully):
> +--+
> | Install package build dependencies  
>  |
> +--+
> 
> 
> Setup apt archive
> -
> 
> Merged Build-Depends: cdbs, debhelper (>= 10), ghc (>= 8), ghc-prof, 
> haskell-devscripts (>= 0.13), libghc-brainfuck-dev (>= 0.1), 
> libghc-brainfuck-prof, libghc-dice-dev (>= 0.1), libghc-dice-prof, 
> libghc-lambdabot-core-dev (>= 5.3), libghc-lambdabot-core-dev (<< 5.4), 
> libghc-lambdabot-core-prof, libghc-misfortune-dev (>= 0.1), 
> libghc-misfortune-prof, libghc-random-dev (>= 1.2), libghc-random-prof, 
> libghc-random-fu-dev (>= 0.3.0.0), libghc-random-fu-prof, 
> libghc-regex-tdfa-dev (>= 1.1), libghc-regex-tdfa-prof, libghc-unlambda-dev 
> (>= 0.1), libghc-unlambda-prof, build-essential, fakeroot, ghc-doc, 
> libghc-brainfuck-doc, libghc-dice-doc, libghc-lambdabot-core-doc, 
> libghc-misfortune-doc, libghc-random-doc, libghc-random-fu-doc, 
> libghc-regex-tdfa-doc, libghc-unlambda-doc
> Filtered Build-Depends: cdbs, debhelper (>= 10), ghc (>= 8), ghc-prof, 
> haskell-devscripts (>= 0.13), libghc-brainfuck-dev (>= 0.1), 
> libghc-brainfuck-prof, libghc-dice-dev (>=

Bug#1054984: marked as done (haskell-lambdabot-social-plugins: FTBFS: unsatisfiable build-dependencies: libghc-base-dev-4.15.1.0-6a406, libghc-binary-dev-0.8.8.0-507cc, libghc-bytestring-dev-0.10.12.1

2023-11-04 Thread Debian Bug Tracking System 
Your message dated Sat, 04 Nov 2023 18:20:32 +
with message-id 
and subject line Bug#1054984: fixed in haskell-lambdabot-social-plugins 
5.3.1.1-1
has caused the Debian Bug report #1054984,
regarding haskell-lambdabot-social-plugins: FTBFS: unsatisfiable 
build-dependencies: libghc-base-dev-4.15.1.0-6a406, 
libghc-binary-dev-0.8.8.0-507cc, libghc-bytestring-dev-0.10.12.1-ced9a, 
libghc-containers-dev-0.6.4.1-31c3b, libghc-dependent-map-dev-0.4.0.0-f824e, 
libghc-dependent-sum-dev-0.7.1.0-2fd03, 
libghc-dependent-sum-template-dev-0.1.1.1-62abf, 
libghc-directory-dev-1.3.6.2-311c9, libghc-edit-distance-dev-0.2.2.1-cc475, 
libghc-exceptions-dev-0.10.4-c14ff, libghc-filepath-dev-1.4.2.1-4459f, 
libghc-haskeline-dev-0.8.2-83f75, libghc-hslogger-dev-1.3.1.0-d393e, 
libghc-http-dev-4000.3.16-b345c, libghc-lifted-base-dev-0.2.3.12-e0695, 
libghc-monad-control-dev-1.0.3.1-20361, libghc-mtl-dev-2.2.2-e3bae, 
libghc-network-bsd-dev-2.8.1.0-726d3, libghc-network-dev-3.1.2.7-bb8a0, 
libghc-parsec-dev-3.1.14.0-377f0, libghc-prim-uniq-dev-0.2-b082a, 
libghc-random-dev-1.2.1.1-f840d, libghc-random-fu-dev-0.3.0.0-f7738, 
libghc-regex-tdfa-dev-1.3.2-1c748, libghc-safesemaphore-dev-0.10.1-b4f2a, 
libghc-split-dev-0.2.3.5-0c13f, libghc-syb-dev-0.7.2.2-ec1fd, 
libghc-template-haskell-dev-2.17.0.0-7274a, libghc-time-dev-1.9.3-bda76, 
libghc-transformers-base-dev-0.4.6-a0a78, 
libghc-transformers-dev-0.5.6.2-fc6f3, libghc-unix-dev-2.7.2.2-bdab4, 
libghc-utf8-string-dev-1.0.2-a50cd, libghc-zlib-dev-0.6.3.0-57e0e, 
haddock-interface-38, libghc-base-prof-4.15.1.0-6a406, 
libghc-binary-prof-0.8.8.0-507cc, libghc-bytestring-prof-0.10.12.1-ced9a, 
libghc-containers-prof-0.6.4.1-31c3b, libghc-dependent-map-prof-0.4.0.0-f824e, 
libghc-dependent-sum-prof-0.7.1.0-2fd03, 
libghc-dependent-sum-template-prof-0.1.1.1-62abf, 
libghc-directory-prof-1.3.6.2-311c9, libghc-edit-distance-prof-0.2.2.1-cc475, 
libghc-exceptions-prof-0.10.4-c14ff, libghc-filepath-prof-1.4.2.1-4459f, 
libghc-haskeline-prof-0.8.2-83f75, libghc-hslogger-prof-1.3.1.0-d393e, 
libghc-http-prof-4000.3.16-b345c, libghc-lifted-base-prof-0.2.3.12-e0695, 
libghc-monad-control-prof-1.0.3.1-20361, libghc-mtl-prof-2.2.2-e3bae, 
libghc-network-bsd-prof-2.8.1.0-726d3, libghc-network-prof-3.1.2.7-bb8a0, 
libghc-parsec-prof-3.1.14.0-377f0, libghc-prim-uniq-prof-0.2-b082a, 
libghc-random-fu-prof-0.3.0.0-f7738, libghc-random-prof-1.2.1.1-f840d, 
libghc-regex-tdfa-prof-1.3.2-1c748, libghc-safesemaphore-prof-0.10.1-b4f2a, 
libghc-split-prof-0.2.3.5-0c13f, libghc-syb-prof-0.7.2.2-ec1fd, 
libghc-template-haskell-prof-2.17.0.0-7274a, libghc-time-prof-1.9.3-bda76, 
libghc-transformers-base-prof-0.4.6-a0a78, 
libghc-transformers-prof-0.5.6.2-fc6f3, libghc-unix-prof-2.7.2.2-bdab4, 
libghc-utf8-string-prof-1.0.2-a50cd, libghc-zlib-prof-0.6.3.0-57e0e
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.)


-- 
1054984: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1054984
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: haskell-lambdabot-social-plugins
Version: 5.3.1-1
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20231028 ftbfs-trixie

Hi,

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


Relevant part (hopefully):
> +--+
> | Install package build dependencies  
>  |
> +--+
> 
> 
> Setup apt archive
> -
> 
> Merged Build-Depends: cdbs, debhelper (>= 10), haskell-devscripts (>= 0.13), 
> ghc (>= 8.4.3), ghc-prof, libghc-lambdabot-core-dev (>= 5.3), 
> libghc-lambdabot-core-dev (<< 5.4), libghc-lambdabot-core-prof, 
> libghc-split-dev (>= 0.2), libghc-split-prof, build-essential, fakeroot, 
> ghc-doc, libghc-lambdabot-core-doc, libghc-split-doc
> Filtered Build-Depends: cdbs, debhelper (>= 10), haskell-devscripts (>= 
> 0.13), ghc (>= 8.4.3), ghc-prof, libghc-lambdabot-core-dev (>= 5.3), 
> libghc-lambdabot-core-dev (<< 5.4), libghc-lambdabot-core-prof, 
> libghc-split-dev (>= 0.2), libghc-split-prof, build-essential, fakeroot, 
> ghc-doc, libghc-lambdabot-core-doc, libghc-split-doc
> dpkg-deb: building package 'sbuild-build-depends-main-dummy' in 
> '/<>/apt_archive/sbuild-build-depends-main-dummy.deb'.
> Ign:1 copy:/<>/apt_archive ./ InRelease
> Get:2 copy:/<>/apt_archive ./ Release [609 B]
> Ign:3 copy:/<>/apt_archive ./ Release.gpg
> Get:4 copy:/<>/apt_archive ./ Sources [893 B]
>

Bug#1054967: marked as done (haskell-lambdabot-misc-plugins: FTBFS: unsatisfiable build-dependencies: libghc-base-dev-4.15.1.0-6a406, libghc-binary-dev-0.8.8.0-507cc, libghc-bytestring-dev-0.10.12.1-c

2023-11-04 Thread Debian Bug Tracking System 
Your message dated Sat, 04 Nov 2023 18:20:16 +
with message-id 
and subject line Bug#1054967: fixed in haskell-lambdabot-misc-plugins 5.3.1.1-1
has caused the Debian Bug report #1054967,
regarding haskell-lambdabot-misc-plugins: FTBFS: unsatisfiable 
build-dependencies: libghc-base-dev-4.15.1.0-6a406, 
libghc-binary-dev-0.8.8.0-507cc, libghc-bytestring-dev-0.10.12.1-ced9a, 
libghc-containers-dev-0.6.4.1-31c3b, libghc-dependent-map-dev-0.4.0.0-f824e, 
libghc-dependent-sum-dev-0.7.1.0-2fd03, 
libghc-dependent-sum-template-dev-0.1.1.1-62abf, 
libghc-directory-dev-1.3.6.2-311c9, libghc-edit-distance-dev-0.2.2.1-cc475, 
libghc-exceptions-dev-0.10.4-c14ff, libghc-filepath-dev-1.4.2.1-4459f, 
libghc-haskeline-dev-0.8.2-83f75, libghc-hslogger-dev-1.3.1.0-d393e, 
libghc-http-dev-4000.3.16-b345c, libghc-lifted-base-dev-0.2.3.12-e0695, 
libghc-monad-control-dev-1.0.3.1-20361, libghc-mtl-dev-2.2.2-e3bae, 
libghc-network-bsd-dev-2.8.1.0-726d3, libghc-network-dev-3.1.2.7-bb8a0, 
libghc-parsec-dev-3.1.14.0-377f0, libghc-prim-uniq-dev-0.2-b082a, 
libghc-random-dev-1.2.1.1-f840d, libghc-random-fu-dev-0.3.0.0-f7738, 
libghc-regex-tdfa-dev-1.3.2-1c748, libghc-safesemaphore-dev-0.10.1-b4f2a, 
libghc-split-dev-0.2.3.5-0c13f, libghc-syb-dev-0.7.2.2-ec1fd, 
libghc-template-haskell-dev-2.17.0.0-7274a, libghc-time-dev-1.9.3-bda76, 
libghc-transformers-base-dev-0.4.6-a0a78, 
libghc-transformers-dev-0.5.6.2-fc6f3, libghc-unix-dev-2.7.2.2-bdab4, 
libghc-utf8-string-dev-1.0.2-a50cd, libghc-zlib-dev-0.6.3.0-57e0e, 
haddock-interface-38, libghc-base-prof-4.15.1.0-6a406, 
libghc-binary-prof-0.8.8.0-507cc, libghc-bytestring-prof-0.10.12.1-ced9a, 
libghc-containers-prof-0.6.4.1-31c3b, libghc-dependent-map-prof-0.4.0.0-f824e, 
libghc-dependent-sum-prof-0.7.1.0-2fd03, 
libghc-dependent-sum-template-prof-0.1.1.1-62abf, 
libghc-directory-prof-1.3.6.2-311c9, libghc-edit-distance-prof-0.2.2.1-cc475, 
libghc-exceptions-prof-0.10.4-c14ff, libghc-filepath-prof-1.4.2.1-4459f, 
libghc-haskeline-prof-0.8.2-83f75, libghc-hslogger-prof-1.3.1.0-d393e, 
libghc-http-prof-4000.3.16-b345c, libghc-lifted-base-prof-0.2.3.12-e0695, 
libghc-monad-control-prof-1.0.3.1-20361, libghc-mtl-prof-2.2.2-e3bae, 
libghc-network-bsd-prof-2.8.1.0-726d3, libghc-network-prof-3.1.2.7-bb8a0, 
libghc-parsec-prof-3.1.14.0-377f0, libghc-prim-uniq-prof-0.2-b082a, 
libghc-random-fu-prof-0.3.0.0-f7738, libghc-random-prof-1.2.1.1-f840d, 
libghc-regex-tdfa-prof-1.3.2-1c748, libghc-safesemaphore-prof-0.10.1-b4f2a, 
libghc-split-prof-0.2.3.5-0c13f, libghc-syb-prof-0.7.2.2-ec1fd, 
libghc-template-haskell-prof-2.17.0.0-7274a, libghc-time-prof-1.9.3-bda76, 
libghc-transformers-base-prof-0.4.6-a0a78, 
libghc-transformers-prof-0.5.6.2-fc6f3, libghc-unix-prof-2.7.2.2-bdab4, 
libghc-utf8-string-prof-1.0.2-a50cd, libghc-zlib-prof-0.6.3.0-57e0e
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.)


-- 
1054967: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1054967
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: haskell-lambdabot-misc-plugins
Version: 5.3.1-1
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20231028 ftbfs-trixie

Hi,

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


Relevant part (hopefully):
> +--+
> | Install package build dependencies  
>  |
> +--+
> 
> 
> Setup apt archive
> -
> 
> Merged Build-Depends: cdbs, debhelper (>= 10), ghc (>= 8.4.3), ghc-prof, 
> haskell-devscripts (>= 0.13), libghc-safesemaphore-dev (>= 0.9), 
> libghc-safesemaphore-prof, libghc-lambdabot-core-dev (>= 5.3), 
> libghc-lambdabot-core-dev (<< 5.4), libghc-lambdabot-core-prof, 
> libghc-lifted-base-dev (>= 0.2), libghc-lifted-base-prof, libghc-network-dev 
> (>= 2.7), libghc-network-dev (<< 3.2), libghc-network-prof, 
> libghc-network-uri-dev (>= 2.6), libghc-network-uri-dev (<< 2.7), 
> libghc-network-uri-prof, libghc-regex-tdfa-dev (>= 1.1), 
> libghc-regex-tdfa-prof, libghc-split-dev (>= 0.2), libghc-split-prof, 
> libghc-tagsoup-dev (>= 0.12), libghc-tagsoup-prof, 
> libghc-transformers-base-dev (>= 0.4), libghc-transformers-base-prof, 
> libghc-transformers-dev, libghc-transformers-prof, libghc-utf8-string-dev (>= 
> 0.3), libghc-utf8-string-prof, libghc-zlib-dev (>= 0.5), libghc-zlib-prof, 
> build-essential, fakeroot, ghc-doc, libghc-safesemaphore-doc, 
> libghc-lambdabot-core-doc, l

Bug#1054679: marked as done (termpaint: FTBFS: ../tests/catch_main.cpp:4:10: fatal error: catch2/catch.hpp: No such file or directory)

2023-11-04 Thread Debian Bug Tracking System 
Your message dated Sat, 04 Nov 2023 17:52:00 +
with message-id 
and subject line Bug#1053775: fixed in termpaint 0.3.0-3
has caused the Debian Bug report #1053775,
regarding termpaint: FTBFS: ../tests/catch_main.cpp:4:10: fatal error: 
catch2/catch.hpp: No such file or directory
to be marked as done.

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

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


-- 
1053775: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1053775
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: termpaint
Version: 0.3.0-2
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20231027 ftbfs-trixie

Hi,

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


Relevant part (hopefully):
> c++ -Ilibtestlib.a.p -I. -I.. -fdiagnostics-color=always 
> -D_FILE_OFFSET_BITS=64 -Wall -Winvalid-pch -std=c++14 -fvisibility=hidden 
> -fvisibility-inlines-hidden -DTERMPAINT_EXPORT_SYMBOLS -Wall -Wextra 
> -Werror=return-type -g -O2 -ffile-prefix-map=/<>=. 
> -fstack-protector-strong -fstack-clash-protection -Wformat 
> -Werror=format-security -fcf-protection -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC 
> -MD -MQ libtestlib.a.p/tests_catch_main.cpp.o -MF 
> libtestlib.a.p/tests_catch_main.cpp.o.d -o 
> libtestlib.a.p/tests_catch_main.cpp.o -c ../tests/catch_main.cpp
> ../tests/catch_main.cpp:4:10: fatal error: catch2/catch.hpp: No such file or 
> directory
> 4 | #include "catch2/catch.hpp"
>   |  ^~
> compilation terminated.
> [14/51] cc -Ilibtermpaint.so.0a.p -I. -I.. -fdiagnostics-color=always 
> -D_FILE_OFFSET_BITS=64 -Wall -Winvalid-pch -std=gnu11 -fvisibility=hidden 
> -DTERMPAINT_EXPORT_SYMBOLS -Wall -Wextra -Werror=strict-prototypes 
> -Werror=incompatible-pointer-types -Werror=implicit-int 
> -Werror=discarded-qualifiers -Werror=return-type 
> -Werror=implicit-function-declaration -DTERMPAINTP_VALGRIND -g -O2 
> -ffile-prefix-map=/<>=. -fstack-protector-strong 
> -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection 
> -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC -DTERMPAINT_RESCUE_EMBEDDED 
> '-DTERMPAINT_RESCUE_PATH="/usr/lib/x86_64-linux-gnu/termpaint0a/"' -MD -MQ 
> libtermpaint.so.0a.p/termpaint_input.c.o -MF 
> libtermpaint.so.0a.p/termpaint_input.c.o.d -o 
> libtermpaint.so.0a.p/termpaint_input.c.o -c ../termpaint_input.c
> [15/51] c++ -Itermquery.p -I. -I.. -fdiagnostics-color=always 
> -D_FILE_OFFSET_BITS=64 -Wall -Winvalid-pch -std=c++14 -fvisibility=hidden 
> -fvisibility-inlines-hidden -DTERMPAINT_EXPORT_SYMBOLS -Wall -Wextra 
> -Werror=return-type -g -O2 -ffile-prefix-map=/<>=. 
> -fstack-protector-strong -fstack-clash-protection -Wformat 
> -Werror=format-security -fcf-protection -Wdate-time -D_FORTIFY_SOURCE=2 -MD 
> -MQ termquery.p/termquery.cpp.o -MF termquery.p/termquery.cpp.o.d -o 
> termquery.p/termquery.cpp.o -c ../termquery.cpp
> [16/51] c++ -Iinputevents.p -I. -I.. -fdiagnostics-color=always 
> -D_FILE_OFFSET_BITS=64 -Wall -Winvalid-pch -std=c++14 -fvisibility=hidden 
> -fvisibility-inlines-hidden -DTERMPAINT_EXPORT_SYMBOLS -Wall -Wextra 
> -Werror=return-type -g -O2 -ffile-prefix-map=/<>=. 
> -fstack-protector-strong -fstack-clash-protection -Wformat 
> -Werror=format-security -fcf-protection -Wdate-time -D_FORTIFY_SOURCE=2 -MD 
> -MQ inputevents.p/inputevents.cpp.o -MF inputevents.p/inputevents.cpp.o.d -o 
> inputevents.p/inputevents.cpp.o -c ../inputevents.cpp
> [17/51] cc -Ilibtermpaint.so.0a.p -I. -I.. -fdiagnostics-color=always 
> -D_FILE_OFFSET_BITS=64 -Wall -Winvalid-pch -std=gnu11 -fvisibility=hidden 
> -DTERMPAINT_EXPORT_SYMBOLS -Wall -Wextra -Werror=strict-prototypes 
> -Werror=incompatible-pointer-types -Werror=implicit-int 
> -Werror=discarded-qualifiers -Werror=return-type 
> -Werror=implicit-function-declaration -DTERMPAINTP_VALGRIND -g -O2 
> -ffile-prefix-map=/<>=. -fstack-protector-strong 
> -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection 
> -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC -DTERMPAINT_RESCUE_EMBEDDED 
> '-DTERMPAINT_RESCUE_PATH="/usr/lib/x86_64-linux-gnu/termpaint0a/"' -MD -MQ 
> libtermpaint.so.0a.p/termpaint.c.o -MF libtermpaint.so.0a.p/termpaint.c.o.d 
> -o libtermpaint.so.0a.p/termpaint.c.o -c ../termpaint.c
> [18/51] c++ -Ilibtermpaint_image.so.0a.p -I. -I.. -fdiagnostics-color=always 
> -D_FILE_OFFSET_BITS=64 -Wall -Winvalid-pch -std=c++14 -fvisibility=hidden 
> -fvisibility-inlines-hidden -DTERMPAINT_EXPORT_SYMBOLS -Wall -Wextra 
> -Werror=return-type -g -O2 -ffile-prefix-map=/<>=. 
> -fstack-protector-strong -fstack-clash-protection -Wformat 
> -Wer

Bug#1053775: marked as done (termpaint: catch2 v3 breaks debci tests)

2023-11-04 Thread Debian Bug Tracking System 
Your message dated Sat, 04 Nov 2023 17:52:00 +
with message-id 
and subject line Bug#1053775: fixed in termpaint 0.3.0-3
has caused the Debian Bug report #1053775,
regarding termpaint: catch2 v3 breaks debci tests
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.)


-- 
1053775: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1053775
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: termpaint
Version: 0.3.0-2
Severity: serious
Justification: debci
Control: tags -1 patch

catch2 v3 was recently uploaded, and breaks termpaint's tests

Upstream has made a patch:
https://github.com/termpaint/termpaint/commit/dc293554b745b3f010445e9445e620399f8ee2f7
--- End Message ---
--- Begin Message ---
Source: termpaint
Source-Version: 0.3.0-3
Done: Christoph Hueffelmann 

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

Debian distribution maintenance software
pp.
Christoph Hueffelmann  (supplier of updated termpaint 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, 14 Oct 2023 21:17:59 +0200
Source: termpaint
Architecture: source
Version: 0.3.0-3
Distribution: unstable
Urgency: medium
Maintainer: Christoph Hueffelmann 
Changed-By: Christoph Hueffelmann 
Closes: 1047032 1053775
Changes:
 termpaint (0.3.0-3) unstable; urgency=medium
 .
   * Fix: Fails to build source after successful build (Closes: #1047032)
   * Upstream patch to fix catch2 version 3.x (Closes: #1053775)
Checksums-Sha1:
 c43547eada10b7692cb713df7f09fada251e624f 2155 termpaint_0.3.0-3.dsc
 14d33ae6139bc686b911464e98681e2de3409a85 8628 termpaint_0.3.0-3.debian.tar.xz
 9786edbfe285fab541018be7c944fe52b4603da7 8973 termpaint_0.3.0-3_amd64.buildinfo
Checksums-Sha256:
 cbd92cd5450b5c4730d3d8fb94ea444ed569304f429bb5babe6ae1824e3c95b7 2155 
termpaint_0.3.0-3.dsc
 ec90cafb1621ada28ef53cd86f90dce3662b134db38233dd419b95d9b7e2c6b5 8628 
termpaint_0.3.0-3.debian.tar.xz
 a042bc7af0abbe7ccaa610b7262bd7c57d182418c468571c01988c9c05af000d 8973 
termpaint_0.3.0-3_amd64.buildinfo
Files:
 bea90bfbdcf42bda0d5e48436122c144 2155 libs optional termpaint_0.3.0-3.dsc
 888b04d9aafe94e080c95fce3510 8628 libs optional 
termpaint_0.3.0-3.debian.tar.xz
 10f0c4976232fdce63b802daf2503748 8973 libs optional 
termpaint_0.3.0-3_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEE/d0M/zhkJ3YwohhskWT6HRe9XTYFAmVGgV8ACgkQkWT6HRe9
XTbVPg/+IoIupgltlyO2lO8kpn0bunlhir54zcBoKazFw/Uv4XPohBVUZqClT6j5
6Qd1iU+OMSAxwiS4scKFDeVaciHHGnj3lX2VCDCDgZD5XagBi/v5ZV/Z0keQD+hh
rsAqoI5cZA/okG4e1+7JHhMkRnbWBJbs+Q7g1hxsgFbkDTAdczy+5tktHensklMi
LqHpYHex/yyvFH61pFlQQN7QczUYVO4+EcYhL0eQ2+zifJPPQXPtX4QB+lHq9u8y
R5lL2IqwG74AIf6QMUD7lxJZXrwfQsVxPNpJnFwWuhKNnpC/XbGBAYh0G2sHk5hj
jGNr61XPMQLJloIhhejuTXffkKHgY9eWz8UbEE34d62ngFIhqedpiFmtc70suM5w
3PWhZDur8kaa0uT912b7y2KvkHHrYe0MrzMoF1/FVxKvQ3AtjHjbZ8MMTamh77YB
HGt2SVYDt07NlnHrszsQHzPaBcs07MU09tPu4UzD7116ssr7tnJg8AphpLGZZMdR
cgNxDEt3eVHx68LHkGu+3tLfaKDkXz2A1vMrhZWaVOJ6OTimSe/dQw5DHSRnPg0p
/S9y725O6s4kJ3eblxdCQngAb9Zoye5GnTkwvquB/HY7TO7uiAmO/njVj7iahhbS
WDy2jnsrpKbAW46ApucKTt5sEys9HqRpMX7j2CzCKKy58LZr038=
=LJ5m
-END PGP SIGNATURE End Message ---

Bug#1055150: marked as done (a2d: apt remove a2d nukes user data (postinst))

2023-11-04 Thread Debian Bug Tracking System 
Your message dated Sat, 04 Nov 2023 17:19:07 +
with message-id 
and subject line Bug#1055150: fixed in a2d 2.0.3-1
has caused the Debian Bug report #1055150,
regarding a2d: apt remove a2d nukes user data (postinst)
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.)


-- 
1055150: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1055150
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: a2d
Version: 2.0.1-1
Severity: serious
Justification: Policy 10.7.3

Found during package review:

postinst has:

#Remove user conf files
case "$1" in
purge|remove|deconfigure|disappear)
# Remove the user-generated configuration file
if [ -e "/etc/a2d" ]; then
  rm -r /etc/a2d
fi

if [ -e "/var/lib/a2d" ]; then
  rm -r /var/lib/a2d
fi

if [ -e "/var/log/a2d_gu_error.log" ]; then
  rm -r /var/log/a2d_gu_error.log
fi

;;

*)
# For other cases, do nothing
;;
esac

Multiple issues.
- Deleting user data is postinst must only done when purging.
- /etc/a2d is handled as conffile, it it dpkg's job to clean it up.
- /var/lib/a2d and /var/lib/a2d/dbs is also shipped with the package,
  and removing the directories should also be left to dpkg.
  (If possible the package should only delete the files it has
  created itself.)
--- End Message ---
--- Begin Message ---
Source: a2d
Source-Version: 2.0.3-1
Done: Yogeswaran Umasankar 

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

Debian distribution maintenance software
pp.
Yogeswaran Umasankar  (supplier of updated a2d 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, 3 Nov 2023 03:30:00 -0400
Source: a2d
Architecture: source
Version: 2.0.3-1
Distribution: unstable
Urgency: medium
Maintainer: Yogeswaran Umasankar 
Changed-By: Yogeswaran Umasankar 
Closes: 1055040 1055150
Changes:
 a2d (2.0.3-1) unstable; urgency=medium
 .
   * New upstream version.
   * Removed conffiles list under description in control.
   * Included GUI metadata file from upstream in a2d.install.
   * Build-Depends list updated to handle pyproject.toml and poetry.
   * Depends updated to handle yaml file introduced in the new upstream.
   * Listed additional files to copyright.
   * Revised a2d.init.d to match the upstream values.
   * Revised rules to include PYBUILD_NAME.
   * Revised postrm not to remove user config files. (Closes: #1055150)
   * Fixed failed VCS repository. (Closes: #1055040)
Checksums-Sha1:
 f5dd8dc927f0124b3900e8e05eb2dbd301190632 2110 a2d_2.0.3-1.dsc
 3d5d1b2b0c655c396a4ba97bede88986cd7bfe20 214819 a2d_2.0.3.orig.tar.gz
 6bb79c97904749134d9ff224d925bd47bb9e7c27 833 a2d_2.0.3.orig.tar.gz.asc
 e8819f854cc7f4b88dca4ede0123e3fd260bd3e1 12288 a2d_2.0.3-1.debian.tar.xz
 e1ce2d1ae68c91c77066083bae33d636b29b47ed 8927 a2d_2.0.3-1_amd64.buildinfo
Checksums-Sha256:
 6740f454939285f25060ef408770b0c80a5863155f9860250ee4d81e7cc97c68 2110 
a2d_2.0.3-1.dsc
 4ddfc42e0983f68bbcc6405d36d2131ddc49fc45864ba91328eb99fe7dd2e08d 214819 
a2d_2.0.3.orig.tar.gz
 01cf4da524d40aede1e23d97038631ddf66a94b0bc69c3cbc8b097c5b7ef685e 833 
a2d_2.0.3.orig.tar.gz.asc
 61e35f1f27f36e1c41496af0ead4eeefb1dd92f1372961d3f4936d95c93ea2c4 12288 
a2d_2.0.3-1.debian.tar.xz
 71d69fcb482f5de77482fe73632880370a3e94b7d62983af7686afd2fc60ce69 8927 
a2d_2.0.3-1_amd64.buildinfo
Files:
 1dabb4435ea3c28abd537bd97eee6806 2110 hamradio optional a2d_2.0.3-1.dsc
 798737020f71c31b0a8364bec0637ba8 214819 hamradio optional a2d_2.0.3.orig.tar.gz
 452c9fa643bdd6ea7c4e93dc05a230ae 833 hamradio optional 
a2d_2.0.3.orig.tar.gz.asc
 761ef36294c9bd55aaf661289f14c54c 12288 hamradio optional 
a2d_2.0.3-1.debian.tar.xz
 a196c5950c2d9fcf43fa1413e47df8d8 8927 hamradio optional 
a2d_2.0.3-1_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEE/d0M/zhkJ3YwohhskWT6HRe9XTYFAmVGeZ4ACgkQkWT6HRe9
XTZP7A//T6oVCAVsKNfIHxKx7hWwxu6pW0aHvR9vdIQGcvbP+myq6p3a3bVuyBFe
gFKPQB3gf3EadiFlpIYyLjDeF794d5c1zYFPS1WBCKqPkIIRjex+RXZZTqw5dZX9
RhWS4g82grZ6NHWLVlh

Bug#1054672: marked as done (megahit: FTBFS: local_assemble.h:31:3: error: ‘uint32_t’ does not name a type)

2023-11-04 Thread Debian Bug Tracking System 
Your message dated Sat, 04 Nov 2023 17:20:15 +
with message-id 
and subject line Bug#1054672: fixed in megahit 1.2.9-5
has caused the Debian Bug report #1054672,
regarding megahit: FTBFS: local_assemble.h:31:3: error: ‘uint32_t’ does not 
name a type
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.)


-- 
1054672: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1054672
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: megahit
Version: 1.2.9-4
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20231027 ftbfs-trixie

Hi,

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


Relevant part (hopefully):
> /usr/bin/c++  -I/<>/src -g -O2 
> -ffile-prefix-map=/<>=. -fstack-protector-strong 
> -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection 
> -Wdate-time -D_FORTIFY_SOURCE=2 -fopenmp -DXXH_INLINE_ALL 
> -ftemplate-depth=3000 -Wall -Wno-unused-function -fprefetch-loop-arrays 
> -funroll-loops -D__XROOT__='"/<>/src"' -std=gnu++11 -MD -MT 
> CMakeFiles/megahit_core_no_hw_accel.dir/src/main_assemble.cpp.o -MF 
> CMakeFiles/megahit_core_no_hw_accel.dir/src/main_assemble.cpp.o.d -o 
> CMakeFiles/megahit_core_no_hw_accel.dir/src/main_assemble.cpp.o -c 
> /<>/src/main_assemble.cpp
> In file included from /<>/src/main_local_assemble.cpp:27:
> /<>/src/localasm/local_assemble.h:31:3: error: ‘uint32_t’ does 
> not name a type
>31 |   uint32_t kmin{11};
>   |   ^~~~
> /<>/src/localasm/local_assemble.h:1:1: note: ‘uint32_t’ is 
> defined in header ‘’; did you forget to ‘#include ’?
>   +++ |+#include 
> 1 | /*
> /<>/src/localasm/local_assemble.h:32:3: error: ‘uint32_t’ does 
> not name a type
>32 |   uint32_t kmax{41};
>   |   ^~~~
> /<>/src/localasm/local_assemble.h:32:3: note: ‘uint32_t’ is 
> defined in header ‘’; did you forget to ‘#include ’?
> /<>/src/localasm/local_assemble.h:33:3: error: ‘uint32_t’ does 
> not name a type
>33 |   uint32_t step{6};
>   |   ^~~~
> /<>/src/localasm/local_assemble.h:33:3: note: ‘uint32_t’ is 
> defined in header ‘’; did you forget to ‘#include ’?
> /<>/src/localasm/local_assemble.h:34:3: error: ‘uint32_t’ does 
> not name a type
>34 |   uint32_t seed_kmer{31};
>   |   ^~~~
> /<>/src/localasm/local_assemble.h:34:3: note: ‘uint32_t’ is 
> defined in header ‘’; did you forget to ‘#include ’?
> /<>/src/localasm/local_assemble.h:36:3: error: ‘uint32_t’ does 
> not name a type
>36 |   uint32_t min_contig_len{200};
>   |   ^~~~
> /<>/src/localasm/local_assemble.h:36:3: note: ‘uint32_t’ is 
> defined in header ‘’; did you forget to ‘#include ’?
> /<>/src/localasm/local_assemble.h:37:3: error: ‘uint32_t’ does 
> not name a type
>37 |   uint32_t sparsity{8};
>   |   ^~~~
> /<>/src/localasm/local_assemble.h:37:3: note: ‘uint32_t’ is 
> defined in header ‘’; did you forget to ‘#include ’?
> /<>/src/localasm/local_assemble.h:39:3: error: ‘uint32_t’ does 
> not name a type
>39 |   uint32_t min_mapping_len{75};
>   |   ^~~~
> /<>/src/localasm/local_assemble.h:39:3: note: ‘uint32_t’ is 
> defined in header ‘’; did you forget to ‘#include ’?
> /<>/src/localasm/local_assemble.h:41:3: error: ‘uint32_t’ does 
> not name a type
>41 |   uint32_t num_threads{0};
>   |   ^~~~
> /<>/src/localasm/local_assemble.h:41:3: note: ‘uint32_t’ is 
> defined in header ‘’; did you forget to ‘#include ’?
> /<>/src/main_local_assemble.cpp: In function ‘LocalAsmOption 
> {anonymous}::ParseLocalAsmOptions(int, char**)’:
> /<>/src/main_local_assemble.cpp:40:34: error: ‘struct 
> LocalAsmOption’ has no member named ‘kmin’
>40 |   desc.AddOption("kmin", "", opt.kmin, "");
>   |  ^~~~
> /<>/src/main_local_assemble.cpp:41:34: error: ‘struct 
> LocalAsmOption’ has no member named ‘kmax’
>41 |   desc.AddOption("kmax", "", opt.kmax, "");
>   |  ^~~~
> /<>/src/main_local_assemble.cpp:42:34: error: ‘struct 
> LocalAsmOption’ has no member named ‘step’
>42 |   desc.AddOption("step", "", opt.step, "");
>   |  ^~~~
> /<>/src/main_local_assemble.cpp:43:39: error: ‘struct 
> LocalAsmOption’ has no member named ‘seed_kmer’
>43 |   desc.AddOption("seed_kmer", "", opt.seed_kmer,
>   |   ^
> /<>/src/main_local_assemble.cpp:45:44: error: ‘struct 
> LocalAsmOption’ has no member named ‘min_contig_len’
>45 |   desc.AddOption("min_contig_len", "", opt.min

Processed: Bug#1054672 marked as pending in megahit

2023-11-04 Thread Debian Bug Tracking System 
Processing control commands:

> tag -1 pending
Bug #1054672 [src:megahit] megahit: FTBFS: local_assemble.h:31:3: error: 
‘uint32_t’ does not name a type
Added tag(s) pending.

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

Bug#1054672: marked as pending in megahit

2023-11-04 Thread Nilesh Patra 
Control: tag -1 pending

Hello,

Bug #1054672 in megahit 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/megahit/-/commit/59953b0ca68d0654d0fa2dd044003c5c814500be


Add patch to fix FTBFS with gcc-13 (Closes: #1054672)


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1054672

Bug#1054773: marked as done (golang-nhooyr-websocket: FTBFS: dh_auto_test: error: cd _build && go test -vet=off -v -p 8 nhooyr.io/websocket nhooyr.io/websocket/internal/bpool nhooyr.io/websocket/inter

2023-11-04 Thread Debian Bug Tracking System 
Your message dated Sat, 4 Nov 2023 22:35:54 +0530
with message-id <20231104170554.yawhizv4y76sy...@office.mailbox.org>
and subject line Re: golang-nhooyr-websocket: FTBFS: dh_auto_test: error: cd 
_build && go test -vet=off -v -p 8 nhooyr.io/websocket 
nhooyr.io/websocket/internal/bpool nhooyr.io/websocket/internal/errd 
nhooyr.io/websocket/internal/test nhooyr.io/websocket/internal/test/assert 
nhooyr.io/websocket/internal/test/wstest 
nhooyr.io/websocket/internal/test/xrand nhooyr.io/websocket/internal/xsync 
nhooyr.io/websocket/wsjson nhooyr.io/websocket/wspb returned exit code 1
has caused the Debian Bug report #1054773,
regarding golang-nhooyr-websocket: FTBFS: dh_auto_test: error: cd _build && go 
test -vet=off -v -p 8 nhooyr.io/websocket nhooyr.io/websocket/internal/bpool 
nhooyr.io/websocket/internal/errd nhooyr.io/websocket/internal/test 
nhooyr.io/websocket/internal/test/assert 
nhooyr.io/websocket/internal/test/wstest 
nhooyr.io/websocket/internal/test/xrand nhooyr.io/websocket/internal/xsync 
nhooyr.io/websocket/wsjson nhooyr.io/websocket/wspb returned exit code 1
to be marked as done.

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

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


-- 
1054773: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1054773
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: golang-nhooyr-websocket
Version: 1.8.7-3
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20231027 ftbfs-trixie

Hi,

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


Relevant part (hopefully):
>  debian/rules binary
> dh binary --builddirectory=_build --buildsystem=golang --with=golang
>dh_update_autotools_config -O--builddirectory=_build -O--buildsystem=golang
>dh_autoreconf -O--builddirectory=_build -O--buildsystem=golang
>dh_auto_configure -O--builddirectory=_build -O--buildsystem=golang
>dh_auto_build -O--builddirectory=_build -O--buildsystem=golang
>   cd _build && go install -trimpath -v -p 8 nhooyr.io/websocket 
> nhooyr.io/websocket/internal/bpool nhooyr.io/websocket/internal/errd 
> nhooyr.io/websocket/internal/test nhooyr.io/websocket/internal/test/assert 
> nhooyr.io/websocket/internal/test/wstest 
> nhooyr.io/websocket/internal/test/xrand nhooyr.io/websocket/internal/xsync 
> nhooyr.io/websocket/wsjson nhooyr.io/websocket/wspb
> internal/goos
> internal/goarch
> internal/coverage/rtcov
> internal/goexperiment
> internal/unsafeheader
> internal/godebugs
> runtime/internal/atomic
> runtime/internal/syscall
> internal/race
> internal/cpu
> internal/abi
> runtime/internal/math
> runtime/internal/sys
> sync/atomic
> unicode
> unicode/utf8
> internal/itoa
> math/bits
> crypto/internal/alias
> crypto/subtle
> crypto/internal/boring/sig
> log/internal
> internal/bytealg
> internal/nettrace
> container/list
> unicode/utf16
> vendor/golang.org/x/crypto/cryptobyte/asn1
> vendor/golang.org/x/crypto/internal/alias
> math
> nhooyr.io/websocket/internal/test
> encoding
> github.com/google/go-cmp/cmp/internal/flags
> runtime
> internal/reflectlite
> sync
> internal/testlog
> internal/singleflight
> internal/bisect
> internal/sysinfo
> runtime/cgo
> internal/godebug
> errors
> sort
> internal/oserror
> internal/safefilepath
> io
> path
> math/rand
> strconv
> syscall
> vendor/golang.org/x/net/dns/dnsmessage
> internal/intern
> crypto/internal/nistec/fiat
> strings
> bytes
> hash
> crypto/internal/randutil
> hash/crc32
> vendor/golang.org/x/text/transform
> crypto
> reflect
> bufio
> net/netip
> crypto/rc4
> net/http/internal/ascii
> nhooyr.io/websocket/internal/bpool
> regexp/syntax
> net/http/internal/testcert
> internal/syscall/unix
> time
> internal/syscall/execenv
> regexp
> context
> io/fs
> github.com/google/go-cmp/cmp/internal/diff
> internal/poll
> embed
> os
> internal/fmtsort
> github.com/google/go-cmp/cmp/internal/function
> encoding/binary
> encoding/base64
> crypto/cipher
> crypto/md5
> vendor/golang.org/x/crypto/internal/poly1305
> crypto/internal/edwards25519/field
> crypto/internal/nistec
> encoding/pem
> io/ioutil
> fmt
> net
> path/filepath
> crypto/internal/boring
> crypto/des
> crypto/internal/edwards25519
> vendor/golang.org/x/crypto/chacha20
> crypto/sha1
> crypto/aes
> crypto/sha512
> crypto/hmac
> crypto/sha256
> vendor/golang.org/x/sys/cpu
> crypto/ecdh
> vendor/golang.org/x/crypto/hkdf
> vendor/golang.org/x/crypto/chacha20poly1305
> encoding/hex
> log
> net/url
> compress/flate
> math/big
> vendor/golang.org/x/text/unicode/norm
> vendor/golang.org/x/net/http2/hpack
> vendor/golang.org/x/text/unicode/bidi
> mime
> mime/quo

Bug#1055348: jetty9: Update from DLA 3641 breaks puppetdb ("Exception in thread "main" java.lang.IllegalStateException: KeyStores with multiple certificates are not supported on the base class org.ecl

2023-11-04 Thread Adam D. Barratt 
Source: jetty9
Version: 9.4.50-4+deb10u1
Severity: serious
X-Debbugs-Cc: d...@debian.org

Hi,

Upgrading libjetty9-java and libjetty9-extra-java to the version from
DLA 3641-1 reliably causes PuppetDB to fail to start, with the
stacktrace shown below. Downgrading resolves the issue.

I'm not sure which keystore is being referred to, but none of the files
listed in /etc/puppetdb/conf.d/jetty.ini appear to contain more than a
single certificate.

Regards,

Adam

-- Logs begin at Sat 2023-11-04 14:52:45 UTC, end at Sat 2023-11-04 16:16:11 
UTC. --
Nov 04 14:52:50 handel systemd[1]: Started Puppet data warehouse server.
Nov 04 14:53:22 handel java[1669]: WARNING: boolean? already refers to: 
#'clojure.core/boolean? in namespace: puppetlabs.trapperkeeper.internal, being 
replaced by: #'puppetlabs.kitchensink.core/boolean?
Nov 04 14:53:32 handel java[1669]: 14:53:32.886 [main] DEBUG 
puppetlabs.puppetdb.http - The v1 API has been retired; please use v4 Caught 
HTTP processing exception
Nov 04 14:53:32 handel java[1669]: 14:53:32.898 [main] DEBUG 
puppetlabs.puppetdb.http - The v2 API has been retired; please use v4 Caught 
HTTP processing exception
Nov 04 14:53:32 handel java[1669]: 14:53:32.899 [main] DEBUG 
puppetlabs.puppetdb.http - The v3 API has been retired; please use v4 Caught 
HTTP processing exception
Nov 04 14:53:34 handel java[1669]: 14:53:34.073 [main] DEBUG 
puppetlabs.trapperkeeper.bootstrap - Loading bootstrap config from classpath: 
'jar:file:/usr/share/puppetdb/puppetdb.jar!/bootstrap.cfg'
Nov 04 14:53:39 handel java[1669]: Exception in thread "main" 
java.lang.IllegalStateException: KeyStores with multiple certificates are not 
supported on the base class org.eclipse.jetty.util.ssl.SslContextFactory
Nov 04 14:53:39 handel java[1669]: at 
org.eclipse.jetty.util.ssl.SslContextFactory.newSniX509ExtendedKeyManager(SslContextFactory.java:1289)
Nov 04 14:53:39 handel java[1669]: at 
org.eclipse.jetty.util.ssl.SslContextFactory.getKeyManagers(SslContextFactory.java:1271)
Nov 04 14:53:39 handel java[1669]: at 
org.eclipse.jetty.util.ssl.SslContextFactory.load(SslContextFactory.java:373)
Nov 04 14:53:39 handel java[1669]: at 
org.eclipse.jetty.util.ssl.SslContextFactory.doStart(SslContextFactory.java:244)
Nov 04 14:53:39 handel java[1669]: at 
org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:73)
Nov 04 14:53:39 handel java[1669]: at 
org.eclipse.jetty.util.component.ContainerLifeCycle.start(ContainerLifeCycle.java:169)
Nov 04 14:53:39 handel java[1669]: at 
org.eclipse.jetty.util.component.ContainerLifeCycle.doStart(ContainerLifeCycle.java:117)
Nov 04 14:53:39 handel java[1669]: at 
org.eclipse.jetty.server.SslConnectionFactory.doStart(SslConnectionFactory.java:97)
Nov 04 14:53:39 handel java[1669]: at 
org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:73)
Nov 04 14:53:39 handel java[1669]: at 
org.eclipse.jetty.util.component.ContainerLifeCycle.start(ContainerLifeCycle.java:169)
Nov 04 14:53:39 handel java[1669]: at 
org.eclipse.jetty.util.component.ContainerLifeCycle.doStart(ContainerLifeCycle.java:117)
Nov 04 14:53:39 handel java[1669]: at 
org.eclipse.jetty.server.AbstractConnector.doStart(AbstractConnector.java:323)
Nov 04 14:53:39 handel java[1669]: at 
org.eclipse.jetty.server.AbstractNetworkConnector.doStart(AbstractNetworkConnector.java:81)
Nov 04 14:53:39 handel java[1669]: at 
org.eclipse.jetty.server.ServerConnector.doStart(ServerConnector.java:234)
Nov 04 14:53:39 handel java[1669]: at 
org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:73)
Nov 04 14:53:39 handel java[1669]: at 
org.eclipse.jetty.server.Server.doStart(Server.java:401)
Nov 04 14:53:39 handel java[1669]: at 
org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:73)
Nov 04 14:53:39 handel java[1669]: at 
java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
Nov 04 14:53:39 handel java[1669]: at 
java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
Nov 04 14:53:39 handel java[1669]: at 
java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
Nov 04 14:53:39 handel java[1669]: at 
java.base/java.lang.reflect.Method.invoke(Method.java:566)
Nov 04 14:53:39 handel java[1669]: at 
clojure.lang.Reflector.invokeMatchingMethod(Reflector.java:167)
Nov 04 14:53:39 handel java[1669]: at 
clojure.lang.Reflector.invokeNoArgInstanceMember(Reflector.java:438)
Nov 04 14:53:39 handel java[1669]: at 
puppetlabs.trapperkeeper.services.webserver.jetty9_core$eval43528$start_webserver_BANG___43533$fn__43534$fn__43535.invoke(jetty9_core.clj:685)
Nov 04 14:53:39 handel java[1669]: at 
puppetlabs.trapperkeeper.services.webser

Processed: mention bookworm in bug title

2023-11-04 Thread Debian Bug Tracking System 
Processing commands for cont...@bugs.debian.org:

> retitle 1036255 python3-onelogin-saml2: FTBFS in bookworm and above: 
> AssertionError: "Invalid issuer in the Logout Request" does not match "Could 
> not validate timestamp: expired. Check system clock.)"
Bug #1036255 [src:python3-onelogin-saml2] python3-onelogin-saml2: FTBFS in 
testing: AssertionError: "Invalid issuer in the Logout Request" does not match 
"Could not validate timestamp: expired. Check system clock.)"
Changed Bug title to 'python3-onelogin-saml2: FTBFS in bookworm and above: 
AssertionError: "Invalid issuer in the Logout Request" does not match "Could 
not validate timestamp: expired. Check system clock.)"' from 
'python3-onelogin-saml2: FTBFS in testing: AssertionError: "Invalid issuer in 
the Logout Request" does not match "Could not validate timestamp: expired. 
Check system clock.)"'.
>
End of message, stopping processing here.

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

Bug#1042607: marked as done (harp: FTBFS with Sphinx 7.1, docutils 0.20: rm: cannot remove 'debian/tmp/usr/share/harp/doc/html/_static/underscore*': No such file or directory)

2023-11-04 Thread Debian Bug Tracking System 
Your message dated Sat, 04 Nov 2023 16:49:30 +
with message-id 
and subject line Bug#1042607: fixed in harp 1.20.1-2
has caused the Debian Bug report #1042607,
regarding harp: FTBFS with Sphinx 7.1, docutils 0.20: rm: cannot remove 
'debian/tmp/usr/share/harp/doc/html/_static/underscore*': No such file or 
directory
to be marked as done.

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

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


-- 
1042607: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1042607
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: harp
Version: 1.18-1
Severity: important
Tags: ftbfs
User: python-modules-t...@lists.alioth.debian.org
Usertags: sphinx7.1

Hi,

harp fails to build with Sphinx 7.1 and docutils 0.20, both of which
are currently available in experimental.

Relevant part (hopefully):
> make[5]: Entering directory '/<>'
> Makefile:5857: warning: ignoring prerequisites on suffix rule definition
> make[5]: Nothing to be done for 'install-data-hook'.
> make[5]: Leaving directory '/<>'
> make[4]: Leaving directory '/<>'
> make[3]: Leaving directory '/<>'
> make[2]: Leaving directory '/<>'
> find debian -name '*.la' -delete
> rm debian/tmp/usr/share/harp/doc/html/_static/jquery*
> rm debian/tmp/usr/share/harp/doc/html/_static/underscore*
> rm: cannot remove 'debian/tmp/usr/share/harp/doc/html/_static/underscore*': 
> No such file or directory
> make[1]: *** [debian/rules:33: override_dh_auto_install] Error 1


The full build log is available from:
http://qa-logs.debian.net/2023/07/30/exp/harp_1.18-1_unstable_sphinx-exp.log

Please see [1] for Sphinx changelog and [2] for Docutils changelog.

Also see [3] for the list of deprecated/removed APIs in Sphinx and possible
alternatives to them.

Some notable changes in Sphinx 6 and Sphinx 7:

- Sphinx no longer includes jquery.js and underscore.js by default.
  Please use python3-sphinxcontrib.jquery package if you are using a custom
  template and it still needs jquery.

- The setup.py build_sphinx command was removed. Please instead call
  sphinx-build or "python3 -m sphinx" directly.

- For packages using the extlinks extension, the caption should contain
  exactly one "%s" placeholder (if caption is not None).

In case you have questions, please Cc sph...@packages.debian.org on reply.

[1]: https://www.sphinx-doc.org/en/master/changes.html
[2]: 
https://repo.or.cz/docutils.git/blob/refs/tags/docutils-0.20.1:/RELEASE-NOTES.txt
[3]: 
https://www.sphinx-doc.org/en/master/extdev/deprecated.html#dev-deprecated-apis

All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=sphinx7.1;users=python-modules-t...@lists.alioth.debian.org
or:
https://udd.debian.org/bugs/?release=na&merged=ign&fnewerval=7&flastmodval=7&fusertag=only&fusertagtag=sphinx7.1&fusertaguser=python-modules-t...@lists.alioth.debian.org&allbugs=1&cseverity=1&ctags=1&caffected=1#results

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
--- End Message ---
--- Begin Message ---
Source: harp
Source-Version: 1.20.1-2
Done: Alastair McKinstry 

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

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

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

Debian distribution maintenance software
pp.
Alastair McKinstry  (supplier of updated harp 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, 04 Nov 2023 14:23:26 +
Source: harp
Architecture: source
Version: 1.20.1-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Science Maintainers  

Changed-By: Alastair McKinstry 
Closes: 1042607
Changes:
 harp (1.20.1-2) unstable; urgency=medium
 .
   * Don't delete js files that aren't shipped in sphinx 7. Closes: #1042607
Checksums-Sha1:
 dfd9f7e29446943d83b1c7ea8442ce39b3cb80ed 2481 harp_1.20.1-2.dsc
 4b60721105659b7f6d19443e7e0e7b5bb6c011da 27968 harp_1.20.1-2.debian.tar.xz
Checksums-Sha256:
 d69e743516f9a264441bb6aa962c958f580b968de611dd1652e1b00f5d7e0443 2481 
harp_1.20.1-2.dsc
 d2e13c64e8ecd3d51ca9c62004df342ccb1e614ba6e072f91be683927359679e 27968

Bug#1054935: marked as done (haskell-yi-keymap-emacs: FTBFS: unsatisfiable build-dependencies: libghc-array-dev-0.5.4.0-0b6fa, libghc-attoparsec-dev-0.14.4-9b901, libghc-base-dev-4.15.1.0-6a406, libgh

2023-11-04 Thread Debian Bug Tracking System 
Your message dated Sat, 04 Nov 2023 16:34:12 +
with message-id 
and subject line Bug#1054935: fixed in haskell-yi-keymap-emacs 0.19.0-3
has caused the Debian Bug report #1054935,
regarding haskell-yi-keymap-emacs: FTBFS: unsatisfiable build-dependencies: 
libghc-array-dev-0.5.4.0-0b6fa, libghc-attoparsec-dev-0.14.4-9b901, 
libghc-base-dev-4.15.1.0-6a406, libghc-binary-dev-0.8.8.0-507cc, 
libghc-bytestring-dev-0.10.12.1-ced9a, libghc-containers-dev-0.6.4.1-31c3b, 
libghc-data-default-dev-0.7.1.1-6d3b3, libghc-directory-dev-1.3.6.2-311c9, 
libghc-dlist-dev-1.0-366f6, libghc-dynamic-state-dev-0.3.1-d49ee, 
libghc-exceptions-dev-0.10.4-c14ff, libghc-filepath-dev-1.4.2.1-4459f, 
libghc-hashable-dev-1.3.5.0-3fad8, libghc-listlike-dev-4.7.7-58f6d, 
libghc-microlens-platform-dev-0.4.2.1-8c955, libghc-mtl-dev-2.2.2-e3bae, 
libghc-old-locale-dev-1.0.0.7-60e52, libghc-oo-prototypes-dev-0.1.0.0-9dda4, 
libghc-parsec-dev-3.1.14.0-377f0, libghc-pointedlist-dev-0.6.1-f22c9, 
libghc-process-dev-1.6.13.2-9f25f, libghc-process-extras-dev-0.7.4-d5396, 
libghc-split-dev-0.2.3.5-0c13f, libghc-text-dev-1.2.5.0-8553e, 
libghc-time-dev-1.9.3-bda76, libghc-transformers-base-dev-0.4.6-a0a78, 
libghc-unix-compat-dev-0.5.4-1f010, libghc-unix-dev-2.7.2.2-bdab4, 
libghc-unordered-containers-dev-0.2.17.0-1d16d, 
libghc-xdg-basedir-dev-0.2.2-01215, libghc-yi-language-dev-0.19.0-ac372, 
libghc-yi-rope-dev-0.11-1df98, haddock-interface-38, 
libghc-array-prof-0.5.4.0-0b6fa, libghc-attoparsec-prof-0.14.4-9b901, 
libghc-base-prof-4.15.1.0-6a406, libghc-binary-prof-0.8.8.0-507cc, 
libghc-bytestring-prof-0.10.12.1-ced9a, libghc-containers-prof-0.6.4.1-31c3b, 
libghc-data-default-prof-0.7.1.1-6d3b3, libghc-directory-prof-1.3.6.2-311c9, 
libghc-dlist-prof-1.0-366f6, libghc-dynamic-state-prof-0.3.1-d49ee, 
libghc-exceptions-prof-0.10.4-c14ff, libghc-filepath-prof-1.4.2.1-4459f, 
libghc-hashable-prof-1.3.5.0-3fad8, libghc-listlike-prof-4.7.7-58f6d, 
libghc-microlens-platform-prof-0.4.2.1-8c955, libghc-mtl-prof-2.2.2-e3bae, 
libghc-old-locale-prof-1.0.0.7-60e52, libghc-oo-prototypes-prof-0.1.0.0-9dda4, 
libghc-parsec-prof-3.1.14.0-377f0, libghc-pointedlist-prof-0.6.1-f22c9, 
libghc-process-extras-prof-0.7.4-d5396, libghc-process-prof-1.6.13.2-9f25f, 
libghc-split-prof-0.2.3.5-0c13f, libghc-text-prof-1.2.5.0-8553e, 
libghc-time-prof-1.9.3-bda76, libghc-transformers-base-prof-0.4.6-a0a78, 
libghc-unix-compat-prof-0.5.4-1f010, libghc-unix-prof-2.7.2.2-bdab4, 
libghc-unordered-containers-prof-0.2.17.0-1d16d, 
libghc-xdg-basedir-prof-0.2.2-01215, libghc-yi-language-prof-0.19.0-ac372, 
libghc-yi-rope-prof-0.11-1df98, libghc-array-dev-0.5.4.0-0b6fa, 
libghc-base-dev-4.15.1.0-6a406, libghc-binary-dev-0.8.8.0-507cc, 
libghc-data-default-dev-0.7.1.1-6d3b3, libghc-filepath-dev-1.4.2.1-4459f, 
libghc-microlens-platform-dev-0.4.2.1-8c955, libghc-text-dev-1.2.5.0-8553e, 
libghc-yi-language-dev-0.19.0-ac372, libghc-yi-rope-dev-0.11-1df98, 
haddock-interface-38, libghc-array-prof-0.5.4.0-0b6fa, 
libghc-base-prof-4.15.1.0-6a406, libghc-binary-prof-0.8.8.0-507cc, 
libghc-data-default-prof-0.7.1.1-6d3b3, libghc-filepath-prof-1.4.2.1-4459f, 
libghc-microlens-platform-prof-0.4.2.1-8c955, libghc-text-prof-1.2.5.0-8553e, 
libghc-yi-language-prof-0.19.0-ac372, libghc-yi-rope-prof-0.11-1df98
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.)


-- 
1054935: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1054935
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: haskell-yi-keymap-emacs
Version: 0.19.0-2
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20231028 ftbfs-trixie

Hi,

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


Relevant part (hopefully):
> +--+
> | Install package build dependencies  
>  |
> +--+
> 
> 
> Setup apt archive
> -
> 
> Merged Build-Depends: debhelper (>= 10), haskell-devscripts-minimal | 
> haskell-devscripts (>= 0.9), cdbs, ghc (>= 8.4.3), ghc-prof, 
> libghc-hclip-dev, libghc-hclip-prof, libghc-microlens-platform-dev, 
> libghc-microlens-platform-prof, libghc-oo-prototypes-dev, 
> libghc-oo-prototypes-prof, libghc-transformers-base-dev, 
> libghc-transformers-base-prof, libghc-yi-core-dev (>= 0.19), 
> libghc-yi-core-prof, libghc-yi-language-dev (>= 0.19), 
> libghc-yi-language-prof, libghc-yi-misc-modes-dev (>= 0.19), 
> libghc-yi-mis

Bug#1052803: Help fixing a gettext translation test

2023-11-04 Thread Mathias Gibbens 
Hi all,

  I'm working on fixing bug #1052803 for golang-github-gosexy-gettext.
That package's tests started failing, and I'm pretty sure it was caused
by the upload of src:glibc 2.37-8 which backported a patch from bug
#874160 that treats language encodings like C.UTF-8 as the C locale.

  This change effectively "turns off" translations, unless you specify
some specific encoding like "en_US.utf8". While I can apply the
attached patch that fixes the tests, it feels less than ideal. And as
this will be a NMU to prevent the package from being AUTORM'ed and
taking src:lxd along with it, I'd like to fix this properly. I'm just
not familiar enough with gettext to know if there's a better solution.

  A simple reproducer is listed below. On a sid system, the first
invocation will fail to return the properly translated string, but the
second will (substitute with your preferred locale).

  Thanks for any advice!

Mathias
(BCC: bug #1052803)

> $ dget 
> https://deb.debian.org/debian/pool/main/g/golang-github-gosexy-gettext/golang-github-gosexy-gettext_0~git20130221-2.1.dsc
> $ cd golang-github-gosexy-gettext-0~git20130221/
> $ LC_ALL=C.UTF-8 LANGUAGE="es_MX.utf8" TEXTDOMAINDIR=./examples/ gettext -d 
> example "Hello, world!"
> $ LC_ALL=en_US.utf8 LANGUAGE="es_MX.utf8" TEXTDOMAINDIR=./examples/ gettext 
> -d example "Hello, world!"
diff --git a/debian/control b/debian/control
index d1364e1..18690eb 100644
--- a/debian/control
+++ b/debian/control
@@ -4,7 +4,7 @@ Priority: optional
 Maintainer: Steve Langasek 
 Build-Depends: debhelper (>= 11~),
dh-golang,
-   golang-any,
+   golang-any, locales-all
 Standards-Version: 4.2.1
 Homepage: https://github.com/gosexy/gettext
 XS-Go-Import-Path: github.com/gosexy/gettext
diff --git a/debian/rules b/debian/rules
index 2d9b72c..1451b07 100755
--- a/debian/rules
+++ b/debian/rules
@@ -20,7 +20,7 @@ override_dh_auto_build:
rm obj-*/src/github.com/gosexy/gettext/examples/*/*.pot
 
 override_dh_auto_test:
-   LC_ALL=C.UTF-8 dh_auto_test
+   LC_ALL=en_US.utf8 dh_auto_test
 
 get-orig-source:
rm -rf $(PKG)

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

Processed: Why should a FTBFS against packages in experimental be serious?

2023-11-04 Thread Debian Bug Tracking System 
Processing commands for cont...@bugs.debian.org:

> severity 1042642 important
Bug #1042642 [src:ns3] ns3: FTBFS with Sphinx 7.1, docutils 0.20: make[6]: *** 
[Makefile:75: html] Error 2
Severity set to 'important' from 'serious'
> thanks
Stopping processing here.

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

Processed: closing 1040051

2023-11-04 Thread Debian Bug Tracking System 
Processing commands for cont...@bugs.debian.org:

> close 1040051
Bug #1040051 [pymodbus] autopkgtest err "Task was destroyed but it is pending!"
Marked Bug as done
> thanks
Stopping processing here.

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

Bug#1040051: closing 1040051

2023-11-04 Thread Sjoerd Simons 
close 1040051
thanks

Retesting with autopkgtest on testing (with pymodbus from unstable) seems to be
succcessful at this point. So closing this bug

Processed: closing 1017263

2023-11-04 Thread Debian Bug Tracking System 
Processing commands for cont...@bugs.debian.org:

> close 1017263 3.0.0-1
Bug #1017263 [src:haskell-cryptol] haskell-cryptol: FTBFS: Parse error in 
pattern: ppInfixName In a function binding for the ‘@’ operator.
Marked as fixed in versions haskell-cryptol/3.0.0-1.
Bug #1017263 [src:haskell-cryptol] haskell-cryptol: FTBFS: Parse error in 
pattern: ppInfixName In a function binding for the ‘@’ operator.
Marked Bug as done
> thanks
Stopping processing here.

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

Processed (with 1 error): your mail

2023-11-04 Thread Debian Bug Tracking System 
Processing commands for cont...@bugs.debian.org:

> package src:ns3
Limiting to bugs with field 'package' containing at least one of 'src:ns3'
Limit currently set to 'package':'src:ns3'

> upstream 1042642
Unknown command or malformed arguments to command.
> forwarded 1042642 https://gitlab.com/nsnam/ns-3-dev/-/issues/978
Bug #1042642 [src:ns3] ns3: FTBFS with Sphinx 7.1, docutils 0.20: make[6]: *** 
[Makefile:75: html] Error 2
Set Bug forwarded-to-address to 
'https://gitlab.com/nsnam/ns-3-dev/-/issues/978'.
>
End of message, stopping processing here.

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

Bug#1054692: tomlplusplus: FTBFS: ../tests/lib_catch2.h:35:2: error: #error Catch2 is missing!

2023-11-04 Thread Bastian Germann 

I am uploading a NMU to fix this.
As this involves a repack I am also updating the upstream version.

Bug#1054692: marked as done (tomlplusplus: FTBFS: ../tests/lib_catch2.h:35:2: error: #error Catch2 is missing!)

2023-11-04 Thread Debian Bug Tracking System 
Your message dated Sat, 4 Nov 2023 15:44:32 +0100
with message-id <33aa2e34-d7cb-4e28-bba3-f19717a33...@debian.org>
and subject line Re: tomlplusplus: FTBFS: ../tests/lib_catch2.h:35:2: error: 
#error Catch2 is missing!
has caused the Debian Bug report #1054692,
regarding tomlplusplus: FTBFS: ../tests/lib_catch2.h:35:2: error: #error Catch2 
is missing!
to be marked as done.

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

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


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

Hi,

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


Relevant part (hopefully):
> c++ -Itests/tomlplusplus_tests.p -Itests -I../tests -Iinclude -I../include 
> -flto=auto -fdiagnostics-color=always -DNDEBUG -D_FILE_OFFSET_BITS=64 -Wall 
> -Winvalid-pch -std=c++17 -g -O2 -Werror=array-bounds -Werror=clobbered 
> -Werror=volatile-register-var 
> -D__DEB_CANARY_CXXFLAGS_a5771bce93e200c36f7cd9dfd0e5deaa__ 
> -ffile-prefix-map=/<>=. -fstack-protector-strong 
> -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection 
> -D__DEB_CANARY_CPPFLAGS_a5771bce93e200c36f7cd9dfd0e5deaa__ -Wdate-time 
> -D_FORTIFY_SOURCE=2 -DTOML_HEADER_ONLY=0 -DTOML_SHARED_LIB=1 -fmax-errors=5 
> -Wno-init-list-lifetime -fchar8_t -D_HAS_EXCEPTIONS=1 -Wno-switch-enum 
> -Wno-padded -Wno-float-equal -DSHOULD_HAVE_EXCEPTIONS=1 -DUSE_VENDORED_LIBS=0 
> -MD -MQ tests/tomlplusplus_tests.p/conformance_burntsushi_valid.cpp.o -MF 
> tests/tomlplusplus_tests.p/conformance_burntsushi_valid.cpp.o.d -o 
> tests/tomlplusplus_tests.p/conformance_burntsushi_valid.cpp.o -c 
> ../tests/conformance_burntsushi_valid.cpp
> In file included from ../tests/tests.h:36,
>  from ../tests/conformance_burntsushi_valid.cpp:8:
> ../tests/lib_catch2.h:35:2: error: #error Catch2 is missing!
>35 | #error Catch2 is missing!
>   |  ^
> ../tests/tests.h:41:17: error: ‘Catch’ has not been declared
>41 | using namespace Catch::literals;
>   | ^
> ../tests/tests.h:41:24: error: ‘literals’ is not a namespace-name
>41 | using namespace Catch::literals;
>   |^~~~
> ../tests/tests.h: In function ‘bool parse_expected_value(std::string_view, 
> uint32_t, std::string_view, const T&)’:
> ../tests/tests.h:151:20: error: no match for ‘operator<<’ (operand types are 
> ‘std::basic_string_view’ and ‘std::string_view’ {aka 
> ‘std::basic_string_view’})
>   151 | INFO("["sv << test_file << ", line "sv << test_line << "] "sv
>   |  ~ ^~ ~
>   |  ||
>   |  |basic_string_view<[...]>
>   |  basic_string_view<[...]>
> In file included from ../include/toml++/toml.h:36,
>  from ../tests/tests.h:8:
> ../include/toml++/impl/forward_declarations.h:253:42: note: candidate: 
> ‘template std::basic_ostream& 
> toml::v3::operator<<(std::basic_ostream&, node_type)’
>   253 | inline std::basic_ostream& 
> operator<<(std::basic_ostream& lhs, node_type rhs)
>   |  ^~~~
> ../include/toml++/impl/forward_declarations.h:253:42: note:   template 
> argument deduction/substitution failed:
> ../tests/tests.h:151:23: note:   ‘std::basic_string_view’ is not 
> derived from ‘std::basic_ostream’
>   151 | INFO("["sv << test_file << ", line "sv << test_line << "] "sv
>   |   ^
> In file included from ../include/toml++/impl/std_string.h:9,
>  from ../include/toml++/toml.h:34:
> /usr/include/c++/13/string_view:760:5: note: candidate: ‘template _CharT, class _Traits> std::basic_ostream<_CharT, _Traits>& 
> std::operator<<(basic_ostream<_CharT, _Traits>&, basic_string_view<_CharT, 
> _Traits>)’
>   760 | operator<<(basic_ostream<_CharT, _Traits>& __os,
>   | ^~~~
> /usr/include/c++/13/string_view:760:5: note:   template argument 
> deduction/substitution failed:
> ../tests/tests.h:151:23: note:   ‘std::basic_string_view’ is not 
> derived from ‘std::basic_ostream<_CharT, _Traits>’
>   151 | INFO("["sv << test_file << ", line "sv << test_line << "] "sv
>   |   ^
> In file included from /usr/include/c++/13/string:54,
>  from ../include/toml++/impl/std_string.h:10:
> /usr/include/c++/13/bits/basic_stri

Processed: also happens in bookworm

2023-11-04 Thread Debian Bug Tracking System 
Processing commands for cont...@bugs.debian.org:

> found 1051924 2.23.4
Bug #1051924 [devscripts] devscripts: FTBFS fails in test test/test_debchange
Marked as found in versions devscripts/2.23.4.
> thanks
Stopping processing here.

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

Bug#1054803: marked as done (dynarmic: FTBFS: make[1]: *** [debian/rules:18: override_dh_auto_configure] Error 2)

2023-11-04 Thread Debian Bug Tracking System 
Your message dated Sat, 04 Nov 2023 13:19:15 +
with message-id 
and subject line Bug#1054803: fixed in dynarmic 6.5.0+ds-1.1
has caused the Debian Bug report #1054803,
regarding dynarmic: FTBFS: make[1]: *** [debian/rules:18: 
override_dh_auto_configure] Error 2
to be marked as done.

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

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


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

Hi,

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


Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> dh_auto_configure -- \
>   -DBUILD_SHARED_LIBS=true \
>   -DCMAKE_INTERPROCEDURAL_OPTIMIZATION=true \
>   -DCMAKE_POLICY_DEFAULT_CMP0069=NEW \
>   -DDYNARMIC_IGNORE_ASSERTS=true \
>   -DDYNARMIC_TESTS=true \
>   -DDYNARMIC_TESTS_USE_UNICORN=false \
>   -DDYNARMIC_USE_LLVM=true \
>   -DDYNARMIC_USE_PRECOMPILED_HEADERS=false
>   cd obj-x86_64-linux-gnu && DEB_PYTHON_INSTALL_LAYOUT=deb cmake 
> -DCMAKE_INSTALL_PREFIX=/usr -DCMAKE_BUILD_TYPE=None 
> -DCMAKE_INSTALL_SYSCONFDIR=/etc -DCMAKE_INSTALL_LOCALSTATEDIR=/var 
> -DCMAKE_EXPORT_NO_PACKAGE_REGISTRY=ON -DCMAKE_FIND_USE_PACKAGE_REGISTRY=OFF 
> -DCMAKE_FIND_PACKAGE_NO_PACKAGE_REGISTRY=ON 
> -DFETCHCONTENT_FULLY_DISCONNECTED=ON -DCMAKE_INSTALL_RUNSTATEDIR=/run 
> -DCMAKE_SKIP_INSTALL_ALL_DEPENDENCY=ON "-GUnix Makefiles" 
> -DCMAKE_VERBOSE_MAKEFILE=ON -DCMAKE_INSTALL_LIBDIR=lib/x86_64-linux-gnu 
> -DBUILD_SHARED_LIBS=true -DCMAKE_INTERPROCEDURAL_OPTIMIZATION=true 
> -DCMAKE_POLICY_DEFAULT_CMP0069=NEW -DDYNARMIC_IGNORE_ASSERTS=true 
> -DDYNARMIC_TESTS=true -DDYNARMIC_TESTS_USE_UNICORN=false 
> -DDYNARMIC_USE_LLVM=true -DDYNARMIC_USE_PRECOMPILED_HEADERS=false ..
> -- The C compiler identification is GNU 13.2.0
> -- The CXX compiler identification is GNU 13.2.0
> -- The ASM compiler identification is GNU
> -- Found assembler: /usr/bin/cc
> -- Detecting C compiler ABI info
> -- Detecting C compiler ABI info - done
> -- Check for working C compiler: /usr/bin/cc - skipped
> -- Detecting C compile features
> -- Detecting C compile features - done
> -- Detecting CXX compiler ABI info
> -- Detecting CXX compiler ABI info - done
> -- Check for working CXX compiler: /usr/bin/c++ - skipped
> -- Detecting CXX compile features
> -- Detecting CXX compile features - done
> -- Target architecture: x86_64
> -- Found Boost: 
> /usr/lib/x86_64-linux-gnu/cmake/Boost-1.74.0/BoostConfig.cmake (found 
> suitable version "1.74.0", minimum required is "1.57")  
> -- Performing Test HAVE_FFI_CALL
> -- Performing Test HAVE_FFI_CALL - Success
> -- Found FFI: /usr/lib/x86_64-linux-gnu/libffi.so  
> -- Performing Test Terminfo_LINKABLE
> -- Performing Test Terminfo_LINKABLE - Success
> -- Found Terminfo: /usr/lib/x86_64-linux-gnu/libtinfo.so  
> -- Found ZLIB: /usr/lib/x86_64-linux-gnu/libz.so (found version "1.2.13")  
> -- Could NOT find zstd (missing: zstd_LIBRARY zstd_INCLUDE_DIR) 
> -- Found LibXml2: /usr/lib/x86_64-linux-gnu/libxml2.so (found version 
> "2.9.14") 
> -- Could NOT find CURL (missing: CURL_LIBRARY CURL_INCLUDE_DIR) 
> CMake Error at externals/CMakeLists.txt:22 (add_subdirectory):
>   add_subdirectory given source "catch" which is not an existing directory.
> 
> 
> -- Configuring incomplete, errors occurred!
>   cd obj-x86_64-linux-gnu && tail -v -n \+0 CMakeCache.txt
> ==> CMakeCache.txt <==
> # This is the CMakeCache file.
> # For build in directory: /<>/obj-x86_64-linux-gnu
> # It was generated by CMake: /usr/bin/cmake
> # You can edit this file to change values found and used by cmake.
> # If you do not want to change any of the values, simply exit the editor.
> # If you do want to change a value, simply edit, save, and exit the editor.
> # The syntax for the file is as follows:
> # KEY:TYPE=VALUE
> # KEY is the name of a variable in the cache.
> # TYPE is a hint to GUIs for the type of VALUE, DO NOT EDIT TYPE!.
> # VALUE is the current value for the KEY.
> 
> 
> # EXTERNAL cache entries
> 
> 
> //No help, variable specified on the command line.
> BUILD_SHARED_LIBS:UNINITIALIZED=true
> 
> //Build the testing tree.
> BUILD_TESTING:BOOL=ON
> 
> //The directory containing a CMake configuration file for Boost.
> Boost_DIR:PATH=/usr/lib/x86_64-linux-gnu/cmake/Boost-1.74.0
> 
> //Path to a file.
> Boost_INCLUDE_DIR:PATH=/usr/include
> 
> /

Bug#1052347: src:canu: fails to migrate to testing for too long: unresolved RC issue

2023-11-04 Thread Nilesh Patra 
On Wed, 1 Nov 2023 19:23:13 +0100 Paul Gevers  wrote:
> Hi Andreas,
> 
> On 01-11-2023 07:34, Andreas Tille wrote:
> >... is it possible that the CI is restricting memory so when it tries
> >to allocate some it fails?
> 
> Because of lack of automatic reporting, I created this wiki some time ago:
> https://wiki.debian.org/ContinuousIntegration/WorkerSpecs
> 
> The memory for the arm64 workers isn't huge (8GB), but all i386 and some 
> of the amd64 workers have the same.

On the same threads, Michael said that he is not able to reproduce the error on 
arm64 porter box however it fails in debci.

The upstream needs the *.out files of the failing tests, as they said at [1]. 
Since it does not work on porter box, and chokes on the CI infra, could you 
please provide these files?

[1]: https://github.com/marbl/canu/issues/2271#issuecomment-1772870568

Thanks,
Nilesh

Bug#1054803: marked as pending in dynarmic

2023-11-04 Thread Bastian Germann 
Control: tag -1 pending

Hello,

Bug #1054803 in dynarmic 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/debian/dynarmic/-/commit/b233e0c05183dd89710dee46ee4655a592582270


Drop catch2 patch (Closes: #1054803)


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1054803

Processed: Bug#1054803 marked as pending in dynarmic

2023-11-04 Thread Debian Bug Tracking System 
Processing control commands:

> tag -1 pending
Bug #1054803 [src:dynarmic] dynarmic: FTBFS: make[1]: *** [debian/rules:18: 
override_dh_auto_configure] Error 2
Added tag(s) pending.

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

Bug#1054667: marked as done (node-browserify-sign: CVE-2023-46234)

2023-11-04 Thread Debian Bug Tracking System 
Your message dated Sat, 04 Nov 2023 12:47:09 +
with message-id 
and subject line Bug#1054667: fixed in node-browserify-sign 4.2.1-3+deb12u1
has caused the Debian Bug report #1054667,
regarding node-browserify-sign: CVE-2023-46234
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.)


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

Hi,

The following vulnerability was published for node-browserify-sign.

CVE-2023-46234[0]:
| browserify-sign is a package to duplicate the functionality of
| node's crypto public key functions, much of this is based on Fedor
| Indutny's work on indutny/tls.js. An upper bound check issue in
| `dsaVerify` function allows an attacker to construct signatures that
| can be successfully verified by any public key, thus leading to a
| signature forgery attack. All places in this project that involve
| DSA verification of user-input signatures will be affected by this
| vulnerability. This issue has been patched in version 4.2.2.

https://github.com/browserify/browserify-sign/security/advisories/GHSA-x9w5-v3q2-3rhw
https://github.com/browserify/browserify-sign/commit/85994cd6348b50f2fd1b73c54e20881416f44a30


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

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2023-46234
https://www.cve.org/CVERecord?id=CVE-2023-46234

Please adjust the affected versions in the BTS as needed.
--- End Message ---
--- Begin Message ---
Source: node-browserify-sign
Source-Version: 4.2.1-3+deb12u1
Done: Yadd 

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

Debian distribution maintenance software
pp.
Yadd  (supplier of updated node-browserify-sign 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, 28 Oct 2023 12:03:04 +0400
Source: node-browserify-sign
Binary: node-browserify-sign
Architecture: source all
Version: 4.2.1-3+deb12u1
Distribution: bookworm-security
Urgency: high
Maintainer: Debian Javascript Maintainers 

Changed-By: Yadd 
Description:
 node-browserify-sign - adds node crypto signing for browsers
Closes: 1054667
Changes:
 node-browserify-sign (4.2.1-3+deb12u1) bookworm-security; urgency=high
 .
   * Team upload
   * Properly check the upper bound for DSA signatures (Closes: #1054667, 
CVE-2023-46234)
Checksums-Sha1:
 444d8e3740b840ad569b76a7c8f4d4befda9c1a8 2432 
node-browserify-sign_4.2.1-3+deb12u1.dsc
 37ca70e9e63c2cdb92bc38d86ea9edac8d3c96b9 80701 
node-browserify-sign_4.2.1.orig.tar.gz
 f9f5497b715190c4d44d272d8a4132ea48311719 14192 
node-browserify-sign_4.2.1-3+deb12u1.debian.tar.xz
 013c5ca46f08ced24ba586fefb0d236e69aea7da 6976 
node-browserify-sign_4.2.1-3+deb12u1_all.deb
 833d48cc732405cf549f9fa557f33bc54b27b91b 16403 
node-browserify-sign_4.2.1-3+deb12u1_amd64.buildinfo
Checksums-Sha256:
 b8ec0b68d7cea35687ecab83d79d121c43b50f5c385040040c77c8bbccae9d27 2432 
node-browserify-sign_4.2.1-3+deb12u1.dsc
 b01c1c04298b186409f3056cb26170dbb9e08dbb399182afd3a8bcbb1aa509c5 80701 
node-browserify-sign_4.2.1.orig.tar.gz
 463dda8ac25691fed0cf297a78d98bda5a8340b7e9b5aab022755624e31794db 14192 
node-browserify-sign_4.2.1-3+deb12u1.debian.tar.xz
 81bfd39756139f1af44018032d7fba7796deaa9d1276f4659ae37eccf838d4d3 6976 
node-browserify-sign_4.2.1-3+deb12u1_all.deb
 9b56447c0d919cffb870b25c53ee0b9a5fd9e3bbc5df6bd54d5d5f886236233b 16403 
node-browserify-sign_4.2.1-3+deb12u1_amd64.buildinfo
Files:
 5481c699fbd5489fb0da5962d5361a59 2432 javascript optional 
node-browserify-sign_4.2.1-3+deb12u1.dsc
 2ea291f5485de7542d6dc1bd9bcf2472 80701 javascript optional 
node-browserify-sign_4.2.1.orig.tar.gz
 a53d5f2ca4fe6e9f5ee2b173c6336cec 14192 javascript optional 
node-browserify-sign_4.2.1-3+deb12u1.debian.tar.xz
 f8529f6c380327a0720cb5f00d238915 6976 javascript optiona

Bug#1054224: marked as done (zookeeper: CVE-2023-44981)

2023-11-04 Thread Debian Bug Tracking System 
Your message dated Sat, 04 Nov 2023 12:47:39 +
with message-id 
and subject line Bug#1054224: fixed in zookeeper 3.8.0-11+deb12u1
has caused the Debian Bug report #1054224,
regarding zookeeper: CVE-2023-44981
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.)


-- 
1054224: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1054224
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: zookeeper
Version: 3.8.0-11
Severity: grave
Tags: security upstream
X-Debbugs-Cc: car...@debian.org, Debian Security Team 
Control: found -1 3.4.13-6

Hi,

The following vulnerability was published for zookeeper.

CVE-2023-44981[0]:
| Authorization Bypass Through User-Controlled Key vulnerability in
| Apache ZooKeeper. If SASL Quorum Peer authentication is enabled in
| ZooKeeper (quorum.auth.enableSasl=true), the authorization is done
| by verifying that the instance part in SASL authentication ID is
| listed in zoo.cfg server list. The instance part in SASL auth ID is
| optional and if it's missing, like 'e...@example.com', the
| authorization check will be skipped. As a result an arbitrary
| endpoint could join the cluster and begin propagating counterfeit
| changes to the leader, essentially giving it complete read-write
| access to the data tree. Quorum Peer authentication is not enabled
| by default.  Users are recommended to upgrade to version 3.9.1,
| 3.8.3, 3.7.2, which fixes the issue.  Alternately ensure the
| ensemble election/quorum communication is protected by a firewall as
| this will mitigate the issue.  See the documentation for more
| details on correct cluster administration.


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

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2023-44981
https://www.cve.org/CVERecord?id=CVE-2023-44981
[1] https://www.openwall.com/lists/oss-security/2023/10/11/4
[2] 
https://github.com/apache/zookeeper/commit/96b3172ca249a8580e9a315d589d319286cee4ee

Regards,
Salvatore
--- End Message ---
--- Begin Message ---
Source: zookeeper
Source-Version: 3.8.0-11+deb12u1
Done: Pierre Gruet 

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

Debian distribution maintenance software
pp.
Pierre Gruet  (supplier of updated zookeeper 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, 29 Oct 2023 08:57:11 +0100
Source: zookeeper
Architecture: source
Version: 3.8.0-11+deb12u1
Distribution: bookworm-security
Urgency: medium
Maintainer: Debian Java Maintainers 

Changed-By: Pierre Gruet 
Closes: 1054224
Changes:
 zookeeper (3.8.0-11+deb12u1) bookworm-security; urgency=medium
 .
   * Team upload:
 - CVE-2023-44981: Prevent a potential authorisation bypass vulnerability.
   If SASL Quorum Peer authentication was enabled (via
   quorum.auth.enableSasl), authorisation was performed by verifying that
   the instance part in the SASL authentication ID was listed in the zoo.cfg
   server list. However, this value is optional, and, if missing (such as in
   'e...@example.com'), the authorisation check will be skipped. As a 
result,
   an arbitrary endpoint could join the cluster and begin propagating
   counterfeit changes to the leader, essentially giving it complete
   read-write access to the data tree. (Closes: #1054224)
Checksums-Sha1:
 7fd7e9ee04fbcd149950e1b23f42547153db2593 3799 zookeeper_3.8.0-11+deb12u1.dsc
 c6556b6e4237f78955e3d8cd313d0ef04ed1b7e9 3485515 zookeeper_3.8.0.orig.tar.gz
 c2622953992c4495ac935662243a60c4e40d8828 488 zookeeper_3.8.0.orig.tar.gz.asc
 3376643eaea0466e1962182574b9e5ac4fbb93e6 92236 
zookeeper_3.8.0-11+deb12u1.debian.tar.xz
 95289d007c7d7cb8c6bdfde75cf05042b5d903f8 24524 
zookeeper_3.8.0-11+deb12u1_amd64.buildinfo
Checksums-Sha256:
 bf8164ee16a6ddad74de4fb04ef280236b71d0c95c17e1d30ea4c33054f171d2 3799 
zookeeper_3.8.0-11+deb12u1.dsc
 b0c5684640bea2d8bd6610b47ff41be2aefd6c910ba48fcad5949bd2bf2fa1ac 3485515 
zookee

Bug#1054666: marked as done (open-vm-tools: CVE-2023-34059 CVE-2023-34058)

2023-11-04 Thread Debian Bug Tracking System 
Your message dated Sat, 04 Nov 2023 12:47:09 +
with message-id 
and subject line Bug#1054666: fixed in open-vm-tools 2:12.2.0-1+deb12u2
has caused the Debian Bug report #1054666,
regarding open-vm-tools: CVE-2023-34059 CVE-2023-34058
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.)


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

Hi,

The following vulnerabilities were published for open-vm-tools.

CVE-2023-34059[0]:
| open-vm-tools contains a file descriptor hijack vulnerability in the
| vmware-user-suid-wrapper. A malicious actor with non-root privileges
| may be able to hijack the  /dev/uinput file descriptor allowing them
| to simulate user inputs.

https://www.openwall.com/lists/oss-security/2023/10/27/3

CVE-2023-34058[1]:
| VMware Tools contains a SAML token signature bypass vulnerability. A
| malicious actor that has been granted  Guest Operation Privileges
| https://docs.vmware.com/en/VMware-vSphere/8.0/vsphere-
| security/GUID-6A952214-0E5E-4CCF-9D2A-90948FF643EC.html  in a target
| virtual machine may be able to elevate their privileges if that
| target virtual machine has been assigned a more privileged  Guest
| Alias https://vdc-download.vmware.com/vmwb-repository/dcr-
| public/d1902b0e-d479-46bf-8ac9-cee0e31e8ec0/07ce8dbd-
| db48-4261-9b8f-c6d3ad8ba472/vim.vm.guest.AliasManager.html .

https://www.openwall.com/lists/oss-security/2023/10/27/1
https://github.com/vmware/open-vm-tools/blob/CVE-2023-34058.patch/CVE-2023-34058.patch


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

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2023-34059
https://www.cve.org/CVERecord?id=CVE-2023-34059
[1] https://security-tracker.debian.org/tracker/CVE-2023-34058
https://www.cve.org/CVERecord?id=CVE-2023-34058

Please adjust the affected versions in the BTS as needed.
--- End Message ---
--- Begin Message ---
Source: open-vm-tools
Source-Version: 2:12.2.0-1+deb12u2
Done: Bernd Zeimetz 

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

Debian distribution maintenance software
pp.
Bernd Zeimetz  (supplier of updated open-vm-tools package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Mon, 30 Oct 2023 17:59:25 +0100
Source: open-vm-tools
Architecture: source
Version: 2:12.2.0-1+deb12u2
Distribution: bookworm-security
Urgency: medium
Maintainer: Bernd Zeimetz 
Changed-By: Bernd Zeimetz 
Closes: 1054666
Changes:
 open-vm-tools (2:12.2.0-1+deb12u2) bookworm-security; urgency=medium
 .
   * Closes:  #1054666
   * [81326c8] Fixing CVE-2023-34059.
 This fixes a file descriptor hijack vulnerability in the 
vmware-user-suid-wrapper
 command.  A malicious actor with non-root privileges might have been able 
to hijack the
 /dev/uinput file descriptor allowing them to simulate user inputs.
   * [95acc49] Fixing CVE-2023-34058.
 This fixes a SAML Token Signature Bypass vulnerability. A malicious actor
 that has been granted Guest Operation Privileges in a target virtual
 machine might have been able to elevate their privileges if that target
 virtual machine has been assigned a more privileged Guest Alias.
Checksums-Sha1:
 6bfc93c62dc26555754cb91846a166389b7ac672 2944 
open-vm-tools_12.2.0-1+deb12u2.dsc
 112cd82f38ebb66afb77c2a3c5a5311f86fa0c39 39740 
open-vm-tools_12.2.0-1+deb12u2.debian.tar.xz
 2a86f97839b4fa6410d03254d6ba98a590673773 5533 
open-vm-tools_12.2.0-1+deb12u2_source.buildinfo
Checksums-Sha256:
 b33137fe8ac9e50003a90026efd74fd20962dfb4e877cc80fe4401187e190e55 2944 
open-vm-tools_12.2.0-1+deb12u2.dsc
 86b76972e193a0c41eafa79005c977e24cd619b76a9b0f8f007b36d241ee951a 39740 
open-vm-tools_12.2.0-1+deb12u2.debian.tar.xz
 9b93eaff53e9fc75f1923b0ebe29875847f73105e6d96176f645d3e24f5f476d 5533 
open-vm-too

Bug#1053261: marked as done (gst-plugins-bad1.0: CVE-2023-40474)

2023-11-04 Thread Debian Bug Tracking System 
Your message dated Sat, 04 Nov 2023 12:48:11 +
with message-id 
and subject line Bug#1053261: fixed in gst-plugins-bad1.0 1.18.4-3+deb11u2
has caused the Debian Bug report #1053261,
regarding gst-plugins-bad1.0: CVE-2023-40474
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.)


-- 
1053261: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1053261
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: gst-plugins-bad1.0
Version: 1.22.4-1
Severity: grave
Tags: security upstream
X-Debbugs-Cc: car...@debian.org, Debian Security Team 

Hi,

The following vulnerability was published for gst-plugins-bad1.0.

CVE-2023-40474[0]:
| Integer overflow leading to heap overwrite in MXF file handling with
| uncompressed video


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

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2023-40474
https://www.cve.org/CVERecord?id=CVE-2023-40474
[1] https://gstreamer.freedesktop.org/security/sa-2023-0006.html
[2] 
https://gitlab.freedesktop.org/gstreamer/gstreamer/-/commit/ce17e968e4cf900d28ca5b46f6e095febc42b4f0

Please adjust the affected versions in the BTS as needed.

Regards,
Salvatore
--- End Message ---
--- Begin Message ---
Source: gst-plugins-bad1.0
Source-Version: 1.18.4-3+deb11u2
Done: Salvatore Bonaccorso 

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

Debian distribution maintenance software
pp.
Salvatore Bonaccorso  (supplier of updated 
gst-plugins-bad1.0 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, 07 Oct 2023 22:34:42 +0200
Source: gst-plugins-bad1.0
Architecture: source
Version: 1.18.4-3+deb11u2
Distribution: bullseye-security
Urgency: high
Maintainer: Maintainers of GStreamer packages 

Changed-By: Salvatore Bonaccorso 
Closes: 1053259 1053260 1053261
Changes:
 gst-plugins-bad1.0 (1.18.4-3+deb11u2) bullseye-security; urgency=high
 .
   * Non-maintainer upload by the Security Team.
   * h265parser: Fix possible overflow using max_sub_layers_minus1
 (CVE-2023-40476) (Closes: #1053259)
   * mxfdemux: Fix integer overflow causing out of bounds writes when handling
 invalid uncompressed video (CVE-2023-40474) (Closes: #1053261)
   * mxfdemux: Check number of channels for AES3 audio (CVE-2023-40475)
 (Closes: #1053260)
Checksums-Sha1:
 ba222f3955d789ab90302f79b07071afc27244a5 5791 
gst-plugins-bad1.0_1.18.4-3+deb11u2.dsc
 d198adcd5d89897c9efd0fcb7b7712c08cf7883e 34924 
gst-plugins-bad1.0_1.18.4-3+deb11u2.debian.tar.xz
 3447a7c1f53e69cdf777f1de8d6042e4619f1e13 7448 
gst-plugins-bad1.0_1.18.4-3+deb11u2_source.buildinfo
Checksums-Sha256:
 66a554a03b50a21b1c2c3eecd1e67ab39131ac13715e16f2bd5d9238034f4f66 5791 
gst-plugins-bad1.0_1.18.4-3+deb11u2.dsc
 fb19fbb975abcc555b6c06e8b750aa5f14429269287297c434f8c5722f713689 34924 
gst-plugins-bad1.0_1.18.4-3+deb11u2.debian.tar.xz
 bde1518cbad61b963a21cdd4b2000a6247381712d087170f011825710df309ae 7448 
gst-plugins-bad1.0_1.18.4-3+deb11u2_source.buildinfo
Files:
 6d1213ca745a1d17941fe420157b5887 5791 libs optional 
gst-plugins-bad1.0_1.18.4-3+deb11u2.dsc
 5cbb227a790c7c5d4219553dae36cf36 34924 libs optional 
gst-plugins-bad1.0_1.18.4-3+deb11u2.debian.tar.xz
 9ed18b26ce6eb5fb6730b4bf68bb2c65 7448 libs optional 
gst-plugins-bad1.0_1.18.4-3+deb11u2_source.buildinfo

-BEGIN PGP SIGNATURE-

iQKmBAEBCgCQFiEERkRAmAjBceBVMd3uBUy48xNDz0QFAmUhxtNfFIAALgAo
aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldDQ2
NDQ0MDk4MDhDMTcxRTA1NTMxRERFRTA1NENCOEYzMTM0M0NGNDQSHGNhcm5pbEBk
ZWJpYW4ub3JnAAoJEAVMuPMTQ89E5RIP/jeEKsIhBkIhCIUmCF51mQ8qUZJV1bBm
XOomI8MlxNqtZGpUo29G3xZdx5b5muEKG5aPsgQUwJqb+TPN+gKUsBkWFMD5oQq2
1nVB/YlBqGGNsi0LvjYaJFnucHC4/rRtOlXR5Fsm3kFTEkFoC/dwQzOCrGIHjqg5
oh+B+aDX9joI4kRiJbz/lULiCDJSKeCpVRTkFU55S4Y4hgd4rLq3y7gX3q/JWZYY
sxTDIR7Up3QSRllIglcZHs2xJ9gWzLeiVZwG4pj4j3cxYAhFhSp8y1m6RViYYB1Y
Us+YTMnKcoYpvsJLLcTKiC765RD/HQwBIrTUfnoTxKul8siZedPDkUkw0dKakZg9
z55k/ue8K56nifLDXj

Bug#1053260: marked as done (gst-plugins-bad1.0: CVE-2023-40475)

2023-11-04 Thread Debian Bug Tracking System 
Your message dated Sat, 04 Nov 2023 12:48:11 +
with message-id 
and subject line Bug#1053260: fixed in gst-plugins-bad1.0 1.18.4-3+deb11u2
has caused the Debian Bug report #1053260,
regarding gst-plugins-bad1.0: CVE-2023-40475
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.)


-- 
1053260: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1053260
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: gst-plugins-bad1.0
Version: 1.22.4-1
Severity: grave
Tags: security upstream
X-Debbugs-Cc: car...@debian.org, Debian Security Team 

Hi,

The following vulnerability was published for gst-plugins-bad1.0.

CVE-2023-40475[0]:
| Integer overflow leading to heap overwrite in MXF file handling with
| AES3 audio


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

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2023-40475
https://www.cve.org/CVERecord?id=CVE-2023-40475
[1] https://gstreamer.freedesktop.org/security/sa-2023-0007.html
[2] 
https://gitlab.freedesktop.org/gstreamer/gstreamer/-/commit/72742dee30cce7bf909639f82de119871566ce39

Please adjust the affected versions in the BTS as needed.

Regards,
Salvatore
--- End Message ---
--- Begin Message ---
Source: gst-plugins-bad1.0
Source-Version: 1.18.4-3+deb11u2
Done: Salvatore Bonaccorso 

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

Debian distribution maintenance software
pp.
Salvatore Bonaccorso  (supplier of updated 
gst-plugins-bad1.0 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, 07 Oct 2023 22:34:42 +0200
Source: gst-plugins-bad1.0
Architecture: source
Version: 1.18.4-3+deb11u2
Distribution: bullseye-security
Urgency: high
Maintainer: Maintainers of GStreamer packages 

Changed-By: Salvatore Bonaccorso 
Closes: 1053259 1053260 1053261
Changes:
 gst-plugins-bad1.0 (1.18.4-3+deb11u2) bullseye-security; urgency=high
 .
   * Non-maintainer upload by the Security Team.
   * h265parser: Fix possible overflow using max_sub_layers_minus1
 (CVE-2023-40476) (Closes: #1053259)
   * mxfdemux: Fix integer overflow causing out of bounds writes when handling
 invalid uncompressed video (CVE-2023-40474) (Closes: #1053261)
   * mxfdemux: Check number of channels for AES3 audio (CVE-2023-40475)
 (Closes: #1053260)
Checksums-Sha1:
 ba222f3955d789ab90302f79b07071afc27244a5 5791 
gst-plugins-bad1.0_1.18.4-3+deb11u2.dsc
 d198adcd5d89897c9efd0fcb7b7712c08cf7883e 34924 
gst-plugins-bad1.0_1.18.4-3+deb11u2.debian.tar.xz
 3447a7c1f53e69cdf777f1de8d6042e4619f1e13 7448 
gst-plugins-bad1.0_1.18.4-3+deb11u2_source.buildinfo
Checksums-Sha256:
 66a554a03b50a21b1c2c3eecd1e67ab39131ac13715e16f2bd5d9238034f4f66 5791 
gst-plugins-bad1.0_1.18.4-3+deb11u2.dsc
 fb19fbb975abcc555b6c06e8b750aa5f14429269287297c434f8c5722f713689 34924 
gst-plugins-bad1.0_1.18.4-3+deb11u2.debian.tar.xz
 bde1518cbad61b963a21cdd4b2000a6247381712d087170f011825710df309ae 7448 
gst-plugins-bad1.0_1.18.4-3+deb11u2_source.buildinfo
Files:
 6d1213ca745a1d17941fe420157b5887 5791 libs optional 
gst-plugins-bad1.0_1.18.4-3+deb11u2.dsc
 5cbb227a790c7c5d4219553dae36cf36 34924 libs optional 
gst-plugins-bad1.0_1.18.4-3+deb11u2.debian.tar.xz
 9ed18b26ce6eb5fb6730b4bf68bb2c65 7448 libs optional 
gst-plugins-bad1.0_1.18.4-3+deb11u2_source.buildinfo

-BEGIN PGP SIGNATURE-

iQKmBAEBCgCQFiEERkRAmAjBceBVMd3uBUy48xNDz0QFAmUhxtNfFIAALgAo
aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldDQ2
NDQ0MDk4MDhDMTcxRTA1NTMxRERFRTA1NENCOEYzMTM0M0NGNDQSHGNhcm5pbEBk
ZWJpYW4ub3JnAAoJEAVMuPMTQ89E5RIP/jeEKsIhBkIhCIUmCF51mQ8qUZJV1bBm
XOomI8MlxNqtZGpUo29G3xZdx5b5muEKG5aPsgQUwJqb+TPN+gKUsBkWFMD5oQq2
1nVB/YlBqGGNsi0LvjYaJFnucHC4/rRtOlXR5Fsm3kFTEkFoC/dwQzOCrGIHjqg5
oh+B+aDX9joI4kRiJbz/lULiCDJSKeCpVRTkFU55S4Y4hgd4rLq3y7gX3q/JWZYY
sxTDIR7Up3QSRllIglcZHs2xJ9gWzLeiVZwG4pj4j3cxYAhFhSp8y1m6RViYYB1Y
Us+YTMnKcoYpvsJLLcTKiC765RD/HQwBIrTUfnoTxKul8siZedPDkUkw0dKakZg9
z55k/ue8K56nifLDXjWF67U6Mx

Bug#1054667: marked as done (node-browserify-sign: CVE-2023-46234)

2023-11-04 Thread Debian Bug Tracking System 
Your message dated Sat, 04 Nov 2023 12:48:27 +
with message-id 
and subject line Bug#1054667: fixed in node-browserify-sign 4.2.1-1+deb11u1
has caused the Debian Bug report #1054667,
regarding node-browserify-sign: CVE-2023-46234
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.)


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

Hi,

The following vulnerability was published for node-browserify-sign.

CVE-2023-46234[0]:
| browserify-sign is a package to duplicate the functionality of
| node's crypto public key functions, much of this is based on Fedor
| Indutny's work on indutny/tls.js. An upper bound check issue in
| `dsaVerify` function allows an attacker to construct signatures that
| can be successfully verified by any public key, thus leading to a
| signature forgery attack. All places in this project that involve
| DSA verification of user-input signatures will be affected by this
| vulnerability. This issue has been patched in version 4.2.2.

https://github.com/browserify/browserify-sign/security/advisories/GHSA-x9w5-v3q2-3rhw
https://github.com/browserify/browserify-sign/commit/85994cd6348b50f2fd1b73c54e20881416f44a30


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

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2023-46234
https://www.cve.org/CVERecord?id=CVE-2023-46234

Please adjust the affected versions in the BTS as needed.
--- End Message ---
--- Begin Message ---
Source: node-browserify-sign
Source-Version: 4.2.1-1+deb11u1
Done: Yadd 

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

Debian distribution maintenance software
pp.
Yadd  (supplier of updated node-browserify-sign package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Mon, 30 Oct 2023 06:52:31 +0400
Source: node-browserify-sign
Binary: node-browserify-sign
Architecture: source all
Version: 4.2.1-1+deb11u1
Distribution: bullseye-security
Urgency: high
Maintainer: Debian Javascript Maintainers 

Changed-By: Yadd 
Description:
 node-browserify-sign - adds node crypto signing for browsers
Closes: 1054667
Changes:
 node-browserify-sign (4.2.1-1+deb11u1) bullseye-security; urgency=high
 .
   * Team upload
   * Properly check the upper bound for DSA signatures
 (Closes: #1054667, CVE-2023-46234)
Checksums-Sha1:
 077827db0dfbc74f8e676eee9eabd9c79c9bedda 2429 
node-browserify-sign_4.2.1-1+deb11u1.dsc
 37ca70e9e63c2cdb92bc38d86ea9edac8d3c96b9 80701 
node-browserify-sign_4.2.1.orig.tar.gz
 ba6401695afe8d449a629717b510e1a316a3c54e 3648 
node-browserify-sign_4.2.1-1+deb11u1.debian.tar.xz
 833ada12d661d562ea9af81dfab0424bc43be9ac 6700 
node-browserify-sign_4.2.1-1+deb11u1_all.deb
 1f198d561da1f9c5aa8c26747f29103f3f184b89 9438 
node-browserify-sign_4.2.1-1+deb11u1_amd64.buildinfo
Checksums-Sha256:
 f039d89d7d48ee479c537d7d245fc88063d62fef7bb91c561905eb37c721b24b 2429 
node-browserify-sign_4.2.1-1+deb11u1.dsc
 b01c1c04298b186409f3056cb26170dbb9e08dbb399182afd3a8bcbb1aa509c5 80701 
node-browserify-sign_4.2.1.orig.tar.gz
 78633da3201c1a043f7bd4515d243368c86982bee99617928b6ce8636d4476b7 3648 
node-browserify-sign_4.2.1-1+deb11u1.debian.tar.xz
 ebace15e67a7d11c770f6711d1f77e93b70f1f1800086a497cb9ea2990fbc58b 6700 
node-browserify-sign_4.2.1-1+deb11u1_all.deb
 7e3a78702dcffe035e44d7c9cbbad0d6bb191380af531c84e1c20ad047c5b192 9438 
node-browserify-sign_4.2.1-1+deb11u1_amd64.buildinfo
Files:
 84f213c5e0a910e6cb720c2c1c845f3e 2429 javascript optional 
node-browserify-sign_4.2.1-1+deb11u1.dsc
 2ea291f5485de7542d6dc1bd9bcf2472 80701 javascript optional 
node-browserify-sign_4.2.1.orig.tar.gz
 203d4cd9fee3c0539f56f402ca50ac75 3648 javascript optional 
node-browserify-sign_4.2.1-1+deb11u1.debian.tar.xz
 c983f3cf683c28afbc05ef94d1cb1e59 6700 javascript optional

Bug#1054224: marked as done (zookeeper: CVE-2023-44981)

2023-11-04 Thread Debian Bug Tracking System 
Your message dated Sat, 04 Nov 2023 12:49:14 +
with message-id 
and subject line Bug#1054224: fixed in zookeeper 3.4.13-6+deb11u1
has caused the Debian Bug report #1054224,
regarding zookeeper: CVE-2023-44981
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.)


-- 
1054224: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1054224
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: zookeeper
Version: 3.8.0-11
Severity: grave
Tags: security upstream
X-Debbugs-Cc: car...@debian.org, Debian Security Team 
Control: found -1 3.4.13-6

Hi,

The following vulnerability was published for zookeeper.

CVE-2023-44981[0]:
| Authorization Bypass Through User-Controlled Key vulnerability in
| Apache ZooKeeper. If SASL Quorum Peer authentication is enabled in
| ZooKeeper (quorum.auth.enableSasl=true), the authorization is done
| by verifying that the instance part in SASL authentication ID is
| listed in zoo.cfg server list. The instance part in SASL auth ID is
| optional and if it's missing, like 'e...@example.com', the
| authorization check will be skipped. As a result an arbitrary
| endpoint could join the cluster and begin propagating counterfeit
| changes to the leader, essentially giving it complete read-write
| access to the data tree. Quorum Peer authentication is not enabled
| by default.  Users are recommended to upgrade to version 3.9.1,
| 3.8.3, 3.7.2, which fixes the issue.  Alternately ensure the
| ensemble election/quorum communication is protected by a firewall as
| this will mitigate the issue.  See the documentation for more
| details on correct cluster administration.


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

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2023-44981
https://www.cve.org/CVERecord?id=CVE-2023-44981
[1] https://www.openwall.com/lists/oss-security/2023/10/11/4
[2] 
https://github.com/apache/zookeeper/commit/96b3172ca249a8580e9a315d589d319286cee4ee

Regards,
Salvatore
--- End Message ---
--- Begin Message ---
Source: zookeeper
Source-Version: 3.4.13-6+deb11u1
Done: Pierre Gruet 

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

Debian distribution maintenance software
pp.
Pierre Gruet  (supplier of updated zookeeper 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, 28 Oct 2023 23:16:44 +0200
Source: zookeeper
Architecture: source
Version: 3.4.13-6+deb11u1
Distribution: bullseye-security
Urgency: medium
Maintainer: Debian Java Maintainers 

Changed-By: Pierre Gruet 
Closes: 1054224
Changes:
 zookeeper (3.4.13-6+deb11u1) bullseye-security; urgency=medium
 .
   * Team upload:
 - CVE-2023-44981: Prevent a potential authorisation bypass vulnerability.
   If SASL Quorum Peer authentication was enabled (via
   quorum.auth.enableSasl), authorisation was performed by verifying that
   the instance part in the SASL authentication ID was listed in the zoo.cfg
   server list. However, this value is optional, and, if missing (such as in
   'e...@example.com'), the authorisation check will be skipped. As a 
result,
   an arbitrary endpoint could join the cluster and begin propagating
   counterfeit changes to the leader, essentially giving it complete
   read-write access to the data tree. (Closes: #1054224)
Checksums-Sha1:
 cd54ff6306b6f2053cfb4020a9159d1aa1624059 3041 zookeeper_3.4.13-6+deb11u1.dsc
 8d1fed2574e8645060154fcffdf7918ea5858377 1970528 zookeeper_3.4.13.orig.tar.xz
 b650c655fd9b27811042e89fd48816a5fe08272d 63300 
zookeeper_3.4.13-6+deb11u1.debian.tar.xz
 fdebce856845a509f7097da27586d02a58cecffe 19074 
zookeeper_3.4.13-6+deb11u1_amd64.buildinfo
Checksums-Sha256:
 4c871960c79a09b9bbee6ef720deefb83a6be56414e23c5f77e18edadee04529 3041 
zookeeper_3.4.13-6+deb11u1.dsc
 4f303a575a3e981d5ef8fe43a4fec157f320841a502eff96ae7cda902c278d2f 1970528 
zookeeper_3.4.13.orig.tar.xz
 ea9f1710fce0a0f9913d0fb814d096d8805dab70fece5b087893b

Bug#1053259: marked as done (gst-plugins-bad1.0: CVE-2023-40476)

2023-11-04 Thread Debian Bug Tracking System 
Your message dated Sat, 04 Nov 2023 12:48:11 +
with message-id 
and subject line Bug#1053259: fixed in gst-plugins-bad1.0 1.18.4-3+deb11u2
has caused the Debian Bug report #1053259,
regarding gst-plugins-bad1.0: CVE-2023-40476
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.)


-- 
1053259: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1053259
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: gst-plugins-bad1.0
Version: 1.22.4-1
Severity: grave
Tags: patch security upstream
X-Debbugs-Cc: car...@debian.org, Debian Security Team 

Hi,

The following vulnerability was published for gst-plugins-bad1.0.

CVE-2023-40476[0]:
| Integer overflow in H.265 video parser leading to stack overwrite


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

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2023-40476
https://www.cve.org/CVERecord?id=CVE-2023-40476
[1] https://gstreamer.freedesktop.org/security/sa-2023-0008.html
[2] 
https://gitlab.freedesktop.org/gstreamer/gstreamer/-/commit/ff91a3d8d6f7e2412c44663bf30fad5c7fdbc9d9

Please adjust the affected versions in the BTS as needed.

Regards,
Salvatore
--- End Message ---
--- Begin Message ---
Source: gst-plugins-bad1.0
Source-Version: 1.18.4-3+deb11u2
Done: Salvatore Bonaccorso 

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

Debian distribution maintenance software
pp.
Salvatore Bonaccorso  (supplier of updated 
gst-plugins-bad1.0 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, 07 Oct 2023 22:34:42 +0200
Source: gst-plugins-bad1.0
Architecture: source
Version: 1.18.4-3+deb11u2
Distribution: bullseye-security
Urgency: high
Maintainer: Maintainers of GStreamer packages 

Changed-By: Salvatore Bonaccorso 
Closes: 1053259 1053260 1053261
Changes:
 gst-plugins-bad1.0 (1.18.4-3+deb11u2) bullseye-security; urgency=high
 .
   * Non-maintainer upload by the Security Team.
   * h265parser: Fix possible overflow using max_sub_layers_minus1
 (CVE-2023-40476) (Closes: #1053259)
   * mxfdemux: Fix integer overflow causing out of bounds writes when handling
 invalid uncompressed video (CVE-2023-40474) (Closes: #1053261)
   * mxfdemux: Check number of channels for AES3 audio (CVE-2023-40475)
 (Closes: #1053260)
Checksums-Sha1:
 ba222f3955d789ab90302f79b07071afc27244a5 5791 
gst-plugins-bad1.0_1.18.4-3+deb11u2.dsc
 d198adcd5d89897c9efd0fcb7b7712c08cf7883e 34924 
gst-plugins-bad1.0_1.18.4-3+deb11u2.debian.tar.xz
 3447a7c1f53e69cdf777f1de8d6042e4619f1e13 7448 
gst-plugins-bad1.0_1.18.4-3+deb11u2_source.buildinfo
Checksums-Sha256:
 66a554a03b50a21b1c2c3eecd1e67ab39131ac13715e16f2bd5d9238034f4f66 5791 
gst-plugins-bad1.0_1.18.4-3+deb11u2.dsc
 fb19fbb975abcc555b6c06e8b750aa5f14429269287297c434f8c5722f713689 34924 
gst-plugins-bad1.0_1.18.4-3+deb11u2.debian.tar.xz
 bde1518cbad61b963a21cdd4b2000a6247381712d087170f011825710df309ae 7448 
gst-plugins-bad1.0_1.18.4-3+deb11u2_source.buildinfo
Files:
 6d1213ca745a1d17941fe420157b5887 5791 libs optional 
gst-plugins-bad1.0_1.18.4-3+deb11u2.dsc
 5cbb227a790c7c5d4219553dae36cf36 34924 libs optional 
gst-plugins-bad1.0_1.18.4-3+deb11u2.debian.tar.xz
 9ed18b26ce6eb5fb6730b4bf68bb2c65 7448 libs optional 
gst-plugins-bad1.0_1.18.4-3+deb11u2_source.buildinfo

-BEGIN PGP SIGNATURE-

iQKmBAEBCgCQFiEERkRAmAjBceBVMd3uBUy48xNDz0QFAmUhxtNfFIAALgAo
aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldDQ2
NDQ0MDk4MDhDMTcxRTA1NTMxRERFRTA1NENCOEYzMTM0M0NGNDQSHGNhcm5pbEBk
ZWJpYW4ub3JnAAoJEAVMuPMTQ89E5RIP/jeEKsIhBkIhCIUmCF51mQ8qUZJV1bBm
XOomI8MlxNqtZGpUo29G3xZdx5b5muEKG5aPsgQUwJqb+TPN+gKUsBkWFMD5oQq2
1nVB/YlBqGGNsi0LvjYaJFnucHC4/rRtOlXR5Fsm3kFTEkFoC/dwQzOCrGIHjqg5
oh+B+aDX9joI4kRiJbz/lULiCDJSKeCpVRTkFU55S4Y4hgd4rLq3y7gX3q/JWZYY
sxTDIR7Up3QSRllIglcZHs2xJ9gWzLeiVZwG4pj4j3cxYAhFhSp8y1m6RViYYB1Y
Us+YTMnKcoYpvsJLLcTKiC765RD/HQwBIrTUfnoTxKul8siZedPDkUkw0dKakZg9
z55k/ue8K56nifLDXjWF67U6MxS2hgGYUPZZ

Processed: this is fixed in bookworm and trixie and sid

2023-11-04 Thread Debian Bug Tracking System 
Processing commands for cont...@bugs.debian.org:

> tags 981600 - bookworm trixie sid
Bug #981600 [src:nghttp2] nghttp2: missing build-depends on tzdata (in 
arch-only build)
Removed tag(s) sid, bookworm, and trixie.
> thanks
Stopping processing here.

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

Bug#1054936: marked as done (agda-stdlib: FTBFS: unsatisfiable build-dependencies: agda-bin (< 2.6.3~), libghc-agda-dev (< 2.6.3~))

2023-11-04 Thread Debian Bug Tracking System 
Your message dated Sat, 04 Nov 2023 12:34:20 +
with message-id 
and subject line Bug#1054936: fixed in agda-stdlib 1.7.3-1
has caused the Debian Bug report #1054936,
regarding agda-stdlib: FTBFS: unsatisfiable build-dependencies: agda-bin (< 
2.6.3~), libghc-agda-dev (< 2.6.3~)
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.)


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

Hi,

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


Relevant part (hopefully):
> +--+
> | Install package build dependencies  
>  |
> +--+
> 
> 
> Setup apt archive
> -
> 
> Merged Build-Depends: debhelper-compat (= 12), agda-bin (>= 2.6.2), agda-bin 
> (<< 2.6.3~), libghc-agda-dev (>= 2.6.2), libghc-agda-dev (<< 2.6.3~), 
> libghc-filemanip-dev, build-essential, fakeroot
> Filtered Build-Depends: debhelper-compat (= 12), agda-bin (>= 2.6.2), 
> agda-bin (<< 2.6.3~), libghc-agda-dev (>= 2.6.2), libghc-agda-dev (<< 
> 2.6.3~), libghc-filemanip-dev, build-essential, fakeroot
> dpkg-deb: building package 'sbuild-build-depends-main-dummy' in 
> '/<>/apt_archive/sbuild-build-depends-main-dummy.deb'.
> Ign:1 copy:/<>/apt_archive ./ InRelease
> Get:2 copy:/<>/apt_archive ./ Release [609 B]
> Ign:3 copy:/<>/apt_archive ./ Release.gpg
> Get:4 copy:/<>/apt_archive ./ Sources [739 B]
> Get:5 copy:/<>/apt_archive ./ Packages [771 B]
> Fetched 2119 B in 0s (0 B/s)
> Reading package lists...
> Reading package lists...
> 
> Install main build dependencies (apt-based resolver)
> 
> 
> Installing build dependencies
> Reading package lists...
> Building dependency tree...
> Reading state information...
> Some packages could not be installed. This may mean that you have
> requested an impossible situation or if you are using the unstable
> distribution that some required packages have not yet been created
> or been moved out of Incoming.
> The following information may help to resolve the situation:
> 
> The following packages have unmet dependencies:
>  sbuild-build-depends-main-dummy : Depends: agda-bin (< 2.6.3~) but 
> 2.6.3-1+b1 is to be installed
>Depends: libghc-agda-dev (< 2.6.3~) but 
> 2.6.3-1+b1 is to be installed
> E: Unable to correct problems, you have held broken packages.
> apt-get failed.


The full build log is available from:
http://qa-logs.debian.net/2023/10/28/agda-stdlib_1.7.1-1_unstable.log

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

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

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

If you fail to reproduce this, please provide a build log and diff it with mine
so that we can identify if something relevant changed in the meantime.
--- End Message ---
--- Begin Message ---
Source: agda-stdlib
Source-Version: 1.7.3-1
Done: Ilias Tsitsimpis 

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

Debian distribution maintenance software
pp.
Ilias Tsitsimpis  (supplier of updated agda-stdlib 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, 0

Bug#1054815: marked as done (adios: FTBFS: mv: cannot stat 'debian/tmp/mpich/lib/python3.11/site-packages/adios_mpi': No such file or directory)

2023-11-04 Thread Debian Bug Tracking System 
Your message dated Sat, 04 Nov 2023 12:19:15 +
with message-id 
and subject line Bug#1054815: fixed in adios 1.13.1-32
has caused the Debian Bug report #1054815,
regarding adios: FTBFS: mv: cannot stat 
'debian/tmp/mpich/lib/python3.11/site-packages/adios_mpi': No such file or 
directory
to be marked as done.

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

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


-- 
1054815: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1054815
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: adios
Version: 1.13.1-31
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20231027 ftbfs-trixie

Hi,

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


Relevant part (hopefully):
> make[5]: Entering directory '/<>/build-mpich'
> (cd ..; \
> if git rev-parse &>/dev/null; then \
> echo "GITLOG=\"`git log -n 1 --format=\"Last commit on %ad hash %h\"`\"" 
> > /<>/build-mpich/adios_git_status; \
> echo "read -d '' GITSTAT <<'_EOF_'" >> 
> /<>/build-mpich/adios_git_status; \
> git status -uno >> /<>/build-mpich/adios_git_status; \
> echo "_EOF_" >> /<>/build-mpich/adios_git_status; \
> else \
> echo "GITLOG=\"git log not available\"" >> 
> /<>/build-mpich/adios_git_status; \
> echo "GITSTAT=\"git status not available\"" >> 
> /<>/build-mpich/adios_git_status; \
> echo "Note: git command not found or /<>/build-mpich is not 
> a git repository."; \
> fi) 
> Note: git command not found or /<>/build-mpich is not a git 
> repository.
> make[5]: Leaving directory '/<>/build-mpich'
> make[4]: Leaving directory '/<>/build-mpich'
> make[3]: Leaving directory '/<>/build-mpich'
> make[2]: Leaving directory '/<>/build-mpich'
> install -D -m 644  build-mpich/adios-mpi.pc 
> /<>/debian/tmp//usr/lib/x86_64-linux-gnu/pkgconfig/adios-mpich.pc
> for p in  python3.11 ; do \
>   ( set -e ; cd build-mpich/numpy && \
>   $p ./setup_mpi.py install --prefix=/<>/debian/tmp/mpich  ) 
> ;  \
>   mv debian/tmp/mpich/lib/$p/site-packages/adios_mpi \
>  debian/tmp/mpich/lib/$p/site-packages/adios_mpich ; \
>   done
> /usr/lib/python3/dist-packages/setuptools/dist.py:744: 
> SetuptoolsDeprecationWarning: Invalid dash-separated options
> !!
> 
> 
> 
> Usage of dash-separated 'description-file' will not be supported in 
> future
> versions. Please use the underscore name 'description_file' instead.
> 
> This deprecation is overdue, please update your project and remove 
> deprecated
> calls to avoid build errors in the future.
> 
> See 
> https://setuptools.pypa.io/en/latest/userguide/declarative_config.html for 
> details.
> 
> 
> 
> !!
>   opt = self.warn_dash_deprecation(opt, section)
> /usr/lib/python3/dist-packages/setuptools/command/sdist.py:126: 
> SetuptoolsDeprecationWarning: `build_py` command does not inherit from 
> setuptools' `build_py`.
> !!
> 
> 
> 
> Custom 'build_py' does not implement 
> 'get_data_files_without_manifest'.
> Please extend command classes from setuptools instead of distutils.
> 
> See https://peps.python.org/pep-0632/ for details.
> 
> 
> 
> !!
>   self._add_data_files(self._safe_data_files(build_py))
> mv: cannot stat 'debian/tmp/mpich/lib/python3.11/site-packages/adios_mpi': No 
> such file or directory
> make[1]: *** [debian/rules:154: override_dh_auto_install] Error 1


The full build log is available from:
http://qa-logs.debian.net/2023/10/27/adios_1.13.1-31_unstable.log

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

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

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

If you fail to reproduce this, please provide a build log and diff it with mine
so tha

Processed: Bug #1042654: forwarded to upstream commit that fixes Sphinx 7 compatibility

2023-11-04 Thread Debian Bug Tracking System 
Processing commands for cont...@bugs.debian.org:

> forwarded 1042654 https://github.com/python-babel/babel/pull/924
Bug #1042654 [src:python-babel] python-babel: FTBFS with Sphinx 7.1, docutils 
0.20: TypeError: not all arguments converted during string formatting
Set Bug forwarded-to-address to 
'https://github.com/python-babel/babel/pull/924'.
> thanks
Stopping processing here.

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

Processed: tagging 1008205, reassign 1055317 to src:llvm-toolchain-16

2023-11-04 Thread Debian Bug Tracking System 
Processing commands for cont...@bugs.debian.org:

> tags 1008205 + sid trixie
Bug #1008205 [src:gamin] RM: gamin -- RoQA; dead upstream
Added tag(s) sid and trixie.
> reassign 1055317 src:llvm-toolchain-16 1:16.0.6-17
Bug #1055317 [src:llvm-toolchain-16-16.0.6] Various problems in source build
Warning: Unknown package 'src:llvm-toolchain-16-16.0.6'
Bug reassigned from package 'src:llvm-toolchain-16-16.0.6' to 
'src:llvm-toolchain-16'.
No longer marked as found in versions llvm-toolchain-16-16.0.6/1:16.0.6-17.
Ignoring request to alter fixed versions of bug #1055317 to the same values 
previously set
Bug #1055317 [src:llvm-toolchain-16] Various problems in source build
Marked as found in versions llvm-toolchain-16/1:16.0.6-17.
> thanks
Stopping processing here.

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

Bug#1055328: node-minimatch: could not build using webpack

2023-11-04 Thread Bastien Roucariès 
Package: node-minimatch
Version: 9.0.3-4
Severity: serious
Justification: FTBFS other package

Dear Maintainer,

I could not build node-envinfo due to the trick done for default export only
for require. Webpack do a mix of two and do not find the import default...

Therefore it is required to export default for both

Bastien



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

Bug#1055319: marked as done (rust-rustls-webpki autopkgtest failure.)

2023-11-04 Thread Debian Bug Tracking System 
Your message dated Sat, 04 Nov 2023 08:24:30 +
with message-id 
and subject line Bug#1055319: fixed in rust-rustls-webpki 0.101.7-2
has caused the Debian Bug report #1055319,
regarding rust-rustls-webpki autopkgtest failure.
to be marked as done.

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

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


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

Package: rust-rustls-webpki
Version: 0.101.6-1
Severity: serious

The autopkgtest for rust-rustls-webpki fails with


238s error[E0583]: file not found for module `test_utils`
238s   --> src/lib.rs:65:1
238s|
238s 65 | pub(crate) mod test_utils;
238s| ^^
238s|
238s= help: to create the module `test_utils`, create file "src/test_utils.rs" or 
"src/test_utils/mod.rs"


This bug affects both the versions in unstable and experimental. It
does not affect the version currently in testing.

It appears that the file src/test_utils.rs is included in the source package
but is not making it into the binary package for some reason.
--- End Message ---
--- Begin Message ---
Source: rust-rustls-webpki
Source-Version: 0.101.7-2
Done: Jonas Smedegaard 

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

Debian distribution maintenance software
pp.
Jonas Smedegaard  (supplier of updated rust-rustls-webpki 
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, 04 Nov 2023 08:57:25 +0100
Source: rust-rustls-webpki
Architecture: source
Version: 0.101.7-2
Distribution: experimental
Urgency: medium
Maintainer: Jonas Smedegaard 
Changed-By: Jonas Smedegaard 
Closes: 1055319
Changes:
 rust-rustls-webpki (0.101.7-2) experimental; urgency=medium
 .
   * extend patch 1002 to install file src/test_utils.rs,
 and to reference Debian bugreport in DEP-3 headers;
 closes: bug#1055319, thanks to Peter Green
Checksums-Sha1:
 cc0bd7bb9d475680fc52d7824260152b75d5643e 2651 rust-rustls-webpki_0.101.7-2.dsc
 faf6bd70df00dbf2930c1dfe8661ade009593225 18228 
rust-rustls-webpki_0.101.7-2.debian.tar.xz
 195c9abf39c6f17d2635a034be8748f214c6eb52 13261 
rust-rustls-webpki_0.101.7-2_amd64.buildinfo
Checksums-Sha256:
 a0cdaabada6898f235ba58bcaef714dd67fc5dfb7fd0d76cd720d1db94a5011b 2651 
rust-rustls-webpki_0.101.7-2.dsc
 0b99d70253e09b95606c5225de7408d0b2405fe1ec6e6a700ecf5f56f41bc7e6 18228 
rust-rustls-webpki_0.101.7-2.debian.tar.xz
 c45075e0e8eef88a3510166e6aa2f6a2b8a9788ef6d93216fbb04934562e2690 13261 
rust-rustls-webpki_0.101.7-2_amd64.buildinfo
Files:
 c565d85f8f105fb8fb10f18f49c808f4 2651 rust optional 
rust-rustls-webpki_0.101.7-2.dsc
 4d216b7fd21a7c9995d246311dfc4e61 18228 rust optional 
rust-rustls-webpki_0.101.7-2.debian.tar.xz
 c6c2e6a67d7149fd81934b4f00aec039 13261 rust optional 
rust-rustls-webpki_0.101.7-2_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEn+Ppw2aRpp/1PMaELHwxRsGgASEFAmVF+68ACgkQLHwxRsGg
ASFezw/9GJHxQWQbec5e9p2G2N+X0cM9UKft5BR9N4xlPx8/GVsxaQCmDEdWt9LA
zqzFdpoh07h7O60jxqpB7FGuR5s54+jRGM5vsGRZQT78cE6rEvYC2zQXrMaRQrfv
hF2IZYz5BXww5UjMS0tMvR015klpph2Y8xxlfedICxVIAIAOQVG+85JGTyb8RwLa
+V+XlghZOH8iANSrVZ9iXBpeVxYijordVOai5/oAvd7//bozTlhSb2fkXe6UwQHO
zJYz3TezH3qfJIQ/NkMGHdmDQTXZRpHe2x2HBPbtmV1ZFlK0KW0aPlCKpqdmEfeh
AUDc0PtqrbQpdVy3fwDuGgEKUeggPEdyg5ZSx06J3I14jQQlJuDwG3G22JOgjvf0
DX2IKotwjAmvcipuGwWtulScqX4xd+yIGOfjNrDAo8943qgGFZBCrbSZ4zhyTgKK
AjuTNIAVFFk/aRwscZm/Jklyw0mZ4A/t/vjRouSYActZb7/y9wzbc3OfbkWSYcOY
QD14FaoV2HmLIkNw68hwcgYUghpwcUo6QyMkeqPJoWLUKCrF20navYRMxcIImUA3
yi/qmEgzBhIhjq28iQq1J7hMoxRLVvrr+2PXvJykAO7WuuLrnInGNt5rggO2qJZU
EKAQJtVYjaVLcTxv7BHtgrzNOL/9phsfWg+ppvNCnTt04vkISXk=
=9WP1
-END PGP SIGNATURE End Message ---

Bug#1042602: marked as done (sphinx-panels: FTBFS with Sphinx 7.1, docutils 0.20: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p 3.11 returned exit code 13)

2023-11-04 Thread Debian Bug Tracking System 
Your message dated Sat, 04 Nov 2023 08:24:47 +
with message-id 
and subject line Bug#1042602: fixed in sphinx-panels 0.6.0-3
has caused the Debian Bug report #1042602,
regarding sphinx-panels: FTBFS with Sphinx 7.1, docutils 0.20: dh_auto_test: 
error: pybuild --test --test-pytest -i python{version} -p 3.11 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.)


-- 
1042602: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1042602
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: sphinx-panels
Version: 0.6.0-2
Severity: important
Tags: ftbfs
User: python-modules-t...@lists.alioth.debian.org
Usertags: sphinx7.1

Hi,

sphinx-panels fails to build with Sphinx 7.1 and docutils 0.20, both of which
are currently available in experimental.

Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> dh_auto_build -i
> I: pybuild base:240: /usr/bin/python3 setup.py build 
> running build
> running build_py
> creating 
> /<>/.pybuild/cpython3_3.11_sphinx-panels/build/sphinx_panels
> copying sphinx_panels/utils.py -> 
> /<>/.pybuild/cpython3_3.11_sphinx-panels/build/sphinx_panels
> copying sphinx_panels/dropdown.py -> 
> /<>/.pybuild/cpython3_3.11_sphinx-panels/build/sphinx_panels
> copying sphinx_panels/icons.py -> 
> /<>/.pybuild/cpython3_3.11_sphinx-panels/build/sphinx_panels
> copying sphinx_panels/__init__.py -> 
> /<>/.pybuild/cpython3_3.11_sphinx-panels/build/sphinx_panels
> copying sphinx_panels/panels.py -> 
> /<>/.pybuild/cpython3_3.11_sphinx-panels/build/sphinx_panels
> copying sphinx_panels/tabs.py -> 
> /<>/.pybuild/cpython3_3.11_sphinx-panels/build/sphinx_panels
> copying sphinx_panels/button.py -> 
> /<>/.pybuild/cpython3_3.11_sphinx-panels/build/sphinx_panels
> creating 
> /<>/.pybuild/cpython3_3.11_sphinx-panels/build/sphinx_panels/_css
> copying sphinx_panels/_css/__init__.py -> 
> /<>/.pybuild/cpython3_3.11_sphinx-panels/build/sphinx_panels/_css
> running egg_info
> creating sphinx_panels.egg-info
> writing sphinx_panels.egg-info/PKG-INFO
> writing dependency_links to sphinx_panels.egg-info/dependency_links.txt
> writing requirements to sphinx_panels.egg-info/requires.txt
> writing top-level names to sphinx_panels.egg-info/top_level.txt
> writing manifest file 'sphinx_panels.egg-info/SOURCES.txt'
> reading manifest file 'sphinx_panels.egg-info/SOURCES.txt'
> reading manifest template 'MANIFEST.in'
> warning: no previously-included files found matching 'docs'
> warning: no previously-included files matching '*' found under directory 
> 'docs'
> warning: no previously-included files found matching 'tests'
> warning: no previously-included files found matching '.circleci'
> warning: no previously-included files matching '*' found under directory 
> '.circleci'
> warning: no previously-included files matching '__pycache__' found under 
> directory '**'
> warning: no previously-included files matching '*' found under directory 
> '**/__pycache__'
> warning: no previously-included files found matching '.pre-commit-config.yaml'
> warning: no previously-included files found matching '.readthedocs.yml'
> warning: no previously-included files found matching '.flake8'
> warning: no previously-included files found matching '.scss-lint.yml'
> warning: no previously-included files found matching 'tox.ini'
> warning: no previously-included files found matching 
> 'git_rebase_theme_branches.sh'
> adding license file 'LICENSE'
> writing manifest file 'sphinx_panels.egg-info/SOURCES.txt'
> /usr/lib/python3/dist-packages/setuptools/command/build_py.py:201: _Warning: 
> Package 'sphinx_panels.data' is absent from the `packages` configuration.
> !!
> 
> 
> 
> 
> # Package would be ignored #
> 
> Python recognizes 'sphinx_panels.data' as an importable package[^1],
> but it is absent from setuptools' `packages` configuration.
> 
> This leads to an ambiguous overall configuration. If you want to 
> distribute this
> package, please make sure that 'sphinx_panels.data' is explicitly 
> added
> to the `packages` configuration field.
> 
> Alternatively, you can also rely on setuptools' discovery methods
> (for example by using `find_namespace_packages(...)`/`find_namespace:`
> instead of `find_packages(...)`/`find:`).
> 
> You can read more about "package discovery" on setuptools 
> documentation page:
> 
> - 
> https://setuptools.pyp