look into this scratch build:
it try to install gstreamer-plugins-good-devel:
DEBUG backend.py:605: /usr/bin/yum --installroot /var/lib/mock/dist-f13-build-811120-117788/root/ resolvedep 'ant-junit' 'ant' 'jpackage-utils' 'jna' 'libswt3-gtk2' 'gstreamer-plugins-good-devel' 'junit4' 'java-devel >= 1:1.6.0'
then why not install it and why install gstreamer-plugins-good-devel-docs?
This is because the gstreamer-plugins-good-0.10.23-1.fc13 build has issues, in that the -docs subpackage actually provides -devel, which is incorrect.
Erm, reading further, there is no -devel like files for gstreamer-plugins-good, there are just documentation files, hence -docs. Is your build failing somewhere?
i find some:-)
Right, those are older builds, and in those "-devel" packages there aren't any development files. I think you may have an incorrect build require on gstreamer-plugins-good-devel, it doesn't actually give you anything useful. So again, are you having a build failure of some sort?
i just assume that was the reason why it's not build for dist-f12-updates-candidate. now i see mock install jna-3.0.9 and not jna-3.2.4 since it's among updates.
ok so my question change why dist-f12-updates-candidate install jna-3.0.9 in stead of jna-3.2.4.
A lingering buildroot override. This has been fixed and the latest jna will be available soon.
and how can i check (other than try a scratch build) what is the jna status? is there any general way, web interface for this?
Generally you can use 'koji wait-repo' in order to wait for a specific build to show up in a repo. Enough time has passed so you should be able to attempt your build.