[pungi-fedora] Issue #738: Replace build_composeinfo with compose-create-legacy-composeinfo

[Martin Styk]

martstyk reported a new issue against the project: `pungi-fedora` that you are following:
``
I suggest replacing build_composeinfo with compose-create-legacy-composeinfo
(compose-utils package).
build_composeinfo is not providing enough information to distinguish between 2 composes.
For example Beta & GOLD.

F29 GOLD
https://paste.fedoraproject.org/paste/kfRpr5QYWq64vrQZlp2Kqg 
F29 Beta
https://paste.fedoraproject.org/paste/HjE6dcKJFWRKJf4iZ5XQEA

This can lead to consider GOLD & Beta as same compose which is obviously wrong.
On other hands .composeinfo generated by compose-create-legacy-composeinfo looks like
this:
F29 GOLD
https://paste.fedoraproject.org/paste/pyJhX1qlWy-S2CWZDO-xKQ
F29 Beta
https://paste.fedoraproject.org/paste/7OcbcowriGvk7wKX3r8hQw

``

To reply, visit the link below or just reply to this email
https://pagure.io/pungi-fedora/issue/738

[Mike Boswell]

mboswell added a new comment to an issue you are following:
``
In the past Fedora releases were not automatically imported to Beaker correctly w/ the
released name (Fedora-29). Instead it was imported as Fedora-29-20181024.1 . We should
require the compose-create-legacy-composeinfo to use name = Fedora-29 VS name =
Fedora-29-20181024.1 
``

To reply, visit the link below or just reply to this email
https://pagure.io/pungi-fedora/issue/738

[Mohan Boddu]

mohanboddu added a new comment to an issue you are following:
``
@kevin Before I make this change, do you know if the current composeinfo file is used
anywhere else other than beaker?
``

To reply, visit the link below or just reply to this email
https://pagure.io/pungi-fedora/issue/738

[Kevin Fenzi]

kevin added a new comment to an issue you are following:
``
I am not sure. It might be used in pulp?

``

To reply, visit the link below or just reply to this email
https://pagure.io/pungi-fedora/issue/738

[Jeffrey Bastian]

jbastian added a new comment to an issue you are following:
``
This problem came up again yesterday with the import of Fedora 31 into Beaker. Kickstarts
were failing because it was using the Beta kernel and initrd with the GA install.img, and
the mismatch of kernel version and modules led to filesystem problems (the kernel could
not load the xfs.ko module). This happens with every Fedora release and it requires manual
effort to fix. Please fix the compose metadata so Beta and GA are distinguishable to
Beaker (and other tools).
``

To reply, visit the link below or just reply to this email
https://pagure.io/pungi-fedora/issue/738

[Martin Styk]

martstyk added a new comment to an issue you are following:
``
I will tell you a secret. This happened again during Fedora 32 :)
``

To reply, visit the link below or just reply to this email
https://pagure.io/pungi-fedora/issue/738

[jiri vanek]

jvanek added a new comment to an issue you are following:
``
 We second.   compose-create-legacy-composeinfo  will make import of newest fedoras to our
infra much more smooth. TY!
``

To reply, visit the link below or just reply to this email
https://pagure.io/pungi-fedora/issue/738

[Mike Boswell]

mboswell added a new comment to an issue you are following:
``
@jiri Vanek  How will compose-create-legacy-composeinfo help?  I don't
doubt you I just want to understand how.  I did the clean up of Fed32
and it was no fun.
Mike

On Thu, May 21, 2020 at 5:34 AM jiri vanek <pagure(a)pagure.io&gt; wrote:
>  jvanek added a new comment to an issue you are following:
>  ``
>   We second.   compose-create-legacy-composeinfo  will make import of newest fedoras to
> our infra much more smooth. TY!
>  ``
>
>  To reply, visit the link below or just reply to this email
>  https://pagure.io/pungi-fedora/issue/738
>  

``

To reply, visit the link below or just reply to this email
https://pagure.io/pungi-fedora/issue/738