From: "Ludovic Courtès" <ludo@gnu.org>
To: Brendan Tildesley <mail@brendan.scot>
Cc: 43367-done@debbugs.gnu.org
Subject: bug#43367: [core-updates]: [PATCH 0/5]: Prevent wrap-progam from double-wrapping.
Date: Thu, 22 Apr 2021 11:06:01 +0200 [thread overview]
Message-ID: <87im4e1yfa.fsf@gnu.org> (raw)
In-Reply-To: <83311dc4-6e9b-e70b-e379-9993bfcd0554@brendan.scot> (Brendan Tildesley's message of "Sun, 13 Sep 2020 15:39:15 +1000")
Hi Brendan,
Brendan Tildesley <mail@brendan.scot> skribis:
> I'm attempting to fix a bug where wrap-program produces ..X-real-real
> files by mistakenly wrapping already wrapped files. I haven't fully
> tested these because it requires rebuilding everything which takes
> hours to days and core-updates is stuck on mesa now anyway. Perhaps
> I'll try testing on master. Also there may be other places where
> .X-real files are accidentally wrapped, which will now error.
The patch series LGTM and I’ve applied it on ‘core-updates’. I’m
building things now and will push shortly if everything goes well.
Thank you and sorry for the loooong delay!
Ludo’.
prev parent reply other threads:[~2021-04-22 9:08 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-13 5:39 [bug#43367] [core-updates]: [PATCH 0/5]: Prevent wrap-progam from double-wrapping Brendan Tildesley
2020-09-13 5:45 ` [bug#43367] [PATCH 1/5] utils: wrap-program: Refuse to wrap .X-real files Brendan Tildesley
2020-09-13 5:45 ` [bug#43367] [PATCH 2/5] utils: Rename wrapper? to wrapped-program? Brendan Tildesley
2020-09-13 5:45 ` [bug#43367] [PATCH 3/5] glib-or-gtk-build-system: Don't double wrap programs Brendan Tildesley
2020-09-13 5:45 ` [bug#43367] [PATCH 4/5] rakudo-build-system: " Brendan Tildesley
2020-09-13 5:45 ` [bug#43367] [PATCH 5/5] qt-build-system: " Brendan Tildesley
2020-09-13 9:40 ` [bug#43367] [core-updates]: [PATCH 0/5]: Prevent wrap-progam from double-wrapping Danny Milosavljevic
2020-09-13 12:30 ` Brendan Tildesley
2021-04-22 9:06 ` Ludovic Courtès [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=87im4e1yfa.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=43367-done@debbugs.gnu.org \
--cc=mail@brendan.scot \
/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).