On Thu, 2017-05-18 at 17:48 +0200, Alessio Ciregia wrote: > Let's say that a package was updated. > Such package is involved in the installation process, like for example > anaconda. I'm referring, for instance, to this bug: https://bugzilla.redhat. > com/show_bug.cgi?id=1451754 > > How to test it? We need to wait the next compose that includes such updated > package? Not a silly question at all, but a catch-22 that's been around a long time. I'm trying to get a better system put into place: https://pagure.io/releng/issue/6746 but until then, you have two choices. One option is to boot a live image, update the relevant packages, and then run the installer. The limitation here is that you can't test various workflows that aren't possible in the live installer. The other option is to build your own image to test with. This isn't actually super hard, though you do need somewhere to host a repository via HTTP (unless there's a way to pass a local repo to lorax that I don't know about). Create a repo with the update packages, create a clean working directory and go into it, then run: setenforce Permissive lorax -p Fedora -v 26 -r 26 -s https://kojipkgs.fedoraproject.org/compose/branched/Fedora-26-20170518.n.0/compose/Everything/x86_64/os/ -s https://path/to/your/repo/ ./results/ setenforce Enforcing changing the first URL to the F26 compose you want to base your image off, of course. Let that run a little while and you should get a results/images/boot.iso which is an Everything network install image built with the packages from the side repo. Of course you can just point it at updates-testing as a side repo, but then you get any *other* packages from u-t as well as the ones you want to test. Note that lorax expects the output directory not to exist, so if you re-use the same scratch directory, you have to wipe results/ every time you run it. -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net http://www.happyassassin.net _______________________________________________ test mailing list -- test@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to test-leave@xxxxxxxxxxxxxxxxxxxxxxx
