Bug#994385: marked as done (uvloop: Removal of the python3-*-dbg packages in sid/bookworm)
Your message dated Fri, 26 Nov 2021 05:34:22 + with message-id and subject line Bug#994385: fixed in uvloop 0.16.0+ds1-2 has caused the Debian Bug report #994385, regarding uvloop: Removal of the python3-*-dbg packages in sid/bookworm 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.) -- 994385: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=994385 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:uvloop Version: 0.16.0+ds1-1 Severity: serious Tags: sid bookworm User: debian-pyt...@lists.debian.org Usertags: pydbg-removal Python 3.8 upstream now has a common ABI for normal and debug extension builds, so we can drop the python3-*-dbg packages. Details at https://lists.debian.org/debian-python/2021/09/msg4.html Stop building the python3-*-dbg package, but be careful that all the reverse dependencies are also removed. Please check for dependencies, build dependencies AND autopkg tests. If help is needed, please ask on IRC #debian-python, or the debian-pyt...@lists.debian.org mailing list. --- End Message --- --- Begin Message --- Source: uvloop Source-Version: 0.16.0+ds1-2 Done: Paul Wise We believe that the bug you reported is fixed in the latest version of uvloop, 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 994...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Paul Wise (supplier of updated uvloop 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: Wed, 24 Nov 2021 15:45:34 +0800 Source: uvloop Architecture: source Version: 0.16.0+ds1-2 Distribution: unstable Urgency: medium Maintainer: Piotr Ożarowski Changed-By: Paul Wise Closes: 994385 Changes: uvloop (0.16.0+ds1-2) unstable; urgency=medium . * Drop the package built for the Python debug interpreter (Closes: #994385) Checksums-Sha1: 7edcade6547cd65b01ff96462efd20a838d7e420 2197 uvloop_0.16.0+ds1-2.dsc f60562287d70b0ce06ca751780de3e1753255e6d 7476 uvloop_0.16.0+ds1-2.debian.tar.xz dc6432642f23595c9d992119a557a19b2e6235f6 8063 uvloop_0.16.0+ds1-2_source.buildinfo Checksums-Sha256: a863d385988dd8db4dff5371eb5da5863afbcf16fbf720f541f166fd5fda7338 2197 uvloop_0.16.0+ds1-2.dsc a175a78a50ddc70a817c7406cec5d02890b0949b8f139b15971146d0cf7e142c 7476 uvloop_0.16.0+ds1-2.debian.tar.xz 9f8de6bb9ad3b19125debe2d4d5dbe710547855daa845c282e7582337911c5fc 8063 uvloop_0.16.0+ds1-2_source.buildinfo Files: 6c1450ced00d6736d14cdaf89d103c0b 2197 python optional uvloop_0.16.0+ds1-2.dsc 2c7a730bd8a2ed4f6e96e36aa63d0366 7476 python optional uvloop_0.16.0+ds1-2.debian.tar.xz 3cbb13c3be60fafc8f32e3adf955803b 8063 python optional uvloop_0.16.0+ds1-2_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEEufrTGSrz5KUwnZ05h588mTgBqU8FAmGgbwIACgkQh588mTgB qU+cIg/+OLqiVA3Tybf2hyX5TMLFqYUHVhwIui81xg/D7rGnWcXq0WQ6J50B9vCq kwkOqwuegISmmuViZf0nXiobSfy3yAQ5W9+Zt1GBfQcfdmp0rTZxZTMYB1PIQA94 fkXUkJ50RWafdE2fvaWdzIH35a9qpPh4XE6W/SLC/IZkJKf5fK7zPfXGlJQm+QSw lmtsnVcblag5P8FDdfCx/md0W5UyXcosEF7K7xo06d5hd6Ud1BfdXOoNdTdmSyLc aAOYj7TacXXt2WB69pnXuXsp60C7xykdlWqWW/VrcFUHDo9ZyiTZrUOGYLSbigbG TJLzDvn4PBvn19JKzAUJcnfDeP9QAcbMGfaZF5vkoP4yAvjvm8lzwnI+sr/Wt3kz cuPd36ksigBit1etVgV/b9SsKQOrmsWlAKE5j6XQlKZEJKUSd8Gfbr0YzSgvpIea VD9RZ8b55JnTgIcATEAZ24d895QzuJprCmvRTLlzTWqLADaB80om+vWGfozQTtfI AWGDvQiYVi+q29dKUd0XRsBaL0gwPZfahE8yd1NTWACNr2xIkCbuGTCOpV8Ng2cp tNVkIM4qXWgyttTmcRpViseFvHGOd+xHXM/wS7oCaCI2LWldgao7z4KwXIfP3ptF GH6alwG+x1SWi+rBAGcMA/3Mu+QveplF9k1Yjd8rQfOVIvl/pg8= =AVwD -END PGP SIGNATURE End Message ---
Bug#997644: marked as done (rnc2rng: FTBFS: error in rnc2rng setup command: use_2to3 is invalid.)
Your message dated Fri, 26 Nov 2021 05:18:59 +
with message-id
and subject line Bug#997644: fixed in rnc2rng 2.6.6-1
has caused the Debian Bug report #997644,
regarding rnc2rng: FTBFS: error in rnc2rng setup command: use_2to3 is invalid.
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
997644: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997644
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: rnc2rng
Version: 2.6.4-1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20211023 ftbfs-bookworm
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> fakeroot debian/rules clean
> dh clean --with python3 --buildsystem=pybuild
>dh_auto_clean -O--buildsystem=pybuild
> I: pybuild base:232: python3.9 setup.py clean
> error in rnc2rng setup command: use_2to3 is invalid.
> E: pybuild pybuild:354: clean: plugin distutils failed with: exit code=1:
> python3.9 setup.py clean
> dh_auto_clean: error: pybuild --clean -i python{version} -p 3.9 returned exit
> code 13
> make: *** [debian/rules:6: clean] Error 25
The full build log is available from:
http://qa-logs.debian.net/2021/10/23/rnc2rng_2.6.4-1_unstable.log
A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!
If you reassign this bug to another package, please marking it as 'affects'-ing
this package. See https://www.debian.org/Bugs/server-control#affects
If you fail to reproduce this, please provide a build log and diff it with mine
so that we can identify if something relevant changed in the meantime.
--- End Message ---
--- Begin Message ---
Source: rnc2rng
Source-Version: 2.6.6-1
Done: Emmanuel Arias
We believe that the bug you reported is fixed in the latest version of
rnc2rng, which is due to be installed in the Debian FTP archive.
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to 997...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Emmanuel Arias (supplier of updated rnc2rng 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: Thu, 25 Nov 2021 15:56:05 -0300
Source: rnc2rng
Architecture: source
Version: 2.6.6-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Team
Changed-By: Emmanuel Arias
Closes: 997644
Changes:
rnc2rng (2.6.6-1) unstable; urgency=medium
.
[ Debian Janitor ]
* Trim trailing whitespace.
* Set upstream metadata fields: Bug-Database, Bug-Submit, Repository,
Repository-Browse.
.
[ Ondřej Nový ]
* d/control: Update Maintainer field with new Debian Python Team
contact address.
* d/control: Update Vcs-* fields with new Debian Python Team Salsa
layout.
.
[ Emmanuel Arias ]
* New upstream version 2.6.6 (Closes: #997644).
* d/control: Bump debhelper-compat to 13.
* d/control: Bump Standards-Version to 4.6.0.1.
* d/patches: Remove patch. Upstream already apply the change.
* d/rules: Run tests for all supported Python version.
* d/tests: Add autopkgtests.
* d/control: Add Rules-Requires-Root: no.
* wrap-and-sort.
Checksums-Sha1:
4096fa213a19baffaf50b95b9c384ea28f2b8a58 2098 rnc2rng_2.6.6-1.dsc
c42a69b4743cbb45f5d8c73dac54f7ba4d626d0b 18089 rnc2rng_2.6.6.orig.tar.gz
449b7c364220335ce2f3b7256f03609ccea78a04 2744 rnc2rng_2.6.6-1.debian.tar.xz
f52b7d3be745f79acdf811f12733fad7a984cde7 6721 rnc2rng_2.6.6-1_source.buildinfo
Checksums-Sha256:
d35b1cad20565a8ef14d064d523ddf74b900a49d100bfba906da093a7db48f42 2098
rnc2rng_2.6.6-1.dsc
5a01d157857b5f010a94167e7092cc49efe2531d58e013f12c4e60b8c4df78f1 18089
rnc2rng_2.6.6.orig.tar.gz
0854e3d799e5e86649253b89567db2c45d51aa53da01cd955ddc1a2573b3214a 2744
rnc2rng_2.6.6-1.debian.tar.xz
2030d74e44688745968af89114599e497a02abbff4fa556e917f27c55fa989bd 6721
rnc2rng_2.6.6-1_source.buildinfo
Files:
6079f60bac2108c31808fb38ba422b2c 2098 python optional rnc2rng_2.6.6-1.dsc
1551ac53b17775991786c6d4866aad97 18089 python optional
rnc2rng_2.6.6.orig.tar.gz
456d408243e9e3bef706606d59a16ad1 2744 python optional
rnc2rng_2.6.6-1.debian.tar.xz
Bug#997620: marked as done (python-dexml: FTBFS: error in dexml setup command: use_2to3 is invalid.)
Your message dated Fri, 26 Nov 2021 05:03:36 +
with message-id
and subject line Bug#997620: fixed in flask-openid 1.3.0+dfsg-1
has caused the Debian Bug report #997620,
regarding python-dexml: FTBFS: error in dexml setup command: use_2to3 is
invalid.
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
997620: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997620
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-dexml
Version: 0.5.1-3
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20211023 ftbfs-bookworm
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> fakeroot debian/rules clean
> dh clean --buildsystem=pybuild
>dh_auto_clean -O--buildsystem=pybuild
> I: pybuild base:232: python3.9 setup.py clean
> error in dexml setup command: use_2to3 is invalid.
> E: pybuild pybuild:354: clean: plugin distutils failed with: exit code=1:
> python3.9 setup.py clean
> dh_auto_clean: error: pybuild --clean -i python{version} -p 3.9 returned exit
> code 13
> make: *** [debian/rules:4: clean] Error 25
The full build log is available from:
http://qa-logs.debian.net/2021/10/23/python-dexml_0.5.1-3_unstable.log
A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!
If you reassign this bug to another package, please marking it as 'affects'-ing
this package. See https://www.debian.org/Bugs/server-control#affects
If you fail to reproduce this, please provide a build log and diff it with mine
so that we can identify if something relevant changed in the meantime.
--- End Message ---
--- Begin Message ---
Source: flask-openid
Source-Version: 1.3.0+dfsg-1
Done: Emmanuel Arias
We believe that the bug you reported is fixed in the latest version of
flask-openid, which is due to be installed in the Debian FTP archive.
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to 997...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Emmanuel Arias (supplier of updated flask-openid 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: Tue, 23 Nov 2021 23:24:25 -0300
Source: flask-openid
Architecture: source
Version: 1.3.0+dfsg-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Team
Changed-By: Emmanuel Arias
Closes: 997620
Changes:
flask-openid (1.3.0+dfsg-1) unstable; urgency=medium
.
* New upstream version 1.3.0+dfsg (Closes: #997620).
* d/control: Bump Standards-Version to 4.6.0.1.
Checksums-Sha1:
e02483f9d10684d8823826ff6bd30fba90e12c51 2220 flask-openid_1.3.0+dfsg-1.dsc
2f324cade4d1a226ec461299d851eb2e108aca48 36360
flask-openid_1.3.0+dfsg.orig.tar.xz
1f044c7ed5eb8409fd86f99d15154eae9eeb4c87 4484
flask-openid_1.3.0+dfsg-1.debian.tar.xz
3f5b5861f397030295e15677459ca5c6eec05a25 7850
flask-openid_1.3.0+dfsg-1_source.buildinfo
Checksums-Sha256:
6c25b7ad28e7ca49460596f34096dd82adeda2548cd32d04696d62f2341770d0 2220
flask-openid_1.3.0+dfsg-1.dsc
ea3070b46fb5d74482a7fa2fcab48b2d61224c087067370575150c14cb3271a2 36360
flask-openid_1.3.0+dfsg.orig.tar.xz
ab03204ae7b08cb0e61d7feb87423dcf8bd77b32a68782a4c2bc924579ec7c0d 4484
flask-openid_1.3.0+dfsg-1.debian.tar.xz
7de40f10e2c0bfa3b7769d3b087b1b151823ed4d8f2f4491c244e95e0ca6228d 7850
flask-openid_1.3.0+dfsg-1_source.buildinfo
Files:
563e8583f37f657b86fde4a04eb96496 2220 python optional
flask-openid_1.3.0+dfsg-1.dsc
7e5578f098d469c81d6ea28d9f0c0c02 36360 python optional
flask-openid_1.3.0+dfsg.orig.tar.xz
e276b50cd1770bdb81ec7f86d70de578 4484 python optional
flask-openid_1.3.0+dfsg-1.debian.tar.xz
41121f9519f8802e61da2510053f739d 7850 python optional
flask-openid_1.3.0+dfsg-1_source.buildinfo
-BEGIN PGP SIGNATURE-
iQIzBAEBCAAdFiEEufrTGSrz5KUwnZ05h588mTgBqU8FAmGgaFwACgkQh588mTgB
qU+aBg//ZT5FlLW4uQuJyfSdRhBG5Gmu2YwjjAs0aEDR6BNNa+CN1URemTWNe1md
/k4KeS+LUQ/5QVTxCV5TqAeMTeV+oMbS/pZR7h1k95ZkddVs+htJoC/TkbXgNDoY
BcRE9E33tdtrG+PkVu/W0vyaJJcjlRyY7xMgSdu5prd+OguJO7FIMat2jNCaSaPk
K/kbvPA+DR/FBo0yK596qI53kGQh7MkFFKQJOoijNP9dTs3jXO9M5oA2miCpzQnW
Bug#996780: gnome-boxes: Systematic system freeze few seconds after launching a Windows WM
Gunnar question made me question X server, and apparently it's related to Wayland, cause opening a session with Xorg, i can't reproduce it Le mar. 23 nov. 2021, 15 h 52, Mathieu R. a écrit : > i'm not, i'm using intel drivers > > Le sam. 20 nov. 2021, 18 h 43, Gunnar Hjalmarsson a > écrit : > >> Are you possibly using a NVIDIA driver? Asking because of this: >> >> https://github.com/NVIDIA/egl-wayland/issues/27#issuecomment-951725683 >> >> -- >> Cheers, >> Gunnar Hjalmarsson >> >
Bug#998471: marked as done (gpgme1.0: b-d on python3-all-dev, but not built for all supported Python3 versions)
Your message dated Fri, 26 Nov 2021 03:04:06 + with message-id and subject line Bug#998471: fixed in gpgme1.0 1.16.0-1.2 has caused the Debian Bug report #998471, regarding gpgme1.0: b-d on python3-all-dev, but not built for all supported Python3 versions 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.) -- 998471: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=998471 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: gpgme1.0 Version: 1.16.0-1.1 Severity: important Tags: ftbfs User: debian-pyt...@lists.debian.org Usertags: python3.10 python3-all-dev Hi Maintainer This package build-depends on python3-all-dev, but does not build extensions/libraries for all supported python3 versions. This is seen on the transition tracker for adding python3.10 support [1] and creates false positives. Please either replace the b-d python3-all-dev with python3-dev, or build for all supported Python3 versions. With the former solution you get later exposure to a new python3 version, with the latter solution you get early exposure. Regards Graham [1] https://release.debian.org/transitions/html/python3.10-add.html --- End Message --- --- Begin Message --- Source: gpgme1.0 Source-Version: 1.16.0-1.2 Done: Stefano Rivera We believe that the bug you reported is fixed in the latest version of gpgme1.0, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 998...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Stefano Rivera (supplier of updated gpgme1.0 package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Tue, 23 Nov 2021 22:23:52 -0400 Source: gpgme1.0 Architecture: source Version: 1.16.0-1.2 Distribution: unstable Urgency: medium Maintainer: Debian GnuPG Maintainers Changed-By: Stefano Rivera Closes: 998471 Changes: gpgme1.0 (1.16.0-1.2) unstable; urgency=medium . * Non-maintainer upload. * Patch: Avoid a hardcoded list of known Python versions. (Closes: #998471) Checksums-Sha1: e83b6c652ad3490057d6a078a33f2ef5c6f200d1 2306 gpgme1.0_1.16.0-1.2.dsc 966ec6c2d323aaffeaedeba65fe447ddf2672f25 20864 gpgme1.0_1.16.0-1.2.debian.tar.xz 75e4a59a91ff2938eb24d18f2c6a94859747e23c 10080 gpgme1.0_1.16.0-1.2_source.buildinfo Checksums-Sha256: 4998f3689c444264fd7761b4c10fb78a9cf806c2c63f9f56de673fe2dd659a02 2306 gpgme1.0_1.16.0-1.2.dsc e836c0dcf1ac9ca12f80ba99558f01c06aab7bc2f6a7807981eef95250abee93 20864 gpgme1.0_1.16.0-1.2.debian.tar.xz 9bcb1832ed24755cf3d1c4fd799ad0552aba23b8865a39ff45a85efb2a003570 10080 gpgme1.0_1.16.0-1.2_source.buildinfo Files: 85762d65145128a8ace3ad307cec16a5 2306 libs optional gpgme1.0_1.16.0-1.2.dsc ba41fcd9598ddfcd91b5d0c45730ae9f 20864 libs optional gpgme1.0_1.16.0-1.2.debian.tar.xz e6753fb1d1416dfe59f895f00a608194 10080 libs optional gpgme1.0_1.16.0-1.2_source.buildinfo -BEGIN PGP SIGNATURE- iIoEARYKADIWIQTumtb5BSD6EfafSCRHew2wJjpU2AUCYZ2jWBQcc3RlZmFub3JA ZGViaWFuLm9yZwAKCRBHew2wJjpU2JUYAQC+//x2xvCMjxp9WjN4y4I4eLoxWLhH dObWYvpbCGfQlgD/bm1GKBWRmx5vumkDiZdRujQ645qVQUm9uSQU5V79Ugg= =GEV4 -END PGP SIGNATURE End Message ---
Bug#997479: marked as done (python-httplib2: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p 3.9 returned exit code 13)
Your message dated Fri, 26 Nov 2021 02:39:38 +
with message-id
and subject line Bug#997479: fixed in python-httplib2 0.20.2-1
has caused the Debian Bug report #997479,
regarding python-httplib2: FTBFS: dh_auto_test: error: pybuild --test
--test-pytest -i python{version} -p 3.9 returned exit code 13
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
997479: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997479
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-httplib2
Version: 0.18.1-3
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20211023 ftbfs-bookworm
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> dpkg-buildpackage
> -
>
> Command: dpkg-buildpackage -us -uc -sa -rfakeroot
> dpkg-buildpackage: info: source package python-httplib2
> dpkg-buildpackage: info: source version 0.18.1-3
> dpkg-buildpackage: info: source distribution unstable
> dpkg-buildpackage: info: source changed by Stefano Rivera
>
> dpkg-source --before-build .
> dpkg-buildpackage: info: host architecture amd64
> debian/rules clean
> dh clean --buildsystem pybuild --with python3
>dh_auto_clean -O--buildsystem=pybuild
> I: pybuild base:232: python3.9 setup.py clean
> running clean
> removing '/<>/.pybuild/cpython3_3.9_httplib2/build' (and
> everything under it)
> 'build/bdist.linux-x86_64' does not exist -- can't clean it
> 'build/scripts-3.9' does not exist -- can't clean it
>dh_autoreconf_clean -O--buildsystem=pybuild
>dh_clean -O--buildsystem=pybuild
> dpkg-source -b .
> dpkg-source: info: using source format '3.0 (quilt)'
> dpkg-source: info: building python-httplib2 using existing
> ./python-httplib2_0.18.1.orig.tar.gz
> dpkg-source: info: using patch list from debian/patches/series
> dpkg-source: info: building python-httplib2 in
> python-httplib2_0.18.1-3.debian.tar.xz
> dpkg-source: info: building python-httplib2 in python-httplib2_0.18.1-3.dsc
> debian/rules binary
> dh binary --buildsystem pybuild --with python3
>dh_update_autotools_config -O--buildsystem=pybuild
>dh_autoreconf -O--buildsystem=pybuild
>dh_auto_configure -O--buildsystem=pybuild
> I: pybuild base:232: python3.9 setup.py config
> running config
>dh_auto_build -O--buildsystem=pybuild
> I: pybuild base:232: /usr/bin/python3 setup.py build
> running build
> running build_py
> creating /<>/.pybuild/cpython3_3.9_httplib2/build/httplib2
> copying python3/httplib2/socks.py ->
> /<>/.pybuild/cpython3_3.9_httplib2/build/httplib2
> copying python3/httplib2/__init__.py ->
> /<>/.pybuild/cpython3_3.9_httplib2/build/httplib2
> copying python3/httplib2/certs.py ->
> /<>/.pybuild/cpython3_3.9_httplib2/build/httplib2
> copying python3/httplib2/iri2uri.py ->
> /<>/.pybuild/cpython3_3.9_httplib2/build/httplib2
>dh_auto_test -O--buildsystem=pybuild
> I: pybuild base:232: cd
> /<>/.pybuild/cpython3_3.9_httplib2/build; python3.9 -m pytest
> tests/
> = test session starts
> ==
> platform linux -- Python 3.9.7, pytest-6.2.5, py-1.10.0, pluggy-0.13.0 --
> /usr/bin/python3.9
> cachedir: .pytest_cache
> rootdir: /<>, configfile: setup.cfg
> plugins: timeout-2.0.1
> timeout: 17.0s
> timeout method: signal
> timeout func_only: False
> collecting ... collected 184 items
>
> tests/test_auth.py::test_credentials PASSED [
> 0%]
> tests/test_auth.py::test_basic PASSED[
> 1%]
> tests/test_auth.py::test_basic_for_domain PASSED [
> 1%]
> tests/test_auth.py::test_basic_two_credentials PASSED[
> 2%]
> tests/test_auth.py::test_digest PASSED [
> 2%]
> tests/test_auth.py::test_digest_next_nonce_nc PASSED [
> 3%]
> tests/test_auth.py::test_digest_auth_stale PASSED[
> 3%]
> tests/test_auth.py::test_parse_www_authenticate_correct[strict-{}] PASSED [
> 4%]
> tests/test_auth.py::test_parse_www_authenticate_correct[strict-{'www-authenticate':
> ''}] PASSED [ 4%]
> tests/test_auth.py::test_parse_www_authenticate_correct[strict-{'www-authenticate':
> 'Test realm="test realm" , foo=foo ,bar="bar", baz=baz,qux=qux'}] PASSED [
> 5%]
> tests/test_auth.py::test_parse_www_authenticate_correct[strict-{'www-authenticate':
> 'T*!%#st realm=to*!%#en, to*!%#en="quoted string"'}] PASSED [ 5%]
>
Processed: bug 996350 is forwarded to https://github.com/nesquena/rabl/issues/745
Processing commands for cont...@bugs.debian.org: > forwarded 996350 https://github.com/nesquena/rabl/issues/745 Bug #996350 [src:ruby-rabl] ruby-rabl: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed. Set Bug forwarded-to-address to 'https://github.com/nesquena/rabl/issues/745'. > thanks Stopping processing here. Please contact me if you need assistance. -- 996350: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=996350 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#996350: Problem can be tracked down to ruby-rr
I was examining the problem. The problem seems to be ruby-rr 3.x. rabl actually requires rr 1.x, and with this version it works. I verified this by building against ruby-rr from Stable. But with ruby-rr 3.x in Testing/Unstable it fails. I don't have a fix for that. -- Regards, Daniel Leidert | https://www.wgdd.de/ GPG-Key RSA4096 / BEED4DED5544A4C03E283DC74BCD0567C296D05D GPG-Key ED25519 / BD3C132D8B3805D1808123AB7ACE00941E338C78 https://www.fiverr.com/dleidert https://www.patreon.com/join/dleidert signature.asc Description: This is a digitally signed message part
Bug#997479: marked as pending in python-httplib2
Control: tag -1 pending Hello, Bug #997479 in python-httplib2 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-httplib2/-/commit/b437c54b520b57fee2c9db1f20228e04995d2a68 Patch: fix test_inject_space failure after bpo-43882 fix (Closes: #997479) (this message was generated automatically) -- Greetings https://bugs.debian.org/997479
Processed: Bug#997479 marked as pending in python-httplib2
Processing control commands:
> tag -1 pending
Bug #997479 [src:python-httplib2] python-httplib2: FTBFS: dh_auto_test: error:
pybuild --test --test-pytest -i python{version} -p 3.9 returned exit code 13
Added tag(s) pending.
--
997479: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997479
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Processed: your mail
Processing commands for cont...@bugs.debian.org: > forwarded 1000597 https://github.com/awaw/dnsproxy/issues/6 Bug #1000597 [dnsproxy] dnsproxy only works with DNS servers at localhost Set Bug forwarded-to-address to 'https://github.com/awaw/dnsproxy/issues/6'. > End of message, stopping processing here. Please contact me if you need assistance. -- 1000597: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1000597 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1000625: libopencv-dev: Broken pkg-config file
Package: libopencv-dev Version: 4.5.4+dfsg-6 Severity: serious https://buildd.debian.org/status/logs.php?pkg=mrgingham=1.20-3%2Bb1 ... g++ -Wl,-z,relro -Wl,-z,now -shared -Wl,--default-symver -fPIC -Wl,-soname,libmrgingham.so.2 find_grid.o find_blobs.o find_chessboard_corners.o mrgingham.o ChESS.o -llibopencv_stitching.so.4.5.4d -llibopencv_alphamat.so.4.5.4d -llibopencv_aruco.so.4.5.4d -llibopencv_barcode.so.4.5.4d -llibopencv_bgsegm.so.4.5.4d -llibopencv_bioinspired.so.4.5.4d -llibopencv_ccalib.so.4.5.4d -llibopencv_dnn_objdetect.so.4.5.4d -llibopencv_dnn_superres.so.4.5.4d -llibopencv_dpm.so.4.5.4d -llibopencv_face.so.4.5.4d -llibopencv_freetype.so.4.5.4d -llibopencv_fuzzy.so.4.5.4d -llibopencv_hdf.so.4.5.4d -llibopencv_hfs.so.4.5.4d -llibopencv_img_hash.so.4.5.4d -llibopencv_intensity_transform.so.4.5.4d -llibopencv_line_descriptor.so.4.5.4d -llibopencv_mcc.so.4.5.4d -llibopencv_quality.so.4.5.4d -llibopencv_rapid.so.4.5.4d -llibopencv_reg.so.4.5.4d -llibopencv_rgbd.so.4.5.4d -llibopencv_saliency.so.4.5.4d -llibopencv_shape.so.4.5.4d -llibopencv_stereo.so.4.5.4d -llibopencv_structured_light.so.4.5.4d -llibopencv_phase_unwrapping.so.4.5.4d -llibopencv_superres.so.4.5.4d -llibopencv_optflow.so.4.5.4d -llibopencv_surface_matching.so.4.5.4d -llibopencv_tracking.so.4.5.4d -llibopencv_highgui.so.4.5.4d -llibopencv_datasets.so.4.5.4d -llibopencv_text.so.4.5.4d -llibopencv_plot.so.4.5.4d -llibopencv_ml.so.4.5.4d -llibopencv_videostab.so.4.5.4d -llibopencv_videoio.so.4.5.4d -llibopencv_viz.so.4.5.4d -llibopencv_wechat_qrcode.so.4.5.4d -llibopencv_ximgproc.so.4.5.4d -llibopencv_video.so.4.5.4d -llibopencv_xobjdetect.so.4.5.4d -llibopencv_objdetect.so.4.5.4d -llibopencv_calib3d.so.4.5.4d -llibopencv_imgcodecs.so.4.5.4d -llibopencv_features2d.so.4.5.4d -llibopencv_dnn.so.4.5.4d -llibopencv_flann.so.4.5.4d -llibopencv_xphoto.so.4.5.4d -llibopencv_photo.so.4.5.4d -llibopencv_imgproc.so.4.5.4d -llibopencv_core.so.4.5.4d -lpthread -o libmrgingham.so.2.1 /usr/bin/ld: cannot find -llibopencv_stitching.so.4.5.4d /usr/bin/ld: cannot find -llibopencv_alphamat.so.4.5.4d /usr/bin/ld: cannot find -llibopencv_aruco.so.4.5.4d /usr/bin/ld: cannot find -llibopencv_barcode.so.4.5.4d /usr/bin/ld: cannot find -llibopencv_bgsegm.so.4.5.4d /usr/bin/ld: cannot find -llibopencv_bioinspired.so.4.5.4d /usr/bin/ld: cannot find -llibopencv_ccalib.so.4.5.4d /usr/bin/ld: cannot find -llibopencv_dnn_objdetect.so.4.5.4d /usr/bin/ld: cannot find -llibopencv_dnn_superres.so.4.5.4d /usr/bin/ld: cannot find -llibopencv_dpm.so.4.5.4d /usr/bin/ld: cannot find -llibopencv_face.so.4.5.4d /usr/bin/ld: cannot find -llibopencv_freetype.so.4.5.4d /usr/bin/ld: cannot find -llibopencv_fuzzy.so.4.5.4d /usr/bin/ld: cannot find -llibopencv_hdf.so.4.5.4d /usr/bin/ld: cannot find -llibopencv_hfs.so.4.5.4d /usr/bin/ld: cannot find -llibopencv_img_hash.so.4.5.4d /usr/bin/ld: cannot find -llibopencv_intensity_transform.so.4.5.4d /usr/bin/ld: cannot find -llibopencv_line_descriptor.so.4.5.4d /usr/bin/ld: cannot find -llibopencv_mcc.so.4.5.4d /usr/bin/ld: cannot find -llibopencv_quality.so.4.5.4d /usr/bin/ld: cannot find -llibopencv_rapid.so.4.5.4d /usr/bin/ld: cannot find -llibopencv_reg.so.4.5.4d /usr/bin/ld: cannot find -llibopencv_rgbd.so.4.5.4d /usr/bin/ld: cannot find -llibopencv_saliency.so.4.5.4d /usr/bin/ld: cannot find -llibopencv_shape.so.4.5.4d /usr/bin/ld: cannot find -llibopencv_stereo.so.4.5.4d /usr/bin/ld: cannot find -llibopencv_structured_light.so.4.5.4d /usr/bin/ld: cannot find -llibopencv_phase_unwrapping.so.4.5.4d /usr/bin/ld: cannot find -llibopencv_superres.so.4.5.4d /usr/bin/ld: cannot find -llibopencv_optflow.so.4.5.4d /usr/bin/ld: cannot find -llibopencv_surface_matching.so.4.5.4d /usr/bin/ld: cannot find -llibopencv_tracking.so.4.5.4d /usr/bin/ld: cannot find -llibopencv_highgui.so.4.5.4d /usr/bin/ld: cannot find -llibopencv_datasets.so.4.5.4d /usr/bin/ld: cannot find -llibopencv_text.so.4.5.4d /usr/bin/ld: cannot find -llibopencv_plot.so.4.5.4d /usr/bin/ld: cannot find -llibopencv_ml.so.4.5.4d /usr/bin/ld: cannot find -llibopencv_videostab.so.4.5.4d /usr/bin/ld: cannot find -llibopencv_videoio.so.4.5.4d /usr/bin/ld: cannot find -llibopencv_viz.so.4.5.4d /usr/bin/ld: cannot find -llibopencv_wechat_qrcode.so.4.5.4d /usr/bin/ld: cannot find -llibopencv_ximgproc.so.4.5.4d /usr/bin/ld: cannot find -llibopencv_video.so.4.5.4d /usr/bin/ld: cannot find -llibopencv_xobjdetect.so.4.5.4d /usr/bin/ld: cannot find -llibopencv_objdetect.so.4.5.4d /usr/bin/ld: cannot find -llibopencv_calib3d.so.4.5.4d /usr/bin/ld: cannot find -llibopencv_imgcodecs.so.4.5.4d /usr/bin/ld: cannot find -llibopencv_features2d.so.4.5.4d /usr/bin/ld: cannot find -llibopencv_dnn.so.4.5.4d /usr/bin/ld: cannot find -llibopencv_flann.so.4.5.4d /usr/bin/ld: cannot find -llibopencv_xphoto.so.4.5.4d /usr/bin/ld: cannot find -llibopencv_photo.so.4.5.4d /usr/bin/ld: cannot find -llibopencv_imgproc.so.4.5.4d /usr/bin/ld: cannot find
Bug#996295: marked as done (ruby-i18n-inflector-rails: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed: ArgumentError:)
Your message dated Fri, 26 Nov 2021 01:08:40 + with message-id and subject line Bug#996295: fixed in ruby-i18n-inflector-rails 1.0.7-5 has caused the Debian Bug report #996295, regarding ruby-i18n-inflector-rails: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed: ArgumentError: 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.) -- 996295: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=996295 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: ruby-i18n-inflector-rails Version: 1.0.7-4.1 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: debian-r...@lists.debian.org Usertags: ruby3.0 Hi, We are about to enable building against ruby3.0 on unstable. During a test rebuild, ruby-i18n-inflector-rails was found to fail to build in that situation. To reproduce this locally, you need to install ruby-all-dev from experimental on an unstable system or build chroot. Relevant part (hopefully): > ArgumentError: > wrong number of arguments (given 2, expected 1) > # > /usr/share/rubygems-integration/all/gems/actionpack-6.0.3.7/lib/abstract_controller/translation.rb:13:in > `translate' > # ./lib/i18n-inflector-rails/inflector.rb:322:in `translate' > # ./spec/inflector_spec.rb:215:in `t_male' > # ./spec/inflector_spec.rb:327:in `block (4 levels) in ' > > Finished in 2.06 seconds (files took 3.09 seconds to load) > 33 examples, 11 failures > > Failed examples: > > rspec ./spec/inflector_spec.rb:272 # ApplicationController controller > instance methods #translate should translate using inflection patterns and > pick up the right value > rspec ./spec/inflector_spec.rb:278 # ApplicationController controller > instance methods #translate should make use of a block passed to inflection > method > rspec ./spec/inflector_spec.rb:282 # ApplicationController controller > instance methods #translate should make use of inherited inflection method > assignments > rspec ./spec/inflector_spec.rb:286 # ApplicationController controller > instance methods #translate should make use of overriden inflection method > assignments > rspec ./spec/inflector_spec.rb:290 # ApplicationController controller > instance methods #translate should prioritize strict kinds when both > inflection options are passed > rspec ./spec/inflector_spec.rb:295 # ApplicationController controller > instance methods #translate should use regular kind option when strict kind > option is missing > rspec ./spec/inflector_spec.rb:300 # ApplicationController controller > instance methods #translate should make use of disabled inflection method > assignments > rspec ./spec/inflector_spec.rb:308 # ApplicationController controller > instance methods #translate should not raise when method does not exists and > verify_methods is enabled > rspec ./spec/inflector_spec.rb:314 # ApplicationController controller > instance methods #translate should translate with the :inflector_lazy_methods > switch turned off > rspec ./spec/inflector_spec.rb:318 # ApplicationController controller > instance methods #translate should omit pattern interpolation when locale is > not inflected > rspec ./spec/inflector_spec.rb:326 # ApplicationController controller > instance methods #t should call translate > > /usr/bin/ruby3.0 > -I/usr/share/rubygems-integration/all/gems/rspec-support-3.9.3/lib:/usr/share/rubygems-integration/all/gems/rspec-core-3.9.2/lib > /usr/share/rubygems-integration/all/gems/rspec-core-3.9.2/exe/rspec > --pattern ./spec/\*\*/\*_spec.rb failed > ERROR: Test "ruby3.0" failed: The full build log is available at https://people.debian.org/~kanashiro/ruby3.0/round2/builds/3/ruby-i18n-inflector-rails/ruby-i18n-inflector-rails_1.0.7-4.1+rebuild1633383189_amd64.build.txt signature.asc Description: PGP signature --- End Message --- --- Begin Message --- Source: ruby-i18n-inflector-rails Source-Version: 1.0.7-5 Done: Daniel Leidert We believe that the bug you reported is fixed in the latest version of ruby-i18n-inflector-rails, 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 996...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Daniel Leidert (supplier of updated ruby-i18n-inflector-rails package) (This message was generated automatically at their request; if you believe that there
Processed: tagging 996221
Processing commands for cont...@bugs.debian.org: > # > https://salsa.debian.org/ruby-team/ruby-ethon/-/commit/fc33a6c779b9e95b8799c9803f8a45fa3a358e4a > tags 996221 + pending Bug #996221 [src:ruby-ethon] ruby-ethon: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed: [31mFailure/Error: require 'rack/handler/webrick'[0m Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 996221: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=996221 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Bug#996295 marked as pending in ruby-i18n-inflector-rails
Processing control commands: > tag -1 pending Bug #996295 [src:ruby-i18n-inflector-rails] ruby-i18n-inflector-rails: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed: ArgumentError: Added tag(s) pending. -- 996295: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=996295 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#996295: marked as pending in ruby-i18n-inflector-rails
Control: tag -1 pending Hello, Bug #996295 in ruby-i18n-inflector-rails 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/ruby-team/ruby-i18n-inflector-rails/-/commit/46f1206101506bef4a831da0f8f62a49111e0799 Add patch to fix FTBFS * d/patches/fix-for-ruby3-and-rails6.patch: Add patch. - Fix errors with Ruby 3.0 and Rails 6 (closes: #996295). * d/patches/series: Enable new patch. (this message was generated automatically) -- Greetings https://bugs.debian.org/996295
Bug#994374: marked as done (reprozip: Removal of the python3-*-dbg packages in sid/bookworm)
Your message dated Fri, 26 Nov 2021 00:20:49 + with message-id and subject line Bug#994374: fixed in reprozip 1.1-1 has caused the Debian Bug report #994374, regarding reprozip: Removal of the python3-*-dbg packages in sid/bookworm 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.) -- 994374: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=994374 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:reprozip Version: 1.0.16-1 Severity: serious Tags: sid bookworm User: debian-pyt...@lists.debian.org Usertags: pydbg-removal Python 3.8 upstream now has a common ABI for normal and debug extension builds, so we can drop the python3-*-dbg packages. Details at https://lists.debian.org/debian-python/2021/09/msg4.html Stop building the python3-*-dbg package, but be careful that all the reverse dependencies are also removed. Please check for dependencies, build dependencies AND autopkg tests. If help is needed, please ask on IRC #debian-python, or the debian-pyt...@lists.debian.org mailing list. --- End Message --- --- Begin Message --- Source: reprozip Source-Version: 1.1-1 Done: Boyuan Yang We believe that the bug you reported is fixed in the latest version of reprozip, 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 994...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Boyuan Yang (supplier of updated reprozip 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: Thu, 25 Nov 2021 18:47:46 -0500 Source: reprozip Architecture: source Version: 1.1-1 Distribution: unstable Urgency: high Maintainer: Debian Science Maintainers Changed-By: Boyuan Yang Closes: 994374 998441 Changes: reprozip (1.1-1) unstable; urgency=high . * Team upload. * New upstream release. (Closes: #998441) * debian/control: Bump Standards-Version to 4.6.0. * debian/control: Drop manual -dbg package. (Closes: #994374) Checksums-Sha1: f392f581e2168beba5441dedee3aaec6a800bb45 2201 reprozip_1.1-1.dsc 1fbd38acc2fc4d31e7a40f230e53f8ae4d11cbe8 55060 reprozip_1.1.orig.tar.gz d332db00c466e4067c44d008138af0b64945e1d3 7780 reprozip_1.1-1.debian.tar.xz 808276dcc323015d4e9ad72d27f65d923a18f3be 8113 reprozip_1.1-1_amd64.buildinfo Checksums-Sha256: 1a8d14eb8d45acc0955bd0fb70ab9aacf2d09b4be367e72af3a49670ac152efe 2201 reprozip_1.1-1.dsc 876801836ad8beb09aaf707cbb2a74d6b3eef72077a27c0cb04ba1f20a3fb26a 55060 reprozip_1.1.orig.tar.gz 618101abc4fa659c19cd11771b40436ed2ff7a85a81819615b1665b5819a36d7 7780 reprozip_1.1-1.debian.tar.xz 505a663fd586cd3e8835bf0ec1f0437bb7e7d5d87c53f2a0a67c34acdf36645b 8113 reprozip_1.1-1_amd64.buildinfo Files: fff3402b33bb21b63ab6b1365cea93c0 2201 science optional reprozip_1.1-1.dsc 680cf545209397a5a1da366c853541f5 55060 science optional reprozip_1.1.orig.tar.gz 58a30d28c9282c65de854f76462341b4 7780 science optional reprozip_1.1-1.debian.tar.xz fb334ef7905d58a29bb337ab0321c6e8 8113 science optional reprozip_1.1-1_amd64.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEfncpR22H1vEdkazLwpPntGGCWs4FAmGgIgQACgkQwpPntGGC Ws4cOA//WYa+c5PfgAyU7ep5uYwAefoYSLKhFICIh+r+wm6efC7FL7aBJ9MtoxZX BoS+333SMzaAr3g1UxIVgF9QWQdE4WKNjQi6o2gu06oGmEY+hfgOnsVRUNrmOXvw ncJvgt1crVNc5TNcmnP7Wf6bRTfO510Rx17sIA79WABUTRPFfPxv/WyGaHWvNps6 2KtdH0F9Ni/ylfAKCtWDy9nBGWJTSoqmGJ0lcjbSxbUNU+AOaCK9Dp1+IGKAyCc7 1F5VzoAI3niNhj8cMfAEUeKF+rucogpwWUhZjYkxbG0LfJpnZb+903LjsD2ZfGi1 M9QMhaSPmS9/hrBnHd3rS23IDwTEjDOaDfSEPhT2bjI9WOfpEtqi4obsvayFJCLN pnc+YPjBPfpNAXv3ZQstvNXui6aXTGjX3k6Q3idq66GzBrinQDdEEgx5ceUlUEEg 6+8HHWa5F/WcjjN4OSAH6qpNvaE4uDoMlbB5Z2iOAZwg6Q5B1wAW23LI3L8JSQ6J iXfsCUS3UVzPgZJMxRC4ArJTHkFZpXGkWASokU8k1hS535kxoS0y/rjP/uC1qYtU okv951BHWJX+nA2emUFVcBlPMgPiCLzjdmedHlD0zJTQaM+jLDxLM33kFve7Cp+t ruT/l60/K8VwPvRbnZLUbkXgqo0BRyNOFyoO61lMytkpLGgpIVA= =ssUk -END PGP SIGNATURE End Message ---
Bug#998441: marked as done (reprozip: FTBFS on 2nd reproducible build)
Your message dated Fri, 26 Nov 2021 00:20:49 + with message-id and subject line Bug#998441: fixed in reprozip 1.1-1 has caused the Debian Bug report #998441, regarding reprozip: FTBFS on 2nd reproducible build 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.) -- 998441: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=998441 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: reprozip Version: 1.0.16-1 Severity: normal Tags: ftbfs bookworm sid User: debian-pyt...@lists.debian.org Usertags: python3.10 Hi Maintainer As can be seen on reproducible builds [1], the second builds of reprozip always fail. I've copied what I hope is the relevant part of the log below. I've set the severity to normal for now, but it will be raised if the failure happens on the buildds as well. Regards Graham [1] https://tests.reproducible-builds.org/debian/rb-pkg/reprozip.html == FAIL: test_get_files (test_reprozip.TestFiles) -- Traceback (most recent call last): File "/build/2/reprozip-1.0.16/2nd/debian/tests/test_reprozip.py", line 277, in test_get_files self.assertEqualPaths(expected, File "/build/2/reprozip-1.0.16/2nd/debian/tests/test_reprozip.py", line 255, in assertEqualPaths self.assertEqual(self.make_paths(objs), second) AssertionError: Items in the second set but not the first: Path(b'/usr/lib64/ld-linux-x86-64.so.2') Path(b'/usr/lib/x86_64-linux-gnu/ld-2.32.so') == FAIL: test_multiple_runs (test_reprozip.TestFiles) -- Traceback (most recent call last): File "/build/2/reprozip-1.0.16/2nd/debian/tests/test_reprozip.py", line 309, in test_multiple_runs self.assertEqualPaths(expected, File "/build/2/reprozip-1.0.16/2nd/debian/tests/test_reprozip.py", line 255, in assertEqualPaths self.assertEqual(self.make_paths(objs), second) AssertionError: Items in the second set but not the first: Path(b'/usr/lib64/ld-linux-x86-64.so.2') Path(b'/usr/lib/x86_64-linux-gnu/ld-2.32.so') -- Ran 8 tests in 0.229s FAILED (failures=2) --- End Message --- --- Begin Message --- Source: reprozip Source-Version: 1.1-1 Done: Boyuan Yang We believe that the bug you reported is fixed in the latest version of reprozip, 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 998...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Boyuan Yang (supplier of updated reprozip 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: Thu, 25 Nov 2021 18:47:46 -0500 Source: reprozip Architecture: source Version: 1.1-1 Distribution: unstable Urgency: high Maintainer: Debian Science Maintainers Changed-By: Boyuan Yang Closes: 994374 998441 Changes: reprozip (1.1-1) unstable; urgency=high . * Team upload. * New upstream release. (Closes: #998441) * debian/control: Bump Standards-Version to 4.6.0. * debian/control: Drop manual -dbg package. (Closes: #994374) Checksums-Sha1: f392f581e2168beba5441dedee3aaec6a800bb45 2201 reprozip_1.1-1.dsc 1fbd38acc2fc4d31e7a40f230e53f8ae4d11cbe8 55060 reprozip_1.1.orig.tar.gz d332db00c466e4067c44d008138af0b64945e1d3 7780 reprozip_1.1-1.debian.tar.xz 808276dcc323015d4e9ad72d27f65d923a18f3be 8113 reprozip_1.1-1_amd64.buildinfo Checksums-Sha256: 1a8d14eb8d45acc0955bd0fb70ab9aacf2d09b4be367e72af3a49670ac152efe 2201 reprozip_1.1-1.dsc 876801836ad8beb09aaf707cbb2a74d6b3eef72077a27c0cb04ba1f20a3fb26a 55060 reprozip_1.1.orig.tar.gz 618101abc4fa659c19cd11771b40436ed2ff7a85a81819615b1665b5819a36d7 7780 reprozip_1.1-1.debian.tar.xz 505a663fd586cd3e8835bf0ec1f0437bb7e7d5d87c53f2a0a67c34acdf36645b 8113 reprozip_1.1-1_amd64.buildinfo Files: fff3402b33bb21b63ab6b1365cea93c0 2201 science optional reprozip_1.1-1.dsc 680cf545209397a5a1da366c853541f5 55060 science optional reprozip_1.1.orig.tar.gz 58a30d28c9282c65de854f76462341b4 7780 science
Bug#996306: marked as done (ruby-jsonpath: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed: RuntimeError: character '|' not supported in query.)
Your message dated Thu, 25 Nov 2021 23:49:57 +
with message-id
and subject line Bug#996306: fixed in ruby-jsonpath 1.1.0-1
has caused the Debian Bug report #996306,
regarding ruby-jsonpath: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed:
RuntimeError: character '|' not supported in query.
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.)
--
996306: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=996306
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ruby-jsonpath
Version: 1.0.5-2
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: debian-r...@lists.debian.org
Usertags: ruby3.0
Hi,
We are about to enable building against ruby3.0 on unstable. During a test
rebuild, ruby-jsonpath was found to fail to build in that situation.
To reproduce this locally, you need to install ruby-all-dev from experimental
on an unstable system or build chroot.
Relevant part (hopefully):
> RuntimeError: character '|' not supported in query.
> ArgumentError expected but nothing was raised.
>
> 89 runs, 122 assertions, 1 failures, 0 errors, 0 skips
> rake aborted!
> Command failed with status (1): [ruby -w -I"test"
> /usr/lib/ruby/gems/3.0.0/gems/rake-13.0.3/lib/rake/rake_test_loader.rb
> "test/test_jsonpath.rb" "test/test_jsonpath_bin.rb" -v]
>
> Tasks: TOP => default
> (See full trace by running task with --trace)
> ERROR: Test "ruby3.0" failed:
The full build log is available at
https://people.debian.org/~kanashiro/ruby3.0/round2/builds/3/ruby-jsonpath/ruby-jsonpath_1.0.5-2+rebuild1633384673_amd64.build.txt
signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Source: ruby-jsonpath
Source-Version: 1.1.0-1
Done: Daniel Leidert
We believe that the bug you reported is fixed in the latest version of
ruby-jsonpath, 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 996...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Daniel Leidert (supplier of updated ruby-jsonpath 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: Fri, 26 Nov 2021 00:29:14 +0100
Source: ruby-jsonpath
Architecture: source
Version: 1.1.0-1
Distribution: unstable
Urgency: low
Maintainer: Debian Ruby Team
Changed-By: Daniel Leidert
Closes: 996306
Changes:
ruby-jsonpath (1.1.0-1) unstable; urgency=low
.
* Team upload.
* New upstream release.
- Fixes build and test issues with Ruby 3.0 (closes: #996306).
.
[ Debian Janitor ]
* Set field Upstream-Contact in debian/copyright.
* Remove obsolete fields Contact, Name from debian/upstream/metadata (already
present in machine-readable debian/copyright).
* Update standards version to 4.5.0, no changes needed.
* Bump debhelper from old 12 to 13.
* Update standards version to 4.5.1, no changes needed.
.
[ Daniel Leidert ]
* d/control (Standards-Version): Bump to 4.6.0.
(Build-Depends): Remove ruby-to-regexp.
(Depends): Remove interpreters and use ${ruby:Depends}.
* d/copyright (Copyright): Add team.
* d/patches/remove-phocus.patch: Update patch.
* d/upstream/metadata: Fix Archive and update Changelog field.
Checksums-Sha1:
adef7b7ab409b716800d899d83b76734fe76f034 2049 ruby-jsonpath_1.1.0-1.dsc
c704dac85ac7733c0ae6a419191354c5e80d2c6c 17615 ruby-jsonpath_1.1.0.orig.tar.gz
f8b29162a75bae2b9c32a8c851350fb286747f2d 3012
ruby-jsonpath_1.1.0-1.debian.tar.xz
73cfcb53a8f2983ae3a535bb367b82bf62cbeaf1 9117
ruby-jsonpath_1.1.0-1_amd64.buildinfo
Checksums-Sha256:
36e4291fc75d551cf54702cc4496852983bb87d093803e3862664a980f0cf535 2049
ruby-jsonpath_1.1.0-1.dsc
c7ca4bcbd79bacf2aa3597b99130c0e54d41818f6ee532a79f4709a9d713a694 17615
ruby-jsonpath_1.1.0.orig.tar.gz
b8f54d6b8201b5e4dbc93a7e42359d04b359f2f11b39190e4cdf56d2c01ff97d 3012
ruby-jsonpath_1.1.0-1.debian.tar.xz
6ce89651fceab65425af84aab1133a0c5f4ca71bdf957fe2255c3a194ac17601 9117
ruby-jsonpath_1.1.0-1_amd64.buildinfo
Files:
060a594abd83c5fa26eaba4649e0a0d0 2049 ruby optional ruby-jsonpath_1.1.0-1.dsc
d2a19bbe6f92f98e8ad5b1577409a18b 17615 ruby optional
ruby-jsonpath_1.1.0.orig.tar.gz
267bd3b44421c57f993940fe63cfd6f6 3012
Bug#1000230: screenruler fails to start
Dear George, On one of the two Debian-stable machines I manage libcanberra-gtk3-module is installed: $ LANG=en_US.utf8 sudo aptitude show libcanberra-gtk3-module | egrep "(State)|(Version)" Version: 0.30-7 State: installed On this machine, screenruler works. I'll check the other machine in several days and let you know.
Bug#997342: marked as done (sorl-thumbnail: FTBFS: ImportError: cannot import name 'python_2_unicode_compatible' from 'django.utils.encoding' (/usr/lib/python3/dist-packages/django/utils/encoding.py))
Your message dated Thu, 25 Nov 2021 23:04:12 + with message-id and subject line Bug#997342: fixed in sorl-thumbnail 12.7.0-1 has caused the Debian Bug report #997342, regarding sorl-thumbnail: FTBFS: ImportError: cannot import name 'python_2_unicode_compatible' from 'django.utils.encoding' (/usr/lib/python3/dist-packages/django/utils/encoding.py) 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.) -- 997342: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997342 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: sorl-thumbnail Version: 12.5.0-2 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[1]: Entering directory '/<>' > py3versions: no X-Python3-Version in control file, using supported versions > mkdir -p tmp-locales > localedef -i en_US -c -f UTF-8 tmp-locales/en_US.UTF-8 > set -e; \ > for python in python3.9; do \ > for name in pil pgmagick imagemagick graphicsmagick; do \ > LOCPATH=/<>/tmp-locales LC_ALL=en_US.UTF-8 PYTHONPATH=. > LOCAL_BUILD=1 DJANGO_SETTINGS_MODULE=tests.settings.$name $python -m pytest ; > \ > done; \ > done > Traceback (most recent call last): > File "/usr/lib/python3.9/runpy.py", line 197, in _run_module_as_main > return _run_code(code, main_globals, None, > File "/usr/lib/python3.9/runpy.py", line 87, in _run_code > exec(code, run_globals) > File "/usr/lib/python3/dist-packages/pytest/__main__.py", line 5, in > > raise SystemExit(pytest.console_main()) > File "/usr/lib/python3/dist-packages/_pytest/config/__init__.py", line 185, > in console_main > code = main() > File "/usr/lib/python3/dist-packages/_pytest/config/__init__.py", line 143, > in main > config = _prepareconfig(args, plugins) > File "/usr/lib/python3/dist-packages/_pytest/config/__init__.py", line 318, > in _prepareconfig > config = pluginmanager.hook.pytest_cmdline_parse( > File "/usr/lib/python3/dist-packages/pluggy/hooks.py", line 286, in __call__ > return self._hookexec(self, self.get_hookimpls(), kwargs) > File "/usr/lib/python3/dist-packages/pluggy/manager.py", line 92, in > _hookexec > return self._inner_hookexec(hook, methods, kwargs) > File "/usr/lib/python3/dist-packages/pluggy/manager.py", line 83, in > > self._inner_hookexec = lambda hook, methods, kwargs: hook.multicall( > File "/usr/lib/python3/dist-packages/pluggy/callers.py", line 203, in > _multicall > gen.send(outcome) > File "/usr/lib/python3/dist-packages/_pytest/helpconfig.py", line 100, in > pytest_cmdline_parse > config: Config = outcome.get_result() > File "/usr/lib/python3/dist-packages/pluggy/callers.py", line 80, in > get_result > raise ex[1].with_traceback(ex[2]) > File "/usr/lib/python3/dist-packages/pluggy/callers.py", line 187, in > _multicall > res = hook_impl.function(*args) > File "/usr/lib/python3/dist-packages/_pytest/config/__init__.py", line > 1003, in pytest_cmdline_parse > self.parse(args) > File "/usr/lib/python3/dist-packages/_pytest/config/__init__.py", line > 1283, in parse > self._preparse(args, addopts=addopts) > File "/usr/lib/python3/dist-packages/_pytest/config/__init__.py", line > 1191, in _preparse > self.hook.pytest_load_initial_conftests( > File "/usr/lib/python3/dist-packages/pluggy/hooks.py", line 286, in __call__ > return self._hookexec(self, self.get_hookimpls(), kwargs) > File "/usr/lib/python3/dist-packages/pluggy/manager.py", line 92, in > _hookexec > return self._inner_hookexec(hook, methods, kwargs) > File "/usr/lib/python3/dist-packages/pluggy/manager.py", line 83, in > > self._inner_hookexec = lambda hook, methods, kwargs: hook.multicall( > File "/usr/lib/python3/dist-packages/pluggy/callers.py", line 208, in > _multicall > return outcome.get_result() > File "/usr/lib/python3/dist-packages/pluggy/callers.py", line 80, in > get_result > raise ex[1].with_traceback(ex[2]) > File "/usr/lib/python3/dist-packages/pluggy/callers.py", line 187, in > _multicall > res = hook_impl.function(*args) > File "/usr/lib/python3/dist-packages/pytest_django/plugin.py", line 335, in > pytest_load_initial_conftests > _setup_django() > File "/usr/lib/python3/dist-packages/pytest_django/plugin.py", line 223, in > _setup_django > django.setup() > File "/usr/lib/python3/dist-packages/django/__init__.py", line 24, in setup > apps.populate(settings.INSTALLED_APPS) > File
Processed: forcibly merging 995410 1000502
Processing commands for cont...@bugs.debian.org: > forcemerge 995410 1000502 Bug #995410 [src:breezy] breezy: FTBFS: Bug #995410 [src:breezy] breezy: FTBFS: Added tag(s) ftbfs. Bug #1000502 [src:breezy] breezy FTBFS: ModuleNotFoundError: No module named 'breezy.testingplugins.plugin' Marked as found in versions breezy/3.1.0-8. Added tag(s) sid and bookworm. Merged 995410 1000502 > thanks Stopping processing here. Please contact me if you need assistance. -- 1000502: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1000502 995410: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=995410 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#951248: marked as done (origami-pdf: autopkgtest failure: output to stderr: warning: constant ::Bignum is deprecated)
Your message dated Thu, 25 Nov 2021 22:21:57 + with message-id and subject line Bug#951248: fixed in origami-pdf 2.0.4+dfsg-1 has caused the Debian Bug report #951248, regarding origami-pdf: autopkgtest failure: output to stderr: warning: constant ::Bignum is deprecated 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.) -- 951248: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=951248 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: origami-pdf Version: 2.0.0-1 X-Debbugs-CC: debian...@lists.debian.org Severity: serious User: debian...@lists.debian.org Usertags: always-fails Dear maintainers, Your package was removed some time ago due to bug 914333, which by now is fixed by src:netperfmeter. However, you package fails to migrate back to testing because the autopkgtest fails. I copied some of the output at the bottom of this report. More information about this bug and the reason for filing it can be found on https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation Paul [1] https://qa.debian.org/excuses.php?package=origami-pdf https://ci.debian.net/data/autopkgtest/testing/amd64/o/origami-pdf/3457321/log.gz autopkgtest [08:58:27]: test command1: [--- /usr/lib/ruby/vendor_ruby/origami/object.rb:28: warning: constant ::Bignum is deprecated /usr/lib/ruby/vendor_ruby/origami/object.rb:34: warning: constant ::Fixnum is deprecated /usr/lib/ruby/vendor_ruby/origami/numeric.rb:104: warning: constant ::Bignum is deprecated [0;36;49m[2019-11-20 08:58:29 +][0m [0;32;49mPDFcop is running on target `debian/tests/signed.pdf', policy = `standard'[0m [0;36;49m[2019-11-20 08:58:29 +][0m [0;35;49m File size: 5812 bytes[0m [0;36;49m[2019-11-20 08:58:29 +][0m [0;35;49m MD5: 8e8344cef61ac3179030b0cccd1df008[0m [0;36;49m[2019-11-20 08:58:29 +][0m [0;33;49m> Inspecting document structure...[0m [0;36;49m[2019-11-20 08:58:29 +][0m [0;33;49m> Inspecting document catalog...[0m [0;36;49m[2019-11-20 08:58:29 +][0m [0;39;49m . AcroForm = YES[0m [0;36;49m[2019-11-20 08:58:29 +][0m [0;33;49m> Inspecting JavaScript names directory...[0m [0;36;49m[2019-11-20 08:58:29 +][0m [0;33;49m> Inspecting attachment names directory...[0m [0;36;49m[2019-11-20 08:58:29 +][0m [0;33;49m> Inspecting document pages...[0m [0;36;49m[2019-11-20 08:58:29 +][0m [0;39;49m >> Inspecting page...[0m [0;36;49m[2019-11-20 08:58:29 +][0m [0;33;49m> Inspecting document streams...[0m [0;36;49m[2019-11-20 08:58:29 +][0m [0;32;49mDocument accepted by policy `standard'.[0m autopkgtest [08:58:29]: test command1: ---] autopkgtest [08:58:29]: test command1: - - - - - - - - - - results - - - - - - - - - - command1 FAIL stderr: /usr/lib/ruby/vendor_ruby/origami/object.rb:28: warning: constant ::Bignum is deprecated signature.asc Description: OpenPGP digital signature --- End Message --- --- Begin Message --- Source: origami-pdf Source-Version: 2.0.4+dfsg-1 Done: Daniel Leidert We believe that the bug you reported is fixed in the latest version of origami-pdf, 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 951...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Daniel Leidert (supplier of updated origami-pdf 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: Thu, 25 Nov 2021 23:04:48 +0100 Source: origami-pdf Architecture: source Version: 2.0.4+dfsg-1 Distribution: unstable Urgency: medium Maintainer: Debian Ruby Team Changed-By: Daniel Leidert Closes: 951248 996155 Changes: origami-pdf (2.0.4+dfsg-1) unstable; urgency=medium . * Team upload. * New upstream release. - Removes Bignum/Fixnum usage (closes: #951248). . [ Antonio Terceiro ] * Remove myself from Uploaders: . [ Debian Janitor ] * Trim trailing whitespace. * Use secure copyright file specification URI. * debian/control: Remove empty control field Uploaders. * Update watch file format version to 4. * Use secure URI in debian/watch. * Use secure URI in Homepage field. * Bump
Bug#996155: marked as done (origami-pdf: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed: ArgumentError: wrong number of arguments (given 2, expected 1))
Your message dated Thu, 25 Nov 2021 22:21:57 + with message-id and subject line Bug#996155: fixed in origami-pdf 2.0.4+dfsg-1 has caused the Debian Bug report #996155, regarding origami-pdf: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed: ArgumentError: wrong number of arguments (given 2, expected 1) to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 996155: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=996155 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: origami-pdf Version: 2.1.0-1~exp1 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: debian-r...@lists.debian.org Usertags: ruby3.0 Hi, We are about to enable building against ruby3.0 on unstable. During a test rebuild, origami-pdf was found to fail to build in that situation. To reproduce this locally, you need to install ruby-all-dev from experimental on an unstable system or build chroot. Relevant part (hopefully): > ArgumentError: wrong number of arguments (given 2, expected 1) > /<>/lib/origami/filters/predictors.rb:83:in > `apply_pre_prediction' > /<>/lib/origami/filters/predictors.rb:65:in `pre_prediction' > /<>/lib/origami/filters/flate.rb:44:in `encode' > /<>/lib/origami/filters.rb:351:in `encode' > /<>/lib/origami/stream.rb:479:in `encode_data' > /<>/lib/origami/stream.rb:377:in `block in encode!' > /<>/lib/origami/stream.rb:365:in `downto' > /<>/lib/origami/stream.rb:365:in `encode!' > /<>/lib/origami/stream.rb:287:in `encoded_data' > /<>/test/test_streams.rb:14:in `test_predictors' > /usr/lib/ruby/vendor_ruby/minitest/test.rb:98:in `block (3 levels) in run' > /usr/lib/ruby/vendor_ruby/minitest/test.rb:195:in `capture_exceptions' > /usr/lib/ruby/vendor_ruby/minitest/test.rb:95:in `block (2 levels) in run' > /usr/lib/ruby/vendor_ruby/minitest.rb:270:in `time_it' > /usr/lib/ruby/vendor_ruby/minitest/test.rb:94:in `block in run' > /usr/lib/ruby/vendor_ruby/minitest.rb:365:in `on_signal' > /usr/lib/ruby/vendor_ruby/minitest/test.rb:211:in `with_info_handler' > /usr/lib/ruby/vendor_ruby/minitest/test.rb:93:in `run' > /usr/lib/ruby/vendor_ruby/minitest.rb:1029:in `run_one_method' > /usr/lib/ruby/vendor_ruby/minitest.rb:339:in `run_one_method' > /usr/lib/ruby/vendor_ruby/minitest.rb:326:in `block (2 levels) in run' > /usr/lib/ruby/vendor_ruby/minitest.rb:325:in `each' > /usr/lib/ruby/vendor_ruby/minitest.rb:325:in `block in run' > /usr/lib/ruby/vendor_ruby/minitest.rb:365:in `on_signal' > /usr/lib/ruby/vendor_ruby/minitest.rb:352:in `with_info_handler' > /usr/lib/ruby/vendor_ruby/minitest.rb:324:in `run' > /usr/lib/ruby/vendor_ruby/minitest.rb:164:in `block in __run' > /usr/lib/ruby/vendor_ruby/minitest.rb:164:in `map' > /usr/lib/ruby/vendor_ruby/minitest.rb:164:in `__run' > /usr/lib/ruby/vendor_ruby/minitest.rb:141:in `run' > /usr/lib/ruby/vendor_ruby/minitest.rb:68:in `block in autorun' > > 41 runs, 318 assertions, 0 failures, 2 errors, 0 skips > rake aborted! > Command failed with status (1): [ruby -w -I"test" > /usr/lib/ruby/gems/3.0.0/gems/rake-13.0.3/lib/rake/rake_test_loader.rb > "test/test_pdf.rb" -v] > > Tasks: TOP => default > (See full trace by running task with --trace) > ERROR: Test "ruby3.0" failed: The full build log is available at https://people.debian.org/~kanashiro/ruby3.0/round2/builds/3/origami-pdf/origami-pdf_2.1.0-1~exp1+rebuild1633374022_amd64.build.txt signature.asc Description: PGP signature --- End Message --- --- Begin Message --- Source: origami-pdf Source-Version: 2.0.4+dfsg-1 Done: Daniel Leidert We believe that the bug you reported is fixed in the latest version of origami-pdf, 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 996...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Daniel Leidert (supplier of updated origami-pdf 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: Thu, 25 Nov 2021 23:04:48 +0100 Source: origami-pdf Architecture: source Version: 2.0.4+dfsg-1 Distribution: unstable Urgency: medium Maintainer: Debian Ruby
Processed: forcibly merging 990443 911735
Processing commands for cont...@bugs.debian.org: > forcemerge 990443 911735 Bug #990443 [origami-pdf] origami-pdf: pdfwalker crashes on start: /usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_require.rb:85:in `require': superclass mismatch for class Socket (TypeError) Bug #911735 [origami-pdf] origami-pdf: pdfwalker does not start Set Bug forwarded-to-address to 'https://github.com/ruby-gnome/ruby-gnome/issues/1449'. Severity set to 'serious' from 'normal' 911735 was not blocked by any bugs. 911735 was not blocking any bugs. Added blocking bug(s) of 911735: 1000618 Merged 911735 990443 > thanks Stopping processing here. Please contact me if you need assistance. -- 911735: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=911735 990443: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=990443 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Bug#951248 marked as pending in origami-pdf
Processing control commands: > tag -1 pending Bug #951248 [src:origami-pdf] origami-pdf: autopkgtest failure: output to stderr: warning: constant ::Bignum is deprecated Added tag(s) pending. -- 951248: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=951248 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#996155: marked as pending in origami-pdf
Control: tag -1 pending Hello, Bug #996155 in origami-pdf 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/ruby-team/origami-pdf/-/commit/ee3bbfed5480084305724d42939638475c313f6f Fix Ruby 3.0 keyword arguments error * d/patches/0002-Fix-Ruby-2.7-keyword-arguments-warnings.patch: Add patch. - Fixes Ruby 3.0 keyword argument handling error (closes: #996155). * d/patches/series: Add new patch. (this message was generated automatically) -- Greetings https://bugs.debian.org/996155
Bug#951248: marked as pending in origami-pdf
Control: tag -1 pending Hello, Bug #951248 in origami-pdf 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/ruby-team/origami-pdf/-/commit/73c56e34ed807c4537c0d1580731fecab1d7703a origami-pdf (2.0.4+dfsg-1) UNRELEASED * New upstream release. - Removes Bignum/Fixnum usage (closes: #951248). (this message was generated automatically) -- Greetings https://bugs.debian.org/951248
Processed: Bug#996155 marked as pending in origami-pdf
Processing control commands: > tag -1 pending Bug #996155 [src:origami-pdf] origami-pdf: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed: ArgumentError: wrong number of arguments (given 2, expected 1) Added tag(s) pending. -- 996155: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=996155 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: cloning 990443, reassign -1 to ruby-gtk2 ..., block 990443 with -1
Processing commands for cont...@bugs.debian.org: > clone 990443 -1 Bug #990443 [origami-pdf] origami-pdf: pdfwalker crashes on start: /usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_require.rb:85:in `require': superclass mismatch for class Socket (TypeError) Bug 990443 cloned as bug 1000618 > reassign -1 ruby-gtk2 3.4.3-1+b3 Bug #1000618 [origami-pdf] origami-pdf: pdfwalker crashes on start: /usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_require.rb:85:in `require': superclass mismatch for class Socket (TypeError) Bug reassigned from package 'origami-pdf' to 'ruby-gtk2'. No longer marked as found in versions origami-pdf/2.0.0-1. Ignoring request to alter fixed versions of bug #1000618 to the same values previously set Bug #1000618 [ruby-gtk2] origami-pdf: pdfwalker crashes on start: /usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_require.rb:85:in `require': superclass mismatch for class Socket (TypeError) Marked as found in versions ruby-gnome/3.4.3-1. > retitle -1 ruby-gtk2: crashes with openssl: superclass mismatch for class > Socket (TypeError) Bug #1000618 [ruby-gtk2] origami-pdf: pdfwalker crashes on start: /usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_require.rb:85:in `require': superclass mismatch for class Socket (TypeError) Changed Bug title to 'ruby-gtk2: crashes with openssl: superclass mismatch for class Socket (TypeError)' from 'origami-pdf: pdfwalker crashes on start: /usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_require.rb:85:in `require': superclass mismatch for class Socket (TypeError)'. > forwarded -1 https://github.com/ruby-gnome/ruby-gnome/issues/1449 Bug #1000618 [ruby-gtk2] ruby-gtk2: crashes with openssl: superclass mismatch for class Socket (TypeError) Ignoring request to change the forwarded-to-address of bug#1000618 to the same value > block 990443 with -1 Bug #990443 [origami-pdf] origami-pdf: pdfwalker crashes on start: /usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_require.rb:85:in `require': superclass mismatch for class Socket (TypeError) 990443 was not blocked by any bugs. 990443 was not blocking any bugs. Added blocking bug(s) of 990443: 1000618 > thanks Stopping processing here. Please contact me if you need assistance. -- 1000618: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1000618 990443: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=990443 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: bug 990443 is forwarded to https://github.com/ruby-gnome/ruby-gnome/issues/1449
Processing commands for cont...@bugs.debian.org: > forwarded 990443 https://github.com/ruby-gnome/ruby-gnome/issues/1449 Bug #990443 [origami-pdf] origami-pdf: pdfwalker crashes on start: /usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_require.rb:85:in `require': superclass mismatch for class Socket (TypeError) Set Bug forwarded-to-address to 'https://github.com/ruby-gnome/ruby-gnome/issues/1449'. > thanks Stopping processing here. Please contact me if you need assistance. -- 990443: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=990443 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1000617: python3-nbclient_0.5.6-1: trying to overwrite '/usr/bin/jupyter-run', which is also in package jupyter-client 7.0.6-2
Package: python3-nbclient Version: 0.5.5-1 Severity: serious -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Dear maintainer, it looks like python3-nbclient / jupyter-client don't play well together: Unpacking python3-nbclient (0.5.6-1) over (0.5.5-1) ... dpkg: error processing archive /tmp/apt-dpkg-install-dawlPe/41-python3-nbclient_0.5.6-1_all.deb (--unpack): trying to overwrite '/usr/bin/jupyter-run', which is also in package jupyter-client 7.0.6-2 Roman - -- System Information: Debian Release: bookworm/sid APT prefers unstable APT policy: (990, 'unstable'), (500, 'unstable-debug'), (1, 'experimental-debug'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 5.15.0-1-amd64 (SMP w/32 CPU threads) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages python3-nbclient depends on: ii python3 3.9.8-1 ii python3-jupyter-client 7.0.6-2 ii python3-nbformat5.1.3-1 ii python3-nest-asyncio1.5.1-1 ii python3-traitlets 5.1.1-1 python3-nbclient recommends no packages. python3-nbclient suggests no packages. - -- debconf-show failed -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEjkF6151RK40WXe2HCDw+u0oWieAFAmGgAWAACgkQCDw+u0oW ieBqgg/8DM/IiyThgtywLCfOU8oGu3WGFCFDQcT7q7X+TkNSB+q3aeZ/rH5+5V19 fwlS2LnNKG/yqvDz2BSUq5+NZZJXp1wEqlpDhpgb3eSMjimBN/AjudtQbATqFtXW EhWIRCH3qlig3Bs/q170DbdAT7D6ql4iDdM3hFVN7W4UpjcxmJL1y1k9lQpYG54G 5F25gUI5yrBJTVmt+24ApZChNEj6L1ZKnF7g5155V6PhMnyjygigzift2RfbUGfB fJerTPjEhPYdwIYq/fLIrVC9cmfVT4EYzxqUIFEK0wlUZNTBYbhb6HO+J9EXtbrB BrN8/6wptBlyP4R4dmCCplqt2UzduLRkVvgSjMNyzTcZIhco5vs8bQzplKOjA9ui vuKCmtjgcuNyCvvCi6p2LTaimne74gUNdPic99THb2XqplfvwPMN/+cvoONCh4r9 AUiv//q/OCJP3bC9bZg0cmwm69td5SUI4FtnkDF344hJLETio8nXhfaIIgi59io5 2hCQQhxIxOMxIQ1/iOpGGq+VrZlIHi8TaqiwItB6vxPrMEMy6P59zk18lamxpIsd 9d/QE6K36+3yYxNscPucpLAMPEQxtIQ68IFQM7M7betVNHPVErDVgn/9CNFR8rNc gwgBvsEyG+0LLjtWD8yLA8L4H8OLgxW27ldGo1OHQOwOMw7oyoI= =BbOc -END PGP SIGNATURE-
Bug#996806: [Pkg-mailman-hackers] Bug#996806: mailmain3: Expected test results for arc_validate tests need updating
Jordi Mallach wrote on 24/11/2021 at 23:39:00+0100: > Source: mailman3 > Version: 3.3.3-1 > Followup-For: Bug #996806 > > Apparently this is fixed in upstream commit > f311b135fe13e3ec07ef2eedadba9c09b25e57ff > > See > > https://gitlab.com/mailman/mailman/-/commit/f311b135fe13e3ec07ef2eedadba9c09b25e57ff > > for more details. > > I might try to work on a fix in the following days, most probably > including an update to the latest version, which includes other fixes I > need. I'm waiting for some stuck dependencies issues to solve to batch a full update of mailman3. Cheers! -- PEB signature.asc Description: PGP signature
Bug#990443: [DRE-maint] Bug#990443: Issue seems to be ruby-gtk2
Am Donnerstag, dem 25.11.2021 um 22:15 +0100 schrieb Daniel Leidert: > I did some debugging with this issue and it actually seems to be caused by > ruby-gtk2. It is easy to reproduce. In irb: > > require 'gtk2' > include Gtk > require 'openssl' > > => crash (happens when openssl loads openssl.so): Correkt traceback: 14: from test.rb:3:in `' 13: from /usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_require.rb:85:in `require' 12: from /usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_require.rb:85:in `require' 11: from /usr/lib/ruby/2.7.0/openssl.rb:20:in `' 10: from /usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_require.rb:85:in `require' 9: from /usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_require.rb:85:in `require' 8: from /usr/lib/ruby/2.7.0/openssl/ssl.rb:15:in `' 7: from /usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_require.rb:85:in `require' 6: from /usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_require.rb:85:in `require' 5: from /usr/lib/ruby/2.7.0/ipaddr.rb:19:in `' 4: from /usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_require.rb:85:in `require' 3: from /usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_require.rb:85:in `require' 2: from /usr/lib/ruby/2.7.0/socket.rb:4:in `' 1: from /usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_require.rb:85:in `require' /usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_require.rb:85:in `require': superclass mismatch for class Socket (TypeError) -- Regards, Daniel Leidert | https://www.wgdd.de/ GPG-Key RSA4096 / BEED4DED5544A4C03E283DC74BCD0567C296D05D GPG-Key ED25519 / BD3C132D8B3805D1808123AB7ACE00941E338C78 https://www.fiverr.com/dleidert https://www.patreon.com/join/dleidert signature.asc Description: This is a digitally signed message part
Bug#1000613: gammapy FTBFS on !amd64: test failures
Source: gammapy
Version: 0.19-1
Severity: serious
Tags: ftbfs
https://buildd.debian.org/status/logs.php?pkg=gammapy=0.19-1
...
=== FAILURES ===
__ test_binary_erode ___
def test_binary_erode():
geom = WcsGeom.create(binsz=0.02, width=2 * u.deg)
mask = geom.region_mask("icrs;circle(0, 0, 1)")
mask = mask.binary_erode(width=0.2 * u.deg, kernel="disk",
use_fft=False)
assert_allclose(mask.data.sum(), 4832)
mask = mask.binary_erode(width=0.2 * u.deg, kernel="box", use_fft=True)
> assert_allclose(mask.data.sum(), 3372)
E AssertionError:
E Not equal to tolerance rtol=1e-07, atol=0
E
E Mismatched elements: 1 / 1 (100%)
E Max absolute difference: 15
E Max relative difference: 0.0044484
Ex: array(3387)
Ey: array(3372)
gammapy/maps/wcs/tests/test_ndmap.py:836: AssertionError
__ test_binary_dilate __
def test_binary_dilate():
geom = WcsGeom.create(binsz=0.02, width=2 * u.deg)
mask = geom.region_mask("icrs;circle(0, 0, 0.8)")
mask = mask.binary_dilate(width=0.2 * u.deg, kernel="disk",
use_fft=False)
assert_allclose(mask.data.sum(), 8048)
mask = mask.binary_dilate(width=(10, 10), kernel="box")
> assert_allclose(mask.data.sum(), 9203)
E AssertionError:
E Not equal to tolerance rtol=1e-07, atol=0
E
E Mismatched elements: 1 / 1 (100%)
E Max absolute difference: 11
E Max relative difference: 0.00119526
Ex: array(9214)
Ey: array(9203)
gammapy/maps/wcs/tests/test_ndmap.py:847: AssertionError
=== short test summary info
FAILED gammapy/maps/wcs/tests/test_ndmap.py::test_binary_erode - AssertionErr...
FAILED gammapy/maps/wcs/tests/test_ndmap.py::test_binary_dilate - AssertionEr...
= 2 failed, 1030 passed, 562 skipped, 10 xfailed in 150.08s (0:02:30) ==
...
Bug#990443: Issue seems to be ruby-gtk2
I did some debugging with this issue and it actually seems to be caused by ruby-gtk2. It is easy to reproduce. In irb: require 'gtk2' include Gtk require 'openssl' => crash (happens when openssl loads openssl.so): Traceback (most recent call last): 28: from /usr/bin/pdfwalker:25:in `' 27: from /usr/bin/pdfwalker:25:in `load' 26: from /usr/share/rubygems-integration/all/gems/origami-2.0.4/bin/pdfwalker:4:in `' 25: from /usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_require.rb:85:in `require' 24: from /usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_require.rb:85:in `require' 23: from /usr/share/origami/gui/walker.rb:31:in `' 22: from /usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_require.rb:85:in `require' 21: from /usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_require.rb:85:in `require' 20: from /usr/share/rubygems-integration/all/gems/origami-2.0.4/lib/origami.rb:41:in `' 19: from /usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_require.rb:85:in `require' 18: from /usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_require.rb:85:in `require' 17: from /usr/share/rubygems-integration/all/gems/origami-2.0.4/lib/origami/pdf.rb:49:in `' 16: from /usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_require.rb:85:in `require' 15: from /usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_require.rb:85:in `require' 14: from /usr/share/rubygems-integration/all/gems/origami-2.0.4/lib/origami/encryption.rb:21:in `' 13: from /usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_require.rb:85:in `require' 12: from /usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_require.rb:85:in `require' 11: from /usr/lib/ruby/2.7.0/openssl.rb:20:in `' 10: from /usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_require.rb:85:in `require' 9: from /usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_require.rb:85:in `require' 8: from /usr/lib/ruby/2.7.0/openssl/ssl.rb:15:in `' 7: from /usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_require.rb:85:in `require' 6: from /usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_require.rb:85:in `require' 5: from /usr/lib/ruby/2.7.0/ipaddr.rb:19:in `' 4: from /usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_require.rb:85:in `require' 3: from /usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_require.rb:85:in `require' 2: from /usr/lib/ruby/2.7.0/socket.rb:4:in `' 1: from /usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_require.rb:85:in `require' /usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_require.rb:85:in `require': superclass mismatch for class Socket (TypeError) That's not a bug in origami. I'll have a look at ruby-gtk2. However, I guess as soon as Gtk2 vanishes from Debian, pdfwalker will become dysfunctional. Regards, Daniel -- Regards, Daniel Leidert | https://www.wgdd.de/ GPG-Key RSA4096 / BEED4DED5544A4C03E283DC74BCD0567C296D05D GPG-Key ED25519 / BD3C132D8B3805D1808123AB7ACE00941E338C78 https://www.fiverr.com/dleidert https://www.patreon.com/join/dleidert signature.asc Description: This is a digitally signed message part
Bug#999524: python-language-server: FTBFS with numpy 1.21 (in experimental): dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p 3.9 returned exit code 13
Source: python-language-server Followup-For: Bug #999524 Upstream lost write access to the python-language-server repo https://github.com/palantir/python-language-server/issues/935 so have forked the project to python-lsp-server at https://github.com/python-lsp/python-lsp-server As part of the move they renamed the module from pyls to pylsp. The new version is packaged and available (python3-pylsp, src:python-lsp-server). python-language-server can be removed once spyder is updated for pylsp.
Bug#1000611: libvtk9{,-qt}: soname change without library transition
Hi Adrian, thanks for the bug report. It was really an accidental upload into unstable instead of experimental. Yes, I will rename the package and upload it ASAP. Regards Anton Am Do., 25. Nov. 2021 um 22:03 Uhr schrieb Adrian Bunk : > > Package: libvtk9 > Version: 9.1.0+dfsg2-2 > Severity: serious > Control: affects -1 libvtk9-qt src:vtk9 > > https://ci.debian.net/data/autopkgtest/testing/amd64/f/freecad/16980590/log.gz > > ... > ERROR: TestFemApp (unittest.loader._FailedTest) > -- > ImportError: Failed to import test module: TestFemApp > Traceback (most recent call last): > File "/usr/lib/python3.9/unittest/loader.py", line 154, in loadTestsFromName > module = __import__(module_name) > File "/usr/share/freecad/Mod/Fem/TestFemApp.py", line 33, in > from femtest.app.test_mesh import TestMeshCommon as FemTest07 > File "/usr/share/freecad/Mod/Fem/femtest/app/test_mesh.py", line 33, in > > import Fem > ImportError: libvtkFiltersExtraction-9.0.so.1: cannot open shared object > file: No such file or directory > ... > > > The soname of the vtk9 libraries is not 9, it is 9.0 for VTK 9.0 > and 9.1 for VTK 9.1: > > $ objdump -p /usr/lib/x86_64-linux-gnu/libvtkChartsCore-9.1.so.1 | grep > SONAME > SONAME libvtkChartsCore-9.1.so.1 > $ > > In bullseye libvtk9 and libvtk9-qt should have been named > libvtk9.0 and libvtk9.0-qt, but this alone is harmless. > > Not harmless is that the libraries must transition to the new > soname in 9.1, renaming the packages to libvtk9.1 and libvtk9.1-qt. > > -- > debian-science-maintainers mailing list > debian-science-maintain...@alioth-lists.debian.net > https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/debian-science-maintainers
Bug#1000612: python-cassandra-driver: flaky test
Source: python-cassandra-driver
Version: 3.24.0-1
Severity: serious
Tags: ftbfs
https://buildd.debian.org/status/logs.php?pkg=python-cassandra-driver=3.24.0-1%2Bb1
...
==
FAIL: Verify that timer timeouts are honored appropriately
--
Traceback (most recent call last):
File
"/<>/.pybuild/cpython3_3.9_dbg_cassandra/build/tests/unit/io/utils.py",
line 171, in test_multi_timer_validation
submit_and_wait_for_completion(self, self.create_timer, 0, 100, 1, 100)
File
"/<>/.pybuild/cpython3_3.9_dbg_cassandra/build/tests/unit/io/utils.py",
line 138, in submit_and_wait_for_completion
unit_test.assertAlmostEqual(callback.expected_wait,
callback.get_wait_time(), delta=.15)
AssertionError: 0.0 != 0.1567823886871338 within 0.15 delta (0.1567823886871338
difference)
>> begin captured logging <<
cassandra.connection: DEBUG: Sending initial options message for new connection
(281473218221072) to 127.0.0.1:9042
cassandra.io.libevreactor: DEBUG: Starting libev event loop
cassandra.io.libevreactor: DEBUG: Closing connection (281473218221072) to
127.0.0.1:9042
cassandra.io.libevreactor: DEBUG: Closed socket to 127.0.0.1:9042
- >> end captured logging << -
--
Ran 594 tests in 121.258s
FAILED (SKIP=18, failures=1)
E: pybuild pybuild:354: test: plugin distutils failed with: exit code=1: cd
/<>/.pybuild/cpython3_3.9_dbg_cassandra/build; python3.9-dbg -m
nose -v --ignore-files="test_eventletreactor\.py"
dh_auto_test: error: pybuild --test -i python{version}-dbg -p "3.10 3.9"
returned exit code 13
make[1]: *** [debian/rules:41: override_dh_auto_test] Error 25
Processed: libvtk9{,-qt}: soname change without library transition
Processing control commands:
> affects -1 libvtk9-qt src:vtk9
Bug #1000611 [libvtk9] libvtk9{,-qt}: soname change without library transition
Added indication that 1000611 affects libvtk9-qt and src:vtk9
--
1000611: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1000611
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#1000611: libvtk9{,-qt}: soname change without library transition
Package: libvtk9 Version: 9.1.0+dfsg2-2 Severity: serious Control: affects -1 libvtk9-qt src:vtk9 https://ci.debian.net/data/autopkgtest/testing/amd64/f/freecad/16980590/log.gz ... ERROR: TestFemApp (unittest.loader._FailedTest) -- ImportError: Failed to import test module: TestFemApp Traceback (most recent call last): File "/usr/lib/python3.9/unittest/loader.py", line 154, in loadTestsFromName module = __import__(module_name) File "/usr/share/freecad/Mod/Fem/TestFemApp.py", line 33, in from femtest.app.test_mesh import TestMeshCommon as FemTest07 File "/usr/share/freecad/Mod/Fem/femtest/app/test_mesh.py", line 33, in import Fem ImportError: libvtkFiltersExtraction-9.0.so.1: cannot open shared object file: No such file or directory ... The soname of the vtk9 libraries is not 9, it is 9.0 for VTK 9.0 and 9.1 for VTK 9.1: $ objdump -p /usr/lib/x86_64-linux-gnu/libvtkChartsCore-9.1.so.1 | grep SONAME SONAME libvtkChartsCore-9.1.so.1 $ In bullseye libvtk9 and libvtk9-qt should have been named libvtk9.0 and libvtk9.0-qt, but this alone is harmless. Not harmless is that the libraries must transition to the new soname in 9.1, renaming the packages to libvtk9.1 and libvtk9.1-qt.
Processed: tagging 997644
Processing commands for cont...@bugs.debian.org: > tags 997644 + pending Bug #997644 [src:rnc2rng] rnc2rng: FTBFS: error in rnc2rng setup command: use_2to3 is invalid. Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 997644: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997644 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1000601: marked as done (python3-casa-formats-io need to depend on a versioned python3-numpy)
Your message dated Thu, 25 Nov 2021 20:33:59 + with message-id and subject line Bug#1000601: fixed in casa-formats-io 0.1-2 has caused the Debian Bug report #1000601, regarding python3-casa-formats-io need to depend on a versioned python3-numpy 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.) -- 1000601: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1000601 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: python3-casa-formats-io Version: 0.1-1 Severity: serious https://ci.debian.net/data/autopkgtest/testing/arm64/c/casa-formats-io/16993092/log.gz ... ___ ERROR collecting tests/test_casa_dask.py ___ ImportError while importing test module '/usr/lib/python3/dist-packages/casa_formats_io/tests/test_casa_dask.py'. Hint: make sure your test modules/packages have valid Python names. Traceback: /usr/lib/python3.9/importlib/__init__.py:127: in import_module return _bootstrap._gcd_import(name[level:], package, level) /usr/lib/python3/dist-packages/casa_formats_io/__init__.py:1: in from .casa_dask import * # noqa /usr/lib/python3/dist-packages/casa_formats_io/casa_dask.py:13: in from ._casa_chunking import _combine_chunks E ImportError: numpy.core.multiarray failed to import --- Captured stderr RuntimeError: module compiled against API version 0xe but this version of numpy is 0xd ... python3-casa-formats-io needs a generated dependency on python3-numpy-api* --- End Message --- --- Begin Message --- Source: casa-formats-io Source-Version: 0.1-2 Done: Ole Streicher We believe that the bug you reported is fixed in the latest version of casa-formats-io, 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 1000...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Ole Streicher (supplier of updated casa-formats-io 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: Thu, 25 Nov 2021 20:58:14 +0100 Source: casa-formats-io Architecture: source Version: 0.1-2 Distribution: unstable Urgency: medium Maintainer: Debian Astronomy Team Changed-By: Ole Streicher Closes: 1000601 Changes: casa-formats-io (0.1-2) unstable; urgency=medium . * Depend on a versioned python3-numpy (Closes: #1000601) Checksums-Sha1: e0c40ed863fe7c81297663ef5789b601b1045138 2293 casa-formats-io_0.1-2.dsc 8a48bf6109032ffe18edb719aa56ad0bb9553a55 2476 casa-formats-io_0.1-2.debian.tar.xz Checksums-Sha256: 477cdc1dd0b2c93b74796590820c32a1ba30a563c1ab2afe9d766f92754d23a8 2293 casa-formats-io_0.1-2.dsc 2cd00ab72cf34b1aa41091edbe3e0c8360cab227aed3f61922ef73da7d7c3626 2476 casa-formats-io_0.1-2.debian.tar.xz Files: 597706d8034271a5241776c391eda926 2293 python optional casa-formats-io_0.1-2.dsc ac3f5fe773d06e39948713dcb739ef00 2476 python optional casa-formats-io_0.1-2.debian.tar.xz -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEuvxshffLFD/utvsVcRWv0HcQ3PcFAmGf7o8ACgkQcRWv0HcQ 3PfM1Q//ayf9hDcI7PIQXTz2fCIAimTQyl2+GfDmrjtI+b9lK8MdVC70uSBhKTRJ 6IsqPvL5btHR8xTHHquxx79CT7KuAVJm+6pj4oEM0sr+WtTjeQ6dp8Ttnf4NUMCi h62vNdoBt6myzv3YRKDDPrBLWDW72co/mBpUDh/etJKU6zOLuGQcjbyNUC5IEML0 95A4oWxjeishQ5JIJUEf7X91vN02PJloNP1gRdGRP10To8RwXSVAuboi/gVfdaMM 27Zm4IQaS4Cvl2UB6U4vCa/nOC7OVYuO5IQ7FwSMSnUF8VXQntFXVGC473lBVdpY 1ubp/qbnTAKZCliOix0gf2I9mXP1Iy5msBf5Qp/d9HZf7kq1haaKa55knjyTVIBf 1OaJdXu5MTwvFUJGVQiNnV09+63PT+RPZ4m4wTF57I3THdbxfeCrKVOFTlpUZj+9 CeM4unXTKeXGl+HIyO7txProvaHvDvUWeFmzimPZ4MkJmBZ5SevYCACDgII7dHx6 B8gdNp9eUuPrfwm/B8RlX9WFqgKap7SbO73d+WvrYE3uHcxUjHmKmWxLcH8ok0QV TUs9swxW5rh03yc+nGW2wJ4p5yvHldjxZLHwqYHnfmcfvh7ynjkWCgGXAMa2Tf7e XRoGDqnXqiZqOhCI62/0vHaUlrfWkJucbnJTkw71/+BxDtLHNVw= =/vbg -END PGP SIGNATURE End Message ---
Processed: reassign 997959 to ftp.debian.org ..., severity of 997959 is normal, tagging 997959
Processing commands for cont...@bugs.debian.org: > reassign 997959 ftp.debian.org Bug #997959 [src:git-annex] git-annex: FTBFS on 32-bit ARM architectures, but built successfully before Bug reassigned from package 'src:git-annex' to 'ftp.debian.org'. No longer marked as found in versions git-annex/8.20210223-2. Ignoring request to alter fixed versions of bug #997959 to the same values previously set > retitle 997959 RM: git-annex [armel armhf] -- ROM; enduring issues building > on 32-bit ARM architectures Bug #997959 [ftp.debian.org] git-annex: FTBFS on 32-bit ARM architectures, but built successfully before Changed Bug title to 'RM: git-annex [armel armhf] -- ROM; enduring issues building on 32-bit ARM architectures' from 'git-annex: FTBFS on 32-bit ARM architectures, but built successfully before'. > severity 997959 normal Bug #997959 [ftp.debian.org] RM: git-annex [armel armhf] -- ROM; enduring issues building on 32-bit ARM architectures Severity set to 'normal' from 'serious' > tags 997959 - help Bug #997959 [ftp.debian.org] RM: git-annex [armel armhf] -- ROM; enduring issues building on 32-bit ARM architectures Removed tag(s) help. > thanks Stopping processing here. Please contact me if you need assistance. -- 997959: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997959 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#997959: RM: git-annex [armel armhf] -- ROM; enduring issues building on 32-bit ARM architectures
reassign -1 ftp.debian.org retitle -1 RM: git-annex [armel armhf] -- ROM; enduring issues building on 32-bit ARM architectures severity -1 normal thanks Recent releases of git-annex fail to build on 32-bit ARM architectures and no-one has been able to figure out why, including upstream. As this situation has persisted for some weeks, I'd like to request removal on those architectures for now. -- Sean Whitton signature.asc Description: PGP signature
Bug#996352: marked as done (ruby-rack-timeout: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed: Error: test_zero_wait_timeout(EnvSettingsTest): ArgumentError: wrong number of arguments (given 2, expe
Your message dated Thu, 25 Nov 2021 19:48:36 + with message-id and subject line Bug#996352: fixed in ruby-rack-timeout 0.5.1-3 has caused the Debian Bug report #996352, regarding ruby-rack-timeout: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed: Error: test_zero_wait_timeout(EnvSettingsTest): ArgumentError: wrong number of arguments (given 2, expected 1) to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 996352: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=996352 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: ruby-rack-timeout Version: 0.5.1-2 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: debian-r...@lists.debian.org Usertags: ruby3.0 Hi, We are about to enable building against ruby3.0 on unstable. During a test rebuild, ruby-rack-timeout was found to fail to build in that situation. To reproduce this locally, you need to install ruby-all-dev from experimental on an unstable system or build chroot. Relevant part (hopefully): > Error: test_zero_wait_timeout(EnvSettingsTest): ArgumentError: wrong number > of arguments (given 2, expected 1) > /<>/debian/ruby-rack-timeout/usr/lib/ruby/vendor_ruby/rack/timeout/core.rb:67:in > `initialize' > /usr/lib/ruby/vendor_ruby/rack/builder.rb:102:in `new' > /usr/lib/ruby/vendor_ruby/rack/builder.rb:102:in `block in use' > /usr/lib/ruby/vendor_ruby/rack/builder.rb:171:in `block in to_app' > /usr/lib/ruby/vendor_ruby/rack/builder.rb:171:in `each' > /usr/lib/ruby/vendor_ruby/rack/builder.rb:171:in `inject' > /usr/lib/ruby/vendor_ruby/rack/builder.rb:171:in `to_app' > /usr/lib/ruby/vendor_ruby/rack/builder.rb:177:in `call' > /usr/lib/ruby/vendor_ruby/rack/mock_session.rb:30:in `request' > /usr/lib/ruby/vendor_ruby/rack/test.rb:249:in `process_request' > /usr/lib/ruby/vendor_ruby/rack/test.rb:59:in `get' > /usr/lib/ruby/3.0.0/forwardable.rb:238:in `get' > /<>/test/env_settings_test.rb:15:in `block in > test_zero_wait_timeout' > 12: > 13: def test_zero_wait_timeout > 14: with_env(RACK_TIMEOUT_WAIT_TIMEOUT: 0) do > => 15: get "/", "", 'HTTP_X_REQUEST_START' => time_in_msec(Time.now - > 100) > 16: assert last_response.ok? > 17: end > 18: end > /<>/test/test_helper.rb:36:in `with_env' > /<>/test/env_settings_test.rb:14:in `test_zero_wait_timeout' > === > : (0.001047) > > Finished in 0.032033303 seconds. > --- > 5 tests, 3 assertions, 3 failures, 2 errors, 0 pendings, 0 omissions, 0 > notifications > 0% passed > --- > 156.09 tests/s, 93.65 assertions/s > rake aborted! > Command failed with status (1): [ruby -w -I"test" > /usr/lib/ruby/gems/3.0.0/gems/rake-13.0.3/lib/rake/rake_test_loader.rb > "test/basic_test.rb" "test/env_settings_test.rb" -v] > > Tasks: TOP => default > (See full trace by running task with --trace) > ERROR: Test "ruby3.0" failed: The full build log is available at https://people.debian.org/~kanashiro/ruby3.0/round2/builds/3/ruby-rack-timeout/ruby-rack-timeout_0.5.1-2+rebuild1633391987_amd64.build.txt signature.asc Description: PGP signature --- End Message --- --- Begin Message --- Source: ruby-rack-timeout Source-Version: 0.5.1-3 Done: Daniel Leidert We believe that the bug you reported is fixed in the latest version of ruby-rack-timeout, 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 996...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Daniel Leidert (supplier of updated ruby-rack-timeout 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: Thu, 25 Nov 2021 20:31:01 +0100 Source: ruby-rack-timeout Architecture: source Version: 0.5.1-3 Distribution: unstable Urgency: low Maintainer: Debian Ruby Team Changed-By: Daniel Leidert Closes: 996352 Changes: ruby-rack-timeout (0.5.1-3) unstable; urgency=low . * Team upload. . [ Debian Janitor ] * Remove obsolete field Name from
Processed: tagging 996223
Processing commands for cont...@bugs.debian.org: > # this is the predecessor of ruby-factory-bot and an RM requets is pending > tags 996223 + wontfix Bug #996223 [src:ruby-factory-girl] ruby-factory-girl: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed: ArgumentError: Added tag(s) wontfix. > thanks Stopping processing here. Please contact me if you need assistance. -- 996223: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=996223 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: tagging 996297
Processing commands for cont...@bugs.debian.org: > tags 996297 + upstream Bug #996297 [src:ruby-ice-nine] ruby-ice-nine: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed: Failure/Error: expect(subject.end).to be_frozen Ignoring request to alter tags of bug #996297 to the same tags previously set > thanks Stopping processing here. Please contact me if you need assistance. -- 996297: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=996297 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#996352: marked as pending in ruby-rack-timeout
Control: tag -1 pending Hello, Bug #996352 in ruby-rack-timeout 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/ruby-team/ruby-rack-timeout/-/commit/df14f02502c32de385e237a09cdbf1a1107bc93b Add patch to fix Ruby 3.0 compatbility * d/patches/Explicitly-convert-hash-to-kwargs-in-test_helper.patch: Add. - Fix for Ruby 3.0 keyword argument handling (closes: #996352). * d/patches/series: Add new patch. (this message was generated automatically) -- Greetings https://bugs.debian.org/996352
Processed: Bug#996352 marked as pending in ruby-rack-timeout
Processing control commands: > tag -1 pending Bug #996352 [src:ruby-rack-timeout] ruby-rack-timeout: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed: Error: test_zero_wait_timeout(EnvSettingsTest): ArgumentError: wrong number of arguments (given 2, expected 1) Added tag(s) pending. -- 996352: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=996352 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#969157: marked as done (ruby-diaspora-federation-rails: FTBFS with rails 6 - Could not find 'actionpack' (< 6, >= 4.2) - did find: [actionpack-6.0.3.1])
Your message dated Thu, 25 Nov 2021 19:18:53 +
with message-id
and subject line Bug#969157: fixed in ruby-diaspora-federation-rails 0.2.7-1
has caused the Debian Bug report #969157,
regarding ruby-diaspora-federation-rails: FTBFS with rails 6 - Could not find
'actionpack' (< 6, >= 4.2) - did find: [actionpack-6.0.3.1]
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
969157: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=969157
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: ruby-diaspora-federation-rails
Version: 0.2.6-1
Severity: serious
User: pkg-ruby-extras-maintain...@lists.alioth.debian.org
Usertags: rails6-transition
This package fails to build from source with rails 6.
┌──┐
│ Checking Rubygems dependency resolution on ruby2.7 │
└──┘
GEM_PATH=/<>/debian/ruby-diaspora-federation-rails/usr/share/rubygems-integration/all:/var/lib/gems/2.7.0:/usr/lib/ruby/gems/2.7.0:/usr/share/rubygems-integration/2.7.0:/usr/share/rubygems-integration/all:/usr/lib/x86_64-linux-gnu/rubygems-integration/2.7.0
ruby2.7 -e gem\ \"diaspora_federation-rails\"
/usr/lib/ruby/2.7.0/rubygems/dependency.rb:313:in `to_specs': Could not
find 'actionpack' (< 6, >= 4.2) - did find: [actionpack-6.0.3.1]
(Gem::MissingSpecVersionError)
Checked in
'GEM_PATH=/<>/debian/ruby-diaspora-federation-rails/usr/share/rubygems-integration/all:/var/lib/gems/2.7.0:/usr/lib/ruby/gems/2.7.0:/usr/share/rubygems-integration/2.7.0:/usr/share/rubygems-integration/all:/usr/lib/x86_64-linux-gnu/rubygems-integration/2.7.0',
execute `gem env` for more information
from /usr/lib/ruby/2.7.0/rubygems/specification.rb:1402:in `block in
activate_dependencies'
from /usr/lib/ruby/2.7.0/rubygems/specification.rb:1391:in `each'
from /usr/lib/ruby/2.7.0/rubygems/specification.rb:1391:in
`activate_dependencies'
from /usr/lib/ruby/2.7.0/rubygems/specification.rb:1373:in `activate'
from /usr/lib/ruby/2.7.0/rubygems/core_ext/kernel_gem.rb:68:in `block
in gem'
from /usr/lib/ruby/2.7.0/rubygems/core_ext/kernel_gem.rb:68:in
`synchronize'
from /usr/lib/ruby/2.7.0/rubygems/core_ext/kernel_gem.rb:68:in `gem'
from -e:1:in `'
Full log is
https://people.debian.org/~praveen/rails6-meta-build/buildlogs/ruby-diaspora-federation-rails.log
--- End Message ---
--- Begin Message ---
Source: ruby-diaspora-federation-rails
Source-Version: 0.2.7-1
Done: Daniel Leidert
We believe that the bug you reported is fixed in the latest version of
ruby-diaspora-federation-rails, 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 969...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Daniel Leidert (supplier of updated
ruby-diaspora-federation-rails 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: Thu, 25 Nov 2021 19:43:17 +0100
Source: ruby-diaspora-federation-rails
Architecture: source
Version: 0.2.7-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Ruby Team
Changed-By: Daniel Leidert
Closes: 969157
Changes:
ruby-diaspora-federation-rails (0.2.7-1) unstable; urgency=medium
.
* Team upload.
* New upstream release.
* d/control (Standards-Version): Bump to 4.6.0.
(Depends): Use ${ruby:Depends}.
(Build-Depends): Bump debhelper to version 13.
* d/copyright: Add Upstream-Contact field.
(Source): Update URL.
(Copyright): Add team.
* d/rules: Use gem installation layout and install upstream changelog.
Exclude app from installation into rubygems destination.
* d/patches/relax-rails-dep.patch: Add patch.
- Relax Rails dependency accordingly to upstream's master
branch (closes: #969157).
* d/patches/series: Add new patch.
* d/tests/control.ex: Remove example template.
* d/upstream/metadata: Remove Name and Contact fields and update the rest.
Checksums-Sha1:
e415328791e767a391b11bf9fc6ec706b05ebced 2281
ruby-diaspora-federation-rails_0.2.7-1.dsc
b04c9fc34920dea50ee6930dc061bb43b529f27b 20425
Processed: retitle 1000603 to specutils FTBFS with astropy 5.0
Processing commands for cont...@bugs.debian.org: > retitle 1000603 specutils FTBFS with astropy 5.0 Bug #1000603 [src:specutils] specutils FTBFS with Python 3.10 Changed Bug title to 'specutils FTBFS with astropy 5.0' from 'specutils FTBFS with Python 3.10'. > thanks Stopping processing here. Please contact me if you need assistance. -- 1000603: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1000603 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: bug 1000603 is forwarded to https://github.com/astropy/specutils/issues/893
Processing commands for cont...@bugs.debian.org: > forwarded 1000603 https://github.com/astropy/specutils/issues/893 Bug #1000603 [src:specutils] specutils FTBFS with astropy 5.0 Set Bug forwarded-to-address to 'https://github.com/astropy/specutils/issues/893'. > thanks Stopping processing here. Please contact me if you need assistance. -- 1000603: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1000603 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#969157: marked as pending in ruby-diaspora-federation-rails
Control: tag -1 pending Hello, Bug #969157 in ruby-diaspora-federation-rails 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/ruby-team/ruby-diaspora-federation-rails/-/commit/1f6da353e718c690b24133e094fea601193e1fbc ruby-diaspora-federation-rails (0.2.7-1) UNRELEASED * New upstream release. - Adds support for Ruby 3.0 and Rails < 7 (closes: #969157). (this message was generated automatically) -- Greetings https://bugs.debian.org/969157
Processed: Bug#969157 marked as pending in ruby-diaspora-federation-rails
Processing control commands: > tag -1 pending Bug #969157 [ruby-diaspora-federation-rails] ruby-diaspora-federation-rails: FTBFS with rails 6 - Could not find 'actionpack' (< 6, >= 4.2) - did find: [actionpack-6.0.3.1] Ignoring request to alter tags of bug #969157 to the same tags previously set -- 969157: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=969157 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Bug#969157 marked as pending in ruby-diaspora-federation-rails
Processing control commands: > tag -1 pending Bug #969157 [ruby-diaspora-federation-rails] ruby-diaspora-federation-rails: FTBFS with rails 6 - Could not find 'actionpack' (< 6, >= 4.2) - did find: [actionpack-6.0.3.1] Added tag(s) pending. -- 969157: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=969157 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#969157: marked as pending in ruby-diaspora-federation-rails
Control: tag -1 pending Hello, Bug #969157 in ruby-diaspora-federation-rails 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/ruby-team/ruby-diaspora-federation-rails/-/commit/e71e325c7082d5a144a31282386c04da4445ec49 Add patch to backport Rails 6 support * d/patches/relax-rails-dep.patch: Add patch. - Relax Rails dependency accordingly to upstream's master branch (closes: #969157). * d/patches/series: Add new patch. The change has not been shipped with version 0.2.7. Therefor we have to "backport" the patch. (this message was generated automatically) -- Greetings https://bugs.debian.org/969157
Bug#1000603: specutils FTBFS with Python 3.10
Source: specutils
Version: 1.4.1-1
Severity: serious
Tags: ftbfs
https://buildd.debian.org/status/logs.php?pkg=specutils=1.4.1-1%2Bb1
...
=== FAILURES ===
__ test_continuum_calculation __
def test_continuum_calculation():
"""
This test fits the first simulated spectrum from the fixture. The
initial guesses are manually set here with bounds that essentially make
sense as the functionality of the test is to make sure the fit works and
we get a reasonable answer out **given** good initial guesses.
"""
x_single_continuum, y_single_continuum = single_peak_continuum()
spectrum = Spectrum1D(flux=y_single_continuum*u.Jy,
spectral_axis=x_single_continuum*u.um)
g1_fit = fit_generic_continuum(spectrum)
> spectrum_normalized = spectrum / g1_fit(spectrum.spectral_axis)
specutils/tests/test_continuum.py:60:
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
specutils/spectra/spectrum1d.py:568: in __truediv__
return self.divide(other)
/usr/lib/python3/dist-packages/astropy/nddata/mixins/ndarithmetic.py:536: in
divide
return self._prepare_then_do_arithmetic(np.true_divide, operand,
/usr/lib/python3/dist-packages/astropy/nddata/mixins/ndarithmetic.py:610: in
_prepare_then_do_arithmetic
operand2 = cls(operand2)
specutils/spectra/spectrum1d.py:288: in __init__
spec_axis = self.wcs.pixel_to_world(np.arange(self.flux.shape[-1]))
specutils/utils/wcs_utils.py:217: in pixel_to_world
return super().pixel_to_world(*args, **kwargs).to(
/usr/lib/python3/dist-packages/gwcs/api.py:299: in pixel_to_world
return self(*pixels, with_units=True)
/usr/lib/python3/dist-packages/gwcs/wcs.py:379: in __call__
result = self.output_frame.coordinates(result)
/usr/lib/python3/dist-packages/gwcs/coordinate_frames.py:463: in coordinates
return coord.SpectralCoord(*args).to(self.unit[0])
/usr/lib/python3/dist-packages/astropy/units/decorators.py:304: in wrapper
return_ = wrapped_function(*func_args, **func_kwargs)
/usr/lib/python3/dist-packages/astropy/coordinates/spectral_coordinate.py:193:
in __new__
obj = super().__new__(cls, value, unit=unit, **kwargs)
/usr/lib/python3/dist-packages/astropy/coordinates/spectral_quantity.py:57: in
__new__
obj = super().__new__(cls, value, unit=unit, **kwargs)
/usr/lib/python3/dist-packages/astropy/units/quantity.py:425: in __new__
value = value.view(cls)
/usr/lib/python3/dist-packages/astropy/coordinates/spectral_coordinate.py:242:
in __array_finalize__
super().__array_finalize__(obj)
/usr/lib/python3/dist-packages/astropy/coordinates/spectral_quantity.py:72: in
__array_finalize__
super().__array_finalize__(obj)
/usr/lib/python3/dist-packages/astropy/units/quantity.py:550: in
__array_finalize__
self._set_unit(unit)
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
self = <[AttributeError("SpectralCoord instance has no attribute
'radial_velocity'") raised in repr()] SpectralCoord object at 0x7f389f6d3d10>
unit = Unit(dimensionless)
def _set_unit(self, unit):
if unit is None or not unit.is_equivalent(self._equivalent_unit):
> raise UnitTypeError(
"{} instances require units equivalent to '{}'"
.format(type(self).__name__, self._equivalent_unit) +
(", but no unit was given." if unit is None else
f", so cannot set it to '{unit}'."))
E astropy.units.core.UnitTypeError: SpectralCoord instances require
units equivalent to '(Unit("Hz"), Unit("m"), Unit("J"), Unit("1 / m"), Unit("km
/ s"))', so cannot set it to ''.
/usr/lib/python3/dist-packages/astropy/units/quantity.py:1933: UnitTypeError
__ test_continuum_full_window __
def test_continuum_full_window():
"""
This test fits the first simulated spectrum from the fixture, but
with the fit_continuum function instead of fit_generic_continuum. Uses
a window to select the entire spectrum and checks that it recovers the
original, non-windowed fit.
"""
x_single_continuum, y_single_continuum = single_peak_continuum()
spectrum = Spectrum1D(flux=y_single_continuum*u.Jy,
spectral_axis=x_single_continuum*u.um)
# Smooth in the same way fit_generic_continuum does.
spectrum_smoothed = median_smooth(spectrum, 3)
# Check that a full width window recovers the original, non-windowed
fit.
g1_fit = fit_continuum(spectrum_smoothed, window=(0.*u.um, 10.*u.um))
g1_fit_orig = fit_continuum(spectrum_smoothed)
> sp_normalized = spectrum / g1_fit(spectrum.spectral_axis)
specutils/tests/test_continuum.py:88:
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
Bug#1000365: marked as done (Current pyzmq not playing well with Python 3.10 ?)
Your message dated Thu, 25 Nov 2021 20:01:58 +0100 with message-id and subject line Fixed indeed! has caused the Debian Bug report #1000365, regarding Current pyzmq not playing well with Python 3.10 ? 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.) -- 1000365: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1000365 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: python3-zmq Version: 22.3.0-1 Severity: grave I have issues updating packages nbconvert and jupyterlab-server, both of which because of autopkgtest failures, with the similar-looking backtrace: autopkgtest [08:13:59]: test autodep8-python3: [--- Testing with python3.10: Traceback (most recent call last): File "", line 1, in File "/usr/lib/python3/dist-packages/nbconvert/__init__.py", line 4, in from .exporters import * File "/usr/lib/python3/dist- packages/nbconvert/exporters/__init__.py", line 4, in from .slides import SlidesExporter File "/usr/lib/python3/dist-packages/nbconvert/exporters/slides.py", line 12, in from ..preprocessors.base import Preprocessor File "/usr/lib/python3/dist- packages/nbconvert/preprocessors/__init__.py", line 10, in from .execute import ExecutePreprocessor File "/usr/lib/python3/dist- packages/nbconvert/preprocessors/execute.py", line 8, in from nbclient import NotebookClient, execute as _execute File "/usr/lib/python3/dist-packages/nbclient/__init__.py", line 5, in from .client import NotebookClient, execute # noqa: F401 File "/usr/lib/python3/dist-packages/nbclient/client.py", line 21, in from jupyter_client import KernelManager File "/usr/lib/python3/dist-packages/jupyter_client/__init__.py", line 6, in from .asynchronous import AsyncKernelClient # noqa File "/usr/lib/python3/dist- packages/jupyter_client/asynchronous/__init__.py", line 1, in from .client import AsyncKernelClient # noqa File "/usr/lib/python3/dist- packages/jupyter_client/asynchronous/client.py", line 6, in from jupyter_client.channels import HBChannel File "/usr/lib/python3/dist-packages/jupyter_client/channels.py", line 12, in import zmq.asyncio File "/usr/lib/python3/dist-packages/zmq/__init__.py", line 103, in from zmq import backend File "/usr/lib/python3/dist-packages/zmq/backend/__init__.py", line 32, in raise original_error from None File "/usr/lib/python3/dist-packages/zmq/backend/__init__.py", line 27, in _ns = select_backend(first) File "/usr/lib/python3/dist-packages/zmq/backend/select.py", line 32, in select_backend mod = import_module(name) File "/usr/lib/python3.10/importlib/__init__.py", line 126, in import_module return _bootstrap._gcd_import(name[level:], package, level) File "/usr/lib/python3/dist-packages/zmq/backend/cython/__init__.py", line 6, in from . import ( ImportError: cannot import name 'constants' from partially initialized module 'zmq.backend.cython' (most likely due to a circular import) (/usr/lib/python3/dist-packages/zmq/backend/cython/__init__.py) autopkgtest [08:14:00]: test autodep8-python3: ---] The same error message is discussed here: https://github.com/zeromq/pyzmq/issues/1460 but it looks like the error message in fact hides the real issue... Cheers, J.Puydt --- End Message --- --- Begin Message --- Hi, the b1 upload indeed made those disappear, so they were transitory: I can close this bug report. Thanks! J.Puydt--- End Message ---
Bug#1000601: python3-casa-formats-io need to depend on a versioned python3-numpy
Package: python3-casa-formats-io Version: 0.1-1 Severity: serious https://ci.debian.net/data/autopkgtest/testing/arm64/c/casa-formats-io/16993092/log.gz ... ___ ERROR collecting tests/test_casa_dask.py ___ ImportError while importing test module '/usr/lib/python3/dist-packages/casa_formats_io/tests/test_casa_dask.py'. Hint: make sure your test modules/packages have valid Python names. Traceback: /usr/lib/python3.9/importlib/__init__.py:127: in import_module return _bootstrap._gcd_import(name[level:], package, level) /usr/lib/python3/dist-packages/casa_formats_io/__init__.py:1: in from .casa_dask import * # noqa /usr/lib/python3/dist-packages/casa_formats_io/casa_dask.py:13: in from ._casa_chunking import _combine_chunks E ImportError: numpy.core.multiarray failed to import --- Captured stderr RuntimeError: module compiled against API version 0xe but this version of numpy is 0xd ... python3-casa-formats-io needs a generated dependency on python3-numpy-api*
Bug#1000578: marked as done (liblogfile-rotate-perl: autopkgtest failure: Can't locate logfile.pm in @INC)
Your message dated Thu, 25 Nov 2021 18:04:50 + with message-id and subject line Bug#1000578: fixed in liblogfile-rotate-perl 1.04-6 has caused the Debian Bug report #1000578, regarding liblogfile-rotate-perl: autopkgtest failure: Can't locate logfile.pm in @INC to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1000578: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1000578 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: liblogfile-rotate-perl Version: 1.04-5 X-Debbugs-CC: debian...@lists.debian.org Severity: serious User: debian...@lists.debian.org Usertags: fails-always Dear maintainer(s), You recently added an autopkgtest to your package liblogfile-rotate-perl, great. However, it fails. Currently this failure is blocking the migration to testing [1]. Can you please investigate the situation and fix it? I copied some of the output at the bottom of this report. More information about this bug and the reason for filing it can be found on https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation Paul [1] https://qa.debian.org/excuses.php?package=liblogfile-rotate-perl https://ci.debian.net/data/autopkgtest/testing/amd64/libl/liblogfile-rotate-perl/16716636/log.gz https://ci.debian.net/data/autopkgtest/testing/amd64/libl/liblogfile-rotate-perl/16716636/log.gz # Failed test ' /usr/bin/perl -w -M"logfile-rotate" -e 1 2>&1 exited successfully' # at /usr/share/pkg-perl-autopkgtest/runtime-deps.d/use.t line 105. # Failed test ' /usr/bin/perl -w -M"logfile-rotate" -e 1 2>&1 produced no (non-whitelisted) output' # at /usr/share/pkg-perl-autopkgtest/runtime-deps.d/use.t line 107. # Failed test 'env PERL_DL_NONLAZY=1 /usr/bin/perl -w -M"logfile-rotate" -e 1 2>&1 exited successfully' # at /usr/share/pkg-perl-autopkgtest/runtime-deps.d/use.t line 105. # Failed test 'env PERL_DL_NONLAZY=1 /usr/bin/perl -w -M"logfile-rotate" -e 1 2>&1 produced no (non-whitelisted) output' # at /usr/share/pkg-perl-autopkgtest/runtime-deps.d/use.t line 107. # Looks like you failed 4 tests of 4. /usr/share/pkg-perl-autopkgtest/runtime-deps.d/use.t .. 1..4 # Can't locate logfile.pm in @INC (you may need to install the logfile module) (@INC contains: /etc/perl /usr/local/lib/x86_64-linux-gnu/perl/5.32.1 /usr/local/share/perl/5.32.1 /usr/lib/x86_64-linux-gnu/perl5/5.32 /usr/share/perl5 /usr/lib/x86_64-linux-gnu/perl-base /usr/lib/x86_64-linux-gnu/perl/5.32 /usr/share/perl/5.32 /usr/local/lib/site_perl). # BEGIN failed--compilation aborted. not ok 1 - /usr/bin/perl -w -M"logfile-rotate" -e 1 2>&1 exited successfully not ok 2 - /usr/bin/perl -w -M"logfile-rotate" -e 1 2>&1 produced no (non-whitelisted) output # Can't locate logfile.pm in @INC (you may need to install the logfile module) (@INC contains: /etc/perl /usr/local/lib/x86_64-linux-gnu/perl/5.32.1 /usr/local/share/perl/5.32.1 /usr/lib/x86_64-linux-gnu/perl5/5.32 /usr/share/perl5 /usr/lib/x86_64-linux-gnu/perl-base /usr/lib/x86_64-linux-gnu/perl/5.32 /usr/share/perl/5.32 /usr/local/lib/site_perl). # BEGIN failed--compilation aborted. not ok 3 - env PERL_DL_NONLAZY=1 /usr/bin/perl -w -M"logfile-rotate" -e 1 2>&1 exited successfully not ok 4 - env PERL_DL_NONLAZY=1 /usr/bin/perl -w -M"logfile-rotate" -e 1 2>&1 produced no (non-whitelisted) output Dubious, test returned 4 (wstat 1024, 0x400) Failed 4/4 subtests Test Summary Report --- /usr/share/pkg-perl-autopkgtest/runtime-deps.d/use.t (Wstat: 1024 Tests: 4 Failed: 4) Failed tests: 1-4 Non-zero exit status: 4 Files=1, Tests=4, 0 wallclock secs ( 0.03 usr 0.00 sys + 0.11 cusr 0.00 csys = 0.14 CPU) Result: FAIL autopkgtest [09:11:29]: test autodep8-perl OpenPGP_signature Description: OpenPGP digital signature --- End Message --- --- Begin Message --- Source: liblogfile-rotate-perl Source-Version: 1.04-6 Done: tony mancill We believe that the bug you reported is fixed in the latest version of liblogfile-rotate-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 1000...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. tony mancill (supplier of updated liblogfile-rotate-perl package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive
Bug#1000597: dnsproxy only works with DNS servers at localhost
Package: dnsproxy Version: 1.17-2 Severity: serious X-Debbugs-Cc: mar...@talau.info Hi there, The dnsproxy (1.17-2) only works with DNS servers at localhost. This is a problem, as you cannot use DNS servers from other hosts. The problem was introduced by patch 03_fix_listen_udp_port.patch. But without this patch, the bug #1000159 comes back, and this can generate a possible security breach. The discussion with upstream about this can be found here [1]. [1] https://github.com/awaw/dnsproxy/issues/6 Regards, mt signature.asc Description: PGP signature
Bug#964607: Massive update necessary
This gem is out-of-date. Upstream is at 3.2.2, which requires packaging for google-cloud-translate-v2 and google-cloud-translate-v3 and updating google- cloud-core to >= 1.6. The tests require packageing google-style. Regards, Daniel -- Regards, Daniel Leidert | https://www.wgdd.de/ GPG-Key RSA4096 / BEED4DED5544A4C03E283DC74BCD0567C296D05D GPG-Key ED25519 / BD3C132D8B3805D1808123AB7ACE00941E338C78 https://www.fiverr.com/dleidert https://www.patreon.com/join/dleidert signature.asc Description: This is a digitally signed message part
Bug#1000578: marked as pending in liblogfile-rotate-perl
Control: tag -1 pending Hello, Bug #1000578 in liblogfile-rotate-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/liblogfile-rotate-perl/-/commit/85a3f1c930e26cc0a9dae70d67ad71e083e8c92c Correct module name in autopkgtest (Closes: #1000578) (this message was generated automatically) -- Greetings https://bugs.debian.org/1000578
Processed: Bug#1000578 marked as pending in liblogfile-rotate-perl
Processing control commands: > tag -1 pending Bug #1000578 [src:liblogfile-rotate-perl] liblogfile-rotate-perl: autopkgtest failure: Can't locate logfile.pm in @INC Added tag(s) pending. -- 1000578: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1000578 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#992564: marked as done (FTBFS: "rpc/rpc.h" not found (removed from glibc 2.32))
Your message dated Thu, 25 Nov 2021 17:33:38 + with message-id and subject line Bug#992564: fixed in caml-crush 1.0.12-1 has caused the Debian Bug report #992564, regarding FTBFS: "rpc/rpc.h" not found (removed from glibc 2.32) 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.) -- 992564: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=992564 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: caml-crush Severity: serious Tags: upstream ftbfs Dear Maintainer, The package fails to build from source in clean environments as it relies on "rpc/rpc.h" being present, while those headers have been removed in glibc 2.32, considered obsolete. The solution is to use tirpc instead. There is a PR upstream to adapt the build system to use tirpc : https://github.com/caml-pkcs11/caml-crush/pull/47 -- System Information: Debian Release: 11.0 APT prefers impish APT policy: (500, 'impish'), (50, 'impish-proposed') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.13.0-14-generic (SMP w/8 CPU threads) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled --- End Message --- --- Begin Message --- Source: caml-crush Source-Version: 1.0.12-1 Done: Thomas Calderon We believe that the bug you reported is fixed in the latest version of caml-crush, 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 992...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Thomas Calderon (supplier of updated caml-crush 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: Thu, 25 Nov 2021 15:23:09 + Source: caml-crush Architecture: source Version: 1.0.12-1 Distribution: unstable Urgency: medium Maintainer: Thomas Calderon Changed-By: Thomas Calderon Closes: 992564 Changes: caml-crush (1.0.12-1) unstable; urgency=medium . * Fix makefile bugs . caml-crush (1.0.11-2) unstable; urgency=medium . * Debian lints . caml-crush (1.0.11-1) unstable; urgency=medium . * Introduces TIRPC support (Closes: #992564) Checksums-Sha1: f7b7ec91ac4b76f89e121f22d96ecf2895864c3c 1961 caml-crush_1.0.12-1.dsc 67939c21a5c335420e203a751025b8682b49eed1 351924 caml-crush_1.0.12.orig.tar.gz e3899f12d46fc0a11938b4a9e4ec60e468726bce 5968 caml-crush_1.0.12-1.debian.tar.xz Checksums-Sha256: f99ff264f73687231d33924077e7425593a329e0e45c71c011357215eb5dfa01 1961 caml-crush_1.0.12-1.dsc 4d93d57344c5acb1df97fb4f205906c52f84406e9b00e42999ac6af1ff3d3471 351924 caml-crush_1.0.12.orig.tar.gz b17193965a139d31583d8d9dc226cd8edf730e4e6d977d7df864015f056ec4f9 5968 caml-crush_1.0.12-1.debian.tar.xz Files: 1c0bea84ee979ecb5f05b950ad8d1190 1961 net optional caml-crush_1.0.12-1.dsc 9ef78093c5a0fc829e06fc2ee86199a3 351924 net optional caml-crush_1.0.12.orig.tar.gz a2ace8acd967eb750653fb87efd8b445 5968 net optional caml-crush_1.0.12-1.debian.tar.xz -BEGIN PGP SIGNATURE- iQEzBAEBCgAdFiEEbeJOl+yohsxW5iUOIbju8bGJMIEFAmGfwmEACgkQIbju8bGJ MIFFqQf+J2dAAWekradt9OZ6b8YFB5Pxz78WDG24lrXGdnqKQA/dS+BVj5SK+rdv SBl8IluZaeZx9nPYgnG9cRVWVKowtMINYID40uH2ksmgeofy2jmK/QrZ+4hp1WcC gXirDOvR+em6ftBDo4kJQ7kqXHGf90uCuatXDJJ/JUV5s0dQcHUOHgel8Ukjw5Gj WIkm6C0H5ILmwnOXbzUCIiytPPgqPkzu+l2z6zrq6QMbqZyGjN3kqxLzV9iGwNdN nG9G0DlSzHYUbpAcqbavs/qx4MUp3J9pQdMvXAMtZyrvVOROTLA2MM3YcYv92b7s yyJdRQgX3aT4I69Y6IC1CGEDD6Sazg== =alJ/ -END PGP SIGNATURE End Message ---
Processed: retitle 1000289 to mbedtls: enabling CMAC support changes ABI
Processing commands for cont...@bugs.debian.org: > retitle 1000289 mbedtls: enabling CMAC support changes ABI Bug #1000289 [mbedtls] tests failing when mbedtls is compiled with CMAC support Changed Bug title to 'mbedtls: enabling CMAC support changes ABI' from 'tests failing when mbedtls is compiled with CMAC support'. > thanks Stopping processing here. Please contact me if you need assistance. -- 1000289: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1000289 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#999626: marked as done (maxima-emacs: fails to install with xemacs21)
Your message dated Thu, 25 Nov 2021 16:48:50 +
with message-id
and subject line Bug#999626: fixed in maxima 5.45.1-6
has caused the Debian Bug report #999626,
regarding maxima-emacs: fails to install with xemacs21
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.)
--
999626: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=999626
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: maxima-emacs
Version: 5.45.1-4
Severity: serious
Hi,
maxima-emacs fails to install if xemacs21 is installed:
Setting up maxima-emacs (5.45.1-4) ...
Install emacsen-common for xemacs21
emacsen-common: Handling install of emacsen flavor xemacs21
Loading /usr/share/emacsen-common/debian-startup...
Loading 00debian...
Compiling /usr/share/xemacs21/site-lisp/debian-startup.el...
Wrote /usr/share/xemacs21/site-lisp/debian-startup.elc
Done
Install maxima-emacs for xemacs21
install/maxima: Handling install for emacsen flavor xemacs21
Compiling /usr/share/xemacs21/site-lisp/maxima/bookmode.el...
Wrote /usr/share/xemacs21/site-lisp/maxima/bookmode.elc
Compiling /usr/share/xemacs21/site-lisp/maxima/emaxima.el...
Wrote /usr/share/xemacs21/site-lisp/maxima/emaxima.elc
Compiling /usr/share/xemacs21/site-lisp/maxima/imath.el...
While compiling toplevel forms in file
/usr/share/xemacs21/site-lisp/maxima/imath.el:
!! File error (("Cannot open load file" "cl-lib"))
>>Error occurred processing imath.el: Cannot open load file: cl-lib
Compiling
/usr/share/xemacs21/site-lisp/maxima/imaxima-autoconf-variables.el...
Wrote /usr/share/xemacs21/site-lisp/maxima/imaxima-autoconf-variables.elc
Compiling /usr/share/xemacs21/site-lisp/maxima/imaxima.el...
While compiling toplevel forms in file
/usr/share/xemacs21/site-lisp/maxima/imaxima.el:
** misplaced interactive spec: (interactive)
** misplaced interactive spec: (interactive "")
** misplaced interactive spec: (interactive "")
** misplaced interactive spec: (interactive "")
** misplaced interactive spec: (interactive "")
** misplaced interactive spec: (interactive "")
Wrote /usr/share/xemacs21/site-lisp/maxima/imaxima.elc
Compiling /usr/share/xemacs21/site-lisp/maxima/maxima-font-lock.el...
Wrote /usr/share/xemacs21/site-lisp/maxima/maxima-font-lock.elc
Compiling /usr/share/xemacs21/site-lisp/maxima/maxima.el...
Wrote /usr/share/xemacs21/site-lisp/maxima/maxima.elc
Compiling /usr/share/xemacs21/site-lisp/maxima/mylatex.ltx.el...
Wrote /usr/share/xemacs21/site-lisp/maxima/mylatex.ltx.elc
Compiling /usr/share/xemacs21/site-lisp/maxima/setup-imaxima-imath.el...
Wrote /usr/share/xemacs21/site-lisp/maxima/setup-imaxima-imath.elc
Compiling /usr/share/xemacs21/site-lisp/maxima/smart-complete.el...
Wrote /usr/share/xemacs21/site-lisp/maxima/smart-complete.elc
Compiling /usr/share/xemacs21/site-lisp/maxima/sshell.el...
Wrote /usr/share/xemacs21/site-lisp/maxima/sshell.elc
Done
ERROR: install script from maxima-emacs package failed
dpkg: error processing package maxima-emacs (--configure):
installed maxima-emacs package post-installation script subprocess returned
error exit status 1
Andreas
maxima-emacs=5.45.1-4_xemacs21.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: maxima
Source-Version: 5.45.1-6
Done: Camm Maguire
We believe that the bug you reported is fixed in the latest version of
maxima, 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 999...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Camm Maguire (supplier of updated maxima 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: Thu, 25 Nov 2021 16:28:00 +
Source: maxima
Architecture: source
Version: 5.45.1-6
Distribution: unstable
Urgency: medium
Maintainer: Camm Maguire
Changed-By: Camm Maguire
Closes: 999626
Changes:
maxima (5.45.1-6) unstable; urgency=medium
.
* maxima-emacs conflicts with xemacs21
* reverse earlier patch attempts
* Bug fix: "fails to install with xemacs21", thanks to Andreas Beckmann
(Closes: #999626).
Checksums-Sha1:
Processed: maxima-emacs: fails to install with xemacs21
Processing commands for cont...@bugs.debian.org: > forwarded 999626 maxima-disc...@lists.sourceforge.net Bug #999626 [maxima-emacs] maxima-emacs: fails to install with xemacs21 Set Bug forwarded-to-address to 'maxima-disc...@lists.sourceforge.net'. > thanks Stopping processing here. Please contact me if you need assistance. -- 999626: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=999626 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#996323: marked as done (ruby-mono-logger: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed: ArgumentError: wrong number of arguments (given 2, expected 0..1))
Your message dated Thu, 25 Nov 2021 16:34:48 + with message-id and subject line Bug#996323: fixed in ruby-mono-logger 1.1.1-1 has caused the Debian Bug report #996323, regarding ruby-mono-logger: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed: ArgumentError: wrong number of arguments (given 2, expected 0..1) to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 996323: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=996323 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: ruby-mono-logger Version: 1.1.0-3.1 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: debian-r...@lists.debian.org Usertags: ruby3.0 Hi, We are about to enable building against ruby3.0 on unstable. During a test rebuild, ruby-mono-logger was found to fail to build in that situation. To reproduce this locally, you need to install ruby-all-dev from experimental on an unstable system or build chroot. Relevant part (hopefully): > ArgumentError: wrong number of arguments (given 2, expected 0..1) > /usr/lib/ruby/3.0.0/logger/log_device.rb:14:in `initialize' > /<>/test/mri_logger_test.rb:289:in `new' > /<>/test/mri_logger_test.rb:289:in `d' > /<>/test/mri_logger_test.rb:323:in `test_write' > /usr/lib/ruby/vendor_ruby/minitest/test.rb:98:in `block (3 levels) in run' > /usr/lib/ruby/vendor_ruby/minitest/test.rb:195:in `capture_exceptions' > /usr/lib/ruby/vendor_ruby/minitest/test.rb:95:in `block (2 levels) in run' > /usr/lib/ruby/vendor_ruby/minitest.rb:270:in `time_it' > /usr/lib/ruby/vendor_ruby/minitest/test.rb:94:in `block in run' > /usr/lib/ruby/vendor_ruby/minitest.rb:365:in `on_signal' > /usr/lib/ruby/vendor_ruby/minitest/test.rb:211:in `with_info_handler' > /usr/lib/ruby/vendor_ruby/minitest/test.rb:93:in `run' > /usr/lib/ruby/vendor_ruby/minitest.rb:1029:in `run_one_method' > /usr/lib/ruby/vendor_ruby/minitest.rb:339:in `run_one_method' > /usr/lib/ruby/vendor_ruby/minitest.rb:326:in `block (2 levels) in run' > /usr/lib/ruby/vendor_ruby/minitest.rb:325:in `each' > /usr/lib/ruby/vendor_ruby/minitest.rb:325:in `block in run' > /usr/lib/ruby/vendor_ruby/minitest.rb:365:in `on_signal' > /usr/lib/ruby/vendor_ruby/minitest.rb:352:in `with_info_handler' > /usr/lib/ruby/vendor_ruby/minitest.rb:324:in `run' > /usr/lib/ruby/vendor_ruby/minitest.rb:164:in `block in __run' > /usr/lib/ruby/vendor_ruby/minitest.rb:164:in `map' > /usr/lib/ruby/vendor_ruby/minitest.rb:164:in `__run' > /usr/lib/ruby/vendor_ruby/minitest.rb:141:in `run' > /usr/lib/ruby/vendor_ruby/minitest.rb:68:in `block in autorun' > > 5) Skipped: > TestLogDevice#test_shifting_size > [/<>/test/mri_logger_test.rb:354]: > shifting age doesn't work because rotation doesn't work > > 6) Skipped: > TestLogDevice#test_shifting_age > [/<>/test/mri_logger_test.rb:442]: > shifting age doesn't work because rotation doesn't work > > 20 runs, 102 assertions, 0 failures, 3 errors, 3 skips > rake aborted! > Command failed with status (1): [ruby -w -I"test" > /usr/lib/ruby/gems/3.0.0/gems/rake-13.0.3/lib/rake/rake_test_loader.rb > "test/mri_logger_test.rb" -v] > > Tasks: TOP => default > (See full trace by running task with --trace) > ERROR: Test "ruby3.0" failed: The full build log is available at https://people.debian.org/~kanashiro/ruby3.0/round2/builds/3/ruby-mono-logger/ruby-mono-logger_1.1.0-3.1+rebuild1633387243_amd64.build.txt signature.asc Description: PGP signature --- End Message --- --- Begin Message --- Source: ruby-mono-logger Source-Version: 1.1.1-1 Done: Daniel Leidert We believe that the bug you reported is fixed in the latest version of ruby-mono-logger, 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 996...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Daniel Leidert (supplier of updated ruby-mono-logger 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: Thu, 25 Nov 2021 16:59:40 +0100 Source: ruby-mono-logger Architecture: source Version: 1.1.1-1 Distribution: unstable Urgency: medium Maintainer: Debian Ruby Team
Processed: update bts with the right meta info
Processing commands for cont...@bugs.debian.org:
> reassign 994783 src:gammapy
Bug #994783 {Done: Ole Streicher } [src:gammapy]
astropy-regions breaks gammapy autopkgtest: KeyError: '.'
Ignoring request to reassign bug #994783 to the same package
> fixed 994783 0.19-1
Bug #994783 {Done: Ole Streicher } [src:gammapy]
astropy-regions breaks gammapy autopkgtest: KeyError: '.'
Ignoring request to alter fixed versions of bug #994783 to the same values
previously set
> affects 994783 src:astropy-regions
Bug #994783 {Done: Ole Streicher } [src:gammapy]
astropy-regions breaks gammapy autopkgtest: KeyError: '.'
Added indication that 994783 affects src:astropy-regions
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
994783: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=994783
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#1000587: marked as done (python-fakeredis: (autopkgtest) needs update for python3.10: ModuleNotFoundError: No module named 'lupa._lupa')
Your message dated Thu, 25 Nov 2021 17:30:53 +0100
with message-id <479dc398-1f83-54ec-bd02-cf4c118ee...@debian.org>
and subject line Re: python-fakeredis: (autopkgtest) needs update for
python3.10: ModuleNotFoundError: No module named 'lupa._lupa'
has caused the Debian Bug report #1000587,
regarding python-fakeredis: (autopkgtest) needs update for python3.10:
ModuleNotFoundError: No module named 'lupa._lupa'
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.)
--
1000587: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1000587
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-fakeredis
Version: 1.6.1-1
Severity: serious
X-Debbugs-CC: debian...@lists.debian.org
Tags: sid bookworm
User: debian...@lists.debian.org
Usertags: needs-update
Control: affects -1 src:python3-defaults
Dear maintainer(s),
We are in the transition of adding python2.10 to the supported Python
versions [0]. With a recent upload of python3-defaults the autopkgtest
of python-fakeredis fails in testing when that autopkgtest is run with
the binary packages of python3-defaults from unstable. It passes when
run with only packages from testing. In tabular form:
passfail
python3-defaults from testing3.9.8-1
python-fakeredis from testing1.6.1-1
all others from testingfrom testing
I copied some of the output at the bottom of this report.
Currently this regression is blocking the migration of python3-defaults
to testing [1]. https://docs.python.org/3/whatsnew/3.10.html lists
what's new in Python2.10, it may help to identify what needs to be updated.
More information about this bug and the reason for filing it can be found on
https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation
Paul
[1] https://qa.debian.org/excuses.php?package=python3-defaults
https://ci.debian.net/data/autopkgtest/testing/amd64/p/python-fakeredis/16956477/log.gz
ERRORS
_ ERROR at teardown of test_failed_script_error[fake]
__
request = >
@pytest.fixture(
params=[
pytest.param('fake', marks=pytest.mark.fake),
pytest.param('real', marks=pytest.mark.real)
]
)
async def r(request):
if request.param == 'fake':
ret = await fakeredis.aioredis.create_redis_pool()
else:
if not request.getfixturevalue('is_redis_running'):
pytest.skip('Redis is not running')
ret = await aioredis.create_redis_pool('redis://localhost')
await ret.flushall()
yield ret
> await ret.flushall()
test/test_aioredis1.py:34: _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
self = >
async_op = False
def flushall(self, async_op=False):
"""
Remove all keys from all databases.
:param async_op: lets the entire dataset to be freed
asynchronously. \
Defaults to False
"""
if async_op:
fut = self.execute(b'FLUSHALL', b'ASYNC')
else:
fut = self.execute(b'FLUSHALL')
/usr/lib/python3/dist-packages/aioredis/commands/server.py:141: _ _ _ _
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
self = >
command = b'FLUSHALL', args = (), kwargs = {}
def execute(self, command, *args, **kwargs):
return self._pool_or_conn.execute(command, *args, **kwargs)
/usr/lib/python3/dist-packages/aioredis/commands/__init__.py:51: _ _ _ _
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
self = , command =
b'FLUSHALL'
args = (), kw = {}, conn = , address = 'fakeredis'
def execute(self, command, *args, **kw):
"""Executes redis command in a free connection and returns
future waiting for result.
Picks connection from free pool and send command through
that connection.
If no connection is found, returns coroutine waiting for
free connection to execute command.
"""
conn, address = self.get_connection(command, args)
if conn is not None:
fut = conn.execute(command, *args, **kw)
/usr/lib/python3/dist-packages/aioredis/pool.py:196: _ _ _ _ _ _ _ _ _ _
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
self = , command = b'FLUSHALL', encoding = None
args = (), is_pubsub = False
def execute(self, command, *args, encoding=_NOTSET):
"""Executes redis command and returns Future
Bug#1000197: marked as done (assimp: binary-any FTBFS)
Your message dated Thu, 25 Nov 2021 16:18:33 +
with message-id
and subject line Bug#1000197: fixed in assimp 5.1.1~ds0-1
has caused the Debian Bug report #1000197,
regarding assimp: binary-any FTBFS
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.)
--
1000197: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1000197
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: assimp
Version: 5.0.1~ds0-4
Severity: serious
Tags: ftbfs
https://buildd.debian.org/status/logs.php?pkg=assimp=5.0.1~ds0-4
...
dh clean --buildsystem=cmake
dh_auto_clean -O--buildsystem=cmake
debian/rules execute_after_dh_auto_clean-arch
make[1]: Entering directory '/<>'
rm -rf doc/tmp/
make[1]: Leaving directory '/<>'
debian/rules execute_after_dh_auto_clean-indep
make[1]: Entering directory '/<>'
dh_auto_clean --indep --buildsystem=pybuild -- \
-d port/PyAssimp/
dh_auto_clean: error: unable to load build system class 'pybuild': Can't locate
Debian/Debhelper/Buildsystem/pybuild.pm in @INC (you may need to install the
Debian::Debhelper::Buildsystem::pybuild module) (@INC contains: /etc/perl
/usr/local/lib/x86_64-linux-gnu/perl/5.32.1 /usr/local/share/perl/5.32.1
/usr/lib/x86_64-linux-gnu/perl5/5.32 /usr/share/perl5
/usr/lib/x86_64-linux-gnu/perl-base /usr/lib/x86_64-linux-gnu/perl/5.32
/usr/share/perl/5.32 /usr/local/lib/site_perl) at (eval 6) line 1.
BEGIN failed--compilation aborted at (eval 6) line 1.
make[1]: *** [debian/rules:73: execute_after_dh_auto_clean-indep] Error 25
--- End Message ---
--- Begin Message ---
Source: assimp
Source-Version: 5.1.1~ds0-1
Done: IOhannes m zmölnig (Debian/GNU)
We believe that the bug you reported is fixed in the latest version of
assimp, 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 1000...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
IOhannes m zmölnig (Debian/GNU) (supplier of updated
assimp 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: Thu, 25 Nov 2021 15:32:47 +0100
Source: assimp
Architecture: source
Version: 5.1.1~ds0-1
Distribution: unstable
Urgency: medium
Maintainer: IOhannes m zmölnig (Debian/GNU)
Changed-By: IOhannes m zmölnig (Debian/GNU)
Closes: 973361 1000197
Changes:
assimp (5.1.1~ds0-1) unstable; urgency=medium
.
* New upstream version 5.1.1~ds0
(Closes: #1000197, #973361)
+ Refresh d/copyright
- Update copyrights
- New exclude location for stb
- Regenerate d/copyright_hints
+ Refresh patches, dropping those applied upstream
* Patch to disable crashy X3DImporter
* Patch to enable HTML documentation
* Build with libdraco support
* Have libassimp-dev depend on lib{draco,minizip}-dev
* Update configure flags
* Drop duplicate CMAKE_INSTALL_PREFIX flag
* Update version-script
* Drop no-longer-needed execute_after_dh_auto_install-arch
* debian/tests
+ add flag to disable traceback
Checksums-Sha1:
585ae11ff17bc7d7e560a97684967928d90d1cbb 2554 assimp_5.1.1~ds0-1.dsc
33a0cce87e860208c2bdd90ea998a3615ca02164 22883832 assimp_5.1.1~ds0.orig.tar.xz
af8c2a078f846dbfa26f617000d22d187e151907 32720 assimp_5.1.1~ds0-1.debian.tar.xz
Checksums-Sha256:
5453cd0318fba0464ee465cdfba668aa51484fe7044bc383f1388b200a3de696 2554
assimp_5.1.1~ds0-1.dsc
2308031b5109e717a2edbbe7292cd8e76222bb57db5a4284e552cd9d86cdb1e5 22883832
assimp_5.1.1~ds0.orig.tar.xz
9c0d2928a501da55ea20633e2112867c79f4d461bad6f87ba5c12a53765ce017 32720
assimp_5.1.1~ds0-1.debian.tar.xz
Files:
f0a122a5cbe20587def8d70b8d822d50 2554 graphics optional assimp_5.1.1~ds0-1.dsc
a985567c7a7a1e41060dd5c979489e3f 22883832 graphics optional
assimp_5.1.1~ds0.orig.tar.xz
46d1f64ac930954b484afb3ed221c22c 32720 graphics optional
assimp_5.1.1~ds0-1.debian.tar.xz
-BEGIN PGP SIGNATURE-
iQIzBAEBCAAdFiEEdAXnRVdICXNIABVttlAZxH96NvgFAmGfsx0ACgkQtlAZxH96
NvhethAAg6AMbtxtYzCDzSLtgbuLK2wlhvhCouH30J8AHtzQot21pRPo9AOywcz5
+EO1BSIY9QTJuFrloe8odQemZR/aiK6waW4UwHIiNZxYOBzbJiOyCfqLrmi1k0Dd
PSe1zWEbdEQJoeYJjSMZ6TkaQfaUlRrm6MaGDEkY0CE9BnHn21zPMHxdoYJ44d+K
Mznr7OsXLbu+CbjAcGQ2oODq5z4e08zVdw2EFdSNe5BEptYx1EYoZUnga533y3Q3
Processed: reassign 1000289 to mbedtls, severity of 1000289 is serious
Processing commands for cont...@bugs.debian.org: > reassign 1000289 mbedtls 2.16.11-0.1 Bug #1000289 [src:shadowsocks-libev] tests failing when mbedtls is compiled with CMAC support Bug reassigned from package 'src:shadowsocks-libev' to 'mbedtls'. No longer marked as found in versions shadowsocks-libev/3.3.5+ds-6. Ignoring request to alter fixed versions of bug #1000289 to the same values previously set Bug #1000289 [mbedtls] tests failing when mbedtls is compiled with CMAC support There is no source info for the package 'mbedtls' at version '2.16.11-0.1' with architecture '' Unable to make a source version for version '2.16.11-0.1' Marked as found in versions 2.16.11-0.1. > severity 1000289 serious Bug #1000289 [mbedtls] tests failing when mbedtls is compiled with CMAC support Severity set to 'serious' from 'normal' > thanks Stopping processing here. Please contact me if you need assistance. -- 1000289: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1000289 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1000292: Why was libpython3.10-dev not available in the test build?
On 25/11/2021 07.52, Graham Inggs wrote: I think you can simply change the build-depends on python3-dev to python3-all-dev. That fixes the build for me. Andreas
Processed: tagging 1000560, tagging 1000559, tagging 1000558, tagging 1000422, tagging 1000491, tagging 998706
Processing commands for cont...@bugs.debian.org:
> tags 1000560 + sid bookworm
Bug #1000560 [php-laravel-framework] Compatibility with Symfony 5
Added tag(s) sid and bookworm.
> tags 1000559 + sid bookworm
Bug #1000559 [php-robmorgan-phinx] Compatibility with Symfony 5
Added tag(s) bookworm and sid.
> tags 1000558 + sid bookworm
Bug #1000558 [php-cboden-ratchet] Compatibility with Symfony 5
Added tag(s) bookworm and sid.
> tags 1000422 + sid bookworm experimental
Bug #1000422 [src:pandas] pandas: FTBFS with Python 3.10 - Test failures
Added tag(s) bookworm, experimental, and sid.
> tags 1000491 + sid bookworm
Bug #1000491 [src:frama-c] FTBFS with Why3 1.4.0
Added tag(s) bookworm and sid.
> tags 998706 + experimental
Bug #998706 {Done: Julien Cristau } [mercurial] git breaks
mercurial autopkgtest: Failed test-convert-git.t: output changed
Added tag(s) experimental.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
1000422: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1000422
1000491: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1000491
1000558: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1000558
1000559: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1000559
1000560: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1000560
998706: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=998706
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#1000230: screenruler fails to start
Dear Peter, please can you check whether installing the package libcanberra-gtk3-module solves your issue? If so, this package is probably missing as a dependency for screenruler, and I can easily fix this bug. Best regards, Georges. Peter Mueller a écrit : > Package: screenruler > Version: 0.960+bzr41+deb10-4 > I use Gnome on Wayland. Reproduce: > 1) Open uxterm, bash being my shell. > 2) Type in > screenruler > and press [Enter]. > 3) Observe: > $ screenruler Loading libraries... Gtk-Message: 00:03:09.619: Failed to load > module "canberra-gtk-module" /usr/bin/screenruler:61:in `block in ': > 'Gdk::Pixbuf' has been deprecated. Use 'GdkPixbuf::Pixbuf'. > /usr/lib/ruby/vendor_ruby/gdk_pixbuf2/deprecated.rb:48:in `new': > GdkPixbuf::Pixbuf.new(path) is deprecated. Use GdkPixbuf::Pixbuf.new(:file => > path) instead. /usr/lib/ruby/vendor_ruby/gdk_pixbuf2/deprecated.rb:48:in > `new': GdkPixbuf::Pixbuf.new(path) is deprecated. Use > GdkPixbuf::Pixbuf.new(:file => path) instead. > /usr/lib/ruby/vendor_ruby/gdk_pixbuf2/deprecated.rb:48:in `new': > GdkPixbuf::Pixbuf.new(path) is deprecated. Use GdkPixbuf::Pixbuf.new(:file => > path) instead. Creating windows... Gtk-WARNING **: Unknown property: > GtkWindow.has-resize-grip from > /usr/share/screenruler/utils/glade_window.rb:29:in `initialize' from > /usr/share/screenruler/ruler_window.rb:51:in `initialize' from > /usr/bin/screenruler:76:in `new' from /usr/bin/screenruler:76:in `' > Reading settings... Presenting ruler... Shutting down... > $ sudo aptitude show gnome|grep Version Version: 1:3.38+3 > I would be happy if I could kindly ask that my bug report finds attention. -- Georges KHAZNADAR et Jocelyne FOURNIER 22 rue des mouettes, 59240 Dunkerque France. Téléphone +33 (0)3 28 29 17 70 signature.asc Description: PGP signature
Processed: Bug#996323 marked as pending in ruby-mono-logger
Processing control commands: > tag -1 pending Bug #996323 [src:ruby-mono-logger] ruby-mono-logger: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed: ArgumentError: wrong number of arguments (given 2, expected 0..1) Added tag(s) pending. -- 996323: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=996323 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#996323: marked as pending in ruby-mono-logger
Control: tag -1 pending Hello, Bug #996323 in ruby-mono-logger 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/ruby-team/ruby-mono-logger/-/commit/4bfe8ac410a0e8532e14e252c388d06a9260a152 ruby-mono-logger (1.1.1-1) UNRELEASED * Team upload. * New upstream release. - Fixes compatibility with Ruby 3.0 (closes: #996323). (this message was generated automatically) -- Greetings https://bugs.debian.org/996323
Processed: bug 996324 is forwarded to https://lists.debian.org/debian-gis/2021/10/msg00003.html
Processing commands for cont...@bugs.debian.org: > forwarded 996324 https://lists.debian.org/debian-gis/2021/10/msg3.html Bug #996324 [src:ruby-netcdf] ruby-netcdf: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed: Segmentation fault at 0x0034 Set Bug forwarded-to-address to 'https://lists.debian.org/debian-gis/2021/10/msg3.html'. > thanks Stopping processing here. Please contact me if you need assistance. -- 996324: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=996324 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1000576: closing 1000576
What about the evdev one? Il gio 25 nov 2021, 14:56 Timo Aaltonen ha scritto: > close 1000576 > thanks > > Not going to happen, synaptics is unmaintained and dropped for a reason. > You can still > have both installed and configure X to use synaptics instead after > installing it. >
Bug#996345: marked as done (ruby-packable: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed: ArgumentError: tried to create Proc object without a block)
Your message dated Thu, 25 Nov 2021 15:23:21 +
with message-id
and subject line Bug#996345: fixed in ruby-packable 1.3.14-2
has caused the Debian Bug report #996345,
regarding ruby-packable: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed:
ArgumentError: tried to create Proc object without a block
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.)
--
996345: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=996345
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ruby-packable
Version: 1.3.14-1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: debian-r...@lists.debian.org
Usertags: ruby3.0
Hi,
We are about to enable building against ruby3.0 on unstable. During a test
rebuild, ruby-packable was found to fail to build in that situation.
To reproduce this locally, you need to install ruby-all-dev from experimental
on an unstable system or build chroot.
Relevant part (hopefully):
> ArgumentError: tried to create Proc object without a block
>
> /<>/debian/ruby-packable/usr/share/rubygems-integration/all/gems/packable-1.3.14/lib/packable/extensions/io.rb:76:in
> `initialize'
>
> /<>/debian/ruby-packable/usr/share/rubygems-integration/all/gems/packable-1.3.14/lib/packable/extensions/io.rb:76:in
> `new'
>
> /<>/debian/ruby-packable/usr/share/rubygems-integration/all/gems/packable-1.3.14/lib/packable/extensions/io.rb:76:in
> `each_with_packing'
> /<>/test/packing_doc_test.rb:22:in `test_doc'
> /usr/lib/ruby/vendor_ruby/minitest/test.rb:98:in `block (3 levels) in run'
> /usr/lib/ruby/vendor_ruby/minitest/test.rb:195:in `capture_exceptions'
> /usr/lib/ruby/vendor_ruby/minitest/test.rb:95:in `block (2 levels) in run'
> /usr/lib/ruby/vendor_ruby/minitest.rb:270:in `time_it'
> /usr/lib/ruby/vendor_ruby/minitest/test.rb:94:in `block in run'
> /usr/lib/ruby/vendor_ruby/minitest.rb:365:in `on_signal'
> /usr/lib/ruby/vendor_ruby/minitest/test.rb:211:in `with_info_handler'
> /usr/lib/ruby/vendor_ruby/minitest/test.rb:93:in `run'
> /usr/lib/ruby/vendor_ruby/minitest.rb:1029:in `run_one_method'
> /usr/lib/ruby/vendor_ruby/minitest.rb:339:in `run_one_method'
> /usr/lib/ruby/vendor_ruby/minitest.rb:326:in `block (2 levels) in run'
> /usr/lib/ruby/vendor_ruby/minitest.rb:325:in `each'
> /usr/lib/ruby/vendor_ruby/minitest.rb:325:in `block in run'
> /usr/lib/ruby/vendor_ruby/minitest.rb:365:in `on_signal'
> /usr/lib/ruby/vendor_ruby/minitest.rb:352:in `with_info_handler'
> /usr/lib/ruby/vendor_ruby/minitest.rb:324:in `run'
> /usr/lib/ruby/vendor_ruby/minitest.rb:164:in `block in __run'
> /usr/lib/ruby/vendor_ruby/minitest.rb:164:in `map'
> /usr/lib/ruby/vendor_ruby/minitest.rb:164:in `__run'
> /usr/lib/ruby/vendor_ruby/minitest.rb:141:in `run'
> /usr/lib/ruby/vendor_ruby/minitest.rb:68:in `block in autorun'
>
> 17 runs, 46 assertions, 0 failures, 1 errors, 0 skips
> ERROR: Test "ruby3.0" failed:
The full build log is available at
https://people.debian.org/~kanashiro/ruby3.0/round2/builds/3/ruby-packable/ruby-packable_1.3.14-1+rebuild1633390366_amd64.build.txt
signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Source: ruby-packable
Source-Version: 1.3.14-2
Done: Daniel Leidert
We believe that the bug you reported is fixed in the latest version of
ruby-packable, 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 996...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Daniel Leidert (supplier of updated ruby-packable 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: Thu, 25 Nov 2021 16:00:08 +0100
Source: ruby-packable
Architecture: source
Version: 1.3.14-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Ruby Team
Changed-By: Daniel Leidert
Closes: 996345
Changes:
ruby-packable (1.3.14-2) unstable; urgency=medium
.
* Team upload.
* d/control (Build-Depends): Bump debhelper to version 13.
(Standards-Version): Bump to 4.6.0.
(Depends): Use ${ruby:Depends}.
* d/copyright (Copyright): Update.
* d/ruby-test-files.yaml:
Processed: owner 1000578
Processing commands for cont...@bugs.debian.org: > owner 1000578 tmanc...@debian.org Bug #1000578 [src:liblogfile-rotate-perl] liblogfile-rotate-perl: autopkgtest failure: Can't locate logfile.pm in @INC Owner recorded as tmanc...@debian.org. > thanks Stopping processing here. Please contact me if you need assistance. -- 1000578: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1000578 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#996345: marked as pending in ruby-packable
Control: tag -1 pending Hello, Bug #996345 in ruby-packable 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/ruby-team/ruby-packable/-/commit/da340b430a052d3313303df76de70ee207505b4a Add patch to fix ArgumentError * d/patches/fix-ruby-3.0-argumenterror.patch: Add patch. - Fix for trying to create a Proc object without a block (closes: #996345). * d/patches/series: Add new patch. (this message was generated automatically) -- Greetings https://bugs.debian.org/996345
Processed: Bug#996345 marked as pending in ruby-packable
Processing control commands: > tag -1 pending Bug #996345 [src:ruby-packable] ruby-packable: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed: ArgumentError: tried to create Proc object without a block Added tag(s) pending. -- 996345: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=996345 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#978875: marked as done (ocaml: ftbfs with autoconf 2.70)
Your message dated Thu, 25 Nov 2021 15:05:06 + with message-id and subject line Bug#978875: fixed in ocaml 4.11.1-5 has caused the Debian Bug report #978875, regarding ocaml: ftbfs with autoconf 2.70 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.) -- 978875: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=978875 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:ocaml Version: 4.08.1-10 Severity: normal Tags: sid bookworm User: d...@debian.org Usertags: ftbfs-ac270 [This bug report is not targeted to the upcoming bullseye release] The package fails to build in a test rebuild on at least amd64 with autoconf 2.70, but succeeds to build with autoconf 2.69. The severity of this report will be raised before the bookworm release, so nothing has to be done for the bullseye release. The full build log can be found at: http://qa-logs.debian.net/2020/09/26.ac270/ocaml_4.08.1-10_unstable_ac270.log The last lines of the build log are at the end of this report. To build with autoconf 2.70, please install the autoconf package from experimental: apt-get -t=experimental install autoconf [...] SCHROOT_ALIAS_NAME=unstable SCHROOT_CHROOT_NAME=sid-amd64-sbuild SCHROOT_COMMAND=env SCHROOT_GID=1001 SCHROOT_GROUP=user42 SCHROOT_SESSION_ID=sid-amd64-sbuild-8b8d0097-0e9c-4202-831e-bd0bc30e720c SCHROOT_UID=1001 SCHROOT_USER=user42 SHELL=/bin/sh USER=user42 dpkg-buildpackage - Command: dpkg-buildpackage -us -uc -sa -rfakeroot dpkg-buildpackage: info: source package ocaml dpkg-buildpackage: info: source version 4.08.1-10 dpkg-buildpackage: info: source distribution unstable dpkg-buildpackage: info: source changed by Stéphane Glondu dpkg-source --before-build . dpkg-buildpackage: info: host architecture amd64 debian/rules clean dh clean debian/rules override_dh_auto_clean make[1]: Entering directory '/<>' /usr/bin/make -f /<>/debian/ocamlinit.mk ocamlinit-clean make[2]: Entering directory '/<>' rm -f ocamlinit-stamp debian/ld.conf debian/ocaml-base-nox.postinst debian/ocaml-base-nox.prerm debian/ocaml-nox.lintian-overrides debian/ocaml-nox.manpages debian/ocaml-nox.postinst debian/ocaml-source.install make[2]: Leaving directory '/<>' if test -d boot.debian; then \ rm -Rf boot; \ mv boot.debian boot; \ fi set -e; for ext in sub guess; do \ if [ -f debian/config.orig.$ext ] ; then \ mv -f debian/config.orig.$ext config/gnu/config.$ext; \ fi; \ done rm -Rf debian/ocaml-source-4.08.1.tar debian/test-build make[1]: Leaving directory '/<>' dh_clean dpkg-source -b . dpkg-source: info: using source format '3.0 (quilt)' dpkg-source: info: building ocaml using existing ./ocaml_4.08.1.orig.tar.xz dpkg-source: info: using patch list from debian/patches/series dpkg-source: info: building ocaml in ocaml_4.08.1-10.debian.tar.xz dpkg-source: info: building ocaml in ocaml_4.08.1-10.dsc debian/rules binary dh binary debian/rules build make[1]: Entering directory '/<>' dh build dh_update_autotools_config debian/rules override_dh_autoreconf make[2]: Entering directory '/<>' ./autogen configure.ac:1518: warning: $as_echo is obsolete; use AS_ECHO(["message"]) instead lib/m4sugar/m4sh.m4:673: AS_IF is expanded from... ./lib/autoconf/general.m4:2149: AC_CACHE_VAL is expanded from... ./lib/autoconf/general.m4:2170: AC_CACHE_CHECK is expanded from... build-aux/ax_pthread.m4:88: AX_PTHREAD is expanded from... lib/m4sugar/m4sh.m4:581: AS_CASE is expanded from... lib/m4sugar/m4sh.m4:673: AS_IF is expanded from... configure.ac:1518: the top level make[2]: *** [debian/rules:303: override_dh_autoreconf] Error 1 make[2]: Leaving directory '/<>' make[1]: *** [debian/rules:82: build] Error 2 make[1]: Leaving directory '/<>' make: *** [debian/rules:77: binary] Error 2 dpkg-buildpackage: error: debian/rules binary subprocess returned exit status 2 --- End Message --- --- Begin Message --- Source: ocaml Source-Version: 4.11.1-5 Done: Stéphane Glondu We believe that the bug you reported is fixed in the latest version of ocaml, 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 978...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Stéphane Glondu (supplier of updated ocaml package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact
Bug#998108: firefox freezes shortly after start
After the upgrade to 94.0-2, I still experienced some crashes, but disabling hardware acceleration (about:preferences > General > Performance > uncheck both checkboxes and set processing limit to 8) fixed it for me.
Processed: Bug#978875 marked as pending in ocaml
Processing control commands: > tag -1 pending Bug #978875 [src:ocaml] ocaml: ftbfs with autoconf 2.70 Added tag(s) pending. -- 978875: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=978875 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#978875: marked as pending in ocaml
Control: tag -1 pending Hello, Bug #978875 in ocaml 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/ocaml-team/ocaml/-/commit/2f4a827125dcf79e2b6a193de69b018379bae836 Do not error on warnings in autoconf (Closes: #978875) (this message was generated automatically) -- Greetings https://bugs.debian.org/978875
Bug#996383: marked as done (ruby-semantic-puppet: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed: RuntimeError:)
Your message dated Thu, 25 Nov 2021 14:38:52 +
with message-id
and subject line Bug#996383: fixed in ruby-semantic-puppet 1.0.4-1
has caused the Debian Bug report #996383,
regarding ruby-semantic-puppet: FTBFS with ruby3.0: ERROR: Test "ruby3.0"
failed: RuntimeError:
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.)
--
996383: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=996383
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ruby-semantic-puppet
Version: 1.0.3-1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: debian-r...@lists.debian.org
Usertags: ruby3.0
Hi,
We are about to enable building against ruby3.0 on unstable. During a test
rebuild, ruby-semantic-puppet was found to fail to build in that situation.
To reproduce this locally, you need to install ruby-all-dev from experimental
on an unstable system or build chroot.
Relevant part (hopefully):
> RuntimeError:
> The `SortedSet` class has been extracted from the `set` library.You
> must use the `sorted_set` gem or other alternatives.
> # ./lib/semantic_puppet/dependency/graph_node.rb:39:in `block in
> dependencies'
> # ./lib/semantic_puppet/dependency/graph_node.rb:47:in `add_dependency'
> # ./spec/unit/semantic_puppet/dependency/graph_node_spec.rb:14:in
> `block in initialize'
> # ./spec/unit/semantic_puppet/dependency/graph_node_spec.rb:14:in `each'
> # ./spec/unit/semantic_puppet/dependency/graph_node_spec.rb:14:in
> `initialize'
> # ./spec/unit/semantic_puppet/dependency/graph_node_spec.rb:26:in `new'
> # ./spec/unit/semantic_puppet/dependency/graph_node_spec.rb:26:in
> `instance'
> # ./spec/unit/semantic_puppet/dependency/graph_node_spec.rb:54:in
> `block (3 levels) in '
> # ./spec/unit/semantic_puppet/dependency/graph_node_spec.rb:57:in
> `block (3 levels) in '
> # --
> # --- Caused by: ---
> # LoadError:
> # cannot load such file -- sorted_set
> # ./lib/semantic_puppet/dependency/graph_node.rb:39:in `block in
> dependencies'
>
> Finished in 1.03 seconds (files took 0.69167 seconds to load)
> 985 examples, 53 failures
[...]
> Randomized with seed 9711
>
> /usr/bin/ruby3.0
> -I/usr/share/rubygems-integration/all/gems/rspec-support-3.9.3/lib:/usr/share/rubygems-integration/all/gems/rspec-core-3.9.2/lib
> /usr/share/rubygems-integration/all/gems/rspec-core-3.9.2/exe/rspec
> --pattern ./spec/\*\*/\*_spec.rb --format documentation failed
> ERROR: Test "ruby3.0" failed:
Note that sorted_set has been removed from the standard library. It needs to be
packaged separately, and when that's done this package will need an explicit
dependency on it.
The full build log is available at
https://people.debian.org/~kanashiro/ruby3.0/round2/builds/3/ruby-semantic-puppet/ruby-semantic-puppet_1.0.3-1+rebuild1633395095_amd64.build.txt
signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Source: ruby-semantic-puppet
Source-Version: 1.0.4-1
Done: Daniel Leidert
We believe that the bug you reported is fixed in the latest version of
ruby-semantic-puppet, 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 996...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Daniel Leidert (supplier of updated ruby-semantic-puppet
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: Thu, 25 Nov 2021 14:58:09 +0100
Source: ruby-semantic-puppet
Architecture: source
Version: 1.0.4-1
Distribution: unstable
Urgency: medium
Maintainer: Puppet Package Maintainers
Changed-By: Daniel Leidert
Closes: 996383
Changes:
ruby-semantic-puppet (1.0.4-1) unstable; urgency=medium
.
* Team upload.
* New upstream release.
- Remove dependency on SortedSet (closes: #996383).
* d/control (Standards-Version): Bump to 4.6.0.
(Depends): Remove interpreters and use ${ruby:Depends}.
* d/copyright: Add Upstream-Contact field.
(Copyright): Add team.
* d/rules: Use gem installation layout and install upstream changelog.
* d/upstream/metadata: Update URLs.
Bug#999650: marked as done (ruby-oily-png FTBFS on 32bit)
Your message dated Thu, 25 Nov 2021 14:38:44 + with message-id and subject line Bug#999650: fixed in ruby-oily-png 1.2.1~dfsg-3 has caused the Debian Bug report #999650, regarding ruby-oily-png FTBFS on 32bit 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.) -- 999650: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=999650 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: ruby-oily-png Version: 1.2.1~dfsg-2 Severity: serious Tags: ftbfs https://buildd.debian.org/status/package.php?p=ruby-oily-png ... Failures: 1) OilyPNG::Color#compose_quick should use the background color as is when a fully transparent pixel is given as foreground color Failure/Error: expect(compose_quick(@fully_transparent, @white)).to be(@white) expected # => 4294967295 got # => 4294967295 Compared using equal?, which compares object identity, but expected and actual are not the same object. Use `expect(actual).to eq(expected)` if you don't care about object identity in this example. # ./spec/color_spec.rb:24:in `block (3 levels) in ' 2) OilyPNG::Color#compose_quick should compose pixels correctly Failure/Error: expect(compose_quick(@non_opaque, @white)).to be(0x9fc2d6ff) expected # => 2680346367 got # => 2680346367 Compared using equal?, which compares object identity, but expected and actual are not the same object. Use `expect(actual).to eq(expected)` if you don't care about object identity in this example. # ./spec/color_spec.rb:28:in `block (3 levels) in ' 3) OilyPNG::Color#compose_quick should compose colors exactly the same as ChunkyPNG Failure/Error: expect(compose_quick(fg, bg)).to be(ChunkyPNG::Color.compose_quick(fg, bg)) expected # => 2126858483 got # => 2126858483 Compared using equal?, which compares object identity, but expected and actual are not the same object. Use `expect(actual).to eq(expected)` if you don't care about object identity in this example. # ./spec/color_spec.rb:33:in `block (3 levels) in ' Finished in 0.36245 seconds (files took 0.22531 seconds to load) 146 examples, 3 failures, 18 pending Failed examples: rspec ./spec/color_spec.rb:23 # OilyPNG::Color#compose_quick should use the background color as is when a fully transparent pixel is given as foreground color rspec ./spec/color_spec.rb:27 # OilyPNG::Color#compose_quick should compose pixels correctly rspec ./spec/color_spec.rb:31 # OilyPNG::Color#compose_quick should compose colors exactly the same as ChunkyPNG /usr/bin/ruby2.7 -I/usr/share/rubygems-integration/all/gems/rspec-support-3.9.3/lib:/usr/share/rubygems-integration/all/gems/rspec-core-3.9.2/lib /usr/share/rubygems-integration/all/gems/rspec-core-3.9.2/exe/rspec --pattern ./spec/\*\*/\*_spec.rb --format documentation failed ERROR: Test "ruby2.7" failed. Exiting. dh_auto_install: error: dh_ruby --install /<>/ruby-oily-png-1.2.1\~dfsg/debian/ruby-oily-png returned exit code 1 make: *** [debian/rules:8: binary-arch] Error 25 --- End Message --- --- Begin Message --- Source: ruby-oily-png Source-Version: 1.2.1~dfsg-3 Done: Lucas Kanashiro We believe that the bug you reported is fixed in the latest version of ruby-oily-png, 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 999...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Lucas Kanashiro (supplier of updated ruby-oily-png 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: Thu, 25 Nov 2021 10:53:31 -0300 Source: ruby-oily-png Architecture: source Version: 1.2.1~dfsg-3 Distribution: unstable Urgency: medium Maintainer: Debian Ruby Team Changed-By: Lucas Kanashiro Closes: 999650 Changes: ruby-oily-png (1.2.1~dfsg-3) unstable; urgency=medium . * Team upload. * Add patch to fix tests failing on 32 bits architectures (Closes: #999650) Checksums-Sha1: 490f004ad592cf2431c93a60a68b153561b56a7d 2136 ruby-oily-png_1.2.1~dfsg-3.dsc c9197b7d2174f16d10efc61cbdd3beec90890294 6680 ruby-oily-png_1.2.1~dfsg-3.debian.tar.xz
Bug#997308: marked as done (python-flask-jwt-extended: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p 3.9 returned exit code 13)
Your message dated Thu, 25 Nov 2021 14:37:27 +
with message-id
and subject line Bug#997308: fixed in python-flask-jwt-extended 4.3.1-1
has caused the Debian Bug report #997308,
regarding python-flask-jwt-extended: FTBFS: dh_auto_test: error: pybuild --test
--test-pytest -i python{version} -p 3.9 returned exit code 13
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
997308: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997308
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-flask-jwt-extended
Version: 3.24.1-2
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> === short test summary info
>
> FAILED tests/test_asymmetric_crypto.py::test_asymmetric_cropto -
> AttributeErr...
> FAILED
> tests/test_blacklist.py::test_non_blacklisted_access_token[blacklist_type0]
> FAILED
> tests/test_blacklist.py::test_non_blacklisted_access_token[blacklist_type1]
> FAILED tests/test_blacklist.py::test_blacklisted_access_token[blacklist_type0]
> FAILED tests/test_blacklist.py::test_blacklisted_access_token[blacklist_type1]
> FAILED
> tests/test_blacklist.py::test_non_blacklisted_refresh_token[blacklist_type0]
> FAILED
> tests/test_blacklist.py::test_non_blacklisted_refresh_token[blacklist_type1]
> FAILED
> tests/test_blacklist.py::test_blacklisted_refresh_token[blacklist_type0]
> FAILED
> tests/test_blacklist.py::test_blacklisted_refresh_token[blacklist_type1]
> FAILED tests/test_blacklist.py::test_no_blacklist_callback_method_provided -
> ...
> FAILED tests/test_blacklist.py::test_revoked_token_of_different_type -
> Attrib...
> FAILED tests/test_blacklist.py::test_custom_blacklisted_message -
> AttributeEr...
> FAILED
> tests/test_claims_verification.py::test_successful_claims_validation[/protected1]
> FAILED
> tests/test_claims_verification.py::test_successful_claims_validation[/protected2]
> FAILED
> tests/test_claims_verification.py::test_successful_claims_validation[/protected3]
> FAILED
> tests/test_claims_verification.py::test_unsuccessful_claims_validation[/protected1]
> FAILED
> tests/test_claims_verification.py::test_unsuccessful_claims_validation[/protected2]
> FAILED
> tests/test_claims_verification.py::test_unsuccessful_claims_validation[/protected3]
> FAILED
> tests/test_claims_verification.py::test_claims_validation_custom_error[/protected1]
> FAILED
> tests/test_claims_verification.py::test_claims_validation_custom_error[/protected2]
> FAILED
> tests/test_claims_verification.py::test_claims_validation_custom_error[/protected3]
> FAILED
> tests/test_claims_verification.py::test_get_jwt_identity_in_verification_method[/protected1]
> FAILED
> tests/test_claims_verification.py::test_get_jwt_identity_in_verification_method[/protected2]
> FAILED
> tests/test_claims_verification.py::test_get_jwt_identity_in_verification_method[/protected3]
> FAILED tests/test_cookies.py::test_jwt_refresh_required_with_cookies[options0]
> FAILED tests/test_cookies.py::test_jwt_refresh_required_with_cookies[options1]
> FAILED tests/test_cookies.py::test_default_access_csrf_protection[options0]
> FAILED tests/test_cookies.py::test_default_access_csrf_protection[options1]
> FAILED tests/test_cookies.py::test_non_matching_csrf_token[options0] -
> assert...
> FAILED tests/test_cookies.py::test_non_matching_csrf_token[options1] -
> assert...
> FAILED tests/test_cookies.py::test_csrf_disabled[options0] - assert 401 == 200
> FAILED tests/test_cookies.py::test_csrf_disabled[options1] - assert 401 == 200
> FAILED tests/test_cookies.py::test_csrf_with_custom_header_names[options0] -
> ...
> FAILED tests/test_cookies.py::test_csrf_with_custom_header_names[options1] -
> ...
> FAILED tests/test_cookies.py::test_csrf_with_default_form_field[options0] -
> T...
> FAILED tests/test_cookies.py::test_csrf_with_default_form_field[options1] -
> T...
> FAILED tests/test_cookies.py::test_csrf_with_custom_form_field[options0] -
> Ty...
> FAILED tests/test_cookies.py::test_csrf_with_custom_form_field[options1] -
> Ty...
> FAILED tests/test_cookies.py::test_custom_csrf_methods[options0] -
> TypeError:...
> FAILED tests/test_cookies.py::test_custom_csrf_methods[options1] -
> TypeError:...
> FAILED tests/test_cookies.py::test_default_cookie_options - assert 0 == 2
> FAILED tests/test_cookies.py::test_custom_cookie_options - assert 0 == 2
> FAILED tests/test_cookies.py::test_custom_cookie_names_and_paths -
Processed: bug 1000589 is forwarded to https://github.com/Segfault-Inc/Multicorn/issues/271
Processing commands for cont...@bugs.debian.org: > forwarded 1000589 https://github.com/Segfault-Inc/Multicorn/issues/271 Bug #1000589 [src:postgresql-multicorn] Incompatible with PostgreSQL 14 Set Bug forwarded-to-address to 'https://github.com/Segfault-Inc/Multicorn/issues/271'. > thanks Stopping processing here. Please contact me if you need assistance. -- 1000589: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1000589 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1000589: Incompatible with PostgreSQL 14
Source: postgresql-multicorn Version: 1.4.0-4 Severity: serious Multicorn is incompatible with PostgreSQL 14 and needs non-trivial porting while upstream work has stalled for the past two years. https://github.com/Segfault-Inc/Multicorn/issues/271 In the meantime, it should be removed from testing. Christoph
Processed: bug 996345 is forwarded to https://github.com/marcandre/packable/issues/15
Processing commands for cont...@bugs.debian.org: > forwarded 996345 https://github.com/marcandre/packable/issues/15 Bug #996345 [src:ruby-packable] ruby-packable: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed: ArgumentError: tried to create Proc object without a block Set Bug forwarded-to-address to 'https://github.com/marcandre/packable/issues/15'. > thanks Stopping processing here. Please contact me if you need assistance. -- 996345: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=996345 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: closing 1000576
Processing commands for cont...@bugs.debian.org: > close 1000576 Bug #1000576 [xserver-xorg-input-all] xserver-xorg-input-all: Please include other input drivers in dependencies Marked Bug as done > thanks Stopping processing here. Please contact me if you need assistance. -- 1000576: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1000576 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1000576: closing 1000576
close 1000576 thanks Not going to happen, synaptics is unmaintained and dropped for a reason. You can still have both installed and configure X to use synaptics instead after installing it.
Bug#996300: marked as done (ruby-jaeger-client: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed: ArgumentError:)
Your message dated Thu, 25 Nov 2021 13:49:15 + with message-id and subject line Bug#996300: fixed in ruby-jaeger-client 1.2.0-1 has caused the Debian Bug report #996300, regarding ruby-jaeger-client: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed: ArgumentError: 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.) -- 996300: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=996300 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: ruby-jaeger-client Version: 1.1.0-2 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: debian-r...@lists.debian.org Usertags: ruby3.0 Hi, We are about to enable building against ruby3.0 on unstable. During a test rebuild, ruby-jaeger-client was found to fail to build in that situation. To reproduce this locally, you need to install ruby-all-dev from experimental on an unstable system or build chroot. Relevant part (hopefully): > ArgumentError: > wrong number of arguments (given 1, expected 0; required keywords: > span_id, trace_id, flags) > # ./lib/jaeger/span_context.rb:25:in `initialize' > # ./spec/spec_helper.rb:16:in `new' > # ./spec/spec_helper.rb:16:in `build_span_context' > # ./spec/jaeger/span_spec.rb:50:in `block (3 levels) in (required)>' > # ./spec/jaeger/span_spec.rb:51:in `block (3 levels) in (required)>' > # ./spec/jaeger/span_spec.rb:61:in `block (4 levels) in (required)>' > > Finished in 0.37196 seconds (files took 1.6 seconds to load) > 177 examples, 42 failures > > Failed examples: > > rspec ./spec/jaeger/injectors/b3_rack_codec_spec.rb:9 # > Jaeger::Injectors::B3RackCodec sets trace information > rspec ./spec/jaeger/injectors/trace_context_rack_codec_spec.rb:14 # > Jaeger::Injectors::TraceContextRackCodec sets traceparent > rspec ./spec/jaeger/injectors/trace_context_rack_codec_spec.rb:27 # > Jaeger::Injectors::TraceContextRackCodec sets traceparent with largest trace > id and span id > rspec ./spec/jaeger/rate_limiter_spec.rb:11 # > Jaeger::RateLimiter#check_credit returns false if item cost is higher than > balance > rspec ./spec/jaeger/rate_limiter_spec.rb:16 # > Jaeger::RateLimiter#check_credit returns true until there is credit left > rspec ./spec/jaeger/rate_limiter_spec.rb:23 # > Jaeger::RateLimiter#check_credit returns true when there is enough credit > rspec ./spec/jaeger/rate_limiter_spec.rb:51 # Jaeger::RateLimiter#update when > balance was full before the update keeps the new balance full > rspec ./spec/jaeger/rate_limiter_spec.rb:61 # Jaeger::RateLimiter#update when > balance was half full before the update marks the new balance half full > rspec ./spec/jaeger/reporters/composite_reporter_spec.rb:9 # > Jaeger::Reporters::CompositeReporter#report forwards span to all reporters > rspec ./spec/jaeger/reporters/in_memory_reporter_spec.rb:7 # > Jaeger::Reporters::InMemoryReporter#report adds span to in memory spans list > rspec ./spec/jaeger/reporters/in_memory_reporter_spec.rb:19 # > Jaeger::Reporters::InMemoryReporter#clear clears spans from the reporter > rspec ./spec/jaeger/reporters/logging_reporter_spec.rb:8 # > Jaeger::Reporters::LoggingReporter#report logs out span information > rspec ./spec/jaeger/samplers/guaranteed_throughput_probabilistic_spec.rb:31 # > Jaeger::Samplers::GuaranteedThroughputProbabilistic when rate is set to 0 > when lower bound return false returns false for every trace > rspec ./spec/jaeger/samplers/guaranteed_throughput_probabilistic_spec.rb:35 # > Jaeger::Samplers::GuaranteedThroughputProbabilistic when rate is set to 0 > when lower bound return false returns tags with param 0 > rspec ./spec/jaeger/samplers/guaranteed_throughput_probabilistic_spec.rb:49 # > Jaeger::Samplers::GuaranteedThroughputProbabilistic when rate is set to 0 > when lower bound sampler returns true returns true > rspec ./spec/jaeger/samplers/guaranteed_throughput_probabilistic_spec.rb:53 # > Jaeger::Samplers::GuaranteedThroughputProbabilistic when rate is set to 0 > when lower bound sampler returns true returns tags with lower bound param > rspec ./spec/jaeger/samplers/guaranteed_throughput_probabilistic_spec.rb:70 # > Jaeger::Samplers::GuaranteedThroughputProbabilistic when rate is set to 1 > returns true for every trace > rspec ./spec/jaeger/samplers/guaranteed_throughput_probabilistic_spec.rb:74 # > Jaeger::Samplers::GuaranteedThroughputProbabilistic when rate is set to 1 > returns tags with param 1 > rspec ./spec/jaeger/samplers/guaranteed_throughput_probabilistic_spec.rb:81 # >
Bug#1000465: libodbc1: Missing dependency and dangling symlink
Hi On 2021-11-25 13:22:12, Guillem Jover wrote: > On Thu, 2021-11-25 at 12:26:29 +0100, [EXT] Vincent Lefevre wrote: > > [Cc Sebastian Ramacher] > > > > On 2021-11-25 21:42:48 +1100, Hugh McMaster wrote: > > > On Thu, 25 Nov 2021 at 03:39, Vincent Lefevre wrote: > > > > > > > > On 2021-11-24 16:31:08 +0100, Guillem Jover wrote: > > > > > The symlinks must be kept for backwards compat. Please see #998169 for > > > > > the context of this packaging cleanup. > > > > > > > > OK, thanks. #998169 gives the explanation. > > > > > > > > Note that I was also wondering whether these symblinks are still > > > > actually used. For instance, libgdal29 3.3.3+dfsg-2 depends on > > > > libodbc1 (>= 2.3.1), but > > > > > > > > $ ldd /usr/lib/libgdal.so.29 | grep libodbc > > > > libodbc.so.2 => /usr/lib/x86_64-linux-gnu/libodbc.so.2 > > > > (0x7fb732d54000) > > > > libodbcinst.so.2 => /usr/lib/x86_64-linux-gnu/libodbcinst.so.2 > > > > (0x7fb732d3c000) > > > > > > > > So the .so.2 names are already used, and the symlinks are not needed > > > > for libgdal29. Now, what about the other packages? Since these .so.2 > > > > sonames were added in 2013 (8 years ago!), I suppose that the old > > > > .so.1 sonames are no longer used at all, so that no backward compat > > > > symlinks are needed. > > > > > > I've inspected a quarter of unixodbc's reverse dependencies so far and > > > found all were using soversion 2. > > > > > > As indicated in #998169, I had removed the symlinks but was advised to > > > reinstate them. > > > > If you mean Sebastian Ramacher's message > > > > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=998169#39 > > > > saying "libodbc1 and odbcinst1debian2 could then be transitional > > packages with the compat symlinks that stay around at least for > > bookworm." I suppose that Sebastian did not know that the .so.2 > > sonames were already used for some time (I recall that the change > > in unixodbc was done in 2013). Was anything particular said on > > #debian-release? > > > > So I assume that only a transitional dummy package (without the > > symlinks) is needed. > > If we have to ship a transitional package anyway, I'm not sure why > is there this pushback about shipping a couple of symlinks with it? > The package will soon enough fade away. > > (I mean if that implied we can solve this with just versioned > Provides, I could understand but…) > > > > I highly doubt that any package is linking via hard-coding to the > > > old soname version. > > > > Well, I think that the only potential issue is for old packages that > > were built before the soname change in 2013 and were removed from > > Debian at that time (thus are no longer rebuilt). But in practice, > > compat symlinks are not kept that long, are they? > > Or old locally built packages, or old third-party packages. > > > Note that given the fact that libodbc1 depends on libltdl7 (>= 2.4.6), > > which appeared in 2016, such packages from 2013 or earlier should > > already be broken. > > This would still break the "contract" of the package that potential > reverse dependencies expect. I think there's a difference between say > program symlinks and library symlinks, as the latter are the entire > raison d'être of these package anyway. More so, when as per above, we > need to ship the package in any case. :) Indeed. These symlinks need to stay for satisfy the "contract" of libodbc1. In bullseye, this currently is: * libodbc.so.2 * libodbccr.so.2 * libodbc.so.1 * libodbccr.so.1 After upgrading to the bookworm version of libodbc1, the same SONAMEs need to be provided. If the plan is to go ahead with the package clean up, this means that libodbc1 needs to have a dependency on libodbc2 and libodcbccr2 and it also needs provides the compat symlinks for libodbc.so.1 and libodbccr.so.1. The same is also true for all the other library packages that are being clean up. What we can do after that was implemented, is to rebuild all packages in bookworm to gain dependencies on libodbc2 and libodbccr2. Once this was done and bookworm was released, one can think of dropping libodbc1 for trixie. Long story short: due to the non-transition in 2013, libodcb1 needs to satisfy its promise to provide both the .1 and .2 versions. Cheers -- Sebastian Ramacher
Processed: bug 999650 is forwarded to https://github.com/wvanbergen/oily_png/issues/24
Processing commands for cont...@bugs.debian.org: > forwarded 999650 https://github.com/wvanbergen/oily_png/issues/24 Bug #999650 [src:ruby-oily-png] ruby-oily-png FTBFS on 32bit Set Bug forwarded-to-address to 'https://github.com/wvanbergen/oily_png/issues/24'. > thanks Stopping processing here. Please contact me if you need assistance. -- 999650: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=999650 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
