Bug#885404: Acknowledgement (duc-nox: please provide bin/duc in duc-nox package)

2018-01-02 Thread Jonathan Dowland
Hi Herbert, On Mon, Jan 01, 2018 at 02:38:41PM -0200, Herbert Fortes wrote: I opened an 'O' bug and you can take the maintenance of the package. Which is in good shape. OK, thank you (yes it is in good shape). Thank you for packaging duc and all your work on it. You will always be welcome to c

Bug#885404: Acknowledgement (duc-nox: please provide bin/duc in duc-nox package)

2018-01-01 Thread Herbert Fortes
Hi Jonathan, You have more interesting in the package than me. I opened an 'O' bug and you can take the maintenance of the package. Which is in good shape. Do not worry about anything. Kind Regards, Herbert

Bug#885404: Acknowledgement (duc-nox: please provide bin/duc in duc-nox package)

2017-12-31 Thread Herbert Fortes
On 30/12/2017 13:41, Andrew Shadura wrote: Hi, On 30 December 2017 at 11:53, Herbert Fortes wrote: But I do not understand. It seems to me that an alias solves the issue. And the user can set anything he wants. Base on that, the use of 'Conflicts' seems too much. It changes a lot of things.

Bug#885404: Acknowledgement (duc-nox: please provide bin/duc in duc-nox package)

2017-12-31 Thread Herbert Fortes
use collab-maint? I did not need to do an NMU, I could have done a regular upload. The reason I did this as an NMU, and the reason I used the DELAYED queue, was just as a courtesy to you. A NMU is when a maintainer does not care about the package for a long time. And it is to fix something. I

Bug#885404: Acknowledgement (duc-nox: please provide bin/duc in duc-nox package)

2017-12-31 Thread Jonathan Dowland
Hi Herbert, On Fri, Dec 29, 2017 at 07:05:18PM -0200, Herbert Fortes wrote: But I do not understand. It seems to me that an alias solves the issue. And the user can set anything he wants. Each individual user could indeed add an alias themselves, but we could remove the need for them to do so.

Bug#885404: Acknowledgement (duc-nox: please provide bin/duc in duc-nox package)

2017-12-30 Thread Andrew Shadura
Hi, On 30 December 2017 at 11:53, Herbert Fortes wrote: > >>> >>> But I do not understand. It seems to me that an alias >>> solves the issue. And the user can set anything he >>> wants. Base on that, the use of 'Conflicts' seems too >>> much. It changes a lot of things. What am I not seem ? >>>

Bug#885404: Acknowledgement (duc-nox: please provide bin/duc in duc-nox package)

2017-12-30 Thread Herbert Fortes
>> >> But I do not understand. It seems to me that an alias >> solves the issue. And the user can set anything he >> wants. Base on that, the use of 'Conflicts' seems too >> much. It changes a lot of things. What am I not seem ? >> I learned that a NMU is when the package has a maintainer >>

Bug#885404: Acknowledgement (duc-nox: please provide bin/duc in duc-nox package)

2017-12-29 Thread Andrew Shadura
On 29/12/17 22:05, Herbert Fortes wrote: > Hi Andrew Shadura and Jonathan Dowland, > > > First, let's not make big noise about this. > > But I do not understand. It seems to me that an alias > solves the issue. And the user can set anything he > wants. Base on that, the use of 'Conflicts' seem

Bug#885404: Acknowledgement (duc-nox: please provide bin/duc in duc-nox package)

2017-12-29 Thread Herbert Fortes
Hi Andrew Shadura and Jonathan Dowland, First, let's not make big noise about this. But I do not understand. It seems to me that an alias solves the issue. And the user can set anything he wants. Base on that, the use of 'Conflicts' seems too much. It changes a lot of things. What am I not se

Bug#885404: Acknowledgement (duc-nox: please provide bin/duc in duc-nox package)

2017-12-29 Thread Andrew Shadura
Hi, On Fri, 29 Dec 2017 19:46:38 + Jonathan Dowland wrote: > On Thu, Dec 28, 2017 at 09:18:32PM -0200, Herbert Fortes wrote: > >Please, do not be so fast. > > That's why I uploaded to DELAYED-7 -- so it wasn't fast. > > >Does all that work really necessary ? There is no complain > >until th

Bug#885404: Acknowledgement (duc-nox: please provide bin/duc in duc-nox package)

2017-12-29 Thread Jonathan Dowland
On Thu, Dec 28, 2017 at 09:18:32PM -0200, Herbert Fortes wrote: Please, do not be so fast. That's why I uploaded to DELAYED-7 -- so it wasn't fast. Does all that work really necessary ? There is no complain until this week It's been bugging me for a while but I've only just had time to file

Bug#885404: Acknowledgement (duc-nox: please provide bin/duc in duc-nox package)

2017-12-29 Thread Herbert Fortes
tags 885404 = wontfix thanks I do not see enough reason to change the way the package is. It is not hard to tab-complete. The proposed solution was not Policy-preferred. And force a NMU is not polite. NMU is not the case.

Bug#885404: Acknowledgement (duc-nox: please provide bin/duc in duc-nox package)

2017-12-28 Thread Herbert Fortes
On 28/12/2017 20:38, Jonathan Dowland wrote: I've now implemented both and I'm leaning towards a simple Conflicts. The Conflicts version is branch jmtd/885404-proposed: 6 files changed, 15 insertions(+), 4 deletions(-) Lintian clean. The alternatives version is branch jmtd/885404-alt: 10 files

Bug#885404: Acknowledgement (duc-nox: please provide bin/duc in duc-nox package)

2017-12-28 Thread Herbert Fortes
On 28/12/2017 20:38, Jonathan Dowland wrote: I've now implemented both and I'm leaning towards a simple Conflicts. The Conflicts version is branch jmtd/885404-proposed: 6 files changed, 15 insertions(+), 4 deletions(-) Lintian clean. The alternatives version is branch jmtd/885404-alt: 10 files

Bug#885404: Acknowledgement (duc-nox: please provide bin/duc in duc-nox package)

2017-12-28 Thread Herbert Fortes
On 28/12/2017 20:38, Jonathan Dowland wrote: I've now implemented both and I'm leaning towards a simple Conflicts. The Conflicts version is branch jmtd/885404-proposed: 6 files changed, 15 insertions(+), 4 deletions(-) Lintian clean. The alternatives version is branch jmtd/885404-alt: 10 files

Bug#885404: Acknowledgement (duc-nox: please provide bin/duc in duc-nox package)

2017-12-28 Thread Jonathan Dowland
I've now implemented both and I'm leaning towards a simple Conflicts. The Conflicts version is branch jmtd/885404-proposed: 6 files changed, 15 insertions(+), 4 deletions(-) Lintian clean. The alternatives version is branch jmtd/885404-alt: 10 files changed, 67 insertions(+), 3 deletions(-) *Not

Bug#885404: Acknowledgement (duc-nox: please provide bin/duc in duc-nox package)

2017-12-27 Thread Jonathan Dowland
On a closer reading of Policy, using alternatives is preferred, even if a bit more complex. -- ⢀⣴⠾⠻⢶⣦⠀ ⣾⠁⢠⠒⠀⣿⡁ Jonathan Dowland ⢿⡄⠘⠷⠚⠋⠀ https://jmtd.net ⠈⠳⣄ Please do not CC me, I am subscribed to the list.