Processed: Bug#970501 marked as pending in dojo
Processing control commands: > tag -1 pending Bug #970501 [src:dojo] dojo FTBFS: Cannot set property "dojo" of null Added tag(s) pending. -- 970501: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=970501 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#970501: marked as pending in dojo
Control: tag -1 pending Hello, Bug #970501 in dojo 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/js-team/dojo/-/commit/68e6a048b4c4386d0495e7faf11bd46bf0516604 Fix shrinksafe tests with newer rhino by setting JS version Closes: #970501 (this message was generated automatically) -- Greetings https://bugs.debian.org/970501
Bug#981237: marked as done (mycli: Mycli breaks with newer sqlparse)
Your message dated Sat, 30 Jan 2021 07:03:31 + with message-id and subject line Bug#981237: fixed in mycli 1.23.2-0.1 has caused the Debian Bug report #981237, regarding mycli: Mycli breaks with newer sqlparse 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.) -- 981237: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=981237 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: mycli Version: 1.22.2-0.1 Severity: grave Justification: renders package unusable Dear Maintainer, The Debian package of mycli has the following dependency: python3-sqlparse (>= 0.3.0) Yet the python code in the package has the following dependency: sqlparse>=0.3.0,<0.4.0 The debian sqlparse package in unstable was just updated to version 0.4.1-1. This causes the mycli code to raise an exception and abort because the installed sqlparse is too new. The master branch of the upstream, mycli source appears to still have the old dependency so the problem is probably not fixed there yet either. David -- System Information: Debian Release: bullseye/sid APT prefers testing APT policy: (900, 'testing'), (100, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.10.0-1-amd64 (SMP w/16 CPU threads) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages mycli depends on: ii python3 3.9.1-1 ii python3-click 7.1.2-1 ii python3-configobj 5.0.6-4 ii python3-cryptography3.2.1-1 ii python3-pkg-resources 51.3.3-1 ii python3-prompt-toolkit 3.0.10-1 ii python3-pygments2.7.1+dfsg-1 ii python3-pymysql 0.9.3-2 ii python3-sqlparse0.4.1-1 ii python3-tabulate0.8.7-0.1 ii python3-terminaltables 3.1.0-3 mycli recommends no packages. mycli suggests no packages. -- no debconf information --- End Message --- --- Begin Message --- Source: mycli Source-Version: 1.23.2-0.1 Done: Daniel Baumann We believe that the bug you reported is fixed in the latest version of mycli, 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 981...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Daniel Baumann (supplier of updated mycli package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sat, 30 Jan 2021 07:31:06 +0100 Source: mycli Architecture: source Version: 1.23.2-0.1 Distribution: unstable Urgency: medium Maintainer: Lennart Weller Changed-By: Daniel Baumann Closes: 981237 Changes: mycli (1.23.2-0.1) unstable; urgency=medium . * Non-maintainer upload. * New upstream release: - compatibility with sqlparse 4 (Closes: #981237) * Refreshing 0001-rename-cli-so-it-can-be-moved-to-usr-share-mycli.patch. * Refreshing 0002-vendorized-cli_helpers.patch. Checksums-Sha1: 7726e2536fc42d367da5fcdc31eb5d6442cf2c5a 1898 mycli_1.23.2-0.1.dsc bff4e19d107aca344ca7f029a745c64d69a7a90e 272295 mycli_1.23.2.orig.tar.gz 99c7524b53b190078020cce86b9d5b45e1c574bf 13768 mycli_1.23.2-0.1.debian.tar.xz 136e5cdae77c9e842c423d968cc2913ca6d45138 6356 mycli_1.23.2-0.1_amd64.buildinfo Checksums-Sha256: d555e2798314247d11ddfcd114e010c7a7389ccd5cba5968419d1e391ac62647 1898 mycli_1.23.2-0.1.dsc 5bc5ad38d5217ef6bd60f75044124a92156b3d64e2f968f9a6ef32ee04ed8ed5 272295 mycli_1.23.2.orig.tar.gz be1d015a1645c492dfb8f7863cd835bf1e221e044e0ec84d64daff67ea0e9ace 13768 mycli_1.23.2-0.1.debian.tar.xz c227e0eaa4353cf7f56a649002fd4ffca3e98dbb1a5428e44a5352bb171cec7f 6356 mycli_1.23.2-0.1_amd64.buildinfo Files: 16ea5f2f8afea4275b35da03297813d9 1898 database optional mycli_1.23.2-0.1.dsc 76cba84e4ea744fd1164d41caf6aa25b 272295 database optional mycli_1.23.2.orig.tar.gz 8f45dfcd59ae23bc11fa83ec445374c5 13768 database optional mycli_1.23.2-0.1.debian.tar.xz dd70ae2eb349961cdd401f12f8bc7633 6356 database optional mycli_1.23.2-0.1_amd64.buildinfo -BEGIN PGP SIGNATURE-
Bug#981252: marked as done (polymake: tests fail on mips{64,}el)
Your message dated Sat, 30 Jan 2021 02:34:13 +
with message-id
and subject line Bug#981252: fixed in polymake 4.3-3
has caused the Debian Bug report #981252,
regarding polymake: tests fail on mips{64,}el
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.)
--
981252: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=981252
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: polymake
Version: 4.3-2
Severity: serious
Justification: FTBFS
X-Debbugs-Cc: Benjamin Lorenz
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
The full log for mips64el is at
https://buildd.debian.org/status/fetch.php?pkg=polymake=mips64el=4.3-2=1611277005=0
The relevant output from the tests seems to be
[ /polytope/objects/Polytope/properties/Triangulation and
volume/RELATIVE_VOLUME ] 1polymake: WARNING: rule RELATIVE_VOLUME :
SQUARED_RELATIVE_VOLUMES failed: Undefined subroutine
::polytope::Polytope__Rational::_Full_Spez::sum_of_square_roots_naive
called at /<>/apps/polytope/rules/rational.rules line 73.
/<>/apps/polytope/rules/rational.rules:65: testcase 1
expected: regular return
got: EXCEPTION: no more rules available to compute 'RELATIVE_VOLUME'
At a guess I'd imagine an architecture dependent bug in one of the
dependencies. But that's purely a guess.
- -- System Information:
Debian Release: bullseye/sid
APT prefers unstable-debug
APT policy: (500, 'unstable-debug'), (500, 'testing-debug'), (500, 'testing')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 5.10.0-1-amd64 (SMP w/8 CPU threads)
Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=en_CA.UTF-8, LC_CTYPE=en_CA.UTF-8 (charmap=UTF-8),
LANGUAGE=en_CA:en
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
- -- no debconf information
-BEGIN PGP SIGNATURE-
iQIzBAEBCAAdFiEEkiyHYXwaY0SiY6fqA0U5G1WqFSEFAmASpwkACgkQA0U5G1Wq
FSExZg/+M1Jnk7AEmuP4LH9VstNLkapOuqAcBsjm+FXBaPPYqZDbWFS/XhrrvcRX
DeTpTciZRG+4dmOYkkN+iBTGEqHCKRxQ4Gfb1nhPN3zgLVLdsubbkFB9+bOgZK1r
F6bu6Ry0nz/pCSi1d8LXZeJMXtctlTHHcb5JeJcpNevi+s8GdZ00jMdsghCLIsbz
oYs3eVW534JAiSrPv3xBP8dlMOwSp9N1tvFqqy47vNvZkJW0IBq3u23dxdvMDVWZ
rOnsSZynE8idI6uCySkeDjjs5g4sUjsE1p+BT9e+BGXuIoDPY2MswcaMyZIIMmvf
MCPiZP1rb857B6+Z45phkac7JK9ZrEaOlwaQ94CyAH5CNyU1o+CIaX9QQg1nLZP5
aXJ+BE+sjbcs2SA7+ZKr1lfNVdhwTmZQ2fzmS2EOJm0RXSjOIwGHSYUqoBX2dJ6c
toSKobwNDKd7EdXY4Yrz2HLJvGgpks1s6AR40CfkyycMSC0aE4ELLvQ5BAhp/u4O
TK0tc+Sr81BLrQaGAfzUS1Zts57wrfHGaxH4zkit+TZvtm3oHHHNx4aa3nR4PSOQ
9sFNgiQ/S9tKt95FzYmJYD2jyZ1SKVo8waebzNlFEvYQrOMhBBLjKt8JU4bWwGLV
EVdj9cVsNpDgxzjFKc6Swlx9eKw9GHV8jwtw1ucQ6PbbcQtv8+A=
=F26M
-END PGP SIGNATURE-
--- End Message ---
--- Begin Message ---
Source: polymake
Source-Version: 4.3-3
Done: David Bremner
We believe that the bug you reported is fixed in the latest version of
polymake, 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 981...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
David Bremner (supplier of updated polymake 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, 29 Jan 2021 20:45:56 -0400
Source: polymake
Architecture: source
Version: 4.3-3
Distribution: unstable
Urgency: medium
Maintainer: David Bremner
Changed-By: David Bremner
Closes: 977722 981252
Changes:
polymake (4.3-3) unstable; urgency=medium
.
* Disable relative volume test when flint is missing (Closes: #981252).
* Bug fix: "man page mentions outdated file argument", thanks to Joachim
Zobel for the report, and Benjamin Lorenz for the update (Closes: #977722).
Checksums-Sha1:
d88ab9f1e940cb859e1c04e76d5d5a6e401d03f7 2548 polymake_4.3-3.dsc
a4932bc5b8ea0d2c1688b70054aa3c1c53726517 11380 polymake_4.3-3.debian.tar.xz
Checksums-Sha256:
44aeec27b2dc05dc79194ea79dced1df0717a87f02ed8fe62778f8a36d002524 2548
polymake_4.3-3.dsc
39c9730372fd67145116d188907adbdb4509a232ded98e521d0d3be3bc74afb4 11380
polymake_4.3-3.debian.tar.xz
Files:
e7489f5fb788132ea6cb969ab936063b 2548 math optional polymake_4.3-3.dsc
251bb2e028d9b0cad7e580df4261cc3c 11380 math optional
polymake_4.3-3.debian.tar.xz
-BEGIN PGP
Processed: Re: rhino breaks dojo autopkgtest: Cannot set property "dojo" of null to "[object Object]"
Processing commands for cont...@bugs.debian.org: > tag 970501 + patch Bug #970501 [src:dojo] dojo FTBFS: Cannot set property "dojo" of null Added tag(s) patch. > thanks Stopping processing here. Please contact me if you need assistance. -- 970501: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=970501 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#970501: rhino breaks dojo autopkgtest: Cannot set property "dojo" of null to "[object Object]"
tag 970501 + patch thanks Hello, It appears that newer JavaScript versions supported by Rhino cause Dojo to throw an exception during tests for shrinksafe module. When using an older JavaScript version 1.7, the error goes away. The attached patch fixes build and autopkgtest problems. Please consider applying the patch to ensure that Dojo and its dependents like tt-rss, used in FreedomBox are available in Bullseye. Thanks, -- Sunil >From c92570f765d73aa6c1d717376f81aafa529964c2 Mon Sep 17 00:00:00 2001 From: Sunil Mohan Adapa Date: Fri, 29 Jan 2021 17:51:10 -0800 Subject: [PATCH] Fix shrinksafe tests with newer rhino by setting JS version Signed-off-by: Sunil Mohan Adapa --- .../0004-Fix-shrinksafe-tests-with-new-rhino.patch | 10 ++ debian/patches/series | 1 + 2 files changed, 11 insertions(+) create mode 100644 debian/patches/0004-Fix-shrinksafe-tests-with-new-rhino.patch diff --git a/debian/patches/0004-Fix-shrinksafe-tests-with-new-rhino.patch b/debian/patches/0004-Fix-shrinksafe-tests-with-new-rhino.patch new file mode 100644 index ..486f939a --- /dev/null +++ b/debian/patches/0004-Fix-shrinksafe-tests-with-new-rhino.patch @@ -0,0 +1,10 @@ +Index: dojo/util/shrinksafe/tests/runner.sh +=== +--- dojo.orig/util/shrinksafe/tests/runner.sh dojo/util/shrinksafe/tests/runner.sh +@@ -1,4 +1,4 @@ + #!/bin/sh + + cd ../../doh +-java -classpath ../shrinksafe/js.jar:../shrinksafe/shrinksafe.jar org.mozilla.javascript.tools.shell.Main ../../dojo/dojo.js baseUrl=../../dojo load=doh test=util/shrinksafe/tests/module testUrl=../shrinksafe/tests/module.js ++java -classpath ../shrinksafe/js.jar:../shrinksafe/shrinksafe.jar org.mozilla.javascript.tools.shell.Main -version 170 ../../dojo/dojo.js baseUrl=../../dojo load=doh test=util/shrinksafe/tests/module testUrl=../shrinksafe/tests/module.js diff --git a/debian/patches/series b/debian/patches/series index f39e7f29..c75b2155 100644 --- a/debian/patches/series +++ b/debian/patches/series @@ -1,3 +1,4 @@ 0001-Compatibility-patch-for-newer-rhino.patch 0002-Do-notrun-test-suite-in-build.patch 0003-Disable-flash-storage.patch +0004-Fix-shrinksafe-tests-with-new-rhino.patch -- 2.29.2
Bug#971946: marked as done (libdebian-installer: READSIZE size insufficient for cdebootstrap to build sid/unstable from buster/stable environment)
Your message dated Sat, 30 Jan 2021 01:18:34 +
with message-id
and subject line Bug#971946: fixed in libdebian-installer 0.121
has caused the Debian Bug report #971946,
regarding libdebian-installer: READSIZE size insufficient for cdebootstrap to
build sid/unstable from buster/stable environment
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.)
--
971946: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=971946
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libdebian-installer
Version: 0.119
When using cdebootstrap from within buster/stable to create a rootfs for
sid/unstable, it will fail with:
W: parser_rfc822: Iek! Don't find end of value!
E: Internal error: download
Seems "64k ought to be enough for everyone" strikes again as this is
functionally a dupe of Bug#55 though it is now that a READSIZE of 65536
in libdebian-installer/src/parser_rfc822.c is now insufficient. I
downloaded the deb-src, updated READSIZE to 262144, debuild'ed it and
installed it, cdebootstrap would then complete successfully for
sid/unstable. My diff is:
diff --git a/src/parser_rfc822.c b/src/parser_rfc822.c
index afd336a..b14859e 100644
--- a/src/parser_rfc822.c
+++ b/src/parser_rfc822.c
@@ -35,7 +35,7 @@
#include
#include
-#define READSIZE 65536
+#define READSIZE 262144
int di_parser_rfc822_read (char *begin, size_t size, di_parser_info *info,
di_parser_read_entry_new entry_new, di_parser_read_entry_finish
entry_finish, void *user_data)
{
--- End Message ---
--- Begin Message ---
Source: libdebian-installer
Source-Version: 0.121
Done: Steve McIntyre <93...@debian.org>
We believe that the bug you reported is fixed in the latest version of
libdebian-installer, which is due to be installed in the Debian FTP archive.
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to 971...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Steve McIntyre <93...@debian.org> (supplier of updated libdebian-installer
package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Sat, 30 Jan 2021 00:50:27 +
Source: libdebian-installer
Architecture: source
Version: 0.121
Distribution: unstable
Urgency: medium
Maintainer: Debian Install System Team
Changed-By: Steve McIntyre <93...@debian.org>
Closes: 971946
Changes:
libdebian-installer (0.121) unstable; urgency=medium
.
[ Holger Wansing ]
* Remove trailing whitespaces from changelog and control file, to fix
lintian tag.
.
[ Debian Janitor ]
* Bump debhelper from deprecated 9 to 12.
* Set debhelper-compat version in Build-Depends.
* Drop unnecessary dependency on dh-autoreconf.
* Rely on pre-initialized dpkg-architecture variables.
.
[ Steve McIntyre ]
* Remove the arbitrary limitation on maximum line length in Packages
and Sources files - it's pointless and breaks things
periodically. Closes: #971946
* Update Standards-Version to 4.5.1
Checksums-Sha1:
5cbba2659d992b9c1d9a8d7ae0d9b91e6913f7b3 2213 libdebian-installer_0.121.dsc
69037a89edb587a880ee0e02212c5757e422e74f 72308 libdebian-installer_0.121.tar.xz
65a488ae098ffae667a09af25d133543cef0293d 5990
libdebian-installer_0.121_source.buildinfo
Checksums-Sha256:
8e0338f8df3f85eec0ead0339176d85aaffe5d083b7b477bd5a17f4320fd536f 2213
libdebian-installer_0.121.dsc
889370308ccb2107f0f1c211f3230018b10f146e0a274f7703fcd3c15f6e7fc0 72308
libdebian-installer_0.121.tar.xz
75626fed228f80ec33605226920a80078c09f9a78d21ec35addaec41d558f023 5990
libdebian-installer_0.121_source.buildinfo
Files:
5dd65192541f123c7ef586c20498d570 2213 libs optional
libdebian-installer_0.121.dsc
8bedbe82dedfdbf8daa3d76863af1a32 72308 libs optional
libdebian-installer_0.121.tar.xz
fb38b9b103d7e4cbc222ad848dc06cc8 5990 libs optional
libdebian-installer_0.121_source.buildinfo
-BEGIN PGP SIGNATURE-
iQJFBAEBCAAvFiEEzrtSMB1hfpEDkP4WWHl5VzRCaE4FAmAUr6ERHDkzc2FtQGRl
Ymlhbi5vcmcACgkQWHl5VzRCaE7Frw/8Dd4TlUVn1BncMA77vE5C/CvBQCZn2kLs
kFNkI2Vz1fvRIRLUHmIZ8M/C4yesqXOVOkCrhTWUD9qJNaNl/V+qnLMEW/WIsrYh
ymS5DW9ziCSk+O1UoSa09GHIxuftGZGiHUpvS0gPF7NEdrejgcsZ5xbILidu2rM9
VCnfdHpPYXcJwCGq7zH2YsXAmjVeIkkINJqsmgPJI3WcSemhlzqYWacAIgz1ECra
Bug#971946: marked as pending in libdebian-installer
Control: tag -1 pending Hello, Bug #971946 in libdebian-installer 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/installer-team/libdebian-installer/-/commit/05bea831d433548d7517e24651dd8183dbeb74ca Remove the arbitrary limitation on maximum line length in Packages and Sources files - it's pointless and breaks things periodically. Closes: #971946 (this message was generated automatically) -- Greetings https://bugs.debian.org/971946
Processed: Bug#971946 marked as pending in libdebian-installer
Processing control commands: > tag -1 pending Bug #971946 [libdebian-installer] libdebian-installer: READSIZE size insufficient for cdebootstrap to build sid/unstable from buster/stable environment Added tag(s) pending. -- 971946: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=971946 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#934843: parsedatetime: FTBFS in stretch
On Thu, 14 Nov 2019, Harlan Lieberman-Berg wrote: > tag 934843 +unreproducible > thanks > > On Thu, 15 Aug 2019 19:12:49 + Santiago Vila wrote: > > I tried to build this package in stretch but it failed: > > Hello! > > This is quite strange. I've tried rebuilding it several times in my > stretch sbuild, and it worked every time without error. I also > re-triggered the build on reproducible-builds, and it's now clean > there as well. > > One possibility that comes to mind is locales -- what locales are you > compiling under? It's possible there's a bug in one of the > locale-specific parsers that's not getting exercised on my sbuild, > through, I admit to not being sure how reproducible-builds could have > been affected by the same thing. Otherwise, maybe a difference in one > of the deps that was fixed in the last... day? Sprry for the late reply. I reported this in 2019-08 and the first reply came in 2019-11. By that time, the package built ok again in my autobuilders according to my build history: Status: successful parsedatetime_2.1-3+deb9u1_amd64-20190216T184806.957Z Status: successful parsedatetime_2.1-3+deb9u1_amd64-20190319T030404.993Z Status: failed parsedatetime_2.1-3+deb9u1_amd64-20190812T104812.785Z Status: failed parsedatetime_2.1-3+deb9u1_amd64-20190812T115932.874Z Status: failed parsedatetime_2.1-3+deb9u1_amd64-20190812T115928.188Z Status: failed parsedatetime_2.1-3+deb9u1_amd64-20190812T115932.124Z Status: failed parsedatetime_2.1-3+deb9u1_amd64-20190812T115937.789Z Status: failed parsedatetime_2.1-3+deb9u1_amd64-20190812T115954.716Z Status: failed parsedatetime_2.1-3+deb9u1_amd64-20190812T120006.211Z Status: failed parsedatetime_2.1-3+deb9u1_amd64-20190812T115946.514Z Status: failed parsedatetime_2.1-3+deb9u1_amd64-20190812T120019.561Z Status: failed parsedatetime_2.1-3+deb9u1_amd64-20190812T115949.086Z Status: failed parsedatetime_2.1-3+deb9u1_amd64-20190812T120022.496Z Status: successful parsedatetime_2.1-3+deb9u1_amd64-20191018T145214.267Z Status: successful parsedatetime_2.1-3+deb9u1_amd64-20191018T172715.052Z Status: successful parsedatetime_2.1-3+deb9u1_amd64-20200210T050524.951Z Status: successful parsedatetime_2.1-3+deb9u1_amd64-20200305T171505.547Z Status: successful parsedatetime_2.1-3+deb9u1_amd64-20200720T162707.522Z However, by looking at the build log and the kind of error, I believe it's the kind of date-related bug in the test suite which only happens in certain times of the year. Does this make sense? Why would this happen if not? Result: (time.struct_time(tm_year=2019, tm_mon=8, tm_mday=22, tm_hour=3, tm_min=26, tm_sec=0, +tm_wday=0, tm_yday=224, tm_isdst=-1), 3) Expected: (time.struct_time(tm_year=2020, tm_mon=8, tm_mday=22, tm_hour=3, tm_min=26, tm_sec=0, +tm_wday=5, tm_yday=235, tm_isdst=-1), 3) I have not tested myself, but if this were my package I would try to built it in 2019-08 (using "libfaketime" or something similar), as the failure in the test suite seems to depend on the date on which it's built. (I'm not reopening the bug, but I believe this little extra information belongs to the bug report). Thanks.
Bug#934843: marked as done (parsedatetime: FTBFS in stretch)
Your message dated Sat, 30 Jan 2021 00:30:19 +0100 with message-id <36e68ae1-26ca-a5cd-3663-48d1430f1...@bzed.de> and subject line stretch, unreproducible, no reply ->closing has caused the Debian Bug report #934843, regarding parsedatetime: FTBFS in stretch 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.) -- 934843: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=934843 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:parsedatetime Version: 2.1-3+deb9u1 Severity: serious Tags: ftbfs Dear maintainer: I tried to build this package in stretch but it failed: [...] debian/rules build-indep dh build-indep --with python2,python3 --buildsystem pybuild dh_testdir -i -O--buildsystem=pybuild dh_update_autotools_config -i -O--buildsystem=pybuild dh_auto_configure -i -O--buildsystem=pybuild I: pybuild base:184: python2.7 setup.py config running config I: pybuild base:184: python3.5 setup.py config running config dh_auto_build -i -O--buildsystem=pybuild I: pybuild base:184: /usr/bin/python setup.py build running build running build_py creating /<>/.pybuild/pythonX.Y_2.7/build/parsedatetime copying parsedatetime/__init__.py -> /<>/.pybuild/pythonX.Y_2.7/build/parsedatetime copying parsedatetime/parsedatetime.py -> /<>/.pybuild/pythonX.Y_2.7/build/parsedatetime copying parsedatetime/context.py -> /<>/.pybuild/pythonX.Y_2.7/build/parsedatetime copying parsedatetime/warns.py -> /<>/.pybuild/pythonX.Y_2.7/build/parsedatetime creating /<>/.pybuild/pythonX.Y_2.7/build/parsedatetime/pdt_locales copying parsedatetime/pdt_locales/nl_NL.py -> /<>/.pybuild/pythonX.Y_2.7/build/parsedatetime/pdt_locales copying parsedatetime/pdt_locales/base.py -> /<>/.pybuild/pythonX.Y_2.7/build/parsedatetime/pdt_locales copying parsedatetime/pdt_locales/icu.py -> /<>/.pybuild/pythonX.Y_2.7/build/parsedatetime/pdt_locales copying parsedatetime/pdt_locales/ru_RU.py -> /<>/.pybuild/pythonX.Y_2.7/build/parsedatetime/pdt_locales copying parsedatetime/pdt_locales/de_DE.py -> /<>/.pybuild/pythonX.Y_2.7/build/parsedatetime/pdt_locales copying parsedatetime/pdt_locales/en_AU.py -> /<>/.pybuild/pythonX.Y_2.7/build/parsedatetime/pdt_locales copying parsedatetime/pdt_locales/__init__.py -> /<>/.pybuild/pythonX.Y_2.7/build/parsedatetime/pdt_locales copying parsedatetime/pdt_locales/es.py -> /<>/.pybuild/pythonX.Y_2.7/build/parsedatetime/pdt_locales copying parsedatetime/pdt_locales/en_US.py -> /<>/.pybuild/pythonX.Y_2.7/build/parsedatetime/pdt_locales copying parsedatetime/pdt_locales/pt_BR.py -> /<>/.pybuild/pythonX.Y_2.7/build/parsedatetime/pdt_locales I: pybuild base:184: /usr/bin/python3 setup.py build running build running build_py creating /<>/.pybuild/pythonX.Y_3.5/build/parsedatetime copying parsedatetime/__init__.py -> /<>/.pybuild/pythonX.Y_3.5/build/parsedatetime copying parsedatetime/parsedatetime.py -> /<>/.pybuild/pythonX.Y_3.5/build/parsedatetime copying parsedatetime/context.py -> /<>/.pybuild/pythonX.Y_3.5/build/parsedatetime copying parsedatetime/warns.py -> /<>/.pybuild/pythonX.Y_3.5/build/parsedatetime creating /<>/.pybuild/pythonX.Y_3.5/build/parsedatetime/pdt_locales copying parsedatetime/pdt_locales/nl_NL.py -> /<>/.pybuild/pythonX.Y_3.5/build/parsedatetime/pdt_locales copying parsedatetime/pdt_locales/base.py -> /<>/.pybuild/pythonX.Y_3.5/build/parsedatetime/pdt_locales copying parsedatetime/pdt_locales/icu.py -> /<>/.pybuild/pythonX.Y_3.5/build/parsedatetime/pdt_locales copying parsedatetime/pdt_locales/ru_RU.py -> /<>/.pybuild/pythonX.Y_3.5/build/parsedatetime/pdt_locales copying parsedatetime/pdt_locales/de_DE.py -> /<>/.pybuild/pythonX.Y_3.5/build/parsedatetime/pdt_locales copying parsedatetime/pdt_locales/en_AU.py -> /<>/.pybuild/pythonX.Y_3.5/build/parsedatetime/pdt_locales copying parsedatetime/pdt_locales/__init__.py -> /<>/.pybuild/pythonX.Y_3.5/build/parsedatetime/pdt_locales copying parsedatetime/pdt_locales/es.py -> /<>/.pybuild/pythonX.Y_3.5/build/parsedatetime/pdt_locales copying parsedatetime/pdt_locales/en_US.py -> /<>/.pybuild/pythonX.Y_3.5/build/parsedatetime/pdt_locales copying parsedatetime/pdt_locales/pt_BR.py -> /<>/.pybuild/pythonX.Y_3.5/build/parsedatetime/pdt_locales dh_auto_test -i -O--buildsystem=pybuild I: pybuild base:184: cd /<>/.pybuild/pythonX.Y_2.7/build; python2.7 -m nose tests .F...SSSSSS == FAIL:
Bug#973175: marked as done (google-i18n-address: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p "3.9 3.8" returned exit code 13)
Your message dated Fri, 29 Jan 2021 23:33:36 +
with message-id
and subject line Bug#973175: fixed in google-i18n-address 2.4.0-1
has caused the Debian Bug report #973175,
regarding google-i18n-address: FTBFS: dh_auto_test: error: pybuild --test
--test-pytest -i python{version} -p "3.9 3.8" returned exit code 13
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
973175: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=973175
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: google-i18n-address
Version: 2.3.2-3
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20201027 ftbfs-bullseye
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> dpkg-buildpackage
> -
>
> Command: dpkg-buildpackage -us -uc -sa -rfakeroot
> dpkg-buildpackage: info: source package google-i18n-address
> dpkg-buildpackage: info: source version 2.3.2-3
> dpkg-buildpackage: info: source distribution unstable
> dpkg-buildpackage: info: source changed by Daniel Kahn Gillmor
>
> dpkg-source --before-build .
> dpkg-buildpackage: info: host architecture amd64
> debian/rules clean
> dh clean --with python3 --buildsystem=pybuild
>dh_auto_clean -O--buildsystem=pybuild
> I: pybuild base:217: python3.9 setup.py clean
> running clean
> removing '/<>/.pybuild/cpython3_3.9_i18address/build' (and
> everything under it)
> 'build/bdist.linux-x86_64' does not exist -- can't clean it
> 'build/scripts-3.9' does not exist -- can't clean it
> I: pybuild base:217: python3.8 setup.py clean
> running clean
> removing '/<>/.pybuild/cpython3_3.8_i18address/build' (and
> everything under it)
> 'build/bdist.linux-x86_64' does not exist -- can't clean it
> 'build/scripts-3.8' does not exist -- can't clean it
>dh_autoreconf_clean -O--buildsystem=pybuild
>dh_clean -O--buildsystem=pybuild
> dpkg-source -b .
> dpkg-source: info: using source format '3.0 (quilt)'
> dpkg-source: info: building google-i18n-address using existing
> ./google-i18n-address_2.3.2.orig.tar.gz
> dpkg-source: info: building google-i18n-address in
> google-i18n-address_2.3.2-3.debian.tar.xz
> dpkg-source: info: building google-i18n-address in
> google-i18n-address_2.3.2-3.dsc
> debian/rules binary
> dh binary --with python3 --buildsystem=pybuild
>dh_update_autotools_config -O--buildsystem=pybuild
>dh_autoreconf -O--buildsystem=pybuild
>dh_auto_configure -O--buildsystem=pybuild
> I: pybuild base:217: python3.9 setup.py config
> running config
> I: pybuild base:217: python3.8 setup.py config
> running config
>dh_auto_build -O--buildsystem=pybuild
> I: pybuild base:217: /usr/bin/python3.9 setup.py build
> running build
> running build_py
> creating /<>/.pybuild/cpython3_3.9_i18address/build/tests
> copying tests/__init__.py ->
> /<>/.pybuild/cpython3_3.9_i18address/build/tests
> copying tests/test_normalization.py ->
> /<>/.pybuild/cpython3_3.9_i18address/build/tests
> copying tests/test_i18naddress.py ->
> /<>/.pybuild/cpython3_3.9_i18address/build/tests
> copying tests/test_downloader.py ->
> /<>/.pybuild/cpython3_3.9_i18address/build/tests
> creating /<>/.pybuild/cpython3_3.9_i18address/build/i18naddress
> copying i18naddress/__init__.py ->
> /<>/.pybuild/cpython3_3.9_i18address/build/i18naddress
> copying i18naddress/downloader.py ->
> /<>/.pybuild/cpython3_3.9_i18address/build/i18naddress
> running egg_info
> writing google_i18n_address.egg-info/PKG-INFO
> writing dependency_links to google_i18n_address.egg-info/dependency_links.txt
> writing requirements to google_i18n_address.egg-info/requires.txt
> writing top-level names to google_i18n_address.egg-info/top_level.txt
> reading manifest file 'google_i18n_address.egg-info/SOURCES.txt'
> reading manifest template 'MANIFEST.in'
> writing manifest file 'google_i18n_address.egg-info/SOURCES.txt'
> creating
> /<>/.pybuild/cpython3_3.9_i18address/build/i18naddress/data
> copying i18naddress/data/ac.json ->
> /<>/.pybuild/cpython3_3.9_i18address/build/i18naddress/data
> copying i18naddress/data/ad.json ->
> /<>/.pybuild/cpython3_3.9_i18address/build/i18naddress/data
> copying i18naddress/data/ae.json ->
> /<>/.pybuild/cpython3_3.9_i18address/build/i18naddress/data
> copying i18naddress/data/af.json ->
> /<>/.pybuild/cpython3_3.9_i18address/build/i18naddress/data
> copying i18naddress/data/ag.json ->
> /<>/.pybuild/cpython3_3.9_i18address/build/i18naddress/data
> copying i18naddress/data/ai.json ->
>
Bug#980600: getdp: FTBFS: ld: /usr/lib/x86_64-linux-gnu/libslepc.so: undefined reference to `MPIU_SUM'
Dear Maintainer, I tried to build your package in a sid chroot environment and no problems occurred. Please see https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=980751 Kind Regards
Bug#937194: opencaster: Python2 removal in sid/bullseye
Hi Moritz, On Fri, 29 Jan 2021, Moritz Mühlenhoff wrote: opencaster seems dead upstream, should it be removed or are you planning to port it to Python 3 yourself? I don't plan to do the porting myself, so I think at the moment it should be better removed. Thorsten
Bug#981365: linux-image-5.10.0-2-amd64: HP EliteBook x360 1040 G6 crashing since 5.10.0-1
Package: src:linux
Version: 5.10.9-1
Severity: critical
Justification: breaks the whole system
X-Debbugs-Cc: filzstift2...@gmail.com
Dear Maintainer,
since kernel 5.10.0-1 debian is very unstable on my HP EliteBook x360 1040 G6.
It freezes after some minutes or hours after boot. When it freezes i can only
move the mouse pointer but can't do anything else.
dmesg gets flooded with "retire_capture_urb: x callbacks suppressed"
messages. and sound via usb interface is crackling. Overall usb devices
work very unreliable.
I already had some "retire_capture_urb: x callbacks suppressed" messages
in older kernel version. but very rarely and the system never crashed.
Kernel version 5.9 works fine for me.
i am using a thunderbolt docking station
-- Package-specific info:
** Version:
Linux version 5.10.0-2-amd64 (debian-ker...@lists.debian.org) (gcc-10 (Debian
10.2.1-6) 10.2.1 20210110, GNU ld (GNU Binutils for Debian) 2.35.1) #1 SMP
Debian 5.10.9-1 (2021-01-20)
** Command line:
BOOT_IMAGE=/boot/vmlinuz-5.10.0-2-amd64
root=UUID=04c8fa04-e284-48d4-b385-624f3a9cb08b ro quiet
** Tainted: OE (12288)
* externally-built ("out-of-tree") module was loaded
* unsigned module was loaded
** Kernel log:
[ 50.170866] input: Unicomp Endura Pro Keyboard Consumer Control as
/devices/pci:00/:00:1c.4/:02:00.0/:03:04.0/:39:00.0/:3a:02.0/:3b:00.0/usb5/5-1/5-1.3/5-1.3.1/5-1.3.1:1.1/0003:17F6:0905.0008/input/input37
[ 50.188545] usb 6-1.3.3: New USB device found, idVendor=0bda,
idProduct=8153, bcdDevice=31.00
[ 50.188548] usb 6-1.3.3: New USB device strings: Mfr=1, Product=2,
SerialNumber=6
[ 50.188550] usb 6-1.3.3: Product: USB 10/100/1000 LAN
[ 50.188551] usb 6-1.3.3: Manufacturer: Realtek
[ 50.188553] usb 6-1.3.3: SerialNumber: 00167F690
[ 50.227862] input: Unicomp Endura Pro Keyboard System Control as
/devices/pci:00/:00:1c.4/:02:00.0/:03:04.0/:39:00.0/:3a:02.0/:3b:00.0/usb5/5-1/5-1.3/5-1.3.1/5-1.3.1:1.1/0003:17F6:0905.0008/input/input38
[ 50.227997] hid-generic 0003:17F6:0905.0008: input,hidraw3: USB HID v1.10
Mouse [Unicomp Endura Pro Keyboard ] on usb-:3b:00.0-1.3.1/input1
[ 50.239354] usbcore: registered new interface driver r8152
[ 50.247329] usbcore: registered new interface driver cdc_ether
[ 50.267791] usb 5-1.4.2: new low-speed USB device number 6 using xhci_hcd
[ 50.381520] usb 5-1.4.2: New USB device found, idVendor=1267,
idProduct=0210, bcdDevice=22.70
[ 50.381525] usb 5-1.4.2: New USB device strings: Mfr=0, Product=2,
SerialNumber=0
[ 50.381528] usb 5-1.4.2: Product: PS/2+USB Mouse
[ 50.390702] input: PS/2+USB Mouse as
/devices/pci:00/:00:1c.4/:02:00.0/:03:04.0/:39:00.0/:3a:02.0/:3b:00.0/usb5/5-1/5-1.4/5-1.4.2/5-1.4.2:1.0/0003:1267:0210.0009/input/input39
[ 50.390902] hid-generic 0003:1267:0210.0009: input,hidraw4: USB HID v1.00
Mouse [PS/2+USB Mouse] on usb-:3b:00.0-1.4.2/input0
[ 50.479769] usb 5-1.3.4: new high-speed USB device number 7 using xhci_hcd
[ 50.832189] usb 6-1.3.3: reset SuperSpeed Gen 1 USB device number 5 using
xhci_hcd
[ 50.858418] r8152 6-1.3.3:1.0: firmware: direct-loading firmware
rtl_nic/rtl8153b-2.fw
[ 50.877463] r8152 6-1.3.3:1.0: load rtl8153b-2 v1 10/23/19 successfully
[ 50.909350] r8152 6-1.3.3:1.0 eth0: v1.11.11
[ 50.936063] usb 5-1.4.3: new high-speed USB device number 8 using xhci_hcd
[ 51.035760] usb 5-1.3.4: New USB device found, idVendor=0bda,
idProduct=49a7, bcdDevice= 0.04
[ 51.035766] usb 5-1.3.4: New USB device strings: Mfr=3, Product=1,
SerialNumber=0
[ 51.035770] usb 5-1.3.4: Product: USB Audio
[ 51.035773] usb 5-1.3.4: Manufacturer: Generic
[ 51.039984] usb 5-1.4.3: New USB device found, idVendor=0424,
idProduct=2422, bcdDevice= 0.a0
[ 51.039990] usb 5-1.4.3: New USB device strings: Mfr=0, Product=0,
SerialNumber=0
[ 51.044322] hub 5-1.4.3:1.0: USB hub found
[ 51.044395] hub 5-1.4.3:1.0: 1 port detected
[ 51.055094] input: Generic USB Audio Consumer Control as
/devices/pci:00/:00:1c.4/:02:00.0/:03:04.0/:39:00.0/:3a:02.0/:3b:00.0/usb5/5-1/5-1.3/5-1.3.4/5-1.3.4:1.3/0003:0BDA:49A7.000A/input/input40
[ 51.112429] input: Generic USB Audio as
/devices/pci:00/:00:1c.4/:02:00.0/:03:04.0/:39:00.0/:3a:02.0/:3b:00.0/usb5/5-1/5-1.3/5-1.3.4/5-1.3.4:1.3/0003:0BDA:49A7.000A/input/input41
[ 51.112917] hid-generic 0003:0BDA:49A7.000A: input,hiddev0,hidraw5: USB HID
v1.11 Device [Generic USB Audio] on usb-:3b:00.0-1.3.4/input3
[ 51.123705] usb 5-1.4.4: new high-speed USB device number 9 using xhci_hcd
[ 51.225238] usb 5-1.4.4: New USB device found, idVendor=1235,
idProduct=8202, bcdDevice= 4.1b
[ 51.225242] usb 5-1.4.4: New USB device strings: Mfr=1, Product=3,
SerialNumber=0
[ 51.225245] usb 5-1.4.4: Product: Scarlett 2i2 USB
[ 51.225246] usb 5-1.4.4: Manufacturer: Focusrite
[ 51.332097] usb 5-1.4.3.1: new high-speed USB device number
Bug#981147: marked as done (loggedfs: missing dependency on fuse/fuse3 for fusermount binary)
Your message dated Fri, 29 Jan 2021 21:49:08 + with message-id and subject line Bug#981147: fixed in loggedfs 0.9+ds-3 has caused the Debian Bug report #981147, regarding loggedfs: missing dependency on fuse/fuse3 for fusermount binary 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.) -- 981147: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=981147 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: loggedfs Version: 0.9+ds-2 Severity: serious When I try to run loggedfs on a system without fuse/fuse3 installed I get an error because the fusermount binary is not found. $ dir=$(mktemp --directory tmp-XX) $ loggedfs -f `pwd`/$dir 2021-01-27 07:14:50,851 INFO [default] LoggedFS not running as a daemon 2021-01-27 07:14:50,851 INFO [default] LoggedFS starting at /home/pabs/tmp-sLfW8Zzzf3. 2021-01-27 07:14:50,851 INFO [default] chdir to /home/pabs/tmp-sLfW8Zzzf3 fuse: failed to exec fusermount: No such file or directory 2021-01-27 07:14:50,854 INFO [default] LoggedFS closing. Based on the other bug I have filed it looks like loggedfs can only use fuse not fuse3. The fuse3 package has "Provides: fuse (= 3.10.1-2)" so you will have to depend on fuse << 3 to make loggedfs work. Unfortunately fuse3 is required by other packages on my system, so adding this dependency will be annoying for me, a better option would be to make the code work with fuse3 and just depend on any fuse. -- System Information: Debian Release: bullseye/sid APT prefers testing-debug APT policy: (900, 'testing-debug'), (900, 'testing'), (800, 'unstable-debug'), (800, 'unstable'), (790, 'buildd-unstable'), (700, 'experimental-debug'), (700, 'experimental'), (690, 'buildd-experimental') Architecture: amd64 (x86_64) Kernel: Linux 5.10.0-2-amd64 (SMP w/4 CPU threads) Kernel taint flags: TAINT_FIRMWARE_WORKAROUND Locale: LANG=en_AU.utf8, LC_CTYPE=en_AU.utf8 (charmap=UTF-8), LANGUAGE=en_AU:en Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages loggedfs depends on: ii libc6 2.31-9 ii libfuse22.9.9-3 ii libgcc-s1 10.2.1-6 ii libpcre32:8.39-13 ii libstdc++6 10.2.1-6 ii libxml2 2.9.10+dfsg-6.3+b1 loggedfs recommends no packages. loggedfs suggests no packages. -- no debconf information -- bye, pabs https://wiki.debian.org/PaulWise signature.asc Description: This is a digitally signed message part --- End Message --- --- Begin Message --- Source: loggedfs Source-Version: 0.9+ds-3 Done: Stephen Kitt We believe that the bug you reported is fixed in the latest version of loggedfs, 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 981...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Stephen Kitt (supplier of updated loggedfs 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: Fri, 29 Jan 2021 22:24:38 +0100 Source: loggedfs Architecture: source Version: 0.9+ds-3 Distribution: unstable Urgency: medium Maintainer: Stephen Kitt Changed-By: Stephen Kitt Closes: 981146 981147 Changes: loggedfs (0.9+ds-3) unstable; urgency=medium . * Explicitly depend on fuse since we need fusermount, or fuse3 with support for “-o nonempty”. Closes: #981146, #981147. Checksums-Sha1: c6c6dc57133d4e89b18de78c5efd3ea6688eb584 1888 loggedfs_0.9+ds-3.dsc baf100c1e626510a71cb21fa22ed21fe1d89221a 3184 loggedfs_0.9+ds-3.debian.tar.xz d4098a2818f7499480274db7bb76b8dbb44251c3 6335 loggedfs_0.9+ds-3_source.buildinfo Checksums-Sha256: f8a18803484bf6e2e734db8a45f92bb530c66fd6d03e6b4b5e6080b35bedbbdb 1888 loggedfs_0.9+ds-3.dsc aa86c998889875def1e0077c1963e61537101f3ed617fecb434f522358bb41b6 3184 loggedfs_0.9+ds-3.debian.tar.xz a3267f8c60a290fc2714dff4678b0a6c6b45e2e22995b330efbea1c2a42e537c 6335 loggedfs_0.9+ds-3_source.buildinfo Files: 63e120365435e56b89259022c2f48894 1888 admin optional loggedfs_0.9+ds-3.dsc 496b971dc190ba6ff5b556d4d5da6155 3184 admin optional loggedfs_0.9+ds-3.debian.tar.xz f280f1bc5e427d00f488aa68baf9b59c 6335 admin optional loggedfs_0.9+ds-3_source.buildinfo -BEGIN PGP
Processed: gparted/1.2.0-1
Processing commands for cont...@bugs.debian.org: > tag 948739 + pending Bug #948739 [gparted] gparted should not mask .mount units Added tag(s) pending. > tag 950425 + pending Bug #950425 [gparted] new upstream (1.1.0) Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 948739: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=948739 950425: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=950425 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#979818: python-dlt: FTBFS in sid
control: forwarded -1 https://github.com/bmwcarit/python-dlt/issues/26 G.
Processed: Re: python-dlt: FTBFS in sid
Processing control commands: > forwarded -1 https://github.com/bmwcarit/python-dlt/issues/26 Bug #979818 [src:python-dlt] python-dlt: FTBFS in sid Set Bug forwarded-to-address to 'https://github.com/bmwcarit/python-dlt/issues/26'. -- 979818: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=979818 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#979865: m2crypto FTBFS on IPV6-only buildds
control: found -1 0.31.0-1 On 2021-01-24 23:08:27 [+0200], Adrian Bunk wrote: > > The release team considers these bugs release critical. it would be easier to enforce to have all buildds configured equally so the package does not fail on a random buildd. > > and let it migrate to > > testing. After all this bug did not first appear in 0.37.1-1, > >... > > If this is true, then the proper action would be a found indicating the > first broken version. Ah. Looking at all the ipv6 testsuite bugs I saw so far, all of them were there from the very beginning. My guess is that it isn't any different here. I reassigned it to the first upload of 31 which is in stable because 0.31.0-4+deb10u1 failed to build on amd64 for the same reason. A retry passed. > cu > Adrian Sebastian
Processed: Re: Bug#979865: m2crypto FTBFS on IPV6-only buildds
Processing control commands: > found -1 0.31.0-1 Bug #979865 [src:m2crypto] m2crypto FTBFS on IPV6-only buildds Marked as found in versions m2crypto/0.31.0-1. -- 979865: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=979865 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Re: Processed: Re: Bug#981289 closed by Debian FTP Masters (reply to Alastair McKinstry ) (Bug#981289: fixed in udunits 2.2.28-3)
Processing commands for cont...@bugs.debian.org:
> fixed 981289 2.2.28-3
Bug #981289 {Done: Alastair McKinstry } [src:udunits]
udunits breaks gnudatalanguage autopkgtest
Marked as fixed in versions udunits/2.2.28-3.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
981289: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=981289
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Processed: Re: Bug#981289 closed by Debian FTP Masters (reply to Alastair McKinstry ) (Bug#981289: fixed in udunits 2.2.28-3)
Processing control commands:
> reassign -1 src:udunits 2.2.28-2
Bug #981289 {Done: Alastair McKinstry } [udunits] udunits
breaks gnudatalanguage autopkgtest
Bug reassigned from package 'udunits' to 'src:udunits'.
No longer marked as found in versions 2.2.28-2.
No longer marked as fixed in versions udunits/2.2.28-3.
Bug #981289 {Done: Alastair McKinstry } [src:udunits]
udunits breaks gnudatalanguage autopkgtest
Marked as found in versions udunits/2.2.28-2.
> affects -1 src:gnudatalanguage
Bug #981289 {Done: Alastair McKinstry } [src:udunits]
udunits breaks gnudatalanguage autopkgtest
Added indication that 981289 affects src:gnudatalanguage
--
981289: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=981289
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#981289: closed by Debian FTP Masters (reply to Alastair McKinstry ) (Bug#981289: fixed in udunits 2.2.28-3)
Control: reassign -1 src:udunits 2.2.28-2 Control: affects -1 src:gnudatalanguage Hi, On 29-01-2021 14:09, Debian Bug Tracking System wrote: > This is an automatic notification regarding your Bug report > which was filed against the udunits package: > > #981289: udunits breaks gnudatalanguage autopkgtest > > It has been closed by Debian FTP Masters > (reply to Alastair McKinstry ). Unfortunately, the bts doesn't handle bugs assigned to two packages perfectly yet. Updating the meta info to reflect the current understanding. Paul OpenPGP_signature Description: OpenPGP digital signature
Bug#937194: opencaster: Python2 removal in sid/bullseye
Am Fri, Aug 30, 2019 at 07:29:17AM + schrieb Matthias Klose: > Package: src:opencaster > Version: 3.2.2+dfsg-1.1 > Severity: normal > Tags: sid bullseye > User: debian-pyt...@lists.debian.org > Usertags: py2removal > > Python2 becomes end-of-live upstream, and Debian aims to remove > Python2 from the distribution, as discussed in > https://lists.debian.org/debian-python/2019/07/msg00080.html Hi Thorsten, opencaster seems dead upstream, should it be removed or are you planning to port it to Python 3 yourself? Cheers, Moritz
Processed: merge GCC issue
Processing commands for cont...@bugs.debian.org: > reassign 981174 src:gcc-10 Bug #981174 [gcc-10] gcc-10 in testing is broken, cannot build linux kernel Bug reassigned from package 'gcc-10' to 'src:gcc-10'. No longer marked as found in versions gcc-10/10.2.1-6. Ignoring request to alter fixed versions of bug #981174 to the same values previously set > forcemerge 980609 981174 Bug #980609 [src:gcc-10] missing i386-cpuinfo.h Bug #981174 [src:gcc-10] gcc-10 in testing is broken, cannot build linux kernel Severity set to 'serious' from 'normal' Added indication that 981174 affects src:odb Added tag(s) bullseye, sid, pending, and ftbfs. Merged 980609 981174 > thanks Stopping processing here. Please contact me if you need assistance. -- 980609: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=980609 981174: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=981174 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#980645: marked as done (leiningen-clojure: FTBFS: Cannot access central (https://repo1.maven.org/maven2/) in offline mode and the artifact org.slf4j:slf4j-nop:jar:1.7.25 has not been downloaded fr
Your message dated Fri, 29 Jan 2021 19:03:50 +
with message-id
and subject line Bug#980645: fixed in leiningen-clojure 2.9.1-4
has caused the Debian Bug report #980645,
regarding leiningen-clojure: FTBFS: Cannot access central
(https://repo1.maven.org/maven2/) in offline mode and the artifact
org.slf4j:slf4j-nop:jar:1.7.25 has not been downloaded from it before.
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.)
--
980645: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=980645
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: leiningen-clojure
Version: 2.9.1-3
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20210120 ftbfs-bullseye
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> cd leiningen-core && lein bootstrap
> Leiningen's classpath: :/usr/share/java/leiningen-2.9.1.jar
> Applying task [with-profile base do install, classpath .lein-bootstrap] to []
> Applying task do to (install, classpath .lein-bootstrap)
> Applying task install to []
> Cannot access central (https://repo1.maven.org/maven2/) in offline mode and
> the artifact org.slf4j:slf4j-nop:jar:1.7.25 has not been downloaded from it
> before.
> Cannot access clojars (https://repo.clojars.org/) in offline mode and the
> artifact org.slf4j:slf4j-nop:jar:1.7.25 has not been downloaded from it
> before.
> This could be due to a typo in :dependencies, file system permissions, or
> network issues.
> If you are behind a proxy, try setting the 'http_proxy' environment variable.
> Error encountered performing task 'do' with profile(s): 'base'
> clojure.lang.ExceptionInfo: Could not resolve dependencies {:suppress-msg
> true, :exit-code 1}
> at
> leiningen.core.classpath$get_dependencies_STAR_.invokeStatic(classpath.clj:312)
> at
> leiningen.core.classpath$get_dependencies_STAR_.invoke(classpath.clj:266)
> at clojure.lang.AFn.applyToHelper(AFn.java:165)
> at clojure.lang.AFn.applyTo(AFn.java:144)
> at clojure.core$apply.invokeStatic(core.clj:665)
> at clojure.core$memoize$fn__6877.doInvoke(core.clj:6353)
> at clojure.lang.RestFn.invoke(RestFn.java:457)
> at
> leiningen.core.classpath$get_dependencies$fn__6444.invoke(classpath.clj:333)
> at
> leiningen.core.classpath$get_dependencies.invokeStatic(classpath.clj:331)
> at leiningen.core.classpath$get_dependencies.doInvoke(classpath.clj:325)
> at clojure.lang.RestFn.invoke(RestFn.java:445)
> at clojure.lang.AFn.applyToHelper(AFn.java:160)
> at clojure.lang.RestFn.applyTo(RestFn.java:132)
> at clojure.core$apply.invokeStatic(core.clj:671)
> at clojure.core$apply.invoke(core.clj:660)
> at
> leiningen.core.classpath$resolve_managed_dependencies.invokeStatic(classpath.clj:444)
> at
> leiningen.core.classpath$resolve_managed_dependencies.doInvoke(classpath.clj:431)
> at clojure.lang.RestFn.invoke(RestFn.java:445)
> at leiningen.core.eval$prep.invokeStatic(eval.clj:85)
> at leiningen.core.eval$prep.invoke(eval.clj:73)
> at leiningen.jar$build_jar.invokeStatic(jar.clj:286)
> at leiningen.jar$build_jar.invoke(jar.clj:283)
> at leiningen.jar$main_jar.invokeStatic(jar.clj:295)
> at leiningen.jar$main_jar.invoke(jar.clj:291)
> at leiningen.jar$jar.invokeStatic(jar.clj:346)
> at leiningen.jar$jar.invoke(jar.clj:328)
> at leiningen.jar$jar.invokeStatic(jar.clj:348)
> at leiningen.jar$jar.invoke(jar.clj:328)
> at leiningen.install$install.invokeStatic(install.clj:21)
> at leiningen.install$install.invoke(install.clj:12)
> at clojure.lang.AFn.applyToHelper(AFn.java:154)
> at clojure.lang.AFn.applyTo(AFn.java:144)
> at clojure.lang.Var.applyTo(Var.java:705)
> at clojure.core$apply.invokeStatic(core.clj:667)
> at clojure.core$apply.invoke(core.clj:660)
> at leiningen.core.main$partial_task$fn__6931.doInvoke(main.clj:284)
> at clojure.lang.RestFn.invoke(RestFn.java:410)
> at clojure.lang.AFn.applyToHelper(AFn.java:154)
> at clojure.lang.RestFn.applyTo(RestFn.java:132)
> at clojure.lang.AFunction$1.doInvoke(AFunction.java:31)
> at clojure.lang.RestFn.applyTo(RestFn.java:137)
> at clojure.core$apply.invokeStatic(core.clj:667)
> at clojure.core$apply.invoke(core.clj:660)
> at leiningen.core.main$apply_task.invokeStatic(main.clj:334)
> at
Bug#980809: log on s390x
On request of Graham I ran the autopkgtest on 390x manually to speed up the results. Please find the output attached. Paul r-cran-glmmtmb@s390x.tar.gz Description: application/gzip OpenPGP_signature Description: OpenPGP digital signature
Bug#974996: Raising severity and offering to NMU package
tis 2021-01-26 klockan 19:25 +0100 skrev Bruno Kleinert: > On Mon, 23 Nov 2020 20:15:52 +0100 Simon Josefsson < > si...@josefsson.org> wrote: > > severity 975030 serious > > severity 974997 serious > > severity 974996 serious > > severity 974995 serious > > severity 974994 serious > > severity 974993 serious > > thanks > > > > It was suggested to me on IRC that the severity of this could be > > serious because the build-dependency libidn2-0-dev is going to be > > removed from Debian. I'm volunteering to do NMU these packages to > fix > > the bug, and could look into that in a couple of weeks -- if you > give > > me permission to do it before, I'd start directly. If I'm mistaken > > that this is not a valid justification for a serious bug, downgrade > the > > bug and let me know, as I'm not sure what the best way to get an > > obsolete deprecated transition package removed from Debian when > build- > > deps remain. > > > > /Simon > > > > Hi, > > looking at the RC bugs list I stumbled across this one and added a > merge request on salsa: > https://salsa.debian.org/debian/curl/-/merge_requests/9 Thank you! I am beginning to think that we are too late in the process for bullseye to see this completed though, but doing NMU's to fix this would indeed be welcome -- I won't have time in the next few weeks for this though, so volunteers welcome. /Simon signature.asc Description: This is a digitally signed message part
Bug#979765: this problem is realted to CPU
I can confirm, that the bug occurs on HP T5550 only. On very similar HP T510 it does not - and since both computers share same motherboard, it must be the CPU. So the problem occurs only on VIA Nano u3500 and does not on VIA Eden X2 U4200. What other informations can I gather, to help solve this issue? Thanks, Kazimierz
Processed: Same problem here
Processing commands for cont...@bugs.debian.org: > severity 973474 grave Bug #973474 [gnome] gnome: Unable to log back in in after screen lock Severity set to 'grave' from 'important' > thanks Stopping processing here. Please contact me if you need assistance. -- 973474: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=973474 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#976132: marked as done (paraview: autopkgtest regression in testing)
Your message dated Fri, 29 Jan 2021 17:04:11 + with message-id and subject line Bug#976132: fixed in paraview 5.9.0-1 has caused the Debian Bug report #976132, regarding paraview: autopkgtest regression in testing 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.) -- 976132: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=976132 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: paraview Version: 5.7.0-5 Severity: serious Tags: sid bullseye X-Debbugs-CC: debian...@lists.debian.org User: debian...@lists.debian.org Usertags: regression Hi Maintainer The autopkgtests of paraview recently started to fail in testing [1]. I've copied what I hope is the relevant part of the log below. Regards Graham [1] https://ci.debian.net/packages/p/paraview/testing/amd64/ autopkgtest [05:36:15]: test paraviewtest.py: [--- bash: line 1: 7140 Segmentation fault /tmp/autopkgtest-lxc._fwfat78/downtmp/build.v9h/src/debian/tests/paraviewtest.py 2> >(tee -a /tmp/autopkgtest-lxc._fwfat78/downtmp/paraviewtest.py-stderr >&2) > >(tee -a /tmp/autopkgtest-lxc._fwfat78/downtmp/paraviewtest.py-stdout) autopkgtest [05:36:16]: test paraviewtest.py: ---] autopkgtest [05:36:16]: test paraviewtest.py: - - - - - - - - - - results - - - - - - - - - - paraviewtest.py FAIL non-zero exit status 139 --- End Message --- --- Begin Message --- Source: paraview Source-Version: 5.9.0-1 Done: Alastair McKinstry We believe that the bug you reported is fixed in the latest version of paraview, 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 976...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Alastair McKinstry (supplier of updated paraview 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, 29 Jan 2021 09:53:39 + Source: paraview Architecture: source Version: 5.9.0-1 Distribution: unstable Urgency: medium Maintainer: Debian Science Team Changed-By: Alastair McKinstry Closes: 893735 959387 976128 976132 Changes: paraview (5.9.0-1) unstable; urgency=medium . * New upstream release. Closes: #976128, #959387, #976132 * Ack. bug fixed/obsoleted by new version: Closes: #893735 * Re-enable gl2ps * use Parallel HDF5 * Build-dep on libopengl-dev Checksums-Sha1: 146f1187ba7f84dee6723bdc458782e45f2d7c57 3087 paraview_5.9.0-1.dsc dc6911225d6ebcd4b494b9734ab6ffad95a9015f 59898372 paraview_5.9.0.orig.tar.xz 5c92b08a0a692d2b1d8be6d961241e24cebae9f0 30700 paraview_5.9.0-1.debian.tar.xz Checksums-Sha256: 4570e9ac7911afc2641ebaf36c7ee3b3825f0b9097f1d31688aafe0919b5dc5d 3087 paraview_5.9.0-1.dsc cfba8df92d187df57e1ac030f26ccba981e7200e37adc0ac0a67190d2ec22801 59898372 paraview_5.9.0.orig.tar.xz 1503b5573a7ee7431b42a81e732766814ac24bd37174675d8e71b4548d853899 30700 paraview_5.9.0-1.debian.tar.xz Files: 4576c99a691f09257149466bcef06606 3087 science optional paraview_5.9.0-1.dsc bb20770437893b91dd769e6d51d87449 59898372 science optional paraview_5.9.0.orig.tar.xz 0b90766ca878741d0af568e1af09de0f 30700 science optional paraview_5.9.0-1.debian.tar.xz -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEEgjg86RZbNHx4cIGiy+a7Tl2a06UFAmAUOdEACgkQy+a7Tl2a 06Vvrw//cFGjKylDwuo6j0PPw3kPGRPqAXNSGby1j+GNLYfFiH8fuO5nRSsweZTC apU3tdIDdkiYLSAW/5l8DUIRDZMtKg3azAXW9TRg/gfPH6tlYdVpOrybeZpocpg3 axzREMU77NscjRf14E/9rSDhU+AHQLBNjR2ygFVGIFCBlv8DWWGHKnF84ZisTC+g fhbgkEoB7JN/Gpv/qlJORJ8XZnCfhkWBwV8gStaCGFL8LYDS21vLuU+O85ozYv02 MFr5HSXK4ObFYdJY5hzw59ry7zGyM1j6fWv6dnem7m5U3OOOlfTnqlAx0+V1ing9 zp8qfZUzBcrPTWYYMLJIU8C1MZSFaj0lLYkcwzuAVQU12pHHBS6C5ZRtmGG6pZrq lLZKZUvDqv8gvD+xDlpGHGuK6POCweJR6joFl9UQ2+MzvXCGqB/Zj+keQdugWgit 6MrMXwJLFDoLDIBQrl9icxzjwx9zcvzLrA5DM5VSfuT36FLKVgN019sgrUDECXsP q4NItTsGFaqpzrV3g8K7OspVssMch6j95hSE+sqIsh/Gm7u6VxT1M1K74VEtE3aX diSts7kioKAu2YIhcsjFW/hbjP+y1RmoT+oYfCUFW2RVB00+rApOMv/rMBVmbfJ5 vh5TdUVXVlKAq65xW8aL7YryCs1ojhHr2B35D227vWrQ5BCJsc0= =48oI -END PGP SIGNATURE End Message ---
Bug#975030: marked as done (Please build-depend on libidn2-dev instead of obsolete transition package libidn2-0-dev)
Your message dated Fri, 29 Jan 2021 17:04:30 + with message-id and subject line Bug#975030: fixed in wget2 1.99.1-2.2 has caused the Debian Bug report #975030, regarding Please build-depend on libidn2-dev instead of obsolete transition package libidn2-0-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.) -- 975030: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=975030 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: wget2 Version: 1.99.1-2.1 Tags: patch The package libidn2-0-dev was obsoleted back in 2017, and replacing it with libidn2-dev should work fine. It would be great if this would be fixed before the next Debian release, so we can finally remove the libidn2-0-dev package from the archive. /Simon PS. The version controlled sources linked from the tracker doesn't seem to contain the latest Debian uploads, is the link really correct? If I would have found the version controlled source, I would have provided a patch. signature.asc Description: This is a digitally signed message part --- End Message --- --- Begin Message --- Source: wget2 Source-Version: 1.99.1-2.2 Done: Boyuan Yang We believe that the bug you reported is fixed in the latest version of wget2, 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 975...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Boyuan Yang (supplier of updated wget2 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, 26 Jan 2021 11:21:32 -0500 Source: wget2 Architecture: source Version: 1.99.1-2.2 Distribution: unstable Urgency: high Maintainer: Noël Köthe Changed-By: Boyuan Yang Closes: 975030 Changes: wget2 (1.99.1-2.2) unstable; urgency=high . * Non-maintainer upload. * Rebuild against new gnulib snapshot (20210102). * debian/control: replace old build-dependency libidn2-0-dev with libidn2-dev. (Closes: #975030) Checksums-Sha1: 1c5b443820edb9a8f8ebe1b7e86e73762416716b 2383 wget2_1.99.1-2.2.dsc 31a9cd8f0032f7fdb12e5024e6a1b8ec32017a57 2660538 wget2_1.99.1.orig.tar.gz 22822845e4e82a2651433f81b1aaf851b8bff795 833 wget2_1.99.1.orig.tar.gz.asc 88f3c58ebde496c206921c804656a4467945423a 3736 wget2_1.99.1-2.2.debian.tar.xz af3e836f7f8e7168fd32553f17712e873d0db4ee 10555 wget2_1.99.1-2.2_amd64.buildinfo Checksums-Sha256: 99c4545c64317fb43ea75c580cfd0eb37a54da1aa804f1b3082cf0e94cd74597 2383 wget2_1.99.1-2.2.dsc 8d9b0b0897ff9623169db47c656d09007677f8d51de5f5cd3652258aab8b4dde 2660538 wget2_1.99.1.orig.tar.gz b97b0d352a56d2f2b5984ef49eb25aaca7ed01abb5152cb45e04d99399153006 833 wget2_1.99.1.orig.tar.gz.asc 24a1574b34f710b4d9b657eea6e1d023dbec71f6eea473d29fe5f059bce1aa06 3736 wget2_1.99.1-2.2.debian.tar.xz 0aefd0e6f2ef7a97431fd2cef2c1f6420321bb53afaca87abff8ab4a853b8b6e 10555 wget2_1.99.1-2.2_amd64.buildinfo Files: 6969d4250cea123147babd2fabf723e0 2383 web optional wget2_1.99.1-2.2.dsc 1a5ce44995f0cc55222ae75d7c92dd1e 2660538 web optional wget2_1.99.1.orig.tar.gz 2390feacaa33f7bac57199875757718e 833 web optional wget2_1.99.1.orig.tar.gz.asc 35bd138640882b3fe047b0468b54a4cb 3736 web optional wget2_1.99.1-2.2.debian.tar.xz c5d1b2c16a2439b37fbde1ce1a2fc6c7 10555 web optional wget2_1.99.1-2.2_amd64.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEfncpR22H1vEdkazLwpPntGGCWs4FAmAQQn4ACgkQwpPntGGC Ws7mYhAAjr6yBUgbGFGs4pCC8Wg0b0pn2qPAfyEn/oQIfyddeQEhQP5Fiftn6N3g Whn8K8H3v71LoFHkdAh89+A0pmINCqZn210i3Lf2J2+ZnUrIWpx2R9Cbeq4iYiOo tdpHVmlD3Cyi0WrUqasNeWc67FyMNwGtyinpIrg2wZnz0loz+TOfKH9JZz1Y4k24 G/a91vzZSnvMaUK9GuSnatL+GDI93UOZnllzvKQ/skUMgtamUlaSOYtTYHc/itU0 0AcNHdnoSK6Zi8VtFRHYPl0XHQJEefoyKzE11g8hgoXU9yUrl0JjOvp6hqQTaZIl KUgC3jVYTfwDzloQ+FVcJdsQzQUaTND/+QNiXz++Ha7raa2WbuK+PJ0Wr/Ev+O6j ncDyxvGUqy2q0Vd+yr5n1pYxxjA8oZdo8BEPAuBPB2klg4fOL+BvkWgtwcID61lD vPirRaiIzDJNzZX6zakNoTsc0B9d4KLm7k2Pk9/ima6dg3RjDz0dxzkLYkyC3kth aqTf1OFCZC8Vti2a2qdoumGbDvl/qpiS26Zk5j8jMW6mK55VUMLB/Ma7yCCJtLXF itZr0M0OQZovezjwLAzMoNOrdr49i3vdgsTdlBt/2xP3cm38Fgvz+aVK7YLHo+Z1 iV/q5gYxCEaUd8zFuaFTYt7OWYq3tLsjhRi7zoYkzybxw/CV24Y= =kZNj -END PGP SIGNATURE End Message ---
Bug#981342: mpich: autopkgtest failure on s390x
Source: mpich Version: 3.4-4 Severity: serious X-Debbugs-CC: debian...@lists.debian.org User: debian...@lists.debian.org Usertags: regression Hi Maintainer Since the upload of mpich 3.4-4, its own autopkgtests have been failing on s390x [1] and continue to fail in the same way with 3.4.1-1. I've copied what I hope is the relevant part of the log below. Regards Graham [1] https://ci.debian.net/packages/m/mpich/unstable/s390x/ autopkgtest [21:55:17]: test hello1: [--- Abort(1615247) on node 0 (rank 0 in comm 0): Fatal error in PMPI_Init: Other MPI error, error stack: MPIR_Init_thread(152)...: MPID_Init(597)..: MPIDI_OFI_mpi_init_hook(689): addr_exchange_root_vni(1931): OFI get endpoint name failed (ofi_init.c:1931:addr_exchange_root_vni:Provided buffer is too small) autopkgtest [21:55:18]: test hello1: ---] hello1 FAIL non-zero exit status 143 autopkgtest [21:55:18]: test hello1: - - - - - - - - - - results - - - - - - - - - - autopkgtest [21:55:18]: test hello1: - - - - - - - - - - stderr - - - - - - - - - - Abort(1615247) on node 0 (rank 0 in comm 0): Fatal error in PMPI_Init: Other MPI error, error stack: MPIR_Init_thread(152)...: MPID_Init(597)..: MPIDI_OFI_mpi_init_hook(689): addr_exchange_root_vni(1931): OFI get endpoint name failed (ofi_init.c:1931:addr_exchange_root_vni:Provided buffer is too small)
Bug#972914: marked as done (pyhst2 ftbfs with python3.9)
Your message dated Fri, 29 Jan 2021 15:19:20 + with message-id and subject line Bug#972914: fixed in pyhst2 2020c-1 has caused the Debian Bug report #972914, regarding pyhst2 ftbfs with python3.9 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 972914: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=972914 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:pyhst2 Version: 2020a-3 Severity: serious Tags: sid bullseye ftbfs User: debian-pyt...@lists.debian.org Usertags: python3.9 pyhst2 ftbfs with python3.9; to reproduce, you can use the repositories found at: deb [trusted=yes] http://people.debian.org/~doko/tmp/python3.9 ./ deb [trusted=yes] http://people.debian.org/~ginggs/python3.9-repo ./ see https://people.debian.org/~ginggs/python3.9-default/pyhst2_2020a-3build1_amd64-2020-10-25T06:41:37Z.build [...] dh build --with python3 --buildsystem=pybuild dh_update_autotools_config -O--buildsystem=pybuild dh_autoreconf -O--buildsystem=pybuild dh_auto_configure -O--buildsystem=pybuild I: pybuild base:217: python3.8 setup.py config running config I: pybuild base:217: python3.9 setup.py config running config dh_auto_build -O--buildsystem=pybuild I: pybuild base:217: /usr/bin/python3.8 setup.py build running build running build_py creating /<>/.pybuild/cpython3_3.8_pyhst2/build/PyHST2_2019b copying PyHST/congrid.py -> /<>/.pybuild/cpython3_3.8_pyhst2/build/PyHST2_2019b copying PyHST/combina.py -> /<>/.pybuild/cpython3_3.8_pyhst2/build/PyHST2_2019b copying PyHST/phasesimple.py -> /<>/.pybuild/cpython3_3.8_pyhst2/build/PyHST2_2019b copying PyHST/phase.py -> /<>/.pybuild/cpython3_3.8_pyhst2/build/PyHST2_2019b copying PyHST/Control.py -> /<>/.pybuild/cpython3_3.8_pyhst2/build/PyHST2_2019b copying PyHST/pyhst_segment.py -> /<>/.pybuild/cpython3_3.8_pyhst2/build/PyHST2_2019b copying PyHST/getSysOutput.py -> /<>/.pybuild/cpython3_3.8_pyhst2/build/PyHST2_2019b copying PyHST/string_six.py -> /<>/.pybuild/cpython3_3.8_pyhst2/build/PyHST2_2019b copying PyHST/PyHST.py -> /<>/.pybuild/cpython3_3.8_pyhst2/build/PyHST2_2019b copying PyHST/NNFBPTrain.py -> /<>/.pybuild/cpython3_3.8_pyhst2/build/PyHST2_2019b copying PyHST/pyhst_jp2edf.py -> /<>/.pybuild/cpython3_3.8_pyhst2/build/PyHST2_2019b copying PyHST/setCpuSet.py -> /<>/.pybuild/cpython3_3.8_pyhst2/build/PyHST2_2019b copying PyHST/tomography.py -> /<>/.pybuild/cpython3_3.8_pyhst2/build/PyHST2_2019b copying PyHST/__init__.py -> /<>/.pybuild/cpython3_3.8_pyhst2/build/PyHST2_2019b copying PyHST/getCpuSetRange.py -> /<>/.pybuild/cpython3_3.8_pyhst2/build/PyHST2_2019b copying PyHST/pyhst_unsharp3D_.py -> /<>/.pybuild/cpython3_3.8_pyhst2/build/PyHST2_2019b copying PyHST/pyhst_.py -> /<>/.pybuild/cpython3_3.8_pyhst2/build/PyHST2_2019b copying PyHST/EdfFile.py -> /<>/.pybuild/cpython3_3.8_pyhst2/build/PyHST2_2019b copying PyHST/LTSparsePrep.py -> /<>/.pybuild/cpython3_3.8_pyhst2/build/PyHST2_2019b copying PyHST/sirtfilter.py -> /<>/.pybuild/cpython3_3.8_pyhst2/build/PyHST2_2019b copying PyHST/Parameters_module.py -> /<>/.pybuild/cpython3_3.8_pyhst2/build/PyHST2_2019b creating /<>/.pybuild/cpython3_3.8_pyhst2/build/PyHST2_2019b/test copying PyHST/test/test_all.py -> /<>/.pybuild/cpython3_3.8_pyhst2/build/PyHST2_2019b/test copying PyHST/test/stop_test_integrate.py -> /<>/.pybuild/cpython3_3.8_pyhst2/build/PyHST2_2019b/test copying PyHST/test/__init__.py -> /<>/.pybuild/cpython3_3.8_pyhst2/build/PyHST2_2019b/test copying PyHST/test/test_dummy.py -> /<>/.pybuild/cpython3_3.8_pyhst2/build/PyHST2_2019b/test copying PyHST/test/utilstest.py -> /<>/.pybuild/cpython3_3.8_pyhst2/build/PyHST2_2019b/test copying PyHST/test/test_crayon.py -> /<>/.pybuild/cpython3_3.8_pyhst2/build/PyHST2_2019b/test creating /<>/.pybuild/cpython3_3.8_pyhst2/build/PyHST2_2019b/third_party copying PyHST/third_party/setup.py -> /<>/.pybuild/cpython3_3.8_pyhst2/build/PyHST2_2019b/third_party copying PyHST/third_party/enum.py -> /<>/.pybuild/cpython3_3.8_pyhst2/build/PyHST2_2019b/third_party copying PyHST/third_party/transformations.py -> /<>/.pybuild/cpython3_3.8_pyhst2/build/PyHST2_2019b/third_party copying PyHST/third_party/__init__.py -> /<>/.pybuild/cpython3_3.8_pyhst2/build/PyHST2_2019b/third_party copying PyHST/third_party/six.py -> /<>/.pybuild/cpython3_3.8_pyhst2/build/PyHST2_2019b/third_party running build_ext cythoning PyHST/segment/segment_cy.pyx to PyHST/segment/segment_cy.cpp building 'PyHST2_2019b.Cspace' extension Warning: Can't read registry to find the necessary compiler setting Make sure that Python modules winreg, win32api or win32con are installed.
Bug#968318: marked as done (pyhst2: FTBFS with CUDA 11: Unsupported gpu architecture 'compute_30')
Your message dated Fri, 29 Jan 2021 15:19:20 + with message-id and subject line Bug#968318: fixed in pyhst2 2020c-1 has caused the Debian Bug report #968318, regarding pyhst2: FTBFS with CUDA 11: Unsupported gpu architecture 'compute_30' 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.) -- 968318: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=968318 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: pyhst2 Version: 2020a-1 Severity: important Tags: ftbfs Justification: fails to build from source Hi, pyhst2 FTBFS with CUDA 11 in experimental: dh_auto_build -O--buildsystem=pybuild I: pybuild base:217: /usr/bin/python3 setup.py build running build running build_ext building 'PyHST2_2019b/libgputomo' extension Warning: Can't read registry to find the necessary compiler setting Make sure that Python modules winreg, win32api or win32con are installed. C compiler: x86_64-linux-gnu-gcc -pthread -Wno-unused-result -Wsign-compare -DNDEBUG -g -fwrapv -O2 -Wall -g -fstack-protector-strong -Wformat -Werror=format-security -g -fwrapv -O2 -g -O2 -fdebug-prefix-map=/build/pyhst2-2020a=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC creating build creating build/temp.linux-x86_64-3.8 creating build/temp.linux-x86_64-3.8/PyHST creating build/temp.linux-x86_64-3.8/PyHST/Cspace creating build/temp.linux-x86_64-3.8/PyHST/Cspace/pdwt creating build/temp.linux-x86_64-3.8/PyHST/Cspace/pdwt/src compile options: '-I/usr/lib/python3/dist-packages/numpy/core/include -I/usr/include -IPyHST/Cspace -I/usr/include/hdf5/serial/ -I/usr/include/python3.8 -c' extra options: 'gcc nvcc' nvcc: PyHST/Cspace/pdwt/src/wt.cu nvcc: PyHST/Cspace/pdwt/src/common.cu nvcc: PyHST/Cspace/pdwt/src/utils.cu nvcc: PyHST/Cspace/pdwt/src/nonseparable.cu nvcc: PyHST/Cspace/pdwt/src/separable.cu nvcc: PyHST/Cspace/pdwt/src/haar.cu nvcc fatal : Unsupported gpu architecture 'compute_30' nvcc fatal : Unsupported gpu architecture 'compute_30' mpicc: PyHST/Cspace/pdwt/src/filters.cpp nvcc fatal : Unsupported gpu architecture 'compute_30' nvcc: PyHST/Cspace/gputomo.cu nvcc fatal : Unsupported gpu architecture 'compute_30' nvcc fatal : Unsupported gpu architecture 'compute_30' nvcc fatal : Unsupported gpu architecture 'compute_30' nvcc fatal : Unsupported gpu architecture 'compute_30' nvcc: PyHST/Cspace/cudamedianfilter.cu nvcc: PyHST/Cspace/chambollepock.cu nvcc: PyHST/Cspace/wavelets.cu nvcc: PyHST/Cspace/sinofilters.cu nvcc fatal : Unsupported gpu architecture 'compute_30' nvcc fatal : Unsupported gpu architecture 'compute_30' nvcc fatal : Unsupported gpu architecture 'compute_30' nvcc fatal : Unsupported gpu architecture 'compute_30' error: Command "/usr/bin/nvcc -I/usr/lib/python3/dist-packages/numpy/core/include -I/usr/include -IPyHST/Cspace -I/usr/include/hdf5/serial/ -I/usr/include/python3.8 -c PyHST/Cspace/pdwt/src/common.cu -o build/temp.linux-x86_64-3.8/PyHST/Cspace/pdwt/src/common.o -gencode arch=compute_30,code=compute_30 -gencode arch=compute_50,code=compute_50 --compiler-options -fPIC -O3 -g -D_FORCE_INLINES" failed with exit status 1 E: pybuild pybuild:352: build: plugin distutils failed with: exit code=1: /usr/bin/python3 setup.py build dh_auto_build: error: pybuild --build returned exit code 13 make: *** [debian/rules:9: build] Error 25 Andreas --- End Message --- --- Begin Message --- Source: pyhst2 Source-Version: 2020c-1 Done: Picca Frédéric-Emmanuel We believe that the bug you reported is fixed in the latest version of pyhst2, 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 968...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Picca Frédéric-Emmanuel (supplier of updated pyhst2 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: Fri, 29 Jan 2021 15:14:00 +0100 Binary: python3-pyhst2-cuda python3-pyhst2-cuda-dbgsym Source: pyhst2 Architecture: amd64 source Version: 2020c-1 Distribution: unstable Urgency: medium Maintainer: Debian Science Maintainers Changed-By: Picca Frédéric-Emmanuel Closes: 968318 972914 Description:
Bug#981336: libgcrypt20: Version 1.9.0 (Debian experimental) know to be broken
Package: libgcrypt20 Version: 1.9.0-1 Severity: serious Tags: upstream Justification: maintainer's opinion https://lists.gnupg.org/pipermail/gcrypt-devel/2021-January/005086.html
Bug#948739: Bug #948739: gparted should not mask .mount units
John Paul Adrian Glaubitz writes: > Hello! > > It looks like this particular issue has been fixed in gparted 1.2.0 which > was just released a few days ago [1]: > >> - Don't try to mask non-existent Systemd \xe2\x97\x8f.service (#129, !64) > > Might be an idea to update gparted to version 1.2.0 before the Bullseye freeze > which is coming in Mid-February [2]. Thanks... on it.
Processed: affects 981296, found 981300 in 1.5.2-2
Processing commands for cont...@bugs.debian.org: > affects 981296 + src:node-ws Bug #981296 [nodejs] nodejs: missing ts definitions Added indication that 981296 affects src:node-ws > found 981300 1.5.2-2 Bug #981300 [arduino-mk] arduino-mk: needs to depend on arduino 2:1.8.13+dfsg1-1 Marked as found in versions arduino-mk/1.5.2-2. > thanks Stopping processing here. Please contact me if you need assistance. -- 981296: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=981296 981300: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=981300 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Linking bug with MR
Processing control commands: > tag -1 patch Bug #971946 [libdebian-installer] libdebian-installer: READSIZE size insufficient for cdebootstrap to build sid/unstable from buster/stable environment Added tag(s) patch. > forwarded -1 > https://salsa.debian.org/installer-team/libdebian-installer/-/merge_requests/2 Bug #971946 [libdebian-installer] libdebian-installer: READSIZE size insufficient for cdebootstrap to build sid/unstable from buster/stable environment Set Bug forwarded-to-address to 'https://salsa.debian.org/installer-team/libdebian-installer/-/merge_requests/2'. -- 971946: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=971946 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#971946: Linking bug with MR
Control: tag -1 patch Control: forwarded -1 https://salsa.debian.org/installer-team/libdebian-installer/-/merge_requests/2 signature.asc Description: This is a digitally signed message part.
Processed: db5.3: diff for NMU version 5.3.28+dfsg1-0.7
Processing control commands: > tags 957124 + patch Bug #957124 [src:db5.3] db5.3: ftbfs with GCC-10 Added tag(s) patch. > tags 957124 + pending Bug #957124 [src:db5.3] db5.3: ftbfs with GCC-10 Added tag(s) pending. -- 957124: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=957124 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#957124: db5.3: diff for NMU version 5.3.28+dfsg1-0.7
Control: tags 957124 + patch
Control: tags 957124 + pending
Dear maintainer,
I've prepared an NMU for db5.3 (versioned as 5.3.28+dfsg1-0.7) and
uploaded it to DELAYED/7. Please feel free to tell me if I
should delay it longer.
Regards.
diff -Nru db5.3-5.3.28+dfsg1/debian/changelog db5.3-5.3.28+dfsg1/debian/changelog
--- db5.3-5.3.28+dfsg1/debian/changelog 2019-03-12 05:16:54.0 +0100
+++ db5.3-5.3.28+dfsg1/debian/changelog 2021-01-29 13:27:20.0 +0100
@@ -1,3 +1,10 @@
+db5.3 (5.3.28+dfsg1-0.7) unstable; urgency=medium
+
+ * Non-maintainer upload.
+ * Add patches for GCC 10 (Closes: #957124)
+
+ -- Jochen Sprickerhof Fri, 29 Jan 2021 13:27:20 +0100
+
db5.3 (5.3.28+dfsg1-0.6) unstable; urgency=medium
* Non-maintainer upload.
diff -Nru db5.3-5.3.28+dfsg1/debian/patches/0012-Don-t-expo-progname-symbol.patch db5.3-5.3.28+dfsg1/debian/patches/0012-Don-t-expo-progname-symbol.patch
--- db5.3-5.3.28+dfsg1/debian/patches/0012-Don-t-expo-progname-symbol.patch 1970-01-01 01:00:00.0 +0100
+++ db5.3-5.3.28+dfsg1/debian/patches/0012-Don-t-expo-progname-symbol.patch 2021-01-29 12:45:00.0 +0100
@@ -0,0 +1,32 @@
+From: Jochen Sprickerhof
+Date: Sat, 23 Jan 2021 19:37:02 +0100
+Subject: Don't expo progname symbol
+
+Fixes:
+
+/usr/bin/ld: .libs/TestDbTuner.o:(.data.rel.local+0x0): multiple definition of `progname'; .libs/Runner.o:(.bss+0x0): first defined here
+---
+ test/c/suites/TestDbTuner.c | 3 +--
+ 1 file changed, 1 insertion(+), 2 deletions(-)
+
+diff --git a/test/c/suites/TestDbTuner.c b/test/c/suites/TestDbTuner.c
+index 21954c2..b84bfd8 100644
+--- a/test/c/suites/TestDbTuner.c
b/test/c/suites/TestDbTuner.c
+@@ -33,7 +33,6 @@ int open_db(DB_ENV **, DB **, char *, char *, u_int32_t, int);
+ int run_test(CuTest *, u_int32_t, int, int, int, int, int);
+ int store_db(DB *, int, int, int, int);
+
+-const char *progname = "TestDbTuner";
+ int total_cases, success_cases;
+
+ int TestDbTuner(CuTest *ct) {
+@@ -201,7 +200,7 @@ open_db(dbenvp, dbpp, dbname, home, pgsize, duptype)
+ *dbenvp = dbenv;
+
+ dbenv->set_errfile(dbenv, stderr);
+- dbenv->set_errpfx(dbenv, progname);
++ dbenv->set_errpfx(dbenv, "TestDbTuner");
+
+ if ((ret =
+ dbenv->set_cachesize(dbenv, (u_int32_t)0,
diff -Nru db5.3-5.3.28+dfsg1/debian/patches/0014-Use-one-object-for-shqueue.h-test.patch db5.3-5.3.28+dfsg1/debian/patches/0014-Use-one-object-for-shqueue.h-test.patch
--- db5.3-5.3.28+dfsg1/debian/patches/0014-Use-one-object-for-shqueue.h-test.patch 1970-01-01 01:00:00.0 +0100
+++ db5.3-5.3.28+dfsg1/debian/patches/0014-Use-one-object-for-shqueue.h-test.patch 2021-01-29 12:45:00.0 +0100
@@ -0,0 +1,185 @@
+From: Jochen Sprickerhof
+Date: Fri, 29 Jan 2021 12:00:31 +0100
+Subject: Use one object for shqueue.h test
+
+shqueue.h uses pointer arithmetic to store the relative offsets of the
+elements. This is only allowed in an array object.
+---
+ test/c/suites/TestQueue.c | 38 ++
+ 1 file changed, 18 insertions(+), 20 deletions(-)
+
+diff --git a/test/c/suites/TestQueue.c b/test/c/suites/TestQueue.c
+index b5bc1ab..02f6f41 100644
+--- a/test/c/suites/TestQueue.c
b/test/c/suites/TestQueue.c
+@@ -44,6 +44,9 @@ const char *failure_reason_names[] = {
+ "expected to be at the head of the list"
+ };
+
++// longest ops[i].final
++#define TEST_QUEUE_LEN 5
++
+ SH_LIST_HEAD(sh_lq);
+ struct sh_le {
+ char content;
+@@ -79,14 +82,15 @@ sh_l_init(items)
+ {
+ const char *c = items;
+ struct sh_le *ele = NULL, *last_ele = (struct sh_le*)-1;
+- struct sh_lq *l = calloc(1, sizeof(struct sh_lq));
++ struct sh_lq *l = calloc(1, sizeof(struct sh_lq) + TEST_QUEUE_LEN * sizeof(struct sh_le));
++ size_t i = 0;
+
+ SH_LIST_INIT(l);
+
+ while (*c != '\0') {
+ if (c[0] != ' ') {
+ last_ele = ele;
+- ele = calloc(1, sizeof(struct sh_le));
++ ele = (struct sh_le*)[sizeof(struct sh_lq) + i++ * sizeof(struct sh_le)];
+ ele->content = c[0];
+ if (SH_LIST_EMPTY(l))
+ SH_LIST_INSERT_HEAD(l, ele, sh_les, sh_le);
+@@ -106,8 +110,6 @@ sh_l_remove_head(l)
+ struct sh_le *ele = SH_LIST_FIRST(l, sh_le);
+
+ SH_LIST_REMOVE_HEAD(l, sh_les, sh_le);
+- if (ele != NULL)
+- free(ele);
+
+ return (l);
+ }
+@@ -126,7 +128,6 @@ sh_l_remove_tail(l)
+
+ if (ele) {
+ SH_LIST_REMOVE(ele, sh_les, sh_le);
+- free(ele);
+ }
+ return (l);
+ }
+@@ -153,7 +154,7 @@ sh_l_insert_head(l, item)
+ struct sh_lq *l;
+ const char *item;
+ {
+- struct sh_le *ele = calloc(1, sizeof(struct sh_le));
++ struct sh_le *ele = (struct sh_le*)[sizeof(struct sh_lq) + (TEST_QUEUE_LEN-1) * sizeof(struct sh_le)];
+
+ ele->content = item[0];
+ SH_LIST_INSERT_HEAD(l, ele, sh_les, sh_le);
+@@ -174,11 +175,11 @@ sh_l_insert_tail(l, item)
+ last_ele = SH_LIST_NEXT(last_ele, sh_les, sh_le);
+
+ if (last_ele == NULL) {
+- ele = calloc(1, sizeof(struct sh_le));
++ ele = (struct sh_le*)[sizeof(struct sh_lq) + (TEST_QUEUE_LEN-1) * sizeof(struct sh_le)];
+ ele->content
Bug#981289: marked as done (udunits breaks gnudatalanguage autopkgtest)
Your message dated Fri, 29 Jan 2021 13:05:28 + with message-id and subject line Bug#981289: fixed in udunits 2.2.28-3 has caused the Debian Bug report #981289, regarding udunits breaks gnudatalanguage autopkgtest to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 981289: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=981289 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: udunits, gnudatalanguage Control: found -1 udunits/2.2.28-2 Control: found -1 gnudatalanguage/0.9.9-13 Severity: serious Tags: sid bullseye X-Debbugs-CC: debian...@lists.debian.org User: debian...@lists.debian.org Usertags: breaks needs-update Dear maintainer(s), With a recent upload of udunits the autopkgtest of gnudatalanguage fails in testing when that autopkgtest is run with the binary packages of udunits from unstable. It passes when run with only packages from testing. In tabular form: passfail udunitsfrom testing2.2.28-2 gnudatalanguagefrom testing0.9.9-13 all others from testingfrom testing I copied some of the output at the bottom of this report. There is no /dev/sda on most of our workers. Currently this regression is blocking the migration of udunits to testing [1]. Due to the nature of this issue, I filed this bug report against both packages. Can you please investigate the situation and reassign the bug to the right package? More information about this bug and the reason for filing it can be found on https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation Paul [1] https://qa.debian.org/excuses.php?package=udunits https://ci.debian.net/data/autopkgtest/testing/amd64/g/gnudatalanguage/10074185/log.gz % WARNING: your version of the GraphicsMagick library will truncate images to 16 bits per pixel % Compiled module: TEST_FILE_TEST. % Compiled module: ERRORS_ADD. % TEST_FILE_TEST_UNIX: Error on operation : This special file /dev/sda should exist ! % TEST_FILE_TEST_UNIX: Error on operation : This special file /dev/sda must be a block device ! % Compiled module: BANNER_FOR_TESTSUITE. % Compiled module: GDL_IDL_FL. % TEST_FILE_TEST_UNIX: === % TEST_FILE_TEST_UNIX: = = % TEST_FILE_TEST_UNIX: = 2 errors encountered during TEST_FILE_TEST_UNIX tests = % TEST_FILE_TEST_UNIX: = = % TEST_FILE_TEST_UNIX: === % Compiled module: ERRORS_CUMUL. % Compiled module: FILE_WHICH. % Compiled module: PATH_SEP. % TEST_FILE_TEST_GET_MODE: Error on operation : This file /tmp/autopkgtest-lxc.tr9rpg1n/downtmp/build.2hE/src/testsuite/Saturn.jpg has a bad mode ! % TEST_FILE_TEST_GET_MODE: Error on operation : This file /dev/sda should exist ! % TEST_FILE_TEST_GET_MODE: === % TEST_FILE_TEST_GET_MODE: = = % TEST_FILE_TEST_GET_MODE: = 2 errors encountered during TEST_FILE_TEST_GET_MODE tests = % TEST_FILE_TEST_GET_MODE: = = % TEST_FILE_TEST_GET_MODE: === % TEST_FILE_TEST_FILE_BASIC: NO errors encountered during TEST_FILE_TEST_FILE_BASIC tests % TEST_FILE_TEST_FILE_SYMLINK: NO errors encountered during TEST_FILE_TEST_FILE_SYMLINK tests % TEST_FILE_TEST_DIR_BASIC: NO errors encountered during TEST_FILE_TEST_DIR_BASIC tests % TEST_FILE_TEST_DIR_SYMLINK: NO errors encountered during TEST_FILE_TEST_DIR_SYMLINK tests % TEST_FILE_TEST_DIR_DANGLING: Error on operation : dir. 2 not removed % TEST_FILE_TEST_DIR_DANGLING: Error on operation : dir. 2 still symlink % TEST_FILE_TEST_DIR_DANGLING: === % TEST_FILE_TEST_DIR_DANGLING: = = % TEST_FILE_TEST_DIR_DANGLING: = 2 errors encountered during TEST_FILE_TEST_DIR_DANGLING tests = % TEST_FILE_TEST_DIR_DANGLING: = = % TEST_FILE_TEST_DIR_DANGLING: === % TEST_FILE_TEST: == % TEST_FILE_TEST: == % TEST_FILE_TEST: = 6 errors encountered during TEST_FILE_TEST tests = %
Bug#981289: udunits breaks gnudatalanguage autopkgtest
Ok, found the bug (and a fix). Instead of looking at the default xml path for the datafile, it tries to calculate the path in absolute terms, does it badly, and always prepends "/lib". Simple fix is to revert to 2.26 behaviour. Regards Alastair On 28/01/2021 19:59, Ole Streicher wrote: Control: notfound -1 gnudatalanguage Dear udunits maintainer, unfortunately, the test log of gnudatalanguage is a bit confusing; these are the relevant lines from it: % Compiled module: TEST_CONSTANTS. % IMSL_CONSTANT: UDUNITS: failed to load the default unit database % IMSL_CONSTANT: UDUNITS: failed to load the default unit database % Execution halted at: TEST_CONSTANTS 36 /tmp/autopkgtest-lxc.tr9rpg1n/downtmp/build.2hE/src/testsuite/test_constants.pro % $MAIN$ This looks that udunits didn't find its unit database. Since from the log one can see that the libudunits2-data package was loaded, I would guess that there is some problem with the library. When looking into the failed CI test for gyoto, the message is a bit similar: In gyoto.C: Error initializing libgyoto: Converters.C:56 in void Gyoto::Units::Init(): error initializing arcsec unit Could you check that? Best regards Ole -- Alastair McKinstry, email: alast...@sceal.ie, matrix: @alastair:sceal.ie, phone: 087-6847928 Green Party Councillor, Galway County Council
Bug#980635: marked as done (pyglet: FTBFS: E: Build killed with signal TERM after 150 minutes of inactivity)
Your message dated Fri, 29 Jan 2021 13:35:40 +0100 with message-id <58bd327e-2e54-ee40-1892-3005f1a60...@debian.org> and subject line Re: pyglet: FTBFS: E: Build killed with signal TERM after 150 minutes of inactivity has caused the Debian Bug report #980635, regarding pyglet: FTBFS: E: Build killed with signal TERM after 150 minutes of inactivity 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.) -- 980635: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=980635 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: pyglet Version: 1.4.10-1 Severity: serious Justification: FTBFS on amd64 Tags: bullseye sid ftbfs Usertags: ftbfs-20210120 ftbfs-bullseye Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > tests/integration/text/test_empty_document.py::test_empty_document[UnformattedDocument] > PASSED [ 37%] > tests/integration/text/test_empty_document.py::test_empty_document[FormattedDocument] > PASSED [ 38%] > tests/integration/text/test_empty_document.py::test_empty_document_bold[UnformattedDocument] > PASSED [ 38%] > tests/integration/text/test_empty_document.py::test_empty_document_bold[FormattedDocument] > PASSED [ 38%] > tests/integration/window/test_context_share.py::ContextShareTest::test_context_noshare_list > PASSED [ 38%] > tests/integration/window/test_context_share.py::ContextShareTest::test_context_share_list > PASSED [ 38%] > tests/integration/window/test_context_share.py::ContextShareTest::test_context_share_texture > PASSED [ 39%] > tests/integration/window/test_event_sequence.py::WindowShowEventSequenceTest::test_method > PASSED [ 39%] > tests/integration/window/test_event_sequence.py::WindowCreateEventSequenceTest::test_method > PASSED [ 39%] > tests/integration/window/test_event_sequence.py::WindowCreateFullScreenEventSequenceTest::test_method > PASSED [ 39%] > tests/integration/window/test_event_sequence.py::WindowSetFullScreenEventSequenceTest::test_method > PASSED [ 39%] > tests/integration/window/test_event_sequence.py::WindowUnsetFullScreenEventSequenceTest::test_method > PASSED [ 39%] > tests/integration/window/test_window_caption.py::test_window_caption PASSED [ > 40%] > tests/integration/window/test_window_caption.py::test_window_caption_from_argv > PASSED [ 40%] > tests/interactive/graphics/test_multitexture.py::test_multitexture > E: Build killed with signal TERM after 150 minutes of inactivity The full build log is available from: http://qa-logs.debian.net/2021/01/20/pyglet_1.4.10-1_unstable.log A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! If you reassign this bug to another package, please marking it as 'affects'-ing this package. See https://www.debian.org/Bugs/server-control#affects If you fail to reproduce this, please provide a build log and diff it with me so that we can identify if something relevant changed in the meantime. About the archive rebuild: The rebuild was done on EC2 VM instances from Amazon Web Services, using a clean, minimal and up-to-date chroot. Every failed build was retried once to eliminate random failures. --- End Message --- --- Begin Message --- Version: 1.4.10-2 Forgot to close this bug in the changelog! -- Michael R. Crusoe OpenPGP_signature Description: OpenPGP digital signature --- End Message ---
Processed: Bug 963363 forwarded to (solved) upstream issue
Processing commands for cont...@bugs.debian.org: > forwarded 963363 https://github.com/cisco/libsrtp/issues/523 Bug #963363 [src:libsrtp2] libsrtp2: FTBFS: running cipher self-test for AES-128 GCM using NSS...failed with error code 8 Set Bug forwarded-to-address to 'https://github.com/cisco/libsrtp/issues/523'. > -- Stopping processing here. Please contact me if you need assistance. -- 963363: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=963363 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#972767: marked as done (frr ftbfs with python3.9)
Your message dated Fri, 29 Jan 2021 12:33:39 + with message-id and subject line Bug#972767: fixed in frr 7.4-1.1 has caused the Debian Bug report #972767, regarding frr ftbfs with python3.9 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 972767: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=972767 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:frr Version: 7.4-1 Severity: serious Tags: sid bullseye User: debian-pyt...@lists.debian.org Usertags: python3.9 frr ftbfs with python3.9 (python3-defaults from experimental) https://people.debian.org/~ginggs/python3.9-default/frr_7.4-1build1_amd64-2020-10-21T08:19:46Z.build [...] checking python interpreter python3... /usr/bin/python3 (python3) checking whether /usr/bin/python3.9-config is available... yes checking whether /usr/bin/python3.9-config provides a working build environment... no checking whether pkg-config python-3.9 is available... yes checking whether pkg-config python-3.9 provides a working build environment... no checking whether /usr/bin/python3.9-config is available... yes checking whether /usr/bin/python3.9-config provides a working build environment... no checking whether pkg-config python-3.9 is available... yes checking whether pkg-config python-3.9 provides a working build environment... no configure: error: PYTHON (/usr/bin/python3) explicitly specified but development environment not working tail -v -n \+0 config.log --- End Message --- --- Begin Message --- Source: frr Source-Version: 7.4-1.1 Done: Adrian Bunk We believe that the bug you reported is fixed in the latest version of frr, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 972...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Adrian Bunk (supplier of updated frr package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Thu, 21 Jan 2021 16:06:12 +0200 Source: frr Architecture: source Version: 7.4-1.1 Distribution: unstable Urgency: medium Maintainer: David Lamparter Changed-By: Adrian Bunk Closes: 972767 Changes: frr (7.4-1.1) unstable; urgency=medium . * Non-maintainer upload. * Backport upstream fix for FTBFS with Python 3.9. (Closes: #972767) Checksums-Sha1: fceb595772c729297b0d68b5de7c30a133892b6f 2583 frr_7.4-1.1.dsc 990929608a127a99946eec559835b12aa7ae9fcf 16204 frr_7.4-1.1.debian.tar.xz Checksums-Sha256: 293a99c7d7891e34717092683fb9f8ec98c4d415c0677ede23533722a14f198e 2583 frr_7.4-1.1.dsc e8466b1cbfb7e0630ae32c10434d32e303dca2b5b1ae370680aad282d240e1e7 16204 frr_7.4-1.1.debian.tar.xz Files: b5363c085ee309d93696ed65f59a0223 2583 net optional frr_7.4-1.1.dsc 190b4b1429a18e83d950c0403d75771a 16204 net optional frr_7.4-1.1.debian.tar.xz -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEOvp1f6xuoR0v9F3wiNJCh6LYmLEFAmAJm5kACgkQiNJCh6LY mLGl7w//e3im3gvhUomE46nh8lfJOGwZFLg9GPdRkBLyPipOv+UHBVl6kgADZbsq wPvGvCI4i/kTE0OjDr7bEnEu/kKeyNUVYvFL/Kzp19b6auyIxPIY1HJxi+acFxE1 ciNg7KKs5SCNxNxFgpCSEB9/txDIjOEUFXooU+HF1Fw4Gb1ojjjXZ1bK891JbWak QCrkZ1n4tUY0pSgHABkg7N/ZHmI1PDV2mpgJ/oPA5+wHOnquhJHUBYyJyaWRAAVz e/x7Q1WT+p5EKLvd/hA+ug6C2HaTeIlMt6fPLH1BJkiHrVWmkauGjRW1Up0ZKeMw nKpWDKeC5xQkCAJPkFBwoVziGsyyenbhzELejgenka6o547ZquwfNWBN2/NzNpnW ZsYrgCU/BP10/lEQIrzw3tTbk7SlnubfIy+AVJLxsN5YJXoC7MryUXd7s8lFjIuq yYrK5cT81wPVVglGAY98l95ikvm5XsAg6o80Zrr8IUrMLLXFBPiWgbk/AQRQnYK2 2rX01eT6LKwb2zavAAF49+S+D91KaK+3IPpj8+5MwocaesSLYEKvJBJr3459WL5j yYFwP98K2hjiAHaU1U9v5D/xSR86EpX/2Y4bwt6Z6I9fRVSUHmBW1pkp3+Nrk393 aJiqizQcTIHNpG7B7PwQXNGWhAxDaFy6PG8uUSLfua3ImecsmIs= =XGuD -END PGP SIGNATURE End Message ---
Bug#976513: marked as done (tuxmath: FTBFS: ld: network.o:./src/network.c:57: multiple definition of `lan_player_info'; menu_lan.o:./src/menu_lan.c:40: first defined here)
Your message dated Fri, 29 Jan 2021 12:33:55 + with message-id and subject line Bug#976513: fixed in tuxmath 2.0.3-6.1 has caused the Debian Bug report #976513, regarding tuxmath: FTBFS: ld: network.o:./src/network.c:57: multiple definition of `lan_player_info'; menu_lan.o:./src/menu_lan.c:40: first defined here 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.) -- 976513: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=976513 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: tuxmath Version: 2.0.3-6 Severity: serious Justification: FTBFS on arm64 Tags: bullseye sid ftbfs Usertags: ftbfs-20201205 ftbfs-bullseye Hi, During a rebuild of all packages in sid, your package failed to build on arm64 (I don't know if it also fails on amd64). Relevant part (hopefully): > aarch64-linux-gnu-gcc -Wall -g -DDATA_PREFIX=\"/usr/share/tuxmath\" -DDEBUG > -DSOUND -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong > -Wformat -Werror=format-security -D_GNU_SOURCE=1 -D_REENTRANT > -I/usr/include/SDL -D_GNU_SOURCE=1 -D_REENTRANT -I/usr/include/SDL -pthread > -I/usr/include/librsvg-2.0 -I/usr/include/gdk-pixbuf-2.0 > -I/usr/include/libmount -I/usr/include/blkid -I/usr/include/cairo > -I/usr/include/glib-2.0 -I/usr/lib/aarch64-linux-gnu/glib-2.0/include > -I/usr/include/pixman-1 -I/usr/include/uuid -I/usr/include/freetype2 > -I/usr/include/libpng16 -I/usr/include/cairo -I/usr/include/glib-2.0 > -I/usr/lib/aarch64-linux-gnu/glib-2.0/include -I/usr/include/pixman-1 > -I/usr/include/uuid -I/usr/include/freetype2 -I/usr/include/libpng16 > -D_GNU_SOURCE=1 -D_REENTRANT -I/usr/include/SDL -I/usr/include/libxml2 > -D_GNU_SOURCE=1 -D_REENTRANT -pthread -I/usr/include/SDL > -I/usr/include/pango-1.0 -I/usr/include/fribidi -I/usr/include/harfbuzz > -I/usr/include/librsvg-2.0 -I/usr/include/gdk-pixbuf-2.0 > -I/usr/include/libmount -I/usr/include/blkid -I/usr/include/cairo > -I/usr/include/glib-2.0 -I/usr/lib/aarch64-linux-gnu/glib-2.0/include > -I/usr/include/pixman-1 -I/usr/include/uuid -I/usr/include/freetype2 > -I/usr/include/libpng16 -I/usr/include/libxml2 -Wl,-z,relro -o tuxmathserver > servermain.o server.o mathcards.o options.o -lm -lSDL -lSDL_image -lSDL > -lSDL_mixer -lSDL -lrsvg-2 -lm -lgio-2.0 -lgdk_pixbuf-2.0 -lgobject-2.0 > -lglib-2.0 -lcairo -lcairo -lSDL_net -lSDL -lxml2 -lt4k_common -lSDL_mixer > -lSDL_net -lSDL_image -lSDL -lSDL_Pango -lpango-1.0 -lharfbuzz -lrsvg-2 -lm > -lgio-2.0 -lgdk_pixbuf-2.0 -lgobject-2.0 -lglib-2.0 -lcairo -lxml2 > /usr/bin/ld: network.o:./src/network.c:57: multiple definition of > `lan_player_info'; menu_lan.o:./src/menu_lan.c:40: first defined here > collect2: error: ld returned 1 exit status The full build log is available from: http://qa-logs.debian.net/2020/12/05/tuxmath_2.0.3-6_unstable.log A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! If you reassign this bug to another package, please marking it as 'affects'-ing this package. See https://www.debian.org/Bugs/server-control#affects If you fail to reproduce this, please provide a build log and diff it with me so that we can identify if something relevant changed in the meantime. About the archive rebuild: The rebuild was done on EC2 VM instances from Amazon Web Services, using a clean, minimal and up-to-date chroot. Every failed build was retried once to eliminate random failures. --- End Message --- --- Begin Message --- Source: tuxmath Source-Version: 2.0.3-6.1 Done: Adrian Bunk We believe that the bug you reported is fixed in the latest version of tuxmath, 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 976...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Adrian Bunk (supplier of updated tuxmath 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 Jan 2021 13:55:10 +0200 Source: tuxmath Architecture: source Version: 2.0.3-6.1 Distribution: unstable Urgency: medium Maintainer: Holger Levsen Changed-By: Adrian Bunk Closes: 976513 Changes: tuxmath (2.0.3-6.1)
Bug#981300: arduino-core-avr breaks arduino-mk
Hello Carsten, i rebuilt arduino-mk and removed its Depends and it worked, so changing it to "arduino-core (>= 2:1.8.13+dfsg1-1)" would be the proper fix. the problem tends to be getting arduino-mk updated, think last time it needed a team upload (python3 fixes). regards. On 29/01/2021 06:00, Carsten Schoenert wrote: Control: reassign -1 arduino-mk Control: rename -1 arduino-mk: needs to depend on arduino >= 2:1.8.13+dfsg1-1 Control: severity -1 serious Hello Simon, thanks for reporting! Am 28.01.21 um 22:42 schrieb debi...@the-jedi.co.uk: Package: arduino Version: 1.8.13+dfsg1-1 The recent rename of arduino-core to arduino-core-avr breaks the Depends in arduino-mk: Depends: arduino-core (>= 1:1.0+dfsg-8), This is not fully correct, the old package arduino-core got melted into arduino, arduino-core-avr is a new dependency of arduino. arduino-mk needs to get adjusted, it needs to change this existing Depends into arduino-core (>= 2:1.8.13+dfsg1-1) -- Simon John
Bug#970497: igraph: FTBFS on mips64el
On Thu, 28 Jan 2021 07:33:56 +0100 Jerome BENOIT wrote: > Hello, > > I am currently isolating the faulty code on the porter Eller. > > The issue seems to appear after the call to arpack functions, > so it does not look as an arparck issue. Finally I isolated the place where the issue emerge. It is indeed an arpack issue. In src/arpack.c in function igraph_arpack_rssolve the dsaupd_ loop works fine in the sense that the loop keeps giving the same output when the random seed is fixed. The issue emerges at the postamble of the loop, dseupd_ gives random output in the same conditions. I am on my way to write a small piece of arpack code to confirm this. If confirmed, I will submit the bug to the arpack debian maintainer. Best wishes, Jerome > > Best wishes, > Jerome > > -- > Jerome BENOIT | calculus+at-rezozer^dot*net > https://qa.debian.org/developer.php?login=calcu...@rezozer.net > AE28 AE15 710D FF1D 87E5 A762 3F92 19A6 7F36 C68B > > -- Jerome BENOIT | calculus+at-rezozer^dot*net https://qa.debian.org/developer.php?login=calcu...@rezozer.net AE28 AE15 710D FF1D 87E5 A762 3F92 19A6 7F36 C68B
Bug#976513: tuxmath: diff for NMU version 2.0.3-6.1
On Mon, Jan 18, 2021 at 03:32:04PM +, Holger Levsen wrote: > Dear Adrian, Hi Holger, > On Mon, Jan 18, 2021 at 01:59:29PM +0200, Adrian Bunk wrote: > > I've prepared an NMU for tuxmath (versioned as 2.0.3-6.1) and uploaded > > it to DELAYED/14. Please feel free to tell me if I should cancel it. > > thank you for this! I've plans to do new releases of tuxmath and tuxtype > this month but it's great that you uploaded already. Feel free to reupload > to DELAYED/0 too. thanks, rescheduled for immediate upload. > cheers, > Holger cu Adrian
Bug#977779: geary FTBFS on mipsel: test suite failure
On Fri, Jan 08, 2021 at 06:07:29PM +0100, Alberto Garcia wrote: > On Mon, Dec 21, 2020 at 11:30:14PM +0200, Adrian Bunk wrote: > > > I see that the build eventually succeeded: > > > > > > > > > https://buildd.debian.org/status/logs.php?pkg=geary=3.38.1-1=mipsel > > > > > > The webkit2gtk build is flaky itself in mipsel, we discussed this > > > already in the past (#962616), I wonder if this is the same root > > > problem? > > > > This is the same problem. > > > > Note that the build is not and never was flaky, it does 100% > > determinisitically fail on Loongson buildds and succeed on Octeon > > buildds. > > > > Jiaxun Yang discovered this weekend that CeilingOnPageSize is wrong > > for Loongson which has 16 kB pagesize and this matches when the > > problems started in 2.28.1, but unfortunately fixing this does not > > seem to fix all problems. > > But this a bug in the CPU, right? Do I understand correctly that the > package can fail depending on what CPU it is run on regardless of how > it was built? > > I'm trying to understand what we can do in WebKit in order to fix or > work around this. It is a bug in WebKit that a kernel configuration is assumed that is not even permitted on Loongson: https://sources.debian.org/src/webkit2gtk/2.31.1-1/Source/WTF/wtf/PageBlock.h/#L54 https://sources.debian.org/src/linux/5.10.9-1/arch/mips/Kconfig/#L2213-L2215 This might not be sufficient to fix all problems of webkit2gtk on MIPS, but has be fixed in WebKit in any case. > Berto cu Adrian BTW: The 4kB setting for arm64 is also questionable, Ubuntu releases now additionally ship kernels with 64 kB page size: https://launchpad.net/ubuntu/groovy/+package/linux-image-unsigned-5.8.0-41-generic-64k
Bug#980701: sasview: FTBFS: error: [Errno 2] No such file or directory: '/<>/docs/sphinx-docs/build/latex/SasView.pdf'
Package: sasview-doc Followup-For: Bug #980701 The cutting point is: > reading sources... [ 16%] dev/sasview-api/sas.qtgui.UnitTesting > qt.qpa.xcb: could not connect to display > qt.qpa.plugin: Could not load the Qt platform plugin "xcb" in "" even though > it was found. > This application failed to start because no Qt platform plugin could be > initialized. Reinstalling the application may fix this problem. > > Available platform plugins are: eglfs, linuxfb, minimal, minimalegl, > offscreen, vnc, xcb. On my system it reports reading sources... [ 16%] dev/sasview-api/sas.qtgui.UnitTesting Warning: Ignoring XDG_SESSION_TYPE=wayland on Gnome. Use QT_QPA_PLATFORM=wayland to run on Wayland anyway. reading sources... [ 16%] dev/sasview-api/sas.qtgui.Utilities reading sources... [ 17%] dev/sasview-api/sas.sascalc reading sources... [ 17%] dev/sasview-api/sas.sascalc.calculator Reprodicibilty tests last succeeded on 2020-12-27. Something must have changed in the environment after that, though it wasn't Qt. Probably the best solution is to figure out how to activate the "offscreen" platform plugin to build with.
Bug#980632: cloud-sptheme: FTBFS: dh_auto_test: error: pybuild --test -i python{version} -p 3.9 returned exit code 13
Control: tags -1 help Hi, I have updated Git[1] to the latest upstream version to potentially solve this issue. Unfortunately the build stops with: ... copying cloud_sptheme/ext/static/auto_redirect.html_t -> /build/cloud-sptheme-1.10.1.post20200504175005/.pybuild/cpython3_3.9/build/cloud_sptheme/ext/static copying cloud_sptheme/ext/static/auto_redirect.css -> /build/cloud-sptheme-1.10.1.post20200504175005/.pybuild/cpython3_3.9/build/cloud_sptheme/ext/static python3 -m sphinx /build/cloud-sptheme-1.10.1.post20200504175005/docs /build/cloud-sptheme-1.10.1.post20200504175005/html Running Sphinx v3.4.3 making output directory... done Theme error: no theme named 'cloud' found (missing theme.conf?) make[1]: *** [debian/rules:8: override_dh_auto_build] Error 2 make[1]: Leaving directory '/build/cloud-sptheme-1.10.1.post20200504175005' Since I'm not involved into the packaging of this package I rather stop here and hope my commits are helpful to solve this issue. I was also running routine-update to modernise the packaging - I hope you agree with those changes. If not feel free to revert. Kind regards Andreas. [1] https://salsa.debian.org/python-team/packages/cloud-sptheme -- http://fam-tille.de
Processed: Re: cloud-sptheme: FTBFS: dh_auto_test: error: pybuild --test -i python{version} -p 3.9 returned exit code 13
Processing control commands:
> tags -1 help
Bug #980632 [src:cloud-sptheme] cloud-sptheme: FTBFS: dh_auto_test: error:
pybuild --test -i python{version} -p 3.9 returned exit code 13
Added tag(s) help.
--
980632: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=980632
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#979815: marked as done (libmeep23: missing Conflicts: libmeep22)
Your message dated Fri, 29 Jan 2021 10:18:24 + with message-id and subject line Bug#979815: fixed in meep 1.17.1-1 has caused the Debian Bug report #979815, regarding libmeep23: missing Conflicts: libmeep22 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.) -- 979815: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=979815 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: libmeep23 Version: 1.17.0-2 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package fails to upgrade from 'testing'. It installed fine in 'testing', then the upgrade to 'sid' fails because it tries to overwrite other packages files without declaring a Breaks+Replaces relation. See policy 7.6 at https://www.debian.org/doc/debian-policy/ch-relationships.html#overwriting-files-and-replacing-packages-replaces >From the attached log (scroll to the bottom...): Preparing to unpack .../libmeep23_1.17.0-2_amd64.deb ... Unpacking libmeep23 (1.17.0-2) ... dpkg: error processing archive /var/cache/apt/archives/libmeep23_1.17.0-2_amd64.deb (--unpack): trying to overwrite '/usr/share/meep/casimir.scm', which is also in package libmeep22 1.16.1-2 Errors were encountered while processing: /var/cache/apt/archives/libmeep23_1.17.0-2_amd64.deb cheers, Andreas libmeep22=1.16.1-2_libmeep23=1.17.0-2.log.gz Description: application/gzip --- End Message --- --- Begin Message --- Source: meep Source-Version: 1.17.1-1 Done: Thorsten Alteholz We believe that the bug you reported is fixed in the latest version of meep, 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 979...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Thorsten Alteholz (supplier of updated meep package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Thu, 28 Jan 2021 19:02:15 + Source: meep Architecture: source Version: 1.17.1-1 Distribution: unstable Urgency: medium Maintainer: Thorsten Alteholz Changed-By: Thorsten Alteholz Closes: 969693 979815 Changes: meep (1.17.1-1) unstable; urgency=medium . * New upstream release * debian/control: fix dependencies (Closes: #979815) * debian/control: close guile-3.0 bug (Closes: #969693) (realy fixed in 1.16.1-3) Checksums-Sha1: fa282cc809d689adbb1b4f90f7c511f49b7e74c9 2410 meep_1.17.1-1.dsc 0c79176208ee0b4176706136860f8f5792aff07a 29639336 meep_1.17.1.orig.tar.gz 813c32792cf48ed47bff563d49781a4385e81bf1 142188 meep_1.17.1-1.debian.tar.xz 495707b8e6fe0e93f8850f0b2ed1966e2dcdeb21 11853 meep_1.17.1-1_amd64.buildinfo Checksums-Sha256: 0420e587df4de0ba97262c9f2d7f05e8234dbdfb9cc58ecef96139cf5815dd01 2410 meep_1.17.1-1.dsc 271b4a547a7abc2e7ac67ecc06c2f112603c7de48c774a519f014b99b59185ad 29639336 meep_1.17.1.orig.tar.gz 32ff6971b94101d7cac223eb89bb56bcec739531cc47ac03c6e0948dc6c2fe0d 142188 meep_1.17.1-1.debian.tar.xz ccf21cfaa48dc23e22f259e1e15d8c154120349c9d59be1f53cb5efb359c2932 11853 meep_1.17.1-1_amd64.buildinfo Files: b55fcc6db4119812c53916b10c39e1c8 2410 science optional meep_1.17.1-1.dsc 1abda0fad3ba94c4b5fc753cf1518ea8 29639336 science optional meep_1.17.1.orig.tar.gz 39536ca6d11269dab2b8adc20ea74617 142188 science optional meep_1.17.1-1.debian.tar.xz 496030571f60a269ad89cce0367991df 11853 science optional meep_1.17.1-1_amd64.buildinfo -BEGIN PGP SIGNATURE- iQKnBAEBCgCRFiEEYgH7/9u94Hgi6ruWlvysDTh7WEcFAmATD/RfFIAALgAo aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldDYy MDFGQkZGREJCREUwNzgyMkVBQkI5Njk2RkNBQzBEMzg3QjU4NDcTHGRlYmlhbkBh bHRlaG9sei5kZQAKCRCW/KwNOHtYR8vfD/98NcSScnfaAy7LsNPhiJnNXjLs7hXo Zc9dvc6f7rFTX4pIc76bNC24XRWyTcWYNyi4fId2nhGgBi4xdXfNfDKv0ORNZ3dx MCIUvoEqg918YP+ZYPoBGXGEPVBq/lFp6xoizLSkLeEGY8uKx+3lDXusmkETG2TP 1AKlWDGqd8O1oaCWJLqQ5VbdbIGnIrk40NyVSyaseO8/oHlQchU0R4Sd4GkpJVAi B5OWzX/NsU42gkj+kLRpgNBU4olC41i/Dxlkl2pix1tZfqeJjhxL+hIDyxxayCWI Ue1hXgdtjFxKde5P7VhgCctb+v54zLqNR9lM6wpyx+5MWVYoCN5S488fv+l1syJ/ aqwC0NtI85ZxOXMHLgIceqUp+tZJHoom5gcS/So1y+78/9mA/Hp+FylWP1SqcaRy DHE9hKR+UU4oH7b+S16GCP2eaIZjbjrOuYu5JamgsxCM29cIwnRJRie5QiG1Dcdi
Bug#978235: marked as done (r10k: FTBFS: ruby-faraday : Breaks: ruby-puppet-forge (<= 2.3.2-1) but 2.3.2-1 is to be installed)
Your message dated Fri, 29 Jan 2021 10:18:30 + with message-id and subject line Bug#978235: fixed in r10k 3.7.0-1 has caused the Debian Bug report #978235, regarding r10k: FTBFS: ruby-faraday : Breaks: ruby-puppet-forge (<= 2.3.2-1) but 2.3.2-1 is to be installed 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.) -- 978235: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=978235 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: r10k Version: 3.4.1-3 Severity: serious Justification: FTBFS on amd64 Tags: bullseye sid ftbfs Usertags: ftbfs-20201226 ftbfs-bullseye Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > +--+ > | Install package build dependencies > | > +--+ > > > Setup apt archive > - > > Merged Build-Depends: debhelper-compat (= 12), gem2deb (>= 0.6.1~), git, > rake, ronn | ruby-ronn (<< 0.7.3-5.1~), ruby-colored2, ruby-cri (>= 2.6.1), > ruby-gettext-setup (>= 0.5), ruby-log4r (>= 1.1.10), ruby-minitar (>= 0.6.1), > ruby-multi-json (>= 1.10), ruby-puppet-forge (>= 2.3.0~), ruby-rspec (>= > 3.1), ruby-rugged (>= 0.24.0), yard (>= 0.8.7.3), build-essential, fakeroot > Filtered Build-Depends: debhelper-compat (= 12), gem2deb (>= 0.6.1~), git, > rake, ronn, ruby-colored2, ruby-cri (>= 2.6.1), ruby-gettext-setup (>= 0.5), > ruby-log4r (>= 1.1.10), ruby-minitar (>= 0.6.1), ruby-multi-json (>= 1.10), > ruby-puppet-forge (>= 2.3.0~), ruby-rspec (>= 3.1), ruby-rugged (>= 0.24.0), > yard (>= 0.8.7.3), build-essential, fakeroot > dpkg-deb: building package 'sbuild-build-depends-main-dummy' in > '/<>/apt_archive/sbuild-build-depends-main-dummy.deb'. > Ign:1 copy:/<>/apt_archive ./ InRelease > Get:2 copy:/<>/apt_archive ./ Release [957 B] > Ign:3 copy:/<>/apt_archive ./ Release.gpg > Get:4 copy:/<>/apt_archive ./ Sources [513 B] > Get:5 copy:/<>/apt_archive ./ Packages [584 B] > Fetched 2054 B in 0s (0 B/s) > Reading package lists... > Reading package lists... > > Install main build dependencies (apt-based resolver) > > > Installing build dependencies > Reading package lists... > Building dependency tree... > Reading state information... > Some packages could not be installed. This may mean that you have > requested an impossible situation or if you are using the unstable > distribution that some required packages have not yet been created > or been moved out of Incoming. > The following information may help to resolve the situation: > > The following packages have unmet dependencies: > ruby-faraday : Breaks: ruby-puppet-forge (<= 2.3.2-1) but 2.3.2-1 is to be > installed > E: Unable to correct problems, you have held broken packages. > apt-get failed. The full build log is available from: http://qa-logs.debian.net/2020/12/26/r10k_3.4.1-3_unstable.log A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! If you reassign this bug to another package, please marking it as 'affects'-ing this package. See https://www.debian.org/Bugs/server-control#affects If you fail to reproduce this, please provide a build log and diff it with me so that we can identify if something relevant changed in the meantime. About the archive rebuild: The rebuild was done on EC2 VM instances from Amazon Web Services, using a clean, minimal and up-to-date chroot. Every failed build was retried once to eliminate random failures. --- End Message --- --- Begin Message --- Source: r10k Source-Version: 3.7.0-1 Done: Sebastien Badia We believe that the bug you reported is fixed in the latest version of r10k, 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 978...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Sebastien Badia (supplier of updated r10k 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#980605: marked as done (snd: FTBFS: ../../../notcurses_s7.c:3815:10: error: ‘CELL_WIDEASIAN_MASK’ undeclared (first use in this function))
Your message dated Fri, 29 Jan 2021 09:34:53 +
with message-id
and subject line Bug#980605: fixed in snd 21.0-2
has caused the Debian Bug report #980605,
regarding snd: FTBFS: ../../../notcurses_s7.c:3815:10: error:
‘CELL_WIDEASIAN_MASK’ undeclared (first use in this function)
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.)
--
980605: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=980605
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: snd
Version: 21.0-1
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20210120 ftbfs-bullseye
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> gcc -c -DSCRIPTS_DIR=\"/usr/share/snd\" -DNOTCURSES_2_0_5=1 -Wdate-time
> -D_FORTIFY_SOURCE=2 -DREPRODUCIBLE_BUILD=1 -DNOTCURSES_2_0_5=1 -O2 -I. -g -O2
> -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat
> -Werror=format-security ../../../snd-nogui.c
> In file included from ../../../nrepl.c:16,
> from ../../../snd-nogui.c:295:
> ../../../notcurses_s7.c: In function ‘g_ncdirect_fg_default’:
> ../../../notcurses_s7.c:176:3: warning: ‘ncdirect_fg_default’ is deprecated
> [-Wdeprecated-declarations]
> 176 | return(s7_make_integer(sc, ncdirect_fg_default((struct ncdirect
> *)s7_c_pointer_with_type(sc, s7_car(args), ncdirect_symbol, __func__, 1;
> | ^~
> In file included from ../../../notcurses_s7.c:10,
> from ../../../nrepl.c:16,
> from ../../../snd-nogui.c:295:
> /usr/include/notcurses/direct.h:148:1: note: declared here
> 148 | ncdirect_fg_default(struct ncdirect* nc){
> | ^~~
> In file included from ../../../nrepl.c:16,
> from ../../../snd-nogui.c:295:
> ../../../notcurses_s7.c: In function ‘g_ncdirect_bg_default’:
> ../../../notcurses_s7.c:181:3: warning: ‘ncdirect_bg_default’ is deprecated
> [-Wdeprecated-declarations]
> 181 | return(s7_make_integer(sc, ncdirect_bg_default((struct ncdirect
> *)s7_c_pointer_with_type(sc, s7_car(args), ncdirect_symbol, __func__, 1;
> | ^~
> In file included from ../../../notcurses_s7.c:10,
> from ../../../nrepl.c:16,
> from ../../../snd-nogui.c:295:
> /usr/include/notcurses/direct.h:156:1: note: declared here
> 156 | ncdirect_bg_default(struct ncdirect* nc){
> | ^~~
> In file included from ../../../nrepl.c:16,
> from ../../../snd-nogui.c:295:
> ../../../notcurses_s7.c: In function ‘g_ncdirect_fg_rgb’:
> ../../../notcurses_s7.c:226:3: warning: ‘ncdirect_fg_rgb’ is deprecated
> [-Wdeprecated-declarations]
> 226 | return(s7_make_integer(sc, ncdirect_fg_rgb((struct ncdirect
> *)s7_c_pointer_with_type(sc, s7_car(args), ncdirect_symbol, __func__, 1),
> | ^~
> In file included from ../../../notcurses_s7.c:10,
> from ../../../nrepl.c:16,
> from ../../../snd-nogui.c:295:
> /usr/include/notcurses/direct.h:57:1: note: declared here
>57 | ncdirect_fg_rgb(struct ncdirect* nc, unsigned rgb){
> | ^~~
> In file included from ../../../nrepl.c:16,
> from ../../../snd-nogui.c:295:
> ../../../notcurses_s7.c: In function ‘g_ncdirect_bg_rgb’:
> ../../../notcurses_s7.c:232:3: warning: ‘ncdirect_bg_rgb’ is deprecated
> [-Wdeprecated-declarations]
> 232 | return(s7_make_integer(sc, ncdirect_bg_rgb((struct ncdirect
> *)s7_c_pointer_with_type(sc, s7_car(args), ncdirect_symbol, __func__, 1),
> | ^~
> In file included from ../../../notcurses_s7.c:10,
> from ../../../nrepl.c:16,
> from ../../../snd-nogui.c:295:
> /usr/include/notcurses/direct.h:65:1: note: declared here
>65 | ncdirect_bg_rgb(struct ncdirect* nc, unsigned rgb){
> | ^~~
> In file included from ../../../nrepl.c:16,
> from ../../../snd-nogui.c:295:
> ../../../notcurses_s7.c: In function ‘g_ncdirect_styles_set’:
> ../../../notcurses_s7.c:238:3: warning: ‘ncdirect_styles_set’ is deprecated
> [-Wdeprecated-declarations]
> 238 | return(s7_make_integer(sc, ncdirect_styles_set((struct ncdirect
> *)s7_c_pointer_with_type(sc, s7_car(args), ncdirect_symbol, __func__, 1),
> | ^~
> In file included from ../../../notcurses_s7.c:10,
> from ../../../nrepl.c:16,
> from ../../../snd-nogui.c:295:
> /usr/include/notcurses/direct.h:170:9: note: declared here
> 170 | API int
Bug#980635: pyglet: FTBFS: E: Build killed with signal TERM after 150 minutes of inactivity
Control: tags -1 upstream Control: forwarded -1 https://github.com/pyglet/pyglet/issues/346 Hi, I have opened an issue on Github about this issue. It persists for the latest upstream version 1.5.14 as well. Kind regards Andreas. -- http://fam-tille.de
Processed: Re: pyglet: FTBFS: E: Build killed with signal TERM after 150 minutes of inactivity
Processing control commands: > tags -1 upstream Bug #980635 [src:pyglet] pyglet: FTBFS: E: Build killed with signal TERM after 150 minutes of inactivity Added tag(s) upstream. > forwarded -1 https://github.com/pyglet/pyglet/issues/346 Bug #980635 [src:pyglet] pyglet: FTBFS: E: Build killed with signal TERM after 150 minutes of inactivity Set Bug forwarded-to-address to 'https://github.com/pyglet/pyglet/issues/346'. -- 980635: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=980635 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#980591: marked as done (eclipselink: FTBFS: [javac] /<>/org/eclipse/persistence/internal/oxm/record/json/JsonParserReader.java:30: error: package javax.json does not exist)
Your message dated Fri, 29 Jan 2021 08:48:53 + with message-id and subject line Bug#980591: fixed in eclipselink 2.6.9-3 has caused the Debian Bug report #980591, regarding eclipselink: FTBFS: [javac] /<>/org/eclipse/persistence/internal/oxm/record/json/JsonParserReader.java:30: error: package javax.json does not exist 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.) -- 980591: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=980591 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: eclipselink Version: 2.6.9-2 Severity: serious Justification: FTBFS on amd64 Tags: bullseye sid ftbfs Usertags: ftbfs-20210120 ftbfs-bullseye Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[1]: Entering directory '/<>' > ant -f debian/build.xml > Buildfile: /<>/debian/build.xml > > init: > [mkdir] Created dir: /<>/target/classes > [mkdir] Created dir: /<>/target/jpql > [mkdir] Created dir: /<>/target/modelgen > > compile: > [javac] Compiling 3363 source files to /<>/target/classes > [javac] > /<>/org/eclipse/persistence/internal/oxm/record/json/JsonParserReader.java:30: > error: package javax.json does not exist > [javac] import javax.json.Json; > [javac] ^ > [javac] > /<>/org/eclipse/persistence/internal/oxm/record/json/JsonParserReader.java:31: > error: package javax.json does not exist > [javac] import javax.json.JsonArrayBuilder; > [javac] ^ > [javac] > /<>/org/eclipse/persistence/internal/oxm/record/json/JsonParserReader.java:32: > error: package javax.json does not exist > [javac] import javax.json.JsonException; > [javac] ^ > [javac] > /<>/org/eclipse/persistence/internal/oxm/record/json/JsonParserReader.java:33: > error: package javax.json does not exist > [javac] import javax.json.JsonObjectBuilder; > [javac] ^ > [javac] > /<>/org/eclipse/persistence/internal/oxm/record/json/JsonParserReader.java:34: > error: package javax.json does not exist > [javac] import javax.json.JsonStructure; > [javac] ^ > [javac] > /<>/org/eclipse/persistence/internal/oxm/record/json/JsonParserReader.java:35: > error: package javax.json does not exist > [javac] import javax.json.JsonValue; > [javac] ^ > [javac] > /<>/org/eclipse/persistence/internal/oxm/record/json/JsonParserReader.java:36: > error: package javax.json.stream does not exist > [javac] import javax.json.stream.JsonParser; > [javac] ^ > [javac] > /<>/org/eclipse/persistence/internal/oxm/record/json/JsonParserReader.java:54: > error: cannot find symbol > [javac] private final JsonParser parser; > [javac] ^ > [javac] symbol: class JsonParser > [javac] location: class JsonParserReader > [javac] > /<>/org/eclipse/persistence/internal/oxm/record/json/JsonStructureReader.java:28: > error: package javax.json does not exist > [javac] import javax.json.Json; > [javac] ^ > [javac] > /<>/org/eclipse/persistence/internal/oxm/record/json/JsonStructureReader.java:29: > error: package javax.json does not exist > [javac] import javax.json.JsonArray; > [javac] ^ > [javac] > /<>/org/eclipse/persistence/internal/oxm/record/json/JsonStructureReader.java:30: > error: package javax.json does not exist > [javac] import javax.json.JsonNumber; > [javac] ^ > [javac] > /<>/org/eclipse/persistence/internal/oxm/record/json/JsonStructureReader.java:31: > error: package javax.json does not exist > [javac] import javax.json.JsonException; > [javac] ^ > [javac] > /<>/org/eclipse/persistence/internal/oxm/record/json/JsonStructureReader.java:32: > error: package javax.json does not exist > [javac] import javax.json.JsonObject; > [javac] ^ > [javac] > /<>/org/eclipse/persistence/internal/oxm/record/json/JsonStructureReader.java:33: > error: package javax.json does not exist > [javac] import javax.json.JsonReader; > [javac] ^ > [javac] > /<>/org/eclipse/persistence/internal/oxm/record/json/JsonStructureReader.java:34: > error: package javax.json does not exist > [javac] import javax.json.JsonString; > [javac] ^ > [javac] > /<>/org/eclipse/persistence/internal/oxm/record/json/JsonStructureReader.java:35: >
Processed: Bug#980605 marked as pending in snd
Processing control commands: > tag -1 pending Bug #980605 [src:snd] snd: FTBFS: ../../../notcurses_s7.c:3815:10: error: ‘CELL_WIDEASIAN_MASK’ undeclared (first use in this function) Added tag(s) pending. -- 980605: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=980605 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#980605: marked as pending in snd
Control: tag -1 pending Hello, Bug #980605 in snd 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/multimedia-team/snd/-/commit/8eea267ffe7871e474b853da2e2b8ac44a5ac8c9 Fixed notcurses version-comparision Closes: #980605 (this message was generated automatically) -- Greetings https://bugs.debian.org/980605
Bug#981287: marked as done (jupyterlab-server: autopkgtest regression: No module named 'anyio')
Your message dated Fri, 29 Jan 2021 09:24:22 +0100 with message-id and subject line Now python-anyio is in unstable and testing has caused the Debian Bug report #981287, regarding jupyterlab-server: autopkgtest regression: No module named 'anyio' 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.) -- 981287: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=981287 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: jupyterlab-server Version: 2.0.0-1 X-Debbugs-CC: debian...@lists.debian.org Severity: serious User: debian...@lists.debian.org Usertags: regression Dear maintainer(s), With a recent upload of jupyterlab-server the autopkgtest of jupyterlab-server fails in testing when that autopkgtest is run with the binary packages of jupyterlab-server from unstable. It passes when run with only packages from testing. In tabular form: passfail jupyterlab-serverfrom testing2.0.0-1 all others from testingfrom testing I copied some of the output at the bottom of this report. Currently this regression is blocking the migration to testing [1]. Can you please investigate the situation and fix it? More information about this bug and the reason for filing it can be found on https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation Paul [1] https://qa.debian.org/excuses.php?package=jupyterlab-server https://ci.debian.net/data/autopkgtest/testing/amd64/j/jupyterlab-server/10075204/log.gz autopkgtest [12:11:40]: test import: [--- Traceback (most recent call last): File "", line 1, in File "/tmp/autopkgtest-lxc.a1pp7mfm/downtmp/build.ywI/src/jupyterlab_server/__init__.py", line 4, in from .app import LabServerApp File "/tmp/autopkgtest-lxc.a1pp7mfm/downtmp/build.ywI/src/jupyterlab_server/app.py", line 11, in from jupyter_server.extension.application import ExtensionApp, ExtensionAppJinjaMixin File "/usr/lib/python3/dist-packages/jupyter_server/extension/application.py", line 20, in from jupyter_server.serverapp import ServerApp File "/usr/lib/python3/dist-packages/jupyter_server/serverapp.py", line 72, in from .services.contents.filemanager import AsyncFileContentsManager, FileContentsManager File "/usr/lib/python3/dist-packages/jupyter_server/services/contents/filemanager.py", line 15, in from anyio import run_sync_in_worker_thread ModuleNotFoundError: No module named 'anyio' autopkgtest [12:11:43]: test import: ---] OpenPGP_signature Description: OpenPGP digital signature --- End Message --- --- Begin Message --- Hi, this bug is now fixed : the src:python-anyio is in unstable and testing. Cheers, JP--- End Message ---
