Bug#936758: marked as done (jack-mixer: Python2 removal in sid/bullseye)
Your message dated Sun, 24 Nov 2019 07:39:13 + with message-id and subject line Bug#945354: Removed package(s) from unstable has caused the Debian Bug report #936758, regarding jack-mixer: Python2 removal in sid/bullseye to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 936758: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=936758 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:jack-mixer Version: 10-1 Severity: normal Tags: sid bullseye User: debian-pyt...@lists.debian.org Usertags: py2removal Python2 becomes end-of-live upstream, and Debian aims to remove Python2 from the distribution, as discussed in https://lists.debian.org/debian-python/2019/07/msg00080.html Your package either build-depends, depends on Python2, or uses Python2 in the autopkg tests. Please stop using Python2, and fix this issue by one of the following actions. - Convert your Package to Python3. This is the preferred option. In case you are providing a Python module foo, please consider dropping the python-foo package, and only build a python3-foo package. Please don't drop Python2 modules, which still have reverse dependencies, just document them. This is the preferred option. - If the package is dead upstream, cannot be converted or maintained in Debian, it should be removed from the distribution. If the package still has reverse dependencies, raise the severity to "serious" and document the reverse dependencies with the BTS affects command. If the package has no reverse dependencies, confirm that the package can be removed, reassign this issue to ftp.debian.org, make sure that the bug priority is set to normal and retitle the issue to "RM: PKG -- removal triggered by the Python2 removal". - If the package has still many users (popcon >= 300), or is needed to build another package which cannot be removed, document that by adding the "py2keep" user tag (not replacing the py2remove tag), using the debian-pyt...@lists.debian.org user. Also any dependencies on an unversioned python package (python, python-dev) must not be used, same with the python shebang. These have to be replaced by python2/python2.7 dependencies and shebang. This is the least preferred option. If the conversion or removal needs action on another package first, please document the blocking by using the BTS affects command, like affects + src:jack-mixer If there is no py2removal bug for that reverse-dependency, please file a bug on this package (similar to this bug report). If there are questions, please refer to the wiki page for the removal: https://wiki.debian.org/Python/2Removal, or ask for help on IRC #debian-python, or the debian-pyt...@lists.debian.org mailing list. --- End Message --- --- Begin Message --- Version: 10-1+rm Dear submitter, as the package jack-mixer has just been removed from the Debian archive unstable we hereby close the associated bug reports. We are sorry that we couldn't deal with your issue properly. For details on the removal, please see https://bugs.debian.org/945354 The version of this package that was in Debian prior to this removal can still be found using http://snapshot.debian.org/. Please note that the changes have been done on the master archive and will not propagate to any mirrors until the next dinstall run at the earliest. This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org. Debian distribution maintenance software pp. Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---
Bug#885309: marked as done (jack-mixer: Depends on unmaintained pygtk)
Your message dated Sun, 24 Nov 2019 07:39:13 + with message-id and subject line Bug#945354: Removed package(s) from unstable has caused the Debian Bug report #885309, regarding jack-mixer: Depends on unmaintained pygtk 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.) -- 885309: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=885309 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: jack-mixer Version: 10-1 Severity: serious User: pkg-gnome-maintain...@lists.alioth.debian.org Usertags: oldlibs pygtk Tags: sid buster pygtk is unmaintained upstream. It has not had a release since GNOME 3 was released in 2011. The way forward is to port your app to use GObject Introspection bindings. For more information on GObject Introspection see [1] and [2]. Please try to do this before the Buster release as we're going to try to remove pygtk this cycle. If you have any question don't hesitate to ask. [1] https://wiki.gnome.org/Projects/GObjectIntrospection [2] https://wiki.gnome.org/Projects/PyGObject On behalf of the Debian GNOME team, Jeremy Bicha --- End Message --- --- Begin Message --- Version: 10-1+rm Dear submitter, as the package jack-mixer has just been removed from the Debian archive unstable we hereby close the associated bug reports. We are sorry that we couldn't deal with your issue properly. For details on the removal, please see https://bugs.debian.org/945354 The version of this package that was in Debian prior to this removal can still be found using http://snapshot.debian.org/. Please note that the changes have been done on the master archive and will not propagate to any mirrors until the next dinstall run at the earliest. This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org. Debian distribution maintenance software pp. Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---
Bug#937160: marked as done (notify-python: Python2 removal in sid/bullseye)
Your message dated Sun, 24 Nov 2019 07:40:13 + with message-id and subject line Bug#945383: Removed package(s) from unstable has caused the Debian Bug report #937160, regarding notify-python: Python2 removal in sid/bullseye to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 937160: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=937160 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:notify-python Version: 0.1.1-4 Severity: normal Tags: sid bullseye User: debian-pyt...@lists.debian.org Usertags: py2removal Python2 becomes end-of-live upstream, and Debian aims to remove Python2 from the distribution, as discussed in https://lists.debian.org/debian-python/2019/07/msg00080.html Your package either build-depends, depends on Python2, or uses Python2 in the autopkg tests. Please stop using Python2, and fix this issue by one of the following actions. - Convert your Package to Python3. This is the preferred option. In case you are providing a Python module foo, please consider dropping the python-foo package, and only build a python3-foo package. Please don't drop Python2 modules, which still have reverse dependencies, just document them. This is the preferred option. - If the package is dead upstream, cannot be converted or maintained in Debian, it should be removed from the distribution. If the package still has reverse dependencies, raise the severity to "serious" and document the reverse dependencies with the BTS affects command. If the package has no reverse dependencies, confirm that the package can be removed, reassign this issue to ftp.debian.org, make sure that the bug priority is set to normal and retitle the issue to "RM: PKG -- removal triggered by the Python2 removal". - If the package has still many users (popcon >= 300), or is needed to build another package which cannot be removed, document that by adding the "py2keep" user tag (not replacing the py2remove tag), using the debian-pyt...@lists.debian.org user. Also any dependencies on an unversioned python package (python, python-dev) must not be used, same with the python shebang. These have to be replaced by python2/python2.7 dependencies and shebang. This is the least preferred option. If the conversion or removal needs action on another package first, please document the blocking by using the BTS affects command, like affects + src:notify-python If there is no py2removal bug for that reverse-dependency, please file a bug on this package (similar to this bug report). If there are questions, please refer to the wiki page for the removal: https://wiki.debian.org/Python/2Removal, or ask for help on IRC #debian-python, or the debian-pyt...@lists.debian.org mailing list. --- End Message --- --- Begin Message --- Version: 0.1.1-4+rm Dear submitter, as the package notify-python has just been removed from the Debian archive unstable we hereby close the associated bug reports. We are sorry that we couldn't deal with your issue properly. For details on the removal, please see https://bugs.debian.org/945383 The version of this package that was in Debian prior to this removal can still be found using http://snapshot.debian.org/. Please note that the changes have been done on the master archive and will not propagate to any mirrors until the next dinstall run at the earliest. This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org. Debian distribution maintenance software pp. Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---
Bug#885380: marked as done (notify-python: Depends on unmaintained pygtk)
Your message dated Sun, 24 Nov 2019 07:40:13 + with message-id and subject line Bug#945383: Removed package(s) from unstable has caused the Debian Bug report #885380, regarding notify-python: Depends on unmaintained pygtk 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.) -- 885380: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=885380 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: notify-python Version: 0.1.1-4 Severity: important User: pkg-gnome-maintain...@lists.alioth.debian.org Usertags: oldlibs pygtk Tags: sid buster pygtk is unmaintained upstream. It has not had a release since GNOME 3 was released in 2011. The way forward is to port your app to use GObject Introspection bindings (and gtk3). For more information on GObject Introspection see [1] and [2]. Please try to do this before the Buster release as we're going to try to remove pygtk this cycle. If you have any question don't hesitate to ask. [1] https://wiki.gnome.org/Projects/GObjectIntrospection [2] https://wiki.gnome.org/Projects/PyGObject On behalf of the Debian GNOME team, Jeremy Bicha --- End Message --- --- Begin Message --- Version: 0.1.1-4+rm Dear submitter, as the package notify-python has just been removed from the Debian archive unstable we hereby close the associated bug reports. We are sorry that we couldn't deal with your issue properly. For details on the removal, please see https://bugs.debian.org/945383 The version of this package that was in Debian prior to this removal can still be found using http://snapshot.debian.org/. Please note that the changes have been done on the master archive and will not propagate to any mirrors until the next dinstall run at the earliest. This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org. Debian distribution maintenance software pp. Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---
Bug#943930: marked as done (Should cvc3 be removed?)
Your message dated Sun, 24 Nov 2019 07:38:09 + with message-id and subject line Bug#945319: Removed package(s) from unstable has caused the Debian Bug report #943930, regarding Should cvc3 be removed? to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 943930: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=943930 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: cvc3 Severity: serious Should cvc3 be removed? It's unmaintained (last maintainer upload is from 2014 and the maintainer is also one of the authors) and FTBFSes since 1.5 years. Cheers, Moritz --- End Message --- --- Begin Message --- Version: 2.4.1-5.2+rm Dear submitter, as the package cvc3 has just been removed from the Debian archive unstable we hereby close the associated bug reports. We are sorry that we couldn't deal with your issue properly. For details on the removal, please see https://bugs.debian.org/945319 The version of this package that was in Debian prior to this removal can still be found using http://snapshot.debian.org/. Please note that the changes have been done on the master archive and will not propagate to any mirrors until the next dinstall run at the earliest. This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org. Debian distribution maintenance software pp. Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---
Bug#945392: hyperkitty: autopkgtest failures
Source: hyperkitty Version: 1.3.0-1 Severity: serious Justification: makes the package in question unusable or mostly so Dear Maintainer, The autopkgtest for your package are failing, which prevent the testing migration of networkx. The logging shows many exceptions like this: AttributeError: 'DiGraph' object has no attribute 'node' See: https://ci.debian.net/data/autopkgtest/testing/amd64/h/hyperkitty/3494471/log.gz Kind Regards, Bas
Bug#902386: marked as done (cvc3: FTBFS in API tests with Java 10 due to -d64 option removal)
Your message dated Sun, 24 Nov 2019 07:38:09 +
with message-id
and subject line Bug#945319: Removed package(s) from unstable
has caused the Debian Bug report #902386,
regarding cvc3: FTBFS in API tests with Java 10 due to -d64 option removal
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.)
--
902386: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=902386
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:cvc3
Version: 2.4.1-5.1
Severity: serious
Hi, after applying the patch sent to bug #873975 building the package
advances into the tests, but then fails like this:
*
Java API test
*
/usr/bin/make -C java test 2>&1 \
| tee -a regressions.log; [ ${PIPESTATUS[0]} -eq 0 ]
make[3]: Entering directory '/home/rt/debian/packages/qa/cvc3-2.4.1/java'
if [ ! -d /home/rt/debian/packages/qa/cvc3-2.4.1/java/lib ]; then mkdir -p
/home/rt/debian/packages/qa/cvc3-2.4.1/java/lib; fi
if [ ! -d obj ]; then mkdir -p obj; fi
/usr/lib/jvm/default-java/bin/java -d64
-Djava.library.path=../java/lib/x86_64-linux-gnu -ea -jar
../java/lib/cvc3test.jar
Unrecognized option: -d64
Error: Could not create the Java Virtual Machine.
Error: A fatal exception has occurred. Program will exit.
make[3]: *** [Makefile:273: test] Error 1
make[3]: Leaving directory '/home/rt/debian/packages/qa/cvc3-2.4.1/java'
make[2]: *** [Makefile:220: regress] Error 1
make[2]: Leaving directory '/home/rt/debian/packages/qa/cvc3-2.4.1'
make[1]: *** [Makefile:246: regress0] Error 2
make[1]: Leaving directory '/home/rt/debian/packages/qa/cvc3-2.4.1'
make: *** [/usr/share/cdbs/1/class/makefile.mk:113:
debian/stamp-makefile-check] Error 2
-- System Information:
Debian Release: buster/sid
APT prefers unstable
APT policy: (500, 'unstable'), (500, 'testing'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 4.16.0-2-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8) (ignored: LC_ALL
set to en_US.utf8), LANGUAGE=en_US:en (charmap=UTF-8) (ignored: LC_ALL set to
en_US.utf8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
--- End Message ---
--- Begin Message ---
Version: 2.4.1-5.2+rm
Dear submitter,
as the package cvc3 has just been removed from the Debian archive
unstable we hereby close the associated bug reports. We are sorry
that we couldn't deal with your issue properly.
For details on the removal, please see https://bugs.debian.org/945319
The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.
Please note that the changes have been done on the master archive and
will not propagate to any mirrors until the next dinstall run at the
earliest.
This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
ftpmas...@ftp-master.debian.org.
Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---
Bug#945393: skimage: autopkgtest failures
Source: skimage Version: 0.14.2-3 Severity: serious Justification: makes the package in question unusable or mostly so Dear Maintainer, The autopkgtest for your package are failing, which prevent the testing migration of networkx. The logging shows many exceptions like this: AttributeError: 'RAG' object has no attribute 'node' See: https://ci.debian.net/data/autopkgtest/testing/amd64/s/skimage/3494472/log.gz Kind Regards, Bas
Bug#873975: marked as done (FTBFS with Java 9 due to -source/-target only)
Your message dated Sun, 24 Nov 2019 07:38:09 + with message-id and subject line Bug#945319: Removed package(s) from unstable has caused the Debian Bug report #873975, regarding FTBFS with Java 9 due to -source/-target only 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.) -- 873975: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=873975 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: cvc3 Version: 2.4.1 Severity: normal User: debian-j...@lists.debian.org Usertags: default-java9 This package fails to build with default-jdk pointing to openjdk-9-jdk. The wiki has some common problems and their solutions: https://wiki.debian.org/Java/Java9Pitfalls An automated tool has decided that this package will build fine if the -source and -target options are changed to 1.6; no additional changes are required. This was done by building with a compiler that changed the settings automatically, then the real compiler, and diffing the results. This modified compiler will never be part of Debian. ant and Maven are supposed to do this for you, and I've tried to check that this package is not using ant or Maven correctly, but I might have messed up. Build log sample: make[2]: Entering directory '/build/cvc3-2.4.1/java' if [ ! -d obj ]; then mkdir -p obj; fi /usr/lib/jvm/default-java/bin/javac -Xlint -g -source 1.4 -sourcepath src \ -d obj src/cvc3/JniUtils.java warning: [options] bootstrap class path not set in conjunction with -source 1.4 error: Source option 1.4 is no longer supported. Use 1.6 or later. make[2]: *** [JniUtils.class] Error 2 Makefile:166: recipe for target 'JniUtils.class' failed make[2]: Leaving directory '/build/cvc3-2.4.1/java' Cheers, Chris. --- End Message --- --- Begin Message --- Version: 2.4.1-5.2+rm Dear submitter, as the package cvc3 has just been removed from the Debian archive unstable we hereby close the associated bug reports. We are sorry that we couldn't deal with your issue properly. For details on the removal, please see https://bugs.debian.org/945319 The version of this package that was in Debian prior to this removal can still be found using http://snapshot.debian.org/. Please note that the changes have been done on the master archive and will not propagate to any mirrors until the next dinstall run at the earliest. This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org. Debian distribution maintenance software pp. Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---
Bug#945390: androguard: autopkgtest failures
Source: androguard Version: 3.3.5-1 Severity: serious Justification: makes the package in question unusable or mostly so Dear Maintainer, The autopkgtest for your package are failing, which prevent the testing migration of networkx. The logging shows many exceptions like this: AttributeError: 'DiGraph' object has no attribute 'node' See: https://ci.debian.net/data/autopkgtest/testing/amd64/a/androguard/3495118/log.gz Kind Regards, Bas
Bug#945389: skimage: FTBFS with python3.8 (test failures)
Source: skimage Version: 0.14.2-3 Severity: serious Justification: makes the package in question unusable or mostly so Dear Maintainer, Your package FTBFS as part of the python3.8 transition, see: https://buildd.debian.org/status/fetch.php?pkg=skimage=amd64=0.14.2-3%2Bb1=1574494998=0 https://buildd.debian.org/status/package.php?p=skimage Kind Regards, Bas
Bug#945386: open-font-design-toolkit: Python2 removal in sid/bullseye
Source: open-font-design-toolkit Version: 1.7 Severity: serious Tags: sid bullseye User: ubuntu-de...@lists.ubuntu.com Usertags: origin-ubuntu focal Dear maintainers, The open-font-design-toolkit package is now uninstallable in unstable because it depends on python-fontforge, a python2 module which has been removed from the latest version of fontforge and is now only available in unstable as an uninstallable cruft package: $ sudo apt install open-font-design-toolkit Reading package lists... Done Building dependency tree Reading state information... Done Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: open-font-design-toolkit : Depends: python-fontforge but it is not going to be installed Depends: xgridfit but it is not going to be installed E: Unable to correct problems, you have held broken packages. $ I don't know why this package was overlooked in the general mass bug filing for python2 removals, but your package is currently unreleasable due to this bug. -- Steve Langasek Give me a lever long enough and a Free OS Debian Developer to set it on, and I can move the world. Ubuntu Developer https://www.debian.org/ slanga...@ubuntu.com vor...@debian.org signature.asc Description: PGP signature
Bug#945384: visp: autopkgtest regression
Source: visp Version: 3.2.0-1 Severity: serious User: ubuntu-de...@lists.ubuntu.com Usertags: origin-ubuntu focal Dear maintainers, The autopkgtests for visp 3.2.0-1 have regressed vs prior versions of this package, which means it will not migrate to testing. The test failure happens to be different in Debian vs. Ubuntu. In Debian it appears to be failing due to uninstallability. This uninstallability doesn't affect Ubuntu (libvisp-detection-dev is installable in Ubuntu), but once past this failure the test fails due to what looks like a missing dependency of the -dev package: autopkgtest [00:17:15]: test build: [--- g++: error: /usr/lib/x86_64-linux-gnu/libOpenGL.so: No such file or directory g++: error: /usr/lib/x86_64-linux-gnu/libGLX.so: No such file or directory g++: error: /usr/lib/x86_64-linux-gnu/libGLU.so: No such file or directory g++: error: /usr/lib/x86_64-linux-gnu/libCoin.so: No such file or directory g++: error: /usr/lib/x86_64-linux-gnu/libXi.so: No such file or directory autopkgtest [00:17:16]: test build: ---] [...] (http://autopkgtest.ubuntu.com/packages/v/visp/focal/amd64) Looking at the autopkgtest in question, it appears that pkg-config for visp is emitting libraries in its Libs: field that are provided by packages which it does not depend on. So this points to an actual bug in visp that needs fixing. -- Steve Langasek Give me a lever long enough and a Free OS Debian Developer to set it on, and I can move the world. Ubuntu Developer https://www.debian.org/ slanga...@ubuntu.com vor...@debian.org signature.asc Description: PGP signature
Bug#943609: marked as done (breezy ftbfs with python 3.8)
Your message dated Sun, 24 Nov 2019 03:19:29 + with message-id and subject line Bug#943609: fixed in breezy 3.0.2-1 has caused the Debian Bug report #943609, regarding breezy ftbfs with python 3.8 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 943609: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=943609 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:breezy Version: 3.0.1-6 Severity: important Tags: sid bullseye User: debian-pyt...@lists.debian.org Usertags: python3.8 breezy fails when trying to build for python 3.8: breezy/_simple_set_pyx.c:318:11: error: too many arguments to function ‘PyCode_New’ 318 | PyCode_New(a, 0, k, l, s, f, code, c, n, v, fv, cell, fn, name, fline, lnos) | ^~ breezy/_simple_set_pyx.c:8604:15: note: in expansion of macro ‘__Pyx_PyCode_New’ 8604 | py_code = __Pyx_PyCode_New( | ^~~~ In file included from /usr/include/python3.8/compile.h:5, from /usr/include/python3.8/Python.h:138, from breezy/_simple_set_pyx.c:4: /usr/include/python3.8/code.h:122:28: note: declared here 122 | PyAPI_FUNC(PyCodeObject *) PyCode_New( |^~ Cannot build extension "breezy._simple_set_pyx". Use "build_ext --allow-python-fallback" to use slower python implementations instead. error: command 'x86_64-linux-gnu-gcc' failed with exit status 1 --- End Message --- --- Begin Message --- Source: breezy Source-Version: 3.0.2-1 We believe that the bug you reported is fixed in the latest version of breezy, 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 943...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Jelmer Vernooij (supplier of updated breezy package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sun, 24 Nov 2019 02:09:25 + Source: breezy Architecture: source Version: 3.0.2-1 Distribution: unstable Urgency: medium Maintainer: Debian Breezy Maintainers Changed-By: Jelmer Vernooij Closes: 941532 943609 943908 944379 Changes: breezy (3.0.2-1) unstable; urgency=medium . * Fix bash completion script. Closes: #941532 * Set Rules-Requires-Root. * Update standards version to 4.4.1, no changes needed. * Re-export upstream signing key without extra signatures. * New upstream release. + Adds support for Python 3.8. Closes: #943609 + Fixes handling of missing .config/breezy directory. Closes: #943908, #944379 Checksums-Sha1: 249449f59719fc089a197b9412ee3d101338faad 2661 breezy_3.0.2-1.dsc 2b4447587549b6c7e90fd83aaabb5e35342b2c12 15271219 breezy_3.0.2.orig.tar.gz 37dde193571d0e1746c39ba27abf16c68676bbf1 56988 breezy_3.0.2-1.debian.tar.xz 4dd3420e78508ba640450368b0995ef3f4b0574c 9844 breezy_3.0.2-1_source.buildinfo Checksums-Sha256: be7954b5d9635153746970a26498a2657e3257d1cacd4f9de84d543f5dbef61f 2661 breezy_3.0.2-1.dsc 50f16bc7faf299f98fe58573da55b0664078f94b1a0e7f0ce9e1e6a0d47e68e0 15271219 breezy_3.0.2.orig.tar.gz eaac68574675f006fbcae285d3f0deb01683b2706a2563b40ecfe8e947b8facc 56988 breezy_3.0.2-1.debian.tar.xz 9cb903373e85278f2281964073993ff1ad5289b044143abf9020db8f19a375de 9844 breezy_3.0.2-1_source.buildinfo Files: 00d4da2c15d147be339059cbf3f9747b 2661 vcs optional breezy_3.0.2-1.dsc 4240d00872ffca6f064db0294bfc76db 15271219 vcs optional breezy_3.0.2.orig.tar.gz 3b4c46a56e1e33039cc6de85756d3a6a 56988 vcs optional breezy_3.0.2-1.debian.tar.xz d81bf9cace4dbeb21368e9a1a7b6596d 9844 vcs optional breezy_3.0.2-1_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEsjhixBXWVlpOhsvXV5wWDUyeI+gFAl3Z8WoACgkQV5wWDUye I+jsWxAApNiphfir7O83v0FCfqTUF/sdXvizCeGuhV/XcMrKpIjJI6deDUloOTdC 6sni+spoyainZevg3JXYVmuxvPFt6+j493oOHiofHd2pQRewmp0R6nzCz2nFcgWt 6OrsMFa8unIc154lL4WzvdCgByBkEIB0HUFLGFp/4RLDbWQ1dDgnKcsGDwMGVJ9B 7FSOPgZh2bBWGFvsatgX8JLhm/5s+roAq+8CeDmxZ+LIFTza6hN8IwkKEWZSRppg u1vFX0KjBl3jeLeE137U184MpomICWBeB06xwQtV+yyN4dvLVGEDZVFWLna5AgHA FsIXHKhwJeeCL7Afy8Hm2xtFYLgodYM2D4DYgZMuIf2Xo62vq2SyPuxRbIGFuf/V UcoMRXjhkGMS+cAdGKCVLO9umVhV/fwUnJmlYywj8GeG7bFw+Tw+BaiXGk5AecFv
Bug#945345: therion: Missing build-dep on python; build-depend on python3 instead
On Fri, Nov 22, 2019 at 11:30:00PM -0800, Steve Langasek wrote: > Rather than adding a build-dependency on python, which is deprecated, I have > attached a patch which moves the invocation to python3 instead and added a > build-dependency on python3. I do wish upstream would pick a scripting language. There are scripts in python, perl and tcl. Feel free to NMU your fix. Cheers, Olly
Bug#943705:
Bug#943533: marked as done (ldh-gui-suite: fails to install: mv: cannot move '/tmp/debconf_SxQLyd2wY8' to '/var/lib/one.liberty/deckhost.conf': No such file or directory)
Your message dated Sun, 24 Nov 2019 01:34:28 + with message-id and subject line Bug#943533: fixed in ldh-gui-suite 0.1~20190927-4 has caused the Debian Bug report #943533, regarding ldh-gui-suite: fails to install: mv: cannot move '/tmp/debconf_SxQLyd2wY8' to '/var/lib/one.liberty/deckhost.conf': No such file or directory to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 943533: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=943533 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: ldh-gui-suite Version: 0.1~20190927-3 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package failed to install. As per definition of the release team this makes the package too buggy for a release, thus the severity. >From the attached log (scroll to the bottom...): Setting up ldh-gui-suite (0.1~20190927-3) ... mv: cannot move '/tmp/debconf_SxQLyd2wY8' to '/var/lib/one.liberty/deckhost.conf': No such file or directory dpkg: error processing package ldh-gui-suite (--configure): installed ldh-gui-suite package post-installation script subprocess returned error exit status 1 Processing triggers for systemd (242-7) ... Processing triggers for libc-bin (2.29-2) ... Processing triggers for dictionaries-common (1.28.1) ... Processing triggers for libgdk-pixbuf2.0-0:amd64 (2.40.0+dfsg-1) ... Errors were encountered while processing: ldh-gui-suite You probably need to ship /var/lib/one.liberty as an empty directory in the package. cheers, Andreas ldh-gui-suite_0.1~20190927-3.log.gz Description: application/gzip --- End Message --- --- Begin Message --- Source: ldh-gui-suite Source-Version: 0.1~20190927-4 We believe that the bug you reported is fixed in the latest version of ldh-gui-suite, 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 943...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Jonas Smedegaard (supplier of updated ldh-gui-suite package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Mon, 18 Nov 2019 23:00:39 +0100 Source: ldh-gui-suite Architecture: source Version: 0.1~20190927-4 Distribution: unstable Urgency: medium Maintainer: Jonas Smedegaard Changed-By: Jonas Smedegaard Closes: 942657 942703 943533 943568 Changes: ldh-gui-suite (0.1~20190927-4) unstable; urgency=medium . * Fix ship empty directory /var/lib/one.liberty; closes: Bug#943533; thanks to Andreas Beckmann. * Add german (de), french (fr), and portuguese (pt) translations; closes: Bug#943568, #942703, #942657; thanks to Helge Kreutzmann, Jean-Philippe MENGUAL, and Américo Monteiro. * Update strings, fuzzying fr and pt translations. Checksums-Sha1: 96ddfdfafc2137d6387f6ea0cc62949f7cf9d2a7 1987 ldh-gui-suite_0.1~20190927-4.dsc 9e1f2d32b620c1e75096e85ddc57bd8022bfc794 21924 ldh-gui-suite_0.1~20190927-4.debian.tar.xz f4140d72679101877d678921c97b545be18fe6ad 7081 ldh-gui-suite_0.1~20190927-4_amd64.buildinfo Checksums-Sha256: fdc1aee66410d4f88b8447648d2fa3261f5a5e767d2a298946461a79c63fad67 1987 ldh-gui-suite_0.1~20190927-4.dsc 9958c7ec1390c2e4a125151536df498d3452523934b658d03641ce7d26805e39 21924 ldh-gui-suite_0.1~20190927-4.debian.tar.xz 29cf911f681f847b447618f68dfc9c5cdb11a8daf9297f6336775728d75914d4 7081 ldh-gui-suite_0.1~20190927-4_amd64.buildinfo Files: 1ae89358465737303b7ecabbe0c60c53 1987 utils optional ldh-gui-suite_0.1~20190927-4.dsc 0907d151549527077d1c7e59a093788e 21924 utils optional ldh-gui-suite_0.1~20190927-4.debian.tar.xz b995095e6a78fa737f6ebc8091b82192 7081 utils optional ldh-gui-suite_0.1~20190927-4_amd64.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEn+Ppw2aRpp/1PMaELHwxRsGgASEFAl3TFhsACgkQLHwxRsGg ASFeAw//Ywy8G25za2ruUM39wLY5R9HPGiddurW5EPMgzgT8C5E6diRrRrz0T11u /Q+W2L6FVdSIqytPUvxx+AZZIcdUrBoHeW2iuqCxDf7o8kj6vRTZxyFkOY/rSrBM I5Siq7bJM9k3bEBKvwMIJGbRVYqouCdZu5bmK8RKx3AyLFvZIkpKJvuum7gbO3j2 y768JduQpRWFQs+YhEwcGBiPWeMhjpEcNxgi0JBtie1CZtnShabFOfxUFk9y71pL 5OAQQbX6Bg4J7Gxg9saKiumeMuGyaBtKq/nCO1Q09ticcl9UaB5fyFYpEg2UvF/X
Bug#936745: re: ipywidgets: Python2 removal in sid/bullseye
On Tue, 19 Nov 2019 06:59:36 + peter green wrote: > unblock 936745 by 936995 > severity 936745 serious > thanks > > matplotlib2 no longer has any dependencies or build-dependencies on packages built from the ipywidgets source. > > According to https://ftp-master.debian.org/users/dktrkranz/NBS ipywidgets has dependencies or build-depdencies on several packages that are no longer built by their corresponding source packages. > > ipywidgets build-depends on python-coverage. > python-widgetsnbextension depends on python-notebook > > It seems like it is time to drop python2 support from this package. Sagemath still build-depends on it, but it's already not in testing for many reasons, so I agree it makes sense to go ahead with the removal. Scott K signature.asc Description: This is a digitally signed message part.
Bug#945348: python3-joblib: Missing new dependency python3-pkg-resources
On Sat, 23 Nov 2019, Andreas Tille wrote: > Package: python3-joblib > Version: 0.14.0-0.2 > Severity: critical > Tags: patch > Justification: breaks unrelated software > Hi, > as per latest debci log of spades[1] joblib needs python3--pkg-resources. > I will add this to the dependencies but I will also take over joblib > packaging to Debian Science team to make the package watched by a > greater audience. I've got confirmation from Yaroslav for similar > cases in the past so I assume its OK. Yes, thank you Andreas! If you could also keep it at debcompat 10, all backport gods would favor you ;) -- Yaroslav O. Halchenko Center for Open Neuroscience http://centerforopenneuroscience.org Dartmouth College, 419 Moore Hall, Hinman Box 6207, Hanover, NH 03755 Phone: +1 (603) 646-9834 Fax: +1 (603) 646-1419 WWW: http://www.linkedin.com/in/yarik
Bug#945196: marked as done (mes: ships /usr/lib//{crt1.o,libc.a})
Your message dated Sun, 24 Nov 2019 00:34:48 +
with message-id
and subject line Bug#945196: fixed in mes 0.20-3
has caused the Debian Bug report #945196,
regarding mes: ships /usr/lib//{crt1.o,libc.a}
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.)
--
945196: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=945196
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: mes
Version: 0.20-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Hi,
during a test with piuparts I noticed your package fails to upgrade from
'sid' to 'experimental'.
It installed fine in 'sid', then the upgrade to 'experimental' fails
because it tries to overwrite other packages files.
>From the attached log (scroll to the bottom...):
Preparing to unpack .../archives/mes_0.20-1_amd64.deb ...
Unpacking mes (0.20-1) ...
dpkg: error processing archive /var/cache/apt/archives/mes_0.20-1_amd64.deb
(--unpack):
trying to overwrite '/usr/lib/x86_64-linux-gnu/crt1.o', which is also in
package libc6-dev:amd64 2.29-3
dpkg-deb: error: paste subprocess was killed by signal (Broken pipe)
Errors were encountered while processing:
/var/cache/apt/archives/mes_0.20-1_amd64.deb
The following files should most likely *not* be shipped by this package:
usr/lib/x86_64-linux-gnu/crt1.o
usr/lib/x86_64-linux-gnu/libc.a
cheers,
Andreas
libc6-dev=2.29-3_mes=0.20-1.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: mes
Source-Version: 0.20-3
We believe that the bug you reported is fixed in the latest version of
mes, 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 945...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Vagrant Cascadian (supplier of updated mes 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, 23 Nov 2019 15:55:05 -0800
Source: mes
Architecture: source
Version: 0.20-3
Distribution: unstable
Urgency: medium
Maintainer: Vagrant Cascadian
Changed-By: Vagrant Cascadian
Closes: 945196
Changes:
mes (0.20-3) unstable; urgency=medium
.
* debian/rules: Call configure with --libdir argument that puts mes
libraries into a "mes" subdir (Closes: #945196). Thanks to Andreas
Beckmann for the report.
Checksums-Sha1:
9372efb8bcb967ae4ff67e50215d6c766e6da453 1530 mes_0.20-3.dsc
431963590251c4816911a565e48319692c95bb7c 10012 mes_0.20-3.debian.tar.xz
4646f92d07e3d8c561853a9143b73aece671f1b2 7976 mes_0.20-3_amd64.buildinfo
Checksums-Sha256:
153cd06f6afa88a9cfcc666c160dbbf2a45796ed7ecb6dd64feefdb121ab1e1e 1530
mes_0.20-3.dsc
4163857d96030cfa5114e3516f831e9319dcabc87340812a8356d618f6b77b57 10012
mes_0.20-3.debian.tar.xz
e353a61f1b73bcdc7765d55a59aed7650bbe0a8669de7ded5318498924f2bfcc 7976
mes_0.20-3_amd64.buildinfo
Files:
3e519b48b854f45886b330136f42c9a7 1530 devel optional mes_0.20-3.dsc
16d72638a1ce00c4354dc23179cd0d66 10012 devel optional mes_0.20-3.debian.tar.xz
6b328bf954e7a6b78261685ecd9c96fb 7976 devel optional mes_0.20-3_amd64.buildinfo
-BEGIN PGP SIGNATURE-
iIkEARYKADEWIQRlgHNhO/zFx+LkXUXcUY/If5cWqgUCXdnNmhMcdmFncmFudEBk
ZWJpYW4ub3JnAAoJENxRj8h/lxaqh1IBAMgomgaRQt9m/TcI65IqsxxJyIfsOIE/
kLrEXO04rJb9AP9ReMvu3AsPrvmHhLkhrHRNYNYs/vXxX1TAX0kMKnYdAA==
=N2K0
-END PGP SIGNATURE End Message ---
Bug#945381: python3-bcolz: missing Breaks+Replaces: python-bcolz
Package: python3-bcolz Version: 1.2.1+ds2-4 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package fails to upgrade from 'testing'. It installed fine in 'testing', then the upgrade to 'sid' fails because it tries to overwrite other packages files without declaring a Breaks+Replaces relation. See policy 7.6 at https://www.debian.org/doc/debian-policy/ch-relationships.html#overwriting-files-and-replacing-packages-replaces >From the attached log (scroll to the bottom...): Preparing to unpack .../python3-bcolz_1.2.1+ds2-4_amd64.deb ... Unpacking python3-bcolz (1.2.1+ds2-4) ... dpkg: error processing archive /var/cache/apt/archives/python3-bcolz_1.2.1+ds2-4_amd64.deb (--unpack): trying to overwrite '/usr/share/doc/python3-bcolz/tutorials/tutorial_carray.ipynb', which is also in package python-bcolz 1.2.1+ds2-2+b1 Errors were encountered while processing: /var/cache/apt/archives/python3-bcolz_1.2.1+ds2-4_amd64.deb cheers, Andreas python-bcolz=1.2.1+ds2-2+b1_python3-bcolz=1.2.1+ds2-4.log.gz Description: application/gzip
Bug#765854: Umount ecryptfs on logout
Hi All, Is anything happening with this? Will it be a problem anywhere if the session is removed from common-session-noninteractive like Michael suggested? Or another way I was testing today is to get the name of the parent process from mount.ecryptfs_private.c and skip incrementing the counter if the parent process is 'systemd'. -- Regards Sudip
Bug#943571: marked as done (sa-exim: Does not work with exim 4.93)
Your message dated Sat, 23 Nov 2019 23:20:58 + with message-id and subject line Bug#943571: fixed in sa-exim 4.2.1-18 has caused the Debian Bug report #943571, regarding sa-exim: Does not work with exim 4.93 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.) -- 943571: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=943571 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: sa-exim Version: 4.2.1-17 Severity: normal I am moving this from direct maintainer-contact to the BTS. https://alioth-lists.debian.net/pipermail/pkg-exim4-maintainers/2019-October/016333.html https://alioth-lists.debian.net/pipermail/pkg-exim4-maintainers/2019-October/016341.html #1 sa-exim 4.2.1-17 (binary) does not work with exim 4.93 since some exported functions have been replaced by #defines. Once the sources are compatible a rebuild will be necessary. #2 If sa-exim is changed to pass -DLOCAL_SCAN and exim bug https://bugs.exim.org/show_bug.cgi?id=2458 is patched then sa-exim compiles. #3 Updating the local_can patch in GIT https://salsa.debian.org/exim-team/exim4/blob/experimental/debian/patches/90_localscan_dlopen.dpatch with #pragma GCC visibility push(default)/#pragma GCC visibility pop in src/string.c at about lines 412/464 gets rid of "undefined symbol:" 451 error in SMTP dialogue. However we get a SIG 11: 2019-10-26 18:39:05 1iOP5l-000768-O8 local_scan() library doesn't contain local_scan_version_major() function - message temporarily rejected 2019-10-26 18:39:05 1iOP5l-000768-O8 local_scan() function crashed with signal 11 - message temporarily rejected (size 265) It is unlikely that I will invest further time/effort in this issue. cu Andreas --- End Message --- --- Begin Message --- Source: sa-exim Source-Version: 4.2.1-18 We believe that the bug you reported is fixed in the latest version of sa-exim, 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 943...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Magnus Holmgren (supplier of updated sa-exim package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Sat, 23 Nov 2019 22:40:24 +0100 Source: sa-exim Architecture: source Version: 4.2.1-18 Distribution: unstable Urgency: medium Maintainer: Magnus Holmgren Changed-By: Magnus Holmgren Closes: 943571 Changes: sa-exim (4.2.1-18) unstable; urgency=medium . * Build with -DLOCAL_SCAN. * sprintf_no_format_string.patch: With exim 4.93, string_sprintf() requires at least two arguments (Closes: #943571). Thanks to Andreas Metzler. Checksums-Sha1: 93fb2f6d35efdbc14795a4e11c675e120ea20c21 1820 sa-exim_4.2.1-18.dsc ccae0e7cc4f75cc476b3e05637daa87a2ba4a4f7 27784 sa-exim_4.2.1-18.debian.tar.xz b447e885ed32d3ef7e066247215cba871c7728ae 5759 sa-exim_4.2.1-18_source.buildinfo Checksums-Sha256: b1700e872c19a000b02a41117e0da9ac8e455e2d0f4f47576d0288ec53b1 1820 sa-exim_4.2.1-18.dsc dcc568dd530ec25b4fdd6b778181a096e554f54b00d38ebc1aba15eb6f1e77a7 27784 sa-exim_4.2.1-18.debian.tar.xz 957ad2e1bcb1894b61aad1d82f60d1859a6e94a010f81036ee0d5ea937c5f2f6 5759 sa-exim_4.2.1-18_source.buildinfo Files: 64666a75415185d447cc0c6ce59dc6b7 1820 mail optional sa-exim_4.2.1-18.dsc e6da6700c0b1472cb7b08eee72188671 27784 mail optional sa-exim_4.2.1-18.debian.tar.xz c47f6ce39b32b3dae8214a4ea354bf61 5759 mail optional sa-exim_4.2.1-18_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEEzSoHOzhhVBcKQILo1PIZv+yZhIkFAl3ZuOMACgkQ1PIZv+yZ hImNxhAArMeioDNSIOZr+kMcmi211x1HHZTZCq8OubixZVcMacXEDUrLY/daiknV uTvvlTAEPbqK8i07lbJ7wmiEKG4ZRsa6NnCnPXYEWlCiiHdWrfPNymAuy6SK58/A CttMdG2ucXmUaJIUD1ppAP4GL3a8JuIGeCzLHP3DrFREmboflE4vqnB3tOeXwSEK YG1+uqtFIvvxje6lxovJ/uACIuzqsjXK4rklc0KQiy2IYgFY5kxpNH3xoVF1yYx3 5GCd5mWdr53DoICqdg4LcSUr7bUWBd3LlXyuljs8Nj+9mOdHDrKlAA0r5pxY6+/U 3Psr3hGY813WopftGHvis6IOFUl2MGRaGI7U21inAgc899n3JFbKrfeqaa2xtFos ie5k7+JwL9bFvlqdenSvI4de64Ak2MvrCa4pMJRbF2hGxukze+p/VIwAnaiuogQO nXRjrxGU+/J0v9RyI285xnC07rew0NS09FZaPcC5YKMEWl7RH7yD4XUfP3gmnUYy 0CllZNn/TYGsKh7ou4m0X1BDY5ztln4tMKK1y6PNUSp4zhMHTy5ZFXL/ULIshxaM ic8KDwL/7AUREaUTo6+VO/rOmVBrsGjgCGZkc3Q5vHbDIR+JbLDI1DlwbhhI3m0A
Bug#944911: marked as done (libfiu: FBTFS: Found too many matching python3 bindings)
Your message dated Sat, 23 Nov 2019 22:35:11 + with message-id and subject line Bug#944911: fixed in libfiu 1.00-4 has caused the Debian Bug report #944911, regarding libfiu: FBTFS: Found too many matching python3 bindings 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.) -- 944911: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=944911 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: libfiu Version: 1.00-3+b1 Severity: serious Tags: ftbfs Justification: fails to build from source (but built successfully in the past) libfiu fails to build from source: | ./wrap-python 3 ./test-manyfps.py | Found too many matching python3 bindingsmake[3]: *** [Makefile:96: py-run-test-manyfps] Error 1 | make[3]: *** Waiting for unfinished jobs | make[4]: Leaving directory '/<>/tests/utils' | parallel nc: 6372609 c: 8276708 e: 509422t: 15158739 | wildcard nc: 577000c: 599000e: 1566 t: 1177566 | rm test-enable_stack test-parallel-wildcard test-parallel test-ferror test-enable_stack_by_name | make[3]: Leaving directory '/<>/tests' | make[2]: *** [Makefile:58: test] Error 2 | make[2]: Leaving directory '/<>' | dh_auto_test: make -j4 test V=1 LC_ALL=C returned exit code 2 | make[1]: *** [debian/rules:28: override_dh_auto_test] Error 255 | make[1]: Leaving directory '/<>' | make: *** [debian/rules:12: build-arch] Error 2 | dpkg-buildpackage: error: debian/rules build-arch subprocess returned exit status 2 The full build log can be found there: https://buildd.debian.org/fetch.php?pkg=libfiu=amd64=1.00-3%2Bb1=1573820091=0 --- End Message --- --- Begin Message --- Source: libfiu Source-Version: 1.00-4 We believe that the bug you reported is fixed in the latest version of libfiu, 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 944...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Chris Lamb (supplier of updated libfiu package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Sat, 23 Nov 2019 17:26:03 -0500 Source: libfiu Architecture: source Version: 1.00-4 Distribution: unstable Urgency: medium Maintainer: Chris Lamb Changed-By: Chris Lamb Closes: 944911 Changes: libfiu (1.00-4) unstable; urgency=medium . * Don't FTBFS when multiple Python version libraries exist in build tree by manually deleting all but the version for the default Python version returned by py3versions prior to running the test suite. (Closes: #944911) * Specify Rules-Requires-Root: no. * Bump Standards-Version to 4.4.1. Checksums-Sha1: e7c252adfb12b1f5b00ec6477ca445f208766ba5 2082 libfiu_1.00-4.dsc a65c7bd6db114ade0e809dffafc30d3aa1d526be 7172 libfiu_1.00-4.debian.tar.xz 08bccabd63abb961729af2d0b0e4c623fbb1a61c 7910 libfiu_1.00-4_amd64.buildinfo Checksums-Sha256: 440b4e80c72befe5ea9c4a67f2b05f9f0bd0acff9e6d7ec84efce385ed15059c 2082 libfiu_1.00-4.dsc facae45e4808efe08f8fb700cc99c23b6b7b2e8f223463b17ec947a57f41c61e 7172 libfiu_1.00-4.debian.tar.xz 742429e39ca01968a9e8da91a56239b47a0052c4b15db45f7228f25838a27c45 7910 libfiu_1.00-4_amd64.buildinfo Files: 5f79fefb5d62b341520b4e48b7138cd8 2082 libs optional libfiu_1.00-4.dsc 01d49238dc9f8f47dd096d33065ad5b0 7172 libs optional libfiu_1.00-4.debian.tar.xz eca911d88e6b3f43fd494b65be46428e 7910 libs optional libfiu_1.00-4_amd64.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEEwv5L0nHBObhsUz5GHpU+J9QxHlgFAl3ZsrYACgkQHpU+J9Qx HljvTQ//VXafWBoxO0FPCP5eH3d8cbkyjnCJ1yIE6gclBN4S6J6PD6+Tzp4WvuzS ZxzhTRfOcW1Ut7IyoJAug/5qtXOdwvnGmwlN+J+DlZ1YBJdcA7ZDGUMpmkWXEFsq U90NTyy7839GtANPdNMjR+Ua5cOlDuF9rkmN2JMutP9Qc83HWUUHdyEBVtTRLdVg WogewM1x/BmWyatehbpI+ASfhIoXAv4bK3TKvBiogKvFownHrYN8gRpijYTRFEYU WcdDU2pLKsYDgY9V48/0XAVMwdGs4t8oKViHqSd+HUzm4B+yA9zFgae1N1Ne7o7V /WIQdPBWgBilyfa1g1kmQaKLpRdsrDH20X3DrBh0ezrzp5HtW3GT/njUvKqcZfgd CJhHidFJj8Ftl1GQk6tSSY7lrMXtQ4HlgTxakjeXJrm27igC+RA4584HWfc8mffJ jUjhU/dp413bZtelRxCDD6xJcjMMlwQjpAsKtSJWfAsUFvnmqX9NavxI0HOuB6V8 ZOSzDNDc9/dax22v2130iZ7sT2Yn3xuePxv9JOantEmlzi/4tBNh/QpsyiVRbDju JivkBDlfbBgm0rApbMXrLsljuw+wz9ygqzft80QWBimOZqYwK8JTcAXG9N0BDzgR zsT/TViZKeMAt+OXM+nAtkhVrAJL+V8br81jinZ2s4gA31zw9Ts= =CDfI -END PGP
Processed: fixed 928420 in 3.4.4-1
Processing commands for cont...@bugs.debian.org:
> # the 3.4.3-4.1 changelog got lost in the 3.4.4-1 upload
> fixed 928420 3.4.4-1
Bug #928420 {Done: Dominik George } [src:php-imagick]
php-imagick: CVE-2019-11037
Marked as fixed in versions php-imagick/3.4.4-1.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
928420: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=928420
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Processed: unarchiving 928420
Processing commands for cont...@bugs.debian.org:
> unarchive 928420
Bug #928420 {Done: Dominik George } [src:php-imagick]
php-imagick: CVE-2019-11037
Unarchived Bug 928420
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
928420: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=928420
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#943574: marked as done (pyhoca-gui: Please don't depend on python-notify)
Your message dated Sat, 23 Nov 2019 21:19:34 + with message-id and subject line Bug#943574: fixed in pyhoca-gui 0.5.1.0-1 has caused the Debian Bug report #943574, regarding pyhoca-gui: Please don't depend on python-notify 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.) -- 943574: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=943574 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: pyhoca-gui Version: 0.5.0.8-1 Severity: serious User: pkg-gnome-maintain...@lists.alioth.debian.org Usertags: oldlibs pygtk Tags: sid bullseye As part of the Python2 removal, the Debian GNOME team is working to remove pygtk from Debian. One of the blockers is python-notify. Please drop pyhoca-gui's dependency on python-notify so that we can remove python-notify from Debian. In my quick look at the source code, it looks like the dependency on python-notify is obsolete since you already depend on gir1.2-notify-0.7 . https://sources.debian.org/src/pyhoca-gui/0.5.0.8-1/pyhoca/wxgui/notify.py/#L25-L32 If you have any questions don't hesitate to ask. On behalf of the Debian GNOME team, Jeremy Bicha --- End Message --- --- Begin Message --- Source: pyhoca-gui Source-Version: 0.5.1.0-1 We believe that the bug you reported is fixed in the latest version of pyhoca-gui, 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 943...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Mike Gabriel (supplier of updated pyhoca-gui package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Sat, 23 Nov 2019 21:59:53 +0100 Source: pyhoca-gui Architecture: source Version: 0.5.1.0-1 Distribution: unstable Urgency: medium Maintainer: Debian Remote Maintainers Changed-By: Mike Gabriel Closes: 943574 Changes: pyhoca-gui (0.5.1.0-1) unstable; urgency=medium . * New upstream release. * debian/control: + Add Rules-Requires-Root: field and set it to no. + Bump Standards-Version: to 4.4.1. No changes needed. + debian/control: Drop from D (pyhoca-gui): python-notify. (Closes: #943574). * debian/patches: + Drop 0001_po-Update-Bokmail-Norwegian-translation-file.-Thanks.patch. Applied upstream. Checksums-Sha1: 74b8f06390e7b082d08add0ba88c419b29c11baa 2358 pyhoca-gui_0.5.1.0-1.dsc f83ff8bc6bf767d234ed3d600c7387605a496b3d 2098593 pyhoca-gui_0.5.1.0.orig.tar.gz dabcde31db1d5160399a2d55f3af3a55a15930e2 488 pyhoca-gui_0.5.1.0.orig.tar.gz.asc 12f312e2b6d7e8baa4d57fc56550706b483a31a3 25212 pyhoca-gui_0.5.1.0-1.debian.tar.xz 9abc085f7967f90f64abf5b53f35ceb492ae1778 9390 pyhoca-gui_0.5.1.0-1_source.buildinfo Checksums-Sha256: 0bd4d725d27563efe1106fe97faba61af0fd7745a2a511f571d22507e49a3b97 2358 pyhoca-gui_0.5.1.0-1.dsc 152128f38a591c389110413642adf3d3b281d71ca52d3a7973110fc15cdbc4ea 2098593 pyhoca-gui_0.5.1.0.orig.tar.gz 4c952f1846a72d21b7c376cfc5ddacc16fde5712de65db6184406d3b6d206ea4 488 pyhoca-gui_0.5.1.0.orig.tar.gz.asc 9173030b315a723959a21257d7fefe17f77162da9cb4a9af8874ff5cffeda9c1 25212 pyhoca-gui_0.5.1.0-1.debian.tar.xz 15996de8692ecd652569572695b4c9fde0a4139ad7acf74e8bd5cab2d96d92c6 9390 pyhoca-gui_0.5.1.0-1_source.buildinfo Files: c26c559772d7587d2ce8f97f8eea188a 2358 x11 optional pyhoca-gui_0.5.1.0-1.dsc 5e37fd45a872ebac86ae18ddca8b8a89 2098593 x11 optional pyhoca-gui_0.5.1.0.orig.tar.gz 102d45262b49d04853c3da7d7a87e8cd 488 x11 optional pyhoca-gui_0.5.1.0.orig.tar.gz.asc 03658a1aa80d81e6d854cc87b0635a96 25212 x11 optional pyhoca-gui_0.5.1.0-1.debian.tar.xz 06c043d6f786f2c0a1a68a4c386476c2 9390 x11 optional pyhoca-gui_0.5.1.0-1_source.buildinfo -BEGIN PGP SIGNATURE- iQJJBAEBCAAzFiEEm/uu6GwKpf+/IgeCmvRrMCV3GzEFAl3Znd8VHHN1bndlYXZl ckBkZWJpYW4ub3JnAAoJEJr0azAldxsxxhwP/RcFSX7M6yPJD0YtU4TQoogkk2HK zhUGiNIwrA+PhlEqM1iBAlJlLuKrhyS1qvaMSkWTcwVbxILYHikcZbArbT+r7YDV m17R3SLXjeaT6UEtuTCzBKKBfaRUv0I2rJqoo7+dvnXGREEP4s8qffJt9H8Kx8LY rY9SRqun3skFo/KiZq+aFl7qH4ytUhLXFAzO15F9Yh0TmU7zJ0oPZWiQNhhpaWrj M5yzEM801gEyNKR0bZJaiUZjTa91bMeozMlIUEUclIFslkaW8h9oT3LjAZ3Dvm0G XKIxlznN9GBQPl1vAM9mDoJ5DrUoPrveIw/cQ2/Ip+qXQnPVlk4TYuM2yCxE1ZJJ
Bug#943574: marked as pending in pyhoca-gui
Control: tag -1 pending Hello, Bug #943574 in pyhoca-gui 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/debian-remote-team/pyhoca-gui/commit/f386489f4b10682987aeeb932c16b0dbfe0e792e debian/control: Drop from D (pyhoca-gui): python-notify. (Closes: #943574). (this message was generated automatically) -- Greetings https://bugs.debian.org/943574
Processed: Bug#943574 marked as pending in pyhoca-gui
Processing control commands: > tag -1 pending Bug #943574 [src:pyhoca-gui] pyhoca-gui: Please don't depend on python-notify Added tag(s) pending. -- 943574: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=943574 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#945369: yard: CVE-2019-1020001
Source: yard Version: 0.9.16-1 Severity: grave Tags: security upstream Justification: user security hole Hi, The following vulnerability was published for yard. CVE-2019-1020001[0]: | yard before 0.9.20 allows path traversal. If you fix the vulnerability please also make sure to include the CVE (Common Vulnerabilities & Exposures) id in your changelog entry. For further information see: [0] https://security-tracker.debian.org/tracker/CVE-2019-1020001 https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-1020001 [1] https://github.com/lsegal/yard/security/advisories/GHSA-xfhh-rx56-rxcr Please adjust the affected versions in the BTS as needed. Regards, Salvatore -- System Information: Debian Release: bullseye/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 5.3.0-2-amd64 (SMP w/2 CPU cores) Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE=C.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled
Bug#944249: [Pkg-emacsen-addons] Bug#944249: gnuplot-mode does not work with emacs26
Hi Dima, On Sat, Nov 23, 2019 at 02:08:30AM -0800, Dima Kogan wrote: > Nicholas D Steeves writes: > > > Is that an official NACK for Augustin's patch for the autoloads? I > > included it in the patch series I just sent... > > Hi. I tried out Augustin's update to the autoloads, and it works for me > (thanks, Augustin!) Nicholas: you wanted to review and to improve > things. Are your patches somewhere we can see them? I've confirmed this bug has my patch series (with Augustin's work integrated). Maybe those emails are in your spam folder? You should be able to use bts to grab the mbox for importation vs git am. Cheers, Nicholas signature.asc Description: PGP signature
Bug#945341: marked as done (libcgal-dev: unhandled symlink to directory conversion: /usr/share/doc/PACKAGE)
Your message dated Sat, 23 Nov 2019 19:34:41 + with message-id and subject line Bug#945341: fixed in cgal 5.0-2 has caused the Debian Bug report #945341, regarding libcgal-dev: unhandled symlink to directory conversion: /usr/share/doc/PACKAGE to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 945341: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=945341 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: libcgal-dev Version: 5.0-1 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, an upgrade test with piuparts revealed that your package installs files over existing symlinks and possibly overwrites files owned by other packages. This usually means an old version of the package shipped a symlink but that was later replaced by a real (and non-empty) directory. This kind of overwriting another package's files cannot be detected by dpkg. This was observed on the following upgrade paths: sid -> experimental For /usr/share/doc/PACKAGE this may not be problematic as long as both packages are installed, ship byte-for-byte identical files and are upgraded in lockstep. But once one of the involved packages gets removed, the other one will lose its documentation files, too, including the copyright file, which is a violation of Policy 12.5: https://www.debian.org/doc/debian-policy/ch-docs.html#copyright-information For other overwritten locations anything interesting may happen. Note that dpkg intentionally does not replace directories with symlinks and vice versa, you need the maintainer scripts to do this. See in particular the end of point 4 in https://www.debian.org/doc/debian-policy/ch-maintainerscripts.html#details-of-unpack-phase-of-installation-or-upgrade It is recommended to use the dpkg-maintscript-helper commands 'dir_to_symlink' and 'symlink_to_dir' (available since dpkg 1.17.14) to perform the conversion, ideally using d/$PACKAGE.maintscript. See dpkg-maintscript-helper(1) and dh_installdeb(1) for details. >From the attached log (scroll to the bottom...): 0m24.9s ERROR: FAIL: silently overwrites files via directory symlinks: /usr/share/doc/libcgal-dev/NEWS.Debian.gz (libcgal-dev:amd64) != /usr/share/doc/libcgal13/NEWS.Debian.gz (libcgal13:amd64) /usr/share/doc/libcgal-dev -> libcgal13 /usr/share/doc/libcgal-dev/README.Debian (libcgal-dev:amd64) != /usr/share/doc/libcgal13/README.Debian (libcgal13:amd64) /usr/share/doc/libcgal-dev -> libcgal13 /usr/share/doc/libcgal-dev/changelog.Debian.gz (libcgal-dev:amd64) != /usr/share/doc/libcgal13/changelog.Debian.gz (libcgal13:amd64) /usr/share/doc/libcgal-dev -> libcgal13 /usr/share/doc/libcgal-dev/changelog.gz (libcgal-dev:amd64) != /usr/share/doc/libcgal13/changelog.gz (libcgal13:amd64) /usr/share/doc/libcgal-dev -> libcgal13 /usr/share/doc/libcgal-dev/copyright (libcgal-dev:amd64) != /usr/share/doc/libcgal13/copyright (libcgal13:amd64) /usr/share/doc/libcgal-dev -> libcgal13 cheers, Andreas libcgal-dev_5.0-1.log.gz Description: application/gzip --- End Message --- --- Begin Message --- Source: cgal Source-Version: 5.0-2 We believe that the bug you reported is fixed in the latest version of cgal, 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 945...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Joachim Reichel (supplier of updated cgal package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Sat, 23 Nov 2019 10:41:42 +0100 Source: cgal Binary: libcgal-demo libcgal-dev libcgal-ipelets libcgal-ipelets-dbgsym libcgal-qt5-dev Architecture: source Version: 5.0-2 Distribution: experimental Urgency: medium Maintainer: Joachim Reichel Changed-By: Joachim Reichel Description: libcgal-demo - C++ library for computational geometry (demos) libcgal-dev - C++ library for computational geometry (development files) libcgal-ipelets - C++ library for computational geometry (ipelets) libcgal-qt5-dev - C++ library for computational geometry (development files, suppor Closes: 945341 Changes: cgal (5.0-2) experimental; urgency=medium . * Add libcgal-dev.maintscript to convert
Bug#945316: polymake: FTBFS with perl 5.30
Control: affects 941933 + src:polymake Control: retitle -1 polymake: FTBFS with normaliz 3.8.1: segfaults during tests On 23/11/2019 10.45, Benjamin Lorenz wrote: > On 22/11/2019 22.06, Andreas Beckmann wrote: >> polymake FTBFS against perl 5.30: > This was already reported and should be fixed with > https://bugs.debian.org/941933 > but it seems that the builds need to be triggered again as the logs are > older than the normaliz 3.8.1+ds-1 upload. OK, tried my first self-served give-backs ... ... some architectures succeeed (arm64, s390x), some had tests failing with segmentation faults (amd64, i386, armhf, ppc64el), mips*el is still building. https://buildd.debian.org/status/package.php?p=polymake=unstable Andreas
Processed: Re: Bug#945316: polymake: FTBFS with perl 5.30
Processing control commands:
> affects 941933 + src:polymake
Bug #941933 {Done: Jerome Benoit } [libnormaliz-dev]
polymake: FTBFS: no more rules available to compute 'HILBERT_BASIS_GENERATORS'
Added indication that 941933 affects src:polymake
> retitle -1 polymake: FTBFS with normaliz 3.8.1: segfaults during tests
Bug #945316 [src:polymake] polymake: FTBFS with perl 5.30
Changed Bug title to 'polymake: FTBFS with normaliz 3.8.1: segfaults during
tests' from 'polymake: FTBFS with perl 5.30'.
--
941933: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=941933
945316: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=945316
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#945343: marked as done (sumo: FTBFS without Internet access)
Your message dated Sat, 23 Nov 2019 19:21:04 + with message-id and subject line Bug#945343: fixed in sumo 1.3.1-5 has caused the Debian Bug report #945343, regarding sumo: FTBFS without Internet access to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 945343: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=945343 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: sumo Version: 1.3.1-4 Severity: serious User: ubuntu-de...@lists.ubuntu.com Usertags: origin-ubuntu focal Hi Anton, The sumo package fails to build from source in Ubuntu because it cannot resolve an Internet hostname: [...] cd /<>/tests_auto; cp /<>/debian/tests/hokkaido/* ./; ../bin/sumo -b 0 -e 1 -n net.net.xml -r input_routes.rou.xml --summary-output sum.out Warning: Environment variable SUMO_HOME is not set, schema resolution will use slow website lookups. Error: unable to resolve host/address 'sumo.dlr.de' In file 'input_routes.rou.xml' At line/column 1/0. [...] (https://launchpad.net/ubuntu/+source/sumo/1.3.1-4/+build/17963765) Packages are by policy not allowed to depend on Internet access during build. This happens to not cause a build failure on any of the Debian autobuilders because they happen to allow Internet access, but it is still a violation of the policy for builds. -- Steve Langasek Give me a lever long enough and a Free OS Debian Developer to set it on, and I can move the world. Ubuntu Developer https://www.debian.org/ slanga...@ubuntu.com vor...@debian.org signature.asc Description: PGP signature --- End Message --- --- Begin Message --- Source: sumo Source-Version: 1.3.1-5 We believe that the bug you reported is fixed in the latest version of sumo, 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 945...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Anton Gladky (supplier of updated sumo 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, 23 Nov 2019 20:02:54 +0100 Source: sumo Architecture: source Version: 1.3.1-5 Distribution: unstable Urgency: medium Maintainer: Debian Science Maintainers Changed-By: Anton Gladky Closes: 945343 Changes: sumo (1.3.1-5) unstable; urgency=medium . * [12e5965] Set SUMO_HOME to escape network usage during build. (Closes: #945343) * [33f60f2] Let autopkgtests be built without network * [fd3c58c] Set Standards-Version to 4.4.1 * [89e5a7f] Set upstream metadata fields: Repository. Checksums-Sha1: 60c339c220c9ad67a8ebc996f827517c33cdb043 2206 sumo_1.3.1-5.dsc bb65aaadaf48f976768057199a5c78ea23b074dc 20096 sumo_1.3.1-5.debian.tar.xz 5f6c991f0a5c21586a9c76338822b31b34470661 14103 sumo_1.3.1-5_source.buildinfo Checksums-Sha256: 60a2482462b3e8a67478f0b3abfe6475e03ba4659c4da69e18fec13200f8f4fc 2206 sumo_1.3.1-5.dsc 144fb67bdac9fd444d028523e0c2deab9bbe4f84959484d542d16661ffd10538 20096 sumo_1.3.1-5.debian.tar.xz 89480c6ddfbe287f237ec476f99583eaca66fe1261088bcf94ca912df33809a2 14103 sumo_1.3.1-5_source.buildinfo Files: 5488ccf7fbc926b1beadceac9ef85788 2206 science optional sumo_1.3.1-5.dsc e93bfb0c4e538d5bfb14fbcafd600063 20096 science optional sumo_1.3.1-5.debian.tar.xz f55b5350d80a0e461c54c1a6ccda 14103 science optional sumo_1.3.1-5_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEu71F6oGKuG/2fnKF0+Fzg8+n/wYFAl3ZgqsACgkQ0+Fzg8+n /wZ17g//fDv3olg5Lzhy8Bf4S30tk5a7+ti/lip8rlf9lWVj1L+nrvWACnym+eo0 kTozEyDOO2sOiQ2buI9ANhE7iceImGNQ9fGT11023lusgegW91T9F7PprgYYC6uZ qPeKZK1JQh9m+iDWvVhc2I7IkUZSz8T8c3GnlQjzRvR92Fq/8x3ixojuNnaGukaT kgBYVoe8/g88TacwLBzmQDMCZhfOCd96Bsc5wjqQbeBoNkaihuDVGmtZbrdzeM1l FMqAKq3yd41OEn26n3qDKO37NmUjNCqXmPkBjHbfsTmwjtcOU0mHs+zs8rUpyPvX sjO1kwfug9FjlkBd9rZOMpJ/T7n0yyId/cpm6inmzs7L+4oytdUqCN8OcRQXqX0T MsdWIm0IRv/WtceMI5D62mEE/j/g+B2Y+tQQgONhkH+ABIDkLUCU6cZQMY4ewvz7 e2T+OuD1OQeWC95bazFGH2guGx4OJT5N+fvoBuaYm4U3PCScrCILIcV8YpfDI/rO rtVr+kn6f8NTpciEnDczbSw7fvUBtFH7E/8cyvwEiJhRG/QjxlCKApeqXuzsgdq8 CoeitscTXFC62HjTelVGu5sZ5w2cloHrigQkBuY4cO0MqCoo2FCUtlyGwIeqDyiu
Bug#945267: marked as pending in devscripts
Control: tag -1 pending Hello, Bug #945267 in devscripts 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/debian/devscripts/commit/d05c232bdade67de0b841bde83e562cce6617366 Make the Python code compliant with pylint-2.4.4. Closes: #945267 Signed-off-by: Mattia Rizzolo (this message was generated automatically) -- Greetings https://bugs.debian.org/945267
Processed: retitle 928131 to julia: FTBFS on arm64 and armhf, found 928131 in 1.2.0+dfsg-1
Processing commands for cont...@bugs.debian.org: > retitle 928131 julia: FTBFS on arm64 and armhf Bug #928131 [src:julia] julia: FTBFS on armhf, i386, ppc64el Changed Bug title to 'julia: FTBFS on arm64 and armhf' from 'julia: FTBFS on armhf, i386, ppc64el'. > found 928131 1.2.0+dfsg-1 Bug #928131 [src:julia] julia: FTBFS on arm64 and armhf Marked as found in versions julia/1.2.0+dfsg-1. > thanks Stopping processing here. Please contact me if you need assistance. -- 928131: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=928131 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Bug#945267 marked as pending in devscripts
Processing control commands: > tag -1 pending Bug #945267 [devscripts] FTBFS: FAIL: test_pylint (devscripts.test.test_pylint.PylintTestCase) Added tag(s) pending. -- 945267: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=945267 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#945316: polymake: FTBFS with perl 5.30
Benjamin Lorenz writes: > On 22/11/2019 22.06, Andreas Beckmann wrote: >> polymake FTBFS against perl 5.30: >> https://buildd.debian.org/status/package.php?p=polymake=unstable >> >> *** Summary *** >> >> *** Failed tests *** >> >> /<>/apps/polytope/src/gc_closure.cc:173: testcase 1 >> expected: regular return >> got: EXCEPTION: no more rules available to compute >> 'HILBERT_BASIS_GENERATORS' >> >> make[1]: *** [debian/rules:41: override_dh_auto_test] Error 1 > > This was already reported and should be fixed with > https://bugs.debian.org/941933 > but it seems that the builds need to be triggered again as the logs are > older than the normaliz 3.8.1+ds-1 upload. > > Benjamin Hello Benjamin; That's true, however with normaliz 3.8.1 I also get test failures. [ /functions/Producing a polytope from polytopes/stack ] 1 verifying: 1 OK [ /functions/Triangulations, subdivisions and volume/staircase_weight ] 1 verifying: 1 OK [ /functions/Producing a polytope from polytopes/tensor ] 1 verifying: 1 OK [ /functions/Optimization/totally_dual_integral ] 1Segmentation fault Full log is attached. polymake_3.2r4-4_amd64-2019-11-23T16:47:22Z.build.gz Description: application/gzip
Processed: reassign 945205 to libwacom-bin, severity of 945205 is important
Processing commands for cont...@bugs.debian.org: > reassign 945205 libwacom-bin Bug #945205 [bugs.debian.org] Wacom Cintiq 27QHD not working [as it did in Stretch] Bug reassigned from package 'bugs.debian.org' to 'libwacom-bin'. Ignoring request to alter found versions of bug #945205 to the same values previously set Ignoring request to alter fixed versions of bug #945205 to the same values previously set > severity 945205 important Bug #945205 [libwacom-bin] Wacom Cintiq 27QHD not working [as it did in Stretch] Severity set to 'important' from 'grave' > thanks Stopping processing here. Please contact me if you need assistance. -- 945205: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=945205 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#942688: NMU for elixir-lang
> >> As elixir-lang is going to be AUTORM if nobody takes care of it, I > >> already added a bit of code in debian/rules to make it retry unit tests > >> if they fail. It will retry 3 times, meaning that if it used to fail 10% > >> of the time, making it retry 3 times makes the unit tests fail 0.01% of > >> the times, which is IMO acceptable. The recent failures on some arch > >> shows that my debian/rules hack works well! :) > > > > Please don't do that sort of thing. It makes things gratuitously painful > > for people like me doing QA. > > > > Either a unit test is to be trusted or it's not (by "trusted" I mean > > here that a failure in the test means the package is unsuitable for > > release). > > > > If the test is trusted but it fails, accept that it fails and do not > > let the package to propagate to testing. > > > > If it's not trusted, there is no point in making it to fail with any > > probability. Not 10%, and not 0.01%. Just disable the test. > > > > Thanks. > > I don't agree with this view. Yes, this makes your work harder. But > running tests improve the quality of the package. Removing them is in no > way an improvement. My complain here is specifically about artificially reducing the probability of a random test to fail. Remember that tests only improve the quality of the package when you actually do something when they fail. If you artificially reduce the probability and do nothing about failing tests, there is no increase of quality at all. [ Please Cc me on any replies, I'm not monitoring this bug ] Thanks.
Bug#942789: marked as done (libbio-{db-{biofetch,gff,seqfeature},searchio-hmmer,tools-run-remoteblast}-perl: missing Breaks+Replaces: libbio-perl-perl (<< 1.7.3))
Your message dated Sat, 23 Nov 2019 16:49:30 +
with message-id
and subject line Bug#942789: fixed in libbio-graphics-perl 2.40-5
has caused the Debian Bug report #942789,
regarding
libbio-{db-{biofetch,gff,seqfeature},searchio-hmmer,tools-run-remoteblast}-perl:
missing Breaks+Replaces: libbio-perl-perl (<< 1.7.3)
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
942789: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=942789
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package:
libbio-db-biofetch-perl,libbio-db-gff-perl,libbio-db-seqfeature-perl,libbio-searchio-hmmer-perl,libbio-tools-run-remoteblast-perl
Version: 1.7.3-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Hi,
during a test with piuparts I noticed your package fails to upgrade from
'testing'.
It installed fine in 'testing', then the upgrade to 'sid' fails
because it tries to overwrite other packages files without declaring a
Breaks+Replaces relation.
See policy 7.6 at
https://www.debian.org/doc/debian-policy/ch-relationships.html#overwriting-files-and-replacing-packages-replaces
>From the attached log (scroll to the bottom...):
Preparing to unpack .../libbio-db-biofetch-perl_1.7.3-1_all.deb ...
Unpacking libbio-db-biofetch-perl (1.7.3-1) ...
dpkg: error processing archive
/var/cache/apt/archives/libbio-db-biofetch-perl_1.7.3-1_all.deb (--unpack):
trying to overwrite '/usr/share/man/man3/Bio::DB::BioFetch.3pm.gz', which is
also in package libbio-perl-perl 1.7.2-3
Errors were encountered while processing:
/var/cache/apt/archives/libbio-db-biofetch-perl_1.7.3-1_all.deb
The (<< 1.7.3) version constraint is based on my assumption that 1.7.3 split
up libbio-perl-perl into several independent source packages.
cheers,
Andreas
libbio-perl-perl=1.7.2-3_libbio-db-biofetch-perl=1.7.3-1.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: libbio-graphics-perl
Source-Version: 2.40-5
We believe that the bug you reported is fixed in the latest version of
libbio-graphics-perl, 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 942...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Michael R. Crusoe (supplier of updated
libbio-graphics-perl 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, 23 Nov 2019 09:23:09 +0100
Source: libbio-graphics-perl
Architecture: source
Version: 2.40-5
Distribution: unstable
Urgency: medium
Maintainer: Debian Med Packaging Team
Changed-By: Michael R. Crusoe
Closes: 942789
Changes:
libbio-graphics-perl (2.40-5) unstable; urgency=medium
.
* Team upload.
* debian/control: Breaks+Replaces the old libbio-bio-perl. (Closes: #942789)
* debian/patches/spelling: fix typos
Checksums-Sha1:
b155e9b4fac62303ebe6d66d04e3ad517e570749 2307 libbio-graphics-perl_2.40-5.dsc
6a146a65449369fd775274279bcd45bb1f70cce5 10980
libbio-graphics-perl_2.40-5.debian.tar.xz
663adb8ec70aa36e684bfbbfae794cff19c14e14 7449
libbio-graphics-perl_2.40-5_source.buildinfo
Checksums-Sha256:
1fb1822b4e941ce69906171bdb9613260b91da1fe5fc6993c515b55212d286f1 2307
libbio-graphics-perl_2.40-5.dsc
564163e1a0646fa2a38e9f446b93f636668a55ce157e7155c697f9832e126eae 10980
libbio-graphics-perl_2.40-5.debian.tar.xz
6d51641d33c37f0d0cb80ae0adca7cbc939b61b589f2b5698eee5d3c3eb01a91 7449
libbio-graphics-perl_2.40-5_source.buildinfo
Files:
d9588c4e3186da46279aea70caa0ae80 2307 perl optional
libbio-graphics-perl_2.40-5.dsc
05c24c994950b6153042d4e70e90e550 10980 perl optional
libbio-graphics-perl_2.40-5.debian.tar.xz
af9e6458b980f0cf67d5e7aed8f23e51 7449 perl optional
libbio-graphics-perl_2.40-5_source.buildinfo
-BEGIN PGP SIGNATURE-
iQIzBAEBCgAdFiEEck1gkzcRPHEFUNdHPCZ2P2xn5uIFAl3Y70UACgkQPCZ2P2xn
5uJFtw/9FJjl6ANTiXDQe8jRDsXhNGxA0X/qLPCvqhkJszVEhkpI+scjsANzl2tc
LxDQqqOUQUFM/ojBN8Kyn6W4FKBd2K3b2plrM4hfPNsk813ScMbBwOWH8GQ6+Q8T
sR05ZAxl1PWsUckz1rTfLqhSHEnuHy4/Zpp+S4Z2FL+VwtK/BzuZmJSHHa4KZ3w7
nacBYFtZZ3PVDekago4hhWY0OtMhToTwNHPK+hA0GUW9E1yUtjvjOOYUgu2YF92j
4LxG99CiU5DYIWkQvciSoS0/G2aB4B9c99+H6awp2IeE7UCa1Tmx0j5SC3yZNK82
Processed: Tagging Python 3.8 FTBFS
Processing commands for cont...@bugs.debian.org: > tags 943622 + ftbfs Bug #943622 [src:python-biom-format] some python-biom-format tests fail with python3.8 Added tag(s) ftbfs. > tags 945326 + ftbfs Bug #945326 [src:pysph] pysph ftbfs in unstable Added tag(s) ftbfs. > tags 945328 + ftbfs Bug #945328 [src:pyzmq] pyzmq ftbfs in unstable Added tag(s) ftbfs. > tags 945346 + ftbfs Bug #945346 [src:python-skbio] python-skbio ftbfs in unstable Added tag(s) ftbfs. > tags 945330 + ftbfs Bug #945330 [src:yt] yt ftbfs in unstable Added tag(s) ftbfs. > thanks Stopping processing here. Please contact me if you need assistance. -- 943622: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=943622 945326: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=945326 945328: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=945328 945330: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=945330 945346: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=945346 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#945202: marked as done (pytest-pylint: FTBFS in sid)
Your message dated Sat, 23 Nov 2019 10:30:24 -0500 with message-id and subject line Re: [Python-modules-team] Bug#945202: Bug#945202: pytest-pylint: FTBFS in sid has caused the Debian Bug report #945202, regarding pytest-pylint: FTBFS in sid to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 945202: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=945202 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: pytest-pylint Version: 0.14.1-2 Severity: serious Hello, your packages FTBFS with default Python3.8 in sid Can you please have a look? I: Running cd /build/pytest-pylint-0.14.1/ && env PATH="/usr/sbin:/usr/bin:/sbin:/bin" HOME="/nonexistent" dpkg-buildpackage -us -uc dpkg-buildpackage: info: source package pytest-pylint dpkg-buildpackage: info: source version 0.14.1-2 dpkg-buildpackage: info: source distribution unstable dpkg-buildpackage: info: source changed by Ond??ej Kobli??ek dpkg-source --before-build . dpkg-buildpackage: info: host architecture amd64 dpkg-source: info: using options from pytest-pylint-0.14.1/debian/source/options: --extend-diff-ignore=^[^/]*[.]egg-info/ debian/rules clean dh clean --with python3 --buildsystem=pybuild dh_auto_clean -O--buildsystem=pybuild I: pybuild base:217: python3.8 setup.py clean running clean removing '/build/pytest-pylint-0.14.1/.pybuild/cpython3_3.8_pytest-pylint/build' (and everything under it) 'build/bdist.linux-amd64' does not exist -- can't clean it 'build/scripts-3.8' does not exist -- can't clean it I: pybuild base:217: python3.7 setup.py clean running clean removing '/build/pytest-pylint-0.14.1/.pybuild/cpython3_3.7_pytest-pylint/build' (and everything under it) 'build/bdist.linux-amd64' does not exist -- can't clean it 'build/scripts-3.7' does not exist -- can't clean it dh_autoreconf_clean -O--buildsystem=pybuild dh_clean -O--buildsystem=pybuild dpkg-source -b . dpkg-source: info: using options from pytest-pylint-0.14.1/debian/source/options: --extend-diff-ignore=^[^/]*[.]egg-info/ dpkg-source: info: using source format '3.0 (quilt)' dpkg-source: info: building pytest-pylint using existing ./pytest-pylint_0.14.1.orig.tar.gz dpkg-source: info: using patch list from debian/patches/series dpkg-source: info: building pytest-pylint in pytest-pylint_0.14.1-2.debian.tar.xz dpkg-source: info: building pytest-pylint in pytest-pylint_0.14.1-2.dsc debian/rules binary dh binary --with python3 --buildsystem=pybuild dh_update_autotools_config -O--buildsystem=pybuild dh_autoreconf -O--buildsystem=pybuild dh_auto_configure -O--buildsystem=pybuild I: pybuild base:217: python3.8 setup.py config running config I: pybuild base:217: python3.7 setup.py config running config dh_auto_build -O--buildsystem=pybuild I: pybuild base:217: /usr/bin/python3.8 setup.py build running build running build_py copying pytest_pylint.py -> /build/pytest-pylint-0.14.1/.pybuild/cpython3_3.8_pytest-pylint/build I: pybuild base:217: /usr/bin/python3 setup.py build running build running build_py copying pytest_pylint.py -> /build/pytest-pylint-0.14.1/.pybuild/cpython3_3.7_pytest-pylint/build create-stamp debian/debhelper-build-stamp dh_testroot -O--buildsystem=pybuild dh_prep -O--buildsystem=pybuild debian/rules override_dh_auto_install make[1]: Entering directory '/build/pytest-pylint-0.14.1' dh_auto_install I: pybuild base:217: /usr/bin/python3.8 setup.py install --root /build/pytest-pylint-0.14.1/debian/python3-pytest-pylint running install running build running build_py running install_lib creating /build/pytest-pylint-0.14.1/debian/python3-pytest-pylint/usr creating /build/pytest-pylint-0.14.1/debian/python3-pytest-pylint/usr/lib creating /build/pytest-pylint-0.14.1/debian/python3-pytest-pylint/usr/lib/python3.8 creating /build/pytest-pylint-0.14.1/debian/python3-pytest-pylint/usr/lib/python3.8/dist-packages copying /build/pytest-pylint-0.14.1/.pybuild/cpython3_3.8_pytest-pylint/build/pytest_pylint.py -> /build/pytest-pylint-0.14.1/debian/python3-pytest-pylint/usr/lib/python3.8/dist-packages byte-compiling /build/pytest-pylint-0.14.1/debian/python3-pytest-pylint/usr/lib/python3.8/dist-packages/pytest_pylint.py to pytest_pylint.cpython-38.pyc running install_egg_info running egg_info creating pytest_pylint.egg-info writing pytest_pylint.egg-info/PKG-INFO writing dependency_links to pytest_pylint.egg-info/dependency_links.txt writing entry points to pytest_pylint.egg-info/entry_points.txt writing requirements to pytest_pylint.egg-info/requires.txt writing top-level names to
Bug#942887: marked as done (python-fabio: autopkgtest failure.)
Your message dated Sat, 23 Nov 2019 14:49:38 +
with message-id
and subject line Bug#942887: fixed in python-fabio 0.9.0+dfsg-3
has caused the Debian Bug report #942887,
regarding python-fabio: autopkgtest failure.
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
942887: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=942887
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: python-fabio
Version: 0.9.0+dfsg-2
Severity: serious
Python-fabio's autopkgtest is failing,
==
ERROR: testFullFormatName (fabio.test.testfabioconvert.TestFabioConvert)
--
Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/fabio/test/testfabioconvert.py", line
135, in testFullFormatName
image = fabio.open("output/03.npy")
File "/usr/lib/python3/dist-packages/fabio/openimage.py", line 159, in
openimage
obj = obj.read(obj.filename, frame)
File "/usr/lib/python3/dist-packages/fabio/numpyimage.py", line 161, in read
self.dataset = numpy.load(infile)
File "/usr/lib/python3/dist-packages/numpy/lib/npyio.py", line 447, in load
pickle_kwargs=pickle_kwargs)
File "/usr/lib/python3/dist-packages/numpy/lib/format.py", line 696, in
read_array
raise ValueError("Object arrays cannot be loaded when "
ValueError: Object arrays cannot be loaded when allow_pickle=False
--
This appears to be happening during both the unstable->testing migration tests
and the pure unstable tests, but not during the pure testing tests.
--- End Message ---
--- Begin Message ---
Source: python-fabio
Source-Version: 0.9.0+dfsg-3
We believe that the bug you reported is fixed in the latest version of
python-fabio, 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 942...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Picca Frédéric-Emmanuel (supplier of updated python-fabio
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, 23 Nov 2019 15:35:06 +0100
Source: python-fabio
Architecture: source
Version: 0.9.0+dfsg-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Science Maintainers
Changed-By: Picca Frédéric-Emmanuel
Closes: 942887
Changes:
python-fabio (0.9.0+dfsg-3) unstable; urgency=medium
.
[ Alexandre Marie ]
* Fixed autopkgtest with ec7a2d1 commit from upstream. (Closes: #942887)
Checksums-Sha1:
3aaec6cc8fa00f2b223bb57a5c3bd08e5272dc19 2922 python-fabio_0.9.0+dfsg-3.dsc
530d3e63907c094d8bc0e3a0100d23a75198a827 8772
python-fabio_0.9.0+dfsg-3.debian.tar.xz
Checksums-Sha256:
3fc0618310d38a2a6b5263387b76f13403bbbcfaf985a653e8c6e59e312e957d 2922
python-fabio_0.9.0+dfsg-3.dsc
e52ec4bd0855255c7baeb8042af81e3f916c5f1b6f88edbae8b353b08f426d8f 8772
python-fabio_0.9.0+dfsg-3.debian.tar.xz
Files:
6538ecee1a8b3139102d78c4be15f528 2922 science optional
python-fabio_0.9.0+dfsg-3.dsc
0d25fa0aa56b49977e599a18ce3bd2de 8772 science optional
python-fabio_0.9.0+dfsg-3.debian.tar.xz
-BEGIN PGP SIGNATURE-
iQJFBAEBCgAvFiEE2bRTt5m4gw2UXmoKW/VOXhK5ALsFAl3ZRJkRHHBpY2NhQGRl
Ymlhbi5vcmcACgkQW/VOXhK5ALtDZhAAj3fPK++WvPEAIk8xqLgh2DPNmfY+XJ9K
cKRuArpoN9nd88K8x9dgKf2hfvYb1WE44DJwRfA2pSFnJ6E78KRBuRLgk2gPLDhL
sISz9k2tRfpv2d/+Qo6LLAIyFf+9Xumxxzad21F2SX/bNsk3JdHn63ZAb6fRc0rK
eD9ytBtd6xaNxFPSHp4jtpXtSR3w7VSKBLQ65aFxt+U9jKAnUXyoKMZgj7iyTB6f
qjO+NJNxg1DlHxJqf5jWjy1I/MJs3/RiMROF/yF5jLUXnUXbepdcUDXJsXHqITsW
h9CAGM1g8CVxaqPIthZcxZNPUYUpbUprOg6OCLZvkMwDEfmVtDbcdMvgB8lxfr5Q
HBHkTZhxdWrSKg8OhPr3rQCb1dUikVEoX5r3BH4YRDkFhKBZsbOjqL7whD+qYlCY
G2p8gypF9r3HSbS4NIrsJn5ezzml+0K4pg67RP2rCsZ08nLGtNImeQAEYuuu/LYA
RloMySr2h+iCE0vQKgMLjKLk7yP/X2uKs5PO0kv7Q9SyhCVkvxvqzxIvcrfksUbD
AbrrgMOh74D/hJC3+05uYEl8IAh+qgZzDjmm3zKzo9MPCOtUHfCOpNnicdwXyDO4
Ga0gJoQEcu8S7OJCWDF/vRu6ulGjwedUnvNFj0utubMHcMGdyOEHnIwyZ7mXvC+y
q2oo/fQDcD4=
=0AWz
-END PGP SIGNATURE End Message ---
Bug#945349: (no subject)
Hi William, On Sat, Nov 23, 2019 at 10:42:16AM +0100, William Desportes wrote: > Hello Salvatore, > > I investigated while reporting the vulnerability, 4.6.6 > (https://packages.debian.org/source/oldstable/phpmyadmin) is not > affected since the table name you need to reproduce the vulnerability is > not supported. Thanks for checking that and reporting back! Regards, Salvatore
Bug#914663: marked as done (gxtuner does not trap errors from make)
Your message dated Sat, 23 Nov 2019 13:20:48 + with message-id and subject line Bug#914663: fixed in gxtuner 3.0-2 has caused the Debian Bug report #914663, regarding gxtuner does not trap errors from make 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.) -- 914663: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=914663 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: gxtuner Version: 3.0-1 Severity: serious Justification: policy 4.6 gxtuner's upstream Makefile does not trap errors from the compiler. Most compiler invocations carry a "-" prefix used for ignoring errors. That prefix violates policy section 4.6. It also makes debugging build failures unnecessarily hard and facilitates misbuilds. Helmut --- End Message --- --- Begin Message --- Source: gxtuner Source-Version: 3.0-2 We believe that the bug you reported is fixed in the latest version of gxtuner, 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 914...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Sebastian Ramacher (supplier of updated gxtuner 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, 23 Nov 2019 13:58:24 +0100 Source: gxtuner Architecture: source Version: 3.0-2 Distribution: unstable Urgency: medium Maintainer: Debian Multimedia Maintainers Changed-By: Sebastian Ramacher Closes: 914663 Changes: gxtuner (3.0-2) unstable; urgency=medium . [ Ondřej Nový ] * Team upload. * d/copyright: Use https protocol in Format field * d/control: Set Vcs-* to salsa.debian.org . [ Felipe Sateler ] * Change maintainer address to debian-multime...@lists.debian.org . [ Ondřej Nový ] * Use debhelper-compat instead of debian/compat . [ Sebastian Ramacher ] * debian/control: - Bump debhelper compat to 12 - Bump Standards-Version - Set RRR: no * debian/patches: Trap errors (Closes: #914663) Checksums-Sha1: 57a92c0d7d4c46b413c6cb54545eacce6fdfcd70 2010 gxtuner_3.0-2.dsc 17d9d616a00b5306ca994cee4e74661533de39e0 6936 gxtuner_3.0-2.debian.tar.xz Checksums-Sha256: 349050a03ea504404bf288cf912ab93db8edb5a81ba2f855945f86310fc9749a 2010 gxtuner_3.0-2.dsc d1bda8b201aac782528601d690f0b580b940a512ceb9e630a6fa87b681930b64 6936 gxtuner_3.0-2.debian.tar.xz Files: 23e305218e36dfeb8a553b7265eb7354 2010 sound optional gxtuner_3.0-2.dsc 5ec6350a62584998a2c76d88f93bde73 6936 sound optional gxtuner_3.0-2.debian.tar.xz -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEE94y6B4F7sUmhHTOQafL8UW6nGZMFAl3ZLVYACgkQafL8UW6n GZNWlhAAhn6NWuH/NPXzuHAGGNTg93Rt5vBxEw+phNAm9PprsdTNvBSVgRqGT7pO 0hjeJ2NPxUa/MKi16HogejTZSGlUymu5aUr+9sjeFYqt153DrDBD8Rsqehrd5Zn+ IqFTgoc+bTGvXYWBu/sNbzStVBl3ywN/JOFLNQeTDuVSDCI4x92wfcyzeICqWVYV 4/+GtNz5n5hINeQXQEXSRsiHEHaWctVhvcpd51Z4PWNHbAWXl6dWrMWdeI3hvd7T pgtxxIdMuuGwTtLzJEqx7psO/eX6avZB2QHcYTHOLJCglKIkzh7HE9Y/bWJ1spQH ErhdoH+CQqSpqVAm8UiNheKAvUdmO3Ukc+uQp4UkRxwTRfZpbla2z7GpiYdGGm7L lFbGSKL7VxbEG1t+pyD0IRIxie/tDAXeh9R2CWmLHajpvK93WtzA3oHGUISRuNSS 3rCr3gf1ZISKtpC9PqNEcqrryC4hPa6LvCh9jkdeDHnCAoKkPfUuMXWtau1joWcZ kkoXoT4Zp4IcN26u24hrfijWJ17LWEq8pzaMfMz8ju7dsuYElB+noTYXGECI8PIG F8YRS5SiiGG32I2sjRmyDwYiMIk9MO7X0XtKyh8OJxt40hpuCViCY9+SlxlwRRh2 IKApAfZ1onbQ03ZNVbBIURmJBe2PTw56jGlNouLz6vgtmYS7Zaw= =aYXh -END PGP SIGNATURE End Message ---
Bug#944468: marked as done (autopkg tests fail on 32bit architectures)
Your message dated Sat, 23 Nov 2019 11:34:32 + with message-id and subject line Bug#944468: fixed in lapack 3.9.0-1 has caused the Debian Bug report #944468, regarding autopkg tests fail on 32bit architectures 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.) -- 944468: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=944468 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:lapack Version: 3.8.0-8 Severity: serious Tags: sid bullseye patch The autopkg tests fail on 32bit architectures, because the 64bit packages are not available. Feel free to extend the list of 32bit archs to other architectures. http://launchpadlibrarian.net/450724497/lapack_3.8.0-8_3.8.0-8ubuntu1.diff.gz --- End Message --- --- Begin Message --- Source: lapack Source-Version: 3.9.0-1 We believe that the bug you reported is fixed in the latest version of lapack, 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 944...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Sébastien Villemot (supplier of updated lapack 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, 23 Nov 2019 11:25:11 +0100 Source: lapack Architecture: source Version: 3.9.0-1 Distribution: unstable Urgency: medium Maintainer: Debian Science Team Changed-By: Sébastien Villemot Closes: 944468 Changes: lapack (3.9.0-1) unstable; urgency=medium . [ Sébastien Villemot ] * d/watch: update for move to Github * New upstream version 3.9.0 * lapacke-makefile.patch: drop patch, applied upstream * d/rules: adapt for renaming of variables and path changes in upstream Makefiles * liblapack-doc: remove unused override for spelling-error-in-manpage * missing-lapacke-prototypes.patch: new patch, fixes unresolved symbols in liblapacke * Adapt lapack autopkgtests for a behaviour change in lapack_testing.py . [ Matthias Klose ] * Don't run the 64bit autopkg tests on 32bit architectures. (Closes: #944468) . [ Mo Zhou ] * Also exclude the rest 32bit Arches (that doko missed) for autopkgtest. Checksums-Sha1: 06a52aa4dfa3703a7a4eff58e9fe66d0c4f45094 3364 lapack_3.9.0-1.dsc 0451d180eed2b12b94aaae77e772d7573e87bec4 7534567 lapack_3.9.0.orig.tar.gz 755608c4fd539521730e903f0589ad192d0bfec1 27332 lapack_3.9.0-1.debian.tar.xz e582c34388cf91f8b515d94495b4af09ba23fd9d 16608 lapack_3.9.0-1_amd64.buildinfo Checksums-Sha256: 3fef51c4fdb061c22be677748bf27574ce1be10bc7fd6ce3b562d28e98abfb72 3364 lapack_3.9.0-1.dsc 106087f1bb5f46afdfba7f569d0cbe23dacb9a07cd24733765a0e89dbe1ad573 7534567 lapack_3.9.0.orig.tar.gz 7e727c8b6d1eb03137f93bb58e057e2689d0700cbc1f33ccaa62cd2303cfb322 27332 lapack_3.9.0-1.debian.tar.xz e0052c6962fb1fbcf7d5ee098acfa82e842365256b9317bb031113acded85a70 16608 lapack_3.9.0-1_amd64.buildinfo Files: 15e3b5171d5e87a5d3ebee0986b49039 3364 libs optional lapack_3.9.0-1.dsc 0b251e2a8d5f949f99b50dd5e2200ee2 7534567 libs optional lapack_3.9.0.orig.tar.gz 6be90683d7485800135c5cc5d69ba234 27332 libs optional lapack_3.9.0-1.debian.tar.xz 376ffc7aa573867c672c15befbd144de 16608 libs optional lapack_3.9.0-1_amd64.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEU5UdlScuDFuCvoxKLOzpNQ7OvkoFAl3ZFjwACgkQLOzpNQ7O vkpFmA/+PDq+uvCpGC41mL+BXzSCFZejIpDrB1JlrBASrt0F2eDH9XxCD/NfDds2 OtZWRXpBpAK2xRFcPknib7Dapf1JxMNwHLiipaCtFLBTHXbXu4S0vPsZ67mZ5ABH GNVEgv8PV2GTDwHsg8saBG+N4t3So+DDN8IH6jOuTgfCgXup2UYl6pxNw7a20e++ ey44eRDK2aAJQ2WYHeWIB81D5VCZcln8NrUaN/qUbTmqf/vyZYdD5XNHRfbrjDK0 99JKM+1MqGy6UvVgXw+QCovgc7lDv8ypovbQGTLcMNRVv0dm+N2k01RpqycGMJCg 0Ggoul9bHLNUBoFj4gs8ObAmOxBnHzM/xZoMLdBTw6uRL2CHAs7s020BSmcoMrNq iwaU++bqUZmJyKifvocUW4buyB+AVDnvc0lf+Hb+GxDKdWioGIYh6RzoUV8pEMRW sDdZHK44f7LETxH3tYAtz2QFcHpHMgezOkilo39CU3Xy6BZITsZhLfb/lbacEwxr m/IZ8kvFxwAavPWucKPGnM0+qgb+fBLpvveO3tTSeJEnYJzsFogmLb5wEX6xYpCT 1C9NREpHzG7cuaU/DUn5bsbc/5A3W2aMlnfFoainBVV44MZZVWz1Iam/SJ9beO8v 4SpaCPEmnWNnc57o3svtOzflaQ/fm7Dx04NfvKmZuF2wd1TFeDk= =0GC/ -END PGP SIGNATURE End Message ---
Bug#943615: marked as done (python-multidict ftbfs with python3.8 (test failures))
Your message dated Sat, 23 Nov 2019 11:19:49 +
with message-id
and subject line Bug#943615: fixed in python-multidict 4.6.1-1
has caused the Debian Bug report #943615,
regarding python-multidict ftbfs with python3.8 (test failures)
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
943615: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=943615
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:python-multidict
Version: 4.5.2-1
Severity: important
Tags: sid bullseye
User: debian-pyt...@lists.debian.org
Usertags: python3.8
test failures when running the tests with python3.8:
=== FAILURES ===
___ test_load_from_file[MultiDict-5] ___
pickle_protocol = 5, cls_name = 'MultiDict'
def test_load_from_file(pickle_protocol, cls_name):
cls = globals()[cls_name]
d = cls([('a', 1), ('a', 2)])
fname = '{}.pickle.{}'.format(cls_name.lower(), pickle_protocol)
p = here / fname
> with p.open('rb') as f:
tests/test_pickle.py:113:
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
/usr/lib/python3.8/pathlib.py:1200: in open
return io.open(self, mode, buffering, encoding, errors, newline,
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
self =
PosixPath('/<>/.pybuild/cpython3_3.8_multidict/build/tests/multidict.pickle.5')
name =
'/<>/.pybuild/cpython3_3.8_multidict/build/tests/multidict.pickle.5'
flags = 524288, mode = 438
def _opener(self, name, flags, mode=0o666):
# A stub for the opener argument to built-in open()
> return self._accessor.open(self, flags, mode)
E FileNotFoundError: [Errno 2] No such file or directory:
'/<>/.pybuild/cpython3_3.8_multidict/build/tests/multidict.pickle.5'
/usr/lib/python3.8/pathlib.py:1054: FileNotFoundError
__ test_load_from_file[CIMultiDict-5] __
pickle_protocol = 5, cls_name = 'CIMultiDict'
def test_load_from_file(pickle_protocol, cls_name):
cls = globals()[cls_name]
d = cls([('a', 1), ('a', 2)])
fname = '{}.pickle.{}'.format(cls_name.lower(), pickle_protocol)
p = here / fname
> with p.open('rb') as f:
tests/test_pickle.py:113:
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
/usr/lib/python3.8/pathlib.py:1200: in open
return io.open(self, mode, buffering, encoding, errors, newline,
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
self =
PosixPath('/<>/.pybuild/cpython3_3.8_multidict/build/tests/cimultidict.pickle.5')
name =
'/<>/.pybuild/cpython3_3.8_multidict/build/tests/cimultidict.pickle.5'
flags = 524288, mode = 438
def _opener(self, name, flags, mode=0o666):
# A stub for the opener argument to built-in open()
> return self._accessor.open(self, flags, mode)
E FileNotFoundError: [Errno 2] No such file or directory:
'/<>/.pybuild/cpython3_3.8_multidict/build/tests/cimultidict.pickle.5'
/usr/lib/python3.8/pathlib.py:1054: FileNotFoundError
__ test_load_from_file[PyMultiDict-5] __
pickle_protocol = 5, cls_name = 'PyMultiDict'
def test_load_from_file(pickle_protocol, cls_name):
cls = globals()[cls_name]
d = cls([('a', 1), ('a', 2)])
fname = '{}.pickle.{}'.format(cls_name.lower(), pickle_protocol)
p = here / fname
> with p.open('rb') as f:
tests/test_pickle.py:113:
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
/usr/lib/python3.8/pathlib.py:1200: in open
return io.open(self, mode, buffering, encoding, errors, newline,
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
self =
PosixPath('/<>/.pybuild/cpython3_3.8_multidict/build/tests/pymultidict.pickle.5')
name =
'/<>/.pybuild/cpython3_3.8_multidict/build/tests/pymultidict.pickle.5'
flags = 524288, mode = 438
def _opener(self, name, flags, mode=0o666):
# A stub for the opener argument to built-in open()
> return self._accessor.open(self, flags, mode)
E FileNotFoundError: [Errno 2] No such file or directory:
'/<>/.pybuild/cpython3_3.8_multidict/build/tests/pymultidict.pickle.5'
/usr/lib/python3.8/pathlib.py:1054: FileNotFoundError
_ test_load_from_file[PyCIMultiDict-5] _
pickle_protocol = 5, cls_name = 'PyCIMultiDict'
def test_load_from_file(pickle_protocol,
Bug#943615: marked as pending in python-multidict
Control: tag -1 pending Hello, Bug #943615 in python-multidict reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/python-team/modules/python-multidict/commit/f5d3ad5e508d5dab0f766e1ad5269c45d471be13 New upstream alpha release - Add support for Python3.8 (Closes: #943615) (this message was generated automatically) -- Greetings https://bugs.debian.org/943615
Processed: Bug#943615 marked as pending in python-multidict
Processing control commands: > tag -1 pending Bug #943615 [src:python-multidict] python-multidict ftbfs with python3.8 (test failures) Added tag(s) pending. -- 943615: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=943615 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#945348: marked as done (python3-joblib: Missing new dependency python3-pkg-resources)
Your message dated Sat, 23 Nov 2019 10:19:32 + with message-id and subject line Bug#945348: fixed in joblib 0.14.0-1 has caused the Debian Bug report #945348, regarding python3-joblib: Missing new dependency python3-pkg-resources 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.) -- 945348: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=945348 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: python3-joblib Version: 0.14.0-0.2 Severity: critical Tags: patch Justification: breaks unrelated software Hi, as per latest debci log of spades[1] joblib needs python3--pkg-resources. I will add this to the dependencies but I will also take over joblib packaging to Debian Science team to make the package watched by a greater audience. I've got confirmation from Yaroslav for similar cases in the past so I assume its OK. Kind regards Andreas. [1] https://ci.debian.net/data/autopkgtest/unstable/amd64/s/spades/3485245/log.gz -- System Information: Debian Release: bullseye/sid APT prefers testing APT policy: (501, 'testing'), (50, 'buildd-unstable'), (50, 'unstable'), (5, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.2.0-3-amd64 (SMP w/4 CPU cores) Kernel taint flags: TAINT_WARN Locale: LANG=de_DE.utf8, LC_CTYPE=de_DE.utf8 (charmap=UTF-8), LANGUAGE=de_DE.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages python3-joblib depends on: ii procps 2:3.3.15-2+b1 ii python3 3.7.5-1 Versions of packages python3-joblib recommends: ii python3-numpy 1:1.16.5-1 ii python3-psutil 5.5.1-1+b2 ii python3-pytest 3.10.1-2 ii python3-simplejson 3.16.0-2+b1 python3-joblib suggests no packages. -- no debconf information --- End Message --- --- Begin Message --- Source: joblib Source-Version: 0.14.0-1 We believe that the bug you reported is fixed in the latest version of joblib, 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 945...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Andreas Tille (supplier of updated joblib package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Sat, 23 Nov 2019 10:54:20 +0100 Source: joblib Architecture: source Version: 0.14.0-1 Distribution: unstable Urgency: medium Maintainer: Debian Science Maintainers Changed-By: Andreas Tille Closes: 945348 Changes: joblib (0.14.0-1) unstable; urgency=medium . * Team upload. * Move package to Debian Science team maintenance * debhelper-compat 12 * Standards-Version: 4.4.1 * Testsuite: autopkgtest-pkg-python * Secure URI in copyright format * Respect DEB_BUILD_OPTIONS in override_dh_auto_test target * Remove trailing whitespace in debian/changelog * Drop ancient X-Python-Version field * Set debhelper-compat version in Build-Depends. * Remove patches missing from debian/patches/series. * Set upstream metadata fields: Repository. * New Dependency: python*-pkg-resources Closes: #945348 Checksums-Sha1: c5f293b952dea52b4f5db1f37bb5edb99e3ed364 2253 joblib_0.14.0-1.dsc 45e2cb96e5399138c44c07c7ad8506f0dc42c22a 6632 joblib_0.14.0-1.debian.tar.xz 88fe2aba742f99906f13461d900813d7d3484a7b 16290 joblib_0.14.0-1_source.buildinfo Checksums-Sha256: 22915abd1c2ed8a7f04772e415e0b5f8e02337cd351fa9f306040e65f96048d5 2253 joblib_0.14.0-1.dsc ef0ec6ffddc357309885e40f3aa77ec5207ef83a62c53e275e9e6819c092473d 6632 joblib_0.14.0-1.debian.tar.xz 58fb1a711d8b69d1c13ec1bc0632ec88f3f09672e23c17c69e5f328105fda21c 16290 joblib_0.14.0-1_source.buildinfo Files: c316d3701011f8404cf09249b19d16c2 2253 python optional joblib_0.14.0-1.dsc dd7092cd29161db6311cf1e55851eff8 6632 python optional joblib_0.14.0-1.debian.tar.xz 98fbf203d9ff76e630f43841f2ad40ce 16290 python optional joblib_0.14.0-1_source.buildinfo -BEGIN PGP SIGNATURE- iQJCBAEBCAAsFiEE8fAHMgoDVUHwpmPKV4oElNHGRtEFAl3ZBNAOHHRpbGxlYUBy a2kuZGUACgkQV4oElNHGRtGwUw/+PY8Sx1KoGzvg06RxZ6KxdQ82kWIijhOK3a7S 716r/LjScsIi1SgH5p/kYUdcK//y7z1vhl1R49Nty3iglR0/VKbTBXDGg01RegTb
Bug#944249: [Pkg-emacsen-addons] Bug#944249: gnuplot-mode does not work with emacs26
Nicholas D Steeves writes: > Is that an official NACK for Augustin's patch for the autoloads? I > included it in the patch series I just sent... Hi. I tried out Augustin's update to the autoloads, and it works for me (thanks, Augustin!) Nicholas: you wanted to review and to improve things. Are your patches somewhere we can see them?
Bug#945349: (no subject)
Hello Salvatore, I investigated while reporting the vulnerability, 4.6.6 (https://packages.debian.org/source/oldstable/phpmyadmin) is not affected since the table name you need to reproduce the vulnerability is not supported. 4.9.2 will patch the vulnerability Regards, William Desportes
Bug#945316: polymake: FTBFS with perl 5.30
On 22/11/2019 22.06, Andreas Beckmann wrote: > polymake FTBFS against perl 5.30: > https://buildd.debian.org/status/package.php?p=polymake=unstable > > *** Summary *** > > *** Failed tests *** > > /<>/apps/polytope/src/gc_closure.cc:173: testcase 1 > expected: regular return > got: EXCEPTION: no more rules available to compute > 'HILBERT_BASIS_GENERATORS' > > make[1]: *** [debian/rules:41: override_dh_auto_test] Error 1 This was already reported and should be fixed with https://bugs.debian.org/941933 but it seems that the builds need to be triggered again as the logs are older than the normaliz 3.8.1+ds-1 upload. Benjamin signature.asc Description: OpenPGP digital signature
Processed: your mail
Processing commands for cont...@bugs.debian.org: > forwarded 945349 https://salsa.debian.org/phpmyadmin-team/phpmyadmin/issues/30 Bug #945349 [src:phpmyadmin] phpmyadmin: CVE-2019-18622 / PMASA-2019-5 Set Bug forwarded-to-address to 'https://salsa.debian.org/phpmyadmin-team/phpmyadmin/issues/30'. > stop Stopping processing here. Please contact me if you need assistance. -- 945349: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=945349 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#945301: marked as done (libhsdis0-fcml: fails to install: find: '/usr/lib/jvm': No such file or directory)
Your message dated Sat, 23 Nov 2019 09:34:15 + with message-id and subject line Bug#945301: fixed in fcml 1.2.0-2 has caused the Debian Bug report #945301, regarding libhsdis0-fcml: fails to install: find: '/usr/lib/jvm': No such file or directory to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 945301: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=945301 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: libhsdis0-fcml Version: 1.2.0-1 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package failed to install. As per definition of the release team this makes the package too buggy for a release, thus the severity. >From the attached log (scroll to the bottom...): Setting up libhsdis0-fcml:amd64 (1.2.0-1) ... find: '/usr/lib/jvm': No such file or directory dpkg: error processing package libhsdis0-fcml:amd64 (--configure): installed libhsdis0-fcml:amd64 package post-installation script subprocess returned error exit status 1 Processing triggers for libc-bin (2.29-3) ... Errors were encountered while processing: libhsdis0-fcml:amd64 cheers, Andreas libhsdis0-fcml_1.2.0-1.log.gz Description: application/gzip --- End Message --- --- Begin Message --- Source: fcml Source-Version: 1.2.0-2 We believe that the bug you reported is fixed in the latest version of fcml, 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 945...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Stephen Kitt (supplier of updated fcml 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, 23 Nov 2019 10:15:42 +0100 Source: fcml Architecture: source Version: 1.2.0-2 Distribution: unstable Urgency: medium Maintainer: Stephen Kitt Changed-By: Stephen Kitt Closes: 945301 Changes: fcml (1.2.0-2) unstable; urgency=medium . * Check that /usr/lib/jvm exists before processing it. Closes: #945301. * Process all template maintainer scripts without listing them explicitly. * Remove symlinks in prerm rather than postrm, to avoid having invalid symlinks at any time. * Fix the generated symlinks (“hdis” → “hsdis”). Checksums-Sha1: 7abefa3c9ebf8f7b94a1731f9354a45358a6d3d0 2022 fcml_1.2.0-2.dsc ec9c5715dc18cfe17ef00f20812694805790a722 15800 fcml_1.2.0-2.debian.tar.xz 8a881075a3d192735ff86a4cd04fba3bad3cdda9 7402 fcml_1.2.0-2_source.buildinfo Checksums-Sha256: 97442dd61e0ea07e3953051a02c72db4a49b29cef3e24dea9f8d670b06f0029c 2022 fcml_1.2.0-2.dsc ca1ca447b8506348ccbd81f6de2218667c20bcdaf94bcb98eecdbc7ec17826d0 15800 fcml_1.2.0-2.debian.tar.xz 0ae30aecd9a4facdf042ba0a723dd96ecbc746fe2aa937ad6cc9d0817ac466f2 7402 fcml_1.2.0-2_source.buildinfo Files: 773138f174eadbbcf6ebf86826a1c845 2022 devel optional fcml_1.2.0-2.dsc 30af8835c1f7543eb6aba4973e9a7a1f 15800 devel optional fcml_1.2.0-2.debian.tar.xz 5a7d906a8ca4c858c858fc21ffa02c93 7402 devel optional fcml_1.2.0-2_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEnPVX/hPLkMoq7x0ggNMC9Yhtg5wFAl3Y+TwACgkQgNMC9Yht g5yFSw//dy+1aZfi682GVfB/rwVyV00Igefmd7UlmjBAFeT+04mJFky0pEF2oPxk bXD3Wiwdq0QNVhDd5AJ2qRVQE/tFQPZZS6IQuu2g5EuI+IpJNBva9TXgFnInDeu+ AdVHgrKM2duaCJEMDvPP13MIlh2w6d/H95tkbJXj70kgY4vyre7BKgAjm5MXxcV4 NHSY/hV8hrAmWD+UW1nB8s6BcnR1sCozFKbR7mBH8MLTrReQ3W22R78CetkVIQVv qLjP4pvfzty2B37L8pxjMEwBIKpiQzSClqmFstQEdTdPG+pK8WtbkMtCmjwTik4j 6RzNIma8N4EwjcqBKeC2Kytp5bocbY/XYatCiUX3j5nwoFkGouOgdRuDAlPucNHN 0e4h8KLIHUf3eq3zAOFukhCVZWtSrFoS9oVyO/XzfsR4Bs5S9QkBlWEPKDHUqKgE TWr6ww2yP544HivXGeHlBVdWxoCvNnF7rUbYBoCxlGkUOcIEYsvGGJfU3Q583oiv aDOiWSjQdtI1qbXvyC43VyQAn9JmKGlESDJUH2BW6Dfopr9w75m23rlqqDROnxLR +KzoBd+9XsmSfE4xL2C4tk0QnXqW4KCFFiU1/uj9+rtf/BH2nRvOQ6mg41gX+n7N O9aq7tCPPPCa6FxNJwQX7JQf2u01GIxO3R6+m7SRotav1lKv1bM= =iH9W -END PGP SIGNATURE End Message ---
Bug#945303: marked as done (calendar-google-provider: Please package version corresponding to thunderbird version)
Your message dated Sat, 23 Nov 2019 10:24:35 +0100 with message-id <5ce1a8de-43a4-f346-9754-d8ee2fc6b...@t-online.de> and subject line Re: Bug#945303: calendar-google-provider: Please package version corresponding to thunderbird version has caused the Debian Bug report #945303, regarding calendar-google-provider: Please package version corresponding to thunderbird version to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 945303: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=945303 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: calendar-google-provider Version: 1:60.9.0-1~deb10u1 Severity: grave Justification: renders package unusable Dear Maintainer, Thunderbird and lightning packages were recently updated to 1:68.2.2-1~deb10u1 to fix security problems, but calendar-google-provider has not been updated. Anyone using the calendar-google-provider package must keep using the old thunderbird with security vulnerabilities until the package is updated. -- System Information: Debian Release: 10.2 APT prefers stable APT policy: (1000, 'stable'), (500, 'stable-updates') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.19.0-6-amd64 (SMP w/4 CPU cores) Locale: LANG=en_CA.utf8, LC_CTYPE=en_CA.utf8 (charmap=UTF-8), LANGUAGE=en_CA:en (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages calendar-google-provider depends on: hi lightning 1:60.9.0-1~deb10u1 calendar-google-provider recommends no packages. calendar-google-provider suggests no packages. -- no debconf information --- End Message --- --- Begin Message --- Hello Jonathan, Am 22.11.19 um 20:13 schrieb Jonathan Addleman: > Thunderbird and lightning packages were recently updated to > 1:68.2.2-1~deb10u1 > to fix security problems, but calendar-google-provider has not been updated. > > Anyone using the calendar-google-provider package must keep using the old > thunderbird with security vulnerabilities until the package is updated. you missed probably the latest NEWS entry for the thunderbird package. > $ zless /usr/share/doc/thunderbird/NEWS.Debian.gz | head -n17 > thunderbird (1:68.2.2-1) unstable; urgency=medium > > Starting with version 68.2.2-1 src:thunderbird isn't building the binary > package calendar-google-provider any more. > > If you want or need to use this Add-On please install this extension from > > > https://addons.thunderbird.net/en-GB/thunderbird/addon/provider-for-google-calendar/ > > (Please choose your preferred language!) > > The removal of this Add-On from the Thunderbird source was discussed within > this issue: > > https://bugzilla.mozilla.org/show_bug.cgi?id=1584614 > > -- Carsten Schoenert Sun, 10 Nov 2019 11:07:00 > +0100 So no, the source and the build of calendar-google-provider was dropped by upstream and we haven't forgotten to update this package. Unfortunately Mozilla isn't communicating such bigger changes very good in public and we can mostly just reacting. The removal was planned for a longer time was told me, but the code within the source had some issue that 2FA wasn't working anymore and an update wasn't possible in time so upstream decided to remove the AddOn directly even if the version was just increased by a minor version. I'll close your report by this email. -- Regards Carsten Schoenert--- End Message ---
Bug#945304: marked as done (calendar-google-provider: Please package version corresponding to thunderbird version)
Your message dated Sat, 23 Nov 2019 10:14:28 +0100 with message-id <503a14e2-1208-b3d6-f6d1-638b4bdbc...@t-online.de> and subject line Re: Bug#945304: (calendar-google-provider: Please package version corresponding to thunderbird version) has caused the Debian Bug report #945304, regarding calendar-google-provider: Please package version corresponding to thunderbird version to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 945304: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=945304 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: calendar-google-provider Version: 1:60.9.0-1~deb10u1 Severity: grave Justification: renders package unusable Dear Maintainer, Thunderbird and lightning packages were recently updated to 1:68.2.2-1~deb10u1 to fix security problems, but calendar-google-provider has not been updated. Anyone using the calendar-google-provider package must keep using the old thunderbird with security vulnerabilities until the package is updated. -- System Information: Debian Release: 10.2 APT prefers stable APT policy: (1000, 'stable'), (500, 'stable-updates') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.19.0-6-amd64 (SMP w/4 CPU cores) Locale: LANG=en_CA.utf8, LC_CTYPE=en_CA.utf8 (charmap=UTF-8), LANGUAGE=en_CA:en (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages calendar-google-provider depends on: hi lightning 1:60.9.0-1~deb10u1 calendar-google-provider recommends no packages. calendar-google-provider suggests no packages. -- no debconf information --- End Message --- --- Begin Message --- Hello Jonathan, Am 22.11.19 um 22:49 schrieb Jonathan Addleman: > Apologies for the duplicate submission. (#945393) Issues with my MTA, > and I thought the first one had bounced, but it had just been delayed... > > This report can be closed/deleted. you can close bug reports by your own. Have a look at to read all the commands to control the Debian BTS. https://www.debian.org/Bugs/server-control Especially have a look at https://www.debian.org/Bugs/Developer#closing -- Regards Carsten Schoenert--- End Message ---
Processed: Bug#945301 marked as pending in fcml
Processing control commands: > tag -1 pending Bug #945301 [libhsdis0-fcml] libhsdis0-fcml: fails to install: find: '/usr/lib/jvm': No such file or directory Added tag(s) pending. -- 945301: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=945301 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#945301: marked as pending in fcml
Control: tag -1 pending Hello, Bug #945301 in fcml 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/debian/fcml/commit/9cbc8414682b69fd74aa71ee5f3664c3a1d5f928 Check that /usr/lib/jvm exists before processing it Closes: #945301 (this message was generated automatically) -- Greetings https://bugs.debian.org/945301
Bug#944265: mailutils: local privilege escalation in maidag utility (fixed in 3.8)
Hi Jordi, On Fri, Nov 22, 2019 at 02:22:00PM +0100, Jordi Mallach wrote: > Hi all, > > El dl. 11 de 11 de 2019 a les 21:32 +0100, en/na Salvatore Bonaccorso > va escriure: > > Control: retitle -1 mailutils: local privilege escalation in maidag > > utility (fixed in 3.8) (CVE-2019-18862) > > Given this does not affect Debian by default, should my upload go > through debian-security or just s-p-u? > > https://salsa.debian.org/debian/mailutils/commit/c1683e71301e3c7454ab407334a211759148d47e I agree, that this does not warrant a DSA, so going via a point release is fine. We have marked it with unimportant severity in the security-tracker due to it's not installed setuid in any of the supported suites. Thanks for your work! Regards, Salvatore
Bug#942514: CVE-2019-16729 fixed in 1.0.4-1.1+deb8u1
fixed 942514 1.0.4-1.1+deb8u1 thanks Hi Russell, thanks for preparing this update. I just became aware of this and noticed that no DLA was released. In fact, neither the bug tracker nor the security tracker are aware of this issue being fixed. Releasing DLA-2000-1 for this, updating the bug tracker as well. regards, Hugo -- Hugo Lefeuvre (hle)|www.owl.eu.com RSA4096_ 360B 03B3 BF27 4F4D 7A3F D5E8 14AA 1EB8 A247 3DFD ed25519_ 37B2 6D38 0B25 B8A2 6B9F 3A65 A36F 5357 5F2D DC4C signature.asc Description: PGP signature
Processed: CVE-2019-16729 fixed in 1.0.4-1.1+deb8u1
Processing commands for cont...@bugs.debian.org: > fixed 942514 1.0.4-1.1+deb8u1 Bug #942514 [src:pam-python] pam-python: CVE-2019-16729: local root escalation The source 'pam-python' and version '1.0.4-1.1+deb8u1' do not appear to match any binary packages Marked as fixed in versions pam-python/1.0.4-1.1+deb8u1. > thanks Stopping processing here. Please contact me if you need assistance. -- 942514: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=942514 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#945333: marked as done (r-cran-seurat: uninstallable in sid: Depends: r-cran-matrix (>= 1.2.14) but 1.2-17-2 is to be installed)
Your message dated Sat, 23 Nov 2019 08:37:35 + with message-id and subject line Bug#945333: fixed in r-cran-seurat 3.1.1-1 has caused the Debian Bug report #945333, regarding r-cran-seurat: uninstallable in sid: Depends: r-cran-matrix (>= 1.2.14) but 1.2-17-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.) -- 945333: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=945333 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: r-cran-seurat Version: 3.0.2-1 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package is no longer installable in sid: The following packages have unmet dependencies: r-cran-seurat : Depends: r-cran-matrix (>= 1.2.14) but 1.2-17-2 is to be installed This seems to be a '.' vs '-' typo. Cheers, Andreas --- End Message --- --- Begin Message --- Source: r-cran-seurat Source-Version: 3.1.1-1 We believe that the bug you reported is fixed in the latest version of r-cran-seurat, 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 945...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Andreas Tille (supplier of updated r-cran-seurat package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Sat, 23 Nov 2019 08:40:02 +0100 Source: r-cran-seurat Binary: r-cran-seurat Architecture: source Version: 3.1.1-1 Distribution: unstable Urgency: medium Maintainer: Debian R Packages Maintainers Changed-By: Andreas Tille Description: r-cran-seurat - Tools for Single Cell Genomics Closes: 945333 Changes: r-cran-seurat (3.1.1-1) unstable; urgency=medium . * Team upload. * New upstream version Closes: #945333 * dh-update-R to update Build-Depends * Trim trailing whitespace. * Set upstream metadata fields: Archive, Bug-Database, Repository. * Standards-Version: 4.4.1 * debian/copyright: Use spaces rather than tabs in continuation lines. * Fix autopkgtest Checksums-Sha1: d273e84b270058c2a8eb43126a3c00b916463887 2710 r-cran-seurat_3.1.1-1.dsc 99bd8bdc621b5b7e15628330e383da974d9eeebb 790426 r-cran-seurat_3.1.1.orig.tar.gz 3f9d4481463bfd74a92e0d2e1a8034f0697c700f 3352 r-cran-seurat_3.1.1-1.debian.tar.xz Checksums-Sha256: 4d0890fc301ae8a5508bb59a622fcb1e520bdc820d48d72dae86dfd19bd2b278 2710 r-cran-seurat_3.1.1-1.dsc c00cbbdf525627a4b36c51733d0fad35a961df1288f3b0ab865acf269dc89420 790426 r-cran-seurat_3.1.1.orig.tar.gz aba230217b1f549865c656879d0784948a9dc0fada272d875c8e9414160c75fa 3352 r-cran-seurat_3.1.1-1.debian.tar.xz Files: e0ad8a54a8357eeec0b1fbeb1b2642bb 2710 gnu-r optional r-cran-seurat_3.1.1-1.dsc d3b87706d669d59c266b0a91d5290583 790426 gnu-r optional r-cran-seurat_3.1.1.orig.tar.gz 1b141f238a71524a5a059ce6eaefab19 3352 gnu-r optional r-cran-seurat_3.1.1-1.debian.tar.xz -BEGIN PGP SIGNATURE- iQJFBAEBCAAvFiEE8fAHMgoDVUHwpmPKV4oElNHGRtEFAl3Y5Z0RHHRpbGxlQGRl Ymlhbi5vcmcACgkQV4oElNHGRtH54w/9EnsejDJjUAqSqfxCTFLdImEfhr6Yz9Pg ZYqHi5c56NXrf8rB/PuBv4cmrxGubKCMdSee1nbhLu+HZjwYthlW3dIOG/L4qibk 5UbUmn1yuKMhZH0ixfdW2SbAbKmV1ViX21NOYKQRrAV3ODmy+BjSteps7I43r7xz 6kmG23AyXzQiK6sMhXPt9VgRCrPaGxTVtnuulKxhnDAK+WOS+/d4EM1l6UqjWaFm Raf6BaafhHJ0cJ3HF+UdM2eTHWdXlAHwc1VzD7rePehd+WPlyRJd0YDzhDmpi21/ Jhv8cGapZdIxH5IuHHceOJGFga4wT/140ctdNVsu4owR/pjIh/TQut6HJP7xwHsc JM3ZdrMc1WfMT28tHlEDXO9pmxuVlG+/oPeBD+6bgT1AjU/PFM41IbwDQuxsS5no WUATn/uIMaoE3ft4rCS3PsCjjTWSlbYNshZ5TJbEq9tLeJXqme4+Ggs8HyuAywmM qzSrggOXKCHBcSpYLOusPU8Qcc0dX9wfQYQKnCbVehRyFpnQ+kJY5xWljiQqffls M55J2ydP9zTNwPXEw+QhB+hG4xW21aeQ2PoXJM9PtvQr3QgXrVfnJO6wI/v3JM3d SieQhYnU42Gws36YL2VglgX3G9PzNCnu41UOn3GQUy/NIkoOa13t7IH9RIYP+Wtu Ky9hLnOOqRw= =O096 -END PGP SIGNATURE End Message ---
Bug#945349: phpmyadmin: CVE-2019-18622 / PMASA-2019-5
Source: phpmyadmin Version: 4:4.9.1+dfsg1-2 Severity: grave Tags: security upstream Justification: user security hole Hi, The following vulnerability was published for phpmyadmin. CVE-2019-18622[0]: | An issue was discovered in phpMyAdmin before 4.9.2. A crafted | database/table name can be used to trigger a SQL injection attack | through the designer feature. If you fix the vulnerability please also make sure to include the CVE (Common Vulnerabilities & Exposures) id in your changelog entry. For further information see: [0] https://security-tracker.debian.org/tracker/CVE-2019-18622 https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-18622 [1] https://www.phpmyadmin.net/security/PMASA-2019-5/ Please adjust the affected versions in the BTS as needed. Versions at least as old as 4.7.7 are affected, possibly olders as well, but looks upstream has only confirmed it (or investigated it) back to 4.7.7. Regards, Salvatore
Bug#945348: python3-joblib: Missing new dependency python3-pkg-resources
Package: python3-joblib Version: 0.14.0-0.2 Severity: critical Tags: patch Justification: breaks unrelated software Hi, as per latest debci log of spades[1] joblib needs python3--pkg-resources. I will add this to the dependencies but I will also take over joblib packaging to Debian Science team to make the package watched by a greater audience. I've got confirmation from Yaroslav for similar cases in the past so I assume its OK. Kind regards Andreas. [1] https://ci.debian.net/data/autopkgtest/unstable/amd64/s/spades/3485245/log.gz -- System Information: Debian Release: bullseye/sid APT prefers testing APT policy: (501, 'testing'), (50, 'buildd-unstable'), (50, 'unstable'), (5, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.2.0-3-amd64 (SMP w/4 CPU cores) Kernel taint flags: TAINT_WARN Locale: LANG=de_DE.utf8, LC_CTYPE=de_DE.utf8 (charmap=UTF-8), LANGUAGE=de_DE.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages python3-joblib depends on: ii procps 2:3.3.15-2+b1 ii python3 3.7.5-1 Versions of packages python3-joblib recommends: ii python3-numpy 1:1.16.5-1 ii python3-psutil 5.5.1-1+b2 ii python3-pytest 3.10.1-2 ii python3-simplejson 3.16.0-2+b1 python3-joblib suggests no packages. -- no debconf information
Bug#945347: radare2 FTBFS: meson.build:3:0: ERROR: ['/usr/bin/python3']> is not a valid python or it is missing setuptools
Source: radare2 Version: 3.2.1+dfsg-5 Severity: serious Tags: ftbfs radare2 fails to build from source. A build notably says: | meson.build:3:0: ERROR: ['/usr/bin/python3']> is not a valid python or it is missing setuptools https://tests.reproducible-builds.org/debian/rbuild/unstable/amd64/radare2_3.2.1+dfsg-5.rbuild.log.gz http://crossqa.debian.net/build/radare2_3.2.1+dfsg-5_armel_20191115204904.log According to crossqa logs this seems to have started between June 22nd and August 20th. Presumably something changed about the Python ecosystem. I understand that this might be fixed in the NEW upload, but I cannot check and poking at ftp-master didn't help thus far. Please just close the bug in case this is already fixed. Helmut
Bug#944844: marked as done (FTBFS on mips* (when building target LLVMAnalysis))
Your message dated Sat, 23 Nov 2019 09:09:40 +0100 with message-id <055356d8-a493-f646-920f-036019033...@debian.org> and subject line Re: Bug#944844: FTBFS on mips* (when building target LLVMAnalysis) has caused the Debian Bug report #944844, regarding FTBFS on mips* (when building target LLVMAnalysis) 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.) -- 944844: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=944844 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:llvm-toolchain-8 Version: 1:8.0.1-4 Severity: serious Tags: ftbfs User: debian-ocaml-ma...@lists.debian.org Usertags: ocaml-4.08-transition Dear Maintainer, llvm-toolchain-8 FTBFS on mips*: https://buildd.debian.org/status/package.php?p=llvm-toolchain-8=unstable This failure blocks the ocaml transition. Cheers, -- Stéphane -- System Information: Debian Release: bullseye/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 5.2.0-3-amd64 (SMP w/4 CPU cores) Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), LANGUAGE=fr_FR.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled --- End Message --- --- Begin Message --- fixed 944844 1:8.0.1-4 thanks Le 19/11/2019 à 10:53, Sylvestre Ledru a écrit : Le 16/11/2019 à 09:00, Stéphane Glondu a écrit : Package: src:llvm-toolchain-8 Version: 1:8.0.1-4 Severity: serious Tags: ftbfs User: debian-ocaml-ma...@lists.debian.org Usertags: ocaml-4.08-transition Dear Maintainer, llvm-toolchain-8 FTBFS on mips*: https://buildd.debian.org/status/package.php?p=llvm-toolchain-8=unstable This failure blocks the ocaml transition. The error is: ../../../bin/llvm-tblgen(_ZN4llvm3sys15PrintStackTraceERNS_11raw_ostreamE+0x44)[0x1202c6564] Stack dump: 0. Program arguments: ../../../bin/llvm-tblgen -gen-global-isel -I /<>/lib/Target/AArch64 -I /<>/include -I /<>/lib/Target /<>/lib/Target/AArch64/AArch64.td -o /<>/build-llvm/tools/clang/stage2-bins/lib/Target/AArch64/AArch64GenGlobalISel.inc Bus error Not sure what it means A rebuild fixed it llvm-toolchain-8 should not be a blocker anymore S--- End Message ---
Processed: Re: Bug#944844: FTBFS on mips* (when building target LLVMAnalysis)
Processing commands for cont...@bugs.debian.org: > fixed 944844 1:8.0.1-4 Bug #944844 [src:llvm-toolchain-8] FTBFS on mips* (when building target LLVMAnalysis) Marked as fixed in versions llvm-toolchain-8/1:8.0.1-4. > thanks Stopping processing here. Please contact me if you need assistance. -- 944844: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=944844 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#945346: python-skbio ftbfs in unstable
Package: src:python-skbio
Version: 0.5.5-2
Severity: serious
Tags: sid bullseye
User: debian-pyt...@lists.debian.org
Usertags: python3.8
python-skbio ftbfs in unstable, two failing tests:
==
ERROR: test_munging_invalid_type_to_self_type
(skbio.sequence.tests.test_sequence.TestDistance)
--
Traceback (most recent call last):
File
"/<>/.pybuild/cpython3_3.8_skbio/build/skbio/sequence/tests/test_sequence.py",
line 2369, in test_munging_invalid_type_to_self_type
Sequence("ACGT").distance(42)
File
"/<>/.pybuild/cpython3_3.8_skbio/build/skbio/sequence/_sequence.py",
line 1539, in distance
other = self._munge_to_self_type(other, 'distance')
File
"/<>/.pybuild/cpython3_3.8_skbio/build/skbio/sequence/_sequence.py",
line 2161, in _munge_to_self_type
return self.__class__(other)
File
"/<>/.pybuild/cpython3_3.8_skbio/build/skbio/sequence/_sequence.py",
line 622, in __init__
s = np.frombuffer(sequence, dtype=np.uint8)
TypeError: a bytes-like object is required, not 'int'
==
ERROR: test_init_invalid_sequence
(skbio.sequence.tests.test_sequence.TestSequence)
--
Traceback (most recent call last):
File
"/<>/.pybuild/cpython3_3.8_skbio/build/skbio/sequence/tests/test_sequence.py",
line 465, in test_init_invalid_sequence
Sequence(('a', 'b', 'c'))
File
"/<>/.pybuild/cpython3_3.8_skbio/build/skbio/sequence/_sequence.py",
line 622, in __init__
s = np.frombuffer(sequence, dtype=np.uint8)
TypeError: a bytes-like object is required, not 'tuple'
==
FAIL: test_no_variation_pearson
(skbio.stats.distance.tests.test_mantel.MantelTests)
--
Traceback (most recent call last):
File
"/<>/.pybuild/cpython3_3.8_skbio/build/skbio/stats/distance/tests/test_mantel.py",
line 250, in test_no_variation_pearson
npt.assert_equal(obs, (0.0, 1.0, 3))
File "/usr/lib/python3/dist-packages/numpy/testing/_private/utils.py", line
355, in assert_equal
assert_equal(actual[k], desired[k], 'item=%r\n%s' % (k, err_msg), verbose)
File "/usr/lib/python3/dist-packages/numpy/testing/_private/utils.py", line
427, in assert_equal
raise AssertionError(msg)
AssertionError:
Items are not equal:
item=0
ACTUAL: nan
DESIRED: 0.0
==
FAIL: test_one_sided_less (skbio.stats.distance.tests.test_mantel.MantelTests)
--
Traceback (most recent call last):
File
"/<>/.pybuild/cpython3_3.8_skbio/build/skbio/stats/distance/tests/test_mantel.py",
line 189, in test_one_sided_less
self.assertEqual(obs, (1, 1, 3))
AssertionError: Tuples differ: (0.9998, 1.0, 3) != (1, 1, 3)
First differing element 0:
0.9998
1
- (0.9998, 1.0, 3)
+ (1, 1, 3)
==
FAIL: Test against a reference implementation from R's ape package
--
Traceback (most recent call last):
File
"/<>/.pybuild/cpython3_3.8_skbio/build/skbio/stats/ordination/tests/test_principal_coordinate_analysis.py",
line 250, in test_pcoa_biplot_from_ape
assert_ordination_results_equal(obs, exp, ignore_directionality=True,
File
"/<>/.pybuild/cpython3_3.8_skbio/build/skbio/util/_testing.py",
line 126, in assert_ordination_results_equal
_assert_frame_equal(left.features, right.features,
File
"/<>/.pybuild/cpython3_3.8_skbio/build/skbio/util/_testing.py",
line 171, in _assert_frame_equal
npt.assert_almost_equal(left_values, right_values, decimal=decimal)
File "/usr/lib/python3/dist-packages/numpy/testing/_private/utils.py", line
584, in assert_almost_equal
return assert_array_almost_equal(actual, desired, decimal, err_msg)
File "/usr/lib/python3/dist-packages/numpy/testing/_private/utils.py", line
1027, in assert_array_almost_equal
assert_array_compare(compare, x, y, err_msg=err_msg, verbose=verbose,
File "/usr/lib/python3/dist-packages/numpy/testing/_private/utils.py", line
769, in assert_array_compare
flagged = func_assert_same_pos(x, y, func=isnan, hasval='nan')
File "/usr/lib/python3/dist-packages/numpy/testing/_private/utils.py", line
745, in func_assert_same_pos
raise AssertionError(msg)
AssertionError:
Arrays are not almost equal to 7 decimals
x and y nan location mismatch:
x: array([[-2.5170346e-02, -3.8742000e-02, 3.7030794e-02, -1.8248587e-02,
-1.2974103e-03, 8.1410679e-04, -1.7370121e-02, 3.6121106e-02,
nan],...
y: array([[-2.5170346e-02, -3.8742000e-02, 3.7030794e-02, -1.8248587e-02,
