Bug#971783: mate-volume-control-status-icon dies here too
Hi Mike. Thanks for your reply about 1.26. But it seems that the project don't want to take on this. https://github.com/mate-desktop/mate-media/issues/159 https://github.com/mate-desktop/mate-media/issues/167 https://github.com/mate-desktop/mate-media/issues/109 https://github.com/mate-desktop/mate-media/issues/148 https://github.com/mate-desktop/mate-media/issues/137 https://github.com/mate-desktop/mate-media/issues/104 https://github.com/mate-desktop/mate-media/issues/89 This is problematic because we use this little icon a lot. Thanks. Max.
Processed: Re: debootstrap: --no-merged-usr became a no-op
Processing control commands: > affects -1 mmdebstrap Bug #998867 [debootstrap] debootstrap: --no-merged-usr became a no-op Added indication that 998867 affects mmdebstrap -- 998867: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=998867 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#998867: debootstrap: --no-merged-usr became a no-op
Control: affects -1 mmdebstrap Hi, Quoting Dimitri John Ledkov (2021-11-15 14:54:36) > > Please point out what you plan to do about this change in debootstrap so > > that I can adapt the mmdebstrap autopkgtest accordingly. > > I did notice the mmdebstrap autopkgtest regression. [...] this bug has now been open and RC for 10 days. Those are 10 days in which I will not notice any other possible regression in mmdebstrap because its autopkgtest fails early. Until I know how you plan to address this bug I cannot fix the problem in mmdebstrap because any possible fix would only be able to migrate after debootstrap with whatever solution is chosen to this bug migrates. So please either: a) decide that this bug is not RC and thus let debootstrap with its current behaviour migrate to testing or b) tell me what other solution you see in the bug -- i can even contribute a patch if you tell me how you want this bug solved Thanks! cheers, josch signature.asc Description: signature
Processed: Re: prototypejs: FTBFS
Processing control commands: > severity -1 normal Bug #993301 [src:prototypejs] prototypejs: FTBFS Severity set to 'normal' from 'serious' -- 993301: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=993301 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#993301: prototypejs: FTBFS
Control: severity -1 normal On 18/11/2021 20.24, Bastien ROUCARIES wrote: The source is https://github.com/prototypejs/prototype/tree/master and I can rebuild prototypejs/1.7.1-3.1 in sid and bullseye without problems. What errors do you encounter? Yes but this not prefered source of modification... Without a reproducible FTBFS I'm downgrading the severity. Sée thé salsa tree un order to understand why i need rake Which repository are you talking about? Andreas
Processed: Re: mate-volume-control-status-icon dies here too
Processing control commands: > severity -1 serious Bug #971783 [mate-media] mate-media: volume-control-applet dies often Severity set to 'serious' from 'normal' -- 971783: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=971783 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1000178: llvmlite: FTBFS with Python 3.10
Source: llvmlite
Version: 0.37.0-1
Severity: serious
User: debian-pyt...@lists.debian.org
Usertags: python3.10
Hi Maintainer
llvmlite FTBFS with Python 3.10 as a supported version [1]. I've
copied what I hope is the relevant part of the log below.
Regards
Graham
[1] https://buildd.debian.org/status/package.php?p=llvmlite
I: pybuild base:237: python3.10 setup.py clean
Traceback (most recent call last):
File "/<>/setup.py", line 55, in
_guard_py_ver()
File "/<>/setup.py", line 52, in _guard_py_ver
raise RuntimeError(msg.format(cur_py, min_py, max_py))
RuntimeError: Cannot install on Python version 3.10.0; only versions
>=3.7,<3.10 are supported.
E: pybuild pybuild:354: clean: plugin distutils failed with: exit
code=1: python3.10 setup.py clean
dh_auto_clean: error: pybuild --clean -i python{version} -p "3.10 3.9"
returned exit code 13
make: *** [debian/rules:10: clean] Error 25
Bug#1000163: phast FTBFS: pcre.h: No such file or directory
Hi Adrian, Am Thu, Nov 18, 2021 at 11:13:33PM +0200 schrieb Adrian Bunk: > Source: phast > Version: 1.6+dfsg-2 > Severity: serious > Tags: ftbfs > > https://buildd.debian.org/status/logs.php?pkg=phast=1.6%2Bdfsg-2 > > ... > /<>/src/../include/phast/stringsplus.h:27:10: fatal error: > pcre.h: No such file or directory >27 | #include > | ^~~~ > compilation terminated. > make[4]: *** [Makefile:13: phast_list_of_lists.o] Error 1 Just for the sake of interest: If this would not have built in my own pbuilder chroot I would not have considered uploading. Well, I could have checked Salsa CI first but it seems my assumption "builds in pbuilder so it builds in autobuilders and CI" is wrong. Any idea how I can track down this? Kind regards Andreas. -- http://fam-tille.de
Bug#999367: marked as done (py-postgresql ftbfs with Python 3.10 (test failures))
Your message dated Fri, 19 Nov 2021 03:35:08 + with message-id and subject line Bug#999367: fixed in py-postgresql 1.2.1+git20180803.ef7b9a9-4 has caused the Debian Bug report #999367, regarding py-postgresql ftbfs with Python 3.10 (test failures) 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.) -- 999367: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=999367 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: py-postgresql Version: 1.2.1+git20180803.ef7b9a9-3 Severity: important Tags: ftbfs User: debian-pyt...@lists.debian.org Usertags: python3.10 py-postgresql ftbfs with python3-defaults from experimental: [...] == ERROR: postgresql.test.testall (unittest.loader._FailedTest) -- ImportError: Failed to import test module: postgresql.test.testall Traceback (most recent call last): File "/usr/lib/python3.10/unittest/loader.py", line 436, in _find_test_path module = self._get_module_from_name(name) File "/usr/lib/python3.10/unittest/loader.py", line 377, in _get_module_from_name __import__(name) File "/<>/py-postgresql-1.2.1+git20180803.ef7b9a9/.pybuild/cpython3_3.10_postgresql/build/postgresql/test/testall.py", line 7, in from ..installation import default File "/<>/py-postgresql-1.2.1+git20180803.ef7b9a9/.pybuild/cpython3_3.10_postgresql/build/postgresql/installation.py", line 17, in from . import api as pg_api File "/<>/py-postgresql-1.2.1+git20180803.ef7b9a9/.pybuild/cpython3_3.10_postgresql/build/postgresql/api.py", line 207, in collections.Iterator, AttributeError: module 'collections' has no attribute 'Iterator' -- Ran 19 tests in 0.003s FAILED (errors=18) E: pybuild pybuild:354: test: plugin distutils f --- End Message --- --- Begin Message --- Source: py-postgresql Source-Version: 1.2.1+git20180803.ef7b9a9-4 Done: Stefano Rivera We believe that the bug you reported is fixed in the latest version of py-postgresql, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 999...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Stefano Rivera (supplier of updated py-postgresql 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: Thu, 18 Nov 2021 23:14:39 -0400 Source: py-postgresql Architecture: source Version: 1.2.1+git20180803.ef7b9a9-4 Distribution: unstable Urgency: medium Maintainer: Debian Python Team Changed-By: Stefano Rivera Closes: 999367 Changes: py-postgresql (1.2.1+git20180803.ef7b9a9-4) unstable; urgency=medium . [ Stefano Rivera ] * Team upload. * Patch: Python 3.10 support. (Closes: #999367) . [ Debian Janitor ] * Bump debhelper from old 12 to 13. * Set upstream metadata fields: Bug-Database, Bug-Submit, Repository, Repository-Browse. * Update standards version to 4.5.1, no changes needed. Checksums-Sha1: 989e60a3039f820b3a7a05837d8759216dfb0471 1706 py-postgresql_1.2.1+git20180803.ef7b9a9-4.dsc 0b58206ffe7aaf30df9f53ebf7459a55de7bdd5c 11156 py-postgresql_1.2.1+git20180803.ef7b9a9-4.debian.tar.xz 4679aed0e101107ac523bb853e4f0a448145b137 7266 py-postgresql_1.2.1+git20180803.ef7b9a9-4_source.buildinfo Checksums-Sha256: b5256e6f4843efc594b2bdbe47d275a674a053730a8675770fe1d71c8e6b1c17 1706 py-postgresql_1.2.1+git20180803.ef7b9a9-4.dsc da7392e56b6dc36c9e5849e6164526e4d48167873b4b0d9daceef686561c6e7d 11156 py-postgresql_1.2.1+git20180803.ef7b9a9-4.debian.tar.xz 8996adbbeadf496a4afdbb8cf548fd1f1cc54170750b63e33bb27f95666bc3dd 7266 py-postgresql_1.2.1+git20180803.ef7b9a9-4_source.buildinfo Files: 051aa0523cd0c6540f93278383687fdf 1706 python optional py-postgresql_1.2.1+git20180803.ef7b9a9-4.dsc 063946ae7095d0a06699c5ae5e22289b 11156 python optional py-postgresql_1.2.1+git20180803.ef7b9a9-4.debian.tar.xz 0d85ded83b1d6fe400bc7bca75da90a6 7266 python optional py-postgresql_1.2.1+git20180803.ef7b9a9-4_source.buildinfo -BEGIN PGP SIGNATURE-
Bug#997719: libvirt-python: FTBFS: ERROR: failed virDomainGetMessages
Hi Lucas (2021.10.24_07:40:18_-0400) Looks like a mismatch between libvirt-python and libvirt itself, that would be resolved by upgrading it to version 7.6.0 (or later). SR
Bug#997363: libtorrent-rasterbar: FTBFS: configure: error: *** A compiler with support for C++17 language features is required.
Presumably resolved in 2.0.0 in NEW, that doesn't use autoconf any more. SR
Bug#984256: nextepc: ftbfs with GCC-11
Package: nextepc
Version: 0.3.10+nods-4.1
Followup-For: Bug #984256
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu jammy ubuntu-patch
Control: tags -1 patch
Hi Ruben,
Please find attached a patch for this issue. It has been uploaded to Ubuntu
to fix the build failure there.
--
Steve Langasek Give me a lever long enough and a Free OS
Debian Developer to set it on, and I can move the world.
Ubuntu Developer https://www.debian.org/
slanga...@ubuntu.com vor...@debian.org
diff -Nru nextepc-0.3.10+nods/debian/patches/gcc-11.patch
nextepc-0.3.10+nods/debian/patches/gcc-11.patch
--- nextepc-0.3.10+nods/debian/patches/gcc-11.patch 1969-12-31
16:00:00.0 -0800
+++ nextepc-0.3.10+nods/debian/patches/gcc-11.patch 2021-11-18
17:50:37.0 -0800
@@ -0,0 +1,27 @@
+Description: fix build failure with gcc-11.
+Author: Steve Langasek
+Bug-Debian: https://bugs.debian.org/984256
+Last-Update: 2021-11-18
+
+Index: nextepc-0.3.10+nods/lib/core/test/testatomic.c
+===
+--- nextepc-0.3.10+nods.orig/lib/core/test/testatomic.c
nextepc-0.3.10+nods/lib/core/test/testatomic.c
+@@ -100,7 +100,7 @@
+
+ static void test_casptr_equal_nonnull(abts_case *tc, void *data)
+ {
+-int a, b;
++int a = 0, b = 0;
+ void *target_ptr =
+ void *old_ptr;
+
+@@ -111,7 +111,7 @@
+
+ static void test_casptr_notequal(abts_case *tc, void *data)
+ {
+-int a, b;
++int a = 0, b = 0;
+ void *target_ptr =
+ void *old_ptr;
+
diff -Nru nextepc-0.3.10+nods/debian/patches/series
nextepc-0.3.10+nods/debian/patches/series
--- nextepc-0.3.10+nods/debian/patches/series 2021-01-23 14:35:09.0
-0800
+++ nextepc-0.3.10+nods/debian/patches/series 2021-11-18 17:49:29.0
-0800
@@ -5,3 +5,4 @@
0005-Set-install-dir-for-freediameter-libs.patch
0006-Fix-big-endian-bug.patch
0007-Patch-deprecated-sys-sysctl.h-problem.patch
+gcc-11.patch
Processed: Re: nextepc: ftbfs with GCC-11
Processing control commands: > tags -1 patch Bug #984256 [src:nextepc] nextepc: ftbfs with GCC-11 Added tag(s) patch. -- 984256: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=984256 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1000175: python3-lz4tools is empty
Package: python3-lz4tools Version: 1.3.1.1-4 Severity: grave $ dpkg -L python3-lz4tools /. /usr /usr/share /usr/share/doc /usr/share/doc/python3-lz4tools /usr/share/doc/python3-lz4tools/changelog.Debian.gz /usr/share/doc/python3-lz4tools/copyright $
Bug#999815: cryptsetup - build-depends on removed package.
On Thu, 18 Nov 2021 at 23:13:59 +0100, Christian Göttsche wrote: > A quick test build without those two build-dependencies resulted in > identical binary packages. They are currently pulled transitively by libdevmapper-dev, so removing them from the explicit Build-Depends doesn't yield a different build environment. -- Guilhem. signature.asc Description: PGP signature
Bug#998455: regina-normal: b-d on python3-all-dev, but not built for all supported Python3 versions
Thanks - there is a new upstream release coming hopefully within the next month, and I will update the build-depends when I push that through. - Ben.
Bug#998443: marked as done (sugar-datastore: b-d on python3-all-dev, but not built for all supported Python3 versions)
Your message dated Thu, 18 Nov 2021 22:05:11 + with message-id and subject line Bug#998443: fixed in sugar-datastore 0.118-3 has caused the Debian Bug report #998443, regarding sugar-datastore: b-d on python3-all-dev, but not built for all supported Python3 versions 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.) -- 998443: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=998443 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: sugar-datastore Version: 0.118-2 Severity: important Tags: ftbfs bookworm sid User: debian-pyt...@lists.debian.org Usertags: python3.10 python3-all-dev Hi Maintainer This package build-depends on python3-all-dev, but does not build extensions/libraries for all supported python3 versions. This is seen on the transition tracker for adding python3.10 support [1] and creates false positives. Please either replace the b-d python3-all-dev with python3-dev, or build for all supported Python3 versions. With the former solution yet get later exposure to a new python3 version, with the latter solution you get early exposure. Regards Graham [1] https://release.debian.org/transitions/html/python3.10-add.html --- End Message --- --- Begin Message --- Source: sugar-datastore Source-Version: 0.118-3 Done: Jonas Smedegaard We believe that the bug you reported is fixed in the latest version of sugar-datastore, 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 998...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Jonas Smedegaard (supplier of updated sugar-datastore 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: Thu, 18 Nov 2021 23:44:50 +0100 Source: sugar-datastore Architecture: source Version: 0.118-3 Distribution: unstable Urgency: medium Maintainer: Debian Sugar Team Changed-By: Jonas Smedegaard Closes: 998443 Changes: sugar-datastore (0.118-3) unstable; urgency=medium . * update copyright info: + use Reference field (not License-Reference); tighten lintian overrides + update coverage * build-depend on python3-dev (not python3-all-dev); closes: bug#998443, thanks to Graham Inggs * declare compliance with Debian Policy 4.6.0 * simplify source helper script copyright-check Checksums-Sha1: c544a2bba0e23e7f1088af94da3f74977ddda999 2096 sugar-datastore_0.118-3.dsc 9b0e8ee5ca5abff8de8fc1a83e15ee71490d74bb 9488 sugar-datastore_0.118-3.debian.tar.xz 49a3e3c157ba8c7b8a07fd3a95754d7e961a6f97 7159 sugar-datastore_0.118-3_amd64.buildinfo Checksums-Sha256: f9baae9f76b1dc7a1d60bab78024659dacc4e35c0af840223e585e3c632f6f35 2096 sugar-datastore_0.118-3.dsc ff5d3da6a9c38979e0315351e9657eb29e58cb575d9896387b66c4ed6b0b801e 9488 sugar-datastore_0.118-3.debian.tar.xz 72a8e1c7af7af56b42275e4f5559bb9e08a1fff0b0d9525633a883d30b2135ed 7159 sugar-datastore_0.118-3_amd64.buildinfo Files: e2b8dc1a6305126d73afd3280df82664 2096 python optional sugar-datastore_0.118-3.dsc ebc232b5b88f2a28bd747e23a2624e42 9488 python optional sugar-datastore_0.118-3.debian.tar.xz 830402c518b6f34ece328fd12b09f492 7159 python optional sugar-datastore_0.118-3_amd64.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEn+Ppw2aRpp/1PMaELHwxRsGgASEFAmGW2WoACgkQLHwxRsGg ASFAdg//Qc2lmbgm6WS8i/BHqEa9gk1wC4TzO13YqB0Fd987/nNBmaXIP956rloM WQZp0lRW5E1IThRA7NUiPkF2YHicCwDG/ecjO4GBoYTN8K7gjK/fMDIOQYPET0Ru otwbdNY/Q7O9Z+IYJeO7cnU59NWxHW8zwSprSDi3O1U0IldRErEdom8+cHnIj5Uu a2CIVyM4yyxDL1wa4Ii1O/nDWO/TpV3ZTaCM35krgc3TpiOZvXDg1lmbkxzOTIrs xhnzb+LW4S0qPOX7X/Wldyk5H6HAsLTkadwjlBMkZqA9dV1cWUIs8p2npGUWkR9x RLLVSfgME5YruFeyQ11kRpZb1JBrHsioPkZamHNJ/P2hPezMfp2ciheZw+rQcTOx 02TXoe6C3Z9WOjH/Z5zyrVjefoxgELA++zNUgC2OqaTiyRduyks4Bf1WGOMjrGsm f7kuAJqSCHdFYEemnRs+q26vZBv5VPTN3qRELTVpoao5cFkQHapXJ7y7nloHrh/h puGRfJ3JWRoaM4GUGevkJqNkzCYVESSbPAhKS+NU6jEbrz4jsdMvPDilOwUYmFX5 CQBmF2/6LtzdgsmfS/HR/OmSm8mLm2Y6men7jz+70sYX0qHf3Sg63LDYQT5JMA5e lRUXBCh0Qki8cLxu9EQH4TG5qexDmpQycQxEJtJ4fGcsDoB2CQ0= =H54m -END PGP SIGNATURE End Message ---
Bug#995980: marked as done (assimp FTCBFS: very wrong python dependency and more issues)
Your message dated Thu, 18 Nov 2021 22:03:38 + with message-id and subject line Bug#995980: fixed in assimp 5.0.1~ds0-4 has caused the Debian Bug report #995980, regarding assimp FTCBFS: very wrong python dependency and more issues 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.) -- 995980: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=995980 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: assimp Version: 5.0.1~ds0-3 Tags: patch Control: clone -1 -2 Control: retitle -2 rules-require-build-prerequisite gives bogus advice Control: reassign -2 lintian Control: severity -2 important Control: tags -2 - patch Control: affects -2 src:assimp User: debian-cr...@lists.debian.org Usertags: ftcbfs X-Debbugs-Cc: debhel...@packages.debian.org X-Debbugs-Cc: debian-cr...@lists.debian.org assimp fails to cross build from source. It attempts to build a python module, but it ultimately fails doing so. While inspecting this, I discovered that assimp "Build-Depends: python3:any | python3-all:any | python3-dev:any | python3-all-dev:any | dh-sequence-python3". This is wrong on so many levels. For starters, sbuild ignores any alternative in unstable, so in practice, this happens to become "python3:any". Any other alternative is simply ignored and shouldn't be there. Then, issuing a dependency on python3-dev:any without libpython3-dev is practically never correct. That could be a separate lintian tag, but that's not too bad here as python3-dev isn't needed. Either you go python3-dev or you go python3-dev:any, libpython3-dev or you have a very special and unusual use case that I have never encountered anywhere. Also listing dh-sequence-python3 there is bogus. You already added "--with python3" in debian/rules. This is duplicate at best. Either should be dropped, but enabling a dh-addon in an alternative is clearly not right, and debhelper should likely fail hard when encountering that. Niels, do you agree? I wondered how one would come up with such a strange dependency and asked #debian-mentors for help. Kindly, a user named "itd" pointed me at the lintian tag rules-require-build-prerequisite, which very likely is the cause for this. Please disable the tag right now as it does more harm than good. While the tag isn't bad per-se, the advice it gives misleads users and produces broken packages. I request hiding or disabling it now and then figuring out what it really should say. Back to assimp. I looked into this to make it cross buildable, right? And it was failing in Python-ish stuff. So why do we actually build the Python module? Did I say module? It's not an extension? No, it isn't. And we really don't have to build it in an arch-only build. So the key to making assimp cross buildable is to make an arch-only build fully skip the Python stuff. And once you do that, you don't care about :any annotations anymore as those are practically irrelevant in Build-Depends-Indep. So I've attached a patch for assimp to fix the cross build and the strange build dependency. Please consider applying it. Helmut diff --minimal -Nru assimp-5.0.1~ds0/debian/changelog assimp-5.0.1~ds0/debian/changelog --- assimp-5.0.1~ds0/debian/changelog 2021-10-06 09:02:14.0 +0200 +++ assimp-5.0.1~ds0/debian/changelog 2021-10-08 20:49:28.0 +0200 @@ -1,3 +1,15 @@ +assimp (5.0.1~ds0-3.1) UNRELEASED; urgency=medium + + * Non-maintainer upload. + * Fix python build dependency. (Closes: #-1) ++ Alternatives in Build-Depends are ignored. ++ Enable the python3 dh addon once only. ++ Build python module in indep build only. ++ Move python Build-Depends to B-D-I. ++ Drop the :any nonsense. + + -- Helmut Grohne Fri, 08 Oct 2021 20:49:28 +0200 + assimp (5.0.1~ds0-3) unstable; urgency=medium [ Debian Janitor ] diff --minimal -Nru assimp-5.0.1~ds0/debian/control assimp-5.0.1~ds0/debian/control --- assimp-5.0.1~ds0/debian/control 2021-10-06 09:02:14.0 +0200 +++ assimp-5.0.1~ds0/debian/control 2021-10-08 20:49:28.0 +0200 @@ -15,8 +15,10 @@ libstb-dev, libutfcpp-dev, zlib1g-dev | libz-dev, - python3:any | python3-all:any | python3-dev:any | python3-all-dev:any | dh-sequence-python3, doxygen, +Build-Depends-Indep: + dh-sequence-python3, + python3, Rules-Requires-Root: no Vcs-Git: https://salsa.debian.org/debian/assimp.git Vcs-Browser: https://salsa.debian.org/debian/assimp diff --minimal -Nru assimp-5.0.1~ds0/debian/rules assimp-5.0.1~ds0/debian/rules --- assimp-5.0.1~ds0/debian/rules 2021-10-06 09:02:14.0 +0200 +++
Bug#998442: marked as done (link-grammar: b-d on python3-all-dev, but not built for all supported Python3 versions)
Your message dated Thu, 18 Nov 2021 21:50:09 + with message-id and subject line Bug#998442: fixed in link-grammar 5.10.2~dfsg-2 has caused the Debian Bug report #998442, regarding link-grammar: b-d on python3-all-dev, but not built for all supported Python3 versions 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.) -- 998442: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=998442 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: link-grammar Version: 5.10.2~dfsg-1 Severity: important Tags: ftbfs User: debian-pyt...@lists.debian.org Usertags: python3.10 python3-all-dev Hi Maintainer This package build-depends on python3-all-dev, but does not build extensions/libraries for all supported python3 versions. This is seen on the transition tracker for adding python3.10 support [1] and creates false positives. Please either replace the b-d python3-all-dev with python3-dev, or build for all supported Python3 versions. With the former solution yet get later exposure to a new python3 version, with the latter solution you get early exposure. Regards Graham [1] https://release.debian.org/transitions/html/python3.10-add.html --- End Message --- --- Begin Message --- Source: link-grammar Source-Version: 5.10.2~dfsg-2 Done: Jonas Smedegaard We believe that the bug you reported is fixed in the latest version of link-grammar, 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 998...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Jonas Smedegaard (supplier of updated link-grammar 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: Thu, 18 Nov 2021 23:32:19 +0100 Source: link-grammar Architecture: source Version: 5.10.2~dfsg-2 Distribution: unstable Urgency: medium Maintainer: Jonas Smedegaard Changed-By: Jonas Smedegaard Closes: 998442 Changes: link-grammar (5.10.2~dfsg-2) unstable; urgency=medium . * revert to disable sh4 as java-supported architecture * build-depend on python3-dev (not python3-all-dev); closes: bug#998442, thanks to Graham Inggs * update copyright info: update coverage Checksums-Sha1: 7c708c6a17845e49f4dc5d44b21fe1a363b69a89 3079 link-grammar_5.10.2~dfsg-2.dsc 8a2e58ab22d1c295dbe46b084bf6d2fafe68a36e 29644 link-grammar_5.10.2~dfsg-2.debian.tar.xz 54098eb24539d00b0c9ecef9f5f3b48b02d8d47e 13461 link-grammar_5.10.2~dfsg-2_amd64.buildinfo Checksums-Sha256: 8a62a4afb67a81afa47701776a1f445a6b310946a9f61be023be0daeea1c8a6c 3079 link-grammar_5.10.2~dfsg-2.dsc 40afb02ac097eb8912a64f9188bae511b30d4bac0b7e7834b4f174a5159fd99e 29644 link-grammar_5.10.2~dfsg-2.debian.tar.xz 2909c4c037330ddb4dc7651572d76e6576af1eaa8191a1d5f71363528fbb3722 13461 link-grammar_5.10.2~dfsg-2_amd64.buildinfo Files: aaa558a11dd116dd3c39cf3391c5aca3 3079 text optional link-grammar_5.10.2~dfsg-2.dsc 742be8f700cb81dd54be8c670a5ab3d1 29644 text optional link-grammar_5.10.2~dfsg-2.debian.tar.xz 5f1d96c1e7201870f3dc0f988e763537 13461 text optional link-grammar_5.10.2~dfsg-2_amd64.buildinfo -BEGIN PGP SIGNATURE- iQIyBAEBCgAdFiEEn+Ppw2aRpp/1PMaELHwxRsGgASEFAmGW2K8ACgkQLHwxRsGg ASFX7A/46X5TThOn8/PIl7CBQqddHN7Hxy3pGnzARu1oaPD7Xzi2gAS/u8du7O1Y q7QgtthDDfrAucAk7mKYNnf5hC89NQ5DPS2i2oyZGVWtzEQ14llCa6PSIrxJk9yS wJe3kZkjCXZQQVmvlHZaFrWcMNgVhT9LficeIF1Im+FZYRNlgDId+DdZjoi30nRZ WtCOSZ8T7C8+f3L+5e4cc9B1mKRfhMoazvJgK4frkUH2hkrLLZfV0xXdLaxJf7K6 46oLHalL6y4UTLUwrdGqkz7sxGxwmyd0kkRft8+JpnltCIH4oFsgL4nteqE2P2nH hog/hz0eCECRpdmAyeUQkeQTJSAc4njPbtJl0zqc0idUtuaZDuCvZ4TdPQT//4Tw 6Bto5Q5PXOsxrt5X5Q7pmGibAbpi6wUBSTBjsUNVkNWeD70wbK1X5S81dO4UccK6 z60Mw7S45A4mlZn8qiJTq1AvuGVHyGJNWjq7UG5fNLJKk4eNVh432G3tdaLHatvH G0WKfMeqIIawHBKHhqf6ijupuP+2uQlmDHmpxSY5CQqFvZSsiUk9PKfbxnt4U9Yj peEnclu8Y5YOR2hWtqCoAknI9FAZ0JGSG/zO2celecVIZHhrTQ0PdwAd1J6D1Tq8 9qeyiJg7SzUh3euJIV/nJczOGBWyRs6heKkbzTNESEftOywWQw== =6S2E -END PGP SIGNATURE End Message ---
Bug#1000169: gufw: Does not start
Package: gufw Version: 20.04.1-2 Severity: grave Justification: renders package unusable X-Debbugs-Cc: witold.bary...@gmail.com It is broken: root@debian:~# gufw /usr/bin/gufw: line 2: [: =: unary operator expected ls: cannot access '/usr/lib/python*/site-packages/gufw/gufw.py': No such file or directory Unable to init server: Could not connect: Connection refused Unable to init server: Could not connect: Connection refused (gufw.py:3421888): Gdk-CRITICAL **: 21:47:05.154: gdk_keymap_get_for_display: assertion 'GDK_IS_DISPLAY (display)' failed (gufw.py:3421888): Gdk-CRITICAL **: 21:47:05.154: gdk_keymap_get_modifier_mask: assertion 'GDK_IS_KEYMAP (keymap)' failed (gufw.py:3421888): Gdk-CRITICAL **: 21:47:05.154: gdk_keymap_get_for_display: assertion 'GDK_IS_DISPLAY (display)' failed (gufw.py:3421888): Gtk-CRITICAL **: 21:47:05.154: _gtk_replace_virtual_modifiers: assertion 'GDK_IS_KEYMAP (keymap)' failed (gufw.py:3421888): Gdk-CRITICAL **: 21:47:05.154: gdk_keymap_get_for_display: assertion 'GDK_IS_DISPLAY (display)' failed (gufw.py:3421888): Gdk-CRITICAL **: 21:47:05.154: gdk_keymap_get_modifier_mask: assertion 'GDK_IS_KEYMAP (keymap)' failed (gufw.py:3421888): Gdk-CRITICAL **: 21:47:05.154: gdk_keymap_get_for_display: assertion 'GDK_IS_DISPLAY (display)' failed (gufw.py:3421888): Gtk-CRITICAL **: 21:47:05.154: _gtk_replace_virtual_modifiers: assertion 'GDK_IS_KEYMAP (keymap)' failed (gufw.py:3421888): Gdk-CRITICAL **: 21:47:05.154: gdk_keymap_get_for_display: assertion 'GDK_IS_DISPLAY (display)' failed (gufw.py:3421888): Gdk-CRITICAL **: 21:47:05.154: gdk_keymap_get_modifier_mask: assertion 'GDK_IS_KEYMAP (keymap)' failed (gufw.py:3421888): Gdk-CRITICAL **: 21:47:05.154: gdk_keymap_get_for_display: assertion 'GDK_IS_DISPLAY (display)' failed (gufw.py:3421888): Gtk-CRITICAL **: 21:47:05.154: _gtk_replace_virtual_modifiers: assertion 'GDK_IS_KEYMAP (keymap)' failed (gufw.py:3421888): Gdk-CRITICAL **: 21:47:05.154: gdk_keymap_get_for_display: assertion 'GDK_IS_DISPLAY (display)' failed (gufw.py:3421888): Gdk-CRITICAL **: 21:47:05.154: gdk_keymap_get_modifier_mask: assertion 'GDK_IS_KEYMAP (keymap)' failed (gufw.py:3421888): Gdk-CRITICAL **: 21:47:05.154: gdk_keymap_get_for_display: assertion 'GDK_IS_DISPLAY (display)' failed (gufw.py:3421888): Gtk-CRITICAL **: 21:47:05.154: _gtk_replace_virtual_modifiers: assertion 'GDK_IS_KEYMAP (keymap)' failed (gufw.py:3421888): Gdk-CRITICAL **: 21:47:05.154: gdk_keymap_get_for_display: assertion 'GDK_IS_DISPLAY (display)' failed (gufw.py:3421888): Gdk-CRITICAL **: 21:47:05.154: gdk_keymap_get_modifier_mask: assertion 'GDK_IS_KEYMAP (keymap)' failed (gufw.py:3421888): Gdk-CRITICAL **: 21:47:05.154: gdk_keymap_get_for_display: assertion 'GDK_IS_DISPLAY (display)' failed (gufw.py:3421888): Gtk-CRITICAL **: 21:47:05.154: _gtk_replace_virtual_modifiers: assertion 'GDK_IS_KEYMAP (keymap)' failed (gufw.py:3421888): Gdk-CRITICAL **: 21:47:05.154: gdk_keymap_get_for_display: assertion 'GDK_IS_DISPLAY (display)' failed (gufw.py:3421888): Gdk-CRITICAL **: 21:47:05.154: gdk_keymap_get_modifier_mask: assertion 'GDK_IS_KEYMAP (keymap)' failed (gufw.py:3421888): Gdk-CRITICAL **: 21:47:05.154: gdk_keymap_get_for_display: assertion 'GDK_IS_DISPLAY (display)' failed (gufw.py:3421888): Gtk-CRITICAL **: 21:47:05.154: _gtk_replace_virtual_modifiers: assertion 'GDK_IS_KEYMAP (keymap)' failed (gufw.py:3421888): Gdk-CRITICAL **: 21:47:05.154: gdk_keymap_get_for_display: assertion 'GDK_IS_DISPLAY (display)' failed (gufw.py:3421888): Gdk-CRITICAL **: 21:47:05.154: gdk_keymap_get_modifier_mask: assertion 'GDK_IS_KEYMAP (keymap)' failed (gufw.py:3421888): Gdk-CRITICAL **: 21:47:05.154: gdk_keymap_get_for_display: assertion 'GDK_IS_DISPLAY (display)' failed (gufw.py:3421888): Gtk-CRITICAL **: 21:47:05.154: _gtk_replace_virtual_modifiers: assertion 'GDK_IS_KEYMAP (keymap)' failed (gufw.py:3421888): Gdk-CRITICAL **: 21:47:05.154: gdk_keymap_get_for_display: assertion 'GDK_IS_DISPLAY (display)' failed (gufw.py:3421888): Gdk-CRITICAL **: 21:47:05.154: gdk_keymap_get_modifier_mask: assertion 'GDK_IS_KEYMAP (keymap)' failed (gufw.py:3421888): Gdk-CRITICAL **: 21:47:05.154: gdk_keymap_get_for_display: assertion 'GDK_IS_DISPLAY (display)' failed (gufw.py:3421888): Gtk-CRITICAL **: 21:47:05.154: _gtk_replace_virtual_modifiers: assertion 'GDK_IS_KEYMAP (keymap)' failed (gufw.py:3421888): Gdk-CRITICAL **: 21:47:05.154: gdk_keymap_get_for_display: assertion 'GDK_IS_DISPLAY (display)' failed (gufw.py:3421888): Gdk-CRITICAL **: 21:47:05.154: gdk_keymap_get_modifier_mask: assertion 'GDK_IS_KEYMAP (keymap)' failed (gufw.py:3421888): Gdk-CRITICAL **: 21:47:05.154: gdk_keymap_get_for_display: assertion 'GDK_IS_DISPLAY (display)' failed (gufw.py:3421888): Gtk-CRITICAL **: 21:47:05.154: _gtk_replace_virtual_modifiers: assertion 'GDK_IS_KEYMAP (keymap)' failed (gufw.py:3421888): Gdk-CRITICAL **: 21:47:05.154: gdk_keymap_get_for_display:
Bug#995843: abook: complete d/copyright file
Hi Rhonda, I've seen that you pushed some commits to your repo and Salsa, great :). Do you still plan to upload them to Debian (tesing removal would be tomorrow)? I've also seen that you force pushed away some commits.. just wondering. And yes I would be happy if you add me to the repo members, thanks! Jochen * Rhonda D'Vine [2021-11-02 12:54]: Hey Jochen, resolving would need to enhance the copyright file so that it fulfills all the required information. Bastian already did a good job and likely the patch provided should be sufficient for that. I haven't gotten around yet to upload that, but plan to do so in the next few days. I likely will move the packaging from my private git instance to salsa, and if you are still interested I can add you to the repository indeed. Thanks for your interest, Rhonda * Jochen Sprickerhof [2021-11-02 08:20:15 CET]: Hi Rhonda, abook is marked for autoremoval in two days due to this bug, can you comment on how to resolve it? I would be happy to help maintain abook, if you need help. Cheers Jochen * Bastian Germann [2021-10-13 14:40]: > Control: tags -1 patch > > Hi, > > A copyright file for abook with the necessary fixes for this bug is enclosed. > Please include it in a new package revision. > > Thanks, > Bastian > Format: https://www.debian.org/doc/packaging-manuals/copyright-format/1.0/ > Upstream-Name: abook > Upstream-Contact: Jaakko Heinonen > Source: http://abook.sourceforge.net/ > > Files: * > Copyright: 2005, Jaakko Heinonen > Comment: No license version is specified for most of the code. > Some GPL-2+ files make the project as a whole GPL-2+. > License: GPL-2+ > > Files: abook.1 abookrc.5 > Copyright: Alan Ford > License: GPL-2+ > > Files: aclocal.m4 config.rpath Makefile.in m4/* > Copyright: (see individual files) > Comment: Some files come with the disclaimer, some do not. > License: FSFULLR > > Files: config.guess config.sub > Copyright: 1992-2013 Free Software Foundation, Inc. > License: GPL-3+ with Autoconf exception > > Files: depcomp > Copyright: 1999-2013 Free Software Foundation, Inc. > License: GPL-2+ > > Files: getname.c > Copyright: This code was taken from hypermail > modified by Jaakko Heinonen > . > For strcpymax() function: > Copyright (C) 1994, 1995 Enterprise Integration Technologies Corp. > VeriFone Inc./Hewlett-Packard. All Rights Reserved. > Comment: See https://bugs.debian.org/979098 for details on assuming GPL-2+ > License: GPL-2+ > > Files: getopt* > Copyright: 1987-1997 Free Software Foundation, Inc. > License: LGPL-2+ > > Files: install-sh > Copyright: 1994 X Consortium > License: X11 > > Files: ldif.c > Copyright: 1992-1996 Regents of the University of Michigan. > Comment: adapted to use with abook by JH > License: Michigan > Redistribution and use in source and binary forms are permitted > provided that this notice is preserved and that due credit is given > to the University of Michigan at Ann Arbor. The name of the University > may not be used to endorse or promote products derived from this > software without specific prior written permission. This software > is provided ``as is'' without express or implied warranty. > > Files: mbswidth.? > Copyright: 2000-2002 Free Software Foundation, Inc. > License: GPL-2+ > > Files: misc.c > Copyright: Jaakko Heinonen > 1994 Lars Wirzenius > Comment: BSD-2-clause covers the getaline() function. > License: GPL-2+ and BSD-2-clause > > Files: missing > Copyright: 1996-2013 Free Software Foundation, Inc. > License: GPL-2+ > > Files: po/fr.po po/it.po po/sv.po > Copyright: 2005 Free Software Foundation, Inc. > License: GPL-2+ > > Files: vcard.c > Copyright: 2012, Raphaël Droz > License: GPL-2+ > > Files: views.c > Copyright: Cedric Duval > License: GPL-2+ > > Files: xmalloc.c > Copyright: 2005 Jaakko Heinonen > License: BSD-2-clause > > Files: debian/* > Copyright: 2000, Alan Ford > 2003, Rhonda D'Vine > 2015, Denis Briand > License: WTFPLv2 > > License: GPL-2+ >This program is free software; you can redistribute it and/or modify >it under the terms of the GNU General Public License as published by >the Free Software Foundation; either version 2 of the License, or >(at your option) any later version. >. >This program is distributed in the hope that it will be useful, >but WITHOUT ANY WARRANTY; without even the implied warranty of >MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the >GNU General Public License for more details. >. >You should have received a copy of the GNU General Public License >along with this program; if not, write to the Free Software >Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, >MA 02110-1301 USA. >. > On Debian GNU/Linux systems, the complete text of the GNU General > Public License version 2 can be found in `/usr/share/common-licenses/GPL-2', > later versions can be found
Bug#997399: marked as done (caja-admin: FTBFS: dh_auto_configure: error: cd obj-x86_64-linux-gnu && LC_ALL=C.UTF-8 meson .. --wrap-mode=nodownload --buildtype=plain --prefix=/usr --sysconfdir=/etc --l
Your message dated Thu, 18 Nov 2021 21:33:51 + with message-id and subject line Bug#997399: fixed in caja-admin 0.0.5-1 has caused the Debian Bug report #997399, regarding caja-admin: FTBFS: dh_auto_configure: error: cd obj-x86_64-linux-gnu && LC_ALL=C.UTF-8 meson .. --wrap-mode=nodownload --buildtype=plain --prefix=/usr --sysconfdir=/etc --localstatedir=/var --libdir=lib/x86_64-linux-gnu returned exit code 1 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.) -- 997399: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997399 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: caja-admin Version: 0.0.3-1 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20211023 ftbfs-bookworm Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > dpkg-buildpackage > - > > Command: dpkg-buildpackage -us -uc -sa -rfakeroot > dpkg-buildpackage: info: source package caja-admin > dpkg-buildpackage: info: source version 0.0.3-1 > dpkg-buildpackage: info: source distribution unstable > dpkg-buildpackage: info: source changed by Mike Gabriel > dpkg-source --before-build . > dpkg-buildpackage: info: host architecture amd64 > debian/rules clean > dh clean --with python3 >dh_clean > dpkg-source -b . > dpkg-source: info: using source format '3.0 (quilt)' > dpkg-source: info: building caja-admin using existing > ./caja-admin_0.0.3.orig.tar.gz > dpkg-source: info: building caja-admin in caja-admin_0.0.3-1.debian.tar.xz > dpkg-source: info: building caja-admin in caja-admin_0.0.3-1.dsc > debian/rules binary > dh binary --with python3 >dh_update_autotools_config >dh_autoreconf >dh_auto_configure > cd obj-x86_64-linux-gnu && LC_ALL=C.UTF-8 meson .. > --wrap-mode=nodownload --buildtype=plain --prefix=/usr --sysconfdir=/etc > --localstatedir=/var --libdir=lib/x86_64-linux-gnu > The Meson build system > Version: 0.59.2 > Source dir: /<> > Build dir: /<>/obj-x86_64-linux-gnu > Build type: native build > Project name: caja-admin > Project version: 0.0.3 > Host machine cpu family: x86_64 > Host machine cpu: x86_64 > Configuring caja-admin.py using configuration > Configuring org.freedesktop.caja-admin.policy using configuration > > ../po/meson.build:3:0: ERROR: add_project_arguments keyword argument > "language" unknown languages: python > > A full log can be found at > /<>/obj-x86_64-linux-gnu/meson-logs/meson-log.txt > cd obj-x86_64-linux-gnu && tail -v -n \+0 meson-logs/meson-log.txt > ==> meson-logs/meson-log.txt <== > Build started at 2021-10-23T07:44:00.010315 > Main binary: /usr/bin/python3 > Build Options: -Dprefix=/usr -Dlibdir=lib/x86_64-linux-gnu > -Dlocalstatedir=/var -Dsysconfdir=/etc -Dbuildtype=plain > -Dwrap_mode=nodownload > Python system: Linux > The Meson build system > Version: 0.59.2 > Source dir: /<> > Build dir: /<>/obj-x86_64-linux-gnu > Build type: native build > Project name: caja-admin > Project version: 0.0.3 > Build machine cpu family: x86_64 > Build machine cpu: x86_64 > Host machine cpu family: x86_64 > Host machine cpu: x86_64 > Target machine cpu family: x86_64 > Target machine cpu: x86_64 > Configuring caja-admin.py using configuration > Configuring org.freedesktop.caja-admin.policy using configuration > > ../po/meson.build:3:0: ERROR: add_project_arguments keyword argument > "language" unknown languages: python > dh_auto_configure: error: cd obj-x86_64-linux-gnu && LC_ALL=C.UTF-8 meson .. > --wrap-mode=nodownload --buildtype=plain --prefix=/usr --sysconfdir=/etc > --localstatedir=/var --libdir=lib/x86_64-linux-gnu returned exit code 1 > make: *** [debian/rules:5: binary] Error 25 The full build log is available from: http://qa-logs.debian.net/2021/10/23/caja-admin_0.0.3-1_unstable.log A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! If you reassign this bug to another package, please marking it as 'affects'-ing this package. See https://www.debian.org/Bugs/server-control#affects If you fail to reproduce this, please provide a build log and diff it with mine so that we can identify if something relevant changed in the meantime. --- End Message --- --- Begin Message --- Source: caja-admin Source-Version: 0.0.5-1 Done: Mike Gabriel We believe that the bug you reported is fixed in the latest version of caja-admin, which is due to be installed in the Debian FTP archive. A summary of the changes between this
Bug#1000165: xdmf FTBFS with more than one supported python3 version
Source: xdmf Version: 3.0+git20190531-8 Severity: serious Tags: ftbfs https://buildd.debian.org/status/logs.php?pkg=xdmf=3.0%2Bgit20190531-8%2Bb1 ... dh_missing -a -O--buildsystem=cmake dh_missing: warning: usr/lib/python3.10/xdmf/Xdmf.py exists in debian/tmp but is not installed to anywhere (related file: "debian/tmp/usr/lib/python3.9/xdmf/Xdmf.py") dh_missing: warning: usr/lib/python3.10/xdmf/XdmfCore.py exists in debian/tmp but is not installed to anywhere (related file: "debian/tmp/usr/lib/python3.9/xdmf/XdmfCore.py") dh_missing: warning: usr/lib/python3.10/xdmf/XdmfUtils.py exists in debian/tmp but is not installed to anywhere (related file: "debian/tmp/usr/lib/python3.9/xdmf/XdmfUtils.py") dh_missing: warning: usr/lib/python3.10/xdmf/__Xdmf.so exists in debian/tmp but is not installed to anywhere (related file: "debian/tmp/usr/lib/python3.9/xdmf/__Xdmf.so") dh_missing: warning: usr/lib/python3.10/xdmf/__XdmfCore.so exists in debian/tmp but is not installed to anywhere (related file: "debian/tmp/usr/lib/python3.9/xdmf/__XdmfCore.so") dh_missing: warning: usr/lib/python3.10/xdmf/__XdmfUtils.so exists in debian/tmp but is not installed to anywhere (related file: "debian/tmp/usr/lib/python3.9/xdmf/__XdmfUtils.so") dh_missing: error: missing files, aborting
Bug#984201: marked as done (libosl: ftbfs with GCC-11)
Your message dated Thu, 18 Nov 2021 21:19:31 +
with message-id
and subject line Bug#984201: fixed in libosl 0.8.0-4
has caused the Debian Bug report #984201,
regarding libosl: ftbfs with GCC-11
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.)
--
984201: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=984201
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:libosl
Version: 0.8.0-3
Severity: normal
Tags: sid bookworm
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-11
[This bug is not targeted to the upcoming bullseye release]
Please keep this issue open in the bug tracker for the package it
was filed for. If a fix in another package is required, please
file a bug for the other package (or clone), and add a block in this
package. Please keep the issue open until the package can be built in
a follow-up test rebuild.
The package fails to build in a test rebuild on at least amd64 with
gcc-11/g++-11, but succeeds to build with gcc-10/g++-10. The
severity of this report will be raised before the bookworm release,
so nothing has to be done for the bullseye release.
The full build log can be found at:
http://people.debian.org/~doko/logs/20210228/filtered/gcc11/libosl_0.8.0-3_unstable_gcc11.log
The last lines of the build log are at the end of this report.
To build with GCC 11, either set CC=gcc-11 CXX=g++-11 explicitly,
or install the gcc, g++, gfortran, ... packages from experimental.
apt-get -t=experimental install g++
Common build failures are new warnings resulting in build failures with
-Werror turned on, or new/dropped symbols in Debian symbols files.
For other C/C++ related build failures see the porting guide at
http://gcc.gnu.org/gcc-11/porting_to.html
GCC 11 defaults to the GNU++17 standard. If your package installs
header files in /usr/include, please don't work around C++17 issues
by choosing a lower C++ standard for the package build, but fix these
issues to build with the C++17 standard.
[...]
177 | osl::misc::LightMutex::scoped_lock lock(m);
| ^
In file included from /<>/full/osl/search/searchTimer.cc:3:
/<>/full/osl/search/searchTimer.h: In member function ‘bool
osl::search::SearchTimer::stopping() const’:
/<>/full/osl/search/searchTimer.h:118:38: error: ‘shared_timer’
was not declared in this scope
118 | bool stopping() const { return shared_timer->stop_all; }
| ^~~~
/<>/full/osl/search/searchTimer.h: In member function ‘void
osl::search::SearchTimer::stopNow()’:
/<>/full/osl/search/searchTimer.h:121:9: error: ‘shared_timer’ was
not declared in this scope
121 | shared_timer->stop_reason = SearchTimerCommon::StopByOutside;
| ^~~~
/<>/full/osl/search/searchTimer.h: In member function
‘osl::search::SearchTimerCommon::StopReason
osl::search::SearchTimer::stopReason()’:
/<>/full/osl/search/searchTimer.h:124:59: error: ‘shared_timer’
was not declared in this scope
124 | SearchTimerCommon::StopReason stopReason() { return
shared_timer->stop_reason; }
| ^~~~
/<>/full/osl/search/searchTimer.h: In member function ‘void
osl::search::SearchTimer::throwIfNoMoreTime(uint64_t)’:
/<>/full/osl/search/searchTimer.h:127:38: error: ‘shared_timer’
was not declared in this scope
127 | SearchTimerCommon& shared = *shared_timer;
| ^~~~
/<>/full/osl/search/searchTimer.h: In member function ‘int
osl::search::SearchTimer::nodeAffordable() const’:
/<>/full/osl/search/searchTimer.h:147:28: error: ‘shared_timer’
was not declared in this scope
147 | const double nps = shared_timer->nps;
|^~~~
/<>/full/osl/search/searchTimer.h: In member function ‘bool
osl::search::SearchTimer::hasMonitor() const’:
/<>/full/osl/search/searchTimer.h:157:18: error: ‘shared_timer’
was not declared in this scope
157 | return ! shared_timer->monitors.empty();
| ^~~~
/<>/full/osl/search/searchTimer.h: In member function ‘int
osl::search::SearchTimer::lastMemoryUseRatio1000() const’:
/<>/full/osl/search/searchTimer.h:165:16: error: ‘shared_timer’
was not declared in this scope
165 | return shared_timer->last_memory_use1000;
|^~~~
[ 62%] Building CXX object
CMakeFiles/osl-static.dir/full/osl/search/simpleHashRecord.cc.o
/usr/bin/c++ -DBOOST_FILESYSTEM_VERSION=3
Bug#1000163: phast FTBFS: pcre.h: No such file or directory
Source: phast Version: 1.6+dfsg-2 Severity: serious Tags: ftbfs https://buildd.debian.org/status/logs.php?pkg=phast=1.6%2Bdfsg-2 ... /<>/src/../include/phast/stringsplus.h:27:10: fatal error: pcre.h: No such file or directory 27 | #include | ^~~~ compilation terminated. make[4]: *** [Makefile:13: phast_list_of_lists.o] Error 1
Bug#999409: marked as done (jpy ftbfs with Python 3.10)
Your message dated Thu, 18 Nov 2021 21:05:59 + with message-id and subject line Bug#999409: fixed in jpy 0.9.0-4 has caused the Debian Bug report #999409, regarding jpy ftbfs with Python 3.10 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 999409: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=999409 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: jpy Version: 0.9.0-3 Severity: important Tags: ftbfs User: debian-pyt...@lists.debian.org Usertags: python3.10 jpy ftbfs with python3-defaults from experimental: https://launchpadlibrarian.net/567963939/buildlog_ubuntu-jammy-amd64.jpy_0.9.0-3build5_BUILDING.txt.gz src/main/c/jpy_jmethod.c:847:5: note: (near initialization for ‘JOverloadedMethod_Type.tp_vectorcall_offset’) x86_64-linux-gnu-gcc -Wno-unused-result -Wsign-compare -DNDEBUG -g -fwrapv -O2 -Wall -g -fstack-protector-strong -Wformat -Werror=format-security -g -fwrapv -O2 -g -O2 -ffile-prefix-map=/<>=. -flto=auto -ffat-lto-objects -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC -Isrc/main/c -I/usr/lib/jvm/default-java/include -I/usr/lib/jvm/default-java/include/linux -I/usr/include/python3.10 -c src/main/c/jpy_jobj.c -o build/temp.linux-x86_64-3.10/src/main/c/jpy_jobj.o src/main/c/jpy_jobj.c: In function ‘JType_InitSlots’: src/main/c/jpy_jobj.c:683:24: error: lvalue required as left operand of assignment 683 | Py_REFCNT(typeObj) = 1; |^ error: command '/usr/bin/x86_64-linux-gnu-gcc' failed with exit code 1 E: pybuild pybuild:354: build: plugin distutils failed with: exit code=1: /usr/bin/python3.10 setup.py build I: pybuild base:237: /usr/bin/python3 setup.py build --- End Message --- --- Begin Message --- Source: jpy Source-Version: 0.9.0-4 Done: Stefano Rivera We believe that the bug you reported is fixed in the latest version of jpy, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 999...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Stefano Rivera (supplier of updated jpy 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: Thu, 18 Nov 2021 13:54:06 -0400 Source: jpy Architecture: source Version: 0.9.0-4 Distribution: unstable Urgency: medium Maintainer: Debian Python Team Changed-By: Stefano Rivera Closes: 946109 999409 Changes: jpy (0.9.0-4) unstable; urgency=medium . * Team upload. . [ Alastair McKinstry ] * Drop hard-coded xz compression * Use dh-sequence-python3 rather than --with python3 * Use debhelper-compat (=13) * Standards-Version: 4.5.1 * Add d/gpb.conf pointing to DEP-14 branches * Point vcs-git to debian/latest branch . [ Louis-Philippe Véronneau ] * Update the VCS paths. Closes: #946109 . [ Debian Janitor ] * Trim trailing whitespace. * Use secure copyright file specification URI. * Drop custom source compression. * Set upstream metadata fields: Bug-Database, Bug-Submit, Repository, Repository-Browse. . [ Ondřej Nový ] * d/control: Update Maintainer field with new Debian Python Team contact address. * d/control: Update Vcs-* fields with new Debian Python Team Salsa layout. . [ Stefano Rivera ] * Patch: Python 3.10 support, thanks Steve Langasek (Closes: #999409) * Declare Rules-Requires-Root: no. Checksums-Sha1: 586ff9563baa8351072bf5929fb149151350b5d8 1387 jpy_0.9.0-4.dsc 535e63bb72c312ab9c5460accd2cf6e582e7fb2b 5996 jpy_0.9.0-4.debian.tar.xz 89ff2418ae5a15a2c535f5411dc85395d54914bf 5996 jpy_0.9.0-4_source.buildinfo Checksums-Sha256: 82cfd2b0b9fc1148980c8bfcbf852d546af94ab542db1894597cfaf323e1bd8d 1387 jpy_0.9.0-4.dsc 25cefd52792af5208801c62133e608634fc61c6e802992d1b9badde9e7529454 5996 jpy_0.9.0-4.debian.tar.xz 8d582adb843e9b441b17cc6b91b60f46091359800f7b56f07f8955bd392e9fde 5996 jpy_0.9.0-4_source.buildinfo Files: 5937dab556044ee1227226d23a034e65 1387 python optional jpy_0.9.0-4.dsc 1cff2b78b574214fc2af6d1a42c9a38a 5996 python optional jpy_0.9.0-4.debian.tar.xz 3a050b75e784e9f37cf648084cadf97e 5996 python optional jpy_0.9.0-4_source.buildinfo -BEGIN PGP
Bug#997877:
I think an update to 3.3.5 will fix this. I have no idea how hard mailman3 upstream updates are :)
Processed: raise severity of python3.10 bugs
Processing commands for cont...@bugs.debian.org: > severity 995980 serious Bug #995980 [src:assimp] assimp FTCBFS: very wrong python dependency and more issues Ignoring request to change severity of Bug 995980 to the same value. > severity 998395 serious Bug #998395 [src:google-auth-httplib2] FTBFS: very wrong python dependency Severity set to 'serious' from 'important' > severity 998398 serious Bug #998398 [src:python-imgviz] FTBFS: very wrong python dependency Severity set to 'serious' from 'important' > severity 998441 serious Bug #998441 [src:reprozip] reprozip: FTBFS on 2nd reproducible build Severity set to 'serious' from 'normal' > severity 998442 serious Bug #998442 [src:link-grammar] link-grammar: b-d on python3-all-dev, but not built for all supported Python3 versions Severity set to 'serious' from 'important' > severity 998443 serious Bug #998443 [src:sugar-datastore] sugar-datastore: b-d on python3-all-dev, but not built for all supported Python3 versions Severity set to 'serious' from 'important' > severity 998455 serious Bug #998455 [src:regina-normal] regina-normal: b-d on python3-all-dev, but not built for all supported Python3 versions Severity set to 'serious' from 'important' > severity 998471 serious Bug #998471 [src:gpgme1.0] gpgme1.0: b-d on python3-all-dev, but not built for all supported Python3 versions Severity set to 'serious' from 'important' > severity 999402 serious Bug #999402 [src:pyasn] pyasn ftbfs with Python 3.10 (test failures) Severity set to 'serious' from 'important' > severity 999405 serious Bug #999405 [src:python-cytoolz] python-cytoolz ftbfs with Python 3.10 (test failures) Severity set to 'serious' from 'important' > severity 999409 serious Bug #999409 [src:jpy] jpy ftbfs with Python 3.10 Severity set to 'serious' from 'important' > severity 999410 serious Bug #999410 [src:python-rocksdb] python-rocksdb ftbfs with Python 3.10 Severity set to 'serious' from 'important' > thanks Stopping processing here. Please contact me if you need assistance. -- 995980: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=995980 998395: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=998395 998398: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=998398 998441: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=998441 998442: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=998442 998443: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=998443 998455: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=998455 998471: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=998471 999402: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=999402 999405: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=999405 999409: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=999409 999410: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=999410 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: severity of 995980 is serious
Processing commands for cont...@bugs.debian.org: > severity 995980 serious Bug #995980 [src:assimp] assimp FTCBFS: very wrong python dependency and more issues Severity set to 'serious' from 'important' > thanks Stopping processing here. Please contact me if you need assistance. -- 995980: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=995980 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1000162: ima-evm-utils: FTBFS with no internet connection
Source: ima-evm-utils Severity: serious Version: 1.3.2-2.1 Hey, Your package fails to build from scratch in an environment with no internect connection. Please check the buildd logs for this. Thanks, Bastian
Bug#999632: r-bioc-isoformswitchanalyzer FTBFS: ERROR: dependencies ‘DRIMSeq’, ‘tximeta’ are not available
On 14.11.21 08:47, Andreas Tille wrote: Control: blocked -1 by 995252 Hi Steffen ERROR: dependencies ‘DRIMSeq’, ‘tximeta’ are not available for package ‘IsoformSwitchAnalyzeR’ r-bioc-tximeta is in Debian and just needs to be mentioned in Build-Depends. However, Git seems not to be up to date so please push. Seems like we have a race condition. I dumped my local one and routine-updated what was in salsa. What is the status of r-bioc-drimseq? I have not found it in new neither did I found any mentioning it on the maintainers list. g...@salsa.debian.org:r-pkg-team/r-bioc-drimseq.git Seems like I had not uploaded it. Just upgraded it to a newer version and sent it away. PS: Please use a chroot when building your packages. I typically do. For the ones with build dependencies in the NEW queue I once had my own local repository but at some point stopped doing that. Steffen
Processed: Re: vtk7: ftbfs with GCC-11
Processing control commands: > tags -1 patch Bug #984401 [src:vtk7] vtk7: ftbfs with GCC-11 Added tag(s) patch. -- 984401: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=984401 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#984401: vtk7: ftbfs with GCC-11
Package: vtk7
Version: 7.1.1+dfsg2-10
Followup-For: Bug #984401
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu jammy ubuntu-patch
Control: tags -1 patch
Please find attached a patch which has been uploaded to Ubuntu to fix this
build failure.
--
Steve Langasek Give me a lever long enough and a Free OS
Debian Developer to set it on, and I can move the world.
Ubuntu Developer https://www.debian.org/
slanga...@ubuntu.com vor...@debian.org
diff -Nru vtk7-7.1.1+dfsg2/debian/patches/gcc-11.patch
vtk7-7.1.1+dfsg2/debian/patches/gcc-11.patch
--- vtk7-7.1.1+dfsg2/debian/patches/gcc-11.patch1969-12-31
16:00:00.0 -0800
+++ vtk7-7.1.1+dfsg2/debian/patches/gcc-11.patch2021-11-18
09:30:28.0 -0800
@@ -0,0 +1,53 @@
+Description: gcc-11 compatibility
+Author: Steve Langasek
+Bug-Debian: https://bugs.debian.org/984401
+Last-Update: 2021-11-18
+
+Index: vtk7-7.1.1+dfsg2/ThirdParty/xdmf2/vtkxdmf2/libsrc/XdmfDsmComm.cxx
+===
+--- vtk7-7.1.1+dfsg2.orig/ThirdParty/xdmf2/vtkxdmf2/libsrc/XdmfDsmComm.cxx
vtk7-7.1.1+dfsg2/ThirdParty/xdmf2/vtkxdmf2/libsrc/XdmfDsmComm.cxx
+@@ -52,7 +52,7 @@
+ XdmfErrorMessage("Cannot Receive Message of Length = " <<
Msg->Length);
+ return(XDMF_FAIL);
+ }
+-if(Msg->Data <= 0 ){
++if(!Msg->Data){
+ XdmfErrorMessage("Cannot Receive Message into Data Buffer = " <<
Msg->Length);
+ return(XDMF_FAIL);
+ }
+@@ -66,7 +66,7 @@
+ XdmfErrorMessage("Cannot Send Message of Length = " << Msg->Length);
+ return(XDMF_FAIL);
+ }
+-if(Msg->Data <= 0 ){
++if(!Msg->Data){
+ XdmfErrorMessage("Cannot Send Message from Data Buffer = " <<
Msg->Length);
+ return(XDMF_FAIL);
+ }
+Index: vtk7-7.1.1+dfsg2/Rendering/Label/vtkLabelHierarchyPrivate.h
+===
+--- vtk7-7.1.1+dfsg2.orig/Rendering/Label/vtkLabelHierarchyPrivate.h
vtk7-7.1.1+dfsg2/Rendering/Label/vtkLabelHierarchyPrivate.h
+@@ -66,7 +66,7 @@
+ {
+ }
+
+-bool operator () ( const vtkIdType& a, const vtkIdType& b )
++bool operator () ( const vtkIdType& a, const vtkIdType& b ) const
+ {
+ if (0 == this->Hierarchy)
+ {
+Index: vtk7-7.1.1+dfsg2/Rendering/Label/vtkLabelHierarchy.cxx
+===
+--- vtk7-7.1.1+dfsg2.orig/Rendering/Label/vtkLabelHierarchy.cxx
vtk7-7.1.1+dfsg2/Rendering/Label/vtkLabelHierarchy.cxx
+@@ -525,7 +525,7 @@
+ {
+ public:
+ bool operator()(const vtkHierarchyNode & a,
+-const vtkHierarchyNode & b)
++const vtkHierarchyNode & b) const
+ {
+ if (a.Level != b.Level)
+ {
diff -Nru vtk7-7.1.1+dfsg2/debian/patches/series
vtk7-7.1.1+dfsg2/debian/patches/series
--- vtk7-7.1.1+dfsg2/debian/patches/series 2020-12-15 11:51:51.0
-0800
+++ vtk7-7.1.1+dfsg2/debian/patches/series 2021-11-18 09:28:09.0
-0800
@@ -23,3 +23,4 @@
mysq8_my_bool.patch
3edc0de2b04ae1e100c229e592d6b9fa94f2915a.patch
581d9eb874b2b80a3fb21c739a96fa6f955ffb5e.patch
+gcc-11.patch
Bug#995999: marked as done (FTBFS: FAIL: TestChunkDiskMapper_WriteChunk_Chunk_IterateChunks)
Your message dated Thu, 18 Nov 2021 19:37:19 + with message-id and subject line Bug#995999: fixed in prometheus 2.31.1+ds1-1 has caused the Debian Bug report #995999, regarding FTBFS: FAIL: TestChunkDiskMapper_WriteChunk_Chunk_IterateChunks 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.) -- 995999: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=995999 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: prometheus Version: 2.24.1+ds-1 Severity: serious X-Debbugs-Cc: z...@debian.org Hi, When rebuild packages, I find it FTBFS. === RUN TestChunkDiskMapper_WriteChunk_Chunk_IterateChunks --- FAIL: TestChunkDiskMapper_WriteChunk_Chunk_IterateChunks (0.05s) panic: runtime error: slice bounds out of range [:104326] with capacity 104293 [recovered] panic: runtime error: slice bounds out of range [:104326] with capacity 104293 goroutine 7 [running]: testing.tRunner.func1.2(0x60da60, 0xc0005f8030) /usr/lib/go-1.16/src/testing/testing.go:1143 +0x332 testing.tRunner.func1(0xc01e00) /usr/lib/go-1.16/src/testing/testing.go:1146 +0x4b6 panic(0x60da60, 0xc0005f8030) /usr/lib/go-1.16/src/runtime/panic.go:965 +0x1b9 github.com/prometheus/prometheus/tsdb/chunks.TestChunkDiskMapper_WriteChunk_Chunk_IterateChunks(0xc01e00) /build/1st/prometheus-2.24.1+ds/build/src/github.com/prometheus/prometheus/tsdb/chunks/head_chunks_test.go:122 +0xc9c testing.tRunner(0xc01e00, 0x637600) /usr/lib/go-1.16/src/testing/testing.go:1193 +0xef created by testing.(*T).Run /usr/lib/go-1.16/src/testing/testing.go:1238 +0x2b3 FAILgithub.com/prometheus/prometheus/tsdb/chunks0.116s It also FTBFS on tests.reproducible-builds.org, ci.debian.net https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/prometheus.html https://ci.debian.net/data/autopkgtest/unstable/amd64/p/prometheus/15535224/log.gz --- End Message --- --- Begin Message --- Source: prometheus Source-Version: 2.31.1+ds1-1 Done: Guillem Jover We believe that the bug you reported is fixed in the latest version of prometheus, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 995...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Guillem Jover (supplier of updated prometheus 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: Thu, 18 Nov 2021 19:18:18 +0100 Source: prometheus Architecture: source Version: 2.31.1+ds1-1 Distribution: unstable Urgency: medium Maintainer: Debian Go Packaging Team Changed-By: Guillem Jover Closes: 981110 995999 Changes: prometheus (2.31.1+ds1-1) unstable; urgency=medium . * Team upload. . [ Guillem Jover ] * New upstream release. - Fix build failure in test suite with Go 1.16. (Closes: #995999) * Use $(BUILDDIR) uniformly instead of the literal build/. * Update copyright claims. * Move note about license location on Debian systems into a Comment field. * Update version.BuildUser to match the Maintainer address. * Decapitalize synopsis first word. * Update gitlab-ci.yml from latest upstream version. * Add After=time-sync.target to systemd unit file. (Closes: #981110) * Switch to Standards-Version 4.6.0 (no changes needed). * Add missing build dependencies needed by new upstream release. * Refresh patches for new upstream release. * Disable XDS, Uyuni, Linode and Scaleway support. * Revert upstream commits introducing unavailable dependencies. * Fix test failure for dennwc/varint. * Replace patch with entry in DH_GOLANG_INSTALL_EXTRA. * Add required fixtures for new upstream release to DH_GOLANG_INSTALL_EXTRA. * Use dh-sequence-golang instead of dh-golang and --with=golang. * Update debian/copyright for new upstream. * Update default file from latest upstream output. * Add /.pc/ to .gitignore. * Switch to use .build/ as the build directory like upstream. . [ Daniel Swarbrick ] * Unvendor github.com/prometheus/exporter-toolkit * Add new build-dep golang-github-prometheus-exporter-toolkit-dev . [ Martina Ferrari ] * Correct my email address. Checksums-Sha1:
Bug#993301: prototypejs: FTBFS
Le mer. 17 nov. 2021 à 13:02, Andreas Beckmann a écrit : > Control: tag -1 moreinfo > > On Mon, 30 Aug 2021 12:23:22 + "=?utf-8?q?Bastien_Roucari=C3=A8s?=" > wrote: > > Source: prototypejs > > Severity: serious > > Justification: 4 > > > > Dear Maintainer, > > > > The source is https://github.com/prototypejs/prototype/tree/master and > need > > rake for building... > > > > So FTBFS > > I can rebuild prototypejs/1.7.1-3.1 in sid and bullseye without > problems. What errors do you encounter? > Yes but this not prefered source of modification... > There is a new upstream release 1.7.3 (from 2015) available on github. > Does that version fail? > > And how is this related to rake? > Sée thé salsa tree un order to understand why i need rake > > > Andreas >
Bug#1000157: pampi FTBFS: pyuic5: No such file or directory
Source: pampi Version: 1.1+dfsg1-2 Severity: serious Tags: ftbfs https://buildd.debian.org/status/fetch.php?pkg=pampi=all=1.1%2Bdfsg1-2=1637082767=0 ... make[3]: Entering directory '/<>/pampi/libs' pyuic5 main.ui -o ui_main.py make[3]: pyuic5: No such file or directory make[3]: *** [Makefile:11: ui_main.py] Error 127
Bug#998156: contains non-DFSG-free files
On Thu, Nov 18, 2021 at 12:44:21PM -0600, Henry Cejtin wrote: > Has there ben any progress on getting MLton packaged for Debian? Yes. The sticking point is that mlton requires itself or smlnj to compile itself. The current version of mlton in the archives has been uninstallable for years, so I've been trying to use smlnj to bootstrap mlton. This has required some changes to the source and it's still not completely there. > Is there anything I can do to help? The right path forward is probably for me to file an issue against the Github mlton project, and then we can discuss fixing the smlnj-to-bootstrap-mlton issues there. Ryan -- |)|/ Ryan Kavanagh | 4E46 9519 ED67 7734 268F |\|\ https://rak.ac | BD95 8F7B F8FC 4A11 C97A signature.asc Description: PGP signature
Bug#998156: contains non-DFSG-free files
Has there ben any progress on getting MLton packaged for Debian? Is there anything I can do to help? I haven't seen anything since Matthew Fluet's response. On Sat, Oct 30, 2021 at 10:39 PM Ryan Kavanagh wrote: > > Package: mlton > Version: 20100608-5.1 > Severity: serious > Tags: upstream > X-Debbugs-Cc: r...@debian.org > > Since at least oldoldoldstable, the mlton sources have included non-free > files. > In particular, the tarball lib/ckit-lib/ckit.tgz contains the files > ckit/src/parser/util/error.sml and ckit/src/parser/util/error-sig.sml. These > files are: > > (* > * Copyright (c) 1996 by Satish Chandra, Brad Richards, Mark D. Hill, > * James R. Larus, and David A. Wood. > * > * Teapot is distributed under the following conditions: > * > * You may make copies of Teapot for your own use and modify those copies. > * > * All copies of Teapot must retain our names and copyright notice. > * > * You may not sell Teapot or distributed Teapot in conjunction with a > * commercial product or service without the expressed written consent of > * the copyright holders. > * > * THIS SOFTWARE IS PROVIDED ``AS IS'' AND WITHOUT ANY EXPRESS OR IMPLIED > * WARRANTIES, INCLUDING, WITHOUT LIMITATION, THE IMPLIED WARRANTIES OF > * MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. > * > *) > > The restriction on distribution in conjunction with a commercial product > or service is in violation of point 6 of the DFSG. > > See also the related bug against SML/NJ: > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=998154 > > -- System Information: > Debian Release: bookworm/sid > APT prefers unstable-debug > APT policy: (500, 'unstable-debug'), (500, 'unstable'), (1, > 'experimental-debug'), (1, 'experimental') > Architecture: amd64 (x86_64) > Foreign Architectures: i386 > > Kernel: Linux 5.14.0-1-amd64 (SMP w/4 CPU threads) > Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, > TAINT_UNSIGNED_MODULE > Locale: LANG=en_CA.UTF-8, LC_CTYPE=en_CA.UTF-8 (charmap=UTF-8), LANGUAGE not > set > Shell: /bin/sh linked to /bin/dash > Init: systemd (via /run/systemd/system) > LSM: AppArmor: enabled > > Versions of packages mlton depends on: > ii mlton-compiler 20130715-3 > ii mlton-doc 20130715-3 > ii mlton-tools 20130715-3 > > mlton recommends no packages. > > mlton suggests no packages. > > -- no debconf information > > -- > |)|/ Ryan Kavanagh | 4E46 9519 ED67 7734 268F > |\|\ https://rak.ac | BD95 8F7B F8FC 4A11 C97A
Bug#999348: marked as done (gtk-d: FTBFS with ldc 1.28.0)
Your message dated Thu, 18 Nov 2021 18:33:41 + with message-id and subject line Bug#999348: fixed in gtk-d 3.10.0-1 has caused the Debian Bug report #999348, regarding gtk-d: FTBFS with ldc 1.28.0 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.) -- 999348: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=999348 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: gtk-d Version: 3.9.0-4 Severity: serious Tags: ftbfs sid bookworm Justification: fails to build from source (but built successfully in the past) | ldc2 -O -g -release -wi -Igenerated/gtkd -Idemos/gtkD/TestWindow -c demos/gtkD/TestWindow/TestText.d -ofdemos/gtkD/TestWindow/TestText.o | demos/gtkD/TestWindow/TestWindow.d(207): Error: import `TestWindow.TestEntries` is used as a type | demos/gtkD/TestWindow/TestWindow.d(212): Error: import `TestWindow.TestStock` is used as a type | demos/gtkD/TestWindow/TestWindow.d(219): Error: import `TestWindow.TestScales` is used as a type | demos/gtkD/TestWindow/TestWindow.d(222): Error: import `TestWindow.TestTreeView` is used as a type | demos/gtkD/TestWindow/TestWindow.d(228): Error: import `TestWindow.TestDrawingArea` is used as a type | demos/gtkD/TestWindow/TestWindow.d(229): Error: import `TestWindow.TestText` is used as a type | demos/gtkD/TestWindow/TestWindow.d(230): Error: import `TestWindow.TestImage` is used as a type | demos/gtkD/TestWindow/TestWindow.d(233): Error: import `TestWindow.TestAspectFrame` is used as a type | demos/gtkD/TestWindow/TestWindow.d(234): Error: import `TestWindow.TestIdle` is used as a type | demos/gtkD/TestWindow/TestWindow.d(949): Error: import `TestWindow.TTextView` is used as a type | make[2]: *** [GNUmakefile:257: demos/gtkD/TestWindow/TestWindow.o] Error 1 https://buildd.debian.org/status/fetch.php?pkg=gtk-d=amd64=3.9.0-4%2Bb1=1636493509=0 Cheers -- Sebastian Ramacher --- End Message --- --- Begin Message --- Source: gtk-d Source-Version: 3.10.0-1 Done: Matthias Klumpp We believe that the bug you reported is fixed in the latest version of gtk-d, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 999...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Matthias Klumpp (supplier of updated gtk-d package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Thu, 18 Nov 2021 19:08:10 +0100 Source: gtk-d Architecture: source Version: 3.10.0-1 Distribution: unstable Urgency: medium Maintainer: Debian GNOME Maintainers Changed-By: Matthias Klumpp Closes: 999348 Changes: gtk-d (3.10.0-1) unstable; urgency=medium . * New upstream release - Fixes build with newer D compiler releases (Closes: #999348) * Drop all patches that were applied upstream * Bump standards version: No changes needed Checksums-Sha1: e00588a377a2cd85ec1b3efc02462eb6d3f6d4a7 2669 gtk-d_3.10.0-1.dsc a36ede2cc228aed83393e3e8415edfba9840f9db 3214521 gtk-d_3.10.0.orig.tar.gz aa4f1bb0a5e4e030f58d9bf48d74594cae47547c 5608 gtk-d_3.10.0-1.debian.tar.xz e0eccfda7e9921a5478976ed8cdb8c199d6f1639 15631 gtk-d_3.10.0-1_source.buildinfo Checksums-Sha256: 3792661d9f8dfc4fdda7a1fca3eff3869b95bc52160f79e348bc92e847215a0c 2669 gtk-d_3.10.0-1.dsc 5c6edcdcfb6160ffc1524ab4996471e608c3632d81bd8ea689cf0e52ed13e953 3214521 gtk-d_3.10.0.orig.tar.gz d8b5441f0d9aa1ea7362538dde90d4dc039bc14e0128f6949b07ac24d15c1769 5608 gtk-d_3.10.0-1.debian.tar.xz 1f1bbfc8f515fdbaa8983df5d54799ed8a21d45428e53aa9352aa67cead10e74 15631 gtk-d_3.10.0-1_source.buildinfo Files: 7ec2c50f9719aeb5a1dc2de614dd1eb4 2669 libs optional gtk-d_3.10.0-1.dsc ead4d778b9689e61e0443253f90f97d8 3214521 libs optional gtk-d_3.10.0.orig.tar.gz a046856712d3157600ec8dffc38956c2 5608 libs optional gtk-d_3.10.0-1.debian.tar.xz 44162326f916cd56d23de37e55951e68 15631 libs optional gtk-d_3.10.0-1_source.buildinfo -BEGIN PGP SIGNATURE- iQJDBAEBCAAtFiEE0zo/DKFrCsxRpgc4SUyKX79N7OsFAmGWmPoPHG1ha0BkZWJp YW4ub3JnAAoJEElMil+/TezroFUQAJLFRtJ1EUtRMqFSzG5D1D7qKD50b/BX++xB 02vM8HQanaggvuvf7B+YRzu/hSqcTt+vgKgSB1qYrMHoTMyZZXHQh94fr9vcnycy t3DSMCB1bi99St+yoYr2EsZxyCipdZ3iIKxsQlsKrCrx7I8/+FzZE4GqEHOw3R2G
Processed: [bts-link] source package redmine
Processing commands for cont...@bugs.debian.org: > # > # bts-link upstream status pull for source package redmine > # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html > # https://bts-link-team.pages.debian.net/bts-link/ > # > user debian-bts-l...@lists.debian.org Setting user to debian-bts-l...@lists.debian.org (was debian-bts-l...@lists.debian.org). > # remote status report for #969206 (http://bugs.debian.org/969206) > # Bug title: redmine: Could not find gem 'rails (~> 5.2.2)' in any of the gem > sources listed in your Gemfile > # * http://www.redmine.org/issues/29914 > # * remote status changed: New -> Closed > # * closed upstream > tags 969206 + fixed-upstream Bug #969206 [redmine] redmine: Could not find gem 'rails (~> 5.2.2)' in any of the gem sources listed in your Gemfile Added tag(s) fixed-upstream. > usertags 969206 - status-New Usertags were: status-New. There are now no usertags set. > usertags 969206 + status-Closed There were no usertags set. Usertags are now: status-Closed. > thanks Stopping processing here. Please contact me if you need assistance. -- 969206: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=969206 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Re: Bug#1000140: Acknowledgement (ruby-moneta: FTBFS: mysqld fails to start)
Processing control commands: > retitle -1 ruby-moneta: FTBFS: mysqld fails to start on tmpfs Bug #1000140 [src:ruby-moneta] ruby-moneta: FTBFS: mysqld fails to start Changed Bug title to 'ruby-moneta: FTBFS: mysqld fails to start on tmpfs' from 'ruby-moneta: FTBFS: mysqld fails to start'. > severity -1 important Bug #1000140 [src:ruby-moneta] ruby-moneta: FTBFS: mysqld fails to start on tmpfs Severity set to 'important' from 'serious' -- 1000140: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1000140 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1000140: Acknowledgement (ruby-moneta: FTBFS: mysqld fails to start)
Control: retitle -1 ruby-moneta: FTBFS: mysqld fails to start on tmpfs Control: severity -1 important I perceived that this is triggered by my sbuild/schroot setup building packages with a tmpfs overlay (union-overlay-directory=/dev/shm), so this does not happen always. I'm thus downgrading the severity of this bug. signature.asc Description: PGP signature
Bug#999364: marked as done (libseccomp ftbfs with Python 3.10)
Your message dated Thu, 18 Nov 2021 17:05:05 + with message-id and subject line Bug#999364: fixed in libseccomp 2.5.3-2 has caused the Debian Bug report #999364, regarding libseccomp ftbfs with Python 3.10 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 999364: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=999364 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: libseccomp Version: 2.5.2-2 Severity: important Tags: ftbfs User: debian-pyt...@lists.debian.org Usertags: python3.10 libseccomp ftbfs with python3-defaults from experimental: a very bad version check in debian/rules ... if python3 -c "pyver='$$pyver'; exit(0 if float(pyver[6:]) >= 3.8 else 1)"; then --- End Message --- --- Begin Message --- Source: libseccomp Source-Version: 2.5.3-2 Done: Felix Geyer We believe that the bug you reported is fixed in the latest version of libseccomp, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 999...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Felix Geyer (supplier of updated libseccomp 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: Thu, 18 Nov 2021 17:52:23 +0100 Source: libseccomp Architecture: source Version: 2.5.3-2 Distribution: unstable Urgency: medium Maintainer: Kees Cook Changed-By: Felix Geyer Closes: 999364 Changes: libseccomp (2.5.3-2) unstable; urgency=medium . [ Alex Murray ] * Fix python version check in debian/rules to properly handle python3.10 to resolve FTBFS (Closes: #999364) . libseccomp (2.5.3-1) experimental; urgency=medium . * New upstream release. * Drop patches from 2.5.2-2, fixed upstream. Checksums-Sha1: 21d32e411ed2d097d6773bd062e456674b50efde 2676 libseccomp_2.5.3-2.dsc 45d367cfc6a62cb5787cb45af556186f3dd59f10 16268 libseccomp_2.5.3-2.debian.tar.xz Checksums-Sha256: d6325664ec9ff84e6b9787b78e0a431424c414217a6dd0f4098ea32df53db26f 2676 libseccomp_2.5.3-2.dsc b0e094e78c3e4f2c94288c1543dd879dabac7d11a22b7e0fb685d7560a1d24ba 16268 libseccomp_2.5.3-2.debian.tar.xz Files: 9a4ca3e58bed62ea857bae91bbfffedc 2676 libs optional libseccomp_2.5.3-2.dsc 14cefd7e6f77ca7a9b9b5137aaac47b6 16268 libs optional libseccomp_2.5.3-2.debian.tar.xz -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEFkxwUS95KUdnZKtW/iLG/YMTXUUFAmGWhYYACgkQ/iLG/YMT XUWxbA/7B/aCuiNcxIQ74CEcWp9dSok64t0u0xh0RE/wSOeyTC0CG2VM8/lXo+9x LPvVk0NERIPRVjInxNAPKxSQn/4Sm5IduuqD4LZAofUIeQ84yp2zJ8X0AyXxnN2i YXEJU5EYLMMy5V21DTgUxqzVT3356rfgQgY/yTSTuAgQAuY7YeoBilw/afRSeZ+7 geFpsL3BK3KHF88xPiHli4d1+bQvoIVGat9z6xO46yNIzBu5IGDpa6MTJBxVvAAM zVm+g2zDYtkWRrEtCigANm338vQg9FHhipYDCLsoO8Afoc4HtIHGJniMIosLdlB3 kqN4IOq0tPdK9EDwmGH3bk0xBB368eAgDK9UgdjKxW+LDBDbR7r0AiHKuyaCFJX2 D0MHhKdxSOrHBQAdkSjc5OgSfFqFcxtnASUtJMe+E/j6PX3BzVPWPA5+U2joZbm+ ljRzZO7wFLdqZd4t3wzxQ9SupMxo0+NBV5peNqOiGa8XHS1cTamwlV6PfKyTkMVR LuAIuwL5WHofdhSsg3MjTWZ/XHdCCWH0QwpNs8W2+LoZ8M5V2iqmpCfghFT3Ohxs QMpBu1EjzwhI9jxls/NYCA0BeT+jB1Ce4CrxHvpcoxrLrGiThFbE5TuHbADTxCy9 dT1+JOC3jdvJ4n1f/DF/GI8WIkkVIw7mNIe3l1drJ66hwKdnPRI= =qH5h -END PGP SIGNATURE End Message ---
Bug#999815: marked as done (cryptsetup - build-depends on removed package.)
Your message dated Thu, 18 Nov 2021 16:48:38 + with message-id and subject line Bug#999815: fixed in cryptsetup 2:2.4.2-1 has caused the Debian Bug report #999815, regarding cryptsetup - build-depends on removed package. to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 999815: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=999815 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: cryptsetup Version: 2:2.4.1-1 Severity: serious cryptsetup build-depends on libsepol1-dev which is no longer built by the libsepol source package. The package is completely gone from testing, in unstable it is still present as a cruft package, but is not usable for building cryptsetup because the current version of libselinux1-dev conflicts with it. I suspect (but have not tested) that you need to change your build-dependency to libsepol-dev. --- End Message --- --- Begin Message --- Source: cryptsetup Source-Version: 2:2.4.2-1 Done: Guilhem Moulin We believe that the bug you reported is fixed in the latest version of cryptsetup, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 999...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Guilhem Moulin (supplier of updated cryptsetup 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: Thu, 18 Nov 2021 17:15:08 +0100 Source: cryptsetup Architecture: source Version: 2:2.4.2-1 Distribution: unstable Urgency: high Maintainer: Debian Cryptsetup Team Changed-By: Guilhem Moulin Closes: 999815 Changes: cryptsetup (2:2.4.2-1) unstable; urgency=high . * New upstream bugfix release 2.4.2. * d/control: Replace Build-Depends on removed package libsepol1-dev with libsepol-dev. (Closes: #999815) * blkid/un_blkid checks: Ignore large offsets when converting from sectors to bytes. * crypttab(5): Formatting fix. * Refresh d/copyright. * Refresh lintian overrides to accommodate lintian v2.112. Checksums-Sha1: 4f540d245b7b4a83a01bdb7ccfb683da7d9ef5f1 3008 cryptsetup_2.4.2-1.dsc 64ff62ca61945b4977854245208e2ddea5491cb6 11327591 cryptsetup_2.4.2.orig.tar.gz a05d8ef8bbf2135c6ba581f5046be65ab8dbde1b 127576 cryptsetup_2.4.2-1.debian.tar.xz 391aa3cf3922953806d947b2c4a3a98ac285e2e0 10324 cryptsetup_2.4.2-1_amd64.buildinfo Checksums-Sha256: 6aeee48de3a4e67ecf485051fc6368a01f498defba21d8f314fa439e07b6a229 3008 cryptsetup_2.4.2-1.dsc 4b023868af0a8fd155ba5705ee289489e4ac79808df4d76db82fccb725e43275 11327591 cryptsetup_2.4.2.orig.tar.gz 5db8a1f3c27fa67468671158a3c667d7d3f61c191181b013b065021db892fda1 127576 cryptsetup_2.4.2-1.debian.tar.xz c30ee6d1b14bbeebb0968dd511876710e656c89ca7fecac504106f0e938d3afb 10324 cryptsetup_2.4.2-1_amd64.buildinfo Files: 41df88a6f08d8a3e63023452f4ca497c 3008 admin optional cryptsetup_2.4.2-1.dsc a38f3fbd289b570864e52ba59acb2152 11327591 admin optional cryptsetup_2.4.2.orig.tar.gz 1cafa25b8de9c01cb51a45e0cd57d88a 127576 admin optional cryptsetup_2.4.2-1.debian.tar.xz 7d981fcd195bc69a97069538399461e4 10324 admin optional cryptsetup_2.4.2-1_amd64.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEERpy6p3b9sfzUdbME05pJnDwhpVIFAmGWfSwACgkQ05pJnDwh pVIFgw//TcGBeWQWKdDHIOUCAcCI3JZzqBNg8M+0x3wqmCH8/7iNeY091wseCVdf p5JwE/z8JnhYYkNPrm1qcj8S036XNSaC+CSwakfLQ9Co/KYTGEUKEMNMWHbt8EXG gV3i/9cFp3WM2gCeKTbCFsvU/sutxWKpOfx5DtobwSlStS2U46rl7JX/p4FuIuZY e3Pwwah1oUrKE0gYnJHWZg6Xh9sFqHHogaAs7f1s9eygvg7t9noYya/++tlRXwMU EclerPqtolf9kiBuYUYDu2CXRddEeeUmVvL4MGbPcjKkgx9CkALTGQ4NKv0IXXOc MWvWcC+d4u/Wx+ZLh9CgqV9/S1xZ4QWVkpNIneLzG8QtFAJEoarsrso/rbNi8dAv oqCr3iDUj7tV3lAMR9rxuZnXTsdrVFW/PWxDNy/rg1PZBA0r4gaS8QCTjQy6FUBV ZyeW5aCoqQvSX2lYCc0cAZhJe2KhmE7McZ2ZtqwwlvfGkLCXA9ILScxGoARkKHJv EqkD1zGE6Q2KrrgfFTTACOnZYd7tj1GtQkMl/2AHkXkotFM8Faesx/7ZKn8An5Ue BV64b8kMx4bw/UEcdx4dUPPdzmfLoJB4BiW1576hwc7+r6+z6u9/7SyEbsMRqC8W EM28TivIq/SJsKy4rpg7iIwmw1Ap+qJ8oa0DxgYsvPLXTDqG//Q= =E45e -END PGP SIGNATURE End Message ---
Bug#993196: Stackpath
Hi, We have a list of Stackpath users with complete contacts if interested let me know so that we can send you count, cost and more info of deliver of data GD-PR etc.. Regards, Elena Williams
Processed: tagging 999398
Processing commands for cont...@bugs.debian.org: > tags 999398 + bookworm sid Bug #999398 [src:zodbpickle] zodbpickle ftbfs with Python 3.10 (test failures) Added tag(s) bookworm and sid. > thanks Stopping processing here. Please contact me if you need assistance. -- 999398: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=999398 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: severity of 999398 is serious
Processing commands for cont...@bugs.debian.org: > severity 999398 serious Bug #999398 [src:zodbpickle] zodbpickle ftbfs with Python 3.10 (test failures) Severity set to 'serious' from 'important' > thanks Stopping processing here. Please contact me if you need assistance. -- 999398: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=999398 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: severity of 999395 is serious
Processing commands for cont...@bugs.debian.org: > severity 999395 serious Bug #999395 [src:python-zstd] python-zstd ftbfs with Python 3.10 (test failures) Severity set to 'serious' from 'important' > thanks Stopping processing here. Please contact me if you need assistance. -- 999395: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=999395 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: tagging 999385
Processing commands for cont...@bugs.debian.org: > tags 999385 + bookworm sid Bug #999385 [src:python-pyalsa] python-pyalsa ftbfs with Python 3.10 Added tag(s) bookworm and sid. > thanks Stopping processing here. Please contact me if you need assistance. -- 999385: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=999385 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: severity of 999385 is serious
Processing commands for cont...@bugs.debian.org: > severity 999385 serious Bug #999385 [src:python-pyalsa] python-pyalsa ftbfs with Python 3.10 Severity set to 'serious' from 'important' > thanks Stopping processing here. Please contact me if you need assistance. -- 999385: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=999385 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: tagging 999380
Processing commands for cont...@bugs.debian.org: > tags 999380 + bookworm sid Bug #999380 [src:python-lzo] python-lzo ftbfs with Python 3.10 (test failures) Added tag(s) bookworm and sid. > thanks Stopping processing here. Please contact me if you need assistance. -- 999380: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=999380 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: severity of 999380 is serious
Processing commands for cont...@bugs.debian.org: > severity 999380 serious Bug #999380 [src:python-lzo] python-lzo ftbfs with Python 3.10 (test failures) Severity set to 'serious' from 'important' > thanks Stopping processing here. Please contact me if you need assistance. -- 999380: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=999380 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: severity of 999373 is serious
Processing commands for cont...@bugs.debian.org: > severity 999373 serious Bug #999373 [src:python-dmidecode] python-dmidcode ftbfs with Python 3.10 (test failures) Severity set to 'serious' from 'important' > thanks Stopping processing here. Please contact me if you need assistance. -- 999373: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=999373 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: tagging 999370
Processing commands for cont...@bugs.debian.org: > tags 999370 + bookworm sid Bug #999370 [src:pystemd] pystemd ftbfs with Python 3.10 Added tag(s) sid and bookworm. > thanks Stopping processing here. Please contact me if you need assistance. -- 999370: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=999370 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: severity of 999367 is serious
Processing commands for cont...@bugs.debian.org: > severity 999367 serious Bug #999367 [src:py-postgresql] py-postgresql ftbfs with Python 3.10 (test failures) Severity set to 'serious' from 'important' > thanks Stopping processing here. Please contact me if you need assistance. -- 999367: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=999367 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: severity of 999370 is serious
Processing commands for cont...@bugs.debian.org: > severity 999370 serious Bug #999370 [src:pystemd] pystemd ftbfs with Python 3.10 Severity set to 'serious' from 'important' > thanks Stopping processing here. Please contact me if you need assistance. -- 999370: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=999370 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: severity of 999364 is serious
Processing commands for cont...@bugs.debian.org: > severity 999364 serious Bug #999364 [src:libseccomp] libseccomp ftbfs with Python 3.10 Severity set to 'serious' from 'important' > thanks Stopping processing here. Please contact me if you need assistance. -- 999364: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=999364 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: severity of 999374 is serious
Processing commands for cont...@bugs.debian.org: > severity 999374 serious Bug #999374 [src:python-gammu] python-gammu ftbfs with Python 3.10 (test failures) Severity set to 'serious' from 'important' > thanks Stopping processing here. Please contact me if you need assistance. -- 999374: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=999374 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: tagging 999376
Processing commands for cont...@bugs.debian.org: > tags 999376 + bookworm sid Bug #999376 [src:python-gmpy2] python-gmpy2 ftbfs with Python 3.10 Added tag(s) sid and bookworm. > thanks Stopping processing here. Please contact me if you need assistance. -- 999376: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=999376 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: severity of 999376 is serious
Processing commands for cont...@bugs.debian.org: > severity 999376 serious Bug #999376 [src:python-gmpy2] python-gmpy2 ftbfs with Python 3.10 Severity set to 'serious' from 'important' > thanks Stopping processing here. Please contact me if you need assistance. -- 999376: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=999376 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#999751: marked as done (di-netboot-assistant: please drop shellcheck autopkgtest)
Your message dated Thu, 18 Nov 2021 16:03:30 +
with message-id
and subject line Bug#999751: fixed in di-netboot-assistant 0.72
has caused the Debian Bug report #999751,
regarding di-netboot-assistant: please drop shellcheck 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.)
--
999751: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=999751
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: di-netboot-assistant
Version: 0.71
Severity: serious
X-Debbugs-CC: debian...@lists.debian.org, shellch...@packages.debian.org
Tags: sid bookworm
User: debian...@lists.debian.org
Usertags: needs-update
Control: affects -1 src:shellcheck
Dear maintainer(s),
With a recent upload of shellcheck the autopkgtest of di-netboot-assistant
fails in testing when that autopkgtest is run with the binary packages
of shellcheck from unstable. It passes when run with only packages from
testing. In tabular form:
passfail
shellcheck from testing0.8.0-2
di-netboot-assistantfrom testing0.71
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 shellcheck to
testing [1]. Of course, shellcheck shouldn't just break your autopkgtest
(or even worse, your package), but in this case shellcheck just evolved.
Static analysis tools are intended to run on source code, while
autopkgtest is intended to run against installed packages, where source
code is in principle not relevant; we want to know whether the binary
packages, as provided in the Debian archive, work correctly. In our
opinion running this type of tools as integration tests in autopkgtest,
or even as build-time tests is Wrong™, and should not be done. (Having
them run in salsaci or equivalent is of course totally great.)
More information about this bug and the reason for filing it can be found on
https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation
[1] https://qa.debian.org/excuses.php?package=shellcheck
https://ci.debian.net/data/autopkgtest/testing/amd64/d/di-netboot-assistant/16684224/log.gz
autopkgtest [03:27:30]: test command1: shellcheck -x
/usr/bin/di-netboot-assistant ; shellcheck -x -s dash
/var/lib/dpkg/info/di-netboot-assistant.post*
/var/lib/dpkg/info/di-netboot-assistant.pre*
autopkgtest [03:27:30]: test command1: [---
In /usr/bin/di-netboot-assistant line 452:
echo -e "MENU BACKGROUND ::${s#$TFTP_ROOT}\n" >> pxelinux.cfg/default
^^ SC2295 (info):
Expansions inside ${..} need to be quoted separately, otherwise they
match as patterns.
Did you mean:
echo -e "MENU BACKGROUND ::${s#"$TFTP_ROOT"}\n" >> pxelinux.cfg/default
For more information:
https://www.shellcheck.net/wiki/SC2295 -- Expansions inside ${..} need to b...
autopkgtest [03:27:32]: test command1: ---]
autopkgtest [03:27:32]: test command1: - - - - - - - - - - results -
- - - - - - - - -
command1 FAIL non-zero exit status 1
I took the liberty to base the body of this email on bugreport
#992798, from Paul Gevers,
--
Samuel Henrique
--- End Message ---
--- Begin Message ---
Source: di-netboot-assistant
Source-Version: 0.72
Done: Andreas B. Mundt
We believe that the bug you reported is fixed in the latest version of
di-netboot-assistant, which is due to be installed in the Debian FTP archive.
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to 999...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Andreas B. Mundt (supplier of updated di-netboot-assistant
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: Thu, 18 Nov 2021 16:27:29 +0100
Source: di-netboot-assistant
Architecture: source
Version: 0.72
Distribution: unstable
Urgency: medium
Maintainer: Debian Install System Team
Changed-By: Andreas B. Mundt
Closes: 999751
Changes:
di-netboot-assistant (0.72) unstable; urgency=medium
.
* Add ARM64 and link EFI and grub files from the latest image installed.
* Update sources, supported releases and architectures.
*
Bug#1000146: cppcheck: incorrect dependencies: libc6 should be >= 2.32
Package: cppcheck Version: 2.6-1 Severity: grave Justification: renders package unusable X-Debbugs-Cc: colomar.6@gmail.com Dear Maintainer, I installed and run cppcheck on a system which I had not used for half a year. For that reason, many of its packages were outdated. glibc was on version 2.31. When I run cppcheck, it failed with the following error: cppcheck: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.32' not found (required by cppcheck) I found the following dependencies' information: $ apt-rdepends cppcheck | head -n2 Reading package lists... Done Building dependency tree... Done Reading state information... Done cppcheck Depends: libc6 (>= 2.29) So it clearly is incorrect, AFAICS. It should declare a dependency for libc6 2.32 Regards, Alex P.S.: You'll find below that my installed libc6 is 2.32; that's because I updated it to be able to use checkpatch, prior to sending this bug report. Please ignore that. -- System Information: Debian Release: bookworm/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 5.10.0-7-amd64 (SMP w/4 CPU threads) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages cppcheck depends on: ii libc6 2.32-4 ii libgcc-s1 11.2.0-10 ii libpcre3 2:8.39-13 ii libstdc++611.2.0-10 ii libtinyxml2-9 9.0.0+dfsg-3 ii libz3-4 4.8.12-1+b1 iu python3 3.9.8-1 ii python3-pygments 2.7.1+dfsg-2.1 cppcheck recommends no packages. Versions of packages cppcheck suggests: ii clang 1:11.0-51+nmu5 ii clang-tidy1:11.0-51+nmu5 pn cppcheck-gui -- no debconf information
Processed: bug 995779 is forwarded to https://gitlab.com/mailman/mailman/-/issues/845
Processing commands for cont...@bugs.debian.org: > forwarded 995779 https://gitlab.com/mailman/mailman/-/issues/845 Bug #995779 [mailman3] autopkgtest fails with sqlalchemy 1.4.23+ds1 Set Bug forwarded-to-address to 'https://gitlab.com/mailman/mailman/-/issues/845'. > thanks Stopping processing here. Please contact me if you need assistance. -- 995779: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=995779 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: bug 1000138 is forwarded to https://savannah.gnu.org/bugs/?61504
Processing commands for cont...@bugs.debian.org: > forwarded 1000138 https://savannah.gnu.org/bugs/?61504 Bug #1000138 [screen] /usr/bin/screen: command arguments beyond 62 silently discarded Set Bug forwarded-to-address to 'https://savannah.gnu.org/bugs/?61504'. > thanks Stopping processing here. Please contact me if you need assistance. -- 1000138: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1000138 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1000140: ruby-moneta: FTBFS: mysqld fails to start
Source: ruby-moneta Version: 1.0.0-9 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs X-Debbugs-CC: debian-r...@lists.debian.org Hi, ruby-moneta fails to build from source. This is a recurring problem. We have a ton of scritps to start mysql for running tests, they are all slightly different, and they all break from time to time. :-/ Relevant part (hopefully): > /usr/bin/ruby2.7 /usr/bin/gem2deb-test-runner > > ┌──┐ > │ Run tests for ruby2.7 from debian/ruby-tests.rb > │ > └──┘ > > RUBYLIB=/<>/debian/ruby-moneta/usr/lib/ruby/vendor_ruby:. > GEM_PATH=/<>/debian/ruby-moneta/usr/share/rubygems-integration/all:/var/lib/gems/2.7.0:/usr/local/lib/ruby/gems/2.7.0:/usr/lib/ruby/gems/2.7.0:/usr/lib/x86_64-linux-gnu/ruby/gems/2.7.0:/usr/share/rubygems-integration/2.7.0:/usr/share/rubygems-integration/all:/usr/lib/x86_64-linux-gnu/rubygems-integration/2.7.0 > ruby2.7 debian/ruby-tests.rb > 2021-11-18 14:48:53 0 [Warning] InnoDB: Retry attempts for writing partial > data failed. > 2021-11-18 14:48:53 0 [ERROR] InnoDB: Write to file ./ibdata1 failed at > offset 0, 1048576 bytes should have been written, only 0 were written. > Operating system error number 22. Check that your OS and file system support > files of this size. Check also that the disk is not full or a disk quota > exceeded. > 2021-11-18 14:48:53 0 [ERROR] InnoDB: Error number 22 means 'Invalid argument' > 2021-11-18 14:48:53 0 [ERROR] InnoDB: Could not set the file size of > './ibdata1'. Probably out of disk space > 2021-11-18 14:48:53 0 [ERROR] InnoDB: Database creation was aborted with > error Generic error. You may need to delete the ibdata1 file before trying to > start up again. > 2021-11-18 14:48:53 0 [ERROR] InnoDB: Operating system error number 22 in a > file operation. > 2021-11-18 14:48:53 0 [ERROR] InnoDB: Error number 22 means 'Invalid argument' > 2021-11-18 14:48:53 0 [ERROR] InnoDB: File (unknown): 'close' returned OS > error 222. Cannot continue operation > 28 14:48:53 [ERROR] mysqld got signal 6 ; > This could be because you hit a bug. It is also possible that this binary > or one of the libraries it was linked against is corrupt, improperly built, > or misconfigured. This error can also be caused by malfunctioning hardware. > > To report this bug, see https://mariadb.com/kb/en/reporting-bugs > > We will try our best to scrape up some info that will hopefully help > diagnose the problem, but since we have already crashed, > something is definitely wrong and this may fail. > > Server version: 10.6.4-MariaDB-1+b1 > key_buffer_size=134217728 > read_buffer_size=131072 > max_used_connections=0 > max_threads=153 > thread_count=0 > It is possible that mysqld could use up to > key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 467956 > K bytes of memory > Hope that's ok; if not, decrease some variables in the equation. > > Thread pointer: 0x0 > Attempting backtrace. You can use the following information to find out > where mysqld died. If you see no messages after this, something went > terribly wrong... > stack_bottom = 0x0 thread_stack 0x49000 > ??:0(my_print_stacktrace)[0x55f65c52e8fe] > ??:0(handle_fatal_signal)[0x55f65c07d2f8] > ??:0(__restore_rt)[0x7ffa991ac8e0] > ??:0(gsignal)[0x7ffa98cb7e71] > ??:0(abort)[0x7ffa98ca1536] > ??:0(Wsrep_server_service::log_dummy_write_set(wsrep::client_state&, > wsrep::ws_meta const&))[0x55f65bd31214] > ??:0(std::unique_lock::unlock())[0x55f65c38bc05] > ??:0(void std::vector > >::_M_realloc_insert(__gnu_cxx::__normal_iterator long*, std::vector > >, unsigned > long&&))[0x55f65c499e68] > ??:0(void std::vector > >::_M_realloc_insert(__gnu_cxx::__normal_iterator long*, std::vector > >, unsigned > long&&))[0x55f65c499ed1] > ??:0(void std::vector > >::_M_realloc_insert(__gnu_cxx::__normal_iterator long*, std::vector > >, unsigned > long&&))[0x55f65c49c530] > ??:0(void std::vector > >::_M_realloc_insert(__gnu_cxx::__normal_iterator long*, std::vector > >, unsigned > long&&))[0x55f65c49d651] > ??:0(void std::this_thread::sleep_for > >(std::chrono::duration > const&))[0x55f65c3fa717] > ??:0(wsrep_notify_status(wsrep::server_state::state, wsrep::view > const*))[0x55f65c33aa95] > ??:0(ha_initialize_handlerton(st_plugin_int*))[0x55f65c08042e] > ??:0(sys_var_pluginvar::sys_var_pluginvar(sys_var_chain*, char const*, > st_plugin_int*, st_mysql_sys_var*))[0x55f65be7ae06] > ??:0(plugin_init(int*, char**, int))[0x55f65be7bdc8] > ??:0(unireg_abort)[0x55f65bda783a] > ??:0(mysqld_main(int, char**))[0x55f65bdad3b2] > ??:0(__libc_start_main)[0x7ffa98ca2e4a] > ??:0(_start)[0x55f65bda29ca] > The manual page at > https://mariadb.com/kb/en/how-to-produce-a-full-stack-trace-for-mysqld/ > contains > information that should help you find out what is causing the crash. > Writing a
Processed: Re: Bug#1000138: command arguments beyond 62 silently discarded
Processing control commands: > tags -1 + patch Bug #1000138 [screen] /usr/bin/screen: command arguments beyond 62 silently discarded Added tag(s) patch. -- 1000138: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1000138 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1000138: command arguments beyond 62 silently discarded
Control: tags -1 + patch
I grepped for MAXARGS and arranged for screen to crash rather than
silently ignoring arguments. I think this is much better, although it
doesn't fully fix the bug.
Confusingly, the source uses MAXARGS both for the maximum number of
arguments for a shell command, and for the maximum number of numerical
arguments to a terminal escape sequence. I left the latter part
alone: excess terminal escape sequence arguments are still ignored.
Applying this patch wouldn't actually fix the bug but it would IMO
render it of "normal" or "minor" severity.
Ian.
>From c73ab91cc30ac9dbc38df54f5eee47e8676fa453 Mon Sep 17 00:00:00 2001
From: Ian Jackson
Date: Thu, 18 Nov 2021 13:55:19 +
Subject: [PATCH] crash rather than silently dropping arguments
---
attacher.c | 10 +++---
extern.h | 1 +
screen.c | 6 ++
socket.c | 14 +-
4 files changed, 23 insertions(+), 8 deletions(-)
diff --git a/attacher.c b/attacher.c
index 18ba43c..23ed479 100644
--- a/attacher.c
+++ b/attacher.c
@@ -1042,11 +1042,15 @@ int query;
}
p = m.m.command.cmd;
n = 0;
- for (; *av && n < MAXARGS - 1; ++av, ++n)
+ for (; *av; ++av, ++n)
{
+ if (!(n < MAXARGS - 1)) {
+ Crash_due_to_argument_limit();
+ }
len = strlen(*av) + 1;
- if (p + len >= m.m.command.cmd + sizeof(m.m.command.cmd) - 1)
- break;
+ if (p + len >= m.m.command.cmd + sizeof(m.m.command.cmd) - 1) {
+ Crash_due_to_argument_limit();
+ }
strcpy(p, *av);
p += len;
}
diff --git a/extern.h b/extern.h
index 8374ec0..74483d6 100644
--- a/extern.h
+++ b/extern.h
@@ -52,6 +52,7 @@ extern void Panic __P(());
extern void QueryMsg __P(());
extern void Dummy __P(());
#endif
+extern void Crash_due_to_argument_limit __P(());
extern void Finit __P((int));
extern void MakeNewEnv __P((void));
extern char *MakeWinMsg __P((char *, struct win *, int));
diff --git a/screen.c b/screen.c
index 1ab7ae1..c5b9653 100644
--- a/screen.c
+++ b/screen.c
@@ -2169,6 +2169,12 @@ DEFINE_VARARGS_FN(Panic)
eexit(1);
}
+void Crash_due_to_argument_limit()
+{
+ Panic(0, "Argument count or length limit exceeded");
+}
+
+
DEFINE_VARARGS_FN(QueryMsg)
{
char buf[MAXPATHLEN*2];
diff --git a/socket.c b/socket.c
index 01674c1..2a8545f 100644
--- a/socket.c
+++ b/socket.c
@@ -701,11 +701,15 @@ struct NewWindow *nwin;
p = m.m.create.line;
n = 0;
if (nwin->args != nwin_undef.args)
-for (av = nwin->args; *av && n < MAXARGS - 1; ++av, ++n)
+for (av = nwin->args; *av; ++av, ++n)
{
+ if (!(n < MAXARGS - 1)) {
+ Crash_due_to_argument_limit();
+ }
len = strlen(*av) + 1;
-if (p + len >= m.m.create.line + sizeof(m.m.create.line) - 1)
- break;
+if (p + len >= m.m.create.line + sizeof(m.m.create.line) - 1) {
+ Crash_due_to_argument_limit();
+ }
strcpy(p, *av);
p += len;
}
@@ -773,7 +777,7 @@ struct msg *mp;
nwin = nwin_undef;
n = mp->m.create.nargs;
if (n > MAXARGS - 1)
-n = MAXARGS - 1;
+Crash_due_to_argument_limit();
/* ugly hack alert... should be done by the frontend! */
if (n)
{
@@ -1782,7 +1786,7 @@ struct msg *mp;
n = mp->m.command.nargs;
if (n > MAXARGS - 1)
-n = MAXARGS - 1;
+Crash_due_to_argument_limit();
for (fc = fullcmd; n > 0; n--)
{
int len = strlen(p);
--
2.20.1
--
Ian JacksonThese opinions are my own.
Pronouns: they/he. If I emailed you from @fyvzl.net or @evade.org.uk,
that is a private address which bypasses my fierce spamfilter.
Bug#983996: marked as done (blist: ftbfs with GCC-11)
Your message dated Thu, 18 Nov 2021 14:34:16 + with message-id and subject line Bug#983996: fixed in blist 1.3.6-8 has caused the Debian Bug report #983996, regarding blist: ftbfs with GCC-11 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.) -- 983996: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=983996 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:blist Version: 1.3.6-7 Severity: normal Tags: sid bookworm User: debian-...@lists.debian.org Usertags: ftbfs-gcc-11 [This bug is not targeted to the upcoming bullseye release] Please keep this issue open in the bug tracker for the package it was filed for. If a fix in another package is required, please file a bug for the other package (or clone), and add a block in this package. Please keep the issue open until the package can be built in a follow-up test rebuild. The package fails to build in a test rebuild on at least amd64 with gcc-11/g++-11, but succeeds to build with gcc-10/g++-10. The severity of this report will be raised before the bookworm release, so nothing has to be done for the bullseye release. The full build log can be found at: http://people.debian.org/~doko/logs/20210228/filtered/gcc11/blist_1.3.6-7_unstable_gcc11.log The last lines of the build log are at the end of this report. To build with GCC 11, either set CC=gcc-11 CXX=g++-11 explicitly, or install the gcc, g++, gfortran, ... packages from experimental. apt-get -t=experimental install g++ Common build failures are new warnings resulting in build failures with -Werror turned on, or new/dropped symbols in Debian symbols files. For other C/C++ related build failures see the porting guide at http://gcc.gnu.org/gcc-11/porting_to.html GCC 11 defaults to the GNU++17 standard. If your package installs header files in /usr/include, please don't work around C++17 issues by choosing a lower C++ standard for the package build, but fix these issues to build with the C++17 standard. [...] blist/_blist.c:2759:20: warning: ‘p’ may be used uninitialized [-Wmaybe-uninitialized] 2759 | return _ob(blist_get1(p, i - so_far)); |^ blist/_blist.c:1061:19: note: in definition of macro ‘_ob’ 1061 | #define _ob(ret) (ret) | ^~~ blist/_blist.c: In function ‘py_blist_repr’: blist/_blist.c:2748:18: note: ‘p’ declared here 2748 | PyBList *p; | ^ In function ‘blist_get1’, inlined from ‘py_blist_repr’ at blist/_blist.c:6430:15, inlined from ‘py_blist_repr’ at blist/_blist.c:6368:1: blist/_blist.c:2759:20: warning: ‘p’ may be used uninitialized [-Wmaybe-uninitialized] 2759 | return _ob(blist_get1(p, i - so_far)); |^ blist/_blist.c:1061:19: note: in definition of macro ‘_ob’ 1061 | #define _ob(ret) (ret) | ^~~ blist/_blist.c: In function ‘py_blist_repr’: blist/_blist.c:2748:18: note: ‘p’ declared here 2748 | PyBList *p; | ^ In function ‘blist_get1’, inlined from ‘blist_delitem_return’ at blist/_blist.c:2817:14, inlined from ‘py_blist_ass_subscript’ at blist/_blist.c:6022:48: blist/_blist.c:2759:20: warning: ‘p’ may be used uninitialized [-Wmaybe-uninitialized] 2759 | return _ob(blist_get1(p, i - so_far)); |^ blist/_blist.c:1061:19: note: in definition of macro ‘_ob’ 1061 | #define _ob(ret) (ret) | ^~~ blist/_blist.c: In function ‘py_blist_ass_subscript’: blist/_blist.c:2748:18: note: ‘p’ declared here 2748 | PyBList *p; | ^ In function ‘blist_get1’, inlined from ‘py_blist_subscript’ at blist/_blist.c:6987:30: blist/_blist.c:2759:20: warning: ‘p’ may be used uninitialized [-Wmaybe-uninitialized] 2759 | return _ob(blist_get1(p, i - so_far)); |^ blist/_blist.c:1061:19: note: in definition of macro ‘_ob’ 1061 | #define _ob(ret) (ret) | ^~~ blist/_blist.c: In function ‘py_blist_subscript’: blist/_blist.c:2748:18: note: ‘p’ declared here 2748 | PyBList *p; | ^ x86_64-linux-gnu-gcc -pthread -shared -Wl,-O1 -Wl,-Bsymbolic-functions -Wl,-z,relro -g -fwrapv -O2 -Wl,-z,relro -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 build/temp.linux-x86_64-3.9/blist/_blist.o -o /<>/.pybuild/cpython3_3.9_blist/build/blist/_blist.cpython-39-x86_64-linux-gnu.so dh_auto_test -O--buildsystem=pybuild pybuild --test -i
Processed: bug 996235 is forwarded to https://gitlab.com/gitlab-org/gitlab-fog-azure-rm/-/issues/1
Processing commands for cont...@bugs.debian.org: > forwarded 996235 https://gitlab.com/gitlab-org/gitlab-fog-azure-rm/-/issues/1 Bug #996235 [src:ruby-gitlab-fog-azure-rm] ruby-gitlab-fog-azure-rm: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed: ArgumentError: tried to create Proc object without a block Set Bug forwarded-to-address to 'https://gitlab.com/gitlab-org/gitlab-fog-azure-rm/-/issues/1'. > thanks Stopping processing here. Please contact me if you need assistance. -- 996235: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=996235 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#997135: abydos: FTBFS: You must configure the bibtex_bibfiles setting
On Sat, Oct 23, 2021 at 08:56:35PM +0200, Lucas Nussbaum wrote: > Source: abydos > Version: 0.5.0+git20201231.344346a-3 > Severity: serious > Justification: FTBFS > Tags: bookworm sid ftbfs > > Hi, > > During a rebuild of all packages in sid, your package failed to build > on amd64. Ah, and though I've now fixed the issue, it still won't build in sid because of numpy not yet being ready for the Python 3.10 transition. I'll upload this once numpy has been fixed. Best wishes, Julian
Bug#983996: marked as pending in blist
Control: tag -1 pending Hello, Bug #983996 in blist reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/python-team/packages/blist/-/commit/751642750572a581e59df63ca136287d9c766ab8 Build with -O1 to workaround FTBFS with gcc-11, thanks Steve Langasek (Closes: #983996). (this message was generated automatically) -- Greetings https://bugs.debian.org/983996
Processed: Bug#983996 marked as pending in blist
Processing control commands: > tag -1 pending Bug #983996 [src:blist] blist: ftbfs with GCC-11 Added tag(s) pending. -- 983996: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=983996 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#998600: marked as done (mdevctl: FTBFS: dh_auto_test: error: /usr/share/cargo/bin/cargo build returned exit code 101)
Your message dated Thu, 18 Nov 2021 13:34:08 +
with message-id
and subject line Bug#998600: fixed in mdevctl 1.1.0-1
has caused the Debian Bug report #998600,
regarding mdevctl: FTBFS: dh_auto_test: error: /usr/share/cargo/bin/cargo build
returned exit code 101
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.)
--
998600: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=998600
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: mdevctl
Version: 1.0.0-1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20211104 ftbfs-bookworm
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> debian/rules binary
> dh binary --buildsystem cargo
>dh_update_autotools_config -O--buildsystem=cargo
>dh_autoreconf -O--buildsystem=cargo
>dh_auto_configure -O--buildsystem=cargo
> install -d /<>/debian/.debhelper/generated/_source/home
> find . ! -newermt 'jan 01, 2000' -exec touch -d@1626260104 {} +
> cp debian/cargo-checksum.json .cargo-checksum.json
> rm -f Cargo.lock
> /usr/share/cargo/bin/cargo prepare-debian debian/cargo_registry
> --link-from-system
> debian cargo wrapper: options, profiles, parallel: ['parallel=4'] [] ['-j4']
> debian cargo wrapper: rust_type, gnu_type: x86_64-unknown-linux-gnu,
> x86_64-linux-gnu
> debian cargo wrapper: linking /usr/share/cargo/registry/* into
> /<>/debian/cargo_registry/
>dh_auto_build -O--buildsystem=cargo
> find . ! -newermt 'jan 01, 2000' -exec touch -d@1626260104 {} +
>dh_auto_test -O--buildsystem=cargo
> find . ! -newermt 'jan 01, 2000' -exec touch -d@1626260104 {} +
> /usr/share/cargo/bin/cargo build
> debian cargo wrapper: options, profiles, parallel: ['parallel=4'] [] ['-j4']
> debian cargo wrapper: rust_type, gnu_type: x86_64-unknown-linux-gnu,
> x86_64-linux-gnu
> debian cargo wrapper: running subprocess (['env', 'RUST_BACKTRACE=1',
> '/usr/bin/cargo', '-Zavoid-dev-deps', 'build', '--verbose', '--verbose',
> '-j4', '--target', 'x86_64-unknown-linux-gnu'],) {}
> error: failed to select a version for the requirement `env_logger = "^0.7.1"`
> candidate versions found which didn't match: 0.9.0
> location searched: directory source `/<>/debian/cargo_registry`
> (which is replacing registry `crates-io`)
> required by package `mdevctl v1.0.0 (/<>)`
> perhaps a crate was updated and forgotten to be re-vendored?
> rm -fr -- /tmp/dh-xdg-rundir-5hMmEe4U
> dh_auto_test: error: /usr/share/cargo/bin/cargo build returned exit code 101
The full build log is available from:
http://qa-logs.debian.net/2021/11/04/mdevctl_1.0.0-1_unstable.log
A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!
If you reassign this bug to another package, please marking it as 'affects'-ing
this package. See https://www.debian.org/Bugs/server-control#affects
If you fail to reproduce this, please provide a build log and diff it with mine
so that we can identify if something relevant changed in the meantime.
--- End Message ---
--- Begin Message ---
Source: mdevctl
Source-Version: 1.1.0-1
Done: Christian Ehrhardt
We believe that the bug you reported is fixed in the latest version of
mdevctl, 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 998...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Christian Ehrhardt (supplier of updated
mdevctl package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Tue, 09 Nov 2021 14:42:49 +0100
Source: mdevctl
Architecture: source
Version: 1.1.0-1
Distribution: unstable
Urgency: medium
Maintainer: Christian Ehrhardt
Changed-By: Christian Ehrhardt
Closes: 998600
Changes:
mdevctl (1.1.0-1) unstable; urgency=medium
.
* New upstream version 1.1.0
- fixes FTBFS in regard to env_logger (Closes: #998600)
* d/control: bump Standards-Version to 4.6.0 (no changes needed)
* d/control: use substvars provided by dh-cargo
* d/p/lower-versions-for-unstable.patch: update
Bug#1000138: Acknowledgement (/usr/bin/screen: command arguments beyond 62 silently discarded)
Also, it has a problem with long arguments:
$ cat t.sh
#!/bin/sh
all="$*"
echo $# ${#all}
sleep 5
$ ./t.sh a "$(yes | head -1)" b
3 20003
$ screen ./t.sh a "$(yes | head -1)" b
[ displays "3 20003", pauses 5 seconds, exits ]
$ screen screen ./t.sh a "$(yes | head -1)" b
[ displays "1 1", pauses 5 seconds, exits ]
$
Here it loses all the arguments after the first long one !
--
Ian JacksonThese opinions are my own.
Pronouns: they/he. If I emailed you from @fyvzl.net or @evade.org.uk,
that is a private address which bypasses my fierce spamfilter.
Processed (with 3 errors): Confirmed and fix verified
Processing commands for cont...@bugs.debian.org: > tags 998600 + confirmed fixed pending Bug #998600 [src:mdevctl] mdevctl: FTBFS: dh_auto_test: error: /usr/share/cargo/bin/cargo build returned exit code 101 Added tag(s) pending, fixed, and confirmed. > I was able to confirm the FTBFS and also that the 1.1.0-1 that I Unknown command or malformed arguments to command. > prepared has fixed it. Unknown command or malformed arguments to command. > I'll mark it in the changelog and upload it later. Unknown command or malformed arguments to command. > -- Stopping processing here. Please contact me if you need assistance. -- 998600: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=998600 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#998600: Confirmed and fix verified
tags 998600 + confirmed fixed pending I was able to confirm the FTBFS and also that the 1.1.0-1 that I prepared has fixed it. I'll mark it in the changelog and upload it later. -- Christian Ehrhardt Staff Engineer, Ubuntu Server Canonical Ltd
Bug#1000138: /usr/bin/screen: command arguments beyond 62 silently discarded
Package: screen
Version: 4.8.0-7
Severity: serious
File: /usr/bin/screen
Tags: upstream
Justification: data loss
X-Debbugs-Cc: t...@womack.net
Steps to reproduce and observed behaviour:
$ cat t.sh
#!/bin/sh
echo $#
sleep 5
$ ./t.sh {0..999}
1000
$ screen ./t.sh {0..999}
[ displays 1000 and exits ]
$ screen screen ./t.sh {0..999}
[ displays 62 and exits ]
$
Expected behaviour: 1000 in all cases.
Tolerable behaviour:
1000 where currently supported. Where not supported, a fatal error
(message on stderr plus nonzero exit status).
This is a potential data loss bug so might justify even "grave" but I
thought that was overkill. I hope you will agree that this deserves
an RC bug.
This has been reported upstream here:
https://savannah.gnu.org/bugs/?61504
Ian.
-- Package-specific info:
File Existence and Permissions
--
drwxr-xr-x 8 root root 4096 Nov 18 13:01 /run
lrwxrwxrwx 1 root ian 4 Jun 3 2016 /var/run -> /run
-rwxr-xr-x 1 root root 482312 Sep 2 00:25 /usr/bin/screen
-rw-r--r-- 1 root root119 Nov 18 13:01 /etc/tmpfiles.d/screen-cleanup.conf
lrwxrwxrwx 1 root root 9 Nov 18 13:01
/lib/systemd/system/screen-cleanup.service -> /dev/null
-rwxr-xr-x 1 root root 1222 Feb 18 2021 /etc/init.d/screen-cleanup
lrwxrwxrwx 1 root root 24 Nov 18 13:01 /etc/rcS.d/S10screen-cleanup ->
../init.d/screen-cleanup
File contents
-
### /etc/tmpfiles.d/screen-cleanup.conf
__
# This file is generated by /var/lib/dpkg/info/screen.postinst upon package
configuration
d /run/screen 1777 root utmp
__
-- System Information:
Debian Release: bookworm/sid
APT prefers unstable
APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 5.10.0-0.bpo.9-amd64 (SMP w/8 CPU threads)
Kernel taint flags: TAINT_WARN
Locale: LANG=C, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)
Versions of packages screen depends on:
ii libc6 2.32-4
ii libcrypt1 1:4.4.26-1
ii libpam0g 1.4.0-10
ii libtinfo6 6.3-1
ii libutempter0 1.2.1-2
screen recommends no packages.
Versions of packages screen suggests:
pn byobu | screenie | iselect
pn ncurses-term
-- no debconf information
Processed: tbb 21.03 required for GCC 11
Processing control commands: > severity -1 serious Bug #987689 [libtbb2] Upgrade to 2021.03 Severity set to 'serious' from 'important' > tags -1 + sid bookworm Bug #987689 [libtbb2] Upgrade to 2021.03 Added tag(s) sid and bookworm. -- 987689: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=987689 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#998483: marked as done (ruby-adsf: FTBFS: ERROR: Test "ruby3.0" failed: LoadError: Couldn't find handler for: puma, thin, falcon, webrick.)
Your message dated Thu, 18 Nov 2021 12:52:40 + with message-id and subject line Bug#998483: fixed in ruby-adsf 1.4.5+dfsg1-2 has caused the Debian Bug report #998483, regarding ruby-adsf: FTBFS: ERROR: Test "ruby3.0" failed: LoadError: Couldn't find handler for: puma, thin, falcon, webrick. 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.) -- 998483: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=998483 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: ruby-adsf Version: 1.4.5+dfsg1-1 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20211104 ftbfs-bookworm Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > LoadError: Couldn't find handler for: puma, thin, falcon, webrick. > /usr/lib/ruby/vendor_ruby/rack/handler.rb:45:in `pick' > /usr/lib/ruby/vendor_ruby/rack/handler.rb:60:in `default' > /<>/adsf/lib/adsf/server.rb:77:in `build_handler' > /<>/adsf/lib/adsf/server.rb:17:in `run' > /<>/adsf/test/test_server.rb:14:in `block in run_server' > > 20 runs, 18 assertions, 0 failures, 11 errors, 0 skips > rake aborted! > Command failed with status (1) > > Tasks: TOP => test > (See full trace by running task with --trace) > rake aborted! > Command failed with status (1): [/usr/bin/ruby3.0 -S rake test...] > /<>/debian/ruby-tests.rake:6:in `block (3 levels) in (required)>' > /<>/debian/ruby-tests.rake:5:in `chdir' > /<>/debian/ruby-tests.rake:5:in `block (2 levels) in (required)>' > Tasks: TOP => default => test-adsf > (See full trace by running task with --trace) > ERROR: Test "ruby3.0" failed: The full build log is available from: http://qa-logs.debian.net/2021/11/04/ruby-adsf_1.4.5+dfsg1-1_unstable.log A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! If you reassign this bug to another package, please marking it as 'affects'-ing this package. See https://www.debian.org/Bugs/server-control#affects If you fail to reproduce this, please provide a build log and diff it with mine so that we can identify if something relevant changed in the meantime. --- End Message --- --- Begin Message --- Source: ruby-adsf Source-Version: 1.4.5+dfsg1-2 Done: Cédric Boutillier We believe that the bug you reported is fixed in the latest version of ruby-adsf, 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 998...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Cédric Boutillier (supplier of updated ruby-adsf 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: Thu, 18 Nov 2021 11:57:54 +0100 Source: ruby-adsf Architecture: source Version: 1.4.5+dfsg1-2 Distribution: unstable Urgency: medium Maintainer: Debian Ruby Team Changed-By: Cédric Boutillier Closes: 998483 Changes: ruby-adsf (1.4.5+dfsg1-2) unstable; urgency=medium . [ Debian Janitor ] * Remove constraints unnecessary since buster: + Build-Depends: Drop versioned constraint on ruby-em-websocket, ruby-listen and ruby-rack. . [ Cédric Boutillier ] * Build-depend on ruby-webrick (Closes: #998483) * Bump Standards-Version to 4.6.0 (no changes needed) Checksums-Sha1: cecb15a1d61686844d2e7fac924311e552b226fc 1655 ruby-adsf_1.4.5+dfsg1-2.dsc a0dff77d7fea76f51ff7a4c83c99e1f2da5aa042 12120 ruby-adsf_1.4.5+dfsg1.orig.tar.xz 89f96a5b381c0745d42ee38857b231f8a9fd288c 4720 ruby-adsf_1.4.5+dfsg1-2.debian.tar.xz 13444cf3e420d87d9ee3f2dc123f02c4daa3277d 9227 ruby-adsf_1.4.5+dfsg1-2_amd64.buildinfo Checksums-Sha256: bb38aa4f690cc1046243afdbc1eaae28e31119aca890b71b4b8e16ad108a9e6e 1655 ruby-adsf_1.4.5+dfsg1-2.dsc 388890784b621ff60fd189c2f8309843e01c3a486c8f7896e569a53c2a832a1d 12120 ruby-adsf_1.4.5+dfsg1.orig.tar.xz 4a2b135b273963868e01a48bb58c8103fef83fa8472013dca471465a517593ff 4720 ruby-adsf_1.4.5+dfsg1-2.debian.tar.xz 84137edca92e6f1fb3317e4c116855730815f8ef1f935d158fac36297f9f3d26 9227 ruby-adsf_1.4.5+dfsg1-2_amd64.buildinfo Files: 15ab66e376b917994f8f8b69736d71be 1655 ruby
Bug#996125: marked as done (ruby-arbre: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed: RuntimeError:)
Your message dated Thu, 18 Nov 2021 12:52:46 + with message-id and subject line Bug#996125: fixed in ruby-arbre 1.2.1-5~exp1 has caused the Debian Bug report #996125, regarding ruby-arbre: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed: RuntimeError: 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.) -- 996125: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=996125 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: ruby-arbre Version: 1.2.1-4 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: debian-r...@lists.debian.org Usertags: ruby3.0 Hi, We are about to enable building against ruby3.0 on unstable. During a test rebuild, ruby-arbre was found to fail to build in that situation. To reproduce this locally, you need to install ruby-all-dev from experimental on an unstable system or build chroot. Relevant part (hopefully): > RuntimeError: > Application has been already initialized. > # > /usr/share/rubygems-integration/all/gems/railties-6.0.3.7/lib/rails/application.rb:362:in > `initialize!' > # > /usr/share/rubygems-integration/all/gems/railties-6.0.3.7/lib/rails/railtie.rb:190:in > `public_send' > # > /usr/share/rubygems-integration/all/gems/railties-6.0.3.7/lib/rails/railtie.rb:190:in > `method_missing' > # > /usr/share/rubygems-integration/all/gems/combustion-1.3.0/lib/combustion.rb:45:in > `initialize!' > # ./spec/rails/rails_spec_helper.rb:4:in `' > # > /usr/share/rubygems-integration/all/gems/activesupport-6.0.3.7/lib/active_support/dependencies.rb:324:in > `require' > # > /usr/share/rubygems-integration/all/gems/activesupport-6.0.3.7/lib/active_support/dependencies.rb:324:in > `block in require' > # > /usr/share/rubygems-integration/all/gems/activesupport-6.0.3.7/lib/active_support/dependencies.rb:291:in > `load_dependency' > # > /usr/share/rubygems-integration/all/gems/activesupport-6.0.3.7/lib/active_support/dependencies.rb:324:in > `require' > # ./spec/rails/integration/rendering_spec.rb:1:in `' > # > /usr/share/rubygems-integration/all/gems/activesupport-6.0.3.7/lib/active_support/dependencies.rb:318:in > `load' > # > /usr/share/rubygems-integration/all/gems/activesupport-6.0.3.7/lib/active_support/dependencies.rb:318:in > `block in load' > # > /usr/share/rubygems-integration/all/gems/activesupport-6.0.3.7/lib/active_support/dependencies.rb:291:in > `load_dependency' > # > /usr/share/rubygems-integration/all/gems/activesupport-6.0.3.7/lib/active_support/dependencies.rb:318:in > `load' > > Finished in 0.9 seconds (files took 1.77 seconds to load) > 0 examples, 0 failures, 2 errors occurred outside of examples > > /usr/bin/ruby3.0 > -I/usr/share/rubygems-integration/all/gems/rspec-support-3.9.3/lib:/usr/share/rubygems-integration/all/gems/rspec-core-3.9.2/lib > /usr/share/rubygems-integration/all/gems/rspec-core-3.9.2/exe/rspec > --pattern ./spec/\*\*/\*_spec.rb --format documentation failed > ERROR: Test "ruby3.0" failed: The full build log is available at https://people.debian.org/~kanashiro/ruby3.0/round2/builds/3/ruby-arbre/ruby-arbre_1.2.1-4+rebuild1633375280_amd64.build.txt signature.asc Description: PGP signature --- End Message --- --- Begin Message --- Source: ruby-arbre Source-Version: 1.2.1-5~exp1 Done: Cédric Boutillier We believe that the bug you reported is fixed in the latest version of ruby-arbre, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 996...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Cédric Boutillier (supplier of updated ruby-arbre package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Wed, 17 Nov 2021 14:19:32 +0100 Source: ruby-arbre Architecture: source Version: 1.2.1-5~exp1 Distribution: experimental Urgency: medium Maintainer: Debian Ruby Team Changed-By: Cédric Boutillier Closes: 996125 Changes: ruby-arbre (1.2.1-5~exp1) experimental; urgency=medium . * Team upload * Update team name * Add .gitattributes to keep unwanted files out of the source package * (Build-)depend on ruby-activesupport >= 6.1 and capybara >= 3.31 (Closes: #996125) * Use
Processed: tagging 999397
Processing commands for cont...@bugs.debian.org: > tags 999397 + bookworm sid Bug #999397 [src:siphashc] siphashc ftbfs with Python 3.10 (test failures) Added tag(s) sid and bookworm. > thanks Stopping processing here. Please contact me if you need assistance. -- 999397: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=999397 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: severity of 999381 is serious
Processing commands for cont...@bugs.debian.org: > severity 999381 serious Bug #999381 [src:python-pairix] python-pairix ftbfs with Python 3.10 (test failures) Severity set to 'serious' from 'important' > thanks Stopping processing here. Please contact me if you need assistance. -- 999381: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=999381 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: severity of 999397 is serious
Processing commands for cont...@bugs.debian.org: > severity 999397 serious Bug #999397 [src:siphashc] siphashc ftbfs with Python 3.10 (test failures) Severity set to 'serious' from 'important' > thanks Stopping processing here. Please contact me if you need assistance. -- 999397: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=999397 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Bug#998483 marked as pending in ruby-adsf
Processing control commands: > tag -1 pending Bug #998483 [src:ruby-adsf] ruby-adsf: FTBFS: ERROR: Test "ruby3.0" failed: LoadError: Couldn't find handler for: puma, thin, falcon, webrick. Added tag(s) pending. -- 998483: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=998483 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#998483: marked as pending in ruby-adsf
Control: tag -1 pending Hello, Bug #998483 in ruby-adsf reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/ruby-team/ruby-adsf/-/commit/fa16d86c8a45e933bac47d858ccd4b08a13c59f5 Build-depend on ruby-webrick (Closes: #998483) (this message was generated automatically) -- Greetings https://bugs.debian.org/998483
Bug#998600: Ack
Thanks for the rebuild report Lucas, I'll have a look. I was working on 1.1.0 anyway and thereby should be able to resolve this. -- Christian Ehrhardt Staff Engineer, Ubuntu Server Canonical Ltd
Bug#999860: marked as done (python3-cylc fails to install)
Your message dated Thu, 18 Nov 2021 11:03:42 + with message-id and subject line Bug#999860: fixed in cylc-flow 8.0~b3-2 has caused the Debian Bug report #999860, regarding python3-cylc fails to install 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.) -- 999860: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=999860 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: python3-cylc Version: 8.0~b3-1 Severity: serious https://piuparts.debian.org/sid/fail/python3-cylc_8.0~b3-1.log ... Setting up python3-cylc (8.0~b3-1) ... File "/usr/lib/python3/dist-packages/cylc/flow/batch_sys_handlers/at.py", line 1 <<< HEAD:cylc/flow/batch_sys_handlers/at.py ^ SyntaxError: invalid syntax File "/usr/lib/python3/dist-packages/cylc/flow/batch_sys_handlers/background.py", line 1 <<< HEAD:cylc/flow/batch_sys_handlers/background.py ^ SyntaxError: invalid syntax File "/usr/lib/python3/dist-packages/cylc/flow/batch_sys_handlers/loadleveler.py", line 1 <<< HEAD:cylc/flow/batch_sys_handlers/loadleveler.py ^ SyntaxError: invalid syntax File "/usr/lib/python3/dist-packages/cylc/flow/batch_sys_handlers/moab.py", line 1 <<< HEAD:cylc/flow/batch_sys_handlers/moab.py ^ SyntaxError: invalid syntax File "/usr/lib/python3/dist-packages/cylc/flow/batch_sys_handlers/pbs.py", line 1 <<< HEAD:cylc/flow/batch_sys_handlers/pbs.py ^ SyntaxError: invalid syntax File "/usr/lib/python3/dist-packages/cylc/flow/batch_sys_handlers/pbs_multi_cluster.py", line 1 <<< HEAD:cylc/flow/batch_sys_handlers/pbs_multi_cluster.py ^ SyntaxError: invalid syntax File "/usr/lib/python3/dist-packages/cylc/flow/batch_sys_handlers/sge.py", line 1 <<< HEAD:cylc/flow/batch_sys_handlers/sge.py ^ SyntaxError: invalid syntax File "/usr/lib/python3/dist-packages/cylc/flow/scripts/cylc_broadcast.py", line 3 <<< HEAD:cylc/flow/scripts/cylc_broadcast.py ^ SyntaxError: invalid syntax File "/usr/lib/python3/dist-packages/cylc/flow/scripts/cylc_cat_log.py", line 3 <<< HEAD:cylc/flow/scripts/cylc_cat_log.py ^ SyntaxError: invalid syntax File "/usr/lib/python3/dist-packages/cylc/flow/scripts/cylc_cycle_point.py", line 4 <<< HEAD:cylc/flow/scripts/cylc_cycle_point.py ^ SyntaxError: invalid syntax File "/usr/lib/python3/dist-packages/cylc/flow/scripts/cylc_diff.py", line 3 <<< HEAD:cylc/flow/scripts/cylc_diff.py ^ SyntaxError: invalid syntax File "/usr/lib/python3/dist-packages/cylc/flow/scripts/cylc_ext_trigger.py", line 3 <<< HEAD:cylc/flow/scripts/cylc_ext_trigger.py ^ SyntaxError: invalid syntax File "/usr/lib/python3/dist-packages/cylc/flow/scripts/cylc_function_run.py", line 2 <<< HEAD:cylc/flow/scripts/cylc_function_run.py ^ SyntaxError: invalid syntax File "/usr/lib/python3/dist-packages/cylc/flow/scripts/cylc_list.py", line 3 <<< HEAD:cylc/flow/scripts/cylc_list.py ^ SyntaxError: invalid syntax File "/usr/lib/python3/dist-packages/cylc/flow/scripts/cylc_message.py", line 3 <<< HEAD:cylc/flow/scripts/cylc_message.py ^ SyntaxError: invalid syntax File "/usr/lib/python3/dist-packages/cylc/flow/scripts/cylc_remote_tidy.py", line 2 <<< HEAD:cylc/flow/scripts/cylc_remote_tidy.py ^ SyntaxError: invalid syntax File "/usr/lib/python3/dist-packages/cylc/flow/scripts/cylc_report_timings.py", line 3 <<< HEAD:cylc/flow/scripts/cylc_report_timings.py ^ SyntaxError: invalid syntax File "/usr/lib/python3/dist-packages/cylc/flow/scripts/cylc_run.py", line 1 <<< HEAD:cylc/flow/scripts/cylc_run.py ^ SyntaxError: invalid syntax File "/usr/lib/python3/dist-packages/cylc/flow/scripts/cylc_suite_state.py", line 3 <<< HEAD:cylc/flow/scripts/cylc_suite_state.py ^ SyntaxError: invalid syntax File "/usr/lib/python3/dist-packages/cylc/flow/scripts/cylc_view.py", line 3 <<< HEAD:cylc/flow/scripts/cylc_view.py ^ SyntaxError: invalid syntax File "/usr/lib/python3/dist-packages/cylc/flow/suite_events.py", line 1 <<< HEAD:cylc/flow/suite_events.py ^ SyntaxError: invalid syntax File "/usr/lib/python3/dist-packages/cylc/flow/tests/cycling/__init__.py", line 1 <<< HEAD:cylc/flow/tests/cycling/__init__.py ^ SyntaxError:
Processed: libpython3.10-stdlib,python3-gdbm: both ship /usr/lib/python3.10/lib-dynload/_dbm.cpython-310-x86_64-linux-gnu.so
Processing control commands: > found -1 3.10.0-5 Bug #12 [libpython3.10-stdlib,python3-gdbm] libpython3.10-stdlib,python3-gdbm: both ship /usr/lib/python3.10/lib-dynload/_dbm.cpython-310-x86_64-linux-gnu.so There is no source info for the package 'python3-gdbm' at version '3.10.0-5' with architecture '' Marked as found in versions python3.10/3.10.0-5. > found -1 3.10.0~b1-3 Bug #12 [libpython3.10-stdlib,python3-gdbm] libpython3.10-stdlib,python3-gdbm: both ship /usr/lib/python3.10/lib-dynload/_dbm.cpython-310-x86_64-linux-gnu.so Marked as found in versions python3-stdlib-extensions/3.10.0~b1-3 and python3.10/3.10.0~b1-3. -- 12: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=12 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#999912: libpython3.10-stdlib,python3-gdbm: both ship /usr/lib/python3.10/lib-dynload/_dbm.cpython-310-x86_64-linux-gnu.so
Package: libpython3.10-stdlib,python3-gdbm Severity: serious User: trei...@debian.org Usertags: edos-file-overwrite Control: found -1 3.10.0-5 Control: found -1 3.10.0~b1-3 Hi, automatic installation tests of packages that share a file and at the same time do not conflict by their package dependency relationships has detected the following problem: Preparing to unpack .../python3-gdbm_3.10.0~b1-3_amd64.deb ... Unpacking python3-gdbm:amd64 (3.10.0~b1-3) ... dpkg: error processing archive /var/cache/apt/archives/python3-gdbm_3.10.0~b1-3_amd64.deb (--unpack): trying to overwrite '/usr/lib/python3.10/lib-dynload/_dbm.cpython-310-x86_64-linux-gnu.so', which is also in package libpython3.10-stdlib:amd64 3.10.0-5 Errors were encountered while processing: /var/cache/apt/archives/python3-gdbm_3.10.0~b1-3_amd64.deb This is a serious bug as it makes installation fail, and violates sections 7.6.1 and 10.1 of the policy. An optimal solution would consist in only one of the packages installing that file, and renaming or removing the file in the other package. Depending on the circumstances you might also consider Replace relations or file diversions. If the conflicting situation cannot be resolved then, as a last resort, the two packages have to declare a mutual Conflict. Please take into account that Replaces, Conflicts and diversions should only be used when packages provide different implementations for the same functionality. Here is a list of files that are known to be shared by both packages (according to the Contents file for sid/amd64, which may be slightly out of sync): /usr/lib/python3.10/lib-dynload/_dbm.cpython-310-x86_64-linux-gnu.so This bug is assigned to both packages. If you, the maintainers of the two packages in question, have agreed on which of the packages will resolve the problem please reassign the bug to that package. You may also register in the BTS that the other package is affected by the bug. Please note: This is a conflict between libpython3.10-stdlib/sid and python3-gdbm/experimental. Cheers, Andreas PS: for more information about the detection of file overwrite errors of this kind see https://qa.debian.org/dose/file-overwrites.html libpython3.10-stdlib=3.10.0-5_python3-gdbm=3.10.0~b1-3.log.gz Description: application/gzip
Bug#999908: python3-celery-haystack-ng: missing Breaks+Replaces: python3-django-celery-haystack (<< 0.20)
Package: python3-celery-haystack-ng Version: 0.20.post2-1 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package failed to install because it tries to overwrite other packages files without declaring a Breaks+Replaces relation. See policy 7.6 at https://www.debian.org/doc/debian-policy/ch-relationships.html#overwriting-files-and-replacing-packages-replaces >From the attached log (scroll to the bottom...): Selecting previously unselected package python3-celery-haystack-ng. Preparing to unpack .../16-python3-celery-haystack-ng_0.20.post2-1_all.deb ... Unpacking python3-celery-haystack-ng (0.20.post2-1) ... dpkg: error processing archive /tmp/apt-dpkg-install-09EOH1/16-python3-celery-haystack-ng_0.20.post2-1_all.deb (--unpack): trying to overwrite '/usr/lib/python3/dist-packages/celery_haystack/__init__.py', which is also in package python3-django-celery-haystack 0.10-4 Errors were encountered while processing: /tmp/apt-dpkg-install-09EOH1/16-python3-celery-haystack-ng_0.20.post2-1_all.deb I assume python3-celery-haystack-ng is intended as successor to python3-django-celery-haystack which was last released with buster and is RC buggy in sid. cheers, Andreas python3-django-celery-haystack=0.10-4_python3-celery-haystack-ng=0.20.post2-1.log.gz Description: application/gzip
Bug#996386: marked as done (ruby-sham-rack: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed: cannot load such file -- webrick/httputils)
Your message dated Thu, 18 Nov 2021 10:35:49 + with message-id and subject line Bug#996386: fixed in ruby-sham-rack 1.4.1-3 has caused the Debian Bug report #996386, regarding ruby-sham-rack: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed: cannot load such file -- webrick/httputils 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.) -- 996386: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=996386 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: ruby-sham-rack Version: 1.4.1-2 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: debian-r...@lists.debian.org Usertags: ruby3.0 Hi, We are about to enable building against ruby3.0 on unstable. During a test rebuild, ruby-sham-rack was found to fail to build in that situation. To reproduce this locally, you need to install ruby-all-dev from experimental on an unstable system or build chroot. Relevant part (hopefully): > cannot load such file -- webrick/httputils > # ./spec/sham_rack_spec.rb:6:in `' > > > Finished in 0.8 seconds (files took 2.28 seconds to load) > 0 examples, 0 failures, 1 error occurred outside of examples > > /usr/bin/ruby3.0 > -I/usr/share/rubygems-integration/all/gems/rspec-support-3.9.3/lib:/usr/share/rubygems-integration/all/gems/rspec-core-3.9.2/lib > /usr/share/rubygems-integration/all/gems/rspec-core-3.9.2/exe/rspec > --pattern ./spec/\*\*/\*_spec.rb failed > ERROR: Test "ruby3.0" failed: Note that webrick has been removed from the standard library. It's already been packaged and is currently in NEW, but this package now needs an explicit dependency on it. The full build log is available at https://people.debian.org/~kanashiro/ruby3.0/round2/builds/3/ruby-sham-rack/ruby-sham-rack_1.4.1-2+rebuild1633395351_amd64.build.txt signature.asc Description: PGP signature --- End Message --- --- Begin Message --- Source: ruby-sham-rack Source-Version: 1.4.1-3 Done: Cédric Boutillier We believe that the bug you reported is fixed in the latest version of ruby-sham-rack, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 996...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Cédric Boutillier (supplier of updated ruby-sham-rack 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: Thu, 18 Nov 2021 11:09:05 +0100 Source: ruby-sham-rack Architecture: source Version: 1.4.1-3 Distribution: unstable Urgency: medium Maintainer: Debian Ruby Team Changed-By: Cédric Boutillier Closes: 996386 Changes: ruby-sham-rack (1.4.1-3) unstable; urgency=medium . [ Utkarsh Gupta ] * Add salsa-ci.yml . [ Debian Janitor ] * Trim trailing whitespace. * Use secure copyright file specification URI. * Use secure URI in Homepage field. * Bump debhelper from old 11 to 12. * Set debhelper-compat version in Build-Depends. * Set upstream metadata fields: Bug-Database, Bug-Submit, Repository, Repository-Browse. * Update standards version to 4.5.0, no changes needed. * Remove constraints unnecessary since buster: + Build-Depends: Drop versioned constraint on ruby-rr. * Update watch file format version to 4. * Bump debhelper from old 12 to 13. * Update standards version to 4.5.1, no changes needed. . [ Cédric Boutillier ] * Add patch to use URI.open in specs (Closes: #996386) * Use gem install layout * Remove explicit dependency on ruby interpreter * Rules-Requires-Root set to no * Bump Standards-Version to 4.6.0 (no changes needed) Checksums-Sha1: 7bdaf7e892d8d5d330c6e16b635226d0a11f003c 1527 ruby-sham-rack_1.4.1-3.dsc 6f9bcc26e57ccf2c829c774cbce08cd85988f180 6660 ruby-sham-rack_1.4.1.orig.tar.gz f68849eb2b33dfd1559cbd7259c26896f7cd1934 4648 ruby-sham-rack_1.4.1-3.debian.tar.xz f9d14f9edd9421285d8c98614cd99b0b466f817d 9544 ruby-sham-rack_1.4.1-3_amd64.buildinfo Checksums-Sha256: 26fd66c79aaa9681b6d2eb976c7fda99cc87fd3d5661ef885fb8f97254712884 1527 ruby-sham-rack_1.4.1-3.dsc 4c2e1c2166c545e31ade8e5de1f96651422067a9ebde4d5c62ddb53bb9082a2b 6660 ruby-sham-rack_1.4.1.orig.tar.gz da502737549bcafdb113053611e16d7bb20a2f5c8fdf499293b49c1c5f8e2320
Processed: Re: Bug#999904: Uncoordinated split of debugedit package out of src:rpm
Processing control commands: > tag -1 + confirmed pending Bug #04 [src:debugedit,src:rpm] Uncoordinated split of debugedit package out of src:rpm Added tag(s) pending and confirmed. -- 04: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=04 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#999904: Uncoordinated split of debugedit package out of src:rpm
control: tag -1 + confirmed pending On Thu, Nov 18, 2021 at 09:45:06AM +0100, Laurent Bigonville wrote: > Source: debugedit,rpm > Severity: serious > Tags: sid bookworm > > Hello, > > debugedit has been split out of the src:rpm package, but src:rpm is > still building the package as well. > > In addition to that, rpm package has a strong versioned dependency > against debugedit (debugedit (= 4.16.1.2+dfsg1-3)) which means that rpm > cannot be installed anymore. > > We need to keep this package out of testing until this is resolved FTR, it has not been completely uncoordinated, there is an ongoing discussion on the RPM packaging team's mailing list where Matthias asked about our plans to upgrade rpm to 4.17 and I confirmed that there is work in progress and it will most probably be done in the next couple of days. Still, thanks for filing this bug for the purpose of keeping the new version of debugedit out of testing for the present. G'luck, Peter -- Peter Pentchev r...@ringlet.net r...@debian.org p...@storpool.com PGP key:http://people.FreeBSD.org/~roam/roam.key.asc Key fingerprint 2EE7 A7A5 17FC 124C F115 C354 651E EFB0 2527 DF13 signature.asc Description: PGP signature
Bug#999907: libglobalarrays-dev,libga-dev: both ship /usr/lib/x86_64-linux-gnu/libga.a
Package: libglobalarrays-dev,libga-dev Severity: serious Tags: sid bookworm User: trei...@debian.org Usertags: edos-file-overwrite Control: found -1 5.7.2-2 Control: found -1 1:2.4.7-5 Hi, automatic installation tests of packages that share a file and at the same time do not conflict by their package dependency relationships has detected the following problem: Preparing to unpack .../libga-dev_1%3a2.4.7-5_amd64.deb ... Unpacking libga-dev:amd64 (1:2.4.7-5) ... dpkg: error processing archive /var/cache/apt/archives/libga-dev_1%3a2.4.7-5_amd64.deb (--unpack): trying to overwrite '/usr/lib/x86_64-linux-gnu/libga.a', which is also in package libglobalarrays-dev 5.7.2-2 dpkg-deb: error: paste subprocess was killed by signal (Broken pipe) Errors were encountered while processing: /var/cache/apt/archives/libga-dev_1%3a2.4.7-5_amd64.deb This is a serious bug as it makes installation fail, and violates sections 7.6.1 and 10.1 of the policy. An optimal solution would consist in only one of the packages installing that file, and renaming or removing the file in the other package. Depending on the circumstances you might also consider Replace relations or file diversions. If the conflicting situation cannot be resolved then, as a last resort, the two packages have to declare a mutual Conflict. Please take into account that Replaces, Conflicts and diversions should only be used when packages provide different implementations for the same functionality. Here is a list of files that are known to be shared by both packages (according to the Contents file for sid/amd64, which may be slightly out of sync): /usr/lib/x86_64-linux-gnu/libga.a This bug is assigned to both packages. If you, the maintainers of the two packages in question, have agreed on which of the packages will resolve the problem please reassign the bug to that package. You may also register in the BTS that the other package is affected by the bug. libglobalarrays-dev does have one reverse build-dependency: nwchem. libga-dev does have none. Cheers, Andreas PS: for more information about the detection of file overwrite errors of this kind see https://qa.debian.org/dose/file-overwrites.html libglobalarrays-dev=5.7.2-2_libga-dev=1:2.4.7-5.log.gz Description: application/gzip
Processed: libglobalarrays-dev,libga-dev: both ship /usr/lib/x86_64-linux-gnu/libga.a
Processing control commands: > found -1 5.7.2-2 Bug #07 [libglobalarrays-dev,libga-dev] libglobalarrays-dev,libga-dev: both ship /usr/lib/x86_64-linux-gnu/libga.a There is no source info for the package 'libga-dev' at version '5.7.2-2' with architecture '' Marked as found in versions ga/5.7.2-2. > found -1 1:2.4.7-5 Bug #07 [libglobalarrays-dev,libga-dev] libglobalarrays-dev,libga-dev: both ship /usr/lib/x86_64-linux-gnu/libga.a There is no source info for the package 'libglobalarrays-dev' at version '1:2.4.7-5' with architecture '' Marked as found in versions galib/1:2.4.7-5. -- 07: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=07 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#996386: marked as pending in ruby-sham-rack
Control: tag -1 pending Hello, Bug #996386 in ruby-sham-rack reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/ruby-team/ruby-sham-rack/-/commit/04e7cb27dd5abd33a0a699e1b788a131c341cad8 Add patch to use URI.open in specs (Closes: #996386) (this message was generated automatically) -- Greetings https://bugs.debian.org/996386
Bug#999903: [Pkg-matrix-maintainers] Bug#999903: python3-olm: python import fails undefined symbol: olm_account_fallback_key
Control: tags -1 +unreproducible +moreinfo Control: severity -1 important Hi Kyle, Quoting Kyle Robbertze (2021-11-18 09:39:57) > Package: python3-olm > Version: 3.2.1~dfsg-7 > Severity: grave > Justification: renders package unusable > > Dear Maintainer, > > Applications are unable to import olm due to the following error: > > > Traceback (most recent call last): > > File "", line 1, in > > File "/usr/lib/python3/dist-packages/olm/__init__.py", line 24, in > > > > from .utility import ed25519_verify, OlmVerifyError, OlmHashError, > > sha256 > > File "/usr/lib/python3/dist-packages/olm/utility.py", line 39, in > > from _libolm import ffi, lib # type: ignore > > ImportError: /usr/lib/python3/dist-packages/_libolm.abi3.so: undefined > > symbol: olm_account_fallback_key > > A simple test case is to run python3 -c "import olm". This renders > python3-olm unusable on stable Thanks for reporting this issue. Unfortunately I cannot reproduce using the simple command you provide last above. Did you test on a pristine system as well? I mean, perhaps you have some non-stable packages interfering? Kind regards, - Jonas -- * Jonas Smedegaard - idealist & Internet-arkitekt * Tlf.: +45 40843136 Website: http://dr.jones.dk/ [x] quote me freely [ ] ask before reusing [ ] keep private signature.asc Description: signature
Processed: Bug#996386 marked as pending in ruby-sham-rack
Processing control commands: > tag -1 pending Bug #996386 [src:ruby-sham-rack] ruby-sham-rack: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed: cannot load such file -- webrick/httputils Added tag(s) pending. -- 996386: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=996386 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Re: [Pkg-matrix-maintainers] Bug#999903: python3-olm: python import fails undefined symbol: olm_account_fallback_key
Processing control commands: > tags -1 +unreproducible +moreinfo Bug #03 [python3-olm] python3-olm: python import fails undefined symbol: olm_account_fallback_key Added tag(s) unreproducible. Bug #03 [python3-olm] python3-olm: python import fails undefined symbol: olm_account_fallback_key Added tag(s) moreinfo. > severity -1 important Bug #03 [python3-olm] python3-olm: python import fails undefined symbol: olm_account_fallback_key Severity set to 'important' from 'grave' -- 03: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=03 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#999862: marked as done (sso.debian.org: SSO no longer seems to work)
Your message dated Thu, 18 Nov 2021 09:45:32 + with message-id and subject line Re: Bug#999862: sso.debian.org: SSO no longer seems to work has caused the Debian Bug report #999862, regarding sso.debian.org: SSO no longer seems to work 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.) -- 999862: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=999862 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: sso.debian.org Severity: serious I'm trying to log in to tracker.debian.org. I've manually created a fresh certificate and loaded it into both Firefox (94.0-1) and Chrome (from Google), I visit tracker.debian.org but it does not recognise it at all. I also tried curl, as described on the wiki page https://wiki.debian.org/DebianSingleSignOn: curl --key $USER.key --cert $USER.crt https://sso.debian.org/ca/test/env but that fails too. So it would seem that sso.debian.org may no longer be functional, which prevents me from logging into tracker.debian.org. I don't know if this is a bug with tracker.debian.org or with sso.debian.org so I'm starting with sso.debian.org. I know the Wiki says that SSO is deprecated, but it doesn't say that it's stopped entirely! Best wishes, Julian --- End Message --- --- Begin Message --- On Thu, Nov 18, 2021 at 09:41:04AM +0800, Paul Wise wrote: > On Wed, 2021-11-17 at 20:55 +, Julian Gilbey wrote: > > > So it would seem that sso.debian.org may no longer be functional, > > which prevents me from logging into tracker.debian.org. > > My current certificate still works on tracker.d.o and the sso test URL. > > I created a new cert and imported it into my browser (Firefox ESR 91) > and it worked for the sso.d.o test site and for tracker.d.o. > > I wasn't able to get curl working with either the old or new certs. Whoops! I've figured out the problem - I was accidentally importing my old expired certificate. All works now. Thanks so much for your help, and sorry for the noise. Best wishes, Julian--- End Message ---
