Re: [OS-BUILD PATCHv2 0/5] redhat: introduce versioning for Gemini kernels

2023-04-05 Thread Don Zickus (via Email Bridge)
From: Don Zickus on gitlab.com https://gitlab.com/cki-project/kernel-ark/-/merge_requests/2386#note_1342932614 I am ok with the thread being closed. ___ kernel mailing list -- kernel@lists.fedoraproject.org To unsubscribe send an email to kernel-le...@li

Re: [OS-BUILD PATCHv2 0/5] redhat: introduce versioning for Gemini kernels

2023-04-05 Thread Prarit Bhargava (via Email Bridge)
From: Prarit Bhargava on gitlab.com https://gitlab.com/cki-project/kernel-ark/-/merge_requests/2386#note_1342830110 @dzickus? Can this thread be closed? ___ kernel mailing list -- kernel@lists.fedoraproject.org To unsubscribe send an email to kernel-le.

Re: [OS-BUILD PATCHv2 0/5] redhat: introduce versioning for Gemini kernels

2023-04-05 Thread Prarit Bhargava (via Email Bridge)
From: Prarit Bhargava on gitlab.com https://gitlab.com/cki-project/kernel-ark/-/merge_requests/2386#note_1342829822 Okay, testing of `kernel-redhat-0.1-42.el9` -> `kernel-redhat-0.1-42.el10` was successful, and we've answered the issue of upgrading to an older kernel version. So I think this thre

Re: soname bump: libtraceevent and libtracefs

2023-04-05 Thread Justin Forbes
On Wed, Apr 5, 2023 at 5:05 AM Zamir SUN wrote: > > Hi, > > I'm working on libtraceevent and libtracefs update. There will be soname > bump happening to them. Namely, > > libtraceevent.so 1.6.3 -> 1.7.2 > libtracefs.so 1.5.0 -> 1.6.4 > > IIRC only kernel-tools (for perf and rtla) and trace-cmd dep

Re: [OS-BUILD PATCHv2 0/5] redhat: introduce versioning for Gemini kernels

2023-04-05 Thread Prarit Bhargava (via Email Bridge)
From: Prarit Bhargava on gitlab.com https://gitlab.com/cki-project/kernel-ark/-/merge_requests/2386#note_1342374369 From Jaroslav Mracek in private email: "Our solver transforms `kernel- redhat-0.1-42.el9` into name ('kernel-redhat'), epoch (not mentioned but present in metadata -> `0`), version (

Re: [OS-BUILD PATCHv2 0/5] redhat: introduce versioning for Gemini kernels

2023-04-05 Thread Prarit Bhargava (via Email Bridge)
From: Prarit Bhargava on gitlab.com https://gitlab.com/cki-project/kernel-ark/-/merge_requests/2386#note_1342289212 @jmflinuxtx please don't feel bad about raising this issue. This is EXACTLY why we do reviews and it's worth checking in with the rpm and dnf teams. I'm also going to do the test I

Re: [OS-BUILD PATCHv2 0/5] redhat: introduce versioning for Gemini kernels

2023-04-05 Thread Justin M. Forbes (via Email Bridge)
From: Justin M. Forbes on gitlab.com https://gitlab.com/cki-project/kernel-ark/-/merge_requests/2386#note_1342277965 I just did a quick test rebuilding the F37 kernel-test against F38 and dnf will consider it an upgrade. This was originally an issue in Fedora a bit over 10 years ago, so there has

Re: [OS-BUILD PATCHv2 0/5] redhat: introduce versioning for Gemini kernels

2023-04-05 Thread Prarit Bhargava (via Email Bridge)
From: Prarit Bhargava on gitlab.com https://gitlab.com/cki-project/kernel-ark/-/merge_requests/2386#note_1342252181 @jstancek, it may be that we do have to add a RHEL_MAJOR value into the new VR. But based on @knurd42 comment above I'd like to have a definitive statement about whether or not the

soname bump: libtraceevent and libtracefs

2023-04-05 Thread Zamir SUN
Hi, I'm working on libtraceevent and libtracefs update. There will be soname bump happening to them. Namely, libtraceevent.so 1.6.3 -> 1.7.2 libtracefs.so 1.5.0 -> 1.6.4 IIRC only kernel-tools (for perf and rtla) and trace-cmd depends on them. So I'm also copying their corresponding contacts