Bug#958362: marked as done (pdfrw: fails with python 3.7+ -- abandoned upstream)

Your message dated Sat, 09 May 2020 06:49:05 + with message-id and subject line Bug#958362: fixed in img2pdf 0.3.6-1 has caused the Debian Bug report #958362, regarding pdfrw: fails with python 3.7+ -- abandoned upstream to be marked as done. This means that you claim that the problem has bee

Processed: affects 959064

Processing commands for cont...@bugs.debian.org: > affects 959064 src:ignition-transport Bug #959064 [cmake] cmake breaks on -isystem Bug #959960 [cmake] ignition-transport: FTBFS in sid Bug #960081 [cmake] src:ignition-transport: FTBFS with pkg-config 0.29.2-1 Added indication that 959064 affects

Bug#960079: Acknowledgement (undefined symbol: _PyNautilusInfoProvider_Type)

This was broken by debian/patches/gcc10.patch Bringing Andreas into the loop here. signature.asc Description: OpenPGP digital signature

Processed: Re: Bug#959940: hdmf FTBFS with h5py 2.10.0

Processing control commands: > reassign -1 python3-h5py 2.10.0-7 Bug #959940 [src:hdmf] hdmf FTBFS with h5py 2.10.0 Bug reassigned from package 'src:hdmf' to 'python3-h5py'. No longer marked as found in versions hdmf/1.5.4-1. Ignoring request to alter fixed versions of bug #959940 to the same valu

Bug#959940: hdmf FTBFS with h5py 2.10.0

Control: reassign -1 python3-h5py 2.10.0-7 Control: affects -1 src:hdmf Control: tags -1 - upstream Control: block 956420 by -1 On Thu, May 07, 2020 at 01:17:05PM +0200, Andreas Tille wrote: > Control: forwarded -1 https://github.com/hdmf-dev/hdmf/issues/343 Reassigning to h5py based on the upstr

Processed: reassign 960081 to cmake, forcibly merging 959064 960081

Processing commands for cont...@bugs.debian.org: > reassign 960081 cmake Bug #960081 [src:ignition-transport] src:ignition-transport: FTBFS with pkg-config 0.29.2-1 Bug reassigned from package 'src:ignition-transport' to 'cmake'. No longer marked as found in versions ignition-transport/8.0.0+dfsg

Processed: fixed 952629 in 10.19.0~dfsg-2

Processing commands for cont...@bugs.debian.org: > fixed 952629 10.19.0~dfsg-2 Bug #952629 {Done: =?utf-8?b?SsOpcsOpbXkgTGFs?= } [src:nodejs] nodejs: FTBFS: make[2]: *** No rule to make target '../deps/acorn/dist/walk.js', needed by '/<>/out/Release/obj/gen/node_javascript.cc'. Stop. Marked as

Bug#960082: nautilus extension fails to load: libeiciel-nautilus.so: undefined symbol: nautilus_module_initialize

Package: eiciel Version: 0.9.12.1-2 Severity: serious The nautilus extension provided by eiciel no longer works with nautilus 3.36. Starting nautilus from the command line: ** (org.gnome.Nautilus:7715): WARNING **: 08:07:07.542: 'nautilus_module_initialize': /usr/lib/x86_64-linux-gnu/nautilus/e

Bug#959942: marked as done (src:caffe: missing (unversioned) Breaks+Replaces: libcaffe-cpu1/libcaffe-cpu-dev/caffe-tools-cpu/python3-caffe-cpu)

Your message dated Sat, 09 May 2020 06:03:30 + with message-id and subject line Bug#959942: fixed in caffe 1.0.0+git20180821.99bd997-7 has caused the Debian Bug report #959942, regarding src:caffe: missing (unversioned) Breaks+Replaces: libcaffe-cpu1/libcaffe-cpu-dev/caffe-tools-cpu/python3-c

Bug#960079: undefined symbol: _PyNautilusInfoProvider_Type

Package: python3-nautilus Version: 1.2.3-2 Severity: serious File: /usr/lib/x86_64-linux-gnu/nautilus/extensions-3.0/libnautilus-python.so Hi, today I was investigating, why nautilus-nextcloud is no longer working for me. nautilus-nextcloud is using python3-nautilus and starting nautilus from the

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

Processing control commands: > close -1 3.1.9 Bug #960078 [src:xfsdump] src:xfsdump: fails to migrate to testing for too long Marked as fixed in versions xfsdump/3.1.9. Bug #960078 [src:xfsdump] src:xfsdump: fails to migrate to testing for too long Marked Bug as done > block -1 by 953537 Bug #9600

Bug#960078: src:xfsdump: fails to migrate to testing for too long

Source: xfsdump Version: 3.1.6+nmu2 Severity: serious Control: close -1 3.1.9 Tags: sid bullseye User: release.debian@packages.debian.org Usertags: out-of-sync Control: block -1 by 953537 Dear maintainer(s), As recently announced [1], the Release Team now considers packages that are out-of-sy

Bug#960077: src:gpgme1.0: fails to migrate to testing for too long

Source: gpgme1.0 Version: 1.13.1-6 Severity: serious Control: close -1 1.13.1-7 Tags: sid bullseye User: release.debian@packages.debian.org Usertags: out-of-sync Control: block -1 by 953800 Dear maintainer(s), As recently announced [1], the Release Team now considers packages that are out-of-

Processed: src:gpgme1.0: fails to migrate to testing for too long

Processing control commands: > close -1 1.13.1-7 Bug #960077 [src:gpgme1.0] src:gpgme1.0: fails to migrate to testing for too long Marked as fixed in versions gpgme1.0/1.13.1-7. Bug #960077 [src:gpgme1.0] src:gpgme1.0: fails to migrate to testing for too long Marked Bug as done > block -1 by 953

Bug#947720: sollya ftbfs with libfplll6

Hi, On 09-05-2020 00:17, Sudip Mukherjee wrote: > Hi Paul, > > On Fri, May 8, 2020 at 9:36 PM Paul Gevers wrote: >> >> Hi Sudip, >> >> On 08-05-2020 01:08, Sudip Mukherjee wrote: >>> Can you please retest and confirm. >> >> I have given it back on arm64. Please ping me if that build succeeds. >>

Bug#960073: Package:python-pyqt5 Run the example code with Trace and crash (SIGABRT)

Package:python-pyqt5 Version: 5.11.3+dfsg-1+b3_arm64 Severity: serious Hi Experts, Hope this email finds you well. I am Peng Zongli, I'm sorry to bother you. When ever I run the example code on the arm machine,It results in the error below: / Could not initialize GLX/ /Aborted (core dumped

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

Your message dated Sat, 09 May 2020 02:34:04 + with message-id and subject line Bug#952167: fixed in astroidmail 0.15-3.1 has caused the Debian Bug report #952167, regarding astroidmail: FTBFS: dh_auto_test: error: cd obj-x86_64-linux-gnu && make -j1 test ARGS\+=-j1 returned exit code 2 to be

Bug#938108: python-pyxenstore: Python2 removal in sid/bullseye

On 5/8/20 9:35 PM, Moritz Mühlenhoff wrote: > On Fri, Aug 30, 2019 at 07:45:40AM +, Matthias Klose wrote: >> Package: src:python-pyxenstore >> Version: 0.0.2-1 >> Severity: normal >> Tags: sid bullseye >> User: debian-pyt...@lists.debian.org >> Usertags: py2removal >> >> Python2 becomes end-of-

Processed: found 938261 in 1.0.0+dfsg1-1, found 953615 in 1.0.9-1

Processing commands for cont...@bugs.debian.org: > found 938261 1.0.0+dfsg1-1 Bug #938261 {Done: Sandro Tosi } [src:python-werkzeug] python-werkzeug: Python2 removal in sid/bullseye Marked as found in versions python-werkzeug/1.0.0+dfsg1-1 and reopened. > found 953615 1.0.9-1 Bug #953615 [borgbac

Bug#959900: marked as done (keystone: CVE-2020-12689 CVE-2020-12690 CVE-2020-12691 CVE-2020-12692)

Your message dated Fri, 08 May 2020 23:03:46 + with message-id and subject line Bug#959900: fixed in keystone 2:17.0.0~rc2-1 has caused the Debian Bug report #959900, regarding keystone: CVE-2020-12689 CVE-2020-12690 CVE-2020-12691 CVE-2020-12692 to be marked as done. This means that you clai

Processed: Bug#959900 marked as pending in keystone

Processing control commands: > tag -1 pending Bug #959900 [src:keystone] keystone: CVE-2020-12689 CVE-2020-12690 CVE-2020-12691 CVE-2020-12692 Ignoring request to alter tags of bug #959900 to the same tags previously set -- 959900: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=959900 Debian

Bug#959900: marked as pending in keystone

Control: tag -1 pending Hello, Bug #959900 in keystone reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/openstack-team/services/keystone/-/commit/d25246ef22950fd

Processed: tagging 945625, bug 945625 is forwarded to st...@electron9.net

Processing commands for cont...@bugs.debian.org: > tags 945625 + upstream Bug #945625 [src:cicero] cicero: Python2 removal in sid/bullseye Added tag(s) upstream. > forwarded 945625 st...@electron9.net Bug #945625 [src:cicero] cicero: Python2 removal in sid/bullseye Set Bug forwarded-to-address to

Bug#947720: sollya ftbfs with libfplll6

Hi Paul, On Fri, May 8, 2020 at 9:36 PM Paul Gevers wrote: > > Hi Sudip, > > On 08-05-2020 01:08, Sudip Mukherjee wrote: > > Can you please retest and confirm. > > I have given it back on arm64. Please ping me if that build succeeds. > > https://buildd.debian.org/status/package.php?p=sollya Than

Bug#945705: selenium-firefoxdriver: Python2 removal in sid/bullseye

On Fri, 29 Nov 2019, Sascha Girrulat wrote: Source: selenium-firefoxdriver Version: 3.14.1-1 Severity: normal Tags: sid bullseye Hi, the firefoxdriver supports only firefox version up to 52.0 and does not work with the current version of firefox anymore. That's why the removal is fine. I'

Bug#959955: Packaging libsis-jhdf5-java -- help needed

Hi Pierre, On Fri, May 08, 2020 at 10:24:47PM +0200, Pierre Gruet wrote: > > Absolutely. This is part of the complementary tasks I was planning to do > (my Salsa push of yesterday was only to fix the RC bug). h5ar was not in > the previous packaging of libsis-jhdf5-java. If you think you might b

Bug#947720: sollya ftbfs with libfplll6

Hi Sudip, On 08-05-2020 01:08, Sudip Mukherjee wrote: > Can you please retest and confirm. I have given it back on arm64. Please ping me if that build succeeds. https://buildd.debian.org/status/package.php?p=sollya Paul signature.asc Description: OpenPGP digital signature

Bug#960057: src:upx-ucl: fails to migrate to testing for too long: autopkgtest failure

Source: upx-ucl Version: 3.95-2 Severity: serious Control: close -1 3.96-1 Tags: sid bullseye 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 between testing and unstable

Processed: src:upx-ucl: fails to migrate to testing for too long: autopkgtest failure

Processing control commands: > close -1 3.96-1 Bug #960057 [src:upx-ucl] src:upx-ucl: fails to migrate to testing for too long: autopkgtest failure Marked as fixed in versions upx-ucl/3.96-1. Bug #960057 [src:upx-ucl] src:upx-ucl: fails to migrate to testing for too long: autopkgtest failure Mar

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

Processing control commands: > close -1 3.59 Bug #960056 [src:tasksel] src:tasksel: fails to migrate to testing for too long Marked as fixed in versions tasksel/3.59. Bug #960056 [src:tasksel] src:tasksel: fails to migrate to testing for too long Marked Bug as done -- 960056: https://bugs.debian

Bug#960056: src:tasksel: fails to migrate to testing for too long

Source: tasksel Version: 3.58 Severity: serious Control: close -1 3.59 Tags: sid bullseye User: release.debian@packages.debian.org Usertags: out-of-sync Dear maintainer(s), kibi, As recently announced [1], the Release Team now considers packages that are out-of-sync between testing and unstab

Processed: src:reactphp-socket: fails to migrate to testing for too long: arch:all uploaded

Processing control commands: > close -1 1.3.0-1 Bug #960054 [src:reactphp-socket] src:reactphp-socket: fails to migrate to testing for too long: arch:all uploaded Marked as fixed in versions reactphp-socket/1.3.0-1. Bug #960054 [src:reactphp-socket] src:reactphp-socket: fails to migrate to testi

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

Processing control commands: > close -1 0.2+bzr42+repack1-9 Bug #960053 [src:libqtdbustest] src:libqtdbustest: fails to migrate to testing for too long Marked as fixed in versions libqtdbustest/0.2+bzr42+repack1-9. Bug #960053 [src:libqtdbustest] src:libqtdbustest: fails to migrate to testing fo

Bug#960053: src:libqtdbustest: fails to migrate to testing for too long

Source: libqtdbustest Version: 0.2+bzr42+repack1-5 Severity: serious Control: close -1 0.2+bzr42+repack1-9 Tags: sid bullseye 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-s

Bug#960054: src:reactphp-socket: fails to migrate to testing for too long: arch:all uploaded

Source: reactphp-socket Version: 1.1.0-1 Severity: serious Control: close -1 1.3.0-1 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 between te

Bug#889748: marked as done (diagnostics FTBFS: FAIL: stacktrace)

Your message dated Fri, 8 May 2020 22:35:26 +0300 with message-id <20200508193526.GA8672@localhost> and subject line Re: diagnostics FTBFS: FAIL: stacktrace has caused the Debian Bug report #889748, regarding diagnostics FTBFS: FAIL: stacktrace to be marked as done. This means that you claim that

Bug#938108: python-pyxenstore: Python2 removal in sid/bullseye

On Fri, Aug 30, 2019 at 07:45:40AM +, Matthias Klose wrote: > Package: src:python-pyxenstore > Version: 0.0.2-1 > Severity: normal > Tags: sid bullseye > User: debian-pyt...@lists.debian.org > Usertags: py2removal > > Python2 becomes end-of-live upstream, and Debian aims to remove > Python2 fr

Bug#936206: binplist: Python2 removal in sid/bullseye

On Fri, Aug 30, 2019 at 07:11:38AM +, Matthias Klose wrote: > Package: src:binplist > Version: 0.1.5-2 > Severity: normal > Tags: sid bullseye > User: debian-pyt...@lists.debian.org > Usertags: py2removal > > Python2 becomes end-of-live upstream, and Debian aims to remove > Python2 from the di

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

Your message dated Fri, 08 May 2020 19:04:59 + with message-id and subject line Bug#938092: fixed in python-pysam 0.15.4+ds-3 has caused the Debian Bug report #938092, regarding python-pysam: Python2 removal in sid/bullseye to be marked as done. This means that you claim that the problem has

Bug#954645: marked as done (behave: FTBFS: dh_auto_test: error: pybuild --test --test-nose -i python{version} -p "3.7 3.8" returned exit code 13)

Your message dated Fri, 08 May 2020 19:03:41 + with message-id and subject line Bug#954645: fixed in behave 1.2.6-2 has caused the Debian Bug report #954645, regarding behave: FTBFS: dh_auto_test: error: pybuild --test --test-nose -i python{version} -p "3.7 3.8" returned exit code 13 to be ma

Bug#954645: marked as pending in behave

Control: tag -1 pending Hello, Bug #954645 in behave 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/behave/-/commit/674c8ea1328bfc84754d85f

Processed: Bug#954645 marked as pending in behave

Processing control commands: > tag -1 pending Bug #954645 [src:behave] behave: FTBFS: dh_auto_test: error: pybuild --test --test-nose -i python{version} -p "3.7 3.8" returned exit code 13 Added tag(s) pending. -- 954645: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=954645 Debian Bug Tracki

Processed: Bug#954645 marked as pending in behave

Processing control commands: > tag -1 pending Bug #954645 [src:behave] behave: FTBFS: dh_auto_test: error: pybuild --test --test-nose -i python{version} -p "3.7 3.8" returned exit code 13 Ignoring request to alter tags of bug #954645 to the same tags previously set -- 954645: https://bugs.debia

Bug#954645: marked as pending in behave

Control: tag -1 pending Hello, Bug #954645 in behave 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/behave/-/commit/15bb8b78186e713871d6cc8

Bug#955403: Set severity to important (Was: bedtools ftbfs, failing tests on armel, armhf, i386, mipsel)

Control: severity -1 important The builds for the failed architectures are requested for removal. So the bug is set to severity important to move on with architectures that are used in practical applications without creating noise in form of lots of testing removal warnings of rdepends. Kind reg

Processed: Set severity to important (Was: bedtools ftbfs, failing tests on armel, armhf, i386, mipsel)

Processing control commands: > severity -1 important Bug #955403 [src:bedtools] bedtools ftbfs, failing tests on armel, armhf, i386, mipsel Severity set to 'important' from 'serious' -- 955403: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=955403 Debian Bug Tracking System Contact ow...@bug

Processed: severity of 959885 is serious, tagging 959885

Processing commands for cont...@bugs.debian.org: > severity 959885 serious Bug #959885 [inkscape] inkscape: crashes when called without X server Severity set to 'serious' from 'important' > tags 959885 + upstream Bug #959885 [inkscape] inkscape: crashes when called without X server Added tag(s) up

Bug#959994: codeville: Consider removing this package

Hello. I agree with this assessment. If you can submit it immediately, that would be fine with me. Marie Janssen --- Jamuraa --- jamu...@base0.net --- jamu...@debian.org On Thu, May 7, 2020 at 8:48 PM Boyuan Yang wrote: > Source: codeville > Severity: serious > Version: 0.8.0-2.1 > Tags: sid

Processed: severity of 954999 is important

Processing commands for cont...@bugs.debian.org: > severity 954999 important Bug #954999 [eclipse-titan] eclipse-titan still encodes an upper dependency on gcc Severity set to 'important' from 'serious' > thanks Stopping processing here. Please contact me if you need assistance. -- 954999: http

Bug#959390: marked as done (adwaita-icon-theme breaks gtk+3.0 autopkgtest: gtk+/icontheme.test (Child process killed by signal 5))

Your message dated Fri, 08 May 2020 16:03:46 + with message-id and subject line Bug#959390: fixed in gtk+3.0 3.24.20-1 has caused the Debian Bug report #959390, regarding adwaita-icon-theme breaks gtk+3.0 autopkgtest: gtk+/icontheme.test (Child process killed by signal 5) to be marked as done

Bug#960041: python-tornado4: Pending removal

Source: python-tornado4 Severity: serious Justification: Policy 7.2 This package is an old fork of the tornado binary package, which appears to have been created for src:salt. There are no longer any rdepends (salt ceased to depend upon it after 3000+dfsg1-1), so unless there are objections this

Bug#955319: marked as done (libtoxcore: autopkgtest regression: Test #2: bootstrap ........................***Timeout 120.00 sec)

Your message dated Fri, 8 May 2020 23:39:14 +0800 with message-id and subject line has caused the Debian Bug report #955319, regarding libtoxcore: autopkgtest regression: Test #2: bootstrap ***Timeout 120.00 sec to be marked as done. This means that you claim that the p

Processed: Bug#959390 marked as pending in gtk+3.0

Processing control commands: > tag -1 pending Bug #959390 [src:adwaita-icon-theme, src:gtk+3.0] adwaita-icon-theme breaks gtk+3.0 autopkgtest: gtk+/icontheme.test (Child process killed by signal 5) Ignoring request to alter tags of bug #959390 to the same tags previously set -- 959390: https://

Bug#959390: marked as pending in gtk+3.0

Control: tag -1 pending Hello, Bug #959390 in gtk+3.0 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/gtk3/-/commit/cc3d2e7851cea7dbeb7d92a6cd8402415

Bug#944020: Help with this for TAILS

Hello- I'm doing some work with the Tails team working to get Trezor python-trezor and python-libusb1 back-ported to Buster. These packages can then be put into testing for Tails to use. Currently this all hinges on getting debian bug 944020

Bug#959981: Trademark concerns with Chef/Cinc package included in Debian and Ubuntu

Hello, This is my attemp at a more detailed response after sleeping on it. On Thu, May 07, 2020 at 11:40:38AM -0700, Lance Albertson wrote: > All, > > I'm a member of the Cinc Project [1] which rebuilds and rebrands various > Chef projects to comply with Chef Trademark Policy [2]. We have worked

Bug#951969: marked as done (social-auth-app-django: FTBFS: dh_auto_test: error: pybuild --test -i python{version} -p "3.8 3.7" --system=custom "--test-args={interpreter} ./manage.py test" returned exi

Your message dated Fri, 08 May 2020 14:36:42 + with message-id and subject line Bug#951969: fixed in social-auth-app-django 3.1.0-2.1 has caused the Debian Bug report #951969, regarding social-auth-app-django: FTBFS: dh_auto_test: error: pybuild --test -i python{version} -p "3.8 3.7" --system

Bug#959402: marked as done (yaml-cpp: FTBFS on mipsel)

Your message dated Fri, 08 May 2020 14:36:48 + with message-id and subject line Bug#959402: fixed in yaml-cpp 0.6.3-2 has caused the Debian Bug report #959402, regarding yaml-cpp: FTBFS on mipsel to be marked as done. This means that you claim that the problem has been dealt with. If this is

Bug#960038: haskell-bz2: Failed to migrate to testing for too long

Source: haskell-bz2 Version: 0.1.1.1-1 Severity: serious Tags: sid bullseye User: release.debian@packages.debian.org Usertags: out-of-sync X-Debbugs-CC: cl...@debian.org Dear maintainer(s), As recently announced [1], the Release Team now considers packages that are out-of-sync between testing

Bug#951620: marked as done (clips: fails to migrate to testing for too long)

Your message dated Fri, 08 May 2020 10:30:17 -0400 with message-id and subject line Re: clips: fails to migrate to testing for too long has caused the Debian Bug report #951620, regarding clips: fails to migrate to testing for too long to be marked as done. This means that you claim that the prob

Bug#944020: Help?

Hello- I'm doing some work with the Tails team working to get Trezor python-trezor and python-libusb1 back-ported to Buster. These packages can then be put into testing for Tails to use. Currently this all hinges on getting debian bug 944020

Bug#919348: xfce4-screensaver is now supprted in xfce4-session

xfce4-screensaver is now supported in xfce4-session https://gitlab.xfce.org/xfce/xfce4-session/-/blob/xfce-4.14/NEWS

Bug#949461: repo is an empty package in unstable/testing, failing it's autopkg tests

Dear Marcos, Thanks for your email and contribution! > An update to this package, based on salsa's repository, is available in > https://github.com/marado/repo . It bumps repo's version to the latest, > as well as fixes the empty package issue. However we usually don't update so much stuff in on

Bug#949461: marked as done (repo is an empty package in unstable/testing, failing it's autopkg tests)

Your message dated Fri, 08 May 2020 13:49:46 + with message-id and subject line Bug#949461: fixed in repo 1.13.7-2 has caused the Debian Bug report #949461, regarding repo is an empty package in unstable/testing, failing it's autopkg tests to be marked as done. This means that you claim that

Bug#959546: marked as done (rabbitmq-server: FTBFS: build-dependency not installable: elixir (>= 1.6.6))

Your message dated Fri, 08 May 2020 13:33:47 + with message-id and subject line Bug#959701: fixed in elixir-lang 1.10.3.dfsg-1 has caused the Debian Bug report #959701, regarding rabbitmq-server: FTBFS: build-dependency not installable: elixir (>= 1.6.6) to be marked as done. This means that

Bug#959458: marked as done (matchbox-panel: Build-Depends on obsolete package linux-kernel-headers)

Your message dated Fri, 08 May 2020 13:34:12 + with message-id and subject line Bug#959458: fixed in matchbox-panel 0.9.3-11 has caused the Debian Bug report #959458, regarding matchbox-panel: Build-Depends on obsolete package linux-kernel-headers to be marked as done. This means that you cla

Bug#959701: marked as done (elixir-lang: incompatible with erlang 22)

Your message dated Fri, 08 May 2020 13:33:47 + with message-id and subject line Bug#959701: fixed in elixir-lang 1.10.3.dfsg-1 has caused the Debian Bug report #959701, regarding elixir-lang: incompatible with erlang 22 to be marked as done. This means that you claim that the problem has been

Processed: retitle 959900 to keystone: CVE-2020-12689 CVE-2020-12690 CVE-2020-12691 CVE-2020-12692

Processing commands for cont...@bugs.debian.org: > retitle 959900 keystone: CVE-2020-12689 CVE-2020-12690 CVE-2020-12691 > CVE-2020-12692 Bug #959900 [src:keystone] CVE pending / OSSA-2020-004: EC2 and credential endpoints are not protected from a scoped context Changed Bug title to 'keystone: C

Processed: tagging 960011, bug 960011 is forwarded to https://github.com/leto/math--gsl/issues/167

Processing commands for cont...@bugs.debian.org: > tags 960011 + upstream Bug #960011 [src:libmath-gsl-perl] libmath-gsl-perl: FBTFS (unsupported version: 2.6 at Build.PL line 80) Bug #960014 [src:libmath-gsl-perl] libmath-gsl-perl: FTBFS with gsl 2.6 Ignoring request to alter tags of bug #960011

Processed: found 959900 in 2:16.0.0-6

Processing commands for cont...@bugs.debian.org: > found 959900 2:16.0.0-6 Bug #959900 [src:keystone] keystone: CVE-2020-12689 CVE-2020-12690 CVE-2020-12691 CVE-2020-12692 Marked as found in versions keystone/2:16.0.0-6. > thanks Stopping processing here. Please contact me if you need assistance

Processed: bug 960011 is forwarded to https://github.com/leto/math--gsl/issues/173, tagging 960011

Processing commands for cont...@bugs.debian.org: > forwarded 960011 https://github.com/leto/math--gsl/issues/173 Bug #960011 [src:libmath-gsl-perl] libmath-gsl-perl: FBTFS (unsupported version: 2.6 at Build.PL line 80) Bug #960014 [src:libmath-gsl-perl] libmath-gsl-perl: FTBFS with gsl 2.6 Set Bu

Bug#945481: Bump minimum version of ruby-molinillo dependency in ruby-bundler

Followup-For: Bug #945481 Control: tag -1 pending Control: block -1 with 960020 Hi, I've backported the fix to buster, uploaded to DELAYED/10 and filed a buster-pu request (#960020) (the debdiff can be found there, too). Andreas

Processed: Re: Bump minimum version of ruby-molinillo dependency in ruby-bundler

Processing control commands: > tag -1 pending Bug #945481 {Done: Debian FTP Masters } [bundler] Bump minimum version of ruby-molinillo dependency in ruby-bundler Added tag(s) pending. > block -1 with 960020 Bug #945481 {Done: Debian FTP Masters } [bundler] Bump minimum version of ruby-molinillo

Processed: Re: scap-security-guide: Python2 removal in sid/bullseye

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

Bug#958577: Uploaded fix to delay/2

Thank you. Feel free to upload directly to unstable. Saludos, Felipe Sateler On Fri, May 8, 2020, 04:57 Thomas Goirand wrote: > Hi, > > Since nobody seem to care, I uploaded the fix to delay/2: > > --- a/debian/control > +++ b/debian/control > @@ -19,7 +19,7 @@ > > Package: python3-docker > A

Bug#959201: marked as done (jami-daemon: dring does not start due to a symbol lookup error)

Your message dated Fri, 08 May 2020 11:33:30 + with message-id and subject line Bug#959201: fixed in yaml-cpp 0.6.3-1.1 has caused the Debian Bug report #959201, regarding jami-daemon: dring does not start due to a symbol lookup error to be marked as done. This means that you claim that the p

