Bug#923376: marked as done (Should only be in unstable)

Your message dated Fri, 06 Sep 2019 05:34:10 + with message-id and subject line Bug#939532: Removed package(s) from unstable has caused the Debian Bug report #923376, regarding Should only be in unstable to be marked as done. This means that you claim that the problem has been dealt with. If

Bug#936229: marked as done (bootstrap-vz: Python2 removal in sid/bullseye)

Your message dated Fri, 06 Sep 2019 05:34:56 + with message-id and subject line Bug#939485: Removed package(s) from unstable has caused the Debian Bug report #936229, regarding bootstrap-vz: Python2 removal in sid/bullseye to be marked as done. This means that you claim that the problem has

Bug#906564: marked as done ([buildnotify] Future Qt4 removal)

Your message dated Fri, 06 Sep 2019 05:34:32 + with message-id and subject line Bug#939525: Removed package(s) from unstable has caused the Debian Bug report #906564, regarding [buildnotify] Future Qt4 removal to be marked as done. This means that you claim that the problem has been dealt

Bug#938956: marked as done (python3-hpilo: missing Breaks+Replaces: python-hpilo)

Your message dated Fri, 06 Sep 2019 04:50:08 + with message-id and subject line Bug#938956: fixed in python-hpilo 4.3-3 has caused the Debian Bug report #938956, regarding python3-hpilo: missing Breaks+Replaces: python-hpilo to be marked as done. This means that you claim that the problem

Bug#938956: marked as pending in python-hpilo

Control: tag -1 pending Hello, Bug #938956 in python-hpilo 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:

Processed: Bug#938956 marked as pending in python-hpilo

Processing control commands: > tag -1 pending Bug #938956 [python3-hpilo] python3-hpilo: missing Breaks+Replaces: python-hpilo Added tag(s) pending. -- 938956: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=938956 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#939044: ocrmypdf: autopkgtest not compatible with new pikepdf, ghostscript and/or pytest

Hello Jonas, On Sat 31 Aug 2019 at 03:58PM +02, Jonas Smedegaard wrote: > Possibly some of the other tools uses undocumented insecure ghostscript > calls which was recently removed. > > To investigate that further, someone needs to extract the actual input > (probably Postscript or PDF) and the

Bug#938955: marked as done (pylint-doc: missing Breaks+Replaces: pylint (<< 2))

Your message dated Fri, 06 Sep 2019 04:05:14 + with message-id and subject line Bug#938955: fixed in pylint 2.2.2-3 has caused the Debian Bug report #938955, regarding pylint-doc: missing Breaks+Replaces: pylint (<< 2) to be marked as done. This means that you claim that the problem has been

Bug#933527: marked as done (snakemake: fails to install: SyntaxError: duplicate argument 'stay_on_remote' in function definition)

Your message dated Fri, 06 Sep 2019 04:07:05 + with message-id and subject line Bug#933527: fixed in snakemake 5.5.4-1 has caused the Debian Bug report #933527, regarding snakemake: fails to install: SyntaxError: duplicate argument 'stay_on_remote' in function definition to be marked as

Bug#938955: marked as pending in pylint

Control: tag -1 pending Hello, Bug #938955 in pylint 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:

Processed: Bug#938955 marked as pending in pylint

Processing control commands: > tag -1 pending Bug #938955 [pylint-doc] pylint-doc: missing Breaks+Replaces: pylint (<< 2) Added tag(s) pending. -- 938955: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=938955 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#939128: marked as done (basemap: AttributeError: module 'pyproj' has no attribute 'pyproj_datadir')

Your message dated Fri, 06 Sep 2019 02:41:05 + with message-id and subject line Bug#939128: fixed in basemap 1.2.1+dfsg-1 has caused the Debian Bug report #939128, regarding basemap: AttributeError: module 'pyproj' has no attribute 'pyproj_datadir' to be marked as done. This means that you

Bug#939128: marked as pending in basemap

Control: tag -1 pending Hello, Bug #939128 in basemap 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:

Processed: Bug#939128 marked as pending in basemap

Processing control commands: > tag -1 pending Bug #939128 [src:basemap] basemap: AttributeError: module 'pyproj' has no attribute 'pyproj_datadir' Added tag(s) pending. -- 939128: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=939128 Debian Bug Tracking System Contact ow...@bugs.debian.org

