[prev in list] [next in list] [prev in thread] [next in thread]
List: fedora-devel-list
Subject: Re: Looking up module information via Koji
From: Owen Taylor <otaylor () redhat ! com>
Date: 2018-05-31 19:00:34
Message-ID: CAEJK_diwUBK=pJVuDc-iud4OViAwuffkBtD4fgqfN8ohaUECyA () mail ! gmail ! com
[Download RAW message or body]
[Attachment #2 (multipart/alternative)]
[ Broadening the audience to include devel@lists.fedoraproject.org ]
Anybody have thoughts about my question below? some examples of places
which will need logic like this to replace PDC usage:
ODCS
Resolve a module name:stream to a particular build, and do dependency
expansion
fedmod
Get the flatpak-runtime modulemd to find what packages aren't in the
runtime and need to be bundled
atomic-reactor
Load the modulemd for particular module builds to get profile
information and figure out what to install in a container
flatpak-module-tools
Load modulemd and do dependency expansion to build a container locally
rpkg
Load the modulemd module we are building into a flatpak to find what
runtime it is using, and hence the right build target
Thanks!
Owen
On Mon, May 21, 2018 at 1:29 PM, Owen Taylor <otaylor@redhat.com> wrote:
> My understanding is that with the planned retirement of the PDC:
>
> https://lists.fedoraproject.org/archives/list/infrastructure@lists.
> fedoraproject.org/thread/JHKHWYU5XK7H2P2QZZCCQR4ZRCTY3OSB/
>
> Querying for module information should be done using the MBS and/or Koji
> APIs.
>
> Various code that I maintain (in OSBS, fedmod, and random tooling) wants
> to do module build lookups - different variations of "look up the modulemd
> for latest build of a NAME:STREAM[:VERSION]". Variations generally being
> exactly what "latest" means here.
>
> The code generally already is using Koji and the MBS api is quite limited,
> so I've chosen to do the lookups via Koji.
>
> https://fishsoup.net/misc/get-module-builds
>
> Is a test tool that incorporates most of the capability that I needed
> across my uses. It's distinctly more than a couple of lines of code - I can
> cut-and-paste it for now, but what's the right long-term home? Is there a
> simpler way?
>
> My best idea right now is that if the 'base_version' and'status' part of
> my code was simplified to simply be "tag" and avoid reliance on the tag
> structure of Fedora, then this might make a reasonable addition to the Koji
> CLI and API - there are some things that using raw tags for the query makes
> trickier, but it's probably workable.
>
> Thanks for any input!
> Owen
>
>
[Attachment #5 (text/html)]
<div dir="ltr"><div><div><div><div><div><div>[ Broadening the audience to include <a \
href="mailto:devel@lists.fedoraproject.org">devel@lists.fedoraproject.org</a> \
]<br><br></div>Anybody have thoughts about my question below? some examples of places \
which will need logic like this to replace PDC usage:<br><br></div><div> ODCS<br> \
Resolve a module name:stream to a particular build, and do dependency \
expansion<br></div> fedmod<br></div><div> Get the flatpak-runtime modulemd to \
find what packages aren't in the runtime and need to be bundled<br></div><div> \
atomic-reactor<br></div><div> Load the modulemd for particular module builds to \
get profile information and figure out what to install in a container<br></div><div> \
flatpak-module-tools <br></div><div> Load modulemd and do dependency expansion \
to build a container locally<br></div> rpkg<br></div><div> Load the modulemd \
module we are building into a flatpak to find what runtime it is using, and hence the \
right build target<br> \
<br></div></div>Thanks!<br></div>Owen<br><div><div><div><div><div> \
<br></div></div></div></div></div></div><div class="gmail_extra"><br><div \
class="gmail_quote">On Mon, May 21, 2018 at 1:29 PM, Owen Taylor <span \
dir="ltr"><<a href="mailto:otaylor@redhat.com" \
target="_blank">otaylor@redhat.com</a>></span> wrote:<br><blockquote \
class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc \
solid;padding-left:1ex"><div dir="ltr"><div><div>My understanding is that with the \
planned retirement of the PDC:<br><br> <a \
href="https://lists.fedoraproject.org/archives/list/infrastructure@lists.fedoraproject.org/thread/JHKHWYU5XK7H2P2QZZCCQR4ZRCTY3OSB/" \
target="_blank">https://lists.fedoraproject.<wbr>org/archives/list/<wbr>infrastructure \
@lists.<wbr>fedoraproject.org/thread/<wbr>JHKHWYU5XK7H2P2QZZCCQR4ZRCTY3O<wbr>SB/</a><br><br></div>Querying \
for module information should be done using the MBS and/or Koji \
APIs.<br><br></div><div>Various code that I maintain (in OSBS, fedmod, and random \
tooling) wants to do module build lookups - different variations of "look up \
the modulemd for latest build of a NAME:STREAM[:VERSION]". Variations generally \
being exactly what "latest" means here.<br><br></div><div>The code \
generally already is using Koji and the MBS api is quite limited, so I've chosen \
to do the lookups via Koji. <br><br> <a \
href="https://fishsoup.net/misc/get-module-builds" \
target="_blank">https://fishsoup.net/misc/<wbr>get-module-builds</a><br><br></div><div>Is \
a test tool that incorporates most of the capability that I needed across my uses. \
It's distinctly more than a couple of lines of code - I can cut-and-paste it for \
now, but what's the right long-term home? Is there a simpler \
way?<br><br></div><div>My best idea right now is that if the 'base_version' \
and'status' part of my code was simplified to simply be "tag" and \
avoid reliance on the tag structure of Fedora, then this might make a reasonable \
addition to the Koji CLI and API - there are some things that using raw tags for the \
query makes trickier, but it's probably \
workable.<br></div><div><br></div><div>Thanks for any input!<span \
class="HOEnZb"><font color="#888888"><br></font></span></div><span \
class="HOEnZb"><font color="#888888"><div>Owen<br><br></div></font></span></div> \
</blockquote></div><br></div>
[Attachment #6 (text/plain)]
_______________________________________________
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-leave@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/message/DXJEL6SJZH4XQQBBX7Z3RAX33S6B6OZB/
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic