From: Arun Isaac <arunisaac@systemreboot.net>
To: alex@pompo.co
Cc: 27003@debbugs.gnu.org
Subject: bug#27003: [PATCH 0/3] Generalized wrap phase for perl, python.
Date: Tue, 30 May 2017 19:15:49 +0530 [thread overview]
Message-ID: <414919d5.AEMAK2iO_jcAAAAAAAAAAAPFd4YAAAACwQwAAAAAAAW9WABZLXea@mailjet.com> (raw)
In-Reply-To: <87h90322vn.fsf@pompo.co>
> I cannot currently make guarantees on when I'll be able to wrap my head
> around the entire problem, so if you come to conclusions for next steps
> on the basis of your testing, we should go with those.
>
> Else I will revisit this issue when I have time (which might be a
> while).
I don't have any ideas on how to fix this. And, I don't understand Guix
internals very well. So, I'll wait for you or someone else to come up
with a solution. But, I can help with testing patches.
next prev parent reply other threads:[~2017-05-30 13:47 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-20 9:37 bug#27003: [PATCH 0/3] Generalized wrap phase for perl, python Alex Sassmannshausen
2017-05-20 9:40 ` bug#27003: [PATCH 1/3] build/utils: Add 'program-wrapper' Alex Sassmannshausen
2017-05-20 9:40 ` bug#27003: [PATCH 2/3] build/perl-build-system: Add 'wrap' phase Alex Sassmannshausen
2017-05-20 9:40 ` bug#27003: [PATCH 3/3] build/python-build-system: Refactor 'wrap' Alex Sassmannshausen
2017-05-20 20:23 ` bug#27003: [PATCH 0/3] Generalized wrap phase for perl, python Marius Bakke
2017-05-27 19:04 ` Arun Isaac
2017-05-28 19:08 ` Arun Isaac
2017-05-29 13:45 ` Alex Sassmannshausen
2017-05-30 13:45 ` Arun Isaac [this message]
[not found] ` <ef869600.AEMAK2iO_jkAAAAAAAAAAAPFd4cAAAACwQwAAAAAAAW9WABZLXea@mailjet.com>
2017-05-30 15:17 ` Marius Bakke
2020-03-21 14:23 ` Brice Waegeneire
2020-03-21 16:32 ` Ludovic Courtès
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=414919d5.AEMAK2iO_jcAAAAAAAAAAAPFd4YAAAACwQwAAAAAAAW9WABZLXea@mailjet.com \
--to=arunisaac@systemreboot.net \
--cc=27003@debbugs.gnu.org \
--cc=alex@pompo.co \
/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).