Processed: reassign 996806 to mailman3
Processing commands for cont...@bugs.debian.org: > reassign 996806 mailman3 Bug #996806 [mailman3] mailmain3: Expected test results for arc_validate tests need updating Ignoring request to reassign bug #996806 to the same package > thanks Stopping processing here. Please contact me if you need assistance. -- 996806: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=996806 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Re: Bug#996806: mailmain3: Expected test results for arc_validate tests need updating
Processing control commands: > reassign -1 mailman3 3.3.3-1 Bug #996806 [mailmain3] mailmain3: Expected test results for arc_validate tests need updating Warning: Unknown package 'mailmain3' Bug reassigned from package 'mailmain3' to 'mailman3'. No longer marked as found in versions 3.3.3-1. Ignoring request to alter fixed versions of bug #996806 to the same values previously set Bug #996806 [mailman3] mailmain3: Expected test results for arc_validate tests need updating Marked as found in versions mailman3/3.3.3-1. -- 996806: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=996806 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#996806: mailmain3: Expected test results for arc_validate tests need updating
Control: reassign -1 mailman3 3.3.3-1 On Ma, 19 oct 21, 01:10:28, Scott Kitterman wrote: > Package: mailmain3 > Version: 3.3.3-1 > Severity: serious > Tags: ftbfs > Justification: fails to build from source (but built successfully in the past) > > mailman3 now fails tests with authheaders 0.14.1 since support for > comments in ARC results was added. Although this isn't precisely an > FTBFS, a autopkgtest failure has similar effects. > > Please update the expected results as this not an authheaders error. > > == > FAIL: test_authentication_whitelist_hit > (mailman.handlers.tests.test_arc_validate.TestValidateAuthenticity) > -- > Traceback (most recent call last): > File > "/tmp/autopkgtest-lxc.wj1y37tc/downtmp/build.0B5/src/src/mailman/handlers/tests/test_arc_validate.py", > line 238, in test_authentication_whitelist_hit > self.assertEqual(msg["Authentication-Results"], ''.join(res)) > AssertionError: 'exam[50 chars]ss header.d=valimail.com; arc=none (Message is > not ARC signed)' != 'exam[50 chars]ss header.d=valimail.com; arc=none' > - example.com; spf=pass smtp.mailfrom=gmail.com; dkim=pass > header.d=valimail.com; arc=none (Message is not ARC signed) > ? > > + example.com; spf=pass smtp.mailfrom=gmail.com; dkim=pass > header.d=valimail.com; arc=none > > > == > FAIL: test_authentication_whitelist_miss > (mailman.handlers.tests.test_arc_validate.TestValidateAuthenticity) > -- > Traceback (most recent call last): > File > "/tmp/autopkgtest-lxc.wj1y37tc/downtmp/build.0B5/src/src/mailman/handlers/tests/test_arc_validate.py", > line 279, in test_authentication_whitelist_miss > self.assertEqual(msg["Authentication-Results"], > AssertionError: 'test[13 chars]ss header.d=valimail.com; arc=none (Message is > not ARC signed)' != 'test[13 chars]ss header.d=valimail.com; arc=none' > - test.com; dkim=pass header.d=valimail.com; arc=none (Message is not ARC > signed) > ? > > + test.com; dkim=pass header.d=valimail.com; arc=none > > > == > FAIL: test_chain_validation_fail > (mailman.handlers.tests.test_arc_validate.TestValidateAuthenticity) > -- > Traceback (most recent call last): > File > "/tmp/autopkgtest-lxc.wj1y37tc/downtmp/build.0B5/src/src/mailman/handlers/tests/test_arc_validate.py", > line 195, in test_chain_validation_fail > self.assertEqual(msg["Authentication-Results"], ''.join(res)) > AssertionError: 'list[94 chars] arc=fail (Most recent ARC-Message-Signature > did not validate)' != 'list[94 chars] arc=fail' > - lists.example.org; spf=pass smtp.mfrom=jqd@d1.example; dkim=pass > header.i=@d1.example; dmarc=pass; arc=fail (Most recent ARC-Message-Signature > did not validate) > ? > > - > + lists.example.org; spf=pass smtp.mfrom=jqd@d1.example; dkim=pass > header.i=@d1.example; dmarc=pass; arc=fail > > > -- > > Scott K Fixing typing error in package name. Kind regards, Andrei -- Looking after bugs assigned to unknown or inexistent packages signature.asc Description: PGP signature
Bug#996806: mailmain3: Expected test results for arc_validate tests need updating
Package: mailmain3 Version: 3.3.3-1 Severity: serious Tags: ftbfs Justification: fails to build from source (but built successfully in the past) mailman3 now fails tests with authheaders 0.14.1 since support for comments in ARC results was added. Although this isn't precisely an FTBFS, a autopkgtest failure has similar effects. Please update the expected results as this not an authheaders error. == FAIL: test_authentication_whitelist_hit (mailman.handlers.tests.test_arc_validate.TestValidateAuthenticity) -- Traceback (most recent call last): File "/tmp/autopkgtest-lxc.wj1y37tc/downtmp/build.0B5/src/src/mailman/handlers/tests/test_arc_validate.py", line 238, in test_authentication_whitelist_hit self.assertEqual(msg["Authentication-Results"], ''.join(res)) AssertionError: 'exam[50 chars]ss header.d=valimail.com; arc=none (Message is not ARC signed)' != 'exam[50 chars]ss header.d=valimail.com; arc=none' - example.com; spf=pass smtp.mailfrom=gmail.com; dkim=pass header.d=valimail.com; arc=none (Message is not ARC signed) ? + example.com; spf=pass smtp.mailfrom=gmail.com; dkim=pass header.d=valimail.com; arc=none == FAIL: test_authentication_whitelist_miss (mailman.handlers.tests.test_arc_validate.TestValidateAuthenticity) -- Traceback (most recent call last): File "/tmp/autopkgtest-lxc.wj1y37tc/downtmp/build.0B5/src/src/mailman/handlers/tests/test_arc_validate.py", line 279, in test_authentication_whitelist_miss self.assertEqual(msg["Authentication-Results"], AssertionError: 'test[13 chars]ss header.d=valimail.com; arc=none (Message is not ARC signed)' != 'test[13 chars]ss header.d=valimail.com; arc=none' - test.com; dkim=pass header.d=valimail.com; arc=none (Message is not ARC signed) ? + test.com; dkim=pass header.d=valimail.com; arc=none == FAIL: test_chain_validation_fail (mailman.handlers.tests.test_arc_validate.TestValidateAuthenticity) -- Traceback (most recent call last): File "/tmp/autopkgtest-lxc.wj1y37tc/downtmp/build.0B5/src/src/mailman/handlers/tests/test_arc_validate.py", line 195, in test_chain_validation_fail self.assertEqual(msg["Authentication-Results"], ''.join(res)) AssertionError: 'list[94 chars] arc=fail (Most recent ARC-Message-Signature did not validate)' != 'list[94 chars] arc=fail' - lists.example.org; spf=pass smtp.mfrom=jqd@d1.example; dkim=pass header.i=@d1.example; dmarc=pass; arc=fail (Most recent ARC-Message-Signature did not validate) ? - + lists.example.org; spf=pass smtp.mfrom=jqd@d1.example; dkim=pass header.i=@d1.example; dmarc=pass; arc=fail -- Scott K
Bug#996583: marked as done (xir FTBFS)
Your message dated Tue, 19 Oct 2021 02:35:43 +
with message-id
and subject line Bug#996583: fixed in xir 1.4-1
has caused the Debian Bug report #996583,
regarding xir FTBFS
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.)
--
996583: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=996583
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: xir
Version: 1.3.2-1
Severity: serious
Tags: ftbfs
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/xir.html
https://buildd.debian.org/status/logs.php?pkg=xir=1.3.2-1
...
/<>/src/xir/graph/elf2xir.cpp: In instantiation of ‘std::ostream&
{anonymous}::operator<<(std::ostream&, const std::vector&) [with T =
std::__cxx11::basic_string; std::ostream = std::basic_ostream]’:
/<>/src/xir/graph/elf2xir.cpp:1010:33: required from here
/<>/src/xir/graph/elf2xir.cpp:403:19: error: loop variable ‘x’
creates a copy from type ‘const std::__cxx11::basic_string’
[-Werror=range-loop-construct]
403 | for (const auto x : v) {
| ^
/<>/src/xir/graph/elf2xir.cpp:403:19: note: use reference type to
prevent copying
403 | for (const auto x : v) {
| ^
| &
...
--- End Message ---
--- Begin Message ---
Source: xir
Source-Version: 1.4-1
Done: Nobuhiro Iwamatsu
We believe that the bug you reported is fixed in the latest version of
xir, which is due to be installed in the Debian FTP archive.
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to 996...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Nobuhiro Iwamatsu (supplier of updated xir 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, 19 Oct 2021 09:25:25 +0900
Source: xir
Architecture: source
Version: 1.4-1
Distribution: unstable
Urgency: medium
Maintainer: Punit Agrawal
Changed-By: Nobuhiro Iwamatsu
Closes: 996583
Changes:
xir (1.4-1) unstable; urgency=medium
.
* New upstream released.
* Add d/patches/Fix-FTBFS-with-Werror-range-loop-construct-Closes-99.patch.
(Closes: #996583)
Checksums-Sha1:
fdfbeab3c3829f0bf47aaafc87251938900e8cd5 2051 xir_1.4-1.dsc
29e060b9a2f381edfb300c26a1fa4f812fb410c7 186664 xir_1.4.orig.tar.xz
111e97d2abf5e722824d5298fd305da7fad7e5bd 5088 xir_1.4-1.debian.tar.xz
4b84fc16b24388e2e88d327b69a4039892a0a061 8164 xir_1.4-1_amd64.buildinfo
Checksums-Sha256:
fa4bfd92e509f0cee95dbf662b45e7defb69db106c9f26d695b2926461ecb3b6 2051
xir_1.4-1.dsc
ffbe7de5686608cbb8360f8764596195319794447dc1b6577ef0d6562bcab88a 186664
xir_1.4.orig.tar.xz
1ba41faa20b35921d1a986e3fa94676ea9a979753fec1b8cac795f72c09f9003 5088
xir_1.4-1.debian.tar.xz
3dcb4b1d2ad4bbeedf842bb3f7f5e339a63fad3660d5f931271251e61a592044 8164
xir_1.4-1_amd64.buildinfo
Files:
fcb86fb25c3aa3e7322f7cf69ae263e5 2051 libs optional xir_1.4-1.dsc
4442f6f41863860785fba1c4bb968827 186664 libs optional xir_1.4.orig.tar.xz
25d001fa3a65888df71049a10f288823 5088 libs optional xir_1.4-1.debian.tar.xz
2985c284a35d16d8bd7a485853e937a1 8164 libs optional xir_1.4-1_amd64.buildinfo
-BEGIN PGP SIGNATURE-
iQIzBAEBCAAdFiEEXmKe5SMhlzV7hM9DMiR/u0CtH6YFAmFuJaUACgkQMiR/u0Ct
H6aP8Q//ZnVNfWWmCp9MRDm6w8d+9n3AbW4+bznVWo4SMtSgwcFvksC1cM2NbP1S
ES2ndpLnNHV9cZSaxSfpO0Ov2fjdFDF/6R5GOWTG1GEH8TEg1KNRlk99yU8c60RG
IKaqJvFwXyMupWlP04heMPrga5Y0odzXcZRqeQchcUNu/lC0wje9idDTAgwI7swf
ELaywjf7hiKazce4ZOqtZcGmqsqGWouB73DkSBSHRQiXjk/hGWIcBc/MbRnjlzdq
aBC+WxVCQ+h0VbqhvMqHy0Cl4EMkD81Ffsm0bY8IYgQt0S6j8Sc6ArQIDqazouW7
c3dlfPWmCG/zj8qfk7GZqxTz4XSUGhChOTOSzQ3ZEwGs+ld5oPA8O/+F+sV3ElJb
PAZiwV6f0aAw4mSBEOAdJ7blV7mCz4punJqyKvHSGxupWfezR5/X82xiUaSjiGTq
EIjfyCn1VezDc/rUqxEwd811/Qejd/akZiRZETe7d4gFm2Uz82T2PSNoWGjGLZSI
yc8wqDTsk5jiirUjlPb2UUtTw0tyRfjglFja6sMFdQG2DOPspDOnhDtXAJbeadtK
eAU7hC8vo+8Gt+kQ+LItJAdDP0TJfxoRhRC43L5cWMCjodG2L7u1E1YG0vu9X1KM
k9zSiUd3EuHweUAPLy2xM9/shYYeNFHz/PnELuiVaCHhQyShWks=
=WfaT
-END PGP SIGNATURE End Message ---
Bug#996583: marked as done (xir FTBFS)
Your message dated Tue, 19 Oct 2021 02:35:35 +
with message-id
and subject line Bug#996583: fixed in xir 1.3.2-2
has caused the Debian Bug report #996583,
regarding xir FTBFS
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.)
--
996583: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=996583
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: xir
Version: 1.3.2-1
Severity: serious
Tags: ftbfs
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/xir.html
https://buildd.debian.org/status/logs.php?pkg=xir=1.3.2-1
...
/<>/src/xir/graph/elf2xir.cpp: In instantiation of ‘std::ostream&
{anonymous}::operator<<(std::ostream&, const std::vector&) [with T =
std::__cxx11::basic_string; std::ostream = std::basic_ostream]’:
/<>/src/xir/graph/elf2xir.cpp:1010:33: required from here
/<>/src/xir/graph/elf2xir.cpp:403:19: error: loop variable ‘x’
creates a copy from type ‘const std::__cxx11::basic_string’
[-Werror=range-loop-construct]
403 | for (const auto x : v) {
| ^
/<>/src/xir/graph/elf2xir.cpp:403:19: note: use reference type to
prevent copying
403 | for (const auto x : v) {
| ^
| &
...
--- End Message ---
--- Begin Message ---
Source: xir
Source-Version: 1.3.2-2
Done: Punit Agrawal
We believe that the bug you reported is fixed in the latest version of
xir, which is due to be installed in the Debian FTP archive.
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to 996...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Punit Agrawal (supplier of updated xir package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Tue, 19 Oct 2021 11:17:02 +0900
Source: xir
Architecture: source
Version: 1.3.2-2
Distribution: unstable
Urgency: medium
Maintainer: Punit Agrawal
Changed-By: Punit Agrawal
Closes: 996583
Changes:
xir (1.3.2-2) unstable; urgency=medium
.
* Fix build bug with recent versions of compiler (Closes: #996583)
Checksums-Sha1:
05cf9abe2a379295683de526a6c0b3b161d1a4e8 2090 xir_1.3.2-2.dsc
3fe98b575c932d7f92444f665afb95cc18cb3df2 5240 xir_1.3.2-2.debian.tar.xz
658aa1fe7bfd57c3e42103b38629a6d44a290740 8296 xir_1.3.2-2_amd64.buildinfo
Checksums-Sha256:
8d3be307305c0a7da4a2866781ac33a5e00b89f060a2a88bf5444bb69d7462d0 2090
xir_1.3.2-2.dsc
05863b8237e47e600f512d1487762350d79c028790698046c170e346a89fe53c 5240
xir_1.3.2-2.debian.tar.xz
ce72e5b50ba212b51fc46c7d5c539b8c5d329d6f32f6c793603c77e1b01c7af1 8296
xir_1.3.2-2_amd64.buildinfo
Files:
c4c14dd4516f555eb38ecbd79d095613 2090 libs optional xir_1.3.2-2.dsc
c57f26c00b020b8a2d8373c5ab923b14 5240 libs optional xir_1.3.2-2.debian.tar.xz
6e325ce71db84e296aa7d6201dbc6726 8296 libs optional xir_1.3.2-2_amd64.buildinfo
-BEGIN PGP SIGNATURE-
iQJFBAEBCgAvFiEEvZ5M7BP8NElWggdO9Tkv0hP7/t0FAmFuK4MRHHB1bml0QGRl
Ymlhbi5vcmcACgkQ9Tkv0hP7/t2/LA//ZhVbwSBK96ogUGP25OeX8XK/FTkIugye
3vDBZAgkNtXGsGsOW9eFrv9SguDBrzoOfyhwDQGYa4ns82xPvS3UjGVxCMDxydIa
3OuAeXYFxmj3U+ITVpfeEU6PXfC4DjmGxVjCfSXPYshZqItgrrwIuU45PLRrkFb7
5LCF9RQ42fA4XUD9pXnvJaa00huI29KvRc4qxMWOtk1JXUneZywMDuB+WNNjlhPi
3o0LkiimruhE8C4PqAJbHPTIZ56WOcAgGgxPEAAYH3uPGe2Ih1eEQEvuKgvOWkJJ
6d1Fgpd4aoHuCheA2ZltNiYQxjbDBEW2gytzSUrzZfrhSR9j7AloF6wBT2wc6bD9
2pB0guJ+Rl2etAc5Q1nG+V97HNo1p1cBcsXsV0QGevm6IGd/lDCr85OH7MNdwhGR
pxVEZx+Jbo6csk51N6hRnFjnrvJikNSO1O+kd30/1MvSz7I2iMv5KFdO6nocJZkG
VYpwCwHQE7anfllK1cEihTjLov45PIJcbiZ50fh2J97QZj5sqdoLAkc+pQfLM0f8
fvBwH5xOOA+83ntoWmvRkT/qUSNnSK7+3PHpkionMkWRpwrrA2p6s/Tz9M9SpTEX
pCed1yL4TAzKL8jPzVS6NI9h75JcTjlldZ3juuFnaE38LY/dg6LpjG/CeRUSXEYz
SkBaf1ZnF6w=
=D6ei
-END PGP SIGNATURE End Message ---
Bug#996761: kwin-x11: KWin crashes and doesn't start
Hello Francisco, hello Albert, this might be the same as in bug #996726 and not directly related to the nvidia driver. I hit a crash in kwin_x11 with an AMD graphics card and could workaround by installing libkdecorations2-5v5_5.21.5-2_amd64.deb like mentioned in #996726. Kind regards, Bernhard https://bugs.debian.org/996726
Bug#983981: Further comment on #983981 marked as pending in bamtools
Howdy, Debian Bug Tracking System, on 2021-10-18: > Processing control commands: > > > tag -1 pending > Bug #983981 [src:bamtools] bamtools: ftbfs with GCC-11 > Ignoring request to alter tags of bug #983981 to the same tags previously set Hmm, scratch that, I didn't realize initially that the bug was already pending upload, so reverted my changes in the repository. I'm probably too tired to upload sensibly this evening. The new version of bamtools with the fix is pending upload already, so I guess it might wait for a good time to coordinate an eventual transission, or just been forgotten. Have a good evening, :) -- Étienne Mollier Fingerprint: 8f91 b227 c7d6 f2b1 948c 8236 793c f67e 8f0d 11da Sent from /dev/pts/2, please excuse my verbosity. signature.asc Description: PGP signature
Bug#994697: marked as done (libgit-annex-perl: Test failure - autopkgtest and build)
Your message dated Mon, 18 Oct 2021 22:33:32 + with message-id and subject line Bug#994697: fixed in git-annex 8.20211011-2 has caused the Debian Bug report #994697, regarding libgit-annex-perl: Test failure - autopkgtest and build 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.) -- 994697: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=994697 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: libgit-annex-perl Version: 0.007-1 Severity: serious Tags: ftbfs sid bookworm Justification: fails to build from source (but built successfully in the past) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 As first seen at ci.debian.net [0], libgit-annex-perl recently started to fail its testsuite. I note that this started to happen after the last git-annex upload (8.20210903-1). The same test failure also happens at buildtime: # Failed test 'other is reinjected' # at t/23_annex-to-annex-reinject.t line 33. # Looks like you failed 1 test of 2. t/23_annex-to-annex-reinject.t ok 1 - other is initially present not ok 2 - other is reinjected 1..2 Dubious, test returned 1 (wstat 256, 0x100) Failed 1/2 subtests Cheers, gregor [0] https://ci.debian.net/data/autopkgtest/unstable/amd64/libg/libgit-annex-perl/15193220/log.gz https://ci.debian.net/data/autopkgtest/unstable/arm64/libg/libgit-annex-perl/15101826/log.gz - -- System Information: Debian Release: bookworm/sid APT prefers unstable APT policy: (990, 'unstable'), (500, 'unstable-debug'), (500, 'stable-security'), (500, 'oldoldstable'), (500, 'experimental'), (500, 'testing'), (500, 'stable'), (500, 'oldstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.10.0-8-amd64 (SMP w/4 CPU threads) Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=C, LC_CTYPE=de_AT.utf8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /bin/dash Init: sysvinit (via /sbin/init) LSM: AppArmor: enabled Versions of packages libgit-annex-perl depends on: ii libdata-compare-perl 1.27-1 ii libdigest-md5-file-perl0.08-1.1 ii libfile-chdir-perl 0.1008-1.1 pn libfile-chmod-perl ii libgit-repository-perl 1.324-2 ii libgit-wrapper-perl0.048-1 ii libipc-system-simple-perl 1.30-1 ii libscalar-list-utils-perl 1:1.55-1+b1 ii libterm-readkey-perl 2.38-1+b2 ii libtry-tiny-perl 0.30-1 ii perl 5.32.1-5 ii perl-base [libscalar-list-utils-perl] 5.32.1-5 Versions of packages libgit-annex-perl recommends: ii git-annex 8.20210903-1 libgit-annex-perl suggests no packages. -BEGIN PGP SIGNATURE- iQKTBAEBCgB9FiEE0eExbpOnYKgQTYX6uzpoAYZJqgYFAmFHV6FfFIAALgAo aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldEQx RTEzMTZFOTNBNzYwQTgxMDREODVGQUJCM0E2ODAxODY0OUFBMDYACgkQuzpoAYZJ qgbA0w//dlEs3en0QAixvRPPX2vDZk7VWOEakpi9c3mg7Mi/N39eoIBfh0DFd6YP suacz+kdGIlw7pTUBvyxzzv04YLVxQ0tB8MUA874ut7d439LLOZRsBomJQoshONa OhDkhc1AGmNwdE8JL3eMKpoLLnrdgZjqFZeozVVZqO229WcbO3kszrZEEiFj225V gruxedqknxki2YUGlN87n4PRip3owl8q1WII97h8fjonWVKhIq5sA1QnlONUd/BU zTrHVYG4/Qi7EtUXeT2O07r4mZW31HOoPUiVE+Ep2Y7k3T0ViPp+DgPl4YCZOtkM QqiUrLkEBM+PWGFv5/0PFDoWEUXl78+tb7E58/oL4tzj4laRUReHLltHvjT64Ll0 udmzEJT9zDey9Hum/edPJ5mjWc1VKq7bNBycoCE9RVX/bXeT0zauVsfZcT4h2dnm Xz/+VCwb2/GGzWoX82805yob5QS/sPI5KsQeIhOm+K7qQ7jeV2AAKG2oX1wx6efW pQwWMFWt4UR6HIu5BYB+BVGR1iCHNwPRJZYJVH4QknP6AVWVEAELObnpDp9oE9Te ZDwJUB5wtmrgiUCCISmkzjFCq49a09WCocTnD6AOL28C2l+4lQ8KO7CqY8Ri61PU TQAkxTnqByQzl9/oH0Ca6ZXlkbolASBv60gXT8aGikti0CLxjjY= =+Deo -END PGP SIGNATURE- --- End Message --- --- Begin Message --- Source: git-annex Source-Version: 8.20211011-2 Done: Sean Whitton We believe that the bug you reported is fixed in the latest version of git-annex, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 994...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Sean Whitton (supplier of updated git-annex 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
Bug#996761: kwin-x11: KWin crashes and doesn't start
Thank you, Patrick and Bernhard; downgrading worked for me as well. Very much appreciated. On Mon, Oct 18, 2021 at 11:24 PM Francisco José Calvo wrote: > > Hello Bernhard, yes it is same issue mentioned in #996726, not related to > nvidia-driver. > > Thanks a lot. > > El lun., 18 oct. 2021 23:16, Bernhard Übelacker > escribió: >> >> Hello Francisco, hello Albert, >> this might be the same as in bug #996726 >> and not directly related to the nvidia driver. >> >> I hit a crash in kwin_x11 with an AMD graphics card >> and could workaround by installing >> libkdecorations2-5v5_5.21.5-2_amd64.deb like >> mentioned in #996726. >> >> Kind regards, >> Bernhard >> >> https://bugs.debian.org/996726
Processed: gkrellm-leds: diff for NMU version 0.8.0-1.4 (was: Bug#995968: gkrellm-leds: This gkrellm plugin does not start, Error: undefined symbol: XTestFakeKeyEvent)
Processing control commands: > tags 995968 + patch Bug #995968 [gkrellm-leds] gkrellm-leds: This gkrellm plugin does not start, Error: undefined symbol: XTestFakeKeyEvent Added tag(s) patch. > tags 995968 + pending Bug #995968 [gkrellm-leds] gkrellm-leds: This gkrellm plugin does not start, Error: undefined symbol: XTestFakeKeyEvent Added tag(s) pending. -- 995968: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=995968 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#995968: gkrellm-leds: diff for NMU version 0.8.0-1.4 (was: Bug#995968: gkrellm-leds: This gkrellm plugin does not start, Error: undefined symbol: XTestFakeKeyEvent)
Control: tags 995968 + patch Control: tags 995968 + pending Renzo Davoli wrote... > Bugfix: add --no-as-needed linker option. Thanks for spotting this and providing a fix. Dear maintainer, to resolve this issue, I've prepared a NMU for gkrellm-leds (versioned as 0.8.0-1.4), upload to DELAYED/5 will follow shortly. Please feel free to tell me if I should delay it longer. Regards. Christoph diff -u gkrellm-leds-0.8.0/Makefile gkrellm-leds-0.8.0/Makefile --- gkrellm-leds-0.8.0/Makefile +++ gkrellm-leds-0.8.0/Makefile @@ -8,7 +8,7 @@ LIBS = $(GTK_LIB) $(X11_LIB) DEFINES = -LFLAGS = -shared +LFLAGS = -shared -Wl,--no-as-needed INCLUDES = $(GTK_INCLUDE) CFLAGS = -ansi -pedantic -Wall -O2 -fPIC CC = gcc diff -u gkrellm-leds-0.8.0/debian/changelog gkrellm-leds-0.8.0/debian/changelog --- gkrellm-leds-0.8.0/debian/changelog +++ gkrellm-leds-0.8.0/debian/changelog @@ -1,3 +1,10 @@ +gkrellm-leds (0.8.0-1.4) unstable; urgency=medium + + * Non-maintainer upload + * Fix startup error, thanks Renzo Davoli. Closes: #995968 + + -- Christoph Biedl Mon, 18 Oct 2021 23:33:29 +0200 + gkrellm-leds (0.8.0-1.3) unstable; urgency=medium * Non-maintainer upload signature.asc Description: PGP signature
Bug#984045: marked as done (dymo-cups-drivers: ftbfs with GCC-11)
Your message dated Mon, 18 Oct 2021 21:48:55 + with message-id and subject line Bug#984045: fixed in dymo-cups-drivers 1.4.0-11 has caused the Debian Bug report #984045, regarding dymo-cups-drivers: ftbfs with GCC-11 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 984045: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=984045 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:dymo-cups-drivers Version: 1.4.0-9 Severity: normal Tags: sid bookworm User: debian-...@lists.debian.org Usertags: ftbfs-gcc-11 [This bug is not targeted to the upcoming bullseye release] Please keep this issue open in the bug tracker for the package it was filed for. If a fix in another package is required, please file a bug for the other package (or clone), and add a block in this package. Please keep the issue open until the package can be built in a follow-up test rebuild. The package fails to build in a test rebuild on at least amd64 with gcc-11/g++-11, but succeeds to build with gcc-10/g++-10. The severity of this report will be raised before the bookworm release, so nothing has to be done for the bullseye release. The full build log can be found at: http://people.debian.org/~doko/logs/20210228/filtered/gcc11/dymo-cups-drivers_1.4.0-9_unstable_gcc11.log The last lines of the build log are at the end of this report. To build with GCC 11, either set CC=gcc-11 CXX=g++-11 explicitly, or install the gcc, g++, gfortran, ... packages from experimental. apt-get -t=experimental install g++ Common build failures are new warnings resulting in build failures with -Werror turned on, or new/dropped symbols in Debian symbols files. For other C/C++ related build failures see the porting guide at http://gcc.gnu.org/gcc-11/porting_to.html GCC 11 defaults to the GNU++17 standard. If your package installs header files in /usr/include, please don't work around C++17 issues by choosing a lower C++ standard for the package build, but fix these issues to build with the C++17 standard. [...] | ^~~~ In file included from /usr/include/c++/11/bits/stl_algobase.h:61, from /usr/include/c++/11/deque:60, from /usr/include/cppunit/Message.h:11, from /usr/include/cppunit/Exception.h:5, from /usr/include/cppunit/TestCaller.h:4, from /usr/include/cppunit/extensions/HelperMacros.h:9, from TestLabelWriterLanguageMonitor.h:24, from TestLabelWriterLanguageMonitor.cpp:21: /usr/include/c++/11/bits/cpp_type_traits.h:404:30: note: candidates are: ‘enum class std::byte’ 404 | enum class byte : unsigned char; | ^~~~ In file included from ../../common/PrinterDriver.h:24, from ../LabelWriterDriver.h:25, from TestLabelWriterLanguageMonitor.h:25, from TestLabelWriterLanguageMonitor.cpp:21: ../../common/CommonTypedefs.h:31:29: note: ‘typedef unsigned char DymoPrinterDriver::byte’ 31 | typedef unsigned char byte; | ^~~~ TestLabelWriterLanguageMonitor.cpp:335:3: error: reference to ‘byte’ is ambiguous 335 | byte OutputPrinterData2[] = | ^~~~ In file included from /usr/include/c++/11/bits/stl_algobase.h:61, from /usr/include/c++/11/deque:60, from /usr/include/cppunit/Message.h:11, from /usr/include/cppunit/Exception.h:5, from /usr/include/cppunit/TestCaller.h:4, from /usr/include/cppunit/extensions/HelperMacros.h:9, from TestLabelWriterLanguageMonitor.h:24, from TestLabelWriterLanguageMonitor.cpp:21: /usr/include/c++/11/bits/cpp_type_traits.h:404:30: note: candidates are: ‘enum class std::byte’ 404 | enum class byte : unsigned char; | ^~~~ In file included from ../../common/PrinterDriver.h:24, from ../LabelWriterDriver.h:25, from TestLabelWriterLanguageMonitor.h:25, from TestLabelWriterLanguageMonitor.cpp:21: ../../common/CommonTypedefs.h:31:29: note: ‘typedef unsigned char DymoPrinterDriver::byte’ 31 | typedef unsigned char byte; | ^~~~ TestLabelWriterLanguageMonitor.cpp:340:25: error: ‘PrinterData’ was not declared in this scope; did you mean ‘PrinterData2’? 340 | buffer_t PrinterData2(PrinterData, PrinterData + sizeof(PrinterData)); |
Bug#996802: llvm-toolchain-12: FTBFS on s390x since 1:12.0.1-10: Cannot find builtins library for the target architecture
Source: llvm-toolchain-12 Version: 1:12.0.1-10 Severity: serious Tags: ftbfs Justification: fails to build from source (but built successfully in the past) The restructuring in 1:12.0.1-10 seems to have caused a regression on s390x: https://buildd.debian.org/status/fetch.php?pkg=llvm-toolchain-12=s390x=1%3A12.0.1-10=1634250418=0 > -- Compiler-RT supported architectures: s390x > CMake Error at > /<>/compiler-rt/cmake/Modules/AddCompilerRT.cmake:243 (message): > Cannot find builtins library for the target architecture > Call Stack (most recent call first): > /<>/compiler-rt/lib/stats/CMakeLists.txt:23 > (add_compiler_rt_runtime)
Processed: Re: Bug#996778: Processed: severity of 996778 is grave
Processing control commands: > severity -1 important Bug #996778 [xymon-client] xymon-client: Disable by default the ability of logfetch to execute arbitrary code fetched from the Xymon server Severity set to 'important' from 'grave' -- 996778: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=996778 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#996778: Processed: severity of 996778 is grave
Control: severity -1 important Hi, Christoph Berg wrote: > Re: Axel Beckert > > "critical" is indeed clearly wrong. I'd have rather said "important" > > only as the claim of being a "root hole" is wrong. But ok. > > I only moved it off "critical" which it really is not. If you think > important (or wishlist?) makes more sense, go ahead. For me, "important" seems appropriate. If the security team disagrees, I'm fine with their opinion on this issue as I might be a bit biased here as I use and value the feature in question. > > I'm though not sure if this is acceptable for stable updates as it is > > a rather invasive change IMHO. > > It would be ok if we buy the security part. There is some security impact by this feature, yes. But IMHO the impact is moderate at most as the client only executes code which it requested explicitly from the server (but does that by default which this bug-report is about) and exploiting would require one of these conditions: * Compromising a router (or routing in any other way) inbetween to modify the response by the monitoring server — which are usually all in the same perimeter. * Compromising the monitoring server itself. * Using DNS hostnames on the client (which is explicitly not recommended for reliability reasons) in combination with a DNS spoofing attack, spoofing the server's DNS record and redirecting logfetch to fetch code from the wrong server. Hint for the security team: Xymon currently does not use TLS for monitoring checks unless you build that yourself with stunnel. Reliability might be one of the reasons here, but I suspect more a lack of upstream developer resources to be the reason. Anyway, I'll prepare an update of Xymon for Unstable changing the default setting to "logfetch --noexec" and then we'll see if more (like stable updates or so) is needed. Regards, Axel -- ,''`. | Axel Beckert , https://people.debian.org/~abe/ : :' : | Debian Developer, ftp.ch.debian.org Admin `. `' | 4096R: 2517 B724 C5F6 CA99 5329 6E61 2FF9 CD59 6126 16B5 `-| 1024D: F067 EA27 26B9 C3FC 1486 202E C09E 1D89 9593 0EDE signature.asc Description: PGP signature
Bug#996801: db2twitter: unusable with tweepy version 4
Package: db2twitter Version: 0.6-1.1 Severity: grave Tag: patch Dear maintainer, db2twitter has become unusable with the new python3-tweepy package because of an backwards-incompatible API changes in version 4. I think you'll need to remove the wait_on_rate_limit_notify=True parameter from the tweepy.API() constructions in twresend.py:43 and twsend.py:46, but I'm not sure if that is enough. Cheers Timo PS. You may also want to update d/watch to point to the new upstream repository at https://gitlab.com/chaica/db2twitter -- ⢀⣴⠾⠻⢶⣦⠀ ╭╮ ⣾⠁⢠⠒⠀⣿⡁ │ Timo Röhling │ ⢿⡄⠘⠷⠚⠋⠀ │ 9B03 EBB9 8300 DF97 C2B1 23BF CC8C 6BDD 1403 F4CA │ ⠈⠳⣄ ╰╯ signature.asc Description: PGP signature
Bug#996800: retweet: unusable with tweepy version 4
Package: retweet Version: 0.10-1.1 Severity: grave Tag: patch Dear maintainer, retweet has become unusable with the new python3-tweepy package because of an backwards-incompatible API changes in version 4. AFAICT you merely need to remove the wait_on_rate_limit_notify=True parameter from main.py:53 to make it work again. Cheers Timo PS. You may also want to update d/watch to point to the new upstream repository at https://gitlab.com/chaica/retweet -- ⢀⣴⠾⠻⢶⣦⠀ ╭╮ ⣾⠁⢠⠒⠀⣿⡁ │ Timo Röhling │ ⢿⡄⠘⠷⠚⠋⠀ │ 9B03 EBB9 8300 DF97 C2B1 23BF CC8C 6BDD 1403 F4CA │ ⠈⠳⣄ ╰╯ signature.asc Description: PGP signature
Bug#996761: kwin-x11: KWin crashes and doesn't start
Hello Bernhard, yes it is same issue mentioned in #996726, not related to nvidia-driver. Thanks a lot. El lun., 18 oct. 2021 23:16, Bernhard Übelacker escribió: > Hello Francisco, hello Albert, > this might be the same as in bug #996726 > and not directly related to the nvidia driver. > > I hit a crash in kwin_x11 with an AMD graphics card > and could workaround by installing > libkdecorations2-5v5_5.21.5-2_amd64.deb like > mentioned in #996726. > > Kind regards, > Bernhard > > https://bugs.debian.org/996726 >
Bug#996799: twitterwatch: unusable with tweepy version 4
Package: twitterwatch
Version: 0.1-2
Severity: grave
Tag: patch
X-Debbugs-Cc: Boyuan Yang
Dear maintainer,
twitterwatch has become unusable with the new python3-tweepy package
because of backwards-incompatible API changes in version 4.
Attached is an (untested) patch that should make the package work
again.
Cheers
Timo
PS. You may also want to update d/watch to point to the new
upstream repository at https://gitlab.com/chaica/twitterwatch
--
⢀⣴⠾⠻⢶⣦⠀ ╭╮
⣾⠁⢠⠒⠀⣿⡁ │ Timo Röhling │
⢿⡄⠘⠷⠚⠋⠀ │ 9B03 EBB9 8300 DF97 C2B1 23BF CC8C 6BDD 1403 F4CA │
⠈⠳⣄ ╰╯
diff --git a/twitterwatch/main.py b/twitterwatch/main.py
index f7a481b..e811e6f 100644
--- a/twitterwatch/main.py
+++ b/twitterwatch/main.py
@@ -43,7 +43,8 @@ class Main(object):
self.auth.secure = True
self.auth.set_access_token(self.cfgvalues['access_token'],
self.cfgvalues['access_token_secret'])
-self.api = tweepy.API(self.auth, wait_on_rate_limit=True, wait_on_rate_limit_notify=True)
+self.api = tweepy.API(self.auth, wait_on_rate_limit=True)
+self.me = self.api.verify_credentials()
self.main()
def main(self):
@@ -59,7 +60,7 @@ class Main(object):
# get the interval between two checks
pause = datetime.timedelta(minutes=self.cfgvalues['check_interval'])
if (currentdate - pause) > lastactiondate:
-user = self.api.me().screen_name
+user = self.me.screen_name
# warn
warning = 'Twitter stream of {} has stopped since {}'.format(user, lastactiondate.strftime("%d/%m/%Y - %H:%M:%S"))
emailwarn = EmailWarning(self.cfgvalues, warning, user)
signature.asc
Description: PGP signature
Bug#996048: [Pkg-openssl-devel] Bug#996048: postfix-mta-sts-resolver: autopkgtest doesn't handle new version of ca-certificates nicely: rehash: warning: skipping ca-certificates.crt, it does not conta
On Mon, Oct 18, 2021 at 10:40:59PM +0200, Julien Cristau wrote: > On Mon, Oct 18, 2021 at 02:50:50PM +0200, Benjamin Hof wrote: > > Hi, > > > > I think the following change might be the relevant one: > > > > --- a/update-ca-certificates > > +++ b/update-ca-certificates > > @@ -164,8 +164,6 @@ > >done > > fi > > > > -rm -f "$CERTBUNDLE" > > - > > ADDED_CNT=$(wc -l < "$ADDED") > > REMOVED_CNT=$(wc -l < "$REMOVED") > > > > It triggers this stderr output during openssl rehash (l. 184): > > > > rehash: warning: skipping ca-certificates.crt,it does not contain > > exactly one certificate or CRL > > > Ah, that makes sense. Annoying... > > Kurt/Sebastian, do you think there's a chance openssl rehash could grow > some sort of ignore option so update-ca-certificates could ask it to > skip ca-certificates.crt, to avoid spitting out a warning for it? As in rehash all files in that directory, excluding a file? I guess that's an option. I guess it's not an option to move the file to a different location. Kurt
Bug#996761: kwin-x11: KWin crashes and doesn't start
Thank you so much Patrick, yes I'm using testing. I downgraded libkdecorations2-5v5 and now it works fine. Kind regards. On Mon, 18 Oct 2021 22:45:17 +0200 Patrick Franz wrote: > Hi, > > I assume you're using testing. Unfortunately, Plasma is broken in > testing at the moment if you have upgraded libkdecorations2-5v5 to 5.23. > Could you check that ? > > If this is the case, I wrote about a possible solution here: > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=996726#10 > > > -- > Med vänliga hälsningar > > Patrick Franz > > > >
Bug#996798: llvm-toolchain-12: FTBFS on mipsel|powerpc since 1:12.0.1-10: undefined reference to `_Unwind_Resume' etc.
Source: llvm-toolchain-12 Version: 1:12.0.1-10 Severity: serious Tags: ftbfs Justification: fails to build from source (but built successfully in the past) The restructuring in 1:12.0.1-10 seems to have caused a build regression on mipsel, which I'm reporting as separate from #996796 because it doesn't affect i386: > [1050/1054] : && /<>/build-llvm/./bin/clang++ > --target=mipsel-unknown-linux-gnu -fPIC -g -O2 > -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat > -Werror=format-security -fPIC -fvisibility-inlines-hidden -Werror=date-time > -Werror=unguarded-availability-new -Wall -Wextra -Wno-unused-parameter > -Wwrite-strings -Wcast-qual -Wmissing-field-initializers > -Wimplicit-fallthrough -Wcovered-switch-default -Wno-noexcept-type > -Wnon-virtual-dtor -Wdelete-non-virtual-dtor -Wsuggest-override -Wno-comment > -Wstring-conversion -fdiagnostics-color -ffunction-sections -fdata-sections > -O3 -DNDEBUG -Wl,-z,relro -Wl,-z,defs -Wl,-z,nodelete -nodefaultlibs > -shared -Wl,-soname,libc++abi.so.1 -o > /<>/build-llvm/lib/libc++abi.so.1.0 > libcxxabi/src/CMakeFiles/cxxabi_shared.dir/cxa_aux_runtime.cpp.o > libcxxabi/src/CMakeFiles/cxxabi_shared.dir/cxa_default_handlers.cpp.o > libcxxabi/src/CMakeFiles/cxxabi_shared.dir/cxa_demangle.cpp.o > libcxxabi/src/CMakeFiles/cxxabi_shared.dir/cxa_exception_storage.cpp.o > libcxxabi/src/CMakeFiles/cxxabi_shared.dir/cxa_guard.cpp.o > libcxxabi/src/CMakeFiles/cxxabi_shared.dir/cxa_handlers.cpp.o > libcxxabi/src/CMakeFiles/cxxabi_shared.dir/cxa_vector.cpp.o > libcxxabi/src/CMakeFiles/cxxabi_shared.dir/cxa_virtual.cpp.o > libcxxabi/src/CMakeFiles/cxxabi_shared.dir/stdlib_exception.cpp.o > libcxxabi/src/CMakeFiles/cxxabi_shared.dir/stdlib_stdexcept.cpp.o > libcxxabi/src/CMakeFiles/cxxabi_shared.dir/stdlib_typeinfo.cpp.o > libcxxabi/src/CMakeFiles/cxxabi_shared.dir/abort_message.cpp.o > libcxxabi/src/CMakeFiles/cxxabi_shared.dir/fallback_malloc.cpp.o > libcxxabi/src/CMakeFiles/cxxabi_shared.dir/private_typeinfo.cpp.o > libcxxabi/src/CMakeFiles/cxxabi_shared.dir/stdlib_new_delete.cpp.o > libcxxabi/src/CMakeFiles/cxxabi_shared.dir/cxa_exception.cpp.o > libcxxabi/src/CMakeFiles/cxxabi_shared.dir/cxa_personality.cpp.o > libcxxabi/src/CMakeFiles/cxxabi_shared.dir/cxa_thread_atexit.cpp.o -lpthread > -lc && : > FAILED: /<>/build-llvm/lib/libc++abi.so.1.0 > : && /<>/build-llvm/./bin/clang++ > --target=mipsel-unknown-linux-gnu -fPIC -g -O2 > -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat > -Werror=format-security -fPIC -fvisibility-inlines-hidden -Werror=date-time > -Werror=unguarded-availability-new -Wall -Wextra -Wno-unused-parameter > -Wwrite-strings -Wcast-qual -Wmissing-field-initializers > -Wimplicit-fallthrough -Wcovered-switch-default -Wno-noexcept-type > -Wnon-virtual-dtor -Wdelete-non-virtual-dtor -Wsuggest-override -Wno-comment > -Wstring-conversion -fdiagnostics-color -ffunction-sections -fdata-sections > -O3 -DNDEBUG -Wl,-z,relro -Wl,-z,defs -Wl,-z,nodelete -nodefaultlibs > -shared -Wl,-soname,libc++abi.so.1 -o > /<>/build-llvm/lib/libc++abi.so.1.0 > libcxxabi/src/CMakeFiles/cxxabi_shared.dir/cxa_aux_runtime.cpp.o > libcxxabi/src/CMakeFiles/cxxabi_shared.dir/cxa_default_handlers.cpp.o > libcxxabi/src/CMakeFiles/cxxabi_shared.dir/cxa_demangle.cpp.o > libcxxabi/src/CMakeFiles/cxxabi_shared.dir/cxa_exception_storage.cpp.o > libcxxabi/src/CMakeFiles/cxxabi_shared.dir/cxa_guard.cpp.o > libcxxabi/src/CMakeFiles/cxxabi_shared.dir/cxa_handlers.cpp.o > libcxxabi/src/CMakeFiles/cxxabi_shared.dir/cxa_vector.cpp.o > libcxxabi/src/CMakeFiles/cxxabi_shared.dir/cxa_virtual.cpp.o > libcxxabi/src/CMakeFiles/cxxabi_shared.dir/stdlib_exception.cpp.o > libcxxabi/src/CMakeFiles/cxxabi_shared.dir/stdlib_stdexcept.cpp.o > libcxxabi/src/CMakeFiles/cxxabi_shared.dir/stdlib_typeinfo.cpp.o > libcxxabi/src/CMakeFiles/cxxabi_shared.dir/abort_message.cpp.o > libcxxabi/src/CMakeFiles/cxxabi_shared.dir/fallback_malloc.cpp.o > libcxxabi/src/CMakeFiles/cxxabi_shared.dir/private_typeinfo.cpp.o > libcxxabi/src/CMakeFiles/cxxabi_shared.dir/stdlib_new_delete.cpp.o > libcxxabi/src/CMakeFiles/cxxabi_shared.dir/cxa_exception.cpp.o > libcxxabi/src/CMakeFiles/cxxabi_shared.dir/cxa_personality.cpp.o > libcxxabi/src/CMakeFiles/cxxabi_shared.dir/cxa_thread_atexit.cpp.o -lpthread > -lc && : > /usr/bin/ld: libcxxabi/src/CMakeFiles/cxxabi_shared.dir/cxa_guard.cpp.o: in > function `~LockGuard': > ./build-llvm/runtimes/runtimes-bins/./libcxxabi/src/cxa_guard_impl.h:(.text.unlikely.__cxa_guard_acquire+0x1cc): > undefined reference to `_Unwind_Resume' > /usr/bin/ld: > ./build-llvm/runtimes/runtimes-bins/./libcxxabi/src/cxa_guard_impl.h:(.text.unlikely.__cxa_guard_acquire+0x1d4): > undefined reference to `_Unwind_Resume' > /usr/bin/ld: libcxxabi/src/CMakeFiles/cxxabi_shared.dir/cxa_demangle.cpp.o: > in function `~AbstractManglingParser': >
Processed: Re: Bug#996796: llvm-toolchain-12: FTBFS on i386|mipsel|powerpc since 1:12.0.1-10: undefined reference to `__udivdi3'
Processing control commands: > retitle -1 llvm-toolchain-12: FTBFS on i386|mipsel|powerpc since 1:12.0.1-10: > undefined reference to `__udivdi3' Bug #996796 [src:llvm-toolchain-12] llvm-toolchain-12: FTBFS on i386 since 1:12.0.1-10: undefined reference to `__udivdi3' Changed Bug title to 'llvm-toolchain-12: FTBFS on i386|mipsel|powerpc since 1:12.0.1-10: undefined reference to `__udivdi3'' from 'llvm-toolchain-12: FTBFS on i386 since 1:12.0.1-10: undefined reference to `__udivdi3''. -- 996796: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=996796 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#996796: llvm-toolchain-12: FTBFS on i386|mipsel|powerpc since 1:12.0.1-10: undefined reference to `__udivdi3'
Control: retitle -1 llvm-toolchain-12: FTBFS on i386|mipsel|powerpc since 1:12.0.1-10: undefined reference to `__udivdi3' On Mon, 18 Oct 2021 at 21:40:33 +0100, Simon McVittie wrote: > The restructuring in 1:12.0.1-10 seem to have triggered a FTBFS on i386 ... > Utility.h:56 is dividing a uint64_t by 10. I would guess that the problem > is -nodefaultlibs suppressing linking with LLVM's equivalent of libgcc > (libclang_rt?) so there's no implementation of the out-of-line __udivdi3() > call. Looking more closely at the mipsel log, mipsel also has this bug (among others). Among non-release architectures, so does powerpc. It's possible that the other 32-bit release architectures, armel and armhf, would also have this bug if their builds got further along. smcv
Bug#996795: silversearcher-ag-el: diff for NMU version 0.48-1.1
Control: tags 996795 + patch
Control: tags 996795 + pending
Dear maintainer,
I've prepared an NMU for silversearcher-ag-el (versioned as 0.48-1.1)
and uploaded it to DELAYED/5. Please feel free to tell me if I should
delay it longer.
Regards.
--
Sean Whitton
diff -Nru silversearcher-ag-el-0.48/debian/changelog
silversearcher-ag-el-0.48/debian/changelog
--- silversearcher-ag-el-0.48/debian/changelog 2020-05-13 23:34:22.0
-0700
+++ silversearcher-ag-el-0.48/debian/changelog 2021-10-18 13:43:54.0
-0700
@@ -1,3 +1,13 @@
+silversearcher-ag-el (0.48-1.1) unstable; urgency=medium
+
+ * Non-maintainer upload.
+ * Drop build-dep on elpa-dash-functional & require elpa-dash >= 2.18.0
+(Closes: #996795).
+ * Set autopkgtest_keep in debian/elpa-test.
+Otherwise, the ert_eval generates an error and the autopkgtest fails.
+
+ -- Sean Whitton Mon, 18 Oct 2021 13:43:54 -0700
+
silversearcher-ag-el (0.48-1) unstable; urgency=medium
* new upstream release (Closes: #960560)
diff -Nru silversearcher-ag-el-0.48/debian/control
silversearcher-ag-el-0.48/debian/control
--- silversearcher-ag-el-0.48/debian/control2020-05-13 23:34:22.0
-0700
+++ silversearcher-ag-el-0.48/debian/control2021-10-18 13:43:54.0
-0700
@@ -10,7 +10,7 @@
Package: elpa-ag
Architecture: all
-Depends: ${shlibs:Depends}, ${misc:Depends}, emacsen-common (>= 2.0.8),
silversearcher-ag, elpa-s, elpa-dash, elpa-dash-functional
+Depends: ${shlibs:Depends}, ${misc:Depends}, emacsen-common (>= 2.0.8),
silversearcher-ag, elpa-s, elpa-dash
Built-Using: ${misc:Built-Using}
Recommends: emacs (>= 46.0)
Enhances: emacs, emacs24, emacs25
diff -Nru silversearcher-ag-el-0.48/debian/elpa-test
silversearcher-ag-el-0.48/debian/elpa-test
--- silversearcher-ag-el-0.48/debian/elpa-test 2020-05-13 23:34:22.0
-0700
+++ silversearcher-ag-el-0.48/debian/elpa-test 2021-10-18 13:43:54.0
-0700
@@ -1 +1,2 @@
+autopkgtest_keep = test/test-helper.el
ert_eval = (load-file "test/test-helper.el")
diff -Nru
silversearcher-ag-el-0.48/debian/patches/drop-build-dep-on-elpa-dash-functional--.patch
silversearcher-ag-el-0.48/debian/patches/drop-build-dep-on-elpa-dash-functional--.patch
---
silversearcher-ag-el-0.48/debian/patches/drop-build-dep-on-elpa-dash-functional--.patch
1969-12-31 17:00:00.0 -0700
+++
silversearcher-ag-el-0.48/debian/patches/drop-build-dep-on-elpa-dash-functional--.patch
2021-10-18 13:43:54.0 -0700
@@ -0,0 +1,19 @@
+From: Sean Whitton
+Date: Mon, 18 Oct 2021 12:53:15 -0700
+X-Dgit-Generated: 0.48-1.1 fae27ab8924d4521197de32a98c6972f2fe57b91
+Subject: Drop build-dep on elpa-dash-functional & require elpa-dash >= 2.18.0
+
+
+---
+
+--- silversearcher-ag-el-0.48.orig/ag.el
silversearcher-ag-el-0.48/ag.el
+@@ -5,7 +5,7 @@
+ ;; Author: Wilfred Hughes
+ ;; Created: 11 January 2013
+ ;; Version: 0.48
+-;; Package-Requires: ((dash "2.8.0") (s "1.9.0") (cl-lib "0.5"))
++;; Package-Requires: ((dash "2.18.0") (s "1.9.0") (cl-lib "0.5"))
+ ;;; Commentary:
+
+ ;; Please see README.md for documentation, or read it online at
diff -Nru silversearcher-ag-el-0.48/debian/patches/series
silversearcher-ag-el-0.48/debian/patches/series
--- silversearcher-ag-el-0.48/debian/patches/series 1969-12-31
17:00:00.0 -0700
+++ silversearcher-ag-el-0.48/debian/patches/series 2021-10-18
13:43:54.0 -0700
@@ -0,0 +1 @@
+drop-build-dep-on-elpa-dash-functional--.patch
signature.asc
Description: PGP signature
Processed: silversearcher-ag-el: diff for NMU version 0.48-1.1
Processing control commands: > tags 996795 + patch Bug #996795 [elpa-ag] silversearcher-ag-el: should drop dependencies on elpa-dash-functional Added tag(s) patch. > tags 996795 + pending Bug #996795 [elpa-ag] silversearcher-ag-el: should drop dependencies on elpa-dash-functional Added tag(s) pending. -- 996795: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=996795 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#996761: kwin-x11: KWin crashes and doesn't start
Hi, I assume you're using testing. Unfortunately, Plasma is broken in testing at the moment if you have upgraded libkdecorations2-5v5 to 5.23. Could you check that ? If this is the case, I wrote about a possible solution here: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=996726#10 -- Med vänliga hälsningar Patrick Franz
Bug#996781: [pkg-lua-devel] Bug#996781: Bug#996781: luarocks: Installation fails with dpkg error
Le lun. 18 oct. 2021 à 22:12, Jérémy Lal a écrit :
> Le lun. 18 oct. 2021 à 16:48, Oliver Schode a
> écrit :
>
> > Package: luarocks
> > Version: 3.7.0+dfsg1-1
> > Severity: grave
> > Justification: renders package unusable
> >
> > Hi,
> >
> > thanks for reviving the package. Now I'm getting this when attempting to
> > install however:
> >
> > Error: Cannot access repository at
> > /root/.luarocks/lib/luarocks/rocks-5.3
> > dpkg: error processing package luarocks (--configure):
> > installed luarocks package post-installation script subprocess
> > returned error exit status 1
> >
> >
> > luarocks.postinst:
> >
> > mkdir -p /usr/local/lib/luarocks/rocks/
> > luarocks-admin make_manifest --local-tree <---
> >
> > Using local-tree here is probably wrong.
>
>
> Indeed i have on my system:
> cat /etc/luarocks/config.lua
> rocks_trees = {
>home..[[/.luarocks]],
>[[/usr/local]]
> }
>
> (and a file named /etc/luarocks/config-5.1.lua with the same content).
>
> Several ideas to solve this:
> - stop assuming things and remove that postinstall script (both
> mkdir/luarocks-admin calls)
> i believe this is the correct, "lua-style" solution
> - do not create directory, but call make_manifest and do not fail
> postinstall if no tree is found
> - furthermore, add /etc/luarocks/config.lua with that above config
>
> Any thoughts about this ?
>
The luarocks changelog clearly states that it's up to the user to set
prefered location for installing lua rocks, so i'm opting for that too.
It has less side effects.
Jérémy
Bug#996796: llvm-toolchain-12: FTBFS on i386 since 1:12.0.1-10: undefined reference to `__udivdi3'
Source: llvm-toolchain-12 Version: 1:12.0.1-10 Severity: serious Tags: ftbfs Justification: fails to build from source (but built successfully in the past) The restructuring in 1:12.0.1-10 seem to have triggered a FTBFS on i386, which breaks multi-arch coinstallability with amd64: > [1385/1405] : && /<>/build-llvm/./bin/clang++ > --target=i686-pc-linux-gnu -fPIC -g -O2 -fdebug-prefix-map=/<>=. > -fstack-protector-strong -Wformat -Werror=format-security -fPIC > -fvisibility-inlines-hidden -Werror=date-time > -Werror=unguarded-availability-new -Wall -Wextra -Wno-unused-parameter > -Wwrite-strings -Wcast-qual -Wmissing-field-initializers > -Wimplicit-fallthrough -Wcovered-switch-default -Wno-noexcept-type > -Wnon-virtual-dtor -Wdelete-non-virtual-dtor -Wsuggest-override -Wno-comment > -Wstring-conversion -fdiagnostics-color -ffunction-sections -fdata-sections > -O3 -DNDEBUG -Wl,-z,relro -Wl,-z,defs -Wl,-z,nodelete -nodefaultlibs > -shared -Wl,-soname,libc++abi.so.1 -o > /<>/build-llvm/lib/libc++abi.so.1.0 > libcxxabi/src/CMakeFiles/cxxabi_shared.dir/cxa_aux_runtime.cpp.o > libcxxabi/src/CMakeFiles/cxxabi_shared.dir/cxa_default_handlers.cpp.o > libcxxabi/src/CMakeFiles/cxxabi_shared.dir/cxa_demangle.cpp.o > libcxxabi/src/CMakeFiles/cxxabi_shared.dir/cxa_exception_storage.cpp.o > libcxxabi/src/CMakeFiles/cxxabi_shared.dir/cxa_guard.cpp.o > libcxxabi/src/CMakeFiles/cxxabi_shared.dir/cxa_handlers.cpp.o > libcxxabi/src/CMakeFiles/cxxabi_shared.dir/cxa_vector.cpp.o > libcxxabi/src/CMakeFiles/cxxabi_shared.dir/cxa_virtual.cpp.o > libcxxabi/src/CMakeFiles/cxxabi_shared.dir/stdlib_exception.cpp.o > libcxxabi/src/CMakeFiles/cxxabi_shared.dir/stdlib_stdexcept.cpp.o > libcxxabi/src/CMakeFiles/cxxabi_shared.dir/stdlib_typeinfo.cpp.o > libcxxabi/src/CMakeFiles/cxxabi_shared.dir/abort_message.cpp.o > libcxxabi/src/CMakeFiles/cxxabi_shared.dir/fallback_malloc.cpp.o > libcxxabi/src/CMakeFiles/cxxabi_shared.dir/private_typeinfo.cpp.o > libcxxabi/src/CMakeFiles/cxxabi_shared.dir/stdlib_new_delete.cpp.o > libcxxabi/src/CMakeFiles/cxxabi_shared.dir/cxa_exception.cpp.o > libcxxabi/src/CMakeFiles/cxxabi_shared.dir/cxa_personality.cpp.o > libcxxabi/src/CMakeFiles/cxxabi_shared.dir/cxa_thread_atexit.cpp.o > /<>/build-llvm/lib/libunwind.so.1.0 -lpthread -lc && : > FAILED: /<>/build-llvm/lib/libc++abi.so.1.0 > : && /<>/build-llvm/./bin/clang++ --target=i686-pc-linux-gnu > -fPIC -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong > -Wformat -Werror=format-security -fPIC -fvisibility-inlines-hidden > -Werror=date-time -Werror=unguarded-availability-new -Wall -Wextra > -Wno-unused-parameter -Wwrite-strings -Wcast-qual > -Wmissing-field-initializers -Wimplicit-fallthrough -Wcovered-switch-default > -Wno-noexcept-type -Wnon-virtual-dtor -Wdelete-non-virtual-dtor > -Wsuggest-override -Wno-comment -Wstring-conversion -fdiagnostics-color > -ffunction-sections -fdata-sections -O3 -DNDEBUG -Wl,-z,relro -Wl,-z,defs > -Wl,-z,nodelete -nodefaultlibs -shared -Wl,-soname,libc++abi.so.1 -o > /<>/build-llvm/lib/libc++abi.so.1.0 > libcxxabi/src/CMakeFiles/cxxabi_shared.dir/cxa_aux_runtime.cpp.o > libcxxabi/src/CMakeFiles/cxxabi_shared.dir/cxa_default_handlers.cpp.o > libcxxabi/src/CMakeFiles/cxxabi_shared.dir/cxa_demangle.cpp.o > libcxxabi/src/CMakeFiles/cxxabi_shared.dir/cxa_exception_storage.cpp.o > libcxxabi/src/CMakeFiles/cxxabi_shared.dir/cxa_guard.cpp.o > libcxxabi/src/CMakeFiles/cxxabi_shared.dir/cxa_handlers.cpp.o > libcxxabi/src/CMakeFiles/cxxabi_shared.dir/cxa_vector.cpp.o > libcxxabi/src/CMakeFiles/cxxabi_shared.dir/cxa_virtual.cpp.o > libcxxabi/src/CMakeFiles/cxxabi_shared.dir/stdlib_exception.cpp.o > libcxxabi/src/CMakeFiles/cxxabi_shared.dir/stdlib_stdexcept.cpp.o > libcxxabi/src/CMakeFiles/cxxabi_shared.dir/stdlib_typeinfo.cpp.o > libcxxabi/src/CMakeFiles/cxxabi_shared.dir/abort_message.cpp.o > libcxxabi/src/CMakeFiles/cxxabi_shared.dir/fallback_malloc.cpp.o > libcxxabi/src/CMakeFiles/cxxabi_shared.dir/private_typeinfo.cpp.o > libcxxabi/src/CMakeFiles/cxxabi_shared.dir/stdlib_new_delete.cpp.o > libcxxabi/src/CMakeFiles/cxxabi_shared.dir/cxa_exception.cpp.o > libcxxabi/src/CMakeFiles/cxxabi_shared.dir/cxa_personality.cpp.o > libcxxabi/src/CMakeFiles/cxxabi_shared.dir/cxa_thread_atexit.cpp.o > /<>/build-llvm/lib/libunwind.so.1.0 -lpthread -lc && : > /usr/bin/ld: libcxxabi/src/CMakeFiles/cxxabi_shared.dir/cxa_demangle.cpp.o: > in function `(anonymous > namespace)::itanium_demangle::OutputStream::writeUnsigned(unsigned long long, > bool)': > ./build-llvm/runtimes/runtimes-bins/./libcxxabi/src/demangle/Utility.h:56: > undefined reference to `__udivdi3' > clang-12: error: linker command failed with exit code 1 (use -v to see > invocation) Utility.h:56 is dividing a uint64_t by 10. I would guess that the problem is -nodefaultlibs suppressing linking with LLVM's equivalent of libgcc (libclang_rt?) so there's no implementation of the out-of-line __udivdi3() call.
Bug#996778: xymon-client: disable logfetch's ability to execute arbitrary code
Hi, On 18/10/2021 21:55, Axel Beckert wrote: Hi again, Christoph Zechner wrote: Severity: critical This is clearly not "critical". Myon already fixed that. Apologies for that, I was not sure how to classify it, but since it was a security-related issue, I thought it was appropriate. Justification: root security hole It is also no root security hole. It gives you access to the xymon user only. (If the admin configured the xymon user to be able to use sudo, that's another problem.) That's true, reportbug stated "introduces a security hole allowing access to root (or another privileged system account), or data normally accessible only such accounts" and since xymon automatically creates a few sudoers entries for its plugins, I thought it best to use this. Sorry if that was a little over-zealous. :-/ Cheers Christoph Regards, Axel
Bug#996048: postfix-mta-sts-resolver: autopkgtest doesn't handle new version of ca-certificates nicely: rehash: warning: skipping ca-certificates.crt,it does not contain exactly one certificate or CRL
On Mon, Oct 18, 2021 at 02:50:50PM +0200, Benjamin Hof wrote: > Hi, > > I think the following change might be the relevant one: > > --- a/update-ca-certificates > +++ b/update-ca-certificates > @@ -164,8 +164,6 @@ >done > fi > > -rm -f "$CERTBUNDLE" > - > ADDED_CNT=$(wc -l < "$ADDED") > REMOVED_CNT=$(wc -l < "$REMOVED") > > It triggers this stderr output during openssl rehash (l. 184): > > rehash: warning: skipping ca-certificates.crt,it does not contain exactly > one certificate or CRL > Ah, that makes sense. Annoying... Kurt/Sebastian, do you think there's a chance openssl rehash could grow some sort of ignore option so update-ca-certificates could ask it to skip ca-certificates.crt, to avoid spitting out a warning for it? Thanks, Julien
Bug#996761: kwin crash on startup
Hi, yes, I confirm sobre behaviour as Albert, other environments are working with no issues, such as LXDE or xfce...but KDE/Plasma available in testing is currently unusable with latest nvidia-driver. Thanks. On Mon, 18 Oct 2021 21:57:43 +0200 Albert Netymk wrote: > I had the same problem as Francisco reported. > > My Nvidia card is NVIDIA Corporation TU117GLM [Quadro T1000 Mobile] > > kwin-x11: 4:5.21.5-2 > nvidia-driver: 470.74-1 > linux-image-amd64: 5.14.9-2 > > I tried to downgrade nvidia-driver, but had problems while installing > the package from stable release, so I went to install LXDE instead, > which seems to work fine with the latest nvidia-driver. > > /Albert > >
Bug#996781: [pkg-lua-devel] Bug#996781: luarocks: Installation fails with dpkg error
Le lun. 18 oct. 2021 à 16:48, Oliver Schode a
écrit :
> Package: luarocks
> Version: 3.7.0+dfsg1-1
> Severity: grave
> Justification: renders package unusable
>
> Hi,
>
> thanks for reviving the package. Now I'm getting this when attempting to
> install however:
>
> Error: Cannot access repository at
> /root/.luarocks/lib/luarocks/rocks-5.3
> dpkg: error processing package luarocks (--configure):
> installed luarocks package post-installation script subprocess
> returned error exit status 1
>
>
> luarocks.postinst:
>
> mkdir -p /usr/local/lib/luarocks/rocks/
> luarocks-admin make_manifest --local-tree <---
>
> Using local-tree here is probably wrong.
Indeed i have on my system:
cat /etc/luarocks/config.lua
rocks_trees = {
home..[[/.luarocks]],
[[/usr/local]]
}
(and a file named /etc/luarocks/config-5.1.lua with the same content).
Several ideas to solve this:
- stop assuming things and remove that postinstall script (both
mkdir/luarocks-admin calls)
i believe this is the correct, "lua-style" solution
- do not create directory, but call make_manifest and do not fail
postinstall if no tree is found
- furthermore, add /etc/luarocks/config.lua with that above config
Any thoughts about this ?
Bug#996778: Processed: severity of 996778 is grave
Re: Axel Beckert > "critical" is indeed clearly wrong. I'd have rather said "important" > only as the claim of being a "root hole" is wrong. But ok. I only moved it off "critical" which it really is not. If you think important (or wishlist?) makes more sense, go ahead. > I'm though not sure if this is acceptable for stable updates as it is > a rather invasive change IMHO. It would be ok if we buy the security part. Christoph
Bug#996778: Processed: severity of 996778 is grave
Hi Christoph, I admittedly just noticed the severity which the bug reporter set when seeing this mail: Debian Bug Tracking System wrote: > > severity 996778 grave > Bug #996778 [xymon-client] xymon-client: disable logfetch's ability to > execute arbitrary code > Severity set to 'grave' from 'critical' "critical" is indeed clearly wrong. I'd have rather said "important" only as the claim of being a "root hole" is wrong. But ok. I'm though not sure if this is acceptable for stable updates as it is a rather invasive change IMHO. Regards, Axel -- ,''`. | Axel Beckert , https://people.debian.org/~abe/ : :' : | Debian Developer, ftp.ch.debian.org Admin `. `' | 4096R: 2517 B724 C5F6 CA99 5329 6E61 2FF9 CD59 6126 16B5 `-| 1024D: F067 EA27 26B9 C3FC 1486 202E C09E 1D89 9593 0EDE
Bug#996761: kwin crash on startup
I had the same problem as Francisco reported. My Nvidia card is NVIDIA Corporation TU117GLM [Quadro T1000 Mobile] kwin-x11: 4:5.21.5-2 nvidia-driver: 470.74-1 linux-image-amd64: 5.14.9-2 I tried to downgrade nvidia-driver, but had problems while installing the package from stable release, so I went to install LXDE instead, which seems to work fine with the latest nvidia-driver. /Albert
Bug#996778: xymon-client: disable logfetch's ability to execute arbitrary code
Hi again, Christoph Zechner wrote: > Severity: critical This is clearly not "critical". Myon already fixed that. > Justification: root security hole It is also no root security hole. It gives you access to the xymon user only. (If the admin configured the xymon user to be able to use sudo, that's another problem.) Regards, Axel -- ,''`. | Axel Beckert , https://people.debian.org/~abe/ : :' : | Debian Developer, ftp.ch.debian.org Admin `. `' | 4096R: 2517 B724 C5F6 CA99 5329 6E61 2FF9 CD59 6126 16B5 `-| 1024D: F067 EA27 26B9 C3FC 1486 202E C09E 1D89 9593 0EDE
Bug#996561: marked as done (qepcad fails autopkgtests on !amd64, !i386)
Your message dated Mon, 18 Oct 2021 19:50:07 + with message-id and subject line Bug#996561: fixed in qepcad 1.74+ds-3 has caused the Debian Bug report #996561, regarding qepcad fails autopkgtests on !amd64, !i386 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.) -- 996561: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=996561 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: qepcad Version: 1.74+ds-2 Severity: serious X-Debbugs-Cc: dtorra...@piedmont.edu Hi Doug, qepcad fails its autopkgtests on every non-x86 arch as seen here. Can you fix this? https://qa.debian.org/excuses.php?package=qepcad Nilesh -- System Information: Debian Release: bookworm/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 5.14.0-1-amd64 (SMP w/8 CPU threads) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled --- End Message --- --- Begin Message --- Source: qepcad Source-Version: 1.74+ds-3 Done: Doug Torrance We believe that the bug you reported is fixed in the latest version of qepcad, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 996...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Doug Torrance (supplier of updated qepcad package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Mon, 18 Oct 2021 15:15:13 -0400 Source: qepcad Built-For-Profiles: noudeb Architecture: source Version: 1.74+ds-3 Distribution: unstable Urgency: medium Maintainer: Debian Science Maintainers Changed-By: Doug Torrance Closes: 996561 Changes: qepcad (1.74+ds-3) unstable; urgency=medium . * debian/control - Bump Standards-Version to 4.6.0. * debian/copyright - Update copyright years. * debian/patches/signed-char-eof.patch - New patch; use signed char when reading input (Closes: #996561). * debian/rules - Use $(MAKE) instead of explicitly calling make. * debian/upstream/metadata - Add Bug-Submit field. Checksums-Sha1: f1df00c28cb636da1671460813c8f29d7014582b 2063 qepcad_1.74+ds-3.dsc bb95d0b3c1c43422f1792773ce6f7612fbc744b0 26152 qepcad_1.74+ds-3.debian.tar.xz d5c8fa71154794a76247abfe37c1301d742c993e 10119 qepcad_1.74+ds-3_source.buildinfo Checksums-Sha256: 6e980a614b2223a0379ade78f7edbd3237853dbb01ba061f3db159a112509fd5 2063 qepcad_1.74+ds-3.dsc 5e57c6331dbd37e1da5fc796534013a50c1af216fc1064a0d61722a7b000c70a 26152 qepcad_1.74+ds-3.debian.tar.xz 8596badb5d814f1a792e682be4934022c71910059e1a482c04cfe348119268c8 10119 qepcad_1.74+ds-3_source.buildinfo Files: b7b5b3db9e6193192259b88bb56a03b3 2063 math optional qepcad_1.74+ds-3.dsc 6de574ef8a489093bbbf7e562033a054 26152 math optional qepcad_1.74+ds-3.debian.tar.xz 779c22a3cdb52d4f9a040316f8753bae 10119 math optional qepcad_1.74+ds-3_source.buildinfo -BEGIN PGP SIGNATURE- iQJLBAEBCgA1FiEEupghwS4HiU+y5K0AkdxKd57FyRAFAmFtyaIXHGR0b3JyYW5j ZUBwaWVkbW9udC5lZHUACgkQkdxKd57FyRArTw//Wgc04pzi3PT/lYr+Wx/IUE3J 9HyBdx+g6rfNYeoEzGIcd5SJuSYr3FpEYQ1BVyilb/28fLkK/msxPigBCrQGCfmH KArTx1XiFYvtRUb2vyegIXyC/yV/htDm+y1gLpojutwwSrpedhlH2Hn3wUPU2YbM kjXmznRNMA7JIyQXxmbmtJwvQZrzCy/u5+FESklH3DW6R+zIll6XkRCcPuDuyUKy 7uG3DEyRP03EqhUTCjF0GNDbOZqJUWpXHNYu9Lg6FnLaQyPcwj2+CRuKOxFsXjvX 0U1DU7nZ9OkXCzTxaFkXcDyRmXr9YoIvX/B+CRabqs4iPzTeBjv5/atofu6eOyh0 c6mP0ME7iFyJkEwWwIzAuN+oJ9AJM5o08GU/fksMZd917ZZxy1/0UTFfpK7wOy27 YaYmkEIP6oh37VPFzOLYfsH5qvjgEibde2SYUYMXFoJavESf67VuS2/TgqihJkm2 ss0u9/roHmOClg8dCKesoVRJC8U6kvgnDz6C/hUU8bv6HWv0qCsMFnVxq3scUUW6 X9YdNk9DVogvvaH9aGiRls0FDExRlW6HTR88EwJvuVooq4s/zKKi1hOAX1neLEyW teXYCD+/tfbVLV8IXxZFMU81e37dfbIarw7w3NfpV15/gjZ50YGBBlIihfuQHKwq Ac8E1hFMr3cuqTmVnxg= =YluL -END PGP SIGNATURE End Message ---
Bug#996795: silversearcher-ag-el: should drop dependencies on elpa-dash-functional
Package: elpa-ag Version: 0.48-1 Severity: serious Justification: not installable in sid due to package removal Hello, Per [1] dash-functional.el is obsolete and elpa-dash-functional has been removed from unstable. It should be sufficient simply to patch out any `require' calls or similar and require dash.el 2.18.0 or newer. [1] https://github.com/magnars/dash.el/wiki/Obsoletion-of-dash-functional.el -- Sean Whitton signature.asc Description: PGP signature
Bug#996778: xymon-client: disable logfetch's ability to execute arbitrary code
Re: Axel Beckert > > LOGFETCHOPTS="--noexec" > > > > instead. > > Hrm. The Debian package for sure will switch that option if upstream > does. > > I'm though currently a bit reluctant to apply this patch and deviate > from upstream's defaults (even more) since the default settings with > IP addresses are less prone to that attack as if the admin uses DNS > names instead of the recommended use of IP addresses for the server. > Tagging as "upstream" for now. > > JFTR: I use that feature in some places and I don't know how widely it > is used by others. I though suspect it is indeed used rather rarely. > The common use-case seems to be if the syslog server adds a date > extension already upon file creation so that logrotate becomes > unnecessary. AFAIK none of Debian's syslog servers does that by > default, though. I guess most installations don't need the feature, so we could indeed disable it by default, and put a note into README.Debian (+ NEWS) that people need to actively enable it. Christoph
Bug#995735: dask.distributed: autopkgtest sometimes times out on ci.d.n worker since dask migrated
Hi, I missed this bug report. I don't have any idea why the tests were failing on a large machine. I've been building and running the autopkgtests for dask.distributed my laptop with 2 cores & 16GB of RAM, and it' hasn't hung for me. I also glanced at the current CI build results and all the runs with 2021.09.1+ds.1-1 seem to be finishing in about 25 minutes both passing and faild tests. I do see the 2h runs with version 2021.08.1+ds.1-1 https://ci.debian.net/packages/d/dask.distributed/ Do you think that's a good enough test to close this bug? Diane
Processed: Re: Bug#996778: xymon-client: disable logfetch's ability to execute arbitrary code
Processing control commands: > retitle -1 xymon-client: Disable by default the ability of logfetch to > execute arbitrary code fetched from the Xymon server Bug #996778 [xymon-client] xymon-client: disable logfetch's ability to execute arbitrary code Changed Bug title to 'xymon-client: Disable by default the ability of logfetch to execute arbitrary code fetched from the Xymon server' from 'xymon-client: disable logfetch's ability to execute arbitrary code'. > forwarded -1 https://lists.xymon.com/archive/2021-October/047749.html Bug #996778 [xymon-client] xymon-client: Disable by default the ability of logfetch to execute arbitrary code fetched from the Xymon server Set Bug forwarded-to-address to 'https://lists.xymon.com/archive/2021-October/047749.html'. > tag -1 + upstream confirmed Bug #996778 [xymon-client] xymon-client: Disable by default the ability of logfetch to execute arbitrary code fetched from the Xymon server Added tag(s) upstream and confirmed. -- 996778: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=996778 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Re: Bug#996561: qepcad fails autopkgtests on !amd64, !i386
Processing control commands: > tags -1 pending Bug #996561 [qepcad] qepcad fails autopkgtests on !amd64, !i386 Added tag(s) pending. -- 996561: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=996561 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#996778: xymon-client: disable logfetch's ability to execute arbitrary code
Control: retitle -1 xymon-client: Disable by default the ability of logfetch to execute arbitrary code fetched from the Xymon server Control: forwarded -1 https://lists.xymon.com/archive/2021-October/047749.html Control: tag -1 + upstream confirmed Hi, Christoph Zechner wrote: > Package: xymon-client > Severity: critical > Tags: patch security > Justification: root security hole > X-Debbugs-Cc: zech...@vrvis.at, Debian Security Team > > > The default for logfetch's options (found in /etc/xymon/xymonclient.cfg) is: > > LOGFETCHOPTS="" > > which enables it to execute arbitrary code [1]. Yes, I saw the discussion on that on the upstream mailing list[2]. As mentioned there by others, this is on purpose and only during a "pull" from the server, i.e. no remote code execution by arbitrary attackers. I updated the bug report title accordingly. [2] https://lists.xymon.com/archive/2021-October/thread.html#47749 Downside here is that Xymon doesn't use TLS and hence DNS spoofing attacks might be able to redirect the client's connection if hostnames instead of the recommended IPs are used in /etc/default/xymon-client. Otherwise attacking this would require first hijacking either the routing or a router inbetween for a MITM attack on this. > This can and should be > prevented by default by using > > LOGFETCHOPTS="--noexec" > > instead. Hrm. The Debian package for sure will switch that option if upstream does. I'm though currently a bit reluctant to apply this patch and deviate from upstream's defaults (even more) since the default settings with IP addresses are less prone to that attack as if the admin uses DNS names instead of the recommended use of IP addresses for the server. Tagging as "upstream" for now. JFTR: I use that feature in some places and I don't know how widely it is used by others. I though suspect it is indeed used rather rarely. The common use-case seems to be if the syslog server adds a date extension already upon file creation so that logrotate becomes unnecessary. AFAIK none of Debian's syslog servers does that by default, though. Myon: Any opinion on this? Regards, Axel -- ,''`. | Axel Beckert , https://people.debian.org/~abe/ : :' : | Debian Developer, ftp.ch.debian.org Admin `. `' | 4096R: 2517 B724 C5F6 CA99 5329 6E61 2FF9 CD59 6126 16B5 `-| 1024D: F067 EA27 26B9 C3FC 1486 202E C09E 1D89 9593 0EDE
Bug#996561: qepcad fails autopkgtests on !amd64, !i386
Control: tags -1 pending On Fri 15 Oct 2021 01:52:37 PM EDT, Doug Torrance wrote: On Fri 15 Oct 2021 10:29:40 AM EDT, Nilesh Patra wrote: qepcad fails its autopkgtests on every non-x86 arch as seen here. Can you fix this? I confirmed that QEPCAD isn't functioning for me locally on an armhf system (Raspberry Pi). I'll see if I can track down the issue. I believe the issue was that QEPCAD was reading input using a `char`, and occasionally checking to see if this was EOF, which is negative (-1). But on the failing architectures, `char` defaults to unsigned, so it was getting 255 instead of -1, and we ended up with infinite loops. I'll upload a new version of the package containing a patch, which I confirmed works on armhf, shortly. Doug signature.asc Description: PGP signature
Processed: Bug#983981 marked as pending in bamtools
Processing control commands: > tag -1 pending Bug #983981 [src:bamtools] bamtools: ftbfs with GCC-11 Ignoring request to alter tags of bug #983981 to the same tags previously set -- 983981: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=983981 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#983981: marked as pending in bamtools
Control: tag -1 pending Hello, Bug #983981 in bamtools reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/med-team/bamtools/-/commit/798f6d312609f68af08dfd32e827d07e811195cc d/rules: build with -fno-new-ttp-matching flag Closes: #983981 (this message was generated automatically) -- Greetings https://bugs.debian.org/983981
Bug#996764: FTBFS: test misc/swaplabel failure
Chris,
On Mon, Oct 18, 2021 at 03:17:14PM +0200, Chris Hofstaedtler wrote:
> Could you add your Signed-off-by: to the patch, so I can forward it
> upstream? (Or you could send it to util-li...@vger.kernel.org
> directly, too.)
Yes, of course. Attached. I'll leave you to send it upstream, so everything is
in one place. Hope that is OK.
Best wishes
Mark
>From b2e6485bbb9e9ce1929d8ba4a3aa0965a52cd52f Mon Sep 17 00:00:00 2001
From: Mark Hindley
Date: Sun, 17 Oct 2021 20:25:47 +0100
Subject: [PATCH] Fix test/misc/swaplabel failure due to change in mkswap
behaviour.
mkswap now warns if the image file has holes. If fallocate is used to create the
file, use POSIX semantics to ensure the file has no holes.
This fixes the test failure
misc: swaplabel ... FAILED (misc/swaplabel)
= script: /build/util-linux-2.37.2/tests/ts/misc/swaplabel =
= OUTPUT =
1 Setting up swapspace version 1, size = 9 pages (9xPGSZ bytes)
2 LABEL=1234567890abcde, UUID=12345678-abcd-abcd-abcd-1234567890ab
3 LABEL: 1234567890abcde
4 UUID: 12345678-abcd-abcd-abcd-1234567890ab
= EXPECTED ===
1 Setting up swapspace version 1, size = 9 pages (9xPGSZ bytes)
2 LABEL=1234567890abcde, UUID=12345678-abcd-abcd-abcd-1234567890ab
3 LABEL: 1234567890abcde
4 UUID: 12345678-abcd-abcd-abcd-1234567890ab
= O/E diff ===
==
The additional error appears in swaplabel.err:
mkswap: contains holes or other unsupported extents.
This swap file can be rejected by kernel on swap activation!
Use --verbose for more details.
Signed-off-by: Mark Hindley
---
tests/ts/misc/swaplabel | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/tests/ts/misc/swaplabel b/tests/ts/misc/swaplabel
index 0801cb213..8b1abb5c3 100755
--- a/tests/ts/misc/swaplabel
+++ b/tests/ts/misc/swaplabel
@@ -25,7 +25,7 @@ ts_check_test_command "$TS_HELPER_SYSINFO"
# fallocate does not work on most file systems
function fallocate_or_skip()
{
- $TS_CMD_FALLOCATE -l $1 $2 2>/dev/null || \
+ $TS_CMD_FALLOCATE -x -l $1 $2 2>/dev/null || \
truncate -s $1 $2 || \
ts_skip "no way to create test image"
}
--
2.20.1
Bug#981761:
Are these files with global writable permissions perhaps being installed by the postinst script? It's not immediately obvious to me where they've come from.
Processed: [bts-link] source package src:fityk
Processing commands for cont...@bugs.debian.org: > # > # bts-link upstream status pull for source package src:fityk > # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html > # https://bts-link-team.pages.debian.net/bts-link/ > # > user debian-bts-l...@lists.debian.org Setting user to debian-bts-l...@lists.debian.org (was debian-bts-l...@lists.debian.org). > # remote status report for #984123 (http://bugs.debian.org/984123) > # Bug title: fityk: ftbfs with GCC-11 > # * https://github.com/wojdyr/fityk/issues/37 > # * remote status changed: (?) -> closed > # * closed upstream > tags 984123 + fixed-upstream Bug #984123 [src:fityk] fityk: ftbfs with GCC-11 Added tag(s) fixed-upstream. > usertags 984123 + status-closed There were no usertags set. Usertags are now: status-closed. > thanks Stopping processing here. Please contact me if you need assistance. -- 984123: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=984123 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#996636: marked as done (trafficserver FTBFS on 32bit)
Your message dated Mon, 18 Oct 2021 17:03:30 +
with message-id
and subject line Bug#996636: fixed in trafficserver 9.1.0+ds-2
has caused the Debian Bug report #996636,
regarding trafficserver FTBFS on 32bit
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.)
--
996636: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=996636
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: trafficserver
Version: 9.1.0+ds-1
Severity: serious
Tags: ftbfs
https://buildd.debian.org/status/logs.php?pkg=trafficserver=9.1.0%2Bds-1
...
Log.cc: In static member function ‘static void Log::trace_va(bool, const
sockaddr*, uint16_t, const char*, va_list)’:
Log.cc:1276:14: error: invalid cast from type ‘ink_thread’ {aka ‘long unsigned
int’} to type ‘uint64_t’ {aka ‘long long unsigned int’}
1276 | reinterpret_cast(ink_thread_self()), in ? "RECV"
: "SEND", ip, peer_port);
| ^
...
--- End Message ---
--- Begin Message ---
Source: trafficserver
Source-Version: 9.1.0+ds-2
Done: Jean Baptiste Favre
We believe that the bug you reported is fixed in the latest version of
trafficserver, which is due to be installed in the Debian FTP archive.
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to 996...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Jean Baptiste Favre (supplier of updated trafficserver
package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Mon, 18 Oct 2021 16:58:03 +0200
Source: trafficserver
Architecture: source
Version: 9.1.0+ds-2
Distribution: unstable
Urgency: medium
Maintainer: Jean Baptiste Favre
Changed-By: Jean Baptiste Favre
Closes: 996636
Changes:
trafficserver (9.1.0+ds-2) unstable; urgency=medium
.
* Restrict architecture to 64bits (Closes: #996636)
Checksums-Sha1:
752f2f79a1b36dd84dd33639d78fb3810c45dab5 3016 trafficserver_9.1.0+ds-2.dsc
2685eb5dfdc5efe64d6622eec868f34d4e06730f 30792
trafficserver_9.1.0+ds-2.debian.tar.xz
cada9e273062c52bf4e86c17d24b24879958aeac 13543
trafficserver_9.1.0+ds-2_source.buildinfo
Checksums-Sha256:
784d39f9329611e9491ffee196a15796d337494752e7b9e7c791ea8bba7c62b8 3016
trafficserver_9.1.0+ds-2.dsc
a27fabf3ad4d7f3dd2ce860bcd6d18e664e40b50afb4c24bc896420b899a14e1 30792
trafficserver_9.1.0+ds-2.debian.tar.xz
9870125cfa7aeaa01acea641043c0a5baf0af4b046e0de4a1340d6e37bea10c9 13543
trafficserver_9.1.0+ds-2_source.buildinfo
Files:
0e8654249613ce8e61f1d94b54c618bd 3016 web optional trafficserver_9.1.0+ds-2.dsc
aa1637017467f6bdf9e16b76e8814c4f 30792 web optional
trafficserver_9.1.0+ds-2.debian.tar.xz
07bdd730793844f2ef9121badfa602e3 13543 web optional
trafficserver_9.1.0+ds-2_source.buildinfo
-BEGIN PGP SIGNATURE-
iQKTBAEBCgB9FiEEToRbojDLTUSJBphHtN1Tas99hzcFAmFtozJfFIAALgAo
aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldDRF
ODQ1QkEyMzBDQjRENDQ4OTA2OTg0N0I0REQ1MzZBQ0Y3RDg3MzcACgkQtN1Tas99
hzfZSQ/8CgybIUcU6GyFOS1xJoIl1+VFsf2N15eMepmV3CUWkuLBQ5NQUlZLk56y
c3W+GeDO/NMy141qpJ6DwPHYrmX7qNODjcEMczIxGDmlA2RPs1CbOpniQlzPKZ2C
z1FHugK1pG3JwbK4g9LcQmDvcvCUxRn0+ScqVE9+6YlN1oWEkd3rk2kAYbxI8JGP
ZaCBhNDAT7x9LC9hWdyfK8Odek/epCzUff4z+vwJ/imLTx4YCp/fybkCaqno61vK
emqVjMvb5kw8pDCTE1RH6zRkvRNEzauVNh1b8dqxUmi5IqvONa8bU7j7ky8bGwLX
PaJD6kRKjGBbazkZE6FVlE0lEBUE6w7SKboPZQruF7GlskTis6P0tNZynI1Q9IxU
iSB6ydqdGpvr6H9AGugWOewW98uhCRUDdL7LI4qIqjfuKb/6DAMrrpaH1xa36pDv
TB65ecPhZldFvlNqAdjBOJ0hkE4qXuUuntmEu6oMKMVQYozRWMspudeWGRpk+SeB
Ldo2mr5WnOiIXbj/C5iBl2xWWdb2TSHAr+svDQXG9YA2p5zRIt5LLW+nt8e3Bphu
mojeos1G4FInAhgra9q06crwF2h9/ppWtcS0SiNxVjHhW8IXnKSuiDyTsFCmEzLZ
0gQfQsfiePcsiKbdmf6YZ6hfAuC2j86vBIngXaOYLhap5kB7DyU=
=M4AT
-END PGP SIGNATURE End Message ---
Bug#992696: marked as done (389-ds: 389-DS no longer starts since bullseye due to libjemalloc.so.2 not found)
Your message dated Mon, 18 Oct 2021 16:48:37 + with message-id and subject line Bug#992696: fixed in 389-ds-base 1.4.4.17-1 has caused the Debian Bug report #992696, regarding 389-ds: 389-DS no longer starts since bullseye due to libjemalloc.so.2 not found to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 992696: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=992696 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: 389-ds Version: 1.4.4.11-2 Severity: grave Justification: renders package unusable -- System Information: Debian Release: 11.0 APT prefers stable-security APT policy: (500, 'stable-security'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 4.19.0-8-amd64 (SMP w/4 CPU threads) Kernel taint flags: TAINT_SOFTLOCKUP Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), LANGUAGE=en_GB:en Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages 389-ds depends on: ii 389-ds-base 1.4.4.11-2 ii cockpit-389-ds 1.4.4.11-2 389-ds recommends no packages. 389-ds suggests no packages. -- no debconf information Hello, Since upgrading from Buster to Bullseye the 389-DS service "dirsrv" no longer starts due to "libjemalloc.so.2" not being found. (For below, my instance is named "amun".) >From syslog when invoking `service dirsrv@amun.service`: > Aug 22 14:04:14 amun systemd[1]: Starting 389 Directory Server > amun.service > Aug 22 14:04:14 amun ds_systemd_ask_password_acl[12466]: ERROR: ld.so: object > '/usr/lib/x86_64-linux-gnu/dirsrv/lib/libjemalloc.so.2' from LD_PRELOAD > cannot be preloaded (cannot open shared object file): ignored. > Aug 22 14:04:14 amun ds_systemd_ask_password_acl[12468]: ERROR: ld.so: object > '/usr/lib/x86_64-linux-gnu/dirsrv/lib/libjemalloc.so.2' from LD_PRELOAD > cannot be preloaded (cannot open shared object file): ignored. > Aug 22 14:04:14 amun ds_systemd_ask_password_acl[12469]: ERROR: ld.so: object > '/usr/lib/x86_64-linux-gnu/dirsrv/lib/libjemalloc.so.2' from LD_PRELOAD > cannot be preloaded (cannot open shared object file): ignored. > Aug 22 14:04:14 amun ds_systemd_ask_password_acl[12468]: grep: > /etc/dirsrv/slapd-amun.service/dse.ldif: No such file or directory > Aug 22 14:04:14 amun ds_systemd_ask_password_acl[12470]: ERROR: ld.so: object > '/usr/lib/x86_64-linux-gnu/dirsrv/lib/libjemalloc.so.2' from LD_PRELOAD > cannot be preloaded (cannot open shared object file): ignored. > Aug 22 14:04:14 amun ns-slapd[12471]: ERROR: ld.so: object > '/usr/lib/x86_64-linux-gnu/dirsrv/lib/libjemalloc.so.2' from LD_PRELOAD > cannot be preloaded (cannot open shared object file): ignored. > Aug 22 14:04:14 amun ns-slapd[12471]: [22/Aug/2021:14:04:14.763765705 +0200] > - INFO - dse_check_file - The config /etc/dirsrv/slapd-amun.service/dse.ldif > can not be accessed. Attempting restore ... (reason: 0) > Aug 22 14:04:14 amun ns-slapd[12471]: [22/Aug/2021:14:04:14.763855927 +0200] > - INFO - dse_check_file - The backup > /etc/dirsrv/slapd-amun.service/dse.ldif.bak can not be accessed. Check it > exists and permissions. > Aug 22 14:04:14 amun ns-slapd[12471]: [22/Aug/2021:14:04:14.763863191 +0200] > - ERR - slapd_bootstrap_config - No valid configurations can be accessed! You > must restore /etc/dirsrv/slapd-amun.service/dse.ldif from backup! > Aug 22 14:04:14 amun ns-slapd[12471]: [22/Aug/2021:14:04:14.763868899 +0200] > - EMERG - main - The configuration files in directory > /etc/dirsrv/slapd-amun.service could not be read or were not found. Please > refer to the error log or output for more information. > Aug 22 14:04:14 amun systemd[1]: dirsrv@amun.service.service: Main process > exited, code=exited, status=1/FAILURE > Aug 22 14:04:14 amun systemd[1]: dirsrv@amun.service.service: Failed with > result 'exit-code'. > Aug 22 14:04:14 amun systemd[1]: Failed to start 389 Directory Server > amun.service.. I noticed the configuration directory does not end with ".service", it's just "/etc/dirsrv/slapd-amun", so looks like an upgrade has changed the service to look at the wrong location. Creating a symbolic link to work around that did reduce the quantity of errors, but the "libjemalloc.so.2" library issue is still there: > Aug 22 14:13:37 amun systemd[1]: Starting 389 Directory Server > amun.service > Aug 22 14:13:37 amun ds_systemd_ask_password_acl[14025]: ERROR: ld.so: object > '/usr/lib/x86_64-linux-gnu/dirsrv/lib/libjemalloc.so.2' from LD_PRELOAD > cannot be preloaded (cannot open shared object file): ignored.
Bug#996551: marked as done (llvm-13-dev: Missing dependency to libomp-13-dev)
Your message dated Mon, 18 Oct 2021 16:18:46 + with message-id and subject line Bug#996551: fixed in llvm-toolchain-13 1:13.0.0-6 has caused the Debian Bug report #996551, regarding llvm-13-dev: Missing dependency to libomp-13-dev 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.) -- 996551: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=996551 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: llvm-13-dev Version: 1:13.0.0-5 Severity: important X-Debbugs-Cc: joubert...@gmail.com Dear Maintainer, With the recent move of llvm-omp-device-info from llvm-X to libomp8-dev, done in llvm-toolchain-13 (1:13.0.0-4), this package should now depend on libomp-X-dev The current situation is that llvm-X-dev references llvm-omp-device-info as part of an installed targets in its cmake configuration, but since it no longer provides that file any attempt to use the LLVM cmake package results in an error: CMake Error at /usr/lib/llvm-13/lib/cmake/llvm/LLVMExports.cmake:1501 (message): The imported target "llvm-omp-device-info" references the file "/usr/lib/llvm-13/bin/llvm-omp-device-info" but this file does not exist. Possible reasons include: * The file was deleted, renamed, or moved to another location. * An install or uninstall procedure did not complete successfully. * The installation package was faulty and contained "/usr/lib/llvm-13/lib/cmake/llvm/LLVMExports.cmake" but not all the files it references. Manually installing libomp-X-dev fixes the problem. -- System Information: Debian Release: bookworm/sid APT prefers testing APT policy: (990, 'testing'), (800, 'stable-updates'), (800, 'stable'), (700, 'unstable'), (90, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 5.14.0-2-amd64 (SMP w/8 CPU threads) Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), LANGUAGE=fr Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages llvm-13-dev depends on: ii libc6 2.32-4 ii libclang-cpp13 1:13.0.0-5 ii libffi-dev 3.4.2-2 ii libgcc-s1 11.2.0-9 ii libllvm13 1:13.0.0-5 ii libncurses-dev [libtinfo-dev] 6.2+20201114-4 ii libstdc++6 11.2.0-9 ii libtinfo-dev 6.2+20201114-4 ii libxml2-dev2.9.12+dfsg-5 ii libz3-dev 4.8.12-1+b1 ii llvm-131:13.0.0-5 ii llvm-13-tools 1:13.0.0-5 llvm-13-dev recommends no packages. llvm-13-dev suggests no packages. --- End Message --- --- Begin Message --- Source: llvm-toolchain-13 Source-Version: 1:13.0.0-6 Done: Sylvestre Ledru We believe that the bug you reported is fixed in the latest version of llvm-toolchain-13, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 996...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Sylvestre Ledru (supplier of updated llvm-toolchain-13 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: Fri, 15 Oct 2021 10:45:30 +0200 Source: llvm-toolchain-13 Architecture: source Version: 1:13.0.0-6 Distribution: unstable Urgency: medium Maintainer: LLVM Packaging Team Changed-By: Sylvestre Ledru Closes: 995684 996551 Changes: llvm-toolchain-13 (1:13.0.0-6) unstable; urgency=medium . * Remove omp-device-info from LLVMExports.cmake (Closes: #996551) * Fix a atomic issue. Thanks to YunQiang Su for the patch Partial fix for #995827 * Bring back the llvm manpages (Closes: #995684) Were generated at the wrong place Checksums-Sha1: 4f6a18e02970d11dc583b5dfb689787f2d3cf5ff 6732 llvm-toolchain-13_13.0.0-6.dsc a877e2db1fe0f34b9daeb75f92a0b2a406bc31f9 141736 llvm-toolchain-13_13.0.0-6.debian.tar.xz d77f8bbad65fe97264b9dc6c5db9407a9bb08241 12142 llvm-toolchain-13_13.0.0-6_source.buildinfo Checksums-Sha256: f9831840a70c0774dd30d5c9027acb5a8571034ecb50c2615be3e8ba73da2ec9 6732 llvm-toolchain-13_13.0.0-6.dsc 72b02d8031af6ddbc51c3624555ad064e023b08e2d690f7c56511d5227f106fc 141736
Bug#996631: marked as done (llvm-toolchain-13: autopkgtest failure)
Your message dated Mon, 18 Oct 2021 16:18:46 + with message-id and subject line Bug#996551: fixed in llvm-toolchain-13 1:13.0.0-6 has caused the Debian Bug report #996551, regarding llvm-toolchain-13: autopkgtest failure 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.) -- 996551: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=996551 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: llvm-toolchain-13 Version: 1:13.0.0-4 Severity: serious X-Debbugs-Cc: sramac...@debian.org The changes in 1:13.0.0-4 introduced new autopkgtest failures: | autopkgtest [11:21:06]: test cmake-test: [--- | -- The C compiler identification is GNU 10.3.0 | -- The CXX compiler identification is GNU 10.3.0 | -- Detecting C compiler ABI info | -- Detecting C compiler ABI info - done | -- Check for working C compiler: /usr/bin/cc - skipped | -- Detecting C compile features | -- Detecting C compile features - done | -- Detecting CXX compiler ABI info | -- Detecting CXX compiler ABI info - done | -- Check for working CXX compiler: /usr/bin/c++ - skipped | -- Detecting CXX compile features | -- Detecting CXX compile features - done | -- Could NOT find ZLIB (missing: ZLIB_LIBRARY ZLIB_INCLUDE_DIR) | -- Found LibXml2: /usr/lib/aarch64-linux-gnu/libxml2.so (found version "2.9.12") | CMake Error at /usr/lib/llvm-13/lib/cmake/llvm/LLVMExports.cmake:1501 (message): | The imported target "llvm-omp-device-info" references the file | | "/usr/lib/llvm-13/bin/llvm-omp-device-info" | | but this file does not exist. Possible reasons include: | | * The file was deleted, renamed, or moved to another location. | | * An install or uninstall procedure did not complete successfully. | | * The installation package was faulty and contained | | "/usr/lib/llvm-13/lib/cmake/llvm/LLVMExports.cmake" | | but not all the files it references. | | Call Stack (most recent call first): | /usr/lib/llvm-13/cmake/LLVMConfig.cmake:299 (include) | CMakeLists.txt:3 (find_package) | | | -- Configuring incomplete, errors occurred! | See also "/tmp/autopkgtest-lxc.w3ziie21/downtmp/autopkgtest_tmp/build/CMakeFiles/CMakeOutput.log". | autopkgtest [11:21:08]: test cmake-test: ---] | autopkgtest [11:21:09]: test cmake-test: - - - - - - - - - - results - - - - - - - - - - | cmake-test FAIL non-zero exit status 1 See https://ci.debian.net/data/autopkgtest/testing/amd64/l/llvm-toolchain-13/15959122/log.gz Cheers -- Sebastian Ramacher signature.asc Description: PGP signature --- End Message --- --- Begin Message --- Source: llvm-toolchain-13 Source-Version: 1:13.0.0-6 Done: Sylvestre Ledru We believe that the bug you reported is fixed in the latest version of llvm-toolchain-13, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 996...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Sylvestre Ledru (supplier of updated llvm-toolchain-13 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: Fri, 15 Oct 2021 10:45:30 +0200 Source: llvm-toolchain-13 Architecture: source Version: 1:13.0.0-6 Distribution: unstable Urgency: medium Maintainer: LLVM Packaging Team Changed-By: Sylvestre Ledru Closes: 995684 996551 Changes: llvm-toolchain-13 (1:13.0.0-6) unstable; urgency=medium . * Remove omp-device-info from LLVMExports.cmake (Closes: #996551) * Fix a atomic issue. Thanks to YunQiang Su for the patch Partial fix for #995827 * Bring back the llvm manpages (Closes: #995684) Were generated at the wrong place Checksums-Sha1: 4f6a18e02970d11dc583b5dfb689787f2d3cf5ff 6732 llvm-toolchain-13_13.0.0-6.dsc a877e2db1fe0f34b9daeb75f92a0b2a406bc31f9 141736 llvm-toolchain-13_13.0.0-6.debian.tar.xz d77f8bbad65fe97264b9dc6c5db9407a9bb08241 12142 llvm-toolchain-13_13.0.0-6_source.buildinfo Checksums-Sha256: f9831840a70c0774dd30d5c9027acb5a8571034ecb50c2615be3e8ba73da2ec9 6732 llvm-toolchain-13_13.0.0-6.dsc 72b02d8031af6ddbc51c3624555ad064e023b08e2d690f7c56511d5227f106fc 141736 llvm-toolchain-13_13.0.0-6.debian.tar.xz
Processed: severity of 996487 is serious
Processing commands for cont...@bugs.debian.org: > severity 996487 serious Bug #996487 [nbd-client] nbd-client: connects to localhost instead of the requested server Severity set to 'serious' from 'important' > thanks Stopping processing here. Please contact me if you need assistance. -- 996487: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=996487 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: tagging 996487
Processing commands for cont...@bugs.debian.org: > tags 996487 + upstream fixed-upstream Bug #996487 [nbd-client] nbd-client: connects to localhost instead of the requested server Added tag(s) fixed-upstream and upstream. > thanks Stopping processing here. Please contact me if you need assistance. -- 996487: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=996487 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#996724: closing 996724
close 996724 3.0.2-5 thanks
Processed: closing 996724
Processing commands for cont...@bugs.debian.org: > close 996724 3.0.2-5 Bug #996724 [src:ruby3.0] ruby3.0: FTBFS on ppc64el: Segmentation fault Marked as fixed in versions ruby3.0/3.0.2-5. Bug #996724 [src:ruby3.0] ruby3.0: FTBFS on ppc64el: Segmentation fault Marked Bug as done > thanks Stopping processing here. Please contact me if you need assistance. -- 996724: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=996724 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: your mail
Processing commands for cont...@bugs.debian.org:
> severity 981525 grave
Bug #981525 {Done: Hubert Chathi } [nheko] nheko login
crashes client, can't be used, in urgent need of a version update
Severity set to 'grave' from 'normal'
>
End of message, stopping processing here.
Please contact me if you need assistance.
--
981525: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=981525
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#996781: luarocks: Installation fails with dpkg error
Package: luarocks Version: 3.7.0+dfsg1-1 Severity: grave Justification: renders package unusable Hi, thanks for reviving the package. Now I'm getting this when attempting to install however: Error: Cannot access repository at /root/.luarocks/lib/luarocks/rocks-5.3 dpkg: error processing package luarocks (--configure): installed luarocks package post-installation script subprocess returned error exit status 1 luarocks.postinst: mkdir -p /usr/local/lib/luarocks/rocks/ luarocks-admin make_manifest --local-tree <--- Using local-tree here is probably wrong. Regards, Oliver Versions of packages luarocks depends on: ii liblua5.3-dev 5.3.6-1 ii lua-any27 ii lua5.3 5.3.6-1 ii unzip 6.0-26 ii wget 1.21.2-2+b1 ii zip3.0-12 Versions of packages luarocks recommends: ii lua-sec 1.0.1-1 luarocks suggests no packages.
Bug#995419: [Pkg-rust-maintainers] Bug#995419: rust-utf-8: autopkgtest regression: crate directory not found: /usr/share/cargo/registry/utf-8-0.7.6
Paul, what do you think about Peter's propositoins ? thanks S Le 01/10/2021 à 00:07, peter green a écrit : >> It passes when run with only packages from testing. > > This is not entirely correct, the version of rust-utf-8 in testing > has no autopkgtests at all. So this is a case of a newly added > (by a newer version of debcargo) test failing, not a case of an > existing test regressing. > > Investigating, it seems the reason for the failure is that > the crate is installed in the wrong place. It is installed > in /usr/share/cargo/registry/utf-0.7.6/ when it should be > installed in /usr/share/cargo/registry/utf-8-0.7.6/ > > The reason it's installed in the wrong place is that > dh-cargo by default determines the crate name from the > source package name, but source package names are ambiguous > "rust-utf-8" could mean a crate called "utf" with a major > version of 8 or it could (and actually does in this case) > mean a crate called utf-8. > > dh-cargo allows a package to specify an explicit crate name > through X-Cargo-Crate in the source section of the control > file but debcargo seems to offer no way to set this other > than overriding the complete control file. There is no mention > of X-Cargo-Crate in the debcargo source and the mechanism > for adding arbitrary lines to the generated control file only > applies to binary package sections. > > This also affects rust-md-5 and rust-sha-1, though neither > of those packages are currently in testing and rust-sha-1 > has not had an upload since debcargo started doing > autopkgtests > > I see a number of possible ways of solving the issue. > > 1. Just override the whole control file > (debcargo rightly discourages this due to the maintenance > burden it creates, but OTOH this issue only affects > three crates) > 2. Add support for adding arbitrary lines to the source > section of debian/control in debcargo and use it to > manually add X-Cargo-Crate > 3. Modify dh-cargo to obtain the crate name from Cargo.toml > instead of the package name. > (would presumablly mean dragging in a perl toml parser > which may not be desirable) > 4. Modify debcargo to generate X-Cargo-Crate lines in > cases where dh-cargo would otherwise get the wrong > crate name. > 5. Modify debcargo to generate X-Cargo-Crate lines > unconditionally > > ___ > Pkg-rust-maintainers mailing list > pkg-rust-maintain...@alioth-lists.debian.net > https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-rust-maintainers >
Bug#996780: gnome-boxes: Systematic system freeze few seconds after launching a Windows WM
Package: gnome-boxes Version: 41.1-1 Severity: critical Justification: breaks the whole system X-Debbugs-Cc: isingasimples...@gmail.com i use gnome-boxes to run a simple windows 10 session since a few months. i updated my system from stable to testing last week, and now my system freeze each time i run that windows 10 session. forcing me to force restart the whole system. -- System Information: Debian Release: bookworm/sid APT prefers testing APT policy: (900, 'testing'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.14.0-2-amd64 (SMP w/8 CPU threads) Locale: LANG=fr_CA.UTF-8, LC_CTYPE=fr_CA.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages gnome-boxes depends on: ii dconf-gsettings-backend [gsettings-backend] 0.40.0-2 ii genisoimage 9:1.1.11-3.2 ii libarchive13 3.4.3-2+b1 ii libc62.32-4 ii libcairo21.16.0-5 ii libgdk-pixbuf-2.0-0 2.42.6+dfsg-2 ii libglib2.0-0 2.70.0-1+b1 ii libgtk-3-0 3.24.30-3 ii libgtk-vnc-2.0-0 1.0.0-1+b1 ii libgtksourceview-4-0 4.8.2-1 ii libgudev-1.0-0 237-2 ii libgvnc-1.0-01.0.0-1+b1 ii libhandy-1-0 1.4.0-1 ii libosinfo-1.0-0 1.8.0-1 ii libosinfo-bin1.8.0-1 ii libpango-1.0-0 1.48.10+ds1-1 ii libsecret-1-00.20.4-2 ii libsoup2.4-1 2.74.0-2 ii libspice-client-glib-2.0-8 0.39-3 ii libspice-client-gtk-3.0-50.39-3 ii libtracker-sparql-3.0-0 3.1.2-3 ii libusb-1.0-0 2:1.0.24-3 ii libvirt-daemon 7.6.0-1 ii libvirt-glib-1.0-0 4.0.0-2 ii libwebkit2gtk-4.0-37 2.34.0-1 ii libxml2 2.9.12+dfsg-5 ii tracker 3.1.2-3 Versions of packages gnome-boxes recommends: ii qemu-system-x86 1:6.1+dfsg-6 Versions of packages gnome-boxes suggests: pn gnome-connections -- no debconf information
Processed: severity of 996778 is grave
Processing commands for cont...@bugs.debian.org: > severity 996778 grave Bug #996778 [xymon-client] xymon-client: disable logfetch's ability to execute arbitrary code Severity set to 'grave' from 'critical' > thanks Stopping processing here. Please contact me if you need assistance. -- 996778: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=996778 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#996778: xymon-client: disable logfetch's ability to execute arbitrary code
Package: xymon-client Severity: critical Tags: patch security Justification: root security hole X-Debbugs-Cc: zech...@vrvis.at, Debian Security Team The default for logfetch's options (found in /etc/xymon/xymonclient.cfg) is: LOGFETCHOPTS="" which enables it to execute arbitrary code [1]. This can and should be prevented by default by using LOGFETCHOPTS="--noexec" instead. Best regards Christoph Zechner patch: --- xymonclient.cfg.DISt +++ xymonclient.cfg.PATCHED @@ -18,7 +18,7 @@ include /var/run/xymon/xymonclient-include.cfg # Options to logfetch, the xymon binary which examines log files for recent changes. -LOGFETCHOPTS="" +LOGFETCHOPTS="--noexec" # Local Mode (Only) Options [1] https://manpages.debian.org/bullseye/xymon-client/logfetch.1.en.html -- System Information: Debian Release: 11.1 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 'stable'), (500, 'oldstable') Architecture: amd64 (x86_64) Kernel: Linux 5.10.0-9-amd64 (SMP w/8 CPU threads) Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=locale: Cannot set LC_ALL to default locale: No such file or directory 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 xymon-client depends on: ii adduser3.118 ii debconf [debconf-2.0] 1.5.77 ii init-system-helpers1.60 ii libc6 2.31-13+deb11u2 ii libssl1.1 1.1.1k-1+deb11u1 ii lsb-base 11.1.0 ii net-tools 1.60+git20181103.0eebece-1 ii procps 2:3.3.17-5 xymon-client recommends no packages. Versions of packages xymon-client suggests: pn xymon-plugins | hobbit-plugins --- xymonclient.cfg.DISt +++ xymonclient.cfg.PATCHED @@ -18,7 +18,7 @@ include /var/run/xymon/xymonclient-include.cfg # Options to logfetch, the xymon binary which examines log files for recent changes. -LOGFETCHOPTS="" +LOGFETCHOPTS="--noexec" # Local Mode (Only) Options
Bug#996060: marked as done (gnome-shell-extension-hamster: does not declare compatibility with GNOME Shell 41)
Your message dated Mon, 18 Oct 2021 13:48:33 + with message-id and subject line Bug#996060: fixed in gnome-shell-extension-hamster 0.10.0+git20210628-2 has caused the Debian Bug report #996060, regarding gnome-shell-extension-hamster: does not declare compatibility with GNOME Shell 41 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.) -- 996060: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=996060 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: gnome-shell-extension-hamster Version: 0.10.0+git20210628-1 Severity: normal Tags: bookworm sid User: pkg-gnome-maintain...@lists.alioth.debian.org Usertags: gnome-shell-41 The metadata.json for this extension doesn't declare compatibility with GNOME 41. I don't know whether the actual code will need changes or not: the conservative assumption is that it probably will (so please test). gnome-shell 41 should be available in experimental soon. In versions of GNOME Shell up to 3.38, metadata.json didn't matter much, because validation of extensions' metadata against the installed Shell version was disabled by default; but since GNOME 40 the default has changed back to enabling the version check by default, in an effort to avoid issues caused by outdated extensions remaining enabled. As a result, GNOME Shell extensions in bookworm should probably have a dependency like: Depends: gnome-shell (>= x), gnome-shell (<< y~) where x and y are set according to metadata.json. gnome-shell-extension-caffeine is a good example of this technique. When we do the GNOME Shell 41 transition, hopefully soon, we will have to either update this extension or remove it from testing. It would be useful to get a fixed version into experimental. Thanks, smcv --- End Message --- --- Begin Message --- Source: gnome-shell-extension-hamster Source-Version: 0.10.0+git20210628-2 Done: Raphaël Hertzog We believe that the bug you reported is fixed in the latest version of gnome-shell-extension-hamster, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 996...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Raphaël Hertzog (supplier of updated gnome-shell-extension-hamster package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Mon, 18 Oct 2021 15:15:36 +0200 Source: gnome-shell-extension-hamster Architecture: source Version: 0.10.0+git20210628-2 Distribution: unstable Urgency: medium Maintainer: Project Hamster Team Changed-By: Raphaël Hertzog Closes: 996060 Changes: gnome-shell-extension-hamster (0.10.0+git20210628-2) unstable; urgency=medium . * Document compatibility with GNOME Shell 41. Tighten the gnome-shell dependency to not allow usage with gnome-shell 42. (Closes: #996060) Checksums-Sha1: 103fb6477cc84097e8e75de5c29d92154c79f548 2022 gnome-shell-extension-hamster_0.10.0+git20210628-2.dsc e6a6969025d0f76b6df977e84c90fd4803e84310 2452 gnome-shell-extension-hamster_0.10.0+git20210628-2.debian.tar.xz 5d150f4f7c00114ef5a786d8542358d95bdce357 7783 gnome-shell-extension-hamster_0.10.0+git20210628-2_source.buildinfo Checksums-Sha256: 6528a7dd3ddf21b167e4f8affa3d5895f843c20034ae750f6e0549160e100433 2022 gnome-shell-extension-hamster_0.10.0+git20210628-2.dsc dfa1af9d4fde2fdec81d65c2250af18e7acacfef21f197230a32fb0d5cc4eb82 2452 gnome-shell-extension-hamster_0.10.0+git20210628-2.debian.tar.xz 4eb710b5483c6bfd8798d6a39d97a4ea85bc159f26484edd4dddf9cf41c9aff6 7783 gnome-shell-extension-hamster_0.10.0+git20210628-2_source.buildinfo Files: 95459e01c53fd1f84ac73afdf5603af1 2022 gnome optional gnome-shell-extension-hamster_0.10.0+git20210628-2.dsc 50dcc9fc7b874b187fe7b67a415661f5 2452 gnome optional gnome-shell-extension-hamster_0.10.0+git20210628-2.debian.tar.xz 62041b2dfc9544f23a8d9b4d44b1478d 7783 gnome optional gnome-shell-extension-hamster_0.10.0+git20210628-2_source.buildinfo -BEGIN PGP SIGNATURE- Comment: Signed by Raphael Hertzog iQEzBAEBCgAdFiEE1823g1EQnhJ1LsbSA4gdq+vCmrkFAmFtdzAACgkQA4gdq+vC mrkinggAgU7EBMOfxEYl7qpopV0KYfNZc76CMaTkaO8tioEsmtTB2zmumMPRZNs4 l/tSvVyaV6a8xSpdqnMUpnOiy4xZPB+86D9YKScgjcTMMV7eSkoSBdh9CuXPr9lO
Bug#995445: logidee-tools: creates incorrect TeX code, breaks other packages via autopkgtests
Hi Raphael, > Sorry that logidee-tools created issues for you. For the record, I have Not really issues, therion took longer to get fixed ;-) And it was quite interesting to find out what was the real problem. > just requested the removal of that package since I'm no longer using > it and in fact nobody else is using it either. Then it is definitely a good idea to let this package go away. Thanks a lot for letting us know, and all the best Norbert -- PREINING Norbert https://www.preining.info Fujitsu Research + IFMGA Guide + TU Wien + TeX Live + Debian Dev GPG: 0x860CDC13 fp: F7D8 A928 26E3 16A1 9FA0 ACF0 6CAC A448 860C DC13
Bug#995445: logidee-tools: creates incorrect TeX code, breaks other packages via autopkgtests
Hello, On Fri, 01 Oct 2021, Norbert Preining wrote: > The failed autopkgtest can be boiled down to the following example (all > the code is as taken from the logidee-tools generated code): Sorry that logidee-tools created issues for you. For the record, I have just requested the removal of that package since I'm no longer using it and in fact nobody else is using it either. RM bug: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=996776 Hopefully the package will be removed soon. Cheers, -- ⢀⣴⠾⠻⢶⣦⠀ Raphaël Hertzog ⣾⠁⢠⠒⠀⣿⡁ ⢿⡄⠘⠷⠚⠋The Debian Handbook: https://debian-handbook.info/get/ ⠈⠳⣄ Debian Long Term Support: https://deb.li/LTS
Bug#996060: marked as pending in gnome-shell-extension-hamster
Control: tag -1 pending Hello, Bug #996060 in gnome-shell-extension-hamster reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/projecthamster-team/gnome-shell-extension-hamster/-/commit/b5ac06729a7eb15f3afaddf354741a678cf93fb4 Document compatibility with GNOME Shell 41 Tighten the gnome-shell dependency to not allow usage with gnome-shell 42. Gbp-Dch: Full Closes: #996060 (this message was generated automatically) -- Greetings https://bugs.debian.org/996060
Processed: Bug#996060 marked as pending in gnome-shell-extension-hamster
Processing control commands: > tag -1 pending Bug #996060 [gnome-shell-extension-hamster] gnome-shell-extension-hamster: does not declare compatibility with GNOME Shell 41 Added tag(s) pending. -- 996060: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=996060 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Re: Bug#996764: FTBFS: test misc/swaplabel failure
Processing control commands: > found -1 2.37.2-1 Bug #996764 [util-linux] FTBFS: test misc/swaplabel failure Marked as found in versions util-linux/2.37.2-1. -- 996764: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=996764 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#996764: FTBFS: test misc/swaplabel failure
Control: found -1 2.37.2-1 Hello Mark, * Mark Hindley [211018 12:33]: [..] > Whilst building a local version of util-linux 2.37.2-3, the misc/swaplabel > test > failed. > > I believe this is caused by the change in behaviour of mkswap, which now > complains on stderr if the provided image contains holes. My build environment > is pbuilder/cowbuilder chroot with /var/cache/pbuilder mounted as > ext3. [..] > I have worked around it with the attached patch which invokes fallocate() with > the -x flag. Although, I suppose fallocate could be dispensed with and > truncate > always used instead. Right, thanks for the patch. Could you add your Signed-off-by: to the patch, so I can forward it upstream? (Or you could send it to util-li...@vger.kernel.org directly, too.) Best wishes, Chris
Bug#996048: postfix-mta-sts-resolver: autopkgtest doesn't handle new version of ca-certificates nicely: rehash: warning: skipping ca-certificates.crt,it does not contain exactly one certificate or CRL
Hi, I think the following change might be the relevant one: --- a/update-ca-certificates +++ b/update-ca-certificates @@ -164,8 +164,6 @@ done fi -rm -f "$CERTBUNDLE" - ADDED_CNT=$(wc -l < "$ADDED") REMOVED_CNT=$(wc -l < "$REMOVED") It triggers this stderr output during openssl rehash (l. 184): rehash: warning: skipping ca-certificates.crt,it does not contain exactly one certificate or CRL I'm happy to change the upstream integration test to adopt to that, or else it would also make sense to me that update-ca-certificates not output to stderr under normal operation. Perhaps it might even make sense to suppress this particular message entirely? Kind regards, Benjamin
Bug#984145: marked as done (gatb-core: ftbfs with GCC-11)
Your message dated Mon, 18 Oct 2021 12:33:41 + with message-id and subject line Bug#984145: fixed in gatb-core 1.4.2+dfsg-7 has caused the Debian Bug report #984145, regarding gatb-core: ftbfs with GCC-11 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 984145: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=984145 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:gatb-core Version: 1.4.2+dfsg-6 Severity: normal Tags: sid bookworm User: debian-...@lists.debian.org Usertags: ftbfs-gcc-11 [This bug is not targeted to the upcoming bullseye release] Please keep this issue open in the bug tracker for the package it was filed for. If a fix in another package is required, please file a bug for the other package (or clone), and add a block in this package. Please keep the issue open until the package can be built in a follow-up test rebuild. The package fails to build in a test rebuild on at least amd64 with gcc-11/g++-11, but succeeds to build with gcc-10/g++-10. The severity of this report will be raised before the bookworm release, so nothing has to be done for the bullseye release. The full build log can be found at: http://people.debian.org/~doko/logs/20210228/filtered/gcc11/gatb-core_1.4.2+dfsg-6_unstable_gcc11.log The last lines of the build log are at the end of this report. To build with GCC 11, either set CC=gcc-11 CXX=g++-11 explicitly, or install the gcc, g++, gfortran, ... packages from experimental. apt-get -t=experimental install g++ Common build failures are new warnings resulting in build failures with -Werror turned on, or new/dropped symbols in Debian symbols files. For other C/C++ related build failures see the porting guide at http://gcc.gnu.org/gcc-11/porting_to.html GCC 11 defaults to the GNU++17 standard. If your package installs header files in /usr/include, please don't work around C++17 issues by choosing a lower C++ standard for the package build, but fix these issues to build with the C++17 standard. [...] _ZSt16__insertion_sortIN9__gnu_cxx17__normal_iteratorIPN4gatb4core8debruijn4impl11kmerIndiceTILm64EEESt6vectorIS7_SaIS7_NS0_5__ops15_Iter_comp_iterINS5_10comparatorILm64EEvT_SI_T0_@Base 1.4.2 _ZSt16__insertion_sortIN9__gnu_cxx17__normal_iteratorIPN4gatb4core8debruijn4impl11kmerIndiceTILm96EEESt6vectorIS7_SaIS7_NS0_5__ops15_Iter_comp_iterINS5_10comparatorILm96EEvT_SI_T0_@Base 1.4.2 @@ -9397,13 +9488,13 @@ _ZSt22__final_insertion_sortIPN4gatb4core5tools11collections4impl6Hash16INS2_4math8LargeIntILi2EEEiE4cellEN9__gnu_cxx5__ops15_Iter_comp_iterIPFbRKSA_SG_vT_SK_T0_@Base 1.4.2 _ZSt22__final_insertion_sortIPN4gatb4core5tools11collections4impl6Hash16INS2_4math8LargeIntILi3EEEiE4cellEN9__gnu_cxx5__ops15_Iter_comp_iterIPFbRKSA_SG_vT_SK_T0_@Base 1.4.2 _ZSt22__final_insertion_sortIPN4gatb4core5tools11collections4impl6Hash16INS2_4math8LargeIntILi4EEEiE4cellEN9__gnu_cxx5__ops15_Iter_comp_iterIPFbRKSA_SG_vT_SK_T0_@Base 1.4.2 - _ZSt22__move_median_to_firstIN9__gnu_cxx17__normal_iteratorIPN4gatb4core8debruijn4impl11kmerIndiceTILm128EEESt6vectorIS7_SaIS7_NS0_5__ops15_Iter_comp_iterINS5_10comparatorILm128EEvT_SI_SI_SI_T0_@Base 1.4.2 - _ZSt22__move_median_to_firstIN9__gnu_cxx17__normal_iteratorIPN4gatb4core8debruijn4impl11kmerIndiceTILm64EEESt6vectorIS7_SaIS7_NS0_5__ops15_Iter_comp_iterINS5_10comparatorILm64EEvT_SI_SI_SI_T0_@Base 1.4.2 - _ZSt22__move_median_to_firstIN9__gnu_cxx17__normal_iteratorIPN4gatb4core8debruijn4impl11kmerIndiceTILm96EEESt6vectorIS7_SaIS7_NS0_5__ops15_Iter_comp_iterINS5_10comparatorILm96EEvT_SI_SI_SI_T0_@Base 1.4.2 - _ZSt22__move_median_to_firstIN9__gnu_cxx17__normal_iteratorIPSt4pairIS2_ImmEmESt6vectorIS4_SaIS4_NS0_5__ops15_Iter_comp_iterIPFbRKS4_SD_vT_SH_SH_SH_T0_@Base 1.4.2 - _ZSt22__move_median_to_firstIN9__gnu_cxx17__normal_iteratorIPmSt6vectorImSaImNS0_5__ops15_Iter_comp_iterIN4gatb4core4kmer4impl11SortCommandILm128EE3CmpvT_SH_SH_SH_T0_@Base 1.4.2 - _ZSt22__move_median_to_firstIN9__gnu_cxx17__normal_iteratorIPmSt6vectorImSaImNS0_5__ops15_Iter_comp_iterIN4gatb4core4kmer4impl11SortCommandILm64EE3CmpvT_SH_SH_SH_T0_@Base 1.4.2 - _ZSt22__move_median_to_firstIN9__gnu_cxx17__normal_iteratorIPmSt6vectorImSaImNS0_5__ops15_Iter_comp_iterIN4gatb4core4kmer4impl11SortCommandILm96EE3CmpvT_SH_SH_SH_T0_@Base 1.4.2 +#MISSING: 1.4.2+dfsg-6#
Bug#984196: marked as done (libopendbx: ftbfs with GCC-11)
Your message dated Mon, 18 Oct 2021 12:18:39 + with message-id and subject line Bug#984196: fixed in libopendbx 1.4.6-16 has caused the Debian Bug report #984196, regarding libopendbx: ftbfs with GCC-11 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 984196: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=984196 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:libopendbx Version: 1.4.6-15 Severity: normal Tags: sid bookworm User: debian-...@lists.debian.org Usertags: ftbfs-gcc-11 [This bug is not targeted to the upcoming bullseye release] Please keep this issue open in the bug tracker for the package it was filed for. If a fix in another package is required, please file a bug for the other package (or clone), and add a block in this package. Please keep the issue open until the package can be built in a follow-up test rebuild. The package fails to build in a test rebuild on at least amd64 with gcc-11/g++-11, but succeeds to build with gcc-10/g++-10. The severity of this report will be raised before the bookworm release, so nothing has to be done for the bullseye release. The full build log can be found at: http://people.debian.org/~doko/logs/20210228/filtered/gcc11/libopendbx_1.4.6-15_unstable_gcc11.log The last lines of the build log are at the end of this report. To build with GCC 11, either set CC=gcc-11 CXX=g++-11 explicitly, or install the gcc, g++, gfortran, ... packages from experimental. apt-get -t=experimental install g++ Common build failures are new warnings resulting in build failures with -Werror turned on, or new/dropped symbols in Debian symbols files. For other C/C++ related build failures see the porting guide at http://gcc.gnu.org/gcc-11/porting_to.html GCC 11 defaults to the GNU++17 standard. If your package installs header files in /usr/include, please don't work around C++17 issues by choosing a lower C++ standard for the package build, but fix these issues to build with the C++17 standard. [...] 193 | unsigned long Result_Impl::columnPos( const string& name ) throw( std::exception ) |^ odbx_impl.cpp:216:67: error: ISO C++17 does not allow dynamic exception specifications 216 | const string Result_Impl::columnName( unsigned long pos ) throw( std::exception ) | ^ odbx_impl.cpp:233:63: error: ISO C++17 does not allow dynamic exception specifications 233 | odbxtype Result_Impl::columnType( unsigned long pos ) throw( std::exception ) | ^ odbx_impl.cpp:245:69: error: ISO C++17 does not allow dynamic exception specifications 245 | unsigned long Result_Impl::fieldLength( unsigned long pos ) throw( std::exception ) | ^ odbx_impl.cpp:257:66: error: ISO C++17 does not allow dynamic exception specifications 257 | const char* Result_Impl::fieldValue( unsigned long pos ) throw( std::exception ) | ^ odbx_impl.cpp:268:61: error: ISO C++17 does not allow dynamic exception specifications 268 | Lob_Iface* Result_Impl::getLob( const char* value ) throw( std::exception ) | ^ odbx_impl.cpp:283:48: error: ISO C++17 does not allow dynamic exception specifications 283 | Stmt_Impl::Stmt_Impl( odbx_t* handle ) throw( std::exception ) |^ odbx_impl.cpp:304:79: error: ISO C++17 does not allow dynamic exception specifications 304 | StmtSimple_Impl::StmtSimple_Impl( odbx_t* handle, const string& sql ) throw( std::exception ) : Stmt_Impl( handle ) | ^ odbx_impl.cpp:329:44: error: ISO C++17 does not allow dynamic exception specifications 329 | StmtSimple_Impl::StmtSimple_Impl() throw( std::exception ) : Stmt_Impl( NULL ) |^ odbx_impl.cpp:368:50: error: ISO C++17 does not allow dynamic exception specifications 368 | Result_Iface* StmtSimple_Impl::execute() throw( std::exception ) | ^ odbx_impl.cpp:380:55: error: ISO C++17 does not allow dynamic exception
Bug#996724: ruby3.0: FTBFS on ppc64el: Segmentation fault
On 10/18/21 13:16, Antonio Terceiro wrote:
> I don't think we are on the right track here. I need to read the failing
> test correctly. this "test case" alone is bogus, as
>
> ruby -e 'END {Process.kill :SEGV, $$}'
>
> is _expected_ to segfault, i.e. the process is sending a SEGV signal to
> itself. This test case is not complete.
It might be an idea to look at the Fedora package:
> https://src.fedoraproject.org/rpms/ruby/blob/rawhide/f/ruby.spec
It has a number of patches against 3.x:
> https://src.fedoraproject.org/rpms/ruby/tree/rawhide
It builds fine on ppc64el:
> https://koji.fedoraproject.org/koji/buildinfo?buildID=1801321
OTOH, ruby3.0 builds fine in openSUSE Factory on ppc64el, but they're still at
version 3.0.1, so it might be an issue that will only show with 3.0.2?
> https://build.opensuse.org/package/show/openSUSE:Factory:PowerPC/ruby3.0
Adrian
--
.''`. John Paul Adrian Glaubitz
: :' : Debian Developer - glaub...@debian.org
`. `' Freie Universitaet Berlin - glaub...@physik.fu-berlin.de
`-GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913
Bug#996724: ruby3.0: FTBFS on ppc64el: Segmentation fault
On Mon, Oct 18, 2021 at 12:59:35PM +0200, John Paul Adrian Glaubitz wrote:
> On 10/18/21 12:51, Antonio Terceiro wrote:
> >> So, we need a backtrace to see where the crash actually happens. I assume
> >> it's in one
> >> of the build dependencies.
> >
> > it happens in glibc:
> >
> > Program received signal SIGSEGV, Segmentation fault.
> > 0x77a48f04 in kill () from /lib/powerpc64le-linux-gnu/libc.so.6
>
> Hmm, both were built with glibc 2.32-4.
I don't think we are on the right track here. I need to read the failing
test correctly. this "test case" alone is bogus, as
ruby -e 'END {Process.kill :SEGV, $$}'
is _expected_ to segfault, i.e. the process is sending a SEGV signal to
itself. This test case is not complete.
signature.asc
Description: PGP signature
Bug#996437: elixir-lang: FTBFS with Erlang 24.1 (one test fails)
Hello Sergei Thank you for the patch you prepared. It's well done. Feel free to do a NMU. -- Evgeny
Bug#996724: ruby3.0: FTBFS on ppc64el: Segmentation fault
On 10/18/21 12:51, Antonio Terceiro wrote: >> So, we need a backtrace to see where the crash actually happens. I assume >> it's in one >> of the build dependencies. > > it happens in glibc: > > Program received signal SIGSEGV, Segmentation fault. > 0x77a48f04 in kill () from /lib/powerpc64le-linux-gnu/libc.so.6 Hmm, both were built with glibc 2.32-4. Adrian -- .''`. John Paul Adrian Glaubitz : :' : Debian Developer - glaub...@debian.org `. `' Freie Universitaet Berlin - glaub...@physik.fu-berlin.de `-GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913
Bug#996724: ruby3.0: FTBFS on ppc64el: Segmentation fault
On Mon, Oct 18, 2021 at 10:00:42AM +0200, John Paul Adrian Glaubitz wrote: > Hello! > > On 10/17/21 21:50, John Paul Adrian Glaubitz wrote: > > Ah, so the last successful build was 3.0.2-2 and the first failure was in > > 3.0.2-3, > > the only difference being the mipsel patch to fix an unaligned access. > > > > However, 3.0.2-2 was built with gcc-10: > > > >> https://buildd.debian.org/status/fetch.php?pkg=ruby3.0=ppc64el=3.0.2-2=1633362713=0 > > > > while 3.0.2-3 was built with gcc-11: > > > >> https://buildd.debian.org/status/fetch.php?pkg=ruby3.0=ppc64el=3.0.2-3=1634169532=0 > > > > So, first we should try building with gcc-10 and see if that makes a > > difference. > > I have tested the build with gcc-10 but the problem remains, so it's not a > compiler > issue. Dropping the patch rand_init-fix-off-by-one-error.patch that was > introduced > with 3.0.2-3 doesn't help either. > > So, we need a backtrace to see where the crash actually happens. I assume > it's in one > of the build dependencies. it happens in glibc: Program received signal SIGSEGV, Segmentation fault. 0x77a48f04 in kill () from /lib/powerpc64le-linux-gnu/libc.so.6 #0 0x77a48f04 in kill () from /lib/powerpc64le-linux-gnu/libc.so.6 #1 0x00010023a8ec in rb_f_kill (argc=, argv=) at signal.c:481 #2 0x0001001d0608 in proc_rb_f_kill (c=, v=, _=) at process.c:8605 #3 0x0001002bd848 in ractor_safe_call_cfunc_m1 (recv=, argc=, argv=, func=) at vm_insnhelper.c:2736 #4 0x0001002d2e6c in vm_call_cfunc_with_frame (ec=0x100453ad0, reg_cfp=0x779effa0, calling=) at vm_insnhelper.c:2926 #5 0x0001002d5bb4 in vm_sendish (ec=0x100453ad0, reg_cfp=0x779effa0, cd=0x1005a0960, block_handler=, method_explorer=) at vm_callinfo.h:336 #6 0x0001002da06c in vm_exec_core (ec=0x100453ad0, initial=, initial@entry=0) at insns.def:789 #7 0x0001002dfcb0 in rb_vm_exec (ec=0x100453ad0, mjit_enable_p=) at vm.c:2172 #8 0x0001002e5d7c in invoke_block (captured=, captured=, opt_pc=, type=, cref=0x0, self=4300276880, iseq=0x10046a478, ec=0x100453ad0) at vm.c:1263 #9 invoke_iseq_block_from_c (me=0x0, is_lambda=0, cref=0x0, passed_block_handler=0, kw_splat=0, argv=0x10046a280, argc=0, self=4300276880, captured=, ec=0x100453ad0) at vm.c:1335 #10 invoke_block_from_c_proc (me=0x0, is_lambda=, passed_block_handler=0, kw_splat=0, argv=0x10046a280, argc=0, self=4300276880, proc=, ec=0x100453ad0) at vm.c:1435 #11 vm_invoke_proc (ec=0x100453ad0, proc=, self=4300276880, argc=, argv=0x10046a280, kw_splat=, passed_block_handler=0) at vm.c:1464 #12 0x0001001c8ffc in rb_proc_call (self=, args=) at proc.c:986 #13 0x0001000c9cb0 in rb_call_end_proc (data=4299596440) at eval_jump.c:13 #14 0x0001000c9d64 in exec_end_procs_chain (procs=procs@entry=0x10043a750 , errp=errp@entry=0x100453b48) at eval_jump.c:105 #15 0x0001000cf9fc in rb_ec_exec_end_proc (ec=ec@entry=0x100453ad0) at eval_jump.c:120 #16 0x0001000cfd84 in rb_ec_teardown (ec=ec@entry=0x100453ad0) at eval.c:175 #17 0x0001000d0068 in rb_ec_cleanup (ec=ec@entry=0x100453ad0, ex=) at eval.c:243 #18 0x0001000d0598 in ruby_run_node (n=0x10046a5b8) at eval.c:375 #19 0x00010002aaa8 in main (argc=, argv=) at ./main.c:50 signature.asc Description: PGP signature
Processed: (No Subject)
Processing commands for cont...@bugs.debian.org: > fixed 996571 lutris/0.5.9.1-1 Bug #996571 [lutris] lutris: since the latest update lutris creates a lutris.log file in $HOME Marked as fixed in versions lutris/0.5.9.1-1. > forwarded 996553 https://github.com/jrmadsen/PTL/issues/16 Bug #996553 [src:ptl] ptl: autopkgtest failure on armhf Set Bug forwarded-to-address to 'https://github.com/jrmadsen/PTL/issues/16'. > thanks Stopping processing here. Please contact me if you need assistance. -- 996553: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=996553 996571: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=996571 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#996764: FTBFS: test misc/swaplabel failure
Package: util-linux
Version: 2.37.2-3
Severity: serious
Tags: patch ftbfs
Justification: fails to build from source (but built successfully in the past)
Chris,
Whilst building a local version of util-linux 2.37.2-3, the misc/swaplabel test
failed.
I believe this is caused by the change in behaviour of mkswap, which now
complains on stderr if the provided image contains holes. My build environment
is pbuilder/cowbuilder chroot with /var/cache/pbuilder mounted as
ext3. Apparently the call to fallocate() in tests/ts/misc/swaplabel allocates a
file with holes that mkswap then complains about. The additional, unexpected
text in /build/util-linux-2.37.2/tests/output/misc/swaplabel.err is:
mkswap: contains holes or other unsupported extents.
This swap file can be rejected by kernel on swap activation!
Use --verbose for more details.
which directly causes the failure.
I have worked around it with the attached patch which invokes fallocate() with
the -x flag. Although, I suppose fallocate could be dispensed with and truncate
always used instead.
Best wishes
Mark
-- System Information:
Debian Release: 10.0
Architecture: amd64 (x86_64)
Kernel: Linux 4.19.0-17-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8),
LANGUAGE=en_GB:en (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)
Versions of packages util-linux depends on:
ii fdisk 2.33.1-0.1+devuan1~beowulf2
ii libaudit1 1:2.8.4-3
ii libblkid1 2.33.1-0.1+devuan1~beowulf2
ii libc6 2.28-10
ii libcap-ng0 0.7.9-2
ii libeudev1 3.2.9-9~beowulf1
ii libmount1 2.33.1-0.1+devuan1~beowulf2
ii libpam0g 1.3.1-5
ii libselinux12.8-1+b1
ii libsmartcols1 2.33.1-0.1+devuan1~beowulf2
ii libtinfo6 6.1+20181013-2+deb10u2
ii libuuid1 2.33.1-0.1+devuan1~beowulf2
ii login 1:4.5-1.1
ii zlib1g 1:1.2.11.dfsg-1
util-linux recommends no packages.
Versions of packages util-linux suggests:
ii dosfstools 4.1-2
ii kbd 2.0.4-4
ii util-linux-locales 2.33.1-0.1+devuan1~beowulf2
-- no debconf information
>From 03a585290d86b74d4861e11569c426362c8b853c Mon Sep 17 00:00:00 2001
From: Mark Hindley
Date: Sun, 17 Oct 2021 20:25:47 +0100
Subject: [PATCH 1/1] Fix test/misc/swaplabel failure due to change in mkswap
behaviour.
mkswap now warns if the image file has holes. If fallocate is used to create the
file, use POSIX semantics to ensure the file has no holes.
This fixes the test failure
misc: swaplabel ... FAILED (misc/swaplabel)
= script: /build/util-linux-2.37.2/tests/ts/misc/swaplabel
=
= OUTPUT =
1 Setting up swapspace version 1, size = 9 pages (9xPGSZ bytes)
2 LABEL=1234567890abcde, UUID=12345678-abcd-abcd-abcd-1234567890ab
3 LABEL: 1234567890abcde
4 UUID: 12345678-abcd-abcd-abcd-1234567890ab
= EXPECTED ===
1 Setting up swapspace version 1, size = 9 pages (9xPGSZ bytes)
2 LABEL=1234567890abcde, UUID=12345678-abcd-abcd-abcd-1234567890ab
3 LABEL: 1234567890abcde
4 UUID: 12345678-abcd-abcd-abcd-1234567890ab
= O/E diff ===
==
The additional error appears in swaplabel.err:
mkswap: contains holes or other unsupported extents.
This swap file can be rejected by kernel on swap activation!
Use --verbose for more details.
diff --git a/tests/ts/misc/swaplabel b/tests/ts/misc/swaplabel
index 0801cb213..8b1abb5c3 100755
--- a/tests/ts/misc/swaplabel
+++ b/tests/ts/misc/swaplabel
@@ -25,7 +25,7 @@ ts_check_test_command "$TS_HELPER_SYSINFO"
# fallocate does not work on most file systems
function fallocate_or_skip()
{
- $TS_CMD_FALLOCATE -l $1 $2 2>/dev/null || \
+ $TS_CMD_FALLOCATE -x -l $1 $2 2>/dev/null || \
truncate -s $1 $2 || \
ts_skip "no way to create test image"
}
--
2.20.1
Bug#996761: kwin-x11: KWin crashes and doesn't start
Package: kwin-x11 Version: 4:5.21.5-2 Severity: grave Justification: renders package unusable X-Debbugs-Cc: isop...@gmail.com Dear Maintainer, This morning just after applying latest package updates my KDE environment failed to start due to Kwin crash. This morning updates included a new version of nvidia propetary driver (I'm using a RTX 3080 card). I removed all .config and results are the same. For your information, this is bug tracing I found in .xsession-errors file KCrash: crashing... crashRecursionCounter = 2 KCrash: Application Name = kwin_x11 path = /usr/bin pid = 6746 KCrash: Arguments: /usr/bin/kwin_x11 --crashes 1 KCrash: Attempting to start /usr/lib/x86_64-linux-gnu/libexec/drkonqi kwin_xkbcommon: XKB: /usr/share/X11/locale/en_US.UTF-8/Compose:5089:46: this compose sequence is a duplicate of another; skipping line kwin_xkbcommon: XKB: /usr/share/X11/locale/en_US.UTF-8/Compose:5091:48: this compose sequence is a duplicate of another; skipping line kwin_xkbcommon: XKB: /usr/share/X11/locale/en_US.UTF-8/Compose:5093:48: this compose sequence is a duplicate of another; skipping line kwin_xkbcommon: XKB: /usr/share/X11/locale/en_US.UTF-8/Compose:5097:47: this compose sequence is a duplicate of another; skipping line kwin_xkbcommon: XKB: /usr/share/X11/locale/en_US.UTF-8/Compose:5099:46: this compose sequence is a duplicate of another; skipping line kwin_xkbcommon: XKB: /usr/share/X11/locale/en_US.UTF-8/Compose:5107:48: this compose sequence is a duplicate of another; skipping line kwin_xkbcommon: XKB: /usr/share/X11/locale/en_US.UTF-8/Compose:5111:46: this compose sequence is a duplicate of another; skipping line kwin_xkbcommon: XKB: /usr/share/X11/locale/en_US.UTF-8/Compose:5113:46: this compose sequence is a duplicate of another; skipping line kwin_xkbcommon: XKB: /usr/share/X11/locale/en_US.UTF-8/Compose:5117:45: this compose sequence is a duplicate of another; skipping line kwin_xkbcommon: XKB: /usr/share/X11/locale/en_US.UTF-8/Compose:5120:46: this compose sequence is a duplicate of another; skipping line kwin_xkbcommon: XKB: inet:232:58: unrecognized keysym "XF86BrightnessAuto" kwin_xkbcommon: XKB: inet:233:58: unrecognized keysym "XF86DisplayOff" kwin_xkbcommon: XKB: inet:237:58: unrecognized keysym "XF86Info" kwin_xkbcommon: XKB: inet:240:58: unrecognized keysym "XF86AspectRatio" kwin_xkbcommon: XKB: inet:241:58: unrecognized keysym "XF86DVD" kwin_xkbcommon: XKB: inet:242:58: unrecognized keysym "XF86Audio" kwin_xkbcommon: XKB: inet:245:58: unrecognized keysym "XF86ChannelUp" kwin_xkbcommon: XKB: inet:246:58: unrecognized keysym "XF86ChannelDown" kwin_xkbcommon: XKB: inet:248:58: unrecognized keysym "XF86Break" kwin_xkbcommon: XKB: inet:249:58: unrecognized keysym "XF86VideoPhone" kwin_xkbcommon: XKB: inet:253:58: unrecognized keysym "XF86ZoomReset" kwin_xkbcommon: XKB: inet:255:58: unrecognized keysym "XF86Editor" kwin_xkbcommon: XKB: inet:257:58: unrecognized keysym "XF86GraphicsEditor" kwin_xkbcommon: XKB: inet:258:58: unrecognized keysym "XF86Presentation" kwin_xkbcommon: XKB: inet:259:58: unrecognized keysym "XF86Database" kwin_xkbcommon: XKB: inet:261:58: unrecognized keysym "XF86Voicemail" kwin_xkbcommon: XKB: inet:262:58: unrecognized keysym "XF86Addressbook" kwin_xkbcommon: XKB: inet:264:58: unrecognized keysym "XF86DisplayToggle" kwin_xkbcommon: XKB: inet:265:58: unrecognized keysym "XF86SpellCheck" kwin_xkbcommon: XKB: inet:271:58: unrecognized keysym "XF86ContextMenu" kwin_xkbcommon: XKB: inet:272:58: unrecognized keysym "XF86MediaRepeat" kwin_xkbcommon: XKB: inet:273:58: unrecognized keysym "XF8610ChannelsUp" kwin_xkbcommon: XKB: inet:274:58: unrecognized keysym "XF8610ChannelsDown" kwin_xkbcommon: XKB: inet:275:58: unrecognized keysym "XF86Images" kwin_xkbcommon: XKB: inet:276:58: unrecognized keysym "XF86NotificationCenter" kwin_xkbcommon: XKB: inet:277:58: unrecognized keysym "XF86PickupPhone" kwin_xkbcommon: XKB: inet:278:58: unrecognized keysym "XF86HangupPhone" kwin_xkbcommon: XKB: inet:279:58: unrecognized keysym "XF86Fn" kwin_xkbcommon: XKB: inet:280:58: unrecognized keysym "XF86Fn_Esc" kwin_xkbcommon: XKB: inet:281:58: unrecognized keysym "XF86FnRightShift" kwin_xkbcommon: XKB: inet:292:58: unrecognized keysym "XF86Numeric0" kwin_xkbcommon: XKB: inet:293:58: unrecognized keysym "XF86Numeric1" kwin_xkbcommon: XKB: inet:294:58: unrecognized keysym "XF86Numeric2" kwin_xkbcommon: XKB: inet:295:58: unrecognized keysym "XF86Numeric3" kwin_xkbcommon: XKB: inet:296:58: unrecognized keysym "XF86Numeric4" kwin_xkbcommon: XKB: inet:297:58: unrecognized keysym "XF86Numeric5" kwin_xkbcommon: XKB: inet:298:58: unrecognized keysym "XF86Numeric6" kwin_xkbcommon: XKB: inet:299:58: unrecognized keysym "XF86Numeric7" kwin_xkbcommon: XKB: inet:300:58: unrecognized keysym "XF86Numeric8" kwin_xkbcommon: XKB: inet:301:58: unrecognized keysym "XF86Numeric9" kwin_xkbcommon: XKB: inet:302:58: unrecognized keysym "XF86NumericStar" kwin_xkbcommon: XKB: inet:303:58: unrecognized keysym
Bug#902953: marked as done (jetty9: CVE-2017-7656 CVE-2017-7657 CVE-2017-7658)
Your message dated Mon, 18 Oct 2021 11:48:13 +0200 with message-id and subject line Re: jetty9: CVE-2017-7656 CVE-2017-7657 CVE-2017-7658 CVE-2018-12536 CVE-2018-12538 has caused the Debian Bug report #902953, regarding jetty9: CVE-2017-7656 CVE-2017-7657 CVE-2017-7658 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.) -- 902953: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=902953 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: jetty9 X-Debbugs-CC: t...@security.debian.org Severity: grave Tags: security Hi, The following vulnerabilities were published for jetty9. CVE-2017-7656[0]: | In Eclipse Jetty, versions 9.2.x and older, 9.3.x (all | configurations), and 9.4.x (non-default configuration with RFC2616 | compliance enabled), HTTP/0.9 is handled poorly. An HTTP/1 style | request line (i.e. method space URI space version) that declares a | version of HTTP/0.9 was accepted and treated as a 0.9 request. If | deployed behind an intermediary that also accepted and passed through | the 0.9 version (but did not act on it), then the response sent could | be interpreted by the intermediary as HTTP/1 headers. This could be | used to poison the cache if the server allowed the origin client to | generate arbitrary content in the response. CVE-2017-7657[1]: | In Eclipse Jetty, versions 9.2.x and older, 9.3.x (all | configurations), and 9.4.x (non-default configuration with RFC2616 | compliance enabled), transfer-encoding chunks are handled poorly. The | chunk length parsing was vulnerable to an integer overflow. Thus a | large chunk size could be interpreted as a smaller chunk size and | content sent as chunk body could be interpreted as a pipelined | request. If Jetty was deployed behind an intermediary that imposed | some authorization and that intermediary allowed arbitrarily large | chunks to be passed on unchanged, then this flaw could be used to | bypass the authorization imposed by the intermediary as the fake | pipelined request would not be interpreted by the intermediary as a | request. CVE-2017-7658[2]: | In Eclipse Jetty Server, versions 9.2.x and older, 9.3.x (all non | HTTP/1.x configurations), and 9.4.x (all HTTP/1.x configurations), | when presented with two content-lengths headers, Jetty ignored the | second. When presented with a content-length and a chunked encoding | header, the content-length was ignored (as per RFC 2616). If an | intermediary decided on the shorter length, but still passed on the | longer body, then body content could be interpreted by Jetty as a | pipelined request. If the intermediary was imposing authorization, the | fake pipelined request would bypass that authorization. CVE-2018-12536[3]: | In Eclipse Jetty Server, all 9.x versions, on webapps deployed using | default Error Handling, when an intentionally bad query arrives that | doesn't match a dynamic url-pattern, and is eventually handled by the | DefaultServlet's static file serving, the bad characters can trigger a | java.nio.file.InvalidPathException which includes the full path to the | base resource directory that the DefaultServlet and/or webapp is | using. If this InvalidPathException is then handled by the default | Error Handler, the InvalidPathException message is included in the | error response, revealing the full server path to the requesting | system. CVE-2018-12538[4]: | In Eclipse Jetty versions 9.4.0 through 9.4.8, when using the optional | Jetty provided FileSessionDataStore for persistent storage of | HttpSession details, it is possible for a malicious user to | access/hijack other HttpSessions and even delete unmatched | HttpSessions present in the FileSystem's storage for the | FileSessionDataStore. If you fix the vulnerabilities please also make sure to include the CVE (Common Vulnerabilities & Exposures) ids in your changelog entry. For further information see: [0] https://security-tracker.debian.org/tracker/CVE-2017-7656 https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-7656 [1] https://security-tracker.debian.org/tracker/CVE-2017-7657 https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-7657 [2] https://security-tracker.debian.org/tracker/CVE-2017-7658 https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-7658 [3] https://security-tracker.debian.org/tracker/CVE-2018-12536 https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-12536 [4] https://security-tracker.debian.org/tracker/CVE-2018-12538 https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-12538 Please adjust the affected versions in the BTS as needed. Markus
Processed: reopen stardict
Processing commands for cont...@bugs.debian.org:
> unarchive 947540
Bug #947540 {Done: Debian FTP Masters }
[src:stardict] stardict: build-depends on deprecated gnome-doc-utils
Unarchived Bug 947540
> reopen 947540 =
Bug #947540 {Done: Debian FTP Masters }
[src:stardict] stardict: build-depends on deprecated gnome-doc-utils
'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 3.0.6+dfsg-0.3+rm.
> notfixed 947540 3.0.6+dfsg-0.3+rm
Bug #947540 [src:stardict] stardict: build-depends on deprecated gnome-doc-utils
The source 'stardict' and version '3.0.6+dfsg-0.3+rm' do not appear to match
any binary packages
Ignoring request to alter fixed versions of bug #947540 to the same values
previously set
>
End of message, stopping processing here.
Please contact me if you need assistance.
--
947540: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=947540
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#994178:
RAmesh
Processed: Re: client certificate verification regression with puppetdb
Processing control commands: > severity -1 normal Bug #924005 [jetty9] client certificate verification regression with puppetdb Severity set to 'normal' from 'grave' -- 924005: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=924005 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#924005: client certificate verification regression with puppetdb
Control: severity -1 normal On Fri, 8 Mar 2019 09:59:14 +0100 "=?UTF-8?Q?Stefan_B=c3=bchler?=" wrote: > Package: jetty9 > Version: 9.4.15-1 > Severity: important > > Hi. > > The update (libjetty9-java and libjetty9-extra-java) to 9.4.15-1 broke > our puppetdb setup; a downgrade to 9.4.14-1 fixes the issue. > > I can't see any (new/useful/related) error message in the puppetdb log. > > The error message from our puppetmaster is: > > Error connecting to puppet-db.XXX on 8081 at route /pdb/cmd/v1?..., error message received was 'SSL_connect returned=1 errno=0 state=error: sslv3 alert certificate unknown'. Failing over to the next PuppetDB server_url in the 'server_urls' list [...] As Manfred Stock in this bug report has already mentioned, the breakage was caused by a change in Jetty 9.4.15 which disabled Endpoint Identification by default and the switch to HTTPS. This apparently caused a problem with Puppet. To me it seems this is merely a configuration problem on the Puppet side and a workaround exists. I leave this bug report open for future reference but I feel there is nothing what we can do to improve the situation in Buster from the Jetty point of view. Markus signature.asc Description: This is a digitally signed message part
Bug#992319: RM: nekobee -- RoQA, unmaintained, RC-buggy, dead-upstream, python2
Control: reassign -1 ftp.debian.org Control: severity -1 normal Reassigning to make the RM happen, as announced three months ago. On Tue, 17 Aug 2021 07:39:54 +0200 Tobias Frost wrote: > Package: nekobee > Severity: serious > > nekobee is currently RC buggy with 2 RC bugs, (one being a gcc 10 and one being > a python-removal-bug; upstream seems dead as well with only a minor commit last > year. > The Debian package has seen the last upload 5 years ago, and missed bullseye, > so it looks unmaintained from here. > > I guess this software is EOL and should probably be removed from the archives. > > Dear maintainer, > > If you disagree, just close this bug. > If you agree, please reassign this bug to ftp.d.o to make the RM happening. > I will do the latter in exactly 3 months from now if there is no answer on this bug. > > -- > tobi > >
Processed: Re: RM: nekobee -- RoQA, unmaintained, RC-buggy, dead-upstream, python2
Processing control commands: > reassign -1 ftp.debian.org Bug #992319 [nekobee] RM: nekobee -- RoQA, unmaintained, RC-buggy, dead-upstream, python2 Bug reassigned from package 'nekobee' to 'ftp.debian.org'. Ignoring request to alter found versions of bug #992319 to the same values previously set Ignoring request to alter fixed versions of bug #992319 to the same values previously set > severity -1 normal Bug #992319 [ftp.debian.org] RM: nekobee -- RoQA, unmaintained, RC-buggy, dead-upstream, python2 Severity set to 'normal' from 'serious' -- 992319: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=992319 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#996758: RM: openlayer: RoQA, unmaintained, dead upstream, low popcon
Source: openlayer Severity: serious The homepage in d/control just leads to berlios.de, dead since many years. The package looks unmaintained, and upstream dead. Popcon is at 4. There are no reverse dependencies. That makes me wonder if openlayer should be just removed. If you disagree, just close this bug, but please show the package some love. If you agree, reassign the bug to ftp.debian.org If there is no answer, I will reassing the bug in exactly 3 months to ftp.debian.org to make the RM happen. Cheers, -- tobi
Bug#996757: golang-github-lucas-clemente-quic-go: FTBFS with golang/1.17: panic: qtls.ClientHelloInfo doesn't match
Source: golang-github-lucas-clemente-quic-go Version: 0.19.3-1 Severity: serious Tags: ftbfs Justification: ftbfs X-Debbugs-Cc: z...@debian.org panic: qtls.ClientHelloInfo doesn't match goroutine 1 [running]: github.com/marten-seemann/qtls-go1-15.init.0() /<>/obj-x86_64-linux-gnu/src/github.com/marten-seemann/qtls-go1-15/unsafe.go:20 +0x132 FAILgithub.com/lucas-clemente/quic-go 0.004s panic: qtls.ClientHelloInfo doesn't match The panic is in golang-github-marten-seemann-qtls-go1-15, but this package needs update as well.
Bug#996756: golang-github-marten-seemann-qtls-go1-15: FTBFS with golang/1.17: panic: qtls.ClientHelloInfo doesn't match
Source: golang-github-marten-seemann-qtls-go1-15 Version: 0.1.1-2 Severity: serious Tags: ftbfs Justification: ftbfs X-Debbugs-Cc: z...@debian.org dh_auto_test -O--builddirectory=_build -O--buildsystem=golang cd _build && go test -vet=off -v -p 12 github.com/marten-seemann/qtls-go1-15 panic: qtls.ClientHelloInfo doesn't match goroutine 1 [running]: github.com/marten-seemann/qtls-go1-15.init.0() /<>/_build/src/github.com/marten-seemann/qtls-go1-15/unsafe.go:20 +0x132 FAILgithub.com/marten-seemann/qtls-go1-15 0.006s FAIL
Bug#996618: marked as done (libhmsbeagle1v5 lists beignet-opencl-icd as first alternative)
Your message dated Mon, 18 Oct 2021 08:24:04 + with message-id and subject line Bug#996618: fixed in libhmsbeagle 3.1.2+dfsg-12 has caused the Debian Bug report #996618, regarding libhmsbeagle1v5 lists beignet-opencl-icd as first alternative 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.) -- 996618: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=996618 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: libhmsbeagle1v5 Version: 3.1.2+dfsg-11 Severity: serious beignet is on the autoremoval list, see https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=974792#35 for background. This put arb/beast-mcmc/beast2-mcmc/libhmsbeagle/mrbayes on the autoremoval list due to Package: libhmsbeagle1v5 Depends: ..., beignet-opencl-icd | mesa-opencl-icd | opencl-icd I think it is a bug in any case that beignet-opencl-icd is listed there as first alternative (which is triggering the autoremoval), OpenCL Maintainers are in Cc for advising what the recommended dependencies are. --- End Message --- --- Begin Message --- Source: libhmsbeagle Source-Version: 3.1.2+dfsg-12 Done: Andreas Tille We believe that the bug you reported is fixed in the latest version of libhmsbeagle, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 996...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Andreas Tille (supplier of updated libhmsbeagle package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Mon, 18 Oct 2021 09:42:01 +0200 Source: libhmsbeagle Architecture: source Version: 3.1.2+dfsg-12 Distribution: unstable Urgency: medium Maintainer: Debian Med Packaging Team Changed-By: Andreas Tille Closes: 996618 Changes: libhmsbeagle (3.1.2+dfsg-12) unstable; urgency=medium . * Drop beignet-opencl-icd from explicit Depends Closes: #996618 * Remove Tim Booth from Uploaders (Tim, thank you for all your previous work) Checksums-Sha1: 5307681e37229bfc41a386f664173eea2df01d92 2362 libhmsbeagle_3.1.2+dfsg-12.dsc 1d4faf358a9ef2afb499d01d4cba0b49d20d3d55 37224 libhmsbeagle_3.1.2+dfsg-12.debian.tar.xz 27a131a4fb8a12f05a6b35df0f32f73f78c2a9ef 13290 libhmsbeagle_3.1.2+dfsg-12_amd64.buildinfo Checksums-Sha256: e466bc7bf9fbae520637d94f9249f4d34d506e78fd066212ae8e50e6a2c113a1 2362 libhmsbeagle_3.1.2+dfsg-12.dsc 7fd65c51ff04477db99fb5b763fe37ae69e24b323ddd533bc9dd4bb0d010d578 37224 libhmsbeagle_3.1.2+dfsg-12.debian.tar.xz b19b7eddd5987a8ba76308316737bd376ce1246674e0ba2e0dad6631e4ecb8ae 13290 libhmsbeagle_3.1.2+dfsg-12_amd64.buildinfo Files: 48cb4e572631e5c6e299624a56fd0b81 2362 libs optional libhmsbeagle_3.1.2+dfsg-12.dsc 298c48c6d82b2a13cc19ea39b0de3327 37224 libs optional libhmsbeagle_3.1.2+dfsg-12.debian.tar.xz d3a28832127f748184f25b91d2824b2e 13290 libs optional libhmsbeagle_3.1.2+dfsg-12_amd64.buildinfo -BEGIN PGP SIGNATURE- iQJFBAEBCgAvFiEE8fAHMgoDVUHwpmPKV4oElNHGRtEFAmFtJtARHHRpbGxlQGRl Ymlhbi5vcmcACgkQV4oElNHGRtE2FA//XaX5DpluuUhFHgc/nC7WgY90hc431MoU GwuR6gwCz0wIlpStPstC7PbKeZkLIYJfND0CndTHa/ATyN2IhFq5dKsvFli6tGgq aTTPC3f8m/ZVjuX29I4ZYk8eFqLTgzrrZOmsKAVefxI+W2PyPMzTlMLmX7hbTovu UOYmRlaQaBNhGbhErerpr2s04z36YP8psMPpf3cQpAocb48IyNDZRmBY9fD9xUJT 7ZgzGjwfMpRWAaS6oDqZJerrK5mAARyUKN4rkbx4FwdHlIv4BFmb4xqMfNU0k9Gs vJmIOLgVdyxwTB1VgAGP9UPBzlyAvxH9zQdpnHDiOiCy8/+vj6ZtU7tq6s8hDxX9 Hvcp+0xTUgHKBBx3q0OCPjN4nbgmmp/dfrL9opBFdZuzlLsMroys4CnX4npD NMgEWWrH7U2ha6NrUdCqopFS5ChZ/zO3t7fncdcBdZJ0+nYsWZqf3RcmPuvTTMQL aoLDPj4u2WEsfEZXFyukZFMfPlKnzQH3uKztnx9pa+Kv22klVMFMx2xVWgWvu0nL cyCNdNAfLGuDRk+8lQ/ju/ufkbxJPOHF9Dol/iMnUpvenAOHzW+Ji4Pi8Vp5aKLN uG8WryPBFoF5R/zCZDP0YjjK1wmjWNkV3HwLlHJ4mRvxDX1z6iblDw6iAHETwdAQ 8l6JS89G1Rg= =B76c -END PGP SIGNATURE End Message ---
Bug#996724: ruby3.0: FTBFS on ppc64el: Segmentation fault
Hello! On 10/17/21 21:50, John Paul Adrian Glaubitz wrote: > Ah, so the last successful build was 3.0.2-2 and the first failure was in > 3.0.2-3, > the only difference being the mipsel patch to fix an unaligned access. > > However, 3.0.2-2 was built with gcc-10: > >> https://buildd.debian.org/status/fetch.php?pkg=ruby3.0=ppc64el=3.0.2-2=1633362713=0 > > while 3.0.2-3 was built with gcc-11: > >> https://buildd.debian.org/status/fetch.php?pkg=ruby3.0=ppc64el=3.0.2-3=1634169532=0 > > So, first we should try building with gcc-10 and see if that makes a > difference. I have tested the build with gcc-10 but the problem remains, so it's not a compiler issue. Dropping the patch rand_init-fix-off-by-one-error.patch that was introduced with 3.0.2-3 doesn't help either. So, we need a backtrace to see where the crash actually happens. I assume it's in one of the build dependencies. Adrian -- .''`. John Paul Adrian Glaubitz : :' : Debian Developer - glaub...@debian.org `. `' Freie Universitaet Berlin - glaub...@physik.fu-berlin.de `-GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913
Bug#996559: minimap2 FTBFS on !x86
Hi Michael, I'd like to bring this issue to your attention. Usually it seems to be cheap to patch out -msse2 from options. However, I'm hesitating with this for targets explicitly named ksw2_extz2_sse2.o:ksw2_extz2_sse.c Since I have no idea about minimap2 at all I'd prefer to be a bit careful - may be discussing the issue with upstream should be done in case you have no idea as well. Kind regards Andreas. Am Fri, Oct 15, 2021 at 04:37:51PM +0300 schrieb Adrian Bunk: > Source: minimap2 > Version: 2.22+dfsg-1 > Severity: serious > Tags: ftbfs > > https://buildd.debian.org/status/logs.php?pkg=minimap2=2.22%2Bdfsg-1 > > ... > cc -c -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong > -Wformat -Werror=format-security -fopenmp-simd -O3 -DSIMDE_ENABLE_OPENMP > -DUSE_SIMDE -DSIMDE_ENABLE_NATIVE_ALIASES -g -Wall -O2 -Wc++-compat -msse2 > -Wdate-time -D_FORTIFY_SOURCE=2 -DHAVE_KALLOC ksw2_ll_sse.c -o ksw2_ll_sse.o > cc: error: unrecognized command-line option ‘-msse2’ > make[2]: *** [Makefile:64: ksw2_ll_sse.o] Error 1 > ___ > Debian-med-packaging mailing list > debian-med-packag...@alioth-lists.debian.net > https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/debian-med-packaging -- http://fam-tille.de
Processed: tagging 994677
Processing commands for cont...@bugs.debian.org: > tags 994677 + pending Bug #994677 [src:ladvd] ladvd FTBFS: error: ‘MAXPATHLEN’ undeclared Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 994677: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=994677 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#991225: marked as done (Needs a versioned dependency on python3-translate)
Your message dated Mon, 18 Oct 2021 06:03:32 +
with message-id
and subject line Bug#991225: fixed in translate-toolkit 3.4.1-1
has caused the Debian Bug report #991225,
regarding Needs a versioned dependency on python3-translate
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.)
--
991225: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=991225
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: translate-toolkit
Version: 3.3.6-1
Severity: serious
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
The translate-toolkit has an unversioned dependency on python3-toolkit.
But so one can install the package from experimenal while still having
python3-toolkit installed. This leads to an error:
pkg_resources.VersionConflict: (translate-toolkit 3.3.2
(/usr/lib/python3/dist-packages), Requirement.parse('translate-toolkit==3.3.6'))
and the scripts die. It clearly needs a versioned dependency on python3-toolkit.
Regards, Daniel
- -- System Information:
Debian Release: 11.0
APT prefers unstable
APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1,
'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 5.10.0-8-amd64 (SMP w/8 CPU threads)
Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages translate-toolkit depends on:
ii python33.9.2-3
ii python3-pkg-resources 52.0.0-4
ii python3-translate 3.3.2-1
Versions of packages translate-toolkit recommends:
ii translate-toolkit-doc 3.3.2-1
translate-toolkit suggests no packages.
- -- no debconf information
- -- debsums errors found:
debsums: changed file /usr/bin/json2po (from translate-toolkit package)
-BEGIN PGP SIGNATURE-
iQIzBAEBCgAdFiEEvu1N7VVEpMA+KD3HS80FZ8KW0F0FAmDzcDAACgkQS80FZ8KW
0F2drA//Vi8EUKDn1gdDfkSnLKvUwnpWcZp5c4oNZeD8uNpBqcEEm2YH5sroMyPk
kpELs76VBNqc+oJRwE7Q+5vMI3UNUriRL+kWJlqA5Ef6fOZjKDfF7oEFXsyFO2oq
gDdmaxs+qvAR0CrhmO7dKxDjT0XTn04xEsaNaKsjRhqi8QCNVS1lj7Ybguj5jquC
jag1NBffmEMjjNfcyw0zjNtGPBVNlFq5WAt4Hfy0MP6NXp5qYUZ2m2kQwn9qLCyz
EGq2UGRx+JdOQh4P/tAPg3Em4MoQXetgsQEt8tq2wmkguHfTWPQc5GmKGYTqbaiF
nZF2xpwNeA/bOB9W1eqjG3djIde88CGGe44X2ZID+ivQUr4M1DK8waBU0YSZR54w
AlPOAce+YDZ6qX3UGCUufRH4NbkuPFsHVwS1FqOdh6izvaYeX1VI+6HazsNIFwgD
S3hTjidDo7lG427/nNBLHA90u0Plumm3vTX/FfcN4KfLxYsbiddCnIxTN14cfKMd
5xsIx5i1KVD5aydnfUkQXgoxU74bxZ1TsZZF7sCR9CBGTyqcpzO+rZVS8xQCPI1a
9NFzK39dDWg0APybbdlAPvtOihBL9p36VK915kOToMHtyFotkLhhL38ITkniJ1qb
iADC6OkQNiJR5eutVj68xcHIPv0xTMMLrM1XVpsEtBlcXOgt4OY=
=XnyG
-END PGP SIGNATURE-
--- End Message ---
--- Begin Message ---
Source: translate-toolkit
Source-Version: 3.4.1-1
Done: Stuart Prescott
We believe that the bug you reported is fixed in the latest version of
translate-toolkit, 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 991...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Stuart Prescott (supplier of updated translate-toolkit
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: Mon, 18 Oct 2021 15:56:46 +1100
Source: translate-toolkit
Architecture: source
Version: 3.4.1-1
Distribution: unstable
Urgency: medium
Maintainer: Debian l10n developers
Changed-By: Stuart Prescott
Closes: 991225
Changes:
translate-toolkit (3.4.1-1) unstable; urgency=medium
.
* New upstream release.
* Update Standards-Version to 4.6.0 (no changes required).
* Include tight version requirement between translate-toolkit and
python3-translate (Closes: #991225).
* Add patch to stub-out use of unpackaged "fluent.syntax" module
in test suite.
Checksums-Sha1:
991c35d00255dd1a8f440c0e254334d381e7b45c 3000 translate-toolkit_3.4.1-1.dsc
8c76d0c38404bbd27acea118b7494f4818e7d532 1147673
translate-toolkit_3.4.1.orig.tar.gz
f9dd854e1120756cd77d2956ee5cf8281a17cb15 23968
translate-toolkit_3.4.1-1.debian.tar.xz
3bd15e5472e23ea682e7485f2a42fc722d9dc659 9508
translate-toolkit_3.4.1-1_amd64.buildinfo
Checksums-Sha256:
Bug#991225: marked as pending in translate-toolkit
Control: tag -1 pending Hello, Bug #991225 in translate-toolkit reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/l10n-team/translate-toolkit/-/commit/7eb1ef7a46051f830ce4ce7c0c1e98e939eba58f Tightly version dep translate-toolkit to modules (Closes: #991225) (this message was generated automatically) -- Greetings https://bugs.debian.org/991225
Processed: Bug#991225 marked as pending in translate-toolkit
Processing control commands: > tag -1 pending Bug #991225 [translate-toolkit] Needs a versioned dependency on python3-translate Added tag(s) pending. -- 991225: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=991225 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
