From: Andreas Enge <andreas@enge.fr>
To: Marius Bakke <mbakke@fastmail.com>
Cc: 34531@debbugs.gnu.org
Subject: bug#34531: Guix profile fails on Overdrive 1000
Date: Tue, 19 Feb 2019 09:27:28 +0100 [thread overview]
Message-ID: <20190219082728.GA5650@jurong> (raw)
In-Reply-To: <87mumsom9l.fsf@fastmail.com>
Hello Marius,
thanks a lot for your quick and helpful reply!
On Mon, Feb 18, 2019 at 09:49:10PM +0100, Marius Bakke wrote:
> The Python contained within this Guix snapshot has a known bug that
> makes it leak memory on newer kernels. The Guix commit that works
> around it is 589aca1c183ef1dfdef54d40fdd6a258bbcd39d0.
okay, so the main problem is fixed then.
> One thing you could try is bootstrap a Guix checkout through the usual
> mechanisms (./bootstrap; ./configure; etc), using packages from the host
> system if necessary.
The host system is Guix, so this is complicated... But I realise that
there is also a guix-0.16.0 lying around, and with this I get beyond the
python point.
Before closing the bug, I would still like to ask whether there is a way
of getting around the need for python. And why "guix pull -n" builds
such a large number of packages, while one would expect it to just print
a number of packages to be built. But maybe this is also solved in a
later version already.
Andreas
next prev parent reply other threads:[~2019-02-19 8:28 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-18 20:05 bug#34531: Guix profile fails on Overdrive 1000 Andreas Enge
2019-02-18 20:49 ` Marius Bakke
2019-02-19 8:27 ` Andreas Enge [this message]
2019-02-19 13:23 ` Ricardo Wurmus
2019-02-19 15:19 ` Danny Milosavljevic
2019-02-20 10:51 ` Danny Milosavljevic
2019-02-20 11:46 ` Ricardo Wurmus
2019-02-20 13:26 ` Danny Milosavljevic
2019-02-20 15:56 ` Ricardo Wurmus
2019-02-20 16:26 ` Danny Milosavljevic
2019-02-20 20:53 ` Ricardo Wurmus
2019-02-20 22:08 ` Danny Milosavljevic
2019-02-20 22:28 ` Danny Milosavljevic
2019-02-23 11:20 ` Ricardo Wurmus
2019-02-24 10:40 ` Danny Milosavljevic
2019-02-24 11:45 ` Ricardo Wurmus
2019-02-24 12:12 ` Danny Milosavljevic
2019-02-26 21:07 ` Ricardo Wurmus
2019-02-20 13:28 ` Danny Milosavljevic
2019-02-19 15:35 ` Andreas Enge
2019-02-19 15:40 ` Danny Milosavljevic
2019-04-04 11:28 ` Ludovic Courtès
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=20190219082728.GA5650@jurong \
--to=andreas@enge.fr \
--cc=34531@debbugs.gnu.org \
--cc=mbakke@fastmail.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 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).