Bug#954064: obsolete: no longer used to build sugar-artwork

Package: icon-slicer Version: 0.3-8 Severity: grave Justification: renders package unusable -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 icon-slicer is no longer used anywhere in Debian: Its only reverse dependency - src:sugar-artwork This is a reminder to drop this package from testing/unsta

Processed: unblock 953775 with 953795

Processing commands for cont...@bugs.debian.org: > unblock 953775 with 953795 Bug #953775 [src:ibus] FTBFS with unicode-data 13.0.0 953775 was blocked by: 953795 953775 was not blocking any bugs. Removed blocking bug(s) of 953775: 953795 > thanks Stopping processing here. Please contact me if you

Bug#949793: marked as done (dh-shlibs fails for Python 3.8 libs)

Your message dated Mon, 16 Mar 2020 05:34:14 + with message-id and subject line Bug#949793: fixed in d-shlibs 0.89 has caused the Debian Bug report #949793, regarding dh-shlibs fails for Python 3.8 libs to be marked as done. This means that you claim that the problem has been dealt with. If t

Bug#954027: marked as done (insighttoolkit4 FTBFS with Pythin 3.8 as default)

Your message dated Mon, 16 Mar 2020 05:20:49 + with message-id and subject line Bug#954027: fixed in insighttoolkit4 4.13.2-dfsg1-8 has caused the Debian Bug report #954027, regarding insighttoolkit4 FTBFS with Pythin 3.8 as default to be marked as done. This means that you claim that the pro

Bug#937408: marked as done (pycodestyle: Python2 removal in sid/bullseye)

Your message dated Mon, 16 Mar 2020 05:20:56 + with message-id and subject line Bug#937408: fixed in pycodestyle 2.5.0-3 has caused the Debian Bug report #937408, regarding pycodestyle: Python2 removal in sid/bullseye to be marked as done. This means that you claim that the problem has been d

Bug#936480: marked as done (empy: Python2 removal in sid/bullseye)

Your message dated Mon, 16 Mar 2020 05:19:15 + with message-id and subject line Bug#936480: fixed in empy 3.3.2-5.1 has caused the Debian Bug report #936480, regarding empy: Python2 removal in sid/bullseye to be marked as done. This means that you claim that the problem has been dealt with. I

Bug#936480: empy: diff for NMU version 3.3.2-5.1

Control: tags 936480 + patch Dear maintainer, I've prepared an NMU for empy (versioned as 3.3.2-5.1). The diff is attached to this message. Regards. diff -Nru empy-3.3.2/debian/changelog empy-3.3.2/debian/changelog --- empy-3.3.2/debian/changelog 2020-02-17 14:56:03.0 -0500 +++ empy-3.

Bug#938819: marked as done (wheel: Python2 removal in sid/bullseye)

Your message dated Mon, 16 Mar 2020 05:04:15 + with message-id and subject line Bug#938819: fixed in wheel 0.33.6-3 has caused the Debian Bug report #938819, regarding wheel: Python2 removal in sid/bullseye to be marked as done. This means that you claim that the problem has been dealt with.

Processed: empy: diff for NMU version 3.3.2-5.1

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

Processed: Bug#937408 marked as pending in pycodestyle

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

Bug#937408: marked as pending in pycodestyle

Control: tag -1 pending Hello, Bug #937408 in pycodestyle 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/python-team/modules/pycodestyle/-/commit/0084eb3c5e94a

Bug#938819: marked as pending in wheel

Control: tag -1 pending Hello, Bug #938819 in wheel 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/python-team/modules/wheel/-/commit/c16e9766cb08921b8ce46f6a4

Processed: Bug#938819 marked as pending in wheel

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

Processed: py2removal bugs severity updates - 2020-03-16 03:35:24.953615+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 https://lists.debian.org/debian-devel-an

Bug#952599: fixed in insighttoolkit4 4.13.2-dfsg1-7

>[ Steve Robbins ] >* Update build-dep from swig3.0 --> swig3. Closes: #952599. This is a typo: the build-dependency is just "swig", which is presently swig 4. -Steve signature.asc Description: This is a digitally signed message part.

Bug#885213: make-dfsg: please migrate to guile-2.2

