Bug#1032914: phog: ships /etc/pam.d/greetd
Hi, I've filled #1034595 to get phog unblocked as well. (also this hopefully delays the autoremoval of phog). Cheers Jochen * Marc Dequènes [2023-04-07 19:45]: Quack Arnaud, greetd was unblocked today. Thanks for your help :-). \_o< -- Marc Dequènes signature.asc Description: PGP signature
Bug#1028104: libboost-dev: Boost with C++20 uses unavailable std functions
Hi, boost-defaults_1.81.0 is in experimental. But boost1.81 is also available in the Debian Bookworm [1]. [1] https://packages.debian.org/source/testing/boost1.81 Regards Anton Am Di., 18. Apr. 2023 um 09:27 Uhr schrieb Olaf van der Spek : > ... > 1.81 is in experimental, not in bookworm, right? > It's unfortunate it's not in bookworm.
Bug#1034582: opencpn: broken symlinks: MathJax.js highlight.min.js due to missing dependencies
Package: opencpn Version: 5.8.0+dfsg-1 Severity: serious File: /usr/share/opencpn/plugins/chartdldr_pi/data/doc/MathJax.js File: /usr/share/opencpn/plugins/chartdldr_pi/data/doc/highlight.min.js User: debian...@lists.debian.org Usertags: adequate broken-symlink opencpn 5.8.0+dfsg-1 introduced two broken symlinks: /usr/share/opencpn/plugins/chartdldr_pi/data/doc/MathJax.js -> ../../../../../javascript/mathjax/MathJax.js /usr/share/opencpn/plugins/chartdldr_pi/data/doc/highlight.min.js -> ../../../../../javascript/highlight.js/highlight.min.js This appears to be because opencpn switched to using the packaged versions of these files, but only added the libjs-mathjax and libjs-highlight.js packages to the Build-Depends. Since there is nothing to auto-populate Depends for JavaScript packages (please talk to the JS team about adding that) and the packages weren't added manually to Depends, the added symlinks aren't working unless the user already had the packages installed. This bug was filed at severity serious because of the missing dependencies. Here is some information about the symlinks: $ adequate opencpn opencpn: broken-symlink /usr/share/opencpn/plugins/chartdldr_pi/data/doc/MathJax.js -> ../../../../../javascript/mathjax/MathJax.js opencpn: broken-symlink /usr/share/opencpn/plugins/chartdldr_pi/data/doc/highlight.min.js -> ../../../../../javascript/highlight.js/highlight.min.js $ readlink /usr/share/opencpn/plugins/chartdldr_pi/data/doc/MathJax.js /usr/share/opencpn/plugins/chartdldr_pi/data/doc/highlight.min.js ../../../../../javascript/mathjax/MathJax.js ../../../../../javascript/highlight.js/highlight.min.js $ chase /usr/share/opencpn/plugins/chartdldr_pi/data/doc/MathJax.js /usr/share/opencpn/plugins/chartdldr_pi/data/doc/highlight.min.js chase: ../../../../../javascript/mathjax: No such file or directory chase: ../../../../../javascript/highlight.js: No such file or directory $ apt-file search javascript/mathjax/MathJax.js libjs-mathjax: /usr/share/javascript/mathjax/MathJax.js $ apt-file search javascript/highlight.js/highlight.min.js libjs-highlight.js: /usr/share/javascript/highlight.js/highlight.min.js $ apt-cache show opencpn opencpn-data | grep libjs ; echo $? 1 Here is the log of the upgrade: Log started: 2023-04-18 17:09:54 apt-listchanges: Reading changelogs... apt-listchanges: Mailing root: apt-listchanges: changelogs for chianamo apt-listchanges: Reading changelogs... Selecting previously unselected package libcxx-serial1:amd64. Preparing to unpack .../libcxx-serial1_1.2.1-5+b1_amd64.deb ... Unpacking libcxx-serial1:amd64 (1.2.1-5+b1) ... Preparing to unpack .../opencpn-data_5.8.0+dfsg-1_all.deb ... Unpacking opencpn-data (5.8.0+dfsg-1) over (5.6.2+dfsg-3) ... Preparing to unpack .../opencpn_5.8.0+dfsg-1_amd64.deb ... Unpacking opencpn (5.8.0+dfsg-1) over (5.6.2+dfsg-3) ... Setting up opencpn-data (5.8.0+dfsg-1) ... Setting up libcxx-serial1:amd64 (1.2.1-5+b1) ... Setting up opencpn (5.8.0+dfsg-1) ... Processing triggers for mailcap (3.70+nmu1) ... Processing triggers for desktop-file-utils (0.26-1) ... Processing triggers for hicolor-icon-theme (0.17-2) ... Processing triggers for gnome-menus (3.36.0-1.1) ... Processing triggers for libc-bin (2.36-9) ... Processing triggers for man-db (2.11.2-2) ... Log ended: 2023-04-18 17:10:17 Here is the changelog of the version that introduced this: opencpn (5.8.0+dfsg-1) unstable; urgency=medium * New upstream release * Drop upstreamed patches, rebase remaining * Exclude MathJax and highlight js libraries, use packages instead. * Add new build deps: - libssl-dev - googletest - libglew-dev - repidjson-dev - libjs-highlight.js - libjs-mathjax * Update deprecated libpixbuf-dev build dep * Update d/copyright using cme. -- Alec Leamas Fri, 14 Apr 2023 09:37:20 +0200 -- System Information: Debian Release: 12.0 APT prefers testing-security APT policy: (950, 'testing-security'), (900, 'testing-debug'), (900, 'testing'), (800, 'unstable-debug'), (800, 'unstable'), (790, 'buildd-unstable'), (700, 'experimental-debug'), (700, 'experimental'), (690, 'buildd-experimental') merged-usr: no Architecture: amd64 (x86_64) Kernel: Linux 6.1.0-7-amd64 (SMP w/8 CPU threads; PREEMPT) Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_AU.utf8, LC_CTYPE=en_AU.utf8 (charmap=UTF-8), LANGUAGE=en_AU:en Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages opencpn depends on: ii bzip2 1.0.8-5+b1 ii libarchive133.6.2-1 ii libbz2-1.0 1.0.8-5+b1 ii libc6 2.36-9 ii libcurl3-gnutls 7.88.1-8 ii libcxx-serial1 1.2.1-5+b1 ii libelf1 0.188-2.1 i
Bug#1034577: marked as done (SSL certificate hostname check too restrictive)
Your message dated Tue, 18 Apr 2023 20:49:12 + with message-id and subject line Bug#1034577: fixed in libgwenhywfar 5.10.1-2 has caused the Debian Bug report #1034577, regarding SSL certificate hostname check too restrictive 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.) -- 1034577: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1034577 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: libgwenhywfar79 Version: 5.6.0-2 Severity: serious Tags: patch upstream fixed-upstream Forwarded: https://www.aquamaniac.de/rdm/issues/295 A few days ago the communication to the banking server https://hbci-pintan.gad.de/ doesn't work anymore because the already accepted server certificate is rejected with the message "Owner of certificate does not match hostname". The issue could be easily reproduced with bogus anonymous credentials as below (the error is triggered before authentication or credentials are needed). The only relevant parameter for the reproduction is the "--server" parameter, all other parameters are just there as the command wants them to be present. ``` $ aqhbci-tool4 adduser --username=Anonymous \ --tokentype=pintan \ --user=anonymous \ --bank=0 \ --server=https://hbci-pintan.gad.de/ 3:2023/04/18 21-14-36:(null)(50094):banking_update.c: 610: No AqBanking config folder found at [/home/user/.aqbanking/settings6/users] (-1) 3:2023/04/18 21-14-36:(null)(50094):banking_update.c: 610: No AqBanking config folder found at [/home/user/.aqbanking/settings/users] (-1) 3:2023/04/18 21-14-36:(null)(50094):banking_update.c: 411: There is no old settings folder, need initial setup ``` On a system which didn't have any AqBanking setup before, a new user with unique id 1 will be created (see output of "aqhbci-tool4 listusers"). ``` $ aqhbci-tool4 listusers User 0: Bank: de/0 User Id: anonymous Customer Id: anonymous Unique Id: 1 ``` Now, for reproduction of the error, you need to retrieve the server certificate, which will implicitly validate it. ``` $ aqhbci-tool4 getcert --user=1 5:2023/04/18 21-22-43:aqbanking(50117):siotlsext.c: 233: Status for certificate 76:42:76:BF:8E:E5:95:22:ED:A7:85:10:8F:52:96:73" has changed to "Certificate owner does not match hostname" (->0020), need to present 4:2023/04/18 21-22-43:gwen(50117):syncio_tls.c: 137: No checkCertFn set, using GWEN_GUI = Certificate Received = The following certificate has been received: Name : fints1.atruvia.de Organisation : Atruvia AG Department : unknown Country : DE City : Karlsruhe State: Baden-W?rttemberg Valid after : 2023/03/21 08:14:05 Valid until : 2024/03/21 08:09:00 Hash (MD5) : 76:42:76:BF:8E:E5:95:22:ED:A7:85:10:8F:52:96:73 Hash (SHA1) : 8E:C0:B3:C1:F7:B6:0A:9B:8F:86:00:D0:F2:72:E9:F6:72:EE:D7:18 Hash (SHA512): DE:A2:D8:16:29:3B:64:83:34:C4:BD:5C:08:40:DE:45:26:BA:EF:5E:79:E9:21:52:77:DE:3A:A2:F6:B8:98:E4:62:BE:28:31:03:57:D8:67:40:64:35:C7:A1:7C:31:AB:C3:B2:7C:B3:3B:98:31:CE:DE:23:36:50:F9:F2:77:E1 Status : Certificate owner does not match hostname Do you wish to accept this certificate? (1) Yes (2) No Please enter your choice: 2 5:2023/04/18 21-22-52:aqbanking(50117):siotlsext.c: 360: User response to presentation of cert "76:42:76:BF:8E:E5:95:22:ED:A7:85:10:8F:52:96:73" (Certificate owner does not match hostname): -108 3:2023/04/18 21-22-52:gwen(50117):syncio_tls.c: 1399: Peer cert not accepted (-108), aborting Could not connect to server 3:2023/04/18 21-22-52:aqhbci(50117):provider_online.c: 919: Could not connect to server (-108) Could not connect to server 3:2023/04/18 21-22-52:aqhbci-tool(50117):getcert.c: 98: Error -108 [Unknown error] 3:2023/04/18 21-22-52:aqhbci-tool(50117):aqhbci-tool.c: 275: Error calling control function (3) ``` Here you can see that Gwenhywfar reports the certificate as invalid with reason "Certificate owner does not match hostname". However, the very same configuration was working in the past just fine. Most likely something on the server end changed. Inspecting the certificate sent by the server shows that the "Common Name" field is set to "fints1.atruvia.de", but also that a SubjectAltName extension is present, which makes the certificate valid also for other hostnames, including "hbci-pintan.gad.de". Quoting https://en.wikipedia.org/wiki/Subject_Alternative_Name: > RFC 2818 (May 2000) specifies Subject Alternative Names as the preferred > method of adding DNS names to certificates, deprecating t
Bug#1034210: marked as done (python3-charon: dh_installsystemd doesn't handle files in /usr/lib/systemd/system)
Your message dated Tue, 18 Apr 2023 20:48:57 + with message-id and subject line Bug#1034210: fixed in libcharon 4.13.0-2 has caused the Debian Bug report #1034210, regarding python3-charon: dh_installsystemd doesn't handle files in /usr/lib/systemd/system 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.) -- 1034210: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1034210 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: python3-charon Version: 4.13.0-1 Severity: serious Tags: sid bookworm User: debhel...@packages.debian.org Usertags: systemd-files-in-usr-bookworm Dear Maintainer, It seems that your package python3-charon is shipping files (.service, .socket or .timer) in /usr/lib/systemd/system. This is not supported by the version of dh_installsystemd/debhelper currently in unstable and bookworm (See: #1031695). That means that currently your service might not be enabled at boot and/or started as expected. With the freeze currently in effect, debhelper will not be fixed for bookworm. As a result, could you please move these files to /lib/systemd/system instead so they are properly detected by debhelper? As soon as debhelper is supporting (not until bookworm+1 aka Trixie) you will be able to move them back to the newer location. Note that bookworm is currently in hard freeze, please limit the changes you are uploading to the ones fixing RC bugs. Also note that you might have to request a freeze exception to the release team. See: https://release.debian.org/testing/freeze_policy.html Feel free to contact me if you have any questions. Kind regards, Laurent Bigonville The list of packages has been generated with the following command: apt-file search -x '^/usr/lib/systemd/system/.*\.(service|timer|socket)$'|cut -d: -f1|sort -u --- End Message --- --- Begin Message --- Source: libcharon Source-Version: 4.13.0-2 Done: Christoph Berg We believe that the bug you reported is fixed in the latest version of libcharon, 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 1034...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Christoph Berg (supplier of updated libcharon package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Tue, 18 Apr 2023 22:29:20 +0200 Source: libcharon Architecture: source Version: 4.13.0-2 Distribution: unstable Urgency: medium Maintainer: Debian 3-D Printing Packages <3dprinter-gene...@lists.alioth.debian.org> Changed-By: Christoph Berg Closes: 1034210 Changes: libcharon (4.13.0-2) unstable; urgency=medium . [ Gregor Riepl ] * Fix systemd service path. Closes: #1034210 Checksums-Sha1: 9a7ebe7f76e98ca853ac6f2b4d037647764b52aa 2167 libcharon_4.13.0-2.dsc 82e6580db8060f20035ab94007e2970e77dfbee8 3344 libcharon_4.13.0-2.debian.tar.xz Checksums-Sha256: ae72c1a9858d4c1b04b32d4f696bae6f1e98ed7157beeac9fa6113e3d7a5b91e 2167 libcharon_4.13.0-2.dsc 9040f527bde57c93f9309fefa1f64c2e573e5e356eee086ad5f2d8190191f69f 3344 libcharon_4.13.0-2.debian.tar.xz Files: 4af14a07c1ecdf752587b7fd7edd373f 2167 python optional libcharon_4.13.0-2.dsc 37b03dc671583fdbce76eb35e9aec213 3344 python optional libcharon_4.13.0-2.debian.tar.xz -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEEXEj+YVf0kXlZcIfGTFprqxLSp64FAmQ+/owACgkQTFprqxLS p660Pg//apgMbNjuF0lvjlVrATfwtVpRBLfG5UUHPLSMEXZlwmWeGIyncmIgjGh+ eFveSGw6jl1AoQeqxWCwkoyvnD4UsZ6nHns55Hb9bYSXPA9+OQkMhLPQTp1Z+n04 FEgkdn1DO9TwwhISFGLV+iZgSzPtLdqXz+Q7FR3omLZFsWjGympSwGlj23X/kZc5 5wAR22187V8ODbHovg4UdI07VwniCC2t6p7MJqqQP1cCRH3h6c+GtkuKVL3a3fUA Xlsqz1NJgBT8eGJWHoFtZYSDz506We99zUVnRL/RKTA64p7EhC21i8wan4mhij4W uxq7edZMuFIz92Kwj0au5ZslF1LkGnOj4zoqUig/gZoPubDvBRmg4btTsS4u+nQ3 Ip5UbyyX5W95bMtvOFKnqKv6iytTgfRe/167ptI1jrci5LeJilpcAPbCej+5QTXM /kXtijN0AmQ4I61YpyTAL64qjZ/iWgeEofvijCONVPeQEy4g2xRFdci9tkxUh36R 3Li3vm/+N9X9GMBfpSjaFCBt5DUfflRXrvkQpXY1Xm478EP9+lxw+2gmER78xkzQ SUxNN80bFTzVzfzoIyONTUG/sNDMV2Mq8VT9kl0HLURB/hBeGl2wMlfLgHCIc6gE /lulWbHXs4lEfH+dAPvC+sy7sfoQoqkygeYi2RSRZQMEb5g9ZkY= =UAuy -END PGP SIGNATURE End Message ---
Bug#1034577: SSL certificate hostname check too restrictive
Patch verification To be sure, I just made a cross-check with the same AqBanking configuration as above and with the patch applied. To prove the fix is working as intended, I've retried the reproduction given in the initial Debian bug report. The hostname was no longer flagged as issue, so the patch seems to work. ``` $ aqhbci-tool4 getcert --user=1 5:2023/04/18 22-26-58:aqbanking(51692):siotlsext.c: 233: Status for certificate 76:42:76:BF:8E:E5:95:22:ED:A7:85:10:8F:52:96:73" has changed to "The certificate is valid" (->8000), need to present 4:2023/04/18 22-26-58:gwen(51692):syncio_tls.c: 137: No checkCertFn set, using GWEN_GUI = Certificate Received = The following certificate has been received: Name : fints1.atruvia.de Organisation : Atruvia AG Department : unknown Country : DE City : Karlsruhe State: Baden-W?rttemberg Valid after : 2023/03/21 08:14:05 Valid until : 2024/03/21 08:09:00 Hash (MD5) : 76:42:76:BF:8E:E5:95:22:ED:A7:85:10:8F:52:96:73 Hash (SHA1) : 8E:C0:B3:C1:F7:B6:0A:9B:8F:86:00:D0:F2:72:E9:F6:72:EE:D7:18 Hash (SHA512): DE:A2:D8:16:29:3B:64:83:34:C4:BD:5C:08:40:DE:45:26:BA:EF:5E:79:E9:21:52:77:DE:3A:A2:F6:B8:98:E4:62:BE:28:31:03:57:D8:67:40:64:35:C7:A1:7C:31:AB:C3:B2:7C:B3:3B:98:31:CE:DE:23:36:50:F9:F2:77:E1 Status : The certificate is valid Do you wish to accept this certificate? (1) Yes (2) No Please enter your choice: ``` To also prove the SSL certificate hostname check is still done correctly, I've temporarily configured in /etc/hosts the hostname of the server to point to the ip address of one of my servers. It got flagged correctly as hostname mismatch: ``` $ aqhbci-tool4 getcert --user=1 4:2023/04/18 22-18-05:gwen(51547):syncio_tls.c: 971: Certificate was not issued for this host Certificate was not issued for this host 5:2023/04/18 22-18-05:aqbanking(51547):siotlsext.c: 233: Status for certificate CA:AB:31:39:32:97:D9:DD:E0:DA:7F:E5:CD:FB:51:D4" has changed to "Certificate owner does not match hostname" (->0020), need to present 4:2023/04/18 22-18-05:gwen(51547):syncio_tls.c: 137: No checkCertFn set, using GWEN_GUI = Certificate Received = The following certificate has been received: Name : www.lenk.info Organisation : unknown Department : unknown Country : unknown City : unknown State: unknown Valid after : 2023/03/23 17:03:39 Valid until : 2023/06/21 18:03:38 Hash (MD5) : CA:AB:31:39:32:97:D9:DD:E0:DA:7F:E5:CD:FB:51:D4 Hash (SHA1) : FD:39:60:A0:8F:07:58:76:47:E5:8D:0E:E1:E5:81:66:1B:CB:C6:87 Hash (SHA512): 8B:DE:8E:4F:F7:B4:3F:89:D1:C3:86:8E:AC:9F:52:26:CC:3F:4F:32:22:86:11:1A:EB:8E:13:18:3B:AE:3B:21:A1:6D:E1:42:88:7C:8A:92:EF:BF:2C:54:B2:57:06:93:90:7C:EC:AA:15:C2:57:4F:2D:C2:32:4B:62:A0:EE:59 Status : Certificate owner does not match hostname Do you wish to accept this certificate? (1) Yes (2) No Please enter your choice: 2 ```
Bug#1034210: marked as done (python3-charon: dh_installsystemd doesn't handle files in /usr/lib/systemd/system)
Your message dated Tue, 18 Apr 2023 20:33:55 + with message-id and subject line Bug#1034210: fixed in libcharon 5.0.0-2 has caused the Debian Bug report #1034210, regarding python3-charon: dh_installsystemd doesn't handle files in /usr/lib/systemd/system 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.) -- 1034210: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1034210 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: python3-charon Version: 4.13.0-1 Severity: serious Tags: sid bookworm User: debhel...@packages.debian.org Usertags: systemd-files-in-usr-bookworm Dear Maintainer, It seems that your package python3-charon is shipping files (.service, .socket or .timer) in /usr/lib/systemd/system. This is not supported by the version of dh_installsystemd/debhelper currently in unstable and bookworm (See: #1031695). That means that currently your service might not be enabled at boot and/or started as expected. With the freeze currently in effect, debhelper will not be fixed for bookworm. As a result, could you please move these files to /lib/systemd/system instead so they are properly detected by debhelper? As soon as debhelper is supporting (not until bookworm+1 aka Trixie) you will be able to move them back to the newer location. Note that bookworm is currently in hard freeze, please limit the changes you are uploading to the ones fixing RC bugs. Also note that you might have to request a freeze exception to the release team. See: https://release.debian.org/testing/freeze_policy.html Feel free to contact me if you have any questions. Kind regards, Laurent Bigonville The list of packages has been generated with the following command: apt-file search -x '^/usr/lib/systemd/system/.*\.(service|timer|socket)$'|cut -d: -f1|sort -u --- End Message --- --- Begin Message --- Source: libcharon Source-Version: 5.0.0-2 Done: Christoph Berg We believe that the bug you reported is fixed in the latest version of libcharon, 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 1034...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Christoph Berg (supplier of updated libcharon package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Tue, 18 Apr 2023 22:26:02 +0200 Source: libcharon Architecture: source Version: 5.0.0-2 Distribution: experimental Urgency: medium Maintainer: Debian 3-D Printing Packages <3dprinter-gene...@lists.alioth.debian.org> Changed-By: Christoph Berg Closes: 1034210 Changes: libcharon (5.0.0-2) experimental; urgency=medium . [ Gregor Riepl ] * Fix systemd service path. Closes: #1034210 Checksums-Sha1: 88ae1497cd9ad7e91d9af0e7609ed6b494c6d68e 2150 libcharon_5.0.0-2.dsc f25f773b955af501a0d64460022a9a850badc92a 3392 libcharon_5.0.0-2.debian.tar.xz Checksums-Sha256: 13e6f106b614b5a04b1e735d986e65c049dafb292573f08cc74bdcd36501ee35 2150 libcharon_5.0.0-2.dsc 40722d78236f419e2fcfb74485e92abd11747a5a08ab7997241c7792d41c5496 3392 libcharon_5.0.0-2.debian.tar.xz Files: d587a1f0dda52f20cc615eb7309b89e8 2150 python optional libcharon_5.0.0-2.dsc 648da5878eae879ad244212b5a7a6307 3392 python optional libcharon_5.0.0-2.debian.tar.xz -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEEXEj+YVf0kXlZcIfGTFprqxLSp64FAmQ+/UQACgkQTFprqxLS p6583A//Xm7CfpWAqFs/7Da7AyoSsJt7UBbjaeF9bgaWtebKyWYIBEjVFY+EwvUI JZrhqL0LVvVx3jEeD9q5OEURSvW9BDeIvdZ+wnOiyawfuUKJWHn87K5E8MtO5ibM Q3klBSVpuwtxxPV5KexZk6c5ctIxWKvGu/MVKIt9PIs/Ld1zctSBvvc+RpQotZwN 32f9kBKAKHJInBjBv1YGkoEiyHyYSSGfBmCay/re+cE0vfa37YLaLkfSCtfNmy4Z TiStldesn6fee/UnC4sDSiuAQxxhqX4E/9Do+UiaeCU9Th23h4/FSuxRXMZDDRLD Mxiz+VieeLD1mfVYzrYZyqGLelU7hoXGoeiY10NrxaNHK7itbHGbDNZFfVQMbxb9 C9eOh7XeD2uVfk7+iiK+Rn/ABwHVXVLiout2DfvofYCyrXn26TH6Fc1ekowMcFmO RnPjAFk994Eeb1NJxf2wHberkn5p+PREi+k4rSe0GG/3rOoQDkfwkmFHwNbeUGUB 4dYBuUqgGGu+a4AdSjj7ry0qOTfKJ4A2E2tP/HXBZQwsJJHnHpkpqTwht9wYCOKZ TYed2cNvjlTemlMPa7cOUp1Vk/E8XjVsclzk2Rp26afvgXV8rTq1g7IimmL0jZFw Qz8Fjd0ss0yRLolmhRoFxA/TKtLomoLua/jhi3MUHthbrL/Bnkg= =ZgWh -END PGP SIGNATURE End Message ---
Bug#1034210: python3-charon: dh_installsystemd doesn't handle files in /usr/lib/systemd/system
Re: Gregor Riepl > -install(FILES service/charon.service DESTINATION lib/systemd/system) > +install(FILES service/charon.service DESTINATION /lib/systemd/system) Thanks for figuring that out! Uploaded to experimental and unstable. Christoph
Bug#1034577: SSL certificate hostname check too restrictive
Package: libgwenhywfar79
Version: 5.6.0-2
Severity: serious
Tags: patch upstream fixed-upstream
Forwarded: https://www.aquamaniac.de/rdm/issues/295
A few days ago the communication to the banking server
https://hbci-pintan.gad.de/ doesn't work anymore because the already accepted
server certificate is rejected with the message "Owner of certificate does not
match hostname".
The issue could be easily reproduced with bogus anonymous credentials as below
(the error is triggered before authentication or credentials are needed). The
only relevant parameter for the reproduction is the "--server" parameter, all
other parameters are just there as the command wants them to be present.
```
$ aqhbci-tool4 adduser --username=Anonymous \
--tokentype=pintan \
--user=anonymous \
--bank=0 \
--server=https://hbci-pintan.gad.de/
3:2023/04/18 21-14-36:(null)(50094):banking_update.c: 610: No AqBanking config
folder found at [/home/user/.aqbanking/settings6/users] (-1)
3:2023/04/18 21-14-36:(null)(50094):banking_update.c: 610: No AqBanking config
folder found at [/home/user/.aqbanking/settings/users] (-1)
3:2023/04/18 21-14-36:(null)(50094):banking_update.c: 411: There is no old
settings folder, need initial setup
```
On a system which didn't have any AqBanking setup before, a new user with
unique id 1 will be created (see output of "aqhbci-tool4 listusers").
```
$ aqhbci-tool4 listusers
User 0: Bank: de/0 User Id: anonymous Customer Id: anonymous Unique Id: 1
```
Now, for reproduction of the error, you need to retrieve the server
certificate, which will implicitly validate it.
```
$ aqhbci-tool4 getcert --user=1
5:2023/04/18 21-22-43:aqbanking(50117):siotlsext.c: 233: Status for
certificate 76:42:76:BF:8E:E5:95:22:ED:A7:85:10:8F:52:96:73" has changed to
"Certificate owner does not match hostname" (->0020), need to
present
4:2023/04/18 21-22-43:gwen(50117):syncio_tls.c: 137: No checkCertFn set, using
GWEN_GUI
= Certificate Received =
The following certificate has been received:
Name : fints1.atruvia.de
Organisation : Atruvia AG
Department : unknown
Country : DE
City : Karlsruhe
State: Baden-W?rttemberg
Valid after : 2023/03/21 08:14:05
Valid until : 2024/03/21 08:09:00
Hash (MD5) : 76:42:76:BF:8E:E5:95:22:ED:A7:85:10:8F:52:96:73
Hash (SHA1) : 8E:C0:B3:C1:F7:B6:0A:9B:8F:86:00:D0:F2:72:E9:F6:72:EE:D7:18
Hash (SHA512):
DE:A2:D8:16:29:3B:64:83:34:C4:BD:5C:08:40:DE:45:26:BA:EF:5E:79:E9:21:52:77:DE:3A:A2:F6:B8:98:E4:62:BE:28:31:03:57:D8:67:40:64:35:C7:A1:7C:31:AB:C3:B2:7C:B3:3B:98:31:CE:DE:23:36:50:F9:F2:77:E1
Status : Certificate owner does not match hostname
Do you wish to accept this certificate?
(1) Yes (2) No
Please enter your choice: 2
5:2023/04/18 21-22-52:aqbanking(50117):siotlsext.c: 360: User response to
presentation of cert "76:42:76:BF:8E:E5:95:22:ED:A7:85:10:8F:52:96:73"
(Certificate owner does not match hostname): -108
3:2023/04/18 21-22-52:gwen(50117):syncio_tls.c: 1399: Peer cert not accepted
(-108), aborting
Could not connect to server
3:2023/04/18 21-22-52:aqhbci(50117):provider_online.c: 919: Could not connect
to server (-108)
Could not connect to server
3:2023/04/18 21-22-52:aqhbci-tool(50117):getcert.c: 98: Error -108 [Unknown
error]
3:2023/04/18 21-22-52:aqhbci-tool(50117):aqhbci-tool.c: 275: Error calling
control function (3)
```
Here you can see that Gwenhywfar reports the certificate as invalid with reason
"Certificate owner does not match hostname".
However, the very same configuration was working in the past just fine. Most
likely something on the server end changed.
Inspecting the certificate sent by the server shows that the "Common Name"
field is set to "fints1.atruvia.de", but also that a SubjectAltName extension
is present, which makes the certificate valid also for other hostnames,
including "hbci-pintan.gad.de".
Quoting https://en.wikipedia.org/wiki/Subject_Alternative_Name:
> RFC 2818 (May 2000) specifies Subject Alternative Names as the preferred
> method of adding DNS names to certificates, deprecating the previous method
> of putting DNS names in the commonName field. Google Chrome version 58
> (March 2017) removed support for checking the commonName field at all,
> instead only looking at the SANs.
So, if the certificate is valid, but AqBanking doesn't accept it, I concluded
to have found a bug.
Looking into the code, I think the culprit is some incomplete hostname
verification in Gwenhywfar's source file src/sio/syncio_tls.c at these lines
(line numbers based on current Git master):
```
1041 rv=gnutls_x509_crt_get_dn_by_oid(cert, GNUTLS_OID_X520_COMMON_NAME,
0, 0, buffer1, &size);
1042 if (rv==0) {
1043 GWEN_SslCertDescr_SetCommonName(certDescr, buffer1);
1044 if (xio->hostName && strcasecmp(xio->hostName, buffer1)!=0) {
1045 DBG_INFO(GWEN_LOGDOMAIN, "Owner of certi
Processed: found 1034182 in 0.27.2-1
Processing commands for cont...@bugs.debian.org:
> found 1034182 0.27.2-1
Bug #1034182 {Done: Bas Couwenberg } [src:owslib] owslib:
CVE-2023-27476
Marked as found in versions owslib/0.27.2-1.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
1034182: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1034182
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#1034210: python3-charon: dh_installsystemd doesn't handle files in /usr/lib/systemd/system
Hi,
As a result, could you please move these files to /lib/systemd/system instead
so they are properly detected by debhelper?
As soon as debhelper is supporting (not until bookworm+1 aka Trixie) you will
be able to move them back to the newer location.
I've committed a patch to Salsa.
It looks like it does what it's supposed to, but I don't know how to
test it because I don't understand the inner workings of debhelper very
well.
@myon: Could you push a new release when you have time, and also against
4.13.0-1? Thanks!
The patch also works with 4.13.0-1, with minor fuzz. Here's the
refreshed version:
$ cat debian/patches/0002-service-files-in-root.patch
--- a/CMakeLists.txt
+++ b/CMakeLists.txt
@@ -35,7 +35,7 @@
install(DIRECTORY Charon DESTINATION ${CHARON_INSTALL_PATH} ${_excludes})
if(INSTALL_SERVICE)
-install(FILES service/charon.service DESTINATION lib/systemd/system)
+install(FILES service/charon.service DESTINATION /lib/systemd/system)
install(FILES service/nl.ultimaker.charon.conf DESTINATION
share/dbus-1/system.d)
endif()
Bug#1032902: Numba issues for genx for other architectures than amd64 and ppc64el (Was: genx won't start: TypeError: Pen(): arguments did not match any overloaded call)
Hi, I've found genx in the "Cleaner view"[1] due to missing builds[2]. It turns out that for instance for arm64[3] the build fails with tests/test_numba_equivalency.py Fatal Python error: Segmentation fault For armel[4] (and armhf) we get dh_auto_test -a -O--buildsystem=pybuild I: pybuild base:240: cd /<>/.pybuild/cpython3_3.11/build; python3.11 -m pytest tests Fatal Python error: Aborted Current thread 0xf7a30020 (most recent call first): File "/usr/lib/python3/dist-packages/llvmlite/binding/ffi.py", line 151 in __call__ File "/usr/lib/python3/dist-packages/llvmlite/binding/executionengine.py", line 92 in finalize_object File "/usr/lib/python3/dist-packages/numba/core/codegen.py", line 1060 in wrapper File "/usr/lib/python3/dist-packages/numba/core/codegen.py", line 999 in _finalize_specific File "/usr/lib/python3/dist-packages/numba/core/codegen.py", line 797 in _finalize_final_module ... For i386[5] I: pybuild base:240: cd /<>/.pybuild/cpython3_3.11/build; python3.11 -m pytest tests = test session starts == platform linux -- Python 3.11.2, pytest-7.2.1, pluggy-1.0.0+repack rootdir: /<> collected 14 items / 1 error ERRORS _ ERROR collecting .pybuild/cpython3_3.11/build/tests/test_numba_equivalency.py _ tests/test_numba_equivalency.py:11: in from genx.models.lib import instrument, instrument_numba, paratt, paratt_numba, neutron_refl, neutron_numba, \ genx/models/lib/instrument_numba.py:9: in @numba.jit( /usr/lib/python3/dist-packages/numba/core/decorators.py:219: in wrapper disp.compile(sig) /usr/lib/python3/dist-packages/numba/core/dispatcher.py:965: in compile cres = self._compiler.compile(args, return_type) ... and we have other errors for other architectures which all contain the string "numba". IMHO this is a mess we can hardly fix in hard freeze. I see only two chances: 1. Restrict the architectures to amd64 and ppc64el (which are the only ones where the build succeeds or 2. Remove the package from testing for the moment. The only rdepends is currently pan-grazing-incidence which will be lowered to suggests once we re-render debian-pan metapackages. What do you think? Kind regards Andreas. [1] https://udd.debian.org/bugs/?release=bookworm_and_sid&merged=ign&done=only&rc=1&flastmod=ign&flastmodval=5&sortby=last_modified&sorto=asc&ctags=1&cdeferred=1&caffected=1&cautormtime=1&cmissingbuilds=1&#results [2] https://buildd.debian.org/status/package.php?p=genx&suite=sid [3] https://buildd.debian.org/status/fetch.php?pkg=genx&arch=arm64&ver=3.6.21-1&stamp=1681143066&raw=0 [4] https://buildd.debian.org/status/fetch.php?pkg=genx&arch=armel&ver=3.6.21-1&stamp=1681142381&raw=0 [5] https://buildd.debian.org/status/fetch.php?pkg=genx&arch=i386&ver=3.6.21-1&stamp=1681142358&raw=0 -- http://fam-tille.de
Bug#999526: Taking over package into Debian Python Team maintenance and fixing bug (Was: mdp: FTBFS with numpy 1.21 (in experimental): dh_auto_test: error: pybuild --test --test-pytest -i python{versi
Hi Yaroslav, Am Mon, Apr 17, 2023 at 05:59:23PM -0400 schrieb Yaroslav Halchenko: > Hi Andreas, > > Thank you very much for offering help. I think Tiziano would not mind, > so please feel very welcome to a) for the sake of b) or any other > goodness you would like to bring ;) https://tracker.debian.org/news/1429393/accepted-mdp-36-2-source-into-unstable/ https://salsa.debian.org/python-team/packages/mdp > Note though that MDP is pretty much inactive project since a few years > back. It seems it is still used by some and somewhat maintained > upstream, so might indeed be worthwhile keeping afloat in Debian but I > would not cry if it got RMed. We have some rdepends: $ apt rdepends python3-mdp python3-mdp Reverse Depends: Recommends: pan-machine-learning Recommends: science-machine-learning Enhances: python3-sklearn Recommends: python3-pymca5 Recommends: science-machine-learning > After/if packaging moves to a new repo on salsa, we can submit a > PR to add an empty out debian/ and add stub debian/README to that > upstream repo to signal that packaging moved to salsa. See above. A finding that came unexpected after adding autopkgtest is that 32bit architectures can't cope with 'float128', 'complex256' data types. Since I wanted to avoid further trouble in hard freeze I decided to restrict architectures to 64bit for the moment. Kind regards Andreas. -- http://fam-tille.de
Bug#1002393: marked as done (mdp: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p "3.10 3.9" returned exit code 13)
Your message dated Tue, 18 Apr 2023 12:49:09 +
with message-id
and subject line Bug#999526: fixed in mdp 3.6-2
has caused the Debian Bug report #999526,
regarding mdp: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i
python{version} -p "3.10 3.9" returned exit code 13
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
999526: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=999526
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: mdp
Version: 3.6-1.1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20211220 ftbfs-bookworm
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> PYBUILD_SYSTEM=custom \
> PYBUILD_TEST_ARGS="{interpreter} -m pytest --seed=725021957 mdp &&
> {interpreter} -m pytest --seed=725021957 bimdp" dh_auto_test
> I: pybuild base:237: python3.10 -m pytest --seed=725021957 mdp && python3.10
> -m pytest --seed=725021957 bimdp
> ImportError while loading conftest '/<>/mdp/test/conftest.py'.
> mdp/__init__.py:131: in
> from . import utils
> mdp/utils/__init__.py:6: in
> from .routines import (timediff, refcast, scast, rotate, random_rot,
> mdp/utils/routines.py:295: in
> _UNSAFE_DTYPES = [numx.typeDict[d] for d in
> mdp/utils/routines.py:297: in
> if d in numx.typeDict]
> E AttributeError: module 'scipy' has no attribute 'typeDict'
> E: pybuild pybuild:355: test: plugin custom failed with: exit code=4:
> python3.10 -m pytest --seed=725021957 mdp && python3.10 -m pytest
> --seed=725021957 bimdp
> I: pybuild base:237: python3.9 -m pytest --seed=725021957 mdp && python3.9 -m
> pytest --seed=725021957 bimdp
> ImportError while loading conftest '/<>/mdp/test/conftest.py'.
> mdp/__init__.py:131: in
> from . import utils
> mdp/utils/__init__.py:6: in
> from .routines import (timediff, refcast, scast, rotate, random_rot,
> mdp/utils/routines.py:295: in
> _UNSAFE_DTYPES = [numx.typeDict[d] for d in
> mdp/utils/routines.py:297: in
> if d in numx.typeDict]
> E AttributeError: module 'scipy' has no attribute 'typeDict'
> E: pybuild pybuild:355: test: plugin custom failed with: exit code=4:
> python3.9 -m pytest --seed=725021957 mdp && python3.9 -m pytest
> --seed=725021957 bimdp
> dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p "3.10
> 3.9" returned exit code 13
The full build log is available from:
http://qa-logs.debian.net/2021/12/20/mdp_3.6-1.1_unstable.log
A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!
If you reassign this bug to another package, please marking it as 'affects'-ing
this package. See https://www.debian.org/Bugs/server-control#affects
If you fail to reproduce this, please provide a build log and diff it with mine
so that we can identify if something relevant changed in the meantime.
--- End Message ---
--- Begin Message ---
Source: mdp
Source-Version: 3.6-2
Done: Andreas Tille
We believe that the bug you reported is fixed in the latest version of
mdp, 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 999...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Andreas Tille (supplier of updated mdp package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Tue, 18 Apr 2023 11:28:17 +0200
Source: mdp
Architecture: source
Version: 3.6-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Team
Changed-By: Andreas Tille
Closes: 999526 1002393
Changes:
mdp (3.6-2) unstable; urgency=medium
.
* Team upload.
* Migrate package to Debian Python Team
* Solve deprecation of numpy.typeDict issue
Closes: #1002393, #999526
* Testsuite: autopkgtest-pkg-python
* debian/salsa-ci.yml
* Add non-trivial autopkgtest
* Package works only on 64 bit, thus restrict architectures
Checksums-Sha1:
889c654fef17fdf035574df107594d419cfcced5 2302 mdp_3.6-2.dsc
b09318983644b297b31f3e4de0eb74338ff51522 5352 mdp_3.6-2.debian.tar.xz
Bug#999526: marked as done (mdp: FTBFS with numpy 1.21 (in experimental): dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p 3.9 returned exit code 13)
Your message dated Tue, 18 Apr 2023 12:49:09 +
with message-id
and subject line Bug#999526: fixed in mdp 3.6-2
has caused the Debian Bug report #999526,
regarding mdp: FTBFS with numpy 1.21 (in experimental): dh_auto_test: error:
pybuild --test --test-pytest -i python{version} -p 3.9 returned exit code 13
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
999526: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=999526
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: mdp
Version: 3.6-1.1
Severity: important
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-numpy121
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64, using numpy 1.21 currently in experimental. This version
will soon be uploaded to unstable.
If you have questions about this, please contact Sandro Tosi
.
Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> PYBUILD_SYSTEM=custom \
> PYBUILD_TEST_ARGS="{interpreter} -m pytest --seed=725021957 mdp &&
> {interpreter} -m pytest --seed=725021957 bimdp" dh_auto_test
> I: pybuild base:232: python3.9 -m pytest --seed=725021957 mdp && python3.9 -m
> pytest --seed=725021957 bimdp
> ImportError while loading conftest '/<>/mdp/test/conftest.py'.
> mdp/__init__.py:131: in
> from . import utils
> mdp/utils/__init__.py:6: in
> from .routines import (timediff, refcast, scast, rotate, random_rot,
> mdp/utils/routines.py:295: in
> _UNSAFE_DTYPES = [numx.typeDict[d] for d in
> mdp/utils/routines.py:297: in
> if d in numx.typeDict]
> E AttributeError: module 'scipy' has no attribute 'typeDict'
> E: pybuild pybuild:354: test: plugin custom failed with: exit code=4:
> python3.9 -m pytest --seed=725021957 mdp && python3.9 -m pytest
> --seed=725021957 bimdp
> dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p 3.9
> returned exit code 13
The full build log is available from:
http://qa-logs.debian.net/2021/11/numpy-matplotlib/numpy-exp/mdp_3.6-1.1_unstable_numpy-exp.log
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: mdp
Source-Version: 3.6-2
Done: Andreas Tille
We believe that the bug you reported is fixed in the latest version of
mdp, 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 999...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Andreas Tille (supplier of updated mdp package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Tue, 18 Apr 2023 11:28:17 +0200
Source: mdp
Architecture: source
Version: 3.6-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Team
Changed-By: Andreas Tille
Closes: 999526 1002393
Changes:
mdp (3.6-2) unstable; urgency=medium
.
* Team upload.
* Migrate package to Debian Python Team
* Solve deprecation of numpy.typeDict issue
Closes: #1002393, #999526
* Testsuite: autopkgtest-pkg-python
* debian/salsa-ci.yml
* Add non-trivial autopkgtest
* Package works only on 64 bit, thus restrict architectures
Checksums-Sha1:
889c654fef17fdf035574df107594d419cfcced5 2302 mdp_3.6-2.dsc
b09318983644b297b31f3e4de0eb74338ff51522 5352 mdp_3.6-2.debian.tar.xz
b430fb1436bb6d7c8c6293cfacabffbd3ce069cb 8001 mdp_3.6-2_amd64.buildinfo
Checksums-Sha256:
42928eee022c4cb030a8f4ff59550a8b9cdf4e5cd5cf121cb74e9433fb95e026 2302
mdp_3.6-2.dsc
92db1a894545c178878de949a2da4ecf5a79925050d7a732a32d502bff15f71f 5352
mdp_3.6-2.debian.tar.xz
c7f2cff725ef8af912d3a6f5f2600825dd5595c33648d9e93a387541041cb967 8001
mdp_3.6-2_amd64.buildinfo
Files:
426a9bc50f68916255762848ad87a1d7 2302 python optional mdp_3.6-2.dsc
361c423bc474f61de7a749ef35bdd33f 5352 python optional mdp_3.6-2.debian.tar.xz
2b62345e732ea43ec7bb4fd7e9f7af53 8001 python optional mdp_3.6-2_amd64.buildinfo
-BEGIN PGP SIGNATURE-
iQJFBAEBCgAvFiEE8fAHMgoDVUHwpm
Bug#1002393: marked as done (mdp: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p "3.10 3.9" returned exit code 13)
Your message dated Tue, 18 Apr 2023 12:49:09 +
with message-id
and subject line Bug#1002393: fixed in mdp 3.6-2
has caused the Debian Bug report #1002393,
regarding mdp: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i
python{version} -p "3.10 3.9" returned exit code 13
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
1002393: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1002393
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: mdp
Version: 3.6-1.1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20211220 ftbfs-bookworm
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> PYBUILD_SYSTEM=custom \
> PYBUILD_TEST_ARGS="{interpreter} -m pytest --seed=725021957 mdp &&
> {interpreter} -m pytest --seed=725021957 bimdp" dh_auto_test
> I: pybuild base:237: python3.10 -m pytest --seed=725021957 mdp && python3.10
> -m pytest --seed=725021957 bimdp
> ImportError while loading conftest '/<>/mdp/test/conftest.py'.
> mdp/__init__.py:131: in
> from . import utils
> mdp/utils/__init__.py:6: in
> from .routines import (timediff, refcast, scast, rotate, random_rot,
> mdp/utils/routines.py:295: in
> _UNSAFE_DTYPES = [numx.typeDict[d] for d in
> mdp/utils/routines.py:297: in
> if d in numx.typeDict]
> E AttributeError: module 'scipy' has no attribute 'typeDict'
> E: pybuild pybuild:355: test: plugin custom failed with: exit code=4:
> python3.10 -m pytest --seed=725021957 mdp && python3.10 -m pytest
> --seed=725021957 bimdp
> I: pybuild base:237: python3.9 -m pytest --seed=725021957 mdp && python3.9 -m
> pytest --seed=725021957 bimdp
> ImportError while loading conftest '/<>/mdp/test/conftest.py'.
> mdp/__init__.py:131: in
> from . import utils
> mdp/utils/__init__.py:6: in
> from .routines import (timediff, refcast, scast, rotate, random_rot,
> mdp/utils/routines.py:295: in
> _UNSAFE_DTYPES = [numx.typeDict[d] for d in
> mdp/utils/routines.py:297: in
> if d in numx.typeDict]
> E AttributeError: module 'scipy' has no attribute 'typeDict'
> E: pybuild pybuild:355: test: plugin custom failed with: exit code=4:
> python3.9 -m pytest --seed=725021957 mdp && python3.9 -m pytest
> --seed=725021957 bimdp
> dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p "3.10
> 3.9" returned exit code 13
The full build log is available from:
http://qa-logs.debian.net/2021/12/20/mdp_3.6-1.1_unstable.log
A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!
If you reassign this bug to another package, please marking it as 'affects'-ing
this package. See https://www.debian.org/Bugs/server-control#affects
If you fail to reproduce this, please provide a build log and diff it with mine
so that we can identify if something relevant changed in the meantime.
--- End Message ---
--- Begin Message ---
Source: mdp
Source-Version: 3.6-2
Done: Andreas Tille
We believe that the bug you reported is fixed in the latest version of
mdp, 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 1002...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Andreas Tille (supplier of updated mdp package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Tue, 18 Apr 2023 11:28:17 +0200
Source: mdp
Architecture: source
Version: 3.6-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Team
Changed-By: Andreas Tille
Closes: 999526 1002393
Changes:
mdp (3.6-2) unstable; urgency=medium
.
* Team upload.
* Migrate package to Debian Python Team
* Solve deprecation of numpy.typeDict issue
Closes: #1002393, #999526
* Testsuite: autopkgtest-pkg-python
* debian/salsa-ci.yml
* Add non-trivial autopkgtest
* Package works only on 64 bit, thus restrict architectures
Checksums-Sha1:
889c654fef17fdf035574df107594d419cfcced5 2302 mdp_3.6-2.dsc
b09318983644b297b31f3e4de0eb74338ff51522 5352 mdp_3.6-2.debian.ta
Bug#999526: marked as done (mdp: FTBFS with numpy 1.21 (in experimental): dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p 3.9 returned exit code 13)
Your message dated Tue, 18 Apr 2023 12:49:09 +
with message-id
and subject line Bug#1002393: fixed in mdp 3.6-2
has caused the Debian Bug report #1002393,
regarding mdp: FTBFS with numpy 1.21 (in experimental): dh_auto_test: error:
pybuild --test --test-pytest -i python{version} -p 3.9 returned exit code 13
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
1002393: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1002393
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: mdp
Version: 3.6-1.1
Severity: important
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-numpy121
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64, using numpy 1.21 currently in experimental. This version
will soon be uploaded to unstable.
If you have questions about this, please contact Sandro Tosi
.
Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> PYBUILD_SYSTEM=custom \
> PYBUILD_TEST_ARGS="{interpreter} -m pytest --seed=725021957 mdp &&
> {interpreter} -m pytest --seed=725021957 bimdp" dh_auto_test
> I: pybuild base:232: python3.9 -m pytest --seed=725021957 mdp && python3.9 -m
> pytest --seed=725021957 bimdp
> ImportError while loading conftest '/<>/mdp/test/conftest.py'.
> mdp/__init__.py:131: in
> from . import utils
> mdp/utils/__init__.py:6: in
> from .routines import (timediff, refcast, scast, rotate, random_rot,
> mdp/utils/routines.py:295: in
> _UNSAFE_DTYPES = [numx.typeDict[d] for d in
> mdp/utils/routines.py:297: in
> if d in numx.typeDict]
> E AttributeError: module 'scipy' has no attribute 'typeDict'
> E: pybuild pybuild:354: test: plugin custom failed with: exit code=4:
> python3.9 -m pytest --seed=725021957 mdp && python3.9 -m pytest
> --seed=725021957 bimdp
> dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p 3.9
> returned exit code 13
The full build log is available from:
http://qa-logs.debian.net/2021/11/numpy-matplotlib/numpy-exp/mdp_3.6-1.1_unstable_numpy-exp.log
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: mdp
Source-Version: 3.6-2
Done: Andreas Tille
We believe that the bug you reported is fixed in the latest version of
mdp, 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 1002...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Andreas Tille (supplier of updated mdp package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Tue, 18 Apr 2023 11:28:17 +0200
Source: mdp
Architecture: source
Version: 3.6-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Team
Changed-By: Andreas Tille
Closes: 999526 1002393
Changes:
mdp (3.6-2) unstable; urgency=medium
.
* Team upload.
* Migrate package to Debian Python Team
* Solve deprecation of numpy.typeDict issue
Closes: #1002393, #999526
* Testsuite: autopkgtest-pkg-python
* debian/salsa-ci.yml
* Add non-trivial autopkgtest
* Package works only on 64 bit, thus restrict architectures
Checksums-Sha1:
889c654fef17fdf035574df107594d419cfcced5 2302 mdp_3.6-2.dsc
b09318983644b297b31f3e4de0eb74338ff51522 5352 mdp_3.6-2.debian.tar.xz
b430fb1436bb6d7c8c6293cfacabffbd3ce069cb 8001 mdp_3.6-2_amd64.buildinfo
Checksums-Sha256:
42928eee022c4cb030a8f4ff59550a8b9cdf4e5cd5cf121cb74e9433fb95e026 2302
mdp_3.6-2.dsc
92db1a894545c178878de949a2da4ecf5a79925050d7a732a32d502bff15f71f 5352
mdp_3.6-2.debian.tar.xz
c7f2cff725ef8af912d3a6f5f2600825dd5595c33648d9e93a387541041cb967 8001
mdp_3.6-2_amd64.buildinfo
Files:
426a9bc50f68916255762848ad87a1d7 2302 python optional mdp_3.6-2.dsc
361c423bc474f61de7a749ef35bdd33f 5352 python optional mdp_3.6-2.debian.tar.xz
2b62345e732ea43ec7bb4fd7e9f7af53 8001 python optional mdp_3.6-2_amd64.buildinfo
-BEGIN PGP SIGNATURE-
iQJFBAEBCgAvFiEE8fAHMgoDV
Bug#918495: marked as done (php5-intl: php intl does not show in modules from get_load_extensions)
Your message dated Tue, 18 Apr 2023 13:56:26 +0200 with message-id <60b2fd0d-2b64-0759-9073-fc452bd16...@debian.org> and subject line php5 has been superseded by php7 has caused the Debian Bug report #918495, regarding php5-intl: php intl does not show in modules from get_load_extensions 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.) -- 918495: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=918495 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: php5-intl Version: 5.6.39+dfsg-0+deb8u1 Severity: grave Justification: renders package unusable Dear Maintainer, I upgraded php to the lasted security from debian up to 5.6.39 etc after the upgrade my software stop working due the intl extension are not listed by get_load_extension a related bug was reportd and i think Debian package are the problem: https://github.com/opensourcepos/opensourcepos/issues/2299 -- Package-specific info: Additional PHP 5 information PHP 5 SAPI (php5query -S): cli cgi PHP 5 Extensions (php5query -M -v): xmlrpc (Enabled for cli by maintainer script) xmlrpc (Enabled for cgi by maintainer script) pdo_odbc (Enabled for cli by maintainer script) pdo_odbc (Enabled for cgi by maintainer script) imagick (Enabled for cli by maintainer script) imagick (Enabled for cgi by maintainer script) pdo_mysql (Enabled for cli by maintainer script) pdo_mysql (Enabled for cgi by maintainer script) pgsql (Enabled for cli by maintainer script) pgsql (Enabled for cgi by maintainer script) gd (Enabled for cli by local administrator) gd (Enabled for cgi by local administrator) apcu (Enabled for cli by maintainer script) apcu (Enabled for cgi by maintainer script) No module matches bcmath No module matches bcmath sqlite3 (Enabled for cli by maintainer script) sqlite3 (Enabled for cgi by maintainer script) No module matches openssl No module matches openssl No module matches help No module matches help curl (Enabled for cli by local administrator) curl (Enabled for cgi by local administrator) opcache (Enabled for cli by maintainer script) opcache (Enabled for cgi by maintainer script) pdo_pgsql (Enabled for cli by maintainer script) pdo_pgsql (Enabled for cgi by maintainer script) mssql (Enabled for cli by maintainer script) mssql (Enabled for cgi by maintainer script) pspell (Enabled for cli by maintainer script) pspell (Enabled for cgi by maintainer script) No module matches mbstriing No module matches mbstriing No module matches mbstring No module matches mbstring pdo (Enabled for cli by maintainer script) pdo (Enabled for cgi by maintainer script) mysqli (Enabled for cli by maintainer script) mysqli (Enabled for cgi by maintainer script) mcrypt (Enabled for cli by maintainer script) mcrypt (Enabled for cgi by maintainer script) intl (Enabled for cli by local administrator) intl (Enabled for cgi by local administrator) readline (Enabled for cli by maintainer script) readline (Enabled for cgi by maintainer script) pdo_sqlite (Enabled for cli by maintainer script) pdo_sqlite (Enabled for cgi by maintainer script) mysql (Enabled for cli by maintainer script) mysql (Enabled for cgi by maintainer script) enchant (Enabled for cli by maintainer script) enchant (Enabled for cgi by maintainer script) xsl (Enabled for cli by maintainer script) xsl (Enabled for cgi by maintainer script) odbc (Enabled for cli by maintainer script) odbc (Enabled for cgi by maintainer script) pdo_dblib (Enabled for cli by maintainer script) pdo_dblib (Enabled for cgi by maintainer script) json (Enabled for cli by maintainer script) json (Enabled for cgi by maintainer script) Configuration files: /etc/php5/mods-available/intl.ini extension=intl.so -- System Information: Debian Release: 8.11 APT prefers oldstable-updates APT policy: (500, 'oldstable-updates'), (500, 'oldstable') Architecture: amd64 (x86_64) Kernel: Linux 3.16.0-4-amd64 (SMP w/1 CPU core) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages php5-intl depends on: ii libc6 2.19-18+deb8u10 ii libgcc11:4.9.2-10+deb8u2 ii libicu52 52.1-8+deb8u4 ii php5-common [phpapi-20131226] 5.6.39+dfsg-0+deb8u1 ii ucf3.0030 php5-intl recommends no packages. php5-intl suggests no packages. Versions of packages php5-common depends on: ii libc6 2.19-18+deb8u10 ii lsof4.86+dfsg-1 ii psmisc 22.21-2 ii sed 4.2.2-4+deb8u1 ii ucf
Bug#1034565: ftbfs tests fail on ppc64el and mips64el
Package: ruby-prometheus-client-mmap Version: 0.17.0+spec-1 Severity: serious Control: forwarded -1 https://gitlab.com/gitlab-org/ruby/gems/prometheus-client-mmap/-/issues/43 Version in testing is not affected as we did not have tests enabled. Failures: 1) Prometheus::Client::Helper::MmapedFile file does not exist creates a file with minimum initial size Failure/Error: expect(File.size(subject.filepath)).to eq(subject.send(:initial_mmap_file_size)) expected: 4096 got: 16384 (compared using ==) # ./spec/prometheus/client/helpers/mmaped_file_spec.rb:30:in `block (3 levels) in ' 2) Prometheus::Client::MmapedDict#initialize empty mmap'ed file is initialized with correct size Failure/Error: expect(File.size(tmp_file.path)).to eq(tmp_mmaped_file.send(:initial_mmap_file_size)) expected: 4096 got: 16384 (compared using ==) # ./spec/prometheus/client/mmaped_dict_spec.rb:19:in `block (4 levels) in ' 3) Prometheus::Client::MmapedDict#initialize mmap'ed file that is above minimum size is initialized with the a page size Failure/Error: expect(tmp_file.size).to eq(4096); expected: 4096 got: 16384 (compared using ==) # ./spec/prometheus/client/mmaped_dict_spec.rb:34:in `block (4 levels) in ' Full build logs https://buildd.debian.org/status/fetch.php?pkg=ruby-prometheus-client-mmap&arch=ppc64el&ver=0.19.1-1&stamp=1681745611&raw=0 https://buildd.debian.org/status/fetch.php?pkg=ruby-prometheus-client-mmap&arch=mips64el&ver=0.19.1-1&stamp=1681745649&raw=0 Forwarded upstream at https://gitlab.com/gitlab-org/ruby/gems/prometheus-client-mmap/-/issues/43 OpenPGP_0x8F53E0193B294B75.asc Description: OpenPGP public key OpenPGP_signature Description: OpenPGP digital signature
Bug#785897: marked as done (exaile: Please update to GStreamer 1.x)
Your message dated Tue, 18 Apr 2023 13:25:48 +0200 with message-id <9c21d3c3-bbf2-dcd9-7f0f-392e6f589...@debian.org> and subject line exaile has been removed from Debian has caused the Debian Bug report #785897, regarding exaile: Please update to GStreamer 1.x 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.) -- 785897: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=785897 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: exaile Severity: important User: sl...@debian.org Usertags: gstreamer0.10-removal Hi maintainer, your package exaile currently still depends on GStreamer 0.10. GStreamer 0.10 is no longer maintained and supported by the upstream project since almost 3 years, and contains many known bugs that are fixed in the new 1.x release series of GStreamer. Next to many bug fixes, the new release series also contains many other improvements, new features and a more streamlined API. For the next Debian release GStreamer 0.10 is planned to be removed, and if your package is not updated it might not be included in the release. Please update your package to use the new version as soon as possible. If you need any help with porting or have further questions, please feel free to also contact me privately. Best regards, Sebastian PS: See https://bugs.debian.org/785198 and https://lists.debian.org/debian-devel/2015/05/msg00335.html for some further discussion. --- End Message --- --- Begin Message --- Version: 3.4.5-1+rm exaile was last released with Debian 8 (jessie) in April 2015 and was removed from the Debian archive afterwards. See https://bugs.debian.org/813255 for details on the removal. I'm closing the remaining bug reports now. Andreas--- End Message ---
Processed: Re: Bug#1034230: fail2ban: dh_installsystemd doesn't handle files in /usr/lib/systemd/system
Processing control commands: > tags -1 patch Bug #1034230 [fail2ban] fail2ban: dh_installsystemd doesn't handle files in /usr/lib/systemd/system Added tag(s) patch. -- 1034230: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1034230 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1034230: fail2ban: dh_installsystemd doesn't handle files in /usr/lib/systemd/system
Control: tags -1 patch On Tue, 11 Apr 2023 15:43:51 +0200 Andreas Henriksson wrote: > Wrong path is used at: > https://sources.debian.org/src/fail2ban/1.0.2-1/debian/rules/#L50 > > Note that the path will likely change again in the future, so rather > than hard-coding a path please consider finding the path via: > pkg-config --variable=systemdsystemunitdir systemd > > (Note: you'll need to build-dep on pkg-config and systemd, for > systemd.pc) > > Regards, > Andreas Henriksson > > Attaching a patch, the git repo seems to be in an inconsistent state/diverged from the archive. diff --git a/debian/control b/debian/control index fe386199..0b8c5421 100644 --- a/debian/control +++ b/debian/control @@ -13,6 +13,8 @@ Build-Depends: , python3-pyinotify , sqlite3 , 2to3 + , pkg-config + , systemd Homepage: https://www.fail2ban.org Vcs-Git: https://salsa.debian.org/python-team/packages/fail2ban.git Vcs-Browser: https://salsa.debian.org/python-team/packages/fail2ban diff --git a/debian/rules b/debian/rules index a2dd769c..3c0391ef 100755 --- a/debian/rules +++ b/debian/rules @@ -16,7 +16,7 @@ export PYBUILD_DISABLE_python2=1 DESTDIR=$(CURDIR)/debian/fail2ban PYVERSION=$(shell py3versions -dv) - +SYSTEMD_SYSTEM_UNIT_DIR = $(shell pkg-config --variable=systemdsystemunitdir systemd) override_dh_clean: rm -rf fail2ban.egg-info -rm debian/fail2ban.init @@ -45,11 +45,11 @@ override_dh_install: install -d $(DESTDIR)/usr/share/bash-completion/completions install -m 644 files/bash-completion $(DESTDIR)/usr/share/bash-completion/completions/fail2ban : # Install systemd files - install -d $(DESTDIR)/usr/lib/systemd/system/ + install -d $(DESTDIR)$(SYSTEMD_SYSTEM_UNIT_DIR) install -d $(DESTDIR)/usr/lib/tmpfiles.d - install -m 644 build/fail2ban.service $(DESTDIR)/usr/lib/systemd/system + install -m 644 build/fail2ban.service $(DESTDIR)$(SYSTEMD_SYSTEM_UNIT_DIR) install -m 644 files/fail2ban-tmpfiles.conf $(DESTDIR)/usr/lib/tmpfiles.d - install -d $(DESTDIR)/usr/lib/systemd/system + install -d $(DESTDIR)$(SYSTEMD_SYSTEM_UNIT_DIR) : # Install default jail enabler install -m 644 debian/debian-files/jail.d_defaults-debian.conf $(DESTDIR)/etc/fail2ban/jail.d/defaults-debian.conf dh_install
Processed: reassign 1034530 to mrtg, closing 821577
Processing commands for cont...@bugs.debian.org: > reassign 1034530 mrtg 2.17.10-4 Bug #1034530 [mtrg] mtrg: mrtg.postinst uses useradd/groupadd (passwd) while mrtg.postrm uses deluser/delgroup (adduser) Warning: Unknown package 'mtrg' Bug reassigned from package 'mtrg' to 'mrtg'. No longer marked as found in versions 2.17.10-4. Ignoring request to alter fixed versions of bug #1034530 to the same values previously set Bug #1034530 [mrtg] mtrg: mrtg.postinst uses useradd/groupadd (passwd) while mrtg.postrm uses deluser/delgroup (adduser) Marked as found in versions mrtg/2.17.10-4. > close 821577 1.1.7-1+rm Bug #821577 [php-google-api-php-client] php-google-api-php-client: PHP 7.0 Transition Warning: Unknown package 'php-google-api-php-client' There is no source info for the package 'php-google-api-php-client' at version '1.1.7-1+rm' with architecture '' Unable to make a source version for version '1.1.7-1+rm' Marked as fixed in versions 1.1.7-1+rm. Warning: Unknown package 'php-google-api-php-client' Bug #821577 [php-google-api-php-client] php-google-api-php-client: PHP 7.0 Transition Warning: Unknown package 'php-google-api-php-client' Marked Bug as done Warning: Unknown package 'php-google-api-php-client' > thanks Stopping processing here. Please contact me if you need assistance. -- 1034530: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1034530 821577: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=821577 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#769218: marked as done (gcc-4.9: FTBFS in jessie: Error! CRCs do not match! Got 264aca47, expected 95962ba4)
Your message dated Tue, 18 Apr 2023 11:53:21 +0200
with message-id
and subject line gcc-4.9 has been removed from Debian
has caused the Debian Bug report #769218,
regarding gcc-4.9: FTBFS in jessie: Error! CRCs do not match! Got 264aca47,
expected 95962ba4
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.)
--
769218: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=769218
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: gcc-4.9
Version: 4.9.1-19
Severity: serious
Tags: jessie sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-2014-11-11 qa-ftbfs
Justification: FTBFS in jessie on amd64
Hi,
During a rebuild of all packages in jessie (in a jessie chroot, not a
sid chroot), your package failed to build on amd64.
Relevant part (hopefully):
> make[2]: Entering directory '/«PKGBUILDDIR»/build/x86_64-linux-gnu/libjava'
> rm -f src.zip
> here=`pwd`; \
> ( \
> ( cd ../../../src/libjava/classpath; \
> find java gnu javax org sun -name '*.java' -print | \
> while read file; do \
> echo "x-C" | sed -e 's/^.//'; \
> echo ../../../src/libjava/classpath; \
> echo $file; \
> done ); \
> ( cd ../../../src/libjava/classpath/external/sax; \
> find org -name '*.java' -print | \
> while read file; do \
> echo "x-C" | sed -e 's/^.//'; \
> echo ../../../src/libjava/classpath/external/sax; \
> echo $file; \
> done ); \
> ( cd ../../../src/libjava/classpath/external/relaxngDatatype; \
> find org -name '*.java' -print | \
> while read file; do \
> echo "x-C" | sed -e 's/^.//'; \
> echo ../../../src/libjava/classpath/external/relaxngDatatype; \
> echo $file; \
> done ); \
> ( cd ../../../src/libjava/classpath/external/w3c_dom; \
> find org -name '*.java' -print | \
> while read file; do \
> echo "x-C" | sed -e 's/^.//'; \
> echo ../../../src/libjava/classpath/external/w3c_dom; \
> echo $file; \
> done ); \
> ( cd classpath; \
> find gnu java -name '*.java' -print | \
> while read file; do \
> echo "x-C" | sed -e 's/^.//'; \
> echo `pwd`; \
> echo $file; \
> done ); \
> ) | \
> jar -cfM@ $here/src.zip
> find: `java': No such file or directory
> here=`pwd`; \
> ( \
> ( cd ../../../src/libjava; \
> find gnu java -name '*.java' -print | \
> while read file; do \
> echo "x-C" | sed -e 's/^.//'; \
> echo ../../../src/libjava; \
> echo $file; \
> done ); \
> ) | \
> jar -ufM@ $here/src.zip
> make[2]: Leaving directory '/«PKGBUILDDIR»/build/x86_64-linux-gnu/libjava'
> touch stamps/05-build-javasrc-stamp
> dh_testdir
> dh_testroot
> dh_installdirs -pgcj-4.9-source usr/share/java
> /usr/lib/jvm/java-1.5.0-gcj-4.9-amd64
> cp -p /«PKGBUILDDIR»/build/x86_64-linux-gnu/libjava/src.zip \
>debian/gcj-4.9-source/usr/share/java/libgcj-src-4.9.zip
> dh_link -pgcj-4.9-source \
> usr/share/java/libgcj-src-4.9.zip \
> /usr/lib/jvm/java-1.5.0-gcj-4.9-amd64/src.zip
> debian/dh_doclink -pgcj-4.9-source gcc-4.9-base
> WARNING: removing doc directory gcj-4.9-source
> debian/dh_rmemptydirs -pgcj-4.9-source
> dh_compress -pgcj-4.9-source
> dh_fixperms -pgcj-4.9-source
> dh_gencontrol -pgcj-4.9-source -- -v4.9.1-19 '-Vlibgcc:Version=1:4.9.1-19'
> '-Vgcc:Version=4.9.1-19' '-Vgcc:EpochVersion=1:4.9.1-19'
> '-Vgcc:SoftVersion=4.9' '-Vgdc:Version=4.9.1-19' '-Vgcj:Version=4.9.1-19'
> '-Vgcj:SoftVersion=4.9' '-Vgcj:BaseVersion=4.9' '-Vgnat:Version=4.9.1-19'
> '-Vbinutils:Version=2.24.90.20141023' '-Vdep:libgcc=libgcc1 (>= 1:4.9.1-19)'
> '-Vdep:libgccdev=libgcc-4.9-dev (>= 4.9.1-19)' '-Vdep:libgccbiarch=lib32gcc1
> (>= 1:4.9.1-19), libx32gcc1 (>= 1:4.9.1-19)'
> '-Vdep:libgccbiarchdev=lib32gcc-4.9-dev (= ${gcc:Version}), libx32gcc-4.9-dev
> (= ${gcc:Version})' '-Vdep:libc=libc6 (>= 2.11)' '-Vdep:libcdev=libc6-dev (>=
> 2.13-5)' '-Vdep:libcbiarch=${shlibs:Depends}'
> '-Vdep:libcbiarchdev=libc6-dev-i386 (>= 2.11), libc6-dev-x32 (>= 2.11)'
> '-Vdep:libunwinddev=' '-Vdep:libcxxbiarchdev=lib32stdc++-4.9-dev (=
> ${gcc:Version}), libx32stdc++-4.9-dev (= ${gcc:Version})'
> '-Vdep:libcxxbiarchdbg=lib32stdc++6-4.9-dbg (>= ${gcc:Version}),
> libx32stdc++6-4.9-dbg (>= ${gcc:Version})' '-Vdep:libgnat='
> '-Vdep:ecj=ecj-gcj, libecj-java-gcj (>= 3.5.1)' '-Vdep:libcloog='
> '-Vgcc:multilib=gcc-4.9-multilib' '-Vgxx:multilib=g++-4.9-multilib'
> '-Vgobjc:multilib=gobjc-4.9-multilib'
> '-Vgobjcxx:multilib=gobjc++-4.9-multilib'
> '-Vgfortran:multilib=gfortran-4.9-multilib' '-Vdep:gold=binutils-gold (>=
> 2.24.90.20141023)' '-Vdep:libgomp=libgomp1 (>= ${gcc:Version})'
> '-Vdep:libitm=libitm1 (>= ${gc
Bug#860044: marked as done (icinga-web: FTBFS: checking if php has xsl module... configure: error: not found)
Your message dated Tue, 18 Apr 2023 11:43:17 +0200 with message-id and subject line icinga-web has been removed from Debian has caused the Debian Bug report #860044, regarding icinga-web: FTBFS: checking if php has xsl module... configure: error: not found 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.) -- 860044: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=860044 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: icinga-web Version: 1.13.1-2.1 Severity: serious Justification: fails to build from source User: reproducible-bui...@lists.alioth.debian.org Usertags: ftbfs X-Debbugs-Cc: reproducible-b...@lists.alioth.debian.org Dear Maintainer, icinga-web fails to build from source in unstable/amd64: […] checking for a BSD-compatible install... /usr/bin/install -c checking for grep that handles long lines and -e... /bin/grep checking for a sed that does not truncate output... /bin/sed checking for php... /usr/bin/php checking for phing... not found configure: WARNING: binary phing not found in PATH checking if php has sockets module... found checking if php has xsl module... configure: error: not found debian/rules:22: recipe for target 'override_dh_auto_configure' failed make[1]: *** [override_dh_auto_configure] Error 1 make[1]: Leaving directory '«BUILDDIR»' debian/rules:15: recipe for target 'build' failed make: *** [build] Error 2 dpkg-buildpackage: error: debian/rules build gave error exit status 2 […] The full build log is attached. Regards, -- ,''`. : :' : Chris Lamb `. `'` la...@debian.org / chris-lamb.co.uk `- icinga-web.1.13.1-2.1.unstable.amd64.log.txt.gz Description: Binary data --- End Message --- --- Begin Message --- Version: 1.13.1-2.1+rm icinga-web was last released with Debian 8 (jessie) in April 2015 and was removed from the Debian archive afterwards. I'm closing the remaining bug reports now. Andreas--- End Message ---
Bug#851671: marked as done (icinga-web: Mysql error: Specified key was too long; max key length is 767 bytes)
Your message dated Tue, 18 Apr 2023 11:43:17 +0200 with message-id and subject line icinga-web has been removed from Debian has caused the Debian Bug report #851671, regarding icinga-web: Mysql error: Specified key was too long; max key length is 767 bytes 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.) -- 851671: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=851671 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: icinga-web Version: 1.13.1-2 Severity: normal Dear Maintainer, *** Reporter, please consider answering these questions, where appropriate *** On installing icinga-web, with default-mysql-server already freshly installed I receive the message mysql said: ERROR 1071 (42000) at line 18: Specified key was too long; max key length is 767 bytes The problem would appear to be in line 18 of /usr/share/dbconfig-common/data/icinga-web/install/mysql which attempts to create the nsm_session table. With the default UTF encoding it seems varchar(255) is larger than session_id is allowed to be. I have worked around it by specifying varchar(125) A dpkg-reconfigure icinga-web then succeeded -- System Information: Debian Release: stretch/sid APT prefers testing APT policy: (500, 'testing') Architecture: armel (armv5tel) Kernel: Linux 4.8.0-2-marvell Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages icinga-web depends on: ii dbconfig-common 2.0.7 ii debconf [debconf-2.0] 1.5.59 ii php 1:7.0+49 ii php-gd 1:7.0+49 ii php-mysql 1:7.0+49 ii php7.0 [php]7.0.14-2 ii php7.0-cli [php-cli]7.0.14-2 ii php7.0-gd [php-gd] 7.0.14-2 ii php7.0-json [php-json] 7.0.14-2 ii php7.0-xml [php-xsl]7.0.14-2 ii ucf 3.0036 Versions of packages icinga-web recommends: ii apache2 [httpd] 2.4.25-1 pn mysql-client | postgresql-client Versions of packages icinga-web suggests: pn icinga-doc ii icinga-web-config-icinga2-ido-mysql 1.13.1-2 pn nagios-images -- Configuration Files: /etc/icinga-web/conf.d/access.xml [Errno 13] Permission denied: '/etc/icinga-web/conf.d/access.xml' /etc/icinga-web/conf.d/auth.xml [Errno 13] Permission denied: '/etc/icinga-web/conf.d/auth.xml' /etc/icinga-web/conf.d/databases.xml [Errno 13] Permission denied: '/etc/icinga-web/conf.d/databases.xml' /etc/icinga-web/conf.d/module_reporting.xml [Errno 13] Permission denied: '/etc/icinga-web/conf.d/module_reporting.xml' -- debconf information: icinga-web/remove-error: abort * icinga-web/dbconfig-reinstall: true * icinga-web/dbconfig-install: true icinga-web/internal/skip-preseed: false icinga-web/remote/newhost: * icinga-web/mysql/method: Unix socket icinga-web/remote/port: * icinga-web/db/dbname: icinga_web * icinga-web/passwords-do-not-match: * icinga-web/db/app-user: icinga_web@localhost * icinga-web/database-type: mysql * icinga-web/install-error: ignore * icinga-web/rootpassword-mismatch: * icinga-web/mysql/admin-user: root icinga-web/upgrade-error: abort icinga-web/missing-db-package-error: abort icinga-web/purge: false icinga-web/dbconfig-remove: true icinga-web/remote/host: localhost icinga-web/upgrade-backup: true icinga-web/dbconfig-upgrade: true icinga-web/internal/reconfiguring: false --- End Message --- --- Begin Message --- Version: 1.13.1-2.1+rm icinga-web was last released with Debian 8 (jessie) in April 2015 and was removed from the Debian archive afterwards. I'm closing the remaining bug reports now. Andreas--- End Message ---
Processed: Re: Bug#1034524: libretro-bsnes-mercury: uses invalid architecture wildcards
Processing control commands: > severity -1 important Bug #1034524 [src:libretro-bsnes-mercury] libretro-bsnes-mercury: uses invalid architecture wildcards Severity set to 'important' from 'serious' -- 1034524: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1034524 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1034524: libretro-bsnes-mercury: uses invalid architecture wildcards
Control: severity -1 important On Mon, Apr 17, 2023 at 05:32:06PM +0100, Graham Inggs wrote: > Source: libretro-bsnes-mercury > Version: 094+git20220807-6 > Severity: serious > > Hi Maintainer > > Since the upload of 094+git20220807-6, the > kodi-game-libretro-bsnes-mercury-* binary packages are no longer built > on armel and armhf [1][2][3]. This is due to the use of invalid > architecture wildcards 'any-armel' and 'any-armhf'. These should be > replaced by 'any-arm' for each of three This is an unfortunate mistake on my part, but given the stage we're at in the release process, the fact these are leaf packages and the fact the packages didn't ship as part of bullseye I don't think this counts as release critical. > kodi-game-libretro-bsnes-mercury-* binary packages in debian/control, > as follows: > > -Architecture: any-amd64 any-arm64 any-armel any-armhf any-i386 > any-powerpc any-ppc64 any-ppc64el any-riscv64 any-s390x any-sparc64 > > +Architecture: any-amd64 any-arm64 any-arm any-i386 any-powerpc > any-ppc64 any-ppc64el any-riscv64 any-s390x any-sparc64 > > Regards > Graham > > > [1] > https://packages.debian.org/unstable/kodi-game-libretro-bsnes-mercury-accuracy > [2] > https://packages.debian.org/unstable/kodi-game-libretro-bsnes-mercury-balanced > [3] > https://packages.debian.org/unstable/kodi-game-libretro-bsnes-mercury-performance J. -- ... If we sleep together, will you like me better?
Bug#1034558: rnp: CVE-2023-29479 VE-2023-29480
Source: rnp Version: 0.16.2-1 Severity: grave Tags: security upstream Justification: user security hole X-Debbugs-Cc: car...@debian.org, Debian Security Team *** /tmp/rnp.reportbug Package: rnp X-Debbugs-CC: t...@security.debian.org Severity: grave Tags: security Hi, The following vulnerabilities were published for rnp, [0] and [1]. The first one was as well affecting mentioned in the recent thunderbird mfsa. If you fix the vulnerabilities please also make sure to include the CVE (Common Vulnerabilities & Exposures) ids in your changelog entry. For further information see: [0] https://security-tracker.debian.org/tracker/CVE-2023-29479 https://www.cve.org/CVERecord?id=CVE-2023-29479 [1] https://security-tracker.debian.org/tracker/CVE-2023-29480 https://www.cve.org/CVERecord?id=CVE-2023-29480 [2] https://www.rnpgp.org/blog/2023-04-13-rnp-release-0-16-3/ Regards, Salvatore
