From: Pierre Langlois <pierre.langlois@gmx.com>
To: John Kehayias <john.kehayias@protonmail.com>
Cc: guix-devel@gnu.org, Andreas Enge <andreas@enge.fr>,
Pierre Langlois <pierre.langlois@gmx.com>
Subject: Re: Core-updates merge
Date: Fri, 14 Jul 2023 19:12:25 +0100 [thread overview]
Message-ID: <87y1jibbmv.fsf@gmx.com> (raw)
In-Reply-To: <87edla1md1.fsf@protonmail.com>
[-- Attachment #1: Type: text/plain, Size: 1580 bytes --]
Hi John!
John Kehayias <john.kehayias@protonmail.com> writes:
> Bringing back up an old thread, but
>
> On Fri, Apr 28, 2023 at 05:55 AM, John Kehayias wrote:
>
>> Dear Andreas and fellow Guix-ers,
>>
>> On Tue, Apr 25, 2023 at 04:09 PM, Andreas Enge wrote:
>>
> [...]
>>> Each and every package is not yet in shape; please feel free to submit
>>> patches for your favourite packages that fail to build. In particular:
>>> - python-yubikey-manager does not build currently; work to correct this
>>> is underway.
>>
>> I've just submitted <https://issues.guix.gnu.org/63139> which does a bit
>> more than just fix that package and would be good for a Python feature
>> branch. I'll send the cover letter to this list for wider visibility,
>> though the Python team was cc'ed on the series. I suppose I should add
>> myself to the team after this.
>>
>
> Thanks to Pierre Langlois python-yubikey should now finally be fixed
> on master, without all the big python build changes. (Poetry is still
> broken.) This was via <https://issues.guix.gnu.org/63354>. Unfortunately
> I managed to clobber the author line in the git log after editing and
> testing locally, sorry about that! (Anything that can be done to fix
> that?)
Thank you for picking up the series! I admit I had forgotten I had sent
it, I don't have too much time for Guix these days I'm afraid.
Attribution is always nice of course, but mistakes happen, especially
with git, so I wouln't worry about it in this instance! At least
personnally I don't mind :-), just happy that the patches went in.
Thanks,
Pierre
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 519 bytes --]
next prev parent reply other threads:[~2023-07-14 18:19 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-14 16:36 Core-updates merge John Kehayias
2023-07-14 16:52 ` Felix Lechner via Development of GNU Guix and the GNU System distribution.
2023-07-14 21:26 ` John Kehayias
2023-07-14 18:12 ` Pierre Langlois [this message]
2023-07-14 21:31 ` John Kehayias
2023-07-14 21:37 ` Felix Lechner via Development of GNU Guix and the GNU System distribution.
-- strict thread matches above, loose matches on Subject: below --
2023-04-25 14:09 Andreas Enge
2023-04-25 14:40 ` Felix Lechner via Development of GNU Guix and the GNU System distribution.
2023-04-25 14:57 ` Katherine Cox-Buday
2023-04-25 19:27 ` Maxim Cournoyer
2023-04-25 15:31 ` Josselin Poiret
2023-04-25 16:09 ` Leo Famulari
2023-05-03 21:07 ` Ludovic Courtès
2023-04-28 5:55 ` John Kehayias
2023-04-28 14:17 ` Simon Tournier
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=87y1jibbmv.fsf@gmx.com \
--to=pierre.langlois@gmx.com \
--cc=andreas@enge.fr \
--cc=guix-devel@gnu.org \
--cc=john.kehayias@protonmail.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).