Hi Marc, > I think the reason is that calibre writes files to /usr/lib/calibre on > startup that debian doesn't know about. E.g. in a fresh install:
No, not startup. > and after starting calibre, it creates .pyc files: It is the postinst that does that, calling pycompile. > The original problem is that calibre at one point generated .pyc files > in calibre/regex that dpkg didn't know anything about, and thus dpkg was > unable to remove them. Hmm, but the prerm does remove these files ... so I can only assume that some old version of calibre had a bug, and the files were not removed, but I just tested: dpkg --purge calibre check whether all files are gone (besides the one from calibre-bin) apt-get -t experimental install calibre both .py and .pyc are there I don't know what else could be done? Best Norbert -- PREINING Norbert http://www.preining.info Accelia Inc. + JAIST + TeX Live + Debian Developer GPG: 0x860CDC13 fp: F7D8 A928 26E3 16A1 9FA0 ACF0 6CAC A448 860C DC13
