Processed: tagging 957557

2020-11-08 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > tags 957557 + ftbfs Bug #957557 [src:mod-gearman] mod-gearman: ftbfs with GCC-10 Added tag(s) ftbfs. > thanks Stopping processing here. Please contact me if you need assistance. -- 957557:

Bug#974021: kvirc FTBFS: error: aggregate ‘QPainterPath sP’ has incomplete type and cannot be defined

2020-11-08 Thread Adrian Bunk
Source: kvirc Version: 4:5.0.0+dfsg-3 Severity: serious Tags: ftbfs https://buildd.debian.org/status/package.php?p=kvirc=sid ... /<>/src/modules/iograph/libkviiograph.cpp: In member function ‘virtual void KviIOGraphWidget::paintEvent(QPaintEvent*)’:

Bug#974016: mrs: FTBFS with libzeep-dev 5.0.0-1: "Checking for libzeep...libzeep is not installed"

2020-11-08 Thread Juhani Numminen
Source: mrs Version: 6.0.5+dfsg-8 Severity: serious Tags: ftbfs sid Justification: fails to build from source (but built successfully in the past) Dear Maintainer, mrs fails to build from source on multiple architectures, with the message quoted below. See

Bug#969839: rust-failure: Should rust-failure be removed from unstable?

2020-11-08 Thread Salvatore Bonaccorso
Hi Peter, On Mon, Nov 09, 2020 at 12:07:16AM +, peter green wrote: > reassign 973298 rust-failure > retitle 973298 rust-failure: Should rust-failure be removed from unstable? > thanks > > > As there was no objection (although admittely 2 weeks might be short), > > but the upstream is

Bug#974014: Fails to install due to depending on ruby-rails < 6.0

2020-11-08 Thread Pirate Praveen
On 2020, നവംബർ 9 8:28:17 AM IST, Daniel Leidert wrote: >Package: diaspora >Version: 0.7.9.0+dfsg-4 >Severity: grave > >-BEGIN PGP SIGNED MESSAGE- >Hash: SHA512 > >While investigating the other RC issue I discovered that diaspora is >uninstallable in Sid: > >The following packages have

Bug#963628: marked as done (Node-jest fails with: Error: Cannot find module 'import-local')

2020-11-08 Thread Debian Bug Tracking System
Your message dated Mon, 09 Nov 2020 05:36:05 + with message-id and subject line Bug#963628: fixed in node-jest 26.6.3+ds+~cs64.27.30-1 has caused the Debian Bug report #963628, regarding Node-jest fails with: Error: Cannot find module 'import-local' to be marked as done. This means that you

Bug#964004: marked as done (jest: missing Breaks+Replaces: node-typescript-types (<< 20200626))

2020-11-08 Thread Debian Bug Tracking System
Your message dated Mon, 09 Nov 2020 05:36:05 + with message-id and subject line Bug#964004: fixed in node-jest 26.6.3+ds+~cs64.27.30-1 has caused the Debian Bug report #964004, regarding jest: missing Breaks+Replaces: node-typescript-types (<< 20200626) to be marked as done. This means that

Bug#974014: Fails to install due to depending on ruby-rails < 6.0

2020-11-08 Thread Daniel Leidert
Package: diaspora Version: 0.7.9.0+dfsg-4 Severity: grave -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 While investigating the other RC issue I discovered that diaspora is uninstallable in Sid: The following packages have unmet dependencies: diaspora : Depends: ruby-rails (< 2:6.0) but

Processed: closing 935660

2020-11-08 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > close 935660 5.5.2-1 Bug #935660 [src:tortoisehg] tortoisehg: Obsolete libs (python2) - depends python-pyqt5.qsci Marked as fixed in versions tortoisehg/5.5.2-1. Bug #935660 [src:tortoisehg] tortoisehg: Obsolete libs (python2) - depends

Bug#867787: cherrytree: Changes sometimes not saved

2020-11-08 Thread Paul Wise
On Sun, 09 Jul 2017 08:11:57 -0500 jtl wrote: > If more the one copy of Cherry Tree is open at a time > > - Auto save sometimes fails. > > - Changes to the the 2nd instance of Cherry Tree are not always saved to disk, > even though the save button was clicked, and Cherry Tree was closed out. >

Processed: closing 822586

2020-11-08 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > close 822586 0.99.15+dfsg-2 Bug #822586 [src:cherrytree] cherrytree: depends on python-gtksourceview2 which is deprecated Marked as fixed in versions cherrytree/0.99.15+dfsg-2. Bug #822586 [src:cherrytree] cherrytree: depends on

Processed: closing 936297

2020-11-08 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > close 936297 0.99.15+dfsg-2 Bug #936297 [src:cherrytree] cherrytree: Python2 removal in sid/bullseye Marked as fixed in versions cherrytree/0.99.15+dfsg-2. Bug #936297 [src:cherrytree] cherrytree: Python2 removal in sid/bullseye Marked Bug as

Processed: closing 941869

2020-11-08 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > close 941869 0.99.15+dfsg-2 Bug #941869 [src:cherrytree] cherrytree: Depends on unmaintained pygtk Marked as fixed in versions cherrytree/0.99.15+dfsg-2. Bug #941869 [src:cherrytree] cherrytree: Depends on unmaintained pygtk Marked Bug as done >

Processed: closing 938614

2020-11-08 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > close 938614 0.9.4.4+ds+git20200927+d09a2ef-2 Bug #938614 [src:syncthing-gtk] syncthing-gtk: Python2 removal in sid/bullseye Marked as fixed in versions syncthing-gtk/0.9.4.4+ds+git20200927+d09a2ef-2. Bug #938614 [src:syncthing-gtk]

Bug#956285: Problems identified in debian/copyright

2020-11-08 Thread Petter Reinholdtsen
[Moritz Mühlenhoff] >> Cristian or Andrew, please, do you have time to have a look? > > Actually 1.2.9 seems even present in salsa.git What is holding up a fix for this now? I noticed upstream closed their issue four hours ago. -- Happy hacking Petter Reinholdtsen

Processed: unarchiving 867787, reopening 867787, unarchiving 822586, reopening 822586, unarchiving 936297 ...

2020-11-08 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > # src:cherrytree was reintroduced: > https://lists.debian.org/msgid-search/546c2c3d77eaef6dc2b26c7ed7663f16df847bda.ca...@debian.org > unarchive 867787 Bug #867787 {Done: Debian FTP Masters } [cherrytree] cherrytree: Changes sometimes not saved

Processed: unarchiving 935660, reopening 935660, unarchiving 701076, reopening 701076, unarchiving 762827 ...

2020-11-08 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > # src:tortoisehg was reintroduced: > https://lists.debian.org/msgid-search/546c2c3d77eaef6dc2b26c7ed7663f16df847bda.ca...@debian.org > unarchive 935660 Bug #935660 {Done: Andreas Beckmann } [src:tortoisehg] tortoisehg: Obsolete libs (python2) -

Processed: unarchiving 938614, reopening 938614

2020-11-08 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > # src:syncthing-gtk was reintroduced: > https://lists.debian.org/msgid-search/546c2c3d77eaef6dc2b26c7ed7663f16df847bda.ca...@debian.org > unarchive 938614 Bug #938614 {Done: Debian FTP Masters } [src:syncthing-gtk] syncthing-gtk: Python2

Bug#974011: xmille: Incorrect license/copyright for xmille

2020-11-08 Thread Ryan Armstrong
Package: xmille Version: 2.0-13+b2 Severity: serious Tags: upstream Justification: Policy 4.5 Dear Maintainer, I have been researching old terminal and X games recently, and realized that much of the code from 'xmille' orignated from the terminal game 'mille', which is part of bsdgames.

Bug#969839: rust-failure: Should rust-failure be removed from unstable?

2020-11-08 Thread peter green
reassign 973298 rust-failure retitle 973298 rust-failure: Should rust-failure be removed from unstable? thanks As there was no objection (although admittely 2 weeks might be short), but the upstream is officially end-of-life. So just reassigned the bug to ftp.d.o for removal. I've just

Bug#972802: Removed package(s) from unstable

2020-11-08 Thread Paul Wise
On Sun, 2020-11-08 at 21:42 +, Debian FTP Masters wrote: > We believe that the bug you reported is now fixed; the following > package(s) have been removed from unstable: > > librust-webpki-roots-dev | 0.20.0-1+b1 | amd64, arm64, armel, armhf, i386 > rust-webpki-roots | 0.20.0-1 | source >

Bug#973588: Update from pari 2.11 to 2.13 breaks giac compilation

2020-11-08 Thread Bill Allombert
On Sat, Nov 07, 2020 at 02:32:41PM +0100, Julien Puydt wrote: > Le samedi 07 novembre 2020 à 11:05 +0100, Bill Allombert a écrit : > > Too late for that, I'll close by hand. Thanks! > > > but still, crashing is pretty bad : it should detect > > > the value is too low at startup and complain. >

Bug#970755: marked as done (gap-guava: Wrong e-mail address in Maintainer field)

2020-11-08 Thread Debian Bug Tracking System
Your message dated Sun, 08 Nov 2020 22:48:23 + with message-id and subject line Bug#970755: fixed in gap-guava 3.15+ds-3 has caused the Debian Bug report #970755, regarding gap-guava: Wrong e-mail address in Maintainer field to be marked as done. This means that you claim that the problem

Bug#973889: marked as done (raptor2: CVE-2017-18926)

2020-11-08 Thread Debian Bug Tracking System
Your message dated Sun, 08 Nov 2020 22:08:07 + with message-id and subject line Bug#973889: fixed in raptor2 2.0.14-1.1 has caused the Debian Bug report #973889, regarding raptor2: CVE-2017-18926 to be marked as done. This means that you claim that the problem has been dealt with. If this is

Processed: tagging 973723

2020-11-08 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > tags 973723 + ftbfs Bug #973723 [src:dcmtk] libcharls-dev ships libcharls.so which is also in libdcmtk-dev Added tag(s) ftbfs. > thanks Stopping processing here. Please contact me if you need assistance. -- 973723:

Bug#967010:

2020-11-08 Thread Quốc mc Nguyễn

Bug#894788: marked as done (vnc-java: FTBFS with openjdk-9)

2020-11-08 Thread Debian Bug Tracking System
Your message dated Sun, 08 Nov 2020 21:48:00 + with message-id and subject line Bug#973709: Removed package(s) from unstable has caused the Debian Bug report #894788, regarding vnc-java: FTBFS with openjdk-9 to be marked as done. This means that you claim that the problem has been dealt

Bug#961507: marked as done (eyes.js: unmaintained in Debian)

2020-11-08 Thread Debian Bug Tracking System
Your message dated Sun, 08 Nov 2020 21:48:27 + with message-id and subject line Bug#973913: Removed package(s) from unstable has caused the Debian Bug report #961507, regarding eyes.js: unmaintained in Debian to be marked as done. This means that you claim that the problem has been dealt

Bug#970029: marked as done (llvm-toolchain-8: should not be part of bullseye)

2020-11-08 Thread Debian Bug Tracking System
Your message dated Sun, 08 Nov 2020 21:45:53 + with message-id and subject line Bug#973479: Removed package(s) from unstable has caused the Debian Bug report #970029, regarding llvm-toolchain-8: should not be part of bullseye to be marked as done. This means that you claim that the problem

Bug#973197: marked as done (ryu: FTBFS: tests failed)

2020-11-08 Thread Debian Bug Tracking System
Your message dated Sun, 08 Nov 2020 21:46:58 + with message-id and subject line Bug#973590: Removed package(s) from unstable has caused the Debian Bug report #973197, regarding ryu: FTBFS: tests failed to be marked as done. This means that you claim that the problem has been dealt with. If

Bug#966776: marked as done (pynast: Unversioned Python removal in sid/bullseye)

2020-11-08 Thread Debian Bug Tracking System
Your message dated Sun, 08 Nov 2020 21:42:33 + with message-id and subject line Bug#972976: Removed package(s) from unstable has caused the Debian Bug report #937488, regarding pynast: Unversioned Python removal in sid/bullseye to be marked as done. This means that you claim that the problem

Bug#966752: marked as done (libaria: Unversioned Python removal in sid/bullseye)

2020-11-08 Thread Debian Bug Tracking System
Your message dated Sun, 08 Nov 2020 21:44:21 + with message-id and subject line Bug#973317: Removed package(s) from unstable has caused the Debian Bug report #936842, regarding libaria: Unversioned Python removal in sid/bullseye to be marked as done. This means that you claim that the

Bug#972802: marked as done (RM: rust-webpki-roots -- ROM; duplicates ca-certificates)

2020-11-08 Thread Debian Bug Tracking System
Your message dated Sun, 08 Nov 2020 21:42:05 + with message-id and subject line Bug#972802: Removed package(s) from unstable has caused the Debian Bug report #972802, regarding RM: rust-webpki-roots -- ROM; duplicates ca-certificates to be marked as done. This means that you claim that the

Bug#966786: marked as done (python-ruamel.ordereddict: Unversioned Python removal in sid/bullseye)

2020-11-08 Thread Debian Bug Tracking System
Your message dated Sun, 08 Nov 2020 21:44:43 + with message-id and subject line Bug#973391: Removed package(s) from unstable has caused the Debian Bug report #938150, regarding python-ruamel.ordereddict: Unversioned Python removal in sid/bullseye to be marked as done. This means that you

Bug#937488: marked as done (pynast: Python2 removal in sid/bullseye)

2020-11-08 Thread Debian Bug Tracking System
Your message dated Sun, 08 Nov 2020 21:42:33 + with message-id and subject line Bug#972976: Removed package(s) from unstable has caused the Debian Bug report #937488, regarding pynast: Python2 removal in sid/bullseye to be marked as done. This means that you claim that the problem has been

Bug#936268: caldav-tester: Python2 removal in sid/bullseye

2020-11-08 Thread Jonas Smedegaard
Quoting Jonas Smedegaard (2020-10-11 03:48:54) > Quoting Jann Haber (2020-10-11 03:26:04) > > This bug does not seem to be fixed. There is still a dependency on > > python2. Reopening. > > Right - I am sorry I processed it wrongly: I have now applied a usertag > as instructed. Seems a usertag

Bug#938150: marked as done (python-ruamel.ordereddict: Python2 removal in sid/bullseye)

2020-11-08 Thread Debian Bug Tracking System
Your message dated Sun, 08 Nov 2020 21:44:43 + with message-id and subject line Bug#973391: Removed package(s) from unstable has caused the Debian Bug report #938150, regarding python-ruamel.ordereddict: Python2 removal in sid/bullseye to be marked as done. This means that you claim that the

Bug#934958: marked as done (sqlalchemy breaks osmalchemy (autopkgtest))

2020-11-08 Thread Debian Bug Tracking System
Your message dated Sun, 08 Nov 2020 21:43:58 + with message-id and subject line Bug#973310: Removed package(s) from unstable has caused the Debian Bug report #934958, regarding sqlalchemy breaks osmalchemy (autopkgtest) to be marked as done. This means that you claim that the problem has

Bug#969622: marked as done (gnome-shell-extension-log-out-button: fails to load: TypeError: System._createActionButton is not a function)

2020-11-08 Thread Debian Bug Tracking System
Your message dated Sun, 08 Nov 2020 21:43:37 + with message-id and subject line Bug#973296: Removed package(s) from unstable has caused the Debian Bug report #969622, regarding gnome-shell-extension-log-out-button: fails to load: TypeError: System._createActionButton is not a function to be

Bug#948081: marked as done (pynast build depends on and recommends the removed blast2 transitional package)

2020-11-08 Thread Debian Bug Tracking System
Your message dated Sun, 08 Nov 2020 21:42:33 + with message-id and subject line Bug#972976: Removed package(s) from unstable has caused the Debian Bug report #948081, regarding pynast build depends on and recommends the removed blast2 transitional package to be marked as done. This means

Bug#936842: marked as done (libaria: Python2 removal in sid/bullseye)

2020-11-08 Thread Debian Bug Tracking System
Your message dated Sun, 08 Nov 2020 21:44:21 + with message-id and subject line Bug#973317: Removed package(s) from unstable has caused the Debian Bug report #936842, regarding libaria: Python2 removal in sid/bullseye to be marked as done. This means that you claim that the problem has been

Bug#967010: https://lifebox.vn/share/xi5iKcs1QnUpO7Ys

2020-11-08 Thread Quốc mc Nguyễn
Google chrome gmail

Processed: src:plink2: fails to migrate to testing for too long: FTBFS on ppc64el

2020-11-08 Thread Debian Bug Tracking System
Processing control commands: > close -1 2.00~a3-200831+dfsg-1 Bug #974003 [src:plink2] src:plink2: fails to migrate to testing for too long: FTBFS on ppc64el Marked as fixed in versions plink2/2.00~a3-200831+dfsg-1. Bug #974003 [src:plink2] src:plink2: fails to migrate to testing for too long:

Bug#974003: src:plink2: fails to migrate to testing for too long: FTBFS on ppc64el

2020-11-08 Thread Paul Gevers
Source: plink2 Version: 2.00~a3-200511+dfsg-1 Severity: serious Control: close -1 2.00~a3-200831+dfsg-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

Processed: severity of 973298 is normal, reassign 973298 to ftp.debian.org

2020-11-08 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > severity 973298 normal Bug #973298 [src:rust-failure] rust-failure: Should rust-failure be removed from unstable? Severity set to 'normal' from 'serious' > reassign 973298 ftp.debian.org Bug #973298 [src:rust-failure] rust-failure: Should

Bug#961208: marked as done (bucardo: needs a dependency on libpod-parser-perl)

2020-11-08 Thread Debian Bug Tracking System
Your message dated Sun, 08 Nov 2020 20:33:24 + with message-id and subject line Bug#961208: fixed in bucardo 5.5.0-1.1 has caused the Debian Bug report #961208, regarding bucardo: needs a dependency on libpod-parser-perl to be marked as done. This means that you claim that the problem has

Processed: affects 973723

2020-11-08 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > affects 973723 src:odin Bug #973723 [src:dcmtk] libcharls-dev ships libcharls.so which is also in libdcmtk-dev Added indication that 973723 affects src:odin > thanks Stopping processing here. Please contact me if you need assistance. --

Processed: Bug#961208 marked as pending in bucardo

2020-11-08 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #961208 [bucardo] bucardo: needs a dependency on libpod-parser-perl Ignoring request to alter tags of bug #961208 to the same tags previously set -- 961208: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=961208 Debian Bug Tracking System

Bug#961208: marked as pending in bucardo

2020-11-08 Thread Christoph Berg
Control: tag -1 pending Hello, Bug #961208 in bucardo reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at:

Bug#973999: armnn: FTBFS: error: no matching function for call to ‘arm_compute::PoolingLayerInfo::PoolingLayerInfo(const arm_compute::PoolingType&)’

2020-11-08 Thread Sebastian Ramacher
Source: armnn Version: 19.11.1-1 Severity: serious Tags: ftbfs sid bullseye Justification: fails to build from source (but built successfully in the past) X-Debbugs-Cc: sramac...@debian.org armnn fails to build arm64: | [ 1%] Building CXX object

Bug#961208: bucardo: diff for NMU version 5.5.0-1.1

2020-11-08 Thread Dominic Hargreaves
Control: tags 961208 + patch Control: tags 961208 + pending Dear maintainer, I've prepared an NMU for bucardo (versioned as 5.5.0-1.1) and uploaded it to DELAYED/5. Please feel free to tell me if I should delay it longer. Regards. diff -u bucardo-5.5.0/debian/changelog

Bug#971969: libdata-alias-perl: FTBFS with Perl 5.32: t/03_copy.t failure

2020-11-08 Thread Dominic Hargreaves
Control: unblock 968912 by -1 On Sat, Oct 10, 2020 at 09:54:54PM +0300, Niko Tyni wrote: > Source: libdata-alias-perl > Version: 1.21-1 > Severity: important > Tags: ftbfs sid bullseye > Forwarded: https://rt.cpan.org/Public/Bug/Display.html?id=130156 > User: debian-p...@lists.debian.org >

Processed: bucardo: diff for NMU version 5.5.0-1.1

2020-11-08 Thread Debian Bug Tracking System
Processing control commands: > tags 961208 + patch Bug #961208 [bucardo] bucardo: needs a dependency on libpod-parser-perl Added tag(s) patch. > tags 961208 + pending Bug #961208 [bucardo] bucardo: needs a dependency on libpod-parser-perl Added tag(s) pending. -- 961208:

Processed: Re: Bug#971969: libdata-alias-perl: FTBFS with Perl 5.32: t/03_copy.t failure

2020-11-08 Thread Debian Bug Tracking System
Processing control commands: > unblock 968912 by -1 Bug #968912 [release.debian.org] transition: perl 5.32 968912 was blocked by: 961157 960863 961208 972275 961155 961152 964902 972274 961154 971969 968913 968912 was not blocking any bugs. Removed blocking bug(s) of 968912: 971969 -- 968912:

Bug#961155: pod2pdf: diff for NMU version 0.42-5.1

2020-11-08 Thread Dominic Hargreaves
Control: tags 961155 + patch Control: tags 961155 + pending Dear maintainer, I've prepared an NMU for pod2pdf (versioned as 0.42-5.1) and uploaded it to DELAYED/5. Please feel free to tell me if I should delay it longer. Regards. diff -Nru pod2pdf-0.42/debian/changelog

Processed: pod2pdf: diff for NMU version 0.42-5.1

2020-11-08 Thread Debian Bug Tracking System
Processing control commands: > tags 961155 + patch Bug #961155 [pod2pdf] pod2pdf: needs build and runtime dependencies on libpod-parser-perl Added tag(s) patch. > tags 961155 + pending Bug #961155 [pod2pdf] pod2pdf: needs build and runtime dependencies on libpod-parser-perl Added tag(s)

Bug#961154: debarchiver: needs a build dependency on libpod-parser-perl

2020-11-08 Thread Dominic Hargreaves
Hi, Could you please upload this soon? We've just kicked off the transition so this will prevent your package from being buildable in unstable soon. Cheers Dominic On Thu, May 21, 2020 at 08:56:35AM +0200, Ola Lundqvist wrote: > Thank you. Will add on next ipload. > > Den ons 20 maj 2020

Processed: apt-show-versions: diff for NMU version 0.22.11+nmu1

2020-11-08 Thread Debian Bug Tracking System
Processing control commands: > tags 961152 + patch Bug #961152 [apt-show-versions] apt-show-versions: needs a build dependency on libpod-parser-perl Added tag(s) patch. > tags 961152 + pending Bug #961152 [apt-show-versions] apt-show-versions: needs a build dependency on libpod-parser-perl

Bug#961152: apt-show-versions: diff for NMU version 0.22.11+nmu1

2020-11-08 Thread Dominic Hargreaves
Control: tags 961152 + patch Control: tags 961152 + pending Dear maintainer, I've prepared an NMU for apt-show-versions (versioned as 0.22.11+nmu1) and uploaded it to DELAYED/5. Please feel free to tell me if I should delay it longer. Regards. diff -Nru

