Bug#982144: php-klogger: Useless in Bullseye
Hi James, On Sat, 06 Feb 2021 15:10:04 -0500 James Valleroy > This is a dependency only for shaarli, which will not be included in Bullseye. We already shipped this package in buster. Do you really think it's useless for users there without shaarli? Is it enough useless to not ship it? Paul PS: not subscribed, CC me if I should read the reply OpenPGP_signature Description: OpenPGP digital signature
Bug#957969: marked as done (xbindkeys-config: ftbfs with GCC-10)
Your message dated Sun, 07 Feb 2021 07:49:28 +
with message-id
and subject line Bug#957969: fixed in xbindkeys-config 0.1.3-2.2
has caused the Debian Bug report #957969,
regarding xbindkeys-config: ftbfs with GCC-10
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
957969: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=957969
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:xbindkeys-config
Version: 0.1.3-2.1
Severity: normal
Tags: sid bullseye
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-10
Please keep this issue open in the bug tracker for the package it
was filed for. If a fix in another package is required, please
file a bug for the other package (or clone), and add a block in this
package. Please keep the issue open until the package can be built in
a follow-up test rebuild.
The package fails to build in a test rebuild on at least amd64 with
gcc-10/g++-10, but succeeds to build with gcc-9/g++-9. The
severity of this report will be raised before the bullseye release,
so nothing has to be done for the buster release.
The full build log can be found at:
http://people.debian.org/~doko/logs/gcc10-20200225/xbindkeys-config_0.1.3-2.1_unstable_gcc10.log
The last lines of the build log are at the end of this report.
To build with GCC 10, either set CC=gcc-10 CXX=g++-10 explicitly,
or install the gcc, g++, gfortran, ... packages from experimental.
apt-get -t=experimental install g++
Common build failures are new warnings resulting in build failures with
-Werror turned on, or new/dropped symbols in Debian symbols files.
For other C/C++ related build failures see the porting guide at
http://gcc.gnu.org/gcc-10/porting_to.html
[...]
from /usr/include/gtk-2.0/gtk/gtk.h:32,
from middle.c:18:
/usr/include/glib-2.0/glib/gtypes.h:551:8: note: declared here
551 | struct _GTimeVal
|^
gcc -Wall -g -O2 `pkg-config --cflags gtk+-2.0` -D_GNU_SOURCE -c speedc.c
In file included from /usr/include/gtk-2.0/gtk/gtkobject.h:37,
from /usr/include/gtk-2.0/gtk/gtkwidget.h:36,
from /usr/include/gtk-2.0/gtk/gtkcontainer.h:35,
from /usr/include/gtk-2.0/gtk/gtkbin.h:35,
from /usr/include/gtk-2.0/gtk/gtkwindow.h:36,
from /usr/include/gtk-2.0/gtk/gtkdialog.h:35,
from /usr/include/gtk-2.0/gtk/gtkaboutdialog.h:32,
from /usr/include/gtk-2.0/gtk/gtk.h:33,
from speedc.c:19:
/usr/include/gtk-2.0/gtk/gtktypeutils.h:236:1: warning: ‘GTypeDebugFlags’ is
deprecated [-Wdeprecated-declarations]
236 | voidgtk_type_init (GTypeDebugFlagsdebug_flags);
| ^~~~
In file included from /usr/include/glib-2.0/gobject/gobject.h:24,
from /usr/include/glib-2.0/gobject/gbinding.h:29,
from /usr/include/glib-2.0/glib-object.h:23,
from /usr/include/glib-2.0/gio/gioenums.h:28,
from /usr/include/glib-2.0/gio/giotypes.h:28,
from /usr/include/glib-2.0/gio/gio.h:26,
from /usr/include/gtk-2.0/gdk/gdkapplaunchcontext.h:30,
from /usr/include/gtk-2.0/gdk/gdk.h:32,
from /usr/include/gtk-2.0/gtk/gtk.h:32,
from speedc.c:19:
/usr/include/glib-2.0/gobject/gtype.h:679:1: note: declared here
679 | {
| ^
In file included from /usr/include/gtk-2.0/gtk/gtktoolitem.h:31,
from /usr/include/gtk-2.0/gtk/gtktoolbutton.h:30,
from /usr/include/gtk-2.0/gtk/gtkmenutoolbutton.h:30,
from /usr/include/gtk-2.0/gtk/gtk.h:126,
from speedc.c:19:
/usr/include/gtk-2.0/gtk/gtktooltips.h:73:3: warning: ‘GTimeVal’ is deprecated:
Use 'GDateTime' instead [-Wdeprecated-declarations]
73 | GTimeVal last_popdown;
| ^~~~
In file included from /usr/include/glib-2.0/glib/galloca.h:32,
from /usr/include/glib-2.0/glib.h:30,
from /usr/include/glib-2.0/gobject/gbinding.h:28,
from /usr/include/glib-2.0/glib-object.h:23,
from /usr/include/glib-2.0/gio/gioenums.h:28,
from /usr/include/glib-2.0/gio/giotypes.h:28,
from /usr/include/glib-2.0/gio/gio.h:26,
from /usr/include/gtk-2.0/gdk/gdkapplaunchcontext.h:30,
from /usr/include/gtk-2.0/gdk/gdk.h:32,
from /usr/include/gtk-2.0/gtk/gtk.h:32,
from speedc.c:19:
/usr/include/glib-2.0/glib/gtypes.h:55
Bug#982177: php8.0: should not be released with bullseye?
Source: php8.0 Severity: serious Justification: not fit for the bullseye release X-Debbugs-Cc: car...@debian.org,debian-rele...@lists.debian.org Hi Ondřej Filling this "blocking bug" for php8.0. In #976811 the conclusion was to remain with php7.4 for bullseye and so for the bugfix and security support. Filling this blocking bug (which should be closed after the bullseye release) to make sure that php8.0 will not be shipped with bullseye. Otherwise i think there will be expectation that php8.0 is additionally as well supported. Filling as well separately/decoupled from the orginal transition bug for php8.0. Do you concur with this approach? Regards, Salvatore
Bug#957495: marked as done (lives: ftbfs with GCC-10)
Your message dated Sun, 07 Feb 2021 07:33:21 + with message-id and subject line Bug#957495: fixed in lives 3.0.2-1.1 has caused the Debian Bug report #957495, regarding lives: ftbfs with GCC-10 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 957495: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=957495 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:lives Version: 3.0.2-1 Severity: normal Tags: sid bullseye User: debian-...@lists.debian.org Usertags: ftbfs-gcc-10 Please keep this issue open in the bug tracker for the package it was filed for. If a fix in another package is required, please file a bug for the other package (or clone), and add a block in this package. Please keep the issue open until the package can be built in a follow-up test rebuild. The package fails to build in a test rebuild on at least amd64 with gcc-10/g++-10, but succeeds to build with gcc-9/g++-9. The severity of this report will be raised before the bullseye release, so nothing has to be done for the buster release. The full build log can be found at: http://people.debian.org/~doko/logs/gcc10-20200225/lives_3.0.2-1_unstable_gcc10.log The last lines of the build log are at the end of this report. To build with GCC 10, either set CC=gcc-10 CXX=g++-10 explicitly, or install the gcc, g++, gfortran, ... packages from experimental. apt-get -t=experimental install g++ Common build failures are new warnings resulting in build failures with -Werror turned on, or new/dropped symbols in Debian symbols files. For other C/C++ related build failures see the porting guide at http://gcc.gnu.org/gcc-10/porting_to.html [...] /usr/bin/ld: giw/giwled.o:./src/./paramspecial.h:77: multiple definition of `mergealign'; widget-helper.o:./src/paramspecial.h:77: first defined here /usr/bin/ld: giw/giwled.o:./src/./events.h:198: multiple definition of `rdet'; widget-helper.o:./src/events.h:198: first defined here /usr/bin/ld: giw/giwled.o:./src/./widget-helper.h:1136: multiple definition of `widget_opts'; widget-helper.o:./src/widget-helper.h:1136: first defined here /usr/bin/ld: giw/giwled.o:./src/./widget-helper-gtk.h:975: multiple definition of `LIVES_STOCK_LABEL_MEDIA_RECORD'; widget-helper.o:./src/widget-helper-gtk.h:975: first defined here /usr/bin/ld: giw/giwled.o:./src/./widget-helper-gtk.h:974: multiple definition of `LIVES_STOCK_LABEL_MEDIA_PAUSE'; widget-helper.o:./src/widget-helper-gtk.h:974: first defined here /usr/bin/ld: giw/giwled.o:./src/./widget-helper-gtk.h:973: multiple definition of `LIVES_STOCK_LABEL_MEDIA_PLAY'; widget-helper.o:./src/widget-helper-gtk.h:973: first defined here /usr/bin/ld: giw/giwled.o:./src/./widget-helper-gtk.h:972: multiple definition of `LIVES_STOCK_LABEL_MEDIA_STOP'; widget-helper.o:./src/widget-helper-gtk.h:972: first defined here /usr/bin/ld: giw/giwled.o:./src/./widget-helper-gtk.h:971: multiple definition of `LIVES_STOCK_LABEL_MEDIA_REWIND'; widget-helper.o:./src/widget-helper-gtk.h:971: first defined here /usr/bin/ld: giw/giwled.o:./src/./widget-helper-gtk.h:970: multiple definition of `LIVES_STOCK_LABEL_MEDIA_FORWARD'; widget-helper.o:./src/widget-helper-gtk.h:970: first defined here /usr/bin/ld: giw/giwled.o:./src/./widget-helper-gtk.h:968: multiple definition of `LIVES_STOCK_LABEL_GO_FORWARD'; widget-helper.o:./src/widget-helper-gtk.h:968: first defined here /usr/bin/ld: giw/giwled.o:./src/./widget-helper-gtk.h:967: multiple definition of `LIVES_STOCK_LABEL_SELECT_ALL'; widget-helper.o:./src/widget-helper-gtk.h:967: first defined here /usr/bin/ld: giw/giwled.o:./src/./widget-helper-gtk.h:966: multiple definition of `LIVES_STOCK_LABEL_DELETE'; widget-helper.o:./src/widget-helper-gtk.h:966: first defined here /usr/bin/ld: giw/giwled.o:./src/./widget-helper-gtk.h:965: multiple definition of `LIVES_STOCK_LABEL_REFRESH'; widget-helper.o:./src/widget-helper-gtk.h:965: first defined here /usr/bin/ld: giw/giwled.o:./src/./widget-helper-gtk.h:964: multiple definition of `LIVES_STOCK_LABEL_REVERT'; widget-helper.o:./src/widget-helper-gtk.h:964: first defined here /usr/bin/ld: giw/giwled.o:./src/./widget-helper-gtk.h:963: multiple definition of `LIVES_STOCK_LABEL_CLOSE'; widget-helper.o:./src/widget-helper-gtk.h:963: first defined here /usr/bin/ld: giw/giwled.o:./src/./widget-helper-gtk.h:962: multiple definition of `LIVES_STOCK_LABEL_APPLY'; widget-helper.o:./src/widget-helper-gtk.h:962: first defined here /usr/bin/ld: giw/giwled.o:./src/./widget-helper-gtk.h:961: multiple definition of `LIVES_STOCK_LABEL_QUIT'; widget-helper.o:./src/
Processed: xbindkeys-config: diff for NMU version 0.1.3-2.2
Processing control commands: > tags 957969 + patch Bug #957969 [src:xbindkeys-config] xbindkeys-config: ftbfs with GCC-10 Added tag(s) patch. -- 957969: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=957969 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#957969: xbindkeys-config: diff for NMU version 0.1.3-2.2
Control: tags 957969 + patch Dear maintainer, I've prepared an NMU for xbindkeys-config (versioned as 0.1.3-2.2). The diff is attached to this message. cu Adrian diff -u xbindkeys-config-0.1.3/debian/changelog xbindkeys-config-0.1.3/debian/changelog --- xbindkeys-config-0.1.3/debian/changelog +++ xbindkeys-config-0.1.3/debian/changelog @@ -1,3 +1,11 @@ +xbindkeys-config (0.1.3-2.2) unstable; urgency=medium + + * Non-maintainer upload. + * Build with -fcommon to workaround FTBFS with gcc 10. +(Closes: #957969) + + -- Adrian Bunk Sun, 07 Feb 2021 09:23:46 +0200 + xbindkeys-config (0.1.3-2.1) unstable; urgency=high * Non-maintainer upload. diff -u xbindkeys-config-0.1.3/debian/rules xbindkeys-config-0.1.3/debian/rules --- xbindkeys-config-0.1.3/debian/rules +++ xbindkeys-config-0.1.3/debian/rules @@ -8,7 +8,7 @@ DEB_HOST_GNU_TYPE ?= $(shell dpkg-architecture -qDEB_HOST_GNU_TYPE) DEB_BUILD_GNU_TYPE ?= $(shell dpkg-architecture -qDEB_BUILD_GNU_TYPE) -CFLAGS = -Wall -g +CFLAGS = -Wall -g -fcommon ifneq (,$(findstring noopt,$(DEB_BUILD_OPTIONS))) CFLAGS += -O0
Bug#977248: marked as done (FTBFS against opencv 4.5.0)
Your message dated Sun, 07 Feb 2021 07:18:24 + with message-id and subject line Bug#977248: fixed in php-facedetect 1.1.0-19-g135c72a-1.1 has caused the Debian Bug report #977248, regarding FTBFS against opencv 4.5.0 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.) -- 977248: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=977248 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: php-facedetect Version: 1.1.0-19-g135c72a-1 Severity: importance Tags: +ftbfs Dear maintainer package php-facedetect FTBFS against opencv 4.5.0 (experimental). --- End Message --- --- Begin Message --- Source: php-facedetect Source-Version: 1.1.0-19-g135c72a-1.1 Done: Adrian Bunk We believe that the bug you reported is fixed in the latest version of php-facedetect, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 977...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Adrian Bunk (supplier of updated php-facedetect 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: Sun, 07 Feb 2021 09:00:56 +0200 Source: php-facedetect Architecture: source Version: 1.1.0-19-g135c72a-1.1 Distribution: unstable Urgency: medium Maintainer: Debian PHP PECL Maintainers Changed-By: Adrian Bunk Closes: 977248 Changes: php-facedetect (1.1.0-19-g135c72a-1.1) unstable; urgency=medium . * Non-maintainer upload. * Add upstream fix for FTBFS with OpenCV 4.5. (Closes: #977248) Checksums-Sha1: 16f2b1e8e80eecf08424ad9fcd75605e6df4eff0 2113 php-facedetect_1.1.0-19-g135c72a-1.1.dsc ff6f6a4878882e3185c73b61b2e3d2d32a6e1e52 3684 php-facedetect_1.1.0-19-g135c72a-1.1.debian.tar.xz Checksums-Sha256: 0d59adefb2507424bc43fb016edaa825bdb917bc635d42c128577eda73d6ee81 2113 php-facedetect_1.1.0-19-g135c72a-1.1.dsc 4b753a24b89455981b2e60ce76c42b9e785d636d63e8a86691bbc668b7e0a173 3684 php-facedetect_1.1.0-19-g135c72a-1.1.debian.tar.xz Files: cf9715c431033222179bfb10953669be 2113 php optional php-facedetect_1.1.0-19-g135c72a-1.1.dsc 3d64682408ce2c9b00971c42b8386cd1 3684 php optional php-facedetect_1.1.0-19-g135c72a-1.1.debian.tar.xz -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEOvp1f6xuoR0v9F3wiNJCh6LYmLEFAmAfkNIACgkQiNJCh6LY mLEvOw//UskuMIEYrulVtZ55KVVR3TQh81Fk6jhYH3iB9vo/KPuDE8m1sYdlnCG1 jLWLiO+dhPTRZHg9SVxERwRy9ZR5z+LZykSKgEtYT0V9B1+1Q384gHKCADG86cnJ baEWGu+xjuSFbfQdoe9+d31XxFtbujpM5YLYaPxrguxH0I5Gxxpiy0JJOmhrZZMS vhVZu2BOmO1CT1K0+RiDsGO2jsUezsqzI5XNDyrnePP2esYgCMcxdGMOx2NO+Jjk aqUXM57dp7dEVuSe1I9eIy4LMZFhE1rrEBcS7/1SUVesX+IIIXWSWnAEzKsf5DqU o7IVlWfovTUQzKMTDGd8HWO3kf5V/vcZ81iaB8nRuv/YqiR7ak32IGjBVcqKX5nt XdgRNdE9aoPybTTQuziLiA1x4V8ut3CKlwKWNvYt+3WSwKU9FTrjgwCJ9Ru7Egqk NB0w8dJbWOhaAUHGwEqLEJuIgrOzPxmPhw6meBV28mtXW73fk4RiQp2ubY4dNOKn aFBkS0rr90Ku72Y+OqzxUHYfxV8QeyD9UXuDS4nt7IWry12CTRRJQX5bK2MqOgP/ U64ZG3bihZsjY/HOjnlYlqHnwlTsZ9HOf68Df5CkBAaPNB7ywYKYeNnhQOl7CsKx iefSXlUcEiGXk4PuLf/z9MCrLB0lWdoPnWtA/qVMygRK0IF+OyE= =7IXF -END PGP SIGNATURE End Message ---
Bug#977248: php-facedetect: diff for NMU version 1.1.0-19-g135c72a-1.1
Dear maintainer, I've prepared an NMU for php-facedetect (versioned as 1.1.0-19-g135c72a-1.1). The diff is attached to this message. cu Adrian diff -Nru php-facedetect-1.1.0-19-g135c72a/debian/changelog php-facedetect-1.1.0-19-g135c72a/debian/changelog --- php-facedetect-1.1.0-19-g135c72a/debian/changelog 2020-03-02 10:37:04.0 +0200 +++ php-facedetect-1.1.0-19-g135c72a/debian/changelog 2021-02-07 09:00:56.0 +0200 @@ -1,3 +1,10 @@ +php-facedetect (1.1.0-19-g135c72a-1.1) unstable; urgency=medium + + * Non-maintainer upload. + * Add upstream fix for FTBFS with OpenCV 4.5. (Closes: #977248) + + -- Adrian Bunk Sun, 07 Feb 2021 09:00:56 +0200 + php-facedetect (1.1.0-19-g135c72a-1) unstable; urgency=medium * New upstream version 1.1.0-19-g135c72a (used git describe to gen vernum) diff -Nru php-facedetect-1.1.0-19-g135c72a/debian/patches/0001-Fix-includedir-for-opencv_cxxflags.patch php-facedetect-1.1.0-19-g135c72a/debian/patches/0001-Fix-includedir-for-opencv_cxxflags.patch --- php-facedetect-1.1.0-19-g135c72a/debian/patches/0001-Fix-includedir-for-opencv_cxxflags.patch 1970-01-01 02:00:00.0 +0200 +++ php-facedetect-1.1.0-19-g135c72a/debian/patches/0001-Fix-includedir-for-opencv_cxxflags.patch 2021-02-07 09:00:37.0 +0200 @@ -0,0 +1,30 @@ +From e2d7613993e69c660f417194843773a33dfd31ae Mon Sep 17 00:00:00 2001 +From: Nicolas Chauvet +Date: Tue, 20 Oct 2020 16:32:51 +0200 +Subject: Fix includedir for opencv_cxxflags + +I'm not sure why includedir_new comes from but if needed it's possible +to use: + --variable=includedir_new --variable=includedir + +Signed-off-by: Nicolas Chauvet +--- + config.m4 | 2 +- + 1 file changed, 1 insertion(+), 1 deletion(-) + +diff --git a/config.m4 b/config.m4 +index 21703cd..133d27e 100644 +--- a/config.m4 b/config.m4 +@@ -17,7 +17,7 @@ if test "$PHP_FACEDETECT" != "no"; then + PHP_ADD_INCLUDE($CV_INCLUDE) + else + if test -x "$PKG_CONFIG" && $PKG_CONFIG --exists opencv4; then +- CV_INCLUDE=`$PKG_CONFIG opencv4 --variable=includedir_new` ++ CV_INCLUDE=`$PKG_CONFIG opencv4 --variable=includedir` + CV_LIBRARY=`$PKG_CONFIG opencv4 --libs` + CV_VERSION=`$PKG_CONFIG opencv4 --modversion` + if $PKG_CONFIG opencv4 --atleast-version=3.0.0 ; then +-- +2.20.1 + diff -Nru php-facedetect-1.1.0-19-g135c72a/debian/patches/series php-facedetect-1.1.0-19-g135c72a/debian/patches/series --- php-facedetect-1.1.0-19-g135c72a/debian/patches/series 1970-01-01 02:00:00.0 +0200 +++ php-facedetect-1.1.0-19-g135c72a/debian/patches/series 2021-02-07 09:00:56.0 +0200 @@ -0,0 +1 @@ +0001-Fix-includedir-for-opencv_cxxflags.patch
Processed: lives: diff for NMU version 3.0.2-1.1
Processing control commands: > tags 957495 + patch Bug #957495 [src:lives] lives: ftbfs with GCC-10 Added tag(s) patch. -- 957495: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=957495 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#957495: lives: diff for NMU version 3.0.2-1.1
Control: tags 957495 + patch Dear maintainer, I've prepared an NMU for lives (versioned as 3.0.2-1.1). The diff is attached to this message. cu Adrian diff -Nru lives-3.0.2/debian/changelog lives-3.0.2/debian/changelog --- lives-3.0.2/debian/changelog 2020-02-15 21:40:29.0 +0200 +++ lives-3.0.2/debian/changelog 2021-02-07 09:13:26.0 +0200 @@ -1,3 +1,11 @@ +lives (3.0.2-1.1) unstable; urgency=medium + + * Non-maintainer upload. + * Build with -fcommon to workaround FTBFS with gcc 10. +(Closes: #957495) + + -- Adrian Bunk Sun, 07 Feb 2021 09:13:26 +0200 + lives (3.0.2-1) unstable; urgency=medium * Team upload. diff -Nru lives-3.0.2/debian/rules lives-3.0.2/debian/rules --- lives-3.0.2/debian/rules 2019-08-11 17:51:26.0 +0300 +++ lives-3.0.2/debian/rules 2021-02-07 09:13:26.0 +0200 @@ -3,6 +3,8 @@ include /usr/share/dpkg/architecture.mk include /usr/share/dpkg/pkg-info.mk +export DEB_CFLAGS_MAINT_APPEND = -fcommon + %: dh $@ --with=python3
Bug#966680: src:acpica-unix: fails to migrate to testing for too long: FTBFS on s390x
Hi Al, On Wed, 9 Dec 2020 22:08:25 +0100 Paul Gevers wrote: > > In case you didn't notice; s390x is fixed now. The package FTBFS on > > armhf and mips64el. > > Friendly ping. Friendly ping again. We're now in the first phase of the freeze for bullseye. It would be good, for all I guess, if your work since October 2019 gets included in bullseye. bullseye currently has 20190509-1. Paul OpenPGP_signature Description: OpenPGP digital signature
Bug#939712: marked as done (performous-composer: missing Depends on libqt5multimedia5-plugins)
Your message dated Sun, 07 Feb 2021 07:03:34 + with message-id and subject line Bug#939712: fixed in performous-composer 2.0+20181009-gitbeeea23-2.1 has caused the Debian Bug report #939712, regarding performous-composer: missing Depends on libqt5multimedia5-plugins 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.) -- 939712: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=939712 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: performous-composer Version: 2.0+20181009-gitbeeea23-1 Severity: serious Justification: dependencies incorrect https://github.com/performous/composer/issues/36 ↓ https://stackoverflow.com/a/22046880/2171120 -- System Information: Debian Release: bullseye/sid APT prefers buildd-unstable APT policy: (500, 'buildd-unstable'), (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.2.0-2-amd64 (SMP w/2 CPU cores) Locale: LANG=C, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE=C (charmap=UTF-8) Shell: /bin/sh linked to /bin/lksh Init: sysvinit (via /sbin/init) Versions of packages performous-composer depends on: ii libavcodec58 7:4.1.4-1+b2 ii libavformat58 7:4.1.4-1+b2 ii libavutil567:4.1.4-1+b2 ii libc6 2.28-10 ii libgcc11:9.2.1-7 ii libqt5core5a 5.11.3+dfsg1-4 ii libqt5gui5 5.11.3+dfsg1-4 ii libqt5multimedia5 5.11.3-2 ii libqt5network5 5.11.3+dfsg1-4 ii libqt5widgets5 5.11.3+dfsg1-4 ii libqt5xml5 5.11.3+dfsg1-4 ii libstdc++6 9.2.1-7 ii libswresample3 7:4.1.4-1+b2 ii libswscale57:4.1.4-1+b2 performous-composer recommends no packages. performous-composer suggests no packages. -- no debconf information --- End Message --- --- Begin Message --- Source: performous-composer Source-Version: 2.0+20181009-gitbeeea23-2.1 Done: Adrian Bunk We believe that the bug you reported is fixed in the latest version of performous-composer, 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 939...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Adrian Bunk (supplier of updated performous-composer 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: Sun, 07 Feb 2021 08:46:46 +0200 Source: performous-composer Architecture: source Version: 2.0+20181009-gitbeeea23-2.1 Distribution: unstable Urgency: medium Maintainer: Debian Games Team Changed-By: Adrian Bunk Closes: 939340 939712 Changes: performous-composer (2.0+20181009-gitbeeea23-2.1) unstable; urgency=medium . * Non-maintainer upload. * Add the missing dependency on libqt5multimedia5-plugins. (Closes: #939712) * Fix a spelling error in the package description. (Closes: #939340) Checksums-Sha1: 8b5a752a0a7c79dfbcb116e07456d3f3c3b227f0 2278 performous-composer_2.0+20181009-gitbeeea23-2.1.dsc 760d2130dec9b44c381c453daec99dc0fa3600f3 2420 performous-composer_2.0+20181009-gitbeeea23-2.1.debian.tar.xz Checksums-Sha256: 847b5d63e8e897d9a3acc152cd513d866a38c6a51aaf0e8556ea5153b1912eb6 2278 performous-composer_2.0+20181009-gitbeeea23-2.1.dsc 7f81b2145ca044181adb8d48c3ccd3bed07d8af8618c0307871c0851e7942905 2420 performous-composer_2.0+20181009-gitbeeea23-2.1.debian.tar.xz Files: 8903828e913c6dab82ea9b439ba1acd8 2278 games optional performous-composer_2.0+20181009-gitbeeea23-2.1.dsc 6e677de474163ab080d31c6067c770a5 2420 games optional performous-composer_2.0+20181009-gitbeeea23-2.1.debian.tar.xz -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEOvp1f6xuoR0v9F3wiNJCh6LYmLEFAmAfjaIACgkQiNJCh6LY mLFl1RAAyoIJ2VgxJZF+zl2Q5VujzA1z8nU7Rf3s+Qt8zRKfQ0mppOcahmtOEyBk 5cETKKNLNaNtoHOmMYFXhjUblikLXJ9BW8wWS3NyqOxFHLeZA5kArMtGT7P4pKWV KSPv77sN4KjHL2zHpx1SBOdrg3g4smOGbGFU4qx0l5DtMu+ZkQOAyEHt9FQK/k6a 3zOU5bwAlUjT1AJVbZddfqtwHdUgGRqWzZZAJvheWnTMvW25lX5wGppGjCpTJyJ1 rAr9U+JTpmy49tP8fTV73ZFT5A8+VcMBWstu4nOnL7juvQuYfO/8ABPVqwRi1/19 3JjEMjvEMJn1FmXNhEbRR4/wj4skRL8OQvClM4i3RQgu65JrO8H/WLqsrg1f97uA oLA8KvVIc8Uem9CnVXtW5a2RPn7yZRzUebY+vDcf6VYpcsLxnGeRVySBywmwKTwl K+zCzIL3j+VUaPQ/PMjaq9jD8i+l1fz5HaWROGUMx4lbqQgSQRYtIRfscku1/H2T EbB5PXoAfXChcaRDwJUVuIdqbx
Bug#939712: performous-composer: diff for NMU version 2.0+20181009-gitbeeea23-2.1
Control: tags 939340 + patch
Control: tags 939712 + patch
Dear maintainer,
I've prepared an NMU for performous-composer (versioned as
2.0+20181009-gitbeeea23-2.1). The diff is attached to this message.
cu
Adrian
diff -Nru performous-composer-2.0+20181009-gitbeeea23/debian/changelog performous-composer-2.0+20181009-gitbeeea23/debian/changelog
--- performous-composer-2.0+20181009-gitbeeea23/debian/changelog 2019-09-10 07:07:37.0 +0300
+++ performous-composer-2.0+20181009-gitbeeea23/debian/changelog 2021-02-07 08:46:46.0 +0200
@@ -1,3 +1,13 @@
+performous-composer (2.0+20181009-gitbeeea23-2.1) unstable; urgency=medium
+
+ * Non-maintainer upload.
+ * Add the missing dependency on libqt5multimedia5-plugins.
+(Closes: #939712)
+ * Fix a spelling error in the package description.
+(Closes: #939340)
+
+ -- Adrian Bunk Sun, 07 Feb 2021 08:46:46 +0200
+
performous-composer (2.0+20181009-gitbeeea23-2) unstable; urgency=medium
* Team upload.
diff -Nru performous-composer-2.0+20181009-gitbeeea23/debian/control performous-composer-2.0+20181009-gitbeeea23/debian/control
--- performous-composer-2.0+20181009-gitbeeea23/debian/control 2019-09-10 06:54:41.0 +0300
+++ performous-composer-2.0+20181009-gitbeeea23/debian/control 2021-02-07 08:46:46.0 +0200
@@ -24,6 +24,7 @@
Depends:
${misc:Depends},
${shlibs:Depends},
+ libqt5multimedia5-plugins,
Enhances:
performous,
Description: song editor for creating (and converting) notes for music games
@@ -34,7 +35,7 @@
.
Key features of Composer include:
.
- * Song pitch analysis based on the esteemed algorithms from Perfomous.
+ * Song pitch analysis based on the esteemed algorithms from Performous.
* Zoomable interface to quickly get an overview or doing very precise timing.
* Possibility to synthesize the notes to get a feel of their "sound".
* Import/export in various formats including:
Processed: performous-composer: diff for NMU version 2.0+20181009-gitbeeea23-2.1
Processing control commands: > tags 939340 + patch Bug #939340 [performous-composer] performous-composer: spelling error in long description: Perfomous → Performous Ignoring request to alter tags of bug #939340 to the same tags previously set > tags 939712 + patch Bug #939712 [performous-composer] performous-composer: missing Depends on libqt5multimedia5-plugins Ignoring request to alter tags of bug #939712 to the same tags previously set -- 939340: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=939340 939712: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=939712 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: performous-composer: diff for NMU version 2.0+20181009-gitbeeea23-2.1
Processing control commands: > tags 939340 + patch Bug #939340 [performous-composer] performous-composer: spelling error in long description: Perfomous → Performous Added tag(s) patch. > tags 939712 + patch Bug #939712 [performous-composer] performous-composer: missing Depends on libqt5multimedia5-plugins Added tag(s) patch. -- 939340: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=939340 939712: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=939712 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#957326: marked as done (gwc: ftbfs with GCC-10)
Your message dated Sun, 07 Feb 2021 06:48:19 + with message-id and subject line Bug#957326: fixed in gwc 0.22.04-1.1 has caused the Debian Bug report #957326, regarding gwc: ftbfs with GCC-10 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 957326: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=957326 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:gwc Version: 0.22.04-1 Severity: normal Tags: sid bullseye User: debian-...@lists.debian.org Usertags: ftbfs-gcc-10 Please keep this issue open in the bug tracker for the package it was filed for. If a fix in another package is required, please file a bug for the other package (or clone), and add a block in this package. Please keep the issue open until the package can be built in a follow-up test rebuild. The package fails to build in a test rebuild on at least amd64 with gcc-10/g++-10, but succeeds to build with gcc-9/g++-9. The severity of this report will be raised before the bullseye release, so nothing has to be done for the buster release. The full build log can be found at: http://people.debian.org/~doko/logs/gcc10-20200225/gwc_0.22.04-1_unstable_gcc10.log The last lines of the build log are at the end of this report. To build with GCC 10, either set CC=gcc-10 CXX=g++-10 explicitly, or install the gcc, g++, gfortran, ... packages from experimental. apt-get -t=experimental install g++ Common build failures are new warnings resulting in build failures with -Werror turned on, or new/dropped symbols in Debian symbols files. For other C/C++ related build failures see the porting guide at http://gcc.gnu.org/gcc-10/porting_to.html [...] biquad.c: In function ‘filter_dialog’: biquad.c:343:9: warning: variable ‘dclose’ set but not used [-Wunused-but-set-variable] 343 | int dclose = 0 ; | ^~ gcc tap_reverb_file_io.o tap_reverb.o reverb.o dialog.o gwc.o audio_device.o audio_edit.o audio_util.o gtkled.o gtkledbar.o preferences.o drawing.o amplify.o denoise.o undo.o declick.o sample_block.o decrackle.o stat.o dethunk.o i0.o i1.o chbevl.o markers.o encode.o soundfile.o pinknoise.o biquad.o -Wl,-z,relro -Wl,-z,now -Wl,--as-needed meschach.a -lgtk-x11-2.0 -lgdk-x11-2.0 -lpangocairo-1.0 -latk-1.0 -lcairo -lgdk_pixbuf-2.0 -lgio-2.0 -lpangoft2-1.0 -lpango-1.0 -lgobject-2.0 -lfontconfig -lfreetype -lglib-2.0 -lsndfile -lasound -lfftw3-lm -o gtk-wave-cleaner /usr/bin/ld: dialog.o:./gwc.h:193: multiple definition of `main_window'; reverb.o:./gwc.h:193: first defined here /usr/bin/ld: dialog.o:./gwc.h:189: multiple definition of `CLIPBOARD_FILE'; reverb.o:./gwc.h:189: first defined here /usr/bin/ld: dialog.o:./gwc.h:188: multiple definition of `tmpdir'; reverb.o:./gwc.h:188: first defined here /usr/bin/ld: gwc.o:./gwc.h:193: multiple definition of `main_window'; reverb.o:./gwc.h:193: first defined here /usr/bin/ld: gwc.o:./gwc.h:188: multiple definition of `tmpdir'; reverb.o:./gwc.h:188: first defined here /usr/bin/ld: gwc.o:./gwc.h:189: multiple definition of `CLIPBOARD_FILE'; reverb.o:./gwc.h:189: first defined here /usr/bin/ld: audio_device.o:./gwc.h:193: multiple definition of `main_window'; reverb.o:./gwc.h:193: first defined here /usr/bin/ld: audio_device.o:./gwc.h:189: multiple definition of `CLIPBOARD_FILE'; reverb.o:./gwc.h:189: first defined here /usr/bin/ld: audio_device.o:./gwc.h:188: multiple definition of `tmpdir'; reverb.o:./gwc.h:188: first defined here /usr/bin/ld: audio_edit.o:./gwc.h:189: multiple definition of `CLIPBOARD_FILE'; reverb.o:./gwc.h:189: first defined here /usr/bin/ld: audio_edit.o:./gwc.h:193: multiple definition of `main_window'; reverb.o:./gwc.h:193: first defined here /usr/bin/ld: audio_edit.o:./gwc.h:188: multiple definition of `tmpdir'; reverb.o:./gwc.h:188: first defined here /usr/bin/ld: audio_util.o:./gwc.h:193: multiple definition of `main_window'; reverb.o:./gwc.h:193: first defined here /usr/bin/ld: audio_util.o:./gwc.h:189: multiple definition of `CLIPBOARD_FILE'; reverb.o:./gwc.h:189: first defined here /usr/bin/ld: audio_util.o:./gwc.h:188: multiple definition of `tmpdir'; reverb.o:./gwc.h:188: first defined here /usr/bin/ld: preferences.o:./gwc.h:193: multiple definition of `main_window'; reverb.o:./gwc.h:193: first defined here /usr/bin/ld: preferences.o:./gwc.h:189: multiple definition of `CLIPBOARD_FILE'; reverb.o:./gwc.h:189: first defined here /usr/bin/ld: preferences.o:./gwc.h:188: multiple definition of `tmpdir'; reverb.o:./gwc.h:188: first defined here /usr/bin/ld: drawing.o:./gwc.h:193: multiple definition of `main
Bug#957326: gwc: diff for NMU version 0.22.04-1.1
Dear maintainer, I've prepared an NMU for gwc (versioned as 0.22.04-1.1). The diff is attached to this message. cu Adrian diff -Nru gwc-0.22.04/debian/changelog gwc-0.22.04/debian/changelog --- gwc-0.22.04/debian/changelog 2019-09-15 19:49:52.0 +0300 +++ gwc-0.22.04/debian/changelog 2021-02-07 08:35:50.0 +0200 @@ -1,3 +1,10 @@ +gwc (0.22.04-1.1) unstable; urgency=medium + + * Non-maintainer upload. + * Add fix from Logan Rosen for FTBFS with gcc 10. (Closes: #957326) + + -- Adrian Bunk Sun, 07 Feb 2021 08:35:50 +0200 + gwc (0.22.04-1) unstable; urgency=medium * Team upload. diff -Nru gwc-0.22.04/debian/patches/gcc-10.patch gwc-0.22.04/debian/patches/gcc-10.patch --- gwc-0.22.04/debian/patches/gcc-10.patch 1970-01-01 02:00:00.0 +0200 +++ gwc-0.22.04/debian/patches/gcc-10.patch 2021-02-07 08:35:45.0 +0200 @@ -0,0 +1,50 @@ +--- a/gwc.h b/gwc.h +@@ -185,12 +185,12 @@ + int ready ; + } DENOISE_DATA ; + +-gchar *tmpdir; +-gchar *CLIPBOARD_FILE ; ++extern gchar *tmpdir; ++extern gchar *CLIPBOARD_FILE ; + + void print_denoise(char *header, struct denoise_prefs *pDnprefs) ; + +-GtkWidget *main_window; ++extern GtkWidget *main_window; + + GtkWidget *add_number_entry_with_label(char *entry_text, char *label_text, GtkWidget *table, int row) ; + GtkWidget *add_number_entry_with_label_int(int value, char *label_text, GtkWidget *table, int row) ; +--- a/gwc.c b/gwc.c +@@ -84,6 +84,7 @@ + GtkWidget *hscrollbar; + GtkWidget *detect_only_widget; + GtkWidget *leave_click_marks_widget; ++GtkWidget *main_window; + + GtkWidget *l_file_time; + GtkWidget *l_file_samples; +@@ -147,6 +148,8 @@ + gchar wave_filename[PATH_MAX+1]; + gchar last_filename[PATH_MAX+1]; + gchar *file_extension; ++gchar *tmpdir; ++gchar *CLIPBOARD_FILE; + + long markers[MAX_MARKERS]; + long n_markers = 0; +--- a/markers.c b/markers.c +@@ -39,8 +39,8 @@ + + /* The file selection widget and the string to store the chosen filename */ + +-GtkWidget *file_selector; +-gchar *selected_filename; ++extern GtkWidget *file_selector; ++extern gchar *selected_filename; + gchar save_cdrdao_toc_filename[PATH_MAX+1]; + extern long num_song_markers, song_markers[] ; + extern gchar wave_filename[] ; diff -Nru gwc-0.22.04/debian/patches/series gwc-0.22.04/debian/patches/series --- gwc-0.22.04/debian/patches/series 2019-09-15 19:47:29.0 +0300 +++ gwc-0.22.04/debian/patches/series 2021-02-07 08:35:45.0 +0200 @@ -1 +1,2 @@ 02-no_extra_docs.patch +gcc-10.patch
Bug#982173: mpich breaks bagel autopkgtest: Internal error
Source: mpich, bagel Control: found -1 mpich/3.4.1-2 Control: found -1 bagel/1.2.2-1 Severity: serious Tags: sid bullseye X-Debbugs-CC: debian...@lists.debian.org User: debian...@lists.debian.org Usertags: breaks needs-update Dear maintainer(s), With a recent upload of mpich the autopkgtest of bagel fails in testing when that autopkgtest is run with the binary packages of mpich from unstable. It passes when run with only packages from testing. In tabular form: passfail mpich from testing3.4.1-2 bagel from testing1.2.2-1 all others from testingfrom testing I copied some of the output at the bottom of this report. Currently this regression is blocking the migration of mpich 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=mpich https://ci.debian.net/data/autopkgtest/testing/amd64/b/bagel/10269200/log.gz running test case 'hf_sto3g_fci_dist'... Assertion failed in file ./src/mpid/ch4/netmod/include/../ofi/ofi_impl.h at line 316: MPIDI_OFI_global.max_order_war != 0 /lib/x86_64-linux-gnu/libmpich.so.12(MPL_backtrace_show+0x35) [0x7ff101b7a5c5] /lib/x86_64-linux-gnu/libmpich.so.12(+0x3d41f4) [0x7ff101af11f4] /lib/x86_64-linux-gnu/libmpich.so.12(+0x2df929) [0x7ff1019fc929] /lib/x86_64-linux-gnu/libmpich.so.12(MPI_Raccumulate+0xaf3) [0x7ff1019fdb43] BAGEL(+0x1175449) [0x55bce38aa449] BAGEL(+0x117556a) [0x55bce38aa56a] BAGEL(+0x2dad12e) [0x55bce54e212e] BAGEL(+0x2da77e7) [0x55bce54dc7e7] BAGEL(+0x1287971) [0x55bce39bc971] BAGEL(+0x128cb48) [0x55bce39c1b48] BAGEL(+0x7984da) [0x55bce2ecd4da] BAGEL(+0x6d00cb) [0x55bce2e050cb] BAGEL(+0x6d0600) [0x55bce2e05600] BAGEL(+0x630a79) [0x55bce2d65a79] /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xea) [0x7ff101251d0a] BAGEL(+0x6cd3ca) [0x55bce2e023ca] Abort(1) on node 0: Internal error Abort(806445583) on node 0 (rank 0 in comm 0): Fatal error in PMPI_Finalize: Other MPI error, error stack: PMPI_Finalize(189)..: MPI_Finalize failed PMPI_Finalize(149)..: MPID_Finalize(702)..: MPIDI_OFI_mpi_finalize_hook(827): destroy_vni_context(1079)...: OFI domain close failed (ofi_init.c:1079:destroy_vni_context:Device or resource busy) FAILED. OpenPGP_signature Description: OpenPGP digital signature
Processed: mpich breaks bagel autopkgtest: Internal error
Processing control commands: > found -1 mpich/3.4.1-2 Bug #982173 [src:mpich, src:bagel] mpich breaks bagel autopkgtest: Internal error Marked as found in versions mpich/3.4.1-2. > found -1 bagel/1.2.2-1 Bug #982173 [src:mpich, src:bagel] mpich breaks bagel autopkgtest: Internal error Marked as found in versions bagel/1.2.2-1. -- 982173: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=982173 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: libint2 breaks cp2k autopkgtest
Processing control commands: > found -1 libint2/2.6.0-11 Bug #982172 [src:libint2, src:cp2k] libint2 breaks cp2k autopkgtest Marked as found in versions libint2/2.6.0-11. > found -1 cp2k/8.1-5 Bug #982172 [src:libint2, src:cp2k] libint2 breaks cp2k autopkgtest Marked as found in versions cp2k/8.1-5. -- 982172: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=982172 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#982172: libint2 breaks cp2k autopkgtest
Source: libint2, cp2k Control: found -1 libint2/2.6.0-11 Control: found -1 cp2k/8.1-5 Severity: serious Tags: sid bullseye X-Debbugs-CC: debian...@lists.debian.org User: debian...@lists.debian.org Usertags: breaks needs-update Dear maintainer(s), With a recent upload of libint2 the autopkgtest of cp2k fails in testing when that autopkgtest is run with the binary packages of libint2 from unstable. It passes when run with only packages from testing. In tabular form: passfail libint2from testing2.6.0-11 cp2k from testing8.1-5 all others from testingfrom testing Normally I copy some of the output at the bottom of this report, however, the report is unconventional and I didn't spot the actual failure. Please follow the link for the full report. Currently this regression is blocking the migration of libint2 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=libint2 https://ci.debian.net/data/autopkgtest/testing/amd64/c/cp2k/10281856/log.gz OpenPGP_signature Description: OpenPGP digital signature
Bug#849025: marked as done (jalview: FTBFS: error: cannot find symbol EnumCallback)
Your message dated Sun, 07 Feb 2021 06:33:21 +
with message-id
and subject line Bug#849025: fixed in jalview 2.11.1.3+dfsg2-1
has caused the Debian Bug report #849025,
regarding jalview: FTBFS: error: cannot find symbol EnumCallback
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.)
--
849025: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=849025
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: jalview
Version: 2.7.dfsg-5
Severity: serious
Justification: fails to build from source
User: reproducible-bui...@lists.alioth.debian.org
Usertags: ftbfs
X-Debbugs-Cc: reproducible-b...@lists.alioth.debian.org
Dear Maintainer,
jalview fails to build from source in unstable/amd64:
[…]
[javac] «BUILDDIR»/src/jalview/ext/jmol/JalviewJmolBinding.java:952:
error: cannot find symbol
[javac] public void notifyCallback(EnumCallback type, Object[] data)
[javac] ^
[javac] symbol: class EnumCallback
[javac] location: class JalviewJmolBinding
[javac] «BUILDDIR»/src/jalview/ext/jmol/JalviewJmolBinding.java:1006:
error: cannot find symbol
[javac] public boolean notifyEnabled(EnumCallback callbackPick)
[javac]^
[javac] symbol: class EnumCallback
[javac] location: class JalviewJmolBinding
[javac] «BUILDDIR»/src/jalview/ws/EnfinEnvision2OneWay.java:67: error:
package com.lowagie.text.html does not exist
[javac] import com.lowagie.text.html.HtmlEncoder;
[javac] ^
[javac] «BUILDDIR»/src/jalview/ws/rest/params/SeqVector.java:37: error:
cannot find symbol
[javac] import org.jmol.util.ArrayUtil;
[javac] ^
[javac] symbol: class ArrayUtil
[javac] location: package org.jmol.util
[javac] «BUILDDIR»/src/jalview/appletgui/AppletJmol.java:32: error:
cannot find symbol
[javac] import org.jmol.viewer.JmolConstants;
[javac] ^
[javac] symbol: class JmolConstants
[javac] location: package org.jmol.viewer
[javac] «BUILDDIR»/src/jalview/appletgui/AppletJmolBinding.java:30:
error: cannot find symbol
[javac] import org.jmol.popup.JmolPopup;
[javac] ^
[javac] symbol: class JmolPopup
[javac] location: package org.jmol.popup
[javac] «BUILDDIR»/src/jalview/bin/Jalview.java:756: warning: non-varargs
call of varargs method with inexact argument type for last parameter;
[javac] gbcons = gbindingc.getConstructor(null);
[javac] ^
[javac] cast to Class for a varargs call
[javac] cast to Class[] for a non-varargs call and to suppress this
warning
[javac] «BUILDDIR»/src/jalview/bin/Jalview.java:757: warning: non-varargs
call of varargs method with inexact argument type for last parameter;
[javac] gbinding = gbcons.newInstance(null);
[javac] ^
[javac] cast to Object for a varargs call
[javac] cast to Object[] for a non-varargs call and to suppress this
warning
[javac] «BUILDDIR»/src/jalview/gui/Desktop.java:2177: warning:
non-varargs call of varargs method with inexact argument type for last
parameter;
[javac] Constructor gccons = gcClass.getConstructor(null);
[javac] ^
[javac] cast to Class for a varargs call
[javac] cast to Class[] for a non-varargs call and to suppress this
warning
[javac] «BUILDDIR»/src/jalview/gui/Desktop.java:2181: warning:
non-varargs call of varargs method with inexact argument type for last
parameter;
[javac] java.lang.reflect.Method run = gcClass.getMethod("run",
null);
[javac] ^
[javac] cast to Class for a varargs call
[javac] cast to Class[] for a non-varargs call and to suppress this
warning
[javac] «BUILDDIR»/src/jalview/gui/Desktop.java:2182: warning:
non-varargs call of varargs method with inexact argument type for last
parameter;
[javac] Object gc = gccons.newInstance(null);
[javac] ^
[javac] cast to Object for a varargs call
[javac] cast to Object[] for a non-varargs call and to suppress this
warning
[javac] «BUILDDIR»/src/jalview/gui/Desktop.java:2185: warning:
non-varargs call of varargs method w
Processed: libint breaks psi4 autopkgtest: 'str' object is not callable; perhaps you missed a comma?
Processing control commands: > found -1 libint/1.2.1-4 Bug #982171 [src:libint, src:psi4] libint breaks psi4 autopkgtest: 'str' object is not callable; perhaps you missed a comma? Marked as found in versions libint/1.2.1-4. > found -1 psi4/1:1.3.2-3 Bug #982171 [src:libint, src:psi4] libint breaks psi4 autopkgtest: 'str' object is not callable; perhaps you missed a comma? Marked as found in versions psi4/1:1.3.2-3. -- 982171: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=982171 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#982171: libint breaks psi4 autopkgtest: 'str' object is not callable; perhaps you missed a comma?
Source: libint, psi4 Control: found -1 libint/1.2.1-4 Control: found -1 psi4/1:1.3.2-3 Severity: serious Tags: sid bullseye X-Debbugs-CC: debian...@lists.debian.org User: debian...@lists.debian.org Usertags: breaks needs-update Dear maintainer(s), With a recent upload of libint the autopkgtest of psi4 fails in testing when that autopkgtest is run with the binary packages of libint from unstable. It passes when run with only packages from testing. In tabular form: passfail libint from testing1.2.1-4 psi4 from testing1:1.3.2-3 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 libint 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=libint https://ci.debian.net/data/autopkgtest/testing/amd64/p/psi4/10275876/log.gz autopkgtest [03:33:29]: test testsuite.sh: [--- Running test psi4numpy/rhf-hessian... 'str' object is not callable; perhaps you missed a comma? 'str' object is not callable; perhaps you missed a comma? 'str' object is not callable; perhaps you missed a comma? 'str' object is not callable; perhaps you missed a comma? "is" with a literal. Did you mean "=="? FAILED LOG: 2021-02-06 03:33 Running test psi4numpy/rhf... 'str' object is not callable; perhaps you missed a comma? 'str' object is not callable; perhaps you missed a comma? 'str' object is not callable; perhaps you missed a comma? 'str' object is not callable; perhaps you missed a comma? "is" with a literal. Did you mean "=="? FAILED LOG: 2021-02-06 03:33 Running test python/energy... 'str' object is not callable; perhaps you missed a comma? 'str' object is not callable; perhaps you missed a comma? 'str' object is not callable; perhaps you missed a comma? 'str' object is not callable; perhaps you missed a comma? "is" with a literal. Did you mean "=="? FAILED LOG: 2021-02-06 03:33 Running test chemps2/scf-n2... 'str' object is not callable; perhaps you missed a comma? 'str' object is not callable; perhaps you missed a comma? 'str' object is not callable; perhaps you missed a comma? 'str' object is not callable; perhaps you missed a comma? "is" with a literal. Did you mean "=="? FAILED LOG: 2021-02-06 03:33 Skipping test pasture-ccsorttransqt2/ccenergy_driver Running test dfmp2-1... 'str' object is not callable; perhaps you missed a comma? 'str' object is not callable; perhaps you missed a comma? 'str' object is not callable; perhaps you missed a comma? 'str' object is not callable; perhaps you missed a comma? "is" with a literal. Did you mean "=="? FAILED LOG: 2021-02-06 03:33 Running test cc1... 'str' object is not callable; perhaps you missed a comma? 'str' object is not callable; perhaps you missed a comma? 'str' object is not callable; perhaps you missed a comma? 'str' object is not callable; perhaps you missed a comma? "is" with a literal. Did you mean "=="? FAILED LOG: 2021-02-06 03:33 Running test casscf-sp... 'str' object is not callable; perhaps you missed a comma? 'str' object is not callable; perhaps you missed a comma? 'str' object is not callable; perhaps you missed a comma? 'str' object is not callable; perhaps you missed a comma? "is" with a literal. Did you mean "=="? FAILED LOG: 2021-02-06 03:33 Skipping test mrcc/ccsdt Skipping test dftd3/energy Skipping test dkh/molpro-2order Skipping test gcp/hf3c Running test tu1-h2o-energy... 'str' object is not callable; perhaps you missed a comma? 'str' object is not callable; perhaps you missed a comma? 'str' object is not callable; perhaps you missed a comma? 'str' object is not callable; perhaps you missed a comma? "is" with a literal. Did you mean "=="? FAILED LOG: 2021-02-06 03:33 Running test json/schema-1-gradient... 'str' object is not callable; perhaps you missed a comma? 'str' object is not callable; perhaps you missed a comma? 'str' object is not callable; perhaps you missed a comma? 'str' object is not callable; perhaps you missed a comma? "is" with a literal. Did you mean "=="? FAILED LOG: 2021-02-06 03:33 Skipping test v2rdm_casscf/v2rdm3 Running test erd/scf5... 'str' object is not callable; perhaps you missed a comma? 'str' object is not callable; perhaps you missed a comma? 'str' object is not callable; perhaps you missed a comma? 'str' object is not callable; perhaps you missed a comma? "is" with a literal. Did you mean "=="? FAILED LOG: 2021-02-06 03:33 Case Study Test of all SCF algorithms/spin-degeneracies: Singlet-Triplet O2 -Nuclear Repulsion: Triplet nuclear repulsion energy...
Bug#982170: libassuan: autopkgtest regression: undefined reference to symbol 'gpg_strerror@@GPG_ERROR_1.0'
Source: libassuan Version: 2.5.4-1 X-Debbugs-CC: debian...@lists.debian.org Severity: serious User: debian...@lists.debian.org Usertags: regression Dear maintainer(s), With a recent upload of libassuan the autopkgtest of libassuan fails in testing when that autopkgtest is run with the binary packages of libassuan from unstable. It passes when run with only packages from testing. In tabular form: passfail libassuan from testing2.5.4-1 all others from testingfrom testing I copied some of the output at the bottom of this report. Currently this regression is blocking the migration to testing [1]. Can you please investigate the situation and fix it? More information about this bug and the reason for filing it can be found on https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation Paul [1] https://qa.debian.org/excuses.php?package=libassuan https://ci.debian.net/data/autopkgtest/testing/amd64/liba/libassuan/10277023/log.gz autopkgtest [05:10:59]: test build: [--- /usr/bin/ld: /tmp/cc0iMBm7.o: undefined reference to symbol 'gpg_strerror@@GPG_ERROR_1.0' /usr/bin/ld: /lib/x86_64-linux-gnu/libgpg-error.so.0: error adding symbols: DSO missing from command line collect2: error: ld returned 1 exit status autopkgtest [05:11:00]: test build: ---] autopkgtest [05:11:00]: test build: - - - - - - - - - - results - - - - - - - - - - buildFAIL non-zero exit status 1 autopkgtest [05:11:00]: test build: - - - - - - - - - - stderr - - - - - - - - - - /usr/bin/ld: /tmp/cc0iMBm7.o: undefined reference to symbol 'gpg_strerror@@GPG_ERROR_1.0' /usr/bin/ld: /lib/x86_64-linux-gnu/libgpg-error.so.0: error adding symbols: DSO missing from command line collect2: error: ld returned 1 exit status OpenPGP_signature Description: OpenPGP digital signature
Bug#982169: biomaj3-process: autopkgtest failure: No module named 'biomaj3_process'
Source: biomaj3-process Version: 3.0.16-1 X-Debbugs-CC: debian...@lists.debian.org Severity: serious User: debian...@lists.debian.org Usertags: fails-always Dear maintainer(s), You recently added an autopkgtest to your package biomaj3-process, great. However, it fails. Currently this failure is blocking the migration to testing [1]. Can you please investigate the situation and fix it? I copied some of the output at the bottom of this report. It seems that autodep8 doesn't work out of the box for you. It has the possibility to specify your module name, see $(man autodep8). 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=biomaj3-process https://ci.debian.net/data/autopkgtest/testing/amd64/b/biomaj3-process/9770961/log.gz autopkgtest [15:25:29]: test autodep8-python3: set -e ; for py in $(py3versions -r 2>/dev/null) ; do cd "$AUTOPKGTEST_TMP" ; echo "Testing with $py:" ; $py -c "import biomaj3_process; print(biomaj3_process)" ; done autopkgtest [15:25:29]: test autodep8-python3: [--- Testing with python3.9: Traceback (most recent call last): File "", line 1, in ModuleNotFoundError: No module named 'biomaj3_process' autopkgtest [15:25:30]: test autodep8-python3: ---] OpenPGP_signature Description: OpenPGP digital signature
Bug#982168: biomaj3-daemon: autopkgtest failure: No module named 'biomaj3_daemon'
Source: biomaj3-daemon Version: 3.0.22-1 X-Debbugs-CC: debian...@lists.debian.org Severity: serious User: debian...@lists.debian.org Usertags: fails-always Dear maintainer(s), You recently added an autopkgtest to your package biomaj3-daemon, great. However, it fails. Currently this failure is blocking the migration to testing [1]. Can you please investigate the situation and fix it? I copied some of the output at the bottom of this report. It seems that autodep8 doesn't work out of the box for you. It has the possibility to specify your module name, see $(man autodep8). 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=biomaj3-daemon https://ci.debian.net/data/autopkgtest/testing/amd64/b/biomaj3-daemon/9770957/log.gz autopkgtest [15:25:14]: test autodep8-python3: set -e ; for py in $(py3versions -r 2>/dev/null) ; do cd "$AUTOPKGTEST_TMP" ; echo "Testing with $py:" ; $py -c "import biomaj3_daemon; print(biomaj3_daemon)" ; done autopkgtest [15:25:14]: test autodep8-python3: [--- Testing with python3.9: Traceback (most recent call last): File "", line 1, in ModuleNotFoundError: No module named 'biomaj3_daemon' autopkgtest [15:25:16]: test autodep8-python3: ---] OpenPGP_signature Description: OpenPGP digital signature
Bug#977765: [Pkg-fonts-devel] Bug#977765: src:gsfonts: package superseded by fonts-urw-base35
Hi Jonas, On Mon, 21 Dec 2020 15:35:04 +0100 Jonas Smedegaard wrote: > > > Setting severity to serious, as this package is not fit for release. > > > > Why do you think the package is not fit for release? Because it did > > not have a maintainer upload for the last 10 years? It is static font > > data, after all? Or because it does not follow a naming convention > > that isn't even Debian policy? > > Because two font packages provide same font - i.e. registers same font > id with fontconfig. And what are the consequences of that? Please assume I have no clue how fontconfig works at all. > Feel free to lower severity or repurpose as a wishlist request to > document what is notable about this font over fonts-urw-base35, or > whatever - I have no strong attachment to this issue, it can linger for > another 10 years without me noticing much... Your comment suggest that we should ignore this issue for bullseye. There's quite some work to get it removed, it's late in the release cycle. Paul PS: please CC me on replies so I see the response quickly elbrus@coccia:~$ dak rm --no-action -R --suite testing gsfonts Will remove the following packages from testing: gsfonts | 1:8.11+urwcyr1.0.7~pre44-4.5 | source, all Maintainer: Masayuki Hatta (mhatta) --- Reason --- -- Checking reverse dependencies... # Broken Depends: abiword: abiword dvd-slideshow: dvd-slideshow gnumeric: gnumeric grace: grace gsfonts-x11: gsfonts-x11 hylafax: hylafax-client ipe: ipe popplerkit.framework: libpopplerkit0 ruby-gruff: ruby-gruff ruby-mojo-magick: ruby-mojo-magick webmagick: webmagick # Broken Build-Depends: aspectc++: gsfonts axiom: gsfonts debian-edu-doc: gsfonts drawtiming: gsfonts fricas: gsfonts gloox: gsfonts gprolog: gsfonts graphicsmagick: gsfonts gri: gsfonts groff: gsfonts gscan2pdf: gsfonts hylafax: gsfonts imagemagick: gsfonts ipe: gsfonts libforms: gsfonts lilypond: gsfonts routino: gsfonts ruby-gruff: gsfonts ruby-mojo-magick: gsfonts ruby-rmagick: gsfonts scalable-cyrfonts: gsfonts sdcc: gsfonts Dependency problem found. OpenPGP_signature Description: OpenPGP digital signature
Bug#963363: marked as done (libsrtp2: FTBFS: running cipher self-test for AES-128 GCM using NSS...failed with error code 8)
Your message dated Sun, 07 Feb 2021 03:33:38 + with message-id and subject line Bug#963363: fixed in libsrtp2 2.3.0-5 has caused the Debian Bug report #963363, regarding libsrtp2: FTBFS: running cipher self-test for AES-128 GCM using NSS...failed with error code 8 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.) -- 963363: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=963363 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: libsrtp2 Version: 2.3.0-4 Severity: serious Justification: FTBFS on amd64 Tags: bullseye sid ftbfs Usertags: ftbfs-20200620 ftbfs-bullseye Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[1]: Entering directory '/<>' > Build done. Please run '/usr/bin/make runtest' to run self tests. > running libsrtp2 test applications... > crypto/test/cipher_driver -v > cipher test driver > David A. McGrew > Cisco Systems, Inc. > running cipher self-test for null cipher...passed > running cipher self-test for AES-128 counter mode using NSS...passed > running cipher self-test for AES-256 counter mode using NSS...passed > running cipher self-test for AES-192 counter mode using NSS...passed > running cipher self-test for AES-128 GCM using NSS...failed with error code 8 > make[1]: *** [Makefile:47: runtest] Error 8 The full build log is available from: http://qa-logs.debian.net/2020/06/20/libsrtp2_2.3.0-4_unstable.log A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! About the archive rebuild: The rebuild was done on EC2 VM instances from Amazon Web Services, using a clean, minimal and up-to-date chroot. Every failed build was retried once to eliminate random failures. --- End Message --- --- Begin Message --- Source: libsrtp2 Source-Version: 2.3.0-5 Done: Jonas Smedegaard We believe that the bug you reported is fixed in the latest version of libsrtp2, 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 963...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Jonas Smedegaard (supplier of updated libsrtp2 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: Sun, 07 Feb 2021 04:11:43 +0100 Source: libsrtp2 Architecture: source Version: 2.3.0-5 Distribution: unstable Urgency: medium Maintainer: Debian VoIP Team Changed-By: Jonas Smedegaard Closes: 963363 Changes: libsrtp2 (2.3.0-5) unstable; urgency=medium . * add patch cherry-picked upstream to support running against nss >= 3.52; closes: bug#963363, thanks to Juhani Numminen Checksums-Sha1: a867f1cc5c3e3e95f6762c405d63ab7a0cdf09fa 2221 libsrtp2_2.3.0-5.dsc 690ca4662cd135ede6f9cbca91e0d2f9f0bdc143 16456 libsrtp2_2.3.0-5.debian.tar.xz aa023aae228848ddf589420e44f804370a28f6be 8072 libsrtp2_2.3.0-5_amd64.buildinfo Checksums-Sha256: 689ad8fa67d3a048fd11b556a51d1c5a8fb695298e1618614443659748668105 2221 libsrtp2_2.3.0-5.dsc 46a4cf460a9c006793520aa790cb4fd0ad48152c1aa3390d114924a835ef9c99 16456 libsrtp2_2.3.0-5.debian.tar.xz 5e98c56c20e90250cfbec226da6c1dd7e03b748edf9af592a4968de674f7ae8e 8072 libsrtp2_2.3.0-5_amd64.buildinfo Files: 70da9fd51159943c8175fb94ec3bea97 2221 libs optional libsrtp2_2.3.0-5.dsc 4a0f83b2885bcf5e18ab30c731019d6a 16456 libs optional libsrtp2_2.3.0-5.debian.tar.xz 018be6cacf25f7924871945e2d84fb18 8072 libs optional libsrtp2_2.3.0-5_amd64.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEn+Ppw2aRpp/1PMaELHwxRsGgASEFAmAfW/kACgkQLHwxRsGg ASGu/Q//YcpDUhb56aLFR/S+y7ps9Joe2cTFYQF5JVhvPNk+ai4Pnwt7ZVTcwa/7 cboxK4RYVgT/8/W5amc7WMe22qeh5ikRGS3LUEXaJeqw5xdIsfWQiA32PQ2wYcW7 /dWwAS297Su7svg7Z4pA5E1w0vqNRKt3WUFw+EKYCNI5z6zC/d0d6+3+h7aH4+yd nYp7p+iautIh71+uHF5uaHtGKuScUG49/m1OL16P9BpSJ81qWrO+18MfKSLLDG19 vmI2JTbXFJHq7Sa9XpMpts22aRB4h0vkw9Qi78u8/1nIjH94Wq6Tr8UE+redRnwN XOduuxSqDpNxhx3YgKymFTv70Q5Y3ZoupyIpXPsTG9k4bL+3eg5yXM5B42tk2D4P 093cffxZpRSpRwqNATaGeKxUSnixXrLvmCwm7u6SKXMRIaUEb83p4xaA5JaHkhtl v10l/fuzVCK5VJAAce5SdTzzgxQK4un7kzObmGw0tivW+b/z9NE9iW6LTGSHWQZj bfOHQF2OiCtX1uozqZX0OKofjNmGL0DYJd14OMGbZC1nrae0GjfL9UTqukVafrFi WUx
Bug#982059: manpages-de,psmisc: File conflict between psmisc and manpages-de: '/usr/share/man/de/man1/fuser.1.gz
Yep, psmisc now ships with translated packages. So fuser.1 and friends are in two places. So manpages-de has fuser, killall, peekfd, pslog and pstree but not prstat. There is also manpages-nl and manpages-pl but neither of those languages are in psmisc. psmisc has ft, pt_BR, ru and uk and the corresponding manpage-* packages don't have the psmisc man pages. So the psmisc overlap is only with manpages-de. We can tackle this a few ways, but Debian should only ship one! As luck would have it, both manpages-de[1] and the upstream issue for psmisc[2] come the same person, Mario Blättermann who I have CC'ed. Hi Mario, as upstream for both sets of translations, what's your future plans? Keep both? Ship only one or prefer one over the other? I've happy enough to either remove the clashing de manpages or put a Replaces line in to override it, but I'd like to line it up with what upstream for both is planning on doing. - Craig 1: https://salsa.debian.org/debian/manpages-l10n/-/blob/master/debian/copyright#L1890 2: https://gitlab.com/psmisc/psmisc/-/issues/22 On Sat, 6 Feb 2021 at 16:48, Axel Beckert wrote: > Package: manpages-de,psmisc > Severity: serious > Version: manpages-de/4.2.0-1 > Version: psmisc/23.4-1 > > Hi, > > there seems a new file conflict between manpages-de (uploaded in > December) and the most recent psmisc upload: > > As I first run into it: > > Unpacking psmisc (23.4-1) over (23.3-1) ... > dpkg: error processing archive > /tmp/apt-dpkg-install-IViNm3/17-psmisc_23.4-1_i386.deb (--unpack): > trying to overwrite '/usr/share/man/de/man1/fuser.1.gz', which is also in > package manpages-de 4.2.0-1 > > But of course also happens the opposite way: > > Unpacking manpages-de (4.2.0-1) ... > dpkg: error processing archive > /var/cache/apt/archives/manpages-de_4.2.0-1_all.deb (--unpack): > trying to overwrite '/usr/share/man/de/man1/fuser.1.gz', which is also in > package psmisc 23.4-1 > > Please decide which package should ship that man page. > > -- System Information: > Debian Release: bullseye/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-1-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 >
Bug#982144: php-klogger: Useless in Bullseye
Package: php-klogger Version: 1.2.1-4 Severity: serious X-Debbugs-Cc: jvalle...@mailbox.org -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 This is a dependency only for shaarli, which will not be included in Bullseye. - -- System Information: Debian Release: bullseye/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.10.0-2-amd64 (SMP w/4 CPU threads) Kernel taint flags: TAINT_WARN, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages php-klogger depends on: ii php-common 2:76 ii php-psr-log 1.1.3-2 php-klogger recommends no packages. php-klogger suggests no packages. - -- no debconf information -BEGIN PGP SIGNATURE- iQJKBAEBCgA0FiEEfWrbdQ+RCFWJSEvmd8DHXntlCAgFAmAe95wWHGp2YWxsZXJv eUBtYWlsYm94Lm9yZwAKCRB3wMdee2UICBQjD/9si/XKAxhW+g70D28ayVKLiQMR 7TFgUUEQiSHsKxnALQYMajzqu6/j33RPOPwoVfSkd1/Dl/BMMZAqXDfytJ3b7Hm8 HYluRt4uB8eoW1XvD8wDzgDZh84CSFcvD6FjpM9xhOhVf58uVl0UEFQlEs+HOUS9 rkd9dvheNSk+kjSqqy4ikpwOdbYxms/2Vz2NFXT4IGHVax0MIw0fD4S6twOuaJzc R5PkffPBnmF+YEAPqwG41K55VC51PG/SCpMNucm3UZxclGb2tTQY5i0v/2vJsMMB 9DrJE3uzTR3oBsTnBlPlaHvAAo3Mkg2uIvXJj9choXt9eyUoVd7N/8PLpX20uRyg fQgD9u9wLRlHKQKLIeL81mwPVUycv6dqR3rUhNNbR2NlHxSNpqFdJCkUt/zsNR7V rtDsMTOqDfFFSOwHlU5rgblfMkEpmqBT/NANH+m/zeTIk/TAkf3U5AtODoxrt6SI FBvGHapQj3rc6tUj4tNW/YSZywBR8BNUK7wcGZOhb5C2LFrvNSX7940uPIHyocuL TohbLDCW5zEc7DvGKqGKd6YoNyO7ooVReyG48jiFl7EJD8/kxrpQQJYYIw588Jif VI7ABoJ0uum+DkGFaeBy/W2K1hdXUff4LjKZVWXdP0aZv5YXj8xyOa0W2LI4nwVN 3N1l0gAb89wb9xwjkQ== =0qBA -END PGP SIGNATURE-
Bug#982155: PXE network booting looks broken to me: the initramfs doesn't attempt to wget my filesystem.squashfs
Source: live-boot Version: 1:20210122 Severity: grave Hi, Since the last upload of live-build and live-boot (ie: 1:20210122) to unstable the live image my script creates cannot be booted. After the network interfaces are up, the image is supposed to wget the filesystem.squashfs, but it does nothing, sitting idle and not even giving me a timeout or something. Also, I wonder how come live-build / live-boot were uploaded 14 days from the freeze, when no other upload were done during the development cycle of Bullseye. There's clearly room for improvement here. If anything has changed in the interface of live-build (which would be breaking me), then I'd like to find out what. If you do know how to help, please do! Also, did you try doing PXE booting of a live image with this version 1:20210122 ? Maybe you should... :) Thanks for maintaining live-build, Cheers, Thomas Goirand (zigo)
Bug#982154: trocla FTBFS: test failure
Source: trocla Version: 0.2.3-1 Severity: serious Tags: ftbfs https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/trocla.html ... Failures: 1) Trocla::Format::X509 x509 selfsigned is able to create self signed cert without being a ca by default Failure/Error: expect(verify(cert,cert)).to be false expected false got true # ./spec/trocla/formats/x509_spec.rb:47:in `block (3 levels) in ' Finished in 3 minutes 0 seconds (files took 3.63 seconds to load) 168 examples, 1 failure Failed examples: rspec ./spec/trocla/formats/x509_spec.rb:34 # Trocla::Format::X509 x509 selfsigned is able to create self signed cert without being a ca by default /usr/bin/ruby2.7 -I/usr/share/rubygems-integration/all/gems/rspec-support-3.9.3/lib:/usr/share/rubygems-integration/all/gems/rspec-core-3.9.2/lib /usr/share/rubygems-integration/all/gems/rspec-core-3.9.2/exe/rspec --pattern ./spec/\*\*/\*_spec.rb failed ERROR: Test "ruby2.7" failed. Exiting. dh_auto_install: error: dh_ruby --install /build/1st/trocla-0.2.3/debian/trocla returned exit code 1 make[1]: *** [debian/rules:21: override_dh_auto_install] Error 25
Processed: netdiag: diff for NMU version 1.2-1.1
Processing control commands: > tags 957596 + pending Bug #957596 [src:netdiag] netdiag: ftbfs with GCC-10 Added tag(s) pending. -- 957596: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=957596 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#957596: netdiag: diff for NMU version 1.2-1.1
Control: tags 957596 + pending
Dear maintainer,
I've prepared an NMU for netdiag (versioned as 1.2-1.1) and uploaded
it to DELAYED/1. Please feel free to tell me if I should cancel it.
cu
Adrian
diff -u netdiag-1.2/debian/changelog netdiag-1.2/debian/changelog
--- netdiag-1.2/debian/changelog
+++ netdiag-1.2/debian/changelog
@@ -1,3 +1,13 @@
+netdiag (1.2-1.1) unstable; urgency=medium
+
+ * Non-maintainer upload.
+ * Add FTBFS fixes from Logan Rosen:
+- Fix FTBFS with GCC 10.
+- Rename pcap_init() to traf_pcap_init() to avoid conflict with libpcap.
+(Closes: #957596)
+
+ -- Adrian Bunk Sun, 07 Feb 2021 00:40:50 +0200
+
netdiag (1.2-1) unstable; urgency=medium
* New upstream version for netwatch. (Closes: #804791)
diff -u netdiag-1.2/debian/patches/series netdiag-1.2/debian/patches/series
--- netdiag-1.2/debian/patches/series
+++ netdiag-1.2/debian/patches/series
@@ -8,0 +9,2 @@
+gcc-10.diff
+pcap_init.diff
only in patch2:
unchanged:
--- netdiag-1.2.orig/debian/patches/gcc-10.diff
+++ netdiag-1.2/debian/patches/gcc-10.diff
@@ -0,0 +1,39 @@
+--- a/netwatch-1.3.1-2/netwatch.c
b/netwatch-1.3.1-2/netwatch.c
+@@ -151,6 +151,10 @@
+ #include "netresolv.h"
+ #include "netwatch.h"
+
++struct port_info *tcp_port_types[TCPHASH];
++
++struct port_info *udp_port_types[UDPHASH];
++
+ extern int errno;
+
+ #define MAXFILENAME 256
+--- a/netwatch-1.3.1-2/netwatch.h
b/netwatch-1.3.1-2/netwatch.h
+@@ -209,10 +209,10 @@
+ };
+
+ #define TCPHASH 1786
+-struct port_info *tcp_port_types[TCPHASH];
++EXTERN_DEF struct port_info *tcp_port_types[TCPHASH];
+
+ #define UDPHASH 1786
+-struct port_info *udp_port_types[UDPHASH];
++EXTERN_DEF struct port_info *udp_port_types[UDPHASH];
+
+ int hashport( int port, int hash);
+ void initlist(struct port_info *first[], int hash);
+--- a/netwatch-1.3.1-2/dispdata.c
b/netwatch-1.3.1-2/dispdata.c
+@@ -178,7 +178,7 @@
+ extern int simchange;
+ extern int simfwdir;
+ extern int simarr[8];
+-char *simfmt;
++extern char *simfmt;
+ extern int iseth;
+ extern int nw_logall;
+ extern char nw_allname[256];
only in patch2:
unchanged:
--- netdiag-1.2.orig/debian/patches/pcap_init.diff
+++ netdiag-1.2/debian/patches/pcap_init.diff
@@ -0,0 +1,29 @@
+--- a/trafshow-5.2.3/trafshow.c
b/trafshow-5.2.3/trafshow.c
+@@ -58,7 +58,7 @@
+ static void vers();
+ static void usage();
+ static pcap_if_t *pcap_matchdev(pcap_if_t *dp, const char *name);
+-static int pcap_init(PCAP_HANDLER **ph_list, pcap_if_t *dp);
++static int traf_pcap_init(PCAP_HANDLER **ph_list, pcap_if_t *dp);
+ static void *pcap_feed(void *arg); /* PCAP_HANDLER *ph */
+ #ifdef HAVE_PCAP_GET_SELECTABLE_FD
+ static void *pcap_feed2(void *arg); /* PCAP_HANDLER *ph */
+@@ -172,7 +172,7 @@
+ }
+
+ /* initialize list of pcap handlers */
+- if ((op = pcap_init(&ph_list, dev_list)) < 1) {
++ if ((op = traf_pcap_init(&ph_list, dev_list)) < 1) {
+ fprintf(stderr, "No packet capture device available (no permission?)\n");
+ exit(1);
+ }
+@@ -301,7 +301,7 @@
+ }
+
+ static int
+-pcap_init(ph_list, dp)
++traf_pcap_init(ph_list, dp)
+ PCAP_HANDLER **ph_list;
+ pcap_if_t *dp;
+ {
Processed: severity of 979879 is important
Processing commands for cont...@bugs.debian.org: > # only FTBFS on non-release archs > severity 979879 important Bug #979879 [src:arpack] arpack: FTBFS on kfreebsd, m68k and sh4 due to tests failure Severity set to 'important' from 'serious' > thanks Stopping processing here. Please contact me if you need assistance. -- 979879: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=979879 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#966894: marked as done (faucc: FTBFS: parse.tab.c:108:10: fatal error: parse.tab.h: No such file or directory)
Your message dated Sat, 06 Feb 2021 22:33:57 + with message-id and subject line Bug#966894: fixed in faucc 20180503-1.1 has caused the Debian Bug report #966894, regarding faucc: FTBFS: parse.tab.c:108:10: fatal error: parse.tab.h: 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.) -- 966894: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=966894 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: faucc Version: 20180503-1 Severity: serious Justification: FTBFS on amd64 Tags: bullseye sid ftbfs Usertags: ftbfs-20200802 ftbfs-bullseye Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > gcc -Wchar-subscripts -Wcomment -Wformat -Wnonnull -Wimplicit-int > -Wimplicit-function-declaration -Wimplicit -Wmain -Wmissing-braces > -Wparentheses -Wsequence-point -Wreturn-type -Wswitch -Wtrigraphs > -Wunused-function -Wunused-label -Wunused-variable -Wunused-value > -Wuninitialized -Wunknown-pragmas -Wstrict-aliasing -Wundef -Wendif-labels > -Wshadow -Wpointer-arith -Wcast-qual -Wcast-align -Wwrite-strings > -Waggregate-return -Wstrict-prototypes -Wmissing-noreturn -Wnested-externs > -DPACKAGE_NAME=\"faucc\" -DPACKAGE_TARNAME=\"faucc\" > -DPACKAGE_VERSION=\"CURRENT\" -DPACKAGE_STRING=\"faucc\ CURRENT\" > -DPACKAGE_BUGREPORT=\"\" -DPACKAGE_URL=\"\" -DPACKAGE=\"faucc\" > -DVERSION=\"CURRENT\" -I. -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 > -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat > -Werror=format-security -MT parse.o -MD -MP -MF .deps/parse.Tpo -c -o parse.o > parse.c > parse.tab.c:108:10: fatal error: parse.tab.h: No such file or directory > compilation terminated. > make[3]: *** [Makefile:557: parse.o] Error 1 The full build log is available from: http://qa-logs.debian.net/2020/08/02/faucc_20180503-1_unstable.log A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! About the archive rebuild: The rebuild was done on EC2 VM instances from Amazon Web Services, using a clean, minimal and up-to-date chroot. Every failed build was retried once to eliminate random failures. --- End Message --- --- Begin Message --- Source: faucc Source-Version: 20180503-1.1 Done: Adrian Bunk We believe that the bug you reported is fixed in the latest version of faucc, 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 966...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Adrian Bunk (supplier of updated faucc 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: Sun, 07 Feb 2021 00:19:10 +0200 Source: faucc Architecture: source Version: 20180503-1.1 Distribution: unstable Urgency: medium Maintainer: FAUcc Team Changed-By: Adrian Bunk Closes: 966894 Changes: faucc (20180503-1.1) unstable; urgency=medium . * Non-maintainer upload. * Add patch from Stefan Potyra for FTBFS with bison 3.7. (Closes: #966894) Checksums-Sha1: 1a9197371c04fa21edffa35e329e1a7075a84ad1 1848 faucc_20180503-1.1.dsc 62ca8b3999e2531200940e697df3a6ebe7b704f9 3156 faucc_20180503-1.1.debian.tar.xz Checksums-Sha256: 6c57260e9a2623646c1667d1f6552a5558c1f041b886022978a01a26c0d478b0 1848 faucc_20180503-1.1.dsc 7288b21fb98d1036d3b81ac3d284c844ca6d4fb02fb2f1ff58752e4d23b7842d 3156 faucc_20180503-1.1.debian.tar.xz Files: 992c08ec100de2d4afbf125fcf1e35b7 1848 devel optional faucc_20180503-1.1.dsc a2e2244ad0ee1d2b22c34b1e414ee2b4 3156 devel optional faucc_20180503-1.1.debian.tar.xz -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEOvp1f6xuoR0v9F3wiNJCh6LYmLEFAmAfFs0ACgkQiNJCh6LY mLHV9BAAxcDrasCQuvHpNtLAtLE4ZnkvRRiYosZ4rTfKL+o6YATwgm87lSeXgQtn 40SXXNLKIzWa8ncWzAERRfKB1PB9/q/eVXiYRgQzrtPIDy06ubE2X6w44+2BQG4F i/ZhC6dolqt/qVdZWyixahXy8FLK8mZLoNEOArxLqQGr9FT/qbMVKq5NvRT2jJFg BOpQHm43fv52aSEOZABmQg4L1EOj1+AS5oG8RwY6Ioq+0sEm8oHZYwfRQE/OoInH q2g9XLqKob0oSWTYNpoD/5B6l3ddUKj9Mdkg4ErT9Zk86wW5ch7y+RdaiIKCpdxU 1wEzRebKAbDbmaPEJ0gHZkfX+k/+U//45GUWCP6mZiuxLemkPgk1+zDdjmzGvthy zCL2krul0Xy1MeB1GXI9YshpuWblkUKajjzoDjNWAo5OSZvB2gB5QKUV9JDQoDMk pmqNtuV
Processed: w-scan: diff for NMU version 20170107-2.1
Processing control commands: > tags 957919 + patch Bug #957919 [src:w-scan] w-scan: ftbfs with GCC-10 Added tag(s) patch. > tags 957919 + pending Bug #957919 [src:w-scan] w-scan: ftbfs with GCC-10 Added tag(s) pending. -- 957919: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=957919 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#957919: w-scan: diff for NMU version 20170107-2.1
Control: tags 957919 + patch
Control: tags 957919 + pending
Dear maintainer,
I've prepared an NMU for w-scan (versioned as 20170107-2.1) and uploaded
it to DELAYED/1. Please feel free to tell me if I should cancel it.
cu
Adrian
diff -Nru w-scan-20170107/debian/changelog w-scan-20170107/debian/changelog
--- w-scan-20170107/debian/changelog 2018-02-18 12:33:38.0 +0200
+++ w-scan-20170107/debian/changelog 2021-02-07 00:28:53.0 +0200
@@ -1,3 +1,12 @@
+w-scan (20170107-2.1) unstable; urgency=medium
+
+ * Non-maintainer upload.
+ * Add patch from Rob Moss for compilation with gcc 10.
+(Closes: #957919)
+ * Remove dead Homepage link.
+
+ -- Adrian Bunk Sun, 07 Feb 2021 00:28:53 +0200
+
w-scan (20170107-2) unstable; urgency=medium
* Moved VCS to salsa.debian.org
diff -Nru w-scan-20170107/debian/control w-scan-20170107/debian/control
--- w-scan-20170107/debian/control 2018-02-18 12:33:38.0 +0200
+++ w-scan-20170107/debian/control 2021-02-07 00:28:45.0 +0200
@@ -7,7 +7,6 @@
Standards-Version: 4.1.2
Vcs-Git: https://salsa.debian.org/vdr-team/w-scan.git
Vcs-Browser: https://salsa.debian.org/vdr-team/w-scan
-Homepage: http://wirbel.htpc-forum.de/w_scan/index2.html
Package: w-scan
Architecture: any
diff -Nru w-scan-20170107/debian/patches/series w-scan-20170107/debian/patches/series
--- w-scan-20170107/debian/patches/series 1970-01-01 02:00:00.0 +0200
+++ w-scan-20170107/debian/patches/series 2021-02-07 00:28:53.0 +0200
@@ -0,0 +1 @@
+support_fno-common_compilation
diff -Nru w-scan-20170107/debian/patches/support_fno-common_compilation w-scan-20170107/debian/patches/support_fno-common_compilation
--- w-scan-20170107/debian/patches/support_fno-common_compilation 1970-01-01 02:00:00.0 +0200
+++ w-scan-20170107/debian/patches/support_fno-common_compilation 2021-02-07 00:28:53.0 +0200
@@ -0,0 +1,32 @@
+Description: support compilation with -fno-common (default in GCC 10)
+Bug-Debian: https://bugs.debian.org/957919
+
+--- w-scan-20170107.orig/si_types.h
w-scan-20170107/si_types.h
+@@ -62,7 +62,7 @@ typedef struct section_buf {
+ time_t running_time;
+ struct section_buf * next_seg;// this is used to handle segmented tables (like NIT-other)
+ pList garbage;
+-} section_t, * p_section_t;
++};
+
+ /***
+ /* service type.
+@@ -114,7 +114,7 @@ struct service {
+ uint32_t logical_channel_number;
+ uint8_t running;
+ void * priv;
+-} service_t, * p_service_t;
++};
+
+ /***
+ /* transponder type.
+@@ -201,7 +201,7 @@ struct transponder {
+ /**/
+ char * network_name;
+ network_change_t network_change;
+-} __attribute__((packed)) transponder_t, * p_transponder_t;
++} __attribute__((packed));
+
+ /***
+ /* satellite channel routing type.
Bug#982031: marked as done (parl-desktop-world depends on hunspell-se which has been removed)
Your message dated Sat, 06 Feb 2021 22:18:31 + with message-id and subject line Bug#982031: fixed in debian-parl 1.9.27 has caused the Debian Bug report #982031, regarding parl-desktop-world depends on hunspell-se which has been removed 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.) -- 982031: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=982031 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: parl-desktop-world Version: 1.9.26 Severity: serious Justification: not installable Hi Jonas, hunspell-se has been removed from unstable. Don't ask me how that is possible as your package still depends on it, but it happened. Please drop the dependency. Paul OpenPGP_signature Description: OpenPGP digital signature --- End Message --- --- Begin Message --- Source: debian-parl Source-Version: 1.9.27 Done: Jonas Smedegaard We believe that the bug you reported is fixed in the latest version of debian-parl, 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 982...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Jonas Smedegaard (supplier of updated debian-parl package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sat, 06 Feb 2021 22:52:43 +0100 Source: debian-parl Architecture: source Version: 1.9.27 Distribution: unstable Urgency: medium Maintainer: DebianParl team Changed-By: Jonas Smedegaard Closes: 982031 Changes: debian-parl (1.9.27) unstable; urgency=medium . * rebuild using newer boxer-data + stop include hunspell-se; closes: bug#982031, thanks to Paul Gevers Checksums-Sha1: 1eb122af16c89b2ceaabe0109e84cd1a172f9550 1966 debian-parl_1.9.27.dsc bb9d792bfd4583042257183104fe06cd1e4a7039 10700 debian-parl_1.9.27.tar.xz 08c9bd4ac1652fa09e4d75586f8b6482bb8367ed 9031 debian-parl_1.9.27_amd64.buildinfo Checksums-Sha256: 161ef61e713fa76a44c312b4700f333c2fdf8fb639820dc7527b8f84d6d87538 1966 debian-parl_1.9.27.dsc 5aabbc8cb12f977f9a4465665c0367d2e0ac952b0954a3c2c595f081bd519254 10700 debian-parl_1.9.27.tar.xz 97a7473b90f158497a9b65c0ad5cc76f6b199f09a9e368e271a55b9d88f5b918 9031 debian-parl_1.9.27_amd64.buildinfo Files: 93d43fde70251addaa98a0a8a9e93465 1966 misc optional debian-parl_1.9.27.dsc cf24f4ae22beba13fcf5dcdd63e7c044 10700 misc optional debian-parl_1.9.27.tar.xz f1ba3ff0b62c2fd2e350f080f9462a15 9031 misc optional debian-parl_1.9.27_amd64.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEn+Ppw2aRpp/1PMaELHwxRsGgASEFAmAfEI0ACgkQLHwxRsGg ASEI/g/+OenSROaWBZNrgL6pV/1JiN5VKzQctF9M75jHtaFyJN3reKrkumoWzxEh TdCO5/BqAoyu4gn+sfLFK4pmCO4eblLJ2UmsUI+Wax0a5DGuteCHOZukFChQVbFB UIIJfWcF4kze32Xqux+dv7oo0T2BUQcoagFXlwO6i5xHys9SNle1SIfTwkOfv9N7 w9MSQmpeUVJe0+wHw8DYVb/XLU5li3TMsieTJCA+gsGaQpU/RWGSi4xBbx2rKmXw 9xvZ9nzgUo3cI4GuHi4lpRe217o3klfL03u9ObUqTPmh8QgA+JOsLx1lu1Ca3Ov/ RpTRbt7LxXUDKZvySUmNHAJf0XjiFgNGJl4zg1FGvK29qK6iivlT0gf6F66Pfpll A6wYqb1doDc4qEBNGSuJZ8AjqdZFLsrx3C4D2zaBAYs/1DDXiAhT/5VAetsZRhe/ Icx71dLb+rXMKIqPMpZuD03NRhwVZMdO/NXjEG/2+ljjwpSFsEFh9p702T5v1CG2 fTO8TQ+QTywKGl57AJ8T5Jz+Cujcq7g6qlW0/L4uXmtYREgd60Y1XWiWwdU9bsc2 FtqwszGSIiaml4FLxfmJgpBBxs889YoASjSzywMPPYF0MKO6Wm+GW6SifDxOuhsW nF7OyD1/IIufd8DUa/B57knqZTZUDmNQGpO8K19X3ihdqyVGi+0= =ExU5 -END PGP SIGNATURE End Message ---
Bug#957478: libsml: diff for NMU version 0.1.1+git20180125-1.1
Control: tags 957478 + pending
Dear maintainer,
I've prepared an NMU for libsml (versioned as 0.1.1+git20180125-1.1) and
uploaded it to DELAYED/1. Please feel free to tell me if I should cancel it.
cu
Adrian
diff -Nru libsml-0.1.1+git20180125/debian/changelog libsml-0.1.1+git20180125/debian/changelog
--- libsml-0.1.1+git20180125/debian/changelog 2018-05-13 11:27:20.0 +0300
+++ libsml-0.1.1+git20180125/debian/changelog 2021-02-07 00:09:04.0 +0200
@@ -1,3 +1,11 @@
+libsml (0.1.1+git20180125-1.1) unstable; urgency=medium
+
+ * Non-maintainer upload.
+ * Add patch from Logan Rosen for FTBFS with gcc 10.
+(Closes: #957478)
+
+ -- Adrian Bunk Sun, 07 Feb 2021 00:09:04 +0200
+
libsml (0.1.1+git20180125-1) unstable; urgency=medium
* New upstream release
diff -Nru libsml-0.1.1+git20180125/debian/patches/gcc-10.patch libsml-0.1.1+git20180125/debian/patches/gcc-10.patch
--- libsml-0.1.1+git20180125/debian/patches/gcc-10.patch 1970-01-01 02:00:00.0 +0200
+++ libsml-0.1.1+git20180125/debian/patches/gcc-10.patch 2021-02-07 00:09:04.0 +0200
@@ -0,0 +1,200 @@
+From 0738cd50632eadb9cd2c21e07b70f984a9cf444b Mon Sep 17 00:00:00 2001
+From: r00t
+Date: Mon, 28 Dec 2020 01:03:43 +0100
+Subject: [PATCH] [test] fix building with -fno-common (gcc10 default),
+
+see https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85678
+---
+ test/src/sml_boolean_test.c | 2 +-
+ test/src/sml_buffer_test.c | 2 +-
+ test/src/sml_file_test.c | 2 +-
+ test/src/sml_get_profile_pack_request_test.c | 2 +-
+ test/src/sml_list_test.c | 4 ++--
+ test/src/sml_message_test.c | 2 +-
+ test/src/sml_number_test.c | 2 +-
+ test/src/sml_octet_string_test.c | 2 +-
+ test/src/sml_open_request_test.c | 2 +-
+ test/src/sml_status_test.c | 2 +-
+ test/src/sml_time_test.c | 2 +-
+ test/src/sml_tree_test.c | 2 +-
+ test/src/sml_value_test.c| 2 +-
+ 13 files changed, 14 insertions(+), 14 deletions(-)
+
+diff --git a/test/src/sml_boolean_test.c b/test/src/sml_boolean_test.c
+index 90b5f3d..0fbebf1 100644
+--- a/test/src/sml_boolean_test.c
b/test/src/sml_boolean_test.c
+@@ -22,7 +22,7 @@
+
+ TEST_GROUP(sml_boolean);
+
+-sml_buffer *buf;
++static sml_buffer *buf;
+
+ TEST_SETUP(sml_boolean) {
+ buf = sml_buffer_init(512);
+diff --git a/test/src/sml_buffer_test.c b/test/src/sml_buffer_test.c
+index bf8e714..45eacc2 100644
+--- a/test/src/sml_buffer_test.c
b/test/src/sml_buffer_test.c
+@@ -22,7 +22,7 @@
+ TEST_GROUP(sml_buffer);
+
+ int buffer_len = 512;
+-sml_buffer *buf;
++static sml_buffer *buf;
+
+ TEST_SETUP(sml_buffer) {
+ buf = sml_buffer_init(buffer_len);
+diff --git a/test/src/sml_file_test.c b/test/src/sml_file_test.c
+index 1b1bb15..9ded16f 100644
+--- a/test/src/sml_file_test.c
b/test/src/sml_file_test.c
+@@ -22,7 +22,7 @@
+
+ TEST_GROUP(sml_file);
+
+-sml_buffer *buf;
++static sml_buffer *buf;
+
+ TEST_SETUP(sml_file) {
+ buf = sml_buffer_init(512);
+diff --git a/test/src/sml_get_profile_pack_request_test.c b/test/src/sml_get_profile_pack_request_test.c
+index c03d6ab..44f1f07 100644
+--- a/test/src/sml_get_profile_pack_request_test.c
b/test/src/sml_get_profile_pack_request_test.c
+@@ -22,7 +22,7 @@
+
+ TEST_GROUP(sml_get_profile_pack_request);
+
+-sml_buffer *buf;
++static sml_buffer *buf;
+
+ TEST_SETUP(sml_get_profile_pack_request) {
+ buf = sml_buffer_init(512);
+diff --git a/test/src/sml_list_test.c b/test/src/sml_list_test.c
+index 9a5f583..56d6ed2 100644
+--- a/test/src/sml_list_test.c
b/test/src/sml_list_test.c
+@@ -22,7 +22,7 @@
+
+ TEST_GROUP(sml_list);
+
+-sml_buffer *buf;
++static sml_buffer *buf;
+
+ TEST_SETUP(sml_list) {
+ buf = sml_buffer_init(512);
+@@ -100,7 +100,7 @@ TEST_GROUP_RUNNER(sml_list) {
+
+ TEST_GROUP(sml_sequence);
+
+-sml_buffer *buf;
++static sml_buffer *buf;
+
+ TEST_SETUP(sml_sequence) {
+ buf = sml_buffer_init(512);
+diff --git a/test/src/sml_message_test.c b/test/src/sml_message_test.c
+index 7462435..3d4bb07 100644
+--- a/test/src/sml_message_test.c
b/test/src/sml_message_test.c
+@@ -22,7 +22,7 @@
+
+ TEST_GROUP(sml_message);
+
+-sml_buffer *buf;
++static sml_buffer *buf;
+
+ TEST_SETUP(sml_message) {
+ buf = sml_buffer_init(512);
+diff --git a/test/src/sml_number_test.c b/test/src/sml_number_test.c
+index 9a5eece..09c00ca 100644
+--- a/test/src/sml_number_test.c
b/test/src/sml_number_test.c
+@@ -23,7 +23,7 @@
+
+ TEST_GROUP(sml_number);
+
+-sml_buffer *buf;
++static sml_buffer *buf;
+
+ TEST_SETUP(sml_number) {
+ buf = sml_buffer_init(512);
+diff --git a/test/src/sml_octet_string_test.c b/test/src/sml_octet_string_test.c
+index 2a47632..c37d219 100644
+--- a/test/src/sml_octet_string_test.c
b/test/src/sml_octet_string_test.c
+@@ -22,7 +22,7 @@
+
+ TEST_GROUP(sml_octet_string);
+
+-sml_buffer *buf;
++
Processed: libsml: diff for NMU version 0.1.1+git20180125-1.1
Processing control commands: > tags 957478 + pending Bug #957478 [src:libsml] libsml: ftbfs with GCC-10 Added tag(s) pending. -- 957478: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=957478 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#980646: marked as done (node-mysticatea-eslint-plugin: FTBFS: tests failed)
Your message dated Sat, 06 Feb 2021 22:05:54 + with message-id and subject line Bug#980646: fixed in node-mysticatea-eslint-plugin 11.0.0~ds-3 has caused the Debian Bug report #980646, regarding node-mysticatea-eslint-plugin: FTBFS: tests failed to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 980646: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=980646 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: node-mysticatea-eslint-plugin Version: 11.0.0~ds-2 Severity: serious Justification: FTBFS on amd64 Tags: bullseye sid ftbfs Usertags: ftbfs-20210120 ftbfs-bullseye Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[1]: Entering directory '/<>' > NO_COLOR=1 NODE_PATH=debian/node_modules eslint --format tap lib scripts tests > TAP version 13 > 1..61 > ok 1 - /<>/lib/configs.js > ok 2 - /<>/lib/configs/_browser-globals.js > ok 3 - /<>/lib/configs/_mocha.js > ok 4 - /<>/lib/configs/_special.js > ok 5 - /<>/lib/configs/_ts.js > ok 6 - /<>/lib/configs/_vue.js > ok 7 - /<>/lib/configs/+browser.js > ok 8 - /<>/lib/configs/+eslint-plugin.js > ok 9 - /<>/lib/configs/+modules.js > ok 10 - /<>/lib/configs/+node.js > ok 11 - /<>/lib/configs/es2015.js > ok 12 - /<>/lib/configs/es2016.js > ok 13 - /<>/lib/configs/es2017.js > ok 14 - /<>/lib/configs/es2018.js > ok 15 - /<>/lib/configs/es2019.js > ok 16 - /<>/lib/configs/es5.js > ok 17 - /<>/lib/foreign-rules/eslint-comments.js > ok 18 - /<>/lib/foreign-rules/eslint-plugin.js > ok 19 - /<>/lib/foreign-rules/node.js > ok 20 - /<>/lib/foreign-rules/prettier.js > ok 21 - /<>/lib/foreign-rules/ts.js > ok 22 - /<>/lib/foreign-rules/vue.js > ok 23 - /<>/lib/processors.js > ok 24 - /<>/lib/processors/vue.js > ok 25 - /<>/lib/rules.js > ok 26 - /<>/lib/rules/arrow-parens.js > ok 27 - /<>/lib/rules/block-scoped-var.js > ok 28 - /<>/lib/rules/no-instanceof-array.js > ok 29 - /<>/lib/rules/no-instanceof-wrapper.js > ok 30 - /<>/lib/rules/no-literal-call.js > ok 31 - /<>/lib/rules/no-this-in-static.js > ok 32 - /<>/lib/rules/no-use-ignored-vars.js > ok 33 - /<>/lib/rules/no-useless-rest-spread.js > ok 34 - /<>/lib/rules/prefer-for-of.js > ok 35 - /<>/lib/utils.js > ok 36 - /<>/scripts/generate-browser-globals.js > ok 37 - /<>/scripts/generate-configs.js > ok 38 - /<>/scripts/generate-rules.js > ok 39 - /<>/tests/lib/configs/_rules.js > ok 40 - /<>/tests/lib/configs/browser.js > ok 41 - /<>/tests/lib/configs/es2015.js > ok 42 - /<>/tests/lib/configs/es2016.js > ok 43 - /<>/tests/lib/configs/es2017.js > ok 44 - /<>/tests/lib/configs/es2018.js > ok 45 - /<>/tests/lib/configs/es5.js > ok 46 - /<>/tests/lib/configs/eslint-plugin.js > ok 47 - /<>/tests/lib/configs/mocha.js > ok 48 - /<>/tests/lib/configs/modules.js > ok 49 - /<>/tests/lib/configs/node.js > ok 50 - /<>/tests/lib/configs/special.js > ok 51 - /<>/tests/lib/configs/ts.js > ok 52 - /<>/tests/lib/configs/vue.js > ok 53 - /<>/tests/lib/rules/arrow-parens.js > ok 54 - /<>/tests/lib/rules/block-scoped-var.js > ok 55 - /<>/tests/lib/rules/no-instanceof-array.js > ok 56 - /<>/tests/lib/rules/no-instanceof-wrapper.js > ok 57 - /<>/tests/lib/rules/no-literal-call.js > ok 58 - /<>/tests/lib/rules/no-this-in-static.js > ok 59 - /<>/tests/lib/rules/no-use-ignored-vars.js > ok 60 - /<>/tests/lib/rules/no-useless-rest-spread.js > ok 61 - /<>/tests/lib/rules/prefer-for-of.js > > NO_COLOR=1 NODE_PATH=debian/node_modules mocha --no-timeout --reporter tap > --exclude tests/lib/configs/ts.js --exclude tests/lib/configs/vue.js > --exclude tests/lib/configs/es5.js --exclude > tests/lib/configs/eslint-plugin.js --exclude tests/lib/configs/node.js \ > "tests/lib/**/*.js" > ok 1 '+browser.js' should be a valid config. > ok 2 'es2015.js' should be a valid config. > ok 3 'es2015.js' should include ES2015 rule 'arrow-body-style'. > ok 4 'es2015.js' should include ES2015 rule 'arrow-parens'. > ok 5 'es2015.js' should include ES2015 rule 'arrow-spacing'. > ok 6 'es2015.js' should include ES2015 rule 'constructor-super'. > ok 7 'es2015.js' should include ES2015 rule 'generator-star-spacing'. > ok 8 'es2015.js' should include ES2015 rule 'no-class-assign'. > ok 9 'es2015.js' should include ES2015 rule 'no-confusing-arrow'. > ok 10 'es2015.js' should include ES2015 rule 'no-const-assign'. > ok 11 'es2015.js' should include ES2015 rule 'no-dupe-class-members'. > ok 12 'es2015.js' should include ES2015 rule 'no-duplicate-imports'. > ok 13 'es2015.js' should include ES2015 rule 'no-new-symbol'. > ok 14 'es2015.js' should include ES2015 rule 'no-restri
Bug#980231: marked as done (node-mysticatea-eslint-plugin: autopkgtest regression in testing: 'es5.js' should include existing rule 'multiline-comment-style')
Your message dated Sat, 06 Feb 2021 22:05:54 + with message-id and subject line Bug#980231: fixed in node-mysticatea-eslint-plugin 11.0.0~ds-3 has caused the Debian Bug report #980231, regarding node-mysticatea-eslint-plugin: autopkgtest regression in testing: 'es5.js' should include existing rule 'multiline-comment-style' 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.) -- 980231: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=980231 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: node-mysticatea-eslint-plugin Version: 11.0.0~ds-2 X-Debbugs-CC: debian...@lists.debian.org Severity: serious User: debian...@lists.debian.org Usertags: regression Dear maintainer(s), With a recent change somewhere outside of your package the autopkgtest of your package started to fail. I copied some of the output at the bottom of this report. Can you please investigate the situation and fix it? More information about this bug and the reason for filing it can be found on https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation Paul https://ci.debian.net/data/autopkgtest/testing/amd64/n/node-mysticatea-eslint-plugin/9705343/log.gz not ok 105 'es5.js' should include existing rule 'multiline-comment-style'. The expression evaluated to a falsy value: assert(ruleId in config.rules) AssertionError [ERR_ASSERTION]: The expression evaluated to a falsy value: assert(ruleId in config.rules) at Context. (tests/lib/configs/es5.js:39:13) at callFn (/usr/share/nodejs/mocha/lib/runnable.js:364:21) at Test.Runnable.run (/usr/share/nodejs/mocha/lib/runnable.js:352:5) at Runner.runTest (/usr/share/nodejs/mocha/lib/runner.js:677:10) at /usr/share/nodejs/mocha/lib/runner.js:801:12 at next (/usr/share/nodejs/mocha/lib/runner.js:594:14) at /usr/share/nodejs/mocha/lib/runner.js:604:7 at next (/usr/share/nodejs/mocha/lib/runner.js:486:14) at Immediate._onImmediate (/usr/share/nodejs/mocha/lib/runner.js:572:5) at processImmediate (internal/timers.js:461:21) OpenPGP_signature Description: OpenPGP digital signature --- End Message --- --- Begin Message --- Source: node-mysticatea-eslint-plugin Source-Version: 11.0.0~ds-3 Done: Jonas Smedegaard We believe that the bug you reported is fixed in the latest version of node-mysticatea-eslint-plugin, 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 980...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Jonas Smedegaard (supplier of updated node-mysticatea-eslint-plugin package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sat, 06 Feb 2021 22:49:11 +0100 Source: node-mysticatea-eslint-plugin Architecture: source Version: 11.0.0~ds-3 Distribution: unstable Urgency: medium Maintainer: Debian Javascript Maintainers Changed-By: Jonas Smedegaard Closes: 980231 980646 Changes: node-mysticatea-eslint-plugin (11.0.0~ds-3) unstable; urgency=medium . * fix grammar in long description * fix skip test related to not yet covered vue.js rules; closes: bug#980231, #980646, thanks to Paul Gevers and Lucas Nussbaum Checksums-Sha1: 915063a510701f6ad3f8b0aca7cc94a6334272c0 2579 node-mysticatea-eslint-plugin_11.0.0~ds-3.dsc f222cd9c30cc465a8db7d36ca851011fc208cc95 6 node-mysticatea-eslint-plugin_11.0.0~ds-3.debian.tar.xz 62f6c779d591590bcf75ecb7c2a827f37277c065 12098 node-mysticatea-eslint-plugin_11.0.0~ds-3_amd64.buildinfo Checksums-Sha256: 0ba02929a635053e91ffbba0186188dfe531be7832cb78540e13fe189bbc80b0 2579 node-mysticatea-eslint-plugin_11.0.0~ds-3.dsc d5b6bd0e2f84a0e523a4fbee8e6c82d0449c0afdaeff63a31f65d9e90873a900 6 node-mysticatea-eslint-plugin_11.0.0~ds-3.debian.tar.xz a2260898db9fa74bb12d36a6a31684d74f9911fea1ae6b55a5de1624bdb902b4 12098 node-mysticatea-eslint-plugin_11.0.0~ds-3_amd64.buildinfo Files: 4a4593f44fe9a800c90db129168e9ecb 2579 javascript optional node-mysticatea-eslint-plugin_11.0.0~ds-3.dsc be49ecf5bfa8c7a42f37c27c86c96577 6 javascript optional node-mysticatea-eslint-plugin_11.0.0~ds-3.debian.tar.xz 8044a2574acbeb1948d2eb7c254c9875 12098 j
Bug#982133: php-pimple: Useless in Bullseye
Package: php-pimple Version: 3.3.1-1 Severity: serious X-Debbugs-Cc: jvalle...@mailbox.org -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 This is a dependency only for shaarli, which will not be included in Bullseye. - -- System Information: Debian Release: bullseye/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.10.0-2-amd64 (SMP w/4 CPU threads) Kernel taint flags: TAINT_WARN, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages php-pimple depends on: ii php-common 2:76 ii php-psr-container 1.0.0-2 php-pimple recommends no packages. php-pimple suggests no packages. - -- no debconf information -BEGIN PGP SIGNATURE- iQJKBAEBCgA0FiEEfWrbdQ+RCFWJSEvmd8DHXntlCAgFAmAe2gAWHGp2YWxsZXJv eUBtYWlsYm94Lm9yZwAKCRB3wMdee2UICJA8EACXXckirDCoVilGLIBRwW1SX/F/ NDGElDlk8OAeghZgFxzaaO4scoYqgWUG4v0EjbSLZ9UsUCG8jyTUuQcfh+LS9rn0 6ArRk3UAfs9O9wwldvT3BDOpeZhRfu3LbgoBN61xcoPjk6tE/V2hEZiQBPv9INui 8m76UAvdIwFirelpymh9O82bpgXHml5lnoEVDqkiPzje5IqIdKvrq1E+xApx32G+ rzbtfPG6tgiPr040n9ikHnvETm4qeoxOIRxxWu2c9sEyMlCwwpfQdNyssawwQUUw iw1I3C8xIKvSQ6zbBHpm4cBCsoMks6WK4zpmcldwhEbCZpylmmI7F9WdxgcbQ8si auw75Czk+gTYVGyOvm4O2apxum+1HnLeH2nzZx3GC3Nw33f0BNUo4pZ696sQBpRM 6/eQZvMBUS7bjs90bSSTd3E1KL+LBaTGAlqhL8pYiQoMxCA6cC1ZeLY1uwqGkN2p QYgTj4c7u05rUJtBPkwrCJRqpz9E75SFg7VGzjILzXFcLA+VGr0g2BYknm6ZomZL MoDJffTg4GqYzGA6OxGB+SXl6zo5PT/khnHwXvW5A7n6iph7ScIxN1KS1umLhQDl 6SwHJcmzTuq19tZqW1MpDupzav2lT2YFhrbZCpf5+goeIjNKaFIybDpdiuLbB8ml bHlg0RRvVAo5+ws0dA== =lpde -END PGP SIGNATURE-
Bug#982132: php-netscape-bookmark-parser: Useless in Bullseye
Package: php-netscape-bookmark-parser Version: 2.1.0-3 Severity: serious X-Debbugs-Cc: jvalle...@mailbox.org -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 This is a dependency only for shaarli, which will not be included in Bullseye. - -- System Information: Debian Release: bullseye/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.10.0-2-amd64 (SMP w/4 CPU threads) Kernel taint flags: TAINT_WARN, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages php-netscape-bookmark-parser depends on: ii php-common 2:76 ii php-klogger 1.2.1-4 php-netscape-bookmark-parser recommends no packages. php-netscape-bookmark-parser suggests no packages. - -- no debconf information -BEGIN PGP SIGNATURE- iQJKBAEBCgA0FiEEfWrbdQ+RCFWJSEvmd8DHXntlCAgFAmAe2ZYWHGp2YWxsZXJv eUBtYWlsYm94Lm9yZwAKCRB3wMdee2UICEWvD/sF3fO0XjTJKGrsqgUJO4PYgLbm xKZYg0Ckjsz43exhsVqgWIgBIyAYfA2NrSWVmeR2GMVxsIkSb2CX7ICMbIAQ/hZ5 vg6YZ34bv6KKAqE/lYslYsT3M2CsoCmhsSVzR5TFudZg6TBSW7kjRYA099qBUegu 34TgejzK/EyMEV0HWR1mocMGj8J33W8qSLiJeejD9iXo8km86VnX+OvLcNGG7xXi 1ODPYSESa4PFTzQE/N92YV9AZfulcicks1rRyDLUEBZD364WjNVe2puSuJHsf/bC Guointdh+hK4Kdz3wBIkEpH8W2PlQmGQnxS/GwO6SsM7YKnyw2XXsmGjPmJa0BMn MaSIR0ouPTw/9y6ia/A+B0/9QQJ3yhpspW2cqNxvWyM52RG1PTZzyArAYcDmaKVG wXxU7FSZdNT4hirsjf3yqUm4l+4ZG9oRV+Wpt84utOCnw2xLnK6D+CuYes63c6JF Zw8JhrjSH5Xw/Pi5HjoD2l+W9SAdbsgcrDQhhiDentmx6ola67OizVt//LkYV7tn VhP8dlPS+41WzdKr7WIwm2XpG3OUKbRDkKTF/16Pm7fwyfYeA8SeyhtNRKfcLq1/ KWprZTTzUZ5dSO4fLcOtwXiluDteKoV8qoumsQ8UEsjmE/zcuKMMem+0HI6Rbhfa FYyNQXvfSJVBSQ5oDw== =5wso -END PGP SIGNATURE-
Bug#980646: marked as done (node-mysticatea-eslint-plugin: FTBFS: tests failed)
Your message dated Sat, 06 Feb 2021 21:48:43 + with message-id and subject line Bug#980646: fixed in eslint 5.16.0~dfsg+~4.16.8-5 has caused the Debian Bug report #980646, regarding node-mysticatea-eslint-plugin: FTBFS: tests failed to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 980646: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=980646 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: node-mysticatea-eslint-plugin Version: 11.0.0~ds-2 Severity: serious Justification: FTBFS on amd64 Tags: bullseye sid ftbfs Usertags: ftbfs-20210120 ftbfs-bullseye Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[1]: Entering directory '/<>' > NO_COLOR=1 NODE_PATH=debian/node_modules eslint --format tap lib scripts tests > TAP version 13 > 1..61 > ok 1 - /<>/lib/configs.js > ok 2 - /<>/lib/configs/_browser-globals.js > ok 3 - /<>/lib/configs/_mocha.js > ok 4 - /<>/lib/configs/_special.js > ok 5 - /<>/lib/configs/_ts.js > ok 6 - /<>/lib/configs/_vue.js > ok 7 - /<>/lib/configs/+browser.js > ok 8 - /<>/lib/configs/+eslint-plugin.js > ok 9 - /<>/lib/configs/+modules.js > ok 10 - /<>/lib/configs/+node.js > ok 11 - /<>/lib/configs/es2015.js > ok 12 - /<>/lib/configs/es2016.js > ok 13 - /<>/lib/configs/es2017.js > ok 14 - /<>/lib/configs/es2018.js > ok 15 - /<>/lib/configs/es2019.js > ok 16 - /<>/lib/configs/es5.js > ok 17 - /<>/lib/foreign-rules/eslint-comments.js > ok 18 - /<>/lib/foreign-rules/eslint-plugin.js > ok 19 - /<>/lib/foreign-rules/node.js > ok 20 - /<>/lib/foreign-rules/prettier.js > ok 21 - /<>/lib/foreign-rules/ts.js > ok 22 - /<>/lib/foreign-rules/vue.js > ok 23 - /<>/lib/processors.js > ok 24 - /<>/lib/processors/vue.js > ok 25 - /<>/lib/rules.js > ok 26 - /<>/lib/rules/arrow-parens.js > ok 27 - /<>/lib/rules/block-scoped-var.js > ok 28 - /<>/lib/rules/no-instanceof-array.js > ok 29 - /<>/lib/rules/no-instanceof-wrapper.js > ok 30 - /<>/lib/rules/no-literal-call.js > ok 31 - /<>/lib/rules/no-this-in-static.js > ok 32 - /<>/lib/rules/no-use-ignored-vars.js > ok 33 - /<>/lib/rules/no-useless-rest-spread.js > ok 34 - /<>/lib/rules/prefer-for-of.js > ok 35 - /<>/lib/utils.js > ok 36 - /<>/scripts/generate-browser-globals.js > ok 37 - /<>/scripts/generate-configs.js > ok 38 - /<>/scripts/generate-rules.js > ok 39 - /<>/tests/lib/configs/_rules.js > ok 40 - /<>/tests/lib/configs/browser.js > ok 41 - /<>/tests/lib/configs/es2015.js > ok 42 - /<>/tests/lib/configs/es2016.js > ok 43 - /<>/tests/lib/configs/es2017.js > ok 44 - /<>/tests/lib/configs/es2018.js > ok 45 - /<>/tests/lib/configs/es5.js > ok 46 - /<>/tests/lib/configs/eslint-plugin.js > ok 47 - /<>/tests/lib/configs/mocha.js > ok 48 - /<>/tests/lib/configs/modules.js > ok 49 - /<>/tests/lib/configs/node.js > ok 50 - /<>/tests/lib/configs/special.js > ok 51 - /<>/tests/lib/configs/ts.js > ok 52 - /<>/tests/lib/configs/vue.js > ok 53 - /<>/tests/lib/rules/arrow-parens.js > ok 54 - /<>/tests/lib/rules/block-scoped-var.js > ok 55 - /<>/tests/lib/rules/no-instanceof-array.js > ok 56 - /<>/tests/lib/rules/no-instanceof-wrapper.js > ok 57 - /<>/tests/lib/rules/no-literal-call.js > ok 58 - /<>/tests/lib/rules/no-this-in-static.js > ok 59 - /<>/tests/lib/rules/no-use-ignored-vars.js > ok 60 - /<>/tests/lib/rules/no-useless-rest-spread.js > ok 61 - /<>/tests/lib/rules/prefer-for-of.js > > NO_COLOR=1 NODE_PATH=debian/node_modules mocha --no-timeout --reporter tap > --exclude tests/lib/configs/ts.js --exclude tests/lib/configs/vue.js > --exclude tests/lib/configs/es5.js --exclude > tests/lib/configs/eslint-plugin.js --exclude tests/lib/configs/node.js \ > "tests/lib/**/*.js" > ok 1 '+browser.js' should be a valid config. > ok 2 'es2015.js' should be a valid config. > ok 3 'es2015.js' should include ES2015 rule 'arrow-body-style'. > ok 4 'es2015.js' should include ES2015 rule 'arrow-parens'. > ok 5 'es2015.js' should include ES2015 rule 'arrow-spacing'. > ok 6 'es2015.js' should include ES2015 rule 'constructor-super'. > ok 7 'es2015.js' should include ES2015 rule 'generator-star-spacing'. > ok 8 'es2015.js' should include ES2015 rule 'no-class-assign'. > ok 9 'es2015.js' should include ES2015 rule 'no-confusing-arrow'. > ok 10 'es2015.js' should include ES2015 rule 'no-const-assign'. > ok 11 'es2015.js' should include ES2015 rule 'no-dupe-class-members'. > ok 12 'es2015.js' should include ES2015 rule 'no-duplicate-imports'. > ok 13 'es2015.js' should include ES2015 rule 'no-new-symbol'. > ok 14 'es2015.js' should include ES2015 rule 'no-restricted-imports'
Processed: severity of 980428 is serious
Processing commands for cont...@bugs.debian.org: > severity 980428 serious Bug #980428 [php-pear] Disallow symlinks to out-of-path filenames (CVE-2020-36193) Ignoring request to change severity of Bug 980428 to the same value. > thanks Stopping processing here. Please contact me if you need assistance. -- 980428: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=980428 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#980428: CVE-2020-28948 write operations with directory traversal affecting Archive_Tar through 1.4.11
Control: severity -1 serous Hi PHP maintainers, On Mon, Jan 18, 2021 at 08:03:42PM -0400, David Prévot wrote: > Package: php-pear > Version: 1:1.10.9+submodules+notgz-1.1 > Severity: important > Tags: security > X-Debbugs-Cc: Debian Security Team > > Hi, > > The latest (1.4.11) Archive_Tar adds a fix related to CVE-2020-28948. > > https://github.com/FriendsOfPHP/security-advisories/pull/525 This should ideally be fixed before the bullseye release, so raising the severity to RC. Regards, Salvatore
Processed: severity of 980428 is serious
Processing commands for cont...@bugs.debian.org: > # should be fixed ideally for bullseye before relese > severity 980428 serious Bug #980428 [php-pear] Disallow symlinks to out-of-path filenames (CVE-2020-36193) Severity set to 'serious' from 'important' > thanks Stopping processing here. Please contact me if you need assistance. -- 980428: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=980428 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Bug#980646 marked as pending in eslint
Processing control commands: > tag -1 pending Bug #980646 [src:node-mysticatea-eslint-plugin] node-mysticatea-eslint-plugin: FTBFS: tests failed Added tag(s) pending. -- 980646: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=980646 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#980646: marked as pending in eslint
Control: tag -1 pending Hello, Bug #980646 in eslint reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/js-team/eslint/-/commit/de37d79e251e7010dfca532256030792d213b0c0 add patch 1002 to use newer release of node module cheerio; closes: bug#980646, thanks to Lucas Nussbaum (this message was generated automatically) -- Greetings https://bugs.debian.org/980646
Processed: ncurses-hexedit: diff for NMU version 0.9.7+orig-7.1
Processing control commands: > tags 957585 + pending Bug #957585 [src:ncurses-hexedit] ncurses-hexedit: ftbfs with GCC-10 Added tag(s) pending. -- 957585: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=957585 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#957585: ncurses-hexedit: diff for NMU version 0.9.7+orig-7.1
Control: tags 957585 + pending
Dear maintainer,
I've prepared an NMU for ncurses-hexedit (versioned as 0.9.7+orig-7.1)
and uploaded it to DELAYED/1. Please feel free to tell me if I should
cancel it.
cu
Adrian
diff -Nru ncurses-hexedit-0.9.7+orig/debian/changelog ncurses-hexedit-0.9.7+orig/debian/changelog
--- ncurses-hexedit-0.9.7+orig/debian/changelog 2019-02-01 00:55:35.0 +0200
+++ ncurses-hexedit-0.9.7+orig/debian/changelog 2021-02-06 23:35:33.0 +0200
@@ -1,3 +1,11 @@
+ncurses-hexedit (0.9.7+orig-7.1) unstable; urgency=medium
+
+ * Non-maintainer upload.
+ * Add patch from Logan Rosen for FTBFS with gcc 10.
+(Closes: #957585)
+
+ -- Adrian Bunk Sat, 06 Feb 2021 23:35:33 +0200
+
ncurses-hexedit (0.9.7+orig-7) unstable; urgency=medium
* Build with Debhelper compat level 12.
diff -Nru ncurses-hexedit-0.9.7+orig/debian/patches/gcc_10.patch ncurses-hexedit-0.9.7+orig/debian/patches/gcc_10.patch
--- ncurses-hexedit-0.9.7+orig/debian/patches/gcc_10.patch 1970-01-01 02:00:00.0 +0200
+++ ncurses-hexedit-0.9.7+orig/debian/patches/gcc_10.patch 2021-02-06 23:35:31.0 +0200
@@ -0,0 +1,44 @@
+--- a/src/hexedit.h
b/src/hexedit.h
+@@ -343,7 +343,7 @@
+
+
+/* Global structure, keep most global variables here. */
+-struct
++struct Globals_t
+ {
+WINDOW *wmain, *wstatus, *whelp; /* three windows used throughout. */
+unsigned long filesize; /* size of the file buffer. */
+@@ -365,7 +365,9 @@
+ /* buf end. */
+int beeping; /* Allow beeping or not. */
+int help_msg_count; /* Number of messages in help menu. */
+-} Globals;
++};
++
++extern struct Globals_t Globals;
+
+
+ struct foundit
+@@ -400,7 +402,9 @@
+int s;
+struct Change *base;
+struct Change *top;
+-} UndoStack;
++};
++
++extern struct ChangeLog UndoStack;
+
+
+ struct FileNames
+--- a/src/init.c
b/src/init.c
+@@ -35,6 +35,8 @@
+
+ extern char **environ;
+
++struct ChangeLog UndoStack;
++struct Globals_t Globals;
+
+/* This is called once at the start of the program. Handles HEXEDIT
+ * Environment variable, command line arguments, sets up signal
diff -Nru ncurses-hexedit-0.9.7+orig/debian/patches/series ncurses-hexedit-0.9.7+orig/debian/patches/series
--- ncurses-hexedit-0.9.7+orig/debian/patches/series 2019-01-31 05:29:46.0 +0200
+++ ncurses-hexedit-0.9.7+orig/debian/patches/series 2021-02-06 23:35:31.0 +0200
@@ -16,3 +16,4 @@
enforce_readonly_mode.patch
fix_buffer_overruns.patch
fix_spelling_errors.patch
+gcc_10.patch
Bug#982149: golang-github-xenolf-lego: autopkgtest regression: Build failure
Source: golang-github-xenolf-lego Version: 3.2.0-3 X-Debbugs-CC: debian...@lists.debian.org Severity: serious User: debian...@lists.debian.org Usertags: regression Dear maintainer(s), With a recent upload of golang-github-xenolf-lego the autopkgtest of golang-github-xenolf-lego fails in testing when that autopkgtest is run with the binary packages of golang-github-xenolf-lego from unstable. It passes when run with only packages from testing. In tabular form: passfail golang-github-xenolf-lego from testing3.2.0-3 all others from testingfrom testing I copied some of the output at the bottom of this report. Looking at the changelog and the situation that golang-github-nrdcg-goinwx is in, it seems your missing a *versioned* (Build-)Depends. Currently this regression is blocking the migration to testing [1]. Can you please investigate the situation and fix it? More information about this bug and the reason for filing it can be found on https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation Paul [1] https://qa.debian.org/excuses.php?package=golang-github-xenolf-lego https://ci.debian.net/data/autopkgtest/testing/arm64/g/golang-github-xenolf-lego/10292237/log.gz github.com/aws/aws-sdk-go/service/lightsail github.com/aws/aws-sdk-go/service/route53 github.com/aws/aws-sdk-go/aws/defaults github.com/aws/aws-sdk-go/service/sts/stsiface github.com/aws/aws-sdk-go/aws/credentials/stscreds github.com/aws/aws-sdk-go/aws/session github.com/go-acme/lego/providers/dns/route53 github.com/go-acme/lego/providers/dns/lightsail dh_auto_build: error: cd _build && go install -trimpath -v -p 4 github.com/go-acme/lego/acme github.com/go-acme/lego/acme/api github.com/go-acme/lego/acme/api/internal/nonces github.com/go-acme/lego/acme/api/internal/secure github.com/go-acme/lego/acme/api/internal/sender github.com/go-acme/lego/certcrypto github.com/go-acme/lego/certificate github.com/go-acme/lego/challenge github.com/go-acme/lego/challenge/dns01 github.com/go-acme/lego/challenge/http01 github.com/go-acme/lego/challenge/resolver github.com/go-acme/lego/challenge/tlsalpn01 github.com/go-acme/lego/cmd github.com/go-acme/lego/cmd/lego github.com/go-acme/lego/internal github.com/go-acme/lego/lego github.com/go-acme/lego/log github.com/go-acme/lego/platform/config/env github.com/go-acme/lego/platform/tester github.com/go-acme/lego/platform/wait github.com/go-acme/lego/providers/dns github.com/go-acme/lego/providers/dns/autodns github.com/go-acme/lego/providers/dns/bluecat github.com/go-acme/lego/providers/dns/cloudns github.com/go-acme/lego/providers/dns/cloudns/internal github.com/go-acme/lego/providers/dns/cloudxns github.com/go-acme/lego/providers/dns/cloudxns/internal github.com/go-acme/lego/providers/dns/conoha github.com/go-acme/lego/providers/dns/conoha/internal github.com/go-acme/lego/providers/dns/digitalocean github.com/go-acme/lego/providers/dns/dnsmadeeasy github.com/go-acme/lego/providers/dns/dnsmadeeasy/internal github.com/go-acme/lego/providers/dns/dode github.com/go-acme/lego/providers/dns/dreamhost github.com/go-acme/lego/providers/dns/duckdns github.com/go-acme/lego/providers/dns/dyn github.com/go-acme/lego/providers/dns/easydns github.com/go-acme/lego/providers/dns/exec github.com/go-acme/lego/providers/dns/gandi github.com/go-acme/lego/providers/dns/gandiv5 github.com/go-acme/lego/providers/dns/gcloud github.com/go-acme/lego/providers/dns/glesys github.com/go-acme/lego/providers/dns/godaddy github.com/go-acme/lego/providers/dns/hostingde github.com/go-acme/lego/providers/dns/httpreq github.com/go-acme/lego/providers/dns/inwx github.com/go-acme/lego/providers/dns/joker github.com/go-acme/lego/providers/dns/lightsail github.com/go-acme/lego/providers/dns/mydnsjp github.com/go-acme/lego/providers/dns/namecheap github.com/go-acme/lego/providers/dns/netcup github.com/go-acme/lego/providers/dns/netcup/internal github.com/go-acme/lego/providers/dns/nifcloud github.com/go-acme/lego/providers/dns/nifcloud/internal github.com/go-acme/lego/providers/dns/otc github.com/go-acme/lego/providers/dns/ovh github.com/go-acme/lego/providers/dns/pdns github.com/go-acme/lego/providers/dns/rackspace github.com/go-acme/lego/providers/dns/rfc2136 github.com/go-acme/lego/providers/dns/route53 github.com/go-acme/lego/providers/dns/selectel github.com/go-acme/lego/providers/dns/selectel/internal github.com/go-acme/lego/providers/dns/stackpath github.com/go-acme/lego/providers/dns/versio github.com/go-acme/lego/providers/dns/vscale github.com/go-acme/lego/providers/dns/vscale/internal github.com/go-acme/lego/providers/dns/vultr github.com/go-acme/lego/providers/dns/zoneee github.com/go-acme/lego/providers/http/webroot github.com/go-acme/lego/registration returned exit code 2 make: *** [debian/rules:37: build] Error 25 autopkgtest [04:11:59]: test dh-golang-autopkgtest: ---] OpenPGP_signature Description: OpenPGP digital signature
Bug#948128: marked as done (gnome-shell-mailnag FTBFS: vala error: syntax error, invalid array parameter declaration)
Your message dated Sat, 06 Feb 2021 21:18:37 + with message-id and subject line Bug#948128: fixed in gnome-shell-mailnag 3.38.1-1 has caused the Debian Bug report #948128, regarding gnome-shell-mailnag FTBFS: vala error: syntax error, invalid array parameter declaration 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.) -- 948128: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=948128 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: gnome-shell-mailnag Version: 3.28.0-0.1 Severity: serious Tags: ftbfs gnome-shell-mailnag fails to build from source in unstable on amd64 using sbuild: | aggregate-avatars.vala:28.30-28.30: error: syntax error, invalid array parameter declaration | static int main(string args[]) | ^ | aggregate-avatars.vala:45.1-45.1: error: expected end of file | } | ^ | aggregate-avatars.vala:30.22-30.20: warning: main blocks are experimental | MainLoop mainloop = new MainLoop(); | | Compilation failed: 2 error(s), 12 warning(s) | make[1]: *** [Makefile:14: aggregate-avatars] Error 1 | make[1]: Leaving directory '/<>' | dh_auto_build: make -j1 returned exit code 2 | make: *** [debian/rules:4: build] Error 255 | dpkg-buildpackage: error: debian/rules build subprocess returned exit status 2 Also reproduced by reproducible builds: https://tests.reproducible-builds.org/debian/rbuild/unstable/amd64/gnome-shell-mailnag_3.28.0-0.1.rbuild.log.gz Helmut --- End Message --- --- Begin Message --- Source: gnome-shell-mailnag Source-Version: 3.38.1-1 Done: Adrian Bunk We believe that the bug you reported is fixed in the latest version of gnome-shell-mailnag, 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 948...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Adrian Bunk (supplier of updated gnome-shell-mailnag package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sat, 06 Feb 2021 22:54:59 +0200 Source: gnome-shell-mailnag Architecture: source Version: 3.38.1-1 Distribution: unstable Urgency: medium Maintainer: Debian QA Group Changed-By: Adrian Bunk Closes: 948128 956167 Changes: gnome-shell-mailnag (3.38.1-1) unstable; urgency=medium . * QA upload. * Set Maintainer to Debian QA Group. (see #968541) * New upstream release. - For GNOME 3.38. (Closes: #956167) - Fixes Vala error. (Closes: #948128) Checksums-Sha1: 3017e311e93d0b2c8206941aa81b0d89cc3e7201 2043 gnome-shell-mailnag_3.38.1-1.dsc 914eba3a797785e5924ef9625fd8af8fca6a8a51 18581 gnome-shell-mailnag_3.38.1.orig.tar.gz dfff12f027d8bb386f5effd3f1f9aca3746e46a6 2884 gnome-shell-mailnag_3.38.1-1.debian.tar.xz Checksums-Sha256: 79b10785560a97d1ec73a45b9971b5ac281c6a57b48ce75a772a9b2ac1148b7e 2043 gnome-shell-mailnag_3.38.1-1.dsc 6d3c9318270f2e1b397c648306cdbe6d5041b69a9de5db7155d3ec31ecef40d2 18581 gnome-shell-mailnag_3.38.1.orig.tar.gz ce641ed0cd787a0e240bb71c544ddb226938f64761922a23f8b69e6c38731fac 2884 gnome-shell-mailnag_3.38.1-1.debian.tar.xz Files: 17ebe12ea4a40950ccdd93bbfa7caa66 2043 gnome optional gnome-shell-mailnag_3.38.1-1.dsc 0c1162fa43d54dee820220ee0de923d2 18581 gnome optional gnome-shell-mailnag_3.38.1.orig.tar.gz a115cdfcc274eaeccf326f0ba32ce412 2884 gnome optional gnome-shell-mailnag_3.38.1-1.debian.tar.xz -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEOvp1f6xuoR0v9F3wiNJCh6LYmLEFAmAfAx8ACgkQiNJCh6LY mLFnEA//cOu64H7kbOBz8Ps8f5u2O43Yetl/c4PIAzO0tIrfZ1RikuDj9QWACK6a qay7z+JGEhW1/ACWLcUrVPY+CXd29BB6w6JtOtuWkhiTPJwuGttB8vkX/4885F9b 0vmnuskF4kaePPN79gBKhWi/gRN4uCGKEuG7iOhrUORJASncdhc1bE8vmxB8t3a4 sZzcTm3bqiU0j7MbeIbbkAwE0Ly77dN5ILR7Sh2rkwc+RStJg1o5ko6Hb4GSFuY9 GLsFrSNq9XVBrMMuE+YTnXI64dTYglzVAdxDlRyxp45KSzgyG6HS+33jxP591OSL 8ie7feVuLRRo8OEIfRNv9FPlDLpYLXMW8gDSnJ8L663rAoDcK5zt1R+BxhfMHe6t 3xTF4iIbF+8uPPKoFZfPRU/SRAlTjAm8R8/ydxosduugypMhqaCgCtzh4KKN+UkW C9LfQqTfRxFxiSzKO8O31qyPBDJEO05AshiWyOGw07s2Yyuqcbmecf7s025KUpi1 QliRbiJs9r1ssHfJQcsskFhP3KD7h+W3CnkILsDdxWVtOZWM3axfflO0io/QRyKI RK0UhAYqxCUWpBMbrK1QVwICXMptlpakjHf0q+hMBMfkM68lVEODi/AByn/jLWoC HpaRMjpBE8AtyxzRjw64QWDBL1IX2zdCXLqhP0ZdO/sKbDrCw2Q= =Y1kl -END PGP SIGNATURE End Mess
Bug#982148: frama-c: autopkgtest failure: nothing logged
Source: frama-c Version: 20201209+titanium-4 X-Debbugs-CC: debian...@lists.debian.org Severity: serious User: debian...@lists.debian.org Usertags: fails-always Dear maintainer(s), You recently added an autopkgtest to your package frama-c, great. However, it fails. Currently this failure is blocking the migration to testing [1]. Can you please investigate the situation and fix it? I copied some of the output at the bottom of this report. Unfortunately, there's not much to see. I also read the last changelog. Please reconsider using skip-not-installable and maybe favor the new Architecture field, as skip-not-installable also hides genuine issues. 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=frama-c https://ci.debian.net/data/autopkgtest/testing/amd64/f/frama-c/9622788/log.gz autopkgtest [04:30:15]: test eva: [--- autopkgtest [04:30:16]: test eva: ---] autopkgtest [04:30:16]: test eva: - - - - - - - - - - results - - - - - - - - - - eva FAIL non-zero exit status 1 OpenPGP_signature Description: OpenPGP digital signature
Processed: tagging 959846
Processing commands for cont...@bugs.debian.org: > # fixed in git: > https://salsa.debian.org/debian/manpages-l10n/-/commit/a50e28bccfbd99c84c609ca90ec738b1813e6c72 > tags 959846 + patch Bug #959846 [manpages-de] manpages-de: missing Breaks+Replaces: manpages-de-dev (<< 4) Added tag(s) patch. > thanks Stopping processing here. Please contact me if you need assistance. -- 959846: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=959846 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#981930: libelf1: fails to install
Hi Norbert, On Sat, Feb 06, 2021 at 08:08:20PM +0900, Norbert Preining wrote: > > The bug you report is actually present in -1 already. > > Hmmm > > > The package is not unusable. It merely cannot be coinstalled. > > then why on earth did I have both arch (amd64, i386) installed on my > computer before? And in addition, downgrading to the versions in testing > did work without a hinch. This particular combination of architectures did work for that combination of builds. Other combinations were already broken in -1. > So no, sorry to say, but you are wrong. The previous -1 packages > **were** co-installable, and that bug did not occur. It did not affect you, but the bug was present in -1 already. > > It doesn't really fix it, because dh-strip-nondeterminism doesn't fix it > > yet. That's a separate bug report. > > Might be a bug induced by the almighty nodeteriminsim/reproducible > groups, but it does show up here. The bug wasn't induced by reproducible. Quite on the contrary. The bug was induced by the usage of Multi-Arch: same! The Debian implementation of Multi-Arch requires reproducibility even before the reproducible people started working on it. Reproducibility just is the cure here. > > Reverting the NMU doesn't help in any way. It's reproducibility issue. > > It **does**. I reverted to the version in testing without any problems. Yes, I do see that. However, you cannot reupload those binary packages to the archive. If you were reverting to the "working" version and performing a build, with luck you'd still be affected. It only depends on when the builds are performed and whether their timing is close enough. The -1 builds were lucky for your particular combination. > And whatever it is, if it is a reproducibility issue, I honestly don't > give a #$#$Y(#'$ about it when it breaks the system. It doesn't break your system. It just breaks coinstallation of libelf1. I don't think that coinstallation issues are considered release critical at this point, because it is not documented in policy. A sad state of affairs, I know. > Reproducibility is not the highest aim we are targetting, it is just a > tool. Exactly. > If it is broken, then dump it and ignore it, who cares (besides > some former Debian Majesty). Reproducibility isn't the thing that is broken here. Multi-Arch is. The "dump it" solution would have been removing Multi-Arch from libelf1. That "fix" would have caused apt to remove a lot of packages from your system. I don't think you'd be any happier. Please don't blame the reproducible people for any of this. They're the cure, not the problem. Helmut
Processed: severity of 973821 is important
Processing commands for cont...@bugs.debian.org: > # tests marked as XFAIL - cfgrib no longer FTBFS > severity 973821 important Bug #973821 [python3-pandas] pandas 1.13.1: regression in datetime handling causes test failures in cfgrib Severity set to 'important' from 'serious' > thanks Stopping processing here. Please contact me if you need assistance. -- 973821: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=973821 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: retitle 973821 to pandas 1.13.1: regression in datetime handling causes test failures in cfgrib
Processing commands for cont...@bugs.debian.org: > retitle 973821 pandas 1.13.1: regression in datetime handling causes test > failures in cfgrib Bug #973821 [python3-pandas] cfgrib: FTBFS: tests failed Changed Bug title to 'pandas 1.13.1: regression in datetime handling causes test failures in cfgrib' from 'cfgrib: FTBFS: tests failed'. > thanks Stopping processing here. Please contact me if you need assistance. -- 973821: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=973821 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Re: Bug#982023: gimp-gmic: prevents gimp from loading
Processing commands for cont...@bugs.debian.org: > severity 982023 normal Bug #982023 [gimp-gmic] gimp-gmic: prevents gimp from loading Severity set to 'normal' from 'grave' > tags 982023 moreinfo Bug #982023 [gimp-gmic] gimp-gmic: prevents gimp from loading Added tag(s) moreinfo. > thanks Stopping processing here. Please contact me if you need assistance. -- 982023: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=982023 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#982023: gimp-gmic: prevents gimp from loading
severity 982023 normal tags 982023 moreinfo thanks Hi, I had the same issue here, reason for that was that some library was linked against libdap25 and another one against libdap27. ==3160905== Invalid free() / delete / delete[] / realloc() ==3160905==at 0x4839EAB: operator delete(void*) (in /usr/lib/x86_64-linux-gnu/valgrind/vgpreload_memcheck-amd64-linux.so) ==3160905==by 0x58BBAC5: __cxa_finalize (cxa_finalize.c:83) ==3160905==by 0x15ED7FA2: ??? (in /usr/lib/x86_64-linux-gnu/libdap.so.27.0.4) ==3160905==by 0x4010342: _dl_fini (dl-fini.c:138) ==3160905==by 0x58BB4D6: __run_exit_handlers (exit.c:108) ==3160905==by 0x58BB679: exit (exit.c:139) ==3160905==by 0x58A3D10: (below main) (libc-start.c:342) ==3160905== Address 0x1674ad90 is 0 bytes inside a block of size 25 free'd ==3160905==at 0x4839EAB: operator delete(void*) (in /usr/lib/x86_64-linux-gnu/valgrind/vgpreload_memcheck-amd64-linux.so) ==3160905==by 0x58BBAC5: __cxa_finalize (cxa_finalize.c:83) ==3160905==by 0x1288B5A2: ??? (in /usr/lib/x86_64-linux-gnu/libdap.so.25.2.3) ==3160905==by 0x4010342: _dl_fini (dl-fini.c:138) ==3160905==by 0x58BB4D6: __run_exit_handlers (exit.c:108) ==3160905==by 0x58BB679: exit (exit.c:139) ==3160905==by 0x58A3D10: (below main) (libc-start.c:342) ==3160905== Block was alloc'd at ==3160905==at 0x4838DEF: operator new(unsigned long) (in /usr/lib/x86_64-linux-gnu/valgrind/vgpreload_memcheck-amd64-linux.so) ==3160905==by 0x1290EC46: ??? (in /usr/lib/x86_64-linux-gnu/libdap.so.25.2.3) ==3160905==by 0x1288B1EC: ??? (in /usr/lib/x86_64-linux-gnu/libdap.so.25.2.3) ==3160905==by 0x400FFB1: call_init.part.0 (dl-init.c:72) ==3160905==by 0x40100B8: call_init (dl-init.c:30) ==3160905==by 0x40100B8: _dl_init (dl-init.c:119) ==3160905==by 0x40010C9: ??? (in /usr/lib/x86_64-linux-gnu/ld-2.31.so) Please either use unstable or wait until all testing migrations are done. If you still see this bug afterwards, please provide a valgrind output. It will be most likely that its not gmic code which triggers this bug. Also: gimp should not hang when a plugin crashes, and it didn't do so for me. That might be a different bug, possibly in gimp. Thanks, Bernd On 2/5/21 7:42 PM, Christoph Anton Mitterer wrote: > Package: gimp-gmic > Version: 2.9.4-1 > Severity: grave > Justification: renders package unusable > > > Hi. > > Since one of the more recent upgrades, gimp doesn't start up anymore, when > gimp-gmic is present (purging it solves the issue), but instead hangs > forever at th slapsh screen. > > > Cheers, > Chris. > > > > $ gimp --verbose > Parsing '/etc/gimp/2.0/gimprc' for configured language. > Parsing '/home/calestyo/.config/GIMP/2.10/gimprc' for configured language. > No language property found. > INIT: gimp_load_config > Parsing '/home/calestyo/.config/GIMP/2.10/unitrc' > Parsing '/etc/gimp/2.0/gimprc' > Parsing '/home/calestyo/.config/GIMP/2.10/gimprc' > Adding icon theme 'Color' (/usr/share/gimp/2.0/icons/Color) > Adding icon theme 'Legacy' (/usr/share/gimp/2.0/icons/Legacy) > Adding icon theme 'Symbolic' (/usr/share/gimp/2.0/icons/Symbolic) > Adding icon theme 'Symbolic-Inverted' > (/usr/share/gimp/2.0/icons/Symbolic-Inverted) > Adding icon theme 'Symbolic-High-Contrast' > (/usr/share/gimp/2.0/icons/Symbolic-High-Contrast) > Adding icon theme 'Symbolic-Inverted-High-Contrast' > (/usr/share/gimp/2.0/icons/Symbolic-Inverted-High-Contrast) > Loading icon theme 'Color' > Adding theme 'Dark' (/usr/share/gimp/2.0/themes/Dark) > Adding theme 'Gray' (/usr/share/gimp/2.0/themes/Gray) > Adding theme 'Light' (/usr/share/gimp/2.0/themes/Light) > Adding theme 'System' (/usr/share/gimp/2.0/themes/System) > Writing '/home/calestyo/.config/GIMP/2.10/themerc' > Trying splash '/home/calestyo/.config/GIMP/2.10/gimp-splash.png' ... failed > Trying splash '/usr/share/gimp/2.0/images/gimp-splash.png' ... OK > INIT: gimp_initialize > INIT: gimp_real_initialize > Parsing '/usr/lib/gimp/2.0/interpreters/default.interp' > Parsing '/usr/lib/gimp/2.0/environ/default.env' > INIT: gui_initialize_after_callback > INIT: gimp_restore > Parsing '/home/calestyo/.config/GIMP/2.10/parasiterc' > Loading 'brush factory' data > Loading /usr/share/gimp/2.0/brushes/Texture/Cell-01.gbr > Loading /usr/share/gimp/2.0/brushes/Texture/Cell-02.gbr > Loading /usr/share/gimp/2.0/brushes/Texture/Grass.gih > Loading /usr/share/gimp/2.0/brushes/Texture/Hatch-Pen-01.gbr > Loading /usr/share/gimp/2.0/brushes/Texture/Smoke.gbr > Loading /usr/share/gimp/2.0/brushes/Texture/Stone-Work-01.gih > Loading /usr/share/gimp/2.0/brushes/Texture/Texture-01.gbr > Loading /usr/share/gimp/2.0/brushes/Texture/Texture-02.gbr > Loading /usr/share/gimp/2.0/brushes/Texture/Texture-Hose-01.gih > Loading /usr/share/gimp/2.0/brushes/Texture/Texture-Hose-02.gih > Loading /usr/share/gimp/2.0/brushes/Texture/Texture-Hose-03.gih > Loading /usr/share/gimp/2.0/brushes/Texture/Vegetation-0
Bug#980202: FTBFS: gscan2pdf tests fail
gscan2pdf does not set a specific font for the unit test. If the default font changes, the unit test fails. To fix, simply remove /usr/share/fonts/type1/urw-base35/ from the URW search path on configure.ac. Run autoconf to update configure. Background: The problem is the ImageMagick Development team added a new URW font directory to search in configure.ac: /usr/share/fonts/type1/urw-base35/. Unfortunately, type1 fonts require an .afm metric file and these metrics incorrectly set the descender and ascender to 0: NimbusSans-Regular.afm: Descender 0 Ascender 0 We reviewed the Freetype code and in some places they sanitize the ascender and descender if they are 0. We added code to 6.9.11-62 to sanitize the values but unfortunately that then changed the default font for gscan2pdf which changes the image size for unit test t/1122_save_pdf_with_hocr.t. By rights, the gscan2pdf developers should have specified a specific font in case the default font changes-- but they didn't. The proper fix for Debian is to patch configure.ac to remove /usr/share/fonts/type1/urw-base35/ from the URW search path, run autoconf then build ImageMagick or have the gscan2pdf development team set a specific font. We ran gscan2pdf unit tests and they pass now. This same fix should work for any release of ImageMagick 6 from 6.9.11-23+. Cristy Principle ImageMagick Architect
Bug#982066: marked as done (python3-watchdog: Missing dependencies on python3-yaml and python3-argh)
Your message dated Sat, 06 Feb 2021 20:33:58 +
with message-id
and subject line Bug#982066: fixed in python-watchdog 1.0.2-2
has caused the Debian Bug report #982066,
regarding python3-watchdog: Missing dependencies on python3-yaml and
python3-argh
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.)
--
982066: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=982066
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: python3-watchdog
Version: 1.0.2-1
Severity: serious
The runtime dependencies on ython3-yaml and python3-argh
were lost in the latest upload:
https://ci.debian.net/data/autopkgtest/testing/amd64/p/python-watchdog/10289743/log.gz
...
autopkgtest [16:32:16]: test command1: /usr/bin/watchmedo --version
autopkgtest [16:32:16]: test command1: [---
Traceback (most recent call last):
File "/usr/bin/watchmedo", line 33, in
sys.exit(load_entry_point('watchdog==1.0.2', 'console_scripts',
'watchmedo')())
File "/usr/bin/watchmedo", line 25, in importlib_load_entry_point
return next(matches).load()
File "/usr/lib/python3.9/importlib/metadata.py", line 77, in load
module = import_module(match.group('module'))
File "/usr/lib/python3.9/importlib/__init__.py", line 127, in import_module
return _bootstrap._gcd_import(name[level:], package, level)
File "", line 1030, in _gcd_import
File "", line 1007, in _find_and_load
File "", line 986, in _find_and_load_unlocked
File "", line 680, in _load_unlocked
File "", line 790, in exec_module
File "", line 228, in _call_with_frames_removed
File "/usr/lib/python3/dist-packages/watchdog/watchmedo.py", line 29, in
import yaml
ModuleNotFoundError: No module named 'yaml'
autopkgtest [16:32:18]: test command1: ---]
autopkgtest [16:32:18]: test command1: - - - - - - - - - - results - - - - - -
- - - -
command1 FAIL non-zero exit status 1
...
--- End Message ---
--- Begin Message ---
Source: python-watchdog
Source-Version: 1.0.2-2
Done: Julian Gilbey
We believe that the bug you reported is fixed in the latest version of
python-watchdog, 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 982...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Julian Gilbey (supplier of updated python-watchdog package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Sat, 06 Feb 2021 19:59:54 +
Source: python-watchdog
Architecture: source
Version: 1.0.2-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Team
Changed-By: Julian Gilbey
Closes: 982066
Changes:
python-watchdog (1.0.2-2) unstable; urgency=medium
.
* Fix dependencies (closes: #982066)
Checksums-Sha1:
cbf5a465fa710a8cd87eb8ff5512c89c9e1661be 2275 python-watchdog_1.0.2-2.dsc
0fd7e972271f42427996dc103275c73ec1202bfb 4808
python-watchdog_1.0.2-2.debian.tar.xz
fcdbb8642faf0d9fc9d71f893db043f3c12081f3 8171
python-watchdog_1.0.2-2_amd64.buildinfo
Checksums-Sha256:
00bf4967092563ebd99aac3e45ce70b891ce0ac536ab66b10c28cd60dd781996 2275
python-watchdog_1.0.2-2.dsc
b95f8d6491e9217dfc77b4499db04ee30a4ad9c943875a472b5644216dd46616 4808
python-watchdog_1.0.2-2.debian.tar.xz
b8caf333e050f146c5e2886a12976003ecf99c17d0e897647a5a87f30af9a14e 8171
python-watchdog_1.0.2-2_amd64.buildinfo
Files:
5de851994640f080b2c5aa9d886aec8b 2275 python optional
python-watchdog_1.0.2-2.dsc
7fd90782af7c1435127262aa64bbf3e9 4808 python optional
python-watchdog_1.0.2-2.debian.tar.xz
164577be6611176fafe5fdd4ab85ae4e 8171 python optional
python-watchdog_1.0.2-2_amd64.buildinfo
-BEGIN PGP SIGNATURE-
iQJDBAEBCAAtFiEEfhrD+iemSShMMj72aVxCkxbAe/4FAmAe9zgPHGpkZ0BkZWJp
YW4ub3JnAAoJEGlcQpMWwHv+80sP/jyhPHX/wdvC9aUz7AniX8s95zBGpQXPZOno
iYM27Vq7RWWLAcIJycTxM9OceGkY/6V6a+5EP1xoCQppFq1dZs5D+yNyjMYQL7O0
YRqK+V0hLfGDUZatISWveCWtzK1hnH3+Y8zYOHSXuat9SWkLaXktD1KLCak/kukr
aCrLSDnnp4CjmPLNvClvpnpKL+jXgpgsXgRYORK4rPEqlaCpgOq5uavzM1aNudVy
S0nnL9c0YG47eh3TGAaI0cdjtvZPSXJIq2m6GdWXTY4g2uk9y1FsOshgqvWujNIE
lG4IX7xS7BGynG2yNZPimcBGKWKyEjXzvRxXV/Jb6PX9C1cBZXvLUAXASSiZpGTw
cTGuUb1OQ/ExMoX3qGUahUvQpHLwyIX/xpGEjttWNmnp6r41MA6IzIlMFa1KeqxF
hznJnK4Z
Bug#981804: yubioath-desktop: fails to read yubikey
Hi > > > — > > > https://github.com/Yubico/yubioath-desktop/issues/693#issuecomment-773096570 BTW, you should upload the packages with Breaks: yubioauth-desktop (<< whatever.version) to ensure other people don't fall into the same trap. Best Norbert -- PREINING Norbert https://www.preining.info Fujitsu Research Labs + IFMGA Guide + TU Wien + TeX Live + Debian Dev GPG: 0x860CDC13 fp: F7D8 A928 26E3 16A1 9FA0 ACF0 6CAC A448 860C DC13
Bug#981228: marked as done (khal: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p 3.9 returned exit code 13)
Your message dated Sat, 06 Feb 2021 20:20:40 +
with message-id
and subject line Bug#981228: fixed in khal 1:0.10.2-0.2
has caused the Debian Bug report #981228,
regarding khal: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i
python{version} -p 3.9 returned exit code 13
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
981228: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=981228
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: khal
Version: 1:0.10.2-0.1
Severity: serious
Tags: ftbfs
Justification: fails to build from source
X-Debbugs-Cc: sramac...@debian.org
| === short test summary info
| FAILED tests/cli_test.py::test_import_from_stdin - AssertionError: assert
not...
| FAILED tests/khalendar_test.py::TestCollection::test_multi_uid_vdir -
IndexEr...
| FAILED tests/khalendar_test.py::test_default_calendar - assert 0 == 1
| FAILED tests/khalendar_test.py::test_only_update_old_event - AssertionError:
...
| FAILED tests/khalendar_test.py::test_birthdays - IndexError: list index out
o...
| FAILED tests/khalendar_test.py::test_birthdays_no_year - assert 0 == 1
| = 6 failed, 284 passed, 1 xfailed, 1 xpassed in 3.62s
==
| E: pybuild pybuild:353: test: plugin distutils failed with: exit code=1: cd
/<>/.pybuild/cpython3_3.9_khal/build; python3.9 -m pytest tests
| dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p 3.9
returned exit code 13
| make[1]: *** [debian/rules:32: override_dh_auto_test] Error 25
See
https://buildd.debian.org/status/fetch.php?pkg=khal&arch=all&ver=1%3A0.10.2-0.1&stamp=1611661499&raw=0
Cheers
--
Sebastian Ramacher
--- End Message ---
--- Begin Message ---
Source: khal
Source-Version: 1:0.10.2-0.2
Done: Jonas Smedegaard
We believe that the bug you reported is fixed in the latest version of
khal, 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 981...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Jonas Smedegaard (supplier of updated khal package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Sat, 06 Feb 2021 20:56:02 +0100
Source: khal
Architecture: source
Version: 1:0.10.2-0.2
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Team
Changed-By: Jonas Smedegaard
Closes: 981228
Changes:
khal (1:0.10.2-0.2) unstable; urgency=medium
.
* Non-maintainer upload.
.
* skip unstable tests;
closes: bug#981228, thanks to Sebastian Ramacher
Checksums-Sha1:
7049fecd4c1c6426c0e4ac1d5adb2ee615fa3d6d 2382 khal_0.10.2-0.2.dsc
20f25366001dfdfbc00ad1fd493fae4410288556 11676 khal_0.10.2-0.2.debian.tar.xz
3cc1ff902581222de121cfeb3e5cad4c2fbd0461 8288 khal_0.10.2-0.2_amd64.buildinfo
Checksums-Sha256:
86ce717196772aa901180e3f4e43b920a0567eb3dc236837e52f0cd21f8f8559 2382
khal_0.10.2-0.2.dsc
b3eddc31374677994cbaa08d7e110a08ccb3856dde6c9016112b8ea789ea548b 11676
khal_0.10.2-0.2.debian.tar.xz
39faefe6c0abc5f7a26958f5fbc52115df344e8e2a75679a787da5587f79ad3c 8288
khal_0.10.2-0.2_amd64.buildinfo
Files:
4e85203dae4c0afc7e33bbd09be1e745 2382 utils optional khal_0.10.2-0.2.dsc
f911fc3204121af6dd6fc3d63425dc31 11676 utils optional
khal_0.10.2-0.2.debian.tar.xz
728aad62efee5cff6dcdcb7a7f9bc0bf 8288 utils optional
khal_0.10.2-0.2_amd64.buildinfo
-BEGIN PGP SIGNATURE-
iQIzBAEBCgAdFiEEn+Ppw2aRpp/1PMaELHwxRsGgASEFAmAe9R8ACgkQLHwxRsGg
ASHpKw/+OHL7aTu35/pflZdvL3TdvFLU/t3QIHtErx2R9A48mpyTfArwz2ZS+0NZ
rhdoDC2AaACBm2cKUSPEOyGY+VQDsStBP/RT93/Dwl9QIii5r8xJplH2ZdFqtUKi
AZyynK4CM9pRaoxVPO+/MDlb2NiVd63TuH6LzbEzobCwu7R2XtsSj7X2JKWApjQs
Lk458lGPINzEcCQZVVcLPbQ+iSAXEebNhQBLOjRmddeu+swaUiZuU7M1fImeQHuv
yOfb8zB4yHz+zFEzg/kpAZ7tgkUovpzJQ8e4QraVf0CkYYp9QzR5h+PqW7dYtnm8
N4b1DIwQA7AthgnEzAy6A3AQORujTROfY7tjSH6thtwZznDShjQ2XQctDM66gylx
mF7S6yUZ8a4VPhnvewV/g8HGA2oiWXkJ67PpprrtMWfvyR2XzYNK1sUsAV/au0P+
+aR8CF2Gf8Mb99ZVvVMJa35Su7DMdOZ7AmY3z9M4YCIVGVQfXGx6GF1kdDYMG9rb
VsDbNaSGJ7WV0I3l74bF78qmuewfaCk0mrn6LfMGG+1+zpgT34L33NBXj8KGVbKm
n5880BLPwLIhftjct1P+/dzQE3khOVluP2rv80NJEzdm6Bw9xYO5eFY1qdXgax51
D/zO/CvJqeCMhwrLzaFD9vt6+e95+KSH82CuTZCvEZmxilEA7II=
=wfxY
-EN
Bug#958590: marked as done (hdapsd: Build-Depends on deprecated dh-systemd which is going away)
Your message dated Sat, 06 Feb 2021 20:20:35 +
with message-id
and subject line Bug#958590: fixed in hdapsd 1:20141203-2
has caused the Debian Bug report #958590,
regarding hdapsd: Build-Depends on deprecated dh-systemd which is going away
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.)
--
958590: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=958590
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: hdapsd
Severity: normal
User: pkg-systemd-maintain...@lists.alioth.debian.org
Usertags: dh-systemd-removal
Hi,
your package hdapsd declares a build dependency on dh-systemd.
dh-systemd was merged into debhelper in version 9.20160709 [1] and since
stretch, dh-systemd is an empty transitional package.
For bullseye we intend to drop this empty transitional package.
Once we drop dh-systemd, this bug report will become RC.
Please update your package accordingly. The change should be as simple as
replacing the build dependency on dh-systemd with a build dependency on
debhelper (>= 9.20160709).
Regards,
Michael
[1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=822670
--- End Message ---
--- Begin Message ---
Source: hdapsd
Source-Version: 1:20141203-2
Done: Evgeni Golov
We believe that the bug you reported is fixed in the latest version of
hdapsd, 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 958...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Evgeni Golov (supplier of updated hdapsd package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Sat, 06 Feb 2021 20:37:00 +0100
Source: hdapsd
Architecture: source
Version: 1:20141203-2
Distribution: unstable
Urgency: medium
Maintainer: Evgeni Golov
Changed-By: Evgeni Golov
Closes: 794384 830875 958590
Changes:
hdapsd (1:20141203-2) unstable; urgency=medium
.
* switch to debhelper 13, drop dh-systemd (Closes: #958590)
* fix typo in package description (Closes: #794384)
* don't recomment tp-smapi-source, it's gone (Closes: #830875)
* add ${misc:Pre-Depends} to Pre-Depends
* add vcs-* headers for salsa
* Standards-Version: 4.5.1
* don't enable on new installs using debhelper instead of old hacks
Checksums-Sha1:
e3992e7ac089f51d7f42acc7d544100799c586d0 1864 hdapsd_20141203-2.dsc
c81f2565fda79b064369a355fefb11440f9eb499 6640 hdapsd_20141203-2.debian.tar.xz
94e59833e779065eb2c0e94c1210ca53adad9545 5758
hdapsd_20141203-2_source.buildinfo
Checksums-Sha256:
283b7ae3885bcd1169efa3b8de298d928759197c87b77313209ca3e8cc0d 1864
hdapsd_20141203-2.dsc
13ebfd20d622b9a960d5df769e315283b73e75609038a3f4d071fad90d569eea 6640
hdapsd_20141203-2.debian.tar.xz
268ef91a24ef0e9dc5ec43c17b684147002fcc759599780311861731a72d2c30 5758
hdapsd_20141203-2_source.buildinfo
Files:
aae862196ab8aa5b5de045fd7c4cf714 1864 misc optional hdapsd_20141203-2.dsc
16152b47a5306a658b2d0a763bc719ee 6640 misc optional
hdapsd_20141203-2.debian.tar.xz
706ce3f9d569f5fae59057e61859e6d4 5758 misc optional
hdapsd_20141203-2_source.buildinfo
-BEGIN PGP SIGNATURE-
iQIzBAEBCgAdFiEExW57amdnGPa81AdGTrsFQAtaiq4FAmAe8CcACgkQTrsFQAta
iq42rRAAhe83YkUokPzThCMe9WUoUrv6yINm6CpM7wlCmV11N3nRK9+XwdV/BJx2
Cj8yBNiuioGLJrN8zuYb2/0WUUxf7RuvSTatuZh6Z2SlT4+Y5LhFvoZG0icMOe5n
tJA8qUEIxYAxV1/+QnuZ9vLu/wbcBq8lbGm1gEK06lxmzih16hE54q7cuhL53dOy
v0dCrLcka+RYkHD5d99I9WRwY0gFi24bXuFPOkXFc/g196OWSJmGNAT+sco+7Y8j
dEQF1qbHsU0lr9WkcBsS8tjwkertYyYrOKGCY9yIh4dqwjLMPYHxw9kMTPGPScS8
/fWFjKXNJ80Q1qSWpgTAWOcxkhYZrvVo+ovCnGKUZTAwqoXKHsi6AKc+1iUFH10L
/NzCapIw3y0rbuq3EPoW7JptLjbvS0h5hWNdB1R1R/DDN2qLLy5qOHm/cqwuZkth
scAVe+OIepaJky1zC5YHT2tAdbgPCxzLd6qjUKgNqqk+rv1DY32FWoW5YbIp2jdh
HnEnXOKg4WtZdfCCihA4W3S1fnxMDzruiWSCuDjRmXnWWPXM7GIWFUpiKHYvBxIR
l2kjJByy+AG0NUSgjqwSX9uloP1q3hEVA4G6ZD1vOrNSmutYU/v+mPcOXyoxJWv5
Ctf6bzWpfQQWLExUpBZTZ7S2gxokG+3aqJtHwmXXJrnt27Df2GA=
=5wPn
-END PGP SIGNATURE End Message ---
Processed: Re: ipywidgets FTBFS with node-semver 7.1.1-2
Processing control commands: > tags -1 - patch Bug #950094 [src:ipywidgets] ipywidgets FTBFS with node-semver 7.1.1-2 Removed tag(s) patch. -- 950094: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=950094 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Re: ipywidgets FTBFS with node-semver 7.1.1-2
Processing control commands: > tags -1 - patch Bug #971224 [src:ipywidgets] ipywidgets: FTBFS: dpkg-source: error: pathname '/<>/debian/fakewebpack-unpacked/html2canvas' points outside source root (to '/usr/lib/nodejs/html2canvas') Removed tag(s) patch. -- 971224: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=971224 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#950094: ipywidgets FTBFS with node-semver 7.1.1-2
Control: tags -1 - patch Hi, On Sat, Feb 06, 2021 at 06:57:32PM +, Gordon Ball wrote: > > This is fixed in git: > > > > https://salsa.debian.org/python-team/packages/ipywidgets/-/commit/23daf45a127b3febe25ecefdbb7148b0f5049990 > > > > Gordon, are you planning to upload this soon? The soft freeze is pretty > > close > > now. > > > > The FTBFS bugs are fixed, in the sense that I have redone the build > system reflecting all the changes that have happened to the parent > libraries, and the basic build sequence runs without error. However, the > resultant object doesn't actually work (yet). Oh. In that case, I'll remove the patch tag, because the (current) patch doesn't actually work correctly. > I'll upload it iff I can get something working before the freeze dates. OK, thanks for you work on this. If this doesn't work out, please send an update to the bug. Cheers, Ivo
Processed: khal: diff for NMU version 1:0.10.2-0.2
Processing control commands:
> tags 981228 + patch
Bug #981228 [src:khal] khal: FTBFS: dh_auto_test: error: pybuild --test
--test-pytest -i python{version} -p 3.9 returned exit code 13
Added tag(s) patch.
--
981228: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=981228
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#981228: khal: diff for NMU version 1:0.10.2-0.2
Control: tags 981228 + patch Dear maintainer, I've uploaded an NMU for khal (versioned as 1:0.10.2-0.2). The diff is attached to this message. Regards. diff -Nru khal-0.10.2/debian/changelog khal-0.10.2/debian/changelog --- khal-0.10.2/debian/changelog2021-01-26 12:16:00.0 +0100 +++ khal-0.10.2/debian/changelog2021-02-06 20:56:02.0 +0100 @@ -1,3 +1,12 @@ +khal (1:0.10.2-0.2) unstable; urgency=medium + + * Non-maintainer upload. + + * skip unstable tests; +closes: bug#981228, thanks to Sebastian Ramacher + + -- Jonas Smedegaard Sat, 06 Feb 2021 20:56:02 +0100 + khal (1:0.10.2-0.1) unstable; urgency=medium * Non-maintainer upload. diff -Nru khal-0.10.2/debian/rules khal-0.10.2/debian/rules --- khal-0.10.2/debian/rules2020-11-05 18:54:56.0 +0100 +++ khal-0.10.2/debian/rules2021-02-06 20:49:21.0 +0100 @@ -2,6 +2,12 @@ export PYBUILD_DESTDIR_python3=debian/khal export PYBUILD_NAME=khal + +# avoid unstable tests +export PYBUILD_TEST_ARGS = \ + --ignore=tests/cli_test.py \ + --ignore=tests/khalendar_test.py + %: dh $@ --with python3,sphinxdoc --buildsystem=pybuild
Processed: psensor: diff for NMU version 1.1.5-1.3
Processing control commands: > tags 917447 + patch Bug #917447 [src:psensor] psensor: Please switch Build-Depends to libsensors-dev from libsensors4-dev Added tag(s) patch. > tags 917447 + pending Bug #917447 [src:psensor] psensor: Please switch Build-Depends to libsensors-dev from libsensors4-dev Added tag(s) pending. > tags 921339 + pending Bug #921339 [psensor] Please switch to Ayatana AppIndicator Added tag(s) pending. -- 917447: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=917447 921339: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=921339 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#921339: psensor: diff for NMU version 1.1.5-1.3
Control: tags 917447 + patch Control: tags 917447 + pending Control: tags 921339 + pending Dear maintainer, I've prepared an NMU for psensor (versioned as 1.1.5-1.3) and uploaded it to DELAYED/1. Please feel free to tell me if I should cancel it. cu Adrian diff -Nru psensor-1.1.5/debian/changelog psensor-1.1.5/debian/changelog --- psensor-1.1.5/debian/changelog 2020-07-31 13:00:39.0 +0300 +++ psensor-1.1.5/debian/changelog 2021-02-06 21:50:55.0 +0200 @@ -1,3 +1,13 @@ +psensor (1.1.5-1.3) unstable; urgency=medium + + * Non-maintainer upload. + * Add patch from Alessio Garzi switching from libappindicator +to libayatana-appindicator3. (Closes: #921339) + * Update the build dependency from libsensors4-dev +to libsensors-dev. (Closes: #917447) + + -- Adrian Bunk Sat, 06 Feb 2021 21:50:55 +0200 + psensor (1.1.5-1.2) unstable; urgency=medium * Non-maintainer upload. diff -Nru psensor-1.1.5/debian/control psensor-1.1.5/debian/control --- psensor-1.1.5/debian/control 2016-06-06 21:24:39.0 +0300 +++ psensor-1.1.5/debian/control 2021-02-06 21:50:55.0 +0200 @@ -11,7 +11,7 @@ debhelper (>= 9), gettext, help2man, - libappindicator3-dev, + libayatana-appindicator3-dev, libatasmart-dev [!hurd-any !kfreebsd-any], libcurl4-gnutls-dev, libgtk-3-dev, @@ -19,7 +19,7 @@ libjson-c-dev, libmicrohttpd-dev, libnotify-dev, - libsensors4-dev, + libsensors-dev, libudisks2-dev [!kfreebsd-any], libxnvctrl-dev [i386 amd64] | nvidia-settings [i386 amd64], perl diff -Nru psensor-1.1.5/debian/patches/ayatana-appindicator.patch psensor-1.1.5/debian/patches/ayatana-appindicator.patch --- psensor-1.1.5/debian/patches/ayatana-appindicator.patch 1970-01-01 02:00:00.0 +0200 +++ psensor-1.1.5/debian/patches/ayatana-appindicator.patch 2021-02-06 21:50:55.0 +0200 @@ -0,0 +1,42 @@ +Index: psensor-1.1.5/configure.ac +=== +--- psensor-1.1.5.orig/configure.ac psensor-1.1.5/configure.ac +@@ -106,9 +106,9 @@ AC_SUBST(LIBNOTIFY_LIBS) + # Checks AppIndicator + APPINDICATOR_LIBS= + +-PKG_CHECK_MODULES(APPINDICATOR, appindicator3-0.1, ++PKG_CHECK_MODULES(APPINDICATOR, ayatana-appindicator3-0.1, + [AC_DEFINE([HAVE_APPINDICATOR],[1],[Use AppIndicator3-0.1])], +- [AC_MSG_WARN(AppIndicator 3-0.1 not present")]) ++ [AC_MSG_WARN(Ayatana AppIndicator 3-0.1 not present")]) + + if test "$APPINDICATOR_LIBS" == ""; then +PKG_CHECK_MODULES(APPINDICATOR, +Index: psensor-1.1.5/src/ui_appindicator.c +=== +--- psensor-1.1.5.orig/src/ui_appindicator.c psensor-1.1.5/src/ui_appindicator.c +@@ -21,7 +21,7 @@ + #include + + #include +-#include ++#include + + #include "cfg.h" + #include "psensor.h" +Index: psensor-1.1.5/src/ui.h +=== +--- psensor-1.1.5.orig/src/ui.h psensor-1.1.5/src/ui.h +@@ -27,7 +27,7 @@ + #include + + #if defined(HAVE_APPINDICATOR) || defined(HAVE_APPINDICATOR_029) +-#include ++#include + #endif + + #include "psensor.h" diff -Nru psensor-1.1.5/debian/patches/series psensor-1.1.5/debian/patches/series --- psensor-1.1.5/debian/patches/series 2020-07-31 12:57:13.0 +0300 +++ psensor-1.1.5/debian/patches/series 2021-02-06 21:50:55.0 +0200 @@ -1,2 +1,3 @@ 0001-Update-rsensor.c-drop-is_error-macro-definition.patch 14.patch +ayatana-appindicator.patch
Processed: psensor: diff for NMU version 1.1.5-1.3
Processing control commands: > tags 917447 + patch Bug #917447 [src:psensor] psensor: Please switch Build-Depends to libsensors-dev from libsensors4-dev Ignoring request to alter tags of bug #917447 to the same tags previously set > tags 917447 + pending Bug #917447 [src:psensor] psensor: Please switch Build-Depends to libsensors-dev from libsensors4-dev Ignoring request to alter tags of bug #917447 to the same tags previously set > tags 921339 + pending Bug #921339 [psensor] Please switch to Ayatana AppIndicator Ignoring request to alter tags of bug #921339 to the same tags previously set -- 917447: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=917447 921339: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=921339 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#982143: supermin: supermin binary does not work on architectures without native OCaml compiler
Package: src:supermin Version: 5.2.0-2 Severity: grave X-Debbugs-Cc: none, Hilko Bengen The libguestfs package fails to build on mipsel, mips64el, armel because dh_strip as used in the supermin build renders the supermin binary unusable.
Bug#982107: php-gettext-languages: Useless in Bullseye
Package: php-gettext-languages Version: 2.6.0-2 Severity: serious X-Debbugs-Cc: jvalle...@mailbox.org -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 This is only a dependency for shaarli, which will not be included in Bullseye. - -- System Information: Debian Release: bullseye/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.10.0-2-amd64 (SMP w/4 CPU threads) Kernel taint flags: TAINT_WARN, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages php-gettext-languages depends on: ii php-common 2:76 php-gettext-languages recommends no packages. php-gettext-languages suggests no packages. - -- no debconf information -BEGIN PGP SIGNATURE- iQJKBAEBCgA0FiEEfWrbdQ+RCFWJSEvmd8DHXntlCAgFAmAeuFIWHGp2YWxsZXJv eUBtYWlsYm94Lm9yZwAKCRB3wMdee2UICGqaEACyeTUztbQD1elQTfyslyajxDe0 HLFFrjD+w875ODR/1jHcFuk3fX8+tzejfA/vjQn7BkfthtdLqh+RZn62Uu97B+jA ittPNuRnDbzWRa5dI3DmAdIup5IAtYxu6BZg9O5djEE40Nturb4TcXwECCpRvr/L tqleYhSncV+nAcFbufkmjV3U1rCEEWoudO+NTY7grEdWsPyec+jQXNrvqZHkm/0q abIfYKPkzmjcXA1ZCz2U5firqde30xnoTbYM44by8B50f7p1hWXdqF6ZJdFDpgUy E/Fg3wIPaDBdPiGRPpQtADSpKFKd4E4tlNpcwdbdrL5UypciIzJmHBGuVNK8byPS XmTLOr7pkJ4CxifKOcrm3kQ2ioINa+X9eiDgE2U0Yfmb3Yt6ceEEze48uEd01EcU 2NRm+PB3L0/X8mPJ4cn8ChC7qmyGPCXlziiZvirYEKwQnoKo5ItU8qThjZN+DKFU Lqvo6S2IeHxcVBhCaLKyA+zdEp4oL4ayfa8KINSltTqN/C2tANUBeypkEB3SjOe8 OHLZAik4C9WvY5LD5foi7DAXa9wWsZ/ywZS8lbD/H7SGWnq3qsvsi0N0RRRpX49m TH36zSxBKJVk34RQDPSBzH9OwOk0ulV2Kx0vBqkFr9KQmMUtlWzup2GE0eYhQzJe gKFKIT0nPXllHUPfCg== =rTzZ -END PGP SIGNATURE-
Bug#974538: marked as done (libkscreenlocker5: kwin cannot start due to missing libkscreenunlocker5 symbols)
Your message dated Sat, 6 Feb 2021 20:39:05 +0100 with message-id <20210206193903.ga32...@debian.org> and subject line Re: Bug#974538 marked as pending in kscreenlocker has caused the Debian Bug report #974538, regarding libkscreenlocker5: kwin cannot start due to missing libkscreenunlocker5 symbols 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.) -- 974538: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=974538 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: libkscreenlocker5 Version: 5.19.5-4 Severity: serious Justification: Policy 8.1 X-Debbugs-Cc: bunge...@chromium.org $ kwin --replace kwin: symbol lookup error: /lib/x86_64-linux-gnu/libkwin.so.5: undefined symbol: _ZN12ScreenLocker7KSldApp30greeterClientConnectionChangedEvy $ ldd /lib/x86_64-linux-gnu/libkwin.so.5 libKScreenLocker.so.5 => /lib/x86_64-linux-gnu/libKScreenLocker.so.5 (0x7f0adc697000) -- System Information: Debian Release: bullseye/sid APT prefers testing-debug APT policy: (500, 'testing-debug'), (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.9.0-1-amd64 (SMP w/32 CPU threads) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages libkscreenlocker5 depends on: ii kpackagetool5 5.74.0-2 ii libc6 2.31-4 ii libkf5configcore5 5.74.0-2 ii libkf5configgui5 5.74.0-2 ii libkf5coreaddons5 5.74.0-2 ii libkf5crash5 5.74.0-2 ii libkf5declarative5 5.74.0-2 ii libkf5globalaccel-bin 5.74.0-2 ii libkf5globalaccel5 5.74.0-2 ii libkf5i18n55.74.0-3 ii libkf5idletime55.74.0-2 ii libkf5notifications5 5.74.0-2 ii libkf5package5 5.74.0-2 ii libkf5quickaddons5 5.74.0-2 ii libkf5waylandclient5 4:5.74.0-2 ii libkf5waylandserver5 4:5.74.0-2 ii libkf5windowsystem55.74.0-2 ii libkf5xmlgui5 5.74.0-2+b1 ii libpam0g 1.3.1-5 ii libqt5core5a 5.15.1+dfsg-2 ii libqt5dbus55.15.1+dfsg-2 ii libqt5gui5 5.15.1+dfsg-2 ii libqt5network5 5.15.1+dfsg-2 ii libqt5qml5 5.15.1+dfsg-3 ii libqt5quick5 5.15.1+dfsg-3 ii libqt5widgets5 5.15.1+dfsg-2 ii libqt5x11extras5 5.15.1-2 ii libseccomp22.4.4-1+b1 ii libstdc++6 10.2.0-16 ii libwayland-client0 1.18.0-2~exp1.1 ii libwayland-server0 1.18.0-2~exp1.1 ii libx11-6 2:1.6.12-1 ii libxcb-keysyms10.4.0-1+b2 ii libxcb11.14-2 ii libxi6 2:1.7.10-1 ii psmisc 23.3-1 Versions of packages libkscreenlocker5 recommends: ii kde-config-screenlocker 5.19.5-4 libkscreenlocker5 suggests no packages. -- no debconf information --- End Message --- --- Begin Message --- Version: 5.19.5-5 Hi, The fix quoted below was done in 5.19.5-5, but that version was never uploaded separately, so there was no bug closure mail. The fix was included in subsequent uploads of 5.20, so the bug can be closed. Doing so now. Thanks! Ivo On Fri, Nov 13, 2020 at 06:01:03PM +, Scarlett Gately Moore wrote: > Date: Fri, 13 Nov 2020 18:01:03 + > From: Scarlett Gately Moore > To: 974538-submit...@bugs.debian.org > Subject: Bug#974538 marked as pending in kscreenlocker > > Control: tag -1 pending > > Hello, > > Bug #974538 in kscreenlocker 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/qt-kde-team/kde/kscreenlocker/-/commit/5b5d09c5a06caa20d0b94d225a6a9c7725943887 > > > Fix "kwin cannot start due to missing libkscreenunlocker5 symbols" > A symbols file was introduced this release in packaging, > in transition an ABI breakage was exposed in kwin-common. > To resolve: added a Breaks to kwin-common < this release > to ensure the new version is installed to avoid the > ABI breakage. Thanks to Norb for suggestion. (Closes: #974538) > > > (this message was generated automatically) > -- > Greetings > > https://bugs.debian.org/974538 > --- End Message ---
Bug#973786: rclone-browser: diff for NMU version 1.8.0-1.2
Control: tags 973786 + pending
Dear maintainer,
I've prepared an NMU for rclone-browser (versioned as 1.8.0-1.2) and
uploaded it to DELAYED/1. Please feel free to tell me if I should cancel it.
cu
Adrian
diff -Nru rclone-browser-1.8.0/debian/changelog rclone-browser-1.8.0/debian/changelog
--- rclone-browser-1.8.0/debian/changelog 2020-10-25 04:34:08.0 +0200
+++ rclone-browser-1.8.0/debian/changelog 2021-02-06 21:31:46.0 +0200
@@ -1,3 +1,10 @@
+rclone-browser (1.8.0-1.2) unstable; urgency=medium
+
+ * Non-maintainer upload.
+ * Build without -Werror. (Closes: #973786)
+
+ -- Adrian Bunk Sat, 06 Feb 2021 21:31:46 +0200
+
rclone-browser (1.8.0-1.1) unstable; urgency=medium
* Non-maintainer upload.
diff -Nru rclone-browser-1.8.0/debian/patches/no-Werror.patch rclone-browser-1.8.0/debian/patches/no-Werror.patch
--- rclone-browser-1.8.0/debian/patches/no-Werror.patch 1970-01-01 02:00:00.0 +0200
+++ rclone-browser-1.8.0/debian/patches/no-Werror.patch 2021-02-06 21:31:46.0 +0200
@@ -0,0 +1,15 @@
+Description: Build without -Werror
+Author: Adrian Bunk
+Bug-Debian: https://bugs.debian.org/973786
+
+--- rclone-browser-1.8.0.orig/src/CMakeLists.txt
rclone-browser-1.8.0/src/CMakeLists.txt
+@@ -10,7 +10,7 @@ endif()
+ if(WIN32)
+ set(CMAKE_CXX_FLAGS "${CMAKE_CXX_FLAGS} /W4 /WX /wd4100 /wd4189")
+ else()
+- add_definitions("-pedantic -Wall -Wextra -Werror -std=c++11")
++ add_definitions("-pedantic -Wall -Wextra -std=c++11")
+ endif()
+
+ if (APPLE)
diff -Nru rclone-browser-1.8.0/debian/patches/series rclone-browser-1.8.0/debian/patches/series
--- rclone-browser-1.8.0/debian/patches/series 1970-01-01 02:00:00.0 +0200
+++ rclone-browser-1.8.0/debian/patches/series 2021-02-06 21:31:46.0 +0200
@@ -0,0 +1 @@
+no-Werror.patch
Processed: rclone-browser: diff for NMU version 1.8.0-1.2
Processing control commands: > tags 973786 + pending Bug #973786 [src:rclone-browser] rclone-browser FTBFS due to -Werror=deprecated-declarations Added tag(s) pending. -- 973786: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=973786 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#835340: Bug#938076: python-pymetar: Python2 removal in sid/bullseye
On Sun, 19 Jul 2020 03:46:12 +0200, gregor herrmann wrote: > Control: tag 835340 + patch > Control: tag 938076 + patch > > On Fri, 30 Aug 2019 07:45:06 +, Matthias Klose wrote: > > > Your package either build-depends, depends on Python2, or uses Python2 > > in the autopkg tests. Please stop using Python2, and fix this issue > > by one of the following actions. > > I looked into preparing an NMU with the new upstream release in order > to fix #835340 and #938076. > > Find attached the full debdiff and the filtered debdiff with only the > debian/* files. > > I tried to find a balance between doing all necessary changes and not > completely overhauling the packaging. It seems that the resulting > binary package works, both the commandline script and the module in > ipython3, but as I'm not a python person I'd welcome reviews and > suggestions for improvement. I don't feel confident uploading this NMU myself but I'd like to see python-pymetar in bullseye. Is this something the Debian Python Team could take over? Cheers, gregor -- .''`. https://info.comodo.priv.at -- Debian Developer https://www.debian.org : :' : OpenPGP fingerprint D1E1 316E 93A7 60A8 104D 85FA BB3A 6801 8649 AA06 `. `' Member VIBE!AT & SPI Inc. -- Supporter Free Software Foundation Europe `- NP: Rolling Stones signature.asc Description: Digital Signature
Bug#982102: php-oscarotero-gettext: Useless in Bullseye
Package: php-oscarotero-gettext Version: 4.8.2-4 Severity: serious X-Debbugs-Cc: jvalle...@mailbox.org -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 This is a dependency only for shaarli, which will not be included in Bullseye. - -- System Information: Debian Release: bullseye/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.10.0-2-amd64 (SMP w/4 CPU threads) Kernel taint flags: TAINT_WARN, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages php-oscarotero-gettext depends on: ii php-common 2:76 ii php-gettext-languages 2.6.0-2 php-oscarotero-gettext recommends no packages. php-oscarotero-gettext suggests no packages. - -- no debconf information -BEGIN PGP SIGNATURE- iQJKBAEBCgA0FiEEfWrbdQ+RCFWJSEvmd8DHXntlCAgFAmAes48WHGp2YWxsZXJv eUBtYWlsYm94Lm9yZwAKCRB3wMdee2UICCNBD/9fyzcLC05VWhvwtRCnhjl2OJD+ 1zuZScGKVa+lJu/O+5trezN+dZ67LYGIIpbuulKpesRTlaphxmn/5sX4t90RAFea Xkv2hyw+b27bsoZKxduMtbYn+LZvkIjpYVs7Pmws/LYEHd4WV5zCX8BB97dtSEGW D3Mm2MlI+kmLkm87/YsUwhV1nLPI7ovJAMZsFP1gSSJPyU5ihKwJa17wBsyojy80 Exm/WzunwASIqv+muyw0dPTvZbpJ673dN8ytrLJYQKsZ6zhSCGjuIo9maI4w4yW/ RXw+pofpaTxSlsSl6IFstb+Hh8fDv+XgPEioxWJnkdFp2FzsQuUh0oWqueXj0kVY 30u571/5ZWKf235zk8nRMhtr9ztT5/XOawlveQNKjskpcUyOMfFNEtFbAzS2TbNS uDYOcL2jQcU2NFT/pUxLrGgY62K0JukMGf6nSVh5eXidL2lM8Nn1c+OHchGvKMoN RpDSTLt5+i4NeL2pTw8EfsNVAWGa76g24dRlGjqn9wigjHNte94FjBEjFb+tIbJN PBqxqtpkFA6znUViYftCLEfbXOVM0UEV/d25LZiKpGX6ngmeHkRfga6kFqudYytw rcOpSGXyYt8z3mejPWp6awKephQJg6R1i1/PvhxeIKMdOQswjLMpC5q5yC/DrDIR Te5M+R9/Oalcl0vO5Q== =WinL -END PGP SIGNATURE-
Bug#950094: ipywidgets FTBFS with node-semver 7.1.1-2
On Sat, Feb 06, 2021 at 04:05:20PM +0100, Ivo De Decker wrote: > Control: tags -1 patch > > Hi, > > On Tue, Jan 28, 2020 at 11:43:47PM +0200, Adrian Bunk wrote: > > Source: ipywidgets > > Version: 6.0.0-6 > > Severity: serious > > Tags: ftbfs > > This is fixed in git: > > https://salsa.debian.org/python-team/packages/ipywidgets/-/commit/23daf45a127b3febe25ecefdbb7148b0f5049990 > > Gordon, are you planning to upload this soon? The soft freeze is pretty close > now. > The FTBFS bugs are fixed, in the sense that I have redone the build system reflecting all the changes that have happened to the parent libraries, and the basic build sequence runs without error. However, the resultant object doesn't actually work (yet). I'll upload it iff I can get something working before the freeze dates. > Thanks! > > Ivo >
Processed: reassign 973613 to src:linux
Processing commands for cont...@bugs.debian.org: > reassign 973613 src:linux 5.9.1-1 Bug #973613 [cifs-utils] cifs-utils: CIFS kernel module crash Bug reassigned from package 'cifs-utils' to 'src:linux'. No longer marked as found in versions cifs-utils/2:6.9-1. Ignoring request to alter fixed versions of bug #973613 to the same values previously set Bug #973613 [src:linux] cifs-utils: CIFS kernel module crash Marked as found in versions linux/5.9.1-1. > thanks Stopping processing here. Please contact me if you need assistance. -- 973613: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=973613 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: severity of 966301 is important
Processing commands for cont...@bugs.debian.org: > # builds for now with tests disabled > severity 966301 important Bug #966301 [src:guile-2.2] guile oom test fails on ppc64el Severity set to 'important' from 'serious' > thanks Stopping processing here. Please contact me if you need assistance. -- 966301: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=966301 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#935115: marked as done (bash: [regression] passing variable assignments to functions broken in POSIX mode, violating POSIX)
Your message dated Sat, 6 Feb 2021 19:49:30 +0100
with message-id <20210206184928.ga30...@debian.org>
and subject line Re: bash: [regression] passing variable assignments to
functions broken in POSIX mode, violating POSIX
has caused the Debian Bug report #935115,
regarding bash: [regression] passing variable assignments to functions broken
in POSIX mode, violating POSIX
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.)
--
935115: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=935115
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: bash
Version: 5.0-4
Severity: critical
Justification: breaks unrelated software
Found this gem in #934027:
tglase@tglase:~ $ cat testscript
dbc_mysql_createdb(){
local ret l_dbname _dbc_nodb
echo "dbc_mysql_createdb: _dbc_nodb(1)=$_dbc_nodb"
_dbc_nodb="yes" dbc_mysql_exec_command "CREATE DATABASE
\`$dbc_dbname\`${extrasql:-}"
ret=$?
echo "dbc_mysql_createdb: _dbc_nodb(2)=$_dbc_nodb" # POSIX:
unspecified
/usr/bin/env | fgrep -c _dbc_nodb | sed 's/^/after: /' # POSIX:
unspecified
echo dbc_mysql_createdb:$ret
}
dbc_mysql_exec_command(){
local statement l_sqlfile l_retval
statement="$@"
l_retval=0
echo "dbc_mysql_exec_command: _dbc_nodb=$_dbc_nodb" # POSIX:
required
/usr/bin/env | fgrep -c _dbc_nodb | sed 's/^/inner: /' # POSIX:
unspecified
return $l_retval
}
dbc_mysql_createdb
tglase@tglase:~ $ dash testscript
dbc_mysql_createdb: _dbc_nodb(1)=
dbc_mysql_exec_command: _dbc_nodb=yes
inner: 0
dbc_mysql_createdb: _dbc_nodb(2)=yes
after: 0
dbc_mysql_createdb:0
tglase@tglase:~ $ ksh -c 'alias local=typeset; . ./testscript'
dbc_mysql_createdb: _dbc_nodb(1)=
dbc_mysql_exec_command: _dbc_nodb=yes
inner: 0
dbc_mysql_createdb: _dbc_nodb(2)=yes
after: 0
dbc_mysql_createdb:0
tglase@tglase:~ $ lksh -o posix testscript # native mksh +o posix is identical
dbc_mysql_createdb: _dbc_nodb(1)=
dbc_mysql_exec_command: _dbc_nodb=yes
inner: 1
dbc_mysql_createdb: _dbc_nodb(2)=yes
after: 1
dbc_mysql_createdb:0
tglase@tglase:~ $ posh testscript
dbc_mysql_createdb: _dbc_nodb(1)=
dbc_mysql_exec_command: _dbc_nodb=yes
inner: 1
dbc_mysql_createdb: _dbc_nodb(2)=
after: 0
dbc_mysql_createdb:0
tglase@tglase:~ $ yash testscript
dbc_mysql_createdb: _dbc_nodb(1)=
dbc_mysql_exec_command: _dbc_nodb=yes
inner: 1
dbc_mysql_createdb: _dbc_nodb(2)=
after: 0
dbc_mysql_createdb:0
tglase@tglase:~ $ zsh -c 'emulate sh; . ./testscript'
dbc_mysql_createdb: _dbc_nodb(1)=
dbc_mysql_exec_command: _dbc_nodb=yes
inner: 1
dbc_mysql_createdb: _dbc_nodb(2)=yes
after: 1
dbc_mysql_createdb:0
tglase@tglase:~ $ bash --version 2>&1 | head -1
GNU bash, version 5.0.3(1)-release (x86_64-pc-linux-gnux32)
tglase@tglase:~ $ bash testscript
dbc_mysql_createdb: _dbc_nodb(1)=
dbc_mysql_exec_command: _dbc_nodb=yes
inner: 1
dbc_mysql_createdb: _dbc_nodb(2)=
after: 0
dbc_mysql_createdb:0
tglase@tglase:~ $ bash --posix testscript
dbc_mysql_createdb: _dbc_nodb(1)=
dbc_mysql_exec_command: _dbc_nodb=
inner: 1
dbc_mysql_createdb: _dbc_nodb(2)=
after: 1
dbc_mysql_createdb:0
tglase@tglase:~ $ schroot -prc stretch
(stretch-i386)tglase@tglase:~ $ bash --version 2>&1 | head -1
GNU bash, version 4.4.12(1)-release (i686-pc-linux-gnu)
(stretch-i386)tglase@tglase:~ $ bash testscript
dbc_mysql_createdb: _dbc_nodb(1)=
dbc_mysql_exec_command: _dbc_nodb=yes
inner: 1
dbc_mysql_createdb: _dbc_nodb(2)=
after: 0
dbc_mysql_createdb:0
(stretch-i386)tglase@tglase:~ $ bash --posix testscript
dbc_mysql_createdb: _dbc_nodb(1)=
dbc_mysql_exec_command: _dbc_nodb=yes
inner: 1
dbc_mysql_createdb: _dbc_nodb(2)=yes
after: 1
dbc_mysql_createdb:0
The expected output is:
dbc_mysql_createdb: _dbc_nodb(1)= # initially not set / empty
dbc_mysql_exec_command: _dbc_nodb=yes # MUST be visible inside the function
inner: 0 or 1 # MAY be exported, does not need to
dbc_mysql_createdb: _dbc_nodb(2)=[yes] # MAY be visible afterwards, optional
after: 0 or 1 # if visible afterwards MAY be exported
dbc_mysql_createdb:0
POSIX reference:
http://pubs.opengroup.org/onlinepubs/9699919799/utilities/V3_chap02.html#tag_18_09_01
specifically:
* If the command name is a function that is not a standard utility
implemented as a function, variable assignments shall affect the
current execution environment during the execution of the function.
It is unspecified:
+ Whether or not the variable assignments persist after the
completion of the function
+ Whether or not the variables gain
Bug#982094: php-slim: Useless in Bullseye
Package: php-slim Version: 3.12.3-4 Severity: serious X-Debbugs-Cc: jvalle...@mailbox.org -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 This is a dependency for shaarli, which will not be included in Bullseye. - -- System Information: Debian Release: bullseye/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.10.0-2-amd64 (SMP w/4 CPU threads) Kernel taint flags: TAINT_WARN, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages php-slim depends on: ii php-common 2:76 ii php-nikic-fast-route1.3.0-3 ii php-pimple 3.3.1-1 ii php-psr-container 1.0.0-2 ii php-psr-http-message1.0.1-2 ii php-xml 2:7.4+76 ii php7.4-json [php-json] 7.4.14-1 ii php7.4-xml [php-xml]7.4.14-1 ii php8.0-xml [php-xml]8.0.1-1 php-slim recommends no packages. php-slim suggests no packages. - -- no debconf information -BEGIN PGP SIGNATURE- iQJKBAEBCgA0FiEEfWrbdQ+RCFWJSEvmd8DHXntlCAgFAmAeq4EWHGp2YWxsZXJv eUBtYWlsYm94Lm9yZwAKCRB3wMdee2UICBasEAC6MEHrezlqiIrd0+M9AepDnEpR XyV7j9MOCZOXl30f+eKjNs2RsYoUsKRr8gMFSjtFxz5e3lkTHmSLHKZkDIH2UgGL JQKvKJqmtZY5RQN8eNpoN/6TnjYvZDFy2gXLm4yfL7jkDV2M0u8xNMp4yGk2tUGr D15uFLIEIbm6iB3WjIB9nAywMJOGtJv483x7Hb9FA7Cxp3bdZwi4b/jXnKg4zA1T D4e/DcFQSj+VhdCW9lGyB1E44XO28OmBhIpELjisiLZoEOvSMcXX7bYUnvs/pTKI Fc73ytbB0YTffVX+4GMwu4w+MZHPEo8wZ0rglLV+uoN0l6OzRS7e7F7RLS9kAsS+ hPpcfzTCB/haC7b/BfdQFgjCdelkAlGwVY7VaR+n338lGIBET+v+CAIiKJ/TVw2/ D2uDJQuLqQdQfUoihJ/hnnh4S3skpJnurtxzv6ht5VGgqQZ+g8LH7mTD3PHcWvwN vvmxUlW3brjVuqLqnSo+xU9hB/RsX/no1GXNxa9Sw7GrpERS4fzw7reiPf7Qbrrf NVRhXxACVOwpoKbgKR0zyjkXhYZGHtFkULUkoPZwtuOY8XZHL/rAmB2dH8RPtR1Q +XKF7NpSHCrB6wOSpriRuA3sg0Q8VLjjIaje2DdX1wVYnOpFQgVN9GIesWm2ijGH UURk0wiKDRktTiKt+w== =Wi75 -END PGP SIGNATURE-
Bug#982093: php-pubsubhubbub-publisher: Useless in Bullseye
Package: php-pubsubhubbub-publisher Version: 0~~20181009-2 Severity: serious X-Debbugs-Cc: jvalle...@mailbox.org -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 This is a dependency only for shaarli, which will not be included in Bullseye. - -- System Information: Debian Release: bullseye/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.10.0-2-amd64 (SMP w/4 CPU threads) Kernel taint flags: TAINT_WARN, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages php-pubsubhubbub-publisher depends on: ii php-common 2:76 ii php-curl2:7.4+76 ii php7.4-curl [php-curl] 7.4.14-1 php-pubsubhubbub-publisher recommends no packages. php-pubsubhubbub-publisher suggests no packages. - -- no debconf information -BEGIN PGP SIGNATURE- iQJKBAEBCgA0FiEEfWrbdQ+RCFWJSEvmd8DHXntlCAgFAmAeqy8WHGp2YWxsZXJv eUBtYWlsYm94Lm9yZwAKCRB3wMdee2UICHafD/0XNK9rmQZfatvDMPZsek1Ir/Gb hrroVeLs8MhJEKOdenCc7uunBmCMmapKTei97wDelpFmcTRCPw0Y9ffE/MMA65Ku zx0pj6shDa4sGm6XtOyl73y644CsxbveuezAPX/gv7fdghpzZenOjsvsrfKUC/E9 uB5bBXsf+AChzpI49tdg69HpivZG+/0JyWJ+BIplOWyvFQP6ttzG+cwxqBjkv80v 2HY9yXK1uMZ2V2cZ5FjnFuS5IZsafRuHtS3tWDlSRfuM6VIVu2VOJ0vQXJi8L9EX hUXJnEgXdGrP1O06mXJ6AMtnf72rKQU3hEsJqNA+d3lMRImVhytGWeNnVgUNc187 TyuIPGYYm0va8Ch0RKNrnCXrNxaQnJhXbYYpHUh+mXWy16qn0F7YZ56hp9vqHD4G 0wlTPTQ3hx0BGhF4yCYJkkeZZOm62tUToiq1CIlsDD8lssclyG8LLlAphLzcVok2 bIFajF8gGYP7AygGA3Ba/lnYuVFud0Cr2SFGEEA4PWJntrSDRqF7p26YpDR+hJf+ WeuBUXt4qsB8FQ8ITQhxxptDMtNFrblc/j7C0DuHqZn6Ommlc/YLIYPSqqy/DiX7 a6ZkMbIPPTIn03zn/5YdBFEaP4NI/YoCm7DLYSLImv20vRFokxc4AORaQapGU4Lw i6+Es3SdIz7vffbqCA== =yZ5A -END PGP SIGNATURE-
Bug#982120: marked as done (heudiconv still depends on python)
Your message dated Sat, 06 Feb 2021 18:35:05 + with message-id and subject line Bug#982120: fixed in heudiconv 0.9.0-2 has caused the Debian Bug report #982120, regarding heudiconv still depends on python 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.) -- 982120: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=982120 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: heudiconv Version: 0.9.0-1 Severity: serious This looks like a forgotten conversion: https://sources.debian.org/src/heudiconv/0.9.0-1/debian/control/#L28 --- End Message --- --- Begin Message --- Source: heudiconv Source-Version: 0.9.0-2 Done: Yaroslav Halchenko We believe that the bug you reported is fixed in the latest version of heudiconv, 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 982...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Yaroslav Halchenko (supplier of updated heudiconv package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Sat, 06 Feb 2021 12:24:25 -0500 Source: heudiconv Architecture: source Version: 0.9.0-2 Distribution: unstable Urgency: medium Maintainer: NeuroDebian Team Changed-By: Yaroslav Halchenko Closes: 923170 982120 Changes: heudiconv (0.9.0-2) unstable; urgency=medium . * Replace python with python3 as a Depends (Closes: #982120) * Suppress warnings from python while producing manpages to make build reproducible. Thanks Chris Lamb (Closes: #923170) * debian/patches + 0001-BF-datalad-use-public-call_git-added-in-0.12.0-not-d.patch for compatibility with datalad 0.14 which deprecated a protected method Checksums-Sha1: e6b14158cef6584b6494e704fa360fd6004d1b75 2169 heudiconv_0.9.0-2.dsc f48aac3ea4f1cf0d00979a595aad59435fc52f3c 4416 heudiconv_0.9.0-2.debian.tar.xz 8d0195dd9dc5ca6d5dc7e1dfdd611b3a4de75f5a 10391 heudiconv_0.9.0-2_source.buildinfo Checksums-Sha256: b5daa0e3669e80d1177d486f07918fde3975d7936703813f56c8ccac163f190f 2169 heudiconv_0.9.0-2.dsc 3f37adf300e013723eddc772ba11ec318591f44076476ec10fe6097ab02a4546 4416 heudiconv_0.9.0-2.debian.tar.xz a46701990b78e9f13a75482fc97985a2e250754fe7fba8b06e75bf225d5cedb9 10391 heudiconv_0.9.0-2_source.buildinfo Files: d7234d3de2dfa517baed361bbdb744bf 2169 science optional heudiconv_0.9.0-2.dsc bb5891fe6721e6b92d906195ca72ea16 4416 science optional heudiconv_0.9.0-2.debian.tar.xz dbd055e180bf7b3b04ba01289d1230ce 10391 science optional heudiconv_0.9.0-2_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEExbkF8OjZ/ZZo/zZvot4jUGLaM/oFAmAe2oEACgkQot4jUGLa M/qT0xAAssCQJEp4GNLqcwEI2t9grH+HF9NjeIdT7Wbq8STuQVvpYso4irVv0c1Q yWbTgUWg+Bo/vnZ/o65k6RbEPBdymtrG2GK5kTyvh6HzD/wMEH+d02TixBzCKekl G7hJ05W76G7/z8oHg6ZdctXYBzeh5lpWH39uv9peBLMOstWDqnoRWvgNVwSJ0vAt QEAAOcBGyvWHyTzb6czsGX3A09z5VrFCfVwxkL4RHWUMiZSWFNlz9AqGiv1SJip5 UNL9K1EZsoY8twC6gYMIwerUTR9GF2xI7vsAWdcUeWlVsQ8Bnjw5qmX0cPKitcXU IHS2TwTBJ/qjiF63M26e8jx9+LI5RPGDrExqWF7zZnzbnlh8VmlYa4/GsXofzfzA AE6c1dTIGGT+sYIZ78lDFMf1KA23Dg+sZ6Pl+PDGCCCIL9G5TGgMaHIZqJiowtPy idg6rfzlIw3h4+r/6B8AZEWaW1HWyG8AOnKd59NFEi4lZLHd9Au0TBHphaZfLmyB E15apG6LFhiTBt2DYYrpUc9WrG4B1jW1JvLinf7KmllpWe7cUuqqtp6a4auDjRyC UEWIhF8qHAtZArib3LJzNWMgoOa5q3MpV4Ft9tLUdLj7teH603CKWyFtaf7RfKR7 iWMICSUGugQFehVG0IZcHCyWZpniMjiI1V5LH9BQROWJN/dg1ec= =Pnss -END PGP SIGNATURE End Message ---
Bug#981840: marked as done (libslirp-helper crashes a few seconds after connection)
Your message dated Sat, 06 Feb 2021 18:35:33 + with message-id and subject line Bug#981840: fixed in rust-libslirp 4.3.0-3 has caused the Debian Bug report #981840, regarding libslirp-helper crashes a few seconds after connection to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 981840: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=981840 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: libslirp-helper Version: 4.3.0-2 Severity: grave Justification: renders package unusable Dear Maintainer, libslirp-helper crashes a few seconds after connection without any explanation on stdout or stderr, even with --debug flag set and RUST_BACKTRACE enabled. Debos and Fakemachine use libslirp-helper under the hood for networking, to create a bridge network for the inner virtual machine to the outside world. This can be tested by installing the fakemachine package and running fakemachine using the uml backend, then trying to connect to the network: $ fakemachine --backend uml wget http://google.com As you can see, the libslirp-helper process which is started by fakemachine quits. >From investigation, I think this is because libslirp-helper was patched to be compiled with an older version of the mio crate (0.6.16) while the libslirp-helper Cargo.toml requires a newer version of mio (0.6.19). These dependencies for this package were relaxed since mio version 0.6.16 was already packaged for debian. When manually building the package with mio version 0.6.16, I get the same error described above. So I am pretty sure that bumping mio will sort this out. -- System Information: Debian Release: bullseye/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.10.0-1-amd64 (SMP w/8 CPU threads) Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), LANGUAGE=en_GB:en Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages libslirp-helper depends on: ii libc6 2.31-9 ii libgcc-s1 10.2.1-3 ii libslirp0 4.4.0-1 libslirp-helper recommends no packages. libslirp-helper suggests no packages. -- no debconf information --- End Message --- --- Begin Message --- Source: rust-libslirp Source-Version: 4.3.0-3 Done: Peter Michael Green We believe that the bug you reported is fixed in the latest version of rust-libslirp, 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 981...@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-libslirp package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Sat, 06 Feb 2021 18:11:59 + Source: rust-libslirp Architecture: source Version: 4.3.0-3 Distribution: unstable Urgency: medium Maintainer: Debian Rust Maintainers Changed-By: Peter Michael Green Closes: 981840 Changes: rust-libslirp (4.3.0-3) unstable; urgency=medium . * Team upload. * Package libslirp 4.3.0 from crates.io using debcargo 2.4.4 * Don't relax dependency on mio, it seems the newer version is actually needed ( Closes: 981840 ) * Set collapse_features = true, it seems that the features were already collapsed in the package that was uploaded, perhaps this was done manually. Checksums-Sha1: 8f2bfd7595dd50bf291ae0c858c81a2475ca2c99 2824 rust-libslirp_4.3.0-3.dsc 32955c711279ffb19baf8e9628b12358854424c2 3804 rust-libslirp_4.3.0-3.debian.tar.xz 24a098877f45e30ce81d1b3d03ba30ccfc0264af 11052 rust-libslirp_4.3.0-3_source.buildinfo Checksums-Sha256: a21cea94b3a313038b0a1147301c3b8c9c8bf34e3233aa637c4021204c4ef431 2824 rust-libslirp_4.3.0-3.dsc 3cf4fc89a6c7af157db66ba3c955c239fe71b5c5f7290f55c9a5c32681080115 3804 rust-libslirp_4.3.0-3.debian.tar.xz 1ced2c111404a4a17fe8c5add0230a5b4e95e9bfe84d44d9109fe50fe511defd 11052 rust-libslirp_4.3.0-3_source.buildinfo Files: 5f64df1032cb55535f226209a78e7b95 2824 rust optional rust-libslirp_4.3.0-3.dsc ab5330e6b49aa537fe6903a5e5590ccc 3804 rust optional rust-libslirp_4.3.0-
Bug#982138: sqlitebrowser: Crash when clicking "database" button
Package: sqlitebrowser Version: 3.12.0-0~2756~202008212354~ubuntu16.04.1 Severity: grave Justification: renders package unusable Dear Maintainer, The program crash when clicking the "database" button with message : sqlitebrowser: symbol lookup error: /usr/lib/x86_64-linux-gnu/libQt5Core.so.5: undefined symbol: ucol_open_63 Regards JP P -- System Information: Debian Release: 10.8 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'proposed-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 5.9.0-0.bpo.5-amd64 (SMP w/4 CPU cores) Kernel taint flags: TAINT_UNSIGNED_MODULE Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), LANGUAGE=C (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages sqlitebrowser depends on: ii libc62.28-10 ii libgcc1 1:8.3.0-6 ii libqt5core5a 5.11.3+dfsg1-1+deb10u4 ii libqt5gui5 5.11.3+dfsg1-1+deb10u4 ii libqt5network5 5.11.3+dfsg1-1+deb10u4 ii libqt5printsupport5 5.11.3+dfsg1-1+deb10u4 ii libqt5widgets5 5.11.3+dfsg1-1+deb10u4 ii libqt5xml5 5.11.3+dfsg1-1+deb10u4 ii libsqlcipher03.4.1-1+b12 ii libstdc++6 8.3.0-6 sqlitebrowser recommends no packages. sqlitebrowser suggests no packages. -- no debconf information
Bug#982092: php-arthurhoaro-web-thumbnailer: Useless in Bullseye
Package: php-arthurhoaro-web-thumbnailer Version: 2.0.3+dfsg-1 Severity: serious X-Debbugs-Cc: jvalle...@mailbox.org -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 This package is only needed for Shaarli, which will not be included in Bullseye. - -- System Information: Debian Release: bullseye/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.10.0-2-amd64 (SMP w/4 CPU threads) Kernel taint flags: TAINT_WARN, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages php-arthurhoaro-web-thumbnailer depends on: ii php-common 2:76 ii php-curl2:7.4+76 ii php-gd 2:7.4+76 ii php-text-template 2.0.4-1 ii php7.4-curl [php-curl] 7.4.14-1 ii php7.4-gd [php-gd] 7.4.14-1 php-arthurhoaro-web-thumbnailer recommends no packages. php-arthurhoaro-web-thumbnailer suggests no packages. - -- no debconf information -BEGIN PGP SIGNATURE- iQJKBAEBCgA0FiEEfWrbdQ+RCFWJSEvmd8DHXntlCAgFAmAepxoWHGp2YWxsZXJv eUBtYWlsYm94Lm9yZwAKCRB3wMdee2UICNttD/9Mmz7tphPQ+sLlRiGzLGnirKgC xgc0P9IbZgOyOcJLA9N7rZ7bKA2YS76jzYcS0kj0Gb0pcTKcFZ5rQbRWOu120ayk TchnvTERCLonFetNI9pTV50V80J5qgyPPyRvCX1BPp9I29ZG/8E3AR3ibO9EKgl3 9iAgDHDJbzREQSyiT4vECH8zBCkifkLy2tJJhg5Mnf2XOXrXt7OFs8FLQ6WSKfQd K4nPYDvC/toIiGHUw2CXkBF0oTLqAs2sLKWULhhrhzHb6FxmDayf5YMdyNtCX1TV 1r/GVcEYfXvpy2wB59sQu39+Qmdb4KJGnxtHD4ZcPST6ghbZ7OgZkELIJiv435Qi Vlyol3Jo0EZo54EDG7V8SOvPKuQ31ikVqudNNka4XvuytyMjsfIfQho+2A6MeUp8 921OEAcNuA1S7A52PMJ4AbYM8yEJvx3M2gzMm1v/h9e0GwZLyGa0t/i8Qysp70bj pAVE0T8sj90iNrDmB0demcfMr1pSIpK+KqrTJvbGMTB7q4owoe5r5Ia8N07FaaIV ruBf5BRuwJmLGk88DXYPuYU89HZ2hCx9JWCkBskRtlSgTbXqk/PUET9z3QASvAq4 817GW8MgHIIfbsRKUTqNUGnooudfKpkqAj7kIIifPj1Q2zupvRixqaeg+8ttI/Li R1kKCUxhXDgHy0wQ1A== =t581 -END PGP SIGNATURE-
Processed: tagging 981300
Processing commands for cont...@bugs.debian.org: > tags 981300 + pending Bug #981300 [arduino-mk] arduino-mk: needs to depend on arduino 2:1.8.13+dfsg1-1 Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 981300: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=981300 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#982119: marked as done (dcmstack: autopkgtest failure)
Your message dated Sat, 06 Feb 2021 18:18:42 + with message-id and subject line Bug#982119: fixed in dcmstack 0.8-2 has caused the Debian Bug report #982119, regarding dcmstack: 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.) -- 982119: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=982119 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: dcmstack Version: 0.8-1 Severity: serious https://ci.debian.net/data/autopkgtest/testing/amd64/d/dcmstack/10273343/log.gz ... autopkgtest [00:00:03]: test command1: nosetests-3 . autopkgtest [00:00:03]: test command1: [--- bash: line 1: nosetests-3: command not found autopkgtest [00:00:04]: test command1: ---] autopkgtest [00:00:04]: test command1: - - - - - - - - - - results - - - - - - - - - - command1 FAIL non-zero exit status 127 --- End Message --- --- Begin Message --- Source: dcmstack Source-Version: 0.8-2 Done: Yaroslav Halchenko We believe that the bug you reported is fixed in the latest version of dcmstack, 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 982...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Yaroslav Halchenko (supplier of updated dcmstack package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Sat, 06 Feb 2021 12:29:32 -0500 Source: dcmstack Architecture: source Version: 0.8-2 Distribution: unstable Urgency: medium Maintainer: NeuroDebian Team Changed-By: Yaroslav Halchenko Closes: 982119 Changes: dcmstack (0.8-2) unstable; urgency=medium . * Replace nosetests-3 with python3 -m nose for autopkgtest invocation (Closes: #982119) Checksums-Sha1: 47f4a3e839302afdb83cd6b002ac99eee9c49202 2187 dcmstack_0.8-2.dsc 73575518911ea26b435a0ba557623b0884875411 3572 dcmstack_0.8-2.debian.tar.xz c17e446a275d0a134842e7a8f506407bb27c6dbb 7904 dcmstack_0.8-2_source.buildinfo Checksums-Sha256: 76ab3ea85092e9c2f048bd05127d427cabb4a81bcb02adc9f380b7ca89d212e6 2187 dcmstack_0.8-2.dsc 68856596a34b9fbdb91bc8d639fb694a048fb8d1daacce520229dce4cf5ec66a 3572 dcmstack_0.8-2.debian.tar.xz d65e554283ba0eefa4de63c9fa2c3e0c3bc0cb2a4c05f1c669863153da319e3f 7904 dcmstack_0.8-2_source.buildinfo Files: f2e9d4283fab53a63f7555d76d6bb6a3 2187 science optional dcmstack_0.8-2.dsc 9ba39fd54c2dbaa82d1e27f5f9e14a90 3572 science optional dcmstack_0.8-2.debian.tar.xz 67a3d4b283ecfb991c6dec5c276d8b1c 7904 science optional dcmstack_0.8-2_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEExbkF8OjZ/ZZo/zZvot4jUGLaM/oFAmAe0goACgkQot4jUGLa M/reRQ//dxjU8BpqAsb80H1Jvr3P0IDvI1sC0oNFTuaK02gPwm20FNlyXN+pGL6j vVLX4iI47X6q21n1YwSKsXw5SkGC/Lg/sD7ObhuHgg3Z5xqP0av02gDznWeOGncq HTFgHtksjUt+LvFi+O23/b0OgddQqhkEn+Mi+6T37OujwW2ksDKwqhe3hxfkh8Mm sw2t4RjtE6AYtboWAGPInbRxEmUlGz+q5U5BHjE3MngDKSTIILxNK45nOavt+6g1 Iq//POVOes53IV1IBl6ASsA1EiD06n1SvZjwNAeXx1W9/uTN0UDkgbD1rcbJ6coo sreZZ6bJU3OQWBdzPHxUrva5FaIlVlLzet2EQgA/IqDZL6r52boS7wXCT2Q18sHF u6csjNykoygVOS/HHZoyMgcdmvFLXDzpq4bZ38A+j3my5C50WwSvlqnHzheWQ8E6 MJq4eRueckgPHtXvHkb8VCgpUsBNmZfsw66kzHiDtOs9iZHgGhUKOqNbLMBu55fg vVsRdXFba26xS0f8SNZfP48CdpEEV4tgpqEV20IN7QvCwqZhsZNnw+d03pf4M3WK HsXwKZF1YuauIoq776iepbtziyWMV+IcfA6kcK17mtSZqpWzUeLYEL9iGuy0v+Hu KooMmllElSxvCrDd/neb3uuLhNz/VjNenbahrIwHbzUaYuwVm0I= =ol4+ -END PGP SIGNATURE End Message ---
Bug#982134: python-redis: autopkgtest regression in 3.5.3-1
Source: python-redis
Version: 3.5.3-1
Severity: serious
https://ci.debian.net/data/autopkgtest/testing/amd64/p/python-redis/10295105/log.gz
...
autopkgtest [23:45:04]: test 0002-python3: [---
+ py3versions -r
+ python3.9 setup.py test
running test
WARNING: Testing via this command is deprecated and will be removed in a future
version. Users looking for a generic test entry point independent of test
runner are encouraged to use tox.
running egg_info
creating redis.egg-info
writing redis.egg-info/PKG-INFO
writing dependency_links to redis.egg-info/dependency_links.txt
writing requirements to redis.egg-info/requires.txt
writing top-level names to redis.egg-info/top_level.txt
writing manifest file 'redis.egg-info/SOURCES.txt'
reading manifest file 'redis.egg-info/SOURCES.txt'
reading manifest template 'MANIFEST.in'
warning: no previously-included files found matching '__pycache__'
warning: no previously-included files matching '*.pyc' found under directory
'tests'
writing manifest file 'redis.egg-info/SOURCES.txt'
running build_ext
Traceback (most recent call last):
File "/tmp/autopkgtest-lxc.gmifqghe/downtmp/build.ljt/src/setup.py", line 4,
in
setup()
File "/usr/lib/python3/dist-packages/setuptools/__init__.py", line 153, in
setup
return distutils.core.setup(**attrs)
File "/usr/lib/python3.9/distutils/core.py", line 148, in setup
dist.run_commands()
File "/usr/lib/python3.9/distutils/dist.py", line 966, in run_commands
self.run_command(cmd)
File "/usr/lib/python3.9/distutils/dist.py", line 985, in run_command
cmd_obj.run()
File "/usr/lib/python3/dist-packages/setuptools/command/test.py", line 232,
in run
self.run_tests()
File "/usr/lib/python3/dist-packages/setuptools/command/test.py", line 250,
in run_tests
test = unittest.main(
File "/usr/lib/python3.9/unittest/main.py", line 100, in __init__
self.parseArgs(argv)
File "/usr/lib/python3.9/unittest/main.py", line 124, in parseArgs
self._do_discovery(argv[2:])
File "/usr/lib/python3.9/unittest/main.py", line 244, in _do_discovery
self.createTests(from_discovery=True, Loader=Loader)
File "/usr/lib/python3.9/unittest/main.py", line 154, in createTests
self.test = loader.discover(self.start, self.pattern, self.top)
File "/usr/lib/python3.9/unittest/loader.py", line 349, in discover
tests = list(self._find_tests(start_dir, pattern))
File "/usr/lib/python3.9/unittest/loader.py", line 405, in _find_tests
tests, should_recurse = self._find_test_path(
File "/usr/lib/python3.9/unittest/loader.py", line 483, in _find_test_path
tests = self.loadTestsFromModule(package, pattern=pattern)
File "/usr/lib/python3/dist-packages/setuptools/command/test.py", line 50, in
loadTestsFromModule
tests.append(self.loadTestsFromName(submodule))
File "/usr/lib/python3.9/unittest/loader.py", line 154, in loadTestsFromName
module = __import__(module_name)
File
"/tmp/autopkgtest-lxc.gmifqghe/downtmp/build.ljt/src/tests/test_connection_pool.py",
line 11, in
from .test_pubsub import wait_for_message
File
"/tmp/autopkgtest-lxc.gmifqghe/downtmp/build.ljt/src/tests/test_pubsub.py",
line 470, in
class TestPubSubSubcommands(object):
File
"/tmp/autopkgtest-lxc.gmifqghe/downtmp/build.ljt/src/tests/test_pubsub.py",
line 472, in TestPubSubSubcommands
@skip_if_server_version_lt('2.8.0')
File "/tmp/autopkgtest-lxc.gmifqghe/downtmp/build.ljt/src/tests/conftest.py",
line 44, in skip_if_server_version_lt
redis_version = REDIS_INFO["version"]
KeyError: 'version'
autopkgtest [23:45:05]: test 0002-python3: ---]
autopkgtest [23:45:05]: test 0002-python3: - - - - - - - - - - results - - - -
- - - - - -
0002-python3 FAIL non-zero exit status 1
...
0002-python3 FAIL non-zero exit status 1
0003-interaction PASS
Bug#982120: heudiconv still depends on python
Thanks, on it. also needs a patch now for datalad 0.14 deprecation On Sat, 06 Feb 2021, Adrian Bunk wrote: > Package: heudiconv > Version: 0.9.0-1 > Severity: serious > This looks like a forgotten conversion: > https://sources.debian.org/src/heudiconv/0.9.0-1/debian/control/#L28 -- Yaroslav O. Halchenko Center for Open Neuroscience http://centerforopenneuroscience.org Dartmouth College, 419 Moore Hall, Hinman Box 6207, Hanover, NH 03755 WWW: http://www.linkedin.com/in/yarik
Bug#934482: marked as done (prctl: probably shouldn't be in testing/stable)
Your message dated Sat, 6 Feb 2021 20:12:13 +0200 with message-id <20210206181213.GA8533@localhost> and subject line Re: Bug#934482: prctl: probably shouldn't be in testing/stable has caused the Debian Bug report #934482, regarding prctl: probably shouldn't be in testing/stable 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.) -- 934482: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=934482 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- package: prctl severity: serious version: 1.6-1 Hi, The buildd 'Packages-arch-specific' configuration has this line for prct: %prctl: hppa ia64 alpha powerpc # ANAIS based on syscall availability https://buildd.debian.org/quinn-diff/sid/Packages-arch-specific As can be seen from the buildd page, this means that it will never be built for any release architecture: https://buildd.debian.org/status/package.php?p=prctl However, prctl has a binary on am64. Either the Packages-arch-specific is wrong, or the package is unusable there and should be removed. If it doens't have a working binary on any release architecture, it shouldn't be in a release. Thanks, Ivo --- End Message --- --- Begin Message --- On Wed, Aug 14, 2019 at 03:55:50PM +0200, Andreas Beckmann wrote: > Control: tag -1 moreinfo > > On Sun, 11 Aug 2019 15:09:15 +0200 Ivo De Decker wrote: > > The buildd 'Packages-arch-specific' configuration has this line for prct: > > > > %prctl: hppa ia64 alpha powerpc # > > ANAIS based on syscall availability > > > > https://buildd.debian.org/quinn-diff/sid/Packages-arch-specific > > > > As can be seen from the buildd page, this means that it will never be built > > for any release architecture: > > > > https://buildd.debian.org/status/package.php?p=prctl > > > > However, prctl has a binary on am64. Either the Packages-arch-specific is > > wrong, or the package is unusable there and should be removed. > > > > If it doens't have a working binary on any release architecture, it > > shouldn't > > be in a release. > > The package builds for me on amd64, i386, armhf (pbuilder chroots, armhf > via qemu). The existing amd64 binary works, i.e. I was able to query and > change the mcekill setting. (More settings are not supported, maybe > architecture/kernel/cpu dependent). > > So maybe the packages-arch-specific setting is wrong. This has now been fixed: https://salsa.debian.org/wb-team/packages-arch-specific/-/commit/8f88ed63e942e55c8ad779888726547a39ea4b15 https://buildd.debian.org/status/package.php?p=prctl > Andreas cu Adrian--- End Message ---
Bug#956548: marked as done (python-cassandra-driver: FTBFS on 32 bit arches)
Your message dated Sat, 6 Feb 2021 20:03:20 +0200 with message-id <20210206180320.GA8070@localhost> and subject line 3.24.0-1 builds on 32bit has caused the Debian Bug report #956548, regarding python-cassandra-driver: FTBFS on 32 bit arches 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.) -- 956548: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=956548 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: python-cassandra-driver Version: 3.20.2-1 Severity: serious Tags: ftbfs sid bullseye Justification: fails to build from source (but built successfully in the past) python-cassandra-driver FTBFS on 32 bit arches with | == | ERROR: test_datetype (tests.unit.cython.test_types.TypesTest) | -- | Traceback (most recent call last): | File "/<>/.pybuild/cpython3_3.8_cassandra/build/tests/unit/cython/test_types.py", line 28, in test_datetype | types_testhelper.test_datetype(self.assertEqual) | File "tests/unit/cython/types_testhelper.pyx", line 59, in tests.unit.cython.types_testhelper.test_datetype | assert_equal(deserialize(expected), datetime.datetime(2242, 3, 16, 12, 56, 32)) | File "tests/unit/cython/types_testhelper.pyx", line 41, in tests.unit.cython.types_testhelper.test_datetype.deserialize | dt = datetime.datetime.utcfromtimestamp(timestamp) | OverflowError: timestamp out of range for platform time_t See https://buildd.debian.org/status/fetch.php?pkg=python-cassandra-driver&arch=i386&ver=3.20.2-2&stamp=1581670586&raw=0 for an example. Cheers -- Sebastian Ramacher signature.asc Description: PGP signature --- End Message --- --- Begin Message --- Version: 3.24.0-1 https://buildd.debian.org/status/logs.php?pkg=python-cassandra-driver&ver=3.24.0-1 cu Adrian--- End Message ---
Bug#982059: psmisc: isn't insallable
Package: psmisc Version: 23.3-1 Followup-For: Bug #982059 Dear Maintainer, I can confirm this! Preparing to unpack .../psmisc_23.4-1_amd64.deb ... Unpacking psmisc (23.4-1) over (23.3-1) ... dpkg: error processing archive /var/cache/apt/archives/psmisc_23.4-1_amd64.deb (--unpack): trying to overwrite '/usr/share/man/de/man1/fuser.1.gz', which is also in package manpages-de 4.2.0-1 Errors were encountered while processing: /var/cache/apt/archives/psmisc_23.4-1_amd64.deb E: Sub-process /usr/bin/dpkg returned an error code (1) -- System Information: Debian Release: bullseye/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'buildd-unstable'), (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 5.10.13-towo.1-siduction-amd64 (SMP w/4 CPU threads; PREEMPT) Kernel taint flags: TAINT_WARN, TAINT_CRAP, TAINT_OOT_MODULE Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE=de Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages psmisc depends on: ii libc62.31-9 ii libselinux1 3.1-2+b2 ii libtinfo66.2+20201114-2 psmisc recommends no packages. psmisc suggests no packages. -- no debconf information
