On May 26, 2009, at 13:29, Niels Breet wrote: >> This morning I got an email, it says >> that the packages have been rejected and they won't be moved in the >> repository because the version (5.0_5.0.32-7etch6maemo3) is minor >> of the >> current [3] version available in the repository >> ( 5.0.32-7etch6maemo2 ). >> Then that's very strange.. what packages have compared the script >> running >> on the autobuilder?
The Packaging Policy document says you can test your version number with dpkg --compare-versions. I assume that is what is being used behind the scenes but there is not much documentation surrounding the autobuild process so I cannot confirm this. You may want to ask Ed Bartosh. I'll read some of the BuildMe source code and see if I can determine what is going on. > It seems that the version comparison used by BuildMe doesn't > understand > the long version number. (7etch6maemo3) I'd need to find out if such > numbers are intended to be supported or that they are illegal. If they are "illegal" this needs to be clearly communicated in the Packaging Policy document so that packagers know what to name their packages. Currently the version naming is rather unclear and version strings like the one mentioned above is confusing at best. Can we encourage Nokia to work with Maemo to clarify and complete the Maemo Packaging Policy. From the packaging document I'd say that the package should be called mysql-dfsg-5.0_5.0.32-0maemo3. This way one would remove the etch specific version. I am not quite sure why an etch specific version is being used. Jeremiah _______________________________________________ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
