Bug#979294: marked as done (python-ase autopkgtests fail with pytest 6)
Your message dated Tue, 05 Jan 2021 07:50:22 +
with message-id
and subject line Bug#979294: fixed in python-ase 3.20.1-2
has caused the Debian Bug report #979294,
regarding python-ase autopkgtests fail with pytest 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.)
--
979294: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=979294
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-ase
Version: 3.20.1-1
Severity: serious
User: pyt...@packages.debian.org
Usertags: pytest-v6
Hi,
python-ase autopkgtests with pytest 6 in unstable. Apparently, something
is trying to write to /usr/lib/:
> File "/usr/lib/python3/dist-packages/pluggy/callers.py", line 187, in
> _multicall
> res = hook_impl.function(*args)
> File "/usr/lib/python3/dist-packages/_pytest/stepwise.py", line 122, in
> pytest_sessionfinish
> self.config.cache.set("cache/stepwise", [])
> File "/usr/lib/python3/dist-packages/_pytest/cacheprovider.py", line 151,
> in set
> self.warn("could not create cache path {path}", path=path)
> File "/usr/lib/python3/dist-packages/_pytest/cacheprovider.py", line 90, in
> warn
> warnings.warn(
> pytest.PytestCacheWarning: could not create cache path
> /usr/lib/python3/dist-packages/ase/test/.pytest_cache/v/cache/stepwise
In the previous debci run (with pytest 4.6.11), this was only warned about:
> /usr/lib/python3/dist-packages/_pytest/cacheprovider.py:127
> /usr/lib/python3/dist-packages/_pytest/cacheprovider.py:127:
> PytestCacheWarning: could not create cache path
> /usr/lib/python3/dist-packages/ase/test/.pytest_cache/v/cache/nodeids
> self.warn("could not create cache path {path}", path=path)
It seems as this has become a hard failure.
--- End Message ---
--- Begin Message ---
Source: python-ase
Source-Version: 3.20.1-2
Done: Andrius Merkys
We believe that the bug you reported is fixed in the latest version of
python-ase, which is due to be installed in the Debian FTP archive.
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to 979...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Andrius Merkys (supplier of updated python-ase package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Tue, 05 Jan 2021 02:23:27 -0500
Source: python-ase
Architecture: source
Version: 3.20.1-2
Distribution: unstable
Urgency: medium
Maintainer: Debichem Team
Changed-By: Andrius Merkys
Closes: 979294
Changes:
python-ase (3.20.1-2) unstable; urgency=medium
.
* Disabling pytest cache usage (Closes: #979294).
Checksums-Sha1:
22079ba44fdbbc4fdb3be743dd357d4a37b777a3 2509 python-ase_3.20.1-2.dsc
1fb9e6e27f4bba208c3e85a0f3b1578a133ccf35 8468 python-ase_3.20.1-2.debian.tar.xz
52d333a1eb33112e1f41f58755c47e672973b083 10846
python-ase_3.20.1-2_source.buildinfo
Checksums-Sha256:
b7b3a765e53e5f0c2d154b7c4d09daa5358dc19d5dfbef064be85201d3246152 2509
python-ase_3.20.1-2.dsc
3c35e999574be98d6079e269598a5d06dc6b171bde42e818ddfd45b768546db8 8468
python-ase_3.20.1-2.debian.tar.xz
b3704714876410b892b656f7b7595884cde8c32195b82e9ca75846bc4939ebec 10846
python-ase_3.20.1-2_source.buildinfo
Files:
b1426f2902105cb1386d39725de64bbf 2509 science optional python-ase_3.20.1-2.dsc
69effa506239ce8c3eeb961d77e61059 8468 science optional
python-ase_3.20.1-2.debian.tar.xz
255a9c50fa2fc1d4814cafa920fa4aeb 10846 science optional
python-ase_3.20.1-2_source.buildinfo
-BEGIN PGP SIGNATURE-
iQJGBAEBCgAwFiEEdyKS9veshfrgQdQe5fQ/nCc08ocFAl/0FJgSHG1lcmt5c0Bk
ZWJpYW4ub3JnAAoJEOX0P5wnNPKHegYQAIwLBt3EOVS0UDqDAdIBMnzab1ntePsX
8E3eP4TqpFi5/8AQx8VNVZm2P5jQS/ReL06HmhTL5k5UNhn99ktDHXn++apSMsSt
h0zPbHhcUCHS3n7LejE/B26touGDn4RK1cJN9XTabIX74fw7QQnizuEgLel+/JmH
TBPlWXZ4OBMcwfEhwV4i57jYt/0yFzxJwLZIVlDefzhSO8jEIdnrTdwgIB4GSD9Z
6DMqNnH6KSmw8cjVode/I3Ak0CzdQuOX99Y3q5J+7B07+Ai7kVXYn/THVcBquBJ2
Hx37lpBu2g0Uvz6H+wY3xpn1lJnO2njQaqlcX9o+tBuNuaupfXdusGns57uqnjKv
GlMn7tGQGkLSIG68jgWit70/3zMfuNCRej4BIlPfK4+Y3rNIkpAdNGp+q+VG2W6k
dMa8FJoDkHoZ/a5WQLnfmeUh7a94Hk3p65hDohZQG8Bsgt6dUfOFQmDrUZ54A3oE
tgCwwmNl1PUjctiSuN7lnrFGhf/YaOycxLn7sXjw2XIY+JHn9rX49lzoNjIHXhZz
l1lBGc8X4dox9K5jZNSYFQCGuaEaPH8fJi84bWiieImm2e6iQo/ZgZmK4Qbt5uas
Processed: Bug#979294 marked as pending in python-ase
Processing control commands:
> tag -1 pending
Bug #979294 {Done: Andrius Merkys } [src:python-ase]
python-ase autopkgtests fail with pytest 6
Added tag(s) pending.
--
979294: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=979294
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#979294: marked as pending in python-ase
Control: tag -1 pending Hello, Bug #979294 in python-ase 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/python-ase/-/commit/2be7ae03ef8586b85e12758f17216e360db27dd8 Disabling pytest cache usage (Closes: #979294). (this message was generated automatically) -- Greetings https://bugs.debian.org/979294
Bug#977243: Still not fixed
On 1/4/21 4:40 PM, Casey Bodley wrote: > you probably need the first commit from > https://github.com/ceph/ceph/pull/38263 I have included it in debian/patches, but that's not enough. :/ Cheers, Thomas Goirand (zigo)
Processed: Re: openmpi: sync data struct with pmix
Processing control commands: > reassign 979085 openmpi Bug #979085 [src:sopt] FTBFS on mips64el Bug reassigned from package 'src:sopt' to 'openmpi'. No longer marked as found in versions sopt/3.0.1-11. Ignoring request to alter fixed versions of bug #979085 to the same values previously set -- 979085: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=979085 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#979085: openmpi: sync data struct with pmix
Control: reassign 979085 openmpi Pmix4 has some changes on its pmix_server.h, while openmpi has a old one, Which make sopt ftbfs on some architectures: mips64el, ia64 etc. mips64el.patch Description: Binary data On Sun, 3 Jan 2021 17:52:22 +0800 YunQiang Su wrote: > On Sun, 3 Jan 2021 11:11:02 +0800 YunQiang Su wrote: > > On Sun, 03 Jan 2021 00:08:34 +0800 Shengjing Zhu wrote: > > > Source: sopt > > > Version: 3.0.1-11 > > > Severity: serious > > > X-Debbugs-Cc: z...@debian.org > > > > > > > > > When binNMU sopt, it FTBFS on mips64el, please check log at > > > https://buildd.debian.org/status/fetch.php?pkg=sopt=mips64el=3.0.1-11%2Bb1=1609594267=0 > > > > > > The following tests FAILED: > > >19 - communicator (Bus error) > > > > It seems like a “aligned” problem. > > I guess it is due to a problem of spdlog. > > > > Let’s have a debug. > > I found the problem:… > > Pmix4 add a new member `client_connected2’ to pmix_server_module_t. > While openmpi doesn’t set the value to it in pmix3x_server_north.c. > > On some architecture, it make the value of `client_connected2’ as Random > value instead of NULL. > > So it is a problem of openmpi, I think. > > > > > >20 - serial_vs_parallel_padmm (Bus error) > > >21 - mpi_wavelets (Bus error) > > >22 - mpi_session (Bus error) > > > > > > The failed tests seem all related mpi, so I think it's not related to > > > spdlog > > > or fmtlib. openmpi bumped its version from 4.0.5 to 4.1.0 on 2020-12-21. I > > > guess it's related to this change of openmpi. > > > > > > > > > >
Bug#979305: bazel-bootstrap: fails to clean after build: rm: cannot remove 'output': Is a directory
Control: severity -1 important Control: tag -1 pending Hi Andreas, On Mon, Jan 4, 2021 at 8:03 PM Andreas Beckmann wrote: > Package: bazel-bootstrap > Version: 3.5.1+ds-2~exp1 > Severity: serious > Tags: ftbfs > Justification: fails to build from source (but built successfully in the > past) > Thanks for the bug report! I've already fixed this problem locally and will upload shortly. I downgraded the severity because the version in unstable (and testing) does not seem to exhibit this problem. The failure was just on a version in experimental that I was using to diagnose unrelated issues. Thanks again! -Olek > >
Processed: Re: Bug#979305: bazel-bootstrap: fails to clean after build: rm: cannot remove 'output': Is a directory
Processing control commands: > severity -1 important Bug #979305 [bazel-bootstrap] bazel-bootstrap: fails to clean after build: rm: cannot remove 'output': Is a directory Severity set to 'important' from 'serious' > tag -1 pending Bug #979305 [bazel-bootstrap] bazel-bootstrap: fails to clean after build: rm: cannot remove 'output': Is a directory Added tag(s) pending. -- 979305: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=979305 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#975490: u-boot-sunxi: Booting the system got stuck after "Starting kernel ..."
On 2020-11-27, Vagrant Cascadian wrote: > On 2020-11-22, Vagrant Cascadian wrote: >> On 2020-11-22, Benedikt Spranger wrote: >>> after a fresh install of Debian "bullseye" the first reboot got stuck >>> after "Starting kernel ..." > ... >>> U-Boot 2020.10+dfsg-1+b1 (Nov 19 2020 - 03:18:11 +) Allwinner >>> Technology > ... >>> Scanning mmc 1:1... >>> Found U-Boot script /boot.scr >>> 2225 bytes read in 2 ms (1.1 MiB/s) >>> ## Executing script at 4fc0 >>> 22744944 bytes read in 1003 ms (21.6 MiB/s) >>> 28403 bytes read in 5 ms (5.4 MiB/s) >>> 30071341 bytes read in 1326 ms (21.6 MiB/s) >>> Booting Debian 5.9.0-2-arm64 from mmc 1:1... >>> Moving Image from 0x4008 to 0x4020, end=4185 >>> ## Flattened Device Tree blob at 4fa0 >>>Booting using the fdt blob at 0x4fa0 >>> EHCI failed to shut down host controller. >>>Loading Ramdisk to 48352000, end 49fffa2d ... OK >>>Loading Device Tree to 48348000, end 48351ef2 ... OK >>> >>> Starting kernel ... > ... >> I'll test on a few of my systems to see if I can reproduce the issue. > > I can confirm similar behavior on a pinebook, although the kernel does > boot and actually load, and eventually displays on the LCD display (if I > "setenv console" from u-boot commandline). It even responds > appropriately to ctrl-alt-delete, so it is not a completely hung > kernel... With a locally built version of 2020.10+dfsg-2, I can no longer reproduce this issue at all. Could you try with the new version? live well, vagrant signature.asc Description: PGP signature
Bug#979283: ddccontrol FTBFS with current glibc
Control: forwarded -1 https://github.com/ddccontrol/ddccontrol/issues/88 On Mon, 4 Jan 2021 20:22:52 +0100 Helmut Grohne wrote: > ddccontrol fails to build from source on arm architectures I filed the above upstream bug about this. > I see basically two options: > * Make the relevant functionality really optional. Options for that I proposed upstream: The correct thing to do would be port the intel740, intel810 and sis code away from x86 I/O ports to architecture-neutral Linux interfaces for device access. If the hardware supported by the intel740, intel810 and sis drivers are not on discrete GPUs that can be plugged into a PCI/PCIe slot on any CPU architecture with PCI support, then porting away from x86 I/O ports would not be useful so a workaround would be reasonable. Since older versions of glibc still have the header, other arches still have the header and other libcs like musl still have the header on the ARM ports, I think the best available workaround would be to check if is available and only build the intel740, intel810 and sis drivers when the header is available. -- bye, pabs https://wiki.debian.org/PaulWise signature.asc Description: This is a digitally signed message part
Processed: Re: ddccontrol FTBFS with current glibc
Processing control commands: > forwarded -1 https://github.com/ddccontrol/ddccontrol/issues/88 Bug #979283 [ddccontrol] ddccontrol FTBFS with current glibc Set Bug forwarded-to-address to 'https://github.com/ddccontrol/ddccontrol/issues/88'. -- 979283: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=979283 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: limit source to symfony, tagging 952431, tagging 977518
Processing commands for cont...@bugs.debian.org: > limit source symfony Limiting to bugs with field 'source' containing at least one of 'symfony' Limit currently set to 'source':'symfony' > tags 952431 + pending Bug #952431 [src:symfony] symfony: FTBFS: test failures with PHP 7.4 Added tag(s) pending. > tags 977518 + pending Bug #977518 [php-symfony-phpunit-bridge] php-symfony-phpunit-bridge: Not compatible with PHPUnit 9 Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 952431: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=952431 977518: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=977518 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#978335: marked as done (rifiuti2: FTBFS: error: gettext infrastructure mismatch: using a Makefile.in.in from gettext version 0.19 but the autoconf macros are from gettext version 0.20)
Your message dated Tue, 05 Jan 2021 01:35:36 +
with message-id
and subject line Bug#978335: fixed in rifiuti2 0.7.0-3
has caused the Debian Bug report #978335,
regarding rifiuti2: FTBFS: error: gettext infrastructure mismatch: using a
Makefile.in.in from gettext version 0.19 but the autoconf macros are from
gettext version 0.20
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.)
--
978335: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=978335
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: rifiuti2
Version: 0.7.0-2
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20201226 ftbfs-bullseye
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> make[4]: Entering directory '/<>/po'
> sed -e '/^#/d' remove-potcdate.sin > t-remove-potcdate.sed
> mv t-remove-potcdate.sed remove-potcdate.sed
> package_gnu="no"; \
> test -n "$package_gnu" || { \
> if { if (LC_ALL=C find --version) 2>/dev/null | grep GNU >/dev/null; then \
>LC_ALL=C find -L .. -maxdepth 1 -type f \
> -size -1000c -exec grep 'GNU rifiuti2' \
> /dev/null '{}' ';' 2>/dev/null; \
>else \
>LC_ALL=C grep 'GNU rifiuti2' ../* 2>/dev/null; \
>fi; \
> } | grep -v 'libtool:' >/dev/null; then \
> package_gnu=yes; \
>else \
> package_gnu=no; \
>fi; \
> }; \
> if test "$package_gnu" = "yes"; then \
> package_prefix='GNU '; \
> else \
> package_prefix=''; \
> fi; \
> if test -n 'https://github.com/abelcheung/rifiuti2/issues' || test
> 'https://github.com/abelcheung/rifiuti2/issues' = '@'PACKAGE_BUGREPORT'@';
> then \
> msgid_bugs_address='https://github.com/abelcheung/rifiuti2/issues'; \
> else \
> msgid_bugs_address='https://github.com/abelcheung/rifiuti2/issues'; \
> fi; \
> case `/usr/bin/xgettext --version | sed 1q | sed -e 's,^[^0-9]*,,'` in \
> '' | 0.[0-9] | 0.[0-9].* | 0.1[0-5] | 0.1[0-5].* | 0.16 | 0.16.[0-1]*) \
> /usr/bin/xgettext --default-domain=rifiuti2 --directory=.. \
> --add-comments=TRANSLATORS: --keyword=_ --keyword=N_
> --add-comments="TRANSLATOR" \
> --files-from=./POTFILES.in \
> --copyright-holder='' \
> --msgid-bugs-address="$msgid_bugs_address" \
> ;; \
> *) \
> /usr/bin/xgettext --default-domain=rifiuti2 --directory=.. \
> --add-comments=TRANSLATORS: --keyword=_ --keyword=N_
> --add-comments="TRANSLATOR" \
> --files-from=./POTFILES.in \
> --copyright-holder='' \
> --package-name="${package_prefix}rifiuti2" \
> --package-version='0.7.0' \
> --msgid-bugs-address="$msgid_bugs_address" \
> ;; \
> esac
> test ! -f rifiuti2.po || { \
> if test -f ./rifiuti2.pot; then \
> sed -f remove-potcdate.sed < ./rifiuti2.pot > rifiuti2.1po && \
> sed -f remove-potcdate.sed < rifiuti2.po > rifiuti2.2po && \
> if cmp rifiuti2.1po rifiuti2.2po >/dev/null 2>&1; then \
> rm -f rifiuti2.1po rifiuti2.2po rifiuti2.po; \
> else \
> rm -f rifiuti2.1po rifiuti2.2po ./rifiuti2.pot && \
> mv rifiuti2.po ./rifiuti2.pot; \
> fi; \
> else \
> mv rifiuti2.po ./rifiuti2.pot; \
> fi; \
> }
> make[4]: Leaving directory '/<>/po'
> *** error: gettext infrastructure mismatch: using a Makefile.in.in from
> gettext version 0.19 but the autoconf macros are from gettext version 0.20
> make[3]: *** [Makefile:219: stamp-po] Error 1
The full build log is available from:
http://qa-logs.debian.net/2020/12/26/rifiuti2_0.7.0-2_unstable.log
A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!
If you reassign this bug to another package, please marking it as 'affects'-ing
this package. See https://www.debian.org/Bugs/server-control#affects
If you fail to reproduce this, please provide a build log and diff it with me
so that we can identify if something relevant changed in the meantime.
About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.
--- End Message ---
--- Begin Message ---
Source: rifiuti2
Source-Version: 0.7.0-3
Done: Giovani Augusto Ferreira
We believe that the bug you reported is fixed in the latest version of
rifiuti2, 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.
Bug#979305: bazel-bootstrap: fails to clean after build: rm: cannot remove 'output': Is a directory
Package: bazel-bootstrap Version: 3.5.1+ds-2~exp1 Severity: serious Tags: ftbfs Justification: fails to build from source (but built successfully in the past) Hi, bazel-bootstrap fails to build twice in a row since it does not properly clean after the first (and successful) build: debian/rules clean dh clean --with python3 rm -f debian/bazel-bootstrap-data.debhelper.log debian/bazel-bootstrap.debhelper.log debian/rules override_dh_auto_clean make[1]: Entering directory '/build/bazel-bootstrap-3.5.1+ds' dh_auto_clean install -d /build/bazel-bootstrap-3.5.1\+ds/debian/.debhelper/generated/_source/home rm -rf derived rm -f output rm: cannot remove 'output': Is a directory make[1]: *** [debian/rules:62: override_dh_auto_clean] Error 1 make[1]: Leaving directory '/build/bazel-bootstrap-3.5.1+ds' make: *** [debian/rules:53: clean] Error 2 Andreas bazel-bootstrap_3.5.1+ds-2~exp1_twice.log.gz Description: application/gzip
Bug#979304: src:libsnmp-multi-perl: invalid maintainer addres
Source: libsnmp-multi-perl Version: 2.1-4 Severity: serious Tags: bullseye sid X-Debbugs-Cc: Holger Levsen The maintainer address is invalid, see below. Ansgar Start of forwarded message From: Mail Delivery System Subject: Mail delivery failed: returning message to sender Date: Tue, 05 Jan 2021 00:36:32 + This message was created automatically by mail delivery software. A message that you sent could not be delivered to one or more of its recipients. This is a permanent error. The following address(es) failed: a...@ubuntu.com host mx.canonical.com [91.189.95.10] SMTP error from remote mail server after RCPT TO:: 550 5.1.1 : Recipient address rejected: User unknown in virtual alias table Reporting-MTA: dns; mailly.debian.org Action: failed Final-Recipient: rfc822;arne@ubuntu.com Status: 5.0.0 Remote-MTA: dns; mx.canonical.com Diagnostic-Code: smtp; 550 5.1.1 : Recipient address rejected: User unknown in virtual alias table
Bug#976518: marked as done (gsound: FTBFS: Unescaped left brace in regex is passed through in regex; marked by <-- HERE in m/^${ <-- HERE abs_top_builddir}/gsound$/ at /usr/bin/automake line 5755.)
Your message dated Tue, 05 Jan 2021 00:19:25 +
with message-id
and subject line Bug#976518: fixed in gsound 1.0.2-5
has caused the Debian Bug report #976518,
regarding gsound: FTBFS: Unescaped left brace in regex is passed through in
regex; marked by <-- HERE in m/^${ <-- HERE abs_top_builddir}/gsound$/ at
/usr/bin/automake line 5755.
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.)
--
976518: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=976518
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: gsound
Version: 1.0.2-4
Severity: serious
Justification: FTBFS on arm64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20201205 ftbfs-bullseye
Hi,
During a rebuild of all packages in sid, your package failed to build
on arm64 (I don't know if it also fails on amd64).
Relevant part (hopefully):
> debian/rules build
> dh build
>dh_update_autotools_config
>dh_autoreconf
> libtoolize: putting auxiliary files in AC_CONFIG_AUX_DIR, 'build-aux'.
> libtoolize: copying file 'build-aux/ltmain.sh'
> libtoolize: putting macros in AC_CONFIG_MACRO_DIRS, 'm4'.
> libtoolize: copying file 'm4/libtool.m4'
> libtoolize: copying file 'm4/ltoptions.m4'
> libtoolize: copying file 'm4/ltsugar.m4'
> libtoolize: copying file 'm4/ltversion.m4'
> libtoolize: copying file 'm4/lt~obsolete.m4'
> libtoolize: Consider adding '-I m4' to ACLOCAL_AMFLAGS in Makefile.am.
> configure.ac:14: installing 'build-aux/compile'
> configure.ac:10: installing 'build-aux/missing'
> gsound/Makefile.am: installing 'build-aux/depcomp'
> Unescaped left brace in regex is passed through in regex; marked by <-- HERE
> in m/^${ <-- HERE abs_top_builddir}/gsound$/ at /usr/bin/automake line 5755.
> autoreconf: automake failed with exit status: 255
> dh_autoreconf: error: autoreconf -f -i returned exit code 1
> make: *** [debian/rules:7: build] Error 25
The full build log is available from:
http://qa-logs.debian.net/2020/12/05/gsound_1.0.2-4_unstable.log
A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!
If you reassign this bug to another package, please marking it as 'affects'-ing
this package. See https://www.debian.org/Bugs/server-control#affects
If you fail to reproduce this, please provide a build log and diff it with me
so that we can identify if something relevant changed in the meantime.
About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.
--- End Message ---
--- Begin Message ---
Source: gsound
Source-Version: 1.0.2-5
Done: Andreas Henriksson
We believe that the bug you reported is fixed in the latest version of
gsound, which is due to be installed in the Debian FTP archive.
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to 976...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Andreas Henriksson (supplier of updated gsound package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Tue, 05 Jan 2021 00:57:58 +0100
Source: gsound
Architecture: source
Version: 1.0.2-5
Distribution: unstable
Urgency: medium
Maintainer: Debian GNOME Maintainers
Changed-By: Andreas Henriksson
Closes: 976518
Changes:
gsound (1.0.2-5) unstable; urgency=medium
.
* Team upload.
.
[ Jeremy Bicha ]
* Bump minimum debhelper to 12 for the dh-sequence feature
.
[ Andreas Henriksson ]
* Add patch to fix autoreconf problem (Closes: #976518)
* Use debhelper-compat (= 12) build-dependency
* Set upstream metadata fields: Bug-Database, Bug-Submit,
Repository, Repository-Browse.
* Update standards version to 4.5.0, no changes needed.
Checksums-Sha1:
38bc049733e4112b714a08b39c1c91d77f566ebc 2383 gsound_1.0.2-5.dsc
08271ddedb919b158814ddfda04f7e58ddd0dd78 4572 gsound_1.0.2-5.debian.tar.xz
f6699ad7544e75d2d29224c6e1a704ad82c503c9 9330 gsound_1.0.2-5_amd64.buildinfo
Checksums-Sha256:
c76a1df1536a6f7c42d4a2e325b040a45f204748521a358f443f5a2604ee542a 2383
gsound_1.0.2-5.dsc
224c0a03dba8e3396cfedf10ed7431d06797028e24bbfe963309bcb196eb5e92 4572
Bug#979302: libgtkextra-3.0: ships libgtkextra-x11-3.0.so
Package: libgtkextra-3.0 Version: 3.3.4-2 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package failed to install because it tries to overwrite other packages files. >From the attached log (scroll to the bottom...): Selecting previously unselected package libgtkextra-3.0. Preparing to unpack .../61-libgtkextra-3.0_3.3.4-2_amd64.deb ... Unpacking libgtkextra-3.0 (3.3.4-2) ... Selecting previously unselected package libgtkextra-dev. Preparing to unpack .../62-libgtkextra-dev_3.3.4-2_amd64.deb ... Unpacking libgtkextra-dev (3.3.4-2) ... dpkg: error processing archive /tmp/apt-dpkg-install-gS1CgJ/62-libgtkextra-dev_3.3.4-2_amd64.deb (--unpack): trying to overwrite '/usr/lib/x86_64-linux-gnu/libgtkextra-x11-3.0.so', which is also in package libgtkextra-3.0 3.3.4-2 Errors were encountered while processing: /tmp/apt-dpkg-install-gS1CgJ/62-libgtkextra-dev_3.3.4-2_amd64.deb The .so symlink belongs into the -dev package, not into the package with the shared library. (Policy 8.4) Looking at the changelog entry of the last upload I noticed > * modified debian/libgtkextra-3.0.install to include files > usr/lib/x86_64-linux-gnu/libgtkextra-x11-3.0.a and The .a file belongs into the -dev package. (Policy 8.3) > usr/lib/x86_64-linux-gnu/libgtkextra-x11-3.0.la in order to prevent The .la file belongs into the trash bin. (https://wiki.debian.org/ReleaseGoals/LAFileRemoval) > dh_missing's warning about files "not installed to anywhere" cheers, Andreas libgtkextra-dev=3.3.4-2_libgtkextra-3.0=3.3.4-2.log.gz Description: application/gzip
Bug#978364: apertium-ukr: FTBFS: Error: Invalid dictionary (hint: the left side of an entry is empty)
apertium-ukr should be removed from Debian. The pair that needed it has been upgraded to bundle the required version instead: https://salsa.debian.org/science-team/apertium-rus-ukr -- Tino Didriksen
Bug#979287: marked as done (libshell-utils-clojure: broken dependency libi18n-clojure)
Your message dated Tue, 05 Jan 2021 00:06:07 + with message-id and subject line Bug#979287: fixed in shell-utils-clojure 1.0.2-2 has caused the Debian Bug report #979287, regarding libshell-utils-clojure: broken dependency libi18n-clojure 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.) -- 979287: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=979287 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: libshell-utils-clojure Version: 1.0.2-1 Severity: grave Owner: po...@debian.org This package has libi18n-clojure as a dependency. This package does not exist and should be libpuppetlabs-i18n-clojure instead. This makes this package uninstallable. -- ⢀⣴⠾⠻⢶⣦⠀ ⣾⠁⢠⠒⠀⣿⡁ Louis-Philippe Véronneau ⢿⡄⠘⠷⠚⠋ po...@debian.org / veronneau.org ⠈⠳⣄ OpenPGP_signature Description: OpenPGP digital signature --- End Message --- --- Begin Message --- Source: shell-utils-clojure Source-Version: 1.0.2-2 Done: Louis-Philippe Véronneau We believe that the bug you reported is fixed in the latest version of shell-utils-clojure, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 979...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Louis-Philippe Véronneau (supplier of updated shell-utils-clojure 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, 04 Jan 2021 18:45:48 -0500 Source: shell-utils-clojure Architecture: source Version: 1.0.2-2 Distribution: unstable Urgency: medium Maintainer: Debian Clojure Maintainers Changed-By: Louis-Philippe Véronneau Closes: 979287 Changes: shell-utils-clojure (1.0.2-2) unstable; urgency=medium . * Team upload. . [ Louis-Philippe Véronneau ] * Rebuild using lein. (Closes: #979287) * d/control: use dh13. * d/watch: create file. * d/control: Standards-Version update to 4.5.1. Add Rules-Requires-Root. * d/copyright: fix upstream name and insecure URI. * d/tests: add autopkgtests. . [ Thomas Goirand ] * Add a debian/salsa-ci.yml. Checksums-Sha1: efb923ee38d12d80c8bce7387781bdfb3c96cc87 2423 shell-utils-clojure_1.0.2-2.dsc 8d842bc8de7fbb9ea8e5a10da69013c94d128c6b 3368 shell-utils-clojure_1.0.2-2.debian.tar.xz 3e344e25483e969b7f92f6b22f6c3dcf27185938 13058 shell-utils-clojure_1.0.2-2_amd64.buildinfo Checksums-Sha256: 1457000221edd01c28ec7d6d082241233bea320376e986831141319bdea4501d 2423 shell-utils-clojure_1.0.2-2.dsc 3566e8e3573f0db634e946db8eb673d53b72e1ca2466ee10421ae28c2c7a254d 3368 shell-utils-clojure_1.0.2-2.debian.tar.xz 82fd4d6a0f8ff50ad1e6b3131f4c0d119fabe0173f32ba5fa5d58c8f6f006a5a 13058 shell-utils-clojure_1.0.2-2_amd64.buildinfo Files: e263be7e34fbca6db05ee5c6e25fc950 2423 java optional shell-utils-clojure_1.0.2-2.dsc cff451d2dc9aa8222b91df4e826547f8 3368 java optional shell-utils-clojure_1.0.2-2.debian.tar.xz dbed15887b9cd7bdbf12ecf41d32fa11 13058 java optional shell-utils-clojure_1.0.2-2_amd64.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEZ39U8fqGga2OwLzmeurE7GqqCpcFAl/zqTsACgkQeurE7Gqq CpfwDRAAvAzDJXpxBi5dOsqbnrNVp/b9bJhcI643aD8Mwi2Xo7SL75ztDkRAy9d6 miXtDW+LCk4u5bcAQsarWl6RRMS8OQxsP/xB/IK5bhnxXheaZls3mI8tH3hNQ1aV NXufytl78pxxPnMCUMZRV+quPSwDweN4L26ON+0aRn+UCAkGmNdWmXshAAq8cM8j qYc0O+5nUMpmSV6v3JyibBvv3Jqg8PbZMs7iCa87viZHV+XvLweZWNMEoaBat3RD LwFvq+Z6oE89yYocgeuWdLeR7I9417zP5VjG5tFSkKCYvCwAlmFIidtUBV7Fd8j1 8dnk1j/H6nyCBx7XzTIwko6JEJuwXj+B3DIxSLkf5gK1ANp08oSrk6z2qvVWsVjq E4QftHlEkXN8ocKfqx6tEqFrq4viGcUx/AGUoDMD8t2tl/Xk8D9CBBm0vvElRwK9 ADu/SGfrg3VqL9On2qEktqD876KPhRruux15KppXtQRTeiAaEL08i/u7a3Eip8vu M3w6/sTbUqMqKXncrDnx6eVEwuVaajF6RnitBfbKY9G65gAYx1wjCjF638cD9gAA FUFpiJLYpFhGZ1cI7XOgYtKEo0I4S21h01mH+bU+HUPEKLcjaWRUBkvtficy++3K sdfj+cTpdcZ6lhw6YHBLtKvjb3hnA5uE+0G1BuBv7TnsZSk7wPY= =CZrN -END PGP SIGNATURE End Message ---
Bug#978377: apertium-eo-fr: FTBFS: Error: Invalid dictionary (hint: entry on the right beginning with whitespace)
Fixed in Salsa https://salsa.debian.org/science-team/apertium-eo-fr -- Tino Didriksen
Processed: Bug#976518 marked as pending in gsound
Processing control commands:
> tag -1 pending
Bug #976518 [src:gsound] gsound: FTBFS: Unescaped left brace in regex is passed
through in regex; marked by <-- HERE in m/^${ <-- HERE
abs_top_builddir}/gsound$/ at /usr/bin/automake line 5755.
Added tag(s) pending.
--
976518: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=976518
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#976518: marked as pending in gsound
Control: tag -1 pending Hello, Bug #976518 in gsound reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/gnome-team/gsound/-/commit/8bc79f25bd01f5a3ac035d40bef40ac73b926f34 Add patch to fix autoreconf problem Closes: #976518 (this message was generated automatically) -- Greetings https://bugs.debian.org/976518
Bug#979301: namazu2-index-tools: contains namazu.1 manpage after separate arch-indep build
Package: namazu2-index-tools Version: 2.0.21-22.1 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package fails to upgrade from 'testing'. It installed fine in 'testing', then the upgrade to 'sid' fails because it tries to overwrite other packages files. >From the attached log (scroll to the bottom...): Preparing to unpack .../namazu2-index-tools_2.0.21-22.1_all.deb ... Unpacking namazu2-index-tools (2.0.21-22.1) ... dpkg: error processing archive /var/cache/apt/archives/namazu2-index-tools_2.0.21-22.1_all.deb (--unpack): trying to overwrite '/usr/share/man/man1/namazu.1.gz', which is also in package namazu2 2.0.21-22 Errors were encountered while processing: /var/cache/apt/archives/namazu2-index-tools_2.0.21-22.1_all.deb This is caused by the override_dh_installman: dh_installman man/namazu.1 target in debian/rules which acts on the first package being built: * namazu2 during a separate binary-arch or combined binary-arch + binary-indep build * namazu2-index-tools during a separate binary-indep build The buildds only perform separate arch and indep builds, while the maintainer uploaded namazu2-index-tools_2.0.21-22_all.deb seems to stem from a combined build. A quick fix is probably to use dh_installman -pnamazu2 man/namazu.1 cheers, Andreas namazu2=2.0.21-22_namazu2-index-tools=2.0.21-22.1.log.gz Description: application/gzip
Bug#979300: sabnzbdplus autopkgtests fail with pytest 6
Source: sabnzbdplus Version: 3.1.1+dfsg-1 Severity: serious User: pyt...@packages.debian.org Usertags: pytest-v6 Hi, sabnzbdplus autopkgtests fail with pytest 6 in unstable. The problem seems to be the -k expression used to exclude particular tests: > ERROR: Wrong expression passed to '-k': tests and not ( > test_publicipv4 or test_extract_pot or > test_functional_downloads ortest_happyeyeballs or > test_internetspeed or test_permissions_450 or > test_http_params_etc or test_daemonizing > ): at column 210: unexpected character " > " The syntax accepted by -k has changed, see https://docs.pytest.org/en/stable/changelog.html#id101
Bug#979297: python-llfuse FTBFS with pytest 6
Source: python-llfuse Version: 1.3.6+dfsg-2 Severity: serious User: pyt...@packages.debian.org Usertags: pytest-v6 Hi, python-llfuse FTBFS with pytest 6 in unstable: > ERRORS > > _ ERROR at setup of test_inquire_bits > __ > Traceback (most recent call last): > File "/<>/test/pytest_checklogs.py", line 135, in > pytest_runtest_setup > check_output(item) > File "/<>/test/pytest_checklogs.py", line 131, in check_output > check_test_log(item.catch_log_handler) > AttributeError: 'Function' object has no attribute 'catch_log_handler' > ERROR at teardown of test_inquire_bits > > Traceback (most recent call last): > File "/<>/test/pytest_checklogs.py", line 141, in > pytest_runtest_teardown > check_output(item) > File "/<>/test/pytest_checklogs.py", line 131, in check_output > check_test_log(item.catch_log_handler) > AttributeError: 'Function' object has no attribute 'catch_log_handler' > === warnings summary > === > /<>/test/util.py:67 > /<>/test/util.py:67 > /<>/test/util.py:67: PytestUnknownMarkWarning: Unknown > pytest.mark.uses_fuse - is this a typo? You can register custom marks to > avoid this warning - for details, see > https://docs.pytest.org/en/stable/mark.html > return pytest.mark.uses_fuse() > > -- Docs: https://docs.pytest.org/en/stable/warnings.html > === short test summary info > > ERROR ../../../test/test_api.py::test_inquire_bits - AttributeError: > 'Functio... > ERROR ../../../test/test_api.py::test_inquire_bits - AttributeError: > 'Functio... > !! stopping after 2 failures > !!! > 2 warnings, 2 errors in 0.06s > = This has been fixed upstream: https://github.com/libfuse/libfuse/issues/510
Bug#976414: libseqlib: ftbfs with libjsoncpp/experimental
looks like somebody is already working on git, I'll leave to the team then. thanks Michael for having a look! G.
Processed: Re: libseqlib: ftbfs with libjsoncpp/experimental
Processing control commands: > tags -1 patch pending Bug #976414 [src:libseqlib] libseqlib: ftbfs with libjsoncpp/experimental Added tag(s) pending and patch. -- 976414: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=976414 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#976414: libseqlib: ftbfs with libjsoncpp/experimental
control: tags -1 patch pending
--- a/src/ReadFilter.cpp
+++ b/src/ReadFilter.cpp
@@ -193,7 +193,8 @@ bool ReadFilter::isReadOverlappingRegion(const BamRecord
) const {
// assign the global rule if there is one
// remove from the rest of the rules
-Json::Value glob = root.removeMember("global");
+Json::Value glob = root.get("global", null);
+root.removeMember("global");
if (!glob.isNull())
rule_all.parseJson(glob);
Will test and upload if build is good
G.
Bug#979294: python-ase autopkgtests fail with pytest 6
Source: python-ase
Version: 3.20.1-1
Severity: serious
User: pyt...@packages.debian.org
Usertags: pytest-v6
Hi,
python-ase autopkgtests with pytest 6 in unstable. Apparently, something
is trying to write to /usr/lib/:
> File "/usr/lib/python3/dist-packages/pluggy/callers.py", line 187, in
> _multicall
> res = hook_impl.function(*args)
> File "/usr/lib/python3/dist-packages/_pytest/stepwise.py", line 122, in
> pytest_sessionfinish
> self.config.cache.set("cache/stepwise", [])
> File "/usr/lib/python3/dist-packages/_pytest/cacheprovider.py", line 151,
> in set
> self.warn("could not create cache path {path}", path=path)
> File "/usr/lib/python3/dist-packages/_pytest/cacheprovider.py", line 90, in
> warn
> warnings.warn(
> pytest.PytestCacheWarning: could not create cache path
> /usr/lib/python3/dist-packages/ase/test/.pytest_cache/v/cache/stepwise
In the previous debci run (with pytest 4.6.11), this was only warned about:
> /usr/lib/python3/dist-packages/_pytest/cacheprovider.py:127
> /usr/lib/python3/dist-packages/_pytest/cacheprovider.py:127:
> PytestCacheWarning: could not create cache path
> /usr/lib/python3/dist-packages/ase/test/.pytest_cache/v/cache/nodeids
> self.warn("could not create cache path {path}", path=path)
It seems as this has become a hard failure.
Bug#979291: xonsh autopkgtests fail with pytest 6
Source: xonsh Version: 0.9.24+dfsg-2 Severity: serious User: pyt...@packages.debian.org Usertags: pytest-v6 Hi, xonsh autopkgtests with pytest 6 in unstable because it uses a deprecated feature that will be removed soon, and that, by default, considered an error in pytest 6. The fragment of the CI the error log below has more details. > ERRORS > > ERROR collecting test session > _ > /usr/lib/python3/dist-packages/pluggy/hooks.py:286: in __call__ > return self._hookexec(self, self.get_hookimpls(), kwargs) > /usr/lib/python3/dist-packages/pluggy/manager.py:92: in _hookexec > return self._inner_hookexec(hook, methods, kwargs) > /usr/lib/python3/dist-packages/pluggy/manager.py:83: in > self._inner_hookexec = lambda hook, methods, kwargs: hook.multicall( > /usr/lib/python3/dist-packages/xonsh/pytest_plugin.py:44: in > pytest_collect_file > return XshFile(path, parent) > /usr/lib/python3/dist-packages/_pytest/nodes.py:95: in __call__ > warnings.warn(NODE_USE_FROM_PARENT.format(name=self.__name__), > stacklevel=2) > E pytest.PytestDeprecationWarning: Direct construction of XshFile has been > deprecated, please use XshFile.from_parent. > E See > https://docs.pytest.org/en/stable/deprecations.html#node-construction-changed-to-node-from-parent > for more details. > === short test summary info > > ERROR - pytest.PytestDeprecationWarning: Direct construction of XshFile has > ... > Interrupted: 1 error during collection > > === 1 error in 0.07s > ===
Bug#978359: apertium-br-fr: FTBFS: Error: Invalid dictionary (hint: entry on the right beginning with whitespace)
Fixed in Salsa https://salsa.debian.org/science-team/apertium-br-fr -- Tino Didriksen
Bug#859926: speechd-up: fails to install
On Mon, Jan 04, 2021 at 10:02:38PM +0100, Paul Gevers wrote: > [...] > > Yes, the "pulse,alsa" user-visible change seems interesting. But the > > implementation seems fragile to me: looking in /proc content is deemed > > to break at some point or another. We've been struck hard by such kind > > of tinkering in the past, I'd rather not see that happen again :/ > > Ack. @Dennis, feel free to comment on this too. I agree with the assessment that depending on /proc is far from ideal, but I've been running it for a few months now and it's been working better than I had expected. However, the issues that I've encountered so far mostly stem from a lack of integration. For example, Orca is started via /etc/xdg/autostart and pulseaudio in some cases via the user's systemd, which means both are uncoordinated and thus race for the audio device. Another issue I've seen under Bullseye is that gdm3 makes its instance of pulseaudio give up control of the audio device when the user switches to console which then mutes speakup if speechd-up has already connected to pulseaudio, and there appears to be no config option to turn that off. I've also had some cases where speech-dispatcher pegs the CPU at 100 % for some reason, but I haven't figured out the cause for that yet. So, if this patch won't make it into Bullseye, it's not going to be the end of the world. The reason I started work on this in the first place is that AFAIK Firefox some time ago dropped ALSA support and now only supports pulseaudio. Also to me it seems like the only way to implement features like automatically picking up a phone call and routing speech and phone audio to different ears or spatialization of arbitrary sound sources. Regards, Dennis
Bug#979290: pytest-mpi autopkgtests fail with pytest 6
Source: pytest-mpi Version: 0.4-2 Severity: serious User: pyt...@packages.debian.org Usertags: pytest-v6 Hi, pytest-mpi autopkgtests fail with pytest 6 in unstable. From the CI log below, for some reason, the test gets aborted at some point: > Testing with python3.9: > = test session starts > == > platform linux -- Python 3.9.1, pytest-6.0.2, py-1.10.0, pluggy-0.13.0 > rootdir: /tmp/autopkgtest.zQV9kC/build.XJA/src > plugins: mpi-0+unknown > collected 13 items > > docs/markers.rst . [ > 7%] > docs/usage.rst ..[ > 23%] > tests/test_fixtures.py ... [ > 46%] > tests/test_markers.py .FF..Fatal Python error: Aborted > > Current thread 0x7fa7514af740 (most recent call first): > File "/usr/lib/python3.9/subprocess.py", line 1752 in _execute_child > File "/usr/lib/python3.9/subprocess.py", line 947 in __init__ > File "/usr/lib/python3/dist-packages/_pytest/pytester.py", line 1193 in > popen > File "/usr/lib/python3/dist-packages/_pytest/pytester.py", line 1234 in run > File "/tmp/autopkgtest.zQV9kC/build.XJA/src/tests/conftest.py", line 44 in > runpytest_subprocess > File "/tmp/autopkgtest.zQV9kC/build.XJA/src/tests/conftest.py", line 52 in > runpytest > File "/tmp/autopkgtest.zQV9kC/build.XJA/src/tests/test_markers.py", line > 113 in test_mpi_xfail_under_mpi > File "/usr/lib/python3/dist-packages/_pytest/python.py", line 180 in > pytest_pyfunc_call > File "/usr/lib/python3/dist-packages/pluggy/callers.py", line 187 in > _multicall > File "/usr/lib/python3/dist-packages/pluggy/manager.py", line 83 in > File "/usr/lib/python3/dist-packages/pluggy/manager.py", line 92 in > _hookexec > File "/usr/lib/python3/dist-packages/pluggy/hooks.py", line 286 in __call__ > File "/usr/lib/python3/dist-packages/_pytest/python.py", line 1570 in > runtest > File "/usr/lib/python3/dist-packages/_pytest/runner.py", line 153 in > pytest_runtest_call > File "/usr/lib/python3/dist-packages/pluggy/callers.py", line 187 in > _multicall > File "/usr/lib/python3/dist-packages/pluggy/manager.py", line 83 in > File "/usr/lib/python3/dist-packages/pluggy/manager.py", line 92 in > _hookexec > File "/usr/lib/python3/dist-packages/pluggy/hooks.py", line 286 in __call__ > File "/usr/lib/python3/dist-packages/_pytest/runner.py", line 247 in > > File "/usr/lib/python3/dist-packages/_pytest/runner.py", line 294 in > from_call > File "/usr/lib/python3/dist-packages/_pytest/runner.py", line 246 in > call_runtest_hook > File "/usr/lib/python3/dist-packages/_pytest/runner.py", line 207 in > call_and_report > File "/usr/lib/python3/dist-packages/_pytest/runner.py", line 117 in > runtestprotocol > File "/usr/lib/python3/dist-packages/_pytest/runner.py", line 100 in > pytest_runtest_protocol > File "/usr/lib/python3/dist-packages/pluggy/callers.py", line 187 in > _multicall > File "/usr/lib/python3/dist-packages/pluggy/manager.py", line 83 in > File "/usr/lib/python3/dist-packages/pluggy/manager.py", line 92 in > _hookexec > File "/usr/lib/python3/dist-packages/pluggy/hooks.py", line 286 in __call__ > File "/usr/lib/python3/dist-packages/_pytest/main.py", line 321 in > pytest_runtestloop > File "/usr/lib/python3/dist-packages/pluggy/callers.py", line 187 in > _multicall > File "/usr/lib/python3/dist-packages/pluggy/manager.py", line 83 in > File "/usr/lib/python3/dist-packages/pluggy/manager.py", line 92 in > _hookexec > File "/usr/lib/python3/dist-packages/pluggy/hooks.py", line 286 in __call__ > File "/usr/lib/python3/dist-packages/_pytest/main.py", line 296 in _main > File "/usr/lib/python3/dist-packages/_pytest/main.py", line 240 in > wrap_session > File "/usr/lib/python3/dist-packages/_pytest/main.py", line 289 in > pytest_cmdline_main > File "/usr/lib/python3/dist-packages/pluggy/callers.py", line 187 in > _multicall > File "/usr/lib/python3/dist-packages/pluggy/manager.py", line 83 in > File "/usr/lib/python3/dist-packages/pluggy/manager.py", line 92 in > _hookexec > File "/usr/lib/python3/dist-packages/pluggy/hooks.py", line 286 in __call__ > File "/usr/lib/python3/dist-packages/_pytest/config/__init__.py", line 157 > in main > File "/usr/lib/python3/dist-packages/_pytest/config/__init__.py", line 180 > in console_main > File "/usr/lib/python3/dist-packages/pytest/__main__.py", line 7 in > File "/usr/lib/python3.9/runpy.py", line 87 in _run_code > File "/usr/lib/python3.9/runpy.py", line 197 in _run_module_as_main > .bash: line 1: 1425 Aborted $py -m pytest -p pytester > autopkgtest [23:28:58]: test command1: ---]
Bug#975228: xdg-utils: FTBFS: tests failed
Control: tags -1 + patch upstream
Hello,
On Thu, Nov 19, 2020 at 10:56:51AM +0100, Lucas Nussbaum wrote:
> Source: xdg-utils
> Version: 1.1.3-2
> Severity: serious
> Justification: FTBFS on amd64
> Tags: bullseye sid ftbfs
> Usertags: ftbfs-20201119 ftbfs-bullseye
>
> Hi,
>
> During a rebuild of all packages in sid, your package failed to build
> on amd64.
>
> Relevant part (hopefully):
> > make[3]: Entering directory '/<>/autotests'
[...]
> > * Testing that xdg-open
> > - opens a URL with gio open in recent GNOME 3, and Cinnamon
> > ASSERTION FAILED: expected command to be run: gio open
> > http://www.freedesktop.org/
> > ASSERTION FAILED: expected command to be run: gio open
> > http://www.freedesktop.org/
[...]
The problem is using the command "gio open" (containing space) and
a/ not properly handling its expansion b/ mocking it as an executable
including the space.
The attached patch fixes the problem, but I have no idea why this
problem appeared now
Regards,
Andreas Henriksson
diff -uriNp xdg-utils-1.1.3.orig/autotests/t-xdg-open.sh xdg-utils-1.1.3/autotests/t-xdg-open.sh
--- xdg-utils-1.1.3.orig/autotests/t-xdg-open.sh 2021-01-04 21:59:11.0 +
+++ xdg-utils-1.1.3/autotests/t-xdg-open.sh 2021-01-04 22:00:09.919276956 +
@@ -7,7 +7,7 @@ test_open_url() {
shift
local cmd=$1
-mock $cmd
+mock "$cmd"
run $de xdg-open http://www.freedesktop.org/
assert_run "$@" http://www.freedesktop.org/
unmock $cmd
diff -uriNp xdg-utils-1.1.3.orig/autotests/test-lib.sh xdg-utils-1.1.3/autotests/test-lib.sh
--- xdg-utils-1.1.3.orig/autotests/test-lib.sh 2018-05-10 15:02:31.0 +
+++ xdg-utils-1.1.3/autotests/test-lib.sh 2021-01-04 21:59:52.927289723 +
@@ -95,7 +95,7 @@ set_de_() {
}
mock() {
-local command="$1" script="$2"
+local command="$(echo $1 | cut -d' ' -f1)" script="$2"
local executable="$BINDIR/$command"
cat >"$executable" <
Processed: Re: xdg-utils: FTBFS: tests failed
Processing control commands: > tags -1 + patch upstream Bug #975228 [src:xdg-utils] xdg-utils: FTBFS: tests failed Added tag(s) patch and upstream. -- 975228: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=975228 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#979289: libliberator-clojure: broken dependencies libdata.csv-clojure libdata.json-clojure
Package: libliberator-clojure Version: 0.15.2-1 Severity: grave Owner: po...@debian.org This package depends on libdata.csv-clojure and libdata.json-clojure, but those packages do not exist. The package should instead depend on libdata-csv-clojure and libdata-json-clojure. This makes this package uninstallable. -- ⢀⣴⠾⠻⢶⣦⠀ ⣾⠁⢠⠒⠀⣿⡁ Louis-Philippe Véronneau ⢿⡄⠘⠷⠚⠋ po...@debian.org / veronneau.org ⠈⠳⣄ OpenPGP_signature Description: OpenPGP digital signature
Bug#979288: ffc autopkgtests fail with pytest 6
Source: ffc Version: 2019.2.0~git20200123.6b621eb-3 Severity: serious User: pyt...@packages.debian.org Usertags: pytest-v6 Hi, ffc autopkgtests with pytest 6 in unstable because it uses a deprecated feature that will be removed soon, and that, by default, considered an error in pytest 6. The fragment of the CI the error log below has more details. > ERRORS > > ERROR collecting test session > _ > /usr/lib/python3.9/importlib/__init__.py:127: in import_module > return _bootstrap._gcd_import(name[level:], package, level) > :1030: in _gcd_import > ??? > :1007: in _find_and_load > ??? > :986: in _find_and_load_unlocked > ??? > :680: in _load_unlocked > ??? > /usr/lib/python3/dist-packages/_pytest/assertion/rewrite.py:170: in > exec_module > exec(co, module.__dict__) > uflacs/crosslanguage/conftest.py:234: in > ??? > /usr/lib/python3/dist-packages/_pytest/fixtures.py:1358: in fixture > warnings.warn(FIXTURE_POSITIONAL_ARGUMENTS, stacklevel=2) > E pytest.PytestDeprecationWarning: Passing arguments to pytest.fixture() as > positional arguments is deprecated - pass them as a keyword argument instead. > === short test summary info > > ERROR .. - pytest.PytestDeprecationWarning: Passing arguments to > pytest.fixtu... > Interrupted: 1 error during collection > > === 1 error in 0.42s > ===
Bug#979287: libshell-utils-clojure: broken dependency libi18n-clojure
Package: libshell-utils-clojure Version: 1.0.2-1 Severity: grave Owner: po...@debian.org This package has libi18n-clojure as a dependency. This package does not exist and should be libpuppetlabs-i18n-clojure instead. This makes this package uninstallable. -- ⢀⣴⠾⠻⢶⣦⠀ ⣾⠁⢠⠒⠀⣿⡁ Louis-Philippe Véronneau ⢿⡄⠘⠷⠚⠋ po...@debian.org / veronneau.org ⠈⠳⣄ OpenPGP_signature Description: OpenPGP digital signature
Bug#979286: gitsome autopkgtests fail with pytest 6
Source: gitsome Version: 0.8.0+ds-4 Severity: serious User: pyt...@packages.debian.org Usertags: pytest-v6 Hi, gitsome autopkgtests fail with pytest 6 in unstable because of changes to the use of TerminalWriter. See https://docs.pytest.org/en/stable/changelog.html#id60 The CI error log below has more details. > == 2 passed, 1 skipped, 39 warnings in 0.94s > === > run: OK > autopkgtest [06:35:40]: test test: ---] > autopkgtest [06:35:40]: test test: - - - - - - - - - - results - - - - - - - > - - - > test FAIL stderr: > /usr/lib/python3/dist-packages/_pytest/compat.py:340: > PytestDeprecationWarning: The TerminalReporter.writer attribute is > deprecated, use TerminalReporter._tw instead at your own risk. > autopkgtest [06:35:40]: test test: - - - - - - - - - - stderr - - - - - - - > - - - > /usr/lib/python3/dist-packages/_pytest/compat.py:340: > PytestDeprecationWarning: The TerminalReporter.writer attribute is > deprecated, use TerminalReporter._tw instead at your own risk. > See > https://docs.pytest.org/en/stable/deprecations.html#terminalreporter-writer > for more information. > return getattr(object, name, default) > autopkgtest [06:35:40]: summary > test FAIL stderr: > /usr/lib/python3/dist-packages/_pytest/compat.py:340: > PytestDeprecationWarning: The TerminalReporter.writer attribute is > deprecated, use TerminalReporter._tw instead at your own risk.
Bug#978369: apertium-eo-ca: FTBFS: Error: Invalid dictionary (hint: entry on the right beginning with whitespace)
Fixed in Salsa https://salsa.debian.org/science-team/apertium-eo-ca -- Tino Didriksen
Bug#979285: docopt autopkgtests fail with with pytest 6
Source: docopt Version: 0.6.2-2.2 Severity: serious User: pyt...@packages.debian.org Usertags: pytest-v6 Hi, docopt autopkgtests fail with pytest 6 in unstable because it uses a deprecated feature that will be removed soon, and that, by default, considered an error in pytest 6. The fragment of the CI error log below has more details. > ERRORS > > ERROR collecting test session > _ > /usr/lib/python3/dist-packages/pluggy/hooks.py:286: in __call__ > return self._hookexec(self, self.get_hookimpls(), kwargs) > /usr/lib/python3/dist-packages/pluggy/manager.py:92: in _hookexec > return self._inner_hookexec(hook, methods, kwargs) > /usr/lib/python3/dist-packages/pluggy/manager.py:83: in > self._inner_hookexec = lambda hook, methods, kwargs: hook.multicall( > conftest.py:14: in pytest_collect_file > return DocoptTestFile(path, parent) > /usr/lib/python3/dist-packages/_pytest/nodes.py:95: in __call__ > warnings.warn(NODE_USE_FROM_PARENT.format(name=self.__name__), > stacklevel=2) > E pytest.PytestDeprecationWarning: Direct construction of DocoptTestFile > has been deprecated, please use DocoptTestFile.from_parent. > E See > https://docs.pytest.org/en/stable/deprecations.html#node-construction-changed-to-node-from-parent > for more details. > === short test summary info > > ERROR - pytest.PytestDeprecationWarning: Direct construction of > DocoptTestFi... > Interrupted: 1 error during collection > > === 1 error in 0.08s > === > autopkgtest [06:22:29]: test unittests: ---] > autopkgtest [06:22:30]: test unittests: - - - - - - - - - - results - - - - > - - - - - - > unittestsFAIL non-zero exit status 2
Bug#979283: ddccontrol FTBFS with current glibc
Package: ddccontrol
Version: 0.4.4-1
Severity: serious
Tags: ftbfs
ddccontrol fails to build from source on arm architectures, because
glibc removed the x86-only header there. This header is used
in src/ddcpci/{intel740,intel810,sis}.c. It seems unlikely that any of
these would work on arm, but the remaining functionality could of
ddccontrol would still be useful on arm. Unfortunately, it isn't
optional. As it happens, ddccontrol did build for arm architectures,
which is why this bug is rc.
I see basically two options:
* Remove ddccontrol for arm architectures and move on for x86. There
still is ddcutil.
* Make the relevant functionality really optional.
The latter is a little harder, but likely what should happen.
Helmut
Bug#978194: marked as done (openms: FTBFS: glpk.h:36:16: error: using typedef-name ‘glp_prob’ after ‘struct’)
Your message dated Mon, 04 Jan 2021 22:05:02 + with message-id and subject line Bug#978194: fixed in openms 2.6.0+cleaned1-2 has caused the Debian Bug report #978194, regarding openms: FTBFS: glpk.h:36:16: error: using typedef-name ‘glp_prob’ after ‘struct’ 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.) -- 978194: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=978194 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: openms Version: 2.6.0+cleaned1-1 Severity: serious Justification: FTBFS on amd64 Tags: bullseye sid ftbfs Usertags: ftbfs-20201226 ftbfs-bullseye Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > cd /<>/obj-x86_64-linux-gnu/src/openms && /usr/bin/c++ > -DBOOST_ALL_NO_LIB -DOpenMS_EXPORTS -DQT_CORE_LIB -DQT_NETWORK_LIB > -DQT_NO_DEBUG -I/<>/obj-x86_64-linux-gnu/src/openms > -I/<>/src/openms > -I/<>/obj-x86_64-linux-gnu/src/openms/OpenMS_autogen/include > -I/<>/src/openms/include > -I/<>/obj-x86_64-linux-gnu/src/openms/include -isystem /usr/lib > -isystem /usr/lib/x86_64-linux-gnu/include -isystem > /<>/src/openms/thirdparty/evergreen/src -isystem > /usr/include/hdf5/serial -isystem /usr/include/libsvm -isystem > /usr/include/eigen3 -isystem /usr/include/libwildmagic -isystem > /<>/src/openswathalgo/include -isystem > /<>/obj-x86_64-linux-gnu/src/openswathalgo/include -isystem > /<>/src/openswathalgo/thirdparty/MIToolbox/include -isystem > /<>/src/openswathalgo/thirdparty/MIToolbox/src -isystem > /usr/include/x86_64-linux-gnu/qt5 -isystem > /usr/include/x86_64-linux-gnu/qt5/QtCore -isystem > /usr/lib/x86_64-linux-gnu/qt5/mkspecs/linux-g++ -isystem > /usr/include/x86_64-linux-gnu/qt5/QtNetwork -isystem > /<>/src/openms/thirdparty/eol-bspline -isystem > /<>/src/openms/thirdparty/IsoSpec -isystem > /<>/src/openms/thirdparty/json -g -O2 > -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat > -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2-O3 -DNDEBUG -fPIC > -fvisibility=hidden -fvisibility-inlines-hidden -Wall -Wextra > -Wno-non-virtual-dtor -Wno-unknown-pragmas -Wno-long-long > -Wno-unused-function -Wno-variadic-macros -fPIC -fopenmp -o > CMakeFiles/OpenMS.dir/source/DATASTRUCTURES/LPWrapper.cpp.o -c > /<>/src/openms/source/DATASTRUCTURES/LPWrapper.cpp > In file included from > /<>/src/openms/source/DATASTRUCTURES/LPWrapper.cpp:63: > /usr/include/glpk.h:36:16: error: using typedef-name ‘glp_prob’ after ‘struct’ >36 | typedef struct glp_prob glp_prob; > |^~~~ > In file included from > /<>/src/openms/source/DATASTRUCTURES/LPWrapper.cpp:37: > /<>/src/openms/include/OpenMS/DATASTRUCTURES/LPWrapper.h:58:3: > note: ‘glp_prob’ has a previous declaration here >58 | } glp_prob; > | ^~~~ > In file included from > /<>/src/openms/source/DATASTRUCTURES/LPWrapper.cpp:63: > /usr/include/glpk.h:36:25: error: conflicting declaration ‘typedef int > glp_prob’ >36 | typedef struct glp_prob glp_prob; > | ^~~~ > In file included from > /<>/src/openms/source/DATASTRUCTURES/LPWrapper.cpp:37: > /<>/src/openms/include/OpenMS/DATASTRUCTURES/LPWrapper.h:58:3: > note: previous declaration as ‘typedef struct glp_prob glp_prob’ >58 | } glp_prob; > | ^~~~ > /<>/src/openms/source/DATASTRUCTURES/LPWrapper.cpp: In member > function ‘void OpenMS::LPWrapper::readProblem(const OpenMS::String&, const > OpenMS::String&)’: > /<>/src/openms/source/DATASTRUCTURES/LPWrapper.cpp:472:69: > warning: unused parameter ‘format’ [-Wunused-parameter] > 472 | void LPWrapper::readProblem(const String& filename, const String& > format) // format=(LP,MPS,GLPK) > | > ~~^~ > /<>/src/openms/source/DATASTRUCTURES/LPWrapper.cpp: In member > function ‘OpenMS::Int > OpenMS::LPWrapper::solve(OpenMS::LPWrapper::SolverParam&, OpenMS::Size)’: > /<>/src/openms/source/DATASTRUCTURES/LPWrapper.cpp:529:37: > warning: unused parameter ‘solver_param’ [-Wunused-parameter] > 529 | Int LPWrapper::solve(SolverParam& solver_param, const Size > |~^~~~ > make[5]: *** [src/openms/CMakeFiles/OpenMS.dir/build.make:1168: > src/openms/CMakeFiles/OpenMS.dir/source/DATASTRUCTURES/LPWrapper.cpp.o] Error > 1 The full build log is available from: http://qa-logs.debian.net/2020/12/26/openms_2.6.0+cleaned1-1_unstable.log A list of current common problems and possible solutions is available at
Processed: tagging 976366
Processing commands for cont...@bugs.debian.org: > tags 976366 + fixed-upstream Bug #976366 [ckb-next] Upgrade to 247 broke keyboard input on Wayland session Bug #977506 [ckb-next] ckb-next: Installation of ckb-next renders keyboard unusable Added tag(s) fixed-upstream. Added tag(s) fixed-upstream. > thanks Stopping processing here. Please contact me if you need assistance. -- 976366: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=976366 977506: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=977506 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#977230: marked as done (bagel FTBFS with Boost 1.74)
Your message dated Mon, 04 Jan 2021 21:48:38 + with message-id and subject line Bug#977230: fixed in boost1.74 1.74.0-7 has caused the Debian Bug report #977230, regarding bagel FTBFS with Boost 1.74 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.) -- 977230: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=977230 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: bagel Version: 1.2.2-1 Severity: serious Tags: ftbfs bullseye sid https://buildd.debian.org/status/fetch.php?pkg=bagel=amd64=1.2.2-1%2Bb2=1607773477=0 ... /usr/include/boost/property_tree/ptree_serialization.hpp: In function ‘void boost::property_tree::detail::load_children(Archive&, boost::property_tree::basic_ptree&)’: /usr/include/boost/property_tree/ptree_serialization.hpp:66:24: error: ‘library_version_type’ in namespace ‘bsa’ does not name a type 66 | const bsa::library_version_type library_version( |^~~~ ... --- End Message --- --- Begin Message --- Source: boost1.74 Source-Version: 1.74.0-7 Done: Anton Gladky We believe that the bug you reported is fixed in the latest version of boost1.74, 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 977...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Anton Gladky (supplier of updated boost1.74 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, 04 Jan 2021 22:17:05 +0100 Source: boost1.74 Architecture: source Version: 1.74.0-7 Distribution: unstable Urgency: medium Maintainer: Debian Boost Team Changed-By: Anton Gladky Closes: 977230 Changes: boost1.74 (1.74.0-7) unstable; urgency=medium . [ Dimitri John Ledkov ] * [8b3d244] Fix ptree_serialization failing to build with boost1.74. (Closes: #977230) Checksums-Sha1: 844c9219fa30dbbe31f2f0a0914edc81c91abdcd 9222 boost1.74_1.74.0-7.dsc 24d02762bdf9ef32cc557f34417825837697 367412 boost1.74_1.74.0-7.debian.tar.xz 77f30c2354afbebe9c1588f67365e5e2c8c21432 11205 boost1.74_1.74.0-7_source.buildinfo Checksums-Sha256: d8454b838ceec0b42eb0efdd32580ff2a3024b19360fc83c90765668fe93fc70 9222 boost1.74_1.74.0-7.dsc 8e4a11ac463fc159447765135f22c67d64e93d9d91d7baef448788b05e50a3d7 367412 boost1.74_1.74.0-7.debian.tar.xz bf0d47a2f017e7910bf579826c2c61677d738132a33ed515dc03308a348f8f81 11205 boost1.74_1.74.0-7_source.buildinfo Files: 870d5bac3830acc1661ca961c37f443e 9222 libs optional boost1.74_1.74.0-7.dsc bc8c873d62c28fa4d1da6faca589d02c 367412 libs optional boost1.74_1.74.0-7.debian.tar.xz 639e527459b5218fb078f9a0fc20a34d 11205 libs optional boost1.74_1.74.0-7_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEu71F6oGKuG/2fnKF0+Fzg8+n/wYFAl/zigEACgkQ0+Fzg8+n /wadFA//RM+S5uYD2DO1j8VogXpe75Sqjycvh5V7eajh3C8AX15Kx4WOJQTb9ZDe oQLpsn6vZfXMZl0PpqWC9UDIY3hpIjByEEbEEfowNKuObLK/aIhKzx461rkDEfzF OX+ER0zDyjpb2CWpP7TDvVqP/1EN7eAYfeTIDrnkbh4NvMdMS8xQVkk4iznL3iUn BCYaU62pJzpaoJXhhlk7XNgN0XKJBoK4gue7cC2RQqgYai1m4cXMIctwG9M2THI5 TMTxWJYXZRag66zKUweT9i0D/KgOkQiBa7ZOkiWl6nzkKurWObnK2SbdKN6Es+pZ bxqPpeMsRrdWey0aeHYibPc9pXA+lgU5jLLDiFRJ/ROVG3iji4SY+kAtnayIgOgz jaPvufuVNwluCmOm28khN2wsBAUEMFErUI+C4xTNE4aYhZ5qMcUPgglVl3q1BhE2 e3B0EKkZGeKWBTZEJ57Gc/JCRDMfD8hh8OEfn2LAr8hIESN4Xlfa25pF/dw8cfMz 5yaW7psgpBMEBxfm6Qm6mTkbsFe6WIub1eGSGANqWL8oME6My74P3NFhP8oNZOVB SXg09xsHEzPcqUIXBeD46wRWKwZUZQtBHPihRy0uMe7Eu5BBjVWIz8dGH95bCKK8 /0MiN6lleMugUyGBeZMHmVJ/B7YxOlrgIbjdaYU8jx6qF+G3c1c= =Si4M -END PGP SIGNATURE End Message ---
Bug#976565: marked as done (golang-github-disintegration-imaging: FTBFS on arm64,ppc64el (arch:all-only src pkg): dh_auto_test: error: cd obj-aarch64-linux-gnu && go test -vet=off -v -p 4 github.com/d
Your message dated Mon, 04 Jan 2021 21:20:44 + with message-id and subject line Bug#976565: fixed in golang-github-disintegration-imaging 1.6.2-1 has caused the Debian Bug report #976565, regarding golang-github-disintegration-imaging: FTBFS on arm64,ppc64el (arch:all-only src pkg): dh_auto_test: error: cd obj-aarch64-linux-gnu && go test -vet=off -v -p 4 github.com/disintegration/imaging returned exit code 1 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 976565: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=976565 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: golang-github-disintegration-imaging Version: 1.6.0+really1.6.0-1 Severity: serious Justification: FTBFS on arm64 Tags: bullseye sid ftbfs Usertags: ftbfs-20201205 ftbfs-bullseye Hi, During a rebuild of all packages in sid, your package failed to build on arm64 (I don't know if it also fails on amd64). Relevant part (hopefully): > debian/rules build > dh build --buildsystem=golang --with=golang >dh_update_autotools_config -O--buildsystem=golang >dh_autoreconf -O--buildsystem=golang >dh_auto_configure -O--buildsystem=golang >dh_auto_build -O--buildsystem=golang > cd obj-aarch64-linux-gnu && go install -trimpath -v -p 4 > github.com/disintegration/imaging > internal/unsafeheader > runtime/internal/sys > internal/cpu > internal/race > runtime/internal/math > runtime/internal/atomic > internal/bytealg > sync/atomic > unicode > unicode/utf8 > math/bits > runtime > image/color > math > internal/testlog > image/color/palette > internal/reflectlite > sync > sort > errors > io > strconv > internal/oserror > syscall > bytes > strings > reflect > hash > hash/adler32 > bufio > hash/crc32 > image > time > internal/syscall/unix > internal/syscall/execenv > image/internal/imageutil > image/draw > image/jpeg > internal/poll > encoding/binary > internal/fmtsort > os > golang.org/x/image/bmp > golang.org/x/image/ccitt > fmt > path/filepath > io/ioutil > golang.org/x/image/tiff/lzw > compress/lzw > compress/flate > image/gif > compress/zlib > image/png > golang.org/x/image/tiff > github.com/disintegration/imaging >dh_auto_test -O--buildsystem=golang > cd obj-aarch64-linux-gnu && go test -vet=off -v -p 4 > github.com/disintegration/imaging > === RUN TestGrayscale > === RUN TestGrayscale/Grayscale_3x3 > --- PASS: TestGrayscale (0.00s) > --- PASS: TestGrayscale/Grayscale_3x3 (0.00s) > === RUN TestInvert > === RUN TestInvert/Invert_3x3 > --- PASS: TestInvert (0.00s) > --- PASS: TestInvert/Invert_3x3 (0.00s) > === RUN TestAdjustSaturation > === RUN TestAdjustSaturation/AdjustSaturation_3x3_10 > === RUN TestAdjustSaturation/AdjustSaturation_3x3_100 > === RUN TestAdjustSaturation/AdjustSaturation_3x3_-10 > === RUN TestAdjustSaturation/AdjustSaturation_3x3_-100 > === RUN TestAdjustSaturation/AdjustSaturation_3x3_0 > --- PASS: TestAdjustSaturation (0.00s) > --- PASS: TestAdjustSaturation/AdjustSaturation_3x3_10 (0.00s) > --- PASS: TestAdjustSaturation/AdjustSaturation_3x3_100 (0.00s) > --- PASS: TestAdjustSaturation/AdjustSaturation_3x3_-10 (0.00s) > --- PASS: TestAdjustSaturation/AdjustSaturation_3x3_-100 (0.00s) > --- PASS: TestAdjustSaturation/AdjustSaturation_3x3_0 (0.00s) > === RUN TestAdjustSaturationGolden > adjust_test.go:238: resulting image differs from golden: > out_saturation_m30.png > adjust_test.go:238: resulting image differs from golden: > out_saturation_p30.png > --- FAIL: TestAdjustSaturationGolden (0.01s) > === RUN TestAdjustContrast > === RUN TestAdjustContrast/AdjustContrast_3x3_10 > === RUN TestAdjustContrast/AdjustContrast_3x3_100 > === RUN TestAdjustContrast/AdjustContrast_3x3_-10 > === RUN TestAdjustContrast/AdjustContrast_3x3_-100 > === RUN TestAdjustContrast/AdjustContrast_3x3_0 > --- PASS: TestAdjustContrast (0.00s) > --- PASS: TestAdjustContrast/AdjustContrast_3x3_10 (0.00s) > --- PASS: TestAdjustContrast/AdjustContrast_3x3_100 (0.00s) > --- PASS: TestAdjustContrast/AdjustContrast_3x3_-10 (0.00s) > --- PASS: TestAdjustContrast/AdjustContrast_3x3_-100 (0.00s) > --- PASS: TestAdjustContrast/AdjustContrast_3x3_0 (0.00s) > === RUN TestAdjustContrastGolden > --- PASS: TestAdjustContrastGolden (0.01s) > === RUN TestAdjustBrightness > === RUN TestAdjustBrightness/AdjustBrightness_3x3_10 > === RUN TestAdjustBrightness/AdjustBrightness_3x3_100 > === RUN TestAdjustBrightness/AdjustBrightness_3x3_-10 > === RUN TestAdjustBrightness/AdjustBrightness_3x3_-100 > === RUN
Processed: tag patch
Processing commands for cont...@bugs.debian.org: > tags 974428 patch Bug #974428 [telnetd] in.telnetd crashes on running Nessus security scan Added tag(s) patch. > thanks Stopping processing here. Please contact me if you need assistance. -- 974428: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=974428 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#859926: speechd-up: fails to install
Hi Samuel, On 18-10-2020 18:05, Samuel Thibault wrote: > Sorry for not answering before, I'm terribly busy atm. Just giving a > quick answer, a proper answer will need more time. Did you have any chance to give this more thought? The bullseye freeze is around the corner. [...] >> @Samuel, what do you think of the patch. It's way to involved for me to >> judge, but it claims to solve a long standing RC issue. > > Yes, the "pulse,alsa" user-visible change seems interesting. But the > implementation seems fragile to me: looking in /proc content is deemed > to break at some point or another. We've been struck hard by such kind > of tinkering in the past, I'd rather not see that happen again :/ Ack. @Dennis, feel free to comment on this too. Paul OpenPGP_signature Description: OpenPGP digital signature
Bug#979229: marked as done (libpcap0.8-dev: missing dependency on libdbus-1-dev causes build failures)
Your message dated Mon, 04 Jan 2021 20:17:21 + with message-id and subject line Bug#979229: fixed in libpcap 1.10.0-2 has caused the Debian Bug report #979229, regarding libpcap0.8-dev: missing dependency on libdbus-1-dev causes build failures 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.) -- 979229: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=979229 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: libpcap0.8-dev Version: 1.9.1-4 Severity: serious Justification: FTBFS on reverse dependency Tags: bullseye sid ftbfs patch Usertags: ftbfs-20201226 ftbfs-bullseye Blocks: 978248 Dear Maintainer(s), libpcap0.8-dev sets "Libs.private: -ldbus-1" in its pkg-config file, but it does not have a dependency on libdbus-1-dev, causing a build failure in reverse dependencies that use pkg-config --static (or macro variations thereof). Please consider adding this dependency, so that everything works out of the box. Found while rebuilding src:openvswitch. I've opened a MR on Salsa which does just this: https://salsa.debian.org/rfrancoise/libpcap/-/merge_requests/2 Thank you! Kind regards, Luca Boccassi --- End Message --- --- Begin Message --- Source: libpcap Source-Version: 1.10.0-2 Done: Romain Francoise We believe that the bug you reported is fixed in the latest version of libpcap, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 979...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Romain Francoise (supplier of updated libpcap 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, 04 Jan 2021 20:39:53 +0100 Source: libpcap Architecture: source Version: 1.10.0-2 Distribution: unstable Urgency: medium Maintainer: Romain Francoise Changed-By: Romain Francoise Closes: 979229 Changes: libpcap (1.10.0-2) unstable; urgency=medium . * Update Hurd support to use the new internal API, fixing FTBFS. * Add missing dependency on libdbus-1-dev to libpcap0.8-dev, patch by Luca Boccassi (closes: #979229). * Bump Standards-Version to 4.5.1. Checksums-Sha1: abbbafe87c37387c5301fd66cd84232a8b4f84e1 2377 libpcap_1.10.0-2.dsc 621fb305594305d14f0646e160ffbbfc97c0b622 19264 libpcap_1.10.0-2.debian.tar.xz b1e731ee7aeabed172842b1d8a31b8d2ff9d88a2 5756 libpcap_1.10.0-2_source.buildinfo Checksums-Sha256: b9197ca79e47f11c118d9572472d5126d1341a91a101a53577cca29e640c0b82 2377 libpcap_1.10.0-2.dsc 84f9ce9d845d957bd9c170ea5bb2bbf46bcb7050371aee16499585066cce6cc9 19264 libpcap_1.10.0-2.debian.tar.xz c7fb68dba0cd0baaef7707b8388267b3a8425a7d31c4ed75d0f83f2c406c2d8e 5756 libpcap_1.10.0-2_source.buildinfo Files: 43d806f3968b2f7f3400b3452c1c94f9 2377 devel optional libpcap_1.10.0-2.dsc e53d1cd1f1cba5fe7f6f193d64269248 19264 devel optional libpcap_1.10.0-2.debian.tar.xz 512378224eadcba8f67d79f91b4878ae 5756 devel optional libpcap_1.10.0-2_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEvjSXQsqYfs1+d+QtrRX0NfBfli0FAl/zcFUACgkQrRX0NfBf li05TRAAjCVgdBEZ1UYPM/Om2JcgBE7wx3W8y6Sst2nvYvzMwKrkCWu7AX0qLraR Y59JMNMHU00AUTXrRbwDsnINn7ZuJOeTG7z1lkBaHDv2ybxMpABr4k7cQQQyBqjT HhBSQ5i8jcwlKnnP+ug94AD/yAd+DSXxE7KWSbRyJvm2WgLJxfOP0CPJumbms0k0 rKwgW/bS5irKxpImEEMCxjf3m4bejnXmDumi2gD8h87k89Bm52sp6mVGTW2m2HHW H1VasG8FbRvXVPCehbdOykr4ZIiLWD+kugWV55VrMogNvaR28/lJorEy8c2AiagR SnREWqvfzgywhgB2aeVQF+cS0IgxTRiyMZkZPTnuAlEXdEiuMwwDJUi344s4NyjU n0dBh6qeYmEIyshe5U1hyq16NzrjMYHLv/EVNXNn2oKH75n5pKNtICA2fKKSSCKC +k6g1J+U0t3syyVmjyY+IfKqTmjtX3C2VFY9yAkAGvTxuW8RbeRFYQPFtveiEzJe 3ziBnGbTTK95ufSoPxLwlIJhJo4JjHTHlOCcvOnlUbqjvT4UEydqrAxqd10k3kP1 L25yTPqSy2JuoplsJmsd8QurxL7sBgau6YbNf8l/hatA6n+X9x7WQRyBnFewpdjr 9Gt9qsIknkqYHrHMI58H2n8BSdvqFD7zfHafmd7hDJVZv/YS6Qk= =S3se -END PGP SIGNATURE End Message ---
Bug#957603: marked as done (netplan.io: ftbfs with GCC-10)
Your message dated Mon, 04 Jan 2021 19:48:55 +
with message-id
and subject line Bug#957603: fixed in netplan.io 0.101-1
has caused the Debian Bug report #957603,
regarding netplan.io: ftbfs with GCC-10
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
957603: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=957603
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:netplan.io
Version: 0.98-2
Severity: normal
Tags: sid bullseye
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-10
Please keep this issue open in the bug tracker for the package it
was filed for. If a fix in another package is required, please
file a bug for the other package (or clone), and add a block in this
package. Please keep the issue open until the package can be built in
a follow-up test rebuild.
The package fails to build in a test rebuild on at least amd64 with
gcc-10/g++-10, but succeeds to build with gcc-9/g++-9. The
severity of this report will be raised before the bullseye release,
so nothing has to be done for the buster release.
The full build log can be found at:
http://people.debian.org/~doko/logs/gcc10-20200225/netplan.io_0.98-2_unstable_gcc10.log
The last lines of the build log are at the end of this report.
To build with GCC 10, either set CC=gcc-10 CXX=g++-10 explicitly,
or install the gcc, g++, gfortran, ... packages from experimental.
apt-get -t=experimental install g++
Common build failures are new warnings resulting in build failures with
-Werror turned on, or new/dropped symbols in Debian symbols files.
For other C/C++ related build failures see the porting guide at
http://gcc.gnu.org/gcc-10/porting_to.html
[...]
dpkg-buildpackage
-
Command: dpkg-buildpackage -us -uc -b -rfakeroot
dpkg-buildpackage: info: source package netplan.io
dpkg-buildpackage: info: source version 0.98-2
dpkg-buildpackage: info: source distribution unstable
dpkg-buildpackage: info: source changed by Andrej Shadura
dpkg-source --before-build .
dpkg-buildpackage: info: host architecture amd64
fakeroot debian/rules clean
dh clean
dh_auto_clean
make -j4 clean
make[1]: Entering directory '/<>'
rm -f netplan/_features.py src/_features.h
rm -f generate doc/*.html doc/*.[1-9]
rm -f netplan-dbus dbus/*.service
rm -f *.gcda *.gcno generate.info
rm -rf test-coverage .coverage
make[1]: Leaving directory '/<>'
dh_clean
debian/rules build
dh build
dh_update_autotools_config
dh_autoreconf
dh_auto_configure
dh_auto_build
make -j4 "INSTALL=install --strip-program=true"
make[1]: Entering directory '/<>'
echo "# Generated file" > netplan/_features.py
cc -std=c99 -D_XOPEN_SOURCE=500 -DSBINDIR=\"/usr/sbin\" -Wall -Werror -g -O2
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat
-Werror=format-security -Wl,-z,relro -o generate src/generate.c src/parse.c
src/util.c src/networkd.c src/nm.c src/validation.c src/error.c `pkg-config
--cflags --libs glib-2.0 gio-2.0 yaml-0.1 uuid`
printf "#include \nstatic const char *feature_flags[]
__attribute__((__unused__)) = {\n" > src/_features.h
echo "NETPLAN_FEATURE_FLAGS = [" >> netplan/_features.py
sed -e "s#@ROOTLIBEXECDIR@#/lib#" dbus/io.netplan.Netplan.service.in >
dbus/io.netplan.Netplan.service
awk 'match ($0, /netplan-feature:.*/ ) { $0=substr($0, RSTART, RLENGTH); print
"\""$2"\"," }' src/generate.c src/error.c src/nm.h src/networkd.h
src/validation.c src/nm.c src/networkd.c src/dbus.c src/parse.h src/util.h
src/validation.h src/parse.c src/util.c src/error.h >> src/_features.h
awk 'match ($0, /netplan-feature:.*/ ) { $0=substr($0, RSTART, RLENGTH); print
"\""$2"\"," }' src/generate.c src/error.c src/nm.h src/networkd.h
src/validation.c src/nm.c src/networkd.c src/dbus.c src/parse.h src/util.h
src/validation.h src/parse.c src/util.c src/error.h >> netplan/_features.py
pandoc -s --toc -o doc/netplan.html doc/netplan.md
echo "NULL, };" >> src/_features.h
echo "]" >> netplan/_features.py
pandoc -s -o doc/netplan.5 doc/manpage-header.md doc/netplan.md
doc/manpage-footer.md
pandoc -s -o doc/netplan-generate.8 doc/netplan-generate.md
pandoc -s -o doc/netplan-apply.8 doc/netplan-apply.md
pandoc -s -o doc/netplan-try.8 doc/netplan-try.md
cc -std=c99 -D_XOPEN_SOURCE=500 -DSBINDIR=\"/usr/sbin\" -Wall -Werror -g -O2
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat
-Werror=format-security -Wl,-z,relro -o netplan-dbus src/dbus.c src/_features.h
`pkg-config --cflags --libs libsystemd glib-2.0`
[WARNING] This document format requires a nonempty element.
Please specify either 'title' or
Processed: src:olive-editor: fails to migrate to testing for too long: FTBFS on arm64
Processing control commands:
> close -1 20200620-2
Bug #979272 [src:olive-editor] src:olive-editor: fails to migrate to testing
for too long: FTBFS on arm64
Marked as fixed in versions olive-editor/20200620-2.
Bug #979272 [src:olive-editor] src:olive-editor: fails to migrate to testing
for too long: FTBFS on arm64
Marked Bug as done
> block -1 by 976515
Bug #979272 {Done: Paul Gevers } [src:olive-editor]
src:olive-editor: fails to migrate to testing for too long: FTBFS on arm64
979272 was not blocked by any bugs.
979272 was not blocking any bugs.
Added blocking bug(s) of 979272: 976515
--
979272: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=979272
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#979272: src:olive-editor: fails to migrate to testing for too long: FTBFS on arm64
Source: olive-editor Version: 20200528-1 Severity: serious Control: close -1 20200620-2 Tags: sid bullseye User: release.debian@packages.debian.org Usertags: out-of-sync Control: block -1 by 976515 Dear maintainer(s), As recently announced [1], the Release Team now considers packages that are out-of-sync between testing and unstable for more than 60 days as having a Release Critical bug in testing. Your package src:olive-editor in its current version in unstable has been trying to migrate for 60 days [2]. Hence, I am filing this bug. If a package is out of sync between unstable and testing for a longer period, this usually means that bugs in the package in testing cannot be fixed via unstable. Additionally, blocked packages can have impact on other packages, which makes preparing for the release more difficult. Finally, it often exposes issues with the package and/or its (reverse-)dependencies. We expect maintainers to fix issues that hamper the migration of their package in a timely manner. This bug will trigger auto-removal when appropriate. As with all new bugs, there will be at least 30 days before the package is auto-removed. I have immediately closed this bug with the version in unstable, so if that version or a later version migrates, this bug will no longer affect testing. I have also tagged this bug to only affect sid and bullseye, so it doesn't affect (old-)stable. If you believe your package is unable to migrate to testing due to issues beyond your control, don't hesitate to contact the Release Team. Paul [1] https://lists.debian.org/debian-devel-announce/2020/02/msg5.html [2] https://qa.debian.org/excuses.php?package=olive-editor OpenPGP_signature Description: OpenPGP digital signature
Bug#943695: didjvu: FTBFS: ERROR: tests.test_timestamp.test_timezones
Hi. Because this package was orphaned (due to retirement of Daniel) and not even present in testing or unstable, I went ahead and uploaded a fix for stable. Debdiff attached. Thanks. diff -Nru didjvu-0.8.2/debian/changelog didjvu-0.8.2/debian/changelog --- didjvu-0.8.2/debian/changelog 2019-02-27 05:34:17.0 +0100 +++ didjvu-0.8.2/debian/changelog 2021-01-04 20:11:00.0 +0100 @@ -1,3 +1,10 @@ +didjvu (0.8.2-2+deb10u1) buster; urgency=medium + + * Add missing build-dependency on tzdata. Closes: #943695. + * Package is orphaned, set Maintainer to "Debian QA Group". + + -- Santiago Vila Mon, 04 Jan 2021 20:11:00 +0100 + didjvu (0.8.2-2) unstable; urgency=medium * drop python-libxmp from deps throughout (Closes: #921747). diff -Nru didjvu-0.8.2/debian/control didjvu-0.8.2/debian/control --- didjvu-0.8.2/debian/control 2019-02-27 05:29:59.0 +0100 +++ didjvu-0.8.2/debian/control 2021-01-04 20:00:00.0 +0100 @@ -1,5 +1,5 @@ Source: didjvu -Maintainer: Daniel Stender +Maintainer: Debian QA Group Uploaders: Python Applications Packaging Team Section: graphics @@ -14,7 +14,8 @@ python-gamera, gir1.2-gexiv2-0.10 (>= 0.10.3), python-gi, python-nose, - python-pil + python-pil, + tzdata Standards-Version: 4.1.3 Homepage: http://jwilk.net/software/didjvu Vcs-Git: https://salsa.debian.org/python-team/applications/didjvu.git
Bug#979270: python-rfc6555: Requires network access during build
Source: python-rfc6555 Version: 0.0~git20190913.1a181b4-2 Severity: serious Justification: Policy 4.9 X-Debbugs-Cc: lo...@ubuntu.com Hi, python-rfc6555 currently requires network access during build for some of its tests, which causes the build to fail in Ubuntu [1] (and reproducible builds [2]) and is a violation of Debian policy. Please look into skipping/adjusting these tests. Thanks, Logan
Bug#979232: lighttpd: does not start with media-types 1.1.0
On Mon, Jan 04, 2021 at 11:23:48AM -0300, Antonio Terceiro wrote: > Package: lighttpd > Version: 1.4.57-1 > Severity: grave > Justification: renders package unusable > > Dear Maintainer, > > After media-types has been upgraded to 1.1.0, lighttpd fails to start, > complaining about duplicated media types. > > jan 04 11:17:27 lemur systemd[1]: Starting Lighttpd Daemon... > jan 04 11:17:27 lemur lighttpd[22434]: Duplicate mimetype: '.png' => > 'image/vnd.mozilla.apng' (already have 'image/png'), merging to > 'application/octet-stream' > jan 04 11:17:27 lemur lighttpd[22434]: Duplicate mimetype: '.pcx' => > 'image/vnd.zbrush.pcx' (already have 'image/pcx'), merging to > 'application/octet-stream' > jan 04 11:17:28 lemur lighttpd[22430]: Error: duplicate array-key: .pgb. > Please get rid of the duplicate entry. > jan 04 11:17:28 lemur lighttpd[22430]: 2021-01-04 11:17:27: > (configfile.c.1966) source: /usr/share/lighttpd/create-mime.conf.pl line: 495 > pos: 8 parser failed somehow near here: (COMMA) > jan 04 11:17:28 lemur lighttpd[22430]: 2021-01-04 11:17:27: > (configfile.c.1966) source: /etc/lighttpd/lighttpd.conf line: 48 pos: 8 > parser failed somehow near here: (EOL) [...] > The new /etc/mime.types has both lowercase and uppercase file extensions > for the same mime type: > > $ grep pgb /etc/mime.types > image/vnd.globalgraphics.pgb PGB pgb > > I'm copying the media-types maintainers just so that they know about > this, but it seems to me that this should be handled properly in > lighttpd. Thank you for reporting this. Yes, lighttpd could handle this better and I have just pushed a patch to salsa.debian.org/debian/lighttpd master branch. An update to lighttpd is scheduled to be released to testing some time later next week. However, I also urge the media-types maintainers to review their change. Of the 800+ lines in /etc/mime.types, only this new addition lists both uppercase and lowercase for the same extension. It is unnecessary and wasteful. If they are going to duplicate uppercase and lowercase for pgb, then they should do so for all extensions, e.g. jpg and JPG, png and PNG, etc One quickly realizes that this is excessive and wasteful and not the convention in /etc/mime.types. Therefore 'image/vnd.globalgraphics.pgb PGB pgb' is the outlier that should be changed to conform to the existing conventions. Cheers, Glenn
Bug#979231: the new mailcap entry breaks mutt
On Jan 04, Vagrant Cascadian wrote: > Removal sounds like a reasonable fix as well, although there are a > handful of reverse dependencies of various forms: > > $ apt rdepends a2ps > a2ps > Reverse Depends: > Depends: apsfilter QA > Recommends: magicfilter QA > Suggests: jed-extra barely related > Depends: ifhp QA > Suggests: gabedit I am not sure about why it depends on a2ps. > Recommends: foomatic-filters Yet anoter filter. ifhp looks like something very obsolete, and the other programs probably could easily replace a2ps with paps. Maybe apsfilter and magicfilter could be replaced by foomatic-filters as well, which is maintained. -- ciao, Marco signature.asc Description: PGP signature
Bug#979231: the new mailcap entry breaks mutt
On 2021-01-04, Marco d'Itri wrote: > The recent NMU of a2ps converted the package to dh, and this enabled > dh_installmime which was present in debian/rules but commented. > > The installed file adds to mailcap an entry for "text/plain", which > breaks mutt and probably other software in fun ways. Hrm. I noticed it was newly added compared to the old version, but figured it was a good thing as an earlier version *attempted* to add it, apparently unsuccessfully... > Solution: override dh_installmime to stop installing the file until > somebody will figure out a better plan. Indeed, that sounds like a simple fix, since it has not shipped the file for quite some time. > It may be worth considering removing a2ps from the archive since its > last upstream release and non-NMU uploads were from 2008 and I am being > told that it does not support UTF-8. > paps has been mentioned as a replacement. Removal sounds like a reasonable fix as well, although there are a handful of reverse dependencies of various forms: $ apt rdepends a2ps a2ps Reverse Depends: Depends: apsfilter Recommends: magicfilter Suggests: jed-extra Depends: ifhp Suggests: gabedit Recommends: foomatic-filters Recommends: magicfilter Suggests: jed-extra Depends: ifhp Recommends: gpr Suggests: gabedit Recommends: foomatic-filters live well, vagrant signature.asc Description: PGP signature
Bug#957647: marked as done (osdsh: ftbfs with GCC-10)
Your message dated Mon, 04 Jan 2021 18:51:23 + with message-id and subject line Bug#957647: fixed in osdsh 0.7.0-10.4 has caused the Debian Bug report #957647, regarding osdsh: ftbfs with GCC-10 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 957647: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=957647 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:osdsh Version: 0.7.0-10.3 Severity: normal Tags: sid bullseye User: debian-...@lists.debian.org Usertags: ftbfs-gcc-10 Please keep this issue open in the bug tracker for the package it was filed for. If a fix in another package is required, please file a bug for the other package (or clone), and add a block in this package. Please keep the issue open until the package can be built in a follow-up test rebuild. The package fails to build in a test rebuild on at least amd64 with gcc-10/g++-10, but succeeds to build with gcc-9/g++-9. The severity of this report will be raised before the bullseye release, so nothing has to be done for the buster release. The full build log can be found at: http://people.debian.org/~doko/logs/gcc10-20200225/osdsh_0.7.0-10.3_unstable_gcc10.log The last lines of the build log are at the end of this report. To build with GCC 10, either set CC=gcc-10 CXX=g++-10 explicitly, or install the gcc, g++, gfortran, ... packages from experimental. apt-get -t=experimental install g++ Common build failures are new warnings resulting in build failures with -Werror turned on, or new/dropped symbols in Debian symbols files. For other C/C++ related build failures see the porting guide at http://gcc.gnu.org/gcc-10/porting_to.html [...] 42 | if (strcmp(command, "")==0) | ^~ osdctl.c:45:48: warning: implicit declaration of function ‘getuid’ [-Wimplicit-function-declaration] 45 | sprintf(fifo_file, "%s.%d", OSD_FIFO_PATH, getuid()); |^~ osdctl.c:55:2: warning: incompatible implicit declaration of built-in function ‘exit’ 55 | exit(1); | ^~~~ osdctl.c:55:2: note: include ‘’ or provide a declaration of ‘exit’ osdctl.c:60:2: warning: incompatible implicit declaration of built-in function ‘exit’ 60 | exit(1); | ^~~~ osdctl.c:60:2: note: include ‘’ or provide a declaration of ‘exit’ osdctl.c:67:2: warning: incompatible implicit declaration of built-in function ‘exit’ 67 | exit(1); | ^~~~ osdctl.c:67:2: note: include ‘’ or provide a declaration of ‘exit’ osdctl.c: In function ‘script_file’: osdctl.c:83:2: warning: incompatible implicit declaration of built-in function ‘exit’ 83 | exit(1); | ^~~~ osdctl.c:83:2: note: include ‘’ or provide a declaration of ‘exit’ osdctl.c: In function ‘main’: osdctl.c:118:6: warning: incompatible implicit declaration of built-in function ‘exit’ 118 | exit(0); | ^~~~ osdctl.c:118:6: note: include ‘’ or provide a declaration of ‘exit’ controlsh.c: In function ‘load_plugin’: controlsh.c:52:22: warning: cast to pointer from integer of different size [-Wint-to-pointer-cast] 52 | plugins[a].myname = (char *) info(); | ^ controlsh.c: In function ‘display_stuff’: controlsh.c:166:2: warning: implicit declaration of function ‘control_options’ [-Wimplicit-function-declaration] 166 | control_options(, arg_first, arg_secound); | ^~~ controlsh.c: In function ‘control_sh’: controlsh.c:213:2: warning: implicit declaration of function ‘initialize_osd’ [-Wimplicit-function-declaration] 213 | initialize_osd(); | ^~ controlsh.c:214:2: warning: implicit declaration of function ‘load_basic_plugins’ [-Wimplicit-function-declaration] 214 | load_basic_plugins(); | ^~ gcc -fPIC -c utils.c make[2]: Leaving directory '/<>/src/osdctl' gcc -c -O3 -rdynamic osdsh.c osdsh.c: In function ‘load_basic_plugins’: osdsh.c:119:6: warning: implicit declaration of function ‘load_plugin’ [-Wimplicit-function-declaration] 119 | a = load_plugin(file); | ^~~ osdsh.c: In function ‘main’: osdsh.c:158:5: warning: implicit declaration of function ‘set_defaults’ [-Wimplicit-function-declaration] 158 | set_defaults(); | ^~~~ osdsh.c:159:5: warning: implicit declaration of function ‘initialize_osd’ [-Wimplicit-function-declaration] 159 | initialize_osd(); | ^~ osdsh.c:195:6: warning: implicit declaration of function ‘control_sh’ [-Wimplicit-function-declaration] 195 | control_sh(NULL);
Bug#977069: marked as done (kombu FTBFS with pytest 6)
Your message dated Mon, 04 Jan 2021 18:33:44 +
with message-id
and subject line Bug#977069: fixed in kombu 5.0.2-3
has caused the Debian Bug report #977069,
regarding kombu FTBFS with pytest 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.)
--
977069: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=977069
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: kombu
Version: 5.0.2-2
Severity: important
User: pyt...@packages.debian.org
Usertags: pytest-v6
Hi,
kombu FTBFS with pytest 6 in experimental.
The error log below has more details.
> I: pybuild base:232: python3.9 setup.py test
> WARNING: Testing via this command is deprecated and will be removed in a
> future version. Users looking for a generic test entry point independent of
> test runner are encouraged to use tox.
> running test
> WARNING: The pip package is not available, falling back to EasyInstall for
> handling setup_requires/test_requires; this is deprecated and will be removed
> in a future version.
> Download error on https://pypi.org/simple/pytest/: [Errno 111] Connection
> refused -- Some packages may not be found!
> Download error on https://pypi.org/simple/: [Errno 111] Connection refused --
> Some packages may not be found!
> No local packages or working download links found for pytest<=5.3.5
> error: Could not find suitable distribution for
> Requirement.parse('pytest<=5.3.5')
> Searching for pytest<=5.3.5
> Reading https://pypi.org/simple/pytest/
> Couldn't retrieve index page for 'pytest'
> Scanning index of all packages (this may take a while)
> Reading https://pypi.org/simple/
> E: pybuild pybuild:353: test: plugin custom failed with: exit code=1:
> python3.9 setup.py test
> make[1]: Leaving directory '/<>'
> dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p 3.9
> --system=custom "--test-args={interpreter} setup.py test" returned exit code
> 13
> make[1]: *** [debian/rules:16: override_dh_auto_test] Error 25
> make: *** [debian/rules:6: binary] Error 2
> dpkg-buildpackage: error: debian/rules binary subprocess returned exit status
> 2
--- End Message ---
--- Begin Message ---
Source: kombu
Source-Version: 5.0.2-3
Done: Thomas Goirand
We believe that the bug you reported is fixed in the latest version of
kombu, 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 977...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Thomas Goirand (supplier of updated kombu package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Mon, 04 Jan 2021 19:08:48 +0100
Source: kombu
Architecture: source
Version: 5.0.2-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Team
Changed-By: Thomas Goirand
Closes: 977069
Changes:
kombu (5.0.2-3) unstable; urgency=medium
.
* Add patch: allow-any-version-of-pytest.patch (Closes: #977069).
Checksums-Sha1:
d36e56f63e5aca639d52f2065f4c86b70c61c113 2805 kombu_5.0.2-3.dsc
5afdfd766c78193cb3e097b168ccc938677ec23a 11088 kombu_5.0.2-3.debian.tar.xz
dfd14ea61d08dbbe60a5197fef778b771b743d63 8485 kombu_5.0.2-3_amd64.buildinfo
Checksums-Sha256:
b6a70da3f2bfdd38cd4ffd47802fca5cb67b7c8ef1b447024a6a55d85393afb3 2805
kombu_5.0.2-3.dsc
cf7d0543e3dd9c8107d41883939c31143b7dfb8af174f1f1121f42f7b360e2c1 11088
kombu_5.0.2-3.debian.tar.xz
d1d226c5c16d5eaf1a32f584c1f4904f373621dd49791eb3601ea88484bbd2a9 8485
kombu_5.0.2-3_amd64.buildinfo
Files:
ef672fc6dba45367a9b5090b02fc19d6 2805 python optional kombu_5.0.2-3.dsc
adb9d6be9385463d85eaae87e391e463 11088 python optional
kombu_5.0.2-3.debian.tar.xz
d48cfe3fe029a27dbd195fb6de2b240f 8485 python optional
kombu_5.0.2-3_amd64.buildinfo
-BEGIN PGP SIGNATURE-
iQIzBAEBCAAdFiEEoLGp81CJVhMOekJc1BatFaxrQ/4FAl/zWiAACgkQ1BatFaxr
Q/5hKw/+NMhCYRmGOVTjFxpwm+LlOf2l6p6YGEEdfyF6G+fdyX6JLgMb3kKYYyll
aVLPzHTFUqsDqUfsUDSEiOoW62tuVrQ//bexyPT9r2ZCHYdOc77MTV/+U5QPtWnl
I0G5tca5tLCgcwwn7+o3vIiRnEZQahsVaxdbGezhYdngSj2+3WnZoIEClamG079G
v6gBNPqO001Qi7tz9fGrEdcyI/6qoZl8wQvgZN+OTimm/8P903u6xNn3dklYeJ0I
9rq0/832OJEOohp18QBK/x2bRUIUV+KzreECrdIJs3nSROagZEafj0NySt+duopU
0IX3a4nikmiEI1V+98zO3tUaivTGslFyaUkRbikDQMbY5Am1zZxHq4PPwDri6gyW
Processed: Re: Bug#979041 closed by Debian FTP Masters (reply to Alastair McKinstry ) (Bug#979041: fixed in openmpi 4.1.0-4)
Processing commands for cont...@bugs.debian.org:
> reopen 979041
Bug #979041 {Done: Alastair McKinstry } [libopenmpi3]
libopempi3: aborts python code due to libfabric fork() issues
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
No longer marked as fixed in versions openmpi/4.1.0-4.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
979041: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=979041
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#979041: closed by Debian FTP Masters (reply to Alastair McKinstry ) (Bug#979041: fixed in openmpi 4.1.0-4)
reopen 979041 thanks Hi, On Mon, Jan 04, 2021 at 09:36:06AM +, Debian Bug Tracking System wrote: >* Fix for missing plugin mca_op_avx.so. Closes: #979041, #978496 This change fixes the mca_op_avx.so issues, but at least my testing shows this abort is still there when trying to run the gpaw autopkgtests with 4.1.0-4: > |A process has executed an operation involving a call > |to the fork() system call to create a child process. > | > |As a result, the libfabric EFA provider is operating in > |a condition that could result in memory corruption or > |other system errors. > | > |For the libfabric EFA provider to work safely when fork() > |is called, you will need to set the following environment > |variable: > | RDMAV_FORK_SAFE > | > |However, setting this environment variable can result in > |signficant performance impact to your application due to > |increased cost of memory registration. > | > |You may want to check with your application vendor to see > |if an application-level alternative (of not using fork) > |exists. > | > |Your job will now abort. Michael
Bug#977960: marked as done (dangling /usr/share/javascript/jquery/jquery.js symlink)
Your message dated Mon, 04 Jan 2021 18:19:00 + with message-id and subject line Bug#977960: fixed in node-jquery 3.5.1+dfsg+~3.5.5-5 has caused the Debian Bug report #977960, regarding dangling /usr/share/javascript/jquery/jquery.js symlink 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.) -- 977960: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=977960 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: libjs-jquery Version: 3.5.1+dfsg+~3.5.5-1 Severity: serious Tags: sid bullseye There's at least one dangling /usr/share/javascript/jquery/jquery.js symlink $ dpkg -S /usr/share/javascript/jquery/jquery.js libjs-jquery: /usr/share/javascript/jquery/jquery.js $ ls -l /usr/share/javascript/jquery/jquery.js lrwxrwxrwx 1 root root 34 Dec 22 08:27 /usr/share/javascript/jquery/jquery.js -> ../../nodejs/jquery/dist/jquery.js $ ls -lL /usr/share/javascript/jquery/jquery.js ls: cannot access '/usr/share/javascript/jquery/jquery.js': No such file or directory --- End Message --- --- Begin Message --- Source: node-jquery Source-Version: 3.5.1+dfsg+~3.5.5-5 Done: Xavier Guimard We believe that the bug you reported is fixed in the latest version of node-jquery, 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 977...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Xavier Guimard (supplier of updated node-jquery 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, 04 Jan 2021 19:00:09 +0100 Source: node-jquery Architecture: source Version: 3.5.1+dfsg+~3.5.5-5 Distribution: unstable Urgency: medium Maintainer: Debian Javascript Maintainers Changed-By: Xavier Guimard Closes: 977960 Changes: node-jquery (3.5.1+dfsg+~3.5.5-5) unstable; urgency=medium . * Team upload * Fix maintscript, thanks to Mattias Ellert (Closes: #977960) Checksums-Sha1: 1cdca2debe58395476ef4a9d40b04414ea13959a 2689 node-jquery_3.5.1+dfsg+~3.5.5-5.dsc e2c882f25a06501ab69116ef5ee4013c0e3362f1 5604 node-jquery_3.5.1+dfsg+~3.5.5-5.debian.tar.xz Checksums-Sha256: d0bd00e1ddabfb8d2e27257c87ef3a13f0b884d8d8b9dd744c1e793073c3b4c6 2689 node-jquery_3.5.1+dfsg+~3.5.5-5.dsc 6483b250b5d5311b00d8c71dee82c53e89741ce20a6e498dd4a56f1abdcbadec 5604 node-jquery_3.5.1+dfsg+~3.5.5-5.debian.tar.xz Files: 4c3fa0d6a747de2be9ae20fdc1b5a5fb 2689 javascript optional node-jquery_3.5.1+dfsg+~3.5.5-5.dsc 7bfb00b4f366256f4af711a441a258d6 5604 javascript optional node-jquery_3.5.1+dfsg+~3.5.5-5.debian.tar.xz -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEAN/li4tVV3nRAF7J9tdMp8mZ7ukFAl/zV/MACgkQ9tdMp8mZ 7uk9Yg//XhiXGPvQcUs+XZ6tSQ13//aErFvtDugkbtnRodiPtdpspLXmBfG6rrhg Bdsz8LJ7bNh6qk6i49aJ2h0n+xSWCecclhyuDSmlYcYHYYH2W4V+XjRllO71YG/n AfM9DNteERFbsXd2iBTw7h6vlt52d7xefQIPNqJwDxi2iufPftu5w6b58kZjF3cJ LtGBKg2guV7Qk/K9bG++L8Bx1svc5L6iYyoiTjnFxxldbdUtBpXXDVx++HtTNwwt 8MgBA5MohhrCgUIH0J9KOHcYySsSfnWiGlKkg5mwCTTCyAch46xRN+3SMbEdayym kvh7+woMWWtz2QCCsLL59nEVbdVhUVFi0O945JL//+Ff9JTN0izPzOF8MbJNKZjq jTV9v8dDqk1k4kuBdTCSBaHpo5rXeatfdpuQuQm/xo2UGwjmLp6YibD8SlYO5wnJ bKF0htemkH2N+9Bnp79vPKDjGOLzirNF9AfhvIxOiNLcuE/orULe9Z73ODTWkavP oHzRbKlz2GHg7Uam58nsylPPR1mO9eAuAHZPjhsFhottDnl4GVXXycUkWyjGeeWy 62pvnqpdeR1EInrE/S/b1uEkCaRhPnWLMmsqKyCMbtGgmpznkQ0h+r3Xjs7+MvdU sKHzLxrbNg9fq+E5lqSkHHwXyVsLDjkNGBm7H1M/Ie86iI+Q+DY= =dKFg -END PGP SIGNATURE End Message ---
Bug#977069: marked as pending in kombu
Control: tag -1 pending Hello, Bug #977069 in kombu 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/python-team/packages/kombu/-/commit/d04161316096e1743d37f44929bb1ad538cd8d46 Add patch: allow-any-version-of-pytest.patch (Closes: #977069). (this message was generated automatically) -- Greetings https://bugs.debian.org/977069
Processed: Bug#977069 marked as pending in kombu
Processing control commands: > tag -1 pending Bug #977069 [src:kombu] kombu FTBFS with pytest 6 Added tag(s) pending. -- 977069: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=977069 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#975774: micropython FTBFS: test failures
Dear Maintainer,
I've added some print statements [1] in 'tests/run-tests' to have
more meaningful context for failed tests:
[...]
EXPECTED: b'True\nTrue\n'
REAL: b'True\nTrue\nValueError\n'
FAIL extmod/urandom_basic.py
[...]
EXPECTED: b'CPYTHON3 CRASH'
REAL: b'pkg __name__: pkg7\npkg __name__: pkg7.subpkg1\npkg __name__:
pkg7.subpkg1.subpkg2\nmod1\nmod2\nmod1.foo\nmod2.bar\nValueError\n'
FAIL import/import_pkg7.py
[...]
Kind Regards
[1]
Index: micropython-1.12/tests/run-tests
===
--- micropython-1.12.orig/tests/run-tests
+++ micropython-1.12/tests/run-tests
@@ -501,6 +501,8 @@ def run_tests(pyb, tests, args, base_pat
rm_f(filename_expected)
rm_f(filename_mupy)
else:
+ print("EXPECTED: ", output_expected)
+ print("REAL: ", output_mupy)
with open(filename_expected, "wb") as f:
f.write(output_expected)
with open(filename_mupy, "wb") as f:
Processed: Re: Bug#978367: libmaa: FTBFS: bmake[2]: "/usr/share/mk-configure/mk/mkc_imp.platform.sys.mk" line 112: 'Settings for gcc-10.2.1 is not available, run "mkc_compiler_settings" utility'
Processing control commands:
> reassign -1 mk-configure 0.35.0-1
Bug #978367 [src:libmaa] libmaa: FTBFS: bmake[2]:
"/usr/share/mk-configure/mk/mkc_imp.platform.sys.mk" line 112: 'Settings for
gcc-10.2.1 is not available, run "mkc_compiler_settings" utility'
Bug reassigned from package 'src:libmaa' to 'mk-configure'.
No longer marked as found in versions libmaa/1.4.7-1.
Ignoring request to alter fixed versions of bug #978367 to the same values
previously set
Bug #978367 [mk-configure] libmaa: FTBFS: bmake[2]:
"/usr/share/mk-configure/mk/mkc_imp.platform.sys.mk" line 112: 'Settings for
gcc-10.2.1 is not available, run "mkc_compiler_settings" utility'
Marked as found in versions mk-configure/0.35.0-1.
> forcemerge 977908 -1
Bug #977908 {Done: Andrej Shadura } [mk-configure]
mk-configure: Fails with 'Settings for gcc-10.2.1 is not available'
Bug #978271 {Done: Andrej Shadura } [mk-configure]
inputplug: FTBFS: dpkg-buildpackage: error: dpkg-source -b . subprocess
returned exit status 2
Bug #978376 {Done: Alexander Ponyatikh } [mk-configure]
paexec: FTBFS: bmake[2]: "/usr/share/mk-configure/mk/mkc_imp.platform.sys.mk"
line 112: 'Settings for gcc-10.2.1 is not available, run
"mkc_compiler_settings" utility'
Bug #978387 {Done: Andrej Shadura } [mk-configure] runawk:
FTBFS: bmake[2]: "/usr/share/mk-configure/mk/mkc_imp.platform.sys.mk" line 112:
'Settings for gcc-10.2.1 is not available, run "mkc_compiler_settings" utility'
Bug #978367 [mk-configure] libmaa: FTBFS: bmake[2]:
"/usr/share/mk-configure/mk/mkc_imp.platform.sys.mk" line 112: 'Settings for
gcc-10.2.1 is not available, run "mkc_compiler_settings" utility'
Marked Bug as done
Marked as fixed in versions mk-configure/0.35.really.0.33.0-1.
Bug #978271 {Done: Andrej Shadura } [mk-configure]
inputplug: FTBFS: dpkg-buildpackage: error: dpkg-source -b . subprocess
returned exit status 2
Bug #978376 {Done: Alexander Ponyatikh } [mk-configure]
paexec: FTBFS: bmake[2]: "/usr/share/mk-configure/mk/mkc_imp.platform.sys.mk"
line 112: 'Settings for gcc-10.2.1 is not available, run
"mkc_compiler_settings" utility'
Bug #978387 {Done: Andrej Shadura } [mk-configure] runawk:
FTBFS: bmake[2]: "/usr/share/mk-configure/mk/mkc_imp.platform.sys.mk" line 112:
'Settings for gcc-10.2.1 is not available, run "mkc_compiler_settings" utility'
Merged 977908 978271 978367 978376 978387
--
977908: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=977908
978271: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=978271
978367: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=978367
978376: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=978376
978387: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=978387
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#978367: libmaa: FTBFS: bmake[2]: "/usr/share/mk-configure/mk/mkc_imp.platform.sys.mk" line 112: 'Settings for gcc-10.2.1 is not available, run "mkc_compiler_settings" utility'
Control: reassign -1 mk-configure 0.35.0-1 Control: forcemerge 977908 -1 On 2020-12-26 23:03 +0100, Lucas Nussbaum wrote: > Source: libmaa > Version: 1.4.7-1 > Severity: serious > Justification: FTBFS on amd64 > Tags: bullseye sid ftbfs > Usertags: ftbfs-20201226 ftbfs-bullseye > > Hi, > > During a rebuild of all packages in sid, your package failed to build > on amd64. > [...] >> checking C compiler type... gcc 10.2.1 >> bmake[2]: "/usr/share/mk-configure/mk/mkc_imp.platform.sys.mk" line 112: >> 'Settings for gcc-10.2.1 is not available, run "mkc_compiler_settings" >> utility' >> *** Error code 1 >> dh_auto_build: error: mkcmake PREFIX=/usr MANDIR=/usr/share/man >> INFODIR=/usr/share/info SYSCONFDIR=/etc STRIPFLAG= >> LIBDIR=/usr/lib/x86_64-linux-gnu LIBEXECDIR=/usr/lib/x86_64-linux-gnu >> returned exit code 1 >> make: *** [debian/rules:12: binary] Error 25 This had already been reported by the libmaa maintainer in #977908 and has been fixed in mk-configure 0.35.really.0.33.0-1. Cheers, Sven
Bug#977960: marked as pending in node-jquery
Control: tag -1 pending Hello, Bug #977960 in node-jquery reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/js-team/node-jquery/-/commit/00b1d48b8af231df2e207574aeea086e52ec2dcb Fix maintscript, thanks to Mattias Ellert Closes: #977960 (this message was generated automatically) -- Greetings https://bugs.debian.org/977960
Processed: Bug#977960 marked as pending in node-jquery
Processing control commands: > tag -1 pending Bug #977960 [libjs-jquery] dangling /usr/share/javascript/jquery/jquery.js symlink Added tag(s) pending. -- 977960: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=977960 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#975943: marked as done (raspi-firmware: arm_64bit is missing and linux-image-arm64 unbootable)
Your message dated Mon, 04 Jan 2021 17:49:55 + with message-id and subject line Bug#975943: fixed in raspi-firmware 1.20201022-3 has caused the Debian Bug report #975943, regarding raspi-firmware: arm_64bit is missing and linux-image-arm64 unbootable 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.) -- 975943: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=975943 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: raspi-firmware Version: 1.20201022-1 Severity: grave Justification: renders package unusable Dear Maintainer, The version 1.20201022-1 does not include "arm_64bit=1" on arm64 architecture, which makes my Raspi runnning linux-image-arm64 unbootable... Of course, adding "arm_64bit=1" by another computer fixes the problem. I did not have this symptom with older version. So I believe that this is a regression. Best regards, Ryutaroh Matsumoto -- System Information: Debian Release: bullseye/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable') Architecture: arm64 (aarch64) Kernel: Linux 5.9.0-3-arm64 (SMP w/4 CPU threads) Kernel taint flags: TAINT_CRAP Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages raspi-firmware depends on: ii dosfstools 4.1-2 ii dpkg1.20.5 raspi-firmware recommends no packages. raspi-firmware suggests no packages. -- no debconf information --- End Message --- --- Begin Message --- Source: raspi-firmware Source-Version: 1.20201022-3 Done: Gunnar Wolf We believe that the bug you reported is fixed in the latest version of raspi-firmware, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 975...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Gunnar Wolf (supplier of updated raspi-firmware package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Sun, 03 Jan 2021 17:00:16 -0600 Source: raspi-firmware Architecture: source Version: 1.20201022-3 Distribution: unstable Urgency: medium Maintainer: pkg-raspi Changed-By: Gunnar Wolf Closes: 975943 Changes: raspi-firmware (1.20201022-3) unstable; urgency=medium . * One more stab at fixing architecture detection - It gets tricky! :-( (Closes: #975943) * Dropped dependency on file - no longer needed Checksums-Sha1: 0373674ae7434bb185b4edba652a7783f61b819e 1616 raspi-firmware_1.20201022-3.dsc a9fb0f5df62f24b46a02999e7ef918473f85dfdb 25772 raspi-firmware_1.20201022-3.debian.tar.xz 33b3c2bc4a9234efc8f152834b0ef3440e17e71b 6584 raspi-firmware_1.20201022-3_source.buildinfo Checksums-Sha256: 0c8f9bf5bdfe10fbab82d6df0031bda395ed3d7e8e974cd0e6e73bad817f1352 1616 raspi-firmware_1.20201022-3.dsc 4ba6930e250f8c4dd8929592c8c0de54d954b85e1e0052af8e5b158b080dde59 25772 raspi-firmware_1.20201022-3.debian.tar.xz 6339fc21ddbbadf4ae1b6be189921746d0f398ee0869db77bae52fc678bb5d2d 6584 raspi-firmware_1.20201022-3_source.buildinfo Files: e426204471ee2a439a195797be2c8f55 1616 non-free/misc optional raspi-firmware_1.20201022-3.dsc b5aa8c3a8a8f57178f9679ae6341ec44 25772 non-free/misc optional raspi-firmware_1.20201022-3.debian.tar.xz 2d877554a073d15b44034012394c2d24 6584 non-free/misc optional raspi-firmware_1.20201022-3_source.buildinfo -BEGIN PGP SIGNATURE- iHUEARYIAB0WIQRgswk9lhCOXLlxQu/i9jtDU/RZiQUCX/NOLgAKCRDi9jtDU/RZ iVYGAQDq4uLzO0G0KXxkdV9soFCt/57Uklv4cM/CFjzQD1SRZwEA02eZL50AzfSD utWLhryuyQ3vILlGzYoJNqWK+7Kv8Ak= =lbbJ -END PGP SIGNATURE End Message ---
Bug#966762: marked as done (nipype: Unversioned Python removal in sid/bullseye)
Your message dated Mon, 4 Jan 2021 12:30:14 -0500 with message-id and subject line Re: Isn't that bug done now? has caused the Debian Bug report #932197, regarding nipype: Unversioned Python removal in sid/bullseye 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.) -- 932197: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=932197 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:nipype Version: 1.1.8-1 Severity: serious Tags: sid bullseye User: debian-pyt...@lists.debian.org Usertags: py2unversioned Python2 becomes end-of-live upstream, and Debian aims to remove Python2 from the distribution, as discussed in https://lists.debian.org/debian-python/2019/07/msg00080.html We will keep some Python2 package as discussed in https://lists.debian.org/debian-python/2020/07/msg00039.html but removing the unversioned python packages python-minimal, python, python-dev, python-dbg, python-doc. Your package either build-depends, depends on one of those packages. Please either convert these packages to Python3, or if that is not possible, replaces the dependencies on the unversioned Python packages with one of the python2 dependencies (python2, python2-dev, python2-dbg, python2-doc). Please check for dependencies, build dependencies AND autopkg tests. If there are questions, please refer to the wiki page for the removal: https://wiki.debian.org/Python/2Removal, or ask for help on IRC #debian-python, or the debian-pyt...@lists.debian.org mailing list. --- End Message --- --- Begin Message --- Version: 1.6.0-1 On Mon, 04 Jan 2021, Andreas Tille wrote: > Hi Yaroslav, > shouldn't this bug be closed now? d'oh -- right, thanks! actually was done within 1.5.0~rc1-1 set of changes marked for experimental -- Yaroslav O. Halchenko Center for Open Neuroscience http://centerforopenneuroscience.org Dartmouth College, 419 Moore Hall, Hinman Box 6207, Hanover, NH 03755 WWW: http://www.linkedin.com/in/yarik--- End Message ---
Bug#937144: marked as done (nipype: Python2 removal in sid/bullseye)
Your message dated Mon, 4 Jan 2021 12:30:14 -0500 with message-id and subject line Re: Isn't that bug done now? has caused the Debian Bug report #932197, regarding nipype: Python2 removal in sid/bullseye 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.) -- 932197: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=932197 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:nipype Version: 1.1.8-1 Severity: normal Tags: sid bullseye User: debian-pyt...@lists.debian.org Usertags: py2removal Python2 becomes end-of-live upstream, and Debian aims to remove Python2 from the distribution, as discussed in https://lists.debian.org/debian-python/2019/07/msg00080.html Your package either build-depends, depends on Python2, or uses Python2 in the autopkg tests. Please stop using Python2, and fix this issue by one of the following actions. - Convert your Package to Python3. This is the preferred option. In case you are providing a Python module foo, please consider dropping the python-foo package, and only build a python3-foo package. Please don't drop Python2 modules, which still have reverse dependencies, just document them. This is the preferred option. - If the package is dead upstream, cannot be converted or maintained in Debian, it should be removed from the distribution. If the package still has reverse dependencies, raise the severity to "serious" and document the reverse dependencies with the BTS affects command. If the package has no reverse dependencies, confirm that the package can be removed, reassign this issue to ftp.debian.org, make sure that the bug priority is set to normal and retitle the issue to "RM: PKG -- removal triggered by the Python2 removal". - If the package has still many users (popcon >= 300), or is needed to build another package which cannot be removed, document that by adding the "py2keep" user tag (not replacing the py2remove tag), using the debian-pyt...@lists.debian.org user. Also any dependencies on an unversioned python package (python, python-dev) must not be used, same with the python shebang. These have to be replaced by python2/python2.7 dependencies and shebang. This is the least preferred option. If the conversion or removal needs action on another package first, please document the blocking by using the BTS affects command, like affects + src:nipype If there is no py2removal bug for that reverse-dependency, please file a bug on this package (similar to this bug report). If there are questions, please refer to the wiki page for the removal: https://wiki.debian.org/Python/2Removal, or ask for help on IRC #debian-python, or the debian-pyt...@lists.debian.org mailing list. --- End Message --- --- Begin Message --- Version: 1.6.0-1 On Mon, 04 Jan 2021, Andreas Tille wrote: > Hi Yaroslav, > shouldn't this bug be closed now? d'oh -- right, thanks! actually was done within 1.5.0~rc1-1 set of changes marked for experimental -- Yaroslav O. Halchenko Center for Open Neuroscience http://centerforopenneuroscience.org Dartmouth College, 419 Moore Hall, Hinman Box 6207, Hanover, NH 03755 WWW: http://www.linkedin.com/in/yarik--- End Message ---
Bug#932542: marked as done (nipype: Please switch to Python 3)
Your message dated Mon, 4 Jan 2021 12:30:14 -0500 with message-id and subject line Re: Isn't that bug done now? has caused the Debian Bug report #932197, regarding nipype: Please switch to Python 3 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.) -- 932197: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=932197 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: nipype Severity: serious Hi, Please make nipype use Python 3, as it wont have python-xvfbwrapper support for Python 2 in a few minutes (I'll be uploading in a few minutes a version of python-xvfbwrapper that removes Python 2 support). Cheers, Thomas Goirand --- End Message --- --- Begin Message --- Version: 1.6.0-1 On Mon, 04 Jan 2021, Andreas Tille wrote: > Hi Yaroslav, > shouldn't this bug be closed now? d'oh -- right, thanks! actually was done within 1.5.0~rc1-1 set of changes marked for experimental -- Yaroslav O. Halchenko Center for Open Neuroscience http://centerforopenneuroscience.org Dartmouth College, 419 Moore Hall, Hinman Box 6207, Hanover, NH 03755 WWW: http://www.linkedin.com/in/yarik--- End Message ---
Bug#932197: marked as done (nipype: Please switch to Python 3)
Your message dated Mon, 4 Jan 2021 12:30:14 -0500 with message-id and subject line Re: Isn't that bug done now? has caused the Debian Bug report #932197, regarding nipype: Please switch to Python 3 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.) -- 932197: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=932197 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: nipype Version: 1.1.9-1 Severity: important Hi, I'd like to switch python-xvfbwrapper to Python 3 only, and noticed that nipype only has Python 2 support. Python 2 is going to be removed from Sid/Testing. Please switch nipype to Python 3 only. Cheers, Thomas Goirand (zigo) --- End Message --- --- Begin Message --- Version: 1.6.0-1 On Mon, 04 Jan 2021, Andreas Tille wrote: > Hi Yaroslav, > shouldn't this bug be closed now? d'oh -- right, thanks! actually was done within 1.5.0~rc1-1 set of changes marked for experimental -- Yaroslav O. Halchenko Center for Open Neuroscience http://centerforopenneuroscience.org Dartmouth College, 419 Moore Hall, Hinman Box 6207, Hanover, NH 03755 WWW: http://www.linkedin.com/in/yarik--- End Message ---
Bug#979257: rabbitvcs-gedit plugin does not load on gedit 3.8+
Package: rabbitvcs-gedit Version: 0.16-1.1 Severity: grave Gedit version: 3.30.2-2 The RabbitVCS plugin won't load at all: - install rabbitrvcs-gedit and gedit packages, run gedit - go to Preferences > Plugins - enable the RabbitVCS plugin - the plugin stays grayed out, the tooltip shows an error message (missing loader) I think the plugin needs to be ported to python3 (https://salsa.debian.org/python-team/packages/rabbitvcs/-/blob/debian/master/clients/gedit/rabbitvcs-plugin.py) Known issue here (https://github.com/rabbitvcs/rabbitvcs/issues/34)
Bug#979243: [Pkg-rust-maintainers] Bug#979243: FTBFS: rust-cpp-demangle - obsolete dep on rust-if-cfg-0.1-dev
librust-cfg-if-0.1+default-dev (>= 0.1.9-~~) , (And a matching, hard-coded Depends line on the binary package) However, this version of rust-cfg-if is now gone and replaced by 1.0 A new source package "rust-cfg-if-0.1" has been introduced which builds the binary package librust-cfg-if-0.1-dev which provides "librust-cfg-if-0.1+default-dev (= 0.1.10-2)". Looking at the log on reproducible builds I see it successfully using the new package. Have you actually seen a build failure anywhere? if so can you point to the log?
Processed: [bts-link] source package src:python-imaplib2
Processing commands for cont...@bugs.debian.org: > # > # bts-link upstream status pull for source package src:python-imaplib2 > # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html > # https://bts-link-team.pages.debian.net/bts-link/ > # > user debian-bts-l...@lists.debian.org Setting user to debian-bts-l...@lists.debian.org (was debian-bts-l...@lists.debian.org). > # remote status report for #937831 (http://bugs.debian.org/937831) > # Bug title: python-imaplib2: Python2 removal in sid/bullseye > # * https://github.com/imaplib2/imaplib2/issues/7 > # * remote status changed: open -> closed > # * closed upstream > tags 937831 + fixed-upstream Bug #937831 [src:python-imaplib2] python-imaplib2: Python2 removal in sid/bullseye Added tag(s) fixed-upstream. > usertags 937831 - status-open Usertags were: status-open. Usertags are now: . > usertags 937831 + status-closed There were no usertags set. Usertags are now: status-closed. > thanks Stopping processing here. Please contact me if you need assistance. -- 937831: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=937831 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#932197: Isn't that bug done now?
Hi Yaroslav, shouldn't this bug be closed now? Kind regards Andreas. -- http://fam-tille.de
Bug#979114: marked as done (opendht: FTBFS in sid)
Your message dated Mon, 4 Jan 2021 11:54:31 -0500
with message-id
and subject line fixed in restinio 0.6.13-1
has caused the Debian Bug report #979114,
regarding opendht: FTBFS in sid
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
979114: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=979114
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: opendht
Version: 2.1.10-1
Severity: serious
tags: ftbfs
Hello, looks like opendht fails because of new boost.
Unfortunately I can't provide a patch since my boost::asio knowledge is limited
and I failed to find upstream patches for this...
example of failure is here:
https://buildd.debian.org/status/fetch.php?pkg=opendht=amd64=2.1.10-1=1609530454=0
[ 67%] Building CXX object
CMakeFiles/opendht-static.dir/src/compat/os_cert.cpp.o
/usr/bin/c++ -DASIO_STANDALONE -DOPENDHT_JSONCPP -DOPENDHT_LOG=true
-DOPENDHT_PEER_DISCOVERY -DOPENDHT_PROXY_CLIENT -DOPENDHT_PROXY_SERVER
-DOPENDHT_PUSH_NOTIFICATIONS -DPACKAGE_VERSION=\"2.1.9\" -I/<>/.
-I/<>/include -I/<>/include/opendht
-I/<>/obj-x86_64-linux-gnu/include -isystem /usr/include/jsoncpp
-g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat
-Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -Wno-return-type -Wall
-Wextra -Wnon-virtual-dtor -pedantic-errors -fvisibility=hidden
-DMSGPACK_DISABLE_LEGACY_NIL -DMSGPACK_DISABLE_LEGACY_CONVERT -fPIC
-std=gnu++14 -o CMakeFiles/opendht-static.dir/src/compat/os_cert.cpp.o -c
/<>/src/compat/os_cert.cpp
/<>/src/http.cpp: In lambda function:
/<>/src/http.cpp:1418:46: warning: unused parameter ‘resp’
[-Wunused-parameter]
1418 | add_on_done_callback([&](const Response& resp){
| ^~~~
In file included from /usr/include/asio/executor.hpp:340,
from /usr/include/asio.hpp:85,
from /usr/include/restinio/asio_include.hpp:14,
from /usr/include/restinio/impl/include_fmtlib.hpp:18,
from /usr/include/restinio/http_headers.hpp:11,
from /<>/include/opendht/http.h:33,
from /<>/include/opendht/dht_proxy_server.h:30,
from /<>/src/dht_proxy_server.cpp:25:
/usr/include/asio/impl/executor.hpp: In instantiation of ‘void
asio::executor::impl< ,
>::on_work_started() [with Executor =
asio::execution::any_executor,
asio::execution::detail::blocking::never_t<0>,
asio::execution::prefer_only
>,
asio::execution::prefer_only
>,
asio::execution::prefer_only
>,
asio::execution::prefer_only
>,
asio::execution::prefer_only
> >; Allocator = std::allocator]’:
/usr/include/asio/impl/executor.hpp:76:8: required from here
/usr/include/asio/impl/executor.hpp:78:15: error: ‘class
asio::execution::any_executor,
asio::execution::detail::blocking::never_t<0>,
asio::execution::prefer_only
>,
asio::execution::prefer_only
>,
asio::execution::prefer_only
>,
asio::execution::prefer_only
>,
asio::execution::prefer_only
> >’ has no member named ‘on_work_started’
78 | executor_.on_work_started();
| ~~^~~
/usr/include/asio/impl/executor.hpp: In instantiation of ‘void
asio::executor::impl< ,
>::on_work_finished() [with Executor =
asio::execution::any_executor,
asio::execution::detail::blocking::never_t<0>,
asio::execution::prefer_only
>,
asio::execution::prefer_only
>,
asio::execution::prefer_only
>,
asio::execution::prefer_only
>,
asio::execution::prefer_only
> >; Allocator = std::allocator]’:
/usr/include/asio/impl/executor.hpp:81:8: required from here
/usr/include/asio/impl/executor.hpp:83:15: error: ‘class
asio::execution::any_executor,
asio::execution::detail::blocking::never_t<0>,
asio::execution::prefer_only
>,
asio::execution::prefer_only
>,
asio::execution::prefer_only
>,
asio::execution::prefer_only
>,
asio::execution::prefer_only
> >’ has no member named ‘on_work_finished’
83 | executor_.on_work_finished();
| ~~^~~~
/usr/include/asio/impl/executor.hpp: In instantiation of ‘void
asio::executor::impl< ,
>::dispatch(asio::executor::function&&) [with Executor =
asio::execution::any_executor,
asio::execution::detail::blocking::never_t<0>,
asio::execution::prefer_only
>,
asio::execution::prefer_only
>,
asio::execution::prefer_only
>,
asio::execution::prefer_only
>,
asio::execution::prefer_only
> >; Allocator = std::allocator; asio::executor::function =
asio::detail::executor_function]’:
/usr/include/asio/impl/executor.hpp:91:8: required from here
Bug#979246: src:fonts-ddc-uchen: invalid maintainer address
Source: fonts-ddc-uchen Version: 1.0-1 Severity: serious X-Debbugs-Cc: fonts-ddc-uchen The maintainer address is invalid, see below. Ansgar Start of forwarded message From: Mail Delivery System Subject: Mail delivery failed: returning message to sender Date: Mon, 04 Jan 2021 14:33:44 + This message was created automatically by mail delivery software. A message that you sent could not be delivered to one or more of its recipients. This is a permanent error. The following address(es) failed: s...@openmailbox.org retry timeout exceeded Reporting-MTA: dns; mailly.debian.org Action: failed Final-Recipient: rfc822;srud@openmailbox.org Status: 5.0.0
Bug#979244: src:moblin-sound-theme: invalid maintainer address
Source: moblin-sound-theme Version: 0.3-1 Severity: serious X-Debbugs-Cc: Holger Levsen The maintainer address is invalid, see below. Ansgar Start of forwarded message From: Mail Delivery System Subject: Mail delivery failed: returning message to sender Date: Mon, 04 Jan 2021 15:50:59 + This message was created automatically by mail delivery software. A message that you sent could not be delivered to one or more of its recipients. This is a permanent error. The following address(es) failed: zhengpeng-...@ubuntu.com host mx.canonical.com [91.189.95.10] SMTP error from remote mail server after RCPT TO:: 550 5.1.1 : Recipient address rejected: User unknown in virtual alias table Reporting-MTA: dns; mailly.debian.org Action: failed Final-Recipient: rfc822;zhengpeng-hou@ubuntu.com Status: 5.0.0 Remote-MTA: dns; mx.canonical.com Diagnostic-Code: smtp; 550 5.1.1 : Recipient address rejected: User unknown in virtual alias table
Processed: fixed 979114 in 0.6.13-1
Processing commands for cont...@bugs.debian.org: > fixed 979114 0.6.13-1 Bug #979114 [restinio] opendht: FTBFS in sid There is no source info for the package 'restinio' at version '0.6.13-1' with architecture '' Unable to make a source version for version '0.6.13-1' Marked as fixed in versions 0.6.13-1. > thanks Stopping processing here. Please contact me if you need assistance. -- 979114: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=979114 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: reassign 979114 to restinio
Processing commands for cont...@bugs.debian.org: > reassign 979114 restinio Bug #979114 [src:opendht] opendht: FTBFS in sid Bug reassigned from package 'src:opendht' to 'restinio'. No longer marked as found in versions opendht/2.1.10-1. Ignoring request to alter fixed versions of bug #979114 to the same values previously set > thanks Stopping processing here. Please contact me if you need assistance. -- 979114: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=979114 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: tagging 977109, tagging 960707, found 974778 in 0.35.0-1, tagging 978623 ..., found 979156 in 0.1.1-1 ...
Processing commands for cont...@bugs.debian.org:
> tags 977109 + experimental
Bug #977109 [ruby-licensee] ruby-licensee, autopkgtest failure with ruby-rugged
1.1.0
Added tag(s) experimental.
> tags 960707 + sid bullseye
Bug #960707 {Done: Bastian Germann } [libalure1]
libalure1: Binary rebuild with current libfluidsynth2
Bug #963122 {Done: Bastian Germann } [libalure1]
bucklespring: error loading shared objectfile
Added tag(s) bullseye and sid.
Added tag(s) bullseye and sid.
> found 974778 0.35.0-1
Bug #974778 [src:llvmlite] llvmlite: stop using llvm-toolchain-10
Bug #974824 [src:llvmlite] llvmlite: stop using llvm-toolchain-10
Marked as found in versions llvmlite/0.35.0-1.
Marked as found in versions llvmlite/0.35.0-1.
> tags 978623 + sid bullseye
Bug #978623 {Done: Roger Shimizu } [src:connect-proxy]
src:connect-proxy: invalid maintainer address
Added tag(s) bullseye and sid.
> found 979137 3.3.2+dfsg-2
Bug #979137 [s3ql] s3ql: Update to newest upstream release
Marked as found in versions s3ql/3.3.2+dfsg-2.
> found 979156 0.1.1-1
Bug #979156 [php-net-idna2] Useless in Debian
Marked as found in versions php-net-idna2/0.1.1-1.
> tags 979156 + sid bullseye
Bug #979156 [php-net-idna2] Useless in Debian
Added tag(s) bullseye and sid.
> tags 969885 + sid bullseye
Bug #969885 [megadown] megadown: [python] is required and it's not installed
Added tag(s) bullseye and sid.
> found 979087 1.0.5-1
Bug #979087 [node-postcss-minify-font-values] incompatible with node-postcss 8
and unmaintained
Marked as found in versions node-postcss-minify-font-values/1.0.5-1.
> tags 979087 + sid bullseye
Bug #979087 [node-postcss-minify-font-values] incompatible with node-postcss 8
and unmaintained
Added tag(s) bullseye and sid.
> notfound 977086 python-dugong/xx
Bug #977086 [src:python-dugong] python-dugong FTBFS with pytest 6
The source python-dugong and version xx do not appear to match any binary
packages
No longer marked as found in versions python-dugong/xx.
> found 977086 3.7.4+dfsg-2
Bug #977086 [src:python-dugong] python-dugong FTBFS with pytest 6
Marked as found in versions python-dugong/3.7.4+dfsg-2.
> tags 977091 + sid bullseye
Bug #977091 [src:python-pymeasure] python-pymeasure FTBFS with pytest 6
Added tag(s) sid and bullseye.
> tags 978192 - sid bullseye
Bug #978192 [src:xfce4-sensors-plugin] xfce4-sensors-plugin: FTBFS:
NVCtrlLib.h:42:1: error: unknown type name ‘Bool’; did you mean ‘bool’?
Removed tag(s) bullseye and sid.
> found 977329 0.14.0-3
Bug #977329 [lxqt-qtplugin] lxqt-plugin: platform theme needs fixes for Qt 5.15
Marked as found in versions lxqt-qtplugin/0.14.0-3.
> tags 977329 + sid bullseye
Bug #977329 [lxqt-qtplugin] lxqt-plugin: platform theme needs fixes for Qt 5.15
Added tag(s) bullseye and sid.
> close 977891 7.5.0+dfsg1-2
Bug #977891 [src:opencascade] opencascade: library package names do not follow
SOVERSION
Marked as fixed in versions opencascade/7.5.0+dfsg1-2.
Bug #977891 [src:opencascade] opencascade: library package names do not follow
SOVERSION
Marked Bug as done
> fixed 955567 4:20.08.0-1
Bug #955567 [kalgebra] kalgebra: Output is always blank
Marked as fixed in versions kalgebra/4:20.08.0-1.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
955567: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=955567
960707: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=960707
963122: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=963122
969885: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=969885
974778: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=974778
974824: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=974824
977086: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=977086
977091: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=977091
977109: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=977109
977329: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=977329
977891: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=977891
978192: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=978192
978623: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=978623
979087: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=979087
979137: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=979137
979156: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=979156
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#977960: I still have a symlink that points to nowhere
Hi. My currently installed version of libjs-jquery is $ dpkg-query --show libjs-jquery libjs-jquery3.5.1+dfsg+~3.5.5-4 which is currently the latest version. I have a symlink as follows: $ ls -l /usr/share/javascript/jquery lrwxrwxrwx 1 root root 29 12 May 2020 /usr/share/javascript/jquery -> /usr/share/nodejs/jquery/dist The target of this symlink does not exist. $ ls /usr/share/nodejs/jquery/dist ls: cannot access '/usr/share/nodejs/jquery/dist': No such file or directory The problem comes from the install history of the package. Version 3.5.1+dfsg+~3.5.4-4 changed a symlink to a directory, but failed to add a maintscript for this change. The following version 3.5.1+dfsg+~3.5.5-1 did add the missing maint- script, but put the previous version in it, not the version that added the script. symlink_to_dir /usr/share/javascript/jquery /usr/share/nodejs/jquery/dist 3.5.1+dfsg+~3.5.4-4~ instead of symlink_to_dir /usr/share/javascript/jquery /usr/share/nodejs/jquery/dist 3.5.1+dfsg+~3.5.5-1~ This means that for everyone that had already updated to 3.5.1+dfsg+~3.5.4-4, when they later updated to 3.5.1+dfsg+~3.5.5-1 the maintscript was not run. To fix this now, there needs to be a 3.5.1+dfsg+~3.5.5-5 update where the mainscriot is updated to symlink_to_dir /usr/share/javascript/jquery /usr/share/nodejs/jquery/dist 3.5.1+dfsg+~3.5.5-5~ For a reproducer 1. Install a version before 3.5.1+dfsg+~3.5.4-4 2. Update to 3.5.1+dfsg+~3.5.4-4 3. Update to a version after 3.5.1+dfsg+~3.5.4-4 Mattias smime.p7s Description: S/MIME cryptographic signature
Bug#979243: FTBFS: rust-cpp-demangle - obsolete dep on rust-if-cfg-0.1-dev
Package: rust-cpp-demangle Version: 0.2.13-1 Severity: Serious It has this build dependency: librust-cfg-if-0.1+default-dev (>= 0.1.9-~~) , (And a matching, hard-coded Depends line on the binary package) However, this version of rust-cfg-if is now gone and replaced by 1.0 (Just FYI: the same holds true for many other rust packages, rust-log for example, IIRC)
Bug#978338: marked as done (nanosv: FTBFS: help2man: can't get `--help' info from ./debian/nanosv/usr/bin/NanoSV)
Your message dated Mon, 04 Jan 2021 15:51:07 +
with message-id
and subject line Bug#978338: fixed in nanosv 1.2.4+git20190409.c1ae30c-3
has caused the Debian Bug report #978338,
regarding nanosv: FTBFS: help2man: can't get `--help' info from
./debian/nanosv/usr/bin/NanoSV
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.)
--
978338: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=978338
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: nanosv
Version: 1.2.4+git20190409.c1ae30c-2
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20201226 ftbfs-bullseye
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> dh_auto_install
> install -d /<>/nanosv-1.2.4\+git20190409.c1ae30c/debian/nanosv
> pybuild --install --test-nose -i python{version} -p 3.9 --dest-dir
> /<>/nanosv-1.2.4\+git20190409.c1ae30c/debian/nanosv
> I: pybuild base:232: /usr/bin/python3 setup.py install --root
> /<>/debian/nanosv
> /usr/lib/python3.9/distutils/dist.py:274: UserWarning: Unknown distribution
> option: 'including_package_data'
> warnings.warn(msg)
> running install
> running build
> running build_py
> running install_lib
> creating /<>/debian/nanosv/usr
> creating /<>/debian/nanosv/usr/lib
> creating /<>/debian/nanosv/usr/lib/python3.9
> creating /<>/debian/nanosv/usr/lib/python3.9/dist-packages
> creating /<>/debian/nanosv/usr/lib/python3.9/dist-packages/nanosv
> copying
> /<>/.pybuild/cpython3_3.9_nanosv/build/nanosv/__init__.py ->
> /<>/debian/nanosv/usr/lib/python3.9/dist-packages/nanosv
> creating
> /<>/debian/nanosv/usr/lib/python3.9/dist-packages/nanosv/utils
> copying
> /<>/.pybuild/cpython3_3.9_nanosv/build/nanosv/utils/parse_svs.py
> -> /<>/debian/nanosv/usr/lib/python3.9/dist-packages/nanosv/utils
> copying
> /<>/.pybuild/cpython3_3.9_nanosv/build/nanosv/utils/__init__.py
> -> /<>/debian/nanosv/usr/lib/python3.9/dist-packages/nanosv/utils
> copying
> /<>/.pybuild/cpython3_3.9_nanosv/build/nanosv/utils/phasing.py
> -> /<>/debian/nanosv/usr/lib/python3.9/dist-packages/nanosv/utils
> copying
> /<>/.pybuild/cpython3_3.9_nanosv/build/nanosv/utils/coverage.py
> -> /<>/debian/nanosv/usr/lib/python3.9/dist-packages/nanosv/utils
> copying
> /<>/.pybuild/cpython3_3.9_nanosv/build/nanosv/utils/create_vcf.py
> ->
> /<>/debian/nanosv/usr/lib/python3.9/dist-packages/nanosv/utils
> copying
> /<>/.pybuild/cpython3_3.9_nanosv/build/nanosv/utils/parse_reads.py
> ->
> /<>/debian/nanosv/usr/lib/python3.9/dist-packages/nanosv/utils
> copying
> /<>/.pybuild/cpython3_3.9_nanosv/build/nanosv/utils/parse_bam.py
> -> /<>/debian/nanosv/usr/lib/python3.9/dist-packages/nanosv/utils
> copying
> /<>/.pybuild/cpython3_3.9_nanosv/build/nanosv/utils/parse_breakpoints.py
> ->
> /<>/debian/nanosv/usr/lib/python3.9/dist-packages/nanosv/utils
> copying /<>/.pybuild/cpython3_3.9_nanosv/build/nanosv/config.ini
> -> /<>/debian/nanosv/usr/lib/python3.9/dist-packages/nanosv
> creating
> /<>/debian/nanosv/usr/lib/python3.9/dist-packages/nanosv/classes
> copying
> /<>/.pybuild/cpython3_3.9_nanosv/build/nanosv/classes/__init__.py
> ->
> /<>/debian/nanosv/usr/lib/python3.9/dist-packages/nanosv/classes
> copying
> /<>/.pybuild/cpython3_3.9_nanosv/build/nanosv/classes/variant.py
> ->
> /<>/debian/nanosv/usr/lib/python3.9/dist-packages/nanosv/classes
> copying
> /<>/.pybuild/cpython3_3.9_nanosv/build/nanosv/classes/read.py ->
> /<>/debian/nanosv/usr/lib/python3.9/dist-packages/nanosv/classes
> copying
> /<>/.pybuild/cpython3_3.9_nanosv/build/nanosv/classes/breakpoint.py
> ->
> /<>/debian/nanosv/usr/lib/python3.9/dist-packages/nanosv/classes
> copying
> /<>/.pybuild/cpython3_3.9_nanosv/build/nanosv/classes/sv.py ->
> /<>/debian/nanosv/usr/lib/python3.9/dist-packages/nanosv/classes
> copying
> /<>/.pybuild/cpython3_3.9_nanosv/build/nanosv/classes/segment.py
> ->
> /<>/debian/nanosv/usr/lib/python3.9/dist-packages/nanosv/classes
> copying /<>/.pybuild/cpython3_3.9_nanosv/build/nanosv/NanoSV.py
> -> /<>/debian/nanosv/usr/lib/python3.9/dist-packages/nanosv
> copying /<>/.pybuild/cpython3_3.9_nanosv/build/nanosv/version.py
> -> /<>/debian/nanosv/usr/lib/python3.9/dist-packages/nanosv
> creating
> /<>/debian/nanosv/usr/lib/python3.9/dist-packages/nanosv/bedfiles
> copying
> /<>/.pybuild/cpython3_3.9_nanosv/build/nanosv/bedfiles/human_hg19.bed
> ->
> /<>/debian/nanosv/usr/lib/python3.9/dist-packages/nanosv/bedfiles
> byte-compiling
>
Bug#978230: marked as done (pymia: FTBFS: build-dependency not installable: mia-doctools (= 2.4.7-4))
Your message dated Mon, 04 Jan 2021 15:50:52 + with message-id and subject line Bug#976756: fixed in mia 2.4.7-6 has caused the Debian Bug report #976756, regarding pymia: FTBFS: build-dependency not installable: mia-doctools (= 2.4.7-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.) -- 976756: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=976756 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: pymia Version: 0.1.9-2.1 Severity: serious Justification: FTBFS on amd64 Tags: bullseye sid ftbfs Usertags: ftbfs-20201226 ftbfs-bullseye Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > +--+ > | Install package build dependencies > | > +--+ > > > Setup apt archive > - > > Merged Build-Depends: debhelper (>= 9), pkg-config, dh-python, > python3-dev:any, python3-numpy, python3-setuptools, libmia-2.4-dev, > build-essential, fakeroot > Filtered Build-Depends: debhelper (>= 9), pkg-config, dh-python, > python3-dev:any, python3-numpy, python3-setuptools, libmia-2.4-dev, > build-essential, fakeroot > dpkg-deb: building package 'sbuild-build-depends-main-dummy' in > '/<>/apt_archive/sbuild-build-depends-main-dummy.deb'. > Ign:1 copy:/<>/apt_archive ./ InRelease > Get:2 copy:/<>/apt_archive ./ Release [957 B] > Ign:3 copy:/<>/apt_archive ./ Release.gpg > Get:4 copy:/<>/apt_archive ./ Sources [411 B] > Get:5 copy:/<>/apt_archive ./ Packages [497 B] > Fetched 1865 B in 0s (142 kB/s) > Reading package lists... > Reading package lists... > > Install main build dependencies (apt-based resolver) > > > Installing build dependencies > Reading package lists... > Building dependency tree... > Reading state information... > Some packages could not be installed. This may mean that you have > requested an impossible situation or if you are using the unstable > distribution that some required packages have not yet been created > or been moved out of Incoming. > The following information may help to resolve the situation: > > The following packages have unmet dependencies: > libmia-2.4-dev : Depends: mia-doctools (= 2.4.7-4) but it is not installable > E: Unable to correct problems, you have held broken packages. > apt-get failed. The full build log is available from: http://qa-logs.debian.net/2020/12/26/pymia_0.1.9-2.1_unstable.log A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! If you reassign this bug to another package, please marking it as 'affects'-ing this package. See https://www.debian.org/Bugs/server-control#affects If you fail to reproduce this, please provide a build log and diff it with me so that we can identify if something relevant changed in the meantime. About the archive rebuild: The rebuild was done on EC2 VM instances from Amazon Web Services, using a clean, minimal and up-to-date chroot. Every failed build was retried once to eliminate random failures. --- End Message --- --- Begin Message --- Source: mia Source-Version: 2.4.7-6 Done: Andreas Tille We believe that the bug you reported is fixed in the latest version of mia, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 976...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Andreas Tille (supplier of updated mia package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Mon, 04 Jan 2021 13:52:08 +0100 Source: mia Architecture: source Version: 2.4.7-6 Distribution: unstable Urgency: medium Maintainer: Debian Med Packaging Team Changed-By: Andreas Tille Closes: 976756 Changes: mia (2.4.7-6) unstable; urgency=medium . * Team upload. * Set -DCMAKE_SKIP_INSTALL_ALL_DEPENDENCY=OFF (which was changed due to debhelper compat level 13 in 2.4.7-3) Closes: #976756 Checksums-Sha1:
Bug#978224: marked as done (miaviewit: FTBFS: build-dependency not installable: mia-doctools (= 2.4.7-4))
Your message dated Mon, 04 Jan 2021 15:50:52 + with message-id and subject line Bug#976756: fixed in mia 2.4.7-6 has caused the Debian Bug report #976756, regarding miaviewit: FTBFS: build-dependency not installable: mia-doctools (= 2.4.7-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.) -- 976756: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=976756 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: miaviewit Version: 1.0.5-3 Severity: serious Justification: FTBFS on amd64 Tags: bullseye sid ftbfs Usertags: ftbfs-20201226 ftbfs-bullseye Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > +--+ > | Install package build dependencies > | > +--+ > > > Setup apt archive > - > > Merged Build-Depends: debhelper-compat (= 13), libmia-2.4-dev (>= 2.4.4), > libgle3-dev, libgtkglextmm-x11-1.2-dev, libboost-thread-dev, > libgtkmm-2.4-dev, libxml++2.6-dev, libvistaio-dev, build-essential, fakeroot > Filtered Build-Depends: debhelper-compat (= 13), libmia-2.4-dev (>= 2.4.4), > libgle3-dev, libgtkglextmm-x11-1.2-dev, libboost-thread-dev, > libgtkmm-2.4-dev, libxml++2.6-dev, libvistaio-dev, build-essential, fakeroot > dpkg-deb: building package 'sbuild-build-depends-main-dummy' in > '/<>/apt_archive/sbuild-build-depends-main-dummy.deb'. > Ign:1 copy:/<>/apt_archive ./ InRelease > Get:2 copy:/<>/apt_archive ./ Release [957 B] > Ign:3 copy:/<>/apt_archive ./ Release.gpg > Get:4 copy:/<>/apt_archive ./ Sources [439 B] > Get:5 copy:/<>/apt_archive ./ Packages [522 B] > Fetched 1918 B in 0s (0 B/s) > Reading package lists... > Reading package lists... > > Install main build dependencies (apt-based resolver) > > > Installing build dependencies > Reading package lists... > Building dependency tree... > Reading state information... > Some packages could not be installed. This may mean that you have > requested an impossible situation or if you are using the unstable > distribution that some required packages have not yet been created > or been moved out of Incoming. > The following information may help to resolve the situation: > > The following packages have unmet dependencies: > libmia-2.4-dev : Depends: mia-doctools (= 2.4.7-4) but it is not installable > E: Unable to correct problems, you have held broken packages. > apt-get failed. The full build log is available from: http://qa-logs.debian.net/2020/12/26/miaviewit_1.0.5-3_unstable.log A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! If you reassign this bug to another package, please marking it as 'affects'-ing this package. See https://www.debian.org/Bugs/server-control#affects If you fail to reproduce this, please provide a build log and diff it with me so that we can identify if something relevant changed in the meantime. About the archive rebuild: The rebuild was done on EC2 VM instances from Amazon Web Services, using a clean, minimal and up-to-date chroot. Every failed build was retried once to eliminate random failures. --- End Message --- --- Begin Message --- Source: mia Source-Version: 2.4.7-6 Done: Andreas Tille We believe that the bug you reported is fixed in the latest version of mia, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 976...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Andreas Tille (supplier of updated mia package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Mon, 04 Jan 2021 13:52:08 +0100 Source: mia Architecture: source Version: 2.4.7-6 Distribution: unstable Urgency: medium Maintainer: Debian Med Packaging Team Changed-By: Andreas Tille Closes: 976756 Changes: mia (2.4.7-6) unstable; urgency=medium . * Team upload. * Set -DCMAKE_SKIP_INSTALL_ALL_DEPENDENCY=OFF
Bug#976756: marked as done (mia: binary-all FTBFS)
Your message dated Mon, 04 Jan 2021 15:50:52 + with message-id and subject line Bug#976756: fixed in mia 2.4.7-6 has caused the Debian Bug report #976756, regarding mia: binary-all FTBFS to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 976756: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=976756 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: mia Version: 2.4.7-3 Severity: serious Tags: ftbfs https://buildd.debian.org/status/fetch.php?pkg=mia=all=2.4.7-3=1607360001=0 ... CMake Error at mia/3d/cmake_install.cmake:110 (file): file INSTALL cannot find "/<>/obj-x86_64-linux-gnu/mia/3d/libmia3dtest-2.4.so.6.0.1": No such file or directory. Call Stack (most recent call first): mia/cmake_install.cmake:65 (include) cmake_install.cmake:130 (include) make[1]: *** [Makefile:96: install] Error 1 --- End Message --- --- Begin Message --- Source: mia Source-Version: 2.4.7-6 Done: Andreas Tille We believe that the bug you reported is fixed in the latest version of mia, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 976...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Andreas Tille (supplier of updated mia package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Mon, 04 Jan 2021 13:52:08 +0100 Source: mia Architecture: source Version: 2.4.7-6 Distribution: unstable Urgency: medium Maintainer: Debian Med Packaging Team Changed-By: Andreas Tille Closes: 976756 Changes: mia (2.4.7-6) unstable; urgency=medium . * Team upload. * Set -DCMAKE_SKIP_INSTALL_ALL_DEPENDENCY=OFF (which was changed due to debhelper compat level 13 in 2.4.7-3) Closes: #976756 Checksums-Sha1: 01c362171b7c9fd0185dab31aa2373ea6a35e936 2839 mia_2.4.7-6.dsc 2c1a7cb3c267a29cbf0eeb2dc5a169dc71776554 10476 mia_2.4.7-6.debian.tar.xz 58a5773b57dd3a67a8efbbb340430079c6621b3d 24504 mia_2.4.7-6_amd64.buildinfo Checksums-Sha256: ff3c1196dec689b7aed9406a2364f076f2a9fdbb5653b0a956bdcc0e2702225e 2839 mia_2.4.7-6.dsc 7ff925d6cd147b31210a441ce066150c4826a05524a7c9413f6c44c968ef86fc 10476 mia_2.4.7-6.debian.tar.xz 8cd956bb0c42f06ba05ddb4bf6b829b9a59c33313ac82caa641abfd433ea0e5c 24504 mia_2.4.7-6_amd64.buildinfo Files: 7c72a358564e0a425c8d5c9a7691c272 2839 science optional mia_2.4.7-6.dsc b1456f36f2fdd9a91ca0152243f6a83f 10476 science optional mia_2.4.7-6.debian.tar.xz 893487a3fc017e09323a74fb4ac0b9d1 24504 science optional mia_2.4.7-6_amd64.buildinfo -BEGIN PGP SIGNATURE- iQJFBAEBCAAvFiEE8fAHMgoDVUHwpmPKV4oElNHGRtEFAl/zNA0RHHRpbGxlQGRl Ymlhbi5vcmcACgkQV4oElNHGRtGICQ//QDHCPJ/3zSMmhoBPc/ObVW1ZFxAyOEg7 ROwoUvABqKSpX1Q36juM7NmKFIjGVCirE9AvBxidIrrfaDmrcdgqvOL98gE/lDu5 sq7orhvhlPhjUW2IhRaVv4yIsWsblVz/BIT6MzT0vrem9lSUPNQi4oqzRLvH2iSf ZzTi46BtfaLzEB3JtPS2S7GbXefWzmUOAyn6OZ6lqaPIijQAPhIqrs9dXTao5qjk +LtLvZbglliUg5Bdh8bZs5ysb0RBnSyVtLlAWO0Zza6XcqEotxyp4AMFXgh3GWxx GT+8Blj4YL43FsSCy1SbnU3WhrkqN3HpJNfPJ8R21TpOf+RiUFq9UVqGWE+R4I01 bzJgocKCyZhkSfAzv4kzUhaWapQFc4c/8QQPp1K872qm8mwFuKZONYraELgsM1+F YEOcTkTXli1988GUJlMnwhCHcjJjqMS+EAN3GBd3ff7ANPxL5ECPekcqXNKiFP+x 8KTzg+zk3ajj2+oQzbEMUSDSDfjh4PTW/Ya2ED3xPFEoc2lNZe6TwYlP8vK81lYz z6LdrRhyxIWks4GHsI5U+0yNulVIYtG1BR6Nguxf1aOw7qnYUXaaFnNkPF8rflr8 Xx8A4t8B9p0C76PWnQRlYvRwSSbKUE6KS4z5yqRWMCJTkX4dNWeGpywluk21VMrR QbJfdxJgHgs= =nGvu -END PGP SIGNATURE End Message ---
Bug#977243: Still not fixed
you probably need the first commit from https://github.com/ceph/ceph/pull/38263
On Thu, Dec 24, 2020 at 8:28 AM Anton Gladky wrote:
>
> tags 977243 -pending
> thanks
>
> CC-ing on of upstream contributors.
>
> @Casey could you please take a look? This part of the code
> fails with the newer boost_1.74? Thanks!
>
> It looks like the last version in git still fails to build.
>
> ===
> ceph/src/common/async/completion.h: In instantiation of 'void
> ceph::async::detail::CompletionImpl Args>::destroy_defer(std::tuple&&) [with Executor1 =
> boost::asio::io_context::basic_executor_typ
> e, 0>; Handler =
> boost::asio::detail::coro_handler (*)(),
> boost::asio::execution::any_executor,
> boost::asio::exec
> ution::detail::blocking::never_t<0>,
> boost::asio::execution::prefer_only
> >,
> >boost::asio::execution::prefer_only
> >, boos
> t::asio::execution::prefer_only
> >,
> >boost::asio::execution::prefer_only
> >, boost::asio::execution::prefer_only asio::execution::detail::relationship::continuation_t<0> > > >, void>;
> T = void; Args = {boost::system::error_code}]':
> /root/mod1/ceph/src/common/async/completion.h:188:8: required from
> here
> /root/mod1/ceph/src/common/async/completion.h:194:29: error:
> 'boost::asio::executor_work_guard,
> boost::asio::execution::detail::blo
> cking::never_t<0>,
> boost::asio::execution::prefer_only
> >,
> >boost::asio::execution::prefer_only
> >, boost::asio::execution
> ::prefer_only
> >,
> >boost::asio::execution::prefer_only
> >, boost::asio::execution::prefer_only etail::relationship::continuation_t<0> > >, void>::executor_type' {aka
> 'class
> boost::asio::execution::any_executor,
> boost::asio::execution::detail::blocking::never_t<0>
> ,
> boost::asio::execution::prefer_only
> >,
> >boost::asio::execution::prefer_only
> >, boost::asio::execution::prefer_only st::asio::execution::detail::outstanding_work::untracked_t<0> >,
> boost::asio::execution::prefer_only
> >,
> >boost::asio::execution::prefer_only ip::continuation_t<0> > >'} has no member named 'defer'; did you mean
> 'prefer'?
> 194 | w.second.get_executor().defer(std::move(f), alloc2);
> | ^
> | prefer
> ceph/src/common/async/completion.h: In instantiation of 'void
> ceph::async::detail::CompletionImpl Args>::destroy_dispatch(std::tuple&&) [with Executor1 =
> boost::asio::io_context::basic_executor_
> type, 0>; Handler =
> boost::asio::detail::coro_handler (*)(),
> boost::asio::execution::any_executor,
> boost::asio::e
> xecution::detail::blocking::never_t<0>,
> boost::asio::execution::prefer_only
> >,
> >boost::asio::execution::prefer_only
> >, b
> oost::asio::execution::prefer_only
> >,
> >boost::asio::execution::prefer_only
> >, boost::asio::execution::prefer_only t::asio::execution::detail::relationship::continuation_t<0> > > >,
> void>; T = void; Args = {boost::system::error_code}]':
> /root/mod1/ceph/src/common/async/completion.h:196:8: required from here
> /root/mod1/ceph/src/common/async/completion.h:202:29: error:
> 'boost::asio::executor_work_guard,
> boost::asio::execution::detail::blo
> cking::never_t<0>,
> boost::asio::execution::prefer_only
> >,
> >boost::asio::execution::prefer_only
> >, boost::asio::execution
> ::prefer_only
> >,
> >boost::asio::execution::prefer_only
> >, boost::asio::execution::prefer_only etail::relationship::continuation_t<0> > >, void>::executor_type' {aka
> 'class
> boost::asio::execution::any_executor,
> boost::asio::execution::detail::blocking::never_t<0>
> ,
> boost::asio::execution::prefer_only
> >,
> >boost::asio::execution::prefer_only
> >, boost::asio::execution::prefer_only st::asio::execution::detail::outstanding_work::untracked_t<0> >,
> boost::asio::execution::prefer_only
> >,
> >boost::asio::execution::prefer_only ip::continuation_t<0> > >'} has no member named 'dispatch'
> 202 | w.second.get_executor().dispatch(std::move(f), alloc2);
> | ^~~~
> ceph/src/common/async/completion.h: In instantiation of 'void
> ceph::async::detail::CompletionImpl Args>::destroy_post(std::tuple&&) [with Executor1 =
> boost::asio::io_context::basic_executor_type
> , 0>; Handler =
> boost::asio::detail::coro_handler (*)(),
> boost::asio::execution::any_executor,
> boost::asio::execu
> tion::detail::blocking::never_t<0>,
> boost::asio::execution::prefer_only
> >,
> >boost::asio::execution::prefer_only
> >, boost
> ::asio::execution::prefer_only
> >,
> >boost::asio::execution::prefer_only
> >, boost::asio::execution::prefer_only sio::execution::detail::relationship::continuation_t<0> > > >, void>;
> T = void; Args = {boost::system::error_code}]':
> /root/mod1/ceph/src/common/async/completion.h:204:8: required from here
> /root/mod1/ceph/src/common/async/completion.h:210:29: error:
> 'boost::asio::executor_work_guard,
> boost::asio::execution::detail::blo
> cking::never_t<0>,
> boost::asio::execution::prefer_only
> >,
> >boost::asio::execution::prefer_only
>
Processed: tagging 979223, tagging 979222, tagging 979221, tagging 979219, tagging 979218, tagging 979058 ...
Processing commands for cont...@bugs.debian.org: > # this metadata is taken from sid > tags 979223 + sid bullseye Bug #979223 [src:moblin-icon-theme] src:moblin-icon-theme: invalid maintainer address Added tag(s) sid and bullseye. > tags 979222 + sid bullseye Bug #979222 [src:geronimo-ejb-3.0-spec] src:geronimo-ejb-3.0-spec: invalid maintainer address Added tag(s) bullseye and sid. > tags 979221 + sid bullseye Bug #979221 [src:gwhois] src:gwhois: invalid maintainer address Added tag(s) bullseye and sid. > tags 979219 + sid bullseye Bug #979219 [src:moblin-cursor-theme] src:moblin-cursor-theme: invalid maintainer address Added tag(s) bullseye and sid. > tags 979218 + sid bullseye Bug #979218 [src:renrot] src:renrot: invalid maintainer address Added tag(s) sid and bullseye. > tags 979058 + sid bullseye Bug #979058 [src:geronimo-j2ee-connector-1.5-spec] src:geronimo-j2ee-connector-1.5-spec: invalid maintainer address Added tag(s) bullseye and sid. > tags 979056 + sid bullseye Bug #979056 [src:geronimo-jms-1.1-spec] src:geronimo-jms-1.1-spec: invalid maintainer address Added tag(s) sid and bullseye. > tags 979055 + sid bullseye Bug #979055 [src:extra-xdg-menus] src:extra-xdg-menus: invalid maintainer address Added tag(s) bullseye and sid. > tags 979054 + sid bullseye Bug #979054 [src:john] src:john: invalid maintainer address Added tag(s) sid and bullseye. > tags 979052 + sid bullseye Bug #979052 [src:nam] src:nam: invalid maintainer address Added tag(s) bullseye and sid. > tags 979051 + sid bullseye Bug #979051 [src:aspell-hr] src:aspell-hr: invalid maintainer address Added tag(s) bullseye and sid. > tags 978624 + sid bullseye Bug #978624 [src:fbxkb] src:fbxkb: invalid maintainer address Added tag(s) bullseye and sid. > thanks Stopping processing here. Please contact me if you need assistance. -- 978624: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=978624 979051: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=979051 979052: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=979052 979054: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=979054 979055: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=979055 979056: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=979056 979058: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=979058 979218: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=979218 979219: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=979219 979221: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=979221 979222: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=979222 979223: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=979223 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#979229: libpcap0.8-dev: missing dependency on libdbus-1-dev causes build failures
Hi Luca, On Mon, Jan 4, 2021 at 2:36 PM Luca Boccassi wrote: > libpcap0.8-dev sets "Libs.private: -ldbus-1" in its pkg-config file, > but it does not have a dependency on libdbus-1-dev, causing a build > failure in reverse dependencies that use pkg-config --static (or macro > variations thereof). > > Please consider adding this dependency, so that everything works out > of the box. Sure, makes sense. I'll pick up your change in the next upload, thanks!
Processed: fixed 875899 in 3.0.36-1, notfound 808724 in 1.185.1, reassign 970802 to src:xen ...
Processing commands for cont...@bugs.debian.org:
> fixed 875899 3.0.36-1
Bug #875899 {Done: Jonas Smedegaard } [licensecheck]
licensecheck cannot detect MIT variant license
Marked as fixed in versions licensecheck/3.0.36-1.
> notfound 808724 1.185.1
Bug #808724 {Done: Iain Buclaw } [gdc] gdc: "switch"
requires a "default" case
There is no source info for the package 'gdc' at version '1.185.1' with
architecture ''
Unable to make a source version for version '1.185.1'
No longer marked as found in versions gcc-defaults/1.185.1.
> reassign 970802 src:xen
Bug #970802 {Done: Ian Jackson } [gcc-10]
gcc-10: armhf: false positive when using -O2 and -Werror=format-truncation
Bug reassigned from package 'gcc-10' to 'src:xen'.
No longer marked as found in versions gcc-10/10.2.0-9.
No longer marked as fixed in versions xen/4.14.0+80-gd101b417b7-1~exp2 and
xen/4.14.0+80-gd101b417b7-1.
> fixed 970802 4.14.0+80-gd101b417b7-1~exp2
Bug #970802 {Done: Ian Jackson } [src:xen]
gcc-10: armhf: false positive when using -O2 and -Werror=format-truncation
Marked as fixed in versions xen/4.14.0+80-gd101b417b7-1~exp2.
> fixed 970802 4.14.0+80-gd101b417b7-1
Bug #970802 {Done: Ian Jackson } [src:xen]
gcc-10: armhf: false positive when using -O2 and -Werror=format-truncation
Marked as fixed in versions xen/4.14.0+80-gd101b417b7-1.
> reassign 974837 src:tpm2-tss 3.0.1-2
Bug #974837 {Done: Ying-Chun Liu (PaulLiu) }
[libtss2-esys0] libtss2-esys0 was split without being renamed
Bug reassigned from package 'libtss2-esys0' to 'src:tpm2-tss'.
No longer marked as found in versions tpm2-tss/3.0.1-2.
No longer marked as fixed in versions tpm2-tss/3.0.2-1.
Bug #974837 {Done: Ying-Chun Liu (PaulLiu) } [src:tpm2-tss]
libtss2-esys0 was split without being renamed
Marked as found in versions tpm2-tss/3.0.1-2.
> fixed 974837 3.0.2-1
Bug #974837 {Done: Ying-Chun Liu (PaulLiu) } [src:tpm2-tss]
libtss2-esys0 was split without being renamed
Marked as fixed in versions tpm2-tss/3.0.2-1.
> reassign 941301 calamares-settings-debian
Bug #941301 {Done: Jonathan Carter } [calamares] Calamares:
write two random seeds to locations for urandom init script and
systemd-random-seed service
Bug reassigned from package 'calamares' to 'calamares-settings-debian'.
No longer marked as found in versions calamares/3.2.4-3.
No longer marked as fixed in versions calamares-settings-debian/11.0.3-1.
> fixed 941301 11.0.3-1
Bug #941301 {Done: Jonathan Carter }
[calamares-settings-debian] Calamares: write two random seeds to locations for
urandom init script and systemd-random-seed service
Marked as fixed in versions calamares-settings-debian/11.0.3-1.
> reassign 962731 thunar 1.8.4-1
Bug #962731 {Done: Yves-Alexis Perez } [xfce4] xfce4: xfce
needs gvfs-backends to read phone memory
Bug reassigned from package 'xfce4' to 'thunar'.
No longer marked as found in versions xfce4/4.12.5.
No longer marked as fixed in versions thunar/4.15.3-1.
Bug #962731 {Done: Yves-Alexis Perez } [thunar] xfce4: xfce
needs gvfs-backends to read phone memory
Marked as found in versions thunar/1.8.4-1.
> fixed 962731 4.15.3-1
Bug #962731 {Done: Yves-Alexis Perez } [thunar] xfce4: xfce
needs gvfs-backends to read phone memory
Marked as fixed in versions thunar/4.15.3-1.
> fixed 932620 6.1.0-1
Bug #932620 {Done: Laszlo Boszormenyi (GCS) }
[libcrypto++-dev] libcrypto++-dev: build system does not include blake2.cpp
Marked as fixed in versions libcrypto++/6.1.0-1.
> reassign 967546 src:debian-installer-utils
Bug #967546 {Done: =?utf-8?q?Rapha=C3=ABl_Hertzog?=
} [udev] udev: missing /dev/stdin etc.
Bug reassigned from package 'udev' to 'src:debian-installer-utils'.
No longer marked as found in versions systemd/246-2.
No longer marked as fixed in versions debian-installer-utils/1.134.
> fixed 967546 1.134
Bug #967546 {Done: =?utf-8?q?Rapha=C3=ABl_Hertzog?=
} [src:debian-installer-utils] udev: missing
/dev/stdin etc.
Marked as fixed in versions debian-installer-utils/1.134.
> notfixed 975017 debian-installer-utils/1.134
Bug #975017 {Done: =?utf-8?q?Rapha=C3=ABl_Hertzog?=
} [udev] udev: missing /dev/stdin etc.
No longer marked as fixed in versions debian-installer-utils/1.134.
> notfound 931237 2.03.02-3
Bug #931237 {Done: Bastian Blank } [lvm2] lvm2: "lvm2-lvmetad
not found" on upgrade
Bug #917159 {Done: Bastian Blank } [lvm2] Please drop
/etc/init.d/lvm2-lvmetad
No longer marked as found in versions lvm2/2.03.02-3.
No longer marked as found in versions lvm2/2.03.02-3.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
808724: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=808724
875899: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=875899
917159: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=917159
931237: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=931237
932620: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=932620
941301: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=941301
962731:
Processed: found 978341 in 7.12.9+~cs150.130.99-1
Processing commands for cont...@bugs.debian.org:
> found 978341 7.12.9+~cs150.130.99-1
Bug #978341 {Done: Xavier Guimard } [node-babel7] node-recast:
FTBFS: node_modules/@babel/parser/typings/babel-parser.d.ts(14,11): error
TS7016: Could not find a declaration file for module '@babel/types'.
'/<>/node_modules/@babel/types/lib/index.js' implicitly has an
'any' type.
Bug #978384 {Done: Xavier Guimard } [node-babel7]
node-ast-types: FTBFS:
node_modules/@babel/parser/typings/babel-parser.d.ts(14,11): error TS7016:
Could not find a declaration file for module '@babel/types'.
'/<>/node_modules/@babel/types/lib/index.js' implicitly has an
'any' type.
Marked as found in versions node-babel7/7.12.9+~cs150.130.99-1.
Marked as found in versions node-babel7/7.12.9+~cs150.130.99-1.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
978341: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=978341
978384: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=978384
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#979232: lighttpd: does not start with media-types 1.1.0
Package: lighttpd Version: 1.4.57-1 Severity: grave Justification: renders package unusable Dear Maintainer, After media-types has been upgraded to 1.1.0, lighttpd fails to start, complaining about duplicated media types. jan 04 11:17:27 lemur systemd[1]: Starting Lighttpd Daemon... jan 04 11:17:27 lemur lighttpd[22434]: Duplicate mimetype: '.png' => 'image/vnd.mozilla.apng' (already have 'image/png'), merging to 'application/octet-stream' jan 04 11:17:27 lemur lighttpd[22434]: Duplicate mimetype: '.pcx' => 'image/vnd.zbrush.pcx' (already have 'image/pcx'), merging to 'application/octet-stream' jan 04 11:17:28 lemur lighttpd[22430]: Error: duplicate array-key: .pgb. Please get rid of the duplicate entry. jan 04 11:17:28 lemur lighttpd[22430]: 2021-01-04 11:17:27: (configfile.c.1966) source: /usr/share/lighttpd/create-mime.conf.pl line: 495 pos: 8 parser failed somehow near here: (COMMA) jan 04 11:17:28 lemur lighttpd[22430]: 2021-01-04 11:17:27: (configfile.c.1966) source: /etc/lighttpd/lighttpd.conf line: 48 pos: 8 parser failed somehow near here: (EOL) jan 04 11:17:28 lemur systemd[1]: lighttpd.service: Control process exited, code=exited, status=255/EXCEPTION jan 04 11:17:28 lemur systemd[1]: lighttpd.service: Failed with result 'exit-code'. jan 04 11:17:28 lemur systemd[1]: Failed to start Lighttpd Daemon. jan 04 11:17:28 lemur systemd[1]: lighttpd.service: Scheduled restart job, restart counter is at 5. jan 04 11:17:28 lemur systemd[1]: Stopped Lighttpd Daemon. jan 04 11:17:28 lemur systemd[1]: lighttpd.service: Start request repeated too quickly. jan 04 11:17:28 lemur systemd[1]: lighttpd.service: Failed with result 'exit-code'. jan 04 11:17:28 lemur systemd[1]: Failed to start Lighttpd Daemon. The new /etc/mime.types has both lowercase and uppercase file extensions for the same mime type: $ grep pgb /etc/mime.types image/vnd.globalgraphics.pgbPGB pgb I'm copying the media-types maintainers just so that they know about this, but it seems to me that this should be handled properly in lighttpd. -- System Information: Debian Release: bullseye/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'testing-debug'), (500, 'unstable'), (500, 'testing'), (1, 'experimental-debug'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 5.10.0-1-amd64 (SMP w/4 CPU threads) Locale: LANG=pt_BR.UTF-8, LC_CTYPE=pt_BR.UTF-8 (charmap=UTF-8), LANGUAGE=pt_BR:pt:en Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages lighttpd depends on: ii init-system-helpers 1.60 ii libc62.31-7 ii libcrypt11:4.4.17-1 ii libnettle8 3.6-2 ii libpcre3 2:8.39-13 ii libxxhash0 0.8.0-1 ii lsb-base 11.1.0 ii mime-support 3.66 Versions of packages lighttpd recommends: ii lighttpd-mod-deflate 1.4.57-1 ii lighttpd-mod-openssl 1.4.57-1 ii perl 5.32.0-6 ii spawn-fcgi1.6.4-2 Versions of packages lighttpd suggests: ii apache2-utils 2.4.46-2 pn lighttpd-doc pn lighttpd-mod-authn-gssapi pn lighttpd-mod-authn-pam pn lighttpd-mod-authn-sasl pn lighttpd-mod-geoip pn lighttpd-mod-maxminddb pn lighttpd-mod-trigger-b4-dl pn lighttpd-mod-vhostdb-pgsql pn lighttpd-mod-webdav pn lighttpd-modules-dbi ii lighttpd-modules-ldap 1.4.57-1 pn lighttpd-modules-lua ii lighttpd-modules-mysql 1.4.57-1 ii openssl 1.1.1i-1 pn php-cgi pn php-fpm pn rrdtool -- no debconf information signature.asc Description: PGP signature
Bug#977087: marked as done (python-google-auth FTBFS with pytest 6)
Your message dated Mon, 04 Jan 2021 14:21:16 +
with message-id
and subject line Bug#977087: fixed in python-google-auth 1.5.1-3
has caused the Debian Bug report #977087,
regarding python-google-auth FTBFS with pytest 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.)
--
977087: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=977087
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-google-auth
Version: 1.5.1-2
Severity: important
User: pyt...@packages.debian.org
Usertags: pytest-v6
Hi,
python-google-auth FTBFS with pytest 6 in experimental because
pytest.warns no longer accepts a second string argument, see
https://docs.pytest.org/en/latest/changelog.html#removals
The error log below has more details.
> I: pybuild base:232: cd
> /<>/.pybuild/cpython3_3.9_google-auth/build; python3.9 -m pytest
> --ignore=tests/transport
> = test session starts
> ==
> platform linux -- Python 3.9.1, pytest-6.0.2, py-1.9.0, pluggy-0.13.0
> rootdir: /<>
> plugins: localserver-0.5.0
> collected 252 items
>
> tests/test__cloud_sdk.py [
> 4%]
> tests/test__default.py .F. [
> 15%]
> tests/test__helpers.py ..[
> 22%]
> tests/test__oauth2client.py .[
> 26%]
> tests/test__service_account_info.py [
> 27%]
> tests/test_app_engine.py . [
> 32%]
> tests/test_credentials.py [
> 37%]
> tests/test_iam.py [
> 39%]
> tests/test_jwt.py [
> 56%]
> tests/compute_engine/test__metadata.py [
> 61%]
> tests/compute_engine/test_credentials.py . [
> 66%]
> tests/crypt/test__cryptography_rsa.py [
> 73%]
> tests/crypt/test__python_rsa.py .. [
> 80%]
> tests/crypt/test_crypt.py .. [
> 80%]
> tests/oauth2/test__client.py [
> 85%]
> tests/oauth2/test_credentials.py . [
> 87%]
> tests/oauth2/test_id_token.py .. [
> 90%]
> tests/oauth2/test_service_account.py .
> [100%]
>
> === FAILURES
> ===
> __ test__load_credentials_from_file_authorized_user_cloud_sdk
> __
>
> def test__load_credentials_from_file_authorized_user_cloud_sdk():
>> with pytest.warns(UserWarning, matches='Cloud SDK'):
> E TypeError: Unexpected keyword arguments passed to pytest.warns:
> matches
> E Use context-manager form instead?
>
> tests/test__default.py:95: TypeError
> === warnings summary
> ===
> .pybuild/cpython3_3.9_google-auth/build/tests/test_jwt.py::test_decode_valid
>
> /<>/.pybuild/cpython3_3.9_google-auth/build/google/auth/jwt.py:221:
> DeprecationWarning: Using or importing the ABCs from 'collections' instead
> of from 'collections.abc' is deprecated since Python 3.3, and in 3.10 it will
> stop working
> if isinstance(certs, collections.Mapping):
>
> -- Docs: https://docs.pytest.org/en/stable/warnings.html
> === short test summary info
>
> FAILED
> tests/test__default.py::test__load_credentials_from_file_authorized_user_cloud_sdk
> === 1 failed, 251 passed, 1 warning in 1.02s
> ===
> E: pybuild pybuild:353: test: plugin distutils failed with: exit code=1: cd
> /<>/.pybuild/cpython3_3.9_google-auth/build; python3.9 -m pytest
> --ignore=tests/transport
> dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p 3.9
> returned exit code 13
> make: *** [debian/rules:10: build] Error 25
> dpkg-buildpackage: error: debian/rules build subprocess returned exit status 2
--- End Message ---
--- Begin Message ---
Source: python-google-auth
Source-Version: 1.5.1-3
Done: Thomas Goirand
We believe that the bug you reported is fixed in the latest version of
python-google-auth, which is due to be installed in the Debian FTP archive.
A summary
Bug#978248: marked as done (openvswitch: FTBFS: configure: error: Could not find DPDK library in default search path, Use --with-dpdk to specify the DPDK library installed in non-standard location)
Your message dated Mon, 4 Jan 2021 15:03:37 +0100 with message-id <68248768-9f4c-47d2-bd2b-bc745c3b7...@infomaniak.com> and subject line Re: openvswitch: FTBFS: configure: error: Could not find DPDK library in default search path, Use --with-dpdk to specify the DPDK library installed in non-standard location has caused the Debian Bug report #978248, regarding openvswitch: FTBFS: configure: error: Could not find DPDK library in default search path, Use --with-dpdk to specify the DPDK library installed in non-standard location 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.) -- 978248: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=978248 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: openvswitch Version: 2.13.0+dfsg1-13 Severity: serious Justification: FTBFS on amd64 Tags: bullseye sid ftbfs Usertags: ftbfs-20201226 ftbfs-bullseye Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > checking whether RTE_IBVERBS_LINK_DLOPEN is declared... (cached) no > checking for library containing mlx4dv_init_obj... -lmlx4 > checking for library containing verbs_init_cq... (cached) -libverbs > checking for library containing dlopen... -ldl > checking whether linking with dpdk works... no > configure: error: Could not find DPDK library in default search path, Use > --with-dpdk to specify the DPDK library installed in non-standard location > make[1]: *** [debian/rules:26: override_dh_auto_configure] Error 1 > make[1]: Leaving directory '/<>' The full build log is available from: http://qa-logs.debian.net/2020/12/26/openvswitch_2.13.0+dfsg1-13_unstable.log A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! If you reassign this bug to another package, please marking it as 'affects'-ing this package. See https://www.debian.org/Bugs/server-control#affects If you fail to reproduce this, please provide a build log and diff it with me so that we can identify if something relevant changed in the meantime. About the archive rebuild: The rebuild was done on EC2 VM instances from Amazon Web Services, using a clean, minimal and up-to-date chroot. Every failed build was retried once to eliminate random failures. --- End Message --- --- Begin Message --- Hi, Thanks for the above investigation, bug and merge requests. I also don't think an upload is needed, and that the bug is really located in libpcap indeed, so I'm just closing this bug with no further action then. Thanks again, Cheers, Thomas Goirand (zigo)--- End Message ---
Bug#977087: marked as pending in python-google-auth
Control: tag -1 pending Hello, Bug #977087 in python-google-auth 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/openstack-team/python/python-google-auth/-/commit/243002eb409c82f5d32436df6c0dad060df64804 * Add patches (Closes: #977087): - fix-unit-test-using-collections.patch - remove_test__load_credentials_from_file_authorized_user_cloud_sdk.patch (this message was generated automatically) -- Greetings https://bugs.debian.org/977087
Processed: Bug#977087 marked as pending in python-google-auth
Processing control commands: > tag -1 pending Bug #977087 [src:python-google-auth] python-google-auth FTBFS with pytest 6 Added tag(s) pending. -- 977087: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=977087 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
