Proposing an EPEL packaging SIG
by Michel Alexandre Salim
Hello all,
Following up from last week's EPEL Steering Committee meeting, I'm
presenting a proposal to create a dedicated SIG to make it easier to
get Fedora packages into EPEL and keep them maintained.
Using the Fedora Changes Process template for this to help structure
the proposal, though this is not really a Fedora Change.
== Summary ==
Have a dedicated SIG for packagers who are interested in making more
Fedora packages available for EPEL releases.
== Owner ==
* Name: [[User:salimma|Michel Salim]]
* Email: <michel(a)michel-slm.name>
== Detailed Description ==
RHEL/CentOS releases are branched off from Fedora; since RHEL 8 this
happens every 3 years. Only a subset of Fedora packages get shipped as
part of RHEL, as Red Hat provides support on these packages for their
paying customers; EPEL (Extra Packages for Enterprise Linux) fills in
the gap; this is similar to the old split between Fedora Core and
Extras.
EPEL packages are maintained in dist-git as additional branches on
Fedora packages; however, unlike with Fedora releases, where by default
a package gets branched for any new Fedora release, EPEL branches are
only created if one of the package maintainers request it (it's opt-
in).
The rationale is that many Fedora packagers do not specifically care
about EL, and with their long release cycles the maintenance burden is
higher (e.g. upgrading to fix a security vulnerability might not be
possible if the newer fixed version has unmet dependencies, so
backporting the fix might be required). EL is more often used server
side too, so the average Fedora packager is not expected to be an EL
user.
This poses a problem for those of us who rely on packages in EPEL --
e.g. Fedora Infrastructure, and many corporate deployments. Right now
the process is as such:
* An org starts rolling out the new version of EL
* It turns out a given package is not available in EPEL
* Bug filed requesting that package be branched and built
* Worst case scenario, no response and we need to use the non-
responsive maintainer flow
* That package might have other unmet dependencies, so repeat this
cycle several times
* Wait for each of these packages to go through the update system
* For organizations that have their own internal mirrors, they now need
to sync the new packages
There are several changes we can make to both streamline the process,
and not increase the maintenance burden on the (other) maintainers of
these packages:
* Have an EPEL SIG modeled after the SIGs centered around programming
language stacks (e.g. Python, Haskell, Java)
* Have an expedited flow where this SIG can request EPEL branches and
admin access to packages if there are no response from package
maintainers for a set period (3 days? 1 week?)
* whether it should be full admin access or whether such access
should be scoped to epel* branches can be discussed. Full admin would
make it possible to adjust the spec in Rawhide to be more EPEL
friendly, for example
* Members of the EPEL SIG can then branch these packages early when the
next EL release is branched
* The member of the SIG doing the branching should be designated as the
primary EPEL assignee for that package
One deviation we might want to have from how Python SIG works is... we
probably don't want to encourage packagers to add this EPEL SIG as a
comaintainer preemptively, but only as needed.
== Benefit to Fedora ==
=== Smoother infra upgrades ===
Upgrading the Fedora infrastructure will get easier over time, as more
of the necessary EPEL packages become co-maintained by the EPEL SIG,
which reduces the amount of time needed to get these packages available
on new releases.
=== Packager experience ===
Reduced burden on Fedora package maintainers who are not interested in
EPEL - the choice is now either:
* One of the existing maintainers does the work of branching and
building
* The requestee gets added as a maintainer and does it
* The request stalls because the requestee is not a packager
=== More involvement by CentOS-using organizations ===
With the EPEL SIG, we should encourage organizations with a long-term
need for EPEL to get their members / employees added to this SIG, so
scenarios #2 and #3 basically becomes this:
* EPEL SIG gets added as co-maintainer of this package
This might encourage more contributions from companies that
traditionally just consume RHEL/CentOS + EPEL, and as RHEL/CentOS is
increasingly developed in the open with CentOS-Stream, eventually also
make it easier to get these companies' input into the EL development
process.
== Scope ==
* Proposal Owners
* Ask Infra to set up EPEL SIG ACL and mailing list (for Bugzilla)
* Announce this in epel-devel
* Have documentation for the SIG as part of the EPEL documentation
* Help onboard people to this SIG
--
Michel Alexandre Salim
profile: https://keyoxide.org/michel@michel-slm.name
chat via email: https://delta.chat/
GPG key: 5DCE 2E7E 9C3B 1CFF D335 C1D7 8B22 9D2F 7CCC 04F2
3 years, 7 months
Schedule for Wednesday's FESCo Meeting (2020-09-16)
by Clement Verna
Following is the list of topics that will be discussed in the
FESCo meeting Wednesday at 14:00UTC in #fedora-meeting-2 on
irc.freenode.net.
To convert UTC to your local time, take a look at
http://fedoraproject.org/wiki/UTCHowto
or run:
date -d '2020-09-16 14:00 UTC'
Links to all issues to be discussed can be found at:
https://pagure.io/fesco/report/meeting_agenda
= Discussed and Voted in the Ticket =
#2469 F34 Self-Contained Change: Python Upstream Architecture Names
https://pagure.io/fesco/issue/2469
APPROVED (+5, 0, 0)
#2466 Nonresponsive maintainer: Jon Disnard parasense
https://pagure.io/fesco/issue/2466
APPROVED (+4, 0, 0)
= Followups =
= New business =
= Open Floor =
For more complete details, please visit each individual
issue. The report of the agenda items can be found at
https://pagure.io/fesco/report/meeting_agenda
If you would like to add something to this agenda, you can
reply to this e-mail, file a new issue at
https://pagure.io/fesco, e-mail me directly, or 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.
_______________________________________________
devel mailing list -- devel(a)lists.fedoraproject.org
To unsubscribe send an email to devel-leave(a)lists.fedoraproject.org
Fedora Code of Conduct:
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives:
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
3 years, 7 months
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 be retired 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-2020-09-14.txt
grep it for your FAS username and follow the dependency chain.
For human readable dependency chains, see https://packager.fedorainfracloud.org/
For all orphaned packages, see https://packager.fedorainfracloud.org/orphan
Package (co)maintainers Status Change
================================================================================
apache-commons-dbcp mizdebsk, orphan 4 weeks ago
dbus-java orphan 5 weeks ago
fedora-icon-theme orphan 1 weeks ago
freight orphan 1 weeks ago
fst orphan 6 weeks ago
geronimo-parent-poms jjelen, mizdebsk, orphan 4 weeks ago
golang-github-mholt- orphan 3 weeks ago
certmagic-0.9
jboss-interceptors-1.2-api orphan 0 weeks ago
joda-time mizdebsk, orphan 4 weeks ago
js-jquery-iframe-transport orphan 5 weeks ago
js-jquery-knob orphan 5 weeks ago
js-jquery-qrcode orphan 5 weeks ago
js-tag-it orphan 5 weeks ago
jvnet-parent mizdebsk, orphan 3 weeks ago
libmatthew-java orphan 5 weeks ago
liquibase awood, orphan 5 weeks ago
log4j12 mizdebsk, orphan 0 weeks ago
man-pages-de orphan, romal 6 weeks ago
marble-widget orphan, rdieter 2 weeks ago
mozilla-iot-gateway-addon-node orphan 6 weeks ago
mozilla-iot-gateway-addon- orphan 6 weeks ago
python
nodejs-babel-code-frame orphan 1 weeks ago
nodejs-base orphan 1 weeks ago
nodejs-bcrypt nodejs-sig, orphan 1 weeks ago
nodejs-body-parser orphan 1 weeks ago
nodejs-bufferutil nodejs-sig, orphan 1 weeks ago
nodejs-cache-base orphan 1 weeks ago
nodejs-call-matcher orphan 1 weeks ago
nodejs-cross-spawn nodejs-sig, orphan 1 weeks ago
nodejs-cross-spawn-async nodejs-sig, orphan 1 weeks ago
nodejs-css-stringify nodejs-sig, orphan, patches 3 weeks ago
nodejs-css-tree orphan 3 weeks ago
nodejs-doctrine galileo, nodejs-sig, orphan, 1 weeks ago
vjancik
nodejs-espower-location- orphan 3 weeks ago
detector
nodejs-esrecurse nodejs-sig, orphan 1 weeks ago
nodejs-faucet orphan 1 weeks ago
nodejs-fs-dot-notify orphan 1 weeks ago
nodejs-gauge nodejs-sig, orphan 1 weeks ago
nodejs-global-prefix nodejs-sig, orphan 1 weeks ago
nodejs-grunt nodejs-sig, orphan, patches, 3 weeks ago
piotrp
nodejs-grunt-legacy-util nodejs-sig, orphan, patches, 1 weeks ago
piotrp
nodejs-http-signature nodejs-sig, orphan, patches 0 weeks ago
nodejs-jsonm nodejs-sig, orphan 1 weeks ago
nodejs-jsonstream nodejs-sig, orphan 1 weeks ago
nodejs-markdown-it-testgen nodejs-sig, orphan 1 weeks ago
nodejs-node-static nodejs-sig, orphan, tdawson 0 weeks ago
nodejs-nopt nodejs-sig, orphan, patches 0 weeks ago
nodejs-option-cache orphan 1 weeks ago
nodejs-raw-body nodejs-sig, orphan, patches 1 weeks ago
nodejs-rechoir nodejs-sig, orphan 1 weeks ago
nodejs-require-yaml nodejs-sig, orphan 1 weeks ago
nodejs-rfile orphan 1 weeks ago
nodejs-rollup-plugin-commonjs orphan 1 weeks ago
nodejs-rollup-plugin-node- orphan 1 weeks ago
resolve
nodejs-snapdragon orphan 3 weeks ago
nodejs-socket-dot-io-parser orphan 1 weeks ago
nodejs-tap-mocha-reporter nodejs-sig, orphan 1 weeks ago
nodejs-tap-parser nodejs-sig, orphan 1 weeks ago
plexus-ant-factory mizdebsk, orphan 2 weeks ago
plexus-component-factories-pom mizdebsk, orphan 2 weeks ago
python-jose orphan 0 weeks ago
python-kaptan bowlofeggs, jcline, orphan 4 weeks ago
python-libtmux orphan 4 weeks ago
python-nnpy orphan 6 weeks ago
python-zope-configuration infra-sig, orphan, tdabasin 1 weeks ago
qrcode-generator orphan 5 weeks ago
rdesktop alexl, caillon, caolanm, cra, 0 weeks ago
fab, gnome-sig, johnp,
mbarnes, orion, orphan,
rhughes, rstrode, ssp
relaxngDatatype dbhole, mizdebsk, orphan 2 weeks ago
relaxngcc orphan 2 weeks ago
rmic-maven-plugin mizdebsk, orphan 4 weeks ago
rubygem-delayed_job orphan 3 weeks ago
rubygem- orphan 3 weeks ago
delayed_job_active_record
rubygem-jgrep lkundrak, orphan, stevetraylen 1 weeks ago
rubygem-org-ruby orphan 3 weeks ago
rubygem-paint orphan 1 weeks ago
rubygem-rkerberos orphan 1 weeks ago
rubygem-rubypants orphan 3 weeks ago
rubygem-sigdump orphan 4 weeks ago
rubygem-wikicloth orphan 5 weeks ago
rubygem-wirb orphan 1 weeks ago
sonatype-oss-parent mizdebsk, orphan 3 weeks ago
umlgraph orphan 1 weeks ago
The following packages require above mentioned packages:
Report too long, see the full version at
https://churchyard.fedorapeople.org/orphans-2020-09-14.txt
See dependency chains of your packages at https://packager.fedorainfracloud.org/
See all orphaned packages at https://packager.fedorainfracloud.org/orphan
Affected (co)maintainers (either directly or via packages' dependencies):
abompard: python-zope-configuration
akurtakov: log4j12
alexl: rdesktop
anishpatil: nodejs-css-stringify
awood: liquibase
bowlofeggs: python-kaptan
caillon: rdesktop
caolanm: rdesktop
cipherboy: log4j12
clime: nodejs-grunt, nodejs-nopt, nodejs-grunt-legacy-util
coolsvap: geronimo-parent-poms, log4j12
copr-sig: nodejs-grunt, nodejs-nopt, nodejs-grunt-legacy-util
cqi: python-jose
cra: rdesktop
dbhole: relaxngDatatype
dcallagh: nodejs-css-stringify
decathorpe: log4j12
djuran: log4j12
dmoluguw: log4j12
dturecek: nodejs-grunt, nodejs-nopt, nodejs-grunt-legacy-util
echevemaster: rdesktop
eclipse-sig: log4j12
edewata: log4j12
fab: nodejs-rechoir, nodejs-css-stringify, rdesktop
fnasser: log4j12
frostyx: nodejs-grunt, nodejs-nopt, nodejs-grunt-legacy-util
galileo: nodejs-doctrine, log4j12
gil: geronimo-parent-poms, log4j12
gnome-sig: rdesktop
ignatenkobrain: python-libtmux, python-kaptan
infra-sig: python-zope-configuration
java-maint-sig: log4j12
jcline: python-kaptan
jdeluyck: nodejs-rechoir
jjames: jvnet-parent
jjelen: geronimo-parent-poms, jboss-interceptors-1.2-api, jvnet-parent, log4j12,
apache-commons-dbcp
johnp: rdesktop
jpokorny: relaxngDatatype
jsmith: nodejs-global-prefix, nodejs-cache-base, nodejs-base,
nodejs-grunt-legacy-util, nodejs-rollup-plugin-node-resolve, nodejs-cross-spawn,
nodejs-css-stringify, nodejs-css-tree, nodejs-snapdragon, nodejs-rechoir,
nodejs-cross-spawn-async, nodejs-grunt, nodejs-nopt
kwright: log4j12
lbazan: rdesktop
lef: jvnet-parent
lkundrak: rubygem-jgrep
luya: nodejs-css-tree
mbarnes: rdesktop
mbooth: log4j12
mharmsen: log4j12
mizdebsk: geronimo-parent-poms, joda-time, jvnet-parent, plexus-ant-factory,
log4j12, relaxngDatatype, sonatype-oss-parent, rmic-maven-plugin,
plexus-component-factories-pom, apache-commons-dbcp
mmorsi: log4j12, joda-time
moceap: geronimo-parent-poms, log4j12
mso: fedora-icon-theme
msuchy: nodejs-grunt, nodejs-nopt, nodejs-grunt-legacy-util
neuro-sig: sonatype-oss-parent
nodejs-sig: nodejs-tap-parser, nodejs-gauge, nodejs-cross-spawn,
nodejs-esrecurse, nodejs-node-static, nodejs-require-yaml,
nodejs-tap-mocha-reporter, nodejs-http-signature, nodejs-grunt-legacy-util,
nodejs-snapdragon, nodejs-bufferutil, nodejs-bcrypt, nodejs-global-prefix,
nodejs-css-stringify, nodejs-jsonstream, nodejs-css-tree, nodejs-raw-body,
nodejs-doctrine, nodejs-jsonm, nodejs-grunt, nodejs-nopt, nodejs-rechoir,
nodejs-cross-spawn-async, nodejs-markdown-it-testgen
orion: rdesktop
patches: nodejs-http-signature, nodejs-grunt-legacy-util, nodejs-css-stringify,
nodejs-rechoir, nodejs-raw-body, nodejs-grunt, nodejs-nopt
piotrp: nodejs-grunt-legacy-util, nodejs-css-stringify, nodejs-jsonstream,
nodejs-grunt, nodejs-nopt
praiskup: nodejs-grunt, nodejs-nopt, nodejs-grunt-legacy-util
pwalter: rdesktop
rdieter: marble-widget
rhughes: rdesktop
romal: man-pages-de
rstrode: rdesktop
sagitter: nodejs-rechoir
sdgathman: sonatype-oss-parent, nodejs-nopt
sergiomb: nodejs-css-stringify, js-jquery-iframe-transport
spike: geronimo-parent-poms, log4j12
ssp: rdesktop
stevetraylen: rubygem-jgrep
tc01: nodejs-grunt-legacy-util, jvnet-parent, nodejs-css-stringify, nodejs-nopt,
log4j12, nodejs-bufferutil, relaxngDatatype, nodejs-raw-body, nodejs-grunt,
nodejs-body-parser
tdabasin: python-zope-configuration
tdawson: nodejs-node-static
vakwetu: log4j12
vjancik: nodejs-doctrine, nodejs-css-stringify
xavierb: nodejs-grunt, nodejs-nopt, nodejs-grunt-legacy-util
zbyszek: sonatype-oss-parent
zvetlik: nodejs-css-stringify
--
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/master/f/scripts/find_unblocked_orphans.py
3 years, 7 months
Paralel dependencyj (Re: kalev pushed to gnome-shell (master). "Add
missing pipewire-gstreamer dependency for screen recorder (..more)")
by Tomasz Kłoczko
On Wed, 9 Sep 2020 at 19:47, <notifications(a)fedoraproject.org> wrote:
> @@ -90,6 +90,8 @@ Requires: gnome-desktop3%{?_isa} >=
> %{gnome_desktop_version}
> Requires: glib2%{?_isa} >= %{glib2_version}
> Requires: gsettings-desktop-schemas%{?_isa} >=
> %{gsettings_desktop_schemas_version}
> Requires: gstreamer1%{?_isa} >= %{gstreamer_version}
> +# needed for screen recorder
> +Requires: pipewire-gstreamer%{?_isa}
> # needed for schemas
> Requires: at-spi2-atk%{?_isa}
> # needed for on-screen keyboard
> @@ -212,6 +214,9 @@ desktop-file-validate
> %{buildroot}%{_datadir}/applications/evolution-calendar.de
> %{_mandir}/man1/gnome-shell.1*
>
> %changelog
> +* Wed Sep 09 2020 Kalev Lember <klember(a)redhat.com> - 3.37.92-4
> +- Add missing pipewire-gstreamer dependency for screen recorder
> +
> * Sun Sep 06 2020 Florian Müllner <fmuellner(a)redhat.com> - 3.37.92-1
> - Update to 3.37.92
>
What is the point to add yet another fixed dependency in gnome-shell
instead *just .. *remove separation between piperwite and
piperwire-gstreamer? Isn't it?
That separation in piiperwire seems now to be causing only some other
ripples of the manually added dependencies like that one🤔
KISS .. please
I'm almost sure that I saw at least a few more similar connections in the
last couple of years. Someone should start looking for that kind of
duplicated dependency by just analysing the network/graph of those
dependencies. All that needs to be processed are only those added by
static/fixed *Requires* token.
Probably it would be even possible to use some (already existing) software
to perform such analysis automatically.
The first similar package which comes to my mind with that kind of ODS
("oversubpackaking disorder syndrome") is udisk2 but there are much more
like udisk2 one in Fedora.
(Probably it would be better to name/classify that kind of dependency as
"parallel dependency")
kloczek
--
Tomasz Kłoczko | LinkedIn: http://lnkd.in/FXPWxH
3 years, 7 months