I'd caution you that the list of 'hard to get' packages is ever changing due to both internal and external factors. Certainly none of the EPEL content is safe.
In particular, for StarlingX releases, you'll probably want to snapshot all packages that went into the release. Exactly. Scott, is there currently a record somewhere in the build
On Thu, Jul 26, 2018 at 10:33 AM, Scott Little <scott.little@windriver.com> wrote: tree or ISO of what was actually used? I suppose in the ISO we can just look at the embedded repo, correct? [SL] $MY_WORKSPACE/export/dist/isolinux/Packages/ contains all the
On 18-07-26 11:50 AM, Dean Troyer wrote: packages added to the iso, excluding anything unique to the initrd (just anaconda think). There is no single record of rpms required by to satisfy all the BuildRequires. I'de try a query like this cd $MY_WORKSPACE grep -i 'Installing :' --no-filename */results/jenkins-CGCS_6.0_Host-2018-07-19_11-30-21-tis-r6-pike-std/*/root.log | awk '{ print $5 }' | sort --unique For both queries, some rpms will by unique to StarlingX, or contain release values suggesting it's stx patched.
Related, is there anything currently recorded regarding the branch/commit of the git repos for a particular build? What I think we might want to re-create a specific build might be a re-written repo manifest (default.xml) that includes tags or commit SHAs...
[SL] I do have code to do that in our jenkins build jobs. I can move it into the build scripts if we have a story to cover it.
dt