@gordonmessmer pushed 1 commit.
2075c5ea488bb45196c89665f203cf938e63b841 Enhance requires with version
information from the build root.
--
View it on GitHub:
https://github.com/rpm-software-management/rpm/pull/2372/files/0af21b5ca6137983cb0eeea60b1d874302e6f67e..2075c5ea488bb45196c89665f203cf9
```
$ elfdeps --requires --libtool-version-fallback /lib64/libsoup-3.0.so.0
libz.so.1(ZLIB_1.2.0)(64bit)
libgssapi_krb5.so.2(gssapi_krb5_2_MIT)(64bit)
libc.so.6(GLIBC_2.14)(64bit)
libc.so.6(GLIBC_2.4)(64bit)
libc.so.6(GLIBC_2.6)(64bit)
libc.so.6(GLIBC_2.7)(64bit)
libc.so.6(GLIBC_2.3.4)(64bit)
libc.
@gordonmessmer pushed 1 commit.
0af21b5ca6137983cb0eeea60b1d874302e6f67e Avoid using fallback version when
versioned symbols are found.
--
View it on GitHub:
https://github.com/rpm-software-management/rpm/pull/2372/files/2ec718ef2f5794c67bdfed8fd915033d472f21e5..0af21b5ca6137983cb0eeea60b1d874
If we assumed that the SHT_GNU_verneed header appeared before SHT_DYNAMIC, then
when processing the latter, we could loop over the existing ei->requires and
look for elements that start with the same filename, and skip the libtool
version lookup if one is found.
The only problem is that I don't
```
libgssapi_krb5.so.2()(64bit) >= 2.2
libz.so.1()(64bit) >= 1.2.12
```
Well... almost as intended. Those two are unnecessary since the libraries
provide versioned symbols, and shouldn't have additional version information.
I'll figure out how to detect and skip that case. In the mean time,
https://github.com/rpm-software-management/rpm/pull/2315
--
Reply to this email directly or view it on GitHub:
https://github.com/rpm-software-management/rpm/discussions/2022#discussioncomment-4845571
You are receiving this because you are subscribed to this thread.
Message ID:
https://github.com/rpm-software-management/rpm/pull/2315
--
Reply to this email directly or view it on GitHub:
https://github.com/rpm-software-management/rpm/pull/1035#issuecomment-1412820654
You are receiving this because you are subscribed to this thread.
Message ID: __
This version seems to work as intended. It's more complex than I'd like, but
still probably better than parsing the output of ldd.
```
$ elfdeps --requires --libtool-version-fallback /lib64/libsoup-3.0.so.0
libz.so.1(ZLIB_1.2.0)(64bit)
libgssapi_krb5.so.2(gssapi_krb5_2_MIT)(64bit)
libc.so.6(GLIB
@gordonmessmer pushed 1 commit.
2ec718ef2f5794c67bdfed8fd915033d472f21e5 Run dlmopen in a child process.
--
View it on GitHub:
https://github.com/rpm-software-management/rpm/pull/2372/files/41da0a2924d11b23a3f8d34efddf2ee39f6b9204..2ec718ef2f5794c67bdfed8fd915033d472f21e5
You are receiving this
It's not a matter of "sometimes printing them and sometimes not" because you're
querying two different things. Querying the "epoch" is not the same as
querying the "evr".
Really the only argument that can be made is that for nonexistent tags, rpm-cli
should print nothing instead of `(none)`,
Merged #2377 into master.
--
Reply to this email directly or view it on GitHub:
https://github.com/rpm-software-management/rpm/pull/2377#event-8409648034
You are receiving this because you are subscribed to this thread.
Message ID:
___
Rpm-maint maili
Sounds reasonable. Thanks for the patch!
--
Reply to this email directly or view it on GitHub:
https://github.com/rpm-software-management/rpm/pull/2377#issuecomment-1411945623
You are receiving this because you are subscribed to this thread.
Message ID: __
Quoting myself from
https://github.com/rpm-software-management/rpm/pull/1470#issuecomment-772410935:
> That said, what little background processing I've managed to do on this, the
> more I think this isn't a use-case we'd want to be maintaining going forward
> in rpm itself.
I could've sworn
# Description
This is a refactoring of PR
[#1470](https://github.com/rpm-software-management/rpm/pull/1470).
The RPM CoW plugin is refactored to register as owner of payloads transcoded by
`rpm2extents` as suggested in comment
[#2057](https://github.com/rpm-software-management/rpm/discussions/20
So that is all what it was about; **deliberate inconsistency.** Choosing to
print sometimes _epoch_ values, with tag _epoch_, and sometimes not to print
them, with tags _evr_ and _nevra_, would not be expected from developers.
Having such a fantasy in your code must have pleased you so far since
@gordonmessmer pushed 2 commits.
a01b715f68d025387ea394fa367730e30b9629a2 Enhance requires with version
information from the build root.
41da0a2924d11b23a3f8d34efddf2ee39f6b9204 Resolve symlinks when gathering
libtool version.
--
View it on GitHub:
https://github.com/rpm-software-management/
@gordonmessmer pushed 1 commit.
398827f176a1482fbde837b1b997395d024ff37a Resolve symlinks when gathering
libtool version.
--
View it on GitHub:
https://github.com/rpm-software-management/rpm/pull/2372/files/d0c8fc93976325c931d0a98d1c4ff73581dae8bd..398827f176a1482fbde837b1b997395d024ff37a
You
17 matches
Mail list logo
