From Fedora Project Wiki

< User:Denisarnaud

Revision as of 17:57, 14 May 2020 by Denisarnaud (talk | contribs) (Creation)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)

Message from Petr Pisar on the 14 May 2020, on the Fedora Devel mailing list:

Let's look at real examples. <> lists avocado-latest-820200512173744.9edba152 module. That's this <> module build in Koji. The Source field reads <>.

Theat means "fedpkg clone modules/avocado" and there these branches:

  • latest
 remotes/origin/HEAD -> origin/latest

The module stream is called "latest", let us check "latest" branch:

commit 12e2140e759fdb0a4477ab2432c411a4452d8efc (HEAD -> latest, origin/lat= est, origin/HEAD) Author: Merlin Mathesius <> Date: Tue May 12 12:37:44 2020 -0500

   Rebuild with avocado 79.0.
   Signed-off-by: Merlin Mathesius <>

So you can see the module is built from a non-epel8 branch. An avocado.yaml file lists these dependencies:

 - buildrequires:
     platform: []
     platform: []

So "platform" is left empty to expand it by MBS on all available platforms. If you look at koji listing <>, there are five modules avocado-latest-*20200512173744 builds of from the same sources. That probably means that Koji attempts to build the module for all Fedoras and EPEL 8. Technically, it's possible to override the platform with "fedpkg module-build" command, but I cannot see any trace of it in the logs.

That build was performed by "merlinm" users. You can ask him for more details.