bug#63308: closed ([BUG] python-pikepdf build broken)

[GNU bug Tracking System]

Your message dated Sat, 11 Nov 2023 23:20:04 -0500 (EST)
with message-id <0e0a9e77-2508-8e39-74eb-8b817648cd6b@jackhill.us>
and subject line Re: bug#63308: [BUG] python-pikepdf build broken
has caused the debbugs.gnu.org bug report #63308,
regarding [BUG] python-pikepdf build broken
to be marked as done.

(If you believe you have received this mail in error, please contact
help-debbugs@gnu.org.)


-- 
63308: https://debbugs.gnu.org/cgi/bugreport.cgi?bug=63308
GNU Bug Tracking System
Contact help-debbugs@gnu.org with problems
> --- Begin Message ---
>
>
>
> Subject: 
>
> [BUG] python-pikepdf build broken
>
>
>
>
> Date: 
>
> Fri, 05 May 2023 14:39:02 +0000
>
>
>
>
> Hey guix,
> I noticed that python-pikepdf is broken on master, which means
> pdfarranger, a tool I like to use is, too. Updating pikepdf solves the
> build issues, but I had to disable tests and and sanity-checks. And
> then, img2pdf which depends on python-pikepdf and is dependency of
> pdfarranger and pdfarranger still needed modifications. So I wanted to
> pass on the issue.
> Cheers  
>
>
>
> --- End Message ---
> --- Begin Message ---
>
>
>
> Subject: 
>
> Re: bug#63308: [BUG] python-pikepdf build broken
>
>
>
>
> Date: 
>
> Sat, 11 Nov 2023 23:20:04 -0500 (EST)
>
>
>
>
> On Sat, 19 Aug 2023, kiasoc5--- via Bug reports for GNU Guix wrote:
>
> > The build is broken because qpdf in Guix is too old (inferring this from 
> > https://github.com/pikepdf/pikepdf/issues/497#issuecomment-1646312997)
> >
> > Therefore a qpdf upgrade would be required, which would involve a patch to 
> > core-updates.
>
> Some time has passed, and I'm happy to notice that pdfarranger and 
> python-pikepdf are currently working! I'll close this issue.
>
> Thanks!
> Jack
>
>
> --- End Message ---