On 16.12.2013 17:55, Alexander Bokovoy wrote:
On Mon, 16 Dec 2013, Rich Megginson wrote:
Simo thinks that this is a reason why 'downgrade package' with 1.3.1.x
inevitably needs automated script which will purge two missing plugins
We have an upgrade/downgrade framework, it should be easy to
disable/remove these plugins.
Is that it? Are there any other problems found attempting to downgrade
1.3.2 to 1.3.1 in F20?
Packaging issue -- epoch will have to be increased and maintained
forever. It is weird but that's what it is.
Sure. But that's a one time thing. And, it's only for F20 - once we go
to F21, we can remove the epoch.
No, and that's key here. Once Epoch is in place, it is forever.
Because that's how RPM is built. When Epoch value is absent it is
assumed to be equal to 0.
188.8.131.52-1 will be equal to 0:184.108.40.206-1 and less than 220.127.116.11-1,
however, 1:18.104.22.168-1 will be greater than 22.214.171.124-1 because the latter
is equal to 0:126.96.36.199-1.
Once epoch is there, it is to stay.
Anyway, is it a real problem? Personally, I consider it like
On my Fedora 19:
$ repoquery -qa | wc -l
(packages in total)
$ repoquery -qa | grep -- '-[1-9][0-9]*:' | wc -l
(packages with non-zero epoch)
Freeipa-devel mailing list