all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: "Ludovic Courtès" <ludo@gnu.org>
To: Philip McGrath <philip@philipmcgrath.com>
Cc: 47614@debbugs.gnu.org
Subject: bug#47614: [security] Chunked store references in .zo files in Racket 8
Date: Fri, 16 Apr 2021 17:46:38 +0200	[thread overview]
Message-ID: <87blae44gx.fsf_-_@gnu.org> (raw)
In-Reply-To: <2abc59d0-905e-ab0c-ae25-bf572f34fcd5@philipmcgrath.com> (Philip McGrath's message of "Tue, 6 Apr 2021 21:48:34 -0400")

Hi Philip and all,

Philip McGrath <philip@philipmcgrath.com> skribis:

> Indeed, I expect this is a more precise diagnosis of the same
> problem. My patch in https://issues.guix.gnu.org/47180 solves it by
> putting the store references (search paths for foreign libraries) in a
> configuration data file that isn't compiled, so they don't end up in
> .zo files in the first place.

IIUC, now that <https://issues.guix.gnu.org/47180> has been closed, this
bug is fixed.  Am I right?

Thanks,
Ludo’.




  reply	other threads:[~2021-04-16 15:56 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-07  1:20 Racket 8 and store references (was [security] Chunked store references in .zo files in Racket 8 #47614) Jack Hill
2021-04-07  1:38 ` Philip McGrath
2021-04-07  1:48   ` bug#47614: [security] Chunked store references in .zo files in Racket 8 #47614 Philip McGrath
2021-04-16 15:46     ` Ludovic Courtès [this message]
2021-04-16 19:46       ` bug#47614: [security] Chunked store references in .zo files in Racket 8 Philip McGrath
2021-04-17  9:25       ` Mark H Weaver
  -- strict thread matches above, loose matches on Subject: below --
2021-04-06 11:06 Mark H Weaver
2021-04-06 17:39 ` Léo Le Bouter via Bug reports for GNU Guix
2021-04-06 21:27   ` Mark H Weaver
2021-04-06 22:18     ` Léo Le Bouter via Bug reports for GNU Guix
2021-04-13 21:27       ` Mark H Weaver

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87blae44gx.fsf_-_@gnu.org \
    --to=ludo@gnu.org \
    --cc=47614@debbugs.gnu.org \
    --cc=philip@philipmcgrath.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 external index

	https://git.savannah.gnu.org/cgit/guix.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.