Bug#1013716: marked as done (flask: FTBFS: pytest7 regression, deprecated pytest feature: pytest.warnsNone)

[Debian Bug Tracking System]

Your message dated Tue, 12 Jul 2022 03:34:11 +
with message-id 
and subject line Bug#1013716: fixed in flask 2.0.1-3
has caused the Debian Bug report #1013716,
regarding flask: FTBFS: pytest7 regression, deprecated pytest feature: 
pytest.warnsNone
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.)


-- 
1013716: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1013716
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: flask
Version: 2.0.1-2
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: debian-pyt...@lists.debian.org
Usertags: pytest7

Hi,

During a selected rebuild of python packages in sid, your package failed
to build with pytest version 7.1.2-1.

The full build log is available from:
http://qa-logs.debian.net/2022/06/09/pytest/flask_2.0.1-2_unstable_pytest-exp.log

I had a closer look at the error log and identified the regression as:
'deprecated pytest feature: pytest.warnsNone'. Hopefully, that's helpful!

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

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

If you fail to reproduce this, please provide a build log and diff it
with the one provided so that we can identify if something relevant
changed in the meantime.

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


OpenPGP_signature
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Source: flask
Source-Version: 2.0.1-3
Done: Sandro Tosi 

We believe that the bug you reported is fixed in the latest version of
flask, 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.
Sandro Tosi  (supplier of updated flask 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, 11 Jul 2022 23:15:20 -0400
Source: flask
Architecture: source
Version: 2.0.1-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Team 
Changed-By: Sandro Tosi 
Closes: 1013716
Changes:
 flask (2.0.1-3) unstable; urgency=medium
 .
   * debian/patches/426a1e25b77e760b4f54bf94aee3e3617850569f.patch
 - fix compat with pytest 7, part of PR #4443; Closes: #1013716
Checksums-Sha1:
 068f1d08a526e37f0501885fdaccd448b393efca 2306 flask_2.0.1-3.dsc
 487aa4a69539d49f2315289e62ea473044ca974b 7632 flask_2.0.1-3.debian.tar.xz
 ee1fb21dd36d0343b681947afc4d83a17191dce6 8310 flask_2.0.1-3_source.buildinfo
Checksums-Sha256:
 b0602523534123931614074ab050311ee255c5a81e8d6276a84adc501eee7e67 2306 
flask_2.0.1-3.dsc
 305c415d275ec3325c1354a1b328827074cac206af0d5b396717023f00e02729 7632 
flask_2.0.1-3.debian.tar.xz
 0deb9caff86e9da225daab88d082576cf0015fdbb0690f710d6b28b9adf5eb8b 8310 
flask_2.0.1-3_source.buildinfo
Files:
 e7c6e4ae32bb2cf6c8533da89dd71c1d 2306 python optional flask_2.0.1-3.dsc
 429958480cce4020da89a40ba23feae1 7632 python optional 
flask_2.0.1-3.debian.tar.xz
 9ff59300e9cb2f5a6721bd5460853900 8310 python optional 
flask_2.0.1-3_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEufrTGSrz5KUwnZ05h588mTgBqU8FAmLM52gACgkQh588mTgB
qU87rQ/8Cwd2d1TmWtgTTfa182ij3xEoaIB2HRc8MHllPwwaiDwjIksZvi5G/ihO
iR+4rzv2QXotV5GxVwsI8KRiqBDnjYJfmY5bHjuQ7nmTvRUvfjl82f70dEVYUd0U
8eVq8hlz/YR2MSDcoVkNDJfQ6mvcYlWsJ4JpKsq6uKe6fApej5P2A26IRLhFNlK1
rRFNatnXK9gifB3wFY8RAZ+zt0vv6H+MnmSBAVinKVqpUs2EvHdZE3W8ougKZ+Wy
P+hD8B9Nxf5Qm1C2nwj3DAZtWTM2nchxS+GViPddRtt8aG6iieN+aO1DAsArjuHK
2eGngUqKQJzo4lcoQnU3prUEaHe4xKp4mqIRzLUgeONbMi+W8L8UvoW84aczAPjX
cACJJGSxn05zgHcelFQhb2K+Ma4zT4k2ZdjfHM89/MlrUmN0A/qDU6Gj2Kj7j5a0
bC4TsbpHJ8UwScjTkdKK3x2Dx5JC/brI47KooeeHnylMlj9sPPt3LY/Gqubffdju
rHeVRAhQdZenZHYjSRcPiUO2eU9929OtivScs/He1HKAII4tlDQbdHsa9FwXYnxg
fu3TOR9/Z/sLfI1mNneCRMP5XgROIaVvMNroDDZuPS2MggiyJ1dYeydOj/jzpEWG
ewLbyel0zKvG50yRTO9/YMT17kr3xM4Ps+g0iAN8orT0Ya/k+Qc=
=j06F
-END PGP SIGNATURE 

Processed: Bug#1013716 marked as pending in flask

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1013716 [src:flask] flask: FTBFS: pytest7 regression, deprecated pytest 
feature: pytest.warnsNone
Added tag(s) pending.

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

Bug#1013716: marked as pending in flask

[Sandro Tosi]

Control: tag -1 pending

Hello,

Bug #1013716 in flask 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/flask/-/commit/391fb2b1e6b5e7f91e93f55e35358400e08bccac


fix compat with pytest 7, part of PR #4443; Closes: #1013716


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1013716

Processed: bug 1013705 is forwarded to https://github.com/xolox/python-humanfriendly/issues/64

[Debian Bug Tracking System]

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

> forwarded 1013705 https://github.com/xolox/python-humanfriendly/issues/64
Bug #1013705 [src:humanfriendly] humanfriendly: FTBFS: pytest7 regression, 
upstream doesn't actually use pytest?
Set Bug forwarded-to-address to 
'https://github.com/xolox/python-humanfriendly/issues/64'.
> thanks
Stopping processing here.

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

Bug#1013725: marked as done (python-aws-xray-sdk: FTBFS: pytest7 regression, deprecated pytest feature: -k-)

[Debian Bug Tracking System]

Your message dated Tue, 12 Jul 2022 02:36:21 +
with message-id 
and subject line Bug#1013725: fixed in python-aws-xray-sdk 0.95-3
has caused the Debian Bug report #1013725,
regarding python-aws-xray-sdk: FTBFS: pytest7 regression, deprecated pytest 
feature: -k-
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.)


-- 
1013725: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1013725
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-aws-xray-sdk
Version: 0.95-2
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: debian-pyt...@lists.debian.org
Usertags: pytest7

Hi,

During a selected rebuild of python packages in sid, your package failed
to build with pytest version 7.1.2-1.

The full build log is available from:
http://qa-logs.debian.net/2022/06/09/pytest/python-aws-xray-sdk_0.95-2_unstable_pytest-exp.log

I had a closer look at the error log and identified the regression as:
'deprecated pytest feature: -k-'. Hopefully, that's helpful!

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

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

If you fail to reproduce this, please provide a build log and diff it
with the one provided so that we can identify if something relevant
changed in the meantime.

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


OpenPGP_signature
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Source: python-aws-xray-sdk
Source-Version: 0.95-3
Done: Sandro Tosi 

We believe that the bug you reported is fixed in the latest version of
python-aws-xray-sdk, 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.
Sandro Tosi  (supplier of updated python-aws-xray-sdk 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, 11 Jul 2022 22:07:51 -0400
Source: python-aws-xray-sdk
Architecture: source
Version: 0.95-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Science Maintainers 

Changed-By: Sandro Tosi 
Closes: 1013725
Changes:
 python-aws-xray-sdk (0.95-3) unstable; urgency=medium
 .
   * debian/rules
 - fix pytest -k syntax for pytest 7; Closes: #1013725
Checksums-Sha1:
 d93e9750669025446b1ceebf5421f5dbb4bb4dbd 2228 python-aws-xray-sdk_0.95-3.dsc
 fcf1e8ddda009f4cd1628d6536207512e25c41d0 1912 
python-aws-xray-sdk_0.95-3.debian.tar.xz
 02148fac22f4c7b0a9dca2f61928c6033abcce38 8093 
python-aws-xray-sdk_0.95-3_source.buildinfo
Checksums-Sha256:
 988890540f8fcf6bc7e66bbf6d41979ac87a79d1249f050f5c8d4cc05ef39ca9 2228 
python-aws-xray-sdk_0.95-3.dsc
 78b16a3c4e2a84060bda126574b483bf3b01ebca8e80caf449309aea128fae39 1912 
python-aws-xray-sdk_0.95-3.debian.tar.xz
 ff19529600be3a0bd6c1c7784823a02a6ad5b3577179dc31260ea6bb1aeba323 8093 
python-aws-xray-sdk_0.95-3_source.buildinfo
Files:
 2c689b6252a0b2b7cfbc88302903f1a8 2228 python optional 
python-aws-xray-sdk_0.95-3.dsc
 2f043cfafc5b85c00d999c4a30a25982 1912 python optional 
python-aws-xray-sdk_0.95-3.debian.tar.xz
 8bc24c3d59fe7c0f13218c5515174653 8093 python optional 
python-aws-xray-sdk_0.95-3_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEufrTGSrz5KUwnZ05h588mTgBqU8FAmLM15wACgkQh588mTgB
qU8UqA/8CekxAoKUTKYHQV+ONjg9oPXzOc7PwLAfkqwP0Oi8BA8OlFCA4q1s9FQg
Rd1eyOnDAQpOSSjmr6QkAuqWuBYTXRen7faeLggWNQawaBTXX+AOyJ7pGfXVXVr3
WYoefmZoy5aGg54X6u26yLLVT6PUJ0GwjDZtto9bvejZyC8Nxvz2Y6+RrQ+byFBO
fHKCC9fJLzVRObJ+g6d+qWycEoT4rNoW60ZNLinDAJKqEQ8T3gPzIga0heacYNkS
/XVUoqjqAUNiJzBHEIIK/pN9sHIvQlhlkXIeRQo2IADJyjPep/iKHm3csUqJJmoW
y6KM3N48/y7Q4WkKTNnxnVZCkJvda2zZzARz2j1xJzX+FfRgSg5t9rwXI/pG5J3D
BgsAlHTtueCeWB/UucjNwsWkH/uIVBTMWkP0cbwjF/wmLzgQTXs50Sbb4MHWoEtg
PSE/gSLco9F5PSDc3GVwMty/g+gw6RPsQNkoneCRT2M0FzL3CQK28gnVJQx9E/dD

Bug#1013708: marked as done (python-pykka: FTBFS: pytest7 regression, AttributeError: module pytest has no attribute collect)

[Debian Bug Tracking System]

Your message dated Tue, 12 Jul 2022 02:36:28 +
with message-id 
and subject line Bug#1013708: fixed in python-pykka 2.0.3-3
has caused the Debian Bug report #1013708,
regarding python-pykka: FTBFS: pytest7 regression, AttributeError: module 
pytest has no attribute collect
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.)


-- 
1013708: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1013708
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-pykka
Version: 2.0.3-2
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: debian-pyt...@lists.debian.org
Usertags: pytest7

Hi,

During a selected rebuild of python packages in sid, your package failed
to build with pytest version 7.1.2-1.

The full build log is available from:
http://qa-logs.debian.net/2022/06/09/pytest/python-pykka_2.0.3-2_unstable_pytest-exp.log

I had a closer look at the error log and identified the regression as:
'AttributeError: module pytest has no attribute collect'. Hopefully,
that's helpful!

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

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

If you fail to reproduce this, please provide a build log and diff it
with the one provided so that we can identify if something relevant
changed in the meantime.

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


OpenPGP_signature
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Source: python-pykka
Source-Version: 2.0.3-3
Done: Sandro Tosi 

We believe that the bug you reported is fixed in the latest version of
python-pykka, 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.
Sandro Tosi  (supplier of updated python-pykka 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, 11 Jul 2022 22:16:58 -0400
Source: python-pykka
Architecture: source
Version: 2.0.3-3
Distribution: unstable
Urgency: medium
Maintainer: Stein Magnus Jodal 
Changed-By: Sandro Tosi 
Closes: 1013708
Changes:
 python-pykka (2.0.3-3) unstable; urgency=medium
 .
   * debian/patches/pytest7.patch
 - fix compatibility with pytest 7; Closes: #1013708
Checksums-Sha1:
 7e908dc7d588db830020e30f766dacf25a601b2f 2086 python-pykka_2.0.3-3.dsc
 989eb0c0502c0030d966174d7c0ea33edf1f0b04 5144 
python-pykka_2.0.3-3.debian.tar.xz
 4dd5319cb65e4f6cb388a083710df026c72257ee 8251 
python-pykka_2.0.3-3_source.buildinfo
Checksums-Sha256:
 997ccddd4a4deac90e27e34a063837d888f62180ca97f72c010306a2310b14ee 2086 
python-pykka_2.0.3-3.dsc
 7149ced0069c44a7efc62e94f8227b6bec9a47d9b7e8529e7a927c3821742c71 5144 
python-pykka_2.0.3-3.debian.tar.xz
 c33f8cef43e5efbe7dec472039775537cb0276de539ec8f411ddd24faf8a770e 8251 
python-pykka_2.0.3-3_source.buildinfo
Files:
 180ce4177fb261072e777ea506d67362 2086 python optional python-pykka_2.0.3-3.dsc
 99acd7b8ecc6516c8bbcc99f588127dd 5144 python optional 
python-pykka_2.0.3-3.debian.tar.xz
 d25feaa4aa80fb2b3eae01c6ef608367 8251 python optional 
python-pykka_2.0.3-3_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEufrTGSrz5KUwnZ05h588mTgBqU8FAmLM2agACgkQh588mTgB
qU/lTxAAuhzlIYqBfflaXvkhqTrcc2us3OrubjQ5uH2uUPshNPDvOfNDsNPoDqPP
hkjlE4M4VKxitN8XjBfX4DINZE4+UU5/N9TsnZM3WFuwlQKvJrdOkgn2EGlCA/DC
v3/5c2BkzfQoIqh9b096DYLKk/RFLz7dMzDAds2wvZavkDNa/kS2BDVU+yyGEHb6
H31s+NZThqa/aJQGafeEZt5BQCsmrcuPANSS1EpUJrqlorHD5ns+ivLXGmkTVsVp
sIRCkl+ODYoFtcMCKqOoY25+eADWJvC+8LRot9b6vhhX6jKWADmWrq9AwtsCisV1
KqHY8xcAbkAMMT4j0jN5wy03tY5V3zb3vgyRiNJwWIy19WbA+jvsaUxsbssI+Saj
s5/i0MTfKaWG9jRfoZEa6yhvDbcFehLeYwDFGJGtDhvPNMA5Oe0AKD+T37lLQVTg
ES4annu3mdQyAsv8vENJfMyFlMBIbuQ/m5Ep9uPM/7pVVFpSjrKrAnbHua3c9Cr4
K3f7Uo3JFaaqlcfOW/RyjIgB2x2Y1fCnLtD7/AGLou++yWLWgzAQV2yDunzfueFI

Bug#1013708: marked as pending in python-pykka

[Sandro Tosi]

Control: tag -1 pending

Hello,

Bug #1013708 in python-pykka 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-pykka/-/commit/b66b92fb1b33a2793aff5a245f8e14b76f61889c


fix compatibility with pytest 7; Closes: #1013708


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1013708

Processed: Bug#1013708 marked as pending in python-pykka

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1013708 [src:python-pykka] python-pykka: FTBFS: pytest7 regression, 
AttributeError: module pytest has no attribute collect
Added tag(s) pending.

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

Bug#1014596: marked as done (curl FTBFS: missing #include )

[Debian Bug Tracking System]

Your message dated Mon, 11 Jul 2022 22:18:59 +
with message-id 
and subject line Bug#1014596: fixed in curl 7.84.0-2
has caused the Debian Bug report #1014596,
regarding curl FTBFS: missing #include 
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.)


-- 
1014596: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1014596
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: curl
Version: 7.84.0-1
Severity: serious
Tags: ftbfs patch upstream
User: helm...@debian.org
Usertags: rebootstrap

Hi,

curl fails to build from source on architectures other than any-x86 and
arm64 due to a missing #include . Please consider applying the
attached patch to fix that.

Helmut
--- curl-7.84.0.orig/lib/easy_lock.h
+++ curl-7.84.0/lib/easy_lock.h
@@ -37,6 +37,10 @@
 #elif defined (HAVE_ATOMIC)
 #include 
 
+#if !defined(__i386__) && !defined(__x86_64__) && !defined(__aarch64__) && defined(HAVE_SCHED_YIELD)
+#include 
+#endif
+
 #define curl_simple_lock atomic_bool
 #define CURL_SIMPLE_LOCK_INIT false
 
--- End Message ---
--- Begin Message ---
Source: curl
Source-Version: 7.84.0-2
Done: Samuel Henrique 

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

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

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

