unofficial mirror of help-guix@gnu.org 
 help / color / mirror / Atom feed
From: Tomas Volf <~@wolfsden.cz>
To: Peter Polidoro <peter@polidoro.io>
Cc: help-guix@gnu.org
Subject: Re: Unable to make guix master branch for over a week
Date: Wed, 1 May 2024 16:20:30 +0200	[thread overview]
Message-ID: <ZjJPrsXrGbQzFRIt@ws> (raw)
In-Reply-To: <87plu5aai3.fsf@polidoro.io>

[-- Attachment #1: Type: text/plain, Size: 1313 bytes --]

On 2024-05-01 10:10:28 -0400, Peter Polidoro wrote:
> I have been unable to make the guix repository master branch without it
> failing due to errors for maybe a week or more.
>
> I am just curious if the repository occasionally gets into a broken state
> and I just need to wait until some set of commits fixes it eventually

Sometimes (rarely) it does happen.

> or if that means that something is wrong with the particular setup on my
> machine.
>
> I make the guix repository with the command:
> cd ~/guix && git checkout master && git clean -xdf && git checkout . && git
> pull && guix shell -D guix --pure -- sh -c "./bootstrap && ./configure
> --localstatedir=/var && make -j$(nproc)"

Could you perhaps share the error you got?

>
> I am running guix on x86_64 Debian stable as a foreign distro, but running guix shell --pure should keep me isolated well enough from the particulars of my machine correct?
>

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.

Have a nice day,
Tomas Volf

--
There are only two hard things in Computer Science:
cache invalidation, naming things and off-by-one errors.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  reply	other threads:[~2024-05-01 14:21 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 [this message]
2024-05-02 17:02   ` Peter Polidoro
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=ZjJPrsXrGbQzFRIt@ws \
    --to=~@wolfsden.cz \
    --cc=help-guix@gnu.org \
    --cc=peter@polidoro.io \
    /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).