[Bug 1468939] Review Request: ocaml-gen - Simple, efficient iterators for OCaml

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



https://bugzilla.redhat.com/show_bug.cgi?id=1468939



--- Comment #6 from Robert-André Mauchin <zebob.m@xxxxxxxxx> ---
You are already member of the packager group so you don't need any sponsor.

Fedora has changed the way to request package since August. We are now using a
tool called fedrepo-req. See the help here https://pagure.io/fedrepo_req

First look at the Configuration section:

 - you need to log on https://src.fedoraproject.org/
 - there request a new token https://pagure.io/settings/token/new
 - this token is valid for two months
 - paste the token in ~/.config/fedrepo_req/config.ini like this:

[app]
pagure_api_token = <api_key_here>


Step 2: now request a new repo for your package (see the Usage section for
details) with you bugzilla bug number:

$ fedrepo-req ocaml-gen -t 1468639 --monitor monitoring

You can also request new branches for f27, f26, epel7… with:

$ fedrepo-req-branch ocaml-gen f27

In both case, you will be given a ticket number (list of tickets are here
https://pagure.io/releng/fedora-scm-requests/issues ). These tickets are
processed by a human' they are generally approved within a day or two.

Step 3: Once your tickets are approved, you can clone the newly created repo:

$ fedpkg clone ocaml-gen

(If you've got an authentication error, make sure you are authenticated with
Kerberos: $ KRB5_TRACE=/dev/stdout kinit andyli@xxxxxxxxxxxxxxxxx )

Then you can import your SRPM:

$ cd ocaml-gen
$ fedpkg import /path/to/your/srpm

Commit the change like this:

$ fedpkg commit -m "Initial import (#1468639)"

Then push it to the repo:

$ fedpkg push

Now that the package is pushed, you can build it in Koji:

$ fedpkg build

If everything is fine, your package will be built on all relevant arches.
It will then be available on Rawhide in the next compose check.

If you have requested more branches, you can now process them too. First we
switch to the version for which we want to build:

$ fedpkg switch-branch f27

Then since it's a new package, we merge master into the new branch:

$ git merge master

We push the new branch:

$ fedpkg push

And finally we can build the package for f27:

$ fedpkg build

When the building is done, you can request a Bodhi ticket in order to have the
package included as an update:

$ fedpkg update

Fill the requested information (newpackage and this bug number), then save. You
will be given a "receipt" acknowledging the request. The package will then be
available in updates-testing shortly.

You can process other branch f26, epel7… the same way. Finally switch back to
master when you're done:

$ fedpkg switch-branch master

-- 
You are receiving this mail because:
You are on the CC list for the bug.
You are always notified about changes to this product and component
_______________________________________________
package-review mailing list -- package-review@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to package-review-leave@xxxxxxxxxxxxxxxxxxxxxxx




[Index of Archives]     [Fedora Users]     [Fedora Desktop]     [Fedora SELinux]     [Yosemite Conditions]     [KDE Users]

  Powered by Linux