Re: sqlcipher soname change in rawhide

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Fri, Aug 26, 2022, 21:20 Demi Marie Obenour <demiobenour@xxxxxxxxx> wrote:
On 8/26/22 06:12, Fabio Valentini wrote:
> On Fri, Aug 26, 2022 at 3:12 AM Carl George <carl@xxxxxxxxxx> wrote:
>>
>> sqlcipher has been requested to be built in epel9 [0].  Rather than
>> branching it from the current rawhide version, I plan to update
>> rawhide to the latest upstream version first [1].  This involves an
>> soname change from libsqlcipher-3.34.1.so.0 to
>> libsqlcipher-3.39.2.so.0.  This will require six packages to be
>> rebuilt.
>>
>> [root@f38-container:~]# repoquery --repo rawhide-source,rawhide-modular-source \
>>> --quiet --queryformat '%{name}' --archlist src --whatrequires sqlcipher-devel
>> libgda
>> python-peewee
>> sqlitebrowser
>> [root@f38-container:~]# repoquery --repo rawhide-source,rawhide-modular-source \
>>> --quiet --queryformat '%{name}' --archlist src --whatrequires 'pkgconfig(sqlcipher)'
>> kmymoney
>> rust-libsqlite3-sys
>> skrooge
>
> Please do not rebuild rust-libsqlite3-sys. It is a source-only package
> that does not ship any compiled code.
> All packages built from rust-libsqlite3-sys are noarch (i.e. they
> can't - by definition - contain architecture-specific binaries).
> Any built binaries that link against libsqlcipher are only used for
> tests, but not shipped with built packages.

Rust FFI uses the ABI, not the API, so if rust-libsqlite3-sys is based on bindgen
then the generated Rust code will need to be recreated.

Yes, and that happens on-the-fly in the crate's build.rs script, so rebuilding the package has zero effect, because the bindings are *always* generated from headers at build-time, and are not included in the package at all.

Fabio


--
Sincerely,
Demi Marie Obenour (she/her/hers)
_______________________________________________
devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx
Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
_______________________________________________
devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx
Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Fedora Announce]     [Fedora Users]     [Fedora Kernel]     [Fedora Testing]     [Fedora Formulas]     [Fedora PHP Devel]     [Kernel Development]     [Fedora Legacy]     [Fedora Maintainers]     [Fedora Desktop]     [PAM]     [Red Hat Development]     [Gimp]     [Yosemite News]

  Powered by Linux