Fixing fatal issues is often a good start, assuming there is nothing more important to do, like trying out a new game etc.

> On 2023-01-09, at 8:41 AM, Taeumel, Marcel <Marcel.Taeumel at hpi.de> wrote:
> 
> Ha! It was exactly that:
> https://github.blog/2022-04-18-highlights-from-git-2-36/#stricter-repository-ownership-checks
> 
> I just had to add this to our linux-arm.yml:
>    git config --global --add safe.directory ${{ github.workspace }}
> 
> Took me about 3 hours to figure this out ... -.-"
> 
> Best,
> Marcel
> 
>> Am 09.01.2023 16:25:19 schrieb Marcel Taeumel <marcel.taeumel at hpi.de>:
>> 
>> 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-ownership-checks
>> 
>> Hmm...
>> 
>> Best,
>> Marcel
>> 
>>> Am 07.01.2023 01:17:34 schrieb tim Rowledge <tim at rowledge.org>:
>>> 
>>> The latest downloadable ARMv8 build - https://github.com/OpenSmalltalk/opensmalltalk-vm/releases/download/latest-build/squeak.cog.spur_linux64ARMv8.tar.gz - 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 at rowledge.org; http://www.rowledge.org/tim
>>> Long computations that yield zero are probably all for naught.
>>> 
>>> 
>>> 
> 


tim
--
tim Rowledge; tim at rowledge.org; http://www.rowledge.org/tim
A bad random number generator:  1, 1, 1, 1, 1, 4.33e+67, 1, 1, 1