Is an update log a good idea? Is it possible?

Would if be wonderful if dnf automatically wrote a dnf_update.log that would include all terminal output of most recent update and a dnf_update.log.old that would have the terminal output of the update immediately prior to most recent update?

Is such a thing possible? Reasonable to do?

This way when our wonderful but technically challenged users post the ever inevitable “Updates broke my system” we can then tell the user:

Please file a bug report for this. Please describe accurately and specifically what is broken. Please state the exact problem in the title of the bug report.
Attach dnf_update.log.
Attach omv-bug-report.log.xz

In fact we could then make the above quote one of @rugyada’s wonderful big yellow dialog boxes and just post that every time we see a user post something even remotely like “Update broke my system”.

Post-edit: This would be especially helpful for those users that update with GUI updater or the plasma-pk-updates thingy.

We can track update log from the console in the file: /var/log/dnf.rpm.log

In my case it looks like this:

2019-02-16T02:02:02Z INFO --- logging initialized ---
2019-02-16T02:04:16Z SUBDEBUG Reinstall: quassel-common-0.13.1-1.x86_64
2019-02-16T02:04:17Z SUBDEBUG Reinstall: quassel-common-0.13.1-1.x86_64
2019-02-16T02:04:17Z SUBDEBUG Reinstall: quassel-0.13.1-1.x86_64
2019-02-16T02:04:18Z SUBDEBUG Reinstall: quassel-0.13.1-1.x86_64
2019-02-16T02:04:18Z SUBDEBUG Upgrade: common-licenses-1.1-20.noarch
2019-02-16T02:04:18Z SUBDEBUG Upgrade: common-licenses-1.1-20.noarch
2019-02-16T02:04:18Z SUBDEBUG Upgrade: bootsplash-3.4.2-8.x86_64
2019-02-16T02:04:18Z SUBDEBUG Upgrade: bootsplash-3.4.2-8.x86_64
2019-02-16T02:04:18Z SUBDEBUG Upgrade: qtractor-0.9.5-1.x86_64
2019-02-16T02:04:19Z SUBDEBUG Upgrade: qtractor-0.9.5-1.x86_64
2019-02-16T02:04:19Z SUBDEBUG Reinstalled: quassel-0.13.1-1.x86_64
2019-02-16T02:04:19Z SUBDEBUG Reinstalled: quassel-0.13.1-1.x86_64
2019-02-16T02:04:20Z SUBDEBUG Reinstalled: quassel-common-0.13.1-1.x86_64
2019-02-16T02:04:20Z SUBDEBUG Reinstalled: quassel-common-0.13.1-1.x86_64
2019-02-16T02:04:20Z SUBDEBUG Upgraded: common-licenses-1.1-19.noarch
2019-02-16T02:29:38Z INFO --- logging initialized ---
2019-02-16T02:30:40Z SUBDEBUG Downgrade: grub2-efi-2.02-21.x86_64
2019-02-16T02:30:41Z SUBDEBUG Downgrade: grub2-efi-2.02-21.x86_64
etc...

I started thinking about this in the context of if we are going to be encouraging users to file bug reports for basically all problems we will need to make it easier and less intimidating for tech challenged users to do so.

It looks like the /var/log/dnf.log would have this information and that is already there so nothing to do in that regard.

The /var/log/dnf.rpm.log contains output I don’t understand and don’t know if this would be helpful but my guess is that it would.

So maybe we should make both of these logs part of omv-bug-report.sh unless they already are?

While at it…

alert-updbr

:grin:

1 Like