Bug#955055: marked as done (python-simpy: FTBFS with Sphinx 2.4: KeyError: 'python')

[Debian Bug Tracking System]

Your message dated Mon, 20 Jun 2022 05:49:03 +
with message-id 
and subject line Bug#955055: fixed in python-simpy 2.3.1+dfsg-4
has caused the Debian Bug report #955055,
regarding python-simpy: FTBFS with Sphinx 2.4: KeyError: 'python'
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.)


-- 
955055: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=955055
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-simpy
Version: 2.3.1+dfsg-2
Severity: important
Tags: ftbfs
User: python-modules-t...@lists.alioth.debian.org
Usertags: sphinx2.4

Hi,

python-simpy fails to build with Sphinx 2.4, currently available in
experimental.

Relevant part (hopefully):
> make[2]: Entering directory '/<>/docs'
> sphinx-build -b html -d build/doctrees   source ./html
> Running Sphinx v2.4.3
> 
> Exception occurred:
>   File "/<>/docs/ext/annotate.py", line 76, in setup
> lexers['python'].add_filter(annotation_filter())
> KeyError: 'python'
> The full traceback has been saved in /tmp/sphinx-err-qp4vz4i3.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:41: html] Error 2

The full build log is available from:
   
http://qa-logs.debian.net/2020/03/26/python-simpy_2.3.1+dfsg-2_unstable_sphinx243.log

Please see [1] for Sphinx changelog, which may give a hint of what changes in
Sphinx caused this error.

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

Sphinx 2.4 is going to be uploaded to unstable in a couple of weeks. When that
happens, the severity of this bug will be bumped to serious.

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

[1]: https://www.sphinx-doc.org/en/2.0/changes.html
[2]: 
https://www.sphinx-doc.org/en/2.0/extdev/deprecated.html#dev-deprecated-apis

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!

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.
--- End Message ---
--- Begin Message ---
Source: python-simpy
Source-Version: 2.3.1+dfsg-4
Done: Sandro Tosi 

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

Debian distribution maintenance software
pp.
Sandro Tosi  (supplier of updated python-simpy 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, 20 Jun 2022 01:39:39 -0400
Source: python-simpy
Architecture: source
Version: 2.3.1+dfsg-4
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Team 
Changed-By: Sandro Tosi 
Closes: 955055
Changes:
 python-simpy (2.3.1+dfsg-4) unstable; urgency=medium
 .
   * debian/patches/doc-disable-annotate-extension.patch
 - disable extension which fails with recent Sphinx, also removed
   upstream in latest releases; Closes: #955055
Checksums-Sha1:
 9df6a97ab11c21848869a9b6fcc3d11f7a1f7ec2 2210 python-simpy_2.3.1+dfsg-4.dsc
 cdd82cf1ea3acdaea467da9f1b8ff8a2f140cdf8 5828 
python-simpy_2.3.1+dfsg-4.debian.tar.xz
 9ce37ca4f5b5670ae977f99265ef8bd7c390dcf2 8037 
python-simpy_2.3.1+dfsg-4_source.buildinfo
Checksums-Sha256:
 9684fe6389f751d0a97248188de45a08f0e5e5d194c78ca0c27f3bca0b17d511 2210 
python-simpy_2.3.1+dfsg-4.dsc
 e1d6a43995c90a3640b6d10526c65e3987b009256ba4cf3acfcc82f4915cffd8 5828 
python-simpy_2.3.1+dfsg-4.debian.tar.xz
 5e468c245893c652f644fc7d468067e6f8373ce1a49ea17de3e2606641f64a35 8037 
python-simpy_2.3.1+dfsg-4_source.buildinfo
Files:
 0dfff16954b974e5d39415ee7c55ddc3 2210 python optional 
python-simpy_2.3.1+dfsg-4.dsc
 516b3f22d97c572e8e78ada5b2900a33 5828 python optional 
python-simpy_2.3.1+dfsg-4.debian.tar.xz
 3be9a379a21f41b878916da7d084edc5 8037 python optional 

Bug#955055: marked as pending in python-simpy

[Sandro Tosi]

Control: tag -1 pending

Hello,

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

https://salsa.debian.org/python-team/packages/python-simpy/-/commit/6e274d4aefa29226045aed39bdaf3163f0c7e7aa


disable extension which fails with recent Sphinx, also removed upstream in 
latest releases; Closes: #955055


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/955055

Processed: Bug#955055 marked as pending in python-simpy

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #955055 [src:python-simpy] python-simpy: FTBFS with Sphinx 2.4: KeyError: 
'python'
Added tag(s) pending.

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

Bug#997645: marked as done (python-slimmer: FTBFS: error in slimmer setup command: use_2to3 is invalid.)

[Debian Bug Tracking System]

Your message dated Mon, 20 Jun 2022 05:33:52 +
with message-id 
and subject line Bug#997645: fixed in python-slimmer 0.1.30-9
has caused the Debian Bug report #997645,
regarding python-slimmer: FTBFS: error in slimmer setup command: use_2to3 is 
invalid.
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.)


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

Hi,

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


Relevant part (hopefully):
>  fakeroot debian/rules clean
> dh clean --with python3 --buildsystem pybuild
>dh_auto_clean -O--buildsystem=pybuild
> I: pybuild base:232: python3.9 setup.py clean 
> error in slimmer setup command: use_2to3 is invalid.
> E: pybuild pybuild:354: clean: plugin distutils failed with: exit code=1: 
> python3.9 setup.py clean 
> dh_auto_clean: error: pybuild --clean -i python{version} -p 3.9 returned exit 
> code 13
> make: *** [debian/rules:7: clean] Error 25


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

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

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

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

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

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

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

Debian distribution maintenance software
pp.
Sandro Tosi  (supplier of updated python-slimmer 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, 20 Jun 2022 01:17:10 -0400
Source: python-slimmer
Architecture: source
Version: 0.1.30-9
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Team 
Changed-By: Sandro Tosi 
Closes: 997645
Changes:
 python-slimmer (0.1.30-9) unstable; urgency=medium
 .
   [ Ondřej Nový ]
   * Bump Standards-Version to 4.4.1.
   * d/control: Update Maintainer field with new Debian Python Team
 contact address.
   * d/control: Update Vcs-* fields with new Debian Python Team Salsa
 layout.
 .
   [ Debian Janitor ]
   * Bump debhelper from old 12 to 13.
   * Update standards version to 4.5.1, no changes needed.
 .
   [ Sandro Tosi ]
   * debian/patches/python3-support.patch
 - run 2to3 by hand, instead at build time; Closes: #997645
Checksums-Sha1:
 27afd01eca0f7999b47983cc00d246afbc343fdc 2080 python-slimmer_0.1.30-9.dsc
 01fee75d9002bee60dcfa7df986387d22404dcc1 11172 
python-slimmer_0.1.30-9.debian.tar.xz
 71c1ef242456f2c0adfda011c0c981f04ef70394 6808 
python-slimmer_0.1.30-9_source.buildinfo
Checksums-Sha256:
 16a8aa42374eb63a2f40df3ff802a2b9e4d39ff9020882f6411802a2887f1c93 2080 
python-slimmer_0.1.30-9.dsc
 8536d7aeb8f72205703f134778d44bfc5a4e8e650aa6d96eb2c5e7cac45d28f7 11172 
python-slimmer_0.1.30-9.debian.tar.xz
 f3dd0c55252ab021331b0bed973d8310c18522fe397a51bdfdfd83315cbc076f 6808 
python-slimmer_0.1.30-9_source.buildinfo
Files:
 fe2dec14e3fffefe3e2d0b367604ef41 2080 python optional 
python-slimmer_0.1.30-9.dsc
 8c883e064b137609a8cb764e081e705e 11172 python optional 
python-slimmer_0.1.30-9.debian.tar.xz
 5f3fb4c32a4de1f3fc0ebe9a22dfbec7 6808 python optional 
python-slimmer_0.1.30-9_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEufrTGSrz5KUwnZ05h588mTgBqU8FAmKwAugACgkQh588mTgB
qU9PcRAA3Jjb/dg60Zafha/5LjfLfteIfo6hoQqHzPhj2XJgkgyiJdkhIkyFL0e5
ME7cOreHVgXFareMNRZUGgD0OMTHaAgPo/jV9fTqq2YgjXo8ZhhpKpvCtLwTLXBl
xx2w3MdHFVQeYiklGHpHUdSw+w0iXWrt9ZsWKkPWLM+BaaGWF3IXLOXl073FStx/

Bug#997645: marked as pending in python-slimmer

[Sandro Tosi]

Control: tag -1 pending

Hello,

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

https://salsa.debian.org/python-team/packages/python-slimmer/-/commit/285878e579f57b802f3df25968c2845d06e32bef


run 2to3 by hand, instead at build time; Closes: #997645


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/997645

Processed: Bug#997645 marked as pending in python-slimmer

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #997645 [src:python-slimmer] python-slimmer: FTBFS: error in slimmer setup 
command: use_2to3 is invalid.
Added tag(s) pending.

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

Bug#997633: marked as done (python-tempita: FTBFS: error in Tempita setup command: use_2to3 is invalid.)

[Debian Bug Tracking System]

Your message dated Mon, 20 Jun 2022 05:04:51 +
with message-id 
and subject line Bug#997633: fixed in python-tempita 0.5.2-7
has caused the Debian Bug report #997633,
regarding python-tempita: FTBFS: error in Tempita setup command: use_2to3 is 
invalid.
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.)


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

Hi,

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


Relevant part (hopefully):
>  fakeroot debian/rules clean
> dh clean --buildsystem=pybuild --with python3
>dh_auto_clean -O--buildsystem=pybuild
> I: pybuild base:232: python3.9 setup.py clean 
> error in Tempita setup command: use_2to3 is invalid.
> E: pybuild pybuild:354: clean: plugin distutils failed with: exit code=1: 
> python3.9 setup.py clean 
> dh_auto_clean: error: pybuild --clean --test-nose -i python{version} -p 3.9 
> returned exit code 13
> make: *** [debian/rules:6: clean] Error 25


The full build log is available from:
http://qa-logs.debian.net/2021/10/23/python-tempita_0.5.2-6_unstable.log

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

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

If you fail to reproduce this, please provide a build log and diff it with mine
so that we can identify if something relevant changed in the meantime.
--- End Message ---
--- Begin Message ---
Source: python-tempita
Source-Version: 0.5.2-7
Done: Sandro Tosi 

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

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

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

Debian distribution maintenance software
pp.
Sandro Tosi  (supplier of updated python-tempita 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, 20 Jun 2022 00:48:23 -0400
Source: python-tempita
Architecture: source
Version: 0.5.2-7
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Team 
Changed-By: Sandro Tosi 
Closes: 997633
Changes:
 python-tempita (0.5.2-7) unstable; urgency=medium
 .
   [ Ondřej Nový ]
   * d/control: Update Maintainer field with new Debian Python Team
 contact address.
   * d/control: Update Vcs-* fields with new Debian Python Team Salsa
 layout.
 .
   [ Debian Janitor ]
   * Update standards version to 4.5.0, no changes needed.
   * Bump debhelper from old 12 to 13.
   * Update standards version to 4.5.1, no changes needed.
 .
   [ Sandro Tosi ]
   * debian/patches/python3-support.patch
 - dont run 2to3 during build; Closes: #997633
Checksums-Sha1:
 d1d06b263aa10eaa2c68d9376b8944797fa9dd25 2039 python-tempita_0.5.2-7.dsc
 bf784f7f42abead6f2f359a7697709107d3e53a8 5788 
python-tempita_0.5.2-7.debian.tar.xz
 516b5416bae4d0cfcccdde1cc38fccf2f80aecab 6570 
python-tempita_0.5.2-7_source.buildinfo
Checksums-Sha256:
 3b42b7820d985da426eb3ae619ad29f8fa29bd26b80ef880d64386959797013c 2039 
python-tempita_0.5.2-7.dsc
 d39b5d60308a737f9172c1e3a9b54a10847f7ec0b0da049528feff3ae8fa4b69 5788 
python-tempita_0.5.2-7.debian.tar.xz
 5e3c6f71d7d4c41c9c493def2375bfb20ae20ddb7d65ba702c0dec0c998b984b 6570 
python-tempita_0.5.2-7_source.buildinfo
Files:
 4c31ffe84bb6d79affe3b89f3324acec 2039 python optional 
python-tempita_0.5.2-7.dsc
 7a137467522d0cec71abdf6965859688 5788 python optional 
python-tempita_0.5.2-7.debian.tar.xz
 ca6137b0f8b41b6231c4760fb1f040ec 6570 python optional 
python-tempita_0.5.2-7_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIyBAEBCAAdFiEEufrTGSrz5KUwnZ05h588mTgBqU8FAmKv/C0ACgkQh588mTgB
qU9O1w/2LUh7AJ3wNFLgqly75dBH9knB6Go1bWDKJ1a4VwawPdFxGYW4czC8mLBv
eTFU0CJNhLBW7TCblSkIj8LepnFOj8T6TdemmDlrSAs4fP7RRVTnIQw35HYSYyIn

Processed: Bug#997633 marked as pending in python-tempita

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #997633 [src:python-tempita] python-tempita: FTBFS: error in Tempita setup 
command: use_2to3 is invalid.
Added tag(s) pending.

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

Bug#997633: marked as pending in python-tempita

[Sandro Tosi]

Control: tag -1 pending

Hello,

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

https://salsa.debian.org/python-team/packages/python-tempita/-/commit/f7a7b352120ef69d63b20138bd44f2a0d569a123


dont run 2to3 during build; Closes: #997633


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/997633

Bug#1011889: marked as done (haskell-tldr: FTBFS: make: *** [/usr/share/cdbs/1/rules/debhelper.mk:252: binary-install/libghc-tldr-doc] Error 25)

[Debian Bug Tracking System]

Your message dated Sun, 19 Jun 2022 23:26:11 -0400 (EDT)
with message-id 
and subject line Fixed by haskell-devscripts 0.16.20
has caused the Debian Bug report #1011889,
regarding haskell-tldr: FTBFS: make: *** 
[/usr/share/cdbs/1/rules/debhelper.mk:252: binary-install/libghc-tldr-doc] 
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.)


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

Hi,

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


Relevant part (hopefully):
>  debian/rules binary
> test -x debian/rules
> dh_testroot
> dh_prep 
> dh_installdirs -A 
> mkdir -p "."
> CDBS WARNING:DEB_DH_STRIP_ARGS is deprecated since 0.4.85
> CDBS WARNING:DEB_COMPRESS_EXCLUDE is deprecated since 0.4.85
> Adding cdbs dependencies to debian/libghc-tldr-doc.substvars
> dh_installdirs -plibghc-tldr-doc \
>   
> perl -d:Confess -MDebian::Debhelper::Buildsystem::Haskell::Recipes=/.*/ \
>   -E 'make_setup_recipe'
> Running ghc --make Setup.hs -o debian/hlibrary.setup
> [1 of 1] Compiling Main ( Setup.hs, Setup.o )
> Linking debian/hlibrary.setup ...
> perl -d:Confess -MDebian::Debhelper::Buildsystem::Haskell::Recipes=/.*/ \
>   -E 'configure_recipe; haddock_recipe; build_recipe; check_recipe'
> Running find . ! -newer /tmp/uQrwkQAmnF -exec touch -d "1998-01-01 UTC" {} ;
> Running dh_listpackages
> libghc-tldr-dev
> libghc-tldr-prof
> libghc-tldr-doc
> tldr
> Running dh_listpackages
> libghc-tldr-dev
> libghc-tldr-prof
> libghc-tldr-doc
> tldr
> Running dpkg-buildflags --get LDFLAGS
> -Wl,-z,relro
> Running debian/hlibrary.setup configure --ghc -v2 
> --package-db=/var/lib/ghc/package.conf.d --prefix=/usr 
> --libdir=/usr/lib/haskell-packages/ghc/lib --libexecdir=/usr/lib 
> --builddir=dist-ghc --ghc-option=-optl-Wl,-z,relro 
> --haddockdir=/usr/lib/ghc-doc/haddock/tldr-0.6.4/ --datasubdir=tldr 
> --htmldir=/usr/share/doc/libghc-tldr-doc/html/ --enable-library-profiling
> Using Parsec parser
> Configuring tldr-0.6.4...
> Dependency ansi-terminal -any: using ansi-terminal-0.10.3
> Dependency base >=4.7 && <5: using base-4.13.0.0
> Dependency bytestring -any: using bytestring-0.10.10.1
> Dependency cmark -any: using cmark-0.6
> Dependency text -any: using text-1.2.4.0
> Dependency base -any: using base-4.13.0.0
> Dependency containers -any: using containers-0.6.2.1
> Dependency directory -any: using directory-1.3.6.0
> Dependency filepath -any: using filepath-1.4.2.1
> Dependency optparse-applicative -any: using optparse-applicative-0.15.1.0
> Dependency semigroups -any: using semigroups-0.19.1
> Dependency tldr -any: using tldr-0.6.4
> Dependency typed-process -any: using typed-process-0.2.6.0
> Source component graph:
> component lib
> component exe:tldr dependency lib
> Configured component graph:
> component tldr-0.6.4-AhmmP7VxCZp2l0XNdrEGdB
> include ansi-terminal-0.10.3-DS0jBrus2yKFjX9eUfmc3L
> include base-4.13.0.0
> include bytestring-0.10.10.1
> include cmark-0.6-60GhJwFkGY8112Jhy6cfyI
> include text-1.2.4.0
> component tldr-0.6.4-9kDqHmPjSlr7K1WcZsFaKh-tldr
> include base-4.13.0.0
> include containers-0.6.2.1
> include directory-1.3.6.0
> include filepath-1.4.2.1
> include optparse-applicative-0.15.1.0-GiY4uo4FBQRKuBqOktTXko
> include semigroups-0.19.1-LKdktuRRdRZ1yx9gBXzSbK
> include tldr-0.6.4-AhmmP7VxCZp2l0XNdrEGdB
> include typed-process-0.2.6.0-5au5NKOH3pCCyHyzwWiAiD
> Linked component graph:
> unit tldr-0.6.4-AhmmP7VxCZp2l0XNdrEGdB
> include ansi-terminal-0.10.3-DS0jBrus2yKFjX9eUfmc3L
> include base-4.13.0.0
> include bytestring-0.10.10.1
> include cmark-0.6-60GhJwFkGY8112Jhy6cfyI
> include text-1.2.4.0
> Tldr=tldr-0.6.4-AhmmP7VxCZp2l0XNdrEGdB:Tldr
> unit tldr-0.6.4-9kDqHmPjSlr7K1WcZsFaKh-tldr
> include base-4.13.0.0
> include containers-0.6.2.1
> include directory-1.3.6.0
> include filepath-1.4.2.1
> include optparse-applicative-0.15.1.0-GiY4uo4FBQRKuBqOktTXko
> include semigroups-0.19.1-LKdktuRRdRZ1yx9gBXzSbK
> include tldr-0.6.4-AhmmP7VxCZp2l0XNdrEGdB
> include typed-process-0.2.6.0-5au5NKOH3pCCyHyzwWiAiD
> Ready component graph:
> definite 

Bug#1011883: marked as done (haskell-wcwidth: FTBFS: make: *** [/usr/share/cdbs/1/class/hlibrary.mk:188: install/libghc-wcwidth-doc] Error 25)

[Debian Bug Tracking System]

Your message dated Sun, 19 Jun 2022 23:26:11 -0400 (EDT)
with message-id 
and subject line Fixed by haskell-devscripts 0.16.20
has caused the Debian Bug report #1011883,
regarding haskell-wcwidth: FTBFS: make: *** 
[/usr/share/cdbs/1/class/hlibrary.mk:188: install/libghc-wcwidth-doc] 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.)


-- 
1011883: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1011883
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: haskell-wcwidth
Version: 0.0.2-2
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20220525 ftbfs-bookworm

Hi,

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


Relevant part (hopefully):
>  fakeroot debian/rules binary
> test -x debian/rules
> dh_testroot
> dh_prep 
> dh_installdirs -A 
> mkdir -p "."
> CDBS WARNING:DEB_DH_STRIP_ARGS is deprecated since 0.4.85
> CDBS WARNING:DEB_COMPRESS_EXCLUDE is deprecated since 0.4.85
> Adding cdbs dependencies to debian/libghc-wcwidth-doc.substvars
> dh_installdirs -plibghc-wcwidth-doc \
>   
> perl -d:Confess -MDebian::Debhelper::Buildsystem::Haskell::Recipes=/.*/ \
>   -E 'make_setup_recipe'
> Running ghc --make Setup.hs -o debian/hlibrary.setup
> [1 of 1] Compiling Main ( Setup.hs, Setup.o )
> Linking debian/hlibrary.setup ...
> perl -d:Confess -MDebian::Debhelper::Buildsystem::Haskell::Recipes=/.*/ \
>   -E 'configure_recipe; haddock_recipe; build_recipe; check_recipe'
> Running find . ! -newer /tmp/uTagLh35uc -exec touch -d "1998-01-01 UTC" {} ;
> Running dh_listpackages
> libghc-wcwidth-dev
> libghc-wcwidth-prof
> libghc-wcwidth-doc
> Running dh_listpackages
> libghc-wcwidth-dev
> libghc-wcwidth-prof
> libghc-wcwidth-doc
> Running dpkg-buildflags --get LDFLAGS
> -Wl,-z,relro -Wl,-z,now
> Running debian/hlibrary.setup configure --ghc -v2 
> --package-db=/var/lib/ghc/package.conf.d --prefix=/usr 
> --libdir=/usr/lib/haskell-packages/ghc/lib --libexecdir=/usr/lib 
> --builddir=dist-ghc --ghc-option=-optl-Wl,-z,relro 
> --ghc-option=-optl-Wl,-z,now --haddockdir=/usr/lib/ghc-doc/haddock/wcwidth-/ 
> --datasubdir=wcwidth --htmldir=/usr/share/doc/libghc-wcwidth-doc/html/ 
> --enable-library-profiling
> Using Parsec parser
> Configuring wcwidth-0.0.2...
> Flags chosen: cli=False, split-base=True
> Dependency base ==4.*: using base-4.13.0.0
> Dependency containers -any: using containers-0.6.2.1
> Source component graph: component lib
> Configured component graph:
> component wcwidth-0.0.2-Dgss9EfJyRR4SDXGezAumY
> include base-4.13.0.0
> include containers-0.6.2.1
> Linked component graph:
> unit wcwidth-0.0.2-Dgss9EfJyRR4SDXGezAumY
> include base-4.13.0.0
> include containers-0.6.2.1
> 
> Data.Char.WCWidth=wcwidth-0.0.2-Dgss9EfJyRR4SDXGezAumY:Data.Char.WCWidth
> Ready component graph:
> definite wcwidth-0.0.2-Dgss9EfJyRR4SDXGezAumY
> depends base-4.13.0.0
> depends containers-0.6.2.1
> Using Cabal-3.0.1.0 compiled by ghc-8.8
> Using compiler: ghc-8.8.4
> Using install prefix: /usr
> Executables installed in: /usr/bin
> Libraries installed in:
> /usr/lib/haskell-packages/ghc/lib/x86_64-linux-ghc-8.8.4/wcwidth-0.0.2-Dgss9EfJyRR4SDXGezAumY
> Dynamic Libraries installed in:
> /usr/lib/haskell-packages/ghc/lib/x86_64-linux-ghc-8.8.4
> Private executables installed in:
> /usr/lib/x86_64-linux-ghc-8.8.4/wcwidth-0.0.2
> Data files installed in: /usr/share/wcwidth
> Documentation installed in:
> /usr/share/doc/x86_64-linux-ghc-8.8.4/wcwidth-0.0.2
> Configuration files installed in: /usr/etc
> No alex found
> Using ar found on system at: /usr/bin/x86_64-linux-gnu-ar
> No c2hs found
> No cpphs found
> No doctest found
> Using gcc version 11 found on system at: /usr/bin/x86_64-linux-gnu-gcc
> Using ghc version 8.8.4 found on system at: /usr/bin/ghc
> Using ghc-pkg version 8.8.4 found on system at: /usr/bin/ghc-pkg
> No ghcjs found
> No ghcjs-pkg found
> No greencard found
> Using haddock version 2.23.0 found on system at: /usr/bin/haddock
> No happy found
> Using haskell-suite found on system at: haskell-suite-dummy-location
> Using haskell-suite-pkg found on system at: haskell-suite-pkg-dummy-location
> No hmake found
> Using hpc version 0.67 found on system at: /usr/bin/hpc
> Using hsc2hs version 0.68.7 found on system at: /usr/bin/hsc2hs
> No hscolour found
> No jhc found
> Using ld found on system at: /usr/bin/x86_64-linux-gnu-ld.gold
> No pkg-config found
> Using runghc version 8.8.4 found on system at: 

Bug#1011866: marked as done (haskell-base-prelude: FTBFS: make: *** [/usr/share/cdbs/1/class/hlibrary.mk:188: install/libghc-base-prelude-doc] Error 25)

[Debian Bug Tracking System]

Your message dated Sun, 19 Jun 2022 23:26:11 -0400 (EDT)
with message-id 
and subject line Fixed by haskell-devscripts 0.16.20
has caused the Debian Bug report #1011866,
regarding haskell-base-prelude: FTBFS: make: *** 
[/usr/share/cdbs/1/class/hlibrary.mk:188: install/libghc-base-prelude-doc] 
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.)


-- 
1011866: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1011866
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: haskell-base-prelude
Version: 1.3-2
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20220525 ftbfs-bookworm

Hi,

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


Relevant part (hopefully):
>  debian/rules binary
> test -x debian/rules
> dh_testroot
> dh_prep 
> dh_installdirs -A 
> mkdir -p "."
> CDBS WARNING:DEB_DH_STRIP_ARGS is deprecated since 0.4.85
> CDBS WARNING:DEB_COMPRESS_EXCLUDE is deprecated since 0.4.85
> Adding cdbs dependencies to debian/libghc-base-prelude-doc.substvars
> dh_installdirs -plibghc-base-prelude-doc \
>   
> perl -d:Confess -MDebian::Debhelper::Buildsystem::Haskell::Recipes=/.*/ \
>   -E 'make_setup_recipe'
> Running ghc --make Setup.hs -o debian/hlibrary.setup
> [1 of 1] Compiling Main ( Setup.hs, Setup.o )
> Linking debian/hlibrary.setup ...
> perl -d:Confess -MDebian::Debhelper::Buildsystem::Haskell::Recipes=/.*/ \
>   -E 'configure_recipe; haddock_recipe; build_recipe; check_recipe'
> Running find . ! -newer /tmp/SrX_MK4R55 -exec touch -d "1998-01-01 UTC" {} ;
> Running dh_listpackages
> libghc-base-prelude-dev
> libghc-base-prelude-prof
> libghc-base-prelude-doc
> Running dh_listpackages
> libghc-base-prelude-dev
> libghc-base-prelude-prof
> libghc-base-prelude-doc
> Running dpkg-buildflags --get LDFLAGS
> -Wl,-z,relro
> Running debian/hlibrary.setup configure --ghc -v2 
> --package-db=/var/lib/ghc/package.conf.d --prefix=/usr 
> --libdir=/usr/lib/haskell-packages/ghc/lib --libexecdir=/usr/lib 
> --builddir=dist-ghc --ghc-option=-optl-Wl,-z,relro 
> --haddockdir=/usr/lib/ghc-doc/haddock/base-prelude-/ 
> --datasubdir=base-prelude 
> --htmldir=/usr/share/doc/libghc-base-prelude-doc/html/ 
> --enable-library-profiling
> Using Parsec parser
> Configuring base-prelude-1.3...
> Dependency base >=4.6 && <5: using base-4.13.0.0
> Source component graph: component lib
> Configured component graph:
> component base-prelude-1.3-GkjcM0d5Bef5VOhNpPY6Ft
> include base-4.13.0.0
> Linked component graph:
> unit base-prelude-1.3-GkjcM0d5Bef5VOhNpPY6Ft
> include base-4.13.0.0
> BasePrelude=base-prelude-1.3-GkjcM0d5Bef5VOhNpPY6Ft:BasePrelude
> Ready component graph:
> definite base-prelude-1.3-GkjcM0d5Bef5VOhNpPY6Ft
> depends base-4.13.0.0
> Using Cabal-3.0.1.0 compiled by ghc-8.8
> Using compiler: ghc-8.8.4
> Using install prefix: /usr
> Executables installed in: /usr/bin
> Libraries installed in:
> /usr/lib/haskell-packages/ghc/lib/x86_64-linux-ghc-8.8.4/base-prelude-1.3-GkjcM0d5Bef5VOhNpPY6Ft
> Dynamic Libraries installed in:
> /usr/lib/haskell-packages/ghc/lib/x86_64-linux-ghc-8.8.4
> Private executables installed in:
> /usr/lib/x86_64-linux-ghc-8.8.4/base-prelude-1.3
> Data files installed in: /usr/share/base-prelude
> Documentation installed in:
> /usr/share/doc/x86_64-linux-ghc-8.8.4/base-prelude-1.3
> Configuration files installed in: /usr/etc
> No alex found
> Using ar found on system at: /usr/bin/x86_64-linux-gnu-ar
> No c2hs found
> No cpphs found
> No doctest found
> Using gcc version 11 found on system at: /usr/bin/x86_64-linux-gnu-gcc
> Using ghc version 8.8.4 found on system at: /usr/bin/ghc
> Using ghc-pkg version 8.8.4 found on system at: /usr/bin/ghc-pkg
> No ghcjs found
> No ghcjs-pkg found
> No greencard found
> Using haddock version 2.23.0 found on system at: /usr/bin/haddock
> No happy found
> Using haskell-suite found on system at: haskell-suite-dummy-location
> Using haskell-suite-pkg found on system at: haskell-suite-pkg-dummy-location
> No hmake found
> Using hpc version 0.67 found on system at: /usr/bin/hpc
> Using hsc2hs version 0.68.7 found on system at: /usr/bin/hsc2hs
> No hscolour found
> No jhc found
> Using ld found on system at: /usr/bin/x86_64-linux-gnu-ld.gold
> No pkg-config found
> Using runghc version 8.8.4 found on system at: /usr/bin/runghc
> Using strip version 2.38 found on system at: /usr/bin/strip
> Using tar found on system at: /bin/tar
> No uhc found
> Running dh_listpackages
> 

Bug#1011831: marked as done (haskell-vector-builder: FTBFS: make: *** [/usr/share/cdbs/1/class/hlibrary.mk:188: install/libghc-vector-builder-doc] Error 25)

[Debian Bug Tracking System]

Your message dated Sun, 19 Jun 2022 23:26:11 -0400 (EDT)
with message-id 
and subject line Fixed by haskell-devscripts 0.16.20
has caused the Debian Bug report #1011831,
regarding haskell-vector-builder: FTBFS: make: *** 
[/usr/share/cdbs/1/class/hlibrary.mk:188: install/libghc-vector-builder-doc] 
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.)


-- 
1011831: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1011831
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: haskell-vector-builder
Version: 0.3.8-1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20220525 ftbfs-bookworm

Hi,

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


Relevant part (hopefully):
>  debian/rules binary
> test -x debian/rules
> dh_testroot
> dh_prep 
> dh_installdirs -A 
> mkdir -p "."
> CDBS WARNING:DEB_DH_STRIP_ARGS is deprecated since 0.4.85
> CDBS WARNING:DEB_COMPRESS_EXCLUDE is deprecated since 0.4.85
> Adding cdbs dependencies to debian/libghc-vector-builder-doc.substvars
> dh_installdirs -plibghc-vector-builder-doc \
>   
> perl -d:Confess -MDebian::Debhelper::Buildsystem::Haskell::Recipes=/.*/ \
>   -E 'make_setup_recipe'
> Running ghc --make Setup.hs -o debian/hlibrary.setup
> [1 of 1] Compiling Main ( Setup.hs, Setup.o )
> Linking debian/hlibrary.setup ...
> perl -d:Confess -MDebian::Debhelper::Buildsystem::Haskell::Recipes=/.*/ \
>   -E 'configure_recipe; haddock_recipe; build_recipe; check_recipe'
> Running find . ! -newer /tmp/PWOTXA6sj3 -exec touch -d "1998-01-01 UTC" {} ;
> Running dh_listpackages
> libghc-vector-builder-dev
> libghc-vector-builder-prof
> libghc-vector-builder-doc
> Running dh_listpackages
> libghc-vector-builder-dev
> libghc-vector-builder-prof
> libghc-vector-builder-doc
> Running dpkg-buildflags --get LDFLAGS
> -Wl,-z,relro
> Running debian/hlibrary.setup configure --ghc -v2 
> --package-db=/var/lib/ghc/package.conf.d --prefix=/usr 
> --libdir=/usr/lib/haskell-packages/ghc/lib --libexecdir=/usr/lib 
> --builddir=dist-ghc --ghc-option=-optl-Wl,-z,relro 
> --haddockdir=/usr/lib/ghc-doc/haddock/vector-builder-/ 
> --datasubdir=vector-builder 
> --htmldir=/usr/share/doc/libghc-vector-builder-doc/html/ 
> --enable-library-profiling
> Using Parsec parser
> Configuring vector-builder-0.3.8...
> Dependency base >=4.8 && <5: using base-4.13.0.0
> Dependency base-prelude <2: using base-prelude-1.3
> Dependency semigroups >=0.16 && <0.20: using semigroups-0.19.1
> Dependency vector >=0.11 && <0.13: using vector-0.12.1.2
> Source component graph: component lib
> Configured component graph:
> component vector-builder-0.3.8-LSLd1ywetcg3orYj01Ibtm
> include base-4.13.0.0
> include base-prelude-1.3-GkjcM0d5Bef5VOhNpPY6Ft
> include semigroups-0.19.1-LKdktuRRdRZ1yx9gBXzSbK
> include vector-0.12.1.2-C2W44iPdAFeHo4yLU081Gd
> Linked component graph:
> unit vector-builder-0.3.8-LSLd1ywetcg3orYj01Ibtm
> include base-4.13.0.0
> include base-prelude-1.3-GkjcM0d5Bef5VOhNpPY6Ft
> include semigroups-0.19.1-LKdktuRRdRZ1yx9gBXzSbK
> include vector-0.12.1.2-C2W44iPdAFeHo4yLU081Gd
> 
> VectorBuilder.Alternative=vector-builder-0.3.8-LSLd1ywetcg3orYj01Ibtm:VectorBuilder.Alternative,VectorBuilder.Builder=vector-builder-0.3.8-LSLd1ywetcg3orYj01Ibtm:VectorBuilder.Builder,VectorBuilder.MVector=vector-builder-0.3.8-LSLd1ywetcg3orYj01Ibtm:VectorBuilder.MVector,VectorBuilder.MonadPlus=vector-builder-0.3.8-LSLd1ywetcg3orYj01Ibtm:VectorBuilder.MonadPlus,VectorBuilder.Vector=vector-builder-0.3.8-LSLd1ywetcg3orYj01Ibtm:VectorBuilder.Vector
> Ready component graph:
> definite vector-builder-0.3.8-LSLd1ywetcg3orYj01Ibtm
> depends base-4.13.0.0
> depends base-prelude-1.3-GkjcM0d5Bef5VOhNpPY6Ft
> depends semigroups-0.19.1-LKdktuRRdRZ1yx9gBXzSbK
> depends vector-0.12.1.2-C2W44iPdAFeHo4yLU081Gd
> Using Cabal-3.0.1.0 compiled by ghc-8.8
> Using compiler: ghc-8.8.4
> Using install prefix: /usr
> Executables installed in: /usr/bin
> Libraries installed in:
> /usr/lib/haskell-packages/ghc/lib/x86_64-linux-ghc-8.8.4/vector-builder-0.3.8-LSLd1ywetcg3orYj01Ibtm
> Dynamic Libraries installed in:
> /usr/lib/haskell-packages/ghc/lib/x86_64-linux-ghc-8.8.4
> Private executables installed in:
> /usr/lib/x86_64-linux-ghc-8.8.4/vector-builder-0.3.8
> Data files installed in: /usr/share/vector-builder
> Documentation installed in:
> /usr/share/doc/x86_64-linux-ghc-8.8.4/vector-builder-0.3.8
> 

Bug#1011782: marked as done (haskell-patience: FTBFS: make: *** [/usr/share/cdbs/1/class/hlibrary.mk:188: install/libghc-patience-doc] Error 25)

[Debian Bug Tracking System]

Your message dated Sun, 19 Jun 2022 23:26:11 -0400 (EDT)
with message-id 
and subject line Fixed by haskell-devscripts 0.16.20
has caused the Debian Bug report #1011782,
regarding haskell-patience: FTBFS: make: *** 
[/usr/share/cdbs/1/class/hlibrary.mk:188: install/libghc-patience-doc] 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.)


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

Hi,

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


Relevant part (hopefully):
>  debian/rules binary
> test -x debian/rules
> dh_testroot
> dh_prep 
> dh_installdirs -A 
> mkdir -p "."
> CDBS WARNING:DEB_DH_STRIP_ARGS is deprecated since 0.4.85
> CDBS WARNING:DEB_COMPRESS_EXCLUDE is deprecated since 0.4.85
> Adding cdbs dependencies to debian/libghc-patience-doc.substvars
> dh_installdirs -plibghc-patience-doc \
>   
> perl -d:Confess -MDebian::Debhelper::Buildsystem::Haskell::Recipes=/.*/ \
>   -E 'make_setup_recipe'
> Running ghc --make Setup.hs -o debian/hlibrary.setup
> [1 of 1] Compiling Main ( Setup.hs, Setup.o )
> Linking debian/hlibrary.setup ...
> perl -d:Confess -MDebian::Debhelper::Buildsystem::Haskell::Recipes=/.*/ \
>   -E 'configure_recipe; haddock_recipe; build_recipe; check_recipe'
> Running find . ! -newer /tmp/yrPo35JbUl -exec touch -d "1998-01-01 UTC" {} ;
> Running dh_listpackages
> libghc-patience-dev
> libghc-patience-prof
> libghc-patience-doc
> Running dh_listpackages
> libghc-patience-dev
> libghc-patience-prof
> libghc-patience-doc
> Running dpkg-buildflags --get LDFLAGS
> -Wl,-z,relro
> Running debian/hlibrary.setup configure --ghc -v2 
> --package-db=/var/lib/ghc/package.conf.d --prefix=/usr 
> --libdir=/usr/lib/haskell-packages/ghc/lib --libexecdir=/usr/lib 
> --builddir=dist-ghc --ghc-option=-optl-Wl,-z,relro 
> --haddockdir=/usr/lib/ghc-doc/haddock/patience-/ --datasubdir=patience 
> --htmldir=/usr/share/doc/libghc-patience-doc/html/ --enable-library-profiling
> Using Parsec parser
> Configuring patience-0.3...
> Dependency base >=4.3 && <5: using base-4.13.0.0
> Dependency containers >=0.5.9 && <0.7: using containers-0.6.2.1
> Source component graph: component lib
> Configured component graph:
> component patience-0.3-I62H27wz80L2IOqnO6Lhfl
> include base-4.13.0.0
> include containers-0.6.2.1
> Linked component graph:
> unit patience-0.3-I62H27wz80L2IOqnO6Lhfl
> include base-4.13.0.0
> include containers-0.6.2.1
> 
> Patience=patience-0.3-I62H27wz80L2IOqnO6Lhfl:Patience,Patience.Map=patience-0.3-I62H27wz80L2IOqnO6Lhfl:Patience.Map
> Ready component graph:
> definite patience-0.3-I62H27wz80L2IOqnO6Lhfl
> depends base-4.13.0.0
> depends containers-0.6.2.1
> Using Cabal-3.0.1.0 compiled by ghc-8.8
> Using compiler: ghc-8.8.4
> Using install prefix: /usr
> Executables installed in: /usr/bin
> Libraries installed in:
> /usr/lib/haskell-packages/ghc/lib/x86_64-linux-ghc-8.8.4/patience-0.3-I62H27wz80L2IOqnO6Lhfl
> Dynamic Libraries installed in:
> /usr/lib/haskell-packages/ghc/lib/x86_64-linux-ghc-8.8.4
> Private executables installed in: /usr/lib/x86_64-linux-ghc-8.8.4/patience-0.3
> Data files installed in: /usr/share/patience
> Documentation installed in: /usr/share/doc/x86_64-linux-ghc-8.8.4/patience-0.3
> Configuration files installed in: /usr/etc
> No alex found
> Using ar found on system at: /usr/bin/x86_64-linux-gnu-ar
> No c2hs found
> No cpphs found
> No doctest found
> Using gcc version 11 found on system at: /usr/bin/x86_64-linux-gnu-gcc
> Using ghc version 8.8.4 found on system at: /usr/bin/ghc
> Using ghc-pkg version 8.8.4 found on system at: /usr/bin/ghc-pkg
> No ghcjs found
> No ghcjs-pkg found
> No greencard found
> Using haddock version 2.23.0 found on system at: /usr/bin/haddock
> No happy found
> Using haskell-suite found on system at: haskell-suite-dummy-location
> Using haskell-suite-pkg found on system at: haskell-suite-pkg-dummy-location
> No hmake found
> Using hpc version 0.67 found on system at: /usr/bin/hpc
> Using hsc2hs version 0.68.7 found on system at: /usr/bin/hsc2hs
> Using hscolour version 1.24 found on system at: /usr/bin/HsColour
> No jhc found
> Using ld found on system at: /usr/bin/x86_64-linux-gnu-ld.gold
> No pkg-config found
> Using runghc version 8.8.4 found on system 