Processed: transition imminent

2020-11-08 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > severity 961152 serious Bug #961152 [apt-show-versions] apt-show-versions: needs a build dependency on libpod-parser-perl Severity set to 'serious' from 'important' > severity 961154 serious Bug #961154 [debarchiver] debarchiver: needs a build

Bug#973199: marked as done (python-libnacl: FTBFS: dh_auto_test: error: pybuild --test -i python{version} -p "3.9 3.8" returned exit code 13)

2020-11-08 Thread Debian Bug Tracking System
Your message dated Sun, 08 Nov 2020 17:04:49 + with message-id and subject line Bug#973199: fixed in python-libnacl 1.7.2-1 has caused the Debian Bug report #973199, regarding python-libnacl: FTBFS: dh_auto_test: error: pybuild --test -i python{version} -p "3.9 3.8" returned exit code 13 to

Bug#973991: gitaly FTBFS: test failures

2020-11-08 Thread Adrian Bunk
Source: gitaly Version: 13.3.9+dfsg-1 Severity: serious Tags: ftbfs https://buildd.debian.org/status/package.php?p=gitaly=sid ... FAIL FAILgitlab.com/gitlab-org/gitaly/client 0.169s ? gitlab.com/gitlab-org/gitaly/cmd/gitaly [no test files] ?

Processed: Bug#973199 marked as pending in python-libnacl

2020-11-08 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #973199 [src:python-libnacl] python-libnacl: FTBFS: dh_auto_test: error: pybuild --test -i python{version} -p "3.9 3.8" returned exit code 13 Ignoring request to alter tags of bug #973199 to the same tags previously set -- 973199:

Bug#966575: marked as done (grub-pc: error: symbol `grub_calloc' not found.)

2020-11-08 Thread Debian Bug Tracking System
Your message dated Sun, 08 Nov 2020 16:48:35 + with message-id and subject line Bug#966575: fixed in grub2 2.04-10 has caused the Debian Bug report #966575, regarding grub-pc: error: symbol `grub_calloc' not found. to be marked as done. This means that you claim that the problem has been

Bug#973199: marked as pending in python-libnacl

2020-11-08 Thread Colin Watson
Control: tag -1 pending Hello, Bug #973199 in python-libnacl reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at:

Processed: Bug#973199 marked as pending in python-libnacl

2020-11-08 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #973199 [src:python-libnacl] python-libnacl: FTBFS: dh_auto_test: error: pybuild --test -i python{version} -p "3.9 3.8" returned exit code 13 Added tag(s) pending. -- 973199: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=973199 Debian Bug

Bug#973199: marked as pending in python-libnacl

2020-11-08 Thread Colin Watson
Control: tag -1 pending Hello, Bug #973199 in python-libnacl reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at:

Bug#957672: marked as done (pekwm: ftbfs with GCC-10)

2020-11-08 Thread Debian Bug Tracking System
Your message dated Sun, 08 Nov 2020 16:33:51 + with message-id and subject line Bug#957672: fixed in pekwm 0.1.17-4 has caused the Debian Bug report #957672, regarding pekwm: ftbfs with GCC-10 to be marked as done. This means that you claim that the problem has been dealt with. If this is

Bug#948197: marked as done (gthumb: CVE-2019-20326: Heap buffer overflow)

2020-11-08 Thread Debian Bug Tracking System
Your message dated Sun, 08 Nov 2020 16:33:46 + with message-id and subject line Bug#948197: fixed in gthumb 3:3.8.3-0.1 has caused the Debian Bug report #948197, regarding gthumb: CVE-2019-20326: Heap buffer overflow to be marked as done. This means that you claim that the problem has been

Bug#966575: marked as pending in grub2

2020-11-08 Thread Colin Watson
Control: tag -1 pending Hello, Bug #966575 in grub2 reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at:

Processed: Bug#966575 marked as pending in grub2

2020-11-08 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #966575 [grub-pc] grub-pc: error: symbol `grub_calloc' not found. Added tag(s) pending. -- 966575: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=966575 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Processed: Clear matters on that bug report

2020-11-08 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > found 972827 1.6.0.25+dfsg1-1 Bug #972827 {Done: Julien Puydt } [libgiac-dev] libgiac-dev: should include config.h Marked as found in versions giac/1.6.0.25+dfsg1-1. > notfound 972827 1.6.0.25+dfsg1-2 Bug #972827 {Done: Julien Puydt }

Bug#972764: marked as done (cantor ftbfs with python3.9)

