--- Begin Message ---
Subject: |
[PATCH 0/1] Update sqlite-next (3.42.0) and python-apsw (3.42.0.1). |
Date: |
Thu, 27 Jul 2023 22:34:48 +0800 |
Hello Guix!
This patch updates sqlite-next and python-apsw. They are put together since
the old python-apsw won't compile with the new sqlite-next.
Thanks
Hilton Chain (1):
gnu: python-apsw: Update to 3.42.0.1.
gnu/packages/databases.scm | 6 +++---
gnu/packages/sqlite.scm | 4 ++--
2 files changed, 5 insertions(+), 5 deletions(-)
base-commit: c7e45139faa27b60f2c7d0a4bc140f9793d97d47
--
2.41.0
--- End Message ---
--- Begin Message ---
Subject: |
Re: [bug#64899] [PATCH 1/1] gnu: python-apsw: Update to 3.42.0.1. |
Date: |
Tue, 12 Sep 2023 08:47:40 +0100 |
User-agent: |
mu4e 1.10.5; emacs 28.2 |
Hilton Chain via Guix-patches via <guix-patches@gnu.org> writes:
> * gnu/packages/databases.scm (python-apsw): Update to 3.42.0.1.
> * gnu/packages/sqlite.scm (sqlite-next): Update to 3.42.0.
> ---
> gnu/packages/databases.scm | 6 +++---
> gnu/packages/sqlite.scm | 4 ++--
> 2 files changed, 5 insertions(+), 5 deletions(-)
Personally I think we can't go down the route of trying to group changes
in to single commits to avoid breaking packages, as that would cause too
many problems for more complex changes.
Therefore, I've gone ahead and split this commit in two and pushed it to
master as d6ad06cd6c9d96735aea5fe98c7dbf27adec25db.
Thanks,
Chris
signature.asc
Description: PGP signature
--- End Message ---