Bug#1003353: marked as pending in lintian

[Axel Beckert]

Control: tag -1 pending

Hello,

Bug #1003353 in lintian 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/lintian/lintian/-/commit/91b36bc14ea6d011b4107bb21b2a80c18aa0586f


Replace unfitting Text::Glob with more flexible Regexp::Wildcards

Write a match_glob() function which emulates Text::Glob's match_glob()
preconfigured for Lintian's needs, put it into Lintian::Utils and
allow to export it from there.

The mentioned preconfiguration for just using the "Jokers" set of
Regexp::Wildcards fixes the issues with brackets in overrides which
Lintian had since the introduction of Text::Glob in commit
139009d5a54225ebff4509ec37b979cb898c17fe.

Closes: #1003353

This also allows us to remove one item from the exception list for
Perl::Critic's Variables::ProhibitPackageVars policy as we no more
need to configure Text::Glob every time (!) when we call match_glob().

Also update the dependencies accordingly.


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1003353

Processed: Bug#1003353 marked as pending in lintian

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1003353 [lintian] lintian: Cannot use brackets in suppression rules?
Ignoring request to alter tags of bug #1003353 to the same tags previously set

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

Bug#1013248: libseat-dev: Missing libseat-dev dependency on libsystemd-dev via pkg-config

[Braiam Peguero]

Package: libseat-dev
Version: 0.7.0-4
Severity: grave
Justification: renders package unusable

Dear Maintainer,

Using pkg-config to find headers fails for libseat-dev with
the following output:

$ /usr/bin/pkg-config --cflags libseat
Package libsystemd was not found in the pkg-config search path.
Perhaps you should add the directory containing `libsystemd.pc'
to the PKG_CONFIG_PATH environment variable
Package 'libsystemd', required by 'libseat', not found

pkgconfig/libseat.pc includes dependency on libsystemd:

$ cat /usr/lib/x86_64-linux-gnu/pkgconfig/libseat.pc
prefix=/usr
includedir=${prefix}/include
libdir=${prefix}/lib/x86_64-linux-gnu

have_seatd=true
have_logind=true
have_builtin=true

Name: libseat
Description: Seat management library
Version: 0.7.0
Requires.private: libsystemd
Libs: -L${libdir} -lseat
Libs.private: -lrt
Cflags: -I${includedir}

Please include libsystemd-dev as a dependency of libseat-dev.

Also, if I'm not mistaken, seatd is trying not to have hard
dependencies on systemd, but couldn't find from where
the .pc file is generated.


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

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

Versions of packages libseat-dev depends on:
ii  libseat1  0.7.0-4

libseat-dev recommends no packages.

libseat-dev suggests no packages.

-- no debconf information

Bug#1003353: lintian: Cannot use brackets in suppression rules?

[Axel Beckert]

Control: tag -1 + pending patch

Hi Samuel,

Samuel Thibault wrote:
> Seeing that qa.debian.org is using version 2.114.123 of lintian, I
> upgraded my lintian from its git tree, only to find that it seems I
> cannot update my suppression rule according to the new output:
> 
> W: libbrlapi-dev: bad-whatis-entry 
> [usr/share/man/man3/brlapi_authClientPacket_t.3.gz]
> W: libbrlapi-dev: mismatched-override bad-whatis-entry 
> [usr/share/man/man3/brlapi_*] [usr/share/lintian/overrides/libbrlapi-dev:2]
> 
> I did have updated this rule to include brackets:
> 
> bad-whatis-entry [usr/share/man/man3/brlapi_*]
> 
> but that doesn't seem to be working. I also tried to use escaping (which
> had fixed things for the ${} case), but to no avail:
> 
> bad-whatis-entry \[usr/share/man/man3/brlapi_*\]

Using * or ? in place of the brackets probably would have worked.

Cause was the switch of was this commit from 6 months ago:

commit 139009d5a54225ebff4509ec37b979cb898c17fe
Author: Felix Lechner 
Date:   Wed Dec 1 21:46:24 2021 -0800

Use Text::Glob to match hint contexts with override patterns.

Replaces a trusted homegrown routine.

Gbp-Dch: ignore

I neither understand why you would replace something "trusted" and
additionally not even plan to mention such a invasive commit in the
changelog.

And because Text::Glob also interprets brackets (and curly braces) and
you can't disable that, such issues were just waiting to happen.

And together with the brackets using "pointed hints" concept
introduced at around the same time, this caused really havoc.

> Lintian has recently been annoying enough that I'm unsure I'd continue
> monitoring its output any more.

*nod* JFYI, in case you didn't notice it (it happend months after your
bug report), but there was an "O: lintian" WNPP bug report in the
meantime: https://bugs.debian.org/1012289

So I'm now trying to clean up the shattered remains which the previous
(recent) Lintian maintainer(s) left behind.

For now I'm trying to get a current lintian version back into Testing,
i.e. I'm concentrating on RC and important bugs as well as bugs which
are annoying and easy to fix, e.g. those with a patch or MR.

At least the lintian internal test suite is no more failing. Although
it likely has some false negatives as it seems that the test suite is
no more able to run more than one check in one test. And running a
test against multiple checks at the same time seems critical to write
tests for issues like this one. Meh.

Anyway, my feature branch for this bug report is
https://salsa.debian.org/lintian/lintian/-/commits/brackets-in-overrides-rc-bug-1003353
but I will likely force-push that branch some more times, so the
commit message in
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1003353#50 might
become stale soon while I refine the commit before that (which
contains a test for this bug), but the patch will likely stay valid.
You also might get further such mails when I force-push new histories
in that feature branch. I hope you don't mind, but I wanted to publish
what I already have.

Regards, Axel
-- 
 ,''`.  |  Axel Beckert , https://people.debian.org/~abe/
: :' :  |  Debian Developer, ftp.ch.debian.org Admin
`. `'   |  4096R: 2517 B724 C5F6 CA99 5329  6E61 2FF9 CD59 6126 16B5
  `-|  1024D: F067 EA27 26B9 C3FC 1486  202E C09E 1D89 9593 0EDE


signature.asc
Description: PGP signature

Processed: Re: Bug#1003353: lintian: Cannot use brackets in suppression rules?

[Debian Bug Tracking System]

Processing control commands:

> tag -1 + pending patch
Bug #1003353 [lintian] lintian: Cannot use brackets in suppression rules?
Added tag(s) patch.

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

Bug#984914: marked as done (rust-combine: depends on multiple unavailable packages)

[Debian Bug Tracking System]

Your message dated Sun, 19 Jun 2022 23:50:42 +
with message-id 
and subject line Bug#984914: fixed in rust-combine 4.6.4-1
has caused the Debian Bug report #984914,
regarding rust-combine: depends on multiple unavailable packages
to be marked as done.

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

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


-- 
984914: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=984914
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: rust-combine
Version: 3.8.1-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Control: affects -1 + librust-combine+combine-regex-1-dev 
librust-combine+doc-dev librust-combine+regex-dev 

Hi,

the binary packages built from src:rust-combine depend on several no
longer available packages, e.g.

  The following packages have unmet dependencies:
   librust-combine+combine-regex-1-dev : Depends: 
librust-combine-regex-1-1+default-dev but it is not installable


Andreas
--- End Message ---
--- Begin Message ---
Source: rust-combine
Source-Version: 4.6.4-1
Done: Peter Michael Green 

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

Debian distribution maintenance software
pp.
Peter Michael Green  (supplier of updated rust-combine 
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, 19 Jun 2022 15:56:36 +
Source: rust-combine
Architecture: source
Version: 4.6.4-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Rust Maintainers 

Changed-By: Peter Michael Green 
Closes: 984914 1013103
Changes:
 rust-combine (4.6.4-1) unstable; urgency=medium
 .
   * Team upload.
   * Package combine 4.6.4 from crates.io using debcargo 2.5.0 (Closes: 
#1013103, #984914)
   * Remove features providing support for old versions of futures and tokio
 which are not in Debian (features for current versions of futures/tokio
 are retained).
   * Eliminate dev-dependencies on packages that are not in Debian.
   * Bump versions of dev-dependencies to match versions in Debian.
   * Disable bench that dpeneds on a file that is not present.
   * set collapse_features = true
Checksums-Sha1:
 ad3cbe9be030d786de30df5107fe098c8589b610 2609 rust-combine_4.6.4-1.dsc
 f7a3b30685a4a0dc7b19570d798de1edbe096e93 132144 rust-combine_4.6.4.orig.tar.gz
 e7a10cc944011ff628b39cf2d4ed1f9cc4faf67d 4528 
rust-combine_4.6.4-1.debian.tar.xz
 b71d2b698aeff9d03c98d829de34728c00629b3e 7465 
rust-combine_4.6.4-1_source.buildinfo
Checksums-Sha256:
 1c957d85ed111f8ea10a7118e322ea5bfadc265d1edb520edc6ee9ab16f8a103 2609 
rust-combine_4.6.4-1.dsc
 2a604e93b79d1808327a6fca85a6f2d69de66461e7620f5a4cbf5fb4d1d7c948 132144 
rust-combine_4.6.4.orig.tar.gz
 00e8efc85aa9ab5d7a432e5015dec4eb124b7650b471ca84f38a3fcb7021c78c 4528 
rust-combine_4.6.4-1.debian.tar.xz
 4ad1bbaec65c24ab90941f012602b026d196cf14d2894b231f6b8183b5571fab 7465 
rust-combine_4.6.4-1_source.buildinfo
Files:
 f49fbc3dba333b99a81051503774b020 2609 rust optional rust-combine_4.6.4-1.dsc
 c9b3ce98c641a58e41c5284c8b5d110e 132144 rust optional 
rust-combine_4.6.4.orig.tar.gz
 88e328482fc7bc068c0c9741695bd568 4528 rust optional 
rust-combine_4.6.4-1.debian.tar.xz
 60baef7826a10ce997eba888734351e1 7465 rust optional 
rust-combine_4.6.4-1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJIBAEBCAAyFiEEU0DQATYMplbjSX63DEjqKnqP/XsFAmKvsx4UHHBsdWd3YXNo
QGRlYmlhbi5vcmcACgkQDEjqKnqP/XvXgxAAi27r3hr/P8EYmMCZtP1XL6E2bykb
lAg/GFvuGSqO17uneM1cultnx1tZJEdCWQ0CVvjjfv3CHLdZt0MIfAhCh1oupUl6
VJrVXYXi0oO6txid5iPXN5ytjcEQeIJP/kvvlMCOw0D2efbD3dZfc1Ejob0anK0t
6QP9GjmmbNPzaCBWJPutxD3elCV1BnI4f0+k7K6iKs8KwoyyRB8ToZJ2TrNkbbDk
cR0R0CnmajgfxFDs3KACnxJs4Tmjsh3EOG8of1yckxUzw1+VwAO58iKODjKvnvGo
G9RLDFbs/u/mUJ3LW1Mijps32qK0CZXBVS/SQcB/UMiq2dnR7z/BQmTWj2Vt+STL
SL6w4VMJEVoN5bLb29OIRU4jx0/9HGIK+eD3AOjpJtYkHRGao3nrR6mEwizLIOER
tlrb3A2F3Q31GupU8KpKih8Heg37BUaRZL+n0HXZHIOAamoTWFAvXe0Q/Nov9bzh
cOuESjhGdOoH2vM0s/6w9hQUBYkZ68ji+BBsnwlDYMv7HclSS8AW2MW0P2Kmjv6C
XxqC4gKgVwZ4em+FXqwF49WDWSHjIrEY/buxZ9pwMoXkrX4sxKnJz9u/ksNMVujU
ynt5JOmwgj8PerKux3dUL+i+w3ApejneyIpmCDuM68nsg99rq30TjPH5/dB4MGyZ
aUJ4BQ8i/AUheMI=
=qYme

Bug#1003353: marked as pending in lintian

[Axel Beckert]

Control: tag -1 pending

Hello,

Bug #1003353 in lintian 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/lintian/lintian/-/commit/f258329316d2882f9acee2eb32f0f9f4a24bd197


Replace unfitting Text::Glob with more flexible Regexp::Wildcards

Write a match_glob() function which emulates Text::Glob's match_glob()
preconfigured for Lintian's needs, put it into Lintian::Utils and
allow to export it from there.

The mentioned preconfiguration for just using the "Jokers" set of
Regexp::Wildcards fixes the issues with brackets in overrides which
Lintian had since the introduction of Text::Glob in commit
139009d5a54225ebff4509ec37b979cb898c17fe.

Closes: #1003353

This also allows us to remove one item from the exception list for
Perl::Critic's Variables::ProhibitPackageVars policy as we no more
need to configure Text::Glob every time (!) when we call match_glob().

Also update the dependencies accordingly.


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1003353

Processed: Bug#1003353 marked as pending in lintian

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1003353 [lintian] lintian: Cannot use brackets in suppression rules?
Added tag(s) pending.

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

Bug#1011909: shellcheck: FTBFS: dpkg-buildpackage: error: debian/rules binary subprocess returned exit status 2

[Samuel Henrique]

The build is now failing with another error, but both FTBFS are not
caused by shellcheck, and can't be fixed by it.

There's something weird going on with haskell packages, I believe the
error will eventually be solved in the next few weeks, let's see...

Regards,

-- 
Samuel Henrique 

Bug#1012600: [Pkg-zfsonlinux-devel] Bug#1012600:

[Richard Laager]

I think this is because it Depends: a kernel << 5.18 and not 
Conflicts/Breaks a kernel >= 5.18. Since you can install multiple kernel 
packages, your existing kernel package is satisfying the dependency.


--
Richard


OpenPGP_signature
Description: OpenPGP digital signature

Bug#966780: marked as done (python-passfd: Unversioned Python removal in sid/bullseye)

[Debian Bug Tracking System]

Your message dated Sun, 19 Jun 2022 19:33:38 +
with message-id 
and subject line Bug#1009280: Removed package(s) from unstable
has caused the Debian Bug report #938001,
regarding python-passfd: Unversioned Python removal in sid/bullseye
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.)


-- 
938001: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=938001
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:python-passfd
Version: 0.2-3
Severity: serious
Tags: sid bullseye
User: debian-pyt...@lists.debian.org
Usertags: py2unversioned

Python2 becomes end-of-live upstream, and Debian aims to remove
Python2 from the distribution, as discussed in
https://lists.debian.org/debian-python/2019/07/msg00080.html

We will keep some Python2 package as discussed in
https://lists.debian.org/debian-python/2020/07/msg00039.html
but removing the unversioned python packages python-minimal, python,
python-dev, python-dbg, python-doc.

Your package either build-depends, depends on one of those packages.
Please either convert these packages to Python3, or if that is not
possible, replaces the dependencies on the unversioned Python
packages with one of the python2 dependencies (python2, python2-dev,
python2-dbg, python2-doc).

Please check for dependencies, build dependencies AND autopkg tests.

If there are questions, please refer to the wiki page for the removal:
https://wiki.debian.org/Python/2Removal, or ask for help on IRC
#debian-python, or the debian-pyt...@lists.debian.org mailing list.
--- End Message ---
--- Begin Message ---
Version: 0.2-3+rm

Dear submitter,

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

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

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

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

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

Debian distribution maintenance software
pp.
Thorsten Alteholz (the ftpmaster behind the curtain)--- End Message ---

Bug#938001: marked as done (python-passfd: Python2 removal in sid/bullseye)

[Debian Bug Tracking System]

Your message dated Sun, 19 Jun 2022 19:33:38 +
with message-id 
and subject line Bug#1009280: Removed package(s) from unstable
has caused the Debian Bug report #938001,
regarding python-passfd: Python2 removal in sid/bullseye
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.)


-- 
938001: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=938001
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:python-passfd
Version: 0.2-3
Severity: normal
Tags: sid bullseye
User: debian-pyt...@lists.debian.org
Usertags: py2removal

Python2 becomes end-of-live upstream, and Debian aims to remove
Python2 from the distribution, as discussed in
https://lists.debian.org/debian-python/2019/07/msg00080.html

Your package either build-depends, depends on Python2, or uses Python2
in the autopkg tests.  Please stop using Python2, and fix this issue
by one of the following actions.

- Convert your Package to Python3. This is the preferred option.  In
  case you are providing a Python module foo, please consider dropping
  the python-foo package, and only build a python3-foo package.  Please
  don't drop Python2 modules, which still have reverse dependencies,
  just document them.
  
  This is the preferred option.

- If the package is dead upstream, cannot be converted or maintained
  in Debian, it should be removed from the distribution.  If the
  package still has reverse dependencies, raise the severity to
  "serious" and document the reverse dependencies with the BTS affects
  command.  If the package has no reverse dependencies, confirm that
  the package can be removed, reassign this issue to ftp.debian.org,
  make sure that the bug priority is set to normal and retitle the
  issue to "RM: PKG -- removal triggered by the Python2 removal".

- If the package has still many users (popcon >= 300), or is needed to
  build another package which cannot be removed, document that by
  adding the "py2keep" user tag (not replacing the py2remove tag),
  using the debian-pyt...@lists.debian.org user.  Also any
  dependencies on an unversioned python package (python, python-dev)
  must not be used, same with the python shebang.  These have to be
  replaced by python2/python2.7 dependencies and shebang.

  This is the least preferred option.

If the conversion or removal needs action on another package first,
please document the blocking by using the BTS affects command, like

  affects  + src:python-passfd

If there is no py2removal bug for that reverse-dependency, please file
a bug on this package (similar to this bug report).

If there are questions, please refer to the wiki page for the removal:
https://wiki.debian.org/Python/2Removal, or ask for help on IRC
#debian-python, or the debian-pyt...@lists.debian.org mailing list.
--- End Message ---
--- Begin Message ---
Version: 0.2-3+rm

Dear submitter,

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

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

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

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

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

Debian distribution maintenance software
pp.
Thorsten Alteholz (the ftpmaster behind the curtain)--- End Message ---

Bug#446343: marked as done (cutter: does not work at all)

[Debian Bug Tracking System]

Your message dated Sun, 19 Jun 2022 19:29:57 +
with message-id 
and subject line Bug#1010705: Removed package(s) from unstable
has caused the Debian Bug report #446343,
regarding cutter: does not work at all
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.)


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

Cutter does not work as described; it always reports "No matching
connections found". Here is a repeatable example:

netstat -an | grep 'ESTABLISHED'
tcp0  0 192.168.130.5:38101 10.1.30.129:22 ESTABLISHED
tcp0  0 192.168.130.5:38819 10.1.30.129:993ESTABLISHED


cutter 192.168.130.5 38101 10.1.30.129 22
No matching connections found
cutter 192.168.130.5 38101 10.1.30.129
No matching connections found
cutter 192.168.130.5 38101
No matching connections found

cutter 10.1.30.129 22 192.168.130.5 38101
No matching connections found
cutter 10.1.30.129 22 192.168.130.5
No matching connections found
cutter 10.1.30.129 22
No matching connections found

Regards,
Chris

-- System Information:
Debian Release: lenny/sid
  APT prefers testing
  APT policy: (990, 'testing'), (900, 'stable'), (300, 'unstable'), (50, 
'experimental')
Architecture: i386 (i686)

Kernel: Linux 2.6.21-2-686 (SMP w/2 CPU cores)
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)
Shell: /bin/sh linked to /bin/bash

Versions of packages cutter depends on:
ii  libc6 2.6.1-1+b1 GNU C Library: Shared libraries

cutter recommends no packages.

-- no debconf information


--- End Message ---
--- Begin Message ---
Version: 1.04-1+rm

Dear submitter,

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

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

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

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

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

Debian distribution maintenance software
pp.
Thorsten Alteholz (the ftpmaster behind the curtain)--- End Message ---

Bug#1011844: marked as done (tools-analyzer-jvm-clojure: FTBFS: Cannot access snapshots (https://oss.sonatype.org/content/repositories/snapshots) in offline mode and the artifact nrepl:nrepl:jar:0.6.0

[Debian Bug Tracking System]

Your message dated Sun, 19 Jun 2022 15:22:30 -0400
with message-id <0adcfb28-0a17-2072-04ea-034120d66...@debian.org>
and subject line close Clojure bugs created by the nrepl bug in lein
has caused the Debian Bug report #1011844,
regarding tools-analyzer-jvm-clojure: FTBFS: Cannot access snapshots 
(https://oss.sonatype.org/content/repositories/snapshots) in offline mode and 
the artifact nrepl:nrepl:jar:0.6.0 has not been downloaded from it before.
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.)


-- 
1011844: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1011844
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: tools-analyzer-jvm-clojure
Version: 1.1.0-3
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20220525 ftbfs-bookworm

Hi,

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


Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> lein test
> Cannot access central (https://repo1.maven.org/maven2/) in offline mode and 
> the artifact nrepl:nrepl:jar:0.6.0 has not been downloaded from it before.
> Cannot access clojars (https://repo.clojars.org/) in offline mode and the 
> artifact nrepl:nrepl:jar:0.6.0 has not been downloaded from it before.
> Cannot access sonatype 
> (https://oss.sonatype.org/content/repositories/releases) in offline mode and 
> the artifact nrepl:nrepl:jar:0.6.0 has not been downloaded from it before.
> Cannot access snapshots 
> (https://oss.sonatype.org/content/repositories/snapshots) in offline mode and 
> the artifact nrepl:nrepl:jar:0.6.0 has not been downloaded from it before.
> This could be due to a typo in :dependencies, file system permissions, or 
> network issues.
> If you are behind a proxy, try setting the 'http_proxy' environment variable.
> make[1]: *** [debian/rules:22: override_dh_auto_test] Error 1


The full build log is available from:
http://qa-logs.debian.net/2022/05/25/tools-analyzer-jvm-clojure_1.1.0-3_unstable.log

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

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

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

If you fail to reproduce this, please provide a build log and diff it with mine
so that we can identify if something relevant changed in the meantime.
--- End Message ---
--- Begin Message ---
These bugs were fixed when #1012824 was.

-- 
  ⢀⣴⠾⠻⢶⣦⠀
  ⣾⠁⢠⠒⠀⣿⡁  Louis-Philippe Véronneau
  ⢿⡄⠘⠷⠚⠋   po...@debian.org / veronneau.org
  ⠈⠳⣄--- End Message ---

Bug#1011864: marked as done (tools-reader-clojure: FTBFS: Cannot access sonatype-oss-public (https://oss.sonatype.org/content/groups/public/) in offline mode and the artifact nrepl:nrepl:jar:0.6.0 has

[Debian Bug Tracking System]

Your message dated Sun, 19 Jun 2022 15:22:30 -0400
with message-id <0adcfb28-0a17-2072-04ea-034120d66...@debian.org>
and subject line close Clojure bugs created by the nrepl bug in lein
has caused the Debian Bug report #1011864,
regarding tools-reader-clojure: FTBFS: Cannot access sonatype-oss-public 
(https://oss.sonatype.org/content/groups/public/) in offline mode and the 
artifact nrepl:nrepl:jar:0.6.0 has not been downloaded from it before.
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.)


-- 
1011864: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1011864
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: tools-reader-clojure
Version: 1.3.4-1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20220525 ftbfs-bookworm

Hi,

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


Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> lein test
> Cannot access central (https://repo1.maven.org/maven2/) in offline mode and 
> the artifact nrepl:nrepl:jar:0.6.0 has not been downloaded from it before.
> Cannot access clojars (https://repo.clojars.org/) in offline mode and the 
> artifact nrepl:nrepl:jar:0.6.0 has not been downloaded from it before.
> Cannot access sonatype-oss-public 
> (https://oss.sonatype.org/content/groups/public/) in offline mode and the 
> artifact nrepl:nrepl:jar:0.6.0 has not been downloaded from it before.
> This could be due to a typo in :dependencies, file system permissions, or 
> network issues.
> If you are behind a proxy, try setting the 'http_proxy' environment variable.
> make[1]: *** [debian/rules:22: override_dh_auto_test] Error 1


The full build log is available from:
http://qa-logs.debian.net/2022/05/25/tools-reader-clojure_1.3.4-1_unstable.log

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

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

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

If you fail to reproduce this, please provide a build log and diff it with mine
so that we can identify if something relevant changed in the meantime.
--- End Message ---
--- Begin Message ---
These bugs were fixed when #1012824 was.

-- 
  ⢀⣴⠾⠻⢶⣦⠀
  ⣾⠁⢠⠒⠀⣿⡁  Louis-Philippe Véronneau
  ⢿⡄⠘⠷⠚⠋   po...@debian.org / veronneau.org
  ⠈⠳⣄--- End Message ---

Bug#1011837: marked as done (tools-analyzer-clojure: FTBFS: Cannot access snapshots (https://oss.sonatype.org/content/repositories/snapshots) in offline mode and the artifact nrepl:nrepl:jar:0.6.0 has

[Debian Bug Tracking System]

Your message dated Sun, 19 Jun 2022 15:22:30 -0400
with message-id <0adcfb28-0a17-2072-04ea-034120d66...@debian.org>
and subject line close Clojure bugs created by the nrepl bug in lein
has caused the Debian Bug report #1011837,
regarding tools-analyzer-clojure: FTBFS: Cannot access snapshots 
(https://oss.sonatype.org/content/repositories/snapshots) in offline mode and 
the artifact nrepl:nrepl:jar:0.6.0 has not been downloaded from it before.
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.)


-- 
1011837: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1011837
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: tools-analyzer-clojure
Version: 1.0.0-2
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20220525 ftbfs-bookworm

Hi,

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


Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> lein test
> Cannot access central (https://repo1.maven.org/maven2/) in offline mode and 
> the artifact nrepl:nrepl:jar:0.6.0 has not been downloaded from it before.
> Cannot access clojars (https://repo.clojars.org/) in offline mode and the 
> artifact nrepl:nrepl:jar:0.6.0 has not been downloaded from it before.
> Cannot access sonatype 
> (https://oss.sonatype.org/content/repositories/releases) in offline mode and 
> the artifact nrepl:nrepl:jar:0.6.0 has not been downloaded from it before.
> Cannot access snapshots 
> (https://oss.sonatype.org/content/repositories/snapshots) in offline mode and 
> the artifact nrepl:nrepl:jar:0.6.0 has not been downloaded from it before.
> This could be due to a typo in :dependencies, file system permissions, or 
> network issues.
> If you are behind a proxy, try setting the 'http_proxy' environment variable.
> make[1]: *** [debian/rules:23: override_dh_auto_test] Error 1


The full build log is available from:
http://qa-logs.debian.net/2022/05/25/tools-analyzer-clojure_1.0.0-2_unstable.log

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

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

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

If you fail to reproduce this, please provide a build log and diff it with mine
so that we can identify if something relevant changed in the meantime.
--- End Message ---
--- Begin Message ---
These bugs were fixed when #1012824 was.

-- 
  ⢀⣴⠾⠻⢶⣦⠀
  ⣾⠁⢠⠒⠀⣿⡁  Louis-Philippe Véronneau
  ⢿⡄⠘⠷⠚⠋   po...@debian.org / veronneau.org
  ⠈⠳⣄--- End Message ---

Bug#1011856: marked as done (test-check-clojure: FTBFS: Cannot access clojars (https://repo.clojars.org/) in offline mode and the artifact org.clojure:clojure:jar:1.10.2 has not been downloaded from i

[Debian Bug Tracking System]

Your message dated Sun, 19 Jun 2022 19:19:14 +
with message-id 
and subject line Bug#1011856: fixed in test-check-clojure 0.9.0-5
has caused the Debian Bug report #1011856,
regarding test-check-clojure: FTBFS: Cannot access clojars 
(https://repo.clojars.org/) in offline mode and the artifact 
org.clojure:clojure:jar:1.10.2 has not been downloaded from it before.
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.)


-- 
1011856: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1011856
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: test-check-clojure
Version: 0.9.0-4
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20220525 ftbfs-bookworm

Hi,

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


Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> lein -o test
> Cannot access central (https://repo1.maven.org/maven2/) in offline mode and 
> the artifact nrepl:nrepl:jar:0.6.0 has not been downloaded from it before.
> Cannot access clojars (https://repo.clojars.org/) in offline mode and the 
> artifact nrepl:nrepl:jar:0.6.0 has not been downloaded from it before.
> Cannot access central (https://repo1.maven.org/maven2/) in offline mode and 
> the artifact org.clojure:clojure:jar:1.10.2 has not been downloaded from it 
> before.
> Cannot access clojars (https://repo.clojars.org/) in offline mode and the 
> artifact org.clojure:clojure:jar:1.10.2 has not been downloaded from it 
> before.
> This could be due to a typo in :dependencies, file system permissions, or 
> network issues.
> If you are behind a proxy, try setting the 'http_proxy' environment variable.
> Error encountered performing task 'test' with profile(s): 
> 'base,system,user,provided,dev,offline'
> Could not resolve dependencies
> make[1]: *** [debian/rules:20: override_dh_auto_test] Error 1


The full build log is available from:
http://qa-logs.debian.net/2022/05/25/test-check-clojure_0.9.0-4_unstable.log

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

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

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

If you fail to reproduce this, please provide a build log and diff it with mine
so that we can identify if something relevant changed in the meantime.
--- End Message ---
--- Begin Message ---
Source: test-check-clojure
Source-Version: 0.9.0-5
Done: Louis-Philippe Véronneau 

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

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

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

Debian distribution maintenance software
pp.
Louis-Philippe Véronneau  (supplier of updated 
test-check-clojure 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, 19 Jun 2022 14:51:09 -0400
Source: test-check-clojure
Architecture: source
Version: 0.9.0-5
Distribution: unstable
Urgency: medium
Maintainer: Debian Clojure Maintainers 
Changed-By: Louis-Philippe Véronneau 
Closes: 1011856
Changes:
 test-check-clojure (0.9.0-5) unstable; urgency=medium
 .
   * Team upload.
 .
   [ Louis-Philippe Véronneau ]
   * d/control: New email for the Clojure Team.
   * d/rules: simplify java lib install.
   * d/patches/0005: use generic '1.10.x' version for clojure.
 (Closes: #1011856)
   * d/rules: simplify build and generate the pom file using lein.
   * d/tests/unittests: rewrite in proper clojure.
   * d/control: Standards-Version update to 4.6.1. No changes.
Checksums-Sha1:
 720a60aad171c2ba5965191cc34a0d2bf8396684 1583 test-check-clojure_0.9.0-5.dsc
 b07ced55e5af12265ffc97fb07d6abfbc6f26f44 10832 
test-check-clojure_0.9.0-5.debian.tar.xz
 

Bug#1013238: src:pyspread: fails to migrate to testing for too long: uploader built arch:all binary

[Paul Gevers]

Source: pyspread
Version: 2.0.1-1
Severity: serious
Control: close -1 2.1-2
Tags: sid bookworm pending
User: release.debian@packages.debian.org
Usertags: out-of-sync

Dear maintainer(s),

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


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


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


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


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


Paul

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



OpenPGP_signature
Description: OpenPGP digital signature

Processed: src:pyspread: fails to migrate to testing for too long: uploader built arch:all binary

[Debian Bug Tracking System]

Processing control commands:

> close -1 2.1-2
Bug #1013238 [src:pyspread] src:pyspread: fails to migrate to testing for too 
long: uploader built arch:all binary
Marked as fixed in versions pyspread/2.1-2.
Bug #1013238 [src:pyspread] src:pyspread: fails to migrate to testing for too 
long: uploader built arch:all binary
Marked Bug as done

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

Bug#1012613: marked as done (nftables: upgrade stops but does not start service)

[Debian Bug Tracking System]

Your message dated Sun, 19 Jun 2022 18:18:54 +
with message-id 
and subject line Bug#1012613: fixed in nftables 1.0.4-2
has caused the Debian Bug report #1012613,
regarding nftables: upgrade stops but does not start service
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.)


-- 
1012613: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1012613
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: nftables
Version: 1.0.4-1
Severity: serious

Dear Maintainer,

upgrades of nftables stop the service but do not start it (even if the
service is actually enabled).
This can lead to lockouts, e.g. when using special rules for ssh access.


nft.preinst:

#!/bin/sh
set -e
# Automatically added by dh_installsystemd/13.7.1
if [ -z "${DPKG_ROOT:-}" ] && [ "$1" = upgrade ] && [ -d
/run/systemd/system ] ; then
   deb-systemd-invoke stop 'nftables.service' >/dev/null || true
fi
# End automatically added section


nft.postinst:

#!/bin/sh
set -e
# Automatically added by dh_installsystemd/13.7.1
if [ "$1" = "configure" ] || [ "$1" = "abort-upgrade" ] || [ "$1" =
"abort-deconfigure" ] || [ "$1" = "abort-remove" ] ; then
   if deb-systemd-helper debian-installed 'nftables.service'; then
   # This will only remove masks created by d-s-h on
package removal.
   deb-systemd-helper unmask 'nftables.service' >/dev/null || true

   if deb-systemd-helper --quiet was-enabled
'nftables.service'; then
   # Create new symlinks, if any.
   deb-systemd-helper enable 'nftables.service'
>/dev/null || true
   fi
   fi

   # Update the statefile to add new symlinks (if any), which need
to be cleaned
   # up on purge. Also remove old symlinks.
   deb-systemd-helper update-state 'nftables.service' >/dev/null || true
fi
# End automatically added section
--- End Message ---
--- Begin Message ---
Source: nftables
Source-Version: 1.0.4-2
Done: Jeremy Sowden 

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

Debian distribution maintenance software
pp.
Jeremy Sowden  (supplier of updated nftables 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, 19 Jun 2022 18:04:19 +0100
Source: nftables
Architecture: source
Version: 1.0.4-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Netfilter Packaging Team 

Changed-By: Jeremy Sowden 
Closes: 1012613
Changes:
 nftables (1.0.4-2) unstable; urgency=medium
 .
   * [9e654e0] d/nftables.conf: use named priorities
   * [0e9757f] d/u/signing-key.asc: minimize signing key
   * [49d2aee] d/libnftables1.symbols: add `Build-Depends-Package` field
   * [1a50850] d/control: set R³: no.
   * [1699c66] d/control: add myself to uploaders.
   * [cd9f31f] d/watch: use HTTPS URL
   * [a6a05b6] d/watch: use `pgpmode=auto`
   * [072624b] d/gbp.conf: buildpackage, import-orig: enable `pristine-tar`
   * [92a12a3] d/gbp.conf: dch: set `id-length`
   * [6ad5a0b] d/not-installed: remove static archive
   * [c53e37d] d/rules: remove obsolete dh_installinit override
   * [fb41a26] d/rules: move dh_auto_configure override
   * [59c9317] d/rules: include architecture.mk
   * [8f18fcd] d/rules: pass `--restart-after-upgrade` to dh_installsystemd
 (closes: #1012613)
   * [f9d8a42] d/copyright: remove obsolete files
   * [75426a2] d/changelog: wrap long line
Checksums-Sha1:
 e77619690cc0883b7c5ff9849837ef6b8d6203b5 2692 nftables_1.0.4-2.dsc
 6b4c538242c1061fe23d4ce226c79519482eeacc 20920 nftables_1.0.4-2.debian.tar.xz
 ce631278eeda5fed78c5ae830c62d27c94f0a99b 8797 nftables_1.0.4-2_amd64.buildinfo
Checksums-Sha256:
 e678a100fcdb25a721ca8365abc1bff8d4c69853eba6e68c9aefb19dd40568b4 2692 
nftables_1.0.4-2.dsc
 67d7e9aa4e97e25c84850ac2b9b8c3657180c258f74363931e5c5eacca6163ae 20920 
nftables_1.0.4-2.debian.tar.xz
 c57bdca73d9cfa76cfc81d57ff833f2ecb625c96c2058c1b8b1c35fa3fe79264 8797 
nftables_1.0.4-2_amd64.buildinfo
Files:
 b7a9825a85e87c34f857736fe73c93ee 2692 net important nftables_1.0.4-2.dsc
 

Processed: Re: Fwd: Re: [Pkg-javascript-devel] Bug#1013218: rails: ftbfs SyntaxError: Unexpected token 'export'

[Debian Bug Tracking System]

Processing control commands:

> tags -1 help
Bug #1013218 [ruby-sprockets] rails: ftbfs SyntaxError: Unexpected token 
'export'
Added tag(s) help.

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

Bug#978259: marked as done (python-testing.mysqld: FTBFS: dh_auto_test: error: pybuild --test --test-nose -i python{version} -p 3.9 returned exit code 13)

[Debian Bug Tracking System]

Your message dated Sun, 19 Jun 2022 18:03:54 +
with message-id 
and subject line Bug#978259: fixed in python-testing.mysqld 1.4.0-6
has caused the Debian Bug report #978259,
regarding python-testing.mysqld: FTBFS: dh_auto_test: error: pybuild --test 
--test-nose -i python{version} -p 3.9 returned exit code 13
to be marked as done.

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

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


-- 
978259: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=978259
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-testing.mysqld
Version: 1.4.0-4
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20201226 ftbfs-bullseye

Hi,

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

Relevant part (hopefully):
>  debian/rules build
> dh build --with python3 --buildsystem=pybuild
>dh_update_autotools_config -O--buildsystem=pybuild
>dh_autoreconf -O--buildsystem=pybuild
>dh_auto_configure -O--buildsystem=pybuild
> I: pybuild base:232: python3.9 setup.py config 
> running config
>dh_auto_build -O--buildsystem=pybuild
> I: pybuild base:232: /usr/bin/python3 setup.py build 
> running build
> running build_py
> creating /<>/.pybuild/cpython3_3.9_testing.mysqld/build/testing
> copying src/testing/__init__.py -> 
> /<>/.pybuild/cpython3_3.9_testing.mysqld/build/testing
> copying src/testing/mysqld.py -> 
> /<>/.pybuild/cpython3_3.9_testing.mysqld/build/testing
> running egg_info
> writing src/testing.mysqld.egg-info/PKG-INFO
> writing dependency_links to src/testing.mysqld.egg-info/dependency_links.txt
> writing namespace_packages to 
> src/testing.mysqld.egg-info/namespace_packages.txt
> writing requirements to src/testing.mysqld.egg-info/requires.txt
> writing top-level names to src/testing.mysqld.egg-info/top_level.txt
> reading manifest file 'src/testing.mysqld.egg-info/SOURCES.txt'
> reading manifest template 'MANIFEST.in'
> writing manifest file 'src/testing.mysqld.egg-info/SOURCES.txt'
>dh_auto_test -O--buildsystem=pybuild
> I: pybuild base:232: cd 
> /<>/.pybuild/cpython3_3.9_testing.mysqld/build; python3.9 -m 
> nose -v tests
> test_MysqldFactory (test_mysql.TestMysqld) ... ERROR
> test_MysqldFactory_with_initialized_handler (test_mysql.TestMysqld) ... ERROR
> test_basic (test_mysql.TestMysqld) ... ERROR
> test_copy_data_from (test_mysql.TestMysqld) ... ERROR
> test_copy_data_from_with_passwd (test_mysql.TestMysqld) ... ERROR
> test_dsn_and_url (test_mysql.TestMysqld) ... ok
> test_fork (test_mysql.TestMysqld) ... ERROR
> test_multiple_mysql (test_mysql.TestMysqld) ... ERROR
> test_mysqld_is_not_found (test_mysql.TestMysqld) ... ok
> test_skipIfNotFound_found (test_mysql.TestMysqld) ... ok
> test_skipIfNotFound_notfound (test_mysql.TestMysqld) ... ok
> test_skipIfNotInstalled_found (test_mysql.TestMysqld) ... ok
> test_skipIfNotInstalled_notfound (test_mysql.TestMysqld) ... ok
> test_skipIfNotInstalled_with_args_found (test_mysql.TestMysqld) ... ok
> test_skipIfNotInstalled_with_args_notfound (test_mysql.TestMysqld) ... ok
> test_stop (test_mysql.TestMysqld) ... ERROR
> test_stop_on_child_process (test_mysql.TestMysqld) ... ERROR
> test_with_mysql (test_mysql.TestMysqld) ... ERROR
> 
> ==
> ERROR: test_MysqldFactory (test_mysql.TestMysqld)
> --
> Traceback (most recent call last):
>   File 
> "/<>/.pybuild/cpython3_3.9_testing.mysqld/build/tests/test_mysql.py",
>  line 252, in test_MysqldFactory
> with Mysqld() as mysqld1:
>   File "/usr/lib/python3/dist-packages/testing/common/database.py", line 54, 
> in __call__
> return self.target_class(**self.settings)
>   File "/usr/lib/python3/dist-packages/testing/common/database.py", line 94, 
> in __init__
> self.start()
>   File "/usr/lib/python3/dist-packages/testing/common/database.py", line 151, 
> in start
> self.poststart()
>   File 
> "/<>/.pybuild/cpython3_3.9_testing.mysqld/build/testing/mysqld.py",
>  line 155, in poststart
> with closing(pymysql.connect(**params)) as conn:
>   File "/usr/lib/python3/dist-packages/pymysql/__init__.py", line 94, in 
> Connect
> return Connection(*args, **kwargs)
>   File "/usr/lib/python3/dist-packages/pymysql/connections.py", line 325, in 
> __init__
> self.connect()
>   File "/usr/lib/python3/dist-packages/pymysql/connections.py", line 599, in 
> connect
> self._request_authentication()
>   File "/usr/lib/python3/dist-packages/pymysql/connections.py", line 861, in 
> 

Bug#1013129: marked as done (exo: CVE-2022-32278)

[Debian Bug Tracking System]

Your message dated Sun, 19 Jun 2022 17:47:08 +
with message-id 
and subject line Bug#1013129: fixed in exo 4.16.0-1+deb11u1
has caused the Debian Bug report #1013129,
regarding exo: CVE-2022-32278
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.)


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

Hi,

The following vulnerability was published for exo.

CVE-2022-32278[0]:
| XFCE 4.16 allows attackers to execute arbitrary code because xdg-open
| can execute a .desktop file on an attacker-controlled FTP server.

https://gitlab.xfce.org/xfce/exo/-/commit/c71c04ff5882b2866a0d8506fb460d4ef796de9f

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-2022-32278
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-32278

Please adjust the affected versions in the BTS as needed.
--- End Message ---
--- Begin Message ---
Source: exo
Source-Version: 4.16.0-1+deb11u1
Done: Yves-Alexis Perez 

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

Debian distribution maintenance software
pp.
Yves-Alexis Perez  (supplier of updated exo 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, 18 Jun 2022 14:17:06 +0200
Source: exo
Binary: exo-utils exo-utils-dbgsym libexo-2-0 libexo-2-0-dbgsym libexo-2-dev 
libexo-common
Architecture: source amd64 all
Version: 4.16.0-1+deb11u1
Distribution: bullseye-security
Urgency: medium
Maintainer: Debian Xfce Maintainers 
Changed-By: Yves-Alexis Perez 
Description:
 exo-utils  - Utility files for libexo
 libexo-2-0 - Library with extensions for Xfce (GTK-3 version)
 libexo-2-dev - Development files for libexo (GTK-3 version)
 libexo-common - libexo common files
Closes: 1013129
Changes:
 exo (4.16.0-1+deb11u1) stable-security; urgency=medium
 .
   * d/patches: 0001-exo-open-Only-execute-local-.desktop-files.patch added
 Fix CVE-2022-32278, exo allows executing .desktop files with remote URI
 scheme. (Closes: #1013129)
Checksums-Sha1:
 328ddf2529764c12965df8dd42158f63dc0d521f 1884 exo_4.16.0-1+deb11u1.dsc
 7f5fa747df1a9b48531b4ff13fb7f7671088f0aa 966143 exo_4.16.0.orig.tar.bz2
 1cbd216290741e8fb6e1c9911b0ea8cc9509664f 13888 
exo_4.16.0-1+deb11u1.debian.tar.xz
 7968726451ec3f1d710411bab1426864e9fb0f95 90208 
exo-utils-dbgsym_4.16.0-1+deb11u1_amd64.deb
 7ccbe1675a5f0284c4feb8ac74b34fe1c686fcb9 218348 
exo-utils_4.16.0-1+deb11u1_amd64.deb
 893a027b84a7d3ef8ac5b7328fd76ac3830acf07 16634 
exo_4.16.0-1+deb11u1_amd64.buildinfo
 5d12667edcedab58767fbc1d7a3e13733529042f 255452 
libexo-2-0-dbgsym_4.16.0-1+deb11u1_amd64.deb
 be3c9f3f3779e56a304998824cfec25671f2ea16 417864 
libexo-2-0_4.16.0-1+deb11u1_amd64.deb
 1179fb3eb7b64f6a312f0d4dd3a15e1aea4aa863 297116 
libexo-2-dev_4.16.0-1+deb11u1_amd64.deb
 1aee934e46e4a584994a010b44a752125912be67 193704 
libexo-common_4.16.0-1+deb11u1_all.deb
Checksums-Sha256:
 89abf6527fc85fa71087065dc294e23f13d0cf3150fad9a324d1abfe4bfee2af 1884 
exo_4.16.0-1+deb11u1.dsc
 1975b00eed9a8aa1f899eab2efaea593731c19138b83fdff2f13bdca5275bacc 966143 
exo_4.16.0.orig.tar.bz2
 12fbfab59721b6c879bbe19cdc768bd084ed2967177b711d7fc9d32e468b2788 13888 
exo_4.16.0-1+deb11u1.debian.tar.xz
 d6b808f9985d58e406f3cd17000d8b49f492c369fb515ea60eea4bd54d73c13b 90208 
exo-utils-dbgsym_4.16.0-1+deb11u1_amd64.deb
 2d64d3656244dbaf9bdcd259f153a14f55b03e14a6f3a572eb2536af9843e3e7 218348 
exo-utils_4.16.0-1+deb11u1_amd64.deb
 075396b463c0c51a8a2a995867c9bfecd1e6db202114053664617b646115026f 16634 
exo_4.16.0-1+deb11u1_amd64.buildinfo
 d93e26198640b07e316a770946a694179f75f7beb654284246a4d3b01a18 255452 
libexo-2-0-dbgsym_4.16.0-1+deb11u1_amd64.deb
 ad038f2461f640b2eac2e6da596995187d41d23cfa5064ce1fb71942d49a57a1 417864 
libexo-2-0_4.16.0-1+deb11u1_amd64.deb
 

Bug#1013129: marked as done (exo: CVE-2022-32278)

[Debian Bug Tracking System]

Your message dated Sun, 19 Jun 2022 17:47:26 +
with message-id 
and subject line Bug#1013129: fixed in exo 0.12.4-1+deb10u1
has caused the Debian Bug report #1013129,
regarding exo: CVE-2022-32278
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.)


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

Hi,

The following vulnerability was published for exo.

CVE-2022-32278[0]:
| XFCE 4.16 allows attackers to execute arbitrary code because xdg-open
| can execute a .desktop file on an attacker-controlled FTP server.

https://gitlab.xfce.org/xfce/exo/-/commit/c71c04ff5882b2866a0d8506fb460d4ef796de9f

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-2022-32278
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-32278

Please adjust the affected versions in the BTS as needed.
--- End Message ---
--- Begin Message ---
Source: exo
Source-Version: 0.12.4-1+deb10u1
Done: Yves-Alexis Perez 

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

Debian distribution maintenance software
pp.
Yves-Alexis Perez  (supplier of updated exo 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, 18 Jun 2022 14:25:09 +0200
Source: exo
Architecture: source
Version: 0.12.4-1+deb10u1
Distribution: oldstable-security
Urgency: medium
Maintainer: Debian Xfce Maintainers 
Changed-By: Yves-Alexis Perez 
Closes: 1013129
Changes:
 exo (0.12.4-1+deb10u1) oldstable-security; urgency=medium
 .
   * d/patches: 0001-exo-open-Only-execute-local-.desktop-files.patch added
 Fix CVE-2022-32278, exo allows executing .desktop files with remote URI
 scheme.
 (Closes: #1013129)
Checksums-Sha1:
 ec7725974545875907d32cf9337f58d8e96f8e1f 2074 exo_0.12.4-1+deb10u1.dsc
 2fda283fa85b79ad7c4f644e5d18879e1f2d57d2 1235738 exo_0.12.4.orig.tar.bz2
 3d477cbe2a54eaf43384f783129c518ba5b56f26 14916 
exo_0.12.4-1+deb10u1.debian.tar.xz
 09c01f389137b68d4360c9271cec8053e7a78974 18991 
exo_0.12.4-1+deb10u1_amd64.buildinfo
Checksums-Sha256:
 7026aa77acb42beaf5530e4b562dc67a6f037140f1026237c9e91c5486e4d4e0 2074 
exo_0.12.4-1+deb10u1.dsc
 b0af60816bdb572ce53f19462fb1f3a5895a04017a878893dc03c166ea2050af 1235738 
exo_0.12.4.orig.tar.bz2
 59dba09929e51705eb634dd63d2738355d1f0fb0c00f1c188c9a5f3aeb409227 14916 
exo_0.12.4-1+deb10u1.debian.tar.xz
 2b03c406fb73882f18d3fe01dedb2c5b706ae17e77b0cbb06e403760f7c6ba8d 18991 
exo_0.12.4-1+deb10u1_amd64.buildinfo
Files:
 e90dcfa04b96133532426725467afd9c 2074 xfce optional exo_0.12.4-1+deb10u1.dsc
 962bbccb38db0aecd4151ca97f6a39bc 1235738 xfce optional exo_0.12.4.orig.tar.bz2
 db85723e76ec39dccc7394c6b63afdfd 14916 xfce optional 
exo_0.12.4-1+deb10u1.debian.tar.xz
 32e49cada7afb46651c4c182f5d6c77e 18991 xfce optional 
exo_0.12.4-1+deb10u1_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQEzBAEBCgAdFiEE8vi34Qgfo83x35gF3rYcyPpXRFsFAmKtxXAACgkQ3rYcyPpX
RFvfhQf/ckVuuVCw3CoDwYNuzsOtvgb3p+GXyIMjc9a9GYS3yP4ggdEanjAjjWdf
smOkclYhVE9jkQSWR0mTvJ33TFRh9uX5QpWH7p3e/SM+LC8R2R1jJTl0TH1u3zIj
BI/lIYJ83JPGjiwXOAbHDzfXqsdrlLINQBM9ZhNkiH9ON4AIZ1M5tI0usbwY6icF
NClKX5sBzrhjv/x3gXV7FEDassop4D23kPVNLZ0dgJN3LuiIWNvBEnId7BYS52L4
dCLAzP9ideCMFx5lBwdn+fs5H2PbCxWEhoJJoAAfoiqyqWO5nEsSxm7rOym/cDbt
pu3Q1Nd7sMHRs0klmvKhwjF6pfe+sA==
=uJT2
-END PGP SIGNATURE End Message ---

Bug#1012613: nftables: upgrade stops but does not start service

[Jeremy Sowden]

On 2022-06-19, at 13:48:59 +0200, Arturo Borrero Gonzalez wrote:
> On Fri, 10 Jun 2022 12:21:37 +0200 Christian Göttsche wrote:
> > Package: nftables
> > Version: 1.0.4-1
> > Severity: serious
> >
> > Dear Maintainer,
> >
> > upgrades of nftables stop the service but do not start it (even if the
> > service is actually enabled).
> > This can lead to lockouts, e.g. when using special rules for ssh access.
> >
> >
> > nft.preinst:
> >
> > #!/bin/sh
> > set -e
> > # Automatically added by dh_installsystemd/13.7.1
> > if [ -z "${DPKG_ROOT:-}" ] && [ "$1" = upgrade ] && [ -d 
> > /run/systemd/system ] ; then
> >deb-systemd-invoke stop 'nftables.service' >/dev/null || true
> > fi
> > # End automatically added section
> >
> >
> > nft.postinst:
> >
> > #!/bin/sh
> > set -e
> > # Automatically added by dh_installsystemd/13.7.1
> > if [ "$1" = "configure" ] || [ "$1" = "abort-upgrade" ] || [ "$1" = 
> > "abort-deconfigure" ] || [ "$1" = "abort-remove" ] ; then
> >if deb-systemd-helper debian-installed 'nftables.service'; then
> ># This will only remove masks created by d-s-h on package 
> > removal.
> >deb-systemd-helper unmask 'nftables.service' >/dev/null || 
> > true
> >
> >if deb-systemd-helper --quiet was-enabled 
> > 'nftables.service'; then
> ># Create new symlinks, if any.
> >deb-systemd-helper enable 'nftables.service' 
> > >/dev/null || true
> >fi
> >fi
> >
> ># Update the statefile to add new symlinks (if any), which need to 
> > be cleaned
> ># up on purge. Also remove old symlinks.
> >deb-systemd-helper update-state 'nftables.service' >/dev/null || true
> > fi
> > # End automatically added section
>
> I confirmed this can be a problem:
>
> [...]
>
> @Alberto, @Jeremy,
>
> It seems to me like we need to play with the dh_installsystemd
> --no-restart-after-upgrade option, but don't have time to figure out the
> right logic.
>
> I'm currently unable to handle this. Could you please take a look?

Passing `--restart-after-upgrade` does the trick:

  diff -u nftables_1.0.4-1/postinst nftables_1.0.4-2/postinst
  --- nftables_1.0.4-1/postinst   2022-06-07 23:59:59.0 +0100
  +++ nftables_1.0.4-2/postinst   2022-06-19 18:04:19.0 +0100
  @@ -17,3 +17,13 @@
  deb-systemd-helper update-state 'nftables.service' >/dev/null || true
  fi
  # End automatically added section
  +# Automatically added by dh_installsystemd/13.7.1
  +if [ "$1" = "configure" ] || [ "$1" = "abort-upgrade" ] || [ "$1" = 
"abort-deconfigure" ] || [ "$1" = "abort-remove" ] ; then
  +   if [ -z "${DPKG_ROOT:-}" ] && [ -d /run/systemd/system ]; then
  +   systemctl --system daemon-reload >/dev/null || true
  +   if [ -n "$2" ]; then
  +   deb-systemd-invoke try-restart 'nftables.service' 
>/dev/null || true
  +   fi
  +   fi
  +fi
  +# End automatically added section

I've pushed that and a few other changes to Salsa.

J.


signature.asc
Description: PGP signature

Processed: Bug#978259 marked as pending in python-testing.mysqld

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #978259 [src:python-testing.mysqld] python-testing.mysqld: FTBFS: 
dh_auto_test: error: pybuild --test --test-nose -i python{version} -p 3.9 
returned exit code 13
Added tag(s) pending.

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

Bug#978259: marked as pending in python-testing.mysqld

[Sandro Tosi]

Control: tag -1 pending

Hello,

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

https://salsa.debian.org/python-team/packages/python-testing.mysqld/-/commit/76d3aebb247f55acce57e3ae282d4fb0a9bf8e0f


disable tests, until someone fixes them; Closes: #978259


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/978259

Bug#1011142: marked as done (nvidia-graphics-drivers-legacy-390xx: CVE-2022-28181, CVE-2022-28185)

[Debian Bug Tracking System]

Your message dated Sun, 19 Jun 2022 17:02:24 +
with message-id 
and subject line Bug#1011142: fixed in nvidia-graphics-drivers-legacy-390xx 
390.151-1~deb10u1
has caused the Debian Bug report #1011142,
regarding nvidia-graphics-drivers-legacy-390xx: CVE-2022-28181, CVE-2022-28185
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.)


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

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

CVE-2022-28181  NVIDIA GPU Display Driver for Windows and Linux contains
a vulnerability in the kernel mode layer, where an unprivileged regular
user on the network can cause an out-of-bounds write through a specially
crafted shader, which may lead to code execution, denial of service,
escalation of privileges, information disclosure, and data tampering.
The scope of the impact may extend to other components.

CVE-2022-28183  NVIDIA GPU Display Driver for Windows and Linux contains
a vulnerability in the kernel mode layer, where an unprivileged regular
user can cause an out-of-bounds read, which may lead to denial of
service and information disclosure.

CVE-2022-28184  NVIDIA GPU Display Driver for Windows and Linux contains
a vulnerability in the kernel mode layer (nvlddmkm.sys) handler for
DxgkDdiEscape, where an unprivileged regular user can access
administrator- privileged registers, which may lead to denial of
service, information disclosure, and data tampering.

CVE-2022-28185 NVIDIA GPU Display Driver for Windows and Linux contains
a vulnerability in the ECC layer, where an unprivileged regular user can
cause an out-of-bounds write, which may lead to denial of service and
data tampering.

CVE-2022-28191  NVIDIA vGPU software contains a vulnerability in the
Virtual GPU Manager (nvidia.ko), where uncontrolled resource consumption
can be triggered by an unprivileged regular user, which may lead to
denial of service.

CVE-2022-28192  NVIDIA vGPU software contains a vulnerability in the
Virtual GPU Manager (nvidia.ko), where it may lead to a use-after-free,
which in turn may cause denial of service. This attack is complex to
carry out because the attacker needs to have control over freeing some
host side resources out of sequence, which requires elevated privileges.

Driver Branch   CVE IDs Addressed
R510 and R470   CVE-2022-28181, CVE-2022-28183, CVE-2022-28184, CVE-2022-28185, 
CVE-2022-28191, CVE-2022-28192
R450CVE-2022-28181, CVE-2022-28185, CVE-2022-28192
R390CVE-2022-28181, CVE-2022-28185

Andreas
--- End Message ---
--- Begin Message ---
Source: nvidia-graphics-drivers-legacy-390xx
Source-Version: 390.151-1~deb10u1
Done: Andreas Beckmann 

We believe that the bug you reported is fixed in the latest version of
nvidia-graphics-drivers-legacy-390xx, which is due to be 

Bug#1011142: marked as done (nvidia-graphics-drivers-legacy-390xx: CVE-2022-28181, CVE-2022-28185)

[Debian Bug Tracking System]

Your message dated Sun, 19 Jun 2022 17:02:08 +
with message-id 
and subject line Bug#1011142: fixed in nvidia-graphics-drivers-legacy-390xx 
390.151-1~deb11u1
has caused the Debian Bug report #1011142,
regarding nvidia-graphics-drivers-legacy-390xx: CVE-2022-28181, CVE-2022-28185
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.)


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

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

CVE-2022-28181  NVIDIA GPU Display Driver for Windows and Linux contains
a vulnerability in the kernel mode layer, where an unprivileged regular
user on the network can cause an out-of-bounds write through a specially
crafted shader, which may lead to code execution, denial of service,
escalation of privileges, information disclosure, and data tampering.
The scope of the impact may extend to other components.

CVE-2022-28183  NVIDIA GPU Display Driver for Windows and Linux contains
a vulnerability in the kernel mode layer, where an unprivileged regular
user can cause an out-of-bounds read, which may lead to denial of
service and information disclosure.

CVE-2022-28184  NVIDIA GPU Display Driver for Windows and Linux contains
a vulnerability in the kernel mode layer (nvlddmkm.sys) handler for
DxgkDdiEscape, where an unprivileged regular user can access
administrator- privileged registers, which may lead to denial of
service, information disclosure, and data tampering.

CVE-2022-28185 NVIDIA GPU Display Driver for Windows and Linux contains
a vulnerability in the ECC layer, where an unprivileged regular user can
cause an out-of-bounds write, which may lead to denial of service and
data tampering.

CVE-2022-28191  NVIDIA vGPU software contains a vulnerability in the
Virtual GPU Manager (nvidia.ko), where uncontrolled resource consumption
can be triggered by an unprivileged regular user, which may lead to
denial of service.

CVE-2022-28192  NVIDIA vGPU software contains a vulnerability in the
Virtual GPU Manager (nvidia.ko), where it may lead to a use-after-free,
which in turn may cause denial of service. This attack is complex to
carry out because the attacker needs to have control over freeing some
host side resources out of sequence, which requires elevated privileges.

Driver Branch   CVE IDs Addressed
R510 and R470   CVE-2022-28181, CVE-2022-28183, CVE-2022-28184, CVE-2022-28185, 
CVE-2022-28191, CVE-2022-28192
R450CVE-2022-28181, CVE-2022-28185, CVE-2022-28192
R390CVE-2022-28181, CVE-2022-28185

Andreas
--- End Message ---
--- Begin Message ---
Source: nvidia-graphics-drivers-legacy-390xx
Source-Version: 390.151-1~deb11u1
Done: Andreas Beckmann 

We believe that the bug you reported is fixed in the latest version of
nvidia-graphics-drivers-legacy-390xx, which is due to be 

Bug#1010230: marked as done (nvidia-graphics-drivers-legacy-390xx: spurious module build failure in autopkgtest on armhf)

[Debian Bug Tracking System]

Your message dated Sun, 19 Jun 2022 17:02:24 +
with message-id 
and subject line Bug#1010230: fixed in nvidia-graphics-drivers-legacy-390xx 
390.151-1~deb10u1
has caused the Debian Bug report #1010230,
regarding nvidia-graphics-drivers-legacy-390xx: spurious module build failure 
in autopkgtest on armhf
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.)


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

Source: nvidia-graphics-drivers-legacy-390xx
Version: 390.147-4
Severity: serious
X-Debbugs-CC: d...@packages.debian.org
Tags: sid bookworm
User: debian...@lists.debian.org
Usertags: needs-update
Control: affects -1 src:dkms

Dear maintainer(s),

With a recent upload of dkms the autopkgtest of 
nvidia-graphics-drivers-legacy-390xx fails in testing when that 
autopkgtest is run with the binary packages of dkms from unstable on 
armhf. It passes when run with only packages from testing. In tabular form:


   passfail
dkms   from testing3.0.3-1
nvidia-graphics-drivers-legacy-390xx   from testing390.147-4
all others from testingfrom testing

I copied some of the output at the bottom of this report. As I 
understand it, the dkms changes extend the testing drastically and show 
a real issue.


Currently this regression is blocking the migration of dkms to testing 
[1]. Of course, dkms shouldn't just break your autopkgtest (or even 
worse, your package), but it seems to me that the change in dkms was 
intended and your package needs to update to the new situation.


If this is a real problem in your package (and not only in your 
autopkgtest), the right binary package(s) from dkms should really add a 
versioned Breaks on the unfixed version of (one of your) package(s). 
Note: the Breaks is nice even if the issue is only in the autopkgtest as 
it helps the migration software to figure out the right versions to 
combine in the tests.


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

Paul

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

https://ci.debian.net/data/autopkgtest/testing/armhf/n/nvidia-graphics-drivers-legacy-390xx/21184047/log.gz

At top level:
/var/lib/dkms/nvidia-legacy-390xx/390.147/build/nvidia/os-interface.c:999:5: 
error: unknown type name ‘NV_WORKQUEUE_DATA_T’; did you mean 
‘NV_WORKQUEUE_FLUSH’?

  999 | NV_WORKQUEUE_DATA_T *data
  | ^~~
  | NV_WORKQUEUE_FLUSH
/var/lib/dkms/nvidia-legacy-390xx/390.147/build/nvidia/nv-vm.c: In 
function ‘nv_flush_caches’:
/var/lib/dkms/nvidia-legacy-390xx/390.147/build/nvidia/nv-vm.c:225:5: 
error: implicit declaration of function ‘NV_ON_EACH_CPU’ 
[-Werror=implicit-function-declaration]

  225 | NV_ON_EACH_CPU(nv_flush_cache, NULL);
  | ^~
cc1: some warnings being treated as errors
make[3]: *** 
[/usr/src/linux-headers-5.17.0-1-common/scripts/Makefile.build:293: 
/var/lib/dkms/nvidia-legacy-390xx/390.147/build/nvidia/nv-vm.o] Error 1
/var/lib/dkms/nvidia-legacy-390xx/390.147/build/nvidia/os-interface.c: 
In function ‘os_queue_work_item’:
/var/lib/dkms/nvidia-legacy-390xx/390.147/build/nvidia/os-interface.c:1031:5: 
error: implicit declaration of function ‘NV_WORKQUEUE_INIT’; did you 
mean ‘NV_WORKQUEUE_FLUSH’? [-Werror=implicit-function-declaration]

 1031 | NV_WORKQUEUE_INIT(>task, os_execute_work_item,
  | ^
  | NV_WORKQUEUE_FLUSH
/var/lib/dkms/nvidia-legacy-390xx/390.147/build/nvidia/os-interface.c:1031:36: 
error: ‘os_execute_work_item’ undeclared (first use in this function); 
did you mean ‘rm_execute_work_item’?

 1031 | NV_WORKQUEUE_INIT(>task, os_execute_work_item,
  |^~~~
  |rm_execute_work_item
In file included from 
/var/lib/dkms/nvidia-legacy-390xx/390.147/build/nvidia/os-interface.c:15:
/var/lib/dkms/nvidia-legacy-390xx/390.147/build/nvidia/os-interface.c: 
In function ‘os_is_efi_enabled’:
/var/lib/dkms/nvidia-legacy-390xx/390.147/build/common/inc/nv-linux.h:224:26: 
warning: returning ‘bool (*)(int)’ {aka ‘_Bool (*)(int)’} from a 
function with return type ‘NvS32’ {aka ‘int’} makes integer from pointer 
without a cast [-Wint-conversion]

  224 | #define NV_EFI_ENABLED() efi_enabled
  |  ^~~

Bug#1010230: marked as done (nvidia-graphics-drivers-legacy-390xx: spurious module build failure in autopkgtest on armhf)

[Debian Bug Tracking System]

Your message dated Sun, 19 Jun 2022 17:02:08 +
with message-id 
and subject line Bug#1010230: fixed in nvidia-graphics-drivers-legacy-390xx 
390.151-1~deb11u1
has caused the Debian Bug report #1010230,
regarding nvidia-graphics-drivers-legacy-390xx: spurious module build failure 
in autopkgtest on armhf
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.)


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

Source: nvidia-graphics-drivers-legacy-390xx
Version: 390.147-4
Severity: serious
X-Debbugs-CC: d...@packages.debian.org
Tags: sid bookworm
User: debian...@lists.debian.org
Usertags: needs-update
Control: affects -1 src:dkms

Dear maintainer(s),

With a recent upload of dkms the autopkgtest of 
nvidia-graphics-drivers-legacy-390xx fails in testing when that 
autopkgtest is run with the binary packages of dkms from unstable on 
armhf. It passes when run with only packages from testing. In tabular form:


   passfail
dkms   from testing3.0.3-1
nvidia-graphics-drivers-legacy-390xx   from testing390.147-4
all others from testingfrom testing

I copied some of the output at the bottom of this report. As I 
understand it, the dkms changes extend the testing drastically and show 
a real issue.


Currently this regression is blocking the migration of dkms to testing 
[1]. Of course, dkms shouldn't just break your autopkgtest (or even 
worse, your package), but it seems to me that the change in dkms was 
intended and your package needs to update to the new situation.


If this is a real problem in your package (and not only in your 
autopkgtest), the right binary package(s) from dkms should really add a 
versioned Breaks on the unfixed version of (one of your) package(s). 
Note: the Breaks is nice even if the issue is only in the autopkgtest as 
it helps the migration software to figure out the right versions to 
combine in the tests.


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

Paul

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

https://ci.debian.net/data/autopkgtest/testing/armhf/n/nvidia-graphics-drivers-legacy-390xx/21184047/log.gz

At top level:
/var/lib/dkms/nvidia-legacy-390xx/390.147/build/nvidia/os-interface.c:999:5: 
error: unknown type name ‘NV_WORKQUEUE_DATA_T’; did you mean 
‘NV_WORKQUEUE_FLUSH’?

  999 | NV_WORKQUEUE_DATA_T *data
  | ^~~
  | NV_WORKQUEUE_FLUSH
/var/lib/dkms/nvidia-legacy-390xx/390.147/build/nvidia/nv-vm.c: In 
function ‘nv_flush_caches’:
/var/lib/dkms/nvidia-legacy-390xx/390.147/build/nvidia/nv-vm.c:225:5: 
error: implicit declaration of function ‘NV_ON_EACH_CPU’ 
[-Werror=implicit-function-declaration]

  225 | NV_ON_EACH_CPU(nv_flush_cache, NULL);
  | ^~
cc1: some warnings being treated as errors
make[3]: *** 
[/usr/src/linux-headers-5.17.0-1-common/scripts/Makefile.build:293: 
/var/lib/dkms/nvidia-legacy-390xx/390.147/build/nvidia/nv-vm.o] Error 1
/var/lib/dkms/nvidia-legacy-390xx/390.147/build/nvidia/os-interface.c: 
In function ‘os_queue_work_item’:
/var/lib/dkms/nvidia-legacy-390xx/390.147/build/nvidia/os-interface.c:1031:5: 
error: implicit declaration of function ‘NV_WORKQUEUE_INIT’; did you 
mean ‘NV_WORKQUEUE_FLUSH’? [-Werror=implicit-function-declaration]

 1031 | NV_WORKQUEUE_INIT(>task, os_execute_work_item,
  | ^
  | NV_WORKQUEUE_FLUSH
/var/lib/dkms/nvidia-legacy-390xx/390.147/build/nvidia/os-interface.c:1031:36: 
error: ‘os_execute_work_item’ undeclared (first use in this function); 
did you mean ‘rm_execute_work_item’?

 1031 | NV_WORKQUEUE_INIT(>task, os_execute_work_item,
  |^~~~
  |rm_execute_work_item
In file included from 
/var/lib/dkms/nvidia-legacy-390xx/390.147/build/nvidia/os-interface.c:15:
/var/lib/dkms/nvidia-legacy-390xx/390.147/build/nvidia/os-interface.c: 
In function ‘os_is_efi_enabled’:
/var/lib/dkms/nvidia-legacy-390xx/390.147/build/common/inc/nv-linux.h:224:26: 
warning: returning ‘bool (*)(int)’ {aka ‘_Bool (*)(int)’} from a 
function with return type ‘NvS32’ {aka ‘int’} makes integer from pointer 
without a cast [-Wint-conversion]

  224 | #define NV_EFI_ENABLED() efi_enabled
  |  ^~~

Bug#1012703: marked as done (vtk9: FTBFS with NetCDF 4.9.0 (error: expected identifier or '(' before numeric constant))

[Debian Bug Tracking System]

Your message dated Sun, 19 Jun 2022 14:44:48 +
with message-id 
and subject line Bug#1012703: fixed in vtk9 9.1.0+really9.1.0+dfsg2-4
has caused the Debian Bug report #1012703,
regarding vtk9: FTBFS with NetCDF 4.9.0 (error: expected identifier or '(' 
before numeric constant)
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.)


-- 
1012703: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1012703
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: vtk9
Version: 9.1.0+really9.1.0+dfsg2-3
Severity: serious
Tags: ftbfs

Dear Maintainer,

Your package FTBFS with NetCDF 4.9.0:

[  2%] Building C object 
ThirdParty/exodusII/vtkexodusII/CMakeFiles/exodusII.dir/src/ex_utils.c.o
cd 
/build/vtk9-9.1.0+really9.1.0+dfsg2/debian/build/ThirdParty/exodusII/vtkexodusII
 && /usr/bin/mpicc -DH5_BUILT_AS_DYNAMIC_LIB -DMPICH_SKIP_MPICXX 
-DMPI_NO_CPPBIND -DOMPI_SKIP_MPICXX -DVTK_IN_VTK -DVTK_MODULE_ENABLE_VTK_mpi=1 
-D_MPICC_
H -DexoIIc_EXPORTS -DexodusII_EXPORTS 
-I/build/vtk9-9.1.0+really9.1.0+dfsg2/debian/build/ThirdParty/exodusII/vtkexodusII
 -I/build/vtk9-9.1.0+really9.1.0+dfsg2/ThirdParty/exodusII/vtkexodusII 
-I/build/vtk9-9.1.0+really9.1.0+dfsg2/ThirdPa
rty/exodusII/vtkexodusII/include 
-I/build/vtk9-9.1.0+really9.1.0+dfsg2/debian/build/ThirdParty/exodusII/vtkexodusII/include
 -isystem /build/vtk9-9.1.0+really9.1.0+dfsg2/debian/build/ThirdParty/exodusII 
-isystem /build/vtk9-9.1.0+really9
.1.0+dfsg2/ThirdParty/exodusII -isystem 
/build/vtk9-9.1.0+really9.1.0+dfsg2/debian/build/ThirdParty/hdf5 -isystem 
/build/vtk9-9.1.0+really9.1.0+dfsg2/ThirdParty/hdf5 -isystem 
/usr/include/hdf5/serial -isystem /build/vtk9-9.1.0+really9.1
.0+dfsg2/debian/build/ThirdParty/netcdf -isystem 
/build/vtk9-9.1.0+really9.1.0+dfsg2/ThirdParty/netcdf -isystem 
/build/vtk9-9.1.0+really9.1.0+dfsg2/debian/build/Utilities/MPI -isystem 
/build/vtk9-9.1.0+really9.1.0+dfsg2/Utilities/MPI -g
 -O2 -ffile-prefix-map=/build/vtk9-9.1.0+really9.1.0+dfsg2=. 
-fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
-D_FORTIFY_SOURCE=2  -O2 -g -DNDEBUG -fPIC -std=gnu99 -MD -MT 
ThirdParty/exodusII/vtkexodusII/CMakeFiles/
exodusII.dir/src/ex_utils.c.o -MF CMakeFiles/exodusII.dir/src/ex_utils.c.o.d -o 
CMakeFiles/exodusII.dir/src/ex_utils.c.o -c 
/build/vtk9-9.1.0+really9.1.0+dfsg2/ThirdParty/exodusII/vtkexodusII/src/ex_utils.c
In file included from 
/build/vtk9-9.1.0+really9.1.0+dfsg2/debian/build/ThirdParty/netcdf/vtk_netcdf.h:22,
 from 
/build/vtk9-9.1.0+really9.1.0+dfsg2/ThirdParty/exodusII/vtkexodusII/include/exodusII.h:22,
 from 
/build/vtk9-9.1.0+really9.1.0+dfsg2/ThirdParty/exodusII/vtkexodusII/src/ex_utils.c:20:
/build/vtk9-9.1.0+really9.1.0+dfsg2/ThirdParty/exodusII/vtkexodusII/src/ex_utils.c:
 In function 'vtkexodusII_ex__compress_variable':
/build/vtk9-9.1.0+really9.1.0+dfsg2/ThirdParty/exodusII/vtkexodusII/src/ex_utils.c:1773:19:
 error: expected identifier or '(' before numeric constant
 1773 | const int NC_SZIP_NN = 32;  /* Selects nearest neighbor 
coding method for szip. */
  |   ^~

In NetCDF 4.9.0 NC_SZIP_NN and other are defined in netcdf.h:

 #define NC_SZIP_NN 32 /**< SZIP NN option mask. */

paraview has the same issue: #1012663.

Kind Regards,

Bas
--- End Message ---
--- Begin Message ---
Source: vtk9
Source-Version: 9.1.0+really9.1.0+dfsg2-4
Done: Anton Gladky 

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

Debian distribution maintenance software
pp.
Anton Gladky  (supplier of updated vtk9 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, 19 Jun 2022 16:25:33 +0200
Source: vtk9
Architecture: source
Version: 9.1.0+really9.1.0+dfsg2-4
Distribution: unstable
Urgency: medium
Maintainer: Debian Science Team 

Changed-By: Anton Gladky 
Closes: 1012703
Changes:
 vtk9 (9.1.0+really9.1.0+dfsg2-4) unstable; urgency=medium
 .
   * [b05b21f] Fix FTBFS against NETCDF>4.9.0. (Closes: #1012703)
Checksums-Sha1:
 9f314bc2ed88310e288e81eaf944a7eb537f5e98 3846 

Processed: Re: tagging 1012326, tagging 1012690, tagging 1012464, tagging 1001317, tagging 1012221, tagging 1011807 ...

[Debian Bug Tracking System]

Processing control commands:

> notfound 1003353 2.114.0
Bug #1003353 [lintian] lintian: Cannot use brackets in suppression rules?
No longer marked as found in versions lintian/2.114.0.

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

Bug#1003353: tagging 1012326, tagging 1012690, tagging 1012464, tagging 1001317, tagging 1012221, tagging 1011807 ...

[Axel Beckert]

Control: notfound 1003353 2.114.0

Hi Andreas,

Andreas Beckmann wrote:
> found 1003353 2.114.0

please explain what makes you think that this issue is present in
lintian 2.114.0 as currently in Debian Unstable.

The submitter clearly said he ran into it when he bumped his lintian
copy to git HEAD.

And as far as I can see that problem is only present if Lintian uses
Text::Glob for evaluating wildcards in overrides and that got
introduced 32 commits _AFTER_ the 2.114.0 release:

  commit 139009d5a54225ebff4509ec37b979cb898c17fe
  Author: Felix Lechner 
  Date:   Wed Dec 1 21:46:24 2021 -0800

Use Text::Glob to match hint contexts with override patterns.

Replaces a trusted homegrown routine.

Gbp-Dch: ignore

(No idea why this was marked "Gbp-Dch: Ignore" as it has quite some
impact, also on dependencies and build-dependencies. *grrr*)

And:

  ~/lintian/lintian → git describe 139009d5a54225ebff4509ec37b979cb898c17fe
  2.114.0-32-g139009d5a
  ^^

Which is the reason why I marked this bug report as NOT being found in
2.114.0 a few days ago. (And now again.)

So please refrain from marking this specific bug report as found in
2.114.0 again unless you have a really good reason to do so. Thanks in
advance!

Regards, Axel
-- 
 ,''`.  |  Axel Beckert , https://people.debian.org/~abe/
