Learn more about these different git repos.
Other Git URLs
This relates to this bz:
Which requires that I build freehoo against the new version of libyahoo2.
{{{ Build Tag Built by
libyahoo2-0.7.7-1.20100314svn.fc11 dist-f11-updates-candidate rayvd libyahoo2-0.7.7-1.20100314svn.fc12 dist-f12-updates-candidate rayvd libyahoo2-0.7.7-1.20100314svn.fc13 dist-f13-updates-candidate rayvd }}}
I would like to get the above builds tagged to their respective buildroots so I can build freehoo against them.
(I'm assuming I don't need to request this for rawhide since it should happen on its own).
FYI, freehoo is the only package which depends on libyahoo2 currently:
{{{ $ repoquery --repoid=rawhide --whatrequires --alldeps --queryformat '%{NAME}' libyahoo2 freehoo libyahoo2-devel }}}
The release value is invalid. It should be 4.%{svn_release}%{?dist} afaics: http://cvs.fedoraproject.org/viewvc/rpms/libyahoo2/devel/libyahoo2.spec?r1=1.7&r2=1.8
You overwrote the old SPECs from CVS with increased release values. Please add the missing changelog entries back to the SPEC and rebuild with the proper release value. If you have any questions, please ask here, on the devel mailing list or in irc in #fedora-devel on Freenode.
D'oh. Ok, I think I have this mess cleaned up now. For the Fedora's I rebuilt everything and the latest builds should be:
{{{ libyahoo2-0.7.7-3.20100314svn.fc11 libyahoo2-0.7.7-4.20100314svn.fc12 libyahoo2-0.7.7-4.20100314svn.fc13 }}}
Thanks.
Replying to [comment:3 rayvd]:
D'oh. Ok, I think I have this mess cleaned up now. For the Fedora's I rebuilt everything and the latest builds should be: {{{ libyahoo2-0.7.7-3.20100314svn.fc11 libyahoo2-0.7.7-4.20100314svn.fc12 libyahoo2-0.7.7-4.20100314svn.fc13 }}}
It looks good now. Everything is tagged. Please report back when the override is not needed anymore.
Builds have completed. You can untag these. Thanks!
untagged libyahoo2-0.7.7-3.20100314svn.fc11 libyahoo2-0.7.7-4.20100314svn.fc12 libyahoo2-0.7.7-4.20100314svn.fc13
Metadata Update from @rayvd: - Issue assigned to till
Login to comment on this ticket.