Processed: retitle 1072391 to python3-specreduce: ships /usr/lib/python3/dist-packages/build/lib/docs/conf.py and /usr/lib/python3/dist-packages/docs/conf.py ...
Processing commands for cont...@bugs.debian.org: > retitle 1072391 python3-specreduce: ships > /usr/lib/python3/dist-packages/build/lib/docs/conf.py and > /usr/lib/python3/dist-packages/docs/conf.py Bug #1072391 [python3-specreduce] python3-specreduce: ships /usr/lib/python3/dist-packages/build/lib/docs/conf.py Changed Bug title to 'python3-specreduce: ships /usr/lib/python3/dist-packages/build/lib/docs/conf.py and /usr/lib/python3/dist-packages/docs/conf.py' from 'python3-specreduce: ships /usr/lib/python3/dist-packages/build/lib/docs/conf.py'. > retitle 1072507 python3-google-auth-oauthlib: ships > /usr/lib/python3/dist-packages/docs/conf.py Bug #1072507 [python3-google-auth-oauthlib] python3-google-auth-oauthlib: ships /usr/lib/python3/dist-packages/build/lib/docs/conf.py Changed Bug title to 'python3-google-auth-oauthlib: ships /usr/lib/python3/dist-packages/docs/conf.py' from 'python3-google-auth-oauthlib: ships /usr/lib/python3/dist-packages/build/lib/docs/conf.py'. > thanks Stopping processing here. Please contact me if you need assistance. -- 1072391: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1072391 1072507: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1072507 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Re: python3-specreduce has an undeclared file conflict
Processing control commands: > retitle -1 python3-specreduce: ships > /usr/lib/python3/dist-packages/build/lib/docs/conf.py Bug #1072391 [python3-specreduce] python3-specreduce has an undeclared file conflict Changed Bug title to 'python3-specreduce: ships /usr/lib/python3/dist-packages/build/lib/docs/conf.py' from 'python3-specreduce has an undeclared file conflict'. -- 1072391: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1072391 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1072391: python3-specreduce has an undeclared file conflict
Followup-For: Bug #1072391 Control: retitle -1 python3-specreduce: ships /usr/lib/python3/dist-packages/build/lib/docs/conf.py /usr/lib/python3/dist-packages/build/lib/docs/conf.py is an overly generic name (and outside the package's namespace) that shouldn't be shipped in any package. Andreas
Bug#1072507: python3-google-auth-oauthlib: ships /usr/lib/python3/dist-packages/build/lib/docs/conf.py
Package: python3-google-auth-oauthlib Version: 1.2.0-1 Severity: serious User: debian...@lists.debian.org Usertags: piuparts fileconflict Hi, during a test with piuparts I noticed your package failed to install because it tries to overwrite other packages files. Preparing to unpack .../python3-google-auth-oauthlib_1.2.0-1_all.deb ... Unpacking python3-google-auth-oauthlib (1.2.0-1) ... dpkg: error processing archive /var/cache/apt/archives/python3-google-auth-oauthlib_1.2.0-1_all.deb (--unpack): trying to overwrite '/usr/lib/python3/dist-packages/docs/conf.py', which is also in package python3-specreduce 1.4.0-1 Errors were encountered while processing: /var/cache/apt/archives/python3-google-auth-oauthlib_1.2.0-1_all.deb /usr/lib/python3/dist-packages/build/lib/docs/conf.py is an overly generic name (and outside the package's namespace) that shouldn't be shipped in any package. There could be even more conflicting files. cheers, Andreas
Bug#1072506: pipenv: ships /usr/lib/python3/dist-packages/build/lib/docs/conf.py
Package: pipenv Version: 2023.12.1+ds-1 Severity: serious User: debian...@lists.debian.org Usertags: piuparts fileconflict Hi, during a test with piuparts I noticed your package failed to install because it tries to overwrite other packages files. Unpacking pipenv (2023.12.1+ds-1) ... dpkg: error processing archive /var/cache/apt/archives/pipenv_2023.12.1+ds-1_all.deb (--unpack): trying to overwrite '/usr/lib/python3/dist-packages/build/lib/docs/conf.py', which is also in package python3-specreduce 1.4.0-1 Errors were encountered while processing: /var/cache/apt/archives/pipenv_2023.12.1+ds-1_all.deb /usr/lib/python3/dist-packages/build/lib/docs/conf.py is an overly generic name (and outside the package's namespace) that shouldn't be shipped in any package. There could be even more conflicting files. cheers, Andreas
Bug#1071567: marked as done (libssh: ISC license missing)
Your message dated Mon, 03 Jun 2024 05:50:50 + with message-id and subject line Bug#1071567: fixed in libssh 0.10.6-3 has caused the Debian Bug report #1071567, regarding libssh: ISC license missing 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.) -- 1071567: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1071567 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: libssh Version: 0.9.5-1 Severity: serious src/external/bcrypt_pbkdf.c is licensed under the ISC license, which is missing from debian/copyright. --- End Message --- --- Begin Message --- Source: libssh Source-Version: 0.10.6-3 Done: Martin Pitt We believe that the bug you reported is fixed in the latest version of libssh, 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 1071...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Martin Pitt (supplier of updated libssh 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: Mon, 03 Jun 2024 07:32:19 +0200 Source: libssh Architecture: source Version: 0.10.6-3 Distribution: unstable Urgency: medium Maintainer: Laurent Bigonville Changed-By: Martin Pitt Closes: 1071567 Changes: libssh (0.10.6-3) unstable; urgency=medium . * debian/copyright: Add bcrypt_pbkdf.c (Closes: #1071567) Checksums-Sha1: f464b0532e465a37d5c4ac5175bf1270a6db8cea 2742 libssh_0.10.6-3.dsc 110d70411e22ba5e069021f4fe1e92d52885cdc0 30740 libssh_0.10.6-3.debian.tar.xz 3b19af3dd6459dbe077956fa3a5c423234d3a6a6 6621 libssh_0.10.6-3_source.buildinfo Checksums-Sha256: 699d81a0ca918059602f532ee3db7b6c38aa2601d8f5a1a5e46f61e42d01b32d 2742 libssh_0.10.6-3.dsc cbbf829687a617a74915618cf04263ca1dec382400d5d611bb1287958885c75f 30740 libssh_0.10.6-3.debian.tar.xz 33e2ba22bd8a01d5330d166af6d8b106fb08cae106b5566f157e6bfd5e5e98e9 6621 libssh_0.10.6-3_source.buildinfo Files: 01fc703f6697e6ece92b7d46b3b9a748 2742 libs optional libssh_0.10.6-3.dsc 9171a472604888fc280da0db729b669f 30740 libs optional libssh_0.10.6-3.debian.tar.xz 066e3b1c1145d6e3802259441876609e 6621 libs optional libssh_0.10.6-3_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEbEuHi35jHxYFV8PN7nvd5LhrVxMFAmZdVaIACgkQ7nvd5Lhr VxOCuQ//XV4s//SUkdquJH84VNylCJOigWHTEendNJPSwW4FWQFFDKBbAAuPnUqJ acwjv2C+16iHHU6gs01by+Se9nK/1JHiVPDhLeVE6rI8YZ0Y1Yl59wS3wqyV672A yXEHuBk5UdIQlB5eaeQdf6r5+w3WQ/N6Cey+VJJiB5KGGTm5sWGhmjCETGsRJHBo 9Fc/B9YUfgxctCLscJ/XJ6+XlA0titH0iFpK4okW96bEyBrx9rK1fqDtuOdysnEj qcEcMIDm4D+yp2xEanY4fcPxFumGys1SMz5vZ9ajea3oMiuBywT7HEpTGMi8eKsz KZVAZu8/R4tePmqnqieb4TDxPaFqhrUp5NpRSLIm53DJ/cBqXGH/jbrKQ7FHfp92 SufWnBsGWMGJngaW05au9meLvg3fRcYNJxK5j+/gDXJdveoTwwRtoAv6BF0f1gYP Hp+ks8p4jqRQIIJCciIcZfEc4CeXfwB4/+gJ4CLMKrP0CcK0INRI0wnkHrbY7OXj mLWIUq6cCP2Bf4m8QpPdBUtzSxdWq764hBX0EsXheN58HpQGO7YaGPRkYGWwIkie GE6Y8/PmWOR+aIsNGkxWeypCXEIBIPYqUFqkUCcfBK56tciutPRBSBpZugloln9h /KT9X0EPmlTikk+ZgJlZyynb1bYVg38F7lKpllJT43n7obn4rd4= =+Yss -END PGP SIGNATURE- pgpuA7i4AujrU.pgp Description: PGP signature --- End Message ---
Bug#1071628: marked as done (python-pymysql: CVE-2024-36039)
Your message dated Mon, 03 Jun 2024 05:33:39 + with message-id and subject line Bug#1071628: fixed in python-pymysql 0.9.3-2+deb11u1 has caused the Debian Bug report #1071628, regarding python-pymysql: CVE-2024-36039 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.) -- 1071628: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1071628 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: python-pymysql X-Debbugs-CC: t...@security.debian.org Severity: grave Tags: security Hi, The following vulnerability was published for python-pymysql. We should also fix this in a DSA, could you prepare debdiffs for bookworm-security and bullseye-security? CVE-2024-36039[0]: | PyMySQL through 1.1.0 allows SQL injection if used with untrusted | JSON input because keys are not escaped by escape_dict. https://github.com/advisories/GHSA-v9hf-5j83-6xpp https://github.com/PyMySQL/PyMySQL/commit/521e40050cb386a499f68f483fefd144c493053c (v1.1.1) If you fix the vulnerability please also make sure to include the CVE (Common Vulnerabilities & Exposures) id in your changelog entry. For further information see: [0] https://security-tracker.debian.org/tracker/CVE-2024-36039 https://www.cve.org/CVERecord?id=CVE-2024-36039 Please adjust the affected versions in the BTS as needed. --- End Message --- --- Begin Message --- Source: python-pymysql Source-Version: 0.9.3-2+deb11u1 Done: Thomas Goirand We believe that the bug you reported is fixed in the latest version of python-pymysql, 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 1071...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Thomas Goirand (supplier of updated python-pymysql 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, 28 May 2024 08:56:57 +0200 Source: python-pymysql Architecture: source Version: 0.9.3-2+deb11u1 Distribution: bullseye-security Urgency: medium Maintainer: Debian Python Modules Team Changed-By: Thomas Goirand Closes: 1071628 Changes: python-pymysql (0.9.3-2+deb11u1) bullseye-security; urgency=medium . * CVE-2024-36039: PyMySQL through 1.1.0 allows SQL injection if used with untrusted JSON input because keys are not escaped by escape_dict. Applied upstream patch: forbid_dict_parameter.patch (Closes: #1071628). Checksums-Sha1: 357ba0df0ea70e74d0756d7a7138876b80f7f5d4 2324 python-pymysql_0.9.3-2+deb11u1.dsc 26207ac507e7b9593816d9b060e52d7a9a9d2eec 86715 python-pymysql_0.9.3.orig.tar.gz 39eca8afcd43dc3670c08dfe9073298933be4c30 6648 python-pymysql_0.9.3-2+deb11u1.debian.tar.xz 3954f2d613ca33a11791dd0964be91318e845357 9750 python-pymysql_0.9.3-2+deb11u1_amd64.buildinfo Checksums-Sha256: 9daa9535965b2ea9dff2034a2feb571d657ec2eaa60bb68a289c479d1cadd569 2324 python-pymysql_0.9.3-2+deb11u1.dsc 5a85599a69b51db185f9447ba5034501482496e481574bce972c7dcb5abe1d57 86715 python-pymysql_0.9.3.orig.tar.gz ca3565d650c580e509598b5e7dfb550c16c863e3c739d33b52757e6bf8bc483c 6648 python-pymysql_0.9.3-2+deb11u1.debian.tar.xz 07195d35181d6fb4356782121c345e9b9156e1861777cfc17a68f9f9a64dffbc 9750 python-pymysql_0.9.3-2+deb11u1_amd64.buildinfo Files: 1b4617b1718a045ffcd17122130c6b67 2324 python optional python-pymysql_0.9.3-2+deb11u1.dsc 7afad735628571b6fffd74086ce451b7 86715 python optional python-pymysql_0.9.3.orig.tar.gz 65545c35069130e979b35320e91c9182 6648 python optional python-pymysql_0.9.3-2+deb11u1.debian.tar.xz e9763923b6b442a29b8de2ab7e6c7b04 9750 python optional python-pymysql_0.9.3-2+deb11u1_amd64.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEEoLGp81CJVhMOekJc1BatFaxrQ/4FAmZWzvMACgkQ1BatFaxr Q/4LdRAAkRb25uh0rg3P+SHY66zh1UtAI0FzFBW1K39JO44Usu/39rch8KWONR3z izrPSDia2dgbrcs6EVlJO4kp/9RY1Ri0GDrx+Aeuu8GJDgFDEYTx0qwOmGBJMpXU oQ8awoAHlKpm4maLNx9MonFDNIuZRvVS2iDAuDohxXrN+WPbGd8izRdTahmvFOIA 0sfa4uLwwrspV+xxte+3edr8nGRCu3UlC3m5mW+s0pRvltqZ7pAKBocqCNEua3hm jRELrRgfINjzgdol24Dc78J9AE3xEBKrW0g5jW3HeHdV5yFpiGaegWQq2r+s2lx7 YayUk09WoFP63/hSmhlhSuVo3hlTy4qZO0SzKqPjNlKanCsL2l9lPwbjh8O+iLex 2tQzmUYwm5OiZ0nUJ4CpYSUYSjvZdKo6oTCvPx0Y8fSP60xmYWH2nL3w8RN271st zEfPhHs8RIEpidDSHu1jWYfzVT0iaey71HxPJdFvZWZ3Xr/sYxYUV
Bug#1071628: marked as done (python-pymysql: CVE-2024-36039)
Your message dated Mon, 03 Jun 2024 05:32:57 + with message-id and subject line Bug#1071628: fixed in python-pymysql 1.0.2-2+deb12u1 has caused the Debian Bug report #1071628, regarding python-pymysql: CVE-2024-36039 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.) -- 1071628: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1071628 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: python-pymysql X-Debbugs-CC: t...@security.debian.org Severity: grave Tags: security Hi, The following vulnerability was published for python-pymysql. We should also fix this in a DSA, could you prepare debdiffs for bookworm-security and bullseye-security? CVE-2024-36039[0]: | PyMySQL through 1.1.0 allows SQL injection if used with untrusted | JSON input because keys are not escaped by escape_dict. https://github.com/advisories/GHSA-v9hf-5j83-6xpp https://github.com/PyMySQL/PyMySQL/commit/521e40050cb386a499f68f483fefd144c493053c (v1.1.1) If you fix the vulnerability please also make sure to include the CVE (Common Vulnerabilities & Exposures) id in your changelog entry. For further information see: [0] https://security-tracker.debian.org/tracker/CVE-2024-36039 https://www.cve.org/CVERecord?id=CVE-2024-36039 Please adjust the affected versions in the BTS as needed. --- End Message --- --- Begin Message --- Source: python-pymysql Source-Version: 1.0.2-2+deb12u1 Done: Thomas Goirand We believe that the bug you reported is fixed in the latest version of python-pymysql, 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 1071...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Thomas Goirand (supplier of updated python-pymysql 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, 28 May 2024 08:15:32 +0200 Source: python-pymysql Architecture: source Version: 1.0.2-2+deb12u1 Distribution: bookworm-security Urgency: medium Maintainer: Debian Python Team Changed-By: Thomas Goirand Closes: 1071628 Changes: python-pymysql (1.0.2-2+deb12u1) bookworm-security; urgency=medium . * CVE-2024-36039: PyMySQL through 1.1.0 allows SQL injection if used with untrusted JSON input because keys are not escaped by escape_dict. Applied upstream patch: forbid_dict_parameter.patch (Closes: #1071628). Checksums-Sha1: 6ec696841cea1194260258aec8240ba940819b9c 2306 python-pymysql_1.0.2-2+deb12u1.dsc 3269e63ad14bc5ad5f1145a7b2e1b3f12da83f77 84985 python-pymysql_1.0.2.orig.tar.gz d29beeba5f5e6a1d155847510c8bc48bf29e94e1 7800 python-pymysql_1.0.2-2+deb12u1.debian.tar.xz 81d3a7bf817a8d6492da52fb74a0a408de6da04e 9754 python-pymysql_1.0.2-2+deb12u1_amd64.buildinfo Checksums-Sha256: 74dc5ec5575eaf7e50cf14ff665e0e59c29ff310fbe7a46d57e963dbc42ef332 2306 python-pymysql_1.0.2-2+deb12u1.dsc 44b19ebe16baa52b74b7d835bdaaf732bb83725339dca307fe0900439adddb6d 84985 python-pymysql_1.0.2.orig.tar.gz a56cfb010b18744ea3324faf719912ccc39f6f6dfb071fe72a797e1f8f03e99f 7800 python-pymysql_1.0.2-2+deb12u1.debian.tar.xz 2ac63a6638f0ee056883ae61be04684d1ded8ae9a0043516bf40d328c61fd9d5 9754 python-pymysql_1.0.2-2+deb12u1_amd64.buildinfo Files: 2aa5407a565a228eb3ce7f82f001ead7 2306 python optional python-pymysql_1.0.2-2+deb12u1.dsc 53c2cf64b0a583dbd14c24d3a8ac46ca 84985 python optional python-pymysql_1.0.2.orig.tar.gz 8e9f153e6b85d51192a3761d9863757c 7800 python optional python-pymysql_1.0.2-2+deb12u1.debian.tar.xz 3ba027da8f3d5d394babe013ab1d1641 9754 python optional python-pymysql_1.0.2-2+deb12u1_amd64.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEEoLGp81CJVhMOekJc1BatFaxrQ/4FAmZWz0kACgkQ1BatFaxr Q/767Q//WUNozOnFTCLW9SnU7WqtgQnB/yBRgknK5VImy5SEn6RMdzXIVstkabU8 J1ltzrpI5xe6iTW/mlr1nQFuy7x3Z/CUhk+CLu13XNAp1oLmG5fzBRdje47uHP9l fU/fpL4BzLjCwpsu9h3L9VYj/9QiVdxC5WMjY/8KnqvcEE6xaoU8X+fGaC6osS2D m3xuEqecCU5PwzY1u2r3YEQaB5HadAGgKvM5Cl5DB7hP4crTpzPjXLFwkRTRIj20 zesVwDEdMVw7e3H9pVC+rwpn4QNp5MxKPgtj6yb16mFBicVk+neUACc34U546yWv gWraGRWIlDcpPIDJMGdQBF28W7vqQlNsUF8RlyzbQaWgQ5blYGpmflEo5aehhir4 vhP9I/0Mmdnvx4lZCpH5GIYke+oZAD0rt4AiioKAu9iWzatZ6syxHJFoYqnRWn36 OBi7GeGVQzjJJmIEpsqqIcQVcnpLJApIUObosJJ6ojzi39a9y+rxw1xCqhI+hG
Bug#1070447: sdpa: dependency generation does not account for t64 changes
Dear Sebastian Ramacher,
Thank you very much for your support on the SDPA package.
I am still trying to contact the mentor of the package,
but I cannot get a reply.
Is there any way to contact the mentor?
Thank you very much in advance.
Best regards,
Makoto Yamashita
2024年5月5日(日) 22:39 Sebastian Ramacher :
>
> Source: sdpa
> Version: 7.3.16+dfsg-1
> Severity: serious
> X-Debbugs-Cc: sramac...@debian.org
>
> Dependencies on libmumps-seq are produced using ${mumps-seq:Version}
> which does not include the changes from the t64 transition. Please adopt
> the dependency generation accordingly.
>
> Cheers
> --
> Sebastian Ramacher
Bug#1061743: Gramps in Debian
Hi both, Thanks so much for doing this. On 27.05.2024 19.49, Dr. Tobias Quathamer wrote: Am 27.05.24 um 15:38 schrieb IOhannes m zmölnig (Debian GNU|Linux): On 5/26/24 23:56, Dr. Tobias Quathamer wrote: The package builds on my machine, although I had to disable a single test for now. You'll find it in the newly created patch. Maybe you have an idea what's causing the failure, so it can be fixed properly. https://gramps-project.org/bugs/view.php?id=13305 i think this is just a wrong assumption on the side of the upstream testsuite (shadowed by their workflows). upstream evades this by ensuring that "~/.gramps/" is there before running the tests (both in their GitHub action, and in their debian/ packaging). i think that for now the proper resolution for the problem is to simply do a `mkdir "$CURDIR)/build/.gramps` before running the tests. (which i've now pushed to the 'experimental' branch) Great, thanks! That's a cleaner approach. as a sidenote: the testsuite now creates a *very* verbose buildlog (~420MB). is that ok? gf,madsr IOhannes Hm, I guess that's because of the "--verbose" option when running the tests. However, the buildlog has been similarly large in v5.1.6 as well. Could that to be due to the switch from nosetest to unittest? Maybe the --verbose option should be dropped? The buildlog gets shrinked to 1.4 MB, but the tests are only displayed as dots. Yes the build log is huge, and has been for a while. If you try and view it in a browser it never loads! I would be happy to turn the --verbose option off until it is needed one day. Regards, Tobias I will try and take a look this week. But if I fail, either of you are welcome to lose patience, merge it to master, and upload it for me. :-) Regards Ross
Bug#1068202: bazel-bootstrap: FTBFS: /usr/include/absl/base/policy_checks.h:79:2: error: #error "C++ versions less than C++14 are not supported."
FYI: I've created MR for it. https://salsa.debian.org/bazel-team/bazel-bootstrap/-/merge_requests/3
Processed: severity of 1070691 is serious
Processing commands for cont...@bugs.debian.org: > # msgpack-c was uploaded to unstable > severity 1070691 serious Bug #1070691 [src:tmate-ssh-server] tmate-ssh-server: FTBFS with msgpack-c 6.x Severity set to 'serious' from 'important' > thanks Stopping processing here. Please contact me if you need assistance. -- 1070691: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1070691 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: severity of 1070694 is serious
Processing commands for cont...@bugs.debian.org: > # msgpack-c was uploaded to unstable > severity 1070694 serious Bug #1070694 [src:webdis] webdis: FTBFS with msgpack-c 6.x Severity set to 'serious' from 'important' > thanks Stopping processing here. Please contact me if you need assistance. -- 1070694: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1070694 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: severity of 1070693 is serious
Processing commands for cont...@bugs.debian.org: > # msgpack-c was uploaded to unstable > severity 1070693 serious Bug #1070693 [src:tmate] tmate: FTBFS with msgpack-c 6.x Severity set to 'serious' from 'important' > thanks Stopping processing here. Please contact me if you need assistance. -- 1070693: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1070693 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: severity of 1070692 is serious
Processing commands for cont...@bugs.debian.org: > # msgpack-c was uploaded to unstable > severity 1070692 serious Bug #1070692 [src:libdata-messagepack-stream-perl] libdata-messagepack-stream-perl: FTBFS with msgpack-c 6.x Severity set to 'serious' from 'important' > thanks Stopping processing here. Please contact me if you need assistance. -- 1070692: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1070692 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1072369: marked as done (dropbear: flaky autopkgtest)
Your message dated Sun, 02 Jun 2024 22:49:30 +
with message-id
and subject line Bug#1072369: fixed in dropbear 2024.85-2
has caused the Debian Bug report #1072369,
regarding dropbear: flaky autopkgtest
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.)
--
1072369: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1072369
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: dropbear
Version: 2024.85-1
Severity: serious
Justification: flaky debci is RC as per RT
X-Debbugs-CC: elb...@debian.org
Hi,
Dropbear's debci sometimes fails and works on reruns, which is RC
according to the release team. E.g.:
44s _ test_read_pty[41234]
_
44s
44s request = >
44s dropbear =
44s size = 41234
44s
44s @pytest.mark.parametrize("size", [0, 1, 2, 100, 20001, 41234])
44s def test_read_pty(request, dropbear, size):
44s# testcase for
44s# https://bugs.openwrt.org/index.php?do=details&task_id=1814
44s# https://github.com/mkj/dropbear/pull/85
44s# From Yousong Zhou
44s# Fixed Oct 2021
44s#
44s#$ ssh -t my.router cat /tmp/bigfile | wc
44s#Connection to my.router closed.
44s# 0 1 14335 <- should be 20001
44s
44s# Write the file. No newlines etc which could confuse ptys
44sdat = random_alnum(size)
44sr = dbclient(request, "tmpf=`mktemp`; echo $tmpf; cat > $tmpf",
input=dat, capture_output=True, text=True)
44stmpf = r.stdout.rstrip()
44sr.check_returncode()
44s# Read with a pty, this is what is being tested.
44s# Timing/buffering is subtle, we seem to need to cat a file
from disk to hit it.
44sm, s = pty.openpty()
44sr = dbclient(request, "-t", f"cat {tmpf}; rm {tmpf}", stdin=s,
capture_output=True)
44sr.check_returncode()
44s > assert r.stdout.decode() == dat
44s EAssertionError: assert '5UJ3MW22xOOI...FaalTbhYJnMCI' ==
'5UJ3MW22xOOI...Y3JVX5tREk1dZ'
44s E
44s E Skipping 35313 identical leading characters in diff, use -v to show
44s E -
alTbhYJnMCIn7LtG6YFfF3Gk3pFejnyM2rEbIILTIFdk1JWuplYKktUPBdJT7np0mbpsUIv4VRwGAVP2JWGnLAm4S4AAQIPMawGHMyoxqV9zFFE8MinMNvpw1aQf9QPfnO8TeBNMyIVtBwW3T3BnV5K9g46lSmnyHzb74TxhKlyUPfxptjwFB1d8v4HyDdl0RyLYulodzxNeIOB1Lm5ALyInEVcVc6cy4O9gmzgUCRHT5i3dJzMCvJJ0yBYRhfSwY4vms9TLH5uloGp5wK8QYMeiM4YGMR8LlGE0p2ol7aiVd0LxNqWb3dzlC17iPYOjxhpUaIuUOkhxu5JXcnEP8QkLOwEgWltymjnnvG3z4ITHf24leozVwGMOO8eR74E9JZdZE6Hs7EWKMuzFmlCHK08L5WtZRPYksOq5HuvUxttVOhtCYJDgPpnJ48Z27q0no73Qeg3gS7Y74nf3ZEGToWh71Wn9whsbp3QoGMENc4UUth8KPoiu2QuEzbl...
44s E
44s E ...Full output truncated (2 lines hidden), use '-vv' to show
https://ci.debian.net/packages/d/dropbear/testing/s390x/47157781/
--
Kind regards,
Luca Boccassi
signature.asc
Description: This is a digitally signed message part
--- End Message ---
--- Begin Message ---
Source: dropbear
Source-Version: 2024.85-2
Done: Guilhem Moulin
We believe that the bug you reported is fixed in the latest version of
dropbear, 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 1072...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Guilhem Moulin (supplier of updated dropbear 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: Mon, 03 Jun 2024 00:24:16 +0200
Source: dropbear
Architecture: source
Version: 2024.85-2
Distribution: unstable
Urgency: medium
Maintainer: Guilhem Moulin
Changed-By: Guilhem Moulin
Closes: 1072369
Changes:
dropbear (2024.85-2) unstable; urgency=medium
.
* DEP-8: Mark upstream-tests as flaky. (Closes: #1072369)
Checksums-Sha1:
2c966852d94610674d070543699c8d0022594e4c 2524 dropbear_2024.85-2.dsc
1dfe5eb323cf31f03f68ddd4aed327b41b8ea777 34800 dropbear_2024.85-2.debian.tar.xz
9d4f75202928e0f5c56f1fe7873651f7060a89a8 6845
dropbear_2024.85-2_amd64.buildinfo
Checksums-Sha256:
3b9b6e4166084cb5da2ef305863535197411a4d271283af4b9d7f6447926996b 2524
dropbear_2024.85-2.dsc
5b40326d
Bug#1072280: marked as done (FTBFS against libmatio 1.5.27)
Your message dated Sun, 02 Jun 2024 19:35:29 +
with message-id
and subject line Bug#1072280: fixed in labplot 2.10.1-3
has caused the Debian Bug report #1072280,
regarding FTBFS against libmatio 1.5.27
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.)
--
1072280: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1072280
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: labplot
Version: 2.10.1-2
Severity: important
Tags: ftbfs patch upstream
Control: block 1071614 by -1
Dear Maintainer,
labplot fails to build against libmatio 1.5.27 (currently in experimental),
because the return type of the Mat_GetDir() function now has some constness.
I attach both a build log and a patch that fixes the issue.
Best wishes,
--
⢀⣴⠾⠻⢶⣦⠀ Sébastien Villemot
⣾⠁⢠⠒⠀⣿⡁ Debian Developer
⢿⡄⠘⠷⠚⠋⠀ https://sebastien.villemot.name
⠈⠳⣄ https://www.debian.org
labplot_2.10.1-2_amd64.build.gz
Description: application/gzip
Description: Fix FTBFS against libmatio 1.5.27
The return type of Mat_GetDir() now has some constness.
Author: Sébastien Villemot
Bug-Debian: https://bugs.debian.org/
Forwarded: no
Last-Update: 2024-05-31
---
This patch header follows DEP-3: http://dep.debian.net/deps/dep3/
--- a/src/backend/datasources/filters/MatioFilter.cpp
+++ b/src/backend/datasources/filters/MatioFilter.cpp
@@ -342,7 +342,7 @@ QString MatioFilter::fileInfoString(cons
info += QLatin1String("");
size_t n;
- char** dir = Mat_GetDir(matfp, &n);
+ char* const* dir = Mat_GetDir(matfp, &n);
info += i18n("Number of variables: ") + QString::number(n);
info += QStringLiteral("");
if (dir && n < 10) { // only show variable info when there are not too
many
@@ -550,7 +550,7 @@ void MatioFilterPrivate::parse(const QSt
}
// get names of all vars
- char** dir = Mat_GetDir(matfp, &varCount);
+ char* const* dir = Mat_GetDir(matfp, &varCount);
DEBUG(Q_FUNC_INFO << ", found " << varCount << " vars")
varsInfo.clear();
--- End Message ---
--- Begin Message ---
Source: labplot
Source-Version: 2.10.1-3
Done: Pino Toscano
We believe that the bug you reported is fixed in the latest version of
labplot, 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 1072...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Pino Toscano (supplier of updated labplot 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, 02 Jun 2024 21:04:24 +0200
Source: labplot
Architecture: source
Version: 2.10.1-3
Distribution: unstable
Urgency: medium
Maintainer: Debian KDE Extras Team
Changed-By: Pino Toscano
Closes: 1072280
Changes:
labplot (2.10.1-3) unstable; urgency=medium
.
* Backport upstream commit d6142308ffa492d9f7cea00fad3b4cd1babfd00c to fix
the
build with newer versions of matio; patch
upstream_matio-Fix-compilation-for-latest-version-1.5.27.patch.
(Closes: #1072280)
* Bump Standards-Version to 4.7.0, no changes required.
* Switch the transitional pkg-config build dependency to pkgconf.
* Update lintian overrides.
Checksums-Sha1:
c53778a9d0590081c307eec848ca8d4c7dc42094 3069 labplot_2.10.1-3.dsc
21b580ded1ac1bf071a0efa59fd8551380c4de87 16772 labplot_2.10.1-3.debian.tar.xz
3dd39db09800bddbf34be87f86b6fa606ad6e680 19717
labplot_2.10.1-3_source.buildinfo
Checksums-Sha256:
34762da801444c124a2d4e08dc3c0cd53d093570e54974a7c7dd6b215e97 3069
labplot_2.10.1-3.dsc
4300ed64554c70889f0b8968e7bd4cb25acc1d071b5aaf84e2ff6513fd286a26 16772
labplot_2.10.1-3.debian.tar.xz
373a22339eedeb09ddc08093512ea539e5a282c8be9280b7ad6edf073d37ddc9 19717
labplot_2.10.1-3_source.buildinfo
Files:
4e1f21f9d69131bb551d8647c51a87ae 3069 math optional labplot_2.10.1-3.dsc
69858368e606439126297230a8df7da2 16772 math optional
labplot_2.10.1-3.debian.tar.xz
028351d7874282d35ddfd5dcfe74f6af 19717 math optional
labplot_2.10.1-3_source.buildinfo
-BEGIN PGP SIGNATURE-
iQIzBAEBCgAdFiEEXyqfuC+mweEHcAcHLRkciEOxP00FAmZcwm0ACgkQLRkciEOx
P01tqQ/7BWcf4WXzL/NpxHaYxUNlY1iAyW/o12Af/ro1QdaJSe6TgNXSuWVwWVv0
ya8fjUakXEjMiTwiNsXwtyfSXxQz4DmdpVSKrNpOZ6Gc5Iy
Bug#1058357: marked as done (python-semantic-release: FTBFS: dh_auto_test: error: pybuild --test -i python{version} -p "3.12 3.11" returned exit code 13)
Your message dated Sun, 2 Jun 2024 20:23:35 +0100
with message-id
and subject line Fixed by python-invoke 2.0.0-1.2
has caused the Debian Bug report #1058357,
regarding python-semantic-release: FTBFS: dh_auto_test: error: pybuild --test
-i python{version} -p "3.12 3.11" 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.)
--
1058357: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1058357
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-semantic-release
Version: 7.32.2-1
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20231212 ftbfs-trixie
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> for dir in /<>/.pybuild/cpython3_3.12_semantic-release/build
> /<>/.pybuild/cpython3_3.11_semantic-release/build; do \
> cp -r tests $dir ; \
> done
> dh_auto_test
> I: pybuild base:310: cd
> /<>/.pybuild/cpython3_3.12_semantic-release/build; python3.12 -m
> pytest -x -k "not test_vcs_helpers.py and not
> test_current_release_version_should_return_correct_version and not test_cli
> and not test_config and not
> test_current_version_should_return_correct_version"
> = test session starts
> ==
> platform linux -- Python 3.12.1, pytest-7.4.3, pluggy-1.3.0
> rootdir: /<>
> plugins: mock-3.12.0
> collected 13 items / 1 error
>
> ERRORS
>
> _ ERROR collecting
> .pybuild/cpython3_3.12_semantic-release/build/tests/test_cli.py _
> ImportError while importing test module
> '/<>/.pybuild/cpython3_3.12_semantic-release/build/tests/test_cli.py'.
> Hint: make sure your test modules/packages have valid Python names.
> Traceback:
> /usr/lib/python3.12/importlib/__init__.py:90: in import_module
> return _bootstrap._gcd_import(name[level:], package, level)
> tests/test_cli.py:3: in
> from semantic_release.cli import changelog, main, print_version, publish,
> version
> semantic_release/cli.py:15: in
> from .dist import build_dists, remove_dists, should_build,
> should_remove_dist
> semantic_release/dist.py:6: in
> from invoke import run
> /usr/lib/python3/dist-packages/invoke/__init__.py:23: in
> from .loader import FilesystemLoader # noqa
> /usr/lib/python3/dist-packages/invoke/loader.py:3: in
> import imp
> E ModuleNotFoundError: No module named 'imp'
> === short test summary info
>
> ERROR tests/test_cli.py
> !! stopping after 1 failures
> !!!
> === 1 error in 0.44s
> ===
> E: pybuild pybuild:395: test: plugin distutils failed with: exit code=1: cd
> /<>/.pybuild/cpython3_3.12_semantic-release/build; python3.12 -m
> pytest -x -k "not test_vcs_helpers.py and not
> test_current_release_version_should_return_correct_version and not test_cli
> and not test_config and not
> test_current_version_should_return_correct_version"
> I: pybuild base:310: cd
> /<>/.pybuild/cpython3_3.11_semantic-release/build; python3.11 -m
> pytest -x -k "not test_vcs_helpers.py and not
> test_current_release_version_should_return_correct_version and not test_cli
> and not test_config and not
> test_current_version_should_return_correct_version"
> = test session starts
> ==
> platform linux -- Python 3.11.7, pytest-7.4.3, pluggy-1.3.0
> rootdir: /<>
> plugins: mock-3.12.0
> collected 929 items / 112 deselected / 817 selected
>
> tests/test_changelog.py .[
> 1%]
> tests/test_dist.py . [
> 4%]
> tests/test_hvcs.py . [
> 10%]
> tests/test_pre_commit.py .. [
> 10%]
> tests/test_repository.py [
> 13%]
> tests/test_settings.py ... [
> 14%]
> tests/test_setup_py_hook.py .. [
> 14%]
> tests/ci_checks/test_bitbucket.py [
> 14%]
> tests/ci_checks/test_checker.py .. [
> 15%]
> tests/ci_checks/test_circle.py [
> 16%]
Bug#1056503: marked as done (python-semantic-release's autopkg tests fail with Python 3.12)
Your message dated Sun, 2 Jun 2024 20:23:35 +0100 with message-id and subject line Fixed by python-invoke 2.0.0-1.2 has caused the Debian Bug report #1056503, regarding python-semantic-release's autopkg tests fail with Python 3.12 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.) -- 1056503: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1056503 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:python-semantic-release Version: 7.32.2-1 Severity: important Tags: sid trixie User: debian-pyt...@lists.debian.org Usertags: python3.12 python-semantic-release's autopkg tests fail with Python 3.12: [...] 212s autopkgtest [19:08:58]: test run-tests: [--- 212s = test session starts == 212s platform linux -- Python 3.12.0+, pytest-7.4.3, pluggy-1.3.0 -- /usr/bin/python3.12 212s cachedir: .pytest_cache 212s rootdir: /tmp/autopkgtest.fltlFo/autopkgtest_tmp 212s plugins: mock-3.11.1 212s collecting ... collected 13 items / 1 error 212s 212s ERRORS 212s __ ERROR collecting tests/test_cli.py __ 212s ImportError while importing test module '/tmp/autopkgtest.fltlFo/autopkgtest_tmp/tests/test_cli.py'. 212s Hint: make sure your test modules/packages have valid Python names. 212s Traceback: 212s /usr/lib/python3.12/importlib/__init__.py:90: in import_module 212s return _bootstrap._gcd_import(name[level:], package, level) 212s tests/test_cli.py:3: in 212s from semantic_release.cli import changelog, main, print_version, publish, version 212s /usr/lib/python3/dist-packages/semantic_release/cli.py:15: in 212s from .dist import build_dists, remove_dists, should_build, should_remove_dist 212s /usr/lib/python3/dist-packages/semantic_release/dist.py:6: in 212s from invoke import run 212s /usr/lib/python3/dist-packages/invoke/__init__.py:23: in 212s from .loader import FilesystemLoader # noqa 212s /usr/lib/python3/dist-packages/invoke/loader.py:3: in 212s import imp 212s E ModuleNotFoundError: No module named 'imp' 212s === short test summary info 212s ERROR tests/test_cli.py 212s !! stopping after 1 failures !!! 212s === 1 error in 0.57s === --- End Message --- --- Begin Message --- These python-semantic-release test failures were actually bugs in python-invoke rather than directly in python-semantic-release, and were fixed there a while ago: python-invoke (2.0.0-1.2) unstable; urgency=medium * Team upload. * Avoid FTBFS with Python3.12 by using python3-zombie-imp -- Alexandre Detiste Tue, 02 Jan 2024 20:32:49 +0100 I've tested that python-semantic-release passes again now. -- Colin Watson (he/him) [cjwat...@debian.org]--- End Message ---
Bug#1070733: linux-image-5.10.0-29-amd64 fails to boot with Error 16: Inconsistent filesystem structure
Control: severity -1 important On Thu, May 16, 2024 at 12:10:41PM +, Dan Poltawski wrote: > Thanks for your response - I hadn't quite noticed that this was legacy grub > (and > had kinda made the assumption the Debian upgrades had forced the upgrade). > > I have migrated to GRUB 2 and can confirm this resolves the issue. OK, good. I tried reproducing this in a VM and couldn't; I suspect that it's something relatively subtle about the filesystem structure that doesn't happen to everyone. As such I'm downgrading this to just below release-critical, since on its own I don't think it quite justifies removing grub-legacy from testing. -- Colin Watson (he/him) [cjwat...@debian.org]
Processed: Re: Bug#1070733: linux-image-5.10.0-29-amd64 fails to boot with Error 16: Inconsistent filesystem structure
Processing control commands: > severity -1 important Bug #1070733 [grub-legacy] linux-image-5.10.0-29-amd64 fails to boot with Error 16: Inconsistent filesystem structure Severity set to 'important' from 'grave' -- 1070733: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1070733 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1066708: marked as done (matchbox-keyboard: FTBFS: main.c:167:19: error: implicit declaration of function ‘mb_kbd_ui_handle_configure’ [-Werror=implicit-function-declaration])
Your message dated Sun, 02 Jun 2024 18:21:10 + with message-id and subject line Bug#1066708: fixed in matchbox-keyboard 0.2+git20160713-1.1 has caused the Debian Bug report #1066708, regarding matchbox-keyboard: FTBFS: main.c:167:19: error: implicit declaration of function ‘mb_kbd_ui_handle_configure’ [-Werror=implicit-function-declaration] 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.) -- 1066708: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1066708 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: matchbox-keyboard Version: 0.2+git20160713-1 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-20240313 ftbfs-trixie ftbfs-impfuncdef Hi, During a rebuild of all packages in sid, your package failed to build on amd64. This is most likely caused by a change in dpkg 1.22.6, that enabled -Werror=implicit-function-declaration. For more information, see https://wiki.debian.org/qa.debian.org/FTBFS#A2024-03-13_-Werror.3Dimplicit-function-declaration Relevant part (hopefully): > /bin/bash ../libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I. -I.. > -DDATADIR=\"/usr/share\" -DPKGDATADIR=\"/usr/share/matchbox-keyboard\" > -DPREFIX=\"/usr\" -g -Wall -fno-strict-aliasing -I/usr/include/freetype2 > -I/usr/include/libpng16-I/usr/include/libpng16 -I.. -I.. -g -O2 > -Werror=implicit-function-declaration -ffile-prefix-map=/<>=. > -fstack-protector-strong -fstack-clash-protection -Wformat > -Werror=format-security -fcf-protection -c -o > libmatchbox_keyboard_la-matchbox-keyboard-ui.lo `test -f > 'matchbox-keyboard-ui.c' || echo './'`matchbox-keyboard-ui.c > main.c: In function ‘mb_kbd_event_loop’: > main.c:167:19: error: implicit declaration of function > ‘mb_kbd_ui_handle_configure’ [-Werror=implicit-function-declaration] > 167 | mb_kbd_ui_handle_configure(ui, > | ^~ > /bin/bash ../libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I. -I.. > -DDATADIR=\"/usr/share\" -DPKGDATADIR=\"/usr/share/matchbox-keyboard\" > -DPREFIX=\"/usr\" -g -Wall -fno-strict-aliasing -I/usr/include/freetype2 > -I/usr/include/libpng16-I/usr/include/libpng16 -I.. -I.. -g -O2 > -Werror=implicit-function-declaration -ffile-prefix-map=/<>=. > -fstack-protector-strong -fstack-clash-protection -Wformat > -Werror=format-security -fcf-protection -c -o > libmatchbox_keyboard_la-config-parser.lo `test -f 'config-parser.c' || echo > './'`config-parser.c > main.c:172:17: error: implicit declaration of function > ‘mb_kbd_ui_update_display_size’ [-Werror=implicit-function-declaration] > 172 | mb_kbd_ui_update_display_size(ui); > | ^ > main.c:85:20: warning: variable ‘press_y’ set but not used > [-Wunused-but-set-variable] >85 | int press_x = 0, press_y = 0; > |^~~ > main.c:85:7: warning: variable ‘press_x’ set but not used > [-Wunused-but-set-variable] >85 | int press_x = 0, press_y = 0; > | ^~~ > main.c: In function ‘main’: > main.c:280:3: error: implicit declaration of function ‘mb_kbd_destroy’; did > you mean ‘mb_kbd_ui_destroy’? [-Werror=implicit-function-declaration] > 280 | mb_kbd_destroy (kb); > | ^~ > | mb_kbd_ui_destroy > libmatchbox-keyboard.c: In function ‘mb_keyboard_destroy’: > libmatchbox-keyboard.c:64:3: error: implicit declaration of function > ‘mb_kbd_destroy’; did you mean ‘mb_kbd_ui_destroy’? > [-Werror=implicit-function-declaration] >64 | mb_kbd_destroy (kb); > | ^~ > | mb_kbd_ui_destroy > libtool: compile: gcc -DHAVE_CONFIG_H -I. -I.. -DDATADIR=\"/usr/share\" > -DPKGDATADIR=\"/usr/share/matchbox-keyboard\" -DPREFIX=\"/usr\" -g -Wall > -fno-strict-aliasing -I/usr/include/freetype2 -I/usr/include/libpng16 > -I/usr/include/libpng16 -I.. -I.. -g -O2 > -Werror=implicit-function-declaration -ffile-prefix-map=/<>=. > -fstack-protector-strong -fstack-clash-protection -Wformat > -Werror=format-security -fcf-protection -c matchbox-keyboard-key.c -fPIC > -DPIC -o .libs/libmatchbox_keyboard_la-matchbox-keyboard-key.o > libtool: compile: gcc -DHAVE_CONFIG_H -I. -I.. -DDATADIR=\"/usr/share\" > -DPKGDATADIR=\"/usr/share/matchbox-keyboard\" -DPREFIX=\"/usr\" -g -Wall > -fno-strict-aliasing -I/usr/include/freetype2 -I/usr/include/libpng16 > -I/usr/include/libpng16 -I.. -I.. -g -O2 > -Werror=implicit-function-declaration -ffile-prefix-map=/<>=. >
Bug#1066708: matchbox-keyboard: diff for NMU version 0.2+git20160713-1.1
Control: tags 1066708 + patch Dear maintainer, I've prepared an NMU for matchbox-keyboard (versioned as 0.2+git20160713-1.1). The diff is attached to this message. Regards. -- Sebastian Ramacher diff -Nru matchbox-keyboard-0.2+git20160713/debian/changelog matchbox-keyboard-0.2+git20160713/debian/changelog --- matchbox-keyboard-0.2+git20160713/debian/changelog 2020-06-15 18:19:48.0 +0200 +++ matchbox-keyboard-0.2+git20160713/debian/changelog 2024-06-02 19:46:51.0 +0200 @@ -1,3 +1,10 @@ +matchbox-keyboard (0.2+git20160713-1.1) unstable; urgency=medium + + * Non-maintainer upload. + * debian/patches: Fix implicit function declarations (Closes: #1066708) + + -- Sebastian Ramacher Sun, 02 Jun 2024 19:46:51 +0200 + matchbox-keyboard (0.2+git20160713-1) unstable; urgency=medium * New upstream release from Yocto Project git. diff -Nru matchbox-keyboard-0.2+git20160713/debian/patches/implicit-functions.patch matchbox-keyboard-0.2+git20160713/debian/patches/implicit-functions.patch --- matchbox-keyboard-0.2+git20160713/debian/patches/implicit-functions.patch 1970-01-01 01:00:00.0 +0100 +++ matchbox-keyboard-0.2+git20160713/debian/patches/implicit-functions.patch 2024-06-02 19:38:14.0 +0200 @@ -0,0 +1,47 @@ +--- a/src/matchbox-keyboard-ui-xft-backend.h b/src/matchbox-keyboard-ui-xft-backend.h +@@ -27,6 +27,9 @@ + MBKeyboardUIBackend* + mb_kbd_ui_xft_init(MBKeyboardUI *ui); + ++void ++mb_kbd_ui_xft_destroy (MBKeyboardUI *ui); ++ + #define MB_KBD_UI_BACKEND_INIT_FUNC(ui) mb_kbd_ui_xft_init((ui)) + #define MB_KBD_UI_BACKEND_DESTROY_FUNC(ui) mb_kbd_ui_xft_destroy((ui)) + +--- a/src/matchbox-keyboard.h b/src/matchbox-keyboard.h +@@ -332,6 +332,12 @@ + void + mb_kbd_ui_handle_widget_xevent (MBKeyboardUI *ui, XEvent *xev); + ++void ++mb_kbd_ui_handle_configure(MBKeyboardUI *ui, int width, int height); ++ ++void ++mb_kbd_ui_update_display_size(MBKeyboardUI *ui); ++ + #ifdef WANT_CAIRO + #define mb_kbd_image_width(x) cairo_image_surface_get_width (x) + #define mb_kbd_image_height(x) cairo_image_surface_get_height (x) +@@ -379,6 +385,9 @@ + int x, int y, int w, int h); + #endif + ++void ++mb_kbd_destroy (MBKeyboard *kb); ++ + int + mb_kbd_row_spacing(MBKeyboard *kb); + +@@ -647,6 +656,9 @@ + void + mb_kbd_key_dump_key(MBKeyboardKey *key); + ++MBKeyboardKeyActionType ++mb_kbd_key_get_action_type(MBKeyboardKey *key, MBKeyboardKeyStateType state); ++ + #define mb_kdb_key_foreach_state(k,s) \ +for((s)=0; (s) < N_MBKeyboardKeyStateTypes; (s)++) \ + if (mb_kdb_key_has_state((k), (s))) diff -Nru matchbox-keyboard-0.2+git20160713/debian/patches/series matchbox-keyboard-0.2+git20160713/debian/patches/series --- matchbox-keyboard-0.2+git20160713/debian/patches/series 2020-06-15 18:19:48.0 +0200 +++ matchbox-keyboard-0.2+git20160713/debian/patches/series 2024-06-02 19:30:47.0 +0200 @@ -1,2 +1,3 @@ linking-fix xmonad-support +implicit-functions.patch
Processed: matchbox-keyboard: diff for NMU version 0.2+git20160713-1.1
Processing control commands: > tags 1066708 + patch Bug #1066708 [src:matchbox-keyboard] matchbox-keyboard: FTBFS: main.c:167:19: error: implicit declaration of function ‘mb_kbd_ui_handle_configure’ [-Werror=implicit-function-declaration] Added tag(s) patch. -- 1066708: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1066708 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: tagging 1072280
Processing commands for cont...@bugs.debian.org: > tags 1072280 + pending Bug #1072280 [src:labplot] FTBFS against libmatio 1.5.27 Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 1072280: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1072280 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1072352: marked as done (lua-vips: replace luajit2 with luajit)
Your message dated Sun, 02 Jun 2024 17:21:10 + with message-id and subject line Bug#1072352: fixed in lua-vips 1.1.11-2 has caused the Debian Bug report #1072352, regarding lua-vips: replace luajit2 with luajit 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.) -- 1072352: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1072352 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: lua-vips Version: 1.1.11-1 Severity: serious Control: block 1069780 by -1 luajit2 was requested to be removed, see #1069780. Please switch your (Build-Depends) over to luajit, which has become the openresty luajit(2) source. --- End Message --- --- Begin Message --- Source: lua-vips Source-Version: 1.1.11-2 Done: Alexandre Detiste We believe that the bug you reported is fixed in the latest version of lua-vips, 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 1072...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Alexandre Detiste (supplier of updated lua-vips 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, 02 Jun 2024 18:39:14 +0200 Source: lua-vips Architecture: source Version: 1.1.11-2 Distribution: unstable Urgency: medium Maintainer: The Debian Lua Team Changed-By: Alexandre Detiste Closes: 1072352 Changes: lua-vips (1.1.11-2) unstable; urgency=medium . * Team upload. * Replace luajit2 by luajit (Closes: #1072352) Checksums-Sha1: 9c435f0b537d88ac215186ca2e5ce4a6fa0d8668 2051 lua-vips_1.1.11-2.dsc de39cb6ce2f674d76e3dd138ba1ac148f133b22a 2328 lua-vips_1.1.11-2.debian.tar.xz 56d6cdfba3d69ed08194b6edbded501dcf3314ab 16426 lua-vips_1.1.11-2_source.buildinfo Checksums-Sha256: 44bb23f50b87f2455028e779b355a7b0cc9f44885baeba79e9fc5a10a18c65eb 2051 lua-vips_1.1.11-2.dsc e0966a201423d51a9ea20bf4a0afd796844e5d3be4eb2317e9374aefeb62abcb 2328 lua-vips_1.1.11-2.debian.tar.xz 107b8e63bca9f3e8e1eda24ec36b80d47f7f8e5264848c5043d930845c4379a5 16426 lua-vips_1.1.11-2_source.buildinfo Files: 7bd0402442bf3de7e8a7a4fa381804b0 2051 misc optional lua-vips_1.1.11-2.dsc 2e32fff7a09f1bb39246b0faf4547c95 2328 misc optional lua-vips_1.1.11-2.debian.tar.xz 3ef3fa0b9517d5afaf28beb1623d74c4 16426 misc optional lua-vips_1.1.11-2_source.buildinfo -BEGIN PGP SIGNATURE- iQJFBAEBCgAvFiEEj23hBDd/OxHnQXSHMfMURUShdBoFAmZcoPgRHHRjaGV0QGRl Ymlhbi5vcmcACgkQMfMURUShdBqaQg//SH2ZAo9q+oIMYbB8P8BYwxNJzzMl9bs8 r7Hx1gaX34ZoWCwOAFnwbOMeqRz2hUScekSsVLr8aRCz95BAxa1sdMC6VFC2N1Sq FnGRLop1zlMKVBssRHpTAsWviGNPvQjs1ITYHbyBDL6Hv9j7U8ZgtHGtXNQWgcZL CcphA8Radf85MV2YDtVKQuYTsR7H8/b0kRrr3HgiczDBWe2eH9UdsICkHXWfLJqM 6IRYIaQuhPqckYsOOG1mbz69LfpGHTKdC/7GTf46vOwinktf8xmnyRFAYWrjyEkd Dx/tZ+Pguc4Eo1OYpvf+JX913YJ6A8rIF514xRQvVKuTmo8VvfOD/ePLq+Ok22a7 D0u73h5hnzbT0djNV0xhyX7jz82jiTUq1pCdoodg11+KErrHs4PlK4ral0p40LTV Z50nF6P8SblZE5HVK30TfWqgY96tgYiQ7wfXfVcv9w+UcbW8GkPtVJaDnE7N/CkS 56EYgvI4mEWvnhszL6Sb5HrgTvsJTnu7Vb/I1wa2kvGCFu0J3e4t21zpKfOnmWet 4wOCf/vNtinFuwabCtQb0Jw4biL5Bp2keaN5j3t1dyd05YvYfg54yoPbkxTd83PU iUS0kqmb+g9xQv/pOmrlADeFKTTL14qLgm43Q9V10Ld5so1gpeHQt2YIVEzthVRb wzvK6SAj8IQ= =br0M -END PGP SIGNATURE- pgpfUmvBQPpLh.pgp Description: PGP signature --- End Message ---
Bug#1072480: condor: hard-coded dependencies on pre-t64 libraries
Source: condor Version: 23.4.0+dfsg-1 Severity: serious X-Debbugs-Cc: sramac...@debian.org condor has a bunch of hard-coded dependencies. At least one of them (libssl3) got renamed as part of the t64 transition. Please take a look at the changes in Ubuntu on how to compute these dependencies. Cheers -- Sebastian Ramacher
debian-bugs-rc@lists.debian.org
Source: litecoin Version: 0.21.3-1 Severity: serious Tags: ftbfs Justification: fails to build from source (but built successfully in the past) X-Debbugs-Cc: sramac...@debian.org https://buildd.debian.org/status/fetch.php?pkg=litecoin&arch=ppc64el&ver=0.21.3-1&stamp=1714303642&raw=0 libsecp256k1 0.1: ./test-suite.log # TOTAL: 2 # PASS: 1 # SKIP: 0 # XFAIL: 0 # FAIL: 1 # XPASS: 0 # ERROR: 0 .. contents:: :depth: 2 FAIL: exhaustive_tests == src/tests_exhaustive.c:57: test condition failed: secp256k1_fe_equal_var(&u1, &u2) FAIL exhaustive_tests (exit status: 134) Testsuite summary for libsecp256k1 0.1 # TOTAL: 2 # PASS: 1 # SKIP: 0 # XFAIL: 0 # FAIL: 1 # XPASS: 0 # ERROR: 0 See ./test-suite.log make[8]: *** [Makefile:1487: test-suite.log] Error 1 Cheers -- Sebastian Ramacher
Processed: Re: bazel-bootstrap: FTBFS: /usr/include/absl/base/policy_checks.h:79:2: error: #error "C++ versions less than C++14 are not supported."
Processing control commands: > tags -1 patch Bug #1068202 [src:bazel-bootstrap] bazel-bootstrap: FTBFS: /usr/include/absl/base/policy_checks.h:79:2: error: #error "C++ versions less than C++14 are not supported." Added tag(s) patch. -- 1068202: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1068202 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1068202: bazel-bootstrap: FTBFS: /usr/include/absl/base/policy_checks.h:79:2: error: #error "C++ versions less than C++14 are not supported."
Control: tags -1 patch
Hi,
> bazel-out/k8-dbg/bin/src/main/protobuf/command_server.grpc.pb.cc:6:
> /usr/include/absl/base/policy_checks.h:79:2: error: #error "C++
> versions less than C++14 are not supported." 79 | #error "C++
> versions less than C++14 are not supported." | ^
>
I've attached a patch [1] to fix FTBFS.
[1] 0001-Fix-FTBFS-with-std-c-0x-C-11.patch
I'm not sure that it should be fixed with .bzl source code under tools
directory too. (I guess that generated bazel command embeds it)
so these files was not touched.
(leave it to bazel-bootstrap maintainer judge)
grep -ir "c++0x"
tools/cpp/cc_toolchain_config.bzl:flag_groups =
[flag_group(flags = ["-std=c++0x"])],
tools/cpp/cc_toolchain_config.bzl:flag_groups =
[flag_group(flags = ["-std=c++0x"])],
tools/cpp/cc_toolchain_config.bzl:flag_groups =
[flag_group(flags = ["-std=c++0x"])],
tools/cpp/cc_toolchain_config.bzl:flag_groups =
[flag_group(flags = ["-std=c++0x"])], tools/cpp/unix_cc_configure.bzl:
"-std=c++0x", tools/cpp/bsd_cc_toolchain_config.bzl:
flag_groups = [flag_group(flags = ["-std=c++0x"])],
Regards,
>From e7f756e9e328516517e7b14ad1070c41c5688d5a Mon Sep 17 00:00:00 2001
From: Kentaro Hayashi
Date: Sun, 2 Jun 2024 23:36:37 +0900
Subject: [PATCH] Fix FTBFS with std=c++0x (C++11)
It will fix the following error:
/usr/include/absl/base/policy_checks.h:79:2: error: #error "C++
versions less than C++14 are not supported."
It seems that -std=c++0x (C++11) is explicitly given in debian/rules,
so newer absl library reject it.
ref. https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1068202
Signed-off-by: Kentaro Hayashi
---
debian/rules | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/debian/rules b/debian/rules
index 629b9caf..5cfeba6a 100755
--- a/debian/rules
+++ b/debian/rules
@@ -22,7 +22,7 @@ export https_proxy=127.0.0.1:9
# BAZEL_CXXOPTS and BAZEL_LINKOPTS take a list of flags seperated by colon
export space = $() $()
-export BAZEL_CXXOPTS = $(subst $(space),:,-std=c++0x ${CPPFLAGS} ${CXXFLAGS})
+export BAZEL_CXXOPTS = $(subst $(space),:,-std=c++14 ${CPPFLAGS} ${CXXFLAGS})
export BAZEL_LINKOPTS = $(subst $(space),:,-lstdc++ -lm ${LDFLAGS})
# Use the local JDK
--
2.45.1
Bug#1071321: tagging 1071321
Following up on this: On Sun, May 26, 2024 at 11:42:56AM +0200, Florian Ernst wrote: > On Sun, May 26, 2024 at 10:54:21AM +0200, Christoph Biedl wrote: > > Étienne Mollier wrote... > > > If that helps, the symbols strlcat and strlcpy have been added > > > to the glibc 2.38, so I believe it should be safe to remove the > > > following symbols without soname bump: > > > > Just came here to say the same (and why does the BTS¹ not show Étienne's > > message?). There might be a small chance this breaks packages due to > > slight implementation differences - but that's what testing and > > autopkgtests are for. > > Thanks for your investigation. I suspected as much, but didn't yet get > around to actually check on this any further, so thanks for the pointer. > > I plan to deal with this on next Sunday, and I'll make sure to check > building all reverse build deps against the updated package as well. Only one of the reverse build depends actually made use of strlcat as provided by libdumbnet: - farpd The last build of 0.2-11.3+b1_amd64 from 2024-03-26 still shows this, but with the upload of 0.2-11.4 on 2024-05-30 it starts to reference the glibc version, so this seems fine now. Two of the reverse build deps provide and use their own copy of strlcat/strlcpy unless those are already available, but don't reference libdumbnet's: - scanssh The last build of 2.0-4.3+b1_amd64 from 2024-03-26 still shows the internal copies, whereas the build of 2.1.3.1-0.1_amd64 from 2024-05-27 shows the glibc versions, so this seems fine. - tcpreplay The last build of 4.4.4-1+b1_amd64 from 2024-03-29 still shows the internal copies, whereas a local rebuild references the glibc versions. This change is unrelated to libdumbnet dropping those symbols, though, and should happen seamlessly some time in the future with the next rebuild. There seems to be no need for such a rebuild as of now. Five of the reverse build deps don't use strlcat/strlcpy at all, so they are all fine: - arpon - daemonlogger - daq - firewalk - libnet-libdnet-perl One of the reverse build deps FTBFS and is overall in a rather sorry state, so I didn't really investigate here: - snort All in all, to me it seems no further action is required here: Bastian's upload of libdumbnet 1.18.0-1.1 solved this bug#1071321 here, and his farpd 0.2-11.4 resolved the followup issue of the then-missing strlcat for that package; all other reverse build deps are not affected or, as is the case with snort, too broken anyway. Cheers, Flo signature.asc Description: PGP signature
Processed: tags
Processing commands for cont...@bugs.debian.org: > # this is not a problem in bookworm > tags 1072469 + trixie sid Bug #1072469 [src:shc] shc: FTBFS: build-depends on ash which does no longer exist Added tag(s) sid and trixie. > thanks Stopping processing here. Please contact me if you need assistance. -- 1072469: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1072469 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1072468: python-tld: FTBFS: No such file or directory: 'update-tld-names'
Package: src:python-tld
Version: 0.13-1
Severity: serious
Tags: ftbfs
Dear maintainer:
During a rebuild of all packages in unstable, your package failed to build:
[...]
debian/rules binary
dh binary --with sphinxdoc --buildsystem=pybuild
dh_update_autotools_config -O--buildsystem=pybuild
dh_autoreconf -O--buildsystem=pybuild
dh_auto_configure -O--buildsystem=pybuild
I: pybuild base:311: python3.12 setup.py config
/usr/lib/python3/dist-packages/setuptools/dist.py:744:
SetuptoolsDeprecationWarning: Invalid dash-separated options
!!
Usage of dash-separated 'license-file' will not be supported in future
versions. Please use the underscore name 'license_file' instead.
This deprecation is overdue, please update your project and remove
deprecated
[... snipped ...]
and os.path.dirname(executable)
and preexec_fn is None
and not close_fds
and not pass_fds
and cwd is None
and (p2cread == -1 or p2cread > 2)
and (c2pwrite == -1 or c2pwrite > 2)
and (errwrite == -1 or errwrite > 2)
and not start_new_session
and process_group == -1
and gid is None
and gids is None
and uid is None
and umask < 0):
self._posix_spawn(args, executable, env, restore_signals,
p2cread, p2cwrite,
c2pread, c2pwrite,
errread, errwrite)
return
orig_executable = executable
# For transferring possible exec failure from child to parent.
# Data format: "exception name:hex errno:description"
# Pickle is not used; it is complex and involves memory allocation.
errpipe_read, errpipe_write = os.pipe()
# errpipe_write must not be in the standard io 0, 1, or 2 fd range.
low_fds_to_close = []
while errpipe_write < 3:
low_fds_to_close.append(errpipe_write)
errpipe_write = os.dup(errpipe_write)
for low_fd in low_fds_to_close:
os.close(low_fd)
try:
try:
# We must avoid complex work that could involve
# malloc or free in the child process to avoid
# potential deadlocks, thus we do all this here.
# and pass it to fork_exec()
if env is not None:
env_list = []
for k, v in env.items():
k = os.fsencode(k)
if b'=' in k:
raise ValueError("illegal environment variable
name")
env_list.append(k + b'=' + os.fsencode(v))
else:
env_list = None # Use execv instead of execve.
executable = os.fsencode(executable)
if os.path.dirname(executable):
executable_list = (executable,)
else:
# This matches the behavior of os._execvpe().
executable_list = tuple(
os.path.join(os.fsencode(dir), executable)
for dir in os.get_exec_path(env))
fds_to_keep = set(pass_fds)
fds_to_keep.add(errpipe_write)
self.pid = _fork_exec(
args, executable_list,
close_fds, tuple(sorted(map(int, fds_to_keep))),
cwd, env_list,
p2cread, p2cwrite, c2pread, c2pwrite,
errread, errwrite,
errpipe_read, errpipe_write,
restore_signals, start_new_session,
process_group, gid, gids, uid, umask,
preexec_fn, _USE_VFORK)
self._child_created = True
finally:
# be sure the FD is closed no matter what
os.close(errpipe_write)
self._close_pipe_fds(p2cread, p2cwrite,
c2pread, c2pwrite,
errread, errwrite)
# Wait for exec to fail or succeed; possibly raising an
# exception (limited in size)
errpipe_data = bytearray()
while True:
part = os.read(errpipe_read, 5)
errpipe_data += part
if not part or len(errpipe_data) > 5:
break
finally:
# be sure the FD is closed no matter what
os.close(errpipe_read)
if errpipe_data:
try:
pid, sts = os.waitpid(self.pi
Bug#1072469: shc: FTBFS: build-depends on ash which does no longer exist
Package: src:shc Version: 4.0.3-1 Severity: serious Tags: ftbfs patch Dear maintainer: During a rebuild of all packages in unstable, your package failed to build: [...] Install main build dependencies (apt-based resolver) Installing build dependencies Reading package lists... Building dependency tree... Reading state information... Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: sbuild-build-depends-main-dummy : Depends: ash but it is not installable E: Unable to correct problems, you have held broken packages. apt-get failed. E: Package installation failed Not removing build depends: cloned chroot in use The above is just how the build ends and not necessarily the most relevant part. If required, the full build log is available here: https://people.debian.org/~sanvila/build-logs/202406/ About the archive rebuild: The build was made on virtual machines of type m6a.large and r6a.large from AWS, using sbuild and a reduced chroot with only build-essential packages. If you could not reproduce the bug please contact me privately, as I am willing to provide ssh access to a virtual machine where the bug is fully reproducible. If this is really a bug in one of the build-depends, please use reassign and affects, so that this is still visible in the BTS web page for this package. Note: This happens because ash (which used to be a dummy package depending on dash) no longer exists. The trivial fix is to build-depend on dash instead, as in the attached patch. Thanks.--- a/debian/control +++ b/debian/control @@ -2,7 +2,7 @@ Source: shc Section: devel Priority: optional Maintainer: Tong Sun -Build-Depends: debhelper-compat (= 13), ash, ksh, rc, tcsh, zsh +Build-Depends: debhelper-compat (= 13), dash, ksh, rc, tcsh, zsh Standards-Version: 4.5.0 Rules-Requires-Root: no Homepage: https://neurobin.org/projects/softwares/unix/shc/
Bug#1072467: pysdl2: FTBFS when built by sbuild (build-depends on libgl1-mesa-glx but it is not installable)
Package: src:pysdl2 Version: 0.9.16+dfsg-1 Severity: serious Tags: ftbfs patch Dear maintainer: During a rebuild of all packages in unstable, your package failed to build: [...] Install main build dependencies (apt-based resolver) Installing build dependencies Reading package lists... Building dependency tree... Reading state information... Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: sbuild-build-depends-main-dummy : Depends: libgl1-mesa-glx but it is not installable E: Unable to correct problems, you have held broken packages. apt-get failed. E: Package installation failed Not removing build depends: cloned chroot in use The above is just how the build ends and not necessarily the most relevant part. If required, the full build log is available here: https://people.debian.org/~sanvila/build-logs/202406/ About the archive rebuild: The build was made on virtual machines of type m6a.large and r6a.large from AWS, using sbuild and a reduced chroot with only build-essential packages. If you could not reproduce the bug please contact me privately, as I am willing to provide ssh access to a virtual machine where the bug is fully reproducible. If this is really a bug in one of the build-depends, please use reassign and affects, so that this is still visible in the BTS web page for this package. Note: This happens because the build depends has "libgl1-mesa-glx | libgl1". When using a virtual package, there must be a real package first. The attached first patch fixes this by reversing the order. However, this is a good time to review such line. Does libgl1-mesa-glx still make sense in trixie/sid? If not, then the second suggested patch would be more appropriate. Thanks.--- a/debian/control +++ b/debian/control @@ -10,7 +10,7 @@ Build-Depends: dia, dh-python, libgl1-mesa-dri, - libgl1-mesa-glx | libgl1, + libgl1 | libgl1-mesa-glx, libsdl2-2.0-0, libsdl2-gfx-1.0-0, libsdl2-image-2.0-0, --- a/debian/control +++ b/debian/control @@ -10,7 +10,7 @@ Build-Depends: dia, dh-python, libgl1-mesa-dri, - libgl1-mesa-glx | libgl1, + libgl1, libsdl2-2.0-0, libsdl2-gfx-1.0-0, libsdl2-image-2.0-0,
Processed: your mail
Processing commands for cont...@bugs.debian.org: > block 1070419 by 1072395 Bug #1070419 [src:gnome-snapshot] src:gnome-snapshot: unsatisfied build dependency in testing: librust-gst-plugin-gtk4-0.11-dev 1070419 was not blocked by any bugs. 1070419 was not blocking any bugs. Added blocking bug(s) of 1070419: 1072395 > block 1070646 by 1072395 Bug #1070646 [src:rust-gst-plugin-gtk4] rust-gst-plugin-gtk4: Please package GStreamer plugin .so as well for use by non-Rust applications 1070646 was blocked by: 1070817 1070646 was not blocking any bugs. Added blocking bug(s) of 1070646: 1072395 > thanks Stopping processing here. Please contact me if you need assistance. -- 1070419: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1070419 1070646: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1070646 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1057949: marked as done (nbconvert: needs update for new version of pandoc: PDF creating failed)
Your message dated Sun, 02 Jun 2024 12:36:51 + with message-id and subject line Bug#1057949: fixed in nbconvert 7.16.4-1 has caused the Debian Bug report #1057949, regarding nbconvert: needs update for new version of pandoc: PDF creating failed to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1057949: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1057949 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: nbconvert Version: 6.5.3-4 Severity: serious X-Debbugs-CC: pan...@packages.debian.org Tags: sid trixie User: debian...@lists.debian.org Usertags: needs-update Control: affects -1 src:pandoc Dear maintainer(s), With a recent upload of pandoc the autopkgtest of nbconvert fails in testing when that autopkgtest is run with the binary packages of pandoc from unstable. It passes when run with only packages from testing. In tabular form: passfail pandoc from testing2.17.1.1+~git20230125+ds-1 nbconvert from testing6.5.3-4 all others from testingfrom testing I copied some of the output at the bottom of this report. Currently this regression is blocking the migration of pandoc to testing [1]. Of course, pandoc shouldn't just break your autopkgtest (or even worse, your package), but it seems to me that the change in pandoc was intended and your package needs to update to the new situation. If this is a real problem in your package (and not only in your autopkgtest), the right binary package(s) from pandoc should really add a versioned Breaks on the unfixed version of (one of your) package(s). Note: the Breaks is nice even if the issue is only in the autopkgtest as it helps the migration software to figure out the right versions to combine in the tests. More information about this bug and the reason for filing it can be found on https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation Paul [1] https://qa.debian.org/excuses.php?package=pandoc https://ci.debian.net/data/autopkgtest/testing/amd64/n/nbconvert/40824350/log.gz 378s [1m[31mE /usr/lib/python3/dist-packages/nbconvert/utils/pandoc.py:51: RuntimeWarning: You are using an unsupported version of pandoc (3.0.1).[0m 378s [1m[31mE Your version must be at least (1.12.1) but less than (3.0.0).[0m 378s [1m[31mE Refer to https://pandoc.org/installing.html.[0m 378s [1m[31mE Continuing with doubts...[0m 378s [1m[31mE check_pandoc_version()[0m 378s [1m[31mE [NbConvertApp] Support files will be in notebook2_files/[0m 378s [1m[31mE [NbConvertApp] Making directory ./notebook2_files[0m 378s [1m[31mE [NbConvertApp] Writing 2889 bytes to support file ./notebook2_files/notebook2_13_1.png[0m 378s [1m[31mE [NbConvertApp] Making directory ./notebook2_files[0m 378s [1m[31mE [NbConvertApp] Writing 74369 bytes to support file ./notebook2_files/notebook2_13_1.pdf[0m 378s [1m[31mE [NbConvertApp] Writing 25528 bytes to notebook.tex[0m 378s [1m[31mE [NbConvertApp] Building PDF[0m 378s [1m[31mE [NbConvertApp] Running xelatex 1 time: ['xelatex', 'notebook.tex', '-quiet'][0m 378s [1m[31mE [NbConvertApp] CRITICAL | xelatex failed: ['xelatex', 'notebook.tex', '-quiet'][0m 378s [1m[31mE [0m 378s [1m[31mE Traceback (most recent call last):[0m 378s [1m[31mE File "", line 198, in _run_module_as_main[0m 378s [1m[31mE File "", line 88, in _run_code[0m 378s [1m[31mE File "/usr/lib/python3/dist-packages/nbconvert/__main__.py", line 3, in [0m 378s [1m[31mE main()[0m 378s [1m[31mE File "/usr/lib/python3/dist-packages/jupyter_core/application.py", line 282, in launch_instance[0m 378s [1m[31mE super().launch_instance(argv=argv, **kwargs)[0m 378s [1m[31mE File "/usr/lib/python3/dist-packages/traitlets/config/application.py", line 982, in launch_instance[0m 378s [1m[31mE app.start()[0m 378s [1m[31mE File "/usr/lib/python3/dist-packages/nbconvert/nbconvertapp.py", line 423, in start[0m 378s [1m[31mE self.convert_notebooks()[0m 378s [1m[31mE File "/usr/lib/python3/dist-packages/nbconvert/nbconvertapp.py", line 597, in convert_notebooks[0m 378s [1m[31mE self.convert_single_notebook(notebook_filename)[0m 378s [1m[31mE File "/usr/lib/pytho
Bug#1072394: fcgiwrap: autopkgtest failures: The requested URL returned error: 500
Source: fcgiwrap
Version: 1.1.0-14
Severity: serious
Hello, since some days, the package starting return autopkgtest errors. I don't
know if this
is related to new git, or new nginx or something else.
https://ci.debian.net/packages/f/fcgiwrap/unstable/amd64/47141721/
34s autopkgtest [14:25:27]: test git-http-backend: [---
34s + cd /tmp/autopkgtest-lxc.9ukljw6a/downtmp/autopkgtest_tmp
34s + export GIT_AUTHOR_NAME=root
34s + export GIT_AUTHOR_EMAIL=root@localhost
34s + export GIT_AUTHOR_DATE=@1234567890 +
34s + export GIT_COMMITTER_NAME=root
34s + export GIT_COMMITTER_EMAIL=root@localhost
34s + export GIT_COMMITTER_DATE=@1234567890 +
34s + git init test1
34s hint: Using 'master' as the name for the initial branch. This default
branch name
34s hint: is subject to change. To configure the initial branch name to use in
all
34s hint: of your new repositories, which will suppress this warning, call:
34s hint:
34s hint: git config --global init.defaultBranch
34s hint:
34s hint: Names commonly chosen instead of 'master' are 'main', 'trunk' and
34s hint: 'development'. The just-created branch can be renamed via this
command:
34s hint:
34s hint: git branch -m
34s Initialized empty Git repository in
/tmp/autopkgtest-lxc.9ukljw6a/downtmp/autopkgtest_tmp/test1/.git/
34s + git -C test1 commit --allow-empty -m test
34s [master (root-commit) 0f8c7c0] test
34s + tee /etc/nginx/sites-available/default
34s server {
34slisten 80;
34s
34slocation / {
34sfastcgi_pass unix:/run/fcgiwrap.socket;
34sinclude fastcgi_params;
34sfastcgi_param SCRIPT_FILENAME
/usr/lib/git-core/git-http-backend;
34sfastcgi_param GIT_PROJECT_ROOT
"/tmp/autopkgtest-lxc.9ukljw6a/downtmp/autopkgtest_tmp";
34sfastcgi_param GIT_HTTP_EXPORT_ALL "";
34sfastcgi_param PATH_INFO $uri;
34sfastcgi_param NO_BUFFERING "";
34sfastcgi_buffering off;
34sgzip off;
34s}
34s }
34s + systemctl restart nginx
34s + git clone http://localhost/test1 test2
34s Cloning into 'test2'...
34s fatal: unable to access 'http://localhost/test1/': The requested URL
returned error: 500
35s autopkgtest [14:25:28]: test git-http-backend: ---]
Please have a look,
thanks
Gianfranco
OpenPGP_signature.asc
Description: OpenPGP digital signature
Bug#1004816: example
https://stackoverflow.com/questions/71565636/replacing-deprecated-avstream-codec-parameter-in-libav
Bug#1071691: nim: (build)-depends on obsolete pcre3 library
I have reported the issue upstream and asked them to port to pcre2: https://github.com/nim-lang/Nim/issues/23668 -- Alexander Kernozhitsky
Bug#1072390: marked as done (python3-requirements: Breaks+Replaces must be (<< 0.9.0-0.3~))
Your message dated Sun, 02 Jun 2024 11:52:20 + with message-id and subject line Bug#1072390: fixed in requirements-parser 0.9.0-0.4 has caused the Debian Bug report #1072390, regarding python3-requirements: Breaks+Replaces must be (<< 0.9.0-0.3~) 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.) -- 1072390: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1072390 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: python3-requirements Version: 0.9.0-0.3 Severity: serious X-Debbugs-Cc: Gavin Lai (賴建宇) , Alexandre Detiste , SZ Lin (林上智) ... Unpacking python3-requirements (0.9.0-0.3) ... dpkg: error processing archive /tmp/apt-dpkg-install-QTQFZ9/47-python3-requirements_0.9.0-0.3_all.deb (--unpack): trying to overwrite '/usr/lib/python3/dist-packages/requirements/__init__.py', which is also in package python3-requirement-parser 0.9.0-0.2 ... --- End Message --- --- Begin Message --- Source: requirements-parser Source-Version: 0.9.0-0.4 Done: Alexandre Detiste We believe that the bug you reported is fixed in the latest version of requirements-parser, 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 1072...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Alexandre Detiste (supplier of updated requirements-parser 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, 02 Jun 2024 13:30:11 +0200 Source: requirements-parser Architecture: source Version: 0.9.0-0.4 Distribution: unstable Urgency: medium Maintainer: Gavin Lai (賴建宇) Changed-By: Alexandre Detiste Closes: 1072390 Changes: requirements-parser (0.9.0-0.4) unstable; urgency=medium . * Non-maintainer upload. * Update Breaks+Replaces (Closes: #1072390) Checksums-Sha1: cb3c414e352072d3839fa3c5745b5da1b719eea1 2308 requirements-parser_0.9.0-0.4.dsc 23c237133055f225782887a22f2edf0384315577 3216 requirements-parser_0.9.0-0.4.debian.tar.xz 12204cb17bae211406bd8e0535788ef54a310c2d 7290 requirements-parser_0.9.0-0.4_source.buildinfo Checksums-Sha256: 0cf7e4cb7bcc659a44415f78b3f2d59d43f0effb27827fcf52bf111813da4b1a 2308 requirements-parser_0.9.0-0.4.dsc 222f2fe28b56a53c7b7f47abef55eed6e81b30ea6a5924498bee995b5a8d79e4 3216 requirements-parser_0.9.0-0.4.debian.tar.xz 077744628580c025e6cf757c096af3530180f08a4d2d734d72a3ccb79c39c489 7290 requirements-parser_0.9.0-0.4_source.buildinfo Files: f78f2f96f6ec72cffc2d20305dd41d97 2308 python optional requirements-parser_0.9.0-0.4.dsc ff1f36437dc197bf1447e0f584ac4d4f 3216 python optional requirements-parser_0.9.0-0.4.debian.tar.xz 3011312f2bea1c321d8d99a2a644ecef 7290 python optional requirements-parser_0.9.0-0.4_source.buildinfo -BEGIN PGP SIGNATURE- iQJFBAEBCgAvFiEEj23hBDd/OxHnQXSHMfMURUShdBoFAmZcWEgRHHRjaGV0QGRl Ymlhbi5vcmcACgkQMfMURUShdBpcWQ//U3cuJR7vnshYEwtJ/74NPkx/yacjSkkX 9BbXb4vwl9OXax1PCnNDSJsrzTggGZSbtz/YPp21JOboM0KptQaSxSp8VGkvLn0p r/0RJ34WCmY1syIG3p9DCjjKpki+wf0t2MrkJ7FBJnGZ+iePslCWF7ogiPHeu2lf qcFQAeTGMa3RGn7NULDr7TZ4ZvN9zHMMfDUqm1wlpDi5Jur+qR7WUAVizZY5YBa1 K97KgzWROF1p7Gs8cZCDBHHxqxhwgjxHqyc3WHf3QUdznJaF/ttKE8q627f9giVm xSxT5xSC9fy6VZWvEz9dJWYPltQjyK7bV+SkqPOI18LszCPyfnGW7SAVqXWZ5MQH nDyLbNb9iMGwJp6CYp8KS9wa8HMwTKCfkdUX6qBbYiqLCneu0FSZe07LUgeyN7qP HwFSuTCKl7AgwcUyq/qb1Ccgn7hL+OUlEkSY7np9rL3anqlyOiHKYPDuS+G9Blux 2F1DLHRpYZGB0ai+JylIYTPt9kzDbaLGTc+KDXP+Ca59ZwDjPieiG/UOpEYAg1qS 8Yrj6DkPtt+io98p/g5nycA3yrondDfP47gxW+XNSRtrstx7hsRv9ErsHHbroqdN cHLlhs2Bk/y75UxSbxdv+U6dJ3yBBU8AO/47AiVm8DkM7WwnF/Pvj/05POdHCIYo ExsfPaKvGdY= =VkYj -END PGP SIGNATURE- pgpdkLdnb1Ihq.pgp Description: PGP signature --- End Message ---
Bug#1072309: marked as done (neochat: Depends: qml-module-org-kde-kirigami-addons-delegates but it is not installable)
Your message dated Sun, 2 Jun 2024 13:49:55 +0200 with message-id and subject line Re: Bug#1072309: neochat: Depends: qml-module-org-kde-kirigami-addons-delegates but it is not installable has caused the Debian Bug report #1072309, regarding neochat: Depends: qml-module-org-kde-kirigami-addons-delegates but it is not installable to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1072309: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1072309 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: neochat Version: 23.08.5-2 Severity: serious X-Debbugs-Cc: sramac...@debian.org The dependencies of neochat cannot be satisfied: $ apt install neochat ... Unsatisfied dependencies: neochat : Depends: qml-module-org-kde-kirigami-addons-delegates but it is not installable Depends: qml-module-org-kde-kirigami-addons-components but it is not installabl Cheers -- Sebastian Ramacher --- End Message --- --- Begin Message --- On 2024-05-31 22:22:59 +0200, Sebastian Ramacher wrote: > Package: neochat > Version: 23.08.5-2 > Severity: serious > X-Debbugs-Cc: sramac...@debian.org > > The dependencies of neochat cannot be satisfied: > > $ apt install neochat > ... > Unsatisfied dependencies: > neochat : Depends: qml-module-org-kde-kirigami-addons-delegates but it is > not installable >Depends: qml-module-org-kde-kirigami-addons-components but it is > not installabl kirigami-addons with the new binary packages was accepted from NEW. Cheers -- Sebastian Ramacher--- End Message ---
Processed: python3-specreduce has an undeclared file conflict
Processing control commands: > affects -1 + pipenv python3-google-auth-oauthlib Bug #1072391 [python3-specreduce] python3-specreduce has an undeclared file conflict Added indication that 1072391 affects pipenv and python3-google-auth-oauthlib -- 1072391: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1072391 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1072391: python3-specreduce has an undeclared file conflict
Package: python3-specreduce Version: 1.4.0-1 Severity: serious User: debian...@lists.debian.org Usertags: fileconflict Control: affects -1 + pipenv python3-google-auth-oauthlib python3-specreduce has an undeclared file conflict. This may result in an unpack error from dpkg. The file /usr/lib/python3/dist-packages/build/lib/docs/conf.py is contained in the packages * pipenv/2023.12.1+ds-1 as present in trixie|unstable * python3-specreduce/1.4.0-1 as present in unstable The file /usr/lib/python3/dist-packages/docs/conf.py is contained in the packages * python3-google-auth-oauthlib/1.2.0-1 as present in trixie|unstable * python3-specreduce/1.4.0-1 as present in unstable These packages can be unpacked concurrently, because there is no relevant Replaces or Conflicts relation. Attempting to unpack these packages concurrently results in an unpack error from dpkg, because none of the packages installs a diversion for the affected files. Kind regards The Debian Usr Merge Analysis Tool This bug report has been automatically filed with no human intervention. The source code is available at https://salsa.debian.org/helmutg/dumat. If the filing is unclear or in error, don't hesitate to contact hel...@subdivi.de for assistance.
Processed: tags
Processing commands for cont...@bugs.debian.org: > tags 1070422 + ftbfs Bug #1070422 [src:intel-vc-intrinsics] src:intel-vc-intrinsics: unsatisfied build dependency in testing: llvm-14-dev Added tag(s) ftbfs. > tags 1071399 + ftbfs Bug #1071399 [src:ndcube] src:ndcube: unsatisfied build dependency in testing: python3-sunpy Added tag(s) ftbfs. > tags 1056198 + ftbfs Bug #1056198 [src:setuptools] src:setuptools: build depends on dh-python but build conflicts with python3-setuptools Added tag(s) ftbfs. > tags 1071398 + ftbfs Bug #1071398 [src:tea-cli] src:tea-cli: unsatisfied build dependency in testing: golang-github-go-git-go-git-dev Added tag(s) ftbfs. > thanks Stopping processing here. Please contact me if you need assistance. -- 1056198: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1056198 1070422: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1070422 1071398: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1071398 1071399: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1071399 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: severity of 1071118 is serious
Processing commands for cont...@bugs.debian.org: > severity 1071118 serious Bug #1071118 [src:openjdk-11] openjdk-11: Mssing builds on armel and armhf Severity set to 'serious' from 'normal' > thanks Stopping processing here. Please contact me if you need assistance. -- 1071118: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1071118 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1072390: python3-requirements: Breaks+Replaces must be (<< 0.9.0-0.3~)
Package: python3-requirements Version: 0.9.0-0.3 Severity: serious X-Debbugs-Cc: Gavin Lai (賴建宇) , Alexandre Detiste , SZ Lin (林上智) ... Unpacking python3-requirements (0.9.0-0.3) ... dpkg: error processing archive /tmp/apt-dpkg-install-QTQFZ9/47-python3-requirements_0.9.0-0.3_all.deb (--unpack): trying to overwrite '/usr/lib/python3/dist-packages/requirements/__init__.py', which is also in package python3-requirement-parser 0.9.0-0.2 ...
Bug#1060772: [Debian-pan-maintainers] Unifying jupyterlab and node-jupyterlab
On 6/2/24 12:53, Yadd wrote: On 6/2/24 10:38, Yadd wrote: In my last commit, I added also a fix for #1060772: - jupyter-lab uses yarnpkg by default - in Debian build context, this can be overridden using YARN_COMMAND=pkgjs-install-minimal Better hook with "YARN_COMMAND=pkgjs" which uses the adapted pkgjs-* command And this produces the final bundle without Internet access => fixes #1060772 :-D then I reimported your hook executed after dh_install to launch `jupyter-lab build`. This seems to work but must be verified (and also python install looks bad). Best regards, Xavier On 6/2/24 07:40, Yadd wrote: Hi Roland, I merged Python and Node.js package into branch "merge-python-and-node", but I didnt yet import the "build" part you entered into dh_auto_install in Python package. Build works but has to be cleaned for the Python part. Hope this will help you. Best regards, Xavier On 6/1/24 17:33, Yadd wrote: On 5/31/24 17:10, Roland Mas wrote: Since I haven't managed to get 4.1 to build yet, I'm thinking of starting from a known-working version (4.0.10+ds1+~cs11.25.27-1). I expect that porting to 4.1 or later afterwards won't add extra work compared to doing both jobs at once. Roland. OK, I just pushed 4.0.11 into node-jupyterlab repo (reverting your upgrade to 4.1.6) Le 30/05/2024 à 05:36, Yadd a écrit : On 5/29/24 17:06, Yadd wrote: On 5/29/24 17:04, Roland Mas wrote: Hi Yadd and others, I'd like to go forward with the jupyterlab/node-jupyterlab merger, because I'm facing more and more problems with jupyterlab/ipywidgets not being up-to-date. I'm going to start from node-jupyterlab (whose build is more complex), create a merge-jupyterlab-and-node-jupyterlab branch in it, and add the Python parts in there, starting from the current working state of the package (and not the current state of the master branch, which doesn't build since I tried to import a new upstream release). I'll ask for review before merging into master, but any help or advice in the meantime will be welcome. I'll try to be present on IRC more often than usual during the operation. Hopefully upgrading one source package will be easier after the merger, and I'll work on ipywidgets after that. Roland. hi, OK, let's do that ;-) From which version of jupyterlab do you want to start? 4.0.11 or later?
Bug#1060772: [Debian-pan-maintainers] Unifying jupyterlab and node-jupyterlab
On 6/2/24 10:38, Yadd wrote: In my last commit, I added also a fix for #1060772: - jupyter-lab uses yarnpkg by default - in Debian build context, this can be overridden using YARN_COMMAND=pkgjs-install-minimal Better hook with "YARN_COMMAND=pkgjs" which uses the adapted pkgjs-* command then I reimported your hook executed after dh_install to launch `jupyter-lab build`. This seems to work but must be verified (and also python install looks bad). Best regards, Xavier On 6/2/24 07:40, Yadd wrote: Hi Roland, I merged Python and Node.js package into branch "merge-python-and-node", but I didnt yet import the "build" part you entered into dh_auto_install in Python package. Build works but has to be cleaned for the Python part. Hope this will help you. Best regards, Xavier On 6/1/24 17:33, Yadd wrote: On 5/31/24 17:10, Roland Mas wrote: Since I haven't managed to get 4.1 to build yet, I'm thinking of starting from a known-working version (4.0.10+ds1+~cs11.25.27-1). I expect that porting to 4.1 or later afterwards won't add extra work compared to doing both jobs at once. Roland. OK, I just pushed 4.0.11 into node-jupyterlab repo (reverting your upgrade to 4.1.6) Le 30/05/2024 à 05:36, Yadd a écrit : On 5/29/24 17:06, Yadd wrote: On 5/29/24 17:04, Roland Mas wrote: Hi Yadd and others, I'd like to go forward with the jupyterlab/node-jupyterlab merger, because I'm facing more and more problems with jupyterlab/ipywidgets not being up-to-date. I'm going to start from node-jupyterlab (whose build is more complex), create a merge-jupyterlab-and-node-jupyterlab branch in it, and add the Python parts in there, starting from the current working state of the package (and not the current state of the master branch, which doesn't build since I tried to import a new upstream release). I'll ask for review before merging into master, but any help or advice in the meantime will be welcome. I'll try to be present on IRC more often than usual during the operation. Hopefully upgrading one source package will be easier after the merger, and I'll work on ipywidgets after that. Roland. hi, OK, let's do that ;-) From which version of jupyterlab do you want to start? 4.0.11 or later?
Processed: bug 1072366 is forwarded to https://github.com/jpirko/libndp/issues/26
Processing commands for cont...@bugs.debian.org: > # many thanks to Salvatore Bonaccorso for filing at both Debian and upstream > forwarded 1072366 https://github.com/jpirko/libndp/issues/26 Bug #1072366 [src:libndp] libndp: CVE-2024-5564 Set Bug forwarded-to-address to 'https://github.com/jpirko/libndp/issues/26'. > thanks Stopping processing here. Please contact me if you need assistance. -- 1072366: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1072366 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
