> > 2. Ask Anaconda team to provide us with their "official" and > > supported solution. > > > > After inspecting updates.img, there is a lot of code copied from > > (some old version of) anaconda. That doesn't seem to me as a good > > solution, because we might get completely unrelated problems in the > > process. I imagine anaconda guys could provide us with a much > > better > > solution. For example they could add "traceback" kernel option that > > causes anaconda crash on startup. This is just a few lines of code, > > it would be maintained, and doesn't involve any updates.img > > downloading etc. What do you think? I'll discuss with anaconda team > > if noone has better ideas. > > I consulted this idea with Vratislav Podzimek from Anaconda team. He > agreed this could be implemented, especially because we're not alone > asking for it. He'll try to get this feature into anaconda very soon > so that we can test it. The new feature is implemented and should be part of the next anaconda release (17.9 probably). We just use 'traceback' boot option. Once a new compose with the new anaconda is ready, I'll re-write the test cases. -- test mailing list test@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
