Bug#1000684: python-django-modelcluster: autopkgtest fails with django-taggit >= 2.0.0
Source: python-django-modelcluster
Version: 5.2-1
Severity: serious
Control: found -1 python-django-modelcluster/5.2-1
Dear Maintainer,
the autopkgtesting is failing since the upload of python3-django-taggit
2.0.0-1 but was working with versions of python3-django-taggit less than
this version.
The relevant part from the autopkgtest is:
System check identified 25 issues (0 silenced).
ss.Ex...
==
ERROR: test_can_access_tags_on_unsaved_instance (tests.tests.test_tag.TagTest)
--
Traceback (most recent call last):
File
"/tmp/autopkgtest-lxc.4wu0r9tw/downtmp/autopkgtest_tmp/tests/tests/test_tag.py",
line 40, in test_can_access_tags_on_unsaved_instance
mission_burrito.tags.set('mexican', 'burrito')
File "/usr/lib/python3/dist-packages/taggit/utils.py", line 124, in inner
return func(self, *args, **kwargs)
File "/usr/lib/python3/dist-packages/modelcluster/contrib/taggit.py", line
78, in set
return super(_ClusterTaggableManager, self).set(*tags, clear=True)
File "/usr/lib/python3/dist-packages/taggit/utils.py", line 124, in inner
return func(self, *args, **kwargs)
TypeError: set() takes 2 positional arguments but 3 were given
--
The full log (for amd64) can be found here;:
https://ci.debian.net/data/autopkgtest/testing/amd64/p/python-django-modelcluster/17044291/log.gz
>From the changelog of django-taggit 2.0.0 I guess that the current
autopkgtest is breaking due a backwards incompatibility (hence that's
the main reason the version was bumped to 2.0.0).
https://github.com/jazzband/django-taggit/blob/2.0.0/CHANGELOG.rst#200-2021-11-14
I think python-django-modelcluster will need some adjustments to work
proper with the recent version of django-taggit, or at least an
adjustments of the used autopktest.
Regards
Carsten
-- System Information:
Debian Release: bookworm/sid
APT prefers testing
APT policy: (500, 'testing'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 5.14.0-4-amd64 (SMP w/6 CPU threads)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Processed: python-django-modelcluster: autopkgtest fails with django-taggit >= 2.0.0
Processing control commands: > found -1 python-django-modelcluster/5.2-1 Bug #1000684 [src:python-django-modelcluster] python-django-modelcluster: autopkgtest fails with django-taggit >= 2.0.0 Ignoring request to alter found versions of bug #1000684 to the same values previously set -- 1000684: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1000684 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1000611: libvtk9{,-qt}: soname change without library transition
Hi Anton, * Anton Gladky [2021-11-25 22:07]: thanks for the bug report. It was really an accidental upload into unstable instead of experimental. Yes, I will rename the package and upload it ASAP. What about uploading the old 9.0.3+dfsg1-3 as 9.1.0+really9.0.3+dfsg1-3 in the meantime to fix unstable? Cheers Jochen Am Do., 25. Nov. 2021 um 22:03 Uhr schrieb Adrian Bunk : Package: libvtk9 Version: 9.1.0+dfsg2-2 Severity: serious Control: affects -1 libvtk9-qt src:vtk9 https://ci.debian.net/data/autopkgtest/testing/amd64/f/freecad/16980590/log.gz ... ERROR: TestFemApp (unittest.loader._FailedTest) -- ImportError: Failed to import test module: TestFemApp Traceback (most recent call last): File "/usr/lib/python3.9/unittest/loader.py", line 154, in loadTestsFromName module = __import__(module_name) File "/usr/share/freecad/Mod/Fem/TestFemApp.py", line 33, in from femtest.app.test_mesh import TestMeshCommon as FemTest07 File "/usr/share/freecad/Mod/Fem/femtest/app/test_mesh.py", line 33, in import Fem ImportError: libvtkFiltersExtraction-9.0.so.1: cannot open shared object file: No such file or directory ... The soname of the vtk9 libraries is not 9, it is 9.0 for VTK 9.0 and 9.1 for VTK 9.1: $ objdump -p /usr/lib/x86_64-linux-gnu/libvtkChartsCore-9.1.so.1 | grep SONAME SONAME libvtkChartsCore-9.1.so.1 $ In bullseye libvtk9 and libvtk9-qt should have been named libvtk9.0 and libvtk9.0-qt, but this alone is harmless. Not harmless is that the libraries must transition to the new soname in 9.1, renaming the packages to libvtk9.1 and libvtk9.1-qt. -- debian-science-maintainers mailing list debian-science-maintain...@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/debian-science-maintainers signature.asc Description: PGP signature
Processed: severity of 996878 is serious
Processing commands for cont...@bugs.debian.org: > severity 996878 serious Bug #996878 [python3-prelude] python3-prelude: python3 import prelude throws an ImportError exception Severity set to 'serious' from 'grave' > thanks Stopping processing here. Please contact me if you need assistance. -- 996878: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=996878 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#996878: marked as done (python3-prelude: python3 import prelude throws an ImportError exception)
Your message dated Sat, 27 Nov 2021 09:34:44 + with message-id and subject line Bug#996878: fixed in libprelude 5.2.0-5 has caused the Debian Bug report #996878, regarding python3-prelude: python3 import prelude throws an ImportError exception 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.) -- 996878: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=996878 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: python3-prelude Version: 5.2.0-4 Severity: grave Justification: renders package unusable Dear Maintainer, * What led up to the situation? Installing python3-prelude on a fresh bullseye, then importing "prelude" in the python3 interpreter * What exactly did you do (or not do) that was effective (or ineffective)? I tried to use python3-prelude from unstable with no luck * What was the outcome of this action? Importing generates : :~# python3 Python 3.9.2 (default, Feb 28 2021, 17:03:44) [GCC 10.2.1 20210110] on linux Type "help", "copyright", "credits" or "license" for more information. >>> import prelude Traceback (most recent call last): File "", line 1, in File "/usr/lib/python3/dist-packages/prelude.py", line 15, in from _prelude import * ImportError: /usr/lib/python3/dist-packages/_prelude.cpython-39-x86_64-linux-gnu.so: undefined symbol: PyIOBase_Type * What outcome did you expect instead? I expected it to load prelude. It seems to also affect prewikka which does this import (my first problem was related to prewikka, I digged it to python3-prelude) Cheers François Lesueur -- System Information: Debian Release: 11.1 APT prefers stable-security APT policy: (500, 'stable-security'), (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 5.10.0-9-amd64 (SMP w/2 CPU threads) Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=C.UTF-8, 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) Versions of packages python3-prelude depends on: ii libc62.31-13+deb11u2 ii libgcc-s110.2.1-6 ii libprelude28 5.2.0-4 ii libpreludecpp12 5.2.0-3+b1 ii libstdc++6 10.2.1-6 ii python3 3.9.2-3 python3-prelude recommends no packages. python3-prelude suggests no packages. -- no debconf information --- End Message --- --- Begin Message --- Source: libprelude Source-Version: 5.2.0-5 Done: Thomas Andrejak We believe that the bug you reported is fixed in the latest version of libprelude, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 996...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Thomas Andrejak (supplier of updated libprelude 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, 3 Nov 2021 20:53:39 +0200 Source: libprelude Architecture: source Version: 5.2.0-5 Distribution: unstable Urgency: medium Maintainer: Pierre Chifflier Changed-By: Thomas Andrejak Closes: 994295 996878 Changes: libprelude (5.2.0-5) unstable; urgency=medium . * d.patches: Update 025-Fix-PyIOBase_Type.patch because swig is not executed (Closes: #996878) * d.libpreludecpp12.symbols: Add arc keyword near x32 to support ARC architecture. Thanks to Evgeniy Didin and Mattia Rizzolo (Closes: #994295) * d.tests: Add test to valid that we can load prelude as a python module Checksums-Sha1: 79c1d4134174ddbcb011984c86587c665967434e 3121 libprelude_5.2.0-5.dsc 0a6b2d91ffa06c28643e5f7b5aa76b4a5a42e29e 28596 libprelude_5.2.0-5.debian.tar.xz 9569a9326dd222dbd829dd51ce1fa3c10e4a99b6 15773 libprelude_5.2.0-5_amd64.buildinfo Checksums-Sha256: 2dd0ed12cfe2dea28cc54c71092b5c5f43b472bdf01aec6789d9c44a62639a54 3121 libprelude_5.2.0-5.dsc 709c95f962376ffa626f13ecfd0a1c917cab71027ad1f82e9f7b99a109d343be 28596 libprelude_5.2.0-5.debian.tar.xz 1250cb97f46d2aad16facd15a5b47e3266b12c5e0bc81233b145a229480a91ae 15773 libprelude_5.2.0-5_amd64.buildinfo Files: 13137ef07ed49086e6360e36293dc8dd 3121 libs optional libprelude_5.2.0-5.dsc 510147fe84c935bbe33c6056ecd25da0 28596 libs option
Processed: Bug#999522 marked as pending in brian
Processing control commands: > tag -1 pending Bug #999522 [src:brian] brian: FTBFS with numpy 1.21 (in experimental): TypeError: logical_and() takes from 2 to 3 positional arguments but 1 were given Added tag(s) pending. -- 999522: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=999522 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#999522: marked as pending in brian
Control: tag -1 pending Hello, Bug #999522 in brian reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/med-team/brian/-/commit/b92cecb7212006f24d53d29b0317f83b8b99a748 Add fix-numpy-test.patch Closes: #999522 (this message was generated automatically) -- Greetings https://bugs.debian.org/999522
Bug#995843: marked as done (abook: missing licenses in d/copyright)
Your message dated Sat, 27 Nov 2021 10:33:29 +
with message-id
and subject line Bug#995843: fixed in abook 0.6.1-2
has caused the Debian Bug report #995843,
regarding abook: missing licenses in d/copyright
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.)
--
995843: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=995843
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: abook
Severity: serious
Version: 0.6.1-1
abook contains distribution licenses that are not copied to
debian/copyright. At least BSD-2-clause (xmalloc.c, misc.c), old-style
MIT (ldif.c), FSFULLR (configure, Makefile.in), X11 (install-sh), and
probably others.
--- End Message ---
--- Begin Message ---
Source: abook
Source-Version: 0.6.1-2
Done: Rhonda D'Vine
We believe that the bug you reported is fixed in the latest version of
abook, 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 995...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Rhonda D'Vine (supplier of updated abook package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Sat, 27 Nov 2021 11:14:49 +0100
Source: abook
Architecture: source
Version: 0.6.1-2
Distribution: unstable
Urgency: low
Maintainer: Rhonda D'Vine
Changed-By: Rhonda D'Vine
Closes: 859407 979098 995843
Changes:
abook (0.6.1-2) unstable; urgency=low
.
[ Denis Briand ]
* Bump standards version to 4.6.0
* Fix SIGSEGV with undefined USER environment variable (Closes: #859407).
.
[ Bastian Germann ]
* Complete debian/copyright (Closes: #995843, #979098)
.
[ Rhonda D'Vine ]
* Bump debhelper-compat to 13.
* Move VCS to salsa.
* Convert debian/po/{de,fr,sv}.po to utf8.
* Bump watchfile version to 4.
Checksums-Sha1:
de625528ff4688e0b59d4c3f37f89183d577032c 1941 abook_0.6.1-2.dsc
6a7fa858d0135a2fde4311636c752d4b7fd5a7b6 16300 abook_0.6.1-2.debian.tar.xz
fe370a0f9212e84ede38b9395dc7e1b2e8efa613 6194 abook_0.6.1-2_amd64.buildinfo
Checksums-Sha256:
b59f97d51547f2a85ae51db1c6143b363410ee2354d20fcde0d803939c407a6b 1941
abook_0.6.1-2.dsc
63e9668af0c75df9e9368deaa0ebb90e4fc92c18081adc09519f36c5233b8041 16300
abook_0.6.1-2.debian.tar.xz
88ce71e6423d935c6f1b817dca08ea75ec196e465e64367578f7a853607a39f9 6194
abook_0.6.1-2_amd64.buildinfo
Files:
8a891b8685f5c9a423a38f00849d9681 1941 mail optional abook_0.6.1-2.dsc
3483b95b5cdff59203d9c60691c73988 16300 mail optional
abook_0.6.1-2.debian.tar.xz
1c3a1ba96a7181169dcd1cb2e76b76ac 6194 mail optional
abook_0.6.1-2_amd64.buildinfo
-BEGIN PGP SIGNATURE-
iQIzBAEBCAAdFiEELHLzKO0XByBPs0mU3ugEPuF+uzAFAmGiBh0ACgkQ3ugEPuF+
uzA4BQ//YGyluEnGlZIhrbybb3zvVrlkK27bpRBgUcZqFZWZ2J6/UQmPuiTt+brG
fOS+IamnQsItAEgWWuSOcNyGOcLWPkGzhFDSSVD2sJ+PDVoDKWtHtfZhhs3luJQT
VykGM8fsDJv6S7hoNrTexIykrZdi0losJVmTCUklwD+3tkEl7lYZyOq6dfk1v9mQ
Hn7jsPrL83lh7WUu9E1UvDVtusSnhHR0Bpy8q2mvqv7mL821DEFUN+1SAatWLhwh
6KS16JQGqBNYo6mU6DJzGvdCclWgSIk5nb0fgBKvn1uhLf9A8P1nHRYL4nKxlL0e
bgdyGl08l0IiryBo7OVlpQZ1unHAdOxPl6pBly2AQW7eCtE3q9B6TxG63JvUo7I5
t6lUIA7jXI8oIL5iVdWrOOuVmyEp5NixJgeZqTI1nBGXFm9XLy71N6qtdIsAZPOu
YRuyh0C6FasUeQMP1e/gP6U3vWfqDMKo6zWyB1xABrXvTmgZmna33q5fbCBqOa07
G3eQBOS4LZDt1PWZrsaoAZm525+cG2vwPgynwttP6XR5mpCUhCJ4Ijrd10QxWleK
RRLEU/mQO47eGvQEQPfntWmlTzBGHsijIl2ER3D4Fp6acVt0R7dbTjhWlDp/v6kx
YENWr/WZ1xW+Tg0eJhnN6zR74FfWs5gFCI5G+Wh5nv8uvAhYun4=
=NLv+
-END PGP SIGNATURE End Message ---
Bug#1000146: cppcheck: incorrect dependencies: libc6 should be >= 2.32
The root case of the problem has now been identified (see bug #100421). I'll upload a new version cppcheck with a workaround shortly (and before the autoremoval kicks in) -- just wanting to wait a bit more for a potential new upstream release. Best regards, Joachim
Processed: Bug#1000146: cppcheck: incorrect dependencies: libc6 should be >= 2.32
Processing commands for cont...@bugs.debian.org: > tag 1000146 pending Bug #1000146 [cppcheck] cppcheck: incorrect dependencies: libc6 should be >= 2.32 Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 1000146: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1000146 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1000289: marked as done (mbedtls: enabling CMAC support changes ABI)
Your message dated Sat, 27 Nov 2021 12:33:13 +0100 with message-id <777e2704-004d-4364-ec73-036e729cd...@debian.org> and subject line Re: shadowsocks-libev: autopkgtest failing on Testing after updating mbedtls has caused the Debian Bug report #1000289, regarding mbedtls: enabling CMAC support changes ABI 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.) -- 1000289: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1000289 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: shadowsocks-libev Version: 3.3.5+ds-6 Severity: normal -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Hi, I've recently updated the mbedtls package to the latest LTS version, and it seems that it has caused a regression for shadowsocks-libev. In fact, debci reports one failed test in autopkgtest. The failure is quite strange though, since I can't reproduce it locally, and every time the CI runs autopkgtest the failure is slightly different. The error message is generated by `curl`, and says "Unable to receive initial SOCKS5 response". It seems really strange to me that this regression was caused by updating libmbedcrypto, as the new LTS version only contains security and bug fixes. Also, the failure appears to be generated by `curl`, sometimes, when it tries to communicate with an external host (www.google.com). What could be the cause of the failures? - -- System Information: Debian Release: bookworm/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.14.0-4-amd64 (SMP w/4 CPU threads) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=it_IT.UTF-8, LC_CTYPE=it_IT.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled -BEGIN PGP SIGNATURE- iIoEARYIADIWIQRm3vFSgpkMIZnvqAGooSioqxzuSQUCYZlwMxQcYW5kcmVhQHBh cHBhY29kYS5pdAAKCRCooSioqxzuSZV0AQCxPe3UmcIxOJCvYH4UvZ2f6ZTxWHnX y8urnpXoRvU2FQEAkbX0tv80Fj5MLlOi0zID7K8Zl+/TSfQ/7PmPU+tFhgE= =azN+ -END PGP SIGNATURE- --- End Message --- --- Begin Message --- Version: 2.16.11-0.3--- End Message ---
Processed: cloning 1000560, reassign -1 to php-laravel-lumen-framework
Processing commands for cont...@bugs.debian.org: > clone 1000560 -1 Bug #1000560 [php-laravel-framework] Compatibility with Symfony 5 Bug 1000560 cloned as bug 1000696 > reassign -1 php-laravel-lumen-framework 6.3.5-2 Bug #1000696 [php-laravel-framework] Compatibility with Symfony 5 Bug reassigned from package 'php-laravel-framework' to 'php-laravel-lumen-framework'. No longer marked as found in versions php-laravel-framework/6.20.14+dfsg-2. Ignoring request to alter fixed versions of bug #1000696 to the same values previously set Bug #1000696 [php-laravel-lumen-framework] Compatibility with Symfony 5 Marked as found in versions php-laravel-lumen-framework/6.3.5-2. > thanks Stopping processing here. Please contact me if you need assistance. -- 1000560: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1000560 1000696: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1000696 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#992927: mutt: Mutt 2.1.2 is available, fixing a potential data-loss IMAP bug
On Tue, Nov 23, 2021 at 12:36:07PM -0800, Kevin J. McCarthy wrote: > On Tue, Nov 23, 2021 at 08:45:47PM +0100, Hannes von Haugwitz wrote: > > Is there any progress with this bug? > > Mutt 2.1.3 included the corrected sort commit referenced in my last email. > So, for unstable/testing it would be nice to get 2.1.3 uploaded. > > For stable/oldstable I guess it rests in the hands of Debian process, but > ideally the three links from my last email would be backported to those. > > -Kevin Updating to mutt 2.1.3 as we speak, I will prepare the fix for the stable/oldstable as well, that will go through the standard process; thanks for referencing those commits.
Processed: your mail
Processing commands for cont...@bugs.debian.org: > notfound 999606 fetchmail/6.4.24-1 Bug #999606 [fetchmail] fetchmail: configuration requires TLS for SSH authentication Ignoring request to alter found versions of bug #999606 to the same values previously set > End of message, stopping processing here. Please contact me if you need assistance. -- 999606: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=999606 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: your mail
Processing commands for cont...@bugs.debian.org: > notfound 999606 fetchmail/6.4.23-1 Bug #999606 [fetchmail] fetchmail: configuration requires TLS for SSH authentication Ignoring request to alter found versions of bug #999606 to the same values previously set > End of message, stopping processing here. Please contact me if you need assistance. -- 999606: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=999606 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: some aiohttp rdeps affected by the failure to import
Processing commands for cont...@bugs.debian.org: > affects 1000680 + python3-matrix-nio weechat-matrix Bug #1000680 [python3-aiohttp] python3-aiohttp: fails to import, "TypeError: function() argument 'code' must be code, not str" Added indication that 1000680 affects python3-matrix-nio and weechat-matrix > thanks Stopping processing here. Please contact me if you need assistance. -- 1000680: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1000680 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#992927: marked as done (mutt: Mutt 2.1.2 is available, fixing a potential data-loss IMAP bug)
Your message dated Sat, 27 Nov 2021 12:53:55 + with message-id and subject line Bug#992927: fixed in mutt 2.1.3-1 has caused the Debian Bug report #992927, regarding mutt: Mutt 2.1.2 is available, fixing a potential data-loss IMAP bug 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.) -- 992927: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=992927 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: mutt Version: 2.0.5-4.1 Severity: grave Justification: causes non-serious data loss Mutt 2.1.2 is available. From the announce: "This is an important bug-fix release, fixing a potential data-loss IMAP bug. IMAP users are strongly advised to upgrade." For stable and oldstable: "Packagers, please consider backporting commit 647efbd1 if at all possible." See http://lists.mutt.org/pipermail/mutt-announce/Week-of-Mon-20210823/40.html for additional information. Note also that there is a minor "mutt -v" output issue with the current Mutt and, in particular, GNU Autoconf 2.71, which is now in unstable. I fixed this issue in Mutt's repository yesterday and I'm going to report a second bug for that. -- Package-specific info: Mutt 2.1.1+55 (898eb3ca) vl-138565 (2021-08-24) Copyright (C) 1996-2021 Michael R. Elkins and others. Mutt comes with ABSOLUTELY NO WARRANTY; for details type `mutt -vv'. Mutt is free software, and you are welcome to redistribute it under certain conditions; type `mutt -vv' for details. System: Linux 5.10.0-8-amd64 (x86_64) ncurses: ncurses 6.2.20201114 (compiled with 6.2) libidn: 1.38 (compiled with 1.38) Compiler: Using built-in specs. COLLECT_GCC=gcc COLLECT_LTO_WRAPPER=/usr/lib/gcc/x86_64-linux-gnu/10/lto-wrapper OFFLOAD_TARGET_NAMES=nvptx-none:amdgcn-amdhsa:hsa OFFLOAD_TARGET_DEFAULT=1 Target: x86_64-linux-gnu Configured with: ../src/configure -v --with-pkgversion='Debian 10.2.1-6' --with-bugurl=file:///usr/share/doc/gcc-10/README.Bugs --enable-languages=c,ada,c++,go,brig,d,fortran,objc,obj-c++,m2 --prefix=/usr --with-gcc-major-version-only --program-suffix=-10 --program-prefix=x86_64-linux-gnu- --enable-shared --enable-linker-build-id --libexecdir=/usr/lib --without-included-gettext --enable-threads=posix --libdir=/usr/lib --enable-nls --enable-bootstrap --enable-clocale=gnu --enable-libstdcxx-debug --enable-libstdcxx-time=yes --with-default-libstdcxx-abi=new --enable-gnu-unique-object --disable-vtable-verify --enable-plugin --enable-default-pie --with-system-zlib --enable-libphobos-checking=release --with-target-system-zlib=auto --enable-objc-gc=auto --enable-multiarch --disable-werror --with-arch-32=i686 --with-abi=m64 --with-multilib-list=m32,m64,mx32 --enable-multilib --with-tune=generic --enable-offload-targets=nvptx-none=/build/gcc-10-Km9U7s/gcc-10-10.2.1/debian/tmp-nvptx/usr,amdgcn-amdhsa=/build/gcc-10-Km9U7s/gcc-10-10.2.1/debian/tmp-gcn/usr,hsa --without-cuda-driver --enable-checking=release --build=x86_64-linux-gnu --host=x86_64-linux-gnu --target=x86_64-linux-gnu --with-build-config=bootstrap-lto-lean --enable-link-mutex Thread model: posix Supported LTO compression algorithms: zlib zstd gcc version 10.2.1 20210110 (Debian 10.2.1-6) Configure options: '--prefix=/home/vinc17 --enable-debug --enable-pop --enable-imap --with-ssl --enable-compressed --with-exec-shell=/home/vinc17/bin/sh.screen --enable-gpgme --with-system-dotlock=/usr/bin/mutt_dotlock CC=gcc '\''CFLAGS=-g -O3 -march=native -fsanitize=undefined -fno-sanitize-recover'\''' Compilation CFLAGS: -Wall -pedantic -Wno-long-long -g -O3 -march=native -fsanitize=undefined -fno-sanitize-recover Compile options: -DOMAIN +DEBUG -HOMESPOOL +USE_SETGID +USE_DOTLOCK +DL_STANDALONE +USE_FCNTL -USE_FLOCK +USE_POP +USE_IMAP -USE_SMTP +USE_SSL_OPENSSL -USE_SSL_GNUTLS -USE_SASL -USE_GSS +HAVE_GETADDRINFO +HAVE_REGCOMP -USE_GNU_REGEX +HAVE_COLOR +HAVE_START_COLOR +HAVE_TYPEAHEAD +HAVE_BKGDSET +HAVE_CURS_SET +HAVE_META +HAVE_RESIZETERM +HAVE_FUTIMENS +CRYPT_BACKEND_CLASSIC_PGP +CRYPT_BACKEND_CLASSIC_SMIME +CRYPT_BACKEND_GPGME -EXACT_ADDRESS -SUN_ATTACHMENT +ENABLE_NLS -LOCALES_HACK +HAVE_WC_FUNCS +HAVE_LANGINFO_CODESET +HAVE_LANGINFO_YESEXPR +HAVE_ICONV -ICONV_NONTRANS +HAVE_LIBIDN -HAVE_LIBIDN2 +HAVE_GETSID -USE_HCACHE -USE_SIDEBAR +USE_COMPRESSED +USE_INOTIFY ISPELL="/usr/bin/ispell" SENDMAIL="/usr/sbin/sendmail" MAILPATH="/var/mail" PKGDATADIR="/home/vinc17/share/mutt" SYSCONFDIR="/home/vinc17/etc" EXECSHELL="/home/vinc17/bin/sh.screen" -MIXMASTER To contact the developers, please mail to . To report a bug, please contac
Bug#996154: obexftp: FTBFS: ld: final link failed: bad value
Control: reassign -1 libopenobex2-dev 1.7.2-2
Control: retitle -1 libopenobex2-dev: openobex-target-release.cmake forces
static linking
Control: affects -1 src:obexftp
Control: tags -1 patch
On Mon, Oct 11, 2021 at 10:33:44AM -0300, Antonio Terceiro wrote:
>...
> Relevant part (hopefully):
> > /usr/bin/ld: /usr/lib/x86_64-linux-gnu/libopenobex.a(api.c.o): relocation
> > R_X86_64_PC32 against symbol `stderr@@GLIBC_2.2.5' can not be used when
> > making a shared object; recompile with -fPIC
> > /usr/bin/ld: final link failed: bad value
> > collect2: error: ld returned 1 exit status
>...
This is not a problem in obexftp, this is a regressiong in libopenobex
which installs files in the wrong order forcing usage of the static
library in the cmake files - which doesn't work when linking a shared
library.
$ grep -r libopenobex /usr/lib/x86_64-linux-gnu/cmake/OpenObex-1.7.2
/usr/lib/x86_64-linux-gnu/cmake/OpenObex-1.7.2/openobex-target-release.cmake:
IMPORTED_LOCATION_RELEASE "${_IMPORT_PREFIX}/lib/x86_64-linux-gnu/libopenobex.a"
/usr/lib/x86_64-linux-gnu/cmake/OpenObex-1.7.2/openobex-target-release.cmake:list(APPEND
_IMPORT_CHECK_FILES_FOR_openobex
"${_IMPORT_PREFIX}/lib/x86_64-linux-gnu/libopenobex.a" )
$
Fix is below.
cu
Adrian
--- debian/rules.old2021-11-27 01:10:36.888770748 +
+++ debian/rules2021-11-27 01:10:53.572753176 +
@@ -37,6 +37,6 @@
dh_auto_build -B $(BUILDDIR)-static
override_dh_auto_install:
- dh_auto_install -B $(BUILDDIR)
dh_auto_install -B $(BUILDDIR)-static
+ dh_auto_install -B $(BUILDDIR)
cp -v $(BUILDDIR)-static/lib/*.a
debian/tmp/usr/lib/$(DEB_HOST_MULTIARCH)/
Processed: Re: Bug#996154: obexftp: FTBFS: ld: final link failed: bad value
Processing control commands: > reassign -1 libopenobex2-dev 1.7.2-2 Bug #996154 [src:obexftp] obexftp: FTBFS with ruby3.0: ld: final link failed: bad value Bug reassigned from package 'src:obexftp' to 'libopenobex2-dev'. No longer marked as found in versions obexftp/0.24-6. Ignoring request to alter fixed versions of bug #996154 to the same values previously set Bug #996154 [libopenobex2-dev] obexftp: FTBFS with ruby3.0: ld: final link failed: bad value Marked as found in versions libopenobex/1.7.2-2. > retitle -1 libopenobex2-dev: openobex-target-release.cmake forces static > linking Bug #996154 [libopenobex2-dev] obexftp: FTBFS with ruby3.0: ld: final link failed: bad value Changed Bug title to 'libopenobex2-dev: openobex-target-release.cmake forces static linking' from 'obexftp: FTBFS with ruby3.0: ld: final link failed: bad value'. > affects -1 src:obexftp Bug #996154 [libopenobex2-dev] libopenobex2-dev: openobex-target-release.cmake forces static linking Added indication that 996154 affects src:obexftp > tags -1 patch Bug #996154 [libopenobex2-dev] libopenobex2-dev: openobex-target-release.cmake forces static linking Added tag(s) patch. -- 996154: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=996154 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1000701: node-mdn-data: Wrong license, package is covered by CC-1.0, not MPL-2.0
Source: node-mdn-data Version: 2.0.23-1 Severity: serious Justification: Policy 2.3 debian/copyright is wrong, package is covered by CC-1.0-Universal, not MPL-2.0
Bug#1000702: src:sonic-visualiser: fails to migrate to testing for too long: FTBFS on armel and mipsel
Source: sonic-visualiser Version: 4.2-1 Severity: serious Tags: sid bookworm ftbfs User: release.debian@packages.debian.org Usertags: out-of-sync Dear maintainer(s), The Release Team considers packages that are out-of-sync between testing and unstable for more than 60 days as having a Release Critical bug in testing [1]. Your package src:sonic-visualiser has been trying to migrate for 61 days [2]. Hence, I am filing this bug. Your package FTBFS on armel and mipsel. If a package is out of sync between unstable and testing for a longer period, this usually means that bugs in the package in testing cannot be fixed via unstable. Additionally, blocked packages can have impact on other packages, which makes preparing for the release more difficult. Finally, it often exposes issues with the package and/or its (reverse-)dependencies. We expect maintainers to fix issues that hamper the migration of their package in a timely manner. This bug will trigger auto-removal when appropriate. As with all new bugs, there will be at least 30 days before the package is auto-removed. I have tagged this bug to only affect sid and bookworm, so it doesn't affect (old-)stable. If you believe your package is unable to migrate to testing due to issues beyond your control, don't hesitate to contact the Release Team. Paul [1] https://lists.debian.org/debian-devel-announce/2020/02/msg5.html [2] https://qa.debian.org/excuses.php?package=sonic-visualiser OpenPGP_signature Description: OpenPGP digital signature
Bug#1000701: marked as pending in node-mdn-data
Control: tag -1 pending Hello, Bug #1000701 in node-mdn-data reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/js-team/node-mdn-data/-/commit/91b06134e9d1ad5d9da8dd57d903d6e0209897f6 Fix license Closes: #1000701 (this message was generated automatically) -- Greetings https://bugs.debian.org/1000701
Processed: Bug#1000701 marked as pending in node-mdn-data
Processing control commands: > tag -1 pending Bug #1000701 [src:node-mdn-data] node-mdn-data: Wrong license, package is covered by CC-1.0, not MPL-2.0 Added tag(s) pending. -- 1000701: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1000701 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1000701: marked as pending in node-css-tree
Control: tag -1 pending Hello, Bug #1000701 in node-css-tree reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/js-team/node-css-tree/-/commit/fbb2270acc1a44f7915faeaf6076495623185bd8 Package upstream 1.1.3 (Closes: #1000701) (this message was generated automatically) -- Greetings https://bugs.debian.org/1000701
Processed: Bug#1000701 marked as pending in node-css-tree
Processing control commands:
> tag -1 pending
Bug #1000701 {Done: Yadd } [src:node-mdn-data] node-mdn-data:
Wrong license, package is covered by CC-1.0, not MPL-2.0
Added tag(s) pending.
--
1000701: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1000701
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#1000701: marked as done (node-mdn-data: Wrong license, package is covered by CC-1.0, not MPL-2.0)
Your message dated Sat, 27 Nov 2021 15:04:39 + with message-id and subject line Bug#1000701: fixed in node-mdn-data 2.0.23-3 has caused the Debian Bug report #1000701, regarding node-mdn-data: Wrong license, package is covered by CC-1.0, not MPL-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.) -- 1000701: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1000701 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: node-mdn-data Version: 2.0.23-1 Severity: serious Justification: Policy 2.3 debian/copyright is wrong, package is covered by CC-1.0-Universal, not MPL-2.0 --- End Message --- --- Begin Message --- Source: node-mdn-data Source-Version: 2.0.23-3 Done: Yadd We believe that the bug you reported is fixed in the latest version of node-mdn-data, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 1000...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Yadd (supplier of updated node-mdn-data package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sat, 27 Nov 2021 15:31:50 +0100 Source: node-mdn-data Architecture: source Version: 2.0.23-3 Distribution: unstable Urgency: medium Maintainer: Debian Javascript Maintainers Changed-By: Yadd Closes: 1000701 Changes: node-mdn-data (2.0.23-3) unstable; urgency=medium . * Team upload * Add debian/gbp.conf * Drop dependency to nodejs * Use dh-sequence-nodejs auto install * Fix license (Closes: #1000701) Checksums-Sha1: 3430f21cdfc1f12f093ad2ea7914c8c9b0ba5ceb 2061 node-mdn-data_2.0.23-3.dsc c7f315cf2d1ff50ca72e4a77e3e197ff9f7bf576 4572 node-mdn-data_2.0.23-3.debian.tar.xz Checksums-Sha256: dc5049bf66be9deac546dbeeb776a07d88ed4280bdca0dc7866ae84bbdff83d6 2061 node-mdn-data_2.0.23-3.dsc 58169cc5411f5d5c61ed15cbab6254ccab542917a0a7ab709b39fbb2ae27e784 4572 node-mdn-data_2.0.23-3.debian.tar.xz Files: be4c6a5fa15658affd4d3afba731a523 2061 javascript optional node-mdn-data_2.0.23-3.dsc 2070fe454751e60f01ad87b9f4cdd19f 4572 javascript optional node-mdn-data_2.0.23-3.debian.tar.xz -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEAN/li4tVV3nRAF7J9tdMp8mZ7ukFAmGiQZYACgkQ9tdMp8mZ 7ukyRg//a5kIRMz8ZZTOGvBgsJ3m9SD7NVm6ePPUcWN7aG6mignDgcZ8m96S2DX4 AgFmJjWRDBrlWM6L6y6WE+8WUT5H8uyRardS3DrWZc9yd/vQA+2+GdVP824I1jiW k+k8JAVUIW28wqKfaJweE44uLPVPsoLmUA8kH47BBqeRJLUVVz+UcmJVAFUFKUWS y/4I2uV/BiOWHXeG52mPhXqaHDRlCT/j7DMd5ECaOZjAjyrV9f04TuzhM3Knn41X YMFsBI3nNaEtLiYDRGhJcxuxmlhSELGUsdyqubjYHTjUEGDqljQQ+uRorB8hnKPl QkonO1HT8KzJTM/fAA+w4nEol1pLL/a0K3UcabWZ66kx7Jl0XLwTqXx0kGFS/Hoc xxsOdsO79n9JxFziZSzdg2y0qaPhnqxbbyrPvO7CuOsxCv3CMKAQrqzXPcuV0wtu zWOiGV8ulw6YaGajTVQ+HqzHIv79XPbUI4OF7ithUq1VMpQfX0A4dqVZQqvzKibv K8jC040xIkx8w8fVVAiDad00ROTL/FkP1DT61yIPIo/s16ti2UQDqfn271SuYf8A v9Ioom0ldV91TC0vJDSft8ilMcOTkQtq40Rxi52Qyz+PdV7LDfxNBkFnmBKwURyH WC2xlaeqSxQoODF1jucyfPmLd5NeO4Dw7Rc1DIcAfS22uk7sSdI= =0FOP -END PGP SIGNATURE End Message ---
Processed: tagging 997389
Processing commands for cont...@bugs.debian.org: > tags 997389 + pending Bug #997389 [src:xrdesktop] xrdesktop: FTBFS: dh_install: error: missing files, aborting Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 997389: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997389 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#995475: marked as done (bash-static: segfault on startup when running with glibc 2.32)
Your message dated Sat, 27 Nov 2021 17:09:29 +0100 with message-id and subject line fixed has caused the Debian Bug report #995475, regarding bash-static: segfault on startup when running with glibc 2.32 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 995475: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=995475 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: bash-static Version: 5.1-3+b1 Severity: grave Justification: renders package unusable X-Debbugs-Cc: ge...@google.com ``` $ bash-static Segmentation fault (core dumped) ``` A simple rebuild of the package against the new glibc version seems to fix the issue for me. -- System Information: Debian Release: bookworm/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'unstable'), (1, 'experimental-debug'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 5.13.0-trunk-amd64 (SMP w/8 CPU threads) 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) LSM: AppArmor: enabled Versions of packages bash-static depends on: ii passwd 1:4.8.1-1 bash-static recommends no packages. Versions of packages bash-static suggests: pn bash-doc -- no debconf information --- End Message --- --- Begin Message --- Version: 5.1-5--- End Message ---
Bug#996878: closed by Debian FTP Masters (reply to Thomas Andrejak ) (Bug#996878: fixed in libprelude 5.2.0-5)
Hi, Thanks for this fix ! I'll test it as soon as the compiled package enters unstable. Cheers, François Le 27/11/2021 à 10:39, Debian Bug Tracking System a écrit : > This is an automatic notification regarding your Bug report > which was filed against the python3-prelude package: > > #996878: python3-prelude: python3 import prelude throws an ImportError > exception > > It has been closed by Debian FTP Masters > (reply to Thomas Andrejak ). > > Their explanation is attached below along with your original report. > If this explanation is unsatisfactory and you have not received a > better one in a separate message then please contact Debian FTP Masters > (reply to Thomas Andrejak > ) by > replying to this email. > >
Processed: Re: statsmodels FTBFS - tests fail
Processing control commands: > forwarded -1 https://github.com/statsmodels/statsmodels/issues/7911 Bug #997081 [src:statsmodels] statsmodels: FTBFS: tests fail Set Bug forwarded-to-address to 'https://github.com/statsmodels/statsmodels/issues/7911'. -- 997081: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997081 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#997177: marked as done (pacvim: FTBFS: src/game.cpp:237:15: error: format not a string literal and no format arguments [-Werror=format-security])
Your message dated Sat, 27 Nov 2021 17:03:37 + with message-id and subject line Bug#997177: fixed in pacvim 1.1.1-1.1 has caused the Debian Bug report #997177, regarding pacvim: FTBFS: src/game.cpp:237:15: error: format not a string literal and no format arguments [-Werror=format-security] 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.) -- 997177: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997177 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: pacvim Version: 1.1.1-1 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > g++ -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong > -Wformat -Werror=format-security -std=c++11 > -DMAPS_LOCATION='"/usr//share/pacvim-maps"' -pthread -Wdate-time > -D_FORTIFY_SOURCE=2 -c -o src/helperFns.o src/helperFns.cpp > src/game.cpp: In function ‘void levelMessage()’: > src/game.cpp:237:15: error: format not a string literal and no format > arguments [-Werror=format-security] > 237 | printw(msg.c_str()); > | ~~^ > src/helperFns.cpp: In function ‘void printAtBottomChar(char)’: > src/helperFns.cpp:103:17: error: format not a string literal and no format > arguments [-Werror=format-security] > 103 | mvprintw(TOP+5, 0, (x).c_str()); > | ^~~ > src/helperFns.cpp: In function ‘void printAtBottom(std::string)’: > src/helperFns.cpp:110:17: error: format not a string literal and no format > arguments [-Werror=format-security] > 110 | mvprintw(TOP+1, 1, msg.c_str()); > | ^~~ > cc1plus: some warnings being treated as errors > make[1]: *** [: src/helperFns.o] Error 1 The full build log is available from: http://qa-logs.debian.net/2021/10/23/pacvim_1.1.1-1_unstable.log A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! If you reassign this bug to another package, please marking it as 'affects'-ing this package. See https://www.debian.org/Bugs/server-control#affects If you fail to reproduce this, please provide a build log and diff it with mine so that we can identify if something relevant changed in the meantime. --- End Message --- --- Begin Message --- Source: pacvim Source-Version: 1.1.1-1.1 Done: Boyuan Yang We believe that the bug you reported is fixed in the latest version of pacvim, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 997...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Boyuan Yang (supplier of updated pacvim package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sat, 13 Nov 2021 10:58:52 -0500 Source: pacvim Architecture: source Version: 1.1.1-1.1 Distribution: unstable Urgency: medium Maintainer: kokoye2007 Changed-By: Boyuan Yang Closes: 997177 Changes: pacvim (1.1.1-1.1) unstable; urgency=medium . * Non-maintainer upload. * debian/rules: Circumvent FTBFS caused by -Werror=format-security. (Closes: #997177) Checksums-Sha1: 93af5d5fc21a2483e1f32150310ec9bddf30b681 2100 pacvim_1.1.1-1.1.dsc 05973ca02242d629c40806267d2137e468f87309 248696 pacvim_1.1.1.orig.tar.xz 50e88c2b0aa8d0c24871c7a4e345d585ad5bc1c5 1684 pacvim_1.1.1.orig.tar.xz.asc 6d26c3b3ca2356615bf761949be987b1e216e36f 3988 pacvim_1.1.1-1.1.debian.tar.xz 884af483d5501a80eb85ea769c3187c6735bc527 6192 pacvim_1.1.1-1.1_amd64.buildinfo Checksums-Sha256: 8e4cf73811c525217d38e547cfb7c1174dea785ca50232569aad6186ae8113e6 2100 pacvim_1.1.1-1.1.dsc 0bfa641b360ebcebd8ff6c9c4bea4a467385a429d256f08b5490a354f13e1582 248696 pacvim_1.1.1.orig.tar.xz 94197302c395d4adb8a43e23ca47dda80fa7b34fec0f8137f4ec4d8151901076 1684 pacvim_1.1.1.orig.tar.xz.asc 1511ba447b67dd5eedd800d6c7bd74adc70db0024e0561858f0148d761f6aa7a 3988 pacvim_1.1.1-1.1.debian.tar.xz 2d97aed68dc97881da1f3f93aacf4b0880688481c2e6a300bbef64cb54799e8e 6192 pacvim_1.1.1-1.1_amd64.buildinfo Files: f3ad532c45f4bfebb430baed6006b1cc 2100 gam
Processed: bug 996380 is forwarded to https://github.com/dtao/safe_yaml/issues/100
Processing commands for cont...@bugs.debian.org: > forwarded 996380 https://github.com/dtao/safe_yaml/issues/100 Bug #996380 [src:ruby-safe-yaml] ruby-safe-yaml: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed: ArgumentError: Set Bug forwarded-to-address to 'https://github.com/dtao/safe_yaml/issues/100'. > thanks Stopping processing here. Please contact me if you need assistance. -- 996380: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=996380 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#998682: marked as done (libgetdata: b-d on python3-all-dev, but not built for all supported Python3 versions)
Your message dated Sat, 27 Nov 2021 19:03:31 + with message-id and subject line Bug#998682: fixed in libgetdata 0.11.0-2 has caused the Debian Bug report #998682, regarding libgetdata: b-d on python3-all-dev, but not built for all supported Python3 versions to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 998682: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=998682 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: libgetdata Version: 0.10.0-11 Severity: important Tags: ftbfs User: debian-pyt...@lists.debian.org Usertags: python3.10 python3-all-dev Hi Maintainer This package build-depends on python3-all-dev, but does not build extensions/libraries for all supported python3 versions. This is seen on the transition tracker for adding python3.10 support [1] and creates false positives. Please either replace the b-d python3-all-dev with python3-dev, or build for all supported Python3 versions. With the former solution you get later exposure to a new python3 version, with the latter solution you get early exposure. Regards Graham [1] https://release.debian.org/transitions/html/python3.10-add.html --- End Message --- --- Begin Message --- Source: libgetdata Source-Version: 0.11.0-2 Done: Alastair McKinstry We believe that the bug you reported is fixed in the latest version of libgetdata, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 998...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Alastair McKinstry (supplier of updated libgetdata package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Sat, 27 Nov 2021 16:50:38 + Source: libgetdata Architecture: source Version: 0.11.0-2 Distribution: unstable Urgency: medium Maintainer: Debian Science Maintainers Changed-By: Alastair McKinstry Closes: 998682 Changes: libgetdata (0.11.0-2) unstable; urgency=medium . * Standards-Version 4.6.0; no changes required * B-D on libpcre3-dev * Fix for python version handling in build: Closes: #998682 Checksums-Sha1: f15871a73feee89b7bc66a75f6cae53590f96128 2763 libgetdata_0.11.0-2.dsc 35c9a3eda4888c14a3608a117a0d8568283cb331 6840 libgetdata_0.11.0-2.debian.tar.xz Checksums-Sha256: 2b61bd33da78d900cc99c10d2139581d21ea400466a8a76e98335cf8f3bf9db5 2763 libgetdata_0.11.0-2.dsc 14af1f474608bce32b9208596fc5cff16a9b4968fccfae443c71528cb2aa5362 6840 libgetdata_0.11.0-2.debian.tar.xz Files: 134563c0c49464e6dd68c05df44850d7 2763 science optional libgetdata_0.11.0-2.dsc f934683d3a083885fd6d66852df9d425 6840 science optional libgetdata_0.11.0-2.debian.tar.xz -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEEgjg86RZbNHx4cIGiy+a7Tl2a06UFAmGifUYACgkQy+a7Tl2a 06VDMA//WQoxyMQ//v5FCo0zcJbtrF+BzVNp/GC5SnZ2ks4qxXvStH8L/PKsBkFX x9IsaduEmN3QHFUJwGOdlj+SEuVz+y/WKxMA5ImqfBYVjMEwNtAPSXlmHVuzmTpm buCebMzjp2n5YS03bezejwGfR885PmqUJM+y+l3wBlZYAXrArZ7iCM8FKmTf7phJ CZGg5z5rzvfCmfO9NSdpxG5dGLbXZ/CUe6EQT+nGorcGdmBQgfPFOc/FduqrPMFq 1g8PPNN1m66w8w7msBcppa2p5R3pzKrIjFcpIQ8u+wNfnxYcONXewx+FA6hyF8va hFOGQl6XPIL3XArD5A5y05O7g5xholyO7pjphPqtgzn9nItvRL2Q1FgTh6ZSW8AG bFC9EKCVJGavf43oc7/7/VDFJVrCCHhjomZ72Y37UXPzh/wPBValbVMy06kCm0Qs LJwOgRSm+A2zCKuuDsky+QHC7U/HsXG+B40cv0Hi9dzcrMSPo7XRbLpEGA2IwCgr tbERp9Xkb3V6IMNhtDjElj6wLkiwqDym3JwE54+knfWGCSRmqSvIDEfKergsVDjJ paevVSUonoIPz8mWROiTsL/oG2D4VxaUS44j/slvKrUmYhnbbiCFurNzJf/V/0sg Vjv9hQPyJrfP6V5xUFM6aWth9spNLqUEXhxkGMBf9LJUnB3w1+Y= =D9V2 -END PGP SIGNATURE End Message ---
Bug#1000255: mpv: autopkgtest failures
On 2021-11-23 15 h 22, Sebastian Ramacher wrote: > Control: reassign -1 src:python-mpv 0.5.2-1 > Control: forwarded -1 https://github.com/jaseg/python-mpv/issues/187 > > On 2021-11-21 23:21:24, Sebastian Ramacher wrote: >> Control: tags -1 help >> >> On 2021-11-20 09:34:37 +0100, Gianfranco Costamagna wrote: >>> Source: mpv >>> Version: 0.34.0-1 >>> Severity: serious >>> >>> >>> Hello, the last version 0.34.0 is regressed on arm64 armhf and probably >>> other architectures. >>> >>> Look, e.g. >>> https://ci.debian.net/data/autopkgtest/testing/arm64/p/python-mpv/16812363/log.gz >>> >>> (Reading database ... 16518 files and directories currently installed.) >>> Removing autopkgtest-satdep (0) ... >>> autopkgtest [18:11:22]: test unittests: [--- >>> === python3.9 === >>> Segmentation fault >>> autopkgtest [18:11:43]: test unittests: ---] >>> autopkgtest [18:11:43]: test unittests: - - - - - - - - - - results - - - >>> - - - - - - - >>> unittestsFAIL non-zero exit status 139 >>> autopkgtest [18:11:43]: summary >>> unittestsFAIL non-zero exit status 139 >>> >>> I don't know which update triggered the regression, if the program itself >>> or something else in the toolchain. >>> >>> Can you please have a look? >>> >>> https://ci.debian.net/packages/p/python-mpv/testing/arm64/ >> >> The failing test is test_write. It crashes due to an infinte recursion >> in libx11-6's XPutImage which calls PutSubImage: >> >> #0 0xf4f3e31c in PutSubImage (dpy=dpy@entry=0x5776b8, d=d@entry=2097154, >> gc=gc@entry=0x5a01e0, image=image@entry=0x5a2ca8, req_xoffset=0, >> req_yoffset=req_yoffset@entry=0, x=0, y=y@entry=0, req_width=2096928, >> req_height=req_height@entry=1, >> dest_bits_per_pixel=dest_bits_per_pixel@entry=32, >> dest_scanline_pad=dest_scanline_pad@entry=32) at ../../src/PutImage.c:878 >> #1 0xf4f3e7a4 in PutSubImage (dpy=dpy@entry=0x5776b8, d=d@entry=2097154, >> gc=gc@entry=0x5a01e0, image=image@entry=0x5a2ca8, req_xoffset=0, >> req_yoffset=req_yoffset@entry=0, x=0, y=y@entry=0, req_width=2096928, >> req_height=req_height@entry=1, >> dest_bits_per_pixel=dest_bits_per_pixel@entry=32, >> dest_scanline_pad=dest_scanline_pad@entry=32) at ../../src/PutImage.c:920 >> #2 0xf4f3e7a4 in PutSubImage (dpy=dpy@entry=0x5776b8, d=d@entry=2097154, >> gc=gc@entry=0x5a01e0, image=image@entry=0x5a2ca8, req_xoffset=0, >> req_yoffset=req_yoffset@entry=0, x=0, y=y@entry=0, req_width=2096928, >> req_height=req_height@entry=1, >> dest_bits_per_pixel=dest_bits_per_pixel@entry=32, >> dest_scanline_pad=dest_scanline_pad@entry=32) at ../../src/PutImage.c:920 >> #3 0xf4f3e7a4 in PutSubImage (dpy=dpy@entry=0x5776b8, d=d@entry=2097154, >> gc=gc@entry=0x5a01e0, image=image@entry=0x5a2ca8, req_xoffset=0, >> req_yoffset=req_yoffset@entry=0, x=0, y=y@entry=0, req_width=2096928, >> req_height=req_height@entry=1, >> dest_bits_per_pixel=dest_bits_per_pixel@entry=32, >> dest_scanline_pad=dest_scanline_pad@entry=32) at ../../src/PutImage.c:920 >> #4 0xf4f3e7a4 in PutSubImage (dpy=dpy@entry=0x5776b8, d=d@entry=2097154, >> gc=gc@entry=0x5a01e0, image=image@entry=0x5a2ca8, req_xoffset=0, >> req_yoffset=req_yoffset@entry=0, x=0, y=y@entry=0, req_width=2096928, >> req_height=req_height@entry=1, >> dest_bits_per_pixel=dest_bits_per_pixel@entry=32, >> dest_scanline_pad=dest_scanline_pad@entry=32) at ../../src/PutImage.c:920 >> #5 0xf4f3e7a4 in PutSubImage (dpy=dpy@entry=0x5776b8, d=d@entry=2097154, >> gc=gc@entry=0x5a01e0, image=image@entry=0x5a2ca8, req_xoffset=0, >> req_yoffset=req_yoffset@entry=0, x=0, y=y@entry=0, req_width=2096928, >> req_height=req_height@entry=1, >> dest_bits_per_pixel=dest_bits_per_pixel@entry=32, >> dest_scanline_pad=dest_scanline_pad@entry=32) at ../../src/PutImage.c:920 >> #6 0xf4f3e7a4 in PutSubImage (dpy=dpy@entry=0x5776b8, d=d@entry=2097154, >> gc=gc@entry=0x5a01e0, image=image@entry=0x5a2ca8, req_xoffset=0, >> req_yoffset=req_yoffset@entry=0, x=0, y=y@entry=0, req_width=2096928, >> req_height=req_height@entry=1, >> dest_bits_per_pixel=dest_bits_per_pixel@entry=32, >> dest_scanline_pad=dest_scanline_pad@entry=32) at ../../src/PutImage.c:920 >> #7 0xf4f3e7a4 in PutSubImage (dpy=dpy@entry=0x5776b8, d=d@entry=2097154, >> gc=gc@entry=0x5a01e0, image=image@entry=0x5a2ca8, req_xoffset=0, >> req_yoffset=req_yoffset@entry=0, x=0, y=y@entry=0, req_width=2096928, >> req_height=req_height@entry=1, >> dest_bits_per_pixel=dest_bits_per_pixel@entry=32, >> dest_scanline_pad=dest_scanline_pad@entry=32) at ../../src/PutImage.c:920 >> #8 0xf4f3e7a4 in PutSubImage (dpy=dpy@entry=0x5776b8, d=d@entry=2097154, >> gc=gc@entry=0x5a01e0, image=image@entry=0x5a2ca8, req_xoffset=0, >> req_yoffset=req_yoffset@entry=0, x=0, y=y@entry=0, req_width=2096928, >> req_height=req_height@entry=1, >> dest_bits_per_pixel=dest_bits_pe
Processed: tagging 996380
Processing commands for cont...@bugs.debian.org: > # https://github.com/paolobrasolin/safe_yaml/compare/master...development > tags 996380 + patch Bug #996380 [src:ruby-safe-yaml] ruby-safe-yaml: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed: ArgumentError: Added tag(s) patch. > thanks Stopping processing here. Please contact me if you need assistance. -- 996380: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=996380 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1000237: marked as done (pygame: FTBFS with python3.10)
Your message dated Sat, 27 Nov 2021 19:17:32 +
with message-id <2ae5befc-4649-5a47-0b23-4edf7b338...@debian.org>
and subject line pygame: FTBFS with python3.10
has caused the Debian Bug report #1000237,
regarding pygame: FTBFS with python3.10
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
1000237: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1000237
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: pygame
Version: 1.9.6+dfsg-4
Severity: serious
Tags: patch
Justification: FTBFS
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu jammy ubuntu-patch
Dear maintainers,
Now that python3.10 is a supported python version in unstable, pygame fails
to build from source.
I wasn't able to find a direct fix for these issues in the upstream git, so
I've prepared the attached patch instead. I've uploaded this patch to
Ubuntu to fix the failure in question. Please consider including it in
Debian as well.
Thanks,
--
Steve Langasek Give me a lever long enough and a Free OS
Debian Developer to set it on, and I can move the world.
Ubuntu Developer https://www.debian.org/
slanga...@ubuntu.com vor...@debian.org
diff -Nru pygame-1.9.6+dfsg/debian/patches/python-3.10.patch
pygame-1.9.6+dfsg/debian/patches/python-3.10.patch
--- pygame-1.9.6+dfsg/debian/patches/python-3.10.patch 1969-12-31
16:00:00.0 -0800
+++ pygame-1.9.6+dfsg/debian/patches/python-3.10.patch 2021-11-19
17:24:50.0 -0800
@@ -0,0 +1,115 @@
+Description: fix compatibility with python 3.10
+ Python 3.10 requires use of Py_ssize_t instead of int.
+ Also, certain math operations are now returning floats instead of ints,
+ so adjust.
+Author: Steve Langasek
+Last-Update: 2021-11-19
+
+Index: pygame-1.9.6+dfsg/src_c/mixer.c
+===
+--- pygame-1.9.6+dfsg.orig/src_c/mixer.c
pygame-1.9.6+dfsg/src_c/mixer.c
+@@ -24,6 +24,7 @@
+ * mixer module for pygame
+ */
+ #define PYGAMEAPI_MIXER_INTERNAL
++#define PY_SSIZE_T_CLEAN
+ #include "pygame.h"
+
+ #include "pgcompat.h"
+@@ -529,7 +530,7 @@
+ {
+ static char *kwids[] = {"frequency", "size", "channels",
+ "buffer","devicename", "allowedchanges",
NULL};
+-int dname_size = 0;
++Py_ssize_t dname_size = 0;
+
+ request_frequency = 0;
+ request_size = 0;
+Index: pygame-1.9.6+dfsg/src_c/sdlmain_osx.m
+===
+--- pygame-1.9.6+dfsg.orig/src_c/sdlmain_osx.m
pygame-1.9.6+dfsg/src_c/sdlmain_osx.m
+@@ -19,6 +19,7 @@
+
+ /* Mac OS X functions to accommodate the fact SDLMain.m is not included */
+
++#define PY_SSIZE_T_CLEAN
+ #include "pygame.h"
+
+ #include
+@@ -234,7 +235,7 @@
+ _InstallNSApplication(PyObject* self, PyObject* arg)
+ {
+ char* icon_data = NULL;
+-int data_len = 0;
++Py_ssize_t data_len = 0;
+ PYGPYGSDLApplicationDelegate *sdlApplicationDelegate = NULL;
+
+ NSAutoreleasePool *pool = [[NSAutoreleasePool alloc] init];
+Index: pygame-1.9.6+dfsg/src_c/overlay.c
+===
+--- pygame-1.9.6+dfsg.orig/src_c/overlay.c
pygame-1.9.6+dfsg/src_c/overlay.c
+@@ -23,6 +23,7 @@
+ * Dmitry Borisov
+ */
+
++#define PY_SSIZE_T_CLEAN
+ #include
+
+ #include "pygame.h"
+@@ -67,7 +68,8 @@
+ {
+ SDL_Rect cRect;
+ // Parse data params for frame
+-int ls_y, ls_u, ls_v, y;
++Py_ssize_t ls_y, ls_u, ls_v;
++int y;
+ unsigned char *src_y = 0, *src_u = 0, *src_v = 0;
+
+ if (PyTuple_Size(args)) {
+Index: pygame-1.9.6+dfsg/src_c/scrap.c
+===
+--- pygame-1.9.6+dfsg.orig/src_c/scrap.c
pygame-1.9.6+dfsg/src_c/scrap.c
+@@ -28,6 +28,7 @@
+
+ #include "SDL_syswm.h"
+
++#define PY_SSIZE_T_CLEAN
+ #include "scrap.h"
+
+ #include "pygame.h"
+@@ -276,7 +277,7 @@
+ static PyObject *
+ _scrap_put_scrap(PyObject *self, PyObject *args)
+ {
+-int scraplen;
++Py_ssize_t scraplen;
+ char *scrap = NULL;
+ char *scrap_type;
+ PyObject *tmp;
+Index: pygame-1.9.6+dfsg/src_py/sprite.py
+===
+--- pygame-1.9.6+dfsg.orig/src_py/sprite.py
pygame-1.9.6+dfsg/src_py/sprite.py
+@@ -1346,14 +1346,14 @@
+ leftrect = left.rect
+ width = leftrect.width
+ height = leftrect.height
+-leftrect = leftrect.inflate(wi
Bug#1000215: glusterfs: diff for NMU version 10.0-1.3
Control: tags 1000215 + patch Control: tags 1000215 + pending Dear maintainer, I've prepared an NMU for glusterfs (versioned as 10.0-1.3) and uploaded it to DELAYED/2. Please feel free to tell me if I should delay it longer. Cheers -- Sebastian Ramacher diff -Nru glusterfs-10.0/debian/changelog glusterfs-10.0/debian/changelog --- glusterfs-10.0/debian/changelog 2021-11-17 09:17:06.0 +0100 +++ glusterfs-10.0/debian/changelog 2021-11-27 19:20:47.0 +0100 @@ -1,3 +1,11 @@ +glusterfs (10.0-1.3) unstable; urgency=medium + + * Non-maintainer upload. + * debian/rules: Set -DUATOMIC_NO_LINK_ERROR on armel, armhf and mipsel +(Closes: #1000215) (LP: #1951408) + + -- Sebastian Ramacher Sat, 27 Nov 2021 19:20:47 +0100 + glusterfs (10.0-1.2) unstable; urgency=medium * d/rules: disable tcmalloc also on x86 avoiding issues in tgt diff -Nru glusterfs-10.0/debian/rules glusterfs-10.0/debian/rules --- glusterfs-10.0/debian/rules 2021-11-17 09:17:06.0 +0100 +++ glusterfs-10.0/debian/rules 2021-11-27 19:17:52.0 +0100 @@ -1,7 +1,13 @@ #!/usr/bin/make -f +include /usr/share/dpkg/architecture.mk include /usr/share/dpkg/pkg-info.mk +# Fix build on these arches (LP: #1951408) (#1000215) +ifneq (,$(filter $(DEB_HOST_ARCH), armel armhf mipsel)) +export DEB_CPPFLAGS_MAINT_APPEND = -DUATOMIC_NO_LINK_ERROR +endif + export DEB_BUILD_MAINT_OPTIONS = hardening=+all DEB_CONFIGURE_EXTRA_FLAGS := \ signature.asc Description: PGP signature
Processed: glusterfs: diff for NMU version 10.0-1.3
Processing control commands: > tags 1000215 + patch Bug #1000215 [src:glusterfs] glusterfs: FTBFS on armel, armhf, mipsel Added tag(s) patch. > tags 1000215 + pending Bug #1000215 [src:glusterfs] glusterfs: FTBFS on armel, armhf, mipsel Added tag(s) pending. -- 1000215: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1000215 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1000716: python3-pony: fails on Python 3.10 with "ModuleNotFoundError: No module named 'parser'"
Package: python3-pony Version: 0.7.14-1 Severity: serious User: debian-pyt...@lists.debian.org Usertags: python3.10 Hello, It seems the current version of ponyorm is broken on python3.10. If you look closely at the logs from the latest DebCI run [1], it outputs (without failing): > Sorry, but pony 0.7.14 requires Python of one of the following > versions: 2.7, 3.3-3.9. You have version 3.10.0+ Actually running pony on 3.10 outputs something like: == ERROR: tests (unittest.loader._FailedTest) -- ImportError: Failed to import test module: tests Traceback (most recent call last): File "/usr/lib/python3.10/unittest/loader.py", line 154, in loadTestsFromName module = __import__(module_name) File "/<>/tests/__init__.py", line 11, in from . import base File "/<>/tests/base/__init__.py", line 10, in from .test_cli import CLITestCase File "/<>/tests/base/test_cli.py", line 14, in from pony.orm import db_session File "/usr/lib/python3/dist-packages/pony/orm/__init__.py", line 3, in from pony.orm.core import * File "/usr/lib/python3/dist-packages/pony/orm/core.py", line 18, in from pony.thirdparty.compiler import ast, parse File "/usr/lib/python3/dist-packages/pony/thirdparty/compiler/__init__.py", line 24, in from .transformer import parse, parseFile File "/usr/lib/python3/dist-packages/pony/thirdparty/compiler/transformer.py", line 32, in import parser ModuleNotFoundError: No module named 'parser' This is because the parser module has been removed in Python 3.10 in favor of ast [2]. I'll suggest upstream to fail their testsuite when ran on Python 3.10. [1]: https://ci.debian.net/data/autopkgtest/unstable/amd64/p/ponyorm/17023056/log.gz [2]: https://docs.python.org/3/whatsnew/3.9.html#new-parser -- ⢀⣴⠾⠻⢶⣦⠀ ⣾⠁⢠⠒⠀⣿⡁ Louis-Philippe Véronneau ⢿⡄⠘⠷⠚⠋ po...@debian.org / veronneau.org ⠈⠳⣄ OpenPGP_signature Description: OpenPGP digital signature
Bug#1000717: supysonic: FTBFS on Python 3.10
Source: supysonic Version: 0.6.2+ds-4 Severity: serious User: debian-pyt...@lists.debian.org Usertags: python3.10 supysonic FTBFS when using Python 3.10. This is caused by python3-pony not supporting Python 3.10 yet. === python3.10 === tests (unittest.loader._FailedTest) ... ERROR == ERROR: tests (unittest.loader._FailedTest) -- ImportError: Failed to import test module: tests Traceback (most recent call last): File "/usr/lib/python3.10/unittest/loader.py", line 154, in loadTestsFromName module = __import__(module_name) File "/tmp/autopkgtest-lxc.l2p5og5f/downtmp/autopkgtest_tmp/tests/__init__.py", line 11, in from . import base File "/tmp/autopkgtest-lxc.l2p5og5f/downtmp/autopkgtest_tmp/tests/base/__init__.py", line 10, in from .test_cli import CLITestCase File "/tmp/autopkgtest-lxc.l2p5og5f/downtmp/autopkgtest_tmp/tests/base/test_cli.py", line 14, in from pony.orm import db_session File "/usr/lib/python3/dist-packages/pony/orm/__init__.py", line 3, in from pony.orm.core import * File "/usr/lib/python3/dist-packages/pony/orm/core.py", line 18, in from pony.thirdparty.compiler import ast, parse File "/usr/lib/python3/dist-packages/pony/thirdparty/compiler/__init__.py", line 24, in from .transformer import parse, parseFile File "/usr/lib/python3/dist-packages/pony/thirdparty/compiler/transformer.py", line 32, in import parser ModuleNotFoundError: No module named 'parser' -- ⢀⣴⠾⠻⢶⣦⠀ ⣾⠁⢠⠒⠀⣿⡁ Louis-Philippe Véronneau ⢿⡄⠘⠷⠚⠋ po...@debian.org / veronneau.org ⠈⠳⣄ OpenPGP_signature Description: OpenPGP digital signature
Processed: tagging 984371
Processing commands for cont...@bugs.debian.org:
> tags 984371 + fixed
Bug #984371 {Done: Adrian Bunk } [src:trafficserver]
trafficserver: ftbfs with GCC-11
Added tag(s) fixed.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
984371: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=984371
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#1000255: marked as done (mpv: autopkgtest failures)
Your message dated Sat, 27 Nov 2021 19:49:03 + with message-id and subject line Bug#1000255: fixed in python-mpv 0.5.2-2 has caused the Debian Bug report #1000255, regarding mpv: autopkgtest failures 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.) -- 1000255: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1000255 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: mpv Version: 0.34.0-1 Severity: serious Hello, the last version 0.34.0 is regressed on arm64 armhf and probably other architectures. Look, e.g. https://ci.debian.net/data/autopkgtest/testing/arm64/p/python-mpv/16812363/log.gz (Reading database ... 16518 files and directories currently installed.) Removing autopkgtest-satdep (0) ... autopkgtest [18:11:22]: test unittests: [--- === python3.9 === Segmentation fault autopkgtest [18:11:43]: test unittests: ---] autopkgtest [18:11:43]: test unittests: - - - - - - - - - - results - - - - - - - - - - unittestsFAIL non-zero exit status 139 autopkgtest [18:11:43]: summary unittestsFAIL non-zero exit status 139 I don't know which update triggered the regression, if the program itself or something else in the toolchain. Can you please have a look? https://ci.debian.net/packages/p/python-mpv/testing/arm64/ thanks Gianfranco --- End Message --- --- Begin Message --- Source: python-mpv Source-Version: 0.5.2-2 Done: Louis-Philippe Véronneau We believe that the bug you reported is fixed in the latest version of python-mpv, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 1000...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Louis-Philippe Véronneau (supplier of updated python-mpv package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sat, 27 Nov 2021 14:14:35 -0500 Source: python-mpv Architecture: source Version: 0.5.2-2 Distribution: unstable Urgency: medium Maintainer: Debian Python Team Changed-By: Louis-Philippe Véronneau Closes: 1000255 Changes: python-mpv (0.5.2-2) unstable; urgency=medium . [ Ondřej Nový ] * d/control: Update Maintainer field with new Debian Python Team contact address. * d/control: Update Vcs-* fields with new Debian Python Team Salsa layout. . [ Louis-Philippe Véronneau ] * d/patches: add 0002 to patch out broken test. (Closes: #1000255) Checksums-Sha1: 28e11f1b8a1a7080d226b0ec30b5d8f2ef104adb 1517 python-mpv_0.5.2-2.dsc 0aef761bd843501f6e55b6f7ea928bb356b856c7 3980 python-mpv_0.5.2-2.debian.tar.xz 49bd50f74e2b1cfcf92b2c755d4ace8924dda270 12060 python-mpv_0.5.2-2_amd64.buildinfo Checksums-Sha256: 378a16aefdb4226fd6ec56e6fafcc1d4edc5db9c52ed1eaeb0849d1f10fb6941 1517 python-mpv_0.5.2-2.dsc 3ea6c02cc8af48c7e44cb2ec838d019279f549a0be5363c65fd948654cc1c979 3980 python-mpv_0.5.2-2.debian.tar.xz 034ae0fde890fff84616e9c8dc0baf8f1da37da36c285e53c63c3f2ec45f98e3 12060 python-mpv_0.5.2-2_amd64.buildinfo Files: 91469883d7bec7579925c3cd1fd72c03 1517 python optional python-mpv_0.5.2-2.dsc bbc0df24351c44ef3c5ba96a7eee196d 3980 python optional python-mpv_0.5.2-2.debian.tar.xz 3ba4697bb8af73de14581a0f1adfcf34 12060 python optional python-mpv_0.5.2-2_amd64.buildinfo -BEGIN PGP SIGNATURE- iHUEARYKAB0WIQTKp0AHB6gWsCAvw830JXpQshz6hQUCYaKE2gAKCRD0JXpQshz6 haKQAP9yPcXiQxFOfg+bxX9KxkYc80C+woK/n2syoFmeyyj+1gD9EOInkQ9PXmmm tthLJjJGuq9KPaf/LRtVhRF1yXmJZAk= =7BUF -END PGP SIGNATURE End Message ---
Processed: ponyorm 3.10 additional details
Processing commands for cont...@bugs.debian.org: > forwarded 1000716 https://github.com/ponyorm/pony/issues/598 Bug #1000716 [python3-pony] python3-pony: fails on Python 3.10 with "ModuleNotFoundError: No module named 'parser'" Set Bug forwarded-to-address to 'https://github.com/ponyorm/pony/issues/598'. > block 1000717 by 1000716 Bug #1000717 [src:supysonic] supysonic: FTBFS on Python 3.10 1000717 was not blocked by any bugs. 1000717 was not blocking any bugs. Added blocking bug(s) of 1000717: 1000716 > thanks Stopping processing here. Please contact me if you need assistance. -- 1000716: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1000716 1000717: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1000717 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1000716: ponyorm 3.10 additional details
reassign 1000716 src:ponyorm rename 1000716 ponyorm: FTBFS on Python 3.10 thanks Oh well, it seems it does sys.exit(1) when trying to build the package, just not when running the testsuite by itself... I: pybuild base:237: python3.10 setup.py clean Sorry, but pony 0.7.14 requires Python of one of the following versions: 2.7, 3.3-3.9. You have version 3.10.0+ E: pybuild pybuild:354: clean: plugin distutils failed with: exit code=1: python3.10 setup.py clean -- ⢀⣴⠾⠻⢶⣦⠀ ⣾⠁⢠⠒⠀⣿⡁ Louis-Philippe Véronneau ⢿⡄⠘⠷⠚⠋ po...@debian.org / veronneau.org ⠈⠳⣄ OpenPGP_signature Description: OpenPGP digital signature
Processed (with 1 error): Re: ponyorm 3.10 additional details
Processing commands for cont...@bugs.debian.org: > reassign 1000716 src:ponyorm Bug #1000716 [python3-pony] python3-pony: fails on Python 3.10 with "ModuleNotFoundError: No module named 'parser'" Bug reassigned from package 'python3-pony' to 'src:ponyorm'. No longer marked as found in versions ponyorm/0.7.14-1. Ignoring request to alter fixed versions of bug #1000716 to the same values previously set > rename 1000716 ponyorm: FTBFS on Python 3.10 Unknown command or malformed arguments to command. > thanks Stopping processing here. Please contact me if you need assistance. -- 1000716: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1000716 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Re: ponyorm 3.10 additional details
Processing commands for cont...@bugs.debian.org: > retitle 1000716 ponyorm: FTBFS on Python 3.10 Bug #1000716 [src:ponyorm] python3-pony: fails on Python 3.10 with "ModuleNotFoundError: No module named 'parser'" Changed Bug title to 'ponyorm: FTBFS on Python 3.10' from 'python3-pony: fails on Python 3.10 with "ModuleNotFoundError: No module named 'parser'"'. > thanks Stopping processing here. Please contact me if you need assistance. -- 1000716: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1000716 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1000611: marked as done (libvtk9{,-qt}: soname change without library transition)
Your message dated Sat, 27 Nov 2021 20:49:51 +
with message-id
and subject line Bug#1000611: fixed in vtk9 9.1.0+really9.0.3+dfsg1-3
has caused the Debian Bug report #1000611,
regarding libvtk9{,-qt}: soname change without library 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.)
--
1000611: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1000611
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libvtk9
Version: 9.1.0+dfsg2-2
Severity: serious
Control: affects -1 libvtk9-qt src:vtk9
https://ci.debian.net/data/autopkgtest/testing/amd64/f/freecad/16980590/log.gz
...
ERROR: TestFemApp (unittest.loader._FailedTest)
--
ImportError: Failed to import test module: TestFemApp
Traceback (most recent call last):
File "/usr/lib/python3.9/unittest/loader.py", line 154, in loadTestsFromName
module = __import__(module_name)
File "/usr/share/freecad/Mod/Fem/TestFemApp.py", line 33, in
from femtest.app.test_mesh import TestMeshCommon as FemTest07
File "/usr/share/freecad/Mod/Fem/femtest/app/test_mesh.py", line 33, in
import Fem
ImportError: libvtkFiltersExtraction-9.0.so.1: cannot open shared object file:
No such file or directory
...
The soname of the vtk9 libraries is not 9, it is 9.0 for VTK 9.0
and 9.1 for VTK 9.1:
$ objdump -p /usr/lib/x86_64-linux-gnu/libvtkChartsCore-9.1.so.1 | grep SONAME
SONAME libvtkChartsCore-9.1.so.1
$
In bullseye libvtk9 and libvtk9-qt should have been named
libvtk9.0 and libvtk9.0-qt, but this alone is harmless.
Not harmless is that the libraries must transition to the new
soname in 9.1, renaming the packages to libvtk9.1 and libvtk9.1-qt.
--- End Message ---
--- Begin Message ---
Source: vtk9
Source-Version: 9.1.0+really9.0.3+dfsg1-3
Done: Anton Gladky
We believe that the bug you reported is fixed in the latest version of
vtk9, which is due to be installed in the Debian FTP archive.
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to 1000...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Anton Gladky (supplier of updated vtk9 package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Sat, 27 Nov 2021 21:27:37 +0100
Source: vtk9
Architecture: source
Version: 9.1.0+really9.0.3+dfsg1-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Science Team
Changed-By: Anton Gladky
Closes: 1000611
Changes:
vtk9 (9.1.0+really9.0.3+dfsg1-3) unstable; urgency=medium
.
* Upload previous version to fix unstable. (Closes: #1000611)
Checksums-Sha1:
a042dde5301b01c35fde94e5cfcca87371a80ba2 3791
vtk9_9.1.0+really9.0.3+dfsg1-3.dsc
25bdcf14d0ceb41b37c0dc9b5d6417af5cefaadb 13152160
vtk9_9.1.0+really9.0.3+dfsg1.orig.tar.xz
6225dc68b64043c7ca81c1fa84b9e6e60f049a7b 22160
vtk9_9.1.0+really9.0.3+dfsg1-3.debian.tar.xz
da508414929f735279033dc10c540362a07210c0 27214
vtk9_9.1.0+really9.0.3+dfsg1-3_source.buildinfo
Checksums-Sha256:
d645fa951b6b495af9aa91448232e5d1c8fc9c6b7ae7a31ffe16b4535ca670b4 3791
vtk9_9.1.0+really9.0.3+dfsg1-3.dsc
88cc4ef389085a26d858f83def848110b3fff0abadac2a3a9af433edf579eab9 13152160
vtk9_9.1.0+really9.0.3+dfsg1.orig.tar.xz
6b5d2214316e45b1ddcf12eb77d976d8c6b8112df6f0879a01e4a47ad7e508e8 22160
vtk9_9.1.0+really9.0.3+dfsg1-3.debian.tar.xz
a2e83a40cb8ce9d23776107507dc4bdb0482032aadfcfedab76295aa607dea3a 27214
vtk9_9.1.0+really9.0.3+dfsg1-3_source.buildinfo
Files:
8fb6b20f06dbb80ac642967774cbb64a 3791 graphics optional
vtk9_9.1.0+really9.0.3+dfsg1-3.dsc
5393bbde195becd1417d376b6683bc7b 13152160 graphics optional
vtk9_9.1.0+really9.0.3+dfsg1.orig.tar.xz
e15355e964b78ca3decf5c52a3293ee6 22160 graphics optional
vtk9_9.1.0+really9.0.3+dfsg1-3.debian.tar.xz
71d3d3aa9fb6a9d10293398a4cc9f1f2 27214 graphics optional
vtk9_9.1.0+really9.0.3+dfsg1-3_source.buildinfo
-BEGIN PGP SIGNATURE-
iQJFBAEBCgAvFiEEu71F6oGKuG/2fnKF0+Fzg8+n/wYFAmGiltcRHGdsYWRrQGRl
Ymlhbi5vcmcACgkQ0+Fzg8+n/wZMgQ//br1k1JydRSUGRuEacuTX8fnRv34WCeYk
FrM/H5E0kXlfjrA8jYvcBXT/psQcpQD3oo4LqyNXtoS9y70pRhBZBedaAz8EAOIM
YtDF5Iw2XzuGMMtb2BxpkGHR0tdwoOZNXTUM/b90MqTakf44Ix2jk8dcWV9iqDgC
ab4mINBfXd6ShdbApBb3ow80jH66TBM3YXKN0P76TZrU
Processed: Bug#1000702 marked as pending in sonic-visualiser
Processing control commands: > tag -1 pending Bug #1000702 [src:sonic-visualiser] src:sonic-visualiser: fails to migrate to testing for too long: FTBFS on armel and mipsel Added tag(s) pending. -- 1000702: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1000702 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1000702: marked as pending in sonic-visualiser
Control: tag -1 pending Hello, Bug #1000702 in sonic-visualiser reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/multimedia-team/sonic-visualiser/-/commit/40777542428ad61abba2aa6c26d3b02121ae555c Link with libatomic on architectures without built-in atomic Closes: #1000702 (this message was generated automatically) -- Greetings https://bugs.debian.org/1000702
Bug#1000293: Problems starting jackd: Method RequestRelease is not implemented on interface org.freedesktop.ReserveDevice1
I guess so, I have both pipewire and pipewire-pulse in the output of ps Altgough I have no idea what that is for Il lun 22 nov 2021, 11:50 Sebastian Ramacher ha scritto: > Control: tags -1 moreinfo > > On 2021-11-21 00:55:50, Arnaldo Pirrone wrote: > > Package: jackd2 > > Version: 1.9.19~dfsg-2 > > Severity: grave > > X-Debbugs-Cc: it9...@gmail.com > > > > Apparently there is something wrong with Jack and dbus. > > Also reported here: > > > https://www.reddit.com/r/linuxaudio/comments/qtmynn/problems_starting_jackd_method_requestrelease_is/ > > Find below the jack server logs. > > > > 00:41:32.228 Resetta le statistiche. > > 00:41:32.269 Connessioni di ALSA cambiate. > > 00:41:32.389 D-BUS: Servizio disponibile (org.jackaudio.service aka > jackdbus). > > Cannot connect to server socket err = File o directory non esistente > > Cannot connect to server request channel > > jack server is not running or cannot be started > > JackShmReadWritePtr::~JackShmReadWritePtr - Init not done for -1, > skipping > > unlock > > JackShmReadWritePtr::~JackShmReadWritePtr - Init not done for -1, > skipping > > unlock > > 00:41:32.563 Cambiamento nel grafico delle connessioni di ALSA. > > 00:41:47.432 D-BUS: il server JACK non può essere avviato. Mi dispiace > > Sun Nov 21 00:41:47 2021: Starting jack server... > > Sun Nov 21 00:41:47 2021: JACK server starting in realtime mode with > priority > > 10 > > Sun Nov 21 00:41:47 2021: self-connect-mode is "Don't restrict self > connect > > requests" > > Cannot connect to server socket err = File o directory non esistente > > Cannot connect to server request channel > > jack server is not running or cannot be started > > JackShmReadWritePtr::~JackShmReadWritePtr - Init not done for -1, > skipping > > unlock > > JackShmReadWritePtr::~JackShmReadWritePtr - Init not done for -1, > skipping > > unlock > > Sun Nov 21 00:41:47 2021: Device reservation request with priority > 2147483647 > > denied for "Audio1": org.freedesktop.DBus.Error.UnknownMethod (Method > > RequestRelease is not implemented on interface > org.freedesktop.ReserveDevice1) > > Sun Nov 21 00:41:47 2021: ERROR: Failed to acquire device name : Audio1 > error : > > Method RequestRelease is not implemented on interface > > org.freedesktop.ReserveDevice1 > > Sun Nov 21 00:41:47 2021: ERROR: Audio device hw:PCH,0 cannot be > acquired... > > Sun Nov 21 00:41:47 2021: ERROR: Cannot initialize driver > > Sun Nov 21 00:41:47 2021: ERROR: JackServer::Open failed with -1 > > Sun Nov 21 00:41:47 2021: ERROR: Failed to open server > > Sun Nov 21 00:41:48 2021: Saving settings to > > "/home/it9exm/.config/jack/conf.xml" ... > > 00:41:49.469 Non sono riuscito ad avviare JACK come client. - Operazione > > fallita. - Impossibile connettersi al server JACK. Controlla la finestra > dei > > messaggi per maggiori informazioni. > > Cannot connect to server socket err = File o directory non esistente > > Cannot connect to server request channel > > jack server is not running or cannot be started > > JackShmReadWritePtr::~JackShmReadWritePtr - Init not done for -1, > skipping > > unlock > > JackShmReadWritePtr::~JackShmReadWritePtr - Init not done for -1, > skipping > > unlock > > Unfortunately I'm not able to reprodue this issue. Are you running > pipewire by any chance? > > Best > Sebastian > > > > > > > -- System Information: > > Debian Release: bookworm/sid > > APT prefers unstable > > APT policy: (500, 'unstable'), (1, 'experimental') > > Architecture: amd64 (x86_64) > > Foreign Architectures: i386 > > > > Kernel: Linux 5.14.19-xanmod1 (SMP w/4 CPU threads) > > Kernel taint flags: TAINT_WARN, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE > > Locale: LANG=it_IT.UTF-8, LC_CTYPE=it_IT.UTF-8 (charmap=UTF-8), LANGUAGE > not set > > Shell: /bin/sh linked to /usr/bin/dash > > Init: systemd (via /run/systemd/system) > > LSM: AppArmor: enabled > > > > Versions of packages jackd2 depends on: > > ii debconf [debconf-2.0] 1.5.79 > > ii libasound2 1.2.5.1-1 > > ii libc6 2.32-4 > > ii libdbus-1-31.12.20-3 > > ii libexpat1 2.4.1-3 > > ii libgcc-s1 11.2.0-10 > > ii libjack-jackd2-0 1.9.19~dfsg-2 > > ii libreadline8 8.1-2 > > ii libsamplerate0 0.2.2-1 > > ii libsndfile11.0.31-2 > > ii libstdc++6 11.2.0-10 > > ii libsystemd0249.6-2 > > ii libzita-alsa-pcmi0 0.3.2-2 > > ii libzita-resampler1 1.8.0-2 > > ii python33.9.8-1 > > ii python3-dbus 1.2.18-3 > > > > Versions of packages jackd2 recommends: > > ii jackd2-firewire 1.9.19~dfsg-2 > > ii libpam-modules 1.4.0-10 > > ii qjackctl 0.9.5-1 > > > > Versions of packages jackd2 suggests: > > pn jack-tools > > pn meterbridge > > > > -- debconf information: > > * jackd/tweak_rt_limits: true > > -- > Sebastian Ramacher >
Bug#997455: marked as done (snapd-glib: FTBFS: dpkg-gensymbols: error: some symbols or patterns disappeared in the symbols file: see diff output below)
Your message dated Sat, 27 Nov 2021 21:18:53 + with message-id and subject line Bug#997455: fixed in snapd-glib 1.59-1 has caused the Debian Bug report #997455, regarding snapd-glib: FTBFS: dpkg-gensymbols: error: some symbols or patterns disappeared in the symbols file: see diff output below 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.) -- 997455: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997455 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: snapd-glib Version: 1.58-4 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20211023 ftbfs-bookworm Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[1]: Entering directory '/<>' > dh_makeshlibs -V -- -c4 > dpkg-gensymbols: error: some symbols or patterns disappeared in the symbols > file: see diff output below > dpkg-gensymbols: warning: debian/libsnapd-qt1/DEBIAN/symbols doesn't match > completely debian/libsnapd-qt1.symbols > --- debian/libsnapd-qt1.symbols (libsnapd-qt1_1.58-4_amd64) > +++ dpkg-gensymbolseAxhpA 2021-10-23 06:31:54.390360539 + > @@ -1,5 +1,5 @@ > libsnapd-qt.so.1 libsnapd-qt1 #MINVER# > - > (optional=templinst|arch=amd64)_Z27qRegisterNormalizedMetaTypeIP9QIODeviceEiRK10QByteArrayPT_N9QtPrivate21MetaTypeDefinedHelperIS5_Xaasr12QMetaTypeId2IS5_E7DefinedntsrSA_9IsBuiltInEE11DefinedTypeE@Base > 1.58 > +#MISSING: 1.58-4# > (optional=templinst|arch=amd64)_Z27qRegisterNormalizedMetaTypeIP9QIODeviceEiRK10QByteArrayPT_N9QtPrivate21MetaTypeDefinedHelperIS5_Xaasr12QMetaTypeId2IS5_E7DefinedntsrSA_9IsBuiltInEE11DefinedTypeE@Base > 1.58 > _Z5loginRK7QStringS1_@Base 1.58 > _Z5loginRK7QStringS1_S1_@Base 1.58 > _ZN10QByteArrayD1Ev@Base 1.58 > @@ -180,8 +180,8 @@ > _ZN12QSnapdClientD0Ev@Base 1.58 > _ZN12QSnapdClientD1Ev@Base 1.58 > _ZN12QSnapdClientD2Ev@Base 1.58 > - (optional=templinst|arch=amd64)_ZN12QWeakPointerI7QObjectED1Ev@Base 1.58 > - (optional=templinst|arch=amd64)_ZN12QWeakPointerI7QObjectED2Ev@Base 1.58 > +#MISSING: 1.58-4# > (optional=templinst|arch=amd64)_ZN12QWeakPointerI7QObjectED1Ev@Base 1.58 > +#MISSING: 1.58-4# > (optional=templinst|arch=amd64)_ZN12QWeakPointerI7QObjectED2Ev@Base 1.58 > _ZN13QSnapdChannel11qt_metacallEN11QMetaObject4CallEiPPv@Base 1.58 > _ZN13QSnapdChannel11qt_metacastEPKc@Base 1.58 > _ZN13QSnapdChannel16staticMetaObjectE@Base 1.58 > @@ -247,8 +247,8 @@ > _ZN15QSnapdInterfaceD0Ev@Base 1.58 > _ZN15QSnapdInterfaceD1Ev@Base 1.58 > _ZN15QSnapdInterfaceD2Ev@Base 1.58 > - _ZN15QtSharedPointer20ExternalRefCountDataD1Ev@Base 1.58 > - _ZN15QtSharedPointer20ExternalRefCountDataD2Ev@Base 1.58 > +#MISSING: 1.58-4# _ZN15QtSharedPointer20ExternalRefCountDataD1Ev@Base 1.58 > +#MISSING: 1.58-4# _ZN15QtSharedPointer20ExternalRefCountDataD2Ev@Base 1.58 > _ZN16QSnapdBuyRequest11qt_metacallEN11QMetaObject4CallEiPPv@Base 1.58 > _ZN16QSnapdBuyRequest11qt_metacastEPKc@Base 1.58 > _ZN16QSnapdBuyRequest12handleResultEPvS0_@Base 1.58 > @@ -319,7 +319,7 @@ > _ZN17QSnapdMaintenanceD2Ev@Base 1.58 > > (optional=templinst)_ZN17QtMetaTypePrivate23QMetaTypeFunctionHelperIP9QIODeviceLb1EE8DestructEPv@Base > 1.58 > > (optional=templinst)_ZN17QtMetaTypePrivate23QMetaTypeFunctionHelperIP9QIODeviceLb1EE9ConstructEPvPKv@Base > 1.58 > - > (optional=templinst|arch=!amd64)_ZN18QMetaTypeIdQObjectIP9QIODeviceLi8EE14qt_metatype_idEv@Base > 1.58 > + > (optional=templinst)_ZN18QMetaTypeIdQObjectIP9QIODeviceLi8EE14qt_metatype_idEv@Base > 1.58 > _ZN18QSnapdAliasRequest11qt_metacallEN11QMetaObject4CallEiPPv@Base 1.58 > _ZN18QSnapdAliasRequest11qt_metacastEPKc@Base 1.58 > _ZN18QSnapdAliasRequest12handleResultEPvS0_@Base 1.58 > @@ -844,14 +844,14 @@ > _ZN33QSnapdGetSystemInformationRequestD0Ev@Base 1.58 > _ZN33QSnapdGetSystemInformationRequestD1Ev@Base 1.58 > _ZN33QSnapdGetSystemInformationRequestD2Ev@Base 1.58 > - (optional=templinst)_ZN4QMapI7QString8QVariantEC1ERKS2_@Base 1.58 > - (optional=templinst)_ZN4QMapI7QString8QVariantEC2ERKS2_@Base 1.58 > +#MISSING: 1.58-4# > (optional=templinst)_ZN4QMapI7QString8QVariantEC1ERKS2_@Base 1.58 > +#MISSING: 1.58-4# > (optional=templinst)_ZN4QMapI7QString8QVariantEC2ERKS2_@Base 1.58 > (optional=templinst)_ZN4QMapI7QString8QVariantED1Ev@Base 1.58 > (optional=templinst)_ZN4QMapI7QString8QVariantED2Ev@Base 1.58 > > (optional=templinst)_ZN5QHashI7QString11QStringListE11deleteNode2EPN9QHashData4NodeE@Base > 1.58 > > (optional=templinst)_ZN5QHashI7QString11QStringListE13duplicateNodeEPN9QHashData4N
Processed: Bug#996350 marked as pending in ruby-rabl
Processing control commands: > tag -1 pending Bug #996350 [src:ruby-rabl] ruby-rabl: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed. Added tag(s) pending. -- 996350: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=996350 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#996350: marked as pending in ruby-rabl
Control: tag -1 pending Hello, Bug #996350 in ruby-rabl reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/ruby-team/ruby-rabl/-/commit/57032c0b6d8285b6f8f9d81ca7307444dc88df01 Fix the test issues * debian/ruby-test-files.yaml: Remove file. * debian/ruby-tests.rake: Add, and enable patches by loading Rakefile and running the test target. This fixes the test failures (closes: #996350). * d/patches/fix-rakefile.patch: Add patch. - Fix Rakefile to be able to run the tests. * d/patches/series: Enable new patch. (this message was generated automatically) -- Greetings https://bugs.debian.org/996350
Bug#1000702: marked as done (src:sonic-visualiser: fails to migrate to testing for too long: FTBFS on armel and mipsel)
Your message dated Sat, 27 Nov 2021 21:50:00 + with message-id and subject line Bug#1000702: fixed in sonic-visualiser 4.4-2 has caused the Debian Bug report #1000702, regarding src:sonic-visualiser: fails to migrate to testing for too long: FTBFS on armel and mipsel 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.) -- 1000702: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1000702 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: sonic-visualiser Version: 4.2-1 Severity: serious Tags: sid bookworm ftbfs User: release.debian@packages.debian.org Usertags: out-of-sync Dear maintainer(s), The Release Team considers packages that are out-of-sync between testing and unstable for more than 60 days as having a Release Critical bug in testing [1]. Your package src:sonic-visualiser has been trying to migrate for 61 days [2]. Hence, I am filing this bug. Your package FTBFS on armel and mipsel. If a package is out of sync between unstable and testing for a longer period, this usually means that bugs in the package in testing cannot be fixed via unstable. Additionally, blocked packages can have impact on other packages, which makes preparing for the release more difficult. Finally, it often exposes issues with the package and/or its (reverse-)dependencies. We expect maintainers to fix issues that hamper the migration of their package in a timely manner. This bug will trigger auto-removal when appropriate. As with all new bugs, there will be at least 30 days before the package is auto-removed. I have tagged this bug to only affect sid and bookworm, so it doesn't affect (old-)stable. If you believe your package is unable to migrate to testing due to issues beyond your control, don't hesitate to contact the Release Team. Paul [1] https://lists.debian.org/debian-devel-announce/2020/02/msg5.html [2] https://qa.debian.org/excuses.php?package=sonic-visualiser OpenPGP_signature Description: OpenPGP digital signature --- End Message --- --- Begin Message --- Source: sonic-visualiser Source-Version: 4.4-2 Done: IOhannes m zmölnig (Debian/GNU) We believe that the bug you reported is fixed in the latest version of sonic-visualiser, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 1000...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. IOhannes m zmölnig (Debian/GNU) (supplier of updated sonic-visualiser package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Sat, 27 Nov 2021 22:08:55 +0100 Source: sonic-visualiser Architecture: source Version: 4.4-2 Distribution: unstable Urgency: medium Maintainer: Debian Multimedia Maintainers Changed-By: IOhannes m zmölnig (Debian/GNU) Closes: 1000702 Changes: sonic-visualiser (4.4-2) unstable; urgency=medium . * Link with libatomic on architectures without built-in atomic (Closes: #1000702) Checksums-Sha1: 092251c2e9b4f23747ca6598a7591c48d3acc347 2689 sonic-visualiser_4.4-2.dsc be924844cc0204297855c90ac9ba62df4002b874 21236 sonic-visualiser_4.4-2.debian.tar.xz Checksums-Sha256: d71b885d2908e0891fee75abb90d397a701499982dbe2bc2b2d7cb48fc891520 2689 sonic-visualiser_4.4-2.dsc 94ea83601582fe8ee2e2a2df20bd5aafb09da2c59e6fda2785aa97347ff708a3 21236 sonic-visualiser_4.4-2.debian.tar.xz Files: 8b90544d65400bb2092d91901882f97b 2689 sound optional sonic-visualiser_4.4-2.dsc 570d3e3945a7512efed0881203108272 21236 sound optional sonic-visualiser_4.4-2.debian.tar.xz -BEGIN PGP SIGNATURE- iQJKBAEBCAA0FiEEdAXnRVdICXNIABVttlAZxH96NvgFAmGio7sWHGZvcnVtQHVt bGFldXRlLm11ci5hdAAKCRC2UBnEf3o2+OTrD/9VzKtgco61fkGpDeVsKC6n9Iu6 XgM33Kz5csshvJAidFXgt+Tf9mOh4sasBV9h3zdt6t793aNMLTd4oJR0uNEk6NDv 1xSh8IR2K4vgUtBVWfSBsjuwvfv9GZaVVP/jOSE+hMoSYjfBF2NLKQiwf/44dWaC /AsT1KMK59QOvWTKrZ+6ifqyXU1FlMyGNiTn2RtiBO5kmibyDCmL6S+wIoMPjpdV Rj9QFXlqoH7vIc83N4cs13DH5dS0AGBbE5EbMRE6LMAiXfBBAp6AYr/CpDUeEqqe pMMbFCXVbTvKYxLVQ/ZN2km1mII7Ji9CEsVbKfVoOwW+QZpbNd4V4oU+B/P2CC1V 4tSv3tlDvVjJ+r6eZeX1xcpX/N6kBGEeHP0FPKZmuj0fCEbiM5qQBFSMjBZXoqOe inXJ6HGK0ON0oP6scGRDoxgNoJDph/Eu1R2NdOEqU2+j3k+ZAUbiXzBYj1xmFaw7 vnj4tMEcO+9HYQNG5mh31Y0yBSoCEmucKA3umqqy+7WOTu9si4uEhzB16
Bug#996350: marked as done (ruby-rabl: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed.)
Your message dated Sat, 27 Nov 2021 21:49:28 +
with message-id
and subject line Bug#996350: fixed in ruby-rabl 0.13.1-2
has caused the Debian Bug report #996350,
regarding ruby-rabl: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed.
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.)
--
996350: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=996350
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ruby-rabl
Version: 0.13.1-1.1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: debian-r...@lists.debian.org
Usertags: ruby3.0
Hi,
We are about to enable building against ruby3.0 on unstable. During a test
rebuild, ruby-rabl was found to fail to build in that situation.
To reproduce this locally, you need to install ruby-all-dev from experimental
on an unstable system or build chroot.
Relevant part (hopefully):
> /usr/bin/ruby3.0 /usr/bin/gem2deb-test-runner
>
> ┌──┐
> │ Checking Rubygems dependency resolution on ruby3.0
> │
> └──┘
>
> GEM_PATH=/<>/debian/ruby-rabl/usr/share/rubygems-integration/all:/var/lib/gems/3.0.0:/usr/local/lib/ruby/gems/3.0.0:/usr/lib/ruby/gems/3.0.0:/usr/lib/x86_64-linux-gnu/ruby/gems/3.0.0:/usr/share/rubygems-integration/3.0.0:/usr/share/rubygems-integration/all:/usr/lib/x86_64-linux-gnu/rubygems-integration/3.0.0
> ruby3.0 -e gem\ \"rabl\"
>
> ┌──┐
> │ Run tests for ruby3.0 from debian/ruby-test-files.yaml
> │
> └──┘
>
> RUBYLIB=/<>/debian/ruby-rabl/usr/lib/ruby/vendor_ruby:.
> GEM_PATH=/<>/debian/ruby-rabl/usr/share/rubygems-integration/all:/var/lib/gems/3.0.0:/usr/local/lib/ruby/gems/3.0.0:/usr/lib/ruby/gems/3.0.0:/usr/lib/x86_64-linux-gnu/ruby/gems/3.0.0:/usr/share/rubygems-integration/3.0.0:/usr/share/rubygems-integration/all:/usr/lib/x86_64-linux-gnu/rubygems-integration/3.0.0
> ruby3.0 -ryaml -e YAML.load_file\(\"debian/ruby-test-files.yaml\"\).each\
> \{\ \|f\|\ require\ f\ \}
> ...E.E.E
> ERROR
> Rabl::Builder #glue asserts that it generates the glue attributes => On
> subject #,
> unexpected method invocation:
> object_to_engine(# @name="rabl", @first="bob", @float=1234.56,
> @hobbies=[#],
> @twitter="rablgem">, root: false)
> expected invocations:
> - object_to_engine(# @name="rabl", @first="bob", @float=1234.56,
> @hobbies=[#],
> @twitter="rablgem">, {:root=>false}) occured
> at /usr/lib/ruby/vendor_ruby/riot.rb:129:in `block in '
> at /usr/lib/ruby/vendor_ruby/riot.rb:38:in `run'
> at /usr/lib/ruby/vendor_ruby/riot/reporter.rb:46:in `summarize'
> at /usr/lib/ruby/vendor_ruby/riot.rb:39:in `block in run'
> at /usr/lib/ruby/vendor_ruby/riot.rb:39:in `each'
> at /usr/lib/ruby/vendor_ruby/riot.rb:39:in `block (2 levels) in run'
> at /usr/lib/ruby/vendor_ruby/riot/context.rb:98:in `run'
> at /usr/lib/ruby/vendor_ruby/riot/context.rb:146:in `run_sub_contexts'
> at /usr/lib/ruby/vendor_ruby/riot/context.rb:146:in `each'
> at /usr/lib/ruby/vendor_ruby/riot/context.rb:146:in `block in
> run_sub_contexts'
> at /usr/lib/ruby/vendor_ruby/riot/context.rb:97:in `run'
> at /usr/lib/ruby/vendor_ruby/riot/context.rb:108:in `local_run'
> at /usr/lib/ruby/vendor_ruby/riot/context.rb:108:in `each'
> at /usr/lib/ruby/vendor_ruby/riot/context.rb:109:in `block in local_run'
> at /usr/lib/ruby/vendor_ruby/riot/rr.rb:33:in `run'
> at /usr/lib/ruby/vendor_ruby/riot/assertion.rb:51:in `run'
> at /usr/lib/ruby/vendor_ruby/riot/situation.rb:61:in `evaluate'
> at /usr/lib/ruby/vendor_ruby/riot/situation.rb:61:in `instance_eval'
> at /<>/test/builder_test.rb:233:in `block (3 levels) in (required)>'
> at /<>/lib/rabl/builder.rb:49:in `to_hash'
> at /<>/lib/rabl/builder.rb:248:in `cache_results'
> at /<>/lib/rabl/builder.rb:55:in `block in to_hash'
> at /<>/lib/rabl/builder.rb:119:in `merge_engines_into_result'
> at /<>/lib/rabl/builder.rb:35:in `engines'
> at /<>/lib/rabl/builder.rb:113:in `compile_settings'
> at /<>/lib/rabl/builder.rb:113:in `each'
> at /<>/lib/rabl/builder.rb:114:in `block in
Processed: Forwarded gammapy bug
Processing commands for cont...@bugs.debian.org: > forwarded 1000613 https://github.com/gammapy/gammapy/issues/3662 Bug #1000613 [src:gammapy] gammapy FTBFS on !amd64: test failures Set Bug forwarded-to-address to 'https://github.com/gammapy/gammapy/issues/3662'. > thanks Stopping processing here. Please contact me if you need assistance. -- 1000613: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1000613 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1000666: marked as pending in git-review
Control: tag -1 pending Hello, Bug #1000666 in git-review reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/openstack-team/third-party/git-review/-/commit/383f99c405d4e0ea7375f5921ef14532948a5d7a * New upstream release: - works with newer Git releases (Closes: #1000666). (this message was generated automatically) -- Greetings https://bugs.debian.org/1000666
Processed: Bug#1000666 marked as pending in git-review
Processing control commands: > tag -1 pending Bug #1000666 [git-review] git-review: Fatal failure with newer git releases Added tag(s) pending. -- 1000666: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1000666 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1000666: marked as done (git-review: Fatal failure with newer git releases)
Your message dated Sat, 27 Nov 2021 22:48:37 + with message-id and subject line Bug#1000666: fixed in git-review 2.2.0-1 has caused the Debian Bug report #1000666, regarding git-review: Fatal failure with newer git releases 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.) -- 1000666: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1000666 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: git-review Version: 1.28.0-2 Severity: serious Hi! The command now fails with git 1:2.34.0-1 as it is using an obsolete option that has been renamed: Errors running git rebase -p -i remotes/origin/branch fatal: --preserve-merges was replaced by --rebase-merges It is likely that your change has a merge conflict. You may resolve it in the working tree now as described above and then run 'git review' again, or if you do not want to resolve it yet (note that the change can not merge until the conflict is resolved) you may run 'git rebase --abort' then 'git review -R' to upload the change without rebasing. The code needs to be updated to replace the «git rebase -p» with «-r». Thanks, Guillem --- End Message --- --- Begin Message --- Source: git-review Source-Version: 2.2.0-1 Done: Thomas Goirand We believe that the bug you reported is fixed in the latest version of git-review, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 1000...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Thomas Goirand (supplier of updated git-review package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Sat, 27 Nov 2021 23:29:26 +0100 Source: git-review Architecture: source Version: 2.2.0-1 Distribution: unstable Urgency: medium Maintainer: Debian OpenStack Changed-By: Thomas Goirand Closes: 1000666 Changes: git-review (2.2.0-1) unstable; urgency=medium . * New upstream release: - works with newer Git releases (Closes: #1000666). * Blacklist GitReviewUnitTest.test_notify(). Checksums-Sha1: 47ba95e09dd03fe9bbb1b774932b0e2b62b949c6 2232 git-review_2.2.0-1.dsc 79ddfc973a52d818c616421124b520ddd039b65e 46052 git-review_2.2.0.orig.tar.xz 5b57075bfacfe53f1ded152388de708f32e862da 3856 git-review_2.2.0-1.debian.tar.xz f2b345edc3e0a10fee897c000d949d443204d7bd 9072 git-review_2.2.0-1_amd64.buildinfo Checksums-Sha256: c3ca591a1822cf2c2b8ca566919d1194c45751a37c67c592ef60b635c4fa58d4 2232 git-review_2.2.0-1.dsc 007a35ca98acf872e71efc7dfa600b7f5615c01c09a4dd94734c9e0dc338648f 46052 git-review_2.2.0.orig.tar.xz 698a063342e7baa451e55edfea238036e9f1c679fd66e8d1b861b081d8754158 3856 git-review_2.2.0-1.debian.tar.xz ae99010e3f8b08950737f5cd3fd192d40b255f2d92ff92f6eca49bb77c9989a0 9072 git-review_2.2.0-1_amd64.buildinfo Files: 0a3167ceec0cf1b7deca07e97a66b470 2232 vcs optional git-review_2.2.0-1.dsc c445e3748cbef3dbfcd81f6ca07fdfbe 46052 vcs optional git-review_2.2.0.orig.tar.xz bfd252457e3bbc558f95406573fb780e 3856 vcs optional git-review_2.2.0-1.debian.tar.xz 74b59ccd177b6fe18602d642903a3050 9072 vcs optional git-review_2.2.0-1_amd64.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEEoLGp81CJVhMOekJc1BatFaxrQ/4FAmGism0ACgkQ1BatFaxr Q/4dQQ//RXibSM/czhBKHzPR77omSJigs6i45+9SgIjrx1PHWwOOWt5S32/K8gjZ mIE3qCXQmAY4iimzRnCoyMFknLmKnX5sHze5oFEnLdFXXxHlp6ACHpj3IitXd6Ya Oz5hFzlVCdTzRR9PDnBsV8oprdfwwd1tEQyIs8BzjDwb6N6CRbqczYunhbLNoNPj edupebGR61W8NfMJuRouoSoVzMqUAGunkxFEuVTPDk0i3xp/eGK32pP0R8KqgH6e swU70P+d4XINnCrT6jOcPbRqQLv1SaFQhxL4gm0PbYar2Tj24/eTbEVFmeEtxEmY q8V9ZnbMR2/ZQ/zLSQyAg4kZL+aFtCFAS2o5JASfzYMTgs7u0aZv5eWQAMi9MYD8 dBOqlfEbtxNmNbaCaGqy68Du87juGNGQg/pU0MkwayZQQTnpTVmpyOIJzqBuz2Yr uBFQUEbeS0DpmchEedLyXCVONQtPfzUcg6bTTd0TRGZskhCxBK10z/asm6UtCIaC RKCmgl3TF3X5nHEdnulx6AbqDo24aK6Zwps5VirDmGrNmbq6UAe15eBBghRvdivK iQLf32klPSXce8MRx6sW+zZhlRapOYAmsrUQegtz5X6bVKbI9dzeFg11hJZeduQV itsJVwo3m+aPhJ67l7P33bVPFL+ib0LEZyY2EtgboiKB1VpMVZY= =94oK -END PGP SIGNATURE End Message ---
Bug#1000414: marked as done (textdistance: autopkgtest regression on arm64: AssertionError: assert 3.0 <= 1)
Your message dated Sat, 27 Nov 2021 22:48:43 +
with message-id
and subject line Bug#1000414: fixed in textdistance 4.2.2-2
has caused the Debian Bug report #1000414,
regarding textdistance: autopkgtest regression on arm64: AssertionError: assert
3.0 <= 1
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
1000414: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1000414
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: textdistance
Version: 4.2.2-1
X-Debbugs-CC: debian...@lists.debian.org
Severity: serious
User: debian...@lists.debian.org
Usertags: regression
Dear maintainer(s),
With a recent upload of textdistance the autopkgtest of textdistance
fails in testing when that autopkgtest is run with the binary packages
of textdistance from unstable on arm64. It passes when run with only
packages from testing. In tabular form:
passfail
textdistance from testing4.2.2-1
all others from testingfrom testing
I copied some of the output at the bottom of this report.
Currently this regression is blocking the migration to testing [1]. Can
you please investigate the situation and fix it?
More information about this bug and the reason for filing it can be found on
https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation
Paul
[1] https://qa.debian.org/excuses.php?package=textdistance
https://ci.debian.net/data/autopkgtest/testing/arm64/t/textdistance/16584010/log.gz
=== FAILURES
===
___ test_normalization_range[alg23]
alg = Editex({'match_cost': 0, 'group_cost': 1, 'mismatch_cost': 2,
'local': False, 'external': True, 'grouped': frozenset({'U', 'B', 'K',
'F', 'D', 'M', 'X', 'S', 'Z', 'T', 'C', 'P', 'Q', 'E', 'N', 'J', 'G',
'V', 'L', 'I', 'R', 'O', 'A', 'Y'})})
@pytest.mark.parametrize('alg', ALGS)
@hypothesis.given(
left=hypothesis.strategies.text(),
right=hypothesis.strategies.text(),
)
tests/test_common.py:50: _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
left = '0', right = 'ῢ'
alg = Editex({'match_cost': 0, 'group_cost': 1, 'mismatch_cost': 2,
'local': False, 'external': True, 'grouped': frozenset({'U', 'B', 'K',
'F', 'D', 'M', 'X', 'S', 'Z', 'T', 'C', 'P', 'Q', 'E', 'N', 'J', 'G',
'V', 'L', 'I', 'R', 'O', 'A', 'Y'})})
@pytest.mark.parametrize('alg', ALGS)
@hypothesis.given(
left=hypothesis.strategies.text(),
right=hypothesis.strategies.text(),
)
def test_normalization_range(left, right, alg):
assert 0 <= alg.normalized_distance(left, right) <= 1
E AssertionError: assert 3.0 <= 1
E+ where 3.0 = Editex({'match_cost': 0, 'group_cost': 1, 'mismatch_cost': 2, 'local':
False... 'B', 'K', 'F', 'D', 'M', 'X', 'S', 'Z', 'T', 'C', 'P', 'Q',
'E', 'N', 'J', 'G', 'V', 'L', 'I', 'R', 'O', 'A', 'Y'})})>('0', 'ῢ')
E+where Editex({'match_cost': 0, 'group_cost': 1, 'mismatch_cost': 2, 'local':
False... 'B', 'K', 'F', 'D', 'M', 'X', 'S', 'Z', 'T', 'C', 'P', 'Q',
'E', 'N', 'J', 'G', 'V', 'L', 'I', 'R', 'O', 'A', 'Y'})})> =
Editex({'match_cost': 0, 'group_cost': 1, 'mismatch_cost': 2, 'local':
False, 'external': True, 'grouped': frozenset({'U', 'B', 'K', 'F', 'D',
'M', 'X', 'S', 'Z', 'T', 'C', 'P', 'Q', 'E', 'N', 'J', 'G', 'V', 'L',
'I', 'R', 'O', 'A', 'Y'})}).normalized_distance
tests/test_common.py:55: AssertionError
-- Hypothesis
--
Falsifying example: test_normalization_range(
left='0',
right='ῢ',
alg=Editex({'match_cost': 0, 'group_cost': 1, 'mismatch_cost': 2,
'local': False, 'external': True, 'grouped': frozenset({'U', 'B', 'K',
'F', 'D', 'M', 'X', 'S', 'Z', 'T', 'C', 'P', 'Q', 'E', 'N', 'J', 'G',
'V', 'L', 'I', 'R', 'O', 'A', 'Y'})}),
)
=== warnings summary
===
tests/test_external.py:16
/tmp/autopkgtest-lxc.iu33ychk/downtmp/autopkgtest_tmp/tests/test_external.py:16:
PytestUnknownMarkWarning: Unknown pytest.mark.external - is this a typo?
You can register custom marks to avoid this warning - for details, see
https://docs.pytest.org/en/stable/mark.html
@pytest.mark.external
tests/test_external.py:39
/tmp/autopkgtest-lxc.iu33ychk/downtmp/autopkgtest_tmp/tests/test_external.py:39:
PytestUnknownMarkWarning: Unknown pytest.mark.external - is this a typo?
You can register custom marks to avoid this
Bug#997208: firmware-microbit-micropython: FTBFS: platform.h:25:10: fatal error: cstddef: No such file or directory
Control: severity 998365 serious Control: close 997208 On Sun, Oct 24, 2021 at 12:48:33PM +0200, Ondřej Kuzník wrote: > On Sat, Oct 23, 2021 at 09:11:58PM +0200, Lucas Nussbaum wrote: > > Source: firmware-microbit-micropython > > Version: 1.0.1-2 > > Severity: serious > > Justification: FTBFS > > Tags: bookworm sid ftbfs > > > > Hi, > > > > During a rebuild of all packages in sid, your package failed to build > > on amd64. > > > > > > Relevant part (hopefully): > >> In file included from > >> /<>/yotta_modules/mbed-classic/api/Ethernet.h:19, > >> from > >> /<>/yotta_modules/mbed-classic/common/Ethernet.cpp:16: > >> /<>/yotta_modules/mbed-classic/api/platform.h:25:10: fatal > >> error: cstddef: No such file or directory > >>25 | #include > >> | ^ > >> compilation terminated. > > On my bookworm system this is caused by the ARM toolchain being out of > sync in the archive, sid/testing have: > - gcc-arm-none-eabi 10.3 (15:10.3-2021.07-1) > - libstdc++-arm-none-eabi from gcc 8 (15:8-2019-q3-1+13) > > Where bullseye has both at 15:8-2019-q3-1+13 (and 15:8-2019-q3-1+b1). > > In essence this is #953420 with different version combinations. I think > the first step would be to mark gcc builds with Breaks for the older > libstdc++ and vice versa. Or, if possible, submit them in lockstep. This is #998365, so the problem has to be fixed there. > Regards, > Ondrej cu Adrian
Processed: Re: Bug#997208: firmware-microbit-micropython: FTBFS: platform.h:25:10: fatal error: cstddef: No such file or directory
Processing control commands: > severity 998365 serious Bug #998365 [libstdc++-arm-none-eabi-newlib] libstdc++-arm-none-eabi-newlib: Version of libstdc++-arm-none-eabi-newlib and gcc-arm-none-eabi must match or the C++ libraries can't be found Severity set to 'serious' from 'important' > close 997208 Bug #997208 [src:firmware-microbit-micropython] firmware-microbit-micropython: FTBFS: platform.h:25:10: fatal error: cstddef: No such file or directory Marked Bug as done -- 997208: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997208 998365: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=998365 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Re: Bug#997208: firmware-microbit-micropython: FTBFS: platform.h:25:10: fatal error: cstddef: No such file or directory
Processing control commands:
> severity 998365 serious
Bug #998365 [libstdc++-arm-none-eabi-newlib] libstdc++-arm-none-eabi-newlib:
Version of libstdc++-arm-none-eabi-newlib and gcc-arm-none-eabi must match or
the C++ libraries can't be found
Ignoring request to change severity of Bug 998365 to the same value.
> close 997208
Bug #997208 {Done: Adrian Bunk }
[src:firmware-microbit-micropython] firmware-microbit-micropython: FTBFS:
platform.h:25:10: fatal error: cstddef: No such file or directory
Bug 997208 is already marked as done; not doing anything.
--
997208: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997208
998365: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=998365
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#998281: marked as done (uhd: FTBFS during binary-indep only build)
Your message dated Sat, 27 Nov 2021 23:38:22 + with message-id and subject line Bug#998281: fixed in uhd 4.1.0.4-2 has caused the Debian Bug report #998281, regarding uhd: FTBFS during binary-indep only 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.) -- 998281: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=998281 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: uhd Version: 4.1.0.4-1 Severity: serious Tags: ftbfs Justification: fails to build from source (but built successfully in the past) Hi, uhd/experimental FTBFS when building only the arch-all packages as done on the buildd: https://buildd.debian.org/status/fetch.php?pkg=uhd&arch=all&ver=4.1.0.4-1&stamp=1634959755&raw=0 fakeroot debian/rules binary-indep dh binary-indep --sourcedirectory=host --with python3 --with numpy3 --buildsystem=cmake+ninja dh_testroot -i -O--sourcedirectory=host -O--buildsystem=cmake\+ninja dh_prep -i -O--sourcedirectory=host -O--buildsystem=cmake\+ninja debian/rules override_dh_auto_install make[1]: Entering directory '/<>' cp debian/uhd-host.limits debian/uhd-host/etc/security/limits.d/uhd.conf cp: cannot create regular file 'debian/uhd-host/etc/security/limits.d/uhd.conf': No such file or directory make[1]: *** [debian/rules:33: override_dh_auto_install] Error 1 make[1]: Leaving directory '/<>' make: *** [debian/rules:17: binary-indep] Error 2 You probably need to split the override_dh_auto_install target into separate override_dh_auto_install-arch and override_dh_auto_install-indep targets. Andreas --- End Message --- --- Begin Message --- Source: uhd Source-Version: 4.1.0.4-2 Done: A. Maitland Bottoms We believe that the bug you reported is fixed in the latest version of uhd, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 998...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. A. Maitland Bottoms (supplier of updated uhd package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Sat, 27 Nov 2021 12:33:25 -0500 Source: uhd Architecture: source Version: 4.1.0.4-2 Distribution: unstable Urgency: medium Maintainer: A. Maitland Bottoms Changed-By: A. Maitland Bottoms Closes: 998281 Changes: uhd (4.1.0.4-2) unstable; urgency=medium . * fix binary-indep build (Closes: #998281) * upload to unstable Checksums-Sha1: c56c98348e9769bf5959fe4fd3fa9bc9f530d5c8 2810 uhd_4.1.0.4-2.dsc b2c676282920da5e2aec8afb94bfdfd240015020 50712 uhd_4.1.0.4-2.debian.tar.xz ecb7cdf4674130037fae011fb93b7bd680391cb7 23878 uhd_4.1.0.4-2_amd64.buildinfo Checksums-Sha256: 2c78c0b4a3ae5b9d9e85e512ff672f53e0d2ff0f5fb587457934a067cae03d7e 2810 uhd_4.1.0.4-2.dsc 89fe55a5e6a59a5538194fb1195b65c580d0cd3eb36df3056cdc9693ac01abbe 50712 uhd_4.1.0.4-2.debian.tar.xz 751a07900d94a77e1c3e0528eeaddc0740e835f9a7ec01f8befe50c213513a82 23878 uhd_4.1.0.4-2_amd64.buildinfo Files: 576cd29cb40e668d23f4a1b95accf968 2810 science optional uhd_4.1.0.4-2.dsc 6cc6a8b7cd5b7a55878547672bdc404d 50712 science optional uhd_4.1.0.4-2.debian.tar.xz 107a237c5101581821df4c8f3301c59d 23878 science optional uhd_4.1.0.4-2_amd64.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEEB8qH3cTCsGJAtrF0UEHxiR9E4JAFAmGivAgACgkQUEHxiR9E 4JAB2w/+Kgf1ndP9lZPQVWr+r5G8d64ByTtbqovwz+IcX1+unFeaQjKcX0fAB8K9 4TUNOSJCTGqZGHASU4A5f7K9O1RiLWXRz2sHsoxcV921pO+vVCk2XA68Muyjw13g hlkgBf0nUW9639ZUfkvp5hhicfZspGCrzwdXclE91eQvg8AEdHSM3R2kkNUVobq6 Qeeq+TA3xNejT55oNkh/Uh2jvg5DvL38eJAuqly08PBVmWZnZapWssy14rpYBaAu zK93FgkdDyt7L+T31+8W7mR8uprNfxDxyPdhDHivt0Ny22U7iGcdGusB2e20M/N7 PCqdrGls8myA34J/XbvnyLfRAJ7PsBmt2cH6WwjVKlXliQuv+pKZX/O9fQwMf4wy YHOMmpAp5AVa1OKOI7IYecT+gELGxpo4xCVh67FGKxR+xkpiab2C2L6SxIDbWDg5 IsEcfRrTxmOsRxsIArwn4vCFuEw+s+2IffuCu4wNZsBjzuJF9bOWZSjImjjLRy3C i/wy65uqIjpQVssJIYYzsFN+EwBDk0b3RJEy2qcpRwnDYbFf+jtjNcXGpXX5jxtN h1sM1Z3b2Tta7aGra0GtBO7TtTGy4OShrc60b1hUoSs1/MsaJdnt38OCRixg3904 iuE/PkgWOBDdnwZwcriZSlzsqEEpO/SHk9UCgFA8NufwaPTd+L0= =gc3P -END PGP SIGNATURE End Message ---
Bug#996238: ruby-hamster FTBFS caused by ruby-rbtree and ruby-sorted-set
Source: ruby-sorted-set Version: 1.0.3-2 Severity: serious User: debian-r...@lists.debian.org Usertags: ruby3.0 Tags: help After doing some debugging on the ruby-hamster FTBFS, the problem seems to be ruby-btree and ruby-sorted-set breaking the tests. In a pure Ruby 2.7 environment, this is true: SortedSet.new([1,3,2]).eql?(SortedSet.new([1,2,3])) => true Installing ruby-rbtree, and the same matcher becomes false: SortedSet.new([1,3,2]).eql?(SortedSet.new([1,2,3])) => false Now adding ruby-sorted-set in the mix for the Ruby3.0 transition, which depends on ruby-rbtree, more tests fail. This is causing ruby-hamster's tests to fail. This bug report is to indicate that this blocks the ruby-hamster fix. Regards, Daniel -- Regards, Daniel Leidert | https://www.wgdd.de/ GPG-Key RSA4096 / BEED4DED5544A4C03E283DC74BCD0567C296D05D GPG-Key ED25519 / BD3C132D8B3805D1808123AB7ACE00941E338C78 https://www.fiverr.com/dleidert https://www.patreon.com/join/dleidert signature.asc Description: This is a digitally signed message part
Processed: bug 1000729 is forwarded to https://github.com/knu/sorted_set/issues/3
Processing commands for cont...@bugs.debian.org: > forwarded 1000729 https://github.com/knu/sorted_set/issues/3 Bug #1000729 [src:ruby-sorted-set] ruby-hamster FTBFS caused by ruby-rbtree and ruby-sorted-set Set Bug forwarded-to-address to 'https://github.com/knu/sorted_set/issues/3'. > thanks Stopping processing here. Please contact me if you need assistance. -- 1000729: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1000729 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: block 996238 with 1000729
Processing commands for cont...@bugs.debian.org: > block 996238 with 1000729 Bug #996238 [src:ruby-hamster] ruby-hamster: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed: RuntimeError: 996238 was not blocked by any bugs. 996238 was not blocking any bugs. Added blocking bug(s) of 996238: 1000729 > thanks Stopping processing here. Please contact me if you need assistance. -- 996238: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=996238 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: bug 996238 is forwarded to https://github.com/hamstergem/hamster/issues/251
Processing commands for cont...@bugs.debian.org: > forwarded 996238 https://github.com/hamstergem/hamster/issues/251 Bug #996238 [src:ruby-hamster] ruby-hamster: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed: RuntimeError: Set Bug forwarded-to-address to 'https://github.com/hamstergem/hamster/issues/251'. > thanks Stopping processing here. Please contact me if you need assistance. -- 996238: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=996238 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: severity of 996238 is important, severity of 1000729 is important
Processing commands for cont...@bugs.debian.org: > severity 996238 important Bug #996238 [src:ruby-hamster] ruby-hamster: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed: RuntimeError: Severity set to 'important' from 'serious' > # workarounds are in place, so demote to important > severity 1000729 important Bug #1000729 [src:ruby-sorted-set] ruby-hamster FTBFS caused by ruby-rbtree and ruby-sorted-set Severity set to 'important' from 'serious' > thanks Stopping processing here. Please contact me if you need assistance. -- 1000729: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1000729 996238: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=996238 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#997424: marked as done (python-aiohttp-security: FTBFS: Could not import extension aiohttp_doctools (exception: cannot import name 'PyModulelevel' from 'sphinx.domains.python' (/usr/lib/python3/di
Your message dated Sun, 28 Nov 2021 01:19:53 + with message-id and subject line Bug#997424: fixed in python-aiohttp-security 0.4.0-3 has caused the Debian Bug report #997424, regarding python-aiohttp-security: FTBFS: Could not import extension aiohttp_doctools (exception: cannot import name 'PyModulelevel' from 'sphinx.domains.python' (/usr/lib/python3/dist-packages/sphinx/domains/python.py)) to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 997424: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997424 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: python-aiohttp-security Version: 0.4.0-2 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20211023 ftbfs-bookworm Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[2]: Entering directory '/<>/docs' > sphinx-build -b html -d _build/doctrees . _build/html > Running Sphinx v4.2.0 > > Extension error: > Could not import extension aiohttp_doctools (exception: cannot import name > 'PyModulelevel' from 'sphinx.domains.python' > (/usr/lib/python3/dist-packages/sphinx/domains/python.py)) > make[2]: *** [Makefile:55: html] Error 2 The full build log is available from: http://qa-logs.debian.net/2021/10/23/python-aiohttp-security_0.4.0-2_unstable.log A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! If you reassign this bug to another package, please marking it as 'affects'-ing this package. See https://www.debian.org/Bugs/server-control#affects If you fail to reproduce this, please provide a build log and diff it with mine so that we can identify if something relevant changed in the meantime. --- End Message --- --- Begin Message --- Source: python-aiohttp-security Source-Version: 0.4.0-3 Done: Martin We believe that the bug you reported is fixed in the latest version of python-aiohttp-security, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 997...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Martin (supplier of updated python-aiohttp-security package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sun, 28 Nov 2021 00:25:53 + Source: python-aiohttp-security Architecture: source Version: 0.4.0-3 Distribution: unstable Urgency: medium Maintainer: Debian Python Team Changed-By: Martin Closes: 997424 Changes: python-aiohttp-security (0.4.0-3) unstable; urgency=medium . * Add patch to update sphinx names (Closes: #997424) . [ Ondřej Nový ] * d/control: Update Maintainer field with new Debian Python Team contact address. * d/control: Update Vcs-* fields with new Debian Python Team Salsa layout. Checksums-Sha1: 764b2588e69459704f11109835e355f8360430cb 2475 python-aiohttp-security_0.4.0-3.dsc b39ac1d23ee3dbb969625b19d245094f8dbda8e7 2552 python-aiohttp-security_0.4.0-3.debian.tar.xz 1e9656d1ad1f875895b181078a230275a5afb3bc 9226 python-aiohttp-security_0.4.0-3_amd64.buildinfo Checksums-Sha256: 928844099d129450853523f85c991c13ac869d1635171fded55f57baeb8dd53e 2475 python-aiohttp-security_0.4.0-3.dsc d385a41b1f17ef5a255d9895cf0670428fe7698110a15d0d893f7a6ba6c77440 2552 python-aiohttp-security_0.4.0-3.debian.tar.xz 9f2ee6b5fb0bd865758a4bb530e54e03921cf7d38aac3f7adabbbc2c6c0a0f1b 9226 python-aiohttp-security_0.4.0-3_amd64.buildinfo Files: 5fcd0a03e4bc341810528d5f97281fef 2475 python optional python-aiohttp-security_0.4.0-3.dsc 6fa4bd7cb7ce2f79216d7baf620c7f20 2552 python optional python-aiohttp-security_0.4.0-3.debian.tar.xz f051ea51e165bebd40863ca62fb236eb 9226 python optional python-aiohttp-security_0.4.0-3_amd64.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEftHeo0XZoKEY1KdA4+Chwoa5Y+oFAmGi0sAACgkQ4+Chwoa5 Y+re1Q//RmdBSg8T5RO1xd83X1Ii/zYrKqovEnJUL92UhKN8fpfX7ljOnXc0juLk 5pvWAVCdPsapeal1ifWlDGehkS1cbRqx+q00/gyfw0WHkf1PyE9ASpSUocWqGdCf zpRBRxWJr68mBcVXqLABP5JvX3+l9X5to000KbDEOQ844VJVnwmevGUeQs6XYCPd yRddYTpPhiJsM54PBE2+fIg/WipVZ3ZsyiWczsJk6AxbUa6ppdoQwuvyH0zLD1Zu rF
Processed: tagging 999857
Processing commands for cont...@bugs.debian.org: > tags 999857 + pending Bug #999857 [src:mod-wsgi] mod-wsgi FTBFS with python 3.10 as supported version Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 999857: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=999857 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1000204: marked as done (pyfai: FTBFS if built using python3.10 (collections.MutableSets deprecated))
Your message dated Sun, 28 Nov 2021 02:48:31 + with message-id and subject line Bug#1000204: fixed in pyfai 0.20.0+dfsg1-4.1 has caused the Debian Bug report #1000204, regarding pyfai: FTBFS if built using python3.10 (collections.MutableSets deprecated) to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1000204: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1000204 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: pyfai Version: 0.20.0+dfsg1-4 Severity: serious Tags: patch ftbfs Justification: fails to build from source (but built successfully in the past) User: ubuntu-de...@lists.ubuntu.com Usertags: origin-ubuntu jammy ubuntu-patch X-Debbugs-Cc: sl...@ubuntu.com Dear Maintainer, collections.MutableSet was deprecated a long time ago and removed with python3.10. https://docs.python.org/3/whatsnew/3.10.html#removed https://bugs.python.org/issue37324 Using the old class name leads to autopkgtest failures such as this one: ``` == ERROR: test_import_all_modules (pyFAI.test.test_bug_regression.TestBugRegression) Try to import every single module in the package -- Traceback (most recent call last): File "/<>/pyfai-0.20.0+dfsg1/.pybuild/cpython3_3.10_pyfai/build/pyFAI/test/test_bug_regression.py", line 286, in test_import_all_modules raise err File "/<>/pyfai-0.20.0+dfsg1/.pybuild/cpython3_3.10_pyfai/build/pyFAI/test/test_bug_regression.py", line 271, in test_import_all_modules load_source(fqn, path) File "/<>/pyfai-0.20.0+dfsg1/.pybuild/cpython3_3.10_pyfai/build/pyFAI/test/test_bug_regression.py", line 78, in load_source spec.loader.exec_module(module) File "", line 883, in exec_module File "", line 241, in _call_with_frames_removed File "/<>/pyfai-0.20.0+dfsg1/.pybuild/cpython3_3.10_pyfai/build/pyFAI/utils/orderedset.py", line 30, in class OrderedSet(collections.MutableSet): AttributeError: module 'collections' has no attribute 'MutableSet' ``` In Ubuntu, the attached patch was applied to achieve the following: * Fix FTBFS with python3.10, due to deprecated collections.MutableSets Forwarded upstream: https://github.com/silx-kit/pyFAI/pull/1588 Thanks for considering the patch. Cheers, Lukas -- System Information: Debian Release: 11.0 APT prefers impish-updates APT policy: (500, 'impish-updates'), (500, 'impish-security'), (500, 'impish'), (100, 'impish-backports') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.13.0-20-generic (SMP w/4 CPU threads) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_WARN, TAINT_OOT_MODULE Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE=de_DE:en_GB:en Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled diff -Nru pyfai-0.20.0+dfsg1/debian/patches/python3.10-compat.patch pyfai-0.20.0+dfsg1/debian/patches/python3.10-compat.patch --- pyfai-0.20.0+dfsg1/debian/patches/python3.10-compat.patch 1970-01-01 01:00:00.0 +0100 +++ pyfai-0.20.0+dfsg1/debian/patches/python3.10-compat.patch 2021-11-19 16:51:28.0 +0100 @@ -0,0 +1,40 @@ +Description: Fix collections.MutableSets compat with python3.10 + collections.MutableSet was deprecated a long time ago and removed with python3.10. + https://docs.python.org/3/whatsnew/3.10.html#removed + https://bugs.python.org/issue37324 + + Using the old class name leads to test failures such as this one: + == + ERROR: test_import_all_modules (pyFAI.test.test_bug_regression.TestBugRegression) + Try to import every single module in the package + -- + Traceback (most recent call last): + File "/<>/pyfai-0.20.0+dfsg1/.pybuild/cpython3_3.10_pyfai/build/pyFAI/test/test_bug_regression.py", line 286, in test_import_all_modules + raise err + File "/<>/pyfai-0.20.0+dfsg1/.pybuild/cpython3_3.10_pyfai/build/pyFAI/test/test_bug_regression.py", line 271, in test_import_all_modules + load_source(fqn, path) + File "/<>/pyfai-0.20.0+dfsg1/.pybuild/cpython3_3.10_pyfai/build/pyFAI/test/test_bug_regression.py", line 78, in load_source + spec.loader.exec_module(module) + File "", line 883, in exec_module + File "", line 241, in _call_with_frames_removed + File "/<>/pyfai-0.20.0+dfsg1/.pybuild/cpython3_3.10_pyfai/build/pyFAI/utils/orderedset.py", line 30, in +
Bug#996294: Change in webrick 1.7.0 is causing a problem with the tests in Ruby 2.7 (at least)
I did some debugging on the issue reported that the tests fail after adding
ruby-webrick 1.7.0 to b-d for Ruby 3.0.
The problem is in parse_header() (lib/httpclient/session.rb) in the line
828 line = socket.gets("\n")
With webrick 1.7.0 it stalls here. This is caused by this small change in
webrick:
https://github.com/ruby/webrick/commit/069e9b1908aad3a30a0dcf67b6d3bb13c3216d2c
If I revert this, the tests no longer timeout and succeed under Ruby 2.7.
Regards, Daniel
--
Regards,
Daniel Leidert | https://www.wgdd.de/
GPG-Key RSA4096 / BEED4DED5544A4C03E283DC74BCD0567C296D05D
GPG-Key ED25519 / BD3C132D8B3805D1808123AB7ACE00941E338C78
https://www.fiverr.com/dleidert
https://www.patreon.com/join/dleidert
signature.asc
Description: This is a digitally signed message part
Processed: bug 996294 is forwarded to https://github.com/nahi/httpclient/issues/448
Processing commands for cont...@bugs.debian.org: > forwarded 996294 https://github.com/nahi/httpclient/issues/448 Bug #996294 [src:ruby-httpclient] ruby-httpclient: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed. Set Bug forwarded-to-address to 'https://github.com/nahi/httpclient/issues/448'. > thanks Stopping processing here. Please contact me if you need assistance. -- 996294: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=996294 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: tagging 996294
Processing commands for cont...@bugs.debian.org: > tags 996294 - pending Bug #996294 [src:ruby-httpclient] ruby-httpclient: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed. Removed tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 996294: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=996294 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1000680: python3-aiohttp: fails to import, "TypeError: function() argument 'code' must be code, not str"
> root@zion:/# python3.9 -c "import aiohttp" > Traceback (most recent call last): > File "", line 1, in > File "/usr/lib/python3/dist-packages/aiohttp/__init__.py", line 6, in > > from .client import ( > File "/usr/lib/python3/dist-packages/aiohttp/client.py", line 35, in > > from . import hdrs, http, payload > File "/usr/lib/python3/dist-packages/aiohttp/http.py", line 7, in > from .http_parser import ( > File "/usr/lib/python3/dist-packages/aiohttp/http_parser.py", line 15, in > > from .helpers import NO_EXTENSIONS, BaseTimerContext > File "/usr/lib/python3/dist-packages/aiohttp/helpers.py", line 667, in > > class CeilTimeout(async_timeout.timeout): > TypeError: function() argument 'code' must be code, not str > > > root@zion:/# python3.10 -c "import aiohttp" > Traceback (most recent call last): > File "", line 1, in > File "/usr/lib/python3/dist-packages/aiohttp/__init__.py", line 6, in > > from .client import ( > File "/usr/lib/python3/dist-packages/aiohttp/client.py", line 35, in > > from . import hdrs, http, payload > File "/usr/lib/python3/dist-packages/aiohttp/http.py", line 7, in > from .http_parser import ( > File "/usr/lib/python3/dist-packages/aiohttp/http_parser.py", line 15, in > > from .helpers import NO_EXTENSIONS, BaseTimerContext > File "/usr/lib/python3/dist-packages/aiohttp/helpers.py", line 667, in > > class CeilTimeout(async_timeout.timeout): > TypeError: function() argument 'code' must be code, not str Boyuan, you caused this by uploading python-async-timeout 4.x https://tracker.debian.org/news/1280914/accepted-python-async-timeout-401-1-source-into-unstable/ while aiohttp is incompatible with it. Apparently the latest version of aiohttp supports async-timeout > 4.0 https://github.com/aio-libs/aiohttp/blob/v3.8.1/setup.cfg#L54 are you going to handle this upgrade?
Bug#1000233: php-remctl lost its phpapi-20190902 dependency
Adrian Bunk writes:
> Package: php-remctl
> Version: 3.17-1
> Severity: serious
> Tags: bookworm sid
> After the src:remctl rebuild to add Python 3.10 as supported version,
> php-remctl lost its phpapi-20190902 dependency:
> Package: php-remctl
> Source: remctl
> Version: 3.17-1
> Installed-Size: 109
> Depends: php-common (>= 1:7.0+33~), phpapi-20190902, libc6 (>= 2.14),
> libremctl1 (>= 3.1)
> Package: php-remctl
> Source: remctl (3.17-1)
> Version: 3.17-1+b2
> Installed-Size: 106
> Depends: php-common (>= 1:7.0+33~), libc6 (>= 2.14), libremctl1 (>= 3.1)
This appears to be intentional in dh-php 4.2:
# Disable the dependency on the phpapi for the transition period
# $depends .= ", " . join(" | ", @api_versions);
PHP maintainers, do you have guidance on this? Should I be doing anything
as a package maintainer, or is this expected? Should it be a serious bug?
--
Russ Allbery (r...@debian.org)
Bug#1000187: [Pkg-auth-maintainers] Bug#1000187: yubikey-manager: Exception when trying to add an oath account
Hi Tobias, On Fri, Nov 19, 2021 at 11:51:46AM +, Tobias Bengfort wrote: > Package: yubikey-manager > Version: 4.0.0~a1-4 > Severity: grave > Justification: renders package unusable > > Dear Maintainer, > >$ ykman oath accounts add foo bar > > always results in > >AttributeError: 'OATH_TYPE' object has no attribute 'upper' Can you try again with yubikey-manager 4.0.7-1 (currently in unstable and testing)? I'm unable to reproduce your issue there, and seem to be able to successfully add an account, once I figured out a valid format for the secret: $ echo '123456' | base64 MTIzNDU2Cg== $ ykman oath accounts add foo 'MTIzNDU2Cg==' $ echo $? 0 $ ykman oath accounts list foo Florian
Bug#1000732: python3-click-threading: broken monkeypatching
Package: python3-click-threading
Version: 0.4.4-2
Severity: serious
X-Debbugs-Cc: none, Tollef Fog Heen
It seems like the monkeypatching in
/usr/lib/python3/dist-packages/click_threading/monkey.py is broken, at
least for me. I'm using python3-click-threading by way of vdirsyncer:
$ vdirsyncer -vdebug sync
debug: Using 1 maximal workers.
) -> None
lambda ) -> None: clear._real_click_fn() -> None)
error: Unknown error occurred: unmatched ')' (, line 1)
error: Use `-vdebug` to see the full traceback.
debug: File "/usr/lib/python3/dist-packages/vdirsyncer/cli/__init__.py", line
30, in inner
debug: f(*a, **kw)
debug: File "/usr/lib/python3/dist-packages/vdirsyncer/cli/__init__.py", line
145, in sync
debug: with wq.join():
debug: File "/usr/lib/python3.9/contextlib.py", line 119, in __enter__
debug: return next(self.gen)
debug: File "/usr/lib/python3/dist-packages/vdirsyncer/cli/utils.py", line
364, in join
debug: with ui_worker.patch_click():
debug: File "/usr/lib/python3.9/contextlib.py", line 119, in __enter__
debug: return next(self.gen)
debug: File "/usr/lib/python3/dist-packages/click_threading/__init__.py",
line 144, in patch_click
debug: with patch_ui_functions(wrapper):
debug: File "/usr/lib/python3.9/contextlib.py", line 119, in __enter__
debug: return next(self.gen)
debug: File "/usr/lib/python3/dist-packages/click_threading/monkey.py", line
50, in patch_ui_functions
debug: stub_f = eval('lambda {s}: {n}._real_click_fn({a})'
Adding a few prints shows that it's trying do do an eval of the string:
lambda ) -> None: clear._real_click_fn() -> None)
This, unsurprisingly, does not work. I'm not sure what component has
changed in a way that breaks python3-click-threading, but the patching
seems pretty brittle.
-- System Information:
Versions of packages python3-click-threading depends on:
ii python33.9.7-1
ii python3-click 8.0.2-1
python3-click-threading recommends no packages.
python3-click-threading suggests no packages.
-- no debconf information
--
Tollef Fog Heen
UNIX is user friendly, it's just picky about who its friends are
Processed: Bug#987816 marked as pending in dask.distributed
Processing control commands: > tag -1 pending Bug #987816 [src:dask.distributed] dask.distributed: FTBFS due to a build-time test failure Added tag(s) pending. -- 987816: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=987816 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#987816: marked as pending in dask.distributed
Control: tag -1 pending Hello, Bug #987816 in dask.distributed reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/python-team/packages/dask.distributed/-/commit/82fc3a8274972ec9c1c4619a2b1291f09fcdf0c0 Import Debian changes 2021.01.0+ds.1-2.1 dask.distributed (2021.01.0+ds.1-2.1) unstable; urgency=medium . * Non-maintainer upload. * Backport upstream fix removing tests that fail under some circumstances. (Closes: #987816) * python-distributed-doc: Fix broken symlink to html5shiv.min.js, dh_link needs absolute paths. (Closes: #988675) (this message was generated automatically) -- Greetings https://bugs.debian.org/987816
