Processed: 957430 is forwarded

Processing commands for cont...@bugs.debian.org: > forwarded 957430 ccp4-...@dl.ac.uk Bug #957430 [src:libccp4] libccp4: ftbfs with GCC-10 Set Bug forwarded-to-address to 'ccp4-...@dl.ac.uk'. > thanks Stopping processing here. Please contact me if you need assistance. -- 957430: https://bugs.deb

Bug#957147: marked as done (docopt.cpp: ftbfs with GCC-10)

Your message dated Thu, 30 Jul 2020 06:48:31 + with message-id and subject line Bug#957147: fixed in docopt.cpp 0.6.2-2.1 has caused the Debian Bug report #957147, regarding docopt.cpp: ftbfs with GCC-10 to be marked as done. This means that you claim that the problem has been dealt with. If

Bug#966432: marked as done (wcslib test failures with GCC 10)

Your message dated Thu, 30 Jul 2020 06:35:03 + with message-id and subject line Bug#966432: fixed in wcslib 7.3+ds-3 has caused the Debian Bug report #966432, regarding wcslib test failures with GCC 10 to be marked as done. This means that you claim that the problem has been dealt with. If th

Bug#957042: marked as done (biometric-authentication: ftbfs with GCC-10)

Your message dated Thu, 30 Jul 2020 06:33:54 + with message-id and subject line Bug#957042: fixed in biometric-authentication 0.9.63-1 has caused the Debian Bug report #957042, regarding biometric-authentication: ftbfs with GCC-10 to be marked as done. This means that you claim that the probl

Bug#966526: casacore: baseline violation on i386

Source: casacore Version: 2.2.0-1 Severity: serious Tags: patch SSE is not part of the baseline of the i386 port, the following fixes the baseline violation: --- debian/rules.old2020-07-28 15:12:17.759357834 +0300 +++ debian/rules2020-07-28 15:12:30.855360420 +0300 @@ -5,7 +5,7 @@

Bug#966525: dmagnetic FTBFS on i386: check-sixel failed

Source: dmagnetic Version: 0.25-1 Severity: serious Tags: ftbfs patch https://buildd.debian.org/status/fetch.php?pkg=dmagnetic&arch=i386&ver=0.25-1&stamp=1595804868&raw=0 ... Initializing the 68K version 0 VM check-high_ansi OK *** dMagnetic 0.25 *** Use at your own risk *** (C)opyright 2020 by d

Bug#966523: r-bioc-rsubread FTBFS on 32bit: error: conflicting types for ‘uintptr_t’

Source: r-bioc-rsubread Version: 2.2.5-1 Severity: serious Tags: ftbfs https://buildd.debian.org/status/package.php?p=r-bioc-rsubread&suite=sid ... In file included from /usr/lib/gcc/i686-linux-gnu/10/include/stdint.h:9, from HelperFunctions.h:139, from R_wrapper

Bug#966522: libgetdata: binary-all FTBFS

Source: libgetdata Version: 0.10.0-8 Severity: serious Tags: ftbfs https://buildd.debian.org/status/fetch.php?pkg=libgetdata&arch=all&ver=0.10.0-8&stamp=1596045626&raw=0 ... dh_missing -i dh_missing: warning: usr/include/getdata.mod exists in debian/tmp but is not installed to anywhere dh_mi

Bug#957641: marked as done (openoverlayrouter: ftbfs with GCC-10)

Your message dated Thu, 30 Jul 2020 04:03:35 + with message-id and subject line Bug#957641: fixed in openoverlayrouter 1.3.0+ds1-3 has caused the Debian Bug report #957641, regarding openoverlayrouter: ftbfs with GCC-10 to be marked as done. This means that you claim that the problem has been

Bug#965064: pkg-haskell-tools: FTBFS in unstable

On Wed, Jul 15, 2020 at 03:09:24PM +0100, Iain Lane wrote: > Upgrading shake will fix this, or it can be worked around in the In theory we can upgrade shake once js-dgtable clears NEW. It's been sitting there for 3 months.

Bug#966393: pandas: FTBFS: TypeError: use() got an unexpected keyword argument 'warn'

Control: found -1 0.25.3+dfsg2-3 Control: tags -1 fixed-upstream patch (untested) Probably matplotlib 3.3: https://github.com/pandas-dev/pandas/pull/35323

Bug#965299: marked as done (haskell-incremental-parser no longer buildable on many architectures.)