Bug#939489: more information

When I run opengl program with optirun or primusrun, the program can not run and I got a error message as below: $ optirun freecad [ 614.056579] [ERROR]Cannot access secondary GPU - error: [XORG] (EE) Failed to load module "mouse" (module does not exist, 0) [ 614.056596] [ERROR]Aborting

Bug#939505: more information

When I run opengl program with optirun or primusrun, the program can not run and I got a error message as below: $ optirun freecad [ 614.056579] [ERROR]Cannot access secondary GPU - error: [XORG] (EE) Failed to load module "mouse" (module does not exist, 0) [ 614.056596] [ERROR]Aborting

Bug#939531: medit: should this package be removed?

Package: src:medit Severity: serious Looking at this package, it appears that: * the last upstream update uploaded to debian is from 2014 * the last commit on upstream hg repo is from late 2017 * interest in this tool is declining (looking at popcon) * it's python2-based, which Debian is trying

Bug#939529: gtg: should this package be removed?

Package: src:gtg Severity: serious By looking at the status of this package, several points are evidend: * upstream abandoned its development * its stack is python2-based, which Debian is trying to remove * nobody is stepping up to keep this tool up to date So, should we remove gtg from Debian?

Bug#939522: marked as done (fetchmail: trying to overwrite '/usr/bin/fetchmailconf', which is also in package fetchmailconf 6.4.0~rc3-1)

Your message dated Fri, 06 Sep 2019 00:19:43 + with message-id and subject line Bug#939522: fixed in fetchmail 6.4.0~rc4-2 has caused the Debian Bug report #939522, regarding fetchmail: trying to overwrite '/usr/bin/fetchmailconf', which is also in package fetchmailconf 6.4.0~rc3-1 to be

Bug#939528: signal-desktop: Program fails to start after latest upgrade, worked fine before.

Package: signal-desktop Version: 1.27.1 Severity: grave Justification: renders package unusable Dear Maintainer, * What led up to the situation? running apt upgrade * What exactly did you do (or not do) that was effective (or ineffective)? After the recent upgrade signal-desktop

Bug#935293: marked as done (rampler: FTBFS on amd64)

Your message dated Thu, 05 Sep 2019 22:11:49 + with message-id and subject line Bug#935293: fixed in rampler 1.1.1-1 has caused the Debian Bug report #935293, regarding rampler: FTBFS on amd64 to be marked as done. This means that you claim that the problem has been dealt with. If this is

Bug#875050: marked as done ([mustang-plug] Future Qt4 removal from Buster)

Your message dated Thu, 05 Sep 2019 22:09:42 + with message-id and subject line Bug#875050: fixed in mustang-plug 1.2-2 has caused the Debian Bug report #875050, regarding [mustang-plug] Future Qt4 removal from Buster to be marked as done. This means that you claim that the problem has been

Bug#874880: [freemedforms-project] Future Qt4 removal from Buster

On Fri, Feb 01, 2019 at 09:36:38AM +0100, Andreas Tille wrote: > Hi again, > > just for your information: If freemedforms will not be uploaded until > end of this weekend I do not see any realistic chance that it will make > it into the next Debian stable release. Hi Andreas, I've downloaded

Processed: severity of 899241 is important

Processing commands for cont...@bugs.debian.org: > severity 899241 important Bug #899241 [mustang-plug] Amplifier detected by source from program developer but not by Debian package. Severity set to 'important' from 'serious' > thanks Stopping processing here. Please contact me if you need

Processed: tagging 899241

Processing commands for cont...@bugs.debian.org: > tags 899241 - pending Bug #899241 [mustang-plug] Amplifier detected by source from program developer but not by Debian package. Removed tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 899241:

Bug#939511: marked as done (/usr/bin/tifffile doesn't work)

Your message dated Thu, 05 Sep 2019 21:09:28 + with message-id and subject line Bug#939511: fixed in tifffile 20181128-2 has caused the Debian Bug report #939511, regarding /usr/bin/tifffile doesn't work to be marked as done. This means that you claim that the problem has been dealt with. If

Bug#875036: marked as done ([libqglviewer] Future Qt4 removal from Buster)

