Re: Documentation for EPEL modules?

[Antonio Trande]

Shortly (Martin is in Cc to confirm):

1) Make a module:

$ fedpkg clone cmake3
$ fedpkg request-repo --namespace modules --exception cmake3-latest
$ fedpkg request-branch --namespace modules --repo cmake3-latest epel8

2) Writing a `modulemd` file based on this example [1]:

[1]
https://docs.fedoraproject.org/en-US/modularity/making-modules/defining-m...

3) Build the module:

$ fedpkg module-build


On 14/05/20 17:51, Petr Pisar wrote:
>  On Thu, May 14, 2020 at 06:46:29AM -0500, Richard Shaw wrote:
> > So this happened:
> >
> > https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2020-ad02b27ee3
> > https://bugzilla.redhat.com/show_bug.cgi?id=1830748
> >
> > TLDR; So we need an updated version of CMake in EPEL 8 but RHEL/CentOS
> > already provide a "3" version. Worse both the Fedora and EL versions
> > provide "cmake3" packages and binaries so it's not possible to install
> the
> > cmake3 package in EL 8.
> >
> > So here's a great use case for modularity but I have no idea how it works
> > and there doesn't seem to be any EPEL specific documentation even though
> > it's obviously getting used:
> >
> > https://bodhi.fedoraproject.org/releases/EPEL-8M
> >
> > Do we need a epel8 branch? Or is the EL module created from master?
> >
>  I believe modules in EPEL are similar to modules in Fedora. I'm not aware
>  about a documentation for modules in EPEL. There were some attempts to draft
>  the guide lines like forbiding default streams and mandating stream prefixes,
>  but I do not remember any output.
>  
>  Let's look at real examples.
>  <https://bodhi.fedoraproject.org/releases/EPEL-8M> lists 
>  avocado-latest-820200512173744.9edba152 module. That's this
>  <https://koji.fedoraproject.org/koji/buildinfo?buildID=1506528> module build
>  in Koji. The Source field reads
> <https://src.fedoraproject.org/modules/avocado.git?#12e2140e759fdb0a4477ab...;.
>  
>  Theat means "fedpkg clone modules/avocado" and there these branches:
>  
>  * latest
>    remotes/origin/52lts
>    remotes/origin/69lts
>    remotes/origin/HEAD -> origin/latest
>    remotes/origin/f29
>    remotes/origin/latest
>    remotes/origin/master
>    remotes/origin/stable
>  
>  The module stream is called "latest", let us check "latest" branch:
>  
>  commit 12e2140e759fdb0a4477ab2432c411a4452d8efc (HEAD -> latest, origin/latest,
> origin/HEAD)
>  Author: Merlin Mathesius <mmathesi(a)redhat.com&gt;
>  Date:   Tue May 12 12:37:44 2020 -0500
>  
>      Rebuild with avocado 79.0.
>  
>      Signed-off-by: Merlin Mathesius <mmathesi(a)redhat.com&gt;
>  
>  So you can see the module is built from a non-epel8 branch. An avocado.yaml
>  file lists these dependencies:
>  
>    dependencies:
>    - buildrequires:
>        platform: []
>      requires:
>        platform: []
>  
>  So "platform" is left empty to expand it by MBS on all available platforms. If
>  you look at koji listing
>  <https://koji.fedoraproject.org/koji/packageinfo?packageID=26942>;, 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 buld was performed by "merlinm" users. You can ask him for more details.
>  
>  -- Petr
>  
>  
>  _______________________________________________
>  devel mailing list -- devel(a)lists.fedoraproject.org
>  To unsubscribe send an email to devel-leave(a)lists.fedoraproject.org
>  Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
>  List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
>  List Archives:
> https://lists.fedoraproject.org/archives/list/[e-mail]
>   
-- 
---
Antonio Trande
Fedora Project
mailto 'sagitter at fedoraproject dot org'
GPG key: 0x7B30EE04E576AA84
GPG key server: https://keys.openpgp.org/