Bug#996012: marked as done (d-shlibs makes libzstd FTBFS: sed: -e expression #89, char 81: Unmatched ( or \()
Your message dated Sun, 10 Oct 2021 06:48:44 + with message-id and subject line Bug#996012: fixed in d-shlibs 0.102 has caused the Debian Bug report #996012, regarding d-shlibs makes libzstd FTBFS: sed: -e expression #89, char 81: Unmatched ( or \( 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.) -- 996012: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=996012 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: d-shlibs Version: 0.101 Severity: serious Tags: ftbfs Control: affects -1 + src:libzstd User: helm...@debian.org Usertags: rebootstrap libzstd fails to build from source in unstable on amd64. A build now ends with: |debian/rules override_dh_install | make[1]: Entering directory '/<>' | # Call d-shlibmove to comply with library packaging guide | d-shlibmove --commit \ | --multiarch \ | --devunversioned \ | --exclude-la \ | --movedev "debian/tmp/usr/include/*" usr/include \ | --movedev "debian/tmp/usr/lib/pkgconfig/*" usr/lib/x86_64-linux-gnu/pkgconfig \ | debian/tmp/usr/lib/lib*.so | Library package automatic movement utility | sed: -e expression #89, char 81: Unmatched ( or \( | make[1]: *** [debian/rules:34: override_dh_install] Error 1 | make[1]: Leaving directory '/<>' | make: *** [debian/rules:16: binary] Error 2 | dpkg-buildpackage: error: fakeroot debian/rules binary subprocess returned exit status 2 I think it is fairly safe to bet that this is caused by the d-shlibs upload. What puzzles me a bit is that build time testing didn't catch this. And that autopkgtests for d-shlibs aren't failing. Can you also look into why testing didn't prevent this? A workaround or quick solution would be appreciated as it breaks all jobs at https://jenkins.debian.net/view/rebootstrap/. Helmut --- End Message --- --- Begin Message --- Source: d-shlibs Source-Version: 0.102 Done: Jonas Smedegaard We believe that the bug you reported is fixed in the latest version of d-shlibs, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 996...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Jonas Smedegaard (supplier of updated d-shlibs 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 Oct 2021 08:36:48 +0200 Source: d-shlibs Architecture: source Version: 0.102 Distribution: unstable Urgency: medium Maintainer: Jonas Smedegaard Changed-By: Jonas Smedegaard Closes: 995972 996012 Changes: d-shlibs (0.102) unstable; urgency=medium . * fix typos in regex; closes: bug#996012, #995972, thanks to Helmut Grohne and Laurent Bigonville * convert custom tests into autopkgtest Checksums-Sha1: c740e78fbdf7e674ca3faeca24ded5e48cd6b77c 1744 d-shlibs_0.102.dsc 9eb6531176f143b7f6d167d3840209747295d639 25156 d-shlibs_0.102.tar.xz c06b4b374963b02e4e5e1caf49e62be31ade10a4 5661 d-shlibs_0.102_amd64.buildinfo Checksums-Sha256: 9ed0e1ad5ded2e313ee4d513cc078914f141a6cbd6e50ffe3ceca066149df11d 1744 d-shlibs_0.102.dsc 4331e9a18c623dd8c9052cf2a985dbb7b48786a1770ca8ba0f7db130deb65bd4 25156 d-shlibs_0.102.tar.xz b26d513e9b07dbecf7d0a15b531d11a55044cadf7bf83d48e74b3c626e2a4bff 5661 d-shlibs_0.102_amd64.buildinfo Files: 29bd9bcd323abfad4f732f049850cd41 1744 utils optional d-shlibs_0.102.dsc d4f28126d208d6b68a4e110de7be0c0b 25156 utils optional d-shlibs_0.102.tar.xz 657ccc828ec54a2fd83b910b802d5fe1 5661 utils optional d-shlibs_0.102_amd64.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEn+Ppw2aRpp/1PMaELHwxRsGgASEFAmFiimEACgkQLHwxRsGg ASGDVBAAhZtcAlAEua/asLLUliZu1Bxp3iE94oY0PPxEdQW5j1r42MdZUmr8REjq WQNx3VI/aljfeKJXVKtAF0R8oASYi20DJeNi+KW8dGghiIuLsUSJiUnA66jvVjN0 7IYrnL8PX8AQBfhS34q+LG3F1ZvCWPBbVPh4r5G2Bb4BW/zLn2zYqFpuUV2YZjFM 2lbXzpDvIGja42vHu4Gu0+QkfsHQ2ZnEDPPvqiYwnLHeWII60wvfE8SnrnmASkYq YSMeXupnmUMuzMB0kxcxOtVrvfbDXRMrRg002DrECiZI5QnbpgjEY93xSHGz/w6F ck29urGSw/Ia1BTJ0dHMN8GI0SEBmB3CNvheMfk8B/i3VCJ9WbJBSOOshEYXz/mw 5ahU7sXvSuJ8DPinxLBSgCvFAmhMA2ULeQMtoQJ+GSBQ+A56n3djDJv7VA373iQh OzXHdP8VeCNorulAzJnC28FMjpv6Vsb/cGXNDqQo3yToqpLhGYUK
Bug#996012: d-shlibs makes libzstd FTBFS: sed: -e expression #89, char 81: Unmatched ( or \(
Package: d-shlibs Version: 0.101 Severity: serious Tags: ftbfs Control: affects -1 + src:libzstd User: helm...@debian.org Usertags: rebootstrap libzstd fails to build from source in unstable on amd64. A build now ends with: |debian/rules override_dh_install | make[1]: Entering directory '/<>' | # Call d-shlibmove to comply with library packaging guide | d-shlibmove --commit \ | --multiarch \ | --devunversioned \ | --exclude-la \ | --movedev "debian/tmp/usr/include/*" usr/include \ | --movedev "debian/tmp/usr/lib/pkgconfig/*" usr/lib/x86_64-linux-gnu/pkgconfig \ | debian/tmp/usr/lib/lib*.so | Library package automatic movement utility | sed: -e expression #89, char 81: Unmatched ( or \( | make[1]: *** [debian/rules:34: override_dh_install] Error 1 | make[1]: Leaving directory '/<>' | make: *** [debian/rules:16: binary] Error 2 | dpkg-buildpackage: error: fakeroot debian/rules binary subprocess returned exit status 2 I think it is fairly safe to bet that this is caused by the d-shlibs upload. What puzzles me a bit is that build time testing didn't catch this. And that autopkgtests for d-shlibs aren't failing. Can you also look into why testing didn't prevent this? A workaround or quick solution would be appreciated as it breaks all jobs at https://jenkins.debian.net/view/rebootstrap/. Helmut
Processed: d-shlibs makes libzstd FTBFS: sed: -e expression #89, char 81: Unmatched ( or \(
Processing control commands: > affects -1 + src:libzstd Bug #996012 [d-shlibs] d-shlibs makes libzstd FTBFS: sed: -e expression #89, char 81: Unmatched ( or \( Added indication that 996012 affects src:libzstd -- 996012: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=996012 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#970880: [Pkg-freeipa-devel] Bug#970880: Bug#970880: freeipa-server: FreeIPA server installation fails with Certificate issuance failed (CA_REJECTED)
Cloned nss repo and did a git bisect: the first commit that causes problems is at the upstream merge of 3.39 (upstream/3.39). >From a very brief perusal of the upstream changes, I see there are some edits with respect to TLS1.3--perhaps this is the reason for our problems--I haven't yet looked hard at all the upstream changes (or tried to bisect the upstream repo yet). On Sat, Oct 9, 2021 at 12:05 PM Spencer Olson wrote: > > Since it doesn't look like any progress has been made on this, I've > started to work through some debugging. > > Right now, it looks like the problem is probably actually due to a > change in libnss3. In fact, the problem appears to be specifically in > libssl3.so from the libnss3 package. > > The problem: > * certmonger has a hard time finishing the certificate requests > because it can't seem to authenticate to the dogtag PKI server. > > Observations: > * When certmonger attempts to request a signed certificate for the > renewal agent, it temporarily explicitly uses the ipa-ca-agent > certificate which has been temporarily extracted from the > /root/ca-agent.p12 storage. > * dogtag-submit attempts to use the CURL library to submit the > request, subsequently approve the request, and then poll for its > finish. > * The initial request does not use/require an encrypted channel, but > the approval and subsequent queries do. > * These attempts to authenticate over this encrypted channel using > the client certificate are rejected. > > Hacks & tests: > * By creating a very small c-program that does the same CURL commands > as dogtag-submit from the certmonger package, this same authorization > denied can be seen. > * By simply replacing the libssl3.so library, using either LD_PRELOAD > or LD_LIBRARY_PATH, from a prior version, the requests succeed. As of > now, I've tried only one other version of libssl3.so (libnss3 3.35 > from ubuntu 18.04). > * Also, instead of linking against libcurl-nss and manualy replacing > the libssl3.so library, success can be found by linking to > libcurl-gnutls or libcurl-openssl > > I suspect that a compile option in libnss3 has to be changed in order > for this to work again. > > Still todo: > * I haven't fully discovered which part/option from libnss3 might have > changed. > * I haven't yet successfully had libnss3 emit much > debugging--probably have to recompile with DEBUG=1.
Bug#994595: marked as done (libuser1-dev: Missing dependencies against libglib2.0-dev)
Your message dated Sun, 10 Oct 2021 01:33:54 + with message-id and subject line Bug#994595: fixed in libuser 1:0.63~dfsg-3 has caused the Debian Bug report #994595, regarding libuser1-dev: Missing dependencies against libglib2.0-dev 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.) -- 994595: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=994595 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: libuser1-dev Version: 1:0.62~dfsg-0.4 Severity: serious Tags: bullseye bookworm sid Hello, Looking at the libuser.pc file, it seems that the libuser1-dev is missing a dependency against libglib2.0-dev Could you please add it? Kind regards, Laurent Bigonville -- System Information: Debian Release: bookworm/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'unstable'), (1, 'experimental-debug'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 5.10.0-8-amd64 (SMP w/8 CPU threads) Kernel taint flags: TAINT_WARN Locale: LANG=fr_BE.UTF-8, LC_CTYPE=fr_BE.UTF-8 (charmap=UTF-8), LANGUAGE=fr_BE:fr Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: SELinux: enabled - Mode: Permissive - Policy name: refpolicy --- End Message --- --- Begin Message --- Source: libuser Source-Version: 1:0.63~dfsg-3 Done: Boyuan Yang We believe that the bug you reported is fixed in the latest version of libuser, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 994...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Boyuan Yang (supplier of updated libuser 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 Oct 2021 21:08:42 -0400 Source: libuser Architecture: source Version: 1:0.63~dfsg-3 Distribution: unstable Urgency: medium Maintainer: Boyuan Yang Changed-By: Boyuan Yang Closes: 994595 Changes: libuser (1:0.63~dfsg-3) unstable; urgency=medium . * Upload to unstable. + Really closes: #994595. Checksums-Sha1: b32d8d36c263ce25326b15ee52c62e4ae4a55a09 2179 libuser_0.63~dfsg-3.dsc 8ed6c51e39946f333b1d76b8b17e8fec8b984b5e 359192 libuser_0.63~dfsg.orig.tar.xz a37b9bed66283dd7375810591e31bd69c910eb7f 7164 libuser_0.63~dfsg-3.debian.tar.xz 00ef2dfa4ea34a83b0863f6f6d462981f2eb9db4 9717 libuser_0.63~dfsg-3_amd64.buildinfo Checksums-Sha256: f89430116db5f92e306427b91754c161fab65db89452290a24a319515e03990a 2179 libuser_0.63~dfsg-3.dsc 1cbc26afd631b224a4548e6aa4d7f14f5585838290fb368a2027007c08b3b27a 359192 libuser_0.63~dfsg.orig.tar.xz ad050896ec9c2a9e85f2aa5d95d3ac6d29a77dc70b97894fe117ecc4d60a3b07 7164 libuser_0.63~dfsg-3.debian.tar.xz b13ef64fd1a9bfcdf47a5903a2a502b0bf23ff7200e420572c2deb0af2f6b16e 9717 libuser_0.63~dfsg-3_amd64.buildinfo Files: 0841a672788776259f44991e2426b950 2179 admin optional libuser_0.63~dfsg-3.dsc 38c006a26d208101c3d15926b7122579 359192 admin optional libuser_0.63~dfsg.orig.tar.xz 2f47c85a7e4d85debc69f006d6d3a724 7164 admin optional libuser_0.63~dfsg-3.debian.tar.xz 5fd5eae8c5a5473c6ff2ab22a369a4ac 9717 admin optional libuser_0.63~dfsg-3_amd64.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEfncpR22H1vEdkazLwpPntGGCWs4FAmFiPa0ACgkQwpPntGGC Ws4ftBAAsBDQlnHnIz+HZ43KqSBCcv5zSaXaXIoR8m5hLRVRggti5tBrzvzfX9jU lZk1sorVbED/CqaXU7kCN1CE6iZJspwuOhRPBbTubXz+ZBuqOthXnOOjH+nnhIc7 4UFTtA4LWcrHzq8UUHpef6lPUPs6HBx8maxx2iRfUF9hmAtErNZ1ymt7fMflc7Qm y5R00E8L7yJYBknbHl5fTwxLlRVUO9bt33qX4osXmpfYBvLV5V0oSK4u0DxVhwCQ ytO8POEIos/UH56FYf6Kn9I2dE/gQEsratgiAn3dW1gCJZtbFPB5PF9yaQKOiIXX v6vxp18urW9rX98PnepHUqhgFdCHmWh3EAOJxTkEOZ1h14m6mpoEYwdV5DCPobJx 33axAQtAZj9ZBn1+OzOLRzeOB4L5ujcEY8s6vxRQyE4MpXwq++Kxaj8KWWEzPom/ CyPMQ1GG2aj5DbpXEGEfQ6JTHA2ezPZ9OimoJP4OcX6Ka7TYpPlp8sPHmhOvTJ2E dtbTu6we8Mn30FRGbKwZ5r0h8/3xTAWAAJH91e7ZpVmtjjt0krw086zCQhNJAIMk fXZ5vTGcwTVBZuEKbTuto6Yn8UtrDSrgvuo0KxKf6cBBxtQYTqyB+cZU3FR9qiUT sqH1XqgW7cIrvbTKRXt0QAE6SeKliPBXTUN0+vIFXh+uM6P/yXM= =UYeB -END PGP SIGNATURE End Message ---
Bug#979100: marked as done (Legally problematic GPL-3+ readline dependency)
Your message dated Sat, 09 Oct 2021 23:48:21 + with message-id and subject line Bug#979100: fixed in connman 1.36-2.3 has caused the Debian Bug report #979100, regarding Legally problematic GPL-3+ readline dependency 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.) -- 979100: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=979100 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: connman Severity: important This package depends on libreadline8 which is GPL-3+ licensed. According to debian/copyright parts of your package are GPL-2-only licensed. If that is also (transitively) the case for the binaries that link with libreadline.so.8 it might be legally problematic (see https://www.gnu.org/licenses/gpl-faq.html#AllCompatibility). There is an easy solution to the problem: Replacing the build dependency libreadline-dev with libreadline-gplv2-dev links with the GPL-2+ licensed older version. However, that is orphaned in Debian, so libeditreadline-dev should be preferred, which does not compile with your package without any patch. It links with the BSD-licensed libedit library which is a readline replacement. --- End Message --- --- Begin Message --- Source: connman Source-Version: 1.36-2.3 Done: Ross Vandegrift We believe that the bug you reported is fixed in the latest version of connman, 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 979...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Ross Vandegrift (supplier of updated connman 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 Oct 2021 14:49:52 -0600 Source: connman Architecture: source Version: 1.36-2.3 Distribution: unstable Urgency: medium Maintainer: Alexander Sack Changed-By: Ross Vandegrift Closes: 979100 Changes: connman (1.36-2.3) unstable; urgency=medium . * Non-maintainer upload. * d/copyright: license on client/* is GPL-2+ Upstream commit 27e37a50 relicensed this to GPL-2+ to fix the license incompatibility with GPL-3+ releases of libreadline. (Closes: #979100) Checksums-Sha1: 962a2bb36e71a99e33064e784362691954085776 2016 connman_1.36-2.3.dsc 9a7a901048a1a5715950fca18d5b1772b0e08a69 16628 connman_1.36-2.3.debian.tar.xz 450a48dde37ea538c1d51318e406ffbc9b28ce1b 8017 connman_1.36-2.3_source.buildinfo Checksums-Sha256: 2f28535a8a68f83d49f7b06398f3306e5d2faa858b39ab7b5ae7a283de4449f5 2016 connman_1.36-2.3.dsc 465d830d1a42af7c6e858e2c2079848531537ee3a7c4e4542d2482d45398d594 16628 connman_1.36-2.3.debian.tar.xz 7119118d87a150490ebaa210816217b29def0527eb6cd8745b41c9a0aadedd7d 8017 connman_1.36-2.3_source.buildinfo Files: 0126a9e49dad2c07dbed7c0f24a5f879 2016 net optional connman_1.36-2.3.dsc 842168a7ab08a3e2de4b72f5b8a20a88 16628 net optional connman_1.36-2.3.debian.tar.xz 95fd99a4cfbf31c64c197ad6fc127681 8017 net optional connman_1.36-2.3_source.buildinfo -BEGIN PGP SIGNATURE- iQGzBAEBCgAdFiEEQGIgyLhVKAI3jM5BH1x6i0VWQxQFAmFiJs4ACgkQH1x6i0VW QxTiUwwAwFSBmjpl71t88U08i80T21nJziOnCjrpIt+yb5fX64NIFYI0MwEyY1nu 5fgCNmm5LmjAjDZqXOh2NyPpmxTb13qx7PF5miDPW/r04aIYZLB3ydLDcPMM6Klt PkeHcV+DnO72s7rREZ+tBqd9utAMsYeDVSpKQjk8XZJhYl1yQUG+vfvsCni8jo+Z 1qNkgQC6+bmJVNqDjMjF/UaEKKaa8fTr1SJRXUuiZz3Lj93bgwkMVQncy5ahfDZz dXXEXOxqm4RQQNl0uXEe72JJ08ADu1Sbcs1GMc7eLnFiI3tYnLN1hMyBVLpjeoYs NPXtOaYzaneGZKLRR1bNiFkAlwlFkzHwp/7mwEMuz4kPTUVHPKsgc+F7q8uQIEqN lrH7ig2u0IwSzBkGeVFZ6IXOAW0HlRHF4P69Gfi1VTt7BgIdqVRByXtpm1mDUI3l R/fvbYpOG2H0tqZwroTLI7K8maZVxA2M2cCNo876XY8Njj04on5KBi1QZzv8AjKL WcQtXDMM =b5bS -END PGP SIGNATURE End Message ---
Bug#996005: ca-certificates: fails upgrading when no new certs selected
Package: ca-certificates Version: 20211004 Severity: grave Justification: renders package unusable Hey. It seems that when not selecting any of the new certs on upgrade, the package install fails: Setting up ca-certificates (20211004) ... Updating certificates in /etc/ssl/certs... chmod: cannot access '/etc/ssl/certs/ca-certificates.crt.new': No such file or directory dpkg: error processing package ca-certificates (--configure): installed ca-certificates package post-installation script subprocess returned error exit status 1 It did work though on other systems, where I selected some of the new certs. Cheers, Chris.
Bug#979100: NMU [RC] connman/1.36-2.3
I am sponsoring the NMU with the enclosed debdiff. diff -Nru connman-1.36/debian/changelog connman-1.36/debian/changelog --- connman-1.36/debian/changelog 2021-06-09 20:48:07.0 +0200 +++ connman-1.36/debian/changelog 2021-10-09 22:49:52.0 +0200 @@ -1,3 +1,12 @@ +connman (1.36-2.3) unstable; urgency=medium + + * Non-maintainer upload. + * d/copyright: license on client/* is GPL-2+ +Upstream commit 27e37a50 relicensed this to GPL-2+ to fix the license +incompatibility with GPL-3+ releases of libreadline. (Closes: #979100) + + -- Ross Vandegrift Sat, 09 Oct 2021 14:49:52 -0600 + connman (1.36-2.2) unstable; urgency=high * Non-maintainer upload. diff -Nru connman-1.36/debian/copyright connman-1.36/debian/copyright --- connman-1.36/debian/copyright 2021-06-09 20:44:49.0 +0200 +++ connman-1.36/debian/copyright 2021-10-09 22:49:52.0 +0200 @@ -87,6 +87,10 @@ Copyright: 2004-2011 Marcel Holtmann License: GPL-2+ +Files: client/* +Copyright: 2012-2014 Intel Corporation. All rights reserved. +License: GPL-2+ + License: GPL-2 This program is free software; you can redistribute it and/or modify it under the terms of the GNU General Public License version 2 as
Bug#979100: Legally problematic GPL-3+ readline dependency
On Sat, 9 Oct 2021 16:04:33 -0600 Ross Vandegrift wrote: Upstream relicensed the client source to GPL v2 or later in 27e37a50 specifically to address this issue [1]. That change was released in 1.10, but d/copyright does not reflect it. I've opened an MR with the fix at [2], but need a sponsor to upload since I'm DN. Since the uploader and maintainer have been inactive for some years, and since this bug has had no reply since January, I'll open a sponsorship request bug today. [1] - https://git.kernel.org/pub/scm/network/connman/connman.git/commit/?id=27e37a50f35cc54c266cbd37e32dadbf3016e5e8 [2] - https://salsa.debian.org/debian/connman/-/merge_requests/6 Thank you for pointing that out. I take this as RFS and can sponsor it as-is.
Bug#979100: Legally problematic GPL-3+ readline dependency
Control: tags -1 pending
Hello,
On Sat, 2 Jan 2021 18:47:07 +0100 Bastian Germann wrote:
> This package depends on libreadline8 which is GPL-3+ licensed. According
> to debian/copyright parts of your package are GPL-2-only licensed. If
> that is also (transitively) the case for the binaries that link with
> libreadline.so.8 it might be legally problematic (see
> https://www.gnu.org/licenses/gpl-faq.html#AllCompatibility).
Since enlightenment Build-Depends on connman, I took a look. I think this
isn't actually a problem.
According to the docs, readline is only used in the cli client. I confirmed in
a fresh sid container:
# dpkg -l connman*
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name Version Architecture Description
+++-=-===--===
ii connman 1.36-2.2amd64Intel
Connection Manager daemon
ii connman-dev:amd64 1.36-2.2amd64Development
files for connman
ii connman-doc 1.36-2.2all ConnMan
documentation
ii connman-vpn 1.36-2.2amd64Intel
Connection Manager daemon - VPN daemon
root@b7aa1f65ab2d:/# for i in $(dpkg -l connman* | grep connman | awk '{print
$2}'); do dpkg -L $i | xargs ldd 2> /dev/null | grep -E '(^/)|libreadline';
done | grep -B 1 readline
/usr/bin/connmanctl:
libreadline.so.8 => /lib/x86_64-linux-gnu/libreadline.so.8
(0x7f3b73d8b000)
Upstream relicensed the client source to GPL v2 or later in 27e37a50
specifically to address this issue [1]. That change was released in 1.10, but
d/copyright does not reflect it.
I've opened an MR with the fix at [2], but need a sponsor to upload since I'm
DN. Since the uploader and maintainer have been inactive for some years, and
since this bug has had no reply since January, I'll open a sponsorship request
bug today.
[1] -
https://git.kernel.org/pub/scm/network/connman/connman.git/commit/?id=27e37a50f35cc54c266cbd37e32dadbf3016e5e8
[2] - https://salsa.debian.org/debian/connman/-/merge_requests/6
Ross
Processed: Re: Legally problematic GPL-3+ readline dependency
Processing control commands: > tags -1 pending Bug #979100 [connman] Legally problematic GPL-3+ readline dependency Added tag(s) pending. -- 979100: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=979100 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#995801: marked as done (unrar-free: license missing in upstream and package)
Your message dated Sat, 09 Oct 2021 21:05:59 + with message-id and subject line Bug#995801: fixed in unrar-free 1:0.0.2-0.1 has caused the Debian Bug report #995801, regarding unrar-free: license missing in upstream and package 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.) -- 995801: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=995801 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: unrar-free Severity: serious Version: 1:0.0.1+cvs20140707-4 src/unrar.c says "dos_to_unix_time came from unzip sources." However, unzip's Info-ZIP license requires to copy the license to distributions and it is not available in unrar-free. https://gitlab.com/bgermann/unrar-free/-/commit/457e5a7b6c15f holds a patch with the license text. Please add it to debian/copyright. --- End Message --- --- Begin Message --- Source: unrar-free Source-Version: 1:0.0.2-0.1 Done: Bastian Germann We believe that the bug you reported is fixed in the latest version of unrar-free, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 995...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Bastian Germann (supplier of updated unrar-free 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 Oct 2021 21:30:58 +0200 Source: unrar-free Architecture: source Version: 1:0.0.2-0.1 Distribution: unstable Urgency: medium Maintainer: Ying-Chun Liu (PaulLiu) Changed-By: Bastian Germann Closes: 874065 995065 995801 Changes: unrar-free (1:0.0.2-0.1) unstable; urgency=medium . * Non-maintainer upload. * Change to new upstream (Closes: #874065) * debian/copyright: Add Info-Zip (Closes: #995801) * Drop Debian patches and manpage (contained in new upstream) * Fix CVE-2017-11190 (Closes: #995065) * debian/README.Debian: drop outdated file * Remove outdated pike versions from Suggests * The unar forwarding is dropped upstream, so drop Recommends * Raise debhelper version to 10; 9 is deprecated Checksums-Sha1: 4a792a7739894578f3ab4e34da90d7eeae9b8e78 1689 unrar-free_0.0.2-0.1.dsc e59bc994b8dcc65e93d63ed40d3284fdd029a686 34036 unrar-free_0.0.2.orig.tar.gz d23f2cb44ce000d3e49bf700fcc4c0e1adf966b3 6256 unrar-free_0.0.2-0.1.debian.tar.xz c1d29852a8ca1faa6f453e79ad568206fba3ab8f 5391 unrar-free_0.0.2-0.1_source.buildinfo Checksums-Sha256: e90dc1fbb062fb23cf958d3dc52a6efd5a27ce33b0628b671a208a5917e2b51b 1689 unrar-free_0.0.2-0.1.dsc 47120c037060fa809b88a12657464a9e66a5dd6d17b550e6c5ecaa84a2026a01 34036 unrar-free_0.0.2.orig.tar.gz 02cf0d5acde1fcd87ab5234332e7d9b2ed470d63296110175905fad854dc9f77 6256 unrar-free_0.0.2-0.1.debian.tar.xz ddb6785a55f3f1ca3fda28151fd0ef547994f6b5ef024e24f82f932957fff98b 5391 unrar-free_0.0.2-0.1_source.buildinfo Files: 6a91cee6d703becbe4d4f1e241f3d1ed 1689 utils optional unrar-free_0.0.2-0.1.dsc 048bc12002ebc66627773747f2885cce 34036 utils optional unrar-free_0.0.2.orig.tar.gz 605efafa44d1d1155126f1041dd70192 6256 utils optional unrar-free_0.0.2-0.1.debian.tar.xz bae3c707ac2fd00d9bfc4b88843393d4 5391 utils optional unrar-free_0.0.2-0.1_source.buildinfo -BEGIN PGP SIGNATURE- iQGzBAEBCgAdFiEEQGIgyLhVKAI3jM5BH1x6i0VWQxQFAmFh/H0ACgkQH1x6i0VW QxQlYgwA1iafcPT0tiQf4uZI41xoPwQm5NTyQeIKMhkABFBuC3RP0LI1iwqHzQnL skXezVcdF9MapUT8yWmj+3SbEoK42m3HGl7dGTYIdN0mkfiV5dLho3eDJfW2QwWt OSpCHNU0tza5ig/9fOFI3VI6MLhRX2KFyDwxcKu+7Bq5u7FmYEWodVQrQmGqYb3Z +sMwvwuidzT0pEoEIeTW1AhPwt2FZTGPKmAYt9a8y+0HqunbemCtgD86Whkw4zQb 6q2tpncQ4ZQ90bRcNX72Gag7AzdOfwTdGByeD8kmnzKQ988ZEPs2UXMhdGJBpBjN 24cVtyV4W0k51ewonb7Ksz6vBulf8HLE+hs02bVy5nBspukWMfHHtV2Iuct4CKRZ Mq8TVH2zKibQI6CN3nwn+DXrT/Uc2mLXYHARllff4YqLVhKaZITQUm58aB4yaOcO 9wNQgFH49Obr6lImtaJ+6pJw0P8rFhfu8j6ORuQylzNNF+I0jhKZ+xUm188R9FCs a8WrmTS9 =FM8U -END PGP SIGNATURE End Message ---
Bug#979096: marked as done (Legally problematic GPL-3+ readline dependency)
Your message dated Sat, 09 Oct 2021 18:48:27 + with message-id and subject line Bug#979096: fixed in omake 0.10.3-2.1 has caused the Debian Bug report #979096, regarding Legally problematic GPL-3+ readline dependency 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.) -- 979096: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=979096 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: omake Severity: important This package depends on libreadline8 which is GPL-3+ licensed. According to debian/copyright parts of your package are GPL-2-only licensed. If that is also (transitively) the case for the binaries that link with libreadline.so.8 it might be legally problematic (see https://www.gnu.org/licenses/gpl-faq.html#AllCompatibility). There is an easy solution to the problem: Replacing the build dependency libreadline-dev with libeditreadline-dev links with the BSD-licensed libedit library which is a readline replacement. --- End Message --- --- Begin Message --- Source: omake Source-Version: 0.10.3-2.1 Done: Bastian Germann We believe that the bug you reported is fixed in the latest version of omake, 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 979...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Bastian Germann (supplier of updated omake 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 Oct 2021 20:02:08 +0200 Source: omake Architecture: source Version: 0.10.3-2.1 Distribution: unstable Urgency: medium Maintainer: Debian OCaml Maintainers Changed-By: Bastian Germann Closes: 979096 Changes: omake (0.10.3-2.1) unstable; urgency=medium . * Non-maintainer upload. * Build with libedit instead of libreadline (Closes: #979096) Checksums-Sha1: aaea664110b738390fd335ae4f4f513c8683567d 1836 omake_0.10.3-2.1.dsc 8e1cc86e21a91a263c9354561c12a83980563424 5324 omake_0.10.3-2.1.debian.tar.xz b23894e1d1ab66930a1f0edd53a1b8416cc880d7 5850 omake_0.10.3-2.1_source.buildinfo Checksums-Sha256: 5c96fff5be4352f8ae9d0705bed8a9ba69fc75982df7d977027cf87318110518 1836 omake_0.10.3-2.1.dsc 6ba6c8402072d0c3cba8d4275185b213465c30994f8f91052a3d4a9e65e16839 5324 omake_0.10.3-2.1.debian.tar.xz 12efed6dcd2ae03e1f638ed254eaccec9b3987bea9ea462c3d6a6681249ab4b8 5850 omake_0.10.3-2.1_source.buildinfo Files: 2d0c132dd5489fc64b5fa1c20271dfb0 1836 ocaml optional omake_0.10.3-2.1.dsc 2d39af2fa35ff03591c9db0c157f3d25 5324 ocaml optional omake_0.10.3-2.1.debian.tar.xz adf69ecc5c13a83f2989db90c0c7f261 5850 ocaml optional omake_0.10.3-2.1_source.buildinfo -BEGIN PGP SIGNATURE- iQGzBAEBCgAdFiEEQGIgyLhVKAI3jM5BH1x6i0VWQxQFAmFh24YACgkQH1x6i0VW QxQ+twv9HB9CDhpbYWwuivb3VGmdRqViWXEclWohMgbs5s5me96C3xnl3OBp31KY Y27DNIOpemViUgHwhT41ZUBOHbtYojI4SmgI2CXo5/XltDZ/PBhk8V6yoUiy/y3P /xsTXZ6GsjJQ0AzCpiPLACPKHrHV7DVhcCPI+zjcCrlbn+q3oQVQiYe4JgsDlMQe atLiHvdLsYHLmmV3iOYH6SMmAkXa0ueqedYF/rMx3xQxXGDoX7pTrGjFjjksbPql QY+xnyXe3hTYJsC9LLJa7jHJYeWcYq3DPMq453LNMNuQ+cyDRPEmG1eiDzBKlf6D NNoBr5njNQwIgkRHc5MOTJRY5FjiDl5zI6askqIoFwdHgf/XPQiCzMUY6u1bfER/ QE0kuN37ZQm0ON5cG70o1fu4kpBY0ittkREkYfJJaew9sUSWcjkt1mjJbEo1Vto2 ar1+V3AFjKOgWrJQVpwzwN15R38iATMZ44NhKrnqrQD48QqCK/fhp/omsYBYjF2e itDeT2Il =IN/2 -END PGP SIGNATURE End Message ---
Processed: bug 995999 is forwarded to https://github.com/prometheus/prometheus/issues/8403
Processing commands for cont...@bugs.debian.org: > forwarded 995999 https://github.com/prometheus/prometheus/issues/8403 Bug #995999 [prometheus] FTBFS: FAIL: TestChunkDiskMapper_WriteChunk_Chunk_IterateChunks Set Bug forwarded-to-address to 'https://github.com/prometheus/prometheus/issues/8403'. > thanks Stopping processing here. Please contact me if you need assistance. -- 995999: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=995999 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#995999: FTBFS: FAIL: TestChunkDiskMapper_WriteChunk_Chunk_IterateChunks
Package: prometheus Version: 2.24.1+ds-1 Severity: serious X-Debbugs-Cc: z...@debian.org Hi, When rebuild packages, I find it FTBFS. === RUN TestChunkDiskMapper_WriteChunk_Chunk_IterateChunks --- FAIL: TestChunkDiskMapper_WriteChunk_Chunk_IterateChunks (0.05s) panic: runtime error: slice bounds out of range [:104326] with capacity 104293 [recovered] panic: runtime error: slice bounds out of range [:104326] with capacity 104293 goroutine 7 [running]: testing.tRunner.func1.2(0x60da60, 0xc0005f8030) /usr/lib/go-1.16/src/testing/testing.go:1143 +0x332 testing.tRunner.func1(0xc01e00) /usr/lib/go-1.16/src/testing/testing.go:1146 +0x4b6 panic(0x60da60, 0xc0005f8030) /usr/lib/go-1.16/src/runtime/panic.go:965 +0x1b9 github.com/prometheus/prometheus/tsdb/chunks.TestChunkDiskMapper_WriteChunk_Chunk_IterateChunks(0xc01e00) /build/1st/prometheus-2.24.1+ds/build/src/github.com/prometheus/prometheus/tsdb/chunks/head_chunks_test.go:122 +0xc9c testing.tRunner(0xc01e00, 0x637600) /usr/lib/go-1.16/src/testing/testing.go:1193 +0xef created by testing.(*T).Run /usr/lib/go-1.16/src/testing/testing.go:1238 +0x2b3 FAILgithub.com/prometheus/prometheus/tsdb/chunks0.116s It also FTBFS on tests.reproducible-builds.org, ci.debian.net https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/prometheus.html https://ci.debian.net/data/autopkgtest/unstable/amd64/p/prometheus/15535224/log.gz
Bug#979096: Legally problematic GPL-3+ readline dependency
I intend to NMU the package. The debdiff is enclosed. diff -Nru omake-0.10.3/debian/changelog omake-0.10.3/debian/changelog --- omake-0.10.3/debian/changelog 2021-02-01 21:59:49.0 +0100 +++ omake-0.10.3/debian/changelog 2021-10-09 20:02:08.0 +0200 @@ -1,3 +1,10 @@ +omake (0.10.3-2.1) unstable; urgency=medium + + * Non-maintainer upload. + * Build with libedit instead of libreadline (Closes: #979096) + + -- Bastian Germann Sat, 09 Oct 2021 20:02:08 +0200 + omake (0.10.3-2) unstable; urgency=medium * Team upload. diff -Nru omake-0.10.3/debian/control omake-0.10.3/debian/control --- omake-0.10.3/debian/control 2021-02-01 21:56:49.0 +0100 +++ omake-0.10.3/debian/control 2021-10-09 20:00:57.0 +0200 @@ -7,7 +7,7 @@ Build-Depends: debhelper-compat (= 13), ocaml-nox, - libreadline-dev, + libeditreadline-dev, libncurses5-dev, dh-ocaml Standards-Version: 4.5.0
Bug#970880: [Pkg-freeipa-devel] Bug#970880: Bug#970880: freeipa-server: FreeIPA server installation fails with Certificate issuance failed (CA_REJECTED)
Since it doesn't look like any progress has been made on this, I've started to work through some debugging. Right now, it looks like the problem is probably actually due to a change in libnss3. In fact, the problem appears to be specifically in libssl3.so from the libnss3 package. The problem: * certmonger has a hard time finishing the certificate requests because it can't seem to authenticate to the dogtag PKI server. Observations: * When certmonger attempts to request a signed certificate for the renewal agent, it temporarily explicitly uses the ipa-ca-agent certificate which has been temporarily extracted from the /root/ca-agent.p12 storage. * dogtag-submit attempts to use the CURL library to submit the request, subsequently approve the request, and then poll for its finish. * The initial request does not use/require an encrypted channel, but the approval and subsequent queries do. * These attempts to authenticate over this encrypted channel using the client certificate are rejected. Hacks & tests: * By creating a very small c-program that does the same CURL commands as dogtag-submit from the certmonger package, this same authorization denied can be seen. * By simply replacing the libssl3.so library, using either LD_PRELOAD or LD_LIBRARY_PATH, from a prior version, the requests succeed. As of now, I've tried only one other version of libssl3.so (libnss3 3.35 from ubuntu 18.04). * Also, instead of linking against libcurl-nss and manualy replacing the libssl3.so library, success can be found by linking to libcurl-gnutls or libcurl-openssl I suspect that a compile option in libnss3 has to be changed in order for this to work again. Still todo: * I haven't fully discovered which part/option from libnss3 might have changed. * I haven't yet successfully had libnss3 emit much debugging--probably have to recompile with DEBUG=1.
Bug#993198: marked as done (gnome-shell-extension-system-monitor: does not declare compatibility with GNOME Shell 40)
Your message dated Sat, 09 Oct 2021 18:03:31 + with message-id and subject line Bug#993198: fixed in gnome-shell-extension-system-monitor 40-1 has caused the Debian Bug report #993198, regarding gnome-shell-extension-system-monitor: does not declare compatibility with GNOME Shell 40 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.) -- 993198: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=993198 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: gnome-shell-extension-system-monitor Version: 38+git20200414-32cc79e-1 Severity: important Tags: fixed-upstream The metadata.json for this extension doesn't declare compatibility with GNOME 40. This seems to have been fixed in upstream git, along with preferences UI changes to make it work in GNOME 40. In many versions of GNOME Shell this didn't matter much, because validation of extensions' metadata against the installed Shell version was disabled by default, but in GNOME 40 the default has changed back to enabling the version check by default, in an effort to avoid issues caused by outdated extensions remaining enabled. When we do the GNOME 40 transition, hopefully soon, we will have to either update this extension or remove it from testing. It would be useful to get a fixed version into experimental. Would you mind adding the GNOME team to Uploaders so we can "officially" do team-uploads? I think that'd be useful for future transitions. Thanks, smcv --- End Message --- --- Begin Message --- Source: gnome-shell-extension-system-monitor Source-Version: 40-1 Done: Samuel Henrique We believe that the bug you reported is fixed in the latest version of gnome-shell-extension-system-monitor, 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 993...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Samuel Henrique (supplier of updated gnome-shell-extension-system-monitor 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 Oct 2021 18:24:00 +0100 Source: gnome-shell-extension-system-monitor Architecture: source Version: 40-1 Distribution: unstable Urgency: medium Maintainer: Jonathan Carter Changed-By: Samuel Henrique Closes: 993198 Changes: gnome-shell-extension-system-monitor (40-1) unstable; urgency=medium . [ Marco Trevisan (Treviño) ] * [36390636] debian/control: Remove useless dependency on clutter gir . [ Leo Antunes ] * convert repo to git-buildpackage * [7c7b70bc] New upstream version 40 (Closes: #993198) . [ Samuel Henrique ] * Bump to DH 13 * Bump Standards-Version to 4.6.0 * Add myself as an uploader Checksums-Sha1: bc6c2104a658aa50779cef59c27f8bc706938849 2257 gnome-shell-extension-system-monitor_40-1.dsc ab3e4738699d423624bcf0cbe48187d0759f403c 114897 gnome-shell-extension-system-monitor_40.orig.tar.gz d2a2112fe8c8455ac2c13f7436526190dbb10ef7 3740 gnome-shell-extension-system-monitor_40-1.debian.tar.xz 7daa14d14f923d14992071d2c48d1a1450d3f323 6191 gnome-shell-extension-system-monitor_40-1_amd64.buildinfo Checksums-Sha256: b447e798410b0204fbd31f6652f8771afbbb951cc21137f50a9972332094fc71 2257 gnome-shell-extension-system-monitor_40-1.dsc 73b6075dbae785ffe0d3657eba406e3759ef338b354633b84fee9d1cf857b566 114897 gnome-shell-extension-system-monitor_40.orig.tar.gz 06e20a11d17f158ed4dab71f0ea8ff0f71c8d2c76088bc638529729d033bbf8e 3740 gnome-shell-extension-system-monitor_40-1.debian.tar.xz 100eab5284b78b179e59b3f761915ab91b8846fdd03d092254735f5426a6a324 6191 gnome-shell-extension-system-monitor_40-1_amd64.buildinfo Files: 6520471378bcf2c6ab98ae1cb08f9026 2257 gnome optional gnome-shell-extension-system-monitor_40-1.dsc 46bd1ed56fe94c82240e99a08c543462 114897 gnome optional gnome-shell-extension-system-monitor_40.orig.tar.gz 5a6a8aa5286b3022d1628380e927120f 3740 gnome optional gnome-shell-extension-system-monitor_40-1.debian.tar.xz b5ed4c7386b6a8b236392323889e3216 6191 gnome optional gnome-shell-extension-system-monitor_40-1_amd64.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEBdtqg34QX0sdAsVfu6n6rcz7RwcFAmFh0FoACgkQu6n6rcz7 RwdGbRAAtHFGKS/NBj8tT85IRY1FJ6u7IFDcu2Yd
Bug#993198: gnome-shell-extension-system-monitor: does not declare compatibility with GNOME Shell 40
Hello Leo, > Just pushed to the main repo. Please take a look and let me know if it works! It works nicely! I have committed a few more changes, pushed it and uploaded the package. I noticed you didn't add yourself to the Uploaders field and I didn't do it because I didn't know if you wanted that. But please feel free to do so if that's your intention. Thank you! -- Samuel Henrique
Processed: tagging 995851
Processing commands for cont...@bugs.debian.org: > tags 995851 + sid Bug #995851 [src:qcelemental] FTBFS: tests fail with new pydantic Added tag(s) sid. > thanks Stopping processing here. Please contact me if you need assistance. -- 995851: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=995851 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Re: Bug#995851: qcelemental: please package latest upstream release
Processing control commands: > severity -1 serious Bug #995851 [src:qcelemental] qcelemental: please package latest upstream release Severity set to 'serious' from 'important' > tags -1 + ftbfs upstream fixed-upstream Bug #995851 [src:qcelemental] qcelemental: please package latest upstream release Added tag(s) fixed-upstream, ftbfs, and upstream. > found -1 0.17.0+dfsg-3 Bug #995851 [src:qcelemental] qcelemental: please package latest upstream release Marked as found in versions qcelemental/0.17.0+dfsg-3. > retitle -1 FTBFS: tests fail with new pydantic Bug #995851 [src:qcelemental] qcelemental: please package latest upstream release Changed Bug title to 'FTBFS: tests fail with new pydantic' from 'qcelemental: please package latest upstream release'. -- 995851: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=995851 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#995970: marked as done (lshw: misses changes from 02.18.85-0.6 & 02.18.85-0.7)
Your message dated Sat, 09 Oct 2021 14:37:36 + with message-id and subject line Bug#995970: fixed in lshw 02.19.git.2021.06.19.996aaad9c7-2 has caused the Debian Bug report #995970, regarding lshw: misses changes from 02.18.85-0.6 & 02.18.85-0.7 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.) -- 995970: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=995970 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: lshw Version: 02.19.git.2021.06.19.996aaad9c7-1 Severity: serious Justification: reverts past changes X-Debbugs-Cc: z...@debian.org Hi, the upload of lshw 02.19.git.2021.06.19.996aaad9c7-1 was done starting from 02.18.85-0.5, meaning that neither 02.18.85-0.6 nor 02.18.85-0.7 are acknowledged: - 02.18.85-0.6 contains Debian-only changes that indeed need to be applied - 02.18.85-0.7 contains the backport of a 2 years old upstream commit, which might be already contained in the packaged Git snapshot Please include them both, acknowledging them in changelog. Thanks, -- Pino --- End Message --- --- Begin Message --- Source: lshw Source-Version: 02.19.git.2021.06.19.996aaad9c7-2 Done: Thomas Goirand We believe that the bug you reported is fixed in the latest version of lshw, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 995...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Thomas Goirand (supplier of updated lshw 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 Oct 2021 16:13:40 +0200 Source: lshw Architecture: source Version: 02.19.git.2021.06.19.996aaad9c7-2 Distribution: unstable Urgency: medium Maintainer: Ghe Rivero Changed-By: Thomas Goirand Closes: 995970 Changes: lshw (02.19.git.2021.06.19.996aaad9c7-2) unstable; urgency=medium . * ACK 02.18.85-0.6 and 02.18.85-0.7 upload and apply the changes that were not there in previous upload (Closes: #995970). The upstream backported patch 0001-fix-755-handle-invalid-FAT.patch is now applied upstream and therefore, removed from d/patches. Checksums-Sha1: dc918fef41a1782f7d7837d62610b0ac798a1e4f 2118 lshw_02.19.git.2021.06.19.996aaad9c7-2.dsc 46fd458f6547258917d306a23ed6c8f2879b169f 17604 lshw_02.19.git.2021.06.19.996aaad9c7-2.debian.tar.xz f43cef3d9247e31e4b2f8418dddefaf4240039eb 14461 lshw_02.19.git.2021.06.19.996aaad9c7-2_amd64.buildinfo Checksums-Sha256: ff66f98069bc95d7d65f75b1b5bc68e57eb1815955cee21c43b3f90d88caa894 2118 lshw_02.19.git.2021.06.19.996aaad9c7-2.dsc 64ad3599a94c6a093868ee0b867beeec998e19f3793ba76eb3a5092bbae0b9b7 17604 lshw_02.19.git.2021.06.19.996aaad9c7-2.debian.tar.xz 390bc34f16922d6ad15777a1a1e5dedccee75a13b7d51121f9935299dab142cb 14461 lshw_02.19.git.2021.06.19.996aaad9c7-2_amd64.buildinfo Files: 56c7c2d2b6a9827b50bb9c20e7358736 2118 utils optional lshw_02.19.git.2021.06.19.996aaad9c7-2.dsc 9d1a4478ed2b4c06b99a2e8eb6563bb5 17604 utils optional lshw_02.19.git.2021.06.19.996aaad9c7-2.debian.tar.xz d5282f7730317c88c3937e5a236fc58b 14461 utils optional lshw_02.19.git.2021.06.19.996aaad9c7-2_amd64.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEEoLGp81CJVhMOekJc1BatFaxrQ/4FAmFhpdMACgkQ1BatFaxr Q/4SUw/+JJnUhIIkD4s/r5TYfGbECulHz5JsVLH0waojrpaCzCmqE1yF4zK4CjI7 drNHOx/9Y9BzkDflGdWQ1WZdtLfnwEd8qkY8KfK2OqSbmiE5tjdyvZaRUF1C92V3 HUX8FptczPRwAyI6i7th8mPSBxoNxluBguoH1+rx6uopTD+MaS3O2UzeTeYn/bug e5XZx79Vu7DWWRaildJsqVv18b3WvqiOL44JUrTj/JwwhvMWp49O/7ykOLZ+iuwG J+AxA3fuf0qrWqjo5jUaq28SfoDh8D4bkIxJWXBS6SCskqu7hmrHY6nUxGweMsN7 sysChtN7XuBrh7sz7T3+9cdx+H2r+GSXT0+OJuuAVUMJPs9tyjRpdGdMapP/8eDj W+eoomBs1GFC+05+0bO/jg1PGvQjidS2qw/+wn6uc3mxEOEXe8CY/L05VHlNRnnZ 37xfWxxT+UPLvTHgkxaJP71Qxklx9ufbQy0H6Eo8s/ae5RjbIQ6mLC94Bh5hl/rp BXlA6t4nUM5vOkhXSEChJ5AHHYvAzhG8RsNVaelBTHQpJicYKkThuNpRjdz5I43+ W20jubNQxULnLBN5c283rex4bBnzMOu3zWRniOb4f79J4Aj8bhdnVeL/xLQsJY6m ec/V2G1HYu/8e5+QjHXmGKGX1xSUOidEbPwrqJcHL4XwyO8hNM4= =LPIg -END PGP SIGNATURE End Message ---
Bug#995952: undertime: Getting TypeError with any timezone
Control: severity -1 normal On 2021-10-08 15:24:56, Gabriel Filion wrote: > Package: undertime > Version: 2.6.0 > Severity: grave > Justification: renders package unusable > > Hello, > > I'm currently getting stack traces consistently when using undertime. No > matter > the timezone that I request, I get a stack trace with a TypeError exception: > > $ undertime pt > Traceback (most recent call last): > File "/usr/bin/undertime", line 994, in > main(args) > File "/usr/bin/undertime", line 733, in main > timezones += filter(None, [guess_zone(z) for z in args.timezones]) > TypeError: 'NoneType' object is not iterable > > $ undertime PST > WARNING: date provided cannot be parsed: PST > Traceback (most recent call last): > File "/usr/bin/undertime", line 994, in > main(args) > File "/usr/bin/undertime", line 733, in main > timezones += filter(None, [guess_zone(z) for z in args.timezones]) > TypeError: 'NoneType' object is not iterable > > If I run that last command with pdb, > > e.g. python3 -m pdb /usb/bin/undertime PST > > and then (r)un the program until the error, I can see that args.timezones is > set to None: > > (Pdb) type(args.timezones) > > > > now from there, I tried using "undertime -t PST" and that actually worked. So > there must be something off with the default value to -t I should have documented this possibly more clearly in the NEWS.Debian file, or maybe make a 3.x release, but I changed the semantics of the commandline arguments quite significantly. The arguments are now a time, and you need to provide a -t (or add it to your config file) for undertime to work. I'll take this bug report as a request to improve the error message and/or data structure. Really, args.timezones should be an empty list instead of None here, I think. A. -- L'homme construit des maisons parce qu'il est vivant, mais il écrit des livres parce qu'il se sait mortel. - Daniel Pennac, Comme un roman
Processed: Re: Bug#995952: undertime: Getting TypeError with any timezone
Processing control commands: > severity -1 normal Bug #995952 [undertime] undertime: Getting TypeError with any timezone Severity set to 'normal' from 'grave' -- 995952: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=995952 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#995971: marked as done (after upgrade to 6.4, polkit authentication doesn't work any more)
Your message dated Sat, 09 Oct 2021 13:18:30 + with message-id and subject line Bug#995971: fixed in brltty 6.4-2 has caused the Debian Bug report #995971, regarding after upgrade to 6.4, polkit authentication doesn't work any more 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.) -- 995971: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=995971 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: brltty-x11 Version: 6.4-1 Severity: normal Dear Maintainer, *** Reporter, please consider answering these questions, where appropriate *** * What led up to the situation? Upgraded to 6.4 from sid * What exactly did you do (or not do) that was effective (or ineffective)? The brltty packages upgraded and restarted * What was the outcome of this action? The screen under X is no longer displayed * What outcome did you expect instead? After investigating, it seems the /etc/brlapi.key has no longer read permission for group and others, which have no permission at all. ONly root has all perm. As a consequence, of course, the user has no braille under X. *** End of the template - remove these template lines *** Regards -- System Information: Debian Release: bookworm/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'buildd-experimental'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.14.0-1-amd64 (SMP w/4 CPU threads) Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages brltty-x11 depends on: ii brltty 6.4-1 ii libatspi2.0-0 2.42.0-1 ii libc6 2.32-4 ii libdbus-1-31.12.20-2 ii libx11-6 2:1.7.2-2+b1 ii libxaw72:1.0.13-1.1 ii libxfixes3 1:5.0.3-2 ii libxt6 1:1.2.0-1 Versions of packages brltty-x11 recommends: ii xbrlapi 6.4-1 brltty-x11 suggests no packages. -- no debconf information --- End Message --- --- Begin Message --- Source: brltty Source-Version: 6.4-2 Done: Samuel Thibault We believe that the bug you reported is fixed in the latest version of brltty, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 995...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Samuel Thibault (supplier of updated brltty 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 Oct 2021 14:54:01 +0200 Source: brltty Architecture: source Version: 6.4-2 Distribution: unstable Urgency: medium Maintainer: Debian Accessibility Team Changed-By: Samuel Thibault Closes: 995971 Changes: brltty (6.4-2) unstable; urgency=medium . * patches/socket-permissions: Fix BrlAPI socket permissions (Closes: Bug#995971) Checksums-Sha1: 9eb50050bb5492dd74874416458fe0c83cb266ab 3298 brltty_6.4-2.dsc 329249a48f1c9e5ff2996d957ba91850820cee05 35708 brltty_6.4-2.debian.tar.xz 7ea0db5559255ca83b135c2861483354a25661d2 17655 brltty_6.4-2_amd64.buildinfo Checksums-Sha256: 4b690a0b54b55bdd8a43d4ddeae90919bef3c1916534a9e4f4cac0e0994253d8 3298 brltty_6.4-2.dsc dfee04f58bdf8cd00eea260f7b0f86209029d3226aa13e850f12ac7e2097e3a7 35708 brltty_6.4-2.debian.tar.xz c5735ed03402212db5638ff0a5665046b52bca3c7db45f25821d960f67433dba 17655 brltty_6.4-2_amd64.buildinfo Files: 7344eab45127c6bc616ac627dd641926 3298 admin optional brltty_6.4-2.dsc 263da48449cbc405d02d76adac487659 35708 admin optional brltty_6.4-2.debian.tar.xz 80653df5b285e81f011d36107d4a34e5 17655 admin optional brltty_6.4-2_amd64.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEE59DSENomQIYa2nfqRdTszGSEm3kFAmFhkc4ACgkQRdTszGSE m3kTpg/9GKfRCfOFwKjlzREMWuBEKZehJk8xyJRVEF7eLzq561Y49daigkANPr3Q AJqNHlmMUzwTKRKKtKAZ4QdFKZ0fnuINiiwgcstAquXgOZzqNX9lbxCbvMJhBD0x 0hEC7Ms0xBnPKuFfrqkfF7gS88Tf9lI23adufQSTKlLZnMltKipdgJBti0m3YhcV TRszbYELG0gudlZBcHfJ4dE39K5A9Bq5DR4qEONYCTY7+kLuRPThHXZVqtIEs9YB 8yliM7p4fIOwYRwcV4gr8lu/DA7pOAE9FUMzgp/M2DP74/mUl3cu7z7ZugtTAez2 L1trk2ux157NvJAMImj478Ugzxwg+ZKauZUY+uit1KNAW8SodwUFw0nAG18zaNw
Bug#995781: [Debian-med-packaging] Bug#995781: python-sqlsoup autopkgtest fails with SQLAlchemy 1.4.23+ds1-2
Hi Mike, Hi Thomas, Mike Bayer, on 2021-10-08: > you woujld have better luck changing epigrass to use automap instead: > https://docs.sqlalchemy.org/en/14/orm/extensions/automap.html Thanks Mike for your recommendation! This is very useful for me and others who might stumble on this bug entry. Thomas, when trying to see whether epigrass could easily be ported away of sqlsoup, I ended up with other issues documented in bug #995966. I don't know how much time is of the essence to you, but I don't expect a timely resolution of the issues at play. A reasonable course of action might be to drop epigrass and python-sqlsoup of Testing sooner than later, for the time being. What do you think? Kind Regards, -- Étienne Mollier Fingerprint: 8f91 b227 c7d6 f2b1 948c 8236 793c f67e 8f0d 11da Sent from /dev/pts/2, please excuse my verbosity. signature.asc Description: PGP signature
Bug#995966: epigrass: epirunner and epidash fail to run due to missing dash modules
Package: epigrass
Version: 3.0.0+dfsg-1
Severity: grave
Justification: renders package unusable
Dear Maintainer,
When investigating #995781 to see whether sqlsoup could be
replaced by automap, per sqlsoup upstream suggestion since
their program is not maintained anymore, I realised I couldn't
run epigrass related programs at all. The epidash program
crashes with:
$ epidash
Traceback (most recent call last):
File "/usr/bin/epidash", line 33, in
sys.exit(load_entry_point('epigrass==3.0', 'console_scripts',
'epidash')())
File "/usr/bin/epidash", line 25, in importlib_load_entry_point
return next(matches).load()
File "/usr/lib/python3.9/importlib/metadata.py", line 77, in load
module = import_module(match.group('module'))
File "/usr/lib/python3.9/importlib/__init__.py", line 127, in
import_module
return _bootstrap._gcd_import(name[level:], package, level)
File "", line 1030, in _gcd_import
File "", line 1007, in _find_and_load
File "", line 986, in
_find_and_load_unlocked
File "", line 680, in _load_unlocked
File "", line 850, in
exec_module
File "", line 228, in
_call_with_frames_removed
File "/usr/lib/python3/dist-packages/Epigrass/epidash.py", line 1, in
import dash
ModuleNotFoundError: No module named 'dash'
The epirunner program fails to execute anything meaningul, even
the -h flag to get help:
$ epirunner -h
Traceback (most recent call last):
File "/usr/bin/epirunner", line 33, in
sys.exit(load_entry_point('epigrass==3.0', 'console_scripts',
'epirunner')())
File "/usr/bin/epirunner", line 25, in importlib_load_entry_point
return next(matches).load()
File "/usr/lib/python3.9/importlib/metadata.py", line 77, in load
module = import_module(match.group('module'))
File "/usr/lib/python3.9/importlib/__init__.py", line 127, in
import_module
return _bootstrap._gcd_import(name[level:], package, level)
File "", line 1030, in _gcd_import
File "", line 1007, in _find_and_load
File "", line 986, in
_find_and_load_unlocked
File "", line 680, in _load_unlocked
File "", line 850, in
exec_module
File "", line 228, in
_call_with_frames_removed
File "/usr/lib/python3/dist-packages/Epigrass/manager.py", line 20,
in
from Epigrass.simobj import graph, edge, siteobj
File "/usr/lib/python3/dist-packages/Epigrass/simobj.py", line 19, in
from Epigrass import epimodels
File "/usr/lib/python3/dist-packages/Epigrass/epimodels.py", line 15,
in
import numba
File "/usr/lib/python3/dist-packages/numba/__init__.py", line 19, in
from numba.core import config
File "/usr/lib/python3/dist-packages/numba/core/config.py", line 16,
in
import llvmlite.binding as ll
File "/usr/lib/python3/dist-packages/llvmlite/binding/__init__.py",
line 4, in
from .dylib import *
File "/usr/lib/python3/dist-packages/llvmlite/binding/dylib.py", line
3, in
from llvmlite.binding import ffi
File "/usr/lib/python3/dist-packages/llvmlite/binding/ffi.py", line
137, in
from pkg_resources import resource_filename
File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line
3243, in
def _initialize_master_working_set():
File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line
3226, in _call_aside
f(*args, **kwargs)
File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line
3255, in _initialize_master_working_set
working_set = WorkingSet._build_master()
File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line
568, in _build_master
ws.require(__requires__)
File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line
886, in require
needed = self.resolve(parse_requirements(requirements))
File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line
772, in resolve
raise DistributionNotFound(req, requirers)
pkg_resources.DistributionNotFound: The 'dash_html_components'
distribution was not found and is required by epigrass
On the good news side, past in the docs/source/install.rst file,
which is merely for informational purpose, I haven't seen any
reference to sqlsoup in the source code, so removing dependency
to python3-sqlsoup shouldn't be too much of a problem hopefully.
I see stubs of packaging for dash python modules [1, 2, 3] on
salsa, and will have some spare cycles this weekend to have a
fresh look at them if that helps.
[1]: https://salsa.debian.org/med-team/python-dash
[2]: https://salsa.debian.o
Bug#995979: pamix FTBFS: error: format not a string literal and no format arguments [-Werror=format-security]
Source: pamix
Version: 1.6~git20180112.ea4ab3b-3
Severity: serious
Tags: ftbfs
pamix fails to build from source in unstable on amd64, because ncurses
added format string annotations to some functions. A non-parallel build
now ends as follows:
| [ 53%] Building CXX object CMakeFiles/pamix.dir/src/pamix_ui.cpp.o
| /usr/bin/c++ -DFEAT_UNICODE -I"/<>/include" -g -O2
-ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat
-Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -std=gnu++11 -MD -MT
CMakeFiles/pamix.dir/src/pamix_ui.cpp.o -MF
CMakeFiles/pamix.dir/src/pamix_ui.cpp.o.d -o
CMakeFiles/pamix.dir/src/pamix_ui.cpp.o -c "/<>/src/pamix_ui.cpp"
| /<>/src/pamix_ui.cpp: In member function ‘void
pamix_ui::redrawAll()’:
| /<>/src/pamix_ui.cpp:106:52: error: format not a string literal
and no format arguments [-Werror=format-security]
| 106 | mvprintw(lineNumber++, 1, applicationName.c_str());
| |^
| /<>/src/pamix_ui.cpp:124:64: error: format not a string literal
and no format arguments [-Werror=format-security]
| 124 | mvprintw(curY, curX + remainingChars + 1, displayName.c_str());
| |^
| /<>/src/pamix_ui.cpp: In member function ‘void
pamix_ui::drawHeader() const’:
| /<>/src/pamix_ui.cpp:187:22: warning: format ‘%d’ expects
argument of type ‘int’, but argument 5 has type ‘std::map >::size_type’ {aka ‘long unsigned int’} [-Wformat=]
| 187 | mvprintw(0, 1, "%d/%d", m_Entries->empty() ? 0 : m_SelectedEntry +
1, m_Entries->size());
| | ~^
~
| | |
|
| | int
std::map >::size_type {aka
long unsigned int}
| | %ld
| cc1plus: some warnings being treated as errors
| make[3]: *** [CMakeFiles/pamix.dir/build.make:163:
CMakeFiles/pamix.dir/src/pamix_ui.cpp.o] Error 1
| make[3]: Leaving directory '/<>/obj-x86_64-linux-gnu'
| make[2]: *** [CMakeFiles/Makefile2:86: CMakeFiles/pamix.dir/all] Error 2
| make[2]: Leaving directory '/<>/obj-x86_64-linux-gnu'
| make[1]: *** [Makefile:139: all] Error 2
| make[1]: Leaving directory '/<>/obj-x86_64-linux-gnu'
| dh_auto_build: error: cd obj-x86_64-linux-gnu && make -j1 "INSTALL=install
--strip-program=true" VERBOSE=1 returned exit code 2
| make: *** [debian/rules:7: build] Error 25
| dpkg-buildpackage: error: debian/rules build subprocess returned exit status 2
Helmut
Processed: Re: Bug#995971: brltty-x11: After upgrade to 6.4, /etc/brlapi.key removes the read permission for users other than root
Processing control commands: > retitle -1 after upgrade to 6.4, polkit authentication doesn't work any more Bug #995971 [brltty-x11] brltty-x11: After upgrade to 6.4, /etc/brlapi.key removes the read permission for users other than root Changed Bug title to 'after upgrade to 6.4, polkit authentication doesn't work any more' from 'brltty-x11: After upgrade to 6.4, /etc/brlapi.key removes the read permission for users other than root'. > severity -1 grave Bug #995971 [brltty-x11] after upgrade to 6.4, polkit authentication doesn't work any more Severity set to 'grave' from 'normal' -- 995971: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=995971 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#995970: lshw: misses changes from 02.18.85-0.6 & 02.18.85-0.7
Source: lshw Version: 02.19.git.2021.06.19.996aaad9c7-1 Severity: serious Justification: reverts past changes X-Debbugs-Cc: z...@debian.org Hi, the upload of lshw 02.19.git.2021.06.19.996aaad9c7-1 was done starting from 02.18.85-0.5, meaning that neither 02.18.85-0.6 nor 02.18.85-0.7 are acknowledged: - 02.18.85-0.6 contains Debian-only changes that indeed need to be applied - 02.18.85-0.7 contains the backport of a 2 years old upstream commit, which might be already contained in the packaged Git snapshot Please include them both, acknowledging them in changelog. Thanks, -- Pino
Bug#995968: gkrellm-leds: This gkrellm plugin does not start, Error: undefined symbol: XTestFakeKeyEvent
Package: gkrellm-leds Version: 0.8.0-1.3+b1 Severity: grave Justification: renders package unusable X-Debbugs-Cc: re...@cs.unibo.it Dear Maintainer, There is a shared library linking problem. Bugfix: add --no-as-needed linker option. --- gkrellm-leds-0.8.0/Makefile 2021-10-09 10:28:38.0 +0200 +++ gkrellm-leds-0.8.0.fix/Makefile 2021-10-09 10:31:35.547270111 +0200 @@ -8,7 +8,7 @@ LIBS = $(GTK_LIB) $(X11_LIB) DEFINES = -LFLAGS = -shared +LFLAGS = -shared -Wl,--no-as-needed INCLUDES = $(GTK_INCLUDE) CFLAGS = -ansi -pedantic -Wall -O2 -fPIC CC = gcc -- System Information: Debian Release: bookworm/sid APT prefers stable-security APT policy: (500, 'stable-security'), (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 5.14.0-1-amd64 (SMP w/8 CPU threads) Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages gkrellm-leds depends on: ii gkrellm 2.3.11-2 ii libc62.32-4 gkrellm-leds recommends no packages. gkrellm-leds suggests no packages. -- no debconf information
