Build date mismatch
Jon Abbott (1421) 2651 posts |
Is the date wrong on the build server? I’ve just spotted that the date of the “riscos” file in the Pi 17-09-14 build is 09-09-14. |
Jeffrey Lee (213) 6048 posts |
What date does *FX 0 show when the ROM is booted? It looks like the ROM has been built from the correct code (I can see the latest SoundDMA version in an OMAP4 ROM I just downloaded), so it’s either the date on the server which is wrong or the new version of ‘zip’ which was recently committed is dodgy. I have a feeling it’s actually zip which is the culprit; I’m fairly certain that one of the bugs that was fixed a long time ago either by myself or Joty was to do with zip/unzip getting the timestamps wrong (amongst many other issues). Although the patches were submitted to info-zip, I’m not sure if they actually made it into the official sources. |
Jon Abbott (1421) 2651 posts |
The build is okay, it’s just the timestamp on the file within the zip that’s wrong. I unzipped it on a PC if that makes any difference. It’s not really an issue, just an observation. |
Jeffrey Lee (213) 6048 posts |
Well, I’d class us using a broken version of zip as being an issue :) Either that or it is a previously-unseen bug in RPCEmu (since the build machine will be using hostfs for the builds) |
David Pitt (102) 743 posts |
The Pi 2014-19-17 ROM unzips with SparkFS on the Pi with the ‘riscos’ file as 06:01:15 17 Sep 2014, a most reasonable result. However unzip the same download on the Mac and the ‘riscos’ file is date stamped as 9 September 2014 13:25. |
Frank de Bruijn (160) 228 posts |
Same on Linux (2014-09-09 13:25:12). I’ve suspected RPCEmu’s hostfs does weird things with timestamps for a long time. It also changes the timestamp of an image file (SparkFS, StrongHelp) even if you only read from it. |