unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Maxim Cournoyer <maxim.cournoyer@gmail.com>
To: guix-devel@gnu.org
Cc: "Josselin Poiret" <dev@jpoiret.xyz>, "Ludovic Courtès" <ludo@gnu.org>
Subject: Re: 03/08: build: Add dependency on guix script for help2man targets.
Date: Tue, 29 Aug 2023 14:19:21 -0400	[thread overview]
Message-ID: <878r9tbtjq.fsf@gmail.com> (raw)
In-Reply-To: <20230825162837.3C5C1C1D37B@vcs2.savannah.gnu.org> (guix-commits@gnu.org's message of "Fri, 25 Aug 2023 12:28:37 -0400 (EDT)")

Hello,

guix-commits@gnu.org writes:

> jpoiret pushed a commit to branch master
> in repository guix.
>
> commit ca8acad38264dd29a808904d3ce8e7249194d95f
> Author: Josselin Poiret <dev@jpoiret.xyz>
> AuthorDate: Fri May 12 10:00:00 2023 +0200
>
>     build: Add dependency on guix script for help2man targets.
>     
>     * doc/local.mk: Add dependency on guix script for help2man targets.
>     
>     Signed-off-by: Ludovic Courtès <ludo@gnu.org>

This changes appears to break building my tree, like this:

--8<---------------cut here---------------start------------->8---
help2man: can't get `--help' info from guix home
Try `--no-discard-stderr' if option outputs to stderr
make[2]: [Makefile:7131 : doc/guix-home.1] Erreur 1 (ignorée)
--8<---------------cut here---------------end--------------->8---

It doesn't happen with 'make as-derivation' though, so it seems to have
to do with some shenanigan in my checkout.  Any idea how I could fix my
checkout without running 'git clean -xfdd' ?

-- 
Thanks,
Maxim


       reply	other threads:[~2023-08-29 18:21 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <169298091613.3657.8519768348473231009@vcs2.savannah.gnu.org>
     [not found] ` <20230825162837.3C5C1C1D37B@vcs2.savannah.gnu.org>
2023-08-29 18:19   ` Maxim Cournoyer [this message]
2023-09-01  7:51     ` 03/08: build: Add dependency on guix script for help2man targets Josselin Poiret
2023-09-01 11:59       ` Maxim Cournoyer

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=878r9tbtjq.fsf@gmail.com \
    --to=maxim.cournoyer@gmail.com \
    --cc=dev@jpoiret.xyz \
    --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 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).