Hi, Am Montag, den 21.02.2011, 15:31 +0100 schrieb Mathieu Malaterre: > > thanks for the patch, and for testing the new version. > > > > I’m not sure if using an untagged branch as the source is useful – did > > they not release a tarball for that version? And if not, how about > > hard-coding the revision in the script? Or just not use such a script at > > all, and manually build the tarball – that’s how I did it with the SVN > > snapshots so far. > > I could not find any tarball. There is no tag AFAIK. > I simply assumed that there is no activity in the 4.3 branch to call it 4.3.0; > > the version is hardcoded in my get-orig-source.sh script. I added the > get-orig-source target as par recommendation for a debian package. > > This make it simplier for other people to download serna.
After the initial upload of 4.3 to Debian, people can just use the .orig.tar.gz. This is especially recommended with more than one maintainer, as the other maintainers need to work with a bit-identical .orig.tar.gz, or the upload will fail. Anyways, it seems that mercurial and the proxy here don’t like each other. Can you upload your .orig.tar.gz somewhere, e.g. on your alioth space? > BTW I could not find a README.source file explaining the reason for > antlr (I had to read the ITP bug for serna...) You mean the reason for antlr being bundled? Greetings, Joachim -- Joachim "nomeata" Breitner Debian Developer nome...@debian.org | ICQ# 74513189 | GPG-Keyid: 4743206C JID: nome...@joachim-breitner.de | http://people.debian.org/~nomeata
signature.asc
Description: This is a digitally signed message part
