[Pkg-jed-commit] r683 - in jed-extra/trunk/debian: . examples patches

[Rafael Laboissiere]

* G. Milde <milde at users.sourceforge.net> [2007-05-15 15:39]:

> On 15.05.07, Rafael Laboissiere wrote:
> 
> > I added a line in debian/rules for outputing the md5sum of the upstream
> > tarball. Note that this is different from (and better than) the md5sum of
> > the output of "tar tfz".  It would be great if an md5sum file is added to
> > the download area at SF, such that an automatic check could be done.
> 
> It is now created by my "jedmodes-src-update-script" and stored at
> http://jedmodes.sourceforge.net/cvs/jedmodes-$(UPSTREAM_VERSION).md5sum

Thanks, I added the code for doing the md5sum check in debian/rules.

An unrelated issue: debian/changelog was committed with "jed-extra (2.3.2)"
and I did not notice that before uploading the new version.  The jed-extra
package is considered now to be "Debian native" and the
jed-extra_2.3.2.orig.tar.gz tarball contais all the Debian files.  There is
no way to repair this, unfortunately.  For instance, I cannot release
2.3.2-1 because the Debian installer will refuse a new upstream tarball with
identical name as the previous one.

This is a little bit annoying, because the next release needs a new upstream
version number in any case, even if it is built against 2.3.2.  I will call
if "2.3.2+fix", or something similar, such that it will not interfere with
future upstream version numbers [1].

[1] dpkg --compare-versions 2.3.2.0 gt 2.3.2+fix-1 && echo true || echo false

-- 
Rafael