From: florhizome@posteo.net
To: 63308@debbugs.gnu.org
Subject: bug#63308: [BUG] python-pikepdf build broken
Date: Fri, 05 May 2023 14:39:02 +0000 [thread overview]
Message-ID: <eb308a183f5412a43d8c9b50e5ec5fef29576965.camel@posteo.net> (raw)
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
next reply other threads:[~2023-05-05 14:40 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-05 14:39 florhizome [this message]
2023-08-19 1:59 ` bug#63308: [BUG] python-pikepdf build broken kiasoc5--- via Bug reports for GNU Guix
2023-11-12 4:20 ` Jack Hill
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=eb308a183f5412a43d8c9b50e5ec5fef29576965.camel@posteo.net \
--to=florhizome@posteo.net \
--cc=63308@debbugs.gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.