Bug#1008407: marked as done (mobile-atlas-creator: FTBFS: I/O error : Attempt to load network entity http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd)
Your message dated Sun, 10 Apr 2022 05:48:55 + with message-id and subject line Bug#1008407: fixed in mobile-atlas-creator 2.1.4+dfsg.1-2 has caused the Debian Bug report #1008407, regarding mobile-atlas-creator: FTBFS: I/O error : Attempt to load network entity http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd 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.) -- 1008407: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1008407 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: mobile-atlas-creator Version: 2.1.4+dfsg.1-1 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20220326 ftbfs-bookworm Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[1]: Entering directory '/<>' > xsltproc -''-nonet -''-param man.charmap.use.subset "0" > /usr/share/sgml/docbook/stylesheet/xsl/docbook-xsl/manpages/docbook.xsl > debian/mobile-atlas-creator.xml > I/O error : Attempt to load network entity > http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd > debian/mobile-atlas-creator.xml:62: warning: failed to load external entity > "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd; > ]> > ^ > Note: Writing mobile-atlas-creator.1 > winicontoppm -allicons -writeands misc/mobac.ico mobac > winicontoppm: abnormal bit per pixel value 24 > make[1]: *** [debian/rules:28: mobac.xpm] Error 1 The full build log is available from: http://qa-logs.debian.net/2022/03/26/mobile-atlas-creator_2.1.4+dfsg.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: mobile-atlas-creator Source-Version: 2.1.4+dfsg.1-2 Done: Ying-Chun Liu (PaulLiu) We believe that the bug you reported is fixed in the latest version of mobile-atlas-creator, 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 1008...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Ying-Chun Liu (PaulLiu) (supplier of updated mobile-atlas-creator 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, 10 Apr 2022 13:11:30 +0800 Source: mobile-atlas-creator Architecture: source Version: 2.1.4+dfsg.1-2 Distribution: unstable Urgency: low Maintainer: Ying-Chun Liu (PaulLiu) Changed-By: Ying-Chun Liu (PaulLiu) Closes: 1008407 Changes: mobile-atlas-creator (2.1.4+dfsg.1-2) unstable; urgency=low . * Use icotool instead of winicontoppm because winicontoppm now doesn't support depth 24 images. * Use local docbookx.dtd (Closes: #1008407) Checksums-Sha1: aabfa5f16190b24255fbf4c2440a71cd99099721 2357 mobile-atlas-creator_2.1.4+dfsg.1-2.dsc 187bdec772d728be28dffcd98efdf3932f4e2cd9 8804 mobile-atlas-creator_2.1.4+dfsg.1-2.debian.tar.xz 4950b9e88fd1c252eb4f223d968e913d7b16b0d2 12280 mobile-atlas-creator_2.1.4+dfsg.1-2_source.buildinfo Checksums-Sha256: dba0b367ab8770d9fd01eb477dd5f75564807004b6df99a56565c955fc908b18 2357 mobile-atlas-creator_2.1.4+dfsg.1-2.dsc 5e7fa6d46d95e1636b0c4cc58b757a2c5f347cc4222fa48e9cb11679e51c1324 8804 mobile-atlas-creator_2.1.4+dfsg.1-2.debian.tar.xz ca3f0436162d6ea99da680e0b84d4d7a1ff4102e1096af266191d0c8cf79b76f 12280 mobile-atlas-creator_2.1.4+dfsg.1-2_source.buildinfo Files: 2b03a4096445c055141d9b30ab487931 2357 utils optional mobile-atlas-creator_2.1.4+dfsg.1-2.dsc bbb897fc2e835c88fa64d63d1d5017fa 8804 utils optional mobile-atlas-creator_2.1.4+dfsg.1-2.debian.tar.xz 16234e26ca4adc18e3a1e9b2d02ff35a 12280 utils optional mobile-atlas-creator_2.1.4+dfsg.1-2_source.buildinfo -BEGIN PGP SIGNATURE- iQJGBAEBCgAxFiEEo2h49GQQhoFgDLZIRBc/oT0FiIgFAmJSaisTHHBhdWxsaXVA
Bug#1009087: marked as done (booth: (autopkgtest) needs update for python3.10: module 'collections' has no attribute 'MutableSet')
Your message dated Sun, 10 Apr 2022 05:34:00 + with message-id and subject line Bug#1009087: fixed in crmsh 4.3.1-2 has caused the Debian Bug report #1009087, regarding booth: (autopkgtest) needs update for python3.10: module 'collections' has no attribute 'MutableSet' 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.) -- 1009087: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1009087 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: booth Version: 1.0-237-gdd88847-4 Severity: serious Tags: sid bookworm User: debian...@lists.debian.org Usertags: needs-update User: debian-pyt...@lists.debian.org Usertags: python3.10 Control: affects -1 src:python3-defaults Dear maintainer(s), We are in the transition of making python3.10 the default Python versions [0]. With a recent upload of python3-defaults the autopkgtest of booth fails in testing when that autopkgtest is run with the binary packages of python3-defaults from unstable. It passes when run with only packages from testing. In tabular form: passfail python3-defaults from testing3.10.4-1 booth from testing1.0-237-gdd88847-4 all others from testingfrom testing I copied some of the output at the bottom of this report. Currently this regression is blocking the migration of python3-defaults to testing [1]. https://docs.python.org/3/whatsnew/3.10.html lists what's new in Python3.10, it may help to identify what needs to be updated. https://docs.python.org/3.9/library/collections.html says: """ Deprecated since version 3.3, will be removed in version 3.10: Moved Collections Abstract Base Classes to the collections.abc module. For backwards compatibility, they continue to be visible in this module through Python 3.9. """ Time to move on. More information about this bug and the reason for filing it can be found on https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation Paul [0] https://bugs.debian.org/996584 [1] https://qa.debian.org/excuses.php?package=python3-defaults https://ci.debian.net/data/autopkgtest/testing/arm64/b/booth/20647454/log.gz === config === authfile = /etc/booth/authkey site = 127.0.0.1 ticket = "ticket-A" === cluster === Traceback (most recent call last): File "/usr/sbin/crm", line 29, in from crmsh import main File "/usr/lib/python3/dist-packages/crmsh/main.py", line 18, in from . import ui_root File "/usr/lib/python3/dist-packages/crmsh/ui_root.py", line 23, in from . import ui_cib File "/usr/lib/python3/dist-packages/crmsh/ui_cib.py", line 16, in from .cibconfig import cib_factory File "/usr/lib/python3/dist-packages/crmsh/cibconfig.py", line 23, in from . import orderedset File "/usr/lib/python3/dist-packages/crmsh/orderedset.py", line 29, in class OrderedSet(collections.MutableSet): AttributeError: module 'collections' has no attribute 'MutableSet' Traceback (most recent call last): File "/usr/sbin/crm", line 29, in from crmsh import main File "/usr/lib/python3/dist-packages/crmsh/main.py", line 18, in from . import ui_root File "/usr/lib/python3/dist-packages/crmsh/ui_root.py", line 23, in from . import ui_cib File "/usr/lib/python3/dist-packages/crmsh/ui_cib.py", line 16, in from .cibconfig import cib_factory File "/usr/lib/python3/dist-packages/crmsh/cibconfig.py", line 23, in from . import orderedset File "/usr/lib/python3/dist-packages/crmsh/orderedset.py", line 29, in class OrderedSet(collections.MutableSet): AttributeError: module 'collections' has no attribute 'MutableSet' Traceback (most recent call last): File "/usr/sbin/crm", line 29, in from crmsh import main File "/usr/lib/python3/dist-packages/crmsh/main.py", line 18, in from . import ui_root File "/usr/lib/python3/dist-packages/crmsh/ui_root.py", line 23, in from . import ui_cib File "/usr/lib/python3/dist-packages/crmsh/ui_cib.py", line 16, in from .cibconfig import cib_factory File "/usr/lib/python3/dist-packages/crmsh/cibconfig.py", line 23, in from . import orderedset File "/usr/lib/python3/dist-packages/crmsh/orderedset.py", line 29, in class OrderedSet(collections.MutableSet): AttributeError: module 'collections' has no attribute 'MutableSet' Traceback (most recent call last): File "/usr/sbin/crm", line 29, in from crmsh import main File "/usr/lib/python3/dist-packages/crmsh/main.py", line 18, in from . import ui_root File
Processed: Re: Bug#1008775: node-expat: Odd autopkgtest failure, prevents migration of nodejs
Processing control commands: > severity -1 normal Bug #1008775 [src:node-expat] node-expat: Odd autopkgtest failure, prevents migration of nodejs Severity set to 'normal' from 'serious' > tags -1 + moreinfo Bug #1008775 [src:node-expat] node-expat: Odd autopkgtest failure, prevents migration of nodejs Ignoring request to alter tags of bug #1008775 to the same tags previously set -- 1008775: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1008775 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1008775: node-expat: Odd autopkgtest failure, prevents migration of nodejs
Control: severity -1 normal Control: tags -1 + moreinfo Hi all, problem seems fixed elsewhere: build & autopkgtest works fine now
Bug#1008419: marked as done (charactermanaj: FTBFS: winicontoppm: abnormal bit per pixel value 32)
Your message dated Sun, 10 Apr 2022 04:48:47 + with message-id and subject line Bug#1008419: fixed in charactermanaj 0.998+git20190331.e45260e3-2 has caused the Debian Bug report #1008419, regarding charactermanaj: FTBFS: winicontoppm: abnormal bit per pixel value 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.) -- 1008419: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1008419 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: charactermanaj Version: 0.998+git20190331.e45260e3-1 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20220326 ftbfs-bookworm Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > debian/rules build > dh build >dh_update_autotools_config >dh_autoreconf >dh_auto_configure > mh_patchpoms -pcharactermanaj --debian-build --keep-pom-version > --maven-repo=/<>/charactermanaj-0.998\+git20190331.e45260e3/debian/maven-repo >debian/rules override_dh_auto_build > make[1]: Entering directory '/<>' > winicontoppm -allicons -writeands icon.ico icon_tmp > winicontoppm: abnormal bit per pixel value 32 > make[1]: *** [debian/rules:27: icon.xpm] Error 1 The full build log is available from: http://qa-logs.debian.net/2022/03/26/charactermanaj_0.998+git20190331.e45260e3-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: charactermanaj Source-Version: 0.998+git20190331.e45260e3-2 Done: Ying-Chun Liu (PaulLiu) We believe that the bug you reported is fixed in the latest version of charactermanaj, 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 1008...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Ying-Chun Liu (PaulLiu) (supplier of updated charactermanaj 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, 10 Apr 2022 12:27:37 +0800 Source: charactermanaj Architecture: source Version: 0.998+git20190331.e45260e3-2 Distribution: unstable Urgency: low Maintainer: Ying-Chun Liu (PaulLiu) Changed-By: Ying-Chun Liu (PaulLiu) Closes: 1008419 Changes: charactermanaj (0.998+git20190331.e45260e3-2) unstable; urgency=low . * Use icotool instead of winicontoppm because winicontoppm now doesn't support depth 32 images. (Closes: #1008419) Checksums-Sha1: bde0345e597235a607fd1e9f37bc96f73b451b25 2227 charactermanaj_0.998+git20190331.e45260e3-2.dsc 3e767dc19a75f7300cf535ced44c665be13d8d38 6996 charactermanaj_0.998+git20190331.e45260e3-2.debian.tar.xz f749218dbc304a50bd2c098e182e772174924619 17858 charactermanaj_0.998+git20190331.e45260e3-2_source.buildinfo Checksums-Sha256: 0f6ce033fe7b46696026c60d86490cafa34f4d76317e7e597a1fc8d4d872334e 2227 charactermanaj_0.998+git20190331.e45260e3-2.dsc c31101c1a0fb1e63a8dc5a51d1099f86a92ae968089f00a016bc8fca17f34662 6996 charactermanaj_0.998+git20190331.e45260e3-2.debian.tar.xz 6c1d9c0b221bcc6371883cf05586d4edf857bab9c24dbf1adfb00f2091b0341f 17858 charactermanaj_0.998+git20190331.e45260e3-2_source.buildinfo Files: 4263835db190eab052b40cc856e0e139 2227 graphics optional charactermanaj_0.998+git20190331.e45260e3-2.dsc 6c5dee0836ce9f142f2ee8b49b07c24e 6996 graphics optional charactermanaj_0.998+git20190331.e45260e3-2.debian.tar.xz 5ecc35a9bfd0192dae1f31e89e0a6b6d 17858 graphics optional charactermanaj_0.998+git20190331.e45260e3-2_source.buildinfo -BEGIN PGP SIGNATURE- iQJHBAEBCgAxFiEEo2h49GQQhoFgDLZIRBc/oT0FiIgFAmJSX0wTHHBhdWxsaXVA ZGViaWFuLm9yZwAKCRBEFz+hPQWIiHAfEAC6XZkCwa751hwVHHzdixo4EDSr8tzF hQWrO7CVtcPMLQ5owH2f2lbP0WiNwhsgiS++itemtkx7jhDsmRfwfzGQoDaFmK2J
Bug#1009168: marked as done (gzip: CVE-2022-1271: zgrep: arbitrary-file-write vulnerability)
Your message dated Sun, 10 Apr 2022 03:03:48 + with message-id and subject line Bug#1009168: fixed in gzip 1.12-1 has caused the Debian Bug report #1009168, regarding gzip: CVE-2022-1271: zgrep: arbitrary-file-write vulnerability 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.) -- 1009168: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1009168 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: xz-utils Version: 5.2.5-2 Severity: important Tags: security upstream X-Debbugs-Cc: car...@debian.org, Debian Security Team Control: clone -1 -2 Control: retitle -2 gzip: CVE-2022-1271: zgrep: arbitrary-file-write vulnerability Control: reassign -2 src:gzip 1.10-4 Control: found -2 1.9-3 Hi, The following vulnerability was published for xz-utils and gzip, both have to date assigned the same CVE, and cloning this bug as well for one for gzip. CVE-2022-1271[0]: | zgrep, xzgrep: arbitrary-file-write vulnerability If you fix the vulnerability please also make sure to include the CVE (Common Vulnerabilities & Exposures) id in your changelog entry. For further information see: [0] https://security-tracker.debian.org/tracker/CVE-2022-1271 https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-1271 [1] https://www.openwall.com/lists/oss-security/2022/04/07/8 [2] https://git.tukaani.org/?p=xz.git;a=commit;h=69d1b3fc29677af8ade8dc15dba83f0589cb63d6 [3] https://lists.gnu.org/r/bug-gzip/2022-04/msg00011.html Please adjust the affected versions in the BTS as needed. Regards, Salvatore --- End Message --- --- Begin Message --- Source: gzip Source-Version: 1.12-1 Done: Milan Kupcevic We believe that the bug you reported is fixed in the latest version of gzip, 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 1009...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Milan Kupcevic (supplier of updated gzip 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, 09 Apr 2022 22:22:26 -0400 Source: gzip Architecture: source Version: 1.12-1 Distribution: sid Urgency: high Maintainer: Milan Kupcevic Changed-By: Milan Kupcevic Closes: 149775 1009168 Changes: gzip (1.12-1) sid; urgency=high . * new upstream release - zgrep: fix arbitrary-file-write vulnerability address CVE-2022-1271 (closes: #1009168) - report correct length of 4 GiB and larger files (closes: #149775) - zgrep: fix "binary file matches" mislabeling; remove zgrep-syntax-error.diff patch - gzip: port to SIGPIPE-less platforms; remove sigpipe.diff patch - gzexe: fix count of lines to skip; remove corresponding patch * set standards version to 4.6.0 * update copyright notice Checksums-Sha1: 4db4932740e481782b9487f62059278872faac41 2009 gzip_1.12-1.dsc 318107297587818c8f1e1fbb55962f4b2897bc0b 825548 gzip_1.12.orig.tar.xz 981d0a887e94223ceb31930395b34af5e8e21270 833 gzip_1.12.orig.tar.xz.asc 7208c37128ef7dcd949913b49475ac7a09cfb60a 18736 gzip_1.12-1.debian.tar.xz f2836da5694551e14eb81c4ae108a2e6229f3521 7370 gzip_1.12-1_amd64.buildinfo Checksums-Sha256: 49a287787a0b4fc816eb576c011c472d1f630ec1778dfa120bd7fce4a844c253 2009 gzip_1.12-1.dsc ce5e03e519f637e1f814011ace35c4f87b33c0bbabeec35baf5fbd3479e91956 825548 gzip_1.12.orig.tar.xz 3ed9ab54452576e0be0d477c772c9f47baa36415133fef7dd1fcf7b15480ba32 833 gzip_1.12.orig.tar.xz.asc fcf2317e8eeddd66766ec5f3853025b109bd13815ec86ed6563e1af68d17193a 18736 gzip_1.12-1.debian.tar.xz 54b6d99094516ce5ee993b5176c48753908f16628b944ea80975629aa8b3b091 7370 gzip_1.12-1_amd64.buildinfo Files: 7330ad11030af6a41177b5abbcd2aa90 2009 utils required gzip_1.12-1.dsc 9608e4ac5f061b2a6479dc44e917a5db 825548 utils required gzip_1.12.orig.tar.xz 431c7f48daf19af368c0bdc483f830a5 833 utils required gzip_1.12.orig.tar.xz.asc 6c75c37b14877fadf4733520164136a4 18736 utils required gzip_1.12-1.debian.tar.xz 3fcedc2f6569ee099684c3aa48ad0bd0 7370 utils required gzip_1.12-1_amd64.buildinfo -BEGIN PGP SIGNATURE- iQHFBAEBCgAvFiEEVkf/m69krCYf+z+G6e1ngbRVCQ4FAmJSRNsRHG1pbGFuQGRl Ymlhbi5vcmcACgkQ6e1ngbRVCQ6ujwwAvqbrGRMGRQCq54Tp9aMJNFz0W+CJ4woW
Bug#1005028: marked as done (pyx3: fix t1 extension with Python 3.10)
Your message dated Sun, 10 Apr 2022 02:48:49 +
with message-id
and subject line Bug#1005028: fixed in pyx3 0.15-6
has caused the Debian Bug report #1005028,
regarding pyx3: fix t1 extension with Python 3.10
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
1005028: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1005028
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: pyx3
Version: 0.15-5
Severity: normal
Dear Maintainer,
building pyx3 with python 3.10 is failing:
Traceback (most recent call last):
File "/tmp/autopkgtest.UtTakl/autopkgtest_tmp/examples/text/marker.py",
line 10, in
c.writeEPSfile("marker")
File "/usr/lib/python3/dist-packages/pyx/canvas.py", line 50, in
wrappedindocument
return method(d, file, **write_kwargs)
File "/usr/lib/python3/dist-packages/pyx/document.py", line 185, in
writeEPSfile
pswriter.EPSwriter(self, f, **kwargs)
File "/usr/lib/python3/dist-packages/pyx/pswriter.py", line 169, in __init__
registry.output(file, self)
File "/usr/lib/python3/dist-packages/pyx/pswriter.py", line 52, in output
resource.output(file, writer, self)
File "/usr/lib/python3/dist-packages/pyx/font/font.py", line 57, in output
self.t1file.getstrippedfont(self.glyphnames,
self.charcodes).outputPS(file, writer)
File "/usr/lib/python3/dist-packages/pyx/font/t1file.py", line 1019,
in getstrippedfont
self.gatherglyphcalls(glyph, seacglyphs, subrs, T1context(self))
File "/usr/lib/python3/dist-packages/pyx/font/t1file.py", line 900,
in gatherglyphcalls
self.gathercalls(self.getglyphcmds(glyph), seacglyphs, subrs, context)
File "/usr/lib/python3/dist-packages/pyx/font/t1file.py", line 859,
in getglyphcmds
self._data2decode()
File "/usr/lib/python3/dist-packages/pyx/font/t1file.py", line 721,
in _data2decode
self._data2 = self._eexecdecode(self._data2eexec)
File "/usr/lib/python3/dist-packages/pyx/font/t1file.py", line 670,
in _eexecdecode
return decoder(code, self.eexecr, 4)
SystemError: PY_SSIZE_T_CLEAN macro must be defined for '#' formats
Python 3.10 is now enforcing https://www.python.org/dev/peps/pep-0353/
Upstream has a fix in commit
https://github.com/pyx-project/pyx/commit/0f2834330f7c86dbb5de9f75f9c7c8b7ab4ebabf
via PR https://github.com/pyx-project/pyx/pull/35
--- End Message ---
--- Begin Message ---
Source: pyx3
Source-Version: 0.15-6
Done: Stuart Prescott
We believe that the bug you reported is fixed in the latest version of
pyx3, 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 1005...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Stuart Prescott (supplier of updated pyx3 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, 09 Apr 2022 13:26:04 +1000
Source: pyx3
Architecture: source
Version: 0.15-6
Distribution: unstable
Urgency: medium
Maintainer: Stuart Prescott
Changed-By: Stuart Prescott
Closes: 1005028
Changes:
pyx3 (0.15-6) unstable; urgency=medium
.
* Fix T1 extension compilation with Python 3.10 with thanks to Andreas
Hasenack for the report and the patch (Closes: #1005028).
* Add lintian overrides to silence some noise.
Checksums-Sha1:
adde020d22e29dd19741cbceb66bf0bf977cbb74 2300 pyx3_0.15-6.dsc
d402b5e65e8bd80807077de70a7105272189fb1d 19796 pyx3_0.15-6.debian.tar.xz
ea30f9c60667c44890f59385fc15aefdb86af423 11779 pyx3_0.15-6_amd64.buildinfo
Checksums-Sha256:
2ad23d3df14b8646eef430bf1e21b941ed8d03adac7a60092896a8b44d1a6055 2300
pyx3_0.15-6.dsc
33d381a548278fdc19508dde2f9aed35cb4cd4b2123cfc0e6335b1c277026562 19796
pyx3_0.15-6.debian.tar.xz
583ceb333c64dd64d3f891a30f83c29c778e4441498dc9d2add0021edb12d364 11779
pyx3_0.15-6_amd64.buildinfo
Files:
b5506635070eee7e5f2d3c3ffecc8474 2300 python optional pyx3_0.15-6.dsc
e62ac7d9b2c9d60496a1970f91d18536 19796 python optional
pyx3_0.15-6.debian.tar.xz
04afb2a7497aedd1c9d936c7e96a9607 11779 python optional
pyx3_0.15-6_amd64.buildinfo
-BEGIN PGP SIGNATURE-
iQIzBAEBCAAdFiEEkOLSwa0Uaht+u4kdu8F+uxOW8vcFAmJRDHgACgkQu8F+uxOW
8vdMlA//ZnCxdwbJdPul2h7vYSELYIPyGkUXdu4zYaGfT9nSztGS8LSIwodo52XF
Bug#965560: marked as done (gnome-icon-theme-yasis: Removal of obsolete debhelper compat 5 and 6 in bookworm)
Your message dated Sun, 10 Apr 2022 00:03:45 + with message-id and subject line Bug#965560: fixed in gnome-icon-theme-yasis 0.4.2-1.2 has caused the Debian Bug report #965560, regarding gnome-icon-theme-yasis: Removal of obsolete debhelper compat 5 and 6 in bookworm to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 965560: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=965560 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: gnome-icon-theme-yasis Version: 0.4.2-1 Severity: normal Usertags: compat-5-6-removal Hi, The package gnome-icon-theme-yasis uses debhelper with a compat level of 5 or 6, which is deprecated and scheduled for removal[1]. Please bump the debhelper compat at your earliest convenience /outside the freeze/! * Compat 13 is recommended (supported in stable-backports) * Compat 7 is the bare minimum PLEASE KEEP IN MIND THAT the release team *DOES NOT* accept uploads with compat bumps during the freeze. If there is any risk that the fix for this bug might not migrate to testing before 2021-01-01[3] then please postpone the fix until after the freeze. At the time of filing this bug, compat 5 and 6 are expected to be removed "some time during the development cycle of bookworm". Thanks, ~Niels [1] https://lists.debian.org/debian-devel/2020/07/msg00065.html [2] https://release.debian.org/bullseye/FAQ.html [3] The choice of 2021-01-01 as a "deadline" is set before the actual freeze deadline to provide a safe cut off point for most people. Mind you, it is still your responsibility to ensure that the upload makes it into testing even if you upload before that date. --- End Message --- --- Begin Message --- Source: gnome-icon-theme-yasis Source-Version: 0.4.2-1.2 Done: Guilherme de Paula Xavier Segundo We believe that the bug you reported is fixed in the latest version of gnome-icon-theme-yasis, 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 965...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Guilherme de Paula Xavier Segundo (supplier of updated gnome-icon-theme-yasis 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, 30 Mar 2022 17:09:43 -0300 Source: gnome-icon-theme-yasis Architecture: source Version: 0.4.2-1.2 Distribution: unstable Urgency: medium Maintainer: Free Ekanayaka Changed-By: Guilherme de Paula Xavier Segundo Closes: 965560 Changes: gnome-icon-theme-yasis (0.4.2-1.2) unstable; urgency=medium . * Non-maintainer upload. * Using new DH level format. Consequently: - debian/compat: removed. - debian/control: changed from 'debhelper' to 'debhelper-compat' in Build-Depends field and bumped level to 13. - Closes: #965560 * Dropped CDBS in favor of the debhelper to allow the build system to use DH level greater than 11. Consequently: - debian/control: removed no longer needed cdbs from Build-Depends field. - debian/rules: changed from CBDS to DH. Checksums-Sha1: 94c9be395cd9f0b9b1012e5030cef98b46a31d62 1780 gnome-icon-theme-yasis_0.4.2-1.2.dsc bdebfa0d9c9d6e8b51f92f50dbb2135341b587ff 1530 gnome-icon-theme-yasis_0.4.2-1.2.diff.gz 8ddfff57208e66c31f4b89bdad3b2bf50f87ab0b 5694 gnome-icon-theme-yasis_0.4.2-1.2_source.buildinfo Checksums-Sha256: 4b970d40f04e3fce2ac9e7435ceaf3df8d74947428329b69503026acf14b73b5 1780 gnome-icon-theme-yasis_0.4.2-1.2.dsc 77c6bd106ac5ee108fc6a4df0ebc517d08aff81bd78eeb91745c460424855ef2 1530 gnome-icon-theme-yasis_0.4.2-1.2.diff.gz f1f5c9765ac4e5c548d3f722dbf3d7a6728fab6fc5be00a448b6faac8116cffd 5694 gnome-icon-theme-yasis_0.4.2-1.2_source.buildinfo Files: 738da554f6abe39eaa1de5f9b09dc6ee 1780 gnome optional gnome-icon-theme-yasis_0.4.2-1.2.dsc 4f7cfa373e5a11eed4e404ab816322d5 1530 gnome optional gnome-icon-theme-yasis_0.4.2-1.2.diff.gz c03088e8f03bbdbf8e5ec661be9a18ca 5694 gnome optional gnome-icon-theme-yasis_0.4.2-1.2_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEENX3LDuyVoBrrofDS3mO5xwTr6e8FAmJE5C0ACgkQ3mO5xwTr 6e+xmhAAm2NaGHkPXydbVtCMcA5AMtT4ECE8hm+wgjwmAAHASo1qvPYvfriUv/2t
Bug#1008847: marked as done (rust-atk-sys)
Your message dated Sat, 9 Apr 2022 23:46:27 +0100
with message-id
and subject line Re: rust-atk-sys (autopkgtest failure with new atk)
has caused the Debian Bug report #1008847,
regarding rust-atk-sys
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.)
--
1008847: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1008847
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: rust-atk-sys
Version: 0.7.0-1
Severity: serious
Tags: upstream patch
Justification: Prevents atk1.0 migration
Control: fixed-upstream -1
Hello,
rust-atk-sys was hardcoding the value of ATK_STATE_LAST_DEFINED,
and thus its autopkgtest fails with the newer atk1.0 package
version 2.38, which introduces ATK_STATE_COLLAPSED thus bumping
ATK_STATE_LAST_DEFINED. Upstream actually stopped hardcoding the value
in 22f00076493c040b5b20d434bd0348d047027f61
Until that newer upstream version gets packaged, could you please apply
the attached patch to update ATK_STATE_LAST_DEFINED so atk1.0 version
2.38 can migrate to testing?
Samuel
-- System Information:
Debian Release: bookworm/sid
APT prefers testing
APT policy: (990, 'testing'), (500, 'unstable-debug'), (500,
'testing-debug'), (500, 'stable-security'), (500, 'stable-debug'), (500,
'proposed-updates-debug'), (500, 'proposed-updates'), (500,
'oldstable-proposed-updates-debug'), (500, 'oldstable-proposed-updates'), (500,
'oldoldstable'), (500, 'buildd-unstable'), (500, 'unstable'), (500, 'stable'),
(500, 'oldstable'), (1, 'experimental-debug'), (1, 'buildd-experimental'), (1,
'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386, arm64
Kernel: Linux 5.17.0 (SMP w/8 CPU threads; PREEMPT)
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
--
Samuel
---
Pour une évaluation indépendante, transparente et rigoureuse !
Je soutiens la Commission d'Évaluation de l'Inria.
--- a/src/lib.rs
+++ b/src/lib.rs
@@ -255,7 +255,8 @@ pub const ATK_STATE_CHECKABLE: AtkStateT
pub const ATK_STATE_HAS_POPUP: AtkStateType = 40;
pub const ATK_STATE_HAS_TOOLTIP: AtkStateType = 41;
pub const ATK_STATE_READ_ONLY: AtkStateType = 42;
-pub const ATK_STATE_LAST_DEFINED: AtkStateType = 43;
+pub const ATK_STATE_COLLAPSED: AtkStateType = 43;
+pub const ATK_STATE_LAST_DEFINED: AtkStateType = 44;
pub type AtkTextAttribute = c_int;
pub const ATK_TEXT_ATTR_INVALID: AtkTextAttribute = 0;
--- a/tests/abi.rs
+++ b/tests/abi.rs
@@ -829,6 +829,7 @@ const RUST_CONSTANTS: &[(, )] =
("(gint) ATK_STATE_BUSY", "3"),
("(gint) ATK_STATE_CHECKABLE", "39"),
("(gint) ATK_STATE_CHECKED", "4"),
+("(gint) ATK_STATE_COLLAPSED", "43"),
("(gint) ATK_STATE_DEFAULT", "36"),
("(gint) ATK_STATE_DEFUNCT", "5"),
("(gint) ATK_STATE_EDITABLE", "6"),
@@ -844,7 +845,7 @@ const RUST_CONSTANTS: &[(, )] =
("(gint) ATK_STATE_INDETERMINATE", "30"),
("(gint) ATK_STATE_INVALID", "0"),
("(gint) ATK_STATE_INVALID_ENTRY", "33"),
-("(gint) ATK_STATE_LAST_DEFINED", "43"),
+("(gint) ATK_STATE_LAST_DEFINED", "44"),
("(gint) ATK_STATE_MANAGES_DESCENDANTS", "29"),
("(gint) ATK_STATE_MODAL", "14"),
("(gint) ATK_STATE_MULTISELECTABLE", "16"),
--- a/tests/constant.c
+++ b/tests/constant.c
@@ -203,6 +203,7 @@ int main() {
PRINT_CONSTANT((gint) ATK_STATE_BUSY);
PRINT_CONSTANT((gint) ATK_STATE_CHECKABLE);
PRINT_CONSTANT((gint) ATK_STATE_CHECKED);
+PRINT_CONSTANT((gint) ATK_STATE_COLLAPSED);
PRINT_CONSTANT((gint) ATK_STATE_DEFAULT);
PRINT_CONSTANT((gint) ATK_STATE_DEFUNCT);
PRINT_CONSTANT((gint) ATK_STATE_EDITABLE);
--- End Message ---
--- Begin Message ---
Version: 0.14.0-2
Done, forgot to close the bug in the changelog.
On 03/04/2022 19:43, Samuel Thibault wrote:
Peter Michael Green, le dim. 03 avril 2022 19:29:46 +0100, a ecrit:
I'm more inclined towards simply ignoring this failure,
I'm fine with that as well, since your proposed changed is aligned with
upstream just dropping the value in 22f00076493c.
Thanks!
Samuel--- End Message ---
Processed: Bug#1009168: gzip: CVE-2022-1271: zgrep: arbitrary-file-write vulnerability
Processing commands for cont...@bugs.debian.org: > tags 1009168 + pending Bug #1009168 [src:gzip] gzip: CVE-2022-1271: zgrep: arbitrary-file-write vulnerability Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 1009168: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1009168 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1006949: src:ldc: fails to migrate to testing for too long: FTBFS on armhf and i386
Hi Matthias, On 09-04-2022 18:36, Matthias Klumpp wrote: Unfortunately I really can't do any deeper investigation into this right now :-/ Thanks for the reply. It a least makes clear where this bug stands. Paul OpenPGP_signature Description: OpenPGP digital signature
Bug#997240: marked as done (lives: FTBFS: htmsocket.c:41:10: fatal error: rpc/rpc.h: No such file or directory)
Your message dated Sat, 09 Apr 2022 16:49:13 +
with message-id
and subject line Bug#997240: fixed in lives 3.0.2-1.2
has caused the Debian Bug report #997240,
regarding lives: FTBFS: htmsocket.c:41:10: fatal error: rpc/rpc.h: No such file
or directory
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.)
--
997240: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997240
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: lives
Version: 3.0.2-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):
> gcc -DPACKAGE_NAME=\"LiVES\" -DPACKAGE_TARNAME=\"lives\"
> -DPACKAGE_VERSION=\"3.0.2\" -DPACKAGE_STRING=\"LiVES\ 3.0.2\"
> -DPACKAGE_BUGREPORT=\"https://github.com/salsaman/LiVES/issues\;
> -DPACKAGE_URL=\"http://lives-video.com\; -DPACKAGE=\"lives\"
> -DVERSION=\"3.0.2\" -DHAVE_STDIO_H=1 -DHAVE_STDLIB_H=1 -DHAVE_STRING_H=1
> -DHAVE_INTTYPES_H=1 -DHAVE_STDINT_H=1 -DHAVE_STRINGS_H=1 -DHAVE_SYS_STAT_H=1
> -DHAVE_SYS_TYPES_H=1 -DHAVE_UNISTD_H=1 -DHAVE_WCHAR_H=1 -DHAVE_SYS_PARAM_H=1
> -DSTDC_HEADERS=1 -D_ALL_SOURCE=1 -D_DARWIN_C_SOURCE=1 -D_GNU_SOURCE=1
> -D_HPUX_ALT_XOPEN_SOCKET_API=1 -D_NETBSD_SOURCE=1 -D_OPENBSD_SOURCE=1
> -D_POSIX_PTHREAD_SEMANTICS=1 -D__STDC_WANT_IEC_60559_ATTRIBS_EXT__=1
> -D__STDC_WANT_IEC_60559_BFP_EXT__=1 -D__STDC_WANT_IEC_60559_DFP_EXT__=1
> -D__STDC_WANT_IEC_60559_FUNCS_EXT__=1 -D__STDC_WANT_IEC_60559_TYPES_EXT__=1
> -D__STDC_WANT_LIB_EXT2__=1 -D__STDC_WANT_MATH_SPEC_FUNCS__=1
> -D_TANDEM_SOURCE=1 -D__EXTENSIONS__=1 -DHAVE_DLFCN_H=1 -DLT_OBJDIR=\".libs/\"
> -DHAVE_PTHREAD_PRIO_INHERIT=1 -DHAVE_PTHREAD=1 -DGETTEXT_PACKAGE=\"lives\"
> -DLOCALEDIR=\"\$\{datarootdir\}/locale\" -DPREFIX=\"/usr\"
> -DLiVES_VERSION=\"3.0.2\" -DHAVE_VISIBILITY=1 -DHAVE_STDINT_H_WITH_UINTMAX=1
> -DHAVE_ALLOCA_H=1 -DHAVE_ALLOCA=1 -DHAVE_GETPAGESIZE=1 -DHAVE_MMAP=1
> -DINTDIV0_RAISES_SIGFPE=1 -DHAVE_INTTYPES_H_WITH_UINTMAX=1
> -DHAVE_UNSIGNED_LONG_LONG_INT=1 -DHAVE_UINTMAX_T=1 -DHAVE_INTTYPES_H=1
> -DUSE_POSIX_THREADS=1 -DUSE_POSIX_THREADS_WEAK=1 -DHAVE_PTHREAD_RWLOCK=1
> -DHAVE_PTHREAD_MUTEX_RECURSIVE=1 -DHAVE_BUILTIN_EXPECT=1 -DHAVE_ARGZ_H=1
> -DHAVE_INTTYPES_H=1 -DHAVE_LIMITS_H=1 -DHAVE_UNISTD_H=1 -DHAVE_SYS_PARAM_H=1
> -DHAVE_GETCWD=1 -DHAVE_GETEGID=1 -DHAVE_GETEUID=1 -DHAVE_GETGID=1
> -DHAVE_GETUID=1 -DHAVE_MEMPCPY=1 -DHAVE_MUNMAP=1 -DHAVE_STPCPY=1
> -DHAVE_STRCASECMP=1 -DHAVE_STRDUP=1 -DHAVE_STRTOUL=1 -DHAVE_TSEARCH=1
> -DHAVE_ARGZ_COUNT=1 -DHAVE_ARGZ_STRINGIFY=1 -DHAVE_ARGZ_NEXT=1
> -DHAVE___FSETLOCKING=1 -DHAVE_DECL_FEOF_UNLOCKED=1
> -DHAVE_DECL_FGETS_UNLOCKED=1 -DHAVE_ICONV=1 -DICONV_CONST=
> -DHAVE_NL_LOCALE_NAME=1 -DHAVE_LONG_LONG_INT=1 -DHAVE_WCHAR_T=1
> -DHAVE_WINT_T=1 -DHAVE_INTMAX_T=1 -DHAVE_POSIX_PRINTF=1 -DHAVE_STDINT_H=1
> -DHAVE_STDINT_H=1 -DHAVE_STDDEF_H=1 -DHAVE_STDLIB_H=1 -DHAVE_STRING_H=1
> -DHAVE_ASPRINTF=1 -DHAVE_FWPRINTF=1 -DHAVE_PUTENV=1 -DHAVE_SETENV=1
> -DHAVE_SETLOCALE=1 -DHAVE_SNPRINTF=1 -DHAVE_WCSLEN=1 -DHAVE_DECL__SNPRINTF=0
> -DHAVE_DECL__SNWPRINTF=0 -DHAVE_DECL_GETC_UNLOCKED=1
> -DHAVE_LANGINFO_CODESET=1 -DHAVE_LC_MESSAGES=1 -DENABLE_NLS=1
> -DHAVE_GETTEXT=1 -DHAVE_DCGETTEXT=1 -DHAVE_LIBDL=1 -DHAVE_POSIX_MEMALIGN=1
> -DHAVE_POSIX_FADVISE=1 -DHAVE_POSIX_FALLOCATE=1 -DHAVE_SYS_PRCTL_H=1
> -DHAVE_LINUX_JOYSTICK_H=1 -DHAVE_JACK_JACK_H=1 -DHAVE_JACK_TRANSPORT_H=1
> -DHAVE_LINUX_VIDEODEV2_H=1 -DHAVE_FREI0R_H=1 -DHAVE_LIBRAW1394_RAW1394_H=1
> -DHAVE_LIBAVC1394_AVC1394_H=1 -DHAVE_LIBAVC1394_ROM1394_H=1 -I. -Wdate-time
> -D_FORTIFY_SOURCE=2 -I.. -g -O2 -ffile-prefix-map=/<>=.
> -fstack-protector-strong -Wformat -Werror=format-security -fcommon -Wall -c
> -o sendOSC-sendOSC.o `test -f 'sendOSC.c' || echo './'`sendOSC.c
> htmsocket.c:41:10: fatal error: rpc/rpc.h: No such file or directory
>41 | #include
> | ^~~
> compilation terminated.
> make[3]: *** [Makefile:605: sendOSC-htmsocket.o] Error 1
The full build log is available from:
http://qa-logs.debian.net/2021/10/23/lives_3.0.2-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
Bug#1006949: src:ldc: fails to migrate to testing for too long: FTBFS on armhf and i386
Hi Paul! Am Sa., 9. Apr. 2022 um 17:30 Uhr schrieb Paul Gevers : > > Hi, > > On Tue, 8 Mar 2022 21:00:25 +0100 Paul Gevers wrote: > > Your package fails to build from > > source on armhf and i386 while it successfully built there before. > > > 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. > > ldc is a key package so will not be autoremoved. Is there any progress > on fixing this issue? I am currently really tid up with other stuff, so I do not have much time (or actually, any...) to work on Debian's D toolchain, so help is absolutely wanted here! However, I hope that this particular issue will just solve itself with the next LDC release which I'd submit as soon as it is available - at least this bug report makes me think that LDC 1.29.x will resolve the issue: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1000919 That new version should actually happen rather soon, so maybe it's okay to just wait a bit. Unfortunately I really can't do any deeper investigation into this right now :-/ Cheers, Matthias -- I welcome VSRE emails. See http://vsre.info/
Bug#1009243: libapache2-mod-python: (autopkgtest) needs update for python3.10
Source: libapache2-mod-python Version: 3.5.0-1 Severity: serious Tags: sid bookworm User: debian...@lists.debian.org Usertags: needs-update User: debian-pyt...@lists.debian.org Usertags: python3.10 Control: affects -1 src:python3-defaults Dear maintainer(s), We are in the transition of making python3.10 the default Python versions [0]. With a recent upload of python3-defaults the autopkgtest of libapache2-mod-python fails in testing when that autopkgtest is run with the binary packages of python3-defaults from unstable. It passes when run with only packages from testing. In tabular form: passfail python3-defaults from testing3.10.4-1 libapache2-mod-python from testing3.5.0-1 all others from testingfrom testing I copied some of the output at the bottom of this report. I note that your package was rebuild for this transition, the failure happens with the binNMU'ed binary and the autopkgtest fails in unstable too. Currently this regression is blocking the migration of python3-defaults to testing [1]. https://docs.python.org/3/whatsnew/3.10.html lists what's new in Python3.10, it may help to identify what needs to be updated. More information about this bug and the reason for filing it can be found on https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation Paul [0] https://bugs.debian.org/1006836 [1] https://qa.debian.org/excuses.php?package=python3-defaults https://ci.debian.net/data/autopkgtest/testing/amd64/liba/libapache2-mod-python/20691134/log.gz Module python already enabled autopkgtest [13:09:55]: test smoke OpenPGP_signature Description: OpenPGP digital signature
Processed: libapache2-mod-python: (autopkgtest) needs update for python3.10
Processing control commands: > affects -1 src:python3-defaults Bug #1009243 [src:libapache2-mod-python] libapache2-mod-python: (autopkgtest) needs update for python3.10 Added indication that 1009243 affects src:python3-defaults -- 1009243: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1009243 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1009242: zfs-dkms: PPC get_user workaround breaks boot on ZFS root
Package: zfs-dkms
Version: 2.1.2-1~bpo11+1
Severity: critical
Tags: patch
Justification: breaks the whole system
X-Debbugs-Cc: nwfila...@gmail.com
Dear Maintainer,
Presently (and since 16 Nov 2021), the Debian ZFS repo has been carrying Colin
Ian King's
https://salsa.debian.org/zfsonlinux-team/zfs/-/blob/master/debian/patches/4900-ppc-get-user-workaround.patch
to work around a build failure on PPC machines whose kernels post-date
7613f5a66becfd0e43a0f34de8518695888f5458 ("powerpc/64s/kuap: Use
mmu_has_feature()"). 5.13 is the first release to contain that patch
(amusingly, someone noticed pretty quickly: https://lwn.net/Articles/856312/).
Unfortunately, while this does fix the compilation error, in a rather
heavy-handed way, it results in the system hanging at boot, well before reaching
the multi-user target. The EFAULT returned to userspace simply triggers a
retry, and so we spin. As I am on a Debian kernel after 5.13, I am unable to
upgrade my ZFS pacakges and keep a working system without rolling back to an
older kernel, which I cannot readily do, due to another bug in pre-5.15 PPC
kernel packages: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=990279 .
I reached out to the original author of mmu_feature_keys, and he has agreed to
change the EXPORT_SYMBOL status of this symbol. His one-line patch to do so,
https://patchwork.ozlabs.org/project/linuxppc-dev/patch/20220329085709.4132729-1-haoke...@gmail.com/
has yet to be picked up by
https://git.kernel.org/pub/scm/linux/kernel/git/powerpc/linux.git/ , but, I
think, could be safely included in Debian's kernel patch set until it does.
Can I ask that the ZFS and linux package maintainers coordinate picking up Kevin
Hao's patch into the kernel package and dropping Colin Ian King's workaround
from the ZFS package?
I do not know if I should also raise a bug against the linux package; please
advise.
-- System Information:
Debian Release: 11.3
APT prefers stable-updates
APT policy: (991, 'stable-updates'), (990, 'stable'), (500,
'unstable-debug'), (500, 'stable-security'), (500, 'stable-debug'), (500,
'proposed-updates-debug'), (300, 'unstable')
Architecture: ppc64el (ppc64le)
Kernel: Linux 5.15.0-0.bpo.2-powerpc64le (SMP w/176 CPU threads)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE,
TAINT_UNSIGNED_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages zfs-dkms depends on:
ii debconf [debconf-2.0] 1.5.77
ii dkms 2.8.4-3
ii file 1:5.39-3
ii libc6-dev [libc-dev] 2.31-13+deb11u3
ii libpython3-stdlib 3.9.2-3
ii lsb-release11.1.0
ii perl 5.32.1-4+deb11u2
ii python3-distutils 3.9.2-1
Versions of packages zfs-dkms recommends:
ii linux-libc-dev 5.16.12-1~bpo11+1
ii zfs-zed 2.1.2-1~bpo11+1
ii zfsutils-linux 2.1.2-1~bpo11+1
Versions of packages zfs-dkms suggests:
ii debhelper 13.3.4
-- debconf information:
zfs-dkms/stop-build-for-unknown-kernel: true
* zfs-dkms/note-incompatible-licenses:
zfs-dkms/stop-build-for-32bit-kernel: true
Bug#1009241: sagemath: autokgtest regression on armhf
Source: sagemath Version: 9.5-2 Severity: serious X-Debbugs-Cc: sramac...@debian.org sagemath's autopkgtests fail on armhf: sage -t --random-seed=151195303580024212553030459496405458934 sage/src/sage/algebras/affine_nil_temperley_lieb.py # 1 doctest failed sage -t --random-seed=151195303580024212553030459496405458934 sage/src/sage/algebras/cellular_basis.py # 1 doctest failed sage -t --random-seed=151195303580024212553030459496405458934 sage/src/sage/algebras/orlik_solomon.py # Killed due to segmentation fault sage -t --random-seed=151195303580024212553030459496405458934 sage/src/sage/categories/bialgebras_with_basis.py # Killed due to segmentation fault sage -t --random-seed=151195303580024212553030459496405458934 sage/src/sage/combinat/cluster_algebra_quiver/interact.py # 1 doctest failed sage -t --random-seed=151195303580024212553030459496405458934 sage/src/sage/combinat/cluster_algebra_quiver/cluster_seed.py # 1 doctest failed sage -t --random-seed=151195303580024212553030459496405458934 sage/src/sage/combinat/cluster_algebra_quiver/quiver.py # 1 doctest failed sage -t --random-seed=151195303580024212553030459496405458934 sage/src/sage/categories/finite_dimensional_modules_with_basis.py # Timed out sage -t --random-seed=151195303580024212553030459496405458934 sage/src/sage/categories/super_hopf_algebras_with_basis.py # Timed out sage -t --random-seed=151195303580024212553030459496405458934 sage/src/sage/coding/databases.py # Timed out sage -t --random-seed=151195303580024212553030459496405458934 sage/src/sage/coding/linear_code.py # Timed out sage -t --random-seed=151195303580024212553030459496405458934 sage/src/sage/combinat/sf/sfa.py # Killed due to segmentation fault sage -t --random-seed=151195303580024212553030459496405458934 sage/src/sage/combinat/designs/bibd.py # Timed out sage -t --random-seed=151195303580024212553030459496405458934 sage/src/sage/combinat/designs/orthogonal_arrays_find_recursive.pyx # Timed out sage -t --random-seed=151195303580024212553030459496405458934 sage/src/sage/dynamics/complex_dynamics/mandel_julia.py # 3 doctests failed sage -t --random-seed=151195303580024212553030459496405458934 sage/src/sage/functions/min_max.py # 2 doctests failed sage -t --random-seed=151195303580024212553030459496405458934 sage/src/sage/combinat/matrices/latin.py # Timed out sage -t --random-seed=151195303580024212553030459496405458934 sage/src/sage/graphs/generators/families.py # 1 doctest failed sage -t --random-seed=151195303580024212553030459496405458934 sage/src/sage/groups/perm_gps/permgroup.py # Timed out sage -t --random-seed=151195303580024212553030459496405458934 sage/src/sage/dynamics/arithmetic_dynamics/projective_ds.py # Timed out sage -t --random-seed=151195303580024212553030459496405458934 sage/src/sage/interacts/test_jupyter.rst # 19 doctests failed sage -t --random-seed=151195303580024212553030459496405458934 sage/src/sage/interfaces/gap.py # 1 doctest failed sage -t --random-seed=151195303580024212553030459496405458934 sage/src/sage/graphs/base/static_sparse_graph.pyx # Timed out sage -t --random-seed=151195303580024212553030459496405458934 sage/src/sage/graphs/generic_graph.py # Timed out sage -t --random-seed=151195303580024212553030459496405458934 sage/src/sage/groups/abelian_gps/abelian_group.py # Timed out sage -t --random-seed=151195303580024212553030459496405458934 sage/src/sage/groups/class_function.py # Timed out sage -t --random-seed=151195303580024212553030459496405458934 sage/src/sage/interfaces/tests.py # 1 doctest failed sage -t --random-seed=151195303580024212553030459496405458934 sage/src/sage/groups/finitely_presented_named.py # Timed out sage -t --random-seed=151195303580024212553030459496405458934 sage/src/sage/groups/fqf_orthogonal.py # Timed out sage -t --random-seed=151195303580024212553030459496405458934 sage/src/sage/libs/singular/function.pyx # 1 doctest failed sage -t --random-seed=151195303580024212553030459496405458934 sage/src/sage/libs/singular/singular.pyx # 1 doctest failed sage -t --random-seed=151195303580024212553030459496405458934 sage/src/sage/interfaces/singular.py # Timed out sage -t --random-seed=151195303580024212553030459496405458934 sage/src/sage/lfunctions/pari.py # Timed out sage -t --random-seed=151195303580024212553030459496405458934 sage/src/sage/misc/compat.py # 1 doctest failed sage -t --random-seed=151195303580024212553030459496405458934 sage/src/sage/misc/html.py # 3 doctests failed sage -t --random-seed=151195303580024212553030459496405458934 sage/src/sage/misc/weak_dict.pyx # 11 doctests failed sage -t --random-seed=151195303580024212553030459496405458934 sage/src/sage/modular/modform/hecke_operator_on_qexp.py # Killed due to segmentation fault sage -t --random-seed=151195303580024212553030459496405458934 sage/src/sage/modules/free_quadratic_module_integer_symmetric.py # 1 doctest failed sage -t
Bug#1000980: marked as done (kubernetes: Please upgrade to golang-1.17)
Your message dated Sat, 09 Apr 2022 15:49:20 + with message-id and subject line Bug#1000980: fixed in kubernetes 1.20.5+really1.20.2-1.1 has caused the Debian Bug report #1000980, regarding kubernetes: Please upgrade to golang-1.17 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.) -- 1000980: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1000980 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: kubernetes Version: 1.20.5+really1.20.2-1 Severity: important X-Debbugs-Cc: z...@debian.org Control: block 998747 by -1 Dear Maintainer, As part of the effort to limit the number of Go compiler in the archive, please upgrade to golang-1.17. --- End Message --- --- Begin Message --- Source: kubernetes Source-Version: 1.20.5+really1.20.2-1.1 Done: Florian Ernst We believe that the bug you reported is fixed in the latest version of kubernetes, 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. Florian Ernst (supplier of updated kubernetes 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, 02 Apr 2022 16:49:13 +0200 Source: kubernetes Architecture: source Version: 1.20.5+really1.20.2-1.1 Distribution: unstable Urgency: medium Maintainer: Janos Lenart Changed-By: Florian Ernst Closes: 1000980 Changes: kubernetes (1.20.5+really1.20.2-1.1) unstable; urgency=medium . * Non-maintainer upload. * Build using golang-go (Closes: #1000980) Checksums-Sha1: 34d11af3560f16585e16d0559a1f25e0806a1511 1941 kubernetes_1.20.5+really1.20.2-1.1.dsc a67c5ecdac0f3b88288a9ea7d8216b1d13e3f9c4 17180 kubernetes_1.20.5+really1.20.2-1.1.debian.tar.xz 4a37967fc42f3008b74531a402d836bd3245ef55 6353 kubernetes_1.20.5+really1.20.2-1.1_amd64.buildinfo Checksums-Sha256: a10e76223228821f8736832170cf9a6ef6b1ee5642d8f886169771918fe2623e 1941 kubernetes_1.20.5+really1.20.2-1.1.dsc b1bc8453b43fe2c0ef615647808092cc35f62f1ee86def5a7a7315af33e45472 17180 kubernetes_1.20.5+really1.20.2-1.1.debian.tar.xz b147fe96f30a063faf5a5f5291d53fba615fb151d2ad3d6a6e2cb01ea7c87aa0 6353 kubernetes_1.20.5+really1.20.2-1.1_amd64.buildinfo Files: f76835d200e54277a900c989b0de3e74 1941 admin optional kubernetes_1.20.5+really1.20.2-1.1.dsc ddacc7f0b3a82311d3536fda1e244a13 17180 admin optional kubernetes_1.20.5+really1.20.2-1.1.debian.tar.xz 4b844eed044815046c9e8d570b50d7e0 6353 admin optional kubernetes_1.20.5+really1.20.2-1.1_amd64.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEBn03XtJwVyplJ26xBjdBuvXdHs4FAmJIZXIACgkQBjdBuvXd Hs6msQ//VhhgKeuocG2J8+AtMHUsPRNGGbSjd2cOAR8ScJPTllOsfKceaIRUVwA8 a928+a9QSdR2U1GJQz7dWi79vwQ5Brd5LAvbQ7g+EWHON87rG/XeoIlE8Um2m85L lRLKvSOi8DP+pqcksDgzBoL/Az/2VBOPOiCHNg/JDamai0kqeBhmTBy80a6WMx6V Iy/rMJF17boEzrnV/K45Bwf4dMAQjBUYf5jtcJ75s2WikoedEKXs38KLShWvBlDG cU6jblw49wNlPkmLsOJrkL9fKG8ThQ5fkpAZiE2zC9iJapHXRlNb2L12E3bcquAb 9I0QVOizzFYcPYS0b/1RSS9L7VtHmr0T0KQGiMN0yDKzwjWgMhOdVcBmipM1Pdaa a0Il+mtyx9MXccfj407knsr73RQ5U2usA7YuIbcbyFBng3jzfkGiFP8i1xgmlNul 7t692iGKpCH/zU+L7qaNBgGdiFCuXBp4dNFelztod7ueksAgCMvRtZnDHKdHPix4 au66x8S+axaG3PhFXWJUdubfVX1lFjLsO77E2OEcWyzSZmHuOinYNWYjMdHddIxs agoFE1rDfa5IsNj1/aKEDgzULnhZZ4BdsEHBthq1LJEteJuMTZKRNhQrqnWHpmHH xfMjXyTIVj1+VrOLeS5x2hWFS9NulYxe6G+vufRNeLA8jSg3IPA= =8K0h -END PGP SIGNATURE End Message ---
Processed: Re: Bug#1009111: python-cobra: (autopkgtest) needs update for python3.10: module 'collections' has no attribute 'Iterable'
Processing control commands: > reassign -1 src:optlang Bug #1009111 [src:python-cobra] python-cobra: (autopkgtest) needs update for python3.10: module 'collections' has no attribute 'Iterable' Bug reassigned from package 'src:python-cobra' to 'src:optlang'. No longer marked as found in versions python-cobra/0.23.0-1. Ignoring request to alter fixed versions of bug #1009111 to the same values previously set > found -1 1.4.4-2 Bug #1009111 [src:optlang] python-cobra: (autopkgtest) needs update for python3.10: module 'collections' has no attribute 'Iterable' Marked as found in versions optlang/1.4.4-2. > fixed -1 1.5.2-1 Bug #1009111 [src:optlang] python-cobra: (autopkgtest) needs update for python3.10: module 'collections' has no attribute 'Iterable' Marked as fixed in versions optlang/1.5.2-1. -- 1009111: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1009111 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1003643: src:lintian: fails to migrate to testing for too long: unresolved RC bug
Hi, On Thu, 13 Jan 2022 08:47:40 +0100 Paul Gevers wrote: 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:lintian has been trying to migrate for 61 days [2]. Hence, I am filing this bug. You have an unresolved RC bug that applies to the unstable package but not to the testing package, hence blocking migration. It's been three months. Any progress on this? Paul OpenPGP_signature Description: OpenPGP digital signature
Bug#1006949: src:ldc: fails to migrate to testing for too long: FTBFS on armhf and i386
Hi, On Tue, 8 Mar 2022 21:00:25 +0100 Paul Gevers wrote: Your package fails to build from source on armhf and i386 while it successfully built there before. 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. ldc is a key package so will not be autoremoved. Is there any progress on fixing this issue? Paul OpenPGP_signature Description: OpenPGP digital signature
Bug#1008638: marked as done (ldns: FTBFS: checking for the distutils Python package... no)
Your message dated Sat, 09 Apr 2022 15:18:55 + with message-id and subject line Bug#1008638: fixed in ldns 1.7.1-2.1 has caused the Debian Bug report #1008638, regarding ldns: FTBFS: checking for the distutils Python package... no 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.) -- 1008638: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1008638 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: ldns Version: 1.7.1-2 Severity: serious Tags: ftbfs sid bookworm Justification: fails to build from source (but built successfully in the past) ldns FTBFS: checking for the distutils Python package... no configure: error: cannot import Python module "distutils". Please check your Python installation. The error was: :1: DeprecationWarning: The distutils package is deprecated and slated for removal in Python 3.12. Use setuptools or check PEP 632 for potential alternatives See https://buildd.debian.org/status/fetch.php?pkg=ldns=amd64=1.7.1-2%2Bb2=1648456911=0 Cheers -- Sebastian Ramacher --- End Message --- --- Begin Message --- Source: ldns Source-Version: 1.7.1-2.1 Done: Michael Tokarev We believe that the bug you reported is fixed in the latest version of ldns, 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 1008...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Michael Tokarev (supplier of updated ldns package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Thu, 07 Apr 2022 16:03:29 +0300 Source: ldns Architecture: source Version: 1.7.1-2.1 Distribution: unstable Urgency: medium Maintainer: Debian DNS Team Changed-By: Michael Tokarev Closes: 1008638 Changes: ldns (1.7.1-2.1) unstable; urgency=medium . * Non-maintainer upload. * add fix-wrong-python-distutils-configure-check.diff to fix the incorrect distutils package check (it should be checking the return code not the emptiness of the output). This fixes FTBFS with new python (3.10) and allows the python3.10 transition to happen, but it is not fixing the actual issiue with ldns using distutils which should be addressed later. Closes: #1008638 Checksums-Sha1: ff8c4b41dafed88873e7fd720660ab253cf0f9dd 1826 ldns_1.7.1-2.1.dsc 48f1806f6989694118ce48511c03b2df07efdcf1 13868 ldns_1.7.1-2.1.debian.tar.xz 6c649873a47581c1380b3a1b836f63dbb07c2837 7363 ldns_1.7.1-2.1_source.buildinfo Checksums-Sha256: 0b5e89d41e7363ea2b8de7d6a9093ed3350d88b588deeb5a4fdc319afa46f0b1 1826 ldns_1.7.1-2.1.dsc a2d57a83aebc9cd35f3530091eee0d24fabd88a4cdacf1502b0917dd0073 13868 ldns_1.7.1-2.1.debian.tar.xz 2a239501d03d1e33e41e03744fda1a16cf23d8a3b830d6891625cefed63782ef 7363 ldns_1.7.1-2.1_source.buildinfo Files: d22980c6505aa4a89358879ed00c044d 1826 net optional ldns_1.7.1-2.1.dsc a026867b3a47485f6002f0f8a22069f4 13868 net optional ldns_1.7.1-2.1.debian.tar.xz 2ca46ced0d1091666a908fbf0204c9a2 7363 net optional ldns_1.7.1-2.1_source.buildinfo -BEGIN PGP SIGNATURE- iQFDBAEBCAAtFiEEe3O61ovnosKJMUsicBtPaxppPlkFAmJO9FwPHG1qdEB0bHMu bXNrLnJ1AAoJEHAbT2saaT5ZY38H/20VCKiawsWxSbyqMzgzqXpVioP+E8thbGaO Mfajk3lM2ttsyoBBGuWqq+zmU6GKKOjWOLj4HVhaJaxSwJTjetxJw5WUSYrild8O OkKMtaIxvRoaBOosx6MfzdMVoxmU+xlo3iJvHISljfSLCGcSHaUi97CTnYDUd9dl CJNg0ypO/AHyfhb+vKzGqy4QYdXQgbQIdHSqTNUjDz4bEU2l/8tSg1Wig84y4GGS hxDt4IcHBG7GtqCKnZYFLbDmZ97S4TtACl1lWfWUQLkI4n2vnMOMly+6wvBuBgli S0Ws7GD8ESSrkEXqCVeE+PvM0x8RE3kSSvcDwPt5IPzGiRayy3E= =eg3c -END PGP SIGNATURE End Message ---
Bug#1009111: [Debian-med-packaging] Bug#1009111: python-cobra: (autopkgtest) needs update for python3.10: module 'collections' has no attribute 'Iterable'
Hi, On 09-04-2022 10:15, Étienne Mollier wrote: Should I just go ahead and close #1009111 without further upload? I think you can do that. Paul OpenPGP_signature Description: OpenPGP digital signature
Processed: fails already in testing
Processing commands for cont...@bugs.debian.org: > found 1004869 0.20.2-1 Bug #1004869 [src:python-xarray] python-xarray: autopkgtest regression on i386 Marked as found in versions python-xarray/0.20.2-1. > found 1004870 0.20.2-1 Bug #1004870 [src:python-xarray] python-xarray: autopkgtest regression on s390x Marked as found in versions python-xarray/0.20.2-1. > thanks Stopping processing here. Please contact me if you need assistance. -- 1004869: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1004869 1004870: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1004870 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1009240: esys-particle: autopkgtest regression since rebuild for python3.10 as default
Source: esys-particle Version: 2.3.5+dfsg2-4 Severity: serious User: debian...@lists.debian.org Usertags: regression Dear maintainer(s), We're in the transition of making python3.10 the default python3. For that reason, esys-particle was binNMUd. Since that rebuild, the autopkgtest of esys-particle fails. Worse, it doesn't end by itself but it times out after 2:47 hours. More information about this bug and the reason for filing it can be found on https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation Paul https://ci.debian.net/packages/e/esys-particle/ https://ci.debian.net/data/autopkgtest/unstable/amd64/e/esys-particle/20729937/log.gz autopkgtest [11:58:06]: test build1: [--- CSubLatticeControler::initMPI() CSubLatticeControler::initMPI() Traceback (most recent call last): File "/tmp/tmp.T1uadp7i2M/compression.py", line 1, in from esys.lsm import * ModuleNotFoundError: No module named 'esys' autopkgtest [14:44:47]: ERROR: timed out on command "su -s /bin/bash debci -c set -e; export USER=`id -nu`; . /etc/profile >/dev/null 2>&1 || true; . ~/.profile >/dev/null 2>&1 || true; buildtree="/tmp/autopkgtest-lxc.fkyhw166/downtmp/build.30O/src"; mkdir -p -m 1777 -- "/tmp/autopkgtest-lxc.fkyhw166/downtmp/build1-artifacts"; export AUTOPKGTEST_ARTIFACTS="/tmp/autopkgtest-lxc.fkyhw166/downtmp/build1-artifacts"; export ADT_ARTIFACTS="$AUTOPKGTEST_ARTIFACTS"; mkdir -p -m 755 "/tmp/autopkgtest-lxc.fkyhw166/downtmp/autopkgtest_tmp"; export AUTOPKGTEST_TMP="/tmp/autopkgtest-lxc.fkyhw166/downtmp/autopkgtest_tmp"; export ADTTMP="$AUTOPKGTEST_TMP"; export DEBIAN_FRONTEND=noninteractive; export LANG=C.UTF-8; export DEB_BUILD_OPTIONS=parallel=2; unset LANGUAGE LC_CTYPE LC_NUMERIC LC_TIME LC_COLLATE LC_MONETARY LC_MESSAGES LC_PAPER LC_NAME LC_ADDRESS LC_TELEPHONE LC_MEASUREMENT LC_IDENTIFICATION LC_ALL;rm -f /tmp/autopkgtest_script_pid; set -C; echo $$ > /tmp/autopkgtest_script_pid; set +C; trap "rm -f /tmp/autopkgtest_script_pid" EXIT INT QUIT PIPE; cd "$buildtree"; chmod +x /tmp/autopkgtest-lxc.fkyhw166/downtmp/build.30O/src/debian/tests/build1; touch /tmp/autopkgtest-lxc.fkyhw166/downtmp/build1-stdout /tmp/autopkgtest-lxc.fkyhw166/downtmp/build1-stderr; /tmp/autopkgtest-lxc.fkyhw166/downtmp/build.30O/src/debian/tests/build1 2> >(tee -a /tmp/autopkgtest-lxc.fkyhw166/downtmp/build1-stderr >&2) > >(tee -a /tmp/autopkgtest-lxc.fkyhw166/downtmp/build1-stdout);" (kind: test) autopkgtest [14:44:47]: test build1: ---] OpenPGP_signature Description: OpenPGP digital signature
Bug#1005424: marked as done (ldap-account-manager: FTBFS: error: unknown option '--skip-rebase')
Your message dated Sat, 09 Apr 2022 13:48:55 + with message-id and subject line Bug#1005424: fixed in ldap-account-manager 7.9-1 has caused the Debian Bug report #1005424, regarding ldap-account-manager: FTBFS: error: unknown option '--skip-rebase' 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.) -- 1005424: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1005424 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: ldap-account-manager Version: 7.7-1 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20220212 ftbfs-bookworm Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > debian/rules build > debian/minify > error: unknown option '--skip-rebase' > make: *** [debian/rules:14: build-indep] Error 1 The full build log is available from: http://qa-logs.debian.net/2022/02/12/ldap-account-manager_7.7-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: ldap-account-manager Source-Version: 7.9-1 Done: Roland Gruber We believe that the bug you reported is fixed in the latest version of ldap-account-manager, 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 1005...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Roland Gruber (supplier of updated ldap-account-manager 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, 09 Mar 2022 17:08:14 +0100 Source: ldap-account-manager Architecture: source Version: 7.9-1 Distribution: unstable Urgency: medium Maintainer: Roland Gruber Changed-By: Roland Gruber Closes: 1005424 1006232 Changes: ldap-account-manager (7.9-1) unstable; urgency=medium . * new upstream release * Fix "FTBFS: error: unknown option '--skip-rebase'" by checking if argument is supported (Closes: #1005424) * Fix "ldap-account-manager.postinst uses a2query without requiring apache2 package" by adding sanity checks (Closes: #1006232) . ldap-account-manager (7.8-1) unstable; urgency=medium . * new upstream release Checksums-Sha1: 7911b988af41bd648f34ca8f685a87fabdaf0c49 2023 ldap-account-manager_7.9-1.dsc 9904aed7d20ee02526649cc4eb04d146101cf12a 27361242 ldap-account-manager_7.9.orig.tar.bz2 1e6f95a11702ad4dfccafaf7d136cbb6ed39895e 35548 ldap-account-manager_7.9-1.debian.tar.xz ea8539ed7eaf1bca473b4fd8a8b46df5db09af50 7684 ldap-account-manager_7.9-1_amd64.buildinfo Checksums-Sha256: c275f4173668a2e9bb4c6a83b559c91c5cadf08bf4a8bf66fae9665066ea6936 2023 ldap-account-manager_7.9-1.dsc 52d1a83f5f753ddaf640e0c825c2292a470256652ccd0819d52e02df05e5c5de 27361242 ldap-account-manager_7.9.orig.tar.bz2 6ead6de59fe20559c46b2d1634464f74eb8371562ca9fb194e5ce60ec72739ec 35548 ldap-account-manager_7.9-1.debian.tar.xz 6079950f62bf86fd4dcefe7e3a3ccb1b16dbf78891bcb7acb737ecaf4b117da6 7684 ldap-account-manager_7.9-1_amd64.buildinfo Files: b31a1c1bacd894a22c7d450f7d1f9ccc 2023 web optional ldap-account-manager_7.9-1.dsc a15f5ae5e69aa33f8a9abef96ce5c1ae 27361242 web optional ldap-account-manager_7.9.orig.tar.bz2 e2f1718bf04efd4f0e2f80636c629881 35548 web optional ldap-account-manager_7.9-1.debian.tar.xz 2b0fec7fd2cf61f540f6967206d1e5ca 7684 web optional ldap-account-manager_7.9-1_amd64.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEERgUMsnxvIxsAsUimhHMGK3zwlLoFAmJRimIACgkQhHMGK3zw lLqHORAAwdunb5kY8al9QYeFArINTcOPluwkQYhklfR2u2ub8gvU+llwu/E/OPns t2CfFugOhpYHEZQyZzCknxR/qhdMLFuqkQfZvth8InVtcUZs5xeM7LFfuWJes4z9 Y2fcPPPS/KiHJ6xf/LtjrNrg2iXXs9M4zK8nS+zz8FnHGAH9EKIDNGo/g6Pd6/Xx JONQs8uEK6a1JFfSczaT5moBoMp7rx9FTnRSDDOIvdNwNMzKSVdHounlmq9hSFO5
Processed: reassign 1008501 to src:linux, reassign 1009127 to debian-installer, reassign 1009022 to imv
Processing commands for cont...@bugs.debian.org:
> reassign 1008501 src:linux 5.17~rc8-1~exp1
Bug #1008501 [linux-headers-5.17.0-rc8-common] pahole-flags.sh: inaccessible or
not found
Warning: Unknown package 'linux-headers-5.17.0-rc8-common'
Bug reassigned from package 'linux-headers-5.17.0-rc8-common' to 'src:linux'.
No longer marked as found in versions 5.16.18-1 and linux/5.17~rc8-1~exp1.
Ignoring request to alter fixed versions of bug #1008501 to the same values
previously set
Bug #1008501 [src:linux] pahole-flags.sh: inaccessible or not found
Marked as found in versions linux/5.17~rc8-1~exp1.
> reassign 1009127 debian-installer
Bug #1009127 [network install initramfs "initrd.gz".] Missing phy_gmii_sel.ko
in dists/bullseye/main/installer-armhf/current/images/netboot/netboot.tar.gz
Warning: Unknown package 'network'
Warning: Unknown package 'install'
Warning: Unknown package 'initramfs'
Warning: Unknown package '"initrd.gz".'
Bug reassigned from package 'network install initramfs "initrd.gz".' to
'debian-installer'.
Ignoring request to alter found versions of bug #1009127 to the same values
previously set
Ignoring request to alter fixed versions of bug #1009127 to the same values
previously set
> reassign 1009022 imv 4.3.0-1
Bug #1009022 [imv-wayland] imv-wayland: Segfault after updating to Sway v1.7 /
libwlroots 1.5
Warning: Unknown package 'imv-wayland'
Bug reassigned from package 'imv-wayland' to 'imv'.
No longer marked as found in versions imv.
Ignoring request to alter fixed versions of bug #1009022 to the same values
previously set
Bug #1009022 [imv] imv-wayland: Segfault after updating to Sway v1.7 /
libwlroots 1.5
Marked as found in versions imv/4.3.0-1.
> reassign 1001174 src:mutter 41.1-1
Bug #1001174 [libmutter-9-0] libmutter-9-0: Screen rotation doesn't work and
icon disappeared from top-right menu in gnome
Warning: Unknown package 'libmutter-9-0'
Bug reassigned from package 'libmutter-9-0' to 'src:mutter'.
No longer marked as found in versions mutter/41.1-1.
Ignoring request to alter fixed versions of bug #1001174 to the same values
previously set
Bug #1001174 [src:mutter] libmutter-9-0: Screen rotation doesn't work and icon
disappeared from top-right menu in gnome
Marked as found in versions mutter/41.1-1.
> tags 1009112 + experimental
Bug #1009112 [src:python-eventlet] python-eventlet: (autopkgtest) needs update
for python3.10: tests.patcher_test.test_patcher_existing_locks_locked
Added tag(s) experimental.
> tags 991566 + sid bookworm
Bug #991566 [r-cran-bookdown] r-cran-bookdown: Please package version 0.25
Added tag(s) sid and bookworm.
> found 1008982 1.21r6b-7
Bug #1008982 [src:adacontrol] adacontrol: depends on unavailable asis
Marked as found in versions adacontrol/1.21r6b-7.
> tags 1008982 + sid bookworm
Bug #1008982 [src:adacontrol] adacontrol: depends on unavailable asis
Added tag(s) bookworm and sid.
> tags 1008981 + sid bookworm
Bug #1008981 [src:libaws] libaws: depends on unavailable asis
Added tag(s) bookworm and sid.
> found 1008981 20.2-2
Bug #1008981 [src:libaws] libaws: depends on unavailable asis
Marked as found in versions libaws/20.2-2.
> tags 1008980 + sid bookworm
Bug #1008980 [adabrowse] adabrowse: depends on unavailable asis
Added tag(s) bookworm and sid.
> found 1008980 4.0.3-14
Bug #1008980 [adabrowse] adabrowse: depends on unavailable asis
Marked as found in versions adabrowse/4.0.3-14.
> tags 1008979 + sid bookworm
Bug #1008979 [src:asis] asis: depends on gnat-util, almost orphaned upstream
Added tag(s) sid and bookworm.
> found 1008979 2019-5
Bug #1008979 [src:asis] asis: depends on gnat-util, almost orphaned upstream
Marked as found in versions asis/2019-5.
> tags 1008889 + sid bookworm
Bug #1008889 [cluster-glue] FTBFS: Build-depends libltdl3-dev which is no
longer available
Added tag(s) sid and bookworm.
> notfixed 815221 3.3.2-1
Bug #815221 {Done: Christian Marillat } [qbittorrent]
qbittorrent: moves downloaded files to dir for incomplete torrents
There is no source info for the package 'qbittorrent' at version '3.3.2-1' with
architecture ''
Unable to make a source version for version '3.3.2-1'
No longer marked as fixed in versions 3.3.2-1.
> fixed 815221 3.3.4-1
Bug #815221 {Done: Christian Marillat } [qbittorrent]
qbittorrent: moves downloaded files to dir for incomplete torrents
Marked as fixed in versions qbittorrent/3.3.4-1.
> tags 965827 + experimental
Bug #965827 {Done: Boyuan Yang } [src:speex] speex: Removal
of obsolete debhelper compat 5 and 6 in bookworm
Added tag(s) experimental.
> reassign 855073 libtorrent-rasterbar9 1.1.1-1
Bug #855073 {Done: Christian Marillat } [qbittorrent]
qbittorrent: Data Loss after reboot
Bug reassigned from package 'qbittorrent' to 'libtorrent-rasterbar9'.
No longer marked as found in versions qbittorrent/3.3.7-2.
No longer marked as fixed in versions qbittorrent/1.1.4-1.
Bug #855073 {Done: Christian Marillat }
[libtorrent-rasterbar9] qbittorrent: Data Loss after reboot
Marked as found in
Bug#987360: swaylock: Occassional unlock without password entered
X-Debbugs-Cc: pe...@riseup.net Hi Pelle, You reported this issue for swaylock 1.5-2. Do you still experience same isue with swaylock 1.6-1 now in Debian unstable? Perhaps sensible to lower severity of this issue, to allow more exposure to it in Debian testing - and then hopefully close it for good soon, when work on ext-session-lock-v1 is finalized: https://github.com/swaywm/sway/pull/6879 Also, please note that you have been kindly requested to also share a stack trace: https://bugs.debian.org/987360#25 Kind regards, - Jonas -- * Jonas Smedegaard - idealist & Internet-arkitekt * Tlf.: +45 40843136 Website: http://dr.jones.dk/ [x] quote me freely [ ] ask before reusing [ ] keep private signature.asc Description: signature
Bug#999659: perdition: diff for NMU version 2.2-3.2
On Sat, Apr 02, 2022 at 01:44:41PM -0300, Marcos Talau wrote: > Control: tags 999659 + patch > Control: tags 999659 + pending > > Dear maintainer, > > I've prepared an NMU for perdition (versioned as 2.2-3.2) and > uploaded it to DELAYED/2. Please feel free to tell me if I > should delay it longer. Thanks, this is very much appreciated. Please go ahead, I see no reason to delay.
Bug#1009097: meson: (autopkgtest) needs update for python3.10: MesonVersionMismatchException.__init__() missing 1 required positional argument: 'current_version'
Hi On 09-04-2022 13:18, Jussi Pakkanen wrote: Is there now a guarantee that starting with 3.10 sysconfig points to the correct place (I don't remember the details, but it had something to do with dist-packages vs site-packages). I'm not involved in Python packaging. You'll have to ask the maintainers. Paul OpenPGP_signature Description: OpenPGP digital signature
Bug#1009097: meson: (autopkgtest) needs update for python3.10: MesonVersionMismatchException.__init__() missing 1 required positional argument: 'current_version'
On Fri, 8 Apr 2022 at 22:21, Paul Gevers wrote: > >> I copied some of the output at the bottom of this report. I noticed that > >> there is a new version of meson in unstable, it fails too, but in a > >> different way. > > > > Can you provide the logs for that? > > Traceback (most recent call last): >File "/usr/bin/meson", line 29, in > sys.exit(mesonmain.main()) > > mesonbuild.interpreterbase.exceptions.InterpreterException: Problem > encountered: Python3 purelib path seems invalid? This should be fixed by https://github.com/mesonbuild/meson/pull/10254 This is due to we having to poke distutils internals because Debian patched distutils to produce different results for install directories than sysconfig (the latter was incorrect). Is there now a guarantee that starting with 3.10 sysconfig points to the correct place (I don't remember the details, but it had something to do with dist-packages vs site-packages).
Bug#1003907: marked as done (fails to successfully associate)
Your message dated Sat, 09 Apr 2022 07:48:47 + with message-id and subject line Bug#1003907: fixed in wpa 2:2.10-8 has caused the Debian Bug report #1003907, regarding fails to successfully associate 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.) -- 1003907: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1003907 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: wpasupplicant Version: 2:2.10-1 Severity: grave Hi, during todays upgrade of wpasupplicant 2:2.9.0-23 to 2:2.10-1 my network connection was killed (I'm using NetworkManager 1.34.0) and I wasn't able to successfully connect again, even after a reboot. Only a downgrade to 2:2.9.0-23 helped. Attached is the journal log for wpasupplicant.service and a dmesg output. Marking as RC so the package doesn't migrate until this has been investigated. Regards, Michael -- System Information: Debian Release: bookworm/sid APT prefers unstable APT policy: (500, 'unstable'), (200, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.15.0-2-amd64 (SMP w/4 CPU threads) Kernel taint flags: TAINT_WARN, TAINT_FIRMWARE_WORKAROUND, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages wpasupplicant depends on: ii adduser3.118 ii libc6 2.33-2 ii libdbus-1-31.12.20-3 ii libnl-3-2003.4.0-1+b1 ii libnl-genl-3-200 3.4.0-1+b1 ii libnl-route-3-200 3.4.0-1+b1 ii libpcsclite1 1.9.5-1 ii libreadline8 8.1.2-1 ii libssl1.1 1.1.1m-1 ii lsb-base 11.1.0 wpasupplicant recommends no packages. Versions of packages wpasupplicant suggests: pn libengine-pkcs11-openssl pn wpagui -- Configuration Files: /etc/wpa_supplicant/ifupdown.sh changed [not included] -- no debconf information dmesg Description: application/json Jan 18 00:17:02 pluto systemd[1]: Starting WPA supplicant... Jan 18 00:17:03 pluto systemd[1]: Started WPA supplicant. Jan 18 00:17:03 pluto wpa_supplicant[664]: Successfully initialized wpa_supplicant Jan 18 00:17:04 pluto wpa_supplicant[664]: dbus: fill_dict_with_properties dbus_interface=fi.w1.wpa_supplicant1.Interface.P2PDevice dbus_property=P2PDeviceConfig getter failed Jan 18 00:17:07 pluto wpa_supplicant[664]: wlp3s0: WPS-CANCEL Jan 18 00:17:07 pluto wpa_supplicant[664]: wlp3s0: SME: Trying to authenticate with 38:10:d5:8f:38:e2 (SSID='myessid' freq=5620 MHz) Jan 18 00:17:08 pluto wpa_supplicant[664]: wlp3s0: SME: Trying to authenticate with 38:10:d5:8f:38:e2 (SSID='myessid' freq=5620 MHz) Jan 18 00:17:08 pluto wpa_supplicant[664]: wlp3s0: PMKSA-CACHE-ADDED 38:10:d5:8f:38:e2 0 Jan 18 00:17:08 pluto wpa_supplicant[664]: wlp3s0: Trying to associate with 38:10:d5:8f:38:e2 (SSID='myessid' freq=5620 MHz) Jan 18 00:17:08 pluto wpa_supplicant[664]: wlp3s0: CTRL-EVENT-ASSOC-REJECT bssid=38:10:d5:8f:38:e2 status_code=40 Jan 18 00:17:08 pluto wpa_supplicant[664]: wlp3s0: SME: Deauth request to the driver failed Jan 18 00:17:08 pluto wpa_supplicant[664]: BSSID 38:10:d5:8f:38:e2 ignore list count incremented to 2, ignoring for 10 seconds Jan 18 00:17:08 pluto wpa_supplicant[664]: wlp3s0: SME: Trying to authenticate with 38:10:d5:8f:38:e1 (SSID='myessid' freq=2462 MHz) Jan 18 00:17:08 pluto wpa_supplicant[664]: wlp3s0: SME: Trying to authenticate with 38:10:d5:8f:38:e1 (SSID='myessid' freq=2462 MHz) Jan 18 00:17:09 pluto wpa_supplicant[664]: wlp3s0: PMKSA-CACHE-ADDED 38:10:d5:8f:38:e1 0 Jan 18 00:17:09 pluto wpa_supplicant[664]: wlp3s0: Trying to associate with 38:10:d5:8f:38:e1 (SSID='myessid' freq=2462 MHz) Jan 18 00:17:12 pluto wpa_supplicant[664]: wlp3s0: SME: Trying to authenticate with 38:10:d5:8f:38:e2 (SSID='myessid' freq=5620 MHz) Jan 18 00:17:12 pluto wpa_supplicant[664]: wlp3s0: Trying to associate with 38:10:d5:8f:38:e2 (SSID='myessid' freq=5620 MHz) Jan 18 00:17:12 pluto wpa_supplicant[664]: wlp3s0: CTRL-EVENT-ASSOC-REJECT bssid=38:10:d5:8f:38:e2 status_code=40 Jan 18 00:17:12 pluto wpa_supplicant[664]: wlp3s0: PMKSA-CACHE-REMOVED 38:10:d5:8f:38:e2 0 Jan 18 00:17:12 pluto wpa_supplicant[664]: wlp3s0: PMKSA-CACHE-REMOVED 38:10:d5:8f:38:e1 0 Jan 18 00:17:12 pluto wpa_supplicant[664]: wlp3s0: SME: Trying to authenticate with 38:10:d5:8f:38:e2 (SSID='myessid' freq=5620 MHz) Jan 18 00:17:13 pluto wpa_supplicant[664]: wlp3s0: SME: Trying to authenticate with 38:10:d5:8f:38:e2
Processed: Re: gnome-shell-extension-sound-device-chooser: does not declare compatibility with GNOME Shell 42
Processing control commands: > tags -1 + fixed-upstream Bug #1008556 [gnome-shell-extension-sound-device-chooser] gnome-shell-extension-sound-device-chooser: does not declare compatibility with GNOME Shell 42 Added tag(s) fixed-upstream. -- 1008556: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1008556 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1008556: gnome-shell-extension-sound-device-chooser: does not declare compatibility with GNOME Shell 42
Control: tags -1 + fixed-upstream On Mon, 28 Mar 2022 16:36:23 +0100 Simon McVittie wrote: > Forwarded: > https://github.com/kgshank/gse-sound-output-device-chooser/issues/229 Upstream has now made a new release fixing this issue. Please update the Debian package to the new upstream release. -- bye, pabs https://wiki.debian.org/PaulWise signature.asc Description: This is a digitally signed message part
