Issue #961: two new packages need tagging for update candidate - dnsperf and unbound - releng

releng

#961 two new packages need tagging for update candidate - dnsperf and unbound

Closed: Fixed None Opened 15 years ago by releng.

I am getting "is not tagged as an update candidate" for unbound and dnsperf packages for F10 and F11. F-9 worked and push requests for testing were successfully created.

Googling showed me I might need to request it from rel-eng?

notting commented 15 years ago

They appear to be in the proper tags. Are you using the web ui or the command line client?

releng commented 15 years ago

I was using the web client. I am still getting: unbound-1.0.2-5.fc11 not tagged as an update candidate

releng commented 15 years ago

The fc10 updates now worked for unbound and dnsperf, but for fc11 they still fail:

unbound-1.0.2-5.fc11 not tagged as an update candidate
dnsperf-1.0.1.0-4.fc11 not tagged as an update candidate

jkeating commented 15 years ago

F11 is still quite a ways off, you can't submit updates for F11.

Metadata

Assignee

None

Tags

None

Blocking

None

Depending on

None

Milestone

None

duplicate

None

blockedby

None

blocking

None

releng

Source Code

Documentation

#961 two new packages need tagging for update candidate - dnsperf and unbound Closed: Fixed None Opened 15 years ago by releng.

Metadata

#961 two new packages need tagging for update candidate - dnsperf and unbound

Closed: Fixed None Opened 15 years ago by releng.