packaging July 2021

packaging@lists.fedoraproject.org

4 participants
14 discussions

RPM-level auto release and changelog bumping - Fedora 33 System-Wide Change proposal
by Ben Cotton 13 Aug '22

13 Aug '22

https://fedoraproject.org/wiki/Changes/rpm_level_auto_release_and_changelog… == Summary == redhat-rpm-config will be updated so users of the auto framework get automated release and changelog bumping. == Owner == * Name: [[User:nim| Nicolas Mailhot]] * Email: <nicolas.mailhot at laposte.net> == Detailed Description == This is a system-wide change because all packages build with redhat-rpm-config, but it only concerns packages that opted to use this part of redhat-rpm-config (auto framework). The change will make those packages auto-bump and auto-changelog at the rpm level, in an infrastructure-independent way. == Benefit to Fedora == Autobumping removes a huge packager shore and makes timestamping in changelogs more reliable. == Scope == * Proposal owners: The feature is coded and works at the rpm level. Unfortunately, mock filters away the srpms containing the bump state, so it does not work in upper layers. * Other developers: The feature requires buy-in by mock developers (and probably koji developers) to lift the restrictions that block it above the rpm level. Also, it requires a mechanism to pass the user name and email that will be used in bumped changelogs (defining two variables in ~/.rpmmacros is sufficient at rpm level) * Mock issue: https://github.com/rpm-software-management/mock/issues/599 * Release engineering: https://pagure.io/releng/issue/9567 * Policies and guidelines: maybe eventually if things work out on the technical level * FPC issue: https://pagure.io/packaging-committee/issue/998 * Trademark approval: N/A (not needed for this Change) == Upgrade/compatibility impact == This is a pure build tooling update, it changes how things are built not what is built. == How To Test == A redhat-rpm-config packages with the changes and some example packages are available in https://copr.fedorainfracloud.org/coprs/nim/refactoring-forge-patches-auto-… Since the mock/copr layer is currently blocking the feature, you need to install the redhat-rpm-config and forge macro packages available in this repo locally. Afterwards you can take any of the example packages in the repo and rebuild them with rpmbuild -ba to your heart content, and see the releases bump and the changelogs being updated accordingly. To get beautiful changelogs, you also need to add <pre> %buildsys_name Your name %buildsys_email Your email </pre> in ~/.rpmmacros == User Experience == N/A Packager experience change only == Dependencies == The change is a spin-off of https://fedoraproject.org/wiki/Changes/Patches_in_Forge_macros_-_Auto_macro… Therefore, it depends on the success of that other change and will probably need rebasing if the code in this other change evolves during the redhat-rpm-config merge. It also depends on mock / copr/ koji buy-in and changes, that may add their own requirements. == Contingency Plan == There is no contingency plan because the change will happen or not at all. == Documentation == There is as much documentation as the average redhat-rpm-config change (ie comments in the macro files themselves) == Release Notes == N/A Packager productivity change only -- Ben Cotton He / Him / His Senior Program Manager, Fedora & CentOS Stream Red Hat TZ=America/Indiana/Indianapolis

12 23

Re: Macro to smoke-test-import a Python module in %check
by Miro Hrončok 05 Aug '21

05 Aug '21

On 29. 06. 21 8:28, Felix Schwarz wrote: > > Am 28.06.21 um 21:44 schrieb Miro Hrončok: >> The semantics is quite simple: >> >> >> %check >> %py3_check_import mymodule mymodule.submodule > > Looks great! Thank you. > > Please let us know when we should start adding that to our Python packages. :-) Feel free to test it out in rawhide. If there is no more feedback, I'll initiate the backports next week. -- Miro Hrončok -- Phone: +420777974800 IRC: mhroncok

2 2

Trying to rebuild grub2-2.06-2.fc34 from source rpm, but one subpackage is not built.
by Michele Riva 25 Jul '21

25 Jul '21

