Dominic, we took the simplest approach we could figure out during the weekend of importing binary packages into new koji. Our primary goal was to unblock nightly and stable builds. Here are notes for katello 3.4 rhel7 nightly.
* Grab the set of packages in the most recent build (http://34.226.218.207/kojifiles/old_repos/katello-3.4-rhel7-build/latest/x86_64/pkglist) * Create a script to load the packages. I did this via: #cat katello_34_rhel7.txt | sed 's/.*\///' | sed 's/-[^-]*-[^-]*\.[^.]*\.[^.]*$//' | sort > add_packages_katello_34_rhel7.sh * Edit that file, and prepend the following to each line: koji add-pkg --owner kojiadm katello-3.4-rhel7 * Create a script to load the builds. I did this via: #cat katello_34_rhel7.txt | sed 's/.*\///' || sort > add_builds_katello_34_rhel7.sh * Edit the script to remove all the strings ".x86_64.rpm" and ".noarch.rpm" * Edit the script to prepend the following to each line: koji tag-build --nowait katello-3.4-rhel7 * Run the first script, which will add the package mappings * Run the second script, which will ahve some failures due to nested binary rpms. These can be ignored. Rinse and repeat for each repo. ~~~ I haven't noticed builds in multiple (incorrect) tags yet. We will need to look into that. We do have a koji running from backup (summer 2016) with the last tags from 1.12 release, do you think comparing these to the new structure and deleting all extra builds would do the trick? Tags have been recreated from scratch, yes. I don't know what blocked package list is, don't know. We have identified that subpackages are tagged which was not necessary (e.g. -doc packages), we will fix this later but my understanding is that it won't hurt the build process. On TODO. On Tue, Jun 13, 2017 at 10:41 PM, Dominic Cleal <[email protected]> wrote: > On 13/06/17 14:44, Lukas Zapletal wrote: >> >> our koji is back online, it's fresh new instance with foreman [..] > > > Are the builds imported from the existing binaries? > > There appears to be a large issue with many builds that have multiple tags > rather than a single tag that's inherited, which will cause problems with > older packages masking new ones. Can you re-check that builds are only in > one tag per version? > > For example, foreman-1.15.0-1.el7 is in three tags: foreman-1.15, > plugins-1.15-nonscl and plugins-1.15, but should only be in the foreman-1.15 > tag. Ditto for many dependencies, e.g. > http://koji.katello.org/koji/buildinfo?buildID=15059 or > http://koji.katello.org/koji/buildinfo?buildID=15741. > > The tags for 1.14 and 1.13 releases are necessary too for plugin builds. > > Have tags been re-created from scratch? i.e. have blocked package lists etc > been lost? I see lots of very strange packages listed in the tags, e.g. doc > and other sub-binary packages, packages with hyphen suffixes, non-SCL > packages in SCL tags. > > -- > Dominic Cleal > [email protected] > > > -- > You received this message because you are subscribed to the Google Groups > "foreman-dev" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > For more options, visit https://groups.google.com/d/optout. -- Later, Lukas @lzap Zapletal -- You received this message because you are subscribed to the Google Groups "foreman-dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
