--Well, it’s possible that these packages will find a new primary maintainer in Fedora: one of the current co-maintainers, one of the maintainers of the mentioned dependent packages, or some other Fedora packager who has an interest in them.
If that doesn’t happen, and the packages end up being retired for the next release of Fedora, then the best workaround if you were using the system packages in your own work would indeed be to install from PyPI instead (not system-wide, preferably into a virtualenv).
Pure-Python libraries like this are usually packaged and maintained mostly to support particular applications in Fedora (perhaps very indirectly) rather than out of a desire to offer system versions of as many PyPI packages as possible.
On 11/9/24 5:49 PM, Blaise Pabon wrote:
Ben,Thank you for your service!Would the workaround be to install from pypi instead?
Blaise
On Sat, Nov 9, 2024, 1:44 PM Ben Beasley <code@xxxxxxxxxxxxxxxxxx> wrote:
I’m orphaning python-opentelemetry and the following related packages:
- python-opentelemetry-contrib
- python-opentelemetry-propagator-aws-xray
- python-opentelemetry-resource-detector-azure
- python-opentelemetry-sdk-extension-aws
The packages are inherently messy, but are in good condition. However,
they are a bit fussy to maintain, and I no longer maintain anything that
relies on them, so I’m choosing to use my time elsewhere.
This will affect python-elastic-transport, which depends on
python3dist(opentelemetry-api) and python3dist(opentelemetry-sdk) from
python-opentelemetry; and it will affect python-sentry-sdk, which
depends on python3dist(opentelemetry-distro).
Maintainers of those affected packages have received this email
directly; so have co-maintainers of the orphaned packages.
An update to the latest versions of python-opentelemetry and
python-opentelemetry-contrib will require dealing with some issues
around old protobuf and grpc versions in Fedora; see
https://src.fedoraproject.org/rpms/python-opentelemetry/pull-request/19.
--
_______________________________________________
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
-- _______________________________________________ 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