Your message dated Thu, 05 Sep 2019 21:01:28 + with message-id and subject line Bug#875036: fixed in libqglviewer 2.6.3+dfsg2-4 has caused the Debian Bug report #875036, regarding [libqglviewer] Future Qt4 removal from Buster to be marked as done. This means that you claim that the problem

Bug#939522: fetchmail: trying to overwrite '/usr/bin/fetchmailconf', which is also in package fetchmailconf 6.4.0~rc3-1

Package: fetchmail Version: 6.4.0~rc3-1 Severity: serious Hi, according to the changelog entry, fetchmailconf is removed, but it actually seems to now being shipped in the fetchmail package without proper Breaks/Replaces headers. The upgrade fails for me as follows: Preparing to unpack

Processed: Re: Bug#939439 closed by Thomas Goirand (Bug#939439: fixed in websockify 0.8.0+dfsg1-15)

Processing control commands: > reopen -1 Bug #939439 {Done: Thomas Goirand } [python3-websockify,websockify] python3-websockify: trying to overwrite '/usr/share/man/man1/websockify.1.gz', which is also in package websockify 0.8.0+dfsg1-14 'reopen' may be inappropriate when a bug has been

Bug#939439: closed by Thomas Goirand (Bug#939439: fixed in websockify 0.8.0+dfsg1-15)