Bug#959586: marked as done (openimageio: FTBFS: ld: /usr/lib/libOpenColorIO.so.1: undefined reference to `YAML::detail::node_data::empty_scalar[abi:cxx11]')

Your message dated Fri, 08 May 2020 11:33:30 + with message-id and subject line Bug#959201: fixed in yaml-cpp 0.6.3-1.1 has caused the Debian Bug report #959201, regarding openimageio: FTBFS: ld: /usr/lib/libOpenColorIO.so.1: undefined reference to `YAML::detail::node_data::empty_scalar[abi:c

Bug#959556: marked as done (olive-editor: FTBFS: ld: /usr/lib/libOpenColorIO.so: undefined reference to `YAML::detail::node_data::empty_scalar[abi:cxx11]')

Your message dated Fri, 08 May 2020 11:33:30 + with message-id and subject line Bug#959201: fixed in yaml-cpp 0.6.3-1.1 has caused the Debian Bug report #959201, regarding olive-editor: FTBFS: ld: /usr/lib/libOpenColorIO.so: undefined reference to `YAML::detail::node_data::empty_scalar[abi:cx

Bug#959657: marked as done (olive-editor: Does not start: symbol lookup error)

Your message dated Fri, 08 May 2020 11:33:30 + with message-id and subject line Bug#959201: fixed in yaml-cpp 0.6.3-1.1 has caused the Debian Bug report #959201, regarding olive-editor: Does not start: symbol lookup error to be marked as done. This means that you claim that the problem has be

Bug#958034: marked as done (python-zeroconf: FTBFS: tests fail without networking)

Your message dated Fri, 08 May 2020 11:18:38 + with message-id and subject line Bug#958034: fixed in python-zeroconf 0.25.0-2 has caused the Debian Bug report #958034, regarding python-zeroconf: FTBFS: tests fail without networking to be marked as done. This means that you claim that the prob

Processed: Bug#958034 marked as pending in python-zeroconf

Processing control commands: > tag -1 pending Bug #958034 [src:python-zeroconf] python-zeroconf: FTBFS: tests fail without networking Added tag(s) pending. -- 958034: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=958034 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#958034: marked as pending in python-zeroconf

Control: tag -1 pending Hello, Bug #958034 in python-zeroconf 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/python-zeroconf/-/commit/d9419

Processed: forcibly merging 960010 960013

Processing commands for cont...@bugs.debian.org: > forcemerge 960010 960013 Bug #960010 [src:freefem++] freefem++: FBTFS (error: multiple definition of ‘enum CBLAS_SIDE’) Bug #960010 [src:freefem++] freefem++: FBTFS (error: multiple definition of ‘enum CBLAS_SIDE’) Added tag(s) bullseye, ftbfs,

Processed: forcibly merging 960011 960014

Processing commands for cont...@bugs.debian.org: > forcemerge 960011 960014 Bug #960011 [src:libmath-gsl-perl] libmath-gsl-perl: FBTFS (unsupported version: 2.6 at Build.PL line 80) Bug #960011 [src:libmath-gsl-perl] libmath-gsl-perl: FBTFS (unsupported version: 2.6 at Build.PL line 80) Added ta

Bug#959973: marked as done (pgcli: does not work due to prompt_toolkit incompatibility)

Your message dated Fri, 08 May 2020 10:18:58 + with message-id and subject line Bug#959973: fixed in pgcli 3.0.0-1 has caused the Debian Bug report #959973, regarding pgcli: does not work due to prompt_toolkit incompatibility to be marked as done. This means that you claim that the problem ha

Processed (with 1 error): reassign 952481 to texlive-lang, fixed 952481 in 2019.20200302-1, reassign 950146 to src:enchant-2 ...

Processing commands for cont...@bugs.debian.org: > reassign 952481 texlive-lang 2019.20200218-1 Bug #952481 {Done: Norbert Preining } [texlive-base] texlive: mktexpk fails to create tcrm1000 Bug reassigned from package 'texlive-base' to 'texlive-lang'. No longer marked as found in versions texliv

Bug#960014: libmath-gsl-perl: FTBFS with gsl 2.6

Source: libmath-gsl-perl Version: 0.40-1 Severity: serious Tags: ftbfs bullseye sid Hi Maintainer In a recent rebuild for the gsl 2.6 transition, libmath-gsl-perl FTBFS on all architectures [1]. I've copied what I hope is the relevant part of the log below. Regards Graham [1] https://buildd.de

Bug#960013: freefem++: FTBFS with gsl 2.6

Source: freefem++ Version: 3.61.1+dfsg1-5 Severity: serious Tags: ftbfs bullseye sid Hi Maintainer In a recent rebuild for the gsl 2.6 transition, freefem++ FTBFS on all architectures. I 've copied what I hope is the relevant part of the log below. Regards Graham [1] https://buildd.debian.org/

