Bug 19471

Summary: dnf: duplicate repositories in repolist
Product: Mageia Reporter: Ulrich Beckmann <bequimao.de>
Component: RPM PackagesAssignee: Neal Gompa <ngompa13>
Status: RESOLVED INVALID QA Contact:
Severity: normal    
Priority: Normal CC: marja11
Version: Cauldron   
Target Milestone: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Source RPM: mageia-repos CVE:
Status comment:
Attachments: CLI output from dnf repolist

Description Ulrich Beckmann 2016-09-27 16:55:07 CEST
Created attachment 8455 [details]
CLI output from dnf repolist

I find two additional repos in my repolist, mageia-x86_64 and updates-x86_64. They were added automatically, I don't recall to have them added manually.

There are often slight differences between mageia and cauldron in the number of packages, but I did not spot any problem during updates yet.

I would expect that the cauldron repos were disabled in the process.

Best regards,
Ulrich
Comment 1 Marja Van Waes 2016-09-27 18:23:22 CEST
If I had used the rpmnew files, both cauldron and Mga6 repos would be enabled here, too

[marja@cldrn_64 ~]$ grep "enabled=1" /etc/yum.repos.d/*rpmnew
/etc/yum.repos.d/cauldron-x86_64.repo.rpmnew:enabled=1
/etc/yum.repos.d/cauldron-x86_64.repo.rpmnew:enabled=1
/etc/yum.repos.d/mageia-x86_64.repo.rpmnew:enabled=1
/etc/yum.repos.d/mageia-x86_64.repo.rpmnew:enabled=1
[marja@cldrn_64 ~]$

Those files date from July 4th, though, so I don't understand how you end up with mixed cauldron/mga6 repos now if you didn't already use a mixed set :-/

CC: (none) => marja11
Assignee: bugsquad => ngompa13

Comment 2 Neal Gompa 2016-09-27 18:40:06 CEST
On Cauldron systems, this is normal, as mageia-repos-cauldron is a required dependency of mageia-repos in Cauldron systems[1]. When Mageia 6 is released, mageia-repos-cauldron will not be a required dependency.

They currently have duplicate content because Mageia Cauldron == Mageia 6. But the idea is that it won't always be that way. When Mageia 6 releases, then Cauldron will bump to become Mageia 7, and the standard repositories will self-disable due to pointing to an invalid path. Then, you'll be left with only the Cauldron repositories.

[1]: http://svnweb.mageia.org/packages/cauldron/mageia-repos/current/SPECS/mageia-repos.spec?view=markup

Status: NEW => RESOLVED
Resolution: (none) => INVALID
Source RPM: (none) => mageia-repos