packaging April 2022

packaging@lists.fedoraproject.org

5 participants
4 discussions

Automatic virtual provides for RPM macros?
by Miro Hrončok 10 Mar '23

10 Mar '23

Hello, today at Nest, somebody said "unfortunately, there is no way to tell what package to install to get a particular RPM macro". I think that having an RPM provides generator for "rpm-macro(__python3)" or similar should be a fairly simple exercise. Would you folks consider that useful? -- Miro Hrončok -- Phone: +420777974800 IRC: mhroncok

4 4

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

Schedule for Thursday's FPC Meeting (2022-04-07 16:00 UTC)
by James Antill 07 Apr '22

07 Apr '22

Following is the list of topics that will be discussed in the FPC meeting Thursday at 2022-04-07 16:00 UTC in #fedora-meeting-1 on irc.libera.chat. Local time information (via. uitime): ================= Day: Thursday ================== 2022-04-07 09:00 PDT US/Pacific 2022-04-07 12:00 EDT --> US/Eastern <-- 2022-04-07 16:00 UTC UTC 2022-04-07 17:00 BST Europe/London 2022-04-07 18:00 CEST Europe/Berlin 2022-04-07 18:00 CEST Europe/Paris 2022-04-07 21:30 IST Asia/Calcutta ---------------- New Day: Friday ----------------- 2022-04-08 00:00 HKT Asia/Hong_Kong 2022-04-08 00:00 +08 Asia/Singapore 2022-04-08 01:00 JST Asia/Tokyo 2022-04-08 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 #topic #1132 Mark comments as scriplets for Sources (automation) .fpc 1132 https://pagure.io/packaging-committee/issue/1132 #topic #1150 request for clarification wrt. base version / compat package naming .fpc 1150 https://pagure.io/packaging-committee/issue/1150 #topic #1159 Ban use of %configure in %prep .fpc 1159 https://pagure.io/packaging-committee/issue/1159 = 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 #topic #pr-1097 Use caret in Obsoletes to simplify https://pagure.io/packaging-committee/pull-request/1097 #topic #pr-1163 Sources: Add section about conditionalization https://pagure.io/packaging-committee/pull-request/1163 = 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

rpmbuild: `! true` does not fail %install, but `false` does, `! true` fails other sections
by Miro Hrončok 06 Apr '22

06 Apr '22

Hello folks, I've realized that if the %install section contains a command that reverses the exit code from success to failure via !, the build does not fail, but it proceeds. In other sections, the build fails. E.g. this: %install ! true Does not fail the build. But this does: %install false As well as this: %build ! true Any idea why this is happening? Is it a bug, or a feature? This happens on Fedora 35 locally as well as Rawhide in Koji/mock. All of the following (applied separately) fail the RPM build: %prep false Executing(%prep): /bin/sh -e /var/tmp/rpm-tmp.A1K5K0 + umask 022 + cd /home/churchyard/rpmbuild/BUILD + false error: Bad exit status from /var/tmp/rpm-tmp.A1K5K0 (%prep) %build false Executing(%build): /bin/sh -e /var/tmp/rpm-tmp.YR6FiX + umask 022 + cd /home/churchyard/rpmbuild/BUILD + false error: Bad exit status from /var/tmp/rpm-tmp.YR6FiX (%build) %install false Executing(%install): /bin/sh -e /var/tmp/rpm-tmp.OapPfB + umask 022 + cd /home/churchyard/rpmbuild/BUILD + '[' /home/churchyard/rpmbuild/BUILDROOT/reproducer-0-0.x86_64 '!=' / ']' + rm -rf /home/churchyard/rpmbuild/BUILDROOT/reproducer-0-0.x86_64 ++ dirname /home/churchyard/rpmbuild/BUILDROOT/reproducer-0-0.x86_64 + mkdir -p /home/churchyard/rpmbuild/BUILDROOT + mkdir /home/churchyard/rpmbuild/BUILDROOT/reproducer-0-0.x86_64 + false error: Bad exit status from /var/tmp/rpm-tmp.OapPfB (%install) %check false Executing(%check): /bin/sh -e /var/tmp/rpm-tmp.CnEWIO + umask 022 + cd /home/churchyard/rpmbuild/BUILD + false error: Bad exit status from /var/tmp/rpm-tmp.CnEWIO (%check) But when replaced with `! true`, %install (and %install only) succeeds: %prep ! true Executing(%prep): /bin/sh -e /var/tmp/rpm-tmp.ojDvj8 + umask 022 + cd /home/churchyard/rpmbuild/BUILD + true + RPM_EC=1 ++ jobs -p + exit 1 error: Bad exit status from /var/tmp/rpm-tmp.ojDvj8 (%prep) %build ! true Executing(%build): /bin/sh -e /var/tmp/rpm-tmp.RTiQQH + umask 022 + cd /home/churchyard/rpmbuild/BUILD + true + RPM_EC=1 ++ jobs -p + exit 1 error: Bad exit status from /var/tmp/rpm-tmp.RTiQQH (%build) %install ! true Executing(%install): /bin/sh -e /var/tmp/rpm-tmp.RczM4N + umask 022 + cd /home/churchyard/rpmbuild/BUILD + '[' /home/churchyard/rpmbuild/BUILDROOT/reproducer-0-0.x86_64 '!=' / ']' + rm -rf /home/churchyard/rpmbuild/BUILDROOT/reproducer-0-0.x86_64 ++ dirname /home/churchyard/rpmbuild/BUILDROOT/reproducer-0-0.x86_64 + mkdir -p /home/churchyard/rpmbuild/BUILDROOT + mkdir /home/churchyard/rpmbuild/BUILDROOT/reproducer-0-0.x86_64 + true + /usr/lib/rpm/check-buildroot + ... + /usr/lib/rpm/redhat/brp-python-hardlink Executing(%check): ... Or even: %install ! true echo UNREACHABLE Executing(%install): /bin/sh -e /var/tmp/rpm-tmp.nzrs6N + umask 022 + cd /home/churchyard/rpmbuild/BUILD + '[' /home/churchyard/rpmbuild/BUILDROOT/reproducer-0-0.x86_64 '!=' / ']' + rm -rf /home/churchyard/rpmbuild/BUILDROOT/reproducer-0-0.x86_64 ++ dirname /home/churchyard/rpmbuild/BUILDROOT/reproducer-0-0.x86_64 + mkdir -p /home/churchyard/rpmbuild/BUILDROOT + mkdir /home/churchyard/rpmbuild/BUILDROOT/reproducer-0-0.x86_64 + true + echo UNREACHABLE UNREACHABLE + /usr/lib/rpm/check-buildroot + ... + /usr/lib/rpm/redhat/brp-python-hardlink Executing(%check): ... %check ! true Executing(%check): /bin/sh -e /var/tmp/rpm-tmp.4E9WU3 + umask 022 + cd /home/churchyard/rpmbuild/BUILD + true + RPM_EC=1 ++ jobs -p + exit 1 error: Bad exit status from /var/tmp/rpm-tmp.4E9WU3 (%check) What sorcery is this? -- Miro Hrončok -- Phone: +420777974800 IRC: mhroncok

4 4

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

packaging April 2022