From: Ricardo Wurmus <rekado@elephly.net>
To: Nils Gillmann <ng0@n0.is>
Cc: guix-devel@gnu.org
Subject: Re: couple of crashes while guix package -u for (libreoffice, kodi, rust, blender)
Date: Mon, 11 Jun 2018 23:07:44 +0200 [thread overview]
Message-ID: <87lgblc9r3.fsf@elephly.net> (raw)
In-Reply-To: <20180611200109.s7d25o6ddy67z45w@abyayala>
Nils Gillmann <ng0@n0.is> writes:
>> > * libreoffice, because of liborcus:
>> >
>> > checking for MDDS... yes
>> > checking for LIBIXION... no
>> > configure: error: Package requirements (libixion-0.13 >= 0.12.0) were not met:
>> >
>> > No package 'libixion-0.13' found
>> […]
>> > cannot build derivation `/gnu/store/4dlhqln57hbb31a519404a7v563yd35c-libreoffice-5.4.6.2.drv': 1 dependencies couldn't be built
>> > guix package: error: build failed: build of `/gnu/store/4dlhqln57hbb31a519404a7v563yd35c-libreoffice-5.4.6.2.drv' failed
>>
>> I don’t think this is right. I’ve upgraded libreoffice a few days ago
>> to version 6.0.x and this included an upgrade of libixion.
>>
>> Are you sure you’re using the latest version of Guix? If so, do you
>> have GUIX_PACKAGE_PATH set?
>
> Yes, the GPP is set, but my pick for this update of it does not
> include any conflicting package definitions.
>
> I will double check in the next days.
>
> My guix version comes from the normal guix pull,
> version b19950a184a9b7506f9be4ecaa043e5a7e460b52
Something is not right here. This commit is much younger than the
commit that upgraded libreoffice
(54179e2463b554ea0b97e0f73d867332b2bf2cee).
--
Ricardo
next prev parent reply other threads:[~2018-06-12 20:54 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-11 19:36 couple of crashes while guix package -u for (libreoffice, kodi, rust, blender) Nils Gillmann
2018-06-11 19:52 ` Ricardo Wurmus
2018-06-11 20:01 ` Nils Gillmann
2018-06-11 21:07 ` Ricardo Wurmus [this message]
2018-06-12 6:22 ` Nils Gillmann
2018-06-11 21:25 ` Tobias Geerinckx-Rice
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=87lgblc9r3.fsf@elephly.net \
--to=rekado@elephly.net \
--cc=guix-devel@gnu.org \
--cc=ng0@n0.is \
/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 public inbox
https://git.savannah.gnu.org/cgit/guix.git
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).