Bug#934047: scilab: please add libnum-ocaml-dev to Build-Depends

2019-11-07 Thread Sylvestre Ledru
forwarded 934047 https://bugzilla.scilab.org/show_bug.cgi?id=16240 thanks Le 06/08/2019 à 14:11, Stéphane Glondu a écrit : Package: scilab Version: 6.0.1-10 Severity: important Hello, Currently, scilab FTBFS with OCaml 4.08.x because it depends on the num library that used to be shipped with

Processed: Re: Bug#934047: scilab: please add libnum-ocaml-dev to Build-Depends

2019-11-07 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > forwarded 934047 https://bugzilla.scilab.org/show_bug.cgi?id=16240 Bug #934047 [scilab] scilab: please add libnum-ocaml-dev to Build-Depends Set Bug forwarded-to-address to 'https://bugzilla.scilab.org/show_bug.cgi?id=16240'. > thanks Stopping

Processed (with 1 error): Re: Bug#944199: exim4: dsearch in config end up in exim4 panic

2019-11-07 Thread Debian Bug Tracking System
Processing control commands: > severity -1 serious Bug #944199 [exim4] exim4: dsearch in config end up in exim4 panic Severity set to 'serious' from 'important' > forwared -1 https://bugs.exim.org/show_bug.cgi?id=2465 Unknown command or malformed arguments to command. -- 944199:

Bug#944309: marked as done (pslib: FTBFS on all autobuilders: configure.ac:45: error: possibly undefined macro: AM_GLIB_GNU_GETTEXT)

2019-11-07 Thread Debian Bug Tracking System
Your message dated Thu, 07 Nov 2019 17:07:06 + with message-id and subject line Bug#944309: fixed in pslib 0.4.7-1 has caused the Debian Bug report #944309, regarding pslib: FTBFS on all autobuilders: configure.ac:45: error: possibly undefined macro: AM_GLIB_GNU_GETTEXT to be marked as done.

Processed: bug 944199 is forwarded to https://bugs.exim.org/show_bug.cgi?id=2465

2019-11-07 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > forwarded 944199 https://bugs.exim.org/show_bug.cgi?id=2465 Bug #944199 [exim4] exim4: dsearch in config end up in exim4 panic Set Bug forwarded-to-address to 'https://bugs.exim.org/show_bug.cgi?id=2465'. > thanks Stopping processing here.

Bug#944249: [Pkg-emacsen-addons] Bug#944249: gnuplot-mode does not work with emacs26

2019-11-07 Thread Sean Whitton
Hello, On Wed 06 Nov 2019 at 08:53PM -05, Nicholas D Steeves wrote: > Hi Olaf and Dima, > > Dima, if it's alright with you can I please take care of this bug? > I've head I need an RC Bug NMU process for the "demonstrates skills > and knowledge of process" section of my eventual DD application.

Bug#944258: lintian 2.32.0~bpo9+1 in stretch-backports depends on coreutils (>= 8.30), but stretch has only 8.26-3

2019-11-07 Thread Chris Lamb
Christoph Berg wrote: > > According to Andreas Beckmann, coreutils 8.30 is in the process of > > being ported to stretch. […] > I'm not sure if that means that backport is really going to appear in > stretch-backports. That is my reading of it too. Felix, can we drop this requirement on

Processed: bug 944060 is forwarded to https://bugs.exim.org/show_bug.cgi?id=2464

2019-11-07 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > forwarded 944060 https://bugs.exim.org/show_bug.cgi?id=2464 Bug #944060 [src:exim4] exim4-daemon-light: FTBFS (testsuite error) on mipsel Set Bug forwarded-to-address to 'https://bugs.exim.org/show_bug.cgi?id=2464'. > thanks Stopping processing

Processed: Bug#885498 marked as pending in nmap

2019-11-07 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #885498 [zenmap] zenmap: Depends on unmaintained pygtk Added tag(s) pending. -- 885498: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=885498 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#941525: marked as done (gnu-standards: build-depend on texlive-plain-generic, not obsolete texlive-generic-recommended)

