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

Groups > linux.debian.bugs.dist > #1174268 > unrolled thread

Bug#1017577: sqlcipher: new upstream version available

Back to article view | Back to linux.debian.bugs.dist

This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by below is the oldest one visible, not the original post.

Contents

  Bug#1017577: sqlcipher: new upstream version available Petter Reinholdtsen <pere@hungry.com> - 2023-11-08 12:40 +0100
    Bug#1017577: sqlcipher: new upstream version available Petter Reinholdtsen <pere@hungry.com> - 2023-11-08 18:10 +0100
      Bug#1017577: sqlcipher: new upstream version available Petter Reinholdtsen <pere@hungry.com> - 2023-11-09 12:30 +0100
        Bug#1017577: sqlcipher: new upstream version available Petter Reinholdtsen <pere@hungry.com> - 2023-11-09 15:30 +0100

#1174268 — Bug#1017577: sqlcipher: new upstream version available

The sqlcipher package is now orphaned.  Daniel, perhaps you can have a
look at updating it?

-- 
Happy hacking
Petter Reinholdtsen

[toc] | [next] | [standalone]

#1174298

[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 transition is needed.  I have
too little experience with maintaining a shared library to feel
comfortable to do this without further research.  Perhaps you can help?

I upgraded to version 3.4.2 in git, and this did not break the build.  A
small set of symbols were added to the library, and I updated
debian/libsqlcipher0.symbols with the list.  Not sure if any of them
should be optional, so I have not uploaded this new version yet.
Perhaps it should go to experimental, or is it better to just move
directly to 4.5.5?  Note, several of the patches did not apply in 4.5.5,
so that will require some investigation too.

On the positive side, I tested a non-Debian build of 4.5.5 and was able
to read messages from the encrypted Signal database, so I now know a
newer version will solve my problem.

-- 
Happy hacking
Petter Reinholdtsen

[toc] | [prev] | [next] | [standalone]

#1174363

[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, several of the patches did not apply in
> 4.5.5, so that will require some investigation too.

I decided to give this a go, and is almost ready to push migration to
version 4.5.5 to salsa.  It will happen this evening.

I believe it is best to move directly to 4.5.5, change the SONAME and
upload to experimental.  Uploading to unstable might need some
coordination with the reverse build dependencies.

Sadly upstream do not so far care about SONAME and backwards
compatibility, so we will have to pick SONAME on our own.

-- 
Happy hacking
Petter Reinholdtsen

[toc] | [prev] | [next] | [standalone]

#1174378

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

[toc] | [prev] | [standalone]

Back to top | Article view | linux.debian.bugs.dist

csiph-web