GNU bug report logs - #69661
[PATCH] gnu: Add redo-apenwarr

Previous Next

Full log

View this message in rfc822 format

From: Skyler Ferris <skyvine <at> protonmail.com>
To: Massimo Zaniboni <mzan <at> dokmelody.org>, 69661 <at> debbugs.gnu.org
Subject: [bug#69661] [PATCH] gnu: Add redo-apenwarr
Date: Fri, 15 Mar 2024 02:19:17 +0000

[Message part 1 (text/plain, inline)]

On 3/12/24 18:52, Skyler Ferris wrote:

>> This is very strange. I have used git commands in build phases before and there was no issue. I was using the same git-fetch origin type. The git folder *should* be there but when I remove the relevant snippet from the build phase and run with --keep-failed it is not. I'll look at this more closely when I have some time.

So, it turns out the reason that it worked for me previously is that I only used `git apply`, which is happy to apply patches even if they are not in a git repository, because the patch file itself has all the information it needs. So I guess this actually is expected.

I don't think that the manual substitution is necessarily a problem. But if you want to avoid it, perhaps using the [tagged release](https://github.com/apenwarr/redo/releases/tag/redo-0.42d) would work better? There is a comment in redo/version/gitvars.do that says that tarballs should have the correct data baked in.

[Message part 2 (text/html, inline)]

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.