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鈥檒l occasionally send you account related emails.
Already on GitHub? Sign in to your account
Does not handle multile architectures in pacman.conf #185
Comments
Ooh never knew that it was possible to specify two architectures. I agree that default behaviour should select the first of the architectures outputted by But another edge case: what if the user wants to explicitly specify the non-initial architecture outputted by |
I personally don't mind a mix of env and CLI configuration. And so something like this, that is rarely in need of setting, could be an env-only situation. But I think you prefer the consistency of all-and-only CLI options for changing behavior. I'm happy to support you in that, in which case, yes |
馃悰 Bug Report
Checklist
downgrade
release from the AUR?Environment
Omitted.
Description
See AUR comment.
Steps to reproduce
Have multiple repositories of different architectures (one use-case is optimized architectures).
Observe the following:
Attempt to
downgrade
something.Expected behavior
We can assume:
Therefore, the first item of the list should become the
DOWNGRADE_ARCH
default.Actual behavior
The multi-line string becomes
DOWNGRADE_ARCH
and we break with ased
error.Known workarounds
^ I suggest we add this to the template.
Users can manually specify the correct
DOWNGRADE_ARCH
.Command trace
Trace
The text was updated successfully, but these errors were encountered: