Bug#951212: marked as done (searx fails autopkg tests)

Your message dated Sun, 16 Feb 2020 07:19:13 + with message-id and subject line Bug#951212: fixed in searx 0.16.0+dfsg1-2 has caused the Debian Bug report #951212, regarding searx fails autopkg tests to be marked as done. This means that you claim that the problem has been dealt with. If

Processed: your mail

Processing commands for cont...@bugs.debian.org: > tags 937681 + pending Bug #937681 [src:python-cycler] python-cycler: Python2 removal in sid/bullseye Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 937681:

Processed: Re: Bug#950474: python-cogent FTBFS on armel and i386: test failures

Processing control commands: > tags -1 upstream Bug #950474 [src:python-cogent] python-cogent FTBFS on armel and i386: test failures Added tag(s) upstream. > forwarded -1 https://github.com/cogent3/cogent3/issues/534 Bug #950474 [src:python-cogent] python-cogent FTBFS on armel and i386: test

Bug#950474: python-cogent FTBFS on armel and i386: test failures

Control: tags -1 upstream Control: forwarded -1 https://github.com/cogent3/cogent3/issues/534 On Sun, Feb 02, 2020 at 01:12:27PM +0200, Adrian Bunk wrote: > > The armel port has no FPU in the baseline, > and the math emulation does not handle all corner cases correctly. > > The i386 port uses

Processed: reassign 933439 to src:amule

Processing commands for cont...@bugs.debian.org: > reassign 933439 src:amule Bug #933439 [amule] amule: Please rebuild against wxWidgets GTK 3 package Bug reassigned from package 'amule' to 'src:amule'. No longer marked as found in versions 1:2.3.2-6. Ignoring request to alter fixed versions of

Bug#951372: golang-github-proglottis-gpgme: CVE-2020-8945

Source: golang-github-proglottis-gpgme Version: 0.1.0-1 Severity: grave Tags: security upstream Forwarded: https://github.com/proglottis/gpgme/pull/23 Hi, The following vulnerability was published for golang-github-proglottis-gpgme. CVE-2020-8945[0]: | The proglottis Go wrapper before 0.1.1 for

Bug#950435: marked as done (haproxy build-depends on package that has been dropped.)

Your message dated Sat, 15 Feb 2020 14:49:22 + with message-id and subject line Bug#950435: fixed in haproxy 2.0.13-1 has caused the Debian Bug report #950435, regarding haproxy build-depends on package that has been dropped. to be marked as done. This means that you claim that the problem

Bug#950556: marked as done (initramfs-tools hook fails to copy libgcc_s.so.1)

Your message dated Sat, 15 Feb 2020 16:34:15 + with message-id and subject line Bug#950556: fixed in btrfs-progs 5.4.1-2 has caused the Debian Bug report #950556, regarding initramfs-tools hook fails to copy libgcc_s.so.1 to be marked as done. This means that you claim that the problem has

Bug#949318: marked as done (systemsettings should Replace (or Conflict) kde-config-systemd << 5.17)

Your message dated Sat, 15 Feb 2020 08:41:56 + with message-id and subject line Bug#949318: fixed in systemsettings 4:5.17.5-2 has caused the Debian Bug report #949318, regarding systemsettings should Replace (or Conflict) kde-config-systemd << 5.17 to be marked as done. This means that you

Bug#951281: FTBFS: /usr/bin/ld: cannot find -lpthreads

Control: retitle -1 widelands FTBFS: SDL2 include dir not found On Thu, 13 Feb 2020 19:02:17 +0100 Hans Joachim Desserud wrote: > Source: widelands > Version: 1:20-1 > Severity: serious > Justification: ftbfs > Tags: ftbfs > > Dear Maintainer, > > Widelands currently fails to build in Sid

Processed: severity of 951349 is serious

Processing commands for cont...@bugs.debian.org: > severity 951349 serious Bug #951349 [src:mecab] mecab: Fails to build against ruby2.7 Severity set to 'serious' from 'critical' > thanks Stopping processing here. Please contact me if you need assistance. -- 951349:

Processed: tagging 937677