Control: reopen -1 Control: found -1 0.8.0+dfsg1-15 Hi Thomas, Debian Bug Tracking System wrote: > websockify (0.8.0+dfsg1-15) unstable; urgency=medium > . >* Remove duplicate manpage from python3-websocify (Closes: #939439). I'm sorry to say, but while the fix looked good on a first

Processed: affects 936341

Processing commands for cont...@bugs.debian.org: > affects 936341 + src:koji src:mock src:open-build-service Bug #936341 [src:createrepo] createrepo: Python2 removal in sid/bullseye Added indication that 936341 affects src:koji, src:mock, and src:open-build-service > thanks Stopping processing

Processed: affects 938875

Processing commands for cont...@bugs.debian.org: > affects 938875 + src:mock Bug #938875 [src:yum-utils] yum-utils: Python2 removal in sid/bullseye Added indication that 938875 affects src:mock > thanks Stopping processing here. Please contact me if you need assistance. -- 938875:

Processed: [bts-link] source package src:srt

Processing commands for cont...@bugs.debian.org: > # > # bts-link upstream status pull for source package src:srt > # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html > # https://bts-link-team.pages.debian.net/bts-link/ > # > user debian-bts-l...@lists.debian.org

Bug#936341: createrepo: Python2 removal in sid/bullseye

Control: block -1 with 912338 The upstream replacement for createrepo is createrepo_c. There is already an ITP filed, set as blocking for this bug. The reverse dependencies of createrepo are src:koji, src:mock, and src:open-build-service. All three packages appear to me to already prefer

Processed: Re: Bug#936341: createrepo: Python2 removal in sid/bullseye

Processing control commands: > block -1 with 912338 Bug #936341 [src:createrepo] createrepo: Python2 removal in sid/bullseye 936341 was not blocked by any bugs. 936341 was not blocking any bugs. Added blocking bug(s) of 936341: 912338 -- 936341:

Bug#938875: yum-utils: Python2 removal in sid/bullseye

The upstream replacement for the combination of yum + yum-utils (Python 2 only) is dnf (Python 3). The only reverse dependency of yum-utils is mock. It looks like the version of mock already in Debian supports either dnf or yum. Once dnf is in Debian, mock can drop the dependency on yum and

Bug#932637: nmu now in the delayed queue

On Mon, 22 Jul 2019 18:38:32 +0200, Matthias Klose wrote: > the nmu is now in the delayed queue. What happened to this NMU? I just noticed that the bug ist still open and perl6-readline was removed from testing … Cheers, gregor, interested bystander in perl6 causes -- .''`.

Processed: severity of 938875 is serious, affects 938875

Processing commands for cont...@bugs.debian.org: > severity 938875 serious Bug #938875 [src:yum-utils] yum-utils: Python2 removal in sid/bullseye Severity set to 'serious' from 'normal' > affects 938875 + mock Bug #938875 [src:yum-utils] yum-utils: Python2 removal in sid/bullseye Added indication

Bug#936025: closed by Ximin Luo (Bug#936025: fixed in rust-memoffset 0.5.1-1)

Hey! On Thu, Sep 05, 2019 at 06:57:09AM +, Debian Bug Tracking System wrote: > rust-memoffset (0.5.1-1) unstable; urgency=medium > . >* Team upload. >* Package memoffset 0.5.1 from crates.io using debcargo 2.4.0 >* Closes: #936025 When CVE fixes are known, please do as well

Processed: notfound 939436 in 1.10.2+dfsg-1

Processing commands for cont...@bugs.debian.org: > notfound 939436 1.10.2+dfsg-1 Bug #939436 [node-js-beautify] node-js-beautify: does not start: 'config-chain' not found Ignoring request to alter found versions of bug #939436 to the same values previously set > thanks Stopping processing here.

Processed: found 934491 in 241.1-1+debian1, notfound 934491 in 241-7

Processing commands for cont...@bugs.debian.org: > found 934491 241.1-1+debian1 Bug #934491 [libelogind0] libelogind0: failing to switch from systemd to sysvinit-core/elogind results in libsystemd.so.0 disappearing Marked as found in versions elogind/241.1-1+debian1. > notfound 934491 241-7 Bug

Bug#939511: /usr/bin/tifffile doesn't work

Package: tifffile Version: 20181128-1+b1 Severity: grave $ tifffile Traceback (most recent call last): File "/usr/bin/tifffile", line 4, in import tifffile ImportError: No module named tifffile The package ships a Python 3 module with a Python 2 wrapper script. -- System Information:

Processed: notfound 939436 in 1.10.2+dfsg-1

Processing commands for cont...@bugs.debian.org: > notfound 939436 1.10.2+dfsg-1 Bug #939436 [node-js-beautify] node-js-beautify: does not start: 'config-chain' not found Ignoring request to alter found versions of bug #939436 to the same values previously set > thanks Stopping processing here.

Bug#936016: closing 936016

close 936016 1.3-1 new upstream version reflect the changed data structure that lead to 936016 thanks -- Alf Gaida BDBF C688 EFAD BA89 5A9F 464B CD28 0A0B 4D72 827C

Processed: tagging 936016

Processing commands for cont...@bugs.debian.org: > tags 936016 + buster Bug #936016 {Done: "Alf Gaida" } [meteo-qt] meteo-qt crashes immediately Added tag(s) buster. > thanks Stopping processing here. Please contact me if you need assistance. -- 936016:

Processed (with 1 error): closing 936016

Processing commands for cont...@bugs.debian.org: > close 936016 1.3-1 Bug #936016 [meteo-qt] meteo-qt crashes immediately Marked as fixed in versions meteo-qt/1.3-1. Bug #936016 [meteo-qt] meteo-qt crashes immediately Marked Bug as done > new upstream version reflect the changed data structure

Bug#939506: unanimity ftbfs in unstable

Package: src:unanimity Version: 3.3.0+dfsg-2.1 Severity: serious Tags: sid buster unanimity ftbfs in unstable: cd /build/1st/unanimity-3.3.0+dfsg/build/src && /usr/bin/cmake -E cmake_link_script CMakeFiles/gcpp.dir/link.txt --verbose=1 /build/1st/unanimity-3.3.0+dfsg/src/main/ccs.cpp: In

Bug#875243: [yagf] Future Qt4 removal from Buster

Hi Boris! On Thu, 5 Sep 2019 at 13:17, Boris Pek wrote: > > Hi, > > > similar ping as for qpxtool, last upstream commits are from 2015. Are you > > planning to port it yourself or should it be removed? > > Patch for yagf port to Qt5 already exists at least in Mageia GNU/Linux distro. > > I may

Bug#875243: [yagf] Future Qt4 removal from Buster

Hi, > similar ping as for qpxtool, last upstream commits are from 2015. Are you > planning to port it yourself or should it be removed? Patch for yagf port to Qt5 already exists at least in Mageia GNU/Linux distro. I may backport this patch to yagf 0.9.3.2 or update yagf package to latest

Bug#939502: haskell-attoparsec-enumerator: Removal notice: unused Haskell library

Source: haskell-attoparsec-enumerator Severity: serious This Haskell library is not part of Buster, has no reverse dependencies, is not on Stackage and is already ignored on our package-plan. I intend to remove this package. If there is a good reason to keep it, please close the bug. -- Ilias

Bug#939436: [Pkg-javascript-devel] Bug#939436: node-js-beautify: does not start: 'config-chain' not found

Control: tags -1 + moreinfo Le 05/09/2019 à 00:00, Johannes Deutsch a écrit : > Package: node-js-beautify > Version: 1.7.5+repack-1 > Severity: grave > Justification: renders package unusable > > Dear Maintainer, > > after installing css-beautify refuses to run with the following error: > > >

Processed: Re: [Pkg-javascript-devel] Bug#939436: node-js-beautify: does not start: 'config-chain' not found

Processing control commands: > tags -1 + moreinfo Bug #939436 [node-js-beautify] node-js-beautify: does not start: 'config-chain' not found Added tag(s) moreinfo. -- 939436: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=939436 Debian Bug Tracking System Contact ow...@bugs.debian.org with

Processed: bug 939044 is forwarded to https://github.com/jbarlow83/OCRmyPDF/issues/425

Processing commands for cont...@bugs.debian.org: > forwarded 939044 https://github.com/jbarlow83/OCRmyPDF/issues/425 Bug #939044 [src:ocrmypdf] ocrmypdf: autopkgtest not compatible with new pikepdf, ghostscript and/or pytest Set Bug forwarded-to-address to

Bug#935092: marked as done (Serious issues with inetsim in Debian 10)

Your message dated Thu, 05 Sep 2019 14:46:03 + with message-id and subject line Bug#935092: fixed in inetsim 1.3.1+dfsg.1-1 has caused the Debian Bug report #935092, regarding Serious issues with inetsim in Debian 10 to be marked as done. This means that you claim that the problem has been

Bug#925711: hdup: ftbfs with GCC-9

Hello, please try again, looks like you need a quilt format if you want to add a patch attached an updated diff G. diff -u hdup-2.0.14/debian/changelog hdup-2.0.14/debian/changelog --- hdup-2.0.14/debian/changelog +++ hdup-2.0.14/debian/changelog @@ -1,3 +1,11 @@ +hdup (2.0.14-5ubuntu1) eoan;

Processed: Re: python-acme: Please port to Python 3 and/or drop Python 2 package

Processing control commands: > tags -1 patch Bug #935211 [python-acme] python-acme: Please port to Python 3 and/or drop Python 2 package Added tag(s) patch. -- 935211: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=935211 Debian Bug Tracking System Contact ow...@bugs.debian.org with

Bug#935211: python-acme: Please port to Python 3 and/or drop Python 2 package

control: tags -1 patch > > More info at: https://wiki.debian.org/Python/2Removal > since the python3 package is already there, and it has no reverse > dependencies, > I'm dropping python-ndg-httpsclient from building, and bumping the severity > accordingly. I'm attaching a patch that also

Bug#939492: nbsphinx: testsuite failures with new pandoc

Source: nbsphinx Version: 0.4.2+ds-1 Severity: serious Hello, looks like the package is not able anymore to include svg into the pdf files... Look to the testsuite https://ci.debian.net/packages/n/nbsphinx/ This might be due to a regression/change in pandoc. cheers, Gianfranco

Bug#939489: bumblebee fails to disable discrete graphics card after upgrade nvidia driver to 430.40-2

Package: bumblebee-nvidia Version: 3.2.1-20 Severity: grave I upgrade my debian just now. The nvidia-driver and other nvidia packages were upgraded to 430.40-2. Then I found that bumblebee fails to disable discrete graphics card. We can not run opengl software with command "optirun", and when

Bug#938961: marked as done (aufs: needs update for new linux)

Your message dated Thu, 05 Sep 2019 13:19:34 + with message-id and subject line Bug#938961: fixed in aufs 5.2+20190902-1 has caused the Debian Bug report #938961, regarding aufs: needs update for new linux to be marked as done. This means that you claim that the problem has been dealt with.

Processed: Bug#926250 marked as pending in python-json-patch

Processing control commands: > tag -1 pending Bug #926250 [python3-jsonpatch] python3-jsonpatch: fails to upgrade from 'sid' - trying to overwrite /usr/bin/jsondiff Added tag(s) pending. -- 926250: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=926250 Debian Bug Tracking System Contact

Bug#926250: marked as pending in python-json-patch

Control: tag -1 pending Hello, Bug #926250 in python-json-patch 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:

Bug#939439: marked as done (python3-websockify: trying to overwrite '/usr/share/man/man1/websockify.1.gz', which is also in package websockify 0.8.0+dfsg1-14)

Your message dated Thu, 05 Sep 2019 12:49:56 + with message-id and subject line Bug#939439: fixed in websockify 0.8.0+dfsg1-15 has caused the Debian Bug report #939439, regarding python3-websockify: trying to overwrite '/usr/share/man/man1/websockify.1.gz', which is also in package

Bug#917507: marked as done (python-os-faults: FTBFS (Unable to create /sbuild-nonexistent/.ansible/tmp))

Your message dated Thu, 05 Sep 2019 14:33:55 +0200 with message-id <1567686835-bcd55ba065eb54eb49e5cbe88fb70...@infomaniak.com> and subject line Could not reproduce has caused the Debian Bug report #917507, regarding python-os-faults: FTBFS (Unable to create /sbuild-nonexistent/.ansible/tmp) to

Bug#939439: marked as pending in websockify

Control: tag -1 pending Hello, Bug #939439 in websockify 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:

Processed: Bug#939439 marked as pending in websockify

Processing control commands: > tag -1 pending Bug #939439 [python3-websockify,websockify] python3-websockify: trying to overwrite '/usr/share/man/man1/websockify.1.gz', which is also in package websockify 0.8.0+dfsg1-14 Added tag(s) pending. -- 939439:

Processed: Re: Bug#935293: rampler: FTBFS on amd64

Processing control commands: > tags -1 upstream Bug #935293 [src:rampler] rampler: FTBFS on amd64 Added tag(s) upstream. > forwarded -1 https://github.com/rvaser/rampler/issues/2 Bug #935293 [src:rampler] rampler: FTBFS on amd64 Set Bug forwarded-to-address to

Bug#939477: incomplete copyright file, and copyright file includes null characters

Package: src:emscripten Version: 1.22.1-1 Severity: serious Tags: sid bullseye Apparently this is an autogenerated file, however the license for tests/sdl_canvas_palette_g.png is bogus and contains null characters (which at least chokes launchpad when trying to upload. Also the file seems to

Bug#935293: rampler: FTBFS on amd64

Control: tags -1 upstream Control: forwarded -1 https://github.com/rvaser/rampler/issues/2 I think upstream has just addressed this and just forgot to tag a release. Just filed an issue to save the time to apply patches since upstream usually responds quickly. Kind regards, Andreas.

Bug#925761: marked as done (libthread-pool: ftbfs with GCC-9)

Your message dated Thu, 05 Sep 2019 12:19:17 + with message-id and subject line Bug#925761: fixed in libthread-pool 1.0.0-3 has caused the Debian Bug report #925761, regarding libthread-pool: ftbfs with GCC-9 to be marked as done. This means that you claim that the problem has been dealt

Bug#933527: snakemake: fails to install: SyntaxError: duplicate argument 'stay_on_remote' in function definition

The current packaging builds and installs fine for me; shall I upload? On Thu, Sep 5, 2019 at 4:51 PM Andreas Tille wrote: > Hi folks, > > this issue is urgent since if snakemake is not installable several of > our packages where snakemake is in (Build-)Depends are broken. Is > anybody working

Bug#939457: lxml breaks beautifulsoup4 autopkgtest: a real XHTML didn't come out *exactly* the same as it went in

On Thu, 05 Sep 2019 at 09:56:41 +0200, Paul Gevers wrote: > AssertionError: b'http://ns1/;>\n xmlns="http://ns2[96 chars]ent>' != b' chars]xmlns:="http://ns1/;>\nhttp://n[99 chars]ent>' "xmlns:=" (note the ":") is not a valid PrefixedAttName in , so this looks

Processed: Re: Processed (with 2 errors): FTBFS also in bullseye

Processing commands for cont...@bugs.debian.org: > found 934079 5.5.3+ds3-3 Bug #934079 [acorn] FTBFS: build depends on older node-unicode-* There is no source info for the package 'acorn' at version '5.5.3+ds3-3' with architecture '' Unable to make a source version for version '5.5.3+ds3-3'

Processed (with 2 errors): FTBFS also in bullseye

Processing commands for cont...@bugs.debian.org: > # This also happens in bullseye > retitle 934079 FTBFS: build depends on older node-unicode-* Bug #934079 [acorn] FTBFS: still depends on node-unicode-11.0.0 Changed Bug title to 'FTBFS: build depends on older node-unicode-*' from 'FTBFS: still

Processed: Re: link-grammar: Python2 removal in sid/bullseye

Processing control commands: > severity -1 serious Bug #936951 [src:link-grammar] link-grammar: Python2 removal in sid/bullseye Severity set to 'serious' from 'normal' -- 936951: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=936951 Debian Bug Tracking System Contact ow...@bugs.debian.org

Bug#933527: snakemake: fails to install: SyntaxError: duplicate argument 'stay_on_remote' in function definition

Hi folks, this issue is urgent since if snakemake is not installable several of our packages where snakemake is in (Build-)Depends are broken. Is anybody working on this? Kevin, you are listed as only Uploader. Does your time limit permit you to work on this package? Any other volunteers to

Bug#939463: FTBFS: psi4 build-depends on missing python3-qcelemental

Source: psi4 Version: 1:1.3.2-1 Severity: serious Tags: ftbfs -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Dear maintainers, Your package build depends on python3-qcelemental which isn't in Debian. Paul - -- System Information: Debian Release: bullseye/sid APT prefers testing APT

Bug#939016: marked as done (rust-debcargo_2.4.0-1_mipsel.changes REJECTED)

Your message dated Thu, 05 Sep 2019 08:44:43 + with message-id and subject line Bug#939016: fixed in dh-cargo 21 has caused the Debian Bug report #939016, regarding rust-debcargo_2.4.0-1_mipsel.changes REJECTED to be marked as done. This means that you claim that the problem has been dealt

Processed: node-supports-color breaks node-mocha autopkgtest: AssertionError [ERR_ASSERTION]: The expression evaluated to a falsy value

Processing control commands: > found -1 node-supports-color/6.1.0-2 Bug #939461 [src:node-supports-color, src:node-mocha] node-supports-color breaks node-mocha autopkgtest: AssertionError [ERR_ASSERTION]: The expression evaluated to a falsy value Marked as found in versions

Bug#939461: node-supports-color breaks node-mocha autopkgtest: AssertionError [ERR_ASSERTION]: The expression evaluated to a falsy value

Source: node-supports-color, node-mocha Control: found -1 node-supports-color/6.1.0-2 Control: found -1 node-mocha/4.1.0+ds3-5 Severity: serious Tags: sid bullseye X-Debbugs-CC: debian...@lists.debian.org User: debian...@lists.debian.org Usertags: breaks needs-update Dear maintainers, With a

Processed: libmojolicious-perl breaks libmojo-ioloop-readwriteprocess-perl autopkgtest: Invalid path at /usr/share/perl5/Mojo/IOLoop/ReadWriteProcess/CGroup/v1.pm line 30.

Processing control commands: > found -1 libmojolicious-perl/8.23+dfsg-1 Bug #939460 [src:libmojolicious-perl, src:libmojo-ioloop-readwriteprocess-perl] libmojolicious-perl breaks libmojo-ioloop-readwriteprocess-perl autopkgtest: Invalid path at

Bug#939460: libmojolicious-perl breaks libmojo-ioloop-readwriteprocess-perl autopkgtest: Invalid path at /usr/share/perl5/Mojo/IOLoop/ReadWriteProcess/CGroup/v1.pm line 30.

Source: libmojolicious-perl, libmojo-ioloop-readwriteprocess-perl Control: found -1 libmojolicious-perl/8.23+dfsg-1 Control: found -1 libmojo-ioloop-readwriteprocess-perl/0.23-1 Severity: serious Tags: sid bullseye X-Debbugs-CC: debian...@lists.debian.org User: debian...@lists.debian.org Usertags:

Processed: lxml breaks beautifulsoup4 autopkgtest: a real XHTML didn't come out *exactly* the same as it went in

Processing control commands: > found -1 lxml/4.4.1-1 Bug #939457 [src:lxml, src:beautifulsoup4] lxml breaks beautifulsoup4 autopkgtest: a real XHTML didn't come out *exactly* the same as it went in Marked as found in versions lxml/4.4.1-1. > found -1 beautifulsoup4/4.8.0-1 Bug #939457 [src:lxml,

Bug#939457: lxml breaks beautifulsoup4 autopkgtest: a real XHTML didn't come out *exactly* the same as it went in

Source: lxml, beautifulsoup4 Control: found -1 lxml/4.4.1-1 Control: found -1 beautifulsoup4/4.8.0-1 Severity: serious Tags: sid bullseye X-Debbugs-CC: debian...@lists.debian.org User: debian...@lists.debian.org Usertags: breaks needs-update Dear maintainers, With a recent upload of lxml the

Bug#935570: marked as done (src:pysph: License and Copyrights missing from debian/copyright)

Your message dated Thu, 05 Sep 2019 07:51:19 + with message-id and subject line Bug#935570: fixed in pysph 1.0~a6-2 has caused the Debian Bug report #935570, regarding src:pysph: License and Copyrights missing from debian/copyright to be marked as done. This means that you claim that the

Bug#939456: ftp.debian.org: phpMyAdmin dependencies waiting in FTP master for months

Package: ftp.debian.org Severity: serious Justification: fails to build from source (but built successfully in the past) Hello, We uploaded (phpMyAdmin packaging Team) new packages to FTP master 2 months ago, It seems like nobody did review them. The packages are: - phpmyadmin-sql-parser -

Bug#939454: link-grammar ftbfs (symbols file mismatches)

Package: src:link-grammar Version: 5.6.2-1 Severity: serious Tags: sid bullseye link-grammar ftbfs, symbols file mismatches for all architectures except for amd64. See https://buildd.debian.org/status/package.php?p=link-grammar

Bug#939455: link-grammar fails the autopkg tests (unrecognized gcc option)

Package: src:link-grammar Version: 5.6.2-1 Severity: serious Tags: sid bullseye as seen at https://ci.debian.net/data/autopkgtest/testing/amd64/l/link-grammar/2887534/log.gz autopkgtest [20:20:24]: test unit-tests: - - - - - - - - - - results - - - - - - - - - - unit-tests FAIL

Bug#890617: marked as done (pyscrabble: No metaservers available and pyscrabble-server also doesn't work)

Your message dated Thu, 05 Sep 2019 07:25:00 + with message-id and subject line Bug#938891: Removed package(s) from unstable has caused the Debian Bug report #890617, regarding pyscrabble: No metaservers available and pyscrabble-server also doesn't work to be marked as done. This means that

Bug#885884: marked as done (bashburn: does not work: it passes incorrect options to wodim, so no CD can ever be burnt)

Your message dated Thu, 05 Sep 2019 07:18:15 + with message-id and subject line Bug#939450: Removed package(s) from unstable has caused the Debian Bug report #885884, regarding bashburn: does not work: it passes incorrect options to wodim, so no CD can ever be burnt to be marked as done.

Bug#936025: marked as done (CVE-2019-15553)

Your message dated Thu, 05 Sep 2019 06:53:53 + with message-id and subject line Bug#936025: fixed in rust-memoffset 0.5.1-1 has caused the Debian Bug report #936025, regarding CVE-2019-15553 to be marked as done. This means that you claim that the problem has been dealt with. If this is not

Processed: block 937671 with 936269

Processing commands for cont...@bugs.debian.org: > block 937671 with 936269 Bug #937671 [src:python-crypto] python-crypto: Python2 removal in sid/bullseye 937671 was blocked by: 936447 938093 938731 936501 938067 937381 937176 936789 937300 936790 938041 938430 938872 936861 936730 936388 938830

Bug#925772: lua-cqueues: ftbfs with GCC-9

Upstream has fixed the issue, please see new releases: https://github.com/wahern/cqueues/releases On Thu, 28 Mar 2019 at 12:49, Daurnimator wrote: > > This issue is known upstream: https://github.com/wahern/cqueues/issues/212 > > It comes down to GCC extensions no longer being compatible with