<div dir="ltr"><div dir="ltr"><br></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Fri, 12 Jul 2019 at 08:05, Leon Fauster via CentOS-devel <<a href="mailto:centos-devel@centos.org">centos-devel@centos.org</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">Am 12.07.2019 um 02:54 schrieb Nico Kadel-Garcia <<a href="mailto:nkadel@gmail.com" target="_blank">nkadel@gmail.com</a>>:<br>
> <br><br>
> On top of that, I build a local copy of mock, using my tools at<br>
> <a href="https://github.com/nkadel/nkadel-rhel-8-mockrepo" rel="noreferrer" target="_blank">https://github.com/nkadel/nkadel-rhel-8-mockrepo</a> . EPEL 8 is welcome<br>
> to my tools to build mock from that repo.. Building RHEL 8 or EPEL 8<br>
> packages requires setting up the relevant "epel-8-x86_64.cfg" to use<br>
> the "best=0" setting, to avoid confusion about the "module" RPMs.<br>
<br>
<br>
Reading this, I wonder if its possible to build the meta information for module <br>
packages out of a rpm list (without additional knowledge)? Similar to createrepo <br>
that works just pointing to a directory. Scenario: pinning a version or incorporating <br>
upstream packages in a local repository. Just curious because that module thing <br>
completely passed me by since I don't use fedora. So, EL8 put the wall in front of me :-)<br>
<br></blockquote><div><br></div><div>There are multiple definitions, filters, controls and other data which are in the modular data file which an rpm list does not have.. much of that data is used in some form. Here is the section for squid from today's in modules.yaml.gz file</div><div><br></div><div><br></div><div>---<br>document: modulemd<br>version: 2<br>data:<br> name: squid<br> stream: 4<br> version: 820181213143653<br> context: 9edba152<br> arch: x86_64<br> summary: Squid - Optimising Web Delivery<br> description: >-<br> an initial version of the squid caching proxy module<br> license:<br> module:<br> - MIT<br> content:<br> - BSD<br> - GPLv2+ and (LGPLv2+ and MIT and BSD and Public Domain)<br> xmd:<br> mbs:<br> mse: TRUE<br> scmurl: git://<a href="http://pkgs.devel.redhat.com/modules/squid?#21e20d36bd79e5a938598ac24dfb9f74b56028ad">pkgs.devel.redhat.com/modules/squid?#21e20d36bd79e5a938598ac24dfb9f74b56028ad</a><br> commit: 21e20d36bd79e5a938598ac24dfb9f74b56028ad<br> buildrequires:<br> platform:<br> stream_collision_modules: <br> stream: el8<br> ref: virtual<br> filtered_rpms: []<br> ursine_rpms: <br> koji_tag: module-rhel-8.0.0-build<br> version: 2<br> context: 00000000<br> rpms:<br> squid:<br> ref: c8510e2ed3af9860df1a961795e47e6070621a18<br> libecap:<br> ref: 1d5fed47e0ff19fa962034645d42bf2e5a2564dc<br> dependencies:<br> - buildrequires:<br> platform: [el8]<br> requires:<br> platform: [el8]<br></div><div> references:<br> documentation: <a href="http://www.squid-cache.org/Doc/">http://www.squid-cache.org/Doc/</a><br> tracker: <a href="https://bugs.squid-cache.org/index.cgi">https://bugs.squid-cache.org/index.cgi</a><br> profiles:<br> common:<br> rpms:<br> - squid<br> api:<br> rpms:<br> - squid<br> components:<br> rpms:<br> libecap:<br> rationale: library needed by Squid<br> repository: git://<a href="http://pkgs.devel.redhat.com/rpms/libecap">pkgs.devel.redhat.com/rpms/libecap</a><br> cache: <a href="http://pkgs.devel.redhat.com/repo/pkgs/libecap">http://pkgs.devel.redhat.com/repo/pkgs/libecap</a><br> ref: stream-1.0<br> buildorder: 1<br> arches: [aarch64, i686, ppc64le, s390x, x86_64]<br> squid:<br> rationale: squid caching proxy<br> repository: git://<a href="http://pkgs.devel.redhat.com/rpms/squid">pkgs.devel.redhat.com/rpms/squid</a><br> cache: <a href="http://pkgs.devel.redhat.com/repo/pkgs/squid">http://pkgs.devel.redhat.com/repo/pkgs/squid</a><br> ref: stream-4<br> buildorder: 2<br> arches: [aarch64, i686, ppc64le, s390x, x86_64]<br> artifacts:<br> rpms:<br> - libecap-0:1.0.1-1.module+el8+2479+dae5d0d3.x86_64<br> - libecap-devel-0:1.0.1-1.module+el8+2479+dae5d0d3.x86_64<br> - squid-7:4.4-4.module+el8+2479+dae5d0d3.x86_64<br>...<br></div><div>---<br>document: modulemd-defaults<br>version: 1<br>data:<br> module: squid<br> stream: 4<br> profiles:<br> 4: [common]<br>...<br></div><div><br></div><div>There may be some other data spread through the file which would be needed for it to use this. This is one of the least complicated ones as it does not have anything which is supposed to tell pungi to filter out packages in the final compose or dependency chains in what it conflicts or requires. Those are very long in text.. so I didn't want to spam email more than I am already with the above.</div><div><br></div><div><br></div><div><br></div><div><br></div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
--<br>
LF<br>
<br>
<br>
_______________________________________________<br>
CentOS-devel mailing list<br>
<a href="mailto:CentOS-devel@centos.org" target="_blank">CentOS-devel@centos.org</a><br>
<a href="https://lists.centos.org/mailman/listinfo/centos-devel" rel="noreferrer" target="_blank">https://lists.centos.org/mailman/listinfo/centos-devel</a><br>
</blockquote></div><br clear="all"><div><br></div>-- <br><div dir="ltr" class="gmail_signature"><div dir="ltr">Stephen J Smoogen.<br><br></div></div></div>