[bug#60009] [PATCH 09/18] gnu: sqlite-next: Update to 3.40.0.

[Ricardo Wurmus <rekado@elephly.net>]

zimoun <zimon.toutoune@gmail.com> writes:

> Hi Ricardo,
>
> On Mon, 12 Dec 2022 at 15:27, Ricardo Wurmus <rekado@elephly.net> wrote:
>> * gnu/packages/sqlite.scm (sqlite-next): Update to 3.40.0.
>> ---
>>  gnu/packages/sqlite.scm | 2 +-
>>  1 file changed, 1 insertion(+), 1 deletion(-)
>>
>> diff --git a/gnu/packages/sqlite.scm b/gnu/packages/sqlite.scm
>> index 71cc923a3a..930dc8041d 100644
>> --- a/gnu/packages/sqlite.scm
>> +++ b/gnu/packages/sqlite.scm
>> @@ -7,7 +7,7 @@
>>  ;;; Copyright © 2016 Ben Woodcroft <donttrustben@gmail.com>
>>  ;;; Copyright © 2016 David Craven <david@craven.ch>
>>  ;;; Copyright © 2016, 2017, 2018, 2019, 2020, 2021 Marius Bakke <marius@gnu.org>
>> -;;; Copyright © 2017 Ricardo Wurmus <rekado@elephly.net>
>> +;;; Copyright © 2017, 2022 Ricardo Wurmus <rekado@elephly.net>
>>  ;;; Copyright © 2017 Jelle Licht <jlicht@fsfe.org>
>>  ;;; Copyright © 2018 Tobias Geerinckx-Rice <me@tobias.gr>
>>  ;;; Copyright © 2018 Alex Vong <alexvong1995@gmail.com>
>
> This patch does not seem to update sqlite-next. :-)

Yes, when I rebased on top of commit 50b36f688b43c219dc64a1ce7f6d5e08c0025089
my change disappeared.  That commit did not update python-apsw, which is
sensitive to the version of sqlite-next.

I wish we could express these dependencies as constraints so that people
know what other packages to pay attention to when updating something.

-- 
Ricardo