Processed: notfixed 945384 in 3.3.0-1

2020-03-13 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > notfixed 945384 3.3.0-1 Bug #945384 [src:visp] visp: autopkgtest regression Ignoring request to alter fixed versions of bug #945384 to the same values previously set > thanks Stopping processing here. Please contact me if you need assistance. --

Bug#945384: closed by Debian FTP Masters (reply to Fabien Spindler ) (Bug#945384: fixed in visp 3.3.0-1)

2020-03-13 Thread Steve Langasek
Control: reopen -1 Control: notfixed 3.3.0-1 The autopkgtests of visp 3.3.0-1 still fail the same way. Installing libvisp-dev still does not pull in libopengl-dev (libOpenGL.so), libglx-dev (libGLX.so), libglu1-mesa-dev (libGLU.so), or libcoin-dev (libCoin.so), which means trying to link against

Processed (with 1 error): Re: Bug#945384 closed by Debian FTP Masters (reply to Fabien Spindler ) (Bug#945384: fixed in visp 3.3.0-1)

2020-03-13 Thread Debian Bug Tracking System
Processing control commands: > reopen -1 Bug #945384 {Done: Fabien Spindler } [src:visp] visp: autopkgtest regression 'reopen' may be inappropriate when a bug has been closed with a version; all fixed versions will be cleared, and you may need to re-add them. Bug reopened No longer marked as fixe

Processed: Re: Bug#953776: qgis: FTBFS on mips64el

2020-03-13 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > severity 953776 important Bug #953776 [src:qgis] qgis: FTBFS on mips64el Severity set to 'important' from 'serious' > thanks Stopping processing here. Please contact me if you need assistance. -- 953776: https://bugs.debian.org/cgi-bin/bugreport

Bug#938027: [Python-modules-team] Bug#938027: Bug#938027: python-pip: Python2 removal in sid/bullseye

2020-03-13 Thread Scott Kitterman
On Friday, March 13, 2020 6:36:59 PM EDT Sandro Tosi wrote: > On Fri, Mar 13, 2020 at 3:51 PM Scott Kitterman wrote: > > I don't know of a reason not to go ahead, but if you do, please be careful > > of what's already in git. Update to the new version is staged there. It > > is blocked on updat

Bug#953856: dict-gazetteer2k: should this package be removed?

2020-03-13 Thread Sandro Tosi
Source: dict-gazetteer2k Severity: serious Hello, i believe this package should be removed: * python2-only * last upstream upload in 2001 (makes sense) * last maintainer upload in 2006, from there 4 NMUs * last reverse dependes on python-dictclient (py2removal effort) * does it still make sense t

Bug#953742: marked as done (vim: FTBFS on armel, armhf, i386, mips64el, mipsel, s390x)

2020-03-13 Thread Debian Bug Tracking System
Your message dated Sat, 14 Mar 2020 04:19:47 + with message-id and subject line Bug#953742: fixed in vim 2:8.2.0378-1 has caused the Debian Bug report #953742, regarding vim: FTBFS on armel, armhf, i386, mips64el, mipsel, s390x to be marked as done. This means that you claim that the problem

Bug#937231: marked as done (paisley: Python2 removal in sid/bullseye)

2020-03-13 Thread Debian Bug Tracking System
Your message dated Sat, 14 Mar 2020 03:16:46 + with message-id and subject line Bug#953845: Removed package(s) from unstable has caused the Debian Bug report #937231, regarding paisley: Python2 removal in sid/bullseye to be marked as done. This means that you claim that the problem has been d

Bug#937241: marked as done (parsley: Python2 removal in sid/bullseye)

2020-03-13 Thread Debian Bug Tracking System
Your message dated Sat, 14 Mar 2020 03:14:37 + with message-id and subject line Bug#953840: Removed package(s) from unstable has caused the Debian Bug report #937241, regarding parsley: Python2 removal in sid/bullseye to be marked as done. This means that you claim that the problem has been d

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

2020-03-13 Thread Debian Bug Tracking System
Your message dated Sat, 14 Mar 2020 03:15:35 + with message-id and subject line Bug#953842: Removed package(s) from unstable has caused the Debian Bug report #938268, regarding python-wstools: Python2 removal in sid/bullseye to be marked as done. This means that you claim that the problem has

Bug#953818: marked as done (RM: python-paver -- RoM; python2-only; no upload since 2013; no rdeps; Maintainer agrees with removal)

2020-03-13 Thread Debian Bug Tracking System
Your message dated Sat, 14 Mar 2020 03:11:43 + with message-id and subject line Bug#953818: Removed package(s) from unstable has caused the Debian Bug report #953818, regarding RM: python-paver -- RoM; python2-only; no upload since 2013; no rdeps; Maintainer agrees with removal to be marked a

Bug#945675: marked as done (ganglia-nagios-bridge: Python2 removal in sid/bullseye)

2020-03-13 Thread Debian Bug Tracking System
Your message dated Sat, 14 Mar 2020 03:13:15 + with message-id and subject line Bug#953835: Removed package(s) from unstable has caused the Debian Bug report #945675, regarding ganglia-nagios-bridge: Python2 removal in sid/bullseye to be marked as done. This means that you claim that the prob

Bug#876301: marked as done (captagent: Broken init script)

2020-03-13 Thread Debian Bug Tracking System
Your message dated Sat, 14 Mar 2020 03:12:20 + with message-id and subject line Bug#953833: Removed package(s) from unstable has caused the Debian Bug report #876301, regarding captagent: Broken init script to be marked as done. This means that you claim that the problem has been dealt with.

Bug#936472: marked as done (egenix-mx-base: Python2 removal in sid/bullseye)

2020-03-13 Thread Debian Bug Tracking System
Your message dated Sat, 14 Mar 2020 03:11:21 + with message-id and subject line Bug#947607: Removed package(s) from unstable has caused the Debian Bug report #936472, regarding egenix-mx-base: Python2 removal in sid/bullseye to be marked as done. This means that you claim that the problem has

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

2020-03-13 Thread Debian Bug Tracking System
Your message dated Sat, 14 Mar 2020 03:11:52 + with message-id and subject line Bug#953818: Removed package(s) from unstable has caused the Debian Bug report #938007, regarding python-paver: Python2 removal in sid/bullseye to be marked as done. This means that you claim that the problem has b

Bug#923319: marked as done (dynalogin: FTBFS with pam >= 1.3)

2020-03-13 Thread Debian Bug Tracking System
Your message dated Sat, 14 Mar 2020 03:13:44 + with message-id and subject line Bug#953837: Removed package(s) from unstable has caused the Debian Bug report #923319, regarding dynalogin: FTBFS with pam >= 1.3 to be marked as done. This means that you claim that the problem has been dealt wit

Bug#948789: [racket/racket] Illegal Instruction on freescale i.mx53 (armv7l) (#3050)

2020-03-13 Thread David Bremner
Paulo Matos writes: > Upstream issue reference for: > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=948789 > Mailing list information: > https://groups.google.com/d/msg/racket-dev/o631-azv-5g/r9Ct1H_KDAAJ I'm not sure if this is a surprise or not, but it looks like the 7.6 is breaking in t

Bug#953849: marked as done (missing check triggers undesired unmounting of the whole target (breaks d-i))

2020-03-13 Thread Debian Bug Tracking System
Your message dated Sat, 14 Mar 2020 01:34:16 + with message-id and subject line Bug#953849: fixed in debootstrap 1.0.123 has caused the Debian Bug report #953849, regarding missing check triggers undesired unmounting of the whole target (breaks d-i) to be marked as done. This means that you

Bug#953852: ardentryst: should this package be removed?

2020-03-13 Thread Sandro Tosi
Package: ardentryst Severity: serious Hello, i believe this package should be removed: * python2-only * dead upstream: * last new upstream release in debian in 2011 * https://sourceforge.net/projects/ardentryst/ reports "Status: Abandoned" * http://www.jordantrudgett.com/ardentryst/ is dead

Bug#953851: pymissile: should this package be removed?

2020-03-13 Thread Sandro Tosi
Package: pymissile Severity: serious Hello, i believe this package should be removed: * python2-only * dead upstream, no new releases since 2007 (!) * no debian uploads since 2016 * last reverse dependency of python-usb (py2removal effort) if i dont hear back within a week with a good reason to

Bug#953850: tinywm: should this package be removed?

2020-03-13 Thread Sandro Tosi
Package: tinywm Severity: serious Hello, i believe this package should be removed: * no upstream release since 2005 (!!!) * no upload since 2012 * last reverse dependency of python-xlib (py2removal effort) if i dont hear back within a week a good reason to keep this package, i'll file for its re

Bug#953849: marked as pending in debootstrap

2020-03-13 Thread Cyril Brulebois
Control: tag -1 pending Hello, Bug #953849 in debootstrap 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/installer-team/debootstrap/-/commit/129f6f199ffd3d1e58

Processed: Bug#953849 marked as pending in debootstrap

2020-03-13 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #953849 [debootstrap] missing check triggers undesired unmounting of the whole target (breaks d-i) Ignoring request to alter tags of bug #953849 to the same tags previously set -- 953849: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=953849

Processed: Bug#953849 marked as pending in debootstrap

2020-03-13 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #953849 [debootstrap] missing check triggers undesired unmounting of the whole target (breaks d-i) Added tag(s) pending. -- 953849: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=953849 Debian Bug Tracking System Contact ow...@bugs.debian.org

Bug#953849: marked as pending in debootstrap

2020-03-13 Thread Cyril Brulebois
Control: tag -1 pending Hello, Bug #953849 in debootstrap 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/installer-team/debootstrap/-/commit/a1a69a111e9d39fe70

Bug#925630: marked as done (aide: ftbfs with GCC-9)

2020-03-13 Thread Debian Bug Tracking System
Your message dated Sat, 14 Mar 2020 00:55:59 + with message-id <20200314005559.blabn7gurywmneb3@debian> and subject line Re: aide: ftbfs with GCC-9 has caused the Debian Bug report #925630, regarding aide: ftbfs with GCC-9 to be marked as done. This means that you claim that the problem has be

Processed: Re: Bug#953849: debootstrap: broken runtime (at least in d-i)

2020-03-13 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > retitle 953849 missing check triggers undesired unmounting of the whole > target (breaks d-i) Bug #953849 [debootstrap] debootstrap: broken runtime (at least in d-i) Changed Bug title to 'missing check triggers undesired unmounting of the whole

Bug#953849: debootstrap: broken runtime (at least in d-i)

2020-03-13 Thread Cyril Brulebois
Package: debootstrap Version: 1.0.121 Severity: serious Justification: RoM [ Could have been filed against debootstrap-udeb instead, but this might also break use cases with regular debootstrap too. ] While reviewing the recent changes in debootstrap (#953759), I was concerned with commit 7ecd819

Bug#938027: python-pip: Python2 removal in sid/bullseye

2020-03-13 Thread Barry Warsaw
Hi Sandro. Honestly, I have not contributed to Debian in a couple of years, and I don’t see that changing any time soon. Best to contact Matthias, the Python Team, or just do whatever you think is best. Cheers, -Barry > On Mar 13, 2020, at 12:32, Sandro Tosi wrote: > > On Fri, 30 Aug 2019 0

Bug#925758: librecad: ftbfs with GCC-9

2020-03-13 Thread Sudip Mukherjee
I was looking at this bug today and I did not get any error in building the current version. Build Architecture: amd64 Build Type: full Build-Space: 1596216 Build-Time: 325 Distribution: unstable Host Architecture: amd64 Install-Time: 192 Job: /home/sudip/debian/librecad/librecad_2.1.3-1.2.dsc Lin

Bug#925753: libneo4j-client: diff for NMU version 2.2.0-1.1

2020-03-13 Thread Sudip Mukherjee
Control: tags 925753 + patch Control: tags 925753 + pending Dear maintainer, I've prepared an NMU for libneo4j-client (versioned as 2.2.0-1.1) and uploaded it to mentors for sponsoring. Please feel free to tell me if I should remove it. -- Regards Sudip diff -Nru libneo4j-client-2.2.0/debian/ch

Processed: libneo4j-client: diff for NMU version 2.2.0-1.1

2020-03-13 Thread Debian Bug Tracking System
Processing control commands: > tags 925753 + patch Bug #925753 [src:libneo4j-client] libneo4j-client: ftbfs with GCC-9 Added tag(s) patch. > tags 925753 + pending Bug #925753 [src:libneo4j-client] libneo4j-client: ftbfs with GCC-9 Added tag(s) pending. -- 925753: https://bugs.debian.org/cgi-bin/

Processed: Bug#953783 marked as pending in installation-guide

2020-03-13 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #953783 {Done: Samuel Thibault } [src:installation-guide] src:installation-guide: fails to migrate to testing for too long Added tag(s) pending. -- 953783: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=953783 Debian Bug Tracking System Cont

Bug#953783: marked as pending in installation-guide

2020-03-13 Thread Samuel Thibault
Control: tag -1 pending Hello, Bug #953783 in installation-guide 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/installer-team/installation-guide/-/commit/7971

Bug#953783: marked as done (src:installation-guide: fails to migrate to testing for too long)

2020-03-13 Thread Debian Bug Tracking System
Your message dated Fri, 13 Mar 2020 23:49:12 + with message-id and subject line Bug#953783: fixed in installation-guide 20191229+rebuild1 has caused the Debian Bug report #953783, regarding src:installation-guide: fails to migrate to testing for too long to be marked as done. This means that

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

2020-03-13 Thread Debian Bug Tracking System
Your message dated Fri, 13 Mar 2020 23:34:57 + with message-id and subject line Bug#937897: fixed in python-lockfile 1:0.12.2-2.1 has caused the Debian Bug report #937897, regarding python-lockfile: Python2 removal in sid/bullseye to be marked as done. This means that you claim that the probl

Bug#953846: psychopy: ships /usr/lib/python3/dist-packages/packaging/__init__.py

2020-03-13 Thread Andreas Beckmann
Package: psychopy Version: 2020.1.3+dfsg-1 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 bottom...): Selec

Bug#953158: sdpa: hardcoded old mumps-seq dependency

2020-03-13 Thread Nobuhiro Iwamatsu
Hi, > http://launchpadlibrarian.net/468909506/sdpa_7.3.13+dfsg-1_7.3.13+dfsg-1ubuntu1.diff.gz > > Can I upload the following fix? otherwise the package won't ever go in testing > > G. Makoto is now working on a package with this fix. Would you please wait for his fix? Best regards, Nobuhiro -

Bug#953818: python-paver: should this package be removed?

