Fedora - Packit – auto-package your projects into Fedora

Fedora - Packit – auto-package your projects into Fedora - Printable Version

+- Sick Gaming (https://www.sickgaming.net)
+-- Forum: Computers (https://www.sickgaming.net/forum-86.html)
+--- Forum: Linux, FreeBSD, and Unix types (https://www.sickgaming.net/forum-88.html)
+--- Thread: Fedora - Packit – auto-package your projects into Fedora (/thread-90500.html)

Fedora - Packit – auto-package your projects into Fedora - xSicKxBot - 05-25-2019

Packit – auto-package your projects into Fedora

<div style="margin: 5px 5% 10px 5%;"><img src="http://www.sickgaming.net/blog/wp-content/uploads/2019/05/packit-auto-package-your-projects-into-fedora.png" width="1024" height="781" title="" alt="" /></div><div>
<h2>What is packit</h2>
Packit (<a href="https://packit.dev/">https://packit.dev/)</a> is a CLI tool that helps you auto-package your upstream projects into the Fedora operating system. But what does it really mean? 
As a developer, you might want to add or update your package in Fedora. If you’ve done it in the past, you know it’s no easy task. If you haven’t let me reiterate: it’s no easy task.
And this is exactly where packit can help: with just one configuration file in your upstream repository, packit will automatically package your software into Fedora and update it when you update your source code upstream.
Furthermore, packit can synchronize downstream changes to a SPEC file back into the upstream repository. This could be useful if the SPEC file of your package is changed in Fedora repositories and you would like to synchronize it into your upstream project.
Packit also provides a way to build an SRPM package based on an upstream repository checkout, which can be used for building RPM packages in COPR.
Last but not least, packit provides a status command. This command provides information about upstream and downstream repositories, like pull requests, release and more others.
Packit provides also another two commands: build and create-update.
The command packit build performs a production build of your project in Fedora build system – koji. You can Fedora version you want to build against using an option –dist-git-branch. The command packit create-updates creates a Bodhi update for the specific branch using the option —dist-git-branch. 
<h2>Installation</h2>
You can install packit on Fedora using dnf:
<pre class="wp-block-preformatted">sudo dnf install -y packit</pre>
<h2>Configuration</h2>
For demonstration use case, I have selected the upstream repository of colin (<a href="https://github.com/user-cont/colin">https://github.com/user-cont/colin)</a>. Colin is a tool to check generic rules and best-practices for containers, dockerfiles, and container images. 
First of all, clone colin git repository:
<pre class="wp-block-preformatted">$ git clone https://github.com/user-cont/colin.git $ cd colin</pre>
Packit expects to run in the root of your git repository.
Packit (<a href="https://github.com/packit-service/packit/">https://github.com/packit-service/packit/)</a> needs information about your project, which has to be stored in the upstream repository in the .packit.yaml file (<a href="https://github.com/packit-service/packit/blob/master/docs/configuration.md#projects-configuration-file">https://github.com/packit-service/packit/blob/master/docs/configuration.md#projects-configuration-file</a>).
See colin’s packit configuration file:
<pre class="wp-block-preformatted">$ cat .packit.yaml specfile_path: colin.spec synced_files:  -.packit.yaml  - colin.spec upstream_project_name: colin downstream_package_name: colins</pre>
What do the values mean?
<ul>
<li>specfile_path – a relative path to a spec file within the upstream repository (mandatory)</li>
<li>synced_files – a list of relative paths to files in the upstream repo which are meant to be copied to dist-git during an update</li>
<li>upstream_project_name – name of the upstream repository (e.g. in PyPI); this is used in %prep section</li>
<li>downstream_package_name – name of the package in Fedora (mandatory)</li>
</ul>
For more information see the packit configuration documentation (<a href="https://github.com/packit-service/packit/blob/master/docs/configuration.md">https://github.com/packit-service/packit/blob/master/docs/configuration.md</a>)
<h2>What can packit do?</h2>
Prerequisite for using packit is that you are in a working directory of a git checkout of your upstream project.
Before running any packit command, you need to do several actions. These actions are mandatory for filing a PR into the upstream or downstream repositories and to have access into the Fedora dist-git repositories.
Export GitHub token taken from <a href="https://github.com/settings/tokens">https://github.com/settings/tokens</a>:
<pre class="wp-block-preformatted">$ export GITHUB_TOKEN=<YOUR_TOKEN> </pre>
Obtain your Kerberos ticket needed for Fedora Account System (FAS) :
<pre class="wp-block-preformatted">$ kinit <yourname>@FEDORAPROJECT.ORG </pre>
Export your Pagure API keys taken from <a href="https://src.fedoraproject.org/settings#nav-api-tab">https://src.fedoraproject.org/settings#nav-api-tab</a>:
<pre class="wp-block-preformatted">$ export PAGURE_USER_TOKEN=<PAGURE_USER_TOKEN> </pre>
Packit also needs a fork token to create a pull request. The token is taken from <a href="https://src.fedoraproject.org/fork/YOU/rpms/PACKAGE/settings#apikeys-tab">https://src.fedoraproject.org/fork/YOU/rpms/PACKAGE/settings#apikeys-tab</a>
Do it by running:
<pre class="wp-block-preformatted">$ export PAGURE_FORK_TOKEN=<PAGURE_FORK_TOKEN> </pre>
Or store these tokens in the ~/.config/packit.yaml file:
<pre class="wp-block-preformatted">$ cat ~/.config/packit.yaml github_token: <GITHUB_TOKEN> pagure_user_token: <PAGURE_USER_TOKEN> pagure_fork_token: <PAGURE_FORK_TOKEN> </pre>
<h3>Propose a new upstream release in Fedora</h3>
The command for this first use case is called propose-update (<a href="https://github.com/jpopelka/packit/blob/master/docs/propose_update.md">https://github.com/jpopelka/packit/blob/master/docs/propose_update.md</a>). The command creates a new pull request in Fedora dist-git repository using a selected or the latest upstream release.
<pre class="wp-block-preformatted">$ packit propose-update INFO: Running 'anitya' versioneer Version in upstream registries is '0.3.1'. Version in spec file is '0.3.0'. WARNING  Version in spec file is outdated Picking version of the latest release from the upstream registry. Checking out upstream version 0.3.1 Using 'master' dist-git branch Copying /home/vagrant/colin/colin.spec to /tmp/tmptfwr123c/colin.spec. Archive colin-0.3.0.tar.gz found in lookaside cache (skipping upload). INFO: Downloading file from URL https://files.pythonhosted.org/packages/source/c/colin/colin-0.3.0.tar.gz 100%[=============================>]     3.18M  eta 00:00:00 Downloaded archive: '/tmp/tmptfwr123c/colin-0.3.0.tar.gz' About to upload to lookaside cache won't be doing kinit, no credentials provided PR created: https://src.fedoraproject.org/rpms/colin/pull-request/14</pre>
Once the command finishes, you can see a PR in the Fedora Pagure instance which is based on the latest upstream release. Once you review it, it can be merged.
<figure class="wp-block-image"><img src="http://www.sickgaming.net/blog/wp-content/uploads/2019/05/packit-auto-package-your-projects-into-fedora.png" alt="" class="wp-image-28017" /></figure>
<h3>Sync downstream changes back to the upstream repository</h3>
Another use case is to sync downstream changes into the upstream project repository.
The command for this purpose is called sync-from-downstream (<a href="https://github.com/jpopelka/packit/blob/master/docs/sync-from-downstream.md">https://github.com/jpopelka/packit/blob/master/docs/sync-from-downstream.md</a>). Files synced into the upstream repository are mentioned in the packit.yaml configuration file under the synced_files value.
<pre class="wp-block-preformatted">$ packit sync-from-downstream upstream active branch master using "master" dist-git branch Copying /tmp/tmplvxqtvbb/colin.spec to /home/vagrant/colin/colin.spec. Creating remote fork-ssh with URL [email protected]:phracek/colin.git. Pushing to remote fork-ssh using branch master-downstream-sync. PR created: <a href="https://github.com/user-cont/colin/pull/229">https://github.com/user-cont/colin/pull/229</a></pre>
As soon as packit finishes, you can see the latest changes taken from the Fedora dist-git repository in the upstream repository. This can be useful, e.g. when Release Engineering performs mass-rebuilds and they update your SPEC file in the Fedora dist-git repository.
<figure class="wp-block-image"><img src="http://www.sickgaming.net/blog/wp-content/uploads/2019/05/packit-auto-package-your-projects-into-fedora-1.png" alt="" class="wp-image-28019" /></figure>
<h3>Get the status of your upstream project</h3>
If you are a developer, you may want to get all the information about the latest releases, tags, pull requests, etc. from the upstream and the downstream repository. Packit provides the status command for this purpose.
<pre class="wp-block-preformatted">$ packit status Downstream PRs:  ID  Title                             URL ----  --------------------------------  ---------------------------------------------------------  14  Update to upstream release 0.3.1  <a href="https://src.fedoraproject.org//rpms/colin/pull-request/14">https://src.fedoraproject.org//rpms/colin/pull-request/14</a>  12  Upstream pr: 226                  <a href="https://src.fedoraproject.org//rpms/colin/pull-request/12">https://src.fedoraproject.org//rpms/colin/pull-request/12</a>  11  Upstream pr: 226                  <a href="https://src.fedoraproject.org//rpms/colin/pull-request/11">https://src.fedoraproject.org//rpms/colin/pull-request/11</a>   8 Upstream pr: 226                  <a href="https://src.fedoraproject.org//rpms/colin/pull-request/8">https://src.fedoraproject.org//rpms/colin/pull-request/8</a> Dist-git versions: f27: 0.2.0 f28: 0.2.0 f29: 0.2.0 f30: 0.2.0 master: 0.2.0 GitHub upstream releases: 0.3.1 0.3.0 0.2.1 0.2.0 0.1.0 Latest builds: f27: colin-0.2.0-1.fc27 f28: colin-0.3.1-1.fc28 f29: colin-0.3.1-1.fc29 f30: colin-0.3.1-2.fc30 Latest bodhi updates: Update                Karma  status ------------------  ------- -------- colin-0.3.1-1.fc29        1  stable colin-0.3.1-1.fc28        1  stable colin-0.3.0-2.fc28        0  obsolete</pre>
<h3>Create an SRPM</h3>
The last packit use case is to generate an SRPM package based on a git checkout of your upstream project. The packit command for SRPM generation is srpm.
<pre class="wp-block-preformatted">$ packit srpm Version in spec file is '0.3.1.37.g00bb80e'. SRPM: /home/phracek/work/colin/colin-0.3.1.37.g00bb80e-1.fc29.src.rpm</pre>
<h2>Packit as a service</h2>
In the summer, the people behind packit would like to introduce packit as a service (<a href="https://github.com/packit-service/packit-service">https://github.com/packit-service/packit-service</a>). In this case, the packit GitHub application will be installed into the upstream repository and packit will perform all the actions automatically, based on the events it receives from GitHub or fedmsg.
</div>