Mageia forum

Hi!

Two mageia 8 installations. Both have kernel----latest packages installed.

But the desktop one has:

Code: Select all

# rpm -qa|grep kernel
kernel-desktop-5.10.37-2.mga8-1-1.mga8
kernel-desktop-5.10.30-1.mga8-1-1.mga8
kernel-desktop-5.10.33-1.mga8-1-1.mga8
kernel-desktop-devel-latest-5.10.37-2.mga8
kernel-userspace-headers-5.10.37-2.mga8
kernel-firmware-20201218-1.mga8
kernel-desktop-devel-5.10.33-1.mga8-1-1.mga8
kernel-firmware-nonfree-20210716-1.mga8.nonfree
kernel-desktop-devel-5.10.37-2.mga8-1-1.mga8
kernel-desktop-devel-5.10.30-1.mga8-1-1.mga8
kernel-desktop-latest-5.10.37-2.mga8

and the laptop has:

Code: Select all

# rpm -qa|grep kernel
kernel-desktop-devel-5.12.4-1.mga8-1-1.mga8
kernel-desktop-5.12.4-1.mga8-1-1.mga8
kernel-desktop-devel-latest-5.12.4-1.mga8
kernel-firmware-nonfree-20210716-1.mga8.nonfree
kernel-firmware-20201218-1.mga8
kernel-userspace-headers-5.12.4-1.mga8
kernel-desktop-5.10.37-2.mga8-1-1.mga8
kernel-desktop-devel-5.10.37-2.mga8-1-1.mga8
kernel-desktop-latest-5.12.4-1.mga8

and there is already a kernel-desktop-5.14 available! None of them has it yet...

So, please, what is the kernel updating policy?

Thanks a lot

I forgot to say that both installations have
Core, Nonfree, Tainted, and their update repos enable...

What is your actual question? It depends on what repositories you have enabled. The latest kernel from core updates is kernel-desktop-latest-5.10.75-1.mga8.
The newer ones 5.12 to 5.14 that you're referring to are from backports. Have a look at e.g. https://madb.mageia.org/package/show/ap ... top-latest
So the question is why do you have a kernel update from backports installed on one machine, and not on the other, how should we answer that question for you ... ?

This may be user induced, or because the quirk in updating that it updates kernels to backports if backport is configured although not enabled...
We hit it sometimes when testing... https://bugs.mageia.org/show_bug.cgi?id=29507#c2

morgano wrote:or because the quirk in updating that it updates kernels to backports if backport is configured although not enabled...

In your example you manually selected packages to install, that's not a regular update process.

Problem is it installed backport kernel which i did not select, and even though that repo was disabled.
https://bugs.mageia.org/show_bug.cgi?id=29148

Ok, things are becoming clearer to me now. Thanks.

Indeed, althought backports updates are not enabled in both installations, I may have enabled/disabled it once in the past in the laptop, but I can't say this caused kernel 5.12 to be installed.

Anyway, in the desktop, as for checking for what was supposed to be installed and wasn't, for some reason, I did:
# urpmi --auto-update
and then I knew there is a kernel-desktop-5.14 (no backport updates enable!). I did not install the updates and the update applet did not signed for any available update.

I see this is not a concern since I'm OK with the Core updates ...

Thanks again

As I recall, I have a laptop that installed kernel 5.14 as well, and I have never enabled backports on any machine.

Maybe ran rpmdrake at some point and switch to "all updates" or "backports" filter? For that you don't need to have backports enabled, they are enabled and updated on-demand, after that they get disabled again.

FWIW, I'm updating via urpmi --auto-update and I've only got kernel-desktop-5.10.x installed, so it doesn't magically update to anything from backports.
If it does, you should write down clear steps to reproduce the issue and report a bug for that, because that is clearly not intended and would be broken.
Although the only slightly related bug for that explains the issue in https://bugs.mageia.org/show_bug.cgi?id=29148#c3 - but this is not for updates, that is after manually selecting a specific package version.

doktor5000 wrote:
FWIW, I'm updating via urpmi --auto-update and I've only got kernel-desktop-5.10.x installed, so it doesn't magically update to anything from backports.

Just to inform: in the desktop, Tainted backports enabled but not for updates.
#urpmi --auto-updates does select kernel-desktop-5.14 for updating.

This behaviour is not repeatable. It also wouldn't make sense because the kernel is not related to the tainted repo. It's in the core repo.

Only Kernel 5.10 installed:

Code: Select all

[root@laptop ~]# rpm -qa|grep kernel
kernel-desktop-5.10.62-1.mga8-1-1.mga8
kernel-desktop-5.10.75-1.mga8-1-1.mga8
kernel-userspace-headers-5.10.75-1.mga8
kernel-desktop-5.10.70-1.mga8-1-1.mga8
kernel-firmware-nonfree-20210716-1.mga8.nonfree
kernel-desktop-latest-5.10.75-1.mga8
kernel-firmware-20201218-1.mga8


Enabling the tainted 32/64bit backport repo (distrib27/44) will NOT pull the 5.14 kernel:

Code: Select all

[root@laptop ~]# urpmi --auto-update
medium "Core Release (distrib1)" is up-to-date
medium "Core Updates (distrib3)" is up-to-date
medium "Nonfree Release (distrib11)" is up-to-date
medium "Nonfree Updates (distrib13)" is up-to-date
medium "Tainted Release (distrib21)" is up-to-date
medium "Tainted Updates (distrib23)" is up-to-date
medium "Tainted Backports (distrib27)" is up-to-date
medium "Core 32bit Release (distrib31)" is up-to-date
medium "Core 32bit Updates (distrib32)" is up-to-date
medium "Nonfree 32bit Release (distrib36)" is up-to-date
medium "Nonfree 32bit Updates (distrib37)" is up-to-date
medium "Tainted 32bit Release (distrib41)" is up-to-date
medium "Tainted 32bit Updates (distrib42)" is up-to-date
medium "Tainted 32bit Backports (distrib44)" is up-to-date
medium "google-chrome" is up-to-date
Packages are up to date
[root@laptop ~]#


ONLY if you activate the core backports repo (distrib7), the 5.14 kernel gets pulled:

Code: Select all

[root@laptop ~]# urpmi --auto-update
medium "Core Release (distrib1)" is up-to-date
medium "Core Updates (distrib3)" is up-to-date
medium "Core Backports (distrib7)" is up-to-date
medium "Nonfree Release (distrib11)" is up-to-date
medium "Nonfree Updates (distrib13)" is up-to-date
medium "Tainted Release (distrib21)" is up-to-date
medium "Tainted Updates (distrib23)" is up-to-date
medium "Core 32bit Release (distrib31)" is up-to-date
medium "Core 32bit Updates (distrib32)" is up-to-date
medium "Nonfree 32bit Release (distrib36)" is up-to-date
medium "Nonfree 32bit Updates (distrib37)" is up-to-date
medium "Tainted 32bit Release (distrib41)" is up-to-date
medium "Tainted 32bit Updates (distrib42)" is up-to-date
medium "google-chrome" is up-to-date
To satisfy dependencies, the following packages are going to be installed:
  Package                        Version      Release       Arch   
(medium "Core Backports (distrib7)")
  cpupower                       5.14.14      1.mga8        x86_64 
  kernel-desktop-5.14.14-1.mga8  1            1.mga8        x86_64 
  kernel-desktop-latest          5.14.14      1.mga8        x86_64 
  kernel-userspace-headers       5.14.14      1.mga8        x86_64 
76MB of additional disk space will be used.
69MB of packages will be retrieved.
Proceed with the installation of the 4 packages? (Y/n)

You can stumble into this quirk various ways, read through bug 29148.

I have not grasped the details, but i think it was confirmed the tool looks in backports even if not enabled, and if the repo is updated and there is a -latest package, it erroneously pulls the package from backport.

My comment was related to the latest claim from adhefe, that the tainted backport repo pulls the 5.14 kernel. This is not the case as i have shown in my previous post.

adhefe wrote:Just to inform: in the desktop, Tainted backports enabled but not for updates.
#urpmi --auto-updates does select kernel-desktop-5.14 for updating.

urpmi --auto-select does not care if a repo is marked as updates or not, only if it is enabled. It will select all latest packages from all enabled repos. That's on you, and also backports is not enabled by default.
You would need to use --update option to only pull updates from repos marked as update repos - which backports is not, by the way. It only offers new versions, it's not meant as an update repository.

man urpmi wrote: --update
Use only update media. This means that urpmi will search packages and resolve dependencies only in media marked as containing updates.
[...]
--auto-select
Select all packages that can be upgraded, according to already installed packages and packages listed in various registered media.
--auto-update
Like --auto-select, but also updates all relevant media before selection of upgradeable packages is made. This avoids a previous call to "urpmi.update".

Thanks for all

Please, don't forget to mark the topic [DONE].
You can do so, by editing the subject/title in the first message in this topic.
Write [DONE] to the left of subject/title, thanks ahead.

Posting this a new topic as well

Because of discussion of kernel updates using (I'm sure I don't understand here?) the wrong repository,
https://forums.mageia.org/en/viewtopic.php?f=8&t=14371
and because the updater is offering to jump to Kernel "5.15"

To satisfy dependencies, the following packages are going to be installed:
Package Version Release Arch
(medium "Core Updates")
cpupower 5.15.4 1.mga8 x86_64
kernel-desktop-5.15.4-1.mga8 1 1.mga8 x86_64
kernel-desktop-latest 5.15.4 1.mga8 x86_64
kernel-userspace-headers 5.15.4 1.mga8 x86_64

I am right now

Operating System: Mageia 8
KDE Plasma Version: 5.20.4
KDE Frameworks Version: 5.76.0
Qt Version: 5.15.2
Kernel Version: 5.10.78-desktop-1.mga8 <---------
OS Type: 64-bit

I am left wondering, is this a real update? jumping from 5.10 to 5.14?

And is there a story on this?

see => https://bugs.mageia.org/show_bug.cgi?id=29682

this kernel has just completed QA testing and has been approved for release.
If you are already seeing it, it means your configured mirror has already updated and is presenting the kernel for update

$ uname -a
Linux localhost.localdomain 5.15.4-desktop-1.mga8 #1 SMP Sun Nov 21 14:04:46 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux