reopen 865879
thanks
> affected by this problem seem to be upgrading from an older version.
Ok, slowly light shines through .. thanks
Hmmm, the code that does the purging was introduced in 3.4.0+dfsg-2
and before there was a different code that removed all pyc files on
configure, which was subop
On Thu, May 09, 2019 at 02:02:21PM +0900, Norbert Preining
wrote:
> > Again, the problem in this bug report almost certainly stem from calibre
> > not removing the .pyc files - the .py files were duly removed by dpkg,
>
> But it *removes* the files. I tried it as I wrote. There were .pyc
> files
On Thu, 09 May 2019, Marc Lehmann wrote:
> Again, the problem in this bug report almost certainly stem from calibre
> not removing the .pyc files - the .py files were duly removed by dpkg,
But it *removes* the files. I tried it as I wrote. There were .pyc
files, and after dpkg --purge calbire the
On Thu, May 09, 2019 at 11:45:05AM +0900, Norbert Preining
wrote:
> > to create those files, running calibre as root suffices which is hardly
> > impossible, and is exactly what has happened in this case.
>
> Well, that is something that is not to be expected. And I guess that a
> lot of other p
Hi
On Thu, 09 May 2019, Marc Lehmann wrote:
> I delete them, calibre recreates them.
If you start calibre as root, yes. That is nothing I can do against it.
If you start it as non-root, you don't have write permissions.
I just *tried* it.
> to create those files, running calibre as root suffice
On Thu, May 09, 2019 at 11:24:15AM +0900, Norbert Preining
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
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 proble
> 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? It is in fact impossible, since
nothing in calibre is setuid, so a normal user cannot create files in
/us
After looking at the debian python policy (I don't grok python) this seems
pretty obvlously caused by multiple bugs in calibre, namely that it creates
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 poli
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:
ls -l /usr/lib/calibre/calibre
-rw-r--r-- 1 root root 10072 Feb 8 09:41 constants.py
-rw-r--r-- 1 root root 15317 Feb 8 09:41 debug.py
-rw-r--r--
10 matches
Mail list logo
