From: Giovanni Biscuolo <g@xelera.eu>
To: Gottfried <gottfried@posteo.de>, help-guix@gnu.org
Subject: Re: Frescobaldi manifest can’t be updated
Date: Wed, 17 May 2023 10:55:38 +0200 [thread overview]
Message-ID: <87cz2zjq0l.fsf@xelera.eu> (raw)
In-Reply-To: <9ca2c2c1-8fea-cd1d-cbe2-13f19ccb0e87@posteo.de>
[-- Attachment #1: Type: text/plain, Size: 1431 bytes --]
Hello Gottfried,
Gottfried <gottfried@posteo.de> writes:
> my Lilypond manifest could not be updated. (since weeks)
> Frescobaldi can’t be build. (python-poppler)
> May be somebody know why?
I also tried to build [1] frescobaldi and the build failed, but it was
caused by python-pyportmidi-217 (see bug#63548) and not python-poppler
Nevertheless, also the build of python-poppler-qt5
(/gnu/store/1jv6lwkfqpjy2jqifs3xjpp7xjz6sw7d-python-poppler-qt5-21.1.0.drv)
is failing the same way you are reporting:
[...]
> /gnu/store/pzlvgglsbwjkgn9x25bfgni2836ch3i3-python-sip-4.19.25/bin/sip
> -I /gnu/store/dy3xh053ahkhrp2jamggq8cpsyvp8mg0-python-3.10.7/share/sip
> -t POPPLER_V21_01_0 -x QTXML_AVAILABLE -c
> build/temp.linux-x86_64-cpython-310 -b
> build/temp.linux-x86_64-cpython-310/poppler-qt5.sbf -I
>
> /gnu/store/7a5cx6yzn5i5cvqm5mg0138dyhy2jcgc-python-pyqt-5.15.9/share/sip
> -n PyQt5.sip -t Qt_5_15_8 -t WS_X11 poppler-qt5.sip
> sip: Unable to find file "QtCore/QtCoremod.sip"
>
> error: command
> '/gnu/store/pzlvgglsbwjkgn9x25bfgni2836ch3i3-python-sip-4.19.25/bin/sip'
> failed with exit code 1
>
> error: in phase 'build': uncaught exception:
[...]
so I filed a new bug: #63549
Sorry I'm not able to propose patches for both packages.
HTH! Gio'
[1] "./pre-inst-env guix build frescobaldi" in a Guix checkout
--
Giovanni Biscuolo
Xelera IT Infrastructures
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 849 bytes --]
prev parent reply other threads:[~2023-05-17 8:56 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-12 8:30 Frescobaldi manifest can’t be updated Gottfried
2023-05-17 8:55 ` Giovanni Biscuolo [this message]
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87cz2zjq0l.fsf@xelera.eu \
--to=g@xelera.eu \
--cc=gottfried@posteo.de \
--cc=help-guix@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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).