AutoQA Upgradepath doesn't consider updates-testing?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



http://autoqa.fedoraproject.org/results/615735-autotest/virt06.qa/upgradepath/results/supermin-4.1.1-2.fc1.html

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.fc19

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.

-- 
Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones
Read my programming blog: http://rwmj.wordpress.com
Fedora now supports 80 OCaml packages (the OPEN alternative to F#)
-- 
devel mailing list
devel@xxxxxxxxxxxxxxxxxxxxxxx
https://admin.fedoraproject.org/mailman/listinfo/devel





[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Fedora Announce]     [Fedora Kernel]     [Fedora Testing]     [Fedora Formulas]     [Fedora PHP Devel]     [Kernel Development]     [Fedora Legacy]     [Fedora Maintainers]     [Fedora Desktop]     [PAM]     [Red Hat Development]     [Gimp]     [Yosemite News]
  Powered by Linux