Hi, Julien BLACHE wrote (Saturday 28 March 2009): > Brendon Higgins <blhigg...@gmail.com> wrote: > > It's like rubbing salt in the wound. Could you *please* check that > > another package, i.e. iscan, doesn't already claim epkowa.conf before > > removing that file, or at least check that iscan isn't installed, first? > > What's the exact package name? Is it just "iscan"?
That's right. > > (Yes, I had to modify the iscan package's control file, removing the > > conflict, to get it to install. I'm sure I'm not the only one.) > > Ah. You should have added a Replaces: libsane-extras, that would have > worked better (iscan effectively taking ownership of the epkowa.conf > conffile in that case). *reads the docs* Whaddaya know. I thought a Replaces was a whole-package thing, but I guess not. > Hopefully we're at the end of the tunnel with this whole mess now, new > packages are mostly ready at Avasys. I haven't really followed the reasons, but it's a shame this mess had to happen. Peace, Brendon
signature.asc
Description: This is a digitally signed message part.
