Bug#938909: Dealing with zope.interface unsatisfiable build-dependency.

2019-12-06 Thread peter green
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 depend

Bug#920369: marked as done (boost1.62: do not release with buster)

2019-12-06 Thread Debian Bug Tracking System
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 deal

Bug#914043: marked as done (boost-defaults breaks boost1.62 autopkgtest)

2019-12-06 Thread Debian Bug Tracking System
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 bee

Bug#885364: marked as done (pybootchartgui: Depends on unmaintained pygtk)

2019-12-06 Thread Debian Bug Tracking System
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 b

Bug#944775: marked as done (FTBFS with CGAL 5.0)

2019-12-06 Thread Debian Bug Tracking System
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

Bug#946030: marked as done (xul-ext-firetray classified as a legacy extension by Thunderbird 68.2.2 (Debian Stable AMD64))

2019-12-06 Thread Debian Bug Tracking System
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.

Bug#936228: marked as done (bootchart2: Python2 removal in sid/bullseye)

2019-12-06 Thread Debian Bug Tracking System
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 bee

Bug#944776: marked as done (FTBFS with CGAL 5.0)

2019-12-06 Thread Debian Bug Tracking System
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

Bug#945796: marked as done (rust-url-serde: (build-)depends on obsolete virtual package.)

2019-12-06 Thread Debian Bug Tracking System
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 th

Bug#937005: marked as done (meep-mpich2: Python2 removal in sid/bullseye)

2019-12-06 Thread Debian Bug Tracking System
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 be

Bug#943070: marked as done (inosync: Python2 removal in sid/bullseye)

2019-12-06 Thread Debian Bug Tracking System
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 d

Bug#936221: marked as done (blueproximity: Python2 removal in sid/bullseye)

2019-12-06 Thread Debian Bug Tracking System
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

Bug#885139: marked as done (blueproximity: Depends on unmaintained pygtk)

2019-12-06 Thread Debian Bug Tracking System
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 be

Bug#941877: marked as done (volti: Depends on unmaintained pygtk)

2019-12-06 Thread Debian Bug Tracking System
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

Bug#937004: marked as done (meep-lam4: Python2 removal in sid/bullseye)

2019-12-06 Thread Debian Bug Tracking System
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

Bug#938799: marked as done (volti: Python2 removal in sid/bullseye)

2019-12-06 Thread Debian Bug Tracking System
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 dea

Bug#938463: marked as done (selectors34: Python2 removal in sid/bullseye)

2019-12-06 Thread Debian Bug Tracking System
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 be

Bug#936894: marked as done (libmpikmeans: Python2 removal in sid/bullseye)

2019-12-06 Thread Debian Bug Tracking System
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 b

Bug#937433: marked as done (pyevolve: Python2 removal in sid/bullseye)

2019-12-06 Thread Debian Bug Tracking System
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

Bug#936689: marked as done (hachoir-subfile: Python2 removal in sid/bullseye)

2019-12-06 Thread Debian Bug Tracking System
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 ha

Bug#936691: marked as done (hachoir-wx: Python2 removal in sid/bullseye)

2019-12-06 Thread Debian Bug Tracking System
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 bee

Bug#936686: marked as done (hachoir-metadata: Python2 removal in sid/bullseye)

2019-12-06 Thread Debian Bug Tracking System
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 h

Bug#942191: marked as done (Depends on qt4)

2019-12-06 Thread Debian Bug Tracking System
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

Bug#913597: marked as done (polyorb depends and build depends on gnat-7)

2019-12-06 Thread Debian Bug Tracking System
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 bee

Bug#936972: marked as done (lunch: Python2 removal in sid/bullseye)

2019-12-06 Thread Debian Bug Tracking System
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 dea

Bug#885513: marked as done (python-lunch: Recommends unmaintained pygtk)

2019-12-06 Thread Debian Bug Tracking System
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 bee

Bug#946234: marked as done ([NMU] FTFBS with CGAL 5.0 (if cmake is absent))

2019-12-06 Thread Debian Bug Tracking System
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 d

Bug#945501: python-statsmodels-doc: unhandled symlink to directory conversion: /usr/share/doc/python-statsmodels-doc/examples

2019-12-06 Thread peter green
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 sa

Processed: re: html5-parser: Python2 removal in sid/bullseye

2019-12-06 Thread Debian Bug Tracking System
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

Bug#936710: html5-parser: Python2 removal in sid/bullseye

2019-12-06 Thread peter green
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

