Bug#966980: marked as done (mochiweb: FTBFS: beam/beam_load.c(1621): Error loading module rebar_utils: please re-compile this module with an 23 compiler (old-style fun with indices: 3/6))
Your message dated Sun, 05 Dec 2021 07:48:49 +
with message-id
and subject line Bug#966980: fixed in mochiweb 2.22.0-1
has caused the Debian Bug report #966980,
regarding mochiweb: FTBFS: beam/beam_load.c(1621): Error loading module
rebar_utils: please re-compile this module with an 23 compiler (old-style fun
with indices: 3/6)
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.)
--
966980: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=966980
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: mochiweb
Version: 2.20.1-1
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20200802 ftbfs-bullseye
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> Uncaught error in rebar_core: {'EXIT',
>{undef,
> [{rebar_utils,get_cwd,[],[]},
> {rebar_config,new,0,[]},
> {rebar,init_config,1,[]},
> {rebar,run,1,[]},
> {rebar,main,1,[]},
> {escript,run,2,
> [{file,"escript.erl"},{line,758}]},
> {escript,start,1,
> [{file,"escript.erl"},{line,277}]},
> {init,start_em,1,[]}]}}
> =ERROR REPORT 2-Aug-2020::17:24:44.255351 ===
> beam/beam_load.c(1621): Error loading module rebar_utils:
> please re-compile this module with an 23 compiler (old-style fun with
> indices: 3/6)
>
>
> =ERROR REPORT 2-Aug-2020::17:24:44.255398 ===
> Loading of /<>/rebar/rebar/ebin/rebar_utils.beam failed: badfile
>
> =ERROR REPORT 2-Aug-2020::17:24:44.272719 ===
> beam/beam_load.c(1621): Error loading module rebar_utils:
> please re-compile this module with an 23 compiler (old-style fun with
> indices: 3/6)
>
>
> =ERROR REPORT 2-Aug-2020::17:24:44.272756 ===
> Loading of /<>/rebar/rebar/ebin/rebar_utils.beam failed: badfile
>
> escript: exception error: undefined function rebar_utils:delayed_halt/1
> in function escript:run/2 (escript.erl, line 758)
> in call from escript:start/1 (escript.erl, line 277)
> in call from init:start_em/1
> in call from init:do_boot/3
> make[1]: *** [Makefile:20: clean] Error 127
The full build log is available from:
http://qa-logs.debian.net/2020/08/02/mochiweb_2.20.1-1_unstable.log
A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!
About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.
--- End Message ---
--- Begin Message ---
Source: mochiweb
Source-Version: 2.22.0-1
Done: Laszlo Boszormenyi (GCS)
We believe that the bug you reported is fixed in the latest version of
mochiweb, 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 966...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Laszlo Boszormenyi (GCS) (supplier of updated mochiweb
package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Sun, 05 Dec 2021 08:28:38 +0100
Source: mochiweb
Architecture: source
Version: 2.22.0-1
Distribution: unstable
Urgency: medium
Maintainer: Laszlo Boszormenyi (GCS)
Changed-By: Laszlo Boszormenyi (GCS)
Closes: 966980
Changes:
mochiweb (2.22.0-1) unstable; urgency=medium
.
* New upstream release (closes: #966980).
* Update watch file.
* Update debhelper level to 13 .
* Update Standards-Version to 4.6.0 .
Checksums-Sha1:
605d152a5066da448aa90489ba6f76411382cb80 1832 mochiweb_2.22.0-1.dsc
4a962b995d36ad58de7cd4a3153a849bc3fb918f 337500 mochiweb_2.22.0.orig.tar.gz
8c7d1015210c6553cab89e6ec6441a3e969e6a9f 2452 mochiweb_2.22.0-1.debian.tar.xz
Checksums-Sha256:
adacc29781099930ba3224eb60586cc57c3cb98649454a7e622d18519557b3d6 1832
Bug#995387: in package dpkg marked as pending
Control: tag 995387 pending Hi! Bug #995387 in package dpkg reported by you has been fixed in the dpkg/dpkg.git Git repository. You can see the changelog below, and you can check the diff of the fix at: https://git.dpkg.org/cgit/dpkg/dpkg.git/diff/?id=20e181fc2 --- dpkg: Fix conffile removal-on-upgrade handling We need to check for file conflicts during conffile removal, otherwise we might end up removing files from any other packages that has started owning them since we targeted the pathname for removal. We remove the conffiles during upgrade, as configure is a local action that does not load all file lists files, so we cannot check for file conflicts. Closes: #995387 Stable-Candidate: 1.20.x
Processed: Bug#995387 in package dpkg marked as pending
Processing control commands: > tag 995387 pending Bug #995387 [dpkg] dpkg: remove-on-upgrade deletes symlink targets owned by another package Added tag(s) pending. -- 995387: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=995387 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#997547: golang-github-alecaivazis-survey: FTBFS: dh_auto_test: error: cd _build && go test -vet=off -v -p 4 github.com/AlecAivazis/survey github.com/AlecAivazis/survey/core github.com/AlecAivazis/
Hi, Lucas Nussbaum (2021-10-23): > During a rebuild of all packages in sid, your package failed to build > on amd64. > > > Relevant part (hopefully): > > dpkg-buildpackage > > - > > > > dh_auto_test: error: cd _build && go test -vet=off -v -p 4 > > github.com/AlecAivazis/survey github.com/AlecAivazis/survey/core > > github.com/AlecAivazis/survey/terminal returned exit code 1 That's an odd one… I can reproduce the timeout issue, see vi started with files that aren't written on disk, and the test suite bail out after 10 minutes, but only in my usual unstable-amd64-devel chroot (entered via schroot). I couldn't confirm with a direct debootstrap + chroot + build-dep + build sequence; I couldn't confirm with either cowbuilder or sbuild, starting from fresh, clean unstable build environments. In some cases, I'm running into: --- FAIL: TestMultiSelectPrompt (0.00s) … --- FAIL: TestMultiSelectPrompt/delete_filter_word_in_rune (0.01s) but I'm not seeing the timeout issues there. I'll keep working on this. Cheers, -- Cyril Brulebois -- Debian Consultant @ DEBAMAX -- https://debamax.com/ signature.asc Description: PGP signature
Bug#994119: marked as done (vdirsyncer: Random cannot import name 'metasync' with python3.9)
Your message dated Sun, 05 Dec 2021 04:18:32 + with message-id and subject line Bug#994119: fixed in vdirsyncer 0.18.0-1 has caused the Debian Bug report #994119, regarding vdirsyncer: Random cannot import name 'metasync' with python3.9 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.) -- 994119: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=994119 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: vdirsyncer Version: 0.16.8-2 Severity: grave Dear Maintainer, I've made an update to Debian 11 and after the update I tried to use "vdirsyncer metasync" with my old configuration. While trying I got the following error message: error: Unknown error occurred: cannot import name 'metasync' from partially initialized module 'vdirsyncer.metasync' (most likely due to a circular import) (/usr/lib/python3/dist-packages/vdirsyncer/metasync.py) Every time I execute the command the result which tasks fail is different. While searching I found a GitHub issue that has the same problem as topic. -> https://github.com/pimutils/vdirsyncer/issues/862 Unfortunately, this error means that I cannot use the program. I hope this bug is easy to fix. Regards, Benedikt -- System Information: Debian Release: 11.0 APT prefers stable-security APT policy: (500, 'stable-security'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 5.10.0-8-amd64 (SMP w/8 CPU threads) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages vdirsyncer depends on: ii init-system-helpers1.60 ii python33.9.2-3 ii python3-atomicwrites 1.4.0-2 ii python3-click 7.1.2-1 ii python3-click-log 0.2.1-2 ii python3-click-threading0.4.4-2 ii python3-requests 2.25.1+dfsg-2 ii python3-requests-toolbelt 0.9.1-1 vdirsyncer recommends no packages. Versions of packages vdirsyncer suggests: pn python3-requests-oauthlib pn vdirsyncer-doc -- no debconf information signature.asc Description: PGP signature --- End Message --- --- Begin Message --- Source: vdirsyncer Source-Version: 0.18.0-1 Done: Jonas Smedegaard We believe that the bug you reported is fixed in the latest version of vdirsyncer, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 994...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Jonas Smedegaard (supplier of updated vdirsyncer package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sun, 05 Dec 2021 04:00:56 +0100 Source: vdirsyncer Architecture: source Version: 0.18.0-1 Distribution: unstable Urgency: medium Maintainer: Debian Python Team Changed-By: Jonas Smedegaard Closes: 994119 997497 Changes: vdirsyncer (0.18.0-1) unstable; urgency=medium . [ upstream ] * new release + several improvements to testsuite; closes: bug#994119, #997497, thanks to Benedikt Tuchen and Lucas Nussbaum . [ Jonas Smedegaard ] * add myself as uploader * update git-buildpackage config: + enable pristine-tar + enable signed tags + filter-out any .git* file + use DEP14 branches debian/latest and upstream/latest * update watch file: + track Github source + mangle upstream prerelease versions + add usage comment * drop patches 1 4 5 8, seemingly obsoleted by upstream testsuite improvements * drop patches 6 7, adopted upstream * tighten, update and renumber remaining patches, and add debian/patches/README file documenting patch numbering micro-policy * add source helper script copyright-check * update copyright info: + update coverage + license my contributions as GPL-3+ + add related lintian overrides * add patch 2002 to relax dependency on Python module click-log * tighten build-dependencies on python3-click python3-click-threading python3-requests * declare compliance with
Bug#997497: marked as done (vdirsyncer: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p 3.9 returned exit code 13)
Your message dated Sun, 05 Dec 2021 04:18:32 +
with message-id
and subject line Bug#997497: fixed in vdirsyncer 0.18.0-1
has caused the Debian Bug report #997497,
regarding vdirsyncer: FTBFS: dh_auto_test: error: pybuild --test --test-pytest
-i python{version} -p 3.9 returned exit code 13
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
997497: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997497
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: vdirsyncer
Version: 0.16.8-3
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):
> make[1]: Entering directory '/<>'
> LC_ALL=C.UTF-8 \
> DETERMINISTIC_TESTS=false \
> CI=false \
> REMOTESTORAGE_SERVER=skip \
> DAV_SERVER=skip \
> RADICALE_BACNEND=filesystem \
> dh_auto_test
> I: pybuild base:232: cd
> /<>/.pybuild/cpython3_3.9_vdirsyncer/build; python3.9 -m pytest
> tests
> = test session starts
> ==
> platform linux -- Python 3.9.7, pytest-6.2.5, py-1.10.0, pluggy-0.13.0
> rootdir: /<>, configfile: setup.cfg
> plugins: hypothesis-5.43.3, localserver-0.5.0
> collected 483 items
>
> tests/storage/test_filesystem.py ... [
> 8%]
> ...sss..ss...[
> 13%]
> tests/storage/test_http.py . [
> 14%]
> tests/storage/test_http_with_singlefile.py . [
> 20%]
> .ssss.ss [
> 26%]
> tests/storage/test_memory.py ..s [
> 34%]
> sssss...ss [
> 37%]
> tests/storage/test_singlefile.py ... [
> 45%]
> .ss.ss [
> 49%]
> tests/storage/dav/test_caldav.py sss [
> 57%]
> sss [
> 60%]
> tests/storage/dav/test_carddav.py ss [
> 66%]
> tests/storage/dav/test_main.py . [
> 73%]
> tests/system/cli/test_config.py .[
> 74%]
> tests/system/cli/test_discover.py F [
> 75%]
> tests/system/cli/test_fetchparams.py F [
> 76%]
> tests/system/cli/test_repair.py .[
> 77%]
> tests/system/cli/test_sync.py . [
> 80%]
> tests/system/cli/test_utils.py ..[
> 81%]
> tests/system/utils/test_main.py .sss.[
> 82%]
> tests/unit/test_exceptions.py . [
> 82%]
> tests/unit/test_metasync.py .[
> 84%]
> tests/unit/test_repair.py .. [
> 86%]
> tests/unit/cli/test_config.py . [
> 86%]
> tests/unit/cli/test_discover.py .. [
> 87%]
> tests/unit/cli/test_fetchparams.py . [
> 89%]
> tests/unit/sync/test_status.py . [
> 89%]
> tests/unit/sync/test_sync.py ... [
> 96%]
> tests/unit/utils/test_vobject.py ..
> [100%]
>
> === FAILURES
> ===
> test_discover_command
> _
> tests/system/cli/test_discover.py:38: in test_discover_command
> assert not result.exception
> E assert not SystemExit(1)
> E+ where SystemExit(1) = .exception
> ___ test_discover_different_collection_names
> ___
> tests/system/cli/test_discover.py:91: in
> test_discover_different_collection_names
> assert not result.exception
> E assert not SystemExit(1)
> E+ where SystemExit(1) = .exception
> __ test_discover_direct_path
> ___
> tests/system/cli/test_discover.py:134: in test_discover_direct_path
> assert not
Processed: Bug#998509 marked as pending in ruby-rspec-puppet
Processing control commands: > tag -1 pending Bug #998509 [src:ruby-rspec-puppet] ruby-rspec-puppet: FTBFS: ERROR: Test "ruby3.0" failed: cannot load such file -- libfacter.so Added tag(s) pending. -- 998509: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=998509 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#998509: marked as pending in ruby-rspec-puppet
Control: tag -1 pending Hello, Bug #998509 in ruby-rspec-puppet 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-rspec-puppet/-/commit/81b88ac3fe3a6232dfdfcd6c7ac59703dd045580 Add patch to fix Ruby 3.0 compatbility * d/patches/Add-Ruby-3.0-support.patch: Add patch. - Fix keyword argument issue (closes: #998509). * d/patches/series: Add new patch. (this message was generated automatically) -- Greetings https://bugs.debian.org/998509
Bug#1001136: openvdb binary-any FTBFS: help2man: can't get `--help' info from ./debian/tmp/usr/bin/vdb_view
Source: openvdb Version: 9.0.0-3 Severity: serious Tags: ftbfs https://buildd.debian.org/status/logs.php?pkg=openvdb=9.0.0-3 ... debian/rules override_dh_install-arch make[1]: Entering directory '/<>' LD_PRELOAD= LD_LIBRARY_PATH=./debian/tmp/usr/lib/x86_64-linux-gnu help2man --version-string=9.0.0 --include=debian/vdb_print.1.in --output=debian/vdb_print.1 --no-info --no-discard-stderr ./debian/tmp/usr/bin/vdb_print LD_PRELOAD= LD_LIBRARY_PATH=./debian/tmp/usr/lib/x86_64-linux-gnu help2man --version-string=9.0.0 --include=debian/vdb_view.1.in --output=debian/vdb_view.1 --no-info --no-discard-stderr ./debian/tmp/usr/bin/vdb_view help2man: can't get `--help' info from ./debian/tmp/usr/bin/vdb_view make[1]: *** [debian/rules:132: debian/vdb_view.1] Error 255
Bug#1001097: marked as done (ksh93u+m_1.0.0~beta.1-2_all-buildd.changes REJECTED)
Your message dated Sun, 05 Dec 2021 03:19:12 + with message-id and subject line Bug#1001097: fixed in ksh93u+m 1.0.0~beta.1-3 has caused the Debian Bug report #1001097, regarding ksh93u+m_1.0.0~beta.1-2_all-buildd.changes REJECTED 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.) -- 1001097: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1001097 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: ksh93u+m Version: 1.0.0~beta.1-2 Severity: serious On 2021-12-03 18:48, Debian FTP Masters wrote: > > > Version check failed: > Your upload included the binary package ksh, version 20210511, for all, > however unstable already has version 20210511. > Uploads to unstable must have a higher version than present in unstable. > > Mapping sid to unstable. > > === > > Please feel free to respond to this email if you don't understand why > your files were rejected, or if you upload new files which address our > concerns. > > > --- End Message --- --- Begin Message --- Source: ksh93u+m Source-Version: 1.0.0~beta.1-3 Done: Anuradha Weeraman We believe that the bug you reported is fixed in the latest version of ksh93u+m, 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 1001...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Anuradha Weeraman (supplier of updated ksh93u+m package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sun, 05 Dec 2021 08:20:33 +0530 Source: ksh93u+m Architecture: source Version: 1.0.0~beta.1-3 Distribution: unstable Urgency: high Maintainer: Anuradha Weeraman Changed-By: Anuradha Weeraman Closes: 1001097 Changes: ksh93u+m (1.0.0~beta.1-3) unstable; urgency=high . * Bump up transitional package version (Closes: #1001097) Checksums-Sha1: 7b217ca2cc735e86671116817b28f09e90145726 1941 ksh93u+m_1.0.0~beta.1-3.dsc d3ee34dd5d01893ebc9c28141b4f285349e25438 14928 ksh93u+m_1.0.0~beta.1-3.debian.tar.xz 9ac288ddc2eb40efb5fed0b324192eda08282bcb 6362 ksh93u+m_1.0.0~beta.1-3_amd64.buildinfo Checksums-Sha256: 36a58ccbbf71b6b6ae56c80159b592f74598c7f4d9aa0816b763b7e470dcbe21 1941 ksh93u+m_1.0.0~beta.1-3.dsc 216b284f726747fe7f1391e5641d0d675e8c785ce597776686ab6765aceb5539 14928 ksh93u+m_1.0.0~beta.1-3.debian.tar.xz d57b11b80901d5dca8b052cee2fcaae07ef501201bd650856b184229a81f451b 6362 ksh93u+m_1.0.0~beta.1-3_amd64.buildinfo Files: c9efc0c7d0f830e5c38257168c176b5d 1941 shells optional ksh93u+m_1.0.0~beta.1-3.dsc 0408b01da1e630e8baa21e49603e2d14 14928 shells optional ksh93u+m_1.0.0~beta.1-3.debian.tar.xz 71483e5f81116ab0f7ee0055eb9b4320 6362 shells optional ksh93u+m_1.0.0~beta.1-3_amd64.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEE9WuPFOAUze9dBH/BY221odkYYP0FAmGsKoMACgkQY221odkY YP1tnw//dIwchSCkaf6dUxLVom9UsybWe5M3dtLxWvT2ycMPy2jbbGHmyoMlFJUn Q1fX/EtCvEf3uMcbaJRA9x4dF0i/Jc46MUdhAbd8PjN77jXdCf8iFcCgd/AFPKWQ q5+Z98RpR+UbgQKliRW4SLt8WciyD5tsMsamTW3UN7N9Qi4VJBOdyrNuiMsF5eJF TgKRqjdM4DOiz9x9Pfkb/j0I6GopBZtJX66mrMXgtO766fwpEwamopMYLlDn9Pph B15t2+OiZrlXgA/JdKSnvSbMg7Y1+4vWwnWKH30gFCsW8UZ3Niv2Nr4YE41RVAH2 JSKEZHSCEQcB2VWoOyn+vCoupfs8zM7bDhqNF9IeZwwynxvF62tz4CUBENjiUdbL uhoAAGb9vzqkVyBHSnzM6EsqSWfsSKT20ih+FJtFwpmJRAc9iz6iPMFydIhBFl/2 qLiigWSOnwv+Kqh3NQGf6WrFQAF3ag4o30Vcuge1OngvWyYLmFmMQPBefawYDkyJ AAEMZOa60ZDhXFxOPfoo73XCXs77xNYFbdYC6ULGbfcOJF0eRn8IsHX2Y8Erkn1h y5bB/4p9PoEWokQP1p0ESsXXB8Xya+uxezr278XblAUgQ6Ptc1BmE2G/qaupQ3CI Wohp8XNvlT39Ot8oZglWbXsqrw8oXa8vAV6MQMzmVl/zbwH18E8= =yvbC -END PGP SIGNATURE End Message ---
Bug#995212: chromium: Update to version 94.0.4606.61 (security-fixes)
On Sun, 24 Oct 2021 15:06:50 -0400 Andres Salomon wrote: > Stable (bullseye) still contains chromium 90, which has had many > security issues. Testing & unstable contain 93, and stable should really > be quickly updated via stable-security to at least chromium 93 (as its > already been packaged and proven to build) or ideally 95 (the latest > stable chromium release). > > > So what's happening with chromium in both sid and stable? I saw on d-release that it was removed from testing (#998676 and #998732), with a discussion about ending security support for it in stable. I'm willing to help out with chromium packaging if the problem is simply lack of time (or I could just as easily help with something like ungoogled-chromium, #939406, if the plan is to have that in debian instead). Either way, both as a user and a developer, it is really not great to have chromium in limbo. :(
Bug#1001129: marked as done (Ruby 3.0: puppet/util.rb:469:in `uri_encode': undefined method `escape' for URI:Module (NoMethodError))
Your message dated Sun, 05 Dec 2021 01:19:40 + with message-id and subject line Bug#1001129: fixed in puppet 5.5.22-2.1 has caused the Debian Bug report #1001129, regarding Ruby 3.0: puppet/util.rb:469:in `uri_encode': undefined method `escape' for URI:Module (NoMethodError) 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.) -- 1001129: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1001129 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: puppet Version: 5.5.22-2 Severity: serious -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 The version is not ruby 3.0 compatible: ruby3.0 -e "require 'puppet'" /usr/lib/ruby/vendor_ruby/puppet/util.rb:469:in `uri_encode': undefined method `escape' for URI:Module (NoMethodError) from /usr/lib/ruby/vendor_ruby/puppet/util.rb:337:in `path_to_uri' from /usr/lib/ruby/vendor_ruby/puppet/pops/model/ast.rb:4863:in `register_pcore_types' from /usr/lib/ruby/vendor_ruby/puppet/pops.rb:119:in `' from /usr/lib/ruby/vendor_ruby/puppet/pops.rb:1:in `' from :85:in `require' from :85:in `require' from /usr/lib/ruby/vendor_ruby/puppet/parser/compiler.rb:8:in `' from :85:in `require' from :85:in `require' from /usr/lib/ruby/vendor_ruby/puppet/parser.rb:6:in `' from :85:in `require' from :85:in `require' from /usr/lib/ruby/vendor_ruby/puppet.rb:302:in `' from :85:in `require' from :85:in `require' from -e:1:in `' I'm intending to do a quick NMU to fix this. Regards, Daniel - -- System Information: Debian Release: bookworm/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'testing-debug'), (500, 'stable-security'), (500, 'stable-debug'), (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.15.0-2-amd64 (SMP w/8 CPU threads) Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages puppet depends on: ii adduser 3.118 ii facter 3.14.12-1.1 ii hiera3.2.0-2.1 ii init-system-helpers 1.60 ii lsb-base 11.1.0 ii ruby 1:2.7.6 ii ruby-augeas 1:0.5.0-3+b9 ii ruby-deep-merge 1.1.1-1 ii ruby-shadow 2.5.0+gh-1+b1 Versions of packages puppet recommends: ii debconf-utils 1.5.79 ii lsb-release11.1.0 pn ruby-selinux Versions of packages puppet suggests: pn ruby-hocon pn ruby-rrd - -- no debconf information -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEvu1N7VVEpMA+KD3HS80FZ8KW0F0FAmGsALEACgkQS80FZ8KW 0F1nHQ/6AyVaWCMDdPHi0AyhhQZiEISZP0GYNqdrnD/LYF9SdZ2PRlXxQrQfJ7RI F226bh4sRgzY/pcgfeUmiizaDfCyKxtGrvyjPqOvnoFACDRHDJm/rhjybdsTDCF7 MnHCNjIEic6qoPBqQmG20W15pshRzxbnSojTrZ+4QpHicn7shGYe2EmEJW2ZD6J3 Wsf/YB0Ny7AXKjZzWBqz3TFbBWObo47LC7XiutuirmjM7xe5f+QB5VtGiBk4448f XgWIPU9LwyAS9uUYWbXd+jxSVZ/92YoR83KyfGTd861Gj042EFXvu/zHRYru+FGj zM/H2PoQRudDUVlsVX4LXjKdaPJWxYjqhFOYeESRh86paZJFTzCp2VFdCMnCjAyo y42hH4SFjYsZhysNyDjEMwwSBKjQguKKqkRCjdJ1PeFYWc8CEQwlgAZLtLGSFdPA d22BplnTtZHT3AEweXUNWDvjfmDjAgObe85u/p5YQgAYldrj5f0C9BoWHpJ02P5I 6pi2KzWDgApuVk8OEbMrgoxsKnGxaXKEGRqoYxYZe8MWvDRJ8vlwTgXqZk3Us0LB taAXdHCdzvQ3NxYT6JgWkOeBwcfKY14sVzPfeKE7vzB/Ib/HxqdR4qyAdkWqt2V0 ujonrXF3NDPL5ZAi2QIkb/7v42p3B1nc2PeJJ2z/SoIbq1nfqh8= =CMGz -END PGP SIGNATURE- --- End Message --- --- Begin Message --- Source: puppet Source-Version: 5.5.22-2.1 Done: Daniel Leidert We believe that the bug you reported is fixed in the latest version of puppet, 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 1001...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Daniel Leidert (supplier of updated puppet package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sun, 05 Dec 2021 00:53:02 +0100 Source: puppet Architecture: source Version:
Processed: block 998494 with 1001129
Processing commands for cont...@bugs.debian.org: > block 998494 with 1001129 Bug #998494 [src:ruby-puppetlabs-spec-helper] ruby-puppetlabs-spec-helper: FTBFS: ERROR: Test "ruby3.0" failed: cannot load such file -- libfacter.so 998494 was blocked by: 984082 998481 984116 998494 was not blocking any bugs. Added blocking bug(s) of 998494: 1001129 > thanks Stopping processing here. Please contact me if you need assistance. -- 998494: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=998494 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1001129: Ruby 3.0: puppet/util.rb:469:in `uri_encode': undefined method `escape' for URI:Module (NoMethodError)
Package: puppet Version: 5.5.22-2 Severity: serious -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 The version is not ruby 3.0 compatible: ruby3.0 -e "require 'puppet'" /usr/lib/ruby/vendor_ruby/puppet/util.rb:469:in `uri_encode': undefined method `escape' for URI:Module (NoMethodError) from /usr/lib/ruby/vendor_ruby/puppet/util.rb:337:in `path_to_uri' from /usr/lib/ruby/vendor_ruby/puppet/pops/model/ast.rb:4863:in `register_pcore_types' from /usr/lib/ruby/vendor_ruby/puppet/pops.rb:119:in `' from /usr/lib/ruby/vendor_ruby/puppet/pops.rb:1:in `' from :85:in `require' from :85:in `require' from /usr/lib/ruby/vendor_ruby/puppet/parser/compiler.rb:8:in `' from :85:in `require' from :85:in `require' from /usr/lib/ruby/vendor_ruby/puppet/parser.rb:6:in `' from :85:in `require' from :85:in `require' from /usr/lib/ruby/vendor_ruby/puppet.rb:302:in `' from :85:in `require' from :85:in `require' from -e:1:in `' I'm intending to do a quick NMU to fix this. Regards, Daniel - -- System Information: Debian Release: bookworm/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'testing-debug'), (500, 'stable-security'), (500, 'stable-debug'), (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.15.0-2-amd64 (SMP w/8 CPU threads) Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages puppet depends on: ii adduser 3.118 ii facter 3.14.12-1.1 ii hiera3.2.0-2.1 ii init-system-helpers 1.60 ii lsb-base 11.1.0 ii ruby 1:2.7.6 ii ruby-augeas 1:0.5.0-3+b9 ii ruby-deep-merge 1.1.1-1 ii ruby-shadow 2.5.0+gh-1+b1 Versions of packages puppet recommends: ii debconf-utils 1.5.79 ii lsb-release11.1.0 pn ruby-selinux Versions of packages puppet suggests: pn ruby-hocon pn ruby-rrd - -- no debconf information -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEvu1N7VVEpMA+KD3HS80FZ8KW0F0FAmGsALEACgkQS80FZ8KW 0F1nHQ/6AyVaWCMDdPHi0AyhhQZiEISZP0GYNqdrnD/LYF9SdZ2PRlXxQrQfJ7RI F226bh4sRgzY/pcgfeUmiizaDfCyKxtGrvyjPqOvnoFACDRHDJm/rhjybdsTDCF7 MnHCNjIEic6qoPBqQmG20W15pshRzxbnSojTrZ+4QpHicn7shGYe2EmEJW2ZD6J3 Wsf/YB0Ny7AXKjZzWBqz3TFbBWObo47LC7XiutuirmjM7xe5f+QB5VtGiBk4448f XgWIPU9LwyAS9uUYWbXd+jxSVZ/92YoR83KyfGTd861Gj042EFXvu/zHRYru+FGj zM/H2PoQRudDUVlsVX4LXjKdaPJWxYjqhFOYeESRh86paZJFTzCp2VFdCMnCjAyo y42hH4SFjYsZhysNyDjEMwwSBKjQguKKqkRCjdJ1PeFYWc8CEQwlgAZLtLGSFdPA d22BplnTtZHT3AEweXUNWDvjfmDjAgObe85u/p5YQgAYldrj5f0C9BoWHpJ02P5I 6pi2KzWDgApuVk8OEbMrgoxsKnGxaXKEGRqoYxYZe8MWvDRJ8vlwTgXqZk3Us0LB taAXdHCdzvQ3NxYT6JgWkOeBwcfKY14sVzPfeKE7vzB/Ib/HxqdR4qyAdkWqt2V0 ujonrXF3NDPL5ZAi2QIkb/7v42p3B1nc2PeJJ2z/SoIbq1nfqh8= =CMGz -END PGP SIGNATURE-
Bug#1000421: Bug#1000146: cppcheck: incorrect dependencies: libc6 should be >= 2.32
Hi! On Sat, 2021-12-04 at 23:09:19 +, Ian Jackson wrote: > Joachim: > > I'm aware of that. And "shortly" definitely means "before the > > autoremoval" (which is currently scheduled for 2022-01-01). > > The real deadline is when I ought to take action myself, as someone > adversely affected by an RC bug. Sorry for not having updated the report before, but I didn't see the urgency either, and was planning on dealing with it before this had any further effect. I'd have appreciated more a request for a status update, instead of wielding the NMU around though… > The timeline for fixing this is: > > NMU DELAYED-10 upload of fixed dpkg > wait 10 days > wait ?? days for dpkg to migrate, say 5 (I think there are tests) > NMU DELAYED-10 upload of no-change cppcheck > wait 10 dayhs > wait 10 days for cppcheck to migrate > > Total waiting time here is 35 days plus time I spend doing the work. There's another RC in dpkg, which I have a fix for, but had pending reviewing it again and checking whether some of the cases from the report are handled right. And then there are also autopkgtest failures which I've also got fixed locally. My intention is to get this uploaded this weekend. > If I want to fix this without having to manually restart the > autoremoval clock and/or ask for help from the release team, I should > have NMU'd dpkg at least a week ago. (Where either of these first options, if they would be required at all, seem like way less effort and way less disruptive anyway…) Regards, Guillem
Bug#998488: marked as done (facterdb: FTBFS: ERROR: Test "ruby3.0" failed: cannot load such file -- libfacter.so)
Your message dated Sat, 04 Dec 2021 23:49:40 + with message-id and subject line Bug#998488: fixed in facterdb 1.12.1-1 has caused the Debian Bug report #998488, regarding facterdb: FTBFS: ERROR: Test "ruby3.0" failed: cannot load such file -- libfacter.so 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.) -- 998488: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=998488 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: facterdb Version: 1.8.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): > cannot load such file -- libfacter.so > Did you mean? lib/facterdb > # ./lib/facterdb.rb:1:in `' > # ./spec/spec_helper.rb:12:in `' > # ./spec/facts_spec.rb:1:in `' > # -- > # --- Caused by: --- > # LoadError: > # cannot load such file -- libfacter.so > # Did you mean? lib/facterdb > # ./lib/facterdb.rb:1:in `' > No examples found. > > Finished in 0.5 seconds (files took 0.1256 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 from: http://qa-logs.debian.net/2021/11/04/facterdb_1.8.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: facterdb Source-Version: 1.12.1-1 Done: Daniel Leidert We believe that the bug you reported is fixed in the latest version of facterdb, 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. Daniel Leidert (supplier of updated facterdb package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sun, 05 Dec 2021 00:20:49 +0100 Source: facterdb Architecture: source Version: 1.12.1-1 Distribution: unstable Urgency: medium Maintainer: Debian Ruby Team Changed-By: Daniel Leidert Closes: 998488 Changes: facterdb (1.12.1-1) unstable; urgency=medium . * Team upload to rebuild with facter built for Ruby 3 (closes: #998488). * New upstream release. * d/clean: Add file and remove debian/tmp/. * d/control (Standards-Version): Bump to 4.6.0. (Homepage): Update URL. * d/copyright: Add Upstream-Contact field. (Source): Update URL. (Copyright): Update and add team. * d/facterdb.man.1.rst: Add file originally created by patch. * d/rules (DH_RUBY_GEM_INSTALL_BLACKLIST_APPEND): Replace by DH_RUBY_GEM_INSTALL_EXCLUDE and shorten list. (override_dh_installman): Adjust path to rst file. * d/watch: Update source. * d/patches/0003-add_man_page.patch: Remove patch. - We can ship the manual page in debian/. * d/patches/0005-Remove-git-from-gemspec.patch: Add patch. - Don't use git in gemspec to fix autopkgtest. * d/patches/series: Adjust file. * d/upstream/metadata: Update all URLs. Checksums-Sha1: 7d3ee85392644f11c770204f87cb13b2a39c85bb 2060 facterdb_1.12.1-1.dsc 933faf300bfef99391fbf59364136439116a466d 2214918 facterdb_1.12.1.orig.tar.gz a464328c52d51817c7b5ba22a7a94e660ebbc497 5012 facterdb_1.12.1-1.debian.tar.xz 92124105584ab5fc5ee35250c3df30613a587b79 10060 facterdb_1.12.1-1_amd64.buildinfo Checksums-Sha256: a54924d9c4b1f7c80915c4a0e445925ad1ee02b4986119054f3ebdd07c8b21cb 2060 facterdb_1.12.1-1.dsc
Bug#1001128: linux-image-5.15.0-2-amd64: Kernel crashes my GPU
Package: src:linux Version: 5.15.5-1 Severity: critical Tags: upstream Justification: breaks the whole system X-Debbugs-Cc: tipos...@tiscali.it Dear Maintainer, Basically the latest kernel has serious GPU issues. It takes several minutes to open sddm, and then the video is all broken and I can't login. Going to a tty takes minutes, but after I'm there everything looks ok. Restarting sddm it seems I can manage to login, but then the system again takes minutes to load plasma, and actually plasmoids randomly disappear, yakuake and krunner take minutes to appear, disappear randomly and so on. Basically my machine works fine under 5.14 but graphical session is completely unusable under 5.15. Let me know what extra information is needed, if any. Best -- Package-specific info: ** Kernel log: boot messages should be attached ** Model information sys_vendor: LENOVO product_name: 20W4008AMX product_version: ThinkPad T15 Gen 2i chassis_vendor: LENOVO chassis_version: None bios_vendor: LENOVO bios_version: N34ET42W (1.42 ) board_vendor: LENOVO board_name: 20W4008AMX board_version: SDK0J40697 WIN ** Network interface configuration: *** /etc/network/interfaces: source /etc/network/interfaces.d/* auto lo iface lo inet loopback ** PCI devices: 00:00.0 Host bridge [0600]: Intel Corporation 11th Gen Core Processor Host Bridge/DRAM Registers [8086:9a14] (rev 01) Subsystem: Lenovo 11th Gen Core Processor Host Bridge/DRAM Registers [17aa:22c9] Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- 00:02.0 VGA compatible controller [0300]: Intel Corporation TigerLake-LP GT2 [Iris Xe Graphics] [8086:9a49] (rev 01) (prog-if 00 [VGA controller]) Subsystem: Lenovo TigerLake-LP GT2 [Iris Xe Graphics] [17aa:22c9] Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- Kernel driver in use: i915 Kernel modules: i915 00:04.0 Signal processing controller [1180]: Intel Corporation TigerLake-LP Dynamic Tuning Processor Participant [8086:9a03] (rev 01) Subsystem: Lenovo TigerLake-LP Dynamic Tuning Processor Participant [17aa:22c9] Control: I/O- Mem+ BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- Kernel driver in use: proc_thermal Kernel modules: processor_thermal_device_pci_legacy 00:06.0 PCI bridge [0604]: Intel Corporation 11th Gen Core Processor PCIe Controller [8086:9a09] (rev 01) (prog-if 00 [Normal decode]) Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- Reset- FastB2B- PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn- Capabilities: Kernel driver in use: pcieport 00:07.0 PCI bridge [0604]: Intel Corporation Tiger Lake-LP Thunderbolt 4 PCI Express Root Port #1 [8086:9a25] (rev 01) (prog-if 00 [Normal decode]) Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- Reset- FastB2B- PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn- Capabilities: Kernel driver in use: pcieport 00:07.2 PCI bridge [0604]: Intel Corporation Tiger Lake-LP Thunderbolt 4 PCI Express Root Port #2 [8086:9a27] (rev 01) (prog-if 00 [Normal decode]) Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- Reset- FastB2B- PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn- Capabilities: Kernel driver in use: pcieport 00:0d.0 USB controller [0c03]: Intel Corporation Tiger Lake-LP Thunderbolt 4 USB Controller [8086:9a13] (rev 01) (prog-if 30 [XHCI]) Subsystem: Lenovo Tiger Lake-LP Thunderbolt 4 USB Controller [17aa:22c9] Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- SERR- Kernel driver in use: xhci_hcd Kernel modules: xhci_pci 00:0d.2 USB controller [0c03]: Intel Corporation Tiger Lake-LP Thunderbolt 4 NHI #0 [8086:9a1b] (rev 01) (prog-if 40 [USB4 Host Interface]) Subsystem: Lenovo Tiger Lake-LP Thunderbolt 4 NHI [17aa:22c9] Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR-
Processed: Re: Grub fails to find LVM volume after previous LV rename - control
Processing commands for cont...@bugs.debian.org: > forwarded 987008 https://savannah.gnu.org/bugs/index.php?61620 Bug #987008 [grub2] Grub fails to find LVM volume after previous LV rename Set Bug forwarded-to-address to 'https://savannah.gnu.org/bugs/index.php?61620'. > End of message, stopping processing here. Please contact me if you need assistance. -- 987008: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=987008 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1000146: cppcheck: incorrect dependencies: libc6 should be >= 2.32
Joachim: > I'm aware of that. And "shortly" definitely means "before the > autoremoval" (which is currently scheduled for 2022-01-01). The real deadline is when I ought to take action myself, as someone adversely affected by an RC bug. The timeline for fixing this is: NMU DELAYED-10 upload of fixed dpkg wait 10 days wait ?? days for dpkg to migrate, say 5 (I think there are tests) NMU DELAYED-10 upload of no-change cppcheck wait 10 dayhs wait 10 days for cppcheck to migrate Total waiting time here is 35 days plus time I spend doing the work. If I want to fix this without having to manually restart the autoremoval clock and/or ask for help from the release team, I should have NMU'd dpkg at least a week ago. Ian. -- 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): Re: Grub fails to find LVM volume after previous LV rename - control
Processing commands for cont...@bugs.debian.org: > tags 987008 upstream Bug #987008 [grub2] Grub fails to find LVM volume after previous LV rename Added tag(s) upstream. > found 987008 2.06-2 Bug #987008 [grub2] Grub fails to find LVM volume after previous LV rename Marked as found in versions grub2/2.06-2. > forwarded 987008 Unknown command or malformed arguments to command. > https://savannah.gnu.org/bugs/index.p Unknown command or malformed arguments to command. > hp?61620 Unknown command or malformed arguments to command. > End of message, stopping processing here. Please contact me if you need assistance. -- 987008: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=987008 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#987008: Info received (Grub fails to find LVM volume after previous LV rename)
As this problem exists upstream, I have submitted an upstream bug report. https://savannah.gnu.org/bugs/index.p hp?61620
Bug#1000797: marked as done (vdeplug4: Provides the same binary package as another source package)
Your message dated Sat, 04 Dec 2021 21:53:03 + with message-id and subject line Bug#1000798: fixed in vde2 2.3.2+r586-8 has caused the Debian Bug report #1000798, regarding vdeplug4: Provides the same binary package as another source 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.) -- 1000798: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1000798 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: vdeplug4 Severity: serious The binary package libvdeplug2 is built by both source packages vde2 and vdeplug4. This violates Debian Policy. Thanks, Jeremy Bicha --- End Message --- --- Begin Message --- Source: vde2 Source-Version: 2.3.2+r586-8 Done: Renzo Davoli We believe that the bug you reported is fixed in the latest version of vde2, 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 1000...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Renzo Davoli (supplier of updated vde2 package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sat, 04 Dec 2021 16:21:27 +0100 Source: vde2 Architecture: source Version: 2.3.2+r586-8 Distribution: unstable Urgency: medium Maintainer: Debian VSquare Team Changed-By: Renzo Davoli Closes: 1000798 Changes: vde2 (2.3.2+r586-8) unstable; urgency=medium . * do not generate vdeplug, libvdeplug* packages (Closes: #1000798) vdeplug4 provides new versions of these packages Checksums-Sha1: 064e06ba2da138f6d13896af416b870bc2ea0d9b 2091 vde2_2.3.2+r586-8.dsc c44243e853e532287f276385cab15d94cc93512f 2419636 vde2_2.3.2+r586-8.tar.gz 61b71d9392d97c0dd7f86d70338663fe99e13181 8973 vde2_2.3.2+r586-8_amd64.buildinfo Checksums-Sha256: abdd88724b52378675f3aa637a5819ad162b4f2192ca339f1a06751fb3d2683c 2091 vde2_2.3.2+r586-8.dsc 5fabc4a07adc86ea12665faaa7602acc1e03d470e490283d52534836c913 2419636 vde2_2.3.2+r586-8.tar.gz 4d44430788d519b14af5e1114f69dfa0991c719ebb43b6a9cb90655cd18e7362 8973 vde2_2.3.2+r586-8_amd64.buildinfo Files: ed2ffe111d45a7655c014c84dc229f9d 2091 net optional vde2_2.3.2+r586-8.dsc b795ec4b1210071554280d26c33a9a9f 2419636 net optional vde2_2.3.2+r586-8.tar.gz bb3466486deeae8717688d6c4b169293 8973 net optional vde2_2.3.2+r586-8_amd64.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEi3hoeGwz5cZMTQpICBa54Yx2K60FAmGr28cACgkQCBa54Yx2 K62K6w/7BHje+6t+TkQ1iyvi0Phw8aUyBYuwpE2QUIiiYMweMu2Jy9B8i9280nuV mRjXLbRfl00iTZKTZBpqKpCHtkD+nz2o4CwO3DYzwJcpZgpZRFmaIiQM4R1hIg4I RUBuSIVKV9wRvyfQ05wf1LlZ2YLk21y4cuWradoFyuIHlwNxUHU0mJdWttHy9YNQ dRl9XnLUBx1gjhaY3CfcsFZinmSPggOqfID1m77XSZWWWCeNHz2Xste2RbozdOE2 GbeGEUNji3vwWB6ztqtgSzD/kDkruYIhV1VmptRmK4kFeBTabVNH7hRoXV45Jazw PG7sog63O/wMsQz6ka4KirhGXh9jmyXWPnuCwZ6gjtdRZKaHnn/QQVQC4i09FkER azUOA+HPXDGYu9zPJycbCFWum5k60sdCckZh5qE4vE4YvXQyP0g7j79L0svAva7y +lvoYRpN/nawkdIi3m9G2v0Y0dUySeBXfJ+OYTpO+2AFxCzOK4RwGnu7UAaDUom5 RZaCWQqBpuXos4+X8KnZvZKPi+hsX1Sj+cK+jLokBNbK4amSxX/Dd4cMa7YN/2G1 vkNMb2o0qeSqTobmOFl/TwKKf9fTVuWuXcSFrD1f00vyf+GuRRSX8PjaLwD1zI4D d7+OL7UVk0Dvgj4YTW9miDvVKYvsalxSQSsqecCKGwnPQ+9UbiA= =b6L/ -END PGP SIGNATURE End Message ---
Bug#1000798: marked as done (vde2: Provides the same binary package as another source package)
Your message dated Sat, 04 Dec 2021 21:53:03 + with message-id and subject line Bug#1000798: fixed in vde2 2.3.2+r586-8 has caused the Debian Bug report #1000798, regarding vde2: Provides the same binary package as another source 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.) -- 1000798: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1000798 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: vde2 Severity: serious The binary package libvdeplug2 is built by both source packages vde2 and vdeplug4. This violates Debian Policy. Thanks, Jeremy Bicha --- End Message --- --- Begin Message --- Source: vde2 Source-Version: 2.3.2+r586-8 Done: Renzo Davoli We believe that the bug you reported is fixed in the latest version of vde2, 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 1000...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Renzo Davoli (supplier of updated vde2 package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sat, 04 Dec 2021 16:21:27 +0100 Source: vde2 Architecture: source Version: 2.3.2+r586-8 Distribution: unstable Urgency: medium Maintainer: Debian VSquare Team Changed-By: Renzo Davoli Closes: 1000798 Changes: vde2 (2.3.2+r586-8) unstable; urgency=medium . * do not generate vdeplug, libvdeplug* packages (Closes: #1000798) vdeplug4 provides new versions of these packages Checksums-Sha1: 064e06ba2da138f6d13896af416b870bc2ea0d9b 2091 vde2_2.3.2+r586-8.dsc c44243e853e532287f276385cab15d94cc93512f 2419636 vde2_2.3.2+r586-8.tar.gz 61b71d9392d97c0dd7f86d70338663fe99e13181 8973 vde2_2.3.2+r586-8_amd64.buildinfo Checksums-Sha256: abdd88724b52378675f3aa637a5819ad162b4f2192ca339f1a06751fb3d2683c 2091 vde2_2.3.2+r586-8.dsc 5fabc4a07adc86ea12665faaa7602acc1e03d470e490283d52534836c913 2419636 vde2_2.3.2+r586-8.tar.gz 4d44430788d519b14af5e1114f69dfa0991c719ebb43b6a9cb90655cd18e7362 8973 vde2_2.3.2+r586-8_amd64.buildinfo Files: ed2ffe111d45a7655c014c84dc229f9d 2091 net optional vde2_2.3.2+r586-8.dsc b795ec4b1210071554280d26c33a9a9f 2419636 net optional vde2_2.3.2+r586-8.tar.gz bb3466486deeae8717688d6c4b169293 8973 net optional vde2_2.3.2+r586-8_amd64.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEi3hoeGwz5cZMTQpICBa54Yx2K60FAmGr28cACgkQCBa54Yx2 K62K6w/7BHje+6t+TkQ1iyvi0Phw8aUyBYuwpE2QUIiiYMweMu2Jy9B8i9280nuV mRjXLbRfl00iTZKTZBpqKpCHtkD+nz2o4CwO3DYzwJcpZgpZRFmaIiQM4R1hIg4I RUBuSIVKV9wRvyfQ05wf1LlZ2YLk21y4cuWradoFyuIHlwNxUHU0mJdWttHy9YNQ dRl9XnLUBx1gjhaY3CfcsFZinmSPggOqfID1m77XSZWWWCeNHz2Xste2RbozdOE2 GbeGEUNji3vwWB6ztqtgSzD/kDkruYIhV1VmptRmK4kFeBTabVNH7hRoXV45Jazw PG7sog63O/wMsQz6ka4KirhGXh9jmyXWPnuCwZ6gjtdRZKaHnn/QQVQC4i09FkER azUOA+HPXDGYu9zPJycbCFWum5k60sdCckZh5qE4vE4YvXQyP0g7j79L0svAva7y +lvoYRpN/nawkdIi3m9G2v0Y0dUySeBXfJ+OYTpO+2AFxCzOK4RwGnu7UAaDUom5 RZaCWQqBpuXos4+X8KnZvZKPi+hsX1Sj+cK+jLokBNbK4amSxX/Dd4cMa7YN/2G1 vkNMb2o0qeSqTobmOFl/TwKKf9fTVuWuXcSFrD1f00vyf+GuRRSX8PjaLwD1zI4D d7+OL7UVk0Dvgj4YTW9miDvVKYvsalxSQSsqecCKGwnPQ+9UbiA= =b6L/ -END PGP SIGNATURE End Message ---
Bug#1001001: linux-image-5.10.0-9-arm64: kernel BUG at include/linux/swapops.h:204!
Hi, On Thu, 02 Dec 2021 13:44:15 +0100 Paul Gevers wrote: The last couple of days, two of the ci.debian.net arm64 workers became unresponsive. The systems were rebooted and I found the message in the journal pasted below. Please let me know if you need more info about these systems. As requested by carnil on IRC, let me try to add some things I checked. In contrast to the previous kernel bug I reported, this time the two machines that hang were testing different packages (syslog-ng being one of them) that succeed often on arm64. I noticed in the logs that *after* the reported kernel bug but before the actual hang, I see multiple instances of: watchdog: BUG: soft lockup - CPU#1 stuck for 22s! [apt-get:2204621] and watchdog: BUG: soft lockup - CPU#2 stuck for 22s! [kcompactd0:40] on ci-worker-arm64-07. The other system (ci-worker-arm64-02) has watchdog: BUG: soft lockup - CPU#2 stuck for 23s! [khugepaged:42] and watchdog: BUG: soft lockup - CPU#3 stuck for 22s! [apt-get:4191233] I found a third system that had to be rebooted recently (ci-worker-arm64-08 on 18 November): watchdog: BUG: soft lockup - CPU#1 stuck for 23s! [apt-get:3325970] and watchdog: BUG: soft lockup - CPU#3 stuck for 23s! [python3:3275229] Although the journal is lost by now, we had more arm64 VM's hang; ci-worker-arm64-03 on 6 November 2021 Probably worth to mention, albeit hopefully unrelated, we had issues in the recent past (ci-worker-arm64-06 on 29 October 2021) with virtio_gpu so we blocked that module on all our workers from loading as we believe we don't need it. [drm:virtio_gpu_dequeue_ctrl_func [virtio_gpu]] *ERROR* response 0x1202 (command 0x103) Paul OpenPGP_signature Description: OpenPGP digital signature
Bug#1001120: src:pyaxmlparser: fails to migrate to testing for too long: uploader built arch:all binaries
Hi On 04-12-2021 20:55, Andres Salomon wrote: Please cancel that upload, I will do a new upload. Done. Paul OpenPGP_signature Description: OpenPGP digital signature
Bug#998008: marked as pending in glibc
Control: tag -1 pending Hello, Bug #998008 in glibc 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/glibc-team/glibc/-/commit/f0b32b609c442083a8af7099ca58fbd74b77befe debian/debhelper.in/libc-bin.postinst: stop replacing older versions from /etc/nsswitch.conf. Closes: #998008. (this message was generated automatically) -- Greetings https://bugs.debian.org/998008
Processed: Bug#998008 marked as pending in glibc
Processing control commands: > tag -1 pending Bug #998008 [libc-bin] libc-bin: postinst makes a working NIS system not to work anymore at every point release Added tag(s) pending. -- 998008: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=998008 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1001122: src:growlight: fails to migrate to testing for too long: autopkgtest regression
Hi Nick On 04-12-2021 21:29, nick black wrote: Thanks. I actually just cut growlight 1.2.38 literally forty minutes ago, and have prepared it for upload. Great timing. :) Unfortunately, it's dependent on the new libnotcurses3, which needs to get through NEW. I'm not yet a DD, so I'm hoping my Application Manager will be willing to sponsor an upload of notcurses 3.0.0 to NEW. Once it gets there, I'll upload the new growlight as part of the library transition. You don't need to wait with uploading growlight. It will just wait with building until the right version notcurses is available. I think this all ought happen within 30 days, but feel free to ping. Feel free to ping this bug to reset the removal timer while waiting for notcurses to pass NEW. Paul OpenPGP_signature Description: OpenPGP digital signature
Bug#1001122: src:growlight: fails to migrate to testing for too long: autopkgtest regression
Thanks. I actually just cut growlight 1.2.38 literally forty minutes ago, and have prepared it for upload. Unfortunately, it's dependent on the new libnotcurses3, which needs to get through NEW. I'm not yet a DD, so I'm hoping my Application Manager will be willing to sponsor an upload of notcurses 3.0.0 to NEW. Once it gets there, I'll upload the new growlight as part of the library transition. I think this all ought happen within 30 days, but feel free to ping. signature.asc Description: PGP signature
Bug#1001122: src:growlight: fails to migrate to testing for too long: autopkgtest regression
Source: growlight Version: 1.2.35-1 Severity: serious Control: close -1 1.2.37-2 Tags: sid bookworm User: release.debian@packages.debian.org Usertags: out-of-sync Control: block -1 by 997845 Dear maintainer(s), The Release Team considers packages that are out-of-sync between testing and unstable for more than 60 days as having a Release Critical bug in testing [1]. Your package src:growlight has been trying to migrate for 61 days [2]. Hence, I am filing this bug. The package fails its autopkgtest. If a package is out of sync between unstable and testing for a longer period, this usually means that bugs in the package in testing cannot be fixed via unstable. Additionally, blocked packages can have impact on other packages, which makes preparing for the release more difficult. Finally, it often exposes issues with the package and/or its (reverse-)dependencies. We expect maintainers to fix issues that hamper the migration of their package in a timely manner. This bug will trigger auto-removal when appropriate. As with all new bugs, there will be at least 30 days before the package is auto-removed. I have immediately closed this bug with the version in unstable, so if that version or a later version migrates, this bug will no longer affect testing. I have also tagged this bug to only affect sid and bookworm, so it doesn't affect (old-)stable. If you believe your package is unable to migrate to testing due to issues beyond your control, don't hesitate to contact the Release Team. Paul [1] https://lists.debian.org/debian-devel-announce/2020/02/msg5.html [2] https://qa.debian.org/excuses.php?package=growlight OpenPGP_signature Description: OpenPGP digital signature
Processed: src:growlight: fails to migrate to testing for too long: autopkgtest regression
Processing control commands:
> close -1 1.2.37-2
Bug #1001122 [src:growlight] src:growlight: fails to migrate to testing for too
long: autopkgtest regression
Marked as fixed in versions growlight/1.2.37-2.
Bug #1001122 [src:growlight] src:growlight: fails to migrate to testing for too
long: autopkgtest regression
Marked Bug as done
> block -1 by 997845
Bug #1001122 {Done: Paul Gevers } [src:growlight]
src:growlight: fails to migrate to testing for too long: autopkgtest regression
1001122 was not blocked by any bugs.
1001122 was not blocking any bugs.
Added blocking bug(s) of 1001122: 997845
--
1001122: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1001122
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Processed: src:httpbin: fails to migrate to testing for too long: autopkgtest failures
Processing control commands: > close -1 0.7.0+dfsg-1 Bug #1001121 [src:httpbin] src:httpbin: fails to migrate to testing for too long: autopkgtest failures Marked as fixed in versions httpbin/0.7.0+dfsg-1. Bug #1001121 [src:httpbin] src:httpbin: fails to migrate to testing for too long: autopkgtest failures Marked Bug as done -- 1001121: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1001121 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1001121: src:httpbin: fails to migrate to testing for too long: autopkgtest failures
Source: httpbin Version: 0.5.0+dfsg-4 Severity: serious Control: close -1 0.7.0+dfsg-1 Tags: sid bookworm X-Debbugs-CC: a...@debian.org User: release.debian@packages.debian.org Usertags: out-of-sync Dear maintainer(s), The Release Team considers packages that are out-of-sync between testing and unstable for more than 60 days as having a Release Critical bug in testing [1]. Your package src:httpbin has been trying to migrate for 61 days [2]. Hence, I am filing this bug. The newly added autopkgtest fails. If a package is out of sync between unstable and testing for a longer period, this usually means that bugs in the package in testing cannot be fixed via unstable. Additionally, blocked packages can have impact on other packages, which makes preparing for the release more difficult. Finally, it often exposes issues with the package and/or its (reverse-)dependencies. We expect maintainers to fix issues that hamper the migration of their package in a timely manner. This bug will trigger auto-removal when appropriate. As with all new bugs, there will be at least 30 days before the package is auto-removed. I have immediately closed this bug with the version in unstable, so if that version or a later version migrates, this bug will no longer affect testing. I have also tagged this bug to only affect sid and bookworm, so it doesn't affect (old-)stable. If you believe your package is unable to migrate to testing due to issues beyond your control, don't hesitate to contact the Release Team. Paul [1] https://lists.debian.org/debian-devel-announce/2020/02/msg5.html [2] https://qa.debian.org/excuses.php?package=httpbin OpenPGP_signature Description: OpenPGP digital signature
Bug#1001120: src:pyaxmlparser: fails to migrate to testing for too long: uploader built arch:all binaries
On 12/4/21 2:51 PM, Paul Gevers wrote: Source: pyaxmlparser Version: 0.3.24-1 [...] Your package is only blocked because the arch:all binary package(s) aren't built on a buildd. Unfortunately the Debian infrastructure doesn't allow arch:all packages to be properly binNMU'ed. Hence, I will shortly do a no-changes source-only upload to DELAYED/15, closing this bug. Please let me know if I should delay or cancel that upload. Paul Please cancel that upload, I will do a new upload.
Processed: src:pyaxmlparser: fails to migrate to testing for too long: uploader built arch:all binaries
Processing control commands: > close -1 0.3.26-1 Bug #1001120 [src:pyaxmlparser] src:pyaxmlparser: fails to migrate to testing for too long: uploader built arch:all binaries Marked as fixed in versions pyaxmlparser/0.3.26-1. Bug #1001120 [src:pyaxmlparser] src:pyaxmlparser: fails to migrate to testing for too long: uploader built arch:all binaries Marked Bug as done -- 1001120: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1001120 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1001120: src:pyaxmlparser: fails to migrate to testing for too long: uploader built arch:all binaries
Source: pyaxmlparser Version: 0.3.24-1 Severity: serious Control: close -1 0.3.26-1 Tags: sid bookworm pending User: release.debian@packages.debian.org Usertags: out-of-sync Dear maintainer(s), The Release Team considers packages that are out-of-sync between testing and unstable for more than 60 days as having a Release Critical bug in testing [1]. Your package src:pyaxmlparser has been trying to migrate for 61 days [2]. Hence, I am filing this bug. If a package is out of sync between unstable and testing for a longer period, this usually means that bugs in the package in testing cannot be fixed via unstable. Additionally, blocked packages can have impact on other packages, which makes preparing for the release more difficult. Finally, it often exposes issues with the package and/or its (reverse-)dependencies. We expect maintainers to fix issues that hamper the migration of their package in a timely manner. This bug will trigger auto-removal when appropriate. As with all new bugs, there will be at least 30 days before the package is auto-removed. I have immediately closed this bug with the version in unstable, so if that version or a later version migrates, this bug will no longer affect testing. I have also tagged this bug to only affect sid and bookworm, so it doesn't affect (old-)stable. Your package is only blocked because the arch:all binary package(s) aren't built on a buildd. Unfortunately the Debian infrastructure doesn't allow arch:all packages to be properly binNMU'ed. Hence, I will shortly do a no-changes source-only upload to DELAYED/15, closing this bug. Please let me know if I should delay or cancel that upload. Paul [1] https://lists.debian.org/debian-devel-announce/2020/02/msg5.html [2] https://qa.debian.org/excuses.php?package=pyaxmlparser OpenPGP_signature Description: OpenPGP digital signature
Bug#947540: marked as done (stardict: build-depends on deprecated gnome-doc-utils)
Your message dated Sat, 04 Dec 2021 19:00:14 + with message-id and subject line Bug#947540: fixed in stardict 3.0.7+git20210701.96b96d8+dfsg-1 has caused the Debian Bug report #947540, regarding stardict: build-depends on deprecated gnome-doc-utils 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.) -- 947540: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=947540 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: stardict Version: 3.0.6+dfsg-0.1 Severity: important Control: block 936625 by -1 Control: block 889019 by -1 User: pkg-gnome-maintain...@lists.alioth.debian.org Usertags: oldlibs gnome-doc-utils This package Build-Depends on gnome-doc-utils. gnome-doc-utils is a deprecated package of documentation utilities. Its most recent upstream release was in 2012, with most changes in its git repository since then being translation updates. The GNOME team do not consider gnome-doc-utils to be suitable for release in Debian 11 'bullseye'. The supported replacement is yelp.m4 in yelp-tools, as used in many GNOME 3 packages. A porting guide is available: https://wiki.gnome.org/Initiatives/GnomeGoals/NewDocumentationInfrastructure gnome-doc-utils relies on Python 2 code that seems unlikely to be converted to Python 3, so bug #936625 (part of the effort to remove Python 2 from Debian for Debian 11 'bullseye') has its severity set to serious. This means that this bug is highly likely to be elevated to serious severity at some point in future. Please convert this package to use yelp-tools, or if necessary remove the documentation processing entirely. Thanks, smcv --- End Message --- --- Begin Message --- Source: stardict Source-Version: 3.0.7+git20210701.96b96d8+dfsg-1 Done: xiao sheng wen We believe that the bug you reported is fixed in the latest version of stardict, 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 947...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. xiao sheng wen (supplier of updated stardict 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, 19 Oct 2021 13:04:47 +0800 Source: stardict Binary: stardict stardict-common stardict-gtk stardict-gtk-dbgsym stardict-plugin stardict-plugin-cal stardict-plugin-cal-dbgsym stardict-plugin-dbgsym stardict-plugin-espeak stardict-plugin-espeak-dbgsym stardict-plugin-festival stardict-plugin-festival-dbgsym stardict-plugin-fortune stardict-plugin-fortune-dbgsym stardict-plugin-info stardict-plugin-info-dbgsym stardict-plugin-spell stardict-plugin-spell-dbgsym stardict-tools stardict-tools-dbgsym Architecture: source all i386 Version: 3.0.7+git20210701.96b96d8+dfsg-1 Distribution: unstable Urgency: medium Maintainer: xiao sheng wen Changed-By: xiao sheng wen Description: stardict - International dictionary lookup program - stardict.png icons stardict-common - International dictionary lookup program - data files stardict-gtk - International dictionary lookup program - gtk stardict-plugin - International dictionary lookup program - common plugins stardict-plugin-cal - International dictionary lookup program - cal plugin stardict-plugin-espeak - International dictionary lookup program - eSpeak TTS plugin stardict-plugin-festival - International dictionary lookup program - Festival TTS plugin stardict-plugin-fortune - International dictionary lookup program - fortune plugin stardict-plugin-info - International dictionary lookup program - info plugin stardict-plugin-spell - International dictionary lookup program - spell plugin stardict-tools - dictionary conversion tools of stardict Closes: 947540 996678 Changes: stardict (3.0.7+git20210701.96b96d8+dfsg-1) unstable; urgency=medium . [ xiao sheng wen(肖盛文) ] * New maintainer (Closes: #996678) * New upstream version 3.0.7+git20210701.96b96d8, support gtk3 * d/copyright: - update Source: field to new upstream URL - add gpl-2+ license paragraph - add Files-Excluded files - add tools/src info, use licensecheck - add Upstream-Contact: Hu Zheng * d/control: - Bump debhelper-compat (= 13) - Bump
Processed: update bts with missing info
Processing commands for cont...@bugs.debian.org:
> notfixed 993324 2.7.1+dfsg-1
Bug #993324 {Done: Dirk Eddelbuettel } [libgsl25] libgsl25:
ABI breakage: removed symbol gsl_linalg_QR_TR_decomp
There is no source info for the package 'libgsl25' at version '2.7.1+dfsg-1'
with architecture ''
Unable to make a source version for version '2.7.1+dfsg-1'
No longer marked as fixed in versions 2.7.1+dfsg-1.
> fixed 993324 gsl/2.7.1+dfsg-1
Bug #993324 {Done: Dirk Eddelbuettel } [libgsl25] libgsl25:
ABI breakage: removed symbol gsl_linalg_QR_TR_decomp
Marked as fixed in versions gsl/2.7.1+dfsg-1.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
993324: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=993324
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Processed: update bts with missing info
Processing commands for cont...@bugs.debian.org:
> fixed 993324 2.7.1+dfsg-1
Bug #993324 {Done: Dirk Eddelbuettel } [libgsl25] libgsl25:
ABI breakage: removed symbol gsl_linalg_QR_TR_decomp
There is no source info for the package 'libgsl25' at version '2.7.1+dfsg-1'
with architecture ''
Unable to make a source version for version '2.7.1+dfsg-1'
Marked as fixed in versions 2.7.1+dfsg-1.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
993324: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=993324
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#997347: marked as done (python-formencode: FTBFS: dh_auto_test: error: pybuild --test --test-nose -i python{version} -p 3.9 --test-nose returned exit code 13)
Your message dated Sat, 04 Dec 2021 18:04:37 +
with message-id
and subject line Bug#997347: fixed in python-formencode 2.0.1-1
has caused the Debian Bug report #997347,
regarding python-formencode: FTBFS: dh_auto_test: error: pybuild --test
--test-nose -i python{version} -p 3.9 --test-nose returned exit code 13
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
997347: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997347
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-formencode
Version: 2.0.0-2
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> # network is required for the
> http://this.domain.does.not.exist.example.org/test.html test
> http_proxy='' dh_auto_test --buildsystem=pybuild -- --test-nose
> I: pybuild pybuild:285: cp
> /<>/formencode/tests/non_empty.txt
> /<>/.pybuild/cpython3_3.9_formencode/build/formencode/tests/
> cp -r /<>/formencode/tests/htmlfill_data
> /<>/.pybuild/cpython3_3.9_formencode/build/formencode/tests/
> cp -r /<>/formencode/i18n
> /<>/.pybuild/cpython3_3.9_formencode/build/formencode/
> I: pybuild base:232: cd
> /<>/.pybuild/cpython3_3.9_formencode/build; python3.9 -m nose -v
> test_validate (formencode.tests.test_cc.TestCreditCardExpires) ... ok
> test_validate (formencode.tests.test_cc.TestCreditCardValidator) ... ok
> test_clone (formencode.tests.test_compound.TestAllCompoundValidator) ... ok
> test_from_python (formencode.tests.test_compound.TestAllCompoundValidator)
> ... ok
> test_repr (formencode.tests.test_compound.TestAllCompoundValidator) ... ok
> test_to_python (formencode.tests.test_compound.TestAllCompoundValidator) ...
> ok
> test_clone (formencode.tests.test_compound.TestAnyCompoundValidator) ... ok
> test_from_python (formencode.tests.test_compound.TestAnyCompoundValidator)
> ... ok
> test_repr (formencode.tests.test_compound.TestAnyCompoundValidator) ... ok
> test_to_python (formencode.tests.test_compound.TestAnyCompoundValidator) ...
> ok
> test_to_python_error
> (formencode.tests.test_compound.TestAnyCompoundValidator) ... ok
> test_clone (formencode.tests.test_compound.TestCompoundValidator) ... ok
> test_from_python (formencode.tests.test_compound.TestCompoundValidator) ... ok
> test_repr (formencode.tests.test_compound.TestCompoundValidator) ... ok
> test_to_python (formencode.tests.test_compound.TestCompoundValidator) ... ok
> test_clone (formencode.tests.test_compound.TestPipeCompoundValidator) ... ok
> test_from_python (formencode.tests.test_compound.TestPipeCompoundValidator)
> ... ok
> test_repr (formencode.tests.test_compound.TestPipeCompoundValidator) ... ok
> test_to_python (formencode.tests.test_compound.TestPipeCompoundValidator) ...
> ok
> formencode.tests.test_context.test_one ... ok
> formencode.tests.test_context.test_fail ... ok
> formencode.tests.test_context.test_default ... ok
> test_call (formencode.tests.test_declarative.TestDeclarative) ... ok
> test_init (formencode.tests.test_declarative.TestDeclarative) ... ok
> test_repr (formencode.tests.test_declarative.TestDeclarative) ... ok
> test_repr_recursive (formencode.tests.test_declarative.TestDeclarative) ... ok
> formencode.tests.test_doctest_xml_compare.test_xml_compare ... ok
> Doctests for docs/htmlfill.txt ... ok
> Doctests for docs/Validator.txt ... ok
> Doctests for formencode/tests/non_empty.txt ... ok
> Doctests for formencode.compound ... ok
> Doctests for formencode.htmlfill ... ok
> Doctests for formencode.htmlgen ... ok
> Doctests for formencode.national ... ok
> Doctests for formencode.schema ... ok
> Doctests for formencode.validators ... FAIL
> test_invalid_email_addresses (formencode.tests.test_email.TestEmail) ... ok
> test_valid_email_addresses (formencode.tests.test_email.TestEmail) ... ok
> formencode.tests.test_htmlfill.test_inputoutput('/<>/.pybuild/cpython3_3.9_formencode/build/formencode/tests/htmlfill_data/data-error1.txt',)
> ... ok
> formencode.tests.test_htmlfill.test_inputoutput('/<>/.pybuild/cpython3_3.9_formencode/build/formencode/tests/htmlfill_data/data-fill4.txt',)
> ... ok
> formencode.tests.test_htmlfill.test_inputoutput('/<>/.pybuild/cpython3_3.9_formencode/build/formencode/tests/htmlfill_data/data-fill1.txt',)
> ... ok
> formencode.tests.test_htmlfill.test_inputoutput('/<>/.pybuild/cpython3_3.9_formencode/build/formencode/tests/htmlfill_data/data-fill3.txt',)
> ... ok
>
Bug#1000812: marked as done (pyrle: import fails on Python 3.10)
Your message dated Sat, 04 Dec 2021 18:04:30 + with message-id and subject line Bug#1000812: fixed in pyrle 0.0.33-2 has caused the Debian Bug report #1000812, regarding pyrle: import fails on 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.) -- 1000812: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1000812 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: python3-pyrle Version: 0.0.33-1 Severity: serious Control: affects -1 python3-pyranges python3-pyrle fails to import on Python 3.10. This causes python3-pyranges to fail its build-time tests. (python3-pyrle itself doesn't run build-time tests.) --- End Message --- --- Begin Message --- Source: pyrle Source-Version: 0.0.33-2 Done: Nilesh Patra We believe that the bug you reported is fixed in the latest version of pyrle, 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 1000...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Nilesh Patra (supplier of updated pyrle package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sat, 04 Dec 2021 23:14:49 +0530 Source: pyrle Architecture: source Version: 0.0.33-2 Distribution: unstable Urgency: medium Maintainer: Debian Med Packaging Team Changed-By: Nilesh Patra Closes: 1000812 Changes: pyrle (0.0.33-2) unstable; urgency=medium . * Tighten B-D on python3-tabulate (Closes: #1000812) Checksums-Sha1: 3d95805a1f628115f9ff375a9f97fb3c8e94cba0 2130 pyrle_0.0.33-2.dsc eac53de6cfed67352b1a2c79aca47ce25335c3a8 4064 pyrle_0.0.33-2.debian.tar.xz 6d7f20c98116755aa9c61142859c7b643aa364da 7993 pyrle_0.0.33-2_amd64.buildinfo Checksums-Sha256: 1fd7dba00fbf59a9069ea80018af49911154ba6e3fab7b7fba91ff68eba86159 2130 pyrle_0.0.33-2.dsc a88f8f116a469ef5593c22b2e61ee2ffdcd443732a99e98f5e2d0ed7048920e2 4064 pyrle_0.0.33-2.debian.tar.xz 34e4a80c81fb42636f4710b4e2392e2d944ca51ecc31ec09af3f9bac2233b217 7993 pyrle_0.0.33-2_amd64.buildinfo Files: a5e11b13f2ca5c185475e3a31104d749 2130 python optional pyrle_0.0.33-2.dsc d1b6162229ad6e3c1c1970da1fe99902 4064 python optional pyrle_0.0.33-2.debian.tar.xz 4c56f08b4e5d1fef1bb8edee11f3a225 7993 python optional pyrle_0.0.33-2_amd64.buildinfo -BEGIN PGP SIGNATURE- iQJGBAEBCgAwFiEEPpmlJvXcwMu/HO6mALrnSzQzafEFAmGrqnQSHG5pbGVzaEBk ZWJpYW4ub3JnAAoJEAC650s0M2nxLOwP/1jBHKDDOPf4CynDp0NHKYndfTyqrUlO FhSVdGzKZWmCCTf4l6ww5Hi4eWJFOxtWfYVSw81CFrgOx5t0moRVgWLohtdCyCe5 p21CvDetAJ3GwZDx0btG2yFGy+xgRgX6tUd/QktuHFKXMejooPh0WR2ZQ7sYB/P7 y9wvnTuokAYELy21bSEpjR9r2PcPWcvZTcx+KIa3wNcboCP+/HK4qeogefmT0eC0 mwwdTWGiM62kSlxr1p56hv2EWg0bjVLyYr4O7MFFW1KSJ+FsjVBk7ddl0SYK4jJJ OgLm+hUYdoyOzWAjBIjgCbNHc9WbonBTZsrJmM7yVLAXvuya6ddXjXqFjJn5Vx7z KTin2rZ/ht+2Yvk8DHCwOZaWyOIF+HNywkHZYeeA3nLRYEbQdWNZAcPrymWT23+y cIR9+gXNtdb40Z6Izv/bmtLhPxHhQSe7te8xuboP+SM3JYyOITCqpg5FfRY1jR4X 8WL5+nv11LVy5G3xKpYCkjDed4dnlgLerrVLfXNMXR2iXJLGpAmng3HE25K5rMH7 2dR2O+Jm/+d8lXeylqRgMw9MTaoehEXXgjPTS1W6AW5sTaodB/7g1GADeNBl96Yh aIVUAd5CS6exmPS/spX8RhwX4dmhyIFmm7JZJ/WirqmCcDGhQymPK/UiAcy/rb+6 +kc+5RK1TkEE =Tkwe -END PGP SIGNATURE End Message ---
Bug#999533: matplotlib: python3-pil.imagetk should be Depends
Dear Sandro, On Fri, 3 Dec 2021 11:49:52 -0500 Sandro Tosi wrote: control: severity -1 normal > > This is not a bug in cartopy, matplotlib tries to use ImageTk but the > > package is not installed. > > > > python3-matplotlib only Recommends python3-pil.imagetk, this should be a > > Depends. > > This issue is still present in matplotlib (3.5.0-2) and affects several > packages. These should not have to add python3-pil.imagetk to their > build dependencies because matplotlib does not pull it in. this is done on purpose, so that people can switch backend and remove the underlying package without causing apt to want to remove also python3-matplotlib. All the backend packages are in Recommends for a reason. If you need a different backend during build, please set the backend rcparams accordingly during your package build. could it make sense to use something like the following? Depends: python3-pil.imagetk | python3-gi | python3-gi-cairo | python3-gobject | python3-pyqt5 kind regards -- Antonio Valentino
Bug#984275: openmw is marked for autoremoval from testing
Hi Bret, > * MyGUI 3.4 being uploaded to Debian: > https://salsa.debian.org/psi29a-guest/MyGUI Can you expand on the status on myGui? AFAICT there is no RFS at the moment, however, there is a patch on the BTS claiming to fix the FTBFS? Is there something actionable where I could help? -- tobi
Processed: Re: openmw is marked for autoremoval from testing
Processing control commands: > block -1 by 913828 Bug #984275 [src:openmw] openmw: ftbfs with GCC-11 984275 was not blocked by any bugs. 984275 was not blocking any bugs. Added blocking bug(s) of 984275: 913828 -- 984275: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=984275 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#984275: openmw is marked for autoremoval from testing
Control: block -1 by 913828 Dang, I did not realize that this needs recastnavigation. It is currently sitting in NEW The current repository on salsa will build with recastnavigation, so all we can do is wait... Bret: Make sure to pull. I'd pushed a few commits fixing this and that. -- tobi
Bug#984275: openmw is marked for autoremoval from testing
Control: tags -1 pending I'm doing a (team-)upload soon(tm) Thanks Bret for working on this! -- tobi
Processed: Re: openmw is marked for autoremoval from testing
Processing control commands: > tags -1 pending Bug #984275 [src:openmw] openmw: ftbfs with GCC-11 Added tag(s) pending. -- 984275: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=984275 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Re: ogmtools: diff for NMU version 1:1.5-4.1
Processing control commands: > tags -1 -pending Bug #984268 [src:ogmtools] ogmtools: ftbfs with GCC-11 Removed tag(s) pending. -- 984268: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=984268 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#984268: ogmtools: diff for NMU version 1:1.5-4.1
Control: tags -1 -pending On Tue, 9 Nov 2021 17:02:49 +0200 Adrian Bunk wrote: > Control: tags 984268 + patch > Control: tags 984268 + pending > > Dear maintainer, > > I've prepared an NMU for ogmtools (versioned as 1:1.5-4.1) and uploaded > it to DELAYED/15. Please feel free to tell me if I should cancel it. > > cu > Adrian mmm, somehow that NMU did not land in unstable -- tobi
Bug#1000742: marked as done (ImportError: cannot import name 'Iterable' from 'collections')
Your message dated Sat, 04 Dec 2021 16:35:03 +
with message-id
and subject line Bug#1000742: fixed in python-tabulate 0.8.7-0.2
has caused the Debian Bug report #1000742,
regarding ImportError: cannot import name 'Iterable' from 'collections'
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.)
--
1000742: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1000742
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: python3-tabulate
Version: 0.8.7-0.1
Severity: important
tabulate can't be imported anymore, starting with python3.10
$ python3.10
>>> import tabulate
Traceback (most recent call last):
File "", line 1, in
File "/usr/lib/python3/dist-packages/tabulate.py", line 16, in
from collections import Iterable
ImportError: cannot import name 'Iterable' from 'collections'
(/usr/lib/python3.10/collections/__init__.py)
The cause seems to be a bugged test "if python_version_tuple() >= ("3", "3",
"0"):"
comparing strings instead of numbers.
Seems to be fixed in recent tabulate.
-- System Information:
Debian Release: bookworm/sid
APT prefers unstable
APT policy: (990, 'unstable'), (500, 'stable-security'), (500, 'stable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 5.15.0-1-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 python3-tabulate depends on:
ii python3 3.9.8-1
python3-tabulate recommends no packages.
python3-tabulate suggests no packages.
-- no debconf information
--
Félix
signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Source: python-tabulate
Source-Version: 0.8.7-0.2
Done: Nilesh Patra
We believe that the bug you reported is fixed in the latest version of
python-tabulate, 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 1000...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Nilesh Patra (supplier of updated python-tabulate package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Sat, 04 Dec 2021 16:25:24 +
Source: python-tabulate
Architecture: source
Version: 0.8.7-0.2
Distribution: unstable
Urgency: medium
Maintainer: Yago González
Changed-By: Nilesh Patra
Closes: 1000742
Changes:
python-tabulate (0.8.7-0.2) unstable; urgency=medium
.
* Non-maintainer upload.
* Add patch to fix FTBFS with python 3.10 (Closes: #1000742)
Checksums-Sha1:
761ec64657f3fc7f1329ff255ab83acf90df2258 1957 python-tabulate_0.8.7-0.2.dsc
b49ef5731f18f7ec594d71db1530a2b990cdd7bb 4488
python-tabulate_0.8.7-0.2.debian.tar.xz
f53835bc65c5610a182062054cf1424262a44e58 6548
python-tabulate_0.8.7-0.2_amd64.buildinfo
Checksums-Sha256:
1fc61d88b37090aaec774a12c44d9ba6086a43813db9e949e3e0ceab6384eeaf 1957
python-tabulate_0.8.7-0.2.dsc
ab74e17587a995c0eb7ae40c9e317c95e8fd45cee9e5c35f3951501b00a10951 4488
python-tabulate_0.8.7-0.2.debian.tar.xz
aeff9b0b38eee19142259100bed69a4085886f2bb897dbac194c3085270f6391 6548
python-tabulate_0.8.7-0.2_amd64.buildinfo
Files:
2b611359fa00ee603fc475e640ad1afb 1957 python optional
python-tabulate_0.8.7-0.2.dsc
5f5169367fcd5ac0de906ccc24266a67 4488 python optional
python-tabulate_0.8.7-0.2.debian.tar.xz
986d1cbb4fa11d75d8040f427f644ed9 6548 python optional
python-tabulate_0.8.7-0.2_amd64.buildinfo
-BEGIN PGP SIGNATURE-
iQJGBAEBCgAwFiEEPpmlJvXcwMu/HO6mALrnSzQzafEFAmGrl5wSHG5pbGVzaEBk
ZWJpYW4ub3JnAAoJEAC650s0M2nxTVEQAKRf4r4Qhmi2S+mcNA0WOX78BryQDrE+
7wmqHRUI9H3sa6w93xiVv+0hWopRjPz2AGB/OBCJI2AfcdB7nboEHjmtz62/+LAD
sHfD88O91teKFTW+ddCZPAU5W0AaOiC9i++m9JCt5nUSjq1dTqb8oqQTTwbFKCv1
aiU15gzhSK1CffpqCy5QpLmx4FRRlIE8OmxuJyPpKmrdgYktzqvqKUnzanaPTjs5
1OO9ZvT2Au6mIKCEStqfUGtsSk3iKgfCF75FLlluVeLVW8rOeVK3ptgPjJJNbESn
G97Qz/oHAv9VS/JaBR9xKLIFis+l6cl/ygcJKSbr6AwuyN8ImKwZQCIWlfvOYfZj
QGb2LTjnmzgneHgd0qdm6rgEL7D9Db/NbUynrL5QuFZWBScRSvrBWBQwgqc96pJJ
pvnM0fRunQCSNDgYUUzs1B3bBxB5djjqOeooiMUtpMz1cfmNIILAaO17BoFF/3xq
wwLh0Eh8ksZ2Q+OzjItr6XJXSBdB7bCamNallJnF0r+TYYlouHHR5VtWOIhEV3yi
Bug#1000812: [RFH] Bug#1000812: pyrle: import fails on Python 3.10
Hi Stefano, On 12/4/21 9:00 PM, Stefano Rivera wrote: Hi Nilesh (2021.12.04_15:15:05_+) Would you have any hint on this? Is it a bug with the python3 package itself? You're waiting for python3-tabulate to be patched for Python 3.10 support. Indeed. I was just being silly as it seems. I patched tabulate to work with python3.10 (smoke tests go well, and I did a few manual tests) and uploaded. Thanks a lot for your time. Regards, Nilesh OpenPGP_signature Description: OpenPGP digital signature
Bug#999693: php8.1: Regular expression functions warn "Compilation failed" and return null
Hi, On 22/11/2021 09:16, Ondřej Surý wrote: I analysed the problem in: https://github.com/PhilipHazel/pcre2/issues/56 Thanks! I've had a read of that, and AIUI it's a behaviour change (matching that of perl) rather than an ABI change? I guess bumping the version in the symbols file like this should do the trick: - pcre2_set_compile_extra_options_8@Base 10.32 + pcre2_set_compile_extra_options_8@Base 10.38 Making this change will cause some things that will work fine with 10.32 to incorrectly state a dependency on >=10.38, yes? But leaving things as-is means that some code that uses a particular flag will not work if compiled with >=10.38 and run against <10.38? I think that probably means on balance we should make the change you suggest, but I wanted to check I'd understood correctly :) Regards, Matthew
Bug#1000506: boost1.71 FTBFS with Python 3.10
Hi, On 24/11/21 12:53, Adrian Bunk wrote: Source: boost1.71 Version: 1.71.0-7+b3 Severity: serious Tags: ftbfs https://buildd.debian.org/status/logs.php?pkg=boost1.71=1.71.0-7%2Bb3 ... libs/python/src/exec.cpp:109:14: error: ‘_Py_fopen’ was not declared in this scope; did you mean ‘_Py_wfopen’? 109 | FILE *fs = _Py_fopen(f, "r"); | ^ | _Py_wfopen ... Thanks for reporting this. Ideally the best way to fix this bug would be to get rid of boost1.71, given that boost1.74 already exists (also, a new version should be packaged, but that's another story). Giovanni. -- Giovanni Mascellani
Processed: severity of 1000742 is serious
Processing commands for cont...@bugs.debian.org: > severity 1000742 serious Bug #1000742 [python3-tabulate] ImportError: cannot import name 'Iterable' from 'collections' Severity set to 'serious' from 'important' > thanks Stopping processing here. Please contact me if you need assistance. -- 1000742: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1000742 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1000812: [RFH] Bug#1000812: pyrle: import fails on Python 3.10
Hi Nilesh (2021.12.04_15:15:05_+) > Would you have any hint on this? > Is it a bug with the python3 package itself? You're waiting for python3-tabulate to be patched for Python 3.10 support. I added a bug blocking link. SR -- Stefano Rivera http://tumbleweed.org.za/ +1 415 683 3272
Processed: block 1000812 with 1000742
Processing commands for cont...@bugs.debian.org: > block 1000812 with 1000742 Bug #1000812 [python3-pyrle] pyrle: import fails on Python 3.10 1000812 was not blocked by any bugs. 1000812 was not blocking any bugs. Added blocking bug(s) of 1000812: 1000742 > thanks Stopping processing here. Please contact me if you need assistance. -- 1000812: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1000812 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#984154: gnome-chemistry-utils: diff for NMU version 0.14.17-6.1
Control: tags 984154 + patch Control: tags 984154 + pending Dear maintainer, I've prepared an NMU for gnome-chemistry-utils (versioned as 0.14.17-6.1) and uploaded it to DELAYED/14. Please feel free to tell me if I should cancel it. cu Adrian diff -Nru gnome-chemistry-utils-0.14.17/debian/changelog gnome-chemistry-utils-0.14.17/debian/changelog --- gnome-chemistry-utils-0.14.17/debian/changelog 2021-03-08 16:06:12.0 +0200 +++ gnome-chemistry-utils-0.14.17/debian/changelog 2021-12-04 16:51:53.0 +0200 @@ -1,3 +1,11 @@ +gnome-chemistry-utils (0.14.17-6.1) unstable; urgency=medium + + * Non-maintainer upload. + * Build with -std=gnu++14 to workaround FTBFS with gcc 11. +(Closes: #984154) + + -- Adrian Bunk Sat, 04 Dec 2021 16:51:53 +0200 + gnome-chemistry-utils (0.14.17-6) unstable; urgency=medium * d/patches/gchempaint-merge-molecules-fix.patch: Add patch. diff -Nru gnome-chemistry-utils-0.14.17/debian/rules gnome-chemistry-utils-0.14.17/debian/rules --- gnome-chemistry-utils-0.14.17/debian/rules 2021-03-08 16:06:12.0 +0200 +++ gnome-chemistry-utils-0.14.17/debian/rules 2021-12-04 16:51:48.0 +0200 @@ -6,6 +6,7 @@ DEB_VENDOR := $(shell dpkg-vendor --query vendor) export DEB_BUILD_MAINT_OPTIONS = hardening=+all +export DEB_CXXFLAGS_MAINT_APPEND = -std=gnu++14 DPKG_EXPORT_BUILDFLAGS = 1 include /usr/share/dpkg/buildflags.mk
Processed: gnome-chemistry-utils: diff for NMU version 0.14.17-6.1
Processing control commands: > tags 984154 + patch Bug #984154 [src:gnome-chemistry-utils] gnome-chemistry-utils: ftbfs with GCC-11 Added tag(s) patch. > tags 984154 + pending Bug #984154 [src:gnome-chemistry-utils] gnome-chemistry-utils: ftbfs with GCC-11 Added tag(s) pending. -- 984154: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=984154 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1000812: [RFH] Bug#1000812: pyrle: import fails on Python 3.10
Dear Python team, Would you have any hint on this? Is it a bug with the python3 package itself? Let me know. Regards, Nilesh On Thu, 2 Dec 2021 12:02:59 +0530 Nilesh Patra wrote: > On Mon, 29 Nov 2021 20:35:40 +0100 Andreas Tille wrote: > > Am Mon, Nov 29, 2021 at 11:36:33PM +0530 schrieb Nilesh Patra: > > > I rebuilt with python3.10, and now error is this. > > > Something wrong with pandas? > > > > As far as I understood we need to wait for pandas 1.3 to work > > with Python3.10. > > I retried autopkgtest now, and it still seems a non-bug with pyrle. > @Rebecca, please re-assign this bug to relevant package. > > autopkgtest [11:57:49]: test autodep8-python3: [--- > Testing with python3.10: > Traceback (most recent call last): > File "", line 1, in > File "/usr/lib/python3/dist-packages/pyrle/__init__.py", line 1, in > from pyrle.rle import Rle > File "/usr/lib/python3/dist-packages/pyrle/rle.py", line 13, in > from tabulate import tabulate > File "/usr/lib/python3/dist-packages/tabulate.py", line 16, in > from collections import Iterable > ImportError: cannot import name 'Iterable' from 'collections' > (/usr/lib/python3.10/collections/__init__.py) > > """ > Minimal example to reproduce: > > $ python3.10 > Python 3.10.0+ (default, Nov 17 2021, 06:49:13) [GCC 11.2.0] on linux > Type "help", "copyright", "credits" or "license" for more information. > >>> from tabulate import tabulate > Traceback (most recent call last): > File "", line 1, in > File "/usr/lib/python3/dist-packages/tabulate.py", line 16, in > from collections import Iterable > ImportError: cannot import name 'Iterable' from 'collections' > (/usr/lib/python3.10/collections/__init__.py) > """ > > $ apt policy python3.10 > python3.10: > Installed: 3.10.0-5 > Candidate: 3.10.0-5 > Version table: > *** 3.10.0-5 500 > 500 http://deb.debian.org/debian sid/main amd64 Packages > 100 /var/lib/dpkg/status signature.asc Description: PGP signature
Bug#1001097: ksh93u+m_1.0.0~beta.1-2_all-buildd.changes REJECTED
On 2021-12-04 16:15, Anuradha Weeraman wrote: > Hi Aruelien > > On Sat, Dec 04, 2021 at 10:39:58AM +0100, Aurelien Jarno wrote: > > Source: ksh93u+m > > Version: 1.0.0~beta.1-2 > > Severity: serious > > > > On 2021-12-03 18:48, Debian FTP Masters wrote: > > > Version check failed: > > > Your upload included the binary package ksh, version 20210511, for all, > > > however unstable already has version 20210511. > > > Uploads to unstable must have a higher version than present in unstable. > > > > > > Mapping sid to unstable. > > The version 20210511 is a transitional package from the older ksh package > over to ksh93u+m [1]. According to this, is the expectation that the the > transitional package version is bumped with each release of ksh93u+m, > at least until the transition is complete in the next Debian release? The error returned by dak, is indeed that it is not allowed to upload the same package with the same version twice, so you should arrange for the version of the resulting ksh package to increase for each new upload. Regards, Aurelien -- Aurelien Jarno GPG: 4096R/1DDD8C9B aurel...@aurel32.net http://www.aurel32.net
Bug#1001110: marked as done (darkradiant FTBFS on 32bit: u64 is not 8 bytes)
Your message dated Sat, 04 Dec 2021 14:48:44 + with message-id and subject line Bug#1001110: fixed in darkradiant 2.14.0-2 has caused the Debian Bug report #1001110, regarding darkradiant FTBFS on 32bit: u64 is not 8 bytes to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1001110: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1001110 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: darkradiant Version: 2.14.0-1 Severity: serious Tags: ftbfs https://buildd.debian.org/status/logs.php?pkg=darkradiant=2.14.0-1 ... /<>/radiantcore/model/import/openfbx/ofbx.h:21:27: error: static assertion failed: u64 is not 8 bytes 21 | static_assert(sizeof(u64) == 8, "u64 is not 8 bytes"); | ^~~~ ... --- End Message --- --- Begin Message --- Source: darkradiant Source-Version: 2.14.0-2 Done: Tobias Frost We believe that the bug you reported is fixed in the latest version of darkradiant, 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 1001...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Tobias Frost (supplier of updated darkradiant package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Sat, 04 Dec 2021 15:31:33 +0100 Source: darkradiant Architecture: source Version: 2.14.0-2 Distribution: unstable Urgency: medium Maintainer: Debian Games Team Changed-By: Tobias Frost Closes: 1001110 Changes: darkradiant (2.14.0-2) unstable; urgency=medium . * New patch to fix FTBFS on 32 bit archs. (Closes: #1001110) Checksums-Sha1: 3e8aea83e61e2f4bc4f7dfff8372ccb9877a4ff7 2434 darkradiant_2.14.0-2.dsc 583cc19111a134ea3dbd75c4789ab5422fb19206 9372 darkradiant_2.14.0-2.debian.tar.xz 3e6fce4b2fa35c35b3e5de08d101c49b006631e5 17159 darkradiant_2.14.0-2_source.buildinfo Checksums-Sha256: 01676955580c2f187ac33d60ef1e52523b9adb827cc8762195d66626258e0ef0 2434 darkradiant_2.14.0-2.dsc 89a7121455db9ad1532ad6e08f93ccffe8e1c425ebf48403204b3c1a60a07a91 9372 darkradiant_2.14.0-2.debian.tar.xz 490bc05610e1f5ea8a643c139ff85f3330d3a9482d357c472538064509b71683 17159 darkradiant_2.14.0-2_source.buildinfo Files: 3c96b793f69e6407b2bb201ea7ecabe4 2434 graphics optional darkradiant_2.14.0-2.dsc 960b845d5054773d9da6a0a18116d846 9372 graphics optional darkradiant_2.14.0-2.debian.tar.xz db25d7d6e6f234763dfb8d6bafee26ab 17159 graphics optional darkradiant_2.14.0-2_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEE/d0M/zhkJ3YwohhskWT6HRe9XTYFAmGre80ACgkQkWT6HRe9 XTZ9yRAAsGZqsTon5U8zOwyDC+igqxorw6ckntmEnJFhfFkY2K6+NmNAAfsFxNbB zMVssF8GiPtg0PHEfqWkQBe8cUZ51ZvdP5GyDzf2+vd8FI1h89pYYyIGy1H+GaRA Vw5ARVb2pkFKqURIYg7gaJl0pDQJ/VkUmFX3DFNdCrojarTOIa9SmqJ7pi8tWV7N Mae5G6BhyXhCXEdx9HaZj2gZbiGFIGBM0YY2AuIAvCcbYenWB7ee+Tou4HIyclKa wrxFTd1ZyHWd+dpXhZhPu0ONg3IhSYrGc1RDB1Ow6aVwdsLH5KNHmAr3p+7QQ0ng kyeOBmn5guUl3uGbxfcof+jBIn0SoGVMiWeKZ9HXcjFgz/FqCh5IFuU/IflgWnCA /269i796q0h63YTJAkHqnqymLalyF6NmjKVBQfkDOF1YqOiC94KRDPpvDRMQIAEA AfVafjNcNnELhKhU8KT8zXJ9wKZBhC9vlX8YRz6X5F8lgI8jXqmgWOKAOjrYuMHF xW01qfKJeFx7TrqtJQT2CxZzCVc9xARspiEUDk90QrnCsEMhTP1KTp1PAoFvQcGy 6sEQvzyA6MkY51HpMjeoLgtpGjY/2niiKLxW+lzAO8TzSWwU6WkwyOk1MhnGJYWl BPWuzzVk029by7ewZPf25IBkFFarYVixnyLV3q88S/NGJwI3b0k= =/XwR -END PGP SIGNATURE End Message ---
Bug#1001016: telegram-desktop backports request
telegram-cli was also outdated and may remain so if no longer supported. On Sat, 4 Dec 2021, Ralf Neubauer wrote: > Hi Nicholas, > > I can second that, everything is fine now! Thank you for the quick reaction! > > Just to have it documented somewhere, in one of the out-of-date versions > I had to click the [Ok] button in the message box multiple times to > activate the window after having been away for some time. I assume the > message boxes were stacking, about five or ten exactly one over the > other. Since the upgrade to 3.1.1 I can't reproduce this any more for > lack of urgent messages, but the code may still behave the same way if > it is triggered the next time and it is very confusing for users. > > Thank you again, > Ralf > > On Sat, Dec 04, 2021 at 11:13:14AM +, piorunz wrote: > > Hi Nicholas, > > > > That's fantastic, everything works ok now! Thank you! > > > > I set up new Firefox profile with Telegram tab just in case, put that in > > place of old Telegram window, that worked for me for a day, but now I am > > back to using telegram desktop app. Great work:) > > > > On 04/12/2021 10:45, Nicholas Guriev wrote: > > > Hello! > > > > > > On ??, 2021-12-03 at 19:44 +, piorunz wrote: > > > > Testing has got 3.1.1. I hope bullseye-backports can update it? CC to > > > > maintainer, Nicholas Guriev! Thanks in advance. > > > > > > I have uploaded this version to Backports. It is already available on > > > mirrors and should work okay. > > > https://ftp.debian.org/debian/pool/main/t/telegram-desktop/ > > > > > > > > > -- > > With kindest regards, Piotr. > > > > ??? > > ??? Debian - The universal operating system > > ??? https://www.debian.org/ > > ??? > >
Bug#999680: marked as done (criu: FTBFS on armhf: cc1: error: '-mfloat-abi=hard': selected architecture lacks an FPU)
Your message dated Sat, 04 Dec 2021 14:34:06 + with message-id and subject line Bug#999680: fixed in criu 3.16.1-2 has caused the Debian Bug report #999680, regarding criu: FTBFS on armhf: cc1: error: '-mfloat-abi=hard': selected architecture lacks an FPU 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.) -- 999680: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=999680 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: criu Version: 3.16.1-1 Severity: serious Tags: ftbfs Justification: FTBFS X-Debbugs-Cc: car...@debian.org This is different from #918229, so filling a separate issue. criu on armhf FTBFS with gcc-11: dh clean --with python3 dh_auto_clean make -j4 clean make[1]: Entering directory '/<>' make[1]: git: No such file or directory /usr/bin/which: this version of `which' is deprecated; use `command -v' in scripts instead. CLEANDocumentation CLEANtest/compel CLEANimages CLEANcriu/arch/arm CLEANcriu/pie CLEANcriu CLEANcriu/unittest CLEANcriu/pie CLEANcriu CLEANsoccr CLEANlib/c CLEANlib/py/images CLEANlib/py CLEANlib CLEANcompel CLEANcompel/plugins CLEANlib/c CLEANlib/py/images CLEANlib/py CLEANlib CLEANcrit make[1]: Leaving directory '/<>' dh_clean debian/rules binary-arch dh binary-arch --with python3 dh_update_autotools_config -a dh_autoreconf -a dh_auto_configure -a dh_auto_build -a make -j4 "INSTALL=install --strip-program=true" make[1]: Entering directory '/<>' Note: Building without setproctitle() and strlcpy() support. To enable these features, please install libbsd-devel (RPM) / libbsd-dev (DEB). Makefile.config:41: Warn: you have libnftables installed but it has incompatible API Makefile.config:42: Warn: Building without nftables support make[1]: git: No such file or directory /usr/bin/which: this version of `which' is deprecated; use `command -v' in scripts instead. GEN .gitid GEN include/common/asm GEN compel/include/asm touch .config GEN compel/include/version.h GEN criu/include/version.h GEN include/common/config.h GEN compel/plugins/include/uapi/std/asm/syscall-types.h DEP compel/arch/arm/plugins/std/parasite-head.d GEN compel/arch/arm/plugins/std/syscalls/syscalls.S cc1: error: '-mfloat-abi=hard': selected architecture lacks an FPU GEN compel/plugins/include/uapi/std/syscall-codes.h DEP soccr/soccr.d cc1: error: '-mfloat-abi=hard': selected architecture lacks an FPU GEN compel/plugins/include/uapi/std/syscall.h CC soccr/soccr.o cc1: error: '-mfloat-abi=hard': selected architecture lacks an FPU make[2]: *** [/<>/scripts/nmk/scripts/build.mk:119: soccr/soccr.o] Error 1 make[1]: *** [Makefile:232: soccr/built-in.o] Error 2 make[1]: *** Waiting for unfinished jobs DEP compel/arch/arm/plugins/std/syscalls/syscalls.d cc1: error: '-mfloat-abi=hard': selected architecture lacks an FPU DEP compel/plugins/std/infect.d DEP compel/plugins/std/string.d DEP compel/plugins/std/log.d cc1: error: '-mfloat-abi=hard': selected architecture lacks an FPU cc1: error: '-mfloat-abi=hard': selected architecture lacks an FPU cc1: error: '-mfloat-abi=hard': selected architecture lacks an FPU DEP compel/plugins/std/fds.d DEP compel/plugins/std/std.d DEP compel/plugins/shmem/shmem.d cc1: error: '-mfloat-abi=hard': selected architecture lacks an FPU cc1: error: '-mfloat-abi=hard': selected architecture lacks an FPU cc1: error: '-mfloat-abi=hard': selected architecture lacks an FPU DEP compel/plugins/fds/fds.d cc1: error: '-mfloat-abi=hard': selected architecture lacks an FPU CC compel/plugins/std/fds.o CC compel/plugins/std/std.o CC compel/plugins/std/log.o cc1: error: '-mfloat-abi=hard': selected architecture lacks an FPU cc1: error: '-mfloat-abi=hard': selected architecture lacks an FPU make[2]: *** [/<>/scripts/nmk/scripts/build.mk:214: compel/plugins/std/std.o] Error 1 make[2]: *** Waiting for unfinished jobs cc1: error: '-mfloat-abi=hard': selected architecture lacks an FPU make[2]: *** [/<>/scripts/nmk/scripts/build.mk:214: compel/plugins/std/fds.o] Error 1 make[2]: *** [/<>/scripts/nmk/scripts/build.mk:214: compel/plugins/std/log.o] Error 1 make[1]: *** [Makefile.compel:56: compel/plugins/std.lib.a] Error 2 PBCC images/apparmor.pb-c.c PBCC images/bpfmap-data.pb-c.c PBCC images/fown.pb-c.c PBCC
Processed: Move where it was fixed (Control: does not work in -done)
Processing commands for cont...@bugs.debian.org:
> reassign 997176 libpq-dev 14~beta1-1
Bug #997176 {Done: Christoph Berg } [src:pgmodeler] pgmodeler:
FTBFS: Project ERROR: libpq development package not found
Bug reassigned from package 'src:pgmodeler' to 'libpq-dev'.
No longer marked as found in versions pgmodeler/0.9.3-1.
No longer marked as fixed in versions 14.1-1.
Bug #997176 {Done: Christoph Berg } [libpq-dev] pgmodeler:
FTBFS: Project ERROR: libpq development package not found
Marked as found in versions postgresql-14/14~beta1-1.
> close 997176 14.1-1
Bug #997176 {Done: Christoph Berg } [libpq-dev] pgmodeler:
FTBFS: Project ERROR: libpq development package not found
Marked as fixed in versions postgresql-14/14.1-1.
Bug #997176 {Done: Christoph Berg } [libpq-dev] pgmodeler:
FTBFS: Project ERROR: libpq development package not found
Bug 997176 is already marked as done; not doing anything.
> affects 997176 src:pgmodeler
Bug #997176 {Done: Christoph Berg } [libpq-dev] pgmodeler:
FTBFS: Project ERROR: libpq development package not found
Added indication that 997176 affects src:pgmodeler
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
997176: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997176
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Processed: tagging 1001110, bug 1001110 is forwarded to https://github.com/codereader/DarkRadiant/pull/26
Processing commands for cont...@bugs.debian.org: > tags 1001110 + upstream Bug #1001110 [src:darkradiant] darkradiant FTBFS on 32bit: u64 is not 8 bytes Added tag(s) upstream. > forwarded 1001110 https://github.com/codereader/DarkRadiant/pull/26 Bug #1001110 [src:darkradiant] darkradiant FTBFS on 32bit: u64 is not 8 bytes Set Bug forwarded-to-address to 'https://github.com/codereader/DarkRadiant/pull/26'. > thanks Stopping processing here. Please contact me if you need assistance. -- 1001110: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1001110 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: tagging 1001113
Processing commands for cont...@bugs.debian.org: > tags 1001113 + experimental Bug #1001113 [src:ocaml-flac] ocaml-flac FTBFS: Error: Unbound module Ogg_demuxer Added tag(s) experimental. > thanks Stopping processing here. Please contact me if you need assistance. -- 1001113: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1001113 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: tagging 1001110
Processing commands for cont...@bugs.debian.org: > tags 1001110 + pending Bug #1001110 [src:darkradiant] darkradiant FTBFS on 32bit: u64 is not 8 bytes Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 1001110: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1001110 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1001113: ocaml-flac FTBFS: Error: Unbound module Ogg_demuxer
Source: ocaml-flac Version: 0.2.0.1~really0.1.7-1 Severity: serious Tags: ftbfs bookworm sid https://buildd.debian.org/status/logs.php?pkg=ocaml-flac=0.2.0.1~really0.1.7-1%2Bb1 ... ocamlc.opt -c -g -w +A-4@5-7@8-9@11@12@20-35-44-45-50 -thread -I /usr/lib/ocaml/bytes -I /usr/lib/ocaml -I /usr/lib/ocaml/ogg ogg_demuxer_flac_decoder.ml File "ogg_demuxer_flac_decoder.ml", lines 63-64, characters 6-15: 63 | ..Ogg_demuxer. 64 |channels.. Error: Unbound module Ogg_demuxer make[4]: *** [OCamlMakefile:952: ogg_demuxer_flac_decoder.cmo] Error 2
Bug#999680: marked as pending in criu
Control: tag -1 pending Hello, Bug #999680 in criu 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/debian/criu/-/commit/55d4dc414e6542c69c4fae95d31160256d726013 Explicitly enable FPU on ARM builds to fix FTBFS with gcc-11 Closes: #999680 (this message was generated automatically) -- Greetings https://bugs.debian.org/999680
Processed: Bug#999680 marked as pending in criu
Processing control commands: > tag -1 pending Bug #999680 [src:criu] criu: FTBFS on armhf: cc1: error: '-mfloat-abi=hard': selected architecture lacks an FPU Added tag(s) pending. -- 999680: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=999680 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1001110: darkradiant FTBFS on 32bit: u64 is not 8 bytes
Source: darkradiant Version: 2.14.0-1 Severity: serious Tags: ftbfs https://buildd.debian.org/status/logs.php?pkg=darkradiant=2.14.0-1 ... /<>/radiantcore/model/import/openfbx/ofbx.h:21:27: error: static assertion failed: u64 is not 8 bytes 21 | static_assert(sizeof(u64) == 8, "u64 is not 8 bytes"); | ^~~~ ...
Bug#1001016: telegram-desktop backports request
Hi Nicholas, I can second that, everything is fine now! Thank you for the quick reaction! Just to have it documented somewhere, in one of the out-of-date versions I had to click the [Ok] button in the message box multiple times to activate the window after having been away for some time. I assume the message boxes were stacking, about five or ten exactly one over the other. Since the upgrade to 3.1.1 I can't reproduce this any more for lack of urgent messages, but the code may still behave the same way if it is triggered the next time and it is very confusing for users. Thank you again, Ralf On Sat, Dec 04, 2021 at 11:13:14AM +, piorunz wrote: > Hi Nicholas, > > That's fantastic, everything works ok now! Thank you! > > I set up new Firefox profile with Telegram tab just in case, put that in > place of old Telegram window, that worked for me for a day, but now I am > back to using telegram desktop app. Great work:) > > On 04/12/2021 10:45, Nicholas Guriev wrote: > > Hello! > > > > On Пт, 2021-12-03 at 19:44 +, piorunz wrote: > > > Testing has got 3.1.1. I hope bullseye-backports can update it? CC to > > > maintainer, Nicholas Guriev! Thanks in advance. > > > > I have uploaded this version to Backports. It is already available on > > mirrors and should work okay. > > https://ftp.debian.org/debian/pool/main/t/telegram-desktop/ > > > > > -- > With kindest regards, Piotr. > > ⢀⣴⠾⠻⢶⣦⠀ > ⣾⠁⢠⠒⠀⣿⡁ Debian - The universal operating system > ⢿⡄⠘⠷⠚⠋⠀ https://www.debian.org/ > ⠈⠳⣄ -- 72 61 6c 66 40 73 74 72 : 63 6d 70 2e 64 65 0a r...@strcmp.de.
Bug#1001016: telegram-desktop backports request
Hi Nicholas, That's fantastic, everything works ok now! Thank you! I set up new Firefox profile with Telegram tab just in case, put that in place of old Telegram window, that worked for me for a day, but now I am back to using telegram desktop app. Great work:) On 04/12/2021 10:45, Nicholas Guriev wrote: Hello! On Пт, 2021-12-03 at 19:44 +, piorunz wrote: Testing has got 3.1.1. I hope bullseye-backports can update it? CC to maintainer, Nicholas Guriev! Thanks in advance. I have uploaded this version to Backports. It is already available on mirrors and should work okay. https://ftp.debian.org/debian/pool/main/t/telegram-desktop/ -- With kindest regards, Piotr. ⢀⣴⠾⠻⢶⣦⠀ ⣾⠁⢠⠒⠀⣿⡁ Debian - The universal operating system ⢿⡄⠘⠷⠚⠋⠀ https://www.debian.org/ ⠈⠳⣄
Bug#1001016: telegram-desktop backports request
Hello! On Пт, 2021-12-03 at 19:44 +, piorunz wrote: > Testing has got 3.1.1. I hope bullseye-backports can update it? CC to > maintainer, Nicholas Guriev! Thanks in advance. I have uploaded this version to Backports. It is already available on mirrors and should work okay. https://ftp.debian.org/debian/pool/main/t/telegram-desktop/ signature.asc Description: This is a digitally signed message part
Bug#1001097: ksh93u+m_1.0.0~beta.1-2_all-buildd.changes REJECTED
Hi Aruelien On Sat, Dec 04, 2021 at 10:39:58AM +0100, Aurelien Jarno wrote: > Source: ksh93u+m > Version: 1.0.0~beta.1-2 > Severity: serious > > On 2021-12-03 18:48, Debian FTP Masters wrote: > > Version check failed: > > Your upload included the binary package ksh, version 20210511, for all, > > however unstable already has version 20210511. > > Uploads to unstable must have a higher version than present in unstable. > > > > Mapping sid to unstable. The version 20210511 is a transitional package from the older ksh package over to ksh93u+m [1]. According to this, is the expectation that the the transitional package version is bumped with each release of ksh93u+m, at least until the transition is complete in the next Debian release? Thanks, Anuradha [1] - https://wiki.debian.org/RenamingPackages
Processed: Re: matplotlib: python3-pil.imagetk should be Depends
Processing control commands: > severity -1 serious Bug #999533 [src:matplotlib] matplotlib: python3-pil.imagetk should be Depends Severity set to 'serious' from 'normal' -- 999533: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=999533 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1000318: marked as done (docker.io: FTBFS on mipsen: FAIL: profiles/seccomp TestUnmarshalDefaultProfile)
Your message dated Sat, 04 Dec 2021 09:48:47 +
with message-id
and subject line Bug#1000318: fixed in docker.io 20.10.11+dfsg1-2
has caused the Debian Bug report #1000318,
regarding docker.io: FTBFS on mipsen: FAIL: profiles/seccomp
TestUnmarshalDefaultProfile
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.)
--
1000318: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1000318
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: docker.io
Version: 20.10.5+dfsg1-1
Severity: serious
Justification: FTBFS - prevents depending packages from migrating
the docker.io package FTBFS on mipsen in the same way:
-
https://buildd.debian.org/status/fetch.php?pkg=docker.io=mips64el=20.10.10%2Bdfsg1-1=1636015943=0
-
https://buildd.debian.org/status/fetch.php?pkg=docker.io=mipsel=20.10.10%2Bdfsg1-1=1636015191=0
=== Failed
=== FAIL: profiles/seccomp TestUnmarshalDefaultProfile (0.15s)
seccomp_test.go:68: assertion failed:
--- expected.Syscalls
+++ profile.Syscalls
[]*seccomp.Syscall{
... // 14 identical elements
&{Names: {"clone"}, Action: "SCMP_ACT_ALLOW", Args: {&{Value:
2114060288, Op: "SCMP_CMP_MASKED_EQ"}}, Excludes: {Caps: {"CAP_SYS_ADMIN"},
Arches: {"s390", "s390x"}}},
&{Names: {"clone"}, Action: "SCMP_ACT_ALLOW", Args: {&{Index:
1, Value: 2114060288, Op: "SCMP_CMP_MASKED_EQ"}}, Comment: "s390 parameter
ordering for clone is different", ...},
&{
Name: "",
Names:{"clone3"},
Action: "SCMP_ACT_ERRNO",
- ErrnoRet: &89,
+ ErrnoRet: &38,
Args: {},
Comment: "",
... // 2 identical fields
},
&{Names: {"reboot"}, Action: "SCMP_ACT_ALLOW", Args: {},
Includes: {Caps: {"CAP_SYS_BOOT"}}, ...},
&{Names: {"chroot"}, Action: "SCMP_ACT_ALLOW", Args: {},
Includes: {Caps: {"CAP_SYS_CHROOT"}}, ...},
... // 8 identical elements
}
-- System Information:
Debian Release: bookworm/sid
APT prefers testing
APT policy: (500, 'testing'), (50, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 5.14.0-4-amd64 (SMP w/4 CPU threads)
Kernel taint flags: TAINT_DIE, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
--- End Message ---
--- Begin Message ---
Source: docker.io
Source-Version: 20.10.11+dfsg1-2
Done: Shengjing Zhu
We believe that the bug you reported is fixed in the latest version of
docker.io, 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 1000...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Shengjing Zhu (supplier of updated docker.io package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Sat, 04 Dec 2021 17:06:15 +0800
Source: docker.io
Architecture: source
Version: 20.10.11+dfsg1-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Go Packaging Team
Changed-By: Shengjing Zhu
Closes: 1000318
Changes:
docker.io (20.10.11+dfsg1-2) unstable; urgency=medium
.
* Team upload.
* Fix default seccomp on mips (Closes: #1000318)
Checksums-Sha1:
658de7b82b0cae43326560461366af2a9d4fb99e 6929 docker.io_20.10.11+dfsg1-2.dsc
0ecbd067b435fff2da1dab6cbad9a3fd86d5e055 45856
docker.io_20.10.11+dfsg1-2.debian.tar.xz
9c38f142607073de43412244568cb1aa4d3c400a 25203
docker.io_20.10.11+dfsg1-2_amd64.buildinfo
Checksums-Sha256:
9f842f2e8270e57c97b681d3d09add582ad9bc0ef7b8c366a8cbd6afcaf13912 6929
docker.io_20.10.11+dfsg1-2.dsc
7b0a7cc3ad9a0e1a1938d3700393e55454867b440c77098faddf79ea43948153 45856
docker.io_20.10.11+dfsg1-2.debian.tar.xz
a3060c73aecb683b59d1a3957072e5bddc4067d8e7274d7b43055528d93a2c58 25203
docker.io_20.10.11+dfsg1-2_amd64.buildinfo
Files:
4a257d75efdc5aa8194d4622a2495b76 6929 admin optional
Bug#1001097: ksh93u+m_1.0.0~beta.1-2_all-buildd.changes REJECTED
Source: ksh93u+m Version: 1.0.0~beta.1-2 Severity: serious On 2021-12-03 18:48, Debian FTP Masters wrote: > > > Version check failed: > Your upload included the binary package ksh, version 20210511, for all, > however unstable already has version 20210511. > Uploads to unstable must have a higher version than present in unstable. > > Mapping sid to unstable. > > === > > Please feel free to respond to this email if you don't understand why > your files were rejected, or if you upload new files which address our > concerns. > > >
Bug#997486: marked as done (pycoast: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p 3.9 returned exit code 13)
Your message dated Sat, 04 Dec 2021 08:48:37 +
with message-id
and subject line Bug#997486: fixed in pycoast 1.5.0+dfsg-2
has caused the Debian Bug report #997486,
regarding pycoast: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i
python{version} -p 3.9 returned exit code 13
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
997486: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997486
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: pycoast
Version: 1.5.0+dfsg-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):
> make[2]: Entering directory '/<>/docs'
> sphinx-build -b html -d build/doctrees -a source build/html
> Running Sphinx v4.2.0
> making output directory... done
> loading intersphinx inventory from https://docs.python.org/3/objects.inv...
> loading intersphinx inventory from
> https://docs.scipy.org/doc/numpy/objects.inv...
> loading intersphinx inventory from
> https://docs.scipy.org/doc/scipy/reference/objects.inv...
> loading intersphinx inventory from
> https://xarray.pydata.org/en/stable/objects.inv...
> loading intersphinx inventory from
> https://dask.pydata.org/en/latest/objects.inv...
> loading intersphinx inventory from
> https://pyresample.readthedocs.io/en/stable/objects.inv...
> loading intersphinx inventory from
> https://trollsift.readthedocs.io/en/stable/objects.inv...
> loading intersphinx inventory from
> https://trollimage.readthedocs.io/en/stable/objects.inv...
> loading intersphinx inventory from
> https://pillow.readthedocs.io/en/stable/objects.inv...
> intersphinx inventory has moved: https://docs.scipy.org/doc/numpy/objects.inv
> -> https://numpy.org/doc/stable/objects.inv
> intersphinx inventory has moved:
> https://dask.pydata.org/en/latest/objects.inv ->
> https://docs.dask.org/en/latest/objects.inv
> building [mo]: all of 0 po files
> building [html]: all source files
> updating environment: [new config] 11 added, 0 changed, 0 removed
> reading sources... [ 9%] api/pycoast
> reading sources... [ 18%] config
> reading sources... [ 27%] graticule
> reading sources... [ 36%] high_quality_contours
> reading sources... [ 45%] index
> reading sources... [ 54%] installation
> reading sources... [ 63%] points
> reading sources... [ 72%] polygons_and_lines
> reading sources... [ 81%] shapefiles
> reading sources... [ 90%] test
> reading sources... [100%] usage
>
> looking for now-outdated files... none found
> pickling environment... done
> checking consistency... done
> preparing documents... done
> writing output... [ 9%] api/pycoast
> writing output... [ 18%] config
> writing output... [ 27%] graticule
> writing output... [ 36%] high_quality_contours
> writing output... [ 45%] index
> writing output... [ 54%] installation
> writing output... [ 63%] points
> writing output... [ 72%] polygons_and_lines
> writing output... [ 81%] shapefiles
> writing output... [ 90%] test
> writing output... [100%] usage
>
> generating indices... genindex py-modindex done
> writing additional pages... search done
> copying images... [ 7%] images/euro_grid.png
> copying images... [ 15%] images/euro_grid_agg.png
> copying images... [ 23%] images/grid_geos_agg.png
> copying images... [ 30%] images/nh_grid_coarse_agg.png
> copying images... [ 38%] images/geos_coast_agg.png
> copying images... [ 46%] images/euro_coast_agg.png
> copying images... [ 53%] images/nh_points_agg.png
> copying images... [ 61%] images/nh_polygons_agg.png
> copying images... [ 69%] images/nh_polygons_lines_agg.png
> copying images... [ 76%] images/brazil_shapefiles_agg.png
> copying images... [ 84%] images/BMNG_clouds_201109181715_areaT2.png
> copying images... [ 92%] images/euro_coast.png
> copying images... [100%] images/geos_coast.png
>
> copying static files... done
> copying extra files... done
> dumping search index in English (code: en)... done
> dumping object inventory... done
> build succeeded.
>
> The HTML pages are in build/html.
>
> Build finished. The HTML pages are in build/html.
> make[2]: Leaving directory '/<>/docs'
> rm -f -r docs/build/html/_images
> make[1]: Leaving directory '/<>'
>dh_auto_test -O--buildsystem=pybuild
> I: pybuild base:232: cd /<>/.pybuild/cpython3_3.9_pycoast/build;
> python3.9 -m pytest /<>/pycoast/tests
> = test session starts
> ==
> platform linux -- Python 3.9.7,
