Re: +1 (Re: should all bug reports be filed against /source/ packages?)

2019-10-24 Thread Gianfranco Costamagna
I agree. With python2 being removed, we will have a lot of "src:python-foo" providing only a "bin:python3-foo" so this confusion will be even more a problem... (will we ever rename also source packages now that python2 is going to be removed?) Gianfranco

Re: +1 (Re: should all bug reports be filed against /source/ packages?)

2019-10-24 Thread Jonas Smedegaard
Quoting Gianfranco Costamagna (2019-10-24 12:31:51) > I agree. > > With python2 being removed, we will have a lot of > "src:python-foo" providing only a "bin:python3-foo" > so this confusion will be even more a problem... > (will we ever rename also source packages now that python2 is going to be

Bug#943411: ITP: cado -- Capability Ambient DO

2019-10-24 Thread Mattia Biondi - mattia.bion...@studio.unibo.it
Package: wnpp Severity: wishlist Owner: Mattia Biondi * Package name: cado Section : admin Version : 0.9.2 Upstream Author : Davide Berardi, Renzo Davoli - VirtualSquare/University of Bologna * URL : http://wiki.virtualsquare.org * License : GPL-2+ *

Possible bug in policy?

2019-10-24 Thread Abou Al Montacir
Dear all, Can you please see thebelow mail and confirm there is a real bug? On Tue, 2019-10-22 at 22:22 +0200, Abou Al Montacir wrote: > Hi Jan, Hi Andreas, > > > both contains the same file, namely > > /usr/lib/lazarus/2.0.2/components/IdeInspector/ideinspector.lpk > > and removing it from one

Re: should all bug reports be filed against /source/ packages?

2019-10-24 Thread Moritz Mühlenhoff
Ansgar schrieb: > the thread about naming (source) packages reminded me of an other thing: > Debian's bug tracking system currently (mostly) tracks bugs against > binary packages and (less often) against source packages. > > It gets confused if a source & binary package with the same name, but > o

Re: should all bug reports be filed against /source/ packages?

2019-10-24 Thread Andrei POPESCU
On Mi, 23 oct 19, 08:32:11, Ansgar wrote: > > Reportbug could probably be easily changed to use > `Source: ...` instead of `Package: ...`; more places could follow later. Beware of #721793, though I'm guessing the reportbug maintainer is aware that 'Source: ' doesn't do what o

Re: Possible bug in policy?

2019-10-24 Thread Russ Allbery
Abou Al Montacir writes: > Can you please see thebelow mail and confirm there is a real bug? > On Tue, 2019-10-22 at 22:22 +0200, Abou Al Montacir wrote: >> The issue is that I copied some code from the Debian policy manual [3] and >> that code was wrong: >> The given example is missing closin

doxygen 1.8.16 is ready for unstable, 10+ packages will FTBFS on amd64

2019-10-24 Thread Paolo Greppi
Hi, ATM doxygen is stuck at 1.8.13 because during the freeze 1.8.15 caused ~20 FTBFS and it was decided to keep it out of buster. Many issues were related to latex + tabu, now upstream has released 1.8.16 and they claim they fixed the tabu issues: https://github.com/doxygen/doxygen/issues/6769#is

Bug#943460: ITP: dnsenum -- tool to enumerate domain DNS information

2019-10-24 Thread Joao Eriberto Mota Filho
Package: wnpp Severity: wishlist Owner: Joao Eriberto Mota Filho * Package name: dnsenum Version : 1.3.0 Upstream Author : Network Silence * URL : https://github.com/SparrowOchon/dnsenum2 * License : GPL-2+ Programming Lang: Perl Description : tool to

Work-needing packages report for Oct 25, 2019

2019-10-24 Thread wnpp
The following is a listing of packages for which help has been requested through the WNPP (Work-Needing and Prospective Packages) system in the last week. Total number of orphaned packages: 1263 (new: 1) Total number of packages offered up for adoption: 249 (new: 3) Total number of packages reques