From Fedora Project Wiki
m
(Update command examples for fedpkg 1.38)
 
(2 intermediate revisions by 2 users not shown)
Line 28: Line 28:


To request a new repo for the package '''package123''' and with the Bugzilla bug '''5516953''':
To request a new repo for the package '''package123''' and with the Bugzilla bug '''5516953''':
<pre>fedpkg --module-name package123 request-repo 5516953</pre>
<pre>fedpkg request-repo package123 5516953</pre>


To request the '''f27''' branch inside a cloned dist-git repository:
To request the '''f27''' branch inside a cloned dist-git repository:
Line 34: Line 34:


To request the '''f27''' branch on '''package123''' without waiting for the requested repository to be approved and created:
To request the '''f27''' branch on '''package123''' without waiting for the requested repository to be approved and created:
<pre>fedpkg --module-name package123 request-branch f27</pre>
<pre>fedpkg request-branch --repo package123 f27</pre>


To request all active Fedora release branches on '''package123''':
To request all active Fedora release branches on '''package123''':
<pre>fedpkg --module-name package123 --all-releases</pre>
<pre>fedpkg request-branch --repo package123 --all-releases</pre>

Latest revision as of 17:06, 18 March 2020

Migrating from fedrepo-req to fedpkg

Context

As requested by several members of the Fedora community, fedrepo-req and fedrepo-req-branch have been implemented in fedpkg as subcommands. fedrepo-req and fedrepo-req-branch will continue to work but they will no longer be receiving updates. Also, as part of this, I took the opportunity to improve some of the syntax based on feedback from the Fedora community. The largest changes are outlined below.

fedpkg request-repo - this replaces fedrepo-req. One major change is that you can no longer request an additional branch to be created alongside of your new repo. This was a rarely used feature but caused some confusion for users and I decided it was best to leave it out of the fedpkg implementation.

fedpkg request-branch - this replaces fedrepo-req-branch. The largest change here is that you can now request branches for all active Fedora releases in a single command using the --all-releases flag.

Migration

fedrepo-req required you to create a configuration file to contain your Pagure API token at ~/.config/fedrepo_req/config.ini. The contents of that file should look like:

[app]
pagure_api_token = long_token_here

fedpkg requires a different configuration file at ~/.config/rpkg/fedpkg.conf. Create it and add your Pagure API token to look like (replacing "long_token_here" with your actual token):

[fedpkg.pagure]
token = long_token_here

Examples

To request a new repo for the package package123 and with the Bugzilla bug 5516953:

fedpkg request-repo package123 5516953

To request the f27 branch inside a cloned dist-git repository:

fedpkg request-branch f27

To request the f27 branch on package123 without waiting for the requested repository to be approved and created:

fedpkg request-branch --repo package123 f27

To request all active Fedora release branches on package123:

fedpkg request-branch --repo package123 --all-releases