Previously the -rc in our rc tags got dropped, meaning that those
packages looked newer to the packaging system than the later release
build. This rectifies the issue, though some damage may already have
been done on 3.6-rc builds.
I'm mostly cargo-culting the RPM version format - there don't appear
to be rules for RPM about how to handle this. Hopefully an RPM
enthusiast can fix up what I've done as a followup.
Now the changelog is different depending if the parent is tagged:
- for tags, keep the previous content, i.e. changelog of the tags.
- for nightly build, changelog of the changesets since the latest tag
As RPM is expecting strictly descending dates, I have used a python
script to reorder the mercurial changelog.
Previous, RPMs was always built from tip, and the release number did not match
the 'hg version' put in place for 1.4.
This will enable also to this script to be able to build official tag and not
only nightly build.
Running this script using a different locale (i.e., Italian) returns
an error:
$ ./contrib/buildrpm
sto aggiornando la directory di lavoro
1060 file aggiornati, 0 file merge, 0 file rimossi, 0 file non risolti
errore: data errata in %changelog: mar giu 23 2009 Stefano Tortarolo <stefano.tortarolo@gmail.com> 1.2.1-1034
mercurial.spec had bitrotted. These changes makes it possible to build an rpm that is usable.
Only minimal changes has been made, and there is plenty of room for improvement.
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
[PATCH] Add contrib/buildrpm script
From: Bryan O'Sullivan <bos@serpentine.com>
Just run "buildrpm", and it builds an RPM for you. No funky monkey
business required.
manifest hash: b8fde5108b5cc8f49ce248d14ac2ee7ad004c91c
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.0 (GNU/Linux)
iD8DBQFCxb6sywK+sNU5EO8RApQZAJ94VD6NQr9l4Xx6w3S8EdpCIUuiIACfdoHA
qnQWtMM+kqAzi3LnO92UYWE=
=SWIO
-----END PGP SIGNATURE-----