Your message dated Thu, 30 Jul 2020 01:47:45 + with message-id <20200730014745.ga20...@scru.org> and subject line rank2classes has caused the Debian Bug report #965299, regarding haskell-incremental-parser no longer buildable on many architectures. to be marked as done. This means that you cla

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

Your message dated Thu, 30 Jul 2020 01:48:27 + with message-id and subject line Bug#936628: fixed in gnucap-python 0.0.2-1.2 has caused the Debian Bug report #936628, regarding gnucap-python: Python2 removal in sid/bullseye to be marked as done. This means that you claim that the problem has

Bug#966392: [pkg-php-pear] Bug#966392: php-codecoverage: FTBFS 4 tests failed

> -Setting up php-token-stream (4.0.1-1) ... > +Setting up php-token-stream (4.0.3-1) ... > [...] >-Setting up php-phpdocumentor-reflection-docblock (4.3.3-1) ... >+Setting up php-phpdocumentor-reflection-docblock (5.1.0-1) ... One or both of these seem to be the cause. The tests pass if I specif

Bug#936288: cfv

On Mon, 27 Jul 2020 01:19:52 +0200 Stefan Alfredsson wrote: > > Closing since cfv is being removed due to python2 dependency. > > (removal request - https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=966332 ) please dont close bugs for packages that are still in the archive. the RM process takes c

Bug#965001: strange version 2.1.0 beta4 fails tests with mpfr4 4.1.0

On Wed, Jul 15, 2020, 4:27 PM Martin Kelly wrote: > On Tue, Jul 14, 2020, 3:15 AM Vincent Lefevre wrote: > >> On 2020-07-14 09:48:18 +0200, Matthias Klose wrote: >> > There is no 2.1.0 beta4, just a beta1, so I don't know what was >> packaged in >> > February 2020. However the tests now fail wi

Bug#936628: gnucap-python: diff for NMU version 0.0.2-1.2

Control: tags 936628 + patch Dear maintainer, I've prepared an NMU for gnucap-python (versioned as 0.0.2-1.2). The diff is attached to this message. Regards. diff -Nru gnucap-python-0.0.2/debian/changelog gnucap-python-0.0.2/debian/changelog --- gnucap-python-0.0.2/debian/changelog 2019-01-20

Processed: gnucap-python: diff for NMU version 0.0.2-1.2

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

Bug#966515: scons: Some upstream sources are missing

So what is this issue? Which tarball debian packages are using as their source? On Wed, Jul 29, 2020 at 4:23 PM Ben Hutchings wrote: > On Wed, 2020-07-29 at 16:11 -0700, Bill Deegan wrote: > > Note there's a bug for this on SCons tracker. > > https://github.com/SCons/scons/issues/3759 > > > > Pl

Processed: Re: Bug#963932: Unversioned symbol json_object_iter_next is in all of json-c, jansson, json-glib

Processing control commands: > severity -1 important Bug #963932 [src:json-c] json-c: Exports symbols in json_* namespace without symbol-versioning Severity set to 'important' from 'serious' -- 963932: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=963932 Debian Bug Tracking System Contact o

Bug#966515: scons: Some upstream sources are missing

On Wed, 2020-07-29 at 16:11 -0700, Bill Deegan wrote: > Note there's a bug for this on SCons tracker. > https://github.com/SCons/scons/issues/3759 > > Please add any comments there. No, that's an entirely different issue. Ben. -- Ben Hutchings, Software Developer Codeth

Bug#963932: Unversioned symbol json_object_iter_next is in all of json-c, jansson, json-glib

Control: severity -1 important * Simon McVittie [200728 00:21]: > On Sun, 28 Jun 2020 at 22:06:13 +0200, Chris Hofstaedtler wrote: > > your libraries BOTH export a symbol named json_object_iter_next, > > causing crashes for binaries that end up loading both (possibly > > transitively). [..] > B

Bug#966515: scons: Some upstream sources are missing

Note there's a bug for this on SCons tracker. https://github.com/SCons/scons/issues/3759 Please add any comments there. On Wed, Jul 29, 2020 at 4:06 PM Ben Hutchings wrote: > Source: scons > Version: 3.1.2-2 > Severity: serious > > Dear Maintainer, > > The current source package uses the 'produ

Bug#966515: scons: Some upstream sources are missing

Source: scons Version: 3.1.2-2 Severity: serious Dear Maintainer, The current source package uses the 'production' tarballs (scons-.tar.gz) as the orig tarball, whereas the upstream source tarballs are released as scons-src-.tar.gz. The 'production' tarballs contain many generated or preprocesse

Processed: Re: Bug#966393: pandas: FTBFS: TypeError: use() got an unexpected keyword argument 'warn'

Processing control commands: > found -1 0.25.3+dfsg2-3 Bug #966393 [src:pandas] pandas: FTBFS: TypeError: use() got an unexpected keyword argument 'warn' Marked as found in versions pandas/0.25.3+dfsg2-3. > tags -1 fixed-upstream patch Bug #966393 [src:pandas] pandas: FTBFS: TypeError: use() got

Bug#966199: nastran: FTBFS with GCC 10: Error: BOZ constant at (1) uses nonstandard postfix syntax

Hi Sylvestre, you sponsored the nastran upload some years ago, could you take a look again? Thanks Andreas On 7/25/20 11:50 AM, Luca Dall'Olio wrote: > Hi, > > Thank you for reporting: I just fixed the issue by adding a check in > configure.ac and defining -fallow-invalid-boz if present. I che

Bug#957004: marked as done (argus-clients: ftbfs with GCC-10)

Your message dated Wed, 29 Jul 2020 21:04:00 + with message-id and subject line Bug#957004: fixed in argus-clients 1:3.0.8.2-6 has caused the Debian Bug report #957004, regarding argus-clients: ftbfs with GCC-10 to be marked as done. This means that you claim that the problem has been dealt w

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

Your message dated Wed, 29 Jul 2020 21:05:14 + with message-id and subject line Bug#951990: fixed in willow 1.4-1 has caused the Debian Bug report #951990, regarding willow: FTBFS: dh_auto_test: error: pybuild --test -i python{version} -p "3.8 3.7" returned exit code 13 to be marked as done.

Bug#957532: marked as done (mes: ftbfs with GCC-10)

Your message dated Wed, 29 Jul 2020 20:39:33 + with message-id and subject line Bug#957532: fixed in mes 0.22-3 has caused the Debian Bug report #957532, regarding mes: 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 the c

Bug#925745: marked as done (libgtextutils: ftbfs with GCC-9)

Your message dated Wed, 29 Jul 2020 20:36:53 + with message-id and subject line Bug#925745: fixed in libgtextutils 0.7-7 has caused the Debian Bug report #925745, regarding libgtextutils: ftbfs with GCC-9 to be marked as done. This means that you claim that the problem has been dealt with. If

Bug#966500: python3-notcurses: missing Breaks+Replaces: notcurses-bin (<< 1.6)

Control: tag -1 pending On 7/29/20 2:32 PM, Nick Black wrote: > Thank you for filing my first Debian bug! How exciting, and at > the same time embarrassing. I should have caught this before > uploading. A fix is obvious, and I ought be able to accomplish > it within the Debian packaging proper, ra

Processed: Re: Bug#966500: python3-notcurses: missing Breaks+Replaces: notcurses-bin (<< 1.6)

Processing control commands: > tag -1 pending Bug #966500 [python3-notcurses] python3-notcurses: missing Breaks+Replaces: notcurses-bin (<< 1.6) Added tag(s) pending. -- 966500: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=966500 Debian Bug Tracking System Contact ow...@bugs.debian.org wit

Bug#837123: marked as done ([anna] segfault in wheezy installer)

Your message dated Wed, 29 Jul 2020 22:02:30 +0200 with message-id <20200729200230.ga14...@aurel32.net> and subject line Re: Bug#837123: [anna] segfault in wheezy installer has caused the Debian Bug report #837123, regarding [anna] segfault in wheezy installer to be marked as done. This means that

Bug#957465: marked as done (libosmocore: ftbfs with GCC-10)

Your message dated Wed, 29 Jul 2020 19:48:56 + with message-id and subject line Bug#957465: fixed in libosmocore 0.12.1-3.1 has caused the Debian Bug report #957465, regarding libosmocore: ftbfs with GCC-10 to be marked as done. This means that you claim that the problem has been dealt with.

Bug#957006: marked as done (argus: ftbfs with GCC-10)

Your message dated Wed, 29 Jul 2020 19:03:50 + with message-id and subject line Bug#957006: fixed in argus 2:3.0.8.2-2 has caused the Debian Bug report #957006, regarding argus: 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#957440: marked as done (libgetdata: ftbfs with GCC-10)

Your message dated Wed, 29 Jul 2020 17:49:18 + with message-id and subject line Bug#957440: fixed in libgetdata 0.10.0-8 has caused the Debian Bug report #957440, regarding libgetdata: ftbfs with GCC-10 to be marked as done. This means that you claim that the problem has been dealt with. If t