Debian distribution maintenance software
pp.
Samuel Henrique  (supplier of updated curl package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Mon, 11 Jul 2022 22:50:01 +0100
Source: curl
Architecture: source
Version: 7.84.0-2
Distribution: unstable
Urgency: medium
Maintainer: Alessandro Ghedini 
Changed-By: Samuel Henrique 
Closes: 1014596
Changes:
 curl (7.84.0-2) unstable; urgency=medium
 .
   * d/p/20_ftbfs_import_sched.patch: New upstream patch to fix FTBFS
 (closes: #1014596)
Checksums-Sha1:
 c2495c80a0bbbe67c08da2dbc19aa92ffb5df543 2959 curl_7.84.0-2.dsc
 7bb0662b1bc703d731134b2937116d48ed164fee 36164 curl_7.84.0-2.debian.tar.xz
 859759a45e177093379e50bebb11091851009c52 12964 curl_7.84.0-2_amd64.buildinfo
Checksums-Sha256:
 f222c5e81b572689741f3a20854692cabb7445a34fa058c11c4894ae3d9b1b7b 2959 
curl_7.84.0-2.dsc
 701ca4ce3122be35875bfef7f2ca7501fb1ff8c92d9655613e2352c6f4581c20 36164 
curl_7.84.0-2.debian.tar.xz
 f766f4baf4fc18db803863a6b3d802b7b187193c4a084e1bbff4ae82d127dc0d 12964 
curl_7.84.0-2_amd64.buildinfo
Files:
 b5374b8bad224ac48b5a1c4854db0fbe 2959 web optional curl_7.84.0-2.dsc
 30d7ada5fbaaddb19f9d9869a8e6eaa5 36164 web optional curl_7.84.0-2.debian.tar.xz
 9eca390ba4c1ac179df060465b0afb4c 12964 web optional 
curl_7.84.0-2_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEBdtqg34QX0sdAsVfu6n6rcz7RwcFAmLMnRQACgkQu6n6rcz7
Rwe7fA/+KVoE07aQmWi0joOlQ5KtvMpmEzJoeXcamDoD16fBTe4d1JdG7dzkVPna
qhD5NdrnkISO0E4Tlt9re6TjCLr7O/x+BL2G3bMmfcPxzvjZq7Ro2/dq+u5641zB
q3pHhPeoJGgW0pTFJORvAlW7lZnWGoAzKhv9AJADxKCbUMVK2sH35/VWwIA3+n7z
GLBDca+/2Hqgdfd7gpT7GkFxwZMNX4OFNXurEAn2juWuX6/k6fLzm9btEXY+rER0
PsATg9i4usX+W1u4cNz/c4XiUPnnFb6wg0fA2qSL4y4lrucVrR0YPfpqGCOkkBMT
aDcd1uMZSHkZcG585htevghE/Eh2MEwSRXykJZqBOM04oyMLz3y4IcsL1ATsvTXM
tm+hHgTaPC3iPVnfg5C7dQWPrx2B4fn1YPLBAprsgAZN+fzRxBi0YEGXhzDbFPsR
KqZjIFzkpsb1QFLw8FFsUGW/SGa67oNQQbgAEXvIOdRMAtNg85bUu7XX8AXhR9b7
aXt4cuwagUDIyJ0AmjBi0UXCsMJxyD48JYmQ8KiW/x/oXOtBzPu6bQb8IOLG9Hou
H+2kVhCeVYEzV6welrvNedZql4kPmlPdSCtX2b4AVQpcQ0B+CTKKbqod0XkQKuW8
Ku7hXoyiPFRbZ2s6rFcbD/E0Y7ruQYeX4uMiYPtCiZj3ng/yw7I=
=2Pqk
-END PGP SIGNATURE End Message ---

Bug#1014787: paraview: no render view created

[Wojciech Aniszewski]

Package: paraview
Version: 5.10.1-2
Severity: grave
Justification: renders package unusable

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Dear Maintainer,

*** Reporter, please consider answering these questions, where appropriate ***

   * What led up to the situation?
   * What exactly did you do (or not do) that was effective (or
 ineffective)?
   * What was the outcome of this action?
   * What outcome did you expect instead?

*** End of the template - remove these template lines ***

Paraview 5.10.1-2 upon launch should display the visualization window (a 
"Layout"). Then, after loading external data or using any data source, it 
should be rendered in the main layout window. Instead, nothing happens, no 
rendering is shown, using other views (such as spreadsheet, etc.) is also 
impossible, Paraview windows is no longer refreshed, making it completely 
unusable.

I will add I'm on a Thinkpad T14, gen1, AMD. I can anclose the lspci etc., for 
now it suffices to say the video card is shown as, (lspci):

07:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] 
Renoir (rev d1)

regards
WA





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

Kernel: Linux 5.18.0-2-amd64 (SMP w/16 CPU threads; PREEMPT)
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 paraview depends on:
ii  libavcodec59   7:5.0.1-3
ii  libavformat59  7:5.0.1-3
ii  libavutil577:5.0.1-3
ii  libc6  2.33-7
ii  libdouble-conversion3  3.1.7-4
ii  libexpat1  2.4.8-1
ii  libfreetype6   2.12.1+dfsg-3
ii  libgcc-s1  12.1.0-2
ii  libgdal31  3.5.0+dfsg-1+b1
ii  libgl2ps1.41.4.2+dfsg1-2
ii  libglew2.2 2.2.0-4
ii  libglx01.4.0-1
ii  libhdf5-103-1  1.10.7+repack-4+b1
ii  libjpeg62-turbo1:2.1.2-1
ii  liblz4-1   1.9.3-2
ii  liblzma5   5.2.5-2.1
ii  libnetcdf191:4.9.0-2
ii  libogg01.3.5-1
ii  libopengl0 1.4.0-1
ii  libopenmpi34.1.4-1
ii  libpng16-161.6.37-5
ii  libpython3.10  3.10.5-1
ii  libpython3.9   3.9.13-1
ii  libqt5core5a   5.15.4+dfsg-3
ii  libqt5gui5 5.15.4+dfsg-3
ii  libqt5help55.15.4-2
ii  libqt5network5 5.15.4+dfsg-3
ii  libqt5widgets5 5.15.4+dfsg-3
ii  libstdc++6 12.1.0-2
ii  libswscale67:5.0.1-3
ii  libtheora0 1.1.1+dfsg.1-16
ii  libtiff5   4.4.0-2
ii  libx11-6   2:1.7.5-1
ii  libxcursor11:1.2.1-1
ii  libxml22.9.14+dfsg-1
ii  python3-autobahn   22.1.1+dfsg1-2
ii  python3-matplotlib 3.5.2-1
ii  python3-mpi4py 3.1.3-2
ii  python3-six1.16.0-3
ii  python3-twisted22.4.0-2
ii  tcl [tclsh]8.6.11+1
ii  zlib1g 1:1.2.11.dfsg-4

Versions of packages paraview recommends:
ii  mpi-default-bin  1.14
ii  paraview-doc 5.10.1-2
ii  python3-paraview [python3-paraview]  5.10.1-2

Versions of packages paraview suggests:
ii  h5utils 1.13.1-4
ii  hdf5-tools  1.10.7+repack-4+b1

- -- no debconf information

-BEGIN PGP SIGNATURE-

iQEzBAEBCgAdFiEENHZ/67ZMjPXjhgdLxBIgNKxmSF4FAmLMgewACgkQxBIgNKxm
SF4mQgf+PyAScbQMwrMi/95gbK2hWhXsi4FJy0SD6PdMXPXUiTAyh8KDW1ufx9XB
CG6+vQnUzZ8LrbxeIvHplZx+n8QN3PTgRNLrGidum7rpaetXd9359FjSQpLwnuWI
nAqa0KxM0HnD9e5o847QZz2/3EBgzcuOVAYrMQeqY4BBo01D2XTs+Dfgt1dd+cLf
/ZJFGubcS8eFRwMzSeimOsUk07LFTKOP2GnSwqsHoL5sHOZUZs+Op+Pi9reGBdjA
KRqPSJFM+KQRpTeE9QRFr47t1unlQq7b+e7TeeQejHYLcu5Kuo/5PrAsWoCjfByo
gJSkruQZgMjJovaktKnTZIdA1eDpjQ==
=OP7V
-END PGP SIGNATURE-

Bug#1014735: rpcsvc-proto: The /usr/include/rpc/* files is not included

[Aurelien Jarno]

Hi,

On 2022-07-11 22:18, Magnus Danielson wrote:
> Hi,
> 
> On 7/11/22 18:30, Aurelien Jarno wrote:
> > control: tag -1 + moreinfo
> > 
> > Hi,
> > 
> > On 2022-07-11 02:46, Magnus Danielson wrote:
> > > Package: rpcsvc-proto
> > > Version: 1.4.2-4
> > > Severity: grave
> > > Justification: renders package unusable
> > rpcsvc-proto is used to build many packages in Debian, so I doubt it is
> > completely unusable.
> Fair enough, but for my purpose it failed completely. Of the options given
> by text in recommended tool reportbug this was closest to my experienced
> situation.
> > 
> > > Dear Maintainer,
> > > 
> > > Template answers first, for your convenience.
> > > 
> > >     * What led up to the situation?
> > > 
> > > Rebuilding an application using rpcgen.
> > > 
> > >     * What exactly did you do (or not do) that was effective (or
> > >   ineffective)?
> > > 
> > > Run rpcgen, then tried to compile the produced files.
> > > 
> > >     * What was the outcome of this action?
> > > 
> > > Any of the /usr/include/rpc/* header-files referenced such as
> > > #include 
> > > etc. fail to include, all the related definitions missing causes large
> > > amount
> > > of compile errors.
> > Could you please give me more details about the issue? Ideally copy and
> > paste the error message.
> make
> rpcgen core.x
> gcc -DHAVE_CONFIG_H -I. -I. -I.    -Wall -g -O2 -c core_svc.c
> In file included from core_svc.c:6:
> core.h:9:10: fatal error: rpc/rpc.h: No such file or directory
>     9 | #include 
>   |  ^~~
> compilation terminated.
> make: *** [Makefile:514: core_svc.o] Error 1
> 
> So, here rpcgen process the core.x, outputting core_clnt.c, core_svc.c,
> core_xdr.c and core.h.

Ok, so that's definitely the issue of the SunRPC removal from glibc.

> The next step is to compile these, and for the case of core_svc.c this fails
> because
> 
> #include 
> 
> which is generated by rpcgen (there is no such reference in core.x) and thus
> needed by users for rpcgen.
> 
> I think it is fair to assume that when using rpcgen, the associated
> headerfiles needed to compile is either directly or indirectly in the
> package (or dependencies of the package).
 
> > My guess is that your problem is not related to rpcsvc-proto itself
> > which just provides rpcgen and related header files, but with the
> > removal of the SunRPC implementation for glibc. You need to switch to
> > the TI RPC implementation instead (using the libtirpc-dev package).
> 
> Which does not work out, since rpcgen does generate the dependence to
> /usr/include/rpc/* and the installed libtirpc-dev delivers the files in
> /usr/include/tirpc/rpc/* so despite being installed, gcc does not find it,
> and the rpcgen produces files that does not compile.

Given the SunRPC library has been removed from glibc, you definitely
need to use pkg-config to get the correct link time flags to link
your code against libtirpc. Therefore changes are needed to your
project, whether you want it or not. You can therefore do the same
changes for the includes.

There are multiple compatible RPC libraries (which actually predates the
SunRPC removal), and users are able to select the one they prefer by
using the correct include and link flags.

Note that most open source projects have already been updated to
automatically switch to an alternative RPC implementation since the
first distribution removed the SunRPC support more than 4 years ago (at
this time this was still an opt-in on the glibc side).

> > >     * What outcome did you expect instead?
> > > 
> > > Nice compile as headerfiles is found.
> > > 
> > > This is most likely a consequence of repackaging the rpc-part. Looking 
> > > back
> > > at
> > > the stable version of libc6 the header files is there in libc6-dev, but 
> > > for
> > > testing and unstable they are not. I expect that using these this would
> > > work.
> > > If the headerfiles is in another package, dependence on that should be in
> > > place.
> > The files that are removed from libc6-dev are the ones related to the
> > removed SunRPC implementation. libc6-dev (indirectly) depends on
> > libtirpc3-dev so the replacement header files should be available on
> > your system. That said it is not a one to one replacement, so you need
> > to use pkgconfig to get the compile and link flags.
> 
> Which is documented where for this change?

The changes is documented on the Debian side in changelog.Debian.gz and
on the upstream side in NEW.gz. That said, I agree that I failed to
properly document the changes with details instructions about how to
convert existing code in the NEWS.Debian.gz file.

> The repackaging caused generated code that did work fail to work. It seems

Just to be clear, this is not a repackaging. This is a *removal* of the
SunRPC support from glibc. The TI RPC library was already packaged in
Debian, and we just provided support for rpcgen (through the
rpcsvc-proto fork). The other alternative would have to just remove

Bug#1014741: libgd-perl: GD and GD2 image formats are disabled in libgd3 package

[Guyang "Alex" Mao]

That's honestly what I did to get my usecases working again.

I also removed the other 2-3 places gd/gd2 are mentioned but I'm not sure 
those break anything.


cheers,

On Mon, 11 Jul 2022, gregor herrmann wrote:


But I don't have enough knowledge about this stuff that I would feel
confident to blindly upload.

Processed: Re: Bug#1014741: libgd-perl: GD and GD2 image formats are disabled in libgd3 package

[Debian Bug Tracking System]

Processing control commands:

> tag -1 + patch
Bug #1014741 [libgd-graph-perl] libgd-perl: GD and GD2 image formats are 
disabled in libgd3 package
Added tag(s) patch.

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

Bug#1014741: libgd-perl: GD and GD2 image formats are disabled in libgd3 package

[gregor herrmann]

Control: tag -1 + patch

On Mon, 11 Jul 2022 17:55:29 +0200, gregor herrmann wrote:

> I also note that the tests (which use the samples (which call the 
> export_format
> function (which has line 515 of Graph.pm))) also fail by now:
> 
> #   Failed test at t/samples.t line 21.
> # died: gdImageGdPtr error at 
> /build/libgd-graph-perl-1.54~ds/blib/lib/GD/Graph.pm line 515.
> # Compilation failed in require at t/samples.t line 17.

With this change

#v+
% cat debian/patches/disable-old-formats.patch 
--- a/Graph.pm
+++ b/Graph.pm
@@ -514,7 +514,7 @@
 $g->colorAllocate(0,0,0);
 $g->$_() 
};
-} qw(gif png jpeg xbm xpm gd gd2);
+} qw(gif png jpeg xbm xpm);
 wantarray ? @f : $f[0];
 }
 
#v-

the tests indeed pass.
But I don't have enough knowledge about this stuff that I would feel
confident to blindly upload.


Cheers,
gregor

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


signature.asc
Description: Digital Signature

Bug#1014784: marked as done (libprimesieve10: unneccessary Provides+Conflicts renders shared library not-coinstallable)

[Debian Bug Tracking System]

Your message dated Mon, 11 Jul 2022 20:56:00 +
with message-id 
and subject line Bug#1014784: fixed in primesieve 8.0+ds-2
has caused the Debian Bug report #1014784,
regarding libprimesieve10: unneccessary Provides+Conflicts renders shared 
library not-coinstallable
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.)


-- 
1014784: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1014784
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libprimesieve10
Version: 8.0+ds-1
Severity: serious
X-Debbugs-Cc: sramac...@debian.org
Justification: Policy §8

libprimesieve10 and libprimesieve9 both declare Provides+Conflicts:
libprimesieve. This causes the shared library packages libprimesieve10
and libprimesieve9 unable to be installed at the same time. This makes
the upgrade from bullseye to bookworm unnecessarily more complex.

Please remove the Provides+Conflicts.

Cheers
-- 
Sebastian Ramacher
--- End Message ---
--- Begin Message ---
Source: primesieve
Source-Version: 8.0+ds-2
Done: Jerome Benoit 

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

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

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

Debian distribution maintenance software
pp.
Jerome Benoit  (supplier of updated primesieve package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Mon, 11 Jul 2022 20:38:41 +
Source: primesieve
Architecture: source
Version: 8.0+ds-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Math Team 
Changed-By: Jerome Benoit 
Closes: 1014784
Changes:
 primesieve (8.0+ds-2) unstable; urgency=medium
 .
   * SBFR, sanitize d/control (Closes: #1014784).
Checksums-Sha1:
 869cd9884a4eef171f24dbddbd2f4ac8a1aa5222 3150 primesieve_8.0+ds-2.dsc
 01b44ef52aa41a52d8dc787ac680bdd4d1ba779d 7512 primesieve_8.0+ds-2.debian.tar.xz
 11826367560d60b4183612551baa5e62f2db7874 7766 
primesieve_8.0+ds-2_source.buildinfo
Checksums-Sha256:
 2c5acaabdd41baac46f8b5b50de0b137a78e622c57c719d4a7ddc34cf36bd624 3150 
primesieve_8.0+ds-2.dsc
 9b9b3baddfb6ea7a3f4cb447344a4fcb865c12ac4993560bd1f6cf06a33979c6 7512 
primesieve_8.0+ds-2.debian.tar.xz
 7148cbb380c5d46e3e4771f2abc1aa8cfc6bc6db5a7ff725be7e8c2fa82e98c4 7766 
primesieve_8.0+ds-2_source.buildinfo
Files:
 308176004d24c3f4459794b05c1e91f4 3150 math optional primesieve_8.0+ds-2.dsc
 9fa24087e14c1069fc0ba3e31412e301 7512 math optional 
primesieve_8.0+ds-2.debian.tar.xz
 97a20bb1c925d2b8f73b9bae607bd174 7766 math optional 
primesieve_8.0+ds-2_source.buildinfo

-BEGIN PGP SIGNATURE-

iQRIBAEBCgAzFiEEriiuFXEN/x2H5adiP5IZpn82xosFAmLMirAVHGNhbGN1bHVz
QHJlem96ZXIubmV0AAoJED+SGaZ/NsaLPggf+O8ZlJHbdJV7OWz8BOBUt0XVQP+F
0DEU2IM6/TtKOZLtJJxjM+RfyWQI9tZpFwUSmT0RYuYEfJJ7eb7yWjy8Gxg3T9jz
bpH0bmP9bLtgnIWvHeessajZsUf4A6dwFAuTWXxINayIrItZQuWU5UyviGyzhAqt
3SOvi2K1eCLTZ/QRStTcE/XCMNnyQjj/iUhk8608G2/39Mb6++McO1LHr4lr8yJI
3vMG+rLfuLbWNkMvEx3FUjAa93KMBjpeH0WR8CSAq7cysNdpIvMQBcth3fHGIHLW
7kHMDvwOmaPJJVsq0tJ/He37KIb2T56OOYwheM4tnhvNIS5B4YSPaS/i8F6n3HcA
d193HOBSk8dmxHyuBZnz2k4W1YiAgufYpyo24gUIMckb2MzfRkK9WtUh2J/KGl3n
Z0jJwVo0Gotuzhyv/7nmth6YfOSRBu2UgscfzOnJ53O9jCaeheQ0kiQBrTc9Pa+2
2ADqktSQ1YoJzqtOpjCNsz6pMwjErmv5FzGUFOn/Pq6XMIvrIf5WLps7+A5PBZ0k
0peEiANm++oRROz22t42cShZO0jhls6qrik3SpeYIncU+yLdPaXNz+F/Pp61Gp99
w4dMvPQ17pT7dfeQoP1ff94aMU9l2pfHwGlqJm1GuuUJsxIJfEQROK2ZI+8kLIJy
xm+rxJL5rufipzCabgehRsyfAhQMNtSye3CEzwFCHI65Fzl+MkCAGERwr/GTMauB
ZZwyKaHpimCa5FvR3kX3bzMAnNR2NLbpUwo+tO/2cxUKe+2ZkCfuWwlshZ97le9Q
iyJwj7sELDZDJcf/ACXpIZ912LkBW0Ayoc238ymXLYcagPvEP2GuoawbeK1peGpm
Pz6wYrTpK40lb944XqAH1ziLd6hHSzGj2k0fpyWNO7nhyaRbCpz7pEM5LLY+Qahn
LVqQ+YWnXyeDlgBRZOYjLusjDBxoVaJogDdsgr10rUFbMna/HvngGkpOZ7vuUVdw
DxTMzo8AvCMa7Ripi0bTpTg93FXJIFyiKQvx7mp2ibS8PSeONVd772DYmQjhO7Bv
KH5M8DMyIZaMfZY2rJXPTa/2C00ImIvESd3PUZ3wX6/51Ku3+RHzGzeqSLoO9Jld
NEHiNes/0PA3XQNAMoGertOkblPxfI+RZGSTG2u/YNTqxc/mQhSFyEk1hhlnQgl6
LFGXpkMM3shto4oO2iYTmFI0icw0imob23HcRNgCbYgGuphZ7jifYyu7oOy6Sqi8
7WdY6/Yti5M1Ffc9zSq8YrEkuQS1COlHSgNAQzBroomCMDYX88IKa61InwjXbA63
6AYS5PetR0lcI/R7nEupbYgq868GD0tESpwU9FlZzdwEX3xprgvdxwuN1A==
=LlMu
-END PGP SIGNATURE End Message ---

Bug#1013299: marked as done (linux-image-4.19.0-20-amd64: NULL pointer deref in qdisc_put() due to missing backport)

[Debian Bug Tracking System]

Your message dated Mon, 11 Jul 2022 20:48:08 +
with message-id 
and subject line Bug#1013299: fixed in linux 4.19.249-1
has caused the Debian Bug report #1013299,
regarding linux-image-4.19.0-20-amd64: NULL pointer deref in qdisc_put() due to 
missing backport
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.)


-- 
1013299: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1013299
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:linux
Version: 4.19.235-1
Severity: critical
Tags: upstream
Justification: breaks the whole system

A recent upstream “stable” upgrade backported the removal of the
qdisc_destroy() function (which, in itself, is questionable enough
already and caused no small amount of fun) using qdisc_put() instead.

However, qdisc_put() does not accept NULL pointers, causing oopses
in several qdiscs that can be configured on a system. This breaks
sudo (su works), networking and even deconfiguration is not possible,
only /proc/sysrq-trigger makes it possible to recover.

https://www.mail-archive.com/netdev@vger.kernel.org/msg314288.html
fixes this but was not backported along.


-- Package-specific info:
** Version:
Linux version 4.19.0-20-amd64 (debian-ker...@lists.debian.org) (gcc version 
8.3.0 (Debian 8.3.0-6)) #1 SMP Debian 4.19.235-1 (2022-03-17)

** Command line:
BOOT_IMAGE=/boot/vmlinuz-4.19.0-20-amd64 root=/dev/vda2 ro net.ifnames=0 
nomodeset

** Not tainted

** Kernel log:
Unable to read kernel log; any relevant messages should be attached

** Model information
sys_vendor: QEMU
product_name: Standard PC (i440FX + PIIX, 1996)
product_version: pc-i440fx-2.8
chassis_vendor: QEMU
chassis_version: pc-i440fx-2.8
bios_vendor: SeaBIOS
bios_version: 1.14.0-2

** Loaded modules:
ipt_MASQUERADE
nf_conntrack_netlink
xfrm_user
xfrm_algo
nft_counter
nft_chain_nat_ipv4
nf_nat_ipv4
xt_addrtype
nft_compat
xt_conntrack
x_tables
nf_nat
nf_conntrack
nf_defrag_ipv6
nf_defrag_ipv4
libcrc32c
br_netfilter
bridge
stp
llc
nf_tables
devlink
nfnetlink
overlay
nfsd
auth_rpcgss
nfs_acl
nfs
lockd
grace
fscache
sunrpc
loop
kvm_intel
ttm
kvm
drm_kms_helper
irqbypass
virtio_rng
joydev
drm
evdev
rng_core
virtio_balloon
serio_raw
pcspkr
button
qemu_fw_cfg
ext4
crc16
mbcache
jbd2
crc32c_generic
fscrypto
ecb
crypto_simd
cryptd
glue_helper
aes_x86_64
hid_generic
usbhid
hid
virtio_net
net_failover
failover
virtio_blk
ata_generic
ata_piix
uhci_hcd
libata
ehci_hcd
usbcore
psmouse
usb_common
virtio_pci
virtio_ring
i2c_piix4
crc32c_intel
scsi_mod
virtio
floppy

** PCI devices:
00:00.0 Host bridge [0600]: Intel Corporation 440FX - 82441FX PMC [Natoma] 
[8086:1237] (rev 02)
Subsystem: Red Hat, Inc Qemu virtual machine [1af4:1100]
Control: I/O+ Mem+ BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR+ FastB2B- DisINTx-
Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- 
SERR- TAbort- 
SERR- TAbort- SERR- TAbort- 
SERR- TAbort- SERR- TAbort- SERR- 
Kernel driver in use: virtio-pci
Kernel modules: virtio_pci

00:04.0 SCSI storage controller [0100]: Red Hat, Inc Virtio block device 
[1af4:1001]
Subsystem: Red Hat, Inc Virtio block device [1af4:0002]
Physical Slot: 4
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR+ FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- 
Kernel driver in use: virtio-pci
Kernel modules: virtio_pci

00:05.0 Unclassified device [00ff]: Red Hat, Inc Virtio memory balloon 
[1af4:1002]
Subsystem: Red Hat, Inc Virtio memory balloon [1af4:0005]
Physical Slot: 5
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR+ FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- 
Kernel driver in use: virtio-pci
Kernel modules: virtio_pci

00:06.0 Unclassified device [00ff]: Red Hat, Inc Virtio RNG [1af4:1005]
Subsystem: Red Hat, Inc Virtio RNG [1af4:0004]
Physical Slot: 6
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR+ FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- 
Kernel driver in use: virtio-pci
Kernel modules: virtio_pci

00:07.0 Ethernet controller [0200]: Red Hat, Inc Virtio network device 
[1af4:1000]
Subsystem: Red Hat, Inc Virtio network device [1af4:0001]
Physical Slot: 7
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- 

Bug#1014198: deepin-movie-reborn: diff for NMU version 5.7.15-3.1

[Sebastian Ramacher]

Control: tags 1014198 + patch
Control: tags 1014198 + pending

Dear maintainer,

I've prepared an NMU for deepin-movie-reborn (versioned as 5.7.15-3.1) and
uploaded it to DELAYED/2. Please feel free to tell me if I
should delay it longer.

Cheers
-- 
Sebastian Ramacher
diff -Nru deepin-movie-reborn-5.7.15/debian/changelog deepin-movie-reborn-5.7.15/debian/changelog
--- deepin-movie-reborn-5.7.15/debian/changelog	2022-04-12 11:00:15.0 +0200
+++ deepin-movie-reborn-5.7.15/debian/changelog	2022-07-11 22:33:15.0 +0200
@@ -1,3 +1,11 @@
+deepin-movie-reborn (5.7.15-3.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * debian/control: Remove manual dependencies on libav* (Closes: #1014198)
+These dependencies are already added by ${shlibs:Depends}.
+
+ -- Sebastian Ramacher   Mon, 11 Jul 2022 22:33:15 +0200
+
 deepin-movie-reborn (5.7.15-3) unstable; urgency=medium
 
   * debian/patches:
diff -Nru deepin-movie-reborn-5.7.15/debian/control deepin-movie-reborn-5.7.15/debian/control
--- deepin-movie-reborn-5.7.15/debian/control	2022-04-12 09:48:53.0 +0200
+++ deepin-movie-reborn-5.7.15/debian/control	2022-07-11 22:33:14.0 +0200
@@ -47,9 +47,6 @@
 Package: deepin-movie
 Architecture: any
 Depends:
- libavcodec58 (>=7:4.0),
- libavformat58 (>=7:4.1),
- libavutil56 (>=7:4.0),
  libdmr0.1 (= ${binary:Version}),
  libffmpegthumbnailer4v5,
  libmpris-qt5-1 (>=0.1.0.1),
@@ -92,9 +89,6 @@
 Architecture: any
 Multi-Arch: same
 Depends:
- libavcodec58 (>=7:4.0),
- libavformat58 (>=7:4.1),
- libavutil56 (>=7:4.0),
  libffmpegthumbnailer4v5,
  libmpris-qt5-1 (>=0.1.0.1),
  libmpv1 (>=0.29),


signature.asc
Description: PGP signature

Processed: deepin-movie-reborn: diff for NMU version 5.7.15-3.1

[Debian Bug Tracking System]

Processing control commands:

> tags 1014198 + patch
Bug #1014198 [deepin-movie] deepin-movie: binary packages still depend on old 
libav* packages after rebuild.
Added tag(s) patch.
> tags 1014198 + pending
Bug #1014198 [deepin-movie] deepin-movie: binary packages still depend on old 
libav* packages after rebuild.
Added tag(s) pending.

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

Processed: tagging 1014785

[Debian Bug Tracking System]

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

> tags 1014785 + upstream
Bug #1014785 [src:dojo] dojo: CVE-2021-23450
Added tag(s) upstream.
> thanks
Stopping processing here.

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

Bug#1014785: dojo: CVE-2021-23450

[Moritz Mühlenhoff]

Source: dojo
X-Debbugs-CC: t...@security.debian.org
Severity: grave
Tags: security

Hi,

The following vulnerability was published for dojo.

CVE-2021-23450[0]:
| All versions of package dojo are vulnerable to Prototype Pollution via
| the setObject function.

https://github.com/advisories/GHSA-m8gw-hjpr-rjv7
Fixed by: 
https://github.com/dojo/dojo/commit/b7b8b279f3e082e9d4b54144fe831bdc77b2e0c9

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

Please adjust the affected versions in the BTS as needed.

Bug#1014784: libprimesieve10: unneccessary Provides+Conflicts renders shared library not-coinstallable

[Sebastian Ramacher]

Package: libprimesieve10
Version: 8.0+ds-1
Severity: serious
X-Debbugs-Cc: sramac...@debian.org
Justification: Policy §8

libprimesieve10 and libprimesieve9 both declare Provides+Conflicts:
libprimesieve. This causes the shared library packages libprimesieve10
and libprimesieve9 unable to be installed at the same time. This makes
the upgrade from bullseye to bookworm unnecessarily more complex.

Please remove the Provides+Conflicts.

Cheers
-- 
Sebastian Ramacher

Processed: tagging 1014780, tagging 1014779, tagging 1014778, tagging 1014777, tagging 1014774, tagging 1014776

[Debian Bug Tracking System]

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

> tags 1014780 + upstream
Bug #1014780 [src:ruby-kubeclient] ruby-kubeclient: CVE-2022-0759
Added tag(s) upstream.
> tags 1014779 + upstream
Bug #1014779 [src:angular.js] angular.js: CVE-2022-25844
Added tag(s) upstream.
> tags 1014778 + upstream
Bug #1014778 [src:gradle] gradle: CVE-2021-32751
Added tag(s) upstream.
> tags 1014777 + upstream
Bug #1014777 [src:libgig] libgig: CVE-2021-32294
Ignoring request to alter tags of bug #1014777 to the same tags previously set
> tags 1014774 + upstream
Bug #1014774 [src:jupyterhub] jupyterhub: CVE-2020-36191
Ignoring request to alter tags of bug #1014774 to the same tags previously set
> tags 1014776 + upstream
Bug #1014776 [src:tinyobjloader] tinyobjloader: CVE-2020-28589
Ignoring request to alter tags of bug #1014776 to the same tags previously set
> thanks
Stopping processing here.

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

Bug#1014781: momd crashing due to error in HypervisorInterfaces/libvirtInterface.py

[Huf]

Package: mom
Version: 0.6.0-2
Severity: grave
Tags: patch
Justification: renders package unusable

Hello Dear Maintainer,

Looks like momd is "broken" in bullseye :-(
Service is failling every start with exception :
Jul 11 20:48:21 minas-anor momd[149966]:   File 
"/usr/lib/python3/dist-packages/mom/HypervisorInterfaces/libvirtInterface.py", 
line 128, in _domainGetPid
Jul 11 20:48:21 minas-anor momd[149966]: matches = 
re.findall(r"^\s*(\d+)\s+.*" + uuid, p1, re.M)
Jul 11 20:48:21 minas-anor momd[149966]:   File 
"/usr/lib/python3.9/re.py", line 241, in findall
Jul 11 20:48:21 minas-anor momd[149966]: return _compile(pattern, 
flags).findall(string)
Jul 11 20:48:21 minas-anor momd[149966]: TypeError: cannot use a string 
pattern on a bytes-like object

Comparing with current code for libvirtInterface.py in mom github 
https://github.com/oVirt/mom/blob/master/mom/HypervisorInterfaces/libvirtInterface.py
I made modification in libvirtInterface.py line 128
#p1 = Popen(["ps", "axww"], stdout=PIPE).communicate()[0]
p1 = Popen(["ps", "axww"], stdout=PIPE).communicate()[0].decode("utf-8")

Sorry for not attaching a patch file, not sure it is needed for this change

After this little change momd is now working correctly and tacking care of VM 
ballooning :-)

For the moment, i'm only using KVM + momd + balloning on test servers
(that's why i only discovered the issue now)
don't know if some other users are impacted in production.
I suppose bug is related to python 3.9, but not shure at all

Think a little "patch" release will be needed for debian package


Thank you for your time maintaining debian :-))




Here more complete log extract if needed
Jul 11 20:48:21 minas-anor momd[149966]: 2022-07-11 20:48:21,840 - 
mom.GuestManager - ERROR - Guest Manager crashed
Jul 11 20:48:21 minas-anor momd[149966]: Traceback (most recent call last):
Jul 11 20:48:21 minas-anor momd[149966]:   File 
"/usr/lib/python3/dist-packages/mom/GuestManager.py", line 86, in run
Jul 11 20:48:21 minas-anor momd[149966]: 
self._spawn_guest_monitors(domain_list)
Jul 11 20:48:21 minas-anor momd[149966]:   File 
"/usr/lib/python3/dist-packages/mom/GuestManager.py", line 112, in 
_spawn_guest_monitors
Jul 11 20:48:21 minas-anor momd[149966]: info = 
self.hypervisor_iface.getVmInfo(id)
Jul 11 20:48:21 minas-anor momd[149966]:   File 
"/usr/lib/python3/dist-packages/mom/HypervisorInterfaces/libvirtInterface.py", 
line 189, in getVmInfo
Jul 11 20:48:21 minas-anor momd[149966]: data['pid'] = 
self._domainGetPid(data['uuid'])
Jul 11 20:48:21 minas-anor momd[149966]:   File 
"/usr/lib/python3/dist-packages/mom/HypervisorInterfaces/libvirtInterface.py", 
line 128, in _domainGetPid
Jul 11 20:48:21 minas-anor momd[149966]: matches = 
re.findall(r"^\s*(\d+)\s+.*" + uuid, p1, re.M)
Jul 11 20:48:21 minas-anor momd[149966]:   File "/usr/lib/python3.9/re.py", 
line 241, in findall
Jul 11 20:48:21 minas-anor momd[149966]: return _compile(pattern, 
flags).findall(string)
Jul 11 20:48:21 minas-anor momd[149966]: TypeError: cannot use a string pattern 
on a bytes-like object
Jul 11 20:48:26 minas-anor momd[149966]: 2022-07-11 20:48:26,825 - mom - ERROR 
- Thread 'GuestManager' has exited



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

Kernel: Linux 5.10.0-8-amd64 (SMP w/6 CPU threads)
Locale: LANG=en_IE.UTF-8, LC_CTYPE=en_IE.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_IE:en
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages mom depends on:
ii  libvirt-daemon 7.0.0-3
ii  libvirt-daemon-system  7.0.0-3
ii  procps 2:3.3.17-5
ii  python33.9.2-3
ii  python3-libvirt7.0.0-2
ii  python3-six1.16.0-2

mom recommends no packages.

mom suggests no packages.

-- Configuration Files:
/etc/momd.conf changed [not included]

-- no debconf information

Bug#1014780: ruby-kubeclient: CVE-2022-0759

[Moritz Mühlenhoff]

Source: ruby-kubeclient
X-Debbugs-CC: t...@security.debian.org
Severity: grave
Tags: security

Hi,

The following vulnerability was published for ruby-kubeclient.

CVE-2022-0759[0]:
| A flaw was found in all versions of kubeclient up to (but not
| including) v4.9.3, the Ruby client for Kubernetes REST API, in the way
| it parsed kubeconfig files. When the kubeconfig file does not
| configure custom CA to verify certs, kubeclient ends up accepting any
| certificate (it wrongly returns VERIFY_NONE). Ruby applications that
| leverage kubeclient to parse kubeconfig files are susceptible to Man-
| in-the-middle attacks (MITM).

https://bugzilla.redhat.com/show_bug.cgi?id=2058404
https://github.com/ManageIQ/kubeclient/issues/554
https://github.com/ManageIQ/kubeclient/pull/556
https://github.com/ManageIQ/kubeclient/issues/555
https://github.com/ManageIQ/kubeclient/pull/556

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

Please adjust the affected versions in the BTS as needed.

Bug#1014724: marked as done (FBTFS: test failure in t/connection.t)

[Debian Bug Tracking System]

Your message dated Mon, 11 Jul 2022 19:19:08 +
with message-id 
and subject line Bug#1014724: fixed in libmojo-sqlite-perl 3.009-2
has caused the Debian Bug report #1014724,
regarding FBTFS: test failure in t/connection.t
to be marked as done.

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

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


-- 
1014724: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1014724
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libmojo-sqlite-perl
Version: 3.001-2
Severity: serious
Tags: upstream ftbfs
Justification: fails to build from source

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

As seen on ci.debian.net, libmojo-sqlite-perl recently fails the
t/connection.t test:

Use of uninitialized value in string eq at 
/build/libmojo-sqlite-perl-3.009/blib/lib/Mojo/SQLite.pm line 70.

#   Failed test 'right data source'
#   at t/connection.t line 60.
#  got: 'dbi:SQLite:'
# expected: 'dbi:SQLite:dbname=/tmp/sqlite.db?#'
# Looks like you failed 1 test of 2.

#   Failed test 'Connection string with absolute filename and options'
#   at t/connection.t line 70.
# Looks like you failed 1 test of 9.
t/connection.t . 
# Subtest: Defaults
ok 1 - right data source
ok 2 - right options
1..2
ok 1 - Defaults
# Subtest: Minimal connection string with file
ok 1 - right data source
ok 2 - right options
1..2
ok 2 - Minimal connection string with file
# Subtest: Minimal connection string with in-memory database and option
ok 1 - right data source
ok 2 - right options
1..2
ok 3 - Minimal connection string with in-memory database and option
# Subtest: Connection string with absolute filename and options
not ok 1 - right data source
ok 2 - right options
1..2
not ok 4 - Connection string with absolute filename and options
# Subtest: Connection string with lots of zeros
ok 1 - right data source
ok 2 - right options
1..2
ok 5 - Connection string with lots of zeros
# Subtest: Parse filename
ok 1 - right data source
ok 2 - right options
1..2
ok 6 - Parse filename
# Subtest: Invalid connection string
ok 1 - right error
1..1
ok 7 - Invalid connection string
# Subtest: Legacy sqlite_unicode enabled
ok 1 - right data source
ok 2 - right options
1..2
ok 8 - Legacy sqlite_unicode enabled
# Subtest: Legacy sqlite_unicode disabled
ok 1 - right data source
ok 2 - right options
1..2
ok 9 - Legacy sqlite_unicode disabled
1..9
Dubious, test returned 1 (wstat 256, 0x100)
Failed 1/9 subtests 


Cf. 
https://ci.debian.net/data/autopkgtest/testing/amd64/libm/libmojo-sqlite-perl/23502612/log.gz


Maybe I'm wrong, but there's a coincidence with the recent upload of
URI 5.11 and some other test failures in other packages. And the
tests pass in testing (with URI 5.10).


Cheers,
gregor



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

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

-BEGIN PGP SIGNATURE-

iQKTBAEBCgB9FiEE0eExbpOnYKgQTYX6uzpoAYZJqgYFAmLLPqNfFIAALgAo
aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldEQx
RTEzMTZFOTNBNzYwQTgxMDREODVGQUJCM0E2ODAxODY0OUFBMDYACgkQuzpoAYZJ
qgbRJBAAxlelxC0jraJg7RiNk41sluNWDNX4LJF5t/CDegrlZ6KjksTKhTNXPKGy
NB9myFz7bRXGTVRD5MYoyToSRlW2lGEv0V7DItgUN39y2hkm0C7q7acBOwKhdSE+
VKFT0rWz7e2AaPx8cQW63jSYWM/XQa6iq/H7kyy9lWAtTCH8/xB56kRBAvIogI3e
9faVuIos6R7gATb/yUZO+Euvl/qwbS8guatEPNWXqRUPXdxp3lgQdTkG2qoxh7/Q
E90OS6ggfBTPmNkn0CmjPClenU0hfOCAzWckCQ2BbD4lWuqSBC2hy4/e/uswzHUI
A5PQ7exu4XJMgpVekxZvLqPwIx/ZKFqPMmbczXNh4uMNqtuy7AgYH+N0lDVhTmpt
umFqYJp+HatQnpHwdT6HW5V1eMTVWwbfmTm66M3EQo68J8dQYHbK+cyz2HnL4ypo
BQw1fhPEiLLsLgNuMqvHVW5e4Ag0E+r7w2YdwtgG/1QO/38tU19p0pKH7lUAU2O0
b73Fv5AjPCcGI0UPFkAJVOAhcz9jhLUdjrpHphSV8TB078saoS2T+vwhGWsFhOzI
dqur6jowhKMpDjYObYxGoPTCFwjCas/SpL18yYjgxP+27YD7bNI5cHKDt+bcz8+A
71DRD5UplQ6SEr+IZbsi4Odate5/HumiKNFODl7m7itn6tuDb4w=
=ZHOT
-END PGP SIGNATURE-
--- End Message ---
--- Begin Message ---
Source: libmojo-sqlite-perl
Source-Version: 3.009-2
Done: gregor herrmann 

We believe that the bug you reported is fixed in the latest version of

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

[Debian Bug Tracking System]

Your message dated Mon, 11 Jul 2022 19:19:00 +
with message-id 
and subject line Bug#1014720: fixed in libcpan-mini-inject-perl 0.35-4
has caused the Debian Bug report #1014720,
regarding FTBFS: test failure in t/update_mirror.t
to be marked as done.

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

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


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

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

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

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

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


Cheers,
gregor

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

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

-BEGIN PGP SIGNATURE-

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

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

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

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

Debian distribution maintenance software
pp.
gregor herrmann  (supplier of updated 
libcpan-mini-inject-perl package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Mon, 11 Jul 2022 20:55:16 +0200
Source: libcpan-mini-inject-perl
Architecture: source
Version: 0.35-4
Distribution: unstable
Urgency: medium
Maintainer: Debian Perl Group 
Changed-By: gregor herrmann 
Closes: 1014720
Changes:
 libcpan-mini-inject-perl (0.35-4) unstable; urgency=medium
 .
   * (Build-)Depend on working liburi-perl versions. (Closes: #1014720)
Checksums-Sha1:
 53b0c692e91cea00ff139454878a26242a1154cd 2873 
libcpan-mini-inject-perl_0.35-4.dsc
 1a3aaa052a101fc0a7ce8d95a0370cd6f2730a52 2528 
libcpan-mini-inject-perl_0.35-4.debian.tar.xz
Checksums-Sha256:
 f458a25e311437c322e77a88feb8cc2ce7adf558804d8972b1c908c86767daa3 2873 
libcpan-mini-inject-perl_0.35-4.dsc
 6a8df3de52d407cea30dae43e71e59cb49f744b92d87659c0486a0e44615db25 2528 
libcpan-mini-inject-perl_0.35-4.debian.tar.xz
Files:
 500ba60126d4b8b94f85a1771363aa81 2873 perl optional 
libcpan-mini-inject-perl_0.35-4.dsc
 

Bug#1014719: marked as done (FTBFS: test failures in t/FormatExternal.t)

[Debian Bug Tracking System]

Your message dated Mon, 11 Jul 2022 19:06:07 +
with message-id 
and subject line Bug#1014719: fixed in libhtml-formatexternal-perl 26-5
has caused the Debian Bug report #1014719,
regarding FTBFS: test failures in t/FormatExternal.t
to be marked as done.

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

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


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

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

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

#   Failed test 'HTML::FormatText::Elinks format_file() filename 
"/tmp/ohXWo1S_oR/-###"'
#   at t/FormatExternal.t line 321.
#   'Local directory 
/[1]build/[2]libhtml-formatexternal-perl-26/
#  
#  drwxr-xr-x   3 pbuilder pbuilder  4096 Jul 10 18:58 [3]..
#  drwxr-xr-x   2 pbuilder pbuilder  4096 Jul 10 18:56 [4].pc
#  drwxr-xr-x   8 pbuilder pbuilder  4096 Jul 10 18:58 [5]blib
#  drwxr-xr-x   6 pbuilder pbuilder  4096 Jul 10 18:58 [6]debian
#  drwxr-xr-x   2 pbuilder pbuilder  4096 Aug 29  2015 [7]devel
#  drwxr-xr-x   2 pbuilder pbuilder  4096 Aug 29  2015 [8]examples
#  drwxr-xr-x   2 pbuilder pbuilder  4096 Aug 29  2015 [9]inc
#  drwxr-xr-x   3 pbuilder pbuilder  4096 Aug 29  2015 [10]lib
#  drwxr-xr-x   2 pbuilder pbuilder  4096 Aug 29  2015 [11]t
#  drwxr-xr-x   2 pbuilder pbuilder  4096 Aug 29  2015 [12]xt
#  drwxr-xr-x   2 pbuilder pbuilder  4096 Aug 29  2015 [13]xtools
#  -rw-r--r--   1 pbuilder pbuilder 35068 Jun 29  2007 [14]COPYING
#  -rw-r--r--   1 pbuilder pbuilder  2294 Aug 29  2015 [15]Changes
#  -rw-r--r--   1 pbuilder pbuilder  1241 Aug 29  2015 [16]MANIFEST
#  -rw-r--r--   1 pbuilder pbuilder  3104 Nov 15  2013 [17]MANIFEST.SKIP
#  -rw-r--r--   1 pbuilder pbuilder  1547 Aug 29  2015 [18]META.json
#  -rw-r--r--   1 pbuilder pbuilder   853 Aug 29  2015 [19]META.yml
#  -rw-r--r--   1 pbuilder pbuilder  1582 Jul 10 18:58 [20]MYMETA.json
#  -rw-r--r--   1 pbuilder pbuilder   893 Jul 10 18:58 [21]MYMETA.yml
#  -rw-r--r--   1 pbuilder pbuilder 34293 Jul 10 18:58 [22]Makefile
#  -rwxr-xr-x   1 pbuilder pbuilder  2558 Apr 23  2015 [23]Makefile.PL
#  -rw-r--r--   1 pbuilder pbuilder  1684 Jun  5  2013 [24]README
#  -rw-r--r--   1 pbuilder pbuilder  4390 Aug 29  2015 [25]SIGNATURE
#  -rw-r--r--   1 pbuilder pbuilder 0 Jul 10 18:58 [26]pm_to_blib
#
#--
#
# References
#
#Visible links
#1. file:///build/
#2. file:///build/libhtml-formatexternal-perl-26/
#3. file:///build/
#4. file:///build/libhtml-formatexternal-perl-26/.pc/
#5. file:///build/libhtml-formatexternal-perl-26/blib/
#6. file:///build/libhtml-formatexternal-perl-26/debian/
#7. file:///build/libhtml-formatexternal-perl-26/devel/
#8. file:///build/libhtml-formatexternal-perl-26/examples/
#9. file:///build/libhtml-formatexternal-perl-26/inc/
#   10. file:///build/libhtml-formatexternal-perl-26/lib/
#   11. file:///build/libhtml-formatexternal-perl-26/t/
#   12. file:///build/libhtml-formatexternal-perl-26/xt/
#   13. file:///build/libhtml-formatexternal-perl-26/xtools/
#   14. file:///build/libhtml-formatexternal-perl-26/COPYING
#   15. file:///build/libhtml-formatexternal-perl-26/Changes
#   16. file:///build/libhtml-formatexternal-perl-26/MANIFEST
#   17. file:///build/libhtml-formatexternal-perl-26/MANIFEST.SKIP
#   18. file:///build/libhtml-formatexternal-perl-26/META.json
#   19. file:///build/libhtml-formatexternal-perl-26/META.yml
#   20. file:///build/libhtml-formatexternal-perl-26/MYMETA.json
#   21. file:///build/libhtml-formatexternal-perl-26/MYMETA.yml
#   22. file:///build/libhtml-formatexternal-perl-26/Makefile
#   23. file:///build/libhtml-formatexternal-perl-26/Makefile.PL
#   24. file:///build/libhtml-formatexternal-perl-26/README
#   25. file:///build/libhtml-formatexternal-perl-26/SIGNATURE
#   26. file:///build/libhtml-formatexternal-perl-26/pm_to_blib
# '
# doesn't match '(?^:body.*text)'

etc.

Cf. 
https://ci.debian.net/data/autopkgtest/unstable/amd64/libh/libhtml-formatexternal-perl/23466975/log.gz


Cheers,
gregor


- -- System Information:
Debian Release: bookworm/sid
  APT prefers unstable
  APT policy: (990, 'unstable'), (500, 'unstable-debug'), (500, 

Bug#1014265: marked as done (libslopy-dev,libslopy7.6: missing Breaks+Replaces: slop (<< 7.6-2))

[Debian Bug Tracking System]

Your message dated Mon, 11 Jul 2022 18:35:28 +
with message-id 
and subject line Bug#1014265: fixed in slop 7.6-3
has caused the Debian Bug report #1014265,
regarding libslopy-dev,libslopy7.6: missing Breaks+Replaces: slop (<< 7.6-2)
to be marked as done.

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

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


-- 
1014265: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1014265
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libslopy-dev,libslopy7.6
Version: 7.6-2
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

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

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

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

  Preparing to unpack .../libslopy7.6_7.6-2_amd64.deb ...
  Unpacking libslopy7.6 (7.6-2) ...
  dpkg: error processing archive 
/var/cache/apt/archives/libslopy7.6_7.6-2_amd64.deb (--unpack):
   trying to overwrite '/usr/lib/x86_64-linux-gnu/libslopy.so.7.6', which is 
also in package slop 7.6-1+b1
  Errors were encountered while processing:
   /var/cache/apt/archives/libslopy7.6_7.6-2_amd64.deb

  Preparing to unpack .../libslopy-dev_7.6-2_amd64.deb ...
  Unpacking libslopy-dev (7.6-2) ...
  dpkg: error processing archive 
/var/cache/apt/archives/libslopy-dev_7.6-2_amd64.deb (--unpack):
   trying to overwrite '/usr/include/slop.hpp', which is also in package slop 
7.6-1+b1
  Errors were encountered while processing:
   /var/cache/apt/archives/libslopy-dev_7.6-2_amd64.deb


libslopy-dev is also missing a
  Depends: libslopy7.6 (= ${binary:Version})


cheers,

Andreas


slop=7.6-1+b1_libslopy-dev=7.6-2.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: slop
Source-Version: 7.6-3
Done: Antoine Beaupré 

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

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

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

Debian distribution maintenance software
pp.
Antoine Beaupré  (supplier of updated slop 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, 11 Jul 2022 14:09:52 -0400
Source: slop
Architecture: source
Version: 7.6-3
Distribution: unstable
Urgency: medium
Maintainer: Antoine Beaupré 
Changed-By: Antoine Beaupré 
Closes: 1014265
Changes:
 slop (7.6-3) unstable; urgency=medium
 .
   * upload to unstable
   * fix upgrade from monolith slop package, thanks georgesk (Closes: #1014265)
Checksums-Sha1:
 097a836df3013f08f6eb06aa9143042702287295 1643 slop_7.6-3.dsc
 6c9cb5072be0e8a527784672ae0297557ce58333 4820 slop_7.6-3.debian.tar.xz
 1a0c469439e60108cc2303d23c590c4f8f905324 9293 slop_7.6-3_amd64.buildinfo
Checksums-Sha256:
 b2dbe47f8746eac2db7cf20f76de8d2eed363368a6d17ff7863cfc7d7ec040d2 1643 
slop_7.6-3.dsc
 a75ad185f187332b1392a01c1826224234b49547ab2e433c505d4a934f939c16 4820 
slop_7.6-3.debian.tar.xz
 0223e6c027e6e284603f6aa0b5e23c44f8a8e20294173320e58c428b5f6584a7 9293 
slop_7.6-3_amd64.buildinfo
Files:
 462fd78cae4a02442fb53466e9fa0163 1643 x11 optional slop_7.6-3.dsc
 2b2d0b5d3620948ac39de14e4d6ad481 4820 x11 optional slop_7.6-3.debian.tar.xz
 e04bd788cc9a8d3cf15686b0f2d982be 9293 x11 optional slop_7.6-3_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQEzBAEBCAAdFiEEexZCBNCWcjsBljWrPqHd3bJh2XsFAmLMaKcACgkQPqHd3bJh
2XvMQAf+KoFYPLAFw9CR6wKEs+6vePRVYZkedI8g1Oe9mqpTwPFBQUIOiXCUG5p0
kbo+2rwP+Eyt0SciQ9Xy6/H5r6hOiFL7rp17F26Sa7IA/OlfskBdiGRn9zJte4Jf
BqGd/IxKDg6Rh7oBcXHKXHJ/SACwjj+GduG+bQUChphGBsOWh6iQXY2F2+Ionxu4
/CIeDSdIyQso9GOUXNqPaiZ8RaNDfKSIpc2Pw4Pn/ICZfq7BiwlAesdnRRT0R5iN
wWuehV+x81/KHFoC2LbAaBaArqxfm6v7Hpkv23ujU1taQ50Rbmps9uPU0XQFmsdp
0Dto6uQi9kxt1CMHzXQP2euxiAHGUQ==
=M15Q
-END PGP SIGNATURE End Message ---

Bug#1013526: libtickit-widget-scrollbox-perl: FTBFS: dh_auto_test: error: /usr/bin/perl Build test --verbose 1 returned exit code 255

[Niko Tyni]

On Sun, Jul 03, 2022 at 05:20:17PM +0300, Niko Tyni wrote:
> On Sat, Jun 25, 2022 at 10:09:46AM +0300, Damyan Ivanov wrote:
> > Control: retitle -1 libtickit-widget-scrollbox-perl: intermittent memory 
> > corruption in t/02input-key.t and t/03input-mouse.t
> > 
> > I can reproduce this when running 02input-key.t and 03input-key.t in 
> > a loop. The symptom is the same - "malloc_consolidate(): unaligned 
> > fastbin chunk detected" error message and the tests exits with Wstat 
> > 134 after saying "All 14 subtests passed".
> > 
> > Wstat 134 is SIGABRT. Looks like a memory corruption of some sort.
> 
> We're seeing this too in Perl 5.36 test rebuilds. Possibly it's even
> more reproducible there, seems to always fail for us.
> 
>   
> http://perl.debian.net/rebuild-logs/perl-5.36-throwaway/libtickit-widget-scrollbox-perl_0.11-1/libtickit-widget-scrollbox-perl_0.11-1_amd64-2022-06-14T06:54:08Z.build

Update: I was able to build it on perl_5.36.0-2 / amd64, so
apparently no real Perl 5.36 relation after all.
-- 
Niko

Processed: Re: Bug#1014286: perl/experimental: FTBFS on mips64el: test failures

[Debian Bug Tracking System]

Processing control commands:

> severity -1 normal
Bug #1014286 [src:perl] perl/experimental: FTBFS on mips64el: test failures
Severity set to 'normal' from 'serious'

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

Bug#1014286: perl/experimental: FTBFS on mips64el: test failures

[Niko Tyni]

Control: severity -1 normal

On Sun, Jul 03, 2022 at 10:41:16PM +0300, Niko Tyni wrote:
> On Sun, Jul 03, 2022 at 04:29:22PM +0300, Niko Tyni wrote:
> > Source: perl
> > Version: 5.36.0-1
> > Severity: serious
> > Tags: ftbfs
> > User: debian-p...@lists.debian.org
> > Usertags: perl-5.36-transition
> > X-Debbugs-Cc: debian-m...@lists.debian.org
> > 
> > The perl package in experimental fails to build from source
> > on mips64el.
> > 
> >   https://buildd.debian.org/status/package.php?p=perl=experimental
> > 
> > It looks like the perl binary dies with SIGSEGV in thread related tests
> > during the test suite. This happened twice on different buildds.
> > 
> > I'm running a test build now on eller.d.o to see if it's reproducible.
> 
> The package builds fine for me on eller, though it failed twice in the
> same way on the buildds (mipsel-osuosl-0[13]).
> 
> @debian-mips: any ideas? Could somebody please check if the package
> builds for you?

We now have two successful builds on mips64el buildds, so presumably
this is not a regression in perl.

Lowering the severity for now.
-- 
Niko Tyni   nt...@debian.org

Bug#1014730: liburi-perl: Breaks apt-cacher with "Can't locate Regexp/IPv6.pm" error

[Niko Tyni]

[apt-cacher maintainers: the context here is that URI.pm introduced an
optional dependency on Regexp::IPv6 by requiring it in an eval block,
but the apt-cacher __DIE__ handler exits when the require fails.]

On Mon, Jul 11, 2022 at 05:35:17PM +0200, gregor herrmann wrote:

> So we have:
> - do nothing
> - patch URI to restart the default signal handler in the eval
> - (reassign? and) do something in apt-cacher

I'm not really sure if there's a consensus on best practices around
$SIG{__DIE__}.  IMO apt-cacher is the one that should be fixed, rather
than demanding that all the modules it uses need to reset and restore
$SIG{__DIE__} before catching exceptions.

>From 'perldoc -f die' :

You can arrange for a callback to be run just before the "die"
does its deed, by setting the $SIG{__DIE__} hook. The associated
handler is called with the exception as an argument, and can
change the exception, if it sees fit, by calling "die" again.
See "%SIG" in perlvar for details on setting %SIG entries, and
"eval" for some examples. Although this feature was to be run only
right before your program was to exit, this is not currently so:
the $SIG{__DIE__} hook is currently called even inside "eval"ed
blocks/strings! If one wants the hook to do nothing in such
situations, put

die @_ if $^S;

as the first line of the handler (see "$^S" in perlvar). Because
this promotes strange action at a distance, this counterintuitive
behavior may be fixed in a future release.

Corresponding untested patch against apt-cacher attached.
-- 
Niko Tyni   nt...@debian.org
>From 33013c19088fa3a43e468ef41aa0d1298e63d233 Mon Sep 17 00:00:00 2001
From: Niko Tyni 
Date: Mon, 11 Jul 2022 21:18:43 +0300
Subject: [PATCH] Handle eval blocks in unsuspecting libraries

$SIG{__DIE__} can get called from eval blocks - don't bail out if so.

Bug-Debian: https://bugs.debian.org/1014730
---
 apt-cacher | 1 +
 1 file changed, 1 insertion(+)

diff --git a/apt-cacher b/apt-cacher
index a8c00cb..8c1fe88 100755
--- a/apt-cacher
+++ b/apt-cacher
@@ -1253,6 +1253,7 @@ sub write_error_log {
 }
 
 sub die_handler {
+die @_ if $^S; # called from an eval block
 my ($msg) = @_;
 write_error_log("error [$$]: $msg");
 sendrsp(HTTP::Response->new(502, 'apt-cacher internal error (died)', ['Connection' => 'close'])) if $con;
-- 
2.30.2

Bug#1014768: gnuradio: FTBFS on mipsel: undefined reference to `__atomic_load_8'

[Sebastian Ramacher]

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

https://buildd.debian.org/status/fetch.php?pkg=gnuradio=mipsel=3.10.3.0-1=1657488517=0

FAILED: gr-blocks/lib/blocks_qa_block_tags.cc 
: && /usr/bin/c++ -g -O2 -ffile-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
-D_FORTIFY_SOURCE=2 -fvisibility=hidden -Wsign-compare -Wall -Wno-uninitialized 
-fcx-limited-range -O3 -DNDEBUG -Wl,-z,relro 
gr-blocks/lib/CMakeFiles/blocks_qa_block_tags.cc.dir/qa_block_tags.cc.o -o 
gr-blocks/lib/blocks_qa_block_tags.cc  
-Wl,-rpath,/<>/obj-mipsel-linux-gnu/gr-blocks/lib:/<>/obj-mipsel-linux-gnu/gnuradio-runtime/lib:/<>/obj-mipsel-linux-gnu/gnuradio-runtime/lib/pmt
  gr-blocks/lib/libgnuradio-blocks.so.3.10.3.0  
/usr/lib/mipsel-linux-gnu/libboost_unit_test_framework.so.1.74.0  
gnuradio-runtime/lib/libgnuradio-runtime.so.3.10.3.0  
gnuradio-runtime/lib/pmt/libgnuradio-pmt.so.3.10.3.0  
/usr/lib/mipsel-linux-gnu/libboost_program_options.so.1.74.0  
/usr/lib/mipsel-linux-gnu/libboost_thread.so.1.74.0  
/usr/lib/mipsel-linux-gnu/libboost_atomic.so.1.74.0  
/usr/lib/mipsel-linux-gnu/libspdlog.so.1.9.2  -lpthread  
/usr/lib/mipsel-linux-gnu/libfmt.so.8.1.1  -Wl,--as-needed  
/usr/lib/mipsel-linux-gnu/libgmpxx.so  /usr/lib/mipsel-linux-gnu/libgmp.so  
-lrt  /usr/lib/mipsel-linux-gnu/libvolk.so.2.5.1  -ldl  -lm  
/usr/lib/mipsel-linux-gnu/libsndfile.so && :
/usr/bin/ld: gr-blocks/lib/libgnuradio-blocks.so.3.10.3.0: undefined reference 
to `__atomic_load_8'
/usr/bin/ld: gr-blocks/lib/libgnuradio-blocks.so.3.10.3.0: undefined reference 
to `__atomic_store_8'
collect2: error: ld returned 1 exit status
[403/1743] /usr/bin/c++ -DBOOST_ALL_NO_LIB -DBOOST_ATOMIC_DYN_LINK 
-DBOOST_PROGRAM_OPTIONS_DYN_LINK -DBOOST_TEST_DYN_LINK -DBOOST_TEST_MAIN 
-DBOOST_THREAD_DYN_LINK -DBOOST_UNIT_TEST_FRAMEWORK_DYN_LINK -DFMT_LOCALE 
-DFMT_SHARED -DGR_MPLIB_GMP -DGR_PERFORMANCE_COUNTERS -DHAVE_SF_FORMAT_OPUS 
-DSPDLOG_COMPILED_LIB -DSPDLOG_FMT_EXTERNAL -DSPDLOG_SHARED_LIB 
-I/<>/gr-blocks/lib/../include 
-I/<>/gnuradio-runtime/lib/../include 
-I/<>/obj-mipsel-linux-gnu/gnuradio-runtime/lib/../include 
-I/<>/gnuradio-runtime/lib/pmt/../../include -isystem 
/usr/include/python3.10 -g -O2 -ffile-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
-D_FORTIFY_SOURCE=2 -fvisibility=hidden -Wsign-compare -Wall -Wno-uninitialized 
-fcx-limited-range -O3 -DNDEBUG -std=c++17 -MD -MT 
gr-blocks/lib/CMakeFiles/blocks_qa_gr_flowgraph.cc.dir/qa_gr_flowgraph.cc.o -MF 
gr-blocks/lib/CMakeFiles/blocks_qa_gr_flowgraph.cc.dir/qa_gr_flowgraph.cc.o.d 
-o gr-blocks/lib/CMakeFiles/blocks_qa_gr_flowgraph.cc.dir/qa_gr_flowgraph.cc.o 
-c /<>/gr-blocks/lib/qa_gr_flowgraph.cc
[404/1743] /usr/bin/c++ -DBOOST_ALL_NO_LIB -DBOOST_ATOMIC_DYN_LINK 
-DBOOST_PROGRAM_OPTIONS_DYN_LINK -DBOOST_TEST_DYN_LINK -DBOOST_TEST_MAIN 
-DBOOST_THREAD_DYN_LINK -DBOOST_UNIT_TEST_FRAMEWORK_DYN_LINK -DFMT_LOCALE 
-DFMT_SHARED -DGR_MPLIB_GMP -DGR_PERFORMANCE_COUNTERS -DHAVE_SF_FORMAT_OPUS 
-DSPDLOG_COMPILED_LIB -DSPDLOG_FMT_EXTERNAL -DSPDLOG_SHARED_LIB 
-I/<>/gr-blocks/lib/../include 
-I/<>/gnuradio-runtime/lib/../include 
-I/<>/obj-mipsel-linux-gnu/gnuradio-runtime/lib/../include 
-I/<>/gnuradio-runtime/lib/pmt/../../include -isystem 
/usr/include/python3.10 -g -O2 -ffile-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
-D_FORTIFY_SOURCE=2 -fvisibility=hidden -Wsign-compare -Wall -Wno-uninitialized 
-fcx-limited-range -O3 -DNDEBUG -std=c++17 -MD -MT 
gr-blocks/lib/CMakeFiles/blocks_qa_gr_hier_block2_derived.cc.dir/qa_gr_hier_block2_derived.cc.o
 -MF 
gr-blocks/lib/CMakeFiles/blocks_qa_gr_hier_block2_derived.cc.dir/qa_gr_hier_block2_derived.cc.o.d
 -o 
gr-blocks/lib/CMakeFiles/blocks_qa_gr_hier_block2_derived.cc.dir/qa_gr_hier_block2_derived.cc.o
 -c /<>/gr-blocks/lib/qa_gr_hier_block2_derived.cc
[405/1743] /usr/bin/c++ -DBOOST_ALL_NO_LIB -DBOOST_ATOMIC_DYN_LINK 
-DBOOST_PROGRAM_OPTIONS_DYN_LINK -DBOOST_TEST_DYN_LINK -DBOOST_TEST_MAIN 
-DBOOST_THREAD_DYN_LINK -DBOOST_UNIT_TEST_FRAMEWORK_DYN_LINK -DFMT_LOCALE 
-DFMT_SHARED -DGR_MPLIB_GMP -DGR_PERFORMANCE_COUNTERS -DHAVE_SF_FORMAT_OPUS 
-DSPDLOG_COMPILED_LIB -DSPDLOG_FMT_EXTERNAL -DSPDLOG_SHARED_LIB 
-I/<>/gr-blocks/lib/../include 
-I/<>/gnuradio-runtime/lib/../include 
-I/<>/obj-mipsel-linux-gnu/gnuradio-runtime/lib/../include 
-I/<>/gnuradio-runtime/lib/pmt/../../include -isystem 
/usr/include/python3.10 -g -O2 -ffile-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
-D_FORTIFY_SOURCE=2 -fvisibility=hidden -Wsign-compare -Wall -Wno-uninitialized 
-fcx-limited-range -O3 -DNDEBUG -std=c++17 -MD -MT 
gr-blocks/lib/CMakeFiles/blocks_qa_gr_top_block.cc.dir/qa_gr_top_block.cc.o -MF 
gr-blocks/lib/CMakeFiles/blocks_qa_gr_top_block.cc.dir/qa_gr_top_block.cc.o.d 
-o 

Bug#1012674: NMU: zlib: contrib/testzlib included (lintian: source-ships-excluded-file)

[Mark Brown]

On Mon, Jul 11, 2022 at 06:54:13PM +0200, Bastian Germann wrote:
> Am 11.07.22 um 18:40 schrieb Mark Brown:
> > On Mon, Jul 11, 2022 at 06:16:31PM +0200, Bastian Germann wrote:

> > > I have uploaded zlib 1.2.12.dfsg-0.1 with the changes attached to 
> > > DELAYED/3.

> > Why?  Please drop this.

> Okay. When are you going to address this bug then?
> It has been a month not reacting to the RC bug.
> I think this is not acceptable for a key package such as zlib.

I'm not sure what there is to react to here other than doing an upload;
it's a packaging thing more than something causing active breakage for
users and we're nowhere near to doing a release yet so there didn't seem
a huge sense of urgency here so I'd been going to roll it into packaging
the new upstream release.  The bug gives the air of being from an audit
and in those cases you do have to balance keeping people up to date with
creating noise for submitters and there's been no followup requests for
status or anything.

I have been hoping that we're going to get another upstream release
which rolls in some of the fixes for the string of problems that people
have been having with the security fix release that was recently done
though that is looking depressingly unlikely and so I need to figure out
what needs backporting.  Given the release schedule startng to kick off
at the beginning of next year it'll be some time this year, I'd guess
some time this quarter.

In any case this upload isn't a targetted fix for the individual issue,
it's got a whole bunch of other unrelated changes including a new
upstream release which are clearly out of scope.  Like I say I have
substantial concerns about the new upstream release so that having been
rolled in is especially worrying.


signature.asc
Description: PGP signature

Bug#990428: bonding now completely broken

[Dirk Jost]

Hiya,

since roughly last week bonding is completely broken for me, whatever way I’m 
using it. Neither via the slave or the master option it works now.
Is there any new synthax, we are supposed to use?

Cheers,
Dirk.

Gesendet von Mail für Windows

Bug#1012674: NMU: zlib: contrib/testzlib included (lintian: source-ships-excluded-file)

[Bastian Germann]

Am 11.07.22 um 18:40 schrieb Mark Brown:

On Mon, Jul 11, 2022 at 06:16:31PM +0200, Bastian Germann wrote:


I have uploaded zlib 1.2.12.dfsg-0.1 with the changes attached to DELAYED/3.


Why?  Please drop this.


Okay. When are you going to address this bug then?
It has been a month not reacting to the RC bug.
I think this is not acceptable for a key package such as zlib.

Bug#1012674: NMU: zlib: contrib/testzlib included (lintian: source-ships-excluded-file)

[Mark Brown]

On Mon, Jul 11, 2022 at 06:16:31PM +0200, Bastian Germann wrote:

> I have uploaded zlib 1.2.12.dfsg-0.1 with the changes attached to DELAYED/3.

Why?  Please drop this.  


signature.asc
Description: PGP signature

Processed: Re: Bug#1014735: rpcsvc-proto: The /usr/include/rpc/* files is not included

[Debian Bug Tracking System]

Processing control commands:

> tag -1 + moreinfo
Bug #1014735 [rpcsvc-proto] rpcsvc-proto: The /usr/include/rpc/* files is not 
included
Added tag(s) moreinfo.

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

Bug#1014735: rpcsvc-proto: The /usr/include/rpc/* files is not included

[Aurelien Jarno]

control: tag -1 + moreinfo

Hi,

On 2022-07-11 02:46, Magnus Danielson wrote:
> Package: rpcsvc-proto
> Version: 1.4.2-4
> Severity: grave
> Justification: renders package unusable

rpcsvc-proto is used to build many packages in Debian, so I doubt it is
completely unusable.

> Dear Maintainer,
> 
> Template answers first, for your convenience.
> 
>    * What led up to the situation?
> 
> Rebuilding an application using rpcgen.
> 
>    * What exactly did you do (or not do) that was effective (or
>  ineffective)?
> 
> Run rpcgen, then tried to compile the produced files.
> 
>    * What was the outcome of this action?
> 
> Any of the /usr/include/rpc/* header-files referenced such as
> #include 
> etc. fail to include, all the related definitions missing causes large
> amount
> of compile errors.

Could you please give me more details about the issue? Ideally copy and
paste the error message.

My guess is that your problem is not related to rpcsvc-proto itself
which just provides rpcgen and related header files, but with the
removal of the SunRPC implementation for glibc. You need to switch to
the TI RPC implementation instead (using the libtirpc-dev package).

>    * What outcome did you expect instead?
> 
> Nice compile as headerfiles is found.
> 
> This is most likely a consequence of repackaging the rpc-part. Looking back
> at
> the stable version of libc6 the header files is there in libc6-dev, but for
> testing and unstable they are not. I expect that using these this would
> work.
> If the headerfiles is in another package, dependence on that should be in
> place.

The files that are removed from libc6-dev are the ones related to the
removed SunRPC implementation. libc6-dev (indirectly) depends on
libtirpc3-dev so the replacement header files should be available on
your system. That said it is not a one to one replacement, so you need
to use pkgconfig to get the compile and link flags.

> Package-testing should actually include a dummy-application that generates
> through rpcgen and then compiles it successfully. Then this error would be
> caught. Another approach would be to check that the same header files gets
> installed from previous packaging and new packaging. Both methods would be
> recommended to create fail-safes and quick turn-around for package
> maintainers.

Don't hesitate to provide a patch doing that.

Regards
Aurelien

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

Bug#1014741: libgd-perl: GD and GD2 image formats are disabled in libgd3 package

[gregor herrmann]

Control: tag -1 - moreinfo + confirmed ftbfs
Control: severity -1 serious

On Mon, 11 Jul 2022 11:02:10 +0200, gregor herrmann wrote:

> I have to admit that I'm a bit confused: It is filed against libgd-perl
> and you mention a Graph.pm file -- but such a file doesn't exist in
> this package.
> 
> Could you please clarify which exact error you are seein in which
> exact file (and maybe in which exact package)?

Thanks for reassigning to libgd-graph-perl!

I also note that the tests (which use the samples (which call the export_format
function (which has line 515 of Graph.pm))) also fail by now:

#   Failed test at t/samples.t line 21.
# died: gdImageGdPtr error at 
/build/libgd-graph-perl-1.54~ds/blib/lib/GD/Graph.pm line 515.
# Compilation failed in require at t/samples.t line 17.

#   Failed test at t/samples.t line 21.
# died: gdImageGdPtr error at 
/build/libgd-graph-perl-1.54~ds/blib/lib/GD/Graph.pm line 515.
# Compilation failed in require at t/samples.t line 17.

#   Failed test at t/samples.t line 21.
# died: gdImageGdPtr error at 
/build/libgd-graph-perl-1.54~ds/blib/lib/GD/Graph.pm line 515.
# Compilation failed in require at t/samples.t line 17.

#   Failed test at t/samples.t line 21.
# died: gdImageGdPtr error at 
/build/libgd-graph-perl-1.54~ds/blib/lib/GD/Graph.pm line 515.
# Compilation failed in require at t/samples.t line 17.

#   Failed test at t/samples.t line 21.
# died: gdImageGdPtr error at 
/build/libgd-graph-perl-1.54~ds/blib/lib/GD/Graph.pm line 515.
# Compilation failed in require at t/samples.t line 17.

#   Failed test at t/samples.t line 21.
# died: gdImageGdPtr error at 
/build/libgd-graph-perl-1.54~ds/blib/lib/GD/Graph.pm line 515.
# Compilation failed in require at t/samples.t line 17.

#   Failed test at t/samples.t line 21.
# died: gdImageGdPtr error at 
/build/libgd-graph-perl-1.54~ds/blib/lib/GD/Graph.pm line 515.
# Compilation failed in require at t/samples.t line 17.

#   Failed test at t/samples.t line 21.
# died: gdImageGdPtr error at 
/build/libgd-graph-perl-1.54~ds/blib/lib/GD/Graph.pm line 515.
# Compilation failed in require at t/samples.t line 17.

#   Failed test at t/samples.t line 21.
# died: gdImageGdPtr error at 
/build/libgd-graph-perl-1.54~ds/blib/lib/GD/Graph.pm line 515.
# Compilation failed in require at t/samples.t line 17.

#   Failed test at t/samples.t line 21.
# died: gdImageGdPtr error at 
/build/libgd-graph-perl-1.54~ds/blib/lib/GD/Graph.pm line 515.
# Compilation failed in require at t/samples.t line 17.

#   Failed test at t/samples.t line 21.
# died: gdImageGdPtr error at 
/build/libgd-graph-perl-1.54~ds/blib/lib/GD/Graph.pm line 515.
# Compilation failed in require at t/samples.t line 17.

#   Failed test at t/samples.t line 21.
# died: gdImageGdPtr error at 
/build/libgd-graph-perl-1.54~ds/blib/lib/GD/Graph.pm line 515.
# Compilation failed in require at t/samples.t line 17.

#   Failed test at t/samples.t line 21.
# died: gdImageGdPtr error at 
/build/libgd-graph-perl-1.54~ds/blib/lib/GD/Graph.pm line 515.
# Compilation failed in require at t/samples.t line 17.

#   Failed test at t/samples.t line 21.
# died: gdImageGdPtr error at 
/build/libgd-graph-perl-1.54~ds/blib/lib/GD/Graph.pm line 515.
# Compilation failed in require at t/samples.t line 17.

#   Failed test at t/samples.t line 21.
# died: gdImageGdPtr error at 
/build/libgd-graph-perl-1.54~ds/blib/lib/GD/Graph.pm line 515.
# Compilation failed in require at t/samples.t line 17.

#   Failed test at t/samples.t line 21.
# died: gdImageGdPtr error at 
/build/libgd-graph-perl-1.54~ds/blib/lib/GD/Graph.pm line 515.
# Compilation failed in require at t/samples.t line 17.

#   Failed test at t/samples.t line 21.
# died: gdImageGdPtr error at 
/build/libgd-graph-perl-1.54~ds/blib/lib/GD/Graph.pm line 515.
# Compilation failed in require at t/samples.t line 17.

#   Failed test at t/samples.t line 21.
# died: gdImageGdPtr error at 
/build/libgd-graph-perl-1.54~ds/blib/lib/GD/Graph.pm line 515.
# Compilation failed in require at t/samples.t line 17.

#   Failed test at t/samples.t line 21.
# died: gdImageGdPtr error at 
/build/libgd-graph-perl-1.54~ds/blib/lib/GD/Graph.pm line 515.
# Compilation failed in require at t/samples.t line 17.

#   Failed test at t/samples.t line 21.
# died: gdImageGdPtr error at 
/build/libgd-graph-perl-1.54~ds/blib/lib/GD/Graph.pm line 515.
# Compilation failed in require at t/samples.t line 17.

#   Failed test at t/samples.t line 21.
# died: gdImageGdPtr error at 
/build/libgd-graph-perl-1.54~ds/blib/lib/GD/Graph.pm line 515.
# Compilation failed in require at t/samples.t line 17.

#   Failed test at t/samples.t line 21.
# died: gdImageGdPtr error at 
/build/libgd-graph-perl-1.54~ds/blib/lib/GD/Graph.pm line 515.
# Compilation failed in require at t/samples.t line 17.

#   Failed test at t/samples.t line 21.
# died: gdImageGdPtr error at 
/build/libgd-graph-perl-1.54~ds/blib/lib/GD/Graph.pm line 515.
# Compilation failed in require at t/samples.t line 17.

# 

Processed: Re: Bug#1014741: libgd-perl: GD and GD2 image formats are disabled in libgd3 package

[Debian Bug Tracking System]

Processing control commands:

> tag -1 - moreinfo + confirmed ftbfs
Bug #1014741 [libgd-graph-perl] libgd-perl: GD and GD2 image formats are 
disabled in libgd3 package
Removed tag(s) moreinfo.
Bug #1014741 [libgd-graph-perl] libgd-perl: GD and GD2 image formats are 
disabled in libgd3 package
Added tag(s) confirmed and ftbfs.
> severity -1 serious
Bug #1014741 [libgd-graph-perl] libgd-perl: GD and GD2 image formats are 
disabled in libgd3 package
Severity set to 'serious' from 'grave'

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

Bug#1011747: marked as done (pyjwt: CVE-2022-29217 - Key confusion through non-blocklisted public key formats)

[Debian Bug Tracking System]

Your message dated Mon, 11 Jul 2022 15:34:17 +
with message-id 
and subject line Bug#1011747: fixed in pyjwt 2.4.0-1
has caused the Debian Bug report #1011747,
regarding pyjwt: CVE-2022-29217 - Key confusion through non-blocklisted public 
key formats
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.)


-- 
1011747: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1011747
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: pyjwt
Version: 2.3.0-1
Severity: important
Tags: security upstream
X-Debbugs-Cc: codeh...@debian.org, Debian Security Team 


Hi,

The following vulnerability was published for pyjwt.

CVE-2022-29217[0]:
| PyJWT is a Python implementation of RFC 7519. PyJWT supports multiple
| different JWT signing algorithms. With JWT, an attacker submitting the
| JWT token can choose the used signing algorithm. The PyJWT library
| requires that the application chooses what algorithms are supported.
| The application can specify `jwt.algorithms.get_default_algorithms()`
| to get support for all algorithms, or specify a single algorithm. The
| issue is not that big as
| `algorithms=jwt.algorithms.get_default_algorithms()` has to be used.
| Users should upgrade to v2.4.0 to receive a patch for this issue. As a
| workaround, always be explicit with the algorithms that are accepted
| and expected when decoding.


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

Please adjust the affected versions in the BTS as needed.




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

Kernel: Linux 5.17.0-2-amd64 (SMP w/6 CPU threads; PREEMPT)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_GB:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
--- End Message ---
--- Begin Message ---
Source: pyjwt
Source-Version: 2.4.0-1
Done: Daniele Tricoli 

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

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Mon, 11 Jul 2022 17:16:24 +0200
Source: pyjwt
Architecture: source
Version: 2.4.0-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Team 
Changed-By: Daniele Tricoli 
Closes: 1011747
Changes:
 pyjwt (2.4.0-1) unstable; urgency=medium
 .
   * New upstream version 2.4.0
 - Fixes CVE-2022-29217 (Closes: #1011747)
   * Enable salsa pipelines.
   * Fix typo on debian/NEWS.
   * debian/control
 - Bump Standards-Version to 4.6.1 (no changes needed).
   * debian/copyright
 - Update copyright years.
Checksums-Sha1:
 2e358c3fad0330dd976e1258346800e655d0f893 2196 pyjwt_2.4.0-1.dsc
 3880207fdf0db1eeadf976092c8fbf80a7335c24 66327 pyjwt_2.4.0.orig.tar.gz
 c495d6b280a2f6354ad6c18986b1c7d653953bdf 4388 pyjwt_2.4.0-1.debian.tar.xz
 ff50e73b305122bbbffa1d15e745d29483ed8bae 7532 pyjwt_2.4.0-1_amd64.buildinfo
Checksums-Sha256:
 ae8563cb8f49a9fb79dd60dd1a4c1015e6e5b9c646accbeabcfad80935dedfcd 2196 
pyjwt_2.4.0-1.dsc
 d42908208c699b3b973cbeb01a969ba6a96c821eefb1c5bfe4c390c01d67abba 66327 
pyjwt_2.4.0.orig.tar.gz
 6b8427713fb94c84785c0dcb3399a09441049f46f045d559ad354ba9a30eb43a 4388 
pyjwt_2.4.0-1.debian.tar.xz
 b70b5a7955b32c82a31dad8cae9c5946ae013750dc1cce7284b5c8beb0e39991 7532 
pyjwt_2.4.0-1_amd64.buildinfo
Files:
 df5c58f58609cc7dfb1706994218a33d 2196 python optional pyjwt_2.4.0-1.dsc
 665f444d7805e36826bb09ce6434e73a 66327 python optional pyjwt_2.4.0.orig.tar.gz
 34d5cadfbaf1f7a1ef1b788f468fa24c 4388 python optional 
pyjwt_2.4.0-1.debian.tar.xz
 6e223aea94745d20f9e22a1523a06597 7532 python optional 
pyjwt_2.4.0-1_amd64.buildinfo

-BEGIN PGP SIGNATURE-

Processed: found 1014741 in 1.54~ds-3

[Debian Bug Tracking System]

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

> found 1014741 1.54~ds-3
Bug #1014741 [libgd-graph-perl] libgd-perl: GD and GD2 image formats are 
disabled in libgd3 package
Marked as found in versions libgd-graph-perl/1.54~ds-3.
> thanks
Stopping processing here.

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

Bug#1014730: liburi-perl: Breaks apt-cacher with "Can't locate Regexp/IPv6.pm" error

[gregor herrmann]

Thanks for your investigations and mails, that makes it a bit clearer
for me :)

Still, I'm not sure how to proceed:


On Mon, 11 Jul 2022 11:11:16 +0100, Niko Tyni wrote:

> apt-cacher is using $SIG{__DIE__}, which triggers even in eval blocks,
> and doing an exit(1) from there.
[…]
> I'd say this is not a bug in liburi-perl.


On Mon, 11 Jul 2022 12:15:12 +0200, Robert Luberda wrote:

> Yes, but it looks like apt-cacher seems to set its own SIG{__DIE__} handler.
[…]
> I've just checked that adding
>   local $SIG{__DIE__};
> here (i.e. before the require line) fixes the issue with apt-cacher for me.

Thanks!
 
> > But may as well move libregexp-ipv6-perl to Depends, I guess.
> Probably yes, but IMHO it would be better to restore default __DIE__
> handler.

Hm, ok …


So we have:
- do nothing
- patch URI to restart the default signal handler in the eval
- (reassign? and) do something in apt-cacher


Cheers,
gregor


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


signature.asc
Description: Digital Signature

Processed: reassigning #1014741

[Debian Bug Tracking System]

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

> reassign 1014741 libgd-graph-perl
Bug #1014741 [libgd-perl] libgd-perl: GD and GD2 image formats are disabled in 
libgd3 package
Bug reassigned from package 'libgd-perl' to 'libgd-graph-perl'.
No longer marked as found in versions libgd-perl/2.76-2.
Ignoring request to alter fixed versions of bug #1014741 to the same values 
previously set
> quit
Stopping processing here.

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

Bug#1011747: pyjwt: CVE-2022-29217 - Key confusion through non-blocklisted public key formats

[Daniele Tricoli]

Hello Neil,

On 26/05/2022 11:40, Neil Williams wrote:

Source: pyjwt
Version: 2.3.0-1
Severity: important
Tags: security upstream
X-Debbugs-Cc: codeh...@debian.org, Debian Security Team 


Hi,

The following vulnerability was published for pyjwt.

CVE-2022-29217[0]:

[CUT]

Thanks for the report, I'm working on this.

Cheers,

--
Daniele Tricoli
https://mornie.org

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

[Debian Bug Tracking System]

Your message dated Mon, 11 Jul 2022 13:24:48 +
with message-id 
and subject line Bug#1013569: fixed in nitime 0.9-3
has caused the Debian Bug report #1013569,
regarding nitime: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i 
python{version} -p "3.9 3.10" 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.)


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

Hi,

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


Relevant part (hopefully):
>  debian/rules binary
> dh binary --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:239: python3.9 setup.py config 
> running config
> I: pybuild base:239: python3.10 setup.py config 
> running config
>dh_auto_build -O--buildsystem=pybuild
> I: pybuild base:239: /usr/bin/python3.9 setup.py build 
> running build
> running build_py
> creating /<>/.pybuild/cpython3_3.9/build/nitime
> copying nitime/__init__.py -> 
> /<>/.pybuild/cpython3_3.9/build/nitime
> copying nitime/index_utils.py -> 
> /<>/.pybuild/cpython3_3.9/build/nitime
> copying nitime/_mpl_units.py -> 
> /<>/.pybuild/cpython3_3.9/build/nitime
> copying nitime/viz.py -> /<>/.pybuild/cpython3_3.9/build/nitime
> copying nitime/descriptors.py -> 
> /<>/.pybuild/cpython3_3.9/build/nitime
> copying nitime/timeseries.py -> 
> /<>/.pybuild/cpython3_3.9/build/nitime
> copying nitime/lazy.py -> /<>/.pybuild/cpython3_3.9/build/nitime
> copying nitime/version.py -> 
> /<>/.pybuild/cpython3_3.9/build/nitime
> copying nitime/lazyimports.py -> 
> /<>/.pybuild/cpython3_3.9/build/nitime
> copying nitime/utils.py -> /<>/.pybuild/cpython3_3.9/build/nitime
> creating /<>/.pybuild/cpython3_3.9/build/nitime/analysis
> copying nitime/analysis/spectral.py -> 
> /<>/.pybuild/cpython3_3.9/build/nitime/analysis
> copying nitime/analysis/__init__.py -> 
> /<>/.pybuild/cpython3_3.9/build/nitime/analysis
> copying nitime/analysis/base.py -> 
> /<>/.pybuild/cpython3_3.9/build/nitime/analysis
> copying nitime/analysis/correlation.py -> 
> /<>/.pybuild/cpython3_3.9/build/nitime/analysis
> copying nitime/analysis/event_related.py -> 
> /<>/.pybuild/cpython3_3.9/build/nitime/analysis
> copying nitime/analysis/granger.py -> 
> /<>/.pybuild/cpython3_3.9/build/nitime/analysis
> copying nitime/analysis/normalization.py -> 
> /<>/.pybuild/cpython3_3.9/build/nitime/analysis
> copying nitime/analysis/coherence.py -> 
> /<>/.pybuild/cpython3_3.9/build/nitime/analysis
> copying nitime/analysis/snr.py -> 
> /<>/.pybuild/cpython3_3.9/build/nitime/analysis
> creating /<>/.pybuild/cpython3_3.9/build/nitime/fmri
> copying nitime/fmri/__init__.py -> 
> /<>/.pybuild/cpython3_3.9/build/nitime/fmri
> copying nitime/fmri/hrf.py -> 
> /<>/.pybuild/cpython3_3.9/build/nitime/fmri
> copying nitime/fmri/io.py -> 
> /<>/.pybuild/cpython3_3.9/build/nitime/fmri
> creating /<>/.pybuild/cpython3_3.9/build/nitime/algorithms
> copying nitime/algorithms/spectral.py -> 
> /<>/.pybuild/cpython3_3.9/build/nitime/algorithms
> copying nitime/algorithms/__init__.py -> 
> /<>/.pybuild/cpython3_3.9/build/nitime/algorithms
> copying nitime/algorithms/cohere.py -> 
> /<>/.pybuild/cpython3_3.9/build/nitime/algorithms
> copying nitime/algorithms/correlation.py -> 
> /<>/.pybuild/cpython3_3.9/build/nitime/algorithms
> copying nitime/algorithms/autoregressive.py -> 
> /<>/.pybuild/cpython3_3.9/build/nitime/algorithms
> copying nitime/algorithms/filter.py -> 
> /<>/.pybuild/cpython3_3.9/build/nitime/algorithms
> copying nitime/algorithms/event_related.py -> 
> /<>/.pybuild/cpython3_3.9/build/nitime/algorithms
> copying nitime/algorithms/entropy.py -> 
> /<>/.pybuild/cpython3_3.9/build/nitime/algorithms
> copying nitime/algorithms/wavelet.py -> 
> /<>/.pybuild/cpython3_3.9/build/nitime/algorithms
> creating /<>/.pybuild/cpython3_3.9/build/nitime/tests
> copying nitime/tests/__init__.py -> 
> /<>/.pybuild/cpython3_3.9/build/nitime/tests
> copying nitime/tests/test_descriptors.py -> 
> /<>/.pybuild/cpython3_3.9/build/nitime/tests
> copying nitime/tests/test_lazy.py -> 
> /<>/.pybuild/cpython3_3.9/build/nitime/tests
> copying nitime/tests/test_utils.py -> 
> /<>/.pybuild/cpython3_3.9/build/nitime/tests
> copying 

Bug#1013569: marked as pending in nitime

[Nilesh Patra]

Control: tag -1 pending

Hello,

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

https://salsa.debian.org/med-team/nitime/-/commit/7a00bbef2ca98f1fdb2b977dbe9355cc97c62d39


Add patch to not set ws lower bound to zero (Closes: #1013569)


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1013569

Processed: Bug#1013569 marked as pending in nitime

[Debian Bug Tracking System]

Processing control commands:

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

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

Processed: severity of 1011747 is grave

[Debian Bug Tracking System]

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

> severity 1011747 grave
Bug #1011747 [src:pyjwt] pyjwt: CVE-2022-29217 - Key confusion through 
non-blocklisted public key formats
Severity set to 'grave' from 'important'
> thanks
Stopping processing here.

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

Processed: severity of 1009926 is grave

[Debian Bug Tracking System]

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

> severity 1009926 grave
Bug #1009926 [src:ruby-git] ruby-git: CVE-2022-25648
Severity set to 'grave' from 'important'
> thanks
Stopping processing here.

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

Bug#1014751: libgpaste-2-common: missing Breaks: libgpaste-common

[Andreas Beckmann]

Package: libgpaste-2-common
Version: 42.1-3
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts replaces-without-breaks

Hi,

during a test with piuparts and DOSE tools I noticed your package causes
removal of files that also belong to another package.
This is caused by using Replaces without corresponding Breaks.

The installation sequence to reproduce this problem is

  apt-get install libgpaste-common/bullseye
  # (1)
  apt-get install libgpaste-2-common/bookworm
  apt-get remove libgpaste-2-common
  # (2)

The list of installed files at points (1) and (2) should be identical,
but the following files have disappeared:

  /usr/share/locale/*/LC_MESSAGES/GPaste.mo


This is a serious bug violating policy 7.6, see
https://www.debian.org/doc/debian-policy/ch-relationships.html#overwriting-files-and-replacing-packages-replaces
and also see the footnote that describes this incorrect behavior:
https://www.debian.org/doc/debian-policy/ch-relationships.html#id13

The libgpaste-2-common package has the following relationships with 
libgpaste-common:

  Conflicts: n/a
  Breaks:n/a
  Replaces:  libgpaste-common

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

0m24.0s ERROR: FAIL: After purging files have disappeared:
  /usr/share/locale/de/LC_MESSAGES/GPaste.mo owned by: libgpaste-2-common
  /usr/share/locale/es/LC_MESSAGES/GPaste.mo owned by: libgpaste-2-common
  /usr/share/locale/fr/LC_MESSAGES/GPaste.mo owned by: libgpaste-2-common
  /usr/share/locale/ja/LC_MESSAGES/GPaste.mo owned by: libgpaste-2-common
  /usr/share/locale/nb_NO/LC_MESSAGES/GPaste.mo  owned by: libgpaste-2-common
  /usr/share/locale/nl_NL/LC_MESSAGES/GPaste.mo  owned by: libgpaste-2-common
  /usr/share/locale/pt_BR/LC_MESSAGES/GPaste.mo  owned by: libgpaste-2-common
  /usr/share/locale/sv/LC_MESSAGES/GPaste.mo owned by: libgpaste-2-common

0m24.0s ERROR: FAIL: After purging files have been modified:
  /var/lib/dpkg/info/libgpaste-common.list   not owned


cheers,

Andreas


libgpaste-common=3.38.5-1_libgpaste-2-common=42.1-3.log.gz
Description: application/gzip

Bug#1014750: xfce4-notes-plugin: fails to build twice in a row

[Andreas Beckmann]

Source: xfce4-notes-plugin
Version: 1.9.0-1
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)

