From: Maxim Cournoyer <maxim.cournoyer@gmail.com>
To: Jack Hill <jackhill@jackhill.us>
Cc: 61064@debbugs.gnu.org
Subject: [bug#61064] acknowledged by developer (control message for bug #61064)
Date: Fri, 05 Jan 2024 15:13:43 -0500 [thread overview]
Message-ID: <87plyfzgg8.fsf@gmail.com> (raw)
In-Reply-To: <d5d81868-8169-5fbf-b5f4-7565eebcf05c@jackhill.us> (Jack Hill's message of "Fri, 5 Jan 2024 14:20:56 -0500 (EST)")
Hi,
Jack Hill <jackhill@jackhill.us> writes:
> On Fri, 5 Jan 2024, GNU bug Tracking System wrote:
>
>> This is an automatic notification regarding your bug report
>> #61064: [PATCH] gnu: gnutls: Update to 3.7.8.,
>> which was filed against the guix-patches package.
>>
>> Thank you for your report, which has now been closed.
>> You can view the full report at
>> https://debbugs.gnu.org/cgi/bugreport.cgi?bug=61064
>>
>> If you require further information, please followup to 61064@debbugs.gnu.org.
>
> Hi Maxim,
>
> Thanks for taking the time to clean up some old issues. However, Can
> you say a little bit more about what the thinking is on this one? I
> notice that we still have some packages (e.g. dino via
> glib-networking) that are still on gnutls-3.7. Is the idea tha it
> would be better to switch those over to 3.8 than update 3.7?
There's a single gnutls package, which is grafted with 3.8.2. So any
updates to anterior versions are obsolete :-).
--
Thanks,
Maxim
next prev parent reply other threads:[~2024-01-05 20:14 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <87a5pj1wq5.fsf@gmail.com>
2023-01-25 18:55 ` [bug#61064] [PATCH] gnu: gnutls: Update to 3.7.8 Jack Hill
[not found] ` <handler.61064.C.170447798719178.notifdonectrl.0@debbugs.gnu.org>
2024-01-05 19:20 ` [bug#61064] acknowledged by developer (control message for bug #61064) Jack Hill
2024-01-05 20:13 ` Maxim Cournoyer [this message]
2024-01-06 5:38 ` Jack Hill
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=87plyfzgg8.fsf@gmail.com \
--to=maxim.cournoyer@gmail.com \
--cc=61064@debbugs.gnu.org \
--cc=jackhill@jackhill.us \
/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).