Bugzilla – Bug 4962
Debian nightly build packages should use ~svn.NNNNN in version number
Last modified: 2008-12-15 13:07:54 UTC
The nightly builds of debian packages (currently 6.5.2 in "testing" and 7.0a in "unstable") should use "~svn.NNNNN" (where NNNNN is either the subversion revision number or an ISO datestamp) at the end of their version strings. That way each night's build is distinctly versioned, and will sort correctly vs the released version as well. Note: 7.0a should probably be 7.0~a, too, to ensure that it sorts before the released version 7.0.
Andy, I noticed Dean asking you a build question the other day, so I'm cc'ing you. :) What do you think of this suggestion?
I think this bug can be closed... the nightly Debian packages have all been competely overhauled at the request of the community, and almost everyone seems happy with the new naming convention.
No, it cannot be closed, sorting between testing and stable versions is still broken. The important detail is using the ~ as the separator for the pre-release build numbers; the current testing packages use a - separator, which results in broken sorting, but changing it to ~ will make things sort correctly. This was recently discussed in the mailing list, but Mike Valera deleted the forum messages because they were replies to a thread he had locked and stickied. Here are the partial archive I have: Mitch Harding wrote: > Hmmm. On my system it's not reporting there are any newer versions in > the stable tree. I've got the following line in my sources list: > deb http://debian.slimdevices.com stable main > > I currently have version 7.0-17737 from late last week. I thought > there had been some changes made since then. If the release versions are not going to use svn revision numbers, then the testing/pre-release builds must use ~ as a separator, not -. https://bugs-archive.lyrion.org/show_bug.cgi?id=4962 - Marc Ben Sandee wrote: > On Tue, Mar 4, 2008 at 12:14 PM, Mitch Harding <mitcharf@gmail.com> wrote: > >> I have voted for this bug. Seems it would solve the problem nicely. >> > > I don't think it will fix it retroactively, but certainly for future > releases. I voted for it as well. Yeah, the only way to fix it retroactively is to rebuild the release .deb with the released svn revision included with a hyphen. Hopefully they'll get this right using the ~ for pre-7.0.1 testing builds. - Marc
I'm changing the severity of this from enhancement to normal; it was an enhancement request when you weren't including svn numbers at all in the version, but now that you are, the incorrect separator which breaks sorting is a bug.
I've built a test package with this schema. I'll test it on my debian system, but this is what you're looking for right?: user@debian-build:~/build/trunk$ dpkg --info /tmp/build-trunk/squeezecenter_7.0.1~18219_all.deb new debian package, version 2.0. size 18928478 bytes: control archive= 62451 bytes. 178 bytes, 6 lines conffiles 587 bytes, 15 lines control 202224 bytes, 2212 lines md5sums 1944 bytes, 70 lines * postinst #!/bin/sh 453 bytes, 24 lines * postrm #!/bin/sh 287 bytes, 11 lines * prerm #!/bin/sh Package: squeezecenter Version: 7.0.1~18219 Section: sound Priority: optional Architecture: all Depends: perl (>= 5.8.1), mysql-server-4.1 | mysql-server-5.0, libmysqlclient14-dev | libmysqlclient15-dev, mysql-client-4.1 | mysql-client-5.0, flac, sox, adduser Conflicts: slimp3, slimserver Replaces: slimp3, slimserver Installed-Size: 47872 Maintainer: Logitech/Slim Devices <debian@slimdevices.com> Description: Streaming Audio Server SlimServer is a cross-platform streaming server that supports a wide range of formats, including AAC, AIFF, FLAC, Ogg Vorbis, MP3, WAV, and WMA. .
Yes, that's correct. Thanks. msherman@pyloric:~$ dpkg --compare-versions 7.0.1-18219 gt 7.0.1 && echo broken || echo fixed broken msherman@pyloric:~$ dpkg --compare-versions 7.0.1~18219 gt 7.0.1 && echo broken || echo fixed fixed
buildme.pl script updated in revision #18234 to fix this problem. Packages now named with a ~ instead of a - for Debian releases.
This bug appears to have been fixed in the latest release! If you are still experiencing this problem, feel free to reopen the bug with your new comments and we'll have another look. Make sure to include the version number of the software you are seeing the error with.