Bug#957289: marked as done (gnss-sdr: ftbfs with GCC-10)

Your message dated Wed, 29 Jul 2020 17:33:41 + with message-id and subject line Bug#957289: fixed in gnss-sdr 0.0.13-1 has caused the Debian Bug report #957289, regarding gnss-sdr: ftbfs with GCC-10 to be marked as done. This means that you claim that the problem has been dealt with. If this

Bug#957507: marked as done (lsmount: ftbfs with GCC-10)

Your message dated Wed, 29 Jul 2020 17:19:19 + with message-id and subject line Bug#957507: fixed in lsmount 0.2.4-1 has caused the Debian Bug report #957507, regarding lsmount: 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#957371: marked as done (ipmitool: ftbfs with GCC-10)

Your message dated Wed, 29 Jul 2020 16:48:59 + with message-id and subject line Bug#957371: fixed in ipmitool 1.8.18-9 has caused the Debian Bug report #957371, regarding ipmitool: ftbfs with GCC-10 to be marked as done. This means that you claim that the problem has been dealt with. If this

Bug#957364: marked as done (iotjs: ftbfs with GCC-10)

Your message dated Wed, 29 Jul 2020 16:48:54 + with message-id and subject line Bug#957364: fixed in iotjs 1.0-2 has caused the Debian Bug report #957364, regarding iotjs: 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 th

Bug#966500: python3-notcurses: missing Breaks+Replaces: notcurses-bin (<< 1.6)

pending thanks ok, I believe i have solved this. the problem arose when i moved notcurses-pydemo from notcurses-bin to python3-notcurses sometime since 1.5.1. so: * i've added the necessary Breaks+Replace to debian/control, and have built this as 1.6.9+dfsg.1-3. it ought remedy the reporte

Bug#957532: mes: ftbfs with GCC-10

On 2020-07-27, Vagrant Cascadian wrote: > Debian has switched to gcc 10 by default for the development releases, > and that currently breaks building mes. Apparently, Adding -fcommon to CFLAGS does allow the build to complete. from https://gcc.gnu.org/gcc-10/porting_to.html: C language issues

Bug#966093: Error: default OCI runtime "runc" not found: invalid argument -Workaround for wrong regular-user defaults

Package: podman Version: 2.0.3+dfsg1-1 Followup-For: Bug #966093 Dear Robby and Maintainer, to avoid the described failure in running podman *as a regular user*, it's enough to execute the command: $ echo 'runtime = "crun"' > ~/.config/containers/libpod.conf afterwards, both $ podman info an

Bug#966093: Error: default OCI runtime "runc" not found: invalid argument - Workaround

Package: podman Version: 2.0.3+dfsg1-1 Followup-For: Bug #966093 Dear Robby and Maintainer, while I can confirm `podman` doesn't correctly execute the `crun` runtime when started from a regular user, after executing the following command from the user's shell: $ echo 'runtime = "crun"' > ~/.c

Processed: retitle 966436 to scrambled property in identify -verbose output

Processing commands for cont...@bugs.debian.org: > retitle 966436 scrambled property in identify -verbose output Bug #966436 [src:imagemagick] ruby-mini-magick FTBFS with imagemagick 8:6.9.11.24+dfsg-1 Changed Bug title to 'scrambled property in identify -verbose output' from 'ruby-mini-magick F

Processed: found 966436 in 8:6.9.11.24+dfsg-1

Processing commands for cont...@bugs.debian.org: > found 966436 8:6.9.11.24+dfsg-1 Bug #966436 [src:imagemagick] ruby-mini-magick FTBFS with imagemagick 8:6.9.11.24+dfsg-1 Marked as found in versions imagemagick/8:6.9.11.24+dfsg-1. > thanks Stopping processing here. Please contact me if you need

Bug#966175: marked as done (libopenblas0-pthread: segfault in scipy tests: calls Haswell)

Your message dated Wed, 29 Jul 2020 15:36:13 + with message-id and subject line Bug#966175: fixed in openblas 0.3.10+ds-2 has caused the Debian Bug report #966175, regarding libopenblas0-pthread: segfault in scipy tests: calls Haswell to be marked as done. This means that you claim that the p

Bug#952673: marked as done (does not start automatically anymore on fresh installs)

Your message dated Wed, 29 Jul 2020 15:35:05 + with message-id and subject line Bug#952673: fixed in knot-resolver 5.1.2-1 has caused the Debian Bug report #952673, regarding does not start automatically anymore on fresh installs to be marked as done. This means that you claim that the proble

