From: Tanguy LE CARROUR <tanguy@bioneland.org>
To: Maxim Cournoyer <maxim.cournoyer@gmail.com>
Cc: "Ludovic Courtès" <ludo@gnu.org>, 54036-done@debbugs.gnu.org
Subject: [bug#54036] [PATCH v5] gnu: gnunet: Update to 0.16.3.
Date: Tue, 05 Apr 2022 09:10:50 +0200 [thread overview]
Message-ID: <164914265065.8030.10535363126881025859@localhost> (raw)
In-Reply-To: <87zgl1yp68.fsf@gmail.com>
Hi Maxim,
Quoting Maxim Cournoyer (2022-04-04 15:05:19)
> Tanguy LE CARROUR <tanguy@bioneland.org> writes:
> > Quoting Maxim Cournoyer (2022-04-04 04:32:25)
> >> Tanguy LE CARROUR <tanguy@bioneland.org> writes:
> >> > I might also try to make it build from source instead of
> >> > relying on the release archive!?
> >>
> >> I usually prefer the release archive when it exists and is signed by the
> >> project's maintainer PGP key (which I believe must be the case here,
> >> given it's part of the GNU project).
> >
> > +1!
> >
> > I tried to build from source, but found out that the bootstrap phase was
> > cloning another repo (gana) and copying files over. :-(
>
> Oh! So these source files are probably in the tarball. If gana is a
> 3rd party project we could add as a TODO to un-bundle it (there's no
> 'gana' package in Guix as of now).
Yes, gana lives in another repository: https://git.gnunet.org/gana.git
The bootstrap phase, which is ran prior to building the release archive,
clones it and copy some files over to the gnunet directory
(see <https://git.gnunet.org/gnunet.git/tree/bootstrap#n114>).
I'll try to write a package definition for gana, make it an (native-)input
for gnunet, skip the bootstrap script and see how it goes!
Regards,
--
Tanguy
prev parent reply other threads:[~2022-04-05 7:11 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 ` [bug#54036] " Tanguy LE CARROUR
2022-04-04 2:32 ` 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 [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=164914265065.8030.10535363126881025859@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.