Zen

Source string Source string

87/10000 · 87

The string is read only.

English Actions
This is a short version of the New Package Process, streamlined to show how existing contributors can make new packages.
Read the xref:packaging-guidelines::index.adoc[Packaging Guidelines] and xref:packaging-guidelines::Naming.adoc[Package Naming Guidelines]. Really. Be comfortable with them.
Make a package.
You should make sure that it is a new package. A list of existing packages in Fedora Packages is here: https://src.fedoraproject.org/projects/rpms/*
Some information on how to create an RPM package is in xref:Packaging_Tutorial.adoc[Packaging Tutorial].
Make sure that your package meets the xref:packaging-guidelines::index.adoc[Packaging Guidelines] and xref:packaging-guidelines::Naming.adoc[Package Naming Guidelines]
Be aware of https://fedoraproject.org/wiki/Forbidden_items[forbidden items] and xref:packaging-guidelines::ReviewGuidelines.adoc[Package Review Guidelines]. They will be used during the package review.
Upload your SRPM and SPEC files onto the internet somewhere.
If you have already got a Fedora Account then you can use your storage at https://fedorapeople.org for this.
Make sure you have a Bugzilla account at bugzilla.redhat.com
Fill out https://bugzilla.redhat.com/bugzilla/enter_bug.cgi?product=Fedora&format=fedora-review[Bugzilla Fedora review form] to create a review request.
Make sure you put the name of the package in the `Review Summary` field, along with a very brief summary of what it is
Make sure that you put the URL paths for the SPEC file and the SRPM file in the `Review Description`
Put a description of your package (usually, this can be the same thing as what you put in the spec `%description`) in `Review Description`
The review process is described in detail in xref:packaging-guidelines::ReviewGuidelines.adoc[Package Review Guidelines].
Watch the review request in Bugzilla. Fix any blockers that the reviewer(s) point out.
When the package is approved, request a distgit repository for your package.
Make sure the reviewer is the Assignee in your Bugzilla ticket.
Request a distgit repository with `fedpkg request-repo PACKAGE-NAME BUGZILLA-TICKET-NUMBER`. (xref:Package_Maintenance_Guide.adoc[Package Maintenance Guide] has more information about `fedpkg`.) You might need to get a pagure-API-token before being able to successfully request the repo.
When the repo is created, it only contains the `rawhide` branch. If you want to bring the package to other Fedora releases, see xref:Package_Maintenance_Guide.adoc#requesting_branches[Requesting branches].
Once the requests have been processed, checkout the distgit repository with `fedpkg clone <packagename>`.
Import your srpm
First `fkinit -u username`
Then you can import the approved SRPM into the rawhide branch by running `fedpkg import libfoo-x.x.x.src.rpm; git commit -m "Initial import (fedora#nnnnnn)."` (where `nnnnnn` is your Bugzilla package review bug number). If your package is using _autochangelog_, writing the bug number as specified will make Bodhi automatically close the bug when your package is submitted to Rawhide stable repository.
Obviously, replace `libfoo-x.x.x.src.rpm` with the full path to your approved SRPM.
You should see it upload the sources, and finish successfully. If you didn't set up `ssh-agent` it will ask often for your ssh-key passphrase. This is normal.
Now run `git push` to get the final versions in your rawhide branch.
You can now import the package to your branches (which you requested in Step 7) too
The quickest way to do this is to use `fedpkg switch-branch BRANCH` to switch the branch (where `BRANCH` can be `f13` and so on).
Now you can `git merge rawhide`. This will get `.spec` file, `.gitignore` and source file together with any patches and other files from the rawhide branch and create an identical commit.
Previous step already created commit for you, now you can push the results using `fedpkg push` or `git push`.

Loading…

User avatar None

String updated in the repository
Watch the review request in Bugzilla. Fix any blockers that the reviewer(s) point out.
Watch the review request in Bugzilla. Fix any blockers that the reviewer(s) point out.
10 months ago
Browse all string changes

Things to check

Unpluralised

The string is used as plural, but not using plural forms

Reset

Glossary

English English
No related strings found in the glossary.

String information

Source string description
type: Plain text
Flags
placeholders:r"`[\w\d -_<>(){}\[\]@$;.\*+=]*`":r"(link:)?https?://[\w\d\-_#?&%=\./]*":r"xref:[\w\d\-_/]*\.adoc(#[\w\d\-_/]*)?", read-only
Source string location
./pages/New_Package_Process_for_Existing_Contributors.adoc:47
String age
10 months ago
Last updated
10 months ago
Source string age
10 months ago
Translation file
pot/master/pages/New_Package_Process_for_Existing_Contributors.pot, string 17