From: Reza Housseini <reza.housseini@gmail.com>
To: Felix Lechner <felix.lechner@lease-up.com>
Cc: guix-devel@gnu.org
Subject: Re: poetry not building
Date: Thu, 22 Jun 2023 22:52:04 +0200 [thread overview]
Message-ID: <48c570b1-f532-42f2-e21c-77ad3d1a2fff@gmail.com> (raw)
In-Reply-To: <CAFHYt57s=1+3-UvGNi_uCMuGLMU90a=FS6cZYuNmUXCv91E++g@mail.gmail.com>
[-- Attachment #1.1.1: Type: text/plain, Size: 1684 bytes --]
Hi Felix
Thanks for your reply.
> I really hope someone responds to you, but in the meantime you could
> set up your own copy of Guix. It's an elegant way to stop begging,
> which I stopped doing because I find it demeaning.
I was not begging only posing a simple question. This is a
misunderstanding on your side.
> More importantly, setting up your own Guix would allow you to test the
> proposed patch set, which is quite large. After some time, you can
> report your experience to the bug. That might provide a measure of
> comfort to anyone who would like to help you but is deterred by the
> fear of making a mistake. Reviewers have lives.
I already tested parts of the patch set, I was never at any point
demanding the reviewers to work on this patch asap.
> As a result, the adoption of the patch set becomes more likely.
>
> An additional benefit is that you could pin your own branch to a
> commit on master that works for you. For example, you could branch off
> of my "prebuilt" branch. [1] It follows "master," but with a delay in
> hope of maximizing substitute availability. I also try to sidestep
> temporary or unresolved quirks like this one [2] which can make it
> impossible to reconfigure your system or your home.
>
> It may be a rational choice depending on your set of personal constraints.
I'm playing with the idea of doing that for a while now, but I fear this
adds another layer of complexity I'm not prepared to handle right now.
Thanks for the suggestion anyway.
Cheers,
Reza
--
Reza Housseini
This message is signed with my GnuPG key:
C0F3 0812 9AF2 80F4 0830 C2C1 C375 C6AF 0512 5C52
[-- Attachment #1.1.2: OpenPGP public key --]
[-- Type: application/pgp-keys, Size: 15557 bytes --]
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2023-06-22 20:52 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <cover.1682660104.git.john.kehayias@protonmail.com>
2023-06-22 7:06 ` poetry not building Reza Housseini
2023-06-22 7:06 ` [bug#63139] " Reza Housseini
2023-06-22 20:28 ` Felix Lechner via Development of GNU Guix and the GNU System distribution.
2023-06-22 20:52 ` Reza Housseini [this message]
2023-06-23 6:49 ` Lars-Dominik Braun
2023-07-31 16:02 ` John Kehayias
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=48c570b1-f532-42f2-e21c-77ad3d1a2fff@gmail.com \
--to=reza.housseini@gmail.com \
--cc=felix.lechner@lease-up.com \
--cc=guix-devel@gnu.org \
/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).