Rob Browning writes: > Actually now that guile-3.0 is in sid (though it's not yet building on > all the release architectures), I suppose we might just side-step 2.2 > entirely, but either would be much appreciated. > > Here this at least builds via "fakeroot debian/rules binary", but > regardles

Bug#953487: marked as pending in runescape

Control: tag -1 pending Hello, Bug #953487 in runescape 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/runescape/-/commit/9b3d6ff837e1f2cdb9be62e4bc

Processed: Bug#953714 marked as pending in runescape

Processing control commands: > tag -1 pending Bug #953714 [src:runescape] src:runescape: fails to migrate to testing for too long Added tag(s) pending. -- 953714: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=953714 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#953714: marked as pending in runescape

Control: tag -1 pending Hello, Bug #953714 in runescape 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/runescape/-/commit/9b3d6ff837e1f2cdb9be62e4bc

Processed: Bug#953487 marked as pending in runescape

Processing control commands: > tag -1 pending Bug #953487 [src:runescape] runescape: binaries for non-free not auto-built Added tag(s) pending. -- 953487: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=953487 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#952099: tootle: FTBFS: ../../src/Views/AbstractView.vala:24.5-24.23: error: Creation method of abstract class cannot be public.

Package: tootle Version: 0.2.0-2 Followup-For: Bug #952099 User: ubuntu-de...@lists.ubuntu.com Usertags: origin-ubuntu focal ubuntu-patch Hi, In Ubuntu, the attached patch was applied to achieve the following: * d/p/vala-0.46.patch: Make constructor for AbstractView protected to fix FTBFS

Bug#953989: borgbackup reports installed python3-msgpack is incompatible

On Sun, 15 Mar 2020 12:16:54 + Gordon Ball wrote: > Package: borgbackup > Version: 1.1.11-2 > Severity: grave > Justification: renders package unusable > > After updating python3-msgpack from 0.5.6-3 -> 0.6.2-1, attempting to > run any borg command fails with the following message, making bor

Bug#954039: prayer: FTBFS against glibc 2.30

Package: prayer Version: 1.3.5-dfsg1-6 Severity: serious Tags: patch ftbfs Justification: fails to build from source (but built successfully in the past) User: ubuntu-de...@lists.ubuntu.com Usertags: origin-ubuntu focal ubuntu-patch Hi, prayer currently FTBFS against glibc 2.30 in unstable. This

Bug#954037: openwince-jtag: FTBFS against glibc 2.30

Package: openwince-jtag Version: 0.5.1-7 Severity: serious Tags: patch ftbfs Justification: fails to build from source (but built successfully in the past) User: ubuntu-de...@lists.ubuntu.com Usertags: origin-ubuntu focal ubuntu-patch Hi, openwince-jtag FTBFS against glibc 2.30 in unstable due to

Bug#939983: marked as done (error: Unable to read from '/sys/fs/cgroup/unified/machine/cgroup.controllers')

Your message dated Mon, 16 Mar 2020 00:37:11 + (UTC) with message-id and subject line Re: [Pkg-libvirt-maintainers] Bug#939983: error: Unable to read from '/sys/fs/cgroup/unified/machine/cgroup.controllers' has caused the Debian Bug report #939983, regarding error: Unable to read from '/sys/

Bug#954033: pdfarranger: The package should depend on python3-gi-cairo. Otherwise the application will not render pages.

Package: pdfarranger Version: 1.1.1-1 Severity: grave Justification: renders package unusable Dear Maintainer, I tried using the application. It rendered empty pages and wrote a lot of TypeError: Couldn't find foreign struct converter for 'cairo.Context' to stderr. I searched the net on the error

Bug#954032: libvirt-daemon-driver-qemu: file conflict /usr/share/augeas/lenses/libvirtd_qemu.aug libvirt-daemon 5.6.0-3

Package: libvirt-daemon-driver-qemu Version: 6.0.0-2 Severity: serious Justification: uninstallable Missing a Replaces: tglase@tglase-nb:~ $ sudo apt-get --purge install libvirt-daemon-system-sysv Reading package lists... Done Building dependency tree Reading state information... Done Starting pk

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

Your message dated Sun, 15 Mar 2020 23:49:37 + with message-id and subject line Bug#938027: fixed in python-pip 20.0.2-1 has caused the Debian Bug report #938027, regarding python-pip: Python2 removal in sid/bullseye to be marked as done. This means that you claim that the problem has been de

Bug#925669:

This bug should be fixed in the current upstream from 66cc4b7 in https://github.com/jedwards1211/dewalls Treating warnings as errors has been disabled. Philip

Bug#951846: marked as done (explicit build dependency on python 3.7-doc)

Your message dated Sun, 15 Mar 2020 22:50:36 + with message-id and subject line Bug#951846: fixed in mutagen 1.44.0-1 has caused the Debian Bug report #951846, regarding explicit build dependency on python 3.7-doc to be marked as done. This means that you claim that the problem has been dealt

Bug#952213: marked as done (mutagen: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i pypy -p 7.3 returned exit code 13)

Your message dated Sun, 15 Mar 2020 22:50:36 + with message-id and subject line Bug#952213: fixed in mutagen 1.44.0-1 has caused the Debian Bug report #952213, regarding mutagen: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i pypy -p 7.3 returned exit code 13 to be marked as done

Processed: Bug#951846 marked as pending in mutagen

Processing control commands: > tag -1 pending Bug #951846 [src:mutagen] explicit build dependency on python 3.7-doc Added tag(s) pending. -- 951846: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=951846 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#952213: marked as pending in mutagen

Control: tag -1 pending Hello, Bug #952213 in mutagen 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/python-team/modules/mutagen/-/commit/4562c54abbfe7191182ad

Bug#951846: marked as pending in mutagen

Control: tag -1 pending Hello, Bug #951846 in mutagen 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/python-team/modules/mutagen/-/commit/65a391da637780fa5a16e

Processed: Bug#952213 marked as pending in mutagen

Processing control commands: > tag -1 pending Bug #952213 [src:mutagen] mutagen: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i pypy -p 7.3 returned exit code 13 Added tag(s) pending. -- 952213: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=952213 Debian Bug Tracking System Con

Bug#954027: insighttoolkit4 FTBFS with Pythin 3.8 as default

Source: insighttoolkit4 Version: 4.13.2-dfsg1-6 Severity: serious Tags: ftbfs https://buildd.debian.org/status/package.php?p=insighttoolkit4&suite=sid ... Traceback (most recent call last): File "/<>/Wrapping/Generators/SwigInterface/igenerator.py", line 971, in wrappingNamespace = genera

Bug#952109: marked as done (phpmyadmin-motranslator FTBFS with phpunit 8)

Your message dated Sun, 15 Mar 2020 21:38:18 + with message-id and subject line Bug#952109: fixed in phpmyadmin-motranslator 5.0.0-1 has caused the Debian Bug report #952109, regarding phpmyadmin-motranslator FTBFS with phpunit 8 to be marked as done. This means that you claim that the proble

Bug#952273: marked as done (phpmyadmin-motranslator: FTBFS: PHP Fatal error: Declaration of FunctionsTest::setUp() must be compatible with PHPUnit\Framework\TestCase::setUp(): void in /<

Your message dated Sun, 15 Mar 2020 21:38:18 + with message-id and subject line Bug#952109: fixed in phpmyadmin-motranslator 5.0.0-1 has caused the Debian Bug report #952109, regarding phpmyadmin-motranslator: FTBFS: PHP Fatal error: Declaration of FunctionsTest::setUp() must be compatible w

Bug#952599: marked as done (insighttoolkit4 build depends on the removed swig3.0)

Your message dated Sun, 15 Mar 2020 21:36:23 + with message-id and subject line Bug#952599: fixed in insighttoolkit4 4.13.2-dfsg1-7 has caused the Debian Bug report #952599, regarding insighttoolkit4 build depends on the removed swig3.0 to be marked as done. This means that you claim that the

Bug#952122: marked as done (dh-python fails tests with 3.7 removed)

Your message dated Sun, 15 Mar 2020 21:21:21 + with message-id and subject line Bug#952122: fixed in dh-python 4.20200315 has caused the Debian Bug report #952122, regarding dh-python fails tests with 3.7 removed to be marked as done. This means that you claim that the problem has been dealt

Bug#949757: marked as done (python-packaging: test failures due to wrong arch check)

Your message dated Sun, 15 Mar 2020 21:21:21 + with message-id and subject line Bug#948319: fixed in dh-python 4.20200315 has caused the Debian Bug report #948319, regarding python-packaging: test failures due to wrong arch check to be marked as done. This means that you claim that the proble

Bug#948319: marked as done (Fix setting _PYTHON_HOST_PLATFORM)

Your message dated Sun, 15 Mar 2020 21:21:21 + with message-id and subject line Bug#948319: fixed in dh-python 4.20200315 has caused the Debian Bug report #948319, regarding Fix setting _PYTHON_HOST_PLATFORM to be marked as done. This means that you claim that the problem has been dealt with.

Bug#948320: marked as done (pybuild hard codes the m modifier now dropped in Python 3.8)

Your message dated Sun, 15 Mar 2020 21:21:21 + with message-id and subject line Bug#948320: fixed in dh-python 4.20200315 has caused the Debian Bug report #948320, regarding pybuild hard codes the m modifier now dropped in Python 3.8 to be marked as done. This means that you claim that the pr

Bug#947789: marked as done (dh-python: autopkgtest needs update for new version of python3-defaults: doesn't depend on itself)

Your message dated Sun, 15 Mar 2020 21:21:21 + with message-id and subject line Bug#947789: fixed in dh-python 4.20200315 has caused the Debian Bug report #947789, regarding dh-python: autopkgtest needs update for new version of python3-defaults: doesn't depend on itself to be marked as done.

Bug#952599: marked as pending in insighttoolkit

Control: tag -1 pending Hello, Bug #952599 in insighttoolkit 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/med-team/insighttoolkit/-/commit/82fbfd7a0e1c63c76a

Processed: Bug#952599 marked as pending in insighttoolkit

Processing control commands: > tag -1 pending Bug #952599 [src:insighttoolkit4] insighttoolkit4 build depends on the removed swig3.0 Added tag(s) pending. -- 952599: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=952599 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#950214: marked as done (dh-python needs to be part of the autopkg test dependencies)

Your message dated Sun, 15 Mar 2020 21:54:58 +0100 with message-id <20200315205458.524yr5gjvqbo7...@sar0.p1otr.com> and subject line fixed in 4.20200315 has caused the Debian Bug report #950214, regarding dh-python needs to be part of the autopkg test dependencies to be marked as done. This means

Bug#953231: marked as done (python-humanize: autopkgtest regression: No module named 'pkg_resources')

Your message dated Sun, 15 Mar 2020 20:56:39 + with message-id and subject line Bug#953231: fixed in python-humanize 2.0.0-2 has caused the Debian Bug report #953231, regarding python-humanize: autopkgtest regression: No module named 'pkg_resources' to be marked as done. This means that you

Bug#953990: marked as done (rust-signal-hook needs a source-only upload.)

Your message dated Sun, 15 Mar 2020 20:57:51 + with message-id and subject line Bug#953990: fixed in rust-signal-hook 0.1.13-1 has caused the Debian Bug report #953990, regarding rust-signal-hook needs a source-only upload. to be marked as done. This means that you claim that the problem has

Bug#953230: balsa: autopkgtest failure: times out

On Fri 2020-03-06 10:16:13 +0100, Paul Gevers wrote: > PS: these kind of timeouts are bad for our infrastructure. If this bug > doesn't get fixed in a timely manner, I may add your package to our > ignore-list. Sorry about the delay in getting this fixed, Paul. I believe the test suite will no lo

Bug#953968: marked as done (junitparser: autopkgtest failure with Python 3.8 as default)

Your message dated Sun, 15 Mar 2020 20:50:32 + with message-id and subject line Bug#953968: fixed in junitparser 1.4.1-2 has caused the Debian Bug report #953968, regarding junitparser: autopkgtest failure with Python 3.8 as default to be marked as done. This means that you claim that the pro

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

Your message dated Sun, 15 Mar 2020 20:50:08 + with message-id and subject line Bug#953784: fixed in iwyu 8.0-4 has caused the Debian Bug report #953784, regarding src:iwyu: fails to migrate to testing for too long to be marked as done. This means that you claim that the problem has been deal

Bug#945903: marked as done (dh-python: py3compile in postinst fails on scripts in /usr/share/doc)

Your message dated Sun, 15 Mar 2020 21:41:33 +0100 with message-id <20200315204133.r4kkems2xu6f2...@sar0.p1otr.com> and subject line cannot reproduce has caused the Debian Bug report #945903, regarding dh-python: py3compile in postinst fails on scripts in /usr/share/doc to be marked as done. This

Bug#953944: marked as done (crmsh: flaky autopkgtest that times out regularly: missing isolation-machine restriction?)

Your message dated Sun, 15 Mar 2020 20:38:12 + with message-id and subject line Bug#953944: fixed in crmsh 4.2.0-3 has caused the Debian Bug report #953944, regarding crmsh: flaky autopkgtest that times out regularly: missing isolation-machine restriction? to be marked as done. This means th

Bug#953766: marked as done (glib-networking: tests fail with GLib 2.64: tls/tests/connection.c:2035:quit_on_handshake_complete: assertion failed (error == (g-tls-error-quark, 3)): error is NULL)

Your message dated Sun, 15 Mar 2020 20:38:26 + with message-id and subject line Bug#953766: fixed in glib2.0 2.64.1-1 has caused the Debian Bug report #953766, regarding glib-networking: tests fail with GLib 2.64: tls/tests/connection.c:2035:quit_on_handshake_complete: assertion failed (error

Processed: lowering severity

Processing commands for cont...@bugs.debian.org: > severity 943334 normal Bug #943334 [src:dh-python] please run the tests for all supported python versions Severity set to 'normal' from 'serious' > thanks Stopping processing here. Please contact me if you need assistance. -- 943334: https://bu

Bug#953230: marked as done (balsa: autopkgtest failure: times out)

Your message dated Sun, 15 Mar 2020 19:49:16 + with message-id and subject line Bug#953230: fixed in balsa 2.5.9-4 has caused the Debian Bug report #953230, regarding balsa: autopkgtest failure: times out to be marked as done. This means that you claim that the problem has been dealt with. If

Processed: Bug#953230 marked as pending in balsa

Processing control commands: > tag -1 pending Bug #953230 [src:balsa] balsa: autopkgtest failure: times out Added tag(s) pending. -- 953230: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=953230 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#953230: marked as pending in balsa

Control: tag -1 pending Hello, Bug #953230 in balsa 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/gnome-team/balsa/-/commit/7a026c8e8e0601e42aa8131f7545ac61b1

Bug#954018: src:refpolicy: fails to migrate to testing for too long

Source: refpolicy Version: 2:2.20190201-6 Severity: serious Control: fixed -1 2:2.20190201-7 Tags: sid bullseye pending User: release.debian@packages.debian.org Usertags: out-of-sync Dear maintainer(s), As recently announced [1], the Release Team now considers packages that are out-of-sync be

Processed: src:refpolicy: fails to migrate to testing for too long

Processing control commands: > fixed -1 2:2.20190201-7 Bug #954018 [src:refpolicy] src:refpolicy: fails to migrate to testing for too long Marked as fixed in versions refpolicy/2:2.20190201-7. -- 954018: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=954018 Debian Bug Tracking System Contact

Bug#953851: pymissile: should this package be removed?

> While these are all good arguments for removal, I still got the hardware > and thus enjoy having the software to use it in Debian. :) > > But I realise that it need some porting to keep working, and lack the > spare time required to do it myself. :( are you ok with removing this package now, and

Processed: Re: Bug#953983: gcr: FTBFS (intermittently?) on amd64: gcr:gcr-base / system-prompt killed by signal 11 SIGSEGV

Processing control commands: > severity -1 important Bug #953983 [src:gcr] gcr: FTBFS (intermittently?) on amd64: gcr:gcr-base / system-prompt killed by signal 11 SIGSEGV Severity set to 'important' from 'serious' > tags -1 + unreproducible Bug #953983 [src:gcr] gcr: FTBFS (intermittently?) on am

Bug#953983: gcr: FTBFS (intermittently?) on amd64: gcr:gcr-base / system-prompt killed by signal 11 SIGSEGV

Control: severity -1 important Control: tags -1 + unreproducible On Sun, 15 Mar 2020 at 11:18:54 +, Simon McVittie wrote: > https://buildd.debian.org/status/fetch.php?pkg=gcr&arch=amd64&ver=3.36.0-1&stamp=1583940832&raw=0 > > 42/43 gcr:gcr-base / system-promptFAIL 0.52 s (kille

Bug#953793: marked as done (node-unicode-tr51: FTBFS with unicode-data 13.0.0)

Your message dated Sun, 15 Mar 2020 16:54:09 + with message-id and subject line Bug#953979: Removed package(s) from unstable has caused the Debian Bug report #953793, regarding node-unicode-tr51: FTBFS with unicode-data 13.0.0 to be marked as done. This means that you claim that the problem h

Bug#953981: marked as done (gcr: FTBFS (intermittently?): test_slot_info: assertion failed: (927623999 == token->utc_time))

Your message dated Sun, 15 Mar 2020 16:50:10 + with message-id and subject line Bug#953981: fixed in gcr 3.36.0-2 has caused the Debian Bug report #953981, regarding gcr: FTBFS (intermittently?): test_slot_info: assertion failed: (927623999 == token->utc_time) to be marked as done. This mean

Bug#953942: jack: should this package be removed?

On Sun, Mar 15, 2020 at 3:01 AM Michael Banck wrote: > > Hi, > > On Sat, Mar 14, 2020 at 03:33:34PM -0400, Sandro Tosi wrote: > > I believe this package should be removed: > > > > * python2-only > > * no upstream release since 2004 (!) or svn update since 2005 (!) > > * it's keeping several pytho

Bug#953999: iwyu: FTBFS on armel

package: src:iwyu version: 8.0-3 severity: serious tags: ftbfs Hi, The latest upload of iwyu to unstable fails on armel: https://buildd.debian.org/status/package.php?p=iwyu Cheers, Ivo

Bug#933749: marked as done (fail2ban: ever-growing fail2ban sqlite database)

Your message dated Sun, 15 Mar 2020 16:28:33 +0100 with message-id <5406e8f1-614c-680f-26b4-ebb6486c3...@debian.org> and subject line fixed - ever-growing fail2ban sqlite database has caused the Debian Bug report #933749, regarding fail2ban: ever-growing fail2ban sqlite database to be marked as don

Processed: fixed - ever-growing fail2ban sqlite database

Processing commands for cont...@bugs.debian.org: > fixed 933749 0.11.1-1 Bug #933749 [fail2ban] fail2ban: ever-growing fail2ban sqlite database Marked as fixed in versions fail2ban/0.11.1-1. > thanks Stopping processing here. Please contact me if you need assistance. -- 933749: https://bugs.debi

Bug#953703: fixed in klog 0.9.9.1-1

Hi, On Sat, Mar 14, 2020 at 07:49:45PM +, Debian FTP Masters wrote: > Subject: Bug#953703: fixed in klog 0.9.9.1-1 > Source: klog > Binary: klog klog-dbgsym > Architecture: source i386 > Version: 0.9.9.1-1 Thanks for fixing this bug. Please note that you did a binary upload. To migrate to t

Bug#953996: julia: FTBFS on ppc64el

package: src:julia version: 1.3.1+dfsg-1 severity: serious tags: ftbfs Hi, The latest upload of julia to unstable fails on ppc64el: https://buildd.debian.org/status/package.php?p=julia Note that it also fails on other architectures, but these don't have old binaries, so those are not blocking m

Bug#953981: marked as pending in gcr

Control: tag -1 pending Hello, Bug #953981 in gcr 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/gnome-team/gcr/-/commit/d15763b72cf254b4ad50b60bd454edf5083e65

Processed: Bug#953981 marked as pending in gcr

Processing control commands: > tag -1 pending Bug #953981 [src:gcr] gcr: FTBFS (intermittently?): test_slot_info: assertion failed: (927623999 == token->utc_time) Added tag(s) pending. -- 953981: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=953981 Debian Bug Tracking System Contact ow...@b

Bug#953562: Possibly causes unbootable state

On Mar 15, Timo Kluck wrote: > Thanks for the suggestion. I ended up doing something similar in > parallel (apologies for ubuntu-specific instructions): Then this is not interesting. -- ciao, Marco signature.asc Description: PGP signature

Bug#953562: Possibly causes unbootable state

>> I'll attempt to recover with a live cd and can post updates here if that's >> useful. > chroot and run ldconfig, for a start. Thanks for the suggestion. I ended up doing something similar in parallel (apologies for ubuntu-specific instructions): 1. boot into the live cd (I used ubuntu 18.04) 2.

Bug#953562: Possibly causes unbootable state

On Mar 15, Timo Kluck wrote: > I'll attempt to recover with a live cd and can post updates here if that's > useful. chroot and run ldconfig, for a start. -- ciao, Marco signature.asc Description: PGP signature

Bug#953990: rust-signal-hook needs a source-only upload.

Source: rust-signal-hook Version: 0.1.12-1 Severity: serious The release team have decreed that non-buildd binaries can no longer migrate to testing. Please make a source-only upload so your package can migrate.

Bug#947999: marked as done (prometheus-varnish-exporter FTBFS in testing/unstable)

Your message dated Sun, 15 Mar 2020 12:49:51 + with message-id and subject line Bug#946215: fixed in prometheus-varnish-exporter 1.5.2-1 has caused the Debian Bug report #946215, regarding prometheus-varnish-exporter FTBFS in testing/unstable to be marked as done. This means that you claim th

Bug#946215: marked as done (prometheus-varnish-exporter: FTBFS)

Your message dated Sun, 15 Mar 2020 12:49:51 + with message-id and subject line Bug#946215: fixed in prometheus-varnish-exporter 1.5.2-1 has caused the Debian Bug report #946215, regarding prometheus-varnish-exporter: FTBFS to be marked as done. This means that you claim that the problem has

Bug#953989: borgbackup reports installed python3-msgpack is incompatible

Package: borgbackup Version: 1.1.11-2 Severity: grave Justification: renders package unusable After updating python3-msgpack from 0.5.6-3 -> 0.6.2-1, attempting to run any borg command fails with the following message, making borg wholly unusable. $ borg -v You do not have a supported msgpack[-py

Bug#952312: marked as done (node-eslint-scope: FTBFS: tests failed)

Your message dated Sun, 15 Mar 2020 12:06:45 + with message-id and subject line Bug#952312: fixed in node-eslint-scope 4.0.3-5 has caused the Debian Bug report #952312, regarding node-eslint-scope: FTBFS: tests failed to be marked as done. This means that you claim that the problem has been d

Processed: bug 953981 is forwarded to https://gitlab.gnome.org/GNOME/gcr/issues/42 ...

Processing commands for cont...@bugs.debian.org: > forwarded 953981 https://gitlab.gnome.org/GNOME/gcr/issues/42 Bug #953981 [src:gcr] gcr: FTBFS (intermittently?): test_slot_info: assertion failed: (927623999 == token->utc_time) Set Bug forwarded-to-address to 'https://gitlab.gnome.org/GNOME/gcr

Bug#953562: Possibly causes unbootable state

I'd like to report that this is the possible cause of my system being unbootable at the moment. I run Ubuntu Focal on a Dell laptop and run regular `dist-upgrade`s. The latest one seems to have triggered the corner case described above. Booting fails to get to my desktop. Ubuntu's recovery mode g

Bug#953940: marked as done (breezy: FTBFS with Python 3.8)

Your message dated Sun, 15 Mar 2020 11:34:20 + with message-id and subject line Bug#953940: fixed in breezy 3.0.2-5 has caused the Debian Bug report #953940, regarding breezy: FTBFS with Python 3.8 to be marked as done. This means that you claim that the problem has been dealt with. If this i

Bug#953361: marked as done (gengetopt: FTBFS on i386: test failures)

Your message dated Sun, 15 Mar 2020 11:21:19 + with message-id and subject line Bug#953361: fixed in gengetopt 2.23+dfsg1-1 has caused the Debian Bug report #953361, regarding gengetopt: FTBFS on i386: test failures to be marked as done. This means that you claim that the problem has been dea

Bug#953983: gcr: FTBFS (intermittently?) on amd64: gcr:gcr-base / system-prompt killed by signal 11 SIGSEGV

Source: gcr Version: 3.36.0-1 Severity: serious Tags: ftbfs Justification: fails to build from source (but built successfully in the past) On the amd64 autobuilder: https://buildd.debian.org/status/fetch.php?pkg=gcr&arch=amd64&ver=3.36.0-1&stamp=1583940832&raw=0 > 42/43 gcr:gcr-base / system-prom

Bug#953981: gcr: FTBFS (intermittently?): test_slot_info: assertion failed: (927623999 == token->utc_time)

Source: gcr Version: 3.36.0-1 Severity: serious Tags: ftbfs Justification: fails to build from source (but built successfully in the past) https://buildd.debian.org/status/fetch.php?pkg=gcr&arch=armhf&ver=3.36.0-1&stamp=1583940931&raw=0 > 16/43 gcr:gck / slot FAIL 0.09

Bug#952344: marked as done (libjs-webrtc-adapter: FTBFS: Error: module sdp in /<>/dist not found)

Your message dated Sun, 15 Mar 2020 11:39:29 +0100 with message-id <158426876920.1679624.10221698976724590...@auryn.jones.dk> and subject line Re: [Pkg-javascript-devel] Bug#952344: libjs-webrtc-adapter: FTBFS: Error: module sdp in /<>/dist not found has caused the Debian Bug report #952344, regar

Bug#953549: marked as done (kopanocore: FTBFS with Python 3.8)

Your message dated Sun, 15 Mar 2020 10:50:53 + with message-id and subject line Bug#953549: fixed in kopanocore 8.7.0-7 has caused the Debian Bug report #953549, regarding kopanocore: FTBFS with Python 3.8 to be marked as done. This means that you claim that the problem has been dealt with. I

Bug#953880: Issue confirmed and possible workaround

Thanks Stefano, I have deleted the same file "pagecurl" and the Gimp works correctly. -- Cordialement, Bernardo. Si les noms sont incorrects, le langage ne sera pas en accord avec la vérité des choses. -+- Confucius -+-

debian-bugs-rc@lists.debian.org

Thx Praaven! Downgrading libsaas1 and dev to 3.6.1-1 solved problem 2. 2. Top-level selectors may not contain the parent selector "&" On 14.03.2020 19:41, Pirate Praveen wrote: On Sat, 14 Mar 2020 21:53:11 +0530 Pirate Praveen < prav...@onenetbeyond.org> wrote: I think this was introduced by

Bug#953851: pymissile: should this package be removed?

[Sandro Tosi] > if i dont hear back within a week with a good reason to keep this > package, i'll file for its removal. While these are all good arguments for removal, I still got the hardware and thus enjoy having the software to use it in Debian. :) But I realise that it need some porting to ke

Bug#952172: marked as done (django-oauth-toolkit: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p "3.8 3.7" --system=custom "--test-args=PYTHONPATH={build_dir} {interpre

Your message dated Sun, 15 Mar 2020 09:49:11 + with message-id and subject line Bug#952172: fixed in django-oauth-toolkit 1.3.0-1 has caused the Debian Bug report #952172, regarding django-oauth-toolkit: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p "3.8 3.7"

Bug#953832: cannot allocate memory in static TLS block

Hi Faidon, could you imagine to build jemalloc with --disable-initial-exec-tls as Sergio suggests below to fix the issue in drmaa (and possibly other packages)? Should I open a separate bug report against jemalloc to request this? Kind regards Andreas. On Sat, Mar 14, 2020 at 05:18:49PM

Bug#953549: kopanocore: FTBFS with Python 3.8

Hello Graham, Am 15.03.20 um 10:23 schrieb Graham Inggs: > On Sun, 15 Mar 2020 at 10:55, Carsten Schoenert > wrote: >> Look's like the check to find Python is now failing for Python 3.8. >> The relevant part in configure.ac (line 676 to 688) is this: > > I think you'll need at least this patch

Bug#953549: kopanocore: FTBFS with Python 3.8

On Sun, 15 Mar 2020 at 10:55, Carsten Schoenert wrote: > Look's like the check to find Python is now failing for Python 3.8. > The relevant part in configure.ac (line 676 to 688) is this: I think you'll need at least this patch from Ubuntu: https://launchpad.net/ubuntu/+source/kopanocore/8.7.0-5u

Bug#953549: kopanocore: FTBFS with Python 3.8

On Tue, Mar 10, 2020 at 03:27:59PM +0200, Graham Inggs wrote: > Hi Maintainer > > kopanocore FTBFS when rebuilt with Python 3.8 [1] > I hope the following is the relevant part of the log: > > checking for PYTHON... yes > configure: error: python requested but not satisfiable > cd debian/bui

Bug#953969: onioncircuits: autopkgtest failure with Python 3.8 as default

Hi Graham & pkg-privacy-team, Graham Inggs (2020-03-15): > The autopkgtests of onioncircuits started to fail with Python 3.8 as > the default Python3 interpreter [1]. > […] > File "/usr/lib/python3/dist-packages/stem/control.py", line 2170, in > get_conf > entries = self.get_conf_map(param

Processed: block 953969 with 953863

Processing commands for cont...@bugs.debian.org: > block 953969 with 953863 Bug #953969 [src:onioncircuits] onioncircuits: autopkgtest failure with Python 3.8 as default 953969 was not blocked by any bugs. 953969 was blocking: 949187 Added blocking bug(s) of 953969: 953863 > thanks Stopping proce

  1   2   >