2019-12-06 Thread Debian Bug Tracking System
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/cg

Processed: tagging 938793, tagging 936274, tagging 936558, tagging 936736, tagging 938600, tagging 946289

2019-12-06 Thread Debian Bug Tracking System
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:casa

Bug#946293: marked as done (Dependency problems between espeakup-udeb and espeak-ng-data-udeb breaking d-i builds)

2019-12-06 Thread Debian Bug Tracking System
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-image

Bug#946311: libpcre2-dev 10.34-5 dependency errors

2019-12-06 Thread Сергей Фёдоров
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) Lo

Bug#944851: closing 944851

2019-12-06 Thread Salvatore Bonaccorso
close 944851 1.4.18-1 thanks

Processed: closing 944851

2019-12-06 Thread Debian Bug Tracking System
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 assistanc

Bug#941971: marked as done (raspi3-firmware: serial console output sent to bluetooth port with kernel 5.x)

2019-12-06 Thread Debian Bug Tracking System
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

Bug#946306: jsonld-java: FTBFS in sid

2019-12-06 Thread Gianfranco Costamagna
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: sou

Bug#921220: marked as done (xchat.desktop makes invalid use of %U, breaks at least lxqt and flwm)

2019-12-06 Thread Debian Bug Tracking System
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

Bug#946304: jsonpickle: FTBFS in sid

2019-12-06 Thread Gianfranco Costamagna
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

Bug#946293: Dependency problems between espeakup-udeb and espeak-ng-data-udeb breaking d-i builds

2019-12-06 Thread Paul Gevers
age: 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

Processed: Re: Bug#946293: Dependency problems between espeakup-udeb and espeak-ng-data-udeb breaking d-i builds

2019-12-06 Thread Debian Bug Tracking System
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.deb

Bug#946238: marked as done (openstack-dashboard-apache: modifies conffiles (policy 10.7.3): /etc/openstack-dashboard/local_settings.d/_0005_debian_webroot.py)

2019-12-06 Thread Debian Bug Tracking System
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_we

Bug#946293: Dependency problems between espeakup-udeb and espeak-ng-data-udeb breaking d-i builds

2019-12-06 Thread Steve McIntyre
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 pac

Bug#946287: marked as done (webext-compactheader: too low dependency on thunderbird)

2019-12-06 Thread Debian Bug Tracking System
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

Bug#944636: marked as done (insighttoolkit4: CMake missing files for imported targets)

2019-12-06 Thread Debian Bug Tracking System
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 tha

Bug#946238: marked as pending in horizon

2019-12-06 Thread Thomas Goirand
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/c62c238be3757baf7f7

Processed: Bug#946238 marked as pending in horizon

2019-12-06 Thread Debian Bug Tracking System
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.cg

Bug#946290: libpcre2-posix2:amd64 is uninstallable

2019-12-06 Thread Matthew Vernon
forcemerge 946279 946290 quit Hi, Please check the BTS for duplicates before filing bugs. Thanks, Matthew

Processed: Tagging a couple of things

2019-12-06 Thread Debian Bug Tracking System
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 test

Processed: tagging 946225, tagging 946228

2019-12-06 Thread Debian Bug Tracking System
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.

Processed (with 1 error): Re: Bug#946290: libpcre2-posix2:amd64 is uninstallable

2019-12-06 Thread Debian Bug Tracking System
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 no

Bug#946290: libpcre2-posix2:amd64 is uninstallable

2019-12-06 Thread Roman Lebedev
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_

Bug#946289: ufw: fails to start with iptables 1.8.4

2019-12-06 Thread Antonio Terceiro
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

Bug#946287: webext-compactheader: too low dependency on thunderbird

2019-12-06 Thread Sven Joachim
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

Bug#937657: marked as done (python-colormap: Python2 removal in sid/bullseye)

2019-12-06 Thread Debian Bug Tracking System
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 ha

Bug#946279: pcre2: Failure when upgrading: file overwrite (libpcre2-posix.so.2.0.3)

2019-12-06 Thread Matthew Vernon
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

Bug#936704: marked as done (hinge: Python2 removal in sid/bullseye)

2019-12-06 Thread Debian Bug Tracking System
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. I

Bug#946279: pcre2: Failure when upgrading: file overwrite (libpcre2-posix.so.2.0.3)

2019-12-06 Thread Boyuan Yang
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

Processed: Re: Bug#946198: Since upgrading to 1.25.13 no remote printer is made available anymore

