Description of problem: feature request - [u]RPM[ie] full [,de]installation log Please log all operations somewhere! date,time,version,operation etc. Thanks!
CC: (none) => alien
i think, in urpmi/e syslog logging of: (syslog will add date) urpm(i/e): requested_package repository real_package_file - requested_package is the one which was the reason of getting this package installed - repository is the one where the package was fetched ( or "REMOVE" if the package is removed) - real_package_file is the one that's being installed/removed (then also a filter to put the syslog stuff into a /var/log/urpm.log file that also would be logrotated.)
This log is already available, it can be produced f.ex. with: grep -F [RPM] /var/log/syslog or zgrep -F [RPM] /var/log/syslog* (to search in log which already have been rotated) What is missing would be the repository, and maybe the reason (user-requested/dependency/suggest).
CC: (none) => doktor5000
well, this looks like RPM logs and not urpm logs, while urpm has the repository and dependency info/reason, i doubt rpm has this info...
CC: (none) => dmorganec, thierry.vignaud
This is useless for 99.99% of our users. What you want is basically -v --debug, which is only usefull when debuging. You can set an alias for you.
Priority: Normal => LowStatus: NEW => RESOLVEDResolution: (none) => WONTFIX
Why closing? Alien declared to have a look on it..
"-v --debug" is not what I need, Florian gave the right way to read old logs of installing and deinstalling packages. But Alien has an idea to extend it and I like this idea - it would help managing orphanes, updates.
@tv: yeah, likely, but i don't want output, it's more like an audit log in syslog. for that reason it can be interesting. to examine later on, (even months) how we got to this stage, even if people didn't do -v or whatever...
Status: RESOLVED => REOPENEDResolution: WONTFIX => (none)
And you just can't because people also run "rpm -Uvh", "rpm -e"... and also uses rpm flags such as --nodeps, --force, ... So you'll just never be able to know how they came to this with examining some urpmi log file.
that's a good point...
well, after 12 years reading bug reports such as "I didn't done anything and the systel is unusable", you get used to that dead end :-)
i guess you have your experience going for you... i've been thinking on a better approach, since urpmi knows most of the things, but lower level should be where the logs is at... either i need some way to pass the info down to RPM, or maybe i need to have both of them add entries and still not have double logs... not as easy as i originally thought...
Hi, This bug was filed against cauldron, but we do not have cauldron at the moment. Please report whether this bug is still valid for Mageia 2. Thanks :) Cheers, marja
Keywords: (none) => NEEDINFO
Keywords: NEEDINFO => (none)
i wonder if it's sufficient (for audit purpose) with journalctl, since i would hope it would not delete anything. the most usability of this feature is to determine what the user actually did (and not trust what he says) like, if you accidentally uninstall KDE 2 months ago, that you can find out in your 'audit' logs, that the person uninstalled phonon and didn't read the warning that a whole bunch would also be uninstalled... (or that it was some kind of weird orphan glitch)
Basically it has become easier with journalctl: query package tranasactions since last boot: journalctl -b | grep -F "[RPM]" query all package transactions since journal start (Mageia 3 journalctl doesn't support -b-N syntax) journalctl | grep -F "[RPM]" Just for curiosity, what's happening with this report? IMHO this got worse over the years, first we had a dedicated urpmi log, then this was merged into syslog, and nowadays most people simply don't know how to get hold of this information. rpm -qa --last is also quite unknown ... Couldn't logdrake be extended with a simple package history from that information? That would be least something ...
(In reply to Florian Hubold from comment #14) > Couldn't logdrake be extended with a simple package history from that > information? That would be least something ... Ping?
(In reply to Florian Hubold from comment #14) > Just for curiosity, what's happening with this report? Nothing currently :) > IMHO this got worse over the years, first we had a dedicated urpmi log, then > this was merged into syslog, and nowadays most people simply don't know how > to get hold of this information. rpm -qa --last is also quite unknown ... > > Couldn't logdrake be extended with a simple package history from that > information? That would be least something ... Updating the summary, status comment, and assigning to the Mageia Tools maintainer group. Which does not need it will be done anytime soon, but that's where it belongs now :)
Status comment: (none) => There is a need among users to easily see the past history of rpm installation / upgrade / removals in an easy way. This could be a feature of logdrake, for example.Status: REOPENED => NEWAssignee: bugsquad => mageiatoolsSummary: feature request - [u]RPM[ie] full [,de]installation log => feature request - [u]RPM[ie] full [,de]installation log - in logdrake for exampleSource RPM: rpm => (none)