Thanks, Chris! I did so, but reboot did not create a debugdata dir. Therefore I have uploaded the dnf logs. >From what I have seen so far, it still seems the best option to modify system-upgrade so it safes the transaction before reboot and reboot reruns it ... or something similar. Trying to figure out what obscure dependency constellation this is causing, will be painful and most likely fail, because we do not have enough information and the state of dependencies changes so quickly, the issue might not occur after the next update of those packages. And even if we find this particular one, it might be there are others as well. Is it worth it to start a discussion on devel@ ? ‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐ On Friday, 4. October 2019 20:44, Chris Murphy <lists@xxxxxxxxxxxxxxxxx> wrote: > I suggest trying --debugsolver with both the download and reboot > subcommands. 'man dnf system-upgrade' suggests --debugsolver should > work. I recommend taring the debugdata dir that will create, and > setting the filename and attachment description so it's clear whether > the tarball is for reboot or download. > > The debugdata dir will be located in the current dir. So that'll be > easy to find for the download command. But I have no idea where it'll > be located for reboot so you'll probably have to use find. > > Sometimes these are bigger than the 20MB attachment size, so you might > have to stick it in a dropbox/googledrive like thing and post the URLs > for them in the bug report. > > -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- > > Chris Murphy > > test mailing list -- test@xxxxxxxxxxxxxxxxxxxxxxx > To unsubscribe send an email to test-leave@xxxxxxxxxxxxxxxxxxxxxxx > Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ > List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines > List Archives: https://lists.fedoraproject.org/archives/list/test@xxxxxxxxxxxxxxxxxxxxxxx _______________________________________________ test mailing list -- test@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to test-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/test@xxxxxxxxxxxxxxxxxxxxxxx
