Brendon Higgins <blhigg...@gmail.com> wrote: Hi,
> 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"? > (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). Hopefully we're at the end of the tunnel with this whole mess now, new packages are mostly ready at Avasys. JB. -- Julien BLACHE - Debian & GNU/Linux Developer - <jbla...@debian.org> Public key available on <http://www.jblache.org> - KeyID: F5D6 5169 GPG Fingerprint : 935A 79F1 C8B3 3521 FD62 7CC7 CD61 4FD7 F5D6 5169 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
