tkopecek
tkopecek
Very briefly, we do a comparison of noarch rpms generated on each architecture and looking for significant differences (rpmdiff -S5TN). Further we're caching hash of this data, to compute it...
What about moving to some github org? E.g https://github.com/fedora-infra or https://github.com/release-engineering/ ?
@clalancette ^ ?
Thank you! It should help a lot, let's see how it will work :-)
@nullr0ute @clalancette any suggestions how to improve this?
Nemá smysl jít přímo po kódech obcí (možná na separátní issue)? Z toho budou přímé vazby na kraje, atd. Navíc je to oficiální výstup csoz, wikidata jsou až sekundární zdroj...
jj, ale spíš jsem to myslel jako reakci na původní problém. Jakože mi přijde zbytečné duplikovat státní open data. Navíc s kódem obce se pak dají dobře párovat státní open...
I've played with current version a bit and what could be confusing is that ``buildroot.lock`` refers to two files: ``$BUILDROOT/buildroot.lock`` which is mock's lock and ``$BUILDROOT/results/buildroot.lock`` which is the json...
About json versioning: Should we also store in the config part which mock version created it? I'm more inclined to "no" as mock probably doesn't have enough information about itself...
Saving whole (parsed) mock config could be valuable? E.g. what if I run the ``--isolated-build`` phase on different machine with different ``site-defaults.cfg``? Maybe it is also up to "process above"...