September 2020 - packaging - Fedora Mailing-Lists

RPM-level auto release and changelog bumping - Fedora 33 System-Wide Change proposal

by Ben Cotton

https://fedoraproject.org/wiki/Changes/rpm_level_auto_release_and_changel... == 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-aut... 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_mac... 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

9 months, 3 weeks

12
23
0 / 0

Schedule for Thursday's FPC Meeting (2019-08-15 16:00 UTC)

by James Antill

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.

1 year, 10 months

3
2
0 / 0

Odd problem with obsoletes in EPEL8

by Martin Jackson

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

1 year, 10 months

2
1
0 / 0

Help reqest: dependencies for packaging writefreely (Golang)

by Edd Salkield

Hi all, I'm currently working on packaging github.com/writeas/writefreely, a platform for building writing spaces. Some of its dependencies are currently not packaged for Fedora, so I'm seeking some advice on the granularity to which I should be packaging each dependency. github.com/writeas/writefreely depends on github.com/writeas/web-core. This is a library that is used by the project developers (write.as) for all their shared code. It is likely that this will be used as a dependency for future packages (for example, when their photo sharing service, snap.as, gets released), but unlikely that it will ever be used by anyone other than these developers. Therefore, should github.com/writeas/web-core be its own package, should I bundle it in with writefreely, should it be a subpackage of writefreely, or indeed something else? Additionally, web-core has its own dependencies of the same kind. Where possible, I have submitted PRs[1,2,3] to their repo to reduce unnecessary dependencies, but web-core still depends upon github.com/writeas/impart and github.com/writeas/openssl-go. These libraries are both unlikely to be used anywhere else; should these be bundled too? If the correct course of action is to bundle the dependencies (in a nested way), I would really appreciate somebody experienced at packaging Go packages to give some guidance on how to do this sensibly with the Go SPEC file macro system. This is especially since the current documentation[4] seems pretty light on the topic of dealing with SPEC files with multiple sources. Also, this is my first time joining a mailing list to actually get involved with the Fedora project, so do let me know if this sort of question actually belongs elsewhere. Kind regards, Edd Salkield [1] https://github.com/writeas/web-core/pull/6 [2] https://github.com/writeas/web-core/pull/8 [3] https://github.com/writeas/web-core/pull/10 [4] https://docs.fedoraproject.org/en-US/packaging-guidelines/Golang/

2 years, 8 months

2
1
0 / 0

Schedule for Thursday's FPC Meeting (2020-09-17 16:00 UTC)

by James Antill

Following is the list of topics that will be discussed in the FPC meeting Thursday at 2020-09-17 16:00 UTC in #fedora-meeting-1 on irc.freenode.net. Local time information (via. uitime): ================= Day: Thursday ================== 2020-09-17 09:00 PDT US/Pacific 2020-09-17 12:00 EDT --> US/Eastern <-- 2020-09-17 16:00 UTC UTC 2020-09-17 17:00 BST Europe/London 2020-09-17 18:00 CEST Europe/Berlin 2020-09-17 18:00 CEST Europe/Paris 2020-09-17 21:30 IST Asia/Calcutta ---------------- New Day: Friday ----------------- 2020-09-18 00:00 HKT Asia/Hong_Kong 2020-09-18 00:00 +08 Asia/Singapore 2020-09-18 01:00 JST Asia/Tokyo 2020-09-18 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 Issues = #topic #907 Which %__foo macros for executables are acceptable? .fpc 907 https://pagure.io/packaging-committee/issue/907 = Followup Pull Requests = #topic #pr-814 Add SELinux Independent Policy Guidelines. https://pagure.io/packaging-committee/pull-request/814 = 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.

2 years, 8 months

1
0
0 / 0

Packaging fish config files

by Orion Poplawski

Background - https://bugzilla.redhat.com/show_bug.cgi?id=1878306 conda can provide an /etc/fish/conf.d/conda.fish file for fish users. As usual, we do not want to add a dependency on fish for conda. For now I think I'll just have conda own /etc/fish and /etc/fish/conf.d, but what do we want to do going forward? Add it to filesystem? Create a fish-filesystem package? Surprisingly, I can't find any other packages that ship /etc/fish/conf.d/* files, so maybe this just isn't an issue worth taking on yet. Thanks, Orion -- Orion Poplawski Manager of NWRA Technical Systems 720-772-5637 NWRA, Boulder/CoRA Office FAX: 303-415-9702 3380 Mitchell Lane orion(a)nwra.com Boulder, CO 80301 https://www.nwra.com/

2 years, 8 months

2
1
0 / 0

Summary/Minutes from today's FPC Meeting (2020-09-10 16:00 - 16:30 UTC)

by James Antill

====================== #fedora-meeting-1: fpc ====================== Meeting started by geppetto at 16:00:29 UTC. The full logs are available at https://meetbot.fedoraproject.org/fedora-meeting-1/2020-09-10/fpc.2020-09... . Meeting summary --------------- * Roll Call (geppetto, 16:00:29) * Schedule (geppetto, 16:05:11) * LINK: https://lists.fedoraproject.org/archives/list/packaging@lists.fedoraproje... (geppetto, 16:05:14) * LINK: https://pagure.io/packaging-committee/issue/907 also looks like it might be done? (geppetto, 16:15:39) * Open Floor (geppetto, 16:22:26) * ACTION: decathorpe Look through all the non-meeting tickets to see if any are stuck and need to be discussed. (geppetto, 16:24:33) Meeting ended at 16:30:08 UTC. Action Items ------------ * decathorpe Look through all the non-meeting tickets to see if any are stuck and need to be discussed. Action Items, by person ----------------------- * decathorpe * decathorpe Look through all the non-meeting tickets to see if any are stuck and need to be discussed. * **UNASSIGNED** * (none) People Present (lines said) --------------------------- * geppetto (34) * zodbot (16) * mhroncok (12) * tibbs (11) * decathorpe (5) * King_InuYasha (3) * limburgher (3) * carlwgeorge (1) Generated by `MeetBot`_ 0.1.4 .. _`MeetBot`: http://wiki.debian.org/MeetBot

