all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Felix Lechner via "Development of GNU Guix and the GNU System distribution." <guix-devel@gnu.org>
To: Guix Devel <guix-devel@gnu.org>
Subject: Re: qtbase 6.3.2 FTBFS
Date: Mon, 29 May 2023 15:15:30 -0700	[thread overview]
Message-ID: <CAFHYt54Naukc4b_6LPAb02eQYF-KPEriBp+ccFugY+4qF4-2xg@mail.gmail.com> (raw)
In-Reply-To: <CAFHYt54sOdNDFi4oU0r8GG62qojpLNgJTvbGTF=PNMHRhAHL6Q@mail.gmail.com>

Hi,

On Mon, May 29, 2023 at 9:00 AM Felix Lechner
<felix.lechner@lease-up.com> wrote:
>
> qtbase 6.3.2 fails to build from source.

Given the complexity of Guix's branching prerequisites, I should
probably have pointed out that this failure part of Jami:

/ 'check' phasebuilder for
`/gnu/store/02a2bidxyv7kd67ksvypkxnpvwjl3dmh-qtbase-6.3.2.drv' failed
with exit code 1
build of /gnu/store/02a2bidxyv7kd67ksvypkxnpvwjl3dmh-qtbase-6.3.2.drv failed
View build log at
'/var/log/guix/drvs/02/a2bidxyv7kd67ksvypkxnpvwjl3dmh-qtbase-6.3.2.drv.gz'.
cannot build derivation
`/gnu/store/5banm7v4nia9c4qwmyn6c4w1q42x660a-jami-20230323.0.drv': 1
dependencies couldn't be built
guix home: error: build of
`/gnu/store/5banm7v4nia9c4qwmyn6c4w1q42x660a-jami-20230323.0.drv'
failed

Kind regards
Felix


  reply	other threads:[~2023-05-29 22:16 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-29 16:00 qtbase 6.3.2 FTBFS Felix Lechner via Development of GNU Guix and the GNU System distribution.
2023-05-29 22:15 ` Felix Lechner via Development of GNU Guix and the GNU System distribution. [this message]
2023-05-31 18:20   ` Josselin Poiret
2023-06-01  9:53     ` Andreas Enge
2023-06-01 20:17       ` Josselin Poiret
2023-06-02  3:58         ` Felix Lechner via Development of GNU Guix and the GNU System distribution.
2023-06-02  3:45     ` Felix Lechner via Development of GNU Guix and the GNU System distribution.

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=CAFHYt54Naukc4b_6LPAb02eQYF-KPEriBp+ccFugY+4qF4-2xg@mail.gmail.com \
    --to=guix-devel@gnu.org \
    --cc=felix.lechner@lease-up.com \
    /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.