Re: Introducting Debian Trends: historical graphs about Debian packaging practices, and "packages smells"

2019-04-15 Thread Andreas Tille
On Mon, Apr 15, 2019 at 05:35:40PM +0200, Bastian Blank wrote: > On Mon, Apr 15, 2019 at 04:55:12PM +0200, Andreas Tille wrote: > > biococoa (U) does not use Debhelper (no compat level found) > > (source version: 2.2.2-4) > > biococoa (U) should switch to dh. Current build

Re: native packages? (Re: Introducting Debian Trends: historical graphs about Debian packaging practices, and "packages smells")

2019-04-15 Thread Simon Richter
Hi, On 15.04.19 21:23, Marco d'Itri wrote: > Generating an upstream tarball in this case is still useful because this > way we do not need to upload and store forever the full source archive > every time that something changes only in the packaging. That, and upstream tarballs generated with "g

Re: native packages? (Re: Introducting Debian Trends: historical graphs about Debian packaging practices, and "packages smells")

2019-04-15 Thread Marco d'Itri
On Apr 15, Sam Hartman wrote: > However if my sources are in git, git is the definitive format for > thinking about things, and the dsc I'm producing is only for the > convenience of the archive, I don't want to deal with an upstream > tarball. Generating an upstream tarball in this case is still

Bug#927170: RFP: jadx -- Android Dex decompiler

2019-04-15 Thread Giovanni Mascellani
Package: wnpp Severity: wishlist X-Debbugs-CC: debian-devel@lists.debian.org Package name: jadx Version: 0.9.0 Upstream Author: Skylot URL: https://github.com/skylot/jadx License: Apache-2.0 Description: Android Dex decompiler Jadx is a decompiler for Android Dex

Re: native packages? (Re: Introducting Debian Trends: historical graphs about Debian packaging practices, and "packages smells")

2019-04-15 Thread Sam Hartman
> "Holger" == Holger Levsen writes: Holger> On Sat, Apr 13, 2019 at 01:48:01PM +0100, Simon McVittie wrote: >> On Sat, 13 Apr 2019 at 10:04:10 +, Holger Levsen wrote: >> > I see no point whatsoever in 3.0 (native). The main advantage >> of 3.0 (native) is that it makes it

Re: Introducting Debian Trends: historical graphs about Debian packaging practices, and "packages smells"

2019-04-15 Thread Lucas Nussbaum
On 15/04/19 at 16:55 +0200, Andreas Tille wrote: > Are you sure that you are not tricked by false positives from lintian? I might be, but if lintian reports something incorrectly about your package, it's probably worth fixing in lintian. Lucas

Re: Introducting Debian Trends: historical graphs about Debian packaging practices, and "packages smells"

2019-04-15 Thread Bastian Blank
On Mon, Apr 15, 2019 at 04:55:12PM +0200, Andreas Tille wrote: > biococoa (U) does not use Debhelper (no compat level found) > (source version: 2.2.2-4) > biococoa (U) should switch to dh. Current build system: cdbs > (source version: 2.2.2-4) | % grep cdbs -r biococoa-2.

Re: Introducting Debian Trends: historical graphs about Debian packaging practices, and "packages smells"

2019-04-15 Thread Andreas Tille
On Sat, Apr 13, 2019 at 03:46:57PM +0200, gregor herrmann wrote: > On Sat, 13 Apr 2019 10:20:53 +0200, Lucas Nussbaum wrote: > > > TL;DR: see https://trends.debian.net and > > https://trends.debian.net/#smells > > Very nice, thank you. +1 I like it a lot! > > [4] https://trends.debian.net/smell

Re: Golang >= 1.12 in Buster?

2019-04-15 Thread Thomas Goirand
On 4/14/19 1:00 PM, Toni Mueller wrote: > Or how about removing Python2 altogether, then? That's actually not a bad idea, which we considered, and only postponed until Buster is out. FYI, I already started removing Python 2 support in many of the packages I maintain (currently only uploaded to Exp

Re: Golang >= 1.12 in Buster?

2019-04-15 Thread Thomas Goirand
On 4/15/19 9:24 AM, Hideki Yamane wrote: > On Sun, 14 Apr 2019 21:11:09 +0200 > "Dr. Tobias Quathamer" wrote: >> I think it's the right decision of the release team to stick with golang >> 1.11 for buster. The previous migration from golang 1.10 to 1.11 took us >> about four weeks until we had fix

Re: Golang >= 1.12 in Buster?

2019-04-15 Thread Hideki Yamane
On Sun, 14 Apr 2019 21:11:09 +0200 "Dr. Tobias Quathamer" wrote: > I think it's the right decision of the release team to stick with golang > 1.11 for buster. The previous migration from golang 1.10 to 1.11 took us > about four weeks until we had fixed all packages with new FTBFS bugs. Can we mi