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

2020-12-04 Thread Graham Inggs
Hi tony On Sat, 5 Dec 2020 at 01:25, tony mancill wrote: > I'd like to kick the debci job again to confirm > before I mark the bug as closed in 0.12.1-1, but I don't know how to do > that. You can retry the migration tests from gffread's tracker page [1], by clicking on the recycle icon next to

Bug#976366: Upgrade to 247 broke keyboard input on Wayland session

2020-12-04 Thread duck
Quack, On 2020-12-05 05:00, Michael Biebl wrote: hidepid is known to cause problems and no longer a supported configuration: https://www.debian.org/releases/stable/amd64/release-notes/ch-information.de.html#hidepid-unsupported Thanks for pointing this out, I did not know it was officially u

Bug#976436: octave-ltfat-common,octave-ltfat: both ship /usr/share/octave/packages/ltfat-2.3.1/*

2020-12-04 Thread Andreas Beckmann
Package: octave-ltfat-common,octave-ltfat Version: 2.3.1+dfsg-5 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package failed to install because it tries to overwrite other packages files. >From the attached log (scroll to the

Bug#976430: libfreecad-python3-0.19: missing Breaks+Replaces: libfreecad-python3-0.18

2020-12-04 Thread Andreas Beckmann
Package: libfreecad-python3-0.19 Version: 0.19~pre1+git20201123.8d73c8f0+dfsg1-1 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package fails to upgrade from 'sid' to 'experimental'. It installed fine in 'sid', then the upgrade

Bug#976429: jellyfish: missing Breaks+Replaces: jellyfish-examples (<< 2.3.0-7)

2020-12-04 Thread Andreas Beckmann
Package: jellyfish Version: 2.3.0-7 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 overwrite other pac

Bug#974075: ugene: FTBFS with Qt 5.15

2020-12-04 Thread tony mancill
On Fri, Dec 04, 2020 at 11:01:59PM +0100, Andreas Tille wrote: > On Fri, Dec 04, 2020 at 12:52:07PM -0800, tony mancill wrote: > > Hi Debian-Med, hi Steffen: > > > > I grabbed this bug to fix the QPainterPath include and noticed that > > packaging of 36.0 is underway on the master branch. I have

Processed: Bug#974075 marked as pending in ugene

2020-12-04 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #974075 [ugene] ugene: FTBFS with Qt 5.15 Added tag(s) pending. -- 974075: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=974075 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#974075: marked as pending in ugene

2020-12-04 Thread Tony Mancill
Control: tag -1 pending Hello, Bug #974075 in ugene reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/med-team/ugene/-/commit/881f164d418273d96755161b666a06b163fb

Bug#974168: [Debian-med-packaging] Bug#974168: Bug #974168: bioperl-run: autopkgtest issue fixed, now different build time error

2020-12-04 Thread Étienne Mollier
Hi again, I pushed a couple of changes on salsa[0] to unlock the situation with BEDtools integration in bioperl-run. Now the vast majority of tests are passing. :) [0] https://salsa.debian.org/med-team/bioperl-run One of the datasets in use by the bedtools related functions is not available in

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

2020-12-04 Thread tony mancill
On Wed, Jul 29, 2020 at 09:58:55AM +0200, Graham Inggs wrote: > Control: reassign -1 src:gffread 0.11.8-1 > Control: severity -1 serious > Control: tags -1 - moreinfo unreproducible > > Hi > > gff2aplot 2.0-13 migrated to testing and now causes gffread's > autopkgtests to fail there [1]. > I'm re

Bug#948244: aseprite is not in stable

2020-12-04 Thread Phil Morrell
Ah, I'm glad this has been reported already, because I was very confused by this other example: https://tracker.debian.org/pkg/aseprite oldstable: 1.0.5+ds-2 stable: 1.1.6+ds-1 aseprite | 1.0.5+ds-2| oldoldstable | source aseprite | 1.1.6+ds-1| oldstable| source sig

Bug#975161: marked as done (zint: FTBFS: qzint.cpp:374:26: error: aggregate ‘QPainterPath pt’ has incomplete type and cannot be defined)

2020-12-04 Thread Debian Bug Tracking System
Your message dated Fri, 04 Dec 2020 23:21:10 + with message-id and subject line Bug#975161: fixed in zint 2.9.1-1 has caused the Debian Bug report #975161, regarding zint: FTBFS: qzint.cpp:374:26: error: aggregate ‘QPainterPath pt’ has incomplete type and cannot be defined to be marked as don

Bug#976424: vtk6: FTBFS in sid

2020-12-04 Thread Gianfranco Costamagna
Source: vtk6 Version: 6.3.0+dfsg2-5 Severity: serious tags: patch Hello, looks like vtk6 started FTBFS in sid, not sure if this is just a matter of including QtPainterPath or something else is needed This patch seems to fix the issue, however, vtk7 and vtk9 have the very same code and they look

Bug#934167: #934167: workaround for buster users

2020-12-04 Thread Robert McQueen
I was facing the error described at https://github.com/cweiske/grauphel/issues/72#issuecomment-519173520 In case anyone finds themselves here, and is running Debian buster, I was able to fix relatively easily. The latest version of php-oauth in bullseye (currently 2.0.5+1.2.3- 1+b1) depends on PH

Bug#974168: Bug#974168: Bug #974168: bioperl-run: autopkgtest issue fixed, now different build time error

2020-12-04 Thread Andreas Tille
Hi Étienne, On Fri, Dec 04, 2020 at 09:56:20PM +0100, Étienne Mollier wrote: > I think I'm on a trail with bioperl-run, and could fix a couple > of issues already. I'm however unsure it might make it for the > 4th of the advent calendar: fixing the initial issue pulls in > gradually more tests, w

Bug#925638: closed by Debian FTP Masters (reply to Bernhard Schmidt ) (Bug#925638: fixed in belle-sip 4.3.1+dfsg-1)

2020-12-04 Thread Bernhard Schmidt
Hi, Am 04.12.20 um 19:23 schrieb Bernhard Schmidt: > Dear Mika, > >> belle-sip is currently missing in Debian/testing AKA bullseye >> because of this issue (which is only fixed in experimental yet): >> >> | Migration status for belle-sip (- to 1.6.3-5): BLOCKED: Rejected/violates >> migration p

Bug#957107: marked as done (crashmail: ftbfs with GCC-10)

2020-12-04 Thread Debian Bug Tracking System
Your message dated Fri, 04 Dec 2020 22:21:04 + with message-id and subject line Bug#957107: fixed in crashmail 1.7-1.1 has caused the Debian Bug report #957107, regarding crashmail: ftbfs with GCC-10 to be marked as done. This means that you claim that the problem has been dealt with. If this

Processed: closing 971562

2020-12-04 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > close 971562 Bug #971562 [src:gall] gall: libgit2 1.0 transition Marked Bug as done > thanks Stopping processing here. Please contact me if you need assistance. -- 971562: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=971562 Debian Bug Track

Processed: closing 971568

2020-12-04 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > close 971568 Bug #971568 [geany-plugins] geany-plugins: libgit2 1.0 transition Marked Bug as done > thanks Stopping processing here. Please contact me if you need assistance. -- 971568: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=971568 De

Processed: severity of 976233 is serious

2020-12-04 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > severity 976233 serious Bug #976233 [src:ghdl] ghdl FTBFS with LLVM 11 as default Severity set to 'serious' from 'important' > thanks Stopping processing here. Please contact me if you need assistance. -- 976233: https://bugs.debian.org/cgi-bin/

Bug#974075: ugene: FTBFS with Qt 5.15

2020-12-04 Thread Andreas Tille
Hi Tony, On Fri, Dec 04, 2020 at 12:52:07PM -0800, tony mancill wrote: > Hi Debian-Med, hi Steffen: > > I grabbed this bug to fix the QPainterPath include and noticed that > packaging of 36.0 is underway on the master branch. I have updated the > debian/patches to apply against this new upstream

Bug#946492: marked as done (vdjtools: broken symlink: /usr/share/java/vdjtools.jar -> vdjtools-1.2.1+git20190311.jar)

2020-12-04 Thread Debian Bug Tracking System
Your message dated Fri, 04 Dec 2020 21:55:10 + with message-id and subject line Bug#946492: fixed in vdjtools 1.2.1+git20190311-2 has caused the Debian Bug report #946492, regarding vdjtools: broken symlink: /usr/share/java/vdjtools.jar -> vdjtools-1.2.1+git20190311.jar to be marked as done.

Bug#974584: marked as done (inspectrum FTBFS: error: aggregate ‘QPainterPath path’ has incomplete type and cannot be defined)

2020-12-04 Thread Debian Bug Tracking System
Your message dated Fri, 04 Dec 2020 21:52:29 + with message-id and subject line Bug#974584: fixed in inspectrum 0.2.3-1 has caused the Debian Bug report #974584, regarding inspectrum FTBFS: error: aggregate ‘QPainterPath path’ has incomplete type and cannot be defined to be marked as done. T

Processed: The FTBFS is reproducable by me.

2020-12-04 Thread Debian Bug Tracking System
Processing control commands: > tags -1 confirmed Bug #975833 [src:radvd] radvd: FTBFS: dh_install: error: missing files, aborting Added tag(s) confirmed. -- 975833: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=975833 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#975833: The FTBFS is reproducable by me.

2020-12-04 Thread Geert Stappers
Control: tags -1 confirmed Now reproducable by me Regards Geert Stappers No time to find out why my build was succesfull. -- Silence is hard to parse

Bug#957251: marked as done (gamgi: ftbfs with GCC-10)

2020-12-04 Thread Debian Bug Tracking System
Your message dated Fri, 04 Dec 2020 21:51:02 + with message-id and subject line Bug#957251: fixed in gamgi 0.17.3-3 has caused the Debian Bug report #957251, regarding gamgi: 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#973143: marked as done (cstore-fdw: FTBFS: diff in generated debian/control)

2020-12-04 Thread Debian Bug Tracking System
Your message dated Fri, 04 Dec 2020 21:49:47 + with message-id and subject line Bug#976384: Removed package(s) from unstable has caused the Debian Bug report #973143, regarding cstore-fdw: FTBFS: diff in generated debian/control to be marked as done. This means that you claim that the problem

Bug#976280: marked as done (ruby-azure-storage: ftbfs with ruby-faraday 1.0)

2020-12-04 Thread Debian Bug Tracking System
Your message dated Fri, 04 Dec 2020 21:49:02 + with message-id and subject line Bug#976281: Removed package(s) from unstable has caused the Debian Bug report #976280, regarding ruby-azure-storage: ftbfs with ruby-faraday 1.0 to be marked as done. This means that you claim that the problem has

