From f4bfa65eb4acdf4c502d3a3bd6db6e73f953d78e Mon Sep 17 00:00:00 2001 From: qhwdw <33189910+qhwdw@users.noreply.github.com> Date: Tue, 14 Nov 2017 12:59:04 +0800 Subject: [PATCH 1/2] Translated by qhwdw Translated by qhwdw --- ... created my first RPM package in Fedora.md | 218 ++++++++++++++++++ 1 file changed, 218 insertions(+) create mode 100644 translated/tech/20171107 How I created my first RPM package in Fedora.md diff --git a/translated/tech/20171107 How I created my first RPM package in Fedora.md b/translated/tech/20171107 How I created my first RPM package in Fedora.md new file mode 100644 index 0000000000..68d7fce8fe --- /dev/null +++ b/translated/tech/20171107 How I created my first RPM package in Fedora.md @@ -0,0 +1,218 @@ +# 怎么在 Fedora 中创建我的第一个 RPM 包？ + +![](https://i0.wp.com/blog.justinwflory.com/wp-content/uploads/2017/11/newpackage.png?resize=1024%2C433&ssl=1) + +过了这个夏天，我迁移我的桌面环境到 i3，一个 Tiling 窗口管理器。当初，切换到 i3 是一个挑战，因为，我必须去处理许多以前 GNOME 帮我处理的事情。其中一件事情就是改变屏幕亮度。 xbacklight，在笔记本电脑上改变背光亮度的标准方法，它在我的硬件上不工作了。 + +最近，我发现[brightlight][1]，一个改变背光亮度的工具。我决定去试一下它，它工作在 root 权限下。但是，我发现 brightligh 在 Fedora 下没有 RPM 包。我决定，是在 Fedora 下尝试创建一个包的时候了，并且可以学习怎么去创建一个 RPM 包。 + +在这篇文章中，我将分享以下的内容： + +*创建 RPM SPEC 文件 +*在 Koji 和 Copr　中构建包 +*使用 debug 包处理一个问题 +*提交这个包到 Fedora 包收集中 + +### 前提条件 + +在 Fedora 上，我安装了包构建过程中所有步骤涉及到的包。 + +``` +sudo dnf install fedora-packager fedpkg fedrepo_req copr-cli +``` + +### 创建 RPM SPEC 文件 + +创建 RPM 包的第一步是去创建 SPEC 文件。这些规范，或者是指令，它告诉 RPM 怎么去构建包。这是告诉 RPM 从包的源代码中创建一个二进制文件。创建 SPEC 文件看上去是整个包处理过程中最难的一部分，并且它的难度取决于项目。 + +对我而言，幸运的是，brightlight 是一个用 C 写的简单应用程序。维护人员可以很容易地创建一个 Makefile 的二进制应用程序。构建它只是在库中简单运行 make 的问题。因此，我用一个简单的项目去学习 RPM 打包。 + +### 查找文档 + +谷歌搜索 “how to create an RPM package” 有很多结果。我开始使用的是 [IBM 的文档][2]。然而，我发现它理解起来非常困难，不知所云（虽然十分详细，它可能适用于复杂的 app）。我也在 Fedora 维基上找到了 [创建包][3] 的介绍。这个文档在构建和处理上解释的非常好，但是，我一直困惑于 “怎么去开始呢？” + +最终，我找到了 [RPM 打包准则][4]，它是大神 [Adam Miller][5] 写的。这些介绍非常有帮助，并且包含了三个优秀的示例，它们分别是用 Bash、C 和 Python 写的。这个指南帮我很容易地理解了怎么去构建一个 RPM SPEC，并且，更重要的是，解释了怎么把这些片断拼到一起。 + +有了这些之后，我可以去写 brightlight 程序的我的 [第一个 SPEC 文件][6] 了。因为它是很简单的，SPEC 很短也很容易理解。因此，我有了我的 SPEC 文件，我发现了其中一些错误。处理掉一些错误之后，我创建了源 RPM (SRPM) 和二进制 RPM，然后，我解决了出现的问题。 + +``` +rpmlint SPECS/brightlight.spec +rpmbuild -bs SPECS/brightlight.spec +rpmlint SRPMS/brightlight-5-1.fc26.src.rpm +rpmbuild -bb SPECS/brightlight-5-1.fc26.x86_64.rpm +rpmlint RPMS/x86_64/brightlight-5-1.fc26.x86_64.rpm +``` + +现在，我有了一个可用的 RPM，可以发送到 Fedora 库了。 + +### 在 Copr 和 Koji 中构建 + +接下来，我读了 [指南][7] 中关于怎么去为 Fedora 创建一个包。在提交之前，他们鼓励打包者通过在一个构建在 [Koji][9] 中托管的 [Copr][8] 库项目去测试要提交的包。 + +#### 使用 Copr + +首先，我为 brightlight 创建了一个 [Copr 库][10]，[Copr][11] 是在 Fedora 的基础设施中的一个服务，它构建你的包，并且设置一个你选择的 Fedora 或 EPEL 的任意版本。它快速运行你的 RPM 包，并与其它人去分享是非常方便的。使用一个 Copr 的主机你不需要特定的许可。 + +我从 web 接口创建了我的 Copr 项目，但是，你也可以使用 copr-cli 工具。这儿是一个 Fedora 开发者入门的 [非常优秀的指南][12]。在网站上创建了我的库之后，我使用这个命令构建了我的包。 + +``` +copr-cli build brightlight SRPMS/brightlight.5-1.fc26.src.rpm +``` + +我的包成功构建，并且，我可以很容易地在我的 Fedora 系统上成功安装它。 + +#### 使用 Koji + +任何人都可以使用 [Koji][13] 在多种架构和 Fedora 或 CentOS/RHEL 版本中，去测试他们的包。在 Koji 中测试，你必须有一个源 RPM。我希望 brightlight 包在 Fedora 所有的版本中都支持，因此，我运行如下的命令： + +``` +koji build --scratch f25 SRPMS/brightlight-5-1.fc26.src.rpm +koji build --scratch f26 SRPMS/brightlight-5-1.fc26.src.rpm +koji build --scratch f27 SRPMS/brightlight-5-1.fc26.src.rpm +``` + +它花费了一些时间，但是，Koji 构建了所有的包。我的包可以很完美地运行在 Fedora 25 和 26 中，但是 Fedora 27 失败了。 Koji 模拟构建始终保持一个跟踪，并且确保我的包构建成功。 + +### 问题：Fedora 27 构建失败！ + +现在，我已经知道我的 Fedora 27 上的包在 Koji 上构建失败了。但是，为什么呢？我发现在 Fedora 27 上有两个相关的变化。 + +*[Subpackage and Source Debuginfo][14] +*[RPM 4.14][15] (特别是，debuginfo 包重写了) + +这些变化意味着 RPM 包必须使用一个 debuginfo 包去构建。这有助于排错或调试一个应用程序。在我的案例中，这并不是关键的或者很必要的，但是，我需要去构建一个。 + +感谢 Igor Gnatenko，他帮我理解了为什么我在 Fedora 27 上构建包，需要去将这些增加到我的包的 SPEC 中。在 %make_build 宏指令之前，我增加了这些行。 + +``` +export CFLAGS="%{optflags}" +export LDFLAGS="%{__global_ldflags}" +``` + +我构建了一个新的 SRPM 并且提交它到 Koji 去在 Fedora 27 上构建。成功了，它构建成功了！ + +### 提交这个包 + +现在，我在 Fedora 25 到 27 上成功校验了我的包，是时候为 Fedora 打包了。第一步是提交这个包，在 Red Hat Bugzilla 上为了评估包，去创建一个新 bug。我为 brightlight [创建了一个票据][16]。因为这是我的第一个包，我显式的标注它 “这是我的第一个包”，并且我寻找一个赞助商。在票据中，我链接 SPEC 和 SRPM 文件到我的 Git 库中。 + +#### 进入 dist-git + +[Igor Gnatenko][17] 发起我进入 Fedora 包组，并且在我的包上留下反馈。我学习了一些其它的关于 C 应用程序打包的特定的知识。在他响应我之后，我可以在 [dist-git][18] 上请求一个库，Fedora 的 RPM 包收集库，为所有的 Fedora 保存了 SPEC 文件。 + +一个很方便的 Python 工具可以帮你很容易地去生成这部分内容。fedrepo-req 是一个用于创建一个新的 dist-git 库的请求的工具。我用这个命令提交我的请求。 + +``` +fedrepo-req brightlight \ + --ticket 1505026 \ + --description "CLI tool to change screen back light brightness" \ + --upstreamurl https://github.com/multiplexd/brightlight +``` + +它为我在 fedora-scm-requests 库创建了一个新的票据。一个我是管理员的 [创建的库][19]。现在，我可以做生意了！ + +![](https://i0.wp.com/blog.justinwflory.com/wp-content/uploads/2017/11/Screenshot-from-2017-11-05-19-58-47.png?w=1366&ssl=1) +My first RPM in Fedora dist-git – woohoo! + +#### 与 dist-git 一起工作 + +接下来，fedpkg 是用于和 dist-git 库进行交互的工具。我改变当前目录到我的 git 工作目录，然后运行这个命令。 + +``` +fedpkg clone brightlight +``` + +fedpkg 从 dist-git 克隆了我的包的库。对于这个仅有的第一个分支，你需要去导入 SRPM。 + +``` +fedpkg import SRPMS/brightlight-5-1.fc26.src.rpm +``` + +fedpkg 导入你的包的 SRPM 到这个库中，然后设置源为你的 Git 库。使用 fedpkg 这一步是很重要的，因为它用一个 Fedora 友好的方去去帮助规范这个库（与手动添加文件相比）。一旦你导入了 SRPM，推送这个改变到 dist-git 库。 + +``` +git commit -m "Initial import (#1505026)." +git push +``` + +#### 构建包 + +自从你推送第一个包导入到你的 dist-git 库中，你已经准备好去做一个真正的 Koji 项目构建者。去构建你的项目，运行这个命令。 + +``` +fedpkg build +``` + +它在 Koji 中为 Rawhide 构建你的包，这是 Fedora 中的非受控分支。在你为其它分支构建之前，你必须在 Rawhide 分支上构建成功。如果构建成功，你现在可以为你的项目的其它分支发送请求了。 + +``` +fedrepo-req brightlight f27 -t 1505026 +fedrepo-req brightlight f26 -t 1505026 +fedrepo-req brightlight f25 -t 1505026 +``` + +#### 关于构建其它分支的注意事项 + +一旦你初始导入了 SRPM，如果你选择去创建它们，记得合并你的主分支到其它分支。例如，如果你后面为 Fedora 27 请求一个分支，你将需要去使用这些命令。 + +``` +fedpkg switch-branch f27 +git merge master +git push +fedpkg build +``` + +#### 提交更新到 Bodhi + +这个过程的最后一步是，提交你的新包作为一个更新到 Bodhi 中。当你初次提交你的更新包时，它将去测试这个库。任何人都可以测试你的包并且增加 karma 到更新中。如果你的更新接收了 3 个以上的投票（或者像 Bodhi 称它为 karma），你的包将自动被推送到稳定库。否则，一周之后，在测试库中推送它。 + +去提交你的更新到 Bodhi，你仅需要一个命令。 + +``` +fedpkg update +``` + +它为你的包用一个不同的配置选项打开一个 Vim 窗口。一般情况下，你仅需要去指定一个输入（比如，新包），然后，去检查你的包的票据 ID 数字。对于更深入的讲解，这里有一个 Fedora 维基上的更新指南。 + +在保存和退出这个文件后，fedpkg 提交你的包作为一个更新到 Bodhi，最后，同步到 Fedora 测试库。我也可以用这个命令去安装我的包。 + +``` +sudo dnf install brightlight -y --enablerepo=updates-testing --refresh +``` + +### 我们是稳定的 + +最近提交了我的包到 [Fedora 26 稳定库][20]，并且，不久将进入 [Fedora 25][21] 和 [Fedora 27][22] 稳定库。感谢帮助我完成我的第一个包的每个人。我期待有更多的机会为发行版添加包。 + +-------------------------------------------------------------------------------- + +via: https://blog.justinwflory.com/2017/11/first-rpm-package-fedora/ + +作者：[JUSTIN W. FLORY ][a] +译者：[qhwdw](https://github.com/qhwdw) +校对：[校对者ID](https://github.com/校对者ID) + +本文由 [LCTT](https://github.com/LCTT/TranslateProject) 原创编译，[Linux中国](https://linux.cn/) 荣誉推出 + +[a]:https://blog.justinwflory.com/author/jflory7/ +[1]:https://github.com/multiplexd/brightlight +[2]:https://www.ibm.com/developerworks/library/l-rpm1/index.html +[3]:https://fedoraproject.org/wiki/How_to_create_an_RPM_package +[4]:https://fedoraproject.org/wiki/How_to_create_an_RPM_package +[5]:https://github.com/maxamillion +[6]:https://src.fedoraproject.org/rpms/brightlight/blob/master/f/brightlight.spec +[7]:https://fedoraproject.org/wiki/Join_the_package_collection_maintainers +[8]:https://copr.fedoraproject.org/ +[9]:https://koji.fedoraproject.org/koji/ +[10]:https://copr.fedorainfracloud.org/coprs/jflory7/brightlight/ +[11]:https://developer.fedoraproject.org/deployment/copr/about.html +[12]:https://developer.fedoraproject.org/deployment/copr/copr-cli.html +[13]:https://koji.fedoraproject.org/koji/ +[14]:https://fedoraproject.org/wiki/Changes/SubpackageAndSourceDebuginfo +[15]:https://fedoraproject.org/wiki/Changes/RPM-4.14 +[16]:https://bugzilla.redhat.com/show_bug.cgi?id=1505026 +[17]:https://fedoraproject.org/wiki/User:Ignatenkobrain +[18]:https://src.fedoraproject.org/ +[19]:https://src.fedoraproject.org/rpms/brightlight +[20]:https://bodhi.fedoraproject.org/updates/brightlight-5-1.fc26 +[21]:https://bodhi.fedoraproject.org/updates/FEDORA-2017-8071ee299f +[22]:https://bodhi.fedoraproject.org/updates/FEDORA-2017-f3f085b86e From d5a6c239a8c8bbd6f488a1b1a6e9ca46b5b695b1 Mon Sep 17 00:00:00 2001 From: qhwdw <33189910+qhwdw@users.noreply.github.com> Date: Tue, 14 Nov 2017 12:59:37 +0800 Subject: [PATCH 2/2] Translated by qhwdw Translated by qhwdw --- ... created my first RPM package in Fedora.md | 218 ------------------ 1 file changed, 218 deletions(-) delete mode 100644 sources/tech/20171107 How I created my first RPM package in Fedora.md diff --git a/sources/tech/20171107 How I created my first RPM package in Fedora.md b/sources/tech/20171107 How I created my first RPM package in Fedora.md deleted file mode 100644 index 8ce8f31afc..0000000000 --- a/sources/tech/20171107 How I created my first RPM package in Fedora.md +++ /dev/null @@ -1,218 +0,0 @@ -Translating by qhwdw # How I created my first RPM package in Fedora - -![](https://i0.wp.com/blog.justinwflory.com/wp-content/uploads/2017/11/newpackage.png?resize=1024%2C433&ssl=1) - -Over the summer, I migrated my desktop environment to i3, a tiling window manager. Switching to i3 was a challenge at first, since I had to replace many things that GNOME handled for me. One of these things was changing screen brightness. xbacklight, the standard way of changing backlight brightness on laptops, doesn’t work on my hardware. - -Recently, I discovered [brightlight][1], a tool that changes backlight brightness. I decided to try it, and it worked with root privileges. However, I found there was no RPM package in Fedora for brightlight. I decided this was the right time to try creating a package in Fedora and learn how to create an RPM. - -In this article, I’ll cover and share how I… - -*Created the RPM SPEC file -*Built the package in Koji and Copr -*Worked through an issue with debug package -*Submitted the package to Fedora package collection - -### Pre-requisites - -On Fedora, I installed these packages for all steps of the package building process. - -``` -sudo dnf install fedora-packager fedpkg fedrepo_req copr-cli -``` - -### Creating the RPM SPEC file - -The first step to create a RPM is to create the SPEC file. These are the specifications, or instructions, that tell RPM how to build the package. This is how you tell RPM to create a binary file from the package’s source code. Creating the SPEC file is likely the hardest part of the packaging process and its difficulty depends on the project. - -Fortunately for me, brightlight is a simple application written in C. The maintainer made it easy to create a binary application with a Makefile. Building it was a matter of simply running make in the repo. So now I had a simple project to learn RPM packaging. - -### Finding documentation - -Googling “how to create an RPM package” yields many results. I started with [IBM’s documentation][2]. However, I found it confusing and difficult to understand (although quite detailed; it might be more useful for a complicated app). I also found the [package creation][3] instructions on the Fedora wiki. The documentation here was good at explaining the composition and process, but I was still confused on how to begin. - -Finally, I found the [RPM Packaging Guidelines][4], written by the amazing [Adam Miller][5]. These instructions were helpful and included three excellent examples for Bash, C, and Python applications. This guide helped me better understand how to compose a RPM SPEC, and more importantly, how all the pieces fit together. - -After this, I was able to write my [first SPEC file][6] for brightlight. Since it is so simple, the SPEC file is short and easy to understand. Once I had my SPEC file, I linted the file for errors. After cleaning a few mistakes, I created the source RPM (SRPM) and the binary RPM, then linted each for errors. - -``` -rpmlint SPECS/brightlight.spec -rpmbuild -bs SPECS/brightlight.spec -rpmlint SRPMS/brightlight-5-1.fc26.src.rpm -rpmbuild -bb SPECS/brightlight-5-1.fc26.x86_64.rpm -rpmlint RPMS/x86_64/brightlight-5-1.fc26.x86_64.rpm -``` - -Now, I had a valid RPM to send to the Fedora repositories. - -### Building in Copr and Koji - -Next, I read the [guidelines][7] to becoming a Fedora packager. Before submitting anything, they encouraged packagers to test their packages by hosting the project in a [Copr][8] repo and building in [Koji][9]. - -#### Using Copr - -First, I created a [Copr repository][10] for brightlight. [Copr][11] is a service in Fedora’s infrastructure that builds your package and sets up a custom repo for whatever version of Fedora or EPEL that you choose. It’s handy to get your RPM hosted quickly and to share it with others for testing. You don’t need special approval to host a Copr. - -I created my Copr project from the web interface, but you can also use the copr-cli tool. There is an [excellent guide][12] in the Fedora Developer portal. After I created my repo on the website, I built my package with this command. - -``` -copr-cli build brightlight SRPMS/brightlight.5-1.fc26.src.rpm -``` - -My packages successfully built for Copr and I was able to install it on my Fedora system easily. - -#### Using Koji - -Anyone can use [Koji][13] to test their package on multiple architectures and versions of Fedora or CentOS / RHEL. To test on Koji, you must have a source RPM. I wanted to package brightlight on all supported versions of Fedora, so I ran these commands. - -``` -koji build --scratch f25 SRPMS/brightlight-5-1.fc26.src.rpm -koji build --scratch f26 SRPMS/brightlight-5-1.fc26.src.rpm -koji build --scratch f27 SRPMS/brightlight-5-1.fc26.src.rpm -``` - -It took some time, but Koji built all the packages. Everything was fine for Fedora 25 and 26, but Fedora 27 failed. Koji scratch builds keep me on the right track and make sure my packages build successfully. - -### Problem: Fedora 27 builds failing! - -Now I know that my Fedora 27 package was failing to build on Koji. But why? I discovered two relevant changes for Fedora 27. - -*[Subpackage and Source Debuginfo][14] -*[RPM 4.14][15] (specifically, the debuginfo package rewrite) - -These changes mean that RPM packages must build with a debuginfo package. This is helpful for troubleshooting or debugging an application. In my case, this wasn’t critical or too necessary, but I needed to build one. - -Thanks to Igor Gnatenko, he helped me understand what I needed to add to my package SPEC for it to build on Fedora 27. Before the %make_build macro, I added these lines. - -``` -export CFLAGS="%{optflags}" -export LDFLAGS="%{__global_ldflags}" -``` - -I built a new SRPM and submitted it to Koji to build on Fedora 27. And success! It built successfully. - -### Submitting the package - -Now that I verified my package successfully built on Fedora 25 to 27, it’s time to begin the packaging process for Fedora. The first step to submitting a package is to create a new bug in the Red Hat Bugzilla to ask for a package review. I [created a ticket][16] for brightlight. Since this was my first package, I made an explicit note that this was my first package and I was seeking a sponsor. In the ticket, I linked to the SPEC and SRPM files in my git repository. - -#### Getting into dist-git - -[Igor Gnatenko][17] sponsored me into the Fedora Packagers group and left feedback on my package. I learned of some other things specific for packaging C applications. After he sponsored me, I was able to ask for a repo in [dist-git][18], Fedora’s collection of RPM package repositories that host SPEC files for all of Fedora. - -A handy Python tool helps make this part easy. fedrepo-req is a tool that creates a request for a new dist-git repository. I submitted my request with this command. - -``` -fedrepo-req brightlight \ - --ticket 1505026 \ - --description "CLI tool to change screen back light brightness" \ - --upstreamurl https://github.com/multiplexd/brightlight -``` - -This created a new ticket for me in the fedora-scm-requests repo. The next day, an admin [created the repository][19] for me. Now, I was in business! - -![](https://i0.wp.com/blog.justinwflory.com/wp-content/uploads/2017/11/Screenshot-from-2017-11-05-19-58-47.png?w=1366&ssl=1) -My first RPM in Fedora dist-git – woohoo! - -#### Working with dist-git - -Next, fedpkg is the tool used for interacting with dist-git repositories. I changed directories into my git working directory and ran this command. - -``` -fedpkg clone brightlight -``` - -fedpkg then clones my package’s repo from dist-git. For the first branch only, you need to import the SRPM. - -``` -fedpkg import SRPMS/brightlight-5-1.fc26.src.rpm -``` - -fedpkg imports your package’s SRPM into the repo and sets up the sources for you. It’s important to use fedpkg for this because it helps provision the repo in a Fedora-friendly way (as compared to adding the files manually yourself). Once you import the SRPM, push the changes to the dist-git repo. - -``` -git commit -m "Initial import (#1505026)." -git push -``` - -#### Building the package - -Once you push the first import to your dist-git repo, you’re ready to do a real Koji build of your project. To build your project, run this command. - -``` -fedpkg build -``` - -This builds your package in Koji for Rawhide, the unversioned branch of Fedora. You must build successfully for Rawhide before you can build for other branches. IF everything builds successfully, you can now ask for other branches for your project. - -``` -fedrepo-req brightlight f27 -t 1505026 -fedrepo-req brightlight f26 -t 1505026 -fedrepo-req brightlight f25 -t 1505026 -``` - -#### Note about building other branches - -Once you import the SRPM initially, remember to merge your master branch to other branches, if you choose to create them. For example, if you later request a branch for Fedora 27, you would want to use these commands. - -``` -fedpkg switch-branch f27 -git merge master -git push -fedpkg build -``` - -#### Submitting update to Bodhi - -The last step of the process is to submit your new package as an update to Bodhi. When you first submit your package as an update, it goes to the testing repositories. Anyone can test your package and add karma to the update. If your update receives +3 votes (or as Bodhi calls it, karma), your package automatically pushes to the stable repositories. Otherwise, it pushes after a week in the testing repositories. - -To submit your update to Bodhi, you only need one command. - -``` -fedpkg update -``` - -This opens a Vim window with different configuration options for your package. Usually, you only need to specify the type (e.g. newpackage) and the ticket ID number for your package review. For a more in-depth explanation, there is an update guide on the Fedora wiki. - -After saving and exiting the file, fedpkg submits your package as an update to Bodhi and eventually synchronizes to the Fedora testing repositories. I was able to install my package with this command. - -``` -sudo dnf install brightlight -y --enablerepo=updates-testing --refresh -``` - -### We’re stable! - -My package was recently submitted to [Fedora 26 stable repositories][20] and will soon enter [Fedora 25][21] and [Fedora 27][22] stable repositories. Thanks for everyone who helped me with my first package. I look forward to more opportunities to add more packages to the distribution. - --------------------------------------------------------------------------------- - -via: https://blog.justinwflory.com/2017/11/first-rpm-package-fedora/ - -作者：[JUSTIN W. FLORY ][a] -译者：[译者ID](https://github.com/译者ID) -校对：[校对者ID](https://github.com/校对者ID) - -本文由 [LCTT](https://github.com/LCTT/TranslateProject) 原创编译，[Linux中国](https://linux.cn/) 荣誉推出 - -[a]:https://blog.justinwflory.com/author/jflory7/ -[1]:https://github.com/multiplexd/brightlight -[2]:https://www.ibm.com/developerworks/library/l-rpm1/index.html -[3]:https://fedoraproject.org/wiki/How_to_create_an_RPM_package -[4]:https://fedoraproject.org/wiki/How_to_create_an_RPM_package -[5]:https://github.com/maxamillion -[6]:https://src.fedoraproject.org/rpms/brightlight/blob/master/f/brightlight.spec -[7]:https://fedoraproject.org/wiki/Join_the_package_collection_maintainers -[8]:https://copr.fedoraproject.org/ -[9]:https://koji.fedoraproject.org/koji/ -[10]:https://copr.fedorainfracloud.org/coprs/jflory7/brightlight/ -[11]:https://developer.fedoraproject.org/deployment/copr/about.html -[12]:https://developer.fedoraproject.org/deployment/copr/copr-cli.html -[13]:https://koji.fedoraproject.org/koji/ -[14]:https://fedoraproject.org/wiki/Changes/SubpackageAndSourceDebuginfo -[15]:https://fedoraproject.org/wiki/Changes/RPM-4.14 -[16]:https://bugzilla.redhat.com/show_bug.cgi?id=1505026 -[17]:https://fedoraproject.org/wiki/User:Ignatenkobrain -[18]:https://src.fedoraproject.org/ -[19]:https://src.fedoraproject.org/rpms/brightlight -[20]:https://bodhi.fedoraproject.org/updates/brightlight-5-1.fc26 -[21]:https://bodhi.fedoraproject.org/updates/FEDORA-2017-8071ee299f -[22]:https://bodhi.fedoraproject.org/updates/FEDORA-2017-f3f085b86e