From: Simon Tournier <zimon.toutoune@gmail.com>
To: "Ludovic Courtès" <ludo@gnu.org>,
"Rostislav Svoboda" <rostislav.svoboda@gmail.com>
Cc: 68333@debbugs.gnu.org
Subject: bug#68333: Time bomb in icedtea/openjdk
Date: Thu, 18 Jan 2024 12:10:40 +0100 [thread overview]
Message-ID: <87h6jaj3rj.fsf@gmail.com> (raw)
In-Reply-To: <87ply9tfxn.fsf@gnu.org>
Hi,
Thanks all for the quick fix.
Well, I am asking here but maybe such discussion would deserve its own
thread on guix-devel. :-)
On mer., 10 janv. 2024 at 15:35, Ludovic Courtès <ludo@gnu.org> wrote:
> Thanks for the quick investigation and patch! I just realized that this
> affects current ‘master’ so we’d rather fix it soon.
>
> What do you think of the attached patch? The difference is that it
> patches code at its root (in the actual source tarball rather than after
> it’s been copied), it does so for IcedTea 7 and 8, and there are patch
> files that are slightly clearer than a substitution pattern.
This fixes the future but not the past. Hum, headache with guix
time-machine? :-)
The question is twofold:
1. Do we document that some Java stack is broken for “guix
time-machine”? Other said, have we an evaluation about which Guix
revisions are broken for the stack of Java?
2. Do we provide a “transformation” for fixing such break? Something
that rewrite on the fly the origin for patching it; accessible only
via manifest.
WDYT?
Cheers,
simon
prev parent reply other threads:[~2024-01-18 11:38 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-07 23:02 bug#68333: Time bomb in icedtea/openjdk Julien Lepiller
2024-01-09 9:51 ` Ludovic Courtès
2024-01-09 11:55 ` Rostislav Svoboda
2024-01-09 21:00 ` Rostislav Svoboda
2024-01-10 14:35 ` Ludovic Courtès
2024-01-10 16:30 ` Ludovic Courtès
2024-01-10 21:00 ` Rostislav Svoboda
2024-01-18 11:10 ` 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=87h6jaj3rj.fsf@gmail.com \
--to=zimon.toutoune@gmail.com \
--cc=68333@debbugs.gnu.org \
--cc=ludo@gnu.org \
--cc=rostislav.svoboda@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).