|Anonymous | Login | Signup for a new account||2017-08-23 15:51 EDT|
|My View | View Issues | Change Log | Roadmap|
|View Issue Details|
|ID||Project||Category||View Status||Date Submitted||Last Update|
|0001111||LuxRender||Documentation||public||2011-06-30 05:42||2012-09-11 09:10|
|Status||closed||Resolution||unable to reproduce|
|Target Version||1.0||Fixed in Version||1.0RC4|
|Summary||0001111: Provide source tarballs for stable releases|
|Description||Currently the only way to obtain sources of LuxRender (and all its subprojects) is to either clone the mercurial repository or to download archive generated by mercurial, such as http://src.luxrender.net/lux/archive/45d3e13eb94c.tar.bz2 [^] for LuxRender 0.8.|
However the md5sum of the generated archive change from time to time. This makes packaging more difficult. Especially on Archlinux, because it breaks ABS builds (which is system similar to ports used to build packages from source).
It would be nice if there were some official source archives available.
|Tags||No tags attached.|
|Mercurial Changeset #|
|Requires Documentation Update||No|
|Requires Exporter Update|
|The MD5 sum of the generated tarball shouldn't change at all, the content being the same. Would you have the ability to make a diff of the download in case the MD5 sum changes? I can only see it changing because of serveur option modifications regarding compression, but that is pretty unusual.|
|jeanphi: I'll do that. It will probably take some time, because it usually took a few days for the check sum to change.|
|Thanks a lot, I'm waiting for some more news from you.|
I just don't get it. According to the logs we had to rebuild luxrender package for archlinux three times in about two weeks because md5sum of the source tarball changed. But now there is no change for nine days.
First we downloaded sources from bitbucket, but the md5sum changed, so we started to use luxrender.net mirror with hope that the md5sum won't change. But it changed twice after that. From bugzilla and IRC log the md5sum changed approximately 25th June and 30th June.
J the Ninja (developer)
|While the v08 tag didn't change in that time, the repo as a whole did (new commits to the trunk). Could Mercurial be changing something in the contents of the tagged tarball because of a new commit? Thus making the md5sum change?|
|I don't think so, and there have been lots of changes since without the MD5 changing.|
Is it possible that the server was updated at that time?
But then it would be strange coincidence that md5sums of tarball from bitbucket changed at least once too at that time…
Maybe this issue should be closed so it doesn't haunt the bugzilla. I can reopen it (or open another one if reopening is not possible in mantis) if I find more information about this issue if it ever happens again.
|2011-06-30 05:42||stativ||New Issue|
|2011-07-01 11:31||jeanphi||Note Added: 0003086|
|2011-07-01 11:31||jeanphi||Assigned To||=> jeanphi|
|2011-07-01 11:31||jeanphi||Status||new => feedback|
|2011-07-01 14:00||stativ||Note Added: 0003088|
|2011-07-01 14:00||stativ||Status||feedback => assigned|
|2011-07-04 08:32||jeanphi||Note Added: 0003090|
|2011-07-09 16:09||stativ||Note Added: 0003094|
|2011-07-09 17:13||J the Ninja||Note Added: 0003095|
|2011-07-15 05:32||jeanphi||Note Added: 0003098|
|2011-07-15 13:04||stativ||Note Added: 0003100|
|2011-07-19 12:37||jeanphi||Status||assigned => resolved|
|2011-07-19 12:37||jeanphi||Fixed in Version||=> 1.0|
|2011-07-19 12:37||jeanphi||Resolution||open => unable to reproduce|
|2011-08-31 08:17||jeanphi||Target Version||=> 1.0|
|2012-08-21 09:54||jeanphi||Fixed in Version||1.0 => 1.0RC4|
|2012-09-11 09:10||jeanphi||Status||resolved => closed|
|Copyright © 2000 - 2017 MantisBT Team|