Skip to content
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

dnfdragora doesn't keep in memory the packages source list #66

Open
anaselli opened this issue Aug 6, 2017 · 3 comments
Open

dnfdragora doesn't keep in memory the packages source list #66

anaselli opened this issue Aug 6, 2017 · 3 comments

Comments

@anaselli
Copy link
Collaborator

anaselli commented Aug 6, 2017

reported https://bugs.mageia.org/show_bug.cgi?id=21453

Description of problem:
open dnfdragora: a window opens, click on "files > package sources" : the window "packages sources manager" opens, displaying a list of sources: only two boxes are checked by default: mageia-x86_64 and updates-x86_64; I have selected mageia-i586, updates-i586 and a couple of others, then I have click on the "apply button" and quitted dnfdragora; it didn't keep my choice in memory, since after running successively as root, and in this order, the commands:

dnf upgrade
urpmi --auto-update

(which returns you'll find in the attached documents) shows that dnf took into account only updates-x86_64 and not upgrades-i586

@rolfep
Copy link

rolfep commented Dec 7, 2017

I came here with, I think, the same issue.
After testing some dnf cli query commands and not finding packages the urpmf|q tools see, I opened "Repository Management" in the dnfdragora gui and checked off my other active repos, thinking this was the problem.

Returning to cli, there was no difference and I see dnfdragora does not implement my choices, even after run as root.

Remarkably, it does display opera, vivaldi, and google-talkplugin repos, added to my system by those programs but small comfort, I'm afraid :P

@anaselli
Copy link
Collaborator Author

anaselli commented Dec 7, 2017

This problem is due to dnfdaemon, we should implement something there, i thought to a workaround per user, but it is pretty ugly... so i discarded it. @Conan-Kudo should we move this to dnfdaemon?

@Conan-Kudo
Copy link
Member

I've been thinking about pulling in a variation of the dnf config-manager code into dnfdaemon. Then the UI could use that API for manipulating repositories and main configuration.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants