The libiio package was created and after the rawhide built I requested f26/f27 branches (this seems to have changed, I couldn't see how to request all the branches I needed with the initial request).
The two tickets for the branches are: https://pagure.io/releng/fedora-scm-requests/issue/250 https://pagure.io/releng/fedora-scm-requests/issue/251
But the pagure src.fp.o is still only showing master and if I git pull I don't get any new branches: https://src.fedoraproject.org/rpms/libiio
It states that it might take 10 mins to sync but 16hrs later it's still not three.
It looks like it might be possibly one of these already closed issues: https://pagure.io/fedora-infrastructure/issue/6240 https://pagure.io/fedrepo_req/issue/56 https://pagure.io/pagure/issue/2513
But really I'm just guessing but something is amiss here so I've opened a new ticket.
Server side the branch seems to exist, but I believe the difference is that now you have to create and push them yourself (git checkout -b f27 && git push -u origin f27)
git checkout -b f27 && git push -u origin f27
where is this documented? this is quite a change in process over the previous method. I don't see them server side in the src.fp.o web interface
Metadata Update from @pingou: - Issue tagged with: src.fp.o
@pbrobinson, it does say in the comment that closes the ticket: "The branch in PDC was created. Pagure is still processing the request, but in about 10 minutes, you may create the branch in Pagure using git."
The key part is it says you may create the branch using git.
If you have any suggestions as to where to document this further, please let me know as I think that'd be a good idea.
Edit: I made this clearer in the fedrepo-req documentation at https://pagure.io/fedrepo_req I also made this clear in https://fedoraproject.org/wiki/Infrastructure/WhatHappenedToPkgdb#How_do_I_request_a_new_package_or_a_new_branch.
Thank you for filing an issue.
OK. Closing this. Let me know if we should re-open it @pbrobinson.
Metadata Update from @ralph: - Issue close_status updated to: Fixed - Issue status updated to: Closed (was: Open)
Login to comment on this ticket.