Bug#938909: Dealing with zope.interface unsatisfiable build-dependency.
zope.interface is currently rc buggy because of an unsatisfiable build-depenency on python-zope.event, the package is also orphaned. The package is a key package, so the issue won't be dealt with by autoremovals, furthermore the python-zope.interface package has quite a stack of reverse dependencies, so dropping it doesn't seem like a good option at this point. Testing reveals that the build-dependency in question is only needed by the test suite, so I believe the least-bad option is to drop the build-dependency and not run the testsuite. It would be preferable to only disable the testsuite for python2, but I have no idea how to do that, so my current debdiff disables the testsuite completely, I also ran into an issue with the package's clean target not cleaning up properly. If anyone can suggest how to modify the package so it runs the testsuite for python3 but not python2 that would be appreciated. I plan to go ahead with an upload next week. diff -Nru zope.interface-4.6.0/debian/changelog zope.interface-4.6.0/debian/changelog --- zope.interface-4.6.0/debian/changelog 2019-09-05 11:09:40.0 + +++ zope.interface-4.6.0/debian/changelog 2019-12-07 07:00:43.0 + @@ -1,3 +1,13 @@ +zope.interface (4.6.0-2) unstable; urgency=medium + + * QA upload. + * Drop build-dependency on nonexistent python-zope.event. Downgrades: #938909. + * Disable testsuite, it needs python-zope.event. + * Fix clean target. + * Add build-depends on moreutils, needed by fixed clean target. + + -- Peter Michael Green Sat, 07 Dec 2019 07:00:43 + + zope.interface (4.6.0-1) unstable; urgency=medium * QA upload. diff -Nru zope.interface-4.6.0/debian/control zope.interface-4.6.0/debian/control --- zope.interface-4.6.0/debian/control 2019-09-05 11:09:40.0 + +++ zope.interface-4.6.0/debian/control 2019-12-07 07:00:43.0 + @@ -12,11 +12,11 @@ python-all-dbg:any, python-all-dev:any, python-setuptools, - python-zope.event, python3-all-dbg:any, python3-all-dev:any, python3-setuptools, - python3-zope.event + python3-zope.event, + moreutils Standards-Version: 4.4.0 Testsuite: autopkgtest Homepage: http://pypi.python.org/pypi/zope.interface diff -Nru zope.interface-4.6.0/debian/rules zope.interface-4.6.0/debian/rules --- zope.interface-4.6.0/debian/rules 2016-07-05 21:43:11.0 + +++ zope.interface-4.6.0/debian/rules 2019-12-07 07:00:43.0 + @@ -97,3 +97,10 @@ override_dh_strip: dh_strip -p$(package) --dbg-package=$(package)-dbg dh_strip -p$(package3) --dbg-package=$(package3)-dbg + +override_dh_auto_test: + echo testsuite disabled + +override_dh_auto_clean: + rm -f .eggs/README.txt + rm -f src/zope.interface.egg-info/requires.txt
Bug#920369: marked as done (boost1.62: do not release with buster)
Your message dated Sat, 07 Dec 2019 07:44:13 + with message-id and subject line Bug#946218: Removed package(s) from unstable has caused the Debian Bug report #920369, regarding boost1.62: do not release with buster 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.) -- 920369: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=920369 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: boost1.62 Severity: serious An RC bug to keep boost 1.62 out of testing once we manage to get it out. -- regards, Mattia Rizzolo GPG Key: 66AE 2B4A FCCF 3F52 DA18 4D18 4B04 3FCD B944 4540 .''`. more about me: https://mapreri.org : :' : Launchpad user: https://launchpad.net/~mapreri `. `'` Debian QA page: https://qa.debian.org/developer.php?login=mattia `- signature.asc Description: PGP signature --- End Message --- --- Begin Message --- Version: 1.62.0+dfsg-10+rm Dear submitter, as the package boost1.62 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/946218 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#914043: marked as done (boost-defaults breaks boost1.62 autopkgtest)
Your message dated Sat, 07 Dec 2019 07:44:13 + with message-id and subject line Bug#946218: Removed package(s) from unstable has caused the Debian Bug report #914043, regarding boost-defaults breaks boost1.62 autopkgtest 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.) -- 914043: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=914043 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: boost-defaults, boost1.62 Control: found -1 boost-defaults/1.67.0.1 Control: found -1 boost1.62/1.62.0+dfsg-10 X-Debbugs-CC: debian...@lists.debian.org User: debian...@lists.debian.org Usertags: breaks needs-update Dear maintainers, With a recent upload of boost-defaults the autopkgtest of boost1.62 fails in testing when that autopkgtest is run with the binary packages of boost-defaults from unstable. It passes when run with only packages from testing. In tabular form: passfail boost-defaults from testing1.67.0.1 boost1.62 from testing1.62.0+dfsg-10 versioned deps [0] from testingfrom unstable all others from testingfrom testing I copied some of the output at the bottom of this report. Currently this regression is contributing to the delay of the migration of boost-defaults to testing [1]. Due to the nature of this issue, I filed this bug report against both packages. Can you please investigate the situation and reassign the bug to the right package? If needed, please change the bug's severity. More information about this bug and the reason for filing it can be found on https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation Paul [0] You can see what packages were added by searching for "unstable/main" in the log. [1] https://qa.debian.org/excuses.php?package=boost-defaults https://ci.debian.net/data/autopkgtest/testing/amd64/b/boost1.62/1330119/log.gz [ 25%] Building CXX object CMakeFiles/demo1.dir/demo1.cpp.o /tmp/tmp.olreDv9k9y/src/demo1.cpp:14:24: error: ‘unbounded_channel’ in namespace ‘boost::fibers’ does not name a template type typedef boost::fibers::unbounded_channel fifo_t; ^ /tmp/tmp.olreDv9k9y/src/demo1.cpp:14:9: note: suggested alternative: ‘unbuffered_channel’ typedef boost::fibers::unbounded_channel fifo_t; ^ unbuffered_channel /tmp/tmp.olreDv9k9y/src/demo1.cpp:16:18: error: variable or field ‘ping’ declared void inline void ping(fifo_t _buf, fifo_t _buf) ^~ /tmp/tmp.olreDv9k9y/src/demo1.cpp:16:18: error: ‘fifo_t’ was not declared in this scope /tmp/tmp.olreDv9k9y/src/demo1.cpp:16:18: note: suggested alternative: ‘ino_t’ inline void ping(fifo_t _buf, fifo_t _buf) ^~ ino_t /tmp/tmp.olreDv9k9y/src/demo1.cpp:16:26: error: ‘recv_buf’ was not declared in this scope inline void ping(fifo_t _buf, fifo_t _buf) ^~~~ /tmp/tmp.olreDv9k9y/src/demo1.cpp:16:26: note: suggested alternative: ‘setvbuf’ inline void ping(fifo_t _buf, fifo_t _buf) ^~~~ setvbuf /tmp/tmp.olreDv9k9y/src/demo1.cpp:16:36: error: ‘fifo_t’ was not declared in this scope inline void ping(fifo_t _buf, fifo_t _buf) ^~ /tmp/tmp.olreDv9k9y/src/demo1.cpp:16:36: note: suggested alternative: ‘ino_t’ inline void ping(fifo_t _buf, fifo_t _buf) ^~ ino_t /tmp/tmp.olreDv9k9y/src/demo1.cpp:16:44: error: ‘send_buf’ was not declared in this scope inline void ping(fifo_t _buf, fifo_t _buf) ^~~~ /tmp/tmp.olreDv9k9y/src/demo1.cpp:16:44: note: suggested alternative: ‘setvbuf’ inline void ping(fifo_t _buf, fifo_t _buf) ^~~~ setvbuf /tmp/tmp.olreDv9k9y/src/demo1.cpp:40:18: error: variable or field ‘pong’ declared void inline void pong(fifo_t _buf, fifo_t _buf) ^~ /tmp/tmp.olreDv9k9y/src/demo1.cpp:40:18: error: ‘fifo_t’ was not declared in this scope /tmp/tmp.olreDv9k9y/src/demo1.cpp:40:18: note: suggested alternative: ‘ino_t’ inline void pong(fifo_t _buf, fifo_t _buf) ^~ ino_t /tmp/tmp.olreDv9k9y/src/demo1.cpp:40:26: error: ‘recv_buf’ was not declared in this scope inline void pong(fifo_t _buf, fifo_t _buf) ^~~~ /tmp/tmp.olreDv9k9y/src/demo1.cpp:40:26: note: suggested
Bug#885364: marked as done (pybootchartgui: Depends on unmaintained pygtk)
Your message dated Sat, 07 Dec 2019 07:38:37 + with message-id and subject line Bug#946113: Removed package(s) from unstable has caused the Debian Bug report #885364, regarding pybootchartgui: 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.) -- 885364: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=885364 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: pybootchartgui Version: 0.14.4-3 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 (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.14.4-3.1+rm Dear submitter, as the package bootchart2 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/946113 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#944775: marked as done (FTBFS with CGAL 5.0)
Your message dated Sat, 07 Dec 2019 07:39:35 + with message-id and subject line Bug#946134: Removed package(s) from unstable has caused the Debian Bug report #944775, regarding FTBFS with CGAL 5.0 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 944775: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=944775 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: pprepair Version: 0.0~20170614-dd91a21-3+b1 Severity: important Tags: upstream Hi, pprepair fails to build with CGAL 5.0 in experimental since it uses features that have been removed in CGAL 5.0. See first item under "2D Triangulations" at https://www.cgal.org/2019/10/31/cgal50-beta2/ . Upstream bug: https://github.com/tudelft3d/pprepair/issues/55 Severity important for now, will be increased once the transition starts. Regards, Joachim -- System Information: Debian Release: 10.1 APT prefers stable-debug APT policy: (800, 'stable-debug'), (800, 'stable'), (700, 'testing-debug'), (700, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.19.0-6-amd64 (SMP w/4 CPU cores) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages pprepair depends on: pn gdal-abi-2-4-0 ii libc6 2.28-10 ii libcgal13 4.14-2~deb10u1 ii libgcc1 1:8.3.0-6 pn libgdal20 ii libgmp102:6.1.2+dfsg-4 ii libgmpxx4ldbl 2:6.1.2+dfsg-4 ii libmpfr64.0.2-1 ii libstdc++6 8.3.0-6 Versions of packages pprepair recommends: pn prepair pprepair suggests no packages. --- End Message --- --- Begin Message --- Version: 0.0~20170614-dd91a21-3+rm Dear submitter, as the package pprepair 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/946134 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#946030: marked as done (xul-ext-firetray classified as a legacy extension by Thunderbird 68.2.2 (Debian Stable AMD64))
Your message dated Sat, 07 Dec 2019 07:38:10 + with message-id and subject line Bug#946081: Removed package(s) from unstable has caused the Debian Bug report #946030, regarding xul-ext-firetray classified as a legacy extension by Thunderbird 68.2.2 (Debian Stable AMD64) 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.) -- 946030: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=946030 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: xul-ext-firetray Version: 0.6.1+dfsg-1.2 Maintainer: Debian Mozilla Extension Maintainers < pkg-mozext-maintain...@lists.alioth.debian.org> Provides: firetray, icedove-firetray, thunderbird-firetray Depends: thunderbird (>= 1:57.0) | icedove (>= 1:57.0) Enhances: icedove, thunderbird Breaks: icedove (<< 1:57.0), thunderbird (<< 1:57.0) Description-en: system tray extension for Thunderbird FireTray is a system tray extension for Thunderbird. It supports setting up a custom icon, hiding to the tray instead of closing, displaying the number of unread mails, and more. FireFox and versions of Thunderbird prior to 57 are no longer supported. Description of the incorrect behavior: xul-ext-firetray used to work with Thunderbird However, there is a recent security update to Thunderbird - the updated Thunderbird classifies the current xul-ext-firetray as a legacy extension and causes it to stop working. For your review and update please. --- End Message --- --- Begin Message --- Version: 0.6.1+dfsg-1.2+rm Dear submitter, as the package firetray 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/946081 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#936228: marked as done (bootchart2: Python2 removal in sid/bullseye)
Your message dated Sat, 07 Dec 2019 07:38:37 + with message-id and subject line Bug#946113: Removed package(s) from unstable has caused the Debian Bug report #936228, regarding bootchart2: 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.) -- 936228: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=936228 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:bootchart2 Version: 0.14.4-3 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:bootchart2 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.14.4-3.1+rm Dear submitter, as the package bootchart2 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/946113 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#944776: marked as done (FTBFS with CGAL 5.0)
Your message dated Sat, 07 Dec 2019 07:39:11 + with message-id and subject line Bug#946133: Removed package(s) from unstable has caused the Debian Bug report #944776, regarding FTBFS with CGAL 5.0 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 944776: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=944776 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: prepair Version: 0.7.1-3+b2 Severity: important Tags: upstream Hi, prepair fails to build with CGAL 5.0 in experimental since it uses features that have been removed in CGAL 5.0. See first item under "2D Triangulations" at https://www.cgal.org/2019/10/31/cgal50-beta2/ . Upstream bug: https://github.com/tudelft3d/prepair/issues/35 Severity important for now, will be increased to RC once the transition starts. Regards, Joachim -- System Information: Debian Release: 10.1 APT prefers stable-debug APT policy: (800, 'stable-debug'), (800, 'stable'), (700, 'testing-debug'), (700, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.19.0-6-amd64 (SMP w/4 CPU cores) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) --- End Message --- --- Begin Message --- Version: 0.7.1-3+rm Dear submitter, as the package prepair 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/946133 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#945796: marked as done (rust-url-serde: (build-)depends on obsolete virtual package.)
Your message dated Sat, 07 Dec 2019 07:36:09 + with message-id and subject line Bug#945959: Removed package(s) from unstable has caused the Debian Bug report #945796, regarding rust-url-serde: (build-)depends on obsolete virtual 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.) -- 945796: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=945796 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: rust-url-serde Version: 0.2.0-1 Severity: serious Tags: bullseye, sid librust-url-serde-dev depends on and rust-url-serde build-depends on librust-url-1+default-dev which is no longer provided by rust-url. It seems to have been replaced by librust-url-2+default-dev --- End Message --- --- Begin Message --- Version: 0.2.0-1+rm Dear submitter, as the package rust-url-serde 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/945959 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#937005: marked as done (meep-mpich2: Python2 removal in sid/bullseye)
Your message dated Sat, 07 Dec 2019 07:34:37 + with message-id and subject line Bug#945937: Removed package(s) from unstable has caused the Debian Bug report #937005, regarding meep-mpich2: 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.) -- 937005: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=937005 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:meep-mpich2 Version: 1.7.0-3 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:meep-mpich2 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: 1.7.0-3+rm Dear submitter, as the package meep-mpich2 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/945937 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#943070: marked as done (inosync: Python2 removal in sid/bullseye)
Your message dated Sat, 07 Dec 2019 07:36:55 + with message-id and subject line Bug#945990: Removed package(s) from unstable has caused the Debian Bug report #943070, regarding inosync: 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.) -- 943070: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=943070 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: inosync Version: 0.2.3+git20120321-6 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 (the specific reason can be found searching this source package in https://people.debian.org/~morph/mass-bug-py2removal_take2.txt ). 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 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.2.3+git20120321-6+rm Dear submitter, as the package inosync 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/945990 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#936221: marked as done (blueproximity: Python2 removal in sid/bullseye)
Your message dated Sat, 07 Dec 2019 07:37:21 + with message-id and subject line Bug#946015: Removed package(s) from unstable has caused the Debian Bug report #936221, regarding blueproximity: 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.) -- 936221: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=936221 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:blueproximity Version: 1.2.5-6 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:blueproximity 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: 1.2.5-6+rm Dear submitter, as the package blueproximity 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/946015 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#885139: marked as done (blueproximity: Depends on unmaintained pygtk)
Your message dated Sat, 07 Dec 2019 07:37:21 + with message-id and subject line Bug#946015: Removed package(s) from unstable has caused the Debian Bug report #885139, regarding blueproximity: 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.) -- 885139: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=885139 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: blueproximity Version: 1.2.5-6 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: 1.2.5-6+rm Dear submitter, as the package blueproximity 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/946015 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#941877: marked as done (volti: Depends on unmaintained pygtk)
Your message dated Sat, 07 Dec 2019 07:35:44 + with message-id and subject line Bug#945946: Removed package(s) from unstable has caused the Debian Bug report #941877, regarding volti: 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.) -- 941877: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=941877 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: volti Version: 0.2.3-7 Severity: serious Control: block 885135 by -1 User: pkg-gnome-maintain...@lists.alioth.debian.org Usertags: oldlibs pygtk Tags: sid bullseye pygtk is unmaintained upstream. It has not had a release since GNOME 3 was released in 2011. Also, it uses Python2 and Python2 is being removed from Debian. 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 Debian 11 "Bullseye" release as we're going 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.2.3-7+rm Dear submitter, as the package volti 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/945946 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#937004: marked as done (meep-lam4: Python2 removal in sid/bullseye)
Your message dated Sat, 07 Dec 2019 07:35:08 + with message-id and subject line Bug#945938: Removed package(s) from unstable has caused the Debian Bug report #937004, regarding meep-lam4: 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.) -- 937004: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=937004 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:meep-lam4 Version: 1.7.0-3 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:meep-lam4 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: 1.7.0-3+rm Dear submitter, as the package meep-lam4 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/945938 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#938799: marked as done (volti: Python2 removal in sid/bullseye)
Your message dated Sat, 07 Dec 2019 07:35:44 + with message-id and subject line Bug#945946: Removed package(s) from unstable has caused the Debian Bug report #938799, regarding volti: 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.) -- 938799: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=938799 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:volti Version: 0.2.3-7 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:volti 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.2.3-7+rm Dear submitter, as the package volti 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/945946 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#938463: marked as done (selectors34: Python2 removal in sid/bullseye)
Your message dated Sat, 07 Dec 2019 07:32:11 + with message-id and subject line Bug#945895: Removed package(s) from unstable has caused the Debian Bug report #938463, regarding selectors34: 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.) -- 938463: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=938463 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:selectors34 Version: 1.2.0-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:selectors34 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: 1.2.0-1+rm Dear submitter, as the package selectors34 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/945895 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#936894: marked as done (libmpikmeans: Python2 removal in sid/bullseye)
Your message dated Sat, 07 Dec 2019 07:33:44 + with message-id and subject line Bug#945856: Removed package(s) from unstable has caused the Debian Bug report #936894, regarding libmpikmeans: 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.) -- 936894: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=936894 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:libmpikmeans Version: 1.5+dfsg-7 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:libmpikmeans 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: 1.5+dfsg-8+rm Dear submitter, as the package libmpikmeans 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/945856 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#937433: marked as done (pyevolve: Python2 removal in sid/bullseye)
Your message dated Sat, 07 Dec 2019 07:33:13 + with message-id and subject line Bug#945855: Removed package(s) from unstable has caused the Debian Bug report #937433, regarding pyevolve: 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.) -- 937433: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=937433 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:pyevolve Version: 0.6+git20151103.589b6a9-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:pyevolve 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.6+git20151103.589b6a9-2+rm Dear submitter, as the package pyevolve 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/945855 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#936689: marked as done (hachoir-subfile: Python2 removal in sid/bullseye)
Your message dated Sat, 07 Dec 2019 07:27:33 + with message-id and subject line Bug#945805: Removed package(s) from unstable has caused the Debian Bug report #936689, regarding hachoir-subfile: 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.) -- 936689: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=936689 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:hachoir-subfile Version: 0.5.3-3 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:hachoir-subfile 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.5.3-3+rm Dear submitter, as the package hachoir-subfile 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/945805 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#936691: marked as done (hachoir-wx: Python2 removal in sid/bullseye)
Your message dated Sat, 07 Dec 2019 07:28:33 + with message-id and subject line Bug#945803: Removed package(s) from unstable has caused the Debian Bug report #936691, regarding hachoir-wx: 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.) -- 936691: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=936691 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:hachoir-wx Version: 0.3-3 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:hachoir-wx 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.3-3+rm Dear submitter, as the package hachoir-wx 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/945803 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#936686: marked as done (hachoir-metadata: Python2 removal in sid/bullseye)
Your message dated Sat, 07 Dec 2019 07:29:56 + with message-id and subject line Bug#945799: Removed package(s) from unstable has caused the Debian Bug report #936686, regarding hachoir-metadata: 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.) -- 936686: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=936686 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:hachoir-metadata Version: 1.3.3-2 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:hachoir-metadata 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: 1.3.3-2+rm Dear submitter, as the package hachoir-metadata 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/945799 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#942191: marked as done (Depends on qt4)
Your message dated Sat, 07 Dec 2019 07:29:56 + with message-id and subject line Bug#945799: Removed package(s) from unstable has caused the Debian Bug report #942191, regarding Depends on qt4 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.) -- 942191: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=942191 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: hachoir-metadata Severity: serious hachoir-metadata build-depends on python-qt4, which is being removed from the archive along with Qt4 soon. Cheers, Moritz --- End Message --- --- Begin Message --- Version: 1.3.3-2+rm Dear submitter, as the package hachoir-metadata 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/945799 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#913597: marked as done (polyorb depends and build depends on gnat-7)
Your message dated Sat, 07 Dec 2019 07:31:09 + with message-id and subject line Bug#946286: Removed package(s) from unstable has caused the Debian Bug report #913597, regarding polyorb depends and build depends on gnat-7 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.) -- 913597: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=913597 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: polyorb Version: 2.11~20140418-5 Severity: serious polyorb depends and build depends on gnat-7, please update to gnat-8. --- End Message --- --- Begin Message --- Version: 2.11~20140418-5+rm Dear submitter, as the package polyorb 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/946286 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#936972: marked as done (lunch: Python2 removal in sid/bullseye)
Your message dated Sat, 07 Dec 2019 07:25:38 + with message-id and subject line Bug#945844: Removed package(s) from unstable has caused the Debian Bug report #936972, regarding lunch: 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.) -- 936972: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=936972 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:lunch Version: 0.4.0-2 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:lunch 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.4.0-2+rm Dear submitter, as the package lunch 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/945844 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#885513: marked as done (python-lunch: Recommends unmaintained pygtk)
Your message dated Sat, 07 Dec 2019 07:25:38 + with message-id and subject line Bug#945844: Removed package(s) from unstable has caused the Debian Bug report #885513, regarding python-lunch: Recommends 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.) -- 885513: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=885513 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: lunch Version: 0.4.0-2 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.4.0-2+rm Dear submitter, as the package lunch 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/945844 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#946234: marked as done ([NMU] FTFBS with CGAL 5.0 (if cmake is absent))
Your message dated Sat, 07 Dec 2019 06:49:07 + with message-id and subject line Bug#946234: fixed in pygalmesh 0.5.0-1 has caused the Debian Bug report #946234, regarding [NMU] FTFBS with CGAL 5.0 (if cmake is absent) 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.) -- 946234: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=946234 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: pygalmesh Version: 0.4.0-1 Severity: serious Tags: ftbfs Control: block 944417 by -1 Hi, the transition to CGAL 5.0 started (see bug #944417) and your package FTBFS (if cmake is not present, see the other bug I just filed). I intend to NMU the package with the attached diff to DELAYED/5-day. Best regards, Joachim diff -Nru pygalmesh-0.4.0/debian/changelog pygalmesh-0.4.0/debian/changelog --- pygalmesh-0.4.0/debian/changelog2019-08-18 18:42:35.0 +0200 +++ pygalmesh-0.4.0/debian/changelog2019-12-05 23:07:13.0 +0100 @@ -1,3 +1,11 @@ +pygalmesh (0.4.0-1.1) unstable; urgency=medium + + * Non-maintainer upload. + * Add patch to fix FTBFS with CGAL >= 5.0 (Closes: #xx). + * Add Build-Depends: libcgal-dev (>= 5.0~). + + -- Joachim Reichel Thu, 05 Dec 2019 23:07:13 +0100 + pygalmesh (0.4.0-1) unstable; urgency=medium * set debian/watch to track upstream git tags, diff -Nru pygalmesh-0.4.0/debian/control pygalmesh-0.4.0/debian/control --- pygalmesh-0.4.0/debian/control 2019-08-18 18:42:35.0 +0200 +++ pygalmesh-0.4.0/debian/control 2019-12-05 23:07:13.0 +0100 @@ -5,7 +5,7 @@ Uploaders: Drew Parsons Build-Depends: debhelper-compat (= 12), dh-python, python3-all-dev, python3-setuptools, - libcgal-dev, + libcgal-dev (>= 5.0~), libeigen3-dev, pandoc, python3-meshio, diff -Nru pygalmesh-0.4.0/debian/patches/series pygalmesh-0.4.0/debian/patches/series --- pygalmesh-0.4.0/debian/patches/series 1970-01-01 01:00:00.0 +0100 +++ pygalmesh-0.4.0/debian/patches/series 2019-12-05 23:06:31.0 +0100 @@ -0,0 +1 @@ +use-cgal-in-header-only-mode.patch diff -Nru pygalmesh-0.4.0/debian/patches/use-cgal-in-header-only-mode.patch pygalmesh-0.4.0/debian/patches/use-cgal-in-header-only-mode.patch --- pygalmesh-0.4.0/debian/patches/use-cgal-in-header-only-mode.patch 1970-01-01 01:00:00.0 +0100 +++ pygalmesh-0.4.0/debian/patches/use-cgal-in-header-only-mode.patch 2019-12-05 23:07:13.0 +0100 @@ -0,0 +1,14 @@ +Index: pygalmesh-0.4.0/setup.py +=== +--- pygalmesh-0.4.0.orig/setup.py pygalmesh-0.4.0/setup.py +@@ -48,8 +48,7 @@ ext_modules = [ + get_pybind_include(), + get_pybind_include(user=True), + ], +-# CGAL_ImageIO for generate_from_inr +-libraries=["CGAL", "CGAL_ImageIO", "gmp", "mpfr"], ++libraries=["stdc++", "gmp", "mpfr"], + ) + ] + --- End Message --- --- Begin Message --- Source: pygalmesh Source-Version: 0.5.0-1 We believe that the bug you reported is fixed in the latest version of pygalmesh, 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 946...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Drew Parsons (supplier of updated pygalmesh 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, 07 Dec 2019 14:07:47 +0800 Source: pygalmesh Architecture: source Version: 0.5.0-1 Distribution: unstable Urgency: medium Maintainer: Debian Science Maintainers Changed-By: Drew Parsons Closes: 946234 Changes: pygalmesh (0.5.0-1) unstable; urgency=medium . * New upstream release. - fixes build against CGAL 5. Thanks Joachim Reichel for a patch. Closes: #946234. Checksums-Sha1: ad337736d1467fa2b57739e383f71e2006fda3ea 2172 pygalmesh_0.5.0-1.dsc 971a1c79848411c99feac16badc9645bb294656b 873932 pygalmesh_0.5.0.orig.tar.xz 95a60a78ecd3527fd068973a0592310287cff819 4332 pygalmesh_0.5.0-1.debian.tar.xz Checksums-Sha256: ecdd3f1519b6a0caeeb27cb3691821660fd93bfcf64e593acee9c5806b584b64 2172 pygalmesh_0.5.0-1.dsc 37bc42821e11b842a13b3f20bcca4643bf56fc6de2e1ec036dea5ce79c3114c6
Bug#945501: python-statsmodels-doc: unhandled symlink to directory conversion: /usr/share/doc/python-statsmodels-doc/examples
Should the package attempt to clean this up (and if so is there a better method than unconditionally deleting those directories), or is permanently leaving this behind (to become more and more obsolete, and potentially be read by users looking for the current documentation) the best that can be safely done? Personally, I would be tempted to add the cleanup code, then remove it again in a couple of months. That should clean up the majority of systems, while not leaving aggressive cleanup code in a stable release.
Processed: re: html5-parser: Python2 removal in sid/bullseye
Processing commands for cont...@bugs.debian.org:
> reopen 936710
Bug #936710 {Done: Norbert Preining } [src:html5-parser]
html5-parser: Python2 removal in sid/bullseye
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
No longer marked as fixed in versions html5-parser/0.4.9-2.
> severity 936710 normal
Bug #936710 [src:html5-parser] html5-parser: Python2 removal in sid/bullseye
Severity set to 'normal' from 'serious'
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
936710: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=936710
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#936710: html5-parser: Python2 removal in sid/bullseye
reopen 936710 severity 936710 normal thanks Thank you for fixing the rc aspect of this issue, reopening and downgrading for the broader issue.
Processed: re: dulwich: Python2 removal in sid/bullseye
Processing commands for cont...@bugs.debian.org: > severity 936454 serious Bug #936454 [src:dulwich] dulwich: Python2 removal in sid/bullseye Severity set to 'serious' from 'normal' > thanks Stopping processing here. Please contact me if you need assistance. -- 936454: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=936454 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: tagging 938793, tagging 936274, tagging 936558, tagging 936736, tagging 938600, tagging 946289
Processing commands for cont...@bugs.debian.org:
> tags 938793 + experimental
Bug #938793 {Done: Balint Reczey }
[src:vmdk-stream-converter] vmdk-stream-converter: Python2 removal in
sid/bullseye
Added tag(s) experimental.
> tags 936274 + experimental
Bug #936274 {Done: Ole Streicher } [src:casacore] casacore:
Python2 removal in sid/bullseye
Added tag(s) experimental.
> tags 936558 + experimental
Bug #936558 {Done: Bernhard Schmidt } [src:freeradius]
freeradius: Python2 removal in sid/bullseye
Added tag(s) experimental.
> tags 936736 + experimental
Bug #936736 {Done: Changwoo Ryu } [src:input-pad] input-pad:
Python2 removal in sid/bullseye
Added tag(s) experimental.
> tags 938600 + experimental
Bug #938600 {Done: Changwoo Ryu } [src:sunpinyin] sunpinyin:
Python2 removal in sid/bullseye
Added tag(s) experimental.
> tags 946289 + sid bullseye
Bug #946289 [ufw] ufw: fails to start with iptables 1.8.4
Added tag(s) bullseye and sid.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
936274: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=936274
936558: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=936558
936736: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=936736
938600: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=938600
938793: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=938793
946289: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=946289
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#946293: marked as done (Dependency problems between espeakup-udeb and espeak-ng-data-udeb breaking d-i builds)
Your message dated Fri, 6 Dec 2019 23:53:11 +0100 with message-id <20191206225311.blgui4anrotrpr7f@function> and subject line Re: Bug#946293: Dependency problems between espeakup-udeb and espeak-ng-data-udeb breaking d-i builds has caused the Debian Bug report #946293, regarding Dependency problems between espeakup-udeb and espeak-ng-data-udeb breaking d-i builds 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.) -- 946293: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=946293 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: espeakup Version: 1:0.80-16 Severity: serious Tags: d-i Hi Samuel, There's a problem with dependencies that's causing d-i to fail to build, as seen in the end of the log at: https://d-i.debian.org/daily-images/amd64/20191206-00:05/build_cdrom_gtk.log ... Reading package lists... Building dependency tree... espeakup-udeb:amd64 Depends on espeak-ng-data-udeb:amd64 < none -> 1.50+dfsg-4 @un puN > (< 1.49.2+dfsgA) can't be satisfied! 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: espeakup-udeb : Depends: espeak-ng-data-udeb (< 1.49.2+dfsgA) but 1.50+dfsg-4 is to be installed E: Unable to correct problems, you have held broken packages. make[2]: *** [Makefile:674: stamps/get_udebs-cdrom_gtk-stamp] Error 100 make[1]: *** [Makefile:298: _build] Error 2 make: *** [Makefile:292: build_cdrom_gtk] Error 2 ... Please could you take a look? -- System Information: Debian Release: 10.2 APT prefers stable-debug APT policy: (500, 'stable-debug'), (500, 'stable'), (500, 'oldstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.19.0-6-amd64 (SMP w/4 CPU cores) Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), LANGUAGE=en_GB:en (charmap=UTF-8) Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages espeakup depends on: pn espeak ii init-system-helpers 1.56+nmu1 ii libc62.28-10 ii libespeak-ng11.49.2+dfsg-8 ii lsb-base 10.2019051400 espeakup recommends no packages. espeakup suggests no packages. --- End Message --- --- Begin Message --- Hello, Paul Gevers, le ven. 06 déc. 2019 21:15:11 +0100, a ecrit: > Yes, it's the auto-upperlimit-espeak-ng-data-udeb.html transition [1]. > I'll schedule the binNMU shortly. Indeed. I wonder if there could be a way to easily remember to add that in transition requests. The rebuilds are now done, so I'm closing this. Thanks! Samuel--- End Message ---
Bug#946311: libpcre2-dev 10.34-5 dependency errors
Package: libpcre2-dev Version: 10.34-5 Severity: grave Tags: a11y Justification: renders package unusable -- System Information: Debian Release: bullseye/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 4.19.0-6-amd64 (SMP w/8 CPU cores) Locale: LANG=ru_RU.utf8, LC_CTYPE=ru_RU.utf8 (charmap=UTF-8), LANGUAGE=ru_RU.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages libpcre2-dev depends on: ii libc6-dev2.29-3 ii libpcre2-16-010.34-5 ii libpcre2-32-010.34-5 ii libpcre2-8-0 10.34-5 pn libpcre2-posix2 libpcre2-dev recommends no packages. libpcre2-dev suggests no packages. -- no debconf information After I installed libpcre2-dev 10.34-5 i get dependency errors for libpcre2-posix2. I get a message: attempt to overwrite "/usr/lib/x86_64-linux-gnu/libpcre2-posix.so. 2. 0. 3" which is already available in package libpcre2-posix 0: amd64 10.34-3+b1 And I have to go back to the previous version 10.34-3+b1.
Bug#944851: closing 944851
close 944851 1.4.18-1 thanks
Processed: closing 944851
Processing commands for cont...@bugs.debian.org: > close 944851 1.4.18-1 Bug #944851 [src:tnef] tnef: CVE-2019-18849 Marked as fixed in versions tnef/1.4.18-1. Bug #944851 [src:tnef] tnef: CVE-2019-18849 Marked Bug as done > thanks Stopping processing here. Please contact me if you need assistance. -- 944851: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=944851 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#941971: marked as done (raspi3-firmware: serial console output sent to bluetooth port with kernel 5.x)
Your message dated Fri, 06 Dec 2019 21:26:56 +
with message-id
and subject line Bug#941971: fixed in raspi-firmware 1.20190819-2
has caused the Debian Bug report #941971,
regarding raspi3-firmware: serial console output sent to bluetooth port with
kernel 5.x
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.)
--
941971: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=941971
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: raspi3-firmware
Version: 1.20190215-1+deb10u1
Severity: critical
Justification: breaks the whole system
I’ve set the severity high because this MIGHT break hardware,
but it it doesn’t (I don’t know enough to judge) feel free to
classify as less critical.
/etc/kernel/postinst.d/z50-raspi3-firmware contains this gem:
90 serial="ttyAMA0,115200"
91 kernelmajor=$(echo "${latest_kernel_basename}" | sed 's,^vmlinuz-,,g' |
cut -d. -f 1)
92 kernelminor=$(echo "${latest_kernel_basename}" | cut -d. -f 2)
93 if [ $kernelmajor -ge 4 ]; then
94 if [ $kernelminor -ge 14 ]; then
95 # Since Linux 4.14, /dev/ttyS1 is the UART on the pinheader.
96 serial="ttyS1,115200"
97 fi
98 fi
The intent is to set serial to ttyAMA0 for Linux << 4.14
and to ttyS1 for Linux >= 4.14, but this fails obviously
using the old location for 5.0‥5.13, 6.0‥6.13, …
You’ll wish to use this instead:
serial="ttyAMA0,115200"
kernelmajmin=$(($(echo $latest_kernel_basename | sed -n \
's/^vmlinu.-\([0-9]*\)\.\([0-9]*\)\..*$/\1*1000+\2/p')))
if test $kernelmajmin -ge 4014; then
# Since Linux 4.14, /dev/ttyS1 is the UART on the pinheader.
serial="ttyS1,115200"
fi
This must be fixed in stable, since the 5.x kernel is in
backports, or at least in unstable and available via backports
and the backports kernel must Breaks the versions prior to this fix.
-- System Information:
Debian Release: 10.1
APT prefers stable-updates
APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: arm64 (aarch64)
Kernel: Linux 5.2.0-0.bpo.2-arm64 (SMP w/4 CPU cores)
Kernel taint flags: TAINT_WARN, TAINT_CRAP
Locale: LANG=C.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=C.UTF-8
(charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)
Versions of packages raspi3-firmware depends on:
ii dosfstools 4.1-2
raspi3-firmware recommends no packages.
raspi3-firmware suggests no packages.
-- Configuration Files:
/etc/default/raspi3-firmware changed:
CMA=128M
-- no debconf information
--- End Message ---
--- Begin Message ---
Source: raspi-firmware
Source-Version: 1.20190819-2
We believe that the bug you reported is fixed in the latest version of
raspi-firmware, 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 941...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Romain Perier (supplier of updated raspi-firmware
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: Thu, 10 Oct 2019 13:18:57 +0200
Source: raspi-firmware
Binary: raspi-firmware raspi3-firmware
Built-For-Profiles: cross nopython nodoc pkg.linux.notools
Architecture: source armhf all
Version: 1.20190819-2
Distribution: unstable
Urgency: medium
Maintainer: pkg-raspi
Changed-By: Romain Perier
Description:
raspi-firmware - Raspberry Pi family GPU firmware and bootloaders
raspi3-firmware - transitional package
Closes: 941971
Changes:
raspi-firmware (1.20190819-2) unstable; urgency=medium
.
* Fix serial console output sent to bluetooth port with kernel 5.x.
Thanks to Thorsten Glaser (Closes: #941971)
Checksums-Sha1:
9b4cb0964bb60aea866026814c89b04871304242 2211 raspi-firmware_1.20190819-2.dsc
8b469408b8e87b551033157415c0e05f1e407363 24396
raspi-firmware_1.20190819-2.debian.tar.xz
674eed2f908c2c049661f23745bf810420491a21 5957
raspi-firmware_1.20190819-2_armhf.buildinfo
2d09271f8ccd18ec1becffe240d59b339a2e3c1b 5713316
raspi-firmware_1.20190819-2_armhf.deb
0bae8a23bd6ecca776dae80f5618dc1e40402bf1 10588
raspi3-firmware_1.20190819-2_all.deb
Checksums-Sha256:
Bug#946306: jsonld-java: FTBFS in sid
Source: jsonld-java Version: 0.13.0-1 Severity: serious Hello, looks like jsonld-java is now FTBFS in sid Can you please have a look? I: Running cd /build/jsonld-java-0.13.0/ && env PATH="/usr/sbin:/usr/bin:/sbin:/bin" HOME="/nonexistent" dpkg-buildpackage -us -uc dpkg-buildpackage: info: source package jsonld-java dpkg-buildpackage: info: source version 0.13.0-1 dpkg-buildpackage: info: source distribution unstable dpkg-buildpackage: info: source changed by Andrius Merkys dpkg-source --before-build . dpkg-buildpackage: info: host architecture amd64 debian/rules clean dh clean dh_auto_clean bash -c "for dir in \$(find . -name target -type d); do if [ -f \$(echo \$dir | sed -e s/target\$/pom.xml/) ]; then rm -Rf \$dir; fi done" mh_unpatchpoms -plibjsonld-java dh_clean dpkg-source -b . dpkg-source: info: using source format '3.0 (quilt)' dpkg-source: info: building jsonld-java using existing ./jsonld-java_0.13.0.orig.tar.xz dpkg-source: info: using patch list from debian/patches/series dpkg-source: info: building jsonld-java in jsonld-java_0.13.0-1.debian.tar.xz dpkg-source: info: building jsonld-java in jsonld-java_0.13.0-1.dsc debian/rules binary dh binary dh_update_autotools_config dh_autoreconf dh_auto_configure mh_patchpoms -plibjsonld-java --debian-build --keep-pom-version --maven-repo=/build/jsonld-java-0.13.0/debian/maven-repo dh_auto_build /usr/lib/jvm/default-java/bin/java -noverify -cp /usr/share/maven/boot/plexus-classworlds-2.x.jar -Dmaven.home=/usr/share/maven -Dmaven.multiModuleProjectDirectory=/build/jsonld-java-0.13.0 -Dclassworlds.conf=/etc/maven/m2-debian.conf -Dproperties.file.manual=/build/jsonld-java-0.13.0/debian/maven.properties org.codehaus.plexus.classworlds.launcher.Launcher -s/etc/maven/settings-debian.xml -Ddebian.dir=/build/jsonld-java-0.13.0/debian -Dmaven.repo.local=/build/jsonld-java-0.13.0/debian/maven-repo package -DskipTests -Dnotimestamp=true -Dlocale=en_US WARNING: An illegal reflective access operation has occurred WARNING: Illegal reflective access by com.google.inject.internal.cglib.core.$ReflectUtils$1 (file:/usr/share/maven/lib/guice.jar) to method java.lang.ClassLoader.defineClass(java.lang.String,byte[],int,int,java.security.ProtectionDomain) WARNING: Please consider reporting this to the maintainers of com.google.inject.internal.cglib.core.$ReflectUtils$1 WARNING: Use --illegal-access=warn to enable warnings of further illegal reflective access operations WARNING: All illegal access operations will be denied in a future release [INFO] Scanning for projects... [WARNING] [WARNING] Some problems were encountered while building the effective model for com.github.jsonld-java:jsonld-java:bundle:0.13.0 [WARNING] 'dependencyManagement.dependencies.dependency.(groupId:artifactId:type:classifier)' must be unique: org.apache.httpcomponents:httpclient:jar -> duplicate declaration of version debian @ com.github.jsonld-java:jsonld-java-parent:0.13.0, /build/jsonld-java-0.13.0/pom.xml, line 121, column 16 [WARNING] [WARNING] Some problems were encountered while building the effective model for com.github.jsonld-java:jsonld-java-parent:pom:0.13.0 [WARNING] 'dependencyManagement.dependencies.dependency.(groupId:artifactId:type:classifier)' must be unique: org.apache.httpcomponents:httpclient:jar -> duplicate declaration of version debian @ line 121, column 16 [WARNING] [WARNING] It is highly recommended to fix these problems because they threaten the stability of your build. [WARNING] [WARNING] For this reason, future Maven versions might no longer support building such malformed projects. [WARNING] [INFO] [INFO] Reactor Build Order: [INFO] [INFO] JSONLD Java :: Parent [pom] [INFO] JSONLD Java :: Core [bundle] [INFO] [INFO] -< com.github.jsonld-java:jsonld-java-parent >-- [INFO] Building JSONLD Java :: Parent 0.13.0 [1/2] [INFO] [ pom ]- [INFO] [INFO] -< com.github.jsonld-java:jsonld-java >- [INFO] Building JSONLD Java :: Core 0.13.0[2/2] [INFO] ---[ bundle ]--- [INFO] [INFO] --- maven-resources-plugin:3.1.0:resources (default-resources) @ jsonld-java --- [INFO] Using 'UTF-8' encoding to copy filtered resources. [INFO] skip non existing resourceDirectory /build/jsonld-java-0.13.0/core/src/main/resources [INFO] [INFO] --- maven-compiler-plugin:3.8.1:compile (default-compile) @ jsonld-java --- [INFO] Changes detected - recompiling the module! [INFO] Compiling 23 source files to /build/jsonld-java-0.13.0/core/target/classes [INFO]
Bug#921220: marked as done (xchat.desktop makes invalid use of %U, breaks at least lxqt and flwm)
Your message dated Fri, 06 Dec 2019 20:41:01 + with message-id and subject line Bug#921220: fixed in xchat 2.8.8-18 has caused the Debian Bug report #921220, regarding xchat.desktop makes invalid use of %U, breaks at least lxqt and flwm 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.) -- 921220: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=921220 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: xchat Version: 2.8.8-17 xchat when launched from lxqt menu does not autoconnect any more, showing only the following. Python interface loaded Tcl plugin for XChat - Version 1.64 Copyright 2002-2005 Daniel P. Stasinski http://www.scriptkitties.com/tclplugin/ Tcl interface loaded Perl interface loaded * Recherche de %U * Hôte inconnu. Peut-être avez vous fait une faute de frappe ? OTOH when launched from cmdline the problem does not appear. And indeed the provided .desktop file shows: Exec=sh -c "xchat --existing --url %U || exec xchat" Could it be that there was a fix in a recently-dropped patch ? --- End Message --- --- Begin Message --- Source: xchat Source-Version: 2.8.8-18 We believe that the bug you reported is fixed in the latest version of xchat, 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 921...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Gianfranco Costamagna (supplier of updated xchat package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Fri, 06 Dec 2019 20:53:59 +0100 Source: xchat Binary: xchat xchat-common Architecture: source Version: 2.8.8-18 Distribution: unstable Urgency: medium Maintainer: Gianfranco Costamagna Changed-By: Gianfranco Costamagna Description: xchat - IRC client for X similar to AmIRC xchat-common - Common files for X-Chat Closes: 921220 Changes: xchat (2.8.8-18) unstable; urgency=medium . * Tweak desktop patch to fix load of %U parameters on some more strict DE configurations (Closes: #921220) - thanks ydir...@free.fr for the hint! Checksums-Sha1: 7a5b42e0117299a64ac709d53c8b1cd52aceb8bb 1916 xchat_2.8.8-18.dsc b7a513bfc3c199d1ad137a5e4830ddf911cc7a56 96784 xchat_2.8.8-18.debian.tar.xz f2d081fad1eb11ceba06cbbcff5352b541d3d9a5 14260 xchat_2.8.8-18_source.buildinfo Checksums-Sha256: c00a0edeec3e39b98aa5eb9b074591b6f60ff16bead642009d33ad5ccaa7e2b5 1916 xchat_2.8.8-18.dsc eba4f78b5a55cadfd887fa45f8225ea33f231575b5a55124fac89a99083ec5e6 96784 xchat_2.8.8-18.debian.tar.xz af5d8e94f3d26b621f0006dab77f76472a863d2b51d2ca7a997264bd78f55471 14260 xchat_2.8.8-18_source.buildinfo Files: 66f6e04a069572f84fd319e479bb530c 1916 net optional xchat_2.8.8-18.dsc 1a3de0abfa33024d2369b5f0d558ce57 96784 net optional xchat_2.8.8-18.debian.tar.xz 3ff599901e65841567b7bcb20c296deb 14260 net optional xchat_2.8.8-18_source.buildinfo -BEGIN PGP SIGNATURE- iQIyBAEBCAAdFiEEkpeKbhleSSGCX3/w808JdE6fXdkFAl3qskgACgkQ808JdE6f XdkusA/3fsogsu6FjbmRyfPd+ewAUNtghsMv7BJ3joaxLw2TjIymDwbSLBIaC85J r835jszw6P5VrtjgsuI+i5+SC3yGKqADar3OU58AWYRS9dfGytfY5RB2fTd4uSmc FgzjZDxiNiZeE20WuPu7sxvVg7sGEI9S+aABzqdIzlm6knq9pUg+YwA3up+gqcFL MihsS55x5ukghEiLmc/Jj6jsuLMDaJ+A4+7WCfRiNQ+bQ4dnbY1FJfPacBGk5HhB +tzh9QQDNhhsWlQW0ENFkUuRwq6Rt3S7WzlNZtLxc2g1Dzn2RWY5ebiLXMslz8ml GRxNxQv52ewliA4bqpipgJTZ65Cc4wiwdKrNxQUfJzee70VThiliJSNcTfA4mfMg iV0SGUZ6/w/3XhbDytl1wTtn2L/4iJAOQbNUyLgLKBO//1uUR821y7jRu+RFhd7T XDd3dl3yhuI05jRd7YyzOKkl0LO29SLMqKpjamplWuQioSRa+cM5c7pgkvv8vZT/ fF31Aw7l0IQBTzOUCV9AumFPQvlplhRDIPyUaklsi4EylIQtxVdvOdeuiPesfm6B ejfwxzCsHhPMXFd2C4AJT6IbCuminw9MAJZZUp08pD5Uyoik3V0QBOVLFVdA+tIA A4q0lVjTKzcaGdfLHU3i4/YefC2dRK5ZXTWCDq98S65lC+kf1w== =wvEz -END PGP SIGNATURE End Message ---
Bug#946304: jsonpickle: FTBFS in sid
Source: jsonpickle
Version: 0.9.5-2
Severity: serious
Hello, looks like some Python3 updates made the package FTBFS in sid, due to
testsuite errors...
log following:
I: Running cd /build/jsonpickle-0.9.5/ && env
PATH="/usr/sbin:/usr/bin:/sbin:/bin" HOME="/nonexistent" dpkg-buildpackage -us
-uc -rfakeroot
dpkg-buildpackage: info: source package jsonpickle
dpkg-buildpackage: info: source version 0.9.5-2
dpkg-buildpackage: info: source distribution unstable
dpkg-buildpackage: info: source changed by Sandro Tosi
dpkg-source --before-build .
dpkg-buildpackage: info: host architecture amd64
fakeroot debian/rules clean
dh clean --with python3,sphinxdoc --buildsystem=pybuild
dh_auto_clean -O--buildsystem=pybuild
I: pybuild base:217: python3.8 setup.py clean
running clean
removing '/build/jsonpickle-0.9.5/.pybuild/cpython3_3.8/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/jsonpickle-0.9.5/.pybuild/cpython3_3.7/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_clean -O--buildsystem=pybuild
dpkg-source -b .
dpkg-source: info: using source format '3.0 (quilt)'
dpkg-source: info: building jsonpickle using existing
./jsonpickle_0.9.5.orig.tar.gz
dpkg-source: info: using patch list from debian/patches/series
dpkg-source: info: building jsonpickle in jsonpickle_0.9.5-2.debian.tar.xz
dpkg-source: info: building jsonpickle in jsonpickle_0.9.5-2.dsc
debian/rules build
dh build --with python3,sphinxdoc --buildsystem=pybuild
dh_update_autotools_config -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
creating /build/jsonpickle-0.9.5/.pybuild/cpython3_3.8/build/jsonpickle
copying jsonpickle/tags.py ->
/build/jsonpickle-0.9.5/.pybuild/cpython3_3.8/build/jsonpickle
copying jsonpickle/handlers.py ->
/build/jsonpickle-0.9.5/.pybuild/cpython3_3.8/build/jsonpickle
copying jsonpickle/unpickler.py ->
/build/jsonpickle-0.9.5/.pybuild/cpython3_3.8/build/jsonpickle
copying jsonpickle/compat.py ->
/build/jsonpickle-0.9.5/.pybuild/cpython3_3.8/build/jsonpickle
copying jsonpickle/pickler.py ->
/build/jsonpickle-0.9.5/.pybuild/cpython3_3.8/build/jsonpickle
copying jsonpickle/version.py ->
/build/jsonpickle-0.9.5/.pybuild/cpython3_3.8/build/jsonpickle
copying jsonpickle/__init__.py ->
/build/jsonpickle-0.9.5/.pybuild/cpython3_3.8/build/jsonpickle
copying jsonpickle/backend.py ->
/build/jsonpickle-0.9.5/.pybuild/cpython3_3.8/build/jsonpickle
copying jsonpickle/util.py ->
/build/jsonpickle-0.9.5/.pybuild/cpython3_3.8/build/jsonpickle
creating /build/jsonpickle-0.9.5/.pybuild/cpython3_3.8/build/jsonpickle/ext
copying jsonpickle/ext/numpy.py ->
/build/jsonpickle-0.9.5/.pybuild/cpython3_3.8/build/jsonpickle/ext
copying jsonpickle/ext/__init__.py ->
/build/jsonpickle-0.9.5/.pybuild/cpython3_3.8/build/jsonpickle/ext
I: pybuild base:217: /usr/bin/python3 setup.py build
running build
running build_py
creating /build/jsonpickle-0.9.5/.pybuild/cpython3_3.7/build/jsonpickle
copying jsonpickle/tags.py ->
/build/jsonpickle-0.9.5/.pybuild/cpython3_3.7/build/jsonpickle
copying jsonpickle/handlers.py ->
/build/jsonpickle-0.9.5/.pybuild/cpython3_3.7/build/jsonpickle
copying jsonpickle/unpickler.py ->
/build/jsonpickle-0.9.5/.pybuild/cpython3_3.7/build/jsonpickle
copying jsonpickle/compat.py ->
/build/jsonpickle-0.9.5/.pybuild/cpython3_3.7/build/jsonpickle
copying jsonpickle/pickler.py ->
/build/jsonpickle-0.9.5/.pybuild/cpython3_3.7/build/jsonpickle
copying jsonpickle/version.py ->
/build/jsonpickle-0.9.5/.pybuild/cpython3_3.7/build/jsonpickle
copying jsonpickle/__init__.py ->
/build/jsonpickle-0.9.5/.pybuild/cpython3_3.7/build/jsonpickle
copying jsonpickle/backend.py ->
/build/jsonpickle-0.9.5/.pybuild/cpython3_3.7/build/jsonpickle
copying jsonpickle/util.py ->
/build/jsonpickle-0.9.5/.pybuild/cpython3_3.7/build/jsonpickle
creating /build/jsonpickle-0.9.5/.pybuild/cpython3_3.7/build/jsonpickle/ext
copying jsonpickle/ext/numpy.py ->
/build/jsonpickle-0.9.5/.pybuild/cpython3_3.7/build/jsonpickle/ext
copying jsonpickle/ext/__init__.py ->
/build/jsonpickle-0.9.5/.pybuild/cpython3_3.7/build/jsonpickle/ext
debian/rules override_dh_auto_test
make[1]: Entering directory '/build/jsonpickle-0.9.5'
PYBUILD_SYSTEM=custom \
PYBUILD_TEST_ARGS="PYTHONPATH={build_dir} {interpreter} tests/runtests.py"
dh_auto_test
I: pybuild base:217:
PYTHONPATH=/build/jsonpickle-0.9.5/.pybuild/cpython3_3.8/build python3.8
tests/runtests.py
/build/jsonpickle-0.9.5/tests/backend_test.py:103: UserWarning:
Bug#946293: Dependency problems between espeakup-udeb and espeak-ng-data-udeb breaking d-i builds
Control: tags -1 pending Hi, Yes, it's the auto-upperlimit-espeak-ng-data-udeb.html transition [1]. I'll schedule the binNMU shortly. Paul [1] https://release.debian.org/transitions/html/auto-upperlimit-espeak-ng-data-udeb.html On 06-12-2019 19:56, Steve McIntyre wrote: > Package: espeakup > Version: 1:0.80-16 > Severity: serious > Tags: d-i > > Hi Samuel, > > There's a problem with dependencies that's causing d-i to fail to > build, as seen in the end of the log at: > > https://d-i.debian.org/daily-images/amd64/20191206-00:05/build_cdrom_gtk.log > > ... > Reading package lists... > Building dependency tree... > espeakup-udeb:amd64 Depends on espeak-ng-data-udeb:amd64 < none -> > 1.50+dfsg-4 @un puN > (< 1.49.2+dfsgA) can't be satisfied! > 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: > espeakup-udeb : Depends: espeak-ng-data-udeb (< 1.49.2+dfsgA) but > 1.50+dfsg-4 is to be installed > E: Unable to correct problems, you have held broken packages. > make[2]: *** [Makefile:674: stamps/get_udebs-cdrom_gtk-stamp] Error 100 > make[1]: *** [Makefile:298: _build] Error 2 > make: *** [Makefile:292: build_cdrom_gtk] Error 2 > ... > > Please could you take a look? > > -- System Information: > Debian Release: 10.2 > APT prefers stable-debug > APT policy: (500, 'stable-debug'), (500, 'stable'), (500, 'oldstable') > Architecture: amd64 (x86_64) > Foreign Architectures: i386 > > Kernel: Linux 4.19.0-6-amd64 (SMP w/4 CPU cores) > Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE > Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), > LANGUAGE=en_GB:en (charmap=UTF-8) > Shell: /bin/sh linked to /usr/bin/dash > Init: systemd (via /run/systemd/system) > LSM: AppArmor: enabled > > Versions of packages espeakup depends on: > pn espeak > ii init-system-helpers 1.56+nmu1 > ii libc62.28-10 > ii libespeak-ng11.49.2+dfsg-8 > ii lsb-base 10.2019051400 > > espeakup recommends no packages. > > espeakup suggests no packages. > signature.asc Description: OpenPGP digital signature
Processed: Re: Bug#946293: Dependency problems between espeakup-udeb and espeak-ng-data-udeb breaking d-i builds
Processing control commands: > tags -1 pending Bug #946293 [espeakup] Dependency problems between espeakup-udeb and espeak-ng-data-udeb breaking d-i builds Added tag(s) pending. -- 946293: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=946293 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#946238: marked as done (openstack-dashboard-apache: modifies conffiles (policy 10.7.3): /etc/openstack-dashboard/local_settings.d/_0005_debian_webroot.py)
Your message dated Fri, 06 Dec 2019 18:35:12 + with message-id and subject line Bug#946238: fixed in horizon 3:16.0.0-3 has caused the Debian Bug report #946238, regarding openstack-dashboard-apache: modifies conffiles (policy 10.7.3): /etc/openstack-dashboard/local_settings.d/_0005_debian_webroot.py 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.) -- 946238: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=946238 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: openstack-dashboard-apache Version: 3:16.0.0-2 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Control: affects -1 + openstack-dashboard Hi, during a test with piuparts I noticed your package modifies conffiles. This is forbidden by the policy, see https://www.debian.org/doc/debian-policy/ch-files.html#configuration-files 10.7.3: "[...] The easy way to achieve this behavior is to make the configuration file a conffile. [...] This implies that the default version will be part of the package distribution, and must not be modified by the maintainer scripts during installation (or at any other time)." Note that once a package ships a modified version of that conffile, dpkg will prompt the user for an action how to handle the upgrade of this modified conffile (that was not modified by the user). Further in 10.7.3: "[...] must not ask unnecessary questions (particularly during upgrades) [...]" If a configuration file is customized by a maintainer script after having asked some debconf questions, it may not be marked as a conffile. Instead a template could be installed in /usr/share and used by the postinst script to fill in the custom values and create (or update) the configuration file (preserving any user modifications!). This file must be removed during postrm purge. ucf(1) may help with these tasks. See also https://wiki.debian.org/DpkgConffileHandling In https://lists.debian.org/debian-devel/2012/09/msg00412.html and followups it has been agreed that these bugs are to be filed with severity serious. debsums reports modification of the following files, from the attached log (scroll to the bottom...): /etc/openstack-dashboard/local_settings.d/_0005_debian_webroot.py (This file is owned by openstack-dashboard.) cheers, Andreas openstack-dashboard-apache_3:16.0.0-2.log.gz Description: application/gzip --- End Message --- --- Begin Message --- Source: horizon Source-Version: 3:16.0.0-3 We believe that the bug you reported is fixed in the latest version of horizon, 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 946...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Thomas Goirand (supplier of updated horizon package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Fri, 06 Dec 2019 18:47:50 +0100 Source: horizon Architecture: source Version: 3:16.0.0-3 Distribution: unstable Urgency: medium Maintainer: Debian OpenStack Changed-By: Thomas Goirand Closes: 946238 Changes: horizon (3:16.0.0-3) unstable; urgency=medium . * Do not install files in debian/local_settings.d/* as CONFFILE, as by definition, these files are to be modified by the Debian packaging. Also, do the copy only a single time for the life of the package (ie: until the package is purged) so that users can continue to tweak the way they want including removing files (Closes: #946238). Checksums-Sha1: add10cbc33f84024a6195482495c54cc190eb0ae 4307 horizon_16.0.0-3.dsc 369301b9c6f8716019e0f24da008b941d4d147a1 28384 horizon_16.0.0-3.debian.tar.xz c335c3f737f5e383a55baeab939a0c9b8bd89693 16050 horizon_16.0.0-3_amd64.buildinfo Checksums-Sha256: 75203f34cdec23173fe43839b2e3adc3ce4f68ee470c6aa4cefef2d5230231b9 4307 horizon_16.0.0-3.dsc 805daccbf2edacd1cdc9503f019f528fae10b818522438cc615feb4fe32882e0 28384 horizon_16.0.0-3.debian.tar.xz 69e01b7520d5fd284adfe2c13c60b930c2ae0f443e61a9328e5a7ff95e2043b3 16050 horizon_16.0.0-3_amd64.buildinfo Files: 715596912bd9dbcbd7009812bb8dcf6a 4307 net optional horizon_16.0.0-3.dsc 9b4d5a2a3203d36c584b4be90da3bd45 28384 net optional horizon_16.0.0-3.debian.tar.xz
Bug#946293: Dependency problems between espeakup-udeb and espeak-ng-data-udeb breaking d-i builds
Package: espeakup Version: 1:0.80-16 Severity: serious Tags: d-i Hi Samuel, There's a problem with dependencies that's causing d-i to fail to build, as seen in the end of the log at: https://d-i.debian.org/daily-images/amd64/20191206-00:05/build_cdrom_gtk.log ... Reading package lists... Building dependency tree... espeakup-udeb:amd64 Depends on espeak-ng-data-udeb:amd64 < none -> 1.50+dfsg-4 @un puN > (< 1.49.2+dfsgA) can't be satisfied! 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: espeakup-udeb : Depends: espeak-ng-data-udeb (< 1.49.2+dfsgA) but 1.50+dfsg-4 is to be installed E: Unable to correct problems, you have held broken packages. make[2]: *** [Makefile:674: stamps/get_udebs-cdrom_gtk-stamp] Error 100 make[1]: *** [Makefile:298: _build] Error 2 make: *** [Makefile:292: build_cdrom_gtk] Error 2 ... Please could you take a look? -- System Information: Debian Release: 10.2 APT prefers stable-debug APT policy: (500, 'stable-debug'), (500, 'stable'), (500, 'oldstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.19.0-6-amd64 (SMP w/4 CPU cores) Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), LANGUAGE=en_GB:en (charmap=UTF-8) Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages espeakup depends on: pn espeak ii init-system-helpers 1.56+nmu1 ii libc62.28-10 ii libespeak-ng11.49.2+dfsg-8 ii lsb-base 10.2019051400 espeakup recommends no packages. espeakup suggests no packages.
Bug#946287: marked as done (webext-compactheader: too low dependency on thunderbird)
Your message dated Fri, 06 Dec 2019 18:19:13 + with message-id and subject line Bug#946287: fixed in compactheader 3.0.0~beta5-2 has caused the Debian Bug report #946287, regarding webext-compactheader: too low dependency on thunderbird 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.) -- 946287: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=946287 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: webext-compactheader Version: 3.0.0~beta5-1 Severity: serious The webext-compactheader depends on thunderbird (>= 68.0~), missing the epoch that the thunderbird package carries. I have just installed it with thunderbird 1:60.9.0-1 where it does not work. Going to upgrade thunderbird now to fix that. Thanks for maintaining thunderbird and this extension! -- System Information: Debian Release: bullseye/sid APT prefers unstable APT policy: (500, 'unstable'), (101, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.4.2-nouveau (SMP w/2 CPU cores) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages webext-compactheader depends on: ii thunderbird 1:60.9.0-1 webext-compactheader recommends no packages. webext-compactheader suggests no packages. -- no debconf information --- End Message --- --- Begin Message --- Source: compactheader Source-Version: 3.0.0~beta5-2 We believe that the bug you reported is fixed in the latest version of compactheader, 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 946...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Carsten Schoenert (supplier of updated compactheader package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Fri, 06 Dec 2019 18:59:16 +0100 Source: compactheader Architecture: source Version: 3.0.0~beta5-2 Distribution: unstable Urgency: medium Maintainer: Debian Mozilla Extension Maintainers Changed-By: Carsten Schoenert Closes: 946287 Changes: compactheader (3.0.0~beta5-2) unstable; urgency=medium . * [25489aa] d/control: fix depending TB version (Closes: #946287) Checksums-Sha1: e456225ce8114bb662367db7fa2abba80f1dde93 2167 compactheader_3.0.0~beta5-2.dsc a4b37a4ae96078b4fef161482b3e0cca6941da18 12404 compactheader_3.0.0~beta5-2.debian.tar.xz b41851d72d18ebbd4c3c571dc0d0c69c1dd697de 5986 compactheader_3.0.0~beta5-2_amd64.buildinfo Checksums-Sha256: 3264ae17cd1de8c9751f2e9acbe86b937e0d2c17c1b5ec92cab4af42308c7946 2167 compactheader_3.0.0~beta5-2.dsc 663995717c22fc08cb79f3e501421b8e2b4a53ee5d7445ff2f278aaa0cb98a50 12404 compactheader_3.0.0~beta5-2.debian.tar.xz 3fef1befcfa15a805bb364dedebe254833c1b091be73dbe40638fe0bf7a73637 5986 compactheader_3.0.0~beta5-2_amd64.buildinfo Files: 9ed260377ca6405c5f7c2c9c3294e073 2167 mail optional compactheader_3.0.0~beta5-2.dsc b572a9da8c9ebd11a529f6a74fdb4298 12404 mail optional compactheader_3.0.0~beta5-2.debian.tar.xz 6891a737f893b068a0fba33d03fe464b 5986 mail optional compactheader_3.0.0~beta5-2_amd64.buildinfo -BEGIN PGP SIGNATURE- iQJMBAEBCgA2FiEEtw38bxNP7PwBHmKqgwFgFCUdHbAFAl3ql3oYHGMuc2Nob2Vu ZXJ0QHQtb25saW5lLmRlAAoJEIMBYBQlHR2wPc4QAJ9J+rovIVVaIwOAODn/ez9G 5CAwP5By4wsTEf4JiThfD/8kwHTDR5vBh47hZUq+v7OajJ7CbWyiyswLcy5YnykD mulNEehhrYkgBdYftqXJad5ZKbKMI1WP/24xv3da1Ot3mHrVl70gA3Qf4hxKbLOf uA1CSjq2ltaup5A5ldntZ6eskvxSLFFYBy9H9u9ivOsGnGRBjuRHrQvLbQIYBj8t krKwSGB5OdRkQwP2HxSAu+yqSJntpYu1AqX/twnXI1+0v+cc9GCZ6/XB0Yhn91bw 3L3a4AGZofJ9/8qtkj8lciHnzz9hgihnunJ6DucDmZeyY5CU09lZ58blJNi/s9i5 5tQaT1A0XaN/adYfNDdzkplEmGtl89kejpfTzEEfDbigHLk1gOCvWMuMYDcH1V3l G+IoRgCB2NLFd8aqMWOuo259VD2YUdYnZMFUjZq9Gs92iJHaXD0lt5OqzhNRRHY7 tdHAWVsHWazEduxbRKODdEY06014vwz7hD7d2/3rlc/OY58DYYmoYGhCYlkALtjc AXpTzmjLgbhI+OCcHnSdGrh9/yrCZtOSD9LgdKnf3zQeaaEDi/O8Om6iyJNMGq1X l+BCBvYmpkz9EDt7Rwe6JH8cYHskP6WGwQcs0LCijJ7gQer5KCvH/7ToK/Ir6Oq5 DCdnP+W1eIlrZNHRcjIR =Equ7 -END PGP SIGNATURE End Message ---
Bug#944636: marked as done (insighttoolkit4: CMake missing files for imported targets)
Your message dated Fri, 06 Dec 2019 18:10:19 + with message-id and subject line Bug#944636: fixed in insighttoolkit4 4.13.2-dfsg1-4 has caused the Debian Bug report #944636, regarding insighttoolkit4: CMake missing files for imported targets 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.) -- 944636: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=944636 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: insighttoolkit4 Version: 4.13.2-dfsg1-1 Severity: important Control: affects -1 src:otb Dear Maintainer, When building otb with only insighttoolkit4 and without opencv (#944341 causes B-D uninstallable), the configure target fails due to missing files for imported targets and missing FindLIBMINC.cmake: -- The imported target "vtkgdcm" references the file "/usr/lib/x86_64-linux-gnu/libvtkgdcm.so.3.0.4" but this file does not exist. Possible reasons include: * The file was deleted, renamed, or moved to another location. * An install or uninstall procedure did not complete successfully. * The installation package was faulty and contained "/usr/lib/x86_64-linux-gnu/gdcm-3.0/GDCMTargets.cmake" but not all the files it references. -- The imported target "vtkgdcmsharpglue" references the file "/usr/lib/x86_64-linux-gnu/libvtkgdcmsharpglue.so" but this file does not exist. Possible reasons include: * The file was deleted, renamed, or moved to another location. * An install or uninstall procedure did not complete successfully. * The installation package was faulty and contained "/usr/lib/x86_64-linux-gnu/gdcm-3.0/GDCMTargets.cmake" but not all the files it references. -- The imported target "vtkgdcmJava" references the file "/usr/lib/x86_64-linux-gnu/jni/libvtkgdcmJava.so" but this file does not exist. Possible reasons include: * The file was deleted, renamed, or moved to another location. * An install or uninstall procedure did not complete successfully. * The installation package was faulty and contained "/usr/lib/x86_64-linux-gnu/gdcm-3.0/GDCMTargets.cmake" but not all the files it references. -- The imported target "vtkgdcmPython" references the file "/usr/lib/python/dist-packages/vtkgdcmPython.so" but this file does not exist. Possible reasons include: * The file was deleted, renamed, or moved to another location. * An install or uninstall procedure did not complete successfully. * The installation package was faulty and contained "/usr/lib/x86_64-linux-gnu/gdcm-3.0/GDCMTargets.cmake" but not all the files it references. -- The imported target "vtkgdcmPythonD" references the file "/usr/lib/x86_64-linux-gnu/libvtkgdcmPythonD.so.3.0.4" but this file does not exist. Possible reasons include: * The file was deleted, renamed, or moved to another location. * An install or uninstall procedure did not complete successfully. * The installation package was faulty and contained "/usr/lib/x86_64-linux-gnu/gdcm-3.0/GDCMTargets.cmake" but not all the files it references. -- The imported target "gdcmdump" references the file "/usr/bin/gdcmdump" but this file does not exist. Possible reasons include: * The file was deleted, renamed, or moved to another location. * An install or uninstall procedure did not complete successfully. * The installation package was faulty and contained "/usr/lib/x86_64-linux-gnu/gdcm-3.0/GDCMTargets.cmake" but not all the files it references. -- The imported target "gdcmdiff" references the file "/usr/bin/gdcmdiff" but this file does not exist. Possible reasons include: * The file was deleted, renamed, or moved to another location. * An install or uninstall procedure did not complete successfully. * The installation package was faulty and contained "/usr/lib/x86_64-linux-gnu/gdcm-3.0/GDCMTargets.cmake" but not all the files it references. -- The imported target "gdcmraw" references the file "/usr/bin/gdcmraw" but this file does not exist. Possible reasons include: * The file was deleted, renamed, or moved to another location. * An install or uninstall procedure did not complete successfully. * The installation package was faulty and contained "/usr/lib/x86_64-linux-gnu/gdcm-3.0/GDCMTargets.cmake" but not all the files it references. -- The imported target "gdcmscanner" references the file "/usr/bin/gdcmscanner" but this file does not exist. Possible reasons include: * The file was deleted, renamed, or moved to another location. * An install or uninstall procedure did not complete successfully. * The installation package
Bug#946238: marked as pending in horizon
Control: tag -1 pending Hello, Bug #946238 in horizon reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/openstack-team/services/horizon/commit/c62c238be3757baf7f749c944f141d04eafb432c * Do not install files in debian/local_settings.d/* as CONFFILE, as by definition, these files are to be modified by the Debian packaging. Also, do the copy only a single time for the life of the package (ie: until the package is purged) so that users can continue to tweak the way they want including removing files (Closes: #946238). (this message was generated automatically) -- Greetings https://bugs.debian.org/946238
Processed: Bug#946238 marked as pending in horizon
Processing control commands: > tag -1 pending Bug #946238 [openstack-dashboard-apache] openstack-dashboard-apache: modifies conffiles (policy 10.7.3): /etc/openstack-dashboard/local_settings.d/_0005_debian_webroot.py Added tag(s) pending. -- 946238: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=946238 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#946290: libpcre2-posix2:amd64 is uninstallable
forcemerge 946279 946290 quit Hi, Please check the BTS for duplicates before filing bugs. Thanks, Matthew
Processed: Tagging a couple of things
Processing commands for cont...@bugs.debian.org: > tags 946279 +pending Bug #946279 [src:pcre2] pcre2: Failure when upgrading: file overwrite (libpcre2-posix.so.2.0.3) Added tag(s) pending. > tags 946275 +pending Bug #946275 [src:pcre2] pcre2: Please make another source-only upload to allow testing migration Added tag(s) pending. > tags 946221 +upstream Bug #946221 [pcre2] rspamd: segfault with pcre2 10.34, works with 10.32 Added tag(s) upstream. > quit Stopping processing here. Please contact me if you need assistance. -- 946221: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=946221 946275: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=946275 946279: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=946279 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: tagging 946225, tagging 946228
Processing commands for cont...@bugs.debian.org: > tags 946225 + sid bullseye Bug #946225 [src:k3d] FTBFS related to Boost.Python Added tag(s) bullseye and sid. > tags 946228 + sid bullseye Bug #946228 [src:k3d] FTBFS with CGAL 5.0 Added tag(s) sid and bullseye. > thanks Stopping processing here. Please contact me if you need assistance. -- 946225: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=946225 946228: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=946228 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed (with 1 error): Re: Bug#946290: libpcre2-posix2:amd64 is uninstallable
Processing commands for cont...@bugs.debian.org: > forcemerge 946279 946290 Bug #946279 [src:pcre2] pcre2: Failure when upgrading: file overwrite (libpcre2-posix.so.2.0.3) Unable to merge bugs because: package of #946290 is 'libpcre2-posix2' not 'src:pcre2' Failed to forcibly merge 946279: Did not alter merged bugs. > quit Stopping processing here. Please contact me if you need assistance. -- 946279: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=946279 946290: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=946290 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#946290: libpcre2-posix2:amd64 is uninstallable
Package: libpcre2-posix2 Version: 10.34-5 Severity: serious -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Preparing to unpack .../4-libpcre2-posix2_10.34-5_amd64.deb ... Unpacking libpcre2-posix2:amd64 (10.34-5) ... dpkg: error processing archive /tmp/apt-dpkg-install-zUiPeq/4-libpcre2-posix2_10.34-5_amd64.deb (--unpack): trying to overwrite '/usr/lib/x86_64-linux-gnu/libpcre2-posix.so.2.0.3', which is also in package libpcre2-posix0:amd64 10.34-3+b1 Preparing to unpack .../5-libpcre2-8-0_10.34-5_amd64.deb ... Unpacking libpcre2-8-0:amd64 (10.34-5) over (10.34-3+b1) ... Errors were encountered while processing: /tmp/apt-dpkg-install-zUiPeq/4-libpcre2-posix2_10.34-5_amd64.deb E: Sub-process /usr/bin/dpkg returned an error code (1) - -- System Information: Debian Release: bullseye/sid APT prefers unstable APT policy: (990, 'unstable'), (500, 'unstable-debug'), (1, 'experimental-debug'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 5.3.0-2-amd64 (SMP w/8 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US (charmap=UTF-8) Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEjkF6151RK40WXe2HCDw+u0oWieAFAl3qjgoACgkQCDw+u0oW ieCDPA//d0SZv6h5xg9hSSzju2i9uNcTpG+pKhxTgLP+umRStmt9IvxUWQQiKnnM qNskn3XuCKSTUqjHpwGqhM+zMMxLqUyBTpluTOekGCuDOtilGG3JL7b/eRVIrItR CwafcADx/ZAbGwb8BMLLtc/L4jFKhfgSaH751FZY60Z8/BYTebBCERt2p002Tcbm A0O89TRCF4epYd89LEgst8sc8PpXVsl+qo5RBsig8puPDrM1mehzEwuo0T2idP69 3UT1tKNoKafrDrQOG+hWnv38xIwwt9MiRUHRb4rz83uBBrCF+la9FjifEVHWz2fc 9zfS/L0VTmmSQbmA7xJTCbdf5HYa3qn4TAjWBZ+424t5sK22pv+JM4yeOgHik3VJ n0HGYI9Juy9e8dP3EZKRUisV0USheVzXYjKc93pKh2fFoJjZqHumVSxqEhYxHz9l jB8qM22HxY+KMRTbej9Xlwiv6StApD0FzmtjtwOlmLlhEdZIMwk1SrdyhSOmm9by i1zQAoT6qZ8qGj382380Tg7gI1IXEdrn5AuAl8XCL3hRLRWWnuE4JD1BnYbLExCU l/KMFoI5btv1iaW6act2ivHXZgaI2DHV2TFSK8JN4Fwi2GN6GwzPIQKz2/2CIfqN MlBAF9c8fX3arjIjEvX3zdngl2TV7AljAuHh4jGS5qcZRTbLJFQ= =JbDP -END PGP SIGNATURE-
Bug#946289: ufw: fails to start with iptables 1.8.4
Package: ufw Version: 0.36-1 Severity: grave Justification: renders package unusable This started since the latest upgrade of iptables (1.8.4). Reverting to 1.8.3 (testing) makes it work again. This is the contents of the journal for ufw.service: -- Logs begin at Thu 2019-12-05 14:15:18 -03, end at Fri 2019-12-06 13:45:35 -03. -- dez 05 14:15:18 lemur ufw-init[455]: Bad argument `DROP' dez 05 14:15:18 lemur ufw-init[455]: Error occurred at line: 4 dez 05 14:15:18 lemur ufw-init[455]: Try `iptables-restore -h' or 'iptables-restore --help' for more information. dez 05 14:15:18 lemur ufw-init[458]: Bad argument `-' dez 05 14:15:18 lemur ufw-init[458]: Error occurred at line: 4 dez 05 14:15:18 lemur ufw-init[458]: Try `iptables-restore -h' or 'iptables-restore --help' for more information. dez 05 14:15:18 lemur ufw-init[460]: iptables-restore: line 2 failed dez 05 14:15:18 lemur ufw-init[465]: Bad argument `-' dez 05 14:15:18 lemur ufw-init[465]: Error occurred at line: 3 dez 05 14:15:18 lemur ufw-init[465]: Try `iptables-restore -h' or 'iptables-restore --help' for more information. dez 05 14:15:18 lemur ufw-init[468]: Bad argument `-' dez 05 14:15:18 lemur ufw-init[468]: Error occurred at line: 3 dez 05 14:15:18 lemur ufw-init[468]: Try `iptables-restore -h' or 'iptables-restore --help' for more information. dez 05 14:15:18 lemur ufw-init[473]: Bad argument `-' dez 05 14:15:18 lemur ufw-init[473]: Error occurred at line: 3 dez 05 14:15:18 lemur ufw-init[473]: Try `iptables-restore -h' or 'iptables-restore --help' for more information. dez 05 14:15:18 lemur ufw-init[474]: Bad argument `-' dez 05 14:15:18 lemur ufw-init[474]: Error occurred at line: 3 dez 05 14:15:18 lemur ufw-init[474]: Try `iptables-restore -h' or 'iptables-restore --help' for more information. dez 05 14:15:18 lemur ufw-init[476]: iptables-restore v1.8.4 (nf_tables): Chain 'ufw-user-input' does not exist dez 05 14:15:18 lemur ufw-init[476]: Error occurred at line: 2 dez 05 14:15:18 lemur ufw-init[476]: Try `iptables-restore -h' or 'iptables-restore --help' for more information. dez 05 14:15:18 lemur ufw-init[478]: Bad argument `DROP' dez 05 14:15:18 lemur ufw-init[478]: Error occurred at line: 4 dez 05 14:15:18 lemur ufw-init[478]: Try `ip6tables-restore -h' or 'ip6tables-restore --help' for more information. dez 05 14:15:18 lemur ufw-init[481]: Bad argument `-' dez 05 14:15:18 lemur ufw-init[481]: Error occurred at line: 4 dez 05 14:15:18 lemur ufw-init[481]: Try `ip6tables-restore -h' or 'ip6tables-restore --help' for more information. dez 05 14:15:18 lemur ufw-init[483]: ip6tables-restore: line 2 failed dez 05 14:15:18 lemur ufw-init[486]: Bad argument `-' dez 05 14:15:18 lemur ufw-init[486]: Error occurred at line: 3 dez 05 14:15:18 lemur ufw-init[486]: Try `ip6tables-restore -h' or 'ip6tables-restore --help' for more information. dez 05 14:15:18 lemur ufw-init[489]: Bad argument `-' dez 05 14:15:18 lemur ufw-init[489]: Error occurred at line: 3 dez 05 14:15:18 lemur ufw-init[489]: Try `ip6tables-restore -h' or 'ip6tables-restore --help' for more information. dez 05 14:15:18 lemur ufw-init[494]: Bad argument `-' dez 05 14:15:18 lemur ufw-init[494]: Error occurred at line: 3 dez 05 14:15:18 lemur ufw-init[494]: Try `ip6tables-restore -h' or 'ip6tables-restore --help' for more information. dez 05 14:15:18 lemur ufw-init[495]: Bad argument `-' dez 05 14:15:18 lemur ufw-init[495]: Error occurred at line: 3 dez 05 14:15:18 lemur ufw-init[495]: Try `ip6tables-restore -h' or 'ip6tables-restore --help' for more information. dez 05 14:15:18 lemur ufw-init[498]: ip6tables-restore v1.8.4 (nf_tables): Chain 'ufw6-user-input' does not exist dez 05 14:15:18 lemur ufw-init[498]: Error occurred at line: 2 dez 05 14:15:18 lemur ufw-init[498]: Try `ip6tables-restore -h' or 'ip6tables-restore --help' for more information. dez 05 14:15:18 lemur ufw-init[503]: Problem running '/etc/ufw/user.rules' dez 05 14:15:18 lemur ufw-init[503]: Problem running '/etc/ufw/user6.rules' dez 06 13:45:26 lemur systemd[1]: Starting Uncomplicated firewall... dez 06 13:45:26 lemur ufw-init[232006]: Bad argument `DROP' dez 06 13:45:26 lemur ufw-init[232006]: Error occurred at line: 4 dez 06 13:45:26 lemur ufw-init[232006]: Try `iptables-restore -h' or 'iptables-restore --help' for more information. dez 06 13:45:26 lemur ufw-init[232009]: Bad argument `-' dez 06 13:45:26 lemur ufw-init[232009]: Error occurred at line: 4 dez 06 13:45:26 lemur ufw-init[232009]: Try `iptables-restore -h' or 'iptables-restore --help' for more information. dez 06 13:45:26 lemur ufw-init[232011]: iptables-restore: line 2 failed dez 06 13:45:26 lemur ufw-init[232014]: Bad argument `-' dez 06 13:45:26 lemur ufw-init[232014]: Error occurred at line: 3 dez 06 13:45:26 lemur ufw-init[232014]: Try `iptables-restore -h' or 'iptables-restore --help' for more information. dez 06 13:45:26 lemur ufw-init[232017]: Bad argument `-' dez 06 13:45:26 lemur ufw-init[232017]: Error occurred at
Bug#946287: webext-compactheader: too low dependency on thunderbird
Package: webext-compactheader Version: 3.0.0~beta5-1 Severity: serious The webext-compactheader depends on thunderbird (>= 68.0~), missing the epoch that the thunderbird package carries. I have just installed it with thunderbird 1:60.9.0-1 where it does not work. Going to upgrade thunderbird now to fix that. Thanks for maintaining thunderbird and this extension! -- System Information: Debian Release: bullseye/sid APT prefers unstable APT policy: (500, 'unstable'), (101, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.4.2-nouveau (SMP w/2 CPU cores) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages webext-compactheader depends on: ii thunderbird 1:60.9.0-1 webext-compactheader recommends no packages. webext-compactheader suggests no packages. -- no debconf information
Bug#937657: marked as done (python-colormap: Python2 removal in sid/bullseye)
Your message dated Fri, 06 Dec 2019 16:51:43 + with message-id and subject line Bug#937657: fixed in python-colormap 1.0.2-2 has caused the Debian Bug report #937657, regarding python-colormap: 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.) -- 937657: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=937657 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:python-colormap Version: 1.0.2-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:python-colormap 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 --- Source: python-colormap Source-Version: 1.0.2-2 We believe that the bug you reported is fixed in the latest version of python-colormap, 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 937...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Andreas Tille (supplier of updated python-colormap package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Fri, 06 Dec 2019 16:54:07 +0100 Source: python-colormap Binary: python3-colormap Architecture: source Version: 1.0.2-2 Distribution: unstable Urgency: medium Maintainer: Debian Med Packaging Team Changed-By: Andreas Tille Description: python3-colormap - ease manipulation of matplotlib colormaps and color codecs (Pytho Closes: 937657 Changes: python-colormap (1.0.2-2) unstable; urgency=medium . * Afif Elghraoui himself from Uploaders * Add myself to Uploaders * Drop Python2 package Closes: #937657 * debhelper-compat 12 * Standards-Version: 4.4.1 * debian/copyright: Use spaces rather than tabs in continuation lines. * Set upstream metadata fields: Repository, Repository-Browse. Checksums-Sha1: c324d329f65d89d6f638774489a1d95393caca60 2187 python-colormap_1.0.2-2.dsc 1ad285dbaf1ece1af63e9f28554726984aaa798b 3072 python-colormap_1.0.2-2.debian.tar.xz Checksums-Sha256:
Bug#946279: pcre2: Failure when upgrading: file overwrite (libpcre2-posix.so.2.0.3)
On 06/12/2019 15:53, Boyuan Yang wrote: > When installing the new package libpcre2-posix2, it provides the same file as > libpcre2-posix0 without declaring Breaks: relationship. This would make the > upgrade fail. Bother, yes, this is because the previous libpcre2-posix0 was misnamed (the soname had already increased to 2). I've fixed this in my tree, it'll be in the next upload. Regards, Matthew
Bug#936704: marked as done (hinge: Python2 removal in sid/bullseye)
Your message dated Fri, 06 Dec 2019 16:10:42 + with message-id and subject line Bug#936704: fixed in hinge 0.5.0-5 has caused the Debian Bug report #936704, regarding hinge: 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.) -- 936704: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=936704 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:hinge Version: 0.5.0-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:hinge 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 --- Source: hinge Source-Version: 0.5.0-5 We believe that the bug you reported is fixed in the latest version of hinge, 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 936...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Andreas Tille (supplier of updated hinge package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Fri, 06 Dec 2019 16:12:32 +0100 Source: hinge Binary: hinge Architecture: source Version: 0.5.0-5 Distribution: unstable Urgency: medium Maintainer: Debian Med Packaging Team Changed-By: Andreas Tille Description: hinge - long read genome assembler based on hinging Closes: 936704 Changes: hinge (0.5.0-5) unstable; urgency=medium . * Afif removed himself from Uploaders * Add myself to Uploaders * Use 2to3 to port to Python3 Closes: #936704 * debhelper-compat 12 * Standards-Version: 4.4.1 * debian/copyright: use spaces rather than tabs to start continuation lines. * Set upstream metadata fields: Repository, Repository-Browse. Checksums-Sha1: 5019f13a1c06389491ac9d77b2fa9add51abf771 2141 hinge_0.5.0-5.dsc 9047d85496f5a89e5b56c40c68b36a70a2ec2657 19368 hinge_0.5.0-5.debian.tar.xz Checksums-Sha256: baa103adf508fd14a8e9ee0363c9a1ad7dc14ee468625736967facf7f83bc9e3 2141 hinge_0.5.0-5.dsc
Bug#946279: pcre2: Failure when upgrading: file overwrite (libpcre2-posix.so.2.0.3)
Source: pcre2 Severity: grave Version: 10.34-5 Dear pcre2 maintainer, When installing the new package libpcre2-posix2, it provides the same file as libpcre2-posix0 without declaring Breaks: relationship. This would make the upgrade fail. Unpacking libpcre2-posix2:amd64 (10.34-5) ... dpkg: error processing archive /tmp/apt-dpkg-install-mPxSYc/2-libpcre2- posix2_10.34-5_amd64.deb (--unpack): trying to overwrite '/usr/lib/x86_64-linux-gnu/libpcre2-posix.so.2.0.3', which is also in package libpcre2-posix0:amd64 10.34-3+b1 Errors were encountered while processing: /tmp/apt-dpkg-install-mPxSYc/2-libpcre2-posix2_10.34-5_amd64.deb E: Sub-process /usr/bin/dpkg returned an error code (1) -- Regards, Boyuan Yang
Processed: Re: Bug#946198: Since upgrading to 1.25.13 no remote printer is made available anymore
Processing commands for cont...@bugs.debian.org: > tags 946198 upstream Bug #946198 [cups-browsed] Since upgrading to 1.25.13 no remote printer is made available anymore Added tag(s) upstream. > thanks Stopping processing here. Please contact me if you need assistance. -- 946198: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=946198 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#946198: Since upgrading to 1.25.13 no remote printer is made available anymore
tags 946198 upstream thanks On Fri 06 Dec 2019 at 11:08:19 +0100, Michael Meskes wrote: > > Which printers list? An application dialog? > > Oops, sorry, I was referring to the printers tab on localhost:631. In > the add printer dialog on the administration tab they are still listed. > All application dialogs do not list the printers anymore either. > > > The outputs of 'lpstat -a' and 'lpstat -l -e', please. Activating > > logging > > 'lpstat -a' does not list any of the printers, 'lpstat -l -e' lists > them all. The first command outputs local print queues; cups-browsed should form these from what CUPS tells it with, essentially, the second command. It obviously isn't doing that. BTW, printing should still be available to you with 'lp -d...'. Also, if you stop cups-browsed, the dialogs of LibreOffice and Qt apps (and maybe GTK apps) should list printers and print queues. > > in cups-browsed.conf and taking a look at a log wouldn't be a bad > > idea. > > Fri Dec 6 11:00:58 2019 Removing entry B... > (ipps://host.local:631/printers/B...) and its CUPS queue. > Fri Dec 6 11:00:58 2019 Recording printer options for B... to > /var/cache/cups/cups-browsed-options-B... > Fri Dec 6 11:00:58 2019 Unable to get PPD file for B...: The printer > or class does not exist. > Fri Dec 6 11:00:58 2019 Unable to load PPD from local queue B..., > queue seems to be raw. > Fri Dec 6 11:00:58 2019 ERROR: Failed disabling printer 'B...': The > printer or class does not exist. > > I guess that explains why the printer is no longer active, but what > changed from the prior version of cups-browsed? I just verified again, > downgrading cups-browsed from 1.25.13-1 to 1.25.12-1 fixes the problem > and makes the printers appear again. And, yes, I can print on any of > them without an issue. Or in other words, the system does have a PPD > for the printer. > > Any idea? In the past I have stopped cups and cups-browsed and removed the files in /var/cache/cups, checked that there aren't any files in /etc/cups/ppd and that /etc/cups/printers.conf is empty, then restarted the cups and cups-browsed services. If you do not get anywhere, please report it upstream at https://github.com/OpenPrinting/cups-filters/issues perhaps after reading https://github.com/OpenPrinting/cups-filters/issues/124 Regards, Brian.
Bug#945970: marked as done (meep: Incomplete debian/copyright?)
Your message dated Fri, 06 Dec 2019 15:00:41 + with message-id and subject line Bug#945970: fixed in meep 1.12.0-2 has caused the Debian Bug report #945970, regarding meep: Incomplete debian/copyright? 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.) -- 945970: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=945970 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: meep Version: 1.12.0-1 Severity: serious Justication: Policy §12.5 X-Debbugs-CC: Thorsten Alteholz , ftpmas...@debian.org Hi, I just ACCEPTed meep from NEW but noticed it was missing attribution in debian/copyright for at least mt19937ar.c. This is in no way exhaustive so please check over the entire package carefully and address these on your next upload. Regards, -- ,''`. : :' : Chris Lamb `. `'` la...@debian.org / chris-lamb.co.uk `- --- End Message --- --- Begin Message --- Source: meep Source-Version: 1.12.0-2 We believe that the bug you reported is fixed in the latest version of meep, 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. Thorsten Alteholz (supplier of updated meep 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: Thu, 05 Dec 2019 21:40:40 +0100 Source: meep Architecture: source Version: 1.12.0-2 Distribution: unstable Urgency: medium Maintainer: Thorsten Alteholz Changed-By: Thorsten Alteholz Closes: 940491 943827 945970 Changes: meep (1.12.0-2) unstable; urgency=medium . * upload to unstable * debian/control: change dependency from atlas to libblas-dev (see MBF Mail and #943712) (Closes: #943827) * debian/copyright: update (Closes: #945970) * debian/control: update Conflicts: (Closes: #940491) traditionally this is done in meep-* packages those have been uploaded now, so I am closing this bug here Checksums-Sha1: 8e41884dde0462e6a20158e469d7de9119d9b44d 2368 meep_1.12.0-2.dsc 47a4b18303dabc5ae25a9ecb90c49e3d978a3d91 141864 meep_1.12.0-2.debian.tar.xz 557d53caf17253931d4bf91cfdee6688b37237d4 10964 meep_1.12.0-2_amd64.buildinfo Checksums-Sha256: 05d3050379d11d74ff478b14e568a59ee3d236330068395b35bb8eb6644e33f3 2368 meep_1.12.0-2.dsc 070760db3e853a3d0ad5dd9926e764d6efe0aafbd0927f72b51461570335da15 141864 meep_1.12.0-2.debian.tar.xz f35d9041eb9c965efef626a0389e89f560d7790f45004f3afb9e42315b8cd895 10964 meep_1.12.0-2_amd64.buildinfo Files: 5b2d500d301f002a4759aaf9d710f963 2368 science optional meep_1.12.0-2.dsc 7957948f6edfe6a0f258d765618547da 141864 science optional meep_1.12.0-2.debian.tar.xz e25cf73faed271d056cbce40b2dc3cb9 10964 science optional meep_1.12.0-2_amd64.buildinfo -BEGIN PGP SIGNATURE- iQKnBAEBCgCRFiEEYgH7/9u94Hgi6ruWlvysDTh7WEcFAl3pmfBfFIAALgAo aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldDYy MDFGQkZGREJCREUwNzgyMkVBQkI5Njk2RkNBQzBEMzg3QjU4NDcTHGRlYmlhbkBh bHRlaG9sei5kZQAKCRCW/KwNOHtYR19jEACXp+iiroSDNUZT3mEibHZLCVZyPzc6 kPdi9YPCiOWXoYLOxGydlNaVfzVeLrUi3RkyQbiq29Q0DgBJyzA3T+ArBZ0P738L 8szzrNuXpEjOCmYTliTKek/GO9vnlXBtLwEQ/uSCq62lXGVSoGznTs5XXUeddJQY fp2i+X745yTUXVZ3cCnrczLt0osJIciac1eJL/0zweidukol4Xju7IHSLUpSLW6I MooqvdGm89E42cPohUkya5xRfj50JmrC+6Qe6fLl1kVzazplRmAf/nW0IKVtxw/t tv5zo/UttamuMsAwC2UjSGzZ8ykvrjuH+G42d1Ow6Fq1Vg472Bdbleic/ED+Zjvd H3ruwN0kt+dRIAtLzlQRPMjfqFhXKX6Iry0L2AwjOr76rAcMv6On1XTOStmrDXor 7iGM7EjR/ISG5UUh5bFTDi4T+CG7Z8DdmVDIZM0iBZRYDnIsefGX8O22kHst2G6n 2un9iCG5M7HPRO7kV78JWYiosV6zenI0TzPlhbOLzPjWZx8g9mpWNpzUX2tO0WCV 3Z9hcyMbns+/Yni0rKoSx3akhghLpgzb95WJWIMp/6fz8bEFi2QrAGk+xiQfse+q PFuYGGTBHT/yHaFOZI9nsdEKH8vZUByQHKt8S8imtfhyoITYco0E+G7stQtRnOLc D02PG86uJ0mfPg== =l1dH -END PGP SIGNATURE End Message ---
Bug#940491: marked as done (src:meep: missing several Breaks+Replaces)
Your message dated Fri, 06 Dec 2019 15:00:41 + with message-id and subject line Bug#940491: fixed in meep 1.12.0-2 has caused the Debian Bug report #940491, regarding src:meep: missing several Breaks+Replaces 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.) -- 940491: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=940491 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: libmeep16 Version: 1.11.0-1 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package fails to upgrade from 'sid' to 'experimental'. It installed fine in 'sid', then the upgrade to 'experimental' 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 .../libmeep16_1.11.0-1_amd64.deb ... Unpacking libmeep16 (1.11.0-1) ... dpkg: error processing archive /var/cache/apt/archives/libmeep16_1.11.0-1_amd64.deb (--unpack): trying to overwrite '/usr/share/meep/casimir.scm', which is also in package libmeep12 1.7.0-3+b1 Errors were encountered while processing: /var/cache/apt/archives/libmeep16_1.11.0-1_amd64.deb cheers, Andreas libmeep12=1.7.0-3+b1_libmeep16=1.11.0-1.log.gz Description: application/gzip --- End Message --- --- Begin Message --- Source: meep Source-Version: 1.12.0-2 We believe that the bug you reported is fixed in the latest version of meep, 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 940...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Thorsten Alteholz (supplier of updated meep 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: Thu, 05 Dec 2019 21:40:40 +0100 Source: meep Architecture: source Version: 1.12.0-2 Distribution: unstable Urgency: medium Maintainer: Thorsten Alteholz Changed-By: Thorsten Alteholz Closes: 940491 943827 945970 Changes: meep (1.12.0-2) unstable; urgency=medium . * upload to unstable * debian/control: change dependency from atlas to libblas-dev (see MBF Mail and #943712) (Closes: #943827) * debian/copyright: update (Closes: #945970) * debian/control: update Conflicts: (Closes: #940491) traditionally this is done in meep-* packages those have been uploaded now, so I am closing this bug here Checksums-Sha1: 8e41884dde0462e6a20158e469d7de9119d9b44d 2368 meep_1.12.0-2.dsc 47a4b18303dabc5ae25a9ecb90c49e3d978a3d91 141864 meep_1.12.0-2.debian.tar.xz 557d53caf17253931d4bf91cfdee6688b37237d4 10964 meep_1.12.0-2_amd64.buildinfo Checksums-Sha256: 05d3050379d11d74ff478b14e568a59ee3d236330068395b35bb8eb6644e33f3 2368 meep_1.12.0-2.dsc 070760db3e853a3d0ad5dd9926e764d6efe0aafbd0927f72b51461570335da15 141864 meep_1.12.0-2.debian.tar.xz f35d9041eb9c965efef626a0389e89f560d7790f45004f3afb9e42315b8cd895 10964 meep_1.12.0-2_amd64.buildinfo Files: 5b2d500d301f002a4759aaf9d710f963 2368 science optional meep_1.12.0-2.dsc 7957948f6edfe6a0f258d765618547da 141864 science optional meep_1.12.0-2.debian.tar.xz e25cf73faed271d056cbce40b2dc3cb9 10964 science optional meep_1.12.0-2_amd64.buildinfo -BEGIN PGP SIGNATURE- iQKnBAEBCgCRFiEEYgH7/9u94Hgi6ruWlvysDTh7WEcFAl3pmfBfFIAALgAo aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldDYy MDFGQkZGREJCREUwNzgyMkVBQkI5Njk2RkNBQzBEMzg3QjU4NDcTHGRlYmlhbkBh bHRlaG9sei5kZQAKCRCW/KwNOHtYR19jEACXp+iiroSDNUZT3mEibHZLCVZyPzc6 kPdi9YPCiOWXoYLOxGydlNaVfzVeLrUi3RkyQbiq29Q0DgBJyzA3T+ArBZ0P738L 8szzrNuXpEjOCmYTliTKek/GO9vnlXBtLwEQ/uSCq62lXGVSoGznTs5XXUeddJQY fp2i+X745yTUXVZ3cCnrczLt0osJIciac1eJL/0zweidukol4Xju7IHSLUpSLW6I MooqvdGm89E42cPohUkya5xRfj50JmrC+6Qe6fLl1kVzazplRmAf/nW0IKVtxw/t tv5zo/UttamuMsAwC2UjSGzZ8ykvrjuH+G42d1Ow6Fq1Vg472Bdbleic/ED+Zjvd H3ruwN0kt+dRIAtLzlQRPMjfqFhXKX6Iry0L2AwjOr76rAcMv6On1XTOStmrDXor 7iGM7EjR/ISG5UUh5bFTDi4T+CG7Z8DdmVDIZM0iBZRYDnIsefGX8O22kHst2G6n
Bug#937196: marked as done (opencolorio: Python2 removal in sid/bullseye)
Your message dated Fri, 06 Dec 2019 14:12:44 + with message-id and subject line Bug#937196: fixed in opencolorio 1.1.1~dfsg0-4 has caused the Debian Bug report #937196, regarding opencolorio: 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.) -- 937196: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=937196 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:opencolorio Version: 1.1.1~dfsg0-3 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:opencolorio 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 --- Source: opencolorio Source-Version: 1.1.1~dfsg0-4 We believe that the bug you reported is fixed in the latest version of opencolorio, 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 937...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Matteo F. Vescovi (supplier of updated opencolorio 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: Thu, 05 Dec 2019 17:39:54 +0100 Source: opencolorio Binary: libopencolorio-dev libopencolorio1v5 libopencolorio1v5-dbgsym opencolorio-doc opencolorio-tools opencolorio-tools-dbgsym python3-pyopencolorio python3-pyopencolorio-dbgsym Architecture: source amd64 all Version: 1.1.1~dfsg0-4 Distribution: unstable Urgency: medium Maintainer: Debian PhotoTools Maintainers Changed-By: Matteo F. Vescovi Description: libopencolorio-dev - complete color management solution - development libopencolorio1v5 - complete color management solution - runtime opencolorio-doc - complete color management solution - documentation opencolorio-tools - complete color management solution - utilities python3-pyopencolorio - complete color management solution - Python bindings Closes: 937196 Changes: opencolorio (1.1.1~dfsg0-4) unstable; urgency=medium . * debian/: py2 -> py3 migration (Closes: #937196) * debian/compat: dropped due
Bug#946267: cpio -i --no-absolute-filenames breaks symlinks starting with / or /..
Package: cpio Version: 2.13+dfsg-1 Severity: serious User: de...@kali.org Usertags: origin-kali Control: affects -1 live-build live-build is able to repack the installer initrd to add custom files. We use that feature in Kali and since last week, when cpio 2.13+dfsg-1 reached testing (and thus our ISO build chroots), our installer images are badly broken and we get errors like “/usr/share/debconf/frontend: not found” or “expr: not found”. After a diffoscope run to compare the original and repacked initrd I saw things like this: │ │ ├── etc/mtab │ │ │┄ symlink │ │ │ @@ -1 +1 @@ │ │ │ -destination: /proc/mounts │ │ │ +destination: proc/mounts │ │ ├── usr/bin/expr │ │ │┄ symlink │ │ │ @@ -1 +1 @@ │ │ │ -destination: /bin/busybox │ │ │ +destination: bin/busybox │ │ ├── usr/share/debconf/frontend │ │ │┄ symlink │ │ │ @@ -1 +1 @@ │ │ │ -destination: ../../lib/cdebconf/debconf │ │ │ +destination: lib/cdebconf/debconf So the target of the symlinks have been modified. live-build uses cpio in the following way to unpack the initrd and repack it: # mkdir temp # cd temp # cpio -i --make-directories --no-absolute-filenames /somewhere/initrd-repacked (see https://salsa.debian.org/live-team/live-build/blob/master/scripts/build/installer_debian-installer#L743 for actual code) So it uses "--no-absolute-filenames" just to ensure that the files are extracted in the current directory and to not extract them in the root directory (in case the archive contains absolute filenames), but it really doesn't want cpio to change the contents of the symlinks that it extracts! I looked in the manual page and could not find any option that would result in the desired behavior. As this is is breaking live-build, I'm putting this as a serious bug for now. This regression is because the upstream fix for CVE-2015-1197 mangles the symlinks in this way: https://git.savannah.gnu.org/cgit/cpio.git/commit/?id=45b0ee2b407913c533f7ded8d6f8cbeec16ff6ca The original SuSE patch that we used was smarter, it would not change the symlinks but it would refuse to extract over a symlink: https://bugzilla.suse.com/attachment.cgi?id=599460=diff FYI I'm putting the author of the above commit in copy so that he can chime in and be aware of this regression. Cheers, -- System Information: Debian Release: bullseye/sid APT prefers oldoldstable APT policy: (500, 'oldoldstable'), (500, 'unstable'), (500, 'testing'), (500, 'stable'), (500, 'oldstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.19.0-6-amd64 (SMP w/4 CPU cores) Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE 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 Versions of packages cpio depends on: ii libc6 2.29-3 cpio recommends no packages. Versions of packages cpio suggests: pn libarchive1 -- no debconf information
Processed: cpio -i --no-absolute-filenames breaks symlinks starting with / or /..
Processing control commands: > affects -1 live-build Bug #946267 [cpio] cpio -i --no-absolute-filenames breaks symlinks starting with / or /.. Added indication that 946267 affects live-build -- 946267: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=946267 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#946234: [NMU] FTFBS with CGAL 5.0 (if cmake is absent)
It's fixed upstream, I released a new version and Drew is on it bumping the version in Debian. [1] [1] https://github.com/nschloe/pygalmesh/issues/56 On Fri, Dec 6, 2019 at 2:30 PM Joachim Reichel wrote: > > > Upstream 0.5.0 now builds against CGAL 5, so we only need an upload here. > > What do you mean with "only"? Is there already a package for the new upstream > ready to be uploaded? > > NMU uploaded to DELAYED/5-day. >
Bug#946234: [NMU] FTFBS with CGAL 5.0 (if cmake is absent)
> Upstream 0.5.0 now builds against CGAL 5, so we only need an upload here. What do you mean with "only"? Is there already a package for the new upstream ready to be uploaded? NMU uploaded to DELAYED/5-day.
Bug#945408: marked as done (missing b-d on dh-python)
Your message dated Fri, 06 Dec 2019 13:19:25 + with message-id and subject line Bug#945408: fixed in astropy-healpix 0.5-1 has caused the Debian Bug report #945408, regarding missing b-d on dh-python to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 945408: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=945408 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:astropy-healpix Version: 0.4-6 Severity: serious Tags: sid bullseye missing b-d on dh-python, now necessary because python3-dev dropped that dependency. --- End Message --- --- Begin Message --- Source: astropy-healpix Source-Version: 0.5-1 We believe that the bug you reported is fixed in the latest version of astropy-healpix, 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. Ole Streicher (supplier of updated astropy-healpix package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Fri, 06 Dec 2019 10:00:17 +0100 Source: astropy-healpix Architecture: source Version: 0.5-1 Distribution: unstable Urgency: low Maintainer: Debian Astronomy Maintainers Changed-By: Ole Streicher Closes: 945408 Changes: astropy-healpix (0.5-1) unstable; urgency=low . * Team upload. * New upstream version 0.5 * Rediff patches. Drop patches that are applied upstream. * Push Standards-Version to 4.4.1. No changes needed * Add explicit dh-python build dependency (Closes: #945408) * Use pytest in CI test * Remove unused paragraphs from d/copyright * Add minimal d/u/metadata file Checksums-Sha1: a5e90f9b56424275a299c74654cd2f74c0972f20 2293 astropy-healpix_0.5-1.dsc d68f5d3a6badcb7453227d4b310135007c49f1d7 163123 astropy-healpix_0.5.orig.tar.gz 56c79f846087b91b6e69cdf370c9a2a8584665e6 4660 astropy-healpix_0.5-1.debian.tar.xz Checksums-Sha256: a599691ae6db62be66c7f2829279d1fc7efeaaa9482d36f51e5fe849ea975ce0 2293 astropy-healpix_0.5-1.dsc 5ae15da796a840f221fb83e25de791e827b6921bc21a365d99bc1a59c7c0cdad 163123 astropy-healpix_0.5.orig.tar.gz b73e36680d7b5014a3af70b7b58d78c7adf0c6a5a436dd5cd429e9e77101e81c 4660 astropy-healpix_0.5-1.debian.tar.xz Files: deaa5c2da56dd426b362dd9ba64f0289 2293 python optional astropy-healpix_0.5-1.dsc 8e474c70da122ff44cb4743176936391 163123 python optional astropy-healpix_0.5.orig.tar.gz 35b46f4ae3b87298d048af6bd8c22f82 4660 python optional astropy-healpix_0.5-1.debian.tar.xz -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEuvxshffLFD/utvsVcRWv0HcQ3PcFAl3qUPsACgkQcRWv0HcQ 3PfzCQ//QgNRJ7BPyNVMuHbghYWo7/WfmaTO0Hsq6idAbvIlsSCR1WqsM7sY72IU B85mWebDG+1hhIuNMJ0MWpvTAGMB8zR6ZcU6SEEj1tPqQR/r/5V97R5sdzCviMn5 CIYWDwHEuwMD0+YsVotfp3wwpkyqvPcg2OvWBsRxOl1gF8F9wE9n9fygRJBYvt/P jJccjy7o/VxTxUdcPWBLq8TQdbdCn9FyZZq5FkAglW+o8bs+B8BcYiVtIyBxzNYi ZOYRnUUADRCgSnALUIwQOnnG9iJKROHlZgfpibVGighd5LULeGr1oN6wUCLKZZHH 5sk3spjeBFDGysa8HA5yfzbuFhiHvMRpj3Owxnf9hKOD/mtrV8xh6wudNNjF8dzD WlOvYR57TzoSpaphNf3p750C/0Z5NOXXC1oGk29ZvWXek9tTUMnlemD2ry/hRFJa g+VxpbEc4toDywYDz5pnTd7dtLK2Te4wJtOyX4fLExoZiax/NWBZeUxpGRbcX4Hg 4kt+hwSbbVk8dFmVJudzxBozRl9IQphIw98IlZXxsyvM9CQ6BP/3HfyTc+OndGfn 0jxWbdNwQNE/p+beOJWMIoneB2EyKAHparMq7cgjKjDsx5XRo40c9HjIrwcE/uBq QecIrm9Qg3cSHOFO4ygq3Hm47BXQFFzKwrotJ9dcxDgktv1Pvnc= =SX/0 -END PGP SIGNATURE End Message ---
Bug#945234: marked as done (cupp: Renaming cupp3 to cupp breaks Debian Sid/Bullseye repository)
Your message dated Fri, 06 Dec 2019 13:00:15 + with message-id and subject line Bug#945234: fixed in cupp 0.0+20190501.git986658-4 has caused the Debian Bug report #945234, regarding cupp: Renaming cupp3 to cupp breaks Debian Sid/Bullseye repository 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.) -- 945234: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=945234 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: cupp Version: 0.0+20160624.git07f9b8-1 Severity: normal Dear maintainer, After renaming cupp3 to cupp suddenly and without coordinate with other maintainers, forensics-extra packages (and maybe others) was affected. If it is a forced needed transition, please coordinate the action before make it. If you only need rename the package from now on because a light reason as Python 2 removing, please follow these instructions[1]. IMO, this is the solution for cupp. Note that you package will arrives to NEW queue. [1] https://wiki.debian.org/RenamingPackages Regards, Eriberto --- End Message --- --- Begin Message --- Source: cupp Source-Version: 0.0+20190501.git986658-4 We believe that the bug you reported is fixed in the latest version of cupp, 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. Marcio de Souza Oliveira (supplier of updated cupp 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: Thu, 28 Nov 2019 23:45:15 -0300 Source: cupp Binary: cupp cupp3 Architecture: source all Version: 0.0+20190501.git986658-4 Distribution: unstable Urgency: medium Maintainer: Marcio de Souza Oliveira Changed-By: Marcio de Souza Oliveira Description: cupp - generate dictionaries for attacks from personal data cupp3 - transitional package Closes: 945234 Changes: cupp (0.0+20190501.git986658-4) unstable; urgency=medium . * debian/control: - Recreated the package cupp3 like dummy package to avoid breaks Debian Sid/Bullseye. Thanks Eriberto. (Closes: #945234) * Created cupp3.links to adds compatibility symlinks. Checksums-Sha1: 814c35060da5a89059de1d5635c2afae276e3752 1962 cupp_0.0+20190501.git986658-4.dsc 4284f3c7a35473810b5420bc90e5a25a51fc8183 23977 cupp_0.0+20190501.git986658.orig.tar.gz c558ff436bc061d25535b5e5af79b4d5e5c62ddc 3604 cupp_0.0+20190501.git986658-4.debian.tar.xz c0bbb68333263c8b0ba8f721ab8cd8e49a9565ab 3392 cupp3_0.0+20190501.git986658-4_all.deb e25c784f193848dc79d4106ba25e991e8ba9cdde 13212 cupp_0.0+20190501.git986658-4_all.deb 60f43e888923834af1dd1dc4aedd84e9b83ee331 6756 cupp_0.0+20190501.git986658-4_amd64.buildinfo Checksums-Sha256: 0abe0ad44f4b808aaa72158d787b0f011703ab72a4dbaa27d31207fd4c9892ba 1962 cupp_0.0+20190501.git986658-4.dsc 5ca414a0b80a348670ff7fffc755634f6db034a11da7d237d2e9499db48b6bc7 23977 cupp_0.0+20190501.git986658.orig.tar.gz d1b41839f6484e08791eecea5dc36aef76c01c0a4507c360bfa73a91346fd93a 3604 cupp_0.0+20190501.git986658-4.debian.tar.xz c0bb7849073a57766ae604bbd8571c2374c26e2acdb5a6e95fc5c82493d4e37d 3392 cupp3_0.0+20190501.git986658-4_all.deb 7dc812a5adc8e2c9911620604c06e651a30a1da42ac4977479c33fa438dce11d 13212 cupp_0.0+20190501.git986658-4_all.deb 31be4023637b2ab8159cdfad5cd3750a8a278e207f2e600d7c72c24303ebdb99 6756 cupp_0.0+20190501.git986658-4_amd64.buildinfo Files: b8ec59e62eda4fc7f18694e423b5adbc 1962 misc optional cupp_0.0+20190501.git986658-4.dsc be0f886efbe1c1991adc4c35ac02a946 23977 misc optional cupp_0.0+20190501.git986658.orig.tar.gz 33d8618fd2b7889464043eddbd1b94ed 3604 misc optional cupp_0.0+20190501.git986658-4.debian.tar.xz 12df809f325ab124dd3d11acb8da3da2 3392 oldlibs optional cupp3_0.0+20190501.git986658-4_all.deb 0c88bcac1bbecc6d3802f79647b65b17 13212 misc optional cupp_0.0+20190501.git986658-4_all.deb c5016c3045764a7e401f6e84250a4169 6756 misc optional cupp_0.0+20190501.git986658-4_amd64.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEuL9rDMyifLF0J67mR23xbSgM2tMFAl3hC3wACgkQR23xbSgM 2tNIbw/7Bh9CWunYNjaTFzBcgXQjQcHEXgSLQHssH4CUUrtSeDX6cxF2FkVdoL+9
Bug#944021: marked as done (xul-ext-compactheader: not compatible with thunderbird 68)
Your message dated Fri, 06 Dec 2019 13:00:14 +
with message-id
and subject line Bug#944021: fixed in compactheader 3.0.0~beta5-1
has caused the Debian Bug report #944021,
regarding xul-ext-compactheader: not compatible with thunderbird 68
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.)
--
944021: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=944021
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: xul-ext-compactheader
Version: 2.1.6-1
Severity: serious
This package is not compatible with thunderbird 68 which has just appeared
in unstable:
,
| $ LANG=C aptitude -s install thunderbird thunderbird-l10n-de
| The following packages will be upgraded:
| thunderbird{b} thunderbird-l10n-de
| The following packages are RECOMMENDED but will NOT be installed:
| lightning
| 2 packages upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
| Need to get 35.3 MB of archives. After unpacking 2812 kB will be used.
| The following packages have unmet dependencies:
| thunderbird : Breaks: xul-ext-compactheader (< 3.0.0) but 2.1.6-1 is
installed
`
On the thunderbird side of things, shouldn't the Breaks be adjusted to
(<< 3.0.0~), since 3.0.0.~beta3 is the latest version on
https://github.com/jmozmoz/compactheader/releases ?
-- System Information:
Debian Release: bullseye/sid
APT prefers unstable
APT policy: (500, 'unstable'), (101, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 5.3.8-nouveau (SMP w/2 CPU cores)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8),
LANGUAGE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
Versions of packages xul-ext-compactheader depends on:
ii thunderbird 1:60.9.0-1
xul-ext-compactheader recommends no packages.
xul-ext-compactheader suggests no packages.
-- no debconf information
--- End Message ---
--- Begin Message ---
Source: compactheader
Source-Version: 3.0.0~beta5-1
We believe that the bug you reported is fixed in the latest version of
compactheader, 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.
Carsten Schoenert (supplier of updated compactheader
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, 01 Dec 2019 12:44:59 +0100
Source: compactheader
Binary: webext-compactheader xul-ext-compactheader
Architecture: source all
Version: 3.0.0~beta5-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Mozilla Extension Maintainers
Changed-By: Carsten Schoenert
Description:
webext-compactheader - Thunderbird extension to reduce header size
xul-ext-compactheader - Thunderbird extension to reduce header size -
Transitional packag
Closes: 944021
Changes:
compactheader (3.0.0~beta5-1) unstable; urgency=medium
.
* [89f1683] d/control: adding versioned B-D on mozilla-devscripts
Using mozilla-devscripts need to be based on some recent version.
* [3503e4b] debhelper: use debhelper-compat in B-D
Moving over to debhelper-compat version 12, reducing the maintenance of
used files.
* [e3ef1f4] d/control: bump Standards-Version to 4.4.1
No further changes needed.
* [e1787a9] d/control: move Homepage info over to GitHub
The upstream project lives basically more on GitHub than on the old mozdev
website.
* [8944c9d] d/gbp.conf: exclude some more VCS files
The upstream source can include some old Mercurial VCS controlling files
which are useless fur us, exclude them while importing the source.
* [8b0d586] New upstream version 3.0.0~beta5
The AddOn is now full web-extension based.
(Closes: #944021)
* [ca0fad3] Remove patch queue
The one patch we have used within the patch queue isn't needed any more.
* [f6a6dca] d/control: remove B-D on mozilla-devscripts
For now drop the usage of any helper from mozilla-devscripts as it brings
no gain or advantage. The dh sequencers are enough to build the package.
* [c578353] d/control: add new package webext-compactheader
The source of the
Bug#943653: marked as done (thrift: fails to clean after build: cannot find java)
Your message dated Fri, 06 Dec 2019 13:01:06 + with message-id and subject line Bug#943653: fixed in thrift 0.13.0-1 has caused the Debian Bug report #943653, regarding thrift: fails to clean after build: cannot find java 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.) -- 943653: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=943653 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: thrift Version: 0.12.0-1 Severity: serious Justification: fails to build from source (but built successfully in the past) Hi, thrift/experimental fails to clean after a successful build (I haven't checked whether the version in sid has the same problem). The build succeeds, but a subsequent 'make distclean' fails. (This does not happen during the first build, since the tree is unconfigured and 'make distclean' does not get called.) [... first build has succeeded ...] fakeroot debian/rules clean dh clean --with python3,ruby,phpcomposer debian/rules override_dh_auto_clean make[1]: Entering directory '/build/thrift-0.12.0' # delete symlinks rm -f /build/thrift-0.12.0/lib/go/test/gopath/src/github.com rm -f /build/thrift-0.12.0/test/go/src/github.com rm -f /build/thrift-0.12.0/lib/go/test/gopath/src/golang.org rm -f /build/thrift-0.12.0/test/go/src/golang.org rm -f /build/thrift-0.12.0/compiler/cpp/test/plugin/t_cpp_generator.cc rm -f /build/thrift-0.12.0/lib/c_glib/src/thrift/stamp-h3 \ /build/thrift-0.12.0/lib/cpp/src/thrift/stamp-h2 \ /build/thrift-0.12.0/stamp-h1 # let make clean dh_auto_clean make -j3 distclean make[2]: Entering directory '/build/thrift-0.12.0' [...] Making distclean in java make[4]: Entering directory '/build/thrift-0.12.0/lib/java' rm -rf .libs _libs ./gradlew clean --console=plain rm -f *.lo test -z "" || rm -f test . = "." || test -z "" || rm -f ERROR: JAVA_HOME is not set and no 'java' command could be found in your PATH. Please set the JAVA_HOME variable in your environment to match the location of your Java installation. make[4]: *** [Makefile:662: clean-local] Error 1 make[4]: Leaving directory '/build/thrift-0.12.0/lib/java' make[3]: *** [Makefile:582: distclean-recursive] Error 1 make[3]: Leaving directory '/build/thrift-0.12.0/lib' make[2]: *** [Makefile:664: distclean-recursive] Error 1 make[2]: Leaving directory '/build/thrift-0.12.0' dh_auto_clean: make -j3 distclean returned exit code 2 make[1]: *** [debian/rules:45: override_dh_auto_clean] Error 255 make[1]: Leaving directory '/build/thrift-0.12.0' make: *** [debian/rules:118: clean] Error 2 Andreas thrift_0.12.0-1_twice.log.gz Description: application/gzip --- End Message --- --- Begin Message --- Source: thrift Source-Version: 0.13.0-1 We believe that the bug you reported is fixed in the latest version of thrift, 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. Laszlo Boszormenyi (GCS) (supplier of updated thrift 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, 01 Dec 2019 10:46:55 + Source: thrift Binary: golang-thrift-dev libthrift-0.13.0 libthrift-0.13.0-dbgsym libthrift-c-glib-dev libthrift-c-glib0 libthrift-c-glib0-dbgsym libthrift-dev libthrift-perl php-thrift php-thrift-dbgsym python3-thrift python3-thrift-dbg thrift-compiler thrift-compiler-dbgsym Architecture: source amd64 all Version: 0.13.0-1 Distribution: experimental Urgency: high Maintainer: Laszlo Boszormenyi (GCS) Changed-By: Laszlo Boszormenyi (GCS) Description: golang-thrift-dev - Go language support for Thrift libthrift-0.13.0 - Thrift C++ library libthrift-c-glib-dev - Thrift glib library (development headers) libthrift-c-glib0 - Thrift glib library libthrift-dev - Thrift C++ library (development headers) libthrift-perl - Perl language support for Thrift php-thrift - PHP language support for Thrift python3-thrift - Python 3 library for Thrift python3-thrift-dbg - Python library for Thrift (debug symbols) thrift-compiler - code generator/compiler for Thrift definitions Closes: 942337 943653 Changes: thrift (0.13.0-1) experimental;
Bug#942337: marked as done (libthrift-0.12.0: missing Breaks+Replaces: libthrift-0.11.0)
Your message dated Fri, 06 Dec 2019 13:01:06 + with message-id and subject line Bug#942337: fixed in thrift 0.13.0-1 has caused the Debian Bug report #942337, regarding libthrift-0.12.0: missing Breaks+Replaces: libthrift-0.11.0 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 942337: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=942337 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: libthrift-0.12.0 Version: 0.12.0-1 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package fails to upgrade from 'sid' to 'experimental'. It installed fine in 'sid', then the upgrade to 'experimental' 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 .../libthrift-0.12.0_0.12.0-1_amd64.deb ... Unpacking libthrift-0.12.0 (0.12.0-1) ... dpkg: error processing archive /var/cache/apt/archives/libthrift-0.12.0_0.12.0-1_amd64.deb (--unpack): trying to overwrite '/usr/lib/x86_64-linux-gnu/libthriftc.so.0.0.0', which is also in package libthrift-0.11.0 0.11.0-6 dpkg-deb: error: paste subprocess was killed by signal (Broken pipe) Errors were encountered while processing: /var/cache/apt/archives/libthrift-0.12.0_0.12.0-1_amd64.deb cheers, Andreas libthrift-0.11.0=0.11.0-6_libthrift-0.12.0=0.12.0-1.log.gz Description: application/gzip --- End Message --- --- Begin Message --- Source: thrift Source-Version: 0.13.0-1 We believe that the bug you reported is fixed in the latest version of thrift, 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. Laszlo Boszormenyi (GCS) (supplier of updated thrift 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, 01 Dec 2019 10:46:55 + Source: thrift Binary: golang-thrift-dev libthrift-0.13.0 libthrift-0.13.0-dbgsym libthrift-c-glib-dev libthrift-c-glib0 libthrift-c-glib0-dbgsym libthrift-dev libthrift-perl php-thrift php-thrift-dbgsym python3-thrift python3-thrift-dbg thrift-compiler thrift-compiler-dbgsym Architecture: source amd64 all Version: 0.13.0-1 Distribution: experimental Urgency: high Maintainer: Laszlo Boszormenyi (GCS) Changed-By: Laszlo Boszormenyi (GCS) Description: golang-thrift-dev - Go language support for Thrift libthrift-0.13.0 - Thrift C++ library libthrift-c-glib-dev - Thrift glib library (development headers) libthrift-c-glib0 - Thrift glib library libthrift-dev - Thrift C++ library (development headers) libthrift-perl - Perl language support for Thrift php-thrift - PHP language support for Thrift python3-thrift - Python 3 library for Thrift python3-thrift-dbg - Python library for Thrift (debug symbols) thrift-compiler - code generator/compiler for Thrift definitions Closes: 942337 943653 Changes: thrift (0.13.0-1) experimental; urgency=high . * New major upstream release: - fixes CVE-2019-0205: endless loop when feed with specific input data, - fixes CVE-2019-0210: Go server may panic when feed with invalid input data, - removed compiler plug-in mechanism (closes: #942337). * Rework upstream distclean process (closes: #943653). Checksums-Sha1: e6185802bed8de248513e4e91b637f2becd68daf 2946 thrift_0.13.0-1.dsc 0cbb06d047a8212c6ac1240492bc569609fecd33 4154357 thrift_0.13.0.orig.tar.gz 49e9402f7966b84adb9976be17ba7a682799ad4b 17752 thrift_0.13.0-1.debian.tar.xz 6a22e3226496fd197836fa57764eb02f5d69e41d 132812 golang-thrift-dev_0.13.0-1_amd64.deb 0c884f71dfa70f8eae57d9e1c189526bd2903a6c 4267392 libthrift-0.13.0-dbgsym_0.13.0-1_amd64.deb e0007f1f063ca951ecd8e81a6e445c2f09921a4b 328696 libthrift-0.13.0_0.13.0-1_amd64.deb 07f2269eb36a0b55bfc06ec5c143b838a1ad5022 139040 libthrift-c-glib-dev_0.13.0-1_amd64.deb 63b46602d281af815ffd8ff52274780e10adf6f3 195764 libthrift-c-glib0-dbgsym_0.13.0-1_amd64.deb
Bug#936558: marked as done (freeradius: Python2 removal in sid/bullseye)
Your message dated Fri, 06 Dec 2019 13:00:44 + with message-id and subject line Bug#936558: fixed in freeradius 3.0.20+dfsg-2 has caused the Debian Bug report #936558, regarding freeradius: 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.) -- 936558: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=936558 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:freeradius Version: 3.0.19+dfsg-3 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:freeradius 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 --- Source: freeradius Source-Version: 3.0.20+dfsg-2 We believe that the bug you reported is fixed in the latest version of freeradius, 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 936...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Bernhard Schmidt (supplier of updated freeradius package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Fri, 29 Nov 2019 23:54:37 +0100 Source: freeradius Binary: freeradius freeradius-common freeradius-config freeradius-dbgsym freeradius-dhcp freeradius-dhcp-dbgsym freeradius-iodbc freeradius-iodbc-dbgsym freeradius-krb5 freeradius-krb5-dbgsym freeradius-ldap freeradius-ldap-dbgsym freeradius-memcached freeradius-memcached-dbgsym freeradius-mysql freeradius-mysql-dbgsym freeradius-postgresql freeradius-postgresql-dbgsym freeradius-python3 freeradius-python3-dbgsym freeradius-redis freeradius-redis-dbgsym freeradius-rest freeradius-rest-dbgsym freeradius-utils freeradius-utils-dbgsym freeradius-yubikey freeradius-yubikey-dbgsym libfreeradius-dev libfreeradius3 libfreeradius3-dbgsym Architecture: source all amd64 Version: 3.0.20+dfsg-2 Distribution: experimental Urgency: medium Maintainer: Debian FreeRADIUS Packaging Team Changed-By: Bernhard Schmidt Description: freeradius - high-performance and highly configurable
Bug#938823: marked as done (wicd: Python2 removal in sid/bullseye)
Your message dated Fri, 06 Dec 2019 13:01:08 + with message-id and subject line Bug#938823: fixed in wicd 1.7.4+tb2+2019.09.18git2e0ba579-1 has caused the Debian Bug report #938823, regarding wicd: 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.) -- 938823: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=938823 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:wicd Version: 1.7.4+tb2-6 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:wicd 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 --- Source: wicd Source-Version: 1.7.4+tb2+2019.09.18git2e0ba579-1 We believe that the bug you reported is fixed in the latest version of wicd, 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 938...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Axel Beckert (supplier of updated wicd 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, 02 Dec 2019 04:47:07 +0100 Source: wicd Binary: python3-wicd wicd wicd-cli wicd-curses wicd-daemon wicd-gtk Architecture: source all Version: 1.7.4+tb2+2019.09.18git2e0ba579-1 Distribution: experimental Urgency: low Maintainer: Debian WICD Packaging Team Changed-By: Axel Beckert Description: python3-wicd - wired and wireless network manager - Python module wicd - wired and wireless network manager - metapackage wicd-cli - wired and wireless network manager - scriptable console client wicd-curses - wired and wireless network manager - Curses client wicd-daemon - wired and wireless network manager - daemon wicd-gtk - wired and wireless network manager - GTK+ client Closes: 833929 852343 901592 938823 Changes: wicd (1.7.4+tb2+2019.09.18git2e0ba579-1) experimental; urgency=low . Upload to experimental to get a broader testing base of the python3 port and the dhcpcd5 changes. Not yet fully functional again. .
Bug#946264: openems: FTBFS (affects CGAL transition)
Source: openems Version: 0.0.35+git20190103.6a75e98+dfsg.1-1 Severity: serious Tags: ftbfs Control: block 944417 by -1 Hi, the transition to CGAL 5.0 started (see bug #944417). A binNMU would have been sufficient, but your package FTBFS for unrelated reasons. See https://buildd.debian.org/status/package.php?p=openems . This might be the same problem as in bug #944144, but I'm not sure. Best regards, Joachim
Bug#938600: marked as done (sunpinyin: Python2 removal in sid/bullseye)
Your message dated Fri, 06 Dec 2019 13:01:05 +
with message-id
and subject line Bug#938600: fixed in sunpinyin 3.0.0~rc1+ds1-3~exp1
has caused the Debian Bug report #938600,
regarding sunpinyin: 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.)
--
938600: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=938600
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:sunpinyin
Version: 3.0.0~rc1+ds1-2
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:sunpinyin
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 ---
Source: sunpinyin
Source-Version: 3.0.0~rc1+ds1-3~exp1
We believe that the bug you reported is fixed in the latest version of
sunpinyin, 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 938...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Changwoo Ryu (supplier of updated sunpinyin package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Tue, 03 Dec 2019 18:42:41 +0900
Source: sunpinyin
Binary: libsunpinyin-dev libsunpinyin3v5 libsunpinyin3v5-dbgsym
python3-sunpinyin sunpinyin-utils sunpinyin-utils-dbgsym
Architecture: source amd64 all
Version: 3.0.0~rc1+ds1-3~exp1
Distribution: experimental
Urgency: medium
Maintainer: Debian Input Method Team
Changed-By: Changwoo Ryu
Description:
libsunpinyin-dev - Simplified Chinese Input Method from SUN (development)
libsunpinyin3v5 - Simplified Chinese Input Method from SUN (runtime)
python3-sunpinyin - Simplified Chinese Input Method from SUN (Python binding)
sunpinyin-utils - Simplified Chinese Input Method from SUN (utilities)
Closes: 938600
Changes:
sunpinyin (3.0.0~rc1+ds1-3~exp1) experimental; urgency=medium
.
* Team upload.
* Use python 3 instead of python 2 (Closes: #938600)
- debian/{control,rules}: Use python3, drop python-sunpinyin, build
python3-sunpinyin
-
Processed: openems: FTBFS (affects CGAL transition)
Processing control commands: > block 944417 by -1 Bug #944417 [release.debian.org] transition: cgal 944417 was blocked by: 946119 946228 946234 946114 944775 946116 944776 946229 946223 944417 was not blocking any bugs. Added blocking bug(s) of 944417: 946264 -- 944417: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=944417 946264: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=946264 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#938262: marked as done (python-whiteboard: Python2 removal in sid/bullseye)
Your message dated Fri, 06 Dec 2019 13:01:03 + with message-id and subject line Bug#938262: fixed in python-whiteboard 1.0+git20170915-3 has caused the Debian Bug report #938262, regarding python-whiteboard: 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.) -- 938262: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=938262 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:python-whiteboard Version: 1.0+git20170915-2 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:python-whiteboard 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 --- Source: python-whiteboard Source-Version: 1.0+git20170915-3 We believe that the bug you reported is fixed in the latest version of python-whiteboard, 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 938...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Georges Khaznadar (supplier of updated python-whiteboard package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Sun, 01 Dec 2019 19:43:04 +0100 Source: python-whiteboard Binary: python3-whiteboard Architecture: source all Version: 1.0+git20170915-3 Distribution: unstable Urgency: medium Maintainer: Georges Khaznadar Changed-By: Georges Khaznadar Description: python3-whiteboard - Make your own electronic whiteboard Closes: 938262 Changes: python-whiteboard (1.0+git20170915-3) unstable; urgency=medium . * renamed the binary package as python3-whiteboard * ported scripts to python3, removed dependencies on Python2. Closes: #938262 * bumped standards-version to 4.3.0, dh level to 11 Checksums-Sha1: 19e992b1cc1a21bb34eede4aa93ba4b34dc95f16 2082 python-whiteboard_1.0+git20170915-3.dsc 7d6ba945778066db74a9b942e5f7b7a735e1c076 6704 python-whiteboard_1.0+git20170915-3.debian.tar.xz 37b67f52c972e57cecfa99280dc19ebf371d7ec0 10948
Bug#936736: marked as done (input-pad: Python2 removal in sid/bullseye)
Your message dated Fri, 06 Dec 2019 13:00:46 + with message-id and subject line Bug#936736: fixed in input-pad 1.0.3-4~exp1 has caused the Debian Bug report #936736, regarding input-pad: 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.) -- 936736: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=936736 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:input-pad Version: 1.0.3-3 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:input-pad 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 --- Source: input-pad Source-Version: 1.0.3-4~exp1 We believe that the bug you reported is fixed in the latest version of input-pad, 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 936...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Changwoo Ryu (supplier of updated input-pad 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: Wed, 04 Dec 2019 08:52:18 +0900 Source: input-pad Binary: gir1.2-input-pad-1.0 input-pad input-pad-dbgsym libinput-pad-dev libinput-pad-xtest libinput-pad-xtest-dbgsym libinput-pad1 libinput-pad1-dbgsym python3-input-pad python3-input-pad-dbgsym Architecture: source amd64 Version: 1.0.3-4~exp1 Distribution: experimental Urgency: medium Maintainer: Debian Input Method Team Changed-By: Changwoo Ryu Description: gir1.2-input-pad-1.0 - On-screen Input Pad to Send Characters with Mouse - introspection input-pad - On-screen Input Pad to Send Characters with Mouse libinput-pad-dev - On-screen Input Pad to Send Characters with Mouse - dev libinput-pad-xtest - On-screen Input Pad to Send Characters with Mouse - xtest libinput-pad1 - On-screen Input Pad to Send Characters with Mouse - libs python3-input-pad - On-screen Input Pad to Send Characters with Mouse - python Closes: 936736 Changes: input-pad (1.0.3-4~exp1) experimental; urgency=medium
Bug#936274: marked as done (casacore: Python2 removal in sid/bullseye)
Your message dated Fri, 06 Dec 2019 13:00:14 + with message-id and subject line Bug#936274: fixed in casacore 3.2.1-1 has caused the Debian Bug report #936274, regarding casacore: 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.) -- 936274: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=936274 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:casacore Version: 3.0.0-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:casacore 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 --- Source: casacore Source-Version: 3.2.1-1 We believe that the bug you reported is fixed in the latest version of casacore, 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 936...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Ole Streicher (supplier of updated casacore package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Tue, 26 Nov 2019 10:26:21 +0100 Source: casacore Binary: casacore-dev casacore-doc casacore-tools casacore-tools-dbgsym libcasa-casa4 libcasa-casa4-dbgsym libcasa-coordinates4 libcasa-coordinates4-dbgsym libcasa-derivedmscal4 libcasa-derivedmscal4-dbgsym libcasa-fits4 libcasa-fits4-dbgsym libcasa-images4 libcasa-images4-dbgsym libcasa-lattices4 libcasa-lattices4-dbgsym libcasa-meas4 libcasa-meas4-dbgsym libcasa-measures4 libcasa-measures4-dbgsym libcasa-mirlib4 libcasa-mirlib4-dbgsym libcasa-ms4 libcasa-ms4-dbgsym libcasa-msfits4 libcasa-msfits4-dbgsym libcasa-python3-4 libcasa-python3-4-dbgsym libcasa-scimath-f4 libcasa-scimath-f4-dbgsym libcasa-scimath4 libcasa-scimath4-dbgsym libcasa-tables4 libcasa-tables4-dbgsym Architecture: source amd64 all Version: 3.2.1-1 Distribution: experimental Urgency: low Maintainer: Debian Astro Team Changed-By: Ole Streicher Description: casacore-dev - CASA core library development files casacore-doc - CASA core
Bug#945338: libpetsc3.11-dev-examples: postinst uses /usr/share/doc content (Policy 12.3): /usr/share/doc/libpetsc3.11-dev-examples/examples/**/*.py
On Sat, 23 Nov 2019 04:18:43 +0100 Andreas Beckmann wrote: > Package: libpetsc3.11-dev-examples > Version: 3.11.4+dfsg1-3 > Severity: serious > User: debian...@lists.debian.org > Usertags: piuparts > > Hi, > > a test with piuparts revealed that your package uses files from > /usr/share/doc in its maintainer scripts which is a violation of > Policy 12.3: "Packages must not require the existence of any files in > /usr/share/doc/ in order to function." > https://www.debian.org/doc/debian-policy/ch-docs.html#additional-documentation > > These files must be moved to /usr/share/$PACKAGE and may be symlinked > from /usr/share/doc/$PACKAGE. > > This piuparts test prevents the installation of (most) files into > /usr/share/doc with 'dpkg --path-exclude=...'. > > From the attached log (scroll to the bottom...): > > Setting up python3 (3.7.5-1) ... > [Errno 2] No such file or directory: '/usr/share/doc/libpetsc3.11-dev-examples/examples/config/cmakegen.py' > [Errno 2] No such file or directory: '/usr/share/doc/libpetsc3.11-dev-examples/examples/config/example_template.py' > [Errno 2] No such file or directory: '/usr/share/doc/libpetsc3.11-dev-examples/examples/config/gmakegen.py' > [Errno 2] No such file or directory: '/usr/share/doc/libpetsc3.11-dev-examples/examples/config/gmakegentest.py' > [Errno 2] No such file or directory: '/usr/share/doc/libpetsc3.11-dev-examples/examples/config/report_tests.py' > [Errno 2] No such file or directory: '/usr/share/doc/libpetsc3.11-dev-examples/examples/config/testparse.py' > [Errno 2] No such file or directory: '/usr/share/doc/libpetsc3.11-dev-examples/examples/src/ksp/ksp/examples/tutorials/ex100.py' > [Errno 2] No such file or directory: '/usr/share/doc/libpetsc3.11-dev-examples/examples/src/ksp/ksp/examples/tutorials/example100.py' > [Errno 2] No such file or directory: '/usr/share/doc/libpetsc3.11-dev-examples/examples/src/ts/examples/tutorials/ex8.py' > [Errno 2] No such file or directory: '/usr/share/doc/libpetsc3.11-dev-examples/examples/src/ts/examples/tutorials/extchem.py' > error running python rtupdate hook libpetsc3.11-dev-examples > dpkg: error processing package python3 (--configure): >installed python3 package post-installation script subprocess returned error exit status 4 > dpkg: dependency problems prevent configuration of libpetsc3.11-dev-examples: >libpetsc3.11-dev-examples depends on python3:any; however: > Package python3 is not configured yet. > > dpkg: error processing package libpetsc3.11-dev-examples (--configure): >dependency problems - leaving unconfigured > Processing triggers for libc-bin (2.29-3) ... > Errors were encountered while processing: >python3 >libpetsc3.11-dev-examples > With this fix, there is no more issue with piuparts. I have checked that the package pestc 3.11 can be installed on Ubuntu Eoan without problem Hope it helps Best C --- petsc-3.11.4+dfsg1/debian/rules 2019-11-11 18:52:48.0 +0100 +++ my-petsc-3.11.4+dfsg1/debian/rules 2019-12-06 10:27:40.251657187 +0100 @@ -292,17 +365,22 @@ override_dh_install: dh_install -p$(PETSC_REAL_PACKAGE) --sourcedir $(PACKAGE_REAL_INSTALL_DIR) $(PETSC_REAL_DIR_PREFIX)/lib/libpetsc_real.so.$(PETSC_VERSION) usr/lib/$(DEB_HOST_MULTIARCH) dh_install -p$(PETSC_REAL_DEV_PACKAGE) --sourcedir $(PACKAGE_REAL_INSTALL_DIR) --autodest --exclude=*html --exclude=conf/uninstall.py --exclude=libpetsc_real.so.$(PETSC_VERSION) --exclude=share/ --exclude=include/petsc/ --exclude=lib/petsc/bin/ usr - + dh_install -p$(PETSC_REAL_DEBUG_PACKAGE) --sourcedir $(PACKAGE_REAL_DEBUG_INSTALL_DIR) --autodest --exclude=*html --exclude=conf/uninstall.py --exclude=share/ --exclude=include/petsc/ --exclude=lib/petsc/bin/ usr - + dh_install -p$(PETSC_COMPLEX_PACKAGE) --sourcedir $(PACKAGE_COMPLEX_INSTALL_DIR) $(PETSC_COMPLEX_DIR_PREFIX)/lib/libpetsc_complex.so.$(PETSC_VERSION) usr/lib/$(DEB_HOST_MULTIARCH) dh_install -p$(PETSC_COMPLEX_DEV_PACKAGE) --sourcedir $(PACKAGE_COMPLEX_INSTALL_DIR) --autodest --exclude=*html --exclude=conf/uninstall.py --exclude=libpetsc_complex.so.$(PETSC_VERSION) --exclude=share/ --exclude=include/petsc/ --exclude=lib/petsc/bin/ usr - + dh_install -p$(PETSC_COMPLEX_DEBUG_PACKAGE) --sourcedir $(PACKAGE_COMPLEX_DEBUG_INSTALL_DIR) --autodest --exclude=*html --exclude=conf/uninstall.py --exclude=share/ --exclude=include/petsc/ --exclude=lib/petsc/bin/ usr - + dh_install -p$(PETSC_DEV_COMMON_PACKAGE) --sourcedir $(PACKAGE_REAL_DEBUG_INSTALL_DIR)/$(PETSC_REAL_DIR_DEBUG_PREFIX) --exclude=share/petsc/examples/ --exclude=share/petsc/datafiles/ share usr/share/petsc/$(PETSC_SONAME_VERSION) dh_install -p$(PETSC_DEV_COMMON_PACKAGE) --sourcedir $(PACKAGE_REAL_DEBUG_INSTALL_DIR)/$(PETSC_REAL_DIR_DEBUG_PREFIX) --exclude=*html include/petsc usr/share/petsc/$(PETSC_SONAME_VERSION)/include dh_install -p$(PETSC_DEV_COMMON_PACKAGE) --sourcedir $(PACKAGE_REAL_DEBUG_INSTALL_DIR)/$(PETSC_REAL_DIR_DEBUG_PREFIX)
Bug#938572: marked as done (stimfit: Python2 removal in sid/bullseye)
Your message dated Fri, 06 Dec 2019 12:00:19 + with message-id and subject line Bug#938572: fixed in stimfit 0.16.0-1 has caused the Debian Bug report #938572, regarding stimfit: 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.) -- 938572: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=938572 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:stimfit Version: 0.15.8-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:stimfit 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 --- Source: stimfit Source-Version: 0.16.0-1 We believe that the bug you reported is fixed in the latest version of stimfit, 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 938...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Christoph Schmidt-Hieber (supplier of updated stimfit package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Tue, 26 Nov 2019 09:35:41 +0200 Source: stimfit Binary: python3-stfio stimfit stimfit-dbg Architecture: source amd64 Version: 0.16.0-1 Distribution: unstable Urgency: low Maintainer: Christoph Schmidt-Hieber Changed-By: Christoph Schmidt-Hieber Description: python3-stfio - Python module to read common electrophysiology file formats. stimfit- Program for viewing and analyzing electrophysiological data stimfit-dbg - Debug symbols for stimfit Closes: 938572 Changes: stimfit (0.16.0-1) unstable; urgency=low . * Upgrade to Python 3 (Closes: #938572) Checksums-Sha1: 8da62e1f7d30d83342e67065472e9ae4939f0959 2134 stimfit_0.16.0-1.dsc 4a238b73a475bae781c31a2220d8df99050529cd 2646705 stimfit_0.16.0.orig.tar.gz 1bcd6b589acab49bfc4e2f824a4913e8a8eb0243 8600 stimfit_0.16.0-1.debian.tar.xz 87dd6db953e81ca9f98fe36b1d4eb858b606802f 483364 python3-stfio_0.16.0-1_amd64.deb c5333c2281eaf2a3f0de7722c583eee0946db90f 11270724 stimfit-dbg_0.16.0-1_amd64.deb
Bug#938793: marked as done (vmdk-stream-converter: Python2 removal in sid/bullseye)
Your message dated Fri, 06 Dec 2019 12:00:20 + with message-id and subject line Bug#938793: fixed in vmdk-stream-converter 0.2-4.1~exp0 has caused the Debian Bug report #938793, regarding vmdk-stream-converter: 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.) -- 938793: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=938793 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:vmdk-stream-converter Version: 0.2-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:vmdk-stream-converter 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 --- Source: vmdk-stream-converter Source-Version: 0.2-4.1~exp0 We believe that the bug you reported is fixed in the latest version of vmdk-stream-converter, 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 938...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Balint Reczey (supplier of updated vmdk-stream-converter 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: Wed, 27 Nov 2019 15:01:52 +0100 Source: vmdk-stream-converter Binary: python3-vmdkstream vmdk-stream-converter Architecture: source all Version: 0.2-4.1~exp0 Distribution: experimental Urgency: medium Maintainer: Hideki Yamane Changed-By: Balint Reczey Description: python3-vmdkstream - Python 3 module for converting raw disk images to VMDK files vmdk-stream-converter - transitional dummy package Closes: 883804 938793 Changes: vmdk-stream-converter (0.2-4.1~exp0) experimental; urgency=medium . * Non-maintainer upload * Switch to Python 3 (LP: #1735370) (Closes: #883804, #938793) * Rename main package to python3-vmdkstream to follow Python 3 module naming policy * debian/control: Simplify build dependencies Checksums-Sha1: fa881f6e2a381feb6f2bb210080e0ce9da9734c1 2075 vmdk-stream-converter_0.2-4.1~exp0.dsc
Bug#946199: akonadi-backend-postgresql: akonadictl fails to start with postgresql backend
On donderdag 5 december 2019 15:34:37 CET Sandro Knauß wrote: > do you have apparmor enabled? Maybe the Apparmor profile does not match > anymore. Can you give it a try with aa-disable postgresql_akonadi? I have akonadi-backend-postgresql and apparmor enabled and it is working for me. I only have PostgreSQL 12 though. https://lists.debian.org/debian-kde/2019/11/msg0.html shows the way I upgraded to PSQL 12 (and purged PSQL 11) If you have both, but didn't upgrade your cluster (ie transfer your akonadi database to PSQL 12) and rebooted, then I think PSQL 12 uses the default PSQL port. If you didn't change your config, then akonadi is asking PSQL 12 for its data, but it can't find it. That could be an explanation why it isn't working for Vincent-Xavier. signature.asc Description: This is a digitally signed message part.
Bug#946179: [lxcfs] lxcfs tries to delete systemd cgroup folders, fails stopping lxc
Control: severity -1 normal Hi, Thanks for reporting this. The main issue with starting the container does not seem to have anything to do with the failing cgroup_rmdir calls even though I admit they shouldn't occur. The main issue lies in """lxc-start 20191204112931.790 ERROR lxc_cgfs - cgroups/cgfs.c:lxc_cgroupfs_create:901 - Could not find writable mount point for cgroup hierarchy 11 while trying to create cgroup.""" A fix has been released in 2.0.8 by upstream, and I'll have a look at the possibility to have this version released in stretch. But, this bug is not as grave as you seem to think. I'm therefore lowering the severity of the bug to the appropriate level. With best regards, -- Pierre-Elliott Bécue GPG: 9AE0 4D98 6400 E3B6 7528 F493 0D44 2664 1949 74E2 It's far easier to fight for one's principles than to live up to them.
Processed: Re: Bug#946179: [lxcfs] lxcfs tries to delete systemd cgroup folders, fails stopping lxc
Processing control commands: > severity -1 normal Bug #946179 [lxcfs] [lxcfs] lxcfs tries to delete systemd cgroup folders, fails stopping lxc Severity set to 'normal' from 'grave' -- 946179: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=946179 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#946198: Since upgrading to 1.25.13 no remote printer is made available anymore
> Which printers list? An application dialog? Oops, sorry, I was referring to the printers tab on localhost:631. In the add printer dialog on the administration tab they are still listed. All application dialogs do not list the printers anymore either. > The outputs of 'lpstat -a' and 'lpstat -l -e', please. Activating > logging 'lpstat -a' does not list any of the printers, 'lpstat -l -e' lists them all. > in cups-browsed.conf and taking a look at a log wouldn't be a bad > idea. Fri Dec 6 11:00:58 2019 Removing entry B... (ipps://host.local:631/printers/B...) and its CUPS queue. Fri Dec 6 11:00:58 2019 Recording printer options for B... to /var/cache/cups/cups-browsed-options-B... Fri Dec 6 11:00:58 2019 Unable to get PPD file for B...: The printer or class does not exist. Fri Dec 6 11:00:58 2019 Unable to load PPD from local queue B..., queue seems to be raw. Fri Dec 6 11:00:58 2019 ERROR: Failed disabling printer 'B...': The printer or class does not exist. I guess that explains why the printer is no longer active, but what changed from the prior version of cups-browsed? I just verified again, downgrading cups-browsed from 1.25.13-1 to 1.25.12-1 fixes the problem and makes the printers appear again. And, yes, I can print on any of them without an issue. Or in other words, the system does have a PPD for the printer. Any idea? Michael -- Michael Meskes Michael at Fam-Meskes dot De, Michael at Meskes dot (De|Com|Net|Org) Meskes at (Debian|Postgresql) dot Org Jabber: michael at xmpp dot meskes dot org VfL Borussia! Força Barça! SF 49ers! Use Debian GNU/Linux, PostgreSQL
Bug#946234:
Upstream 0.5.0 now builds against CGAL 5, so we only need an upload here.
Bug#945840: /usr/bin/ledger: error while loading shared libraries: libboost_python27.so.1.67.0: cannot open shared object file: No such file or directory
Il 05/12/19 22:37, Dimitri John Ledkov ha scritto: > All python2 bugs for leaf packages have been made RC on like 30th of > november, causing a tonne of packages to be scheduled for autoremoval. > Most of them are on 18th/19th December. See tracker.d.o for various > leaf packages. That's only from testing. I still believe that unstable should not be broken if it can be avoided at nearly zero cost. However, I see your point now. I think disabling Python 2 should have been handled differently (i.e., not disabling it in Boost before all the rev deps in unstable wouldn't use it any more), but let's call it a day and avoid uselessly escalating this. I will not re-enable Python 2 in boost1.67. Thanks for working on this anyway. Giovanni. -- Giovanni Mascellani Postdoc researcher - Université Libre de Bruxelles signature.asc Description: OpenPGP digital signature
