Bas Wijnen <[EMAIL PROTECTED]> writes: > You can base security uploads on NMUs, so I think you could get > +s1+nmu1+s1+nmu1, etc. Or should it go from +s1 to +s1+nmu1 to +s2 to > +s2+nmu1?
I was assuming the latter. > I prefer the longer versions in this case. When a package gets too many > security and other non-maintainer uploads, it should probably be > orphaned or co-maintianed anyway (since there's appearantly a lot to do, > and the maintainer isn't doing it). We have other ways of tracking that information than the version, though. > Hmm, the second dot probably has the same meaning then. This only matters when appended to a Debian revision; for native packages, it doesn't matter. So ignore me unless we're talking about using the same convention for both native and non-native packages. (Having three periods in the Debian revision is the old marker of a binNMU and various things may still trigger off that.) > So we should go for +deb31[+]_1 or something? To make it clear again: > > +deb is a fixed part which means this is a security upload Or any other stable upload, yes? We're not currently distinguishing between security uploads and maintainer uploads for the etch/sarge/etc. versions. > 31 is the current (at time of upload) stable release > + means this is an upload to testing, skipping it means to stable You wouldn't need the presence/absence thing of the + if you used a higher version number for the testing security update. I'd be inclined to say that we just always add 1 to the minor version of the last stable version when making a testing security upload until the actual version number for the next release has been picked. So in other words, use +deb40 for etch and +deb41 for lenny until a version number has been picked, under the assumption that the choices are 4.1 or 5.0 and either way 41 has the right version ordering properties. (Now, of course, people could start using +deb50 if they wanted to.) -- Russ Allbery ([EMAIL PROTECTED]) <http://www.eyrie.org/~eagle/> -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