Hi,

xfce4-notes-plugin/experimental fails to build twice in a row.
Cleaning after the successful first build seems to remove some sources
that cannot be regenerated.

Building the source package after the successful first build (and
subsequent debian/rules clean) reports:

 dpkg-source -b .
dpkg-source: info: using source format '3.0 (quilt)'
dpkg-source: info: building xfce4-notes-plugin using existing 
./xfce4-notes-plugin_1.9.0.orig.tar.bz2
dpkg-source: warning: ignoring deletion of file configure.ac, use 
--include-removal to override
dpkg-source: warning: ignoring deletion of file Makefile.in, use 
--include-removal to override
dpkg-source: warning: ignoring deletion of file missing, use --include-removal 
to override
dpkg-source: warning: ignoring deletion of file compile, use --include-removal 
to override
dpkg-source: warning: ignoring deletion of file config.h.in, use 
--include-removal to override
dpkg-source: warning: ignoring deletion of file configure, use 
--include-removal to override
dpkg-source: warning: ignoring deletion of file ltmain.sh, use 
--include-removal to override
dpkg-source: warning: ignoring deletion of file install-sh, use 
--include-removal to override
dpkg-source: warning: ignoring deletion of file aclocal.m4, use 
--include-removal to override
dpkg-source: warning: ignoring deletion of file depcomp, use --include-removal 
to override
dpkg-source: warning: ignoring deletion of file data/Makefile.in, use 
--include-removal to override
dpkg-source: warning: ignoring deletion of file data/pixmaps/Makefile.in, use 
--include-removal to override
dpkg-source: warning: ignoring deletion of file data/icons/Makefile.in, use 
--include-removal to override
dpkg-source: warning: ignoring deletion of file 
data/icons/scalable/Makefile.in, use --include-removal to override
dpkg-source: warning: ignoring deletion of file data/icons/32x32/Makefile.in, 
use --include-removal to override
dpkg-source: warning: ignoring deletion of file data/icons/24x24/Makefile.in, 
use --include-removal to override
dpkg-source: warning: ignoring deletion of file data/icons/22x22/Makefile.in, 
use --include-removal to override
dpkg-source: warning: ignoring deletion of file data/icons/16x16/Makefile.in, 
use --include-removal to override
dpkg-source: warning: ignoring deletion of file data/gtk-3.0/Makefile.in, use 
--include-removal to override
dpkg-source: warning: ignoring deletion of file src/Makefile.in, use 
--include-removal to override
dpkg-source: warning: ignoring deletion of file lib/icon-button.c, use 
--include-removal to override
dpkg-source: warning: ignoring deletion of file lib/Makefile.in, use 
--include-removal to override
dpkg-source: warning: ignoring deletion of file lib/hypertextview.c, use 
--include-removal to override
dpkg-source: warning: ignoring deletion of file lib/note.c, use 
--include-removal to override
dpkg-source: warning: ignoring deletion of file lib/theme-gtkcss.c, use 
--include-removal to override
dpkg-source: warning: ignoring deletion of file lib/window.c, use 
--include-removal to override
dpkg-source: warning: ignoring deletion of file lib/application.c, use 
--include-removal to override
dpkg-source: warning: ignoring deletion of file lib/theme.c, use 
--include-removal to override
dpkg-source: warning: ignoring deletion of file lib/window-monitor.c, use 
--include-removal to override
dpkg-source: warning: newly created empty file 'po/.intltool-merge-cache.lock' 
will not be represented in diff
dpkg-source: info: building xfce4-notes-plugin in 
xfce4-notes-plugin_1.9.0-1.debian.tar.xz
dpkg-source: info: building xfce4-notes-plugin in xfce4-notes-plugin_1.9.0-1.dsc

The deletion of configure.ac and lib/*.c looks very suspicious ...
A following debian/rules build is a no-op (no build system is
autodetected) and then dh_install fails due to an empty debian/tmp tree.

 debian/rules build
dh build
   dh_update_autotools_config
   dh_autoreconf
   create-stamp debian/debhelper-build-stamp
 fakeroot debian/rules binary
dh binary
   dh_testroot
   dh_prep
   debian/rules override_dh_install
make[1]: Entering directory '/build/xfce4-notes-plugin-1.9.0'
rm -rf debian/tmp/usr/lib/x86_64-linux-gnu/xfce4/panel/plugins/*.la
dh_install
dh_install: warning: Cannot find (any matches for) "etc" (tried in ., 
debian/tmp)
...


Andreas


xfce4-notes-plugin_1.9.0-1_twice.log.gz
Description: application/gzip

Bug#1014749: Acknowledgement (openvswitch-test,python3-openvswitch: both ship /usr/lib/python3/dist-packages/ovstest/*.py)

[Andreas Beckmann]

openvswitch/experimental fails to clean after a successful build:

 debian/rules clean
py3versions: no X-Python3-Version in control file, using supported versions
dh clean
   debian/rules execute_before_dh_auto_clean
make[1]: Entering directory '/build/openvswitch-2.17.2'
py3versions: no X-Python3-Version in control file, using supported versions
find . -name "*.pyc" -delete
make[1]: Leaving directory '/build/openvswitch-2.17.2'
   dh_autoreconf_clean
   dh_clean
rm: cannot remove './_debian': Is a directory
rm: cannot remove './_dpdk': Is a directory
dh_clean: error: rm -f -- debian/openvswitch-common.substvars 
debian/openvswitch-doc.substvars debian/openvswitch-ipsec.substvars 
debian/openvswitch-ipsec.postrm.debhelper debian/openvswitch-pki.substvars 
debian/openvswitch-source.substvars debian/openvswitch-switch.substvars 
debian/openvswitch-switch.postrm.debhelper 
debian/openvswitch-switch-dpdk.substvars debian/openvswitch-test.substvars 
debian/openvswitch-test.postinst.debhelper 
debian/openvswitch-test.prerm.debhelper 
debian/openvswitch-testcontroller.substvars debian/openvswitch-vtep.substvars 
debian/python3-openvswitch.substvars 
debian/python3-openvswitch.postinst.debhelper 
debian/python3-openvswitch.prerm.debhelper ./_debian ./_dpdk debian/files 
returned exit code 1
make: *** [debian/rules:7: clean] Error 25

Looks like you are missing some trailing '/' in debian/clean
denoting directory trees to be removed.


Andreas

Bug#1014749: openvswitch-test,python3-openvswitch: both ship /usr/lib/python3/dist-packages/ovstest/*.py

[Andreas Beckmann]

Package: openvswitch-test,python3-openvswitch
Version: 2.17.2-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package failed to install
because it tries to overwrite other packages files.

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

  Selecting previously unselected package python3-openvswitch.
  Preparing to unpack .../python3-openvswitch_2.17.2-1_all.deb ...
  Unpacking python3-openvswitch (2.17.2-1) ...
  dpkg: error processing archive 
/var/cache/apt/archives/python3-openvswitch_2.17.2-1_all.deb (--unpack):
   trying to overwrite '/usr/lib/python3/dist-packages/ovstest/__init__.py', 
which is also in package openvswitch-test 2.17.2-1
  Errors were encountered while processing:
   /var/cache/apt/archives/python3-openvswitch_2.17.2-1_all.deb


cheers,

Andreas


openvswitch-test=2.17.2-1_python3-openvswitch=2.17.2-1.log.gz
Description: application/gzip

Processed: fixed 1012795 in 3.0.1-1

[Debian Bug Tracking System]

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

> fixed 1012795 3.0.1-1
Bug #1012795 {Done: Wartan Hachaturow } 
[libengine-gost-openssl1.1] libengine-gost-openssl1.1: Shared library file in /
Marked as fixed in versions libengine-gost-openssl/3.0.1-1.
> thanks
Stopping processing here.

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

Bug#1014747: node-jest-debbundle: mising Breaks+Replaces: jest (<< 28.1.2~)

[Andreas Beckmann]

Package: node-jest-debbundle
Version: 28.1.2~ds+~cs70.48.26-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package fails to upgrade from
'bullseye'.
It installed fine in 'bullseye', then the upgrade to 'bookworm' fails
because it tries to overwrite other packages files without declaring a
Breaks+Replaces relation.

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

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

  Preparing to unpack .../node-jest-debbundle_28.1.2~ds+~cs70.48.26-1_all.deb 
...
  Unpacking node-jest-debbundle (28.1.2~ds+~cs70.48.26-1) over 
(26.6.3+repack+~cs64.44.39-3) ...
  dpkg: error processing archive 
/var/cache/apt/archives/node-jest-debbundle_28.1.2~ds+~cs70.48.26-1_all.deb 
(--unpack):
   trying to overwrite 
'/usr/share/nodejs/@bcoe/v8-coverage/dist/lib/ascii.d.ts', which is also in 
package jest 26.6.3+repack+~cs64.44.39-3
  Errors were encountered while processing:
   /var/cache/apt/archives/node-jest-debbundle_28.1.2~ds+~cs70.48.26-1_all.deb


cheers,

Andreas


jest=26.6.3+repack+~cs64.44.39-3_node-jest-debbundle=28.1.2~ds+~cs70.48.26-1.log.gz
Description: application/gzip

Bug#1014730: liburi-perl: Breaks apt-cacher with "Can't locate Regexp/IPv6.pm" error

[Robert Luberda]

gregor herrmann pisze:


I'm a bit surprised, because the new code in 5.11 should behave
better if Regexp::IPv6 is not available:


Yes, but it looks like apt-cacher seems to set its own SIG{__DIE__} handler.



+our $IPv6_re;
+
+sub _looks_like_raw_ip6_address {
+  my $addr = shift;
+
+  if ( !$IPv6_re ) { #-- lazy / runs once / use Regexp::IPv6 if installed
+eval {


I've just checked that adding

  local $SIG{__DIE__};

here (i.e. before the require line) fixes the issue with apt-cacher for me.


+  require Regexp::IPv6;
+  Regexp::IPv6->import( qw($IPv6_re) );
+  1;
+}  ||  do { $IPv6_re = qr/[:0-9a-f]{3,}/; }; #-- fallback: unambitious 
guess




But may as well move libregexp-ipv6-perl to Depends, I guess.


Probably yes, but IMHO it would be better to restore default __DIE__ 
handler.


Regards,
robert

Bug#1014730: liburi-perl: Breaks apt-cacher with "Can't locate Regexp/IPv6.pm" error

[Niko Tyni]

On Mon, Jul 11, 2022 at 10:36:30AM +0200, gregor herrmann wrote:
> On Mon, 11 Jul 2022 00:12:11 +0200, Robert Luberda wrote:

> > The following information is printed into apt-cacher.log:
> > Mon Jul 11 00:02:52 2022|error [18513]: Can't locate Regexp/IPv6.pm in @INC 
> > (you may need to install the Regexp::
> > IPv6 module)
> 
> Thanks for your bug report.
> 
> I'm a bit surprised, because the new code in 5.11 should behave
> better if Regexp::IPv6 is not available:

apt-cacher is using $SIG{__DIE__}, which triggers even in eval blocks,
and doing an exit(1) from there.

  https://sources.debian.org/src/apt-cacher/1.7.26/apt-cacher/#L2251

  https://sources.debian.org/src/apt-cacher/1.7.26/apt-cacher/#L1259

I'd say this is not a bug in liburi-perl.
-- 
Niko Tyni   nt...@debian.org

Bug#1014417: meson: test changes causes FTBFS

[Jeremy Bicha]

Control: forwarded -1 https://github.com/mesonbuild/meson/issues/10577

I linked an upstream meson issue.
See also https://github.com/mesonbuild/meson/issues/10563

A large merge proposal is at
https://github.com/mesonbuild/meson/pull/10580

Jeremy

Bug#1014681: glewlwyd: Add build dependency to node-react-dom

[Nicolas Mora]

10 juill. 2022 10 h 45 min 13 s Yadd :

> Source: glewlwyd
> Version: 2.7.1-1
> Severity: important
> 
> Hi,
> 
> node-react is going to be split into multiple packages. Please add build
> dependency to node-react-dom to fix test.
> This can be done right now since current node-react provides
> node-react-dom virtual package.
> 
> Regards,
> Yadd
Thanks Yadd for notifying

I won't be able to upload a new package for the next 3 weeks though.

If the package glewlwyd will ftbfs until then, can someone in the team upload a 
fixed package? Otherwise, I'll make the fix in August.

/Nicolas

Processed: Re: meson: test changes causes FTBFS

[Debian Bug Tracking System]

Processing control commands:

> forwarded -1 https://github.com/mesonbuild/meson/issues/10577
Bug #1014417 [src:meson] meson: test changes causes FTBFS
Set Bug forwarded-to-address to 
'https://github.com/mesonbuild/meson/issues/10577'.

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

Bug#1014730: marked as done (liburi-perl: Breaks apt-cacher with "Can't locate Regexp/IPv6.pm" error)

[Debian Bug Tracking System]

Your message dated Mon, 11 Jul 2022 09:19:47 +
with message-id 
and subject line Bug#1014730: fixed in liburi-perl 5.12-1
has caused the Debian Bug report #1014730,
regarding liburi-perl: Breaks apt-cacher with "Can't locate Regexp/IPv6.pm" 
error
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.)


-- 
1014730: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1014730
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: liburi-perl
Version: 5.11-1
Severity: serious
Justification: Policy 7.2
Control: affects -1 apt-cacher

After recent upgrade I've noticed that apt-cached does no longer work:
 Err:2 http://apt-testing.vox:3142/apt-cacher/debian bookworm InRelease 

   502  apt-cacher internal error (died) [IP: 127.0.0.1 3142]

The following information is printed into apt-cacher.log:
Mon Jul 11 00:02:52 2022|error [18513]: Can't locate Regexp/IPv6.pm in @INC 
(you may need to install the Regexp::
IPv6 module) (@INC contains: /usr/share/apt-cacher/lib /etc/perl 
/usr/local/lib/x86_64-linux-gnu/perl/5.34.0 /usr
 /local/share/perl/5.34.0 /usr/lib/x86_64-linux-gnu/perl5/5.34 /usr/share/perl5 
/usr/lib/x86_64-linux-gnu/perl-bas
e /usr/lib/x86_64-linux-gnu/perl/5.34 /usr/share/perl/5.34 
/usr/local/lib/site_perl) at /usr/share/perl5/URI/_gen
eric.pm line 25.

Downgrading liburi-perl to 5.10 fixes the issue.

Regards,
robert


-- System Information:
Debian Release: bookworm/sid
  APT prefers unstable-debug
Architecture: amd64 (x86_64)
Foreign Architectures: i386

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

Versions of packages liburi-perl depends on:
ii  perl  5.34.0-5

liburi-perl recommends no packages.

Versions of packages liburi-perl suggests:
pn  libbusiness-isbn-perl  
pn  libregexp-ipv6-perl
ii  libwww-perl6.67-1

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: liburi-perl
Source-Version: 5.12-1
Done: gregor herrmann 

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

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

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

Debian distribution maintenance software
pp.
gregor herrmann  (supplier of updated liburi-perl package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Mon, 11 Jul 2022 10:41:18 +0200
Source: liburi-perl
Architecture: source
Version: 5.12-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Perl Group 
Changed-By: gregor herrmann 
Closes: 1014730
Changes:
 liburi-perl (5.12-1) unstable; urgency=medium
 .
   * Import upstream version 5.12.
   * Move libregexp-ipv6-perl to Depends.
 Thanks to Robert Luberda for the bug report.
 (Closes: #1014730)
   * Also add it as a test dependency, to have the same environment.
Checksums-Sha1:
 a0d0f39f1b36ef679058671a95436a4058c70edb 2406 liburi-perl_5.12-1.dsc
 74721a0f49498af11aea58590d8f8d0bdda6085d 114641 liburi-perl_5.12.orig.tar.gz
 ffc826f99017c4ee78183e53984c4d858f91b783 6324 liburi-perl_5.12-1.debian.tar.xz
Checksums-Sha256:
 dc48a28bd71de118e9746316799d34317a7b072eb8928f41ea432d573a1dd661 2406 
liburi-perl_5.12-1.dsc
 66abe0eaddd76b74801ecd28ec1411605887550fc0a45ef6aa744fdad768d9b3 114641 
liburi-perl_5.12.orig.tar.gz
 927a5d3bc9f842f6debf6aa545bdeb14402818dbfa263ffa0626024697aaa6a0 6324 
liburi-perl_5.12-1.debian.tar.xz
Files:
 bb49825c6fb2849d1bebd7ec99642732 2406 perl optional liburi-perl_5.12-1.dsc
 d7fc1b1c88d03357aed2f03b455a223e 114641 perl optional 
liburi-perl_5.12.orig.tar.gz
 ea63296f975999641a7cdda63410fc16 6324 perl optional 
liburi-perl_5.12-1.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQKTBAEBCgB9FiEE0eExbpOnYKgQTYX6uzpoAYZJqgYFAmLL5H9fFIAALgAo
aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldEQx
RTEzMTZFOTNBNzYwQTgxMDREODVGQUJCM0E2ODAxODY0OUFBMDYACgkQuzpoAYZJ
qgZLjhAAh4BIdeie6XfGFaQOgkuhNsFRADAvAM/RCnTyiW+c3gtadD/GmH1C5FYq
oOTnoan+m1CvIzhnEp9Rt0YGdVJWU9ETyBnZdMhlhI++LrrEn1Ox63A2LPtzkFLw

Processed: Re: Bug#1014741: libgd-perl: GD and GD2 image formats are disabled in libgd3 package

[Debian Bug Tracking System]

Processing control commands:

> tag -1 + moreinfo
Bug #1014741 [libgd-perl] libgd-perl: GD and GD2 image formats are disabled in 
libgd3 package
Added tag(s) moreinfo.

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

Bug#1014741: libgd-perl: GD and GD2 image formats are disabled in libgd3 package

[gregor herrmann]

Control: tag -1 + moreinfo

On Sun, 10 Jul 2022 23:26:04 -0500, Guyang Mao wrote:

> Package: libgd-perl
> Version: 2.76-2+b1
> Severity: grave
> Justification: renders package unusable
> 
> Graph.pm contains code that specifies file formats "gd" and "gd2" which are
> currently disabled in Debian's libgd3 package (these are actually obsolete
> formats, apparently, and only used in testing scenarios according to cursory
> googling).  Attempting to use libgd-perl will always result in an error at 
> line
> 515 in Graph.pm and likely elsewhere.
> 
> Removing gd and gd2 as options from line 515 (and elsewhere as needed) renders
> client uses of this library functional again.

Thanks for your bug report.

I have to admit that I'm a bit confused: It is filed against libgd-perl
and you mention a Graph.pm file -- but such a file doesn't exist in
this package.

Could you please clarify which exact error you are seein in which
exact file (and maybe in which exact package)?


Cheers,
gregor

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


signature.asc
Description: Digital Signature

Bug#1014745: thunderbird: Using "Reply All" is sometimes removing all Cc recipients

[Carsten Schoenert]

Package: thunderbird
Version: 1:102.0.1-1
Severity: grave
Tags: upstream
Justification: renders package mostly unusable
Forwarded: https://bugzilla.mozilla.org/show_bug.cgi?id=1778840

This report is created to prevent the migration of Thunderbird into
testing.

In some cases it might happen that using "Reply All" will drop all Cc
recipients. The issue is known and confirmed by upstream.

Regards
Carsten

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

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

Versions of packages thunderbird depends on:
ii  debianutils  5.7-0.2
ii  fontconfig   2.13.1-4.4
ii  libatk1.0-0  2.38.0-1
ii  libbotan-2-192.19.1+dfsg-3
ii  libbz2-1.0   1.0.8-5
ii  libc62.33-7
ii  libcairo-gobject21.16.0-5
ii  libcairo21.16.0-5
ii  libdbus-1-3  1.14.0-1
ii  libdbus-glib-1-2 0.112-2
ii  libevent-2.1-7   2.1.12-stable-5+b1
ii  libffi8  3.4.2-4
ii  libfontconfig1   2.13.1-4.4
ii  libfreetype6 2.12.1+dfsg-3
ii  libgcc-s112.1.0-2
ii  libgdk-pixbuf-2.0-0  2.42.8+dfsg-1
ii  libglib2.0-0 2.72.3-1
ii  libgtk-3-0   3.24.34-1
ii  libjson-c5   0.16-1
ii  libnspr4 2:4.34-1
ii  libnss3  2:3.79-1
ii  libpango-1.0-0   1.50.7+ds-1
ii  libstdc++6   12.1.0-2
ii  libvpx7  1.11.0-2
ii  libx11-6 2:1.7.5-1
ii  libx11-xcb1  2:1.7.5-1
ii  libxcb-shm0  1.14-3
ii  libxcb1  1.14-3
ii  libxext6 2:1.3.4-1
ii  libxrender1  1:0.9.10-1.1
ii  psmisc   23.5-1
ii  x11-utils7.7+5
ii  zenity   3.42.1-2
ii  zlib1g   1:1.2.11.dfsg-4

Versions of packages thunderbird recommends:
ii  hunspell-de-at [hunspell-dictionary]  20161207-9
ii  hunspell-de-ch [hunspell-dictionary]  20161207-9
ii  hunspell-de-de [hunspell-dictionary]  20161207-9
ii  hunspell-en-us [hunspell-dictionary]  1:2020.12.07-2
ii  myspell-da [myspell-dictionary]   1.6.36-11.1

Versions of packages thunderbird suggests:
ii  apparmor  3.0.4-3
ii  fonts-lyx 2.3.6.1-1
ii  libgssapi-krb5-2  1.19.2-2+b2

-- no debconf information

Processed: Bug#1014730 marked as pending in liburi-perl

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1014730 [liburi-perl] liburi-perl: Breaks apt-cacher with "Can't locate 
Regexp/IPv6.pm" error
Added tag(s) pending.

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

Bug#1014730: marked as pending in liburi-perl

[gregor herrmann]

Control: tag -1 pending

Hello,

Bug #1014730 in liburi-perl 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/perl-team/modules/packages/liburi-perl/-/commit/8856ade5cdc26efddcef5a6b4aeb8c1a95a2ebb1


Move libregexp-ipv6-perl to Depends.

Closes: #1014730
Thanks: Robert Luberda for the bug report.


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1014730

Bug#1014730: liburi-perl: Breaks apt-cacher with "Can't locate Regexp/IPv6.pm" error

[gregor herrmann]

On Mon, 11 Jul 2022 00:12:11 +0200, Robert Luberda wrote:

> The following information is printed into apt-cacher.log:
> Mon Jul 11 00:02:52 2022|error [18513]: Can't locate Regexp/IPv6.pm in @INC 
> (you may need to install the Regexp::
> IPv6 module)

Thanks for your bug report.

I'm a bit surprised, because the new code in 5.11 should behave
better if Regexp::IPv6 is not available:

+our $IPv6_re;
+
+sub _looks_like_raw_ip6_address {
+  my $addr = shift;
+
+  if ( !$IPv6_re ) { #-- lazy / runs once / use Regexp::IPv6 if installed
+eval {
+  require Regexp::IPv6;
+  Regexp::IPv6->import( qw($IPv6_re) );
+  1;
+}  ||  do { $IPv6_re = qr/[:0-9a-f]{3,}/; }; #-- fallback: unambitious 
guess
+  }
+
+  return 0 unless $addr;
+  return 0 if $addr =~ tr/:/:/ < 2;  #-- fallback must not create false 
positive for IPv4:Port = 0:0
+  return 1 if $addr =~ /^$IPv6_re$/i;
+  return 0;
+}


But may as well move libregexp-ipv6-perl to Depends, I guess.


Cheers,
gregor

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


signature.asc
Description: Digital Signature

Bug#1014719: FTBFS: test failures in t/FormatExternal.t

[gregor herrmann]

On Sun, 10 Jul 2022 22:35:43 +0200, gregor herrmann wrote:

> On Sun, 10 Jul 2022 22:15:04 +0200, gregor herrmann wrote:
> 
> > As also seen by the autopkgtests on ci.debian.net,
> > this package has recently started to fail its tests, which also
> > causes a build failure:
> 
> According to https://rt.cpan.org/Public/Bug/Display.html?id=143689
> this might be caused by liburi-perl 5.11-1

Cf. also https://github.com/libwww-perl/URI/issues/102
Should be fixed with URI 5.12

Cheers,
gregor

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


signature.asc
Description: Digital Signature

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

[Debian Bug Tracking System]

Your message dated Mon, 11 Jul 2022 07:04:20 +
with message-id 
and subject line Bug#1008452: fixed in python-streamz 0.6.3-3
has caused the Debian Bug report #1008452,
regarding python-streamz: FTBFS: dh_auto_test: error: pybuild --test 
--test-pytest -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.)


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

Hi,

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


Relevant part (hopefully):
>  debian/rules binary
> dh binary --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 
> running config
> I: pybuild base:237: python3.9 setup.py config 
> running config
>dh_auto_build -O--buildsystem=pybuild
> I: pybuild base:237: /usr/bin/python3.10 setup.py build 
> running build
> running build_py
> creating /<>/.pybuild/cpython3_3.10_streamz/build/streamz
> copying streamz/graph.py -> 
> /<>/.pybuild/cpython3_3.10_streamz/build/streamz
> copying streamz/__init__.py -> 
> /<>/.pybuild/cpython3_3.10_streamz/build/streamz
> copying streamz/dask.py -> 
> /<>/.pybuild/cpython3_3.10_streamz/build/streamz
> copying streamz/orderedweakset.py -> 
> /<>/.pybuild/cpython3_3.10_streamz/build/streamz
> copying streamz/plugins.py -> 
> /<>/.pybuild/cpython3_3.10_streamz/build/streamz
> copying streamz/core.py -> 
> /<>/.pybuild/cpython3_3.10_streamz/build/streamz
> copying streamz/utils_test.py -> 
> /<>/.pybuild/cpython3_3.10_streamz/build/streamz
> copying streamz/sources.py -> 
> /<>/.pybuild/cpython3_3.10_streamz/build/streamz
> copying streamz/collection.py -> 
> /<>/.pybuild/cpython3_3.10_streamz/build/streamz
> copying streamz/batch.py -> 
> /<>/.pybuild/cpython3_3.10_streamz/build/streamz
> copying streamz/sinks.py -> 
> /<>/.pybuild/cpython3_3.10_streamz/build/streamz
> copying streamz/utils.py -> 
> /<>/.pybuild/cpython3_3.10_streamz/build/streamz
> creating 
> /<>/.pybuild/cpython3_3.10_streamz/build/streamz/dataframe
> copying streamz/dataframe/__init__.py -> 
> /<>/.pybuild/cpython3_3.10_streamz/build/streamz/dataframe
> copying streamz/dataframe/core.py -> 
> /<>/.pybuild/cpython3_3.10_streamz/build/streamz/dataframe
> copying streamz/dataframe/aggregations.py -> 
> /<>/.pybuild/cpython3_3.10_streamz/build/streamz/dataframe
> copying streamz/dataframe/utils.py -> 
> /<>/.pybuild/cpython3_3.10_streamz/build/streamz/dataframe
> creating /<>/.pybuild/cpython3_3.10_streamz/build/streamz/tests
> copying streamz/tests/__init__.py -> 
> /<>/.pybuild/cpython3_3.10_streamz/build/streamz/tests
> copying streamz/tests/py3_test_core.py -> 
> /<>/.pybuild/cpython3_3.10_streamz/build/streamz/tests
> copying streamz/tests/test_plugins.py -> 
> /<>/.pybuild/cpython3_3.10_streamz/build/streamz/tests
> copying streamz/tests/test_sinks.py -> 
> /<>/.pybuild/cpython3_3.10_streamz/build/streamz/tests
> copying streamz/tests/test_core.py -> 
> /<>/.pybuild/cpython3_3.10_streamz/build/streamz/tests
> copying streamz/tests/test_batch.py -> 
> /<>/.pybuild/cpython3_3.10_streamz/build/streamz/tests
> copying streamz/tests/test_sources.py -> 
> /<>/.pybuild/cpython3_3.10_streamz/build/streamz/tests
> copying streamz/tests/test_graph.py -> 
> /<>/.pybuild/cpython3_3.10_streamz/build/streamz/tests
> copying streamz/tests/test_dask.py -> 
> /<>/.pybuild/cpython3_3.10_streamz/build/streamz/tests
> copying streamz/tests/test_kafka.py -> 
> /<>/.pybuild/cpython3_3.10_streamz/build/streamz/tests
> package init file 'streamz/dataframe/tests/__init__.py' not found (or not a 
> regular file)
> creating 
> /<>/.pybuild/cpython3_3.10_streamz/build/streamz/dataframe/tests
> copying streamz/dataframe/tests/test_dataframe_utils.py -> 
> /<>/.pybuild/cpython3_3.10_streamz/build/streamz/dataframe/tests
> copying streamz/dataframe/tests/test_dataframes.py -> 
> /<>/.pybuild/cpython3_3.10_streamz/build/streamz/dataframe/tests
> I: pybuild base:237: /usr/bin/python3 setup.py build 
> running build
> running build_py
> creating /<>/.pybuild/cpython3_3.9_streamz/build/streamz
> copying streamz/graph.py -> 
> /<>/.pybuild/cpython3_3.9_streamz/build/streamz
> copying streamz/__init__.py -> 
> 

Bug#1008452: marked as pending in python-streamz

[Nilesh Patra]

Control: tag -1 pending

Hello,

Bug #1008452 in python-streamz 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-streamz/-/commit/0a3bd9d8a9ee247e3d3f378ff3b681054f631b23


Add patch to fix FTBFS with new distributed (Closes: #1008452)


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1008452

Processed: Bug#1008452 marked as pending in python-streamz

[Debian Bug Tracking System]

Processing control commands:

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

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

Processed: tagging 997514 ...

[Debian Bug Tracking System]

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

> tags 997514 + patch fixed-upstream
Bug #997514 [src:ctpl] ctpl: FTBFS: dh_auto_test: error: make -j1 check 
VERBOSE=1 returned exit code 2
Added tag(s) fixed-upstream and patch.
> forwarded 997514 
> https://git.tuxfamily.org/ctpl/ctpl.git/commit/?id=932f7767af15592fc36137a868187e45dea80068
Bug #997514 [src:ctpl] ctpl: FTBFS: dh_auto_test: error: make -j1 check 
VERBOSE=1 returned exit code 2
Set Bug forwarded-to-address to 
'https://git.tuxfamily.org/ctpl/ctpl.git/commit/?id=932f7767af15592fc36137a868187e45dea80068'.
> thanks
Stopping processing here.

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

Bug#1014737: marked as done (node-react: missing Breaks+Replaces: node-react (<< 18))

[Debian Bug Tracking System]

Your message dated Mon, 11 Jul 2022 06:34:21 +
with message-id 
and subject line Bug#1014737: fixed in node-react 18.2.0+dfsg+~cs87.31.26-2
has caused the Debian Bug report #1014737,
regarding node-react: missing Breaks+Replaces: node-react (<< 18)
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.)


-- 
1014737: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1014737
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: node-react
Version: 18.1.0~18.2.0+dfsg+~cs87.31.26-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

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

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

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

  Preparing to unpack 
.../node-react-is_18.1.0~18.2.0+dfsg+~cs87.31.26-1_all.deb ...
  Unpacking node-react-is (18.1.0~18.2.0+dfsg+~cs87.31.26-1) ...
  dpkg: error processing archive 
/var/cache/apt/archives/node-react-is_18.1.0~18.2.0+dfsg+~cs87.31.26-1_all.deb 
(--unpack):
   trying to overwrite '/usr/share/nodejs/@types/react-is/index.d.ts', which is 
also in package node-react 17.0.2+dfsg+~cs106.66.62-1
  Errors were encountered while processing:
   
/var/cache/apt/archives/node-react-is_18.1.0~18.2.0+dfsg+~cs87.31.26-1_all.deb

The Breaks+Replaces are missing in all the recently split out packages.


cheers,

Andreas


node-react=17.0.2+dfsg+~cs106.66.62-1_node-react-is=18.1.0~18.2.0+dfsg+~cs87.31.26-1.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: node-react
Source-Version: 18.2.0+dfsg+~cs87.31.26-2
Done: Yadd 

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

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

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

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

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Mon, 11 Jul 2022 07:55:24 +0200
Source: node-react
Built-For-Profiles: nocheck
Architecture: source
Version: 18.2.0+dfsg+~cs87.31.26-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Javascript Maintainers 

Changed-By: Yadd 
Closes: 1014737
Changes:
 node-react (18.2.0+dfsg+~cs87.31.26-2) unstable; urgency=medium
 .
   * Team upload
   * Add breaks node-react < 18 (Closes: #1014737)
   * Back to unstable
Checksums-Sha1: 
 b35d1c787857617068ff9bb7a5104fc6989c7e1d 5370 
node-react_18.2.0+dfsg+~cs87.31.26-2.dsc
 43ea6afab179688bf43db3d24ad6a5006e4e6d11 53564 
node-react_18.2.0+dfsg+~cs87.31.26-2.debian.tar.xz
Checksums-Sha256: 
 d82e9262e1d9e2172087d564fd9d21d00660787821b30c31f36ab84b76831d77 5370 
node-react_18.2.0+dfsg+~cs87.31.26-2.dsc
 f790a951a9114b76c15dee80a9d1afc6e699d98d323cdd9a4f90826d76617498 53564 
node-react_18.2.0+dfsg+~cs87.31.26-2.debian.tar.xz
Files: 
 a86db30f16d7b12e9246291c68b6e709 5370 javascript optional 
node-react_18.2.0+dfsg+~cs87.31.26-2.dsc
 224ed236c031ea1b6721e0c9ed7144d7 53564 javascript optional 
node-react_18.2.0+dfsg+~cs87.31.26-2.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEAN/li4tVV3nRAF7J9tdMp8mZ7ukFAmLLvYAACgkQ9tdMp8mZ
7un5JQ//eBKtxEvP0ZfVuVlrzmGAMVXjeiYUI8yiryvZQ9iR7wmqYIXum4cpjIOi
TmImd70ZRmhReAiHBUUw5x/7IxKHmLi3LT60Vm2Gcf3oySNB1l/ZhCdXPg+c2520
mdzCVb1MFcPdEHQXbcYkCEcfBFb4L0h12j+oaWNqG3RJ8NllIpUFVYZBrx77aTE0
ca/ql6WAG0g5/gLOP2kDtgt/xSUSWFndgnY544v3VXUdU6fSgxYVpWYU3meWkeft
wokFjWsUjmhT0dBuVR2Ztmz0DKCnJi9HdLPdvII6BZ/8FS5tN+Gywe9P9YCgUr94
4mPcSdyIfo91erjEMdS876wWXQtLU+Q6PEL17Lz9H/9T8/qWzJwHyxg1rCdsWeco
3N5CKxp1QEFn185PDComYSz/CjSaax0/pmI7dvLgNtAKx1z6AonUa5rxJf76BC8/
o9q+RARZJcL3c9ch0JshGRdfkwG1x0Lbt3CuUemHhsCt+lqy+xatgM1gmJ6oS5Of
yGB5krdc7tv1ScTnBPxD7tTB7BJ4zyirYKYs5euB+YkjHg97mMk8EpqMGdIigWcH

Bug#1014739: marked as done (node-parse5-*: missing Breaks+Replaces: node-jsdom (<< 20.0.0+repack1~))

[Debian Bug Tracking System]

Your message dated Mon, 11 Jul 2022 06:34:09 +
with message-id 
and subject line Bug#1014739: fixed in node-parse5 7.0.0+dfsg-5
has caused the Debian Bug report #1014739,
regarding node-parse5-*: missing Breaks+Replaces: node-jsdom (<< 
20.0.0+repack1~)
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.)


-- 
1014739: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1014739
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: node-parse5
Version: 7.0.0+dfsg-4
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package fails to upgrade from
'testing'.
It installed fine in 'testing', then the upgrade to 'sid' fails
because it tries to overwrite other packages files without declaring a
Breaks+Replaces relation.

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

The Breaks+Replaces are needed in all binary packages built from
src:node-parse5

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

  Preparing to unpack 
.../node-parse5-html-rewriting-stream_7.0.0+dfsg-4_all.deb ...
  Unpacking node-parse5-html-rewriting-stream (7.0.0+dfsg-4) ...
  dpkg: error processing archive 
/var/cache/apt/archives/node-parse5-html-rewriting-stream_7.0.0+dfsg-4_all.deb 
(--unpack):
   trying to overwrite 
'/usr/share/nodejs/parse5-html-rewriting-stream/dist/index.d.ts', which is also 
in package node-jsdom 20.0.0+~cs119.22.37-3
  Errors were encountered while processing:
   
/var/cache/apt/archives/node-parse5-html-rewriting-stream_7.0.0+dfsg-4_all.deb


cheers,

Andreas


node-jsdom=20.0.0+~cs119.22.37-3_node-parse5-html-rewriting-stream=7.0.0+dfsg-4.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: node-parse5
Source-Version: 7.0.0+dfsg-5
Done: Yadd 

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

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

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

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

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Mon, 11 Jul 2022 08:02:46 +0200
Source: node-parse5
Built-For-Profiles: nocheck
Architecture: source
Version: 7.0.0+dfsg-5
Distribution: unstable
Urgency: medium
Maintainer: Debian Javascript Maintainers 

Changed-By: Yadd 
Closes: 1014739
Changes:
 node-parse5 (7.0.0+dfsg-5) unstable; urgency=medium
 .
   * Add breaks node-jsdom < 20.0.0+repack1~ in all packages (Closes: #1014739)
Checksums-Sha1: 
 55bbd265017d9cc835a7f0365e8b21c987845e1f 2622 node-parse5_7.0.0+dfsg-5.dsc
 39faf961b64655523263be8844d45ed81f94a31e 4004 
node-parse5_7.0.0+dfsg-5.debian.tar.xz
Checksums-Sha256: 
 fde5bd169f8f1e57716ea5bf91382f5884d20ec8e8dc24d80af962e746645ee1 2622 
node-parse5_7.0.0+dfsg-5.dsc
 dabafd1a6fb814445d3e3c2948ff5bc95c7cbc6802b1009b9240ddf28a1b41a1 4004 
node-parse5_7.0.0+dfsg-5.debian.tar.xz
Files: 
 866972ba9c00270f819a17d9b1297bdd 2622 javascript optional 
node-parse5_7.0.0+dfsg-5.dsc
 c48a6d49ee849b9b1ea69f68d411cd86 4004 javascript optional 
node-parse5_7.0.0+dfsg-5.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEAN/li4tVV3nRAF7J9tdMp8mZ7ukFAmLLvZoACgkQ9tdMp8mZ
7uk4Tg/7BT8SjHmxeFBa8LOIO1WsTHRtN7Ow39lop3QQfOKPpAhfp6lKqmZeKZTZ
Y0YvL8biJNrEOkUY9leQyORrwE2lLtzXH1JvTSPcWqNVTyEg79cFZ3PS7pyNI3gh
hTyYzCu0KAyWD8ajKOPWZD95IwFwcFSbhsLTcLVadO+yf0S2wrwdC7garPrDquLn
jmt0cZlPGFCo7/oHkov67FLiEYYM/hS+nx+I2HB7kr8p4jWyjm0v86592y/F0FGH
lBM8KRL6VO1flunNtnOa4/HfX+uMBKtVASCf0h58aVXUazZet7D1jzmw9G1spaSp
WX7xsoz6GDViXdFzR5NhOfXSVnVJynHVwitrB8CF844gxVdZFbSbCcgoXuJpyDl7
FMU7tJRWZnLGReWFHr6pIoxPZZddfBbjBvtRQH3IsX7JjPkUOoMuVnrom1p5NgaK
axA9pUodGKEdFoTS0gqnz90CSwORP7zt7to6dJoBBhV0Fl/B1L/ePXGtlaDNrx1q
cm3A3FA5m65dCdgOQMg+qq05LBvcYZM2xpv9qe2dgts/49sBQfWndOynkCzMgw4Y
YKaujH2Fnty8qv8bfafnQgkjVz2geRDLJnKTzYmDSyUENxMn0hhD7iXJE5RQcLdH
K8blyT3MPBisQzetX0RmvMs1jag8lJxRHXB4LzZ6OYAEvASwrAE=
=SnNW
-END PGP SIGNATURE End Message ---

Processed: Bug#1014739 marked as pending in node-parse5

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1014739 [src:node-parse5] node-parse5-*: missing Breaks+Replaces: 
node-jsdom (<< 20.0.0+repack1~)
Added tag(s) pending.

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

Bug#1014739: marked as pending in node-parse5

[Yadd]

Control: tag -1 pending

Hello,

Bug #1014739 in node-parse5 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/js-team/node-parse5/-/commit/d183ca7719278ec680cecbcb859c53c206687719


Add breaks node-jsdom < 20.0.0+repack1~ in all packages

Closes: #1014739


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1014739

Bug#1014737: marked as pending in node-react

[Yadd]

Control: tag -1 pending

Hello,

Bug #1014737 in node-react 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/js-team/node-react/-/commit/d2188b33d7e63d7f1fafc4ac8568102566f9094c


Add breaks node-react < 18

Closes: #1014737


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1014737

Processed: tagging 1014681, severity of 1014681 is serious

[Debian Bug Tracking System]

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

> tags 1014681 + ftbfs
Bug #1014681 [src:glewlwyd] glewlwyd: Add build dependency to node-react-dom
Added tag(s) ftbfs.
> severity 1014681 serious
Bug #1014681 [src:glewlwyd] glewlwyd: Add build dependency to node-react-dom
Severity set to 'serious' from 'important'
> thanks
Stopping processing here.

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

Processed: Bug#1014737 marked as pending in node-react

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1014737 [src:node-react] node-react: missing Breaks+Replaces: node-react 
(<< 18)
Added tag(s) pending.

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

Processed: notfound 1014737 in 18.1.0~18.2.0+dfsg+~cs87.31.26-1, found 1014737 in 18.2.0+dfsg+~cs87.31.26-1

[Debian Bug Tracking System]

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

> notfound 1014737 18.1.0~18.2.0+dfsg+~cs87.31.26-1
Bug #1014737 [src:node-react] node-react: missing Breaks+Replaces: node-react 
(<< 18)
The source 'node-react' and version '18.1.0~18.2.0+dfsg+~cs87.31.26-1' do not 
appear to match any binary packages
No longer marked as found in versions 
node-react/18.1.0~18.2.0+dfsg+~cs87.31.26-1.
> found 1014737 18.2.0+dfsg+~cs87.31.26-1
Bug #1014737 [src:node-react] node-react: missing Breaks+Replaces: node-react 
(<< 18)
Marked as found in versions node-react/18.2.0+dfsg+~cs87.31.26-1.
> thanks
Stopping processing here.

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