: :' :  |  Debian Developer, ftp.ch.debian.org Admin
`. `'   |  4096R: 2517 B724 C5F6 CA99 5329  6E61 2FF9 CD59 6126 16B5
  `-|  1024D: F067 EA27 26B9 C3FC 1486  202E C09E 1D89 9593 0EDE


signature.asc
Description: PGP signature

Bug#1013193: closing 1013193

[Jochen Sprickerhof]

close 1013193 1.16.0-4
thanks

Processed: closing 1013193

[Debian Bug Tracking System]

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

> close 1013193 1.16.0-4
Bug #1013193 [ros-image-proc] ros-image-proc: missing Breaks+Replaces: 
libimage-proc-dev (<< 1.16.0-3)
Marked as fixed in versions ros-image-pipeline/1.16.0-4.
Bug #1013193 [ros-image-proc] ros-image-proc: missing Breaks+Replaces: 
libimage-proc-dev (<< 1.16.0-3)
Marked Bug as done
> thanks
Stopping processing here.

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

Bug#1008415: libnih: FTBFS: dh_auto_test: error: make -j8 check VERBOSE=1 returned exit code 2

[Axel Beckert]

Hi Marius,

Marius Gripsgard wrote:
> libnih has been removed as dependency for lomiri-donwload-manager
> for a good while upstream [0]

Ah, nice!

> but has not had a release with this in it yet. So I make a new
> released lomiri-download-manager 0.1.1 with libnih removed as dep,
> and uploaded this to unstable.

Yay! Thanks a lot.

> So nih can be removed IMO.

Done so now: https://bugs.debian.org/1013225

Regards, Axel
-- 
 ,''`.  |  Axel Beckert , https://people.debian.org/~abe/
