Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update SQLite3 Multiple Ciphers #26

Open
utelle opened this issue Jun 16, 2024 · 3 comments
Open

Update SQLite3 Multiple Ciphers #26

utelle opened this issue Jun 16, 2024 · 3 comments

Comments

@utelle
Copy link
Contributor

utelle commented Jun 16, 2024

While working on a Python3 wrapper for SQLite3 Multiple Ciphers several bugs/glitches were detected and fixed. Therefore the SQLite3 Multiple Ciphers version used in cb (and SQLitePCL.raw) should be updated to the latest version 1.8.6 (based on SQLite 3.46.0).

I tried to test this update in my cb fork, but the GitHub workflow fails for macOS with an obscure error message (see workflow log).

Unfortunately I don't have much experience with macOS. Could you please have a look to find out how to fix this problem? TIA.

@utelle
Copy link
Contributor Author

utelle commented Jun 17, 2024

GitHub workflow fails for macOS with an obscure error message

Applying the changes from PR #25 seems to solve the problem.

@ericsink
Copy link
Owner

Just acknowledge that I've seen this and I need to catch up. But this is a travel week for me, so I'll continue to be slow.

@utelle
Copy link
Contributor Author

utelle commented Jun 17, 2024

Just acknowledge that I've seen this and I need to catch up. But this is a travel week for me, so I'll continue to be slow.

Thanks for your quick response.

With the workflow modifications mentioned in my previous post the cb build process succeeded without problems. And building the NuGet packages in my own repo worked, too.

So, upgrading SQLitePCL.raw to SQLite3 Multiple Ciphers version 1.8.6 should work in your repository also.

So far I have not received any reports about bugs in the NuGet packages. Therefore it seems that upgrading is not extremely urgent. But IMHO it should be done as soon as you can find the time.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants