and, what am I missing in my queries that fails to show why/where it's dependency-tied to ~ 3.2G of pkg?
You did not look at the package provides. On an F39 system:
thx; indeed:
rpm -q --whatrequires 'libpcre.so.1()(64bit)'
pcre-8.45-1.fc40.6.x86_64
sord-0.16.14-3.fc40.x86_64
pcre-cpp-8.45-1.fc40.6.x86_64
in any case,
dnf remove sord
...
Transaction Summary
================================================================================================================
Remove 331 Packages
Freed space: 3.2 G
1st, i had no recollection of what 'sord' is, or why I need it. reading @ https://src.fedoraproject.org/rpms/sord
"sord is a lightweight C library for storing Resource Description
Framework (RDF) data in memory. sord and parent library serd form
a lightweight RDF tool-set for resource limited or performance critical
applications. (upstream)"
which refs
-> https://drobilla.net/software/sord.html
-> https://gitlab.com/drobilla/sord
i understand that
> sord provides a library required by lilv-libs, which provides a library
> required by ffmpeg-libs and gstreamer1-plugins-bad-free, which then
> takes out an escalating stack of things.
re-digging @
https://fedoraproject.org/wiki/Changes/PcreDeprecation#Current_status
takes me back to
https://bugzilla.redhat.com/show_bug.cgi?id=2127507#c3
where i read my own, forgotten question. which then mentions 'sord'. sigh.
that a single pkg can muck up dependencies in pkg mgmt like this can't -- well, shouldn't -- still be an acceptable state of affairs.
note that at the F40 sord pkg build,
Version: 0.16.14
where
ldd `rpm -ql sord | grep bin`
/usr/bin/sord_validate:
linux-vdso.so.1 (0x00007fdcd6d8e000)
libsord-0.so.0 => /lib64/libsord-0.so.0 (0x00007fdcd6d53000)
libserd-0.so.0 => /lib64/libserd-0.so.0 (0x00007fdcd6d3b000)
libpcre.so.1 => /lib64/libpcre.so.1 (0x00007fdcd6cbf000)
libc.so.6 => /lib64/libc.so.6 (0x00007fdcd6ad2000)
libm.so.6 => /lib64/libm.so.6 (0x00007fdcd69ef000)
/lib64/ld-linux-x86-64.so.2 (0x00007fdcd6d90000)
/usr/bin/sordi:
linux-vdso.so.1 (0x00007fbc72402000)
libsord-0.so.0 => /lib64/libsord-0.so.0 (0x00007fbc723cb000)
libserd-0.so.0 => /lib64/libserd-0.so.0 (0x00007fbc723b3000)
libc.so.6 => /lib64/libc.so.6 (0x00007fbc721c6000)
libm.so.6 => /lib64/libm.so.6 (0x00007fbc720e3000)
/lib64/ld-linux-x86-64.so.2 (0x00007fbc72404000)
checking @ upstream
https://gitlab.com/drobilla/sord/-/releases
Sord 0.16.16 (Released 8 months ago)
!! Port sord_validate to pcre2
i don't yet know
(1) why sord maintainer hasn't picked this up
(2) whether a simple update sord 0.16.14 -> 0.16.16
-- actually fixes the dep correctly in sord pkg
-- manages to NOT break anything in the aforementioned "escalating stack of things"
cc: for any comment
jjavorsk@xxxxxxxxxx
guido.aulisi@xxxxxxxxx
--
_______________________________________________
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