Hello everyone! I am trying to apply a patch to grub2-2.06-2.fc34 and to make a package out of it. To do so I'm using fedpkg for the most part, but when I come to the point of building the package with "fedpkg local" one of the subpackages seems missing: grub2-pc-modules.noarch This unfortunately makes impossible to replace the whole grub package set with the newly compiled packages, as dnf rightfully complains the missing one (see below for installed vs built packages). Weirdly enough, searching for "pc-modules" among the rpm source files does not return any result, while searching just "modules" shows some code used to build other packages (such as grub2-efi-x64-modules). It doesn't look like anything related to "pc-modules" exists in the code in the first place. Is there something I am not doing right? I can see other .noarch subpackages are built just fine in the process. Thanks to anyone who can help me clear this up :) Here's a list of the grub2 related packages on my system (fresh fedora 34 installation): ``` [michele@tre grub2]$ dnf list --installed | grep grub2 grub2-common.noarch 1:2.06-2.fc34 @updates grub2-efi-ia32.x86_64 1:2.06-2.fc34 @updates grub2-efi-ia32-cdboot.x86_64 1:2.06-2.fc34 @updates grub2-efi-x64.x86_64 1:2.06-2.fc34 @updates grub2-efi-x64-cdboot.x86_64 1:2.06-2.fc34 @updates grub2-pc.x86_64 1:2.06-2.fc34 @updates grub2-pc-modules.noarch 1:2.06-2.fc34 @updates grub2-tools.x86_64 1:2.06-2.fc34 @updates grub2-tools-efi.x86_64 1:2.06-2.fc34 @updates grub2-tools-extra.x86_64 1:2.06-2.fc34 @updates grub2-tools-minimal.x86_64 1:2.06-2.fc34 @updates ``` And here's the list of files built by "fedpkg local" ``` Wrote: /home/michele/fedpkg/grub2/grub2-2.06-2.fc34.maikeriva.src.rpm Wrote: /home/michele/fedpkg/grub2/noarch/grub2-common-2.06-2.fc34.maikeriva.noarch.rpm Wrote: /home/michele/fedpkg/grub2/x86_64/grub2-tools-debuginfo-2.06-2.fc34.maikeriva.x86_64.rpm Wrote: /home/michele/fedpkg/grub2/x86_64/grub2-tools-extra-debuginfo-2.06-2.fc34.maikeriva.x86_64.rpm Wrote: /home/michele/fedpkg/grub2/x86_64/grub2-tools-extra-2.06-2.fc34.maikeriva.x86_64.rpm Wrote: /home/michele/fedpkg/grub2/noarch/grub2-efi-x64-modules-2.06-2.fc34.maikeriva.noarch.rpm Wrote: /home/michele/fedpkg/grub2/x86_64/grub2-tools-2.06-2.fc34.maikeriva.x86_64.rpm Wrote: /home/michele/fedpkg/grub2/x86_64/grub2-emu-debuginfo-2.06-2.fc34.maikeriva.x86_64.rpm Wrote: /home/michele/fedpkg/grub2/x86_64/grub2-efi-ia32-cdboot-2.06-2.fc34.maikeriva.x86_64.rpm Wrote: /home/michele/fedpkg/grub2/x86_64/grub2-efi-x64-cdboot-2.06-2.fc34.maikeriva.x86_64.rpm Wrote: /home/michele/fedpkg/grub2/noarch/grub2-efi-ia32-modules-2.06-2.fc34.maikeriva.noarch.rpm Wrote: /home/michele/fedpkg/grub2/x86_64/grub2-debugsource-2.06-2.fc34.maikeriva.x86_64.rpm Wrote: /home/michele/fedpkg/grub2/x86_64/grub2-tools-minimal-debuginfo-2.06-2.fc34.maikeriva.x86_64.rpm Wrote: /home/michele/fedpkg/grub2/x86_64/grub2-tools-minimal-2.06-2.fc34.maikeriva.x86_64.rpm Wrote: /home/michele/fedpkg/grub2/x86_64/grub2-debuginfo-2.06-2.fc34.maikeriva.x86_64.rpm Wrote: /home/michele/fedpkg/grub2/x86_64/grub2-pc-2.06-2.fc34.maikeriva.x86_64.rpm Wrote: /home/michele/fedpkg/grub2/x86_64/grub2-emu-2.06-2.fc34.maikeriva.x86_64.rpm Wrote: /home/michele/fedpkg/grub2/x86_64/grub2-tools-efi-debuginfo-2.06-2.fc34.maikeriva.x86_64.rpm Wrote: /home/michele/fedpkg/grub2/x86_64/grub2-tools-efi-2.06-2.fc34.maikeriva.x86_64.rpm Wrote: /home/michele/fedpkg/grub2/x86_64/grub2-efi-ia32-2.06-2.fc34.maikeriva.x86_64.rpm Wrote: /home/michele/fedpkg/grub2/x86_64/grub2-efi-x64-2.06-2.fc34.maikeriva.x86_64.rpm Wrote: /home/michele/fedpkg/grub2/x86_64/grub2-emu-modules-2.06-2.fc34.maikeriva.x86_64.rpm ```

