- 1 貢献という役割
- 2 Fedora パッケージコレクションメンテナへの参加方法
- 2.1 Fedora パッケージコレクションメンテナになる
- 2.1.1 ガイドラインを読む
- 2.1.2 Bugzilla アカウントを作成する
- 2.1.3 重要なメーリングリストへ参加する
- 2.1.4 パッケージが適切なものだと保証する
- 2.1.5 他の提案を読む
- 2.1.6 パッケージを作る
- 2.1.7 パッケージをアップロードする
- 2.1.8 レビューリクエストを作成する
- 2.1.9 アップストリームへ知らせる
- 2.1.10 フィードバックを監視する
- 2.1.11 Fedora アカウントを取得する
- 2.1.12 クライアントツール(Koji)をインストールする
- 2.1.13 スポンサーを得る
- 2.1.14 ソースコード管理(SCM)システムへパッケージを追加して所有者をセットする
- 2.1.15 そのモジュールをチェックアウトする
- 2.1.16 パッケージをインポートする
- 2.1.17 ブランチを更新する
- 2.1.18 ビルドをリクエストする
- 2.1.19 Bodhi へ至るものとしてパッケージを投稿する
- 2.1.20 パッケージを "comps" ファイルで利用可能状態にする
- 2.1.21 アップデートを監視する
- 2.2 ヘルプを取得する
- 2.3 既存のメンテナのために Fedora パッケージコレクションに新たなパッケージを入れる
- 2.1 Fedora パッケージコレクションメンテナになる
So, you have decided to become a package maintainer in the Fedora Project? This guide will lead you through your first package submission.
You need to be thoroughly familiar with these. They govern all package submissions. If you have questions, ask on the Fedora Packaging List .
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.
You must join the fedora firstname.lastname@example.org mailing list. It is a low traffic announcements only list, where important development information is posted.
You can join the fedora email@example.com mailing list, where discussions about the development of Fedora are held. This is a high traffic mailing list.
You can also consider joining the firstname.lastname@example.org 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 email@example.com. This is the mailing list of the Fedora Packaging Committee, who determine the official packaging guidelines for Fedora projects.
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.
- Search the Fedora Package Database for packages already in the repository.
- Search in the Review Tracker for packages under review.
- Also check the retired package list.
- Be aware of forbidden items.
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 firstname.lastname@example.org mailing list ; all comments on Fedora package reviews are sent to this (read-only from your point of view) list.
- If you don't know how to create an RPM package, see the How to create an RPM package.
- Make sure that your package meets the Packaging Guidelines and PackageNamingGuidelines .
- Be aware of the Package Review Guidelines (they will be used during the package review).
Upload your SRPM and SPEC files onto the Internet somewhere. This can be anywhere accessible by a URL. If you have already got a Fedora Account then you can use your storage at http://fedorapeople.org for this.
- Before submitting your request, be sure there’s no a previous request for the same package.
- 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.
- 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 '
Review Description' field. Include the URLs to your SRPM and SPEC files. Also, explain that this is your first package and you need a sponsor.
The review process is described in detail on the Package Review Process page.
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 a 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 the Bugzilla report for your first package. You should get notifications of changes by email. Fix any blockers that the reviewer(s) point out.
Create an account in the Fedora Account System (this is not just a bugzilla account)
- Visit the account system home: https://admin.fedoraproject.org/accounts/
- Click on 'New account' and fill in the blanks.
- 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)
Note: Red Hat employees should apply for
cla_redhatinstead. From the Account System, Apply for a New Group, put
cla_redhatin the group field, and click Apply. Then ask TomCallaway to approve you.
To build Packages for the Fedora Collection or EPEL, you need Koji.
You'll also need to generate a client side certificate at the Fedora Account System and save the file in
fedpkg will look for it by default.
fedora-packager package provides tools to help you setup and work with fedora, therefore install it:
yum install fedora-packager
After installation run it as your user to setup your koji configuration:
You can now use "koji" to try to build your RPM packages on platforms (e.g., PPC) or distributions you 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:
koji build --arch-override=PLATFORM --scratch TARGET path_to_source_RPM
- 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.
- 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
rpmbuild --nodeps -bs SPECFILEto 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://fedorahosted.org/rel-eng/newticket and request that that package be 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.
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 email confirmation of your sponsorship.
Follow Package SCM admin requests to get a module for your new package and branches for recent releases.
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 features. This step creates a module in the repository your new package, with branches for each requested distribution.
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 that. Also, run ssh-add, so that you won't have to keep typing in your key password.
Now you are ready to checkout your module from the SCM:
fedpkg clone -B <packagename>
<packagename> 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.
Now that you've checked out your (empty) package module with fedkpkg, cd into the module:
Run the fedpkg, to import the contents of the SRPM into the SCM:
fedpkg import PATH_TO_SRPM (Review Changes) fedpkg commit -p
PATH_TO_SRPM with the full path (not URL) to your approved SRPM.
This imports into only the master (rawhide) 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.:
./common/cvs-import.sh -b F-9 PATH_TO_SRPM
The cvs-import.sh program will respond with:
Checking out module: 'NAME'
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. 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 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
and press 'Enter' again to finish the import.
F-# and before that
master, etc. So f13 is the branch for Fedora 13.
However, your local directory may not have exactly the right versions of the files, so go into the branch directory (e.g.
cd devel/ or
cd f12/) and run:
For each branch that you'd like to request a build for, go into the branch directory (e.g.
cd f13/) and run:
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, and request a new build.
The Fedora update system called Bodhi is used for pushing updates, classifying packages etc. Do not submit "master" (aka rawhide) packages via bodhi.
You can push an update using Bodhi via the command line using:
You can also use "bodhi" command directly as described in the Bodhi Guide.
You can also use the Web interface for Bodhi to request enhancement updates for each released Fedora you are bringing a new package to.
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.
For new packages, choose "newpackage" as the "type" of update.
Put the "Request" as "testing" if you want to put the package through testing first, see Fedora Quality Assurance . Put "stable" if you want to push the package directly to stable.
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.
For new packages, add a copy of the package's description in the "Notes" section, so end users will know what the package is.
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.
パッケージを "comps" ファイルで利用可能状態にする
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.
Fedora has infrastructure available for monitoring new upstream releases of the software you are packaging. Refer to Upstream Release Monitoring for more details. Learn to handle updates by reading the Package update HOWTO
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 email@example.com mailing list or in #fedora-devel on freenode . See the Communicate page for details.
The Fedora Mentors Project has people willing to help new contributors in their packaging efforts. See the Mentors page for more information.
See also using git FAQ for package maintainers.
既存のメンテナのために Fedora パッケージコレクションに新たなパッケージを入れる
If you already maintain a package in Fedora and want to maintain another, follow the new package process for existing contributors .