[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: preventing update of a custom package

On Mon, Apr 01, 2002 at 11:51:44AM -0500, Matt Zimmerman wrote:
> On Fri, Mar 29, 2002 at 01:37:44PM +0000, Sean Neakums wrote:
> > What I've been doing is giving my hacked versions of Debian packages
> > revisions of -x.0.y, where x is the original package's revision and y
> > is my local revision.  I use the 0 in between to avoid clashing with
> > possible NMUs.
> If I'm not mistaken, that scheme is reserved for use by binary-only NMUs
> (simple recompiles) for porting efforts.  So while it is unlikely to clash,
> it is not by any means guaranteed.

*scratches head*

Am I mistaken, then, in my reading of policy and the developer's reference
that indicate one *should not* change the version, changelog, or anything
else when doing a binary-only porting NMU?

The use of fractional Debian revisions is clearly in the domain of NMUs
and suchlike, but the only special case for "0" that I see listed is the
use of -0.x when NMUing a new upstream version (IE, 1.3.4-3 -> 1.3.5-0.1
if you source NMU the 1.3.5 sources, which both keeps the fractional NMU
component, and leaves -1 and higher available for maintainer use).
Joel Baker                           System Administrator - lightbearer.com
lucifer@lightbearer.com              http://users.lightbearer.com/lucifer/

To UNSUBSCRIBE, email to debian-devel-request@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org

Reply to: