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

Re: What warrants a non-maintainer release number?



> > Why do you think we are still discussing "non-maintainer" uploads?
>
> I don't know ;-) that's why I got into the discussion.

The discussion started when someone (I forgot who :) did a non-maintainer
upload for another architecture _twice_, the second time with different
depedencies (resulted from simply recompiling) but with the same version
number.

However, the `non-maintainer' part of this discussion is totally
unimportant. What matters is the question `in which cases has the version
number to be incremented and in which cases can it be left'?

I think we all agree now that the version number has to be incremented
whenever the binary package is changed on master (even in Incoming/).

(The only situation where one can upload a binary package twice without
changing the version number would be when the first upload wasn't
successful--i.e., the fules got truncated.)


Thanks,

Chris

--                  Christian Schwarz
                   schwarz@monet.m.isar.de, schwarz@schwarz-online.com
                  schwarz@debian.org, schwarz@mathematik.tu-muenchen.de
                       
                PGP-fp: 8F 61 EB 6D CF 23 CA D7  34 05 14 5C C8 DC 22 BA
              
 CS Software goes online! Visit our new home page at
 	                                     http://www.schwarz-online.com


--
TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to
debian-devel-request@lists.debian.org . 
Trouble?  e-mail to templin@bucknell.edu .


Reply to: