Processed: severity of 955317 is normal, retitle 955317 to support multiple Python versions

2020-03-30 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > severity 955317 normal Bug #955317 [src:ros-ros-comm] ros-ros-comm: autopkgtest regression: No rule to make target '/usr/lib/x86_64-linux-gnu/libpython3.8.so' Severity set to 'normal' from 'serious' > retitle 955317 support multiple Python versio

Bug#954977: "Daily Limit Exceeded" connection error

2020-03-30 Thread william l-k
Package: evolution Version: 3.36.0-1 Followup-For: Bug #954977 This is happening to me daily in evolution. When it does I am unable to use evolution email or calendar. The message I'm getting is: Daily Limit Exceeded. The quota will be reset at midnight Pacific Time (PT). You may monitor your qu

Bug#953086: marked as done (samba: uninstallable, depends on unavailable python3 version <3.8 while 3.8.2-1 is available)

2020-03-30 Thread Debian Bug Tracking System
Your message dated Tue, 31 Mar 2020 06:48:40 +0100 with message-id and subject line re: samba: uninstallable, depends on unavailable python3 version <3.8 while 3.8.2-1 is available has caused the Debian Bug report #953086, regarding samba: uninstallable, depends on unavailable python3 version <3.

Bug#954582: samba: FTBFS glibc/stropts/python issue.

2020-03-30 Thread Andrew Bartlett
On Tue, 2020-03-31 at 02:09 +0100, peter green wrote: > The samba FTBFS is blocking the python 3.8 transition in raspbian > bullseye, so I decided to take a look. Thanks for digging into this. I've updated the Samba bug below, and I think this is a Python bug and needs to be fixed in Python. The

Bug#951101: marked as done (cracklib2 FTBFS: debian/rules:6: /usr/share/python/python.mk: No such file or directory)

2020-03-30 Thread Debian Bug Tracking System
Your message dated Tue, 31 Mar 2020 05:18:29 + with message-id and subject line Bug#951101: fixed in cracklib2 2.9.6-3.2 has caused the Debian Bug report #951101, regarding cracklib2 FTBFS: debian/rules:6: /usr/share/python/python.mk: No such file or directory to be marked as done. This mean

Bug#951101: cracklib2 FTBFS: debian/rules:6: /usr/share/python/python.mk: No such file or directory

2020-03-30 Thread peter green
Since this bug had no maintainer response for a month I decided to go ahead with a NMU, the debdiff is attatched (same as helmuts other than changelog tweaks). diff -Nru cracklib2-2.9.6/debian/changelog cracklib2-2.9.6/debian/changelog --- cracklib2-2.9.6/debian/changelog2019-11-19 15:14:51

Bug#953780: src:zip4j: fails to migrate to testing for too long

2020-03-30 Thread merkys
Hi Paul, On 2020-03-30 21:53, Paul Gevers wrote: > That assumption is wrong. Closure is done by either a "Closes" in the > changelog or by manual sending a message to bug-done, like I've done > now. Probably someone doing QA on the BTS would have closed it in due > time as the bug impacts no relea

Bug#951040: marked as done (python-yubico-tools: Depends: python3-argparse but it is not installable)

2020-03-30 Thread Debian Bug Tracking System
Your message dated Tue, 31 Mar 2020 04:36:02 + with message-id and subject line Bug#951040: fixed in python-yubico 1.3.3-0.3 has caused the Debian Bug report #951040, regarding python-yubico-tools: Depends: python3-argparse but it is not installable to be marked as done. This means that you

Bug#954582: samba: FTBFS glibc/stropts/python issue.

2020-03-30 Thread peter green
If my understanding is correct I see two possible ways forward. 1. Rebuild python3.8 against the new glibc. 2. Remove the stropts include from samba, it doesn't seem to actually be used for anything (at least I can't find any other references to HAVE_STROPTS_H in the code). I am currently t

Bug#954587: marked as done (yp-tools: FTBFS: nis-hosts.c:232:21: error: ‘RES_USE_INET6’ undeclared (first use in this function))

2020-03-30 Thread Debian Bug Tracking System
Your message dated Tue, 31 Mar 2020 03:50:14 + with message-id and subject line Bug#954587: fixed in yp-tools 3.3-5.3 has caused the Debian Bug report #954587, regarding yp-tools: FTBFS: nis-hosts.c:232:21: error: ‘RES_USE_INET6’ undeclared (first use in this function) to be marked as done.

Bug#934949: marked as done (clips: build-depends on removed package pdf2htmlex)

2020-03-30 Thread Debian Bug Tracking System
Your message dated Tue, 31 Mar 2020 03:48:41 + with message-id and subject line Bug#934949: fixed in clips 6.30-4.1 has caused the Debian Bug report #934949, regarding clips: build-depends on removed package pdf2htmlex to be marked as done. This means that you claim that the problem has been

Bug#952621: marked as done (clips: FTBFS: build-dependency not installable: pdf2htmlex)

