[Logcheck-devel] Bug#453519: logcheck-database: amavisd-new file looks like the one shipped by amavisd-new

[Frédéric Brière]

On Fri, Aug 21, 2009 at 12:03:41PM -0700, Russ Allbery wrote:
> Do we have the md5 checksums of the last version that we shipped with the
> package anywhere?

Yes, that can be easily extracted.  I see two issues with this:

First, there's no guarantee that the file will be the last version
shipped.  If a file was included in version X, modified in X+1, and
removed in X+2, it's possible that the user upgraded directly from X to
X+2, and therefore doesn't have the last version of that file.  Checking
for the last version is therefore a "best effort", but not foolproof.

(If we really want to nitpick, if the user copied the file contents from
X+1 manually before upgrading to X+2, Policy might possibly require us
to leave that file alone.)

Second, it's quite possible that the file now belongs to another
package, with the exact same contents as our last version of it.  I
guess that could be avoided by asking dpkg whether it is currently
owned.


Anybody eager to write that mess of a script?  <g>


-- 
*** PUBLIC flooding detected from erikyyy
<lewnie> THAT's an erik, pholx.... ;)
		-- Seen on #LinuxGER