2019-11-07 Thread Debian Bug Tracking System
Your message dated Thu, 07 Nov 2019 16:19:08 + with message-id and subject line Bug#941525: fixed in gnu-standards 2010.03.11-1.1 has caused the Debian Bug report #941525, regarding gnu-standards: build-depend on texlive-plain-generic, not obsolete texlive-generic-recommended to be marked as

Bug#944258: lintian 2.32.0~bpo9+1 in stretch-backports depends on coreutils (>= 8.30), but stretch has only 8.26-3

2019-11-07 Thread Felix Lechner
Hi, On Thu, Nov 7, 2019 at 10:33 AM Chris Lamb wrote: > > > I'm not sure if that means that backport is really going to appear in > > stretch-backports. > > That is my reading of it too. Felix, can we drop this requirement on > coreutils for the time being? (I'm afraid I wasn't following the >

Bug#885498: marked as pending in nmap

2019-11-07 Thread Hilko Bengen
Control: tag -1 pending Hello, Bug #885498 in nmap reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at:

Bug#944258: lintian 2.32.0~bpo9+1 in stretch-backports depends on coreutils (>= 8.30), but stretch has only 8.26-3

2019-11-07 Thread Chris Lamb
Hi Felix, > Yes, we probably can but I would like to understand, please, why > coreutils 8.30 (which, according to Andreas Beckmann, builds cleanly > in stretch) cannot find its way into stretch-bpo. Backporting such a big package (with likely lots of other changes) does not seem particularly

Bug#944258: lintian 2.32.0~bpo9+1 in stretch-backports depends on coreutils (>= 8.30), but stretch has only 8.26-3

2019-11-07 Thread Christoph Berg
Re: Felix Lechner 2019-11-06 > According to Andreas Beckmann, coreutils 8.30 is in the process of > being ported to stretch. Thanks for the feedback. > For details, please have a look at the PS here: > > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=943910#25 I'm not sure if that

Bug#939963: marked as done (FTBFS with OCaml 4.08.0 (num))

2019-11-07 Thread Debian Bug Tracking System
Your message dated Thu, 07 Nov 2019 10:34:09 + with message-id and subject line Bug#939963: fixed in orpie 1.5.2-3 has caused the Debian Bug report #939963, regarding FTBFS with OCaml 4.08.0 (num) to be marked as done. This means that you claim that the problem has been dealt with. If this

Bug#885273: marked as done (diffuse: Depends on unmaintained pygtk)

2019-11-07 Thread Debian Bug Tracking System
Your message dated Fri, 08 Nov 2019 07:35:46 + with message-id and subject line Bug#944307: Removed package(s) from unstable has caused the Debian Bug report #885273, regarding diffuse: Depends on unmaintained pygtk to be marked as done. This means that you claim that the problem has been

Bug#942203: marked as done (postbooks: fails to comply with the DFSG)

2019-11-07 Thread Debian Bug Tracking System
Your message dated Fri, 08 Nov 2019 07:37:04 + with message-id and subject line Bug#944283: Removed package(s) from unstable has caused the Debian Bug report #942203, regarding postbooks: fails to comply with the DFSG to be marked as done. This means that you claim that the problem has been

Bug#942971: marked as done (diffuse: Python2 removal in sid/bullseye)

2019-11-07 Thread Debian Bug Tracking System
Your message dated Fri, 08 Nov 2019 07:35:46 + with message-id and subject line Bug#944307: Removed package(s) from unstable has caused the Debian Bug report #942971, regarding diffuse: Python2 removal in sid/bullseye to be marked as done. This means that you claim that the problem has been

Bug#874880: [freemedforms-project] Future Qt4 removal from Buster