Bug#976279: marked as done (ruby-azure-core: ftbfs with ruby-faraday 1.0)

2020-12-04 Thread Debian Bug Tracking System
Your message dated Fri, 04 Dec 2020 21:49:17 + with message-id and subject line Bug#976282: Removed package(s) from unstable has caused the Debian Bug report #976279, regarding ruby-azure-core: ftbfs with ruby-faraday 1.0 to be marked as done. This means that you claim that the problem has be

Bug#974583: marked as done (jerry FTFBS: error: aggregate ‘QPainterPath path’ has incomplete type and cannot be defined)

2020-12-04 Thread Debian Bug Tracking System
Your message dated Fri, 04 Dec 2020 21:48:40 + with message-id and subject line Bug#976234: Removed package(s) from unstable has caused the Debian Bug report #974583, regarding jerry FTFBS: error: aggregate ‘QPainterPath path’ has incomplete type and cannot be defined to be marked as done. T

Bug#958403: marked as done (node-cross-spawn: unneeded for Debian, does risky path mangling, and does it wrong in current release 5.1.0)

2020-12-04 Thread Debian Bug Tracking System
Your message dated Fri, 04 Dec 2020 21:47:32 + with message-id and subject line Bug#975942: Removed package(s) from unstable has caused the Debian Bug report #958403, regarding node-cross-spawn: unneeded for Debian, does risky path mangling, and does it wrong in current release 5.1.0 to be ma

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

2020-12-04 Thread Debian Bug Tracking System
Your message dated Fri, 04 Dec 2020 21:46:48 + with message-id and subject line Bug#975564: Removed package(s) from unstable has caused the Debian Bug report #966970, regarding piexif: FTBFS: dh_auto_test: error: pybuild --test -i python{version} -p 3.8 returned exit code 13 to be marked as d

Bug#957411: marked as done (knocker: ftbfs with GCC-10)

2020-12-04 Thread Debian Bug Tracking System
Your message dated Fri, 04 Dec 2020 21:46:25 + with message-id and subject line Bug#975403: Removed package(s) from unstable has caused the Debian Bug report #957411, regarding knocker: ftbfs with GCC-10 to be marked as done. This means that you claim that the problem has been dealt with. If

Bug#966767: marked as done (oidua: Unversioned Python removal in sid/bullseye)

2020-12-04 Thread Debian Bug Tracking System
Your message dated Fri, 04 Dec 2020 21:45:28 + with message-id and subject line Bug#975264: Removed package(s) from unstable has caused the Debian Bug report #943136, regarding oidua: Unversioned Python removal in sid/bullseye to be marked as done. This means that you claim that the problem h

Bug#975645: marked as done (fprint-demo, depends and build-depends on cruft packages.)

2020-12-04 Thread Debian Bug Tracking System
Your message dated Fri, 04 Dec 2020 21:43:50 + with message-id and subject line Bug#974855: Removed package(s) from unstable has caused the Debian Bug report #975645, regarding fprint-demo, depends and build-depends on cruft packages. to be marked as done. This means that you claim that the p

Bug#974016: marked as done (mrs: FTBFS with libzeep-dev 5.0.0-1: "Checking for libzeep...libzeep is not installed")

2020-12-04 Thread Debian Bug Tracking System
Your message dated Fri, 04 Dec 2020 21:44:15 + with message-id and subject line Bug#974895: Removed package(s) from unstable has caused the Debian Bug report #974016, regarding mrs: FTBFS with libzeep-dev 5.0.0-1: "Checking for libzeep...libzeep is not installed" to be marked as done. This m

Bug#943136: marked as done (oidua: Python2 removal in sid/bullseye)

2020-12-04 Thread Debian Bug Tracking System
Your message dated Fri, 04 Dec 2020 21:45:28 + with message-id and subject line Bug#975264: Removed package(s) from unstable has caused the Debian Bug report #943136, regarding oidua: Python2 removal in sid/bullseye to be marked as done. This means that you claim that the problem has been dea

Bug#973090: marked as done (python3-antlr3: FTBFS: make[1]: pyversions: No such file or directory)

2020-12-04 Thread Debian Bug Tracking System
Your message dated Fri, 04 Dec 2020 21:42:38 + with message-id and subject line Bug#974434: Removed package(s) from unstable has caused the Debian Bug report #973090, regarding python3-antlr3: FTBFS: make[1]: pyversions: No such file or directory to be marked as done. This means that you clai

Bug#860483: marked as done ([node-minimalistic-assert] Could be replaced by node-assert)

2020-12-04 Thread Debian Bug Tracking System
Your message dated Fri, 04 Dec 2020 21:44:29 + with message-id and subject line Bug#974906: Removed package(s) from unstable has caused the Debian Bug report #860483, regarding [node-minimalistic-assert] Could be replaced by node-assert to be marked as done. This means that you claim that the

Bug#937387: marked as done (py-asterisk: Python2 removal in sid/bullseye)

2020-12-04 Thread Debian Bug Tracking System
Your message dated Fri, 04 Dec 2020 21:45:14 + with message-id and subject line Bug#975263: Removed package(s) from unstable has caused the Debian Bug report #937387, regarding py-asterisk: Python2 removal in sid/bullseye to be marked as done. This means that you claim that the problem has be

