http://autoqa.fedoraproject.org/results/615735-autotest/virt06.qa/upgradepat...
says 'supermin-4.1.1-2.fc18' fails the test because f19 + f19-updates only has 'supermin-4.1.1-1.fc19' (which is a lower version number).
Fair enough, but f19 updates-testing (not updates) does have the right package, it just hasn't quite made it to the end of the testing period yet:
https://admin.fedoraproject.org/updates/FEDORA-2013-12393/supermin-4.1.1-2.f...
Shouldn't updates-testing be taken into account by the Upgradepath test?
Or perhaps there should be a way to push all packages at once, even though they are in different branches? In this case the issue was a crasher bug which I wanted to fix in all branches at once.
This seems to be a similar issue:
https://fedorahosted.org/autoqa/ticket/330
Rich.
On Sun, Jul 14, 2013 at 13:55:49 +0100, "Richard W.M. Jones" rjones@redhat.com wrote:
Shouldn't updates-testing be taken into account by the Upgradepath test?
Probably only for stuff that is part of the same update. Otherwise there is no guaranty that both will be released at the same time.
Shouldn't updates-testing be taken into account by the Upgradepath test?
Probably only for stuff that is part of the same update. Otherwise there is no guaranty that both will be released at the same time.
Exactly. Also see 2) in https://fedoraproject.org/wiki/AutoQA_tests/Upgradepath#Fixing_the_failures
The upgrade path is now broken, since your F18 update went stable. People upgrading F18 to F19 will end up with a .fc18 package instead of .fc19 package, which might break some functionality (or even RPM dependencies) for them.