-
-
Notifications
You must be signed in to change notification settings - Fork 361
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
Number menu mixes up packages #812
Comments
Also the reason I didn't just make a PR is because this did actually start out as a bug report. I wrote up the issue then started figuring the rest out and adding the "#812" bits. Didn't want to waste what I'd already written up. |
I have also noticed that and it is specially prevalent on stable to git upgrades |
Feel free to make a new release, it's been a long while since the last one. There's not too many commits but taking a look I just realised the depsolver merge is still not in stable. I think it's been in git long enough. |
I'm sorry 😅, just thought it was such a transient bug it would get fixed by the config system soon enough. I'll make a new release today |
Affected Version
yay v8.1173.0.r21.ge18c236 - libalpm v11.0.1
Issue
Weirdly, when trying to install javafx the number menu gets a little confused.
hitting 1 tries to install the entry labelled as 3 and vice versa. Entry 2 is correct.
Looking into it more it seems like a topdown/bottomup issue. The lists are actually reversed,
entering 1 tries to get the last package, 2 the last but one and so on.
This is not present on stable.
Looking into it even more explicitly using --topdown or --bottomup fixes it
This seems to be because my config.json file lists sortmode as 0 but --topdown is 4 and --bottomup is 3
So it seem slike 2ed7df4 is the cause. Reverting this back may cause the same issue in reverse, the config file having 3 saved while valid values are 0 and 1. But as this code has never hit release I'm happy to partially revert the merging of types.
Steps to reproduce
yay javafx
1
Output
The text was updated successfully, but these errors were encountered: