On Sun, 04 Feb 2001, Siggi Langauf wrote: > On Sun, 4 Feb 2001, Adrian Bunk wrote: > > consider the situation when an older version of your package is in frozen > > and you must fix a RC bug but the release manager won't allow you to > > In that case, I'd have to make a second branch, anyway. > The only difference is that it's not uploaded as a whole, but only as a > modified .diff.gz for non-native packages... > > But you're right. In that case a .diff.gz could come handy. Is there any > problem switching to non-native format when that happens? Well, no, there is not; it will work and nothing will complain, AFAIK. I'd not advise you to change from non-native to native, however (because we have so many broken uploads of non-native as native that someone will end up writing a script that flags non-native->native as suspicious ;-) ). Anyway, when you change from native to non-native, the first non-native upload takes as many resources as a native upload would (because there wasn't a .orig.tar.gz in there yet), so you'll only have resource gains in a second non-native upload (of the same upstream branch --> same .orig.tar.gz). -- "One disk to rule them all, One disk to find them. One disk to bring them all and in the darkness grind them. In the Land of Redmond where the shadows lie." -- The Silicon Valley Tarot Henrique Holschuh
Attachment:
pgpr7MeqjhZ54.pgp
Description: PGP signature