This is a bit late on schedule, but...
In accordance with FESCo policy[1], the following provenpackagers will
be submitted for removal in two weeks based on a lack of Koji builds
submitted in the last six months. If you received this directly, you
can reply off-list to indicate you should still be in the
provenpackager group.
Note that removal from this group is not a "punishment" or a lack of
appreciation for the work you have done. The intent of the process is
to ensure contributors with distro-wide package privileges are still
active and responsive. This process is done regularly at the branch
point in each release.
[1]
https://docs.fedoraproject.org/en-US/fesco/Provenpackager_policy/#_maintain…
================
Checked 132 provenpackagers
The following 10 provenpackagers have not submitted a Koji build since
at least 2023-02-23 00:00:00:
puiterwijk
ajax
rdieter
ausil
pjones
hguemar
jwilson
law
wtogami
steve
================
== Summary ==
New or revised (sub)package names are proposed for Kubernetes packages
in Fedora. The new names will better align Kubernetes with current
usage as documented upstream and improve alignment of package content
with current Fedora practices and standards.
See https://discussion.fedoraproject.org/t/f40-change-proposal-restructure-kube…
for details and to reply.
== Summary ==
The python-sqlalchemy package is upgraded to major version 2. A
compatibility package python-sqlalchemy1.4 is added to the
distribution to cater for software which doesn’t yet use the new API,
this can be installed side-by-side. Other packages using SQLAlchemy
are identified and, if necessary, steps are taken to ensure they use
the correct major version package.
See https://discussion.fedoraproject.org/t/f40-change-proposal-sqlalchemy-2/878…
for details and to reply.
(I'm announcing this myself as per https://pagure.io/fesco/issue/3051.)
https://fedoraproject.org/wiki/Changes/Revitalize_Forge_Macros
This document represents a proposed Change. As part of the Changes
process, proposals are publicly announced in order to receive community
feedback. This proposal will only be implemented if approved by the
Fedora Engineering Steering Committee.
== Summary ==
Up until now, the
[https://src.fedoraproject.org/rpms/redhat-rpm-config/blob/7331757cf12ee645e… forge macros]
have been part of {{package|redhat-rpm-config}}.
We will split them out into a new `forge-srpm-macros` package.
We will add more test coverage and add a new `%forgeversion` macro to allow adding snapshot info to Version instead of Release.
== Owner ==
* Name: [[User:gotmax23| Maxwell G]]
* Email: maxwell(a)gtmx.me
== Detailed Description ==
The forge macros will be removed from
{{package|redhat-rpm-config}} in favor of a standalone `forge-srpm-macros`
package.
{{package|redhat-rpm-config}} will gain a dependency on `forge-srpm-macros`.
This will ease maintenance and allow the forge macros to develop independently
of redhat-rpm-config.
This split will also allow us to address longstanding issues such as
lack of test coverage and noncompliance with the new Versioning Guidelines that
mandate putting snapshot info in Version instead of Release.
Development is under way in https://git.sr.ht/~gotmax23/forge-srpm-macros.
Maintaining the macros in a separate upstream repository enables us to have
proper CI and proper versioning and frees us from having to sync macro files
across distgit branches.
The new forge-srpm-macros project
now has support for Codeberg, nested Gitlab groups, and a new
[https://git.sr.ht/~gotmax23/forge-srpm-macros/commit/145b7fc72a31b7e547bfdd… `%forgeversion` macro].
There are also unit tests covering the core forge macros functionality to
prevent future regressions.
The tests have already uncovered a two year old bug in the Pagure forge
functionality!
For now, we will limit this Change to rawhide, but we may backport the
`forge-srpm-macros` package to stable Fedora releases depending on feedback
from the redhat-rpm-config maintainers and other stakeholders.
This is not a backwards incompatible Change,
so it should be safe to backport after proper testing in Rawhide.
== Feedback ==
The redhat-rpm-config maintainers have expressed that they'd prefer if the forge
macros were split into a separate project.
Other developers have expressed that the lack of regression tests makes them
hesitant to propose or accept changes to the forge macros; this Change fixes that.
The Go SIG who makes use of {{package|go-rpm-macros}} that relies on the forge
macros is happy to see more maintenance of these macros.
The inability to get changes into the forge macros have blocked us from fixing
bugs that affect the Go macros.
== Benefit to Fedora ==
This split out will ease maintenance and allow us to address longstanding
issues in the current codebase.
== Scope ==
* Proposal owners:
** ✅ Create an upstream repository for the forge-srpm-macros project
** ✅ Prepare a PR for {{package|redhat-rpm-config}} to remove the macros and associated forge.lua code and add a dependency on the new package: https://src.fedoraproject.org/rpms/redhat-rpm-config/pull-request/260
** Submit the `forge-srpm-macros` package for review
** Build `forge-srpm-macros` and the updated {{package|redhat-rpm-config}} package in a side tag using provenpackager privileges
** Close existing PRs open against the forge macros and direct authors to the new project
* Other developers:
** Review the {{package|redhat-rpm-config}} PR
** Preform test builds of packages that use the forge macros
* Policies and guidelines:
** ✅ Adjust the [https://docs.fedoraproject.org/en-US/packaging-guidelines/SourceURL/ SourceURL Packaging Guidelines] to recommend the new `%forgeversion` macro: https://pagure.io/packaging-committee/pull-request/1295
* Trademark approval: N/A (not needed for this Change)
* Alignment with Community Initiatives: N/A
== Upgrade/compatibility impact ==
There shouldn't be any.
The forge macros will remain in the buildroot,
and {{package|redhat-rpm-config}} will Require the new package.
== How To Test ==
There is a test Copr available that contains builds of `forge-srpm-macros`'
`main` branch.
You can use it in mock like this:
<pre>
copr mock-config gotmax23/forge-srpm-macros-dev fedora-rawhide-x86_64 > ~/.config/mock/forge.cfg
fedpkg sources
# To preform a full package build
mock --spec *.spec --source . -r forge
# To build a source package only
mock --buildsrpm --spec *.spec --source . -r forge
</pre>
== User Experience ==
This is a developer focussed Change.
This Change does not propose any drastic changes to the macros themselves and
does not mandate specfile changes,
so it shouldn't be too visible.
== Dependencies ==
This change requires coordination with the redhat-rpm-config developers to
split out the macros.
== Contingency Plan ==
* Contingency mechanism: Revert the {{package|redhat-rpm-config}} change and retire `forge-srpm-macros`
* Contingency deadline: N/A (not a System Wide Change)
* Blocks release? No
== Documentation ==
N/A (not a System Wide Change)
== Release Notes ==
Planned Outage - Sever updates/reboots - 2023-08-16 21:00 UTC
There will be an outage starting at 2023-08-16 21:00 UTC,
which will last approximately 4 hours.
To convert UTC to your local time, take a look at
http://fedoraproject.org/wiki/Infrastructure/UTCHowto
or run:
date -d '2023-08-16 21:00UTC'
Reason for outage:
We will be applying all updates and rebooting servers into current kernels.
Services will be up and down in the outage window.
Package maintainers are advised to avoid submitting builds or doing other packaging work in the outage window.
Affected Services:
Many services will be up and down in the outage window as servers are updated and rebooted.
Ticket Link:
https://pagure.io/fedora-infrastructure/issue/11475
Please join #fedora-admin or #fedora-noc on irc.libera.chat
or #admin:fedoraproject.org / #noc:fedoraproject.org on matrix.
Please add comments to the ticket for this outage above.
Updated status for this outage may be available at
https://www.fedorastatus.org/
Hi All,
Fedora Linux 39 has now been branched, please be sure to do a
'git fetch -v' to pick up the new branch. As an additional reminder,
rawhide/39 has been completely isolated from previous releases, which
means that anything you do for 39 you also have to do in the rawhide
branch and do a build there. There is already a Fedora Linux 39 compose
at [1].
Bodhi is currently enabled in the 39 branch like it is for rawhide, with
automatic update creation. At the hit Beta change freeze point in the
Fedora Linux 39 schedule [2] updates-testing will be enabled and manual
bodhi updates will be required as in all stable releases.
Thanks
Regards,
Fedora Release Engineering
[1] https://dl.fedoraproject.org/pub/fedora/linux/development/30/
[2] https://fedorapeople.org/groups/schedule/f-39/f-39-key-tasks.html
Hi All,
Fedora Linux 39 is going to be branched in the upcoming hours as per
the previous discussion[1] we are going to disable new koji builds for
the duration of this event.
All builds that will be running at that time for the rawhide will be
canceled and can be resubmitted by maintainers after the branching.
All rawhide updates that are in a pending state for rawhide will be unpushed.
Once Fedora Linux 39 is branched we will reenable builds in koji with
notification to this list.
Tomas Hrcka
Fedora Release Engineering
@humaton:fedora.im
1 - https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org…
--
Tomas Hrcka
fas: humaton
libera.CHAT: jednorozec