Bug#966463: marked as done (openblas breaks scipy autopkgtest: tests/test_vq.py::TestKMean::test_krandinit Segmentation fault)

Your message dated Wed, 29 Jul 2020 15:36:13 + with message-id and subject line Bug#966175: fixed in openblas 0.3.10+ds-2 has caused the Debian Bug report #966175, regarding openblas breaks scipy autopkgtest: tests/test_vq.py::TestKMean::test_krandinit Segmentation fault to be marked as done.

Bug#966498: marked as done (libgd-perl: Dropped libgd-gd2-perl breaks a Recommends in lcov and prevents a clean upgrade)

Your message dated Wed, 29 Jul 2020 15:04:46 + with message-id and subject line Bug#966498: fixed in libgd-perl 2.72-2 has caused the Debian Bug report #966498, regarding libgd-perl: Dropped libgd-gd2-perl breaks a Recommends in lcov and prevents a clean upgrade to be marked as done. This me

Bug#966365: marked as done (shanty: Uninstallable due to removal of libgd-gd2-{,noxpm-}perl Provides in libgd-perl)

Your message dated Wed, 29 Jul 2020 15:04:46 + with message-id and subject line Bug#966498: fixed in libgd-perl 2.72-2 has caused the Debian Bug report #966498, regarding shanty: Uninstallable due to removal of libgd-gd2-{,noxpm-}perl Provides in libgd-perl to be marked as done. This means t

Bug#966436: files

Here are the promised files Image: spec/fixtures/clipping_path.jpg Format: JPEG (Joint Photographic Experts Group JFIF format) Mime type: image/jpeg Class: DirectClass Geometry: 200x120+0+0 Resolution: 72x72 Print size: 2.8x1.7 Units: PixelsPerInch Colorspace: sRGB Type: P

Processed: found 966498 in libgd-perl/2.72-1

Processing commands for cont...@bugs.debian.org: > found 966498 libgd-perl/2.72-1 Bug #966498 [libgd-perl] libgd-perl: Dropped libgd-gd2-perl breaks a Recommends in lcov and prevents a clean upgrade Bug #966365 [libgd-perl] shanty: Uninstallable due to removal of libgd-gd2-{,noxpm-}perl Provides

Bug#966436: reassign to imagemagick 8:6.9.11.24+dfsg-1

reassign 966436 src:imagemagick found 966436 8:6.9.11.24+dfsg-1n retitle scrambled property in identify -verbose output affects 966436 ruby-mini-magick thanks ruby-mini-magick relies (too) heavily on a parsing of output of imagemagick tools like identify. The issue discussed here is caused by a c

Processed (with 1 error): reassign to imagemagick 8:6.9.11.24+dfsg-1

Processing commands for cont...@bugs.debian.org: > reassign 966436 src:imagemagick Bug #966436 [src:ruby-mini-magick] ruby-mini-magick FTBFS with imagemagick 8:6.9.11.24+dfsg-1 Bug reassigned from package 'src:ruby-mini-magick' to 'src:imagemagick'. No longer marked as found in versions ruby-mini

Bug#957700: marked as done (postgresql-mysql-fdw: ftbfs with GCC-10)

Your message dated Wed, 29 Jul 2020 14:45:01 + with message-id and subject line Bug#957700: fixed in postgresql-mysql-fdw 2.5.3-2 has caused the Debian Bug report #957700, regarding postgresql-mysql-fdw: ftbfs with GCC-10 to be marked as done. This means that you claim that the problem has be

Bug#966498: marked as pending in libgd-perl

Control: tag -1 pending Hello, Bug #966498 in libgd-perl 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/perl-team/modules/packages/libgd-perl/-/commit/ef0f4a08

Processed (with 1 error): Re: Processed (with 5 errors): Re: Bug#966498: libgd-perl: Dropped libgd-gd2-perl breaks a Recommends in lcov and prevents a clean upgrade

Processing commands for cont...@bugs.debian.org: > reassign 966365 libgd-perl Bug #966365 [shanty] shanty: Uninstallable due to removal of libgd-gd2-{,noxpm-}perl Provides in libgd-perl Bug reassigned from package 'shanty' to 'libgd-perl'. No longer marked as found in versions shanty/3-4. Ignorin

Bug#957099: marked as done (comskip: ftbfs with GCC-10)

Your message dated Wed, 29 Jul 2020 14:41:53 + with message-id and subject line Bug#957099: fixed in comskip 0.82.009+ds.1-2 has caused the Debian Bug report #957099, regarding comskip: ftbfs with GCC-10 to be marked as done. This means that you claim that the problem has been dealt with. If

Processed: Bug#966498 marked as pending in libgd-perl

Processing control commands: > tag -1 pending Bug #966498 [libgd-perl] libgd-perl: Dropped libgd-gd2-perl breaks a Recommends in lcov and prevents a clean upgrade Bug #966365 [libgd-perl] shanty: Uninstallable due to removal of libgd-gd2-{,noxpm-}perl Provides in libgd-perl Added tag(s) pending.

Processed (with 5 errors): Re: Bug#966498: libgd-perl: Dropped libgd-gd2-perl breaks a Recommends in lcov and prevents a clean upgrade

Processing control commands: > forcemerge -1 966365 Bug #966498 [libgd-perl] libgd-perl: Dropped libgd-gd2-perl breaks a Recommends in lcov and prevents a clean upgrade Unable to merge bugs because: package of #966365 is 'shanty' not 'libgd-perl' Failed to forcibly merge 966498: Did not alter mer

Bug#957700: marked as pending in postgresql-mysql-fdw

Control: tag -1 pending Hello, Bug #957700 in postgresql-mysql-fdw 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/postgresql/postgresql-mysql-fdw/-/commit/02b2

Processed: Bug#957700 marked as pending in postgresql-mysql-fdw

Processing control commands: > tag -1 pending Bug #957700 [src:postgresql-mysql-fdw] postgresql-mysql-fdw: ftbfs with GCC-10 Added tag(s) pending. -- 957700: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=957700 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#957815: marked as done (slony1-2: ftbfs with GCC-10)

Your message dated Wed, 29 Jul 2020 13:52:12 + with message-id and subject line Bug#957815: fixed in slony1-2 2.2.8-4 has caused the Debian Bug report #957815, regarding slony1-2: ftbfs with GCC-10 to be marked as done. This means that you claim that the problem has been dealt with. If this i

Bug#957815: marked as pending in slony1-2

Control: tag -1 pending Hello, Bug #957815 in slony1-2 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/postgresql/slony1-2/-/commit/c4759164a59c85eecab00e6abb73

Processed: Bug#957815 marked as pending in slony1-2

Processing control commands: > tag -1 pending Bug #957815 [src:slony1-2] slony1-2: ftbfs with GCC-10 Added tag(s) pending. -- 957815: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=957815 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#957627: marked as done (octave-optiminterp: ftbfs with GCC-10)

Your message dated Wed, 29 Jul 2020 13:20:04 + with message-id and subject line Bug#957627: fixed in octave-optiminterp 0.3.6-3 has caused the Debian Bug report #957627, regarding octave-optiminterp: ftbfs with GCC-10 to be marked as done. This means that you claim that the problem has been d

Processed: Bug#957627 marked as pending in octave-optiminterp

Processing control commands: > tag -1 pending Bug #957627 [src:octave-optiminterp] octave-optiminterp: ftbfs with GCC-10 Added tag(s) pending. -- 957627: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=957627 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#957627: marked as pending in octave-optiminterp

Control: tag -1 pending Hello, Bug #957627 in octave-optiminterp 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/pkg-octave-team/octave-optiminterp/-/commit/f8d

Bug#957289: gnss-sdr: ftbfs with GCC-10

Dear all, this should be fixed in https://mentors.debian.net/package/gnss-sdr/ The respective dsc file can be found at: https://mentors.debian.net/debian/pool/main/g/gnss-sdr/gnss-sdr_0.0.13-1.dsc

Bug#966501: 2.0.3 REST API regression: Failed to parse parameters for /v1.12/libpod/events: unexpected end of JSON input

Package: podman Version: 2.0.3+dfsg1-1 Severity: serious Tags: upsteam fixed-upstream Version 2.0.3 breaks the REST API really hard, which breaks cockpit-podman and any other API user. This is tracked here: https://github.com/containers/podman/issues/7078 This has been fixed upstream and will

Bug#966500: python3-notcurses: missing Breaks+Replaces: notcurses-bin (<< 1.6)

#thanks Thank you for filing my first Debian bug! How exciting, and at the same time embarrassing. I should have caught this before uploading. A fix is obvious, and I ought be able to accomplish it within the Debian packaging proper, rather than requiring a new release (I'm the upstream author).

Bug#966500: python3-notcurses: missing Breaks+Replaces: notcurses-bin (<< 1.6)

Package: python3-notcurses Version: 1.6.9+dfsg.1-2 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package fails to upgrade from 'testing'. It installed fine in 'testing', then the upgrade to 'sid' fails because it tries to over

Bug#957785: marked as done (see: ftbfs with GCC-10)

Your message dated Wed, 29 Jul 2020 11:33:55 + with message-id and subject line Bug#957785: fixed in see 0.72-7 has caused the Debian Bug report #957785, regarding see: 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 the c

Processed: Re: Bug#933031: pristine-tar: unable to unpack some deltas of version 2

Processing control commands: > tags -1 +patch Bug #933031 [pristine-tar] pristine-tar: unable to unpack some deltas of version 2 Added tag(s) patch. -- 933031: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=933031 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#933031: pristine-tar: unable to unpack some deltas of version 2

Control: tags -1 +patch On Tue, Jul 28, 2020 at 04:17:08PM +0100, Steve McIntyre wrote: >Control: severity -1 grave ... >IMHO this has to be a grave bug - without reimporting this repo we >can't get our older revisions back. Then I'm worried that this will >break things if we need to go back and

Bug#960680: marked as done (ruby-actionpack-page-caching: CVE-2020-8159)

Your message dated Wed, 29 Jul 2020 16:02:40 +0530 with message-id <1596018760.438...@onenetbeyond.org> and subject line close already fixed bug has caused the Debian Bug report #960680, regarding ruby-actionpack-page-caching: CVE-2020-8159 to be marked as done. This means that you claim that the

Processed: Re: gnss-sdr: ftbfs with GCC-10

Processing control commands: > tags -1 fixed-upstream Bug #957289 [src:gnss-sdr] gnss-sdr: ftbfs with GCC-10 Added tag(s) fixed-upstream. -- 957289: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=957289 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#957289: gnss-sdr: ftbfs with GCC-10

control: tags -1 fixed-upstream The new release is out, and might be fixing also this issue... I tried a build and resulted in https://github.com/gnss-sdr/gnss-sdr/issues/414 but this looks like more a gnuradio issue, not sure who is to blame... (even boost might be faulty) G. On Fri, 17 Apr

Processed: Re: [Aptitude-devel] Bug#966488: aptitude corrupts package install selection after dpkg error

Processing control commands: > severity -1 important Bug #966488 [aptitude] aptitude corrupts package install selection after dpkg error Severity set to 'important' from 'grave' -- 966488: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=966488 Debian Bug Tracking System Contact ow...@bugs.deb

Bug#945467: marked as done (fix build for python 3.8)

Your message dated Wed, 29 Jul 2020 09:55:03 + with message-id and subject line Bug#945467: fixed in veusz 3.2.1-1 has caused the Debian Bug report #945467, regarding fix build for python 3.8 to be marked as done. This means that you claim that the problem has been dealt with. If this is not

Bug#966488: [Aptitude-devel] Bug#966488: aptitude corrupts package install selection after dpkg error

Control: severity -1 important Dear Vincent, Vincent Lefevre wrote: > Severity: grave > Justification: causes non-serious data loss while I agree that this is "data loss" and that it's anything but "serious" (and serious is less than grave btw. ;-), I disagree that this validates the "grave" sev

Bug#957772: marked as done (saint: ftbfs with GCC-10)

Your message dated Wed, 29 Jul 2020 09:54:56 + with message-id and subject line Bug#957772: fixed in saint 2.5.0+dfsg-4 has caused the Debian Bug report #957772, regarding saint: 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#966488: aptitude corrupts package install selection after dpkg error

On 2020-07-29 11:06:16 +0200, Vincent Lefevre wrote: > An upgrade with aptitude failed due to a dpkg lock error (bug 95). > Then I noticed that not all packages were upgraded, so that I started > aptitude again to complete the upgrade. I typed 'g', but got: > > [1(1)/...] Actions: no changes >

Bug#966488: aptitude corrupts package install selection after dpkg error

Package: aptitude Version: 0.8.13-1+b1 Severity: grave Justification: causes non-serious data loss An upgrade with aptitude failed due to a dpkg lock error (bug 95). Then I noticed that not all packages were upgraded, so that I started aptitude again to complete the upgrade. I typed 'g', but g

Processed: reassign 964810 to libllvm7,libllvm9,libllvm10, forcibly merging 852746 964810, affects 852746

Processing commands for cont...@bugs.debian.org: > reassign 964810 libllvm7,libllvm9,libllvm10 Bug #964810 [libllvm10,libllvm9,libllvm7] gimp: Failure to start - GTK problem Bug reassigned from package 'libllvm10,libllvm9,libllvm7' to 'libllvm7,libllvm9,libllvm10'. Ignoring request to alter found

Bug#966483: iptables-netflow: sourcing of external scripts in dkms file?

Source: iptables-netflow Version: 2.5-2 Severity: serious tags: patch Hello, looks like your dkms ship file is sourcing external stuff with pushd/popd and so on. I don't think this is a sane idea, specially because in Debian we don't even use version.sh script to fill the dkms.conf file. Can yo

Processed: found 966409 in 1:1.5.1-2

Processing commands for cont...@bugs.debian.org: > found 966409 1:1.5.1-2 Bug #966409 [src:libjpeg-turbo] libjpeg-turbo: versions in debian/*.symbols files are missing the epochs Bug #966419 [src:libjpeg-turbo] libjpeg-turbo: versions in debian/*.symbols files are missing the epochs Marked as fo

Processed (with 2 errors): Re: Bug#964810: gimp: Unable to start gimp in debian unstable

Processing control commands: > reassign -1 libllvm10,libllvm9,libllvm7 Bug #964810 [gimp] gimp: Failure to start - GTK problem Bug reassigned from package 'gimp' to 'libllvm10,libllvm9,libllvm7'. No longer marked as found in versions gimp/2.10.18-1. Ignoring request to alter fixed versions of bug

Bug#964810: gimp: Unable to start gimp in debian unstable

Control: reassign -1 libllvm10,libllvm9,libllvm7 Control: forcemerge 852746 -1 Control: affects 852746 + gimp On Thu, 16 Jul 2020 at 12:26:26 -0300, zeden wrote: > $ gimp > : CommandLine Error: Option 'polly' registered more than once! > LLVM ERROR: inconsistency in registered CommandLine options

Bug#957230: Bug#966370: bsdmainutils: 12.1.3 removal of lorder breaks rdeps

On Mon, Jul 27, 2020 at 03:01:31PM +0100, Jessica Clarke wrote: > Package: bsdmainutils > Version: 12.1.3 > Severity: serious > Control: affects -1 src:freebsd-buildutils src:freebsd-glue src:freebsd-libs > > Hi, > The removal of lorder in 12.1.3 causes various freebsd-* packages to > FTBFS which

Processed: Re: Bug#962553: gffread: autopkgtest needs update for new version of gff2aplot: warning on stderr

Processing control commands: > reassign -1 src:gffread 0.11.8-1 Bug #962553 [src:gff2aplot] gffread: autopkgtest needs update for new version of gff2aplot: warning on stderr Bug reassigned from package 'src:gff2aplot' to 'src:gffread'. Ignoring request to alter found versions of bug #962553 to th

Processed: fixed 965317 in 3.36.4-1

Processing commands for cont...@bugs.debian.org: > fixed 965317 3.36.4-1 Bug #965317 {Done: debian-edid } [gnome-shell] gnome-shell: failed to write to XWayland Marked as fixed in versions gnome-shell/3.36.4-1. > thanks Stopping processing here. Please contact me if you need assistance. -- 9653

Bug#963290: e-antic: FTBFS: error: #error FLINT 2.5.2 or 2.5.3 required

Hello Lucas, thanks for the report. I am working on it. Jerome -- Jerome BENOIT | calculus+at-rezozer^dot*net https://qa.debian.org/developer.php?login=calcu...@rezozer.net AE28 AE15 710D FF1D 87E5 A762 3F92 19A6 7F36 C68B signature.asc Description: OpenPGP digital signature

Bug#966216: marked as done (libxrdesktop-0.15-0: missing Breaks+Replaces: libxrdesktop-0.14-0)

Your message dated Wed, 29 Jul 2020 07:49:19 + with message-id and subject line Bug#966216: fixed in xrdesktop 0.15.1-4 has caused the Debian Bug report #966216, regarding libxrdesktop-0.15-0: missing Breaks+Replaces: libxrdesktop-0.14-0 to be marked as done. This means that you claim that th

Bug#966479: sysdig: broken support on 32 bit kernels?

Source: sysdig Version: 0.26.7-2 Severity: serious Forwarded: https://github.com/draios/sysdig/issues/1669 Hello, I don't know if this happens also in Debian, but there is no reason for it not happening there. I asked upstream for help, this is what happens: CC [M] /var/lib/dkms/sysdig/0.26.7