-
Notifications
You must be signed in to change notification settings - Fork 482
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[pacman] Standalone pacman.exe usage against different root: "failed to execute correctly" during post_* scripts #2784
Comments
I've had similar issues before, and it was resolved by adding |
Use a new login shell with the right environment. This means we can depend on the default PATH in the hook code. See msys2#2784
the hooks are handled in #2787 |
Oh, my bad, I dug around #1998 but hadn't gotten down to this comment.
My mistake, thanks! |
Describe the issue
I'm bootstrapping a little MSYS2-lite for a Windows Firefox developer environment.
As part of this, I'm essentially running
<msys2>/usr/bin/pacman.exe -Sy --root <target> <list-of-packages ...>
However, I'm seeing errors when I do this:
Note that this only happens when running
pacman.exe
directly from the Command Prompt, and not when running it from an MSYS2 context.Steps to Reproduce the Problem
Do the following from the Command Prompt.
Note that this assumes that MSYS2 is installed to
C:\msys64
mkdir msys2-test\var\lib\pacman msys2-test\var\log msys2-test\tmp
cd msys2-test
C:\msys64\usr\bin\pacman.exe -Sy --root . msys2-runtime bash
C:\msys64\usr\bin\pacman.exe -Sy --root . libtasn1
Log (non-debug)
Debug log when installing just libtasn1
Additional Context: Operating System, Screenshots
If applicable, add screenshots to help explain your problem.
Notes
mirror.msys2.org
. I'm guessing that it's either because it just went down, or I'm being rate-limited. Since the packages were already cached, it doesn't appear to be affecting the bug in questionpacman
, because/tmp/alpm_<random>/
was removed before I could copy it. If you have tips for digging in further, I'd appreciate it :)The text was updated successfully, but these errors were encountered: