Bug#976107: builds with 2.4.2-0.2, will be fixed in next openssl upload
Control: severity -1 important builds with 2.4.2-0.2, will be fixed in next openssl upload
Processed: builds with 2.4.2-0.2, will be fixed in next openssl upload
Processing control commands: > severity -1 important Bug #976107 [src:python-asyncssh] python-asyncssh FTBFS: FAIL: test_expired_root (tests.test_x509._TestX509) Severity set to 'important' from 'serious' -- 976107: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=976107 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#976475: Bug#976535: Bug#976495: also happens on amd64, should be worked around by 1.8.20-5 but the real fix will come with 1.8.20-6
Lucas Nussbaum writes:
> There was a texlive update in the meantime. Here are the versions of
> packages that differ.
I explored this a bit today -- there's something quite amiss with the
docbook toolchain. I'm seeing a lot of this error:
! Undefined control sequence.
\close@pdflink ->\Hy@endcolorlink
\Hy@VerboseLinkStop \pdfendlink
l.585 ...-mode}}History\endNode{}\endSeq{}\endLink
{}\Seq%
The result is that pdfjadetex exits with status 1 and the resulting PDF
has a lot of artifacts in the TOC. Each TOC label and page number are
prefixed with 'black'.
I'd be happy to help fix things, but I'm afraid I'm way out of my
docbook depth here.
--
-keith
signature.asc
Description: PGP signature
Bug#973122: marked as done (rust-core-foundation: FTBFS: build-dependency not installable: librust-core-foundation-sys-0.7+default-dev)
Your message dated Sun, 6 Dec 2020 03:02:28 + with message-id <5067a991-a4f7-db1c-7790-a76412992...@p10link.net> and subject line re: rust-core-foundation: FTBFS: build-dependency not installable: librust-core-foundation-sys-0.7+default-dev has caused the Debian Bug report #973122, regarding rust-core-foundation: FTBFS: build-dependency not installable: librust-core-foundation-sys-0.7+default-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.) -- 973122: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=973122 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: rust-core-foundation Version: 0.7.0-1 Severity: serious Justification: FTBFS on amd64 Tags: bullseye sid ftbfs Usertags: ftbfs-20201027 ftbfs-bullseye Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > +--+ > | Install package build dependencies > | > +--+ > > > Setup apt archive > - > > Merged Build-Depends: debhelper (>= 11), dh-cargo (>= 18), cargo, rustc, > libstd-rust-dev, librust-core-foundation-sys-0.7+default-dev, > librust-libc-0.2+default-dev, build-essential, fakeroot > Filtered Build-Depends: debhelper (>= 11), dh-cargo (>= 18), cargo, rustc, > libstd-rust-dev, librust-core-foundation-sys-0.7+default-dev, > librust-libc-0.2+default-dev, 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 [437 B] > Get:5 copy:/<>/apt_archive ./ Packages [505 B] > Fetched 1899 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... > 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: > sbuild-build-depends-main-dummy : Depends: > librust-core-foundation-sys-0.7+default-dev but it is not installable > 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/10/27/rust-core-foundation_0.7.0-1_unstable.log A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! About the archive rebuild: The rebuild was done on EC2 VM instances from Amazon Web Services, using a clean, minimal and up-to-date chroot. Every failed build was retried once to eliminate random failures. --- End Message --- --- Begin Message --- Version: 0.9.1-1 Forgot to close this in the changelog, closing now.--- End Message ---
Processed: your mail
Processing commands for cont...@bugs.debian.org: > block 975795 by 976624 Bug #975795 [src:polybar] polybar: FTBFS: ImportError: cannot import name 'gcd' from 'fractions' (/usr/lib/python3.9/fractions.py) 975795 was not blocked by any bugs. 975795 was not blocking any bugs. Added blocking bug(s) of 975795: 976624 > thanks Stopping processing here. Please contact me if you need assistance. -- 975795: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=975795 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#976624: python3-xcbgen: not compatible with python 3.9
Package: xcb-proto Severity: serious Tags: patch upstream Hello Maintainer, Python 3.9 deprecated fractions.gcd in favor of math.gcd, this causes a FTBFS in polybar #975795[0]. I believe this issue can cause FTBFS in other packages and thus I picked the serious severity (same one applied to the polybar bug report caused by this). I have tried to find the correct place to send patches upstream and gave up along the way when I couldn't find the project on freedesktop's gitlab instance[1] and the homepage pointed to an empty bugzilla (which I assume is not used anymore). I proposed a solution on salsa[2], which I'm also attaching to this email. I'm also willing to NMU the fix in case the maintainers don't have available time. Thanks, [0] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=975795 [1] https://gitlab.freedesktop.org [2] https://salsa.debian.org/xorg-team/proto/xcb-proto/-/merge_requests/2 -- Samuel Henrique From 0cb3fba7b33aae669d47ea5f30a5a2bc5f21e465 Mon Sep 17 00:00:00 2001 From: Samuel Henrique Date: Sat, 5 Dec 2020 20:07:58 + Subject: [PATCH] d/p/python39-compat.patch: Add patch for python 3.9 compatibility --- debian/patches/python39-compat.patch | 21 + debian/patches/series| 1 + 2 files changed, 22 insertions(+) create mode 100644 debian/patches/python39-compat.patch create mode 100644 debian/patches/series diff --git a/debian/patches/python39-compat.patch b/debian/patches/python39-compat.patch new file mode 100644 index 000..924ed40 --- /dev/null +++ b/debian/patches/python39-compat.patch @@ -0,0 +1,21 @@ +Description: Fix import of deprecated fractions.gcd function (for python >= 3.9) +Author: Samuel Henrique +Index: xcb-proto/xcbgen/align.py +=== +--- xcb-proto.orig/xcbgen/align.py xcb-proto/xcbgen/align.py +@@ -2,7 +2,13 @@ + This module contains helper classes for alignment arithmetic and checks + ''' + +-from fractions import gcd ++# python >= 3.9 compatibility ++# fractions.gcd is deprecated since python 3.9 ++# math.gcd is available since python 3.5 ++try: ++from fractions import gcd ++except ImportError: ++from math import gcd + + class Alignment(object): + diff --git a/debian/patches/series b/debian/patches/series new file mode 100644 index 000..5703b40 --- /dev/null +++ b/debian/patches/series @@ -0,0 +1 @@ +python39-compat.patch -- 2.29.2
Processed (with 1 error): Predictprotein RM title, severity
Processing commands for cont...@bugs.debian.org: > retitle 963927 RM: predictprotein -- ROM; does not work; code is not Bug #963927 [ftp.debian.org] [ROM] Please remove predictprotein Changed Bug title to 'RM: predictprotein -- ROM; does not work; code is not' from '[ROM] Please remove predictprotein'. > maintainable Unknown command or malformed arguments to command. > severity 963927 normal Bug #963927 [ftp.debian.org] RM: predictprotein -- ROM; does not work; code is not Severity set to 'normal' from 'serious' > End of message, stopping processing here. Please contact me if you need assistance. -- 963927: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=963927 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: lib3mf: diff for NMU version 1.8.1+ds-3.1
Processing control commands: > tags 957420 + pending Bug #957420 [src:lib3mf] lib3mf: ftbfs with GCC-10 Added tag(s) pending. -- 957420: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=957420 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#976475: Bug#976405: Bug#976495: also happens on amd64, should be worked around by 1.8.20-5 but the real fix will come with 1.8.20-6
Hi thanks for the digging through the errors. > < texlive-base_2020.20200925-1 > --- > > texlive-base_2020.20201203-2 > Also, I noticed a few new latex-related failures in this archive rebuild. [...] It seems that something in the interface with hyperref has changed. Unfortunately the docbook/jadetex stuff is rather cryptic to deciper and hardly possible to get a *minimal* example. If someone can send me a minimal (as far as possible) input file, and the list of commands necessary to run (openjade/doxy/whatever) I can look into the old/new code and contact the upupstream authors. Best Norbert -- PREINING Norbert https://www.preining.info Accelia Inc. + IFMGA ProGuide + TU Wien + JAIST + TeX Live + Debian Dev GPG: 0x860CDC13 fp: F7D8 A928 26E3 16A1 9FA0 ACF0 6CAC A448 860C DC13
Bug#962553: marked as done (gffread: autopkgtest needs update for new version of gff2aplot: warning on stderr)
Your message dated Sun, 06 Dec 2020 00:18:39 + with message-id and subject line Bug#962553: fixed in gffread 0.12.1-2 has caused the Debian Bug report #962553, regarding gffread: autopkgtest needs update for new version of gff2aplot: warning on stderr 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.) -- 962553: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=962553 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: gffread Version: 0.11.8-1 Severity: serious X-Debbugs-CC: debian...@lists.debian.org, gff2ap...@packages.debian.org Tags: sid bullseye User: debian...@lists.debian.org Usertags: needs-update Control: affects -1 src:gff2aplot Dear maintainer(s), With a recent upload of gff2aplot the autopkgtest of gffread fails in testing when that autopkgtest is run with the binary packages of gff2aplot from unstable. It passes when run with only packages from testing. In tabular form: passfail gff2aplot from testing2.0-12 gffreadfrom testing0.11.8-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 of gff2aplot to testing [1]. Of course, gff2aplot shouldn't just break your autopkgtest (or even worse, your package), but it seems to me that the change in gff2aplot was intended and your package needs to update to the new situation. If you can't fix the issue which triggers the warning, you can add the allow-stderr restriction for your test. If this is a real problem in your package (and not only in your autopkgtest), the right binary package(s) from gff2aplot should really add a versioned Breaks on the unfixed version of (one of your) package(s). Note: the Breaks is nice even if the issue is only in the autopkgtest as it helps the migration software to figure out the right versions to combine in the tests. 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=gff2aplot https://ci.debian.net/data/autopkgtest/testing/amd64/g/gffread/5834059/log.gz autopkgtest [01:19:28]: test run-tests: - - - - - - - - - - stderr - - - - - - - - - - Warning: invalid start coordinate at line: #name1:name2source feature beg1:beg2 end1:end2 score strand frame group comment Warning: invalid start coordinate at line: #name1:name2source feature beg1:beg2 end1:end2 score strand frame group comment autopkgtest [01:19:28]: summary run-testsFAIL stderr: Warning: invalid start coordinate at line: signature.asc Description: OpenPGP digital signature --- End Message --- --- Begin Message --- Source: gffread Source-Version: 0.12.1-2 Done: Graham Inggs We believe that the bug you reported is fixed in the latest version of gffread, 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 962...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Graham Inggs (supplier of updated gffread 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, 05 Dec 2020 23:56:29 + Source: gffread Architecture: source Version: 0.12.1-2 Distribution: unstable Urgency: medium Maintainer: Debian Med Packaging Team Changed-By: Graham Inggs Closes: 962553 Changes: gffread (0.12.1-2) unstable; urgency=medium . * Team upload * Skip two failing tests from gff2aplot that were not run previously due to being compressed (Closes: #962553) * Adjust autopkgtest dependencies for various architectures * Bump Standards-Version to 4.5.1, no changes Checksums-Sha1: f4903e6fd3a85e257ea80a28dcadfe6dae6538ad 2407 gffread_0.12.1-2.dsc d741db2cc333fd28a0deb9165faa78d680078b69 8288 gffread_0.12.1-2.debian.tar.xz Checksums-Sha256: 39c25e4197efdd2f3cfaa753328aa968cfe2128b2b2a59e69f1f3bcbbef7ac6f 2407 gffread_0.12.1-2.dsc 01c39502325660eb9696c85ef5e50319e7eb99e976b05b65fa2b07e81dce72e3
Bug#976541: marked as done (libgit2-glib: FTBFS: ../libgit2-glib/ggit-clone-options.c:152:5: error: token ""1.0"" is not valid in preprocessor expressions)
Your message dated Sat, 05 Dec 2020 23:49:09 + with message-id and subject line Bug#976541: fixed in libgit2-glib 0.99.0.1-1 has caused the Debian Bug report #976541, regarding libgit2-glib: FTBFS: ../libgit2-glib/ggit-clone-options.c:152:5: error: token ""1.0"" is not valid in preprocessor expressions 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.) -- 976541: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=976541 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: libgit2-glib Version: 0.28.0.1-2 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): > cc -Ilibgit2-glib/libgit2-glib-1.0.so.0.2800.0.p -Ilibgit2-glib > -I../libgit2-glib -I. -I.. -I/usr/include/libmount -I/usr/include/blkid > -I/usr/include/glib-2.0 -I/usr/lib/aarch64-linux-gnu/glib-2.0/include > -fdiagnostics-color=always -pipe -D_FILE_OFFSET_BITS=64 -Wall -Winvalid-pch > -ffast-math -fstrict-aliasing -Wpointer-arith -Wmissing-declarations > -Wformat=2 -Wstrict-prototypes -Wmissing-prototypes -Wnested-externs > -Wold-style-definition -Wdeclaration-after-statement -Wunused -Wuninitialized > -Wshadow -Wmissing-noreturn -Wmissing-format-attribute -Wredundant-decls > -Wlogical-op -Wcast-align -Wno-unused-local-typedefs -Werror=implicit > -Werror=init-self -Werror=main -Werror=missing-braces -Werror=return-type > -Werror=array-bounds -Werror=write-strings -DG_DISABLE_CAST_CHECKS > -DG_DISABLE_CHECKS -g -O2 -fdebug-prefix-map=/<>=. > -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time > -D_FORTIFY_SOURCE=2 -fPIC -pthread -DGIT_SSH=1 '-DG_LOG_DOMAIN="Ggit"' -MD > -MQ libgit2-glib/libgit2-glib-1.0.so.0.2800.0.p/ggit-clone-options.c.o -MF > libgit2-glib/libgit2-glib-1.0.so.0.2800.0.p/ggit-clone-options.c.o.d -o > libgit2-glib/libgit2-glib-1.0.so.0.2800.0.p/ggit-clone-options.c.o -c > ../libgit2-glib/ggit-clone-options.c > In file included from /usr/include/git2.h:69, > from ../libgit2-glib/ggit-clone-options.c:21: > ../libgit2-glib/ggit-clone-options.c: In function ‘create_repository_wrapper’: > ../libgit2-glib/ggit-clone-options.c:152:5: error: token ""1.0"" is not valid > in preprocessor expressions > 152 | #if LIBGIT2_SOVERSION >= 28 > | ^ > ../libgit2-glib/ggit-clone-options.c: In function ‘create_remote_wrapper’: > ../libgit2-glib/ggit-clone-options.c:194:5: error: token ""1.0"" is not valid > in preprocessor expressions > 194 | #if LIBGIT2_SOVERSION >= 28 > | ^ > [11/86] cc -Ilibgit2-glib/libgit2-glib-1.0.so.0.2800.0.p -Ilibgit2-glib > -I../libgit2-glib -I. -I.. -I/usr/include/libmount -I/usr/include/blkid > -I/usr/include/glib-2.0 -I/usr/lib/aarch64-linux-gnu/glib-2.0/include > -fdiagnostics-color=always -pipe -D_FILE_OFFSET_BITS=64 -Wall -Winvalid-pch > -ffast-math -fstrict-aliasing -Wpointer-arith -Wmissing-declarations > -Wformat=2 -Wstrict-prototypes -Wmissing-prototypes -Wnested-externs > -Wold-style-definition -Wdeclaration-after-statement -Wunused -Wuninitialized > -Wshadow -Wmissing-noreturn -Wmissing-format-attribute -Wredundant-decls > -Wlogical-op -Wcast-align -Wno-unused-local-typedefs -Werror=implicit > -Werror=init-self -Werror=main -Werror=missing-braces -Werror=return-type > -Werror=array-bounds -Werror=write-strings -DG_DISABLE_CAST_CHECKS > -DG_DISABLE_CHECKS -g -O2 -fdebug-prefix-map=/<>=. > -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time > -D_FORTIFY_SOURCE=2 -fPIC -pthread -DGIT_SSH=1 '-DG_LOG_DOMAIN="Ggit"' -MD > -MQ libgit2-glib/libgit2-glib-1.0.so.0.2800.0.p/ggit-cherry-pick-options.c.o > -MF > libgit2-glib/libgit2-glib-1.0.so.0.2800.0.p/ggit-cherry-pick-options.c.o.d -o > libgit2-glib/libgit2-glib-1.0.so.0.2800.0.p/ggit-cherry-pick-options.c.o -c > ../libgit2-glib/ggit-cherry-pick-options.c > [12/86] cc -Ilibgit2-glib/libgit2-glib-1.0.so.0.2800.0.p -Ilibgit2-glib > -I../libgit2-glib -I. -I.. -I/usr/include/libmount -I/usr/include/blkid > -I/usr/include/glib-2.0 -I/usr/lib/aarch64-linux-gnu/glib-2.0/include > -fdiagnostics-color=always -pipe -D_FILE_OFFSET_BITS=64 -Wall -Wi
Bug#971563: marked as done (libgit2-glib: libgit2 1.0 transition)
Your message dated Sat, 05 Dec 2020 23:49:09 + with message-id and subject line Bug#971563: fixed in libgit2-glib 0.99.0.1-1 has caused the Debian Bug report #971563, regarding libgit2-glib: libgit2 1.0 transition 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.) -- 971563: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=971563 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: libgit2-glib Version: 0.28.0.1-2 Severity: important Dear Maintainer, libgit2 1.0 is now available in experimental. Please make sure your package is ready for this version by the time we upload this package to unstable in one to two weeks. The severity of this report will be raised to serious once libgit2 1.0 is uploaded to unstable. Thanks Ximin -- System Information: Debian Release: bullseye/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable-debug'), (500, 'testing-debug'), (500, 'stable'), (300, 'unstable'), (100, 'experimental'), (1, 'experimental-debug') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.7.0-1-amd64 (SMP w/4 CPU threads) Locale: LANG=en_GB.utf8, LC_CTYPE=en_GB.utf8 (charmap=UTF-8), LANGUAGE=en_GB:en Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled --- End Message --- --- Begin Message --- Source: libgit2-glib Source-Version: 0.99.0.1-1 Done: Simon McVittie We believe that the bug you reported is fixed in the latest version of libgit2-glib, 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. Simon McVittie (supplier of updated libgit2-glib 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, 05 Dec 2020 22:23:05 + Source: libgit2-glib Architecture: source Version: 0.99.0.1-1 Distribution: unstable Urgency: medium Maintainer: Debian GNOME Maintainers Changed-By: Simon McVittie Closes: 971563 976541 Changes: libgit2-glib (0.99.0.1-1) unstable; urgency=medium . * Team upload * New upstream release - Compatible with libgit2 1.0 (Closes: #971563, #976541) * Update symbols file for new API * Add patches from upstream to fix VAPI installation Checksums-Sha1: 245007fa3f9e21d01ee6f28d51732c6ef8480639 2713 libgit2-glib_0.99.0.1-1.dsc 45b3eca14193062ea9db769e75bf687e5ad88331 140996 libgit2-glib_0.99.0.1.orig.tar.xz 1db5200552388b5fec83612c662b2f2389c6f75d 12012 libgit2-glib_0.99.0.1-1.debian.tar.xz 2c16fd588df6fbba618dd0eba43df816eb1924f7 8070 libgit2-glib_0.99.0.1-1_source.buildinfo Checksums-Sha256: f1721d8dc1aacb682f9139fee89274b645ab5614cb40e19173b8d66782fa035e 2713 libgit2-glib_0.99.0.1-1.dsc e05a75c444d9c8d5991afc4a5a64cd97d731ce21aeb7c1c651ade1a3b465b9de 140996 libgit2-glib_0.99.0.1.orig.tar.xz 68ef728e6e61403f064d67276ed350f869096ed8e70acc4c4482441d73894b07 12012 libgit2-glib_0.99.0.1-1.debian.tar.xz e83938250a543c6ffccadbfc258c7fd1d323b1e0f022a0d581f10fcaf760c645 8070 libgit2-glib_0.99.0.1-1_source.buildinfo Files: 211d453c62a1eb1faac6973aedf6f078 2713 libs optional libgit2-glib_0.99.0.1-1.dsc 0507d588f149f7b002256e5e8e733156 140996 libs optional libgit2-glib_0.99.0.1.orig.tar.xz 1d31529176c622d848031bb80b9bce3a 12012 libs optional libgit2-glib_0.99.0.1-1.debian.tar.xz 299804ed611efcebb93aa843715e1a09 8070 libs optional libgit2-glib_0.99.0.1-1_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEENuxaZEik9e95vv6Y4FrhR4+BTE8FAl/MF3UACgkQ4FrhR4+B TE/NaA/+PFG5BcTKpGxwo3i4keAVoXeJQlE8DdDWmUglpfc2YFL9req5podgMHiO mMIhS5yx5OX0d8SVmtjRg/yyGayasIWVGkd+5U1ynDujHRrhxmUxvHrveow9mMe6 zuCgEOPunMD9vo00kDCH81z4PuxIYJHOpIRPFL317HMxi0XhiNglhLLi/pCdb1GE R3aJ2rJcf36bP8JDeSlRZEGWxbGdzSBLx5m2XDucioy7E5iX47v8bY/LZv9xNauE c4NDHTGSSdLDzi+ddYDitnjNVTfwcZ06m2UGkRBa/IhqG6BqRqZMOiMNoB5D0kpz KEAQCn91VenTbpjCZS0WFX0Q6tSe9bmZIUsRmsuwSRZcPCdu8b2+mPXW6WcKcF/3 YLdc8hzORgauxY5uTmzSa6LZHcmfIEgH5L1SkX3jOIuQDK9gv6i6nUwOTetTefKp oBsvjm6ab5ecJzD+JiCI2+mcropBimrctR1PC1mAx6eyl9PIjTqJHfkqj5zTp0Du uU9UJBUTMfqv7etjLvzB8evWpwi7TqJg5haRe/MOsey+ikBaZ4fZtP9b0TK2WbMO vkhL2zzLNsmcP/1GMlqK2ZoSB8ML1hKVMtPB7ztLt1jR0QtaF7YLroXqm1x1SVNz
Processed: Re: Should libhal1-flash be shipped in bullseye?
Processing commands for cont...@bugs.debian.org: > severity 972870 normal Bug #972870 [ftp.debian.org] RM: hal-flash -- RoQA; No longer maintained and replaced by HTML5(DRM) Severity set to 'normal' from 'serious' > stop Stopping processing here. Please contact me if you need assistance. -- 972870: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=972870 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#976567: libhmsbeagle: FTBFS: GPUInterface.h:221:27: error: there are no arguments to ‘malloc’ that depend on a template parameter, so a declaration of ‘malloc’ must be available [-fpermissive]
On 05/12/2020 20:26, Andreas Tille wrote: Control: tags -1 help Hi, I need to admit that I have no idea why this error occures on arm64. According to reproducible builds, it's also happening on i386 and armhf, it's showing a pass for amd64 but that could just be because it hasn't been tested for a while (I've just hit the re-test button) Any hint would be welcome Looks like you need to add #include to libhmsbeagle/GPU/GPUInterface.h I would guess stdlib.h was previously pulled in implicitly by some other header and no longer is.
Processed: Re: Should libhal1-flash be shipped in bullseye?
Processing commands for cont...@bugs.debian.org: > retitle 972870 RM: hal-flash -- RoQA; No longer maintained and replaced by > HTML5(DRM) Bug #972870 [ftp.debian.org] RM: libhal1-flash -- RoQA; No longer maintained and replaced by HTML5(DRM) Changed Bug title to 'RM: hal-flash -- RoQA; No longer maintained and replaced by HTML5(DRM)' from 'RM: libhal1-flash -- RoQA; No longer maintained and replaced by HTML5(DRM)'. > tags 972870 - bullseye sid Bug #972870 [ftp.debian.org] RM: hal-flash -- RoQA; No longer maintained and replaced by HTML5(DRM) Removed tag(s) sid and bullseye. > thanks Stopping processing here. Please contact me if you need assistance. -- 972870: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=972870 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#975584: marked as done (consul: CVE-2020-28053)
Your message dated Sat, 05 Dec 2020 22:48:33 + with message-id and subject line Bug#975584: fixed in consul 1.8.6+dfsg1-1 has caused the Debian Bug report #975584, regarding consul: CVE-2020-28053 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.) -- 975584: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=975584 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: consul Version: 1.7.4+dfsg1-1 Severity: grave Tags: security upstream Forwarded: https://github.com/hashicorp/consul/issues/9240 X-Debbugs-Cc: car...@debian.org, Debian Security Team Hi, The following vulnerability was published for consul. CVE-2020-28053[0]: | HashiCorp Consul and Consul Enterprise 1.2.0 up to 1.8.5 allowed | operators with operator:read ACL permissions to read the Connect CA | private key configuration. Fixed in 1.6.10, 1.7.10, and 1.8.6. If you fix the vulnerability please also make sure to include the CVE (Common Vulnerabilities & Exposures) id in your changelog entry. For further information see: [0] https://security-tracker.debian.org/tracker/CVE-2020-28053 https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-28053 [1] https://github.com/hashicorp/consul/issues/9240 Please adjust the affected versions in the BTS as needed. Regards, Salvatore --- End Message --- --- Begin Message --- Source: consul Source-Version: 1.8.6+dfsg1-1 Done: Arnaud Rebillout We believe that the bug you reported is fixed in the latest version of consul, 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. Arnaud Rebillout (supplier of updated consul 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, 03 Dec 2020 14:22:00 +0700 Source: consul Architecture: source Version: 1.8.6+dfsg1-1 Distribution: unstable Urgency: medium Maintainer: Debian Go Packaging Team Changed-By: Arnaud Rebillout Closes: 964873 975584 Changes: consul (1.8.6+dfsg1-1) unstable; urgency=medium . [ Dmitry Smirnov ] * New upstream release. * Build-Depends: + golang-github-coreos-go-oidc-dev + golang-github-patrickmn-go-cache-dev + golang-golang-x-time-dev (>= 0.0+git20200630~) = golang-github-hashicorp-go-memdb-dev (>= 1.2.1~) = golang-github-hashicorp-memberlist-dev (>= 0.2.2~) = golang-github-hashicorp-serf-dev (>= 0.9.4~) = golang-github-mitchellh-cli-dev (>= 1.1.1~) = golang-github-mitchellh-go-testing-interface-dev (>= 1.14.1~) + procps * fixed hclog-related FTBFS (Closes: #964873). . [ Arnaud Rebillout ] * New upstream release [1.8.6] (Closes: #975584). * Update patches * Add upstream git details, feed it to the build command Checksums-Sha1: d111ab672bd82cc61d370fe5a38f6ba35067fc15 5800 consul_1.8.6+dfsg1-1.dsc e09c539f31853e6f4969f16814663a08bfc4d65b 18434720 consul_1.8.6+dfsg1.orig.tar.xz b287f0de1f5ec06cf991995a08a53a62af3c22c1 21664 consul_1.8.6+dfsg1-1.debian.tar.xz Checksums-Sha256: 8678f8426bef510fd764671008fbd0bd31b4089d9419d58e062b93c9d102e3fe 5800 consul_1.8.6+dfsg1-1.dsc 91441eded2c935b7c0e978d0a85a6b3c212aabdd2c23fb49fb61367b50468b71 18434720 consul_1.8.6+dfsg1.orig.tar.xz 7a6ddb3de3fa764013894ef6d05029395a4673331ee13d81f7698fe1367126b3 21664 consul_1.8.6+dfsg1-1.debian.tar.xz Files: 4bd5e5936cb2bbdc34a37ae669451f32 5800 devel optional consul_1.8.6+dfsg1-1.dsc f0129cfbc0325931ac1096f5614e3382 18434720 devel optional consul_1.8.6+dfsg1.orig.tar.xz 68d139a0f46ce36a6937b9931c280541 21664 devel optional consul_1.8.6+dfsg1-1.debian.tar.xz -BEGIN PGP SIGNATURE- iQJIBAEBCgAyFiEEMN59F2OrlFLH4IJQSadpd5QoJssFAl/MClcUHHNpcmV0YXJ0 QGRlYmlhbi5vcmcACgkQSadpd5QoJsseyxAAzx9BeFeDiJ1EXglVSM4A4EnOtY8n T1yJiHCYjwYSD+EhY6FM7hYKiKdRkI6CIV0M1TWW0Y5p8mlOkekPC80blfRT+5Yq PipawIMJBOtbLEGPlzCdgLGWVEfqq7kL2waq7cg+g1ZpLbvwNmDP1waCh2T8QeiM bpFgB/iFp84T1d4vbYv4JMQIFGEPsLWH7rii7s+nnwdg0/l1VFbcOJhYpBCM+TYv fr6z9Bl7ObH2c/2ZrfJKXu4yTgRHBd095It4/s0DuyvSAfTfKHh9QLT/yyZwstRW 1w9D2jjxKAu3vhRI6l3uvf71XNHrRhjjA1okVrxnp2Lm01GUtzSc079kgrIxuk/V QWVqRhVUQm/DoXRZMkw83SZUzkYWzNA3/AbJCwN26W6wY5Fnd5tOSXfi/vTqdWm+
Bug#976436: marked as done (octave-ltfat-common,octave-ltfat: both ship /usr/share/octave/packages/ltfat-2.3.1/*)
Your message dated Sat, 05 Dec 2020 22:35:50 + with message-id and subject line Bug#976436: fixed in octave-ltfat 2.3.1+dfsg-6 has caused the Debian Bug report #976436, regarding octave-ltfat-common,octave-ltfat: both ship /usr/share/octave/packages/ltfat-2.3.1/* to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 976436: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=976436 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: octave-ltfat-common,octave-ltfat Version: 2.3.1+dfsg-5 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package failed to install because it tries to overwrite other packages files. >From the attached log (scroll to the bottom...): Preparing to unpack .../octave-ltfat_2.3.1+dfsg-5_amd64.deb ... Unpacking octave-ltfat (2.3.1+dfsg-5) ... dpkg: error processing archive /var/cache/apt/archives/octave-ltfat_2.3.1+dfsg-5_amd64.deb (--unpack): trying to overwrite '/usr/share/octave/packages/ltfat-2.3.1/AUTHORS', which is also in package octave-ltfat-common 2.3.1+dfsg-5 dpkg-deb: error: paste subprocess was killed by signal (Broken pipe) Errors were encountered while processing: /var/cache/apt/archives/octave-ltfat_2.3.1+dfsg-5_amd64.deb execute_before_dh_installdeb-indep is supposed to move stuff around from debian/octave-ltfat, but that target is not being run during a separate binary-arch build. cheers, Andreas octave-ltfat-common=2.3.1+dfsg-5_octave-ltfat=2.3.1+dfsg-5.log.gz Description: application/gzip --- End Message --- --- Begin Message --- Source: octave-ltfat Source-Version: 2.3.1+dfsg-6 Done: =?utf-8?q?Rafael_Laboissi=C3=A8re?= We believe that the bug you reported is fixed in the latest version of octave-ltfat, 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. Rafael Laboissière (supplier of updated octave-ltfat 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, 05 Dec 2020 12:12:46 -0300 Source: octave-ltfat Architecture: source Version: 2.3.1+dfsg-6 Distribution: experimental Urgency: medium Maintainer: Debian Octave Group Changed-By: Rafael Laboissière Closes: 976436 Changes: octave-ltfat (2.3.1+dfsg-6) experimental; urgency=medium . * d/rules: Remove the arch-indep files for the octave-ltfat package (Closes: #976436) Checksums-Sha1: a14ed9613ebc18d01c2b8021f839bd3b1d223aca 2181 octave-ltfat_2.3.1+dfsg-6.dsc 54de964aebd362536490677fa5f1e5fa7e642423 9236 octave-ltfat_2.3.1+dfsg-6.debian.tar.xz 13d41406a0bafc3a12575c03b0e0ad4bf3db5567 21921 octave-ltfat_2.3.1+dfsg-6_amd64.buildinfo Checksums-Sha256: 68b44e74c05385287b20ad84a429eae84d027bdc91695f71b9ccb34950bf50dc 2181 octave-ltfat_2.3.1+dfsg-6.dsc a30fe454f47761bc98ee01bf2a161872869e2d36d6a62601604fc2b8331976ab 9236 octave-ltfat_2.3.1+dfsg-6.debian.tar.xz fcb69b83c4c6eddac9f880da44feda9a297b7565bd678e156a248781a889558d 21921 octave-ltfat_2.3.1+dfsg-6_amd64.buildinfo Files: b8de3c59c3aba4e32cf1ab3d54ed7e73 2181 math optional octave-ltfat_2.3.1+dfsg-6.dsc ee13d5ca06d8f143e2fd550b3cc8b3eb 9236 math optional octave-ltfat_2.3.1+dfsg-6.debian.tar.xz 6063511dd438a7889666765bb22c293d 21921 math optional octave-ltfat_2.3.1+dfsg-6_amd64.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEEP0ZDkUmP6HS9tdmPISSqGYN4XJAFAl/L+y0ACgkQISSqGYN4 XJAr3hAAhBcwIMqJH7Odb6DEYJiFr3ZKZ6zY7C88bL+6j+/Q7r5osj3lshqYiPEx NkVM0g3OvDy6kzWCvvBaaTogJWDLnxzyCxr0xdigohVohPl84T0I8vT5jKxCCExp ImNa6C5AlPnfJngS2YsMa38c4ASHIO5VHdvhrFmfnb7MaC0A8GXPbdn2prSs0Prl zHpRZcPoE36UZKrWK4+ELHJ5SaNfKOxIEG7yp/2vetHNkJEb8wVgDawLWnIqMTT3 MnPuop4bCD/7yIWyRIg5ZCu23g16Y52BbOVfSZw6pBMuk+5L2cnFKUCYgG8kkfSm 3/esE24joillU8eug47gqdqYnsnPf0kKgl5I74UkFiu6b0Du+0HKANu+WuaxUurr OOWty+DfLohTmYolVH/2u0PMDLT2T+dbm90n1fnJKpkC/+CWpO1qHtnzJj9d5nms wL2QqWqtfvEOodSe4Hzy0dY7/ouGjrxwjkKOv1JfAp8bAYvDSR+aAxrtUPBbGNB+ tKGLjbm/HwMKkF5XvW9dEhWvXxoeoqmZjkH1TAR06M5yjoKBuO57OIQVF4omu9MO VtmKQ/baA509LZToGOOJVzox9iVJcSrokTI50DnrqKPGULF1n6ZdmfmWq+cdvi07 Ht3JyiwmE15KnY91eFygld6CwyXSyBCGDfRzMjrk9dgrdWgYNzo=
Processed: forwarded dssp 4 issue upstream
Processing commands for cont...@bugs.debian.org: > forwarded 976542 https://github.com/biopython/biopython/issues/3433 Bug #976542 [src:python-biopython] python-biopython: FTBFS: AssertionError: 0 != 24 Set Bug forwarded-to-address to 'https://github.com/biopython/biopython/issues/3433'. > tags 976542 + pending upstream Bug #976542 [src:python-biopython] python-biopython: FTBFS: AssertionError: 0 != 24 Added tag(s) upstream and pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 976542: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=976542 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Bug#975584 marked as pending in consul
Processing control commands: > tag -1 pending Bug #975584 [src:consul] consul: CVE-2020-28053 Ignoring request to alter tags of bug #975584 to the same tags previously set -- 975584: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=975584 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#976619: ts-node: required modules not declared as dependencies
Package: ts-node Version: 9.0.0-1 Severity: serious Justification: Policy 3.5 -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 ts-node package lacks declaring its runtime dependencies: node-arg node-diff node-make-error node-source-map-support node-yn (yes, I notice that ts-node is only in experimental for now - I am just eager to play with it: it is needed for recent eslint). - Jonas -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEn+Ppw2aRpp/1PMaELHwxRsGgASEFAl/MB/8ACgkQLHwxRsGg ASFhSBAAlMIFTKmL+Uix01Akrj+lX0qfIGHZmvcANj7dl4zOuimVd8hMlqAxRKFs 2jt3mwp6m3jo2FW3Qyyon4RSkBQUUXMebBfn/fwiqo1SMiZLtIV02SK1lWuWMuIu ORZuCiHAwUZiVior2Wi1M7roJSTgYO57bzFT+tmjup5lzf3QQCKH8elsWWTtUFT7 sm2vVMK5BnDvZ3nZpUTJ25H6MbkidyQBqVGx/oR2bcnlEwRVTRiUhpRkcz1Z3xGW v2cGR+ou2a1ig7F/BsXJETLWPo9NjAmKPVpjx47qa1zEYuml6XOkLvqeODR06vYt XTVscDSz2/1B4g/xmmx/BHYTN9b4BmH5uSAu+o4F0zB06Prb1Kz9IS6lbfYBdwwn un93crppIopWivtT8UXGbG3NaOf//9xp3C04RhjQI41B6127gZXMw1wYmsuSYrdp +c/oLmFsNPYbp94ID3FSpZ2DfVENKie3F4SGKboDeZOlC6yckPZzu7I5RHHRzcKA UywkoAN77orMIU6RJyJn62k46pzMRwSy3mtoYP7O8wn83cluRLpMVfnQBnx8MB2+ T+HyQG7Urcm7xfHrOJpTK+pxMJ8wmxmITuL5NTzida2u7q7aUyFPN1UyBXCblBaF qt4Gn0rDo7WDJ5W4dM0J/wB1f12/CdMYF2rnCEBjvcv+fogd0+k= =DKy+ -END PGP SIGNATURE-
Bug#975584: marked as pending in consul
Control: tag -1 pending Hello, Bug #975584 in consul 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/go-team/packages/consul/-/commit/9650adb23f7363d8e0d5a19522542e3be78b9f72 New upstream release (Closes: #975584) (this message was generated automatically) -- Greetings https://bugs.debian.org/975584
Bug#976436: marked as pending in octave-ltfat
Control: tag -1 pending Hello, Bug #976436 in octave-ltfat 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/pkg-octave-team/octave-ltfat/-/commit/b0cb4862e4f8766fae48144daea9d807f525116f d/rules: Remove the arch-indep files for the octave-ltfat package Closes: #976436 (this message was generated automatically) -- Greetings https://bugs.debian.org/976436
Processed: Bug#976436 marked as pending in octave-ltfat
Processing control commands: > tag -1 pending Bug #976436 [octave-ltfat-common,octave-ltfat] octave-ltfat-common,octave-ltfat: both ship /usr/share/octave/packages/ltfat-2.3.1/* Added tag(s) pending. -- 976436: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=976436 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#976545: Build failures on arm64 are release critical now
Control: severity -1 normal Hello, The package builds fine on amd64. I don't think it is correct to use severity serious in this case because ufoai-maps is an arch:all package. The same is true for Java packages. If we want to make this a release goal (making arch all packages buildable on all supported architectures), it should have been discussed months before the freeze. I saw that you have lowered the severity on some packages already. Can we agree to use severity normal for build failures on other architectures than amd64 if the package in question is arch:all? Regards, Markus signature.asc Description: This is a digitally signed message part
Processed: Build failures on arm64 are release critical now
Processing control commands: > severity -1 normal Bug #976545 [src:ufoai-maps] ufoai-maps: FTBFS: "mkdir /sbuild-nonexistent" failed, reason: "Permission denied"."mkdir /sbuild-nonexistent/.ufoai" failed, reason: "No such file or directory"."mkdir /sbuild-nonexistent/.ufoai/2.5" failed, reason: "No such file or directory"."mkdir /sbuild-nonexistent/.ufoai/2.5/base" failed, reason: "No such file or directory".Adding game dir: /sbuild-nonexistent/.ufoai/2.5/base Severity set to 'normal' from 'serious' -- 976545: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=976545 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#976492: marked as pending in bochs
Control: tag -1 pending Hello, Bug #976492 in bochs reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/debian/bochs/-/commit/acaf70cc296a979fb08dfa105f46e93db052cb15 Use cross-binutils tools when building rombios32 Closes: #976492 (this message was generated automatically) -- Greetings https://bugs.debian.org/976492
Processed: Bug#976492 marked as pending in bochs
Processing control commands: > tag -1 pending Bug #976492 [src:bochs] bochs: FTBFS on arm64: ld: cannot represent machine `i386' Added tag(s) pending. -- 976492: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=976492 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Re: Bug#976541: libgit2-glib: FTBFS: ../libgit2-glib/ggit-clone-options.c:152:5: error: token ""1.0"" is not valid in preprocessor expressions
Processing control commands: > tags -1 + pending fixed-upstream Bug #976541 [src:libgit2-glib] libgit2-glib: FTBFS: ../libgit2-glib/ggit-clone-options.c:152:5: error: token ""1.0"" is not valid in preprocessor expressions Added tag(s) fixed-upstream and pending. -- 976541: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=976541 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#976541: libgit2-glib: FTBFS: ../libgit2-glib/ggit-clone-options.c:152:5: error: token ""1.0"" is not valid in preprocessor expressions
Control: tags -1 + pending fixed-upstream On Sat, 05 Dec 2020 at 20:58:26 +0100, Lucas Nussbaum wrote: > It also fails on amd64 This is caused by API changes in libgit2 (#971563). I'm part way through packaging a new upstream version that will fix this. smcv
Bug#975943: Reproducing the problem
A related discussion happened on https://salsa.debian.org/raspi-team/image-specs/-/issues/37 Thanks to the hint by Axel Beckert, I've managed to consistently reproduce the issue: # update-initramfs -u # aptitude reinstall raspi-firmware I still don't know whether the issue is in raspi-firmware or in initramfs- tools, but making it easy to reproduce should hopefully help solving it. Cheers, Diederik signature.asc Description: This is a digitally signed message part.
Bug#976469: This package specifies Architecture:any (or a variant) but FTBFS on arm64 (and not amd64)
Hi, This package specifies Architecture: any (or a variant of it) but currently FTBFS on arm64, while it is currently building fine on amd64. If arm64 is not supposed to be supported by this package, it might be better to specify a subset of architectures, see https://www.debian.org/doc/debian-policy/ch-controlfields.html#s-f-architecture For reference, a list of packages (and their Architecture field) falling in this category: bcachefs-tools_0.1+git20201025.742dbbdb-1_unstable.log:Architecture: linux-any blastem_0.6.3.3-3_unstable.log:Architecture: any bmtk_0.0+git20201018.018da0a+ds-1_unstable.log:Architecture: any all bochs_2.6.11+dfsg-3_unstable.log:Architecture: any all clippoly_0.11-9_unstable.log:Architecture: any dune-pdelab_2.7~20200605-2_unstable.log:Architecture: any all haskell-xml-html-qq_0.1.0.1-2_unstable.log:Architecture: any all kafs-client_0.5-2_unstable.log:Architecture: any libatomic-queue_0.0+git20201007.df79403-2_unstable.log:Architecture: any libecpint_1.0.2-1_unstable.log:Architecture: any libhmsbeagle_3.1.2+dfsg-8_unstable.log:Architecture: linux-any libsis-base-java_18.09~pre1+git20180928.45fbd31+dfsg-1_unstable.log:Architecture: any all libview_0.6.6-2.1_unstable.log:Architecture: any mecat2_0.0+git20200428.f54c542+ds-2_unstable.log:Architecture: any mes_0.22-5_unstable.log:Architecture: any metabat_2.15-2_unstable.log:Architecture: any mojoshader_0.0~hg1314+dfsg-1.1_unstable.log:Architecture: any ngmlr_0.2.7+dfsg-2_unstable.log:Architecture: any ompl_1.4.2+ds1-6_unstable.log:Architecture: any all python-parasail_1.2.1-1_unstable.log:Architecture: any r-cran-s2_1.0.3-1_unstable.log:Architecture: any rust-generator_0.6.20-2_unstable.log:Architecture: any rust-mach-o-sys_0.1.1-3_unstable.log:Architecture: any scrappie_1.4.2-3_unstable.log:Architecture: any siconos_4.3.0+dfsg-3_unstable.log:Architecture: any sidplay_2.0.9-6_unstable.log:Architecture: any spades_3.13.1+dfsg-2_unstable.log:Architecture: any tinyarray_1.2.3-2_unstable.log:Architecture: any xtpcpp_0.4.9-1_unstable.log:Architecture: any Lucas
Processed: Re: Bug#976525: plast: FTBFS: SmallGapHitIteratorSSE8.cpp:294:5: error: ‘__m128i’ was not declared in this scope
Processing control commands: > severity -1 minor Bug #976525 [src:plast] plast: FTBFS: SmallGapHitIteratorSSE8.cpp:294:5: error: ‘__m128i’ was not declared in this scope Severity set to 'minor' from 'serious' -- 976525: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=976525 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#976525: plast: FTBFS: SmallGapHitIteratorSSE8.cpp:294:5: error: ‘__m128i’ was not declared in this scope
Control: severity -1 minor On 05/12/20 at 13:26 +0100, Lucas Nussbaum wrote: > Source: plast > Version: 2.3.2+dfsg-3 > 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). It doesn't fail on amd64. I missed the fact that plast was already specifying Architecture: any-amd64 all so this only affects building arch:all packages. Unfortunately, we don't have a way to say that arch:all packages should be built on a specific architecture. So I'm downgrading this bug. Lucas
Bug#969839: [Pkg-rust-maintainers] Bug#969839: Bug#973298: Bug#969839: rust-failure: Should rust-failure be removed from unstable?
On 15973 March 1977, Sylvestre Ledru wrote: So you are right, thanks for spotting my mistake, which is because I indeed only check if dak rm would cause any issues. I agree that we thus likely cannot remove it for now from unstable. It has been removed despite this comment. This causes a bunch of breakage. At the request of the release-team, we re-injected the packages which were still in testing back into unstable. Should be back at the next dinstall. Thanks Mark, and for the rest: If you don't want us to act on a rm bug, tag it moreinfo (if its likely to need action later) *or* close it. That ensures that it won't be acted on, as the interface we mostly use for looking at removals hides those. -- bye, Joerg
Bug#976484: unsigned values cannot be negated
On 05/12/20 at 21:30 +0100, Geert Stappers wrote: > Yes, that should also fail on amd64 ... It does not fail on amd64 (build log attached). Lucas DC-Build-Header: rust-mach-o-sys 0.1.1-3 / 2020-12-05 18:07:02 + DC-Task: type:rebuild-full source:rust-mach-o-sys version:0.1.1-3 chroot:unstable esttime:28 logfile:/tmp/rust-mach-o-sys_0.1.1-3_unstable.log modes: DC-Sbuild-call: su user42 -c 'sbuild -n -A -s --force-orig-source --apt-update -d unstable -v --no-run-lintian rust-mach-o-sys_0.1.1-3' sbuild (Debian sbuild) 0.78.1 (09 February 2019) on ip-172-31-9-164.eu-central-1.compute.internal +==+ | rust-mach-o-sys 0.1.1-3 (amd64) Sat, 05 Dec 2020 18:07:03 + | +==+ Package: rust-mach-o-sys Version: 0.1.1-3 Source Version: 0.1.1-3 Distribution: unstable Machine Architecture: amd64 Host Architecture: amd64 Build Architecture: amd64 Build Type: full I: NOTICE: Log filtering will replace 'var/run/schroot/mount/sid-amd64-sbuild-4956d765-6352-4e01-9c06-607c86533ce4' with '<>' I: NOTICE: Log filtering will replace 'build/rust-mach-o-sys-pxXV0L/resolver-8ecqZq' with '<>' +--+ | Update chroot| +--+ Hit:1 http://127.0.0.1:12990/debian sid InRelease Reading package lists... Reading package lists... Building dependency tree... Calculating upgrade... 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. +--+ | Fetch source files | +--+ Check APT - Checking available source versions... Download source files with APT -- Reading package lists... NOTICE: 'rust-mach-o-sys' packaging is maintained in the 'Git' version control system at: https://salsa.debian.org/rust-team/debcargo-conf.git [src/mach-o-sys] Please use: git clone https://salsa.debian.org/rust-team/debcargo-conf.git [src/mach-o-sys] to retrieve the latest (possibly unreleased) updates to the package. Need to get 84.7 kB of source archives. Get:1 http://127.0.0.1:12990/debian sid/main rust-mach-o-sys 0.1.1-3 (dsc) [1540 B] Get:2 http://127.0.0.1:12990/debian sid/main rust-mach-o-sys 0.1.1-3 (tar) [80.5 kB] Get:3 http://127.0.0.1:12990/debian sid/main rust-mach-o-sys 0.1.1-3 (diff) [2648 B] Fetched 84.7 kB in 0s (540 kB/s) Download complete and in download only mode I: NOTICE: Log filtering will replace 'build/rust-mach-o-sys-pxXV0L/rust-mach-o-sys-0.1.1' with '<>' I: NOTICE: Log filtering will replace 'build/rust-mach-o-sys-pxXV0L' with '<>' +--+ | Install package build dependencies | +--+ Setup apt archive - Merged Build-Depends: debhelper (>= 11), dh-cargo (>= 18), cargo, rustc, libstd-rust-dev, build-essential, fakeroot Filtered Build-Depends: debhelper (>= 11), dh-cargo (>= 18), cargo, rustc, libstd-rust-dev, 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 [405 B] Get:5 copy:/<>/apt_archive ./ Packages [475 B] Fetched 1837 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... The following additional packages will be installed: autoconf automake autopoint autotools-dev bsdextrautils cargo debhelper dh-autoreconf dh-cargo dh-strip-nondeterminism dwz file gettext gettext-base groff-base intltool-debian libarchive-zip-perl libbrotli1 libbsd0 libcroco3 libcurl3-gnutls libdebhelper-perl libedit2 libelf1 libexpat1 libfile-stripnondeterminism-perl libgit2-28 libglib2.0-0 libhttp-parser2.9 libicu67 libldap-2.4-2 libllvm11 libmagic-mgc libmagic1 libmbedcrypto3 libmbedtls12 libmbedx509-0 libncursesw6 libnghttp2-14 libpipeline1 libpsl5 libpython3-stdlib libpython3.9-minimal libpython3.9-stdlib libreadline8 librtmp1 libsasl2-2 libsasl2-modules-db libsigsegv2 libsqlite3-0 libssh2-1 libstd-rust-1.48 libstd-rust-dev libsub-override-perl libtool libuchardet0 libxml2 libz3-4 m4 mailcap man-db media-types mime-support po-debconf
Bug#976576: Bug#976588: rapmap: FTBFS: cc: error: unrecognized command-line option ‘-msse4.1’
Control: severity 976588 minor Control: severity 976576 minor Control: retitle 976588 rapmap: FTBFS on arm64 (when trying to build arch:all) Control: retitle 976576 spring: FTBFS on arm64 (when trying to build arch:all) Hi, This package builds Arch:all binary packages, but they cannot be built on arm64. I don't think we have a good way to indicate that. The Architecture: field already restricts the arch-specific binary packages to something that does not include arm64. For reference, here are some other packages I ran into in the same case: bolt-lmm_2.3.4+dfsg-2_unstable.log:Architecture: amd64 i386 ppc64el all gkl_0.8.6+dfsg-2_unstable.log:Architecture: all amd64 libosl_0.8.0-3_unstable.log:Architecture: i386 amd64 all rapmap_0.15.0+dfsg-1_unstable.log:Architecture: amd64 all reprozip_1.0.16-1_unstable.log:Architecture: all amd64 i386 x32 spring_104.0+dfsg-7_unstable.log:Architecture: amd64 i386 all Lucas
Processed: Re: Bug#976588: rapmap: FTBFS: cc: error: unrecognized command-line option ‘-msse4.1’
Processing control commands:
> severity 976588 minor
Bug #976588 [src:rapmap] rapmap: FTBFS: cc: error: unrecognized command-line
option ‘-msse4.1’
Severity set to 'minor' from 'serious'
> severity 976576 minor
Bug #976576 [src:spring] spring: FTBFS: {standard input}:37: Error: unknown
mnemonic `fstcw' -- `fstcw [sp,18]'
Severity set to 'minor' from 'serious'
> retitle 976588 rapmap: FTBFS on arm64 (when trying to build arch:all)
Bug #976588 [src:rapmap] rapmap: FTBFS: cc: error: unrecognized command-line
option ‘-msse4.1’
Changed Bug title to 'rapmap: FTBFS on arm64 (when trying to build arch:all)'
from 'rapmap: FTBFS: cc: error: unrecognized command-line option ‘-msse4.1’'.
> retitle 976576 spring: FTBFS on arm64 (when trying to build arch:all)
Bug #976576 [src:spring] spring: FTBFS: {standard input}:37: Error: unknown
mnemonic `fstcw' -- `fstcw [sp,18]'
Changed Bug title to 'spring: FTBFS on arm64 (when trying to build arch:all)'
from 'spring: FTBFS: {standard input}:37: Error: unknown mnemonic `fstcw' --
`fstcw [sp,18]''.
--
976576: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=976576
976588: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=976588
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#975770: marked as done (python3-wokkel: wrong dependency on python3-cryptodome)
Your message dated Sat, 05 Dec 2020 20:48:53 + with message-id and subject line Bug#975748: fixed in wokkel 18.0.0-3.1 has caused the Debian Bug report #975748, regarding python3-wokkel: wrong dependency on python3-cryptodome 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.) -- 975748: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=975748 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: sat-pubsub Version: 0.4.0~hg422.c21f31355ab9-1 Severity: serious Justification: FTBFS on amd64 Tags: bullseye sid ftbfs Usertags: ftbfs-20201125 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 (= 11), dh-python, python3-all, > python3-psycopg2, python3-setuptools, python3-simplejson, python3-wokkel, > sat-xmpp-core (>= 0.8.0~), build-essential, fakeroot > Filtered Build-Depends: debhelper-compat (= 11), dh-python, python3-all, > python3-psycopg2, python3-setuptools, python3-simplejson, python3-wokkel, > sat-xmpp-core (>= 0.8.0~), 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 [433 B] > Get:5 copy:/<>/apt_archive ./ Packages [517 B] > Fetched 1907 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: > python3-wokkel : Depends: python3-cryptodome but it is not installable > 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/11/25/sat-pubsub_0.4.0~hg422.c21f31355ab9-1_unstable.log A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! About the archive rebuild: The rebuild was done on EC2 VM instances from Amazon Web Services, using a clean, minimal and up-to-date chroot. Every failed build was retried once to eliminate random failures. --- End Message --- --- Begin Message --- Source: wokkel Source-Version: 18.0.0-3.1 Done: Martin We believe that the bug you reported is fixed in the latest version of wokkel, 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. Martin (supplier of updated wokkel 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, 05 Dec 2020 20:32:17 + Source: wokkel Architecture: source Version: 18.0.0-3.1 Distribution: unstable Urgency: medium Maintainer: Angel Abad Changed-By: Martin Closes: 975748 Changes: wokkel (18.0.0-3.1) unstable; urgency=medium . * Non-maintainer upload. * Fix typo in debian/control (Closes: #975748) Checksums-Sha1: 4f2a69ec4e77be563e2081ddfb905183d43c3b24 2044 wokkel_18.0.0-3.1.dsc 506901dfc496be7c83102e0083f7f513b2fc92b4 3624 wokkel_18.0.0-3.1.debian.tar.xz 267c6601ae6a1ff4ad93685832067409a6b8cc16 6827 wokkel_18.0.0-3.1_amd64.buildinfo Checksums-Sha256:
Bug#975748: marked as done (python3-wokkel: wrong dependency on python3-cryptodome)
Your message dated Sat, 05 Dec 2020 20:48:53 + with message-id and subject line Bug#975748: fixed in wokkel 18.0.0-3.1 has caused the Debian Bug report #975748, regarding python3-wokkel: wrong dependency on python3-cryptodome 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.) -- 975748: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=975748 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: salutatoi Version: 0.8.0~hg3247.f981c0e99220-2 Severity: serious Justification: FTBFS on amd64 Tags: bullseye sid ftbfs Usertags: ftbfs-20201125 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 (= 11), dh-python, markdown, python3, > python3-lxml, python3-setuptools, python3-shortuuid, python3-twisted, > python3-wokkel, python3-xdg, build-essential, fakeroot > Filtered Build-Depends: debhelper-compat (= 11), dh-python, markdown, > python3, python3-lxml, python3-setuptools, python3-shortuuid, > python3-twisted, python3-wokkel, python3-xdg, 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 [426 B] > Get:5 copy:/<>/apt_archive ./ Packages [507 B] > Fetched 1890 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: > python3-wokkel : Depends: python3-cryptodome but it is not installable > 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/11/25/salutatoi_0.8.0~hg3247.f981c0e99220-2_unstable.log A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! About the archive rebuild: The rebuild was done on EC2 VM instances from Amazon Web Services, using a clean, minimal and up-to-date chroot. Every failed build was retried once to eliminate random failures. --- End Message --- --- Begin Message --- Source: wokkel Source-Version: 18.0.0-3.1 Done: Martin We believe that the bug you reported is fixed in the latest version of wokkel, 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. Martin (supplier of updated wokkel 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, 05 Dec 2020 20:32:17 + Source: wokkel Architecture: source Version: 18.0.0-3.1 Distribution: unstable Urgency: medium Maintainer: Angel Abad Changed-By: Martin Closes: 975748 Changes: wokkel (18.0.0-3.1) unstable; urgency=medium . * Non-maintainer upload. * Fix typo in debian/control (Closes: #975748) Checksums-Sha1: 4f2a69ec4e77be563e2081ddfb905183d43c3b24 2044 wokkel_18.0.0-3.1.dsc 506901dfc496be7c83102e0083f7f513b2fc92b4 3624 wokkel_18.0.0-3.1.debian.tar.xz 267c6601ae6a1ff4ad93685832067409a6b8cc16 6827 wokkel_18.0.0-3.1_amd64.buildinfo Checksums-Sha256:
Bug#976468: This package only builds Arch:all binary packages
Hi, This package only builds Arch:all binary packages. Unfortunately, I don't think that we have a way to indicate that such binary packages must be built on a specific architecture, and thus avoid a failure on arm64. In those cases, building those packages on amd64 works fine, so the bug is limited to building arch:all packages on specific architectures. I pondered downgrading the severity of those bugs, but in some cases, it could indicate severe bugs in other packages, or packaging bugs such as confusing arch:any and arch:all. However, I don't object to someone else downgrading them. For reference, here are the packages I ran into in that category: akuma 976548 backward-cpp 976582 bmagic 976517 dune-localfunctions 976552 golang-github-disintegration-imaging 976565 golang-github-labstack-gommon 976578 golang-github-linuxkit-virtsock 976564 golang-github-montanaflynn-stats 976562 golang-github-rcrowley-go-metrics 976543 golang-github-robertkrimen-otto 976549 golang-github-shirou-gopsutil 976509 golang-google-cloud 976507 jctools 976534 jnr-ffi 976521 libcereal 976585 libmiglayout-java 976546 multiboot 976502 nova 976590 python-fluids 976558 python-ptrace 976468 rapidjson 976536 xenium 976480 xfonts-100dpi 976571 xfonts-75dpi 976471 xfonts-cyrillic 976510 - Lucas
Bug#976408: marked as done (many dependencies in the archive differ by major)
Your message dated Sun, 06 Dec 2020 02:00:15 +0530 with message-id and subject line fixed in last upload has caused the Debian Bug report #976408, regarding many dependencies in the archive differ by major 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.) -- 976408: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=976408 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: node-compression-webpack-plugin Version: 3.0.1-3 Severity: serious Control: affects -1 gitlab Installation of gitlab started failing with the following error. I think this is related to the recent update of node-schema-utils. Webpacking... /usr/share/nodejs/webpack/node_modules/webpack-cli/bin/cli.js:93 throw err; ^ TypeError: (0 , _schemaUtils.validate) is not a function at new CompressionPlugin (/usr/share/nodejs/compression-webpack-plu gin/dist/index.js:40:31) at Object. (/etc/gitlab/webpack.config.js:451:41) at Module._compile (/usr/share/nodejs/webpack/node_modules/v8-compi le-cache/v8-compile-cache.js:194:30) at Object.Module._extensions..js (internal/modules/cjs/loader.js:10 35:10) at Module.load (internal/modules/cjs/loader.js:879:32) at Function.Module._load (internal/modules/cjs/loader.js:724:14) at Module.require (internal/modules/cjs/loader.js:903:19) at require (/usr/share/nodejs/webpack/node_modules/v8-compile-cache /v8-compile-cache.js:161:20) at WEBPACK_OPTIONS (/usr/share/nodejs/webpack/node_modules/webpack- cli/bin/utils/convert-argv.js:114:13) at requireConfig (/usr/share/nodejs/webpack/node_modules/webpack-cl i/bin/utils/convert-argv.js:116:6) at /usr/share/nodejs/webpack/node_modules/webpack-cli/bin/utils/con vert-argv.js:123:17 at Array.forEach () at module.exports (/usr/share/nodejs/webpack/node_modules/webpack-c li/bin/utils/convert-argv.js:121:15) at /usr/share/nodejs/webpack/node_modules/webpack-cli/bin --- End Message --- --- Begin Message --- but wrong bug (#976310) was closed--- End Message ---
Processed: python3-wokkel: wrong dependency on python3-cryptodome
Processing commands for cont...@bugs.debian.org: > reassign 975748 python3-wokkel Bug #975748 [src:salutatoi] salutatoi: FTBFS: build-dependency not installable: python3-cryptodome Bug reassigned from package 'src:salutatoi' to 'python3-wokkel'. No longer marked as found in versions salutatoi/0.8.0~hg3247.f981c0e99220-2. Ignoring request to alter fixed versions of bug #975748 to the same values previously set > retitle 975748 python3-wokkel: wrong dependency on python3-cryptodome Bug #975748 [python3-wokkel] salutatoi: FTBFS: build-dependency not installable: python3-cryptodome Changed Bug title to 'python3-wokkel: wrong dependency on python3-cryptodome' from 'salutatoi: FTBFS: build-dependency not installable: python3-cryptodome'. > reassign 975770 python3-wokkel Bug #975770 [src:sat-pubsub] sat-pubsub: FTBFS: build-dependency not installable: python3-cryptodome Bug reassigned from package 'src:sat-pubsub' to 'python3-wokkel'. No longer marked as found in versions sat-pubsub/0.4.0~hg422.c21f31355ab9-1. Ignoring request to alter fixed versions of bug #975770 to the same values previously set > retitle 975770 python3-wokkel: wrong dependency on python3-cryptodome Bug #975770 [python3-wokkel] sat-pubsub: FTBFS: build-dependency not installable: python3-cryptodome Changed Bug title to 'python3-wokkel: wrong dependency on python3-cryptodome' from 'sat-pubsub: FTBFS: build-dependency not installable: python3-cryptodome'. > merge 975748 975770 Bug #975748 [python3-wokkel] python3-wokkel: wrong dependency on python3-cryptodome Bug #975770 [python3-wokkel] python3-wokkel: wrong dependency on python3-cryptodome Merged 975748 975770 > thanks Stopping processing here. Please contact me if you need assistance. -- 975748: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=975748 975770: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=975770 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: reopen wrongly closed bug
Processing commands for cont...@bugs.debian.org:
> reopen 976310
Bug #976310 {Done: Pirate Praveen } [gitlab]
node-compression-webpack-plugin: TypeError: (0 , _schemaUtils.validate) is not
a function
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
No longer marked as fixed in versions node-css-loader/3.2.1+~cs21.3.8.1-1.
>
End of message, stopping processing here.
Please contact me if you need assistance.
--
976310: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=976310
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Processed: unsigned values cannot be negated
Processing control commands: > retitle -1 rust-mach-o-sys: unsigned values cannot be negated Bug #976484 [src:rust-mach-o-sys] rust-mach-o-sys: FTBFS: dh_auto_test: error: /usr/share/cargo/bin/cargo test --all returned exit code 101 Changed Bug title to 'rust-mach-o-sys: unsigned values cannot be negated' from 'rust-mach-o-sys: FTBFS: dh_auto_test: error: /usr/share/cargo/bin/cargo test --all returned exit code 101'. -- 976484: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=976484 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#976484: unsigned values cannot be negated
Control: retitle -1 rust-mach-o-sys: unsigned values cannot be negated On Sat, Dec 05, 2020 at 02:28:20PM +0100, Lucas Nussbaum wrote: > Source: rust-mach-o-sys > Version: 0.1.1-3 > > 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): > > > > > > -C link-arg=-Wl,-z,relro --remap-path-prefix > > /<>=/usr/share/cargo/registry/mach-o-sys-0.1.1` > > error[E0600]: cannot apply unary operator `-` to type `u8` > > --> src/arch.rs:35:46 > >| > > 35 | pub const INT8_MIN: ::std::os::raw::c_char = -128; > >| cannot apply unary > > operator `-` > >| > >= note: unsigned values cannot be negated > > > > error[E0600]: cannot apply unary operator `-` to type `u8` > > --> src/arch.rs:42:48 > >| > > 42 | pub const UINT64_MAX: ::std::os::raw::c_char = -1; > >|^^ cannot apply unary > > operator `-` > >| > >= note: unsigned values cannot be negated Yes, that should also fail on amd64 ...
Processed: Re: Bug#976567: libhmsbeagle: FTBFS: GPUInterface.h:221:27: error: there are no arguments to ‘malloc’ that depend on a template parameter, so a declaration of ‘malloc’ must be available [-f
Processing control commands: > tags -1 help Bug #976567 [src:libhmsbeagle] libhmsbeagle: FTBFS: GPUInterface.h:221:27: error: there are no arguments to ‘malloc’ that depend on a template parameter, so a declaration of ‘malloc’ must be available [-fpermissive] Added tag(s) help. -- 976567: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=976567 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#976567: libhmsbeagle: FTBFS: GPUInterface.h:221:27: error: there are no arguments to ‘malloc’ that depend on a template parameter, so a declaration of ‘malloc’ must be available [-fpermissive]
Control: tags -1 help
Hi,
I need to admit that I have no idea why this error occures on arm64.
Any hint would be welcome
Andreas.
On Sat, Dec 05, 2020 at 01:21:43PM +0100, Lucas Nussbaum wrote:
> Source: libhmsbeagle
> Version: 3.1.2+dfsg-8
> 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):
> > /bin/bash ../../libtool --tag=CXX --mode=compile g++ -DHAVE_CONFIG_H -I.
> > -I../../libhmsbeagle -I/<> -I/<> -Wdate-time
> > -D_FORTIFY_SOURCE=2 -I/usr/lib/jvm/java-11-openjdk-arm64/include
> > -I/usr/lib/jvm/java-11-openjdk-arm64/include/linux -O3 -std=c++11 -D
> > FW_OPENCL -I/usr/include/CL/include -g -O2
> > -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat
> > -Werror=format-security -c -o libhmsbeagle_opencl_la-OpenCLPlugin.lo `test
> > -f 'OpenCLPlugin.cpp' || echo './'`OpenCLPlugin.cpp
> > libtool: compile: g++ -DHAVE_CONFIG_H -I. -I../../libhmsbeagle
> > -I/<> -I/<> -Wdate-time -D_FORTIFY_SOURCE=2
> > -I/usr/lib/jvm/java-11-openjdk-arm64/include
> > -I/usr/lib/jvm/java-11-openjdk-arm64/include/linux -O3 -std=c++11 -D
> > FW_OPENCL -I/usr/include/CL/include -g -O2
> > -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat
> > -Werror=format-security -c OpenCLPlugin.cpp -fPIC -DPIC -o
> > .libs/libhmsbeagle_opencl_la-OpenCLPlugin.o
> > In file included from /usr/include/CL/cl.h:20,
> > from /usr/include/CL/opencl.h:24,
> > from /<>/libhmsbeagle/GPU/GPUInterface.h:60,
> > from /<>/libhmsbeagle/GPU/BeagleGPUImpl.h:39,
> > from OpenCLPlugin.cpp:8:
> > /usr/include/CL/cl_version.h:22:104: note: ‘#pragma message: cl_version.h:
> > CL_TARGET_OPENCL_VERSION is not defined. Defaulting to 300 (OpenCL 3.0)’
> >22 | #pragma message("cl_version.h: CL_TARGET_OPENCL_VERSION is not
> > defined. Defaulting to 300 (OpenCL 3.0)")
> > |
> >^
> > In file included from /<>/libhmsbeagle/GPU/BeagleGPUImpl.h:39,
> > from OpenCLPlugin.cpp:8:
> > /<>/libhmsbeagle/GPU/GPUInterface.h: In member function ‘void
> > opencl_device::GPUInterface::PrintfDeviceVector(GPUPtr, int, double, int*,
> > Real)’:
> > /<>/libhmsbeagle/GPU/GPUInterface.h:221:27: error: there are
> > no arguments to ‘malloc’ that depend on a template parameter, so a
> > declaration of ‘malloc’ must be available [-fpermissive]
> > 221 | Real* hPtr = (Real*) malloc(sizeof(Real) * length);
> > | ^~
> > /<>/libhmsbeagle/GPU/GPUInterface.h:221:27: note: (if you use
> > ‘-fpermissive’, G++ will accept your code, but allowing the use of an
> > undeclared name is deprecated)
> > make[6]: *** [Makefile:701: libhmsbeagle_opencl_la-OpenCLPlugin.lo] Error 1
>
> The full build log is available from:
>http://qa-logs.debian.net/2020/12/05/libhmsbeagle_3.1.2+dfsg-8_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.
>
> ___
> Debian-med-packaging mailing list
> debian-med-packag...@alioth-lists.debian.net
> https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/debian-med-packaging
--
http://fam-tille.de
Bug#976614: r-bioc-deseq2: autopkgtest dependency check plays bad in Debian migration setup
Source: r-bioc-deseq2 Version: 1.30.0+dfsg-2 Severity: serious X-Debbugs-CC: debian...@lists.debian.org User: debian...@lists.debian.org Usertags: issue Dear maintainer, Your package has an autopkgtest, great. However, apparently you have been waiting for a test dependency to become available and have implemented a check to not forget to remove the overwrite: https://sources.debian.org/src/r-bioc-deseq2/1.30.0+dfsg-2/debian/tests/run-unit-test/#L14 echo "FIXME: Do not delete tests requiring glmGamPoi once r-bioc-glmgampoi is available" if apt-cache show r-bioc-glmgampoi > /dev/null 2>/dev/null ; then echo "Package r-bioc-glmgampoi is available now - do not remove the test requiring it any more" exit -1 fi However, this plays badly now in the default Debian migration software as can be seen on ppc64el. r-bioc-glmgampoi fails to migrate, so in a pure testing environment your test passes, but with unstable added (which we do to test uploads of your dependencies) the test fails. Your test has been blocking e.g. glibc and gcc-10 from migrating to testing for no good reason. Please fix your test. Paul OpenPGP_signature Description: OpenPGP digital signature
Bug#976532: [Pkg-rust-maintainers] Bug#976532: marked as done (rust-cpuid-bool: FTBFS: compile_error!("This crate works only on my computer"); )
On Sat, Dec 05, 2020 at 07:45:29PM +, Debian Bug Tracking System wrote:
> Date: Sat, 5 Dec 2020 14:28:14 +0100
> From: Lucas Nussbaum
> To: sub...@bugs.debian.org
> Subject: rust-cpuid-bool: FTBFS: dh_auto_test: error:
> /usr/share/cargo/bin/cargo test --all returned exit code 101
> Source: rust-cpuid-bool
> Version: 0.1.2-2
> Severity: serious
> Justification: FTBFS on arm64
>
> Hi,
>
> Relevant part (hopefully):
> > 20 | compile_error!("This crate works only on x86 and x86-64 targets.");
> >| ^^^
> >
> > error: aborting due to previous error
> Date: Sat, 5 Dec 2020 20:42:02 +0100
> From: Lucas Nussbaum
> To: 976532-d...@bugs.debian.org
> Subject: Re: Bug#976532: rust-cpuid-bool: FTBFS: dh_auto_test: error:
> /usr/share/cargo/bin/cargo test --all returned exit code 101
> User-Agent: Mutt/1.10.1 (2018-07-13)
>
> Version: 0.1.2-3
>
> Actually, this was fixed in 0.1.2-3 (by disabling tests) before I filed the
> bug.
It allows us to find a better fix
Regards
Geert Stappers
--
Silence is hard to parse
Bug#976568: zvmcloudconnector: FTBFS: make[1]: pyversions: No such file or directory
On 05/12/20 at 14:30 +0100, Lucas Nussbaum wrote: > Source: zvmcloudconnector > Version: 1.4.1-3 > 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). It also fails on amd64. You can find a build log in http://qa-logs.debian.net/2020/12/05/amd64/ Lucas
Bug#976537: specutils: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p "3.8 3.9" returned exit code 13
On 05/12/20 at 14:28 +0100, Lucas Nussbaum wrote: > Source: specutils > Version: 1.1-2 > 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). It also fails on amd64. You can find a build log in http://qa-logs.debian.net/2020/12/05/amd64/ Lucas
Bug#976513: 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
On 05/12/20 at 13:32 +0100, Lucas Nussbaum wrote: > 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). It also fails on amd64. You can find a build log in http://qa-logs.debian.net/2020/12/05/amd64/ Lucas
Bug#976482: strace: FTBFS: ../io_uring.c:30:1: error: static assertion failed: "struct io_cqring_offsets.resv is missing, please update the decoder"
On 05/12/20 at 13:31 +0100, Lucas Nussbaum wrote: > Source: strace > Version: 5.5-3 > 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). It also fails on amd64. You can find a build log in http://qa-logs.debian.net/2020/12/05/amd64/ Lucas
Bug#976472: rust-packed-simd: FTBFS: dh_auto_test: error: /usr/share/cargo/bin/cargo build returned exit code 101
On 05/12/20 at 14:28 +0100, Lucas Nussbaum wrote: > Source: rust-packed-simd > Version: 0.3.3-5 > 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). It also fails on amd64. You can find a build log in http://qa-logs.debian.net/2020/12/05/amd64/ Lucas
Bug#976467: rust-core-arch: FTBFS: dh_auto_test: error: /usr/share/cargo/bin/cargo build returned exit code 101
On 05/12/20 at 14:28 +0100, Lucas Nussbaum wrote: > Source: rust-core-arch > Version: 0.1.5-4 > 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). It also fails on amd64. You can find a build log in http://qa-logs.debian.net/2020/12/05/amd64/ Lucas
Bug#976579: libgsecuredelete: FTBFS: gsecuredelete.vapi:8.3-8.25: error: `Gsd.Intl' already contains a definition for `init'
On 05/12/20 at 13:21 +0100, Lucas Nussbaum wrote: > Source: libgsecuredelete > Version: 0.3-2 > 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). It also fails on amd64. You can find a build log in http://qa-logs.debian.net/2020/12/05/amd64/ Lucas
Bug#976577: librsvg: FTBFS: dh_auto_test: error: make -j4 check VERBOSE=1 "TESTS=api loading crash render-crash dimensions errors infinite-loop" returned exit code 2
On 05/12/20 at 14:06 +0100, Lucas Nussbaum wrote: > Source: librsvg > Version: 2.50.2+dfsg-1 > 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). It also fails on amd64. You can find a build log in http://qa-logs.debian.net/2020/12/05/amd64/ Lucas
Bug#976573: pandas: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p "3.8 3.9" returned exit code 13
On 05/12/20 at 13:47 +0100, Lucas Nussbaum wrote: > Source: pandas > Version: 1.1.4+dfsg-1 > 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). It also fails on amd64. You can find a build log in http://qa-logs.debian.net/2020/12/05/amd64/ Lucas
Bug#976563: bazel-bootstrap: FTBFS: FATAL: couldn't connect to server (22400) after 120 seconds.
On 05/12/20 at 13:54 +0100, Lucas Nussbaum wrote: > Source: bazel-bootstrap > Version: 3.4.0+ds-2 > 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). It also fails on amd64. You can find a build log in http://qa-logs.debian.net/2020/12/05/amd64/ Lucas
Bug#976566: opencolorio: FTBFS: Imath.h:13:10: fatal error: OpenEXR/OpenEXRConfig.h: No such file or directory
On 05/12/20 at 13:25 +0100, Lucas Nussbaum wrote: > Source: opencolorio > Version: 1.1.1~dfsg0-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). It also fails on amd64. You can find a build log in http://qa-logs.debian.net/2020/12/05/amd64/ Lucas
Bug#976555: python-escript: FTBFS: ERROR: build stopped due to errors
On 05/12/20 at 13:49 +0100, Lucas Nussbaum wrote: > Source: python-escript > Version: 5.5-5 > 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). It also fails on amd64. You can find a build log in http://qa-logs.debian.net/2020/12/05/amd64/ Lucas
Bug#976559: python-x2go: FTBFS: NameError: name 'AF_INET' is not defined
On 05/12/20 at 13:49 +0100, Lucas Nussbaum wrote: > Source: python-x2go > Version: 0.6.1.3-2 > 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). It also fails on amd64. You can find a build log in http://qa-logs.debian.net/2020/12/05/amd64/ Lucas
Bug#976541: libgit2-glib: FTBFS: ../libgit2-glib/ggit-clone-options.c:152:5: error: token ""1.0"" is not valid in preprocessor expressions
On 05/12/20 at 13:21 +0100, Lucas Nussbaum wrote: > Source: libgit2-glib > Version: 0.28.0.1-2 > 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). It also fails on amd64. You can find a build log in http://qa-logs.debian.net/2020/12/05/amd64/ Lucas
Bug#976539: elinks: FTBFS: ! Undefined control sequence.
On 05/12/20 at 13:58 +0100, Lucas Nussbaum wrote: > Source: elinks > Version: 0.13.2-1 > 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). It also fails on amd64. You can find a build log in http://qa-logs.debian.net/2020/12/05/amd64/ Lucas
Bug#976533: pulseview: FTBFS: util.cpp:140:6: error: no match for ‘operator<<’ (operand types are ‘QTextStream’ and ‘’)
On 05/12/20 at 13:27 +0100, Lucas Nussbaum wrote: > Source: pulseview > Version: 0.4.2-1 > 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). It also fails on amd64. You can find a build log in http://qa-logs.debian.net/2020/12/05/amd64/ Lucas
Bug#976530: dolphin-emu: FTBFS: tests failed
On 05/12/20 at 14:21 +0100, Lucas Nussbaum wrote: > Source: dolphin-emu > Version: 5.0+dfsg-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). It also fails on amd64. You can find a build log in http://qa-logs.debian.net/2020/12/05/amd64/ Lucas
Bug#976531: python-eventlet: FTBFS: dh_auto_test: error: pybuild --test --test-nose -i python{version} -p "3.8 3.9" returned exit code 13
On 05/12/20 at 13:49 +0100, Lucas Nussbaum wrote: > Source: python-eventlet > Version: 0.26.1-3 > 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). It also fails on amd64. You can find a build log in http://qa-logs.debian.net/2020/12/05/amd64/ Lucas
Bug#976522: golang-gopkg-libgit2-git2go.v28: FTBFS: src/gopkg.in/libgit2/git2go.v28/git_dynamic.go:10:3: error: #error "Invalid libgit2 version; this git2go supports libgit2 v0.28"
On 05/12/20 at 13:19 +0100, Lucas Nussbaum wrote: > Source: golang-gopkg-libgit2-git2go.v28 > Version: 0.28.5-1 > 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). It also fails on amd64. You can find a build log in http://qa-logs.debian.net/2020/12/05/amd64/ Lucas
Bug#976529: ring-clojure: FTBFS: Syntax error (FileNotFoundException) compiling at (potemkin/macros.clj:1:1).
On 05/12/20 at 14:28 +0100, Lucas Nussbaum wrote: > Source: ring-clojure > Version: 1.6.2-2 > 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). It also fails on amd64. You can find a build log in http://qa-logs.debian.net/2020/12/05/amd64/ Lucas
Bug#976518: gsound: FTBFS: Unescaped left brace in regex is passed through in regex; marked by <-- HERE in m/^${ <-- HERE abs_top_builddir}/gsound$/ at /usr/bin/automake line 5755.
On 05/12/20 at 14:24 +0100, Lucas Nussbaum wrote: > Source: gsound > Version: 1.0.2-4 > 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). It also fails on amd64. You can find a build log in http://qa-logs.debian.net/2020/12/05/amd64/ Lucas
Bug#976516: pyside2: FTBFS: ValueError: At least one failure was not blacklisted and met the criterion 'FAIL! >= 3'
On 05/12/20 at 13:47 +0100, Lucas Nussbaum wrote: > Source: pyside2 > Version: 5.15.0-5 > 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). It also fails on amd64. You can find a build log in http://qa-logs.debian.net/2020/12/05/amd64/ Lucas
Bug#976503: lintian-brush: FTBFS: dh_auto_test: error: pybuild --test -i python{version} -p "3.8 3.9" returned exit code 13
On 05/12/20 at 13:45 +0100, Lucas Nussbaum wrote: > Source: lintian-brush > Version: 0.87 > 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). It also fails on amd64. You can find a build log in http://qa-logs.debian.net/2020/12/05/amd64/ Lucas
Bug#976506: conda-package-handling: FTBFS on arm64: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p 3.9 returned exit code 13
On 05/12/20 at 13:44 +0100, Lucas Nussbaum wrote: > Source: conda-package-handling > Version: 1.7.2-1 > 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). It also fails on amd64. You can find a build log in http://qa-logs.debian.net/2020/12/05/amd64/ Lucas
Bug#976493: ruby-psych: FTBFS: NameError: undefined method `default_specifications_dir' for class `#'
On 05/12/20 at 14:12 +0100, Lucas Nussbaum wrote: > Source: ruby-psych > Version: 3.1.0+really3.1.0-1 > 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). It also fails on amd64. You can find a build log in http://qa-logs.debian.net/2020/12/05/amd64/ Lucas
Bug#976477: jruby: FTBFS: cp: cannot stat '/usr/lib/ruby/vendor_ruby/rake*': No such file or directory
On 05/12/20 at 14:03 +0100, Lucas Nussbaum wrote: > Source: jruby > Version: 9.1.17.0-3 > 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). It also fails on amd64. You can find a build log in http://qa-logs.debian.net/2020/12/05/amd64/ Lucas
Bug#976487: grpc-java: FTBFS: CensusStatsModule.java:21: error: cannot find symbol
On 05/12/20 at 13:19 +0100, Lucas Nussbaum wrote: > Source: grpc-java > Version: 1.20.0+ds-3 > 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). It also fails on amd64. You can find a build log in http://qa-logs.debian.net/2020/12/05/amd64/ Lucas
Bug#976585: libcereal: FTBFS: writer.h:430:67: error: comparison is always true due to limited range of data type [-Werror=type-limits]
Control: tags -1 help
Hi,
I wonder why
static_cast(c) < 256
triggers a "error: comparison is always true due to limited range of data type
[-Werror=type-limits]"
only on arm64 but not on amd64.
Any hint how to fix this bug would be welcome.
Kind regards
Andreas.
On Sat, Dec 05, 2020 at 01:21:26PM +0100, Lucas Nussbaum wrote:
> Source: libcereal
> Version: 1.3.0-3
> 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):
> > cd /<>/obj-aarch64-linux-gnu/unittests && /usr/bin/c++
> > -I/<>/./include -Werror -Wall -g -Wextra -Wshadow -pedantic
> > -Wold-style-cast -g -O2 -fdebug-prefix-map=/<>=.
> > -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time
> > -D_FORTIFY_SOURCE=2 -std=gnu++11 -o
> > CMakeFiles/test_structs.dir/structs.cpp.o -c
> > /<>/unittests/structs.cpp
> > In file included from
> > /<>/./include/cereal/external/rapidjson/prettywriter.h:18,
> > from
> > /<>/./include/cereal/archives/json.hpp:64,
> > from /<>/unittests/common.hpp:55,
> > from /<>/unittests/structs.hpp:29,
> > from /<>/unittests/structs.cpp:28:
> > /<>/./include/cereal/external/rapidjson/writer.h: In
> > instantiation of ‘bool rapidjson::Writer > TargetEncoding, StackAllocator, writeFlags>::WriteString(const Ch*,
> > rapidjson::SizeType) [with OutputStream =
> > rapidjson::BasicOStreamWrapper >; SourceEncoding =
> > rapidjson::UTF8<>; TargetEncoding = rapidjson::UTF8<>; StackAllocator =
> > rapidjson::CrtAllocator; unsigned int writeFlags = 2;
> > rapidjson::Writer > StackAllocator, writeFlags>::Ch = char; rapidjson::SizeType = unsigned
> > int]’:
> > /<>/./include/cereal/external/rapidjson/prettywriter.h:114:48:
> > required from ‘bool rapidjson::PrettyWriter > TargetEncoding, StackAllocator, writeFlags>::String(const Ch*,
> > rapidjson::SizeType, bool) [with OutputStream =
> > rapidjson::BasicOStreamWrapper >; SourceEncoding =
> > rapidjson::UTF8<>; TargetEncoding = rapidjson::UTF8<>; StackAllocator =
> > rapidjson::CrtAllocator; unsigned int writeFlags = 2;
> > rapidjson::PrettyWriter > StackAllocator, writeFlags>::Ch = char; rapidjson::SizeType = unsigned int]’
> > /<>/./include/cereal/archives/json.hpp:258:136: required
> > from here
> > /<>/./include/cereal/external/rapidjson/writer.h:430:67:
> > error: comparison is always true due to limited range of data type
> > [-Werror=type-limits]
> > 430 | else if ((sizeof(Ch) == 1 || static_cast(c) <
> > 256) && CEREAL_RAPIDJSON_UNLIKELY(escape[static_cast(c)])) {
> > |
> > ~^
> > In file included from
> > /<>/./include/cereal/external/rapidjson/prettywriter.h:18,
> > from
> > /<>/./include/cereal/archives/json.hpp:64,
> > from /<>/unittests/common.hpp:55,
> > from /<>/unittests/stack.hpp:29,
> > from /<>/unittests/stack.cpp:28:
> > /<>/./include/cereal/external/rapidjson/writer.h: In
> > instantiation of ‘bool rapidjson::Writer > TargetEncoding, StackAllocator, writeFlags>::WriteString(const Ch*,
> > rapidjson::SizeType) [with OutputStream =
> > rapidjson::BasicOStreamWrapper >; SourceEncoding =
> > rapidjson::UTF8<>; TargetEncoding = rapidjson::UTF8<>; StackAllocator =
> > rapidjson::CrtAllocator; unsigned int writeFlags = 2;
> > rapidjson::Writer > StackAllocator, writeFlags>::Ch = char; rapidjson::SizeType = unsigned
> > int]’:
> > /<>/./include/cereal/external/rapidjson/prettywriter.h:114:48:
> > required from ‘bool rapidjson::PrettyWriter > TargetEncoding, StackAllocator, writeFlags>::String(const Ch*,
> > rapidjson::SizeType, bool) [with OutputStream =
> > rapidjson::BasicOStreamWrapper >; SourceEncoding =
> > rapidjson::UTF8<>; TargetEncoding = rapidjson::UTF8<>; StackAllocator =
> > rapidjson::CrtAllocator; unsigned int writeFlags = 2;
> > rapidjson::PrettyWriter > StackAllocator, writeFlags>::Ch = char; rapidjson::SizeType = unsigned int]’
> > /<>/./include/cereal/archives/jso
Processed: Re: Bug#976585: libcereal: FTBFS: writer.h:430:67: error: comparison is always true due to limited range of data type [-Werror=type-limits]
Processing control commands: > tags -1 help Bug #976585 [src:libcereal] libcereal: FTBFS: writer.h:430:67: error: comparison is always true due to limited range of data type [-Werror=type-limits] Added tag(s) help. -- 976585: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=976585 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#976542: Biopython FTBFS probably related to new mkdssp
Hi Lucas, This is reproducible under amd64 machines. I think this issue is related to a recent update of the dssp package; I'm having a look to see if I can pinpoint the issue more precisely. Thanks for reporting this! -- Étienne Mollier Fingerprint: 8f91 b227 c7d6 f2b1 948c 8236 793c f67e 8f0d 11da Sent from /dev/pts/3, please excuse my verbosity. signature.asc Description: PGP signature
Bug#975157: marked as done (meshlab: FTBFS: AtomicCounter.h:28:35: error: ‘ULONG_MAX’ was not declared in this scope)
Your message dated Sat, 05 Dec 2020 19:50:06 +
with message-id
and subject line Bug#975157: fixed in meshlab 2020.09+dfsg1-1
has caused the Debian Bug report #975157,
regarding meshlab: FTBFS: AtomicCounter.h:28:35: error: ‘ULONG_MAX’ was not
declared in this scope
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.)
--
975157: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=975157
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: meshlab
Version: 2020.06+dfsg1-1
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20201119 ftbfs-bullseye
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> /usr/bin/c++ -DMESHLAB_SCALAR=float -DQT_CORE_LIB -DQT_GUI_LIB -DQT_NO_DEBUG
> -DQT_OPENGL_LIB -DQT_SCRIPT_LIB -DQT_WIDGETS_LIB -DQT_XML_LIB
> -I/<>/obj-x86_64-linux-gnu/external-ssynth_autogen/include
> -I/<>/vcglib -I/<>/src -I/usr/include/eigen3
> -isystem /<>/src/external/structuresynth-1.5/ssynth -isystem
> /usr/include/x86_64-linux-gnu/qt5 -isystem
> /usr/include/x86_64-linux-gnu/qt5/QtCore -isystem
> /usr/lib/x86_64-linux-gnu/qt5/mkspecs/linux-g++ -isystem
> /usr/include/x86_64-linux-gnu/qt5/QtXml -isystem
> /usr/include/x86_64-linux-gnu/qt5/QtOpenGL -isystem
> /usr/include/x86_64-linux-gnu/qt5/QtWidgets -isystem
> /usr/include/x86_64-linux-gnu/qt5/QtGui -isystem
> /usr/include/x86_64-linux-gnu/qt5/QtScript -g -O2
> -ffile-prefix-map=/<>=. -fstack-protector-strong -Wdate-time
> -D_FORTIFY_SOURCE=2 -fPIC -fPIC -o
> CMakeFiles/external-ssynth.dir/external/structuresynth-1.5/ssynth/SyntopiaCore/GLEngine/Raytracer/AtomicCounter.cpp.o
> -c
> /<>/src/external/structuresynth-1.5/ssynth/SyntopiaCore/GLEngine/Raytracer/AtomicCounter.cpp
> In file included from
> /<>/src/external/structuresynth-1.5/ssynth/SyntopiaCore/GLEngine/Raytracer/AtomicCounter.cpp:1:
> /<>/src/external/structuresynth-1.5/ssynth/SyntopiaCore/GLEngine/Raytracer/AtomicCounter.h:28:35:
> error: ‘ULONG_MAX’ was not declared in this scope
>28 |bool wait(unsigned long time = ULONG_MAX) { wcm.lock(); bool w =
> wc.wait(,time); wcm.unlock(); return w; }
> | ^
> /<>/src/external/structuresynth-1.5/ssynth/SyntopiaCore/GLEngine/Raytracer/AtomicCounter.h:5:1:
> note: ‘ULONG_MAX’ is defined in header ‘’; did you forget to
> ‘#include ’?
> 4 | #include
> +++ |+#include
> 5 |
> make[3]: *** [CMakeFiles/external-ssynth.dir/build.make:410:
> CMakeFiles/external-ssynth.dir/external/structuresynth-1.5/ssynth/SyntopiaCore/GLEngine/Raytracer/AtomicCounter.cpp.o]
> Error 1
The full build log is available from:
http://qa-logs.debian.net/2020/11/19/meshlab_2020.06+dfsg1-1_unstable.log
A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!
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: meshlab
Source-Version: 2020.09+dfsg1-1
Done: Ryan Pavlik
We believe that the bug you reported is fixed in the latest version of
meshlab, 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.
Ryan Pavlik (supplier of updated meshlab 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, 01 Dec 2020 13:35:09 -0600
Source: meshlab
Architecture: source
Version: 2020.09+dfsg1-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Science Team
Changed-By: Ryan Pavlik
Closes: 975157
Changes:
meshlab (2020.09+dfsg1-1) unstable; urgency=medium
.
* New upstream version 2020.09+dfsg1
- New plugin: global registration.
- Closes: #975157
* d/get-orig-source.sh: Improve
* d/copyright:
- Update exclusion lists.
- Update source location.
- Update copyright entries.
* d/control: Add more Build-Depends
Bug#976532: marked as done (rust-cpuid-bool: FTBFS: compile_error!("This crate works only on my computer");)
Your message dated Sat, 5 Dec 2020 20:42:02 +0100
with message-id <20201205194202.ga24...@xanadu.blop.info>
and subject line Re: Bug#976532: rust-cpuid-bool: FTBFS: dh_auto_test: error:
/usr/share/cargo/bin/cargo test --all returned exit code 101
has caused the Debian Bug report #976532,
regarding rust-cpuid-bool: FTBFS: compile_error!("This crate works only on my
computer");
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.)
--
976532: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=976532
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: rust-cpuid-bool
Version: 0.1.2-2
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):
> make[1]: Entering directory '/<>'
> dh_auto_test -- test --all
> debian cargo wrapper: options, profiles, parallel: ['parallel=4'] [] ['-j4']
> debian cargo wrapper: rust_type, gnu_type: aarch64-unknown-linux-gnu,
> aarch64-linux-gnu
> debian cargo wrapper: running subprocess (['env', 'RUST_BACKTRACE=1',
> '/usr/bin/cargo', '-Zavoid-dev-deps', 'test', '--verbose', '--verbose',
> '-j4', '--target', 'aarch64-unknown-linux-gnu', '--all'],) {}
>Compiling cpuid-bool v0.1.2 (/<>)
> Running `CARGO_PKG_REPOSITORY='https://github.com/RustCrypto/utils'
> CARGO_MANIFEST_DIR=/<> CARGO_PKG_NAME=cpuid-bool
> CARGO_PKG_VERSION_PRE= CARGO_PKG_HOMEPAGE= CARGO_PKG_VERSION_MAJOR=0
> LD_LIBRARY_PATH='/<>/target/debug/deps:/usr/lib'
> CARGO_PKG_VERSION_PATCH=2 CARGO_PKG_VERSION_MINOR=1 CARGO=/usr/bin/cargo
> CARGO_PKG_DESCRIPTION='A lightweight no-std compatible alternative to
> is_x86_feature_detected' CARGO_PKG_VERSION=0.1.2
> CARGO_PKG_AUTHORS='RustCrypto Developers' rustc --crate-name cpuid_bool
> --edition=2018 src/lib.rs --error-format=json --json=diagnostic-rendered-ansi
> --crate-type lib --emit=dep-info,metadata,link -C debuginfo=2 -C
> metadata=638d73400b0fbf8b -C extra-filename=-638d73400b0fbf8b --out-dir
> /<>/target/aarch64-unknown-linux-gnu/debug/deps --target
> aarch64-unknown-linux-gnu -C
> incremental=/<>/target/aarch64-unknown-linux-gnu/debug/incremental
> -L dependency=/<>/target/aarch64-unknown-linux-gnu/debug/deps
> -L dependency=/<>/target/debug/deps -C debuginfo=2 --cap-lints
> warn -C linker=aarch64-linux-gnu-gcc -C link-arg=-Wl,-z,relro
> --remap-path-prefix
> /<>=/usr/share/cargo/registry/cpuid-bool-0.1.2`
> Running `CARGO_PKG_REPOSITORY='https://github.com/RustCrypto/utils'
> CARGO_MANIFEST_DIR=/<> CARGO_PKG_NAME=cpuid-bool
> CARGO_PKG_VERSION_PRE= CARGO_PKG_HOMEPAGE= CARGO_PKG_VERSION_MAJOR=0
> LD_LIBRARY_PATH='/<>/target/debug/deps:/usr/lib'
> CARGO_PKG_VERSION_PATCH=2 CARGO_PKG_VERSION_MINOR=1 CARGO=/usr/bin/cargo
> CARGO_PKG_DESCRIPTION='A lightweight no-std compatible alternative to
> is_x86_feature_detected' CARGO_PKG_VERSION=0.1.2
> CARGO_PKG_AUTHORS='RustCrypto Developers' rustc --crate-name cpuid_bool
> --edition=2018 src/lib.rs --error-format=json --json=diagnostic-rendered-ansi
> --emit=dep-info,link -C debuginfo=2 --test -C metadata=9bdbf0620c157365 -C
> extra-filename=-9bdbf0620c157365 --out-dir
> /<>/target/aarch64-unknown-linux-gnu/debug/deps --target
> aarch64-unknown-linux-gnu -C
> incremental=/<>/target/aarch64-unknown-linux-gnu/debug/incremental
> -L dependency=/<>/target/aarch64-unknown-linux-gnu/debug/deps
> -L dependency=/<>/target/debug/deps -C debuginfo=2 --cap-lints
> warn -C linker=aarch64-linux-gnu-gcc -C link-arg=-Wl,-z,relro
> --remap-path-prefix
> /<>=/usr/share/cargo/registry/cpuid-bool-0.1.2`
> error: This crate works only on x86 and x86-64 targets.
> --> src/lib.rs:20:1
>|
> 20 | compile_error!("This crate works only on x86 and x86-64 targets.");
>| ^^^
>
> error: This crate works only on x86 and x86-64 targets.
> --> src/lib.rs:20:1
>|
> 20 | compile_error!("This crate works only on x86 and x86-64 targets.");
>| ^^^
>
> error: aborting due to previous error
>
> error:
Processed: Re: Bug#976500: helpful-el: FTBFS: tests failed
Processing control commands: > severity -1 important Bug #976500 [src:helpful-el] helpful-el: FTBFS: tests failed Severity set to 'important' from 'serious' > retitle -1 helpful-el: FTBFS randomly on arm64 Bug #976500 [src:helpful-el] helpful-el: FTBFS: tests failed Changed Bug title to 'helpful-el: FTBFS randomly on arm64' from 'helpful-el: FTBFS: tests failed'. -- 976500: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=976500 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#976500: helpful-el: FTBFS: tests failed
Control: severity -1 important Control: retitle -1 helpful-el: FTBFS randomly on arm64 Hi, On 05/12/20 at 14:24 +0100, Lucas Nussbaum wrote: > 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). I tried again, and the build succeeded. The exact same packages versions were installed, so it's not due to an update in another package. Lucas
Bug#976475: Bug#976495: also happens on amd64, should be worked around by 1.8.20-5 but the real fix will come with 1.8.20-6
[ Copying other bugs affected by new latex failures since my last rebuild ] Hi Paolo, On 05/12/20 at 18:55 +0100, Paolo Greppi wrote: > Hi Lucas (is it you, or a bot?), I'm not a bot, but only noticed this message by chance. Remember that bug submitters do not receive emails sent to nnn...@bugs.debian.org > thanks for the new bug report about doxygen 1.8.20-4 FTBFS on arm64: > https://bugs.debian.org/976495 > > I had noticed this issue yesterday and worked around it with 1.8.20-5 but the > real fix will come with 1.8.20-6, thanks to a tip from Norbert Preining: > https://bugs.debian.org/976405#10 > > It would be interesting to know when you last run the archive rebuild on > arm64 or amd64, because it's not clear since when this error happens. I last ran an archive rebuild on 24/11. Successful log for doxygen is at: http://qa-logs.debian.net/2020/12/05/tmp/doxygen_1.8.20-4_unstable.log There was a texlive update in the meantime. Here are the versions of packages that differ. < texlive-base_2020.20200925-1 --- > texlive-base_2020.20201203-2 438,446c434,442 < texlive-extra-utils_2020.20200925-1 < texlive-font-utils_2020.20200925-1 < texlive-fonts-recommended_2020.20200925-1 < texlive-latex-base_2020.20200925-1 < texlive-latex-extra_2020.20200925-1 < texlive-latex-recommended_2020.20200925-1 < texlive-luatex_2020.20200925-1 < texlive-pictures_2020.20200925-1 < texlive-plain-generic_2020.20200925-1 --- > texlive-extra-utils_2020.20201129-1 > texlive-font-utils_2020.20201129-1 > texlive-fonts-recommended_2020.20201203-2 > texlive-latex-base_2020.20201203-2 > texlive-latex-extra_2020.20201129-1 > texlive-latex-recommended_2020.20201203-2 > texlive-luatex_2020.20201203-2 > texlive-pictures_2020.20201203-2 > texlive-plain-generic_2020.20201129-1 Also, I noticed a few new latex-related failures in this archive rebuild. https://bugs.debian.org/976475 https://bugs.debian.org/976501 https://bugs.debian.org/976508 https://bugs.debian.org/976519 https://bugs.debian.org/976535 https://bugs.debian.org/976538 https://bugs.debian.org/976544 https://bugs.debian.org/976547 https://bugs.debian.org/976554 https://bugs.debian.org/976556 https://bugs.debian.org/976574 https://bugs.debian.org/976586 Lucas
Bug#969839: [Pkg-rust-maintainers] Bug#969839: Bug#973298: Bug#969839: rust-failure: Should rust-failure be removed from unstable?
Le 05/12/2020 à 18:58, Mark Hymers a écrit : On Sat, 05, Dec, 2020 at 12:26:27PM +0100, Sylvestre Ledru spoke thus.. So you are right, thanks for spotting my mistake, which is because I indeed only check if dak rm would cause any issues. I agree that we thus likely cannot remove it for now from unstable. It has been removed despite this comment. This causes a bunch of breakage. Could you please bring it back? At the request of the release-team, we re-injected the packages which were still in testing back into unstable. Should be back at the next dinstall. Excellent, many thanks! S
Processed: reassign 976339 to python3-libtorrent, forcibly merging 975953 976339
Processing commands for cont...@bugs.debian.org:
> reassign 976339 python3-libtorrent
Bug #976339 [deluge] Deluge standalone client broken with latest Python3
Bug reassigned from package 'deluge' to 'python3-libtorrent'.
No longer marked as found in versions deluge/2.0.3-3.
Ignoring request to alter fixed versions of bug #976339 to the same values
previously set
> forcemerge 975953 976339
Bug #975953 {Done: Andrey Rahmatullin } [python3-libtorrent]
Can't be imported, undefined symbol: _ZNK10libtorrent5entry4dictEv
Bug #975891 {Done: Andrey Rahmatullin } [python3-libtorrent]
deluge: error from deluge/_libtorrent.py
Bug #975899 {Done: Andrey Rahmatullin } [python3-libtorrent]
deluge: Deluge refuses to start properly
Bug #976339 [python3-libtorrent] Deluge standalone client broken with latest
Python3
Severity set to 'grave' from 'normal'
Marked Bug as done
Added indication that 976339 affects deluged,deluge
Marked as fixed in versions libtorrent-rasterbar/1.2.9-0.2.
Marked as found in versions libtorrent-rasterbar/1.2.9-0.1.
Added tag(s) patch.
Bug #975891 {Done: Andrey Rahmatullin } [python3-libtorrent]
deluge: error from deluge/_libtorrent.py
Bug #975899 {Done: Andrey Rahmatullin } [python3-libtorrent]
deluge: Deluge refuses to start properly
Merged 975891 975899 975953 976339
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
975891: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=975891
975899: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=975899
975953: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=975953
976339: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=976339
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Processed: reassign 975899 to python3-libtorrent, forcibly merging 975953 975899
Processing commands for cont...@bugs.debian.org:
> reassign 975899 python3-libtorrent
Bug #975899 [deluge] deluge: Deluge refuses to start properly
Bug reassigned from package 'deluge' to 'python3-libtorrent'.
No longer marked as found in versions deluge/2.0.3-3.
Ignoring request to alter fixed versions of bug #975899 to the same values
previously set
> forcemerge 975953 975899
Bug #975953 {Done: Andrey Rahmatullin } [python3-libtorrent]
Can't be imported, undefined symbol: _ZNK10libtorrent5entry4dictEv
Bug #975891 {Done: Andrey Rahmatullin } [python3-libtorrent]
deluge: error from deluge/_libtorrent.py
Bug #975899 [python3-libtorrent] deluge: Deluge refuses to start properly
Marked Bug as done
Added indication that 975899 affects deluged,deluge
Marked as fixed in versions libtorrent-rasterbar/1.2.9-0.2.
Marked as found in versions libtorrent-rasterbar/1.2.9-0.1.
Added tag(s) patch.
Bug #975891 {Done: Andrey Rahmatullin } [python3-libtorrent]
deluge: error from deluge/_libtorrent.py
Merged 975891 975899 975953
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
975891: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=975891
975899: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=975899
975953: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=975953
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#976424: marked as done (vtk6: FTBFS in sid)
Your message dated Sat, 05 Dec 2020 19:34:52 + with message-id and subject line Bug#976424: fixed in vtk6 6.3.0+dfsg2-6 has caused the Debian Bug report #976424, regarding vtk6: FTBFS in sid 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.) -- 976424: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=976424 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: vtk6 Version: 6.3.0+dfsg2-5 Severity: serious tags: patch Hello, looks like vtk6 started FTBFS in sid, not sure if this is just a matter of including QtPainterPath or something else is needed This patch seems to fix the issue, however, vtk7 and vtk9 have the very same code and they looks not failing... --- vtk6-6.3.0+dfsg2.orig/Rendering/Qt/vtkQtLabelRenderStrategy.cxx +++ vtk6-6.3.0+dfsg2/Rendering/Qt/vtkQtLabelRenderStrategy.cxx @@ -34,6 +34,7 @@ #include "vtkTextureMapToPlane.h" #include "vtkTimerLog.h" +#include #include #include #include --- vtk6-6.3.0+dfsg2.orig/Rendering/Qt/vtkQtStringToImage.cxx +++ vtk6-6.3.0+dfsg2/Rendering/Qt/vtkQtStringToImage.cxx @@ -25,6 +25,7 @@ #include "vtkObjectFactory.h" // Qt classes +#include #include #include #include This is an example of failure log libvtkCommonMath-6.3.so.6.3.0 ../../lib/libvtkCommonSystem-6.3.so.6.3.0 ../../lib/libvtkCommonCore-6.3.so.6.3.0 -Wl,-rpath-link,/<>/debian/build/lib /<>/Rendering/Qt/vtkQtStringToImage.cxx: In member function ‘virtual vtkVector2i vtkQtStringToImage::GetBounds(vtkTextProperty*, const vtkUnicodeString&, int)’: /<>/Rendering/Qt/vtkQtStringToImage.cxx:109:16: error: aggregate ‘QPainterPath path’ has incomplete type and cannot be defined 109 | QPainterPath path; |^~~~ /<>/Rendering/Qt/vtkQtStringToImage.cxx: In member function ‘virtual vtkVector2i vtkQtStringToImage::GetBounds(vtkTextProperty*, const vtkStdString&, int)’: /<>/Rendering/Qt/vtkQtStringToImage.cxx:140:16: error: aggregate ‘QPainterPath path’ has incomplete type and cannot be defined 140 | QPainterPath path; |^~~~ /<>/Rendering/Qt/vtkQtStringToImage.cxx: In member function ‘virtual int vtkQtStringToImage::RenderString(vtkTextProperty*, const vtkUnicodeString&, int, vtkImageData*, int*)’: /<>/Rendering/Qt/vtkQtStringToImage.cxx:187:16: error: aggregate ‘QPainterPath path’ has incomplete type and cannot be defined 187 | QPainterPath path; |^~~~ make[3]: *** [Rendering/Qt/CMakeFiles/vtkRenderingQt.dir/build.make:124: Rendering/Qt/CMakeFiles/vtkRenderingQt.dir/vtkQtStringToImage.cxx.o] Error 1 make[3]: *** Waiting for unfinished jobs /<>/Rendering/Qt/vtkQtLabelRenderStrategy.cxx: In member function ‘virtual void vtkQtLabelRenderStrategy::ComputeLabelBounds(vtkTextProperty*, vtkUnicodeString, double*)’: /<>/Rendering/Qt/vtkQtLabelRenderStrategy.cxx:271:18: error: aggregate ‘QPainterPath path’ has incomplete type and cannot be defined 271 | QPainterPath path; | ^~~~ /<>/Rendering/Qt/vtkQtLabelRenderStrategy.cxx: In member function ‘virtual void vtkQtLabelRenderStrategy::RenderLabel(int*, vtkTextProperty*, vtkUnicodeString, int)’: /<>/Rendering/Qt/vtkQtLabelRenderStrategy.cxx:373:16: error: aggregate ‘QPainterPath path’ has incomplete type and cannot be defined 373 | QPainterPath path; |^~~~ /<>/Rendering/Qt/vtkQtLabelRenderStrategy.cxx: In member function ‘virtual void vtkQtLabelRenderStrategy::RenderLabel(int*, vtkTextProperty*, vtkUnicodeString)’: /<>/Rendering/Qt/vtkQtLabelRenderStrategy.cxx:484:18: error: aggregate ‘QPainterPath path’ has incomplete type and cannot be defined 484 | QPainterPath path; | ^~~~ make[3]: *** [Rendering/Qt/CMakeFiles/vtkRenderingQt.dir/build.make:111: Rendering/Qt/CMakeFiles/vtkRenderingQt.dir/vtkQtLabelRenderStrategy.cxx.o] Error 1 cd /<>/debian/build/Interaction/Widgets && /usr/bin/cmake -E cmake_symlink_library ../../lib/libvtkInteractionWidgets-6.3.so.6.3.0 ../../lib/libvtkInteractionWidgets-6.3.so.6.3 ../../lib/libvtkInteractionWidgets-6.3.so make[3]: Leaving directory '/<>/debian/build' [ 96%] Built target vtkInteractionWidgets make -f Views/Core/CMakeFiles/vtkViewsCore.dir/build.make Views/Core/CMakeFiles/vtkViewsCore.dir/depend Can you please have a look? G. --- End Message --- --- Begin Message --- Source: vtk6 Source-Version: 6.3.0+dfsg2-6 Done: Anton Gladky We believe that the bug you reported is fixed in the latest version of vtk6, which is due to be installed in the Debian FTP archive. A summary of the changes between
Bug#975135: marked as done (vtk6: FTBFS: vtkQtLabelRenderStrategy.cxx:271:18: error: aggregate ‘QPainterPath path’ has incomplete type and cannot be defined)
Your message dated Sat, 05 Dec 2020 19:34:52 + with message-id and subject line Bug#975135: fixed in vtk6 6.3.0+dfsg2-6 has caused the Debian Bug report #975135, regarding vtk6: FTBFS: vtkQtLabelRenderStrategy.cxx:271:18: error: aggregate ‘QPainterPath path’ has incomplete type and cannot be defined 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.) -- 975135: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=975135 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: vtk6 Version: 6.3.0+dfsg2-5 Severity: serious Justification: FTBFS on amd64 Tags: bullseye sid ftbfs Usertags: ftbfs-20201119 ftbfs-bullseye Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[3]: Entering directory '/<>/debian/build' > [ 85%] Building CXX object > GUISupport/QtOpenGL/CMakeFiles/vtkGUISupportQtOpenGL.dir/QVTKGraphicsItem.cxx.o > cd /<>/debian/build/GUISupport/QtOpenGL && /usr/bin/mpic++ > -DQT_CORE_LIB -DQT_GUI_LIB -DQT_NO_DEBUG -DQT_OPENGL_LIB -DQT_WIDGETS_LIB > -DVTK_IN_VTK -DvtkGUISupportQtOpenGL_EXPORTS > -I/<>/debian/build/GUISupport/Qt > -I/<>/GUISupport/Qt > -I/<>/debian/build/Common/ExecutionModel > -I/<>/Common/ExecutionModel > -I/<>/debian/build/Common/DataModel > -I/<>/Common/DataModel > -I/<>/debian/build/Common/Math -I/<>/Common/Math > -I/<>/debian/build/Common/Core -I/<>/Common/Core > -I/<>/debian/build/Utilities/KWSys > -I/<>/Utilities/KWSys > -I/<>/debian/build/Common/Misc -I/<>/Common/Misc > -I/<>/debian/build/Common/System > -I/<>/Common/System > -I/<>/debian/build/Common/Transforms > -I/<>/Common/Transforms > -I/<>/debian/build/Filters/Extraction > -I/<>/Filters/Extraction > -I/<>/debian/build/Filters/Core -I/<>/Filters/Core > -I/<>/debian/build/Filters/General > -I/<>/Filters/General > -I/<>/debian/build/Common/ComputationalGeometry > -I/<>/Common/ComputationalGeometry > -I/<>/debian/build/Filters/Statistics > -I/<>/Filters/Statistics > -I/<>/debian/build/Imaging/Fourier > -I/<>/Imaging/Fourier > -I/<>/debian/build/Imaging/Core -I/<>/Imaging/Core > -I/<>/debian/build/ThirdParty/alglib > -I/<>/ThirdParty/alglib > -I/<>/debian/build/Interaction/Style > -I/<>/Interaction/Style > -I/<>/debian/build/Filters/Sources > -I/<>/Filters/Sources > -I/<>/debian/build/Rendering/Core > -I/<>/Rendering/Core > -I/<>/debian/build/Common/Color -I/<>/Common/Color > -I/<>/debian/build/Filters/Geometry > -I/<>/Filters/Geometry > -I/<>/debian/build/Rendering/OpenGL > -I/<>/Rendering/OpenGL > -I/<>/debian/build/Imaging/Hybrid > -I/<>/Imaging/Hybrid -I/<>/debian/build/IO/Image > -I/<>/IO/Image > -I/<>/debian/build/Utilities/DICOMParser > -I/<>/Utilities/DICOMParser > -I/<>/debian/build/IO/Core -I/<>/IO/Core > -I/<>/debian/build/ThirdParty/zlib > -I/<>/ThirdParty/zlib > -I/<>/debian/build/Utilities/MetaIO/vtkmetaio > -I/<>/debian/build/Utilities/MetaIO > -I/<>/Utilities/MetaIO > -I/<>/debian/build/ThirdParty/jpeg > -I/<>/ThirdParty/jpeg > -I/<>/debian/build/ThirdParty/png > -I/<>/ThirdParty/png > -I/<>/debian/build/ThirdParty/tiff > -I/<>/ThirdParty/tiff > -I/<>/debian/build/Utilities/ParseOGLExt > -I/<>/Utilities/ParseOGLExt > -I/<>/debian/build/Utilities/EncodeString > -I/<>/Utilities/EncodeString > -I/<>/debian/build/GUISupport/QtOpenGL > -I/<>/GUISupport/QtOpenGL -isystem > /usr/include/x86_64-linux-gnu/qt5 -isystem > /usr/include/x86_64-linux-gnu/qt5/QtOpenGL -isystem > /usr/include/x86_64-linux-gnu/qt5/QtWidgets -isystem > /usr/include/x86_64-linux-gnu/qt5/QtGui -isystem > /usr/include/x86_64-linux-gnu/qt5/QtCore -isystem > /usr/lib/x86_64-linux-gnu/qt5/mkspecs/linux-g++ -g -O2 > -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat > -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -DVTK_USE_BOOST > -fPIC -fvisibility=hidden -fvisibility-inlines-hidden -fPIC -o > CMakeFiles/vtkGUISupportQtOpenGL.dir/QVTKGraphicsItem.cxx.o -c > /<>/GUISupport/QtOpenGL/QVTKGraphicsItem.cxx > [ 85%] Building CXX object > Rendering/Qt/CMakeFiles/vtkRenderingQt.dir/vtkQtInitialization.cxx.o > cd /<>/debian/build/Rendering/Qt && /usr/bin/mpic++ > -DQT_CORE_LIB -DQT_GUI_LIB -DQT_NO_DEBUG -DQT_WIDGETS_LIB -DVTK_IN_VTK > -DvtkRenderingQt_EXPORTS -I/<>/debian/build/Filters/Sources > -I/<>/Filters/Sources > -I/<>/debian/build/Common/ComputationalGeometry > -I/<>/Common/ComputationalGeometry > -I/<>/debian/build/Common/DataModel > -I/<>/Common/DataModel > -I/<>/debian/build/Common/Math -I/<>/Common/Math > -I/<>/debian/build/Common/Core -I/<>/Common/Core >
Bug#971563: marked as pending in libgit2-glib
Control: tag -1 pending Hello, Bug #971563 in libgit2-glib 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/gnome-team/libgit2-glib/-/commit/f262e2e08892929fc95fcfbfaff8084f92ba5cdf New upstream release, compatible with libgit2 1.0 Closes: #971563 (this message was generated automatically) -- Greetings https://bugs.debian.org/971563
Processed: Bug#971563 marked as pending in libgit2-glib
Processing control commands: > tag -1 pending Bug #971563 [src:libgit2-glib] libgit2-glib: libgit2 1.0 transition Added tag(s) pending. -- 971563: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=971563 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#976233: marked as done (ghdl FTBFS with LLVM 11 as default)
Your message dated Sat, 05 Dec 2020 19:18:40 + with message-id and subject line Bug#976233: fixed in ghdl 0.37+dfsg-3 has caused the Debian Bug report #976233, regarding ghdl FTBFS with LLVM 11 as default 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.) -- 976233: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=976233 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: ghdl Version: 0.37+dfsg-2 Severity: important Tags: ftbfs patch Forwarded: https://github.com/ghdl/ghdl/pull/1451 Control: block 973480 by -1 LLVM 11 will soon be default, and this causes a FTBFS in ghdl. Manually applying the one-line upstream change linked above fixes the build. --- End Message --- --- Begin Message --- Source: ghdl Source-Version: 0.37+dfsg-3 Done: Jonathan McDowell We believe that the bug you reported is fixed in the latest version of ghdl, 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. Jonathan McDowell (supplier of updated ghdl 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, 05 Dec 2020 13:36:28 + Source: ghdl Architecture: source Version: 0.37+dfsg-3 Distribution: unstable Urgency: medium Maintainer: Debian Electronics Team Changed-By: Jonathan McDowell Closes: 970660 976233 Changes: ghdl (0.37+dfsg-3) unstable; urgency=medium . * Team upload. * Update watchfile to ignore date tags * Switch to GCC/GNAT 10. Thanks to Ludovic Brenta (Closes: #970660) * Allow builds with LLVM 11 (Closes: #976233) Checksums-Sha1: 9e205deec3760fe31d6b521b6bd368fe6a35b1b1 2473 ghdl_0.37+dfsg-3.dsc ef85067089711663f0ddfa6fd8c65c52218a582b 18636 ghdl_0.37+dfsg-3.debian.tar.xz 5a38d385e1c2a9dfa77c54b064218edf6d443266 9344 ghdl_0.37+dfsg-3_amd64.buildinfo Checksums-Sha256: 625aae4b7a756127ce3283e12c9b559057a3b50773e677fc5bc327d0f93c6c58 2473 ghdl_0.37+dfsg-3.dsc 9f1a0fecf4f2b3c75b736428b6ce266048b5cf10aaa18fa1f6485af139f370ad 18636 ghdl_0.37+dfsg-3.debian.tar.xz dccff7189a46d41567e70f526a4bacd139bcde1832599b903d824fce4cc0cc9e 9344 ghdl_0.37+dfsg-3_amd64.buildinfo Files: 5d1da6cdb9aa4b2fc5729cf883a95f1b 2473 electronics optional ghdl_0.37+dfsg-3.dsc 73120361d9e3efbea1aa293ada3d542a 18636 electronics optional ghdl_0.37+dfsg-3.debian.tar.xz 7a6a67c5e21996e81f71df2db07edf7f 9344 electronics optional ghdl_0.37+dfsg-3_amd64.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEE/S8txYRw4wP3eXWjSgDzSK903QIFAl/L21cACgkQSgDzSK90 3QIRtA//fdZ64w9qQ01IHC5ZmC7/TpPVavRqOjJgkPHOcPiA0Go9jI1f/O3OjEUy EremRTHyC8Pj8Z2AEGu1odKagJ5uLUMU57axBMCiyq3AUGuI8+AwHhDnCVlGOVpA F8xN1vk3KKrQzzFf27DB9bZZ+vugMTv0VYo5ZAGy0TkrTYTz99c0VceQafPzKCRb DzjH1A5MDgmy4sG5fd3wd2EAaUvm3kdjnv+0WLup4iJr8x00U4C+Zxn9zRK6Rb4Y MNvzSYqzb2rqabQbF6ISiTL7b8SwCurONXX9AuE7UqlKmtnMacJsyL8gD9ae17L4 tT0eeLlF/XvOBSSINGRVQqh5a66H7hfw770ItxEcQ+ijYcrukbm5tyaTkXaDUKwT dO/EzoBb6wQtkvMi+vJZrdWk/Pk6QZxeuaY1IgqUcVJ6PRRWj0AgPRbbX56P2d3/ 9cAlCp42U0/oN5F/BjfOaQcZbZNo4kWks67VxQEs9ZoBfhecpUmnB0SJBJ0EtY1j gLyKqk5iAl7W2GcohMaA5Un8/6WSV3PDQO9nEXSjBOUTl6EykUhs+kFIZArK5liY bS1fHjVTBmyJarnfLGsqfhGsh4w9bu+i1CsGBEJo7d0lGt6cSTGnrZgHmWLUnnji XHVxnt4eKeJO6+H5XrafKbWcF04gwIo7PaFeZKSdcIGuY6kNPMw= =+fCU -END PGP SIGNATURE End Message ---
Bug#976410: glibc breaks libpod autopkgtest: dh_auto_build: error: cd _output && go install -trimpath ...
On Fri, Dec 4, 2020 at 3:24 PM Aurelien Jarno wrote: > > I have tried and for me the issue is reproducible with both old and new > glibc. I am therefore reassign the bug to libpod. > This is because of an upstream update in a dependency. It should be very straight-forward to fix. Unfortunately, libpod is currently in binary NEW. I'll upload a fix as soon as it clears. -- regards, Reinhard
Bug#969839: Bug#973298: [Pkg-rust-maintainers] Bug#969839: rust-failure: Should rust-failure be removed from unstable?
On Sat, 05, Dec, 2020 at 12:26:27PM +0100, Sylvestre Ledru spoke thus.. > > So you are right, thanks for spotting my mistake, which is because I > > indeed only check if dak rm would cause any issues. I agree that we > > thus likely cannot remove it for now from unstable. > > It has been removed despite this comment. This causes a bunch of breakage. > Could you please bring it back? At the request of the release-team, we re-injected the packages which were still in testing back into unstable. Should be back at the next dinstall. Mark -- Mark Hymers
Bug#976495: also happens on amd64, should be worked around by 1.8.20-5 but the real fix will come with 1.8.20-6
Hi Lucas (is it you, or a bot?), thanks for the new bug report about doxygen 1.8.20-4 FTBFS on arm64: https://bugs.debian.org/976495 I had noticed this issue yesterday and worked around it with 1.8.20-5 but the real fix will come with 1.8.20-6, thanks to a tip from Norbert Preining: https://bugs.debian.org/976405#10 It would be interesting to know when you last run the archive rebuild on arm64 or amd64, because it's not clear since when this error happens. Paolo
Bug#976589: marked as done (node-source-map-support: FTBFS: chmod: cannot access 'debian/node-source-map-support/usr/share/nodejs/source-map-support/build.js': No such file or directory)
Your message dated Sat, 05 Dec 2020 17:40:36 + with message-id and subject line Bug#976589: fixed in node-source-map-support 0.5.19+ds-4 has caused the Debian Bug report #976589, regarding node-source-map-support: FTBFS: chmod: cannot access 'debian/node-source-map-support/usr/share/nodejs/source-map-support/build.js': No such file or directory to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 976589: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=976589 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: node-source-map-support Version: 0.5.19+ds-3 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): > make[1]: Entering directory '/<>' > dh_fixperms > chmod +x > debian/node-source-map-support/usr/share/nodejs/source-map-support/build.js > chmod: cannot access > 'debian/node-source-map-support/usr/share/nodejs/source-map-support/build.js': > No such file or directory > make[1]: *** [debian/rules:8: override_dh_fixperms] Error 1 The full build log is available from: http://qa-logs.debian.net/2020/12/05/node-source-map-support_0.5.19+ds-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: node-source-map-support Source-Version: 0.5.19+ds-4 Done: Xavier Guimard We believe that the bug you reported is fixed in the latest version of node-source-map-support, 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. Xavier Guimard (supplier of updated node-source-map-support 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, 05 Dec 2020 17:49:32 +0100 Source: node-source-map-support Architecture: source Version: 0.5.19+ds-4 Distribution: unstable Urgency: medium Maintainer: Debian Javascript Maintainers Changed-By: Xavier Guimard Closes: 976589 Changes: node-source-map-support (0.5.19+ds-4) unstable; urgency=medium . * Team upload * Declare compliance with policy 4.5.1 * Use dh-sequence-nodejs * Remove bad fixperms hook (Closes: #976589) Checksums-Sha1: efadb4f629d398fae36024db5a297e6a43a661ff 2252 node-source-map-support_0.5.19+ds-4.dsc 650810f8e7c874a7fd38396c0072e211cdd1d900 4520 node-source-map-support_0.5.19+ds-4.debian.tar.xz Checksums-Sha256: 828f797f52ed79fac23d57657cd9a8e0bd64d18d5d15de211cf530e7a56ff65f 2252 node-source-map-support_0.5.19+ds-4.dsc 47f2b41e17afe98f6908f3727b87967425b0680f5cfaa5260ccfdf950c6de106 4520 node-source-map-support_0.5.19+ds-4.debian.tar.xz Files: 6456da98c3faa26624170c5afe910f55 2252 javascript optional node-source-map-support_0.5.19+ds-4.dsc 5306998ef048ee88d33179e87824e42c 4520 javascript optional node-source-map-support_0.5.19+ds-4.debian.tar.xz -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEAN/li4tVV3nRAF7J9tdMp8mZ7ukFAl/LulsACgkQ9tdMp8mZ 7ul3DA/+JHJ9msZ4K26SjKb8R6NRuleABQmys+QG8lm2CQ5v8KHWHGSDD4y5isOo QrAgbBW7SI85ixJ0uOSGk18dmLdYbXkK8AjeJE9cOP7EE0o2exhotIXNdA4IFilS wHJ5hUAJYbeAqaFopTmABozKMLgnoMYDrb6WV/CPfaCh8jnuiw0fIVLY4OCLschH FIAt0QtLJMy4fQWxtKXjHRCLQPts86AY52oP8VCrT6PhV3YF/utaCozkubHozTqv a4jH+M6KhvNOyCBYo+Ec9x1IVWUZehqGDeeOMMV9ZgH2QhOdlgnJYjudY7PC4eai j2cMDtAEsKO6tGicGNx2tcfx3xd5eVy6/el6Tj4rNe98kOwQEuXYv3LPCuBlpOoP dHSftZglV06vrLHfyTGAQ6MCrKTVBWW9UP
Bug#976599: marked as done (tortoisehg FTBFS: AttributeError: 'array.array' object has no attribute 'tostring')
Your message dated Sat, 05 Dec 2020 17:40:55 +
with message-id
and subject line Bug#976599: fixed in tortoisehg 5.5.2-3
has caused the Debian Bug report #976599,
regarding tortoisehg FTBFS: AttributeError: 'array.array' object has no
attribute 'tostring'
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.)
--
976599: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=976599
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: tortoisehg
Version: 5.5.2-2
Severity: serious
Tags: ftbfs
https://buildd.debian.org/status/fetch.php?pkg=tortoisehg=all=5.5.2-2=1606920482=0
...
dh_auto_build
I: pybuild base:232: /usr/bin/python3 setup.py build
running build
running build_config
creating /<>/.pybuild/cpython3_3.9/build/tortoisehg
creating /<>/.pybuild/cpython3_3.9/build/tortoisehg/util
generating
/<>/.pybuild/cpython3_3.9/build/tortoisehg/util/config.py from
/<>/setup.py
running build_ui
generating /<>/tortoisehg/hgqt/hgemail_ui.py from
/<>/tortoisehg/hgqt/hgemail.ui, /<>/setup.py
generating /<>/tortoisehg/hgqt/phabreview_ui.py from
/<>/tortoisehg/hgqt/phabreview.ui, /<>/setup.py
generating /<>/tortoisehg/hgqt/postreview_ui.py from
/<>/tortoisehg/hgqt/postreview.ui, /<>/setup.py
generating /<>/tortoisehg/hgqt/webconf_ui.py from
/<>/tortoisehg/hgqt/webconf.ui, /<>/setup.py
generating /<>/tortoisehg/hgqt/serve_ui.py from
/<>/tortoisehg/hgqt/serve.ui, /<>/setup.py
running build_mo
creating locale
creating locale/et
creating locale/et/LC_MESSAGES
generating locale/et/LC_MESSAGES/tortoisehg.mo from i18n/tortoisehg/et.po
Traceback (most recent call last):
File "/<>/setup.py", line 780, in
setup(name=productname,
File "/usr/lib/python3.9/distutils/core.py", line 148, in setup
dist.run_commands()
File "/usr/lib/python3.9/distutils/dist.py", line 966, in run_commands
self.run_command(cmd)
File "/usr/lib/python3.9/distutils/dist.py", line 985, in run_command
cmd_obj.run()
File "/usr/lib/python3.9/distutils/command/build.py", line 135, in run
self.run_command(cmd_name)
File "/usr/lib/python3.9/distutils/cmd.py", line 313, in run_command
self.distribution.run_command(command)
File "/usr/lib/python3.9/distutils/dist.py", line 985, in run_command
cmd_obj.run()
File "/<>/setup.py", line 66, in run
self.make_file(pofile, mofile, _msgfmt, (pofile, mofile))
File "/usr/lib/python3.9/distutils/cmd.py", line 400, in make_file
self.execute(func, args, exec_msg, level)
File "/usr/lib/python3.9/distutils/cmd.py", line 335, in execute
util.execute(func, args, msg, dry_run=self.dry_run)
File "/usr/lib/python3.9/distutils/util.py", line 304, in execute
func(*args)
File "/<>/setup.py", line 49, in _msgfmt
modata = Msgfmt(pofile).get()
File "/<>/i18n/msgfmt.py", line 132, in get
return self.generate()
File "/<>/i18n/msgfmt.py", line 123, in generate
output += array.array("i", offsets).tostring()
AttributeError: 'array.array' object has no attribute 'tostring'
E: pybuild pybuild:353: build: plugin distutils failed with: exit code=1:
/usr/bin/python3 setup.py build
dh_auto_build: error: pybuild --build -i python{version} -p 3.9 returned exit
code 13
make[1]: *** [debian/rules:7: override_dh_auto_build] Error 25
--- End Message ---
--- Begin Message ---
Source: tortoisehg
Source-Version: 5.5.2-3
Done: Andrej Shadura
We believe that the bug you reported is fixed in the latest version of
tortoisehg, which is due to be installed in the Debian FTP archive.
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to 976...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Andrej Shadura (supplier of updated tortoisehg package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Sat, 05 Dec 2020 18:18:58 +0100
Source: tortoisehg
Architecture: source
Version: 5.5.2-3
Distribution: unstable
Urgency: medium
Maintainer: Andrej Shadura
Changed-By: Andrej Shadura
Closes: 976599
Changes:
tortoisehg (5.5.2-3) unstable; urgency=medium
.
* Replace the deprecated tostring() with tobytes() (Closes: #976599).
Checksums-Sha1:
6d4f33b5bf9542e0cacd2223882a86bcf69e7821 1930 tortoisehg_5.5.2-3.dsc
Bug#976504: marked as done (node-yargs: FTBFS: dh_auto_test: error: /bin/sh -ex debian/tests/pkg-js/test returned exit code 1)
Your message dated Sat, 05 Dec 2020 17:40:41 + with message-id and subject line Bug#976504: fixed in node-yargs 15.3.1+repack-2 has caused the Debian Bug report #976504, regarding node-yargs: FTBFS: dh_auto_test: error: /bin/sh -ex debian/tests/pkg-js/test returned exit code 1 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 976504: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=976504 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: node-yargs Version: 15.3.1+repack-1 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): > dpkg-buildpackage > - > > Command: dpkg-buildpackage -us -uc -sa -rfakeroot > dpkg-buildpackage: info: source package node-yargs > dpkg-buildpackage: info: source version 15.3.1+repack-1 > dpkg-buildpackage: info: source distribution unstable > dpkg-buildpackage: info: source changed by Xavier Guimard > dpkg-source --before-build . > dpkg-buildpackage: info: host architecture arm64 > debian/rules clean > dh clean >dh_auto_clean --buildsystem=nodejs > rm -rf ./node_modules/.cache > rm -rf types-yargs/node_modules/.cache >dh_clean > dpkg-source -b . > dpkg-source: info: using source format '3.0 (quilt)' > dpkg-source: info: building node-yargs using existing > ./node-yargs_15.3.1+repack.orig-types-yargs.tar.gz > dpkg-source: info: building node-yargs using existing > ./node-yargs_15.3.1+repack.orig.tar.gz > dpkg-source: info: using patch list from debian/patches/series > dpkg-source: info: building node-yargs in > node-yargs_15.3.1+repack-1.debian.tar.xz > dpkg-source: info: building node-yargs in node-yargs_15.3.1+repack-1.dsc > debian/rules binary > dh binary >dh_update_autotools_config >dh_autoreconf >dh_auto_configure --buildsystem=nodejs > mkdir node_modules > mkdir -p node_modules/\@types > ln -s ../../types-yargs node_modules/\@types/yargs >dh_auto_build --buildsystem=nodejs > No build command found, searching known files > No build command found, searching known files >dh_auto_test --buildsystem=nodejs > ln -s ../. node_modules/yargs > /bin/sh -ex debian/tests/pkg-js/test > + mocha --require ./test/before.js --timeout=3 --check-leaks > /usr/share/nodejs/yargs/yargs.js:1242 > else throw err >^ > > Error: Cannot find module 'cross-spawn' > Require stack: > - /<>/test/integration.js > - /usr/share/nodejs/mocha/lib/mocha.js > - /usr/share/nodejs/mocha/lib/cli/one-and-dones.js > - /usr/share/nodejs/mocha/lib/cli/options.js > - /usr/share/nodejs/mocha/bin/mocha > at Function.Module._resolveFilename > (internal/modules/cjs/loader.js:831:15) > at Function.Module._load (internal/modules/cjs/loader.js:687:27) > at Module.require (internal/modules/cjs/loader.js:903:19) > at require (internal/modules/cjs/helpers.js:74:18) > at Object. (/<>/test/integration.js:4:15) > at Module._compile (internal/modules/cjs/loader.js:1015:30) > at Object.Module._extensions..js (internal/modules/cjs/loader.js:1035:10) > at Module.load (internal/modules/cjs/loader.js:879:32) > at Function.Module._load (internal/modules/cjs/loader.js:724:14) > at Module.require (internal/modules/cjs/loader.js:903:19) > at require (internal/modules/cjs/helpers.js:74:18) > at /usr/share/nodejs/mocha/lib/mocha.js:311:36 > at Array.forEach () > at Mocha.loadFiles (/usr/share/nodejs/mocha/lib/mocha.js:308:14) > at Mocha.run (/usr/share/nodejs/mocha/lib/mocha.js:849:10) > at Object.exports.singleRun > (/usr/share/nodejs/mocha/lib/cli/run-helpers.js:108:16) > at exports.runMocha > (/usr/share/nodejs/mocha/lib/cli/run-helpers.js:143:13) > at Object.exports.handler (/usr/share/nodejs/mocha/lib/cli/run.js:305:3) > at Object.runCommand (/usr/share/nodejs/yargs/lib/command.js:240:40) > at Object.parseArgs [as _parseArgs] > (/usr/share/nodejs/yargs/yargs.js:1182:35) > at Object.parse (/usr/share/nodejs/yargs/yargs.js:627:25) > at Object.exports.main (/usr/share/nodejs/mocha/lib/cli/cli.js:68:6) > at Object. (/usr/share/nodejs/mocha/bin/mo
Processed: re: bio-eagle: FTBFS: MemoryUtils.hpp:34:10: fatal error: xmmintrin.h: No such file or directory
Processing commands for cont...@bugs.debian.org: > severity 976572 normal Bug #976572 [src:bio-eagle] bio-eagle: FTBFS: MemoryUtils.hpp:34:10: fatal error: xmmintrin.h: No such file or directory Severity set to 'normal' from 'serious' > thanks Stopping processing here. Please contact me if you need assistance. -- 976572: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=976572 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#976572: bio-eagle: FTBFS: MemoryUtils.hpp:34:10: fatal error: xmmintrin.h: No such file or directory
severity 976572 normal thanks 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). It's cool that you have expanded your rebuild tests to include arm64, but it seems your test workflow needs some work. arm64 is not on the architecture list for bio-eagle, even if it was, the normal practice in Debian is only to consider a FTBFS bug rc if the package has built on the architecture in the past. I have downgraded the bug, I will leave the decision on whether to close it or not up to the maintainer.
