Orphaned packages looking for new maintainers
by Miro Hrončok
The following packages are orphaned and will be retired when they
are orphaned for six weeks, unless someone adopts them. If you know for sure
that the package should be retired, please do so now with a proper reason:
https://fedoraproject.org/wiki/How_to_remove_a_package_at_end_of_life
Note: If you received this mail directly you (co)maintain one of the affected
packages or a package that depends on one. Please adopt the affected package or
retire your depending package to avoid broken dependencies, otherwise your
package will fail to install and/or build when the affected package gets retired.
Request package ownership via the *Take* button in he left column on
https://src.fedoraproject.org/rpms/<pkgname>
Full report available at:
https://churchyard.fedorapeople.org/orphans-2021-02-22.txt
grep it for your FAS username and follow the dependency chain.
For human readable dependency chains,
see https://packager-dashboard.fedoraproject.org/
For all orphaned packages,
see https://packager-dashboard.fedoraproject.org/orphan
Package (co)maintainers Status Change
================================================================================
adf-accanthis-fonts orphan 0 weeks ago
arduino-builder orphan 1 weeks ago
arp-scan moceap, orphan, xmrbrz 0 weeks ago
balance lbazan, orphan 0 weeks ago
bareftp chreide, orphan 0 weeks ago
bind-to-tinydns orphan, timj 0 weeks ago
bucardo lbazan, orphan 0 weeks ago
bugzilla eseyman, orphan 0 weeks ago
cri-tools dwalsh, fkluknav, lsm5, 0 weeks ago
orphan, umohnani
ctorrent orphan 0 weeks ago
dianara orphan 0 weeks ago
drehatlas-warender-bibliothek- orphan 0 weeks ago
fonts
drehatlas-widelands-fonts orphan 0 weeks ago
drehatlas-xaporho-fonts orphan 0 weeks ago
eclipse-cdt akurtakov, eclipse-sig, 4 weeks ago
jjohnstn, kdaniel, orphan,
rgrunber
eclipse-pydev eclipse-sig, jjohnstn, orphan 3 weeks ago
eclipse-remote eclipse-sig, orphan 5 weeks ago
ez-ipupdate abo, jlayton, orphan 0 weeks ago
felix-bundlerepository mizdebsk, orphan 2 weeks ago
geronimo-jcdi-1.1-api orphan 2 weeks ago
geronimo-validation orphan 2 weeks ago
git-up orphan 2 weeks ago
glom orphan 1 weeks ago
golang-gvisor eclipseo, elmarco, orphan 3 weeks ago
goocanvasmm orphan 1 weeks ago
goocanvasmm2 orphan 1 weeks ago
gstreamermm orphan 1 weeks ago
httpunit fnasser, mizdebsk, orphan 0 weeks ago
ifstat orphan 0 weeks ago
jfsutils fcami, orphan 0 weeks ago
jmdns mizdebsk, orphan 1 weeks ago
jnr-enxio jjohnstn, orphan, rgrunber 5 weeks ago
jnr-unixsocket jjohnstn, orphan, rgrunber 5 weeks ago
jomolhari-fonts orphan, pnemade 0 weeks ago
jython akurtakov, dmalcolm, 3 weeks ago
jmatthews, lkundrak, orphan,
pmackinn
kanjistrokeorders-fonts orphan 0 weeks ago
knemo nucleo, orphan, rdieter, 0 weeks ago
tuxbrewr
krb5-auth-dialog alexl, caolanm, gnome-sig, 0 weeks ago
mbarnes, orphan, rhughes,
rstrode, simo, ssp
lcm dcallagh, mrunge, nmarques, 3 weeks ago
orphan
libglademm24 orphan 1 weeks ago
libinfinity orphan 1 weeks ago
libmirage orphan 0 weeks ago
libmypaint2 orphan 5 weeks ago
libnotifymm orphan 1 weeks ago
libss7 jsmith, orphan 0 weeks ago
mydns orphan 0 weeks ago
netty mizdebsk, orphan 3 weeks ago
nload cicku, fab, fale, orphan 0 weeks ago
ocaml-merlin orphan 2 weeks ago
opendbx orphan 0 weeks ago
opendmarc orphan 0 weeks ago
os-maven-plugin mizdebsk, orphan 3 weeks ago
pen cicku, danniel, orphan 0 weeks ago
perl-DBIx-Safe orphan 0 weeks ago
perl-pgsql_perl5 orphan 0 weeks ago
pg_activity orphan 0 weeks ago
pg_top orphan 0 weeks ago
php-pecl-ssh2 orphan, remi 0 weeks ago
pidgin-logviewer orphan 2 weeks ago
plotmm orphan 1 weeks ago
pokerth orphan 0 weeks ago
puppetlabs-stdlib gchamoul, orphan 3 weeks ago
python-django-registration orphan 2 weeks ago
python-fastapi orphan 0 weeks ago
python-flask-assets orphan, pjp, sundaram 2 weeks ago
python-flask-babelex devrim, orphan 0 weeks ago
python-flask-gravatar devrim, orphan 0 weeks ago
python-flask-htmlmin devrim, orphan 0 weeks ago
python-flask-mail devrim, orphan 0 weeks ago
python-flask-migrate jkaluza, orphan, ralph 0 weeks ago
python-flask-oauth orphan, pjp, sundaram 2 weeks ago
python-flask-paranoid devrim, orphan 0 weeks ago
python-flask-pymongo orphan 0 weeks ago
python-flask-security devrim, orphan 0 weeks ago
python-flask-sphinx-themes devrim, orphan 0 weeks ago
python-jose orphan 0 weeks ago
python-pg8000 fab, orphan 0 weeks ago
python-pgspecial orphan 0 weeks ago
python-ryu orphan, slaweq 5 weeks ago
python-setuptools_hg orphan 2 weeks ago
python-shadowsocks orphan 1 weeks ago
python-sshtunnel orphan 0 weeks ago
python-starlette orphan 0 weeks ago
python-vcversioner fab, orphan 0 weeks ago
python-webassets dcallagh, orphan, pjp, 2 weeks ago
sundaram
qroneko orphan 2 weeks ago
redir orphan 0 weeks ago
reiserfs-utils cicku, orphan 0 weeks ago
ripmime orphan, xavierb 0 weeks ago
rubygem-fog-aws orphan 4 weeks ago
rubygem-oauth mmorsi, orphan 4 weeks ago
simple-jndi orphan 2 weeks ago
sofia-sip orphan 0 weeks ago
squirrelmail orphan 4 weeks ago
sumwars orphan 0 weeks ago
swt-chart orphan 4 weeks ago
sylpheed cicku, cwickert, orphan, 0 weeks ago
sharkcz
tibetan-machine-uni-fonts orphan 0 weeks ago
tlomt-junction-fonts orphan 0 weeks ago
tmw-music orphan 2 weeks ago
tomcat-taglibs-parent orphan 5 weeks ago
trac-batchmodify-plugin orphan 3 weeks ago
trac-navadd-plugin orphan 3 weeks ago
trac-themeengine-plugin orphan 3 weeks ago
trac-tocmacro-plugin orphan 3 weeks ago
trac-vatar-plugin orphan 3 weeks ago
trac-workflowadmin-plugin orphan 3 weeks ago
transmission-remote-gtk orphan, tingping 2 weeks ago
ttyd orphan 0 weeks ago
ubuntu-title-fonts orphan 0 weeks ago
usbview orphan 0 weeks ago
vollkorn-fonts orphan 0 weeks ago
wput orphan 0 weeks ago
xmlrpc kdaniel, mizdebsk, orphan 3 weeks ago
xmonad-log-applet dcallagh, orphan 3 weeks ago
yanone-tagesschrift-fonts orphan 0 weeks ago
ytnef orphan, sheltren 0 weeks ago
The following packages require above mentioned packages:
Report too long, see the full version at
https://churchyard.fedorapeople.org/orphans-2021-02-22.txt
See dependency chains of your packages at
https://packager-dashboard.fedoraproject.org/
See all orphaned packages at https://packager-dashboard.fedoraproject.org/orphan
Affected (co)maintainers (either directly or via packages' dependencies):
aarem: sylpheed
abbra: tomcat-taglibs-parent
abo: ez-ipupdate
ajax: jomolhari-fonts
akien: tomcat-taglibs-parent
akurtakov: netty, eclipse-cdt, tomcat-taglibs-parent, jython, eclipse-remote,
os-maven-plugin
alexl: jomolhari-fonts, krb5-auth-dialog, ytnef
alexlan: perl-pgsql_perl5, tomcat-taglibs-parent
almac: jython, netty, os-maven-plugin
andymenderunix: drehatlas-widelands-fonts
arobinso: jython, netty, os-maven-plugin
asn: ytnef
asrob: php-pecl-ssh2
atim: gstreamermm
avsej: tomcat-taglibs-parent
berrange: jomolhari-fonts
besser82: jomolhari-fonts
bkabrda: python-flask-migrate
breilly: python-flask-migrate
brouhaha: tomcat-taglibs-parent
bruno: gstreamermm, tomcat-taglibs-parent
caillon: jomolhari-fonts, ytnef
caniszczyk: jython, netty, os-maven-plugin
caolanm: jomolhari-fonts, krb5-auth-dialog, ytnef
cfu: tomcat-taglibs-parent
cheese: tomcat-taglibs-parent
chreide: bareftp
churchyard: netty, jmdns, arduino-builder, jython, os-maven-plugin
cicku: sylpheed, reiserfs-utils, tomcat-taglibs-parent, nload, pen
cipherboy: tomcat-taglibs-parent
clumens: tomcat-taglibs-parent
coolsvap: tomcat-taglibs-parent
cqi: python-flask-migrate, python-jose
csutherl: tomcat-taglibs-parent
cverna: python-flask-migrate
cwickert: sylpheed, libglademm24, ytnef
cycloptivity: php-pecl-ssh2
danniel: pen
dbhole: jython, netty, os-maven-plugin
dcallagh: lcm, xmonad-log-applet, python-webassets
dciabrin: tomcat-taglibs-parent
deamn: jython, netty, os-maven-plugin
deji: tomcat-taglibs-parent
devrim: python-flask-sphinx-themes, python-flask-gravatar,
python-flask-paranoid, python-flask-security, python-flask-babelex,
perl-pgsql_perl5, python-flask-htmlmin, python-flask-mail
dmalcolm: jython, netty, os-maven-plugin
dmoluguw: tomcat-taglibs-parent
dominik: tomcat-taglibs-parent
dwalsh: cri-tools
dwmw2: opendmarc, ytnef
dwrobel: tomcat-taglibs-parent
ebaron: jython, netty, os-maven-plugin
eclipse-sig: netty, eclipse-cdt, xmlrpc, eclipse-pydev, jython, eclipse-remote,
os-maven-plugin
eclipseo: golang-gvisor, tomcat-taglibs-parent
edewata: tomcat-taglibs-parent
elmarco: golang-gvisor
elxreno: netty, jmdns, arduino-builder, jython, os-maven-plugin
eseyman: bugzilla, jomolhari-fonts
evgenyz: jomolhari-fonts
fab: tomcat-taglibs-parent, nload, python-pg8000, python-vcversioner,
perl-pgsql_perl5
fale: nload
fcami: jfsutils, tomcat-taglibs-parent
filabrazilska: jomolhari-fonts
filiperosset: jython, netty, os-maven-plugin
fivaldi: python-flask-migrate
fkluknav: cri-tools
fnasser: httpunit
fsimonce: tomcat-taglibs-parent
fujiwara: tomcat-taglibs-parent
galileo: jython, netty, os-maven-plugin
gchamoul: puppetlabs-stdlib
gil: tomcat-taglibs-parent
gnaponie: python-flask-migrate
gnome-sig: jomolhari-fonts, krb5-auth-dialog
greghellings: tomcat-taglibs-parent
helloworld1: tomcat-taglibs-parent
hhorak: tomcat-taglibs-parent
huwang: tomcat-taglibs-parent
hvad: jomolhari-fonts
infra-sig: jomolhari-fonts
ipa-maint: tomcat-taglibs-parent
jcerny: jomolhari-fonts
jerboaa: jython, netty, tomcat-taglibs-parent, os-maven-plugin
jfearn: tomcat-taglibs-parent
jfilak: jnr-unixsocket, jnr-enxio
jhrozek: tomcat-taglibs-parent
jjelen: tomcat-taglibs-parent
jjohnstn: netty, eclipse-cdt, xmlrpc, eclipse-pydev, jnr-enxio, jython,
jnr-unixsocket, eclipse-remote, os-maven-plugin
jkaluza: python-flask-migrate
jkang: jython, netty, os-maven-plugin
jlayton: ez-ipupdate
jmatthews: jython, netty, os-maven-plugin
jmlich: perl-pgsql_perl5
jorton: tomcat-taglibs-parent
jplesnik: jomolhari-fonts
jpokorny: tomcat-taglibs-parent
jreznik: kanjistrokeorders-fonts
jskarvad: opendmarc
jsmith: php-pecl-ssh2, libss7
jvanek: jython, netty, os-maven-plugin
jwrdegoede: drehatlas-widelands-fonts, tomcat-taglibs-parent
kalev: python-flask-migrate
kdaniel: netty, eclipse-cdt, xmlrpc, tomcat-taglibs-parent, jython,
eclipse-remote, os-maven-plugin
kde-sig: kanjistrokeorders-fonts
kevin: jomolhari-fonts
kwenning: tomcat-taglibs-parent
kwright: tomcat-taglibs-parent
laxathom: tomcat-taglibs-parent
lbazan: perl-DBIx-Safe, balance, bucardo
lef: jython, netty, tomcat-taglibs-parent, os-maven-plugin
lennart: libglademm24
lholecek: python-flask-migrate
liangsuilong: jomolhari-fonts, tomcat-taglibs-parent
limb: tomcat-taglibs-parent
linkdupont: tomcat-taglibs-parent
lkundrak: netty, tomcat-taglibs-parent, jython, jomolhari-fonts, os-maven-plugin
lon: tomcat-taglibs-parent
lsedlar: python-flask-migrate
lsm5: cri-tools
lucarval: python-flask-migrate
lucilanga: ytnef
matyc: jomolhari-fonts
maxamillion: perl-pgsql_perl5, python-flask-migrate
mayorga: perl-pgsql_perl5
mbarabas: jomolhari-fonts
mbarnes: jomolhari-fonts, krb5-auth-dialog, ytnef
mbayer: tomcat-taglibs-parent
mbooth: jython, netty, os-maven-plugin
mcrha: ytnef
mdomsch: opendbx
meeuw: python-pgspecial
mharmsen: tomcat-taglibs-parent
mikem: python-flask-migrate
mizdebsk: netty, jmdns, xmlrpc, tomcat-taglibs-parent, httpunit,
felix-bundlerepository, os-maven-plugin, jython
mkosek: tomcat-taglibs-parent
mlichvar: tomcat-taglibs-parent
mlysonek: jomolhari-fonts
mmarhefk: jomolhari-fonts
mmorsi: rubygem-oauth
moceap: tomcat-taglibs-parent, arp-scan
mprahl: python-flask-migrate
mrunge: lcm
mschorm: tomcat-taglibs-parent
mschwendt: ytnef
mskalick: tomcat-taglibs-parent
nmarques: lcm
nphilipp: drehatlas-widelands-fonts, tomcat-taglibs-parent
nucleo: knemo
oget: jython, netty, os-maven-plugin
oliver: jython, netty, os-maven-plugin
omajid: tomcat-taglibs-parent
otaylor: python-flask-migrate
panovotn: tomcat-taglibs-parent
patches: netty, jmdns, arduino-builder, jython, os-maven-plugin
pcpa: python-flask-sphinx-themes, tomcat-taglibs-parent
perl-maint-sig: jomolhari-fonts
peter: jython, netty, tomcat-taglibs-parent, os-maven-plugin
pfrields: php-pecl-ssh2
pingou: jomolhari-fonts
pjp: python-flask-assets, python-flask-oauth, python-webassets
pkubat: perl-pgsql_perl5
pmackinn: jython, netty, os-maven-plugin
pnemade: jomolhari-fonts
ppisar: jomolhari-fonts
praiskup: perl-pgsql_perl5
pvoborni: tomcat-taglibs-parent
pvrabec: jomolhari-fonts
pwalter: tomcat-taglibs-parent
pwu: tomcat-taglibs-parent
qwan: python-flask-migrate
ralph: python-flask-migrate, jomolhari-fonts
rathann: gstreamermm
rcritten: tomcat-taglibs-parent
rdieter: kanjistrokeorders-fonts, knemo
remi: php-pecl-ssh2
rgrunber: netty, eclipse-cdt, jnr-enxio, jython, jnr-unixsocket, eclipse-remote,
os-maven-plugin
rhughes: jomolhari-fonts, krb5-auth-dialog, ytnef
richardfearn: jython, netty, os-maven-plugin
rjones: jomolhari-fonts, tomcat-taglibs-parent
rlandmann: tomcat-taglibs-parent
rmattes: libglademm24, tomcat-taglibs-parent
robmv: jomolhari-fonts
rstrode: jomolhari-fonts, krb5-auth-dialog, ytnef
russellb: libss7
s4504kr: tomcat-taglibs-parent
sagitter: tomcat-taglibs-parent
salimma: ytnef
sasiddiq: jython, netty, os-maven-plugin
scenek: jomolhari-fonts
sdodson: php-pecl-ssh2
sergiomb: jomolhari-fonts
sharkcz: sylpheed
sheltren: ytnef
simo: krb5-auth-dialog, tomcat-taglibs-parent
siwinski: php-pecl-ssh2
slaweq: python-ryu
smani: perl-pgsql_perl5, tomcat-taglibs-parent
spike: tomcat-taglibs-parent
spot: netty, jmdns, tomcat-taglibs-parent, arduino-builder, jython,
jomolhari-fonts, os-maven-plugin
ssp: jomolhari-fonts, krb5-auth-dialog, ytnef
sundaram: python-flask-assets, python-flask-oauth, python-webassets
suve: tomcat-taglibs-parent
tagoh: jomolhari-fonts
terjeros: jython, netty, os-maven-plugin
teuf: tomcat-taglibs-parent
than: kanjistrokeorders-fonts
thm: ytnef
thofmann: libglademm24
thozza: netty, jmdns, arduino-builder, jython, os-maven-plugin
timj: bind-to-tinydns
timn: libglademm24, tomcat-taglibs-parent
tingping: transmission-remote-gtk
tkorbar: opendbx
tomh: perl-pgsql_perl5, tomcat-taglibs-parent
tpopela: ytnef
ttomecek: python-flask-migrate
ttorling: tomcat-taglibs-parent
tuxbrewr: knemo
twaugh: python-flask-migrate
twoerner: tomcat-taglibs-parent
umohnani: cri-tools
vakwetu: tomcat-taglibs-parent
van: tomcat-taglibs-parent
vascom: netty, jmdns, arduino-builder, jython, os-maven-plugin
verdurin: tomcat-taglibs-parent
vmaljulin: python-flask-migrate
volter: perl-pgsql_perl5
vrutkovs: python-flask-migrate
wsato: jomolhari-fonts
xavierb: ripmime, jomolhari-fonts
xmrbrz: arp-scan
--
The script creating this output is run and developed by Fedora
Release Engineering. Please report issues at its pagure instance:
https://pagure.io/releng/
The sources of this script can be found at:
https://pagure.io/releng/blob/main/f/scripts/find_unblocked_orphans.py
2 years, 3 months
Fedora Packager Dashboard - Available for wide use to all packagers
by Frantisek Zatloukal
Hi,
We'd like to announce that the Fedora Packager Dashboard passed the testing
period, was properly deployed inside Fedora Infrastructure, got fixes,
improvements and feature additions and is now available for widespread use
among all Fedora Packagers.
For those of you who didn’t hear about the Dashboard yet, It combines all
relevant information for package maintainers into one web application with
searching and both simple and advanced (regex based) filtering
possibilities. You’ll find things like open bug reports, updates,
overrides, FTBFS (from koschei and from Fedora Health Check by decathorpe)
and FTI reports, pull requests and orphan/retire warnings not only for your
packages directly, but even for packages you depend on. It’s designed to
make a packager's life easier and save our packagers some of their time. An
article showing it’s current features is available on Fedora Community
Blog: https://communityblog.fedoraproject.org/fedora-packager-dashboard/
. There
will also be a talk about the Dashboard on DevConf.cz 2021:
https://devconfcz2021.sched.com/event/gmLm/packager-dashboard-life-of-pac...
.
Dashboard itself is available: https://packager-dashboard.fedoraproject.org/
(the Dashboard is automatically pulling new data every 15 minutes, so you
can just leave it open in one of your browser tabs and don’t worry about
reloading it :) )
Fedora Packager Dashboard leverages caching in the Oraculum backend to
significantly speed-up loading times with comparison to querying all the
relevant resources separately. We, of course, can't cache the entire
Bugzilla, Pagure, Bodhi... so we only cache data for users who
visit Packager Dashboard at least once per 14 days. Please keep in mind
that the first load for a “new” user might take a while. Most of the data
sources are refreshed every hour.
You can use the Dashboard for individual accounts as well as for FAS groups.
While the testing period is behind us and we have everything properly
deployed, the work doesn’t end here. We have longer term plans for even
more stuff for the dashboard. On the top of our list currently sit support
for private bugs (visible after you authenticate with FAS), and contextual
schedules and calendars for packages you might be interested in (eg. Do you
maintain some Python packages? You might want to have a Python Release
Calendar on your dashboard.)
Feel free to provide ideas or bug reports at
https://pagure.io/fedora-qa/packager_dashboard or simply send an email
reply to this thread with all kinds of feedback.
2 years, 3 months
REMINDER: Fedora 34 Change complete (100% complete) deadline in one week
by Ben Cotton
The change complete (100% complete) deadline for Fedora 34 changes is
Tuesday 23 February. At that point, changes should be 100% code
complete, along with supporting documentation where appropriate.
Please indicate this by setting the tracker bug for your change to
ON_QA.
Other upcoming schedule milestones:
* 2021-02-23 — Beta freeze begins
* 2021-03-16 — Beta release early target date
* 2021-03-23 — Beta release target date #1
For more information, see the schedule[1]
[1] https://fedorapeople.org/groups/schedule/f-34/f-34-key-tasks.html
--
Ben Cotton
He / Him / His
Senior Program Manager, Fedora & CentOS Stream
Red Hat
TZ=America/Indiana/Indianapolis
2 years, 3 months
Fedora 35 Change proposal: POWER 4k page size (System-Wide Change proposal)
by Ben Cotton
https://fedoraproject.org/wiki/Changes/Power4kPageSize
== Summary ==
On ppc64le, the kernel is currently compiled for 64k page size.
This change proposes using the more common 4k page size.
Some HPC workloads may be disadvantaged slightly. Workstation users
are likely to encounter fewer bugs.
Some things, like the AMD Radeon GPU drivers, firmware or related
code, appear to be completely non-functional on the 64k page size.
Insufficient upstream developers are testing such issues on this
architecture.
== Owner ==
* Name: [[User:pocock|Daniel Pocock]]
* Email: daniel(a)pocock.pro
== Detailed Description ==
== Feedback ==
Discussed several times on devel,
[https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.o...
latest here]
[https://forums.raptorcs.com/index.php/topic,248.msg1852.html
discussed upstream in the Raptor forum]
== Benefit to Fedora ==
Better first impression for users of ppc64le workstations.
Users can focus on reporting ppc64le bugs without being sidetracked by
page size bugs.
== Scope ==
* Proposal owners: [[DanielPocock]]
* Other developers: please volunteer by adding your name here
* Release engineering: [https://pagure.io/releng/issue/9939 #9939]
** wait for 5.12 kernel, verify that it includes the Btrfs patches for
arbitrary 4k / 64k sector size, independent of the page size
** create a kernel with 4k page size to run on the ppc64le build servers
** ensure the default kernel RPM in the distribution has 4k page size
** perform the mass rebuild running on the 4k page size
** create an installer ISO based on the revised kernel with 4k page size
* Policies and guidelines: no, as it is an arch-specific issues, most
other architectures already have a 4k page size
* Trademark approval: N/A (not needed for this Change)
* Alignment with Objectives: none of the current objectives relate to
this change
== Upgrade/compatibility impact ==
If the user has already formatted their root filesystem with Btrfs and
a 64k sector size, they need to be using a Fedora kernel that supports
both 4k and 64k. This is anticipated in a future kernel release, 5.12
and will hopefully be ready for F34 or
F35[https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproje....
== User Experience ==
New GPUs are more likely to just work on this non-x86 architecture, as
long as the latest firmware, mesa, llvm are also used.
Btrfs, the default filesystem, will use the sector size identical to
the running kernel's page size. As the 4k page size is more common,
this will ensure Btrfs filesystems created on ppc64le hosts can be
used on x86 and other hosts without hassle.
== Dependencies ==
All RPMs must be rebuilt on a server running the final page size (4k)
== Contingency Plan ==
* Contingency mechanism: Prepare a kernel with the original 64k
config, install it on the build server, rebuild all the packages for
this architecture
* Contingency deadline: whenever the last time for a full rebuild or
kernel change is possible
* Blocks release? Yes, full rebuild of all packages must be completed
before release
--
Ben Cotton
He / Him / His
Senior Program Manager, Fedora & CentOS Stream
Red Hat
TZ=America/Indiana/Indianapolis
2 years, 3 months
Fedora 35 Change: rpmautospec - removing release and changelog fields
from spec files (System-Wide Change proposal)
by Ben Cotton
https://fedoraproject.org/wiki/Changes/rpmautospec
== Summary ==
The goal of this change is to deploy in production the
[https://docs.pagure.org/fedora-infra.rpmautospec/ rpmautospec]
project.
With it, the content of the `Release` and `%changelog` fields in spec
files can be auto-generated, either locally or in the builder using
the information present in the git repo (in the form of git tags).
Note: This proposal is about changing the way the `Release` and
`%changelog` sections of the '''spec files''' are filled, not about
removing them from the SRPM or binary RPM.
== Owner ==
* Name: [[User:pingou| Pierre-Yves Chibon]]
* Email: pingou - at - pingoured.fr
* Name: [[User:nphilipp| Nils Philippsen]]
* Email: nphilipp - at - redhat.com
== Detailed Description ==
rpmautospec offers packagers who want to use it the possibility of
replacing the content of the `Release` of their spec file by `Release:
%autorel` and/or replace the content of the `%changelog` section of
their spec file by:
%changelog
%autochangelog
Both `%autorel` and `%autochangelog` are RPM macros that will be
expanded or replaced when the SRPM is built on the build system by
their corresponding values according to rpmautospec.
An overview of how rpmautospec works can be found at:
https://docs.pagure.org/fedora-infra.rpmautospec/principle.html.
We will describe below how each macro works.
=== The %autorel macro ===
To determine the next release information, rpmautospec relies on the
build history of the package.
This information is extracted from the buildsystem when running as a
koji plugin and from git tags when running outside of the buildsystem.
Using the build history of the package (ie a list of NEVRs) as well as
the information provided by the packager in the spec file, rpmautospec
then computes the next best release number for the package.
Once defined, it prepends a suitably defined %autorel macro to the top
of the spec file, freezing the computed value of the release number
and thus allowing reproducible builds of the SRPM.
The [https://docs.pagure.org/fedora-infra.rpmautospec/autorel.html
documentation of the autorel macro] describes how packagers can use it
to provide extra information.
=== The %autochangelog macro ===
The %autochangelog macro is in fact more a placeholder that
rpmautospec fills in during the creation of the SRPM (or when ran
manually on a project).
rpmautospec uses two sources of information to automatically generate
the changelog:
* an optional `changelog` file that packagers can add to the repository
* the git history of the spec file
rpmautospec will include the `changelog` as is in the `%changelog`
section and will use all the commits made to the repository after the
last change of the `changelog` file to generate the changelog.
In other words, if the packager has a repository created on January
10th and works on it for 6 months, adds a `changelog` file on June
1st. All the commits made before that commit of June 1st will be
ignored in favor of the content of the `changelog` file.
Similarly, if the packager then edits the file on July 1st, all the
commits prior to that commit of July 1st will be ignored.
All the commits involving files ending with either ".spec" or ".patch"
(this list can be expended if desired) and made after July 1st will be
used to generate the changelog.
== Benefit to Fedora ==
In short: easier packaging in Fedora for the packagers who opt-in.
The `Release` and `%changelog` fields are the two most conflicting
fields in RPM spec files. They impact most pull requests if they
involve updating the package or if the package is updated/rebuilt
while pull-request are being reviewed.
We currently have three different change logs per package and while
they target different audiences (package maintainer: git, sysadmin:
%changelog and end-user: bodhi notes) they overlap a lot and in most
cases are redundant. With this proposal, package maintainers will only
have to cope with two changelogs: git and bodhi notes.
== Scope ==
* Proposal owners:
** Finish the work on the %autorel macro to support some of the use
cases not implemented currently
** Adjust the packaging so rpmautospec does not live in a specific,
versionized python environment (and thus could be use to bootstrap
python)
** Adjust rpmdev-bumpspec (used by releng for mass-rebuilds) so it
ignores spec files using %autorel/%autochangelog
** Adjust the mass-rebuild script so it only adds a suitable git
commit log message for spec files using %autorel/%autochangelog
** Adjust fedpkg to skip the NEVR check when using rpmautospec
** Add dependency on rpmautospec on redhat-rpm-config
* Other developers:
** Opt-in for those who want to use it
** Test changes in staging
** Provide feedback
* Release engineering: [https://pagure.io/releng/issues #Releng issue number]
* Policies and guidelines: Packaging guidelines should be adjust to
explain how rpmautospec works and can be used. Documentation at:
https://docs.pagure.org/fedora-infra.rpmautospec/ should provide a
good basis for this
* Trademark approval: N/A (not needed for this Change)
* Alignment with Objectives:
== Upgrade/compatibility impact ==
Not applicable
== How To Test ==
In staging:
* Use `stg-koji` instead of `koji`
* Use `fedpkg-stage` instead of `fedpkg` (``dnf install fedpkg-stage``)
* Run `kinit <accountname>@STG.FEDORAPROJECT.ORG`
* Test with rawhide as rpmautospec is only available there in staging
at this point
* Install `rpmautospec-rpm-macros` to build packages locally.
* Edit the spec file to use either macro (or both)
* (Optional) Run `rpmautospec` on the git repository of your choice to
see what it does (you may have to run `rpmautospec tag-package` the
first time you run it).
* Build the package
* Check its release or changelog according to the macro set
In production:
* Edit the spec file to use either macro (or both)
* (Optional) Run `rpmautospec` on the git repository of your choice to
see what it does (you may have to run `rpmautospec tag-package` the
first time you run it).
* Build the package
* Check its release or changelog according to the macro set
Issues can be reported at: https://pagure.io/fedora-infra/rpmautospec/issues
Note that using this approach has some peculiarities, we've documented
the ones we've encountered at:
https://docs.pagure.org/fedora-infra.rpmautospec/peculiarities.html
== User Experience ==
Packagers not opting-in should not be affected in any way by this change.
Packagers opting-in should be able to stop worrying (or worry much
less) about the content of the Release/%changelog fields in their spec
file.
== Dependencies ==
None
== Contingency Plan ==
* Contingency mechanism: rpmautospec is not deployed in koji
* Contingency deadline: N/A (this isn't tied to a Fedora release)
* Blocks release? No
== Documentation ==
All the upstream documentations can be
https://docs.pagure.org/fedora-infra.rpmautospec/
== Release Notes ==
N/A, this change will not affect end-users (except maybe for some
changes in the content of the rpm changelog).
--
Ben Cotton
He / Him / His
Senior Program Manager, Fedora & CentOS Stream
Red Hat
TZ=America/Indiana/Indianapolis
2 years, 3 months
koji save-failed-tree enabled
by Kevin Fenzi
Greetings.
We have enabled the koji 'save-failed-tree' plugin in
koji.fedoraproject.org. This plugin allows you to tell koji to bundle up
a failed official builds chroot (either partly or fully) and download it
to investigate it locally.
This plugin should only be used for the case where you cannot determine
the cause of a build failure by any other means and need to examine
specific files in the chroot to do so.
A few things to note:
* This will only work on failed official builds that have failed
recently enough to still have their chroot on the builder where they
failed (default: 1 day) Not scratch builds. Not canceled builds.
The chroot downloads are REALLY LARGE. Please use this sparingly.
* This will only work on buildArch tasks, not images, etc
* Saved tree .tar.gz's are deleted from koji after 14 days.
* You need to have python3-koji-cli-plugins subpackage installed to use
the command.
* You run the command as: koji save-failed-tree <failed-taskid>
I hope that this will be of use to help maintainers track down hard to
isolate bugs when all other means fail.
kevin
2 years, 3 months
Fedora 35 Change: Autoconf-2.71 (Self-Contained Change proposal)
by Ben Cotton
https://fedoraproject.org/wiki/Changes/Autoconf_271
== Summary ==
Autoconf upgrade from version 2.69 to the last upstream version 2.71 in Fedora.
== Owner ==
* Name: [[User:odubaj| Ondrej Dubaj]]
* Email: odubaj(a)redhat.com
== Detailed Description ==
Upgrading autoconf from version 2.69 to version 2.71 according to new
upstream release. Version 2.70 is skipped due to multiple ABI
incompatibilities, where some of them were fixed in version 2.71.
Years of development differ these two releases, so problems are
expected.
This change might easily cause fails during builds of multiple
packages, as some of them still require autoconf-2.69. This step must
be properly discussed with maintainers of dependent packages, which
should forward this change proposal to their upstream projects.
== Benefit to Fedora ==
Brings a stable and up-to-date version of autoconf according to
upsteam release. It is expected, that in the future many upstream
development teams will use autoconf-2.71 as their default builder, so
Fedora will be prepared for such a step.
== Scope ==
* Proposal owners:
**Prepare autoconf-2.71 as RPM package for Fedora Rawhide
**Check software that requires `autoconf` or `autoconf-2.69` and
rebuild it with autoconf-2.71
**Build autoconf-2.71 to Rawhide in a side-tag
(https://fedoraproject.org/wiki/Package_update_HOWTO#Creating_a_side-tag)
**Rebuild depended packages with autoconf-2.71 in the side-tag
**Merge the side-tag to Rawhide
* Other developers:
**Check if their packages can be build with autoconf-2.71
* Release engineering: [https://pagure.io/releng/issues #Releng issue number]
* Policies and guidelines: N/A (not needed for this Change)
* Trademark approval: N/A (not needed for this Change)
* Alignment with Objectives:
== Upgrade/compatibility impact ==
Problems during build can appear in multiple packages what can lead to
build failure, as multiple packages require autoconf-2.69 as their
upstream dependency. These problems have to be resolved before adding
autoconf-2.71 into Fedora. It seems aprox. 20% of dependent packages
are having problems during build, which could be caused by a problem
with same pattern.
== How To Test ==
Rebuilding your packages with autoconf-2.71 dependency in copr
(https://copr.fedorainfracloud.org/coprs/odubaj/autoconf-2.70/).
Mass rebuild of dependent packages in a side tag.
== User Experience ==
Users will be able to use the newer version (2.71) of autoconf, and
building packages with autoconf-2.69 won't be available, as it won't
be present on the specific fedora version. This can affect 3rd partly
packages, which are not part of Fedora.
== Dependencies ==
Hundreds of packages have build dependency on autoconf, therefore it
is a huge step forward for Fedora, what should be properly discussed
and tested. List of dependent packages with their ability to be built
with autoconf-2.71 can be found in the given copr project
(https://copr.fedorainfracloud.org/coprs/odubaj/autoconf-2.70/packages/)
We should also look at dependent packages of `libtool` and `automake`
(other critical autotools packages), as there might be some
incompatibilities with the new autoconf version.
== Contingency Plan ==
* Contingency mechanism: moving this change to Fedora 36, if not
successfully finished until Fedora 35 branching from Rawhide
* Contingency deadline: Fedora 35 branching from Rawhide (2021-08-10)
* Blocks release? No
== Documentation ==
Latest autoconf documentation:
https://www.gnu.org/savannah-checkouts/gnu/autoconf/manual/autoconf-2.70/...
== Release Notes ==
Release notes for autoconf-2.70:
https://lists.gnu.org/archive/html/autotools-announce/2020-12/msg00001.html
Release notes for autoconf-2.71:
https://lists.gnu.org/archive/html/autotools-announce/2021-01/msg00000.html
--
Ben Cotton
He / Him / His
Senior Program Manager, Fedora & CentOS Stream
Red Hat
TZ=America/Indiana/Indianapolis
2 years, 3 months
Stale provenpackagers to be removed from group
by Ben Cotton
In accordance with the new FESCo policy[1] the following
provenpackagers will be submitted for removal in two weeks based on a
lack of builds submitted in the last six months. If you received this
directly, you can reply off-list to indicate you believe you should
still have provenpackager status.
This is the first time we have done a regular audit of the
provenpackagers group, so please be patient with any hiccups in the
process. This will be done regularly at the branch point in each
release.
[1] https://pagure.io/fesco/issue/2549
Checked 252 provenpackagers
The following 117 provenpackagers have not submitted a Koji build
since at least 2020-08-05 00:00:00:
alexl
alexlan
arg
athimm
atkac
ausil
averi
awjb
bernie
bkabrda
bpepple
c4chris
caillon
cebbert
chitlesh
codeblock
cweyl
cwickert
davej
dbhole
dcbw
denis
dgregor
dmalcolm
drago01
dsd
dwmw2
echevemaster
ecik
ensc
epienbro
fitzsim
gemi
hguemar
hubbitus
huzaifas
ianweller
iarnell
ilianaw
ishcherb
ivazquez
ixs
jcapik
jhogarth
jkeating
johnp
jpo
jreznik
jspaleta
jstanley
jsteffan
jwilson
kanarip
kasal
katzj
kay
ke4qqq
kengert
kyle
kylev
laxathom
lennart
lkundrak
lmacken
lutter
markmc
maxamillion
mbarnes
mclasen
mef
michich
mjakubicek
mjg59
mmahut
mmaslano
mmcgrath
msimacek
mstuchli
nalin
nim
npmccallum
overholt
paragn
patches
pertusus
pjp
praveenp
pravins
rakesh
rkuska
rvokal
s4504kr
scop
sdake
sdz
skvidal
smooge
sochotni
stahnma
steve
sundaram
thias
thomasvs
thozza
till
tomspur
toshio
tradej
tremble
tstclair
tuxbrewr
vakwetu
vicodan
wart
willb
wolfy
wtogami
The following 1 provenpackagers do not exist in Koji:
gdk
--
Ben Cotton
He / Him / His
Senior Program Manager, Fedora & CentOS Stream
Red Hat
TZ=America/Indiana/Indianapolis
2 years, 3 months
Fedora 34 Mass Branching
by Mohan Boddu
Hello All,
Fedora 34 will be branched from rawhide on Feb 09th 2021 as per the
Fedora 34 schedule[1]. The process takes about a day and everything
should be ready by Feb 10th 2021. You can still be able to build
packages normally until then, but after the mass branching, rawhide
and F34 will be separated.
We will send another email once the branching is done.
Thanks,
Mohan Boddu.
[1] https://fedorapeople.org/groups/schedule/f-34/f-34-key-tasks.html
2 years, 3 months
