Bug 1979499 - Obsolete custodia and python3-custodia 0.6.0-15
Summary: Obsolete custodia and python3-custodia 0.6.0-15
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Fedora
Classification: Fedora
Component: fedora-obsolete-packages
Version: rawhide
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Miro Hrončok
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On: 1980460
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-07-06 08:28 UTC by Christian Heimes
Modified: 2021-07-14 09:57 UTC (History)
2 users (show)

Fixed In Version: fedora-obsolete-packages-35-11
Clone Of:
Environment:
Last Closed: 2021-07-14 09:56:45 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Fedora Pagure freeipa issue 8882 0 None None None 2021-07-06 08:28:39 UTC

Description Christian Heimes 2021-07-06 08:28:39 UTC
Description of problem:
FreeIPA no longer depends on Custodia. The package has been retired in Rawhide. Please include obsoletes in fedora-obsolete-packages

Version-Release number of selected component (if applicable):
custodia-0.6.0-15
python3-custodia-0.6.0-15

Comment 2 Miro Hrončok 2021-07-06 08:55:36 UTC
The general rule of thumb is: if it isn't causing upgrade path issues or if there is no legal/security reason etc., we don't obsolete packages, but rather leave them to rot on the installed systems.

This package will cause upgrade path issues, because it requires Python 3.9 packages on Fedora 34, so we can merge this.

Do note however that I plan to obsolete packages that used to required Python 3.9 in Fedora 33/34 but are retired or otherwise removed from Fedora 35 in one batch.

Comment 3 Christian Heimes 2021-07-06 09:13:37 UTC
I opened this obsolete BZ because FreeIPA's OpenQA on Rawhide is failing with an upgrade issue related to python3-custodia: https://openqa.fedoraproject.org/tests/921494#step/upgrade_run/15

FreeIPA <= 4.6.9-1 required python3-custodia. The dependency was removed by update 4.9.6-2.


Note You need to log in before you can comment on or make changes to this bug.