Processed: Re: dwz: fails while building assaultcube
Processing control commands: > forwarded -1 https://sourceware.org/bugzilla/show_bug.cgi?id=27375 Bug #1016936 [dwz] dwz: Unknown debugging section .debug_addr causes some builds to fail Set Bug forwarded-to-address to 'https://sourceware.org/bugzilla/show_bug.cgi?id=27375'. -- 1016936: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1016936 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1016936: dwz: fails while building assaultcube
Control: forwarded -1 https://sourceware.org/bugzilla/show_bug.cgi?id=27375 OK, so it turns out this error is due to Clang's adoption of DWARFv5 [1] which dwz doesn't fully support yet [2]. Until that is fixed, the issue can be worked around by using DWARFv4 by adding `-gdwarf-4` to flags. -- Ben Westover [1] https://www.phoronix.com/news/LLVM-Clang-DWARFv5-Default [2] https://sourceware.org/bugzilla/show_bug.cgi?id=24726 OpenPGP_signature Description: OpenPGP digital signature
Bug#984256: marked as done (nextepc: ftbfs with GCC-11)
Your message dated Fri, 09 Sep 2022 00:24:49 + with message-id and subject line Bug#984256: fixed in nextepc 0.3.10+nods-4.2 has caused the Debian Bug report #984256, regarding nextepc: ftbfs with GCC-11 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 984256: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=984256 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:nextepc Version: 0.3.10+nods-4.1 Severity: normal Tags: sid bookworm User: debian-...@lists.debian.org Usertags: ftbfs-gcc-11 [This bug is not targeted to the upcoming bullseye release] Please keep this issue open in the bug tracker for the package it was filed for. If a fix in another package is required, please file a bug for the other package (or clone), and add a block in this package. Please keep the issue open until the package can be built in a follow-up test rebuild. The package fails to build in a test rebuild on at least amd64 with gcc-11/g++-11, but succeeds to build with gcc-10/g++-10. The severity of this report will be raised before the bookworm release, so nothing has to be done for the bullseye release. The full build log can be found at: http://people.debian.org/~doko/logs/20210228/filtered/gcc11/nextepc_0.3.10+nods-4.1_unstable_gcc11.log The last lines of the build log are at the end of this report. To build with GCC 11, either set CC=gcc-11 CXX=g++-11 explicitly, or install the gcc, g++, gfortran, ... packages from experimental. apt-get -t=experimental install g++ Common build failures are new warnings resulting in build failures with -Werror turned on, or new/dropped symbols in Debian symbols files. For other C/C++ related build failures see the porting guide at http://gcc.gnu.org/gcc-11/porting_to.html GCC 11 defaults to the GNU++17 standard. If your package installs header files in /usr/include, please don't work around C++17 issues by choosing a lower C++ standard for the package build, but fix these issues to build with the C++17 standard. [...] libtool: compile: gcc -DHAVE_CONFIG_H -I. -I../../.. -I../../../lib/core/include/arch/unix -I../../../lib/core/include -Wdate-time -D_FORTIFY_SOURCE=2 -Wall -Werror -DLINUX=1 -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -Wno-unused-result -c unix/sockaddr.c -fPIC -DPIC -o unix/.libs/sockaddr.o libtool: compile: gcc -DHAVE_CONFIG_H -I. -I../../.. -I../../../lib/core/include/arch/unix -I../../../lib/core/include -Wdate-time -D_FORTIFY_SOURCE=2 -Wall -Werror -DLINUX=1 -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -Wno-unused-result -c unix/udp.c -fPIC -DPIC -o unix/.libs/udp.o libtool: compile: gcc -DHAVE_CONFIG_H -I. -I../../.. -I../../../lib/core/include/arch/unix -I../../../lib/core/include -Wdate-time -D_FORTIFY_SOURCE=2 -Wall -Werror -DLINUX=1 -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -Wno-unused-result -c unix/tcp.c -fPIC -DPIC -o unix/.libs/tcp.o /bin/bash ../../../libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I. -I../../.. -I../../../lib/core/include/arch/unix -I../../../lib/core/include -Wdate-time -D_FORTIFY_SOURCE=2 -Wall -Werror -DLINUX=1 -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -Wno-unused-result -c -o unix/tun.lo unix/tun.c /bin/bash ../../../libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I. -I../../.. -I../../../lib/core/include/arch/unix -I../../../lib/core/include -Wdate-time -D_FORTIFY_SOURCE=2 -Wall -Werror -DLINUX=1 -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -Wno-unused-result -c -o unix/sctp.lo unix/sctp.c libtool: compile: gcc -DHAVE_CONFIG_H -I. -I../../.. -I../../../lib/core/include/arch/unix -I../../../lib/core/include -Wdate-time -D_FORTIFY_SOURCE=2 -Wall -Werror -DLINUX=1 -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -Wno-unused-result -c unix/tun.c -fPIC -DPIC -o unix/.libs/tun.o libtool: compile: gcc -DHAVE_CONFIG_H -I. -I../../.. -I../../../lib/core/include/arch/unix -I../../../lib/core/include -Wdate-time -D_FORTIFY_SOURCE=2 -Wall -Werror -DLINUX=1 -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -Wno-unused-result -c unix/sctp.c -fPIC -DPIC -o unix/.libs/sctp.o /bin/bash ../../../libtool --tag=CC --mode=link gcc -Wall -Werror -DLINUX=1 -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -W
Bug#1007962: sslsplit NMU: Bug #1007962: sslsplit FTBFS when only loopback interface is configured
* Timo Lindfors: > I hope it is ok to NMU this to get sslsplit back to Debian. If not, > please let me know! I'll wait wait for 10 days in case there are > comments from you, others in Debian or upstream. I also hope it is ok > to push these patches to salsa after the package has been uploaded. Please upload and push the changes. No need for delays. Cheers, -Hilko
Bug#1016506: marked as done (libghc-shake-{doc,dev,data}: all ship /usr/lib/haskell-packages/extra-packages/shake-0.19.6)
Your message dated Thu, 08 Sep 2022 21:50:16 +
with message-id
and subject line Bug#1016506: fixed in haskell-shake 0.19.6-2
has caused the Debian Bug report #1016506,
regarding libghc-shake-{doc,dev,data}: all ship
/usr/lib/haskell-packages/extra-packages/shake-0.19.6
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
1016506: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1016506
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libghc-shake-doc,libghc-shake-dev,libghc-shake-data
Version: 0.19.6-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Hi,
during a test with piuparts I noticed your package failed to install
because it tries to overwrite other packages files.
>From the attached log (scroll to the bottom...):
...
Selecting previously unselected package libghc-shake-data.
Preparing to unpack .../12-libghc-shake-data_0.19.6-1_all.deb ...
Unpacking libghc-shake-data (0.19.6-1) ...
dpkg: error processing archive
/tmp/apt-dpkg-install-2iAjjB/12-libghc-shake-data_0.19.6-1_all.deb (--unpack):
trying to overwrite '/usr/lib/haskell-packages/extra-packages/shake-0.19.6',
which is also in package libghc-shake-doc 0.19.6-1
Selecting previously unselected package libghc-unordered-containers-dev.
Preparing to unpack
.../13-libghc-unordered-containers-dev_0.2.17.0-2+b1_amd64.deb ...
Unpacking libghc-unordered-containers-dev (0.2.17.0-2+b1) ...
Selecting previously unselected package libghc-utf8-string-dev.
Preparing to unpack .../14-libghc-utf8-string-dev_1.0.2-1+b1_amd64.deb ...
Unpacking libghc-utf8-string-dev (1.0.2-1+b1) ...
Selecting previously unselected package libghc-shake-dev.
Preparing to unpack .../15-libghc-shake-dev_0.19.6-1_amd64.deb ...
Unpacking libghc-shake-dev (0.19.6-1) ...
dpkg: error processing archive
/tmp/apt-dpkg-install-2iAjjB/15-libghc-shake-dev_0.19.6-1_amd64.deb (--unpack):
trying to overwrite '/usr/lib/haskell-packages/extra-packages/shake-0.19.6',
which is also in package libghc-shake-doc 0.19.6-1
Errors were encountered while processing:
/tmp/apt-dpkg-install-2iAjjB/12-libghc-shake-data_0.19.6-1_all.deb
/tmp/apt-dpkg-install-2iAjjB/15-libghc-shake-dev_0.19.6-1_amd64.deb
...
cheers,
Andreas
libghc-shake-doc=0.19.6-1_libghc-shake-dev=0.19.6-1.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: haskell-shake
Source-Version: 0.19.6-2
Done: Clint Adams
We believe that the bug you reported is fixed in the latest version of
haskell-shake, 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 1016...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Clint Adams (supplier of updated haskell-shake 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: Wed, 07 Sep 2022 12:00:50 -0400
Source: haskell-shake
Architecture: source
Version: 0.19.6-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Haskell Group
Changed-By: Clint Adams
Closes: 1016506
Changes:
haskell-shake (0.19.6-2) unstable; urgency=medium
.
* Depend on newer haskell-devscripts to avoid duplicate
extra-packages issue. closes: #1016506.
Checksums-Sha1:
ae2eb1fe7debac7595ce8671cf8a8f3af6f3f693 3315 haskell-shake_0.19.6-2.dsc
6abde97fecfdbb2775f54ed5bd5b7eaaef8238c4 267771
haskell-shake_0.19.6.orig.tar.gz
197f2d3a98146e1482dac4a1153bdcd7e9fa90a7 4920
haskell-shake_0.19.6-2.debian.tar.xz
b190a9577ff57cc93baaee0e8556d7074ede4068 9103
haskell-shake_0.19.6-2_source.buildinfo
Checksums-Sha256:
dc3958ab6f0c36460f4e77dc11fc4b4ef8d00038113821310232ac5f632e0c7c 3315
haskell-shake_0.19.6-2.dsc
7d9db837bfd67acaaabdb3cea29acc15559ede82dd9f75d438589268031cd542 267771
haskell-shake_0.19.6.orig.tar.gz
c0a1cf5fbfaab42c33a6ad9b33643b731e33f31e8aaa9984419667ff0996646a 4920
haskell-shake_0.19.6-2.debian.tar.xz
6a86d6da9d4a842bdff4504e341b4761008f6af18e99df0eb075731873b9842d 9103
haskell-shake_0.19.6-2_source.buildinfo
Files:
a7952c27dd3fe08ee5abd34bf9ecc506 3315 haskell optional
haskell-shake_0.19.6-2.dsc
0a2a58613378f57beadd63d4bf8583da 267771 haskell optional
haskell-shake_0.19.6.or
Processed: forcibly merging 1017425 1019399
Processing commands for cont...@bugs.debian.org:
> forcemerge 1017425 1019399
Bug #1017425 {Done: Salvatore Bonaccorso } [src:linux]
[i386] Unconditional LFENCE instructions in FILL_RETURN_BUFFER
Bug #1017494 {Done: Salvatore Bonaccorso } [src:linux]
[i386] Unconditional LFENCE instructions in FILL_RETURN_BUFFER
Bug #1018060 {Done: Salvatore Bonaccorso } [src:linux]
linux-image-5.18.0-4-686-pae: crashes right away in switch_to_asm
Bug #1018776 {Done: Salvatore Bonaccorso } [src:linux]
linux-image-5.18.0-4-686-pae Kernel panic on Pentium 3 and Athlon XP
Bug #1019399 [src:linux] Fail to boot with kernel panic module switch_to_asm
Set Bug forwarded-to-address to
'https://lore.kernel.org/lkml/yv7arj%2fsvvhsd...@decadent.org.uk/'.
Severity set to 'grave' from 'critical'
Marked Bug as done
Marked as fixed in versions linux/5.10.140-1 and linux/5.19.6-1.
Marked as found in versions linux/5.18.16-1.
Added tag(s) confirmed.
Bug #1017494 {Done: Salvatore Bonaccorso } [src:linux]
[i386] Unconditional LFENCE instructions in FILL_RETURN_BUFFER
Bug #1018060 {Done: Salvatore Bonaccorso } [src:linux]
linux-image-5.18.0-4-686-pae: crashes right away in switch_to_asm
Bug #1018776 {Done: Salvatore Bonaccorso } [src:linux]
linux-image-5.18.0-4-686-pae Kernel panic on Pentium 3 and Athlon XP
Merged 1017425 1017494 1018060 1018776 1019399
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
1017425: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1017425
1017494: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1017494
1018060: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1018060
1018776: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1018776
1019399: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1019399
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#1018867: marked as done (luajit2: stop building on ppc64el)
Your message dated Thu, 8 Sep 2022 19:44:51 +0200 with message-id <8648d772-5f7c-897b-7957-54f539ae9...@debian.org> and subject line Re: luajit2: stop building on ppc64el has caused the Debian Bug report #1018867, regarding luajit2: stop building on ppc64el 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.) -- 1018867: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1018867 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: luajit2 Version: 2.1-20220411-5 Severity: serious Justification: broken Hi Mo, all, As a follow-up of our transition bug # 1012362, I just discussed with ftp-master on IRC to finally clean up the luajit* situation and I learned (I should have realized) that the first thing that needs to happen is that luajit2 doesn't build itself on ppc64el. If the binaries are still there, any reverse build dependency will just be rebuild if the those binaries are removed. If you can't (or don't want to) do this soon, I'll upload luajit2 with only ppc64el dropped from the Architectures field (well, convert `any` to the list where it builds). Please let me know if you want me to do that. Paul --- End Message --- --- Begin Message --- Version: 2.1-20220411-5.1 On Sat, 3 Sep 2022 13:25:00 +0200 Paul Gevers wrote: I have uploaded the attached debdiff to DELAYED/5. But I forgot to close the bug in the changelog. Paul OpenPGP_signature Description: OpenPGP digital signature --- End Message ---
Processed: Re: dwz: fails while building assaultcube
Processing control commands: > retitle 1016936 dwz: Unknown debugging section .debug_addr causes some builds > to fail Bug #1016936 [dwz] dwz: fails while building assaultcube Changed Bug title to 'dwz: Unknown debugging section .debug_addr causes some builds to fail' from 'dwz: fails while building assaultcube'. > tags 1016936 + upstream Bug #1016936 [dwz] dwz: Unknown debugging section .debug_addr causes some builds to fail Added tag(s) upstream. -- 1016936: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1016936 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1016936: dwz: fails while building assaultcube
Control: retitle 1016936 dwz: Unknown debugging section .debug_addr causes some builds to fail Control: tags 1016936 + upstream Hello, This error also occurred for me when building PolyMC under Clang, but not GCC. It seems this problem is common for many Clang builds [1]. Fedora also seems to be having issues with this; Thus, I'm retitling this bug to be more generic, and adding an upstream tag. I will create a bug when my Bugzilla account creation request is approved by the admin. Thanks, -- Ben Westover [1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997080#41 OpenPGP_signature Description: OpenPGP digital signature
Bug#1003463: marked as done (Functionally broken with current PHP)
Your message dated Thu, 08 Sep 2022 17:20:16 +
with message-id
and subject line Bug#1003463: fixed in phabricator 0~git20220903-1
has caused the Debian Bug report #1003463,
regarding Functionally broken with current PHP
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.)
--
1003463: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1003463
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: arcanist
Version: 0~git20200925-2
Severity: grave
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
I *think* this has been fixed upstream in
https://github.com/phacility/arcanist/commit/3626582354e4fc62191927a80b274ec71284cb77
and
https://github.com/phacility/arcanist/commit/b50a646a3f49c8b842cf0764c59ea2c38c2f9567
llvm-project$ /usr/bin/arc patch --nobranch D116766
PHP Deprecated: Function libxml_disable_entity_loader() is deprecated in
/usr/share/arcanist/support/init/init-script.php on line 92
Deprecated: Function libxml_disable_entity_loader() is deprecated in
/usr/share/arcanist/support/init/init-script.php on line 92
PHP Fatal error: Uncaught Exception: Error while loading file
"/usr/share/arcanist/src/object/Phobject.php": Return type of
Phobject::rewind() should either be compatible with Iterator::rewind(): void,
or the #[\ReturnTypeWillChange] attribute should be used to temporarily
suppress the notice in /usr/share/arcanist/src/init/lib/PhutilBootloader.php:275
Stack trace:
#0 /usr/share/arcanist/src/init/lib/PhutilBootloader.php(207):
PhutilBootloader->executeInclude()
#1 /usr/share/arcanist/src/symbols/PhutilSymbolLoader.php(422):
PhutilBootloader->loadLibrarySource()
#2 /usr/share/arcanist/src/symbols/PhutilSymbolLoader.php(277):
PhutilSymbolLoader->loadSymbol()
#3 /usr/share/arcanist/src/init/init-library.php(23):
PhutilSymbolLoader->selectAndLoadSymbols()
#4 /usr/share/arcanist/src/filesystem/Filesystem.php(18): __phutil_autoload()
#5 /usr/share/arcanist/src/init/lib/PhutilBootloader.php(247):
include_once('...')
#6 /usr/share/arcanist/src/init/lib/PhutilBootloader.php(207):
PhutilBootloader->executeInclude()
#7 /usr/share/arcanist/src/symbols/PhutilSymbolLoader.php(422):
PhutilBootloader->loadLibrarySource()
#8 /usr/share/arcanist/src/symbols/PhutilSymbolLoader.php(277):
PhutilSymbolLoader->loadSymbol()
#9 /usr/share/arcanist/src/init/init-library.php(23):
PhutilSymbolLoader->selectAndLoadSymbols()
#10 /usr/share/arcanist/src/init/lib/PhutilBootloader.php(97):
__phutil_autoload()
#11 /usr/share/arcanist/src/init/lib/PhutilBootloader.php(21):
PhutilBootloader->registerLibrary()
#12 /usr/share/arcanist/src/init/init-library.php(70):
PhutilBootloader::newLibrary()
#13 /usr/share/arcanist/support/init/init-script.php(96): require_once('...')
#14 /usr/share/arcanist/support/init/init-script.php(115):
__arcanist_init_script__()
#15 /usr/share/arcanist/support/init/init-arcanist.php(3): require_once('...')
#16 /usr/share/arcanist/bin/arc(10): require_once('...')
#17 {main}
thrown in /usr/share/arcanist/src/init/lib/PhutilBootloader.php on line 275
Fatal error: Uncaught Exception: Error while loading file
"/usr/share/arcanist/src/object/Phobject.php": Return type of
Phobject::rewind() should either be compatible with Iterator::rewind(): void,
or the #[\ReturnTypeWillChange] attribute should be used to temporarily
suppress the notice in /usr/share/arcanist/src/init/lib/PhutilBootloader.php:275
Stack trace:
#0 /usr/share/arcanist/src/init/lib/PhutilBootloader.php(207):
PhutilBootloader->executeInclude()
#1 /usr/share/arcanist/src/symbols/PhutilSymbolLoader.php(422):
PhutilBootloader->loadLibrarySource()
#2 /usr/share/arcanist/src/symbols/PhutilSymbolLoader.php(277):
PhutilSymbolLoader->loadSymbol()
#3 /usr/share/arcanist/src/init/init-library.php(23):
PhutilSymbolLoader->selectAndLoadSymbols()
#4 /usr/share/arcanist/src/filesystem/Filesystem.php(18): __phutil_autoload()
#5 /usr/share/arcanist/src/init/lib/PhutilBootloader.php(247):
include_once('...')
#6 /usr/share/arcanist/src/init/lib/PhutilBootloader.php(207):
PhutilBootloader->executeInclude()
#7 /usr/share/arcanist/src/symbols/PhutilSymbolLoader.php(422):
PhutilBootloader->loadLibrarySource()
#8 /usr/share/arcanist/src/symbols/PhutilSymbolLoader.php(277):
PhutilSymbolLoader->loadSymbol()
#9 /usr/share/arcanist/src/init/init-library.php(23):
PhutilSymbolLoader->selectAndLoadSymbols()
#10 /usr/share/arcanist/src/init/lib/PhutilBootloader.php(97):
__phutil_autoload()
#11 /usr/share/arcanist/src/init/lib/PhutilBootloader.php(21):
PhutilBootloader->registerLibrary()
#12 /usr/share/arcanist/src/init/
Bug#1017188: marked as done (python-exchangelib: FTBFS: AssertionError: Items in the first set but not the second:)
Your message dated Thu, 08 Sep 2022 17:20:56 +
with message-id
and subject line Bug#1017188: fixed in python-exchangelib 4.7.6-1
has caused the Debian Bug report #1017188,
regarding python-exchangelib: FTBFS: AssertionError: Items in the first set but
not the second:
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.)
--
1017188: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1017188
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-exchangelib
Version: 4.7.2-2
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20220813 ftbfs-bookworm
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> dh_auto_test -- --system=custom --test-args="cd {build_dir}; {interpreter} -m
> unittest"
> I: pybuild base:239: cd
> /<>/.pybuild/cpython3_3.10_exchangelib/build; python3.10 -m
> unittest
> ..sss.s.sss..sss.s..s...F...s
> ==
> FAIL: test_ewstimezone (tests.test_ewsdatetime.EWSDateTimeTest)
> --
> Traceback (most recent call last):
> File
> "/<>/.pybuild/cpython3_3.10_exchangelib/build/tests/test_ewsdatetime.py",
> line 68, in test_ewstimezone
> self.assertEqual(set(sanitized) - set(EWSTimeZone.IANA_TO_MS_MAP), set())
> AssertionError: Items in the first set but not the second:
> 'Europe/Kyiv'
>
> --
> Ran 60 tests in 0.095s
>
> FAILED (failures=1, skipped=25)
> Skipping TasksTest - no settings.yml file found
> Copy settings.yml.sample to settings.yml and enter values for your test server
> Skipping BulkMethodTest - no settings.yml file found
> Copy settings.yml.sample to settings.yml and enter values for your test server
> Skipping CalendarBulkMethodTest - no settings.yml file found
> Copy settings.yml.sample to settings.yml and enter values for your test server
> Skipping ContactsTest - no settings.yml file found
> Copy settings.yml.sample to settings.yml and enter values for your test server
> Skipping FolderTest - no settings.yml file found
> Copy settings.yml.sample to settings.yml and enter values for your test server
> Skipping CalendarTest - no settings.yml file found
> Copy settings.yml.sample to settings.yml and enter values for your test server
> Skipping AutodiscoverTest - no settings.yml file found
> Copy settings.yml.sample to settings.yml and enter values for your test server
> Skipping ItemQuerySetTest - no settings.yml file found
> Copy settings.yml.sample to settings.yml and enter values for your test server
> Skipping AttachmentsTest - no settings.yml file found
> Copy settings.yml.sample to settings.yml and enter values for your test server
> Skipping ExtendedPropertyTest - no settings.yml file found
> Copy settings.yml.sample to settings.yml and enter values for your test server
> Skipping MessagesTest - no settings.yml file found
> Copy settings.yml.sample to settings.yml and enter values for your test server
> Skipping GenericItemTest - no settings.yml file found
> Copy settings.yml.sample to settings.yml and enter values for your test server
> Skipping SyncTest - no settings.yml file found
> Copy settings.yml.sample to settings.yml and enter values for your test server
> Skipping AccountTest - no settings.yml file found
> Copy settings.yml.sample to settings.yml and enter values for your test server
> Skipping ServicesTest - no settings.yml file found
> Copy settings.yml.sample to settings.yml and enter values for your test server
> Skipping ProtocolTest - no settings.yml file found
> Copy settings.yml.sample to settings.yml and enter values for your test server
> Skipping ItemHelperTest - no settings.yml file found
> Copy settings.yml.sample to settings.yml and enter values for your test server
> Skipping CommonTest - no settings.yml file found
> Copy settings.yml.sample to settings.yml and enter values for your test server
> Skipping UtilTest - no settings.yml file found
> Copy settings.yml.sample to settings.yml and enter values for your test server
> E: pybuild pybuild:369: test: plugin custom failed with: exit code=1: cd
> /<>/.pybuild/cpython3_3.10_exchangelib/build; python3.10 -m
> unittest
> dh_auto_test: error: pybuild --test -i python{version} -p 3.10
> --system=custom "--test-args=cd {build_dir}; {interpreter} -m unittest"
> returned
Bug#930722: marked as done (arc, arcanist: Both ship arc binary)
Your message dated Thu, 08 Sep 2022 17:20:16 + with message-id and subject line Bug#919697: fixed in phabricator 0~git20220903-1 has caused the Debian Bug report #919697, regarding arc, arcanist: Both ship arc binary to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 919697: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=919697 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: arc,arcanist Severity: serious arc: /usr/bin/arc arcanist: /usr/bin/arc One of them needs to be renamed, or both. -- System Information: Debian Release: buster/sid APT prefers eoan APT policy: (991, 'eoan'), (500, 'eoan'), (500, 'cosmic-security') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.0.0-15-generic (SMP w/8 CPU cores) Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled -- debian developer - deb.li/jak | jak-linux.org - free software dev ubuntu core developer i speak de, en --- End Message --- --- Begin Message --- Source: phabricator Source-Version: 0~git20220903-1 Done: Christoph Biedl We believe that the bug you reported is fixed in the latest version of phabricator, 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 919...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Christoph Biedl (supplier of updated phabricator package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Mon, 05 Sep 2022 20:02:43 +0200 Source: phabricator Architecture: source Version: 0~git20220903-1 Distribution: unstable Urgency: medium Maintainer: Sylvestre Ledru Changed-By: Christoph Biedl Closes: 919697 1003463 Changes: phabricator (0~git20220903-1) unstable; urgency=medium . * get-orig-source: Update github URLs to https, make reproducible * Update to latest commits upstream. Closes: #1003463 * Revert "Provide the phabrication notification service "aphlict" as a separate package" * Install the arc program as arcanist. Closes: #919697 Checksums-Sha1: a6ddc898149f1684e4b58b3e941cd834a119b191 2623 phabricator_0~git20220903-1.dsc 52f773df5cd2f45c301b79cff39fc447935693e8 1177384 phabricator_0~git20220903.orig-arcanist.tar.xz 4894b6bf78a11b53fc25da2649a88609dcf0c193 496 phabricator_0~git20220903.orig-libphutil.tar.xz e2492a4e9c6c8cc94d46880e76647dad53b0a657 6198004 phabricator_0~git20220903.orig.tar.xz 6c3a7a1b4277a539adedc14f4c19c1b263601fde 47480 phabricator_0~git20220903-1.debian.tar.xz 2dc198ffbfdeaefc7bcd2b361668bdb815b48269 6027 phabricator_0~git20220903-1_armel.buildinfo Checksums-Sha256: f2c319933bdf57e5d275ed18d93b3d78e01fdc35af9c5f3b07326c416d0da550 2623 phabricator_0~git20220903-1.dsc 1dd1d01f87ec03caedaa7e8425c24f5c9996016041b8e6e5fadb73c070385e8f 1177384 phabricator_0~git20220903.orig-arcanist.tar.xz f876d9bc150ecdae110792c2b9b5da47b2289ada83be6c5a3f7ac8f26560 496 phabricator_0~git20220903.orig-libphutil.tar.xz 53ec2e92b51f36581d386768ccf8602dc73f272b0624a0e1cfed8726733b3fbb 6198004 phabricator_0~git20220903.orig.tar.xz 5c0dda07e0553c1d500fd8cbbad1ac765f524bd8ea4f180cf34f0a02586cbfb4 47480 phabricator_0~git20220903-1.debian.tar.xz ae88920454f44585f1e5f5997ca4d1dbdd36da4bdf4adc9211c3efcf30cfd528 6027 phabricator_0~git20220903-1_armel.buildinfo Files: 40a1e1f4655089ea85ba7ae996e14c10 2623 web optional phabricator_0~git20220903-1.dsc 0ee80dc64e2021973643d44bc6b55a26 1177384 web optional phabricator_0~git20220903.orig-arcanist.tar.xz 4dc30dd2757304262bc734c893a447e4 496 web optional phabricator_0~git20220903.orig-libphutil.tar.xz f120636aac4dcaad3c854b7aa3b66bf2 6198004 web optional phabricator_0~git20220903.orig.tar.xz d32e3e8c46034dfd7ba45a3a5f495dd2 47480 web optional phabricator_0~git20220903-1.debian.tar.xz d72b22f9d3ac7fa75cf8accfbd69f039 6027 web optional phabricator_0~git20220903-1_armel.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEWXMI+726A12MfJXdxCxY61kUkv0FAmMaHv0ACgkQxCxY61
Bug#919697: marked as done (arcanist: file conflict with arc)
Your message dated Thu, 08 Sep 2022 17:20:16 + with message-id and subject line Bug#919697: fixed in phabricator 0~git20220903-1 has caused the Debian Bug report #919697, regarding arcanist: file conflict with arc 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.) -- 919697: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=919697 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: arcanist Severity: serious Justification: Policy §10.1 This package ships /usr/bin/arc, which is also shipped by unrelated package arc. Policy says: “Two different packages must not install programs with different functionality but with the same filenames.” -- Jakub Wilk --- End Message --- --- Begin Message --- Source: phabricator Source-Version: 0~git20220903-1 Done: Christoph Biedl We believe that the bug you reported is fixed in the latest version of phabricator, 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 919...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Christoph Biedl (supplier of updated phabricator package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Mon, 05 Sep 2022 20:02:43 +0200 Source: phabricator Architecture: source Version: 0~git20220903-1 Distribution: unstable Urgency: medium Maintainer: Sylvestre Ledru Changed-By: Christoph Biedl Closes: 919697 1003463 Changes: phabricator (0~git20220903-1) unstable; urgency=medium . * get-orig-source: Update github URLs to https, make reproducible * Update to latest commits upstream. Closes: #1003463 * Revert "Provide the phabrication notification service "aphlict" as a separate package" * Install the arc program as arcanist. Closes: #919697 Checksums-Sha1: a6ddc898149f1684e4b58b3e941cd834a119b191 2623 phabricator_0~git20220903-1.dsc 52f773df5cd2f45c301b79cff39fc447935693e8 1177384 phabricator_0~git20220903.orig-arcanist.tar.xz 4894b6bf78a11b53fc25da2649a88609dcf0c193 496 phabricator_0~git20220903.orig-libphutil.tar.xz e2492a4e9c6c8cc94d46880e76647dad53b0a657 6198004 phabricator_0~git20220903.orig.tar.xz 6c3a7a1b4277a539adedc14f4c19c1b263601fde 47480 phabricator_0~git20220903-1.debian.tar.xz 2dc198ffbfdeaefc7bcd2b361668bdb815b48269 6027 phabricator_0~git20220903-1_armel.buildinfo Checksums-Sha256: f2c319933bdf57e5d275ed18d93b3d78e01fdc35af9c5f3b07326c416d0da550 2623 phabricator_0~git20220903-1.dsc 1dd1d01f87ec03caedaa7e8425c24f5c9996016041b8e6e5fadb73c070385e8f 1177384 phabricator_0~git20220903.orig-arcanist.tar.xz f876d9bc150ecdae110792c2b9b5da47b2289ada83be6c5a3f7ac8f26560 496 phabricator_0~git20220903.orig-libphutil.tar.xz 53ec2e92b51f36581d386768ccf8602dc73f272b0624a0e1cfed8726733b3fbb 6198004 phabricator_0~git20220903.orig.tar.xz 5c0dda07e0553c1d500fd8cbbad1ac765f524bd8ea4f180cf34f0a02586cbfb4 47480 phabricator_0~git20220903-1.debian.tar.xz ae88920454f44585f1e5f5997ca4d1dbdd36da4bdf4adc9211c3efcf30cfd528 6027 phabricator_0~git20220903-1_armel.buildinfo Files: 40a1e1f4655089ea85ba7ae996e14c10 2623 web optional phabricator_0~git20220903-1.dsc 0ee80dc64e2021973643d44bc6b55a26 1177384 web optional phabricator_0~git20220903.orig-arcanist.tar.xz 4dc30dd2757304262bc734c893a447e4 496 web optional phabricator_0~git20220903.orig-libphutil.tar.xz f120636aac4dcaad3c854b7aa3b66bf2 6198004 web optional phabricator_0~git20220903.orig.tar.xz d32e3e8c46034dfd7ba45a3a5f495dd2 47480 web optional phabricator_0~git20220903-1.debian.tar.xz d72b22f9d3ac7fa75cf8accfbd69f039 6027 web optional phabricator_0~git20220903-1_armel.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEWXMI+726A12MfJXdxCxY61kUkv0FAmMaHv0ACgkQxCxY61kU kv3n5A/8CKGCnzg7qZiaL+LGDztuVyAhpk8A2yYPoi4F3bVsnOyc1eyc77to1dHX aCN/IYLweYmQ35HgAqzkSewp/MOrn9nV1B0egvqJ+agREDRdwb1K/twZTNcRIYwU C65gYW3A0MrjVTWXOmqXg4ftJ26NVWhMptGOFiyt467RtXCg5H+/tKq+jvVcVS0u 9R7EllASweuX7r2OEvqRgnwD2B16M6vprDJVad0LOgvCZliN6tvVtCznp1FKLjnw jETB/HCaNsJuBAV0xEsJZGaZBcxDjXH3aVm0xEuDE4piykGo7Ai4N1AXdT70Q/nY HR7JDPMSq2T4DD4n0jkmpt8ObVQtNQiDAmE1EyQQ4iuFm4Fl+pXmk2mBe4TvJoiy n/JsC6DwdM8sNgK6NHAXUA2jXfaHoQ6UF4E5s6uIX0eOXDlfLCDfQSamJGK2fR7N dz/A/e67EjcHPqKClF5bCTN6Kf
Bug#1019388: Acknowledgement (apt-clone: Fails to run - no /usr/bin/dpkg-repack found)
Fixed by installing dpkg-repack. So maybe this is just a dependency issue? On 9/8/22 07:39, Debian Bug Tracking System wrote: Thank you for filing a new Bug report with Debian. You can follow progress on this Bug here: 1019388: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1019388. This is an automatically generated reply to let you know your message has been received. Your message is being forwarded to the package maintainers and other interested parties for their attention; they will reply in due course. As you requested using X-Debbugs-CC, your message was also forwarded to baronr...@gmail.com (after having been given a Bug report number, if it did not have one). Your message has been sent to the package maintainer(s): Michael Vogt If you wish to submit further information on this problem, please send it to 1019...@bugs.debian.org. Please do not send mail to ow...@bugs.debian.org unless you wish to report a problem with the Bug-tracking system. -- -- Rann Bar-On he/him/his
Bug#1018971: marked as done (poppler: CVE-2022-38784)
Your message dated Thu, 08 Sep 2022 15:49:04 + with message-id and subject line Bug#1018971: fixed in poppler 22.08.0-2.1 has caused the Debian Bug report #1018971, regarding poppler: CVE-2022-38784 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.) -- 1018971: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1018971 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: poppler Version: 22.08.0-2 Severity: grave Tags: security upstream X-Debbugs-Cc: car...@debian.org, Debian Security Team Hi, The following vulnerability was published for poppler. CVE-2022-38784[0]: | Poppler prior to and including 22.08.0 contains an integer overflow in | the JBIG2 decoder (JBIG2Stream::readTextRegionSeg() in JBIGStream.cc). | Processing a specially crafted PDF file or JBIG2 image could lead to a | crash or the execution of arbitrary code. This is similar to the | vulnerability described by CVE-2022-38171 in Xpdf. 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-2022-38784 https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-38784 [1] https://gitlab.freedesktop.org/poppler/poppler/-/commit/27354e9d9696ee2bc063910a6c9a6b27c5184a52 [2] https://gist.github.com/zmanion/b2ed0d1a0cec163ecd07d5e3d9740dc6 Please adjust the affected versions in the BTS as needed. Regards, Salvatore --- End Message --- --- Begin Message --- Source: poppler Source-Version: 22.08.0-2.1 Done: Salvatore Bonaccorso We believe that the bug you reported is fixed in the latest version of poppler, 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 1018...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Salvatore Bonaccorso (supplier of updated poppler 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, 03 Sep 2022 21:30:51 +0200 Source: poppler Built-For-Profiles: noudeb Architecture: source Version: 22.08.0-2.1 Distribution: unstable Urgency: medium Maintainer: Debian freedesktop.org maintainers Changed-By: Salvatore Bonaccorso Closes: 1018971 Changes: poppler (22.08.0-2.1) unstable; urgency=medium . * Non-maintainer upload. * JBIG2Stream: Fix crash on broken file (CVE-2022-38784) (Closes: #1018971) Checksums-Sha1: f12beba67800947a34d6d6de3e8c34484e308642 3253 poppler_22.08.0-2.1.dsc f21a6c04cd75b91a436316b2d1d8dab2f23ae3ed 37608 poppler_22.08.0-2.1.debian.tar.xz a80d6dc4b3a965c7396e0031803abecebfeeabf4 15959 poppler_22.08.0-2.1_source.buildinfo Checksums-Sha256: e3eed305cea51907f0620eab90cef097af692ec5773e96cba9d008f39c15 3253 poppler_22.08.0-2.1.dsc 22ef8a4971956c61e60a56b1355af8b2e7a4a8fab619d6757fb224458ea3f63d 37608 poppler_22.08.0-2.1.debian.tar.xz 899dad5dd1f5596bc49cf3b4042e2bf93e6c2f32ff968017412e09097d74a30f 15959 poppler_22.08.0-2.1_source.buildinfo Files: a301f9fbbc9600e5b93ba759447f3f2b 3253 devel optional poppler_22.08.0-2.1.dsc af455e488373114938ce81ec5c8870c9 37608 devel optional poppler_22.08.0-2.1.debian.tar.xz e2c2afd525c1a13ee47559ccc4f3258e 15959 devel optional poppler_22.08.0-2.1_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEETQvhLw5HdtiqzpaW5mx3Wuv+bH0FAmMZ+fIACgkQ5mx3Wuv+ bH31gw//X8NZvbJKOThPx26XMdddC8LYRtlmW1LW8e6t1baGqzVqaFN3rWKlB525 C/xvJexSrIjKOUpgdW6xvBix23KHcU2SZYFbO46rYy6fa1/LCPj6KQ3ULIHbKo1Y bkM1K/3CPJGSWgAuYjilPnDc+iWwwh8jz2jZ2QrW7kwqC8dIX1/BchPxGo5B9mwM rPVQ3wfynagJFEcvfY53G8lMtLa8uJWrj2TG35NmyhF8Frkw58YuK9HgixUEb2Ov QtBjytNXZgZLhAhtgqBgIXoEfaqM28rjZzp6EuZfe7Y1vpJ8taov2CAzK9yzeiGZ KU2VR+WS8DtTk9CcYGxV+IiSRmTFpAX2MShMhPl1GPc6vNWissq1MoKDbcEcABgD Hrx+AG3cRcb1kYTWYQqTYwbuhGrrTYovB58v6NfUVA/0yTzU4DOqVG1Yj4fNKZsc 3yqck/MiXw3L4gcY5UZ2Qg/NKvlpN3qPBVAWjMtWwpNkowcxv+krxacrI6yAXEBm yOMYAjBS9BSYeUWJHwf8lReuAgEBQn01osbf3NGnWl9AUJ0F1whA9Rpw1jneg/aa UjAJCPJNz7zW5SfB68jiZX5rYq7zlOGh1WtZ+zRJ012Ke9Pw1QaM0ydOYiknsLe4 Io6zvdBFDs5Pi/2hAi4MM5dZnub9cBn0p+eLszz6ZfYd6z6+O6s= =v2Ga -END PGP SIGNATURE End Message ---
Bug#1019394: rails breaks ruby-arbre autopkgtest: different output
Source: rails, ruby-arbre Control: found -1 rails/2:6.1.6.1+dfsg-4 Control: found -1 ruby-arbre/1.4.0-1 Severity: serious Tags: sid bookworm User: debian...@lists.debian.org Usertags: breaks needs-update Dear maintainer(s), With a recent upload of rails the autopkgtest of ruby-arbre fails in testing when that autopkgtest is run with the binary packages of rails from unstable. It passes when run with only packages from testing. In tabular form: passfail rails from testing2:6.1.6.1+dfsg-4 ruby-arbre from testing1.4.0-1 all others from testingfrom testing I copied some of the output at the bottom of this report. Currently this regression is blocking the migration of rails to testing [1]. Due to the nature of this issue, I filed this bug report against both packages. Can you please investigate the situation and reassign the bug to the right package? More information about this bug and the reason for filing it can be found on https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation Paul [1] https://qa.debian.org/excuses.php?package=rails https://ci.debian.net/data/autopkgtest/testing/amd64/r/ruby-arbre/25833919/log.gz Failures: 1) Building forms building a simple form for should include the hidden authenticity token Failure/Error: expect(html).to include 'name="authenticity_token" value="AUTH_TOKEN" />' expected "id=\"new_mock_person_\" action=\"/\" accept-charset=\"UTF-8\" method...e\">Nameid=\"mock_person_name\" />\n" to include "name=\"authenticity_token\" value=\"AUTH_TOKEN\" />" Diff: @@ -1,2 +1,3 @@ -value="AUTH_TOKEN" /> +accept-charset="UTF-8" method="post">value="✓" autocomplete="off" />name="authenticity_token" value="AUTH_TOKEN" autocomplete="off" /> +Namename="mock_person[name]" id="mock_person_name" /> # ./spec/rails/integration/forms_spec.rb:25:in `block (3 levels) in ' Finished in 0.23882 seconds (files took 1.79 seconds to load) 128 examples, 1 failure Failed examples: rspec ./spec/rails/integration/forms_spec.rb:24 # Building forms building a simple form for should include the hidden authenticity token /usr/bin/ruby3.0 -I/usr/share/rubygems-integration/all/gems/rspec-support-3.10.3/lib:/usr/share/rubygems-integration/all/gems/rspec-core-3.10.1/lib /usr/share/rubygems-integration/all/gems/rspec-core-3.10.1/exe/rspec --pattern ./spec/\*\*/\*_spec.rb --format documentation failed mv ./.gem2deb.lib lib mv ./.gem2deb.Gemfile.lock Gemfile.lock autopkgtest [04:15:16]: test gem2deb-test-runner OpenPGP_signature Description: OpenPGP digital signature
Processed: rails breaks ruby-arbre autopkgtest: different output
Processing control commands: > found -1 rails/2:6.1.6.1+dfsg-4 Bug #1019394 [src:rails, src:ruby-arbre] rails breaks ruby-arbre autopkgtest: different output Marked as found in versions rails/2:6.1.6.1+dfsg-4. > found -1 ruby-arbre/1.4.0-1 Bug #1019394 [src:rails, src:ruby-arbre] rails breaks ruby-arbre autopkgtest: different output Marked as found in versions ruby-arbre/1.4.0-1. -- 1019394: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1019394 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: hdf5 breaks libsis-jhdf5-java autopkgtest: Could not initialize class
Processing control commands: > found -1 hdf5/1.10.8+repack-1 Bug #1019393 [src:hdf5, src:libsis-jhdf5-java] hdf5 breaks libsis-jhdf5-java autopkgtest: Could not initialize class Marked as found in versions hdf5/1.10.8+repack-1. > found -1 libsis-jhdf5-java/19.04.1+dfsg-1 Bug #1019393 [src:hdf5, src:libsis-jhdf5-java] hdf5 breaks libsis-jhdf5-java autopkgtest: Could not initialize class Marked as found in versions libsis-jhdf5-java/19.04.1+dfsg-1. -- 1019393: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1019393 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1019393: hdf5 breaks libsis-jhdf5-java autopkgtest: Could not initialize class
Source: hdf5, libsis-jhdf5-java
Control: found -1 hdf5/1.10.8+repack-1
Control: found -1 libsis-jhdf5-java/19.04.1+dfsg-1
Severity: serious
Tags: sid bookworm
User: debian...@lists.debian.org
Usertags: breaks needs-update
Dear maintainer(s),
With a recent upload of hdf5 the autopkgtest of libsis-jhdf5-java fails
in testing when that autopkgtest is run with the binary packages of hdf5
from unstable. It passes when run with only packages from testing. In
tabular form:
passfail
hdf5 from testing1.10.8+repack-1
libsis-jhdf5-java from testing19.04.1+dfsg-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 hdf5 to testing
[1]. Due to the nature of this issue, I filed this bug report against
both packages. Can you please investigate the situation and reassign the
bug to the right package?
More information about this bug and the reason for filing it can be found on
https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation
Paul
[1] https://qa.debian.org/excuses.php?package=hdf5
https://ci.debian.net/data/autopkgtest/testing/amd64/libs/libsis-jhdf5-java/25831074/log.gz
Note: Some input files use or override a deprecated API.
Note: Recompile with -Xlint:deprecation for details.
[TestNGContentHandler] [WARN] It is strongly recommended to add
"http://testng.org/testng-1.0.dtd"; >" at the top
of your file, otherwise TestNG may fail or not work as expected.
[TestNG] Running:
/tmp/autopkgtest-lxc.50ajov7f/downtmp/build.MuO/src/sourceTest/java/tests.xml
sourceTest/java/ch/systemsx/cisd/hdf5/h5ar/test.h5ar
sourceTest/java/ch/systemsx/cisd/hdf5/h5ar/test_14_12_0.h5ar
[Utils] Attempting to create /tmp/tmp.FUdpvQH0CP/test-output/All/All.xml
[Utils] Directory /tmp/tmp.FUdpvQH0CP/test-output/All exists: true
PASSED: testBitSetArrayRoundTrip([Ljava.util.BitSet;@697a0948)
PASSED: testBitSetArrayRoundTrip([Ljava.util.BitSet;@7cf63b9a)
PASSED: testBitSetArrayRoundTrip([Ljava.util.BitSet;@4776e209)
PASSED: testBitSetArrayRoundTrip([Ljava.util.BitSet;@265a094b)
PASSED: testBitSetArrayRoundTrip([Ljava.util.BitSet;@1f536481)
PASSED: testBitSetArrayRoundTrip([Ljava.util.BitSet;@5234b61a)
PASSED: testBitSetArrayRoundTrip([Ljava.util.BitSet;@22a260ff)
PASSED: testBitSetArrayRoundTrip([Ljava.util.BitSet;@54c425b1)
PASSED: testBitSetArrayRoundTrip([Ljava.util.BitSet;@50b734c4)
PASSED: testBitSetRoundTrip({})
PASSED: testBitSetRoundTrip({0})
PASSED: testBitSetRoundTrip({31})
PASSED: testBitSetRoundTrip({64})
PASSED: testBitSetRoundTrip({128})
PASSED: testBitSetRoundTrip({63, 191})
PASSED: testBitSetRoundTrip({64, 192})
PASSED: testBitSetRoundTrip({17, 88, 155})
PASSED: testBitSetRoundTrip({0, 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12,
13, 14, 15, 16, 17, 18, 19, 20, 21, 22, 23, 24, 25, 26, 27, 28, 29, 30,
31, 32, 33, 34, 35, 36, 37, 38, 39, 40, 41, 42, 43, 44, 45, 46, 47, 48,
49, 50, 51, 52, 53, 54, 55, 56, 57, 58, 59, 60, 61, 62, 63, 64, 65, 66,
67, 68, 69, 70, 71, 72, 73, 74, 75, 76, 77, 78, 79, 80, 81, 82, 83, 84,
85, 86, 87, 88, 89, 90, 91, 92, 93, 94, 95, 96, 97, 98, 99, 100, 101,
102, 103, 104, 105, 106, 107, 108, 109, 110, 111, 112, 113, 114, 115,
116, 117, 118, 119, 120, 121, 122, 123, 124, 125, 126, 127, 128, 129,
130, 131, 132, 133, 134, 135, 136, 137, 138, 139, 140, 141, 142, 143,
144, 145, 146, 147, 148, 149, 150, 151, 152, 153, 154, 155, 156, 157,
158, 159, 160, 161, 162, 163, 164, 165, 166, 167, 168, 169, 170, 171,
172, 173, 174, 175, 176, 177, 178, 179, 180, 181, 182, 183, 184, 185,
186, 187, 188, 189, 190, 191, 192, 193, 194, 195, 196, 197, 198, 199,
200, 201, 202, 203, 204, 205, 206, 207, 208, 209, 210, 211, 212, 213,
214, 215, 216, 217, 218, 219, 220, 221, 222, 223, 224, 225, 226, 227,
228, 229, 230, 231, 232, 233, 234, 235, 236, 237, 238, 239, 240, 241,
242, 243, 244, 245, 246, 247, 248, 249, 250, 251, 252, 253, 254, 255})
PASSED: testAttributeTypeVariantAttributeName
PASSED: testConversion
PASSED: testTypeVariant
PASSED: testFileExistsOnFS
PASSED: testOnlyFileAndDirExistsOnFS
PASSED: testConcatLink
PASSED: testGetParentPath
PASSED: testNormalizePath
PASSED: testDescribeLink
PASSED: testGetPermissions
PASSED: testIdCache
PASSED: testToInt64
PASSED: testToInt64_Overflow
PASSED: testToUint16
PASSED: testToUint32
PASSED: testToUint8
PASSED: testIncrementIdx
PASSED: testConvertUnit
PASSED: testCompressAll
PASSED: testCompressBlackList
PASSED: testCompressBlackWhiteList
PASSED: testCompressDefault
PASSED: testCompressDefaultWithCompression
PASSED: testCompressWhiteList
FAILED: testAccessClosedReaderWriter
java.lang.ExceptionInInitializerError
at hdf.hdf5lib.HDF5Constants.(HDF5Constants.java:29)
at
ch.systemsx.cisd.hdf5.IHDF5WriterConfigurator$FileFormatVersion.(IHDF5WriterConfigurator.java:74)
at
ch.systemsx.cisd.hdf5.IHDF5WriterConfigurator$FileFormatVersionBounds.(IHDF5WriterConfigura
Bug#1019392: toybox: autopkgtest regression on ppc64el: exited with signal (or returned 255)
Source: toybox
Version: 0.8.8+dfsg-1
Severity: serious
User: debian...@lists.debian.org
Usertags: regression
Dear maintainer(s),
With a recent upload of toybox the autopkgtest of toybox fails in
testing when that autopkgtest is run with the binary packages of toybox
from unstable. It passes when run with only packages from testing. In
tabular form:
passfail
toybox from testing0.8.8+dfsg-1
all others from testingfrom testing
I copied some of the output at the bottom of this report.
Currently this regression is blocking the migration to testing [1]. Can
you please investigate the situation and fix it?
More information about this bug and the reason for filing it can be found on
https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation
Paul
[1] https://qa.debian.org/excuses.php?package=toybox
https://ci.debian.net/data/autopkgtest/testing/ppc64el/t/toybox/25825642/log.gz
# README:
# The maximum sane configuration is "make defconfig": allyesconfig isn't
CFLAGS="-g -O2
-ffile-prefix-map=/tmp/autopkgtest-lxc.ftn7u0vb/downtmp/build.Qwz/src=.
-fstack-protector-strong -Wformat -Werror=format-security -Wdate-time
-D_FORTIFY_SOURCE=2 -Wl,-z,relro -Wl,-z,now" make defconfig
make[1]: Entering directory
'/tmp/autopkgtest-lxc.ftn7u0vb/downtmp/build.Qwz/src'
cc -g -O2
-ffile-prefix-map=/tmp/autopkgtest-lxc.ftn7u0vb/downtmp/build.Qwz/src=.
-fstack-protector-strong -Wformat -Werror=format-security -Wdate-time
-D_FORTIFY_SOURCE=2 -Wl,-z,relro -Wl,-z,now -o kconfig/conf
kconfig/conf.c kconfig/zconf.tab.c -DKBUILD_NO_NLS=1 \
-DPROJECT_NAME=\"ToyBox\"
kconfig/conf.c: In function ‘conf_askvalue’:
kconfig/conf.c:104:17: warning: ignoring return value of ‘fgets’
declared with attribute ‘warn_unused_result’ [-Wunused-result]
104 | fgets(line, 128, stdin);
| ^~~
kconfig/conf.c: In function ‘conf_choice’:
kconfig/conf.c:359:25: warning: ignoring return value of ‘fgets’
declared with attribute ‘warn_unused_result’ [-Wunused-result]
359 | fgets(line, 128, stdin);
| ^~~
scripts/genconfig.sh
kconfig/conf -D /dev/null Config.in > /dev/null
make[1]: Leaving directory
'/tmp/autopkgtest-lxc.ftn7u0vb/downtmp/build.Qwz/src'
# Go for insanely overpowered toys!
# allyesconfig add build-depends: libssl-dev zlib1g-dev
#CFLAGS="-g -O2
-ffile-prefix-map=/tmp/autopkgtest-lxc.ftn7u0vb/downtmp/build.Qwz/src=.
-fstack-protector-strong -Wformat -Werror=format-security -Wdate-time
-D_FORTIFY_SOURCE=2 -Wl,-z,relro -Wl,-z,now" make allyesconfig
# Hardening and such FLAGS
echo -g -O2
-ffile-prefix-map=/tmp/autopkgtest-lxc.ftn7u0vb/downtmp/build.Qwz/src=.
-fstack-protector-strong -Wformat -Werror=format-security > generated/cflags
echo -Wdate-time -D_FORTIFY_SOURCE=2 >> generated/cflags
scripts/test.sh
make[1]: Entering directory
'/tmp/autopkgtest-lxc.ftn7u0vb/downtmp/build.Qwz/src'
scripts/install.sh --symlink --force
Compile instlist...
Library probe
generated/{Config.in,newtoys.h,flags.h,globals.h,tags.h,help.h}
Install commands...
make[1]: Leaving directory
'/tmp/autopkgtest-lxc.ftn7u0vb/downtmp/build.Qwz/src'
PASS: base32 simple
PASS: base32 file
PASS: base32 simple -d
PASS: base32 file -d
PASS: base32 default wrap
PASS: base32 multiline -d PASS: base32 -w
PASS: base32 -w0
PASS: base64 simple
PASS: base64 file
PASS: base64 simple -d
PASS: base64 simple -d
PASS: base64 default wrap
PASS: base64 multiline -d PASS: base64 -w
PASS: base64 -w0
PASS: basename /-only
PASS: basename trailing /
PASS: basename combined
PASS: basename suffix
PASS: basename suffix=result
PASS: basename reappearing suffix 1
PASS: basename reappearing suffix 2
PASS: basename invalid suffix
PASS: basename zero-length suffix
PASS: basename -s
PASS: basename -s implies -a
PASS: basename -a
PASS: blkid cramfs
PASS: blkid ext2
PASS: blkid ext3
PASS: blkid ext4
PASS: blkid f2fs
PASS: blkid msdos
PASS: blkid ntfs
PASS: blkid reiserfs
PASS: blkid squashfs
PASS: blkid vfat
PASS: blkid xfs
PASS: blkid stdin
PASS: blkid -o value -s
PASS: blkid -o export
PASS: bzcat 2 known files
PASS: bzcat overflow
PASS: bzcat badcrc
PASS: cat cat
PASS: cat -
PASS: cat file1 file2
PASS: cat - file
PASS: cat file -
PASS: cat file1 notfound file2
PASS: cat binary
PASS: cat - file1
PASS: cat > /dev/full
SKIP: chattr (not root)
SKIP: chgrp (not root)
PASS: chmod 000 dir
PASS: chmod 000 file
PASS: chmod 007 dir
PASS: chmod 007 file
PASS: chmod 030 dir
PASS: chmod 030 file
PASS: chmod 037 dir
PASS: chmod 037 file
PASS: chmod 060 dir
PASS: chmod 060 file
PASS: chmod 067 dir
PASS: chmod 067 file
PASS: chmod 100 dir
PASS: chmod 100 file
PASS: chmod 107 dir
PASS: chmod 107 file
PASS: chmod 130 dir
PASS: chmod 130 file
PASS: chmod 137 dir
PASS: chmod 137 file
PASS: chmod 160 dir
PASS: chmod 160 file
PASS: chmod 167 dir
PASS: chmod 167 file
PASS: chmod 200
Bug#1019391: python-typing-inspect breaks python-marshmallow-dataclass autopkgtest: TypeError: CustomTypeNoneValidator is not a dataclass
Source: python-typing-inspect, python-marshmallow-dataclass
Control: found -1 python-typing-inspect/0.8.0-1
Control: found -1 python-marshmallow-dataclass/8.5.8-2
Severity: serious
Tags: sid bookworm
User: debian...@lists.debian.org
Usertags: breaks needs-update
Dear maintainer(s),
With a recent upload of python-typing-inspect the autopkgtest of
python-marshmallow-dataclass fails in testing when that autopkgtest is
run with the binary packages of python-typing-inspect from unstable. It
passes when run with only packages from testing. In tabular form:
passfail
python-typing-inspectfrom testing0.8.0-1
python-marshmallow-dataclass from testing8.5.8-2
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
python-typing-inspect to testing [1]. Due to the nature of this issue, I
filed this bug report against both packages. Can you please investigate
the situation and reassign the bug to the right package?
More information about this bug and the reason for filing it can be found on
https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation
Paul
[1] https://qa.debian.org/excuses.php?package=python-typing-inspect
https://ci.debian.net/data/autopkgtest/testing/amd64/p/python-marshmallow-dataclass/25831906/log.gz
=== FAILURES
===
___ TestClassSchema.test_validator_stacking
class_or_instance = .new_type at 0x7f0b19be1990>
def fields(class_or_instance):
"""Return a tuple describing the fields of this dataclass.
Accepts a dataclass or an instance of one. Tuple elements
are of
type Field.
"""
# Might it be worth caching this, per class?
try:
fields = getattr(class_or_instance, _FIELDS)
E AttributeError: 'function' object has no attribute
'__dataclass_fields__'
/usr/lib/python3.10/dataclasses.py:1197: AttributeError
During handling of the above exception, another exception occurred:
clazz = .new_type at 0x7f0b19be1990>
base_schema = None
clazz_frame = '/tmp/autopkgtest-lxc.c9zyolii/downtmp/autopkgtest_tmp/tests/test_class_schema.py',
line 319, code test_validator_stacking>
@lru_cache(maxsize=MAX_CLASS_SCHEMA_CACHE_SIZE)
def _internal_class_schema(
clazz: type,
base_schema: Optional[Type[marshmallow.Schema]] = None,
clazz_frame: types.FrameType = None,
) -> Type[marshmallow.Schema]:
_RECURSION_GUARD.seen_classes[clazz] = clazz.__name__
try:
# noinspection PyDataclass
fields: Tuple[dataclasses.Field, ...] = dataclasses.fields(clazz)
/usr/lib/python3/dist-packages/marshmallow_dataclass/__init__.py:370: _
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
_ _ _
class_or_instance = .new_type at 0x7f0b19be1990>
def fields(class_or_instance):
"""Return a tuple describing the fields of this dataclass.
Accepts a dataclass or an instance of one. Tuple elements
are of
type Field.
"""
# Might it be worth caching this, per class?
try:
fields = getattr(class_or_instance, _FIELDS)
except AttributeError:
raise TypeError('must be called with a dataclass type or instance')
E TypeError: must be called with a dataclass type or instance
/usr/lib/python3.10/dataclasses.py:1199: TypeError
During handling of the above exception, another exception occurred:
clazz = .new_type at 0x7f0b19be1990>
base_schema = None
clazz_frame = '/tmp/autopkgtest-lxc.c9zyolii/downtmp/autopkgtest_tmp/tests/test_class_schema.py',
line 319, code test_validator_stacking>
@lru_cache(maxsize=MAX_CLASS_SCHEMA_CACHE_SIZE)
def _internal_class_schema(
clazz: type,
base_schema: Optional[Type[marshmallow.Schema]] = None,
clazz_frame: types.FrameType = None,
) -> Type[marshmallow.Schema]:
_RECURSION_GUARD.seen_classes[clazz] = clazz.__name__
try:
# noinspection PyDataclass
fields: Tuple[dataclasses.Field, ...] =
dataclasses.fields(clazz)
except TypeError: # Not a dataclass
try:
warnings.warn(
"** WARNING ** "
f"marshmallow_dataclass was called on the class
{clazz}, which is not a dataclass. "
"It is going to try and convert the class into a
dataclass, which may have "
"undesirable side effects. To avoid this message,
make sure all your classes and "
"all the classes of their fields are either
explicitly supported by "
"marshmallow_dataclass, or define the schema
explicitly using "
"field(metadata=dict(marshmallow
Processed: your mail
Processing commands for cont...@bugs.debian.org: > tags 1017499 + fixed-upstream Bug #1017499 [src:mesa] mesa: Updates to 22.2 RCs cause artifacts on nouveau and blank screen on VirtIO Added tag(s) fixed-upstream. > End of message, stopping processing here. Please contact me if you need assistance. -- 1017499: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1017499 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: python-typing-inspect breaks python-marshmallow-dataclass autopkgtest: TypeError: CustomTypeNoneValidator is not a dataclass
Processing control commands: > found -1 python-typing-inspect/0.8.0-1 Bug #1019391 [src:python-typing-inspect, src:python-marshmallow-dataclass] python-typing-inspect breaks python-marshmallow-dataclass autopkgtest: TypeError: CustomTypeNoneValidator is not a dataclass Marked as found in versions python-typing-inspect/0.8.0-1. > found -1 python-marshmallow-dataclass/8.5.8-2 Bug #1019391 [src:python-typing-inspect, src:python-marshmallow-dataclass] python-typing-inspect breaks python-marshmallow-dataclass autopkgtest: TypeError: CustomTypeNoneValidator is not a dataclass Marked as found in versions python-marshmallow-dataclass/8.5.8-2. -- 1019391: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1019391 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1019390: o2: autopkgtest regression on i386 and s390x: Assertion `arg->v.vf[i] == 123.456F + i' failed.
Source: o2 Version: 1.1~ds-1 Severity: serious User: debian...@lists.debian.org Usertags: regression Dear maintainer(s), With a recent upload of o2 the autopkgtest of o2 fails in testing on i386 and s390x when that autopkgtest is run with the binary packages of o2 from unstable. It passes when run with only packages from testing. In tabular form: passfail o2 from testing1.1~ds-1 all others from testingfrom testing I copied some of the output on i386 at the bottom of this report. Currently this regression is blocking the migration to testing [1]. Can you please investigate the situation and fix it? More information about this bug and the reason for filing it can be found on https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation Paul [1] https://qa.debian.org/excuses.php?package=o2 https://ci.debian.net/data/autopkgtest/testing/i386/o/o2/24929151/log.gz make: Entering directory '/tmp/autopkgtest-lxc.xo3rn8r3/downtmp/build.74d/src/debian/tests' ./arraytest DONE sending [3456] DONE sending [] DONE sending [123, 234] DONE sending [xixdx] messages DONE sending 456,[456,12345][1234.56,1234.567,2345.678],1234.567 arraytest: ../../test/arraytest.c:502: service_ifvxif: Assertion `arg->v.vf[i] == 123.456F + i' failed. make: *** [Makefile:64: arraytest.test] Aborted make: Leaving directory '/tmp/autopkgtest-lxc.xo3rn8r3/downtmp/build.74d/src/debian/tests' autopkgtest [19:16:11]: test simple_run OpenPGP_signature Description: OpenPGP digital signature
Bug#1017232: marked as done (gcc-11-cross: FTBFS: unsatisfiable build-dependencies: libc6-dev-amd64-cross (= 2.33-1cross1), libc6-dev-amd64-cross (= 2.33-1cross1), libc6-dev-amd64-cross (>= 2.32))
Your message dated Thu, 8 Sep 2022 15:40:53 +0200 with message-id and subject line buildable again has caused the Debian Bug report #1017232, regarding gcc-11-cross: FTBFS: unsatisfiable build-dependencies: libc6-dev-amd64-cross (= 2.33-1cross1), libc6-dev-amd64-cross (= 2.33-1cross1), libc6-dev-amd64-cross (>= 2.32) 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.) -- 1017232: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1017232 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: gcc-11-cross Version: 14 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20220813 ftbfs-bookworm 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: gcc-11-source (>= 11.3.0-3~), gcc-11-base (>= > 11.3.0-3~), binutils-multiarch (>= 2.37-5), autoconf2.69, bison (>= 1:2.3), > chrpath, debhelper (>= 9), dpkg-dev (>= 1.14.15), flex, gawk, gettext, gperf > (>= 3.0.1), lib32gcc1-amd64-cross, libx32gcc1-amd64-cross, > lib64gcc1-i386-cross, libx32gcc1-i386-cross, lib32gcc1-s390x-cross, > binutils-x86-64-linux-gnu (>= 2.37-5), binutils-s390x-linux-gnu (>= 2.37-5), > binutils-powerpc64le-linux-gnu (>= 2.37-5), binutils-aarch64-linux-gnu (>= > 2.37-5), binutils-arm-linux-gnueabihf (>= 2.37-5), binutils-arm-linux-gnueabi > (>= 2.37-5), binutils-i686-linux-gnu (>= 2.37-5), libc6-dev-amd64-cross (>= > 2.32), libc6-dev-s390x-cross (>= 2.32), libc6-dev-ppc64el-cross (>= 2.32), > libc6-dev-arm64-cross (>= 2.32), libc6-dev-armhf-cross (>= 2.32), > libc6-dev-armel-cross (>= 2.32), libc6-dev-i386-cross (>= 2.32), > libc6-dev-i386-amd64-cross, libc6-dev-x32-amd64-cross, > libc6-dev-amd64-i386-cross, libc6-dev-x32-i386-cross, > libc6-dev-s390-s390x-cross, linux-libc-dev-amd64-cross, > linux-libc-dev-s390x-cross, linux-libc-dev-ppc64el-cross, > linux-libc-dev-arm64-cross, linux-libc-dev-armhf-cross, > linux-libc-dev-armel-cross, linux-libc-dev-i386-cross, libisl-dev (>= > 0.22.1-1~), libmpc-dev, libmpfr-dev (>= 2.3.0), libtool, lsb-release, m4, > make (>= 3.81), dwz, pkg-config, libgc-dev, patchutils, procps, quilt, > coreutils (>= 2.26) | realpath (>= 1.9.12), sharutils, texinfo (>= 4.3), > g++-11, gccgo-11, gdc-11, gm2-11, gnat-11, xz-utils, zlib1g-dev, libzstd-dev, > python3, time, build-essential, fakeroot > Merged Build-Conflicts: gcc-multilib, libc6-i386, libc6-x32 > Filtered Build-Depends: gcc-11-source (>= 11.3.0-3~), gcc-11-base (>= > 11.3.0-3~), binutils-multiarch (>= 2.37-5), autoconf2.69, bison (>= 1:2.3), > chrpath, debhelper (>= 9), dpkg-dev (>= 1.14.15), flex, gawk, gettext, gperf > (>= 3.0.1), lib32gcc1-amd64-cross, libx32gcc1-amd64-cross, > lib64gcc1-i386-cross, libx32gcc1-i386-cross, lib32gcc1-s390x-cross, > binutils-x86-64-linux-gnu (>= 2.37-5), binutils-s390x-linux-gnu (>= 2.37-5), > binutils-powerpc64le-linux-gnu (>= 2.37-5), binutils-aarch64-linux-gnu (>= > 2.37-5), binutils-arm-linux-gnueabihf (>= 2.37-5), binutils-arm-linux-gnueabi > (>= 2.37-5), binutils-i686-linux-gnu (>= 2.37-5), libc6-dev-amd64-cross (>= > 2.32), libc6-dev-s390x-cross (>= 2.32), libc6-dev-ppc64el-cross (>= 2.32), > libc6-dev-arm64-cross (>= 2.32), libc6-dev-armhf-cross (>= 2.32), > libc6-dev-armel-cross (>= 2.32), libc6-dev-i386-cross (>= 2.32), > libc6-dev-i386-amd64-cross, libc6-dev-x32-amd64-cross, > libc6-dev-amd64-i386-cross, libc6-dev-x32-i386-cross, > libc6-dev-s390-s390x-cross, linux-libc-dev-amd64-cross, > linux-libc-dev-s390x-cross, linux-libc-dev-ppc64el-cross, > linux-libc-dev-arm64-cross, linux-libc-dev-armhf-cross, > linux-libc-dev-armel-cross, linux-libc-dev-i386-cross, libisl-dev (>= > 0.22.1-1~), libmpc-dev, libmpfr-dev (>= 2.3.0), libtool, lsb-release, m4, > make (>= 3.81), dwz, pkg-config, libgc-dev, patchutils, procps, quilt, > coreutils (>= 2.26), sharutils, texinfo (>= 4.3), g++-11, gccgo-11, gdc-11, > gm2-11, gnat-11, xz-utils, zlib1g-dev, libzstd-dev, python3, time, > build-essential, fakeroot > Filtered Build-Conflicts: gcc-multilib, libc6-i386, libc6-x32 > 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 co
Bug#1017192: marked as done (gcc-10-cross: FTBFS: unsatisfiable build-dependencies: libc6-dev-amd64-cross (= 2.33-1cross1), libc6-dev-amd64-cross (= 2.33-1cross1), libc6-dev-amd64-cross (>= 2.31))
Your message dated Thu, 8 Sep 2022 15:40:53 +0200 with message-id and subject line buildable again has caused the Debian Bug report #1017192, regarding gcc-10-cross: FTBFS: unsatisfiable build-dependencies: libc6-dev-amd64-cross (= 2.33-1cross1), libc6-dev-amd64-cross (= 2.33-1cross1), libc6-dev-amd64-cross (>= 2.31) 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.) -- 1017192: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1017192 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: gcc-10-cross Version: 18 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20220813 ftbfs-bookworm 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: gcc-10-source (>= 10.3.0-8~), gcc-10-base (>= > 10.3.0-8~), binutils-multiarch (>= 2.35.2-2), autoconf, bison (>= 1:2.3), > chrpath, debhelper (>= 9), dpkg-dev (>= 1.14.15), flex, gawk, gettext, gperf > (>= 3.0.1), binutils-x86-64-linux-gnu (>= 2.35.2-2), binutils-s390x-linux-gnu > (>= 2.35.2-2), binutils-powerpc64le-linux-gnu (>= 2.35.2-2), > binutils-aarch64-linux-gnu (>= 2.35.2-2), binutils-arm-linux-gnueabihf (>= > 2.35.2-2), binutils-arm-linux-gnueabi (>= 2.35.2-2), binutils-i686-linux-gnu > (>= 2.35.2-2), libc6-dev-amd64-cross (>= 2.31), libc6-dev-s390x-cross (>= > 2.31), libc6-dev-ppc64el-cross (>= 2.31), libc6-dev-arm64-cross (>= 2.31), > libc6-dev-armhf-cross (>= 2.31), libc6-dev-armel-cross (>= 2.31), > libc6-dev-i386-cross (>= 2.31), libc6-dev-i386-amd64-cross, > libc6-dev-x32-amd64-cross, libc6-dev-amd64-i386-cross, > libc6-dev-x32-i386-cross, libc6-dev-s390-s390x-cross, > linux-libc-dev-amd64-cross, linux-libc-dev-s390x-cross, > linux-libc-dev-ppc64el-cross, linux-libc-dev-arm64-cross, > linux-libc-dev-armhf-cross, linux-libc-dev-armel-cross, > linux-libc-dev-i386-cross, libisl-dev (>= 0.22.1-1~), libmpc-dev, libmpfr-dev > (>= 2.3.0), libtool, lsb-release, m4, make (>= 3.81), dwz, pkg-config, > libgc-dev, patchutils, procps, quilt, coreutils (>= 2.26) | realpath (>= > 1.9.12), sharutils, texinfo (>= 4.3), g++-10, gccgo-10, gdc-10, gm2-10, > python3, gnat-10, xz-utils, zlib1g-dev, libzstd-dev, time, build-essential, > fakeroot > Merged Build-Conflicts: gcc-multilib, libc6-i386, libc6-x32 > Filtered Build-Depends: gcc-10-source (>= 10.3.0-8~), gcc-10-base (>= > 10.3.0-8~), binutils-multiarch (>= 2.35.2-2), autoconf, bison (>= 1:2.3), > chrpath, debhelper (>= 9), dpkg-dev (>= 1.14.15), flex, gawk, gettext, gperf > (>= 3.0.1), binutils-x86-64-linux-gnu (>= 2.35.2-2), binutils-s390x-linux-gnu > (>= 2.35.2-2), binutils-powerpc64le-linux-gnu (>= 2.35.2-2), > binutils-aarch64-linux-gnu (>= 2.35.2-2), binutils-arm-linux-gnueabihf (>= > 2.35.2-2), binutils-arm-linux-gnueabi (>= 2.35.2-2), binutils-i686-linux-gnu > (>= 2.35.2-2), libc6-dev-amd64-cross (>= 2.31), libc6-dev-s390x-cross (>= > 2.31), libc6-dev-ppc64el-cross (>= 2.31), libc6-dev-arm64-cross (>= 2.31), > libc6-dev-armhf-cross (>= 2.31), libc6-dev-armel-cross (>= 2.31), > libc6-dev-i386-cross (>= 2.31), libc6-dev-i386-amd64-cross, > libc6-dev-x32-amd64-cross, libc6-dev-amd64-i386-cross, > libc6-dev-x32-i386-cross, libc6-dev-s390-s390x-cross, > linux-libc-dev-amd64-cross, linux-libc-dev-s390x-cross, > linux-libc-dev-ppc64el-cross, linux-libc-dev-arm64-cross, > linux-libc-dev-armhf-cross, linux-libc-dev-armel-cross, > linux-libc-dev-i386-cross, libisl-dev (>= 0.22.1-1~), libmpc-dev, libmpfr-dev > (>= 2.3.0), libtool, lsb-release, m4, make (>= 3.81), dwz, pkg-config, > libgc-dev, patchutils, procps, quilt, coreutils (>= 2.26), sharutils, texinfo > (>= 4.3), g++-10, gccgo-10, gdc-10, gm2-10, python3, gnat-10, xz-utils, > zlib1g-dev, libzstd-dev, time, build-essential, fakeroot > Filtered Build-Conflicts: gcc-multilib, libc6-i386, libc6-x32 > 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 [963 B] > Ign:3 copy:/<>/apt_archive ./ Release.gpg > Get:4 copy:/<>/apt_archive ./ Sources [947 B] > Get:5 copy:/<>/apt_archive ./ Packages [884 B] > Fetched 2794 B in 0s (165 kB/s) >
Bug#1008326: marked as done (gcc-10-cross-ports: FTBFS: checking for suffix of executables... collect2: error: ld returned 1 exit status)
Your message dated Thu, 8 Sep 2022 15:40:53 +0200 with message-id and subject line buildable again has caused the Debian Bug report #1008326, regarding gcc-10-cross-ports: FTBFS: checking for suffix of executables... collect2: error: ld returned 1 exit status 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.) -- 1008326: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1008326 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: gcc-10-cross-ports Version: 19 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20220326 ftbfs-bookworm Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > /<>/gcc/build/./gcc/xgcc -B/<>/gcc/build/./gcc/ > -B/usr/x86_64-linux-gnux32/bin/ -B/usr/x86_64-linux-gnux32/lib/ -isystem > /usr/x86_64-linux-gnux32/include -isystem > /usr/x86_64-linux-gnux32/sys-include -isystem > /<>/gcc/build/sys-include-c -g -O2 -fpic -W -Wall -gnatpg > -nostdinc -gnatn -fpic memtrack.adb -o memtrack.o > checking dirent.h usability... Running configure in multilib subdir 32 > pwd: /<>/gcc/build/x86_64-linux-gnux32 > yes > checking dirent.h presence... yes > checking for dirent.h... yes > checking sys/statvfs.h usability... yes > checking sys/statvfs.h presence... yes > checking for sys/statvfs.h... yes > checking utime.h usability... yes > checking utime.h presence... yes > checking for utime.h... yes > checking whether to build Filesystem TS support... yes > checking for struct dirent.d_type... make[9]: Leaving directory > '/<>/gcc/build/gcc/ada/rts' > rm -f rts/libgna*.so > cd rts; `echo "/<>/gcc/build/./gcc/xgcc > -B/<>/gcc/build/./gcc/ -B/usr/x86_64-linux-gnux32/bin/ > -B/usr/x86_64-linux-gnux32/lib/ -isystem /usr/x86_64-linux-gnux32/include > -isystem /usr/x86_64-linux-gnux32/sys-include -isystem > /<>/gcc/build/sys-include " \ > | sed -e 's,\./xgcc,../../xgcc,' -e 's,-B\./,-B../../,'` > -shared -g -O2 \ > -fpic \ > -o libgnat-10.so \ > -Wl,-z,relro -Wl,--no-allow-shlib-undefined > -Wl,--no-copy-dt-needed-entries -Wl,--no-undefined \ > a-assert.o a-btgbso.o a-calari.o a-calcon.o a-caldel.o a-calend.o > a-calfor.o a-catizo.o a-cbdlli.o a-cbhama.o a-cbhase.o a-cbmutr.o a-cborma.o > a-cborse.o a-cbprqu.o a-cbsyqu.o a-cdlili.o a-cfdlli.o a-cfhama.o a-cfhase.o > a-cfinve.o a-cforma.o a-cforse.o a-cgaaso.o a-cgarso.o a-cgcaso.o a-chacon.o > a-chahan.o a-charac.o a-chlat1.o a-chlat9.o a-chtgbk.o a-chtgbo.o a-chtgke.o > a-chtgop.o a-chzla1.o a-chzla9.o a-cidlli.o a-cihama.o a-cihase.o a-cimutr.o > a-ciorma.o a-ciormu.o a-ciorse.o a-clrefi.o a-coboho.o a-cobove.o a-cofove.o > a-cofuba.o a-cofuma.o a-cofuse.o a-cofuve.o a-cogeso.o a-cohama.o a-cohase.o > a-cohata.o a-coinho.o a-coinve.o a-colien.o a-colire.o a-comlin.o a-comutr.o > a-conhel.o a-contai.o a-convec.o a-coorma.o a-coormu.o a-coorse.o a-coprnu.o > a-coteio.o a-crbltr.o a-crbtgk.o a-crbtgo.o a-crdlli.o a-csquin.o a-cuprqu.o > a-cusyqu.o a-cwila1.o a-cwila9.o a-decima.o a-dhfina.o a-diocst.o a-direct.o > a-direio.o a-dirval.o a-einuoc.o a-elchha.o a-envvar.o a-except.o a-exctra.o > a-finali.o a-flteio.o a-fwteio.o a-fzteio.o a-inteio.o a-ioexce.o a-iteint.o > a-iwteio.o a-izteio.o a-lcteio.o a-lfteio.o a-lfwtio.o a-lfztio.o a-liteio.o > a-liwtio.o a-liztio.o a-llctio.o a-llftio.o a-llfwti.o a-llfzti.o a-llitio.o > a-lliwti.o a-llizti.o a-locale.o a-nbnbin.o a-nbnbre.o a-ncelfu.o a-ngcefu.o > a-ngcoar.o a-ngcoty.o a-ngelfu.o a-ngrear.o a-nlcefu.o a-nlcoar.o a-nlcoty.o > a-nlelfu.o a-nllcar.o a-nllcef.o a-nllcty.o a-nllefu.o a-nllrar.o a-nlrear.o > a-nscefu.o a-nscoty.o a-nselfu.o a-nubinu.o a-nucoar.o a-nucoty.o a-nudira.o > a-nuelfu.o a-nuflra.o a-numaux.o a-numeri.o a-nurear.o a-rbtgbk.o a-rbtgbo.o > a-rbtgso.o a-sbecin.o a-sbhcin.o a-sblcin.o a-scteio.o a-secain.o a-sequio.o > a-sfecin.o a-sfhcin.o a-sflcin.o a-sfteio.o a-sfwtio.o a-sfztio.o a-shcain.o > a-siocst.o a-siteio.o a-siwtio.o a-siztio.o a-slcain.o a-ssicst.o a-ssitio.o > a-ssiwti.o a-ssizti.o a-stboha.o a-stfiha.o a-stmaco.o a-storio.o a-strbou.o > a-stream.o a-strfix.o a-strhas.o a-string.o a-strmap.o a-strsea.o a-strsup.o > a-strunb.o a-ststio.o a-stunau.o a-stunha.o a-stuten.o a-stwibo.o a-stwifi.o > a-stwiha.o a-stwima.o a-stwise.o a-stwisu.o a-stwiun.o a-stzbou.o a-stzfix.o > a-stzhas.o a-stzmap.o a-stzsea.o a-stzsup.o a-stzunb.o a-suecin.o a-suenco.o > a-suenst.o a-suewst.o a-suezst.o a-suhcin.o a-sulcin.o a-suteio.o a-swbwha.o > a-swfwha.o a-swmwco.o a-
Bug#1005473: marked as done (gcc-11-cross-ports: FTBFS: s-tsmona.adb:160: undefined reference to `dladdr')
Your message dated Thu, 8 Sep 2022 15:40:53 +0200 with message-id and subject line buildable again has caused the Debian Bug report #1005473, regarding gcc-11-cross-ports: FTBFS: s-tsmona.adb:160: undefined reference to `dladdr' 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.) -- 1005473: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1005473 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: gcc-11-cross-ports Version: 8 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20220212 ftbfs-bookworm Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > /bin/bash ./libtool --tag=CC --mode=compile > /<>/gcc/build/./gcc/xgcc -B/<>/gcc/build/./gcc/ > -B/usr/x86_64-linux-gnux32/bin/ -B/usr/x86_64-linux-gnux32/lib/ -isystem > /usr/x86_64-linux-gnux32/include -isystem > /usr/x86_64-linux-gnux32/sys-include -isystem > /<>/gcc/build/sys-include-DHAVE_CONFIG_H -I. > -I../../../src/libgfortran -iquote../../../src/libgfortran/io > -I../../../src/libgfortran/../gcc -I../../../src/libgfortran/../gcc/config > -I../../../src/libgfortran/../libquadmath -I../.././gcc > -I../../../src/libgfortran/../libgcc -I../libgcc > -I../../../src/libgfortran/../libbacktrace -I../libbacktrace > -I../libbacktrace -std=gnu11 -Wall -Wstrict-prototypes -Wmissing-prototypes > -Wold-style-definition -Wextra -Wwrite-strings > -Werror=implicit-function-declaration -Werror=vla -fcf-protection -mshstk > -fcx-fortran-rules -ffunction-sections -fdata-sections -g -O2 -MT > iany_i4.lo -MD -MP -MF .deps/iany_i4.Tpo -c -o iany_i4.lo `test -f > '../../../src/libgfortran/generated/iany_i4.c' || echo > '../../../src/libgfortran/'`../../../src/libgfortran/generated/iany_i4.c > libtool: compile: /<>/gcc/build/./gcc/xgcc > -B/<>/gcc/build/./gcc/ -B/usr/x86_64-linux-gnux32/bin/ > -B/usr/x86_64-linux-gnux32/lib/ -isystem /usr/x86_64-linux-gnux32/include > -isystem /usr/x86_64-linux-gnux32/sys-include -isystem > /<>/gcc/build/sys-include -DHAVE_CONFIG_H -I. > -I../../../src/libgfortran -iquote../../../src/libgfortran/io > -I../../../src/libgfortran/../gcc -I../../../src/libgfortran/../gcc/config > -I../../../src/libgfortran/../libquadmath -I../.././gcc > -I../../../src/libgfortran/../libgcc -I../libgcc > -I../../../src/libgfortran/../libbacktrace -I../libbacktrace > -I../libbacktrace -std=gnu11 -Wall -Wstrict-prototypes -Wmissing-prototypes > -Wold-style-definition -Wextra -Wwrite-strings > -Werror=implicit-function-declaration -Werror=vla -fcf-protection -mshstk > -fcx-fortran-rules -ffunction-sections -fdata-sections -g -O2 -MT iany_i4.lo > -MD -MP -MF .deps/iany_i4.Tpo -c ../../../src/libgfortran/generated/iany_i4.c > -fPIC -DPIC -o .libs/iany_i4.o > /usr/x86_64-linux-gnux32/bin/ld: s-trasym.o: in function > `system__traceback__symbolic__module_name__getXnn': > /<>/gcc/build/gcc/ada/rts/s-tsmona.adb:160: undefined reference > to `dladdr' > collect2: error: ld returned 1 exit status The full build log is available from: http://qa-logs.debian.net/2022/02/12/gcc-11-cross-ports_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 mine so that we can identify if something relevant changed in the meantime. --- End Message --- --- Begin Message --- these are buildable again with recent c-t-b updates.--- End Message ---
Bug#1000927: marked as done (creduce: Please upgrade to llvm-toolchain-14)
Your message dated Thu, 8 Sep 2022 15:20:23 +0200 with message-id and subject line fixed in unstable has caused the Debian Bug report #1000927, regarding creduce: Please upgrade to llvm-toolchain-14 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.) -- 1000927: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1000927 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: creduce Severity: important Dear Maintainer, As part of the effort to limit the number of llvm packages in the archive, it would be great if you could upgrade to -13 (or -12). Bookworm won't ship with llvm-toolchain-11 llvm-defaults is now pointing to -13. Thanks, Sylvestre --- End Message --- --- Begin Message --- fixed in unstable, now built using LLVM 13.--- End Message ---
Bug#1015995: gpgme1.0 FTBFS with 3.10 as only supported Python3 version
Hello, indeed! thanks for fixing it up! G. Il martedì 6 settembre 2022 21:18:09 CEST, Paul Gevers ha scritto: Hi Alexandre, On Mon, 25 Jul 2022 10:03:04 +0200 Gianfranco Costamagna wrote: > Hello, looks like Ubuntu already has a patch for this: > http://launchpadlibrarian.net/594282639/gpgme1.0_1.16.0-1.2ubuntu3_1.16.0-1.2ubuntu4.diff.gz I was about to upload an NMU gpgme with your patch applied, but it looks wrong to me. If I understand the patch correctly (make isn't my strongest point), it will just run the test with the last PYTHON in PYTHONS. Why was the test not put inside the do-done block? --- a/lang/python/tests/Makefile.am +++ b/lang/python/tests/Makefile.am @@ -70,7 +70,8 @@ check: xcheck .PHONY: xcheck xcheck: all - $(TESTS_ENVIRONMENT) $(PYTHON) $(srcdir)/run-tests.py \ + for PYTHON in $(PYTHONS); do true; done; \ + $(TESTS_ENVIRONMENT) $$PYTHON $(srcdir)/run-tests.py \ --interpreters="$(PYTHONS)" --srcdir=$(srcdir) $(TESTFLAGS) \ $(XTESTS) Paul
Processed: Bug#1016227 marked as pending in openbabel
Processing control commands:
> tag -1 pending
Bug #1016227 {Done: Andrius Merkys } [src:openbabel]
openbabel: FTBFS: obutil.h:65:14: error: ‘clock’ was not declared in this scope
Added tag(s) pending.
--
1016227: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1016227
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#1016227: marked as pending in openbabel
Control: tag -1 pending Hello, Bug #1016227 in openbabel 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/debichem-team/openbabel/-/commit/b0d93c983566d19977c36ab28368b7b2fe4b7129 Include in obutil.h (Closes: #1016227) (this message was generated automatically) -- Greetings https://bugs.debian.org/1016227
Bug#1016227: marked as done (openbabel: FTBFS: obutil.h:65:14: error: ‘clock’ was not declared in this scope)
Your message dated Thu, 08 Sep 2022 12:56:16 + with message-id and subject line Bug#1016227: fixed in openbabel 3.1.1+dfsg-7 has caused the Debian Bug report #1016227, regarding openbabel: FTBFS: obutil.h:65:14: error: ‘clock’ 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.) -- 1016227: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1016227 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: openbabel Version: 3.1.1+dfsg-6 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20220728 ftbfs-bookworm Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > cd /<>/builddir/src/formats && /usr/bin/c++ -DBUILD_LINK_AS_DLL > -DHAVE_EIGEN -DHAVE_EIGEN3 -DHAVE_LIBZ -DHAVE_RADPIJSON -DHAVE_SHARED_POINTER > -DHAVE_WXWIDGETS -DUSING_DYNAMIC_LIBS -DWXUSINGDLL -D_FILE_OFFSET_BITS=64 > -D__WXGTK__ -Dasciiformat_EXPORTS -I/<>/builddir/include > -I/<>/data -I/<>/include -I/usr/include/eigen3 > -I/usr/include/cairo -I/usr/include/libxml2 -isystem > /usr/lib/x86_64-linux-gnu/wx/include/gtk3-unicode-3.0 -isystem > /usr/include/wx-3.0 -g -O2 -ffile-prefix-map=/<>=. > -fstack-protector-strong -Wformat -Werror=format-security -std=gnu++98 > -Wdate-time -D_FORTIFY_SOURCE=2 -Wdate-time -D_FORTIFY_SOURCE=2 -pthread > -fopenmp -fPIC -std=gnu++11 -MD -MT > src/formats/CMakeFiles/asciiformat.dir/__/depict/asciipainter.cpp.o -MF > CMakeFiles/asciiformat.dir/__/depict/asciipainter.cpp.o.d -o > CMakeFiles/asciiformat.dir/__/depict/asciipainter.cpp.o -c > /<>/src/depict/asciipainter.cpp > In file included from /<>/src/depict/asciipainter.cpp:18: > /<>/include/openbabel/obutil.h: In member function ‘void > OpenBabel::OBStopwatch::Start()’: > /<>/include/openbabel/obutil.h:65:14: error: ‘clock’ was not > declared in this scope >65 | start= clock(); > | ^ > /<>/include/openbabel/obutil.h:40:1: note: ‘clock’ is defined in > header ‘’; did you forget to ‘#include ’? >39 | #include > +++ |+#include >40 | > /<>/include/openbabel/obutil.h: In member function ‘double > OpenBabel::OBStopwatch::Lap()’: > /<>/include/openbabel/obutil.h:70:13: error: ‘clock’ was not > declared in this scope >70 | stop= clock(); > | ^ > /<>/include/openbabel/obutil.h:70:13: note: ‘clock’ is defined > in header ‘’; did you forget to ‘#include ’? > /<>/include/openbabel/obutil.h:71:40: error: ‘CLOCKS_PER_SEC’ > was not declared in this scope >71 | return((stop - start) / (double) CLOCKS_PER_SEC); > |^~ > /<>/include/openbabel/obutil.h:71:40: note: the macro > ‘CLOCKS_PER_SEC’ had not yet been defined > In file included from /usr/include/time.h:33, > from /usr/include/pthread.h:23, > from > /usr/include/x86_64-linux-gnu/c++/12/bits/gthr-default.h:35, > from /usr/include/x86_64-linux-gnu/c++/12/bits/gthr.h:148, > from /usr/include/c++/12/ext/atomicity.h:35, > from /usr/include/c++/12/bits/ios_base.h:39, > from /usr/include/c++/12/ios:42, > from /usr/include/c++/12/istream:38, > from /usr/include/c++/12/sstream:38, > from /<>/include/openbabel/depict/painter.h:25, > from > /<>/include/openbabel/depict/asciipainter.h:21, > from /<>/src/depict/asciipainter.cpp:19: > /usr/include/x86_64-linux-gnu/bits/time.h:34: note: it was later defined here >34 | #define CLOCKS_PER_SEC ((__clock_t) 100) > | > In file included from /<>/include/openbabel/op.h:25, > from /<>/src/ops/gen2D.cpp:22: > /<>/include/openbabel/plugin.h:41:42: warning: ‘template _Arg1, class _Arg2, class _Result> struct std::binary_function’ is deprecated > [-Wdeprecated-declarations] >41 | struct OBERROR CharPtrLess : public std::binary_function char*,const char*, bool> > | ^~~ > In file included from /usr/include/c++/12/string:48, > from /usr/include/c++/12/bits/locale_classes.h:40, > from /usr/include/c++/12/bits/ios_base.h:41, > from /usr/include/c++/12/ios:42, > from /usr/include/c++/12/ostream:38, > from /usr/include/c++/12/iostream:39, > from /<>/src/ops/gen2D.cpp:21: > /usr/include/c++/12/bits/st
Bug#1019388: apt-clone: Fails to run - no /usr/bin/dpkg-repack found
Package: apt-clone
Version: 0.4.3+nmu1
Severity: grave
Justification: renders package unusable
X-Debbugs-Cc: baronr...@gmail.com
Dear Maintainer,
Traceback (most recent call last):
File "/usr/bin/apt-clone", line 107, in
clone.save_state(args.source, args.destination,
File "/usr/lib/python3/dist-packages/apt_clone.py", line 158, in save_state
self._dpkg_repack(tar)
File "/usr/lib/python3/dist-packages/apt_clone.py", line 300, in _dpkg_repack
self.commands.repack_deb(pkgname, tdir)
File "/usr/lib/python3/dist-packages/apt_clone.py", line 64, in repack_deb
raise IOError("no '%s' found" % self.dpkg_repack)
OSError: no '/usr/bin/dpkg-repack' found
E: Problem executing scripts DPkg::Post-Invoke
Did dpkg-repack disappear with some recent update?
-- System Information:
Debian Release: bookworm/sid
APT prefers unstable
APT policy: (1000, 'unstable'), (500, 'unstable-debug'), (500,
'testing-debug'), (500, 'stable-updates'), (500, 'stable-security'), (500,
'proposed-updates'), (500, 'stable'), (100, 'testing'), (1,
'experimental-debug'), (1, 'experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 5.18.0-4-amd64 (SMP w/4 CPU threads; PREEMPT)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages apt-clone depends on:
ii lsb-release 11.2
ii python3 3.10.6-1
ii python3-apt 2.3.0+b2
Versions of packages apt-clone recommends:
pn dpkg-repack
apt-clone suggests no packages.
-- no debconf information
Bug#1019345: marked as done (flake8-class-newline: autopkgtest failure)
Your message dated Thu, 08 Sep 2022 10:03:50 + with message-id and subject line Bug#1019345: fixed in flake8-class-newline 1.6.0-3 has caused the Debian Bug report #1019345, regarding flake8-class-newline: autopkgtest failure to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1019345: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1019345 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: flake8-class-newline Version: 1.6.0-2 Severity: serious Hi, the test fails with the latest flake8 version in sid (5.0.4-1). The output of flake8 --version with -class-newline installed is now: $ flake8 --version 5.0.4 (flake8-class-newline: 1.6.0, mccabe: 0.6.1, pycodestyle: 2.9.1, pyflakes: 2.5.0) CPython 3.10.6 on Linux While the autopkgtest expects it to include the string "new_line_checker". https://ci.debian.net/data/autopkgtest/testing/amd64/f/flake8-class-newline/25797651/log.gz [...] Processing triggers for libc-bin (2.34-7) ... (Reading database ... 14305 files and directories currently installed.) Removing autopkgtest-satdep (0) ... autopkgtest [20:13:42]: test install: [--- autopkgtest [20:13:43]: test install: ---] autopkgtest [20:13:43]: test install: - - - - - - - - - - results - - - - - - - - - - install FAIL non-zero exit status 1 autopkgtest [20:13:43]: summary install FAIL non-zero exit status 1 --- End Message --- --- Begin Message --- Source: flake8-class-newline Source-Version: 1.6.0-3 Done: Emanuele Rocca We believe that the bug you reported is fixed in the latest version of flake8-class-newline, 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 1019...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Emanuele Rocca (supplier of updated flake8-class-newline package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Thu, 08 Sep 2022 10:29:10 +0200 Source: flake8-class-newline Architecture: source Version: 1.6.0-3 Distribution: unstable Urgency: medium Maintainer: Debian Python Team Changed-By: Emanuele Rocca Closes: 1019345 Changes: flake8-class-newline (1.6.0-3) unstable; urgency=medium . * Team upload. * Update 'install' autopkgtest to support the --version output of flake8 5.x, currently in sid. (Closes: #1019345) * Add 'functional' autopkgtest to ensure that CNL100 violations are actually getting caught. * Update Standards-Version to 4.6.1, no changes required. Checksums-Sha1: 91a825def5b5867b84c05f2184ea215defa9fad4 2204 flake8-class-newline_1.6.0-3.dsc ce08bc05012f7b438b536b2414370b7b2d29a3aa 2652 flake8-class-newline_1.6.0-3.debian.tar.xz a266cf76dbbe7cf2195784b64d45a3742d58f4d0 7049 flake8-class-newline_1.6.0-3_amd64.buildinfo Checksums-Sha256: ce4189858e88ea09cc07966af24cacfa0cd69a2b0d5eff9146c18169941b0b39 2204 flake8-class-newline_1.6.0-3.dsc ec946be21de9c6aec3f6efb54e06c85a98071409bf323b16356ff336f168b544 2652 flake8-class-newline_1.6.0-3.debian.tar.xz b88c025cf36125b49173e7b5aa5e18139a442099d62cd5c6687468c3e49b068a 7049 flake8-class-newline_1.6.0-3_amd64.buildinfo Files: 19c750db63f0988735172133b2db23d7 2204 python optional flake8-class-newline_1.6.0-3.dsc fc94f8fb7a6992fe6956661b89a63268 2652 python optional flake8-class-newline_1.6.0-3.debian.tar.xz eb66d8aa76a01a83a08703c65198ee23 7049 python optional flake8-class-newline_1.6.0-3_amd64.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEElUWWlhkoHBf/rFiR1QhaB1D9t6MFAmMZuJIACgkQ1QhaB1D9 t6N5pg//UCFUc9NrsFhUGIFihhJ9k5prD55G/QVnTYLoQrR7y7Qd1yDR29L+rC3o LAyPYYZ2n7xmWs06z6gMVWsF9TnV5OwFOeZ5Fvq7/4ifQz9h2GnQ9DR1ZxbYKxVC qQZM9XJJhNaat3duHrlXUKVtNE+0hqvtgo0kf/lraVzXJXJQCnvjR18oDkfjcaLu HStR5ztafDLEDkGhyZGKsw0BDxI32oWntXkuhEtyh5UFdeEo6/pde4SmASg/N9y6 h5bQzHfO6W7S0bT6cO5G/WXbwDBtLBgqvNe8P1/fUYh9FKEwMh8n/0PrwS/FacUt YMsNBQvWND7U/H5bvVMIN5sbA2BnIQZOEHUWuI4Ynf/h5EMYJfYmnhqPKiZGsyRn 8biq6OZv3nfeGjVTWC2u50W/ZRAYmOYjz6lgq62sRnCEJuElJhWqs/Fzz5C0V1WH 6B5a0cxHF1xXBnes9lEyFbeZc/bnlEm/s5GnTPnAtco/+8uu3nhgw1q3juFYpdGV LRw2k+3lkZWlvxDZndEzDmJLSL+fPSbFPy9FJTUQ4wtCMKCn4rF6KAfnvkaZfS6h 1CzmLvjlf/e4trVqwEWvEG
Bug#1017609: ruby-terser: Test fails with node-terser >= 5
On 07/09/2022 19:49, Mohd Bilal wrote: On 9/7/22 14:11, Yadd wrote: Can I push an NMU upload to unblock node-terser migration or can a Ruby-Team member push that ? Hi, Thanks for the patch :) . I've uploaded ruby-terser 1.1.12+dfsg-1 (the patch works with the latest version only) to unstable now. Hopefully this clears way for migration of node-terser. Thanks Looking at tracker.d.o, all seems OK now. Thanks a lot !
Bug#1019352: marked as done (python-pytest-flake8: FTBFS with flake8 5.0.4)
Your message dated Thu, 08 Sep 2022 09:04:34 + with message-id and subject line Bug#1019352: fixed in python-pytest-flake8 1.1.1-1 has caused the Debian Bug report #1019352, regarding python-pytest-flake8: FTBFS with flake8 5.0.4 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.) -- 1019352: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1019352 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: python-pytest-flake8 Version: 1.0.6-4 Severity: serious The package fails to build with the flake8 version currently in sid, namely 5.0.4-1. Multiple tests fail, partial output follows: [...] copying pytest_flake8.py -> /build/python-pytest-flake8-1.0.6/.pybuild/cpython3_3.10_python-pytest-flake8/build dh_auto_test -O--buildsystem=pybuild I: pybuild base:240: cd /build/python-pytest-flake8-1.0.6/.pybuild/cpython3_3.10_python-pytest-flake8/build; pyt hon3.10 -m pytest = test session starts == platform linux -- Python 3.10.6, pytest-7.1.2, pluggy-1.0.0+repack rootdir: /build/python-pytest-flake8-1.0.6, configfile: tox.ini plugins: flake8-1.0.6 collected 14 items pytest_flake8.py F [ 7%] test_flake8.py F...FF.xF [100%] LURES === _ FLAKE8-check _ pytest_flake8.py:122: in runtest found_errors = check_file( pytest_flake8.py:201: in check_file config_finder = config.ConfigFileFinder( E AttributeError: module 'flake8.options.config' has no attribute 'ConfigFileFinder' _ FLAKE8-check _ /usr/lib/python3/dist-packages/pluggy/_hooks.py:265: in __call__ return self._hookexec(self.name, self.get_hookimpls(), kwargs, firstresult) /usr/lib/python3/dist-packages/pluggy/_manager.py:80: in _hookexec [...] The autopkgtests also fail, see full output at: https://ci.debian.net/data/autopkgtest/testing/amd64/p/python-pytest-flake8/25797652/log.gz --- End Message --- --- Begin Message --- Source: python-pytest-flake8 Source-Version: 1.1.1-1 Done: Emanuele Rocca We believe that the bug you reported is fixed in the latest version of python-pytest-flake8, 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 1019...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Emanuele Rocca (supplier of updated python-pytest-flake8 package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Thu, 08 Sep 2022 10:42:17 +0200 Source: python-pytest-flake8 Architecture: source Version: 1.1.1-1 Distribution: unstable Urgency: medium Maintainer: Debian Python Team Changed-By: Emanuele Rocca Closes: 1019352 Changes: python-pytest-flake8 (1.1.1-1) unstable; urgency=medium . * Team upload. * New upstream release. * Add flake8-5.x-support.patch to support version 5 of flake8, currently in unstable. (Closes: #1019352) * Drop fix-flake8-4.x-support.patch, applied upstream. * Bump Standards-Version to 4.6.1, no changes needed. Checksums-Sha1: a4903238a177cbc5e76d8f55f555110640abd144 2241 python-pytest-flake8_1.1.1-1.dsc ed5831556e655ba25ecf64800908ea90c3e79aac 9144 python-pytest-flake8_1.1.1.orig.tar.gz 3df7e4f0737c399a69f7e2b7278c8983594c0989 3696 python-pytest-flake8_1.1.1-1.debian.tar.xz ce2a1ea77b9147dd94012a9aa00bf149837f5b22 7021 python-pytest-flake8_1.1.1-1_amd64.buildinfo Checksums-Sha256: 95135fc48405b0bd9edeb650deeaddc6901feb3f876d80c06820cd6335f08598 2241 python-pytest-flake8_1.1.1-1.dsc ba4f243de3cb4c2486ed9e70752c80dd4b636f7ccb27d4eba763c35ed0cd316e 9144 python-pytest-flake8_1.1.1.orig.tar.gz dc0bea968053856093033743d02abaacd371cf73cdfb5c55987aa5ac1eb7b209 3696 python-pytest-flake8_1.1.1-1.debian.tar.xz 6bd6e5668c516dcd216f9796f32e569c5df8e7333b6c930204c0eada0639c4d7 7021 python-pytest-flake8_1.1.1-1_amd64.buildinfo Files: 6d8b90b4f908aa98257aba2af8ae92b0 2241 python optional python-pytest-flake8_1.1.1-1.dsc 15f0042167c2cd75b4b32a82fc92eeae 9144 python optional pytho
Bug#1013591: marked as done (oscar4: FTBFS: [ERROR] Failed to execute goal org.apache.maven.plugins:maven-resources-plugin:3.1.0:resources)
Your message dated Thu, 08 Sep 2022 07:49:14 + with message-id and subject line Bug#1013591: fixed in oscar4 5.2.0+dfsg-1 has caused the Debian Bug report #1013591, regarding oscar4: FTBFS: [ERROR] Failed to execute goal org.apache.maven.plugins:maven-resources-plugin:3.1.0:resources 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.) -- 1013591: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1013591 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: oscar4 Version: 5.1.2+dfsg-1 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20220624 ftbfs-bookworm Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[1]: Entering directory '/<>' > ln -fs /usr/share/EMBOSS/data/OBO/chebi.obo > oscar4-obo/src/main/resources/uk/ac/cam/ch/wwmm/oscar/obo/terms/chebi.obo > ln -s oscar4-tokeniser oscar4-tokenizer > dh_auto_configure > mh_patchpoms -pliboscar4-java --debian-build --keep-pom-version > --maven-repo=/<>/oscar4-5.1.2\+dfsg/debian/maven-repo > make[1]: Leaving directory '/<>' >dh_auto_build > /usr/lib/jvm/default-java/bin/java -noverify -cp > /usr/share/maven/boot/plexus-classworlds-2.x.jar > -Dmaven.home=/usr/share/maven > -Dmaven.multiModuleProjectDirectory=/<>/oscar4-5.1.2\+dfsg > -Dclassworlds.conf=/etc/maven/m2-debian.conf > org.codehaus.plexus.classworlds.launcher.Launcher > -s/etc/maven/settings-debian.xml > -Ddebian.dir=/<>/oscar4-5.1.2\+dfsg/debian > -Dmaven.repo.local=/<>/oscar4-5.1.2\+dfsg/debian/maven-repo > --batch-mode package -DskipTests -Dnotimestamp=true -Dlocale=en_US > [INFO] Scanning for projects... > [INFO] > > [INFO] Reactor Build Order: > [INFO] > [INFO] oscar4-parent > [pom] > [INFO] oscar4-core > [jar] > [INFO] Chemical Name Dictionaries > [jar] > [INFO] oscar4-obo > [jar] > [INFO] oscar4-tokenizer > [jar] > [INFO] oscar4-recogniser-core > [jar] > [INFO] oscar4-memmrecogniser > [jar] > [INFO] oscar4-patternrecogniser > [jar] > [INFO] oscar4-opsin > [jar] > [INFO] oscar4-api > [jar] > [INFO] oscar4-preprocessor > [jar] > [INFO] oscar4-formatter > [jar] > [INFO] oscar4-data > [jar] > [INFO] > [INFO] ---< uk.ac.cam.ch.wwmm.oscar:oscar4 > >--- > [INFO] Building oscar4-parent 5.1.2 > [1/13] > [INFO] [ pom > ]- > [INFO] > [INFO] --- maven-enforcer-plugin:3.0.0-M2:enforce (enforce-maven) @ oscar4 --- > [INFO] > [INFO] < uk.ac.cam.ch.wwmm.oscar:oscar4-core > >- > [INFO] Building oscar4-core 5.1.2 > [2/13] > [INFO] [ jar > ]- > [INFO] > [INFO] --- maven-enforcer-plugin:3.0.0-M2:enforce (enforce-maven) @ > oscar4-core --- > [INFO] > [INFO] --- maven-resources-plugin:3.1.0:resources (default-resources) @ > oscar4-core --- > [INFO] Using 'UTF-8' encoding to copy filtered resources. > [INFO] Copying 11 resources > [INFO] > [INFO] --- maven-compiler-plugin:3.8.1:compile (default-compile) @ > oscar4-core --- > [INFO] Changes detected - recompiling the module! > [INFO] Compiling 29 source files to > /<>/oscar4-core/target/classes > Use of target 1.6 is no longer supported, switching to 7 > Use of source 1.6 is no longer supported, switching to 7 > [INFO] > /<>/oscar4-core/src/main/java/uk/ac/cam/ch/wwmm/oscar/document/NamedEntity.java: > > /<>/oscar4-core/src/main/java/uk/ac/cam/ch/wwmm/oscar/document/NamedEntity.java > uses or overrides a deprecated API. > [INFO] > /<>/oscar4-core/src/main/java/uk/ac/cam/ch/wwmm/oscar/document/NamedEntity.java: > Recompile with -Xlint:deprecation for details. > [INFO] > [INFO] --- maven-resour
