Bug#1071861: plakativ: prepare for next python3-fitz version

2024-06-28 Thread Johannes Schauer Marin Rodrigues
Quoting Bastian Germann (2024-06-26 19:36:05)
> Control: retitle -1 plakativ: autopkgtest fails with python3-fitz 1.24.x
> Control: severity -1 serious
> 
> Now the pymupdf version has been updated.

Thank you!

Unfortunately, with the changes and the new version I now get a segmentation
fault in the tests:

https://ci.debian.net/packages/p/plakativ/testing/amd64/48338176/

I didn't look into this yet.

signature.asc
Description: signature


Bug#1071861: plakativ: prepare for next python3-fitz version

2024-06-26 Thread Bastian Germann

Control: retitle -1 plakativ: autopkgtest fails with python3-fitz 1.24.x
Control: severity -1 serious

Now the pymupdf version has been updated.



Bug#1071861: plakativ: prepare for next python3-fitz version

2024-05-25 Thread Bastian Germann

Am 25.05.24 um 18:30 schrieb Johannes Schauer Marin Rodrigues:

I found this for context: https://github.com/pymupdf/PyMuPDF/discussions/2680


It is now Stage 2 of the migration, fitz and fitz_old. In Debian, the prerequisites for the rebased "fitz" are not built 
by the mupdf package yet, which is why only fitz_old is available in experimental.


I have already handed in a patch for the other reverse dependency openlp to be 
aware of fitz_old.



Bug#1071861: plakativ: prepare for next python3-fitz version

2024-05-25 Thread Johannes Schauer Marin Rodrigues
Hi,

On Sat, 25 May 2024 16:48:08 +0200 Bastian Germann  wrote:
> python3-fitz's exported module is going to be renamed from fitz to fitz_old
> with the next unstable revision (already in experimental). Please prepare for
> the rename.

I found this for context: https://github.com/pymupdf/PyMuPDF/discussions/2680

According to that document:

> The rebased implementation will behave identically to the classic
> implementation, and will not require any changes to user code.

or:

> You can try the rebased implementation with import fitz_new as fitz (no other
> changes to your code are needed).

or:

> Users of PyMuPDF will be able to carry on using PyMuPDF throughout the
> migration without making any changes to their code.

So I don't understand why I have to rename the import.

Thanks!

cheers, josch

signature.asc
Description: signature


Bug#1071861: plakativ: prepare for next python3-fitz version

2024-05-25 Thread Bastian Germann

Source: plakativ

python3-fitz's exported module is going to be renamed from fitz to fitz_old with the next unstable revision (already in 
experimental). Please prepare for the rename.