Matt Domsch (Matt_Domsch@xxxxxxxx) said: > > $ make update > > [snip clog] > > Creating a new update for vdr-remote-0.4.0-5.fc10 > > vdr-remote-0.4.0-5.fc10 not tagged as an update candidate > > > > $ koji tag-pkg dist-f10-updates-candidate vdr-remote-0.4.0-5.fc10 > > [snip] > > TagError: build vdr-remote-0.4.0-5.fc10 already tagged > > (dist-f10-updates-candidate) > > 0 free 0 open 0 done 1 failed > > > > $ make update > > [snip clog] > > Creating a new update for vdr-remote-0.4.0-5.fc10 > > vdr-remote-0.4.0-5.fc10 not tagged as an update candidate > > > > http://koji.fedoraproject.org/koji/buildinfo?buildID=68113 > > > You need to request rel-eng to pull it in. > https://fedorahosted.org/rel-eng/newticket Shouldn't be needed for updates. What I suspect is happening is that the wrong branch is being passed to bodhi-client. If you do an early branch for F10 and then do the update, the right thing will probably happen, although that may not be what you want. (The web UI may also work, if it's been set up.) Bill -- fedora-devel-list mailing list fedora-devel-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/fedora-devel-list
