epel

#294 Fixing nautilus-python in EPEL {8,9} - incompatible update or not?
Opened by salimma. Modified

Open
Close Issue

nautilus-python in EPEL 8 and 9 are at version 1.2.3 - the latest is 4.0.1

Apparently this does not actually work - https://bugzilla.redhat.com/show_bug.cgi?id=2117450 - and probably never worked? Troy mentioned he only packaged it as a build dependency of KDE

Happy to request an incompatible update for this, but ... is this an example of a situation where we don't need it, because the package never worked?

We (Michel and I) are going to give this a couple of weeks to try to get this fixed. It might involve updating the package.
If we are unable to get it fixed, we'll work on getting it retired out of EPEL 8 and 9.
Edited by salimma

Metadata Update from @tdawson:
- Issue untagged with: meeting

updated the Bugzilla

We don't have a standing rule to allow an incompatible update because a package is broken. If we go down the incompat update process, we'll evaluate it like anything else, but can certainly factor in the current brokenness.

I do think we should either get the package working or retire it, in both EPEL 8 and 9. The impact from retiring it seems rather minimal. The packages that require it seem to be optional subpackages that can be easily conditionally disabled in their respective spec files.

EPEL 8:
- kde-connect-nautilus
- nextcloud-client-nautilus

EPEL 9:
- kde-connect-nautilus
- nextcloud-client-nautilus
- tilix-nautilus

Metadata Update from @carlwgeorge:
- Issue tagged with: meeting

Metadata Update from @carlwgeorge:
- Issue untagged with: meeting

This issue has been migrated to Fedora Forge:
https://forge.fedoraproject.org/epel/steering/issues/294

Please continue any further discussion there.
Metadata
None
None
None
None
None
Static archive. pagure.io was sunset in 2026; this is a read-only snapshot.
Red Hat Logo

Fedora is sponsored by Red Hat. Learn more about the relationship between Red Hat and Fedora »

© Red Hat, Inc. and others.