2020-03-13 Thread Hans-Christoph Steiner
Please remove! Sandro Tosi: > Package: python-paver > Severity: serious > > Hello, > i believe this package should be removed: > > * python2-only > * while upstream has released a py3k compatible version (and several others in > between the one in the archive), the debian maintainer didnt up

Bug#953158: sdpa: hardcoded old mumps-seq dependency

2020-03-13 Thread Nobuhiro Iwamatsu
Hi Gianfranco, 2020年3月8日(日) 17:10 Gianfranco Costamagna : > > control: tags -1 patch > > the following works. > diff -Nru sdpa-7.3.12+dfsg/debian/changelog sdpa-7.3.12+dfsg/debian/changelog > --- sdpa-7.3.12+dfsg/debian/changelog2019-12-06 08:00:00.0 +0100 > +++ sdpa-7.3.12+dfsg/debian

Processed: reassign 953818 to ftp.debian.org ...

2020-03-13 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > reassign 953818 ftp.debian.org Bug #953818 [python-paver] python-paver: should this package be removed? Bug reassigned from package 'python-paver' to 'ftp.debian.org'. Ignoring request to alter found versions of bug #953818 to the same values pre

Processed: python-lockfile: diff for NMU version 1:0.12.2-2.1

2020-03-13 Thread Debian Bug Tracking System
Processing control commands: > tags 937897 + patch Bug #937897 [src:python-lockfile] python-lockfile: Python2 removal in sid/bullseye Ignoring request to alter tags of bug #937897 to the same tags previously set -- 937897: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=937897 939930: https:/

Processed: python-lockfile: diff for NMU version 1:0.12.2-2.1

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

Bug#937897: python-lockfile: diff for NMU version 1:0.12.2-2.1

2020-03-13 Thread Sandro Tosi
Control: tags 937897 + patch Dear maintainer, I've prepared an NMU for python-lockfile (versioned as 1:0.12.2-2.1). The diff is attached to this message. Regards. diff -Nru python-lockfile-0.12.2/debian/changelog python-lockfile-0.12.2/debian/changelog --- python-lockfile-0.12.2/debian/changel

Processed: found 953807 in 0.6.0-1, tagging 953807, tagging 953766

2020-03-13 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > found 953807 0.6.0-1 Bug #953807 [src:tftpy] tftpy: should this package be removed? Marked as found in versions tftpy/0.6.0-1. > tags 953807 + sid bullseye Bug #953807 [src:tftpy] tftpy: should this package be removed? Added tag(s) bullseye and si

Processed: reassign 952347 to libreoffice-dev, affects 952347

2020-03-13 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > reassign 952347 libreoffice-dev 1:6.4.1~rc1-2 Bug #952347 [src:openclipart] openclipart: FTBFS: /usr/lib/libreoffice/program/gengal.bin: symbol lookup error: /usr/lib/libreoffice/program/gengal.bin: undefined symbol: _Z10getGlxPipev Bug reassign

Bug#952366:

2020-03-13 Thread Mybillserv Inc
Test

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

2020-03-13 Thread Debian Bug Tracking System
Your message dated Fri, 13 Mar 2020 22:41:23 + with message-id and subject line Bug#953823: Removed package(s) from unstable has caused the Debian Bug report #937931, regarding python-mrjob: Python2 removal in sid/bullseye to be marked as done. This means that you claim that the problem has b

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

2020-03-13 Thread Debian Bug Tracking System
Your message dated Fri, 13 Mar 2020 22:40:16 + with message-id and subject line Bug#953813: Removed package(s) from unstable has caused the Debian Bug report #938279, regarding python-xmltv: Python2 removal in sid/bullseye to be marked as done. This means that you claim that the problem has b

Processed: forcibly merging 953806 953830

2020-03-13 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > forcemerge 953806 953830 Bug #953806 {Done: Matthias Klose } [cpp-9] cpp-9: no include path in which to search for limits.h Bug #953815 {Done: Matthias Klose } [cpp-9] libc6-dev: Cannot build GNU Emacs - limits.h error in configure Bug #953815 {

Bug#942990: marked as done (ditrack: Python2 removal in sid/bullseye)

2020-03-13 Thread Debian Bug Tracking System
Your message dated Fri, 13 Mar 2020 22:40:37 + with message-id and subject line Bug#953814: Removed package(s) from unstable has caused the Debian Bug report #942990, regarding ditrack: Python2 removal in sid/bullseye to be marked as done. This means that you claim that the problem has been d

Bug#936180: marked as done (backports.ssl-match-hostname: Python2 removal in sid/bullseye)

2020-03-13 Thread Debian Bug Tracking System
Your message dated Fri, 13 Mar 2020 22:42:17 + with message-id and subject line Bug#953825: Removed package(s) from unstable has caused the Debian Bug report #936180, regarding backports.ssl-match-hostname: Python2 removal in sid/bullseye to be marked as done. This means that you claim that t

Processed: reassign 953830 to cpp-9

2020-03-13 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > reassign 953830 cpp-9 Bug #953830 [gcc-9] /usr/include/limits.h:124:26: error: no include path in which to search for limits.h Bug reassigned from package 'gcc-9' to 'cpp-9'. Ignoring request to alter found versions of bug #953830 to the same val

Bug#936735: marked as done (inotifyx: Python2 removal in sid/bullseye)

2020-03-13 Thread Debian Bug Tracking System
Your message dated Fri, 13 Mar 2020 22:41:45 + with message-id and subject line Bug#953824: Removed package(s) from unstable has caused the Debian Bug report #936735, regarding inotifyx: Python2 removal in sid/bullseye to be marked as done. This means that you claim that the problem has been

Bug#938758: marked as done (urlgrabber: Python2 removal in sid/bullseye)

2020-03-13 Thread Debian Bug Tracking System
Your message dated Fri, 13 Mar 2020 22:36:48 + with message-id and subject line Bug#929544: Removed package(s) from unstable has caused the Debian Bug report #938758, regarding urlgrabber: Python2 removal in sid/bullseye to be marked as done. This means that you claim that the problem has bee

Bug#936629: marked as done (gnukhata-core-engine: Python2 removal in sid/bullseye)

2020-03-13 Thread Debian Bug Tracking System
Your message dated Fri, 13 Mar 2020 22:38:24 + with message-id and subject line Bug#953746: Removed package(s) from unstable has caused the Debian Bug report #936629, regarding gnukhata-core-engine: Python2 removal in sid/bullseye to be marked as done. This means that you claim that the probl

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

2020-03-13 Thread Debian Bug Tracking System
Your message dated Fri, 13 Mar 2020 22:39:53 + with message-id and subject line Bug#953808: Removed package(s) from unstable has caused the Debian Bug report #938196, regarding python-statistics: Python2 removal in sid/bullseye to be marked as done. This means that you claim that the problem

Bug#952074: marked as done (foodcritic: FTBFS: ERROR: Test "ruby2.7" failed.)

2020-03-13 Thread Debian Bug Tracking System
Your message dated Fri, 13 Mar 2020 22:39:09 + with message-id and subject line Bug#953753: Removed package(s) from unstable has caused the Debian Bug report #952074, regarding foodcritic: FTBFS: ERROR: Test "ruby2.7" failed. to be marked as done. This means that you claim that the problem ha

Bug#885486: marked as done (tekka: Depends on unmaintained pygtk)

2020-03-13 Thread Debian Bug Tracking System
Your message dated Fri, 13 Mar 2020 22:38:46 + with message-id and subject line Bug#953750: Removed package(s) from unstable has caused the Debian Bug report #885486, regarding tekka: Depends on unmaintained pygtk to be marked as done. This means that you claim that the problem has been dealt

Bug#938604: marked as done (sushi: Python2 removal in sid/bullseye)

2020-03-13 Thread Debian Bug Tracking System
Your message dated Fri, 13 Mar 2020 22:38:46 + with message-id and subject line Bug#953750: Removed package(s) from unstable has caused the Debian Bug report #938604, regarding sushi: Python2 removal in sid/bullseye to be marked as done. This means that you claim that the problem has been dea

Bug#916508: marked as done (netplan: Should not be included in buster)

2020-03-13 Thread Debian Bug Tracking System
Your message dated Fri, 13 Mar 2020 22:37:55 + with message-id and subject line Bug#953738: Removed package(s) from unstable has caused the Debian Bug report #916508, regarding netplan: Should not be included in buster to be marked as done. This means that you claim that the problem has been

Bug#950043: marked as done (python-invocations FTBFS: test failures)

2020-03-13 Thread Debian Bug Tracking System
Your message dated Fri, 13 Mar 2020 22:39:30 + with message-id and subject line Bug#953771: Removed package(s) from unstable has caused the Debian Bug report #950043, regarding python-invocations FTBFS: test failures to be marked as done. This means that you claim that the problem has been de

Bug#953830: /usr/include/limits.h:124:26: error: no include path in which to search for limits.h

2020-03-13 Thread Aurelien Jarno
control: reassign -1 gcc-9 control: forcemerge 953806 -1 On 2020-03-13 23:00, Thorsten Glaser wrote: > Package: libc6-dev > Version: 2.30-2 > Severity: grave > Justification: renders package unusable > > Unsure whether it’s upstream or Debian, but… It's debian specific and not a glibc issue. Rea

Bug#938027: [Python-modules-team] Bug#938027: Bug#938027: python-pip: Python2 removal in sid/bullseye

2020-03-13 Thread Sandro Tosi
On Fri, Mar 13, 2020 at 3:51 PM Scott Kitterman wrote: > > I don't know of a reason not to go ahead, but if you do, please be careful of > what's already in git. Update to the new version is staged there. It is > blocked on updates for some of the packages it builds wheels from. oooh i see yo

Processed (with 1 error): Re: Bug#953830: /usr/include/limits.h:124:26: error: no include path in which to search for limits.h

2020-03-13 Thread Debian Bug Tracking System
Processing control commands: > reassign -1 gcc-9 Bug #953830 [libc6-dev] /usr/include/limits.h:124:26: error: no include path in which to search for limits.h Bug reassigned from package 'libc6-dev' to 'gcc-9'. No longer marked as found in versions glibc/2.30-2. Ignoring request to alter fixed ver

Bug#948206: mitmproxy incompatible with python3-wsproto=0.15.0-2

2020-03-13 Thread Kevin Locke
On Sun, 2020-01-05 at 11:27 +0100, Adrian Vollmer wrote: > After upgrading python3-wsproto to version 0.15.0-2, mitmproxy fails > immediately with this error message: > > ImportError: cannot import name 'WSConnection' from 'wsproto.connection' > (/usr/lib/python3/dist-packages/wsproto/conn

Bug#926094: marked as done (src:scilab-ann: FTBFS, scilab hangs)

2020-03-13 Thread Debian Bug Tracking System
Your message dated Fri, 13 Mar 2020 23:09:38 +0100 with message-id <67d7d12e-62a4-5e0f-95cf-5a8a0d5fa...@debian.org> and subject line scilab-ann has been removed from Debian has caused the Debian Bug report #926094, regarding src:scilab-ann: FTBFS, scilab hangs to be marked as done. This means tha

Bug#953832: drmaa: autopkgtest failure: RuntimeError: Could not find drmaa library

2020-03-13 Thread Paul Gevers
Source: drmaa Version: 0.7.9-1 X-Debbugs-CC: debian...@lists.debian.org Severity: serious User: debian...@lists.debian.org Usertags: fails-always Dear maintainers, With a recent upload of drmaa you added an autopkgtest, great. However, it fails. I copied some of the output at the bottom of this r

Bug#897550: marked as done (scilab-ann: FTBFS: /usr/bin/scilab-bin: error while loading shared libraries: libjava.so: cannot open shared object file: No such file or directory)

2020-03-13 Thread Debian Bug Tracking System
Your message dated Fri, 13 Mar 2020 23:09:38 +0100 with message-id <67d7d12e-62a4-5e0f-95cf-5a8a0d5fa...@debian.org> and subject line scilab-ann has been removed from Debian has caused the Debian Bug report #897550, regarding scilab-ann: FTBFS: /usr/bin/scilab-bin: error while loading shared libra

Bug#953830: /usr/include/limits.h:124:26: error: no include path in which to search for limits.h

2020-03-13 Thread Thorsten Glaser
Package: libc6-dev Version: 2.30-2 Severity: grave Justification: renders package unusable Unsure whether it’s upstream or Debian, but… tglase@tglase-nb:~ $ gcc x.c In file included from x.c:1: /usr/include/limits.h:124:26: error: no include path in which to search for limits.h 124 | # includ

Bug#935660: marked as done (tortoisehg: Obsolete libs (python2) - depends python-pyqt5.qsci)

2020-03-13 Thread Debian Bug Tracking System
Your message dated Fri, 13 Mar 2020 22:56:47 +0100 with message-id <99e17f67-5d91-cef0-854c-cbbb7d66a...@debian.org> and subject line tortoisehg has been removed from Debian has caused the Debian Bug report #935660, regarding tortoisehg: Obsolete libs (python2) - depends python-pyqt5.qsci to be mar

Bug#921704: marked as done (tortoisehg: uninstallable with mercurial 4.9)

2020-03-13 Thread Debian Bug Tracking System
Your message dated Fri, 13 Mar 2020 22:56:47 +0100 with message-id <99e17f67-5d91-cef0-854c-cbbb7d66a...@debian.org> and subject line tortoisehg has been removed from Debian has caused the Debian Bug report #921704, regarding tortoisehg: uninstallable with mercurial 4.9 to be marked as done. This

Bug#953828: nevow: should this package be removed?

2020-03-13 Thread Sandro Tosi
Source: nevow Severity: serious Hello, i believe this package should be removed: * python2-only * upstream still hasnt finish porting it to python3, https://github.com/twisted/nevow/issues/101 * no rdeps * relatively low popcon and dropping rapidly if i dont hear back within a week with a good

Bug#953826: r-cran-rprotobuf: autopkgtest regression: cannot open file '/usr/share/doc/r-cran-rprotobuf/tests/runUnitTests.R'

2020-03-13 Thread Paul Gevers
Source: r-cran-rprotobuf Version: 0.4.15-1 X-Debbugs-CC: debian...@lists.debian.org Severity: serious User: debian...@lists.debian.org Usertags: regression Dear maintainers, With a recent upload of r-cran-rprotobuf the autopkgtest of r-cran-rprotobuf fails in testing when that autopkgtest is run

Bug#953682: marked as done (src:dosage: fails to migrate to testing for too long)

2020-03-13 Thread Debian Bug Tracking System
Your message dated Fri, 13 Mar 2020 21:19:17 + with message-id and subject line Bug#953682: fixed in dosage 2.15-4 has caused the Debian Bug report #953682, regarding src:dosage: fails to migrate to testing for too long to be marked as done. This means that you claim that the problem has been

Processed: src:debian-cloud-images: fails to migrate to testing for too long

2020-03-13 Thread Debian Bug Tracking System
Processing control commands: > fixed -1 0.0.3 Bug #953822 [src:debian-cloud-images] src:debian-cloud-images: fails to migrate to testing for too long Marked as fixed in versions debian-cloud-images/0.0.3. -- 953822: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=953822 Debian Bug Tracking Sy

Bug#953822: src:debian-cloud-images: fails to migrate to testing for too long

2020-03-13 Thread Paul Gevers
Source: debian-cloud-images Version: 0.0.1 Severity: serious Control: fixed -1 0.0.3 Tags: sid bullseye User: release.debian@packages.debian.org Usertags: out-of-sync Dear maintainer(s), As recently announced [1], the Release Team now considers packages that are out-of-sync between testing an

Bug#953820: foolscap: should this package be removed?

2020-03-13 Thread Sandro Tosi
Source: foolscap Severity: serious Hello, i belive this package should be removed: * python2-only * upstream hasnt finish porting it to python3 https://github.com/warner/foolscap/issues/48 * no rdeps in testing if i dont hear back within a week with a good reason to keep it, i'm gonna file for

Bug#953818: python-paver: should this package be removed?

2020-03-13 Thread Sandro Tosi
Package: python-paver Severity: serious Hello, i believe this package should be removed: * python2-only * while upstream has released a py3k compatible version (and several others in between the one in the archive), the debian maintainer didnt upload this package since late 2013 * no rdeps *

Bug#949732: closing 949732

2020-03-13 Thread Barak A. Pearlmutter
close 949732 3.2.2-3 thanks merge Ubuntu patch which addresses the issue

Processed: closing 949732

2020-03-13 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > close 949732 3.2.2-3 Bug #949732 [src:mlpack] package ftbfs on some archs, and has missing dependencies Marked as fixed in versions mlpack/3.2.2-3. Bug #949732 [src:mlpack] package ftbfs on some archs, and has missing dependencies Marked Bug as

Bug#953815: libc6-dev: Cannot build GNU Emacs - limits.h error in configure

2020-03-13 Thread Adam Sjøgren
Sven writes: > Known problem, wait for gcc-9 9.3.0-3 to appear on your mirror. Thanks - sorry for hitting the wrong "target" (I only looked at libc6-dev and glibc bugs :-/) > Welcome to unstable! Been here since bo. Best regards, Adam -- "Vilken sanning, Måns, är sann?"

Bug#938027: [Python-modules-team] Bug#938027: python-pip: Python2 removal in sid/bullseye

2020-03-13 Thread Scott Kitterman
I don't know of a reason not to go ahead, but if you do, please be careful of what's already in git. Update to the new version is staged there. It is blocked on updates for some of the packages it builds wheels from. Scott K On March 13, 2020 7:32:35 PM UTC, Sandro Tosi wrote: >On Fri, 30 Au

Bug#953815: marked as done (libc6-dev: Cannot build GNU Emacs - limits.h error in configure)

2020-03-13 Thread Debian Bug Tracking System
Your message dated Fri, 13 Mar 2020 20:38:47 +0100 with message-id <4354a783-e51c-d987-30a9-388294ead...@debian.org> and subject line Re: Bug#953806: cpp-9: no include path in which to search for limits.h has caused the Debian Bug report #953806, regarding libc6-dev: Cannot build GNU Emacs - limit

Bug#953806: marked as done (cpp-9: no include path in which to search for limits.h)

2020-03-13 Thread Debian Bug Tracking System
Your message dated Fri, 13 Mar 2020 20:38:47 +0100 with message-id <4354a783-e51c-d987-30a9-388294ead...@debian.org> and subject line Re: Bug#953806: cpp-9: no include path in which to search for limits.h has caused the Debian Bug report #953806, regarding cpp-9: no include path in which to search

Bug#938027: python-pip: Python2 removal in sid/bullseye

2020-03-13 Thread Sandro Tosi
On Fri, 30 Aug 2019 07:44:13 + Matthias Klose wrote: > Package: src:python-pip > Version: 18.1-5 > Severity: normal > Tags: sid bullseye > User: debian-pyt...@lists.debian.org > Usertags: py2removal the only rdeps of `bin:python-pip` have been removed from testing, so it's probably time we dr

Processed: Re: Bug#953815: libc6-dev: Cannot build GNU Emacs - limits.h error in configure

2020-03-13 Thread Debian Bug Tracking System
Processing control commands: > reassign -1 cpp-9 Bug #953815 [libc6-dev] libc6-dev: Cannot build GNU Emacs - limits.h error in configure Bug reassigned from package 'libc6-dev' to 'cpp-9'. No longer marked as found in versions glibc/2.30-2. Ignoring request to alter fixed versions of bug #953815

Bug#953766: marked as done (glib-networking: tests fail with GLib 2.64: tls/tests/connection.c:2035:quit_on_handshake_complete: assertion failed (error == (g-tls-error-quark, 3)): error is NULL)

2020-03-13 Thread Debian Bug Tracking System
Your message dated Fri, 13 Mar 2020 19:19:09 + with message-id and subject line Bug#953766: fixed in glib-networking 2.64.0-1 has caused the Debian Bug report #953766, regarding glib-networking: tests fail with GLib 2.64: tls/tests/connection.c:2035:quit_on_handshake_complete: assertion faile

Processed: Bug#953766 marked as pending in glib-networking

2020-03-13 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #953766 [src:glib-networking] glib-networking: tests fail with GLib 2.64: tls/tests/connection.c:2035:quit_on_handshake_complete: assertion failed (error == (g-tls-error-quark, 3)): error is NULL Ignoring request to alter tags of bug #953766 to t

Bug#953766: marked as pending in glib-networking

2020-03-13 Thread Simon McVittie
Control: tag -1 pending Hello, Bug #953766 in glib-networking reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/gnome-team/glib-networking/-/commit/ffb51dd367ca5d

Bug#953806: marked as done (cpp-9: no include path in which to search for limits.h)

2020-03-13 Thread Debian Bug Tracking System
Your message dated Fri, 13 Mar 2020 19:55:14 +0100 with message-id <87ftecjd9p@turtle.gmx.de> and subject line Re: Bug#953806: cpp-9: no include path in which to search for limits.h has caused the Debian Bug report #953806, regarding cpp-9: no include path in which to search for limits.h to be

Bug#953806: cpp-9: no include path in which to search for limits.h

2020-03-13 Thread Vincent Lefevre
Compare: cventin:~> cpp-8 tst.c # 1 "tst.c" # 1 "" # 1 "" # 31 "" # 1 "/usr/include/stdc-predef.h" 1 3 4 # 32 "" 2 # 1 "tst.c" # 1 "/usr/lib/gcc/x86_64-linux-gnu/8/include-fixed/limits.h" 1 3 4 [...] cventin:~> cpp-9 tst.c # 1 "tst.c" # 1 "" # 1 "" # 31 "" # 1 "/usr/include/stdc-predef.h" 1 3 4 #

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

2020-03-13 Thread Debian Bug Tracking System
Your message dated Fri, 13 Mar 2020 18:07:48 + with message-id and subject line Bug#937942: fixed in python-netaddr 0.7.19-4 has caused the Debian Bug report #937942, regarding python-netaddr: Python2 removal in sid/bullseye to be marked as done. This means that you claim that the problem has

Bug#953807: tftpy: should this package be removed?

2020-03-13 Thread Sandro Tosi
Source: tftpy Severity: serious Hello, i believe this package should be removed: * python2-only * upstream released 0.8.0, py3k-compatible, but it's now non-free, see https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=784028#10 * still in https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=784028#

Bug#953806: cpp-9: no include path in which to search for limits.h

2020-03-13 Thread Vincent Lefevre
Package: cpp-9 Version: 9.3.0-1 Severity: grave Justification: renders package unusable The compilation of a simple program like #include int main (void) { return 0; } now fails: cventin:~> gcc-9 tst.c -o tst In file included from tst.c:1: /usr/include/limits.h:124:26: error: no include pat

Bug#937942: marked as pending in python-netaddr

2020-03-13 Thread Sandro Tosi
Control: tag -1 pending Hello, Bug #937942 in python-netaddr reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/python-team/modules/python-netaddr/-/commit/02dc442

Processed: Bug#937942 marked as pending in python-netaddr

2020-03-13 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #937942 [src:python-netaddr] python-netaddr: Python2 removal in sid/bullseye Added tag(s) pending. -- 937942: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=937942 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#953800: gpgme1.0: don't fail checky2106 on 32bit systems

2020-03-13 Thread Gianfranco Costamagna
Source: gpgme1.0 Version: 1.13.1-7 Severity: serious Justification: test failure on release architecture Tags: patch Hello, looks like checky2106 is obviously failing on 32bit architectures. I suggest to just ignore the test results on that architectures. Patch: diff -Nru gpgme1.0-1.13.1/debia

Bug#953799: flaky autopkgtest on arm64

2020-03-13 Thread Michael Biebl
Source: mandos Version: 1.8.9-2 Severity: serious User: debian...@lists.debian.org Usertags: flaky Hi, it appears the autopkgtest on arm64 is not working reliably. This is a serious issue as nowadays autopkgtest results are using for gating testing migration. E.g. currently systemd is blocked by

Bug#950376: marked as done (apertium-cy-en FTBFS with apertium 3.6.1)

2020-03-13 Thread Debian Bug Tracking System
Your message dated Fri, 13 Mar 2020 16:20:27 + with message-id and subject line Bug#950376: fixed in apertium-cy-en 0.1.1~r57554-5 has caused the Debian Bug report #950376, regarding apertium-cy-en FTBFS with apertium 3.6.1 to be marked as done. This means that you claim that the problem has

  1   2   >