2020-11-08 Thread Debian Bug Tracking System
Your message dated Sun, 08 Nov 2020 12:18:28 + with message-id and subject line Bug#972764: fixed in cantor 4:20.08.3-1 has caused the Debian Bug report #972764, regarding cantor ftbfs with python3.9 to be marked as done. This means that you claim that the problem has been dealt with. If

Bug#973703: marked as done (cantor-backend-scilab: dependency no longer available on i386 and armhf)

2020-11-08 Thread Debian Bug Tracking System
Your message dated Sun, 08 Nov 2020 12:18:28 + with message-id and subject line Bug#973703: fixed in cantor 4:20.08.3-1 has caused the Debian Bug report #973703, regarding cantor-backend-scilab: dependency no longer available on i386 and armhf to be marked as done. This means that you claim

Processed: tagging 972764, tagging 973703

2020-11-08 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > tags 972764 + pending Bug #972764 [src:cantor] cantor ftbfs with python3.9 Added tag(s) pending. > tags 973703 + pending Bug #973703 [cantor-backend-scilab] cantor-backend-scilab: dependency no longer available on i386 and armhf Added tag(s)

Bug#973868: marked as done (satpy: autopkgtest failure with pyproj 3.0.0)

2020-11-08 Thread Debian Bug Tracking System
Your message dated Sun, 08 Nov 2020 11:33:44 + with message-id and subject line Bug#973867: fixed in pyresample 1.16.0+ds-3 has caused the Debian Bug report #973867, regarding satpy: autopkgtest failure with pyproj 3.0.0 to be marked as done. This means that you claim that the problem has

Bug#973868: marked as done (satpy: autopkgtest failure with pyproj 3.0.0)

2020-11-08 Thread Debian Bug Tracking System
Your message dated Sun, 08 Nov 2020 11:33:44 + with message-id and subject line Bug#973868: fixed in pyresample 1.16.0+ds-3 has caused the Debian Bug report #973868, regarding satpy: autopkgtest failure with pyproj 3.0.0 to be marked as done. This means that you claim that the problem has

Bug#973867: marked as done (pyresample: autopkgtest failure with pyproj 3.0.0)

2020-11-08 Thread Debian Bug Tracking System
Your message dated Sun, 08 Nov 2020 11:33:44 + with message-id and subject line Bug#973868: fixed in pyresample 1.16.0+ds-3 has caused the Debian Bug report #973868, regarding pyresample: autopkgtest failure with pyproj 3.0.0 to be marked as done. This means that you claim that the problem

Bug#973867: marked as done (pyresample: autopkgtest failure with pyproj 3.0.0)

2020-11-08 Thread Debian Bug Tracking System
Your message dated Sun, 08 Nov 2020 11:33:44 + with message-id and subject line Bug#973867: fixed in pyresample 1.16.0+ds-3 has caused the Debian Bug report #973867, regarding pyresample: autopkgtest failure with pyproj 3.0.0 to be marked as done. This means that you claim that the problem

Bug#961534: marked as done (s-tui: Missing package relation with stress/stress-ng (Suggests or Recommends))

2020-11-08 Thread Debian Bug Tracking System
Your message dated Sun, 08 Nov 2020 11:34:16 + with message-id and subject line Bug#961534: fixed in s-tui 1.0.2-2 has caused the Debian Bug report #961534, regarding s-tui: Missing package relation with stress/stress-ng (Suggests or Recommends) to be marked as done. This means that you

Processed: close bug that was accidentally reopened

2020-11-08 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > close 973499 69.5.1-2 Bug #973499 [rust-onig-sys] rust-onig: autopkgtest fails on i386/armhf with new bindgen/onig-sys There is no source info for the package 'rust-onig-sys' at version '69.5.1-2' with architecture '' Unable to make a source

Processed: forcibly merging 973867 973868

2020-11-08 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > forcemerge 973867 973868 Bug #973867 [src:pyresample] pyresample: autopkgtest failure with pyproj 3.0.0 Bug #973868 [src:pyresample] satpy: autopkgtest failure with pyproj 3.0.0 Set Bug forwarded-to-address to

Bug#973955: bind9: flaky autopkgtest: DNS query rootserver

2020-11-08 Thread Sebastian Andrzej Siewior
Source: bind9 Version: 1:9.16.6-3 Severity: serious Tags: sid bullseye User: debian...@lists.debian.org Usertags: flaky Hi, the autopkg test validates DNSSEC of internetsociety.org for it requires unrestricted internet access. For this it is needed to specify Restrictions: needs-internet in

Processed: tagging 973867

2020-11-08 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > tags 973867 - fixed Bug #973867 [src:pyresample] pyresample: autopkgtest failure with pyproj 3.0.0 Removed tag(s) fixed. > thanks Stopping processing here. Please contact me if you need assistance. -- 973867:

Processed (with 1 error): merge #973868 and #973867

