Closed Brli closed 3 months ago
Have you tried with makepkg -sr
as indicated in the BUILDING
file?
Have you tried with
makepkg -sr
as indicated in theBUILDING
file?
It's irrelevant anyway
If it's not clean build, the patch would failed even earlier
Patch things require no dependencies, it's just a base-devel package that do inline replacement to source code, aka. text file.
Can you give us the log of the build, at least with the output of MS_COMMIT
?
Here the log of the test build before the push to the AUR (https://github.com/VSCodium/vscodium/actions/runs/8207306570/job/22449034203#step:3:691)
okay, I see what's happening here:
check out the first few lines:
applying patch: ../patches/binary-name.patch
and check the failure lines:
applying patch: ../patches//binary-name.patch
error: patch failed: build/gulpfile.vscode.js:289
it just re-applying the patch again.
ok, so it seems to be that some capitalized environment variables are presumed to be exported by the docker mechanism?
where if not a docker, they don't exist?
I have to explicitly export OS_NAME and VSCODE_QUALITY at least for prepare_vscode.sh to work
Please post your full log.
Describe the bug During building for Linux x86_64, using aur/vscodium's recipe
Please confirm that this problem is VSCodium-specific
Please confirm that the issue/resolution isn't already documented
To Reproduce Steps to reproduce the behavior:
Expected behavior
Pass, and build continues.
Screenshots If applicable, add screenshots to help explain your problem.
Desktop (please complete the following information):
Additional context Add any other context about the problem here.