[Solved] mintupdate -history export
Forum rules
Before you post please read how to get help
Before you post please read how to get help
[Solved] mintupdate -history export
Does anyone know how to export the update history from mintupdate ? [LM19.1 Mate 64]
A search in the obvious places doesn't locate a txt or a log file and mintupdate-cli doesn't seem to have a history option.
I've been using screen grabs, but a txt file would be more useful.
many thanks
Lanser
A search in the obvious places doesn't locate a txt or a log file and mintupdate-cli doesn't seem to have a history option.
I've been using screen grabs, but a txt file would be more useful.
many thanks
Lanser
Last edited by Lanser on Tue Jul 09, 2019 7:15 am, edited 1 time in total.
Thinkpads:- LM19.x Mate, LMDE3, Debian 10
Re: mintupdate -history export
May I ask what you would want that for?
mintupdate parses dpkg's log to generate the history but without knowing what you are trying to achieve I'm not sure that's the best answer to give you.
mintupdate parses dpkg's log to generate the history but without knowing what you are trying to achieve I'm not sure that's the best answer to give you.
Tune up your LM 19.x: ppa:gm10/linuxmint-tools
Re: mintupdate -history export
Sure. The history view provides a detailed list of the individual updated files which I find useful for problem determination.
The primary update descriptions generally only provide a high level description of an update that often includes multiple files.
Occasionally one of these files causes an unexpected problem with HW or another app. Having a list just makes PD a bit easier.
Lanser
The primary update descriptions generally only provide a high level description of an update that often includes multiple files.
Occasionally one of these files causes an unexpected problem with HW or another app. Having a list just makes PD a bit easier.
Lanser
Thinkpads:- LM19.x Mate, LMDE3, Debian 10
Re: mintupdate -history export
No I get that, that's why the history exists, but that still doesn't explain why you'd want to export it/screenshot it, and that's what I was really wondering about.
Tune up your LM 19.x: ppa:gm10/linuxmint-tools
Re: mintupdate -history export
Old habits. When I see updates that are more complex and maybe have implications down track, I document and keep a record for "change control".
Maybe I have been in IT for too long...but it has helped me identify and fix a few issues over the years
Lanser
Maybe I have been in IT for too long...but it has helped me identify and fix a few issues over the years
Lanser
Thinkpads:- LM19.x Mate, LMDE3, Debian 10
Re: mintupdate -history export
Well, the history doesn't go away, but if you want a separate record for your own documentation then the answer I'll give you is:
Code: Select all
zgrep -e " upgrade " -sh /var/log/dpkg.log*
Tune up your LM 19.x: ppa:gm10/linuxmint-tools
Re: mintupdate -history export
Thank you gm10. Perfect. I should have realised that it was "dpkg" action.
Using timeshift snapshots to restore is often the quickest way to fix an update problem, but I learn more if I try to understand the root cause and fix options.
cheers
Lanser
Using timeshift snapshots to restore is often the quickest way to fix an update problem, but I learn more if I try to understand the root cause and fix options.
cheers
Lanser
Thinkpads:- LM19.x Mate, LMDE3, Debian 10