Processed: Re: opendht: Need -latomic on at least RISC-V architecture
Processing control commands: > reassign -1 src:opendht 2.1.1-1 Bug #960837 [opendht] opendht: Need -latomic on at least RISC-V architecture Bug reassigned from package 'opendht' to 'src:opendht'. No longer marked as found in versions 2.1.1-1. Ignoring request to alter fixed versions of bug #960837 to the same values previously set Bug #960837 [src:opendht] opendht: Need -latomic on at least RISC-V architecture Marked as found in versions opendht/2.1.1-1. > severity -1 serious Bug #960837 [src:opendht] opendht: Need -latomic on at least RISC-V architecture Severity set to 'serious' from 'wishlist' > tags -1 +ftbfs Bug #960837 [src:opendht] opendht: Need -latomic on at least RISC-V architecture Added tag(s) ftbfs. -- 960837: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=960837 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: your mail
Processing commands for cont...@bugs.debian.org: > fixed 938234 python-tz/2020.1-2 Bug #938234 [src:python-tz] python-tz: Python2 removal in sid/bullseye Marked as fixed in versions python-tz/2020.1-2. > End of message, stopping processing here. Please contact me if you need assistance. -- 938234: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=938234 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: your mail
Processing commands for cont...@bugs.debian.org:
> unarchive 938234
Bug #938234 {Done: Sandro Tosi } [src:python-tz] python-tz:
Python2 removal in sid/bullseye
Unarchived Bug 938234
> reopen 938234
Bug #938234 {Done: Sandro Tosi } [src:python-tz] python-tz:
Python2 removal in sid/bullseye
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
No longer marked as fixed in versions python-tz/2020.1-2.
> found 938234 python-tz/2020.4-1
Bug #938234 [src:python-tz] python-tz: Python2 removal in sid/bullseye
Marked as found in versions python-tz/2020.4-1.
>
End of message, stopping processing here.
Please contact me if you need assistance.
--
938234: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=938234
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Processed: Re: libzeep: FTBFS: 2 failures are detected in the test module "HTTP_Test"
Processing commands for cont...@bugs.debian.org:
> # Control - fix version typo and reopen
> notfound 973526 5.0.5-2
Bug #973526 {Done: maar...@hekkelman.com (Maarten L. Hekkelman)} [src:libzeep]
libzeep: FTBFS: 2 failures are detected in the test module "HTTP_Test"
The source 'libzeep' and version '5.0.5-2' do not appear to match any binary
packages
No longer marked as found in versions libzeep/5.0.5-2.
> found973526 5.0.0-2
Bug #973526 {Done: maar...@hekkelman.com (Maarten L. Hekkelman)} [src:libzeep]
libzeep: FTBFS: 2 failures are detected in the test module "HTTP_Test"
The source 'libzeep' and version '5.0.0-2' do not appear to match any binary
packages
Marked as found in versions libzeep/5.0.0-2.
> reopen 973526
Bug #973526 {Done: maar...@hekkelman.com (Maarten L. Hekkelman)} [src:libzeep]
libzeep: FTBFS: 2 failures are detected in the test module "HTTP_Test"
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
No longer marked as fixed in versions libzeep/5.0.0-3.
> stop
Stopping processing here.
Please contact me if you need assistance.
--
973526: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=973526
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#973526: libzeep: FTBFS: 2 failures are detected in the test module "HTTP_Test"
# Control - fix version typo and reopen notfound 973526 5.0.5-2 found973526 5.0.0-2 reopen 973526 stop # Hi, libzeep 5.0.0-3 failed to build in the same manner as 5.0.0-2 on amd64 this time, see the log https://buildd.debian.org/status/fetch.php?pkg=libzeep=amd64=5.0.0-3=1604607341=0 [0;39;49m>> test/http-test.cpp test/http-test.cpp: In member function ‘void connection_read::test_method()’: test/http-test.cpp:74:17: note: ‘#pragma message: write test for avail/used’ 74 | #pragma message "write test for avail/used" | ^~~ >>> building http-test cd test; ./http-test Running 7 test cases... started daemon at port 5923 terminate called after throwing an instance of 'boost::wrapexcept' what(): resolve: Host not found (authoritative) unknown location(0): [4;31;49mfatal error: in "webapp_7": signal: SIGABRT (application abort requested)[0;39;49m test/http-test.cpp(122): [1;36;49mlast checkpoint: "webapp_7" test entry[0;39;49m started daemon at port 3364 terminate called recursively unknown location(0): [4;31;49mfatal error: in "server_with_security_1": signal: SIGABRT (application abort requested)[0;39;49m test/http-test.cpp(159): [1;36;49mlast checkpoint: "server_with_security_1" test entry[0;39;49m Regards, Juhani
Processed: Re: Bug#973467: vmdb2 tries to install grub-pc or grub-efi-amd64 on arm64 and does not work on arm64
Processing commands for cont...@bugs.debian.org: > tags 973467 - patch Bug #973467 [vmdb2] vmdb2 tries to install grub-pc or grub-efi-amd64 and does not work on arm64 nor grub-efi-ia32 Removed tag(s) patch. > tags 973467 + confirmed upstream Bug #973467 [vmdb2] vmdb2 tries to install grub-pc or grub-efi-amd64 and does not work on arm64 nor grub-efi-ia32 Added tag(s) upstream and confirmed. > severity 973467 important Bug #973467 [vmdb2] vmdb2 tries to install grub-pc or grub-efi-amd64 and does not work on arm64 nor grub-efi-ia32 Severity set to 'important' from 'grave' > thanks Stopping processing here. Please contact me if you need assistance. -- 973467: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=973467 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#973467: vmdb2 tries to install grub-pc or grub-efi-amd64 on arm64 and does not work on arm64
tags 973467 - patch
tags 973467 + confirmed upstream
severity 973467 important
thanks
Hello Ryutaroh,
As you said here, the workaround is not a fix, as it would make vmdb2
produce images unable to boot on amd64 - So I'm removing the "patch"
tag. I am also adding the tags "confirmed" and "upstream", as the
comments in the file in question mention:
# Note that this is currently rather strongly assuming that UEFI and
# the amd64 (a.k.a. x86_64) architecture are being used. These should
# probably not be hardcoded. Patch welcome.
I will be taking this issue with upstream author, I think the patch is
somewhat trivial, but given I lack any hardware to test it, I will not
commit a fix without his approval.
Finally, I am downgrading the severity to "important", as I judge this
bug to be "a bug which has a major effect on the usability of a
package, without rendering it completely unusable to everyone"¹. It
does not completely render vmdb2 useless, not even for the arm64
architecture (for which I use it on a daily basis!) - Just for arm64
machines that boot via UEFI.
¹ https://www.debian.org/Bugs/Developer#severities
Greetings,
Ryutaroh Matsumoto dijo [Sat, Oct 31, 2020 at 02:32:27PM +0900]:
> Control: tags -1 + patch
>
> The following workaround (NOT A FIX AT ALL) let vmdb2 work for my arm64...
>
> --- usr/lib/python3/dist-packages/vmdb/plugins/grub_plugin.py-orig
> 2020-10-31 12:47:04.796899268 +0900
> +++ usr/lib/python3/dist-packages/vmdb/plugins/grub_plugin.py 2020-10-31
> 12:50:00.322817935 +0900
> @@ -112,8 +112,8 @@
> raise Exception('"efi" or "efi-part" required in UEFI GRUB
> installation')
>
> vmdb.progress("Installing GRUB for UEFI")
> -grub_package = "grub-efi-amd64"
> -grub_target = "x86_64-efi"
> +grub_package = "grub-efi-arm64"
> +grub_target = "arm64-efi"
> self.install_grub(values, settings, state, grub_package, grub_target)
>
> def install_bios(self, values, settings, state):
>
--
Bug#972682: marked as done (breezy fails tests (already with Python 3.8, not yet tested with 3.9))
Your message dated Sun, 08 Nov 2020 05:18:26 +
with message-id
and subject line Bug#972682: fixed in breezy 3.1.0-6
has caused the Debian Bug report #972682,
regarding breezy fails tests (already with Python 3.8, not yet tested with 3.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.)
--
972682: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=972682
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:breezy
Version: 3.1.0-5
Severity: serious
Tags: sid bullseye
User: debian-pyt...@lists.debian.org
Usertags: python3.9
breezy fails tests (already with Python 3.8, not yet tested with 3.9)
[...]
==
ERROR: breezy.git.tests.test_remote.ParseHangupTests.test_filter_boring
--
Traceback (most recent call last):
testtools.testresult.real._StringException: Empty attachments:
log
Traceback (most recent call last):
File "/<>/breezy/git/tests/test_remote.py", line 154, in setUp
HangupException(['foo'])
File "/usr/lib/python3/dist-packages/dulwich/errors.py", line 146, in __init__
[line.decode('utf-8', 'surrogateescape')
File "/usr/lib/python3/dist-packages/dulwich/errors.py", line 146, in
[line.decode('utf-8', 'surrogateescape')
AttributeError: 'str' object has no attribute 'decode'
==
ERROR: breezy.git.tests.test_remote.ParseHangupTests.test_multi_lines
--
Traceback (most recent call last):
testtools.testresult.real._StringException: Empty attachments:
log
Traceback (most recent call last):
File "/<>/breezy/git/tests/test_remote.py", line 154, in setUp
HangupException(['foo'])
File "/usr/lib/python3/dist-packages/dulwich/errors.py", line 146, in __init__
[line.decode('utf-8', 'surrogateescape')
File "/usr/lib/python3/dist-packages/dulwich/errors.py", line 146, in
[line.decode('utf-8', 'surrogateescape')
AttributeError: 'str' object has no attribute 'decode'
==
ERROR: breezy.git.tests.test_remote.ParseHangupTests.test_not_set
--
Traceback (most recent call last):
testtools.testresult.real._StringException: Empty attachments:
log
Traceback (most recent call last):
File "/<>/breezy/git/tests/test_remote.py", line 154, in setUp
HangupException(['foo'])
File "/usr/lib/python3/dist-packages/dulwich/errors.py", line 146, in __init__
[line.decode('utf-8', 'surrogateescape')
File "/usr/lib/python3/dist-packages/dulwich/errors.py", line 146, in
[line.decode('utf-8', 'surrogateescape')
AttributeError: 'str' object has no attribute 'decode'
==
ERROR: breezy.git.tests.test_remote.ParseHangupTests.test_permission_denied
--
Traceback (most recent call last):
testtools.testresult.real._StringException: Empty attachments:
log
Traceback (most recent call last):
File "/<>/breezy/git/tests/test_remote.py", line 154, in setUp
HangupException(['foo'])
File "/usr/lib/python3/dist-packages/dulwich/errors.py", line 146, in __init__
[line.decode('utf-8', 'surrogateescape')
File "/usr/lib/python3/dist-packages/dulwich/errors.py", line 146, in
[line.decode('utf-8', 'surrogateescape')
AttributeError: 'str' object has no attribute 'decode'
==
ERROR: breezy.git.tests.test_remote.ParseHangupTests.test_single_line
--
Traceback (most recent call last):
testtools.testresult.real._StringException: Empty attachments:
log
Traceback (most recent call last):
File "/<>/breezy/git/tests/test_remote.py", line 154, in setUp
HangupException(['foo'])
File "/usr/lib/python3/dist-packages/dulwich/errors.py", line 146, in __init__
[line.decode('utf-8', 'surrogateescape')
File "/usr/lib/python3/dist-packages/dulwich/errors.py", line 146, in
[line.decode('utf-8', 'surrogateescape')
AttributeError: 'str' object has no attribute 'decode'
--
Ran 31584 tests in 1955.670s
FAILED (errors=5, known_failure_count=68)
2061 tests skipped
Missing feature 'Filesystem treats '\' as a directory
Bug#973767: marked as done (dolfin FTBFS: The MPI_Comm_rank() function was called before MPI_INIT was invoked.)
Your message dated Sun, 08 Nov 2020 11:18:12 +0800 with message-id and subject line Re: dolfin FTBFS: The MPI_Comm_rank() function was called before MPI_INIT was invoked. has caused the Debian Bug report #973767, regarding dolfin FTBFS: The MPI_Comm_rank() function was called before MPI_INIT was invoked. 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.) -- 973767: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=973767 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: dolfin Version: 2019.2.0~git20200629.946dbd3-3 Severity: serious Tags: ftbfs https://buildd.debian.org/status/package.php?p=dolfin ... 3/51 Test #13: demo_eigenvalue_serial ***Failed0.02 sec *** The MPI_Comm_rank() function was called before MPI_INIT was invoked. *** This is disallowed by the MPI standard. *** Your MPI job will now abort. [x86-csail-01:13764] Local abort before MPI_INIT completed completed successfully, but am not able to aggregate error messages, and not able to guarantee that all other processes were killed! ... 48/51 Test #101: demo_waveguide_serial .***Failed0.02 sec *** The MPI_Comm_rank() function was called before MPI_INIT was invoked. *** This is disallowed by the MPI standard. *** Your MPI job will now abort. [x86-csail-01:15044] Local abort before MPI_INIT completed completed successfully, but am not able to aggregate error messages, and not able to guarantee that all other processes were killed! ... The following tests FAILED: 13 - demo_eigenvalue_serial (Failed) 101 - demo_waveguide_serial (Failed) Errors while running CTest make[1]: *** [debian/rules:237: override_dh_auto_test-arch] Error 8 --- End Message --- --- Begin Message --- Control: reassign 973767 src:slepc 3.14.0+dfsg1-1 Control: fixed 973767 3.14.0+dfsg1-4 dolfin is now building again with slepc 3.14.0+dfsg1-4--- End Message ---
Bug#973628: marked as done (nitrokey-authenticator: icon clashes with nitrokey-app)
Your message dated Sun, 08 Nov 2020 00:34:10 + with message-id and subject line Bug#973628: fixed in nitrokey-authenticator 1.1-1 has caused the Debian Bug report #973628, regarding nitrokey-authenticator: icon clashes with nitrokey-app 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.) -- 973628: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=973628 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: nitrokey-authenticator Version: 1.0-2 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package failed to install because it tries to overwrite other packages files. >From the attached log (scroll to the bottom...): Selecting previously unselected package nitrokey-authenticator. Preparing to unpack .../9-nitrokey-authenticator_1.0-2+b1_amd64.deb ... Unpacking nitrokey-authenticator (1.0-2+b1) ... dpkg: error processing archive /tmp/apt-dpkg-install-4dNd2a/9-nitrokey-authenticator_1.0-2+b1_amd64.deb (--unpack): trying to overwrite '/usr/share/icons/hicolor/128x128/apps/nitrokey-app.png', which is also in package nitrokey-app 1.4.1-1 Errors were encountered while processing: /tmp/apt-dpkg-install-4dNd2a/9-nitrokey-authenticator_1.0-2+b1_amd64.deb These files are shipped by both packages: usr/share/icons/hicolor/128x128/apps/nitrokey-app.png usr/share/icons/hicolor/16x16/apps/nitrokey-app.png usr/share/icons/hicolor/22x22/apps/nitrokey-app.png usr/share/icons/hicolor/24x24/apps/nitrokey-app.png usr/share/icons/hicolor/32x32/apps/nitrokey-app.png usr/share/icons/hicolor/48x48/apps/nitrokey-app.png usr/share/icons/hicolor/scalable/apps/nitrokey-app.svg cheers, Andreas nitrokey-app=1.4.1-1_nitrokey-authenticator=1.0-2+b1.log.gz Description: application/gzip --- End Message --- --- Begin Message --- Source: nitrokey-authenticator Source-Version: 1.1-1 Done: Patryk Cisek We believe that the bug you reported is fixed in the latest version of nitrokey-authenticator, 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 973...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Patryk Cisek (supplier of updated nitrokey-authenticator 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, 07 Nov 2020 16:04:52 -0800 Source: nitrokey-authenticator Binary: nitrokey-authenticator nitrokey-authenticator-dbgsym Architecture: source amd64 Version: 1.1-1 Distribution: unstable Urgency: medium Maintainer: Patryk Cisek Changed-By: Patryk Cisek Description: nitrokey-authenticator - TOTP authenticator app that's using Nitrokey Pro2 and/or LibremKe Closes: 973628 Changes: nitrokey-authenticator (1.1-1) unstable; urgency=medium . * New upstream release (Closes: #973628) Checksums-Sha1: 73a21c1d1383c9cfa314b30a03781d3e82c4c9d6 1755 nitrokey-authenticator_1.1-1.dsc 27d779907ca877606ea0516a09e4eac0aa69bb33 96003 nitrokey-authenticator_1.1.orig.tar.bz2 225d38dcbc183e4f205d1e62b6c151d0ae60e197 3100 nitrokey-authenticator_1.1-1.debian.tar.xz bde3f3aa7454c254a46bc967b734dc90d7093388 2428488 nitrokey-authenticator-dbgsym_1.1-1_amd64.deb 96d6cfee8a4a30bddc4682094336d5d7f90606c3 16301 nitrokey-authenticator_1.1-1_amd64.buildinfo ac7e72274260b3d5e8f19b5a946701e086ea849e 102608 nitrokey-authenticator_1.1-1_amd64.deb Checksums-Sha256: e007e871c101ee2ce3652df6b1323282c1dbe3f17a8c871d6e48a825a6e12787 1755 nitrokey-authenticator_1.1-1.dsc 9172298ad11e1f88df86d3b47344f94f95c544ab50a0eef8af5f39ca5db4cc60 96003 nitrokey-authenticator_1.1.orig.tar.bz2 a68cadc00641041f97d7f5d1e9e5d1230ee523dff64cc40627d51adcd06c82dc 3100 nitrokey-authenticator_1.1-1.debian.tar.xz d0b07c1505fea1c1715241681eefa295af5e140cbb402caae41744ce26648f1f 2428488 nitrokey-authenticator-dbgsym_1.1-1_amd64.deb 0792ec7576d9c7a7ef3712fb505a434e773141f8c7763aeb8a087a856bab2fcb 16301 nitrokey-authenticator_1.1-1_amd64.buildinfo 19fabf85194b0cd3572efc4e57e891c4581995f40798d13339c6f614a628bfeb 102608 nitrokey-authenticator_1.1-1_amd64.deb Files: bf8225a80bef3c3aa4dfc163a8b3b637 1755 utils optional nitrokey-authenticator_1.1-1.dsc
Bug#966922: libnitrokey: FTBFS: dpkg-gensymbols: error: some symbols or patterns disappeared in the symbols file: see diff output below
I have uploaded an NMU fix to DELAYED/10 earlier today. Please, see the last 2 commits on top of the following for details: https://salsa.debian.org/patryk/libnitrokey
Bug#973217: marked as done (python-fedora: FTBFS: dh_auto_test: error: pybuild --test --test-nose -i python{version} -p "3.9 3.8" returned exit code 13)
Your message dated Sat, 07 Nov 2020 22:48:52 +
with message-id
and subject line Bug#973217: fixed in python-fedora 1.1.0-1
has caused the Debian Bug report #973217,
regarding python-fedora: FTBFS: dh_auto_test: error: pybuild --test --test-nose
-i python{version} -p "3.9 3.8" 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.)
--
973217: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=973217
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-fedora
Version: 0.10.0-2
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20201027 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 '/<>'
> dh_auto_build
> I: pybuild base:217: /usr/bin/python3.9 setup.py build
> running build
> running build_py
> file flask_fas.py (for module flask_fas) not found
> copying flask_fas_openid.py ->
> /<>/.pybuild/cpython3_3.9_fedora/build
> creating /<>/.pybuild/cpython3_3.9_fedora/build/tests
> copying tests/__init__.py ->
> /<>/.pybuild/cpython3_3.9_fedora/build/tests
> copying tests/test_urlutils.py ->
> /<>/.pybuild/cpython3_3.9_fedora/build/tests
> creating /<>/.pybuild/cpython3_3.9_fedora/build/fedora
> copying fedora/iterutils.py ->
> /<>/.pybuild/cpython3_3.9_fedora/build/fedora
> copying fedora/__init__.py ->
> /<>/.pybuild/cpython3_3.9_fedora/build/fedora
> copying fedora/urlutils.py ->
> /<>/.pybuild/cpython3_3.9_fedora/build/fedora
> copying fedora/textutils.py ->
> /<>/.pybuild/cpython3_3.9_fedora/build/fedora
> copying fedora/release.py ->
> /<>/.pybuild/cpython3_3.9_fedora/build/fedora
> creating /<>/.pybuild/cpython3_3.9_fedora/build/tests/functional
> copying tests/functional/__init__.py ->
> /<>/.pybuild/cpython3_3.9_fedora/build/tests/functional
> copying tests/functional/test_openidbaseclient.py ->
> /<>/.pybuild/cpython3_3.9_fedora/build/tests/functional
> copying tests/functional/functional_test_utils.py ->
> /<>/.pybuild/cpython3_3.9_fedora/build/tests/functional
> creating /<>/.pybuild/cpython3_3.9_fedora/build/fedora/tg2
> copying fedora/tg2/__init__.py ->
> /<>/.pybuild/cpython3_3.9_fedora/build/fedora/tg2
> copying fedora/tg2/utils.py ->
> /<>/.pybuild/cpython3_3.9_fedora/build/fedora/tg2
> creating /<>/.pybuild/cpython3_3.9_fedora/build/fedora/client
> copying fedora/client/openidproxyclient.py ->
> /<>/.pybuild/cpython3_3.9_fedora/build/fedora/client
> copying fedora/client/baseclient.py ->
> /<>/.pybuild/cpython3_3.9_fedora/build/fedora/client
> copying fedora/client/__init__.py ->
> /<>/.pybuild/cpython3_3.9_fedora/build/fedora/client
> copying fedora/client/openidbaseclient.py ->
> /<>/.pybuild/cpython3_3.9_fedora/build/fedora/client
> copying fedora/client/proxyclient.py ->
> /<>/.pybuild/cpython3_3.9_fedora/build/fedora/client
> copying fedora/client/bodhi.py ->
> /<>/.pybuild/cpython3_3.9_fedora/build/fedora/client
> copying fedora/client/fas2.py ->
> /<>/.pybuild/cpython3_3.9_fedora/build/fedora/client
> copying fedora/client/fasproxy.py ->
> /<>/.pybuild/cpython3_3.9_fedora/build/fedora/client
> copying fedora/client/wiki.py ->
> /<>/.pybuild/cpython3_3.9_fedora/build/fedora/client
> copying fedora/client/openidcclient.py ->
> /<>/.pybuild/cpython3_3.9_fedora/build/fedora/client
> creating /<>/.pybuild/cpython3_3.9_fedora/build/fedora/tg
> copying fedora/tg/tg1utils.py ->
> /<>/.pybuild/cpython3_3.9_fedora/build/fedora/tg
> copying fedora/tg/controllers.py ->
> /<>/.pybuild/cpython3_3.9_fedora/build/fedora/tg
> copying fedora/tg/tg2utils.py ->
> /<>/.pybuild/cpython3_3.9_fedora/build/fedora/tg
> copying fedora/tg/widgets.py ->
> /<>/.pybuild/cpython3_3.9_fedora/build/fedora/tg
> copying fedora/tg/__init__.py ->
> /<>/.pybuild/cpython3_3.9_fedora/build/fedora/tg
> copying fedora/tg/json.py ->
> /<>/.pybuild/cpython3_3.9_fedora/build/fedora/tg
> copying fedora/tg/util.py ->
> /<>/.pybuild/cpython3_3.9_fedora/build/fedora/tg
> copying fedora/tg/client.py ->
> /<>/.pybuild/cpython3_3.9_fedora/build/fedora/tg
> copying fedora/tg/utils.py ->
> /<>/.pybuild/cpython3_3.9_fedora/build/fedora/tg
> creating /<>/.pybuild/cpython3_3.9_fedora/build/fedora/wsgi
> copying fedora/wsgi/__init__.py ->
> /<>/.pybuild/cpython3_3.9_fedora/build/fedora/wsgi
> copying fedora/wsgi/csrf.py ->
> /<>/.pybuild/cpython3_3.9_fedora/build/fedora/wsgi
> creating /<>/.pybuild/cpython3_3.9_fedora/build/fedora/django
> copying fedora/django/__init__.py ->
>
Bug#973939: ismrmrd: binary-all FTBFS
Source: ismrmrd Version: 1.4.2.1-2 Severity: serious Tags: ftbfs https://buildd.debian.org/status/fetch.php?pkg=ismrmrd=all=1.4.2.1-2=1604772139=0 ... dh_auto_install -i cd obj-x86_64-linux-gnu && make -j4 install DESTDIR=/<>/debian/tmp AM_UPDATE_INFO_DIR=no "INSTALL=install --strip-program=true" make[1]: Entering directory '/<>/obj-x86_64-linux-gnu' /usr/bin/cmake -S/<> -B/<>/obj-x86_64-linux-gnu --check-build-system CMakeFiles/Makefile.cmake 0 make -f CMakeFiles/Makefile2 preinstall make[2]: Entering directory '/<>/obj-x86_64-linux-gnu' make[2]: Nothing to be done for 'preinstall'. make[2]: Leaving directory '/<>/obj-x86_64-linux-gnu' Install the project... /usr/bin/cmake -P cmake_install.cmake -- Install configuration: "None" -- Installing: /<>/debian/tmp/usr/include/ismrmrd/version.h -- Installing: /<>/debian/tmp/usr/lib/x86_64-linux-gnu/libismrmrd.so.1.4.2 -- Installing: /<>/debian/tmp/usr/lib/x86_64-linux-gnu/libismrmrd.so.1.4 -- Set runtime path of "/<>/debian/tmp/usr/lib/x86_64-linux-gnu/libismrmrd.so.1.4.2" to "" -- Installing: /<>/debian/tmp/usr/lib/x86_64-linux-gnu/libismrmrd.so CMake Error at cmake_install.cmake:103 (file): file INSTALL cannot find "/<>/obj-x86_64-linux-gnu/libismrmrd.a": No such file or directory. make[1]: *** [Makefile:119: install] Error 1
Bug#973938: libismrmrd1.4: Missing Breaks+Replaces: libismrmrd1.3
Package: libismrmrd1.4 Version: 1.4.2.1-2 Severity: serious Unpacking libismrmrd1.4:amd64 (1.4.2.1-2) ... dpkg: error processing archive /tmp/apt-dpkg-install-onDkpV/15-libismrmrd1.4_1.4.2.1-2_amd64.deb (--unpack): trying to overwrite '/usr/lib/x86_64-linux-gnu/libismrmrd.so.1.4', which is also in package libismrmrd1.3:amd64 1.4.0-1+b2
Bug#973927: incron SEGV when monitoring directories
Package: incron
Version: 0.5.12-1+deb10u1
Severity: grave
Justification: renders package unusable
Dear Maintainer,
Incrond crashes with SIGSEGV when monitoring IN_CREATE event in a directory and
a new directory is created inside the monitored dir.
How to reproduce :
su -
apt-get install incrond
echo root >/etc/incron.allow
echo '/home IN_CREATE,recursive=false /root/scripts/first-try $@ $#' |
incrontab -u root -
touch /home/foo-$RANDOM # this does not crash incrond
mkdir /home/foo-$RANDOM # this crashes incrond
Here is an strace output on the incrond daemon :
poll([{fd=4, events=POLLIN}, {fd=6, events=POLLIN}, {fd=8, events=POLLIN}],
3, -1) = ? ERESTART_RESTARTBLOCK (Interrupted by signal)
--- SIGCONT {si_signo=SIGCONT, si_code=SI_USER, si_pid=18788, si_uid=0} ---
restart_syscall(<... resuming interrupted poll ...>) = 1
read(8, "\1\0\0\0\0\1\0@\0\0\0\0\20\0\0\0foo-5175\0\0\0\0\0\0\0\0", 32768) =
32
stat("/home", {st_mode=S_IFDIR|0755, st_size=4096, ...}) = 0
getpid()= 20473
sendto(3, "<78>Nov 7 17:15:47 incrond[20473]: PATH (/home) FILE (foo-5175)
EVENT (IN_CREATE,IN_ISDIR)", 91, MSG_NOSIGNAL, NULL, 0) = 91
inotify_rm_watch(8, 1) = 0
nanosleep({tv_sec=1, tv_nsec=0}, 0x7ffe411006b0) = 0
openat(AT_FDCWD, "/var/spool/incron/root", O_RDONLY) = 7
fstat(7, {st_mode=S_IFREG|0600, st_size=62, ...}) = 0
read(7, "/home\tIN_CREATE,recursive=false\t/root/scripts/first-try $@ $#\n",
4096) = 62
read(7, "", 4096) = 0
close(7)= 0
stat("/home", {st_mode=S_IFDIR|0755, st_size=4096, ...}) = 0
inotify_add_watch(8, "/home", IN_CREATE) = 2
mmap(NULL, 135168, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) =
0x7f38a9f0
--- SIGSEGV {si_signo=SIGSEGV, si_code=SEGV_ACCERR, si_addr=0x7f38aa9ec000}
---
+++ killed by SIGSEGV +++
I'm not completely sure this is the same as #947425 . Sorry if this is the case.
-- System Information:
Debian Release: 10.6
APT prefers stable
APT policy: (500, 'stable')
Architecture: amd64 (x86_64)
Kernel: Linux 4.19.0-12-amd64 (SMP w/2 CPU cores)
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8),
LANGUAGE=fr_FR.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages incron depends on:
ii adduser 3.118
ii init-system-helpers 1.56+nmu1
ii libc62.28-10
ii libgcc1 1:8.3.0-6
ii libstdc++6 8.3.0-6
ii lsb-base 10.2019051400
incron recommends no packages.
incron suggests no packages.
-- Configuration Files:
/etc/incron.allow [Errno 13] Permission non accordée: '/etc/incron.allow'
/etc/incron.deny [Errno 13] Permission non accordée: '/etc/incron.deny'
-- no debconf information
Bug#972334: marked as done (llvm-toolchain-11: autopkgtest failure on i386: integration-test-suite-test FAIL non-zero exit status 2)
Your message dated Sat, 07 Nov 2020 20:48:53 + with message-id and subject line Bug#972334: fixed in llvm-toolchain-11 1:11.0.0-5 has caused the Debian Bug report #972334, regarding llvm-toolchain-11: autopkgtest failure on i386: integration-test-suite-test FAIL non-zero exit status 2 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.) -- 972334: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=972334 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: llvm-toolchain-11 Version: 1:11.0.0-2 Severity: serious The autopkgtest for i386 currently fail: | | Failed Tests (4): | LLVM regression suite :: basic_lldb.c | LLVM regression suite :: basic_lldb2.cpp | LLVM regression suite :: test_asan_lc.c | LLVM regression suite :: test_tsan.c | | | Testing Time: 13.96s | Unsupported: 3 | Passed : 18 | Failed : 4 See https://ci.debian.net/data/autopkgtest/testing/i386/l/llvm-toolchain-11/7487758/log.gz for the full log Cheers -- Sebastian Ramacher --- End Message --- --- Begin Message --- Source: llvm-toolchain-11 Source-Version: 1:11.0.0-5 Done: Sylvestre Ledru We believe that the bug you reported is fixed in the latest version of llvm-toolchain-11, 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 972...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Sylvestre Ledru (supplier of updated llvm-toolchain-11 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, 07 Nov 2020 15:53:51 +0100 Source: llvm-toolchain-11 Architecture: source Version: 1:11.0.0-5 Distribution: unstable Urgency: medium Maintainer: LLVM Packaging Team Changed-By: Sylvestre Ledru Closes: 972334 Changes: llvm-toolchain-11 (1:11.0.0-5) unstable; urgency=medium . [ Adrian Bunk ] * Fix the fuzzer build on i386. . [ Sylvestre Ledru ] * Ignore some tests on i386 to get autopkgtest fixed (Closes: #972334) Checksums-Sha1: 29a503194cdfe4ebd1dafea380eafd8519f91b5c 6004 llvm-toolchain-11_11.0.0-5.dsc 5e95ec7b551037c6c94f11bd7de79e0e1faaf442 129244 llvm-toolchain-11_11.0.0-5.debian.tar.xz 20a6edd18972115bedddf11e1ac6bff7fd03b1f4 12330 llvm-toolchain-11_11.0.0-5_source.buildinfo Checksums-Sha256: 517bd1b5089dd857e1247179df62ebcf858a26a5247efcee66e0b62e968b9e64 6004 llvm-toolchain-11_11.0.0-5.dsc babe13a14a3539ea090f495f76309ee03b16edac4cf4bb78a2e43646bd05f0ac 129244 llvm-toolchain-11_11.0.0-5.debian.tar.xz ddaa420a837966ba878a3839f4ee0a0e97a8215854dd0dc84fdaaafbf405012e 12330 llvm-toolchain-11_11.0.0-5_source.buildinfo Files: e5376f96daa4868c2f6baa85941b8416 6004 devel optional llvm-toolchain-11_11.0.0-5.dsc aa20b40082e90af4e29e53e2fbdc6554 129244 devel optional llvm-toolchain-11_11.0.0-5.debian.tar.xz 60b3bc5683bd27fcac77075dadc133d6 12330 devel optional llvm-toolchain-11_11.0.0-5_source.buildinfo -BEGIN PGP SIGNATURE- iQJJBAEBCAAzFiEEtg21mU05vsTRqVzPfmUo2nUvG+EFAl+nArcVHHN5bHZlc3Ry ZUBkZWJpYW4ub3JnAAoJEH5lKNp1Lxvh6XUQAJxXeN/48G/s337wcsy2IzkXQ8tY lTJ3VzHlSXWx7gmsw8GrfK/q7vkmCTFEN66m+UW1xosJ0j1HX+fVXNrJmE0D7YDd nQjGy9vi+ux5olucudxQ/qpPPXd6YVkqMXUnj1ES6yAneWQAjpJ4Fnw/e7s+RvIt PQHQpyXaeWsanFLG3svaw46RSW5OEBuhwLHqAcezVOfLx2OAuw6m27dzwf9CgEGA PF+I/aW+dcqtpSCyRR/bOJU+mgpoAgQyYXxuWPaiuMmFTpUu05ngqgENVfPqedKa 2avuVnFPAmPfR/2LbqU5vrfZ5BBZiTUZNvhnLPUCnk52aHrlmR4ytjOswaANxLi0 Ia+MSTw2WSDAcHrRTDsMUDOhl2t1BgajMogQhti19GW4pV3tdYZQ1b2Y5xHkEzVG nQ14SbAYeKM7xSGSBJHow7eZ8EATjMVprHyTVMDntmz4K96XS6vrhwpj0gEuoUFy ShJ3fh8yUhqFDgcZAmybgi0BlXbFNFpVS5lFFJ1FlVTXHaluPv8R87UPM47s8nQt c9kuoSlExqgWvIyCIaSolRyDwkgHmg1PIzZlQsryaMa6VnYORyx47huzSjwUFGgK o6Gc+oZ7v7h3RripkslpZxd8bDrhU3u6oTXEb4BImFKj3tbyD2yi3VDZYAcK+e5c qcU8e14eYvTC/EuO =YApX -END PGP SIGNATURE End Message ---
Processed: fixed 972829 in 1.41.1+dfsg1-1
Processing commands for cont...@bugs.debian.org: > fixed 972829 1.41.1+dfsg1-1 Bug #972829 [rust-lldb] rust-lldb, depends on nonexistent package in buster. Marked as fixed in versions rustc/1.41.1+dfsg1-1. > thanks Stopping processing here. Please contact me if you need assistance. -- 972829: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=972829 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: notfound 972829 in 1.41.1+dfsg1-1
Processing commands for cont...@bugs.debian.org: > notfound 972829 1.41.1+dfsg1-1 Bug #972829 [rust-lldb] rust-lldb, depends on nonexistent package in buster. Ignoring request to alter found versions of bug #972829 to the same values previously set > thanks Stopping processing here. Please contact me if you need assistance. -- 972829: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=972829 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: tagging 972829
Processing commands for cont...@bugs.debian.org: > tags 972829 + buster Bug #972829 [rust-lldb] rust-lldb, depends on nonexistent package in buster. Added tag(s) buster. > thanks Stopping processing here. Please contact me if you need assistance. -- 972829: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=972829 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#973933: sddm: auth:sddm-helper exited with 1
Package: sddm Version: 0.19.0-1 Severity: grave Justification: renders package unusable Dear Maintainer, after upgrade to version 0.19.0-1 I can't log in to my window manager (I use Openbox). After running sysmtectl restart sddm.service in a virtual terminal there's this message: auth:sddm-helper exited with 1. Regards. -- System Information: Debian Release: bullseye/sid APT prefers buster APT policy: (500, 'buster'), (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 5.9.0-1-amd64 (SMP w/8 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 /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages sddm depends on: ii adduser 3.118 ii debconf [debconf-2.0] 1.5.74 ii libc6 2.31-4 ii libgcc-s1 10.2.0-16 ii libpam0g 1.3.1-5 ii libqt5core5a 5.15.1+dfsg-2 ii libqt5dbus5 5.15.1+dfsg-2 ii libqt5gui55.15.1+dfsg-2 ii libqt5network55.15.1+dfsg-2 ii libqt5qml55.15.1+dfsg-3 ii libqt5quick5 5.15.1+dfsg-3 ii libstdc++610.2.0-16 ii libsystemd0 246.6-2 ii libxcb-xkb1 1.14-2 ii libxcb1 1.14-2 ii qml-module-qtquick2 5.15.1+dfsg-3 ii tigervnc-standalone-server [xserver] 1.10.1+dfsg-9 ii x11-common1:7.7+21 ii xauth 1:1.0.10-1 ii xserver-xephyr [xserver] 2:1.20.9-2 ii xserver-xorg [xserver]1:7.7+21 ii xvfb [xserver]2:1.20.9-2 Versions of packages sddm recommends: pn haveged ii libpam-systemd 246.6-2 ii sddm-theme-debian-maui [sddm-theme] 0.19.0-1 Versions of packages sddm suggests: ii libpam-kwallet5 5.19.5-3 pn qtvirtualkeyboard-plugin -- debconf information: * shared/default-x-display-manager: lightdm sddm/daemon_name: /usr/bin/sddm
Bug#973187: marked as done (company-mode: FTBFS: tests failed)
Your message dated Sat, 07 Nov 2020 19:33:34 + with message-id and subject line Bug#973187: fixed in company-mode 0.9.13-1 has caused the Debian Bug report #973187, regarding company-mode: FTBFS: tests failed to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 973187: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=973187 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: company-mode Version: 0.9.9-2 Severity: serious Justification: FTBFS on amd64 Tags: bullseye sid ftbfs Usertags: ftbfs-20201027 ftbfs-bullseye Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[2]: Entering directory '/<>' > emacs -Q --batch -L . -l test/all.el \ > --eval "(ert-run-tests-batch-and-exit '(not (tag interactive)))" > Running 103 tests (2020-10-27 12:30:11+, selector ‘(not (tag > interactive))’) >passed1/103 company--manual-prefix-set-and-unset (0.041435 sec) >passed2/103 company-abort-manual-when-too-short (0.82 sec) >passed3/103 company-auto-complete-explicit (0.000251 sec) >passed4/103 company-auto-complete-with-electric-pair (0.000873 sec) >passed5/103 company-backspace-into-bad-prefix (0.000163 sec) >passed6/103 company-basic-capf (0.001290 sec) >passed7/103 company-basic-capf-highlighting (0.001817 sec) >passed8/103 company-bbdb-prefix-begins-after-comma-or-semi (0.88 > sec) >passed9/103 company-bbdb-prefix-includes-space (0.61 sec) >passed 10/103 company-bbdb-prefix-looks-in-header-value (0.58 sec) >passed 11/103 > company-begin-backend-failure-doesnt-break-company-backends (0.000166 sec) >passed 12/103 company-call-backend-errors-on-timeout (0.120434 sec) >passed 13/103 company-call-backend-forces-sync (0.060233 sec) >passed 14/103 company-call-backend-raw-passes-return-value-verbatim > (0.65 sec) >passed 15/103 company-clang-anon-union-annotation (0.77 sec) >passed 16/103 company-clang-func-ptr-annotation (0.97 sec) >passed 17/103 company-clang-generic-annotation (0.74 sec) >passed 18/103 company-clang-null-annotation (0.58 sec) > Mark set >passed 19/103 company-clang-objc-templatify-empty-args (0.000151 sec) >passed 20/103 company-clang-simple-annotation (0.65 sec) >passed 21/103 company-clears-explicit-action-when-no-matches (0.000144 > sec) >passed 22/103 company-cmake-complete-in-string-more-prefix (0.99 > sec) >passed 23/103 company-cmake-complete-in-string-more-prefix-2 (0.76 > sec) >passed 24/103 company-cmake-complete-in-string-prefix-quotes (0.76 > sec) >passed 25/103 company-common-with-non-prefix-completion (0.72 sec) >passed 26/103 company-create-lines-handles-multiple-width-in-annotation > (0.000253 sec) >passed 27/103 company-create-lines-shows-numbers (0.000188 sec) >passed 28/103 company-create-lines-truncates-annotations (0.000447 sec) >passed 29/103 company-create-lines-truncates-common-part (0.000371 sec) >passed 30/103 > company-dont-require-match-if-was-a-match-and-new-prefix-is-stop (0.000236 > sec) > Matching input is required >passed 31/103 > company-dont-require-match-if-was-a-match-and-old-prefix-ended (0.000278 sec) >passed 32/103 company-dont-require-match-when-idle (0.000205 sec) >passed 33/103 company-elisp-candidates-no-duplicates (0.000120 sec) >passed 34/103 company-elisp-candidates-predicate (0.000100 sec) >passed 35/103 company-elisp-candidates-predicate-binding-without-value > (0.000180 sec) >passed 36/103 company-elisp-candidates-predicate-in-docstring (0.67 > sec) >passed 37/103 company-elisp-candidates-recognizes-binding-form > (0.000131 sec) >passed 38/103 company-elisp-finds-functions (0.53 sec) >passed 39/103 company-elisp-finds-things (0.56 sec) >passed 40/103 company-elisp-finds-vars (0.52 sec) >passed 41/103 company-elisp-locals-funs (0.98 sec) >passed 42/103 company-elisp-locals-single-var (0.94 sec) >passed 43/103 company-elisp-locals-skips-current-varlist (0.80 sec) >passed 44/103 company-elisp-locals-vars (0.000102 sec) >passed 45/103 company-elisp-prefix-in-defun-body (0.96 sec) >passed 46/103 company-elisp-should-complete-def-call (0.85 sec) >passed 47/103 company-elisp-should-complete-in-defvar (0.83 sec) >
Processed: tagging 973639
Processing commands for cont...@bugs.debian.org: > tags 973639 + upstream Bug #973639 [libgromacs6] libgromacs6: missing Breaks+Replaces: libgromacs5 Added tag(s) upstream. > thanks Stopping processing here. Please contact me if you need assistance. -- 973639: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=973639 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#957226: marked as done (francine: ftbfs with GCC-10)
Your message dated Sat, 07 Nov 2020 18:05:42 +
with message-id
and subject line Bug#957226: fixed in francine 0.99.8+orig-2.1
has caused the Debian Bug report #957226,
regarding francine: ftbfs with GCC-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.)
--
957226: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=957226
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:francine
Version: 0.99.8+orig-2
Severity: normal
Tags: sid bullseye
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-10
Please keep this issue open in the bug tracker for the package it
was filed for. If a fix in another package is required, please
file a bug for the other package (or clone), and add a block in this
package. Please keep the issue open until the package can be built in
a follow-up test rebuild.
The package fails to build in a test rebuild on at least amd64 with
gcc-10/g++-10, but succeeds to build with gcc-9/g++-9. The
severity of this report will be raised before the bullseye release,
so nothing has to be done for the buster release.
The full build log can be found at:
http://people.debian.org/~doko/logs/gcc10-20200225/francine_0.99.8+orig-2_unstable_gcc10.log
The last lines of the build log are at the end of this report.
To build with GCC 10, either set CC=gcc-10 CXX=g++-10 explicitly,
or install the gcc, g++, gfortran, ... packages from experimental.
apt-get -t=experimental install g++
Common build failures are new warnings resulting in build failures with
-Werror turned on, or new/dropped symbols in Debian symbols files.
For other C/C++ related build failures see the porting guide at
http://gcc.gnu.org/gcc-10/porting_to.html
[...]
pam_login.c: In function ‘pam_pamconv’:
pam_login.c:65:15: warning: ignoring return value of ‘fgets’ declared with
attribute ‘warn_unused_result’ [-Wunused-result]
65 | fgets(buf2, sizeof(buf2)-1,stdin);
| ^
gcc -DHAVE_CONFIG_H -I. -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat
-Werror=format-security -c -o signal_handle.o signal_handle.c
signal_handle.c: In function ‘handle_sigint’:
signal_handle.c:56:3: warning: implicit declaration of function ‘exit’
[-Wimplicit-function-declaration]
56 | exit (-1);
| ^~~~
signal_handle.c:56:3: warning: incompatible implicit declaration of built-in
function ‘exit’
signal_handle.c:34:1: note: include ‘’ or provide a declaration of
‘exit’
33 | #include
+++ |+#include
34 |
signal_handle.c: In function ‘handle_sigterm’:
signal_handle.c:69:3: warning: incompatible implicit declaration of built-in
function ‘exit’
69 | exit (0);
| ^~~~
signal_handle.c:69:3: note: include ‘’ or provide a declaration of
‘exit’
gcc -DHAVE_CONFIG_H -I. -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat
-Werror=format-security -c -o speech.o speech.c
gcc -DHAVE_CONFIG_H -I. -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat
-Werror=format-security -c -o system_logon.o system_logon.c
system_logon.c: In function ‘write_lastlog_entry’:
system_logon.c:210:9: warning: passing argument 1 of ‘time’ from incompatible
pointer type [-Wincompatible-pointer-types]
210 | time (_time);
| ^~~~
| |
| int32_t * {aka int *}
In file included from system_logon.c:42:
/usr/include/time.h:75:29: note: expected ‘time_t *’ {aka ‘long int *’} but
argument is of type ‘int32_t *’ {aka ‘int *’}
75 | extern time_t time (time_t *__timer) __THROW;
| ^~~
system_logon.c: In function ‘system_logon’:
system_logon.c:279:3: warning: ignoring return value of ‘chdir’ declared with
attribute ‘warn_unused_result’ [-Wunused-result]
279 | chdir (user->pw_dir);
| ^~~~
system_logon.c:288:3: warning: ignoring return value of ‘chown’ declared with
attribute ‘warn_unused_result’ [-Wunused-result]
288 | chown (ttyname(0), user->pw_uid, grp->gr_gid);
| ^
system_logon.c:306:7: warning: ignoring return value of ‘setgid’ declared with
attribute ‘warn_unused_result’ [-Wunused-result]
306 | setgid (user->pw_gid);
| ^
system_logon.c:308:7: warning: ignoring return value of ‘setuid’ declared with
attribute ‘warn_unused_result’ [-Wunused-result]
308 | setuid (user->pw_uid);
|
Bug#921704: marked as done (tortoisehg: uninstallable with mercurial 4.9)
Your message dated Sat, 07 Nov 2020 14:53:25 + with message-id and subject line Bug#921704: fixed in tortoisehg 5.5.2-1 has caused the Debian Bug report #921704, regarding tortoisehg: uninstallable with mercurial 4.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.) -- 921704: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=921704 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: tortoisehg Version: 4.8.1-0.1 Severity: serious X-Debbugs-Cc: James Cowgill Hi, mercurial 4.9 is now in sid, so tortoisehg needs an update. Cheers, Julien --- End Message --- --- Begin Message --- Source: tortoisehg Source-Version: 5.5.2-1 Done: Andrej Shadura We believe that the bug you reported is fixed in the latest version of tortoisehg, 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 921...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Andrej Shadura (supplier of updated tortoisehg 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: Sun, 25 Oct 2020 14:32:49 +0100 Binary: tortoisehg tortoisehg-caja tortoisehg-nautilus Source: tortoisehg Architecture: all source Version: 5.5.2-1 Distribution: unstable Urgency: medium Maintainer: Andrej Shadura Changed-By: Andrej Shadura Closes: 921704 922565 Description: tortoisehg-caja - Graphical tool for working with Mercurial (Caja extension) tortoisehg - Graphical tool for working with Mercurial tortoisehg-nautilus - Graphical tool for working with Mercurial (Nautilus extension) Changes: tortoisehg (5.5.2-1) unstable; urgency=medium . * New maintainer (Closes: #922565). * New upstream version (Closes: #921704). * Refresh patches. * Switch over to Python 3. * Bump Mercurial dependency. Checksums-Sha1: da1723c460275a3a4b8501ab5452ab77658a86b3 1923 tortoisehg_5.5.2-1.dsc c12a0b83a78cbaeb6228bf26ea79076ecf61095f 8919653 tortoisehg_5.5.2.orig.tar.gz 19d12227e1673637615b9c9d49ceb3c5a79bf5ec 18068 tortoisehg_5.5.2-1.debian.tar.xz 7a64cdeb17e7c257924a78735fc90f5aafc4b461 16072 tortoisehg-caja_5.5.2-1_all.deb a30837c23c839c4b52b5a801c3771b18a22be20f 15976 tortoisehg-nautilus_5.5.2-1_all.deb ecbfe3ab29bd21b8e631aa0bf4e04e5c55678abe 2327968 tortoisehg_5.5.2-1_all.deb 7c341a12598c970f04104c49440f0886c4fc5fd1 10708 tortoisehg_5.5.2-1_amd64.buildinfo Checksums-Sha256: 42bf57b0db6a0f80fa2e22795e4c0920facad5b8a54b88bdffd16ba3298f6f13 1923 tortoisehg_5.5.2-1.dsc c3dbeaf1e91aae9eeb62f692aaf603feb93c9b16d3684a02b46484e72dda7f57 8919653 tortoisehg_5.5.2.orig.tar.gz 2c6f91550d800d1b8eb230e733ec622e22bd37fe87d167513c76cdc0c6e10d58 18068 tortoisehg_5.5.2-1.debian.tar.xz e08144f9dc63231f484aa2c489c486f8979d39a8ca60da90a5bbf0efe1917081 16072 tortoisehg-caja_5.5.2-1_all.deb 877f04aee9491b6f04cc9d725ab958efaddb90ef300e4dfc92f5d888391ac552 15976 tortoisehg-nautilus_5.5.2-1_all.deb 0ab8bae717fda803a0eff37cec46927413752789ec11eb96aa9e8ea61123c96d 2327968 tortoisehg_5.5.2-1_all.deb 36fa2d09b9a3da4766ee24ce7e3ac2f1ef34eabd0088a98618e2e7cfebca941b 10708 tortoisehg_5.5.2-1_amd64.buildinfo Files: c809bd04befd713d670d6d8603f55095 1923 vcs optional tortoisehg_5.5.2-1.dsc 4bfcf7840ad55d54f38c903d93163123 8919653 vcs optional tortoisehg_5.5.2.orig.tar.gz efd472092a083e71471ae19b9f0adf39 18068 vcs optional tortoisehg_5.5.2-1.debian.tar.xz 511c018cb7be0620e0db94d8ecb53fa1 16072 vcs optional tortoisehg-caja_5.5.2-1_all.deb fc6cfd7a5bbd9ae4d56c5278d299e1dd 15976 vcs optional tortoisehg-nautilus_5.5.2-1_all.deb 39ecf52d1fa638639f971de018f8bc73 2327968 vcs optional tortoisehg_5.5.2-1_all.deb e4c26bc4bf79a57ccf3c0ab77e42f9e9 10708 vcs optional tortoisehg_5.5.2-1_amd64.buildinfo -BEGIN PGP SIGNATURE- iQEzBAEBCAAdFiEEeuS9ZL8A0js0NGiOXkCM2RzYOdIFAl+VgAQACgkQXkCM2RzY OdI1Dwf/cHie4RMt1sS5Rdc2+8ZWMIRsn7BESLe0mVZB4xldu5zMHG58PKF3LrWP AubTdliXy1Ts7oqQYvpSLyHpEAdjiZZb8IoHKWX+uCuiE8aUSAe7Pg6oL9Ru2h51 Fp1XTfaiT/XRIWU6kJweVTDAy1qIjIDRhvxZ5dRdIbswzMbQd9sm9/M8afroTB3e uYYrCduTrdRlbRktAs/io/1w/q3dc3LcRjHeMespWi+IAs3NBPEt9CNN0uBFD5MV N+2AMhOHna/jTWvGVsaEog+py+/OF3lybCDwWL7CGuSAv2jB9hR3PbqN46YXB5V8 X6MimktAk8XN0PMliy2IEJ1katGEBQ== =ceu2 -END PGP
Bug#959955: marked as done (libsis-jhdf5-jni: ships /usr/lib/jni/libjhdf5.so already provided by libjhdf5-jni)
Your message dated Sat, 07 Nov 2020 14:10:13 + with message-id and subject line Bug#959955: fixed in libsis-jhdf5-java 19.04.0+dfsg-2 has caused the Debian Bug report #959955, regarding libsis-jhdf5-jni: ships /usr/lib/jni/libjhdf5.so already provided by libjhdf5-jni 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.) -- 959955: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=959955 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: libsis-jhdf5-jni Version: 19.04.0+dfsg-1 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package failed to install because it tries to overwrite other packages files without declaring a Breaks+Replaces relation. See policy 7.6 at https://www.debian.org/doc/debian-policy/ch-relationships.html#overwriting-files-and-replacing-packages-replaces >From the attached log (scroll to the bottom...): Preparing to unpack .../libsis-jhdf5-jni_19.04.0+dfsg-1_amd64.deb ... Unpacking libsis-jhdf5-jni (19.04.0+dfsg-1) ... dpkg: error processing archive /var/cache/apt/archives/libsis-jhdf5-jni_19.04.0+dfsg-1_amd64.deb (--unpack): trying to overwrite '/usr/lib/jni/libjhdf5.so', which is also in package libjhdf5-jni 2.11.0+dfsg-4 dpkg-deb: error: paste subprocess was killed by signal (Broken pipe) Errors were encountered while processing: /var/cache/apt/archives/libsis-jhdf5-jni_19.04.0+dfsg-1_amd64.deb cheers, Andreas libjhdf5-jni=2.11.0+dfsg-4_libsis-jhdf5-jni=19.04.0+dfsg-1.log.gz Description: application/gzip --- End Message --- --- Begin Message --- Source: libsis-jhdf5-java Source-Version: 19.04.0+dfsg-2 Done: Pierre Gruet We believe that the bug you reported is fixed in the latest version of libsis-jhdf5-java, 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 959...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Pierre Gruet (supplier of updated libsis-jhdf5-java package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Tue, 12 May 2020 22:37:32 +0200 Source: libsis-jhdf5-java Binary: h5ar libsis-jhdf5-java libsis-jhdf5-jni libsis-jhdf5-jni-dbgsym Architecture: source all amd64 Version: 19.04.0+dfsg-2 Distribution: unstable Urgency: medium Maintainer: Debian Med Packaging Team Changed-By: Pierre Gruet Description: h5ar - easy-to-use HDF archiver using Java libsis-jhdf5-java - easy-to-use HDF library for Java libsis-jhdf5-jni - native libs used by libsis-jhdf5-java package Closes: 959955 Changes: libsis-jhdf5-java (19.04.0+dfsg-2) unstable; urgency=medium . [ Pierre Gruet ] * Changing the name of the .so file in libsis-jhdf5-jni (Closes: #959955) * Providing the executable h5ar and a manpage * Adding a test for h5ar to the testsuite * Adding final qualifier to some arguments of functions * Providing hardening while compiling the jni part * Providing tests of the testsuite as examples . [ Steffen Moeller ] * d/control: Added R-R-R:no . [ Andreas Tille ] * Mention source/c/jni/* in d/copyright * Make sure build-time test will pass for the moment Checksums-Sha1: e2f244d10e97b072a5a5e284078b14ca2994ce6d 2723 libsis-jhdf5-java_19.04.0+dfsg-2.dsc ab59b1c5de06e6f740d66b47cda8594e46a2a829 13504 libsis-jhdf5-java_19.04.0+dfsg-2.debian.tar.xz cb5c5ff8497bb36865ddb963b37f16956119c880 1486552 h5ar_19.04.0+dfsg-2_all.deb f0fdb95961b89e5c8ec3d7fcfbd543cbbd5bc549 1490048 libsis-jhdf5-java_19.04.0+dfsg-2_all.deb b8f0a223ddf6009cb6fbeac69fcce2fe433ca8b4 16456 libsis-jhdf5-java_19.04.0+dfsg-2_amd64.buildinfo e9e832c1fe752d1d574f64a13301f7c265cf9803 326272 libsis-jhdf5-jni-dbgsym_19.04.0+dfsg-2_amd64.deb 19fce877314b511afda96eb9a1d6054de60b9485 95528 libsis-jhdf5-jni_19.04.0+dfsg-2_amd64.deb Checksums-Sha256: 1d2b3961544fb9bc996d46302a0e54dbec4116a7178b9d1dc834609df284b1d9 2723 libsis-jhdf5-java_19.04.0+dfsg-2.dsc 7df275b588bfc02d3300f4b59b96f02b2f06ef689721ae5a1b05aba3ee9c169b 13504 libsis-jhdf5-java_19.04.0+dfsg-2.debian.tar.xz 2966f6ef52c5e5930251458539c3f26edff6b47002e641c44acfb2dd2c480b4b 1486552 h5ar_19.04.0+dfsg-2_all.deb
Bug#973507: marked as done (libsis-jhdf5-java: incorrect license text for source/c/jni/)
Your message dated Sat, 07 Nov 2020 14:10:13 + with message-id and subject line Bug#973507: fixed in libsis-jhdf5-java 19.04.0+dfsg-3 has caused the Debian Bug report #973507, regarding libsis-jhdf5-java: incorrect license text for source/c/jni/ 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.) -- 973507: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=973507 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: libsis-jhdf5-java Version: 19.04.0+dfsg-1 Severity: serious Justification: Policy 2.3, 4.5, 12.5 X-Debbugs-CC: ftpmas...@debian.org Hello, The file source/c/jni/COPYING is a different HDF license to that which applies to source/java/hdf/hdf5lib. The version in NEW has the same problem as what's currently in the archive. -- Sean Whitton signature.asc Description: PGP signature --- End Message --- --- Begin Message --- Source: libsis-jhdf5-java Source-Version: 19.04.0+dfsg-3 Done: Andreas Tille We believe that the bug you reported is fixed in the latest version of libsis-jhdf5-java, 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 973...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Andreas Tille (supplier of updated libsis-jhdf5-java 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: Sun, 01 Nov 2020 15:13:17 +0100 Source: libsis-jhdf5-java Binary: h5ar libsis-jhdf5-java libsis-jhdf5-jni libsis-jhdf5-jni-dbgsym Architecture: source all amd64 Version: 19.04.0+dfsg-3 Distribution: unstable Urgency: medium Maintainer: Debian Med Packaging Team Changed-By: Andreas Tille Description: h5ar - easy-to-use HDF archiver using Java libsis-jhdf5-java - easy-to-use HDF library for Java libsis-jhdf5-jni - native libs used by libsis-jhdf5-java package Closes: 973507 Changes: libsis-jhdf5-java (19.04.0+dfsg-3) unstable; urgency=medium . [ Pierre Gruet ] * Activating build-time tests again * Deleting useless rm in override_dh_auto_clean * Solving issues in tests due to misclosed files * Forwarding patches . [ Andreas Tille ] * Declare different HDF licenses for source/c/jni and source/java/hdf/hdf5lib Closes: #973507 Checksums-Sha1: 7c6d00064db34c31aad59f9132108fd95b05d95e 2723 libsis-jhdf5-java_19.04.0+dfsg-3.dsc d2e135028e67cb686ecaebab789ab7330590fc16 14720 libsis-jhdf5-java_19.04.0+dfsg-3.debian.tar.xz f4635e37d666395ed98625ebfbbcf7be7043 1487816 h5ar_19.04.0+dfsg-3_all.deb 577f3206d72d80ee727556ae965f4e995b23c4a3 1491148 libsis-jhdf5-java_19.04.0+dfsg-3_all.deb 8f59d750fc32294cacd327e90eb016765c420b48 16734 libsis-jhdf5-java_19.04.0+dfsg-3_amd64.buildinfo 090016dccbac71360bc32efd978aa223f350aeac 326264 libsis-jhdf5-jni-dbgsym_19.04.0+dfsg-3_amd64.deb 37251e7145ad31ad53479d9f3619e53f87cf763c 96560 libsis-jhdf5-jni_19.04.0+dfsg-3_amd64.deb Checksums-Sha256: e5e04bd3e2fa4b8e95abb438ecac8d438789352cf6eebcbdbeefd7548484136f 2723 libsis-jhdf5-java_19.04.0+dfsg-3.dsc c4c1ee2b0e73da7d41bb95c1be449c752dc387034a243e621558623893e43f17 14720 libsis-jhdf5-java_19.04.0+dfsg-3.debian.tar.xz b9ca04b2ff12c9d6ae6c27a6dbe3f347d0d3aa23d5c1bde888e1ee98a09cc8d0 1487816 h5ar_19.04.0+dfsg-3_all.deb a025548b689ef5d22dd2ac9f09f3bc49afec7e60e961390485eb331630783096 1491148 libsis-jhdf5-java_19.04.0+dfsg-3_all.deb d26885483bcd6aaa3d70d5abe4621fc24d10481ddd13a3a003431477903f80af 16734 libsis-jhdf5-java_19.04.0+dfsg-3_amd64.buildinfo e1d480cbf1c2f0fa9c4a309ffecc699f3ee45d7265a948715a5d4e719047d659 326264 libsis-jhdf5-jni-dbgsym_19.04.0+dfsg-3_amd64.deb 33b7a53248c7728b1c89652cf74a2e7602177302eae5d385e29542bf2f78b7aa 96560 libsis-jhdf5-jni_19.04.0+dfsg-3_amd64.deb Files: 6e0f8d89b699c2854d76f2d198102185 2723 java optional libsis-jhdf5-java_19.04.0+dfsg-3.dsc c9d3306be5bdb19eb5e0e0d301baeb3d 14720 java optional libsis-jhdf5-java_19.04.0+dfsg-3.debian.tar.xz 9d1399c84f443d4a0f041fd6fe116960 1487816 java optional h5ar_19.04.0+dfsg-3_all.deb 96b34e43c79275a38f32a740783e7afe 1491148 java optional libsis-jhdf5-java_19.04.0+dfsg-3_all.deb 2ee93efec60c719411dc58176de2b101 16734 java optional
Bug#973919: suckless-tools: dmenu disappears when typing in i3wm
Package: suckless-tools Version: 45-1 Severity: grave Justification: renders package unusable X-Debbugs-Cc: fake...@ammd.net Dear Maintainer, When using d-menu in i3, d-menu appears, but as soon as a key is pressed, it disappears, making it impossible to launch any applications using that way. Thanks a lot. -- System Information: Debian Release: bullseye/sid APT prefers testing APT policy: (500, 'testing'), (500, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.9.0-1-amd64 (SMP w/4 CPU threads) Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /bin/bash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages suckless-tools depends on: ii libc6 2.30-4 ii libcap2-bin 1:2.44-1 ii libfontconfig1 2.13.1-4.2 ii libpam0g1.3.1-5 ii libx11-62:1.6.12-1 ii libxft2 2.3.2-2 ii libxinerama12:1.1.4-2 ii libxrandr2 2:1.5.1-1 ii libxss1 1:1.2.3-1 suckless-tools recommends no packages. Versions of packages suckless-tools suggests: pn dwm pn stterm pn surf -- no debconf information
Bug#973588: marked as done (Update from pari 2.11 to 2.13 breaks giac compilation)
Your message dated Sat, 07 Nov 2020 14:35:18 +0100
with message-id <9a8ae98b8253a791d4eef4ed6177f0cf4bce8bc0.ca...@gmail.com>
and subject line Fixed on giac's side
has caused the Debian Bug report #973588,
regarding Update from pari 2.11 to 2.13 breaks giac compilation
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.)
--
973588: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=973588
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libpari-dev
Version: 2.13.0-2
Severity: grave
The last pari upload broke giac on amd64, arm64 and mipsel :
https://buildd.debian.org/status/fetch.php?pkg=giac=amd64=1.6.0.25%2Bdfsg1-2%2Bb1=1604135053=0
The failing test on amd64 is a segfault. I could check that running the
failing test by hand while exporting PARI_SIZE=1024000 makes the
problem disappear, and PARI_SIZE=512000 or nothing makes it come back ;
here is an abstract from giac's pari.cc:
static struct pari_constants_initialization {
pari_constants_initialization () {
if (getenv("PARI_SIZE")){
string pari_size_s(getenv("PARI_SIZE"));
pari_mem_size= atoi(pari_size_s.c_str());
}
entree * ptr=functions_basic;
for (;ptr->name;++ptr){
pari_function_table[ptr->name]=ptr;
}
}
} pari_constants_initialization_singleton;
static void call_pari_init()
{
// do not initialize INIT_JMP so that PARI error do not exit
pari_init_opts(pari_mem_size,pari_maxprime,INIT_SIGm | INIT_DFTm);
paristack_setsize(pari_mem_size, (1<<30));
// initialize variable ordering x,y,z
gp_read_str("[x,y,z,t]");
}
Since it worked with pari 2.11 and breaks with pari 2.13, I guess the
problem is on pari's side.
Setting severity to grave because it breaks another package.
I hope it helps,
JP
--- End Message ---
--- Begin Message ---
Hi,
the problem seems in large part to be coming giac's initialisation
code, and the recent giac 1.6.0.25+dfsg1-3 upload made it disappear.
I'm hence closing this report against pari.
Thanks,
JP--- End Message ---
Bug#970495: marked as done (python-livereload: autopkgtest regression: needs-internet but fails)
Your message dated Sat, 07 Nov 2020 13:20:38 +
with message-id
and subject line Bug#970495: fixed in python-livereload 2.6.3-2
has caused the Debian Bug report #970495,
regarding python-livereload: autopkgtest regression: needs-internet but fails
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.)
--
970495: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=970495
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-livereload
Version: 2.6.3-1
X-Debbugs-CC: debian...@lists.debian.org
Severity: serious
User: debian...@lists.debian.org
Usertags: regression
Dear maintainer(s),
With a recent upload of python-livereload the autopkgtest of
python-livereload fails in testing when that autopkgtest is run with the
binary packages of python-livereload from unstable. It passes when run
with only packages from testing. In tabular form:
passfail
python-livereload from testing2.6.3-1
all others from testingfrom testing
I copied some of the output at the bottom of this report. Your tests is
trying to download stuff from the internet (please add the
needs-internet restriction), but fails to do so. On top of this, if the
stuff from the internet is executed, this violates an ftp-master rule [0].
Currently this regression is blocking the migration to testing [1]. Can
you please investigate the situation and fix it?
More information about this bug and the reason for filing it can be found on
https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation
Paul
[0] https://ftp-master.debian.org/REJECT-FAQ.html (Non-main II)
[1] https://qa.debian.org/excuses.php?package=python-livereload
https://ci.debian.net/data/autopkgtest/testing/amd64/p/python-livereload/7046752/log.gz
autopkgtest [03:13:34]: test command1: python3 setup.py test
autopkgtest [03:13:34]: test command1: [---
running test
WARNING: Testing via this command is deprecated and will be removed in a
future version. Users looking for a generic test entry point independent
of test runner are encouraged to use tox.
WARNING: The pip package is not available, falling back to EasyInstall
for handling setup_requires/test_requires; this is deprecated and will
be removed in a future version.
Searching for tornado
Reading https://pypi.org/simple/tornado/
Download error on https://pypi.org/simple/tornado/: [SSL:
CERTIFICATE_VERIFY_FAILED] certificate verify failed: unable to get
local issuer certificate (_ssl.c:1123) -- Some packages may not be found!
Couldn't find index page for 'tornado' (maybe misspelled?)
Scanning index of all packages (this may take a while)
Reading https://pypi.org/simple/
Download error on https://pypi.org/simple/: [SSL:
CERTIFICATE_VERIFY_FAILED] certificate verify failed: unable to get
local issuer certificate (_ssl.c:1123) -- Some packages may not be found!
No local packages or working download links found for tornado
error: Could not find suitable distribution for Requirement.parse('tornado')
autopkgtest [03:13:35]: test command1: ---]
signature.asc
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Source: python-livereload
Source-Version: 2.6.3-2
Done: =?utf-8?q?Pierre-Elliott_B=C3=A9cue?=
We believe that the bug you reported is fixed in the latest version of
python-livereload, 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 970...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Pierre-Elliott Bécue (supplier of updated python-livereload
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, 07 Nov 2020 14:02:34 +0100
Source: python-livereload
Architecture: source
Version: 2.6.3-2
Distribution: unstable
Urgency: medium
Maintainer: Agustin Henze
Changed-By: Pierre-Elliott Bécue
Closes: 970495
Changes:
python-livereload (2.6.3-2) unstable; urgency=medium
.
* Wrap-and-sort
* Use pytest to run the package's tests. (Closes: #970495)
Checksums-Sha1:
7db511bd760797d50b29a36222664d83024d9237 2272 python-livereload_2.6.3-2.dsc
c43fed18ac7ebc433b80ff7dfa4c9a22559b7101 6200
Bug#972867: gdcm: FTBFS in testing and unstable
Control: reopen -1 Hi, this still seems to be happening with charls 2.1.0+dfsg-6.
Processed: gdcm: FTBFS in testing and unstable
Processing control commands:
> reopen -1
Bug #972867 {Done: Mathieu Malaterre } [src:charls] gdcm:
FTBFS in testing and unstable
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
No longer marked as fixed in versions charls/2.1.0+dfsg-6.
--
972867: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=972867
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#973351: marked as done (cypari2 need an update for pari-2.13)
Your message dated Sat, 07 Nov 2020 11:35:05 + with message-id and subject line Bug#973351: fixed in cypari2 2.1.2-1 has caused the Debian Bug report #973351, regarding cypari2 need an update for pari-2.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.) -- 973351: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=973351 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: cypari2 Version: 2.1.1-2 Severity: important Tags: patch Dear Debian Science Team, cypari2 need an update to be compatible with pari 2.13.0 (in experimental) which will be uploded to sid soon. The fix needed is simple however the doctests are very fragile (they depend on unspecified behaviors) and need to be updated (for example they depend on the documentation of some functions). The patch does not attempt to deal with the doctests failure. Cheers, -- Bill. Imagine a large red swirl here. Index: cypari2-2.1.1/cypari2/gen.pyx === --- cypari2-2.1.1.orig/cypari2/gen.pyx +++ cypari2-2.1.1/cypari2/gen.pyx @@ -4109,7 +4109,7 @@ cdef class Gen(Gen_base): non-constant polynomial, or False if f is reducible or constant. """ sig_on() -t = isirreducible(self.g) +t = polisirreducible(self.g) clear_stack() return t != 0 Index: cypari2-2.1.1/cypari2/paridecl.pxd === --- cypari2-2.1.1.orig/cypari2/paridecl.pxd +++ cypari2-2.1.1/cypari2/paridecl.pxd @@ -3850,7 +3850,7 @@ cdef extern from *: # PARI headers a GEN glcm0(GEN x, GEN y) GEN gp_factor0(GEN x, GEN flag) GEN idealfactorback(GEN nf, GEN L, GEN e, int red) -longisirreducible(GEN x) +longpolisirreducible(GEN x) GEN newtonpoly(GEN x, GEN p) GEN nffactorback(GEN nf, GEN L, GEN e) GEN nfrootsQ(GEN x) --- End Message --- --- Begin Message --- Source: cypari2 Source-Version: 2.1.2-1 Done: Tobias Hansen We believe that the bug you reported is fixed in the latest version of cypari2, 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 973...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Tobias Hansen (supplier of updated cypari2 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, 07 Nov 2020 11:01:53 + Source: cypari2 Architecture: source Version: 2.1.2-1 Distribution: unstable Urgency: medium Maintainer: Debian Science Team Changed-By: Tobias Hansen Closes: 973351 Changes: cypari2 (2.1.2-1) unstable; urgency=medium . * New upstream version. (Closes: #973351) * Mark python-cypari2-doc as Multi-Arch: foreign. * Fix paths in doc-base file. Checksums-Sha1: 354236482bc0303454b784d410263df2a1fa873e 2247 cypari2_2.1.2-1.dsc 2a3039aa6bd690206cb58d4c39aef21e736eacf1 2178968 cypari2_2.1.2.orig.tar.gz 4389876143bee1eed350e83940f7d4e948cc0e29 4716 cypari2_2.1.2-1.debian.tar.xz 95b21eb4c11f161e7c4e05719b24abdcb20debff 7773 cypari2_2.1.2-1_source.buildinfo Checksums-Sha256: 9f7ce9faea6ff5bea07f72be5e12a098f30d8acb4d22abe17d789e911bffa7bc 2247 cypari2_2.1.2-1.dsc 03cd45edab8716ebbfdb754e65fea72e873c73dc91aec098fe4a01e35324ac7a 2178968 cypari2_2.1.2.orig.tar.gz ab1065e49092492c2c7f28b2247066afe939defda7bac43094380d3831782938 4716 cypari2_2.1.2-1.debian.tar.xz f1b3a668eafdd2836d99c7a148beb762c891c19a69802739192d183dc5769078 7773 cypari2_2.1.2-1_source.buildinfo Files: cf51da3149acca6c354b5c2e9b9d0e4b 2247 python optional cypari2_2.1.2-1.dsc 6267c0dace847160763dc1777a390c0a 2178968 python optional cypari2_2.1.2.orig.tar.gz cc8501e78af5b7b67a2a93943eaad40f 4716 python optional cypari2_2.1.2-1.debian.tar.xz cc6251ee67b61f37791d413d1e3c5668 7773 python optional cypari2_2.1.2-1_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEEoH46ol3M2u2mYo0kjIIWnY7OzSoFAl+mgkQACgkQjIIWnY7O zSruJg//UaATNFp/u8XoHebRDxAy/7Zt1ixXlxtsXFglAuEwK9zBy6AqKqhnsQg/ bLz71NJpUmjxn0Ssvvhe84IOPDqC4M8wMD+NgO2b8CayW/yrQkHpXmqLN6VBcKFy NyOnJlRfeDFe6gkyEZZSqyvb7BZIYkQlunrlSAJDY9y6QZlzEE4LZJRLun1GqvBD
Bug#973221: marked as done (soundkonverter: FTBFS: MetaReplayGain.h:25:10: fatal error: fileref.h: No such file or directory)
Your message dated Sat, 07 Nov 2020 11:06:20 + with message-id and subject line Bug#973221: fixed in soundkonverter 3.0.1-2 has caused the Debian Bug report #973221, regarding soundkonverter: FTBFS: MetaReplayGain.h:25:10: fatal error: fileref.h: No such file or directory 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.) -- 973221: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=973221 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: soundkonverter Version: 3.0.1-1 Severity: serious Justification: FTBFS on amd64 Tags: bullseye sid ftbfs Usertags: ftbfs-20201027 ftbfs-bullseye Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > cd /<>/obj-x86_64-linux-gnu/plugins/soundkonverter_codec_lame && > /usr/bin/c++ -DKCOREADDONS_LIB -DKGUIADDONS_LIB -DQT_CONCURRENT_LIB > -DQT_CORE_LIB -DQT_DBUS_LIB -DQT_DISABLE_DEPRECATED_BEFORE=0 -DQT_GUI_LIB > -DQT_NETWORK_LIB -DQT_NO_DEBUG -DQT_PRINTSUPPORT_LIB -DQT_WIDGETS_LIB > -DQT_XML_LIB -DSOUNDKONVERTER_KF5_BUILD -D_GNU_SOURCE -D_LARGEFILE64_SOURCE > -Dsoundkonverter_codec_lame_EXPORTS > -I/<>/obj-x86_64-linux-gnu/plugins/soundkonverter_codec_lame > -I/<>/src/plugins/soundkonverter_codec_lame > -I/<>/obj-x86_64-linux-gnu/plugins/soundkonverter_codec_lame/soundkonverter_codec_lame_autogen/include > -I/<>/obj-x86_64-linux-gnu -I/<>/src -isystem > /usr/include/KF5/KWidgetsAddons -isystem /usr/include/KF5 -isystem > /usr/include/x86_64-linux-gnu/qt5 -isystem > /usr/include/x86_64-linux-gnu/qt5/QtWidgets -isystem > /usr/include/x86_64-linux-gnu/qt5/QtGui -isystem > /usr/include/x86_64-linux-gnu/qt5/QtCore -isystem > /usr/lib/x86_64-linux-gnu/qt5/mkspecs/linux-g++ -isystem > /usr/include/x86_64-linux-gnu/qt5/QtXml -isystem > /usr/include/KF5/KIOFileWidgets -isystem /usr/include/KF5/KIOWidgets -isystem > /usr/include/KF5/KIOGui -isystem /usr/include/KF5/KIOCore -isystem > /usr/include/KF5/KCoreAddons -isystem /usr/include/KF5/KService -isystem > /usr/include/KF5/KConfigCore -isystem > /usr/include/x86_64-linux-gnu/qt5/QtNetwork -isystem > /usr/include/x86_64-linux-gnu/qt5/QtConcurrent -isystem > /usr/include/x86_64-linux-gnu/qt5/QtDBus -isystem > /usr/include/KF5/KWindowSystem -isystem /usr/include/KF5/KJobWidgets -isystem > /usr/include/KF5/KCompletion -isystem /usr/include/KF5/KBookmarks -isystem > /usr/include/KF5/KItemViews -isystem /usr/include/KF5/KXmlGui -isystem > /usr/include/KF5/KConfigWidgets -isystem /usr/include/KF5/KCodecs -isystem > /usr/include/KF5/KConfigGui -isystem /usr/include/KF5/KAuth -isystem > /usr/include/KF5/Solid -isystem /usr/include/KF5/KDELibs4Support -isystem > /usr/include/KF5/KDELibs4Support/KDE -isystem > /usr/include/x86_64-linux-gnu/qt5/QtPrintSupport -isystem > /usr/include/KF5/KCrash -isystem /usr/include/KF5/KI18n -isystem > /usr/include/KF5/KNotifications -isystem /usr/include/KF5/KIconThemes > -isystem /usr/include/KF5/KGuiAddons -isystem > /usr/include/KF5/KUnitConversion -isystem /usr/include/KF5/KTextWidgets > -isystem /usr/include/KF5/SonnetUi -isystem /usr/include/KF5/KParts -g -O2 > -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat > -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -Wall -pedantic > -Wno-deprecated-declarations -fno-operator-names -fno-exceptions -Wall > -Wextra -Wcast-align -Wchar-subscripts -Wformat-security -Wno-long-long > -Wpointer-arith -Wundef -Wnon-virtual-dtor -Woverloaded-virtual > -Werror=return-type -Wvla -Wdate-time -Wsuggest-override -Wlogical-op -fPIC > -fvisibility=hidden -fvisibility-inlines-hidden -fPIC -std=gnu++11 -o > CMakeFiles/soundkonverter_codec_lame.dir/lameconversionoptions.cpp.o -c > /<>/src/plugins/soundkonverter_codec_lame/lameconversionoptions.cpp > In file included from /<>/src/configdialog/../pluginloader.h:15, > from /<>/src/configdialog/../config.h:10, > from > /<>/src/configdialog/configcoverartpage.cpp:4: > /<>/src/configdialog/../core/codecplugin.h:36:21: warning: > ‘virtual QString CodecPlugin::type() const’ can be marked override > [-Wsuggest-override] >36 | virtual QString type() const; > | ^~~~ > In file included from /<>/src/configdialog/../pluginloader.h:16, > from /<>/src/configdialog/../config.h:10, > from > /<>/src/configdialog/configcoverartpage.cpp:4: > /<>/src/configdialog/../core/filterplugin.h:42:21: warning: > ‘virtual QString FilterPlugin::type() const’ can be marked override > [-Wsuggest-override] >
Bug#973223: marked as done (ktorrent: FTBFS: ./obj-x86_64-linux-gnu/plugins/mediaplayer/./plugins/mediaplayer/playlist.cpp:153: undefined reference to `TagLib::String::~String()')
Your message dated Sat, 07 Nov 2020 10:18:50 + with message-id and subject line Bug#973223: fixed in ktorrent 5.2.0-2 has caused the Debian Bug report #973223, regarding ktorrent: FTBFS: ./obj-x86_64-linux-gnu/plugins/mediaplayer/./plugins/mediaplayer/playlist.cpp:153: undefined reference to `TagLib::String::~String()' 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.) -- 973223: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=973223 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: ktorrent Version: 5.2.0-1 Severity: serious Justification: FTBFS on amd64 Tags: bullseye sid ftbfs Usertags: ftbfs-20201027 ftbfs-bullseye Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > /usr/bin/ld: CMakeFiles/ktorrent_mediaplayer.dir/playlist.cpp.o: in function > `kt::PlayList::data(QModelIndex const&, int) const': > ./obj-x86_64-linux-gnu/plugins/mediaplayer/./plugins/mediaplayer/playlist.cpp:153: > undefined reference to `TagLib::String::~String()' > /usr/bin/ld: > ./obj-x86_64-linux-gnu/plugins/mediaplayer/./plugins/mediaplayer/playlist.cpp:122: > undefined reference to `TagLib::String::~String()' > /usr/bin/ld: > ./obj-x86_64-linux-gnu/plugins/mediaplayer/./plugins/mediaplayer/playlist.cpp:154: > undefined reference to `TagLib::String::~String()' > collect2: error: ld returned 1 exit status The full build log is available from: http://qa-logs.debian.net/2020/10/27/ktorrent_5.2.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! 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: ktorrent Source-Version: 5.2.0-2 Done: Pino Toscano We believe that the bug you reported is fixed in the latest version of ktorrent, 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 973...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Pino Toscano (supplier of updated ktorrent 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, 07 Nov 2020 10:52:19 +0100 Source: ktorrent Architecture: source Version: 5.2.0-2 Distribution: unstable Urgency: medium Maintainer: Debian KDE Extras Team Changed-By: Pino Toscano Closes: 973223 Changes: ktorrent (5.2.0-2) unstable; urgency=medium . * Team upload. * Backport upstream commit f4c1c91d9b091941ebb4dae6aef95bcf9bc1c388 to fix the cmake search and use of taglib; patch upstream_Update-FindTaglib-from-ECM.patch (Closes: #973223) * Fix day-of-week for changelog entry 1.1-1. * Set upstream metadata fields: Repository, Repository-Browse. * Add the configuration for the CI on salsa. * Explicitly add the pkg-config build dependency. Checksums-Sha1: 64e33f001a11eb88d989a6740291cc699c5310a0 3067 ktorrent_5.2.0-2.dsc 8db18922fad6134029a1dc17eb695381ca9baab9 24672 ktorrent_5.2.0-2.debian.tar.xz 9fe3ff802cc51dc77d36591be616ae072acc2d3e 20900 ktorrent_5.2.0-2_source.buildinfo Checksums-Sha256: b6a1dfd32c407bc05827e4f180a99b3cbc690999af8840b9823d05411cebcc08 3067 ktorrent_5.2.0-2.dsc 0e12c50a193c425bd4a81035fc275e56fe9b1fad3aefa5d9854f67dc979190d6 24672 ktorrent_5.2.0-2.debian.tar.xz 0cd3bd7d91f346f035b88e30a7b0b50e8ca1491b014cef19af443cae76d3e81c 20900 ktorrent_5.2.0-2_source.buildinfo Files: ef36b1e51f5bec2bffc16efcb8761bd3 3067 net optional ktorrent_5.2.0-2.dsc 3cc698feafa2a7fc471c351caae17143 24672 net optional ktorrent_5.2.0-2.debian.tar.xz a2ad7ece742a666d78722a176f3a378a 20900 net optional ktorrent_5.2.0-2_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEXyqfuC+mweEHcAcHLRkciEOxP00FAl+mbt8ACgkQLRkciEOx P00EhhAAnrct7mL84gmfTJChOAsBmOAYXMoNqykjZlaj7kgpQt9KF7Ok1e1lWvSj jl+q9puseCu2gF4LESFOHfskHsMF+uOGp0M7lQSJ2+sVr+EkxF28RRvT2oPlezRG hwAfWEFN9oRv8lrmKT3FC6aqdiKlnQ7oyrjWkT/q79eH8NrAqhYZjn4PGoPIFnu2
Processed: closing 972239
Processing commands for cont...@bugs.debian.org: > close 972239 0.8.4-3 Bug #972239 [geoalchemy2] geoalchemy2 build-depends on obsolete packages. There is no source info for the package 'geoalchemy2' at version '0.8.4-3' with architecture '' Unable to make a source version for version '0.8.4-3' Marked as fixed in versions 0.8.4-3. Bug #972239 [geoalchemy2] geoalchemy2 build-depends on obsolete packages. Marked Bug as done > thanks Stopping processing here. Please contact me if you need assistance. -- 972239: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=972239 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#972239: closing 972239
close 972239 0.8.4-3 thanks
Processed: tagging 973221
Processing commands for cont...@bugs.debian.org: > tags 973221 + pending Bug #973221 [src:soundkonverter] soundkonverter: FTBFS: MetaReplayGain.h:25:10: fatal error: fileref.h: No such file or directory Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 973221: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=973221 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#973588: Update from pari 2.11 to 2.13 breaks giac compilation
On Sat, Nov 07, 2020 at 10:29:18AM +0100, Julien Puydt wrote: > Le jeudi 05 novembre 2020 à 19:12 +0100, Bill Allombert a écrit : > > On Mon, Nov 02, 2020 at 09:57:07AM +0100, Bill Allombert wrote: > > > This means 512000 is not sufficient. This is a fatal error. > > > The test cannot pass. > > > > Would you mind uploading giac with PARI_SIZE=1024000 so that we can > > close this bug ? > > I have done that, Excellent, thanks! Mind closing the bug with the giac upload ? > but still, crashing is pretty bad : it should detect > the value is too low at startup and complain. The amount of stack needed depend on the computation the user requested, so it is the responsibiity of the user to set the stack size. However, the user can set parisizemax to allow PARI to increase the stack as needed up to parisizemax. If the stack is still too low, then you get an error that you can trap and recover from. It seems giac recovery code does not handle pari stack overflow correctly. This should be fixed, but this is not a RC bug in pari, and probably not a regression. Cheers, Bill
Bug#973748: closing 973748
close 973748 0.19.0-1 thanks
Processed: closing 973748
Processing commands for cont...@bugs.debian.org: > close 973748 0.19.0-1 Bug #973748 [src:sddm] sddm: CVE-2020-28049: local privilege escalation due to race condition in creation of the Xauthority file Marked as fixed in versions sddm/0.19.0-1. Bug #973748 [src:sddm] sddm: CVE-2020-28049: local privilege escalation due to race condition in creation of the Xauthority file Marked Bug as done > thanks Stopping processing here. Please contact me if you need assistance. -- 973748: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=973748 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: tagging 973223
Processing commands for cont...@bugs.debian.org: > tags 973223 + pending Bug #973223 [src:ktorrent] ktorrent: FTBFS: ./obj-x86_64-linux-gnu/plugins/mediaplayer/./plugins/mediaplayer/playlist.cpp:153: undefined reference to `TagLib::String::~String()' Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 973223: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=973223 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#973588: Update from pari 2.11 to 2.13 breaks giac compilation
Le jeudi 05 novembre 2020 à 19:12 +0100, Bill Allombert a écrit : > On Mon, Nov 02, 2020 at 09:57:07AM +0100, Bill Allombert wrote: > > This means 512000 is not sufficient. This is a fatal error. > > The test cannot pass. > > Would you mind uploading giac with PARI_SIZE=1024000 so that we can > close this bug ? I have done that, but still, crashing is pretty bad : it should detect the value is too low at startup and complain. JP
Bug#971704: marked as done (gnome-shell-pomodoro: No JS module 'tweener' found in search path)
Your message dated Sat, 07 Nov 2020 09:03:37 + with message-id and subject line Bug#971704: fixed in gnome-shell-pomodoro 0.18.0-0.1 has caused the Debian Bug report #971704, regarding gnome-shell-pomodoro: No JS module 'tweener' found in search path 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.) -- 971704: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=971704 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: gnome-shell-pomodoro Version: 0.17.0-1 Severity: normal (This could be a Gnome 3.38 issue) I've just saw that Pomodoro stoped working for me, Gnome.Extensions says "No JS module 'tweener' found in search path" Currently trying to compile 0.18 (released yesterday) to see if that works. -- tobi --- End Message --- --- Begin Message --- Source: gnome-shell-pomodoro Source-Version: 0.18.0-0.1 Done: Tobias Frost We believe that the bug you reported is fixed in the latest version of gnome-shell-pomodoro, 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 971...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Tobias Frost (supplier of updated gnome-shell-pomodoro package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Thu, 05 Nov 2020 16:06:29 +0100 Source: gnome-shell-pomodoro Architecture: source Version: 0.18.0-0.1 Distribution: unstable Urgency: medium Maintainer: Joseph Herlant Changed-By: Tobias Frost Closes: 971704 Changes: gnome-shell-pomodoro (0.18.0-0.1) unstable; urgency=medium . * Non-maintainer-upload * New upstream version with Gnome 3.38 support. (Closes: #971704) Checksums-Sha1: 1def1af2c83e90c3dd84c0bd7c75c6be09129170 2572 gnome-shell-pomodoro_0.18.0-0.1.dsc 37f58bbd3a2fa50d6ec369f0c65c99d93bd4d137 6203162 gnome-shell-pomodoro_0.18.0.orig.tar.gz 95f133007da20002435f160f41f8d8abe0801735 6872 gnome-shell-pomodoro_0.18.0-0.1.debian.tar.xz Checksums-Sha256: c2cf3584e0f582c6fcf824aea81bc2785945a94d3c3567e61634f9ab0384bedb 2572 gnome-shell-pomodoro_0.18.0-0.1.dsc 16cb0a772a5e0adad1519dbc63f98a6959887b4e65f8db512a9b7a4d24fcc52d 6203162 gnome-shell-pomodoro_0.18.0.orig.tar.gz d3fefbc401096985878effef1c0f355dd1e2221e38686c8ae9e4f4c1a9ca4b23 6872 gnome-shell-pomodoro_0.18.0-0.1.debian.tar.xz Files: 3897f302aecbbf9a6e8ef0db9e76e149 2572 gnome optional gnome-shell-pomodoro_0.18.0-0.1.dsc e884579bb509ca586b1fd443e9b0b9f4 6203162 gnome optional gnome-shell-pomodoro_0.18.0.orig.tar.gz 5bf75dffdb535f51405a8470328de8a2 6872 gnome optional gnome-shell-pomodoro_0.18.0-0.1.debian.tar.xz -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEE/d0M/zhkJ3YwohhskWT6HRe9XTYFAl+mXMIACgkQkWT6HRe9 XTaTdg//eljIv1TcNnmYfxyykvcSJJs9ZX4ImKcWkkClflNsUN/Mbm5IFbkMBOH6 m83RRbaZjcBCAcJwOlvcrJw7/q2BaspwfjnPbDhuTyIIVJWHYRNgidkEZtG/9gbX jOZlf6VG/e+uRJ8gyx2FmTaNOFqZ26/gedL7fH5MQvnfLeJVI02ZHiSrEzUJQHsI yybX8zbPJpslZoQ2xoxP/dA+J6aE8353n2kM65tHS4R0fV6dbOQJo7/NrKD0GU5i nJ6iguDVaDsEPQkbQps1ncHc1aNXcnz5r0gjIdd8GtuiCbcSPtz1KkNiACZrRaY/ 2UwvegKSCS7wqQ1BQ4Iy+joM9wm9/K3poSqV0Nwp8n9v3ckV3dYEYuXPXraLMkiR zR56Fzg38XkLSo3hKvHa4luUHZY0zyMDGazXxxu1bB1EzFUtYDfamFaWpefI9Ri/ VjJBC0On0/blc29ofDe4x2BtZudspszJf4h4Q2lhSWn3OVVUOyaJGab/6wXwj8Bc zaVtBJPeuSaxs5gicWbQm0cPb7F8VFg04Ek88PP3M7JRUfTOs4XtGww7bbicZ7Hx MpwthFmzhchNLMhE0uQVJHFCdAqrH08u6bPEPIIaLzI6nkAS2UERpShgphmoF6mA syZoWSS2q4grlmk53g0gO6FItoR26BjxI2oCdtRlXP/uz8T4llc= =bpc5 -END PGP SIGNATURE End Message ---
Bug#971704: gnome-shell-pomodoro: diff for NMU version 0.18.0-0.1
On Fri, Nov 06, 2020 at 11:34:11AM -0800, Joseph Herlant wrote: > Feel free to push it now. It's totally fine with me. Done, thanks for the heads-up! -- tobi > Thanks > Joseph