2019-12-06 Thread Debian Bug Tracking System
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.d

Bug#946198: Since upgrading to 1.25.13 no remote printer is made available anymore

2019-12-06 Thread Brian Potkin
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 appli

Bug#945970: marked as done (meep: Incomplete debian/copyright?)

2019-12-06 Thread Debian Bug Tracking System
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 th

Bug#940491: marked as done (src:meep: missing several Breaks+Replaces)

2019-12-06 Thread Debian Bug Tracking System
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

Bug#937196: marked as done (opencolorio: Python2 removal in sid/bullseye)

2019-12-06 Thread Debian Bug Tracking System
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

Bug#946267: cpio -i --no-absolute-filenames breaks symlinks starting with / or /..

2019-12-06 Thread Raphaël Hertzog
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

Processed: cpio -i --no-absolute-filenames breaks symlinks starting with / or /..

2019-12-06 Thread Debian Bug Tracking System
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 o

Bug#946234: [NMU] FTFBS with CGAL 5.0 (if cmake is absent)

2019-12-06 Thread Nico Schlömer
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

Bug#946234: [NMU] FTFBS with CGAL 5.0 (if cmake is absent)

2019-12-06 Thread Joachim Reichel
> 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)

2019-12-06 Thread Debian Bug Tracking System
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

Bug#945234: marked as done (cupp: Renaming cupp3 to cupp breaks Debian Sid/Bullseye repository)

2019-12-06 Thread Debian Bug Tracking System
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 c

Bug#944021: marked as done (xul-ext-compactheader: not compatible with thunderbird 68)

2019-12-06 Thread Debian Bug Tracking System
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 t

Bug#943653: marked as done (thrift: fails to clean after build: cannot find java)

2019-12-06 Thread Debian Bug Tracking System
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 be

Bug#942337: marked as done (libthrift-0.12.0: missing Breaks+Replaces: libthrift-0.11.0)

2019-12-06 Thread Debian Bug Tracking System
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

Bug#936558: marked as done (freeradius: Python2 removal in sid/bullseye)

2019-12-06 Thread Debian Bug Tracking System
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 be

Bug#938823: marked as done (wicd: Python2 removal in sid/bullseye)

2019-12-06 Thread Debian Bug Tracking System
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 proble

Bug#946264: openems: FTBFS (affects CGAL transition)

2019-12-06 Thread Joachim Reichel
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/

Bug#938600: marked as done (sunpinyin: Python2 removal in sid/bullseye)

2019-12-06 Thread Debian Bug Tracking System
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 h

Processed: openems: FTBFS (affects CGAL transition)

2019-12-06 Thread Debian Bug Tracking System
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/

Bug#938262: marked as done (python-whiteboard: Python2 removal in sid/bullseye)

2019-12-06 Thread Debian Bug Tracking System
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

Bug#936736: marked as done (input-pad: Python2 removal in sid/bullseye)

2019-12-06 Thread Debian Bug Tracking System
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

Bug#936274: marked as done (casacore: Python2 removal in sid/bullseye)

2019-12-06 Thread Debian Bug Tracking System
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 w

Bug#945338: libpetsc3.11-dev-examples: postinst uses /usr/share/doc content (Policy 12.3): /usr/share/doc/libpetsc3.11-dev-examples/examples/**/*.py

2019-12-06 Thread Christophe Trophime
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

Bug#938572: marked as done (stimfit: Python2 removal in sid/bullseye)

2019-12-06 Thread Debian Bug Tracking System
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 wi

Bug#938793: marked as done (vmdk-stream-converter: Python2 removal in sid/bullseye)

2019-12-06 Thread Debian Bug Tracking System
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 th

Bug#946199: akonadi-backend-postgresql: akonadictl fails to start with postgresql backend

2019-12-06 Thread Diederik de Haas
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

Bug#946179: [lxcfs] lxcfs tries to delete systemd cgroup folders, fails stopping lxc

2019-12-06 Thread Pierre-Elliott Bécue
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

Processed: Re: Bug#946179: [lxcfs] lxcfs tries to delete systemd cgroup folders, fails stopping lxc

2019-12-06 Thread Debian Bug Tracking System
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.

Bug#946198: Since upgrading to 1.25.13 no remote printer is made available anymore

2019-12-06 Thread Michael Meskes
> 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

Bug#946234:

2019-12-06 Thread Nico Schlömer
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

2019-12-06 Thread Giovanni Mascellani
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