On Thu, May 09, 2019 at 11:24:15AM +0900, Norbert Preining
<norb...@preining.info> wrote:
> > the .pyc files on first start rather than in post-install (as per policy)
> > and
> > doesn't remove the files in the pre-remove script (as required by policy).
>
> How do you come to this assumption?
I delete them, calibre recreates them. I also looked at the regex problem,
and the regex/ in an "old" backup from debian stable (stretch) looks like
this:
# ls -l regex/
total 160
-rw-r--r-- 1 root root 27153 May 30 2017 __init__.pyc
-rw-r--r-- 1 root root 134212 May 30 2017 _regex_core.pyc
So pre-remove didn't remove them, otherwise they would be gone (calibre
never having been installed outside of debian).
If this was indeed a bug in an older version, then this might indeed
be fixed by now, and the timestamps might indicate which version is
responsible (most likely the one from stretch, but I don't know the exact
history of this users machine).
> It is in fact impossible, since nothing in calibre is setuid, so a
> normal user cannot create files in /usr/lib/calibre.
Don't be so quick with "impossible" - calibre doesn't have to be setuid
to create those files, running calibre as root suffices which is hardly
impossible, and is exactly what has happened in this case.
--
The choice of a Deliantra, the free code+content MORPG
-----==- _GNU_ http://www.deliantra.net
----==-- _ generation
---==---(_)__ __ ____ __ Marc Lehmann
--==---/ / _ \/ // /\ \/ / schm...@schmorp.de
-=====/_/_//_/\_,_/ /_/\_\
