On Fri, 02 Nov 2007 14:07:12 +0100, Till Maas wrote:
> The upgrade path ends with:
>
> ... F8 + F8 updates + F8 updates-testing --> rawhide
>
> An EVR upgrade in F8 updates-testing can only break the path to
> rawhide, not the path to older dists.
Here is an example from the report:
Zim
F7-updates-testing > F8 (0:0.21-1.fc7 > 0:0.19-1.fc7)
Zim-0.21-1.fc7 is in F7 updates-testing but the version in F8 is older. Btw.
there is already a request to add Zim-0.21-1.fc8 to F8 updates-testing.
Yes, but if you only repeat Roland McGrath's request, that one has
been noticed. Perhaps bodhi already offers an interface where to
retrieve a list of pending push requests. Perhaps it doesn't yet.
It's not too long before F8 updates-testing will be opened, and then
push requests will be processed frequently again and won't sit in pending
for a long time.
It seemed to me, that we discuss here, how we would like the script
to behave.
Btw. imho there should be a warning when a stable package in F7 is evr-higher
than a stable package in F8, even when there is a newer package in
F8-updates-testing.
And other maintainers disagree, because as soon as they've pushed an
update to "F8 updates-testing", they don't want to the receive a mail
that tells them that the pkg in "F7 updates" is still newer than "F8
updates".