Re: NMUs: Do we want to Require or Recommend DH

2019-05-15 Thread Jonas Smedegaard
Quoting Scott Kitterman (2019-05-15 04:47:48) > > > On May 15, 2019 1:13:52 AM UTC, Paul Wise wrote: > >On Wed, May 15, 2019 at 2:31 AM Sam Hartman wrote: > > > >> How do we feel about people making build system conversions when > >> those conversion make it easier to fix some other bug that th

Re: Do we want to Require or Recommend DH

2019-05-15 Thread Simon McVittie
On Mon, 13 May 2019 at 17:58:47 +0200, Thomas Goirand wrote: > Now, I have another example, which is quite the opposite one of what you > gave as example: > > https://salsa.debian.org/openstack-team/debian/openstack-debian-images/blob/debian/stein/debian/rules > > Why would one want to switch tha

Re: QA expectations (Was: Do we want to Require or Recommend DH)

2019-05-15 Thread Simon McVittie
On Tue, 14 May 2019 at 18:19:47 +0200, Johannes Schauer wrote: > So maybe instead of creating unstable-proposed, stuff should move from > buildd-unstable to unstable only after it successfully passed all kinds of > automatable QA tests? Prior art: Ubuntu already does this, gating the transition wi

Re: NMUs: Do we want to Require or Recommend DH

2019-05-15 Thread Enrico Zini
On Tue, May 14, 2019 at 02:30:52PM -0400, Sam Hartman wrote: > How do we feel about people making build system conversions when those > conversion make it easier to fix some other bug that they are fixing as > part of an NMU? > That is, imagine that a package is mishandling the combination of > sy

Nie masz pomysłu na nowy post? Poprowadzimy Twój FanPage.

2019-05-15 Thread Twój Zleceniobiorca . FanPage na Facebook'u .
Dzień dobry, pragniemy zwrócić Państwa uwagę na jedną z najskuteczniejszych metod pozyskiwania klientów oraz zarabiania pieniędzy. Jesteśmy profesjonalistami, którzy skutecznie administrują *_FanPage’ami na Facebook’u. _* Dzięki zgromadzonemu doświadczeniu możemy śmiało powiedzieć, że gr

Re: NMUs: Do we want to Require or Recommend DH

2019-05-15 Thread Jonas Smedegaard
Quoting Enrico Zini (2019-05-15 11:31:46) > On Tue, May 14, 2019 at 02:30:52PM -0400, Sam Hartman wrote: > > > How do we feel about people making build system conversions when > > those conversion make it easier to fix some other bug that they are > > fixing as part of an NMU? > > That is, imagi

dh_testroot usage is still always required (was Re: Do we want to Require or Recommend DH)

2019-05-15 Thread Guillem Jover
On Wed, 2019-05-15 at 09:18:26 +0100, Simon McVittie wrote: > It uses dh_testroot, so it probably can't have Rules-Requires-Root: no, > and needs to be built as (fake)root indefinitely - even though a package > this simple can almost certainly be built correctly without fakeroot. You've mention th

Re: NMUs: Do we want to Require or Recommend DH

2019-05-15 Thread Benjamin Drung
Am Mittwoch, den 15.05.2019, 11:31 +0200 schrieb Enrico Zini: > I'd propose to recommend dh as the default build system, and document > in README.source if there are reasons to use something else. > > At that point, one could look at README.source to see if changing > build system would be an poss

Re: binutils security support (Re: fixing debian-security-support upgrades from stretch (for good))

2019-05-15 Thread Holger Levsen
On Tue, May 14, 2019 at 11:39:50PM +0200, Moritz Mühlenhoff wrote: > Holger Levsen schrieb: > > (and yes, I also agree this is quite a desaster, just like > > kde4libs/khtml only is suitable for trusted content, which IOW means, > > one should not use konqueror or kmail on the interweb.) > That is

Re: NMUs: Do we want to Require or Recommend DH

2019-05-15 Thread Ian Jackson
Enrico Zini writes ("Re: NMUs: Do we want to Require or Recommend DH"): > I'd propose to recommend dh as the default build system, and document in > README.source if there are reasons to use something else. > > At that point, one could look at README.source to see if changing build > system would

Re: NMUs: Do we want to Require or Recommend DH

2019-05-15 Thread Andreas Tille
Hi, On Wed, May 15, 2019 at 02:09:14PM +0200, Benjamin Drung wrote: > Am Mittwoch, den 15.05.2019, 11:31 +0200 schrieb Enrico Zini: > > I'd propose to recommend dh as the default build system, and document > > in README.source if there are reasons to use something else. > > > > At that point, one

Re: Do we want to Require or Recommend DH

2019-05-15 Thread Jonathan Dowland
On Tue, May 14, 2019 at 02:27:30PM +0800, Paul Wise wrote: I think conversion to dh should only be done when doing hostile hijacking of packages, salvaging packages, adopting packages, orphaning packages or team/maintainer uploads and only if the person doing the conversion builds the package twi

