Last modified 8 years ago Last modified on 09/16/08 11:04:22


Inasnum wants to create an automated way for testing Fedora packages sanity on a per update basis.

Jan Hutař <jhutar@…>


  • prepare phase - failure terminates test
    • server prepares a job
      • gets new packages list for an pending advisory (e.g. FEDORA-2008-6415 - drupal-6.3-1.fc9) using Bodhi and Koji
      • creates repo_advisory with packages from the advisory (from Koji)
      • creates new_advisory.list file with N E V R A of the packages from the advisory
      • creates new_src_advisory.list file with N E V R A of the source package(s) from the advisory
    • updates repo_update - just mirror of oficial Fedora Updates repo
    • server creates a LVM snapshot where the clinet will be stared
    • client boots up and updates itself from the repo_update repo
  • test phase
    • client queries a job from server, do the test with packages from the repo_advisory repo
      • all new packages installable/updatable?
      • no rpm verification issues or only whitelisted ones?
      • are these packages rebuidable?
      • no file-conflicts?
      • ...
    • report results to the server
  • clean up phase
    • server destroys test system, delete its snapshot partition


To clone your copy of the inasnum git repo, just run:

$ git-clone git://

or you can browse it on inasnum.git.

To push changes to the git use ssh (you have to be in the FAS group gitinasnum):

$ git-remote add fedorahosted ssh://
$ git-push fedorahosted