Re: Updating the policy for conflicting binaries names ? [was: Re: Re: New package netgen-lvs with binary /usr/bin/netgen - already taken]

2018-09-08 Thread Andrey Rahmatullin
On Sat, Sep 08, 2018 at 06:07:43PM -0300, David Bremner wrote: > Andrey Rahmatullin writes: > > > Last upload of ax25-node was in 2008, in 2009 it was effectively orphaned, > > the TC bug was filed in 2011 and resolved in 2012, in 2015 ax25-node was > > removed with "ROM; no activity, open securi

Re: Updating the policy for conflicting binaries names ? [was: Re: Re: New package netgen-lvs with binary /usr/bin/netgen - already taken]

2018-09-08 Thread Guillem Jover
Hi! On Sat, 2018-09-08 at 20:18:10 +0200, Sylvestre Ledru wrote: > Le 08/09/2018 à 18:39, Sean Whitton a écrit : > > On Fri 07 Sep 2018 at 10:10PM +0200, Ruben Undheim wrote: > > > However, I think the policy gives us a lot of freedom to choose (it > > > is not very strict in this case). > > > >

Re: Updating the policy for conflicting binaries names ? [was: Re: Re: New package netgen-lvs with binary /usr/bin/netgen - already taken]

2018-09-08 Thread Russ Allbery
Paride Legovini writes: > However, there are clearly cases where renaming binaries makes several > people unhappy (most likely: the package maintainers, upstream, people > writing scripts, users of different distributions), while not making a > single user happier. This is especially true with lo

Re: New package netgen-lvs with binary /usr/bin/netgen - already taken

2018-09-08 Thread Kurt Kremitzki
> Hello, > > On Sat 08 Sep 2018 at 07:31PM +0200, Ruben Undheim wrote: > >> Yes, you are right, when I read it again. What I have been "reading" before >> is. >> >> "Two different packages must not install programs with different >> functionality >> but with the same filenames if they do not

Re: Updating the policy for conflicting binaries names ? [was: Re: Re: New package netgen-lvs with binary /usr/bin/netgen - already taken]

2018-09-08 Thread Martin Steigerwald
Sean Whitton - 08.09.18, 21:03: > My understanding is that there are quite deep social reasons for the > current policy (please note, though, that I was not involved in Debian > when this piece of policy was created; neither was I involved during > the nodejs TC decision). > > The current policy p

Re: Updating the policy for conflicting binaries names ? [was: Re: Re: New package netgen-lvs with binary /usr/bin/netgen - already taken]

