<!DOCTYPE html><html><head><title></title><style type="text/css">p.MsoNormal,p.MsoNoSpacing{margin:0}</style></head><body><div style="font-size:1.266em;"><br></div><div style="font-size:1.266em;"><br></div><div>On Mon, Mar 10, 2025, at 6:03 PM, Thorsten Alteholz wrote:<br></div><blockquote type="cite" id="qt" style=""><div style="font-size:1.266em;">Hi Jay,<br></div><div style="font-size:1.266em;"><br></div><div style="font-size:1.266em;">On Mon, 10 Mar 2025, Jay Berkenbilt wrote:<br></div><div style="font-size:1.266em;">> I've uploaded qpdf 12.0.0 to debian unstable, which means the packages python3-pikepdf, cups-filters, and r-cran-qpdf will need to relink. There are some breaking changes in qpdf 12, but they are minor and hopefully won't impact any of the above packages. This is just a heads up in case you want to check. I'd like to get this transition through pretty soon so qpdf 12 and libqpdf30 will transition to trixie. Thanks!<br></div><div style="font-size:1.266em;"><br></div><div style="font-size:1.266em;">so you were able to successfully build those three packages?<br></div><div style="font-size:1.266em;"><br></div><div style="font-size:1.266em;"> Thorsten<br></div></blockquote><div style="font-size:1.266em;"><br></div><div style="font-size:1.266em;">I haven't tried. I was going to give it a day and see what the automated systems do. qpdf's CI runs pikepdf's test suite from pikepdf's main, so current pikepdf should work with current qpdf. pikepdf upstream watches qpdf carefully, and we are in regular communication. I haven't checked the others, but they use qpdf in a fairly straightforward way, and the API changes were all in dark corners of qpdf's tokenizer and so forth...not stuff the other packages would be likely to ever have to touch. All API changes were to functions that were deprecated for a long time, so there would be no surprises.<br></div><div style="font-size:1.266em;"><br></div><div style="font-size:1.266em;">I'll keep an eye on things over the next couple of days.</div></body></html>