Hi Tim --
I think that "strftime" and/or "gmtime" are not working anymore correctly in our QEMU environment, that we set up on GitHub Actions in a Debian "Buster" container.
See this extract from ".git_filters/RevDateURL.smudge":
#!/usr/bin/env perl use POSIX qw(strftime);
$myrev = `git log -n1 --format="%at"`; $myrev =~ s/\s+$//m; $ENV{'TZ'} = 'UTC'; $myrev = strftime "%Y%m%d%H%M", gmtime($myrev); $myrev =~ s/\s+$//m;
"..."
Not sure how to debug this locally. All assets have the wrong revision: https://github.com/OpenSmalltalk/opensmalltalk-vm/actions/runs/3834141967 Only a few of them were wrong a month ago: https://github.com/OpenSmalltalk/opensmalltalk-vm/actions/runs/3691011134
Hmm... anyway, the revision gets extracted via "scripts/ci/actions_build.sh":
"..." echo "$(cat platforms/Cross/vm/sqSCCSVersion.h | .git_filters/RevDateURL.smudge)" > platforms/Cross/vm/sqSCCSVersion.h echo "$(cat platforms/Cross/plugins/sqPluginsSCCSVersion.h | .git_filters/RevDateURL.smudge)" > platforms/Cross/plugins/sqPluginsSCCSVersion.h "..." readonly ASSET_REVISION=$(grep -m1 "SvnRawRevisionString" "platforms/Cross/vm/sqSCCSVersion.h" | sed 's/[^0-9.]*([0-9.]*).*/\1/') "..."
Which means that if our .smudge script does not work, the revision data cannot be extracted from sqSCCSVersion.h. Hmm... any perl-related year-2023-bug out there? :-D
No clue. We could try:
A) Bumping "Buster" to "Bullseye". Yet, "Buster" is not that old. 2021. B) Fix those "fatal warnings": fatal: detected dubious ownership in repository at '/home/runner/work/opensmalltalk-vm/opensmalltalk-vm'
Maybe, "git log" is actually not working here... But those warnings have been around since we migrated to GHA in 2021. So...
Maybe this is something that changed April 2022? https://github.blog/2022-04-18-highlights-from-git-2-36/#stricter-repository...
Hmm...
Best, Marcel
Am 07.01.2023 01:17:34 schrieb tim Rowledge tim@rowledge.org:
The latest downloadable ARMv8 build - https://github.com/OpenSmalltalk/opensmalltalk-vm/releases/download/latest-b... - has a weird looking directory structure.
Normally I'd expect an sqcogspur64ARMv8linuxht directory I can drag out of the archive app and into my main Squeak directory, whereupon the contents get overlaid onto what was already there. Amongst other things I'd expect to find a new lib/squeak/5.0-20230103xxxxxxxx-64bit directory or similar. Instead it has lib/squeak/5.0-197001010000-64bit and I'm fairly sure we didn't have spur & cog in 1970. Who done broke the clock?
tim -- tim Rowledge; tim@rowledge.org; http://www.rowledge.org/tim Long computations that yield zero are probably all for naught.