2019-11-07 Thread Eric Maeker
Hi, I've just release a pre-version of 1.1.0 for MacOs. I'll work in the next week to correct the package and will provide a Debian package ASAP after this... Thanks Le lun. 28 oct. 2019 à 23:50, Andreas Tille a écrit : > I'll do so once I'm back from vacation. > Its a shame that Eric does

Bug#944258: lintian 2.32.0~bpo9+1 in stretch-backports depends on coreutils (>= 8.30), but stretch has only 8.26-3

2019-11-07 Thread Christoph Berg
Am 7. November 2019 23:19:51 MEZ schrieb Felix Lechner : >Hi Chris, > >On Thu, Nov 7, 2019 at 2:07 PM Chris Lamb wrote: >> >> I do not understand the frequency that Christoph's checks >> his email has any bearing here. Can you elaborate? > >Unfortunately, I can only speculate that he meant to

Bug#942193: marked as done (dwz: dh_dwz freecad build regression: write_die: Assertion `value && refdcu->cu_kind != CU_ALT' failed.)

2019-11-07 Thread Debian Bug Tracking System
Your message dated Thu, 07 Nov 2019 13:33:55 + with message-id and subject line Bug#942193: fixed in dwz 0.13-2 has caused the Debian Bug report #942193, regarding dwz: dh_dwz freecad build regression: write_die: Assertion `value && refdcu->cu_kind != CU_ALT' failed. to be marked as done.

Bug#944305: rpki-trust-anchors: fails to purge: rmdir: failed to remove '/etc/tals/': No such file or directory

2019-11-07 Thread Andreas Beckmann
Package: rpki-trust-anchors Version: 20191019-2 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package failed to purge. According to policy 7.2 you cannot rely on the depends being available during purge, only the essential

Bug#933364: marked as done (lua-geoip depends on cruft package.)

2019-11-07 Thread Debian Bug Tracking System
Your message dated Thu, 07 Nov 2019 11:18:58 + with message-id and subject line Bug#933364: fixed in lua-geoip 0.2-1 has caused the Debian Bug report #933364, regarding lua-geoip depends on cruft package. to be marked as done. This means that you claim that the problem has been dealt with.

Bug#944305: marked as done (rpki-trust-anchors: fails to purge: rmdir: failed to remove '/etc/tals/': No such file or directory)

2019-11-07 Thread Debian Bug Tracking System
Your message dated Thu, 07 Nov 2019 15:21:43 + with message-id and subject line Bug#944305: fixed in rpki-trust-anchors 20191019-3 has caused the Debian Bug report #944305, regarding rpki-trust-anchors: fails to purge: rmdir: failed to remove '/etc/tals/': No such file or directory to be

Processed: tagging 944053, reassign 944262 to wnpp, reassign 940068 to src:gr-gsm, tagging 943603 ...

2019-11-07 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > tags 944053 - moreinfo Bug #944053 {Done: Andreas Beckmann } [nvidia-legacy-390xx-kernel-dkms] nvidia-legacy-390xx-kernel-dkms: Unable to build the driver Removed tag(s) moreinfo. > reassign 944262 wnpp Bug #944262 [adios2] ITP: adios2 -- The

Bug#944309: pslib: FTBFS on all autobuilders: configure.ac:45: error: possibly undefined macro: AM_GLIB_GNU_GETTEXT

2019-11-07 Thread Andreas Metzler
Source: pslib Version: 0.4.6-1 Severity: serious Tags: ftbfs Justification: fails to build from source (but built successfully in the past) Hello, the latest upload did not build: https://buildd.debian.org/status/fetch.php?pkg=pslib=arm64=0.4.6-1=1573122104=0 dh build-arch

Bug#944258: lintian 2.32.0~bpo9+1 in stretch-backports depends on coreutils (>= 8.30), but stretch has only 8.26-3

2019-11-07 Thread Christoph Berg
Re: Felix Lechner 2019-11-07 > Also, as a side note, would someone please explain why someone still > on stretch would need lintian? I am personally on stable, but most > package maintainers out there seem to track testing or the bleeding > edge, unstable. sbuild recently started running

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

