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 
> removed?)

Seems fine to me that projects targeting python library namespaces use 
"python-" prefix for source packages, indicating the _family_ of 
Pythonic namespaces.

 - Jonas

-- 
 * Jonas Smedegaard - idealist & Internet-arkitekt
 * Tlf.: +45 40843136  Website: http://dr.jones.dk/

 [x] quote me freely  [ ] ask before reusing  [ ] keep private


signature.asc
Description: signature


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+
* Vcs : https://github.com/rd235/cado
  Programming Lang: C
  Description : Capability Ambient DO

Cado permits the delegation of capabilities to users. Cado is a capability
based sudo. Sudo allows authorized users to run programs as root (or as
another user), cado permits authorized users to run programs with specific
(ambient) capabilities. Cado is more selective than sudo, users can be
authorized to have only specific capabilities (and not others).

I will be the maintainer of the package.



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 of them would fix the issue.
> That is not a bug, but rather a feature that is solving previous bugs [1] and
> [2]
> 
> The issue is that I copied some code from the Debian policy manual [3] and
> that code was wrong:
> 
> The given example is missing closing bracket. I should noticed it before, but
> for some obscure reason it is passing on my computer:
> if [ upgrade != "$1 || dpkg --compare-versions "$2" lt 1.0-2; thenI've checked
> it again and I've fixed it. Will upload soon.
> 
> [1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=823706
> [2] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=898310
> [3] https://www.debian.org/doc/debian-policy/ap-pkg-diversions.html
> -- 
> Cheers,Abou Al Montacir
> 
> ___Pkg-pascal-devel mailing 
> listpkg-pascal-de...@alioth-lists.debian.net
> https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-pascal-devel
-- 
Cheers,
Abou Al Montacir



signature.asc
Description: This is a digitally signed message part


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
> otherwise unrelated exist; or when the same binary is built from
> different sources on different architectures; or when binary and source
> versions don't match (version tracking really should use source
> versions).  In addition there are issues when binary packages get
> renamed (e.g. when libfoo1 gets dropped in favor of libfoo2).
>
> I believe bugs should always be assigned to source packages as source
> packages are really the unit we use to keep track of packages.

Fully agreed. It's also hard for users to pinpoint the correct binary
package and they tend to get stale with changes to binary names anyway
(soname changes to libs etc.)

Cheers,
Moritz



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 one might expect ;)

Kind regards,
Andrei
-- 
http://wiki.debian.org/FAQsFromDebianUser


signature.asc
Description: PGP signature


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 closing bracket. I should noticed it
>> before, but for some obscure reason it is passing on my computer:

