From: Tanguy LE CARROUR <tanguy@bioneland.org>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: 54036-done@debbugs.gnu.org, maxim.cournoyer@gmail.com
Subject: [bug#54036] [PATCH v5] gnu: gnunet: Update to 0.16.3.
Date: Fri, 01 Apr 2022 18:49:42 +0200 [thread overview]
Message-ID: <164883178226.634.11191733749757072106@localhost> (raw)
In-Reply-To: <87pmm0n667.fsf@gnu.org>
Hi Ludo’,
Quoting Ludovic Courtès (2022-04-01 18:02:08)
> Tanguy Le Carrour <tanguy@bioneland.org> skribis:
>
> > * gnu/packages/gnunet.scm (gnunet): Update to 0.16.3.
> > [arguments]: Enable all the tests that were disabled.
> > [inputs]: Use new style. [native-inputs]: Add openssl.
> > [home-page]: Update URL.
>
> Woohoo! Applied, thanks!
Thanks!
Now, I "just" have to make sure that it works as expected! ^_^'
I might also try to make it build from source instead of
relying on the release archive!?
Cheers,
--
Tanguy
next prev parent reply other threads:[~2022-04-01 16:51 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-17 8:03 [bug#54036] [PATCH] gnu: gnunet: Update to 0.15.3 Tanguy Le Carrour
2022-02-21 21:23 ` Maxim Cournoyer
2022-02-22 11:43 ` Tanguy LE CARROUR
2022-02-22 18:30 ` Maxim Cournoyer
2022-02-28 15:36 ` Tanguy LE CARROUR
2022-03-01 8:05 ` [bug#54036] [PATCH v2] gnu: gnunet: Update to 0.16.0 Tanguy Le Carrour
2022-03-01 19:30 ` Maxim Cournoyer
2022-03-02 16:35 ` [bug#54036] [PATCH v3] " Tanguy Le Carrour
2022-03-06 21:21 ` [bug#54036] [PATCH] gnu: gnunet: Update to 0.15.3 Ludovic Courtès
2022-03-07 13:28 ` Tanguy LE CARROUR
2022-03-21 9:46 ` [bug#54036] [PATCH v4] [WIP] gnu: gnunet: Update to 0.16.2 Tanguy Le Carrour
2022-03-30 8:36 ` [bug#54036] [PATCH v5] gnu: gnunet: Update to 0.16.3 Tanguy Le Carrour
2022-04-01 16:02 ` bug#54036: " Ludovic Courtès
2022-04-01 16:49 ` Tanguy LE CARROUR [this message]
2022-04-04 2:32 ` [bug#54036] " Maxim Cournoyer
2022-04-04 7:00 ` Tanguy LE CARROUR
2022-04-04 13:05 ` Maxim Cournoyer
2022-04-05 7:10 ` Tanguy LE CARROUR
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=164883178226.634.11191733749757072106@localhost \
--to=tanguy@bioneland.org \
--cc=54036-done@debbugs.gnu.org \
--cc=ludo@gnu.org \
--cc=maxim.cournoyer@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.