Re: NMU versioning

2008-05-04 Thread Lucas Nussbaum
On 29/04/08 at 11:54 +0200, Mike Hommey wrote: FWIW, I think NMUing a package shouldn't end up with a sourceful upload but should instead have a .diff.gz, whether it's a native package or not. When NMUing a native package, which problem would it add to upload a source package with a single

Re: NMU versioning (was: DEP1: Clarifying policies and workflows for Non Maintainer Uploads)

2008-04-30 Thread Stefano Zacchiroli
On Tue, Apr 29, 2008 at 10:17:12PM +0200, Raphael Hertzog wrote: I'd be very unhappy about that. For one, I think using such suffix in a field that forms part of users' everyday's life is, uhm, inappropriate or disruptive. What do they care if the version is a NMU or not? Hu? And +dfsg is

Re: NMU versioning

2008-04-29 Thread Kartik Mistry
On Tuesday 29 Apr 2008 3:02:34 pm Amaya wrote: The version must be the version of the last upload, plus +nmuX, where X is a counter starting at 1. I have found that NMUing native source packages is a bit tricky, as in, what is the consensuous regarding this increment? Where to increment?

Re: NMU versioning

2008-04-29 Thread Amaya
James Vega wrote: The version must be the version of the last upload, plus +nmuX, where X is a counter starting at 1. I have found that NMUing native source packages is a bit tricky, as in, what is the consensuous regarding this increment? Where to increment? I hope I made myself understood,

Re: NMU versioning

2008-04-29 Thread Adeodato Simó
* Mike Hommey [Tue, 29 Apr 2008 11:54:59 +0200]: FWIW, I think NMUing a package shouldn't end up with a sourceful upload but should instead have a .diff.gz, whether it's a native package or not. 100% agreed. (Assuming you mean a NMU should never, ever, create a new tarball, particularly

Re: NMU versioning

2008-04-29 Thread Kumar Appaiah
On Tue, Apr 29, 2008 at 12:16:28PM +0200, Adeodato Simó wrote: FWIW, I think NMUing a package shouldn't end up with a sourceful upload but should instead have a .diff.gz, whether it's a native package or not. 100% agreed. (Assuming you mean a NMU should never, ever, create a new tarball,

Re: NMU versioning

2008-04-29 Thread Bastian Blank
On Tue, Apr 29, 2008 at 12:16:28PM +0200, Adeodato Simó wrote: * Mike Hommey [Tue, 29 Apr 2008 11:54:59 +0200]: FWIW, I think NMUing a package shouldn't end up with a sourceful upload but should instead have a .diff.gz, whether it's a native package or not. 100% agreed. (Assuming you mean a

Re: NMU versioning

2008-04-29 Thread Amaya
Kartik Mistry wrote: someversion+nmu1, someversion+nmu2 for example see, bzflag package. It is at 2.0.10.20071115+nmu1 right now. Thanks, that answers my question. -- ·''`. Come, let me sing into your ear, those dancing days are gone : :' : I carry the sun in a golden cup, the moon

Re: NMU versioning

2008-04-29 Thread Adeodato Simó
* Bastian Blank [Tue, 29 Apr 2008 12:55:23 +0200]: On Tue, Apr 29, 2008 at 12:16:28PM +0200, Adeodato Simó wrote: * Mike Hommey [Tue, 29 Apr 2008 11:54:59 +0200]: FWIW, I think NMUing a package shouldn't end up with a sourceful upload but should instead have a .diff.gz, whether it's a

Re: NMU versioning

2008-04-29 Thread Mike Hommey
On Tue, Apr 29, 2008 at 01:01:53PM +0200, Adeodato Simó [EMAIL PROTECTED] wrote: * Bastian Blank [Tue, 29 Apr 2008 12:55:23 +0200]: On Tue, Apr 29, 2008 at 12:16:28PM +0200, Adeodato Simó wrote: * Mike Hommey [Tue, 29 Apr 2008 11:54:59 +0200]: FWIW, I think NMUing a package shouldn't

Re: NMU versioning (was: DEP1: Clarifying policies and workflows for Non Maintainer Uploads)

2008-04-29 Thread Raphael Hertzog
On Tue, 29 Apr 2008, Adeodato Simó wrote: I want a consistent versioning scheme, thus +nmuX for both native and non-natives packages. I'd be very unhappy about that. For one, I think using such suffix in a field that forms part of users' everyday's life is, uhm, inappropriate or

NMU versioning (was: DEP1: Clarifying policies and workflows for Non Maintainer Uploads)

2008-04-25 Thread James Vega
On Thu, Apr 24, 2008 at 09:42:59PM +0200, Bas Wijnen wrote: This DEP is available on the Debian Wiki[1]. The version must be the version of the last upload, plus +nmuX, where X is a counter starting at 1. The above was added to the DEP to match dch but dch only uses that format for native NMUs

Re: NMU versioning (was: DEP1: Clarifying policies and workflows for Non Maintainer Uploads)

2008-04-25 Thread Raphael Hertzog
(reply-to set to debian-devel only) On Fri, 25 Apr 2008, James Vega wrote: On Thu, Apr 24, 2008 at 09:42:59PM +0200, Bas Wijnen wrote: This DEP is available on the Debian Wiki[1]. The version must be the version of the last upload, plus +nmuX, where X is a counter starting at 1. The

Re: NMU versioning (was: DEP1: Clarifying policies and workflowsfor Non Maintainer Uploads)

2008-04-25 Thread Adam D. Barratt
Raphael Hertzog wrote, Friday, April 25, 2008 3:16 PM On Fri, 25 Apr 2008, James Vega wrote: On Thu, Apr 24, 2008 at 09:42:59PM +0200, Bas Wijnen wrote: This DEP is available on the Debian Wiki[1]. The version must be the version of the last upload, plus +nmuX, where X is a counter starting

Re: NMU versioning

2008-04-25 Thread Russ Allbery
Raphael Hertzog [EMAIL PROTECTED] writes: I want a consistent versioning scheme, thus +nmuX for both native and non-natives packages. Consider this a wishlist bug against devscripts. :-) And the Developer's Reference. I do recommend actually filing said wishlist bugs, of course. :) --