Bug 32301

Summary: When upgrading from mga8 to mga9 using the dnf CLI, the urpmi media sources are not updated
Product: Mageia Reporter: Jeff Robins <jeffrobinsSAE>
Component: InstallerAssignee: Mageia Bug Squad <bugsquad>
Status: RESOLVED INVALID QA Contact:
Severity: normal    
Priority: Normal CC: davidwhodgins
Version: 9   
Target Milestone: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Source RPM: CVE:
Status comment:

Description Jeff Robins 2023-09-18 00:22:07 CEST
Description of problem:
When upgrading from mga8 to mga9 using the dnf command line process from the mga9 release notes page, the urpmi media sources are not updated and are still set to mga8.  The updater applet in KDE (not sure about others) may report updates that are for mga8.  It did this for something today that was openssl related.  I didn't realize what I had seen until after it was done.

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

How reproducible:
always

Steps to Reproduce:
1. Upgrade from mga8 to mga9 using dnf command line
2. Check the media sources for urpmi using the Mageia Control Center and see they are set to mga8
Comment 1 Jeff Robins 2023-09-18 00:23:04 CEST
Core Release URL on mga9, after upgrading from mga8 using the DNF command line:
http://mirrors.mageia.org/api/mageia.8.$ARCH.list
Comment 2 sturmvogel 2023-09-18 14:32:25 CEST
MCC only uses urpmi. DNFdragora only uses DNF.

Both tools are separated from each other and use different repository definition files. That means updating/changing DNF repositories does NOT change urpmi repositorys and vice versa. You need to change the repository definitions separate from each other. This is as it is designed atm.
Comment 3 Dave Hodgins 2023-09-18 20:08:13 CEST
The intention is that while urpmi is always used for an initial install,
systems should either stay with urpmi or switch to dnf (and stop using
urpmi/mgaapplet), not mix them.

Closing as invalid since this is the way it's intended to work.

CC: (none) => davidwhodgins
Resolution: (none) => INVALID
Status: NEW => RESOLVED