#201: Add mash support to depcheck ---------------------+------------------------------------------------------ Reporter: wwoods | Owner: jskladan Type: task | Status: assigned Priority: major | Milestone: Package Update Acceptance Test Plan - depcheck Component: tests | Version: 1.0 Resolution: | Keywords: ---------------------+------------------------------------------------------ Comment (by wwoods):
So, what do we expect mash to do for us? I've seen some "solve_multilib"
routine inside the sources, so i guess that might be it, but it also seems to be working over the currently created repo.
Right. The way I understand it, mash works kind of like createrepo except it takes a tag as input and - more importantly - does the multilib-solving magic.
In short: {{{ createrepo: packages -> repodata mash: tag -> package list -> multilib solving -> repodata }}} Originally I talked to the rel-eng team about having a koji tag for "packages in bodhi that have requested push to {stable,testing}". Then we could run mash against that. And I'm pretty sure jkeating created some tags for this purpose.
But they also said we would need to run mash ourselves (i.e. on the autoqa systems) since it was too much strain to make koji/bodhi run mash for us. Furthermore, bodhi is not maintaining any "proposed-update" tags for us to use, so either: a. we figure out a way to run mash without a tag (e.g. using a list of build names instead), a. we update bodhi to maintain some special koji tags for us, a. we maintain the tags ourselves (e.g. in the watcher), or a. we roll our own code to generate repodata from a list of packages, and use Mash's 'solve_multilib' to make sure we ge get the full (multilib) set of packages.