Bug#967172: Python2 removal bug resurfaced in madness

2020-08-11 Thread merkys
Hi Stuart, I saw you have fixed Python2 removal related issue (#943167) in madness 0.10.1~gite4aa500e-11 upload to experimental. However, unstable still has 0.10.1~gite4aa500e-10.1 with the same issue now reported as #967172. Is there a reason for not uploading your fix to unstable? Best,

Bug#957049: marked as done (bluez-tools: ftbfs with GCC-10)

2020-08-11 Thread Debian Bug Tracking System
Your message dated Wed, 12 Aug 2020 03:03:26 + with message-id and subject line Bug#957049: fixed in bluez-tools 2.0~20170911.0.7cb788c-3 has caused the Debian Bug report #957049, regarding bluez-tools: ftbfs with GCC-10 to be marked as done. This means that you claim that the problem has

Bug#967487: libubootenv: Cannot build libubootenv with dpkg-buildpackage

2020-08-11 Thread Nobuhiro Iwamatsu
Hi, Thanks for your report. 2020年8月4日(火) 19:50 Gylstorff Quirin : > > Package: libubootenv-tool > Version: 0.2-1 > Severity: serious > Tags: patch ftbfs > Justification: fails to build from source > > Dear Maintainer, > > I tried to build libubootenv-tool with dpkg-buildpackage and the

Processed: notfound 967130 in foxtrotgps/1.2.2-2

2020-08-11 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > notfound 967130 foxtrotgps/1.2.2-2 Bug #967130 {Done: Paul Wise } [src:foxtrotgps] foxtrotgps: Unversioned Python removal in sid/bullseye No longer marked as found in versions foxtrotgps/1.2.2-2. > thanks Stopping processing here. Please

Bug#968248: marked as done (orca: Do not install Orca 3.36.4; wait for Orca 3.36.5)

2020-08-11 Thread Debian Bug Tracking System
Your message dated Wed, 12 Aug 2020 01:48:26 + with message-id and subject line Bug#968248: fixed in orca 3.36.5-1 has caused the Debian Bug report #968248, regarding orca: Do not install Orca 3.36.4; wait for Orca 3.36.5 to be marked as done. This means that you claim that the problem has

Bug#968047: closed by Debian FTP Masters (reply to Norbert Preining ) (Bug#968047: fixed in texlive-extra 2020.20200804-2)

2020-08-11 Thread Norbert Preining
> That change did not make it into the package, the B+R still contain the > old version: Uggh, ACKed ... sometimes one cannot see the forest between all the trees ... # CharisSIL-*.ttf moved from texlive-fonts-extra to texlive-fonts-extra-links

Processed: Re: Bug#968047 closed by Debian FTP Masters (reply to Norbert Preining ) (Bug#968047: fixed in texlive-extra 2020.20200804-2)

2020-08-11 Thread Debian Bug Tracking System
Processing control commands: > found -1 2020.20200804-2 Bug #968047 {Done: Norbert Preining } [texlive-fonts-extra-links] texlive-fonts-extra-links: missing Breaks+Replaces: texlive-fonts-extra (<< 2020.20200804) Marked as found in versions texlive-extra/2020.20200804-2; no longer marked as

Bug#968047: closed by Debian FTP Masters (reply to Norbert Preining ) (Bug#968047: fixed in texlive-extra 2020.20200804-2)

2020-08-11 Thread Andreas Beckmann
Control: found -1 2020.20200804-2 That change did not make it into the package, the B+R still contain the old version: Package: texlive-fonts-extra-links Source: texlive-extra Version: 2020.20200804-2 Replaces: texlive-fonts-extra (<< 2019.20191208) Breaks: texlive-fonts-extra (<< 2019.20191208)

Processed: tagging 956355

2020-08-11 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > tags 956355 + pending Bug #956355 [src:pam] pam: Please stop using deprecated and headers Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 956355:

Bug#968246: dnstwist: Autopkgtest failure due to depgrecation warning with dnspython 2.0.0

2020-08-11 Thread Scott Kitterman
On Tuesday, August 11, 2020 1:38:52 PM EDT Peter Wienemann wrote: > Hi Scott, > > On 11.08.20 17:54, Scott Kitterman wrote: > > Unless you object, I'll probably do an NMU to do that since this will > > block dnspython testing migration. I'll post a diff to the bug before I > > do. > > that is

Bug#963760: new upstream release (1.4.10)

2020-08-11 Thread Daniel Baumann
retitle 963760 new upstream release (1.4.11) thanks ...and now there's 1.4.11. Regards, Daniel

Processed: Re: new upstream release (1.4.10)

2020-08-11 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > retitle 963760 new upstream release (1.4.11) Bug #963760 [ceph] new upstream release (1.4.10) Changed Bug title to 'new upstream release (1.4.11)' from 'new upstream release (1.4.10)'. > thanks Stopping processing here. Please contact me if you

Bug#957327: marked as done (hardinfo: ftbfs with GCC-10)

2020-08-11 Thread Debian Bug Tracking System
Your message dated Tue, 11 Aug 2020 22:03:32 + with message-id and subject line Bug#957327: fixed in hardinfo 0.5.1+git20180227-2.1 has caused the Debian Bug report #957327, regarding hardinfo: ftbfs with GCC-10 to be marked as done. This means that you claim that the problem has been dealt

Bug#966935: libpandoc-wrapper-perl: FTBFS: dh_auto_test: error: perl Build test --verbose 1 returned exit code 1

2020-08-11 Thread itd
Hi, Lucas Nussbaum writes: >> # at t/methods.t line 86. >> # got: '> class="header-section-number">1 x >> # ' >> # expected: '1 >> x >> # ' >> # Looks like you failed 1 test of 36. my best guess is that this is caused by changes in pandoc or its dependencies. (And the

Processed: tagging 957029

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

Bug#968246: dnstwist: Autopkgtest failure due to depgrecation warning with dnspython 2.0.0

2020-08-11 Thread Samuel Henrique
Hello, > On Tuesday, August 11, 2020 1:38:52 PM EDT Peter Wienemann wrote: > > @Security tools team: I requested a review/upload of a new version of > > dnstwist last week [0]. Given Scott's planned NMU it might be good to > > hold off the upload of the new version until the NMU is acknowledged.

Processed: Re: Bug#967022: mes: FTBFS: checking for cc is Mes C....config.c:2:2: error: #error no mesc

2020-08-11 Thread Debian Bug Tracking System
Processing control commands: > retitle 967022 mes: FTBFS: test failure on amd64: > lib/tests/scaffold/63-struct-cell.c Bug #967022 [src:mes] mes: FTBFS: checking for cc is Mes Cconfig.c:2:2: error: #error no mesc Changed Bug title to 'mes: FTBFS: test failure on amd64:

Bug#967022: mes: FTBFS: checking for cc is Mes C....config.c:2:2: error: #error no mesc

2020-08-11 Thread Vagrant Cascadian
Control: retitle 967022 mes: FTBFS: test failure on amd64: lib/tests/scaffold/63-struct-cell.c Control: forwarded 967022 https://lists.gnu.org/archive/html/bug-mes/2020-07/msg4.html Thanks for the report! On 2020-08-03, Lucas Nussbaum wrote: >> [0;31mFAIL[m:

Bug#957353: marked as done (ifhp: ftbfs with GCC-10)

2020-08-11 Thread Debian Bug Tracking System
Your message dated Tue, 11 Aug 2020 20:26:56 + with message-id and subject line Bug#957353: fixed in ifhp 3.5.20-17 has caused the Debian Bug report #957353, regarding ifhp: ftbfs with GCC-10 to be marked as done. This means that you claim that the problem has been dealt with. If this is not

Bug#957189: f-irc: diff for NMU version 1.36-1.1

2020-08-11 Thread Sudip Mukherjee
Control: tags 957189 + patch Control: tags 957189 + pending Dear maintainer, I've prepared an NMU for f-irc (versioned as 1.36-1.1) and uploaded it to DELAYED/2. Please feel free to tell me if I should cancel it. -- Regards Sudip diff -Nru f-irc-1.36/debian/changelog

Processed: f-irc: diff for NMU version 1.36-1.1

2020-08-11 Thread Debian Bug Tracking System
Processing control commands: > tags 957189 + patch Bug #957189 [src:f-irc] f-irc: ftbfs with GCC-10 Added tag(s) patch. > tags 957189 + pending Bug #957189 [src:f-irc] f-irc: ftbfs with GCC-10 Added tag(s) pending. -- 957189: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=957189 Debian Bug

Bug#966943: marked as done (tinygltf: FTBFS: dpkg-gensymbols: error: some symbols or patterns disappeared in the symbols file: see diff output below)

2020-08-11 Thread Debian Bug Tracking System
Your message dated Tue, 11 Aug 2020 19:49:46 + with message-id and subject line Bug#966943: fixed in tinygltf 2.2.0+dfsg1-4 has caused the Debian Bug report #966943, regarding tinygltf: FTBFS: dpkg-gensymbols: error: some symbols or patterns disappeared in the symbols file: see diff output

Bug#964541: marked as done (flatpak: Wrong argument order for clone syscall seccomp filter on s390x)

2020-08-11 Thread Debian Bug Tracking System
Your message dated Tue, 11 Aug 2020 19:18:26 + with message-id and subject line Bug#964541: fixed in gnome-desktop3 3.37.90.1-2 has caused the Debian Bug report #964541, regarding flatpak: Wrong argument order for clone syscall seccomp filter on s390x to be marked as done. This means that

Bug#968246: dnstwist: Autopkgtest failure due to depgrecation warning with dnspython 2.0.0

2020-08-11 Thread Scott Kitterman
On Tuesday, August 11, 2020 1:38:52 PM EDT Peter Wienemann wrote: > Hi Scott, > > On 11.08.20 17:54, Scott Kitterman wrote: > > Unless you object, I'll probably do an NMU to do that since this will > > block dnspython testing migration. I'll post a diff to the bug before I > > do. > > that is

Processed: your mail

2020-08-11 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > tags 966998 +patch Bug #966998 [src:lxc] lxc: FTBFS: lsm/selinux.c:35:2: error: ‘security_context_t’ is deprecated [-Werror=deprecated-declarations] Added tag(s) patch. > End of message, stopping processing here. Please contact me if you need

Bug#966998: patch

2020-08-11 Thread Harald Dunkel
Attached you can find the diff. commit 15d82dfe4f7900be54e06b6ca0a79321ee2a9b34 Author: Christian Brauner Date: Sat Jul 25 11:36:46 2020 +0200 selinux: remove security_context_t usage as it's deprecated Link: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1888705

Bug#907496: libcurlpp0: Always fails with "No URL set!"

2020-08-11 Thread Aloïs Micard
This bug has been finally reproduced on a refresh VM. It happens when the NSS flavour of libcurl4-dev is installed. Otherwise with both GnuTLS / OpenSSL it works without problem. I will write a patch to fix that. Cheers -- Aloïs Micard (creekorful) GPG: DA4A A436 9BFA E299 67CD E85B F733

Processed: your mail

2020-08-11 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > reopen 907496 Bug #907496 {Done: Aloïs Micard } [libcurlpp0] libcurlpp0: Always fails with "No URL set!" Bug reopened Ignoring request to alter fixed versions of bug #907496 to the same values previously set > forwarded 907496

Bug#968246: dnstwist: Autopkgtest failure due to depgrecation warning with dnspython 2.0.0

2020-08-11 Thread Peter Wienemann
Hi Scott, On 11.08.20 17:54, Scott Kitterman wrote: > Unless you object, I'll probably do an NMU to do that since this will block > dnspython testing migration. I'll > post a diff to the bug before I do. that is fine with me. @Security tools team: I requested a review/upload of a new version

Bug#966575: How to fix LLVM/LUKS installs?

2020-08-11 Thread Colin Watson
On Tue, Aug 11, 2020 at 12:51:17PM -0400, Todd Howe wrote: > I got around to fixing my desktop today. In addition to the instructions I > posted above and the procedure to mount system directories below, there was > only one necessary change: > >

Bug#966575: How to fix LLVM/LUKS installs?

2020-08-11 Thread Todd Howe
I got around to fixing my desktop today. In addition to the instructions I posted above and the procedure to mount system directories below, there was only one necessary change: https://gist.github.com/samuelcolvin/43c5ed2807e7db004b1058d0c9bfb068 That guy suggested used grub-install /dev/sda

Processed: fixed 968248 in 3.37.90-1

2020-08-11 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > fixed 968248 3.37.90-1 Bug #968248 [orca] orca: Do not install Orca 3.36.4; wait for Orca 3.36.5 Marked as fixed in versions orca/3.37.90-1. > thanks Stopping processing here. Please contact me if you need assistance. -- 968248:

Bug#968248: orca: Do not install Orca 3.36.4; wait for Orca 3.36.5

2020-08-11 Thread Samuel Thibault
Package: orca Version: 3.36.4-1 Severity: serious Tags: upstream Justification: breaks web navigation Forwarded: https://mail.gnome.org/archives/orca-list/2020-August/msg00085.html As reported by upstream https://mail.gnome.org/archives/orca-list/2020-August/msg00085.html we really need to

Bug#963645: marked as done (libcork: FTBFS with Sphinx 3.1: assert symbol.siblingAbove.siblingBelow is None)

2020-08-11 Thread Debian Bug Tracking System
Your message dated Tue, 11 Aug 2020 16:18:52 + with message-id and subject line Bug#963645: fixed in libcork 0.15.0+ds-14 has caused the Debian Bug report #963645, regarding libcork: FTBFS with Sphinx 3.1: assert symbol.siblingAbove.siblingBelow is None to be marked as done. This means that

Bug#968246: dnstwist: Autopkgtest failure due to depgrecation warning with dnspython 2.0.0

2020-08-11 Thread Scott Kitterman
Package: dnstwist Version: 0~20200424-1 Severity: serious Tags: ftbfs Justification: fails to build from source (but built successfully in the past) Note: Using FTBTS tag since it's the closest thing we have to this (since autopkgtest failures block testing migration). >From the autopkgtest log

Bug#964880: [Pkg-javascript-devel] Bug#964880: npm: test failures in ppc64el and s390x

2020-08-11 Thread Xavier
Le 11/07/2020 à 19:54, Gianfranco Costamagna a écrit : > Source: npm > Version: 6.14.6+ds-1 > Severity: serious > > Hello, looks like one test is failing on ppc64el and s390x. > Could you please have a look? > > this on s390x >

Bug#968245: fpc: autopkgtest failure.

2020-08-11 Thread peter green
Package: fpc Version: 3.2.0+dfsg-5 Severity: serious The autopkgtest for fpc 3.2.0 is failing Compiling utests.pp PPU Loading /usr/lib/x86_64-linux-gnu/fpc/3.2.0/units/x86_64-linux/fcl-base/custapp.ppu PPU Source: custapp.pp not available Recompiling CustApp, checksum changed for

Bug#968079: [Python-modules-team] Bug#968079: libapache2-mod-wsgi: Package is not installable. Needs older Python2.

2020-08-11 Thread Emmanuel Arias
Hi, The package needs some more work. I plan work on it this week, I hope have some news in the next few days. Cheers, Arias Emmanuel @eamanu http://eamanu.com El mar., 11 de ago. de 2020 a la(s) 12:15, nb (n...@dagami.org) escribió: > > How much time does it take to come to sid? > >

Bug#968079: libapache2-mod-wsgi: Package is not installable. Needs older Python2.

2020-08-11 Thread nb
How much time does it take to come to sid?

Bug#966760: marked as done (mklibs: Unversioned Python removal in sid/bullseye)

2020-08-11 Thread Debian Bug Tracking System
Your message dated Tue, 11 Aug 2020 15:08:21 + with message-id and subject line Bug#966760: fixed in mklibs 0.1.44.1 has caused the Debian Bug report #966760, regarding mklibs: Unversioned Python removal in sid/bullseye to be marked as done. This means that you claim that the problem has

Bug#966972: [in-toto-dev] Bug#966972: in-toto: FTBFS: ValueError: SSH supports only 1024 bit DSA keys

2020-08-11 Thread Lukas Puehringer
FYI: We just bumped upstream to include the fix: https://github.com/secure-systems-lab/securesystemslib/releases/tag/v0.16.0 Will prepare a downstream release later this week. On 06.08.2020 2:21 PM, Holger Levsen wrote: > hey Lukas, > > On Thu, Aug 06, 2020 at 02:03:00PM +0200, Lukas

Bug#966085: marked as done (gitlab contains git bundles with non-free code, unlisted code)

2020-08-11 Thread Debian Bug Tracking System
Your message dated Tue, 11 Aug 2020 14:48:31 + with message-id and subject line Bug#966085: fixed in gitlab 13.2.3-2 has caused the Debian Bug report #966085, regarding gitlab contains git bundles with non-free code, unlisted code to be marked as done. This means that you claim that the

Bug#967162: marked as done (libosmocore: Unversioned Python removal in sid/bullseye)

2020-08-11 Thread Debian Bug Tracking System
Your message dated Tue, 11 Aug 2020 14:34:08 + with message-id and subject line Bug#967162: fixed in libosmocore 0.12.1-4 has caused the Debian Bug report #967162, regarding libosmocore: Unversioned Python removal in sid/bullseye to be marked as done. This means that you claim that the

Bug#963646: marked as done (dynare: FTBFS with Sphinx 3.1: ImportError: cannot import name 'l_' from 'sphinx.locale' (/usr/lib/python3/dist-packages/sphinx/locale/__init__.py))

2020-08-11 Thread Debian Bug Tracking System
Your message dated Tue, 11 Aug 2020 14:33:41 + with message-id and subject line Bug#963646: fixed in dynare 4.6.1-2 has caused the Debian Bug report #963646, regarding dynare: FTBFS with Sphinx 3.1: ImportError: cannot import name 'l_' from 'sphinx.locale'

Bug#968212: marked as done (scheme48 misses source for S48_DETERMINE_BITS_PER_BYTE)

2020-08-11 Thread Debian Bug Tracking System
Your message dated Tue, 11 Aug 2020 14:34:52 + with message-id and subject line Bug#968212: fixed in scheme48 1.9.2-2 has caused the Debian Bug report #968212, regarding scheme48 misses source for S48_DETERMINE_BITS_PER_BYTE to be marked as done. This means that you claim that the problem

Bug#957433: marked as done (libcec: ftbfs with GCC-10)

2020-08-11 Thread Debian Bug Tracking System
Your message dated Tue, 11 Aug 2020 14:33:46 + with message-id and subject line Bug#957433: fixed in libcec 6.0.2-1 has caused the Debian Bug report #957433, regarding libcec: 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#968121: [Pkg-pascal-devel] FPC 3.2.0 upload to SID

2020-08-11 Thread peter green
On 11/08/2020 13:06, Graham Inggs wrote: I've had a quick look at ddrescue [1], but I don't know how to fix that. Does anyone have any suggestions? Googling the error message took me to https://wiki.freepascal.org/User_Changes_Trunk which has an entry "Property field access lists no longer

Processed: Bug#963646 marked as pending in dynare

2020-08-11 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #963646 [src:dynare] dynare: FTBFS with Sphinx 3.1: ImportError: cannot import name 'l_' from 'sphinx.locale' (/usr/lib/python3/dist-packages/sphinx/locale/__init__.py) Added tag(s) pending. -- 963646:

Bug#963646: marked as pending in dynare

2020-08-11 Thread Sébastien Villemot
Control: tag -1 pending Hello, Bug #963646 in dynare 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#968126: [Pkg-pascal-devel] FPC 3.2.0 upload to SID

2020-08-11 Thread peter green
On 11/08/2020 13:06, Graham Inggs wrote: I've also looked at mricron [2][3], and changing '(**)' to '*)' in both places fixes the compilation, but I have no idea what the '(**)' means. Can anyone tell me? (* and *) are comment delimeters Borland style pascal traditionally handled comments

