Open MateuszKlatecki opened 4 years ago
Hi @MateuszKlatecki,
thanks for reporting back. This is an issue caused by moving away from Git-LFS. Can you please try to disable Git-LFS smudge filter?
You can achieve that by setting GIT_LFS_SKIP_SMUDGE=1
in your environment. All binary files are unavailable in this case, like PackChk and SVDConv. If you need these files please refer to a official release package instead.
Cheers, Jonatan
@JonatanAntoni thank you for your help, Solution you provided helped me
Sorry for any inconvenience resulting from this fundamental change. Please leave this issue open until we finally solved it. I am still looking for a solid solution. The current situation might affect all users referring to this repository.
I am happy for any idea how we could distribute binary utilities (such as PackChk and SVDConv) in the future.
Are we not expected to run the git lfs commands any more after cloning the CMSIS_5 git repository? 'git lfs install --local && git lfs pull'
We removed all files formerly stored in Git-LFS due to bandwidth quota issues. So no need to run lfs commands any more.
Is there any other way to get the binaries of previous releases? The release tarballs does not contain the binaries.
Yes, all binaries are in the released pack, see https://github.com/ARM-software/CMSIS_5/releases/download/5.7.0/ARM.CMSIS.5.7.0.pack.
Unfortunately you are right, the source tarball only contains the pointer-files. Too bad.
Thanks! I only checked the tar.gz and zip files before, but the pack archive seems to contain all the necessary binaries.
Is this applicable to all branches/tags? We have been using the 5.5.0 tag for trusted-firmware builds.
Previously used commands: git clone https://github.com/ARM-software/CMSIS_5.git -b 5.5.0 && cd CMSIS_5 && git lfs install --local && git lfs pull && cd -
What commands should we use now?
This is the error I get now:
You are in 'detached HEAD' state. You can look around, make experimental changes and commit them, and you can discard any commits you make in this state without impacting any branches by performing another checkout.
If you want to create a new branch to retain commits you create, you may do so (now or later) by using -b with the checkout command again. Example:
git checkout -b
Downloading CMSIS/DSP/Lib/ARM/arm_ARMv8MBLl_math.lib (2.4 MB) Error downloading object: CMSIS/DSP/Lib/ARM/arm_ARMv8MBLl_math.lib (afa93f0): Smudge error: Error downloading CMSIS/DSP/Lib/ARM/arm_ARMv8MBLl_math.lib (afa93f014c4252cf0c530b223264c5d0b9b5d06b1fd02cce0e68976ed2877b5e): [afa93f014c4252cf0c530b223264c5d0b9b5d06b1fd02cce0e68976ed2877b5e] Object does not exist on the server: [410] Object does not exist on the server
Errors logged to /var/tmp/gitlab-runner1/builds/7e5c9300/1/repo/tfm/trusted-firmware-m/CMSIS_5/.git/lfs/objects/logs/20200424T204818.428715277.log
Use git lfs logs last
to view the log.
error: external filter 'git-lfs filter-process' failed
fatal: CMSIS/DSP/Lib/ARM/arm_ARMv8MBLl_math.lib: smudge filter lfs failed
warning: Clone succeeded, but checkout failed.
Hi @malferns,
yes, all branches/tags are affected, currently. I am going to fix this, today.
Sorry for any inconvenience, Jonatan
Hi all,
we have decided to bring back all files to LFS storage to assure backward compatibility for the time being. Checking out older branches/tags should be possible, again.
In order to reduce bandwidth consumption I want to ask you to reduce cloning from GitHub to a bare minimum. Please consider adding caches to your CI systems for instance, i.e. keep a bare clone somewhere local.
Cheers, Jonatan
I've verified that my previous commands work once again with the upstream GitHub repo.
We do maintain a bare mirrored repo which is used for our CI builds, but I had temporarily switched to the upstream repo as our mirror was broken because of these changes.
The mirror has been fixed now and we are back to using the mirror for our CI builds.
Thanks for reverting the changes.
Hi @malferns,
thank you for your confirmation.
Cheers, Jonatan
Hi,
Since yesterday I cannot clone this repository. Neither develop branch nor tags. It looks like a problem with git-lfs.
Here are the logs: