-
-
Notifications
You must be signed in to change notification settings - Fork 391
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
don't ask for confirmation if there is only one remote repository installed #4364
Comments
The install command can search available remotes for a specified flatpak when a remote wasn't specified. In case only one remote is configured, or in case only one of the configured remotes matches the ref specified, we currently prompt the user to confirm use of the remote anyway (unless -y/--assumeyes was used). Skip this prompt even when -y/--assumeyes was not used, since the remote to use will still effectively be confirmed when the list of refs to be installed is presented for confirmation. Fixes #4364
Thanks for the bug report, fix available in #4382 |
I dont know if it is also needed but I will add it here: there are two scenarios with one remote installed. first:
the second scenario is when user installs with a complete name ( I dont know what is the technical word for it ) like "flatpak install org.freefilesync.FreeFileSync" which would give :
as can be seen the first scenario has the redundant question which is the question number one. the second scenario has only one question but it the the first scenario's first question:
so if you remove the first scenario's first question then it may impact the second scenario too because the second scenario doesnt ask for
|
Yeah the PR changes the behavior in both cases to avoid the |
what I mean was that even in second scenario the user needs to see from what remote it is going to be installed. if you remove that found similar ref question the user still see that in 1st case but if you remove the question, then in second case user will not see the remote used in the installation. for example imagine user has two repos, one defaut and one that has, say, firefox experimental builds. then the user should only get one question that combines both info into one. this way when there is one ref, user only is asked one question that has repo info in too. so overall I wanted to be a way (if possible) that if only one result is found, be it a general word or a specific ref , and be it in one repo only or one found in all the repos together, then user only is asked one question that has the ref and the repo name in it. but I dont insist on this if it messes with the logic of it too much. EDIT: i used bold for it but maybe because it is inside code snippet it gets shown as literal double stars. |
No, the user will still see the remote being used even when they have more than one configured and don't explicitly specify which to use in the |
you are right. thanks for the answer. |
Reopening this until the PR is merged |
The install command can search available remotes for a specified flatpak when a remote wasn't specified. In case only one remote is configured, or in case only one of the configured remotes matches the ref specified, we currently prompt the user to confirm use of the remote anyway (unless -y/--assumeyes was used). Skip this prompt even when -y/--assumeyes was not used, since the remote to use will still effectively be confirmed when the list of refs to be installed is presented for confirmation. Fixes #4364
Linux distribution and version
archlinux
Flatpak version
Flatpak 1.11.2
Description of the problem
even though I have only one remote configured ,flatpak still ask me if I am sure that I want to use that repo when searching for an app to install
Steps to reproduce
only have the default flatpak repo installed then run:
flatpak install app/org.rolisteam.rolisteam/x86_64/stable
Looking for matches…
Found similar ref(s) for ‘app/org.rolisteam.rolisteam/x86_64/stable’ in remote ‘flathub’ (user).
Use this remote? [Y/n]:
the question is redundant when use only has one repo.
The text was updated successfully, but these errors were encountered: