When you try to rebuild the same commit in version control with 'mbs-build local', things can go pretty wrong, due to the combination of the following:
So createrepo_c during the rebuild finds some random selection of rpms from the last build in <tagname>/results/Thread-<N> directories, which may then be deleted while builds that use the repodata are running.
It seems to me that three things should be done:
When reusing the same build directory, the old directory should simply be deleted with all contents. I see no virtue in having a build directory which has a mix of old and new log files. Possibly one old build directory could be saved verbatim as builds/<tagname>.old/, but I'm not sure this is useful.
createrepo_c needs to be run only on the rpms directly in <tagname>/results. I think this means creating a temporary package list to pass to createrepo_c --pkglist
It probably would be better to move, not copy, the files from the thread results directory to the main results directory to save IO and disk space.
@otaylor, are the issues outlined here still a problem?
flatpak-module-tools always uses a new version ,and hence a new build directory, so we're not hitting these issues, but I don't know of any fixes - I suspect they still happen.
Login to comment on this ticket.