all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Maxim Cournoyer <maxim.cournoyer@gmail.com>
To: Hartmut Goebel <h.goebel@crazy-compilers.com>
Cc: help-guix <help-guix@gnu.org>
Subject: Re: Tons of packages get rebuild
Date: Mon, 21 Oct 2019 23:27:29 -0400	[thread overview]
Message-ID: <87y2xde9y6.fsf@gmail.com> (raw)
In-Reply-To: <f5b89397-c7a5-7617-27bd-6288081372a4@crazy-compilers.com> (Hartmut Goebel's message of "Mon, 21 Oct 2019 16:54:26 +0200")

Hello Hartmut,

Hartmut Goebel <h.goebel@crazy-compilers.com> writes:

> Hi,
>
> I'm again experiencing wired behavior on my system: When trying to
> rebuild KDE Framework based on c37c8ef (2019-10-18 20:35:28), tons of
> packages get rebuild, including ruby, llvm-8.0.0, gcc, glibc, openssl,
> mariadb, linux-PAM, etc. Since my computer is not quite fast, this is
> running since Saturday morning already.
>
> Looks like I've  broken my setup.
>
> Daemon is running with
>
> guix-daemon --build-users-group=guixbuild
> --substitute-urls=https://ci.guix.gnu.org
>
> $ /usr/local/sbin/guix-daemon --version
> guix-daemon (GNU Guix) 1.0.1-6.0ed97e6
>
> $ ./pre-inst-env guix --version
> guix (GNU Guix) 1.0.1.3831-dec845   -- which is my branch based on c37c8ef
>
> Building packages with e.g.
>
> $ ./pre-inst-env guix build -K attica
>
> What's wrong here?

I can only think that one of the packages you updated as part of your
work on the KDE Framework must be a dependency of many others (such as
Python, or another core tool)?

Sorry, I don't have other ideas.

Maxim

  reply	other threads:[~2019-10-22  3:27 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-21 14:54 Tons of packages get rebuild Hartmut Goebel
2019-10-22  3:27 ` Maxim Cournoyer [this message]
2019-10-22  7:05   ` Hartmut Goebel
2019-10-23 18:07     ` Marius Bakke
2019-10-24  8:22       ` Hartmut Goebel

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=87y2xde9y6.fsf@gmail.com \
    --to=maxim.cournoyer@gmail.com \
    --cc=h.goebel@crazy-compilers.com \
    --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.
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.