: :' :  |  Debian Developer, ftp.ch.debian.org Admin
`. `'   |  4096R: 2517 B724 C5F6 CA99 5329  6E61 2FF9 CD59 6126 16B5
  `-|  1024D: F067 EA27 26B9 C3FC 1486  202E C09E 1D89 9593 0EDE


signature.asc
Description: PGP signature

Bug#1012613: nftables: upgrade stops but does not start service

[Jeremy Sowden]

On 2022-06-19, at 13:48:59 +0200, Arturo Borrero Gonzalez wrote:
> On Fri, 10 Jun 2022 12:21:37 +0200 Christian Göttsche wrote:
> > Package: nftables
> > Version: 1.0.4-1
> > Severity: serious
> >
> > Dear Maintainer,
> >
> > upgrades of nftables stop the service but do not start it (even if the
> > service is actually enabled).
> > This can lead to lockouts, e.g. when using special rules for ssh access.
> >
> >
> > nft.preinst:
> >
> > #!/bin/sh
> > set -e
> > # Automatically added by dh_installsystemd/13.7.1
> > if [ -z "${DPKG_ROOT:-}" ] && [ "$1" = upgrade ] && [ -d 
> > /run/systemd/system ] ; then
> >deb-systemd-invoke stop 'nftables.service' >/dev/null || true
> > fi
> > # End automatically added section
> >
> >
> > nft.postinst:
> >
> > #!/bin/sh
> > set -e
> > # Automatically added by dh_installsystemd/13.7.1
> > if [ "$1" = "configure" ] || [ "$1" = "abort-upgrade" ] || [ "$1" = 
> > "abort-deconfigure" ] || [ "$1" = "abort-remove" ] ; then
> >if deb-systemd-helper debian-installed 'nftables.service'; then
> ># This will only remove masks created by d-s-h on package 
> > removal.
> >deb-systemd-helper unmask 'nftables.service' >/dev/null || 
> > true
> >
> >if deb-systemd-helper --quiet was-enabled 
> > 'nftables.service'; then
> ># Create new symlinks, if any.
> >deb-systemd-helper enable 'nftables.service' 
> > >/dev/null || true
> >fi
> >fi
> >
> ># Update the statefile to add new symlinks (if any), which need to 
> > be cleaned
> ># up on purge. Also remove old symlinks.
> >deb-systemd-helper update-state 'nftables.service' >/dev/null || true
> > fi
> > # End automatically added section
>
> I confirmed this can be a problem:
>
> [...]
>
> @Alberto, @Jeremy,
>
> It seems to me like we need to play with the dh_installsystemd
> --no-restart-after-upgrade option, but don't have time to figure out the
> right logic.
>
> I'm currently unable to handle this. Could you please take a look?

Yup.

J.


signature.asc
Description: PGP signature

Bug#1013223: bird2: FTBFS on arm64: make[1]: *** [Makefile:180: obj/lib/bitmap_test.ok] Error 1

[Sebastian Ramacher]

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

https://buildd.debian.org/status/fetch.php?pkg=bird2=arm64=2.0.9-3=1649868353=0


obj/lib/bitmap_test: t_hmap_set_clear_fill 5.023173111s  [FAIL] 
obj/lib/bitmap_test 6.241085926s [FAIL] 
make[1]: *** [Makefile:180: obj/lib/bitmap_test.ok] Error 1
make[1]: *** Waiting for unfinished jobs
In function ‘memcpy’,
inlined from ‘nl_add_attr’ at sysdep/linux/netlink.c:598:5,
inlined from ‘nl_add_attr_ip6’ at sysdep/linux/netlink.c:638:3,
inlined from ‘nl_send_route’ at sysdep/linux/netlink.c:1381:7:
/usr/include/aarch64-linux-gnu/bits/string_fortified.h:29:10: warning: writing 
16 bytes into a region of size 12 [-Wstringop-overflow=]
   29 |   return __builtin___memcpy_chk (__dest, __src, __len,
  |  ^
sysdep/linux/netlink.c: In function ‘nl_send_route’:
sysdep/linux/netlink.c:1338:21: note: at offset [4, 16] into destination object 
‘h’ of size 16
 1338 | struct nlmsghdr h;
  | ^
In function ‘memcpy’,
inlined from ‘nl_add_attr’ at sysdep/linux/netlink.c:598:5,
inlined from ‘nl_add_attr_ip6’ at sysdep/linux/netlink.c:638:3,
inlined from ‘nl_add_attr_ipa’ at sysdep/linux/netlink.c:647:5,
inlined from ‘nl_send_route’ at sysdep/linux/netlink.c:1423:5:
/usr/include/aarch64-linux-gnu/bits/string_fortified.h:29:10: warning: writing 
16 bytes into a region of size 12 [-Wstringop-overflow=]
   29 |   return __builtin___memcpy_chk (__dest, __src, __len,
  |  ^
sysdep/linux/netlink.c: In function ‘nl_send_route’:
sysdep/linux/netlink.c:1338:21: note: at offset [4, 16] into destination object 
‘h’ of size 16
 1338 | struct nlmsghdr h;
  | ^
In function ‘memcpy’,
inlined from ‘nl_add_attr’ at sysdep/linux/netlink.c:598:5,
inlined from ‘nl_add_attr_ip6’ at sysdep/linux/netlink.c:638:3,
inlined from ‘nl_send_route’ at sysdep/linux/netlink.c:1381:7:
/usr/include/aarch64-linux-gnu/bits/string_fortified.h:29:10: warning: writing 
16 bytes into a region of size 12 [-Wstringop-overflow=]
   29 |   return __builtin___memcpy_chk (__dest, __src, __len,
  |  ^
sysdep/linux/netlink.c: In function ‘nl_send_route’:
sysdep/linux/netlink.c:1338:21: note: at offset [4, 16] into destination object 
‘h’ of size 16
 1338 | struct nlmsghdr h;
  | ^
In function ‘memcpy’,
inlined from ‘nl_add_attr’ at sysdep/linux/netlink.c:598:5,
inlined from ‘nl_add_attr_ip6’ at sysdep/linux/netlink.c:638:3,
inlined from ‘nl_add_attr_ipa’ at sysdep/linux/netlink.c:647:5,
inlined from ‘nl_send_route’ at sysdep/linux/netlink.c:1423:5:
/usr/include/aarch64-linux-gnu/bits/string_fortified.h:29:10: warning: writing 
16 bytes into a region of size 12 [-Wstringop-overflow=]
   29 |   return __builtin___memcpy_chk (__dest, __src, __len,
  |  ^
sysdep/linux/netlink.c: In function ‘nl_send_route’:
sysdep/linux/netlink.c:1338:21: note: at offset [4, 16] into destination object 
‘h’ of size 16
 1338 | struct nlmsghdr h;
  | ^
In function ‘memcpy’,
inlined from ‘nl_add_attr’ at sysdep/linux/netlink.c:598:5,
inlined from ‘nl_add_attr_ip6’ at sysdep/linux/netlink.c:638:3,
inlined from ‘nl_send_route’ at sysdep/linux/netlink.c:1381:7:
/usr/include/aarch64-linux-gnu/bits/string_fortified.h:29:10: warning: writing 
16 bytes into a region of size 12 [-Wstringop-overflow=]
   29 |   return __builtin___memcpy_chk (__dest, __src, __len,
  |  ^
sysdep/linux/netlink.c: In function ‘nl_send_route’:
sysdep/linux/netlink.c:1338:21: note: at offset [4, 16] into destination object 
‘h’ of size 16
 1338 | struct nlmsghdr h;
  | ^
In function ‘memcpy’,
inlined from ‘nl_add_attr’ at sysdep/linux/netlink.c:598:5,
inlined from ‘nl_add_attr_ip6’ at sysdep/linux/netlink.c:638:3,
inlined from ‘nl_add_attr_ipa’ at sysdep/linux/netlink.c:647:5,
inlined from ‘nl_send_route’ at sysdep/linux/netlink.c:1423:5:
/usr/include/aarch64-linux-gnu/bits/string_fortified.h:29:10: warning: writing 
16 bytes into a region of size 12 [-Wstringop-overflow=]
   29 |   return __builtin___memcpy_chk (__dest, __src, __len,
  |  ^
sysdep/linux/netlink.c: In function ‘nl_send_route’:
sysdep/linux/netlink.c:1338:21: note: at offset [4, 16] into destination object 
‘h’ of size 16
 1338 | struct nlmsghdr h;
  | ^
make[1]: Leaving directory '/<>'
dh_auto_test: error: make -j8 test VERBOSE=1 returned exit code 2


Cheers
-- 
Sebastian Ramacher

Bug#1012613: nftables: upgrade stops but does not start service

[Arturo Borrero Gonzalez]

On Fri, 10 Jun 2022 12:21:37 +0200 =?UTF-8?Q?Christian_G=C3=B6ttsche?= 
 wrote:

Package: nftables
Version: 1.0.4-1
Severity: serious

Dear Maintainer,

upgrades of nftables stop the service but do not start it (even if the
service is actually enabled).
This can lead to lockouts, e.g. when using special rules for ssh access.


nft.preinst:

#!/bin/sh
set -e
# Automatically added by dh_installsystemd/13.7.1
if [ -z "${DPKG_ROOT:-}" ] && [ "$1" = upgrade ] && [ -d
/run/systemd/system ] ; then
   deb-systemd-invoke stop 'nftables.service' >/dev/null || true
fi
# End automatically added section


nft.postinst:

#!/bin/sh
set -e
# Automatically added by dh_installsystemd/13.7.1
if [ "$1" = "configure" ] || [ "$1" = "abort-upgrade" ] || [ "$1" =
"abort-deconfigure" ] || [ "$1" = "abort-remove" ] ; then
   if deb-systemd-helper debian-installed 'nftables.service'; then
   # This will only remove masks created by d-s-h on
package removal.
   deb-systemd-helper unmask 'nftables.service' >/dev/null || true

   if deb-systemd-helper --quiet was-enabled
'nftables.service'; then
   # Create new symlinks, if any.
   deb-systemd-helper enable 'nftables.service'
>/dev/null || true
   fi
   fi

   # Update the statefile to add new symlinks (if any), which need
to be cleaned
   # up on purge. Also remove old symlinks.
   deb-systemd-helper update-state 'nftables.service' >/dev/null || true
fi
# End automatically added section




I confirmed this can be a problem:

=== 8< ===
⌂0.65 arturo@nostromo:~ $ apt-cache policy nftables
nftables:
  Installed: 1.0.2-1
  Candidate: 1.0.4-1
  Version table:
 1.0.4-1 500
500 http://deb.debian.org/debian sid/main amd64 Packages
 *** 1.0.2-1 500
500 http://deb.debian.org/debian testing/main amd64 Packages
100 /var/lib/dpkg/status
⌂0.68 arturo@nostromo:~ $ sudo systemctl status nftables
● nftables.service - nftables
 Loaded: loaded (/lib/systemd/system/nftables.service; disabled; 
vendor preset: enabled)

 Active: active (exited) since Sun 2022-06-19 13:38:11 CEST; 51s ago
   Docs: man:nft(8)
 http://wiki.nftables.org
Process: 5537 ExecStart=/usr/sbin/nft -f /etc/nftables.conf 
(code=exited, status=0/SUCCESS)

   Main PID: 5537 (code=exited, status=0/SUCCESS)
CPU: 13ms

Jun 19 13:38:11 nostromo systemd[1]: Starting nftables...
Jun 19 13:38:11 nostromo systemd[1]: Finished nftables.
⌂0.70 arturo@nostromo:~ $ sudo nft list ruleset
table inet filter {
chain input {
type filter hook input priority filter; policy accept;
iif "lo" accept
ct state established,related accept
tcp dport 22 ct state new accept
		ip6 nexthdr ipv6-icmp icmpv6 type { nd-router-advert, 
nd-neighbor-solicit, nd-neighbor-advert } accept

counter packets 6 bytes 898 drop
}
}
⌂0.65 arturo@nostromo:~ $ sudo aptitude install nftables
The following packages will be upgraded:
  libnftables1 nftables
2 packages upgraded, 0 newly installed, 0 to remove and 754 not upgraded.
Need to get 365 kB of archives. After unpacking 27.6 kB will be used.
Do you want to continue? [Y/n/?] Y
Get: 1 http://deb.debian.org/debian sid/main amd64 nftables amd64 
1.0.4-1 [71.9 kB]
Get: 2 http://deb.debian.org/debian sid/main amd64 libnftables1 amd64 
1.0.4-1 [294 kB]

Fetched 365 kB in 0s (4,064 kB/s)
Reading changelogs... Done
(Reading database ... 273043 files and directories currently installed.)
Preparing to unpack .../nftables_1.0.4-1_amd64.deb ...
Unpacking nftables (1.0.4-1) over (1.0.2-1) ...
Preparing to unpack .../libnftables1_1.0.4-1_amd64.deb ...
Unpacking libnftables1:amd64 (1.0.4-1) over (1.0.2-1) ...
Setting up libnftables1:amd64 (1.0.4-1) ...
Setting up nftables (1.0.4-1) ...
Processing triggers for man-db (2.10.2-1) ...
Processing triggers for libc-bin (2.33-7) ...

Current status: 754 (-2) upgradable.
⌂0.78 arturo@nostromo:~ $ sudo nft list ruleset
⌂0.78 arturo@nostromo:~ $ sudo systemctl status nftables
○ nftables.service - nftables
 Loaded: loaded (/lib/systemd/system/nftables.service; disabled; 
vendor preset: enabled)

 Active: inactive (dead)
   Docs: man:nft(8)
 http://wiki.nftables.org

Jun 19 13:38:11 nostromo systemd[1]: Starting nftables...
Jun 19 13:38:11 nostromo systemd[1]: Finished nftables.
Jun 19 13:39:13 nostromo systemd[1]: Stopping nftables...
Jun 19 13:39:13 nostromo systemd[1]: nftables.service: Deactivated 
successfully.

Jun 19 13:39:13 nostromo systemd[1]: Stopped nftables.
=== 8< ===

@Alberto, @Jeremy,

It seems to me like we need to play with the dh_installsystemd 
--no-restart-after-upgrade option, but don't have time to figure out the 
right logic.


I'm currently unable to handle this. Could you please take a look?

regards.

Processed: bug 1012663 is forwarded to https://gitlab.kitware.com/paraview/paraview/-/issues/21442

[Debian Bug Tracking System]

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

> forwarded 1012663 https://gitlab.kitware.com/paraview/paraview/-/issues/21442
Bug #1012663 [src:paraview] paraview: FTBFS in unstable (error: expected 
identifier or ‘(’ before numeric constant)
Set Bug forwarded-to-address to 
'https://gitlab.kitware.com/paraview/paraview/-/issues/21442'.
> thanks
Stopping processing here.

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

Processed (with 1 error): Re: paraview: FTBFS in unstable (error: expected identifier or ‘(’ before numeric constant)

[Debian Bug Tracking System]

Processing control commands:

> tags -1 upstream patch
Bug #1012663 [src:paraview] paraview: FTBFS in unstable (error: expected 
identifier or ‘(’ before numeric constant)
Added tag(s) patch and upstream.
> forwarded -1
Unknown command or malformed arguments to command.


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

Bug#1012663: paraview: FTBFS in unstable (error: expected identifier or ‘(’ before numeric constant)

[Sebastiaan Couwenberg]

Control: tags -1 upstream patch
Control: forwarded -1 
https://gitlab.kitware.com/paraview/paraview/-/issues/21442


The attached patch resolves the issue by renaming the conflicting variable.

Kind Regards,

Bas

--
 GPG Key ID: 4096R/6750F10AE88D4AF1
Fingerprint: 8182 DE41 7056 408D 6146  50D1 6750 F10A E88D 4AF1Description: Fix FTBFS with NetCDF 4.9.0.
Author: Bas Couwenberg 
Bug-Debian: https://bugs.debian.org/1012663
Forwarded: https://gitlab.kitware.com/paraview/paraview/-/issues/21442

--- a/VTK/ThirdParty/exodusII/vtkexodusII/src/ex_utils.c
+++ b/VTK/ThirdParty/exodusII/vtkexodusII/src/ex_utils.c
@@ -1770,11 +1770,11 @@ void ex__compress_variable(int exoid, in
 */
 
 /* const int NC_SZIP_EC = 4; */ /* Selects entropy coding method for szip. */
-const int NC_SZIP_NN = 32;  /* Selects nearest neighbor coding method for szip. */
+const int NC_SZIP_NN_ = 32;  /* Selects nearest neighbor coding method for szip. */
 /* Even and between 4 and 32; typical values are 8, 10, 16, 32 */
 const int SZIP_PIXELS_PER_BLOCK =
 file->compression_level == 0 ? 32 : file->compression_level;
-nc_def_var_szip(exoid, varid, NC_SZIP_NN, SZIP_PIXELS_PER_BLOCK);
+nc_def_var_szip(exoid, varid, NC_SZIP_NN_, SZIP_PIXELS_PER_BLOCK);
 #else
 char errmsg[MAX_ERR_LENGTH];
 snprintf(errmsg, MAX_ERR_LENGTH,

Processed: Re: vtk9: FTBFS with NetCDF 4.9.0 (error: expected identifier or '(' before numeric constant)

[Debian Bug Tracking System]

Processing control commands:

> tags -1 upstream patch
Bug #1012703 [src:vtk9] vtk9: FTBFS with NetCDF 4.9.0 (error: expected 
identifier or '(' before numeric constant)
Added tag(s) upstream and patch.
> forwarded -1 https://gitlab.kitware.com/vtk/vtk/-/issues/18576
Bug #1012703 [src:vtk9] vtk9: FTBFS with NetCDF 4.9.0 (error: expected 
identifier or '(' before numeric constant)
Set Bug forwarded-to-address to 
'https://gitlab.kitware.com/vtk/vtk/-/issues/18576'.

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

Bug#1012703: vtk9: FTBFS with NetCDF 4.9.0 (error: expected identifier or '(' before numeric constant)

[Sebastiaan Couwenberg]

Control: tags -1 upstream patch
Control: forwarded -1 https://gitlab.kitware.com/vtk/vtk/-/issues/18576

The attached patch resolves the issue by renaming the conflicting variable.

Kind Regards,

Bas

--
 GPG Key ID: 4096R/6750F10AE88D4AF1
Fingerprint: 8182 DE41 7056 408D 6146  50D1 6750 F10A E88D 4AF1Description: Fix FTBFS with NetCDF 4.9.0.
Author: Bas Couwenberg 
Bug-Debian: https://bugs.debian.org/1012703
Forwarded: https://gitlab.kitware.com/vtk/vtk/-/issues/18576

--- a/ThirdParty/exodusII/vtkexodusII/src/ex_utils.c
+++ b/ThirdParty/exodusII/vtkexodusII/src/ex_utils.c
@@ -1770,11 +1770,11 @@ void ex__compress_variable(int exoid, in
 */
 
 /* const int NC_SZIP_EC = 4; */ /* Selects entropy coding method for szip. */
-const int NC_SZIP_NN = 32;  /* Selects nearest neighbor coding method for szip. */
+const int NC_SZIP_NN_ = 32;  /* Selects nearest neighbor coding method for szip. */
 /* Even and between 4 and 32; typical values are 8, 10, 16, 32 */
 const int SZIP_PIXELS_PER_BLOCK =
 file->compression_level == 0 ? 32 : file->compression_level;
-nc_def_var_szip(exoid, varid, NC_SZIP_NN, SZIP_PIXELS_PER_BLOCK);
+nc_def_var_szip(exoid, varid, NC_SZIP_NN_, SZIP_PIXELS_PER_BLOCK);
 #else
 char errmsg[MAX_ERR_LENGTH];
 snprintf(errmsg, MAX_ERR_LENGTH,

Bug#1012741: modprobe: ERROR: could not insert 'crc_itu_t': Key was rejected by service

[Ben Hutchings]

On Sat, 2022-06-18 at 16:21 +0200, Ben Hutchings wrote:
> On Thu, 2022-06-16 at 01:28 +0200, Ben Hutchings wrote:
> [...]
> 
> > linux-image-4.19.0-17-amd64 4.19.194-1 
> > lib/modules/4.19.0-17-amd64/kernel/drivers/dma/dw/dw_dmac_core.ko
> > linux-image-4.19.0-17-amd64 4.19.194-2 
> > lib/modules/4.19.0-17-amd64/kernel/drivers/dma/dw/dw_dmac_core.ko
> > linux-image-4.19.0-17-amd64 4.19.194-3 
> > lib/modules/4.19.0-17-amd64/kernel/drivers/dma/dw/dw_dmac_core.ko
> [...]
> > A significant pattern visible here is a short signature for the same
> > module in multiple consecutive versions, where the module may have
> > identical contents.  That implies that this is a reproducible issue for
> > certain inputs that cannot be worked around by re-running the signing
> > process.
> > 
> > However, I have *not* yet verified that all short signatures really are
> > invalid.
> 
> These module files are indeed identical, and their signatures are
> rejected by the kernel.
> 
> I'm now looking at whether the missing bytes are recoverable (e.g. are
> they always zeroes).
[...]

I wrote a script to try all possible byte values for 2 bytes before or
after the short signature.  For this particular file, none of them
producd a valid signature.  So the short signatures seem to be
corrupted in a more complex way.

In the mean time, we have another security update coming which might
not hit this bug again.  But there are 28,679 signed binaries across
the three architectures, so the probability is only about 65%.

Ben.

-- 
Ben Hutchings
The most exhausting thing in life is being insincere.
 - Anne Morrow Lindberg


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

Processed: closing 1013189

[Debian Bug Tracking System]

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

> close 1013189
Bug #1013189 [src:node-babel-polyfills] node-webpack: ftbfs Error: [BABEL]: 
Cannot find module '@babel/helper-define-polyfill-provider'
Marked Bug as done
> thanks
Stopping processing here.

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

Processed (with 1 error): Re: Fwd: Re: [Pkg-javascript-devel] Bug#1013218: rails: ftbfs SyntaxError: Unexpected token 'export'

[Debian Bug Tracking System]

Processing control commands:

> forwarded -1
Unknown command or malformed arguments to command.

> reassign -1 ruby-sprockets
Bug #1013218 [rails,ruby-coffee-script-source] rails: ftbfs SyntaxError: 
Unexpected token 'export'
Bug reassigned from package 'rails,ruby-coffee-script-source' to 
'ruby-sprockets'.
Ignoring request to alter found versions of bug #1013218 to the same values 
previously set
Ignoring request to alter fixed versions of bug #1013218 to the same values 
previously set
> affects -1 rails,ruby-cofee-source
Bug #1013218 [ruby-sprockets] rails: ftbfs SyntaxError: Unexpected token 
'export'
Added indication that 1013218 affects rails and ruby-cofee-source

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

Processed: Fwd: Re: [Pkg-javascript-devel] Bug#1013218: rails: ftbfs SyntaxError: Unexpected token 'export'

[Debian Bug Tracking System]

Processing control commands:

> reassign -1 rails,ruby-coffee-script-source
Bug #1013218 [rails,node-babel7] rails: ftbfs SyntaxError: Unexpected token 
'export'
Bug reassigned from package 'rails,node-babel7' to 
'rails,ruby-coffee-script-source'.
No longer marked as found in versions 2:6.1.4.6+dfsg-3.
Ignoring request to alter fixed versions of bug #1013218 to the same values 
previously set

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

Bug#1012600:

[Kevin P. Fleming]

I'm no expert, but since these packages are in 'contrib' I suspect
they don't have the ability to block package upgrades in 'main'.

On Sun, Jun 19, 2022 at 5:51 AM Chris Putnam  wrote:
>
> Apologies if this question is well-answered, but why isn't this package 
> holding back the kernel to 5.17? In my mind an "apt upgrade" should not have 
> pulled 5.18, especially when the net result may well be an unbootable system. 
> Surely there's some way to mark this package as broken in tandem with 5.18?
>
> I'm also quite surprised this wasn't caught in sid before it was pulled into 
> testing. Is there any form of testing for this package going on in sid?

Bug#1011990: marked as done (pappl: autopkgtest regression: fails on output to stderr)

[Debian Bug Tracking System]

Your message dated Sun, 19 Jun 2022 10:04:29 +
with message-id 
and subject line Bug#1011990: fixed in pappl 1.2.1-1
has caused the Debian Bug report #1011990,
regarding pappl: autopkgtest regression: fails on output to stderr
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.)


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

Source: pappl
Version: 1.2.0-1
Severity: serious
User: debian...@lists.debian.org
Usertags: regression

Dear maintainer(s),

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


   passfail
pappl  from testing1.2.0-1
all others from testingfrom testing

I copied some of the output at the bottom of this report. The test 
itself seems to pass, but there's output to stderr. Output to stderr is 
by default treated as failure by autopkgtest, unless the allow-stderr 
restriction is set.


Currently this regression is blocking the migration to testing [1]. Can 
you please investigate the situation and fix it?


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

Paul

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

https://ci.debian.net/data/autopkgtest/testing/amd64/p/pappl/22174962/log.gz

testsuiteFAIL stderr: Starting tests...
autopkgtest [18:13:16]: test testsuite:  - - - - - - - - - - stderr - - 
- - - - - - - -

Starting tests...
api: papplSystemFindLoc('de'): PASS
api: papplLocGetString('A printer with that name already exists.'): PASS 
(got 'Ein Drucker mit diesem Namen existiert bereits.')

api: papplSystemFindLoc('en'): PASS
api: papplLocGetString('A printer with that name already exists.'): PASS 
(got 'A printer with that name already exists.')

api: papplSystemFindLoc('es'): PASS
api: papplLocGetString('A printer with that name already exists.'): PASS 
(got 'Una impresora con ese nombre ya existe.')

api: papplSystemFindLoc('fr'): PASS
api: papplLocGetString('A printer with that name already exists.'): PASS 
(got 'Une imprimante avec ce nom existe déjà.')

api: papplSystemFindLoc('it'): PASS
api: papplLocGetString('A printer with that name already exists.'): PASS 
(got 'Una stampante con quel nome esiste già.')

api: papplSystemFindLoc('ja'): PASS
api: papplLocGetString('A printer with that name already exists.'): PASS 
(got '既に存在している名前のプリンター。')

api: papplSystemFindLoc('zz'): PASS (got NULL)
api: papplLocGetString('A printer with that name already exists.'): PASS 
(got key string)

api: papplSystemGetAdminGroup: PASS
api: papplSystemGet/SetAdminGroup('admin-0'): PASS
api: papplSystemGet/SetAdminGroup('admin-1'): PASS
api: papplSystemGet/SetAdminGroup('admin-2'): PASS
api: papplSystemGet/SetAdminGroup('admin-3'): PASS
api: papplSystemGet/SetAdminGroup('admin-4'): PASS
api: papplSystemGet/SetAdminGroup('admin-5'): PASS
api: papplSystemGet/SetAdminGroup('admin-6'): PASS
api: papplSystemGet/SetAdminGroup('admin-7'): PASS
api: papplSystemGet/SetAdminGroup('admin-8'): PASS
api: papplSystemGet/SetAdminGroup('admin-9'): PASS
api: papplSystemGet/SetAdminGroup(NULL): PASS
api: papplSystemGetContact: PASS
api: papplSystemGet/SetContact('Admin 0'): PASS
api: papplSystemGet/SetContact('Admin 1'): PASS
api: papplSystemGet/SetContact('Admin 2'): PASS
api: papplSystemGet/SetContact('Admin 3'): PASS
api: papplSystemGet/SetContact('Admin 4'): PASS
api: papplSystemGet/SetContact('Admin 5'): PASS
api: papplSystemGet/SetContact('Admin 6'): PASS
api: papplSystemGet/SetContact('Admin 7'): PASS
api: papplSystemGet/SetContact('Admin 8'): PASS
api: papplSystemGet/SetContact('Admin 9'): PASS
api: papplSystemGetDefaultPrinterID: PASS (1)
api: papplSystemSetDefaultPrinterID(2): PASS
api: papplSystemSetDefaultPrinterID(1): PASS
api: papplSystemGetDefaultPrintGroup: PASS
api: papplSystemGet/SetDefaultPrintGroup('users-0'): PASS
api: papplSystemGet/SetDefaultPrintGroup('users-1'): PASS
api: papplSystemGet/SetDefaultPrintGroup('users-2'): PASS
api: papplSystemGet/SetDefaultPrintGroup('users-3'): PASS
api: papplSystemGet/SetDefaultPrintGroup('users-4'): PASS
api: papplSystemGet/SetDefaultPrintGroup('users-5'): PASS
api: papplSystemGet/SetDefaultPrintGroup('users-6'): PASS
api: papplSystemGet/SetDefaultPrintGroup('users-7'): PASS
api: 

Bug#1012600:

[Chris Putnam]

Apologies if this question is well-answered, but why isn't this package
holding back the kernel to 5.17? In my mind an "apt upgrade" should not
have pulled 5.18, especially when the net result may well be an unbootable
system. Surely there's some way to mark this package as broken in tandem
with 5.18?

I'm also quite surprised this wasn't caught in sid before it was pulled
into testing. Is there any form of testing for this package going on in sid?

Processed: Re: [Pkg-javascript-devel] Bug#1013189: Bug#1013189: node-webpack: ftbfs Error: [BABEL]: Cannot find module '@babel/helper-define-polyfill-provider'

[Debian Bug Tracking System]

Processing control commands:

> notfound -1 5.65.0+dfsg+~cs9.20.9-13
Bug #1013189 [src:node-babel-polyfills] node-webpack: ftbfs Error: [BABEL]: 
Cannot find module '@babel/helper-define-polyfill-provider'
The source 'node-babel-polyfills' and version '5.65.0+dfsg+~cs9.20.9-13' do not 
appear to match any binary packages
Ignoring request to alter found versions of bug #1013189 to the same values 
previously set

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

Bug#1011726: switcheroo-control: FTBFS: AssertionError: 0 != 1

[Laurent Bigonville]

severity 1011726 important
thanks

On Thu, 26 May 2022 08:13:24 +0200 Lucas Nussbaum  wrote:


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

Hello,

I cannot reproduce this on my laptop, not sure what happened

I'll reduce the severity to important so the package is not removed from 
unstable for now


Kind regards,

Laurent Bigonville

Processed: Re: switcheroo-control: FTBFS: AssertionError: 0 != 1

[Debian Bug Tracking System]

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

> severity 1011726 important
Bug #1011726 [src:switcheroo-control] switcheroo-control: FTBFS: 
AssertionError: 0 != 1
Severity set to 'important' from 'serious'
> thanks
Stopping processing here.

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

Processed: reassign 1013189 to src:node-babel-polyfills, found 1013189 in 0~20220520+ds1-1 ...

[Debian Bug Tracking System]

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

> reassign 1013189 src:node-babel-polyfills
Bug #1013189 {Done: Yadd } [src:node-webpack] node-webpack: 
ftbfs Error: [BABEL]: Cannot find module 
'@babel/helper-define-polyfill-provider'
Bug reassigned from package 'src:node-webpack' to 'src:node-babel-polyfills'.
No longer marked as found in versions node-webpack/5.65.0+dfsg+~cs9.20.9-13.
Ignoring request to alter fixed versions of bug #1013189 to the same values 
previously set
> found 1013189 0~20220520+ds1-1
Bug #1013189 {Done: Yadd } [src:node-babel-polyfills] 
node-webpack: ftbfs Error: [BABEL]: Cannot find module 
'@babel/helper-define-polyfill-provider'
Marked as found in versions node-babel-polyfills/0~20220520+ds1-1 and reopened.
> fixed 1013189 0~20220520+ds1-3
Bug #1013189 [src:node-babel-polyfills] node-webpack: ftbfs Error: [BABEL]: 
Cannot find module '@babel/helper-define-polyfill-provider'
The source 'node-babel-polyfills' and version '0~20220520+ds1-3' do not appear 
to match any binary packages
Marked as fixed in versions node-babel-polyfills/0~20220520+ds1-3.
> thanks
Stopping processing here.

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

Bug#1013189: marked as done (node-webpack: ftbfs Error: [BABEL]: Cannot find module '@babel/helper-define-polyfill-provider')

[Debian Bug Tracking System]

Your message dated Sun, 19 Jun 2022 08:53:03 +0200
with message-id <11be2313-1e9b-bdac-cfec-2a456b43d...@debian.org>
and subject line Re: [Pkg-javascript-devel] Bug#1013189: node-webpack: ftbfs 
Error: [BABEL]: Cannot find module '@babel/helper-define-polyfill-provider'
has caused the Debian Bug report #1013189,
regarding node-webpack: ftbfs Error: [BABEL]: Cannot find module 
'@babel/helper-define-polyfill-provider'
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.)


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

Package: src:node-webpack
Version: 5.65.0+dfsg+~cs9.20.9-13
severity: serious

failed to build on buildd

https://buildd.debian.org/status/fetch.php?pkg=node-webpack=all=5.65.0%2Bdfsg%2B%7Ecs9.20.9-13=1654591817=0

likely a missing build depends
--- End Message ---
--- Begin Message ---

On 18/06/2022 20:21, Pirate Praveen wrote:

Package: src:node-webpack
Version: 5.65.0+dfsg+~cs9.20.9-13
severity: serious

failed to build on buildd

https://buildd.debian.org/status/fetch.php?pkg=node-webpack=all=5.65.0%2Bdfsg%2B%7Ecs9.20.9-13=1654591817=0 



likely a missing build depends


This build is old, bug is fixed since 2022-06-10 (in 
node-babel-polyfills dependencies)--- End Message ---

Bug#1013189: [Pkg-javascript-devel] Bug#1013189: node-webpack: ftbfs Error: [BABEL]: Cannot find module '@babel/helper-define-polyfill-provider'

[Yadd]

On 18/06/2022 20:21, Pirate Praveen wrote:

Package: src:node-webpack
Version: 5.65.0+dfsg+~cs9.20.9-13
severity: serious

failed to build on buildd

https://buildd.debian.org/status/fetch.php?pkg=node-webpack=all=5.65.0%2Bdfsg%2B%7Ecs9.20.9-13=1654591817=0 



likely a missing build depends


This build is old, bug is fixed since 2022-06-10 (in 
node-babel-polyfills dependencies)

Bug#1002361: marked as done (python-testing.postgresql: FTBFS: dh_auto_test: error: pybuild --test --test-nose -i python{version} -p "3.10 3.9" returned exit code 13)

[Debian Bug Tracking System]

Your message dated Sun, 19 Jun 2022 06:19:43 +
with message-id 
and subject line Bug#1002361: fixed in python-testing.common.database 2.0.3-1
has caused the Debian Bug report #1002361,
regarding python-testing.postgresql: FTBFS: dh_auto_test: error: pybuild --test 
--test-nose -i python{version} -p "3.10 3.9" returned exit code 13
to be marked as done.

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

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


-- 
1002361: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1002361
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-testing.postgresql
Version: 1.3.0-2
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20211220 ftbfs-bookworm

Hi,

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


Relevant part (hopefully):
>  debian/rules build
> dh build --with python3 --buildsystem=pybuild
>dh_update_autotools_config -O--buildsystem=pybuild
>dh_autoreconf -O--buildsystem=pybuild
>dh_auto_configure -O--buildsystem=pybuild
> I: pybuild base:237: python3.10 setup.py config 
> /usr/lib/python3/dist-packages/setuptools/dist.py:723: UserWarning: Usage of 
> dash-separated 'build-base' will not be supported in future versions. Please 
> use the underscore name 'build_base' instead
>   warnings.warn(
> running config
> I: pybuild base:237: python3.9 setup.py config 
> /usr/lib/python3/dist-packages/setuptools/dist.py:723: UserWarning: Usage of 
> dash-separated 'build-base' will not be supported in future versions. Please 
> use the underscore name 'build_base' instead
>   warnings.warn(
> running config
>dh_auto_build -O--buildsystem=pybuild
> I: pybuild base:237: /usr/bin/python3.10 setup.py build 
> /usr/lib/python3/dist-packages/setuptools/dist.py:723: UserWarning: Usage of 
> dash-separated 'build-base' will not be supported in future versions. Please 
> use the underscore name 'build_base' instead
>   warnings.warn(
> running build
> running build_py
> creating 
> /<>/.pybuild/cpython3_3.10_testing.postgresql/build/testing
> copying src/testing/__init__.py -> 
> /<>/.pybuild/cpython3_3.10_testing.postgresql/build/testing
> copying src/testing/postgresql.py -> 
> /<>/.pybuild/cpython3_3.10_testing.postgresql/build/testing
> running egg_info
> writing src/testing.postgresql.egg-info/PKG-INFO
> writing dependency_links to 
> src/testing.postgresql.egg-info/dependency_links.txt
> writing namespace_packages to 
> src/testing.postgresql.egg-info/namespace_packages.txt
> writing requirements to src/testing.postgresql.egg-info/requires.txt
> writing top-level names to src/testing.postgresql.egg-info/top_level.txt
> reading manifest file 'src/testing.postgresql.egg-info/SOURCES.txt'
> reading manifest template 'MANIFEST.in'
> adding license file 'LICENSE'
> writing manifest file 'src/testing.postgresql.egg-info/SOURCES.txt'
> I: pybuild base:237: /usr/bin/python3 setup.py build 
> /usr/lib/python3/dist-packages/setuptools/dist.py:723: UserWarning: Usage of 
> dash-separated 'build-base' will not be supported in future versions. Please 
> use the underscore name 'build_base' instead
>   warnings.warn(
> running build
> running build_py
> creating 
> /<>/.pybuild/cpython3_3.9_testing.postgresql/build/testing
> copying src/testing/__init__.py -> 
> /<>/.pybuild/cpython3_3.9_testing.postgresql/build/testing
> copying src/testing/postgresql.py -> 
> /<>/.pybuild/cpython3_3.9_testing.postgresql/build/testing
> running egg_info
> writing src/testing.postgresql.egg-info/PKG-INFO
> writing dependency_links to 
> src/testing.postgresql.egg-info/dependency_links.txt
> writing namespace_packages to 
> src/testing.postgresql.egg-info/namespace_packages.txt
> writing requirements to src/testing.postgresql.egg-info/requires.txt
> writing top-level names to src/testing.postgresql.egg-info/top_level.txt
> reading manifest file 'src/testing.postgresql.egg-info/SOURCES.txt'
> reading manifest template 'MANIFEST.in'
> adding license file 'LICENSE'
> writing manifest file 'src/testing.postgresql.egg-info/SOURCES.txt'
>dh_auto_test -O--buildsystem=pybuild
> I: pybuild base:237: cd 
> /<>/.pybuild/cpython3_3.10_testing.postgresql/build; python3.10 
> -m nose -v tests
> test_PostgresqlFactory (test_postgresql.TestPostgresql) ... ok
> test_PostgresqlFactory_with_initialized_handler 
> (test_postgresql.TestPostgresql) ... ok
> test_basic (test_postgresql.TestPostgresql) ... ok
> test_copy_data_from (test_postgresql.TestPostgresql) ... ok
> test_dsn_and_url (test_postgresql.TestPostgresql) ... ok
> test_fork (test_postgresql.TestPostgresql) 

Processed: Bug#1002361 marked as pending in python-testing.common.database

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1002361 [src:python-testing.postgresql] python-testing.postgresql: FTBFS: 
dh_auto_test: error: pybuild --test --test-nose -i python{version} -p "3.10 
3.9" returned exit code 13
Added tag(s) pending.

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

Bug#1002361: marked as pending in python-testing.common.database

[Sandro Tosi]

Control: tag -1 pending

Hello,

Bug #1002361 in python-testing.common.database reported by you has been fixed 
in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:

https://salsa.debian.org/python-team/packages/python-testing.common.database/-/commit/fd36d7ffbe911cd53358edd01f04021daae2621e


add upstream patch to properly import Callable; Closes: #1002361 (and partially 
#978259)


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1002361