Fedora 33 Beta Go/No-Go tomorrow
by Ben Cotton
Hi everyone,
No cancelations this time! The Fedora 33 Beta Go/No-Go[1] meeting is
scheduled for Thursday 24 September. We will meet at 1700 UTC in
#fedora-meeting-1 to determine if we will release Fedora 33 Beta.
[1] https://apps.fedoraproject.org/calendar/meeting/9810/
--
Ben Cotton
He / Him / His
Senior Program Manager, Fedora & CentOS Stream
Red Hat
TZ=America/Indiana/Indianapolis
3 years, 6 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-21.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 5 weeks ago
fedora-icon-theme orphan 2 weeks ago
freight orphan 2 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 1 weeks ago
joda-time mizdebsk, orphan 5 weeks ago
jvnet-parent mizdebsk, orphan 4 weeks ago
log4j12 mizdebsk, orphan 1 weeks ago
marble-widget orphan, rdieter 3 weeks ago
nodejs-babel-code-frame orphan 2 weeks ago
nodejs-base orphan 2 weeks ago
nodejs-bcrypt nodejs-sig, orphan 2 weeks ago
nodejs-body-parser orphan 2 weeks ago
nodejs-bufferutil nodejs-sig, orphan 2 weeks ago
nodejs-cache-base orphan 2 weeks ago
nodejs-call-matcher orphan 2 weeks ago
nodejs-cross-spawn nodejs-sig, orphan 2 weeks ago
nodejs-cross-spawn-async nodejs-sig, orphan 2 weeks ago
nodejs-css-stringify nodejs-sig, orphan, patches 4 weeks ago
nodejs-css-tree orphan 4 weeks ago
nodejs-doctrine galileo, nodejs-sig, orphan, 2 weeks ago
vjancik
nodejs-espower-location- orphan 4 weeks ago
detector
nodejs-esrecurse nodejs-sig, orphan 2 weeks ago
nodejs-faucet orphan 2 weeks ago
nodejs-fs-dot-notify orphan 2 weeks ago
nodejs-gauge nodejs-sig, orphan 2 weeks ago
nodejs-global-prefix nodejs-sig, orphan 2 weeks ago
nodejs-grunt nodejs-sig, orphan, patches, 4 weeks ago
piotrp
nodejs-grunt-legacy-util nodejs-sig, orphan, patches, 2 weeks ago
piotrp
nodejs-http-signature nodejs-sig, orphan, patches 1 weeks ago
nodejs-jsonm nodejs-sig, orphan 2 weeks ago
nodejs-jsonstream nodejs-sig, orphan 2 weeks ago
nodejs-markdown-it-testgen nodejs-sig, orphan 2 weeks ago
nodejs-node-static nodejs-sig, orphan, tdawson 1 weeks ago
nodejs-nopt nodejs-sig, orphan, patches 1 weeks ago
nodejs-option-cache orphan 2 weeks ago
nodejs-raw-body nodejs-sig, orphan, patches 2 weeks ago
nodejs-rechoir nodejs-sig, orphan 2 weeks ago
nodejs-require-yaml nodejs-sig, orphan 2 weeks ago
nodejs-rfile orphan 2 weeks ago
nodejs-rollup-plugin-commonjs orphan 2 weeks ago
nodejs-rollup-plugin-node- orphan 2 weeks ago
resolve
nodejs-snapdragon orphan 4 weeks ago
nodejs-socket-dot-io-parser orphan 2 weeks ago
nodejs-tap-mocha-reporter nodejs-sig, orphan 2 weeks ago
nodejs-tap-parser nodejs-sig, orphan 2 weeks ago
plexus-ant-factory mizdebsk, orphan 3 weeks ago
plexus-component-factories-pom mizdebsk, orphan 3 weeks ago
python-jose orphan 1 weeks ago
python-kaptan bowlofeggs, jcline, orphan 5 weeks ago
python-libtmux orphan 5 weeks ago
python-zope-configuration infra-sig, orphan, tdabasin 2 weeks ago
relaxngDatatype dbhole, mizdebsk, orphan 3 weeks ago
relaxngcc orphan 3 weeks ago
rmic-maven-plugin mizdebsk, orphan 5 weeks ago
rubygem-delayed_job orphan 4 weeks ago
rubygem- orphan 4 weeks ago
delayed_job_active_record
rubygem-erubis orphan 0 weeks ago
rubygem-jgrep lkundrak, orphan, stevetraylen 2 weeks ago
rubygem-org-ruby orphan 4 weeks ago
rubygem-paint orphan 2 weeks ago
rubygem-rkerberos orphan 2 weeks ago
rubygem-rubypants orphan 4 weeks ago
rubygem-sigdump orphan 5 weeks ago
rubygem-wirb orphan 2 weeks ago
sonatype-oss-parent mizdebsk, orphan 4 weeks ago
umlgraph orphan 2 weeks ago
vdr-skinsoppalusikka orphan 0 weeks ago
winetricks orphan, raphgro, tc01 0 weeks ago
The following packages require above mentioned packages:
Report too long, see the full version at
https://churchyard.fedorapeople.org/orphans-2020-09-21.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
abradshaw: rubygem-erubis
amahdal: rubygem-erubis
anishpatil: nodejs-css-stringify
asrob: rubygem-erubis
athoscr: rubygem-erubis
besser82: rubygem-erubis
bowlofeggs: python-kaptan
brandfbb: rubygem-erubis
chrisw: rubygem-erubis
churchyard: rubygem-erubis
cicku: rubygem-erubis
ckyriakidou: rubygem-erubis
clime: nodejs-nopt, nodejs-grunt-legacy-util, nodejs-grunt
coolsvap: log4j12, geronimo-parent-poms
copr-sig: nodejs-nopt, nodejs-grunt-legacy-util, nodejs-grunt
cottsay: rubygem-erubis
cqi: python-jose
dbhole: relaxngDatatype
dcallagh: nodejs-css-stringify
decathorpe: rubygem-erubis
dfateyev: rubygem-erubis
djbw: rubygem-erubis
djuran: log4j12
dturecek: nodejs-nopt, nodejs-grunt-legacy-util, nodejs-grunt
evgeni: rubygem-erubis
fab: rubygem-erubis, nodejs-css-stringify, nodejs-rechoir
fale: rubygem-erubis
fnasser: log4j12
frostyx: nodejs-nopt, nodejs-grunt-legacy-util, nodejs-grunt
galileo: nodejs-doctrine
gchamoul: rubygem-erubis
germano: rubygem-erubis
gil: log4j12, geronimo-parent-poms
hguemar: rubygem-erubis
hobbes1069: rubygem-erubis
honzaf: rubygem-erubis
ignatenkobrain: python-kaptan, rubygem-erubis, python-libtmux
infra-sig: python-zope-configuration
irina: rubygem-erubis
jaruga: rubygem-erubis
jcline: python-kaptan
jdeluyck: nodejs-rechoir
jhli: rubygem-erubis
jhrozek: rubygem-erubis
jjames: jvnet-parent
jjelen: jboss-interceptors-1.2-api, geronimo-parent-poms, jvnet-parent,
apache-commons-dbcp, log4j12
jpokorny: rubygem-erubis, relaxngDatatype
jskarvad: rubygem-erubis
jsmith: nodejs-cross-spawn, nodejs-global-prefix, nodejs-snapdragon,
nodejs-grunt-legacy-util, nodejs-css-stringify, nodejs-rechoir,
nodejs-cross-spawn-async, nodejs-cache-base, nodejs-rollup-plugin-node-resolve,
nodejs-css-tree, nodejs-nopt, nodejs-base, nodejs-grunt
jstanek: rubygem-erubis
jussilehtola: rubygem-erubis
keitellf: rubygem-erubis
lef: jvnet-parent
lkundrak: rubygem-jgrep
luya: nodejs-css-tree
maha: rubygem-erubis
mizdebsk: sonatype-oss-parent, joda-time, rmic-maven-plugin,
geronimo-parent-poms, relaxngDatatype, jvnet-parent,
plexus-component-factories-pom, apache-commons-dbcp, plexus-ant-factory, log4j12
mmorsi: joda-time, rubygem-erubis
moceap: log4j12, geronimo-parent-poms
mojavelinux: rubygem-erubis
mso: fedora-icon-theme
msuchy: nodejs-nopt, nodejs-grunt-legacy-util, nodejs-grunt
neuro-sig: sonatype-oss-parent
ngompa: rubygem-erubis
niveusluna: rubygem-erubis
nodejs-sig: nodejs-gauge, nodejs-jsonstream, nodejs-rechoir, nodejs-css-tree,
nodejs-tap-parser, nodejs-jsonm, nodejs-require-yaml, nodejs-grunt-legacy-util,
nodejs-bufferutil, nodejs-node-static, nodejs-cross-spawn, nodejs-esrecurse,
nodejs-global-prefix, nodejs-snapdragon, nodejs-cross-spawn-async,
nodejs-tap-mocha-reporter, nodejs-bcrypt, nodejs-http-signature, nodejs-nopt,
nodejs-doctrine, nodejs-css-stringify, nodejs-grunt, nodejs-markdown-it-testgen,
nodejs-raw-body
nonamedotc: rubygem-erubis
olysonek: rubygem-erubis
patches: nodejs-grunt-legacy-util, nodejs-css-stringify, nodejs-rechoir,
nodejs-http-signature, nodejs-nopt, nodejs-grunt, nodejs-raw-body
pbrobinson: rubygem-erubis
pcahyna: rubygem-erubis
piotrp: nodejs-jsonstream, nodejs-grunt-legacy-util, nodejs-css-stringify,
nodejs-nopt, nodejs-grunt
pknirsch: rubygem-erubis
ppisar: rubygem-erubis
praiskup: nodejs-nopt, nodejs-grunt-legacy-util, nodejs-grunt
pstodulk: rubygem-erubis
raphgro: winetricks
rdieter: marble-widget
ruby-packagers-sig: rubygem-erubis
rust-sig: rubygem-erubis
sagitter: nodejs-rechoir
salimma: rubygem-erubis
sandeen: rubygem-erubis
sdgathman: nodejs-nopt, sonatype-oss-parent
sdyroff: rubygem-erubis
sergiomb: nodejs-css-stringify
simo: rubygem-erubis
skisela: rubygem-erubis
snecker: rubygem-erubis
spike: log4j12, geronimo-parent-poms
spontsle: rubygem-erubis
stevetraylen: rubygem-jgrep
stingray: rubygem-erubis
tc01: winetricks, relaxngDatatype, nodejs-grunt-legacy-util,
nodejs-css-stringify, nodejs-bufferutil, nodejs-nopt, nodejs-body-parser,
nodejs-grunt, jvnet-parent, nodejs-raw-body
tdabasin: python-zope-configuration
tdawson: nodejs-node-static
thias: rubygem-erubis
thm: rubygem-erubis
tmz: rubygem-erubis
tross: rubygem-erubis
valtri: rubygem-erubis
vishalv: rubygem-erubis
vjancik: nodejs-doctrine, nodejs-css-stringify
vondruch: rubygem-erubis
xavierb: nodejs-nopt, nodejs-grunt-legacy-util, nodejs-grunt
xenithorb: rubygem-erubis
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
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
F34 Change Proposal: Rust Crate Packages For Release Branches
(System-Wide Change)
by Ben Cotton
https://fedoraproject.org/wiki/Changes/Rust_Crate_Packages_For_Release_Br...
== Summary ==
This Change proposal aims to enable shipping Rust crate packages
(<code>rust-$CRATE_NAME</code>) on release branches of fedora.
Currently, they are only available for rawhide, which makes building
Rust packages for release branches difficult.
== Owner ==
* Name: [[User:decathorpe| Fabio Valentini]]
* Email: <decathorpe(a)gmail.com>
== Detailed Description ==
Following the general upwards trend in the Rust language's popularity,
more and more applications and services in fedora are written in Rust.
This includes some CoreOS services, PARSEC, some nice command line
tools (e.g. ripgrep, bat, fedora-update-feedback, ...), and parts of
the GNOME stack.
However, because rust crate packages are currently only available on
rawhide, packaging rust applications for release branches is difficult
and involves more steps than usual.
This Change proposal aims to bring Rust packaging in line with the
normal packaging workflows in fedora.
In particular, the following additional steps will become obsolete:
* use koji side tags for *every package build* on release branches
* manual tagging and untagging of koji buildroot contents
Instead, rust packages can be built like any other package in fedora.
== Benefit to Fedora ==
This Change lowers the bar for contributing to the Rust stack in
fedora, because it will no longer be a special case that involves
additional steps.
It will also make it possible to build Rust packages for release
branches locally in mock without the need for custom mock buildroot
configurations and / or third-party repositories.
== Scope ==
* Proposal owner(s):
** one-off change: submit PR to revert the special-case handling for
<code>rust-*</code> packages in the mass branching releng script
** ongoing effort: help package maintainers with merging changes from
rawhide (where appropriate) and creating compat packages (when
necessary) - this is made easier by the strong SemVer compatibility
guarantees of Rust crates
* Other developers:
Initially, there is no impact on other developers.
However, as soon as fedora 34 is branched, building Rust applications
on that release branch will be easier than without this change.
This will require packagers to merge rawhide updates into release
branches when appropriate (again, bringing Rust packaging in line with
the rest of fedora).
I also expect there to be reduced load on koji due less side tags
being in use concurrently, which will benefit all package maintainers
in fedora.
* Release engineering: [https://pagure.io/releng/issue/9753 #9753]
Release engineering will need to remove special-case handling of
<code>rust-*</code> packages from their mass branching script before
f34 is branched off of rawhide.
* Policies and guidelines:
The Rust packaging Guidelines will need small adaptations.
They are already outdated, so Change owner(s) will update them to the
current state of Rust packaging regardless.
* Trademark approval: N/A (not needed for this Change)
* Alignment with Objectives:
The fedora IoT Edition promotes PARSEC, which is comprised of Rust
packages - its package maintainers will benefit from being able to
update and build those packages faster and more easily for release
branches.
== Upgrade/compatibility impact ==
There will be no impact on upgrades from previous fedora releases,
since Rust crate packages will only be available for those users for
the first time.
If for some reason a user installed <code>rust-*-devel</code> packages
manually after downloading them from the rawhide repositories, they
will be gracefully upgraded.
== How To Test ==
Users should be able to build Rust applications for fedora 34 without
workarounds or special steps (both in mock locally and in koji - both
scratch and non-scratch builds).
== User Experience ==
Users should not notice this change. However, I expect some
application updates to be available for release branches faster, since
it will be easier for package maintainers to create them.
== Dependencies ==
N/A (this only affects the Rust package stack and has no external dependencies)
== Contingency Plan ==
* Contingency mechanism: untag and block <code>rust-*</code> packages
in the f34 tag in koji (help from releng / a koji admin required),
revert mass branching script changes before f35 branch point
* Contingency deadline: Final Freeze (removing packages from koji will
no longer be possible after this point)
* Blocks release? No (the initial Change is small and does not
negatively affect release process)
* Blocks product? N/A
== Documentation ==
The Packaging Guidelines for Rust will be updated to reflect this Change.
== Release Notes ==
TBD
--
Ben Cotton
He / Him / His
Senior Program Manager, Fedora & CentOS Stream
Red Hat
TZ=America/Indiana/Indianapolis
3 years, 7 months
stk update and soname change
by Thomas Moschny
The Synthesis ToolKit in C++ (STK) package has been updated to 4.6.1,
which includes an SONAME change from "libstk.so.4" to "libstk-4.6.1.so".
The stk package has been built in side tag f34-build-side-29971, which
will be merged to f34 in about a week.
Packages that need to be rebuilt:
csound-0:6.15.0-1.fc34.src
lmms-0:1.1.3-19.fc33.src
lv2-newtonator-0:0.6.0-20.fc33.src
I will take care of lmms, other package maintainers cc'ed.
- Thomas
3 years, 7 months
F34 Change proposal: Wayland by Default for KDE Plasma Desktop
(System-Wide Change)
by Ben Cotton
https://fedoraproject.org/wiki/Changes/WaylandByDefaultForPlasma
== Summary ==
Change the default session selection in SDDM to prefer the
Wayland-based KDE Plasma Desktop session over the X11-based one.
== Owner ==
* Name: [[User:Ngompa|Neal Gompa]], [[User:Rdieter|Rex Dieter]],
[[User:Jgrulich|Jan Grulich]]
* Email: ngompa13(a)gmail.com, rdieter(a)gmail.com, jgrulich(a)redhat.com
* Product: KDE Spin
* Responsible WG: KDE SIG
== Detailed Description ==
With KDE Plasma 5.20, the KDE Plasma desktop environment has reached a
point where nearly all commonly used features in the desktop and all
major applications function in the Plasma Wayland environment on all
major GPUs (including NVIDIA with the proprietary driver). Starting
with Plasma 5.20 in Fedora 34, we will change the default
configuration for Wayland and X11 Plasma sessions so that Wayland is
preferred and used by default, while permitting the X11 session to be
selected as the alternative desktop environment option.
== Feedback ==
==== Is Wayland ready? ====
Wayland has been used by default for Fedora Workstation (which uses
GNOME) since Fedora 25. And while it was somewhat immature initially,
today it is a very rock-solid experience on virtually everything
Fedora Workstation runs on. The change in Fedora 25 kickstarted the
drive to get everything working on Wayland, and the Workstation team
succeeded beyond their wildest dreams. Firefox has been Wayland-native
by default since Fedora 31 as well.
On the KDE side, serious work into supporting Wayland started shortly
after GNOME switched to Wayland by default. Unlike GNOME, KDE has a
much broader stack in its toolkit, and it has taken longer to get to a
usable state. With the Plasma 5.20 release, the Wayland protocol for
screencasting as well as middle-click paste finally are supported,
completing the required feature set for switching to Wayland by
default.
==== What about NVIDIA? ====
Plasma, in fact, ''does'' support NVIDIA GPUs with the proprietary
driver on Wayland. It needs to be manually activated, which will be
taken care of by the <code>kwin-wayland-nvidia</code> package. So the
expectation is that all major GPUs will work just fine.
==== Why not keep using X11? ====
The fact of the matter is, Xorg is in
[https://blogs.gnome.org/uraeus/2019/06/24/on-the-road-to-fedora-workstati...
"hard maintenance mode"] per [[User:Uraeus|Christian Schaller]] and
development on it has basically stopped beyond the most critical of
fixes. Combined with the rapid maturation of the Wayland session in
KDE Plasma, this is the best time to make the switch and push things
over the edge for the KDE ecosystem in the same way that Fedora
Workstation did for the GNOME ecosystem.
== Benefit to Fedora ==
Fedora has long been a leader in advancing the adoption of the Wayland
protocol as part of the overall strategy to improve the Linux
graphical software stack. Much of the quality of Wayland for GNOME can
be attributed to the work done by the Fedora Workstation WG as part of
advancing the GNOME platform. It is now the KDE SIG's turn to do the
same for the KDE platform. By making this change, we are helping push
the adoption forward for newer, more streamlined, and overall more
actively developed graphics technology for the KDE ecosystem.
== Scope ==
* Proposal owners:
** Modify {{package|kwin}} to switch to Wayland
*** Split out <code>/usr/bin/kwin_x11</code> to the
<code>kwin-x11</code> subpackage.
*** Make {{package|kwin}} require <code>kwin-wayland</code> and
recommend <code>kwin-x11</code>
*** Add <code>kwin-wayland-nvidia</code> subpackage which contains
<code>/usr/lib/environment.d/10-kwin-wayland-nvidia.conf</code> to set
<code>$KWIN_DRM_USE_EGL_STREAMS</code> to <code>1</code>. This package
will have have a Supplements dependency <code>(kwin-wayland and
kmod-nvidia)</code>.
** Modify {{package|plasma-workspace}} to switch to Wayland
*** Rename <code>/usr/share/xsessions/plasma.desktop</code> to
<code>/usr/share/xsessions/plasma-xorg.desktop</code>, subpackage it
out as <code>plasma-workspace-xorg</code>, and have it require
<code>kwin-x11</code>
*** Rename <code>/usr/share/wayland-sessions/plasmawayland.desktop</code>
to <code>/usr/share/wayland-sessions/plasma.desktop</code>
*** Make {{package|plasma-workspace}} require
<code>plasma-workspace-wayland</code> and recommend
<code>plasma-workspace-xorg</code>
** Modify <code>@kde-desktop</code> comps group for Fedora 34 to
include <code>plasma-workspace-xorg</code> for the media.
* Other developers: N/A (not applicable for this Change)
* Release engineering: [https://pagure.io/releng/issue/9741 #9741]
* Policies and guidelines: N/A (not needed for this Change)
* Trademark approval: N/A (not needed for this Change)
* Alignment with Objectives: N/A (not applicable for this Change)
== Upgrade/compatibility impact ==
Systems using certain (very old) graphics hardware or graphics drivers
(matrox, etc.) may have problems running the Wayland session. In these
(rare) cases, users may have to configure SDDM to use X11.
== How To Test ==
Log into a KDE Plasma desktop. Do any activity you would normally do
in your daily desktop use: launching applications, configuring
displays, etc. Things should work the same way under Wayland as they
used to under X.
== User Experience ==
The user experience should not change noticeably.
== Dependencies ==
This mainly affects the {{package|plasma-workspace}} and
{{package|kwin}} packages, and details for the changes for those
packages are described in the Scope section.
== Contingency Plan ==
* Contingency mechanism: Revert the file renames and switch
<code>plasma-workspace-xorg</code> to be the required package instead
of <code>plasma-workspace-wayland</code>
* Contingency deadline: beta freeze
* Blocks release? Yes
* Blocks product? KDE Spin
== Documentation ==
Some upstream documents about Wayland
* https://community.kde.org/Plasma/Wayland
* https://community.kde.org/KWin/Wayland
There is currently no coherent up to date documentation about Plasma Wayland.
== Release Notes ==
The KDE Plasma Desktop is using the Wayland display system now. X
applications will continue to run transparently through XWayland.
--
Ben Cotton
He / Him / His
Senior Program Manager, Fedora & CentOS Stream
Red Hat
TZ=America/Indiana/Indianapolis
3 years, 7 months
F34 Change proposal: Remove support for SELinux runtime disable
(System-Wide Change)
by Ben Cotton
https://fedoraproject.org/wiki/Changes/Remove_Support_For_SELinux_Runtime...
== Summary ==
Remove support for SELinux runtime disable so that the LSM hooks can
be hardened via read-only-after-initialization protections.
Migrate users to using ''selinux=0'' if they want to disable SELinux.
== Owner ==
* Name: [[User:plautrba| Petr Lautrbach]]
* Email: plautrba(a)redhat.com
* Name: [[User:omos| Ondrej Mosnacek]]
* Email: omosnace(a)redhat.com
== Detailed Description ==
Support for SELinux runtime disable via ''/etc/selinux/config'' was
originally developed to make it easier for Linux distributions to
support architectures where adding parameters to the kernel command
line was difficult.
Unfortunately, supporting runtime disable meant we had to make some
security trade-offs when it comes to the kernel LSM hooks.
Marking the kernel LSM hooks as read only provides some very nice
security benefits, but it does mean that we can no longer disable
SELinux at runtime.
Toggling between enforcing and permissive mode while booted will
remain unaffected and it will still be possible to disable SELinux by
adding ''selinux=0'' to the kernel command line via the boot loader
(GRUB).
System with ''SELINUX=disabled'' in ''/etc/selinux/config'' will come
up with ''/sys/fs/selinuxfs'' unmounted,
userspace will detect SELinux as disabled. Internally SELinux will be
enabled but not initialized so that there will be no SELinux checks
applied.
NOTE: Runtime disable is considered deprecated by upstream, and using
it will become increasingly painful (e.g. sleeping/blocking) through
future kernel releases until eventually it is removed completely.
Current kernel reports the following message during runtime disable:
''SELinux: Runtime disable is deprecated, use selinux=0 on the kernel
cmdline''
Additional info:
* https://lwn.net/Articles/666550
* https://lore.kernel.org/selinux/159110207843.57260.5661475689740939480.st...
* https://lore.kernel.org/selinux/157836784986.560897.13893922675143903084....
== Benefit to Fedora ==
Marking the LSM hooks as read-only provides extra security hardening
against certain attacks, e.g. in case an attacker gains ability to
write to random kernel memory locations, with support for disable
SELinux runtime (''CONFIG_SECURITY_SELINUX_DISABLE=y'') they have a
bigger chance to turn off (parts of) SELinux permission checking.
== Scope ==
* Proposal owners:
** Make sure the kernel is built with
''CONFIG_SECURITY_SELINUX_DISABLE'' disabled.
** Make sure the relevant documentation is updated in a way that
''selinux=0'' on kernel command line is the preferred way to disable
SELinux.
*** https://docs.fedoraproject.org/en-US/quick-docs/changing-selinux-states-a...
*** ''selinux(8)'' man page
** Make sure [https://github.com/rhinstaller/anaconda/ the installer]
uses the kernel command line instead of ''/etc/selinux/config'' to
disable SELinux.
** Optional: [https://github.com/ansible/ansible/blob/devel/lib/ansible/module_utils/fa...
''selinux'' Ansible module] should warn that SELinux needs to be
disabled using ''selinux=0''.
** Optional: [https://github.com/linux-system-roles/selinux
linux-system-roles.selinux] should disable SELinux using
''selinux=0''.
* Other developers: N/A
* Release engineering: https://pagure.io/releng/issue/9742
* Policies and guidelines: N/A
* Trademark approval: N/A (not needed for this Change)
== Upgrade/compatibility impact ==
Users should not be directly affected by this change.
== How To Test ==
# Install a kernel built with ''CONFIG_SECURITY_SELINUX_DISABLE''
disabled, e.g. from
https://copr.fedorainfracloud.org/coprs/omos/drop-selinux-disable/.
# Confirm that SELinux is disabled when ''selinux=0'' is used on
kernel command line.
# Confirm that userspace considers SELinux disabled when
''SELINUX=disabled'' is used in ''/etc/selinux/config''.
# Confirm that userspace considers SELinux disabled when there is no
''/etc/selinux/config''.
# Confirm that the system works as expected in all previous cases.
== User Experience ==
There's no visible change for users with SELinux enabled.
Users with ''SELINUX=disabled'' in ''/etc/selinux/config'' and without
''selinux=0'' on kernel command line might notice that `ps Z` command
uses ''kernel'' domain for processes, while with ''selinux=0'' `ps Z`
prints '-'.
These users will also be able to load SELinux policy after boot.
== Dependencies ==
Upstream kernel SELinux subsystem waits for this change in order to
remove CONFIG_SECURITY_SELINUX_DISABLE functionality -
https://lore.kernel.org/selinux/157836784986.560897.13893922675143903084....
== Contingency Plan ==
* Contingency mechanism: Revert the kernel build option change and
build kernel with ''CONFIG_SECURITY_SELINUX_DISABLE=y''
* Contingency deadline: Beta freeze
* Blocks release? No
== Documentation ==
TBD
== Release Notes ==
TBD
--
Ben Cotton
He / Him / His
Senior Program Manager, Fedora & CentOS Stream
Red Hat
TZ=America/Indiana/Indianapolis
3 years, 7 months