From: Ashish via Guix-patches via <guix-patches@gnu.org>
To: Thanos Apollo <public@thanosapollo.org>
Cc: 72222@debbugs.gnu.org
Subject: [bug#72222] [PATCH] gnu: Update fossil to 2.25.
Date: Sun, 4 Aug 2024 10:13:46 +0000 [thread overview]
Message-ID: <2wcc2rztx76asijtvt6xhqllhgohjqpzkr57wknjhpmuixazaf@k4lcjuh2mpan> (raw)
In-Reply-To: <87y15c986y.fsf@thanosapollo.org>
[-- Attachment #1: Type: text/plain, Size: 721 bytes --]
On Sun, Aug 04, 2024 at 08:19:01AM +0300, Thanos Apollo wrote:
> Ashish SHUKLA <ashish.is@lostca.se> writes:
>
> > Hi,
> >
> > Just came across your issue report[0], as I updated my issue report[1].
> > If you have a moment, would you like to give it a shot ?
>
> LGTM, but it'd be preferable to use sqlite instead of sqlite-next,
> thus we should update sqlite to the latest version.
Thanks for taking a look.
I believe updating sqlite will trigger a few rebuilds, why is why I
decided to just go for sqlite-next which is already there.
--
Ashish SHUKLA | GPG: F682 CDCC 39DC 0FEA E116 20B6 C746 CFA9 E74F A4B0
"If I destroy you, what business is it of yours ?" (Dark Forest, Liu Cixin)
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 963 bytes --]
prev parent reply other threads:[~2024-08-04 10:16 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-21 6:31 [bug#72222] [PATCH] gnu: Update fossil to 2.25 Thanos Apollo
2024-07-21 7:33 ` [bug#72222] [PATCH 1/2] gnu: Update fossil to 2.23 Thanos Apollo
2024-07-21 7:33 ` [bug#72222] [PATCH 2/2] gnu: Update sqlite to 3.46.0 Thanos Apollo
2024-10-16 17:27 ` bug#72222: [PATCH 1/2] gnu: Update fossil to 2.23 Ludovic Courtès
2024-07-21 7:40 ` [bug#72222] version 2.25 fails to build Thanos Apollo
2024-08-01 22:30 ` [bug#72222] [PATCH] gnu: Update fossil to 2.25 Ashish SHUKLA via Guix-patches via
2024-08-04 5:19 ` Thanos Apollo via Guix-patches via
2024-08-04 10:13 ` Ashish via Guix-patches via [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
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=2wcc2rztx76asijtvt6xhqllhgohjqpzkr57wknjhpmuixazaf@k4lcjuh2mpan \
--to=guix-patches@gnu.org \
--cc=72222@debbugs.gnu.org \
--cc=ashish.is@lostca.se \
--cc=public@thanosapollo.org \
/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).