2 years, 8 months

1
0
0 / 0

Schedule for Thursday's FPC Meeting (2020-09-10 16:00 UTC)

by James Antill

Following is the list of topics that will be discussed in the FPC meeting Thursday at 2020-09-10 16:00 UTC in #fedora-meeting-1 on irc.freenode.net. Local time information (via. uitime): ================= Day: Thursday ================== 2020-09-10 09:00 PDT US/Pacific 2020-09-10 12:00 EDT --> US/Eastern <-- 2020-09-10 16:00 UTC UTC 2020-09-10 17:00 BST Europe/London 2020-09-10 18:00 CEST Europe/Berlin 2020-09-10 18:00 CEST Europe/Paris 2020-09-10 21:30 IST Asia/Calcutta ---------------- New Day: Friday ----------------- 2020-09-11 00:00 HKT Asia/Hong_Kong 2020-09-11 00:00 +08 Asia/Singapore 2020-09-11 01:00 JST Asia/Tokyo 2020-09-11 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 Issues = #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 = Followup Pull Requests = #topic #pr-814 Add SELinux Independent Policy Guidelines. https://pagure.io/packaging-committee/pull-request/814 #topic #pr-947 Deprecate Old Style Dependency Generators. https://pagure.io/packaging-committee/pull-request/947 = 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.

2 years, 8 months

1
0
0 / 0

Summary/Minutes from today's FPC Meeting (2020-09-03 16:00 - 16:45 UTC)

by James Antill

====================== #fedora-meeting-1: fpc ====================== Meeting started by geppetto at 16:00:39 UTC. The full logs are available at https://meetbot.fedoraproject.org/fedora-meeting-1/2020-09-03/fpc.2020-09... . Meeting summary --------------- * Roll Call (geppetto, 16:00:39) * Schedule (geppetto, 16:05:56) * LINK: https://lists.fedoraproject.org/archives/list/packaging@lists.fedoraproje... (geppetto, 16:05:59) * LINK: https://lists.fedoraproject.org/archives/list/packaging@lists.fedoraproje... (geppetto, 16:08:02) * #pr-814 Add SELinux Independent Policy Guidelines. (geppetto, 16:08:14) * LINK: https://pagure.io/packaging-committee/pull-request/814 (geppetto, 16:08:14) * LINK: https://pagure.io/packaging-committee/pull-request/814#request_diff I guess (tibbs, 16:13:11) * ACTION: mhroncok to speak to authors again, having a working example might help a lot. (geppetto, 16:34:35) * #1007 Golang pkg review exception to update a lot of packages (geppetto, 16:34:56) * LINK: https://pagure.io/packaging-committee/issue/1007 (geppetto, 16:34:56) * ACTION: Golang pkg review exception to update a lot of packages (+1:6, 0:0, -1:0) (geppetto, 16:40:19) * Open Floor (geppetto, 16:41:22) Meeting ended at 16:45:43 UTC. Action Items ------------ * mhroncok to speak to authors again, having a working example might help a lot. * Golang pkg review exception to update a lot of packages (+1:6, 0:0, -1:0) Action Items, by person ----------------------- * mhroncok * mhroncok to speak to authors again, having a working example might help a lot. * **UNASSIGNED** * Golang pkg review exception to update a lot of packages (+1:6, 0:0, -1:0) People Present (lines said) --------------------------- * geppetto (49) * zodbot (15) * mhroncok (14) * King_InuYasha (11) * tibbs (7) * carlwgeorge (2) * decathorpe (1) Generated by `MeetBot`_ 0.1.4 .. _`MeetBot`: http://wiki.debian.org/MeetBot

2 years, 9 months

1
0
0 / 0

Schedule for Thursday's FPC Meeting (2020-09-03 16:00 UTC)

by James Antill

Following is the list of topics that will be discussed in the FPC meeting Thursday at 2020-09-03 16:00 UTC in #fedora-meeting-1 on irc.freenode.net. Local time information (via. uitime): ================= Day: Thursday ================== 2020-09-03 09:00 PDT US/Pacific 2020-09-03 12:00 EDT --> US/Eastern <-- 2020-09-03 16:00 UTC UTC 2020-09-03 17:00 BST Europe/London 2020-09-03 18:00 CEST Europe/Berlin 2020-09-03 18:00 CEST Europe/Paris 2020-09-03 21:30 IST Asia/Calcutta ---------------- New Day: Friday ----------------- 2020-09-04 00:00 HKT Asia/Hong_Kong 2020-09-04 00:00 +08 Asia/Singapore 2020-09-04 01:00 JST Asia/Tokyo 2020-09-04 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 Issues = #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 #1007 Golang pkg review exception to update a lot of packages .fpc 1007 https://pagure.io/packaging-committee/issue/1007 = Followup Pull Requests = #topic #pr-814 Add SELinux Independent Policy Guidelines. https://pagure.io/packaging-committee/pull-request/814 #topic #pr-947 Deprecate Old Style Dependency Generators. https://pagure.io/packaging-committee/pull-request/947 = 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.

2 years, 9 months

1
0
0 / 0

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

packaging September 2020