From Fedora Project Wiki

(→‎Install the Client Tools (Koji): plague is no longer used by EPEL & some other cleanup and additions)
(183 intermediate revisions by 78 users not shown)
Line 1: Line 1:
{{autolang|base=yes}}
= Contributing roles =
= Contributing roles =
{{admon/tip|Contributing roles|These are only suggestions for contributing roles. Only your imagination sets the limits. }}
{{admon/tip|Contributing roles|These are only suggestions for contributing roles. Only your imagination sets the limits. }}
Line 11: Line 13:
= How to join the Fedora Package Collection Maintainers? =
= How to join the Fedora Package Collection Maintainers? =


So, you have decided to become a package maintainer in the Fedora Project?  This guide will lead you through your first package submission.
So, you have decided to become a package maintainer in the Fedora Project?  This guide will lead you through your first package submission. It can be a completely new package, or update to an existing package.


== Becoming a Fedora Package Collection Maintainer ==
[[Image:fedora-submit-package.png]]
 
== Preparation ==


=== Read the Guidelines ===
=== Read the Guidelines ===


If you don't know how to create an RPM package, see the [[PackageMaintainers/CreatingPackageHowTo|Creating Package HOWTO]] and the [[Docs/Drafts/BuildingPackagesGuide|Building Packages Guide]].
If you don't know how to create an RPM package, refer to the tutorial at [[How to create a GNU Hello RPM package]] or the more advanced and much more detailed  [https://docs.fedoraproject.org/en-US/quick-docs/creating-rpm-packages/index.html Creating RPM packages].


Read the [[Packaging/Guidelines|  Packaging Guidelines]] and [[Packaging/NamingGuidelines|  Package Naming Guidelines]] .
Read the [https://docs.fedoraproject.org/en-US/packaging-guidelines/ Packaging Guidelines] and [https://docs.fedoraproject.org/en-US/packaging-guidelines/Naming/ Package Naming Guidelines].


You need to be thoroughly familiar with these.  They govern all package submissions.  If you have questions, ask on the [https://www.redhat.com/mailman/listinfo/fedora-packaging Fedora Packaging List] .
You need to be thoroughly familiar with these.  They govern all package submissions.  If you have questions, ask on the Fedora {{fplist|packaging}} List.


=== Create a Bugzilla Account ===
=== Create a Bugzilla Account ===
Line 27: Line 31:
Make sure you have an account in [https://bugzilla.redhat.com/ Red Hat Bugzilla] .
Make sure you have an account in [https://bugzilla.redhat.com/ Red Hat Bugzilla] .


The email address that you use for your bugzilla account should be the same email address as you use in the [[#Get_a_Fedora_Account| Fedora Account System]] for all things related to Fedora Packaging.
The email address that you use for your Bugzilla account should be the same email address as you use in the [[#Get_a_Fedora_Account| Fedora Account System]] for all things related to Fedora Packaging.
 
{{admon/important|Do not use your @fedoraproject.org address if you already have one.|You should not use your @fedoraproject.org email address in Bugzilla, because you will not get your Bugzilla privileges once you are sponsored. If you want to use your @fedoraproject.org address, you might try to request at the [https://pagure.io/fedora-infrastructure/issues Fedora Infrastructure Ticket System] for an administrator to manually override the Bugzilla address connected with your Fedora Account.}}
 
{{Anchor|GetAFedoraAccount}}
 
=== Create a Fedora Account ===
 
Create an account in the [[Infrastructure/AccountSystem |Fedora Account System]] (this is ''not'' the same as the Bugzilla account)
 
# Visit the account system home: https://accounts.fedoraproject.org/
# Click on 'New account' and fill in the blanks.  Note that the email you give should be the same as the one you gave Bugzilla.  This allows the system to link privileges between the two accounts.
# After you create your account, please be sure to agree to the FPCA (if you click on the "edit profile" link on the right, then the 'Agreements' tab. If this says 'view' you have agreed already, if it says 'sign' you still need to agree).
# You will also need to upload a public SSH key. You need to use the matching private key to access Fedora machines via SSH.  You can read more about this [[Cryptography | here]].


=== Join the important Mailing Lists ===
=== Join the important Mailing Lists ===


You must join the [https://www.redhat.com/mailman/listinfo/fedora-devel-announce fedora-devel-announce@redhat.com]  mailing list. It is a low traffic announcements only list, where important development information is posted.
You should join the fedora {{fplist|devel-announce}} mailing list. It is a low traffic announcements only list, where important development information is posted.


You can join the [https://www.redhat.com/mailman/listinfo/fedora-devel-list fedora-devel-list@redhat.com]  mailing list, where discussions about the development of Fedora are held. This is a high traffic mailing list.
You should join the fedora {{fplist|devel}} mailing list, where discussions about the development of Fedora are held. This is a high traffic mailing list.


You can also consider joining the [https://www.redhat.com/mailman/listinfo/fedora-extras-commits fedora-extras-commits@redhat.com]  mailing list -- The commits mailing list gets notifications on all commits in any package in the Fedora repository. This is a very high traffic mailing list. The Fedora package database sends commit mails for packages you (co-)maintain.
You should also consider joining the {{fplist|package-announce}} mailing list -- The commits mailing list gets notifications on all commits in any package in the Fedora repository. This is a very high traffic mailing list. The Fedora package database sends commit mails for packages you (co-)maintain.


Another mailing list you might consider (at least to view the archives) is
Another mailing list you might consider (at least to view the archives) is {{fplist|packaging}}. This is the mailing list of the [[Packaging/Committee | Fedora Packaging Committee]], who determine the official packaging guidelines for Fedora projects.
[http://www.redhat.com/mailman/listinfo/fedora-packaging fedora-packaging@redhat.com].
This is the mailing list of the [[Packaging/Committee | Fedora Packaging Committee]],
who determine the official packaging guidelines for Fedora projects.


=== Read Other Submissions ===
=== Introduce yourself ===
 
Next, you should introduce yourself to the community on the {{fplist|devel}} mailing list. The primary purpose of this is to begin the process of building trust by allowing the Fedora community members to get to know you a bit more.
 
We want to break anonymity and foster real-world community within the project. You are under no obligation to reveal personal secrets. The objective is to establish a level of trust between yourself and the other members of the project. But you should at least use your real name when communicating with us. Also, a brief description of who you are, your motivations and perhaps a description of the software you have submitted for review are advisable.


Read some other package submissions to learn about packaging and gain familiarity with the process and requirements.
<pre>


One way of doing this is to join the [http://www.redhat.com/mailman/listinfo/fedora-package-review fedora-package-review@redhat.com mailing list] ;
Subject: Self Introduction<Your name>
all comments on Fedora package reviews are sent to this (read-only from your point of view) list.


=== Make a Package ===
Body:  Add any information you believe is applicable
including past experience in free and open source projects,
a link to the review request you have filed and
a brief description of yourself. You can also post
your GPG key information if you want to.


You should make sure that it is a new package. The package you are submitting can be of any Free and open source project that is not already packaged in Fedora. You can find a list of existing packages in Fedora Package Collection in the [https://admin.fedoraproject.org/pkgdb/packages/ Fedora Package Database]. Please also check the [[PackageMaintainers/ReviewRequests | in progress and unassigned Review Requests]], giving the list of packages that need a review or are currently under review, as well as the [[PackageMaintainers/RetiredPackages | retired package]] list.
</pre>


* If you don't know how to create an RPM package, see the [[PackageMaintainers/CreatingPackageHowTo|Creating Package HOWTO]].
Feel free to participate in all the discussion that goes on in any of the lists. Community discussion and feedback is always encouraged.
* Make sure that your package meets the [[Packaging/Guidelines|  Packaging Guidelines]]  and [[Packaging/NamingGuidelines|  PackageNamingGuidelines]] .
* Be aware of [[ForbiddenItems | Forbidden Items]] and [[Packaging/ReviewGuidelines| Package Review Guidelines]]  (they will be used during the package review).


=== Upload Your Package ===
=== Find software you wish to package/maintain for Fedora ===


Upload your SRPM and SPEC files onto the Internet somewhereThis can be anywhere accessible by a URL.
{{admon/note||Note that there's other methods for getting sponsored into the packager group than submitting a new packageCheck the [[How_to_get_sponsored_into_the_packager_group| How to get sponsored page]] for more info.}}


{{Anchor|CreateYourReviewRequest}}
The package you are submitting can be of any Free and Open Source project that is not already packaged in Fedora. Before creating your package, make sure that the software is not already in the Fedora repository, or waiting for review.
=== Create Your Review Request ===


Fill out this form: https://bugzilla.redhat.com/bugzilla/enter_bug.cgi?product=Fedora&format=extras-review.
* Search the [https://src.fedoraproject.org/ Fedora packages] for packages already in the repository.
* Search in the [http://fedoraproject.org/PackageReviewStatus/ Review Tracker] for packages under review.
* Also check the [[Orphaned package that need new maintainers | orphaned packages that need new maintainers]].
* Be aware of [[forbidden items]].


* Make sure that you put the '''name of the package''' (excluding version and release numbers) in the '<code>Review Summary</code>' field, along with a very '''brief summary''' of what the package is.
=== Understand your responsibilities ===
* Upload the spec file and SRPM to a public website. If you need hosting space, please make a note of it in your ticket submission and someone will take care of you. If you are a Fedora package maintainer already, you can make use of http://fedorapeople.org
* Put a '''description''' of your package (usually, this can be the same thing as what you put in the spec %description) in the '<code>Review Description</code>' field.  Include the '''URLs''' to your '''SRPM''' and '''SPEC''' files. Also, explain that this is your first package and you need a sponsor.


{{Admon/warning | Make sure that you mention in the '<code>Review Description</code>' field that this is your first package, and you are seeking a sponsor. In Fedora Package Collection, all new contributors must be sponsored. Some potential sponsors will look at the [https://bugzilla.redhat.com/bugzilla/showdependencytree.cgi?id&#61;FE-NEEDSPONSOR FE-NEEDSPONSOR] bug in bugzilla to find packages to review. You can add your package to this list by editing your review request bug and adding <code>FE-NEEDSPONSOR</code> in the '<code>Bug </code>''xyz''<code> blocks</code>' field (where ''xyz'' is the bug number for your review request).}}
Software components included in Fedora need to be maintained actively, and bugs - especially security issues - need to be fixed in a timely manner. As a Fedora package maintainer, it is your primary [https://docs.fedoraproject.org/en-US/fesco/Package_maintainer_responsibilities/ responsibility] to ensure this. We encourage you to get [[Policy_for_encouraging_comaintainers_of_packages | co-maintainers]] and seek the help of the Fedora community via the development mailing list whenever needed.


The review process is described in detail on the [[Package Review Process| Package Review Process]]  page.
=== Read Other Submissions ===


{{Anchor|WatchForFeedback}}
Read some other package submissions to learn about packaging and gain familiarity with the process and requirements.
=== Watch for Feedback ===


Watch the Bugzilla report for your first package. You should get notifications of changes by email. Fix any blockers that the reviewer(s) point out.
One way of doing this is to join the {{fplist|package-review}} mailing list;All comments on Fedora package reviews are sent to this (read-only from your point of view) list.


{{Anchor|GetAFedoraAccount}}
=== Configure Your Git ===
=== Get a Fedora Account ===


Create an account in the [[Infrastructure/AccountSystem|  Fedora Account System]] (this is ''not'' just a bugzilla account)
The first thing to do when you set up Fedora packaging is to configure your username and email address for Git. These are linked in each commit you do to Fedora packages.


# Visit the account system home: https://admin.fedoraproject.org/accounts/
<pre>
# Click on 'New account' and fill in the blanks.
git config --global user.name "John Doe"
# After you create your account, please be sure to sign the CLA (if you click on the "My Account" link in the top right, you should see CLA: CLA Done)<br>'''Note:''' Red Hat employees should apply for <code>cla_redhat</code> instead. From the Account System, Apply for a New Group, put <code>cla_redhat</code> in the group field, and click Apply.  Then ask TomCallaway to approve you.
git config --global user.email johndoe@example.com
# Once you get email confirmation that your account has been created and you're a member of the <code>cla_done</code> group, return to edit your account: https://admin.fedoraproject.org/accounts/group/list?search=packager*
</pre>
## In the table, look for the <code>packager</code> group, and click <code>Apply</code> under Status.
## Once this is done, your account will show up as "pending" to all of the Fedora Package Collection sponsors (who will receive an email).
## When you are sponsored, you will be automatically added/approved to the fedorabugs group as well.  This will allow you to make changes to the state of bugs in Bugzilla, which is what you'll need to do to get them checked in.  It will also allow you to do complete package reviews, including approving packages yourself!


{{Anchor|GetSponsored}}
=== Install the developer client tools ===


=== Install the Client Tools (Koji) ===
To build Packages for the Fedora Collection or [[EPEL]] in the Fedora build system you need [[Using_the_Koji_build_system|Koji]].
To build Packages for the Fedora Collection or [[EPEL]], you need [[PackageMaintainers/UsingKoji|Koji]].
You'll also need to generate a client side certificate at the [https://admin.fedoraproject.org/accounts/user/gencert|Fedora Account System] and save the file in <code>~/.fedora.cert</code>, where the Fedora CVS makefiles will look for it by default.


{{admon/tip|Certificate Expiration|Your certificate will expire after 6 months. Then you have to request another one. Also everytime you request a new certificate, the old one is invalidated and cannot be used anymore.}}
The {{package|fedora-packager}} package provides tools to help you setup and work with fedora; it will bring in everything necessary for general packaging work. Run the following as root:
dnf install fedora-packager


The <code>fedora-packager</code> package provides tools to help you setup and work with fedora, therefore install it:
After installation set your Fedora Account System username in {{filename|~/.fedora.upn}} (do this as your normal user, not root).  You can do this via:
<code>
echo "yourfasid" > ~/.fedora.upn
yum install fedora-packager
(replacing "''yourfasid''", of course.)
</code>


After installation run it as your user to setup your koji configuration:
{{admon/tip|Kerberos|You will need to have a Kerberos ticket in order to use Koji. To get a ticket, use the following command in a Terminal: "kinit yourfasid@FEDORAPROJECT.ORG". The domain is case-sensitive, so keep FEDORAPROJECT.ORG upper case.<br /><br />
<code>
To configure this if using GNOME, see [[Infrastructure/Kerberos]]
fedora-packager-setup
}}
</code>
{{admon/tip|Certificate update|You will have to rerun <code>fedora-packager-setup</code> everytime you update your Fedora certificate.}}


You can now use "koji" to try to build your RPM packages on platforms (e.g., PPC) or distributions don't have.  Note that you can test out builds ("scratch" builds) even when your package hasn't been approved and you don't have a sponsor.  A simple way to do a scratch build using koji is to do this at the command line:
You can now use "koji" to try to build your RPM packages in the Fedora build system, even on platforms or Fedora versions you don't have.  Note that you can (and definitely should) test out builds ("scratch" builds) even before your package has been approved and you have been sponsored.  A simple way to do a scratch build using koji is to do this at the command line:
  koji build --arch-override=PLATFORM --scratch TARGET path_to_source_RPM
  koji build --scratch TARGET path_to_source_RPM
Where:
Where:
* TARGET is a distribution keyword such as dist-f9 (for Fedora 9).  You can run "koji list-targets" to see all targets.  To build for the next release (rawhide), ''don't'' use "dist-rawhide" - use "dist-fX" where X is one more than the latest stable release.
* TARGET is a distribution keyword such as f25 (for Fedora 25).  You can run "koji list-targets" to see all targets.  To build for the next release (rawhide), ''don't'' use "dist-rawhide" - use "fX" where X is one more than the latest stable or branched release.  
* PLATFORM is a platform keyword such as i386 (32-bit), x86_64, ppc, or ppc64. You can omit --arch-override=PLATFORM, in which case koji will do test builds on all the architectures the spec file says the package supports.
* Note that you need to supply the ''path'' to the source RPM (which ends in .src.rpm), and '''not''' a URL.  (If you only have the spec file, use <code>rpmbuild --nodeps -bs SPECFILE</code> to create the new source RPM).
* Note that you need to supply the ''path'' to the source RPM (which ends in .src.rpm), and '''not''' a URL.  (If you only have the spec file, use <code>rpmbuild --nodeps -bs SPECFILE</code> to create the new source RPM).


Your koji builds can only depend on packages that are actually in the TARGET distribution repository.  Thus, you can't use koji to build for released distributions if your package depends on other new packages that Bodhi hasn't released yet.  You ''can'' use koji to build for rawhide (the next unreleased version), even if it depends on other new packages, as long as the other packages were built in the CVS "devel" section as described below.  If you need to build against a package that is not yet a stable released
Your koji builds can only depend on packages that are actually in the TARGET distribution repository.  Thus, you can't use koji to build for released distributions if your package depends on other new packages that [[Bodhi | Bodhi]] hasn't released yet.  You ''can'' use koji to build for rawhide (the next unreleased version), even if it depends on other new packages, as long as the other packages were built for the "rawhide" as described below.  If you need to build against a package that is not yet a stable released
update, you can file a ticket with rel-eng at: https://fedorahosted.org/rel-eng/newticket and request that that package be
update, you can file a ticket with rel-eng at: https://pagure.io/releng/new_issue and request that that package is
added as a buildroot override. For packages in EPEL, you have to use the component ''epel'' to get the request to the right persons.
added as a buildroot override. For packages in EPEL, you have to use the component ''epel'' to get the request to the right persons.


Line 127: Line 136:
  koji COMMAND --help    # help on command COMMAND
  koji COMMAND --help    # help on command COMMAND


[[PackageMaintainers/UsingKoji]] has more information about using Koji.
[[Using the Koji build system]] has more information about using Koji.


=== Get Sponsored ===
== Adding a new package ==
 
=== Make a Package ===
 
* If you don't know how to create an RPM package, see the [https://docs.fedoraproject.org/en-US/quick-docs/creating-rpm-packages/index.html How to create an RPM package].
* Make sure that your package meets the [https://docs.fedoraproject.org/en-US/packaging-guidelines/ Packaging Guidelines] and [https://docs.fedoraproject.org/en-US/packaging-guidelines/Naming/ PackageNamingGuidelines] .
* Be aware of the [https://docs.fedoraproject.org/en-US/packaging-guidelines/ReviewGuidelines/ Package Review Guidelines] (they will be used during the package review).
* Make sure your package builds. This is surprisingly important because a significant number of submissions don't.


When the package is APPROVED by the reviewer, you must separately obtain member sponsorship in order to check in and build your package.  Sponsorship is not automatic and may require that you further participate in other ways in order to demonstrate your understanding of the packaging guidelines.  Key to becoming sponsored is to convince an existing sponsor-level member that you understand and follow the project's guidelines and processes.
=== Upload Your Package ===


See [[PackageMaintainers/HowToGetSponsored]] for more information on the process of becoming sponsored.
Upload your SRPM and SPEC files onto the Internet somewhere so that others can retrieve them. This can be anywhere accessible by a URL, but it is important that the files be directly accessible, not hidden behind some service that makes people wait to download things or redirects through advertising pages.


{{Admon/warning | First reviews for new packagers '''must''' be done by registered sponsors. Informal reviews can be done by anyone interested.}}
If you want to make ad-hoc builds available for users while you are getting the package into the official repositories, consider using [https://copr.fedorainfracloud.org Copr].  It is a lightweight automated build system that can create repositories using the SRPM you upload. You can use this Copr space to point reviewers to your src.rpm and spec.


Your sponsor can approve your request and move you from "pending" to "sponsored". You should receive email confirmation of your sponsorship.
{{Anchor|CreateYourReviewRequest}}


=== Add Package to CVS and Set Owner ===
=== Create Your Review Request ===


Follow [[PackageMaintainers/CVSAdminProcedure | CVSAdminProcedure]] to get a CVS module for your new package and branches for recent releases.
Fill out this form: https://bugzilla.redhat.com/bugzilla/enter_bug.cgi?product=Fedora&format=fedora-review.


This will be used to set up the proper records in the owners database, which is used for access to build the package, bugzilla population, and other featuresThis step creates a CVS module for your new package, with empty directories for each requested distribution.
* Before submitting your request, be sure there’s not a previous request for the same package.  There is a convenient search box on the [http://fedoraproject.org/PackageReviewStatus/ package review status page].
* Make sure that you put the '''name of the package''' (excluding version and release numbers) in the '<code>Review Summary</code>' field, along with a very '''brief summary''' of what the package is.
* Put a '''description''' of your package (usually, this can be the same thing as what you put in the spec %description) in the '<code>Review Description</code>' field.  Include the '''URLs''' to your '''SRPM''' and '''SPEC''' files.
* Explain in the ticket that this is your first package and you need a sponsor.  Also, include any information that may help prospective sponsors.  If you've been active in other review work, include linksIf you're the upstream maintainer, be sure to say so.
* For bonus points, include a link to a successful koji build so that everyone knows you did all of your homework.


=== Check out the module ===
{{Admon/warning | Make sure that you mention in the '<code>Review Description</code>' field that this is your first package, and you are seeking a sponsor. In Fedora Package Collection, all new contributors must be sponsored. Some potential sponsors will look at the [https://bugzilla.redhat.com/bugzilla/showdependencytree.cgi?id&#61;FE-NEEDSPONSOR FE-NEEDSPONSOR]  bug in Bugzilla to find packages to review. You can add your package to this list by editing your review request bug (which will be created once you click 'Commit' on the form) and adding <code>FE-NEEDSPONSOR</code> in the '<code>Blocks</code>' field.}}


You ''could'' check out your module now, but before doing that, consider doing "mkdir ~/cvs ; cd ~/cvs" - that way, all your files are inside that. Also, run ssh-add, so that you won't have to keep typing in your key password.
The review process is described in detail on the [[Package Review Process| Package Review Process]] page.


{{Admon/tip | Running <code>ssh-add</code> before doing any cvs operations is a very good idea. It will save you from having to type your key password for every operation. You only have to run ssh-add once per session, it will remember it until you log out or reboot. If "ssh-add" reports "Could not open a connection to your authentication agent.", start a new shell under it using "exec ssh-agent bash".}}
{{Anchor|WatchForFeedback}}


Now you are ready to checkout your module from CVS:
=== Inform Upstream ===
<pre>
 
fedora-cvs <packagename>
Fedora as a project prefers to [[Staying_close_to_upstream_projects | stay close to upstream]]. Inform the developers that you are packaging the software. You can do that by sending them an email introducing yourself and pointing out the review request. This sets up the stage for future conversations. They will usually advertise the fact that their software is now part of Fedora or might want to inform you of important bugs in the existing release, future roadmaps etc.
</pre>


Where <code><packagename></code> should be replaced with the name of your package.


You should now have a directory named after your package with a directory for each branch inside of it.
=== Watch for Feedback ===


{{Admon/caution | If this step fails, be sure your private ssh key (<code>~/.ssh/id_rsa</code>) mode is set to 0400. You might have to wait for up to an hour after your request for a new CVS module has been approved to get write access. Make sure your public key is the same as in the Fedora Accounts System (FAS). Key propagation may take an hour or so after uploading into FAS}}
Watch the Bugzilla report for your first package. You should get notifications of changes by email. Fix any blockers that the reviewer(s) point out.


You can use fedora-cvs with many modules at the same time.  To checkout from cvs run fedora-cvs {module names seperated by spaces}, for example:
{{Anchor|GetSponsored}}
<pre>
=== Get Sponsored ===
fedora-cvs konversation mysql-gui-tools snort
</pre>


=== Import Your Package ===
When the package is APPROVED by the reviewer, you must separately obtain member sponsorship in order to check in and build your package.  Sponsorship is not automatic and may require that you further participate in other ways in order to demonstrate your understanding of the packaging guidelines.  Key to becoming sponsored is to convince an existing sponsor-level member that you understand and follow the project's guidelines and processes.


Now that you've checked out your (empty) package module with fedora-cvs,
See [[how to get sponsored into the packager group]] for more information on the process of becoming sponsored.
cd into the module:
cd MODULE_NAME


Run the common/cvs-import.sh script, to import the contents of the SRPM into CVS:
Your sponsor can add you to the packager group. You should receive an email confirmation of your sponsorship.
./common/cvs-import.sh PATH_TO_SRPM


Obviously, replace <code>PATH_TO_SRPM</code> with the full path (not URL) to your approved SRPM.
=== Add Package to Source Code Management (SCM) system and Set Owner ===


This imports into only the '''devel''' branch.  You will probably ''also'' want to do additional imports using the -b parameter, which will import the package into other distribution branches like '''F-9''', e.g.:
Before proceeding, please sync your account by login on https://src.fedoraproject.org/ using your FAS credentials.
  ./common/cvs-import.sh -b F-9 PATH_TO_SRPM


The cvs-import.sh program will respond with:
If you are becoming a maintainer for a new package, instead of being a co-maintainer, use [https://pagure.io/fedpkg fedpkg] to request a new git repository for your package. The sub-command is "fedpkg request-repo" which includes help text for setting up the Pagure API token the command requires. When creating your API-key choose toogle-all for the ACLs. You must specify the repository name and review bug number. For example:
Checking out module: 'NAME'
  fedpkg request-repo python-prometheus_client  1590452
You may see errors like this several times, these can be ignored:
buffer_get_ret: trying to get more bytes 129 than in buffer 34
buffer_get_string_ret: buffer_get failed
buffer_get_bignum2_ret: invalid bignum
key_from_blob: can't read rsa key
key_read: key_from_blob AA.... failed
But among them you should see:
  Unpacking source package: NAME....src.rpm...
Along with a list of the source files in the source package,
followed by checking and uploading of the files.


Then, you'll see "If you want to make any changes before committing, please press Ctrl-C.
The request will be reviewed and processed by an admin, usually within 24 hours. Once the ticket is processed, you will have access to commit and build the package.
Otherwise press Enter to proceed to commit."  Press Enter.


Finally (if you haven't set up an other editor) vi will open up to let you edit the CVS changelog. For the changelog, use the same format as the end of the .spec file. If you haven't used vi yet, after entering your changelog press 'Enter' and type
Please that the "fedpkg request-repo" command only creates a branch for rawhide by default. To request branches for other Fedora releases, please use "fedpkg request-branch". For example:
   :wq
   fedpkg request-branch --repo python-prometheus_client f34
and press 'Enter' again to finish the import.


=== Tag Or Update Your Branches ===
You will need to run this for each non-rawhide branch. If you wish, you can also use the "--all-releases" flag to request branches for all current Fedora releases.


Branches are <code>F-</code># (formerly <code>FC-</code>#), <code>devel</code>, etc.  So ''F-9'' is the branch for Fedora 9.
=== Check out the module ===


Before a branch can be built in the Fedora Package build system, the files in that branch ''must'' be tagged in CVS.
You ''could'' check out your module now, but before doing that, consider doing <code>mkdir ~/fedora-scm ; cd ~/fedora-scm</code> - that way, all your files are inside a single directory.  Also, run <code>ssh-add</code>, so that you won't have to keep typing in your key password.


<!-- Found in https://bugzilla.redhat.com/show_bug.cgi?id=452559 -->
{{Admon/tip | Running <code>ssh-add</code> before doing any SCM operations is a very good idea. It will save you from having to type your key password for every operation. You only have to run <code>ssh-add</code> once per session, it will remember it until you log out or reboot. If <code>ssh-add</code> reports "Could not open a connection to your authentication agent.", start a new shell under it using <code>exec ssh-agent bash</code>.}}
The "import" command, described above, automatically tags the files. However, your local directory may not have exactly the right versions of the files, so go into the branch directory (e.g. <code>cd devel/</code> or <code>cd F-9/</code>) and run:
 
Now you are ready to checkout your module from the SCM:
<pre>
<pre>
  cvs up
  fedpkg clone <packagename>
</pre>
</pre>


The "import" script automatically tags the files. However, if you imported your files "by hand" or you're doing a release
Where <code><packagename></code> should be replaced with the name of your package.
bump after a final build failure, instead of using the "import" script, then you need to tag it yourself.
 
To tag it yourself, when you're happy with the source, go into the branch directory (e.g. <code>cd devel/</code>) and run:
{{Admon/caution | If this step fails, be sure your private ssh key (<code>~/.ssh/id_rsa</code>) mode is set to 0400. You might have to wait for up to an hour after your request for a new git module has been approved to get write access. Make sure your public key is the same as in the [[Account_System|Fedora Account System]] (FAS). Key propagation may take an hour or so after uploading into FAS.}}


<pre>
{{Admon/important| Note that fedpkg does not set the user config for your new git repo automatically. Make sure to have these set globally or locally in your new repo before you do your first commit (see [[Git_Quickref#Configure_your_global_git_settings|Configure your global git settings]]).}}
  make tag
{{Admon/important| Note: If you are not a member of the fedora packager group, you will receive a "permission denied" error. Use the <code>-a</code> flag to clone anonymously. }}
</pre>
 
=== Test Your Package ===
 
Refer to [[Using_Mock_to_test_package_builds]] and [[Using_the_Koji_build_system#Scratch_Builds]] for more information on testing your package.  Mock uses your local system while Koji command line tool uses the Fedora build system server. 
 
=== Import, commit, and build your package ===
 
Now that you've checked out your (empty) package module with fedpkg,
cd into the module's main branch:
cd <packagename>
Run fedpkg to import the contents of the SRPM into the SCM:
fedpkg import PATH_TO_SRPM
 
# Review Changes, press 'q' to stop; Revert with: git reset --hard HEAD
git commit -m "Initial import (#XXXXXX)."
git push
fedpkg build


You should see it tag the branch with the version and release from the SPEC file. You need to tag all of the branches that you want to build.
Obviously, replace <code>PATH_TO_SRPM</code> with the full path (not URL) to your approved SRPM, and <code>XXXXXX</code> with the package review bug number.


=== Request Builds ===
This imports into, commits, and builds only the '''main''' ([[Releases/Rawhide|Rawhide]])  branch. 


For each tagged branch that you'd like to request a build for, go into the branch directory (e.g. <code>cd devel/</code>) and run:
If the push fails with this kind of message:
W access for why DENIED to YOUR_ACCOUNT
fatal: The remote end hung up unexpectedly
Could not push: Command '['git', 'push']' returned non-zero exit status 128
Then you don't have the necessary rights to modify that package branch;
view https://src.fedoraproject.org/rpms/PACKAGE_NAME
to request those rights.


<pre>
For more information on using the Fedora package maintenance system, see the [[Package maintenance guide]].
make build
</pre>
{{Admon/warning | Be sure that you build for rawhide before pushing updates for any other branches! Otherwise, those updates will get inherited into rawhide, which is almost certainly not what you want.}}
{{Admon/warning | Sync to buildsys is an hourly thing. So, sometimes you might have to wait for an hour to get access of the build server to give "make build"}}
If everything goes well, it should queue up your branch for building, the package will cleanly build, and you're done!


If it fails to build, the build system will send you an email to report the failure and show you to the logs. Commit any needed changes to cvs, bump the SPEC release number, retag the branch, and request a new build.
=== Update Your Branches (if desired) ===


=== Submit Package as Update in Bodhi ===
Branches are <code>f</code># (formerly <code>F-</code># and before that <code>FC-</code>#), <code>main</code>, etc.  So ''f{{FedoraVersion}}'' is the branch for Fedora {{FedoraVersion}}.


The Fedora update system called Bodhi is used for pushing updates, classifying packages etc.
To switch to a branch first:
Do not submit "devel" (aka rawhide) packages via bodhi.
fedpkg switch-branch BRANCH (e.g. f{{FedoraVersion}})


At one time you could push an update using Bodhi via the command line using:
Merge the initial commit from main (Rawhide), creating an identical commit in the branch:
<pre>
git merge rawhide
make update
</pre>
<!-- On 2008-07-21 "make update" no longer works. -->


Now, if you want to use the command line, use the "bodhi" command as described in the [[Bodhi_Guide|Bodhi Guide]].
Push the changes to the server:
git push


You can also use [https://admin.fedoraproject.org/updates/new/ the Web interface for Bodhi] to request enhancement updates for each released Fedora you are bringing a new package to.
Build the package:
fedpkg build


The first field asks for the name of the "Package". This field will auto-complete the package name found in the Koji build system, e.g. <package-name>-<version>-<release>.fc9. If completion doesn't work, just enter the package build name yourself.
If there is another branch to work with repeat "To switch to a branch" and import and commit to each branch.


For new packages, choose "newpackage" as the "type" of update.
{{Admon/warning | Be sure that you build for rawhide (main) branch before pushing updates for any other branches! Otherwise, those updates will get inherited into rawhide, which is almost certainly not what you want.}}
{{Admon/warning | Sync to buildsys is an hourly thing. So, sometimes you might have to wait for an hour to get access of the build server to give "fedpkg build".}}
If everything goes well, it should queue up your branch for building, the package will cleanly build, and you're done!


Put the "Request" as "testing" if you want to put the package through testing first, see [[QA|  Fedora Quality Assurance]] . Put "stable" if you want to push the package directly to stable.
If it fails to build, the build system will send you an email to report the failure and show you to the logs. Commit any needed changes to git, bump the SPEC release number, and request a new build.


Put the bug number of the package's Review Request in the "Bugs" field blank. Bodhi will automatically close it as NEXTRELEASE when it gets pushed to the requested update status.
=== Submit Package as Update in Bodhi ===


For new packages, add a copy of the package's description in the "Notes" section, so end users will know what the package is.
The Fedora update system called [[Bodhi]] is used for pushing updates, classifying packages etc. Do not submit Rawhide (main branch) builds via Bodhi.


Here is the [[Bodhi_Guide|Bodhi Guide]] and
You can push an update using Bodhi via the command line using this in each branch:
[[Infrastructure/UpdatesSystem/Bodhi-info-DRAFT|more information on Bodhi]] .
fedpkg update


After you have submitted an upgrade through bodhi, your package is placed in a queue. Periodically, an administrator will check the queue and push all of the packages into the appropriate repositories.
See the [[Package_update_HOWTO|update submission guide]] for more details.


=== Make the package available in "comps" files ===
=== Make the package available in "comps" files ===


If appropriate for the package, make it available in "comps" files so that it can be selected during installation and included in yum's package group operations.  See [[PackageMaintainers/CompsXml]] for more info.
If appropriate for the package, make it available in "comps" files so that it can be selected during installation and included in dnf's|yum's package group operations.  See [[PackageMaintainers/CompsXml|How to use and edit comps.xml for package groups]] for more info.
 
=== Watch for updates ===
 
Fedora has the infrastructure available for monitoring new upstream releases of the software you are packaging. Refer to [[Upstream Release Monitoring]] for more details.


== Getting Help  ==
== Getting Help  ==


We know that this process can be as clear as mud sometimes, and we're always trying to make it better. If you run into any problems, or have any questions, please ask on the [https://www.redhat.com/mailman/listinfo/fedora-devel-list fedora-devel-list]  mailing list or in #fedora-devel on [http://freenode.net/ freenode] . See the [[Communicate]] page for details.
We know that this process can be as clear as mud sometimes, and we're always trying to make it better. If you run into any problems, or have any questions, please ask on the {{fplist|devel}} mailing list or in {{fpchat|#fedora-devel}} on [https://libera.chat/ Libera].


The Fedora Mentors Project has people willing to help new contributors in their packaging efforts. See the [[Mentors]] page for more information.
== Getting a new package into Fedora Package Collection for existing maintainers ==


See also the [[using CVS FAQ for package maintainers|CVS FAQ]]
If you already maintain a package in Fedora and want to maintain another, follow the [[new package process for existing contributors]].


== Getting a new package into Fedora Package Collection for existing maintainers  ==
== One-off contributions ==


If you already maintain a package in Fedora and want to maintain another, follow the [[PackageMaintainers/NewPackageProcess|  new package process]] .
Changes to [https://src.fedoraproject.org/browse/projects/ existing packages] can be suggested by submitting [https://docs.pagure.org/pagure/usage/pull_requests.html pull requests].
You must have a [[Join_the_package_collection_maintainers#Create_a_Fedora_Account|Fedora account]] to create a pull request. See [[Package_maintenance_guide#Using_fedpkg_anonymously]] for instructions and [[Infrastructure/HTTPS-commits]] for more information.


[[Category:Package Maintainers]] [[Category:Join]]
[[Category:Package Maintainers]] [[Category:Join]]

Revision as of 10:25, 9 July 2021

Contributing roles

Idea.png
Contributing roles
These are only suggestions for contributing roles. Only your imagination sets the limits.

Join OSDeveloper.png
OS Developer

How to join the Fedora Package Collection Maintainers?

So, you have decided to become a package maintainer in the Fedora Project? This guide will lead you through your first package submission. It can be a completely new package, or update to an existing package.

Fedora-submit-package.png

Preparation

Read the Guidelines

If you don't know how to create an RPM package, refer to the tutorial at How to create a GNU Hello RPM package or the more advanced and much more detailed Creating RPM packages.

Read the Packaging Guidelines and Package Naming Guidelines.

You need to be thoroughly familiar with these. They govern all package submissions. If you have questions, ask on the Fedora packaging List.

Create a Bugzilla Account

Make sure you have an account in Red Hat Bugzilla .

The email address that you use for your Bugzilla account should be the same email address as you use in the Fedora Account System for all things related to Fedora Packaging.

Important.png
Do not use your @fedoraproject.org address if you already have one.
You should not use your @fedoraproject.org email address in Bugzilla, because you will not get your Bugzilla privileges once you are sponsored. If you want to use your @fedoraproject.org address, you might try to request at the Fedora Infrastructure Ticket System for an administrator to manually override the Bugzilla address connected with your Fedora Account.

Create a Fedora Account

Create an account in the Fedora Account System (this is not the same as the Bugzilla account)

  1. Visit the account system home: https://accounts.fedoraproject.org/
  2. Click on 'New account' and fill in the blanks. Note that the email you give should be the same as the one you gave Bugzilla. This allows the system to link privileges between the two accounts.
  3. After you create your account, please be sure to agree to the FPCA (if you click on the "edit profile" link on the right, then the 'Agreements' tab. If this says 'view' you have agreed already, if it says 'sign' you still need to agree).
  4. You will also need to upload a public SSH key. You need to use the matching private key to access Fedora machines via SSH. You can read more about this here.

Join the important Mailing Lists

You should join the fedora devel-announce mailing list. It is a low traffic announcements only list, where important development information is posted.

You should join the fedora devel mailing list, where discussions about the development of Fedora are held. This is a high traffic mailing list.

You should also consider joining the package-announce mailing list -- The commits mailing list gets notifications on all commits in any package in the Fedora repository. This is a very high traffic mailing list. The Fedora package database sends commit mails for packages you (co-)maintain.

Another mailing list you might consider (at least to view the archives) is packaging. This is the mailing list of the Fedora Packaging Committee, who determine the official packaging guidelines for Fedora projects.

Introduce yourself

Next, you should introduce yourself to the community on the devel mailing list. The primary purpose of this is to begin the process of building trust by allowing the Fedora community members to get to know you a bit more.

We want to break anonymity and foster real-world community within the project. You are under no obligation to reveal personal secrets. The objective is to establish a level of trust between yourself and the other members of the project. But you should at least use your real name when communicating with us. Also, a brief description of who you are, your motivations and perhaps a description of the software you have submitted for review are advisable.


Subject: Self Introduction:  <Your name>

Body:  Add any information you believe is applicable 
including past experience in free and open source projects, 
a link to the review request you have filed and 
a brief description of yourself. You can also post 
your GPG key information if you want to.

Feel free to participate in all the discussion that goes on in any of the lists. Community discussion and feedback is always encouraged.

Find software you wish to package/maintain for Fedora

Note.png
Note that there's other methods for getting sponsored into the packager group than submitting a new package. Check the How to get sponsored page for more info.

The package you are submitting can be of any Free and Open Source project that is not already packaged in Fedora. Before creating your package, make sure that the software is not already in the Fedora repository, or waiting for review.

Understand your responsibilities

Software components included in Fedora need to be maintained actively, and bugs - especially security issues - need to be fixed in a timely manner. As a Fedora package maintainer, it is your primary responsibility to ensure this. We encourage you to get co-maintainers and seek the help of the Fedora community via the development mailing list whenever needed.

Read Other Submissions

Read some other package submissions to learn about packaging and gain familiarity with the process and requirements.

One way of doing this is to join the package-review mailing list;All comments on Fedora package reviews are sent to this (read-only from your point of view) list.

Configure Your Git

The first thing to do when you set up Fedora packaging is to configure your username and email address for Git. These are linked in each commit you do to Fedora packages.

git config --global user.name "John Doe"
git config --global user.email johndoe@example.com

Install the developer client tools

To build Packages for the Fedora Collection or EPEL in the Fedora build system you need Koji.

The Package-x-generic-16.pngfedora-packager package provides tools to help you setup and work with fedora; it will bring in everything necessary for general packaging work. Run the following as root:

dnf install fedora-packager

After installation set your Fedora Account System username in ~/.fedora.upn (do this as your normal user, not root). You can do this via:

echo "yourfasid" > ~/.fedora.upn

(replacing "yourfasid", of course.)

Idea.png
Kerberos
You will need to have a Kerberos ticket in order to use Koji. To get a ticket, use the following command in a Terminal: "kinit yourfasid@FEDORAPROJECT.ORG". The domain is case-sensitive, so keep FEDORAPROJECT.ORG upper case.

To configure this if using GNOME, see Infrastructure/Kerberos

You can now use "koji" to try to build your RPM packages in the Fedora build system, even on platforms or Fedora versions you don't have. Note that you can (and definitely should) test out builds ("scratch" builds) even before your package has been approved and you have been sponsored. A simple way to do a scratch build using koji is to do this at the command line:

koji build --scratch TARGET path_to_source_RPM

Where:

  • TARGET is a distribution keyword such as f25 (for Fedora 25). You can run "koji list-targets" to see all targets. To build for the next release (rawhide), don't use "dist-rawhide" - use "fX" where X is one more than the latest stable or branched release.
  • Note that you need to supply the path to the source RPM (which ends in .src.rpm), and not a URL. (If you only have the spec file, use rpmbuild --nodeps -bs SPECFILE to create the new source RPM).

Your koji builds can only depend on packages that are actually in the TARGET distribution repository. Thus, you can't use koji to build for released distributions if your package depends on other new packages that Bodhi hasn't released yet. You can use koji to build for rawhide (the next unreleased version), even if it depends on other new packages, as long as the other packages were built for the "rawhide" as described below. If you need to build against a package that is not yet a stable released update, you can file a ticket with rel-eng at: https://pagure.io/releng/new_issue and request that that package is added as a buildroot override. For packages in EPEL, you have to use the component epel to get the request to the right persons.

You can learn more about koji via:

koji --help            # General help
koji --help-commands   # list of koji commands
koji COMMAND --help    # help on command COMMAND

Using the Koji build system has more information about using Koji.

Adding a new package

Make a Package

Upload Your Package

Upload your SRPM and SPEC files onto the Internet somewhere so that others can retrieve them. This can be anywhere accessible by a URL, but it is important that the files be directly accessible, not hidden behind some service that makes people wait to download things or redirects through advertising pages.

If you want to make ad-hoc builds available for users while you are getting the package into the official repositories, consider using Copr. It is a lightweight automated build system that can create repositories using the SRPM you upload. You can use this Copr space to point reviewers to your src.rpm and spec.

Create Your Review Request

Fill out this form: https://bugzilla.redhat.com/bugzilla/enter_bug.cgi?product=Fedora&format=fedora-review.

  • Before submitting your request, be sure there’s not a previous request for the same package. There is a convenient search box on the package review status page.
  • Make sure that you put the name of the package (excluding version and release numbers) in the 'Review Summary' field, along with a very brief summary of what the package is.
  • Put a description of your package (usually, this can be the same thing as what you put in the spec %description) in the 'Review Description' field. Include the URLs to your SRPM and SPEC files.
  • Explain in the ticket that this is your first package and you need a sponsor. Also, include any information that may help prospective sponsors. If you've been active in other review work, include links. If you're the upstream maintainer, be sure to say so.
  • For bonus points, include a link to a successful koji build so that everyone knows you did all of your homework.
Warning.png
Make sure that you mention in the 'Review Description' field that this is your first package, and you are seeking a sponsor. In Fedora Package Collection, all new contributors must be sponsored. Some potential sponsors will look at the FE-NEEDSPONSOR bug in Bugzilla to find packages to review. You can add your package to this list by editing your review request bug (which will be created once you click 'Commit' on the form) and adding FE-NEEDSPONSOR in the 'Blocks' field.

The review process is described in detail on the Package Review Process page.

Inform Upstream

Fedora as a project prefers to stay close to upstream. Inform the developers that you are packaging the software. You can do that by sending them an email introducing yourself and pointing out the review request. This sets up the stage for future conversations. They will usually advertise the fact that their software is now part of Fedora or might want to inform you of important bugs in the existing release, future roadmaps etc.


Watch for Feedback

Watch the Bugzilla report for your first package. You should get notifications of changes by email. Fix any blockers that the reviewer(s) point out.

Get Sponsored

When the package is APPROVED by the reviewer, you must separately obtain member sponsorship in order to check in and build your package. Sponsorship is not automatic and may require that you further participate in other ways in order to demonstrate your understanding of the packaging guidelines. Key to becoming sponsored is to convince an existing sponsor-level member that you understand and follow the project's guidelines and processes.

See how to get sponsored into the packager group for more information on the process of becoming sponsored.

Your sponsor can add you to the packager group. You should receive an email confirmation of your sponsorship.

Add Package to Source Code Management (SCM) system and Set Owner

Before proceeding, please sync your account by login on https://src.fedoraproject.org/ using your FAS credentials.

If you are becoming a maintainer for a new package, instead of being a co-maintainer, use fedpkg to request a new git repository for your package. The sub-command is "fedpkg request-repo" which includes help text for setting up the Pagure API token the command requires. When creating your API-key choose toogle-all for the ACLs. You must specify the repository name and review bug number. For example:

fedpkg request-repo python-prometheus_client  1590452

The request will be reviewed and processed by an admin, usually within 24 hours. Once the ticket is processed, you will have access to commit and build the package.

Please that the "fedpkg request-repo" command only creates a branch for rawhide by default. To request branches for other Fedora releases, please use "fedpkg request-branch". For example:

 fedpkg request-branch --repo python-prometheus_client f34

You will need to run this for each non-rawhide branch. If you wish, you can also use the "--all-releases" flag to request branches for all current Fedora releases.

Check out the module

You could check out your module now, but before doing that, consider doing mkdir ~/fedora-scm ; cd ~/fedora-scm - that way, all your files are inside a single directory. Also, run ssh-add, so that you won't have to keep typing in your key password.

Idea.png
Running ssh-add before doing any SCM operations is a very good idea. It will save you from having to type your key password for every operation. You only have to run ssh-add once per session, it will remember it until you log out or reboot. If ssh-add reports "Could not open a connection to your authentication agent.", start a new shell under it using exec ssh-agent bash.

Now you are ready to checkout your module from the SCM:

 fedpkg clone <packagename>

Where <packagename> should be replaced with the name of your package.

Stop (medium size).png
If this step fails, be sure your private ssh key (~/.ssh/id_rsa) mode is set to 0400. You might have to wait for up to an hour after your request for a new git module has been approved to get write access. Make sure your public key is the same as in the Fedora Account System (FAS). Key propagation may take an hour or so after uploading into FAS.
Important.png
Note that fedpkg does not set the user config for your new git repo automatically. Make sure to have these set globally or locally in your new repo before you do your first commit (see Configure your global git settings).
Important.png
Note: If you are not a member of the fedora packager group, you will receive a "permission denied" error. Use the -a flag to clone anonymously.

Test Your Package

Refer to Using_Mock_to_test_package_builds and Using_the_Koji_build_system#Scratch_Builds for more information on testing your package. Mock uses your local system while Koji command line tool uses the Fedora build system server.

Import, commit, and build your package

Now that you've checked out your (empty) package module with fedpkg, cd into the module's main branch:

cd <packagename>

Run fedpkg to import the contents of the SRPM into the SCM:

fedpkg import PATH_TO_SRPM
# Review Changes, press 'q' to stop; Revert with: git reset --hard HEAD
git commit -m "Initial import (#XXXXXX)."
git push
fedpkg build

Obviously, replace PATH_TO_SRPM with the full path (not URL) to your approved SRPM, and XXXXXX with the package review bug number.

This imports into, commits, and builds only the main (Rawhide) branch.

If the push fails with this kind of message:

W access for why DENIED to YOUR_ACCOUNT
fatal: The remote end hung up unexpectedly
Could not push: Command '['git', 'push']' returned non-zero exit status 128

Then you don't have the necessary rights to modify that package branch; view https://src.fedoraproject.org/rpms/PACKAGE_NAME to request those rights.

For more information on using the Fedora package maintenance system, see the Package maintenance guide.

Update Your Branches (if desired)

Branches are f# (formerly F-# and before that FC-#), main, etc. So f39 is the branch for Fedora 39.

To switch to a branch first:

fedpkg switch-branch BRANCH (e.g. f39)

Merge the initial commit from main (Rawhide), creating an identical commit in the branch:

git merge rawhide

Push the changes to the server:

git push

Build the package:

fedpkg build

If there is another branch to work with repeat "To switch to a branch" and import and commit to each branch.

Warning.png
Be sure that you build for rawhide (main) branch before pushing updates for any other branches! Otherwise, those updates will get inherited into rawhide, which is almost certainly not what you want.
Warning.png
Sync to buildsys is an hourly thing. So, sometimes you might have to wait for an hour to get access of the build server to give "fedpkg build".

If everything goes well, it should queue up your branch for building, the package will cleanly build, and you're done!

If it fails to build, the build system will send you an email to report the failure and show you to the logs. Commit any needed changes to git, bump the SPEC release number, and request a new build.

Submit Package as Update in Bodhi

The Fedora update system called Bodhi is used for pushing updates, classifying packages etc. Do not submit Rawhide (main branch) builds via Bodhi.

You can push an update using Bodhi via the command line using this in each branch:

fedpkg update

See the update submission guide for more details.

Make the package available in "comps" files

If appropriate for the package, make it available in "comps" files so that it can be selected during installation and included in dnf's|yum's package group operations. See How to use and edit comps.xml for package groups for more info.

Watch for updates

Fedora has the infrastructure available for monitoring new upstream releases of the software you are packaging. Refer to Upstream Release Monitoring for more details.

Getting Help

We know that this process can be as clear as mud sometimes, and we're always trying to make it better. If you run into any problems, or have any questions, please ask on the devel mailing list or in #fedora-devel[?] on Libera.

Getting a new package into Fedora Package Collection for existing maintainers

If you already maintain a package in Fedora and want to maintain another, follow the new package process for existing contributors.

One-off contributions

Changes to existing packages can be suggested by submitting pull requests. You must have a Fedora account to create a pull request. See Package_maintenance_guide#Using_fedpkg_anonymously for instructions and Infrastructure/HTTPS-commits for more information.