Received Tue 01 Mar 2005 8:10am +1100 from Karl Schmidt: > Package: wajig > Version: 2.0.22 > Severity: wishlist > > > > -- System Information: > Debian Release: 3.1 > APT prefers testing > APT policy: (600, 'testing') > Architecture: i386 (i686) > Kernel: Linux 2.6.8-2-k7-smp > Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) > > Versions of packages wajig depends on: > ii apt 0.5.28.1 Advanced front-end for dpkg > ii python 2.3.4-5 An interactive high-level > object-o > ii python-apt 0.5.10 Python interface to libapt-pkg > > -- no debconf information > wajig is an excellent program, but there is no way to log what is happening. > The dpkg bug at: > > http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=957 > > Has been open now for 9 years and 269 days and logging may not get added in > my life time... > If wajig could provide this function it would make a lot of people happy. > > All that is needed is to dump a copy of wajig's std out to a log file with a > date stamp on > install, remove, purge, distupgrade, upgrade, fix-xx -- anything that changes > what is installed > > This would be an interim solution, but it is a needed interim solution.
Thanks again for the bug report. I've implemented something! In the end, my simple, but I hope sufficient, approach is to take a snapshot of all the installed packages at the beginning of wajig, and then compare this at the end of wajig and then write to a Log file something like: 2005-03-01T19:43:38.329189 install dia-common 0.94.0-6 2005-03-01T19:43:38.329189 install dia-gnome 0.94.0-6 2005-03-01T19:45:29.534552 remove eject 2.0.13deb-8sarge2 2005-03-01T19:45:56.200279 install eject 2.0.13deb-8sarge2 .... I'll test it for a while. Might play around with some other ideas and new commands to list the log, remove the log, etc. Is this the kind of thing you had in mind - at least for a start! Regards, Graham -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