Bug#960011: libmath-gsl-perl: FBTFS (unsupported version: 2.6 at Build.PL line 80)

Source: libmath-gsl-perl Version: 0.40-1 Severity: serious Justification: makes the package in question unusable or mostly so Control: block 959133 by -1 Dear Maintainer, Your package FTBFS during the gsl transition: dh build-arch dh_update_autotools_config -a dh_autoreconf -a dh_au

Processed: libmath-gsl-perl: FBTFS (unsupported version: 2.6 at Build.PL line 80)

Processing control commands: > block 959133 by -1 Bug #959133 [release.debian.org] release.debian.org: Transition for gsl 959133 was blocked by: 960010 959133 was not blocking any bugs. Added blocking bug(s) of 959133: 960011 -- 959133: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=959133 96

Processed: freefem++: FBTFS (error: multiple definition of ‘enum CBLAS_SIDE’)

Processing control commands: > block 959133 by -1 Bug #959133 [release.debian.org] release.debian.org: Transition for gsl 959133 was not blocked by any bugs. 959133 was not blocking any bugs. Added blocking bug(s) of 959133: 960010 -- 959133: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=959

Bug#960010: freefem++: FBTFS (error: multiple definition of ‘enum CBLAS_SIDE’)

Source: freefem++ Version: 3.61.1+dfsg1-5 Severity: serious Justification: makes the package in question unusable or mostly so Control: block 959133 by -1 Dear Maintainer, Your package FTBFS during the gsl transition. The builog shows many errors like this: In file included from /usr/include/g

Bug#932779: lirc: Fails to install due to missing /etc/lirc/lirc_options.conf

The package has been broken by the 5.1 and 5.2 SRUs, Ccing Nicolas and Tobias who did those changes. * The package before -5.1 were handling those conffiles by doing debian/rules     # Don't overwrite existing config files.     for f in lircd.conf lircmd.conf irexec.lircrc lirc_options.conf; do

Bug#937769: uploaded ripe-atlas, beaker

I've [team-]uploaded beaker and ripe-atlas-cousteau, and filed bugs against kombu and pagure (on the basis that they are both have recent activity). They've been added as blockers to this bug. Apart from python-oslo.* changes already in experimental, I think that means all the reverse[-build]-depe

Bug#939826: marked as done (bustle: ftbfs with new cabal)

Your message dated Fri, 08 May 2020 09:03:55 + with message-id and subject line Bug#939826: fixed in bustle 0.7.5-2 has caused the Debian Bug report #939826, regarding bustle: ftbfs with new cabal to be marked as done. This means that you claim that the problem has been dealt with. If this is

Bug#958577: Uploaded fix to delay/2

Hi, Since nobody seem to care, I uploaded the fix to delay/2: --- a/debian/control +++ b/debian/control @@ -19,7 +19,7 @@ Package: python3-docker Architecture: all -Depends: ${misc:Depends}, ${python3:Depends} +Depends: python3-distutils, ${misc:Depends}, ${python3:Depends} Description: Pytho

Bug#956276: marked as done (runescape: downloads unverified binary and runs it)

Your message dated Fri, 08 May 2020 08:39:54 + with message-id and subject line Bug#956276: fixed in runescape 0.8-1 has caused the Debian Bug report #956276, regarding runescape: downloads unverified binary and runs it to be marked as done. This means that you claim that the problem has been

Bug#956275: marked as done (runescape: license issue - runscape.png probably undistributable)

Your message dated Fri, 08 May 2020 08:39:54 + with message-id and subject line Bug#956275: fixed in runescape 0.8-1 has caused the Debian Bug report #956275, regarding runescape: license issue - runscape.png probably undistributable to be marked as done. This means that you claim that the pr

Processed: tagging 959801, notfound 959889 in 0.5.0, found 959889 in 0.5.0-1, found 912504 in 3.1-3.3 ...

Processing commands for cont...@bugs.debian.org: > tags 959801 + sid Bug #959801 {Done: Debian FTP Masters } [src:ropemode] ropemode: Consider removing it from Debian Added tag(s) sid. > notfound 959889 0.5.0 Bug #959889 {Done: Sandro Tosi } [sphinx-gallery] python3-sphinx-gallery: AttributeErro

Processed: affects 904742, tagging 872215, tagging 872113, tagging 872208

Processing commands for cont...@bugs.debian.org: > affects 904742 + sat-xmpp-jp Bug #904742 [jp] jp: name conflict of /usr/bin/jp with sat-xmpp-jp Bug #954443 [jp] jp: name conflict of /usr/bin/jp with sat-xmpp-jp Added indication that 904742 affects sat-xmpp-jp Added indication that 954443 affect

  1   2   >