View Issue Details
|ID||Project||Category||View Status||Date Submitted||Last Update|
|0000742||LDMud 3.5||Other||public||2010-03-30 13:44||2010-04-23 18:30|
|Target Version||3.5.0||Fixed in Version||3.5.0|
|Summary||0000742: incorrect build no in debug-log (3.5)|
|Description||all my debug logs show in the first line:|
2010.03.22 11:37:26 LDMud 3.5.0 (Build 2656) (development)
this can't be the correct build no / revision. it is the same on all my machines.
can anyone else reproduce or invalidate this?
|Tags||No tags attached.|
No, its true. As far I as can see that info comes from version.sh which is generated by the release scripts and release time. Unfortunately, the script which is supposed to modify version.sh is not in the svn repo, right now I can't even look what is it should do.
Ok, as I can't properly update version.sh right now, because I don't now, which script should do that, I changed now mk-patchlevel to extract the revision from SVN or git (depending on availability) first and fall back to the data from version.sh if no SCM data is available.
I hope, the shell logic is portable enough. ;-) If you like, please test r2900.
||works on debian|
||Then I assume this to be resolved for now.|
|2010-03-30 13:44||_xtian_||New Issue|
|2010-04-08 14:18||zesstra||Note Added: 0001818|
|2010-04-08 14:18||zesstra||Status||new => confirmed|
|2010-04-21 17:22||zesstra||Note Added: 0001819|
|2010-04-21 18:28||_xtian_||Note Added: 0001824|
|2010-04-23 18:29||zesstra||Project||LDMud => LDMud 3.5|
|2010-04-23 18:30||zesstra||Note Added: 0001827|
|2010-04-23 18:30||zesstra||Assigned To||=> zesstra|
|2010-04-23 18:30||zesstra||Status||confirmed => resolved|
|2010-04-23 18:30||zesstra||Resolution||open => fixed|
|2010-04-23 18:30||zesstra||Fixed in Version||=> 3.5.0|
|2010-04-23 18:30||zesstra||Target Version||=> 3.5.0|