From: Maxim Cournoyer <maxim.cournoyer@gmail.com>
To: Josselin Poiret <dev@jpoiret.xyz>
Cc: 53258@debbugs.gnu.org, "Ludovic Courtès" <ludo@gnu.org>,
"Marek Felšöci" <marek@felsoci.sk>
Subject: bug#53258: Python unable to find modules within a Singularity container created with guix pack
Date: Thu, 02 Feb 2023 10:40:49 -0500 [thread overview]
Message-ID: <87tu04oz26.fsf@gmail.com> (raw)
In-Reply-To: <87v8kkw2i1.fsf@jpoiret.xyz> (Josselin Poiret's message of "Thu, 02 Feb 2023 15:44:38 +0100")
Hi Josselin,
Josselin Poiret <dev@jpoiret.xyz> writes:
> Hi Ludo,
>
> Ludovic Courtès <ludo@gnu.org> writes:
>
>> Thanks for the investigation and for reporting it upstream!
>>
>> Is there a workaround we could apply locally, ideally one that does not
>> lead to a world rebuild?
>
> So, upstream hasn't replied at all to the above proposal. How do we move
> forward? I have a patch that still applies on Python 3.9.9 that we can
> put into core-updates. Would that be fine?
I haven't revisited that patch, but if you are confident it wouldn't
break anything in the Python world, core-updates would be a fine place,
yes.
--
Thanks,
Maxim
next prev parent reply other threads:[~2023-02-02 15:41 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-14 14:20 bug#53258: Python unable to find modules within a Singularity container created with guix pack Marek Felšöci
2022-01-14 17:45 ` Ludovic Courtès
2022-02-04 20:50 ` Ludovic Courtès
2022-02-05 22:28 ` Josselin Poiret via Bug reports for GNU Guix
2022-02-05 22:30 ` Josselin Poiret via Bug reports for GNU Guix
2022-03-07 8:25 ` Ludovic Courtès
2023-02-02 14:44 ` Josselin Poiret via Bug reports for GNU Guix
2023-02-02 15:40 ` Maxim Cournoyer [this message]
2023-02-06 17:34 ` Simon Tournier
2024-01-04 12:35 ` Konrad Hinsen
2024-01-04 13:01 ` Konrad Hinsen
2024-01-05 15:23 ` Konrad Hinsen
2024-01-21 18:31 ` Maxim Cournoyer
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=87tu04oz26.fsf@gmail.com \
--to=maxim.cournoyer@gmail.com \
--cc=53258@debbugs.gnu.org \
--cc=dev@jpoiret.xyz \
--cc=ludo@gnu.org \
--cc=marek@felsoci.sk \
/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.