Description of problem: during updates, the system complains about a conflict between: kernel-desktop-latest-4.1.8-1.mga5.x86_64 kernel-desktop-4.1.8-1.mga5-1-1.mga5.x86_64 and won't install the '-latest' one. The problem is there since several days. Actual kernel : 3.19.8-2.mga5 (from -kernel-desktop-latest version) Reproducible: Steps to Reproduce:
There should be no such issue :/ and "3.19.8-2.mga5" is a pre-final mga5 kernel... Can you show full urpmi output
I feel like I don't understand my dear mageia anymore :/ Let me explain: I was using MageiaUpdate under cauldron since several months, after mga5 was released, I kept using it and it kept installing mga5 packages (which was what I wanted!), and I forgot that I had done nothing to stay in mga5... Now that you asked me the full output, I used the CLI: sudo urpmi --auto-update -v and it proposed me mga6 packages!!! Which was no absurd as all lines in urpmi.cfg where pointing on cauldron. After changing all links in urpmi.cfg to mga 5 ones, and refreshing all media through MageiaUpdate, the kernel package installs just fine :) So I just have one question before closing the bug: What was using MageiaUpdate to install mga5 packages when urpmi.cfg was pointing on cauldron?
Mass-reassigning all bugs with "kernel" in the Source RPM field that are assigned to tmb, to the kernel packagers group, because tmb is currently MIA.
Assignee: tmb => kernel
(In reply to Claire Revillet from comment #2) > I feel like I don't understand my dear mageia anymore :/ > > Let me explain: > I was using MageiaUpdate under cauldron since several months, after mga5 was > released, I kept using it and it kept installing mga5 packages (which was > what I wanted!), and I forgot that I had done nothing to stay in mga5... > > Now that you asked me the full output, I used the CLI: > sudo urpmi --auto-update -v > and it proposed me mga6 packages!!! > Which was no absurd as all lines in urpmi.cfg where pointing on cauldron. > > After changing all links in urpmi.cfg to mga 5 ones, and refreshing all > media through MageiaUpdate, the kernel package installs just fine :) > > So I just have one question before closing the bug: What was using > MageiaUpdate to install mga5 packages when urpmi.cfg was pointing on > cauldron? It's 2½ yrs later, and no one answered. Closing as OLD, because Mageia 5 has officially reached its End of Life on December 31st, 2017 https://blog.mageia.org/en/2017/11/07/mageia-5-eol-postponed/ It only continued to get important security updates since then, but non-security bugs have no chance of still getting fixed. Please reopen if something similare happens in Mageia 6 (with Mga7cauldron packages suddenly getting suggested instead of stable Mga6 ones) Reassigning to the Mageia Tools maintainers, in case this report needs to be reopened for a supported Mga release.
Status: NEW => RESOLVEDResolution: (none) => OLDCC: (none) => marja11Assignee: kernel => mageiatoolsSource RPM: kernel-desktop-latest-4.1.8-1.mga5.x86_64.rpm => (none)Summary: kernel-desktop-latest-4.1.8-1.mga5 won't install => After installing stable mga5 packages for several months, urpmi --auto-update suddenly wanted to install mga6cauldron packages (was: kernel-desktop-latest-4.1.8-1.mga5 won't install)