Hi all.
I need to downgrade python-reportlab in Fedora 35 for a missing runtime dependency. What's the most accurate way?
Bug ticket: https://bugzilla.redhat.com/show_bug.cgi?id=2097817 Update: https://bodhi.fedoraproject.org/updates/FEDORA-2022-23aefe21ad
Regards.
On Thursday, 16 June 2022 17.55.45 WEST Antonio T. sagitter wrote:
Hi all.
I need to downgrade python-reportlab in Fedora 35 for a missing runtime dependency. What's the most accurate way?
Bug ticket: https://bugzilla.redhat.com/show_bug.cgi?id=2097817 Update: https://bodhi.fedoraproject.org/updates/FEDORA-2022-23aefe21ad
Regards.
Not to be the bad news bringer but I think that the only way is to use epoch in the spec file. And to rebuild with a higher epoch.
Something that I do not remember is what to do the with the other releases. Are we still forced, in order to ensure an upgrade path, to keep the epoch?
Or can we assume that system-upgrade will allow to get rid of that artifact (of all the things I could call to epoch I think that this is the nicest). :-)
Regards,
On Fri, Jun 17, 2022 at 10:38:19AM +0100, José Abílio Matos wrote:
On Thursday, 16 June 2022 17.55.45 WEST Antonio T. sagitter wrote:
Hi all.
I need to downgrade python-reportlab in Fedora 35 for a missing runtime dependency. What's the most accurate way?
Bug ticket: https://bugzilla.redhat.com/show_bug.cgi?id=2097817 Update: https://bodhi.fedoraproject.org/updates/FEDORA-2022-23aefe21ad
Regards.
Not to be the bad news bringer but I think that the only way is to use epoch in the spec file. And to rebuild with a higher epoch.
Something that I do not remember is what to do the with the other releases. Are we still forced, in order to ensure an upgrade path, to keep the epoch?
Or can we assume that system-upgrade will allow to get rid of that artifact (of all the things I could call to epoch I think that this is the nicest). :-)
Nope, it has to stay forever. Sorry.
kevin
On Fri, Jun 17 2022 at 02:00:14 PM -0700, Kevin Fenzi kevin@scrye.com wrote:
Nope, it has to stay forever. Sorry.
Hi, can you explain why? Since we do not maintain upgrade paths from one release to the next anymore, and instead require use of system upgrade, I would have assumed that epoch would only have to stay for the life of a particular Fedora release?
On Fri, Jun 17, 2022 at 04:15:35PM -0500, Michael Catanzaro wrote:
On Fri, Jun 17 2022 at 02:00:14 PM -0700, Kevin Fenzi kevin@scrye.com wrote:
Nope, it has to stay forever. Sorry.
Hi, can you explain why? Since we do not maintain upgrade paths from one release to the next anymore, and instead require use of system upgrade, I would have assumed that epoch would only have to stay for the life of a particular Fedora release?
I suppose it could be feasable to do it for packages that nothing has any dependencies on. But for packages that do, there would be a lot of churn adjusting the deps every cycle, it would prevent merges back to older branches and just cause confusion. IMHO.
If we want to allow this, it should at least have a clear checklist/guideline on how to do things because I think it would be easy to get wrong. :(
kevin
-
Antonio T. sagitter -
José Abílio Matos -
Kevin Fenzi -
Michael Catanzaro