all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: 白い熊@相撲道 <guix-devel_gnu.org@sumou.com>
To: ludo@gnu.org
Cc: guix-devel@gnu.org
Subject: Re: 'core-updates': should we mention Graphviz in "Requirements"?
Date: Thu, 27 Aug 2015 15:47:34 +0200	[thread overview]
Message-ID: <c87eabe527abf0974ea33c8b9838ec39@hcoop.net> (raw)
In-Reply-To: <878u8x2cnc.fsf@gnu.org>

On 2015-08-27 13:28, ludo@gnu.org wrote:
> 白い熊@相撲道 <guix-devel_gnu.org@sumou.com> skribis:
> 
>> ERROR: In procedure scm-error:
>> ERROR: unsupported manifest format #<procedure %manifest-procedure
>> (entries)>
> 
> It seems you’ve been somehow mixing versions, and this error was
> produced by a Guix version older than the one use to upgrade your
> profile, hence the error (and it’s a Guix version older than 0.8.3.)
> 
> Please make sure to use the latest Guix, and you should be fine.

I thought I would not be able to install graphviz from the git pull as I 
ran 'make clean' when it wouldn't build, but alas the git guix still 
installed it, and now the git build is running.

How will I purge the older versions BTW? 'guix gc' doesn't seem to do it 
and this issue - the old version being used - must be due to the fact 
that originally I install GuixSD 0.8.0 but then have been working with 
the git version ever since.
-- 
白い熊@相撲道

  reply	other threads:[~2015-08-27 13:47 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-27  8:28 'core-updates': should we mention Graphviz in "Requirements"? 白い熊@相撲道
2015-08-27  9:10 ` Ludovic Courtès
2015-08-27 10:13   ` 白い熊@相撲道
2015-08-27 11:28     ` Ludovic Courtès
2015-08-27 13:47       ` 白い熊@相撲道 [this message]
2015-08-27 20:51         ` Ludovic Courtès
  -- strict thread matches above, loose matches on Subject: below --
2013-07-09 21:37 Nikita Karetnikov
2013-07-09 21:42 ` 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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=c87eabe527abf0974ea33c8b9838ec39@hcoop.net \
    --to=guix-devel_gnu.org@sumou.com \
    --cc=guix-devel@gnu.org \
    --cc=ludo@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.