Bug#973629: marked as done (golang-gopkg-alecthomas-kingpin.v3-dev: missing Breaks+Replaces: golang-gopkg-alecthomas-kingpin.v2-dev)

2020-12-04 Thread Debian Bug Tracking System
Your message dated Fri, 04 Dec 2020 21:38:58 + with message-id and subject line Bug#974041: Removed package(s) from unstable has caused the Debian Bug report #973629, regarding golang-gopkg-alecthomas-kingpin.v3-dev: missing Breaks+Replaces: golang-gopkg-alecthomas-kingpin.v2-dev to be marked

Bug#973229: marked as done (golang-gopkg-alecthomas-kingpin.v3: FTBFS: src/gopkg.in/alecthomas/kingpin.v3/i18n_init.go:13:2: cannot find package "github.com/nicksnyder/go-i18n/i18n")

2020-12-04 Thread Debian Bug Tracking System
Your message dated Fri, 04 Dec 2020 21:38:58 + with message-id and subject line Bug#974041: Removed package(s) from unstable has caused the Debian Bug report #973229, regarding golang-gopkg-alecthomas-kingpin.v3: FTBFS: src/gopkg.in/alecthomas/kingpin.v3/i18n_init.go:13:2: cannot find package

Bug#973385: marked as done (CVE-2020-27739 CVE-2020-27740 CVE-2020-27741 CVE-2020-27742)

2020-12-04 Thread Debian Bug Tracking System
Your message dated Fri, 04 Dec 2020 21:40:27 + with message-id and subject line Bug#974151: Removed package(s) from unstable has caused the Debian Bug report #973385, regarding CVE-2020-27739 CVE-2020-27740 CVE-2020-27741 CVE-2020-27742 to be marked as done. This means that you claim that the

Bug#974168: [Debian-med-packaging] Bug#974168: Bug #974168: bioperl-run: autopkgtest issue fixed, now different build time error

2020-12-04 Thread Étienne Mollier
Hi Andreas, I think I'm on a trail with bioperl-run, and could fix a couple of issues already. I'm however unsure it might make it for the 4th of the advent calendar: fixing the initial issue pulls in gradually more tests, which in turn may fail to run for all sorts of reasons. Kind Regards, --

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

2020-12-04 Thread Debian Bug Tracking System
Your message dated Fri, 04 Dec 2020 21:39:44 + with message-id and subject line Bug#974081: Removed package(s) from unstable has caused the Debian Bug report #973194, regarding ldif3: FTBFS: dh_auto_test: error: pybuild --test --test-nose -i python{version} -p "3.9 3.8" returned exit code 13

Bug#971187: marked as done (haskell-ncurses: FTBFS: Cannot find a definition for `KEY_EVENT' in the header file.)

2020-12-04 Thread Debian Bug Tracking System
Your message dated Fri, 04 Dec 2020 21:36:24 + with message-id and subject line Bug#971267: Removed package(s) from unstable has caused the Debian Bug report #971187, regarding haskell-ncurses: FTBFS: Cannot find a definition for `KEY_EVENT' in the header file. to be marked as done. This mea

Bug#969839: marked as done (rust-failure: type confusion when downcasting, which is an undefined behavior)

2020-12-04 Thread Debian Bug Tracking System
Your message dated Fri, 04 Dec 2020 21:37:21 + with message-id and subject line Bug#973298: Removed package(s) from unstable has caused the Debian Bug report #969839, regarding rust-failure: type confusion when downcasting, which is an undefined behavior to be marked as done. This means that

Bug#964823: marked as done (haskell-ghc-syb-utils: FTBFS with GHC 8.8)

2020-12-04 Thread Debian Bug Tracking System
Your message dated Fri, 04 Dec 2020 21:35:24 + with message-id and subject line Bug#966708: Removed package(s) from unstable has caused the Debian Bug report #964823, regarding haskell-ghc-syb-utils: FTBFS with GHC 8.8 to be marked as done. This means that you claim that the problem has been

Bug#964827: marked as done (haskell-vector-space-points: BD-Uninstallable)

2020-12-04 Thread Debian Bug Tracking System
Your message dated Fri, 04 Dec 2020 21:35:44 + with message-id and subject line Bug#966711: Removed package(s) from unstable has caused the Debian Bug report #964827, regarding haskell-vector-space-points: BD-Uninstallable to be marked as done. This means that you claim that the problem has b

Bug#974584: inspectrum FTBFS: error: aggregate ‘QPainterPath path’ has incomplete type and cannot be defined

2020-12-04 Thread tony mancill
On Fri, Dec 04, 2020 at 05:36:29PM +0100, Christoph Berg wrote: > Control: tags -1 fixed-upstream > Control: forwarded -1 > https://github.com/miek/inspectrum/commit/1f2b4587ec2c6d1a1945eee8bbf361dbdf3dc8af > > Re: Helmut Grohne > > | /<>/traceplot.cpp:120:18: error: aggregate ‘QPainterPath > >

Bug#964689: marked as done (haskell-permutation: FTBFS: Setup.lhs:14:11: error: Not in scope: ‘runTests’)

2020-12-04 Thread Debian Bug Tracking System
Your message dated Fri, 04 Dec 2020 21:32:11 + with message-id and subject line Bug#962970: Removed package(s) from unstable has caused the Debian Bug report #964689, regarding haskell-permutation: FTBFS: Setup.lhs:14:11: error: Not in scope: ‘runTests’ to be marked as done. This means that

