#7694 New Repo for "rpms/python-inotify_simple"
Closed: Processed 5 years ago Opened 5 years ago by praiskup.

{
 "bug_id": 1618686, 
 "repo": "python-inotify_simple", 
 "exception": false, 
 "description": "", 
 "branch": "master", 
 "action": "new_repo", 
 "upstreamurl": "", 
 "summary": "A simple Python wrapper around inotify", 
 "namespace": "rpms", 
 "monitor": "monitoring"
}

Why I can not request multiple branches by single fedpkg request-repo ticket?

What difference does it make to you? The ticket repository is only be used as a place to store the relevant bit of json and should be treated as opaque. Which is how it normally works, until someone decides to add comments.

Metadata Update from @limb:
- Issue close_status updated to: Processed
- Issue status updated to: Closed (was: Open)

5 years ago

@tibbs, I mean, it would be nice if I could request epel7 and f27+ branches directly during the initial request. It used to work like that these days...

The new thing for fedora rpms is that I have to submit one ticket (this one), wait till it is processed, and then submit several other tickets (for each branch:

$ fedpkg request-branch epel7 f29 f28 f27
usage: fedpkg [-h] [--config CONFIG] [--release RELEASE | --dist DIST]
..
fedpkg: error: unrecognized arguments: f29 f28 f27

But yeah, it's not really proper place to discuss this.

Login to comment on this ticket.

Metadata