unofficial mirror of help-guix@gnu.org 
 help / color / mirror / Atom feed
From: Peter Polidoro <peter@polidoro.io>
To: help-guix@gnu.org
Subject: Re: Unable to make guix master branch for over a week
Date: Thu, 02 May 2024 13:02:06 -0400	[thread overview]
Message-ID: <875xvwdtyj.fsf@polidoro.io> (raw)
In-Reply-To: <ZjJPrsXrGbQzFRIt@ws> (Tomas Volf's message of "Wed, 1 May 2024 16:20:30 +0200")

Tomas Volf <~@wolfsden.cz> writes:
>
> Could you perhaps share the error you got?
>

  DOT      doc/images/service-graph.png
Error: Could not set character size
make[2]: *** [Makefile:7330: doc/images/service-graph.png] Error 1
make[2]: Leaving directory '/home/polidorop/guix'
make[1]: *** [Makefile:6302: all-recursive] Error 1
make[1]: Leaving directory '/home/polidorop/guix'
make: *** [Makefile:4369: all] Error 2

>
> Often yes, however sometimes there are issues due to your Guix being too old
> (since the `shell -D guix' uses package versions from *your* Guix version, not
> from the repository).  However this issue is also somewhat rare.

I always upgrade my guix version right before attempting to make the guix repository.

Perhaps it would be better for me to use a channels file and guix time-machine when making the guix repository? If so, what would be the best commit to use when making the head of the master branch, the previous commit on the master branch? Would it make sense for the guix repository to include a channel file for properly making itself using time-machine for shell -D guix?


  reply	other threads:[~2024-05-02 17:07 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-01 14:10 Unable to make guix master branch for over a week Peter Polidoro
2024-05-01 14:20 ` Tomas Volf
2024-05-02 17:02   ` Peter Polidoro [this message]
2024-05-03  8:43     ` Guillaume Le Vaillant
2024-05-06 13:53       ` Peter Polidoro
2024-05-08  9:24         ` Guillaume Le Vaillant

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=875xvwdtyj.fsf@polidoro.io \
    --to=peter@polidoro.io \
    --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.
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).