Bug 28245 - dnfdragora 2.1.1 from Mageia 8...repository settings don't always hold
Summary: dnfdragora 2.1.1 from Mageia 8...repository settings don't always hold
Status: RESOLVED DUPLICATE of bug 21453
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: 8
Hardware: All Linux
Priority: Normal normal
Target Milestone: ---
Assignee: Mageia Bug Squad
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2021-01-29 00:13 CET by Lloyd Osten
Modified: 2021-01-29 01:55 CET (History)
3 users (show)

See Also:
Source RPM: not sure...dnfdragora
CVE:
Status comment:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Description Lloyd Osten 2021-01-29 00:13:19 CET 
Description of problem:The repository settings of dnfdragora 2.1.1 (as supplied with Mageia 8) don't always hold. Sometimes they work; sometimes they don't. I disabled all cauldron repositories; sometimes they show up anyway. And the Mageia repositories (not cauldron) just seem to disappear.

BTW, I did a netinstall of Mageia 8 today.


Version-Release number of selected component (if applicable):dnfdragora 2.1.1


How reproducible: It happened several times. After closing dnfdragora and restarting it, the enabled repositories seem to change.


Steps to Reproduce:
1.Start dnfdragora and enable some repositories.
2.Close dnfdragora.
3.Restart dnfdragora and see if the repositories you enabled are still there (or are not persistent)
Lloyd Osten 2021-01-29 00:13:50 CET

CC: (none) => lloyd.osten

Comment 1 Morgan Leijström 2021-01-29 00:47:26 CET 
Thank you for reporting.

I see we have a bug for this already, unfortunately not fixed yet.

*** This bug has been marked as a duplicate of bug 21453 ***

Status: NEW => RESOLVED
CC: (none) => fri
Resolution: (none) => DUPLICATE

Comment 2 Angelo Naselli 2021-01-29 01:55:50 CET 
Unfortunately we don't have api yet to do that...

Repo management is valid for the time dnfdragora is open, changes are not permanent.

CC: (none) => anaselli
Note You need to log in before you can comment on or make changes to this bug.