unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
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 21:52:45 +0200	[thread overview]
Message-ID: <87muw1cd82.fsf@elephly.net> (raw)
In-Reply-To: <20180611193616.3hnhyx67wsugkm3u@abyayala>


Hi Nils,

> * rust is failing a (tiny?) part of its testsuite:
> […]
> note: Run with `RUST_BACKTRACE=1` for a backtrace.

Have you tried that to see the backtrace?

> * blender, because of imageio:

Here you seem to have elided the actual error message of openimageio.

> * kodi (once again, as usual), because of mysql:

Can kodi use mariadb instead?  (That’s no fix, of course, because mysql
should not fail to build.)  Unfortunately, we don’t see the error
message in what you included here.

> * 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?

--
Ricardo

  reply	other threads:[~2018-06-11 19:53 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 [this message]
2018-06-11 20:01   ` Nils Gillmann
2018-06-11 21:07     ` Ricardo Wurmus
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=87muw1cd82.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).