Bug#942622: marked as done (src:lightyears: Maintainer email address not working)
Your message dated Sat, 07 May 2022 03:33:55 + with message-id and subject line Bug#942622: fixed in lightyears 1.5.0-1 has caused the Debian Bug report #942622, regarding src:lightyears: Maintainer email address not working 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.) -- 942622: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=942622 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:lightyears Severity: serious Justification: 3.3 Policy requires a maintainer email address that accepts mail. Mail for this maintainer has been failing for some time: This message was created automatically by mail delivery software. A message that you sent could not be delivered to one or more of its recipients. This is a permanent error. The following address(es) failed: rai...@ubuntu.com host mx.canonical.com [91.189.95.10] SMTP error from remote mail server after RCPT TO:: 550 5.1.1 : Recipient address rejected: User unknown in virtual alias table Scott K --- End Message --- --- Begin Message --- Source: lightyears Source-Version: 1.5.0-1 Done: Boyuan Yang We believe that the bug you reported is fixed in the latest version of lightyears, 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 942...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Boyuan Yang (supplier of updated lightyears package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Fri, 06 May 2022 23:08:48 -0400 Source: lightyears Architecture: source Version: 1.5.0-1 Distribution: unstable Urgency: low Maintainer: Debian Python Team , Changed-By: Boyuan Yang Closes: 820718 912488 936945 942622 1010036 Changes: lightyears (1.5.0-1) unstable; urgency=low . [ Jakub Wilk ] * Use canonical URIs for Vcs-* fields. . [ Ondřej Nový ] * d/changelog: Remove trailing whitespaces * d/control: Remove ancient X-Python-Version field * d/control: Update Vcs-* fields with new Debian Python Team Salsa layout. . [ Debian Janitor ] * Use secure URI in debian/watch. * Use secure URI in Homepage field. * Bump debhelper from deprecated 8 to 12. . [ Sandro Tosi ] * Use the new Debian Python Team contact name and address. (Closes: #942622) . [ Boyuan Yang ] * New upstream release 1.5.0. + Migrate package to python3. (Closes: #1010036, #936945) + Migrate to python3-pygame. (Closes: #912488) * debian/control: Update homepage field. (Closes: #820718) * debian/patches: Drop all old patches. + Keep font patch as 0001-Use-fonts-dejavu-core-new-path.patch. + Add debian/patches/0002-Fix-system-datadir-detection.patch to fix python3 library detection. Checksums-Sha1: 2a3dbe5e3c53f13f637ad96647e08ea83ccf3c47 2029 lightyears_1.5.0-1.dsc da18b1201d94219454168d3f710f659077acd317 25455585 lightyears_1.5.0.orig.tar.gz bedb9c5adb935d65f43e0c9813713e1317c36721 8584 lightyears_1.5.0-1.debian.tar.xz cb3a9791e0f1d98ce5a966d900a25ba35e123fd4 6338 lightyears_1.5.0-1_amd64.buildinfo Checksums-Sha256: 3db9730098184aba8649d98a8a0675c9ba72aac477fa1d8aa1d49fd1bb010bff 2029 lightyears_1.5.0-1.dsc ecd20a1e9f3c41b9728ce1b4ff91163de36d9e046fefd6bb4c1da869b00599c7 25455585 lightyears_1.5.0.orig.tar.gz b96fff2b152104a0516d748d4e3b5bf178673e5acd570778844e4d1e6b262e10 8584 lightyears_1.5.0-1.debian.tar.xz 961e5a3d7a8ee21f5ba0d9cc97eab7d2c23ba05c38bcec0a9f4bb62f64cc355e 6338 lightyears_1.5.0-1_amd64.buildinfo Files: 87d494c387678ee91baed47b9fe3481e 2029 games optional lightyears_1.5.0-1.dsc 1e698cd23bf6e016c59b984660a2d47b 25455585 games optional lightyears_1.5.0.orig.tar.gz 48b9e6dc426cb8d4eb66f3d640d9d8b8 8584 games optional lightyears_1.5.0-1.debian.tar.xz e0af827d4ce1c364bdd3310a6ac62c4d 6338 games optional lightyears_1.5.0-1_amd64.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEfncpR22H1vEdkazLwpPntGGCWs4FAmJ14u0ACgkQwpPntGGC Ws4PvA/+KHm9Sj87QqICyhDedMWEQPjUh3qvRUDGgCPtxUyFtv5wbxkQvF6tMD6W cqb8DMnh42E4UYlD3PyS6woSUFkG/jG35F+vS2xW31XupO1FrDfCm3hxQ0vIVfHG Kaoo9jhTMhnCJ6RdXV2kLwEqHWzNCJYENQ2L31LCE4bZm0osCUrwv/XKwM6oiDI5
Bug#936945: marked as done (lightyears: Python2 removal in sid/bullseye)
Your message dated Sat, 07 May 2022 03:33:55 + with message-id and subject line Bug#936945: fixed in lightyears 1.5.0-1 has caused the Debian Bug report #936945, regarding lightyears: Python2 removal in sid/bullseye 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.) -- 936945: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=936945 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:lightyears Version: 1.4-2 Severity: normal Tags: sid bullseye User: debian-pyt...@lists.debian.org Usertags: py2removal Python2 becomes end-of-live upstream, and Debian aims to remove Python2 from the distribution, as discussed in https://lists.debian.org/debian-python/2019/07/msg00080.html Your package either build-depends, depends on Python2, or uses Python2 in the autopkg tests. Please stop using Python2, and fix this issue by one of the following actions. - Convert your Package to Python3. This is the preferred option. In case you are providing a Python module foo, please consider dropping the python-foo package, and only build a python3-foo package. Please don't drop Python2 modules, which still have reverse dependencies, just document them. This is the preferred option. - If the package is dead upstream, cannot be converted or maintained in Debian, it should be removed from the distribution. If the package still has reverse dependencies, raise the severity to "serious" and document the reverse dependencies with the BTS affects command. If the package has no reverse dependencies, confirm that the package can be removed, reassign this issue to ftp.debian.org, make sure that the bug priority is set to normal and retitle the issue to "RM: PKG -- removal triggered by the Python2 removal". - If the package has still many users (popcon >= 300), or is needed to build another package which cannot be removed, document that by adding the "py2keep" user tag (not replacing the py2remove tag), using the debian-pyt...@lists.debian.org user. Also any dependencies on an unversioned python package (python, python-dev) must not be used, same with the python shebang. These have to be replaced by python2/python2.7 dependencies and shebang. This is the least preferred option. If the conversion or removal needs action on another package first, please document the blocking by using the BTS affects command, like affects + src:lightyears If there is no py2removal bug for that reverse-dependency, please file a bug on this package (similar to this bug report). If there are questions, please refer to the wiki page for the removal: https://wiki.debian.org/Python/2Removal, or ask for help on IRC #debian-python, or the debian-pyt...@lists.debian.org mailing list. --- End Message --- --- Begin Message --- Source: lightyears Source-Version: 1.5.0-1 Done: Boyuan Yang We believe that the bug you reported is fixed in the latest version of lightyears, 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 936...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Boyuan Yang (supplier of updated lightyears package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Fri, 06 May 2022 23:08:48 -0400 Source: lightyears Architecture: source Version: 1.5.0-1 Distribution: unstable Urgency: low Maintainer: Debian Python Team , Changed-By: Boyuan Yang Closes: 820718 912488 936945 942622 1010036 Changes: lightyears (1.5.0-1) unstable; urgency=low . [ Jakub Wilk ] * Use canonical URIs for Vcs-* fields. . [ Ondřej Nový ] * d/changelog: Remove trailing whitespaces * d/control: Remove ancient X-Python-Version field * d/control: Update Vcs-* fields with new Debian Python Team Salsa layout. . [ Debian Janitor ] * Use secure URI in debian/watch. * Use secure URI in Homepage field. * Bump debhelper from deprecated 8 to 12. . [ Sandro Tosi ] * Use the new Debian Python Team contact name and address. (Closes: #942622) . [ Boyuan Yang ] * New upstream release 1.5.0. + Migrate package to python3. (Closes: #1010036, #936945) + Migrate to python3-pygame.
Bug#1009398: marked as done (rnetclient: FTBFS: dh_auto_test: error: make -j8 check VERBOSE=1 returned exit code 2)
Your message dated Sat, 07 May 2022 01:05:34 + with message-id and subject line Bug#1009398: fixed in rnetclient 2017.1-2 has caused the Debian Bug report #1009398, regarding rnetclient: FTBFS: dh_auto_test: error: make -j8 check VERBOSE=1 returned exit code 2 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1009398: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1009398 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: rnetclient Version: 2017.1-1 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20220412 ftbfs-bookworm Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[4]: Entering directory '/<>' > FAIL: t-parse > = >rnetclient 2017.1: ./test-suite.log > = > > # TOTAL: 1 > # PASS: 0 > # SKIP: 0 > # XFAIL: 0 > # FAIL: 1 > # XPASS: 0 > # ERROR: 0 > > .. contents:: :depth: 2 > > FAIL: t-parse > = > > Error encoding message > FAIL t-parse (exit status: 255) > > > Testsuite summary for rnetclient 2017.1 > > # TOTAL: 1 > # PASS: 0 > # SKIP: 0 > # XFAIL: 0 > # FAIL: 1 > # XPASS: 0 > # ERROR: 0 > > See ./test-suite.log > Please report to softwares-impos...@fsfla.org > > make[4]: *** [Makefile:888: test-suite.log] Error 1 > make[4]: Leaving directory '/<>' > make[3]: *** [Makefile:996: check-TESTS] Error 2 > make[3]: Leaving directory '/<>' > make[2]: *** [Makefile:1233: check-am] Error 2 > make[2]: Leaving directory '/<>' > make[1]: *** [Makefile:773: check-recursive] Error 1 > make[1]: Leaving directory '/<>' > dh_auto_test: error: make -j8 check VERBOSE=1 returned exit code 2 The full build log is available from: http://qa-logs.debian.net/2022/04/12/rnetclient_2017.1-1_unstable.log All bugs filed during this archive rebuild are listed at: https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20220412;users=lu...@debian.org or: https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20220412=lu...@debian.org=1=1=1=1#results 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: rnetclient Source-Version: 2017.1-2 Done: Sergio Durigan Junior We believe that the bug you reported is fixed in the latest version of rnetclient, 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. Sergio Durigan Junior (supplier of updated rnetclient package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Fri, 06 May 2022 20:56:27 -0400 Source: rnetclient Architecture: source Version: 2017.1-2 Distribution: unstable Urgency: medium Maintainer: Sergio Durigan Junior Changed-By: Sergio Durigan Junior Closes: 1009398 Changes: rnetclient (2017.1-2) unstable; urgency=medium . [ Sergio Durigan Junior ] * Update Vcs-* URLs to use salsa. * d/p/0001-Disable-libgcrypt-FIPS-mode.patch: Disable libgcrypt FIPS mode. Thanks to Thadeu Lima de Souza Cascardo (Closes: #1009398) * d/copyright: Update year and email address. * d/control: Update my email address. * d/control: Wrap long B-D line. * d/control: Bump Standards-Version to 4.6.0. * d/control: Add Rules-Requires-Root: no. * Use debhelper-compat 13. - d/control: B-D on debhelper-compat 13.
Processed: affects 1010536
Processing commands for cont...@bugs.debian.org: > affects 1010536 libdcmtk16 src:plastimatch Bug #1010536 [src:dcmtk] libdcmimage.so.16: cannot open shared object file: No such file or directory Added indication that 1010536 affects libdcmtk16 and src:plastimatch > thanks Stopping processing here. Please contact me if you need assistance. -- 1010536: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1010536 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: tagging 1010536
Processing commands for cont...@bugs.debian.org: > tags 1010536 + ftbfs Bug #1010536 [src:dcmtk] libdcmimage.so.16: cannot open shared object file: No such file or directory Added tag(s) ftbfs. > thanks Stopping processing here. Please contact me if you need assistance. -- 1010536: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1010536 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1004107: meson: flaky autopkgtest on armhf: dictionary changed size during iteration -> timeout
On Thu, 5 May 2022 at 22:39, Paul Gevers wrote: > It just occurred to me that it may be useful to try and reduce the > number of concurrent running tests to something you would expect on a > more normal computer (under conditions where the framework is better > tested). Our armel host has 160 cores, similar, our amd64 ci-worker13 > host has 56. No harm in trying I guess: https://github.com/mesonbuild/meson/pull/10358
Bug#1010608: openldap: Flaky test test063-delta-multiprovider
On Fri, May 06, 2022 at 01:04:54PM -0700, Ryan Tandy wrote: > Control: tag -1 help > > Hi Adrian, Hi Ryan, > On Thu, May 05, 2022 at 02:54:14PM +0300, Adrian Bunk wrote: > > https://tests.reproducible-builds.org/debian/rbuild/unstable/i386/openldap_2.5.11+dfsg-1.rbuild.log.gz > > I'm afraid this link has been superseded by the new upload (which built > successfully & reproducibly). Just to confirm, you're saying that it failed > for the same reason as the amd64 build? > > > Using ldapadd to populate server 2... > > Using ldapsearch to read all the entries from server 1... > > Using ldapsearch to read all the entries from server 2... > > Using ldapsearch to read all the entries from server 3... > > Using ldapsearch to read all the entries from server 4... > > Comparing retrieved entries from server 1 and server 2... > > Comparing retrieved entries from server 1 and server 3... > > test failed - server 1 and server 3 databases differ this was from the reproducible build log. It is the same reason, except that it was "server 3" instead of "server 4" in the "test failed" line. >... > thanks, > Ryan cu Adrian
Bug#1010608: openldap: Flaky test test063-delta-multiprovider
Control: tag -1 help Hi Adrian, On Thu, May 05, 2022 at 02:54:14PM +0300, Adrian Bunk wrote: https://tests.reproducible-builds.org/debian/rbuild/unstable/i386/openldap_2.5.11+dfsg-1.rbuild.log.gz I'm afraid this link has been superseded by the new upload (which built successfully & reproducibly). Just to confirm, you're saying that it failed for the same reason as the amd64 build? Using ldapadd to populate server 2... Using ldapsearch to read all the entries from server 1... Using ldapsearch to read all the entries from server 2... Using ldapsearch to read all the entries from server 3... Using ldapsearch to read all the entries from server 4... Comparing retrieved entries from server 1 and server 2... Comparing retrieved entries from server 1 and server 3... test failed - server 1 and server 3 databases differ I looked at this script, and I think I see how this part might be fragile: *if* I'm reading correctly, it waits for server 1 to receive the changes, but then I think it proceeds with the comparison immediately, and could fail if server 3 or 4 was slower. https://git.openldap.org/openldap/openldap/-/blob/master/tests/scripts/test063-delta-multiprovider#L309-359 This is also different from the previous section (lines 264-294) which waits a flat $SLEEP1 seconds (default: 7) for changes to be synced. However I'm not comfortable proposing changes to the script if I can't validate them. I could really use some help figuring out how to reproduce this failure. I would need to have just server 3 or 4 affected by some slowdown - and not sure what kind, whether CPU or network or disk. I guess I'll start by seeing if I can use tc to add latency to just the specific port... thanks, Ryan
Processed: Re: Bug#1010608: openldap: Flaky test test063-delta-multiprovider
Processing control commands: > tag -1 help Bug #1010608 [src:openldap] openldap: Flaky test test063-delta-multiprovider Added tag(s) help. -- 1010608: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1010608 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1010679: golang-openldap: should this package be removed?
Source: golang-openldap Version: 0.2-2 Severity: serious Tags: bookworm sid Dear Go team, I recently opened an RC bug against golang-openldap (#1007217). Rather than fixing the bug, I am wondering if golang-openldap should just be removed from Debian: - It's an old library with no reverse-dependencies in the archive; - Upstream has stopped development (last release in 2012, last commit in 2016); - The package has been orphaned since 2016 (#836498); - It looks like an actively maintained alternative exists: golang-github-go-ldap-ldap. thanks, Ryan
Processed: tagging 1010657 ...
Processing commands for cont...@bugs.debian.org: > tags 1010657 + upstream Bug #1010657 [src:google-oauth-client-java] google-oauth-client-java: CVE-2021-22573 - IdTokenVerifier does not verify the signature of ID Token Added tag(s) upstream. > forwarded 1010657 > https://github.com/googleapis/google-oauth-java-client/issues/786 Bug #1010657 [src:google-oauth-client-java] google-oauth-client-java: CVE-2021-22573 - IdTokenVerifier does not verify the signature of ID Token Set Bug forwarded-to-address to 'https://github.com/googleapis/google-oauth-java-client/issues/786'. > thanks Stopping processing here. Please contact me if you need assistance. -- 1010657: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1010657 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1010678: slapd: dpkg-reconfigure doesn't restart slapd
Package: slapd Version: 2.5.12+dfsg-1 Severity: serious Control: affects -1 src:sssd The last upload of openldap is affected by #1010677 in debhelper: "dpkg-reconfigure slapd" doesn't restart slapd and the config reset isn't applied. In addition to users' expectations, this breaks (at least) the autopkgtest of sssd, which uses dpkg-reconfigure to reset the configuration to a known starting point.
Processed: slapd: dpkg-reconfigure doesn't restart slapd
Processing control commands: > affects -1 src:sssd Bug #1010678 [slapd] slapd: dpkg-reconfigure doesn't restart slapd Added indication that 1010678 affects src:sssd -- 1010678: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1010678 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#942502: marked as done (src:isc-dhcp: please switch to bundled BIND 9 libraries)
Your message dated Fri, 06 May 2022 16:04:04 + with message-id and subject line Bug#942502: fixed in isc-dhcp 4.4.3-1 has caused the Debian Bug report #942502, regarding src:isc-dhcp: please switch to bundled BIND 9 libraries 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.) -- 942502: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=942502 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:isc-dhcp Version: 4.4.1-2 Severity: important Dear Maintainer, the BIND 9 libraries as used in isc-dhcp has been made private by ISC as of BIND 9.14 release. The ISC-DHCP (a code that has been on life-support for years anyway) is going to keep using BIND 9.11 libraries (where BIND 9.11 is going to be supported until end of 2021). There are two possible options: * The ISC-DHCP will switch to bundled BIND 9 libraries (libisc, libdns, ...) * We keep packaging export libraries in a separate project I think that because the ISC-DHCP is a sole user of the export libraries it makes sense to use the first option. Ondrej -- System Information: Debian Release: 10.1 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.19.0-6-amd64 (SMP w/8 CPU cores) Locale: LANG=en_IE.UTF-8, LC_CTYPE=en_IE.UTF-8 (charmap=UTF-8), LANGUAGE=en_IE:en (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) --- End Message --- --- Begin Message --- Source: isc-dhcp Source-Version: 4.4.3-1 Done: Santiago Ruano Rincón We believe that the bug you reported is fixed in the latest version of isc-dhcp, 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 942...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Santiago Ruano Rincón (supplier of updated isc-dhcp 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: Fri, 06 May 2022 17:24:11 +0200 Source: isc-dhcp Architecture: source Version: 4.4.3-1 Distribution: unstable Urgency: low Maintainer: Debian ISC DHCP Maintainers Changed-By: Santiago Ruano Rincón Closes: 942502 1009209 Changes: isc-dhcp (4.4.3-1) unstable; urgency=low . * New upstream version 4.4.3 * Refresh fix-manpage-macro.patch * Refresh fix-spelling.patch * Disable dhclient-script-exit-status.patch. Upstream has fixed the related bug (#123) * Use bundled BIND libraries instead of libbind-export-dev (Closes: #942502) * Bump debhelper-compat to 13 * Remove Fixed_gcc_10_compilation_issues.patch * Fix some install paths to make dh_missing happy * Add EOM NEWS for client and relay * Fix handling of stale pid file for init.d/dhcpd start. Thanks to H.-Dirk Schmitt (Closes: #1009209) * Bump Standards-Version to 4.6.0.1. No changes required * Bump d/watch version to 4. * Update d/copyright Checksums-Sha1: fcff2de5ada2be42ca21818d570c13358e122672 2172 isc-dhcp_4.4.3-1.dsc 0f29ce84a41b87257f759605db0fd68440354409 10078953 isc-dhcp_4.4.3.orig.tar.gz 6fabdd7d48efc3502e4500b4c0cd29df70310b29 874 isc-dhcp_4.4.3.orig.tar.gz.asc 9d20106968eeb82939240b1e07b6123bf70d56ae 96636 isc-dhcp_4.4.3-1.debian.tar.xz 8903e39c6fc34466460d233b6104e257bd76ea29 9665 isc-dhcp_4.4.3-1_amd64.buildinfo Checksums-Sha256: 427cf495055ec0f7165d69f526223c9726bae73fbc22b07e70452d19374ca47e 2172 isc-dhcp_4.4.3-1.dsc 0e3ec6b4c2a05ec0148874bcd999a66d05518378d77421f607fb0bc9d0135818 10078953 isc-dhcp_4.4.3.orig.tar.gz 0c861bca4ca666a2d93a3f236d20d46791d6eeb80bee16c9fa80187021e63177 874 isc-dhcp_4.4.3.orig.tar.gz.asc ffc468f8189c2c074e1e949b7f2a2f702728e3b6803e15b594f5bb2afd61a427 96636 isc-dhcp_4.4.3-1.debian.tar.xz 05f16bd7b7b8ac59d34a67ec329aed2408a4fd7d2bc027063e90261b4fac4e68 9665 isc-dhcp_4.4.3-1_amd64.buildinfo Files: 003f97ec32b5aa35f334e366dc309273 2172 net important isc-dhcp_4.4.3-1.dsc 9076af4cc1293dde5a7c6cae7de6ab45 10078953 net important isc-dhcp_4.4.3.orig.tar.gz 2c6c1bd70210a0a7a4eb6f92654017f1 874 net important isc-dhcp_4.4.3.orig.tar.gz.asc 06c1dfd4959ec721cdef11b6695998db 96636 net important isc-dhcp_4.4.3-1.debian.tar.xz
Bug#1009209: marked as done (isc-dhcp-server: dhcpd is not starting due to stale pid file)
Your message dated Fri, 06 May 2022 16:04:04 + with message-id and subject line Bug#1009209: fixed in isc-dhcp 4.4.3-1 has caused the Debian Bug report #1009209, regarding isc-dhcp-server: dhcpd is not starting due to stale pid file 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.) -- 1009209: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1009209 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: isc-dhcp-server Severity: grave Tags: patch X-Debbugs-Cc: none, H.-Dirk Schmitt In /etc/init.d/isc-dhcp-server the daemon start is inhibited if a pid file is existing. The content is not checked. So a stale pidfile hinder the start and has to be resolved manually. deb-patch Description: Binary data -- System Information: Debian Release: 11.3 APT prefers stable-updates APT policy: (600, 'stable-updates'), (600, 'stable-security'), (600, 'stable'), (500, 'oldstable-updates'), (490, 'focal-updates'), (490, 'focal-security'), (490, 'focal'), (200, 'testing'), (99, 'oldstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.16.0-0.bpo.4-amd64 (SMP w/8 CPU threads; PREEMPT) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to de_DE.UTF-8), LANGUAGE=de_DE:de:en_US:en Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) -- --- End Message --- --- Begin Message --- Source: isc-dhcp Source-Version: 4.4.3-1 Done: Santiago Ruano Rincón We believe that the bug you reported is fixed in the latest version of isc-dhcp, 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. Santiago Ruano Rincón (supplier of updated isc-dhcp 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: Fri, 06 May 2022 17:24:11 +0200 Source: isc-dhcp Architecture: source Version: 4.4.3-1 Distribution: unstable Urgency: low Maintainer: Debian ISC DHCP Maintainers Changed-By: Santiago Ruano Rincón Closes: 942502 1009209 Changes: isc-dhcp (4.4.3-1) unstable; urgency=low . * New upstream version 4.4.3 * Refresh fix-manpage-macro.patch * Refresh fix-spelling.patch * Disable dhclient-script-exit-status.patch. Upstream has fixed the related bug (#123) * Use bundled BIND libraries instead of libbind-export-dev (Closes: #942502) * Bump debhelper-compat to 13 * Remove Fixed_gcc_10_compilation_issues.patch * Fix some install paths to make dh_missing happy * Add EOM NEWS for client and relay * Fix handling of stale pid file for init.d/dhcpd start. Thanks to H.-Dirk Schmitt (Closes: #1009209) * Bump Standards-Version to 4.6.0.1. No changes required * Bump d/watch version to 4. * Update d/copyright Checksums-Sha1: fcff2de5ada2be42ca21818d570c13358e122672 2172 isc-dhcp_4.4.3-1.dsc 0f29ce84a41b87257f759605db0fd68440354409 10078953 isc-dhcp_4.4.3.orig.tar.gz 6fabdd7d48efc3502e4500b4c0cd29df70310b29 874 isc-dhcp_4.4.3.orig.tar.gz.asc 9d20106968eeb82939240b1e07b6123bf70d56ae 96636 isc-dhcp_4.4.3-1.debian.tar.xz 8903e39c6fc34466460d233b6104e257bd76ea29 9665 isc-dhcp_4.4.3-1_amd64.buildinfo Checksums-Sha256: 427cf495055ec0f7165d69f526223c9726bae73fbc22b07e70452d19374ca47e 2172 isc-dhcp_4.4.3-1.dsc 0e3ec6b4c2a05ec0148874bcd999a66d05518378d77421f607fb0bc9d0135818 10078953 isc-dhcp_4.4.3.orig.tar.gz 0c861bca4ca666a2d93a3f236d20d46791d6eeb80bee16c9fa80187021e63177 874 isc-dhcp_4.4.3.orig.tar.gz.asc ffc468f8189c2c074e1e949b7f2a2f702728e3b6803e15b594f5bb2afd61a427 96636 isc-dhcp_4.4.3-1.debian.tar.xz 05f16bd7b7b8ac59d34a67ec329aed2408a4fd7d2bc027063e90261b4fac4e68 9665 isc-dhcp_4.4.3-1_amd64.buildinfo Files: 003f97ec32b5aa35f334e366dc309273 2172 net important isc-dhcp_4.4.3-1.dsc 9076af4cc1293dde5a7c6cae7de6ab45 10078953 net important isc-dhcp_4.4.3.orig.tar.gz 2c6c1bd70210a0a7a4eb6f92654017f1 874 net important isc-dhcp_4.4.3.orig.tar.gz.asc 06c1dfd4959ec721cdef11b6695998db 96636 net important isc-dhcp_4.4.3-1.debian.tar.xz b0db728a8ef554b80b8568e341df5800 9665 net important isc-dhcp_4.4.3-1_amd64.buildinfo -BEGIN PGP
Bug#1010215: marked as done (sympy breaks einsteinpy autopkgtest: name 'numpy' is not defined)
Your message dated Fri, 6 May 2022 17:59:47 +0200
with message-id
and subject line The new NMUed release is uploaded ...
has caused the Debian Bug report #1010215,
regarding sympy breaks einsteinpy autopkgtest: name 'numpy' is not defined
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.)
--
1010215: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1010215
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: sympy, einsteinpy
Control: found -1 sympy/1.10.1-1
Control: found -1 einsteinpy/0.3.0-2
Severity: serious
Tags: sid bookworm
User: debian...@lists.debian.org
Usertags: breaks needs-update
Dear maintainer(s),
With a recent upload of sympy the autopkgtest of einsteinpy fails in
testing when that autopkgtest is run with the binary packages of sympy
from unstable. It passes when run with only packages from testing. In
tabular form:
passfail
sympy from testing1.10.1-1
einsteinpy from testing0.3.0-2
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 sympy to testing
[1]. Due to the nature of this issue, I filed this bug report against
both packages. Can you please investigate the situation and reassign the
bug to the right package?
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=sympy
https://ci.debian.net/data/autopkgtest/testing/amd64/e/einsteinpy/21184013/log.gz
=== FAILURES
===
___ test_lambdify_with_args
def test_lambdify_with_args():
x, y = symbols("x y")
T = BaseRelativityTensor([x + y, x], (x, y), config="l")
args, f = T.tensor_lambdify(y, x)
arr = np.array(f(2, 1))
/usr/lib/python3/dist-packages/einsteinpy/tests/test_symbolic/test_tensor.py:251:
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
_ _ _ _
y = 2, x = 1
def _lambdifygenerated(y, x):
return numpy.array((x + y, x))
E NameError: name 'numpy' is not defined
:2: NameError
=== warnings summary
===
../../../../usr/lib/python3/dist-packages/einsteinpy/ijit.py:30
../../../../usr/lib/python3/dist-packages/einsteinpy/ijit.py:30
/usr/lib/python3/dist-packages/einsteinpy/ijit.py:30: UserWarning:
Could not import numba package. All einsteinpy functions will work
properly but the CPU intensive algorithms will be slow. Consider
installing numba to boost performance.
tests/test_plotting/test_fractal.py: 64 warnings
/usr/lib/python3/dist-packages/einsteinpy/plotting/fractal.py:20:
DeprecationWarning:
`np.complex` is a deprecated alias for the builtin `complex`. To
silence this warning, use `complex` by itself. Doing this will not
modify any behavior and is safe. If you specifically wanted the numpy
scalar type, use `np.complex128` here.
Deprecated in NumPy 1.20; for more details and guidance:
https://numpy.org/devdocs/release/1.20.0-notes.html#deprecations
-- Docs: https://docs.pytest.org/en/stable/warnings.html
=== short test summary info
FAILED tests/test_symbolic/test_tensor.py::test_lambdify_with_args -
NameErro...
1 failed, 230 passed, 8 xfailed, 640002 warnings in 322.36s
(0:05:22) =
autopkgtest [12:16:46]: test command1
OpenPGP_signature
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
and sucessfully passes the tests.
--
Georges KHAZNADAR et Jocelyne FOURNIER
22 rue des mouettes, 59240 Dunkerque France.
Téléphone +33 (0)3 28 29 17 70
signature.asc
Description: PGP signature
--- End Message ---
Bug#1010215: fixed the bug.
The tiny changes are in a push request at salsa.debian.org I apologize: I forgot the "--delayed 10" option when I made the NMU. The new version of the package (revision 0.3.0-2.1) has been built properly: https://buildd.debian.org/status/package.php?p=einsteinpy Best regards, Georges. -- Georges KHAZNADAR et Jocelyne FOURNIER 22 rue des mouettes, 59240 Dunkerque France. Téléphone +33 (0)3 28 29 17 70 signature.asc Description: PGP signature
Processed: fixed 1010656 in 1.5.1-4
Processing commands for cont...@bugs.debian.org:
> fixed 1010656 1.5.1-4
Bug #1010656 {Done: Adrian Bunk } [libcoq-mathcomp-finmap]
libcoq-mathcomp-finmap: Depends: coq- but it is not installable
Marked as fixed in versions mathcomp-finmap/1.5.1-4.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
1010656: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1010656
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#1010656: marked as done (libcoq-mathcomp-finmap: Depends: coq- but it is not installable)
Your message dated Fri, 6 May 2022 18:12:39 +0300 with message-id <20220506151239.GA16754@localhost> and subject line Close the correct bug (typo in the changelog) has caused the Debian Bug report #1010656, regarding libcoq-mathcomp-finmap: Depends: coq- but it is not installable 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.) -- 1010656: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1010656 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: libcoq-mathcomp-finmap Version: 1.5.1-3 Severity: serious The following packages have unmet dependencies: libcoq-mathcomp-finmap : Depends: coq- but it is not installable --- End Message --- --- Begin Message --- mathcomp-finmap (1.5.1-4) unstable; urgency=medium * Fix previous change. (Closes: #101656) -- Julien Puydt Fri, 06 May 2022 15:13:51 +0200--- End Message ---
Processed: Re: python-anyio: FTBFS in Ubuntu and local pbuilder (ipv6?)
Processing commands for cont...@bugs.debian.org:
> unarchive 1006816
Bug #1006816 {Done: Julien Puydt } [src:python-anyio]
python-anyio: FTBFS in Ubuntu and local pbuilder (ipv6?)
Unarchived Bug 1006816
> reopen 1006816
Bug #1006816 {Done: Julien Puydt } [src:python-anyio]
python-anyio: FTBFS in Ubuntu and local pbuilder (ipv6?)
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
No longer marked as fixed in versions python-anyio/3.5.0-3.
> notfixed 1006816 3.5.0-3
Bug #1006816 [src:python-anyio] python-anyio: FTBFS in Ubuntu and local
pbuilder (ipv6?)
Ignoring request to alter fixed versions of bug #1006816 to the same values
previously set
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
1006816: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1006816
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Processed: patch isn't acceptable
Processing commands for cont...@bugs.debian.org: > tag 859926 - patch Bug #859926 [speech-dispatcher] breaks with pulse-audio as output when spawned by speechd-up from init system Removed tag(s) patch. > thanks Stopping processing here. Please contact me if you need assistance. -- 859926: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=859926 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#909750: applications tries to write to /usr/* directories via libfontconfig1
Hi all, On Mon, 22 Feb 2021 18:41:15 +0100 Dennis Filder wrote: Fix was in v2.13.91 (c4324f54ee16e648ba91f3e9c66af13ab3b1754c) [1] which removed the relevant codepath. Is the current phase of the bookworm release a good moment to apply this? If anyone still deems this worth addressing in 2.13.1, the attached patch fontconfig-2.13.1-909750-access-w_ok.patch silences the warning through an added writability check. It's policy violation, I think it's worth to try and fix it. However, while looking into this I ran into test suite issues: - test/run-test-conf.sh needs dash.patch to work with dash as /bin/sh - test/run-test.sh fails if /bin/bwrap (package bubblewrap) is installed; disable-bwrap.patch patches it out. This last one can probably be dealt with via an Build-Conflicts stanza? 1: https://gitlab.freedesktop.org/fontconfig/fontconfig/-/commit/c4324f54ee16e648ba91f3e9c66af13ab3b1754c Paul OpenPGP_signature Description: OpenPGP digital signature
Bug#998557: spice-gtk: FTBFS: ../meson.build:4:0: ERROR: Unknown options: "celt051"
Source: spice-gtk
Version: 0.39-3
Tags: pending
Followup-For: Bug #998557
Dear maintainer,
I have uploaded an NMU to DELAYED/2 to fix this issue. Please let me
know if I should cancel or delay.
Paul
diff --git a/debian/changelog b/debian/changelog
index bf8a2aa..3d72d7c 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,15 @@
+spice-gtk (0.39-3.1) unstable; urgency=medium
+
+ [ Paul Gevers ]
+ * Non-maintainer upload
+ * Add pyparsing-detection.patch (taken from upstream) to prevent FTBFS
+
+ [ Simon Chopin ]
+ * d/rules: remove the -Dcelt051=disabled option as the whole CELT
+support has been removed upstream (Closes: #998557)
+
+ -- Paul Gevers Thu, 05 May 2022 22:15:35 +0200
+
spice-gtk (0.39-3) unstable; urgency=medium
* debian/control: Increased debhelper-compat to 13
diff --git a/debian/patches/pyparsing-detection.patch
b/debian/patches/pyparsing-detection.patch
new file mode 100644
index 000..3fd5913
--- /dev/null
+++ b/debian/patches/pyparsing-detection.patch
@@ -0,0 +1,33 @@
+From a7b5474bf808934cf0ee1107a58d5f4d97b9afbf Mon Sep 17 00:00:00 2001
+From: Frediano Ziglio
+Date: Thu, 28 Oct 2021 16:45:34 +0100
+Subject: [PATCH] build: Correctly check for Python modules
+
+Currently using Meson the command "python -m " is
+run. However this command instead of trying to import the module
+tried to execute it as a script failing for the updated pyparsing
+with:
+
+/usr/bin/python3: No module named pyparsing.__main__; 'pyparsing' is a
package and cannot be directly executed
+
+So instead use "python -c 'import ".
+Autoconf is already using that command (see m4/ax_python_module.m4).
+
+Signed-off-by: Frediano Ziglio
+---
+ meson.build | 2 +-
+ 1 file changed, 1 insertion(+), 1 deletion(-)
+
+Index: spice-gtk/subprojects/spice-common/meson.build
+===
+--- spice-gtk.orig/subprojects/spice-common/meson.build
spice-gtk/subprojects/spice-common/meson.build
+@@ -132,7 +132,7 @@ if spice_common_generate_client_code or
+ if get_option('python-checks')
+ foreach module : ['six', 'pyparsing']
+ message('Checking for python module @0@'.format(module))
+- cmd = run_command(python, '-m', module)
++ cmd = run_command(python, '-c', 'import @0@'.format(module))
+ if cmd.returncode() != 0
+ error('Python module @0@ not found'.format(module))
+ endif
diff --git a/debian/patches/series b/debian/patches/series
new file mode 100644
index 000..86fe649
--- /dev/null
+++ b/debian/patches/series
@@ -0,0 +1 @@
+pyparsing-detection.patch
diff --git a/debian/rules b/debian/rules
index 53672d4..83928b4 100755
--- a/debian/rules
+++ b/debian/rules
@@ -6,7 +6,7 @@
override_dh_auto_configure:
dh_auto_configure -- \
-Dsmartcard=enabled -Dgtk=enabled \
--Dintrospection=enabled -Dvapi=enabled -Dcelt051=disabled \
+-Dintrospection=enabled -Dvapi=enabled \
-Dusbredir=enabled -Dpolkit=enabled \
-Dlz4=enabled -Dgtk_doc=enabled \
-Dusb-acl-helper-dir=/usr/libexec \
Bug#1010655: marked as done (libcoq-mathcomp-bigenough: Depends: coq- but it is not installable)
Your message dated Fri, 06 May 2022 13:34:58 + with message-id and subject line Bug#1010655: fixed in mathcomp-bigenough 1.0.1-4 has caused the Debian Bug report #1010655, regarding libcoq-mathcomp-bigenough: Depends: coq- but it is not installable 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.) -- 1010655: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1010655 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: libcoq-mathcomp-bigenough Version: 1.0.1-3 Severity: serious The following packages have unmet dependencies: libcoq-mathcomp-bigenough : Depends: coq- but it is not installable --- End Message --- --- Begin Message --- Source: mathcomp-bigenough Source-Version: 1.0.1-4 Done: Julien Puydt We believe that the bug you reported is fixed in the latest version of mathcomp-bigenough, 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 1010...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Julien Puydt (supplier of updated mathcomp-bigenough package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Fri, 06 May 2022 15:11:30 +0200 Source: mathcomp-bigenough Architecture: source Version: 1.0.1-4 Distribution: unstable Urgency: medium Maintainer: Debian OCaml Maintainers Changed-By: Julien Puydt Closes: 1010655 Changes: mathcomp-bigenough (1.0.1-4) unstable; urgency=medium . * Fix previous change. (Closes: #1010655) Checksums-Sha1: f12a905fd467a365bbd28a3ce25c539ed7731ba2 2107 mathcomp-bigenough_1.0.1-4.dsc 995e29521c806065f5a24a18e620421e30ab8252 8496 mathcomp-bigenough_1.0.1-4.debian.tar.xz dbae6dae6b83f3e556c53e679e89469929cdf960 6688 mathcomp-bigenough_1.0.1-4_source.buildinfo Checksums-Sha256: e539c4c2ef1b3d7ec55da1eaad9811d71881eff9f65c4fd658ae8849fb1242f6 2107 mathcomp-bigenough_1.0.1-4.dsc 7ac689e7219a277ec85c91e21c1bcc09b928173584a7aff682d1e071e950c698 8496 mathcomp-bigenough_1.0.1-4.debian.tar.xz 2bef88d4804d8e17696e4a37983c6794a4ad30e06e89946218dbbf14a4a6dccb 6688 mathcomp-bigenough_1.0.1-4_source.buildinfo Files: 124575fe421016c6df9c403b782ec479 2107 ocaml optional mathcomp-bigenough_1.0.1-4.dsc ea4b7a63ad85f54d0bfb2637e73d5bc2 8496 ocaml optional mathcomp-bigenough_1.0.1-4.debian.tar.xz 7c2d45637a794f8b51381ae75a979498 6688 ocaml optional mathcomp-bigenough_1.0.1-4_source.buildinfo -BEGIN PGP SIGNATURE- iQJGBAEBCgAwFiEEgS7v2KP7pKzk3xFLBMU71/4DBVEFAmJ1HrQSHGpwdXlkdEBk ZWJpYW4ub3JnAAoJEATFO9f+AwVRyhwP/ihz2IpfeQs5jhsxnJA5RuOhRiePKSDp nYmQ0OAAeIOT+OrpSVqCqrhb8YQFcxED63qg8KWNleZQYbdX0v+oVP3BJKWwKv9y aY0vJ1R9HQU2STGxfVcO14B9LphyYqjZykl1tMQ4InGXyZeL2kahSUWZQG3q0lDy deTZouj1scKquXgzvwu9OsOM2EWP1opRwle+j+OLTXBqbcrGlnCEDF9vdodPNT1g rEwUkIgwys9bBmg7PcM7j7vdguZqF6aRaDLs4Fmz26bMGmVdFrkKzQ22BZku9qdb K+DxHWm/Y3RgRQDtfRQRKB+t6XQfpd5ODMLcaIbaIEtZCd01t0zeIOHCbFaUfCAB rlz7vcr+3EXeMIriLuiH3qTYeIU3qLCXC57tFicSUPMxGUUb95HfVblnnkLRufrn rRZgw5DpJKxIWWaJQb7I5fa2nnV22mQA3mTYF2nYD/FXT4f0xwnS8U0efwUCIoZu xnO4glOzicPucIC220bpXaGQR/8LvH9ViiKDdBp1/8Vsa/Rrg04TTFHjU0KmeLAp KXJI/VhEVwuaiMVS9gWpheq2P+c6udMURAtnEi0lklI9G2rj/11hU9FwUjEqXer5 VSvnRubPat1Iz+6zkbkQz1FUXwBkocR3wFyrPSN5NNx6H1ueI4DpATcSPxATAcYk hkGjaJMiioEs =JhCr -END PGP SIGNATURE End Message ---
Processed: Re:
Processing commands for cont...@bugs.debian.org: > unmerge 951627 Bug #951627 [isc-dhcp-server] isc-dhcp-server: Can't stop the daemon Bug #1009209 [isc-dhcp-server] isc-dhcp-server: dhcpd is not starting due to stale pid file Disconnected #951627 from all other report(s). > severity 951627 important Bug #951627 [isc-dhcp-server] isc-dhcp-server: Can't stop the daemon Severity set to 'important' from 'grave' > tags 951627 - patch Bug #951627 [isc-dhcp-server] isc-dhcp-server: Can't stop the daemon Removed tag(s) patch. > tags 1009209 + pending Bug #1009209 [isc-dhcp-server] isc-dhcp-server: dhcpd is not starting due to stale pid file Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 1009209: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1009209 951627: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=951627 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#951627:
unmerge 951627 severity 951627 important tags 951627 - patch tags 1009209 + pending thanks El 14/04/22 a las 12:58, H.-Dirk Schmitt escribió: > forcemerge 1009209 951627 > thanks Thanks, but I don't see how both bugs are the same. I am applying your patch. I hope to upload a new revision shortly. Cheers, -- Santiago signature.asc Description: PGP signature
Bug#1010192: marked as done (ModuleNotFoundError: No module named 'qrtools')
Your message dated Fri, 06 May 2022 12:49:12 + with message-id and subject line Bug#1010192: fixed in qr-tools 2.1~bzr46-3 has caused the Debian Bug report #1010192, regarding ModuleNotFoundError: No module named 'qrtools' 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.) -- 1010192: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1010192 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: qtqr Version: 2.1~bzr46-2 Severity: grave Justification: renders package unusable Hey. On a fresh install of the package: $ qtqr Traceback (most recent call last): File "/usr/bin/qtqr", line 15, in from qrtools import QR ModuleNotFoundError: No module named 'qrtools' Thanks, Chris. -- System Information: Debian Release: bookworm/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 5.17.0-1-amd64 (SMP w/4 CPU threads; PREEMPT) Locale: LANG=en_DE.UTF-8, LC_CTYPE=en_DE.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages qtqr depends on: ii python3-pyqt55.15.6+dfsg-1+b2 ii python3-qrtools 2.1~bzr46-2 qtqr recommends no packages. qtqr suggests no packages. -- no debconf information --- End Message --- --- Begin Message --- Source: qr-tools Source-Version: 2.1~bzr46-3 Done: Georges Khaznadar We believe that the bug you reported is fixed in the latest version of qr-tools, 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 1010...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Georges Khaznadar (supplier of updated qr-tools 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: Fri, 06 May 2022 14:02:13 +0200 Source: qr-tools Architecture: source Version: 2.1~bzr46-3 Distribution: unstable Urgency: medium Maintainer: Georges Khaznadar Changed-By: Georges Khaznadar Closes: 1010192 Changes: qr-tools (2.1~bzr46-3) unstable; urgency=medium . * uploaded the source package again, in order to have it compiled with Python3.10. Closes: #1010192 Checksums-Sha1: 069bf5bfd048926dbb7325e8c076225d33e18285 1947 qr-tools_2.1~bzr46-3.dsc 68e19e9c7cf238a5a2bb7c8d09997993c1b054e7 10480 qr-tools_2.1~bzr46-3.debian.tar.xz 33f96d904fb67492a2ebd24b0361bda16ffc462c 10424 qr-tools_2.1~bzr46-3_amd64.buildinfo Checksums-Sha256: 86c84d720f6ff49e72677164b6be0b1ad588bf90a041881e54402085b3c49a2d 1947 qr-tools_2.1~bzr46-3.dsc c7cf32606c369d32e6d680ff13614bdf0516e3c93a72b54878a9cfde7dc9ba42 10480 qr-tools_2.1~bzr46-3.debian.tar.xz c79289ce5052e29308d066075c8f3987a0f390845e647041b55ada7f503bd513 10424 qr-tools_2.1~bzr46-3_amd64.buildinfo Files: 9e015f402769c227bcf2c9b5f18efb5b 1947 python optional qr-tools_2.1~bzr46-3.dsc e91c0b70d185559810ff15e040c407d7 10480 python optional qr-tools_2.1~bzr46-3.debian.tar.xz 3894cb9087065519fad40ee5051e0659 10424 python optional qr-tools_2.1~bzr46-3_amd64.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEEM0CzZP9nFT+3zK6FHCgWkHE2rjkFAmJ1EcEACgkQHCgWkHE2 rjmJ2BAArBsZCdRrfOA7piwvB4fwarWjKt7QFGp1uUka5gKSZ08SpKgiMt+y/vxE DPJJxVf3kK7IdEqtPaHMvmSxvofFRHbW7XtcUkFHe4+rYGevaQgylnfu6TRRgVLH Pxm4prDB9M6jTM81ebGKI7Uk9pYy2pFAWdbtE4FprYE7FfBFxXZOm41xcUyQZDJ9 +cdG2jQOlWC2VDRubSOWt1BrWN/ohklR2XEAgVSkc7vV+MbQOlK6kbR+L4t2CBLy LJ+lVq57KmhrSg9GC9aBvR3E8RvsBceatrGSeVA9VCEghnjRVr3gkgfskr1xDASA xFfh1GIMyxulYATdMV9BDZcAMnG82P9D0rbdPmgKEq57rlIqOg46Ag+6ZjbA0b1V tWWYQe7DBtEkT9pgjhwaK9HZDBut3F05XXaqYc7qJwEy8IofcTEJF1//VEOXEJ7C QqU99DNbrSbxR6LdCDPWfN/sb15tmdpKmsbt46GYgooSREBwr8S+euFBxF2xtbb+ df9itLcQ49EFQbt5Q689TfMT9wI+Qv1+KPmx4JREgYYF7JdoVykH5NOOAlnRamOt xf7k0NeR0T7Rl0KAbHxgpMgOG2HYjlGpCZGsmXxtpxzVV+/aynHrtjuYmfdGG2tA PIC+ecg1PiTWFYHmJdpUs87eKXbfaIaTQD64e605hW7MW/FqO0E= =DkrQ -END PGP SIGNATURE End Message ---
Bug#1008052: marked as done (python-pecan FTBFS: build tests fail with python3.10)
Your message dated Fri, 06 May 2022 12:03:55 +
with message-id
and subject line Bug#1008052: fixed in python-pecan 1.4.1-1
has caused the Debian Bug report #1008052,
regarding python-pecan FTBFS: build tests fail 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.)
--
1008052: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1008052
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: python-pecan
Version: 1.3.3-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
Dear Maintainer,
In Ubuntu, the attached patch was applied to fix the build tests when
using python3.10:
* debian/patches/fix-tests-on-python-3.10.patch: Pull in upstream patch to
fix build tests on python3.10 (LP: #1965132).
Thanks,
Nick
diff -Nru python-pecan-1.3.3/debian/patches/fix-tests-on-python-3.10.patch
python-pecan-1.3.3/debian/patches/fix-tests-on-python-3.10.patch
--- python-pecan-1.3.3/debian/patches/fix-tests-on-python-3.10.patch
1969-12-31 19:00:00.0 -0500
+++ python-pecan-1.3.3/debian/patches/fix-tests-on-python-3.10.patch
2022-03-18 15:41:48.0 -0400
@@ -0,0 +1,87 @@
+Description: Fix tests to work on Python 3.10
+Origin: upstream,
https://github.com/pecan/pecan/pull/131/commits/f189d0eafbaacc5b5093bb8854cd2068e22b6c08
+Bug-Ubuntu: https://bugs.launchpad.net/ubuntu/+source/python-pecan/+bug/1965132
+---
+From f189d0eafbaacc5b5093bb8854cd2068e22b6c08 Mon Sep 17 00:00:00 2001
+From: Evangelos Foutras
+Date: Wed, 8 Dec 2021 07:01:16 +0200
+Subject: [PATCH] Fix tests to work on Python 3.10
+
+Python 3.10 adds the class name to the exception; adjust four tests
+affected by this change.
+
+Fixes: https://github.com/pecan/pecan/issues/130
+---
+ pecan/tests/test_base.py | 18 +-
+ pecan/tests/test_no_thread_locals.py | 20 ++--
+ 2 files changed, 27 insertions(+), 11 deletions(-)
+--- a/pecan/tests/test_base.py
b/pecan/tests/test_base.py
+@@ -456,8 +456,12 @@
+ assert type(ex) == TypeError
+ assert ex.args[0] in (
+ "index() takes exactly 2 arguments (1 given)",
+-"index() missing 1 required positional argument: 'id'"
+-) # this messaging changed in Python 3.3
++"index() missing 1 required positional argument: 'id'",
++(
++"TestControllerArguments.app_..RootController."
++"index() missing 1 required positional argument: 'id'"
++),
++) # this messaging changed in Python 3.3 and again in Python 3.10
+
+ def test_single_argument(self):
+ r = self.app_.get('/1')
+@@ -994,9 +998,13 @@
+ except Exception as ex:
+ assert type(ex) == TypeError
+ assert ex.args[0] in (
+-"eater() takes at least 2 arguments (1 given)",
+-"eater() missing 1 required positional argument: 'id'"
+-) # this messaging changed in Python 3.3
++"eater() takes exactly 2 arguments (1 given)",
++"eater() missing 1 required positional argument: 'id'",
++(
++"TestControllerArguments.app_..RootController."
++"eater() missing 1 required positional argument: 'id'"
++),
++) # this messaging changed in Python 3.3 and again in Python 3.10
+
+ def test_one_remainder(self):
+ r = self.app_.get('/eater/1')
+--- a/pecan/tests/test_no_thread_locals.py
b/pecan/tests/test_no_thread_locals.py
+@@ -361,9 +361,13 @@
+ except Exception as ex:
+ assert type(ex) == TypeError
+ assert ex.args[0] in (
+-"index() takes exactly 4 arguments (3 given)",
+-"index() missing 1 required positional argument: 'id'"
+-) # this messaging changed in Python 3.3
++"index() takes exactly 2 arguments (1 given)",
++"index() missing 1 required positional argument: 'id'",
++(
++"TestControllerArguments.app_..RootController."
++"index() missing 1 required positional argument: 'id'"
++),
++) # this messaging changed in Python 3.3 and again in Python 3.10
+
+ def test_single_argument(self):
+ r = self.app_.get('/1')
+@@ -763,9 +767,13 @@
+ except Exception as
Bug#1008052: marked as pending in python-pecan
Control: tag -1 pending Hello, Bug #1008052 in python-pecan 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/python/python-pecan/-/commit/9c3b8dc4f75227329b1d3cfc672b51ea777bfc81 Fixes FTBFS with Python 3.10 (Closes: #1008052). (this message was generated automatically) -- Greetings https://bugs.debian.org/1008052
Processed: Bug#1008052 marked as pending in python-pecan
Processing control commands: > tag -1 pending Bug #1008052 [python-pecan] python-pecan FTBFS: build tests fail with python3.10 Added tag(s) pending. -- 1008052: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1008052 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1007738: marked as done (webcamoid: autopkgtest regression: Unknown failure encountered running a test)
Your message dated Fri, 06 May 2022 10:49:43 + with message-id and subject line Bug#1007738: fixed in webcamoid 9.0.0-4 has caused the Debian Bug report #1007738, regarding webcamoid: autopkgtest regression: Unknown failure encountered running a test 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.) -- 1007738: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1007738 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: webcamoid Version: 9.0.0-3 Severity: serious User: debian...@lists.debian.org Usertags: regression Dear maintainer(s), With a recent upload of webcamoid the autopkgtest of webcamoid fails in testing when that autopkgtest is run with the binary packages of webcamoid from unstable. It passes when run with only packages from testing. In tabular form: passfail webcamoid from testing9.0.0-3 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=webcamoid https://ci.debian.net/data/autopkgtest/testing/amd64/w/webcamoid/19983920/log.gz [100%] Built target StandAlone make[2]: Leaving directory '/tmp/autopkgtest-lxc.bimp4e9z/downtmp/build.UDP/src/obj-x86_64-linux-gnu' /usr/bin/cmake -E cmake_progress_start /tmp/autopkgtest-lxc.bimp4e9z/downtmp/build.UDP/src/obj-x86_64-linux-gnu/CMakeFiles 0 make[1]: Leaving directory '/tmp/autopkgtest-lxc.bimp4e9z/downtmp/build.UDP/src/obj-x86_64-linux-gnu' dh_auto_test -a rm -fr -- /tmp/dh-xdg-rundir-ifBRypUJ create-stamp debian/debhelper-build-stamp test_exists ASSERT:Unknown failure encountered running a test Ran 2 tests. FAILED (failures=1) autopkgtest [03:06:45]: test check-auto-tests.sh OpenPGP_signature Description: OpenPGP digital signature --- End Message --- --- Begin Message --- Source: webcamoid Source-Version: 9.0.0-4 Done: Barak A. Pearlmutter We believe that the bug you reported is fixed in the latest version of webcamoid, 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 1007...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Barak A. Pearlmutter (supplier of updated webcamoid package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Fri, 06 May 2022 10:58:49 +0100 Source: webcamoid Architecture: source Version: 9.0.0-4 Distribution: unstable Urgency: medium Maintainer: Barak A. Pearlmutter Changed-By: Barak A. Pearlmutter Closes: 1007738 Changes: webcamoid (9.0.0-4) unstable; urgency=medium . * Track upstream mods, mainly translations * Remove debian/tests/ (closes: #1007738) which were (a) useless, and (b) failing due to upstream build system changes * Install new metainfo file Checksums-Sha1: e9ee40ca1f305c548e04e2e2b05b33aa2445cc3b 2628 webcamoid_9.0.0-4.dsc 9f1e5ca35ba2bdbfda04d6458c4f17fbaaa5a0c6 265896 webcamoid_9.0.0-4.debian.tar.xz 78ee0939c639be6e16bf0a9035b4c3517752307a 19047 webcamoid_9.0.0-4_source.buildinfo Checksums-Sha256: dd3cc1beb002909c6839f2e926776d62b1d3d8da85722d3c3aed3ef4e10df629 2628 webcamoid_9.0.0-4.dsc 77fd20a96e73fb04aa2fbe3393a01c31fdebd889ce210204d56057a21b17b2b9 265896 webcamoid_9.0.0-4.debian.tar.xz 6edfb46a17de9bc033832af0be1aba198562f00ee80b18a85cb2bcd2b2bf0a0e 19047 webcamoid_9.0.0-4_source.buildinfo Files: d0ab2c0089ceef83b743b20b2f29afe2 2628 video optional webcamoid_9.0.0-4.dsc 28521b5aa574410f5dab7fc0cb4dc8fc 265896 video optional webcamoid_9.0.0-4.debian.tar.xz 75b0727ec83fec3487b6aecbfbc556ea 19047 video optional webcamoid_9.0.0-4_source.buildinfo -BEGIN PGP SIGNATURE- iQJDBAEBCgAtFiEE+nZaz+JE7Dn2AefCmesepNIze4gFAmJ0+QYPHGJhcEBkZWJp YW4ub3JnAAoJEJnrHqTSM3uIHIYP/3G34nJ/BOzu+yFUyirdh927CBAoHuBzHtq4 pFEFBhB3sl0+ic4HDMeXW0OSF0g+WPNXXY5Ey+fMAgYbMLjMDK1snEvqqlk8hxrP
Bug#1010166: webkit2gtk: 2.36.1-1 apparent regression seen in devhelp autopkgtest
On Mon, Apr 25, 2022 at 11:37:02AM -0400, Jeremy Bicha wrote: > The new release of webkit2gtk won't migrate to Testing because of an > autopkgtest regression in devhelp. I'm filing this bug to make sure > that the maintainer notices the issue. This has been fixed upstream but I think I'll just wait for the next stable release instead of patching the current one. Berto
Processed: severity of 1010639 is minor
Processing commands for cont...@bugs.debian.org: > severity 1010639 minor Bug #1010639 [beep] beep: Doesn't beep - could not open any device Severity set to 'minor' from 'grave' > thanks Stopping processing here. Please contact me if you need assistance. -- 1010639: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1010639 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1010307: closing 1010307
# UML version 5.17.3 has already been uploaded close 1010307 thanks -- Ritesh Raj Sarraf RESEARCHUT - http://www.researchut.com "Necessity is the mother of invention." "à¤à¤µà¥à¤¶à¥à¤¯à¤à¥à¤¤à¤¾ à¤à¤µà¤¿à¤·à¥à¤à¤¾à¤° à¤à¥ à¤à¤¨à¤¨à¥ हà¥"
Bug#1010639: beep: Doesn't beep - could not open any device
severity -1 minor Dear Richard, * Richard Z [2022-05-05 22:24:21 CEST]: > Dear Maintainer, > > installed the beep package and tried beep without any arguments and it does > not > work. > > $ BEEP_LOG_LEVEL=999 beep > beep-log: Verbose: log_constructor > beep-log: Verbose: beep_driver_console_constructor > beep-log: Verbose: beep_drivers_register 0x5658c6a0 (console) > beep-log: Verbose: beep_driver_evdev_constructor > beep-log: Verbose: beep_drivers_register 0x5658c6e0 (evdev) > beep: Verbose: evdev driver_detect 0x5658c6e0 (nil) > beep: Verbose: b-lib: could not open(2) /dev/input/by-path/platform-pcspkr- > event-spkr: Permission denied How are you logged into your system? The udev rule that beep installs requires you to be logged in on a virtual console. Please be referred to the documentation in /usr/share/doc/beep/PERMISSIONS.md.gz why this is so. What always works is using beep as root, regardless of how people are logged in, so I don't follow your call for that this is a grave bug - in fact it works as intended and isn't even a bug at all. I am starting to (re)implement a specific beep group to which people could be added on top of that. This requires a bit testing though, and will hit unstable and only be in the next release then. In the meantime you could add a corresponding udev rule for giving access to users of a specific group yourself while following the documentation in the PERMISSIONS file. Hope that helps, Rhonda -- Fühlst du dich mutlos, fass endlich Mut, los | Fühlst du dich hilflos, geh raus und hilf, los| Wir sind Helden Fühlst du dich machtlos, geh raus und mach, los | 23.55: Alles auf Anfang Fühlst du dich haltlos, such Halt und lass los|
Processed: closing 1010307
Processing commands for cont...@bugs.debian.org: > # UML version 5.17.3 has already been uploaded > close 1010307 Bug #1010307 [src:user-mode-linux] user-mode-linux: FTBFS in bookworm as it Build-Depends on removed linux-source-5.16" Marked Bug as done > thanks Stopping processing here. Please contact me if you need assistance. -- 1010307: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1010307 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1010657: google-oauth-client-java: CVE-2021-22573 - IdTokenVerifier does not verify the signature of ID Token
Source: google-oauth-client-java Version: 1.28.0-2 Severity: grave Tags: security Justification: user security hole X-Debbugs-Cc: codeh...@debian.org, Debian Security Team Hi, The following vulnerability was published for google-oauth-client-java. CVE-2021-22573[0]: | The vulnerability is that IDToken verifier does not verify if token is | properly signed. Signature verification makes sure that the token's | payload comes from valid provider, not from someone else. An attacker | can provide a compromised token with custom payload. The token will | pass the validation on the client side. We recommend upgrading to | version 1.33.3 or above > The spec requires to validate the signature of ID token for apps that > cannot guarantee TLS communication, which is the case for this library. > This library initiates a local server that can run on any client machine > without TLS support. So, it is critical to validate the signature, > before trusting the claims of an ID token, which can be received from > a malicious service provider. Fixed in upstream release 1.33.3 If you fix the vulnerability please also make sure to include the CVE (Common Vulnerabilities & Exposures) id in your changelog entry. For further information see: [0] https://security-tracker.debian.org/tracker/CVE-2021-22573 https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-22573 Please adjust the affected versions in the BTS as needed. -- 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.17.0-1-amd64 (SMP w/16 CPU threads; PREEMPT) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), LANGUAGE=en_GB:en Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled
Bug#1010656: libcoq-mathcomp-finmap: Depends: coq- but it is not installable
Package: libcoq-mathcomp-finmap Version: 1.5.1-3 Severity: serious The following packages have unmet dependencies: libcoq-mathcomp-finmap : Depends: coq- but it is not installable
Bug#1010655: libcoq-mathcomp-bigenough: Depends: coq- but it is not installable
Package: libcoq-mathcomp-bigenough Version: 1.0.1-3 Severity: serious The following packages have unmet dependencies: libcoq-mathcomp-bigenough : Depends: coq- but it is not installable
