all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: John Kehayias <john.kehayias@protonmail.com>
To: Andreas Enge <andreas@enge.fr>,
	Simon Tournier <zimon.toutoune@gmail.com>,
	David Lecompte <david@metani.eu>
Cc: help-guix@gnu.org, 62956@debbugs.gnu.org
Subject: Re: Fail to update gajim: [PATCH] Updates for python-k5test and python-gssapi
Date: Wed, 26 Apr 2023 21:22:06 +0000	[thread overview]
Message-ID: <87ildi5og6.fsf@protonmail.com> (raw)
In-Reply-To: <87jzxy5p38.fsf@protonmail.com>

> I will send the two patches for the needed updates and then gajim
> builds for me locally (I only built and checked that it ran, though it
> wouldn't open a window in my pure environment at least). I'll attempt
> with the new mumi updates, so it may take a bit for me to get it set
> up.
>

Ah, when sending via mumi it was sent directly to the bug address and
didn't CC anyone else. Please see the patches starting at
<https://issues.guix.gnu.org/62956#6>

> Notes:
>
> 1. For python-k5tests I removed all inputs (guix refresh -u suggested
>    some) and everything built and seemed to work fine for
>    python-gssapi. I'm not familiar with these packages though.
>
> 2. gajim built for me with only the addition of python-idna, but again
>    did not test extensively.
>
> If they look good feel free to push to master (after QA if it sees
> these patches?) or I can later if no complaints.
>
> John



      reply	other threads:[~2023-04-26 21:22 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-20 11:43 Fail to update gajim David Lecompte
2023-04-24  7:19 ` Andreas Enge
2023-04-24  8:51   ` Simon Tournier
2023-04-24  9:52     ` Andreas Enge
2023-04-26 21:08       ` Fail to update gajim: [PATCH] Updates for python-k5test and python-gssapi John Kehayias
2023-04-26 21:22         ` John Kehayias [this message]

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=87ildi5og6.fsf@protonmail.com \
    --to=john.kehayias@protonmail.com \
    --cc=62956@debbugs.gnu.org \
    --cc=andreas@enge.fr \
    --cc=david@metani.eu \
    --cc=help-guix@gnu.org \
    --cc=zimon.toutoune@gmail.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.