Fix afws client certs #21
Loading…
Reference in New Issue
No description provided.
Delete Branch "esavkin/artiq-extrapkg:fix-cacerts-and-package"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
reinstalls cacerts after msys2 is installed (works offline too) - better be backported to release-8fixes wrong prefix in package which made it appear in- #22C:\msys64\nix\store....
instead of normal installationCopies already extracted certs from base image into clang64 subenvironment.
Tested by installing and calling afws_client and checking that it successfully connects (and returns login failed in my case).
@ -16,3 +16,3 @@
package() {
cd source
wine-msys2-build python -m installer --destdir="${pkgdir}" dist/*.whl
wine-msys2-build python -m installer --destdir="${pkgdir}" --prefix="clang64/" dist/*.whl
Shouldn't it be
c:\clang64
or similar?Again, please split PRs.
No,
[archive]/clang64
in the package is translated into/clang64
by pacman and it is translated tofull\path\to\msys2\root\clang64
automatically in msys2 environment.Overall seems like we could have packaged ARTIQ for the Arch same way, except dependencies names.
d26ba7bbce
toa73be047fe
Fix afws clientto Fix afws client certsWhy is this not an issue when msys2 is installed normally (i.e. without the ARTIQ installer)?
Because there are post-install hooks in cacert package, that are quite troublesome to make it working outside of windows environment.
There are lots of things you think are troublesome when they aren't really. What are the exact issues?
a73be047fe
tof61fb65c84
f61fb65c84
tod244efc689
p11-kit extract doesn't work as intended in isolated environment, and I couldn't make it work.
For now I made the builder copy certificates from base image into clang64.