2018-09-08 Thread David Bremner
Andrey Rahmatullin writes: > Last upload of ax25-node was in 2008, in 2009 it was effectively orphaned, > the TC bug was filed in 2011 and resolved in 2012, in 2015 ax25-node was > removed with "ROM; no activity, open security issues, de facto orphaned" > (the status that was true when the TC bug

Re: New package netgen-lvs with binary /usr/bin/netgen - already taken

2018-09-08 Thread Ruben Undheim
> stupid idea: > > do these scripts (and other consumers of the netgen binaries) actually > use the fully qualified "/usr/bin/netgen" or just an unqualified "netgen"? > > if the latter, you might just put the unchanged names into something > like /usr/share/netgen/bin/ and tell users to add to th

Re: New package netgen-lvs with binary /usr/bin/netgen - already taken

2018-09-08 Thread Ruben Undheim
Hi David, > I may have missed it, but it looks like you didn’t ask directly the > netgen maintainers (or explicitly CC them during this discussion). Maybe > a first good step is to communicate with them and ask what is their take > on that matter If there is no way to actually share a file name w

Re: Updating the policy for conflicting binaries names ? [was: Re: Re: New package netgen-lvs with binary /usr/bin/netgen - already taken]

2018-09-08 Thread Paride Legovini
Hello Sean, Sean Whitton wrote on 08/09/2018: > Hello Sylvestre, > > On Sat 08 Sep 2018 at 08:18PM +0200, Sylvestre Ledru wrote: > >> Renaming binaries is a big pain, it is confusing for the user, making the >> life of the maintainer >> harder, the documentations won't reflect the Debian-realit

Re: Updating the policy for conflicting binaries names ? [was: Re: Re: New package netgen-lvs with binary /usr/bin/netgen - already taken]

2018-09-08 Thread Ruben Undheim
Hi, > > Renaming binaries is a big pain, it is confusing for the user, making the > > life of the maintainer > > harder, the documentations won't reflect the Debian-reality. > > > > The wording should be changed from "must" to "should": > > --- > > Two different packages should not install progra

Re: Updating the policy for conflicting binaries names ? [was: Re: Re: New package netgen-lvs with binary /usr/bin/netgen - already taken]

2018-09-08 Thread Andrey Rahmatullin
On Sat, Sep 08, 2018 at 12:03:18PM -0700, Sean Whitton wrote: > My understanding is that there are quite deep social reasons for the > current policy (please note, though, that I was not involved in Debian > when this piece of policy was created; neither was I involved during the > nodejs TC decisi

Re: Updating the policy for conflicting binaries names ? [was: Re: Re: New package netgen-lvs with binary /usr/bin/netgen - already taken]

2018-09-08 Thread Sean Whitton
Hello Sylvestre, On Sat 08 Sep 2018 at 08:18PM +0200, Sylvestre Ledru wrote: > Renaming binaries is a big pain, it is confusing for the user, making the > life of the maintainer > harder, the documentations won't reflect the Debian-reality. > > The wording should be changed from "must" to "shoul

Re: Updating the policy for conflicting binaries names ? [was: Re: Re: New package netgen-lvs with binary /usr/bin/netgen - already taken]

2018-09-08 Thread Shengjing Zhu
On Sun, Sep 9, 2018 at 2:29 AM Sylvestre Ledru wrote: > > Hello, > > Le 08/09/2018 à 18:39, Sean Whitton a écrit : > > Hello, > > > > On Fri 07 Sep 2018 at 10:10PM +0200, Ruben Undheim wrote: > > > >> However, I think the policy gives us a lot of freedom to choose (it is not > >> very > >> strict

Re: New package netgen-lvs with binary /usr/bin/netgen - already taken

2018-09-08 Thread Sean Whitton
Hello, On Sat 08 Sep 2018 at 07:31PM +0200, Ruben Undheim wrote: > Yes, you are right, when I read it again. What I have been "reading" before > is. > > "Two different packages must not install programs with different > functionality > but with the same filenames if they do not declare that t

Updating the policy for conflicting binaries names ? [was: Re: Re: New package netgen-lvs with binary /usr/bin/netgen - already taken]

2018-09-08 Thread Sylvestre Ledru
Hello, Le 08/09/2018 à 18:39, Sean Whitton a écrit : > Hello, > > On Fri 07 Sep 2018 at 10:10PM +0200, Ruben Undheim wrote: > >> However, I think the policy gives us a lot of freedom to choose (it is not >> very >> strict in this case). > > I don't understand. This seems pretty strict: > >

Re: New package netgen-lvs with binary /usr/bin/netgen - already taken

2018-09-08 Thread David Prévot
Le 08/09/2018 à 07:31, Ruben Undheim a écrit : > And it also means that the package pair "nodejs-legacy" and "node" was RC > buggy when the packages were present (jessie I guess) You may have a look at the TC ruling for a bit of context for node. https://bugs.debian.org/614907 > Does anyone kno

Re: New package netgen-lvs with binary /usr/bin/netgen - already taken

2018-09-08 Thread Ruben Undheim
Hi Sean, > > However, I think the policy gives us a lot of freedom to choose (it is not > > very > > strict in this case). > > I don't understand. This seems pretty strict: > > Two different packages must not install programs with different > functionality but with the same filenames.

Re: Browserified copy and DFSG

2018-09-08 Thread Shengjing Zhu
(drop pkg-javascript-devel) On Sun, Sep 9, 2018 at 12:52 AM Sean Whitton wrote: > > Hello, > > On Sat 08 Sep 2018 at 10:02AM +0800, Paul Wise wrote: > > > On Fri, Sep 7, 2018 at 7:22 PM, Bastien ROUCARIES wrote: > > > >> Ok adding cc @security > >> > >> How will you handle security problem in sta

Re: Browserified copy and DFSG

2018-09-08 Thread Sean Whitton
Hello, On Sat 08 Sep 2018 at 10:02AM +0800, Paul Wise wrote: > On Fri, Sep 7, 2018 at 7:22 PM, Bastien ROUCARIES wrote: > >> Ok adding cc @security >> >> How will you handle security problem in static >> (browserified/webpacked) javascript library ? > > Same goes for the other languages that do s

Re: New package netgen-lvs with binary /usr/bin/netgen - already taken

2018-09-08 Thread Sean Whitton
Hello, On Fri 07 Sep 2018 at 10:10PM +0200, Ruben Undheim wrote: > However, I think the policy gives us a lot of freedom to choose (it is not > very > strict in this case). I don't understand. This seems pretty strict: Two different packages must not install programs with different fu

Bug#908325: ITP: node-chart.js -- Simple HTML5 charts using the canvas element

2018-09-08 Thread Pirate Praveen
Package: wnpp Severity: wishlist Owner: Pirate Praveen X-Debbugs-CC: debian-devel@lists.debian.org * Package name: node-chart.js Version : 1.0.2 Upstream Author : Nick Downie * URL : http://www.chartjs.org * License : Expat Programming Lang: JavaScript Desc

Bug#908314: ITP: rustfmt -- Find and fix Rust formatting issues

2018-09-08 Thread Sylvestre Ledru
Package: wnpp Severity: wishlist Owner: Rust Maintainers * Package name: rustfmt * URL : https://github.com/rust-lang-nursery/rustfmt * License : MIT license and the Apache License Programming Lang: Rust Description : Find and fix Rust formatting issues clang-form

Bug#908312: ITP: cbindgen -- Generating C bindings to Rust code

2018-09-08 Thread Sylvestre Ledru
Package: wnpp Severity: wishlist Owner: Rust Maintainers * Package name: cbindgen Version : 0.6.3 * URL : https://github.com/eqrion/cbindgen * License : MPL Programming Lang: Rust Description : Generating C bindings to Rust code