Bug#976198: marked as done (FTBFS on i386: Build killed with signal TERM after 150 minutes of inactivity)

2020-12-04 Thread Debian Bug Tracking System
Your message dated Fri, 04 Dec 2020 21:30:22 + with message-id and subject line Bug#976198: fixed in octave-image 2.12.0-7 has caused the Debian Bug report #976198, regarding FTBFS on i386: Build killed with signal TERM after 150 minutes of inactivity to be marked as done. This means that yo

Bug#964676: marked as done (haskell-bytestring-show: FTBFS: Setup.lhs:5:50: error: Not in scope: ‘runTests’)

2020-12-04 Thread Debian Bug Tracking System
Your message dated Fri, 04 Dec 2020 21:28:31 + with message-id and subject line Bug#962890: Removed package(s) from unstable has caused the Debian Bug report #964676, regarding haskell-bytestring-show: FTBFS: Setup.lhs:5:50: error: Not in scope: ‘runTests’ to be marked as done. This means th

Bug#976409: glibc breaks node-iconv autopkgtest: AssertionError [ERR_ASSERTION]: Missing expected exception

2020-12-04 Thread Aurelien Jarno
On 2020-12-04 21:54, Aurelien Jarno wrote: > On 2020-12-04 21:38, Xavier wrote: > > Control: tags -1 + ftbfs > > > > Le 04/12/2020 à 20:46, Paul Gevers a écrit : > > > Source: glibc, node-iconv > > > Control: found -1 glibc/2.31-5 > > > Control: found -1 node-iconv/2.3.5-4 > > > Severity: serious

Processed: tagging 951891

2020-12-04 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > tags 951891 - help Bug #951891 [src:open-ath9k-htc-firmware] open-ath9k-htc-firmware FTBFS with binutils 2.34 Removed tag(s) help. > thanks Stopping processing here. Please contact me if you need assistance. -- 951891: https://bugs.debian.org/c

Bug#970878: ghostscript breaks doc-rfc autopkgtest: segmentation fault

2020-12-04 Thread Paul Gevers
Hi Jonas, On Fri, 23 Oct 2020 12:07:27 +0200 Jonas Smedegaard wrote: > > Of course, I'm biased since I'm the maintainer of doc-rfc, but I think > > it's a fair assesment. > > For the record it is not a PDF file but a (quite large and allegedly) > PostScript file that causes Ghostscript to segf

Processed: src:liquidsoap: fails to migrate to testing for too long: FTBFS on armel, and mips(64)el

2020-12-04 Thread Debian Bug Tracking System
Processing control commands: > close -1 1.4.3-1 Bug #976419 [src:liquidsoap] src:liquidsoap: fails to migrate to testing for too long: FTBFS on armel, and mips(64)el Marked as fixed in versions liquidsoap/1.4.3-1. Bug #976419 [src:liquidsoap] src:liquidsoap: fails to migrate to testing for too l

Processed: tagging 971565

2020-12-04 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > tags 971565 + ftbfs Bug #971565 [ruby-rugged] ruby-rugged: libgit2 1.0 transition Added tag(s) ftbfs. > thanks Stopping processing here. Please contact me if you need assistance. -- 971565: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=97156

Bug#976419: src:liquidsoap: fails to migrate to testing for too long: FTBFS on armel, and mips(64)el

2020-12-04 Thread Paul Gevers
Source: liquidsoap Version: 1.4.2-1 Severity: serious Control: close -1 1.4.3-1 Tags: sid bullseye User: release.debian@packages.debian.org Usertags: out-of-sync Control: block -1 by 972272 976355 Dear maintainer(s), As recently announced [1], the Release Team now considers packages that are

Processed: tagging 971563

2020-12-04 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > tags 971563 + ftbfs Bug #971563 [src:libgit2-glib] libgit2-glib: libgit2 1.0 transition Added tag(s) ftbfs. > thanks Stopping processing here. Please contact me if you need assistance. -- 971563: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug

Processed: Re: Bug#976310: marked as pending in node-css-loader

2020-12-04 Thread Debian Bug Tracking System
Processing control commands: > reopen -1 Bug #976310 {Done: Xavier Guimard } [gitlab] node-compression-webpack-plugin: TypeError: (0 , _schemaUtils.validate) is not a function 'reopen' may be inappropriate when a bug has been closed with a version; all fixed versions will be cleared, and you may

Bug#975129: qwt: FTBFS: qwt_painter_command.h:85:22: error: field ‘clipPath’ has incomplete type ‘QPainterPath’

2020-12-04 Thread tony mancill
On Wed, Nov 25, 2020 at 08:35:48AM +0100, Gudjon I. Gudjonsson wrote: > This requires a quite simple fix. I will fix this before the weekend and then > start looking into version 6.1.5. Hi Gudjon, Do you mind if I upload an NMU of 6.1.4 for the simple fix? There are a number of r-deps that are

Bug#976310: marked as pending in node-css-loader

2020-12-04 Thread Pirate Praveen
Control: reopen -1 On Fri, Dec 4, 2020 at 19:52, Xavier Guimard wrote: Control: tag -1 pending Hello, Bug #976310 in node-css-loader 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: src:imbalanced-learn: fails to migrate to testing for too long: autopkgtest regression

2020-12-04 Thread Debian Bug Tracking System
Processing control commands: > block -1 by 974088 Bug #976417 [src:imbalanced-learn] src:imbalanced-learn: fails to migrate to testing for too long: autopkgtest regression 976417 was not blocked by any bugs. 976417 was not blocking any bugs. Added blocking bug(s) of 976417: 974088 -- 976417: ht

Bug#976417: src:imbalanced-learn: fails to migrate to testing for too long: autopkgtest regression

2020-12-04 Thread Paul Gevers
Source: imbalanced-learn Version: 0.7.0-4 Severity: serious Tags: sid bullseye User: release.debian@packages.debian.org Usertags: out-of-sync Control: block -1 by 974088 Dear maintainer(s), As recently announced [1], the Release Team now considers packages that are out-of-sync between testing

Bug#976393: marked as done (texlive-latex-base-doc: file conflict with texlive-latex-recommended-doc: /usr/share/doc/texlive-doc/latex/l3packages/CHANGELOG.md)

2020-12-04 Thread Debian Bug Tracking System
Your message dated Fri, 04 Dec 2020 20:57:45 + with message-id and subject line Bug#976393: fixed in texlive-base 2020.20201203-2 has caused the Debian Bug report #976393, regarding texlive-latex-base-doc: file conflict with texlive-latex-recommended-doc: /usr/share/doc/texlive-doc/latex/l3p

Bug#976409: glibc breaks node-iconv autopkgtest: AssertionError [ERR_ASSERTION]: Missing expected exception

2020-12-04 Thread Aurelien Jarno
On 2020-12-04 21:38, Xavier wrote: > Control: tags -1 + ftbfs > > Le 04/12/2020 à 20:46, Paul Gevers a écrit : > > Source: glibc, node-iconv > > Control: found -1 glibc/2.31-5 > > Control: found -1 node-iconv/2.3.5-4 > > Severity: serious > > Tags: sid bullseye > > X-Debbugs-CC: debian...@lists.de

Bug#976310: marked as done (node-compression-webpack-plugin: TypeError: (0 , _schemaUtils.validate) is not a function)

2020-12-04 Thread Debian Bug Tracking System
Your message dated Fri, 04 Dec 2020 20:55:33 + with message-id and subject line Bug#976310: fixed in node-css-loader 3.2.1+~cs14.0.5-3 has caused the Debian Bug report #976310, regarding node-compression-webpack-plugin: TypeError: (0 , _schemaUtils.validate) is not a function to be marked as

Bug#976198: marked as pending in octave-image

2020-12-04 Thread Rafael Laboissiere
Control: tag -1 pending Hello, Bug #976198 in octave-image 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-image/-/commit/30c72bef7fa4a3b

Processed: Bug#976198 marked as pending in octave-image

2020-12-04 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #976198 [src:octave-image] FTBFS on i386: Build killed with signal TERM after 150 minutes of inactivity Added tag(s) pending. -- 976198: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=976198 Debian Bug Tracking System Contact ow...@bugs.debia

Bug#974075: ugene: FTBFS with Qt 5.15

2020-12-04 Thread tony mancill
On Mon, Nov 09, 2020 at 05:52:43PM +0100, Andreas Beckmann wrote: > Package: ugene > Version: 34.0+dfsg-1 > Severity: serious > Tags: ftbfs > Justification: fails to build from source Hi Debian-Med, hi Steffen: I grabbed this bug to fix the QPainterPath include and noticed that packaging of 36.0

Bug#819641: marked as done (golang-github-jinzhu-gorm: FTBFS: FAIL: TestScannableSlices (0.00s))

2020-12-04 Thread Debian Bug Tracking System
Your message dated Fri, 04 Dec 2020 20:48:14 + with message-id and subject line Bug#819641: fixed in golang-github-jinzhu-gorm 1.9.6-1 has caused the Debian Bug report #819641, regarding golang-github-jinzhu-gorm: FTBFS: FAIL: TestScannableSlices (0.00s) to be marked as done. This means that

Processed: Re: glibc breaks node-iconv autopkgtest: AssertionError [ERR_ASSERTION]: Missing expected exception

2020-12-04 Thread Debian Bug Tracking System
Processing control commands: > tags -1 + ftbfs Bug #976409 [src:glibc, src:node-iconv] glibc breaks node-iconv autopkgtest: AssertionError [ERR_ASSERTION]: Missing expected exception Added tag(s) ftbfs. -- 976409: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=976409 Debian Bug Tracking Syst

Bug#976409: glibc breaks node-iconv autopkgtest: AssertionError [ERR_ASSERTION]: Missing expected exception

2020-12-04 Thread Xavier
Control: tags -1 + ftbfs Le 04/12/2020 à 20:46, Paul Gevers a écrit : > Source: glibc, node-iconv > Control: found -1 glibc/2.31-5 > Control: found -1 node-iconv/2.3.5-4 > Severity: serious > Tags: sid bullseye > X-Debbugs-CC: debian...@lists.debian.org > User: debian...@lists.debian.org > Usertag

Processed: reassign 976410 to libpod

2020-12-04 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > reassign 976410 libpod Bug #976410 [src:glibc, src:libpod] glibc breaks libpod autopkgtest: dh_auto_build: error: cd _output && go install -trimpath ... Bug reassigned from package 'src:glibc, src:libpod' to 'libpod'. No longer marked as found in

Bug#976410: glibc breaks libpod autopkgtest: dh_auto_build: error: cd _output && go install -trimpath ...

2020-12-04 Thread Aurelien Jarno
control: reassign libpod/2.0.6+dfsg1-2 On 2020-12-04 20:50, Paul Gevers wrote: > Source: glibc, libpod > Control: found -1 glibc/2.31-5 > Control: found -1 libpod/2.0.6+dfsg1-2 > Severity: serious > Tags: sid bullseye > X-Debbugs-CC: debian...@lists.debian.org > User: debian...@lists.debian.org >

Processed: owner 974075

2020-12-04 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > owner 974075 tmanc...@debian.org Bug #974075 [ugene] ugene: FTBFS with Qt 5.15 Owner recorded as tmanc...@debian.org. > thanks Stopping processing here. Please contact me if you need assistance. -- 974075: https://bugs.debian.org/cgi-bin/bugrepo

Processed: fixed 971568 in 1.37+dfsg-3

2020-12-04 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > notfound 971568 1.37+dfsg-3 Bug #971568 [geany-plugins] geany-plugins: libgit2 1.0 transition No longer marked as found in versions geany-plugins/1.37+dfsg-3. > thanks Stopping processing here. Please contact me if you need assistance. -- 971568

Bug#976366: Upgrade to 247 broke keyboard input on Wayland session

2020-12-04 Thread Michael Biebl
Am 04.12.2020 um 11:56 schrieb Marc Dequènes (duck): On 2020-12-04 17:04, Michael Biebl wrote: Is policykit-1 installed and working? I dug a little bit more on this front and I am affected by this:   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=860040 which then made the polkit agent qu

Processed: Bug#976310 marked as pending in node-css-loader

2020-12-04 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #976310 [gitlab] node-compression-webpack-plugin: TypeError: (0 , _schemaUtils.validate) is not a function Added tag(s) pending. -- 976310: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=976310 Debian Bug Tracking System Contact ow...@bugs.de

Bug#976310: marked as pending in node-css-loader

2020-12-04 Thread Xavier Guimard
Control: tag -1 pending Hello, Bug #976310 in node-css-loader 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/js-team/node-css-loader/-/commit/130e5ef8425bb78f3

Processed: fixed 971568 in 1.37+dfsg-3

2020-12-04 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > fixed 971568 1.37+dfsg-3 Bug #971568 [geany-plugins] geany-plugins: libgit2 1.0 transition Marked as fixed in versions geany-plugins/1.37+dfsg-3. > thanks Stopping processing here. Please contact me if you need assistance. -- 971568: https://bug

Bug#976410: glibc breaks libpod autopkgtest: dh_auto_build: error: cd _output && go install -trimpath ...

2020-12-04 Thread Paul Gevers
Source: glibc, libpod Control: found -1 glibc/2.31-5 Control: found -1 libpod/2.0.6+dfsg1-2 Severity: serious Tags: sid bullseye X-Debbugs-CC: debian...@lists.debian.org User: debian...@lists.debian.org Usertags: breaks needs-update Dear maintainer(s), With a recent upload of glibc the autopkgtes

Bug#969074: marked as done (libiscsi FTBFS with gcc 10)

2020-12-04 Thread Debian Bug Tracking System
Your message dated Fri, 04 Dec 2020 19:50:09 + with message-id and subject line Bug#969074: fixed in libiscsi 1.19.0-3 has caused the Debian Bug report #969074, regarding libiscsi FTBFS with gcc 10 to be marked as done. This means that you claim that the problem has been dealt with. If this i

Processed: glibc breaks libpod autopkgtest: dh_auto_build: error: cd _output && go install -trimpath ...

2020-12-04 Thread Debian Bug Tracking System
Processing control commands: > found -1 glibc/2.31-5 Bug #976410 [src:glibc, src:libpod] glibc breaks libpod autopkgtest: dh_auto_build: error: cd _output && go install -trimpath ... Marked as found in versions glibc/2.31-5. > found -1 libpod/2.0.6+dfsg1-2 Bug #976410 [src:glibc, src:libpod] glib

Bug#976409: glibc breaks node-iconv autopkgtest: AssertionError [ERR_ASSERTION]: Missing expected exception

2020-12-04 Thread Paul Gevers
Source: glibc, node-iconv Control: found -1 glibc/2.31-5 Control: found -1 node-iconv/2.3.5-4 Severity: serious Tags: sid bullseye X-Debbugs-CC: debian...@lists.debian.org User: debian...@lists.debian.org Usertags: breaks needs-update Dear maintainer(s), With a recent upload of glibc the autopkgt

Processed: glibc breaks node-iconv autopkgtest: AssertionError [ERR_ASSERTION]: Missing expected exception

2020-12-04 Thread Debian Bug Tracking System
Processing control commands: > found -1 glibc/2.31-5 Bug #976409 [src:glibc, src:node-iconv] glibc breaks node-iconv autopkgtest: AssertionError [ERR_ASSERTION]: Missing expected exception Marked as found in versions glibc/2.31-5. > found -1 node-iconv/2.3.5-4 Bug #976409 [src:glibc, src:node-ico

Bug#971564: marked as done (python-pygit2: libgit2 1.0 transition)

2020-12-04 Thread Debian Bug Tracking System
Your message dated Fri, 04 Dec 2020 19:33:57 + with message-id and subject line Bug#971564: fixed in python-pygit2 1.3.0+dfsg1-2 has caused the Debian Bug report #971564, regarding python-pygit2: libgit2 1.0 transition to be marked as done. This means that you claim that the problem has been

Bug#976310: [Pkg-javascript-devel] Bug#976310: Bug#976310: node-compression-webpack-plugin: TypeError: (0 , _schemaUtils.validate) is not a function

2020-12-04 Thread Pirate Praveen
Control: clone -1 -2 Control: reassign -2 node-css-loader Control: retitle -2 many dependencies in the archive differ by major versions On Fri, Dec 4, 2020 at 02:35, Pirate Praveen wrote: I will try to get css-loader from debian working with gitlab as a proper fix. With css-loader 3, the e

Processed: Re: [Pkg-javascript-devel] Bug#976310: Bug#976310: node-compression-webpack-plugin: TypeError: (0 , _schemaUtils.validate) is not a function

2020-12-04 Thread Debian Bug Tracking System
Processing control commands: > clone -1 -2 Bug #976310 [gitlab] node-compression-webpack-plugin: TypeError: (0 , _schemaUtils.validate) is not a function Bug 976310 cloned as bug 976408 > reassign -2 node-css-loader Bug #976408 [gitlab] node-compression-webpack-plugin: TypeError: (0 , _schemaUti

Bug#975163: marked as done (deepin-picker: FTBFS: src/picker.cpp:123:22: error: aggregate ‘QPainterPath circlePath’ has incomplete type and cannot be defined)

2020-12-04 Thread Debian Bug Tracking System
Your message dated Fri, 04 Dec 2020 18:33:56 + with message-id and subject line Bug#975163: fixed in deepin-picker 5.0.1-2 has caused the Debian Bug report #975163, regarding deepin-picker: FTBFS: src/picker.cpp:123:22: error: aggregate ‘QPainterPath circlePath’ has incomplete type and cannot

Bug#925638: closed by Debian FTP Masters (reply to Bernhard Schmidt ) (Bug#925638: fixed in belle-sip 4.3.1+dfsg-1)

2020-12-04 Thread Bernhard Schmidt
Dear Mika, > belle-sip is currently missing in Debian/testing AKA bullseye > because of this issue (which is only fixed in experimental yet): > > | Migration status for belle-sip (- to 1.6.3-5): BLOCKED: Rejected/violates > migration policy/introduces a regression > | Issues preventing migration

Bug#971751: marked as done (spice-gtk: CVE-2020-14355)

2020-12-04 Thread Debian Bug Tracking System
Your message dated Fri, 04 Dec 2020 17:48:48 + with message-id and subject line Bug#971751: fixed in spice-gtk 0.39-1 has caused the Debian Bug report #971751, regarding spice-gtk: CVE-2020-14355 to be marked as done. This means that you claim that the problem has been dealt with. If this is

Bug#970730: marked as done (spice-gtk build-depends unsatisfiable in testing)

2020-12-04 Thread Debian Bug Tracking System
Your message dated Fri, 04 Dec 2020 17:48:48 + with message-id and subject line Bug#970730: fixed in spice-gtk 0.39-1 has caused the Debian Bug report #970730, regarding spice-gtk build-depends unsatisfiable in testing to be marked as done. This means that you claim that the problem has been

Bug#976404: mpi4py: flaky ppc64el autopkgtest on ci.debian.net: regularly times out

2020-12-04 Thread Paul Gevers
Source: mpi4py Version: 3.0.3-7 Severity: serious Tags: sid bullseye X-Debbugs-CC: debian...@lists.debian.org User: debian...@lists.debian.org Usertags: flaky timeout Dear maintainer(s), The autopkgtest of your package turned up a couple of times on our list of regressions. I looked into the hist

Bug#976111: topydo 0.13-3 upload seems to hang ci.debian.net workers while testing todo.txt-base

2020-12-04 Thread Paul Gevers
Hi Dave, On 04-12-2020 15:23, Dave Steele wrote: > Could you lift the block now? There is a version submitted that passes > all autopkgtests. Ack. > Note that the block did not stop the tests from running (which passed).  Yes, because I lifted the blocklist. I wanted to prevent a broken package

Bug#976401: uftp: autopkgtest regression in testing: rm: cannot remove '/tmp/uftp-test-data': Operation not permitted

2020-12-04 Thread Paul Gevers
Source: uftp Version: 4.10.2-1 X-Debbugs-CC: debian...@lists.debian.org Severity: serious User: debian...@lists.debian.org Usertags: regression Dear maintainer(s), With a recent change in testing the autopkgtest of your package started to fail. I copied some of the output at the bottom of this re

Processed: tagging 976303

2020-12-04 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > tags 976303 + pending Bug #976303 [src:kodi] kodi: FTBFS during separate binary-indep build Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 976303: https://bugs.debian.org/cgi-bin/bugreport.c

Processed: Re: Bug#975705: cura lost all information and will not continue wizard

2020-12-04 Thread Debian Bug Tracking System
Processing control commands: > tags -1 confirmed Bug #975705 [cura] cura lost all information and will not continue wizard Added tag(s) confirmed. -- 975705: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=975705 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#975705: cura lost all information and will not continue wizard

2020-12-04 Thread Christoph Berg
Control: tags -1 confirmed Re: RA > Since the update on 22. 11. 2020 cura is not usable any more. It is stuck in > the wizard which I had to go through again at choosing the 3d printer. > > Before I printed normally but since the update nothing goes anymore. Ack, I can confirm the regression on

  1   2   >