Switching to RPMv4

Tags: #<Tag:0x00007fcbcb2b9438>



we are bout to switch RPM to version 4.

Cooker and 3.0 may be broken for upcoming days, as we need to adapt our docker builders and scripts to RPM4 and dnf.

Yes DNF, and this means urpmi is going to say bye bye for cooker and 4.0. @bero and @ngompa are working on smooth upgrade process from 3.x to cooker/4.0

So what are the benefits ?

  • RPM4 is actively maintained over RPM5
  • RPM4 gives whole consistent suit for package management and repository management
  • DNF a wide standard to manage rpm packages (install, uninstall, upgrade etc.)
  • Less bloat, no more ugly perl code and hacks
  • No more ugly hacks and ancient adaptations just to make thing a “little work”
  • Support from the upstream

Sorry for all the inconvenience.

Big thanks goes to @ngompa for preparing whole RPM4, @bero, @fedya





Thanks four your huge work! :smiley:


Here is the status.

cooker x86_64 has rpm4 available
cooker i686 has rpm4 available
cooker aarch64 is rpm4 ready
cooker armv7hl awaits for rpm4

ABF builders has beed adapted to rpm4 and dnf.
ABF publisher has beed adapted to rpm4 and createrepo_c
ABF builders are adapted to use mock client side chroot-cache (greatly improves rpm build time)

ABF isobuilder needs to support dnf for cooker and urpmi for 3.0 and older releases - without this building cooker ISO on abf is not possbile
abf-console-client needs to be adapted to rpm4, mock and dnf

Many thanks goes to @ngompa @bero @fedya for doing great job!


Just having a look to IRC or ABF in these days we can take an idea of how great is the job you all are doing …