Re: Minizip renaming Fedora Change

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

 



I've checked the packaging that should be affected by this change on Fedora Rawhide:
repoquery --whatrequires "*libminizip.so.3*" | pkgname | uniq
R-libSBML
collada-dom
dolphin-emu
dolphin-emu-tool
java-libsbml
keepassxc
libnuml
librasterlite2
libsbml
libspatialite
libxlsxwriter
minizip-devel
perl-LibSBML
python3-libsbml
ruby-SBML
sigil
vxl
xiphos
zfstream

On Thu, Jul 28, 2022 at 11:18 AM Lukas Javorsky <ljavorsk@xxxxxxxxxx> wrote:
Also, the idea is to file Bugs for all packages that BuildRequire/Require the minizip package and let them know about this change and if they should change theirs requirements.

On Thu, Jul 28, 2022 at 10:57 AM Marcus Müller <marcus@xxxxxxxxxxx> wrote:
ah, true, different sonames solves this :)

On 28.07.22 10:52, Daniel P. Berrangé wrote:
> On Thu, Jul 28, 2022 at 10:44:14AM +0200, Marcus Müller wrote:
>> The latter change seems unwise. Packages which now depend on minizip (to be
>> minizip-ng) will continue to do depend on whatever Provides(minizip); if you
>> rename the zlib subpackage to minizip, they will depend on the wrong thing.
> Both these packages merely provide an ELF library. As such anything that
> depends on them should have automatically gained a Requires against the
> SONAME of the contained library - 'libminizip.so.3.0()(64bit)' (for minizip)
> vs 'libminizip.so.1()(64bit)' (for minizip-compat).
>
> As such it shouldn't matter what the actual package name is, any dep will
> continue to resolve to the correct renamed package at install time.
>
> The only significant impact of the rename should be on BuildRequires
> which could end up pulling in the wrong version, but presumably if
> the API is different that ought to resolve in a koji build failure
> which is easy enough to identify and fix the BuildRequires.
>
> With regards,
> Daniel
_______________________________________________
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 on the list, report it: https://pagure.io/fedora-infrastructure


--
S pozdravom/ Best regards

Lukáš Javorský

Software Engineer, Core service - Databases

Red Hat

Purkyňova 115 (TPB-C)

612 00 Brno - Královo Pole

ljavorsk@xxxxxxxxxx



--
S pozdravom/ Best regards

Lukáš Javorský

Software Engineer, Core service - Databases

Red Hat

Purkyňova 115 (TPB-C)

612 00 Brno - Královo Pole

ljavorsk@xxxxxxxxxx

_______________________________________________
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 on the list, report it: https://pagure.io/fedora-infrastructure

[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