2 1

Trying to rebuild grub2-2.06-2.fc34 from source rpm, but one subpackage is not built.
by michele.riva＠protonmail.com 24 Jul '21

24 Jul '21

1 0

Trying to rebuild grub2-2.06-2.fc34 from source rpm, but one subpackage is not built.
by michele.riva＠protonmail.com 24 Jul '21

24 Jul '21

1 0

Bring your Python package to Nest and we'll help you convert it to the new Python macros
by Miro Hrončok 23 Jul '21

23 Jul '21

Hello Fedorans and especially Pythonistas, The Python Maintenance team from Red Hat just submitted a proposal [1] for a hackfest on Nest with Fedora [2]. With the new Python packaging guidelines [3], changes of your spec files are necessary to benefit from all the new fancy stuff, such as automatically generated build (incl. test) requires, packaging packages that use poetry or flit, using tox in %check or semi-automatically generating the %files section. On this hackfest, we plan to be available for you for half a day either on Thursday, August 5 or Friday, August 6. You hop on or hop off to Hopin as needed, ask us questions in the chat or via audio/video and we'll try our best to help you get started with the new tools and macros. Please, let the Nest organizers know in the ticket [1] if you are interested, so they can make a better decision whether to include this hackfest or not. See you on Nest either way! [1] https://pagure.io/flock/issue/346 [2] https://flocktofedora.org/ [3] https://fedoraproject.org/wiki/Changes/PythonPackagingGuidelines202x -- Miro Hrončok -- Phone: +420777974800 IRC: mhroncok

1 0

Summary/Minutes from today's FPC Meeting (2021-07-22 16:00 - 16:20 UTC)
by James Antill 22 Jul '21

22 Jul '21

====================== #fedora-meeting-1: fpc ====================== Meeting started by james at 16:00:19 UTC. The full logs are available at https://meetbot.fedoraproject.org/fedora-meeting-1/2021-07-22/fpc.2021-07-2… . Meeting summary --------------- * Roll Call (james, 16:00:19) * Open Floor (james, 16:05:15) Meeting ended at 16:20:01 UTC. Action Items ------------ Action Items, by person ----------------------- * **UNASSIGNED** * (none) People Present (lines said) --------------------------- * james (24) * tibbs (13) * zodbot (9) * decathorpe (7) * limburgher (3) Generated by `MeetBot`_ 0.1.4 .. _`MeetBot`: http://wiki.debian.org/MeetBot

1 0

Schedule for Thursday's FPC Meeting (2021-07-22 16:00 UTC)
by James Antill 22 Jul '21

22 Jul '21

Following is the list of topics that will be discussed in the FPC meeting Thursday at 2021-07-22 16:00 UTC in #fedora-meeting-1 on irc.libera.chat. Local time information (via. uitime): ================= Day: Thursday ================== 2021-07-22 09:00 PDT US/Pacific 2021-07-22 12:00 EDT --> US/Eastern <-- 2021-07-22 16:00 UTC UTC 2021-07-22 17:00 BST Europe/London 2021-07-22 18:00 CEST Europe/Berlin 2021-07-22 18:00 CEST Europe/Paris 2021-07-22 21:30 IST Asia/Calcutta ---------------- New Day: Friday ----------------- 2021-07-23 00:00 HKT Asia/Hong_Kong 2021-07-23 00:00 +08 Asia/Singapore 2021-07-23 01:00 JST Asia/Tokyo 2021-07-23 02:00 AEST Australia/Brisbane Links to all tickets below can be found at: https://pagure.io/packaging-committee/issues?status=Open&tags=meeting = Followup Actions = #topic #pr-814 * mhroncok talk to authors again, having a working example might help a lot = Followup Issues = #topic #886 Enable BRP for detecting RPATH .fpc 886 https://pagure.io/packaging-committee/issue/886 #topic #907 Which %__foo macros for executables are acceptable? .fpc 907 https://pagure.io/packaging-committee/issue/907 #topic #1058 How to handle %lang files in package owned directories? .fpc 1058 https://pagure.io/packaging-committee/issue/1058 = Followup Pull Requests = #topic #pr-814 Add SELinux Independent Policy Guidelines. https://pagure.io/packaging-committee/pull-request/814 #topic #pr-1045 WIP: Add discussion of macro names beginning with underscores. https://pagure.io/packaging-committee/pull-request/1045 #topic #pr-1071 Overhaul the RPATH section of the guidelines. https://pagure.io/packaging-committee/pull-request/1071 = Open Floor = For more complete details, please visit each individual ticket. The report of the agenda items can be found at: https://pagure.io/packaging-committee/issues?status=Open&tags=meeting If you would like to add something to this agenda, you can: * Reply to this e-mail * File a new ticket at: https://pagure.io/packaging-committee * E-mail me directly * Bring it up at the end of the meeting, during the open floor topic. Note that added topics may be deferred until the following meeting.

