I’ve read about this problem and therefore blacklisted linux-zen and zen-headers (using the zen kernel)
Now if I look for it in the package search, I can see 5.12.13.zen1-2 being flagged. So I assume, that the maintainers are aware of the problem and therefore “reverted” the change.
In that post there are comments stating, that the problem is gone with the new update. The zen kernel seems not to be updated, but the generic kernel is also still flagged.
What am I missing? Can someone explain what is happening? Can I update the kernel?
The issue is fixed with 5.12.14, so yes you can update (both zen and regular kernel is at .14).
Imho, the reason that it got immediately flagged again is that 5.13.0 is out…
1 Like
Ah, so testing repo is enabled by default? Edit: No, it’s disabled. Why am I getting the .14 update? (It is indeed working)
I don’t understand what you mean here.
Because it’s there in the regular repository, not only testing.
What I’m saying is that linux-zen got updated to 5.12.14 but got immediately flagged as out of date (again) by some user because the 5.13.0 was already released. https://www.kernel.org/
1 Like
I was a bit stupid and forgot to reload the website.
But what I still don’t understand: The package is flagged, why am I getting the update?
What is the connection between these two events? 14 is newer than 13 so 14 should not be out of date?
Why not? Everyone can flag something as out-of-date. It’s meant as a notification for the package maintainer to update it. It does not prevent it from being installed or anything.
We are talking about:
5.12.14
5.13.0
The 5.13 is new kernel series, obviously newer than 5.12
1 Like
Ah. I understand.
Oh. Yeah. That makes sense.
Thanks for your reply!
1 Like
This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.