Processed: RFS: splash/3.10.1-2 [ITA] -- Visualisation tool for Smoothed Particle Hydrodynamics simulation
Processing commands for cont...@bugs.debian.org: > close 1061666 Bug #1061666 [sponsorship-requests] RFS: splash/3.10.1-2 [ITA] -- Visualisation tool for Smoothed Particle Hydrodynamics simulation Marked Bug as done > stop Stopping processing here. Please contact me if you need assistance. -- 1061666: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1061666 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1061807: marked as done (lazygal fails its autopkg tests with Python 3.12)
Your message dated Wed, 31 Jan 2024 05:35:40 +
with message-id
and subject line Bug#1061807: fixed in lazygal 0.10.9-1
has caused the Debian Bug report #1061807,
regarding lazygal fails its autopkg tests with Python 3.12
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.)
--
1061807: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1061807
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:lazygal
Version: 0.10.8-1
Severity: important
Tags: sid trixie ftbfs
User: debian-pyt...@lists.debian.org
Usertags: python3.12
With python3-defaults from experimental, the package fails its autopkg
tests:
[...]
770s autopkgtest [13:43:41]: test smoke: ---]
770s smokeFAIL stderr:
/tmp/autopkgtest.MQIt8M/build.0vV/src/lazygal/sourcetree.py:110:
SyntaxWarning: invalid escape sequence '\D'
770s autopkgtest [13:43:41]: test smoke: - - - - - - - - - - results -
- - - - - - - - -
770s autopkgtest [13:43:41]: test smoke: - - - - - - - - - - stderr - -
- - - - - - - -
770s /tmp/autopkgtest.MQIt8M/build.0vV/src/lazygal/sourcetree.py:110:
SyntaxWarning: invalid escape sequence '\D'
770s numeric_part = re.sub("\D", "", self.filename)
770s /tmp/autopkgtest.MQIt8M/build.0vV/src/lazygal/mediautils.py:152:
SyntaxWarning: invalid escape sequence '\,'
770s self.videofilters.append('select=gt(scene\,0.4)')
771s autopkgtest [13:43:42]: summary
771s smokeFAIL stderr:
/tmp/autopkgtest.MQIt8M/build.0vV/src/lazygal/sourcetree.py:110:
SyntaxWarning: invalid escape sequence '\D'
--- End Message ---
--- Begin Message ---
Source: lazygal
Source-Version: 0.10.9-1
Done: Alexandre Rossi
We believe that the bug you reported is fixed in the latest version of
lazygal, 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 1061...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Alexandre Rossi (supplier of updated lazygal 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: Wed, 31 Jan 2024 05:59:04 +0100
Source: lazygal
Architecture: source
Version: 0.10.9-1
Distribution: unstable
Urgency: medium
Maintainer: Michal Čihař
Changed-By: Alexandre Rossi
Closes: 1061807
Changes:
lazygal (0.10.9-1) unstable; urgency=medium
.
* New upstream version 0.10.9 (Closes: #1061807)
Checksums-Sha1:
9354cc682318bc6eda20a24d6aeec8c1368d1d45 2116 lazygal_0.10.9-1.dsc
726bf4cc9df3fc7a34aa43379a98e07fcc0b8174 817938 lazygal_0.10.9.orig.tar.bz2
e994bab8b40cb200b9764f5d3a397e8e33fec8d3 5104 lazygal_0.10.9-1.debian.tar.xz
f388dc0c26b62014544e69390cb16e371a14c1bc 7455 lazygal_0.10.9-1_amd64.buildinfo
Checksums-Sha256:
5e82140130958acf47d12a79d3b59d56412afe7008a4eae5a838c6de81e4c4b5 2116
lazygal_0.10.9-1.dsc
219b81be748f8b920f3e70a5a52bebf18842f3c5df9ed56764bb4c2f117aa738 817938
lazygal_0.10.9.orig.tar.bz2
d7b77729db387d8551837416bb8c36cf044b4f1a4d8abd015206a8a6ed99e184 5104
lazygal_0.10.9-1.debian.tar.xz
45da5da223678e545021d1382adf7f704fe7e332fb5fd001f4bccb2f77961843 7455
lazygal_0.10.9-1_amd64.buildinfo
Files:
5ade7424b525a69ca11f28e92dd20aec 2116 graphics optional lazygal_0.10.9-1.dsc
80f5eb2925d8dcbc83037ee71b4bc361 817938 graphics optional
lazygal_0.10.9.orig.tar.bz2
c49140bd72acdfab1515fdb071c16a43 5104 graphics optional
lazygal_0.10.9-1.debian.tar.xz
0cf939409e63ec00a085d178dfc0649f 7455 graphics optional
lazygal_0.10.9-1_amd64.buildinfo
-BEGIN PGP SIGNATURE-
iQIzBAEBCgAdFiEEqURFrS/GV/h4cdpsWI+eupOKFo8FAmW51OEACgkQWI+eupOK
Fo8n/RAAyQay5wwZ4xUXruqHdt5nQSrziZsY1q453biumLxcoLkuDNXNu5iNuVbu
ZTdU93jVJHDdi5swNQ5DXDhWXsdaupL1qB+uqCqIPtkUvPDk1xcVRV8Ebz7rrFCv
TG7LwUs+/JBAYbtdvszWtCm3znPr1Q6FpfKt4Kbqj0+59tFG4i6anNZ9zBN+7ChB
c5UYkFn0KEi3DlXn27hzC+jG0PpIcfmeWcgQsthPaZrGQYnwnXR6vf96b4/nadtF
+4TzsHQImD84iTMppWkmNxotZEcOhnvNVj2bc2RfotZmxhJmoE3IiGB6Tc0c/Bop
ogIRjeRSUwHCQ/GZ4ssBbUYF6o8F7yI9bPJQAaAbIw8HLzRvWVUu2/dln4AjWi9E
jFxmEFODKbSyJuZWzLgop+HfofTHIlEZCu43r9AJaM+riyEABDVaAwRmF3m2jxwV
o+WTk6YEuSxD0aYyZQ+OnEr4C4OUoIP8WKTGijcdLuY6Bt7mLBx+BsHX45aw7GNO
9r76EiUZ04FkfSM8fyhunmnVU+4yV1MA9FSoCdUUKXnUqtrkLZpfms5a2ZS2R7EY
Bug#1018379: marked as done (ipywidgets: build-depends on python3-nose or uses it for autopkgtest)
Your message dated Tue, 30 Jan 2024 23:34:15 + with message-id and subject line Bug#1018379: fixed in ipywidgets 8.1.1-2 has caused the Debian Bug report #1018379, regarding ipywidgets: build-depends on python3-nose or uses it for autopkgtest 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.) -- 1018379: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1018379 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: ipywidgets Version: 6.0.0-9 User: python-modules-t...@lists.alioth.debian.org Usertags: nose-rm Dear Maintainer, Your package still uses nose [1], which is an obsolete testing framework for Python, dead and unmaintained since 2015 [2][3]. If you received this bug report, it means that your package either has a build-dependency on python3-nose or uses that package in debian/tests/control. If that is not the case, please reply and CC me explicitly. Please port your package to one of the alternatives: nose2 [4], pytest [5] or unittest from Python standard library [6]. There is a script called nose2pytest [7] which can assist with migrating from nose to pytest. This mass bug filing was discussed on debian-devel in [8]. [1]: https://tracker.debian.org/pkg/nose [2]: https://github.com/nose-devs/nose/commit/0f40fa995384afad [3]: https://pypi.org/project/nose/#history [4]: https://docs.nose2.io/en/latest/ [5]: https://docs.pytest.org/en/latest/ [6]: https://docs.python.org/3/library/unittest.html [7]: https://github.com/pytest-dev/nose2pytest [8]: https://lists.debian.org/debian-devel/2022/08/msg00184.html -- Dmitry Shachnev --- End Message --- --- Begin Message --- Source: ipywidgets Source-Version: 8.1.1-2 Done: Roland Mas We believe that the bug you reported is fixed in the latest version of ipywidgets, 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 1018...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Roland Mas (supplier of updated ipywidgets 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: Wed, 31 Jan 2024 00:06:41 +0100 Source: ipywidgets Architecture: source Version: 8.1.1-2 Distribution: unstable Urgency: medium Maintainer: Debian Python Team Changed-By: Roland Mas Closes: 1018379 Changes: ipywidgets (8.1.1-2) unstable; urgency=medium . * Upload to unstable. * Bug fix: "build-depends on python3-nose or uses it for autopkgtest", thanks to Dmitry Shachnev (Closes: #1018379). * Require recent python3-comm. Checksums-Sha1: 94c019c68ed8090aec5d65cb6cbd2be1804ec745 3400 ipywidgets_8.1.1-2.dsc 24cb67cff4651f94a8939c7683ae7cdcb6d1b7ff 141704 ipywidgets_8.1.1-2.debian.tar.xz f1b80fa034f8f0713a497d1e8c7ef828ab526870 38432 ipywidgets_8.1.1-2_amd64.buildinfo Checksums-Sha256: 93123f85fa9bb02b66b806efdbdf43aecc9d3e32a6f49f8a49f3ca0e45a09060 3400 ipywidgets_8.1.1-2.dsc be5daebf25063f62ce19cfb9d436ed20bbdeb7f7a4f3837f6be95c689134a11b 141704 ipywidgets_8.1.1-2.debian.tar.xz f68eb3cd57cbba4e943372a2907bae358e8e2a7bee60df27da49f10b4d1b70a2 38432 ipywidgets_8.1.1-2_amd64.buildinfo Files: bc57a8add19a1ba4acf8b8120e44871c 3400 python optional ipywidgets_8.1.1-2.dsc 29f32bb48a84a9678afb5e950ebc16d3 141704 python optional ipywidgets_8.1.1-2.debian.tar.xz 967bfd7fc97eb3d829a787952ea73e16 38432 python optional ipywidgets_8.1.1-2_amd64.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEtBU2D1kett1zr/uD0w3s0lmTIvwFAmW5ga4ACgkQ0w3s0lmT IvyxNQ/+Pb/rVOkS+YIMAvyhY12z0yjp2oBYU1P1Rb9OJEskn6oeyDMyR0aJwCFG VaI6e5Tzs2u3cYZGM2BALXpDvLTJPIr4tVhjZ9ybfWIAL4ckvuU9q8HT2KfjEx+t KIbDojvv07ucya6ry7zr3bHxnrtDsftKnrtrqjZ/tetGBFPTlAXj3vx8OAPgE1QM +9mmP3UXHbxWyZ6y/33Ks5P0Nx5dXp5qseTY8pSNIOFFRMidmDnMgKs0H0CTWt7s xMw58dOnxqCZ5A7jHC0r1iSoRvTtO3hguP9LHNYjInKBMhgklcyk398VH230do2V DjgNDv4B/JvIfIwo36DBPbPMRJVOlqXqNdG3E0IXgWBSo7jUJ06q0+gaXXmkDExr pCklWBNZpii9Ont6kXgc71lid6R+IfLquzZbVpHe32dUd9xp2nzqkE2zWeBIfbjh 0xJrLaKMeUUvtInul91YHcJz5w6M4etRSa6GGDImi4wGdB6Bw2z1vsNCs0VkEfho 0/ZCf29xFC0c8XwatzBmjr+VKI/yjyZLw4zWgqt9lQE32Ih/QLzXnTVzo2ldi/z6 E0SQSU24GcdWyAARGVBvKQhnyQHskMIDb9riXUyFKS8cbaA66CkRJcFJ85Sfqp32 H5VInz8MXr4iumkjTQdG+MGG68SNhmc7hTkWtaML2GxdedtHF+A= =a2W2 -END PGP
Bug#1054132: marked as done (podget: line 2532: ITEM_TITLE: unbound variable)
Your message dated Tue, 30 Jan 2024 16:29:35 -0700 with message-id and subject line Fixed in podget 0.9.3-1 has caused the Debian Bug report #1054132, regarding podget: line 2532: ITEM_TITLE: unbound variable to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1054132: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1054132 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: podget Version: 0.9.1-1 Severity: normal I haven't had time to see whether this is something trivial, but just to report that the new podget is giving: /usr/bin/podget: line 2532: ITEM_TITLE: unbound variable In context: Downloading feed index from http://www.thenakedscientists.com/naked_scientists_podcast.xml 2023-10-17 16:59:51 URL:https://www.thenakedscientists.com/naked_scientists_podcast.xml [2448064/2448064] -> "-" [1] /usr/bin/podget: line 2532: ITEM_TITLE: unbound variable serverlist entry is http://www.thenakedscientists.com/naked_scientists_podcast.xml sci n_sci -- System Information: Debian Release: trixie/sid APT prefers testing-debug APT policy: (500, 'testing-debug'), (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 6.5.0-1-amd64 (SMP w/8 CPU threads; PREEMPT) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), LANGUAGE=en_GB:en Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) Versions of packages podget depends on: ii gawk 1:5.2.1-2 ii mawk 1.3.4.20230808-1 ii wget 1.21.4-1+b1 podget recommends no packages. podget suggests no packages. -- no debconf information --- End Message --- --- Begin Message --- Version: 0.9.3-1 This should be fixed now. -- Dave VehrsEmail: dve...@gmail.com--- End Message ---
Bug#1054131: marked as done (podget: line 2532: ITEM_TITLE: unbound variable)
Your message dated Tue, 30 Jan 2024 16:27:48 -0700 with message-id and subject line Fixed in podget 0.9.3-1 has caused the Debian Bug report #1054131, regarding podget: line 2532: ITEM_TITLE: unbound variable to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1054131: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1054131 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: podget Version: 0.9.1-1 Severity: normal I haven't had time to see whether this is omething trivial, but just to report that the new podget is giving: /usr/bin/podget: line 2532: ITEM_TITLE: unbound variable In context: Downloading feed index from http://www.thenakedscientists.com/naked_scientists_podcast.xml 2023-10-17 16:59:51 URL:https://www.thenakedscientists.com/naked_scientists_podcast.xml [2448064/2448064] -> "-" [1] /usr/bin/podget: line 2532: ITEM_TITLE: unbound variable serverlist entry is http://www.thenakedscientists.com/naked_scientists_podcast.xml sci n_sci -- System Information: Debian Release: trixie/sid APT prefers testing-debug APT policy: (500, 'testing-debug'), (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 6.5.0-1-amd64 (SMP w/8 CPU threads; PREEMPT) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), LANGUAGE=en_GB:en Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) Versions of packages podget depends on: ii gawk 1:5.2.1-2 ii mawk 1.3.4.20230808-1 ii wget 1.21.4-1+b1 podget recommends no packages. podget suggests no packages. -- no debconf information --- End Message --- --- Begin Message --- Version: 0.9.3-1 This should be fixed. -- Dave VehrsEmail: dve...@gmail.com--- End Message ---
Bug#1054130: marked as done (podget: line 2532: ITEM_TITLE: unbound variable)
Your message dated Tue, 30 Jan 2024 16:17:22 -0700 with message-id and subject line Fixed in podget 0.9.3-1 has caused the Debian Bug report #1054130, regarding podget: line 2532: ITEM_TITLE: unbound variable to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1054130: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1054130 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: podget Version: 0.9.1-1 Severity: normal I haven't had time to see whether this is omething trivial, but just to report that the new podget is giving: /usr/bin/podget: line 2532: ITEM_TITLE: unbound variable In context: Downloading feed index from http://www.thenakedscientists.com/naked_scientists_podcast.xml 2023-10-17 16:59:51 URL:https://www.thenakedscientists.com/naked_scientists_podcast.xml [2448064/2448064] -> "-" [1] /usr/bin/podget: line 2532: ITEM_TITLE: unbound variable serverlist entry is http://www.thenakedscientists.com/naked_scientists_podcast.xml sci n_sci -- System Information: Debian Release: trixie/sid APT prefers testing-debug APT policy: (500, 'testing-debug'), (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 6.5.0-1-amd64 (SMP w/8 CPU threads; PREEMPT) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), LANGUAGE=en_GB:en Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) Versions of packages podget depends on: ii gawk 1:5.2.1-2 ii mawk 1.3.4.20230808-1 ii wget 1.21.4-1+b1 podget recommends no packages. podget suggests no packages. -- no debconf information --- End Message --- --- Begin Message --- Version: 0.9.3-1 This should be fixed now. Sorry for not marking this complete sooner. Dave --- Dave VehrsEmail: dve...@gmail.com--- End Message ---
Bug#1047610: marked as done (pd-flext: Fails to build source after successful build)
Your message dated Tue, 30 Jan 2024 22:52:46 + with message-id and subject line Bug#1047610: fixed in pd-flext 0.6.3-1 has caused the Debian Bug report #1047610, regarding pd-flext: Fails to build source after successful 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.) -- 1047610: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1047610 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: pd-flext Version: 0.6.2-4 Severity: minor Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-sab-20230813 ftbfs-source-after-build User: debian...@lists.debian.org Usertags: qa-doublebuild Hi, This package fails to build a source package after a successful build (dpkg-buildpackage ; dpkg-buildpackage -S). This is probably a clear violation of Debian Policy section 4.9 (clean target), but this is filed as severity:minor for now, because a discussion on debian-devel showed that we might want to revisit the requirement of a working 'clean' target. More information about this class of issues, included common problems and solutions, is available at https://wiki.debian.org/qa.debian.org/FTBFS/SourceAfterBuild Relevant part of the build log: > cd /<> && runuser -u user42 -- dpkg-buildpackage --sanitize-env > -us -uc -rfakeroot -S > --- > > dpkg-buildpackage: info: source package pd-flext > dpkg-buildpackage: info: source version 0.6.2-4 > dpkg-buildpackage: info: source distribution unstable > dpkg-buildpackage: info: source changed by IOhannes m zmölnig (Debian/GNU) > > dpkg-source --before-build . > debian/rules clean > dh clean >dh_autoreconf_clean >dh_clean > dpkg-source -b . > dpkg-source: error: unwanted binary file: > debian/build/flavor-pd64/source/.libs/libflext-pd64.so.0 > dpkg-source: error: unwanted binary file: > debian/build/flavor-pd64/source/.libs/libflext-pd64.so.0.6.2 > dpkg-source: error: unwanted binary file: > debian/build/flavor-pd64/source/.libs/libflext-pd64_d.so.0 > dpkg-source: error: unwanted binary file: > debian/build/flavor-pd64/source/.libs/libflext-pd64_d.so.0.6.2 > dpkg-source: error: unwanted binary file: > debian/build/flavor-pd32/source/.libs/libflext-pd.so.0 > dpkg-source: error: unwanted binary file: > debian/build/flavor-pd32/source/.libs/libflext-pd_d.so.0.6.2 > dpkg-source: error: unwanted binary file: > debian/build/flavor-pd32/source/.libs/libflext-pd_d.so.0 > dpkg-source: error: unwanted binary file: > debian/build/flavor-pd32/source/.libs/libflext-pd.so.0.6.2 > dpkg-source: error: detected 8 unwanted binary files (add them in > debian/source/include-binaries to allow their inclusion). > dpkg-source: info: using source format '3.0 (quilt)' > dpkg-buildpackage: error: dpkg-source -b . subprocess returned exit status 255 > > E: Command 'cd /<> && runuser -u user42 -- dpkg-buildpackage > --sanitize-env -us -uc -rfakeroot -S' failed to run. The full build log is available from: http://qa-logs.debian.net/2023/08/13/pd-flext_0.6.2-4_unstable.log If you reassign this bug to another package, please mark it as 'affects'-ing this package. See https://www.debian.org/Bugs/server-control#affects If you fail to reproduce this, please provide a build log and diff it with mine so that we can identify if something relevant changed in the meantime. --- End Message --- --- Begin Message --- Source: pd-flext Source-Version: 0.6.3-1 Done: IOhannes m zmölnig (Debian/GNU) We believe that the bug you reported is fixed in the latest version of pd-flext, 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 1047...@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 pd-flext 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, 30 Jan 2024 23:24:55 +0100 Source: pd-flext Architecture: source Version: 0.6.3-1 Distribution: unstable Urgency: medium Maintainer: Debian Multimedia Maintainers Changed-By: IOhannes m zmölnig (Debian/GNU) Closes: 1047610 Changes: pd-flext (0.6.3-1)
Bug#1059970: marked as done (fitspng: autopkgtest regression in testing)
Your message dated Tue, 30 Jan 2024 21:50:20 + with message-id and subject line Bug#1059970: fixed in fitspng 2.0-2 has caused the Debian Bug report #1059970, regarding fitspng: autopkgtest regression in testing 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.) -- 1059970: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1059970 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: fitspng Version: 2.0-1 Severity: serious Tags: sid trixie User: debian...@lists.debian.org Usertags: regression Hi Maintainer Sometime between 2023-12-10 and 2024-01-3, fitspng's autopkgtests started to fail in testing [1]. I've copied what I hope is the relevant part of the log below. Regards Graham [1] https://ci.debian.net/packages/f/fitspng/testing/amd64/ 18s autopkgtest [06:35:13]: test check: [--- 19s OK: hippo.png (139x152, 24-bit RGB, non-interlaced, 38.7%). 19s zlib warning: different version (expected 1.2.13, using 1.3) 19s 19s autopkgtest [06:35:14]: test check: ---] 19s autopkgtest [06:35:14]: test check: - - - - - - - - - - results - - - - - - - - - - 19s check FAIL stderr: zlib warning: different version (expected 1.2.13, using 1.3) 19s autopkgtest [06:35:14]: test check: - - - - - - - - - - stderr - - - - - - - - - - 19s zlib warning: different version (expected 1.2.13, using 1.3) 19s --- End Message --- --- Begin Message --- Source: fitspng Source-Version: 2.0-2 Done: Filip Hroch We believe that the bug you reported is fixed in the latest version of fitspng, 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 1059...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Filip Hroch (supplier of updated fitspng 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, 30 Jan 2024 19:53:50 +0100 Source: fitspng Architecture: source Version: 2.0-2 Distribution: unstable Urgency: low Maintainer: Debian Astronomy Team Changed-By: Filip Hroch Closes: 1059970 1061774 Changes: fitspng (2.0-2) unstable; urgency=low . * Update of autopkgtests by ignoring of a warning due pngcheck (Closes: #1059970, #1061774) * Update of packaging: latest standards, included .acs of the source. Checksums-Sha1: f2c80204677be6bbe49931024debea24da445b1f 2271 fitspng_2.0-2.dsc 4466fd15ce56fceabbb417f3ace5309f40a9ccaa 1138938 fitspng_2.0.orig.tar.gz 93736e8081f86b78bae8125526e80440308781b5 833 fitspng_2.0.orig.tar.gz.asc fe090421e61bc790b5a6052ece470c7a37561f92 40808 fitspng_2.0-2.debian.tar.xz 801876f6b582953dff3c7e42e19e7ffed316e2bf 6604 fitspng_2.0-2_source.buildinfo Checksums-Sha256: 4ec387f109d1c15893351d3d3555c9a6199a2c3d013d5aed48638093ace0f3e8 2271 fitspng_2.0-2.dsc a2109c37ab85f6d15126c5f5cb4727e95f61db38c94f56849c03c872813d133a 1138938 fitspng_2.0.orig.tar.gz ee79ce8e13256be67ebeaed79e71f84cda6b9d914c09d7fd29217ab3a4d7dd5b 833 fitspng_2.0.orig.tar.gz.asc 53255ab5d6c9ec6200f55cb486cbc3f46aa87635e77993317b282e16ee8d8802 40808 fitspng_2.0-2.debian.tar.xz 6ce65aecb0ab0de50d9a6c3bf393fb060e4d455e000cf8340256682b7bf6077c 6604 fitspng_2.0-2_source.buildinfo Files: 3e9536c63fd3b127e1723770e0372ca1 2271 science optional fitspng_2.0-2.dsc 0fd84d5a244dd6348fe4f3224591da3e 1138938 science optional fitspng_2.0.orig.tar.gz b4a4d9084a94db00a17b8b2e4b83d0dc 833 science optional fitspng_2.0.orig.tar.gz.asc 9e97142656d3edf120f02cba7bda64d2 40808 science optional fitspng_2.0-2.debian.tar.xz 3eadcb30bfb26d4c14de07512460bced 6604 science optional fitspng_2.0-2_source.buildinfo -BEGIN PGP SIGNATURE- iQJKBAEBCgA0FiEEUDKf13MuKrCBYUNfHmJd9kly/5oFAmW5a8gWHGhyb2NoQHBo eXNpY3MubXVuaS5jegAKCRAeYl32SXL/mi/BD/4/BzQxMVeou/szInOVBxpmKG9L 8h3JhwgPgYZB8SizBXdkOIth8ah6uDiJFb+2vTLHVpSpLFZvv2hCmL4SWhAopCDy V0/hfvGjFyLbYnAS0jUQ6TcIUzotuyq/pAMSiM26L71I3vVsqJba9agQsRXned+y q2XMEXRtpv2QqsGl+8z3LpprAaCSpmC0ZcRQjfuhlTXufMfIhQBStX0Lqe2nmZab wZxlnhOTsAAPq2RNR18Nk21Hq2E9Vy0Q0nTSasafNaBA2rZn0clFYkqiv1z8n4CO 9C16yajJyDsofx8ilNeqwJX/EZdGmrl9ldaxkPAFSScoT9XEAkLh9CTKYq0cXs8A yHBlm2tZDK941hbJ5YPa1zykbmsS+PmmmKLPipkK/OfPZW+iiWuO0l2OJXyRmYVn
Bug#1061984: marked as done (libboinc-app7t64 and libboinc7t64 have an undeclared file conflict)
Your message dated Tue, 30 Jan 2024 21:49:43 + with message-id and subject line Bug#1061984: fixed in boinc 7.20.5+dfsg-1.2~exp2 has caused the Debian Bug report #1061984, regarding libboinc-app7t64 and libboinc7t64 have an undeclared file conflict 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.) -- 1061984: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1061984 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: libboinc7t64,libboinc-app7t64 Version: 7.20.5+dfsg-1.2~exp1 Severity: serious User: debian...@lists.debian.org Usertags: fileconflict Control: affects -1 + libboinc-app7 libboinc7 X-Debbugs-Cc: vor...@debian.org libboinc-app7t64 and libboinc7t64 have an undeclared file conflict. This may result in an unpack error from dpkg. The files * /usr/lib/x86_64-linux-gnu/libboinc_api.so.7 * /usr/lib/x86_64-linux-gnu/libboinc_api.so.7.20.5 * /usr/lib/x86_64-linux-gnu/libboinc_graphics2.so.7 * /usr/lib/x86_64-linux-gnu/libboinc_graphics2.so.7.20.5 * /usr/lib/x86_64-linux-gnu/libboinc_opencl.so.7 * /usr/lib/x86_64-linux-gnu/libboinc_opencl.so.7.20.5 are contained in the packages * libboinc-app7 * 7.20.5+dfsg-1.1 as present in bookworm * 7.20.5+dfsg-1.1+b2 as present in trixie|unstable * libboinc-app7t64/7.20.5+dfsg-1.2~exp1 as present in experimental The files * /usr/lib/x86_64-linux-gnu/libboinc.so.7 * /usr/lib/x86_64-linux-gnu/libboinc.so.7.20.5 * /usr/lib/x86_64-linux-gnu/libboinc_crypt.so.7 * /usr/lib/x86_64-linux-gnu/libboinc_crypt.so.7.20.5 * /usr/lib/x86_64-linux-gnu/libboinc_zip.so.7 * /usr/lib/x86_64-linux-gnu/libboinc_zip.so.7.20.5 * /usr/lib/x86_64-linux-gnu/libsched.so.7 * /usr/lib/x86_64-linux-gnu/libsched.so.7.20.5 are contained in the packages * libboinc7 * 7.20.5+dfsg-1.1 as present in bookworm * 7.20.5+dfsg-1.1+b2 as present in trixie|unstable * libboinc7t64/7.20.5+dfsg-1.2~exp1 as present in experimental These packages can be unpacked concurrently, because there is no relevant Replaces or Conflicts relation. Attempting to unpack these packages concurrently results in an unpack error from dpkg, because none of the packages installs a diversion for the affected files. Kind regards The Debian Usr Merge Analysis Tool This bug report has been automatically filed with no human intervention. The source code is available at https://salsa.debian.org/helmutg/dumat. If the filing is unclear or in error, don't hesitate to contact hel...@subdivi.de for assistance. --- End Message --- --- Begin Message --- Source: boinc Source-Version: 7.20.5+dfsg-1.2~exp2 Done: Steve Langasek We believe that the bug you reported is fixed in the latest version of boinc, 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 1061...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Steve Langasek (supplier of updated boinc 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, 30 Jan 2024 21:15:58 + Source: boinc Architecture: source Version: 7.20.5+dfsg-1.2~exp2 Distribution: experimental Urgency: medium Maintainer: Debian BOINC Maintainers Changed-By: Steve Langasek Closes: 1061984 Changes: boinc (7.20.5+dfsg-1.2~exp2) experimental; urgency=medium . * Patch debian/control.in, which uses idiosyncratic format and therefore failed to be automatically patched, then clobbered necessary changes in debian/control regarding Breaks/Replaces/Provides. Closes: #1061984. Checksums-Sha1: 27adad01e5a3ff8c11c1e52cea395ac324df609a 3170 boinc_7.20.5+dfsg-1.2~exp2.dsc fe848333ef11633bbfcefdbbc6860ee10dd275de 455144 boinc_7.20.5+dfsg-1.2~exp2.debian.tar.xz d39658070c760b48f3929102ee13a7fa0b0d85b3 20430 boinc_7.20.5+dfsg-1.2~exp2_source.buildinfo Checksums-Sha256: 3c2c4f66940b76747e1e628ec4bf624437cd4a0f2755f2b1e833cb7ce0a14880 3170 boinc_7.20.5+dfsg-1.2~exp2.dsc 8820e38551cdb5eb3913a7b1a0a2ddfd20a4577da3eaafca07108a5d7a6b07dd 455144 boinc_7.20.5+dfsg-1.2~exp2.debian.tar.xz 08ed1cce1e81d753de8cdb47a378bbf565bdeeb63392c6c57380b7286aa2a175 20430 boinc_7.20.5+dfsg-1.2~exp2_source.buildinfo Files: 62ebc9886ccd48be15db60c316de72bc 3170 net optional
Bug#1061774: marked as done (fitspng: prints warnings on zlib updates)
Your message dated Tue, 30 Jan 2024 21:50:20 +
with message-id
and subject line Bug#1061774: fixed in fitspng 2.0-2
has caused the Debian Bug report #1061774,
regarding fitspng: prints warnings on zlib updates
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.)
--
1061774: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1061774
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: binnmu
X-Debbugs-Cc: pngch...@packages.debian.org
Control: affects -1 + src:pngcheck
Dear Release Team,
may I ask you to rebuild pngcheck package against to
the current version of zlib?
I'm maintainer of fitspng package having bug #1059970,
and I found that the bug is not related on fitspng itself.
Actually, it is caused by pngcheck during CI tests
verification. The current binary of pngcheck is compiled
against an old zlib yet, and needs a recompilation.
A test run under sid (as well as trixie) has revealed:
x@trixiesid:/tmp/xxx$ pngcheck hippo.png
zlib warning: different version (expected 1.2.13, using 1.3)
OK: hippo.png (139x152, 24-bit RGB, non-interlaced, 38.7%).
The string can be identified as the part of the source of pngcheck.c
(https://salsa.debian.org/debian/pngcheck/-/blob/debian/master/pngcheck.c)
which compares versions of the run-time zlib and the zlib compiled in:
...
} else if (strcmp(zlib_version, ZLIB_VERSION) != 0) {
fprintf(stderr, "zlib warning: different version (expected %s,"
" using %s)\n\n", ZLIB_VERSION, zlib_version);
}
..
In my opinion, the test on a zlib version is greatly valuable,
although it may create doubts during those transitional phases.
Thank you,
FH
nmu pngcheck_3.0.3-1 . ANY . -m "Rebuild against a new version of zlib."
--- End Message ---
--- Begin Message ---
Source: fitspng
Source-Version: 2.0-2
Done: Filip Hroch
We believe that the bug you reported is fixed in the latest version of
fitspng, 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 1061...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Filip Hroch (supplier of updated fitspng 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, 30 Jan 2024 19:53:50 +0100
Source: fitspng
Architecture: source
Version: 2.0-2
Distribution: unstable
Urgency: low
Maintainer: Debian Astronomy Team
Changed-By: Filip Hroch
Closes: 1059970 1061774
Changes:
fitspng (2.0-2) unstable; urgency=low
.
* Update of autopkgtests by ignoring of a warning due pngcheck (Closes:
#1059970, #1061774)
* Update of packaging: latest standards, included .acs of the source.
Checksums-Sha1:
f2c80204677be6bbe49931024debea24da445b1f 2271 fitspng_2.0-2.dsc
4466fd15ce56fceabbb417f3ace5309f40a9ccaa 1138938 fitspng_2.0.orig.tar.gz
93736e8081f86b78bae8125526e80440308781b5 833 fitspng_2.0.orig.tar.gz.asc
fe090421e61bc790b5a6052ece470c7a37561f92 40808 fitspng_2.0-2.debian.tar.xz
801876f6b582953dff3c7e42e19e7ffed316e2bf 6604 fitspng_2.0-2_source.buildinfo
Checksums-Sha256:
4ec387f109d1c15893351d3d3555c9a6199a2c3d013d5aed48638093ace0f3e8 2271
fitspng_2.0-2.dsc
a2109c37ab85f6d15126c5f5cb4727e95f61db38c94f56849c03c872813d133a 1138938
fitspng_2.0.orig.tar.gz
ee79ce8e13256be67ebeaed79e71f84cda6b9d914c09d7fd29217ab3a4d7dd5b 833
fitspng_2.0.orig.tar.gz.asc
53255ab5d6c9ec6200f55cb486cbc3f46aa87635e77993317b282e16ee8d8802 40808
fitspng_2.0-2.debian.tar.xz
6ce65aecb0ab0de50d9a6c3bf393fb060e4d455e000cf8340256682b7bf6077c 6604
fitspng_2.0-2_source.buildinfo
Files:
3e9536c63fd3b127e1723770e0372ca1 2271 science optional fitspng_2.0-2.dsc
0fd84d5a244dd6348fe4f3224591da3e 1138938 science optional
fitspng_2.0.orig.tar.gz
b4a4d9084a94db00a17b8b2e4b83d0dc 833 science optional
fitspng_2.0.orig.tar.gz.asc
9e97142656d3edf120f02cba7bda64d2 40808 science optional
fitspng_2.0-2.debian.tar.xz
3eadcb30bfb26d4c14de07512460bced 6604 science optional
fitspng_2.0-2_source.buildinfo
-BEGIN PGP SIGNATURE-
iQJKBAEBCgA0FiEEUDKf13MuKrCBYUNfHmJd9kly/5oFAmW5a8gWHGhyb2NoQHBo
Bug#1044078: marked as done (cnvkit: FTBFS with pandas 2.0)
Your message dated Tue, 30 Jan 2024 21:34:32 + with message-id <845d1345-7923-4fd7-a075-a4843bb59...@zoho.com> and subject line Re: cnvkit and pandas 2.x has caused the Debian Bug report #1044078, regarding cnvkit: FTBFS with pandas 2.0 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.) -- 1044078: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1044078 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:cnvkit Version: 0.9.9-2 Control: block 1043240 by -1 cnvkit fails to build with pandas 2.0, currently in experimental. Build log: https://launchpadlibrarian.net/680699189/buildlog_ubuntu-mantic-amd64.cnvkit_0.9.9-2_BUILDING.txt.gz Autopkgtest log: https://ci.debian.net/data/autopkgtest/unstable/amd64/c/cnvkit/36575798/log.gz A common source of failures is that pandas.util.testing has been renamed to pandas.testing. Both names were available in all 1.x versions (and hence in Debian stable and oldstable), so Debian packages that were using this can immediately switch unconditionally. --- End Message --- --- Begin Message --- Version: 0.9.10-1 No longer failing, which probably means upstream have fixed this.--- End Message ---
Bug#1061949: marked as done (elan - upcoming rust-toml update.)
Your message dated Tue, 30 Jan 2024 20:51:19 + with message-id and subject line Bug#1061949: fixed in elan 3.0.0-3 has caused the Debian Bug report #1061949, regarding elan - upcoming rust-toml update. 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.) -- 1061949: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1061949 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: elan Version: 3.0.0-2 I hope to update the rust-toml package to version 0.8 soon. I have tested that elan builds with the dependency bumped. However, given https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1061550 I think it probably makes more sense for your package to switch back to using toml 0.5, as your upstream expects. toml 0.5 is maintained in a seperate source package and is unlikely to be going away any time soon. The debdiff for doing so is posted over in the other bug. --- End Message --- --- Begin Message --- Source: elan Source-Version: 3.0.0-3 Done: Christopher Hoskin We believe that the bug you reported is fixed in the latest version of elan, 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 1061...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Christopher Hoskin (supplier of updated elan 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, 30 Jan 2024 19:55:08 + Source: elan Architecture: source Version: 3.0.0-3 Distribution: unstable Urgency: medium Maintainer: Christopher Hoskin Changed-By: Christopher Hoskin Closes: 1061550 1061949 Changes: elan (3.0.0-3) unstable; urgency=medium . [ Peter Michael Green ] * Non-maintainer upload. * Switch back to using toml-0.5, toml-0.7 seems to cause incorrect config generation (Closes: #1061550, #1061949). . [ Christopher Hoskin ] * Apply patch from Peter Michael Green Checksums-Sha1: f1de18fd965d4795dc75b498f62a7e157ecd52ae 2781 elan_3.0.0-3.dsc 0c8bb603f0da1eec345c589ba2054249fe786a24 6200 elan_3.0.0-3.debian.tar.xz 839ea4e6246801f4c16d9c38b46a05b12cf6e273 18459 elan_3.0.0-3_amd64.buildinfo Checksums-Sha256: 0fe45e19e66cfd1b1dda00ae0df5f710784d219bab5616988b78c96be62db2be 2781 elan_3.0.0-3.dsc 06afe0d4ed6d5bbe452212709394ae7d536998f8aa2b0c3946a4672c5182adac 6200 elan_3.0.0-3.debian.tar.xz d3c4274bd13d94c401f58dded06682b06908995464277ea4c28cafda6d7f2a1d 18459 elan_3.0.0-3_amd64.buildinfo Files: 7802690e7c329d9064c02bf8b634aeb2 2781 math optional elan_3.0.0-3.dsc 4e059a36c302909a0244214d24c047e8 6200 math optional elan_3.0.0-3.debian.tar.xz e85060b49eb077bed1a4d863b8bd22e1 18459 math optional elan_3.0.0-3_amd64.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEbctJ5K6JlvFsvhGhf6qUsnUUSpoFAmW5VX0ACgkQf6qUsnUU Spp4nxAAlQ5ZLtKMcmXO6tCKm9yrw87JZtPbubIhwRMOFlEAm0yvLhUubseCsw66 ttfZFBpcosk6xg89mLlUIrewCjatIFg1QnlApm4AV83JOfkBEN3O8MmoiCaz/bCy i2akuhPxlvJLs6nOdG0dM5rn83xsXn0rJ3M4SsIizYizq4e+W7qQpW3m/y8cPZ1+ jvOwS3sO0kBxcjKIu4MM1I89KRaSgZq9hCia1W933C5n1SpBKquJ796xbUHGI9+d uecKbxgsBkYTvZx+1ISwANBsfWf6vDXj1DPOqoiewh0YBCFLQ6bsVFEN187TOXA5 /FYelUOdI9EhWh1k2NJBC+J9q2U4NCYOc8OF6mKcIozCf/3zNcDWy0gQGaSCnOjo kPk5uy7Svxrmsy5Y83Db4k+YL7cCoWFVX7CRp066503p5ETup+xVfUTm5MgwzbqX ex+JJJxFXHoxjthvDAnuxOzFMqLMEAmtB3MQBbjR873CoKai7yKmdYpeQ1Hwe5Hc 563y0T8hUO6Z04UoygWOPe/XL+mcL+6ladNcJNHIX0ykKEqqZ0FUwVkspZCnJnzU nMl5JNSAOAdYdWVUHV892yjCCMlJ1GHE0e2XMWdQX4t30hYXaUrQfPjufR/70Zbg Tv0YGsarCD4Po5j9PtcTFC3d+gDpMJDj0cnlxfu26MnuOnZfI5Q= =sjJU -END PGP SIGNATURE End Message ---
Bug#1061550: marked as done (elan: creates invalid settings file on startup)
Your message dated Tue, 30 Jan 2024 20:51:19 +
with message-id
and subject line Bug#1061550: fixed in elan 3.0.0-3
has caused the Debian Bug report #1061550,
regarding elan: creates invalid settings file on startup
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.)
--
1061550: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1061550
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: elan
Version: 3.0.0-2
Severity: important
I installed elan, and had no ~/.elan directory. I created an empty
directory ~/leantest, changed into it and ran the command "elan
default stable". This creates the ~/.elan directory and populates
it. However, the output of this command was:
info: syncing channel updates for 'stable'
info: latest update on stable, lean version v4.4.0
info: downloading component 'lean'
Total: 182.6 MiB Speed: 8.0 MiB/s
info: installing component 'lean'
error: error parsing settings
The settings file, ~/.elan/settings.toml, contains the single line:
{ telemetry = false, version = "12", overrides = {} }
which is clearly in JSON format rather than TOML format.
Manually editing the file to read:
telemetry = false
version = "12"
overrides = { }
allows "elan default stable" to work, though it then modifies
~/.elan/settings.toml to read:
{ default_toolchain = "stable", telemetry = false, version = "12", overrides =
{} }
which then breaks the next attempt to use elan:
euler:~/leantest $ elan default stable
info: using existing install for 'stable'
error: error parsing settings
So it seems that elan is for some reason writing out the settings in
JSON rather than TOML format every time it touches them.
As a data point, the settings.toml on a Mac reads (between the "---"
lines):
---
default_toolchain = "stable"
telemetry = false
version = "12"
[overrides]
---
So something is very wrong here.
Best wishes,
Julian
--- End Message ---
--- Begin Message ---
Source: elan
Source-Version: 3.0.0-3
Done: Christopher Hoskin
We believe that the bug you reported is fixed in the latest version of
elan, 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 1061...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Christopher Hoskin (supplier of updated elan 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, 30 Jan 2024 19:55:08 +
Source: elan
Architecture: source
Version: 3.0.0-3
Distribution: unstable
Urgency: medium
Maintainer: Christopher Hoskin
Changed-By: Christopher Hoskin
Closes: 1061550 1061949
Changes:
elan (3.0.0-3) unstable; urgency=medium
.
[ Peter Michael Green ]
* Non-maintainer upload.
* Switch back to using toml-0.5, toml-0.7 seems to cause incorrect config
generation (Closes: #1061550, #1061949).
.
[ Christopher Hoskin ]
* Apply patch from Peter Michael Green
Checksums-Sha1:
f1de18fd965d4795dc75b498f62a7e157ecd52ae 2781 elan_3.0.0-3.dsc
0c8bb603f0da1eec345c589ba2054249fe786a24 6200 elan_3.0.0-3.debian.tar.xz
839ea4e6246801f4c16d9c38b46a05b12cf6e273 18459 elan_3.0.0-3_amd64.buildinfo
Checksums-Sha256:
0fe45e19e66cfd1b1dda00ae0df5f710784d219bab5616988b78c96be62db2be 2781
elan_3.0.0-3.dsc
06afe0d4ed6d5bbe452212709394ae7d536998f8aa2b0c3946a4672c5182adac 6200
elan_3.0.0-3.debian.tar.xz
d3c4274bd13d94c401f58dded06682b06908995464277ea4c28cafda6d7f2a1d 18459
elan_3.0.0-3_amd64.buildinfo
Files:
7802690e7c329d9064c02bf8b634aeb2 2781 math optional elan_3.0.0-3.dsc
4e059a36c302909a0244214d24c047e8 6200 math optional elan_3.0.0-3.debian.tar.xz
e85060b49eb077bed1a4d863b8bd22e1 18459 math optional
elan_3.0.0-3_amd64.buildinfo
-BEGIN PGP SIGNATURE-
iQIzBAEBCgAdFiEEbctJ5K6JlvFsvhGhf6qUsnUUSpoFAmW5VX0ACgkQf6qUsnUU
Spp4nxAAlQ5ZLtKMcmXO6tCKm9yrw87JZtPbubIhwRMOFlEAm0yvLhUubseCsw66
ttfZFBpcosk6xg89mLlUIrewCjatIFg1QnlApm4AV83JOfkBEN3O8MmoiCaz/bCy
i2akuhPxlvJLs6nOdG0dM5rn83xsXn0rJ3M4SsIizYizq4e+W7qQpW3m/y8cPZ1+
jvOwS3sO0kBxcjKIu4MM1I89KRaSgZq9hCia1W933C5n1SpBKquJ796xbUHGI9+d
uecKbxgsBkYTvZx+1ISwANBsfWf6vDXj1DPOqoiewh0YBCFLQ6bsVFEN187TOXA5
/FYelUOdI9EhWh1k2NJBC+J9q2U4NCYOc8OF6mKcIozCf/3zNcDWy0gQGaSCnOjo
Bug#1044079: marked as done (augur: FTBFS with pandas 2.0)
Your message dated Tue, 30 Jan 2024 20:46:34 + with message-id and subject line Bug#1044079: fixed in augur 24.0.0-1 has caused the Debian Bug report #1044079, regarding augur: FTBFS with pandas 2.0 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.) -- 1044079: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1044079 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:augur Version: 22.1.0-1 Control: block 1043240 by -1 augur fails to build with pandas 2.0, currently in experimental. Build log: https://launchpadlibrarian.net/680698719/buildlog_ubuntu-mantic-amd64.augur_22.1.0-1_BUILDING.txt.gz Autopkgtest log: https://ci.debian.net/data/autopkgtest/unstable/amd64/a/augur/36575793/log.gz A common source of failures is that pandas.util.testing has been renamed to pandas.testing. Both names were available in all 1.x versions (and hence in Debian stable and oldstable), so Debian packages that were using this can immediately switch unconditionally. --- End Message --- --- Begin Message --- Source: augur Source-Version: 24.0.0-1 Done: Étienne Mollier We believe that the bug you reported is fixed in the latest version of augur, 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 1044...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Étienne Mollier (supplier of updated augur 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, 30 Jan 2024 20:41:16 +0100 Source: augur Architecture: source Version: 24.0.0-1 Distribution: unstable Urgency: medium Maintainer: Debian Med Packaging Team Changed-By: Étienne Mollier Closes: 1044079 Changes: augur (24.0.0-1) unstable; urgency=medium . * New upstream version (Closes: #1044079) Checksums-Sha1: 053fad0c35f743d68efd3b37418337b47a7b64ca 2754 augur_24.0.0-1.dsc 4d9c422d4df8878f96a8408381865eb2f1796c2c 6711386 augur_24.0.0.orig.tar.gz b33938139a0712e0ccb0572f6f61b0815f4dca73 15908 augur_24.0.0-1.debian.tar.xz Checksums-Sha256: 5a449b9faf41413e3df0ac60120a21437cc1342bfd9b98673e9c0f3f141ccb54 2754 augur_24.0.0-1.dsc 1be2ec4627660a151aad34fbabce592102a034cbb661f10cd5d56934960f28de 6711386 augur_24.0.0.orig.tar.gz 4460c3a9c5b4091e7525fb7cff67e400f3e1541cba62b9372a492a6912b161ba 15908 augur_24.0.0-1.debian.tar.xz Files: 44d47cbd56d386fc42eec89c9c5dfcd5 2754 science optional augur_24.0.0-1.dsc a06baf5804a59b0afdc0b1a5be5dda6c 6711386 science optional augur_24.0.0.orig.tar.gz 3823a4d9e3a99469c82217612d1b4943 15908 science optional augur_24.0.0-1.debian.tar.xz -BEGIN PGP SIGNATURE- iQJIBAEBCgAyFiEEj5GyJ8fW8rGUjII2eTz2fo8NEdoFAmW5UkQUHGVtb2xsaWVy QGRlYmlhbi5vcmcACgkQeTz2fo8NEdoyHhAAql+VbjGbx8TLKogUM/1XCH0Gi+f/ crIdIama+TIu6vOcJK7/HRHZAKvuXaIRhs6mfRuEIGzsV0gkYSOXWxv5s9d4zKpQ Xat/NfUsx1oCEeTL7L7bKmjwzYFBnpps+tBr7rtAc46CppxLMJxZAUzybk0anqeC 2sSX3Ur1ZBWQkflG2Uf8asoM7LsoVGjjn5/X+TWP/cz5ENy1mmp0gN2K7rCImywJ 1+zLbyBuwvLlVGrBvU/JeINiIu0KHntuYRIeHquu2lBCZ2Katv5C96mQ6sPRKUiZ R8n4sdaVjO19walVP0Ui4Wu4AodPorXdBzNnJpzj4xMe6YWtTaH5MUvrQqPHC5GU a0CX+dAp5GzAYM29wMz4U4w5LdiJS/Sx2hTIFQjOwRmmITiI+uM9IkypEFbMO6Hc mh24y2U92x/9jf+Wkqg7UtQlDVpY7gzUrHpg6SFfNyPz3vw0zjuLHOqZMgBTYflm HjbK9Tz9qksiZTsttO+0ZFxeVRKbJHeWbtHiF3OudqRFqCf32BYLD/SlpIbbGGAN HrFBQCaiFSVG4aiOMey3/+CuF3lDil51aW3El8t4cp9U2EM5HuSJQSsxnKlU6S/4 gOLTqj9zreQiylATFi2zw5cHpUvUdpRJXQkb2Sn7HimfHo54gNRlwz33MrEC1Lul Gstlq9yy6U/KyLQ= =MNUd -END PGP SIGNATURE End Message ---
Bug#1059104: marked as done (rust-toml: please upgrade to v0.8)
Your message dated Tue, 30 Jan 2024 19:14:02 + with message-id and subject line Bug#1059104: fixed in rust-toml 0.8.8-2 has caused the Debian Bug report #1059104, regarding rust-toml: please upgrade to v0.8 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.) -- 1059104: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1059104 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: rust-toml Version: 0.7.8-1 Severity: normal Tags: upstream -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Please upgrade to, or separately provide, branch v0.8. -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEn+Ppw2aRpp/1PMaELHwxRsGgASEFAmWCunAACgkQLHwxRsGg ASEuZw//WJgOhrvFFENMZYBICTzjaceHzDFqFMM6YpRUJT0o8qD2XE9JtEW118IB GFmq+n9BquwvnqLPC76bW7zZ2zTjS5XXsFA4eD7DOcjYKeDdpC+AEVx1ZolRZ1x9 H0z81X9VNEfHDqOUy1YkYF9z2kzI3i/UHuvAiRmLUpllnWQaBi7nkrw1N/wTt+Gi /x+iYQoLTJ8oB33+6CAQeiD2R202Jc0sJxok6adp7F2Sq8pwcJCGdic5lKFSdIeJ EfOA6vShQv0FWu6c8K6VJ8Z0yHkrsaYznqeSUXLWnaT/yMKYy/o0jI3z35fIznWZ 0YrNlHBA5uE780FJNybxv/N2Q/tljwrKU1annmRWD1GBrSeqNrWvqUM/vBgNXmnz eR07mDy63Coi2/CXEFtJErUdhxU1V6J92Qsqjsml5yHavMRsukJonm9Ekm6PQy6n Zgs0Vei5+lfti3GH9Ongnx/gZlcd/ZGH+KQfk481za2eFl996FXegt/RuWtrYTGs 3IoXjCVavw1iN32eWbieWz3bklUFIEKnDGzLJp2VTph75Z0mmSd3AvJr4Z/uF9uq Di2Or8jkyaB07uqTQVrooLDvrUAauzJd2F1AUo+b3tS1KZiC+aUBFfd6s7paPiJG cKJZ/Osv1Rr6kMT5fy+QeH1mRbQOwvDIsnqHaYFgjtS8jkY67hQ= =mWyn -END PGP SIGNATURE- --- End Message --- --- Begin Message --- Source: rust-toml Source-Version: 0.8.8-2 Done: Peter Michael Green We believe that the bug you reported is fixed in the latest version of rust-toml, 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 1059...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Peter Michael Green (supplier of updated rust-toml 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, 30 Jan 2024 16:08:01 + Source: rust-toml Architecture: source Version: 0.8.8-2 Distribution: unstable Urgency: medium Maintainer: Debian Rust Maintainers Changed-By: Peter Michael Green Closes: 1059104 Changes: rust-toml (0.8.8-2) unstable; urgency=medium . * Team upload. * Package toml 0.8.8 from crates.io using debcargo 2.6.1 (Closes: #1059104. #1053955) Checksums-Sha1: dbee233c4d6e3b052cb39fa56c4bd478ccc645c8 2705 rust-toml_0.8.8-2.dsc 1007d68949785644c637367991924363b1c54c2f 3952 rust-toml_0.8.8-2.debian.tar.xz 3da08856c3bb7f484846a85ef9806af3bfec8178 8006 rust-toml_0.8.8-2_source.buildinfo Checksums-Sha256: 13623304fb32a07a6869a3d3b7a09fb56eec7ba4d1ac95a09d29bb5ad5797f0f 2705 rust-toml_0.8.8-2.dsc 8e59ce43cf073016a7b5d667845ad52e3ea4ee3c222c2a69e05d3f2ca441b3ce 3952 rust-toml_0.8.8-2.debian.tar.xz c210d344955d5a293697403b843fd90220943c6e359518e48c011cc88e2b8ef1 8006 rust-toml_0.8.8-2_source.buildinfo Files: f46d4fceaa3d9e307b8733580a502e53 2705 rust optional rust-toml_0.8.8-2.dsc 08cdb82e74a378d0b872481b9a587c46 3952 rust optional rust-toml_0.8.8-2.debian.tar.xz 87f0ab87cd560efee907631467a9160b 8006 rust optional rust-toml_0.8.8-2_source.buildinfo -BEGIN PGP SIGNATURE- iQJIBAEBCAAyFiEEU0DQATYMplbjSX63DEjqKnqP/XsFAmW5QOMUHHBsdWd3YXNo QGRlYmlhbi5vcmcACgkQDEjqKnqP/Xtx/Q/+P/d+7vUsHQUWYeC2n6SPU896haP1 oCaR/L1cR7HpFB2dV5QqsH2rlHcXpQ6gp12gD99X9DhyiD4q1I6e3Ol61geIC86Z tg8X710gR5LZ2B71CErcX6ci8hzDO14AHGAyS3IEW+yeC38ZCiII+QLGjD0Z7Ldy 3jeyIiTcdUSeu+bEycCw2TiJPKjtn/+SeskZD2FLIGIf8s7kHbSwtm6IzjvnJFh8 EyaDnRQ8pv8l4dg4GrNr09BA6k4Jw6CU9ez2t09G9XZ6Btx8tAabwv/4MWgBr1Ax bOVKgLc8z2wN3+RvahBqrcNBViLw0Vkh2plnE1KcQjmVqTJPQJ8MVYFwnhDfGxnl Wm/m7fVnF4GfqQTShj35ebKFhsqd6dmXBvvTQZEu4E24NBR03sUSJAN94kC7Z0By MQo2CwEte1FVcyGcOIVumznDIM0bGXNwVnCVVERo+MDQALE8TNPibQjPqOs2SAze Ax6m3kq8iMaZj6l40bubXFRrXdFMVglY2UsVexZFyLNu6Ta1oil0SvIWSig0/edh OEs7DdLgdHfNrXsE1dDEbq812WtukSxn9bKa1WecXrPMMQi90i9SbNGnwwFVkZQD Uj9jCvsmZIDCy8xE5+0xjDiM8UQrJn8dX7jKdBtnKPariGvhxck9el94SOormmyd NR8p9tCa2vJU5bc= =Nyua -END PGP SIGNATURE End Message ---
Bug#1044053: marked as done (dials: test failure with pandas 2.0)
Your message dated Tue, 30 Jan 2024 18:56:01 + with message-id and subject line Re: Bug#1043240: transition: pandas 1.5 -> 2.1 - please upload fixes has caused the Debian Bug report #1044053, regarding dials: test failure with pandas 2.0 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.) -- 1044053: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1044053 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:dials Version: 3.12.1+dfsg3-5 Control: block 1043240 by -1 dials fails its autopkgtest with pandas 2.0, currently in experimental. Log: https://ci.debian.net/data/autopkgtest/unstable/amd64/d/dials/36575801/log.gz A common source of failures is that pandas.util.testing has been renamed to pandas.testing. Both names were available in all 1.x versions (and hence in Debian stable and oldstable), so Debian packages that were using this can immediately switch unconditionally. --- End Message --- --- Begin Message --- Version: 3.17.0+dfsg3-1 On 30/01/2024 10:31, PICCA Frederic-Emmanuel wrote: for dials it seems that the CI works with pandas 2.1 from experimental. Probably because upstream fixed it, thanks.--- End Message ---
Bug#1061318: marked as done (device-tree-compiler ftbfs with Python 3.12 as default)
Your message dated Tue, 30 Jan 2024 17:45:53 + with message-id and subject line Bug#1061318: fixed in device-tree-compiler 1.7.0-2 has caused the Debian Bug report #1061318, regarding device-tree-compiler ftbfs with Python 3.12 as default 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.) -- 1061318: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1061318 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:device-tree-compiler Version: 1.7.0-1 Severity: serious Tags: sid trixie ftbfs User: debian-pyt...@lists.debian.org Usertags: python3.12 with python3-defaults from experimental: [...] testCreate (__main__.PyLibfdtSwTests.testCreate) ... FAIL == FAIL: testReserveMap (__main__.PyLibfdtBasicTests.testReserveMap) Test that we can access the memory reserve map -- Traceback (most recent call last): File "/<>/tests/./pylibfdt_tests.py", line 421, in testReserveMap self.assertEqual([ 0xdeadbeef, 0x10], AssertionError: Lists differ: [16045690981097406464, 1048576] != [0, 16045690981097406464, 1048576] First differing element 0: 16045690981097406464 0 Second list contains 1 additional elements. First extra element 2: 1048576 - [16045690981097406464, 1048576] + [0, 16045690981097406464, 1048576] ? +++ == FAIL: testCreate (__main__.PyLibfdtSwTests.testCreate) -- Traceback (most recent call last): File "/<>/tests/./pylibfdt_tests.py", line 585, in testCreate self.assertEqual([TEST_ADDR_1, TEST_SIZE_1], fdt.get_mem_rsv(0)) AssertionError: Lists differ: [9223372036854775808, 1048576] != [0, 9223372036854775808, 1048576] First differing element 0: 9223372036854775808 0 Second list contains 1 additional elements. First extra element 2: 1048576 - [9223372036854775808, 1048576] + [0, 9223372036854775808, 1048576] ? +++ -- Ran 39 tests in 0.005s FAILED (failures=2) ** TEST SUMMARY * Total testcases: 2100 *PASS: 2098 *FAIL: 0 * Bad configuration: 0 * Strange test result: 0 ** make[1]: *** [tests/Makefile.tests:89: check] Error 1 make[1]: Leaving directory '/<>' --- End Message --- --- Begin Message --- Source: device-tree-compiler Source-Version: 1.7.0-2 Done: Héctor Orón Martínez We believe that the bug you reported is fixed in the latest version of device-tree-compiler, 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 1061...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Héctor Orón Martínez (supplier of updated device-tree-compiler 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, 30 Jan 2024 17:49:08 +0100 Source: device-tree-compiler Architecture: source Version: 1.7.0-2 Distribution: unstable Urgency: medium Maintainer: Héctor Orón Martínez Changed-By: Héctor Orón Martínez Closes: 1061318 Changes: device-tree-compiler (1.7.0-2) unstable; urgency=medium . * debian/patches/fix-tests-for-Python3.12.patch: new patch (Closes: #1061318) Checksums-Sha1: 7ba686126cdd72c7a7a6c15f292e904b16d2c289 2458 device-tree-compiler_1.7.0-2.dsc 869a126a96028df7bd2cd967a52816f465730803 14400 device-tree-compiler_1.7.0-2.debian.tar.xz 8ad11b8a9177d49cdc9cd7a10954948b9825d413 9855 device-tree-compiler_1.7.0-2_source.buildinfo Checksums-Sha256: caf7b2345cd150cfdd42c630b838aa770c2f2ed1adeecda870eb55eac4d3e2e5 2458 device-tree-compiler_1.7.0-2.dsc e1488fae5b87911fc2fb5c1e888baabbac147888e528b60e66ffed68ef1e2747 14400 device-tree-compiler_1.7.0-2.debian.tar.xz 5dd1cb5d39193799eee9acc1a2dd6a24133c6b3f256765576e7ea25bce1eca22 9855 device-tree-compiler_1.7.0-2_source.buildinfo Files: 1e34dbfe8df03545f88127334b9a6901 2458 devel optional device-tree-compiler_1.7.0-2.dsc 6852c908e40120843b424fea6039 14400 devel optional
Bug#1061312: marked as done (mypaint ftbfs with Python 3.12 as the default)
Your message dated Tue, 30 Jan 2024 17:12:30 +
with message-id
and subject line Bug#1061312: fixed in mypaint 2.0.1-10
has caused the Debian Bug report #1061312,
regarding mypaint ftbfs with Python 3.12 as the default
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.)
--
1061312: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1061312
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:mypaint
Version: 2.0.1-9
Severity: serious
Tags: sid trixie ftbfs
User: debian-pyt...@lists.debian.org
Usertags: python3.12
with python3-defaults from experimental:
[...]
fakeroot debian/rules clean
dh clean --buildsystem=pybuild
dh_auto_clean -O--buildsystem=pybuild
pybuild --clean -i python{version} -p 3.12
I: pybuild base:305: python3.12 setup.py clean
Traceback (most recent call last):
File "/<>/setup.py", line 17, in
from distutils.command.build import build
ModuleNotFoundError: No module named 'distutils'
E: pybuild pybuild:391: clean: plugin distutils failed with: exit
code=1: python3.12 setup.py clean
--- End Message ---
--- Begin Message ---
Source: mypaint
Source-Version: 2.0.1-10
Done: Boyuan Yang
We believe that the bug you reported is fixed in the latest version of
mypaint, 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 1061...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Boyuan Yang (supplier of updated mypaint 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, 30 Jan 2024 01:08:47 -0500
Source: mypaint
Architecture: source
Version: 2.0.1-10
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Team
Changed-By: Boyuan Yang
Closes: 1061312
Changes:
mypaint (2.0.1-10) unstable; urgency=medium
.
* Team upload.
* debian/patches/0002-Handle-python3-distutils-removal.patch:
Add temp patch to avoid using python3-distutils, which is no longer
available with python3.12. (Closes: #1061312)
* debian/control: Drop python3-distutils usage.
* debian/rules:
+ Drop commands about python2.
+ Drop commands about distutils.
Checksums-Sha1:
34fc464cbf2272f802e9d7f9806d8d7cac7f8451 2372 mypaint_2.0.1-10.dsc
454fda6f35f382454b4e01f7555be1aa0f6a8a41 7295048 mypaint_2.0.1.orig.tar.xz
712447c3840e374504d8d009cb98df10b006cffc 21468 mypaint_2.0.1-10.debian.tar.xz
d12e1052059cc865b90d5a539577c8e617d30cea 17809 mypaint_2.0.1-10_amd64.buildinfo
Checksums-Sha256:
59f79fc0c8fe4bf7c438436ebc0ad5c5f3fab70342be9d38f5a1c60ce0856f9b 2372
mypaint_2.0.1-10.dsc
f3e437d7cdd5fd28ef6532e8ab6b4b05d842bcdd644f16a0162dad3d8e57bb16 7295048
mypaint_2.0.1.orig.tar.xz
5e49a36a25a2f7081a9bbf459726326c53f85d372b9d2e681e8d9af039d871e4 21468
mypaint_2.0.1-10.debian.tar.xz
20e60fb74351c05e6a1f9c9565b0120eea315abc8acde1b6bfb0c4af3ea67f58 17809
mypaint_2.0.1-10_amd64.buildinfo
Files:
2320d2c88b8274b7216aaa333284bc73 2372 graphics optional mypaint_2.0.1-10.dsc
dc9abd2e9da8477cbad55905ed07a46a 7295048 graphics optional
mypaint_2.0.1.orig.tar.xz
8d9068e7b3d8b96149fa2e39b92bdb4c 21468 graphics optional
mypaint_2.0.1-10.debian.tar.xz
935d5cace2f62f389cc961bec92b0a5d 17809 graphics optional
mypaint_2.0.1-10_amd64.buildinfo
-BEGIN PGP SIGNATURE-
iQIzBAEBCgAdFiEEfncpR22H1vEdkazLwpPntGGCWs4FAmW5KKUACgkQwpPntGGC
Ws540A//QT9HGJXGqr2iWrDK82S4TXob/A1SvxzOOg8MefAXbMuri1V1qRANZkoo
Z1n7ojrehmP2Fonqt5GbEEBBBH0przN7CWeQ9UI7ac389s2L/jsJ4xb8AAIWqKIQ
XU4dB9wcKd/YcU2pnEB08Vl/qpY1EAtZ+8EYZtTzvR4WZkJCz39To19ZaKEC3s9g
vBOqzwpLnQkOW6mA9SUMXK2QJoXiD2zNoQIIgYZwysDWScXSd3tYQ022Z8S7U+i/
1cCZu+ixBeDlQR7NUWjSVUszzQrLvwPvvxK5jG6/Z2OnMI9akQakQU4kRD2tXLfm
f2nf09hViK48NqvoaQSgIvYHueA9AmUsDdU2U6Jc5do9oqXHEe+hewFp1V/yeghr
zDa7KBg4pw5/mEUPVtS29NwzXaXfNrHuLgm+JTh/5fnMSegkU4bPrN6XdvMECkwG
C1E+dOuHqTcHVZFZaPhawOrhgfeBBt4Nnx5IOxJXx3Kavn7aj3gx8VchmKo7+SHf
GoUHVzgBGcR0LTF/yrjRq3VeJOa+o3vEB4xRv7Lxa8eVllV868uOxFsNedJjBczM
Q41IRzUytJJlwAGynmb3DGwbtM7Xja3cbQ5nvF81TyUnNNRN68zRXiX386ea9n71
y8lVmEO/iXTeLARWu/lqv0xK4CekqQMPgQ10Y87t9Cc2LkWmNTY=
=dkP3
-END PGP SIGNATURE End Message ---
Bug#1048362: marked as done (q2-taxa: Fails to build source after successful build)
Your message dated Tue, 30 Jan 2024 16:54:01 + with message-id and subject line Bug#1048362: fixed in q2-taxa 2023.9.0+dfsg-1 has caused the Debian Bug report #1048362, regarding q2-taxa: Fails to build source after successful 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.) -- 1048362: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1048362 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: q2-taxa Version: 2022.11.1+dfsg-2 Severity: minor Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-sab-20230813 ftbfs-source-after-build User: debian...@lists.debian.org Usertags: qa-doublebuild Hi, This package fails to build a source package after a successful build (dpkg-buildpackage ; dpkg-buildpackage -S). This is probably a clear violation of Debian Policy section 4.9 (clean target), but this is filed as severity:minor for now, because a discussion on debian-devel showed that we might want to revisit the requirement of a working 'clean' target. More information about this class of issues, included common problems and solutions, is available at https://wiki.debian.org/qa.debian.org/FTBFS/SourceAfterBuild Relevant part of the build log: > cd /<> && runuser -u user42 -- dpkg-buildpackage --sanitize-env > -us -uc -rfakeroot -S > -- > > dpkg-buildpackage: info: source package q2-taxa > dpkg-buildpackage: info: source version 2022.11.1+dfsg-2 > dpkg-buildpackage: info: source distribution unstable > dpkg-buildpackage: info: source changed by Andreas Tille > dpkg-source --before-build . > debian/rules clean > dh clean --with python3 --buildsystem=pybuild >debian/rules override_dh_auto_clean > make[1]: Entering directory '/<>' > dh_auto_clean > I: pybuild base:275: python3.11 setup.py clean > running clean > removing '/<>/.pybuild/cpython3_3.11/build' (and everything > under it) > 'build/bdist.linux-x86_64' does not exist -- can't clean it > 'build/scripts-3.11' does not exist -- can't clean it > rm -f q2_taxa.egg-info/PKG-INFO q2_taxa.egg-info/SOURCES.txt > q2_taxa.egg-info/dependency_links.txt q2_taxa.egg-info/entry_points.txt > q2_taxa.egg-info/not-zip-safe q2_taxa.egg-info/top_level.txt > make[1]: Leaving directory '/<>' >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 q2-taxa using existing > ./q2-taxa_2022.11.1+dfsg.orig.tar.xz > dpkg-source: info: using patch list from debian/patches/series > dpkg-source: warning: file > q2-taxa-2022.11.1+dfsg/q2_taxa/assets/barplot/dist/bundle.js has no final > newline (either original or modified version) > dpkg-source: info: local changes detected, the modified files are: > q2-taxa-2022.11.1+dfsg/q2_taxa/assets/barplot/dist/bundle.js > q2-taxa-2022.11.1+dfsg/q2_taxa/assets/barplot/dist/bundle.js.LICENSE.txt > dpkg-source: error: aborting due to unexpected upstream changes, see > /tmp/q2-taxa_2022.11.1+dfsg-2.diff.Qy5evj > dpkg-source: info: Hint: make sure the version in debian/changelog matches > the unpacked source tree > dpkg-source: info: you can integrate the local changes with dpkg-source > --commit > dpkg-buildpackage: error: dpkg-source -b . subprocess returned exit status 2 > > E: Command 'cd /<> && runuser -u user42 -- dpkg-buildpackage > --sanitize-env -us -uc -rfakeroot -S' failed to run. The full build log is available from: http://qa-logs.debian.net/2023/08/13/q2-taxa_2022.11.1+dfsg-2_unstable.log If you reassign this bug to another package, please mark it as 'affects'-ing this package. See https://www.debian.org/Bugs/server-control#affects If you fail to reproduce this, please provide a build log and diff it with mine so that we can identify if something relevant changed in the meantime. --- End Message --- --- Begin Message --- Source: q2-taxa Source-Version: 2023.9.0+dfsg-1 Done: Andreas Tille We believe that the bug you reported is fixed in the latest version of q2-taxa, 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 1048...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Andreas Tille (supplier of updated q2-taxa package) (This message was
Bug#1061854: marked as done (shishi: install PAM module into /usr)
Your message dated Tue, 30 Jan 2024 16:40:49 + with message-id and subject line Bug#1061854: fixed in shishi 1.0.3-2 has caused the Debian Bug report #1061854, regarding shishi: install PAM module into /usr 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.) -- 1061854: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1061854 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: shishi Version: 1.0.3-1 Severity: normal Tags: patch User: helm...@debian.org Usertags: dep17m2 We want to finalize the /usr-merge via DEP17 by moving all files to /usr. shishi installs files into /lib these should be moved into the respective canonical locations in /usr/. Please find a patch attached. It has been build-tested. Note: this should not be backported to bookworm. If you intend to backport, please use dh_movetousr instead. If your package will change for the t64 transition or otherwise rename/split/move its binaries (packages) during trixie, please then upload to experimental and get in touch with the UsrMerge driver, please see the wiki [1]. Michael [1] https://wiki.debian.org/UsrMerge diff -Nru shishi-1.0.3/debian/changelog shishi-1.0.3/debian/changelog --- shishi-1.0.3/debian/changelog 2022-08-07 18:29:29.0 +0200 +++ shishi-1.0.3/debian/changelog 2024-01-29 22:16:26.0 +0100 @@ -1,3 +1,10 @@ +shishi (1.0.3-1.1) UNRELEASED; urgency=medium + + * Non-maintainer upload. + * Install PAM module into /usr. (Closes: #-1) + + -- Michael Biebl Mon, 29 Jan 2024 22:16:26 +0100 + shishi (1.0.3-1) unstable; urgency=medium * New upstream version 1.0.3 diff -Nru shishi-1.0.3/debian/libpam-shishi.install shishi-1.0.3/debian/libpam-shishi.install --- shishi-1.0.3/debian/libpam-shishi.install 2022-08-07 04:17:31.0 +0200 +++ shishi-1.0.3/debian/libpam-shishi.install 2024-01-29 22:13:13.0 +0100 @@ -1 +1 @@ -lib/*/security/pam_shishi.so +usr/lib/*/security/pam_shishi.so diff -Nru shishi-1.0.3/debian/not-installed shishi-1.0.3/debian/not-installed --- shishi-1.0.3/debian/not-installed 2022-08-07 12:33:13.0 +0200 +++ shishi-1.0.3/debian/not-installed 2024-01-29 22:16:26.0 +0100 @@ -1,2 +1,2 @@ usr/lib/*/*.la -lib/*/security/pam_shishi.la +usr/lib/*/security/pam_shishi.la diff -Nru shishi-1.0.3/debian/rules shishi-1.0.3/debian/rules --- shishi-1.0.3/debian/rules 2022-08-07 10:06:48.0 +0200 +++ shishi-1.0.3/debian/rules 2024-01-29 22:13:07.0 +0100 @@ -21,7 +21,7 @@ CONFIGURE_FLAGS = \ --disable-rpath \ --with-db-dir=/var/lib/shishi \ - --with-pam-dir=/lib/$(DEB_HOST_MULTIARCH)/security \ + --with-pam-dir=/usr/lib/$(DEB_HOST_MULTIARCH)/security \ --with-packager=Debian \ --with-packager-version=$(DEB_VERSION) \ --with-packager-bug-reports=https://bugs.debian.org/ --- End Message --- --- Begin Message --- Source: shishi Source-Version: 1.0.3-2 Done: Simon Josefsson We believe that the bug you reported is fixed in the latest version of shishi, 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 1061...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Simon Josefsson (supplier of updated shishi 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, 30 Jan 2024 17:09:13 +0100 Source: shishi Architecture: source Version: 1.0.3-2 Distribution: unstable Urgency: medium Maintainer: Debian Shishi Team Changed-By: Simon Josefsson Closes: 1061854 Changes: shishi (1.0.3-2) unstable; urgency=medium . [ Simon Josefsson ] * Bump Standards-Version: to 4.6.2. * Build-Depend on libidn-dev not libidn11-dev. * Use valgrind [amd64] due to #1061496, #1057693 and similar problems. * Bump d/copyright year. . [ Michael Biebl ] * Install PAM module into /usr. (Closes: #1061854) Checksums-Sha1: 9626a10cd6885176ef1cd02075160c151a1249f6 2290 shishi_1.0.3-2.dsc 2978f8a5b52f6be448293556d8d7317c31d04c7f 22748 shishi_1.0.3-2.debian.tar.xz 8b2cbd1d3651f5cfd198773e046eef7e155e337f 14615 shishi_1.0.3-2_amd64.buildinfo Checksums-Sha256:
Bug#1055515: marked as done (ldc: diff for NMU version 1:1.35.0-1.1)
Your message dated Tue, 30 Jan 2024 16:23:38 + with message-id and subject line Bug#1055515: fixed in ldc 1:1.35.0-1.1 has caused the Debian Bug report #1055515, regarding ldc: diff for NMU version 1:1.35.0-1.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.) -- 1055515: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1055515 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: ldc Version: 1:1.35.0-1 Severity: normal Tags: patch Dear maintainer, I found the application FTBFS if bash-completion is installed due to a wrong check and assumption about its presence on CMakeLists.txt. I propose to add the dependency and let cmake do the correct job, resulting in a simplification of install target diff -Nru ldc-1.35.0/debian/changelog ldc-1.35.0/debian/changelog --- ldc-1.35.0/debian/changelog 2023-11-04 18:40:54.0 +0100 +++ ldc-1.35.0/debian/changelog 2023-11-07 16:15:22.0 +0100 @@ -1,3 +1,9 @@ +ldc (1:1.35.0-1.1) unstable; urgency=medium + + * Add bash-completion dependency to let cmake helper do the right job (Closes: #-1) + + -- Gianfranco Costamagna Tue, 07 Nov 2023 16:15:22 +0100 + ldc (1:1.35.0-1) unstable; urgency=medium [ Matthias Klumpp ] diff -Nru ldc-1.35.0/debian/control ldc-1.35.0/debian/control --- ldc-1.35.0/debian/control 2023-11-04 18:40:54.0 +0100 +++ ldc-1.35.0/debian/control 2023-11-07 16:15:22.0 +0100 @@ -4,7 +4,8 @@ Maintainer: Debian D Language Group Uploaders: Konstantinos Margaritis , Matthias Klumpp -Build-Depends: cmake, +Build-Depends: bash-completion, + cmake, debhelper-compat (= 12), dh-exec, gdmd, diff -Nru ldc-1.35.0/debian/ldc.install ldc-1.35.0/debian/ldc.install --- ldc-1.35.0/debian/ldc.install 2022-08-12 18:36:13.0 +0200 +++ ldc-1.35.0/debian/ldc.install 2023-11-07 16:15:20.0 +0100 @@ -1,4 +1,4 @@ -etc/bash_completion.d/*usr/share/bash-completion/completions/ +usr/share/bash-completion/completions/ etc/ldc2.conf usr/bin/* usr/lib/ldc_rt.dso.o OpenPGP_signature.asc Description: OpenPGP digital signature --- End Message --- --- Begin Message --- Source: ldc Source-Version: 1:1.35.0-1.1 Done: Gianfranco Costamagna We believe that the bug you reported is fixed in the latest version of ldc, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 1055...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Gianfranco Costamagna (supplier of updated ldc 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, 07 Nov 2023 16:15:22 +0100 Source: ldc Built-For-Profiles: noudeb Architecture: source Version: 1:1.35.0-1.1 Distribution: unstable Urgency: medium Maintainer: Debian D Language Group Changed-By: Gianfranco Costamagna Closes: 1055515 Changes: ldc (1:1.35.0-1.1) unstable; urgency=medium . * Non-maintainer upload * Add bash-completion dependency to let cmake helper do the right job (Closes: #1055515) Checksums-Sha1: e6879546aebfc6e3cce4f671035256a5f4fdd020 2333 ldc_1.35.0-1.1.dsc cadb4539881824bf39b1e44a1ed9b8b90db6892f 19588 ldc_1.35.0-1.1.debian.tar.xz 44757942db10f2a1e154c94305ff6fb494f81674 9237 ldc_1.35.0-1.1_source.buildinfo Checksums-Sha256: a4d66d3fdd9f7e82ea3daaa1771698b2e34872f2aae4462de95e1f7647d0e445 2333 ldc_1.35.0-1.1.dsc 08f950f2fd57149818a9c85ea5dbaa20d1c05ed282899cb384deffbe7d377d63 19588 ldc_1.35.0-1.1.debian.tar.xz eff0f909641e9b8a0a5bbbdaade48187514a3d9b504eb4b43985180408032323 9237 ldc_1.35.0-1.1_source.buildinfo Files: 19bb3e7a0ac9ec50229be09bc178fc74 2333 devel optional ldc_1.35.0-1.1.dsc 5472f28d02b3f433cf252a126594fb8c 19588 devel optional ldc_1.35.0-1.1.debian.tar.xz db1cdb0d0e3c68c42b9b8bc4809df575 9237 devel optional ldc_1.35.0-1.1_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEEkpeKbhleSSGCX3/w808JdE6fXdkFAmWlSzwACgkQ808JdE6f XdnrjRAAgyFe8u2Imcf5aEB0D2wifNqK1x4DscdusOeDoK3Gv+PK/3sseF2dV+xA q/FKJZT9rus8VMIg8yyfHGH6GHdcjoqViMeYrqqo5KJkrJs0SJ5rRwotGBKpfwbQ VtkD5mjH2TFlGlmhoSgiJSaCvGUyYwp0N5y3A3xvgWeCvlIjXIdqPs46yZLtrGKN
Bug#1049550: marked as done (terraphast: Fails to build binary packages again after successful build)
Your message dated Tue, 30 Jan 2024 16:25:14 + with message-id and subject line Bug#1049550: fixed in terraphast 0.0+git20200413.8af2e4c+dfsg-3 has caused the Debian Bug report #1049550, regarding terraphast: Fails to build binary packages again after successful 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.) -- 1049550: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1049550 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: terraphast Version: 0.0+git20200413.8af2e4c+dfsg-2 Severity: minor Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-binary-20230816 ftbfs-binary-after-build User: debian...@lists.debian.org Usertags: qa-doublebuild Hi, This package fails to do build a binary-only build (not source) after a successful build (dpkg-buildpackage ; dpkg-buildpackage -b). This is probably a clear violation of Debian Policy section 4.9 (clean target), but this is filed as severity:minor for now, because a discussion on debian-devel showed that we might want to revisit the requirement of a working 'clean' target. More information about this class of issues, included common problems and solutions, is available at https://wiki.debian.org/qa.debian.org/FTBFS/DoubleBuild Relevant part of the build log: > cd /<> && runuser -u user42 -- dpkg-buildpackage --sanitize-env > -us -uc -rfakeroot -b > -- > > dpkg-buildpackage: info: source package terraphast > dpkg-buildpackage: info: source version 0.0+git20200413.8af2e4c+dfsg-2 > dpkg-buildpackage: info: source distribution unstable > dpkg-buildpackage: info: source changed by Nilesh Patra > dpkg-source --before-build . > dpkg-buildpackage: info: host architecture amd64 > debian/rules clean > dh clean >dh_auto_clean >dh_clean > debian/rules binary > dh binary >dh_update_autotools_config >dh_autoreconf >debian/rules override_dh_auto_configure > make[1]: Entering directory '/<>' > dh_auto_configure -- \ > -DVERSION="0.0" \ > -DSOVERSION="0" \ > -DTERRAPHAST_ARCH_NATIVE=OFF > cd obj-x86_64-linux-gnu && cmake -DCMAKE_INSTALL_PREFIX=/usr > -DCMAKE_BUILD_TYPE=None -DCMAKE_INSTALL_SYSCONFDIR=/etc > -DCMAKE_INSTALL_LOCALSTATEDIR=/var -DCMAKE_EXPORT_NO_PACKAGE_REGISTRY=ON > -DCMAKE_FIND_USE_PACKAGE_REGISTRY=OFF > -DCMAKE_FIND_PACKAGE_NO_PACKAGE_REGISTRY=ON > -DFETCHCONTENT_FULLY_DISCONNECTED=ON -DCMAKE_INSTALL_RUNSTATEDIR=/run > -DCMAKE_SKIP_INSTALL_ALL_DEPENDENCY=ON "-GUnix Makefiles" > -DCMAKE_VERBOSE_MAKEFILE=ON -DCMAKE_INSTALL_LIBDIR=lib/x86_64-linux-gnu > -DVERSION=0.0 -DSOVERSION=0 -DTERRAPHAST_ARCH_NATIVE=OFF .. > CMake Warning (dev) at CMakeLists.txt:1 (project): > cmake_minimum_required() should be called prior to this top-level project() > call. Please see the cmake-commands(7) manual for usage documentation of > both commands. > This warning is for project developers. Use -Wno-dev to suppress it. > > -- The C compiler identification is GNU 13.2.0 > -- The CXX compiler identification is GNU 13.2.0 > -- Detecting C compiler ABI info > -- Detecting C compiler ABI info - done > -- Check for working C compiler: /usr/bin/cc - skipped > -- Detecting C compile features > -- Detecting C compile features - done > -- Detecting CXX compiler ABI info > -- Detecting CXX compiler ABI info - done > -- Check for working CXX compiler: /usr/bin/c++ - skipped > -- Detecting CXX compile features > -- Detecting CXX compile features - done > CMake Deprecation Warning at CMakeLists.txt:3 (cmake_minimum_required): > Compatibility with CMake < 3.5 will be removed from a future version of > CMake. > > Update the VERSION argument value or use a ... suffix to tell > CMake that the project does not need compatibility with older versions. > > > -- Found GMP: /usr/include/x86_64-linux-gnu > -- GMP libraries found > -- clang-tidy not found. > -- Configuring done (0.9s) > CMake Error at CMakeLists.txt:77 (add_library): > Cannot find source file: > > include/terraces/advanced.hpp > > Tried extensions .c .C .c++ .cc .cpp .cxx .cu .mpp .m .M .mm .ixx .cppm > .ccm .cxxm .c++m .h .hh .h++ .hm .hpp .hxx .in .txx .f .F .for .f77 .f90 > .f95 .f03 .hip .ispc > > > CMake Error at CMakeLists.txt:77 (add_library): > No SOURCES given to target: terraces_static > > > CMake Error at CMakeLists.txt:78 (add_library): > No SOURCES given to target: terraces > > > CMake Generate step failed. Build files cannot be
Bug#1053945: marked as done (seaborn: test failure with pandas 2.1)
Your message dated Tue, 30 Jan 2024 16:09:25 + with message-id and subject line Bug#1053945: fixed in seaborn 0.13.2-1 has caused the Debian Bug report #1053945, regarding seaborn: test failure with pandas 2.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.) -- 1053945: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1053945 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:seaborn Version: 0.12.2-1 Control: block 1043240 by -1 seaborn fails its tests with pandas 2.1, currently in experimental. Logs: https://ci.debian.net/data/autopkgtest/unstable/amd64/s/seaborn/38997875/log.gz https://launchpad.net/~rebecca-palmer/+archive/ubuntu/pandas2p1/+build/26770797/+files/buildlog_ubuntu-mantic-amd64.seaborn_0.12.2-1_BUILDING.txt.gz A common source of failures is new pandas FutureWarnings in tests that are set to fail on unexpected warnings. --- End Message --- --- Begin Message --- Source: seaborn Source-Version: 0.13.2-1 Done: Nilesh Patra We believe that the bug you reported is fixed in the latest version of seaborn, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 1053...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Nilesh Patra (supplier of updated seaborn 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, 30 Jan 2024 20:55:35 +0530 Source: seaborn Architecture: source Version: 0.13.2-1 Distribution: unstable Urgency: medium Maintainer: Debian Science Maintainers Changed-By: Nilesh Patra Closes: 1053945 Changes: seaborn (0.13.2-1) unstable; urgency=medium . * New upstream version 0.13.2 (Closes: #1053945) Checksums-Sha1: 3b7c0cccf2e312701aff1fc20e743a605ff8eb8d 1726 seaborn_0.13.2-1.dsc 9a35743ff4252edadeee5027cfab1ee74ba5ca1c 1912495 seaborn_0.13.2.orig.tar.gz 8ae403d5f8fc50d1143ec48691bcc344846f363f 5612 seaborn_0.13.2-1.debian.tar.xz da073577160abd90b019aa9da6bc4b5698c62179 10477 seaborn_0.13.2-1_amd64.buildinfo Checksums-Sha256: f375e2f0768d308bb52710150cb09724bbe4fadcc04f0e1fcf0d20ea45b63661 1726 seaborn_0.13.2-1.dsc f95141106bf1815246a3108055405c7ffe27ed69687fb3c21c754c2a7a5781c7 1912495 seaborn_0.13.2.orig.tar.gz 48176fd9689058cf64456e71114a2fe911cbbe05b94a9de6f7c1bc0f3c506b4d 5612 seaborn_0.13.2-1.debian.tar.xz 683b17b5dff4251187915c5a56636cdf3639c1d163d709fa075beee75b199ad6 10477 seaborn_0.13.2-1_amd64.buildinfo Files: 4fbfa092f73ba3656449d7c2f5a26a03 1726 python optional seaborn_0.13.2-1.dsc 75f99a7a5724f231d13fb27ac47c226b 1912495 python optional seaborn_0.13.2.orig.tar.gz 9aecb4e97fcd6cdc628800b46c97180a 5612 python optional seaborn_0.13.2-1.debian.tar.xz 27ce10f9558fb78a09034d3db3e99c99 10477 python optional seaborn_0.13.2-1_amd64.buildinfo -BEGIN PGP SIGNATURE- iHUEARYIAB0WIQSglbZu4JAkvuai8HIqJ5BL1yQ+2gUCZbkZugAKCRAqJ5BL1yQ+ 2oZhAP9nLhbv5ntd/ytlSAMUb/hYkwztoSu4uylOq3D22OQK7AEA6SiBq2S7clmS 8s/n43h2Z8WY7bsCZ0K2LdgUDD1hFQg= =3TYG -END PGP SIGNATURE End Message ---
Processed: RFS: streamlink/6.5.1-1~bpo12+1 -- CLI for extracting video streams from various websites to a video player
Processing commands for cont...@bugs.debian.org: > close 1061819 Bug #1061819 [sponsorship-requests] RFS: streamlink/6.5.1-1~bpo12+1 -- CLI for extracting video streams from various websites to a video player Marked Bug as done > stop Stopping processing here. Please contact me if you need assistance. -- 1061819: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1061819 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1061948: marked as done (precious - upcoming rust-toml-update)
Your message dated Tue, 30 Jan 2024 15:38:38 + with message-id and subject line Bug#1061948: fixed in precious 0.6.0-3 has caused the Debian Bug report #1061948, regarding precious - upcoming rust-toml-update 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.) -- 1061948: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1061948 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: precious Version: 0.6.0-2 I plan to update rust-toml to 0.8 soon, to accommodate this, precious will need a patch dropping and an update to it's build-dependencies. Since this is moving closer to what upstream wants I see it as low risk. I have tested that the package builds succesfully with the changes in question. If you want to do further testing, the new version of toml is available in experimental. diff -Nru precious-0.6.0/debian/changelog precious-0.6.0/debian/changelog --- precious-0.6.0/debian/changelog 2023-12-19 20:56:31.0 + +++ precious-0.6.0/debian/changelog 2024-01-30 08:22:29.0 + @@ -1,3 +1,11 @@ +precious (0.6.0-2.1) UNRELEASED; urgency=medium + + * Non-maintainer upload. + * Bump toml build-dependency to use 0.8. + * Drop patch 2001_toml.patch + + -- Peter Michael Green Tue, 30 Jan 2024 08:22:29 + + precious (0.6.0-2) unstable; urgency=medium * drop patches 2001_anyhow 2001_rayon 2001_serde, diff -Nru precious-0.6.0/debian/control precious-0.6.0/debian/control --- precious-0.6.0/debian/control 2023-09-20 23:10:32.0 + +++ precious-0.6.0/debian/control 2024-01-30 08:22:29.0 + @@ -37,7 +37,7 @@ librust-tempfile-3+default-dev (>= 3.3) , librust-test-case-3+default-dev , librust-thiserror-1+default-dev (>= 1.0.37), - librust-toml-0.7+default-dev, + librust-toml-0.8+default-dev, librust-which+default-dev (<< 5), libstring-shellquote-perl, Standards-Version: 4.6.2 diff -Nru precious-0.6.0/debian/patches/2001_toml.patch precious-0.6.0/debian/patches/2001_toml.patch --- precious-0.6.0/debian/patches/2001_toml.patch 2023-12-19 20:56:31.0 + +++ precious-0.6.0/debian/patches/2001_toml.patch 1970-01-01 00:00:00.0 + @@ -1,18 +0,0 @@ -Description: accept older branch of crate toml -Author: Jonas Smedegaard -Bug-Debian: https://bugs.debian.org/1053955 -Forwarded: not-needed -Last-Update: 2023-12-19 -This patch header follows DEP-3: http://dep.debian.net/deps/dep3/ a/Cargo.toml -+++ b/Cargo.toml -@@ -52,7 +52,7 @@ - tempfile = "3.8.0" - test-case = "3.2.1" - thiserror = "1.0.49" --toml = "0.8.2" -+toml = ">= 0.7.6, <= 0.8.2" - which = ">= 3.0.0, < 5.0.0" - - [workspace] diff -Nru precious-0.6.0/debian/patches/series precious-0.6.0/debian/patches/series --- precious-0.6.0/debian/patches/series2023-11-28 23:56:05.0 + +++ precious-0.6.0/debian/patches/series2024-01-30 08:22:29.0 + @@ -1,4 +1,3 @@ 2001_comfy-table.patch 2001_indexmap.patch -2001_toml.patch 2002_privacy.patch --- End Message --- --- Begin Message --- Source: precious Source-Version: 0.6.0-3 Done: Jonas Smedegaard We believe that the bug you reported is fixed in the latest version of precious, 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 1061...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Jonas Smedegaard (supplier of updated precious 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, 30 Jan 2024 15:43:30 +0100 Source: precious Architecture: source Version: 0.6.0-3 Distribution: unstable Urgency: medium Maintainer: Jonas Smedegaard Changed-By: Jonas Smedegaard Closes: 1061948 Changes: precious (0.6.0-3) unstable; urgency=medium . * update patch 2001_toml; relax build-dependency for crate toml; closes: bug#1061948, thanks to Peter Green Checksums-Sha1: 8d1dde994582f6cf0425c234123a3102f1ed5617 3048 precious_0.6.0-3.dsc d3805260587ce0d45e58742a369aa383bd722962 29624 precious_0.6.0-3.debian.tar.xz fcd6c4876a3d8268339584c891b82e4eed1a0736 18160 precious_0.6.0-3_amd64.buildinfo Checksums-Sha256:
Bug#1061714: marked as done (oath-toolkit: install PAM module into /usr)
Your message dated Tue, 30 Jan 2024 15:38:30 + with message-id and subject line Bug#1061714: fixed in oath-toolkit 2.6.11-2 has caused the Debian Bug report #1061714, regarding oath-toolkit: install PAM module into /usr 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.) -- 1061714: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1061714 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: oath-toolkit Version: 2.6.11-1 Severity: normal Tags: patch User: helm...@debian.org Usertags: dep17m2 We want to finalize the /usr-merge via DEP17 by moving all files to /usr. oath-toolkit installs files into /lib; these should be moved into the respective canonical locations in /usr/. Please find a patch attached. It has been build-tested. Note: this should not be backported to bookworm. If you intend to backport, please use dh_movetousr instead. If your package will change for the t64 transition or otherwise rename/split/move its binaries (packages) during trixie, please then upload to experimental and get in touch with the UsrMerge driver, please see the wiki [1]. Michael [1] https://wiki.debian.org/UsrMerge diff -Nru oath-toolkit-2.6.11/debian/changelog oath-toolkit-2.6.11/debian/changelog --- oath-toolkit-2.6.11/debian/changelog2024-01-11 09:27:56.0 +0100 +++ oath-toolkit-2.6.11/debian/changelog2024-01-29 00:30:56.0 +0100 @@ -1,3 +1,10 @@ +oath-toolkit (2.6.11-1.1) UNRELEASED; urgency=medium + + * Non-maintainer upload. + * Install PAM module into /usr. (Closes: #-1) + + -- Michael Biebl Mon, 29 Jan 2024 00:30:56 +0100 + oath-toolkit (2.6.11-1) unstable; urgency=medium * New upstream version 2.6.11 diff -Nru oath-toolkit-2.6.11/debian/libpam-oath.install oath-toolkit-2.6.11/debian/libpam-oath.install --- oath-toolkit-2.6.11/debian/libpam-oath.install 2024-01-11 09:15:28.0 +0100 +++ oath-toolkit-2.6.11/debian/libpam-oath.install 2024-01-29 00:30:49.0 +0100 @@ -1 +1 @@ -lib/*/security/pam_oath.so +usr/lib/*/security/pam_oath.so diff -Nru oath-toolkit-2.6.11/debian/rules oath-toolkit-2.6.11/debian/rules --- oath-toolkit-2.6.11/debian/rules2024-01-11 09:15:28.0 +0100 +++ oath-toolkit-2.6.11/debian/rules2024-01-29 00:30:34.0 +0100 @@ -16,7 +16,7 @@ dh_auto_configure -- \ --disable-rpath \ --disable-gtk-doc \ - --with-pam-dir=/lib/$(DEB_HOST_MULTIARCH)/security + --with-pam-dir=/usr/lib/$(DEB_HOST_MULTIARCH)/security override_dh_auto_install: dh_auto_install --- End Message --- --- Begin Message --- Source: oath-toolkit Source-Version: 2.6.11-2 Done: Simon Josefsson We believe that the bug you reported is fixed in the latest version of oath-toolkit, 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 1061...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Simon Josefsson (supplier of updated oath-toolkit 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, 30 Jan 2024 15:58:17 +0100 Source: oath-toolkit Architecture: source Version: 2.6.11-2 Distribution: unstable Urgency: medium Maintainer: OATH Toolkit Team Changed-By: Simon Josefsson Closes: 1061714 Changes: oath-toolkit (2.6.11-2) unstable; urgency=medium . [ Michael Biebl ] * Install PAM module into /usr. (Closes: #1061714) Checksums-Sha1: fb8e27a23a5cb1d45cc7e5f2c4087bcfe29afe0f 2096 oath-toolkit_2.6.11-2.dsc 720c1974962dce2901cd4e8a63150fca455f76a4 13148 oath-toolkit_2.6.11-2.debian.tar.xz a9cb01a0281be000c8a27ed47d499147fc77edbf 9727 oath-toolkit_2.6.11-2_amd64.buildinfo Checksums-Sha256: cf4a2d58abd5539fad3786139d17506a99bd37bd4726c2c91c084d80a16d4612 2096 oath-toolkit_2.6.11-2.dsc a603f4daff921b988200efd2ff67e4b287db02b085cbbd954fec93b965a06671 13148 oath-toolkit_2.6.11-2.debian.tar.xz 335a9df01a55b26e511cc09b25e0fbdc927b003e97f34698b672b95ab8aa1ed8 9727 oath-toolkit_2.6.11-2_amd64.buildinfo Files: 4f42675f22dd173d735476bb98370688 2096 devel optional oath-toolkit_2.6.11-2.dsc 1a68ecce43f41ccc097d4b2d1f60330b 13148 devel optional
Bug#1045829: marked as done (q2-demux: Fails to build source after successful build)
Your message dated Tue, 30 Jan 2024 15:39:03 + with message-id and subject line Bug#1045829: fixed in q2-demux 2023.9.1+dfsg-1 has caused the Debian Bug report #1045829, regarding q2-demux: Fails to build source after successful 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.) -- 1045829: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1045829 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: q2-demux Version: 2022.11.1+dfsg-2 Severity: minor Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-sab-20230813 ftbfs-source-after-build User: debian...@lists.debian.org Usertags: qa-doublebuild Hi, This package fails to build a source package after a successful build (dpkg-buildpackage ; dpkg-buildpackage -S). This is probably a clear violation of Debian Policy section 4.9 (clean target), but this is filed as severity:minor for now, because a discussion on debian-devel showed that we might want to revisit the requirement of a working 'clean' target. More information about this class of issues, included common problems and solutions, is available at https://wiki.debian.org/qa.debian.org/FTBFS/SourceAfterBuild Relevant part of the build log: > cd /<> && runuser -u user42 -- dpkg-buildpackage --sanitize-env > -us -uc -rfakeroot -S > > > dpkg-buildpackage: info: source package q2-demux > dpkg-buildpackage: info: source version 2022.11.1+dfsg-2 > dpkg-buildpackage: info: source distribution unstable > dpkg-buildpackage: info: source changed by Andreas Tille > dpkg-source --before-build . > debian/rules clean > dh clean --with python3 --buildsystem=pybuild >debian/rules override_dh_auto_clean > make[1]: Entering directory '/<>' > dh_auto_clean > I: pybuild base:275: python3.11 setup.py clean > running clean > removing '/<>/.pybuild/cpython3_3.11/build' (and everything > under it) > 'build/bdist.linux-x86_64' does not exist -- can't clean it > 'build/scripts-3.11' does not exist -- can't clean it > rm -f q2_demux.egg-info/PKG-INFO q2_demux.egg-info/SOURCES.txt > q2_demux.egg-info/dependency_links.txt q2_demux.egg-info/entry_points.txt > q2_demux.egg-info/not-zip-safe q2_demux.egg-info/top_level.txt > make[1]: Leaving directory '/<>' >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 q2-demux using existing > ./q2-demux_2022.11.1+dfsg.orig.tar.xz > dpkg-source: info: using patch list from debian/patches/series > dpkg-source: warning: file > q2-demux-2022.11.1+dfsg/q2_demux/_summarize/assets/dist/bundle.js has no > final newline (either original or modified version) > dpkg-source: info: local changes detected, the modified files are: > q2-demux-2022.11.1+dfsg/q2_demux/_summarize/assets/dist/bundle.js > dpkg-source: error: aborting due to unexpected upstream changes, see > /tmp/q2-demux_2022.11.1+dfsg-2.diff.xgsFON > dpkg-source: info: Hint: make sure the version in debian/changelog matches > the unpacked source tree > dpkg-source: info: you can integrate the local changes with dpkg-source > --commit > dpkg-buildpackage: error: dpkg-source -b . subprocess returned exit status 2 > > E: Command 'cd /<> && runuser -u user42 -- dpkg-buildpackage > --sanitize-env -us -uc -rfakeroot -S' failed to run. The full build log is available from: http://qa-logs.debian.net/2023/08/13/q2-demux_2022.11.1+dfsg-2_unstable.log If you reassign this bug to another package, please mark it as 'affects'-ing this package. See https://www.debian.org/Bugs/server-control#affects If you fail to reproduce this, please provide a build log and diff it with mine so that we can identify if something relevant changed in the meantime. --- End Message --- --- Begin Message --- Source: q2-demux Source-Version: 2023.9.1+dfsg-1 Done: Andreas Tille We believe that the bug you reported is fixed in the latest version of q2-demux, 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 1045...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Andreas Tille (supplier of updated q2-demux package) (This message was generated automatically at their request; if
Bug#1061961: marked as done (fyba: NMU diff for 64-bit time_t transition)
Your message dated Tue, 30 Jan 2024 15:35:46 +
with message-id
and subject line Bug#1061961: fixed in fyba 4.1.1-9~exp1
has caused the Debian Bug report #1061961,
regarding fyba: NMU diff for 64-bit time_t transition
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.)
--
1061961: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1061961
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: fyba
Version: 4.1.1-8
Severity: serious
Tags: patch pending
Justification: library ABI skew on upgrade
User: debian-...@lists.debian.org
Usertags: time-t
Dear maintainer,
As part of the 64-bit time_t transition required to support 32-bit
architectures in 2038 and beyond
(https://wiki.debian.org/ReleaseGoals/64bit-time), we have identified
fyba as a source package shipping runtime libraries whose ABI
either is affected by the change in size of time_t, or could not be
analyzed via abi-compliance-checker (and therefore to be on the safe
side we assume is affected).
To ensure that inconsistent combinations of libraries with their
reverse-dependencies are never installed together, it is necessary to
have a library transition, which is most easily done by renaming the
runtime library package.
Since turning on 64-bit time_t is being handled centrally through a change
to the default dpkg-buildflags (https://bugs.debian.org/1037136), it is
important that libraries affected by this ABI change all be uploaded close
together in time. Therefore I have prepared a 0-day NMU for fyba
which will initially be uploaded to experimental if possible, then to
unstable after packages have cleared binary NEW.
Please find the patch for this NMU attached.
If you have any concerns about this patch, please reach out ASAP. Although
this package will be uploaded to experimental immediately, there will be a
period of several days before we begin uploads to unstable; so if information
becomes available that your package should not be included in the transition,
there is time for us to amend the planned uploads.
-- System Information:
Debian Release: trixie/sid
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)
Kernel: Linux 6.5.0-14-generic (SMP w/8 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
diff -Nru fyba-4.1.1/debian/changelog fyba-4.1.1/debian/changelog
--- fyba-4.1.1/debian/changelog 2022-12-01 08:22:00.0 +
+++ fyba-4.1.1/debian/changelog 2024-01-30 13:50:04.0 +
@@ -1,3 +1,10 @@
+fyba (4.1.1-8.1) experimental; urgency=medium
+
+ * Non-maintainer upload.
+ * Rename libraries for 64-bit time_t transition.
+
+ -- Lukas Märdian Tue, 30 Jan 2024 13:50:04 +
+
fyba (4.1.1-8) unstable; urgency=medium
* Team upload.
diff -Nru fyba-4.1.1/debian/control fyba-4.1.1/debian/control
--- fyba-4.1.1/debian/control 2022-11-27 12:30:31.0 +
+++ fyba-4.1.1/debian/control 2024-01-30 13:50:04.0 +
@@ -10,7 +10,10 @@
Homepage: https://github.com/kartverket/fyba
Rules-Requires-Root: no
-Package: libfyba0
+Package: libfyba0t64
+Provides: ${t64:Provides}
+Replaces: libfyba0
+Breaks: libfyba0 (<< ${source:Version})
Architecture: any
Multi-Arch: same
Depends: ${shlibs:Depends},
@@ -25,7 +28,7 @@
Architecture: any
Multi-Arch: same
Section: libdevel
-Depends: libfyba0 (= ${binary:Version}),
+Depends: libfyba0t64 (= ${binary:Version}),
${misc:Depends}
Description: Header files for FYBA library
This is the development package for developing applications that depends on
diff -Nru fyba-4.1.1/debian/libfyba0.docs fyba-4.1.1/debian/libfyba0.docs
--- fyba-4.1.1/debian/libfyba0.docs 2016-08-28 16:24:46.0 +
+++ fyba-4.1.1/debian/libfyba0.docs 1970-01-01 00:00:00.0 +
@@ -1 +0,0 @@
-README
diff -Nru fyba-4.1.1/debian/libfyba0.install fyba-4.1.1/debian/libfyba0.install
--- fyba-4.1.1/debian/libfyba0.install 2016-08-28 16:24:46.0 +
+++ fyba-4.1.1/debian/libfyba0.install 1970-01-01 00:00:00.0 +
@@ -1 +0,0 @@
-usr/lib/*/lib*.so.*
diff -Nru fyba-4.1.1/debian/libfyba0.lintian-overrides
fyba-4.1.1/debian/libfyba0.lintian-overrides
--- fyba-4.1.1/debian/libfyba0.lintian-overrides2018-07-29
19:51:51.0 +
+++ fyba-4.1.1/debian/libfyba0.lintian-overrides1970-01-01
00:00:00.0 +
@@ -1,3 +0,0 @@
-# Symbols are problematic for C++ libraries, shlibs is used
Processed: your mail
Processing commands for cont...@bugs.debian.org: > close 990343 1.4.2 Bug #990343 [backintime] backintime 1.1.24 - unhandled exception There is no source info for the package 'backintime' at version '1.4.2' with architecture '' Unable to make a source version for version '1.4.2' Marked as fixed in versions 1.4.2. Bug #990343 [backintime] backintime 1.1.24 - unhandled exception Marked Bug as done > End of message, stopping processing here. Please contact me if you need assistance. -- 990343: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=990343 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: your mail
Processing commands for cont...@bugs.debian.org: > close 1061973 Bug #1061973 [backintime] (no subject) Marked Bug as done > close 1061975 Bug #1061975 [backintime] (no subject) Marked Bug as done > End of message, stopping processing here. Please contact me if you need assistance. -- 1061973: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1061973 1061975: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1061975 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1061939: marked as done (libtag-c-dev and libtag-dev have an undeclared file conflict)
Your message dated Tue, 30 Jan 2024 15:11:42 + with message-id and subject line Bug#1061939: fixed in taglib 2.0-1~exp3 has caused the Debian Bug report #1061939, regarding libtag-c-dev and libtag-dev have an undeclared file conflict 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.) -- 1061939: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1061939 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: libtag-c-dev,libtag-dev Version: 2.0-1~exp2 Severity: serious User: debian...@lists.debian.org Usertags: fileconflict Control: affects -1 + libtag1-dev libtagc0-dev libtag-c-dev and libtag-dev have an undeclared file conflict. This may result in an unpack error from dpkg. The files * /usr/lib/x86_64-linux-gnu/libtag_c.so * /usr/lib/x86_64-linux-gnu/pkgconfig/taglib_c.pc are contained in the packages * libtag-c-dev/2.0-1~exp2 as present in experimental * libtagc0-dev * 1.11.1+dfsg.1-3 as present in bullseye * 1.13-2 as present in bookworm * 1.13.1-1 as present in trixie|unstable The files * /usr/bin/taglib-config * /usr/lib/x86_64-linux-gnu/libtag.so * /usr/lib/x86_64-linux-gnu/pkgconfig/taglib.pc are contained in the packages * libtag-dev/2.0-1~exp2 as present in experimental * libtag1-dev * 1.11.1+dfsg.1-3 as present in bullseye * 1.13-2 as present in bookworm * 1.13.1-1 as present in trixie|unstable These packages can be unpacked concurrently, because there is no relevant Replaces or Conflicts relation. Attempting to unpack these packages concurrently results in an unpack error from dpkg, because none of the packages installs a diversion for the affected files. Kind regards The Debian Usr Merge Analysis Tool This bug report has been automatically filed with no human intervention. The source code is available at https://salsa.debian.org/helmutg/dumat. If the filing is unclear or in error, don't hesitate to contact hel...@subdivi.de for assistance. --- End Message --- --- Begin Message --- Source: taglib Source-Version: 2.0-1~exp3 Done: Boyuan Yang We believe that the bug you reported is fixed in the latest version of taglib, 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 1061...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Boyuan Yang (supplier of updated taglib 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, 30 Jan 2024 09:03:39 -0500 Source: taglib Architecture: source Version: 2.0-1~exp3 Distribution: experimental Urgency: medium Maintainer: Debian Multimedia Maintainers Changed-By: Boyuan Yang Closes: 1061939 Changes: taglib (2.0-1~exp3) experimental; urgency=medium . * Refresh symbols again. * debian/control: Let new dev packages also declare versioned Breaks+Replaces on old dev packages. (Closes: #1061939) Checksums-Sha1: e792d332efcf451c59413285dad60a519e598aaa 2276 taglib_2.0-1~exp3.dsc 5045554ec63578c77d98f056961ccf65edf1a02f 1429934 taglib_2.0.orig.tar.gz 797a3b25820f16adabbe0f486dfe16f34a422c60 34120 taglib_2.0-1~exp3.debian.tar.xz 876253758857ae40d1bebb7660e4db4971394740 11405 taglib_2.0-1~exp3_amd64.buildinfo Checksums-Sha256: 6a20e7946b8bba03aeab2a2d0186f75d340e8072f012ae46e5fc941c81807493 2276 taglib_2.0-1~exp3.dsc e36ea877a6370810b97d84cf8f72b1e4ed205149ab3ac8232d44c850f38a2859 1429934 taglib_2.0.orig.tar.gz 7a8c97fad7ee1ed8d9c9384435e6d259db03296570f741c5412ac35d7104bb40 34120 taglib_2.0-1~exp3.debian.tar.xz bd4d50f83218a6389bdb382ff8368269aa3f4b657361f490717da346f5187be6 11405 taglib_2.0-1~exp3_amd64.buildinfo Files: e58622c1e8c339744fd6b7318134997a 2276 libs optional taglib_2.0-1~exp3.dsc 1826bf7e8486246a23fd98579f666413 1429934 libs optional taglib_2.0.orig.tar.gz ba2dce465efd5ebd93a58db8cf4dc945 34120 libs optional taglib_2.0-1~exp3.debian.tar.xz a1e30f68acd1d9b14cf537a01055e138 11405 libs optional taglib_2.0-1~exp3_amd64.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEfncpR22H1vEdkazLwpPntGGCWs4FAmW5A4kACgkQwpPntGGC Ws4USg//axDUqRWUG8BGjcCifwWonzFn3Mv4hAPTnp7CU4HgzDnywOgAs4EOZYsA JxjXg3niZxJVYsnT5u0ivW3tl8nWGIN/lVKKCE66Z5SkTaABQpnOVMpaTecorQBD
Bug#1061935: marked as done (please don't link against the shared libbfd library)
Your message dated Tue, 30 Jan 2024 15:07:09 + with message-id and subject line Bug#1061935: fixed in lfortran 0.30.0-3 has caused the Debian Bug report #1061935, regarding please don't link against the shared libbfd library 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.) -- 1061935: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1061935 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:lfortran Version: 0.30.0-2 Severity: important Tags: sid trixie please don't link against the private shared libbfd library, but use static linking instead and add a Built-Using attribute to the lfortran binary package. libbinutils has an upper versioned dependency, provides no stable ABI, and then requires rebuilding with each new binutils snapshot. --- End Message --- --- Begin Message --- Source: lfortran Source-Version: 0.30.0-3 Done: Alastair McKinstry We believe that the bug you reported is fixed in the latest version of lfortran, 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 1061...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Alastair McKinstry (supplier of updated lfortran 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, 30 Jan 2024 14:22:10 + Source: lfortran Architecture: source Version: 0.30.0-3 Distribution: unstable Urgency: medium Maintainer: Alastair McKinstry Changed-By: Alastair McKinstry Closes: 1061935 Changes: lfortran (0.30.0-3) unstable; urgency=medium . * Patch to ensure we use shared zstd lib, not static * Add lfortran.1 manpages * Add WITH_KOKKOS=yes for cpp backend * clang-16 needed for specified llvm backend * Add autopkgtests from example files * Build-dep on xeus-dev, xeus-zmq-dev for Jupyter kernel support * Don't use shared bfd library. Closes: #1061935 * Add Built-Using for BFD (+ iberty, sframe) * Fix VCS repo to science-team and push to salsa Checksums-Sha1: 6b66a8da4b27cee274f33899d489e3c543bb316e 2194 lfortran_0.30.0-3.dsc 4a6a5eb90ec376335701c3c9dc498ea52630a3ec 6056 lfortran_0.30.0-3.debian.tar.xz Checksums-Sha256: 3cb8688d538863d28f588fca63a2f270584d3e11c4a4666cbdd6ba6a30d89e87 2194 lfortran_0.30.0-3.dsc 0a7c316ca4c144d6c53b3eb5923fa8b61edb26cddb60f2a98fdf8fd450126b84 6056 lfortran_0.30.0-3.debian.tar.xz Files: de4840fbb7a64567de1f55b909fc2196 2194 devel optional lfortran_0.30.0-3.dsc 187a16b594bea2670ef9d186e6d20871 6056 devel optional lfortran_0.30.0-3.debian.tar.xz -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEEgjg86RZbNHx4cIGiy+a7Tl2a06UFAmW5CQsACgkQy+a7Tl2a 06VkzhAAiUEkeXgDPWm38ayQHOdh7rquVoaF8nrPbRMdDlmflLpwyx5FBXLsIc1d Em/1z3sn6eDoMbbnGt/DmZ/4B2EPZfyzz1qqsCuqGaE5PKS12wuslyhZFuyyBg1h XwRK4kpbC9YOpD8IMcFCbAKfKvgAaQ3mfgko16mAK4qtYfF7rOYqUfzzcgGGGWZg WWHgYxEJRr5H0ip+jZIQvjszJBZgFhz/d/ZZ8WBVAwDplDiKpUhKM4DytWJXsql6 eef1DgvLG2V/qsk1lV4lUJQ8PDyUa9GMTt0bE+gI858DzhksmQpp0PZMbafYeX7c lcVJdkDFxRs3KnnFHD/H/LnqXO2RDF9X3OI2fn2+cGD3Yco4pgnjEmuq0MAcvhnE 2MlFVQT9Wlgj1GXN0dVY321C+NHG7wOMGJpq0dTCA3ouofXEWELusce1h4sdBBCf d4OOAnnfR/kn1bWrDIoDhEF5hLgoOnD1qerc24yTB0agXlzzIK7x85FRjcqTt2Bt AP0/OYm31sNP7LOmbctoLMFZWsiz3IqQjnivLB9ahNFjvW/xt4ynwLdANaFFbYy1 ZE4e3gQW/RNyvMvX2B8D0ydSKx1ammv41BggPWw4Z/+TBU6uvC4RkbsfH6w184Mf BHZR84esBSnjU8kbwa6tu3MYy5aW+cpnV/tU7oRSBAA62fYmyoo= =2Xx/ -END PGP SIGNATURE End Message ---
Bug#1061648: marked as done (gnat-13-x86-64-linux-gnu: needs to inherit the Conflicts from gnat-13)
Your message dated Tue, 30 Jan 2024 15:02:11 +
with message-id
and subject line Bug#1061648: fixed in gcc-13 13.2.0-13
has caused the Debian Bug report #1061648,
regarding gnat-13-x86-64-linux-gnu: needs to inherit the Conflicts from gnat-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.)
--
1061648: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1061648
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: gnat-13-x86-64-linux-gnu
Version: 13.2.0-12
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Hi,
during a test with piuparts I noticed your package failed to install
because it tries to overwrite other packages files.
>From the attached log (scroll to the bottom...):
Selecting previously unselected package gnat-13-x86-64-linux-gnu.
Preparing to unpack .../5-gnat-13-x86-64-linux-gnu_13.2.0-12_amd64.deb ...
Unpacking gnat-13-x86-64-linux-gnu (13.2.0-12) ...
dpkg: error processing archive
/tmp/apt-dpkg-install-N8eYXp/5-gnat-13-x86-64-linux-gnu_13.2.0-12_amd64.deb
(--unpack):
trying to overwrite '/usr/bin/x86_64-linux-gnu-gnatgcc', which is also in
package gnat-12 12.3.0-14
Errors were encountered while processing:
/tmp/apt-dpkg-install-N8eYXp/5-gnat-13-x86-64-linux-gnu_13.2.0-12_amd64.deb
There are currently
Package: gnat-13
Version: 13.2.0-12
Depends: gnat-13-x86-64-linux-gnu (= 13.2.0-12), gcc-13-base (= 13.2.0-12),
gcc-13 (>= 13)
Suggests: gnat-13-doc, ada-reference-manual-2012, gnat-13-sjlj
Conflicts: gnat-10, gnat-11, gnat-12, gnat-4.9, gnat-5, gnat-6, gnat-7, gnat-8,
gnat-9
but these Conflicts are no longer effective (and can probably be
removed) due to the introduction of gnat-13-
This bug probably affects all gnat-13- packages for all
architectures.
cheers,
Andreas
--- End Message ---
--- Begin Message ---
Source: gcc-13
Source-Version: 13.2.0-13
Done: Matthias Klose
We believe that the bug you reported is fixed in the latest version of
gcc-13, 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 1061...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Matthias Klose (supplier of updated gcc-13 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, 30 Jan 2024 14:43:53 +0100
Source: gcc-13
Architecture: source
Version: 13.2.0-13
Distribution: unstable
Urgency: medium
Maintainer: Debian GCC Maintainers
Changed-By: Matthias Klose
Closes: 1061648
Changes:
gcc-13 (13.2.0-13) unstable; urgency=medium
.
* Update to git 20240130 from the gcc-13 branch.
- Fix PR preprocessor/105608.
* Fix and add dependencies for -for-build and -for-host packages.
* Correct conflicts with old gnat-N versions. Closes: #1061648.
* Fix some -for-{build,host} package descriptions. Addresses: #1061670.
* For Ubuntu, only define _FORTIFY_SOURCE, if there are no options
-U_FORTIFY_SOURCE or -D_FORTIFY_SOURCE=N given.
Checksums-Sha1:
6d0c8d48d1e4e77fc011425e87ed23073ab5 39059 gcc-13_13.2.0-13.dsc
b26b49cf6248f6a2ef7f117f948dbafcfbbd2f96 1789428 gcc-13_13.2.0-13.debian.tar.xz
27722fc48adb911fc7d9e5e6ab406cd50c2f471b 9263 gcc-13_13.2.0-13_source.buildinfo
Checksums-Sha256:
1364ce788f123bb41b633c0a50b604d7ebb7823f81153ffe077f6a87bd114f7e 39059
gcc-13_13.2.0-13.dsc
97e85b24c9ac130d9aec1ca26ac6b948338277929125aa956cbff009280a9648 1789428
gcc-13_13.2.0-13.debian.tar.xz
6e3597054dd2bea35f5afd6dccb23d68dbf44508f64d77dbc20740b8e313df98 9263
gcc-13_13.2.0-13_source.buildinfo
Files:
9a7d006e44ef480e472c93562f283a99 39059 devel optional gcc-13_13.2.0-13.dsc
677fdeb206fefcb75f29919362f4d5a5 1789428 devel optional
gcc-13_13.2.0-13.debian.tar.xz
62d1932bd1d5f1a2d8245edc12d724f6 9263 devel optional
gcc-13_13.2.0-13_source.buildinfo
-BEGIN PGP SIGNATURE-
iQJEBAEBCgAuFiEE1WVxuIqLuvFAv2PWvX6qYHePpvUFAmW4/boQHGRva29AZGVi
aWFuLm9yZwAKCRC9fqpgd4+m9VaND/0b58LYYxSiCq7zjSRfgdnWrx+S8MpG1BQ3
d6mET/VrifJ+wiQf0K4EBzgqfPxLPYwYNVAs6gOlgLio9GIAsoBFenJeK4PveuaO
695tdIqB+xJMMpkqvpx8fcRqAVv2HByU/BNG3F/Dx8yXCWpbcyhtVrFbxeZai/DS
72oqKEJyErPFlXvg9+v5xJvoVFYzS4l6GWhURBKPJ8YktH684VFgwCWbu65wvIZN
dJvhrW0+flfR2q4rGVeXLiJwPyrW9P
Bug#1060275: marked as done (asterisk: log flooded with ast_translate NOTICEs: lost frame(s))
Your message dated Tue, 30 Jan 2024 14:47:30 + with message-id and subject line Bug#1060275: fixed in asterisk 1:20.6.0~dfsg+~cs6.13.40431414-2 has caused the Debian Bug report #1060275, regarding asterisk: log flooded with ast_translate NOTICEs: lost frame(s) 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.) -- 1060275: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1060275 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: asterisk Version: 1:20.5.2~dfsg+~cs6.13.40431414-1 Severity: normal Tags: upstream Dear Maintainer, after upgrading from Debian11/asterisk 18.20.2 compiled from source to Debian12/Asterisk 20.5.2 from unstable, we receive lots of NOTICE logs like [2024-01-08 11:35:31] NOTICE[58221][C-028a]: translate.c:603 ast_translate: 18182 lost frame(s) 48240/30057 (alaw@8000)->(ulaw@8000) [2024-01-08 11:35:31] NOTICE[58710][C-0298]: translate.c:603 ast_translate: 1253 lost frame(s) 1254/0 (slin@16000)->(slin@8000)->(alaw@8000) doesn't matter IAX2 or PJSIP endpoints. We are surprised to see such notice between alaw & ulaw. Codecs used for PJSIP and IAX customers EP are !all,g722,ulaw,alaw and for providers !all,ulaw,alaw We checked translation and tried by adding slin,slin16 on both sides, no changes. On 18.20.2 we didn't have this behaviour. Answer we get from asterisk community list "If you’re using the Debian package, then that includes patches which are not present in Asterisk mainline. Those log messages, and some codec translation behavior, is from one of those patches." Thanks for your support -- System Information: Debian Release: 12.4 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 'stable'), (50, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 6.1.0-17-amd64 (SMP w/4 CPU threads; PREEMPT) Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to fr_FR.UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages asterisk depends on: ii adduser 3.134 ii asterisk-config 1:20.5.2~dfsg+~cs6.13.40431414-1 ii asterisk-core-sounds-en 1.6.1-1 ii asterisk-modules 1:20.5.2~dfsg+~cs6.13.40431414-1 ii init-system-helpers 1.65.2 ii libc62.36-9+deb12u3 ii libcap2 1:2.66-4 ii libcrypt11:4.4.33-2 ii libedit2 3.1-20221030-2 ii libjansson4 2.14-2 ii libpopt0 1.19+dfsg-1 ii libsqlite3-0 3.40.1-2 ii libssl3 3.0.11-1~deb12u2 ii libsystemd0 252.19-1~deb12u1 ii liburiparser10.9.7+dfsg-2 ii libuuid1 2.38.1-5+b1 ii libxml2 2.9.14+dfsg-1.3~deb12u1 ii libxslt1.1 1.1.35-1 Versions of packages asterisk recommends: ii asterisk-moh-opsound-gsm 2.03-1.1 ii sox 14.4.2+git20190427-4 Versions of packages asterisk suggests: pn asterisk-dahdi pn asterisk-dev pn asterisk-doc pn asterisk-ooh323 pn asterisk-opus -- no debconf information --- End Message --- --- Begin Message --- Source: asterisk Source-Version: 1:20.6.0~dfsg+~cs6.13.40431414-2 Done: Jonas Smedegaard We believe that the bug you reported is fixed in the latest version of asterisk, 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 1060...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Jonas Smedegaard (supplier of updated asterisk 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, 30 Jan 2024 11:42:08 +0100 Source: asterisk Architecture: source Version: 1:20.6.0~dfsg+~cs6.13.40431414-2 Distribution: unstable Urgency: medium Maintainer: Debian VoIP Team Changed-By: Jonas Smedegaard Closes: 1060275 Changes: asterisk (1:20.6.0~dfsg+~cs6.13.40431414-2) unstable; urgency=medium . * update patch 2016 to avoid excessive logging; closes: bug#1060275, thanks to Daniel Checksums-Sha1: 977b34513ce31778a47764cc22081e708af1fe33 5333
Processed: your mail
Processing commands for cont...@bugs.debian.org: > close 963849 1.3.3-1 Bug #963849 [backintime-qt] backintime-qt: GUI fails to launch Marked as fixed in versions backintime/1.3.3-1. Bug #963849 [backintime-qt] backintime-qt: GUI fails to launch Marked Bug as done > End of message, stopping processing here. Please contact me if you need assistance. -- 963849: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=963849 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1061522: marked as done (atril: CVE-2023-52076)
Your message dated Tue, 30 Jan 2024 13:34:28 + with message-id and subject line Bug#1061522: fixed in atril 1.26.2-1 has caused the Debian Bug report #1061522, regarding atril: CVE-2023-52076 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.) -- 1061522: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1061522 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: atril Version: 1.26.1-4 Severity: grave Tags: security upstream Justification: user security hole X-Debbugs-Cc: car...@debian.org, Debian Security Team Hi, The following vulnerability was published for atril. CVE-2023-52076[0]: | Atril Document Viewer is the default document reader of the MATE | desktop environment for Linux. A path traversal and arbitrary file | write vulnerability exists in versions of Atril prior to 1.26.2. | This vulnerability is capable of writing arbitrary files anywhere on | the filesystem to which the user opening a crafted document has | access. The only limitation is that this vulnerability cannot be | exploited to overwrite existing files, but that doesn't stop an | attacker from achieving Remote Command Execution on the target | system. Version 1.26.2 of Atril contains a patch for this | vulnerability. If you fix the vulnerability please also make sure to include the CVE (Common Vulnerabilities & Exposures) id in your changelog entry. For further information see: [0] https://security-tracker.debian.org/tracker/CVE-2023-52076 https://www.cve.org/CVERecord?id=CVE-2023-52076 [1] https://github.com/mate-desktop/atril/security/advisories/GHSA-6mf6-mxpc-jc37 [2] https://github.com/mate-desktop/atril/commit/e70b21c815418a1e6ebedf6d8d31b8477c03ba50 Please adjust the affected versions in the BTS as needed. Regards, Salvatore --- End Message --- --- Begin Message --- Source: atril Source-Version: 1.26.2-1 Done: Mike Gabriel We believe that the bug you reported is fixed in the latest version of atril, 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 1061...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Mike Gabriel (supplier of updated atril 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, 30 Jan 2024 14:03:41 +0100 Source: atril Architecture: source Version: 1.26.2-1 Distribution: unstable Urgency: medium Maintainer: Debian+Ubuntu MATE Packaging Team Changed-By: Mike Gabriel Closes: 1061522 Changes: atril (1.26.2-1) unstable; urgency=medium . * New upstream release. - CVE-2023-52076: epub: Prevent path traversal when extracting files. (Closes: #1061522). * debian/patches: + Drop 0001-Use-a-blank-line-at-most.patch, 0002-comics-Use-libarchive-to- unpack-documents.patch and 1001-webkit2gtk4.1.patch, rebase 1002-avoid- crash-on-certain-epub-files.patch. * debian/copyright: + Update copyright attribution for debian/. Checksums-Sha1: 8fc7ad532a3a75ab7b6668f2a46460d64bc7ef5d 3111 atril_1.26.2-1.dsc 887b2af873ff3d5f1a6863a461fcba887c5459c1 1446416 atril_1.26.2.orig.tar.xz 4b9fef92673454f9aa3bd1dacd975c27ac6d7973 20440 atril_1.26.2-1.debian.tar.xz eced77cf64f0e9bfea097ab76c44f86b7b06a869 17679 atril_1.26.2-1_source.buildinfo Checksums-Sha256: 7555a183d1666e6825966423c9a1fc0fb7711d02d3c0db8554c8126a7a8fbfa9 3111 atril_1.26.2-1.dsc e3638b52552ea7cd71db81602ffecd2d39b99eab46336eaec11b30e6f5b475af 1446416 atril_1.26.2.orig.tar.xz e4291057a99b1958e7874710424b96aee9ac9db14d79542d931830c1b9db855f 20440 atril_1.26.2-1.debian.tar.xz 7ed76e05c0e283eb137bc97f19b9a47d67ec0ddb1d076a1719a53d3e392edaa1 17679 atril_1.26.2-1_source.buildinfo Files: b2ceb1da438fe85bcedcbb49cab27621 3111 x11 optional atril_1.26.2-1.dsc e020f5af934b90705bd69146c89f3577 1446416 x11 optional atril_1.26.2.orig.tar.xz 38b806e856e0c6e3cd45279ceca025da 20440 x11 optional atril_1.26.2-1.debian.tar.xz 0a92dfac63080892588d31d1198cd311 17679 x11 optional atril_1.26.2-1_source.buildinfo -BEGIN PGP SIGNATURE- iQJJBAEBCAAzFiEEm/uu6GwKpf+/IgeCmvRrMCV3GzEFAmW493IVHHN1bndlYXZl ckBkZWJpYW4ub3JnAAoJEJr0azAldxsxJ1QP/07C2LDgTUmOlq7x99T0C4qCaeQ2
Bug#1060948: marked as done (sqlreduce: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p "3.12 3.11" returned exit code 13)
Your message dated Tue, 30 Jan 2024 12:30:16 +
with message-id
and subject line Bug#1060948: fixed in sqlreduce 1.3-1
has caused the Debian Bug report #1060948,
regarding sqlreduce: FTBFS: dh_auto_test: error: pybuild --test --test-pytest
-i python{version} -p "3.12 3.11" returned exit code 13
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
1060948: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1060948
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: sqlreduce
Version: 1.2-1
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20240115 ftbfs-trixie
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> pg_virtualenv dh_auto_test
> Creating new PostgreSQL cluster 16/regress ...
> I: pybuild base:305: cd
> /<>/.pybuild/cpython3_3.12_sqlreduce/build; python3.12 -m pytest
> tests
> = test session starts
> ==
> platform linux -- Python 3.12.1, pytest-7.4.4, pluggy-1.3.0
> rootdir: /<>
> collected 3 items
>
> tests/test_sqlreduce.py ..F
> [100%]
>
> === FAILURES
> ===
> __ test_rules
> __
>
> def test_rules():
> for classname, rule in rules.items():
> print(f"{classname}:")
> tests = rule['tests']
> if tests is None:
> raise Exception(f"{classname} is missing tests")
> for test, expected in zip(tests[0::2], tests[1::2]):
> print(" test:", test)
> res, _ = run_reduce(test)
> print(" got:", res)
> if res != expected:
> print("expect:", expected)
> > raise Exception(f"{classname} test: {test}: expected
> > {expected}, got {res}")
> E Exception: FetchStmt test: fetch all in foo: expected
> FETCH ALL foo, got FETCH FORWARD ALL FROM foo
>
> tests/test_sqlreduce.py:59: Exception
> - Captured stdout call
> -
> A_ArrayExpr:
> test: select array[2, foo]
>got: SELECT foo
> A_Const:
> test: select '1,1'::point = '1,1'
>got: SELECT CAST(NULL AS point) = NULL
> A_Expr:
> test: select 1 + moo
>got: SELECT moo
> test: select foo between 2 and 3
>got: SELECT foo
> test: select 1 between moo and 3
>got: SELECT moo
> test: select 1 between 2 and bar
>got: SELECT bar
> A_Indirection:
> test: select foo[2]
>got: SELECT foo
> test: select (select array[1])[foo]
>got: SELECT (SELECT ARRAY[NULL])[foo]
> AlterPolicyStmt:
> test: alter policy moo on bar using (true)
>got: ALTER POLICY moo ON bar USING (NULL)
> BoolExpr:
> test: select moo and foo
>got: SELECT moo
> test: select true and (foo or false)
>got: SELECT foo
> test: select set_config('a.b', 'blub', true) = 'blub' and
> set_config('work_mem', current_setting('a.b'), true) = '' and true
>got: SELECT set_config('a.b', 'blub', NULL) = 'blub' AND
> set_config('work_mem', current_setting('a.b'), NULL) = ''
> BooleanTest:
> test: select foo is true
>got: SELECT foo
> CallStmt:
> test: call foo()
>got: CALL foo()
> test: call foo(bar + 1)
>got: CALL foo(bar)
> CaseExpr:
> test: select case foo when 1 then 2 else bar end
>got: SELECT foo
> test: select case when moo then 1 else bar end
>got: SELECT moo
> test: select case when true then foo end
>got: SELECT foo
> test: select case when true then 1 else bar end
>got: SELECT bar
> CaseWhen:
> test: select case when bar then 1 else 2 end
>got: SELECT bar
> ClusterStmt:
> test: cluster foo
>got: CLUSTER foo
> CoalesceExpr:
> test: select coalesce(1, bar)
>got: SELECT bar
> test: select coalesce(1, '', 2)
>got: SELECT COALESCE('', 2)
> ColumnRef:
> test: select 'foo'
>got: SELECT
> CommonTableExpr:
> test: with a as (select moo) select from a
>got: SELECT moo
> test: with recursive a(a) as (select 5 union select 1 from a) cycle a set
> is_cycle using path, b(b) as (select null) select a = b from a, b
>got: WITH a(a) AS (SELECT NULL UNION SELECT 1), b(b) AS (SELECT NULL)
> SELECT a = b FROM a, b
> CopyStmt:
> test: copy (select foo) to 'bla'
>got: SELECT foo
> test: create table foo (id int); copy foo from
Bug#1061768: marked as done (vulkan-loader: new upstream release 1.3.275.0)
Your message dated Tue, 30 Jan 2024 11:58:58 + with message-id and subject line Bug#1061768: fixed in vulkan-loader 1.3.275.0-1 has caused the Debian Bug report #1061768, regarding vulkan-loader: new upstream release 1.3.275.0 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.) -- 1061768: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1061768 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: vulkan-loader Version: 1.3.268.0-1 Severity: wishlist A new upstream release vulkan-sdk-1.3.275.0 is available. smcv --- End Message --- --- Begin Message --- Source: vulkan-loader Source-Version: 1.3.275.0-1 Done: Timo Aaltonen We believe that the bug you reported is fixed in the latest version of vulkan-loader, 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 1061...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Timo Aaltonen (supplier of updated vulkan-loader 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, 30 Jan 2024 13:29:31 +0200 Source: vulkan-loader Built-For-Profiles: noudeb Architecture: source Version: 1.3.275.0-1 Distribution: unstable Urgency: medium Maintainer: Debian X Strike Force Changed-By: Timo Aaltonen Closes: 1061768 Changes: vulkan-loader (1.3.275.0-1) unstable; urgency=medium . * New upstream release. (Closes: #1061768) * rules: Create loader/generated if it doesn't exist. Checksums-Sha1: 3a12eee216227995e4bed3033e883c99366dd1ba 2252 vulkan-loader_1.3.275.0-1.dsc 7295569482af305619609300bb2468a21fb39ac3 2642760 vulkan-loader_1.3.275.0.orig.tar.xz 8286013148b3c52824979e8b2fb03d9594c4c237 9012 vulkan-loader_1.3.275.0-1.debian.tar.xz 0f49348fc399275140b33df31365f23a700883f4 8854 vulkan-loader_1.3.275.0-1_source.buildinfo Checksums-Sha256: daf53ed7e6784e9b8e6dca6c18cdf1ba9b67fdc4dd75e39e9a57fa2e9eb7d443 2252 vulkan-loader_1.3.275.0-1.dsc 5f95219fc189b4c09ce537d8ec1ea4b5861b087cd00b6d821f99aecf6e9dddce 2642760 vulkan-loader_1.3.275.0.orig.tar.xz 99fb9e65b015b2e9e9c693b58c1326ad2f419930831bc45d3f6b1ce76fb832c6 9012 vulkan-loader_1.3.275.0-1.debian.tar.xz e8c2b6e80f323d00a99aecb195a09764666192255f2f634ffb547f4b1db1e6bc 8854 vulkan-loader_1.3.275.0-1_source.buildinfo Files: bd600148c0caab775429ae3115d71376 2252 libs optional vulkan-loader_1.3.275.0-1.dsc 6d1907a69c5218d29b917c7700fd7fc2 2642760 libs optional vulkan-loader_1.3.275.0.orig.tar.xz c269222b5832d137951824ac8f97c910 9012 libs optional vulkan-loader_1.3.275.0-1.debian.tar.xz 3dc17beca03cd3255b849de54fd99fa7 8854 libs optional vulkan-loader_1.3.275.0-1_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEdS3ifE3rFwGbS2Yjy3AxZaiJhNwFAmW43csACgkQy3AxZaiJ hNzhqBAAgbl0JNX9HtNDEimldT7+ieAVdMtJrqdj6At3Zno6olaaGFnQD/b9Jydv E9xeyUdcwSP9Do2GXOhplRWH4hoZkMc/dtsDqOdrQi0oGLOez2NH2Ue1AulvGoQH oFJR6UXZQzmrSd8+q54aJg85ezxw5UaxdJXCT700IKeqAXtZOoaLqIM9zwuo8WBk WqqQQM68JR+gm0OTshwNwLlRUWlHlKYKTf85924Wu7XFmQYvJdx3F+5sCRAbvjIn dCI71lF/zep+LS9pBDX305UqespMVUABkgyCuexde5cuACM6JgocU1xrObZrqKC7 gP2XUbK/XfpA+1pwfADLViNOnga71/VpqljN5iGdf1bkLBW/EMDG2aNb2x9inwb2 VMdJO1DSvWhwbxhrpWj/u4XYDgvBaQhlv9gLzO/1a3OrubyuqIbJbwBRw4gFIaEe 65/BwWFSgGPFZ76+kImuXv2ysap+vOit9/4ny0URRNpnctVaA0qS2KQ9AfaCC388 3HdfvTX0VJkbOPMOLaOeW51ShcGlaGCx9rOSTUfFyBrd8ASucjcIdnm4yJrlgamP qY7DRksYgfcIZyrQkePTNqVtxLBUx/IQYqJiFY/JehAxV5Bg13h/D32ag1HnvvRt ILyJoNCROh2vU7O8h4fpOIRpcAjWXE0dfSc1NpSE0my23N0oFWU= =jepR -END PGP SIGNATURE End Message ---
Bug#1061756: marked as done (python-twilio ftbfs with Python 3.12 as default)
Your message dated Tue, 30 Jan 2024 10:53:54 +0100
with message-id
and subject line Re: python-twilio ftbfs with Python 3.12 as default
has caused the Debian Bug report #1061756,
regarding python-twilio ftbfs with Python 3.12 as default
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.)
--
1061756: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1061756
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:python-twilio
Version: 7.7.1+ds1-1
Severity: serious
Tags: sid trixie ftbfs
User: debian-pyt...@lists.debian.org
Usertags: python3.12
With python3-defaults from experimental, the package fails to build:
[...]
=== FAILURES
===
___ ClientValidationJwtTest.test_jwt_payload
___
self = testMethod=test_jwt_payload>
def test_jwt_payload(self):
vp = ValidationPayload(
method='GET',
path='/Messages',
query_string='PageSize=5=10',
signed_headers=['authorization', 'host'],
all_headers={'authorization': 'foobar', 'host':
'api.twilio.com'},
body='foobar'
)
expected_hash =
'4dc9b67bed579647914587b0e22a1c65c1641d8674797cd82de65e766cce5f80'
jwt = ClientValidationJwt('AC123', 'SK123', 'CR123', 'secret', vp)
> self.assertDictContainsSubset({
'hrh': 'authorization;host',
'rqh': expected_hash,
'iss': 'SK123',
'sub': 'AC123',
}, jwt.payload)
E AttributeError: 'ClientValidationJwtTest' object has no
attribute 'assertDictContainsSubset'
tests/unit/jwt/test_client_validation.py:234: AttributeError
___ ClientValidationJwtTest.test_jwt_signing
___
self = testMethod=test_jwt_signing>
def test_jwt_signing(self):
vp = ValidationPayload(
method='GET',
path='/Messages',
query_string='PageSize=5=10',
signed_headers=['authorization', 'host'],
all_headers={'authorization': 'foobar', 'host':
'api.twilio.com'},
body='foobar'
)
expected_hash =
'4dc9b67bed579647914587b0e22a1c65c1641d8674797cd82de65e766cce5f80'
private_key = rsa.generate_private_key(
public_exponent=65537,
key_size=2048,
backend=default_backend()
)
public_key =
private_key.public_key().public_bytes(Encoding.PEM, PublicFormat.PKCS1)
private_key = private_key.private_bytes(Encoding.PEM,
PrivateFormat.PKCS8, NoEncryption())
jwt = ClientValidationJwt('AC123', 'SK123', 'CR123',
private_key, vp)
decoded = ClientValidationJwt.from_jwt(jwt.to_jwt(), public_key)
> self.assertDictContainsSubset({
'hrh': 'authorization;host',
'rqh': expected_hash,
'iss': 'SK123',
'sub': 'AC123',
}, decoded.payload)
E AttributeError: 'ClientValidationJwtTest' object has no
attribute 'assertDictContainsSubset'
tests/unit/jwt/test_client_validation.py:271: AttributeError
__ JwtTest.test_encode_decode
__
self =
def test_encode_decode(self):
test_start = self.now()
jwt = DummyJwt('secret_key', 'issuer', subject='hey',
payload={'sick': 'sick'})
decoded_jwt = Jwt.from_jwt(jwt.to_jwt(), 'secret_key')
self.assertGreaterEqual(decoded_jwt.valid_until, self.now() + 3600)
self.assertGreaterEqual(decoded_jwt.nbf, test_start)
self.assertEqual(decoded_jwt.issuer, 'issuer')
self.assertEqual(decoded_jwt.secret_key, 'secret_key')
self.assertEqual(decoded_jwt.algorithm, 'HS256')
self.assertEqual(decoded_jwt.subject, 'hey')
self.assertEqual(decoded_jwt.headers, {'typ': 'JWT', 'alg':
'HS256'})
> self.assertDictContainsSubset({
'iss': 'issuer',
'sub': 'hey',
'sick': 'sick',
}, decoded_jwt.payload)
E AttributeError: 'JwtTest' object has no attribute
'assertDictContainsSubset'
tests/unit/jwt/test_jwt.py:206: AttributeError
--- End Message ---
--- Begin Message ---
Source: python-twilio
Source-Version: 8.12.0-1
This is the same bug as 1058428, closing and merging.
--- End Message ---
Bug#1061615: marked as done (src:nanobind: unsatisfied build dependency in testing: python3-torch)
Your message dated Tue, 30 Jan 2024 09:35:08 + with message-id and subject line Bug#1061615: fixed in nanobind 1.8.0-4 has caused the Debian Bug report #1061615, regarding src:nanobind: unsatisfied build dependency in testing: python3-torch 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.) -- 1061615: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1061615 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: nanobind Version: 1.8.0-3 Severity: serious Tags: sid trixie User: debian...@lists.debian.org Usertags: edos-uninstallable Dear maintainer(s), Dose [1] is reporting a build issue with your package, it's missing a build dependency. Obviously your build dependencies shouldn't be removed from testing, but unfortunately there are multiple scenarios where that can happen nevertheless. To uphold our social contract, Debian requires that packages can be rebuild from source in the suite we are shipping them, so currently this is a serious issue with your package in testing.python3-torch Can you please investigate the situation and figure out how to resolve it? Regularly, if the build dependency is available in unstable, helping the maintainer of your Build-Depends to enable migration to testing is a great way to solve the issue. If your build dependency is gone from unstable and testing, you'll have to fix the build process in some other way. Paul Note: this bug report was sent after some quick manual checks using a template. Please reach out to me if you believe I made a mistake in my process. [1] https://qa.debian.org/dose/debcheck/src_testing_main/latest/amd64.html OpenPGP_signature.asc Description: OpenPGP digital signature --- End Message --- --- Begin Message --- Source: nanobind Source-Version: 1.8.0-4 Done: Timo Röhling We believe that the bug you reported is fixed in the latest version of nanobind, 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 1061...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Timo Röhling (supplier of updated nanobind 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, 30 Jan 2024 10:19:10 +0100 Source: nanobind Architecture: source Version: 1.8.0-4 Distribution: unstable Urgency: medium Maintainer: Debian Python Team Changed-By: Timo Röhling Closes: 1061615 Changes: nanobind (1.8.0-4) unstable; urgency=medium . * Remove optional test dependency on python3-torch (Closes: #1061615) Checksums-Sha1: f9b6f7151c192114961f4f366e6aaf34cafd7119 2635 nanobind_1.8.0-4.dsc 54b0734d7ec0a70daa38f3a41c437019a3352fd2 4460 nanobind_1.8.0-4.debian.tar.xz Checksums-Sha256: c7937013f19e82161636da04b1a091839351b601725df3fbafc10234eca7ef66 2635 nanobind_1.8.0-4.dsc b246d7bebd2b1d6920a215ed1f0b8b8b3b7e8681442944be75b7d60577348e6b 4460 nanobind_1.8.0-4.debian.tar.xz Files: cb5b8503aafca4e708b570c1fc7a3676 2635 python optional nanobind_1.8.0-4.dsc 2087d08eb3d98479da851334b57df03a 4460 python optional nanobind_1.8.0-4.debian.tar.xz -BEGIN PGP SIGNATURE- iQHIBAEBCgAyFiEEJvtDgpxjkjCIVtam+C8H+466LVkFAmW4wFYUHHJvZWhsaW5n QGRlYmlhbi5vcmcACgkQ+C8H+466LVnXQwwAirmSB1zQaLd4jhL4KojLERnnEmU0 J42hAR6VjhLobHJgYMRyQY0Yqt/2w7YPbZHpw8m9lrf6p4kxF1olQmwR6XNBgqyG Sqc7XjGLP3nSdOeTdQ7rSG8MaynVds+RQD6NUXQipGu4wpVZtismp/IzJtvVUSz1 5PlnuuoOiZWFDYkMizhrtwI8FmPMV3XTbBv2a5upX3ATwpcxUlN4A56/9eu+EvOa ymz0p01D1x7EMn8SecQAAuy2pL95qnbskk46MbzdISjOLqAgaFqbr68++G/+RbwK GWm9A1PAHQ5njqxyJPe+8D0cQFbQG4H/rnXtHkvcCixjf1XWzp79gjNxBEN7uLVt nYN5DOhPs/pHC8HG0f7LsiOVgN/CkXGJeQiW/gkAfArpok+i3miUeeYbPeCoBZ7E rJOJmlCxkQ2KkjZPR+WSKe/BPlVdzFBIRbkPLWpCwZfLHJPLB3SsPSJ8o28fnGc2 V4skl84dQtei7uE5qknTsQplv0krXE/j8w80 =kud6 -END PGP SIGNATURE End Message ---
Bug#1061931: marked as done (biosquid: NMU diff for 64-bit time_t transition)
Your message dated Tue, 30 Jan 2024 08:34:14 +
with message-id
and subject line Bug#1061931: fixed in biosquid 1.9g+cvs20050121-14
has caused the Debian Bug report #1061931,
regarding biosquid: NMU diff for 64-bit time_t transition
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.)
--
1061931: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1061931
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: biosquid
Version: 1.9g+cvs20050121-13
Severity: serious
Tags: patch pending
Justification: library ABI skew on upgrade
User: debian-...@lists.debian.org
Usertags: time-t
Dear maintainer,
As part of the 64-bit time_t transition required to support 32-bit
architectures in 2038 and beyond
(https://wiki.debian.org/ReleaseGoals/64bit-time), we have identified
biosquid as a source package shipping runtime libraries whose ABI
either is affected by the change in size of time_t, or could not be
analyzed via abi-compliance-checker (and therefore to be on the safe
side we assume is affected).
To ensure that inconsistent combinations of libraries with their
reverse-dependencies are never installed together, it is necessary to
have a library transition, which is most easily done by renaming the
runtime library package.
Since turning on 64-bit time_t is being handled centrally through a change
to the default dpkg-buildflags (https://bugs.debian.org/1037136), it is
important that libraries affected by this ABI change all be uploaded close
together in time. Therefore I have prepared a 0-day NMU for biosquid
which will initially be uploaded to experimental if possible, then to
unstable after packages have cleared binary NEW.
Please find the patch for this NMU attached.
If you have any concerns about this patch, please reach out ASAP. Although
this package will be uploaded to experimental immediately, there will be a
period of several days before we begin uploads to unstable; so if information
becomes available that your package should not be included in the transition,
there is time for us to amend the planned uploads.
-- System Information:
Debian Release: trixie/sid
APT prefers unstable
APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 6.5.0-14-generic (SMP w/12 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE
Locale: LANG=C, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
diff -Nru biosquid-1.9g+cvs20050121/debian/changelog
biosquid-1.9g+cvs20050121/debian/changelog
--- biosquid-1.9g+cvs20050121/debian/changelog 2024-01-14 13:29:59.0
+
+++ biosquid-1.9g+cvs20050121/debian/changelog 2024-01-30 04:35:42.0
+
@@ -1,3 +1,10 @@
+biosquid (1.9g+cvs20050121-13.1) experimental; urgency=medium
+
+ * Non-maintainer upload.
+ * Rename libraries for 64-bit time_t transition.
+
+ -- Steve Langasek Tue, 30 Jan 2024 04:35:42 +
+
biosquid (1.9g+cvs20050121-13) unstable; urgency=medium
* Fix clean target
diff -Nru biosquid-1.9g+cvs20050121/debian/control
biosquid-1.9g+cvs20050121/debian/control
--- biosquid-1.9g+cvs20050121/debian/control2024-01-14 13:29:59.0
+
+++ biosquid-1.9g+cvs20050121/debian/control2024-01-30 04:35:42.0
+
@@ -28,7 +28,10 @@
This package contains some tools to demonstrate the features of the
SQUID library.
-Package: libsquid1
+Package: libsquid1t64
+Provides: ${t64:Provides}
+Replaces: libsquid1
+Breaks: libsquid1 (<< ${source:Version})
Architecture: any
Section: libs
Depends: ${shlibs:Depends},
--- End Message ---
--- Begin Message ---
Source: biosquid
Source-Version: 1.9g+cvs20050121-14
Done: Andreas Tille
We believe that the bug you reported is fixed in the latest version of
biosquid, 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 1061...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Andreas Tille (supplier of updated biosquid 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, 30 Jan 2024 08:30:22 +0100
Source: biosquid
