Bug#1004331: pytorch: b-d on python3-all-dev, but not built for all supported Python3 versions
Source: pytorch Version: 1.8.1-3 Severity: serious Tags: ftbfs User: debian-pyt...@lists.debian.org Usertags: python3.10 python3-all-dev Hi Maintainer This package build-depends on python3-all-dev, but does not build extensions/libraries for all supported python3 versions. This is seen on the transition tracker for adding python3.10 support [1] and creates false positives. Please either replace the b-d python3-all-dev with python3-dev, or build for all supported Python3 versions. With the former solution yet get later exposure to a new python3 version, with the latter solution you get early exposure. Regards Graham [1] https://release.debian.org/transitions/html/python3.10-add.html
Bug#1003606: marked as done (python3-flask-httpauth: missing Breaks+Replaces: python-flask-httpauth-doc (<< 4))
Your message dated Tue, 25 Jan 2022 06:03:46 + with message-id and subject line Bug#1003606: fixed in python-flask-httpauth 4.5.0-4 has caused the Debian Bug report #1003606, regarding python3-flask-httpauth: missing Breaks+Replaces: python-flask-httpauth-doc (<< 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.) -- 1003606: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1003606 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: python3-flask-httpauth Version: 4.5.0-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 without declaring a Breaks+Replaces relation. See policy 7.6 at https://www.debian.org/doc/debian-policy/ch-relationships.html#overwriting-files-and-replacing-packages-replaces >From the attached log (scroll to the bottom...): Preparing to unpack .../python3-flask-httpauth_4.5.0-1_all.deb ... Unpacking python3-flask-httpauth (4.5.0-1) ... dpkg: error processing archive /var/cache/apt/archives/python3-flask-httpauth_4.5.0-1_all.deb (--unpack): trying to overwrite '/usr/share/man/man1/flask-httpauth.1.gz', which is also in package python-flask-httpauth-doc 3.2.4-3.1 Errors were encountered while processing: /var/cache/apt/archives/python3-flask-httpauth_4.5.0-1_all.deb Obviously the manpage was moved between the packages. cheers, Andreas python-flask-httpauth-doc=3.2.4-3.1_python3-flask-httpauth=4.5.0-1.log.gz Description: application/gzip --- End Message --- --- Begin Message --- Source: python-flask-httpauth Source-Version: 4.5.0-4 Done: Martina Ferrari We believe that the bug you reported is fixed in the latest version of python-flask-httpauth, 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 1003...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Martina Ferrari (supplier of updated python-flask-httpauth package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Tue, 25 Jan 2022 04:36:56 + Source: python-flask-httpauth Architecture: source Version: 4.5.0-4 Distribution: unstable Urgency: medium Maintainer: Martina Ferrari Changed-By: Martina Ferrari Closes: 1003606 Changes: python-flask-httpauth (4.5.0-4) unstable; urgency=medium . * Another attempt at fixing the manpage. (Hopefully) closes: #1003606 Checksums-Sha1: d32623b7f8b49f26751f0971116b5d43f0bef183 2220 python-flask-httpauth_4.5.0-4.dsc ecb866d5bb098f89e631f72e5e15c8ae42c8e604 5412 python-flask-httpauth_4.5.0-4.debian.tar.xz 3907341d9d4923abd515923bbcbd62d0824ad283 8450 python-flask-httpauth_4.5.0-4_amd64.buildinfo Checksums-Sha256: 99df9fec82237a6fcab7f5c2f6d10015025fcefbe820320ad0d4b21dc765662d 2220 python-flask-httpauth_4.5.0-4.dsc 4ebd5185bed2c1595b51506022caafd77f3e058e675143432885dee3d65d8de1 5412 python-flask-httpauth_4.5.0-4.debian.tar.xz f920e15f66b4ab09cc59ad365855d4217a711f69a20ff3bf5c7d5431d1f38bf1 8450 python-flask-httpauth_4.5.0-4_amd64.buildinfo Files: 1997b7372bc323140ced99a0e8896271 2220 python optional python-flask-httpauth_4.5.0-4.dsc 72bc1c8b24a3b2bae346e8b16cc300a0 5412 python optional python-flask-httpauth_4.5.0-4.debian.tar.xz 41c4c377435294914d4dcaf0e1eb0bed 8450 python optional python-flask-httpauth_4.5.0-4_amd64.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEE2qbv8cYn6hwmsaaSqiMPxF+MJ7EFAmHvfrUACgkQqiMPxF+M J7E6Sw//WFTD1UXki6w8riHFEPR/eqG40WmmmxqpMk4RpwVttjqhVjU0V8QLZlzO a5oKTD7Hw97o4d/D/Bi6vAhrp73LStNa/jEQwWnLgioAedEa7ck+daJs4+DtyI+D u38IWdca/ERzGSDyWzgC8l2aPD0vqi7N9nSAfe/jeoatvxjN9UzRfzPbC+eNhJ9u 4SYXxJbC/Iv4Sm93NAgUUlZ2LAVWV/9xyi1cErsNN8Feurx9ckhHQP43dmoKcK5Z mSDb/4iQJgCJMOgQ+iNaXIKdxsRrWciOr2bw+RhLSnSaQ24nIeaOSfd//WogkHuz nYbcuaHMiDNT68BKwCCZDCbXfdd7Hd28TZ2Lf4QDXFoJY0z3nOtY5fiTtUpEM0Fm 62ClCkYdhqzXDvNPSB3ITy/zfZjIF6OT3Q7FpJUaBvayKknS2upEAMl9heB2lia+ nmIuq/TCR+UblvotPxGIs9RfVOYyZz7suN9QttdZnOqbDgbf+qaoFib95rh3oIDo lSCGrVySh5K0V89hli06AjP9TCBZxmdROjS0nsgprYlyURTEAy6Mv3FMXaIYjqZk
Processed: tagging 1004330
Processing commands for cont...@bugs.debian.org: > tags 1004330 + bookworm sid Bug #1004330 [dokuwiki] dokuwiki: No more works with PHP 8.1: Array and string offset access syntax with curly braces is no longer supported in /usr/share/dokuwiki/inc/init.php on line 557 Added tag(s) bookworm and sid. > thanks Stopping processing here. Please contact me if you need assistance. -- 1004330: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1004330 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1004330: dokuwiki: No more works with PHP 8.1: Array and string offset access syntax with curly braces is no longer supported in /usr/share/dokuwiki/inc/init.php on line 557
Package: dokuwiki
Severity: serious
Version: 0.0.20180422.a-2.1
Tags: fixed-upstream
Dokuwiki broke when PHP was upgraded to 8.1 (now in testing):
[Tue Jan 25 03:54:31.666206 2022] [php:error] [pid 1959] [client
127.0.0.1:39658] PHP Fatal error: Array and string offset access syntax with
curly braces is no longer supported in /usr/share/dokuwiki/inc/init.php on line
557
This is very likely fixed upstream, either in the not yet packaged
upstream release 2020-07-29 “Hogfather” ("some preparations for the
upcoming PHP8") or in the upcoming upstream release "Igor" ("Fix various
errors in PHP8 support").
-- System Information:
Debian Release: bookworm/sid APT prefers testing
(Bug report not written on the server where the issue occurs.)
Processed: See #1003569
Processing commands for cont...@bugs.debian.org:
> severity 1002254 important
Bug #1002254 [src:lookatme] lookatme: FTBFS: dh_auto_test: error: pybuild
--test --test-pytest -i python{version} -p 3.9 returned exit code 13
Severity set to 'important' from 'serious'
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
1002254: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1002254
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Processed: Merge duplicates
Processing commands for cont...@bugs.debian.org:
> reassign 1002397 src:nbconvert
Bug #1002397 [src:qiskit-terra] qiskit-terra: FTBFS: dh_auto_test: error:
pybuild --test -i python{version} -p "3.10 3.9" returned exit code 13
Bug reassigned from package 'src:qiskit-terra' to 'src:nbconvert'.
No longer marked as found in versions qiskit-terra/0.12.0-2.1.
Ignoring request to alter fixed versions of bug #1002397 to the same values
previously set
> forcemerge 1002372 1002397
Bug #1002372 {Done: Gordon Ball } [src:nbconvert]
nbconvert: FTBFS: AttributeError: module 'mistune' has no attribute
'BlockGrammar'
Bug #1002397 [src:nbconvert] qiskit-terra: FTBFS: dh_auto_test: error: pybuild
--test -i python{version} -p "3.10 3.9" returned exit code 13
Set Bug forwarded-to-address to
'https://github.com/jupyter/nbconvert/issues/1685'.
Severity set to 'serious' from 'important'
999540 was blocked by: 1002372
999540 was not blocking any bugs.
Added blocking bug(s) of 999540: 1002397
1002317 was blocked by: 1002372
1002317 was not blocking any bugs.
Added blocking bug(s) of 1002317: 1002397
1002317 was blocked by: 1002372 1002397
1002317 was not blocking any bugs.
Ignoring request to alter blocking bugs of bug #1002317 to the same blocks
previously set
999540 was blocked by: 1002372 1002397
999540 was not blocking any bugs.
Ignoring request to alter blocking bugs of bug #999540 to the same blocks
previously set
Marked Bug as done
Added indication that 1002397 affects src:mdtraj,src:qiskit-terra
Marked as fixed in versions nbconvert/6.3.0-1.
Marked as found in versions nbconvert/6.1.0-1.
Merged 1002372 1002397
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
1002317: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1002317
1002372: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1002372
1002397: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1002397
999540: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=999540
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Processed: Merge duplicates
Processing commands for cont...@bugs.debian.org:
> reassign 1002317 src:qiskit-terra
Bug #1002317 [src:qiskit-aer] qiskit-aer: FTBFS: dh_auto_test: error: pybuild
--test -i python{version} -p "3.10 3.9" returned exit code 13
Bug reassigned from package 'src:qiskit-aer' to 'src:qiskit-terra'.
No longer marked as found in versions qiskit-aer/0.4.1-2.
Ignoring request to alter fixed versions of bug #1002317 to the same values
previously set
> forcemerge 999540 1002317
Bug #999540 [src:qiskit-terra] qiskit-terra: FTBFS with matplotlib 3.5 (in
experimental): dh_auto_test: error: pybuild --test -i python{version} -p 3.9
returned exit code 13
Bug #1002317 [src:qiskit-terra] qiskit-aer: FTBFS: dh_auto_test: error: pybuild
--test -i python{version} -p "3.10 3.9" returned exit code 13
1002317 was not blocked by any bugs.
1002317 was not blocking any bugs.
Added blocking bug(s) of 1002317: 1002372
Marked as found in versions qiskit-terra/0.12.0-2.1.
Merged 999540 1002317
> affects 999540 src:qiskit-aer
Bug #999540 [src:qiskit-terra] qiskit-terra: FTBFS with matplotlib 3.5 (in
experimental): dh_auto_test: error: pybuild --test -i python{version} -p 3.9
returned exit code 13
Bug #1002317 [src:qiskit-terra] qiskit-aer: FTBFS: dh_auto_test: error: pybuild
--test -i python{version} -p "3.10 3.9" returned exit code 13
Added indication that 999540 affects src:qiskit-aer
Added indication that 1002317 affects src:qiskit-aer
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
1002317: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1002317
999540: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=999540
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Processed: severity of 1002397 is important
Processing commands for cont...@bugs.debian.org:
> severity 1002397 important
Bug #1002397 [src:qiskit-terra] qiskit-terra: FTBFS: dh_auto_test: error:
pybuild --test -i python{version} -p "3.10 3.9" returned exit code 13
Severity set to 'important' from 'serious'
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
1002397: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1002397
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Processed: bug 1002143 is forwarded to https://gitlab.freedesktop.org/xorg/driver/xf86-video-qxl/-/issues/12
Processing commands for cont...@bugs.debian.org: > forwarded 1002143 > https://gitlab.freedesktop.org/xorg/driver/xf86-video-qxl/-/issues/12 Bug #1002143 [src:xserver-xorg-video-qxl] xserver-xorg-video-qxl: FTBFS: xf86Opt.h:44:10: error: two or more data types in declaration specifiers Set Bug forwarded-to-address to 'https://gitlab.freedesktop.org/xorg/driver/xf86-video-qxl/-/issues/12'. > thanks Stopping processing here. Please contact me if you need assistance. -- 1002143: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1002143 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: tagging 999519
Processing commands for cont...@bugs.debian.org:
> tags 999519 + fixed
Bug #999519 {Done: Stefano Rivera } [src:xrayutilities]
xrayutilities: FTBFS with matplotlib 3.5 (in experimental): dh_auto_test:
error: pybuild --test -i python{version} -p 3.9 -s custom
"--test-args={interpreter} {dir}/setup.py egg_info -e {build_dir}; cd
{build_dir}; {interpreter} -m unittest2 discover -v;" returned exit code 13
Added tag(s) fixed.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
999519: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=999519
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#999824: ima-evm-utils: missing evm portable signature verification in tooling
A7m 24.01.22 um 13:36 schrieb Bastian Germann:
Control: retitle -1 ima-evm-utils: FTBFS because of the signature
verification unit tests
Control: severity -1 serious
On Wed, 17 Nov 2021 10:35:05 +0100 Steffen Kothe wrote:
EVM signatures can be created with the option '--portable | -o ' to
get rid of a hashing of i_version and fsuuid.
When files should be verified after a signing with '--portable' on the
host, the tooling returns with "Verification failed" unless
the signing itself is correct.
The cause for this issue is a missing implementation for the probing
and verification of portable signatures.
A patch for this issue is already available in the official git source
of the ima-evm-utils tooling:
https://git.code.sf.net/p/linux-ima/ima-evm-utils
f4b901d081ec ("Add support for verifying portable EVM signatures")
The wrong checking of the signature format results in a false-positive
error.
Note, that this bug also affects version 1.3.2-2.1 provided
by Debian/SID https://packages.debian.org/sid/ima-evm-utils.
The official release 1.4 of the ima-evm-utils contains this fixes.
Version 1.4 was imported but still fails to build from scratch on buildd
because the unit tests for
that new feature do not run without gnutls-bin and softhsm2 installed as
build dependencies.
I did not catch that building my NMU in a clean sid chroot. I do not
know why, it still
builds in that chroot and claims two of the three test to succeed with
those packages uninstalled.
I cross built the package via dpkg-buildpackage --host-arch=armhf
on an x86 Buster host:
1 test skipped, 1 passed, 1 failed.
After some research, I figured out, that the evmctl -engine pkcs11
flagging caused an error since the "libengine-pkcs11-openssl" seems not
not be referenced properly in Build-depends:
After apt install libengine-pkcs11-openssl:arm64 on my host, test
succeeded. Have to confirm this behavior on a clean native ARM64 target.
I guess somebody forgot the pkcs11 backend engine.
Same story for x86.
Mit freundlichen Grüßen / Kind Regards
--
Steffen Kothe
Linutronix GmbH | Bahnhofstrasse 3 | D-88690 Uhldingen-Mühlhofen
Phone: +49 7556 25 999 38; Fax.: +49 7556 25 999 99
Hinweise zum Datenschutz finden Sie hier (Informations on data privacy
can be found here): https://linutronix.de/kontakt/Datenschutz.php
Linutronix GmbH | Firmensitz (Registered Office): Uhldingen-Mühlhofen |
Registergericht (Registration Court): Amtsgericht Freiburg i.Br., HRB700
806 | Geschäftsführer (Managing Directors): Heinz Egger, Thomas Gleixner
Bug#1004321: marked as done (fwupd-amd64-signed-template: missing package name in files.json)
Your message dated Mon, 24 Jan 2022 22:49:31 +
with message-id
and subject line Bug#1004321: fixed in fwupd-efi 1:1.2-1
has caused the Debian Bug report #1004321,
regarding fwupd-amd64-signed-template: missing package name in files.json
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.)
--
1004321: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1004321
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: fwupd-amd64-signed-template
Version: 1:1.1-5
Severity: serious
The package name is missing in the third line of the generated files.json:
+---
| {
| "packages": {
| "": {
| "trusted_certs": [],
| "files": [
| {"sig_type": "efi", "file": "usr/libexec/fwupd/efi/fwupdx64.efi"}
| ]
| }
| }
| }
+---[ usr/share/code-signing/fwupd-amd64-signed-template/files.json ]
Ansgar
--- End Message ---
--- Begin Message ---
Source: fwupd-efi
Source-Version: 1:1.2-1
Done: Mario Limonciello
We believe that the bug you reported is fixed in the latest version of
fwupd-efi, 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 1004...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Mario Limonciello (supplier of updated fwupd-efi 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, 24 Jan 2022 16:31:44 -0600
Source: fwupd-efi
Architecture: source
Version: 1:1.2-1
Distribution: unstable
Urgency: medium
Maintainer: Debian EFI
Changed-By: Mario Limonciello
Closes: 1004321
Changes:
fwupd-efi (1:1.2-1) unstable; urgency=medium
.
* Update to 1.2 version.
* Fix the JSON file generation for fwupd/fwupd-efi split (Closes: #1004321)
Checksums-Sha1:
08f79a297fbf547978d22ee58b03cbca807025a4 2535 fwupd-efi_1.2-1.dsc
09a6704cc63afde72d26d7ded47009e9131dbf41 38867 fwupd-efi_1.2.orig.tar.gz
5262481c5265049419e2b61c59df291ebc9128ab 8608 fwupd-efi_1.2-1.debian.tar.xz
f73d7c6206597812454599dbb113d1df9ee662a6 7595 fwupd-efi_1.2-1_source.buildinfo
Checksums-Sha256:
9d466f970fb39eeb888d6d73e3085c92085288e6fd23288e335312fbcb879cd2 2535
fwupd-efi_1.2-1.dsc
568fa4a9eb884821661d47d0c04ad5681ffe26346a1f8186a068efe56854b77b 38867
fwupd-efi_1.2.orig.tar.gz
5793a15eb52692ae8002b7a1893023ac4bdb1d11c632a0a940c4952535ad5eaa 8608
fwupd-efi_1.2-1.debian.tar.xz
c7aa9a8f12a1026299a6ad6de4809d52b7668d28a8c99a206d57553851c20886 7595
fwupd-efi_1.2-1_source.buildinfo
Files:
e349c31eda575105f3dfc61c294f77f2 2535 admin optional fwupd-efi_1.2-1.dsc
8cdcd0fd4e784330e985b4d1bb032211 38867 admin optional fwupd-efi_1.2.orig.tar.gz
1da651f2b2e5f165e3fdac1b28cc90a1 8608 admin optional
fwupd-efi_1.2-1.debian.tar.xz
e98626a42bc127ce45f242587bfb2bf6 7595 admin optional
fwupd-efi_1.2-1_source.buildinfo
-BEGIN PGP SIGNATURE-
iQJGBAEBCgAwFiEECwtuSU6dXvs5GA2aLRkspiR3AnYFAmHvKVkSHHN1cGVybTFA
Z21haWwuY29tAAoJEC0ZLKYkdwJ2RPIP/06kcFke0qiVYMSFGLiejsLJxPcZ482B
nPkn+Nk9WAIsILYL8IJUUbRhz3swT0PDjyXfDh0bQS9x7p/OauElAVuTpdbdN1ve
wxfIp2IDqMIvgYfm1lTxPJ5kbiqbrnSLpmBipjnV32YHgy3ciPFFsQ/GZprrpeb2
UkKWSFcESGW++odpoL0QAhOybLJAeWVr1kxSmFVfGPhNTw1r0Sq6bGrJieC6/G1P
WbgF+mF7ef1+b0kJAz+r2E9yhW5pcsmdvNxxaLEIWs3Lz4T/obs/a5YAIKu6GNHN
HZd1Pss3NtpCTHhuvukLlQJjohitfB+b88Qb8QNctjm3sWhzjB/mMzo/YGD8bEdn
PHHp8FDLkd8BHYq+oL/bw1hmoSWg96pGHFXzSA9+bH9t962Uy+gLLGibDLy499fu
VWqhBPHWEn7M/ZjgBspjWfSlMP+jUb9EfITiItSHXgHJONj4iOm7YAKVIVzJEST3
sQYDgAKxH45PrZpj2E9AqGtww+9JqrJEqBE+hMopnTY2POa9SLhc4fVMU7utKaNu
JC19e3L7oXL6yGQ1WS52fQej3iLMQj4rBqtCY0P6R/9y2vnVIPsbsErc0xtXlNuN
TBsFcj562bDEIxPRACnR+IcCwH+/6ts8tKen+JJE4q5CxesqlhhXah13VRtN5hbC
qP0E4fsC5lWF
=nuls
-END PGP SIGNATURE End Message ---
Bug#1004321: fwupd-amd64-signed-template: missing package name in files.json
Package: fwupd-amd64-signed-template
Version: 1:1.1-5
Severity: serious
The package name is missing in the third line of the generated files.json:
+---
| {
| "packages": {
| "": {
| "trusted_certs": [],
| "files": [
| {"sig_type": "efi", "file": "usr/libexec/fwupd/efi/fwupdx64.efi"}
| ]
| }
| }
| }
+---[ usr/share/code-signing/fwupd-amd64-signed-template/files.json ]
Ansgar
Bug#1002210: marked as done (adapt: FTBFS: dh_auto_test: error: pybuild --test -i python{version} -p "3.10 3.9" returned exit code 13)
Your message dated Mon, 24 Jan 2022 21:34:17 +
with message-id
and subject line Bug#1002210: fixed in adapt 1.0.0-1.1
has caused the Debian Bug report #1002210,
regarding adapt: FTBFS: dh_auto_test: error: pybuild --test -i python{version}
-p "3.10 3.9" returned exit code 13
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
1002210: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1002210
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: adapt
Version: 1.0.0-1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20211220 ftbfs-bookworm
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> debian/rules binary
> dh binary --with python3 --buildsystem=pybuild
>dh_update_autotools_config -O--buildsystem=pybuild
>dh_autoreconf -O--buildsystem=pybuild
>dh_auto_configure -O--buildsystem=pybuild
> I: pybuild base:237: python3.10 setup.py config
> running config
> I: pybuild base:237: python3.9 setup.py config
> running config
>dh_auto_build -O--buildsystem=pybuild
> I: pybuild base:237: /usr/bin/python3.10 setup.py build
> running build
> running build_py
> creating /<>/.pybuild/cpython3_3.10_adapt/build/adapt
> copying adapt/__init__.py ->
> /<>/.pybuild/cpython3_3.10_adapt/build/adapt
> copying adapt/parser.py ->
> /<>/.pybuild/cpython3_3.10_adapt/build/adapt
> copying adapt/engine.py ->
> /<>/.pybuild/cpython3_3.10_adapt/build/adapt
> copying adapt/intent.py ->
> /<>/.pybuild/cpython3_3.10_adapt/build/adapt
> copying adapt/expander.py ->
> /<>/.pybuild/cpython3_3.10_adapt/build/adapt
> copying adapt/context.py ->
> /<>/.pybuild/cpython3_3.10_adapt/build/adapt
> copying adapt/entity_tagger.py ->
> /<>/.pybuild/cpython3_3.10_adapt/build/adapt
> creating /<>/.pybuild/cpython3_3.10_adapt/build/adapt/tools
> copying adapt/tools/__init__.py ->
> /<>/.pybuild/cpython3_3.10_adapt/build/adapt/tools
> creating /<>/.pybuild/cpython3_3.10_adapt/build/adapt/tools/text
> copying adapt/tools/text/__init__.py ->
> /<>/.pybuild/cpython3_3.10_adapt/build/adapt/tools/text
> copying adapt/tools/text/trie.py ->
> /<>/.pybuild/cpython3_3.10_adapt/build/adapt/tools/text
> copying adapt/tools/text/tokenizer.py ->
> /<>/.pybuild/cpython3_3.10_adapt/build/adapt/tools/text
> creating /<>/.pybuild/cpython3_3.10_adapt/build/adapt/tools/debug
> copying adapt/tools/debug/__init__.py ->
> /<>/.pybuild/cpython3_3.10_adapt/build/adapt/tools/debug
> I: pybuild base:237: /usr/bin/python3 setup.py build
> running build
> running build_py
> creating /<>/.pybuild/cpython3_3.9_adapt/build/adapt
> copying adapt/__init__.py ->
> /<>/.pybuild/cpython3_3.9_adapt/build/adapt
> copying adapt/parser.py ->
> /<>/.pybuild/cpython3_3.9_adapt/build/adapt
> copying adapt/engine.py ->
> /<>/.pybuild/cpython3_3.9_adapt/build/adapt
> copying adapt/intent.py ->
> /<>/.pybuild/cpython3_3.9_adapt/build/adapt
> copying adapt/expander.py ->
> /<>/.pybuild/cpython3_3.9_adapt/build/adapt
> copying adapt/context.py ->
> /<>/.pybuild/cpython3_3.9_adapt/build/adapt
> copying adapt/entity_tagger.py ->
> /<>/.pybuild/cpython3_3.9_adapt/build/adapt
> creating /<>/.pybuild/cpython3_3.9_adapt/build/adapt/tools
> copying adapt/tools/__init__.py ->
> /<>/.pybuild/cpython3_3.9_adapt/build/adapt/tools
> creating /<>/.pybuild/cpython3_3.9_adapt/build/adapt/tools/text
> copying adapt/tools/text/__init__.py ->
> /<>/.pybuild/cpython3_3.9_adapt/build/adapt/tools/text
> copying adapt/tools/text/trie.py ->
> /<>/.pybuild/cpython3_3.9_adapt/build/adapt/tools/text
> copying adapt/tools/text/tokenizer.py ->
> /<>/.pybuild/cpython3_3.9_adapt/build/adapt/tools/text
> creating /<>/.pybuild/cpython3_3.9_adapt/build/adapt/tools/debug
> copying adapt/tools/debug/__init__.py ->
> /<>/.pybuild/cpython3_3.9_adapt/build/adapt/tools/debug
>dh_auto_test -O--buildsystem=pybuild
> I: pybuild base:237: cd /<>/.pybuild/cpython3_3.10_adapt/build;
> python3.10 -m unittest discover -v
> adapt.tools.debug (unittest.loader._FailedTest) ... ERROR
>
> ==
> ERROR: adapt.tools.debug (unittest.loader._FailedTest)
> --
> ImportError: Failed to import test module: adapt.tools.debug
> Traceback (most recent call last):
> File "/usr/lib/python3.10/unittest/loader.py", line 470, in _find_test_path
> package = self._get_module_from_name(name)
> File
Bug#1002210: adapt: diff for NMU version 1.0.0-1.1
On Mon, Jan 24, 2022 at 06:38:21PM +0200, Wouter Verhelst wrote: > Thanks! > > The delay is absolutely not necessary; feel free to redirect to a direct > upload. Thanks, rescheduled for immediate upload. cu Adrian
Bug#996747: src:debianutils: fails to migrate to testing for too long: blocked by sramacher
Hi Sebastian, On Fri, 21 Jan 2022 13:52:15 +0100 Johannes Schauer Marin Rodrigues wrote: > Sebastian, do you think that this is a solution that would allow debianutils > to > be unblocked from migration to testing? the recent debianutils NMU by waldi implements the tech ctte decisions. Could you consider unblocking debianutils so that it can transition to testing? Thanks! cheers, josch signature.asc Description: signature
Processed: fixed
Processing commands for cont...@bugs.debian.org:
> package nheko
Limiting to bugs with field 'package' containing at least one of 'nheko'
Limit currently set to 'package':'nheko'
> notfound 1002679 0.9.0-1
Bug #1002679 {Done: Hubert Chathi } [nheko] nheko depends on
gstreamer1.0-qt5 which is not available on armel/armhf
No longer marked as found in versions nheko/0.9.0-1.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
1002679: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1002679
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Processed: Re: bctoolbox: ftbfs with GCC-11
Processing control commands: > tags -1 patch fixed-upstream Bug #983985 [src:bctoolbox] bctoolbox: ftbfs with GCC-11 Added tag(s) patch and fixed-upstream. -- 983985: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=983985 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#983985: bctoolbox: ftbfs with GCC-11
Control: tags -1 patch fixed-upstream Upstream has that fixed with https://gitlab.linphone.org/BC/public/bctoolbox/-/commit/9ac0e412c45bf28d02829e9d912342359714f638
Bug#999824: marked as done (ima-evm-utils: FTBFS without extended attributes support)
Your message dated Mon, 24 Jan 2022 18:20:03 +
with message-id
and subject line Bug#999824: fixed in ima-evm-utils 1.4-1.2
has caused the Debian Bug report #999824,
regarding ima-evm-utils: FTBFS without extended attributes support
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.)
--
999824: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=999824
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: ima-evm-utils
Version: 1.1-1+b1
Severity: normal
Dear Maintainer,
EVM signatures can be created with the option '--portable | -o ' to get
rid of a hashing of i_version and fsuuid.
When files should be verified after a signing with '--portable' on the
host, the tooling returns with "Verification failed" unless
the signing itself is correct.
The cause for this issue is a missing implementation for the probing
and verification of portable signatures.
A patch for this issue is already available in the official git source
of the ima-evm-utils tooling:
https://git.code.sf.net/p/linux-ima/ima-evm-utils
f4b901d081ec ("Add support for verifying portable EVM signatures")
The wrong checking of the signature format results in a false-positive
error.
Note, that this bug also affects version 1.3.2-2.1 provided
by Debian/SID https://packages.debian.org/sid/ima-evm-utils.
The official release 1.4 of the ima-evm-utils contains this fixes.
Please update the package version near-term.
Note:
ima-evm-utils were installed on my host manually since Debian Buster
does not provide a mainline ima-evm-utils version.
Thanks,
Steffen
The mentioned version above
-- System Information:
Debian Release: 10.11
APT prefers oldstable-updates
APT policy: (500, 'oldstable-updates'), (500, 'oldstable')
Architecture: amd64 (x86_64)
Foreign Architectures: armhf, arm64
Kernel: Linux 4.19.0-18-amd64 (SMP w/8 CPU cores)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8),
LANGUAGE= (charmap=UTF-8)
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages ima-evm-utils depends on:
ii attr 1:2.4.48-4
ii keyutils 1.6-6
ii libc6 2.28-10
ii libimaevm01.1-1+b1
ii libkeyutils1 1.6-6
ii libssl1.1 1.1.1d-0+deb10u7
ima-evm-utils recommends no packages.
ima-evm-utils suggests no packages.
-- no debconf information
--- End Message ---
--- Begin Message ---
Source: ima-evm-utils
Source-Version: 1.4-1.2
Done: Bastian Germann
We believe that the bug you reported is fixed in the latest version of
ima-evm-utils, 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 999...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Bastian Germann (supplier of updated ima-evm-utils 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, 24 Jan 2022 18:33:09 +0100
Source: ima-evm-utils
Architecture: source
Version: 1.4-1.2
Distribution: unstable
Urgency: high
Maintainer: Dmitry Baryshkov
Changed-By: Bastian Germann
Closes: 953929 999824
Changes:
ima-evm-utils (1.4-1.2) unstable; urgency=high
.
* Non-maintainer upload.
* d/control: Drop unnecessary build dependency libattr1-dev (Closes: #953929)
* d/rules: Skip tests (many depend on extended attrs, Closes: #999824)
Checksums-Sha1:
dcb68900a9a4ca6478237f563887d17ef04d71f3 1947 ima-evm-utils_1.4-1.2.dsc
59bed47d5213ba5c2d14a68248b503a63720c902 5896
ima-evm-utils_1.4-1.2.debian.tar.xz
6f203f405e7d6e4677d3f722a2359c463a368d67 6353
ima-evm-utils_1.4-1.2_source.buildinfo
Checksums-Sha256:
553d68e7ee5287d95a032f2281d23f3129f83c8fad184180059972084a9d2f3b 1947
ima-evm-utils_1.4-1.2.dsc
74ae485cfa7074fd9fe22468dbf78dc63d324a15d7057b5c620c31bc23b0772e 5896
ima-evm-utils_1.4-1.2.debian.tar.xz
7d2fe429ede4bc3f7fe32a0e6a16cae8614a37d0c02ffa56b3fb017b87bb5247 6353
ima-evm-utils_1.4-1.2_source.buildinfo
Files:
e9941259ee53484b59c4a0ef099cdddc 1947 utils optional ima-evm-utils_1.4-1.2.dsc
32e6d4500cfcd8d8350afdf78d37b345 5896 utils optional
ima-evm-utils_1.4-1.2.debian.tar.xz
891aed51ef8d41d6daf4398fd2949f11 6353 utils optional
Bug#999155: ping
On 24.01.22 18:02, Mark Brown wrote: On Mon, Jan 24, 2022 at 05:51:43PM +0100, Thorsten Alteholz wrote: In order have some activity on this bug and to avoid autoremoval of dependencies, this is a reminder of outstanding things to do ... Please don't send content free pings, they just add noise and make it likely that it's going to take longer (since I remember that I did something but forget that it was just handling the ping). Please have a look at [1]. Those ping I send to the corresponding bugs reset the time of the autorm again. As I don't want my packages to be removed from testing, I am afraid you need to bear those pings. Thorsten [1] https://lists.debian.org/debian-devel-announce/2013/09/msg6.html
Bug#1004310: knxd: ftbfs with glibc 2.34: don't use common unix function name as variable name
Package: knxd
Version: 0.14.46-1
Severity: serious
Tags: patch experimental
Justification: ftbfs
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu jammy ubuntu-patch
Hi Matthias,
In Ubuntu, we have found that the knxd package fails to build from source
because glibc header dependencies mean that the link() declaration from
unistd.h is now exposed in a context it wasn't previously, leading to a
namespace conflict:
[...]
g++ -DHAVE_CONFIG_H -I. -I../.. -I../../src/libserver -I../../src/backend -I../
../src/common -I../../src/usb -I/usr/include/libusb-1.0 -Wno-missing-field-init
ializers -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 -ffile-prefix-map=/<>=. -flto=auto -ffat-lto-objects -flto=auto -ffat-lto-objects -fstack-protecto
r-strong -std=c++0x -Wno-subobject-linkage -MT knxd_args.o -MD -MP -MF .deps/knx
d_args.Tpo -c -o knxd_args.o knxd_args.cpp
knxd_args.cpp:71:13: error: ‘char link [99]’ redeclared as different kind of
entity
71 | char link[99] = "@.";
| ^
In file included from /usr/include/x86_64-linux-gnu/bits/sigstksz.h:24,
from /usr/include/signal.h:328,
from /usr/include/ev.h:162,
from /usr/include/ev++.h:46,
from ../../src/libserver/common.h:31,
from ../../src/libserver/trace.h:40,
from knxd_args.cpp:29:
/usr/include/unistd.h:818:12: note: previous declaration ‘int link(const char*,
const char*)’
818 | extern int link (const char *__from, const char *__to)
|^~~~
[...]
(https://launchpad.net/ubuntu/+source/knxd/0.14.46-1build1/+build/22982832)
glibc 2.34 is currently in Debian experimental, so this problem will also
affect Debian soon.
I've uploaded the attached patch to Ubuntu to fix the build failure there;
please consider including it in Debian. You can of course choose any more
meaningful variable name of your choice if you don't like the one I've
chosen :), but I don't think it's worth the effort to try to mask the
standard symbol from the namespace in order to keep the current variable
name.
Thanks for considering,
--
Steve Langasek Give me a lever long enough and a Free OS
Debian Developer to set it on, and I can move the world.
Ubuntu Developer https://www.debian.org/
slanga...@ubuntu.com vor...@debian.org
diff -Nru knxd-0.14.46/debian/patches/glibc-2.34.patch
knxd-0.14.46/debian/patches/glibc-2.34.patch
--- knxd-0.14.46/debian/patches/glibc-2.34.patch1969-12-31
16:00:00.0 -0800
+++ knxd-0.14.46/debian/patches/glibc-2.34.patch2022-01-24
09:17:19.0 -0800
@@ -0,0 +1,151 @@
+Description: Fix build failure with glibc 2.34
+ The code uses a generic variable name of 'link' which collides with a
+ standard (unistd.h) function that as of glibc 2.34 happens to be
+ indirectly exposed in the namespace for this file. Address this by
+ renaming the variable.
+Author: Steve Langasek
+Last-Update: 2022-01-24
+Forwarded: no
+
+Index: knxd-0.14.46/src/server/knxd_args.cpp
+===
+--- knxd-0.14.46.orig/src/server/knxd_args.cpp
knxd-0.14.46/src/server/knxd_args.cpp
+@@ -68,13 +68,13 @@
+ } while(0)
+
+ IniData ini;
+-char link[99] = "@.";
++char link_target[99] = "@.";
+ void link_to(const char *arg)
+ {
+ char *p;
+- ++*link;
+- strcpy(link+2,arg);
+- p = strchr(link+2,':');
++ ++*link_target;
++ strcpy(link_target+2,arg);
++ p = strchr(link_target+2,':');
+ if (p)
+ *p = 0;
+ }
+@@ -163,10 +163,10 @@
+ {
+ link_to(name);
+ ITER(i, more_args)
+-(*ini[link])[i->first] = i->second;
+-(*ini[link])["filter"] = name;
++(*ini[link_target])[i->first] = i->second;
++(*ini[link_target])["filter"] = name;
+ more_args.clear();
+-filters.push_back(link);
++filters.push_back(link_target);
+ }
+ else
+ filters.push_back(name);
+@@ -232,7 +232,7 @@
+ {
+ va_list apl;
+ va_start(apl, ap);
+- (*ini[link])["driver"] = arg;
++ (*ini[link_target])["driver"] = arg;
+ char *pa = NULL;
+
+ while(ap)
+@@ -250,7 +250,7 @@
+ if (*pa == '!') // required-argument flag
+ pa++;
+ if (*ap) // skip empty arguments
+-(*ini[link])[pa] = ap;
++(*ini[link_target])[pa] = ap;
+ ap = p2;
+ }
+ if (pa != NULL)
+@@ -280,7 +280,7 @@
+ else if(!strcmp(arg,"iptn"))
+ {
+ driver_argsv("ipt",ap,
"!ip-address","dest-port","src-port","nat-ip","data-port", NULL);
+- (*ini[link])["nat"] = "true";
++ (*ini[link_target])["nat"] = "true";
+ }
+ else if(!strcmp(arg,"ft12") || !strcmp(arg,"ncn5120") ||
!strcmp(arg,"tpuarts") || !strcmp(arg,"ft12cemi") || !strcmp(arg,"tpuart"))
+ {
+@@ -556,18 +556,18 @@
+ if (arguments->want_server)
+ die("You need -S after -D/-T/-R");
+
Processed: NMU
Processing control commands: > tags -1 patch Bug #999824 [ima-evm-utils] ima-evm-utils: FTBFS without extended attributes support Added tag(s) patch. -- 999824: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=999824 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#999824: NMU
Control: tags -1 patch A debdiff that fixes this is enclosed. I am uploading a NMU again because my last one did not build on buildd.diff -Nru ima-evm-utils-1.4/debian/changelog ima-evm-utils-1.4/debian/changelog --- ima-evm-utils-1.4/debian/changelog 2022-01-24 10:49:06.0 +0100 +++ ima-evm-utils-1.4/debian/changelog 2022-01-24 18:33:09.0 +0100 @@ -1,3 +1,11 @@ +ima-evm-utils (1.4-1.2) unstable; urgency=high + + * Non-maintainer upload. + * d/control: Drop unnecessary build dependency libattr1-dev (Closes: #953929) + * d/rules: Skip tests (many depend on extended attrs, Closes: #999824) + + -- Bastian Germann Mon, 24 Jan 2022 18:33:09 +0100 + ima-evm-utils (1.4-1.1) unstable; urgency=high * Non-maintainer upload. diff -Nru ima-evm-utils-1.4/debian/control ima-evm-utils-1.4/debian/control --- ima-evm-utils-1.4/debian/control2022-01-24 10:49:06.0 +0100 +++ ima-evm-utils-1.4/debian/control2022-01-24 18:32:41.0 +0100 @@ -8,7 +8,6 @@ docbook-xml, docbook-xsl, attr, - libattr1-dev, libkeyutils-dev, libssl-dev, openssl, diff -Nru ima-evm-utils-1.4/debian/rules ima-evm-utils-1.4/debian/rules --- ima-evm-utils-1.4/debian/rules 2021-09-24 11:39:11.0 +0200 +++ ima-evm-utils-1.4/debian/rules 2022-01-24 18:33:09.0 +0100 @@ -4,3 +4,6 @@ %: dh $@ + +override_dh_auto_test: +# Many tests set extended attributes, which are not guaranteed to work on a system
Bug#997478: pyls-black: diff for NMU version 0.4.6-3.1
On Wed, Jan 19, 2022 at 07:22:50PM +0200, Adrian Bunk wrote: > Control: tags 997478 + patch > Control: tags 997478 + pending > > Dear maintainer, > > I've prepared an NMU for pyls-black (versioned as 0.4.6-3.1) and > uploaded it to DELAYED/15. Please feel free to tell me if I should > cancel it. > > cu > Adrian Dear Adrian, Many thanks for doing this! It will help keep things ticking over for the time being. I've been in discussion with the upstream Spyder developers, and they would like us to wait a few months before upgrading Spyder until they have released 5.3.0, as 5.2.x crashes on quitting when using the current PyQt5 (which is a little unfortunate). So this will help for now. (Though as python-language-server is also due for removal due to #1002351 and #999524, this fix may not be sufficient to keep Spyder in testing.) Once Spyder 5.3.0 is uploaded, we will be requesting the removal of pyls-black from the archive, as it has been superseded by pylsp-black. Best wishes, Julian
Processed: untag
Processing commands for cont...@bugs.debian.org: > tags 999824 - fixed-upstream Bug #999824 [ima-evm-utils] ima-evm-utils: FTBFS without extended attributes support Removed tag(s) fixed-upstream. > End of message, stopping processing here. Please contact me if you need assistance. -- 999824: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=999824 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1002210: adapt: diff for NMU version 1.0.0-1.1
Thanks! The delay is absolutely not necessary; feel free to redirect to a direct upload. -- Verstuurd vanaf mijn Android apparaat met K-9 Mail. Excuseer mijn beknoptheid.
Bug#999155: ping
On Mon, Jan 24, 2022 at 05:51:43PM +0100, Thorsten Alteholz wrote: > In order have some activity on this bug and to avoid autoremoval of > dependencies, this is a reminder of outstanding things to do ... Please don't send content free pings, they just add noise and make it likely that it's going to take longer (since I remember that I did something but forget that it was just handling the ping). signature.asc Description: PGP signature
Bug#999155: ping
In order have some activity on this bug and to avoid autoremoval of dependencies, this is a reminder of outstanding things to do ... Thorsten
Bug#998553: ping
In order have some activity on this bug and to avoid autoremoval of dependencies, this is a reminder of outstanding things to do ... Thorsten
Bug#1002532: pygments breaks ruby-pygments.rb autopkgtest: UTF-8 != ASCII-8BIT
On Sun, 23 Jan 2022 22:17:08 +0100 Mattia Rizzolo wrote: > On Fri, Jan 21, 2022 at 03:51:02PM +0100, Alexandre Ghiti wrote: > > I can't find how to create a MR in salsa, can you pull directly from here: > > > > https://salsa.debian.org/alexghiti/ruby-pygments.rb/-/tree/int/alex/2.3.0 > > > > It successfully built in my PPA, if you need any more modification, do > > not hesitate. > > Ah, another thing. Please be careful with the version you pick. > > You used 2.3.0+ds-1ubuntu1, which is *higher* than what I'll be > uploading, namely 2.3.0+ds-1. > Furthermore, in your PPA you used 2.3.0+ds-1ubuntu2, which would also > conflict with an eventual -1ubuntu done in the offical ubuntu archive. > > I'd recommend you used something like -0ppa1 or -0ubuntu1~ppa1 or > somesuch. > > (in this case this is of no consequence, but just something to note). Thanks for the advice. > > > > Lastly, I noticed that you haven't even touched the changelog. In this > case there was even a new copyright holder, so it really should have > been updated. Sorry and thanks for taking care of that. > I didn't add you to the paragraph of d/copyright, as I assume you are > doing this under your paid time, and I don't know what's Canonical's > rules regarding copyright here. If needed/wanted, just send me a note > and I'll update the copy in git. No problem. Regarding the autopkgtest failure (again an oversight on my part, sorry), I fixed it here, it works in my PPA and on an ubuntu jammy VM (I failed to make autopkgtest work with testing): https://salsa.debian.org/alexghiti/ruby-pygments.rb/-/commit/19442f7b89c5a6ca5ef1d8e1e6ebc42a261e441e Thanks again, Alex > > -- > regards, > Mattia Rizzolo > > GPG Key: 66AE 2B4A FCCF 3F52 DA18 4D18 4B04 3FCD B944 4540 .''`. > More about me: https://mapreri.org : :' : > Launchpad user: https://launchpad.net/~mapreri `. `'` > Debian QA page: https://qa.debian.org/developer.php?login=mattia `-
Bug#903586: marked as done (bind: fails to build twice in a row)
Your message dated Mon, 24 Jan 2022 15:48:52 + with message-id and subject line Bug#903586: fixed in bind9 1:9.18.0~0+git28350c-1 has caused the Debian Bug report #903586, regarding bind: fails to build twice in a row 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.) -- 903586: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=903586 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: bind Version: 1:9.13.1+dfsg-1 Severity: serious Justification: fails to build from source (but built successfully in the past) Hi, bind/experimental fails to build twice in a row. I didn't check whether bind9/sid has similar problems. The package seems to use autotools in "creative ways" causing autoreconf to no longer recognize that it needs to run libtoolize if libtool.m4/libtool.m4 is gone (because it was deleted by dh_autoreconf-clean). It is easily reproducible by the commands debian/rules override_dh_autoreconf debian/rules clean debian/rules override_dh_autoreconf The failure occurs early in the second build, full build log attached, notice the different output from the two dh_autoreconf runs: debian/rules build dh build --with python3 --fail-missing --exclude=.la --exclude=lwresd --exclude=__pycache__ dh_update_autotools_config -O--fail-missing -O--exclude=.la -O--exclude=lwresd -O--exclude=__pycache__ debian/rules override_dh_autoreconf make[1]: Entering directory '/build/bind-9.13.1+dfsg' if [ ! -f version.bak ]; then \ mv version version.bak; \ sed -e 's,^EXTENSIONS=,EXTENSIONS="$(dpkg-parsechangelog --file=../debian/changelog | sed -n '/^Version/s/[^-]*//p')-$(dpkg-vendor --query Vendor)",' < version.bak > version; \ fi dh_autoreconf configure.in:11: warning: prefer named diversions libtoolize: putting auxiliary files in '.'. libtoolize: copying file './ltmain.sh' libtoolize: putting macros in AC_CONFIG_MACRO_DIRS, 'libtool.m4'. libtoolize: copying file 'libtool.m4/libtool.m4' libtoolize: copying file 'libtool.m4/ltoptions.m4' libtoolize: copying file 'libtool.m4/ltsugar.m4' libtoolize: copying file 'libtool.m4/ltversion.m4' libtoolize: copying file 'libtool.m4/lt~obsolete.m4' libtoolize: Consider adding '-I libtool.m4' to ACLOCAL_AMFLAGS in Makefile.am. configure.in:11: warning: prefer named diversions autoheader: WARNING: Using auxiliary files such as `acconfig.h', `config.h.bot' autoheader: WARNING: and `config.h.top', to define templates for `config.h.in' autoheader: WARNING: is deprecated and discouraged. autoheader: autoheader: WARNING: Using the third argument of `AC_DEFINE' and autoheader: WARNING: `AC_DEFINE_UNQUOTED' allows one to define a template without autoheader: WARNING: `acconfig.h': autoheader: autoheader: WARNING: AC_DEFINE([NEED_FUNC_MAIN], 1, autoheader: [Define if a function `main' is needed.]) autoheader: autoheader: WARNING: More sophisticated templates can also be produced, see the autoheader: WARNING: documentation. configure.in:11: warning: prefer named diversions make[1]: Leaving directory '/build/bind-9.13.1+dfsg' debian/rules override_dh_auto_configure ... [snipped the successful first build] ... fakeroot debian/rules clean dh clean --with python3 --fail-missing --exclude=.la --exclude=lwresd --exclude=__pycache__ debian/rules override_dh_auto_clean make[1]: Entering directory '/build/bind-9.13.1+dfsg' if [ -f version.bak ]; then \ mv version.bak version; \ fi dh_auto_clean -B build make[1]: Leaving directory '/build/bind-9.13.1+dfsg' dh_autoreconf_clean -O--fail-missing -O--exclude=.la -O--exclude=lwresd -O--exclude=__pycache__ dh_clean -O--fail-missing -O--exclude=.la -O--exclude=lwresd -O--exclude=__pycache__ dpkg-source -b bind-9.13.1+dfsg dpkg-source: info: using source format '3.0 (quilt)' dpkg-source: info: building bind using existing ./bind_9.13.1+dfsg.orig.tar.xz dpkg-source: warning: ignoring deletion of file ltmain.sh, use --include-removal to override dpkg-source: warning: ignoring deletion of file configure, use --include-removal to override dpkg-source: warning: ignoring deletion of file config.h.in, use --include-removal to override dpkg-source: warning: ignoring deletion of file libtool.m4/libtool.m4, use --include-removal to override dpkg-source: info: building bind in bind_9.13.1+dfsg-1.debian.tar.xz dpkg-source: info: building bind in bind_9.13.1+dfsg-1.dsc debian/rules build dh build --with python3 --fail-missing --exclude=.la --exclude=lwresd --exclude=__pycache__ dh_update_autotools_config -O--fail-missing -O--exclude=.la -O--exclude=lwresd
Bug#1004271: marked as done (os.c:84: fatal error: RUNTIME_CHECK((size_t)s == (size_t)64) failed)
Your message dated Mon, 24 Jan 2022 15:48:52 +
with message-id
and subject line Bug#1004271: fixed in bind9 1:9.18.0~0+git28350c-1
has caused the Debian Bug report #1004271,
regarding os.c:84: fatal error: RUNTIME_CHECK((size_t)s == (size_t)64) failed
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.)
--
1004271: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1004271
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: bind9-dnsutils
Version: 1:9.17.22-1
Severity: serious
X-Debbugs-Cc: p...@packages.debian.org
Dear ISC BIND Maintainers,
Hello Ondřej,
src:pdns uses dig in its build to test pdns_server. On ppc64el this
apparently now crashes:
+ dig -p 5301 @127.0.0.1 smoke.bind.example.org
+ tee /tmp/tmp.RRMQ1Z4fs4
os.c:84: fatal error: RUNTIME_CHECK((size_t)s == (size_t)64) failed
Full pdns build log here:
https://buildd.debian.org/status/fetch.php?pkg=pdns=ppc64el=4.5.3-1=1642956562=0
It feels like, if this crashes on an arch, it would crash regardless of
the supplied parameters, etc.
The RUNTIME_CHECK was introduced in upstream commit
https://gitlab.isc.org/isc-projects/bind9/-/commit/4f78f9d72a5dc3f6a596251e662d00cb80cd5e6d
as I am sure you know :-)
Thanks,
Chris
--- End Message ---
--- Begin Message ---
Source: bind9
Source-Version: 1:9.18.0~0+git28350c-1
Done: Ondřej Surý
We believe that the bug you reported is fixed in the latest version of
bind9, 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 1004...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Ondřej Surý (supplier of updated bind9 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, 24 Jan 2022 16:00:49 +0100
Source: bind9
Architecture: source
Version: 1:9.18.0~0+git28350c-1
Distribution: unstable
Urgency: medium
Maintainer: Debian DNS Team
Changed-By: Ondřej Surý
Closes: 903586 942377 1000893 1004271
Changes:
bind9 (1:9.18.0~0+git28350c-1) unstable; urgency=medium
.
* New upstream version 9.18.0~0+git28350c
+ Pull the 9.18.0 pre-release git to have the L1 cache line
fix (Closes: #1004271)
* Fix the typo when backing up and restoring configure{,.ac}
(Closes: #903586)
* Remove some prehistoring conffile no longer in use
(Closes: #942377)
* Pick UTC date for release_date variable (Closes: #1000893)
Checksums-Sha1:
552d97534eba0e0b549ecc03ce534caa6de12d19 3110 bind9_9.18.0~0+git28350c-1.dsc
275496d2410b2598fa627ea97a8a277f9e112caf 4924520
bind9_9.18.0~0+git28350c.orig.tar.xz
780d5d87ad965443fdbe739902aa712ec62824ea 78680
bind9_9.18.0~0+git28350c-1.debian.tar.xz
6373f6db375df47df763f22a25533ad769512e1a 15640
bind9_9.18.0~0+git28350c-1_amd64.buildinfo
Checksums-Sha256:
4bb1bb127da90a855241a2048b902c53ee1ceef09bd965a7cd56af9008215e8a 3110
bind9_9.18.0~0+git28350c-1.dsc
8ced0b77ddbc15d203a1ed1df19a13fc7da3923eb4cb3ae7c90db2e0f31e6365 4924520
bind9_9.18.0~0+git28350c.orig.tar.xz
57cd596529e8ae879dfd04be3ea7f525b987532fa93f85be84d7b6a3d4cdbb19 78680
bind9_9.18.0~0+git28350c-1.debian.tar.xz
ee1fe0dc70d58a5b518abb0c6e5442d12089e33fc4b8e0f056a0755aa03b050a 15640
bind9_9.18.0~0+git28350c-1_amd64.buildinfo
Files:
7ada68e753fbc6877faab6df8f519e46 3110 net optional
bind9_9.18.0~0+git28350c-1.dsc
44563a49f911cdba37392971d69fbe37 4924520 net optional
bind9_9.18.0~0+git28350c.orig.tar.xz
b77755e64bb32d2e8ec9f85142e598d3 78680 net optional
bind9_9.18.0~0+git28350c-1.debian.tar.xz
4a814e22cb5015346e6907e756266d8f 15640 net optional
bind9_9.18.0~0+git28350c-1_amd64.buildinfo
-BEGIN PGP SIGNATURE-
iQKTBAEBCgB9FiEEw2Gx4wKVQ+vGJel9g3Kkd++uWcIFAmHux0lfFIAALgAo
aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldEMz
NjFCMUUzMDI5NTQzRUJDNjI1RTk3RDgzNzJBNDc3RUZBRTU5QzIACgkQg3Kkd++u
WcKKixAAjTQ+XYrYI2MXEo3lR5BSQyKB7ligPiVx9IpyEV9kMcv4F/jqxX8tYe2q
b6SuWzpR7X8ncPYn4KQikhXnvJab2iBFwNesV0dr3V7YaWUfpDBb+gDYkhC8mN3r
gsj110Qs9I9yqpe5WvUg6v6ZR3rfACOrdqfY9iDGtxEpxBauiojMc9HduYwI4aK/
z+BzejzwYzw9US54zFKMCxKUsnO91ZxwnLOs8HlegoTqUitF7pTfGmS0LKgC7k4g
AMfzsh8mmicIoKDO5KXrmuV0x5fJz+SFBDJeAq6UkNcgVvBPDIUddET5pkUKnYwh
Bug#1002679: marked as done (nheko depends on gstreamer1.0-qt5 which is not available on armel/armhf)
Your message dated Mon, 24 Jan 2022 10:21:00 -0500 with message-id <87czkh40tf@svladcjelli.uhoreg.ca> and subject line fixed by new gstreamer has caused the Debian Bug report #1002679, regarding nheko depends on gstreamer1.0-qt5 which is not available on armel/armhf 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.) -- 1002679: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1002679 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: nheko Version: 0.9.0-1 Severity: serious nheko depends on gstreamer1.0-qt5 which is not available on armel/armhf this is blocking it's migration to testing. Please evaluate how important the dependency is and either make it arch specific or if your package can't live without it alter your package so it does not build on armel/armhf. --- End Message --- --- Begin Message --- It looks like attempts to merge this with #998383 failed, so I'm just going to close this. This was fixed by a new version of GStreamer that includes gstreamer1.0-qt5 for armel/armhf. -- Hubert Chathi -- https://www.uhoreg.ca/ Jabber: hub...@uhoreg.ca -- Matrix: @uhoreg:matrix.org PGP/GnuPG key: 4096R/F24C F749 6C73 DDB8 DCB8 72DE B2DE 88D3 113A 1368--- End Message ---
Bug#984144: marked as done (fwbuilder: ftbfs with GCC-11)
Your message dated Mon, 24 Jan 2022 15:34:12 + with message-id and subject line Bug#984144: fixed in fwbuilder 5.3.7-5 has caused the Debian Bug report #984144, regarding fwbuilder: ftbfs with GCC-11 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 984144: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=984144 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:fwbuilder Version: 5.3.7-4.1 Severity: normal Tags: sid bookworm User: debian-...@lists.debian.org Usertags: ftbfs-gcc-11 [This bug is not targeted to the upcoming bullseye release] Please keep this issue open in the bug tracker for the package it was filed for. If a fix in another package is required, please file a bug for the other package (or clone), and add a block in this package. Please keep the issue open until the package can be built in a follow-up test rebuild. The package fails to build in a test rebuild on at least amd64 with gcc-11/g++-11, but succeeds to build with gcc-10/g++-10. The severity of this report will be raised before the bookworm release, so nothing has to be done for the bullseye release. The full build log can be found at: http://people.debian.org/~doko/logs/20210228/filtered/gcc11/fwbuilder_5.3.7-4.1_unstable_gcc11.log The last lines of the build log are at the end of this report. To build with GCC 11, either set CC=gcc-11 CXX=g++-11 explicitly, or install the gcc, g++, gfortran, ... packages from experimental. apt-get -t=experimental install g++ Common build failures are new warnings resulting in build failures with -Werror turned on, or new/dropped symbols in Debian symbols files. For other C/C++ related build failures see the porting guide at http://gcc.gnu.org/gcc-11/porting_to.html GCC 11 defaults to the GNU++17 standard. If your package installs header files in /usr/include, please don't work around C++17 issues by choosing a lower C++ standard for the package build, but fix these issues to build with the C++17 standard. [...] ../fwbuilder/XMLTools.h:148:7: error: ISO C++17 does not allow dynamic exception specifications 148 | ) throw(FWException); | ^ ../fwbuilder/XMLTools.h:158:7: error: ISO C++17 does not allow dynamic exception specifications 158 | ) throw(FWException); | ^ ../fwbuilder/XMLTools.h:197:7: error: ISO C++17 does not allow dynamic exception specifications 197 | ) throw(FWException); | ^ In file included from ../fwbuilder/Interface.h:36, from InetAddr.cpp:32: ../fwbuilder/FWOptions.h:43:45: error: ISO C++17 does not allow dynamic exception specifications 43 | virtual void fromXML(xmlNodePtr parent) throw(FWException); | ^ ../fwbuilder/FWOptions.h:44:49: error: ISO C++17 does not allow dynamic exception specifications 44 | virtual xmlNodePtr toXML(xmlNodePtr parent) throw(FWException); | ^ In file included from InetAddr.cpp:32: ../fwbuilder/Interface.h:91:49: error: ISO C++17 does not allow dynamic exception specifications 91 | virtual void fromXML(xmlNodePtr parent) throw(FWException); | ^ ../fwbuilder/Interface.h:92:53: error: ISO C++17 does not allow dynamic exception specifications 92 | virtual xmlNodePtr toXML(xmlNodePtr parent) throw(FWException); | ^ ../fwbuilder/Interface.h:192:69: error: ISO C++17 does not allow dynamic exception specifications 192 |bool preserve_id = true) throw(FWException); | ^ ../fwbuilder/Interface.h:194:62: error: ISO C++17 does not allow dynamic exception specifications 194 | bool preserve_id = true) throw(FWException); | ^ ../fwbuilder/Interface.h:196:69: error: ISO C++17 does not allow dynamic exception specifications 196 | virtual bool cmp(const FWObject *obj, bool recursive=false) throw(FWException); | ^ InetAddr.cpp:214:5: error: ISO C++17 does not allow dynamic exception specifications 214 | throw(FWException, FWNotSupportedException) | ^ InetAddr.cpp:221:5: error: ISO C++17 does not allow dynamic exception
Processed: Re: ima-evm-utils: FTBFS because of the signature verification unit tests
Processing control commands: > retitle -1 ima-evm-utils: FTBFS without extended attributes support Bug #999824 [ima-evm-utils] ima-evm-utils: FTBFS because of the signature verification unit tests Changed Bug title to 'ima-evm-utils: FTBFS without extended attributes support' from 'ima-evm-utils: FTBFS because of the signature verification unit tests'. -- 999824: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=999824 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#999824: ima-evm-utils: FTBFS because of the signature verification unit tests
Control: retitle -1 ima-evm-utils: FTBFS without extended attributes support On Mon, 24 Jan 2022 13:36:00 +0100 Bastian Germann wrote: Version 1.4 was imported but still fails to build from scratch on buildd because the unit tests for that new feature do not run without gnutls-bin and softhsm2 installed as build dependencies. The mentioned packages only enable tests that are currently skipped. The failure reason is that extended attributes are unsupported on the build file system. An easy solution would be disabling the test suite generally.
Bug#1002210: adapt: diff for NMU version 1.0.0-1.1
Control: tags 1002210 + patch Control: tags 1002210 + pending Dear maintainer, I've prepared an NMU for adapt (versioned as 1.0.0-1.1) and uploaded it to DELAYED/15. Please feel free to tell me if I should cancel it. cu Adrian diff -Nru adapt-1.0.0/debian/changelog adapt-1.0.0/debian/changelog --- adapt-1.0.0/debian/changelog 2021-11-21 20:15:54.0 +0200 +++ adapt-1.0.0/debian/changelog 2022-01-24 16:42:31.0 +0200 @@ -1,3 +1,10 @@ +adapt (1.0.0-1.1) unstable; urgency=medium + + * Non-maintainer upload. + * Add the missing build dependency on python3-six. (Closes: #1002210) + + -- Adrian Bunk Mon, 24 Jan 2022 16:42:31 +0200 + adapt (1.0.0-1) unstable; urgency=medium * New upstream release. diff -Nru adapt-1.0.0/debian/control adapt-1.0.0/debian/control --- adapt-1.0.0/debian/control 2021-07-08 18:39:16.0 +0300 +++ adapt-1.0.0/debian/control 2022-01-24 16:42:31.0 +0200 @@ -2,7 +2,7 @@ Section: python Priority: optional Maintainer: Wouter Verhelst -Build-Depends: debhelper-compat (= 13), dh-python, python3-setuptools, python3-all +Build-Depends: debhelper-compat (= 13), dh-python, python3-setuptools, python3-all, python3-six Standards-Version: 4.5.1 Homepage: https://github.com/MycroftAI/adapt Vcs-Browser: https://salsa.debian.org/mycroftai-team/adapt
Processed: adapt: diff for NMU version 1.0.0-1.1
Processing control commands:
> tags 1002210 + patch
Bug #1002210 [src:adapt] adapt: FTBFS: dh_auto_test: error: pybuild --test -i
python{version} -p "3.10 3.9" returned exit code 13
Added tag(s) patch.
> tags 1002210 + pending
Bug #1002210 [src:adapt] adapt: FTBFS: dh_auto_test: error: pybuild --test -i
python{version} -p "3.10 3.9" returned exit code 13
Added tag(s) pending.
--
1002210: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1002210
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#916132: marked as done (hepmc FTBFS: FAIL testWeights)
Your message dated Mon, 24 Jan 2022 14:40:01 + with message-id and subject line Bug#996845: Removed package(s) from unstable has caused the Debian Bug report #916132, regarding hepmc FTBFS: FAIL testWeights 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.) -- 916132: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=916132 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: hepmc Version: 2.06.09-3 Severity: serious Tags: ftbfs Some recent change in unstable makes hepmc FTBFS: https://tests.reproducible-builds.org/debian/history/hepmc.html https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/hepmc.html ... make check-TESTS make[3]: Entering directory '/build/1st/hepmc-2.06.09/test' make[4]: Entering directory '/build/1st/hepmc-2.06.09/test' PASS: testSimpleVector PASS: testUnits PASS: testHepMC.sh PASS: testHepMCIteration.sh PASS: testMass.sh PASS: testFlow.sh PASS: testStreamIO.sh PASS: testPrintBug.sh PASS: testMultipleCopies PASS: testPolarization.sh ../test-driver: line 107: 52027 Segmentation fault "$@" > $log_file 2>&1 FAIL: testWeights HepMC 2.06.09: test/test-suite.log # TOTAL: 11 # PASS: 10 # SKIP: 0 # XFAIL: 0 # FAIL: 1 # XPASS: 0 # ERROR: 0 .. contents:: :depth: 2 FAIL: testWeights = FAIL testWeights (exit status: 139) Testsuite summary for HepMC 2.06.09 # TOTAL: 11 # PASS: 10 # SKIP: 0 # XFAIL: 0 # FAIL: 1 # XPASS: 0 # ERROR: 0 See test/test-suite.log Please report to https://savannah.cern.ch/projects/hepmc/ make[4]: *** [Makefile:881: test-suite.log] Error 1 Backtrace: Core was generated by `/tmp/hepmc-2.06.09/test/.libs/testWeights'. Program terminated with signal SIGSEGV, Segmentation fault. #0 0x7fc39a374474 in std::_Rb_tree_increment(std::_Rb_tree_node_base*) () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6 (gdb) bt #0 0x7fc39a374474 in std::_Rb_tree_increment(std::_Rb_tree_node_base*) () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6 #1 0x7fc39a4ddc08 in std::_Rb_tree_iterator, std::allocator > const, unsigned long> >::operator++ (this=) at /usr/include/c++/8/bits/stl_tree.h:285 #2 HepMC::WeightContainer::pop_back (this=this@entry=0x7ffdd7410790) at WeightContainer.cc:56 #3 0x55e8672df5ab in main () at testWeights.cc:36 --- End Message --- --- Begin Message --- Version: 2.06.09-3+rm Dear submitter, as the package hepmc has just been removed from the Debian archive unstable we hereby close the associated bug reports. We are sorry that we couldn't deal with your issue properly. For details on the removal, please see https://bugs.debian.org/996845 The version of this package that was in Debian prior to this removal can still be found using http://snapshot.debian.org/. Please note that the changes have been done on the master archive and will not propagate to any mirrors until the next dinstall run at the earliest. This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org. Debian distribution maintenance software pp. Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---
Bug#966790: marked as done (rivet: Unversioned Python removal in sid/bullseye)
Your message dated Mon, 24 Jan 2022 14:38:50 + with message-id and subject line Bug#996843: Removed package(s) from unstable has caused the Debian Bug report #966790, regarding rivet: 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.) -- 966790: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=966790 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:rivet Version: 1.8.3-3 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.8.3-3+rm Dear submitter, as the package rivet has just been removed from the Debian archive unstable we hereby close the associated bug reports. We are sorry that we couldn't deal with your issue properly. For details on the removal, please see https://bugs.debian.org/996843 The version of this package that was in Debian prior to this removal can still be found using http://snapshot.debian.org/. Please note that the changes have been done on the master archive and will not propagate to any mirrors until the next dinstall run at the earliest. This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org. Debian distribution maintenance software pp. Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---
Bug#954648: marked as done (FTBFS with Boost 1.71)
Your message dated Mon, 24 Jan 2022 14:38:50 +
with message-id
and subject line Bug#996843: Removed package(s) from unstable
has caused the Debian Bug report #954648,
regarding FTBFS with Boost 1.71
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.)
--
954648: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=954648
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: rivet
Version: 1.8.3-3
Severity: wishlist
User: team+bo...@tracker.debian.org
Usertags: boost1.71
Forwarded: https://github.com/boostorg/assign/issues/33
Dear Maintainer,
your package fails to build with boost1.71. You can find a build log
attached. If you want to attempt the build yourself, an updated version
of boost-defaults which brings in boost1.71 dependencies can be found
adding this line to your sources.list file:
deb https://people.debian.org/~gio/reprepro gio main
This bug has severity whishlist for the moment, but it will raised to RC
as soon as version 1.71 of Boost is promoted to default.
More specifically, your package fails building because it seems that a
certain usage of operator+= seems to be not supported any more by
Boost.Assign. I asked upstream about whether it should be considered
legitimate or not:
https://github.com/boostorg/assign/issues/33
From the build log:
> In file included from /usr/include/boost/assign/std/vector.hpp:18,
> from /usr/include/boost/assign/std.hpp:18,
> from /usr/include/boost/assign.hpp:19,
> from ../../include/Rivet/RivetBoost.hh:6,
> from ../../include/Rivet/Math/MathUtils.hh:6,
> from ../../include/Rivet/Rivet.hh:42,
> from RivetPaths.cc:1:
> /usr/include/boost/assign/list_inserter.hpp: In instantiation of 'void
> boost::assign_detail::call_push_back::operator()(T&&) [with T =
> std::vector >; C =
> std::vector >]':
> /usr/include/boost/assign/list_inserter.hpp:414:13: required from 'void
> boost::assign::list_inserter Argument>::insert(boost::assign::list_inserter Argument>::single_arg_type, T&&) [with T =
> std::vector >; Function =
> boost::assign_detail::call_push_back
> > >; Argument = std::__cxx11::basic_string]'
> /usr/include/boost/assign/list_inserter.hpp:406:13: required from
> 'boost::assign::list_inserter&
> boost::assign::list_inserter::operator()(Ts&& ...) [with
> Ts = {std::vector,
> std::allocator >, std::allocator std::char_traits, std::allocator > > >}; Function =
> boost::assign_detail::call_push_back
> > >; Argument = std::__cxx11::basic_string]'
> /usr/include/boost/assign/std/vector.hpp:42:30: required from
> 'boost::assign::list_inserter _Alloc> >, V> boost::assign::operator+=(std::vector<_Tp, _Alloc>&, V2&&)
> [with V = std::__cxx11::basic_string; A =
> std::allocator >; V2 =
> std::vector >]'
> RivetPaths.cc:57:28: required from here
> /usr/include/boost/assign/list_inserter.hpp:91:13: error: no matching
> function for call to 'std::vector
> >::push_back(std::vector >)'
>91 | c_.push_back(boost::forward(r));
> | ^~
> In file included from /usr/include/c++/9/vector:67,
> from ../../include/Rivet/RivetSTL.hh:11,
> from ../../include/Rivet/Rivet.hh:8,
> from RivetPaths.cc:1:
> /usr/include/c++/9/bits/stl_vector.h:1184:7: note: candidate: 'void
> std::vector<_Tp, _Alloc>::push_back(const value_type&) [with _Tp =
> std::__cxx11::basic_string; _Alloc =
> std::allocator >; std::vector<_Tp,
> _Alloc>::value_type = std::__cxx11::basic_string]'
> 1184 | push_back(const value_type& __x)
> | ^
> /usr/include/c++/9/bits/stl_vector.h:1184:35: note: no known conversion for
> argument 1 from 'std::vector >' to 'const
> value_type&' {aka 'const std::__cxx11::basic_string&'}
> 1184 | push_back(const value_type& __x)
> | ~~^~~
> /usr/include/c++/9/bits/stl_vector.h:1200:7: note: candidate: 'void
> std::vector<_Tp, _Alloc>::push_back(std::vector<_Tp, _Alloc>::value_type&&)
> [with _Tp = std::__cxx11::basic_string; _Alloc =
> std::allocator >; std::vector<_Tp,
> _Alloc>::value_type = std::__cxx11::basic_string]'
> 1200 | push_back(value_type&& __x)
> | ^
> /usr/include/c++/9/bits/stl_vector.h:1200:30: note: no known conversion for
> argument 1 from 'std::vector >' to
> 'std::vector >::value_type&&' {aka
> 'std::__cxx11::basic_string&&'}
> 1200 | push_back(value_type&& __x)
> | ~^~~
Bug#998924: marked as done (libview: missing required debian/rules targets build-arch and/or build-indep)
Your message dated Mon, 24 Jan 2022 14:37:57 + with message-id and subject line Bug#674884: Removed package(s) from unstable has caused the Debian Bug report #998924, regarding libview: missing required debian/rules targets build-arch and/or build-indep 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.) -- 998924: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=998924 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: libview Version: 0.6.6-2.1 Severity: important Justification: Debian Policy section 4.9 Tags: bookworm sid User: debian...@lists.debian.org Usertags: missing-build-arch-indep Dear maintainer, Your package does not include build-arch and/or build-indep targets in debian/rules. This is required by Debian Policy section 4.9, since 2012. https://www.debian.org/doc/debian-policy/ch-source.html#main-building-script-debian-rules Please note that this is also a sign that the packaging of this software could benefit from a refresh. For example, packages using 'dh' cannot be affected by this issue. This mass bug filing was discussed on debian-devel@ in https://lists.debian.org/debian-devel/2021/11/msg00052.html . The severity of this bug will be changed to 'serious' after a month. Best, Lucas --- End Message --- --- Begin Message --- Version: 0.6.6-2.1+rm Dear submitter, as the package libview has just been removed from the Debian archive unstable we hereby close the associated bug reports. We are sorry that we couldn't deal with your issue properly. For details on the removal, please see https://bugs.debian.org/674884 The version of this package that was in Debian prior to this removal can still be found using http://snapshot.debian.org/. Please note that the changes have been done on the master archive and will not propagate to any mirrors until the next dinstall run at the earliest. This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org. Debian distribution maintenance software pp. Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---
Bug#996758: marked as done (RM: openlayer: RoQA, unmaintained, dead upstream, low popcon)
Your message dated Mon, 24 Jan 2022 14:38:15 + with message-id and subject line Bug#996758: Removed package(s) from unstable has caused the Debian Bug report #996758, regarding RM: openlayer: RoQA, unmaintained, dead upstream, low popcon 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.) -- 996758: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=996758 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: openlayer Severity: serious The homepage in d/control just leads to berlios.de, dead since many years. The package looks unmaintained, and upstream dead. Popcon is at 4. There are no reverse dependencies. That makes me wonder if openlayer should be just removed. If you disagree, just close this bug, but please show the package some love. If you agree, reassign the bug to ftp.debian.org If there is no answer, I will reassing the bug in exactly 3 months to ftp.debian.org to make the RM happen. Cheers, -- tobi --- End Message --- --- Begin Message --- We believe that the bug you reported is now fixed; the following package(s) have been removed from unstable: libopenlayer-dev | 2.1-2.1+b2 | amd64, arm64, armel, armhf, i386, mips64el, mipsel, ppc64el, s390x libopenlayer2v5 | 2.1-2.1+b2 | amd64, arm64, armel, armhf, i386, mips64el, mipsel, ppc64el, s390x openlayer |2.1-2.1 | source --- Reason --- RoQA, unmaintained, dead upstream, low popcon -- Note that the package(s) have simply been removed from the tag database and may (or may not) still be in the pool; this is not a bug. The package(s) will be physically removed automatically when no suite references them (and in the case of source, when no binary references it). Please also remember that the changes have been done on the master archive and will not propagate to any mirrors until the next dinstall run at the earliest. Packages are usually not removed from testing by hand. Testing tracks unstable and will automatically remove packages which were removed from unstable when removing them from testing causes no dependency problems. The release team can force a removal from testing if it is really needed, please contact them if this should be the case. We try to close bugs which have been reported against this package automatically. But please check all old bugs, if they were closed correctly or should have been re-assigned to another package. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 996...@bugs.debian.org. The full log for this bug can be viewed at https://bugs.debian.org/996758 This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org. Debian distribution maintenance software pp. Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---
Processed: severity of 996843 is normal, severity of 996845 is normal, severity of 996846 is normal ...
Processing commands for cont...@bugs.debian.org: > severity 996843 normal Bug #996843 [ftp.debian.org] RM: rivet -- RoQA, unmaintained, python2, lowpopcon, RC-buggy Severity set to 'normal' from 'serious' > severity 996845 normal Bug #996845 [ftp.debian.org] RM: hepmc -- RoQA, unmaintained, RC-buggy, low-popcon Severity set to 'normal' from 'serious' > severity 996846 normal Bug #996846 [ftp.debian.org] RM: pythia8 -- RoQA, unmaintained, low popcon Severity set to 'normal' from 'serious' > severity 996849 normal Bug #996849 [ftp.debian.org] RM: dlz-ldap-enum -- RoQA, unmaintained, dead-upstream, low popcon Severity set to 'normal' from 'serious' > thanks Stopping processing here. Please contact me if you need assistance. -- 996843: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=996843 996845: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=996845 996846: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=996846 996849: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=996849 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#996171: marked as done (glibmm2.4: FTBFS on buildds / reproducible builds without network access)
Your message dated Mon, 24 Jan 2022 12:48:44 + with message-id and subject line Bug#996171: fixed in glibmm2.4 2.66.2-2 has caused the Debian Bug report #996171, regarding glibmm2.4: FTBFS on buildds / reproducible builds without network access 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.) -- 996171: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=996171 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: glibmm2.4 Version: 2.66.2-1 Severity: serious Tags: upstream ftbfs Justification: Debian Policy 4.9 According to Debian Policy 4.9: | For packages in the main archive, required targets must not attempt | network access, except, via the loopback interface, to services on the | build host that have been started by the build. However the giomm_tls_client test in glibmm2.4 tries to connect to https://www.gnome.org and fails to build if that host is not accessible: | Summary of Failures: | | 34/34 giomm_tls_client_testTIMEOUT30.03s killed by signal 15 SIGTERM | | | Ok: 33 | Expected Fail: 0 | Fail: 0 | Unexpected Pass:0 | Skipped:0 | Timeout:1 | dh_auto_test: error: cd obj-riscv64-linux-gnu && LC_ALL=C.UTF-8 MESON_TESTTHREADS=4 meson test returned exit code 1 | make: *** [debian/rules:7: build-arch] Error 25 | dpkg-buildpackage: error: debian/rules build-arch subprocess returned exit status 2 The full build log can be found there: https://buildd.debian.org/status/fetch.php?pkg=glibmm2.4=riscv64=2.66.2-1=1633924088=0 When instead the build happens with only the localhost interface, it fails in a slightly different way: | Summary of Failures: | | 14/34 giomm_tls_client_testFAIL0.15s killed by signal 6 SIGABRT | | | Ok: 33 | Expected Fail: 0 | Fail: 1 | Unexpected Pass:0 | Skipped:0 | Timeout:0 | dh_auto_test: error: cd obj-x86_64-linux-gnu && LC_ALL=C.UTF-8 MESON_TESTTHREADS=15 meson test returned exit code 1 | make: *** [debian/rules:7: binary] Error 25 | dpkg-buildpackage: error: fakeroot debian/rules binary subprocess returned exit status 2 | | The full build log can be found there: | https://tests.reproducible-builds.org/debian/rbuild/unstable/amd64/glibmm2.4_2.66.1-1.rbuild.log.gz --- End Message --- --- Begin Message --- Source: glibmm2.4 Source-Version: 2.66.2-2 Done: Jeremy Bicha We believe that the bug you reported is fixed in the latest version of glibmm2.4, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 996...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Jeremy Bicha (supplier of updated glibmm2.4 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, 24 Jan 2022 07:26:10 -0500 Source: glibmm2.4 Built-For-Profiles: noudeb Architecture: source Version: 2.66.2-2 Distribution: unstable Urgency: medium Maintainer: Debian GNOME Maintainers Changed-By: Jeremy Bicha Closes: 996171 Changes: glibmm2.4 (2.66.2-2) unstable; urgency=medium . * Update 01-disable-tls-test.patch for meson (Closes: #996171) Checksums-Sha1: b86183f7fc8cb5b47445e60dea5f33eac223c1db 2255 glibmm2.4_2.66.2-2.dsc 0f63e4125d497e5ed2b30f418e0254c47fffa199 9780 glibmm2.4_2.66.2-2.debian.tar.xz c592d68a3d9215e5ce13316722ab064983c060b1 10684 glibmm2.4_2.66.2-2_source.buildinfo Checksums-Sha256: daf163f024dae59f0dbf51a0871732ffe233f37488dd243724813a80962283a5 2255 glibmm2.4_2.66.2-2.dsc 1243c68f831af8a1428e6560e61f02431d8ab2f45f244a4fe1952f2ea4f9d797 9780 glibmm2.4_2.66.2-2.debian.tar.xz 609ec6fc8ff74f3ea468a66fb937e055a6d703acc018b2a70330aefbe64cd834 10684 glibmm2.4_2.66.2-2_source.buildinfo Files: 9e646f4ad46dcf82bb3619cbc8bfd114 2255 libs optional glibmm2.4_2.66.2-2.dsc 385b7f92115f6c59d79c4a4d5892e43f 9780 libs optional glibmm2.4_2.66.2-2.debian.tar.xz b77868f26010218abdc1986b14ff305b 10684 libs optional glibmm2.4_2.66.2-2_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEETQvhLw5HdtiqzpaW5mx3Wuv+bH0FAmHumxgACgkQ5mx3Wuv+
Processed: reassign 996849 to ftp.debian.org
Processing commands for cont...@bugs.debian.org: > reassign 996849 ftp.debian.org Bug #996849 [dlz-ldap-enum] RM: dlz-ldap-enum -- RoQA, unmaintained, dead-upstream, low popcon Bug reassigned from package 'dlz-ldap-enum' to 'ftp.debian.org'. Ignoring request to alter found versions of bug #996849 to the same values previously set Ignoring request to alter fixed versions of bug #996849 to the same values previously set > thanks Stopping processing here. Please contact me if you need assistance. -- 996849: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=996849 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: reassign 996846 to ftp.debian.org
Processing commands for cont...@bugs.debian.org: > reassign 996846 ftp.debian.org Bug #996846 [src:pythia8] RM: pythia8 -- RoQA, unmaintained, low popcon Bug reassigned from package 'src:pythia8' to 'ftp.debian.org'. Ignoring request to alter found versions of bug #996846 to the same values previously set Ignoring request to alter fixed versions of bug #996846 to the same values previously set > thanks Stopping processing here. Please contact me if you need assistance. -- 996846: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=996846 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: reassign 996843 to ftp.debian.org
Processing commands for cont...@bugs.debian.org: > reassign 996843 ftp.debian.org Bug #996843 [rivet] RM: rivet -- RoQA, unmaintained, python2, lowpopcon, RC-buggy Bug reassigned from package 'rivet' to 'ftp.debian.org'. Ignoring request to alter found versions of bug #996843 to the same values previously set Ignoring request to alter fixed versions of bug #996843 to the same values previously set > thanks Stopping processing here. Please contact me if you need assistance. -- 996843: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=996843 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: reassign 996758 to ftp.debian.org
Processing commands for cont...@bugs.debian.org: > reassign 996758 ftp.debian.org Bug #996758 [src:openlayer] RM: openlayer: RoQA, unmaintained, dead upstream, low popcon Bug reassigned from package 'src:openlayer' to 'ftp.debian.org'. Ignoring request to alter found versions of bug #996758 to the same values previously set Ignoring request to alter fixed versions of bug #996758 to the same values previously set > thanks Stopping processing here. Please contact me if you need assistance. -- 996758: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=996758 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: reassign 996845 to ftp.debian.org
Processing commands for cont...@bugs.debian.org: > reassign 996845 ftp.debian.org Bug #996845 [src:hepmc] RM: hepmc -- RoQA, unmaintained, RC-buggy, low-popcon Bug reassigned from package 'src:hepmc' to 'ftp.debian.org'. Ignoring request to alter found versions of bug #996845 to the same values previously set Ignoring request to alter fixed versions of bug #996845 to the same values previously set > thanks Stopping processing here. Please contact me if you need assistance. -- 996845: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=996845 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Re: ima-evm-utils: missing evm portable signature verification in tooling
Processing control commands: > retitle -1 ima-evm-utils: FTBFS because of the signature verification unit > tests Bug #999824 [ima-evm-utils] ima-evm-utils: missing evm portable signature verification in tooling Changed Bug title to 'ima-evm-utils: FTBFS because of the signature verification unit tests' from 'ima-evm-utils: missing evm portable signature verification in tooling'. > severity -1 serious Bug #999824 [ima-evm-utils] ima-evm-utils: FTBFS because of the signature verification unit tests Severity set to 'serious' from 'normal' -- 999824: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=999824 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#996171: marked as pending in glibmm2.4
Control: tag -1 pending Hello, Bug #996171 in glibmm2.4 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/glibmm/-/commit/89cc951b90820cc1b59cc93fd58794827cad9dbb Update 01-disable-tls-test.patch for meson Closes: #996171 (this message was generated automatically) -- Greetings https://bugs.debian.org/996171
Processed: Bug#996171 marked as pending in glibmm2.4
Processing control commands: > tag -1 pending Bug #996171 [src:glibmm2.4] glibmm2.4: FTBFS on buildds / reproducible builds without network access Added tag(s) pending. -- 996171: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=996171 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#994451: marked as pending in golang-github-opencontainers-specs
Control: tag -1 pending Hello, Bug #994451 in golang-github-opencontainers-specs reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/go-team/packages/golang-github-opencontainers-specs/-/commit/b10b754211b3d231f701295074f75e5efdbc6b60 seccomp: allow to override default errno return code Backport upstream patch f7ef278d1bbaa6f97b8ef511fad478a31e953290 LP: #1943049 Closes: #994451 (this message was generated automatically) -- Greetings https://bugs.debian.org/994451
Processed: Bug#994451 marked as pending in golang-github-opencontainers-specs
Processing control commands: > tag -1 pending Bug #994451 [golang-github-containers-common] golang-github-containers-common: secomp.json does not include newer syscall used by stable kernel/glibc on arm Added tag(s) pending. -- 994451: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=994451 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1002657: marked as done (FTBFS with OCaml 4.13.1)
Your message dated Mon, 24 Jan 2022 11:51:58 + with message-id and subject line Bug#1002657: fixed in sks 1.1.6+git20210302.c3ba6d5a-4 has caused the Debian Bug report #1002657, regarding FTBFS with OCaml 4.13.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.) -- 1002657: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1002657 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: sks Version: 1.1.6+git20210302.c3ba6d5a-3 Severity: important Tags: ftbfs Dear Maintainer, Your package FTBFS with OCaml 4.13.1 with the following error: > File "mList.ml", line 203, characters 14-23: > 203 | let slist = List.sort compare list in > ^ > Error (warning 6 [labels-omitted]): label cmp was omitted in the application > of this function. > File "mList.ml", line 211, characters 14-23: > 211 | let slist = List.sort compare list in > ^ > Error (warning 6 [labels-omitted]): label cmp was omitted in the application > of this function. Packages rebuilt with OCaml 4.13.1 are available at: https://ocaml.debian.net/transitions/ocaml-4.13.1/ Cheers, -- Stéphane -- System Information: Debian Release: bookworm/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.15.0-2-amd64 (SMP w/4 CPU threads) Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled --- End Message --- --- Begin Message --- Source: sks Source-Version: 1.1.6+git20210302.c3ba6d5a-4 Done: Christoph Martin We believe that the bug you reported is fixed in the latest version of sks, 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 1002...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Christoph Martin (supplier of updated sks 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, 24 Jan 2022 12:33:30 +0100 Source: sks Architecture: source Version: 1.1.6+git20210302.c3ba6d5a-4 Distribution: unstable Urgency: medium Maintainer: Christoph Martin Changed-By: Christoph Martin Closes: 1002657 Changes: sks (1.1.6+git20210302.c3ba6d5a-4) unstable; urgency=medium . * include tail-recursive-key-parsing.patch from https://github.com/SKS-Keyserver/sks-keyserver/pull/79 * include Do-not-error-on-warning-6-labels-omitted.patch (closes: 1002657) Checksums-Sha1: 26bd54a9c582b01619015d47aa5f4e22ef4ce7de sks_1.1.6+git20210302.c3ba6d5a-4.dsc ca2be5035debd37d8f8d65a83776c2a1ad74b339 135109544 sks_1.1.6+git20210302.c3ba6d5a.orig.tar.gz 4019c216fe79bceb8ba249bc5c102118ccf61d89 22880 sks_1.1.6+git20210302.c3ba6d5a-4.debian.tar.xz 40a4e66c2e8bb443693543d31ecec31ee61269db 8034 sks_1.1.6+git20210302.c3ba6d5a-4_amd64.buildinfo Checksums-Sha256: 7054b9790e523ff6379ffac63ef0400ffb22244cc67c82e651c3f2143996732c sks_1.1.6+git20210302.c3ba6d5a-4.dsc 9b86e1dfe4876cfaaf8b080ca8e4b98b85145999659016e3906c6aa68d2c59fb 135109544 sks_1.1.6+git20210302.c3ba6d5a.orig.tar.gz 447701a6f2c84ae126d5ba4984c5d8580f56d0d674a4b053180947aa770f36ce 22880 sks_1.1.6+git20210302.c3ba6d5a-4.debian.tar.xz d75ca3fb8dc8d86e773ca71d87885ba04d540ac49eb0589558d7f3fc15d3f5a4 8034 sks_1.1.6+git20210302.c3ba6d5a-4_amd64.buildinfo Files: 52ed9189b6d45d9cb8309162fcbf65e0 net optional sks_1.1.6+git20210302.c3ba6d5a-4.dsc eb4831ae968f4f1afeefc3bceadeeba5 135109544 net optional sks_1.1.6+git20210302.c3ba6d5a.orig.tar.gz 589e3f246b0b9aff5e2f6037504418bf 22880 net optional sks_1.1.6+git20210302.c3ba6d5a-4.debian.tar.xz 10f5ac8cfad79063d4ed366ce1f76e5e 8034 net optional sks_1.1.6+git20210302.c3ba6d5a-4_amd64.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEienqSdlSvBRoCebg9oBraugTkrAFAmHukDcACgkQ9oBraugT krBExw/+OCJGj+qGA2+HVXjQZhxBZIN/jDcS2WIaKNdIbqCt4RyOH5OuLL8+mJAF Kp/JyCI5S0D/RBvG6JBOb9/bXb+IZje3pr/b1g3CNFPDXuUY1ujjUvRgFxCv5sta ImRSO+H4Kefe3CIBPAzI/y3XsDSK8UpFkyUcZeCNkubnCVQK46xT4VaUC3iDQFcD
Bug#1002608: marked as done (Build-Conflicts with ocaml)
Your message dated Mon, 24 Jan 2022 11:49:17 +
with message-id
and subject line Bug#1002608: fixed in llvm-toolchain-12 1:12.0.1-18
has caused the Debian Bug report #1002608,
regarding Build-Conflicts with ocaml
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.)
--
1002608: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1002608
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: llvm-toolchain-11
Version: 1:11.1.0-4
Severity: important
X-Debbugs-Cc: debian-ocaml-ma...@lists.debian.org
Dear Maintainer,
I don't understand with llvm-toolchain-11 build-conflicts with ocaml.
With ocaml 4.13.1 (in experimental), the *-nox binary packages are
becoming transitional, and their contents moved to
ocaml{,-base}. Hence, llvm-toolchain-11 cannot be built in the
universe rebuit with the new ocaml.
The build-conflicts should be dropped.
Cheers,
--
Stéphane
-- System Information:
Debian Release: bookworm/sid
APT prefers testing
APT policy: (990, 'testing'), (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 5.15.0-2-amd64 (SMP w/4 CPU threads)
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
--- End Message ---
--- Begin Message ---
Source: llvm-toolchain-12
Source-Version: 1:12.0.1-18
Done: Sylvestre Ledru
We believe that the bug you reported is fixed in the latest version of
llvm-toolchain-12, 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 1002...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Sylvestre Ledru (supplier of updated llvm-toolchain-12
package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Thu, 16 Dec 2021 17:49:22 +0100
Source: llvm-toolchain-12
Architecture: source
Version: 1:12.0.1-18
Distribution: unstable
Urgency: medium
Maintainer: LLVM Packaging Team
Changed-By: Sylvestre Ledru
Closes: 1002608
Changes:
llvm-toolchain-12 (1:12.0.1-18) unstable; urgency=medium
.
* Unbreak llvm-toolchain-12 on buster.
-fuse-ld=gold wasn't passed to compiler-rt. it was using bfd.
And binutils shipping in buster has a bug preventing this to work:
https://github.com/llvm/llvm-project/issues/42339
* Rename ocaml-nox => ocaml-base (Closes: #1002608)
* Remove Build-Conflicts: ocaml
Checksums-Sha1:
a4cbdd9958f459388a04052f89c662f4efff0401 6660 llvm-toolchain-12_12.0.1-18.dsc
bdef3eeeb2c8b3ddbc5ad49543c3d834adc5379f 144124
llvm-toolchain-12_12.0.1-18.debian.tar.xz
a9d983ce64e11a2a97e68d46103d133354c43394 28998
llvm-toolchain-12_12.0.1-18_amd64.buildinfo
Checksums-Sha256:
876289c468f618e2ac2f04664ba6bdd2e2c8ff2023172b0b9c9942db7f2bf7c1 6660
llvm-toolchain-12_12.0.1-18.dsc
ba947596d5ec4a1ad7dd8d27ea843486d1a768ec7762ae128e7b4c43750a6b63 144124
llvm-toolchain-12_12.0.1-18.debian.tar.xz
1ea16ef8e48083a4a72c7987dba9574772a15cf59fdd39441b88b03860dbc52b 28998
llvm-toolchain-12_12.0.1-18_amd64.buildinfo
Files:
86ced409845cd2a9a582cc6802629c03 6660 devel optional
llvm-toolchain-12_12.0.1-18.dsc
471b68afd012ce8b93268c31b1050cc3 144124 devel optional
llvm-toolchain-12_12.0.1-18.debian.tar.xz
99e5e97a410aafb41245cd1a8fd2b1d8 28998 devel optional
llvm-toolchain-12_12.0.1-18_amd64.buildinfo
-BEGIN PGP SIGNATURE-
iQIzBAEBCAAdFiEEtg21mU05vsTRqVzPfmUo2nUvG+EFAmHujYgACgkQfmUo2nUv
G+H7ew/9GpdFKBJEIJRfmWJUiPIFdwF0XiZafjzRQRg1OZG5NRtVSscGxJbJ4jRu
uDPMfh1d57FoPIxrEaEaN7dIeTnaYTI1UFqwHHR58uB2gWs4Y3dtuZJE7OOUb83g
vuZlccGkqGe8hYSWFPra5vWTVPa17W3PB3pg8bz2m5zbn4WXcL2Z7YXtApJR2a9Y
0QCzLkc2Ml2XDP8Pu2H4NPcUrtOTalgURau9InUpsnaehycQoEO9s2dsdNt7dkdH
75FW8G94tH7JGfIaDsNh/0D/X/bSgXgQIXv+xFqH3UQq4N5WfftiYf1Gp3BpM2R0
0KVYGWrJfuq5jOd0yJ68BcIYOlyJtTVUhxp6kk4GvqCbBsjUcHmdo2uCfPTXkCPv
XoWdAMuuiR4p5HJ7mX+IC0/NvY2gudIG7bARCJDFd0TXCxtxrfrQI0oslATXYmOe
XwBidBHr5P0qbu0VIcw6qgcs82x5ZvDDbSVhPDeUMGtgR+bIaRXaKXT+TcRqsW4l
2IoOKJQV11Ft3wEd692CovG3Wr9CxFGtg2DPidb5WrvLdC4l2ozVNMFaXtNHZH7Z
TG8bvmXRmVAW+kTdZii5nZy5gRozJq/GjM9A44L9p6DQkzCdF6oOjPj0TaD3aznf
dW1iyNgvIDZC0J/K5ma+Bq0tCb3Vq1KXRXl/2QH3KE9zVJZIc9U=
Processed: Bug#997415: build depends on tex-gyre
Processing control commands: > tags -1 + patch Bug #997415 [src:gprbuild] gprbuild: FTBFS: '! LaTeX Error: File `tgtermes.sty' not found.' Added tag(s) patch. -- 997415: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997415 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#997415: build depends on tex-gyre
Control: tags -1 + patch Hello, This issue should be fixed by build-depending on tex-gyre which provides the missing tgtermes.sty. I have successfully built gprbuild-2021.0.0.0778b109 in clean chroot with tex-gyre additionally installed. Andrius
Bug#1004285: davical: problems after upgrade to php 8, calendar clients reports "500"
Some additional information. On 24/01/2022 11:58, Benno Overeinder wrote: * What exactly did you do (or not do) that was effective (or ineffective)? I have looked at the apache2 log files and checked the /etc/php and /etc/davical directories if there were any references to php7 instead of php/php8. The apache2 log file reported [Mon Jan 24 11:29:29.678647 2022] [php:notice] [pid 684] [client /IPv6 address/] davical: LOG: response:-->DAViCal Fatal Error The macOS Calendar application warned with the error message: “500” to operation CalDAVAccountRefreshQueueableOperation
Bug#1002607: marked as done (Build-Conflicts with ocaml)
Your message dated Mon, 24 Jan 2022 11:04:34 +
with message-id
and subject line Bug#1002607: fixed in llvm-toolchain-11 1:11.1.0-5
has caused the Debian Bug report #1002607,
regarding Build-Conflicts with ocaml
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.)
--
1002607: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1002607
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: llvm-toolchain-11
Version: 1:11.1.0-4
Severity: important
X-Debbugs-Cc: debian-ocaml-ma...@lists.debian.org
Dear Maintainer,
I don't understand with llvm-toolchain-11 build-conflicts with ocaml.
With ocaml 4.13.1 (in experimental), the *-nox binary packages are
becoming transitional, and their contents moved to
ocaml{,-base}. Hence, llvm-toolchain-11 cannot be built in the
universe rebuit with the new ocaml.
The build-conflicts should be dropped.
Cheers,
--
Stéphane
-- System Information:
Debian Release: bookworm/sid
APT prefers testing
APT policy: (990, 'testing'), (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 5.15.0-2-amd64 (SMP w/4 CPU threads)
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
--- End Message ---
--- Begin Message ---
Source: llvm-toolchain-11
Source-Version: 1:11.1.0-5
Done: Sylvestre Ledru
We believe that the bug you reported is fixed in the latest version of
llvm-toolchain-11, 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 1002...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Sylvestre Ledru (supplier of updated llvm-toolchain-11
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, 11 Oct 2021 20:36:19 +0200
Source: llvm-toolchain-11
Architecture: source
Version: 1:11.1.0-5
Distribution: unstable
Urgency: medium
Maintainer: LLVM Packaging Team
Changed-By: Sylvestre Ledru
Closes: 1002607
Changes:
llvm-toolchain-11 (1:11.1.0-5) UNRELEASED; urgency=medium
.
* relax the llvm-11-linker-tools dep for apt.llvm.org
* Fix some lintian warnings
* Remove the build conflict on ocaml (Closes: #1002607)
Checksums-Sha1:
ff8c5241ea5dfb4e89e8ca31bd59efb2cdf880f6 6113 llvm-toolchain-11_11.1.0-5.dsc
599d2552ce33abf99c026d202d19d1c55970d60a 154180
llvm-toolchain-11_11.1.0-5.debian.tar.xz
fa0df98bf2569bca00cd553b02ec294437cde396 27275
llvm-toolchain-11_11.1.0-5_amd64.buildinfo
Checksums-Sha256:
667bac25d13ed254164bee40fce8c37e8e4eb188defa87ada3a3d9607956d027 6113
llvm-toolchain-11_11.1.0-5.dsc
fdd40aa4c641117e47b1910178a696147da9bf7a946c0e420215b4b5167472a8 154180
llvm-toolchain-11_11.1.0-5.debian.tar.xz
2765e2a1757d1e5b6aea01b488e3933efc767e0c6c1430a730b228a606219af5 27275
llvm-toolchain-11_11.1.0-5_amd64.buildinfo
Files:
644af1234c2cdb199a89bee799fbbf8b 6113 devel optional
llvm-toolchain-11_11.1.0-5.dsc
0354ffa645f84ee74204b6b2adea6e1a 154180 devel optional
llvm-toolchain-11_11.1.0-5.debian.tar.xz
3a13354628e0a3f280688e929d2b8921 27275 devel optional
llvm-toolchain-11_11.1.0-5_amd64.buildinfo
-BEGIN PGP SIGNATURE-
iQIzBAEBCAAdFiEEtg21mU05vsTRqVzPfmUo2nUvG+EFAmHugkQACgkQfmUo2nUv
G+FNiw//YBsUGuJPSK//Yu1inBusPT7YaECD8IMUlFWS6c83ZPHrT7hABMmKpEEk
nAAkCD+MFe8ZkHgqKFmVuwmz1uHnOg1HVAG3OcQsoK6+oznV9Fraqf9M76VR3Y/X
dfK27hVo0H6/XJlqX711MD1TNsvPTlnvxhKCVGaaBydcdM7VdCsADW4F8Aca/bbl
3e9VoVn239bWHViketkF3DtQRTETPB12fCiQuUDn6NyM28W3VCRm3guf4fdTHZTl
XI188JFPNKPVJ2fOLjnBegh/TDoosTtbOVmabkAmRelbJApq4CwSnW25+7S0/Gi5
N3rgMCWwRAJcW4GTSYOKyIYO5LrSHcEQJ++RjP5yE34JgUYlwGOt8w+mXJl5zNEv
Ft72KHE31B8NjCDa+r8LMVC6TdiI0oqFqh2ibkJEn96HUqA9MjFpc/1SbO1ZGpSD
m7dDzLFVD6QyCj44Dp1+OYUb/RJmKhKvHWWvb/GRL4+mBvuSTQuyIurcMbc5PNJL
kIMG1biSzlc243hsiNoM/vKJAy7oFPBEMfyL4ZEpdRS4HRczWpRodGztozT2fv5N
wxzAQ802D9/a1TNBClfUqPPl/4m2tNcRm8kif52b6Q+hukEua/06r5V2Es8FC6Gn
V39xVxgpAdTOWnc3CLOzgkHuC9d31AlDLUjF84ToTuwLJuJnyjY=
=wjt4
-END PGP SIGNATURE End Message ---
Bug#984284: marked as done (otb: ftbfs with GCC-11)
Your message dated Mon, 24 Jan 2022 11:49:11 +0100 with message-id and subject line insighttoolki4: ftbfs with GCC-11 has caused the Debian Bug report #984284, regarding otb: ftbfs with GCC-11 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 984284: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=984284 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:otb Version: 7.2.0+dfsg-1 Severity: normal Tags: sid bookworm User: debian-...@lists.debian.org Usertags: ftbfs-gcc-11 [This bug is not targeted to the upcoming bullseye release] Please keep this issue open in the bug tracker for the package it was filed for. If a fix in another package is required, please file a bug for the other package (or clone), and add a block in this package. Please keep the issue open until the package can be built in a follow-up test rebuild. The package fails to build in a test rebuild on at least amd64 with gcc-11/g++-11, but succeeds to build with gcc-10/g++-10. The severity of this report will be raised before the bookworm release, so nothing has to be done for the bullseye release. The full build log can be found at: http://people.debian.org/~doko/logs/20210228/filtered/gcc11/otb_7.2.0+dfsg-1_unstable_gcc11.log The last lines of the build log are at the end of this report. To build with GCC 11, either set CC=gcc-11 CXX=g++-11 explicitly, or install the gcc, g++, gfortran, ... packages from experimental. apt-get -t=experimental install g++ Common build failures are new warnings resulting in build failures with -Werror turned on, or new/dropped symbols in Debian symbols files. For other C/C++ related build failures see the porting guide at http://gcc.gnu.org/gcc-11/porting_to.html GCC 11 defaults to the GNU++17 standard. If your package installs header files in /usr/include, please don't work around C++17 issues by choosing a lower C++ standard for the package build, but fix these issues to build with the C++17 standard. [...] cd /<>/obj-x86_64-linux-gnu/Modules/Wrappers/ApplicationEngine/src && /usr/bin/c++ -DOTBApplicationEngine_EXPORTS -I/<>/Modules/ThirdParty/Boost/src -I/<>/obj-x86_64-linux-gnu/Modules/Core/Common -I/<>/Modules/Adapters/BoostAdapters/include -I/usr/include/gdal -I/<>/Modules/ThirdParty/ITK/include -I/<>/Modules/Core/Common/include -I/<>/Modules/ThirdParty/Ossim/include -I/usr/include/geotiff -I/<>/Modules/ThirdParty/OssimPlugins/src -I/<>/Modules/ThirdParty/OssimPlugins/src/ossim -I/<>/Modules/ThirdParty/OssimPlugins/include -I/<>/Modules/Adapters/OSSIMAdapters/include -I/<>/Modules/Core/ObjectList/include -I/<>/Modules/Core/Metadata/include -I/<>/Modules/Core/ImageBase/include -I/<>/Modules/Adapters/GdalAdapters/include -I/<>/obj-x86_64-linux-gnu/Modules/ThirdParty/TinyXML/src -I /<>/Modules/Core/VectorDataBase/include -I/<>/Modules/IO/IOGDAL/include -I/<>/Modules/IO/ExtendedFilename/include -I/<>/Modules/IO/IOBSQ/include -I/<>/Modules/IO/IOLUM/include -I/<>/Modules/IO/IOMSTAR/include -I/<>/Modules/IO/IOONERA/include -I/<>/Modules/IO/IORAD/include -I/<>/Modules/Core/Streaming/include -I/<>/Modules/IO/ImageIO/include -I/<>/Modules/Core/Interpolation/include -I/<>/Modules/Core/Transform/include -I/<>/Modules/Filtering/ImageManipulation/include -I/<>/Modules/Core/Functor/include -I/<>/Modules/Filtering/Path/include -I/<>/Modules/Filtering/VectorDataManipulation/include -I/<>/Modules/Filtering/Projection/include -I/<>/Modules/IO/IOKML/include -I/<>/Modules/IO/VectorDataIO/include -I/<>/Modules/Wrappers/Appl icationEngine/include -isystem /usr/include/ITK-4.13 -msse2 -mfpmath=sse -Wall -Wcast-align -Wdisabled-optimization -Wextra -Wformat=2 -Winvalid-pch -Wno-format-nonliteral -Wpointer-arith -Wunused -Wwrite-strings -funit-at-a-time -Wno-strict-overflow -Wno-deprecated -Wno-invalid-offsetof -Woverloaded-virtual -Wstrict-null-sentinel -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -O3 -DNDEBUG -fPIC -std=c++14 -o CMakeFiles/OTBApplicationEngine.dir/otbWrapperInputImageParameterUInt32.cxx.o -c /<>/Modules/Wrappers/ApplicationEngine/src/otbWrapperInputImageParameterUInt32.cxx [ 33%] Building CXX object Modules/Wrappers/ApplicationEngine/src/CMakeFiles/OTBApplicationEngine.dir/otbWrapperInputImageParameterInt16.cxx.o cd /<>/obj-x86_64-linux-gnu/Modules/Wrappers/ApplicationEngine/src && /usr/bin/c++ -DOTBApplicationEngine_EXPORTS -I/<>/Modules/ThirdParty/Boost/src -I/<>/obj-x86_64-linux-gnu/Modules/Core/Common
Bug#1004285: davical: problems after upgrade to php 8, calendar clients reports "500"
Package: davical Version: 1.1.10-1 Severity: grave Justification: renders package unusable X-Debbugs-Cc: be...@overeinder.net Dear Maintainer, *** Reporter, please consider answering these questions, where appropriate *** * What led up to the situation? I am using debian testing. After upgrade to php8 (with all dependencies), my calendar applications/clients on laptop and mobile were unable to contact the davical server. I have also logged into the davical (apache2) server via web browser, and there the user administration web pages seem to work as before. * What exactly did you do (or not do) that was effective (or ineffective)? I have looked at the apache2 log files and checked the /etc/php and /etc/davical directories if there were any references to php7 instead of php/php8. The apache2 log file reported [Mon Jan 24 11:29:29.678647 2022] [php:notice] [pid 684] [client /IPv6 address/] davical: LOG: response:-->DAViCal Fatal Error * What was the outcome of this action? There were no hints or clues for me to further investigate what might be going on. * What outcome did you expect instead? *** End of the template - remove these template lines *** -- System Information: Debian Release: bookworm/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 5.15.0-3-amd64 (SMP w/4 CPU threads) Kernel taint flags: TAINT_FIRMWARE_WORKAROUND Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages davical depends on: ii libawl-php0.62-1 ii libdbd-pg-perl3.15.0-2 ii libyaml-perl 1.30-1 ii perl 5.32.1-6 ii php 2:8.1+92 ii php-pgsql 2:8.1+92 ii php-xml 2:8.1+92 ii php8.1 [php] 8.1.1-4 ii php8.1-cli [php-cli] 8.1.1-4 ii php8.1-pgsql [php-pgsql] 8.1.1-4 ii php8.1-xml [php-xml] 8.1.1-4 ii postgresql-client-14 [postgresql-client] 14.1-5 Versions of packages davical recommends: ii php-curl2:8.1+92 ii php8.1-curl [php-curl] 8.1.1-4 ii postgresql 14+237 Versions of packages davical suggests: pn php-ldap | php5-ldap -- no debconf information
Bug#1004223: closing 1004223
Salvatore Bonaccorso writes: > close 1004223 5.4.1+repack-1 > thanks Yes, the problem is fixed in later Minetest versions – as I said … However, the current version in Debian stable (bullseye) is 5.3.0. This means that the patch needs to be backported to protect users! signature.asc Description: PGP signature
Processed: insighttoolki4: ftbfs with GCC-11
Processing commands for cont...@bugs.debian.org: > fixed 984284 insighttoolkit4/4.13.3withdata-dfsg2-1 Bug #984284 [src:insighttoolkit4] otb: ftbfs with GCC-11 Marked as fixed in versions insighttoolkit4/4.13.3withdata-dfsg2-1. > thanks Stopping processing here. Please contact me if you need assistance. -- 984284: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=984284 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1000162: ima-evm-utils: FTBFS with no internet connection
пн, 24 янв. 2022 г. в 13:00, Bastian Germann : > > On Thu, 18 Nov 2021 21:59:12 +0100 Bastian Germann wrote: > > Your package fails to build from scratch in an environment with no > > internect connection. > > Please check the buildd logs for this. > > I am going to fix this via a NMU as it was not resolved with the latest > upload. Ack for the NMU. -- With best wishes Dmitry
Bug#1000162: marked as done (ima-evm-utils: FTBFS with no internet connection)
Your message dated Mon, 24 Jan 2022 10:18:56 + with message-id and subject line Bug#1000162: fixed in ima-evm-utils 1.4-1.1 has caused the Debian Bug report #1000162, regarding ima-evm-utils: FTBFS with no internet connection 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.) -- 1000162: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1000162 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: ima-evm-utils Severity: serious Version: 1.3.2-2.1 Hey, Your package fails to build from scratch in an environment with no internect connection. Please check the buildd logs for this. Thanks, Bastian --- End Message --- --- Begin Message --- Source: ima-evm-utils Source-Version: 1.4-1.1 Done: Bastian Germann We believe that the bug you reported is fixed in the latest version of ima-evm-utils, 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 1000...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Bastian Germann (supplier of updated ima-evm-utils 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, 24 Jan 2022 10:49:06 +0100 Source: ima-evm-utils Architecture: source Version: 1.4-1.1 Distribution: unstable Urgency: high Maintainer: Dmitry Baryshkov Changed-By: Bastian Germann Closes: 1000162 Changes: ima-evm-utils (1.4-1.1) unstable; urgency=high . * Non-maintainer upload. * d/libimaevm2.symbols: Correct SO version * d/control: Add docbook-xml build dependency (Closes: #1000162) Checksums-Sha1: a1de96f963207baf53339b0e3f6ad0ebd2006e94 1961 ima-evm-utils_1.4-1.1.dsc 588a622c5a35a33e85f1335fb012374c57ef0517 5796 ima-evm-utils_1.4-1.1.debian.tar.xz 805bf8994a41b897dd00679a437a30299234f876 6323 ima-evm-utils_1.4-1.1_source.buildinfo Checksums-Sha256: 4844edfcec2fcc1871c58bb151fff2c259f16591006468411eebf68280a82f6d 1961 ima-evm-utils_1.4-1.1.dsc 89c3bd258ecdc41973a04fba444725eddb854e6eec942168ee8c8dbabb394f33 5796 ima-evm-utils_1.4-1.1.debian.tar.xz 6016c2c3b61c1c7aee62d2bb5f062c6c618880e18ebd93c022970f70abdc0050 6323 ima-evm-utils_1.4-1.1_source.buildinfo Files: 0005d654f6d234e18bb46f3e7e601ca1 1961 utils optional ima-evm-utils_1.4-1.1.dsc 5396a53baeaa6bdcbf7dab322f42e47d 5796 utils optional ima-evm-utils_1.4-1.1.debian.tar.xz 88d8792aaf5200a14da09f019dbb286a 6323 utils optional ima-evm-utils_1.4-1.1_source.buildinfo -BEGIN PGP SIGNATURE- iQHEBAEBCgAuFiEEQGIgyLhVKAI3jM5BH1x6i0VWQxQFAmHudwsQHGJhZ2VAZGVi aWFuLm9yZwAKCRAfXHqLRVZDFIIjDAD4rroWOx2c+nr/xnhuyJejB7j8+2CaB5Iw Fdzfu6dqhAr+avx6z7bJvS3Qr9eVd89aUbAeWqBZCYfHQhQUTAfLTteE1t0Hc4WM 08664OJwUoW9eGbiP2pOqZdoSmUkfxUJRWixBrbdWE8eimsTU7FB6d68k1Dk5Jl2 a9nQAClXjW0xPltSwLQ2mczGyzP6HsZuKDjwTb1sKUjMAst1F70tz5rhBE4+ezpT h7wKQajSBubfJMyaAj/FGOUCvNrCLY4o3V/PKb53pszbQ6+Nbb+UQVwsBo+TLEbw 7nW6eJA3BxG9pfrbhIrfSUzciq0fotskn3FcjRJhbZkhIJG/LNebL6xaT8uFDr0Y cxRDrHXyx0FCo50v32t1CspeEf2TEOfIZ4d89SpgA2AzqVKVXk/KZxjDVHRIFrNN 9XhaYHJHygipUAhgLhRyT3VeTVcRroxGBS/QifGx5avNb/YYCiluT9V42boTaPtK QtK8s/mWmEukBCWvTYQ9AL5wPLRYjpY= =VmJy -END PGP SIGNATURE End Message ---
Processed: unarchiving 759824, reopening 759824, unarchiving 849973, reopening 849973, unarchiving 866915 ...
Processing commands for cont...@bugs.debian.org:
> # src:pyfltk was reintroduced:
> https://lists.debian.org/msgid-search/546c2c3d77eaef6dc2b26c7ed7663f16df847bda.ca...@debian.org
> unarchive 759824
Bug #759824 {Done: Debian FTP Masters }
[src:pyfltk] pyfltk: FTBFS: ./python/fltk_wrap.cpp:5241:35: error: format not a
string literal and no format arguments [-Werror=format-security]
Unarchived Bug 759824
> reopen 759824
Bug #759824 {Done: Debian FTP Masters }
[src:pyfltk] pyfltk: FTBFS: ./python/fltk_wrap.cpp:5241:35: error: format not a
string literal and no format arguments [-Werror=format-security]
'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 1.3.0-1+rm.
> unarchive 849973
Bug #849973 {Done: Debian FTP Masters }
[src:pyfltk] python-fltk: please add dependency “Suggests: python-fltk-doc”
Unarchived Bug 849973
> reopen 849973
Bug #849973 {Done: Debian FTP Masters }
[src:pyfltk] python-fltk: please add dependency “Suggests: python-fltk-doc”
'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 1.3.0-1+rm.
> unarchive 866915
Bug #866915 {Done: Debian FTP Masters }
[src:pyfltk] Updating the pyfltk Uploaders list
Unarchived Bug 866915
> reopen 866915
Bug #866915 {Done: Debian FTP Masters }
[src:pyfltk] Updating the pyfltk Uploaders list
'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 1.3.0-1+rm.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
759824: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=759824
849973: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=849973
866915: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=866915
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Processed: closing 759824
Processing commands for cont...@bugs.debian.org: > close 759824 1.3.7+repack-1 Bug #759824 [src:pyfltk] pyfltk: FTBFS: ./python/fltk_wrap.cpp:5241:35: error: format not a string literal and no format arguments [-Werror=format-security] Marked as fixed in versions pyfltk/1.3.7+repack-1. Bug #759824 [src:pyfltk] pyfltk: FTBFS: ./python/fltk_wrap.cpp:5241:35: error: format not a string literal and no format arguments [-Werror=format-security] Marked Bug as done > thanks Stopping processing here. Please contact me if you need assistance. -- 759824: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=759824 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1000162: ima-evm-utils: FTBFS with no internet connection
On Thu, 18 Nov 2021 21:59:12 +0100 Bastian Germann wrote: Your package fails to build from scratch in an environment with no internect connection. Please check the buildd logs for this. I am going to fix this via a NMU as it was not resolved with the latest upload.diff -Nru ima-evm-utils-1.4/debian/changelog ima-evm-utils-1.4/debian/changelog --- ima-evm-utils-1.4/debian/changelog 2022-01-22 04:21:14.0 +0100 +++ ima-evm-utils-1.4/debian/changelog 2022-01-24 10:49:06.0 +0100 @@ -1,3 +1,11 @@ +ima-evm-utils (1.4-1.1) unstable; urgency=high + + * Non-maintainer upload. + * d/libimaevm2.symbols: Correct SO version + * d/control: Add docbook-xml build dependency (Closes: #1000162) + + -- Bastian Germann Mon, 24 Jan 2022 10:49:06 +0100 + ima-evm-utils (1.4-1) unstable; urgency=medium * New upstream release diff -Nru ima-evm-utils-1.4/debian/control ima-evm-utils-1.4/debian/control --- ima-evm-utils-1.4/debian/control2021-09-24 11:39:11.0 +0200 +++ ima-evm-utils-1.4/debian/control2022-01-24 10:49:06.0 +0100 @@ -5,6 +5,7 @@ Standards-Version: 4.6.0 Build-Depends: asciidoc, debhelper (>= 11), + docbook-xml, docbook-xsl, attr, libattr1-dev, diff -Nru ima-evm-utils-1.4/debian/libimaevm2.symbols ima-evm-utils-1.4/debian/libimaevm2.symbols --- ima-evm-utils-1.4/debian/libimaevm2.symbols 2021-09-24 11:39:11.0 +0200 +++ ima-evm-utils-1.4/debian/libimaevm2.symbols 2022-01-24 10:49:06.0 +0100 @@ -1,4 +1,4 @@ -libimaevm.so.2 libimaevm2 #MINVER# +libimaevm.so.3 libimaevm2 #MINVER# * Build-Depends-Package: libimaevm-dev calc_keyid_v1@Base 1.3.1 calc_keyid_v2@Base 1.3.1
Processed: Re: src:isc-dhcp: please switch to bundled BIND 9 libraries
Processing control commands: > severity -1 serious Bug #942502 [src:isc-dhcp] src:isc-dhcp: please switch to bundled BIND 9 libraries Severity set to 'serious' from 'important' -- 942502: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=942502 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