Processed: Re:Re:See if the same error comes with gitlab 13.2.3 which I just uploaded

2020-08-11 Thread Debian Bug Tracking System
Processing control commands: > clone -1 -2 Bug #966653 [ruby-google-protobuf] gitlab: [BUG] Segmentation fault at 0x Bug 966653 cloned as bug 968239 > retitle -2 "ruby-sidekiq 6 makes gitlab uninstallable" Bug #968239 [ruby-google-protobuf] gitlab: [BUG] Segmentation fault at

Bug#966653: Re:See if the same error comes with gitlab 13.2.3 which I just uploaded

2020-08-11 Thread Pirate Praveen
Control: clone -1 -2 Control: retitle -2 "ruby-sidekiq 6 makes gitlab uninstallable" Control: reassign -2 gitlab On Tue, Aug 11, 2020 at 16:08, Pirate Praveen wrote: On Tue, Aug 11, 2020 at 13:35, dragos.ja...@dynamicpuzzle.ro wrote: dpkg -i ruby-sidekiq_5.2.7+dfsg-1_all.deb dpkg: warning:

Processed: Re: Help with new sphinx version needed (Was: Bug#966983: Most likely fixed in sphinx (2.4.3-5))

2020-08-11 Thread Debian Bug Tracking System
Processing control commands: > reassign -1 python3-sphinx 3.2.0-1 Bug #966983 [src:python-skbio] python-skbio: FTBFS: dh_sphinxdoc: error: debian/python-skbio-doc/usr/share/doc/python-skbio-doc/html/search.html does not load searchindex.js Bug reassigned from package 'src:python-skbio' to

Bug#966983: Help with new sphinx version needed (Was: Bug#966983: Most likely fixed in sphinx (2.4.3-5))

2020-08-11 Thread Dmitry Shachnev
Control: reassign -1 python3-sphinx 3.2.0-1 Control: affects -1 + src:python-skbio Hi Andreas! On Tue, Aug 11, 2020 at 02:26:40PM +0200, Andreas Tille wrote: > I need some help with a sphinx error for python-skbio: > > > > Extension error: > > > Handler for event > > >

Bug#967035: marked as done (autodep8: Unversioned Python removal in sid/bullseye)

2020-08-11 Thread Debian Bug Tracking System
Your message dated Tue, 11 Aug 2020 13:19:35 + with message-id and subject line Bug#967035: fixed in autodep8 0.24 has caused the Debian Bug report #967035, regarding autodep8: Unversioned Python removal in sid/bullseye to be marked as done. This means that you claim that the problem has

Bug#957014: marked as done (asyncpg: ftbfs with GCC-10)

2020-08-11 Thread Debian Bug Tracking System
Your message dated Tue, 11 Aug 2020 13:19:30 + with message-id and subject line Bug#957014: fixed in asyncpg 0.21.0-1 has caused the Debian Bug report #957014, regarding asyncpg: ftbfs with GCC-10 to be marked as done. This means that you claim that the problem has been dealt with. If this

Processed: fixed in 1.17.0+ds1-1

2020-08-11 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > fixed 967181 mupdf/1.17.0+ds1-1 Bug #967181 [src:mupdf] mupdf: Unversioned Python removal in sid/bullseye Marked as fixed in versions mupdf/1.17.0+ds1-1. > End of message, stopping processing here. Please contact me if you need assistance. --

Processed: Bug#967035 marked as pending in autodep8

2020-08-11 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #967035 [src:autodep8] autodep8: Unversioned Python removal in sid/bullseye Added tag(s) pending. -- 967035: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=967035 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#967035: marked as pending in autodep8

2020-08-11 Thread Antonio Terceiro
Control: tag -1 pending Hello, Bug #967035 in autodep8 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#931566: marked as done (Don't complain about suite changes (Acquire::AllowReleaseInfoChange::Suite should be "true"))

2020-08-11 Thread Debian Bug Tracking System
Your message dated Tue, 11 Aug 2020 12:48:30 + with message-id and subject line Bug#931566: fixed in apt 2.1.10 has caused the Debian Bug report #931566, regarding Don't complain about suite changes (Acquire::AllowReleaseInfoChange::Suite should be "true") to be marked as done. This means

Bug#968035: marked as done (Cannot migrate to testing due to Breaks: mercurial-crecord (<= 0.20151121-2))

2020-08-11 Thread Debian Bug Tracking System
Your message dated Tue, 11 Aug 2020 12:34:11 + with message-id and subject line Bug#968035: fixed in mercurial 5.4.1-3 has caused the Debian Bug report #968035, regarding Cannot migrate to testing due to Breaks: mercurial-crecord (<= 0.20151121-2) to be marked as done. This means that you

Bug#966983: Help with new sphinx version needed (Was: Bug#966983: Most likely fixed in sphinx (2.4.3-5))

2020-08-11 Thread Andreas Tille
Hi, I need some help with a sphinx error for python-skbio: On Tue, Aug 11, 2020 at 10:26:10AM +0200, Sebastiaan Couwenberg wrote: > On 8/11/20 9:41 AM, Andreas Tille wrote: > > On Tue, Aug 11, 2020 at 07:17:30AM +0200, Sebastiaan Couwenberg wrote: > >> A smiliar issue was reported for mapproxy

Bug#968207: marked as done (podman: Breaks docker)

2020-08-11 Thread Debian Bug Tracking System
Your message dated Tue, 11 Aug 2020 12:18:27 + with message-id and subject line Bug#968207: fixed in libpod 2.0.4+dfsg2-2 has caused the Debian Bug report #968207, regarding podman: Breaks docker to be marked as done. This means that you claim that the problem has been dealt with. If this is

Processed: forcibly merging 968220 968233

2020-08-11 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > forcemerge 968220 968233 Bug #968220 [apt] apt: 'apt source' fails: Data left in buffer Bug #968233 [apt] apt regression: abort downloads on "long" package lists Severity set to 'normal' from 'serious' Merged 968220 968233 > thanks Stopping

Processed: reassigning to protobuf

2020-08-11 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > reassign 966653 ruby-google-protobuf Bug #966653 [gitlab] gitlab: [BUG] Segmentation fault at 0x Bug reassigned from package 'gitlab' to 'ruby-google-protobuf'. No longer marked as found in versions gitlab/13.1.4-2. Ignoring

Bug#968233: apt regression: abort downloads on "long" package lists

2020-08-11 Thread Daniel Baumann
Package: apt Version: 2.1.9 Severity: serious Hi, I think I've found a regression in the apt 2.1.9 upload. When building system images, we do call 'apt install' with all the packages in one single line, which is what we've been e.g. doing since 2006 for all the live images. Until 2.1.8 this

Processed: Bug#968035 marked as pending in mercurial

2020-08-11 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #968035 [src:mercurial] Cannot migrate to testing due to Breaks: mercurial-crecord (<= 0.20151121-2) Added tag(s) pending. -- 968035: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=968035 Debian Bug Tracking System Contact

Bug#968035: marked as pending in mercurial

2020-08-11 Thread Tristan Seligmann
Control: tag -1 pending Hello, Bug #968035 in mercurial 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#955674: marked as done (haskell-gi-pango: FTBFS: hlibrary.setup: An 'autogen-module' is neither on 'exposed-modules' or 'other-modules'.)

2020-08-11 Thread Debian Bug Tracking System
Your message dated Tue, 11 Aug 2020 11:43:18 + with message-id <2020084318.ga1...@scru.org> and subject line gi-pango has caused the Debian Bug report #955674, regarding haskell-gi-pango: FTBFS: hlibrary.setup: An 'autogen-module' is neither on 'exposed-modules' or 'other-modules'. to be

Bug#968207: marked as pending in libpod

2020-08-11 Thread Reinhard Tartler
Control: tag -1 pending Hello, Bug #968207 in libpod 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#968127: marked as done (view3dscene: FTBFS with fpc 3.2.0)

2020-08-11 Thread Debian Bug Tracking System
Your message dated Tue, 11 Aug 2020 13:43:24 +0200 with message-id and subject line view3dscene: FTBFS with fpc 3.2.0 has caused the Debian Bug report #968127, regarding view3dscene: FTBFS with fpc 3.2.0 to be marked as done. This means that you claim that the problem has been dealt with. If

Processed: Bug#968207 marked as pending in libpod

2020-08-11 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #968207 [podman] podman: Breaks docker Added tag(s) pending. -- 968207: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=968207 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#966991: marked as done (seaborn: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p 3.8 returned exit code 13)

2020-08-11 Thread Debian Bug Tracking System
Your message dated Tue, 11 Aug 2020 11:35:36 + with message-id and subject line Bug#966991: fixed in seaborn 0.10.1-2 has caused the Debian Bug report #966991, regarding seaborn: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p 3.8 returned exit code 13 to be

Processed: Re: Bug#968124: diffoscope: FTBFS with fpc 3.2.0

2020-08-11 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > tags 968124 + pending Bug #968124 [src:diffoscope] diffoscope: FTBFS with fpc 3.2.0 Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 968124:

Bug#968124: diffoscope: FTBFS with fpc 3.2.0

2020-08-11 Thread Chris Lamb
tags 968124 + pending thanks Hi Graham, > As can be seen on reproducible builds [1], this package FTBFS since > the upload of fpc 3.2.0+dfsg-5 to unstable. Thanks, very useful bug report. I've fixed this in:

Bug#966653: Re:See if the same error comes with gitlab 13.2.3 which I just uploaded

2020-08-11 Thread Pirate Praveen
On Tue, Aug 11, 2020 at 13:35, dragos.ja...@dynamicpuzzle.ro wrote: dpkg -i ruby-sidekiq_5.2.7+dfsg-1_all.deb dpkg: warning: downgrading ruby-sidekiq from 6.0.4+dfsg-2 to 5.2.7+dfsg-1 (Reading database ... 411139 files and directories currently installed.) Preparing to unpack

Bug#957985: marked as done (xjdic: ftbfs with GCC-10)

2020-08-11 Thread Debian Bug Tracking System
Your message dated Tue, 11 Aug 2020 10:34:39 + with message-id and subject line Bug#957985: fixed in xjdic 24-11 has caused the Debian Bug report #957985, regarding xjdic: ftbfs with GCC-10 to be marked as done. This means that you claim that the problem has been dealt with. If this is not

Processed: ddrescueview: FTBFS with fpc 3.2.0

2020-08-11 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > tags 968121 + upstream Bug #968121 [src:ddrescueview] ddrescueview: FTBFS with fpc 3.2.0 Added tag(s) upstream. > forwarded 968121 https://sourceforge.net/p/ddrescueview/tickets/13/ Bug #968121 [src:ddrescueview] ddrescueview: FTBFS with fpc

Bug#966653: See if the same error comes with gitlab 13.2.3 which I just uploaded

2020-08-11 Thread Pirate Praveen
On Tue, Aug 11, 2020 at 13:11, dragos.ja...@dynamicpuzzle.ro wrote: Hi Praveen I installed 13.2.3,but have problems on configure with sidekiq* versions: Bundler could not find compatible versions for gem "sidekiq": In Gemfile: sidekiq gitlab-sidekiq-fetcher was resolved to 0.5.2, which

Processed: reopening 964880

2020-08-11 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > reopen 964880 Bug #964880 {Done: Xavier Guimard } [src:npm] npm: test failures in ppc64el and s390x Bug #964854 {Done: Xavier Guimard } [src:npm] npm: autopkgtests failures on s390x 'reopen' may be inappropriate when a bug has been closed with

Bug#966883: procenv: FTBFS: platform/linux/platform.c:1266:21: error: ‘%s’ directive writing up to 1017 bytes into a region of size 16 [-Werror=format-overflow=]

2020-08-11 Thread Lukas Märdian
Hello! This bug has been fixed in Ubuntu's procenv 0.50-1ubuntu3: https://launchpad.net/ubuntu/+source/procenv/0.50-1ubuntu3 A fix was proposed upstream as well: https://github.com/jamesodhunt/procenv/pull/16 Best, Lukas On Mon, 3 Aug 2020 10:05:29 +0200 Lucas Nussbaum wrote: > Source:

Bug#964880: marked as done (npm: test failures in ppc64el and s390x)

2020-08-11 Thread Debian Bug Tracking System
Your message dated Tue, 11 Aug 2020 10:06:03 + with message-id and subject line Bug#964880: fixed in node-tap 12.0.1+ds-3 has caused the Debian Bug report #964880, regarding npm: test failures in ppc64el and s390x to be marked as done. This means that you claim that the problem has been

Bug#964854: marked as done (npm: autopkgtests failures on s390x)

2020-08-11 Thread Debian Bug Tracking System
Your message dated Tue, 11 Aug 2020 10:06:03 + with message-id and subject line Bug#964880: fixed in node-tap 12.0.1+ds-3 has caused the Debian Bug report #964880, regarding npm: autopkgtests failures on s390x to be marked as done. This means that you claim that the problem has been dealt

Bug#957433: marked as done (libcec: ftbfs with GCC-10)

2020-08-11 Thread Debian Bug Tracking System
Your message dated Tue, 11 Aug 2020 10:00:12 + with message-id and subject line Bug#957433: fixed in libcec 6.0.2-1~exp0 has caused the Debian Bug report #957433, regarding libcec: ftbfs with GCC-10 to be marked as done. This means that you claim that the problem has been dealt with. If this

Processed: tagging 964880

2020-08-11 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > tags 964880 - pending Bug #964880 [src:npm] npm: test failures in ppc64el and s390x Bug #964854 [src:npm] npm: autopkgtests failures on s390x Removed tag(s) pending. Removed tag(s) pending. > thanks Stopping processing here. Please contact me if

Bug#956986: marked as done (aflplusplus: ftbfs with GCC-10)

2020-08-11 Thread Debian Bug Tracking System
Your message dated Tue, 11 Aug 2020 10:00:10 + with message-id and subject line Bug#956986: fixed in aflplusplus 2.66c-1 has caused the Debian Bug report #956986, regarding aflplusplus: ftbfs with GCC-10 to be marked as done. This means that you claim that the problem has been dealt with. If

Processed: fixed 963437 in 12.0.1+ds-3

2020-08-11 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > fixed 963437 12.0.1+ds-3 Bug #963437 [src:node-tap] node-tap: FTBFS: failed tests The source 'node-tap' and version '12.0.1+ds-3' do not appear to match any binary packages Marked as fixed in versions node-tap/12.0.1+ds-3. > thanks Stopping

Bug#964880: marked as pending in node-tap

2020-08-11 Thread Xavier Guimard
Control: tag -1 pending Hello, Bug #964880 in node-tap 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#964880 marked as pending in node-tap

2020-08-11 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #964880 [src:npm] npm: test failures in ppc64el and s390x Bug #964854 [src:npm] npm: autopkgtests failures on s390x Added tag(s) pending. Added tag(s) pending. -- 964854: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=964854 964880:

Bug#957563: marked as done (mpg321: ftbfs with GCC-10)

2020-08-11 Thread Debian Bug Tracking System
Your message dated Tue, 11 Aug 2020 09:33:42 + with message-id and subject line Bug#957563: fixed in mpg321 0.3.2-3.1 has caused the Debian Bug report #957563, regarding mpg321: 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#966857: marked as done (libtpms: FTBFS: tpm2/NVDynamic.c:126:10: error: ‘nvHandle’ may be used uninitialized in this function [-Werror=maybe-uninitialized])

2020-08-11 Thread Debian Bug Tracking System
Your message dated Tue, 11 Aug 2020 09:09:42 + with message-id and subject line Bug#966857: fixed in libtpms 0.8.0~dev1-1.2 has caused the Debian Bug report #966857, regarding libtpms: FTBFS: tpm2/NVDynamic.c:126:10: error: ‘nvHandle’ may be used uninitialized in this function

Bug#968149: mysql-router-dbgsym,mysql-server-core-8.0-dbgsym: file conflict due to shared build-id

2020-08-11 Thread Andrei POPESCU
Control: reassign -1 src:mysql-8.0 The BTS doesn't know about -dbgsym packages (see #868539), reassigning to the source package. On Du, 09 aug 20, 21:48:13, Andreas Beckmann wrote: > Package: mysql-router-dbgsym,mysql-server-core-8.0-dbgsym > Version: 8.0.20-1~exp1 > Severity: serious > User:

Processed: Re: Bug#968149: mysql-router-dbgsym,mysql-server-core-8.0-dbgsym: file conflict due to shared build-id

2020-08-11 Thread Debian Bug Tracking System
Processing control commands: > reassign -1 src:mysql-8.0 Bug #968149 [mysql-router-dbgsym,mysql-server-core-8.0-dbgsym] mysql-router-dbgsym,mysql-server-core-8.0-dbgsym: file conflict due to shared build-id Warning: Unknown package 'mysql-router-dbgsym' Warning: Unknown package

Bug#966976: marked as pending in msgpack-java

2020-08-11 Thread Andrius Merkys
Control: tag -1 pending Hello, Bug #966976 in msgpack-java 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#966976: marked as done (msgpack-java: FTBFS: dh_auto_test: error: /usr/lib/jvm/default-java/bin/java -noverify -cp /usr/share/maven/boot/plexus-classworlds-2.x.jar -Dmaven.home=/usr/share/maven -D

2020-08-11 Thread Debian Bug Tracking System
Your message dated Tue, 11 Aug 2020 08:35:33 + with message-id and subject line Bug#966976: fixed in msgpack-java 0.8.20-2 has caused the Debian Bug report #966976, regarding msgpack-java: FTBFS: dh_auto_test: error: /usr/lib/jvm/default-java/bin/java -noverify -cp

Bug#967007: marked as done (rails: package new gem dependencies for autopkgtests)

2020-08-11 Thread Debian Bug Tracking System
Your message dated Tue, 11 Aug 2020 08:36:02 + with message-id and subject line Bug#967007: fixed in rails 2:6.0.3.2+dfsg-9 has caused the Debian Bug report #967007, regarding rails: package new gem dependencies for autopkgtests to be marked as done. This means that you claim that the

Processed: Bug#966976 marked as pending in msgpack-java

2020-08-11 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #966976 {Done: Andrius Merkys } [src:msgpack-java] msgpack-java: FTBFS: dh_auto_test: error: /usr/lib/jvm/default-java/bin/java -noverify -cp /usr/share/maven/boot/plexus-classworlds-2.x.jar -Dmaven.home=/usr/share/maven

Bug#968225: marked as done (advi: FTBFS in sid)

2020-08-11 Thread Debian Bug Tracking System
Your message dated Tue, 11 Aug 2020 08:33:50 + with message-id and subject line Bug#968225: fixed in advi 1.10.2-7 has caused the Debian Bug report #968225, regarding advi: FTBFS in sid to be marked as done. This means that you claim that the problem has been dealt with. If this is not the

Bug#966983: Most likely fixed in sphinx (2.4.3-5)

2020-08-11 Thread Sebastiaan Couwenberg
On 8/11/20 9:41 AM, Andreas Tille wrote: > On Tue, Aug 11, 2020 at 07:17:30AM +0200, Sebastiaan Couwenberg wrote: >> A smiliar issue was reported for mapproxy in #966979, which was not an >> issue in mapproxy but in sphinx, and fixed in sphinx (2.4.3-5). >> >> I have not tested the build of this

Bug#963437: [Pkg-javascript-devel] Bug#963437: node-tap: FTBFS: failed tests

2020-08-11 Thread Xavier
Le 21/06/2020 à 22:32, Lucas Nussbaum a écrit : > Source: node-tap > Version: 12.0.1+ds-2 > Severity: serious > Justification: FTBFS on amd64 > Tags: bullseye sid ftbfs > Usertags: ftbfs-20200620 ftbfs-bullseye > > Hi, > > During a rebuild of all packages in sid, your package failed to build >

  1   2   >