2020-11-08 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > reassign 973868 src:pyresample 1.16.0+ds-2 Bug #973868 [pyresample] satpy: autopkgtest failure with pyproj 3.0.0 Bug reassigned from package 'pyresample' to 'src:pyresample'. No longer marked as found in versions 1.16.0+ds-2. Ignoring request to

Processed (with 1 error): merge #973868 and #973867

2020-11-08 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > merge 973868 973867 Bug #973868 [pyresample] satpy: autopkgtest failure with pyproj 3.0.0 Unable to merge bugs because: affects of #973867 is '' not 'src:satpy' package of #973867 is 'src:pyresample' not 'pyresample' Failed to merge 973868: Did

Processed: affects 973868

2020-11-08 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > affects 973868 src:satpy Bug #973868 [python3-pyresample] satpy: autopkgtest failure with pyproj 3.0.0 Added indication that 973868 affects src:satpy > thanks Stopping processing here. Please contact me if you need assistance. -- 973868:

Processed: reassign #973868

2020-11-08 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > reassign 973868 pyresample 1.16.0+ds-2 Bug #973868 [python3-pyresample] satpy: autopkgtest failure with pyproj 3.0.0 Bug reassigned from package 'python3-pyresample' to 'pyresample'. No longer marked as found in versions pyresample/1.16.0+ds-2.

Processed: reassign #973868

2020-11-08 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > reassign 973868 python3-pyresample 1.16.0+ds-2 Bug #973868 [src:satpy] satpy: autopkgtest failure with pyproj 3.0.0 Bug reassigned from package 'src:satpy' to 'python3-pyresample'. No longer marked as found in versions satpy/0.23.0-1. Ignoring

Bug#954613: rust-process-viewer: FTBFS: unsatisfiable build-dependency: librust-sysinfo-0.9+default-dev

2020-11-08 Thread Sylvestre Ledru
Hello Wofgang, Do you have the intention to fix process-viewer? We have a RC bug from March on it. If you don't plan to, maybe we should just remove it from the Debian archive. Thanks Sylvestre

Bug#973022: marked as done (python-blosc's autopkg tests are failing with python3.9)

2020-11-08 Thread Debian Bug Tracking System
Your message dated Sun, 08 Nov 2020 08:50:42 + with message-id and subject line Bug#973022: fixed in python-blosc 1.8.1+ds1-2.1 has caused the Debian Bug report #973022, regarding python-blosc's autopkg tests are failing with python3.9 to be marked as done. This means that you claim that the

Processed: tagging 971771

2020-11-08 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > tags 971771 + fixed Bug #971771 {Done: Mechtilde Stehmann } [webext-eas4tbsync] Incompatible with Thunderbird 78 Added tag(s) fixed. > thanks Stopping processing here. Please contact me if you need assistance. -- 971771:

Processed: tweak some bug metadata so it doesn't cause unnecessary testing removals.

2020-11-08 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > #build dependencies of testing's version are satisfiable in testing > notfound 971141 5.0.0-3 Bug #971141 {Done: Paride Legovini } [src:rust-onig] rust-onig: FTBFS: unsatisfiable build-dependencies: librust-cexpr-0.3+default-dev (>= 0.3.3-~~),

Processed: Actually execute the commands

2020-11-08 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > reassign 973767 src:slepc 3.14.0+dfsg1-1 Bug #973767 {Done: Drew Parsons } [src:dolfin] dolfin FTBFS: The MPI_Comm_rank() function was called before MPI_INIT was invoked. Bug reassigned from package 'src:dolfin' to 'src:slepc'. No longer marked

Processed: Move bugs where it was fixed

2020-11-08 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > reassign 973007 gnuradio-dev 3.8.2.0-5 Bug #973007 {Done: bott...@debian.org (A. Maitland Bottoms)} [src:gr-air-modes] gr-air-modes: FTBFS in unstable Bug reassigned from package 'src:gr-air-modes' to 'gnuradio-dev'. No longer marked as found in

Processed: python3-rna, librna-perl: Cannot fulfill the dependencies

2020-11-08 Thread Debian Bug Tracking System
Processing control commands: > affects -1 librna-perl Bug #973947 [python3-rna] python3-rna, librna-perl: Cannot fulfill the dependencies Added indication that 973947 affects librna-perl -- 973947: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=973947 Debian Bug Tracking System Contact

Bug#973947: python3-rna, librna-perl: Cannot fulfill the dependencies

2020-11-08 Thread Adrian Bunk
Package: python3-rna Version: 2.4.14+dfsg-2 Severity: serious Control: affects -1 librna-perl The following packages have unmet dependencies: python3-rna : Depends: libvienna-rna but it is not installable librna-perl : Depends: libviennarna0 but it is not installable The library does not