Bug#929024: ITP: routinator -- An RPKI Validator

2019-05-15 Thread Marco d'Itri
Package: wnpp Severity: wishlist Owner: Marco d'Itri * Package name: routinator Version : 0.3.3 Upstream Author : NLnet Labs * URL : https://nlnetlabs.nl/rpki * License : BSD Programming Lang: Rust Description : An RPKI Validator The Routinator 3000 is

Re: Do we want to Require or Recommend DH

2019-05-15 Thread Jonathan Dowland
On Mon, May 13, 2019 at 05:58:47PM +0200, Thomas Goirand wrote: Why would one want to switch that one to something else? The package, basically, consists of a shell script and a man page only. The minimalism of this package doesn't require an over-engineered dh sequencer, does it? I maintain on

Towards lapack / lapack64 packaging

2019-05-15 Thread Mo Zhou
Hi science team, I'm trying to add multi-flavor support to the openblas package, as a part of the ongoing BLAS64 + LAPACK64 work. However, there is some problems need to be discussed. Two problems will be discussed in this email: (1) building problem about OpenBLAS's liblapack64.so (2) confirming

Re: QA expectations (Was: Do we want to Require or Recommend DH)

2019-05-15 Thread Helmut Grohne
On Wed, May 15, 2019 at 09:28:59AM +0100, Simon McVittie wrote: > Prior art: Ubuntu already does this, gating the transition with a version > of Debian's testing migration scripts that has been configured for a 0 day > delay for all urgencies. Yes. Colin Watson even had a talk about this in Vaumar

Re: Towards lapack / lapack64 packaging

2019-05-15 Thread Sébastien Villemot
Hi Lumin, Le mercredi 15 mai 2019 à 08:39 -0700, Mo Zhou a écrit : > (1) building problem about OpenBLAS's liblapack64.so > - > > Sébastien provided some possible solutions: > > 1. build a 64-bit indexing variant of src:lapack > 2. provide

Bug#929040: ITP: tty-solitaire -- klondike solitaire game for text terminal

2019-05-15 Thread Marcin Owsiany
Package: wnpp Severity: wishlist Owner: Marcin Owsiany * Package name: tty-solitaire Version : 1.1.1 Upstream Author : Murilo Pereira * URL : https://github.com/mpereira/tty-solitaire * License : MIT Programming Lang: C Description : klondike solitaire

Re: Do we want to Require or Recommend DH

2019-05-15 Thread Tollef Fog Heen
]] Andreas Tille > Can you give an example for a package that has a non-dh rules file > "working for years" that gives as a result a package with no lintian > warnings without changing this d/rules file? If you're talking about the binary package, fortunes-bofh-excuses. It has some lintian warn

Bug#929047: ITP: libubootenv -- Library to access U-Boot environment

2019-05-15 Thread Nobuhiro Iwamatsu
Package: wnpp Severity: wishlist Owner: Nobuhiro Iwamatsu * Package name: libubootenv Version : 0.1 Upstream Author : Stefano Babic * URL : https://github.com/sbabic/libubootenv * License : LGPL-2.1 Programming Lang: C Description : Library to access U

Re: dgit FAQ

2019-05-15 Thread Sean Whitton
Hello, On Tue 14 May 2019 at 01:59PM +10, Ben Finney wrote: > One issue I noticed: > > git-buildpackage and git-dpm users are fully supported […] > > That seems to contradict earlier statements that “separate > Debian-packaging-only repository” workflow (which is supported by > Git-BuildPacka

Re: Do we want to Require or Recommend DH

2019-05-15 Thread Sean Whitton
Hello, On Tue 14 May 2019 at 12:30PM +01, Ian Jackson wrote: > Sean Whitton writes ("Re: Do we want to Require or Recommend DH"): >> I agree with Scott's emphasis on the distinction between new and >> existing packages. Perhaps application of the distinction could be >> extended: perhaps there a

Re: Towards lapack / lapack64 packaging

2019-05-15 Thread Mo Zhou
Hi Sébastien, On 2019-05-15 16:23, Sébastien Villemot wrote: >> Sébastien provided some possible solutions: >> >> 1. build a 64-bit indexing variant of src:lapack >> 2. provide a liblapack64-pic (Sébastien prefer this) > > First, note that solution 1 is a superset of solution 2 (i.e. we would

Re: Do we want to Require or Recommend DH

2019-05-15 Thread Andreas Tille
Hi Tollef, On Wed, May 15, 2019 at 09:54:50PM +0200, Tollef Fog Heen wrote: > ]] Andreas Tille > > > Can you give an example for a package that has a non-dh rules file > > "working for years" that gives as a result a package with no lintian > > warnings without changing this d/rules file? > > I