From: Simon Tournier <zimon.toutoune@gmail.com>
To: Maxim Cournoyer <maxim.cournoyer@gmail.com>
Cc: 67240-done@debbugs.gnu.org
Subject: bug#67240: dev: “make” of Guix fails, non-existent .git/hooks directory
Date: Tue, 12 Nov 2024 20:20:18 +0100 [thread overview]
Message-ID: <87v7wsb6od.fsf@gmail.com> (raw)
In-Reply-To: <87cyj16idu.fsf@gmail.com>
Hi,
On Tue, 12 Nov 2024 at 16:06, Maxim Cournoyer <maxim.cournoyer@gmail.com> wrote:
>> cp: cannot create regular file '.git/hooks/pre-push': No such file or directory
>> make[2]: *** [Makefile:7454: .git/hooks/pre-push] Error 1
>> make[2]: Leaving directory '/home/simon/src/guix/guix'
>> make[1]: *** [Makefile:6137: all-recursive] Error 1
>> make[1]: Leaving directory '/home/simon/src/guix/guix'
>> make: *** [Makefile:4253: all] Error 2
[...]
>> + mkdir -p .git/hooks; \
>> cp etc/git/pre-push .git/hooks/pre-push; \
>
> If you could come up with a reproducer, I don't mind applying such a
> change, but so far it seems unnecessary?
Bah I barely clone. ;-)
Well, I am not able to reproduce too. Maybe an issue with a clone that
had been completed at once. Anyway.
In all, I think it’s always a good idea to check if the folder
destination exists before copying. It costs almost nothing and it
avoids spurious annoyances, as initially reported.
Cheers,
simon
prev parent reply other threads:[~2024-11-12 19:25 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-17 15:46 bug#67240: dev: “make” of Guix fails, non-existent .git/hooks directory Simon Tournier
2024-11-12 7:06 ` Maxim Cournoyer
2024-11-12 19:20 ` Simon Tournier [this message]
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=87v7wsb6od.fsf@gmail.com \
--to=zimon.toutoune@gmail.com \
--cc=67240-done@debbugs.gnu.org \
--cc=maxim.cournoyer@gmail.com \
/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).