Page Comparison

...

What are the “Fetch RPM” flow differences between Base OS (prune_packages) & External (yumdownloader) packages?

Jira LegacyserverSystem JIRAcolumnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolutionserverId45e63be1-2551-37a6-b050-86a38172f71dkeyhttps://simp-project.atlassian.net/browse/SIMP-9643

How can we know the URL/path to an RPM’s source repo’s repomd.xml file?

...

source repo’s repomd.xml file?

https://simp-project.atlassian.net/browse/SIMP-9644

This is simple enough to do by hand for an individual package, but I’m not sure how to automate it yet. Here are some ideas:

1. Option 1: see if yumdownloader can be convinced to display the repo root’s URL, like --urls does with the RPM

   

   • (I haven’t found an option that does this)

2. Option 2: walk up the dir tree until we find metadata

   • (hacky, expensive)

3. Option 3: (somehow) find/define the DNF cache that was used to download the RPM and (somehow) fish out the modulemd data that was used for that specific package

4. Status
   colour Green title Current favorite

   Option 4: Do it everything the other way around:

   1. Before getting packages, get a each representative repo’s repomd.xml file first, then use it to find the xxx-packages.yaml.gz

   2. read the modulemd data from the packages.yaml file

   3. filter the modulemd data down to just the streams and packages you need

   4. then run yumdownloader to acquire those exact packages

...