>> if [ upgrade != "$1 || dpkg --compare-versions "$2" lt 1.0-2; then

>> I've checked it again and I've fixed it. Will upload soon.

Indeed, that's a bug.  Thank you!  The automated conversion to
reStructuredText wasn't perfect, and we missed a few issues like this.

Now fixed for the next release.

-- 
Russ Allbery (r...@debian.org)  



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#issuecomment-519620678

A few weeks ago I have uploaded doxygen 1.8.16-1~exp3 to experimental.
I have also run a ratt job (https://github.com/debian/ratt) on amd64.
Of 722 reverse build dependencies:
- 86 failed the build
- of those 70 also fail without the new doxygen (could be proper FTBFS or
something with my setup like insufficient memory, timeout etc).
- the remaining 16 failures could be related to the new doxygen version.

2 are false positives (did not fail when manually rebuilt):
- libsigrok
- libtrace3

These 4:
- apophenia
- libemf
- libgnomecanvasmm2.6
- siscone
failed because of https://github.com/doxygen/doxygen/issues/7190
for that I included the patch from upstream here: 
https://salsa.debian.org/debian/doxygen/blob/master/debian/patches/blank-file-patterns.diff

The 10 remaining packages all fail with latex-related errors.
Unfortunately I know nothing about latex so I cant' help with those.
But I filed bugs or updated the existing open bug:
- ccfits, "Overfull \hbox" latex error, see: https://bugs.debian.org/943423
- fltk1.3, "! Undefined control sequence." latex error, see: 
https://bugs.debian.org/943426
- frobby, LaTeX Error: File `listofitems.sty' not found, see: 
https://bugs.debian.org/921300
- lapack, easy to fix by just removing one line from d/rules, see: 
https://bugs.debian.org/943431
- librostlab, LaTeX Error: File `listofitems.sty' not found, see: 
https://bugs.debian.org/943420
- libstxxl, LaTeX Error: File `listofitems.sty' not found, see: 
https://bugs.debian.org/921298
- openms, "! Undefined control sequence." latex error, see: 
https://bugs.debian.org/943450
- ppl, "! Undefined control sequence." latex error, see: 
https://bugs.debian.org/943451
- qevercloud, LaTeX Error: File `listofitems.sty' not found, see: 
https://bugs.debian.org/921297
- sdformat, LaTeX Error: File `listofitems.sty' not found, see: 
https://bugs.debian.org/943421

In a couple of weeks I'll upload to unstable, so we'll see what happens on 
non-amd64 archs.
I hope in the meantime we can address the 10 packages we already know will fail 
on amd64.

Paolo



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 enumerate domain DNS information

 Dnsenum is a multithreaded perl script to enumerate DNS information of a
 domain and to discover non-contiguous ip blocks. The main purpose of Dnsenum
 is to gather as much information as possible about a domain. The program
 currently performs the following operations:
 .
   1) Get the host's addresses (A record).
   2) Get the namservers (threaded).
   3) Get the MX record (threaded).
   4) Perform axfr queries on nameservers and get BIND versions(threaded).
   5) Get extra names and subdomains via google scraping (google query =
  "allinurl: -www site:domain").
   6) Brute force subdomains from file, can also perform recursion on subdomain
  that have NS records (all threaded).
   7) Calculate C class domain network ranges and perform whois queries on them
  (threaded).
   8) Perform reverse lookups on netranges (C class or/and whois netranges)
  (threaded).
   9) Write to domain_ips.txt file ip-blocks.
 .
 This program is useful for pentesters, ethical hackers and forensics experts.
 It also can be used for security tests.


I will maintain this package inside Debian Security Tools Packaging Team.



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 requested help for: 54 (new: 0)

Please refer to https://www.debian.org/devel/wnpp/ for more information.



The following packages have been orphaned:

   sopel (#943404), orphaned today
 Description: simple, lightweight, open source, easy-to-use IRC
   utility bot
 Installations reported by Popcon: 9
 Bug Report URL: https://bugs.debian.org/943404

1262 older packages have been omitted from this listing, see
https://www.debian.org/devel/wnpp/orphaned for a complete list.



The following packages have been given up for adoption:

   dh-make-elpa (#942642), offered 5 days ago
 Description: helper for creating Debian packages from ELPA packages
 Installations reported by Popcon: 37
 Bug Report URL: https://bugs.debian.org/942642

   python-dnsq (#942724), offered 4 days ago
 Description: Python DNS query tool
 Installations reported by Popcon: 26
 Bug Report URL: https://bugs.debian.org/942724

   python-requests-toolbelt (#943419), offered today
 Description: Utility belt for advanced users of python-requests
 Reverse Depends: mlbstreamer python3-acme python3-bioblend
   python3-flickrapi python3-jira python3-marathon python3-pylxd
   python3-zeep twine vdirsyncer
 Installations reported by Popcon: 8593
 Bug Report URL: https://bugs.debian.org/943419

246 older packages have been omitted from this listing, see
https://www.debian.org/devel/wnpp/rfa_bypackage for a complete list.



For the following packages help is requested:

   autopkgtest (#846328), requested 1058 days ago
 Description: automatic as-installed testing for Debian packages
 Reverse Depends: debci-worker
 Installations reported by Popcon: 1177
 Bug Report URL: https://bugs.debian.org/846328

   balsa (#642906), requested 2951 days ago
 Description: An e-mail client for GNOME
 Installations reported by Popcon: 699
 Bug Report URL: https://bugs.debian.org/642906

   broadcom-sta (#886599), requested 654 days ago (non-free)
 Description: Broadcom STA Wireless driver (non-free)
 Installations reported by Popcon: 1794
 Bug Report URL: https://bugs.debian.org/886599

   cargo (#860116), requested 926 days ago
 Description: Rust package manager
 Reverse Depends: dh-cargo
 Installations reported by Popcon: 1282
 Bug Report URL: https://bugs.debian.org/860116

   cyrus-sasl2 (#799864), requested 1492 days ago
 Description: authentication abstraction library
 Reverse Depends: 389-ds-base adcli autofs-ldap
   cairo-dock-mail-plug-in cyrus-caldav cyrus-clients cyrus-common
   cyrus-dev cyrus-imapd cyrus-imspd (77 more omitted)
 Installations reported by Popcon: 202263
 Bug Report URL: https://bugs.debian.org/799864

   dee (#831388), requested 1196 days ago
 Description: model to synchronize mutiple instances over DBus
 Reverse Depends: dee-tools gir1.2-dee-1.0 libdee-dev zeitgeist-core
 Installations reported by Popcon: 43532
 Bug Report URL: https://bugs.debian.org/831388

   developers-reference (#759995), requested 1881 days ago
 Description: guidelines and information for Debian developers
 Installations reported by Popcon: 8102
 Bug Report URL: https://bugs.debian.org/759995

   devscripts (#800413), requested 1486 days ago
 Description: scripts to make the life of a Debian Package maintainer
   easier
 Reverse Depends: apt-build apt-listdifferences aptfs arriero
   brz-debian customdeb debci debian-builder debmake debpear (31 more
   omitted)
 Installations reported by Popcon: 12061
 Bug Report URL: https://bugs.debian.org/800413

   docker.io (#908868), requested 404 days ago
 Description: Linux container runtime
 Reverse Depends: golang-docker-dev
   golang-github-containers-image-dev
   golang-github-containers-storage-dev
   golang-github-fsouza-go-dockerclient-dev
   golang-github-google-cadvisor-dev
   golang-github-openshift-imagebuilder-dev
   golang-github-samalba-dockerclient-dev kubernetes-node subuser
   whalebuilder
 Installations reported by Popcon: 2380
 Bug Report URL: https://bugs.debian.org/908868

   ed (#886643), requested 654 days ago
 Description: classic UNIX line editor
 Reverse Depends: apt-cacher libdebbugs-perl opensmtpd sn
 Installations reported by Popcon: 16234
 Bug Report URL: https://bugs.debian.org/886643

   ejabberd (#767874), requested 1816 days ago