#12437 consistent naming of release artifacts
Closed: Get back later a month ago by jnsamyak. Opened a month ago by petersen.

Lately I am seeing looser naming of release artifacts.

For Fedora 41, both the iso images for MiracleWM and KDE Mobile have different filename conventions from other Live images:

Fedora-MiracleWM-Live-41-1.4.x86_64.iso
Fedora-KDE-Mobile-Live-41-1.4.x86_64.iso

whereas all other Live iso images are named:

Fedora-<NAME>-Live-x86_64-41-1.4.iso

A similar thing happened previously with the IoT image which was named differently to other ostree iso images.

This kind of thing makes life harder for everyone who keeps track of these filenames: and makes scripting/automation harder too, including for me as the maintainer of dl-fedora for example, but I am sure it affects many others too.

It would be great if there was some way for releng to check and enforce the naming schemes of release artifacts.


The naming convention is mostly enforced by the image build tools. Most of the tools are not flexible in filename structure, but for kiwi created artifacts, we're enforcing a global naming convention at the Pungi level.

Okay so Neal explained to me these new images are made with Kiwi, which uses consistent NVRA naming via pungi for all kinds of artifacts.

So hopefully as gradually more release artifacts are going to be made with Kiwi going forward all the filenames should become consistent again eventually at some point, but in the meantime things are going to be a bit unpredictable unfortunately it seems.

yeah, +1 to that! We could either do these renaming manually, but again it will be more error-prone I guess

Hopefully, this issue will go away once we have these build using kiwi, until then we have to deal with such exceptions.

Metadata Update from @jnsamyak:
- Issue close_status updated to: Get back later
- Issue status updated to: Closed (was: Open)

a month ago

Log in to comment on this ticket.

Metadata