That's not something the rpm upstream can help with, this would be a packaging
matter in brew. How that all works or who maintains it there, we have no idea.
--
Reply to this email directly or view it on GitHub:
Closed #2684 as resolved.
--
Reply to this email directly or view it on GitHub:
https://github.com/rpm-software-management/rpm/discussions/2684
You are receiving this because you are subscribed to this thread.
Message ID:
___
Rpm-maint mailing list
We don't provide builds or packaging for any platform. You need to report that
to whoever maintains that build/package.
--
Reply to this email directly or view it on GitHub:
https://github.com/rpm-software-management/rpm/issues/2682#issuecomment-1742530085
You are receiving this because you are
Closed #2682 as completed.
--
Reply to this email directly or view it on GitHub:
https://github.com/rpm-software-management/rpm/issues/2682#event-10522821207
You are receiving this because you are subscribed to this thread.
Message ID:
___
Rpm-maint
@pmatilai Fine. Should I understand that the elfdeps depedency is platform
dependent?
--
Reply to this email directly or view it on GitHub:
https://github.com/rpm-software-management/rpm/issues/2682#issuecomment-1742724041
You are receiving this because you are subscribed to this thread.
That question doesn't really make sense in the upstream context because there's
no "elfdeps dependency" anywhere.
Building the elfdeps tool requires the libelf library. I'm not aware of it
being a Linux-only thing but that doesn't much.
--
Reply to this email directly or view it on GitHub:
> Requiring Python >= 3.7 is not a problem, I'm just curious as to what makes
> that particular version special.
[`PySlice_GetIndicesEx`](https://docs.python.org/3/c-api/slice.html#c.PySlice_GetIndicesEx)
uses a deprecated implementation (on all Python versions) if ABI compatibility
with 3.6