2019-11-07 Thread Debian Bug Tracking System
Your message dated Thu, 7 Nov 2019 21:39:01 +0100 with message-id <20191107203901.igkobzsuqflt7...@p1otr.com> and subject line osmalchemy is no longer in testing has caused the Debian Bug report #934958, regarding sqlalchemy breaks osmalchemy (autopkgtest) to be marked as done. This means that

Bug#944156: marked as done (gr-dab: Don't Build-Depend on pygtk)

2019-11-07 Thread Debian Bug Tracking System
Your message dated Thu, 07 Nov 2019 20:39:38 + with message-id and subject line Bug#944156: fixed in gr-dab 0.4-2 has caused the Debian Bug report #944156, regarding gr-dab: Don't Build-Depend on pygtk to be marked as done. This means that you claim that the problem has been dealt with. If

Bug#944258: lintian 2.32.0~bpo9+1 in stretch-backports depends on coreutils (>= 8.30), but stretch has only 8.26-3

2019-11-07 Thread Felix Lechner
Hi, The version requirement was dropped: https://salsa.debian.org/lintian/lintian/commit/33bd1434f0c160770a26bea55328e5bf7545322f Since Christoph receives emails every six hours, a new release may be in order. Thank you for your patience as we work to make Lintian better for everyone.

Bug#944258: lintian 2.32.0~bpo9+1 in stretch-backports depends on coreutils (>= 8.30), but stretch has only 8.26-3

2019-11-07 Thread Felix Lechner
Hi Chris, On Thu, Nov 7, 2019 at 2:07 PM Chris Lamb wrote: > > I do not understand the frequency that Christoph's checks > his email has any bearing here. Can you elaborate? Unfortunately, I can only speculate that he meant to present a sense of urgency. If a new release is needed, Christoph

Bug#944093: marked as pending in abinit

2019-11-07 Thread Michael Banck
Control: tag -1 pending Hello, Bug #944093 in abinit reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at:

Processed: Bug#944093 marked as pending in abinit

2019-11-07 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #944093 [src:abinit] abinit ftbfs on every architecture Added tag(s) pending. -- 944093: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=944093 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#944324: python-paraview has to be renamed to python3-paraview

2019-11-07 Thread Matthias Klose
Package: src:paraview Version: 5.7.0-1 Severity: serious Tags: sid bullseye Thanks for converting the package to Python3, however the python-paraview has to be renamed to python3-paraview, according to our Python policy. Please also change the shebang for the autopkg test when doing that.

Bug#944258: lintian 2.32.0~bpo9+1 in stretch-backports depends on coreutils (>= 8.30), but stretch has only 8.26-3

2019-11-07 Thread Adam D. Barratt
On Thu, 2019-11-07 at 10:49 -0800, Felix Lechner wrote: > Also, as a side note, would someone please explain why someone still > on stretch would need lintian? I am personally on stable, but most > package maintainers out there seem to track testing or the bleeding > edge, unstable. Well, at

Bug#933459: marked as pending in pgadmin3

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

Processed: Bug#933459 marked as pending in pgadmin3

2019-11-07 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #933459 [pgadmin3] pgadmin3: Please rebuild against wxWidgets GTK 3 package Added tag(s) pending. -- 933459: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=933459 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#944258: lintian 2.32.0~bpo9+1 in stretch-backports depends on coreutils (>= 8.30), but stretch has only 8.26-3

2019-11-07 Thread Chris Lamb
Hi Felix, > Since Christoph receives emails every six hours, a new release may > be in order. Thanks for addressing this. I did just release Lintian prior to this change, but I do not understand the frequency that Christoph's checks his email has any bearing here. Can you elaborate? I suspect

Bug#944093: marked as done (abinit ftbfs on every architecture)

