Processed: retitle 992058 to opensysusers: uses `eval` on data that is not supposed to be safe to eval (CVE-2021-40084)
Processing commands for cont...@bugs.debian.org: > retitle 992058 opensysusers: uses `eval` on data that is not supposed to be > safe to eval (CVE-2021-40084) Bug #992058 [opensysusers] opensysusers: uses `eval` on data that is not supposed to be safe to eval Changed Bug title to 'opensysusers: uses `eval` on data that is not supposed to be safe to eval (CVE-2021-40084)' from 'opensysusers: uses `eval` on data that is not supposed to be safe to eval'. > thanks Stopping processing here. Please contact me if you need assistance. -- 992058: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=992058 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#992919: lebiniou: Upgrade fails: trying to overwrite '/usr/share/lebiniou/etc/schemes.json', which is also in package lebiniou-data 3.54.1-1
Package: lebiniou Version: 3.61.1-1 Severity: serious Unpacking lebiniou (3.61.1-1) over (3.54.1-1) ... dpkg: error processing archive /tmp/apt-dpkg-install-ryc9hl/423-lebiniou_3.61.1-1_i386.deb (--unpack): trying to overwrite '/usr/share/lebiniou/etc/schemes.json', which is also in package lebiniou-data 3.54.1-1 dpkg-deb: error: paste subprocess was killed by signal (Broken pipe) dpkg: considering deconfiguration of lebiniou, which would be broken by installation of lebiniou-data ... dpkg: yes, will deconfigure lebiniou (broken by lebiniou-data) Preparing to unpack .../424-lebiniou-data_3.61.0-2_all.deb ... De-configuring lebiniou (3.54.1-1) ... Unpacking lebiniou-data (3.61.0-2) over (3.54.1-1) ... […] Errors were encountered while processing: /tmp/apt-dpkg-install-ryc9hl/423-lebiniou_3.61.1-1_i386.deb This is likely either a file which is accidentially shipped in both packages or the file was moved from one package to the other and according Breaks and Replaces headers are missing. -- System Information: Debian Release: bookworm/sid APT prefers unstable APT policy: (990, 'unstable'), (600, 'testing'), (500, 'unstable-debug'), (500, 'buildd-unstable'), (110, 'experimental'), (1, 'experimental-debug'), (1, 'buildd-experimental')
Bug#992917: grok: FTBFS due to RPC removal from glibc
Source: grok Version: 1.20110708.1-4.5 Severity: serious Tags: patch ftbfs Justification: fails to build from source (but built successfully in the past) The glibc SunRPC implementation has been marked obsolete for some time. It has been removed upstream from glibc 2.32, and it got disabled in the recent glibc uploads. The TI RPC implementation should be used instead, which also brings new features (IPv6, Kerberos support, ...). For this reason grok now fails to build from source. You will find attached a patch to switch to the TI RPC implementation, fixing the FTBFS. Regards, Aurelien --- grok-1.20110708.1/debian/control +++ grok-1.20110708.1/debian/control @@ -14,6 +14,7 @@ libevent-dev, libpcre3-dev, libtokyocabinet-dev, + libtirpc-dev, Standards-Version: 3.9.3 Homepage: http://code.google.com/p/semicomplete/wiki/Grok Vcs-Browser: http://anonscm.debian.org/gitweb/?p=collab-maint/grok.git --- grok-1.20110708.1/debian/patches/libtirpc.patch +++ grok-1.20110708.1/debian/patches/libtirpc.patch @@ -0,0 +1,19 @@ +Description: use TI RPC implementation instead of removed GNU libc one +Author: Aurelien Jarno +Last-Update: 2021-08-24 + +--- grok-1.20110708.1.orig/Makefile grok-1.20110708.1/Makefile +@@ -31,6 +31,12 @@ ifeq ($(PLATFORM), GNULinux) + LDFLAGS+=-ldl + endif + ++# Use TI RPC on GNU/Linux ++ifeq ($(PLATFORM), GNULinux) ++CFLAGS+=-I/usr/include/tirpc ++LDFLAGS+=-ltirpc ++endif ++ + # For GNU/kFreeBSD, we also need libdl + ifeq ($(PLATFORM), GNUkFreeBSD) + LDFLAGS+=-ldl --- grok-1.20110708.1/debian/patches/series +++ grok-1.20110708.1/debian/patches/series @@ -7,3 +7,4 @@ gperf-function-declaration.patch move_ldflags.patch fix_gcc10.patch +libtirpc.patch
Processed: grub-legacy: Removing kernel image fails: /usr/sbin/update-grub: line 273: tempfile: command not found
Processing control commands: > affects -1 src:linux Bug #992915 [grub-legacy] grub-legacy: Removing kernel image fails: /usr/sbin/update-grub: line 273: tempfile: command not found Added indication that 992915 affects src:linux -- 992915: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=992915 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#992915: grub-legacy: Removing kernel image fails: /usr/sbin/update-grub: line 273: tempfile: command not found
Package: grub-legacy
Severity: serious
Version: 0.97-77
Tags: patch
Control: affects -1 src:linux
Removing a kernel image fails as follows due to grub-legacy's
update-grub uses the deprecated and now removed tempfile utility:
Removing linux-image-5.10.0-6-amd64 (5.10.28-1) ...
/etc/kernel/postrm.d/initramfs-tools:
update-initramfs: Deleting /boot/initrd.img-5.10.0-6-amd64
/etc/kernel/postrm.d/zz-update-grub:
Searching for GRUB installation directory ... found: /boot/grub
/usr/sbin/update-grub: line 273: tempfile: command not found
run-parts: /etc/kernel/postrm.d/zz-update-grub exited with return code 127
dpkg: error processing package linux-image-5.10.0-6-amd64 (--remove):
installed linux-image-5.10.0-6-amd64 package post-removal script subprocess
returned error exit status 1
dpkg: too many errors, stopping
Errors were encountered while processing:
linux-image-5.10.0-6-amd64
Processing was halted because there were too many errors.
This currently blocks all further apt activities.
The following patch seems to fix the issue:
--- /usr/sbin/update-grub~ 2018-05-05 14:45:49.0 +0200
+++ /usr/sbin/update-grub 2021-08-25 00:26:21.52990 +0200
@@ -270,7 +270,7 @@
# Default options to use in a new config file. This will only be used if
$menu_file
# doesn't already exist. Only edit the lines between the two "EOF"s. The
others are
# part of the script.
-newtemplate=$(tempfile)
+newtemplate=$(mktemp)
cat > "$newtemplate" <> $buffer
echo "## lines between the AUTOMAGIC KERNELS LIST markers will be modified" >>
$buffer
echo "## by the debian update-grub script except for the default options
below" >> $buffer
@@ -1034,7 +1034,7 @@
fi
else
value="$1"
- newmenu=$(tempfile)
+ newmenu=$(mktemp)
sed -e "s/^[[:blank:]]*default[[:blank:]]*[[:digit:]]*\(.*\)/default
${value}\1/;b" $menu > $newmenu
cat $newmenu > $menu
rm -f $newmenu
-- System Information:
Debian Release: bookworm/sid
APT prefers unstable
APT policy: (990, 'unstable'), (600, 'testing'), (500, 'unstable-debug'),
(500, 'buildd-unstable'), (110, 'experimental'), (1, 'experimental-debug'), (1,
'buildd-experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 5.10.0-8-amd64 (SMP w/4 CPU threads)
Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)
LSM: AppArmor: enabled
Versions of packages grub-legacy depends on:
ii grub-common 2.04-20
ii libc6-i386 2.31-17
grub-legacy recommends no packages.
Versions of packages grub-legacy suggests:
pn grub-legacy-doc
pn mdadm
ii multiboot0.6.96+20101113-3
-- no debconf information
Bug#978924: marked as done (wp2latex: ftbfs with autoconf 2.70)
Your message dated Tue, 24 Aug 2021 22:20:56 + with message-id and subject line Bug#978924: fixed in wp2latex 3.98+ds-1 has caused the Debian Bug report #978924, regarding wp2latex: ftbfs with autoconf 2.70 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.) -- 978924: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=978924 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:wp2latex Version: 3.91-1 Severity: normal Tags: sid bookworm User: d...@debian.org Usertags: ftbfs-ac270 [This bug report is not targeted to the upcoming bullseye release] The package fails to build in a test rebuild on at least amd64 with autoconf 2.70, but succeeds to build with autoconf 2.69. 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://qa-logs.debian.net/2020/09/26.ac270/wp2latex_3.91-1_unstable_ac270.log The last lines of the build log are at the end of this report. To build with autoconf 2.70, please install the autoconf package from experimental: apt-get -t=experimental install autoconf [...] ./lib/autoconf/headers.m4:657: AC_HEADER_STDC is expanded from... configure.in:91: the top level configure.in:105: warning: The macro `AC_TYPE_SIGNAL' is obsolete. configure.in:105: You should run autoupdate. ./lib/autoconf/types.m4:776: AC_TYPE_SIGNAL is expanded from... configure.in:105: the top level configure.in:407: warning: The macro `AC_TRY_LINK' is obsolete. configure.in:407: You should run autoupdate. ./lib/autoconf/general.m4:2816: AC_TRY_LINK is expanded from... configure.in:407: the top level configure.in:470: warning: The macro `AC_TRY_COMPILE' is obsolete. configure.in:470: You should run autoupdate. ./lib/autoconf/general.m4:2743: AC_TRY_COMPILE is expanded from... configure.in:470: the top level configure.in:497: warning: The macro `AC_TRY_COMPILE' is obsolete. configure.in:497: You should run autoupdate. ./lib/autoconf/general.m4:2743: AC_TRY_COMPILE is expanded from... configure.in:497: the top level configure.in:513: warning: The macro `AC_TRY_COMPILE' is obsolete. configure.in:513: You should run autoupdate. ./lib/autoconf/general.m4:2743: AC_TRY_COMPILE is expanded from... configure.in:513: the top level configure.in:555: warning: The macro `AC_TRY_COMPILE' is obsolete. configure.in:555: You should run autoupdate. ./lib/autoconf/general.m4:2743: AC_TRY_COMPILE is expanded from... configure.in:555: the top level autoheader: warning: autoconf input should be named 'configure.ac', not 'configure.in' debian/rules override_dh_auto_configure make[1]: Entering directory '/<>' ./configure --prefix=/usr checking for g++... g++ checking whether the C++ compiler works... yes checking for C++ compiler default output file name... a.out checking for suffix of executables... checking whether we are cross compiling... no checking for suffix of object files... o checking whether the compiler supports GNU C++... yes checking whether g++ accepts -g... yes checking for g++ option to enable C++11 features... none needed checking for gcc... gcc checking whether the compiler supports GNU C... yes checking whether gcc accepts -g... yes checking for gcc option to enable C11 features... none needed checking whether make sets $(MAKE)... yes checking if -lm is necessary... checking for sin in -lm... yes checking for sys/types.h... yes checking for sys/stat.h... yes checking for strings.h... yes checking for inttypes.h... yes checking for stdint.h... yes checking for unistd.h... yes checking for grep that handles long lines and -e... /bin/grep checking for egrep... /bin/grep -E checking for limits.h... yes checking for stddef.h... yes checking for stdlib.h... yes checking for string.h... yes checking for strings.h... (cached) yes checking for unistd.h... (cached) yes checking for values.h... yes checking for stdbool.h that conforms to C99... yes checking for _Bool... yes checking for an ANSI C-conforming const... yes checking for inline... inline checking for size_t... yes configure: error: cannot find install-sh, install.sh, or shtool in "." "./.." "./../.." make[1]: *** [debian/rules:19: override_dh_auto_configure] Error 1 make[1]: Leaving directory '/<>' make: *** [debian/rules:15: build] Error 2 dpkg-buildpackage: error: debian/rules build subprocess returned exit status 2 --- End Message --- --- Begin Message --- Source: wp2latex Source-Version: 3.98+ds-1 Done: Hilmar Preusse We believe that the bug you reported is fixed in the latest version of wp2latex, which is due to be instal
Processed: tagging 992627
Processing commands for cont...@bugs.debian.org: > tags 992627 + sid bookworm Bug #992627 [dino-im] dino-im: Dino-im crashes with GLib error Bug #992689 [dino-im] dino crashing with new gnome 40 Added tag(s) bookworm and sid. Added tag(s) sid and bookworm. > thanks Stopping processing here. Please contact me if you need assistance. -- 992627: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=992627 992689: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=992689 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: tagging 992913
Processing commands for cont...@bugs.debian.org: > tags 992913 + sid bookworm Bug #992913 [trickle] trickle: FTBFS due to RPC removal from glibc Added tag(s) sid and bookworm. > thanks Stopping processing here. Please contact me if you need assistance. -- 992913: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=992913 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: tagging 992914
Processing commands for cont...@bugs.debian.org: > tags 992914 + sid bookworm Bug #992914 [src:libassa] libassa: FTBFS due to RPC removal from glibc Added tag(s) sid and bookworm. > thanks Stopping processing here. Please contact me if you need assistance. -- 992914: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=992914 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#992911: marked as done (rust-grep_0.2.8-1_amd64-buildd.changes REJECTED)
Your message dated Tue, 24 Aug 2021 22:06:37 + with message-id and subject line Bug#992911: fixed in rust-grep 0.2.8-2 has caused the Debian Bug report #992911, regarding rust-grep_0.2.8-1_amd64-buildd.changes REJECTED 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.) -- 992911: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=992911 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: rust-grep Version: 0.2.8-1 Severity: serious On 2021-08-24 21:13, Debian FTP Masters wrote: > librust-grep-dev_0.2.8-1_amd64.deb: has 6 file(s) with a timestamp too far in > the past: > usr/share/cargo/registry/grep-0.2.8/COPYING (Thu Nov 29 21:33:09 1973) > usr/share/cargo/registry/grep-0.2.8/LICENSE-MIT (Thu Nov 29 21:33:09 1973) > usr/share/cargo/registry/grep-0.2.8/README.md (Thu Nov 29 21:33:09 1973) > usr/share/cargo/registry/grep-0.2.8/UNLICENSE (Thu Nov 29 21:33:09 1973) > usr/share/cargo/registry/grep-0.2.8/examples/simplegrep.rs (Thu Nov 29 > 21:33:09 1973) usr/share/cargo/registry/grep-0.2.8/src/lib.rs (Thu Nov 29 > 21:33:09 1973) > > > > === > > Please feel free to respond to this email if you don't understand why > your files were rejected, or if you upload new files which address our > concerns. > > > --- End Message --- --- Begin Message --- Source: rust-grep Source-Version: 0.2.8-2 Done: Peter Michael Green We believe that the bug you reported is fixed in the latest version of rust-grep, 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 992...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Peter Michael Green (supplier of updated rust-grep 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, 24 Aug 2021 21:24:51 + Source: rust-grep Architecture: source Version: 0.2.8-2 Distribution: unstable Urgency: medium Maintainer: Debian Rust Maintainers Changed-By: Peter Michael Green Closes: 992911 Changes: rust-grep (0.2.8-2) unstable; urgency=medium . * Team upload. * Package grep 0.2.8 from crates.io using debcargo 2.4.4 * Fix 1973 timestamps (Closes: 992911). Checksums-Sha1: ff03a2334fd0755f974be324f36b17bed5aa9885 2692 rust-grep_0.2.8-2.dsc 617a41e596605edf33dc929cbc963f93c256ff8d 3712 rust-grep_0.2.8-2.debian.tar.xz a71972e62ea38bf0c1d32c8cfe2299d8e3ff9e88 9706 rust-grep_0.2.8-2_source.buildinfo Checksums-Sha256: 0368b00afe4658105a03960b3fef8f935b8610c82e3be351f19ee85618da78a3 2692 rust-grep_0.2.8-2.dsc 2d1d18870d4a06e4282dc22a3502289d3e88ee3b8701c831e7b541701c99d8c2 3712 rust-grep_0.2.8-2.debian.tar.xz b0756bcbf7f9588480cd85ddb5c6390f125b480da714c8fbb0bff90a5aca4eb7 9706 rust-grep_0.2.8-2_source.buildinfo Files: 114c42adedb176d93f495e9ae4ee8ced 2692 rust optional rust-grep_0.2.8-2.dsc f5e73b1f12d7c3559c194edb1a5f6ee2 3712 rust optional rust-grep_0.2.8-2.debian.tar.xz be02338fa8f685046d4f32f89b042e7b 9706 rust optional rust-grep_0.2.8-2_source.buildinfo -BEGIN PGP SIGNATURE- iQJIBAEBCAAyFiEEU0DQATYMplbjSX63DEjqKnqP/XsFAmElZzAUHHBsdWd3YXNo QGRlYmlhbi5vcmcACgkQDEjqKnqP/XutpRAAmilj3eyl0PuoNrQ/VWBuOw5EWDMq N5tzFS8FZD657YoWvvmN9Jx4nbYcp+k4hfSOnRoyyDm1ccjGFTFRiK9ySI8uJqnO B1YhqpIccXyk3tEMShx87Wt++KuH3SELzu0N9odve1BHuIjXO8/9QUOlEzf8EnA3 0fu4FME5UCrXT9nAjbSN+n1/2KJxPgBphoJ0kMGLCVydPNscHwgleYMo0gXVFQa7 SUnrF6KqAxtJIPTQ0WdCedVelLv+eyL7PhbL9PYQElNSaoOuRoqhXSXxmg9AXA5H j6hluc92mr+dq6BraYD8GwCjWfN+Cuixb8n73ENhrgc7VRLU2Ty/h4HsG3kXaCiX X8CZwxklml65CWFrJDSPi732oiJEKtIus56N5nOGpgPDQsijEvIHDSR3bxq4cq/6 9e2WqjDrGppWIj/bjv4rro6rWuPr1RCeAerxIJTL2w1u63KwSLhyw+b6e6eyO4Is bFyN4q6yqv8GP6Lp83VmXirRWKLuMuT+3esd0+p+BiEJWieLVfj4dFySAGdaWzux /zDhWj/o6bg0rnXFNN0NuVRXlTgZzFE8Kxv/PawQc7v5y0SjQ4jHjn0QvWTUL24L 2W1tWrHJMgrITnjHeNCpx6OIjqOtN+DDUopP5pZXoOyHSqtzPBOyDzlwS9Id0yps 9rEXmHk7UkeX/xk= =WzcO -END PGP SIGNATURE End Message ---
Processed: tagging 992908
Processing commands for cont...@bugs.debian.org: > tags 992908 + sid bookworm Bug #992908 [src:awesome] awesome: autopkgtest regression between 20 and 23 August 2021: Could not resolve keysym Added tag(s) sid and bookworm. > thanks Stopping processing here. Please contact me if you need assistance. -- 992908: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=992908 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: tagging 992902
Processing commands for cont...@bugs.debian.org: > tags 992902 + sid bookworm Bug #992902 [lizzie] lizzie build-depends on removed package Added tag(s) sid and bookworm. > thanks Stopping processing here. Please contact me if you need assistance. -- 992902: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=992902 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: tagging 992897
Processing commands for cont...@bugs.debian.org: > tags 992897 + sid bookworm Bug #992897 [debian-design] debian-design build-depends on obsolete version of boxer-data Added tag(s) sid and bookworm. > thanks Stopping processing here. Please contact me if you need assistance. -- 992897: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=992897 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#992914: libassa: FTBFS due to RPC removal from glibc
Source: libassa Version: 3.5.1-7 Severity: serious Tags: patch ftbfs Justification: fails to build from source (but built successfully in the past) The glibc SunRPC implementation has been marked obsolete for some time. It has been removed upstream from glibc 2.32, and it got disabled in the recent glibc uploads. The TI RPC implementation should be used instead. libassa was already supposed to use libtirpc, but in practice was still linked to glibc due a missing entry in Makefile.am. Please find attach a patch fixing the FTBFS. --- libassa-3.5.1/debian/patches/06-link-with-tirpc.diff +++ libassa-3.5.1/debian/patches/06-link-with-tirpc.diff @@ -0,0 +1,18 @@ +Description: Correctly link with libtirpc +Author: Aurelien Jarno +Forwarded: no +Last-Update: 2021-08-24 +--- +This patch header follows DEP-3: http://dep.debian.net/deps/dep3/ + +--- libassa-3.5.1.orig/assa/Makefile.am libassa-3.5.1/assa/Makefile.am +@@ -111,6 +111,8 @@ libassa_3_5_la_LDFLAGS = \ + @WIN32_EXTRA_LDFLAGS@ \ + -version-info @LIBASSA_SO_VERSION@ + ++libassa_3_5_la_LIBADD = @TIRPC_LIBS@ ++ + # Disable autoheader. + AUTOHEADER=echo + --- libassa-3.5.1/debian/patches/series +++ libassa-3.5.1/debian/patches/series @@ -3,3 +3,4 @@ 03-support-hurd.patch 04-fix-more-spelling.patch 05-remove-build-path-from-doxygen.patch +06-link-with-tirpc.diff
Bug#992904: marked as done (shut-up build-depends on removed transitional package.)
Your message dated Tue, 24 Aug 2021 21:51:06 + with message-id and subject line Bug#992904: fixed in shut-up 0.3.3-3 has caused the Debian Bug report #992904, regarding shut-up build-depends on removed transitional package. 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.) -- 992904: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=992904 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: shut-up Version: 0.3.3-1 Severity: serious Tags: bookworm, sid shut-up build-depends on the s-el binary package which has been dropped by the s-el source package. It is still present in unstable as a cruft package but is completely gone from testing. Since this package was previously an empty transitional package it should be possible to simply update the dependency. --- End Message --- --- Begin Message --- Source: shut-up Source-Version: 0.3.3-3 Done: Sean Whitton We believe that the bug you reported is fixed in the latest version of shut-up, 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 992...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Sean Whitton (supplier of updated shut-up package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Tue, 24 Aug 2021 14:21:45 -0700 Source: shut-up Architecture: source Version: 0.3.3-3 Distribution: unstable Urgency: medium Maintainer: Debian Emacsen team Changed-By: Sean Whitton Closes: 992904 Changes: shut-up (0.3.3-3) unstable; urgency=medium . [ Nicholas D Steeves ] * Drop emacs24 from Enhances (package does not exist in bullseye). . [ Sean Whitton ] * Update build-deps s-el -> elpa-s, dash-el -> elpa-dash (Closes: #992904). . shut-up (0.3.3-2) UNRELEASED; urgency=medium . * Drop spurious slash from end of Vcs-Git. Checksums-Sha1: c63d3658cc77a4ad0dc1f44d2d07837655854e73 2055 shut-up_0.3.3-3.dsc 4cb09225a192fd826c12061f786df94f166c172e 3072 shut-up_0.3.3-3.debian.tar.xz Checksums-Sha256: aae8193dcef2537ecc5e30b7d3c3d7a14fd98dbefc2f7efa6a8ec90d4b4f193c 2055 shut-up_0.3.3-3.dsc e93dab1d543e5ce7fb059e541aba7bdce3c6640aa1e8caf63563cf96b1242d59 3072 shut-up_0.3.3-3.debian.tar.xz Files: de08ea792920d33c6ff0f68894dcb2f4 2055 lisp optional shut-up_0.3.3-3.dsc bce963ecf9c421b56f2d46a047f1517b 3072 lisp optional shut-up_0.3.3-3.debian.tar.xz -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEm5FwB64DDjbk/CSLaVt65L8GYkAFAmElYv8ACgkQaVt65L8G YkBDZQ//SzbZSiwYKKTPjozDUQdn3/CjZd8Gaqt7wjociG9kncK0S0FajCgbFx1w 5UNq0lLO0LeYY60cV9gpSJ/+IKwffz7AvP+QdDoboYzy5kP8FY+jH/qM71YXFbce +A+7AiaXuX4CIxCgfCtZmcFnsu+292ZZfIvaBoyz4OeBvKirix0zW2H2QQKrid/L v6sQDwaKsHV8q+t2itZ86VkdSEbSPOtzzy7ryWYPUtkG2hRx8RBO6ecfk7WmUsGF 2LUOcp1K8T/IOomqqcYg5Jr/jQQAZGjgqAWr5o0tw7O+3hxtMt5ivk56gUuuc2bj ibVgtbLwjBrMX44k/XbZSa4q/KxuONZilpH4fMHhOTiSkCpsBvbAAs7sSUer5w18 vOEiHkiBBAFZYqhFiY8kcvUE4PV23XemewuevfuFV4367gxvIltsjVtqBe/blekg zS33hPSyyyFBLgiGfAsCzA9mjc6xOm96qn40JcD4Ns8kpAuHUckYzwDccSto5+tD h8OzYL492AnEhMH5G2cTKxangliEdi5hAXXeEjLKXadERfxlV6C/hw/t64vxVLGR F6iVDOMS1tg355eTEIx/g6r4wJ5IxqZB4PF0jYmon/3ipjwHMoGj/GvQIVs3qvin QZDgjBvVAmw/3PKAFNVgDfnKJ+qtm94CfMm7mrngG40cus+p0Fg= =2ONC -END PGP SIGNATURE End Message ---
Bug#992900: marked as done (epl build-depends on removed transitional package.)
Your message dated Tue, 24 Aug 2021 21:48:45 + with message-id and subject line Bug#992900: fixed in epl 0.9-4 has caused the Debian Bug report #992900, regarding epl build-depends on removed transitional package. 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.) -- 992900: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=992900 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: epl Version: 0.9-3 Severity: serious Tags: bookworm, sid epl build-depends on the s-el binary package which has been dropped by the s-el source package. It is still present in unstable as a cruft package but is completely gone from testing. Since this package was previously an empty transitional package it should be possible to simply update the dependency. --- End Message --- --- Begin Message --- Source: epl Source-Version: 0.9-4 Done: Sean Whitton We believe that the bug you reported is fixed in the latest version of epl, 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 992...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Sean Whitton (supplier of updated epl package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Tue, 24 Aug 2021 14:21:27 -0700 Source: epl Architecture: source Version: 0.9-4 Distribution: unstable Urgency: medium Maintainer: Debian Emacsen Team Changed-By: Sean Whitton Closes: 992900 Changes: epl (0.9-4) unstable; urgency=medium . [ Nicholas D Steeves ] * Drop emacs25 from Enhances (package does not exist in bullseye). . [ Sean Whitton ] * Update build-dep s-el -> elpa-s (Closes: #992900). * Drop --parallel from d/rules. Checksums-Sha1: fc39fc716a7756866f87176cd1283018f755df31 2018 epl_0.9-4.dsc 19582502250468d88247e45e3798474128ab2cea 2500 epl_0.9-4.debian.tar.xz Checksums-Sha256: c46beb6278881432e1aeec7e85e7cd02b1e6505108132c80471288297ea40e72 2018 epl_0.9-4.dsc 1ba612b1c8cd1fd7d0113ffe462b3f81f8bd9d8712447887927ef701a30b84ec 2500 epl_0.9-4.debian.tar.xz Files: 2540cb2804b3278de7d7a6545dea2f89 2018 lisp optional epl_0.9-4.dsc ee50389f85f30864b4564014b79a6fe7 2500 lisp optional epl_0.9-4.debian.tar.xz -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEm5FwB64DDjbk/CSLaVt65L8GYkAFAmElYusACgkQaVt65L8G YkAelQ//QgcZMSXRAfacZKdDBmnII9q3ongAakCoktUoqpdGz6CzXfHP2LZuIA3y wdtahsQdl7FOvTjKm4NssGdIDkMZqpP0wzVak/IZxiOZxMqSAYs/h1BbFp/0aBtK UEV8mVgJNdDvH98pK1HIxmnL0tXuMD2Y1TX28AVMxq4QpLB9qrNDjhjZnQY9/MRP 2ylQcLeBHQ/sRAHpxUIBBbWAfvZtBEno7T9x9Sn6Y5LH4QdW5yLDzzlQ3nd7hmSB 612XlmaIep0283+V9BcezYaqSTNZJbWNvDRc8x0xmg4+unvcoQoQ7U4rCMrdyDuI fxI891DNtKAPeBADAv1lclhpVK6hBEyC5dhv6nafEzmW+6M8smCRaB9odbN3Tnja zfhYe7yBUpEtJF0VNS/jUowpKLtOTqkK4dHI5x/lzA/ukzoKqTWsgKHbk4pQMlsL fFRRgVupk9EuOF1HC3UDhlSx1hx1AY4R38WefuvdbMHD6vGM5/UzhnnI0N70eiIh S4dZZKmCrQT1g7H+uvmT6xgH0tWPL5rmEFgn1Ui1I1DV5mT3d1YKaIDPPF4IX2Cv Fxt/jcOqOrejTiSrGSxiycVl9T4otQbfjvCJwyO0aYqQFtCxfBBf7YM/s+FUvcHK NO1wIUv5Gz60UooeAt1mzfj1ORWQfxga8dVj3tRlt+MW59k1ci0= =b6z8 -END PGP SIGNATURE End Message ---
Bug#992609: marked as done (rabbitmq-server fails to start after erlang v24 update)
Your message dated Tue, 24 Aug 2021 21:39:02 +
with message-id
and subject line Bug#992609: fixed in rabbitmq-server 3.9.4-1
has caused the Debian Bug report #992609,
regarding rabbitmq-server fails to start after erlang v24 update
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.)
--
992609: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=992609
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: rabbitmq-server
Version: 3.8.9-3
Severity: grave
Justification: renders package unusable
Dear Maintainer,
The rabbitmq-server to start after erlang v24 update with the followinr message:
{"Kernel pid terminated",application_controller,"{application_start_failure,
credentials_obfuscation,{{shutdown,{failed_to_start_child,
credentials_obfuscaton_svc,{undef,[{crypto,hmac,[sha512,<>,[<>,<<0,0,0,1>>],64],[]},
{credentials_obfuscation_pbe,xor_sum,7,[{file,\"src/credentials_obfuscation_pbe.erl\"},{line,276}]},
{credentials_obfuscation_pbe,blocks,10,[{file,\"src/credentials_obfuscation_pbe.erl\"},{line,268}]},
{credentials_obfuscation_pbe,make_key,5,[{file,\"src/credentials_obfuscation_pbe.erl\"},{line,125}]},
{credentials_obfuscation_pbe,encrypt,5,[{file,\"src/credentials_obfuscation_pbe.erl\"},{line,107}]},
{credentials_obfuscation_svc,check,3,[{file,\"src/credentials_obfuscation_svc.erl\"},{line,163}]},
{credentials_obfuscation_svc,init_state,0,[{file,\"src/credentials_obfuscation_svc.erl\"},{line,133}]},
{gen_server,init_it,2,[{file,\"gen_server.erl\"},{line,423}]}]}}},
{credentials_obfuscation_app,start,[normal,[]]}}}"}
It seems that rabbitmq-server required deoricated in erlang 22 and dropped in
erlang 24
functions from crypto module.
Since 27.08.2021 RabbitMQ 3.9.4 release is available that supports Erlang 24.
-- System Information:
Debian Release: 11.0
APT prefers unstable
APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 5.10.0-8-amd64 (SMP w/8 CPU threads)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE,
TAINT_UNSIGNED_MODULE
Locale: LANG=ru_RU.UTF-8, LC_CTYPE=ru_RU.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages rabbitmq-server depends on:
ii adduser 3.118
ii erlang-base 1:24.0.5+dfsg-2
ii erlang-crypto 1:24.0.5+dfsg-2
ii erlang-eldap 1:24.0.5+dfsg-2
ii erlang-inets 1:24.0.5+dfsg-2
ii erlang-mnesia 1:24.0.5+dfsg-2
ii erlang-os-mon 1:24.0.5+dfsg-2
ii erlang-parsetools 1:24.0.5+dfsg-2
ii erlang-public-key 1:24.0.5+dfsg-2
ii erlang-runtime-tools 1:24.0.5+dfsg-2
ii erlang-ssl1:24.0.5+dfsg-2
ii erlang-syntax-tools 1:24.0.5+dfsg-2
ii erlang-tools 1:24.0.5+dfsg-2
ii erlang-xmerl 1:24.0.5+dfsg-2
ii locales-all 2.31-16
ii logrotate 3.18.1-2
ii lsb-base 11.1.0
ii python3 3.9.2-3
ii socat 1.7.4.1-3
rabbitmq-server recommends no packages.
rabbitmq-server suggests no packages.
-- no debconf information
--- End Message ---
--- Begin Message ---
Source: rabbitmq-server
Source-Version: 3.9.4-1
Done: Thomas Goirand
We believe that the bug you reported is fixed in the latest version of
rabbitmq-server, 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 992...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Thomas Goirand (supplier of updated rabbitmq-server package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Sun, 22 Aug 2021 17:32:09 +0200
Source: rabbitmq-server
Architecture: source
Version: 3.9.4-1
Distribution: unstable
Urgency: medium
Maintainer: Debian OpenStack
Changed-By: Thomas Goirand
Closes: 992609
Changes:
rabbitmq-server (3.9.4-1) unstable; urgency=medium
.
* New upstream release:
- Works with Erlang 24 (Closes: #992609).
* Remove debian/patches/Upstream_PR2965_fixing_rabbitmqctl_parsing applied
upstream.
* Remove hunk from lets-use-python3-not-python-binary.patch as one upstream
Bug#992913: trickle: FTBFS due to RPC removal from glibc
Package: trickle Version: 1.07-10.1 Severity: serious Tags: patch ftbfs Justification: fails to build from source (but built successfully in the past) Dear maintainer, The glibc SunRPC implementation has been marked obsolete for some time. It has been removed upstream from glibc 2.32, and it got disabled in the recent glibc uploads. The TI RPC implementation should be used instead, which also brings new features (IPv6, Kerberos support, ...). For this reason trickle now fails to build from source. You will find attached a patch to switch to the TI RPC implementation, fixing the FTBFS. Regards, Aurelien diff -u trickle-1.07/Makefile.am trickle-1.07/Makefile.am --- trickle-1.07/Makefile.am +++ trickle-1.07/Makefile.am @@ -24,12 +24,12 @@ trickled_SOURCES = trickled.c atomicio.c print.c bwstat.c client.c conf.c \ util.c cleanup.c getopt.c xdr.c -trickled_LDADD = @EVENTLIB@ -lbsd +trickled_LDADD = @EVENTLIB@ @TIRPC_LIBS@ -lbsd tricklectl_SOURCES = tricklectl.c trickledu.c atomicio.c xdr.c -tricklectl_LDADD = @ERRO@ -lbsd +tricklectl_LDADD = @ERRO@ @TIRPC_LIBS@ -lbsd -AM_CFLAGS = -Wall -Icompat @EVENTINC@ +AM_CFLAGS = -Wall -Icompat @EVENTINC@ @TIRPC_CFLAGS@ overloaddir = $(libdir) #overload_DATA = libtrickle.so diff -u trickle-1.07/configure.in trickle-1.07/configure.in --- trickle-1.07/configure.in +++ trickle-1.07/configure.in @@ -119,6 +119,9 @@ AC_SUBST(EVENTINC) AC_SUBST(EVENTLIB) +dnl Checks for libtirpc +PKG_CHECK_MODULES(TIRPC, libtirpc) + dnl check if underscores are needed AC_MSG_CHECKING(if underscores are needed for symbols) AC_TRY_RUN( diff -u trickle-1.07/debian/control trickle-1.07/debian/control --- trickle-1.07/debian/control +++ trickle-1.07/debian/control @@ -3,7 +3,7 @@ Priority: optional Maintainer: Robert Lemmen Build-Depends: debhelper (>= 7.0.0), libevent-dev (>= 0.7b), autoconf, - libbsd-dev, dh-autoreconf + libbsd-dev, dh-autoreconf, pkg-config, libtirpc-dev Standards-Version: 3.9.4 Package: trickle
Bug#992908: awesome: autopkgtest regression between 20 and 23 August 2021: Could not resolve keysym
Hi Paul, On Tue, Aug 24, 2021 at 10:56:25PM +0200, Paul Gevers wrote: > Your package has an autopkgtest, great! However, since this week > (somewhere between 20 August and 23 August 2021) it started to fail [1]. > Can you look at it and fix the situation? [...] > [1] https://ci.debian.net/packages/a/awesome/testing/amd64/ > > autopkgtest [13:23:59]: test integration.sh: [--- > awesome_log: /tmp/tmp.Tu7TMRXwgL/_awesome_test.log > The XKEYBOARD keymap compiler (xkbcomp) reports: > > Internal error: Could not resolve keysym XF86BrightnessAuto [...] > > Internal error: Could not resolve keysym XF86KbdLcdMenu5 Thanks for the information. At a first glance this looks very similar to a test failure from last year, which was caused by Xorg-related packages, see #953032. The bug has already been re-opened, as someone else also noticed that this issue re-appeared. Below is a diff of installed packages between runs [2] and [3]. I will try to figure out what exactly is causing it. Kind regards, Reiner [2] https://ci.debian.net/data/autopkgtest/testing/amd64/a/awesome/14741180/log.gz [3] https://ci.debian.net/data/autopkgtest/testing/amd64/a/awesome/14793442/log.gz @@ -16,25 +16,21 @@ gcc-10 10.2.1-6 gcc 4:10.2.1-1 gir1.2-atk-1.0 2.36.0-2 -gir1.2-freedesktop 1.66.1-1+b1 +gir1.2-freedesktop 1.68.0-2 -gir1.2-gdkpixbuf-2.0 2.42.2+dfsg-1 +gir1.2-gdkpixbuf-2.0 2.42.6+dfsg-2 -gir1.2-glib-2.0 1.66.1-1+b1 +gir1.2-glib-2.0 1.68.0-2 -gir1.2-gtk-3.0 3.24.24-4 +gir1.2-gtk-3.0 3.24.30-1 gir1.2-harfbuzz-0.0 2.7.4-1 gir1.2-pango-1.0 1.46.2-3 -glib-networking 2.66.0-2 -glib-networking-common 2.66.0-2 -glib-networking-services 2.66.0-2 groff-base 1.22.4-6 -gsettings-desktop-schemas 3.38.0-2 -gtk-update-icon-cache 3.24.24-4 +gtk-update-icon-cache 3.24.30-1 hicolor-icon-theme 0.17-2 libasan6 10.2.1-6 libatk1.0-0 2.36.0-2 libatk1.0-data 2.36.0-2 libatk-bridge2.0-0 2.38.0-1 libatomic1 10.2.1-6 -libatspi2.0-0 2.38.0-4 +libatspi2.0-0 2.40.3-3 libavahi-client3 0.8-5 libavahi-common3 0.8-5 libavahi-common-data 0.8-5 @@ -49,22 +45,22 @@ libcups2 2.3.3op2-3+deb11u1 libdatrie1 0.2.13-1 libdconf1 0.38.0-2 -libdeflate0 1.7-1 +libdeflate0 1.7-2 libdrm2 2.4.104-1 libdrm-amdgpu1 2.4.104-1 libdrm-common 2.4.104-1 libdrm-intel1 2.4.104-1 libdrm-nouveau2 2.4.104-1 libdrm-radeon1 2.4.104-1 -libepoxy0 1.5.5-1 +libepoxy0 1.5.8-1 libfontconfig1 2.13.1-4.2 libfontenc1 1:1.1.4-1 libfreetype6 2.10.4+dfsg-1 libfribidi0 1.0.8-2 libgcc-10-dev 10.2.1-6 -libgdk-pixbuf-2.0-0 2.42.2+dfsg-1 +libgdk-pixbuf-2.0-0 2.42.6+dfsg-2 -libgdk-pixbuf2.0-common 2.42.2+dfsg-1 +libgdk-pixbuf2.0-common 2.42.6+dfsg-2 -libgirepository-1.0-1 1.66.1-1+b1 +libgirepository-1.0-1 1.68.0-2 libgl1 1.3.2-1 libgl1-mesa-dri 20.3.5-1 libglapi-mesa 20.3.5-1 @@ -74,8 +70,8 @@ libglx-mesa0 20.3.5-1 libgomp1 10.2.1-6 libgraphite2-3 1.3.14-1 -libgtk-3-0 3.24.24-4 +libgtk-3-0 3.24.30-1 -libgtk-3-common 3.24.24-4 +libgtk-3-common 3.24.30-1 libharfbuzz0b 2.7.4-1 libice6 2:1.0.10-1 libicu67 67.1-7 @@ -83,8 +79,6 @@ libitm1 10.2.1-6 libjbig0 2.1-3.1+b2 libjpeg62-turbo 1:2.0.6-4 -libjson-glib-1.0-0 1.6.2-1 -libjson-glib-1.0-common 1.6.2-1 liblcms2-2 2.12~rc1-2 libllvm11 1:11.0.1-2 liblsan0 10.2.1-6 @@ -100,22 +94,17 @@ libpipeline1 1.5.3-1 libpixman-1-0 0.40.0-1 libpng16-16 1.6.37-3 -libproxy1v5 0.4.17-1 -libpsl5 0.21.0-1.2 libpthread-stubs0-dev 0.4-1 libquadmath0 10.2.1-6 -librest-0.7-0 0.8.1-1.1 libsensors5 1:3.6.0-7 libsensors-config 1:3.6.0-7 libsm6 2:1.2.3-1 -libsoup2.4-1 2.72.0-4 -libsoup-gnome2.4-1 2.72.0-4 libstartup-notification0 0.12-6+b1 libstdc++-10-dev 10.2.1-6 -libthai0 0.1.28-3 +libthai0 0.1.28-4 -libthai-data 0.1.28-3 +libthai-data 0.1.28-4 libtiff5 4.2.0-1 -libtirpc-dev 1.3.1-1 +libtirpc-dev 1.3.2-2 libtsan0 10.2.1-6 libubsan1 10.2.1-6 libuchardet0 0.0.7-1 @@ -192,7 +181,7 @@ menu 2.1.48 shared-mime-info 2.0-1 x11-apps 7.7+8 -x11-common 1:7.7+22 +x11-common 1:7.7+23 x11proto-dev 2020.1-1 x11-utils 7.7+5 x11-xkb-utils 7.7+5 @@ -201,8 +190,8 @@ xfonts-base 1:1.0.5 xfonts-encodings 1:1.0.4-2.1 xfonts-utils 1:7.7+6 -xkb-data 2.29-2 +xkb-data 2.33-1 xorg-sgml-doctools 1:1.11-1.1 xserver-common 2:1.20.11-1 -xterm 366-1 +xterm 368-2 xvfb 2:1.20.11-1 signature.asc Description: PGP signature
Bug#992912: mat2: autopkgtests fail with ffmpeg 4.4
Source: mat2
Version: 0.12.1-3
Severity: serious
X-Debbugs-Cc: sramac...@debian.org
Tags: sid bookworm
=== FAILURES ===
___ TestCleaning.test_all_parametred ___
self =
def test_all_parametred(self):
for case in self.data:
if 'ffmpeg' in case:
try:
video._get_ffmpeg_path()
except RuntimeError:
raise unittest.SkipTest
print('[+] Testing %s' % case['name'])
target = './tests/data/clean.' + case['name']
shutil.copy('./tests/data/dirty.' + case['name'], target)
p1 = case['parser'](target)
for k, v in p1.get_meta().items():
if k not in case['meta']:
continue
if isinstance(v, dict):
for _k, _v in v.items():
if _k in case['meta'][k]:
self.assertEqual(_v, case['meta'][k][_k])
else:
self.assertEqual(v, case['meta'][k])
p1.lightweight_cleaning = True
self.assertTrue(p1.remove_all())
p2 = case['parser'](p1.output_filename)
for k, v in p2.get_meta().items():
> self.assertIn(k, case['expected_meta'])
E AssertionError: 'ColorRepresentation' not found in
{'CompatibleBrands': ['isom', 'iso2', 'avc1', 'mp41'], 'CompressorID': 'avc1',
'GraphicsMode': 'srcCopy', 'HandlerDescription': 'SoundHandler', 'HandlerType':
'Metadata', 'HandlerVendorID': 'Apple', 'MajorBrand': 'MP4 Base Media v1 [IS0
14496-12:2003]', 'MediaDataOffset': 48, 'MediaDataSize': 379872,
'MediaHeaderVersion': 0, 'MinorVersion': '0.2.0', 'MovieDataOffset': 48,
'MovieHeaderVersion': 0, 'NextTrackID': 3, 'PreferredRate': 1, 'Rotation': 0,
'TimeScale': 1000, 'TrackHeaderVersion': 0, 'TrackID': 1, 'TrackLayer': 0}
From
https://ci.debian.net/data/autopkgtest/testing/amd64/m/mat2/14794812/log.gz
Cheers
--
Sebastian Ramacher
signature.asc
Description: PGP signature
Bug#992911: rust-grep_0.2.8-1_amd64-buildd.changes REJECTED
Source: rust-grep Version: 0.2.8-1 Severity: serious On 2021-08-24 21:13, Debian FTP Masters wrote: > librust-grep-dev_0.2.8-1_amd64.deb: has 6 file(s) with a timestamp too far in > the past: > usr/share/cargo/registry/grep-0.2.8/COPYING (Thu Nov 29 21:33:09 1973) > usr/share/cargo/registry/grep-0.2.8/LICENSE-MIT (Thu Nov 29 21:33:09 1973) > usr/share/cargo/registry/grep-0.2.8/README.md (Thu Nov 29 21:33:09 1973) > usr/share/cargo/registry/grep-0.2.8/UNLICENSE (Thu Nov 29 21:33:09 1973) > usr/share/cargo/registry/grep-0.2.8/examples/simplegrep.rs (Thu Nov 29 > 21:33:09 1973) usr/share/cargo/registry/grep-0.2.8/src/lib.rs (Thu Nov 29 > 21:33:09 1973) > > > > === > > Please feel free to respond to this email if you don't understand why > your files were rejected, or if you upload new files which address our > concerns. > > >
Bug#989774: marked as done (ruby-pg-query: no longer works with ruby-google-protobuf)
Your message dated Tue, 24 Aug 2021 21:13:18 + with message-id and subject line Bug#989774: fixed in ruby-pg-query 2.0.3-3 has caused the Debian Bug report #989774, regarding ruby-pg-query: no longer works with ruby-google-protobuf 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.) -- 989774: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=989774 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: ruby-pg-query Version: 2.0.3-1 Severity: grave Control: affects -1 gitlab gitaly ruby-gitlab-labkit gitlab-sidekiq service fails to start when ruby-google-protobuf package is used, works with gem install -v 3.17.1 google-protobuf and removing ruby-google-protobuf Possibly the debian build is not ABI compatible with rubygems.org version and *_pb.rb needs to be regenerated. root@gitlab:/usr/share/gitlab# sudo -u gitlab /usr/bin/bundle exec sidekiq -C /etc/gitlab/sidekiq_queues.yml -e production fatal: not a git repository (or any of the parent directories): .git fatal: not a git repository (or any of the parent directories): .git Traceback (most recent call last): 31: from /usr/bin/sidekiq:23:in `' 30: from /usr/bin/sidekiq:23:in `load' 29: from /usr/share/rubygems-integration/all/gems/sidekiq-6.0.4/bin/sidekiq:12:in `' 28: from /usr/share/rubygems-integration/all/gems/sidekiq-6.0.4/lib/sidekiq/cli.rb:37:in `run' 27: from /usr/share/rubygems-integration/all/gems/sidekiq-6.0.4/lib/sidekiq/cli.rb:248:in `boot_system' 26: from /usr/share/rubygems-integration/all/gems/activesupport-6.0.3.6/lib/active_support/dependencies.rb:324:in `require' 25: from /usr/share/rubygems-integration/all/gems/activesupport-6.0.3.6/lib/active_support/dependencies.rb:291:in `load_dependency' 24: from /usr/share/rubygems-integration/all/gems/activesupport-6.0.3.6/lib/active_support/dependencies.rb:324:in `block in require' 23: from /usr/share/rubygems-integration/all/gems/activesupport-6.0.3.6/lib/active_support/dependencies.rb:324:in `require' 22: from /usr/share/gitlab/config/environment.rb:4:in `(required)>' 21: from /usr/share/rubygems-integration/all/gems/activesupport-6.0.3.6/lib/active_support/dependencies.rb:324:in `require' 20: from /usr/share/rubygems-integration/all/gems/activesupport-6.0.3.6/lib/active_support/dependencies.rb:291:in `load_dependency' 19: from /usr/share/rubygems-integration/all/gems/activesupport-6.0.3.6/lib/active_support/dependencies.rb:324:in `block in require' 18: from /usr/share/rubygems-integration/all/gems/activesupport-6.0.3.6/lib/active_support/dependencies.rb:324:in `require' 17: from /usr/share/gitlab/config/application.rb:15:in `(required)>' 16: from /usr/share/rubygems-integration/all/gems/bundler-2.2.5/lib/bundler.rb:173:in `require' 15: from /usr/share/rubygems-integration/all/gems/bundler-2.2.5/lib/bundler/runtime.rb:50:in `require' 14: from /usr/share/rubygems-integration/all/gems/bundler-2.2.5/lib/bundler/runtime.rb:50:in `each' 13: from /usr/share/rubygems-integration/all/gems/bundler-2.2.5/lib/bundler/runtime.rb:61:in `block in require' 12: from /usr/share/rubygems-integration/all/gems/bundler-2.2.5/lib/bundler/runtime.rb:61:in `each' 11: from /usr/share/rubygems-integration/all/gems/bundler-2.2.5/lib/bundler/runtime.rb:66:in `block (2 levels) in require' 10: from /usr/share/rubygems-integration/all/gems/bundler-2.2.5/lib/bundler/runtime.rb:66:in `require' 9: from /usr/lib/x86_64-linux-gnu/rubygems-integration/2.7.0/gems/pg_query-2.0.3/lib/pg_query.rb:4:in `' 8: from /usr/share/rubygems-integration/all/gems/activesupport-6.0.3.6/lib/active_support/dependencies.rb:324:in `require' 7: from /usr/share/rubygems-integration/all/gems/activesupport-6.0.3.6/lib/active_support/dependencies.rb:291:in `load_dependency' 6: from /usr/share/rubygems-integration/all/gems/activesupport-6.0.3.6/lib/active_support/dependencies.rb:324:in `block in require' 5: from /usr/share/rubygems-integration/all/gems/activesupport-6.0.3.6/lib/active_support/dependencies.rb:324:in `require' 4: from /usr/lib/x86_64-linux-gnu/rubygems-integration/2.7.0/gems/pg_query-2.0.3/lib/pg_query/pg_query_pb.rb:4:in `' 3: from /usr/share/rubygems-integration/all/gems/activesupport-6.0.3.6/lib/active_support/dependencies.rb:324:in `require' 2: from /usr/share/rubygems-integration/all/gems/activesupport-6.0.3.6/lib/active_support/dependencies.rb:291:in `load_dependency' 1: from /usr/share/rubygems-integration/all/gems/activesupport-6.0.3.6/lib/active_support/dependencies.rb:324:in `block in require' /usr/share/rubygems-integration/all/gems/ac
Processed: fwupd: binNMUs produce broken Built-Using for fwupd-*-signed
Processing control commands: > block 981078 by -1 Bug #981078 [release.debian.org] transition: libxmlb 981078 was not blocked by any bugs. 981078 was not blocking any bugs. Added blocking bug(s) of 981078: 992910 -- 981078: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=981078 992910: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=992910 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#992910: fwupd: binNMUs produce broken Built-Using for fwupd-*-signed
Source: fwupd Version: 1.5.7-4 Severity: serious Tags: sid bookworm Control: block 981078 by -1 X-Debbugs-Cc: sramac...@debian.org fwupd was recently binNMUed for the libxmlb transition. Builds of fwupd-*-signed for the binNMUs were rejeced by dak due to invalid Built-Using: fwupd-amd64-signed_1.5.7+4.b1_amd64.deb: Built-Using refers to non-existing source package fwupd (= 1.5.7-4+b1) fwupd-arm64-signed_1.5.7+4.b1_arm64.deb: Built-Using refers to non-existing source package fwupd (= 1.5.7-4+b1) fwupd-armhf-signed_1.5.7+4.b1_armhf.deb: Built-Using refers to non-existing source package fwupd (= 1.5.7-4+b1) fwupd-i386-signed_1.5.7+4.b1_i386.deb: Built-Using refers to non-existing source package fwupd (= 1.5.7-4+b1) Cheers -- Sebastian Ramacher signature.asc Description: PGP signature
Processed: Bug#992609 marked as pending in rabbitmq-server
Processing control commands: > tag -1 pending Bug #992609 [rabbitmq-server] rabbitmq-server fails to start after erlang v24 update Added tag(s) pending. -- 992609: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=992609 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#992609: marked as pending in rabbitmq-server
Control: tag -1 pending Hello, Bug #992609 in rabbitmq-server reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/openstack-team/third-party/rabbitmq-server/-/commit/b7c77808deb81aa6fa8c0d43299a8e05c7d16656 Now packaging 3.9.4: - Works with Erlang 24 (Closes: #992609). (this message was generated automatically) -- Greetings https://bugs.debian.org/992609
Bug#992908: awesome: autopkgtest regression between 20 and 23 August 2021: Could not resolve keysym
Source: awesome Version: 4.3-5 Severity: serious User: debian...@lists.debian.org Usertags: regression X-Debbugs-CC: debian...@lists.debian.org Dear maintainer, Your package has an autopkgtest, great! However, since this week (somewhere between 20 August and 23 August 2021) it started to fail [1]. Can you look at it and fix the situation? Paul [1] https://ci.debian.net/packages/a/awesome/testing/amd64/ autopkgtest [13:23:59]: test integration.sh: [--- awesome_log: /tmp/tmp.Tu7TMRXwgL/_awesome_test.log The XKEYBOARD keymap compiler (xkbcomp) reports: > Internal error: Could not resolve keysym XF86BrightnessAuto > Internal error: Could not resolve keysym XF86DisplayOff > Internal error: Could not resolve keysym XF86Info > Internal error: Could not resolve keysym XF86AspectRatio > Internal error: Could not resolve keysym XF86DVD > Internal error: Could not resolve keysym XF86Audio > Internal error: Could not resolve keysym XF86ChannelUp > Internal error: Could not resolve keysym XF86ChannelDown > Internal error: Could not resolve keysym XF86Break > Internal error: Could not resolve keysym XF86VideoPhone > Internal error: Could not resolve keysym XF86ZoomReset > Internal error: Could not resolve keysym XF86Editor > Internal error: Could not resolve keysym XF86GraphicsEditor > Internal error: Could not resolve keysym XF86Presentation > Internal error: Could not resolve keysym XF86Database > Internal error: Could not resolve keysym XF86Voicemail > Internal error: Could not resolve keysym XF86Addressbook > Internal error: Could not resolve keysym XF86DisplayToggle > Internal error: Could not resolve keysym XF86SpellCheck > Internal error: Could not resolve keysym XF86ContextMenu > Internal error: Could not resolve keysym XF86MediaRepeat > Internal error: Could not resolve keysym XF8610ChannelsUp > Internal error: Could not resolve keysym XF8610ChannelsDown > Internal error: Could not resolve keysym XF86Images > Internal error: Could not resolve keysym XF86NotificationCenter > Internal error: Could not resolve keysym XF86PickupPhone > Internal error: Could not resolve keysym XF86HangupPhone > Internal error: Could not resolve keysym XF86Fn > Internal error: Could not resolve keysym XF86Fn_Esc > Internal error: Could not resolve keysym XF86FnRightShift > Internal error: Could not resolve keysym XF86Numeric0 > Internal error: Could not resolve keysym XF86Numeric1 > Internal error: Could not resolve keysym XF86Numeric2 > Internal error: Could not resolve keysym XF86Numeric3 > Internal error: Could not resolve keysym XF86Numeric4 > Internal error: Could not resolve keysym XF86Numeric5 > Internal error: Could not resolve keysym XF86Numeric6 > Internal error: Could not resolve keysym XF86Numeric7 > Internal error: Could not resolve keysym XF86Numeric8 > Internal error: Could not resolve keysym XF86Numeric9 > Internal error: Could not resolve keysym XF86NumericStar > Internal error: Could not resolve keysym XF86NumericPound > Internal error: Could not resolve keysym XF86NumericA > Internal error: Could not resolve keysym XF86NumericB > Internal error: Could not resolve keysym XF86NumericC > Internal error: Could not resolve keysym XF86NumericD > Internal error: Could not resolve keysym XF86CameraFocus > Internal error: Could not resolve keysym XF86WPSButton > Internal error: Could not resolve keysym XF86CameraZoomIn > Internal error: Could not resolve keysym XF86CameraZoomOut > Internal error: Could not resolve keysym XF86CameraUp > Internal error: Could not resolve keysym XF86CameraDown > Internal error: Could not resolve keysym XF86CameraLeft > Internal error: Could not resolve keysym XF86CameraRight > Internal error: Could not resolve keysym XF86AttendantOn > Internal error: Could not resolve keysym XF86AttendantOff > Internal error: Could not resolve keysym XF86AttendantToggle > Internal error: Could not resolve keysym XF86LightsToggle > Internal error: Could not resolve keysym XF86ALSToggle > Internal error: Could not resolve keysym XF86Buttonconfig > Internal error: Could not resolve keysym XF86Taskmanager > Internal error: Could not resolve keysym XF86Journal > Internal error: Could not resolve keysym XF86ControlPanel > Internal error: Could not resolve keysym XF86AppSelect > Internal error: Could not resolve keysym XF86Screensaver > Internal error: Could not resolve keysym XF86VoiceCommand > Internal error: Could not resolve keysym XF86Assistant > Internal error: Could not resolve keysym XF86BrightnessMin > Internal error: Could not resolve keysym XF86BrightnessMax > Internal error: Could not resolve keysym XF86KbdInputAssistPrev > Internal error: Could not resolve keysym XF86KbdInputAssistNext > Internal error: Could not resolve keysym XF86KbdInputAssistPrevgroup > Internal error: Could not resolve keysym XF86KbdInputAssistNextgroup > Internal
Processed: king: contains a file with a non-free "disparaging to Sun" license
Processing control commands: > tag -1 confirmed Bug #992092 [king] king: contains a file with a non-free "disparaging to Sun" license Added tag(s) confirmed. -- 992092: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=992092 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#992092: king: contains a file with a non-free "disparaging to Sun" license
Control: tag -1 confirmed Hi, For the record, this text concerns 12 icons that are in king/resource/king/images. The problematic text is also in a file in this folder. I offer to create DFSG-free icons to replace those ones. Best, -- Pierre
Bug#978918: marked as done (vsearch: ftbfs with autoconf 2.70)
Your message dated Wed, 25 Aug 2021 01:31:49 +0530 with message-id and subject line Re: vsearch: ftbfs with autoconf 2.70 has caused the Debian Bug report #978918, regarding vsearch: ftbfs with autoconf 2.70 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.) -- 978918: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=978918 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:vsearch Version: 2.15.0-1 Severity: normal Tags: sid bookworm User: d...@debian.org Usertags: ftbfs-ac270 [This bug report is not targeted to the upcoming bullseye release] The package fails to build in a test rebuild on at least amd64 with autoconf 2.70, but succeeds to build with autoconf 2.69. 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://qa-logs.debian.net/2020/09/26.ac270/vsearch_2.15.0-1_unstable_ac270.log The last lines of the build log are at the end of this report. To build with autoconf 2.70, please install the autoconf package from experimental: apt-get -t=experimental install autoconf [...] /usr/lib/gcc/x86_64-linux-gnu/10/include/mm_malloc.h: In function ‘void* _mm_malloc(size_t, size_t)’: /usr/lib/gcc/x86_64-linux-gnu/10/include/mm_malloc.h:42:12: error: ‘malloc’ was not declared in this scope 42 | return malloc (__size); |^~ /usr/lib/gcc/x86_64-linux-gnu/10/include/mm_malloc.h:28:1: note: ‘malloc’ is defined in header ‘’; did you forget to ‘#include ’? 27 | #include +++ |+#include 28 | In file included from /usr/lib/gcc/x86_64-linux-gnu/10/include/xmmintrin.h:34, from /usr/lib/gcc/x86_64-linux-gnu/10/include/immintrin.h:29, from /usr/lib/gcc/x86_64-linux-gnu/10/include/x86intrin.h:32, from vsearch.h:103, from allpairs.cc:61: /usr/lib/gcc/x86_64-linux-gnu/10/include/mm_malloc.h: In function ‘void* _mm_malloc(size_t, size_t)’: /usr/lib/gcc/x86_64-linux-gnu/10/include/mm_malloc.h:42:12: error: ‘malloc’ was not declared in this scope 42 | return malloc (__size); |^~ In file included from /usr/lib/gcc/x86_64-linux-gnu/10/include/xmmintrin.h:34, from /usr/lib/gcc/x86_64-linux-gnu/10/include/immintrin.h:29, from /usr/lib/gcc/x86_64-linux-gnu/10/include/x86intrin.h:32, from vsearch.h:103, from align.cc:61: /usr/lib/gcc/x86_64-linux-gnu/10/include/mm_malloc.h: In function ‘void* _mm_malloc(size_t, size_t)’: /usr/lib/gcc/x86_64-linux-gnu/10/include/mm_malloc.h:42:12: error: ‘malloc’ was not declared in this scope 42 | return malloc (__size); |^~ /usr/lib/gcc/x86_64-linux-gnu/10/include/mm_malloc.h:28:1: note: ‘malloc’ is defined in header ‘’; did you forget to ‘#include ’? 27 | #include +++ |+#include 28 | /usr/lib/gcc/x86_64-linux-gnu/10/include/mm_malloc.h:28:1: note: ‘malloc’ is defined in header ‘’; did you forget to ‘#include ’? 27 | #include +++ |+#include 28 | In file included from /usr/lib/gcc/x86_64-linux-gnu/10/include/xmmintrin.h:34, from /usr/lib/gcc/x86_64-linux-gnu/10/include/immintrin.h:29, from /usr/lib/gcc/x86_64-linux-gnu/10/include/x86intrin.h:32, from vsearch.h:103, from align_simd.cc:61: /usr/lib/gcc/x86_64-linux-gnu/10/include/mm_malloc.h: In function ‘void* _mm_malloc(size_t, size_t)’: /usr/lib/gcc/x86_64-linux-gnu/10/include/mm_malloc.h:42:12: error: ‘malloc’ was not declared in this scope 42 | return malloc (__size); |^~ /usr/lib/gcc/x86_64-linux-gnu/10/include/mm_malloc.h:28:1: note: ‘malloc’ is defined in header ‘’; did you forget to ‘#include ’? 27 | #include +++ |+#include 28 | arch.cc: In function ‘void* xrealloc(void*, size_t)’: arch.cc:225:14: error: ‘realloc’ was not declared in this scope 225 | void * t = realloc(ptr, size); | ^~~ arch.cc:62:1: note: ‘realloc’ is defined in header ‘’; did you forget to ‘#include ’? 61 | #include "vsearch.h" +++ |+#include 62 | make[4]: *** [Makefile:729: arch.o] Error 1 make[4]: *** Waiting for unfinished jobs make[4]: *** [Makefile:729: align_simd.o] Error 1 make[4]: *** [Makefile:729: align.o] Error 1 make[4]: *** [Makefile:729: allpairs.o] Error 1 make[4]: Leaving directory '/<>/src' make[3]: *** [Makefile:374: all-recursive] Error 1 make[3]: Leaving directory '/<>' make[2]: *** [Makefile:315: all] E
Bug#978784: marked as done (clustalw: ftbfs with autoconf 2.70)
Your message dated Wed, 25 Aug 2021 01:23:54 +0530 with message-id and subject line Re: clustalw: ftbfs with autoconf 2.70 has caused the Debian Bug report #978784, regarding clustalw: ftbfs with autoconf 2.70 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.) -- 978784: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=978784 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:clustalw Version: 2.1+lgpl-6 Severity: normal Tags: sid bookworm User: d...@debian.org Usertags: ftbfs-ac270 [This bug report is not targeted to the upcoming bullseye release] The package fails to build in a test rebuild on at least amd64 with autoconf 2.70, but succeeds to build with autoconf 2.69. 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://qa-logs.debian.net/2020/09/26.ac270/clustalw_2.1+lgpl-6_unstable_ac270.log The last lines of the build log are at the end of this report. To build with autoconf 2.70, please install the autoconf package from experimental: apt-get -t=experimental install autoconf [...] | ^~ ./pairwise/../alignment/../substitutionMatrix/SubMatrix.h:97:66: warning: ISO C++ forbids converting a string constant to ‘char*’ [-Wwrite-strings] 97 | void printVectorToFile(vector& temp, char* name = "tempfile.out"); | ^~ In file included from ./pairwise/../alignment/../substitutionMatrix/globalmatrix.h:8, from ./pairwise/../alignment/Alignment.h:42, from ./pairwise/PairwiseAlignBase.h:10, from ./pairwise/FastPairwiseAlign.h:9, from ./pairwise/FastPairwiseAlign.cpp:10: ./pairwise/../alignment/../substitutionMatrix/SubMatrix.h:96:62: warning: ISO C++ forbids converting a string constant to ‘char*’ [-Wwrite-strings] 96 | void printInFormat(vector& temp, char* name = "tempfile.out"); | ^~ ./pairwise/../alignment/../substitutionMatrix/SubMatrix.h:97:66: warning: ISO C++ forbids converting a string constant to ‘char*’ [-Wwrite-strings] 97 | void printVectorToFile(vector& temp, char* name = "tempfile.out"); | ^~ In file included from ./fileInput/../alignment/../substitutionMatrix/globalmatrix.h:8, from ./fileInput/../alignment/Alignment.h:42, from ./fileInput/FileReader.h:12, from ./fileInput/FileReader.cpp:29: ./fileInput/../alignment/../substitutionMatrix/SubMatrix.h:96:62: warning: ISO C++ forbids converting a string constant to ‘char*’ [-Wwrite-strings] 96 | void printInFormat(vector& temp, char* name = "tempfile.out"); | ^~ ./fileInput/../alignment/../substitutionMatrix/SubMatrix.h:97:66: warning: ISO C++ forbids converting a string constant to ‘char*’ [-Wwrite-strings] 97 | void printVectorToFile(vector& temp, char* name = "tempfile.out"); | ^~ In file included from ./fileInput/FileReader.cpp:29: ./fileInput/FileReader.h:42:38: warning: ‘template class std::auto_ptr’ is deprecated [-Wdeprecated-declarations] 42 | void checkInfile(int* nseqs, auto_ptr& fileParser); | ^~~~ In file included from /usr/include/c++/10/memory:83, from ./fileInput/FileReader.h:11, from ./fileInput/FileReader.cpp:29: /usr/include/c++/10/bits/unique_ptr.h:57:28: note: declared here 57 | template class auto_ptr; |^~~~ ./fileInput/FileReader.cpp: In member function ‘int clustalw::FileReader::readSeqs(clustalw::Alignment*, int, std::string*)’: ./fileInput/FileReader.cpp:155:5: warning: ‘template class std::auto_ptr’ is deprecated [-Wdeprecated-declarations] 155 | auto_ptr fileParser; // Means we dont need to delete it! | ^~~~ In file included from /usr/include/c++/10/memory:83, from ./fileInput/FileReader.h:11, from ./fileInput/FileReader.cpp:29: /usr/include/c++/10/bits/unique_ptr.h:57:28: note: declared here 57 | template class auto_ptr;
Bug#978794: marked as done (crac: ftbfs with autoconf 2.70)
Your message dated Tue, 24 Aug 2021 21:46:25 +0200 with message-id <6aaf6800-e297-6546-0e31-d9581a268...@debian.org> and subject line Re: crac: ftbfs with autoconf 2.70 has caused the Debian Bug report #978794, regarding crac: ftbfs with autoconf 2.70 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.) -- 978794: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=978794 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:crac Version: 2.5.2+dfsg-2 Severity: normal Tags: sid bookworm User: d...@debian.org Usertags: ftbfs-ac270 [This bug report is not targeted to the upcoming bullseye release] The package fails to build in a test rebuild on at least amd64 with autoconf 2.70, but succeeds to build with autoconf 2.69. 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://qa-logs.debian.net/2020/09/26.ac270/crac_2.5.2+dfsg-2_unstable_ac270.log The last lines of the build log are at the end of this report. To build with autoconf 2.70, please install the autoconf package from experimental: apt-get -t=experimental install autoconf [...] /usr/include/x86_64-linux-gnu/bits/string_fortified.h:106:34: warning: ‘char* __builtin_strncpy(char*, const char*, long unsigned int)’ specified bound 2 equals destination size [-Wstringop-truncation] 106 | return __builtin___strncpy_chk (__dest, __src, __len, __bos (__dest)); | ^~ In function ‘char* strncpy(char*, const char*, size_t)’, inlined from ‘OptionalField::OptionalField(const char*, char)’ at samLine.cpp:60:10, inlined from ‘IntOptionalField::IntOptionalField(const char*, int)’ at samLine.cpp:117:34: /usr/include/x86_64-linux-gnu/bits/string_fortified.h:106:34: warning: ‘char* __builtin_strncpy(char*, const char*, long unsigned int)’ specified bound 2 equals destination size [-Wstringop-truncation] 106 | return __builtin___strncpy_chk (__dest, __src, __len, __bos (__dest)); | ^~ In function ‘char* strncpy(char*, const char*, size_t)’, inlined from ‘OptionalField::OptionalField(const char*, char)’ at samLine.cpp:60:10, inlined from ‘IntOptionalField::IntOptionalField(const char*, uint)’ at samLine.cpp:121:34: /usr/include/x86_64-linux-gnu/bits/string_fortified.h:106:34: warning: ‘char* __builtin_strncpy(char*, const char*, long unsigned int)’ specified bound 2 equals destination size [-Wstringop-truncation] 106 | return __builtin___strncpy_chk (__dest, __src, __len, __bos (__dest)); | ^~ In function ‘char* strncpy(char*, const char*, size_t)’, inlined from ‘OptionalField::OptionalField(const char*, char)’ at samLine.cpp:60:10, inlined from ‘StringOptionalField::StringOptionalField(const char*, std::string)’ at samLine.cpp:147:34: /usr/include/x86_64-linux-gnu/bits/string_fortified.h:106:34: warning: ‘char* __builtin_strncpy(char*, const char*, long unsigned int)’ specified bound 2 equals destination size [-Wstringop-truncation] 106 | return __builtin___strncpy_chk (__dest, __src, __len, __bos (__dest)); | ^~ In function ‘char* strncpy(char*, const char*, size_t)’, inlined from ‘OptionalField::OptionalField(const char*, char)’ at samLine.cpp:60:10, inlined from ‘StringOptionalField::StringOptionalField(const char*, char*)’ at samLine.cpp:150:34: /usr/include/x86_64-linux-gnu/bits/string_fortified.h:106:34: warning: ‘char* __builtin_strncpy(char*, const char*, long unsigned int)’ specified bound 2 equals destination size [-Wstringop-truncation] 106 | return __builtin___strncpy_chk (__dest, __src, __len, __bos (__dest)); | ^~ In function ‘char* strncpy(char*, const char*, size_t)’, inlined from ‘OptionalField::OptionalField(const char*, char)’ at samLine.cpp:60:10, inlined from ‘CharOptionalField::CharOptionalField(const char*, char)’ at samLine.cpp:91:34, inlined from ‘void SamLine::addOptionalField(const char*, char)’ at samLine.cpp:476:68: /usr/include/x86_64-linux-gnu/bits/string_fortified.h:106:34: warning: ‘char* __builtin_strncpy(char*, const char*, long unsigned int)’ specified bound 2 equals destination size [-Wstringop-truncation] 106 | return __builtin___strncpy_chk (
Bug#978794: crac: ftbfs with autoconf 2.70
On 8/24/21 9:36 PM, Nilesh Patra wrote: > control: tags -1 moreinfo > > Hi Matthias, > > I admit that I do not get any failures on build, same for several other > bugs, for instance #978784 > > I've triple-checked that my environment is updated, and I'm using > version 2.71-2 of autoconf > > Are these somehow false-positive in any case? > If so, will there be a re-build soonish? > > Please do let me know > Thanks a lot for your work! > > Nilesh > just close.
Bug#978885: marked as done (popt: ftbfs with autoconf 2.70)
Your message dated Tue, 24 Aug 2021 19:36:28 + with message-id and subject line Bug#978885: fixed in popt 1.18-3 has caused the Debian Bug report #978885, regarding popt: ftbfs with autoconf 2.70 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.) -- 978885: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=978885 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:popt Version: 1.18-1 Severity: normal Tags: sid bookworm User: d...@debian.org Usertags: ftbfs-ac270 [This bug report is not targeted to the upcoming bullseye release] The package fails to build in a test rebuild on at least amd64 with autoconf 2.70, but succeeds to build with autoconf 2.69. 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://qa-logs.debian.net/2020/09/26.ac270/popt_1.18-1_unstable_ac270.log The last lines of the build log are at the end of this report. To build with autoconf 2.70, please install the autoconf package from experimental: apt-get -t=experimental install autoconf [...] dpkg-buildpackage: info: source version 1.18-1 dpkg-buildpackage: info: source distribution unstable dpkg-buildpackage: info: source changed by Michael Jeanson dpkg-source --before-build . dpkg-buildpackage: info: host architecture amd64 debian/rules clean dh clean --with autoreconf dh_clean dpkg-source -b . dpkg-source: info: using source format '3.0 (quilt)' dpkg-source: info: building popt using existing ./popt_1.18.orig.tar.gz dpkg-source: info: using patch list from debian/patches/series dpkg-source: info: building popt in popt_1.18-1.debian.tar.xz dpkg-source: info: building popt in popt_1.18-1.dsc debian/rules binary dh binary --with autoreconf dh_update_autotools_config dh_autoreconf autopoint: using AM_GNU_GETTEXT_REQUIRE_VERSION instead of AM_GNU_GETTEXT_VERSION Copying file ABOUT-NLS Copying file build-aux/config.rpath Copying file m4/codeset.m4 Copying file m4/extern-inline.m4 Copying file m4/fcntl-o.m4 Copying file m4/gettext.m4 Copying file m4/glibc2.m4 Copying file m4/glibc21.m4 Copying file m4/iconv.m4 Copying file m4/intdiv0.m4 Copying file m4/intl.m4 Copying file m4/intldir.m4 Copying file m4/intmax.m4 Copying file m4/inttypes-pri.m4 Copying file m4/inttypes_h.m4 Copying file m4/lcmessage.m4 Copying file m4/lock.m4 Copying file m4/longlong.m4 Copying file m4/po.m4 Copying file m4/printf-posix.m4 Copying file m4/size_max.m4 Copying file m4/stdint_h.m4 Copying file m4/threadlib.m4 Copying file m4/uintmax_t.m4 Copying file m4/visibility.m4 Copying file m4/wchar_t.m4 Copying file m4/wint_t.m4 Copying file m4/xsize.m4 Copying file po/Makefile.in.in Copying file po/Makevars.template Copying file po/Rules-quot configure.ac:11: warning: The macro `AC_PROG_CC_STDC' is obsolete. configure.ac:11: You should run autoupdate. ./lib/autoconf/c.m4:1483: AC_PROG_CC_STDC is expanded from... configure.ac:11: the top level configure.ac:35: warning: The macro `AC_HELP_STRING' is obsolete. configure.ac:35: You should run autoupdate. ./lib/autoconf/general.m4:203: AC_HELP_STRING is expanded from... configure.ac:35: the top level configure.ac:11: warning: The macro `AC_PROG_CC_STDC' is obsolete. configure.ac:11: You should run autoupdate. ./lib/autoconf/c.m4:1483: AC_PROG_CC_STDC is expanded from... configure.ac:11: the top level configure.ac:35: warning: The macro `AC_HELP_STRING' is obsolete. configure.ac:35: You should run autoupdate. ./lib/autoconf/general.m4:203: AC_HELP_STRING is expanded from... configure.ac:35: the top level Use of uninitialized value $args[0] in split at /usr/bin/autoreconf line 441, line 7. dh_autoreconf: error: autoreconf -f -i returned exit code 29 make: *** [debian/rules:9: binary] Error 25 dpkg-buildpackage: error: debian/rules binary subprocess returned exit status 2 --- End Message --- --- Begin Message --- Source: popt Source-Version: 1.18-3 Done: Michael Jeanson We believe that the bug you reported is fixed in the latest version of popt, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 978...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Michael Jeanson (supplier of updated popt package) (This message was generated automatically at their request; if you believe that there is a pro
Processed: Re: crac: ftbfs with autoconf 2.70
Processing control commands: > tags -1 moreinfo Bug #978794 [src:crac] crac: ftbfs with autoconf 2.70 Added tag(s) moreinfo. -- 978794: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=978794 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#978794: crac: ftbfs with autoconf 2.70
control: tags -1 moreinfo Hi Matthias, I admit that I do not get any failures on build, same for several other bugs, for instance #978784 I've triple-checked that my environment is updated, and I'm using version 2.71-2 of autoconf Are these somehow false-positive in any case? If so, will there be a re-build soonish? Please do let me know Thanks a lot for your work! Nilesh signature.asc Description: PGP signature
Processed: fix bug title
Processing commands for cont...@bugs.debian.org: > retitle 992898 debian-parl build-depends on obsolete version of boxer-data Bug #992898 [debian-parl] debian-design build-depends on obsolete version of boxer-data Changed Bug title to 'debian-parl build-depends on obsolete version of boxer-data' from 'debian-design build-depends on obsolete version of boxer-data'. > thanks Stopping processing here. Please contact me if you need assistance. -- 992898: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=992898 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#992905: src:perceptualdiff: fails to migrate to testing for too long due to ftbfs
Source: perceptualdiff Version: 1.2-2 Severity: serious Tags: sid bookworm User: release.debian@packages.debian.org Usertags: out-of-sync Dear maintainer(s), As recently announced [1], the Release Team now considers packages that are out-of-sync between testing and unstable for more than 60 days as having a Release Critical bug in testing. Your package src:perceptualdiff has been trying to migrate for 224 days [2] (yes, I know, big part during the freeze). Hence, I am filing this bug. If a package is out of sync between unstable and testing for a longer period, this usually means that bugs in the package in testing cannot be fixed via unstable. Additionally, blocked packages can have impact on other packages, which makes preparing for the release more difficult. Finally, it often exposes issues with the package and/or its (reverse-)dependencies. We expect maintainers to fix issues that hamper the migration of their package in a timely manner. This bug will trigger auto-removal when appropriate. As with all new bugs, there will be at least 30 days before the package is auto-removed. I have tagged this bug to only affect sid and bookworm, so it doesn't affect (old-)stable. If you believe your package is unable to migrate to testing due to issues beyond your control, don't hesitate to contact the Release Team. Paul [1] https://lists.debian.org/debian-devel-announce/2020/02/msg5.html [2] https://qa.debian.org/excuses.php?package=perceptualdiff OpenPGP_signature Description: OpenPGP digital signature
Processed: Re: src:perceptualdiff: fails to migrate to testing for too long due to ftbfs on armel
Processing control commands: > reassign -1 src:geary 3.38.1-1 Bug #992901 [src:perceptualdiff] src:perceptualdiff: fails to migrate to testing for too long due to ftbfs on armel Bug reassigned from package 'src:perceptualdiff' to 'src:geary'. No longer marked as found in versions perceptualdiff/1.2-2. Ignoring request to alter fixed versions of bug #992901 to the same values previously set Bug #992901 [src:geary] src:perceptualdiff: fails to migrate to testing for too long due to ftbfs on armel Marked as found in versions geary/3.38.1-1. -- 992901: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=992901 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#992901: src:perceptualdiff: fails to migrate to testing for too long due to ftbfs on armel
Control: reassign -1 src:geary 3.38.1-1 Oops, I mixed two submissions. This text should have gone to geary (the one for perceptualdiff will follow shortly). Paul On Tue, 24 Aug 2021 21:22:16 +0200 Paul Gevers wrote: > Source: perceptualdiff > Version: 1.2-2 > Severity: serious > Tags: sid bookworm ftbfs > User: release.debian@packages.debian.org > Usertags: out-of-sync > > Dear maintainer(s), > > As recently announced [1], the Release Team now considers packages that > are out-of-sync between testing and unstable for more than 60 days as > having a Release Critical bug in testing. Your package > src:perceptualdiff has been trying to migrate for 224 days [2] (yes, I > know, mostly during the freeze). Hence, I am filing this bug. > > If a package is out of sync between unstable and testing for a longer > period, this usually means that bugs in the package in testing cannot be > fixed via unstable. Additionally, blocked packages can have impact on > other packages, which makes preparing for the release more difficult. > Finally, it often exposes issues with the package and/or > its (reverse-)dependencies. We expect maintainers to fix issues that > hamper the migration of their package in a timely manner. > > Your package fails to build on armel [3]: > Summary of Failures: > > 7/7 geary / client-tests FAIL 33.45s > (killed by signal 11 SIGSEGV) > > Ok: 6 > Expected Fail: 0 > Fail: 1 > Unexpected Pass:0 > Skipped:0 > Timeout:0 > dh_auto_test: error: cd obj-arm-linux-gnueabi && LC_ALL=C.UTF-8 > MESON_TESTTHREADS=4 meson test returned exit code 1 > xvfb-run: error: problem while cleaning up temporary directory > make[1]: *** [debian/rules:28: override_dh_auto_test] Error 5 > make[1]: Leaving directory '/<>' > make: *** [debian/rules:21: binary-arch] Error 2 > > This bug will trigger auto-removal when appropriate. As with all new > bugs, there will be at least 30 days before the package is auto-removed. > > I have tagged this bug to only affect sid and bookworm, so it doesn't > affect (old-)stable. > > If you believe your package is unable to migrate to testing due to > issues beyond your control, don't hesitate to contact the Release Team. > > Paul > > [1] https://lists.debian.org/debian-devel-announce/2020/02/msg5.html > [2] https://qa.debian.org/excuses.php?package=perceptualdiff > [3] > https://buildd.debian.org/status/fetch.php?pkg=geary&arch=armel&ver=3.38.2-1&stamp=1626009864&raw=0 > OpenPGP_signature Description: OpenPGP digital signature
Bug#992904: shut-up build-depends on removed transitional package.
Source: shut-up Version: 0.3.3-1 Severity: serious Tags: bookworm, sid shut-up build-depends on the s-el binary package which has been dropped by the s-el source package. It is still present in unstable as a cruft package but is completely gone from testing. Since this package was previously an empty transitional package it should be possible to simply update the dependency.
Bug#992903: node-matrix-js-sdk build-depends on removed virtual package node-olm
Package: node-matrix-js-sdk Version: 9.3.0+~cs9.9.16-2 Severity: serious Tags: bookworm, sid node-matrix-js-sdk build-depends on node-olm, afaict this was previously a virtual package provided by libjs-olm but is no longer provided. From reading the changelog it looks like the replacement virtual package is node-matrix-olm but that some adjustments may be needed. * update Node.js install path, and have libjs-olm provide node-matrix-org-olm (not node-olm)
Bug#992849: marked as done (gnutls28 arch-only FTBFS: Can't exec "gtkdocize": No such file or directory at /usr/share/autoconf/Autom4te/FileUtils.pm line 293.)
Your message dated Tue, 24 Aug 2021 19:15:16 +
with message-id
and subject line Bug#992849: fixed in gnutls28 3.7.2-2
has caused the Debian Bug report #992849,
regarding gnutls28 arch-only FTBFS: Can't exec "gtkdocize": No such file or
directory at /usr/share/autoconf/Autom4te/FileUtils.pm line 293.
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.)
--
992849: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=992849
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: gnutls28
Version: 3.7.1-5
Severity: serious
Tags: ftbfs
User: helm...@debian.org
Usertags: rebootstrap
gnutls28 fails to build from source when performing an arch-only build.
A build ends with:
| dh binary-arch --builddirectory=b4deb
|dh_update_autotools_config -a -O--builddirectory=b4deb
|debian/rules override_dh_autoreconf
| make[1]: Entering directory '/<>'
| rm -v `grep -rl gettext-0.20 m4/`
| removed 'm4/po.m4'
| removed 'm4/intlmacosx.m4'
| removed 'm4/gettext.m4'
| dh_autoreconf --verbose -O--builddirectory=b4deb
| find ! -ipath "./debian/*" -a ! \( -path '*/.git/*' -o -path
'*/.hg/*' -o -path '*/.bzr/*' -o -path '*/.svn/*' -o -path '*/CVS/*' \) -a
-type f -exec md5sum {} + -o -type l -printf "symlink %p
| " > debian/autoreconf.before
| grep -q ^XDT_ configure.ac
| autoreconf -f -i
| autopoint: using AM_GNU_GETTEXT_REQUIRE_VERSION instead of
AM_GNU_GETTEXT_VERSION
| Copying file m4/gettext.m4
| Copying file m4/intlmacosx.m4
| Copying file m4/nls.m4
| Copying file m4/po.m4
| Copying file m4/progtest.m4
| Copying file po/Makefile.in.in
| Copying file po/Makevars.template
| aclocal: overwriting 'm4/pkg.m4' with '/usr/share/aclocal/pkg.m4'
| libtoolize: putting auxiliary files in AC_CONFIG_AUX_DIR, 'build-aux'.
| libtoolize: copying file 'build-aux/ltmain.sh'
| libtoolize: putting macros in AC_CONFIG_MACRO_DIRS, 'm4'.
| libtoolize: copying file 'm4/libtool.m4'
| libtoolize: copying file 'm4/ltoptions.m4'
| libtoolize: copying file 'm4/ltsugar.m4'
| libtoolize: copying file 'm4/ltversion.m4'
| libtoolize: copying file 'm4/lt~obsolete.m4'
| Can't exec "gtkdocize": No such file or directory at
/usr/share/autoconf/Autom4te/FileUtils.pm line 293.
| autoreconf: error: gtkdocize failed with exit status: 2
| find ! -ipath "./debian/*" -a ! \( -path '*/.git/*' -o -path
'*/.hg/*' -o -path '*/.bzr/*' -o -path '*/.svn/*' -o -path '*/CVS/*' \) -a
-type f -exec md5sum {} + -o -type l -printf "symlink %p
| " > debian/autoreconf.after
| dh_autoreconf: error: autoreconf -f -i returned exit code 2
| make[1]: *** [debian/rules:50: override_dh_autoreconf] Error 25
| make[1]: Leaving directory '/<>'
| make: *** [debian/rules:127: binary-arch] Error 2
| dpkg-buildpackage: error: debian/rules binary-arch subprocess returned exit
status 2
A full build does not run into this issue, because gtk-doc-tools is
included in Build-Depends-Indep. I suppose it'll have to be moved to
Build-Depends.
This presently breaks architecture bootstrap.
Helmut
--- End Message ---
--- Begin Message ---
Source: gnutls28
Source-Version: 3.7.2-2
Done: Andreas Metzler
We believe that the bug you reported is fixed in the latest version of
gnutls28, 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 992...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Andreas Metzler (supplier of updated gnutls28 package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Tue, 24 Aug 2021 19:46:02 +0200
Source: gnutls28
Architecture: source
Version: 3.7.2-2
Distribution: unstable
Urgency: low
Maintainer: Debian GnuTLS Maintainers
Changed-By: Andreas Metzler
Closes: 992849
Changes:
gnutls28 (3.7.2-2) unstable; urgency=low
.
* Invoke dh_autoreconf with GTKDOCIZE=echo for arch-only builds, fixing
FTBFS. Closes: #992849
* Upload to unstable.
Checksums-Sha1:
538b1e1b4c233c6c59f3f629f099a6e895f1fb8c 3487 gnutls28_3.7.2-2.dsc
c6c5235df0c6730103441d505ae778d68fc733da 65144 gnutls28_3.7.2-2.debian.tar.xz
Checksums-Sha256:
f2c1cfd399a5631133f37590d470929ba0344c94ae30ae89c4673711613409d7 3487
gnutls28_3.7.2-2.dsc
900fdef4138494346a4e5
Bug#992447: marked as done (php-oscarotero-gettext build depends on the removed php-twig-extensions)
Your message dated Tue, 24 Aug 2021 19:18:51 + with message-id and subject line Bug#992447: fixed in php-oscarotero-gettext 4.8.2-5 has caused the Debian Bug report #992447, regarding php-oscarotero-gettext build depends on the removed php-twig-extensions 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.) -- 992447: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=992447 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: php-oscarotero-gettext Version: 4.8.2-4 Severity: serious Tags: ftbfs The following packages have unmet dependencies: builddeps:php-oscarotero-gettext : Depends: php-twig-extensions but it is not installable --- End Message --- --- Begin Message --- Source: php-oscarotero-gettext Source-Version: 4.8.2-5 Done: James Valleroy We believe that the bug you reported is fixed in the latest version of php-oscarotero-gettext, 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 992...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. James Valleroy (supplier of updated php-oscarotero-gettext package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Tue, 24 Aug 2021 14:24:18 -0400 Source: php-oscarotero-gettext Architecture: source Version: 4.8.2-5 Distribution: unstable Urgency: medium Maintainer: Debian PHP PEAR Maintainers Changed-By: James Valleroy Closes: 992447 Changes: php-oscarotero-gettext (4.8.2-5) unstable; urgency=medium . * Patch out Twig support * Remove twig dependencies (Closes: #992447) Checksums-Sha1: 852de30abbca0117815fe9b8443033a4fa8249dc 2303 php-oscarotero-gettext_4.8.2-5.dsc 671a365e95c791591a6ec782d948900895fbed0c 7940 php-oscarotero-gettext_4.8.2-5.debian.tar.xz 4d4f6bf8c0eec82973d8da511fae2671efbdcefc 8440 php-oscarotero-gettext_4.8.2-5_amd64.buildinfo Checksums-Sha256: 73cc3a6398f13db3b8a8c0566d7783b6ff4b3f5d0a9f3f369818dca4e5af10b1 2303 php-oscarotero-gettext_4.8.2-5.dsc 6a5c48991427b85c4a58aaa51f97a78e017c4888ce04b8e29c611ccaddaf88b0 7940 php-oscarotero-gettext_4.8.2-5.debian.tar.xz d1d1ceca702b6718eecb7516de68dbd8bb9813295c2751d8bd4914799099ffd8 8440 php-oscarotero-gettext_4.8.2-5_amd64.buildinfo Files: 3e454c14dcdcac9344b04b4643238fdd 2303 php optional php-oscarotero-gettext_4.8.2-5.dsc 4a06c78c9b7e17e5c8f8deaebbd97fbd 7940 php optional php-oscarotero-gettext_4.8.2-5.debian.tar.xz 0a0b31cd26cc22e3509134f7d3e5dcef 8440 php optional php-oscarotero-gettext_4.8.2-5_amd64.buildinfo -BEGIN PGP SIGNATURE- iQJKBAEBCgA0FiEEfWrbdQ+RCFWJSEvmd8DHXntlCAgFAmElOfIWHGp2YWxsZXJv eUBtYWlsYm94Lm9yZwAKCRB3wMdee2UICCPzEACiRvnqHTMfXO5VduFyCGnPkC9X njxP528wYbsKHi5f2auI32aGodBpRxHEB2pq8PBBPVG3JfaBmTBHeKP0SNFWFr3j lpzhM02Fvy4hmuhrOBHIjkQI9Qyh5+ux7Zpe06GWwVDRk0KsGkGqwyf7RTujcJ+e rG6yeq5n+OuQwmFJcu8Dpb8g64CqnDFNAcx1MFGnPEZ6xTJ5br26Ob6h833OyatS jfILjumR0nYV5yCd/luXhuwR9IThSioPofV/9rdQ7B7bIKkd11qGEPFHN9ehBZXF 8LEKRVM0XBVVMbsAvNJekzgZQpX+9oJuIlrJixvILorHBHCK3txGx0QXym6J/x3n PnTMOjhGlRXK7IECzsuSvGMRYmnoGt0f0bRLiOZEM1c+jCodOczQWjlsTNG+rbM2 8n0vT4CoDQgRtdaRtSkK4+UqKBLlj9iKJSzn5c4q2W9Ai1KzY4YlxvJQQBX8jL8w uzND+8+XrvuJThEaicEU08cwQNoByzYXpwB+gHkCdeCK4zSTw9C1ycmi6rkZvCi0 0kBf7lN1jMCbB7cgzXS6bnsDxnvLNe2ujzju2YYR6c0Tdqc0hk6M1BcW4ARTBX01 Mta78VvFCMzL1pSMzj/s6b0R6+qSXLZRcEW94nNHNzHb+UMNAEL/QsaJ0MNTRUHU pbWGyI03jk/AynibHQ== =mK9B -END PGP SIGNATURE End Message ---
Bug#978877: marked as done (pdfresurrect: ftbfs with autoconf 2.70)
Your message dated Tue, 24 Aug 2021 12:15:26 -0700
with message-id
and subject line
has caused the Debian Bug report #978877,
regarding pdfresurrect: ftbfs with autoconf 2.70
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.)
--
978877: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=978877
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:pdfresurrect
Version: 0.21-1
Severity: normal
Tags: sid bookworm
User: d...@debian.org
Usertags: ftbfs-ac270
[This bug report is not targeted to the upcoming bullseye release]
The package fails to build in a test rebuild on at least amd64 with
autoconf 2.70, but succeeds to build with autoconf 2.69. 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://qa-logs.debian.net/2020/09/26.ac270/pdfresurrect_0.21-1_unstable_ac270.log
The last lines of the build log are at the end of this report.
To build with autoconf 2.70, please install the autoconf package from
experimental: apt-get -t=experimental install autoconf
[...]
PACKAGE_URL=''
PACKAGE_VERSION=''
PATH_SEPARATOR=':'
SHELL='/bin/bash'
ac_ct_CC='gcc'
bindir='${exec_prefix}/bin'
build='x86_64-linux-gnu'
build_alias='x86_64-linux-gnu'
build_cpu=''
build_os=''
build_vendor=''
datadir='${datarootdir}'
datarootdir='${prefix}/share'
docdir='${datarootdir}/doc/${PACKAGE}'
dvidir='${docdir}'
exec_prefix='NONE'
host=''
host_alias=''
host_cpu=''
host_os=''
host_vendor=''
htmldir='${docdir}'
includedir='${prefix}/include'
infodir='${prefix}/share/info'
libdir='${prefix}/lib/x86_64-linux-gnu'
libexecdir='${exec_prefix}/libexec'
localedir='${datarootdir}/locale'
localstatedir='/var'
mandir='${prefix}/share/man'
oldincludedir='/usr/include'
pdfdir='${docdir}'
prefix='/usr'
program_transform_name='s,x,x,'
psdir='${docdir}'
runstatedir='/run'
sbindir='${exec_prefix}/sbin'
sharedstatedir='${prefix}/com'
sysconfdir='/etc'
target_alias=''
## --- ##
## confdefs.h. ##
## --- ##
/* confdefs.h */
#define PACKAGE_NAME ""
#define PACKAGE_TARNAME ""
#define PACKAGE_VERSION ""
#define PACKAGE_STRING ""
#define PACKAGE_BUGREPORT ""
#define PACKAGE_URL ""
#define HAVE_DIRENT_H 1
#define HAVE_SYS_TYPES_H 1
#define HAVE_SYS_STAT_H 1
#define HAVE_STRINGS_H 1
#define HAVE_INTTYPES_H 1
#define HAVE_STDINT_H 1
#define HAVE_UNISTD_H 1
#define HAVE_STDLIB_H 1
#define HAVE_STRING_H 1
#define STDC_HEADERS 1
#define HAVE_STDLIB_H 1
#define HAVE_STRING_H 1
#define HAVE_STRDUP 1
#define HAVE_STRTOL 1
configure: exit 1
dh_auto_configure: error: ./configure --build=x86_64-linux-gnu --prefix=/usr
--includedir=\${prefix}/include --mandir=\${prefix}/share/man
--infodir=\${prefix}/share/info --sysconfdir=/etc --localstatedir=/var
--disable-option-checking --disable-silent-rules
--libdir=\${prefix}/lib/x86_64-linux-gnu --runstatedir=/run
--disable-maintainer-mode --disable-dependency-tracking returned exit code 1
make: *** [debian/rules:7: binary] Error 25
dpkg-buildpackage: error: debian/rules binary subprocess returned exit status 2
--- End Message ---
--- Begin Message ---
Version: 0.22-1
This appears to be working fine as of 0.22-1.
Neither myself nor upstream are able to reproduce the problem.
Francois
--
https://fmarier.org/--- End Message ---
Bug#992901: src:perceptualdiff: fails to migrate to testing for too long due to ftbfs on armel
Source: perceptualdiff Version: 1.2-2 Severity: serious Tags: sid bookworm ftbfs User: release.debian@packages.debian.org Usertags: out-of-sync Dear maintainer(s), As recently announced [1], the Release Team now considers packages that are out-of-sync between testing and unstable for more than 60 days as having a Release Critical bug in testing. Your package src:perceptualdiff has been trying to migrate for 224 days [2] (yes, I know, mostly during the freeze). Hence, I am filing this bug. If a package is out of sync between unstable and testing for a longer period, this usually means that bugs in the package in testing cannot be fixed via unstable. Additionally, blocked packages can have impact on other packages, which makes preparing for the release more difficult. Finally, it often exposes issues with the package and/or its (reverse-)dependencies. We expect maintainers to fix issues that hamper the migration of their package in a timely manner. Your package fails to build on armel [3]: Summary of Failures: 7/7 geary / client-tests FAIL 33.45s (killed by signal 11 SIGSEGV) Ok: 6 Expected Fail: 0 Fail: 1 Unexpected Pass:0 Skipped:0 Timeout:0 dh_auto_test: error: cd obj-arm-linux-gnueabi && LC_ALL=C.UTF-8 MESON_TESTTHREADS=4 meson test returned exit code 1 xvfb-run: error: problem while cleaning up temporary directory make[1]: *** [debian/rules:28: override_dh_auto_test] Error 5 make[1]: Leaving directory '/<>' make: *** [debian/rules:21: binary-arch] Error 2 This bug will trigger auto-removal when appropriate. As with all new bugs, there will be at least 30 days before the package is auto-removed. I have tagged this bug to only affect sid and bookworm, so it doesn't affect (old-)stable. If you believe your package is unable to migrate to testing due to issues beyond your control, don't hesitate to contact the Release Team. Paul [1] https://lists.debian.org/debian-devel-announce/2020/02/msg5.html [2] https://qa.debian.org/excuses.php?package=perceptualdiff [3] https://buildd.debian.org/status/fetch.php?pkg=geary&arch=armel&ver=3.38.2-1&stamp=1626009864&raw=0 OpenPGP_signature Description: OpenPGP digital signature
Bug#992902: lizzie build-depends on removed package
package: lizzie version: 0.7.4+dfsg1-2 severity: serious lizzie build-depends on libjuniversalchardet-java-doc which is no longer built by the libjuniversalchardet-java source package. It is still present in unstable as a cruft package but is completely gone from testing.
Bug#992900: epl build-depends on removed transitional package.
Source: epl Version: 0.9-3 Severity: serious Tags: bookworm, sid epl build-depends on the s-el binary package which has been dropped by the s-el source package. It is still present in unstable as a cruft package but is completely gone from testing. Since this package was previously an empty transitional package it should be possible to simply update the dependency.
Processed: src:dub: fails to migrate to testing for too long
Processing control commands: > close -1 1.24.0-1 Bug #992899 [src:dub] src:dub: fails to migrate to testing for too long Marked as fixed in versions dub/1.24.0-1. Bug #992899 [src:dub] src:dub: fails to migrate to testing for too long Marked Bug as done -- 992899: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=992899 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#992899: src:dub: fails to migrate to testing for too long
Source: dub Version: 1.22.0-1 Severity: serious Control: close -1 1.24.0-1 Tags: sid bookworm User: release.debian@packages.debian.org Usertags: out-of-sync Dear maintainer(s), As recently announced [1], the Release Team now considers packages that are out-of-sync between testing and unstable for more than 60 days as having a Release Critical bug in testing. Your package src:dub has been trying to migrate for 209 days [2] (yes, I know, mostly during the freeze). Hence, I am filing this bug. If a package is out of sync between unstable and testing for a longer period, this usually means that bugs in the package in testing cannot be fixed via unstable. Additionally, blocked packages can have impact on other packages, which makes preparing for the release more difficult. Finally, it often exposes issues with the package and/or its (reverse-)dependencies. We expect maintainers to fix issues that hamper the migration of their package in a timely manner. This bug will trigger auto-removal when appropriate. As with all new bugs, there will be at least 30 days before the package is auto-removed. I have immediately closed this bug with the version in unstable, so if that version or a later version migrates, this bug will no longer affect testing. I have also tagged this bug to only affect sid and bookworm, so it doesn't affect (old-)stable. If you believe your package is unable to migrate to testing due to issues beyond your control, don't hesitate to contact the Release Team. Paul [1] https://lists.debian.org/debian-devel-announce/2020/02/msg5.html [2] https://qa.debian.org/excuses.php?package=dub OpenPGP_signature Description: OpenPGP digital signature
Bug#983793: marked as done (grc needs a source-only upload for testing migration)
Your message dated Tue, 24 Aug 2021 21:15:19 +0200 with message-id <1bd8273f-f045-f736-353d-a92499b9f...@debian.org> and subject line Re: grc needs a source-only upload for testing migration has caused the Debian Bug report #983793, regarding grc needs a source-only upload for testing migration 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.) -- 983793: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=983793 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: grc Version: 1.12-1 Severity: serious https://tracker.debian.org/pkg/grc Migration status for grc (1.11.3-1.1 to 1.12-1): BLOCKED: Rejected/violates migration policy/introduces a regression Issues preventing migration: Not built on buildd: arch all binaries uploaded by garabik, a new source-only upload is needed to allow migration --- End Message --- --- Begin Message --- Version: 1.13.1-1 Hi Adrian, On Mon, 01 Mar 2021 22:25:41 +0200 Adrian Bunk wrote: > Source: grc > Version: 1.12-1 > Severity: serious > > https://tracker.debian.org/pkg/grc > > Migration status for grc (1.11.3-1.1 to 1.12-1): BLOCKED: Rejected/violates > migration policy/introduces a regression > Issues preventing migration: > Not built on buildd: arch all binaries uploaded by garabik, a new source-only > upload is needed to allow migration Apart from age, the only blocker now is this bug, closing. Paul OpenPGP_signature Description: OpenPGP digital signature --- End Message ---
Bug#992898: debian-design build-depends on obsolete version of boxer-data
Package: debian-parl Version: 1.9.27 Severity: serious Tags: bookworm, sid Debian-parl has a build-dependency on boxer-data (< 10.9) but testing and unstable have version 10.9.1
Bug#992897: debian-design build-depends on obsolete version of boxer-data
Package: debian-design Version: 3.0.22 Severity: serious Debian-design has a build-dependency on boxer-data (< 10.9) but testing and unstable have version 10.9.1
Bug#992896: etbemon: FTBFS due to RPC removal from glibc
Source: etbemon Version: 1.3.5-7 Severity: serious Tags: patch ftbfs Justification: fails to build from source (but built successfully in the past) Dear maintainer, The glibc SunRPC implementation has been marked obsolete for some time. It has been removed upstream from glibc 2.32, and it got disabled in the recent glibc uploads. The TI RPC implementation should be used instead, which also brings new features (IPv6, Kerberos support, ...). Your recent package upload failed to build in sid for that reason. You will find attached a patch to switch to the TI RPC implementation, fixing the FTBFS. Regards, Aurelien diff -u etbemon-1.3.5/debian/control etbemon-1.3.5/debian/control --- etbemon-1.3.5/debian/control +++ etbemon-1.3.5/debian/control @@ -4,7 +4,7 @@ Maintainer: Debian Mon Maintainers Uploaders: Dario Minnucci , Russell Coker -Build-Depends: debhelper (>= 11), perl, libtime-period-perl +Build-Depends: debhelper (>= 11), perl, libtime-period-perl, libtirpc-dev Standards-Version: 4.3.0 Homepage: https://doc.coker.com.au/projects/etbe-mon/ Vcs-Git: https://salsa.debian.org/etbe/etbemon.git only in patch2: unchanged: --- etbemon-1.3.5.orig/mon.d/Makefile +++ etbemon-1.3.5/mon.d/Makefile @@ -6,7 +6,8 @@ CC = gcc CFLAGS = `dpkg-buildflags --get CFLAGS` LDFLAGS = `dpkg-buildflags --get LDFLAGS` -LDLIBS = +INCFLAGS = -I/usr/include/tirpc +LDLIBS = -ltirpc # uncomment next line for Solaris # LDLIBS = -lnsl -lsocket @@ -20,7 +21,7 @@ all: $(PROGS) rpc.monitor: rpc.monitor.c - $(CC) -o rpc.monitor $(CFLAGS) $(CPPFLAGS) $(LDFLAGS) rpc.monitor.c $(LDLIBS) + $(CC) -o rpc.monitor $(CFLAGS) $(CPPFLAGS) $(INCFLAGS) $(LDFLAGS) rpc.monitor.c $(LDLIBS) dialin.monitor.wrap: dialin.monitor.wrap.c $(CC) -o dialin.monitor.wrap $(CFLAGS) $(CPPFLAGS) $(LDFLAGS) \
Processed: src:python-xarray: fails to migrate to testing for too long
Processing control commands: > close -1 0.19.0-2 Bug #992895 [src:python-xarray] src:python-xarray: fails to migrate to testing for too long Marked as fixed in versions python-xarray/0.19.0-2. Bug #992895 [src:python-xarray] src:python-xarray: fails to migrate to testing for too long Marked Bug as done -- 992895: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=992895 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#992895: src:python-xarray: fails to migrate to testing for too long
Source: python-xarray Version: 0.16.2-2 Severity: serious Control: close -1 0.19.0-2 Tags: sid bookworm User: release.debian@packages.debian.org Usertags: out-of-sync Dear maintainer(s), As recently announced [1], the Release Team now considers packages that are out-of-sync between testing and unstable for more than 60 days as having a Release Critical bug in testing. Your package src:python-xarray has been trying to migrate for 178 days [2] (yes, most of that time was during the freeze). Hence, I am filing this bug. If a package is out of sync between unstable and testing for a longer period, this usually means that bugs in the package in testing cannot be fixed via unstable. Additionally, blocked packages can have impact on other packages, which makes preparing for the release more difficult. Finally, it often exposes issues with the package and/or its (reverse-)dependencies. We expect maintainers to fix issues that hamper the migration of their package in a timely manner. This bug will trigger auto-removal when appropriate. As with all new bugs, there will be at least 30 days before the package is auto-removed. I have immediately closed this bug with the version in unstable, so if that version or a later version migrates, this bug will no longer affect testing. I have also tagged this bug to only affect sid and bookworm, so it doesn't affect (old-)stable. If you believe your package is unable to migrate to testing due to issues beyond your control, don't hesitate to contact the Release Team. Paul [1] https://lists.debian.org/debian-devel-announce/2020/02/msg5.html [2] https://qa.debian.org/excuses.php?package=python-xarray OpenPGP_signature Description: OpenPGP digital signature
Bug#991788: Disabling Upower support in xfce4-settings
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Control: severity -1 normal On Tue, 2021-08-17 at 22:05 +0200, truetec...@tutanota.com wrote: > Hello, > > When compiled with --enable-upower-glib, xfce4-power-manager doesn't seem to > re-enable laptop displays after suspending the system. And, for that reason, > this is disabled by default upstream... but it was explicitly re-enabled in > Debian for some reason. I reported this issue as a critical bug under > #991788 in xfce4-settings and was told that xfce4 maintainers in Debian > would have to decide whether or not to change this. However, it has been a > while and I want to bring attention to it further, especially as an update > without attention to this feature has already been pushed to unstable. > > Upstream bug report: > https://gitlab.xfce.org/xfce/xfce4-settings/-/issues/222 > Debian bug report: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=991788 > Hi Elliot, thanks for the message, but it's usually best to directly send messages to the bug report, that way it's archived on the bug tracker (sorry we didn't reply earlier on it). That's definitely not a “critical” bug though (thus adjusting the severity). And unfortunately the “upstream” fix isn't really good because that actually means just not listening to the lid events, and that's a behavior which I think we do want. As far as I can tell it does work fine on other configurations, but maybe there's an issue with the proprietary NVidia driver (if you can try with nouveau or something like that, it'd be an interesting data point). Regards, - -- Yves-Alexis -BEGIN PGP SIGNATURE- iQEzBAEBCAAdFiEE8vi34Qgfo83x35gF3rYcyPpXRFsFAmElQ6kACgkQ3rYcyPpX RFsP2Qf/aaipVYYhL8CdBZ3oL6xF72n3JNhCPOIvCggH+5BAKHG/xdgROsalKJLd l0mI8kHqqotc7SBWd6Rlndz26SvxTMgcIZ5rxrevkq05e8zzhystfCtqK8kIGs1+ LzHA+yS1kPrGqx170I4Dkw/EtdLovXOvJFQwGcGZDvqFq1IEAtvwg3m7OaN06xWj WTYnVPF2ByzC6g3t5VAUglKG8AwKS65fmAJzauv/iCF28QApYcUchQhDu4mLy/Rm TmdWjT/n0Fv2IZiB6HMbGzB8o0p86niUb4+RgKZ58RV1a89exRG6i7vuVt/BAPpF BohukQsr4iVsA5+GyWF0gnY3IZR9Pg== =1nfL -END PGP SIGNATURE-
Processed: Re: Disabling Upower support in xfce4-settings
Processing control commands: > severity -1 normal Bug #991788 [xfce4-settings] xfce4-settings: black screen after suspend when laptop lid is closed and re-opened Severity set to 'normal' from 'critical' -- 991788: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=991788 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: src:mit-scheme: fails to migrate to testing for too long
Processing control commands: > close -1 11.2-1 Bug #992894 [src:mit-scheme] src:mit-scheme: fails to migrate to testing for too long Marked as fixed in versions mit-scheme/11.2-1. Bug #992894 [src:mit-scheme] src:mit-scheme: fails to migrate to testing for too long Marked Bug as done -- 992894: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=992894 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#992894: src:mit-scheme: fails to migrate to testing for too long
Source: mit-scheme Version: 10.1.11-2 Severity: serious Control: close -1 11.2-1 Tags: sid bookworm User: release.debian@packages.debian.org Usertags: out-of-sync Dear maintainer(s), As recently announced [1], the Release Team now considers packages that are out-of-sync between testing and unstable for more than 60 days as having a Release Critical bug in testing. Your package src:mit-scheme has been trying to migrate for 196 days [2]. Hence, I am filing this bug. If a package is out of sync between unstable and testing for a longer period, this usually means that bugs in the package in testing cannot be fixed via unstable. Additionally, blocked packages can have impact on other packages, which makes preparing for the release more difficult. Finally, it often exposes issues with the package and/or its (reverse-)dependencies. We expect maintainers to fix issues that hamper the migration of their package in a timely manner. This bug will trigger auto-removal when appropriate. As with all new bugs, there will be at least 30 days before the package is auto-removed. I have immediately closed this bug with the version in unstable, so if that version or a later version migrates, this bug will no longer affect testing. I have also tagged this bug to only affect sid and bookworm, so it doesn't affect (old-)stable. If you believe your package is unable to migrate to testing due to issues beyond your control, don't hesitate to contact the Release Team. Paul [1] https://lists.debian.org/debian-devel-announce/2020/02/msg5.html [2] https://qa.debian.org/excuses.php?package=mit-scheme OpenPGP_signature Description: OpenPGP digital signature
Bug#992680: marked as done (latencytop_0.5-0.1_mipsel-buildd.changes REJECTED)
Your message dated Tue, 24 Aug 2021 18:05:39 + with message-id and subject line Bug#992680: fixed in latencytop 0.5.0-0.1 has caused the Debian Bug report #992680, regarding latencytop_0.5-0.1_mipsel-buildd.changes REJECTED 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.) -- 992680: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=992680 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: latencytop Version: 0.5-0.1 Severity: serious On 2021-08-22 05:34, Debian FTP Masters wrote: > Version check failed: > Your upload included the binary package latencytop, version 0.5-0.1, for > mipsel, > however oldoldstable already has version 0.5+b3. > Uploads to unstable must have a higher version than present in oldoldstable. > > Mapping sid to unstable. > > === > > Please feel free to respond to this email if you don't understand why > your files were rejected, or if you upload new files which address our > concerns. > > > --- End Message --- --- Begin Message --- Source: latencytop Source-Version: 0.5.0-0.1 Done: Boyuan Yang We believe that the bug you reported is fixed in the latest version of latencytop, 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 992...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Boyuan Yang (supplier of updated latencytop package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Tue, 24 Aug 2021 13:26:42 -0400 Source: latencytop Architecture: source Version: 0.5.0-0.1 Distribution: unstable Urgency: high Maintainer: Giacomo Catenazzi Changed-By: Boyuan Yang Closes: 992680 Changes: latencytop (0.5.0-0.1) unstable; urgency=high . * Non-maintainer upload. * Bump source version string to avoid rejection from previous unreasonable version string. (Closes: #992680) Checksums-Sha1: 05eff5dc96ac6a08ec1f6671155304a915fac350 1902 latencytop_0.5.0-0.1.dsc cfd8a83fa40e630cf680d96a186ff4fdbf6f22c8 25374 latencytop_0.5.0.orig.tar.gz d631d7ad2d1a721bc983a5f5ef8f12a1fd445758 3796 latencytop_0.5.0-0.1.debian.tar.xz 0edd0325686e985d5db8675569ad25f54fb26a96 11246 latencytop_0.5.0-0.1_amd64.buildinfo Checksums-Sha256: 8c5c296e7e0cbb0d202f6ee6b89dc47a4862d46ca5153be4b0fcb69c96acf5d4 1902 latencytop_0.5.0-0.1.dsc 9e7f72fbea7bd918e71212a1eabaad8488d2c602205d2e3c95d62cd57e9203ef 25374 latencytop_0.5.0.orig.tar.gz 677a9623216a84da2c5999852630274ecfd834bce508e9265e8082dddc34a2c3 3796 latencytop_0.5.0-0.1.debian.tar.xz 769d92fedd99de15c93e6931cbe25587fbd4c02d3e4e19ac4de8410697baa0ed 11246 latencytop_0.5.0-0.1_amd64.buildinfo Files: b77f81d3737fa03d81dc8fe2fddefd87 1902 utils optional latencytop_0.5.0-0.1.dsc 73bb3371c6ee0b0e68e25289027e865c 25374 utils optional latencytop_0.5.0.orig.tar.gz 9af46bc98b9bd2d941380863b76e2060 3796 utils optional latencytop_0.5.0-0.1.debian.tar.xz de3cd3335879f89b25d14d7dfa9aad1e 11246 utils optional latencytop_0.5.0-0.1_amd64.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEfncpR22H1vEdkazLwpPntGGCWs4FAmElL28ACgkQwpPntGGC Ws5d0g/7BFA98/TEXfbv7vLBOOLDSks2HLcp15FHI44PK16/PS4Oor8zhQ2Q2l75 /+2XPyZhUO85wBSs6XfUvQPHVZekCQWP+lwPXaIRCkB+1hwLsVR2Uq9A8ryC0C5A OyxMowMyPyvP3noa/p8JiGnJRD/tlJ4mTR5owUdd/e7T7PfgCUSSqOrw1BbJ9jsv XcQhG7Db1ilxL+t1f+nwmsfumxzQtSWINKnHoG4axHh8l537lVC5kgaiJRsPkcFp Bevpjk6SDcbaIVJXW9NHVP7QT8WWR1vdYShvxzjLBoNZGTLxP8s9De7xLRF2KsjM cNtipcdG90FzTpdOtMVnzdFsmU6jok2M5DZHw5BXibmzyEh2k8+CqJawsVISiiBe pkSUM4gZjM3YGIbI32bsDvat/XIU7HbuF0TXVRwR4TizuyicIDmpVU3/qZZKUnXn qPdarDfmsXrhnBNKtIT99zwchYl5EDmt1ba4JXa//VAXBAQvghnNXwYeeFitsYRI 5bOs20eRTKMwMBg54/TyInDG6Wo3v3BsvOz7F0aapIaQWwez+o5dX5M4STBaCEVZ 4mmo2XDitzGGWLK1iLiw60ZFP8vcrx1JAwoIVFSq6VQFSmpkSAAxvp0/AuB62j76 PnaOwCOMjgfAsYaZiiiTEIo2z66+lCE2iDWXzV/3tA1eZfkTG6s= =Zjch -END PGP SIGNATURE End Message ---
Bug#992778: marked as done (rust-thread-local: autopkgtest failure)
Your message dated Tue, 24 Aug 2021 16:50:11 + with message-id and subject line Bug#992778: fixed in rust-thread-local 1.1.3-3 has caused the Debian Bug report #992778, regarding rust-thread-local: autopkgtest failure to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 992778: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=992778 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: rust-thread-local Version: 1.1.3-2 Severity: serious Rust-thread-local's autopkgtests are failing and blocking it's migration to testing. https://ci.debian.net/data/autopkgtest/testing/amd64/r/rust-thread-local/14765623/log.gz Running `CARGO=/usr/bin/cargo CARGO_CRATE_NAME=thread_local CARGO_MANIFEST_DIR=/usr/share/cargo/registry/thread_local-1.1.3 CARGO_PKG_AUTHORS='Amanieu d'\''Antras ' CARGO_PKG_DESCRIPTION='Per-object thread-local storage' CARGO_PKG_HOMEPAGE='' CARGO_PKG_LICENSE=Apache-2.0/MIT CARGO_PKG_LICENSE_FILE='' CARGO_PKG_NAME=thread_local CARGO_PKG_REPOSITORY='https://github.com/Amanieu/thread_local-rs' CARGO_PKG_VERSION=1.1.3 CARGO_PKG_VERSION_MAJOR=1 CARGO_PKG_VERSION_MINOR=1 CARGO_PKG_VERSION_PATCH=3 CARGO_PKG_VERSION_PRE='' LD_LIBRARY_PATH='/tmp/tmp.OlDihhKdPX/target/debug/deps:/usr/lib' rustc --crate-name thread_local --edition=2018 benches/thread_local.rs --error-format=json --json=diagnostic-rendered-ansi --emit=dep-info,link -Cembed-bitcode=no -C debuginfo=2 --test -C metadata=84c6c306f6e0bed2 -C extra-filename=-84c6c306f6e0bed2 --out-dir /tmp/tmp.OlDihhKdPX/target/x86_64-unknown-linux-gnu/debug/deps --target x86_64-unknown-linux-gnu -C incremental=/tmp/tmp.OlDihhKdPX/target/x86_64-unknown-linux-gnu/debug/incremental -L dependency=/tmp/tmp.OlDihhKdPX/target/x86_64-unknown-linux-gnu/debug/deps -L dependency=/tmp/tmp.OlDihhKdPX/target/debug/deps --extern once_cell=/tmp/tmp.OlDihhKdPX/target/x86_64-unknown-linux-gnu/debug/deps/libonce_cell-453a2446d2f99dbf.rlib --extern thread_local=/tmp/tmp.OlDihhKdPX/target/x86_64-unknown-linux-gnu/debug/deps/libthread_local-f9dcf1a1fea5cb2d.rlib -C debuginfo=2 --cap-lints warn -C linker=x86_64-linux-gnu-gcc -C link-arg=-Wl,-z,relro --remap-path-prefix /usr/share/cargo/registry/thread_local-1.1.3=/usr/share/cargo/registry/thread-local-1.1.3` error[E0463]: can't find crate for `criterion` --> benches/thread_local.rs:1:1 | 1 | extern crate criterion; | ^^^ can't find crate error: aborting due to previous error For more information about this error, try `rustc --explain E0463`. error: could not compile `thread_local`. Looking at the package, it seems some attempt was made to disable criterion, but it doesn't seem to have been successful with regards to autopkgtests, I'm not sure if there is a sane way to tell autopkgtest not to run "benches". In sniffglue I resorted to completely deleting the offending file to solve a similarissie but that is a pain from a maintenance point of view, so I'd rather not do it in more packages. I'd rather not completely disable/mark as broken the autopkgtests because they pass in testing, so it would be a step backwards. Thoughts on the best way to proceed? --- End Message --- --- Begin Message --- Source: rust-thread-local Source-Version: 1.1.3-3 Done: Peter Michael Green We believe that the bug you reported is fixed in the latest version of rust-thread-local, 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 992...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Peter Michael Green (supplier of updated rust-thread-local 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, 24 Aug 2021 16:23:08 + Source: rust-thread-local Architecture: source Version: 1.1.3-3 Distribution: unstable Urgency: medium Maintainer: Debian Rust Maintainers Changed-By: Peter Michael Green Closes: 992778 Changes: rust-thread-local (1.1.3-3) unstable; urgency=medium . * Team upload. * Package thread_local 1.1.3 from crates.io using debcargo 2.4.4 * Disable benches that depend on criterion which we don't have in Debian. (Closes: 992778) Checksums-Sha1: d899d5d3
Bug#978921: marked as done (watchman: ftbfs with autoconf 2.70)
Your message dated Tue, 24 Aug 2021 16:06:59 +
with message-id
and subject line Bug#978921: fixed in watchman 4.9.0-6
has caused the Debian Bug report #978921,
regarding watchman: ftbfs with autoconf 2.70
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.)
--
978921: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=978921
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:watchman
Version: 4.9.0-4
Severity: normal
Tags: sid bookworm
User: d...@debian.org
Usertags: ftbfs-ac270
[This bug report is not targeted to the upcoming bullseye release]
The package fails to build in a test rebuild on at least amd64 with
autoconf 2.70, but succeeds to build with autoconf 2.69. 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://qa-logs.debian.net/2020/09/26.ac270/watchman_4.9.0-4_unstable_ac270.log
The last lines of the build log are at the end of this report.
To build with autoconf 2.70, please install the autoconf package from
experimental: apt-get -t=experimental install autoconf
[...]
-o -name '*.orig' -o -name '*.rej' -o -name '*.bak' \
-o -name '.*.orig' -o -name .*.rej -o -name '.SUMS' \
-o -name TAGS -o \( -path '*/.deps/*' -a -name '*.P' \) \
\) -exec rm -f {} + \) -o \
\( -type d -a -name autom4te.cache -prune -exec rm -rf {} + \)
\)
dpkg-source -b .
dpkg-source: info: using source format '3.0 (quilt)'
dpkg-source: info: building watchman using existing ./watchman_4.9.0.orig.tar.gz
dpkg-source: info: using patch list from debian/patches/series
dpkg-source: info: building watchman in watchman_4.9.0-4.debian.tar.xz
dpkg-source: info: building watchman in watchman_4.9.0-4.dsc
debian/rules binary
dh binary --with python3
py3versions: no X-Python3-Version in control file, using supported versions
dh_update_autotools_config
debian/rules override_dh_autoreconf
make[1]: Entering directory '/<>'
dh_autoreconf -- ./autogen.sh
py3versions: no X-Python3-Version in control file, using supported versions
find ! -ipath "./debian/*" -a ! \( -path '*/.git/*' -o -path '*/.hg/*'
-o -path '*/.bzr/*' -o -path '*/.svn/*' -o -path '*/CVS/*' \) -a -type f -exec
md5sum {} + -o -type l -printf "symlink %p
" > debian/autoreconf.before
./autogen.sh ./autogen.sh
libtoolize: putting auxiliary files in '.'.
libtoolize: linking file './ltmain.sh'
libtoolize: putting macros in AC_CONFIG_MACRO_DIRS, 'm4'.
libtoolize: linking file 'm4/libtool.m4'
libtoolize: linking file 'm4/ltoptions.m4'
libtoolize: linking file 'm4/ltsugar.m4'
libtoolize: linking file 'm4/ltversion.m4'
libtoolize: linking file 'm4/lt~obsolete.m4'
configure.ac:231: warning: The macro `AC_TRY_LINK' is obsolete.
configure.ac:231: You should run autoupdate.
./lib/autoconf/general.m4:2816: AC_TRY_LINK is expanded from...
configure.ac:231: the top level
configure.ac:325: warning: The macro `AC_CONFIG_HEADER' is obsolete.
configure.ac:325: You should run autoupdate.
./lib/autoconf/status.m4:719: AC_CONFIG_HEADER is expanded from...
configure.ac:325: the top level
configure.ac:231: warning: The macro `AC_TRY_LINK' is obsolete.
configure.ac:231: You should run autoupdate.
./lib/autoconf/general.m4:2816: AC_TRY_LINK is expanded from...
configure.ac:231: the top level
configure.ac:325: warning: The macro `AC_CONFIG_HEADER' is obsolete.
configure.ac:325: You should run autoupdate.
./lib/autoconf/status.m4:719: AC_CONFIG_HEADER is expanded from...
configure.ac:325: the top level
configure.ac:231: warning: The macro `AC_TRY_LINK' is obsolete.
configure.ac:231: You should run autoupdate.
./lib/autoconf/general.m4:2816: AC_TRY_LINK is expanded from...
configure.ac:231: the top level
configure.ac:325: warning: The macro `AC_CONFIG_HEADER' is obsolete.
configure.ac:325: You should run autoupdate.
./lib/autoconf/status.m4:719: AC_CONFIG_HEADER is expanded from...
configure.ac:325: the top level
configure.ac:22: installing './compile'
configure.ac:3: installing './config.guess'
configure.ac:3: installing './config.sub'
configure.ac:4: installing './install-sh'
configure.ac:4: installing './missing'
Makefile.am: installing './depcomp'
parallel-tests: installing './test-driver'
pkg-config appears to be missing (not available to autoconf tools)
please install the pkg-config package for your system.
find ! -ipath "./debian/*" -a ! \( -path '*/.git/*' -o -path '*/.hg/*'
-o -path '*/.bzr/*' -o -path '*/.svn/*' -o -path '*/CVS/*' \)
Bug#978809: marked as done (flickcurl: ftbfs with autoconf 2.70)
Your message dated Tue, 24 Aug 2021 16:04:12 + with message-id and subject line Bug#978809: fixed in flickcurl 1.26-6 has caused the Debian Bug report #978809, regarding flickcurl: ftbfs with autoconf 2.70 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.) -- 978809: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=978809 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:flickcurl Version: 1.26-5 Severity: normal Tags: sid bookworm User: d...@debian.org Usertags: ftbfs-ac270 [This bug report is not targeted to the upcoming bullseye release] The package fails to build in a test rebuild on at least amd64 with autoconf 2.70, but succeeds to build with autoconf 2.69. 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://qa-logs.debian.net/2020/09/26.ac270/flickcurl_1.26-5_unstable_ac270.log The last lines of the build log are at the end of this report. To build with autoconf 2.70, please install the autoconf package from experimental: apt-get -t=experimental install autoconf [...] LOGNAME=user42 PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games SCHROOT_ALIAS_NAME=unstable SCHROOT_CHROOT_NAME=sid-amd64-sbuild SCHROOT_COMMAND=env SCHROOT_GID=1001 SCHROOT_GROUP=user42 SCHROOT_SESSION_ID=sid-amd64-sbuild-81297f0d-182a-4fcf-bb77-5b2c472b153e SCHROOT_UID=1001 SCHROOT_USER=user42 SHELL=/bin/sh USER=user42 dpkg-buildpackage - Command: dpkg-buildpackage -us -uc -sa -rfakeroot dpkg-buildpackage: info: source package flickcurl dpkg-buildpackage: info: source version 1.26-5 dpkg-buildpackage: info: source distribution unstable dpkg-buildpackage: info: source changed by Kumar Appaiah dpkg-source --before-build . dpkg-buildpackage: info: host architecture amd64 fakeroot debian/rules clean dh clean --with autoreconf dh: warning: Compatibility levels before 10 are deprecated (level 9 in use) dh_clean dh_clean: warning: Compatibility levels before 10 are deprecated (level 9 in use) dpkg-source -b . dpkg-source: info: using source format '3.0 (quilt)' dpkg-source: info: building flickcurl using existing ./flickcurl_1.26.orig.tar.gz dpkg-source: info: using patch list from debian/patches/series dpkg-source: info: building flickcurl in flickcurl_1.26-5.debian.tar.xz dpkg-source: info: building flickcurl in flickcurl_1.26-5.dsc debian/rules build make: 'build' is up to date. fakeroot debian/rules binary dh binary --with autoreconf dh: warning: Compatibility levels before 10 are deprecated (level 9 in use) dh_update_autotools_config dh_autoreconf configure.ac:100: warning: The macro `AC_HEADER_STDC' is obsolete. configure.ac:100: You should run autoupdate. ./lib/autoconf/headers.m4:657: AC_HEADER_STDC is expanded from... configure.ac:100: the top level configure.ac:102: warning: The macro `AC_HEADER_TIME' is obsolete. configure.ac:102: You should run autoupdate. ./lib/autoconf/headers.m4:696: AC_HEADER_TIME is expanded from... configure.ac:102: the top level configure.ac:100: warning: The macro `AC_HEADER_STDC' is obsolete. configure.ac:100: You should run autoupdate. ./lib/autoconf/headers.m4:657: AC_HEADER_STDC is expanded from... configure.ac:100: the top level configure.ac:102: warning: The macro `AC_HEADER_TIME' is obsolete. configure.ac:102: You should run autoupdate. ./lib/autoconf/headers.m4:696: AC_HEADER_TIME is expanded from... configure.ac:102: the top level libtoolize: putting auxiliary files in AC_CONFIG_AUX_DIR, 'build'. libtoolize: copying file 'build/ltmain.sh' libtoolize: putting macros in AC_CONFIG_MACRO_DIRS, 'build'. libtoolize: copying file 'build/libtool.m4' libtoolize: copying file 'build/ltoptions.m4' libtoolize: copying file 'build/ltsugar.m4' libtoolize: copying file 'build/ltversion.m4' libtoolize: copying file 'build/lt~obsolete.m4' Can't exec "gtkdocize": No such file or directory at /usr/share/autoconf/Autom4te/FileUtils.pm line 293. autoreconf: error: gtkdocize failed with exit status: 2 dh_autoreconf: error: autoreconf -f -i returned exit code 2 make: *** [debian/rules:3: binary] Error 25 dpkg-buildpackage: error: fakeroot debian/rules binary subprocess returned exit status 2 --- End Message --- --- Begin Message --- Source: flickcurl Source-Version: 1.26-6 Done: Kumar Appaiah We believe that the bug you reported is fixed in the latest version of flickcurl, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is att
Processed: limit source to flickcurl, tagging 978809
Processing commands for cont...@bugs.debian.org: > limit source flickcurl Limiting to bugs with field 'source' containing at least one of 'flickcurl' Limit currently set to 'source':'flickcurl' > tags 978809 + pending Bug #978809 [src:flickcurl] flickcurl: ftbfs with autoconf 2.70 Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 978809: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=978809 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#978920: marked as done (wbar: ftbfs with autoconf 2.70)
Your message dated Tue, 24 Aug 2021 14:42:35 + with message-id and subject line Bug#978920: fixed in wbar 2.3.4-11 has caused the Debian Bug report #978920, regarding wbar: ftbfs with autoconf 2.70 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.) -- 978920: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=978920 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:wbar Version: 2.3.4-10 Severity: normal Tags: sid bookworm User: d...@debian.org Usertags: ftbfs-ac270 [This bug report is not targeted to the upcoming bullseye release] The package fails to build in a test rebuild on at least amd64 with autoconf 2.70, but succeeds to build with autoconf 2.69. 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://qa-logs.debian.net/2020/09/26.ac270/wbar_2.3.4-10_unstable_ac270.log The last lines of the build log are at the end of this report. To build with autoconf 2.70, please install the autoconf package from experimental: apt-get -t=experimental install autoconf [...] aclocal: warning: couldn't open directory 'm4': No such file or directory configure.ac:6: warning: 'AM_CONFIG_HEADER': this macro is obsolete. configure.ac:6: You should use the 'AC_CONFIG_HEADERS' macro instead. ./lib/autoconf/general.m4:2328: AC_DIAGNOSE is expanded from... /usr/share/aclocal-1.16/obsolete.m4:11: AM_CONFIG_HEADER is expanded from... configure.ac:6: the top level configure.ac:6: warning: The macro `AC_DIAGNOSE' is obsolete. configure.ac:6: You should run autoupdate. ./lib/autoconf/general.m4:2328: AC_DIAGNOSE is expanded from... /usr/share/aclocal-1.16/obsolete.m4:11: AM_CONFIG_HEADER is expanded from... configure.ac:6: the top level configure.ac:11: warning: The macro `AC_HEADER_STDC' is obsolete. configure.ac:11: You should run autoupdate. ./lib/autoconf/headers.m4:657: AC_HEADER_STDC is expanded from... configure.ac:11: the top level configure.ac:61: warning: The macro `AC_PROG_INTLTOOL' is obsolete. configure.ac:61: You should run autoupdate. /usr/share/aclocal/intltool.m4:209: AC_PROG_INTLTOOL is expanded from... configure.ac:61: the top level configure.ac:62: warning: The macro `GLIB_GNU_GETTEXT' is obsolete. configure.ac:62: You should run autoupdate. /usr/share/aclocal/glib-gettext.m4:366: GLIB_GNU_GETTEXT is expanded from... /usr/share/aclocal/glib-gettext.m4:466: AM_GLIB_GNU_GETTEXT is expanded from... configure.ac:62: the top level configure.ac:62: warning: The macro `AC_TRY_LINK' is obsolete. configure.ac:62: You should run autoupdate. ./lib/autoconf/general.m4:2816: AC_TRY_LINK is expanded from... lib/m4sugar/m4sh.m4:673: AS_IF is expanded from... ./lib/autoconf/general.m4:2149: AC_CACHE_VAL is expanded from... ./lib/autoconf/general.m4:2170: AC_CACHE_CHECK is expanded from... /usr/share/aclocal/glib-gettext.m4:51: GLIB_LC_MESSAGES is expanded from... /usr/share/aclocal/glib-gettext.m4:366: GLIB_GNU_GETTEXT is expanded from... /usr/share/aclocal/glib-gettext.m4:466: AM_GLIB_GNU_GETTEXT is expanded from... configure.ac:62: the top level configure.ac:62: warning: The macro `AC_TRY_LINK' is obsolete. configure.ac:62: You should run autoupdate. ./lib/autoconf/general.m4:2816: AC_TRY_LINK is expanded from... lib/m4sugar/m4sh.m4:673: AS_IF is expanded from... ./lib/autoconf/general.m4:2149: AC_CACHE_VAL is expanded from... ./lib/autoconf/general.m4:2170: AC_CACHE_CHECK is expanded from... lib/m4sugar/m4sh.m4:673: AS_IF is expanded from... ./lib/autoconf/headers.m4:89: _AC_CHECK_HEADER_COMPILE is expanded from... ./lib/autoconf/headers.m4:56: AC_CHECK_HEADER is expanded from... /usr/share/aclocal/glib-gettext.m4:150: GLIB_WITH_NLS is expanded from... /usr/share/aclocal/glib-gettext.m4:366: GLIB_GNU_GETTEXT is expanded from... /usr/share/aclocal/glib-gettext.m4:466: AM_GLIB_GNU_GETTEXT is expanded from... configure.ac:62: the top level configure.ac:62: warning: The macro `AC_TRY_LINK' is obsolete. configure.ac:62: You should run autoupdate. ./lib/autoconf/general.m4:2816: AC_TRY_LINK is expanded from... lib/m4sugar/m4sh.m4:673: AS_IF is expanded from... ./lib/autoconf/headers.m4:89: _AC_CHECK_HEADER_COMPILE is expanded from... ./lib/autoconf/headers.m4:56: AC_CHECK_HEADER is expanded from... /usr/share/aclocal/glib-gettext.m4:150: GLIB_WITH_NLS is expanded from... /usr/share/aclocal/glib-gettext.m4:366: GLIB_GNU_GETTEXT is expanded from... /usr/share/aclocal/glib-gettext.m4:466: AM_GLIB_GNU_GETTEXT is expanded from... configure.ac:62: the top level configure.ac:62: warning: T
Bug#978772: marked as done (autogen: ftbfs with autoconf 2.70)
Your message dated Tue, 24 Aug 2021 16:01:04 +0200
with message-id
and subject line Re: Bug#978772: autogen: ftbfs with autoconf 2.70
has caused the Debian Bug report #978772,
regarding autogen: ftbfs with autoconf 2.70
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.)
--
978772: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=978772
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:autogen
Version: 5.18.16-4
Severity: normal
Tags: sid bookworm
User: d...@debian.org
Usertags: ftbfs-ac270
[This bug report is not targeted to the upcoming bullseye release]
The package fails to build in a test rebuild on at least amd64 with
autoconf 2.70, but succeeds to build with autoconf 2.69. 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://qa-logs.debian.net/2020/09/26.ac270/autogen_5.18.16-4_unstable_ac270.log
The last lines of the build log are at the end of this report.
To build with autoconf 2.70, please install the autoconf package from
experimental: apt-get -t=experimental install autoconf
[...]
#define HAVE_UINTMAX_T 1
#define HAVE_SIZE_T 1
#define HAVE_WCHAR_T 1
#define SIZEOF_CHARP 8
#define SIZEOF_INT 4
#define SIZEOF_LONG 8
#define SIZEOF_SHORT 2
#define HAVE_UNSIGNED_LONG_LONG_INT 1
#define HAVE_STRUCT_STAT_ST_MTIM 1
#define HAVE_STRCHR 1
#define HAVE_SNPRINTF 1
#define HAVE_DLOPEN 1
#define HAVE_UTIMENSAT 1
#define HAVE_CLOCK_GETTIME 1
#define HAVE_COPYSIGN 1
#define HAVE_COPYSIGNL 1
#define HAVE_MODFL 1
#define HAVE_CTYPE_H 1
#define HAVE_ASSERT_H 1
#define HAVE_SYS_RESOURCE_H 1
#define HAVE_DECL_SIGSETJMP 1
#define HAVE_DECL_SYS_SIGLIST 1
#define HAVE_PUTENV 1
#define HAVE_GETDATE_R 1
#define HAVE_UTIMES 1
#define HAVE_FUTIMES 1
#define HAVE_LONG_LONG_INT 1
#define HAVE_FORK 1
#define HAVE_VFORK 1
#define HAVE_VPRINTF 1
#ifndef __x86_64__
#define __x86_64__ 1
#endif
#ifndef __x86_64__
#define __x86_64__ 1
#endif
#define HAVE_DIRENT_H 1
#define HAVE_SYS_MMAN_H 1
#define HAVE_SYS_PARAM_H 1
#define HAVE_SYS_POLL_H 1
#define HAVE_SYS_SELECT_H 1
#define HAVE_SYS_SOCKET_H 1
#define HAVE_SYS_TIME_H 1
#define HAVE_SYS_UN_H 1
#define HAVE_SYS_WAIT_H 1
#define HAVE_DLFCN_H 1
#define HAVE_ERRNO_H 1
#define HAVE_FCNTL_H 1
#define HAVE_LIBGEN_H 1
#define HAVE_LIBINTL_H 1
#define HAVE_MEMORY_H 1
#define HAVE_NETINET_IN_H 1
#define HAVE_SETJMP_H 1
#define HAVE_STDBOOL_H 1
#define HAVE_SYSEXITS_H 1
#define HAVE_UNISTD_H 1
#define HAVE_UTIME_H 1
#define HAVE_STDARG_H 1
#define HAVE_STRING_H 1
#define HAVE_LIMITS_H 1
#define HAVE_INTTYPES_H 1
#define HAVE_WCHAR_H 1
#define ENABLE_NLS 1
configure: exit 1
dh_auto_configure: error: ./configure --build=x86_64-linux-gnu --prefix=/usr
--includedir=\${prefix}/include --mandir=\${prefix}/share/man
--infodir=\${prefix}/share/info --sysconfdir=/etc --localstatedir=/var
--disable-option-checking --disable-silent-rules
--libdir=\${prefix}/lib/x86_64-linux-gnu --runstatedir=/run
--disable-maintainer-mode --disable-dependency-tracking --disable-silent-rules
--enable-timeout=78 --with-libxml2-libs=-lxml2
--with-libxml2-cflags=-I/usr/include/libxml2 GREP=/bin/grep POSIX_SHELL=/bin/sh
SHELL=/bin/sh returned exit code 1
make[1]: *** [debian/rules:19: override_dh_auto_configure] Error 25
make[1]: Leaving directory '/<>'
make: *** [debian/rules:59: binary] Error 2
dpkg-buildpackage: error: debian/rules binary subprocess returned exit status 2
--- End Message ---
--- Begin Message ---
On 2020-12-31 Andreas Metzler wrote:
> Control: tags -1 patch
> On 2020-12-31 Matthias Klose wrote:
> > Package: src:autogen
> > Version: 5.18.16-4
> > [This bug report is not targeted to the upcoming bullseye release]
> > The package fails to build in a test rebuild on at least amd64 with
> > autoconf 2.70, but succeeds to build with autoconf 2.69. The
> > severity of this report will be raised before the bookworm release,
> > so nothing has to be done for the bullseye release.
[...]
> For autogen/experimental (5.19.96) config/std-gnu11.m4 needs to be
> updated from gnulib m4/std-gnu11.m4 with
> ---
> a3b3fc85e3e632374811b27cb2111e50fa177e36
> 2020-12-09 04:06:40
> std-gnu11: Make compatible with Autoconf 2.70.
> * m4/std-gnu11.m4: Disable the entire file if Autoconf >= 2.70 is in
> use.
[...]
Hello,
This was fixed on autoconf's side with 2.71, quoting
https://lists.gnu.org/archive/html/autoconf/2021-01/msg00126.html
| We are pleased to announce stable release 2.71 of Autoconf.
[...]
| ** Bug fixes, including:
[...]
| *** Co
Bug#992867: Stop flooding syslog! You will fill up the disk.
Package: x11-xkb-utils Version: 7.7+5 Severity: grave Did anybody take a look at syslog recently? It is flooded with Internal error: Could not resolve keysym ... So much so that the disk will fill up.
Bug#992731: marked as done (rust-grep-regex_0.1.9-1_amd64-buildd.changes REJECTED)
Your message dated Tue, 24 Aug 2021 13:20:18 + with message-id and subject line Bug#992731: fixed in rust-grep-regex 0.1.9-2 has caused the Debian Bug report #992731, regarding rust-grep-regex_0.1.9-1_amd64-buildd.changes REJECTED 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.) -- 992731: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=992731 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: rust-grep-regex Version: 0.1.9-1 Severity: serious On 2021-08-22 19:18, Debian FTP Masters wrote: > > > librust-grep-regex-dev_0.1.9-1_amd64.deb: has 15 file(s) with a timestamp too > far in the past: > usr/share/cargo/registry/grep-regex-0.1.9/LICENSE-MIT (Thu Nov 29 21:33:09 > 1973) usr/share/cargo/registry/grep-regex-0.1.9/README.md (Thu Nov 29 > 21:33:09 1973) usr/share/cargo/registry/grep-regex-0.1.9/UNLICENSE (Thu Nov > 29 21:33:09 1973) usr/share/cargo/registry/grep-regex-0.1.9/src/ast.rs (Thu > Nov 29 21:33:09 1973) > usr/share/cargo/registry/grep-regex-0.1.9/src/config.rs (Thu Nov 29 21:33:09 > 1973) usr/share/cargo/registry/grep-regex-0.1.9/src/crlf.rs (Thu Nov 29 > 21:33:09 1973) usr/share/cargo/registry/grep-regex-0.1.9/src/error.rs (Thu > Nov 29 21:33:09 1973) usr/share/cargo/registry/grep-regex-0.1.9/src/lib.rs > (Thu Nov 29 21:33:09 1973) > usr/share/cargo/registry/grep-regex-0.1.9/src/literal.rs (Thu Nov 29 21:33:09 > 1973) usr/share/cargo/registry/grep-regex-0.1.9/src/matcher.rs (Thu Nov 29 > 21:33:09 1973) usr/share/cargo/registry/grep-regex-0.1.9/src/multi.rs (Thu > Nov 29 21:33:09 1973) > usr/share/cargo/registry/grep-regex-0.1.9/src/non_matching.rs (Thu Nov 29 > 21:33:09 1973) usr/share/cargo/registry/grep-regex-0.1.9/src/strip.rs (Thu > Nov 29 21:33:09 1973) usr/share/cargo/registry/grep-regex-0.1.9/src/util.rs > (Thu Nov 29 21:33:09 1973) > usr/share/cargo/registry/grep-regex-0.1.9/src/word.rs (Thu Nov 29 21:33:09 > 1973) > > > > === > > Please feel free to respond to this email if you don't understand why > your files were rejected, or if you upload new files which address our > concerns. > > > --- End Message --- --- Begin Message --- Source: rust-grep-regex Source-Version: 0.1.9-2 Done: Peter Michael Green We believe that the bug you reported is fixed in the latest version of rust-grep-regex, 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 992...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Peter Michael Green (supplier of updated rust-grep-regex 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, 23 Aug 2021 10:00:42 + Source: rust-grep-regex Architecture: source Version: 0.1.9-2 Distribution: unstable Urgency: medium Maintainer: Debian Rust Maintainers Changed-By: Peter Michael Green Closes: 992731 Changes: rust-grep-regex (0.1.9-2) unstable; urgency=medium . * Team upload. * Package grep-regex 0.1.9 from crates.io using debcargo 2.4.4 * Fix 1973 timestamps (Closes: 992731) Checksums-Sha1: 77dadad3a709053fc1ac1987909c75154482507d 2654 rust-grep-regex_0.1.9-2.dsc 56cf8ef29db9bb7c954f529575d08dbdc5619e8b 3268 rust-grep-regex_0.1.9-2.debian.tar.xz 32c1fd3dae833becf7f37a5d0cd02324311aa548 8793 rust-grep-regex_0.1.9-2_source.buildinfo Checksums-Sha256: 0ba19e93e2420408762480c530dd330a89a45fb1b8013ddc9f6b51ea09b3a528 2654 rust-grep-regex_0.1.9-2.dsc 52e1745f2c83d3b8340c093a2d0909e572ec0d663647b6238757372235f852a2 3268 rust-grep-regex_0.1.9-2.debian.tar.xz 48be711586f3d462bb2d800485dcb11191809c955c253b72f85be15465533bcd 8793 rust-grep-regex_0.1.9-2_source.buildinfo Files: 660daa275114f9be7aa22b65bcd817d7 2654 rust optional rust-grep-regex_0.1.9-2.dsc cdf02a56b300fbe273ad056caf01e372 3268 rust optional rust-grep-regex_0.1.9-2.debian.tar.xz 8585aae76fd9212e2fc59059d38016cc 8793 rust optional rust-grep-regex_0.1.9-2_source.buildinfo -BEGIN PGP SIGNATURE- iQJIBAEBCAAyFiEEU0DQATYMplbjSX63DEjqKnqP/XsFAmEk64wUHHBsdWd3YXNo QGRlYmlhbi5vcmcACgkQDEjqKnqP/XtTPQ/+JHU2XZpymAjkXinuOTrasExtyYAl /8tMPIRBd8zurrJ1ZJONQ9fuoFSeneQZX7+HYvdB1AMLHPNq7fMMlyS5Gt6AeIi2 v+hldDYfxh38PV13/uUYMm8PJSaB+L6vPAOF
Bug#964603: marked as done (notepadqq: FTBFS: Error copying /<>/out/release/appdata/extension_tools to /<>/debian/tmp/usr/share/notepadqq/extension_tools: Cannot open /<
Your message dated Tue, 24 Aug 2021 13:19:15 + with message-id and subject line Bug#964603: fixed in notepadqq 2.0.0~beta1-2 has caused the Debian Bug report #964603, regarding notepadqq: FTBFS: Error copying /<>/out/release/appdata/extension_tools to /<>/debian/tmp/usr/share/notepadqq/extension_tools: Cannot open /<>/out/release/appdata/extension_tools for input 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.) -- 964603: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=964603 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: notepadqq Version: 2.0.0~beta1-1 Severity: serious Justification: FTBFS on amd64 Tags: bullseye sid ftbfs Usertags: ftbfs-20200709 ftbfs-bullseye Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[4]: Entering directory '/<>/src/extension_tools' > make[4]: Nothing to be done for 'all'. > make[4]: Leaving directory '/<>/src/extension_tools' > (/usr/bin/qtchooser -run-tool=lrelease -qt=5 "/<>/src/ui/ui.pro") > Updating '/<>/src/ui/../translations/notepadqq_de.qm'... > Generated 453 translation(s) (453 finished and 0 unfinished) > Updating '/<>/src/ui/../translations/notepadqq_es.qm'... > Generated 454 translation(s) (454 finished and 0 unfinished) > Updating '/<>/src/ui/../translations/notepadqq_fr.qm'... > Generated 345 translation(s) (345 finished and 0 unfinished) > Updating '/<>/src/ui/../translations/notepadqq_hu.qm'... > Generated 454 translation(s) (454 finished and 0 unfinished) > Updating '/<>/src/ui/../translations/notepadqq_it.qm'... > Generated 451 translation(s) (434 finished and 17 unfinished) > Ignored 1 untranslated source text(s) > Updating '/<>/src/ui/../translations/notepadqq_ja.qm'... > Generated 447 translation(s) (447 finished and 0 unfinished) > Ignored 5 untranslated source text(s) > Updating '/<>/src/ui/../translations/notepadqq_pl.qm'... > Generated 452 translation(s) (452 finished and 0 unfinished) > Updating '/<>/src/ui/../translations/notepadqq_pt.qm'... > Generated 454 translation(s) (454 finished and 0 unfinished) > Updating '/<>/src/ui/../translations/notepadqq_ru.qm'... > Generated 328 translation(s) (326 finished and 2 unfinished) > Ignored 17 untranslated source text(s) > Updating '/<>/src/ui/../translations/notepadqq_sl.qm'... > Generated 345 translation(s) (345 finished and 0 unfinished) > Updating '/<>/src/ui/../translations/notepadqq_sv.qm'... > Generated 359 translation(s) (359 finished and 0 unfinished) > Updating '/<>/src/ui/../translations/notepadqq_uk.qm'... > Generated 453 translation(s) (453 finished and 0 unfinished) > Updating '/<>/src/ui/../translations/notepadqq_zh.qm'... > Generated 448 translation(s) (448 finished and 0 unfinished) > (cd "/<>/src/ui" && mkdir -p "../../out/release/lib/../bin/" && > cp -f "../../support_files/launch/notepadqq" "../../out/release/lib/../bin/" > && chmod 755 "../../out/release/lib/../bin/notepadqq") > /usr/lib/qt5/bin/rcc -name resources resources.qrc -o > ../../out/build_data/qrc_resources.cpp > c++ -c -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong > -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -O2 > -std=gnu++1y -Wall -Wextra -Wold-style-cast -D_REENTRANT -fPIC > -DQT_NO_URL_CAST_FROM_STRING -DQT_NO_DEBUG -DQT_SVG_LIB > -DQT_WEBENGINEWIDGETS_LIB -DQT_PRINTSUPPORT_LIB -DQT_WIDGETS_LIB > -DQT_WEBENGINECORE_LIB -DQT_QUICK_LIB -DQT_GUI_LIB -DQT_QMLMODELS_LIB > -DQT_WEBCHANNEL_LIB -DQT_QML_LIB -DQT_WEBSOCKETS_LIB -DQT_NETWORK_LIB > -DQT_POSITIONING_LIB -DQT_DBUS_LIB -DQT_CORE_LIB -I. -Ilibs/qtpromise/include > -Ilibs/qtpromise/src -isystem /usr/include/uchardet -isystem > /usr/include/x86_64-linux-gnu/qt5 -isystem > /usr/include/x86_64-linux-gnu/qt5/QtSvg -isystem > /usr/include/x86_64-linux-gnu/qt5/QtWebEngineWidgets -isystem > /usr/include/x86_64-linux-gnu/qt5/QtPrintSupport -isystem > /usr/include/x86_64-linux-gnu/qt5/QtWidgets -isystem > /usr/include/x86_64-linux-gnu/qt5/QtWebEngineCore -isystem > /usr/include/x86_64-linux-gnu/qt5/QtQuick -isystem > /usr/include/x86_64-linux-gnu/qt5/QtGui -isystem > /usr/include/x86_64-linux-gnu/qt5/QtQmlModels -isystem > /usr/include/x86_64-linux-gnu/qt5/QtWebChannel -isystem > /usr/include/x86_64-linux-gnu/qt5/QtQml -isystem > /usr/include/x86_64-linux-gnu/qt5/QtWebSockets -isystem > /usr/include/x86_64-linux-gnu/qt5/QtNetwork -isystem > /usr/include/x86_64-linux-gnu/qt5/QtPositioning -isystem > /usr/include/x86_64-linux-gnu/qt5/QtDBus -isystem > /us
Bug#978907: #978907: timbl: ftbfs with autoconf 2.70
tag 978907 +pending thanks thanks to Ko van der Sloot: fixed upstream in https://github.com/LanguageMachines/timbl/commit/63740b Bye, Joost
Processed: #978907: timbl: ftbfs with autoconf 2.70
Processing commands for cont...@bugs.debian.org: > tag 978907 +pending Bug #978907 [src:timbl] timbl: ftbfs with autoconf 2.70 Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 978907: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=978907 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#991897: removal of the any/local-rtlddir-cross.diff patch broke cross builds
Hi,
On 2021-08-18 15:43, Aurelien Jarno wrote:
> Hi,
>
> On 2021-08-18 11:02, Matthias Klose wrote:
> > On 8/6/21 10:44 AM, Aurelien Jarno wrote:
> > > control: reassign -1 cross-toolchain-base-ports-46
> > > control: tag -1 + patch
> > > control: tag -1 - moreinfo
> > > control: tag -1 - unreproducible
> > >
> > > On 2021-08-05 18:59, Aurelien Jarno wrote:
> > >> control: tag -1 + moreinfo
> > >> control: tag -1 + unreproducible
> > >>
> > >> On 2021-08-04 19:03, Matthias Klose wrote:
> > >>> Package: src:glibc
> > >>> Version: 2.31-13
> > >>> Severity: serious
> > >>> Tags: sid bullseye
> > >>>
> > >>> when cross-building glibc in the c-t-b packages, the libc.so linker
> > >>> file for
> > >>> some non-default multilib builds like the sparc build for sparc64 is
> > >>> broken,
> > >>> leading to build failures for at least all gcc-N cross multilib
> > >>> packages at least.
> > >>>
> > >>> $ cat usr/lib32/libc.so
> > >>> /* GNU ld script
> > >>>Use the shared library, but some functions are only in
> > >>>the static library, so try that secondarily. */
> > >>> OUTPUT_FORMAT(elf32-sparc)
> > >>> GROUP ( /lib32/libc.so.6 /usr/lib32/libc_nonshared.a AS_NEEDED (
> > >>> /lib/ld-linux.so.2 ) )
> > >>
> > >> Can you point me where you got that file? It doesn't make sense from the
> > >> path and the content point of view. Also it's not what I get in the
> > >> libc6-sparc-sparc64-cross package generated by building
> > >> cross-toolchain-base-ports in a bullseye chroot. I get instead:
> > >>
> > >> | cat /usr/sparc64-linux-gnu/lib32/libc.so
> > >> | /* GNU ld script
> > >> | Use the shared library, but some functions are only in
> > >> |the static library, so try that secondarily. */
> > >> | OUTPUT_FORMAT(elf32-sparc)
> > >> | GROUP ( /usr/sparc64-linux-gnu/lib32/libc.so.6
> > >> /usr/sparc64-linux-gnu/lib32/libc_nonshared.a AS_NEEDED (
> > >> /usr/sparc64-linux-gnu/lib/ld-linux.so.2 ) )
> > >>
> > >>> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=985617#62 says that
> > >>> the
> > >>> maintainer is investigating, but apparently this never happened.
> > >>
> > >> I *did* investigate, and checked that the changes in the linker files
> > >> are correct. I have just done that again for both cross-toolchain-base
> > >> and cross-toolchain-base-ports. Here are the differences I observed on
> > >> the linker scripts:
> > >
> > > I have ran a build of gcc-10-cross and gcc-10-cross-ports over the
> > > night. gcc-10-cross just built fine, but gcc-10-cross-ports indeed
> > > failed to build the sparc64 cross compiler as you reported.
> > >
> > > It appears that the embedded copy of dpkg-cross decided to map the
> > > multiarch path to /usr/$triplet/lib, leaving lib32, lib64 or libx32 to
> > > the other multilib builds. This causes an issue for the dynamic linker
> > > symlink, which usually follows the upstream way of putting a 64-bit
> > > library in /lib64. At the end, it means the 32-bit dynamic linker
> > > ends-up in the /usr/triplet/lib directory containing the 64 bit
> > > libraries. This is not a big deal for most architectures, except when
> > > the 32- and 64-bit dynamic linkers have the same name like on sparc64.
> > >
> > > The problem seems to have been identified, as one of the two is just
> > > removed in the debian/rules file, with this associated comment:
> > >
> > > # FIXME: don't remove these here, but find out why these are left in the
> > > glibc build
> > >
> > > The problem is that the removed one is the most useful one, breaking the
> > > assumption that /usr/$triplet/$rtld.so exists. The following patches
> > > fixes the issue for sparc64:
> > >
> > >
> > > diff -Nru cross-toolchain-base-ports-45/debian/rules
> > > cross-toolchain-base-ports-46/debian/rules
> > > --- cross-toolchain-base-ports-45/debian/rules2021-03-03
> > > 15:22:03.0 +0100
> > > +++ cross-toolchain-base-ports-46/debian/rules2021-08-06
> > > 10:31:22.0 +0200
> > > @@ -831,7 +831,7 @@
> > > case "$$pkgname" in \
> > > libc6-mips32-mips64-cross|libc6-mips32-mips64el-cross) \
> > > rm -f $$tmp/usr/*/lib/ld.so.1;; \
> > > - libc6-sparc-sparc64-cross) \
> > > + libc6-sparc64-cross) \
> > > rm -f $$tmp/usr/*/lib/ld-linux.so.2;; \
> > > esac; \
> > > if [ 'lib$(libgcc_base)1-dbg-$${cross_arch}-cross' = $$pkgname ]; then \
> > >
> > > I guess the same fix is needed for gcc-10-cross-mipsen, but I haven't
> > > been able to build it yet.
> >
> > this fixes the gcc-N-cross-ports build, but leaves the libc.so with the
> > wrong
> > path of ld-linux.so.2.
>
> What do you mean with the wrong path? gcc-N-cross-ports failed to build
> because it was pointing to the wrong ld-linux.so.2. If it builds, I
> believe it points to the correct one.
>
> > Do you intend to fix that, or should that be worked
> > around in the c-t-b package?
>
> This is not something to fix in the glibc package. The packages
> generated by cross-compiling glibc have the
Bug#992854: digikam: symbol lookup error: undefined symbol: FT_Palette_Select
I tried to build digikam from source usr/bin/ld : /lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 : référence indéfinie vers « FT_Palette_Select » /usr/bin/ld : /lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 : référence indéfinie vers « FT_Get_Color_Glyph_Layer » collect2: error: ld returned 1 exit status Best regards Alain
Bug#978847: marked as done (libglade2: ftbfs with autoconf 2.70)
Your message dated Tue, 24 Aug 2021 10:19:10 + with message-id and subject line Bug#978847: fixed in libglade2 1:2.6.4-2.4 has caused the Debian Bug report #978847, regarding libglade2: ftbfs with autoconf 2.70 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.) -- 978847: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=978847 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:libglade2 Version: 2.6.4-2.3 Severity: normal Tags: sid bookworm User: d...@debian.org Usertags: ftbfs-ac270 [This bug report is not targeted to the upcoming bullseye release] The package fails to build in a test rebuild on at least amd64 with autoconf 2.70, but succeeds to build with autoconf 2.69. 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://qa-logs.debian.net/2020/09/26.ac270/libglade2_2.6.4-2.3_unstable_ac270.log The last lines of the build log are at the end of this report. To build with autoconf 2.70, please install the autoconf package from experimental: apt-get -t=experimental install autoconf [...] /usr/share/aclocal/gtk-2.0.m4:12: AM_PATH_GTK_2_0 is expanded from... configure.in:35: the top level configure.in:35: warning: The macro `AC_TRY_LINK' is obsolete. configure.in:35: You should run autoupdate. ./lib/autoconf/general.m4:2816: AC_TRY_LINK is expanded from... /usr/share/aclocal/gtk-2.0.m4:12: AM_PATH_GTK_2_0 is expanded from... configure.in:35: the top level configure.in:117: warning: The macro `GLIB_GNU_GETTEXT' is obsolete. configure.in:117: You should run autoupdate. /usr/share/aclocal/glib-gettext.m4:366: GLIB_GNU_GETTEXT is expanded from... /usr/share/aclocal/glib-gettext.m4:466: AM_GLIB_GNU_GETTEXT is expanded from... configure.in:117: the top level configure.in:117: warning: The macro `AC_TRY_LINK' is obsolete. configure.in:117: You should run autoupdate. ./lib/autoconf/general.m4:2816: AC_TRY_LINK is expanded from... lib/m4sugar/m4sh.m4:673: AS_IF is expanded from... ./lib/autoconf/general.m4:2149: AC_CACHE_VAL is expanded from... ./lib/autoconf/general.m4:2170: AC_CACHE_CHECK is expanded from... /usr/share/aclocal/glib-gettext.m4:51: GLIB_LC_MESSAGES is expanded from... /usr/share/aclocal/glib-gettext.m4:366: GLIB_GNU_GETTEXT is expanded from... /usr/share/aclocal/glib-gettext.m4:466: AM_GLIB_GNU_GETTEXT is expanded from... configure.in:117: the top level configure.in:117: warning: The macro `AC_TRY_LINK' is obsolete. configure.in:117: You should run autoupdate. ./lib/autoconf/general.m4:2816: AC_TRY_LINK is expanded from... lib/m4sugar/m4sh.m4:673: AS_IF is expanded from... ./lib/autoconf/general.m4:2149: AC_CACHE_VAL is expanded from... ./lib/autoconf/general.m4:2170: AC_CACHE_CHECK is expanded from... lib/m4sugar/m4sh.m4:673: AS_IF is expanded from... ./lib/autoconf/headers.m4:89: _AC_CHECK_HEADER_COMPILE is expanded from... ./lib/autoconf/headers.m4:56: AC_CHECK_HEADER is expanded from... /usr/share/aclocal/glib-gettext.m4:150: GLIB_WITH_NLS is expanded from... /usr/share/aclocal/glib-gettext.m4:366: GLIB_GNU_GETTEXT is expanded from... /usr/share/aclocal/glib-gettext.m4:466: AM_GLIB_GNU_GETTEXT is expanded from... configure.in:117: the top level configure.in:117: warning: The macro `AC_TRY_LINK' is obsolete. configure.in:117: You should run autoupdate. ./lib/autoconf/general.m4:2816: AC_TRY_LINK is expanded from... lib/m4sugar/m4sh.m4:673: AS_IF is expanded from... ./lib/autoconf/headers.m4:89: _AC_CHECK_HEADER_COMPILE is expanded from... ./lib/autoconf/headers.m4:56: AC_CHECK_HEADER is expanded from... /usr/share/aclocal/glib-gettext.m4:150: GLIB_WITH_NLS is expanded from... /usr/share/aclocal/glib-gettext.m4:366: GLIB_GNU_GETTEXT is expanded from... /usr/share/aclocal/glib-gettext.m4:466: AM_GLIB_GNU_GETTEXT is expanded from... configure.in:117: the top level configure.in:117: warning: The macro `AC_OUTPUT_COMMANDS' is obsolete. configure.in:117: You should run autoupdate. ./lib/autoconf/status.m4:1025: AC_OUTPUT_COMMANDS is expanded from... /usr/share/aclocal/glib-gettext.m4:150: GLIB_WITH_NLS is expanded from... /usr/share/aclocal/glib-gettext.m4:366: GLIB_GNU_GETTEXT is expanded from... /usr/share/aclocal/glib-gettext.m4:466: AM_GLIB_GNU_GETTEXT is expanded from... configure.in:117: the top level configure.in:147: warning: The macro `AC_HELP_STRING' is obsolete. configure.in:147: You should run autoupdate. ./lib/autoconf/general.m4:203: AC_HELP_STRING is expanded from... m4/jh-xml-catalog.m4:6: JH_PATH_XML_CATALOG is expanded from... configure
Bug#992854: digikam: symbol lookup error: undefined symbol: FT_Palette_Select
Package: digikam Version: 4:7.1.0-2 Severity: grave Justification: renders package unusable X-Debbugs-Cc: alai...@free.fr Dear Maintainer, *** Reporter, please consider answering these questions, where appropriate *** * What led up to the situation? I upgraded from Buster to Bullseye * What exactly did you do (or not do) that was effective (or ineffective)? Launching digikam * What was the outcome of this action? digikam: symbol lookup error: /lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5: undefined symbol: FT_Palette_Select and digikam exits * What outcome did you expect instead? Using digikam -- System Information: Debian Release: 11.0 APT prefers stable-security APT policy: (500, 'stable-security'), (500, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.10.0-8-rt-amd64 (SMP w/4 CPU threads; PREEMPT) 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 Versions of packages digikam depends on: ii digikam-data 4:7.1.0-2 ii digikam-private-libs 4:7.1.0-2 ii libc6 2.31-13 ii libgcc-s1 10.2.1-6 ii libkf5configcore5 5.78.0-4 ii libkf5coreaddons5 5.78.0-4 ii libkf5i18n5 5.78.0-2 ii libmagick++-6.q16-8 8:6.9.11.60+dfsg-1.3 ii libqt5core5a 5.15.2+dfsg-9 ii libqt5gui55.15.2+dfsg-9 ii libqt5sql55.15.2+dfsg-9 ii libqt5sql5-mysql 5.15.2+dfsg-9 ii libqt5sql5-sqlite 5.15.2+dfsg-9 ii libqt5widgets55.15.2+dfsg-9 ii libstdc++610.2.1-6 ii perl 5.32.1-4+deb11u1 Versions of packages digikam recommends: ii chromium [www-browser] 90.0.4430.212-1 ii ffmpegthumbs 4:20.12.0-1 ii firefox-esr [www-browser] 78.13.0esr-1~deb11u1 Versions of packages digikam suggests: pn digikam-doc pn systemsettings -- no debconf information
Processed: reassign to source that fixed the double assigned bug
Processing commands for cont...@bugs.debian.org:
> reassign 992534 src:cross-toolchain-base 53
Bug #992534 {Done: Matthias Klose } [src:binutils,
src:cross-toolchain-base] binutils breaks cross-toolchain-base autopkgtest: No
such file or directory
Bug reassigned from package 'src:binutils, src:cross-toolchain-base' to
'src:cross-toolchain-base'.
No longer marked as found in versions binutils/2.37-4 and
cross-toolchain-base/53.
No longer marked as fixed in versions 54.
Bug #992534 {Done: Matthias Klose } [src:cross-toolchain-base]
binutils breaks cross-toolchain-base autopkgtest: No such file or directory
Marked as found in versions cross-toolchain-base/53.
> fixed 992534 54
Bug #992534 {Done: Matthias Klose } [src:cross-toolchain-base]
binutils breaks cross-toolchain-base autopkgtest: No such file or directory
Marked as fixed in versions cross-toolchain-base/54.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
992534: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=992534
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#992534: marked as done (binutils breaks cross-toolchain-base autopkgtest: No such file or directory)
Your message dated Tue, 24 Aug 2021 11:17:53 +0200 with message-id <36ba6b32-5f30-0781-24a6-284ff9a00...@debian.org> and subject line fixed in 54 has caused the Debian Bug report #992534, regarding binutils breaks cross-toolchain-base autopkgtest: No such file or directory to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 992534: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=992534 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: binutils, cross-toolchain-base Control: found -1 binutils/2.37-4 Control: found -1 cross-toolchain-base/53 Severity: serious Tags: sid bookworm X-Debbugs-CC: debian...@lists.debian.org User: debian...@lists.debian.org Usertags: breaks needs-update Dear maintainer(s), With a recent upload of binutils the autopkgtest of cross-toolchain-base fails in testing when that autopkgtest is run with the binary packages of binutils from unstable. It passes when run with only packages from testing. In tabular form: passfail binutils from testing2.37-4 cross-toolchain-base from testing53 all others from testingfrom testing I copied some of the output at the bottom of this report. Currently this regression is blocking the migration of binutils to testing [1]. Due to the nature of this issue, I filed this bug report against both packages. Can you please investigate the situation and reassign the bug to the right package? More information about this bug and the reason for filing it can be found on https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation Paul [1] https://qa.debian.org/excuses.php?package=binutils https://ci.debian.net/data/autopkgtest/testing/amd64/c/cross-toolchain-base/14718169/log.gz autopkgtest [12:31:01]: test build: [--- Testing cross builds on amd64 ... + CROSS_ARCHS=ppc64el DEB_BUILD_OPTIONS=parallel=2 nopgo nolto dpkg-buildpackage -d -b --no-sign dpkg-buildpackage: info: source package cross-toolchain-base dpkg-buildpackage: info: source version 53 dpkg-buildpackage: info: source distribution unstable dpkg-buildpackage: info: source changed by Matthias Klose dpkg-source --before-build . dpkg-buildpackage: info: host architecture amd64 fakeroot debian/rules clean linux: 5.10.46-4 / 5.10.13-1cross4 glibc: 2.31-13 / 2.31-9cross4 old linux version: 5.10.13-1 / 4 old glibc version: 2.31-9 / 4 new linux version: 5.10.46-4cross1 new glibc version: 2.31-13cross1 rm -rf linux-source-* rm -rf linux-[45]* rm -rf glibc-* rm -rf gcc rm -rf binutils-* rm -rf debian/tmp.ppc64el rm -f debian/files debian/no-packages rm -f debian/cross-compile find debian -name '*~' | xargs -r rm -f rm -f *.*deb *.changes *.buildinfo rm -rf repackfiles tmp tmp-* debian/tmp.* rm -rf stamp-dir/ mkdir stamp-dir/ dh_clean dh_clean: warning: Compatibility levels before 10 are deprecated (level 9 in use) debian/rules build linux: 5.10.46-4 / 5.10.13-1cross4 glibc: 2.31-13 / 2.31-9cross4 old linux version: 5.10.13-1 / 4 old glibc version: 2.31-9 / 4 new linux version: 5.10.46-4cross1 new glibc version: 2.31-13cross1 START stamp-dir/init-glibc rm -rf glibc-2.31 tar -x -f /usr/src/glibc/glibc-2.31.tar.xz cp -a /usr/src/glibc/debian/ glibc-2.31 cd glibc-2.31 ; \ QUILT_PATCHES=/tmp/autopkgtest-lxc._6ladi09/downtmp/build.RXi/src/debian/patches/glibc/debian quilt --quiltrc /dev/null push -a && \ rm -rf .pc/ Applying patch dpkg-shlibs.patch patching file debian/rules.d/debhelper.mk Hunk #1 succeeded at 82 (offset 2 lines). Applying patch local-kill-locales.patch patching file debian/rules Hunk #1 succeeded at 145 (offset 3 lines). patching file localedata/SUPPORTED Applying patch glibc-build-tools.diff patching file debian/rules Now at patch glibc-build-tools.diff touch stamp-dir/init-glibc START stamp-dir/init-gcc set -e; \ mkdir gcc -p ; \ cd gcc ; \ ln -sf /usr/src/gcc-10/gcc-10.2.0-dfsg.tar.xz \ $(basename $(tar tf /usr/src/gcc-10/gcc-10.2.0-dfsg.tar.xz | head -1)).tar.xz ;\ cp -a /usr/src/gcc-10/debian/ . ; \ if [ -n "$(grep -v '^\#' /tmp/autopkgtest-lxc._6ladi09/downtmp/build.RXi/src/debian/patches/gcc/series)" ]; then \ QUILT_PATCHES=/tmp/autopkgtest-lxc._6ladi09/downtmp/build.RXi/src/debian/patches/gcc quilt --quiltrc /dev/null push -a ; \ fi; touch stamp-dir/init-gcc START stamp-dir/init-linux rm -rf linux-source-[45].* tar -x -f /usr/src/linux-source-5.10.tar.xz touch stamp-dir/init-linux mkdir -p debian/tmp.ppc64el touch stamp-dir/init-dirs START stamp-dir/init-binutils tar -x -f /usr/src/binutils/binutils-2.37.tar.xz set -e; cd binutils-2.3
Bug#978767: marked as done (apr: ftbfs with autoconf 2.70)
Your message dated Tue, 24 Aug 2021 09:18:39 + with message-id and subject line Bug#978767: fixed in apr 1.7.0-8 has caused the Debian Bug report #978767, regarding apr: ftbfs with autoconf 2.70 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.) -- 978767: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=978767 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:apr Version: 1.7.0-3 Severity: normal Tags: sid bookworm User: d...@debian.org Usertags: ftbfs-ac270 [This bug report is not targeted to the upcoming bullseye release] The package fails to build in a test rebuild on at least amd64 with autoconf 2.70, but succeeds to build with autoconf 2.69. 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://qa-logs.debian.net/2020/09/26.ac270/apr_1.7.0-3_unstable_ac270.log The last lines of the build log are at the end of this report. To build with autoconf 2.70, please install the autoconf package from experimental: apt-get -t=experimental install autoconf [...] checking for pwd.h... yes checking for semaphore.h... yes checking for signal.h... yes checking for stdarg.h... yes checking for stddef.h... yes checking for stdio.h... yes checking for stdlib.h... yes checking for string.h... yes checking for strings.h... (cached) yes checking for sysapi.h... no checking for sysgtime.h... no checking for termios.h... yes checking for time.h... yes checking for tpfeq.h... no checking for tpfio.h... no checking for unistd.h... (cached) yes checking for unix.h... no checking for windows.h... (cached) no checking for winsock2.h... no checking for arpa/inet.h... yes checking for kernel/OS.h... (cached) no checking for net/errno.h... no checking for netinet/in.h... yes checking for netinet/sctp.h... yes checking for netinet/sctp_uio.h... no checking for sys/file.h... (cached) yes checking for sys/ioctl.h... yes checking for sys/mman.h... (cached) yes checking for sys/param.h... yes checking for sys/poll.h... yes checking for sys/resource.h... yes checking for sys/select.h... yes checking for sys/sem.h... yes checking for sys/sendfile.h... yes checking for sys/signal.h... yes checking for sys/socket.h... (cached) yes checking for sys/sockio.h... no checking for sys/stat.h... (cached) yes checking for sys/sysctl.h... yes checking for sys/syslimits.h... no checking for sys/time.h... yes checking for sys/types.h... (cached) yes checking for sys/uio.h... yes checking for sys/un.h... yes checking for sys/wait.h... yes checking for netinet/tcp.h... yes checking for h_errno in netdb.h... yes checking for off_t... yes checking for pid_t... yes checking for size_t... (cached) yes checking for uid_t in sys/types.h... yes checking for ssize_t... yes checking for inline... inline checking for an ANSI C-conforming const... yes checking whether setpgrp takes no argument... yes checking for socklen_t... yes checking size of void*... 8 checking size of char... 1 checking size of short... 2 checking size of int... 4 checking size of long... 8 checking size of long long... 8 checking whether int64_t and int use fmt %d... no checking whether int64_t and long use fmt %ld... no checking whether int64_t and long long use fmt %lld... no configure: error: could not determine the string function for int64_t make[1]: *** [debian/rules:84: override_dh_auto_configure] Error 1 make[1]: Leaving directory '/<>' make: *** [debian/rules:20: build] Error 2 dpkg-buildpackage: error: debian/rules build subprocess returned exit status 2 --- End Message --- --- Begin Message --- Source: apr Source-Version: 1.7.0-8 Done: Yadd We believe that the bug you reported is fixed in the latest version of apr, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 978...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Yadd (supplier of updated apr package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Tue, 24 Aug 2021 10:54:34 +0200 Source: apr Architecture: source Version: 1.7.0-8 Distribution: unstable Urgency: medium Maintainer: Debian Apac
Processed: fixed 978888 in 2.13-1
Processing commands for cont...@bugs.debian.org: > fixed 97 2.13-1 Bug #97 [src:powertop] powertop: ftbfs with autoconf 2.70 Marked as fixed in versions powertop/2.13-1. > thanks Stopping processing here. Please contact me if you need assistance. -- 97: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=97 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#978838: marked as done (hubicfuse: ftbfs with autoconf 2.70)
Your message dated Tue, 24 Aug 2021 11:01:29 +0200
with message-id
and subject line Re: Bug#978838: hubicfuse: ftbfs with autoconf 2.70
has caused the Debian Bug report #978838,
regarding hubicfuse: ftbfs with autoconf 2.70
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.)
--
978838: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=978838
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:hubicfuse
Version: 3.0.1-3
Severity: normal
Tags: sid bookworm
User: d...@debian.org
Usertags: ftbfs-ac270
[This bug report is not targeted to the upcoming bullseye release]
The package fails to build in a test rebuild on at least amd64 with
autoconf 2.70, but succeeds to build with autoconf 2.69. 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://qa-logs.debian.net/2020/09/26.ac270/hubicfuse_3.0.1-3_unstable_ac270.log
The last lines of the build log are at the end of this report.
To build with autoconf 2.70, please install the autoconf package from
experimental: apt-get -t=experimental install autoconf
[...]
docdir='${datarootdir}/doc/${PACKAGE_TARNAME}'
dvidir='${docdir}'
exec_prefix='NONE'
host=''
host_alias=''
host_cpu=''
host_os=''
host_vendor=''
htmldir='${docdir}'
includedir='${prefix}/include'
infodir='${prefix}/share/info'
libdir='${prefix}/lib/x86_64-linux-gnu'
libexecdir='${exec_prefix}/libexec'
localedir='${datarootdir}/locale'
localstatedir='/var'
mandir='${prefix}/share/man'
oldincludedir='/usr/include'
pdfdir='${docdir}'
prefix='/usr'
program_transform_name='s,x,x,'
psdir='${docdir}'
runstatedir='/run'
sbindir='${exec_prefix}/sbin'
sharedstatedir='${prefix}/com'
sysconfdir='/etc'
target_alias=''
## --- ##
## confdefs.h. ##
## --- ##
/* confdefs.h */
#define PACKAGE_NAME "hubicfuse"
#define PACKAGE_TARNAME "hubicfuse"
#define PACKAGE_VERSION "3.0.0"
#define PACKAGE_STRING "hubicfuse 3.0.0"
#define PACKAGE_BUGREPORT "Pascal Obry "
#define PACKAGE_URL ""
#define HAVE_SYS_TYPES_H 1
#define HAVE_SYS_STAT_H 1
#define HAVE_STRINGS_H 1
#define HAVE_INTTYPES_H 1
#define HAVE_STDINT_H 1
#define HAVE_UNISTD_H 1
#define HAVE_SYS_TIME_H 1
#define HAVE_STDLIB_H 1
#define HAVE_STRING_H 1
#define STDC_HEADERS 1
#define HAVE_ALLOCA_H 1
#define HAVE_ALLOCA 1
#define HAVE_FCNTL_H 1
#define HAVE_STDINT_H 1
#define HAVE_STDDEF_H 1
#define HAVE_STDLIB_H 1
#define HAVE_STRING_H 1
#define HAVE_STRINGS_H 1
#define HAVE_SYS_TIME_H 1
#define HAVE_UNISTD_H 1
#define HAVE_PTHREAD_H 1
#define HAVE_FUSE_H 1
#define HAVE_CURL_CURL_H 1
#define HAVE_LIBXML_TREE_H 1
#define HAVE_OPENSSL /**/
#define HAVE_STRUCT_STAT_ST_BLOCKS 1
#define HAVE_ST_BLOCKS 1
configure: exit 127
dh_auto_configure: error: ./configure --build=x86_64-linux-gnu --prefix=/usr
--includedir=\${prefix}/include --mandir=\${prefix}/share/man
--infodir=\${prefix}/share/info --sysconfdir=/etc --localstatedir=/var
--disable-option-checking --disable-silent-rules
--libdir=\${prefix}/lib/x86_64-linux-gnu --runstatedir=/run
--disable-maintainer-mode --disable-dependency-tracking returned exit code 127
make: *** [debian/rules:6: binary] Error 25
dpkg-buildpackage: error: debian/rules binary subprocess returned exit status 2
--- End Message ---
--- Begin Message ---
Hi Matthias,
Le 31/12/2020 15:27, Matthias Klose a écrit :
Package: src:hubicfuse
Version: 3.0.1-3
Severity: normal
Tags: sid bookworm
User: d...@debian.org
Usertags: ftbfs-ac270
[This bug report is not targeted to the upcoming bullseye release]
The package fails to build in a test rebuild on at least amd64 with
autoconf 2.70, but succeeds to build with autoconf 2.69. The
severity of this report will be raised before the bookworm release,
so nothing has to be done for the bullseye release.
The package builds successfully in unstable now (with autoconf 2.71).
Regards,
Stephen--- End Message ---
Bug#978774: autossh: ftbfs with autoconf 2.70
Control: tag -1 + unreproducible moreinfo
Control: severity -1 important
Dear Matthias,
Matthias Klose wrote:
> Package: src:autossh
> Version: 1.4g-1
[…]
> The package fails to build in a test rebuild on at least amd64 with
> autoconf 2.70, but succeeds to build with autoconf 2.69.
I'm sorry, but I can't reproduce this:
~/autossh/autossh → apt-cache policy autoconf
autoconf:
Installed: 2.71-2
Candidate: 2.71-2
Version table:
*** 2.71-2 990
990 https://debian.ethz.ch/debian sid/main amd64 Packages
990 https://debian.ethz.ch/debian sid/main i386 Packages
500 https://incoming.debian.org/debian-buildd buildd-unstable/main
amd64 Packages
500 https://incoming.debian.org/debian-buildd buildd-unstable/main i386
Packages
100 /var/lib/dpkg/status
2.69-14 600
600 https://debian.ethz.ch/debian testing/main amd64 Packages
600 https://debian.ethz.ch/debian testing/main i386 Packages
~/autossh/autossh → debuild -j16 -uc -us
dpkg-buildpackage -us -uc -ui -i -j16 -j16
dpkg-buildpackage: info: source package autossh
dpkg-buildpackage: info: source version 1.4g-1
dpkg-buildpackage: info: source distribution unstable
dpkg-buildpackage: info: source changed by Axel Beckert
dpkg-source -i --before-build .
dpkg-buildpackage: info: host architecture amd64
dpkg-source: info: using patch list from debian/patches/series
dpkg-source: info: applying 010_override_cmdline_port.diff
dpkg-source: info: applying 030_manpage_fix.diff
dpkg-source: info: applying 040_manpage_debian.diff
debian/rules clean
dh clean
dh_clean
dpkg-source -i -b .
dpkg-source: info: using source format '3.0 (quilt)'
dpkg-source: info: building autossh using existing ./autossh_1.4g.orig.tar.gz
dpkg-source: info: using patch list from debian/patches/series
dpkg-source: info: building autossh in autossh_1.4g-1.debian.tar.xz
dpkg-source: info: building autossh in autossh_1.4g-1.dsc
debian/rules binary
dh binary
dh_update_autotools_config
dh_autoreconf
configure.ac:8: warning: The macro `AC_CONFIG_HEADER' is obsolete.
configure.ac:8: You should run autoupdate.
./lib/autoconf/status.m4:719: AC_CONFIG_HEADER is expanded from...
configure.ac:8: the top level
configure.ac:19: warning: The macro `AC_HELP_STRING' is obsolete.
configure.ac:19: You should run autoupdate.
./lib/autoconf/general.m4:204: AC_HELP_STRING is expanded from...
configure.ac:19: the top level
configure.ac:39: warning: The macro `AC_HEADER_STDC' is obsolete.
configure.ac:39: You should run autoupdate.
./lib/autoconf/headers.m4:704: AC_HEADER_STDC is expanded from...
configure.ac:39: the top level
configure.ac:50: warning: The macro `AC_HEADER_TIME' is obsolete.
configure.ac:50: You should run autoupdate.
./lib/autoconf/headers.m4:743: AC_HEADER_TIME is expanded from...
configure.ac:50: the top level
configure.ac:134: warning: The macro `AC_TRY_LINK' is obsolete.
configure.ac:134: You should run autoupdate.
./lib/autoconf/general.m4:2920: AC_TRY_LINK is expanded from...
lib/m4sugar/m4sh.m4:692: _AS_IF_ELSE is expanded from...
lib/m4sugar/m4sh.m4:699: AS_IF is expanded from...
./lib/autoconf/general.m4:2249: AC_CACHE_VAL is expanded from...
./lib/autoconf/general.m4:2270: AC_CACHE_CHECK is expanded from...
configure.ac:134: the top level
debian/rules override_dh_auto_configure
make[1]: Entering directory '/home/abe/autossh/autossh'
dh_auto_configure
./configure --build=x86_64-linux-gnu --prefix=/usr
--includedir=\${prefix}/include --mandir=\${prefix}/share/man
--infodir=\${prefix}/share/info --sysconfdir=/etc --localstatedir=/var
--disable-option-checking --disable-silent-rules
--libdir=\${prefix}/lib/x86_64-linux-gnu --runstatedir=/run
--disable-maintainer-mode --disable-dependency-tracking
checking for gcc... gcc
checking whether the C compiler works... yes
checking for C compiler default output file name... a.out
checking for suffix of executables...
checking whether we are cross compiling... no
checking for suffix of object files... o
checking whether the compiler supports GNU C... yes
checking whether gcc accepts -g... yes
checking for gcc option to enable C11 features... none needed
checking for ssh... /usr/bin/ssh
checking for stdio.h... yes
checking for stdlib.h... yes
checking for string.h... yes
checking for inttypes.h... yes
checking for stdint.h... yes
checking for strings.h... yes
checking for sys/stat.h... yes
checking for sys/types.h... yes
checking for unistd.h... yes
checking for sys/time.h... yes
checking for vfork.h... no
checking for sys/select.h... yes
checking for sys/socket.h... yes
checking for grep that handles long lines and -e... /bin/grep
checking for egrep... /bin/grep -E
checking for sys/wait.h that is POSIX.1 compatible... yes
checking for arpa/inet.h... yes
checking for fcntl.h... yes
checking for limits.h... yes
checking for netdb.h... yes
checking for netinet/in.h... yes
checking for paths.h... yes
checking for stdlib.h... (cached) yes
checking for string.h... (cached)
Processed: Re: Bug#978774: autossh: ftbfs with autoconf 2.70
Processing control commands: > tag -1 + unreproducible moreinfo Bug #978774 [src:autossh] autossh: ftbfs with autoconf 2.70 Added tag(s) moreinfo and unreproducible. > severity -1 important Bug #978774 [src:autossh] autossh: ftbfs with autoconf 2.70 Severity set to 'important' from 'serious' -- 978774: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=978774 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#978806: marked as done (eztrace: ftbfs with autoconf 2.70)
Your message dated Tue, 24 Aug 2021 10:42:37 +0200
with message-id <20210824084237.53dtq5ro2untqofr@begin>
and subject line Re: Bug#978806: eztrace: ftbfs with autoconf 2.70
has caused the Debian Bug report #978806,
regarding eztrace: ftbfs with autoconf 2.70
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.)
--
978806: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=978806
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:eztrace
Version: 1.1-8-6
Severity: normal
Tags: sid bookworm
User: d...@debian.org
Usertags: ftbfs-ac270
[This bug report is not targeted to the upcoming bullseye release]
The package fails to build in a test rebuild on at least amd64 with
autoconf 2.70, but succeeds to build with autoconf 2.69. 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://qa-logs.debian.net/2020/09/26.ac270/eztrace_1.1-8-6_unstable_ac270.log
The last lines of the build log are at the end of this report.
To build with autoconf 2.70, please install the autoconf package from
experimental: apt-get -t=experimental install autoconf
[...]
infodir='${prefix}/share/info'
install_sh='${SHELL} /<>/install-sh'
libdir='${prefix}/lib/x86_64-linux-gnu'
libexecdir='${prefix}/lib/x86_64-linux-gnu'
localedir='${datarootdir}/locale'
localstatedir='/var'
mandir='${prefix}/share/man'
mkdir_p='$(MKDIR_P)'
oldincludedir='/usr/include'
pdfdir='${docdir}'
prefix='/usr'
program_transform_name='s,x,x,'
psdir='${docdir}'
runstatedir='${localstatedir}/run'
sbindir='${exec_prefix}/sbin'
sharedstatedir='${prefix}/com'
sysconfdir='/etc'
target_alias=''
## --- ##
## confdefs.h. ##
## --- ##
/* confdefs.h */
#define PACKAGE_NAME "eztrace"
#define PACKAGE_TARNAME "eztrace"
#define PACKAGE_VERSION "1.1-8"
#define PACKAGE_STRING "eztrace 1.1-8"
#define PACKAGE_BUGREPORT "eztrace-de...@lists.gforge.inria.fr"
#define PACKAGE_URL ""
#define PACKAGE "eztrace"
#define VERSION "1.1-8"
#define HAVE_SYS_TYPES_H 1
#define HAVE_SYS_STAT_H 1
#define HAVE_STRINGS_H 1
#define HAVE_INTTYPES_H 1
#define HAVE_STDINT_H 1
#define HAVE_UNISTD_H 1
#define HAVE_STDLIB_H 1
#define HAVE_STRING_H 1
#define STDC_HEADERS 1
#define HAVE_DLFCN_H 1
#define LT_OBJDIR ".libs/"
#define HAVE_LIBDL 1
#define HAVE_LIBM 1
#define HAVE_LIBPTHREAD 1
#define HAVE_LIBZ 1
#define HAVE_DECL_BASENAME 1
#define HAVE_FCNTL_H 1
#define HAVE_LIMITS_H 1
#define HAVE_MALLOC_H 1
#define HAVE_STDINT_H 1
#define HAVE_STDLIB_H 1
#define HAVE_STRING_H 1
#define HAVE_SYS_TIME_H 1
#define HAVE_UNISTD_H 1
#define HAVE_SYS_SYSCALL_H 1
#define HAVE_LIBIBERTY 1
#define HAVE_LIBBFD 1
#define HAVE_MALLOC 0
#define malloc rpl_malloc
#define HAVE_ATEXIT 1
#define HAVE_LIBBFD 1
configure: exit 1
dh_auto_configure: error: cd build-mpich && ../configure
--build=x86_64-linux-gnu --prefix=/usr --includedir=\${prefix}/include
--mandir=\${prefix}/share/man --infodir=\${prefix}/share/info --sysconfdir=/etc
--localstatedir=/var --disable-option-checking --disable-silent-rules
--libdir=\${prefix}/lib/x86_64-linux-gnu
--libexecdir=\${prefix}/lib/x86_64-linux-gnu --disable-maintainer-mode
--disable-dependency-tracking --with-litl=/usr --with-gtg=/usr
--with-starpu=/usr --includedir=/usr/include/x86_64-linux-gnu
--with-mpi-include=/usr/include/mpich --with-mpi-module-name=mpich
--with-mpi-event-id=4 returned exit code 1
make[1]: *** [debian/rules:22: override_dh_auto_configure] Error 25
make[1]: Leaving directory '/<>'
make: *** [debian/rules:19: build] Error 2
dpkg-buildpackage: error: debian/rules build subprocess returned exit status 2
--- End Message ---
--- Begin Message ---
As already mentioned:
Samuel Thibault, le dim. 10 janv. 2021 02:00:33 +0100, a ecrit:
> Control: tags -1 unreproducible moreinfo
> conftest.cpp:43:18: error: invalid conversion from 'void*' to 'char*'
> [-fpermissive]
>43 | char *p = malloc (0);
> | ~~~^~~
> | |
> | void*
>
> but... where is this code actually coming from?? I tried to install
> autoconf/experimental, the eztrace package built fine... and indeed that
> version of autoconf has:
>
> ./autoconf/autoconf.m4f: [[void *p = malloc (0);
>
> not char *. Was the rebuild really made with autoconf 2.70-1?
> (FTR, autoconf 2.69 generates return ! malloc (0); instead)
I cannot reproduce the issue, including with the 2.71-2 package
currently in unstable, thus closing.
Samuel--- End Message ---
Bug#992760: marked as done (ksystemtray: cannot be started, wrong version)
Your message dated Tue, 24 Aug 2021 10:11:58 +0200 with message-id <47441fb5-dbe7-98b3-cac8-3c162bbc1...@rail.eu.org> and subject line Closing bug has caused the Debian Bug report #992760, regarding ksystemtray: cannot be started, wrong version 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.) -- 992760: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=992760 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: plasma-workspace Version: 4:5.21.5-3 Severity: grave Justification: renders package unusable With new plasma 5.21, systemtray does not start with error : kf.plasma.core: "/usr/lib/x86_64-linux-gnu/qt5/plugins/plasma/applets/org.kde.plasma.systemtray.so" : this plugin is compiled against incompatible Plasma version 348928 This build is compatible with 5 .0.0 ( 327680 ) to 5.78.0 ( 347708 ) kf.plasma.core: Applet "org.kde.plasma.systemtray" could not be loaded. Seems wrong version got packaged into plasma-workspace -- System Information: Debian Release: 11.0 APT prefers testing APT policy: (990, 'testing'), (500, 'stable-security'), (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 5.10.0-8-amd64 (SMP w/8 CPU threads) Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages plasma-workspace depends on: ii dbus-user-session [default-dbus-session-bus] 1.12.20-2 ii drkonqi 5.21.5-2 ii frameworkintegration 5.83.0-2 ii gdb 10.1-2 ii init-system-helpers 1.60 ii iso-codes 4.6.0-1 ii kactivitymanagerd 5.21.5-2 ii kded5 5.83.0-2 ii kinit 5.83.0-2 ii kio 5.83.0-2 ii kpackagetool5 5.83.0-2 ii kwin-common 4:5.21.5-2 ii libappstreamqt2 0.14.4-1 ii libc6 2.31-13 ii libcolorcorrect5 4:5.21.5-3 ii libegl1 1.3.2-1 ii libfontconfig12.13.1-4.2 ii libfreetype6 2.10.4+dfsg-1 ii libgcc-s1 10.2.1-6 ii libgl11.3.2-1 ii libgps28 3.22-4 ii libice6 2:1.0.10-1 ii libkf5activities5 5.83.0-2 ii libkf5activitiesstats15.83.0-2 ii libkf5archive55.83.0-2 ii libkf5authcore5 5.83.0-2 ii libkf5baloo5 5.83.0-2 ii libkf5bookmarks5 5.83.0-2 ii libkf5calendarevents5 5.83.0-2 ii libkf5completion5 5.83.0-2 ii libkf5config-bin 5.83.0-2 ii libkf5configcore5 5.83.0-2 ii libkf5configgui5 5.83.0-2 ii libkf5configwidgets5 5.83.0-3 ii libkf5coreaddons5 5.83.0-2 ii libkf5crash5 5.83.0-2 ii libkf5dbusaddons5 5.83.0-2 ii libkf5declarative55.83.0-2 ii libkf5globalaccel-bin 5.83.0-2 ii libkf5globalaccel55.83.0-2 ii libkf5guiaddons5 5.83.0-2 ii libkf5holidays5 1:5.83.0-2 ii libkf5i18n5 5.83.0-3 ii libkf5iconthemes5 5.83.0-2 ii libkf5idletime5 5.83.0-2 ii libkf5itemmodels5 5.83.0-2 ii libkf5jobwidgets5 5.83.0-2 ii libkf5kcmutils5 5.83.0-2 ii libkf5kdelibs4support55.83.0-2 ii libkf5kiocore55.83.0-2 ii libkf5kiofilewidgets5 5.83.0-2 ii libkf5kiogui5 5.83.0-2 ii libkf5kiowidgets5
Bug#992849: gnutls28 arch-only FTBFS: Can't exec "gtkdocize": No such file or directory at /usr/share/autoconf/Autom4te/FileUtils.pm line 293.
Source: gnutls28
Version: 3.7.1-5
Severity: serious
Tags: ftbfs
User: helm...@debian.org
Usertags: rebootstrap
gnutls28 fails to build from source when performing an arch-only build.
A build ends with:
| dh binary-arch --builddirectory=b4deb
|dh_update_autotools_config -a -O--builddirectory=b4deb
|debian/rules override_dh_autoreconf
| make[1]: Entering directory '/<>'
| rm -v `grep -rl gettext-0.20 m4/`
| removed 'm4/po.m4'
| removed 'm4/intlmacosx.m4'
| removed 'm4/gettext.m4'
| dh_autoreconf --verbose -O--builddirectory=b4deb
| find ! -ipath "./debian/*" -a ! \( -path '*/.git/*' -o -path
'*/.hg/*' -o -path '*/.bzr/*' -o -path '*/.svn/*' -o -path '*/CVS/*' \) -a
-type f -exec md5sum {} + -o -type l -printf "symlink %p
| " > debian/autoreconf.before
| grep -q ^XDT_ configure.ac
| autoreconf -f -i
| autopoint: using AM_GNU_GETTEXT_REQUIRE_VERSION instead of
AM_GNU_GETTEXT_VERSION
| Copying file m4/gettext.m4
| Copying file m4/intlmacosx.m4
| Copying file m4/nls.m4
| Copying file m4/po.m4
| Copying file m4/progtest.m4
| Copying file po/Makefile.in.in
| Copying file po/Makevars.template
| aclocal: overwriting 'm4/pkg.m4' with '/usr/share/aclocal/pkg.m4'
| libtoolize: putting auxiliary files in AC_CONFIG_AUX_DIR, 'build-aux'.
| libtoolize: copying file 'build-aux/ltmain.sh'
| libtoolize: putting macros in AC_CONFIG_MACRO_DIRS, 'm4'.
| libtoolize: copying file 'm4/libtool.m4'
| libtoolize: copying file 'm4/ltoptions.m4'
| libtoolize: copying file 'm4/ltsugar.m4'
| libtoolize: copying file 'm4/ltversion.m4'
| libtoolize: copying file 'm4/lt~obsolete.m4'
| Can't exec "gtkdocize": No such file or directory at
/usr/share/autoconf/Autom4te/FileUtils.pm line 293.
| autoreconf: error: gtkdocize failed with exit status: 2
| find ! -ipath "./debian/*" -a ! \( -path '*/.git/*' -o -path
'*/.hg/*' -o -path '*/.bzr/*' -o -path '*/.svn/*' -o -path '*/CVS/*' \) -a
-type f -exec md5sum {} + -o -type l -printf "symlink %p
| " > debian/autoreconf.after
| dh_autoreconf: error: autoreconf -f -i returned exit code 2
| make[1]: *** [debian/rules:50: override_dh_autoreconf] Error 25
| make[1]: Leaving directory '/<>'
| make: *** [debian/rules:127: binary-arch] Error 2
| dpkg-buildpackage: error: debian/rules binary-arch subprocess returned exit
status 2
A full build does not run into this issue, because gtk-doc-tools is
included in Build-Depends-Indep. I suppose it'll have to be moved to
Build-Depends.
This presently breaks architecture bootstrap.
Helmut
Processed: raise severity of autoconf 2.7x issues (package now in unstable)
Processing commands for cont...@bugs.debian.org: > severity 978772 serious Bug #978772 [src:autogen] autogen: ftbfs with autoconf 2.70 Severity set to 'serious' from 'normal' > severity 978763 serious Bug #978763 [src:ample] ample: ftbfs with autoconf 2.70 Severity set to 'serious' from 'normal' > severity 978764 serious Bug #978764 [src:amule] amule: ftbfs with autoconf 2.70 Severity set to 'serious' from 'normal' > severity 978765 serious Bug #978765 [src:apachetop] apachetop: ftbfs with autoconf 2.70 Severity set to 'serious' from 'normal' > severity 978766 serious Bug #978766 [src:aprx] aprx: ftbfs with autoconf 2.70 Severity set to 'serious' from 'normal' > severity 978767 serious Bug #978767 [src:apr] apr: ftbfs with autoconf 2.70 Severity set to 'serious' from 'normal' > severity 978768 serious Bug #978768 [binutils-x86-64-linux-gnu] gold linker crashing with -Wl,--threads Severity set to 'serious' from 'normal' > severity 978769 serious Bug #978769 [src:argus-clients] argus-clients: ftbfs with autoconf 2.70 Severity set to 'serious' from 'normal' > severity 978770 serious Bug #978770 [src:arpalert] arpalert: ftbfs with autoconf 2.70 Severity set to 'serious' from 'normal' > severity 978771 serious Bug #978771 [src:bison++] bison++: ftbfs with autoconf 2.70 Severity set to 'serious' from 'normal' > severity 978773 serious Bug #978773 [src:bmake] bmake: ftbfs with autoconf 2.70 Severity set to 'serious' from 'normal' > severity 978775 serious Bug #978775 [src:brotli] brotli: ftbfs with autoconf 2.70 Severity set to 'serious' from 'normal' > severity 978776 serious Bug #978776 [src:buzztrax] buzztrax: ftbfs with autoconf 2.70 Severity set to 'serious' from 'normal' > severity 978777 serious Bug #978777 [src:boinctui] boinctui: ftbfs with autoconf 2.70 Severity set to 'serious' from 'normal' > severity 978778 serious Bug #978778 [src:canna] canna: ftbfs with autoconf 2.70 Severity set to 'serious' from 'normal' > severity 978780 serious Bug #978780 [src:cdo] cdo: ftbfs with autoconf 2.70 Severity set to 'serious' from 'normal' > severity 978781 serious Bug #978781 [src:chafa] chafa: ftbfs with autoconf 2.70 Severity set to 'serious' from 'normal' > severity 978782 serious Bug #978782 [src:charybdis] charybdis: ftbfs with autoconf 2.70 Severity set to 'serious' from 'normal' > severity 978783 serious Bug #978783 [src:clamav] clamav: ftbfs with autoconf 2.70 Severity set to 'serious' from 'normal' > severity 978784 serious Bug #978784 [src:clustalw] clustalw: ftbfs with autoconf 2.70 Severity set to 'serious' from 'normal' > severity 978785 serious Bug #978785 [src:clp] clp: ftbfs with autoconf 2.70 Severity set to 'serious' from 'normal' > severity 978786 serious Bug #978786 [src:coinor-cbc] coinor-cbc: ftbfs with autoconf 2.70 Severity set to 'serious' from 'normal' > severity 978787 serious Bug #978787 [src:clsync] clsync: ftbfs with autoconf 2.70 Severity set to 'serious' from 'normal' > severity 978788 serious Bug #978788 [src:coinor-osi] coinor-osi: ftbfs with autoconf 2.70 Severity set to 'serious' from 'normal' > severity 978789 serious Bug #978789 [src:coinor-cgl] coinor-cgl: ftbfs with autoconf 2.70 Severity set to 'serious' from 'normal' > severity 978790 serious Bug #978790 [src:coinutils] coinutils: ftbfs with autoconf 2.70 Severity set to 'serious' from 'normal' > severity 978791 serious Bug #978791 [src:coinor-vol] coinor-vol: ftbfs with autoconf 2.70 Severity set to 'serious' from 'normal' > severity 978792 serious Bug #978792 [src:cpm] cpm: ftbfs with autoconf 2.70 Severity set to 'serious' from 'normal' > severity 978793 serious Bug #978793 [src:dnssec-trigger] dnssec-trigger: ftbfs with autoconf 2.70 Severity set to 'serious' from 'normal' > severity 978794 serious Bug #978794 [src:crac] crac: ftbfs with autoconf 2.70 Severity set to 'serious' from 'normal' > severity 978795 serious Bug #978795 [src:dar] dar: ftbfs with autoconf 2.70 Severity set to 'serious' from 'normal' > severity 978796 serious Bug #978796 [src:erlang-p1-eimp] erlang-p1-eimp: ftbfs with autoconf 2.70 Severity set to 'serious' from 'normal' > severity 978797 serious Bug #978797 [src:erlang-p1-pam] erlang-p1-pam: ftbfs with autoconf 2.70 Severity set to 'serious' from 'normal' > severity 978798 serious Bug #978798 [src:dvipng] dvipng: ftbfs with autoconf 2.70 Severity set to 'serious' from 'normal' > severity 978799 serious Bug #978799 [src:erlang-p1-stringprep] erlang-p1-stringprep: ftbfs with autoconf 2.70 Severity set to 'serious' from 'normal' > severity 978800 serious Bug #978800 [src:erlang-p1-sip] erlang-p1-sip: ftbfs with autoconf 2.70 Severity set to 'serious' from 'normal' > severity 978801 serious Bug #978801 [src:erlang-p1-yaml] erlang-p1-yaml: ftbfs with autoconf 2.70 Severity set to 'serious' from 'normal' > severity 978802 serious Bug #978802 [src:erlang-p1-tls] erlang-p1-tls: ftbfs with autoconf 2.70 Severity set to 'serious' from 'normal' > severity 978803 serious Bug #978803 [src:erlang-p1-xml] er
Bug#992760: ksystemtray: cannot be started, wrong version
De : Norbert Preining [mailto:norb...@preining.info] Envoyé : lundi 23 août 2021 à 11:24 UTC+2 Pour : Erwan David , 992...@bugs.debian.org Cc : Debian Kde Objet : Bug#992760: ksystemtray: cannot be started, wrong version Hi Erwan, kf.plasma.core: "/usr/lib/x86_64-linux-gnu/qt5/plugins/plasma/applets/org.kde.plasma.systemtray.so" : this plugin is compiled against incompatible Plasma version 348928 This build is compatible with 5 .0.0 ( 327680 ) to 5.78.0 ( 347708 ) kf.plasma.core: Applet "org.kde.plasma.systemtray" could not be loaded. ii libkf5plasma5 5.78.0-3 The problem is that this packages (and several others) from the frameworks are not updated. I guess we have to introduce a breaks somewhere ... this incompatibility is somehow surprising, because it is not documented in the CMakeList files - at least as far I see... So better wait for a newer version... No, wait for all frameworks being updated ... Best Norbert Thanks, everything is OK now. Now, I just have to close the bug I opened.
Processed: src:yash: fails to migrate to testing for too long
Processing control commands: > close -1 2.51-1 Bug #992846 [src:yash] src:yash: fails to migrate to testing for too long Marked as fixed in versions yash/2.51-1. Bug #992846 [src:yash] src:yash: fails to migrate to testing for too long Marked Bug as done -- 992846: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=992846 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#992846: src:yash: fails to migrate to testing for too long
Source: yash Version: 2.50-1 Severity: serious Control: close -1 2.51-1 Tags: sid bookworm User: release.debian@packages.debian.org Usertags: out-of-sync Dear maintainer(s), As recently announced [1], the Release Team now considers packages that are out-of-sync between testing and unstable for more than 60 days as having a Release Critical bug in testing. Your package src:yash has been trying to migrate for 241 days [2] (of which most were during the freeze). Hence, I am filing this bug. If a package is out of sync between unstable and testing for a longer period, this usually means that bugs in the package in testing cannot be fixed via unstable. Additionally, blocked packages can have impact on other packages, which makes preparing for the release more difficult. Finally, it often exposes issues with the package and/or its (reverse-)dependencies. We expect maintainers to fix issues that hamper the migration of their package in a timely manner. This bug will trigger auto-removal when appropriate. As with all new bugs, there will be at least 30 days before the package is auto-removed. I have immediately closed this bug with the version in unstable, so if that version or a later version migrates, this bug will no longer affect testing. I have also tagged this bug to only affect sid and bullseye, so it doesn't affect (old-)stable. If you believe your package is unable to migrate to testing due to issues beyond your control, don't hesitate to contact the Release Team. Paul [1] https://lists.debian.org/debian-devel-announce/2020/02/msg5.html [2] https://qa.debian.org/excuses.php?package=yash OpenPGP_signature Description: OpenPGP digital signature
Bug#992844: mercurial: FTBFS on s390x (ERROR: test-upgrade-repo.t output changed)
Source: mercurial Version: 5.9-1 Severity: serious Tags: ftbfs >From the log https://buildd.debian.org/status/fetch.php?pkg=mercurial&arch=s390x&ver=5.9-1&stamp=1629766216&raw=0 > --- /<>/tests/test-upgrade-repo.t > +++ /<>/tests/test-upgrade-repo.t.err > @@ -1531,9 +1531,8 @@ >sparserevlog >store >$ hg debugsidedata -c 0 > - 2 sidedata entries > - entry-0001 size 4 > - entry-0002 size 32 > + abort: cannot read from revlog 00changelog-5e69c5d1.sda; expected > 1942585158 bytes from offset 0, data size is 90 > + [50] > > downgrade > > @@ -1552,6 +1551,8 @@ > - changelog > - manifest > > + abort: cannot read from revlog data/foo-1335303a.sda; expected 1942585158 > bytes from offset 0, data size is 0 > + [50] >$ hg debugformat -v >format-variant repo config default >fncache:yesyes yes > @@ -1563,7 +1564,7 @@ >persistent-nodemap: no no no (no-rust !) >persistent-nodemap: yesyes no (rust !) >copies-sdc: no no no > - revlog-v2: no no no > + revlog-v2: yes no no >changelog-v2:no no no >plain-cl-delta: yesyes yes >compression:zlib zlibzlib (no-zstd !) > @@ -1571,14 +1572,16 @@ >compression-level: default default default >$ cat .hg/requires >dotencode > - fncache > + exp-revlogv2.2 > + fncache > + persistent-nodemap (rust !) >generaldelta > - persistent-nodemap (rust !) > - revlog-compression-zstd (zstd !) > - revlogv1 > + revlog-compression-zstd >sparserevlog >store >$ hg debugsidedata -c 0 > + abort: cannot read from revlog 00changelog-5e69c5d1.sda; expected > 1942585158 bytes from offset 0, data size is 90 > + [50] > > upgrade from hgrc > > @@ -1587,20 +1590,8 @@ >> revlogv2=enable-unstable-format-and-corrupt-my-data >> EOF >$ hg debugupgraderepo --run --no-backup --quiet > - upgrade will perform the following actions: > - > - requirements > preserved: dotencode, fncache, generaldelta, sparserevlog, store > (no-zstd !) > - preserved: dotencode, fncache, generaldelta, revlog-compression-zstd, > sparserevlog, store (zstd no-rust !) > preserved: dotencode, fncache, generaldelta, persistent-nodemap, > revlog-compression-zstd, sparserevlog, store (rust !) > - removed: revlogv1 > - added: exp-revlogv2.2 > - > - processed revlogs: > -- all-filelogs > -- changelog > -- manifest > - >$ hg debugformat -v >format-variant repo config default >fncache:yesyes yes > @@ -1628,6 +1619,8 @@ >sparserevlog >store >$ hg debugsidedata -c 0 > + abort: cannot read from revlog 00changelog-5e69c5d1.sda; expected > 1942585158 bytes from offset 0, data size is 90 > + [50] > > Demonstrate that nothing to perform upgrade will still run all the way > through > > > ERROR: test-upgrade-repo.t output changed > !# Ret was: 0 (test-upgrade-repo.t)
Bug#992704: (no subject)
Ack, already looking at it. Unfortunately, there is unlikely to be a quick fix, since upstream has resolved this by removing their existing html/css sanitizer in favour of an alternative one from the jupyterlab source tree, which will require more packaging work before we can utilise it. This is going to be even more of a problem to backport to stable.
Processed: Reassigning, merging and rising severity level of Bugs #979458 and #979459
Processing control commands: > reassign 979458 src:jed 1:0.99.19-8 Bug #979458 [src:jed] jed-common: WARNING: tempfile is deprecated; consider using mktemp instead. Bug #979459 [src:jed] jed: WARNING: tempfile is deprecated; consider using mktemp instead. Ignoring request to reassign bug #979458 to the same package Ignoring request to reassign bug #979459 to the same package Bug #979458 [src:jed] jed-common: WARNING: tempfile is deprecated; consider using mktemp instead. Bug #979459 [src:jed] jed: WARNING: tempfile is deprecated; consider using mktemp instead. Ignoring request to alter found versions of bug #979458 to the same values previously set Ignoring request to alter found versions of bug #979459 to the same values previously set > reassign 979459 src:jed 1:0.99.19-8 Bug #979459 [src:jed] jed: WARNING: tempfile is deprecated; consider using mktemp instead. Bug #979458 [src:jed] jed-common: WARNING: tempfile is deprecated; consider using mktemp instead. Ignoring request to reassign bug #979459 to the same package Ignoring request to reassign bug #979458 to the same package Bug #979459 [src:jed] jed: WARNING: tempfile is deprecated; consider using mktemp instead. Bug #979458 [src:jed] jed-common: WARNING: tempfile is deprecated; consider using mktemp instead. Ignoring request to alter found versions of bug #979459 to the same values previously set Ignoring request to alter found versions of bug #979458 to the same values previously set > severity 979458 serious Bug #979458 [src:jed] jed-common: WARNING: tempfile is deprecated; consider using mktemp instead. Bug #979459 [src:jed] jed: WARNING: tempfile is deprecated; consider using mktemp instead. Ignoring request to change severity of Bug 979458 to the same value. Ignoring request to change severity of Bug 979459 to the same value. > severity 979459 serious Bug #979459 [src:jed] jed: WARNING: tempfile is deprecated; consider using mktemp instead. Bug #979458 [src:jed] jed-common: WARNING: tempfile is deprecated; consider using mktemp instead. Ignoring request to change severity of Bug 979459 to the same value. Ignoring request to change severity of Bug 979458 to the same value. > tags 979458 + patch Bug #979458 [src:jed] jed-common: WARNING: tempfile is deprecated; consider using mktemp instead. Bug #979459 [src:jed] jed: WARNING: tempfile is deprecated; consider using mktemp instead. Ignoring request to alter tags of bug #979458 to the same tags previously set Ignoring request to alter tags of bug #979459 to the same tags previously set > tags 979459 + patch Bug #979459 [src:jed] jed: WARNING: tempfile is deprecated; consider using mktemp instead. Bug #979458 [src:jed] jed-common: WARNING: tempfile is deprecated; consider using mktemp instead. Ignoring request to alter tags of bug #979459 to the same tags previously set Ignoring request to alter tags of bug #979458 to the same tags previously set > merge 979458 979459 Bug #979458 [src:jed] jed-common: WARNING: tempfile is deprecated; consider using mktemp instead. Bug #979459 [src:jed] jed: WARNING: tempfile is deprecated; consider using mktemp instead. Bug #979459 [src:jed] jed: WARNING: tempfile is deprecated; consider using mktemp instead. Merged 979458 979459 -- 979458: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=979458 979459: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=979459 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#979459: Reassigning, merging and rising severity level of Bugs #979458 and #979459
Control: reassign 979458 src:jed 1:0.99.19-8 Control: reassign 979459 src:jed 1:0.99.19-8 Control: severity 979458 serious Control: severity 979459 serious Control: tags 979458 + patch Control: tags 979459 + patch Control: merge 979458 979459 With the upload of version 5.3-1 of the package debianutils, the tempfile command is definitively gone from Debian. This means that installation of the jed, jed-common, and xjed packages does not succeed in bookworm, since their postinst scripts invoke tempfile. I am hereby reassigning the Bugs #979458 and #979459, which were assigned to the binary jed and jed-common packages, to the jed source package. I am also merging this two bug reports and rising their severity level to serious. The trivial patch that fixes the problem is attached to this message. Best, Rafael Laboissière P.S.: Note that removing the jed-common package from a bookworm system also fails because the tempfile command is used in the prerm maintainer script. Here is a simple recipe for doing it successfully: sudo ln -sf /bin/mktemp /usr/bin/tempfile ; sudo apt remove jed-common ; sudo rm /usr/bin/tempfile diff --git a/debian/jed-common.postinst b/debian/jed-common.postinst index 415dbde..96b204a 100644 --- a/debian/jed-common.postinst +++ b/debian/jed-common.postinst @@ -7,7 +7,7 @@ set -e case "$1" in configure) - TEMP=$(tempfile) + TEMP=$(mktemp) printf "Running /usr/share/jed/compile/jed-common..." if ! /usr/share/jed/compile/jed-common install >$TEMP 2>&1; then diff --git a/debian/jed-common.prerm b/debian/jed-common.prerm index 296fd78..ca3e677 100644 --- a/debian/jed-common.prerm +++ b/debian/jed-common.prerm @@ -5,7 +5,7 @@ set -e case "$1" in remove|upgrade|deconfigure) -TEMP=$(tempfile) +TEMP=$(mktemp) printf "Running /usr/share/jed/compile/jed-common..." RET=0 /usr/share/jed/compile/jed-common remove >$TEMP 2>&1 || RET=$? diff --git a/debian/jed.postinst b/debian/jed.postinst index 96bb2f9..f3ca2fa 100644 --- a/debian/jed.postinst +++ b/debian/jed.postinst @@ -12,7 +12,7 @@ case "$1" in --install /usr/bin/jed-script jed-script /usr/bin/jed 50 \ --slave /usr/share/man/man1/jed-script.1.gz jed-script.1.gz /usr/share/man/man1/jed.1.gz; -TEMP=$(tempfile) +TEMP=$(mktemp) RET=0 printf "Updating precompiled files..." run-parts --exit-on-error --arg=install /usr/share/jed/compile/ \ diff --git a/debian/xjed.postinst b/debian/xjed.postinst index 2648220..47ed8a0 100644 --- a/debian/xjed.postinst +++ b/debian/xjed.postinst @@ -12,7 +12,7 @@ case "$1" in --install /usr/bin/jed-script jed-script /usr/bin/xjed 40 \ --slave /usr/share/man/man1/jed-script.1.gz jed-script.1.gz /usr/share/man/man1/xjed.1.gz; -TEMP=$(tempfile) +TEMP=$(mktemp) RET=0 printf "Updating precompiled files..." run-parts --exit-on-error --arg=install /usr/share/jed/compile/ \
Processed: Reassigning, merging and rising severity level of Bugs #979458 and #979459
Processing control commands: > reassign 979458 src:jed 1:0.99.19-8 Bug #979458 [jed-common] jed-common: WARNING: tempfile is deprecated; consider using mktemp instead. Bug reassigned from package 'jed-common' to 'src:jed'. No longer marked as found in versions jed/1:0.99.19-8. Ignoring request to alter fixed versions of bug #979458 to the same values previously set Bug #979458 [src:jed] jed-common: WARNING: tempfile is deprecated; consider using mktemp instead. Marked as found in versions jed/1:0.99.19-8. > reassign 979459 src:jed 1:0.99.19-8 Bug #979459 [jed] jed: WARNING: tempfile is deprecated; consider using mktemp instead. Bug reassigned from package 'jed' to 'src:jed'. No longer marked as found in versions jed/1:0.99.19-8. Ignoring request to alter fixed versions of bug #979459 to the same values previously set Bug #979459 [src:jed] jed: WARNING: tempfile is deprecated; consider using mktemp instead. Marked as found in versions jed/1:0.99.19-8. > severity 979458 serious Bug #979458 [src:jed] jed-common: WARNING: tempfile is deprecated; consider using mktemp instead. Severity set to 'serious' from 'normal' > severity 979459 serious Bug #979459 [src:jed] jed: WARNING: tempfile is deprecated; consider using mktemp instead. Severity set to 'serious' from 'normal' > tags 979458 + patch Bug #979458 [src:jed] jed-common: WARNING: tempfile is deprecated; consider using mktemp instead. Added tag(s) patch. > tags 979459 + patch Bug #979459 [src:jed] jed: WARNING: tempfile is deprecated; consider using mktemp instead. Added tag(s) patch. > merge 979458 979459 Bug #979458 [src:jed] jed-common: WARNING: tempfile is deprecated; consider using mktemp instead. Bug #979459 [src:jed] jed: WARNING: tempfile is deprecated; consider using mktemp instead. Merged 979458 979459 -- 979458: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=979458 979459: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=979459 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
