Hi, Quoting Santiago Vila (2025-04-28 21:18:07) > Version 0.6.1-1 uploaded yesterday builds ok in both my setup and the > official buildds. > > I'm not sure where the bug is/was, but if you consider this to be a bug in > img2pdf, then the bug is fixed in 0.6.1-1.
no, the changelog of my last upload contains a line explaining that I disabled the compilation tests. Reason is that I'm in the middle of figuring out where the problem is and for that it would be good if I could run the img2pdf autopkgtest on debci against imagemagick in unstable but that can only happen after img2pdf compiled successfully and for that I have to temporarily disable the tests. I'm still in the process of bisecting quite a few things. You can see the progress of this in the upstream bug I linked this bug to. I also encountered a new problem as well where new imagemagick creates json with a number formatted as "nan" which python json does not understand (it wants "NaN" it seems). It is not clear where this bug is because it's not clear to attach a "fault" to either. Maybe img2pdf has to learn about "nan" or maybe imagemagick should have to emit "NaN". So still in the middle of debugging this... Thanks! cheers, josch
signature.asc
Description: signature