2019-11-07 Thread Debian Bug Tracking System
Your message dated Thu, 07 Nov 2019 23:21:04 + with message-id and subject line Bug#944093: fixed in abinit 8.10.3-2 has caused the Debian Bug report #944093, regarding abinit ftbfs on every architecture to be marked as done. This means that you claim that the problem has been dealt with. If

Bug#932679: marked as done (python-networkx: Don't depend on python-gdal)

2019-11-07 Thread Debian Bug Tracking System
Your message dated Thu, 07 Nov 2019 23:33:49 + with message-id and subject line Bug#932679: fixed in python-networkx 2.2-2 has caused the Debian Bug report #932679, regarding python-networkx: Don't depend on python-gdal to be marked as done. This means that you claim that the problem has

Bug#944327: fribidi: CVE-2019-18397

2019-11-07 Thread Salvatore Bonaccorso
Source: fribidi Version: 1.0.7-1 Severity: grave Tags: security upstream Justification: user security hole Control: found -1 1.0.5-3.1 Control: fixed -1 1.0.5-3.1+deb10u1 Hi, The following vulnerability was published for fribidi. CVE-2019-18397[0]: | stack buffer overflow in the

Processed: fribidi: CVE-2019-18397

2019-11-07 Thread Debian Bug Tracking System
Processing control commands: > found -1 1.0.5-3.1 Bug #944327 [src:fribidi] fribidi: CVE-2019-18397 Marked as found in versions fribidi/1.0.5-3.1. > fixed -1 1.0.5-3.1+deb10u1 Bug #944327 [src:fribidi] fribidi: CVE-2019-18397 The source 'fribidi' and version '1.0.5-3.1+deb10u1' do not appear to

Processed: affects 942203

2019-11-07 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > affects 942203 src:csvimp src:openrpt src:postbooks-schema > src:postbooks-updater Bug #942203 [postbooks] postbooks: fails to comply with the DFSG Added indication that 942203 affects src:csvimp, src:openrpt, src:postbooks-schema, and

Bug#942203: postbooks: fails to comply with the DFSG

2019-11-07 Thread Andrej Shadura
On Sat, 12 Oct 2019 11:00:41 +0200 "Francesco Poli (wintermute)" wrote: > Package: postbooks > Version: 4.11.3-2 > Severity: serious > Justification: Policy 2.2.1 > > Dear xTuple Maintainers, > I noticed that this package is in Debian main and is [released] under > the terms of the Common Public

Bug#933128: libparse-debianchangelog-perl: Unsuitable for Bullseye unless someone becomes upstream

2019-11-07 Thread intrigeri
Hi!, Guillem Jover: > Ah! Thanks for the info. How about the following clarification then? :) Perfect! That's exactly what I would have needed :) Cheers, -- intrigeri

Bug#932679: marked as pending in python-networkx

2019-11-07 Thread Sandro Tosi
Control: tag -1 pending Hello, Bug #932679 in python-networkx reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at:

Bug#944129: marked as done (arp-scan: not returning any results)

2019-11-07 Thread Debian Bug Tracking System
Your message dated Thu, 07 Nov 2019 19:48:58 + with message-id and subject line Bug#944129: fixed in arp-scan 1.9.6-1 has caused the Debian Bug report #944129, regarding arp-scan: not returning any results to be marked as done. This means that you claim that the problem has been dealt with.

Bug#932534: marked as done (longrun: Uses manual dh sequence operations that are going to be removed)

2019-11-07 Thread Debian Bug Tracking System
Your message dated Thu, 07 Nov 2019 20:42:34 + with message-id and subject line Bug#932534: fixed in longrun 0.9-22.1 has caused the Debian Bug report #932534, regarding longrun: Uses manual dh sequence operations that are going to be removed to be marked as done. This means that you claim

Processed: Bug#932679 marked as pending in python-networkx

2019-11-07 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #932679 [src:python-networkx] python-networkx: Don't depend on python-gdal Added tag(s) pending. -- 932679: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=932679 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems