On Tue, 10 Mar 2026 at 13:24, Matthew Ware (mattware) via
lists.openembedded.org <[email protected]>
wrote:
> I see that the next OpenEmbedded release, Wrynose, currently uses RPM 4.20.1, 
> but that there are efforts to use RPM 6 instead. I was wondering, what is the 
> current state of the RPM 6 effort? Is it looking likely that Wrynose will 
> take RPM 6?

It still has issues, so whether the update makes it in wrynose is
unclear, and the effort may not be ready in time. Rpm updates tend to
break all over the place in all kinds of corner cases, and fixing
issues often reveals new issues, especially when the person working on
the update isn't able to run yocto CI pipeline themselves.

If rpm 6 in wrynose is important to you, help is very welcome.
Mathieu/Robert should be able point to particular remaining issues.

Alex
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#232778): 
https://lists.openembedded.org/g/openembedded-core/message/232778
Mute This Topic: https://lists.openembedded.org/mt/118239565/21656
Group Owner: [email protected]
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub 
[[email protected]]
-=-=-=-=-=-=-=-=-=-=-=-

  • [OE-core] RPM 6 in Wryn... Matthew Ware (mattware) via lists.openembedded.org
    • Re: [OE-core] RPM ... Alexander Kanavin via lists.openembedded.org
      • Re: [OE-core] ... Matthew Ware (mattware) via lists.openembedded.org
        • Re: [OE-co... Matthew Ware (mattware) via lists.openembedded.org
          • Re: [O... Alexander Kanavin via lists.openembedded.org
            • R... Clayton Casciato via lists.openembedded.org
            • R... Matthew Ware (mattware) via lists.openembedded.org
              • ... Robert Yang via lists.openembedded.org
                • ... Matthew Ware (mattware) via lists.openembedded.org
                • ... Adam Duskett via lists.openembedded.org
                • ... Robert Yang via lists.openembedded.org
                • ... Alexander Kanavin via lists.openembedded.org

Reply via email to