[eigen] Providing non-tag downloads over BitBucket |
[ Thread Index |
Date Index
| More lists.tuxfamily.org/eigen Archives
]
- To: eigen@xxxxxxxxxxxxxxxxxxx
- Subject: [eigen] Providing non-tag downloads over BitBucket
- From: Raphael Kubo da Costa <rakuco@xxxxxxxxxxx>
- Date: Sun, 01 Jan 2012 21:05:49 -0200
- Cancel-lock: sha1:G+eXd728svXHNa81Rjfg971EsKA=
Hi there,
I package eigen on FreeBSD, and it has been reported that the current
SHA256 sum of the 2.0.16 tarball provided by our port does not match the
one from the actual download from BitBucket. Since we check the
checksums before publishing an update, this means the tarball has
changed since it was first published.
Comparing FreeBSD's own copy of the 2.0.16 tarball [1] with the one
currently being provided by BitBucket [2], it looks like only the
tarball name (and the directory inside it) have changed from
eigen-eigen-2.0.16 to eigen-eigen-<hash of the commit which the tag
points to>. diff shows no difference in the actual contents.
As a packager, I would appreciate if Eigen started providing
"real" download tarballs in the Downloads section in BitBucket (like
other projects do) to prevent this kind of issue -- I guess tarballs
which are not created automatically do not risk being changed by
BitBucket.
[1]
ftp://ftp.freebsd.org/pub/FreeBSD/ports/distfiles/eigen/2.0.16.tar.bz2
and other mirrors
[2] https://bitbucket.org/eigen/eigen/get/2.0.16.tar.bz2