Salsa is updated with version 4.5.5, and an upload heading for
experimental was just submitted for NEW processing due to the SONAME
change. I forgot to close this issue, and suggest it is closed when the
upload to unstable happen.
--
Happy hacking
Petter Reinholdtsen
[Petter Reinholdtsen]
> I have too little experience with maintaining a shared library to feel
> comfortable to do this without further research. Perhaps you can
> help?
This is still the case.
> Perhaps it should go to experimental, or is it better to just move
> directly to 4.5.5? Note,
[Petter Reinholdtsen]
> The sqlcipher package is now orphaned. Daniel, perhaps you can have a
> look at updating it?
I had a look, but discovered that the symbol set in the libsqlcipher0
package has change so much between version 3.4.1 and 4.5.5 that the
build fail. I suspect this mean a soname
The sqlcipher package is now orphaned. Daniel, perhaps you can have a
look at updating it?
--
Happy hacking
Petter Reinholdtsen
I would also like a newer versoin of sqlcipher with encryption support,
as described on
https://www.yoranbrondsema.com/post/the-guide-to-extracting-statistics-from-your-signal-conversations/#2-decrypt-and-convert-the-sqlite-database-to-csv
>.
--
Happy hacking
Petter Reinholdtsen
Control: affects 1017577 + src:rust-libsqlite3-sys librust-libsqlite3-sys-dev
The old version of sqlcipher in debian means that building from the
packaged versions of the rust libsqlite3-dev crate with
"buildtime_bindgen" and "sqlcipher" features active will fail.
--dkg
Source: sqlcipher
Version: 3.4.1-2
Severity: normal
X-Debbugs-Cc: d...@fifthhorseman.net
sqlcipher upstream offers version 4.5.2. debian is pretty far out of
date. I ran into this when packaging and experimenting with the rust
bindings for sqlite3 (package: rust-rusqlite), which include
7 matches
Mail list logo
