On Wed, May 28, 2014 at 10:21:28AM +0200, Mark Clarke wrote: > On 28/05/2014 09:08, Florian Ernst wrote: > > Furthermore, your atop package would need severe polishing, as at > > the moment it doesn't adress any of the update issues that will > > arise (and which led Marc to not yet package any release breaking > > compatibility). You might want to add your experiences to #729614, > > though (atop: Please package latest upstream version (2.0.2)). > > > Where can I find out what the issues are with atop that you mention? I > want to use this as a learning exercise to compare with my effort. I > have visited bug #729614 but it doesn't mention anything there as far > as I can tell. http://www.atoptool.nl/downloadatop.php : | Version 1.27-3: | [...] | General: The format of the raw file is incompatible with earlier | versions. However, the earlier version of atop is automatically | activated when accessing an older raw file. This means a newer atop can't read the raw files created by an older atop, ie. older atop logs become inaccessible. Upstream's workaround is to let atop automatically call atop-1.26 when reading older logs, but this doesn't work well with Debian as it would require keeping the older binary around. Other packages confronted by a comparable problem, e.g. sysstat, have decided to simply throw old logs away on such an incompatible change. I, for one, would welcome not to rely on this "solution", though ... BTW, I need to correct my statement from above, 1.27-3 has already been packaged, but only in experimental. Cheers, Flo
Attachment:
signature.asc
Description: Digital signature