unofficial mirror of help-guix@gnu.org 
 help / color / mirror / Atom feed
From: Simon Josefsson via <help-guix@gnu.org>
To: brice@waegenei.re
Cc: help-guix@gnu.org
Subject: Re: 'guix reconfigure' fail to build 'rsnapshot'
Date: Sat, 17 Jul 2021 21:04:06 +0200	[thread overview]
Message-ID: <87h7gslq3d.fsf@latte.josefsson.org> (raw)
In-Reply-To: <3987-60f31800-ed-3bd98f40@168269356> (brice@waegenei.re's message of "Sat, 17 Jul 2021 19:49:27 +0200")

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

brice@waegenei.re writes:

> First we go back to our failing build² and have a look in its log⁷. At the
> end of it there is 2 failing tests t/backup_exec/backup_exec.t and
> t/cmd-post_pre-exec/cmd-post_pre-exec.t. That's what we need to repair or
> disable. Now we need to build it locally and inspect it more in depth, we
> do that with “guix build rsnapshot --keep-failed --no-offload” and
> obviously it fail as expected and guix guide us to the build directory
> “/tmp/guix-build-rsnapshot-1.4.4.drv-1”.
>
> To find out why thoses 2 tests ae failing we are gonna run them manually.
> We change directory to
> “/tmp/guix-build-rsnapshot-1.4.4.drv-0/rsnapshot-1.4.4” the failed build
> and find the build “rsnapshot“ program in it but it's not executable, so we
> make it so “chmod +x rsnapshot”. Then we inspect the build tests

Hi Brice.  May thanks for this excellent walk-through, I followed the
steps locally here to learn, hoping my next problem follows the same
pattern.

/Simon

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

  parent reply	other threads:[~2021-07-17 19:04 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-17 16:07 'guix reconfigure' fail to build 'rsnapshot' Simon Josefsson via
2021-07-17 17:49 ` brice
2021-07-17 18:00   ` Tobias Geerinckx-Rice
2021-07-17 19:04   ` Simon Josefsson via [this message]
2021-07-17 17:55 ` Tobias Geerinckx-Rice

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=87h7gslq3d.fsf@latte.josefsson.org \
    --to=help-guix@gnu.org \
    --cc=brice@waegenei.re \
    --cc=simon@josefsson.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).