Processing commands for cont...@bugs.debian.org: > tags 937677 + fixed Bug #937677 {Done: Sandro Tosi } [src:python-css-parser] python-css-parser: Python2 removal in sid/bullseye Added tag(s) fixed. > thanks Stopping processing here. Please contact me if you need assistance. -- 937677:

Processed: tagging 937678

Processing commands for cont...@bugs.debian.org: > tags 937678 + fixed Bug #937678 {Done: Sandro Tosi } [src:python-cssselect] python-cssselect: Python2 removal in sid/bullseye Added tag(s) fixed. > thanks Stopping processing here. Please contact me if you need assistance. -- 937678:

Processed: tagging 949144

Processing commands for cont...@bugs.debian.org: > tags 949144 + fixed-upstream Bug #949144 [src:font-manager] font-manager: FTBFS: error: Creation method of abstract class cannot be public. Added tag(s) fixed-upstream. > thanks Stopping processing here. Please contact me if you need

Processed: tagging 936710

Processing commands for cont...@bugs.debian.org: > tags 936710 + fixed Bug #936710 {Done: Norbert Preining } [src:html5-parser] html5-parser: Python2 removal in sid/bullseye Added tag(s) fixed. > thanks Stopping processing here. Please contact me if you need assistance. -- 936710:

Processed: tagging 938127

Processing commands for cont...@bugs.debian.org: > tags 938127 + fixed Bug #938127 {Done: Sandro Tosi } [src:python-regex] python-regex: Python2 removal in sid/bullseye Added tag(s) fixed. > thanks Stopping processing here. Please contact me if you need assistance. -- 938127:

Processed: tagging 942978

Processing commands for cont...@bugs.debian.org: > tags 942978 + fixed Bug #942978 {Done: Sandro Tosi } [src:cssutils] cssutils: Python2 removal in sid/bullseye Added tag(s) fixed. > thanks Stopping processing here. Please contact me if you need assistance. -- 942978:

Processed: Re: Bug#938184 closed by Debian FTP Masters (reply to Federico Ceratto ) (Bug#938184: fixed in python-socksipychain 2.1.0-2)

Processing control commands: > reopen -1 Bug #938184 {Done: Debian FTP Masters } [src:python-socksipychain] python-socksipychain: 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#938184: closed by Debian FTP Masters (reply to Federico Ceratto ) (Bug#938184: fixed in python-socksipychain 2.1.0-2)

Control: reopen -1 On Fri, Jan 31, 2020 at 10:54:06AM +, Debian Bug Tracking System wrote: >... >* Migrate an autopkgtest to Python 3 from Python 2 (Closes: #948930) > (Closes: #938184). >... There is still a test dependency on Python 2. For some reason the autopkgtest also fails.

Processed: Add tag patch: Bug#951281

Processing commands for cont...@bugs.debian.org: > tags 951281 + patch Bug #951281 [src:widelands] widelands FTBFS: SDL2 include dir not found Added tag(s) patch. > stop Stopping processing here. Please contact me if you need assistance. -- 951281:

Processed: tagging 937578

Processing commands for cont...@bugs.debian.org: > tags 937578 + fixed Bug #937578 {Done: Sandro Tosi } [src:python-apsw] python-apsw: Python2 removal in sid/bullseye Added tag(s) fixed. > thanks Stopping processing here. Please contact me if you need assistance. -- 937578:

Processed: Re: Bug#951281: widelands FTBFS: SDL2_INCLUDE_DIR-NOTFOUND

Processing control commands: > affects 951087 + src:widelands Bug #951087 [libsdl2-dev] libsdl2-dev: Packages that embed FindSDL2.cmake fail to find SDL2 Ignoring request to set affects of bug 951087 to the same value previously set -- 951087:

Bug#951087: Bug#951281: widelands FTBFS: SDL2_INCLUDE_DIR-NOTFOUND

Control: affects 951087 + src:widelands On Sat, 15 Feb 2020 at 10:49:59 +0200, Juhani Numminen wrote: > I think the error is actually this (abridged): > > -- SDL2_INCLUDE_DIR is SDL2_INCLUDE_DIR-NOTFOUND ... > The trigger to breaking cmake/Modules/FindSDL2.cmake in widelands is > libsdl2

Processed: Re: Bug#951281: widelands FTBFS: SDL2_INCLUDE_DIR-NOTFOUND

Processing control commands: > affects 951087 + src:widelands Bug #951087 [libsdl2-dev] libsdl2-dev: Packages that embed FindSDL2.cmake fail to find SDL2 Added indication that 951087 affects src:widelands -- 951087: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=951087 Debian Bug Tracking

Processed: tagging 937911

Processing commands for cont...@bugs.debian.org: > tags 937911 + fixed Bug #937911 {Done: Sandro Tosi } [src:python-mechanize] python-mechanize: Python2 removal in sid/bullseye Added tag(s) fixed. > thanks Stopping processing here. Please contact me if you need assistance. -- 937911:

Bug#944849: marked as done (ruby-rack-cors: CVE-2019-18978)

Your message dated Sat, 15 Feb 2020 12:34:27 + with message-id and subject line Bug#944849: fixed in ruby-rack-cors 1.1.1-1 has caused the Debian Bug report #944849, regarding ruby-rack-cors: CVE-2019-18978 to be marked as done. This means that you claim that the problem has been dealt with.

Bug#947296: mercurial-keyring: Python2 removal in sid/bullseye

Hi Andrej! On Fri, Feb 14, 2020 at 03:17:07PM +0100, Andrej Shadura wrote: > On Thu, 30 Jan 2020 12:08:33 +0300 Dmitry Shachnev wrote: > > setuptools-scm has removed Python 2 support (see #938470), so python-keyring > > build-dependencies are no longer satisfiable. > > It has since been

Processed: Re: Bug#951281: FTBFS: /usr/bin/ld: cannot find -lpthreads

Processing control commands: > retitle -1 widelands FTBFS: SDL2 include dir not found Bug #951281 [src:widelands] FTBFS: /usr/bin/ld: cannot find -lpthreads Changed Bug title to 'widelands FTBFS: SDL2 include dir not found' from 'FTBFS: /usr/bin/ld: cannot find -lpthreads'. -- 951281:

Bug#948908: marked as done (plasma-desktop: FTBFS: error: ‘targetDesktop’ was not declared in this scope)

Your message dated Sat, 15 Feb 2020 10:23:34 +0100 with message-id <9382221.6Hj67J5WcI@thyrus> and subject line Re: Bug#948908: plasma-desktop: FTBFS: error: ‘targetDesktop’ was not declared in this scope has caused the Debian Bug report #948908, regarding plasma-desktop: FTBFS: error:

Bug#949941: byobu build depends on the removed pep8 transitional package

Okay, just tried a new upload. Disabling pep8 for now, until I figure out a different solution. @DustinKirkland Ubuntu Core Dev On Tue, Feb 11, 2020 at 5:42 PM Boyuan Yang wrote: > Control: reopen -1 > Control: notfixed -1 5.131-1 > Control: found -1 5.131-1 > X-Debbugs-CC:

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

Your message dated Sat, 15 Feb 2020 18:21:57 + with message-id and subject line Bug#937757: fixed in python-flake8 3.7.9-2 has caused the Debian Bug report #937757, regarding python-flake8: Python2 removal in sid/bullseye to be marked as done. This means that you claim that the problem has

Bug#930869: Don't release with buster

Package: pm-utils Followup-For: Bug #930869 pm-utils is now marked for autoremoval due to this frivolous RC bug. As another satisfied pm-utils user, this worries me. Would someone with more authority please downgrade/close this as invalid, or at least get Michael Biebl to to adress the questions

Bug#948859: coccinelle: Package is uninstallable

On 2020-01-16 15:11:42 [+0100], Stéphane Glondu wrote: > > The following packages have unmet dependencies: > > coccinelle : Depends: libpcre-ocaml-2h5n2 but it is not installable > > Depends: ocaml-base-nox-4.05.0 but it is not installable > > E: Unable to correct problems, you have

Bug#948834: glib2.0: FTBFS: SIGABRT in gsocketclient-slow test

On Sun, Feb 09, 2020 at 07:19:24PM +, Simon McVittie wrote: > I personally think this is a pbuilder bug (see also > ). The fact that > "localhost" resolves to 127.0.0.1 and/or ::1 is part of the "OS API", > and I think packages' tests

Processed: py2removal bugs severity updates - 2020-02-15 17:35:09.841748+00:00

Processing commands for cont...@bugs.debian.org: > # This is an automated script, part of the effort for the removal of Python 2 > from bullseye > # * https://wiki.debian.org/Python/2Removal > # * http://sandrotosi.me/debian/py2removal/index.html > # See

Bug#937757: marked as pending in python-flake8

Control: tag -1 pending Hello, Bug #937757 in python-flake8 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#937757 marked as pending in python-flake8

Processing control commands: > tag -1 pending Bug #937757 [src:python-flake8] python-flake8: Python2 removal in sid/bullseye Added tag(s) pending. -- 937757: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=937757 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#951389: akonadi-backend-postgresql: Initialisation of database fail if locale en_US.UTF8 is not avalaible systemwide

Package: akonadi-backend-postgresql Version: 4:19.08.3-1 Severity: grave Justification: renders package unusable Tags: l10n patch forwarded: https://bugs.kde.org/show_bug.cgi?id=417721 Dear Maintainer, The creation of database fail if locale en_US.UTF8 is not installed systemwise (by pulling

Bug#944392: marked as done (frr: /usr/share/man/man8/vrrpd.8.gz is already shipped by vrrpd)

Your message dated Sat, 15 Feb 2020 20:49:36 + with message-id and subject line Bug#944392: fixed in frr 7.2.1-1 has caused the Debian Bug report #944392, regarding frr: /usr/share/man/man8/vrrpd.8.gz is already shipped by vrrpd to be marked as done. This means that you claim that the

Bug#951388: [akonadi-backend-postgresql] apparmor profile unsuitable

Package: akonadi-backend-postgresql Version: 4:19.08.3-1 Severity: grave Justification: renders package unusable Tags: patch Dear Maintainer, Please find the following update for apparmor Please apply Bastiendiff --git a/apparmor.d/postgresql_akonadi b/apparmor.d/postgresql_akonadi index

Bug#943517: marked as done (boxbackup: FTBFS with test failures)

Your message dated Sat, 15 Feb 2020 20:36:31 + with message-id and subject line Bug#943517: fixed in boxbackup 0.13~~git20190527.g039c4a1-4 has caused the Debian Bug report #943517, regarding boxbackup: FTBFS with test failures to be marked as done. This means that you claim that the problem

Processed: py2removal bugs severity updates - 2020-02-16 03:35:20.567044+00:00

Processing commands for cont...@bugs.debian.org: > # This is an automated script, part of the effort for the removal of Python 2 > from bullseye > # * https://wiki.debian.org/Python/2Removal > # * http://sandrotosi.me/debian/py2removal/index.html > # See

Processed: Patch

Processing control commands: > tags -1 + patch Bug #951398 [src:texlive-extra] FTBFS: pax.jar Added tag(s) patch. -- 951398: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=951398 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#951398: Patch

control: tags -1 + patch Patch file

Bug#936772: jupyter-client: Python2 removal in sid/bullseye

On Fri, 30 Aug 2019 07:21:43 + Matthias Klose wrote: > Package: src:jupyter-client > Version: 5.2.4-1 > Severity: normal > Tags: sid bullseye > User: debian-pyt...@lists.debian.org > Usertags: py2removal Hey Gordon, jupyter-client (and python-jupyter-client) is the last reverse depends on

Bug#951398: FTBFS: pax.jar

severity 951398 normal thanks Hi Bastien, On Sun, 16 Feb 2020, Bastien Roucariès wrote: > I could not found the source of file texmf-dist/scripts/pax.jar Mind looking into the .orig.tar.xz? drwxr-xr-x norbert/norbert0 2020-02-10 10:40

Processed: Re: Bug#951398: FTBFS: pax.jar

Processing commands for cont...@bugs.debian.org: > severity 951398 normal Bug #951398 [src:texlive-extra] FTBFS: pax.jar Severity set to 'normal' from 'serious' > thanks Stopping processing here. Please contact me if you need assistance. -- 951398:

Bug#943073: marked as done (fonts-fantasque-sans: Python2 removal in sid/bullseye)

Your message dated Sun, 16 Feb 2020 00:04:33 + with message-id and subject line Bug#943073: fixed in fonts-fantasque-sans 1.7.2~alpha.3~dfsg-2 has caused the Debian Bug report #943073, regarding fonts-fantasque-sans: Python2 removal in sid/bullseye to be marked as done. This means that you

Bug#903448: marked as done (ruby-websocket-parser: hijacks namespace from ruby-websocket)

Your message dated Sun, 16 Feb 2020 00:20:20 + with message-id and subject line Bug#951129: Removed package(s) from unstable has caused the Debian Bug report #903448, regarding ruby-websocket-parser: hijacks namespace from ruby-websocket to be marked as done. This means that you claim that

Bug#938608: marked as done (RM: svn-workbench -- RoQA; dead upstream; low popcon; blocking py2 removal)

Your message dated Sun, 16 Feb 2020 00:19:15 + with message-id and subject line Bug#938608: Removed package(s) from unstable has caused the Debian Bug report #938608, regarding RM: svn-workbench -- RoQA; dead upstream; low popcon; blocking py2 removal to be marked as done. This means that

Bug#939181: marked as done (RM: cycle -- RoQA; dead upstream; unmaintained; low popcon; blocking py2 removal)

Your message dated Sun, 16 Feb 2020 00:19:38 + with message-id and subject line Bug#939181: Removed package(s) from unstable has caused the Debian Bug report #939181, regarding RM: cycle -- RoQA; dead upstream; unmaintained; low popcon; blocking py2 removal to be marked as done. This means

Bug#892185: marked as done (reel: FTBFS and Debci failure with Ruby 2.5)

Your message dated Sun, 16 Feb 2020 00:20:47 + with message-id and subject line Bug#951130: Removed package(s) from unstable has caused the Debian Bug report #892185, regarding reel: FTBFS and Debci failure with Ruby 2.5 to be marked as done. This means that you claim that the problem has

Bug#869919: marked as done (remove ruby-berkshelf-api-client?)

Your message dated Sun, 16 Feb 2020 00:21:38 + with message-id and subject line Bug#951132: Removed package(s) from unstable has caused the Debian Bug report #869919, regarding remove ruby-berkshelf-api-client? to be marked as done. This means that you claim that the problem has been dealt

Bug#895132: marked as done (ruby-grape-msgpack: FTBFS and Debci failure)

Your message dated Sun, 16 Feb 2020 00:23:11 + with message-id and subject line Bug#951174: Removed package(s) from unstable has caused the Debian Bug report #895132, regarding ruby-grape-msgpack: FTBFS and Debci failure to be marked as done. This means that you claim that the problem has

Bug#950340: marked as done (volatility: keep out of testing (for now))

Your message dated Sun, 16 Feb 2020 00:22:29 + with message-id and subject line Bug#951171: Removed package(s) from unstable has caused the Debian Bug report #950340, regarding volatility: keep out of testing (for now) to be marked as done. This means that you claim that the problem has been

Bug#870744: marked as done (berkshelf-api FTBFS with ruby-buff-extensions 2.0.0-1)

Your message dated Sun, 16 Feb 2020 00:21:12 + with message-id and subject line Bug#951131: Removed package(s) from unstable has caused the Debian Bug report #870744, regarding berkshelf-api FTBFS with ruby-buff-extensions 2.0.0-1 to be marked as done. This means that you claim that the

Bug#870306: marked as done (ruby-dep-selector FTBFS with libgecode-dev 5.1.0-2)

Your message dated Sun, 16 Feb 2020 00:22:49 + with message-id and subject line Bug#951172: Removed package(s) from unstable has caused the Debian Bug report #870306, regarding ruby-dep-selector FTBFS with libgecode-dev 5.1.0-2 to be marked as done. This means that you claim that the problem

Bug#867650: marked as done (berkshelf: FTBFS: ERROR: Test "ruby2.3" failed: Did you mean? Berkshelf::NullFormatter (NameError))

Your message dated Sun, 16 Feb 2020 00:22:05 + with message-id and subject line Bug#951133: Removed package(s) from unstable has caused the Debian Bug report #867650, regarding berkshelf: FTBFS: ERROR: Test "ruby2.3" failed: Did you mean? Berkshelf::NullFormatter (NameError) to be marked as

Bug#951247: marked as done (html2canvas: build-depends on removed package libjs-mocha)

Your message dated Sun, 16 Feb 2020 00:25:26 + with message-id and subject line Bug#951285: Removed package(s) from unstable has caused the Debian Bug report #951247, regarding html2canvas: build-depends on removed package libjs-mocha to be marked as done. This means that you claim that the

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

Your message dated Sun, 16 Feb 2020 00:25:01 + with message-id and subject line Bug#951266: Removed package(s) from unstable has caused the Debian Bug report #937750, regarding python-feedvalidator: Python2 removal in sid/bullseye to be marked as done. This means that you claim that the

Bug#897520: marked as done (html2canvas: FTBFS: TypeError: Attempting to change the setter of an unconfigurable property.)

Your message dated Sun, 16 Feb 2020 00:25:26 + with message-id and subject line Bug#951285: Removed package(s) from unstable has caused the Debian Bug report #897520, regarding html2canvas: FTBFS: TypeError: Attempting to change the setter of an unconfigurable property. to be marked as done.

Bug#943195: marked as done (reconf-inetd: Python2 removal in sid/bullseye)

Your message dated Sun, 16 Feb 2020 00:25:53 + with message-id and subject line Bug#951290: Removed package(s) from unstable has caused the Debian Bug report #943195, regarding reconf-inetd: Python2 removal in sid/bullseye to be marked as done. This means that you claim that the problem has

Bug#938737: marked as done (u1db: Python2 removal in sid/bullseye)

Your message dated Sun, 16 Feb 2020 00:27:02 + with message-id and subject line Bug#951298: Removed package(s) from unstable has caused the Debian Bug report #938737, regarding u1db: Python2 removal in sid/bullseye to be marked as done. This means that you claim that the problem has been

Bug#938875: marked as done (yum-utils: Python2 removal in sid/bullseye)

Your message dated Sun, 16 Feb 2020 00:29:36 + with message-id and subject line Bug#951299: Removed package(s) from unstable has caused the Debian Bug report #938875, regarding yum-utils: Python2 removal in sid/bullseye to be marked as done. This means that you claim that the problem has

Bug#945701: marked as done (mock: Python2 removal in sid/bullseye)

Your message dated Sun, 16 Feb 2020 00:29:04 + with message-id and subject line Bug#951299: Removed package(s) from unstable has caused the Debian Bug report #945701, regarding mock: Python2 removal in sid/bullseye to be marked as done. This means that you claim that the problem has been

Bug#936341: marked as done (createrepo: Python2 removal in sid/bullseye)

Your message dated Sun, 16 Feb 2020 00:30:52 + with message-id and subject line Bug#951299: Removed package(s) from unstable has caused the Debian Bug report #936341, regarding createrepo: Python2 removal in sid/bullseye to be marked as done. This means that you claim that the problem has

Bug#936447: marked as done (dtc-xen: Python2 removal in sid/bullseye)

Your message dated Sun, 16 Feb 2020 00:30:14 + with message-id and subject line Bug#951299: Removed package(s) from unstable has caused the Debian Bug report #936447, regarding dtc-xen: Python2 removal in sid/bullseye to be marked as done. This means that you claim that the problem has been

Bug#938874: marked as done (yum-metadata-parser: Python2 removal in sid/bullseye)

Your message dated Sun, 16 Feb 2020 00:32:20 + with message-id and subject line Bug#951299: Removed package(s) from unstable has caused the Debian Bug report #938874, regarding yum-metadata-parser: Python2 removal in sid/bullseye to be marked as done. This means that you claim that the

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

Your message dated Sun, 16 Feb 2020 00:33:28 + with message-id and subject line Bug#951299: Removed package(s) from unstable has caused the Debian Bug report #937902, regarding python-lzma: Python2 removal in sid/bullseye to be marked as done. This means that you claim that the problem has

Bug#936995: marked as done (matplotlib2: Python2 removal in sid/bullseye)

Your message dated Sun, 16 Feb 2020 00:34:21 + with message-id and subject line Bug#951400: Removed package(s) from unstable has caused the Debian Bug report #936995, regarding matplotlib2: Python2 removal in sid/bullseye to be marked as done. This means that you claim that the problem has

Bug#946239: marked as done (lynkeos.app: missing Breaks+Replaces: lynkeos.app-common (<< 3.3+dfsg1))

Your message dated Sat, 15 Feb 2020 21:23:38 + with message-id and subject line Bug#946239: fixed in lynkeos.app 3.3+dfsg1-2 has caused the Debian Bug report #946239, regarding lynkeos.app: missing Breaks+Replaces: lynkeos.app-common (<< 3.3+dfsg1) to be marked as done. This means that you

Bug#943501: marked as done (ftbfs with python3.8 (test failure))

Your message dated Sat, 15 Feb 2020 21:24:21 + with message-id and subject line Bug#943501: fixed in python-tesserocr 2.5.0-1 has caused the Debian Bug report #943501, regarding ftbfs with python3.8 (test failure) to be marked as done. This means that you claim that the problem has been

Bug#943618: marked as done (python-tesserocr ftbfs in unstable (failing test))

Your message dated Sat, 15 Feb 2020 21:24:21 + with message-id and subject line Bug#943618: fixed in python-tesserocr 2.5.0-1 has caused the Debian Bug report #943618, regarding python-tesserocr ftbfs in unstable (failing test) to be marked as done. This means that you claim that the problem

Bug#949903: marked as done (gammaray ftbfs on s390x)

Your message dated Sat, 15 Feb 2020 21:50:30 + with message-id and subject line Bug#949903: fixed in gammaray 2.11.0-2 has caused the Debian Bug report #949903, regarding gammaray ftbfs on s390x to be marked as done. This means that you claim that the problem has been dealt with. If this is

Bug#930869: marked as done (Don't release with buster)

Your message dated Sat, 15 Feb 2020 23:10:59 +0100 with message-id <20200215221059.ga4...@angband.pl> and subject line nothing to fix -- thus not a bug has caused the Debian Bug report #930869, regarding Don't release with buster to be marked as done. This means that you claim that the problem

Bug#951398: FTBFS: pax.jar

Source: texlive-extra Version: 2019.202000210-1 Severity: serious Justification: DFSG #2 Dear Maintainer, I could not found the source of file texmf-dist/scripts/pax.jar I have recreated a github solving also the problem of using an old pdfbox source

Processed: py2removal bugs severity updates - 2020-02-15 21:35:16.160145+00:00

Processing commands for cont...@bugs.debian.org: > # This is an automated script, part of the effort for the removal of Python 2 > from bullseye > # * https://wiki.debian.org/Python/2Removal > # * http://sandrotosi.me/debian/py2removal/index.html > # See

Bug#949903: marked as pending in gammaray

Control: tag -1 pending Hello, Bug #949903 in gammaray 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#949903 marked as pending in gammaray

Processing control commands: > tag -1 pending Bug #949903 [src:gammaray] gammaray ftbfs on s390x Added tag(s) pending. -- 949903: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=949903 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Processed: Bug#937910 marked as pending in python-mccabe

Processing control commands: > tag -1 pending Bug #937910 [src:python-mccabe] python-mccabe: Python2 removal in sid/bullseye Added tag(s) pending. -- 937910: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=937910 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#937910: marked as pending in python-mccabe

Control: tag -1 pending Hello, Bug #937910 in python-mccabe 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#937910: marked as done (python-mccabe: Python2 removal in sid/bullseye)

Your message dated Sat, 15 Feb 2020 22:20:23 + with message-id and subject line Bug#937910: fixed in python-mccabe 0.6.1-3 has caused the Debian Bug report #937910, regarding python-mccabe: Python2 removal in sid/bullseye to be marked as done. This means that you claim that the problem has

Processed: reopening 930869

Processing commands for cont...@bugs.debian.org: > reopen 930869 Bug #930869 {Done: Adam Borowski } [pm-utils] Don't release with buster Bug reopened Ignoring request to alter fixed versions of bug #930869 to the same values previously set > thanks Stopping processing here. Please contact me

Bug#930869: marked as done (Don't release with buster)

Debian Bug Tracking System writes ("Bug#930869: marked as done (Don't release with buster)"): > The new maintainer, Ian Jackson, seems to be quite busy, and did not > decide yet whether to drop the i386 parts. But, even if untestable > for most of us, they're unlikely to regress -- and thus,