[Pkg-mailman-hackers] Bug#358575: Purging mailman safely

[Lionel Elie Mamane]

On Thu, May 25, 2006 at 08:37:10AM +0100, Roger Lynn wrote:
> Would replacing (please excuse the line wrap):
> 
>   for file in $(sed -e ':/etc/mailman:!d' -e 's:^[0-9a-f]* *::'
> /var/lib/ucf/hashfile); do
> 
> with
> 
>   for file in $(sed -e '\|^[0-9a-fA-F]\+[[:space:]]\+/etc/mailman/|!d' -e
> 's|^[0-9a-fA-F]\+[[:space:]]\+||' /var/lib/ucf/hashfile); do

sed lines are not the easiest to read when one didn't write them in
the last 5 minutes. Take the line from 2.1.8-1, it is the one I stand
behind.

> in /var/lib/dpkg/info/mailman.postrm (is this the right file?)

That's the right file.

> allow me to safely purge 2.1.7-1 without having to compile and
> install 2.1.8-1 first?

The line from 2.1.8-1 should be OK. You can test what files it will
touch by running the part between $() (without the $()) and looking at
the output. If it does something wrong, please tell me.

> I assume the same would apply to Sarge users.

Yes. Or they can fish 2.1.5-8sarge3 out of the proposed update queue.

-- 
Lionel