Processed: Patch prepared
Processing control commands: > tags -1 patch Bug #936880 [src:libiptcdata] libiptcdata: Python2 removal in sid/bullseye Added tag(s) patch. -- 936880: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=936880 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#936880: Patch prepared
control: tags -1 patch
I prepared an NMU which drops the python-iptcdata binary package. Then,
libiptcdata does not require python2 anymore. Debdiff is attached.
diff -Nru libiptcdata-1.0.5/debian/changelog libiptcdata-1.0.5/debian/changelog
--- libiptcdata-1.0.5/debian/changelog 2020-08-08 22:18:23.0 +0200
+++ libiptcdata-1.0.5/debian/changelog 2020-08-20 16:36:58.0 +0200
@@ -1,3 +1,10 @@
+libiptcdata (1.0.5-2.3) unstable; urgency=medium
+
+ * Non-maintainer upload.
+ * Drop binary package python-iptcdata. Closes: #936880.
+
+ -- Jann Haber Thu, 20 Aug 2020 16:36:58 +0200
+
libiptcdata (1.0.5-2.2) unstable; urgency=medium
* Non-maintainer upload.
diff -Nru libiptcdata-1.0.5/debian/control libiptcdata-1.0.5/debian/control
--- libiptcdata-1.0.5/debian/control2019-02-24 17:12:43.0 +0100
+++ libiptcdata-1.0.5/debian/control2020-08-20 16:30:26.0 +0200
@@ -8,7 +8,7 @@
debhelper (>= 10~),
dh-buildinfo,
dh-autoreconf,
- licensecheck, dpkg-dev (>= 1.13.19), gtk-doc-tools, pkg-config,
python-all-dev (>= 2.6.6-3~), dh-python
+ licensecheck, dpkg-dev (>= 1.13.19), gtk-doc-tools, pkg-config
Standards-Version: 4.2.1.1
Vcs-Browser: https://salsa.debian.org/debian/libiptcdata
Vcs-Git: https://salsa.debian.org/debian/libiptcdata.git
@@ -66,16 +66,3 @@
Telecommunications Council (IPTC) metadata stored within multimedia
files such as images. The library provides routines for parsing,
viewing, modifying, and saving this metadata.
-
-Package: python-iptcdata
-Architecture: any
-Section: python
-Depends: ${shlibs:Depends}, ${misc:Depends}, ${python:Depends}
-Provides: ${python:Provides}
-Description: Python bindings for the iptcdata library
- libiptcdata is a library, for manipulating the International Press
- Telecommunications Council (IPTC) metadata stored within multimedia
- files such as images. The library provides routines for parsing,
- viewing, modifying, and saving this metadata.
- .
- This package contains the python bindings for libiptcdata.
diff -Nru libiptcdata-1.0.5/debian/control.in
libiptcdata-1.0.5/debian/control.in
--- libiptcdata-1.0.5/debian/control.in 2019-02-24 17:12:43.0 +0100
+++ libiptcdata-1.0.5/debian/control.in 2020-08-20 16:30:45.0 +0200
@@ -2,7 +2,7 @@
Section: libs
Priority: optional
Maintainer: Ian Wienand
-Build-Depends: @cdbs@, dpkg-dev (>= 1.13.19), gtk-doc-tools, pkg-config,
python-all-dev (>= 2.6.6-3~), dh-python
+Build-Depends: @cdbs@, dpkg-dev (>= 1.13.19), gtk-doc-tools, pkg-config
Standards-Version: 4.2.1.1
Vcs-Browser: https://salsa.debian.org/debian/libiptcdata
Vcs-Git: https://salsa.debian.org/debian/libiptcdata.git
@@ -61,16 +61,3 @@
Telecommunications Council (IPTC) metadata stored within multimedia
files such as images. The library provides routines for parsing,
viewing, modifying, and saving this metadata.
-
-Package: python-iptcdata
-Architecture: any
-Section: python
-Depends: ${shlibs:Depends}, ${misc:Depends}, ${python:Depends}
-Provides: ${python:Provides}
-Description: Python bindings for the iptcdata library
- libiptcdata is a library, for manipulating the International Press
- Telecommunications Council (IPTC) metadata stored within multimedia
- files such as images. The library provides routines for parsing,
- viewing, modifying, and saving this metadata.
- .
- This package contains the python bindings for libiptcdata.
diff -Nru libiptcdata-1.0.5/debian/rules libiptcdata-1.0.5/debian/rules
--- libiptcdata-1.0.5/debian/rules 2020-08-08 22:18:23.0 +0200
+++ libiptcdata-1.0.5/debian/rules 2020-08-20 16:36:58.0 +0200
@@ -32,15 +32,13 @@
include /usr/share/cdbs/1/rules/autoreconf.mk
include /usr/share/cdbs/1/rules/utils.mk
-PY_VERSIONS = $(shell pyversions --requested debian/control)
-
DEB_BUILDDIR := build
-DEB_CONFIGURE_EXTRA_FLAGS := --enable-python --enable-gtk-doc
--libdir=\$${prefix}/lib/$(DEB_HOST_MULTIARCH)
+DEB_CONFIGURE_EXTRA_FLAGS := --enable-gtk-doc
--libdir=\$${prefix}/lib/$(DEB_HOST_MULTIARCH)
configure-stamp-%:
mkdir build-$*
- cd build-$* && PYTHON=`which $*` $(DEB_CONFIGURE_SCRIPT_ENV) \
+ cd build-$* && $(DEB_CONFIGURE_SCRIPT_ENV) \
$(DEB_CONFIGURE_SCRIPT) \
$(DEB_CONFIGURE_NORMAL_ARGS) \
--disable-maintainer-mode \
@@ -50,31 +48,18 @@
touch $@
-configure/python-iptcdata:: $(addprefix configure-stamp-, $(PY_VERSIONS))
-
build-stamp-%:
make -C build-$*
touch $@
-build/python-iptcdata:: $(addprefix build-stamp-, $(PY_VERSIONS))
-
build/libiptcdata-bin::
install-stamp-%:
make -C build-$* install DESTDIR=$(CURDIR)/debian/tmp
touch $@
-install/python-iptcdata:: $(addprefix install-stamp-, $(PY_VERSIONS))
-
-binary-install/python-iptcdata::
- dh_python2
-
DEB_INSTALL_MANPAGES_libiptcdata-bin := debian/iptc.1
clean::
-$(RM) -r $(DEB_BUILDDIR)
- -$(RM) -r $(addprefix $(CURDIR)/build-, $(PY
Bug#968739: [benjamin.redeli...@gmail.com: Bug#968739: igv will not run]
Hi Andreas,
Le 21/08/2020 à 07:38, Andreas Tille a écrit :
> Hi Pierre,
>
> do you have some spare cycles for this issue?
>
> BTW, I do not think that we should stick to that now outdated
> version but while fixing the issue package latest upstream.
>
> On a more general note: Igv is another Java package that is in
> non-free only due to the included binary JARs. If we could that
> sorted out it probably could go into main which would be a real
> advantage.
>
> Kind regards
>
> Andreas.
I will have a look at it!
Having this package leave non-free would indeed be great.
Best,
Pierre
>
>
> - Forwarded message from Benjamin Redelings
> -
>
> Date: Thu, 20 Aug 2020 14:01:13 -0400
> From: Benjamin Redelings
> To: Debian Bug Tracking System
> Subject: Bug#968739: igv will not run
> X-Debian-PR-Message: report 968739
> X-Debian-PR-Package: igv
> X-Debian-PR-Keywords:
> X-Debian-PR-Source: igv
>
> Package: igv
> Version: 2.4.17+dfsg-1
> Severity: grave
> Justification: renders package unusable
>
> Dear Maintainer,
>
> The IGV package seems not to work. It throws a NoSuchMethodError exception
> on startup with the following trace:
>
> $ igv
> log4j: reset attribute= "false".
> log4j: Threshold ="null".
> log4j: Retreiving an instance of org.apache.log4j.Logger.
> log4j: Setting [org.broad.igv] additivity to [true].
> log4j: Level value for org.broad.igv is [INFO].
> log4j: org.broad.igv level set to INFO
> log4j: Class name: [org.apache.log4j.ConsoleAppender]
> log4j: Parsing layout of class: "org.apache.log4j.PatternLayout"
> log4j: Setting property [conversionPattern] to [%d{-MM-dd HH:mm:ss} %-5p
> %c{1}:%L - %m%n].
> log4j: Adding appender named [console] to category [org.broad.igv].
> 2020-08-20 13:59:59 INFO DirectoryManager:179 - IGV Directory:
> /home/bredelings/igv
> 2020-08-20 13:59:59 INFO Main:155 - Startup IGV Version user not_set
> 2020-08-20 13:59:59 INFO Main:156 - Java 11.0.8
> 2020-08-20 13:59:59 INFO DirectoryManager:84 - Fetching user directory...
> 2020-08-20 13:59:59 INFO Main:157 - Default User Directory: /home/bredelings
> 2020-08-20 13:59:59 INFO Main:158 - OS: Linux
> 2020-08-20 13:59:59 INFO Main:208 - Unknown version: user
> 2020-08-20 14:00:00 ERROR DefaultExceptionHandler:49 - Unhandled exception
> java.lang.NoSuchMethodError: 'void
> htsjdk.tribble.util.ParsingUtils.registerHelperClass(java.lang.Class)'
> at org.broad.igv.util.HttpUtils.(HttpUtils.java:104)
> at org.broad.igv.util.HttpUtils.getInstance(HttpUtils.java:97)
> at org.broad.igv.ui.Main.open(Main.java:279)
> at org.broad.igv.ui.Main$1.run(Main.java:110)
> at
> java.desktop/java.awt.event.InvocationEvent.dispatch(InvocationEvent.java:313)
> at
> java.desktop/java.awt.EventQueue.dispatchEventImpl(EventQueue.java:770)
> at java.desktop/java.awt.EventQueue$4.run(EventQueue.java:721)
> at java.desktop/java.awt.EventQueue$4.run(EventQueue.java:715)
> at java.base/java.security.AccessController.doPrivileged(Native Method)
> at
> java.base/java.security.ProtectionDomain$JavaSecurityAccessImpl.doIntersectionPrivilege(ProtectionDomain.java:85)
> at java.desktop/java.awt.EventQueue.dispatchEvent(EventQueue.java:740)
> at
> java.desktop/java.awt.EventDispatchThread.pumpOneEventForFilters(EventDispatchThread.java:203)
> at
> java.desktop/java.awt.EventDispatchThread.pumpEventsForFilter(EventDispatchThread.java:124)
> at
> java.desktop/java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:113)
> at
> java.desktop/java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:109)
> at
> java.desktop/java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:101)
> at
> java.desktop/java.awt.EventDispatchThread.run(EventDispatchThread.java:90)
> 2020-08-20 14:00:01 INFO ShutdownThread:46 - Shutting down
>
> -- System Information:
> Debian Release: bullseye/sid
> APT prefers unstable
> APT policy: (2000, 'unstable'), (1999, 'experimental')
> Architecture: amd64 (x86_64)
> Foreign Architectures: i386
>
> Kernel: Linux 5.7.0-2-amd64 (SMP w/12 CPU threads)
> Kernel taint flags: TAINT_PROPRIETARY_MODULE, 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 igv depends on:
> ii default-jre 2:1.11-72
> ii junit44.12-8
> ii libbatik-java 1.12-1.1
> ii libbcprov-java1.65-1
> ii libcofoja-java1.3-4
> ii libcommons-io-java2.6-2
> ii libcommons-logging-java 1.2-2
> ii libcommons-math-java 2.2-7
> ii libcommons-net-java 3.6-1
> ii libgoogle-gson-java 2.8.6-1
> ii libguava-java 29.0-5
> ii
Processed: bug 912880 is forwarded to https://sourceforge.net/p/gprename/bugs/18/
Processing commands for cont...@bugs.debian.org: > forwarded 912880 https://sourceforge.net/p/gprename/bugs/18/ Bug #912880 [src:gprename] gprename: Depends on libgtk2-perl, that won't be part of Bullseye Set Bug forwarded-to-address to 'https://sourceforge.net/p/gprename/bugs/18/'. > thanks Stopping processing here. Please contact me if you need assistance. -- 912880: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=912880 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#912880: gprename: Depends on libgtk2-perl, that won't be part of Bullseye
Hi Marvin, intrigeri (2019-07-16): > as announced on this bug report and on debian-devel@ in November 2018, > GTK 2 is going away in Bullseye, so I'm hereby bumping severity of > these bugs, on every reverse-dependency of libgtk2-perl, to RC. > > I hope that upstream will port the code to GTK 3 in time for the > Bullseye freeze :) A year later, it's now clear this is not going to happen: https://sourceforge.net/p/gprename/bugs/18/ … where upstream says they've given up and would rather port the code to Tk Python. I also notice that: - We're shipping a version from 2014. There's been several new upstream releases since. - 2 open bug reports filed 3 years ago in the Debian BTS have not been answered. This suggests to me that you lack interest and/or capacity to actively maintain this package. It's OK: there are several other batch renaming GUIs in the archive :) Would you mind if we remove gprename from the archive? Of course, it'll be possible to reintroduce it in Debian once the program is ported to a non-deprecated GUI toolkit. Cheers!
Bug#957921: marked as done (w1retap: ftbfs with GCC-10)
Your message dated Fri, 21 Aug 2020 09:06:34 + with message-id and subject line Bug#957921: fixed in w1retap 1.4.4-4 has caused the Debian Bug report #957921, regarding w1retap: 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.) -- 957921: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=957921 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:w1retap Version: 1.4.4-3 Severity: normal Tags: sid bullseye User: debian-...@lists.debian.org Usertags: ftbfs-gcc-10 Please keep this issue open in the bug tracker for the package it was filed for. If a fix in another package is required, please file a bug for the other package (or clone), and add a block in this package. Please keep the issue open until the package can be built in a follow-up test rebuild. The package fails to build in a test rebuild on at least amd64 with gcc-10/g++-10, but succeeds to build with gcc-9/g++-9. The severity of this report will be raised before the bullseye release, so nothing has to be done for the buster release. The full build log can be found at: http://people.debian.org/~doko/logs/gcc10-20200225/w1retap_1.4.4-3_unstable_gcc10.log The last lines of the build log are at the end of this report. To build with GCC 10, either set CC=gcc-10 CXX=g++-10 explicitly, or install the gcc, g++, gfortran, ... packages from experimental. apt-get -t=experimental install g++ Common build failures are new warnings resulting in build failures with -Werror turned on, or new/dropped symbols in Debian symbols files. For other C/C++ related build failures see the porting guide at http://gcc.gnu.org/gcc-10/porting_to.html [...] libtool: compile: gcc -DHAVE_CONFIG_H -I. -I../.. -Wall -D_GNU_SOURCE=1 -I . -pthread -I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -Wdate-time -D_FORTIFY_SOURCE=2 -Werror -Wno-unused-result -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -Wall -c ioutil.c -fPIC -DPIC -o .libs/ioutil.o libtool: compile: gcc -DHAVE_CONFIG_H -I. -I../.. -Wall -D_GNU_SOURCE=1 -I . -pthread -I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -Wdate-time -D_FORTIFY_SOURCE=2 -Werror -Wno-unused-result -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -Wall -c crcutil.c -fPIC -DPIC -o .libs/crcutil.o /bin/bash ../../libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I. -I../.. -Wall -D_GNU_SOURCE=1 -I . -pthread -I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -Wdate-time -D_FORTIFY_SOURCE=2 -Werror -Wno-unused-result -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -Wall -c -o acquire.lo acquire.c libtool: compile: gcc -DHAVE_CONFIG_H -I. -I../.. -Wall -D_GNU_SOURCE=1 -I . -pthread -I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -Wdate-time -D_FORTIFY_SOURCE=2 -Werror -Wno-unused-result -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -Wall -c owerr.c -o owerr.o >/dev/null 2>&1 libtool: compile: gcc -DHAVE_CONFIG_H -I. -I../.. -Wall -D_GNU_SOURCE=1 -I . -pthread -I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -Wdate-time -D_FORTIFY_SOURCE=2 -Werror -Wno-unused-result -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -Wall -c crcutil.c -o crcutil.o >/dev/null 2>&1 libtool: compile: gcc -DHAVE_CONFIG_H -I. -I../.. -Wall -D_GNU_SOURCE=1 -I . -pthread -I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -Wdate-time -D_FORTIFY_SOURCE=2 -Werror -Wno-unused-result -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -Wall -c acquire.c -fPIC -DPIC -o .libs/acquire.o gcc -DHAVE_CONFIG_H -I. -I../.. -Wall -D_GNU_SOURCE=1 -I . -pthread -I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -Wdate-time -D_FORTIFY_SOURCE=2 -Werror -Wno-unused-result -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -Wall -c -o mbappreg.o mbappreg.c gcc -DHAVE_CONFIG_H -I. -I../.. -Wall -D_GNU_SOURCE=1 -I . -pthread -I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -Wdate-time -D_FORTIFY_SOURCE=2 -Werror -Wno-unused-result -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -Wall -c -o mbeprom.o mbeprom.c libtool: compile: gcc -DHAVE_CONFIG_H -I. -I../.. -Wall -D_GNU_SOURCE=1 -I . -pthread -I/usr/include/g
Bug#968739: [benjamin.redeli...@gmail.com: Bug#968739: igv will not run]
Hi again,
I injected the latest upstream version into Git. It does not include so
many binary jar's any more but I think its trying to download these
instead. I gave up for the moment since I have no idea about gradle.
Kind regards
Andreas.
On Fri, Aug 21, 2020 at 07:38:21AM +0200, Andreas Tille wrote:
> Hi Pierre,
>
> do you have some spare cycles for this issue?
>
> BTW, I do not think that we should stick to that now outdated
> version but while fixing the issue package latest upstream.
>
> On a more general note: Igv is another Java package that is in
> non-free only due to the included binary JARs. If we could that
> sorted out it probably could go into main which would be a real
> advantage.
>
> Kind regards
>
> Andreas.
>
>
> - Forwarded message from Benjamin Redelings
> -
>
> Date: Thu, 20 Aug 2020 14:01:13 -0400
> From: Benjamin Redelings
> To: Debian Bug Tracking System
> Subject: Bug#968739: igv will not run
> X-Debian-PR-Message: report 968739
> X-Debian-PR-Package: igv
> X-Debian-PR-Keywords:
> X-Debian-PR-Source: igv
>
> Package: igv
> Version: 2.4.17+dfsg-1
> Severity: grave
> Justification: renders package unusable
>
> Dear Maintainer,
>
> The IGV package seems not to work. It throws a NoSuchMethodError exception
> on startup with the following trace:
>
> $ igv
> log4j: reset attribute= "false".
> log4j: Threshold ="null".
> log4j: Retreiving an instance of org.apache.log4j.Logger.
> log4j: Setting [org.broad.igv] additivity to [true].
> log4j: Level value for org.broad.igv is [INFO].
> log4j: org.broad.igv level set to INFO
> log4j: Class name: [org.apache.log4j.ConsoleAppender]
> log4j: Parsing layout of class: "org.apache.log4j.PatternLayout"
> log4j: Setting property [conversionPattern] to [%d{-MM-dd HH:mm:ss} %-5p
> %c{1}:%L - %m%n].
> log4j: Adding appender named [console] to category [org.broad.igv].
> 2020-08-20 13:59:59 INFO DirectoryManager:179 - IGV Directory:
> /home/bredelings/igv
> 2020-08-20 13:59:59 INFO Main:155 - Startup IGV Version user not_set
> 2020-08-20 13:59:59 INFO Main:156 - Java 11.0.8
> 2020-08-20 13:59:59 INFO DirectoryManager:84 - Fetching user directory...
> 2020-08-20 13:59:59 INFO Main:157 - Default User Directory: /home/bredelings
> 2020-08-20 13:59:59 INFO Main:158 - OS: Linux
> 2020-08-20 13:59:59 INFO Main:208 - Unknown version: user
> 2020-08-20 14:00:00 ERROR DefaultExceptionHandler:49 - Unhandled exception
> java.lang.NoSuchMethodError: 'void
> htsjdk.tribble.util.ParsingUtils.registerHelperClass(java.lang.Class)'
> at org.broad.igv.util.HttpUtils.(HttpUtils.java:104)
> at org.broad.igv.util.HttpUtils.getInstance(HttpUtils.java:97)
> at org.broad.igv.ui.Main.open(Main.java:279)
> at org.broad.igv.ui.Main$1.run(Main.java:110)
> at
> java.desktop/java.awt.event.InvocationEvent.dispatch(InvocationEvent.java:313)
> at
> java.desktop/java.awt.EventQueue.dispatchEventImpl(EventQueue.java:770)
> at java.desktop/java.awt.EventQueue$4.run(EventQueue.java:721)
> at java.desktop/java.awt.EventQueue$4.run(EventQueue.java:715)
> at java.base/java.security.AccessController.doPrivileged(Native Method)
> at
> java.base/java.security.ProtectionDomain$JavaSecurityAccessImpl.doIntersectionPrivilege(ProtectionDomain.java:85)
> at java.desktop/java.awt.EventQueue.dispatchEvent(EventQueue.java:740)
> at
> java.desktop/java.awt.EventDispatchThread.pumpOneEventForFilters(EventDispatchThread.java:203)
> at
> java.desktop/java.awt.EventDispatchThread.pumpEventsForFilter(EventDispatchThread.java:124)
> at
> java.desktop/java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:113)
> at
> java.desktop/java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:109)
> at
> java.desktop/java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:101)
> at
> java.desktop/java.awt.EventDispatchThread.run(EventDispatchThread.java:90)
> 2020-08-20 14:00:01 INFO ShutdownThread:46 - Shutting down
>
> -- System Information:
> Debian Release: bullseye/sid
> APT prefers unstable
> APT policy: (2000, 'unstable'), (1999, 'experimental')
> Architecture: amd64 (x86_64)
> Foreign Architectures: i386
>
> Kernel: Linux 5.7.0-2-amd64 (SMP w/12 CPU threads)
> Kernel taint flags: TAINT_PROPRIETARY_MODULE, 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 igv depends on:
> ii default-jre 2:1.11-72
> ii junit44.12-8
> ii libbatik-java 1.12-1.1
> ii libbcprov-java1.65-1
> ii libcofoja-java1.3-4
> ii libcommons-io-java2.6-2
> ii libcommons-logging-java 1.2-2
> ii libcommons-m
Bug#912889: tinyca: Depends on libgtk2-perl, that won't be part of Bullseye
Hi! intrigeri (2019-07-16): > as announced on this bug report and on debian-devel@ in November 2018, > GTK 2 is going away in Bullseye, so I'm hereby bumping severity of > these bugs, on every reverse-dependency of libgtk2-perl, to RC. > > I hope that upstream will port the code to GTK 3 in time for the > Bullseye freeze :) A year after this package was removed from testing, I'm wondering what's the best course of action for the next steps. I see that: - The last upstream release dates back to 2006, although Axel Beckert reported on #782341 that a newer version was floating around on the web, although it might be a third-party CVS snapshot not sanctioned by the upstream maintainer. - The last upload to Debian happened in 2015. - The Homepage control field points to Alioth, which was decommissioned a while ago. - In the BTS, there are a bunch of patches submitted years ago. All this suggests to me that you lack interest and/or capacity to maintain this package. That's perfectly OK: life and priorities shifts do happen :) What do you think we should do? I can think of several options, from the least drastic to the most: - File a Request For Help (RFH) bug against wnpp, in order to alert users and fellow Debian people about the current situation. popcon suggests this package is still quite popular, so I have some hope someone could volunteer :) - Orphan the package. - Remove the package from sid. What do you think? Cheers!
Bug#912870: asciio: GTK 2 Perl is going away
Hi David, intrigeri (2019-09-16): > In case you've missed it, here's my message from 2 months ago: > > intrigeri: >> as announced on this bug report and on debian-devel@ in November 2018, >> GTK 2 is going away in Bullseye, so I'm hereby bumping severity of >> these bugs, on every reverse-dependency of libgtk2-perl, to RC. > >> I hope that upstream will port the code to GTK 3 in time for the >> Bullseye freeze :) > [...] > I could not spot any upstream activity since 3+ years so I am not very > hopeful wrt. the chances they port the code to GTK 3 themselves :/ Almost a year later, it looks like the situation has not changed :( That's sad: I'm told asciio is the best tool available for the task at hand. Would you mind if I filed a Request For Help bug report against wnpp, in order to alert users and fellow Debian folks about the current situation? This might prompt someone to volunteer and port this program to a non-obsolete toolkit :) Cheers!
Bug#968739: [benjamin.redeli...@gmail.com: Bug#968739: igv will not run]
Hi Andreas, Le 21/08/2020 à 11:05, Andreas Tille a écrit : > Hi again, > > I injected the latest upstream version into Git. It does not include so > many binary jar's any more but I think its trying to download these > instead. I gave up for the moment since I have no idea about gradle. > Thanks! Many of those jars are in Debian packages, so there is hope to get rid of many, maybe all... I'm looking at it. > > Kind regards > > Andreas. > Best regards, Pierre
Bug#968245: [Pkg-pascal-devel] Bug#968245: Bug#968245: fpc: autopkgtest failure.
Hello, > Once fpc is otherwise in a good state i'll pop a mail > to Adam Conrad asking him to bootstrap it for ppc64el Ubuntu. I'll try to bootstrap it G.
Bug#968739: [benjamin.redeli...@gmail.com: Bug#968739: igv will not run]
Hi Pierre, On Fri, Aug 21, 2020 at 11:32:47AM +0200, Pierre Gruet wrote: > > I injected the latest upstream version into Git. It does not include so > > many binary jar's any more but I think its trying to download these > > instead. I gave up for the moment since I have no idea about gradle. > > > Thanks! Many of those jars are in Debian packages, so there is hope to > get rid of many, maybe all... I'm looking at it. Thanks a lot. That would be another mile stone! Kind regards Andreas. -- http://fam-tille.de
Bug#968742: marked as done (diffoscope build-depends on package that is not in testing.)
Your message dated Fri, 21 Aug 2020 11:48:25 + with message-id and subject line Bug#968742: fixed in diffoscope 157 has caused the Debian Bug report #968742, regarding diffoscope build-depends on package that is not in testing. 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.) -- 968742: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=968742 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: diffoscope Version: 156 Severity: serious Diffoscope has been removed from testing and cannot re-enter because it build-depends on gnumeric, which has been kicked out of testing due to a python2 dependency. Since this build-dependency only appears to be used for testing I would suggest dropping it until/unless gnumeric is fixed. --- End Message --- --- Begin Message --- Source: diffoscope Source-Version: 157 Done: Chris Lamb We believe that the bug you reported is fixed in the latest version of diffoscope, 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 968...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Chris Lamb (supplier of updated diffoscope 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: Fri, 21 Aug 2020 12:24:25 +0100 Source: diffoscope Architecture: source Version: 157 Distribution: unstable Urgency: medium Maintainer: Reproducible builds folks Changed-By: Chris Lamb Closes: 968742 Changes: diffoscope (157) unstable; urgency=medium . [ Chris Lamb ] . * Try obsensibly "data" files named .pgp against pgpdump to determine whether they are PGP files. (Closes: reproducible-builds/diffoscope#211) * Don't raise an exception when we encounter XML files with "" declarations inside the DTD, or when a DTD or entity references an external resource. (Closes: reproducible-builds/diffoscope#212) * Temporarily drop gnumeric from Build-Depends as it has been removed from testing due to Python 2.x deprecation. (Closes: #968742) * Codebase changes: - Add support for multiple file extension matching; we previously supported only a single extension to match. - Move generation of debian/tests/control.tmp to an external script. - Move to our assert_diff helper entirely in the PGP tests. - Drop some unnecessary control flow, unnecessary dictionary comprehensions and some unused imports found via pylint. * Include the filename in the "... not identified by any comparator" logging message. Checksums-Sha1: d039c7ad6b7c107399b8a99909d4ce6c311ca071 4807 diffoscope_157.dsc a55496e4d7c5fc37c2411640abc250383f4a9a4b 982348 diffoscope_157.tar.xz b5933f6107b7def66c81b2e85a47b0a5a75a990a 26873 diffoscope_157_amd64.buildinfo Checksums-Sha256: f54c3f68f2abad6322c747bda72ad0d7ec85ef5f1bd5d4b26dbc2b62bcc84829 4807 diffoscope_157.dsc cf5986e807ffe80d5f65d49180d26c6240e146978f0dc80862efeb8d99116e1e 982348 diffoscope_157.tar.xz 3aa9dfe65cdcdd784d3103beda5bd25f46b11b04accec83be8dff0c210c3cef5 26873 diffoscope_157_amd64.buildinfo Files: 4cbb7d60d47eec30aa6e485a997f1d92 4807 devel optional diffoscope_157.dsc bc663ee73bff81e37bd49b7d260af34b 982348 devel optional diffoscope_157.tar.xz 1d3affd23c9804fa9e8035bb38f49ce6 26873 devel optional diffoscope_157_amd64.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEEwv5L0nHBObhsUz5GHpU+J9QxHlgFAl8/sTQACgkQHpU+J9Qx HlgPPQ//fNq2ileXa/CaV/Jk/BHlvJ45CVF4i6p5O87rMn9TdkALNYj9fCB6lzdO HElkjgm2kJh7ZqouWwnd2KI5iUQg4oIpgUxhT2Xr5BhgI/pZ8rZYT0ja2qORq5AF 3aCt/LweeXpgbkl/nAvFHapCBWvdfkGnB9FN/uq9eqiI54n3u55g91jdOtsMg3nV tCrnYKmwCnD5W3PMpTqMDF2duDYYu9JY1uuYkf8pXU8dJwaEN2NdGscw3dc6y+7T G4Djwj2aBg/eQgrEYkLotALgdO0Qli1jrJA8SxpY7ZPaZTMbtVjkyxyk+Thrb+ph O4BHUg52wXve1CSr1xbE+Ba/HGNXxyoQNwkohKK2evzTdpYAPzlwpbbOCoOXwY8W u0WLnTAIgxASCVDb/K762bsdmZAXUqEdzsCxviK+b5gLcJboJ7x9sG74N8+8AmPT +dnsxh/ZjyzwIP/dA1zaVnLa1wXWLU+b4EdQF1QuxwCnhBXmV9N8YeSwXNa+CowY dgCImi/jwWOPTy3X1I+hkBHjVxqch59JdBduxcZzWowR1wrZ7g+M/G5PHtlIf4pm bh1CWwPb68+Saxq0t+bYx3oF5VbCZ2cn70YTCyrgj1jmdZt1L70aZyFZLc2dinVW hKHpURMliE9cMaoMk/9k5a1sT1e6miGLub/kt1DPWaz/uh9kd+g= =cbUL -END PGP SIGNATURE End Message ---
Bug#912870: asciio: GTK 2 Perl is going away
Hello, Sorry for top-quoting, but replying from a mobile phone. Yes, please go ahead, and sorry for not reacting before. Thank you for pinging me! David Il Ven 21 Ago 2020, 11:23 intrigeri ha scritto: > Hi David, > > intrigeri (2019-09-16): > > In case you've missed it, here's my message from 2 months ago: > > > > intrigeri: > >> as announced on this bug report and on debian-devel@ in November 2018, > >> GTK 2 is going away in Bullseye, so I'm hereby bumping severity of > >> these bugs, on every reverse-dependency of libgtk2-perl, to RC. > > > >> I hope that upstream will port the code to GTK 3 in time for the > >> Bullseye freeze :) > > > [...] > > > I could not spot any upstream activity since 3+ years so I am not very > > hopeful wrt. the chances they port the code to GTK 3 themselves :/ > > Almost a year later, it looks like the situation has not changed :( > That's sad: I'm told asciio is the best tool available for the > task at hand. > > Would you mind if I filed a Request For Help bug report against wnpp, > in order to alert users and fellow Debian folks about the > current situation? > > This might prompt someone to volunteer and port this program to > a non-obsolete toolkit :) > > Cheers! >
Bug#957398: marked as done (kbd: ftbfs with GCC-10)
Your message dated Fri, 21 Aug 2020 12:33:41 + with message-id and subject line Bug#957398: fixed in kbd 2.2.0-1 has caused the Debian Bug report #957398, regarding kbd: 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.) -- 957398: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=957398 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:kbd Version: 2.0.4-4 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/kbd_2.0.4-4_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 [...] /bin/bash ../../libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I. -I../.. -I. -I. -I./.. -I./.. -DDATADIR=\"/usr/share\" -DLOCALEDIR=\"/usr/share/locale\" -U_GNU_SOURCE -D_FORTIFY_SOURCE=2 -funit-at-a-time -Wdate-time -D_FORTIFY_SOURCE=2 -Os -g -c -o kmap.lo kmap.c libtool: compile: gcc -DHAVE_CONFIG_H -I. -I../.. -I. -I. -I./.. -I./.. -DDATADIR=\"/usr/share\" -DLOCALEDIR=\"/usr/share/locale\" -U_GNU_SOURCE -D_FORTIFY_SOURCE=2 -funit-at-a-time -Wdate-time -D_FORTIFY_SOURCE=2 -Os -g -c kmap.c -fPIC -DPIC -o .libs/kmap.o libtool: compile: gcc -DHAVE_CONFIG_H -I. -I../.. -I. -I. -I./.. -I./.. -DDATADIR=\"/usr/share\" -DLOCALEDIR=\"/usr/share/locale\" -U_GNU_SOURCE -D_FORTIFY_SOURCE=2 -funit-at-a-time -Wdate-time -D_FORTIFY_SOURCE=2 -Os -g -c kmap.c -o kmap.o >/dev/null 2>&1 /bin/bash ../../libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I. -I../.. -I. -I. -I./.. -I./.. -DDATADIR=\"/usr/share\" -DLOCALEDIR=\"/usr/share/locale\" -U_GNU_SOURCE -D_FORTIFY_SOURCE=2 -funit-at-a-time -Wdate-time -D_FORTIFY_SOURCE=2 -Os -g -c -o diacr.lo diacr.c libtool: compile: gcc -DHAVE_CONFIG_H -I. -I../.. -I. -I. -I./.. -I./.. -DDATADIR=\"/usr/share\" -DLOCALEDIR=\"/usr/share/locale\" -U_GNU_SOURCE -D_FORTIFY_SOURCE=2 -funit-at-a-time -Wdate-time -D_FORTIFY_SOURCE=2 -Os -g -c diacr.c -fPIC -DPIC -o .libs/diacr.o libtool: compile: gcc -DHAVE_CONFIG_H -I. -I../.. -I. -I. -I./.. -I./.. -DDATADIR=\"/usr/share\" -DLOCALEDIR=\"/usr/share/locale\" -U_GNU_SOURCE -D_FORTIFY_SOURCE=2 -funit-at-a-time -Wdate-time -D_FORTIFY_SOURCE=2 -Os -g -c diacr.c -o diacr.o >/dev/null 2>&1 /bin/bash ../../libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I. -I../.. -I. -I. -I./.. -I./.. -DDATADIR=\"/usr/share\" -DLOCALEDIR=\"/usr/share/locale\" -U_GNU_SOURCE -D_FORTIFY_SOURCE=2 -funit-at-a-time -Wdate-time -D_FORTIFY_SOURCE=2 -Os -g -c -o func.lo func.c libtool: compile: gcc -DHAVE_CONFIG_H -I. -I../.. -I. -I. -I./.. -I./.. -DDATADIR=\"/usr/share\" -DLOCALEDIR=\"/usr/share/locale\" -U_GNU_SOURCE -D_FORTIFY_SOURCE=2 -funit-at-a-time -Wdate-time -D_FORTIFY_SOURCE=2 -Os -g -c func.c -fPIC -DPIC -o .libs/func.o libtool: compile: gcc -DHAVE_CONFIG_H -I. -I../.. -I. -I. -I./.. -I./.. -DDATADIR=\"/usr/share\" -DLOCALEDIR=\"/usr/share/locale\" -U_GNU_SOURCE -D_FORTIFY_SOURCE=2 -funit-at-a-time -Wdate-time -D_FORTIFY_SOURCE=2 -Os -g -c func.c -o func.o >/dev/null 2>&1 /bin/bash ../../libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I. -I../.. -I. -I. -I./.. -I./.. -DDATADIR=\"/usr/share\" -DLOCALEDIR=\"/usr/share/locale\" -U_GNU_SOURCE -D_FORTIFY_SOURCE=2 -funit-at-a-time -Wdate-time -D_FORTIFY_SOURCE=2 -Os -g -c -o summary.lo summary.c libtool: compile: gcc -DHAVE_CONFIG_H -I. -I../.. -I. -I. -I./.. -I./.. -DDATADIR=\"/usr/share\" -DLOCALEDIR=\"/usr/share/locale\" -U_GNU_SOURCE -D_FORTIFY_SOURCE=2 -funit-at-a-time -Wdate-time -D_FORTIFY_SOURCE=2 -Os -g -c su
Bug#966066: marked as pending in opentyrian
Control: tag -1 pending Hello, Bug #966066 in opentyrian 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/games-team/opentyrian/-/commit/e655f30915125d91cdd38186937fa372b70a8d68 Add patch from upstream to fix FTBFS with -fno-common (gcc 10) Closes: #966066 (this message was generated automatically) -- Greetings https://bugs.debian.org/966066
Processed: Bug#966066 marked as pending in opentyrian
Processing control commands: > tag -1 pending Bug #966066 [src:opentyrian] opentyrian: FTBFS with GCC 10: multiple definition of ... due to -fno-common Added tag(s) pending. -- 966066: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=966066 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#966066: marked as done (opentyrian: FTBFS with GCC 10: multiple definition of ... due to -fno-common)
Your message dated Fri, 21 Aug 2020 13:04:34 + with message-id and subject line Bug#966066: fixed in opentyrian 2.1.20130907+dfsg-4 has caused the Debian Bug report #966066, regarding opentyrian: FTBFS with GCC 10: multiple definition of ... due to -fno-common 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.) -- 966066: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=966066 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: opentyrian Version: 2.1.20130907+dfsg-3 Severity: serious Tags: ftbfs sud bullseye Justification: fails to build from source (but built successfully in the past) User: debian-...@lists.debian.org Usertags: ftbfs-gcc-10 Hi, opentyrian started to FTBFS when GCC 10 was made the default compiler: cc -c -o obj/xmas.o -std=c99 -I./src -DTARGET_UNIX -g0 -O2 -DNDEBUG -MMD -pedantic -Wall -Wextra -Wno-missing-field-initializers -DWITH_NETWORK '-DHG_REV="2.1.20130907"' -I/usr/include/SDL -D_GNU_SOURCE=1 -D_REENTRANT -g -O2 -fdebug-prefix-map=/build/opentyri an-2.1.20130907+dfsg=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 src/xmas.c cc -o opentyrian -Wl,-z,relro -Wl,-z,now obj/animlib.o obj/arg_parse.o obj/backgrnd.o obj/cJSON.o obj/config.o obj/destruct.o obj/editship.o obj/episodes.o obj/file.o obj/font.o obj/fonthand.o obj/game_menu.o obj/helptext.o obj/joystick.o obj/jukebox.o obj/ke yboard.o obj/lds_play.o obj/loudness.o obj/lvllib.o obj/lvlmast.o obj/mainint.o obj/menus.o obj/mingw_fixes.o obj/mouse.o obj/mtrand.o obj/musmast.o obj/network.o obj/nortsong.o obj/nortvars.o obj/opentyr.o obj/opl.o obj/palette.o obj/params.o obj/pcxload.o o bj/pcxmast.o obj/picload.o obj/player.o obj/scroller.o obj/setup.o obj/shots.o obj/sizebuf.o obj/sndmast.o obj/sprite.o obj/starlib.o obj/tyrian2.o obj/varz.o obj/vga256d.o obj/vga_palette.o obj/video.o obj/video_scale.o obj/video_scale_hqNx.o obj/xmas.o -lm -L/usr/lib/x86_64-linux-gnu -lSDL -lSDL_net /usr/bin/ld: obj/destruct.o:./src/opl.h:172: multiple definition of `tremtab_add'; obj/config.o:./src/opl.h:172: first defined here /usr/bin/ld: obj/destruct.o:./src/opl.h:171: multiple definition of `tremtab_pos'; obj/config.o:./src/opl.h:171: first defined here /usr/bin/ld: obj/destruct.o:./src/opl.h:170: multiple definition of `vibtab_add'; obj/config.o:./src/opl.h:170: first defined here /usr/bin/ld: obj/destruct.o:./src/opl.h:169: multiple definition of `vibtab_pos'; obj/config.o:./src/opl.h:169: first defined here /usr/bin/ld: obj/destruct.o:./src/opl.h:164: multiple definition of `wave_sel'; obj/config.o:./src/opl.h:164: first defined here /usr/bin/ld: obj/destruct.o:./src/opl.h:163: multiple definition of `adlibreg'; obj/config.o:./src/opl.h:163: first defined here /usr/bin/ld: obj/destruct.o:./src/opl.h:158: multiple definition of `opl_index'; obj/config.o:./src/opl.h:158: first defined here /usr/bin/ld: obj/destruct.o:./src/opl.h:157: multiple definition of `status'; obj/config.o:./src/opl.h:157: first defined here /usr/bin/ld: obj/destruct.o:./src/opl.h:155: multiple definition of `int_samplerate'; obj/config.o:./src/opl.h:155: first defined here /usr/bin/ld: obj/destruct.o:./src/opl.h:153: multiple definition of `op'; obj/config.o:./src/opl.h:153: first defined here /usr/bin/ld: obj/destruct.o:./src/opl.h:152: multiple definition of `chip_num'; obj/config.o:./src/opl.h:152: first defined here /usr/bin/ld: obj/game_menu.o:./src/opl.h:172: multiple definition of `tremtab_add'; obj/config.o:./src/opl.h:172: first defined here /usr/bin/ld: obj/game_menu.o:./src/opl.h:171: multiple definition of `tremtab_pos'; obj/config.o:./src/opl.h:171: first defined here /usr/bin/ld: obj/game_menu.o:./src/opl.h:170: multiple definition of `vibtab_add'; obj/config.o:./src/opl.h:170: first defined here /usr/bin/ld: obj/game_menu.o:./src/opl.h:169: multiple definition of `vibtab_pos'; obj/config.o:./src/opl.h:169: first defined here /usr/bin/ld: obj/game_menu.o:./src/opl.h:164: multiple definition of `wave_sel'; obj/config.o:./src/opl.h:164: first defined here /usr/bin/ld: obj/game_menu.o:./src/opl.h:163: multiple definition of `adlibreg'; obj/config.o:./src/opl.h:163: first defined here /usr/bin/ld: obj/game_menu.o:./src/opl.h:158: multiple definition of `opl_index'; obj/config.o:./src/opl.h:158: first defined here /usr/bin/ld: obj/game_menu.o:./src/opl.h:157: multiple definition of `status'; obj/config.o:./src/opl.h:157: first defined here /usr/bin/ld: obj/game_menu.o:./src/opl.h:155: multiple definition of `int_samplerate'; obj/config.o:./src/opl.h:155: fi
Processed: Administrivia
Processing commands for cont...@bugs.debian.org: > tag 951973 + confirmed pending Bug #951973 [src:auctex] auctex: FTBFS: configure: error: Cannot find the texmf directory! Added tag(s) confirmed and pending. > tag 896844 + confirmed upstream pending Bug #896844 [auctex] auctex: Preview latex doesn't work - fixed upstream. Added tag(s) upstream, pending, and confirmed. > tag 769977 + confirmed pending Bug #769977 [auctex] auctex: Enabling bib-cite-minor-mode fails with (void-function make-local-hook) Added tag(s) pending and confirmed. > tag 912438 + upstream fixed-upstream pending Bug #912438 [auctex] auctex: ConTeXt source no longer recognized automatically Added tag(s) upstream, fixed-upstream, and pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 769977: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=769977 896844: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=896844 912438: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=912438 951973: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=951973 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Administrivia
Processing commands for cont...@bugs.debian.org: > tag 951973 + confirmed pending Bug #951973 [src:auctex] auctex: FTBFS: configure: error: Cannot find the texmf directory! Ignoring request to alter tags of bug #951973 to the same tags previously set > tag 896844 + confirmed upstream pending Bug #896844 [auctex] auctex: Preview latex doesn't work - fixed upstream. Ignoring request to alter tags of bug #896844 to the same tags previously set > tag 769977 + confirmed pending Bug #769977 [auctex] auctex: Enabling bib-cite-minor-mode fails with (void-function make-local-hook) Ignoring request to alter tags of bug #769977 to the same tags previously set > tag 912438 + upstream fixed-upstream pending Bug #912438 [auctex] auctex: ConTeXt source no longer recognized automatically Ignoring request to alter tags of bug #912438 to the same tags previously set > thanks Stopping processing here. Please contact me if you need assistance. -- 769977: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=769977 896844: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=896844 912438: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=912438 951973: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=951973 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#949913: marked as done (haskell-yesod-bin ftbfs in unstable (all archs))
Your message dated Fri, 21 Aug 2020 17:01:04 +0300 with message-id <20200821140104.ounuhdobzftvz...@iliastsi.net> and subject line Re: Bug#949913: haskell-yesod-bin ftbfs in unstable (all archs) has caused the Debian Bug report #949913, regarding haskell-yesod-bin ftbfs in unstable (all archs) 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.) -- 949913: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=949913 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:haskell-yesod-bin Version: 1.6.0.3-5 Severity: serious Tags: sid bullseye haskell-yesod-bin ftbfs in unstable (all archs), seen in a binNMU: [...] haskell-yesod-bin build-depends on: - libghc-fsnotify-dev:amd64 (< 0.4) libghc-fsnotify-dev depends on missing: - libghc-hinotify-dev-0.3.10-125c2:amd64 --- End Message --- --- Begin Message --- Version: 1.6.0.3-5+b1 This was fixed with a binNMU. -- Ilias--- End Message ---
Bug#957259: marked as done (gdbm: ftbfs with GCC-10)
Your message dated Fri, 21 Aug 2020 14:33:50 + with message-id and subject line Bug#957259: fixed in gdbm 1.18.1-5.1 has caused the Debian Bug report #957259, regarding gdbm: 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.) -- 957259: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=957259 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:gdbm Version: 1.18.1-5 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/gdbm_1.18.1-5_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 [...] /bin/bash ../libtool --tag=CC --mode=compile diet gcc -DHAVE_CONFIG_H -I. -I../../src -I.. -DIN_GDBM -DLOCALEDIR=\"/usr/share/locale\" -UHAVE_MMAP -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -U__DATE__ -U__TIME__ -c -o update.lo ../../src/update.c libtool: compile: diet gcc -DHAVE_CONFIG_H -I. -I../../src -I.. -DIN_GDBM -DLOCALEDIR=\"/usr/share/locale\" -UHAVE_MMAP -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -U__DATE__ -U__TIME__ -c ../../src/recover.c -o recover.o : warning: undefining "__DATE__" [-Wbuiltin-macro-redefined] : warning: undefining "__TIME__" [-Wbuiltin-macro-redefined] : warning: undefining "__DATE__" [-Wbuiltin-macro-redefined] : warning: undefining "__TIME__" [-Wbuiltin-macro-redefined] /bin/bash ../libtool --tag=CC --mode=compile diet gcc -DHAVE_CONFIG_H -I. -I../../src -I.. -DIN_GDBM -DLOCALEDIR=\"/usr/share/locale\" -UHAVE_MMAP -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -U__DATE__ -U__TIME__ -c -o version.lo ../../src/version.c diet gcc -DHAVE_CONFIG_H -I. -I../../src -I.. -DIN_GDBM -DLOCALEDIR=\"/usr/share/locale\" -UHAVE_MMAP -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -U__DATE__ -U__TIME__ -c -o gdbm_load.o ../../src/gdbm_load.c : warning: undefining "__DATE__" [-Wbuiltin-macro-redefined] : warning: undefining "__TIME__" [-Wbuiltin-macro-redefined] libtool: compile: diet gcc -DHAVE_CONFIG_H -I. -I../../src -I.. -DIN_GDBM -DLOCALEDIR=\"/usr/share/locale\" -UHAVE_MMAP -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -U__DATE__ -U__TIME__ -c ../../src/update.c -o update.o libtool: compile: diet gcc -DHAVE_CONFIG_H -I. -I../../src -I.. -DIN_GDBM -DLOCALEDIR=\"/usr/share/locale\" -UHAVE_MMAP -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -U__DATE__ -U__TIME__ -c ../../src/version.c -o version.o : warning: undefining "__DATE__" [-Wbuiltin-macro-redefined] : warning: undefining "__TIME__" [-Wbuiltin-macro-redefined] : warning: undefining "__DATE__" [-Wbuiltin-macro-redefined] : warning: undefining "__TIME__" [-Wbuiltin-macro-redefined] diet gcc -DHAVE_CONFIG_H -I. -I../../src -I.. -DIN_GDBM -DLOCALEDIR=\"/usr/share/locale\" -UHAVE_MMAP -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -U__DATE__ -U__TIME__ -c -o gdbm_dump.o ../../src/gdbm_dump.c : warning: undefining "__DATE__" [-Wbuiltin-macro-redefined] : warning: undefining "__TIME__" [-Wbuiltin-macro-redefined] rm -f libgdbmapp.a ar cru libgdb
Bug#967096: marked as done (haskell-stack: FTBFS: unsatisfiable build-dependency: libghc-hackage-security-dev (< 0.6) but 0.6.0.1-2 is to be installed)
Your message dated Fri, 21 Aug 2020 14:37:35 + with message-id and subject line Bug#967096: fixed in haskell-stack 2.3.3-1 has caused the Debian Bug report #967096, regarding haskell-stack: FTBFS: unsatisfiable build-dependency: libghc-hackage-security-dev (< 0.6) but 0.6.0.1-2 is to be installed 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.) -- 967096: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=967096 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: haskell-stack Version: 1.9.3.1-1 Severity: serious Justification: FTBFS on amd64 Tags: bullseye sid ftbfs Usertags: ftbfs-20200803 ftbfs-bullseye Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > +--+ > | Install package build dependencies > | > +--+ > > > Setup apt archive > - > > Merged Build-Depends: cdbs, debhelper (>= 10), haskell-devscripts (>= 0.13), > ghc (>= 8.4.3), libghc-aeson-dev, libghc-annotated-wl-pprint-dev (>= 0.7.0), > libghc-annotated-wl-pprint-dev (<< 0.8), libghc-ansi-terminal-dev, > libghc-async-dev, libghc-attoparsec-dev, libghc-base64-bytestring-dev, > libghc-bindings-uname-dev, libghc-conduit-dev, libghc-conduit-extra-dev, > libghc-cryptonite-dev, libghc-cryptonite-conduit-dev, libghc-echo-dev, > libghc-exceptions-dev, libghc-extra-dev, libghc-file-embed-dev, > libghc-filelock-dev, libghc-fsnotify-dev, libghc-generic-deriving-dev, > libghc-hackage-security-dev (>= 0.5.2.2), libghc-hackage-security-dev (<< > 0.6), libghc-hashable-dev, libghc-hpack-dev, libghc-http-client-dev, > libghc-http-client-tls-dev, libghc-http-conduit-dev, libghc-http-types-dev, > libghc-memory-dev, libghc-microlens-dev, libghc-monad-logger-dev, > libghc-mono-traversable-dev, libghc-mustache-dev, > libghc-neat-interpolation-dev, libghc-network-uri-dev, > libghc-open-browser-dev, libghc-optparse-applicative-dev, libghc-path-dev, > libghc-path-io-dev, libghc-persistent-dev, libghc-persistent-sqlite-dev, > libghc-persistent-template-dev, libghc-primitive-dev, > libghc-project-template-dev, libghc-regex-applicative-text-dev, > libghc-resourcet-dev, libghc-retry-dev, libghc-rio-dev, > libghc-semigroups-dev, libghc-split-dev, libghc-store-dev, > libghc-store-core-dev, libghc-streaming-commons-dev, libghc-tar-dev, > libghc-temporary-dev, libghc-text-metrics-dev, libghc-th-reify-many-dev, > libghc-tls-dev, libghc-typed-process-dev, libghc-unicode-transforms-dev, > libghc-unix-compat-dev, libghc-unliftio-dev, libghc-unordered-containers-dev, > libghc-vector-dev, libghc-yaml-dev, libghc-zip-archive-dev, libghc-zlib-dev, > libghc-quickcheck2-dev, libghc-hspec-dev, libghc-smallcheck-dev, > build-essential, fakeroot > Filtered Build-Depends: cdbs, debhelper (>= 10), haskell-devscripts (>= > 0.13), ghc (>= 8.4.3), libghc-aeson-dev, libghc-annotated-wl-pprint-dev (>= > 0.7.0), libghc-annotated-wl-pprint-dev (<< 0.8), libghc-ansi-terminal-dev, > libghc-async-dev, libghc-attoparsec-dev, libghc-base64-bytestring-dev, > libghc-bindings-uname-dev, libghc-conduit-dev, libghc-conduit-extra-dev, > libghc-cryptonite-dev, libghc-cryptonite-conduit-dev, libghc-echo-dev, > libghc-exceptions-dev, libghc-extra-dev, libghc-file-embed-dev, > libghc-filelock-dev, libghc-fsnotify-dev, libghc-generic-deriving-dev, > libghc-hackage-security-dev (>= 0.5.2.2), libghc-hackage-security-dev (<< > 0.6), libghc-hashable-dev, libghc-hpack-dev, libghc-http-client-dev, > libghc-http-client-tls-dev, libghc-http-conduit-dev, libghc-http-types-dev, > libghc-memory-dev, libghc-microlens-dev, libghc-monad-logger-dev, > libghc-mono-traversable-dev, libghc-mustache-dev, > libghc-neat-interpolation-dev, libghc-network-uri-dev, > libghc-open-browser-dev, libghc-optparse-applicative-dev, libghc-path-dev, > libghc-path-io-dev, libghc-persistent-dev, libghc-persistent-sqlite-dev, > libghc-persistent-template-dev, libghc-primitive-dev, > libghc-project-template-dev, libghc-regex-applicative-text-dev, > libghc-resourcet-dev, libghc-retry-dev, libghc-rio-dev, > libghc-semigroups-dev, libghc-split-dev, libghc-store-dev, > libghc-store-core-dev, libghc-streaming-commons-dev, libghc-tar-dev, > libghc-temporary-dev, libghc-text-metrics-dev, libghc-th-reify-many-dev, > libghc-tls-dev, libghc-typed-process-dev, libghc-unicode-transforms-dev, > libghc-unix-compat-dev,
Bug#964821: marked as done (haskell-github: BD-Uninstallable)
Your message dated Fri, 21 Aug 2020 14:35:37 + with message-id and subject line Bug#964821: fixed in haskell-github 0.23-1 has caused the Debian Bug report #964821, regarding haskell-github: BD-Uninstallable 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.) -- 964821: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=964821 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: haskell-github Version: 0.20-2 Severity: serious Tags: ftbfs Justification: fails to build from source (but built successfully in the past) haskell-github currently cannot be built since libghc-base-compat-dev has a higher version than 0.11: haskell-github build-depends on missing: - libghc-base-compat-dev:amd64 (< 0.11) Cheers -- Sebastian Ramacher signature.asc Description: PGP signature --- End Message --- --- Begin Message --- Source: haskell-github Source-Version: 0.23-1 Done: Ilias Tsitsimpis We believe that the bug you reported is fixed in the latest version of haskell-github, 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 964...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Ilias Tsitsimpis (supplier of updated haskell-github 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: Fri, 21 Aug 2020 08:12:01 +0300 Source: haskell-github Architecture: source Version: 0.23-1 Distribution: unstable Urgency: medium Maintainer: Debian Haskell Group Changed-By: Ilias Tsitsimpis Closes: 964821 964983 Changes: haskell-github (0.23-1) unstable; urgency=medium . * New upstream release (Closes: #964983, #964821) Checksums-Sha1: 180c40e6afff8c702393cbbf2b5f27f9e09ea93b 4786 haskell-github_0.23-1.dsc c54985996591dbdf52043ebcbadfc17f2972f479 71927 haskell-github_0.23.orig.tar.gz 40363eced766990f12ac9aad6dc33af31793f169 4244 haskell-github_0.23-1.debian.tar.xz acfd8ca92b49e551e2b2544587f2960ed2bf1b46 5522 haskell-github_0.23-1_source.buildinfo Checksums-Sha256: b44c4af6ac8b7a03951f7b4e7d5fb65fc9869c114cdf82c02338814be89189ae 4786 haskell-github_0.23-1.dsc aba66a0a2d21d97268f6522b5357fe45891d2ba92b874f5556df50a926a808b4 71927 haskell-github_0.23.orig.tar.gz 3f1f889ed6b56cb942a94bf8863ea0a9d7d91c7bbd537894c45e817e7a774a8e 4244 haskell-github_0.23-1.debian.tar.xz b44ce5609e9dc6c43d08509efb133582f9a1d45cd0d04cd256d0af8e65e72174 5522 haskell-github_0.23-1_source.buildinfo Files: 47060ba1299646622a4af17e14eb185f 4786 haskell optional haskell-github_0.23-1.dsc 045e2e5f7093ea30075d5ecd2ebf8adc 71927 haskell optional haskell-github_0.23.orig.tar.gz 54ecd4a4a61afc3e4db94becc5805dcd 4244 haskell optional haskell-github_0.23-1.debian.tar.xz 5bad42be8f7e9959237186b4600bdda0 5522 haskell optional haskell-github_0.23-1_source.buildinfo -BEGIN PGP SIGNATURE- iQJIBAEBCgAyFiEEJ9c8pfW11+AaUTb116hngMxkQDwFAl8/0mMUHGlsaWFzdHNp QGRlYmlhbi5vcmcACgkQ16hngMxkQDyNFhAAt3R2guYRKgbf89LDjwZeXXh5lmTz s0P4JFiThYtZSmYzW9YCfRzKvZphRDb1Ahb6IwKxfZRdhnKvkxs+caEroyb/KGJm y3cs0qDOmJZ94l+dToRDClGoDybuUH9eZGGzn+LvmMOC+Lqw7UXSVuzS7/os3oet /wfh9Vdi7wr7h2wBB27QczJdghJRCf/0/S/wWlGWcNEyQm901E/qNtkVj/j17RMQ QgY+iKZQ8UsPJxc+WU4lyRtZGLuGj95Kg8dVYsPq1O2nP5JgLz/iF/Ci/ZHfK6AE S3cGKoKHOaNN2LgmwPS5EG+vOVOCqtUgitQj7YC47yTFq1JX+kVbk+cqD9njvv46 NF4LvpDbzdgDzM/pLMOkCqi7oMiB35eZCGjfe3h0bVjJQXXqGqVh28o7aCZU+Oj8 0uSDF16qpv8ddrQ8cAm7OTcSz+SCFX5tS+/aiqQzcO+HLrSgjQaRC6khF36MLyjA zafLXtEZRHybiP7FEaUBU3vorRkC9yQoYHp9RP5+N2W2yfjSt8NPMz6Dbs9alVwX WU6pH0Sc8ufTyYnWW+UxLRI9+ndoAKrTZfWBm67nA/ZENfoTE4S7oz5FlUsh/CyF sjV7mljd2KdVQwUDPbT7t2YspVzinlOwh++b0NXqP0ujFIMFnaF03RyME/tZfnK+ gSWGQ2j7xd7ZmBA= =7Bi5 -END PGP SIGNATURE End Message ---
Bug#951973: marked as done (auctex: FTBFS: configure: error: Cannot find the texmf directory!)
Your message dated Fri, 21 Aug 2020 15:03:37 + with message-id and subject line Bug#951973: fixed in auctex 12.2-1 has caused the Debian Bug report #951973, regarding auctex: FTBFS: configure: error: Cannot find the texmf 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.) -- 951973: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=951973 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: auctex Version: 11.91-2 Severity: serious Justification: FTBFS on amd64 Tags: buster sid Usertags: ftbfs-20200222 ftbfs-buster Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > "" > checking for TDS-compliant directory... ./configure: line 3413: kpsepath: > command not found > no > checking for TeX directory hierarchy... no > checking for TeX input directory... no > configure: error: Cannot find the texmf directory! > Please use --with-texmf-dir=dir to specify where the preview tex files go > tail -v -n \+0 config.log The full build log is available from: http://qa-logs.debian.net/2020/02/22/auctex_11.91-2_unstable.log A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! 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: auctex Source-Version: 12.2-1 Done: sa...@debian.org (Davide G. M. Salvetti) We believe that the bug you reported is fixed in the latest version of auctex, 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 951...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Davide G. M. Salvetti (supplier of updated auctex 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: Fri, 21 Aug 2020 16:05:59 +0200 Source: auctex Architecture: source Version: 12.2-1 Distribution: unstable Urgency: medium Maintainer: Davide G. M. Salvetti Changed-By: Davide G. M. Salvetti Closes: 63513 702871 769977 884360 896844 912438 951973 Changes: auctex (12.2-1) unstable; urgency=medium . * [0c6b2de] New upstream release 12.2 Thanks to Benjamin Redelings, Itaï BEN YAACOV, Sanjoy Mahajan (Closes: #63513, #702871, #769977, #896844, #912438) * [79f0a28] Drop alternate recommends on dummy package evince-gtk. Thanks to Jeremy Bicha (Closes: #884360) * [7f3946b] Refresh upstream patches * [a25f788] debian/control (Build-Depends-Indep): Add texlive-extra-utils. Thanks to Lucas Nussbaum, Itaï BEN YAACOV (Closes: #951973) * [ebabf80] debian/auctex.lintian-ovverrides: Update according to 4.2.0 policy * [c5718d9] debian/po/de.po: Reencode in UTF-8 * [cc9cf07] debian/compat: Update dh compatibility level to 12 * [8541bc8] debian/control (Rules-Requires-Root): Declare no root need * [17f62ae] debian/control (Standards-Version): Upgrade to 4.5.0 Checksums-Sha1: 3ff3cc5ef8e8d205234d3a8c8e56fa79c1cb7493 2043 auctex_12.2-1.dsc f9a72b0005ea0a56731ea059c5b24d1c09c0b37c 1146225 auctex_12.2.orig.tar.gz ee59ecc4e97c1343bdd9cd07b921ebd4f96b4204 53260 auctex_12.2-1.debian.tar.xz 61f2a91a3aee515dfc3da26bbf83d23e1edadfb0 12025 auctex_12.2-1_amd64.buildinfo Checksums-Sha256: 39c835406ee69f87bec5b91e25824ed5cb30b23b87da8ec9f5819627869bc9a1 2043 auctex_12.2-1.dsc 4c0c4a3fb9b586d2310dccd3969c72310ac98575ffa6941faefb134650fab795 1146225 auctex_12.2.orig.tar.gz cc4631b65421fe97656dbabc98977c6b13afaad5fd6c897f4c5fd4885d475706 53260 auctex_12.2-1.debian.tar.xz 5eaeea0b95f9d5cf4112714cb6b18125462df0aaf58cb65650a921cd0041a65f 12025 auctex_12.2-1_amd64.buildinfo Files: 66caf76e1bba9af3f5175b0bb89dab51 2043 tex optional auctex_12.2-1.dsc e2976b29331812af638c895d8df5dc23 1146225 tex optional auctex_12.2.orig.tar.gz 9bf2f45bd7da55e1fa34e9524f5eab52 53260 tex optional auctex_12.2-1.debian.tar.xz 3567cb4ae4eab2186d90186f457a8129 12025 tex optional auctex_12.2-1_amd64.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCAAdF
Bug#958599: marked as done (yrmcds: Build-Depends on deprecated dh-systemd which is going away)
Your message dated Fri, 21 Aug 2020 15:23:16 + with message-id and subject line Bug#958599: fixed in yrmcds 1.1.8-2 has caused the Debian Bug report #958599, regarding yrmcds: 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.) -- 958599: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=958599 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: yrmcds Severity: normal User: pkg-systemd-maintain...@lists.alioth.debian.org Usertags: dh-systemd-removal Hi, your package yrmcds 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: yrmcds Source-Version: 1.1.8-2 Done: Kouhei Maeda We believe that the bug you reported is fixed in the latest version of yrmcds, 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. Kouhei Maeda (supplier of updated yrmcds 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: Fri, 21 Aug 2020 23:54:27 +0900 Source: yrmcds Binary: yrmcds yrmcds-dbgsym Architecture: source amd64 Version: 1.1.8-2 Distribution: unstable Urgency: medium Maintainer: Kouhei Maeda Changed-By: Kouhei Maeda Description: yrmcds - memcached compatible KVS with master/slave replication Closes: 958599 Changes: yrmcds (1.1.8-2) unstable; urgency=medium . * debian/yrmcds.postinst - Fix adduser-with-home-var-run postinst. * debian/control - Bump version Standards-Version to 4.5.0 - Build-Depends: * Bump version debhelper >= 9.20160709~. * Remove dh-systemd. (Closes: #958599) * Appends debhelper-compat (= 10). * debian/rules - Fixes debian-rules-uses-unnecessary-dh-argument dh ... --with=systemd. * Fixes spelling-error-in-patch-description. - debian/patches/Override-CC-CXX.patch - debian/patches/hange-dependency-of-libgoogle-perftools-dev.patch * Removes files. - debian/compat - debian/yrmcds.upstart - Fixes patch-file-present-but-not-mentioned-in-series * debian/patches/Drop-AI_ADDRCONFIG-to-support-IPv6-link-local-address-only.patch * debian/patches/Fixes-logrotate.patch * debian/patches/Make-tcp_connect-work-in-IPv6-only-env.patch * debian/patches/test-detect.patch * debian/patches/Change-to-append-CPPFLAGS.patch * debian/patches/Add-support-for-IPv6-link-local-address.patch Checksums-Sha1: 19c7f7e4880a0075dc9f8c49639c3c67bb5641e2 1869 yrmcds_1.1.8-2.dsc 2a24e6c4722d62f93a20efff7a2b476186d4b141 10240 yrmcds_1.1.8-2.debian.tar.xz 4e4593e6aa79105b230271af35dc93894afefccb 2711900 yrmcds-dbgsym_1.1.8-2_amd64.deb b41d466a19a82477585f5ba39224a8ebbc0563e4 6361 yrmcds_1.1.8-2_amd64.buildinfo 99909cf16d74e792c928f93b7139c78d4710ce36 138112 yrmcds_1.1.8-2_amd64.deb Checksums-Sha256: de5de105c8f0434aed8e27d2fa1f237733a7b9e5720b1406ed41920414c31664 1869 yrmcds_1.1.8-2.dsc 9356212a7e0f2322d0e06c392fdde68178ed681de33550eb1b47276a63e3ab6c 10240 yrmcds_1.1.8-2.debian.tar.xz ba061bf48cd424592ac2b4d776de9dc8df848a69472f383ae3e4fb1bddfb0ca0 2711900 yrmcds-dbgsym_1.1.8-2_amd64.deb ab75817366a6462a769e0e8f6792ebd098a5c44a77572d3afa8299bf600aa0da 6361 yrmcds_1.1.8-2_amd64.buildinfo 1d8a3ff21f3bc480be41b19ed46c43b97438e60f789cc2cf9e9aa8fdbb45ce6b 138112 yrmcds_1.1.8-2_amd64.deb Files: 663563b4cdac5a18a933c2673df651d0 1869 web optional yrmcds_1.1.8-2.dsc 36517839aa17d9491251f0d54e9c6ce2 10240 web optional yrmcds_1.1.8-2.debian.tar.xz 37a8e60a650912cafef22bfd9b243082 2711900 debug optional yrmcds-dbgsym_1.1.8-2_amd64.deb 12b648e9e39d
Bug#966895: marked as done (ms-gsl: FTBFS: multi_span:1467:96: error: array subscript 6 is outside array bounds of ‘int [5]’ [-Werror=array-bounds])
Your message dated Fri, 21 Aug 2020 15:37:00 +
with message-id
and subject line Bug#966895: fixed in ms-gsl 3.1.0-2
has caused the Debian Bug report #966895,
regarding ms-gsl: FTBFS: multi_span:1467:96: error: array subscript 6 is
outside array bounds of ‘int [5]’ [-Werror=array-bounds]
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.)
--
966895: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=966895
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ms-gsl
Version: 3.1.0-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):
> /usr/bin/c++ -g -O2 -fdebug-prefix-map=/<>=.
> -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time
> -D_FORTIFY_SOURCE=2 -Wl,-z,relro -rdynamic
> CMakeFiles/span_tests.dir/span_tests.cpp.o -o span_tests -lgtest_main
> -lpthread -lgtest -lpthread -lgtest
> In file included from /<>/tests/multi_span_tests.cpp:21:
> /<>/include/gsl/multi_span: In member function ‘virtual void
> multi_span_test_subspan_Test::TestBody()’:
> /<>/include/gsl/multi_span:1467:96: error: array subscript 6 is
> outside array bounds of ‘int [5]’ [-Werror=array-bounds]
> 1467 | return {this->data() + offset, count == dynamic_range ?
> this->length() - offset : count};
> |
> ^
> /<>/tests/multi_span_tests.cpp:986:9: note: while referencing
> ‘arr’
> 986 | int arr[5] = {1, 2, 3, 4, 5};
> | ^~~
> make[3]: Leaving directory '/<>/obj-x86_64-linux-gnu'
> [ 78%] Built target span_tests
> make -f tests/CMakeFiles/strided_span_tests.dir/build.make
> tests/CMakeFiles/strided_span_tests.dir/depend
> make[3]: Entering directory '/<>/obj-x86_64-linux-gnu'
> cd /<>/obj-x86_64-linux-gnu && /usr/bin/cmake -E cmake_depends
> "Unix Makefiles" /<> /<>/tests
> /<>/obj-x86_64-linux-gnu
> /<>/obj-x86_64-linux-gnu/tests
> /<>/obj-x86_64-linux-gnu/tests/CMakeFiles/strided_span_tests.dir/DependInfo.cmake
> --color=
> Scanning dependencies of target strided_span_tests
> make[3]: Leaving directory '/<>/obj-x86_64-linux-gnu'
> make -f tests/CMakeFiles/strided_span_tests.dir/build.make
> tests/CMakeFiles/strided_span_tests.dir/build
> make[3]: Entering directory '/<>/obj-x86_64-linux-gnu'
> [ 81%] Building CXX object
> tests/CMakeFiles/strided_span_tests.dir/strided_span_tests.cpp.o
> cd /<>/obj-x86_64-linux-gnu/tests && /usr/bin/c++
> -I/<>/include -isystem
> /<>/tests/googletest/googletest/include -g -O2
> -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat
> -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2
> -fno-strict-aliasing -Wall -Wcast-align -Wconversion -Wctor-dtor-privacy
> -Werror -Wextra -Wpedantic -Wshadow -Wsign-conversion
> -Wno-deprecated-declarations -Wdouble-promotion -Wlogical-op
> -Wduplicated-cond -Wmisleading-indentation -Wnull-dereference
> -Wno-unused-variable -Wduplicated-branches -o
> CMakeFiles/strided_span_tests.dir/strided_span_tests.cpp.o -c
> /<>/tests/strided_span_tests.cpp
> cc1plus: all warnings being treated as errors
> make[3]: *** [tests/CMakeFiles/multi_span_tests.dir/build.make:66:
> tests/CMakeFiles/multi_span_tests.dir/multi_span_tests.cpp.o] Error 1
The full build log is available from:
http://qa-logs.debian.net/2020/08/02/ms-gsl_3.1.0-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: ms-gsl
Source-Version: 3.1.0-2
Done: Nicholas Guriev
We believe that the bug you reported is fixed in the latest version of
ms-gsl, 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.
Nicholas Guriev (supplier of updated ms-gsl package)
(This message was generated automatically at their request; if you
believe that there is a
Processed: Missing TLS symlink
Processing commands for cont...@bugs.debian.org: > reassign 956499 libgl1-mesa-dr1 Bug #956499 [libdrm2] MESA-LOADER: failed to open i915 Bug reassigned from package 'libdrm2' to 'libgl1-mesa-dr1'. Warning: Unknown package 'libgl1-mesa-dr1' Warning: Unknown package 'libgl1-mesa-dr1' No longer marked as found in versions libdrm/2.4.102-1. Warning: Unknown package 'libgl1-mesa-dr1' Warning: Unknown package 'libgl1-mesa-dr1' Ignoring request to alter fixed versions of bug #956499 to the same values previously set Warning: Unknown package 'libgl1-mesa-dr1' > found 956499 20.1.5-1 Bug #956499 [libgl1-mesa-dr1] MESA-LOADER: failed to open i915 Warning: Unknown package 'libgl1-mesa-dr1' There is no source info for the package 'libgl1-mesa-dr1' at version '20.1.5-1' with architecture '' Unable to make a source version for version '20.1.5-1' Marked as found in versions 20.1.5-1. Warning: Unknown package 'libgl1-mesa-dr1' > retitle 956499 Missing TLS symlink Bug #956499 [libgl1-mesa-dr1] MESA-LOADER: failed to open i915 Warning: Unknown package 'libgl1-mesa-dr1' Changed Bug title to 'Missing TLS symlink' from 'MESA-LOADER: failed to open i915'. Warning: Unknown package 'libgl1-mesa-dr1' > severity 956499 critical Bug #956499 [libgl1-mesa-dr1] Missing TLS symlink Warning: Unknown package 'libgl1-mesa-dr1' Severity set to 'critical' from 'normal' Warning: Unknown package 'libgl1-mesa-dr1' > thanks Stopping processing here. Please contact me if you need assistance. -- 956499: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=956499 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#968816: tilix: Library load failed (librsvg-2.so.2): ... Illegal instruction
Package: tilix Version: 1.9.3-4+b2 Severity: serious When librsvg2-2 is not installed, tilix crashes with SIGILL: $ tilix object.Exception@generated/gtkd/gtkd/Loader.d(125): Library load failed (librsvg-2.so.2): librsvg-2.so.2: cannot open shared object file: No such file or directory Illegal instruction GDB says: (gdb) x/i $pc => 0xf6c61df1 <_D2rt8monitor_9lockMutexFNbNiPS4core3sys5posixQk5types15pthread_mutex_tZv+33>: ud2 (gdb) bt #0 0xf6c61df1 in _D2rt8monitor_9lockMutexFNbNiPS4core3sys5posixQk5types15pthread_mutex_tZv () from /usr/lib/i386-linux-gnu/libdruntime-ldc-shared.so.91 #1 0xf6c57641 in _d_criticalenter () from /usr/lib/i386-linux-gnu/libdruntime-ldc-shared.so.91 #2 0xf6c65ca6 in _staticDtor_L376_C1 () from /usr/lib/i386-linux-gnu/libdruntime-ldc-shared.so.91 #3 0xf6c61344 in rt.minfo.ModuleGroup.runTlsDtors() () from /usr/lib/i386-linux-gnu/libdruntime-ldc-shared.so.91 #4 0xf6c63a44 in _d_dso_registry () from /usr/lib/i386-linux-gnu/libdruntime-ldc-shared.so.91 #5 0xf6c176e2 in ldc.register_dso () from /usr/lib/i386-linux-gnu/libdruntime-ldc-shared.so.91 #6 0xf7f9626a in _dl_fini () at dl-fini.c:138 #7 0xf69d780e in __run_exit_handlers (status=1, listp=0xf6b853fc <__exit_funcs>, run_list_atexit=true, run_dtors=true) at exit.c:108 #8 0xf69d79e1 in __GI_exit (status=1) at exit.c:139 #9 0xf69bee02 in __libc_start_main (main=0x5665e230 , argc=1, argv=0xffb25e64, init=0x5675fc60 <__libc_csu_init>, fini=0x5675fcc0 <__libc_csu_fini>, rtld_fini=0xf7f96080 <_dl_fini>, stack_end=0xffb25e5c) at ../csu/libc-start.c:342 #10 0x56650061 in _start () -- System Information: Architecture: i386 Versions of packages tilix depends on: ii dconf-gsettings-backend [gsettings-backend] 0.36.0-1 ii libc62.31-3 ii libgtkd-3-0 3.9.0-3+b3 ii libphobos2-ldc-shared91 1:1.21.0-1+b1 ii libunwind8 1.3.2-2 ii libvted-3-0 3.9.0-3+b3 ii libx11-6 2:1.6.10-3 ii tilix-common 1.9.3-4 -- Jakub Wilk
Bug#964899: ruby-net-dns: not able to reproduce the ftbfs
Attaching the sbuild log. I wonder if this has something to do with ipv6 support. sbuild (Debian sbuild) 0.79.1 (22 April 2020) on ilvala2 +==+ | ruby-net-dns 0.9.1-2 (amd64) Fri, 21 Aug 2020 16:42:17 + | +==+ Package: ruby-net-dns Version: 0.9.1-2 Source Version: 0.9.1-2 Distribution: unstable Machine Architecture: amd64 Host Architecture: amd64 Build Architecture: amd64 Build Type: full I: NOTICE: Log filtering will replace 'var/run/schroot/mount/unstable-amd64-sbuild-c16cc795-b2a5-443c-8266-1e8cc8f9686e' with '<>' I: NOTICE: Log filtering will replace 'build/ruby-net-dns-JRLEUt/resolver-WePKxs' with '<>' +--+ | Update chroot| +--+ Get:1 http://deb.debian.org/debian unstable InRelease [146 kB] Get:2 http://deb.debian.org/debian unstable/main Sources.diff/Index [27.9 kB] Get:3 http://deb.debian.org/debian unstable/main amd64 Packages.diff/Index [27.9 kB] Get:4 http://deb.debian.org/debian unstable/main Sources 2020-08-21-1400.36.pdiff [8299 B] Get:4 http://deb.debian.org/debian unstable/main Sources 2020-08-21-1400.36.pdiff [8299 B] Get:5 http://deb.debian.org/debian unstable/main amd64 Packages 2020-08-21-1400.36.pdiff [30.7 kB] Get:5 http://deb.debian.org/debian unstable/main amd64 Packages 2020-08-21-1400.36.pdiff [30.7 kB] Fetched 241 kB in 2s (110 kB/s) Reading package lists... Reading package lists... Building dependency tree... Reading state information... Calculating upgrade... 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. +--+ | Fetch source files | +--+ Local sources - /home/pravi/forge/ruby-team/build-area/ruby-net-dns_0.9.1-2.dsc exists in /home/pravi/forge/ruby-team/build-area; copying to chroot I: NOTICE: Log filtering will replace 'build/ruby-net-dns-JRLEUt/ruby-net-dns-0.9.1' with '<>' I: NOTICE: Log filtering will replace 'build/ruby-net-dns-JRLEUt' with '<>' +--+ | Install package build dependencies | +--+ Setup apt archive - Merged Build-Depends: debhelper-compat (= 12), gem2deb, rake, ruby-minitest-reporters, build-essential, fakeroot Filtered Build-Depends: debhelper-compat (= 12), gem2deb, rake, ruby-minitest-reporters, build-essential, fakeroot dpkg-deb: building package 'sbuild-build-depends-main-dummy' in '/<>/apt_archive/sbuild-build-depends-main-dummy.deb'. Ign:1 copy:/<>/apt_archive ./ InRelease Get:2 copy:/<>/apt_archive ./ Release [957 B] Ign:3 copy:/<>/apt_archive ./ Release.gpg Get:4 copy:/<>/apt_archive ./ Sources [395 B] Get:5 copy:/<>/apt_archive ./ Packages [477 B] Fetched 1829 B in 0s (94.6 kB/s) Reading package lists... Reading package lists... Install main build dependencies (apt-based resolver) Installing build dependencies Reading package lists... Building dependency tree... Reading state information... The following additional packages will be installed: autoconf automake autopoint autotools-dev bsdextrautils ca-certificates debhelper devscripts dh-autoreconf dh-strip-nondeterminism dirmngr dwz file gem2deb gem2deb-test-runner gettext gettext-base gnupg gnupg-l10n gnupg-utils gpg gpg-agent gpg-wks-client gpg-wks-server gpgconf gpgsm groff-base intltool-debian libarchive-zip-perl libassuan0 libb-hooks-op-check-perl libclass-method-modifiers-perl libcroco3 libdebhelper-perl libdevel-callchecker-perl libdynaloader-functions-perl libelf1 libencode-locale-perl libexpat1 libfile-homedir-perl libfile-listing-perl libfile-stripnondeterminism-perl libfile-which-perl libglib2.0-0 libgmp-dev libgmpxx4ldbl libhtml-parser-perl libhtml-tagset-perl libhtml-tree-perl libhttp-cookies-perl libhttp-date-perl libhttp-message-perl libhttp-negotiate-perl libicu67 libimport-into-perl libio-html-perl libio-pty-perl libio-socket-ssl-perl libipc-run-perl libksba8 libldap-2.4-2 libldap-common liblwp-mediatypes-perl liblwp-protocol-https-perl libmagic-mgc libmagic1 libmodule-runtime-perl libmoo-perl libncursesw6 libnet-http-perl libnet-ssleay-perl libnpth0 libparams-classify-perl libpipeline1 libpython3-stdlib libpython3.8-minimal libpython3.8-stdlib libreadline8 librole-tiny-perl libruby2.7 libsasl2-2 libsasl2-modules-db libsigsegv2 libsqlite3-0 lib
Bug#964899: ruby-net-dns: cannot reproduce ftbfs
Even with an ipv6 address with global scope, I can't reproduce it. See the attached sbuild log. Can you retry building it? sbuild (Debian sbuild) 0.79.1 (22 April 2020) on ilvala2 +==+ | ruby-net-dns 0.9.1-2 (amd64) Fri, 21 Aug 2020 16:48:53 + | +==+ Package: ruby-net-dns Version: 0.9.1-2 Source Version: 0.9.1-2 Distribution: unstable Machine Architecture: amd64 Host Architecture: amd64 Build Architecture: amd64 Build Type: full I: NOTICE: Log filtering will replace 'var/run/schroot/mount/unstable-amd64-sbuild-ce796322-0117-482d-83a7-c57785b2cb7a' with '<>' I: NOTICE: Log filtering will replace 'build/ruby-net-dns-AuzjZA/resolver-EpADco' with '<>' +--+ | Update chroot| +--+ Get:1 http://deb.debian.org/debian unstable InRelease [146 kB] Get:2 http://deb.debian.org/debian unstable/main Sources.diff/Index [27.9 kB] Get:3 http://deb.debian.org/debian unstable/main amd64 Packages.diff/Index [27.9 kB] Get:4 http://deb.debian.org/debian unstable/main Sources 2020-08-21-1400.36.pdiff [8299 B] Get:4 http://deb.debian.org/debian unstable/main Sources 2020-08-21-1400.36.pdiff [8299 B] Get:5 http://deb.debian.org/debian unstable/main amd64 Packages 2020-08-21-1400.36.pdiff [30.7 kB] Get:5 http://deb.debian.org/debian unstable/main amd64 Packages 2020-08-21-1400.36.pdiff [30.7 kB] Fetched 241 kB in 2s (121 kB/s) Reading package lists... Reading package lists... Building dependency tree... Reading state information... Calculating upgrade... 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. +--+ | Fetch source files | +--+ Local sources - /home/pravi/forge/ruby-team/build-area/ruby-net-dns_0.9.1-2.dsc exists in /home/pravi/forge/ruby-team/build-area; copying to chroot I: NOTICE: Log filtering will replace 'build/ruby-net-dns-AuzjZA/ruby-net-dns-0.9.1' with '<>' I: NOTICE: Log filtering will replace 'build/ruby-net-dns-AuzjZA' with '<>' +--+ | Install package build dependencies | +--+ Setup apt archive - Merged Build-Depends: debhelper-compat (= 12), gem2deb, rake, ruby-minitest-reporters, build-essential, fakeroot Filtered Build-Depends: debhelper-compat (= 12), gem2deb, rake, ruby-minitest-reporters, build-essential, fakeroot dpkg-deb: building package 'sbuild-build-depends-main-dummy' in '/<>/apt_archive/sbuild-build-depends-main-dummy.deb'. Ign:1 copy:/<>/apt_archive ./ InRelease Get:2 copy:/<>/apt_archive ./ Release [957 B] Ign:3 copy:/<>/apt_archive ./ Release.gpg Get:4 copy:/<>/apt_archive ./ Sources [395 B] Get:5 copy:/<>/apt_archive ./ Packages [476 B] Fetched 1828 B in 0s (78.2 kB/s) Reading package lists... Reading package lists... Install main build dependencies (apt-based resolver) Installing build dependencies Reading package lists... Building dependency tree... Reading state information... The following additional packages will be installed: autoconf automake autopoint autotools-dev bsdextrautils ca-certificates debhelper devscripts dh-autoreconf dh-strip-nondeterminism dirmngr dwz file gem2deb gem2deb-test-runner gettext gettext-base gnupg gnupg-l10n gnupg-utils gpg gpg-agent gpg-wks-client gpg-wks-server gpgconf gpgsm groff-base intltool-debian libarchive-zip-perl libassuan0 libb-hooks-op-check-perl libclass-method-modifiers-perl libcroco3 libdebhelper-perl libdevel-callchecker-perl libdynaloader-functions-perl libelf1 libencode-locale-perl libexpat1 libfile-homedir-perl libfile-listing-perl libfile-stripnondeterminism-perl libfile-which-perl libglib2.0-0 libgmp-dev libgmpxx4ldbl libhtml-parser-perl libhtml-tagset-perl libhtml-tree-perl libhttp-cookies-perl libhttp-date-perl libhttp-message-perl libhttp-negotiate-perl libicu67 libimport-into-perl libio-html-perl libio-pty-perl libio-socket-ssl-perl libipc-run-perl libksba8 libldap-2.4-2 libldap-common liblwp-mediatypes-perl liblwp-protocol-https-perl libmagic-mgc libmagic1 libmodule-runtime-perl libmoo-perl libncursesw6 libnet-http-perl libnet-ssleay-perl libnpth0 libparams-classify-perl libpipeline1 libpython3-stdlib libpython3.8-minimal libpython3.8-stdlib libreadline8 librole-tiny-perl libruby2.7 libsasl2-2 libsasl
Bug#966900: marked as done (range-v3: FTBFS: cc1plus: error: command-line option ‘-Wno-missing-prototypes’ is valid for C/ObjC but not for C++ [-Werror])
Your message dated Fri, 21 Aug 2020 16:50:36 + with message-id and subject line Bug#966900: fixed in range-v3 0.11.0-1 has caused the Debian Bug report #966900, regarding range-v3: FTBFS: cc1plus: error: command-line option ‘-Wno-missing-prototypes’ is valid for C/ObjC but not for C++ [-Werror] 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.) -- 966900: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=966900 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: range-v3 Version: 0.10.0-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): > cd /<>/obj-x86_64-linux-gnu/test && /usr/bin/c++ > -I/<>/include -g -O2 -fdebug-prefix-map=/<>=. > -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time > -D_FORTIFY_SOURCE=2 -O3 -DNDEBUG -std=c++14 -Wall -Wextra -Werror > -fdiagnostics-show-template-tree -ftemplate-backtrace-limit=0 > -fomit-frame-pointer -Ofast -fstrict-aliasing -ffast-math > -fsized-deallocation -DRANGES_CXX_ALIGNED_NEW=0 -pedantic -pedantic-errors > -Wno-padded -Wno-missing-prototypes -Wno-old-style-cast -Wno-noexcept-type -o > CMakeFiles/bug1335.dir/bug1335.cpp.o -c /<>/test/bug1335.cpp > cc1plus: error: command-line option ‘-Wno-missing-prototypes’ is valid for > C/ObjC but not for C++ [-Werror] > [ 0%] Building CXX object test/CMakeFiles/bug566.dir/bug566.cpp.o > [ 1%] Building CXX object test/CMakeFiles/bug474.dir/bug474.cpp.o > cd /<>/obj-x86_64-linux-gnu/test && /usr/bin/c++ > -I/<>/include -g -O2 -fdebug-prefix-map=/<>=. > -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time > -D_FORTIFY_SOURCE=2 -O3 -DNDEBUG -std=c++14 -Wall -Wextra -Werror > -fdiagnostics-show-template-tree -ftemplate-backtrace-limit=0 > -fomit-frame-pointer -Ofast -fstrict-aliasing -ffast-math > -fsized-deallocation -DRANGES_CXX_ALIGNED_NEW=0 -pedantic -pedantic-errors > -Wno-padded -Wno-missing-prototypes -Wno-old-style-cast -Wno-noexcept-type -o > CMakeFiles/bug566.dir/bug566.cpp.o -c /<>/test/bug566.cpp > cd /<>/obj-x86_64-linux-gnu/test && /usr/bin/c++ > -I/<>/include -g -O2 -fdebug-prefix-map=/<>=. > -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time > -D_FORTIFY_SOURCE=2 -O3 -DNDEBUG -std=c++14 -Wall -Wextra -Werror > -fdiagnostics-show-template-tree -ftemplate-backtrace-limit=0 > -fomit-frame-pointer -Ofast -fstrict-aliasing -ffast-math > -fsized-deallocation -DRANGES_CXX_ALIGNED_NEW=0 -pedantic -pedantic-errors > -Wno-padded -Wno-missing-prototypes -Wno-old-style-cast -Wno-noexcept-type -o > CMakeFiles/bug474.dir/bug474.cpp.o -c /<>/test/bug474.cpp > cc1plus: error: command-line option ‘-Wno-missing-prototypes’ is valid for > C/ObjC but not for C++ [-Werror] > cc1plus: error: command-line option ‘-Wno-missing-prototypes’ is valid for > C/ObjC but not for C++ [-Werror] > Scanning dependencies of target test.range.v3.headers > make[4]: Leaving directory '/<>/obj-x86_64-linux-gnu' > make -f CMakeFiles/test.range.v3.headers.dir/build.make > CMakeFiles/test.range.v3.headers.dir/build > make[4]: Entering directory '/<>/obj-x86_64-linux-gnu' > [ 1%] Building CXX object > CMakeFiles/test.range.v3.headers.dir/headers/concepts/concepts.cpp.o > /usr/bin/c++ -I/<>/include -g -O2 > -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat > -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -O3 -DNDEBUG > -std=c++14 -Wall -Wextra -Werror -fdiagnostics-show-template-tree > -ftemplate-backtrace-limit=0 -fomit-frame-pointer -Ofast -fstrict-aliasing > -ffast-math -fsized-deallocation -DRANGES_CXX_ALIGNED_NEW=0 -o > CMakeFiles/test.range.v3.headers.dir/headers/concepts/concepts.cpp.o -c > /<>/obj-x86_64-linux-gnu/headers/concepts/concepts.cpp > [ 1%] Building CXX object > CMakeFiles/test.range.v3.headers.dir/headers/concepts/swap.cpp.o > /usr/bin/c++ -I/<>/include -g -O2 > -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat > -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -O3 -DNDEBUG > -std=c++14 -Wall -Wextra -Werror -fdiagnostics-show-template-tree > -ftemplate-backtrace-limit=0 -fomit-frame-pointer -Ofast -fstrict-aliasing > -ffast-math -fsized-deallocation -DRANGES_CXX_ALIGNED_NEW=0 -o > CMakeFiles/test.range.v3.headers.dir/headers/concepts/swap.cpp.o -c > /<>/obj-x86_64-linux-gnu/headers/concepts/swap.cpp > [ 1%] Building CXX object > CMakeFiles/test.range.v3.headers.dir/headers/conc
Processed: Missing TLS symlink
Processing commands for cont...@bugs.debian.org: > reassign 956499 libgl1-mesa-dri Bug #956499 [libgl1-mesa-dr1] Missing TLS symlink Warning: Unknown package 'libgl1-mesa-dr1' Bug reassigned from package 'libgl1-mesa-dr1' to 'libgl1-mesa-dri'. No longer marked as found in versions 20.1.5-1. Ignoring request to alter fixed versions of bug #956499 to the same values previously set > found 956499 20.1.5-1 Bug #956499 [libgl1-mesa-dri] Missing TLS symlink Marked as found in versions mesa/20.1.5-1. > End of message, stopping processing here. Please contact me if you need assistance. -- 956499: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=956499 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: bug 956499 is forwarded to https://gitlab.freedesktop.org/mesa/drm/-/issues/50
Processing commands for cont...@bugs.debian.org: > forwarded 956499 https://gitlab.freedesktop.org/mesa/drm/-/issues/50 Bug #956499 [libgl1-mesa-dri] Missing TLS symlink Set Bug forwarded-to-address to 'https://gitlab.freedesktop.org/mesa/drm/-/issues/50'. > thanks Stopping processing here. Please contact me if you need assistance. -- 956499: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=956499 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#967233: marked as done (wims-help: Unversioned Python removal in sid/bullseye)
Your message dated Fri, 21 Aug 2020 17:34:53 + with message-id and subject line Bug#967233: fixed in wims-help 4.01-4 has caused the Debian Bug report #967233, regarding wims-help: Unversioned Python removal in sid/bullseye to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 967233: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=967233 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:wims-help Version: 4.01-3 Severity: serious Tags: sid bullseye User: debian-pyt...@lists.debian.org Usertags: py2unversioned Python2 becomes end-of-live upstream, and Debian aims to remove Python2 from the distribution, as discussed in https://lists.debian.org/debian-python/2019/07/msg00080.html We will keep some Python2 package as discussed in https://lists.debian.org/debian-python/2020/07/msg00039.html but removing the unversioned python packages python-minimal, python, python-dev, python-dbg, python-doc. Your package either build-depends, depends on one of those packages. Please either convert these packages to Python3, or if that is not possible, replaces the dependencies on the unversioned Python packages with one of the python2 dependencies (python2, python2-dev, python2-dbg, python2-doc). Please check for dependencies, build dependencies AND autopkg tests. If there are questions, please refer to the wiki page for the removal: https://wiki.debian.org/Python/2Removal, or ask for help on IRC #debian-python, or the debian-pyt...@lists.debian.org mailing list. --- End Message --- --- Begin Message --- Source: wims-help Source-Version: 4.01-4 Done: Georges Khaznadar We believe that the bug you reported is fixed in the latest version of wims-help, 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 967...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Georges Khaznadar (supplier of updated wims-help 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: Fri, 21 Aug 2020 18:56:08 +0200 Source: wims-help Binary: wims-help Architecture: source all Version: 4.01-4 Distribution: unstable Urgency: medium Maintainer: Georges Khaznadar Changed-By: Georges Khaznadar Description: wims-help - help files for wims Closes: 943265 967233 Changes: wims-help (4.01-4) unstable; urgency=medium . * upgraded to debhelper-compat (=12), Standards-Version: 4.5.0 * replaced calls to Python by calls to Python3 and updated the script debian/make-copyright.py; Closes: #967233; Closes: #943265 Checksums-Sha1: f25bb660bdaf1a2ed8b3d594f289d567d8cfd2a9 1746 wims-help_4.01-4.dsc e7a8751c7d42a36e9edfc7a85d26a8a5b7de21b5 2836 wims-help_4.01-4.debian.tar.xz 05deb424dec1c7aebf62f3caf1d80550b64c8195 13924836 wims-help_4.01-4_all.deb 0db4ee56ead46f9305f44f8c4916a1a498e15be3 6347 wims-help_4.01-4_amd64.buildinfo Checksums-Sha256: ef3bb7aa9ce1efcbb8d2b6907117e406acb8b687e2b7796e02644e3b969e344a 1746 wims-help_4.01-4.dsc 3634f8e672143ac17845ab003ec4e4ee6c2d3784b521f816699701d3cb317e8b 2836 wims-help_4.01-4.debian.tar.xz 18755134e9852baa42ecc92ddbbce0101239398a65348fb5319981f3e3c2c04c 13924836 wims-help_4.01-4_all.deb 5bfceefb7245b690bd4340c63699fbb2be074e53ce7bf0e98568f2db1187552f 6347 wims-help_4.01-4_amd64.buildinfo Files: 371a8a513cb0828397383562812a7b5a 1746 web extra wims-help_4.01-4.dsc 8d09350ca8bdd63a970002c36fcf8af4 2836 web extra wims-help_4.01-4.debian.tar.xz 62ab54c7930d3b9139d608805d2f28d2 13924836 web extra wims-help_4.01-4_all.deb a3d8f66a680a3d2f2164ee76551ee43d 6347 web extra wims-help_4.01-4_amd64.buildinfo -BEGIN PGP SIGNATURE- iQJIBAEBCAAyFiEEM0CzZP9nFT+3zK6FHCgWkHE2rjkFAl8//ewUHGdlb3JnZXNr QGRlYmlhbi5vcmcACgkQHCgWkHE2rjm/iw/8D8ULuvA6f0eojXFr26xzGIrpNAgj s+SUOzIiRvpuLEnWzFx+w3Zp2BE79rDwd3Ub/HkiVGhXYsbC+UqEoFmdMwfcOa7z gByS5xJV15x9czBiRF0veUOkOH3m2xieTpoFoEplvxhoMfKQ4navBCdgL2/IIdha Uri0IXZ/pOTsQH/S5ZIJsXokgnS2FGN8uu8GibwXVl+wOVUs4PEasKbb2AX/N9nc g03Fi5YTM01HJKPoQKClW6X5jsw3velURH4sQG/WxnYErA/ontrvsq5FOUjs+O35 7bKP/iGnBcJXpWV0H3/WX6+q7JNHc9Xn3p8fb6fV5jt0AnNyeE2Cc4NLQ9c4776H nx60ITi59HVnWS9JxtV2IQ6vGUV9ndpzQf4BZHCrtB5EnIpglx4Ywtq7Oliun0Sq qPkngtEUyTtzb4O+e1ScVM8iyo4I5Rg3US/wwvFaS
Bug#956990: marked as pending in aircrack-ng
Control: tag -1 pending Hello, Bug #956990 in aircrack-ng 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/pkg-security-team/aircrack-ng/-/commit/6c88dbd8974ae26fcf3ab190c5294f0e0b89fe83 Bump changelog for 1:1.6+git20200821.87bf5727-1 (closes: #956990) (this message was generated automatically) -- Greetings https://bugs.debian.org/956990
Processed: Bug#956990 marked as pending in aircrack-ng
Processing control commands: > tag -1 pending Bug #956990 [src:aircrack-ng] aircrack-ng: ftbfs with GCC-10 Added tag(s) pending. -- 956990: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=956990 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#957219: marked as done (foremost: ftbfs with GCC-10)
Your message dated Fri, 21 Aug 2020 19:03:30 + with message-id and subject line Bug#957219: fixed in foremost 1.5.7-9.1 has caused the Debian Bug report #957219, regarding foremost: 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.) -- 957219: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=957219 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:foremost Version: 1.5.7-9 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/foremost_1.5.7-9_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 [...] 2105 | unsigned int size_of_headers = 0; | ^~~ extract.c:2103:15: warning: variable ‘sizeofimage’ set but not used [-Wunused-but-set-variable] 2103 | unsigned int sizeofimage = 0; | ^~~ extract.c:2100:15: warning: variable ‘rva’ set but not used [-Wunused-but-set-variable] 2100 | unsigned int rva = 0; | ^~~ extract.c:2099:15: warning: variable ‘SizeOfUninitializedData’ set but not used [-Wunused-but-set-variable] 2099 | unsigned int SizeOfUninitializedData = 0; | ^~~ extract.c:2098:15: warning: variable ‘SizeOfInitializedData’ set but not used [-Wunused-but-set-variable] 2098 | unsigned int SizeOfInitializedData = 0; | ^ extract.c:2097:15: warning: variable ‘SizeOfCode’ set but not used [-Wunused-but-set-variable] 2097 | unsigned int SizeOfCode = 0; | ^~ extract.c: In function ‘extract_rar’: extract.c:2272:13: warning: variable ‘file_size’ set but not used [-Wunused-but-set-variable] 2272 | u_int64_t file_size = 0; | ^ api.c: In function ‘dump_dirent’: api.c:481:10: warning: variable ‘unknown’ set but not used [-Wunused-but-set-variable] 481 | short unknown; | ^~~ extract.c: In function ‘extract_exe’: extract.c:2139:29: warning: ‘:’ directive writing 1 byte into a region of size between 0 and 16 [-Wformat-overflow=] 2139 |"%02d/%02d/%04d %02d:%02d:%02d", | ^ In file included from /usr/include/stdio.h:867, from main.h:33, from extract.c:16: /usr/include/x86_64-linux-gnu/bits/stdio2.h:36:10: note: ‘__builtin___sprintf_chk’ output between 20 and 72 bytes into a destination of size 32 36 | return __builtin___sprintf_chk (__s, __USE_FORTIFY_LEVEL - 1, | ^~ 37 | __bos (__s), __fmt, __va_arg_pack ()); | ~ cc -D__LINUX -DLARGEFILE64_SOURCE -D_FILE_OFFSET_BITS=64 main.o state.o helpers.o config.o cli.o engine.o dir.o extract.o api.o -o foremost -Wl,-z,relro -Wl,-z,now /usr/bin/ld: state.o:./main.h:296: multiple definition of `wildcard'; main.o:./main.h:296: first defined here /usr/bin/ld: state.o:./main.h:348: multiple definition of `search_spec'; main.o:./main.h:348: first defined here /usr/bin/ld: state.o:./main.h:371: multiple definition of `signal_caught'; main.o:./main.h:371: first defined here /usr/bin/ld: helpers.o:./main.h:348: multiple definition of `search_spec'; main.o:./main.h:348: first defined here /usr/bin/ld: helpers.o:./main.h:296: multiple definition of `wildcard'; main.o:./main.h:296: first defined here /usr/bin/ld: helpers.o:./main.h:371: multiple definition of `signal_caught'; main.o:./ma
Processed: Lessen severity
Processing commands for cont...@bugs.debian.org: > # Release 3.4.0-2 builds against gfortran-9 as a workaround > severity 957432 important Bug #957432 [src:libcgns] libcgns: ftbfs with GCC-10 Severity set to 'important' from 'serious' > thanks Stopping processing here. Please contact me if you need assistance. -- 957432: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=957432 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#956990: marked as done (aircrack-ng: ftbfs with GCC-10)
Your message dated Fri, 21 Aug 2020 20:21:34 + with message-id and subject line Bug#956990: fixed in aircrack-ng 1:1.6+git20200821.87bf5727-1 has caused the Debian Bug report #956990, regarding aircrack-ng: 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.) -- 956990: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=956990 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:aircrack-ng Version: 1:1.6-4 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/aircrack-ng_1.6-4_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/include/x86_64-linux-gnu/bits/string_fortified.h:136:10: warning: ‘__builtin___strncat_chk’ output may be truncated copying 2 bytes from a string of length 15 [-Wstringop-truncation] 136 | return __builtin___strncat_chk (__dest, __src, __len, __bos (__dest)); | ^~ /usr/include/x86_64-linux-gnu/bits/string_fortified.h:136:10: warning: ‘__builtin___strncat_chk’ output may be truncated copying 2 bytes from a string of length 15 [-Wstringop-truncation] /bin/bash ./libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I. -I/<> -I/<>/include -I/<>/include -I/<>/lib -I/<>/lib -I/<>/lib/radiotap -I/<>/lib/radiotap -Wdate-time -D_FORTIFY_SOURCE=2 -pthread -DUSE_GCRYPT -Wall -O3 -std=gnu99 -fno-strict-aliasing -Wpointer-arith -Wstrict-overflow=2 -Wstrict-prototypes -fvisibility=hidden -fstack-protector-strong -Wno-unused-but-set-variable -Wno-array-bounds -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -c -o lib/ce-wpa/libaircrack_ce_wpa_la-crypto_engine.lo `test -f 'lib/ce-wpa/crypto_engine.c' || echo './'`lib/ce-wpa/crypto_engine.c libtool: compile: gcc -DHAVE_CONFIG_H -I. -I/<> -I/<>/include -I/<>/include -I/<>/lib -I/<>/lib -I/<>/lib/radiotap -I/<>/lib/radiotap -Wdate-time -D_FORTIFY_SOURCE=2 -pthread -DUSE_GCRYPT -Wall -O3 -std=gnu99 -fno-strict-aliasing -Wpointer-arith -Wstrict-overflow=2 -Wstrict-prototypes -fvisibility=hidden -fstack-protector-strong -Wno-unused-but-set-variable -Wno-array-bounds -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -c lib/ce-wpa/crypto_engine.c -fPIC -DPIC -o lib/ce-wpa/.libs/libaircrack_ce_wpa_la-crypto_engine.o /bin/bash ./libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I. -I/<> -I/<>/include -I/<>/include -I/<>/lib -I/<>/lib -I/<>/lib/radiotap -I/<>/lib/radiotap -Wdate-time -D_FORTIFY_SOURCE=2 -pthread -DUSE_GCRYPT -Wall -O3 -std=gnu99 -fno-strict-aliasing -Wpointer-arith -Wstrict-overflow=2 -Wstrict-prototypes -fvisibility=hidden -fstack-protector-strong -Wno-unused-but-set-variable -Wno-array-bounds -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -c -o lib/ce-wpa/libaircrack_ce_wpa_la-memory.lo `test -f 'lib/ce-wpa/memory.c' || echo './'`lib/ce-wpa/memory.c libtool: compile: gcc -DHAVE_CONFIG_H -I. -I/<> -I/<>/include -I/<>/include -I/<>/lib -I/<>/lib -I/<>/lib/radiotap -I/<>/lib/radiotap -Wdate-time -D_FORTIFY_SOURCE=2 -pthread -DUSE_GCRYPT -Wall -O3 -std=gnu99 -fno-strict-aliasing -Wpointer-arith -Wstrict-overflow=2 -Wstrict-prototypes -fvisibility=hidden -fstack-protector-strong -Wno-unused-but-set-variable -Wno-array-bounds -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -c lib/ce-wpa/memory
Processed: exactimage: FTBFS against ilmbase/openexr 2.5.x
Processing control commands: > block 968580 by -1 Bug #968580 [release.debian.org] transition: ilmbase/openexr 968580 was not blocked by any bugs. 968580 was not blocking any bugs. Added blocking bug(s) of 968580: 968829 -- 968580: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=968580 968829: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=968829 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#968833: CVE-2020-24368
Package: icingaweb2 Severity: grave Tags: security X-Debbugs-Cc: Debian Security Team This was assigned CVE-2020-24368: https://icinga.com/2020/08/19/icinga-web-security-release-v2-6-4-v2-7-4-and-v2-8-2/ https://github.com/Icinga/icingaweb2/issues/4226 Cheers, Moritz
Bug#959444: marked as done (openexr: CVE-2020-11758 CVE-2020-11759 CVE-2020-11760 CVE-2020-11761 CVE-2020-11762 CVE-2020-11763 CVE-2020-11764 CVE-2020-11765)
Your message dated Fri, 21 Aug 2020 21:19:47 + with message-id and subject line Bug#959444: fixed in openexr 2.5.3-2 has caused the Debian Bug report #959444, regarding openexr: CVE-2020-11758 CVE-2020-11759 CVE-2020-11760 CVE-2020-11761 CVE-2020-11762 CVE-2020-11763 CVE-2020-11764 CVE-2020-11765 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.) -- 959444: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=959444 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: openexr Version: 2.3.0-6 Severity: grave Tags: security upstream Justification: user security hole Hi, The following vulnerabilities were published for openexr, all are fixed in 2.4.1. CVE-2020-11758[0]: | An issue was discovered in OpenEXR before 2.4.1. There is an out-of- | bounds read in ImfOptimizedPixelReading.h. CVE-2020-11759[1]: | An issue was discovered in OpenEXR before 2.4.1. Because of integer | overflows in CompositeDeepScanLine::Data::handleDeepFrameBuffer and | readSampleCountForLineBlock, an attacker can write to an out-of-bounds | pointer. CVE-2020-11760[2]: | An issue was discovered in OpenEXR before 2.4.1. There is an out-of- | bounds read during RLE uncompression in rleUncompress in ImfRle.cpp. CVE-2020-11761[3]: | An issue was discovered in OpenEXR before 2.4.1. There is an out-of- | bounds read during Huffman uncompression, as demonstrated by | FastHufDecoder::refill in ImfFastHuf.cpp. CVE-2020-11762[4]: | An issue was discovered in OpenEXR before 2.4.1. There is an out-of- | bounds read and write in DwaCompressor::uncompress in | ImfDwaCompressor.cpp when handling the UNKNOWN compression case. CVE-2020-11763[5]: | An issue was discovered in OpenEXR before 2.4.1. There is an | std::vector out-of-bounds read and write, as demonstrated by | ImfTileOffsets.cpp. CVE-2020-11764[6]: | An issue was discovered in OpenEXR before 2.4.1. There is an out-of- | bounds write in copyIntoFrameBuffer in ImfMisc.cpp. CVE-2020-11765[7]: | An issue was discovered in OpenEXR before 2.4.1. There is an off-by- | one error in use of the ImfXdr.h read function by | DwaCompressor::Classifier::Classifier, leading to an out-of-bounds | read. If you fix the vulnerabilities please also make sure to include the CVE (Common Vulnerabilities & Exposures) ids in your changelog entry. For further information see: [0] https://security-tracker.debian.org/tracker/CVE-2020-11758 https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-11758 [1] https://security-tracker.debian.org/tracker/CVE-2020-11759 https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-11759 [2] https://security-tracker.debian.org/tracker/CVE-2020-11760 https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-11760 [3] https://security-tracker.debian.org/tracker/CVE-2020-11761 https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-11761 [4] https://security-tracker.debian.org/tracker/CVE-2020-11762 https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-11762 [5] https://security-tracker.debian.org/tracker/CVE-2020-11763 https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-11763 [6] https://security-tracker.debian.org/tracker/CVE-2020-11764 https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-11764 [7] https://security-tracker.debian.org/tracker/CVE-2020-11765 https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-11765 [8] https://bugs.chromium.org/p/project-zero/issues/detail?id=1987 Regards, Salvatore --- End Message --- --- Begin Message --- Source: openexr Source-Version: 2.5.3-2 Done: m...@debian.org (Matteo F. Vescovi) We believe that the bug you reported is fixed in the latest version of openexr, 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 959...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Matteo F. Vescovi (supplier of updated openexr 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: Fri, 21 Aug 2020 22:56:55 +0200 Source: openexr Architecture: source Version: 2.5.3-2 Distribution: unstable Urgency: medium Maintainer: Debian PhotoTools Maintainers Changed-By: Matteo F. Vescovi Closes: 959444 Cha
Bug#968747: marked as done (vim-gtk3: vim (when linked to vim-gtk3 or vim-nox) fails to start due to undefined symbol)
Your message dated Fri, 21 Aug 2020 22:15:53 -0400 with message-id <20200822021553.d7k2pqzahdep3k6n@localhost> and subject line Re: Bug#968747: vim-gtk3: vim (when linked to vim-gtk3 or vim-nox) fails to start due to undefined symbol has caused the Debian Bug report #968747, regarding vim-gtk3: vim (when linked to vim-gtk3 or vim-nox) fails to start due to undefined symbol 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.) -- 968747: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=968747 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: vim-gtk3 Version: 2:8.2.0716-3 Severity: grave Justification: renders package unusable After dist-upgrading Debian testing to bullseye/sid, vim/ex/gvim/etc. no longer started: vim: symbol lookup error: /usr/lib/x86_64-linux-gnu/libpython3.8.so.1.0: undefined symbol: XML_SetHashSalt A check shows that this only affects vim.gtk3 and vim.nox; vim.basic works fine. -- Package-specific info: --- real paths of main Vim binaries --- /usr/bin/vi is /usr/bin/vim.gtk3 /usr/bin/vim is /usr/bin/vim.gtk3 /usr/bin/gvim is /usr/bin/vim.gtk3 -- System Information: Debian Release: bullseye/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.7.0-2-amd64 (SMP w/4 CPU threads) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages vim-gtk3 depends on: ii libacl1 2.2.53-8 ii libc62.31-3 ii libcairo21.16.0-4 ii libcanberra0 0.30-7 ii libgdk-pixbuf2.0-0 2.40.0+dfsg-5 ii libglib2.0-0 2.64.4-1 ii libgpm2 1.20.7-6 ii libgtk-3-0 3.24.22-1 ii libice6 2:1.0.9-2 ii liblua5.2-0 5.2.4-1.1+b3 ii libpango-1.0-0 1.46.0-2 ii libpangocairo-1.0-0 1.46.0-2 ii libperl5.30 5.30.3-4 ii libpython3.8 3.8.5-2 ii libruby2.7 2.7.1-3 ii libselinux1 3.1-2 ii libsm6 2:1.2.3-1 ii libtcl8.68.6.10+dfsg-1 ii libtinfo66.2-1 ii libx11-6 2:1.6.10-3 ii libxt6 1:1.1.5-1+b3 ii vim-common 2:8.2.0716-3 ii vim-gui-common 2:8.2.0716-3 ii vim-runtime 2:8.2.0716-3 vim-gtk3 recommends no packages. Versions of packages vim-gtk3 suggests: ii cscope15.9-1 ii fonts-dejavu 2.37-2 ii gnome-icon-theme 3.12.0-3 ii vim-doc 2:8.2.0716-3 -- no debconf information --- End Message --- --- Begin Message --- On Thu, Aug 20, 2020 at 09:24:01PM +0200, Tim Van Holder wrote: > After dist-upgrading Debian testing to bullseye/sid, vim/ex/gvim/etc. no > longer > started: > > vim: symbol lookup error: /usr/lib/x86_64-linux-gnu/libpython3.8.so.1.0: > undefined symbol: XML_SetHashSalt While trying to load libpython3.8.so.1.0, which requires libexpat.so.1, it couldn't resolve expat's XML_SetHashSalt symbol. This suggests you either have a broken libexpat1 package installed or a version of it that's not built by Debian. "ldd /usr/lib/x86_64-linux-gnu/libpython3.8.so.1.0 | grep expat" should show which libexpat is being loaded. It should also be in /usr/lib/x86_64-linux-gnu. > A check shows that this only affects vim.gtk3 and vim.nox; vim.basic works > fine. That's because vim.basic doesn't include the language interpreters. Cheers, -- James GPG Key: 4096R/91BF BF4D 6956 BD5D F7B7 2D23 DFE6 91AE 331B A3DB--- End Message ---
Bug#957160: marked as done (e17: ftbfs with GCC-10)
Your message dated Fri, 21 Aug 2020 19:26:05 -0700 with message-id <20200822022531.eswhaekmqczbzivh@stgulik> and subject line Re: Bug#957160: e17: ftbfs with GCC-10 has caused the Debian Bug report #957160, regarding e17: 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.) -- 957160: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=957160 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:e17 Version: 0.23.1-4 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/e17_0.23.1-4_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 [...] [235/691] /usr/bin/wayland-scanner code ../src/bin/generated/../../protocol/action_route.xml src/bin/3a6e061@@loader@sha/action_route-protocol.c Using "code" is deprecated - use private-code or public-code. See the help page for details. [236/691] /usr/bin/wayland-scanner client-header ../src/bin/generated/../../protocol/e-gadget.xml src/bin/3a6e061@@loader@sha/e-gadget-client-protocol.h [237/691] /usr/bin/wayland-scanner code ../src/bin/generated/../../protocol/e-gadget.xml src/bin/3a6e061@@loader@sha/e-gadget-protocol.c Using "code" is deprecated - use private-code or public-code. See the help page for details. [238/691] cc -Isrc/bin/3a6e061@@loader@sha -Isrc/bin -I../src/bin -Isrc/bin/../.. -I../src/bin/../.. -I/usr/include/uuid -I/usr/include/elementary-1 -I/usr/include/ecore-x-1 -I/usr/include/ecore-wl2-1 -I/usr/include/ecore-drm2-1 -I/usr/include/elput-1 -I/usr/include/ethumb-client-1 -I/usr/include/ethumb-1 -I/usr/include/edje-1 -I/usr/include/ecore-evas-1 -I/usr/include/ecore-input-evas-1 -I/usr/include/ecore-input-1 -I/usr/include/ecore-imf-evas-1 -I/usr/include/ecore-imf-1 -I/usr/include/embryo-1 -I/usr/include/ecore-audio-1 -I/usr/include/ephysics-1 -I/usr/include/bullet -I/usr/include/elocation-1 -I/usr/include/emotion-1 -I/usr/include/evas-1 -I/usr/include/evas-1/canvas -I/usr/include/evas-1/gesture -I/usr/include/ector-1 -I/usr/include/eeze-1 -I/usr/include/libmount -I/usr/include/blkid -I/usr/include/freetype2 -I/usr/include/libpng16 -I/usr/include/fribidi -I/usr/include/luajit-2.1 -I/usr/include/harfbuzz -I/usr/include/eio-1 -I/usr/include/efreet-1 -I/usr/include/ecore-file-1 -I/usr/include/ecore-ipc-1 -I/usr/include/ecore-con-1 -I/usr/include/eldbus-1 -I/usr/include/dbus-1.0 -I/usr/lib/x86_64-linux-gnu/dbus-1.0/include -I/usr/include/ecore-1 -I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/include/eet-1 -I/usr/include/emile-1 -I/usr/include/p11-kit-1 -I/usr/include/efl-1/interfaces -I/usr/include/eo-1 -I/usr/include/eina-1 -I/usr/include/efl-1 -I/usr/include/eina-1/eina -I/usr/include/x86_64-linux-gnu -fdiagnostics-color=always -pipe -D_FILE_OFFSET_BITS=64 -std=gnu99 -DHAVE_CONFIG_H=1 -Wall -W -Wpointer-arith -Wshadow -Wno-missing-field-initializers -Wfloat-equal -Wuninitialized -Wundef -Wcast-align -Wformat=2 -Wno-format-y2k '-DPACKAGE_BIN_DIR="/usr/bin"' '-DPACKAGE_LIB_DIR="/usr/lib/x86_64-linux-gnu"' '-DPACKAGE_DATA_DIR="/usr/share/enlightenment"' '-DPACKAGE_SYSCONF_DIR="/etc"' -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC -pthrea d -D_REENTRANT -MD -MQ 'src/bin/3a6e061@@loader@sha/meson-generated_action_route-protocol.c.o' -MF 'src/bin/3a6e061@@loader@sha/meson-generated_action_route-protocol.c.o.d' -o 'src/bin/3a6e061@@loader@sha/meson-generated_action_route-protocol.c.
Bug#968839: pyacoustid: autopkgtest regression: python: not found
Source: pyacoustid Version: 1.2.0-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 pyacoustid you added an autopkgtest, great. However, it fails. I copied some of the output at the bottom of this report. I think you need to use $(python2) instead of $(python). 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=pyacoustid https://ci.debian.net/data/autopkgtest/testing/amd64/p/pyacoustid/6421811/log.gz autopkgtest [13:31:49]: test fingerprint-calculation: [--- /usr/share/sounds/freedesktop/stereo/alarm-clock-elapsed.oga: OK /tmp/autopkgtest-lxc.9dkmffjn/downtmp/build.vae/src/debian/tests/fingerprint-calculation: 24: python: not found autopkgtest [13:31:49]: test fingerprint-calculation: ---] signature.asc Description: OpenPGP digital signature
Processed: block 933116 by 968836
Processing commands for cont...@bugs.debian.org: > block 933116 by 968836 Bug #933116 [libcgi-application-plugin-viewcode-perl] libcgi-application-plugin-viewcode-perl: build-depends on pkg-components that won't be in Bullseye unless it finds a new upstream maintainer 933116 was not blocked by any bugs. 933116 was blocking: 933110 Added blocking bug(s) of 933116: 968836 > thanks Stopping processing here. Please contact me if you need assistance. -- 933116: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=933116 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#968833: marked as done (CVE-2020-24368)
Your message dated Sat, 22 Aug 2020 06:03:44 + with message-id and subject line Bug#968833: fixed in icingaweb2 2.8.2-1 has caused the Debian Bug report #968833, regarding CVE-2020-24368 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.) -- 968833: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=968833 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: icingaweb2 Severity: grave Tags: security X-Debbugs-Cc: Debian Security Team This was assigned CVE-2020-24368: https://icinga.com/2020/08/19/icinga-web-security-release-v2-6-4-v2-7-4-and-v2-8-2/ https://github.com/Icinga/icingaweb2/issues/4226 Cheers, Moritz --- End Message --- --- Begin Message --- Source: icingaweb2 Source-Version: 2.8.2-1 Done: Bas Couwenberg We believe that the bug you reported is fixed in the latest version of icingaweb2, 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 968...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Bas Couwenberg (supplier of updated icingaweb2 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, 22 Aug 2020 07:16:12 +0200 Source: icingaweb2 Architecture: source Version: 2.8.2-1 Distribution: unstable Urgency: high Maintainer: Debian Nagios Maintainer Group Changed-By: Bas Couwenberg Closes: 968833 Changes: icingaweb2 (2.8.2-1) unstable; urgency=high . * Team upload. * New upstream release. - Fixes CVE-2020-24368. (closes: #968833) * Update uglifyjs options for 3.10.1. * Update lintian overrides. Checksums-Sha1: 6c0c26d9f2a7c3ca6f9a757e6177b34cb5e18dc0 2354 icingaweb2_2.8.2-1.dsc 6220132866baf03bef0e532cf232a2ea8b3d2252 8514166 icingaweb2_2.8.2.orig.tar.gz d2826ed318878deb3e6f5c3273a1d45d4eb64f86 12824 icingaweb2_2.8.2-1.debian.tar.xz 8a375731dd01a60f4f6dcda2e748a0087212436e 8357 icingaweb2_2.8.2-1_amd64.buildinfo Checksums-Sha256: 52f12aeb1b6b0768fcb64b31075c4b498adad3ac2243da8a3a1da98229a0c5b0 2354 icingaweb2_2.8.2-1.dsc 47d64bc4eeb574ca4ca2f765866a1612ed885d47d53cb3e7dc19adeb10b2b3db 8514166 icingaweb2_2.8.2.orig.tar.gz 789856ff7f97ed2da73a22bd9f2acdf34884307cc0f5729d2f8d72ea7d25cf98 12824 icingaweb2_2.8.2-1.debian.tar.xz 4e73e489b71bc6f080a2c8beb1cbf3d4fc17f009565bc25e9197d88942959f28 8357 icingaweb2_2.8.2-1_amd64.buildinfo Files: 1ce76448dacfa23a5779a7f1e3313024 2354 admin optional icingaweb2_2.8.2-1.dsc a6574b5f5f0af00bb1f4c53ff4322fe3 8514166 admin optional icingaweb2_2.8.2.orig.tar.gz e6bfbc0454efd4604531c12795cb507c 12824 admin optional icingaweb2_2.8.2-1.debian.tar.xz 763b05c7251457eb46af1169d039df2c 8357 admin optional icingaweb2_2.8.2-1_amd64.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEgYLeQXBWQI1hRlDRZ1DxCuiNSvEFAl9AsHAACgkQZ1DxCuiN SvGEOxAAuWs4QL1TCgRKmfBeL8gnMmE+mCeqTbcNjU0I83tTevGhd/jPzrxOVq7T ygHE846mRe1q156uVC7dX4PCl6jem/A9vxsAEteTWvztDQppD2V63cjbDFr4jZRH GebSvMZnvJsY7p7CdqX3+MHbTATUgj6VHAS5rtp08ciotBQj9bTZEdqWsR3IoMDD o7e0DihHvk0amoOU2uzxpEYxowTQlHdsszyeXPf5Z7IRVX7u95hN+zAfNajE+NQa 15jxVKN40P6mAx8McDPSqFRVXj/NcSkFckdXwTdZSqQ1ilhqh917stYAGDdFcpKT lmzXl2h6thO/eldLtPwxilcjdBdn9q/7xUoiNvkSIhucJaZqb4w+wwQzDFhEdr16 ElgcjSy8OGhCgKnjBy2aDr+BuOeBJ2H/Ub3r9Cm6yqCDujN1xGMSwzgQ58il9ZTi N1WhQ3oLZMGbCHBtbnhK2OeJF3sJfzvOHkAb5cSs77ZpPmUHA4MgdHGHh++GCAU+ Q6aJDpTq4dFKXRJBk1ho9Dv2creh2Yt01+1exvfMxUXYtOo1ryDRctZ1ojFce9u2 r7CBDl6QePLtYbmETvydxJKFK4cfsuBtKGYdaHiuVQJZu9M3ZTSDXg7JuVLHsL1R WRYvy+5mcl/FHR8zdBmxArRRJIRfQR50blIMkREbp6KTlBtbUcY= =N5W4 -END PGP SIGNATURE End Message ---
Processed: Re: [Pkg-nagios-devel] Bug#968833: CVE-2020-24368
Processing control commands:
> tags -1 pending
Bug #968833 {Done: Bas Couwenberg } [icingaweb2]
CVE-2020-24368
Added tag(s) pending.
--
968833: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=968833
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#968833: [Pkg-nagios-devel] Bug#968833: CVE-2020-24368
Control: tags -1 pending Hi Moritz, This is fixed in icingaweb2 (2.8.2-1) which was just uploaded to unstable. I've also prepared an update for buster, see: https://salsa.debian.org/nagios-team/pkg-icingaweb2/-/commits/buster Do you want to upload that to security-master or shall I? Kind Regards, Bas -- GPG Key ID: 4096R/6750F10AE88D4AF1 Fingerprint: 8182 DE41 7056 408D 6146 50D1 6750 F10A E88D 4AF1
Bug#968841: mozilla-devstripts FTBFS: tests/dh_xul-ext/test: No such file or directory
Package: mozilla-devscripts X-Debbugs-Cc: d...@debian.org Version: 0.54.1 Severity: serious Justification: FTBFS Dear maintainers, Matthias, The latest upload of mozilla-devscripts FTBFS. https://buildd.debian.org/status/fetch.php?pkg=mozilla-devscripts&arch=all&ver=0.54.1&stamp=1596924970&raw=0 Command: dpkg-buildpackage -us -uc -mall / amd64 / i386 Build Daemon (x86-conova-01) -A -rfakeroot --changes-option=-O../mozilla-devscripts_0.54.1_all-buildd.changes --buildinfo-option=-O../mozilla-devscripts_0.54.1_all-buildd.buildinfo dpkg-buildpackage: info: source package mozilla-devscripts dpkg-buildpackage: info: source version 0.54.1 dpkg-buildpackage: info: source distribution unstable dpkg-source --before-build . dpkg-source: warning: relation > is deprecated: use >> or >= dpkg-checkbuilddeps: warning: relation > is deprecated: use >> or >= fakeroot debian/rules clean dh clean --with python2,python3 dh_auto_clean make -j4 clean make[1]: Entering directory '/<>' rm -rf build *.pyc make[1]: Leaving directory '/<>' dh_clean debian/rules build-indep dh build-indep --with python2,python3 dh_update_autotools_config -i dh_autoreconf -i dh_auto_configure -i dh_auto_build -i make -j4 "INSTALL=install --strip-program=true" make[1]: Entering directory '/<>' make[1]: Nothing to be done for 'build'. make[1]: Leaving directory '/<>' dh_auto_test -i make -j4 test make[1]: Entering directory '/<>' tests/dh_xul-ext/test make[1]: tests/dh_xul-ext/test: No such file or directory make[1]: *** [Makefile:4: test] Error 127 make[1]: Leaving directory '/<>' dh_auto_test: error: make -j4 test returned exit code 2 make: *** [debian/rules:4: build-indep] Error 25 dpkg-buildpackage: error: debian/rules build-indep subprocess returned exit status 2 Build finished at 2020-08-08T22:16:06Z Paul -- System Information: Debian Release: bullseye/sid APT prefers testing APT policy: (990, 'testing'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 5.7.0-2-amd64 (SMP w/8 CPU threads) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages mozilla-devscripts depends on: ii perl 5.30.3-4 ii python 2.7.17-2 pn python-librdf ii python22.7.17-2 ii python33.8.2-3 ii unzip 6.0-25 ii zip3.0-11+b1 mozilla-devscripts recommends no packages. mozilla-devscripts suggests no packages. signature.asc Description: OpenPGP digital signature
Processed: tagging 968740
Processing commands for cont...@bugs.debian.org: > tags 968740 + upstream Bug #968740 [etcd] CVE-2020-15106 CVE-2020-15112 CVE-2020-15113 CVE-2020-15114 CVE-2020-15115 Added tag(s) upstream. > thanks Stopping processing here. Please contact me if you need assistance. -- 968740: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=968740 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: tagging 968833, found 968833 in 2.8.2-1, found 968833 in 2.6.2-3
Processing commands for cont...@bugs.debian.org:
> tags 968833 + upstream
Bug #968833 {Done: Bas Couwenberg } [icingaweb2]
CVE-2020-24368
Added tag(s) upstream.
> found 968833 2.8.2-1
Bug #968833 {Done: Bas Couwenberg } [icingaweb2]
CVE-2020-24368
Marked as found in versions icingaweb2/2.8.2-1; no longer marked as fixed in
versions icingaweb2/2.8.2-1 and reopened.
> found 968833 2.6.2-3
Bug #968833 [icingaweb2] CVE-2020-24368
Marked as found in versions icingaweb2/2.6.2-3.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
968833: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=968833
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Processed: bug 968833 is forwarded to https://github.com/Icinga/icingaweb2/issues/4226
Processing commands for cont...@bugs.debian.org: > forwarded 968833 https://github.com/Icinga/icingaweb2/issues/4226 Bug #968833 [icingaweb2] CVE-2020-24368 Set Bug forwarded-to-address to 'https://github.com/Icinga/icingaweb2/issues/4226'. > thanks Stopping processing here. Please contact me if you need assistance. -- 968833: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=968833 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#963663: marked as done (nitime: FTBFS with Sphinx 3.1: TypeError: add_directive() takes from 3 to 4 positional arguments but 5 were given)
Your message dated Sat, 22 Aug 2020 06:48:41 +
with message-id
and subject line Bug#963663: fixed in nitime 0.8.1-4
has caused the Debian Bug report #963663,
regarding nitime: FTBFS with Sphinx 3.1: TypeError: add_directive() takes from
3 to 4 positional arguments but 5 were given
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.)
--
963663: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=963663
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: nitime
Version: 0.8.1-3
Severity: important
Tags: ftbfs
User: python-modules-t...@lists.alioth.debian.org
Usertags: sphinx3.1
Hi,
nitime fails to build with Sphinx 3.1, currently available in
experimental.
Relevant part (hopefully):
> make[2]: Entering directory '/<>/doc'
> ../tools/make_examples.py --no-exec
> python3 ../tools/build_modref_templates.py
> WARNING: Empty - nitime
> WARNING: Empty - nitime.algorithms
> WARNING: Empty - nitime.analysis
> WARNING: Empty - nitime.fmri
> WARNING: Empty - nitime.version
> 26 files written
> Build API docs finished.
> sphinx-build -b html -d _build/doctrees . _build/html
> Running Sphinx v3.1.1
> /<>/doc/conf.py:34: MatplotlibDeprecationWarning:
> The mpl_toolkits.axes_grid module was deprecated in Matplotlib 2.1 and will
> be removed two minor releases later. Use mpl_toolkits.axes_grid1 and
> mpl_toolkits.axisartist, which provide the same functionality instead.
> __import__(package, fromlist=parts)
> WARNING: while setting up extension ipython_console_highlighting: extension
> 'ipython_console_highlighting' has no setup() function; is it really a Sphinx
> extension module?
>
> Exception occurred:
> File "/<>/doc/sphinxext/only_directives.py", line 40, in setup
> app.add_directive('htmlonly', html_only_directive, True, (0, 0, 0))
> TypeError: add_directive() takes from 3 to 4 positional arguments but 5 were
> given
> The full traceback has been saved in /tmp/sphinx-err-k48qa3n2.log, if you
> want to report the issue to the developers.
> Please also report this if it was a user error, so that a better error
> message can be provided next time.
> A bug report can be filed in the tracker at
> . Thanks!
> make[2]: *** [Makefile:35: htmlonly] Error 2
The full build log is available from:
http://qa-logs.debian.net/2020/06/23/nitime_0.8.1-3_unstable_sphinx-exp.log
Please see [1] for Sphinx changelog, which may give a hint of what changes in
Sphinx caused this error.
Also see [2] for the list of deprecated/removed APIs and possible alternatives
to them.
Sphinx 3.1 is going to be uploaded to unstable in a couple of weeks. When that
happens, the severity of this bug will be bumped to serious.
In case you have questions, please Cc sph...@packages.debian.org on reply.
[1]: https://www.sphinx-doc.org/en/3.x/changes.html
[2]: https://www.sphinx-doc.org/en/3.x/extdev/deprecated.html
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: nitime
Source-Version: 0.8.1-4
Done: Nilesh Patra
We believe that the bug you reported is fixed in the latest version of
nitime, 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.
Nilesh Patra (supplier of updated nitime 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, 22 Aug 2020 02:34:08 +0530
Source: nitime
Architecture: source
Version: 0.8.1-4
Distribution: unstable
Urgency: medium
Maintainer: Debian Med Packaging Team
Changed-By: Nilesh Patra
Closes: 963663
Changes:
nitime (0.8.1-4) unstable; urgency=medium
.
* Team Upload.
* Fix according changed sphinx API (Closes: #963663)
* Remove ajax inclusion in html files
* Fix lintian
* debhelper-compat 13 (routine-update)
* Update upst
Processed: notfound 968833 in 2.8.2-1
Processing commands for cont...@bugs.debian.org: > notfound 968833 2.8.2-1 Bug #968833 [icingaweb2] CVE-2020-24368 No longer marked as found in versions icingaweb2/2.8.2-1. > thanks Stopping processing here. Please contact me if you need assistance. -- 968833: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=968833 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Fixed in last upload
Processing commands for cont...@bugs.debian.org: > fixed 966388 0.13.0-3 Bug #966388 [src:ruby-googleauth] ruby-googleauth breaks ruby-google-api-client from testing but misses the versioned Breaks Marked as fixed in versions ruby-googleauth/0.13.0-3. > -- Stopping processing here. Please contact me if you need assistance. -- 966388: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=966388 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#966388: marked as done (ruby-googleauth breaks ruby-google-api-client from testing but misses the versioned Breaks)
Your message dated Sat, 22 Aug 2020 12:19:22 +0530 with message-id <053b3b0b-018b-4d10-8a39-9b8c03b61...@onenetbeyond.org> and subject line Fixed in last upload has caused the Debian Bug report #966388, regarding ruby-googleauth breaks ruby-google-api-client from testing but misses the versioned Breaks 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.) -- 966388: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=966388 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: ruby-googleauth Control: found -1 ruby-googleauth/0.13.0-2 Affects: -1 src:ruby-google-api-client Severity: serious Tags: sid bullseye X-Debbugs-CC: debian...@lists.debian.org User: debian...@lists.debian.org Usertags: breaks Dear maintainer(s), With a recent upload of ruby-googleauth the autopkgtest of ruby-google-api-client fails in testing when that autopkgtest is run with the binary packages of ruby-googleauth from unstable. It passes when run with only packages from testing. In tabular form: passfail ruby-googleauthfrom testing0.13.0-2 ruby-google-api-client from testing0.28.4-1 versioned deps [0] from testingfrom unstable all others from testingfrom testing I copied some of the output at the bottom of this report. It seems to me that the version of ruby-google-api-client needed an update (which is available in unstable), but ruby-googleauth is missing a versioned Breaks on the version in testing. Once the versioned Breaks is added, the autopkgtest of ruby-google-api-client for the updated ruby-googleauth will be scheduled with ruby-google-api-client from unstable and if it passes, they can migrate together. Currently this regression is blocking the migration of ruby-googleauth [1] and ruby-google-api-client to testing. 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=ruby-googleauth https://ci.debian.net/data/autopkgtest/testing/amd64/r/ruby-google-api-client/6441812/log.gz autopkgtest [15:06:41]: test gem2deb-test-runner: [--- ┌──┐ │ Checking Rubygems dependency resolution on ruby2.7 │ └──┘ GEM_PATH= ruby2.7 -e gem\ \"google-api-client\" /usr/lib/ruby/2.7.0/rubygems/dependency.rb:313:in `to_specs': Could not find 'googleauth' (< 0.10.0, >= 0.5) - did find: [googleauth-0.13.0] (Gem::MissingSpecVersionError) signature.asc Description: OpenPGP digital signature --- End Message --- --- Begin Message --- fixed 966388 0.13.0-3 -- Sent from my Android device with K-9 Mail. Please excuse my brevity.--- End Message ---
Processed: notfound 968833 in 2.8.2-1, fixed 968833 in 2.8.2-1
Processing commands for cont...@bugs.debian.org: > notfound 968833 2.8.2-1 Bug #968833 [icingaweb2] CVE-2020-24368 Ignoring request to alter found versions of bug #968833 to the same values previously set > fixed 968833 2.8.2-1 Bug #968833 [icingaweb2] CVE-2020-24368 Marked as fixed in versions icingaweb2/2.8.2-1. > thanks Stopping processing here. Please contact me if you need assistance. -- 968833: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=968833 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
