Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > linux.debian.bugs.dist > #1280432

Bug#1124657: rust-rusqlite: please upgrade to v0.37

From Peter Michael Green <plugwash@debian.org>
Newsgroups linux.debian.bugs.dist
Subject Bug#1124657: rust-rusqlite: please upgrade to v0.37
Date 2026-02-01 18:00 +0100
Message-ID <MjIXL-eZdv-11@gated-at.bofh.it> (permalink)
References <M9O8q-8c2u-3@gated-at.bofh.it>
Organization linux.* mail to news gateway

Show all headers | View raw


[Multipart message — attachments visible in raw view] - view raw

> Please upgrade crate rusqlite to v0.37.
Based on my preliminary analysis (see below) my feeling is we should go
straight for 0.38, I'll start preparing that soon if noone objects.

preliminary analysis.

libchewing - has no upper limit on the dependency upstream.
meli - uses 0.37 upstream, Debian is downpatching
rust-cargo - upstream git uses 0.38, upstream version in Debian uses 
0.32. No code changes but an extra feature flag was added when updating 
to 0.38.
rust-erbium-core - upstream uses 0.29
rust-hickory-server - upstreaqm uses 0.35
rust-parsec-service - upstream uses 0.29
rust-rustyline - upstream uses 0.37
rust-sequoia-cert-store - upstream allows up to 0.37
rust-sequoia-chameleon-gnupg - upstream allows up to 0.31
rust-sequoia-octopus-librnp - - upstream allows up to 0.31
rust-sequoia-sq - upstream allows up to 0.32
rust-tokio-rusqlite - upstream uses 0.37
settle - upstream uses 0.29

"Breaking changes" from upstream changelog.

0.38

  * Disable u64, usize ToSql/FromSql impl by default #1732
    <https://github.com/rusqlite/rusqlite/pull/1732>, ##1722
    <https://github.com/rusqlite/rusqlite/issues/1722> (breaking change)
  * Make statement cache optional #1682
    <https://github.com/rusqlite/rusqlite/pull/1682>, #1173
    <https://github.com/rusqlite/rusqlite/issues/1173> (breaking change)
  * Bump minimal SQLite version to 3.34.1 #1733
    <https://github.com/rusqlite/rusqlite/pull/1733>, #1731
    <https://github.com/rusqlite/rusqlite/issues/1731> (breaking change)
  * Check Connection is owned when registering Closure as hook #1764
    <https://github.com/rusqlite/rusqlite/pull/1764> (breaking change)

0.37

no breaking changes listed

0.36

no breaking changes listed

0.35

  * Breaking change: Check that Connection::execute has no tail #1679
    <https://github.com/rusqlite/rusqlite/pull/1679> / #397
    <https://github.com/rusqlite/rusqlite/issues/397>
  * Breaking change: Check for multiple statements in prepare #1680
    <https://github.com/rusqlite/rusqlite/pull/1680> / #1147
    <https://github.com/rusqlite/rusqlite/issues/1147>

no breaking changes were listed for versions 0.31 through 0.34

0.30

  * [breaking change] Update edition from 2018 to 2021 #1267
    <https://github.com/rusqlite/rusqlite/pull/1267>


Back to linux.debian.bugs.dist | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread


Thread

Bug#1124657: rust-rusqlite: please upgrade to v0.37 Jonas Smedegaard <dr@jones.dk> - 2026-01-05 09:30 +0100
  Bug#1124657: rust-rusqlite: please upgrade to v0.37 Peter Michael Green <plugwash@debian.org> - 2026-02-01 18:00 +0100
    Bug#1124657: rust-rusqlite: please upgrade to v0.37 Jonas Smedegaard <dr@jones.dk> - 2026-02-01 18:20 +0100
  Bug#1124657: rust-rusqlite: please upgrade to v0.37 Peter Green <plugwash@debian.org> - 2026-04-16 21:50 +0200

csiph-web