On May 26, 2009, at 23:12, Tim Teulings wrote: > Hello! > >> unfair to users if the version is not changed. So if I understand you >> correctly, you are saying a failure to build is not reason enough to >> change the version number, with which I agree. But if you change the > > Right. Fine :-) > >> code somehow, or change the packaging, so that it can build, then >> perhaps change the version number? > > For what purpose?
Because the _code_ has changed. > Nobody but me and the autobuilder might know what I > have changed (and somthing I must have changed else it would not pass > this time). Isn't that just versionities? No one wants a new version just for a new version's sake. > >>> Once package P version X has been successfully built then a >>> subsequent attempt >>> to upload package P version X should be rejected. >> >> Exactly - this is the current behavior. > > and coming back to the original question... If there is already > version > 1.0 in the repository I cannot upload version 0.9 either, because it > would build but nobody who see it by default (tools would always take > the highest version available). More of a statement than a question, but okay. The packaging policy is pretty clear about this; versioning follows the debian versioning policy so that the apt tool chain can work properly. So increment your version higher with each new version. It is up to you to decide if the changes you made warrant a new version or not. But if you change the code significantly, whether or not it is related to packaging, please consider a new version so that users know there are changes. Jeremiah _______________________________________________ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