1 0

Schedule for Thursday's FPC Meeting (2019-08-15 16:00 UTC)
by James Antill 19 Jul '21

19 Jul '21

Following is the list of topics that will be discussed in the FPC meeting Thursday at 2019-08-15 16:00 UTC in #fedora-meeting-1 on irc.freenode.net. Local time information (via. uitime): ================= Day: Thursday ================== 2019-08-15 09:00 PDT US/Pacific 2019-08-15 12:00 EDT --> US/Eastern <-- 2019-08-15 16:00 UTC UTC 2019-08-15 17:00 BST Europe/London 2019-08-15 18:00 CEST Europe/Berlin 2019-08-15 18:00 CEST Europe/Paris 2019-08-15 21:30 IST Asia/Calcutta ---------------- New Day: Friday ----------------- 2019-08-16 00:00 HKT Asia/Hong_Kong 2019-08-16 00:00 +08 Asia/Singapore 2019-08-16 01:00 JST Asia/Tokyo 2019-08-16 02:00 AEST Australia/Brisbane Links to all tickets below can be found at: https://pagure.io/packaging-committee/issues?status=Open&tags=meeting = Followups = #topic #902 Cleanup & enhance spec files .fpc 902 https://pagure.io/packaging-committee/issue/902 #topic #904 Caret versioning .fpc 904 https://pagure.io/packaging-committee/issue/904 #topic #907 Which %__foo macros for executables are acceptable? .fpc 907 https://pagure.io/packaging-committee/issue/907 #topic #909 Suggest that linting/measuring-coverage is not for %check .fpc 909 https://pagure.io/packaging-committee/issue/909 #topic #914 Automatic R runtime dependencies .fpc 914 https://pagure.io/packaging-committee/issue/914 = Open Floor = For more complete details, please visit each individual ticket. The report of the agenda items can be found at: https://pagure.io/packaging-committee/issues?status=Open&tags=meeting If you would like to add something to this agenda, you can: * Reply to this e-mail * File a new ticket at: https://pagure.io/packaging-committee * E-mail me directly * Bring it up at the end of the meeting, during the open floor topic. Note that added topics may be deferred until the following meeting.

3 2

Odd problem with obsoletes in EPEL8
by Martin Jackson 19 Jul '21

19 Jul '21

Hello, I'm having a problem I don't understand how to fix, and I would appreciate some guidance. I'm maintaining nagios-plugins, which bundles a number of different "check" plugins and has some metapackages that include different subsets of those check plugins. In the EL 8.2 release cycle, one of the dependencies of one of those plugins was moved from EPEL into EL proper, which broke new installs of that plugin and the -all metapackage. A user filed a bug, so as a temporary workaround, I stopped building the plugin package with that dependency (nagios-plugins-ssl_validity, and had that version (nagios-plugins-2.3.3-3) obsolete the ssl_validity plugin, since leaving it around caused it to want to keep the base package in conflict with other packages that were upgrading. Now that CentOS 8.2 is released, and the dependency is available, I've issued an update (https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2020-70bcfe5382) that builds ssl_validity again, and also adds it back to the -all subpackage. I can upgrade it sucessfully (which installs the ssl_validity plugin again, as expected), but subsequent calls to dnf upgrade give this error: Obsoleting Packages nagios-plugins.x86_64 2.3.3-3.el8 epel nagios-plugins-ssl_validity.x86_64 2.3.3-4.el8 @epel-testing nagios-plugins 2.3.3-3 is not installed anymore, and there are no explicit Obsoletes: in the ssl_validity package. I'm not sure what needs to be done here, but whatever it is I'm willing to make the change. Also wondering if this is expected behavior. Thanks, Marty

2 1

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

packaging July 2021