GNU bug report logs - #63308
[BUG] python-pikepdf build broken

Previous Next

Package: guix;

Reported by: florhizome <at> posteo.net

Date: Fri, 5 May 2023 14:40:02 UTC

Severity: normal

Done: Jack Hill <jackhill <at> jackhill.us>

Bug is archived. No further changes may be made.

To add a comment to this bug, you must first unarchive it, by sending
a message to control AT debbugs.gnu.org, with unarchive 63308 in the body.
You can then email your comments to 63308 AT debbugs.gnu.org in the normal way.

Toggle the display of automated, internal messages from the tracker.

View this report as an mbox folder, status mbox, maintainer mbox

Report forwarded to bug-guix <at> gnu.org:
bug#63308; Package guix. (Fri, 05 May 2023 14:40:02 GMT) Full text and rfc822 format available.
Acknowledgement sent to florhizome <at> posteo.net:
New bug report received and forwarded. Copy sent to bug-guix <at> gnu.org. (Fri, 05 May 2023 14:40:02 GMT) Full text and rfc822 format available.

Message #5 received at submit <at> debbugs.gnu.org (full text, mbox):

From: florhizome <at> posteo.net
To: bug-guix <at> gnu.org
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
Information forwarded to bug-guix <at> gnu.org:
bug#63308; Package guix. (Sat, 19 Aug 2023 02:00:01 GMT) Full text and rfc822 format available.

Message #8 received at 63308 <at> debbugs.gnu.org (full text, mbox):

From: kiasoc5 <at> disroot.org
To: 63308 <at> debbugs.gnu.org
Subject: Re: [BUG] python-pikepdf build broken
Date: Sat, 19 Aug 2023 03:59:06 +0200

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.
Reply sent to Jack Hill <jackhill <at> jackhill.us>:
You have taken responsibility. (Sun, 12 Nov 2023 04:21:01 GMT) Full text and rfc822 format available.
Notification sent to florhizome <at> posteo.net:
bug acknowledged by developer. (Sun, 12 Nov 2023 04:21:01 GMT) Full text and rfc822 format available.

Message #13 received at 63308-done <at> debbugs.gnu.org (full text, mbox):

From: Jack Hill <jackhill <at> jackhill.us>
To: kiasoc5 <at> disroot.org
Cc: 63308-done <at> debbugs.gnu.org
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
bug archived. Request was from Debbugs Internal Request <help-debbugs <at> gnu.org> to internal_control <at> debbugs.gnu.org. (Sun, 10 Dec 2023 12:24:05 GMT) Full text and rfc822 format available.
This bug report was last modified 136 days ago.

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.