2020-03-30 Thread Debian Bug Tracking System
Your message dated Tue, 31 Mar 2020 03:48:41 + with message-id and subject line Bug#952621: fixed in clips 6.30-4.1 has caused the Debian Bug report #952621, regarding clips: FTBFS: build-dependency not installable: pdf2htmlex to be marked as done. This means that you claim that the problem h

Bug#934949: marked as done (clips: build-depends on removed package pdf2htmlex)

2020-03-30 Thread Debian Bug Tracking System
Your message dated Tue, 31 Mar 2020 03:48:41 + with message-id and subject line Bug#952621: fixed in clips 6.30-4.1 has caused the Debian Bug report #952621, regarding clips: build-depends on removed package pdf2htmlex to be marked as done. This means that you claim that the problem has been

Bug#925721: marked as done (jnettop: ftbfs with GCC-9)

2020-03-30 Thread Debian Bug Tracking System
Your message dated Tue, 31 Mar 2020 03:49:55 + with message-id and subject line Bug#925721: fixed in jnettop 0.13.0-1.1 has caused the Debian Bug report #925721, regarding jnettop: ftbfs with GCC-9 to be marked as done. This means that you claim that the problem has been dealt with. If this i

Bug#952057: marked as done (kdocker: FTBFS: src/xlibutil.h:33:10: fatal error: X11/Xlib-xcb.h: No such file or directory)

2020-03-30 Thread Debian Bug Tracking System
Your message dated Tue, 31 Mar 2020 03:50:01 + with message-id and subject line Bug#952057: fixed in kdocker 5.0-1.1 has caused the Debian Bug report #952057, regarding kdocker: FTBFS: src/xlibutil.h:33:10: fatal error: X11/Xlib-xcb.h: No such file or directory to be marked as done. This mea

Bug#951979: marked as done (antimony: FTBFS: datum.h:3:10: fatal error: Python.h: No such file or directory)

2020-03-30 Thread Debian Bug Tracking System
Your message dated Tue, 31 Mar 2020 03:48:26 + with message-id and subject line Bug#951979: fixed in antimony 0.9.3-1.2 has caused the Debian Bug report #951979, regarding antimony: FTBFS: datum.h:3:10: fatal error: Python.h: No such file or directory to be marked as done. This means that yo

Bug#881009: marked as done (src:clips: typo in maintainer address (.og instead of .org))

2020-03-30 Thread Debian Bug Tracking System
Your message dated Tue, 31 Mar 2020 03:48:41 + with message-id and subject line Bug#881009: fixed in clips 6.30-4.1 has caused the Debian Bug report #881009, regarding src:clips: typo in maintainer address (.og instead of .org) to be marked as done. This means that you claim that the problem

Bug#952621: marked as done (clips: FTBFS: build-dependency not installable: pdf2htmlex)

2020-03-30 Thread Debian Bug Tracking System
Your message dated Tue, 31 Mar 2020 03:48:41 + with message-id and subject line Bug#934949: fixed in clips 6.30-4.1 has caused the Debian Bug report #934949, regarding clips: FTBFS: build-dependency not installable: pdf2htmlex to be marked as done. This means that you claim that the problem h

Processed: py2removal bugs severity updates - 2020-03-31 02:42:37.359181+00:00

2020-03-30 Thread Debian Bug Tracking System
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 https://lists.debian.org/debian-devel-an

Bug#954582: samba: FTBFS glibc/stropts/python issue.

2020-03-30 Thread peter green
The samba FTBFS is blocking the python 3.8 transition in raspbian bullseye, so I decided to take a look. error: Unable to determine origin of type `struct cli_credentials' I don't think this is the error that is causing the build failure. The same error can be seen in succesful build logs. e.

Bug#954679: marked as done (mockery: FTBFS: src/golang.org/x/tools/internal/imports/mod.go:17:2: cannot find package "golang.org/x/mod/module")

2020-03-30 Thread Debian Bug Tracking System
Your message dated Tue, 31 Mar 2020 01:04:05 + with message-id and subject line Bug#954679: fixed in mockery 0.0~git20181123.e78b021-3 has caused the Debian Bug report #954679, regarding mockery: FTBFS: src/golang.org/x/tools/internal/imports/mod.go:17:2: cannot find package "golang.org/x/mod

Bug#954679: marked as pending in mockery

2020-03-30 Thread Dmitry Smirnov
Control: tag -1 pending Hello, Bug #954679 in mockery 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/go-team/packages/mockery/-/commit/be4d52ac1d425b503fd7ff48

Processed: Bug#954679 marked as pending in mockery

2020-03-30 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #954679 [src:mockery] mockery: FTBFS: src/golang.org/x/tools/internal/imports/mod.go:17:2: cannot find package "golang.org/x/mod/module" Added tag(s) pending. -- 954679: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=954679 Debian Bug Tracki

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

2020-03-30 Thread Debian Bug Tracking System
Your message dated Mon, 30 Mar 2020 17:29:50 -0700 with message-id and subject line Fixed in latest version 2.1.0.5.geb5ee87-1 has caused the Debian Bug report #938184, regarding python-socksipychain: Python2 removal in sid/bullseye to be marked as done. This means that you claim that the problem

Bug#952359: marked as done (strophejs: FTBFS: Error: ERROR: module path does not exist: /usr/lib/nodejs/almond/almond.js for module named: /usr/lib/nodejs/almond/almond.js. Path is relative to: /<

2020-03-30 Thread Debian Bug Tracking System
Your message dated Mon, 30 Mar 2020 23:40:53 + with message-id and subject line Bug#952359: fixed in strophejs 1.2.14+dfsg-5 has caused the Debian Bug report #952359, regarding strophejs: FTBFS: Error: ERROR: module path does not exist: /usr/lib/nodejs/almond/almond.js for module named: /usr

Bug#954698: serf: FTBFS: 1) test_ssltunnel_basic_auth_server_has_keepalive_off: test/test_context.c:2138: expected <0> but was <120199>

2020-03-30 Thread James McCoy
On Mon, Mar 30, 2020 at 02:53:40PM -0400, Justin Erenkrantz wrote: > Here's a tentative patch that causes the test cases to pass with OpenSSL > 1.1.1e+ for me on Debian Sid. > > James, can you please give it a go and confirm that it works for you? The package does build and pass tests with the pa

Bug#952359: Please apply the patch and upload

2020-03-30 Thread Sunil Mohan Adapa
Hello, Only a few days remain until the package is removed from testing because of this bug. As a consequence, libjs-jsxc, which is used in FreedomBox to provide a web-based XMPP client will also be removed. Please consider applying the attached simple patch and prevent removal this package and i

Processed: your mail

2020-03-30 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > tag 952359 + patch Bug #952359 [src:strophejs] strophejs: FTBFS: Error: ERROR: module path does not exist: /usr/lib/nodejs/almond/almond.js for module named: /usr/lib/nodejs/almond/almond.js. Path is relative to: /<> Added tag(s) patch. > thanks

Bug#925721: jnettop: diff for NMU version 0.13.0-1.1

2020-03-30 Thread Sudip Mukherjee
Control: tags 925721 + patch Control: tags 925721 + pending Dear maintainer, I've prepared an NMU for jnettop (versioned as 0.13.0-1.1) and uploaded it mentors for sponsoring. Please feel free to tell me if I should remove it. -- Regards Sudip diff -Nru jnettop-0.13.0/debian/changelog jnettop-0

Processed: jnettop: diff for NMU version 0.13.0-1.1

2020-03-30 Thread Debian Bug Tracking System
Processing control commands: > tags 925721 + patch Bug #925721 [src:jnettop] jnettop: ftbfs with GCC-9 Added tag(s) patch. > tags 925721 + pending Bug #925721 [src:jnettop] jnettop: ftbfs with GCC-9 Added tag(s) pending. -- 925721: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=925721 Debian

Processed: Re: Bug#955367: libdvdread7: crashes vlc when trying to read a DVD iso image

2020-03-30 Thread Debian Bug Tracking System
Processing control commands: > tags -1 + confirmed upstream Bug #955367 [libdvdread7] libdvdread7: crashes vlc when trying to read a DVD iso image Added tag(s) confirmed and upstream. > forwarded -1 https://code.videolan.org/videolan/libdvdread/issues/14 Bug #955367 [libdvdread7] libdvdread7: cra

Bug#954676: [Pkg-pascal-devel] Bug#954676: pasdoc: FTBFS: dh_installman: error: Could not determine section for ./pasdoc.1

2020-03-30 Thread Michalis Kamburelis
Paul Gevers napisał(a): > > Hi Michalis, > > On 30-03-2020 14:11, Michalis Kamburelis wrote: > > Do we know what the message "Could not determine section for" means, > > or how to investigate it? I mean, this manpage should go to section 1 > > ("User Commands"), which is indicated both by the file

Bug#953747: marked as done (icu: CVE-2020-10531)

2020-03-30 Thread Debian Bug Tracking System
Your message dated Mon, 30 Mar 2020 21:32:33 + with message-id and subject line Bug#953747: fixed in icu 57.1-6+deb9u4 has caused the Debian Bug report #953747, regarding icu: CVE-2020-10531 to be marked as done. This means that you claim that the problem has been dealt with. If this is not t

Bug#953770: marked as done (bluez: CVE-2020-0556)

2020-03-30 Thread Debian Bug Tracking System
Your message dated Mon, 30 Mar 2020 21:32:23 + with message-id and subject line Bug#953770: fixed in bluez 5.43-2+deb9u2 has caused the Debian Bug report #953770, regarding bluez: CVE-2020-0556 to be marked as done. This means that you claim that the problem has been dealt with. If this is no

Processed: closing 953716

2020-03-30 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > close 953716 Bug #953716 [src:libvirt] src:libvirt: fails to migrate to testing for too long Marked Bug as done > thanks Stopping processing here. Please contact me if you need assistance. -- 953716: https://bugs.debian.org/cgi-bin/bugreport.cgi

Bug#955284: marked as done (gitinspector crashes: TypeError: 'bool' object is not iterable)

2020-03-30 Thread Debian Bug Tracking System
Your message dated Mon, 30 Mar 2020 20:48:37 + with message-id and subject line Bug#955284: fixed in gitinspector 0.4.4+dfsg-7 has caused the Debian Bug report #955284, regarding gitinspector crashes: TypeError: 'bool' object is not iterable to be marked as done. This means that you claim tha

Bug#954018: marked as done (src:refpolicy: fails to migrate to testing for too long)

2020-03-30 Thread Debian Bug Tracking System
Your message dated Mon, 30 Mar 2020 20:33:35 + with message-id and subject line Bug#954018: fixed in refpolicy 2:2.20190201-7.1 has caused the Debian Bug report #954018, regarding src:refpolicy: fails to migrate to testing for too long to be marked as done. This means that you claim that the

Bug#954511: Can someone habe a look at bioperl-run in connection with kalign (was: bioperl-run is marked for autoremoval from testing]

2020-03-30 Thread Pranav Ballaney
Hi, Yes, Kalign is on v3 now. I've pushed some patches to fix this bug. All build-time tests pass now. Autopkgtests don't, however, but that issue seems to be unrelated. Please take a look at https://salsa.debian.org/med-team/bioperl-run and verify the patches. This is my first time working with qu

Bug#934949: clips: diff for NMU version 6.30-4.1

2020-03-30 Thread Håvard Flaget Aasen
Package: clips Version: 6.30-4 Severity: normal Tags: patch pending Dear maintainer, I've prepared an NMU for clips (versioned as 6.30-4.1) and uploaded it to mentors. Please feel free to tell me if I should remove it. Regards. Håvard diff -Nru clips-6.30/debian/changelog clips-6.30/debian/chan

Bug#954676: pasdoc: FTBFS: dh_installman: error: Could not determine section for ./pasdoc.1

2020-03-30 Thread Paul Gevers
Hi Michalis, On 30-03-2020 14:11, Michalis Kamburelis wrote: > Do we know what the message "Could not determine section for" means, > or how to investigate it? I mean, this manpage should go to section 1 > ("User Commands"), which is indicated both by the filename "pasdoc.1" > and by text inside "

Bug#955135: marked as done (TypeError: '<' not supported between instances of 'NotImplementedType' and 'int')

2020-03-30 Thread Debian Bug Tracking System
Your message dated Mon, 30 Mar 2020 19:33:41 + with message-id and subject line Bug#955135: fixed in unattended-upgrades 2.1 has caused the Debian Bug report #955135, regarding TypeError: '<' not supported between instances of 'NotImplementedType' and 'int' to be marked as done. This means t

Bug#953970: Taking over DPMT (Was: python-boto: autopkgtest failure with Python 3.8 as default)

2020-03-30 Thread Andreas Tille
On Mon, Mar 30, 2020 at 11:18:34AM -0400, Noah Meyerhans wrote: > On Mon, Mar 30, 2020 at 11:44:23AM +0200, Andreas Tille wrote: > > I wonder whether we should take over python-boto into DPMT maintenance > > which would enable commits to Git way more easily. > > If it's going to move, might I sug

Bug#954698: serf: FTBFS: 1) test_ssltunnel_basic_auth_server_has_keepalive_off: test/test_context.c:2138: expected <0> but was <120199>

2020-03-30 Thread Justin Erenkrantz
Here's a tentative patch that causes the test cases to pass with OpenSSL 1.1.1e+ for me on Debian Sid. James, can you please give it a go and confirm that it works for you? Before I commit, we'd also need to gate this based on the new OpenSSL constant. We could gate based upon the OpenSSL versio

Bug#953780: marked as done (src:zip4j: fails to migrate to testing for too long)

2020-03-30 Thread Debian Bug Tracking System
Your message dated Mon, 30 Mar 2020 20:53:58 +0200 with message-id <74ef34de-2a9f-408c-602d-4a5d8d18a...@debian.org> and subject line Re: Bug#953780: src:zip4j: fails to migrate to testing for too long has caused the Debian Bug report #953780, regarding src:zip4j: fails to migrate to testing for t

Processed: your mail

2020-03-30 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > tags 955359 + help Bug #955359 [swi-prolog] swi-prolog: FTBFS on mips: error due to ATOMIC Added tag(s) help. > thanks Stopping processing here. Please contact me if you need assistance. -- 955359: https://bugs.debian.org/cgi-bin/bugreport.cgi?b

Bug#937273: marked as done (pepper: Python2 removal in sid/bullseye)

2020-03-30 Thread Debian Bug Tracking System
Your message dated Mon, 30 Mar 2020 18:48:46 + with message-id and subject line Bug#937273: fixed in pepper 0.3.3-4 has caused the Debian Bug report #937273, regarding pepper: Python2 removal in sid/bullseye to be marked as done. This means that you claim that the problem has been dealt with.

Processed: bug 954079 is forwarded to https://github.com/glyph/automat/issues/118

2020-03-30 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > forwarded 954079 https://github.com/glyph/automat/issues/118 Bug #954079 [automat] magic-wormhole: Fails to send with a type error Set Bug forwarded-to-address to 'https://github.com/glyph/automat/issues/118'. > thanks Stopping processing here. P

Processed (with 1 error): Re: Bug#954079: magic-wormhole: Fails to send with a type error

2020-03-30 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > reassign 954079 automat Bug #954079 [magic-wormhole] magic-wormhole: Fails to send with a type error Bug reassigned from package 'magic-wormhole' to 'automat'. No longer marked as found in versions magic-wormhole/0.11.2-1. Ignoring request to alte

Processed: yp-tools: diff for NMU version 3.3-5.3

2020-03-30 Thread Debian Bug Tracking System
Processing control commands: > tags 954587 + patch Bug #954587 [src:yp-tools] yp-tools: FTBFS: nis-hosts.c:232:21: error: ‘RES_USE_INET6’ undeclared (first use in this function) Added tag(s) patch. > tags 954587 + pending Bug #954587 [src:yp-tools] yp-tools: FTBFS: nis-hosts.c:232:21: error: ‘RE

Bug#954587: yp-tools: diff for NMU version 3.3-5.3

2020-03-30 Thread Sudip Mukherjee
Control: tags 954587 + patch Control: tags 954587 + pending Dear maintainer, I've prepared an NMU for yp-tools (versioned as 3.3-5.3) and uploaded it to mentors for sponsoring. Please feel free to tell me if I should remove it. -- Regards Sudip diff -Nru yp-tools-3.3/debian/changelog yp-tools-3

Bug#954079: magic-wormhole: Fails to send with a type error

2020-03-30 Thread Antoine Beaupré
reassign 954079 automat affects 954079 magic-wormhole forward 954079 https://github.com/glyph/automat/issues/118 thanks On 2020-03-16 13:49:58, Guillem Jover wrote: > Package: magic-wormhole > Version: 0.11.2-1 > Severity: serious > > Hi! > > This package does not work anymore in unstable. I guess

Processed: bug 952041 is forwarded to https://github.com/seattlerb/hoe/issues/106

2020-03-30 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > forwarded 952041 https://github.com/seattlerb/hoe/issues/106 Bug #952041 [src:ruby-hoe] ruby-hoe: FTBFS: ERROR: Test "ruby2.7" failed. Set Bug forwarded-to-address to 'https://github.com/seattlerb/hoe/issues/106'. > thanks Stopping processing here

Bug#952041: more information

2020-03-30 Thread Daniel Leidert
The expected date is the current date, whereas the actual date is the same as the how.gemspec's file date (in the package it is Feb. 6th; in Git it is March 2nd. I've opened an issue to clarify the situation: https://github.com/seattlerb/hoe/issues/106 signature.asc Description: This is a digital

Processed: [bts-link] source package python3.8

2020-03-30 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > # > # bts-link upstream status pull for source package python3.8 > # 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 Setti

Processed: [bts-link] source package systemd

2020-03-30 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > # > # bts-link upstream status pull for source package systemd > # 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 Setting

Processed: [bts-link] source package python2.7

2020-03-30 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > # > # bts-link upstream status pull for source package python2.7 > # 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 Setti

Bug#954541: marked as done (cmark: FTBFS: dh_auto_test: error: cd obj-x86_64-linux-gnu && make -j4 test ARGS\+=-j4 returned exit code 2)

2020-03-30 Thread Debian Bug Tracking System
Your message dated Mon, 30 Mar 2020 17:18:28 + with message-id and subject line Bug#954541: fixed in cmark 0.29.0-2 has caused the Debian Bug report #954541, regarding cmark: FTBFS: dh_auto_test: error: cd obj-x86_64-linux-gnu && make -j4 test ARGS\+=-j4 returned exit code 2 to be marked as d

Processed: [bts-link] source package ruby-excon

2020-03-30 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > # > # bts-link upstream status pull for source package ruby-excon > # 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 Sett

Processed: [bts-link] source package python3.7

2020-03-30 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > # > # bts-link upstream status pull for source package python3.7 > # 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 Setti

Bug#951979: antimony: diff for NMU version 0.9.3-1.2

2020-03-30 Thread Håvard Flaget Aasen
Control: tags 951979 + patch Control: tags 951979 + pending Dear maintainer, I've prepared an NMU for antimony (versioned as 0.9.3-1.2) and uploaded it to mentors. Please feel free to tell me if I should remove it. Regards. Håvard diff -Nru antimony-0.9.3/debian/changelog antimony-0.9.3/debian/c

Bug#936366: marked as done (darkradiant: Python2 removal in sid/bullseye)

2020-03-30 Thread Debian Bug Tracking System
Your message dated Mon, 30 Mar 2020 17:03:31 + with message-id and subject line Bug#936366: fixed in darkradiant 2.7.0-1 has caused the Debian Bug report #936366, regarding darkradiant: Python2 removal in sid/bullseye to be marked as done. This means that you claim that the problem has been d

Processed: antimony: diff for NMU version 0.9.3-1.2

2020-03-30 Thread Debian Bug Tracking System
Processing control commands: > tags 951979 + patch Bug #951979 [src:antimony] antimony: FTBFS: datum.h:3:10: fatal error: Python.h: No such file or directory Added tag(s) patch. > tags 951979 + pending Bug #951979 [src:antimony] antimony: FTBFS: datum.h:3:10: fatal error: Python.h: No such file

Bug#936366: marked as pending in darkradiant

2020-03-30 Thread Tobias Frost
Control: tag -1 pending Hello, Bug #936366 in darkradiant 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/games-team/darkradiant/-/commit/3bcdf13fcbec29be1398f6

Processed: Bug#936366 marked as pending in darkradiant

2020-03-30 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #936366 [src:darkradiant] darkradiant: Python2 removal in sid/bullseye Ignoring request to alter tags of bug #936366 to the same tags previously set -- 936366: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=936366 Debian Bug Tracking System Co

Bug#952267: marked as done (fsplib: FTBFS: dpkg-buildpackage: error: dpkg-source -b . subprocess returned exit status 2)

2020-03-30 Thread Debian Bug Tracking System
Your message dated Mon, 30 Mar 2020 16:33:37 + with message-id and subject line Bug#952267: fixed in fsplib 0.14-2 has caused the Debian Bug report #952267, regarding fsplib: FTBFS: dpkg-buildpackage: error: dpkg-source -b . subprocess returned exit status 2 to be marked as done. This means

Bug#936721: marked as done (idjc: Python2 removal in sid/bullseye)

2020-03-30 Thread Debian Bug Tracking System
Your message dated Mon, 30 Mar 2020 16:29:18 + with message-id and subject line Bug#955171: Removed package(s) from unstable has caused the Debian Bug report #936721, regarding idjc: Python2 removal in sid/bullseye to be marked as done. This means that you claim that the problem has been deal

Bug#936634: marked as done (go2: Python2 removal in sid/bullseye)

2020-03-30 Thread Debian Bug Tracking System
Your message dated Mon, 30 Mar 2020 16:30:05 + with message-id and subject line Bug#955178: Removed package(s) from unstable has caused the Debian Bug report #936634, regarding go2: Python2 removal in sid/bullseye to be marked as done. This means that you claim that the problem has been dealt

Bug#928324: marked as done (crash: UnicodeEncodeError)

2020-03-30 Thread Debian Bug Tracking System
Your message dated Mon, 30 Mar 2020 16:30:05 + with message-id and subject line Bug#955178: Removed package(s) from unstable has caused the Debian Bug report #928324, regarding crash: UnicodeEncodeError to be marked as done. This means that you claim that the problem has been dealt with. If t

Bug#936158: marked as done (asterisk-testsuite: Python2 removal in sid/bullseye)

2020-03-30 Thread Debian Bug Tracking System
Your message dated Mon, 30 Mar 2020 16:30:28 + with message-id and subject line Bug#955253: Removed package(s) from unstable has caused the Debian Bug report #936158, regarding asterisk-testsuite: Python2 removal in sid/bullseye to be marked as done. This means that you claim that the problem

Bug#935204: marked as done (go2: uninstalling go2 breaks "bash cd")

2020-03-30 Thread Debian Bug Tracking System
Your message dated Mon, 30 Mar 2020 16:30:05 + with message-id and subject line Bug#955178: Removed package(s) from unstable has caused the Debian Bug report #935204, regarding go2: uninstalling go2 breaks "bash cd" to be marked as done. This means that you claim that the problem has been dea

Bug#937191: marked as done (openalpr: Python2 removal in sid/bullseye)

2020-03-30 Thread Debian Bug Tracking System
Your message dated Mon, 30 Mar 2020 16:28:56 + with message-id and subject line Bug#955163: Removed package(s) from unstable has caused the Debian Bug report #937191, regarding openalpr: Python2 removal in sid/bullseye to be marked as done. This means that you claim that the problem has been

Bug#908802: marked as done (asttest missing from asttest)

2020-03-30 Thread Debian Bug Tracking System
Your message dated Mon, 30 Mar 2020 16:30:28 + with message-id and subject line Bug#955253: Removed package(s) from unstable has caused the Debian Bug report #908802, regarding asttest missing from asttest to be marked as done. This means that you claim that the problem has been dealt with. I

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

2020-03-30 Thread Debian Bug Tracking System
Your message dated Mon, 30 Mar 2020 16:29:39 + with message-id and subject line Bug#955177: Removed package(s) from unstable has caused the Debian Bug report #937946, regarding python-nids: Python2 removal in sid/bullseye to be marked as done. This means that you claim that the problem has be

Bug#922588: marked as done (FTBFS against opencv 4.0.1 (exp))

2020-03-30 Thread Debian Bug Tracking System
Your message dated Mon, 30 Mar 2020 16:28:56 + with message-id and subject line Bug#955163: Removed package(s) from unstable has caused the Debian Bug report #922588, regarding FTBFS against opencv 4.0.1 (exp) to be marked as done. This means that you claim that the problem has been dealt wit

Bug#885308: marked as done (idjc: Depends on unmaintained pygtk)

2020-03-30 Thread Debian Bug Tracking System
Your message dated Mon, 30 Mar 2020 16:29:18 + with message-id and subject line Bug#955171: Removed package(s) from unstable has caused the Debian Bug report #885308, regarding idjc: Depends on unmaintained pygtk to be marked as done. This means that you claim that the problem has been dealt

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

2020-03-30 Thread Debian Bug Tracking System
Your message dated Mon, 30 Mar 2020 16:22:05 + with message-id and subject line Bug#955162: Removed package(s) from unstable has caused the Debian Bug report #937916, regarding python-mhash: Python2 removal in sid/bullseye to be marked as done. This means that you claim that the problem has b

Bug#942623: marked as done (src:frevial: Maintainer email address not working)

2020-03-30 Thread Debian Bug Tracking System
Your message dated Mon, 30 Mar 2020 16:19:39 + with message-id and subject line Bug#955159: Removed package(s) from unstable has caused the Debian Bug report #942623, regarding src:frevial: Maintainer email address not working to be marked as done. This means that you claim that the problem h

Bug#936559: marked as done (freevial: Python2 removal in sid/bullseye)

2020-03-30 Thread Debian Bug Tracking System
Your message dated Mon, 30 Mar 2020 16:19:39 + with message-id and subject line Bug#955159: Removed package(s) from unstable has caused the Debian Bug report #936559, regarding freevial: Python2 removal in sid/bullseye to be marked as done. This means that you claim that the problem has been

Bug#912487: marked as done (pyntor: Please migrate to python3-pygame)

2020-03-30 Thread Debian Bug Tracking System
Your message dated Mon, 30 Mar 2020 16:17:35 + with message-id and subject line Bug#955148: Removed package(s) from unstable has caused the Debian Bug report #912487, regarding pyntor: Please migrate to python3-pygame to be marked as done. This means that you claim that the problem has been d

Bug#937492: marked as done (pyntor: Python2 removal in sid/bullseye)

2020-03-30 Thread Debian Bug Tracking System
Your message dated Mon, 30 Mar 2020 16:17:35 + with message-id and subject line Bug#955148: Removed package(s) from unstable has caused the Debian Bug report #912487, regarding pyntor: Python2 removal in sid/bullseye to be marked as done. This means that you claim that the problem has been de

Bug#936267: marked as done (calabash: Python2 removal in sid/bullseye)

2020-03-30 Thread Debian Bug Tracking System
Your message dated Mon, 30 Mar 2020 16:20:14 + with message-id and subject line Bug#955160: Removed package(s) from unstable has caused the Debian Bug report #936267, regarding calabash: Python2 removal in sid/bullseye to be marked as done. This means that you claim that the problem has been

Bug#954154: marked as done (src:salt: Requires a package outside of Main)

2020-03-30 Thread Debian Bug Tracking System
Your message dated Mon, 30 Mar 2020 16:19:13 + with message-id and subject line Bug#954154: fixed in salt 3000+dfsg1-4 has caused the Debian Bug report #954154, regarding src:salt: Requires a package outside of Main to be marked as done. This means that you claim that the problem has been dea

Bug#954541: cmark: FTBFS: dh_auto_test: error: cd obj-x86_64-linux-gnu && make -j4 test ARGS\+=-j4 returned exit code 2

2020-03-30 Thread Hubert Chathi
On Sun, 22 Mar 2020 08:53:46 +0100, Lucas Nussbaum said: > During a rebuild of all packages in sid, your package failed to build > on amd64. [...] It looks like the test failure would be fixed by this commit from upstream: https://github.com/commonmark/cmark/commit/68c3a91166347a32a57fb81223750

Bug#943033: marked as done (dictclient: Python2 removal in sid/bullseye)

2020-03-30 Thread Debian Bug Tracking System
Your message dated Mon, 30 Mar 2020 16:12:12 + with message-id and subject line Bug#954456: Removed package(s) from unstable has caused the Debian Bug report #943033, regarding dictclient: Python2 removal in sid/bullseye to be marked as done. This means that you claim that the problem has bee

Bug#954456: marked as done (RM: dictclient -- RoQA; python2-only; no real development in 3 years; no rdeps; very low popcon)

2020-03-30 Thread Debian Bug Tracking System
Your message dated Mon, 30 Mar 2020 16:12:04 + with message-id and subject line Bug#954456: Removed package(s) from unstable has caused the Debian Bug report #954456, regarding RM: dictclient -- RoQA; python2-only; no real development in 3 years; no rdeps; very low popcon to be marked as done

Processed: tagging 936366

2020-03-30 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > tags 936366 + pending Bug #936366 [src:darkradiant] darkradiant: Python2 removal in sid/bullseye Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 936366: https://bugs.debian.org/cgi-bin/bugrep

Processed: Bug#954154 marked as pending in salt

2020-03-30 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #954154 [src:salt] src:salt: Requires a package outside of Main Added tag(s) pending. -- 954154: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=954154 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#954154: marked as pending in salt

2020-03-30 Thread Benjamin Drung
Control: tag -1 pending Hello, Bug #954154 in salt 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/salt-team/salt/-/commit/99a56cbd6582f99b8677e7f52b8bc5163e7f3

Bug#953970: Taking over DPMT (Was: python-boto: autopkgtest failure with Python 3.8 as default)

2020-03-30 Thread Noah Meyerhans
On Mon, Mar 30, 2020 at 11:44:23AM +0200, Andreas Tille wrote: > I wonder whether we should take over python-boto into DPMT maintenance > which would enable commits to Git way more easily. If it's going to move, might I suggest maintaining it within the cloud-team instead? Among other things, th

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

2020-03-30 Thread Debian Bug Tracking System
Your message dated Mon, 30 Mar 2020 15:04:42 + with message-id and subject line Bug#938212: fixed in python-termcolor 1.1.0-3 has caused the Debian Bug report #938212, regarding python-termcolor: Python2 removal in sid/bullseye to be marked as done. This means that you claim that the problem

Bug#930527: linux-image-4.19.0-5-amd64: when logging out, not the whole screen is erased, leaving private information

2020-03-30 Thread Ivo De Decker
Control: severity -1 important Control: fixed -1 5.4.19-1 Control: retitle -1 linux-image-4.19.0-5-amd64: nouveau driver sometimes crashes Hi, Thanks for the clarification. On Mon, Mar 30, 2020 at 01:05:20PM +0200, Vincent Lefevre wrote: > On 2020-03-30 09:06:15 +0200, Ivo De Decker wrote: > > O

Bug#954511: Can someone habe a look at bioperl-run in connection with kalign (was: bioperl-run is marked for autoremoval from testing]

2020-03-30 Thread Christopher Fields
I have seen per exit codes of 256 for other bioperl-run wrappers in the past where the application API changed (constant game of playing catchup unfortunately). That seems to be the case here based on the error. Is kalign is now at v3? chris On 3/30/20, 2:57 AM, "Andreas Tille" wrote:

Processed: Re: linux-image-4.19.0-5-amd64: when logging out, not the whole screen is erased, leaving private information

2020-03-30 Thread Debian Bug Tracking System
Processing control commands: > severity -1 important Bug #930527 [src:linux] linux-image-4.19.0-5-amd64: when logging out, not the whole screen is erased, leaving private information Severity set to 'important' from 'grave' > fixed -1 5.4.19-1 Bug #930527 [src:linux] linux-image-4.19.0-5-amd64: w

Bug#955356: marked as done (shim-signed-* - Uninstallable)

2020-03-30 Thread Debian Bug Tracking System
Your message dated Mon, 30 Mar 2020 14:48:57 + with message-id and subject line Bug#955356: fixed in shim 15+1533136590.3beb971-9 has caused the Debian Bug report #955356, regarding shim-signed-* - Uninstallable to be marked as done. This means that you claim that the problem has been dealt w

Bug#955360: phpmyadmin: depends on non-existing php-recode package

2020-03-30 Thread Gianfranco Costamagna
Source: phpmyadmin Version: 4.9.5+dfsg1-1 Severity: serious Tags: patch Hello, looks like php-recode is now removed in new php-defaults_75 php-defaults (75) unstable; urgency=medium * Remove the php-recode, as there's no php7.4-recode anymore (Closes: #955027) so, please drop it from

Bug#938212: marked as pending in python-termcolor

2020-03-30 Thread Sandro Tosi
Control: tag -1 pending Hello, Bug #938212 in python-termcolor 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/python/python-termcolor/-/commit/8

Processed: Bug#938212 marked as pending in python-termcolor

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

Bug#954635: golang-github-thecreeper-go-notify: FTBFS: Errors while processing: libdbus2.0-cil libglib2.0-cil libgtk2.0-cil libdbus-glib2.0-cil libnotify0.4-cil libnotify-cil-dev sbuild-build-depend

2020-03-30 Thread Joseph Shields
Your analysis is correct, Emilio. It’s related to that upstream bug, in that `gacutil` is used by packages to register their libraries to the system library cache, but `gacutil` does not work until `/etc/mono/config` exists and contains a mapping for System.Native. There’s a pre-depends from mo

Bug#955359: swi-prolog: FTBFS on mips: error due to ATOMIC

2020-03-30 Thread Lev Lamberov
Package: swi-prolog Version: 8.1.26+dfsg-2 Severity: serious Dear Maintainer, current development version of swi-prolog fails to build from source [log]: [ 84%] Building C object packages/xpce/CMakeFiles/plugin_pl2xpce.dir/swipl/pcecall.c.o cd /<>/build/packages/xpce && /usr/bin/cc -Dplugin_pl2

Bug#954500: marked as done (pyqi: FTBFS: dpkg-buildpackage: error: dpkg-source -b . subprocess returned exit status 2)

2020-03-30 Thread Debian Bug Tracking System
Your message dated Mon, 30 Mar 2020 13:34:35 + with message-id and subject line Bug#954500: fixed in pyqi 0.3.2+dfsg-5 has caused the Debian Bug report #954500, regarding pyqi: FTBFS: dpkg-buildpackage: error: dpkg-source -b . subprocess returned exit status 2 to be marked as done. This mean

  1   2   >