https://fedoraproject.org/wiki/Changes/F38-FPC-repackaging
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 ==
Split the `fpc` package (the Free Pascal Compiler) into several
sub-packages (built from the same spec file).
== Owner ==
* Name: [[User:suve|Artur Frenszek-Iwicki]]
* Email: <fedora@svgames.pl>
== Detailed Description ==
The `fpc` package will be split into three packages:
* `fpc` - the compiler itself, plus utility programs
* `fpc-ide` - the terminal-based TUI IDE (`/usr/bin/fp`)
* `fpc-units-ARCHNAME-linux` - pre-compiled units (think "FPC's
stdlib") for developing programs for Linux
The "units" subpackage will be a shared dependency for both `fpc` and `fpc-ide`.
== Benefit to Fedora ==
The TUI IDE will be moved to a separate package, slightly reducing the
download size for packages requiring FPC to build.
Putting Linux units in an `fpc-units-ARCHNAME-linux` package will
create a precedent which can be used in the future for introducing
cross-compilation packages, like `fpc-units-x86_64-win64` for MS
Windows.
== Scope ==
* Proposal owners:
** Edit `fpc.spec` as required and rebuild the package, preferably
before the Mass Rebuild.
* Other developers: No action required.
* Release engineering: No action required.
* Policies and guidelines: N/A (not needed for this Change)
* Trademark approval: N/A (not needed for this Change)
* Alignment with Objectives: N/A
== Upgrade/compatibility impact ==
After upgrading to Fedora 38, users interested in the TUI IDE will
need to manually install the `fpc-ide` package. For those not
interested in the TUI IDE, there will be no impact.
== How To Test ==
A copr repository has been created where users can test out the
modified package:
[https://copr.fedorainfracloud.org/coprs/suve/fpc-split/
copr/suve/fpc-split].
This copr repository also modifies the spec to build units for MS
Windows (`x86_64` only), allowing for cross-compilation.
== User Experience ==
For users not interested in the TUI IDE, this Change will slightly
reduce the install size (about 1.5 MiB for the IDE plus another 3.5
MiB for its dependencies).
Since the TUI IDE does not launch the compiler as a sub-process, but
rather contains an embedded copy of the compiler, users who use only
the IDE and not the standalone compiler will benefit in a similar way
- they will be able to install just the IDE, without the main compiler
package.
== Dependencies ==
None.
== Contingency Plan ==
Worst case scenario - give up, revert to an old version of `fpc.spec`
and rebuild the package.
== Documentation ==
N/A (not a System Wide Change)
== Release Notes ==
The `fpc` package no longer includes the terminal-based TUI IDE. Users
interested in the IDE should install the `fpc-ide` package.
--
Ben Cotton
He / Him / His
Fedora Program Manager
Red Hat
TZ=America/Indiana/Indianapolis
_______________________________________________
devel-announce mailing list -- devel-announce@lists.fedoraproject.org
To unsubscribe send an email to devel-announce-leave@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-announce@lists.fedoraproject.org
Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Friday, December 30, 2022
F38 proposal: GNU Toolchain Update (gcc 13.0, binutils 2.39, glibc 2.37, gdb 12.1) (System-Wide Change proposal)
https://fedoraproject.org/wiki/Changes/GNUToolchainF38
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 ==
Update the Fedora 38 GNU Toolchain to gcc 13.0, binutils 2.39, and glibc 2.37.
The existing gdb 12.1 will be used as-is.
The set of core GNU Toolchain packages for Fedora 38 are as follows:
* GNU C Compiler 13.0
** Associated runtimes for C++ (libstdc++), Go (gccgo), OpenMP (gomp),
Fortran (gfortran), D (phobos), Objective C/C++.
* GNU Binary Utilities 2.39
* GNU C Library 2.37
* GNU Debugger 12.1 (immediately available in Fedora 37)
The gcc 13.0 change will be tracked in this top-level GNU Toolchain
system-wide update.
The binutils 2.39 change will be tracked in this top-level GNU
Toolchain system-wide update.
The glibc 2.37 change will be tracked in this top-level GNU Toolchain
system-wide update.
== Owner ==
* Name: [[User:codonell|Carlos O'Donell]]
* Email: carlos@redhat.com
== Detailed Description ==
The GNU Compiler Collection, GNU Binary Utilities, GNU C Library, and
the GNU Debugger make up the core part of the GNU Toolchain and it is
useful for our users to transition these components as a complete
implementation when making a new release of Fedora.
The GNU Compiler Collection is expected to release version 13.0, after
the Fedora 38 release. It will contain many new features, documented
here: https://gcc.gnu.org/gcc-13/changes.html. The latest release
candidate for gcc 13 will be included in Fedora 38 and will be updated
when released.
The GNU Binutils version 2.39 was released before Fedora 38; and we
have already been using this version of binutils in Fedora Rawhide
successfully to build the distribution for the last 4 months. Given
the present schedule for Fedora 38 we will continue to use Binutils
2.39.
The GNU C Library version 2.37 is expected to be release before Fedora
38; we have started closely tracking the glibc 2.37 development code
in Fedora Rawhide and are addressing any issues as they arise. Given
the present schedule Fedora 38 will branch after the release of glibc
2.37. However, the mass rebuild schedule means Fedora 38 will mass
rebuild (if required) before the final release of glibc 2.37, but
after the ABI is frozen.
The GNU Debugger version 12.1 was released before Fedora 38; and we
plan to continue to use this version of the debugger.
== Benefit to Fedora ==
Stays up to date with latest features, improvements, security and bug
fixes from gcc, glibc, binutils, and gdb upstream.
The goal is to track and transition to the latest components of the
GNU Toolchain.
== Scope ==
* Proposal owners: Fedora Toolchain Team (gcc, glibc, binutils, gdb,
...) developers need to ensure that gcc, glibc, binutils, and gdb in
rawhide are stable and ready for the Fedora 38 branch.
* Other developers: Given that glibc is backwards compatible and we
have been testing the new glibc in rawhide it should make very little
impact when updated, except for the occasional deprecation warnings
and removal of legacy interfaces from public header files.
* Release engineering: A mass rebuild is strongly encouraged;
[https://pagure.io/releng/issue/XX #XX]
** Filed after approval.
* Policies and guidelines: N/A (not needed for this Change)
* Trademark approval: N/A (not needed for this Change)
* Alignment with Objectives: N/A
== Upgrade/compatibility impact ==
The compiler, the static linker and the the library are backwards
compatible with the previous version of Fedora.
Some source changes may be required for the gcc 13 update. Please
refer to the latest changes here:
https://gcc.gnu.org/gcc-13/changes.html
Any source level changes required for glibc 2.37 will be noted here:
https://sourceware.org/glibc/wiki/Release/2.37#Packaging_Changes
== How To Test ==
The GNU Compiler Collection has its own testsuite which is run during
the package build and examined by the gcc developers before being
uploaded.
The GNU C Library has its own testsuite which is run during the
package build and examined by the glibc developers before being
uploaded. This test suite has over 6200 tests that run to verify the
correct operation of the library. In the future we may also run the
microbenchmark to look for performance regressions.
The GNU Binutils has its own testsuite which is run during the package
build and examined by binutils developers before being uploaded. The
regression testsuite is run to verify the correct operation of the
static linker and attendant utilities.
The GNU Debugger has its own testsuite which is run during the package
build and examined by gdb developers before being uploaded. The
regression testsuite is run to verify the correct operation of the
debugger.
== User Experience ==
Fedora developers as well as developers using the distribution will be
able to use and develop using the new features offered by the updated
components. Developers will need to enable specific compiler features
as required e.g. '-mcpu=neoverse-v2'.
== Dependencies ==
All packages do not need to be rebuilt due to backwards compatibility.
However, it is advantageous if a mass rebuild is performed during the
Fedora 38 cycle. The mass rebuild would ensure all packages can be
built with the newer compiler and core runtime.
== Contingency Plan ==
* Contingency mechanism glibc: If glibc 2.37 proves too disruptive to
compiling the distribution we could revert to 2.36, but given that
Rawhide has started tracking glibc 2.37, no show-stopper problems are
expected. At this point we can still revert to upstream version 2.36
if insurmountable problems appear, but to do so may require a mass
rebuild to remove new symbols from the ABI/API.
* Contingency mechanism binutils: If binutils 2.39 proves too
distruptive to assembling and linking the distribution we could revert
to 2.38, but given that Rawhide is using 2.39, no show-stopper
problems are expected. At this point we can still revert if
insurmountable problems appear, but to do so may require a mass
rebuild if the defects involve generated binaries.
* Contingency mechanism for gcc: If gcc 13 proves too disruptive to
compiling the distribution we could revert to gcc 12.
* Contingency mechanism for gdb: The gdb 12.1 release is already in
all the Fedora releases and it would not be reverted. If any gcc,
glibc or binutils changes cause gdb to fail then that would need to be
reviewed on a case-by-case basis.
* Contingency deadline: Fedora mass rebuild on 2023-01-18.
* Blocks release?
** Yes, upgrading to gcc 13.0 does block the release.
** Yes, upgrading to binutils 2.39 does block the release.
** Yes, upgrading to glibc 2.37 does block the release.
** No, upgrading to gdb 12.1 does block the release (already released).
== Documentation ==
The gcc manual contains the documentation for the release and doesn't
need any more additional work.
The binutils manual contains the documentation for the release and
doesn't need any more additional work.
The glibc manual contains the documentation for the release and
doesn't need any more additional work.
The gdb manual contains the documentation for the release and doesn't
need any more additional work.
== Release Notes ==
<!-- Use this text for GCC updates: -->
See https://gcc.gnu.org/gcc-13/changes.html for the GNU Compiler
Collection version 13 release notes.
<!-- Use this text for GLIBC updates: -->
The GNU C Library version 2.37 will be released at the beginning of
February 2023. The current NEWS notes can be seen here as they are
added: https://sourceware.org/git/?p=glibc.git;a=blob;f=NEWS;hb=HEAD
The GNU Binary Utilities version 2.39 was released August 2022. The
current release notes will be sent to the developer mailing list:
https://sourceware.org/pipermail/binutils/2022-August/122246.html.
--
Ben Cotton
He / Him / His
Fedora Program Manager
Red Hat
TZ=America/Indiana/Indianapolis
_______________________________________________
devel-announce mailing list -- devel-announce@lists.fedoraproject.org
To unsubscribe send an email to devel-announce-leave@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-announce@lists.fedoraproject.org
Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
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 ==
Update the Fedora 38 GNU Toolchain to gcc 13.0, binutils 2.39, and glibc 2.37.
The existing gdb 12.1 will be used as-is.
The set of core GNU Toolchain packages for Fedora 38 are as follows:
* GNU C Compiler 13.0
** Associated runtimes for C++ (libstdc++), Go (gccgo), OpenMP (gomp),
Fortran (gfortran), D (phobos), Objective C/C++.
* GNU Binary Utilities 2.39
* GNU C Library 2.37
* GNU Debugger 12.1 (immediately available in Fedora 37)
The gcc 13.0 change will be tracked in this top-level GNU Toolchain
system-wide update.
The binutils 2.39 change will be tracked in this top-level GNU
Toolchain system-wide update.
The glibc 2.37 change will be tracked in this top-level GNU Toolchain
system-wide update.
== Owner ==
* Name: [[User:codonell|Carlos O'Donell]]
* Email: carlos@redhat.com
== Detailed Description ==
The GNU Compiler Collection, GNU Binary Utilities, GNU C Library, and
the GNU Debugger make up the core part of the GNU Toolchain and it is
useful for our users to transition these components as a complete
implementation when making a new release of Fedora.
The GNU Compiler Collection is expected to release version 13.0, after
the Fedora 38 release. It will contain many new features, documented
here: https://gcc.gnu.org/gcc-13/changes.html. The latest release
candidate for gcc 13 will be included in Fedora 38 and will be updated
when released.
The GNU Binutils version 2.39 was released before Fedora 38; and we
have already been using this version of binutils in Fedora Rawhide
successfully to build the distribution for the last 4 months. Given
the present schedule for Fedora 38 we will continue to use Binutils
2.39.
The GNU C Library version 2.37 is expected to be release before Fedora
38; we have started closely tracking the glibc 2.37 development code
in Fedora Rawhide and are addressing any issues as they arise. Given
the present schedule Fedora 38 will branch after the release of glibc
2.37. However, the mass rebuild schedule means Fedora 38 will mass
rebuild (if required) before the final release of glibc 2.37, but
after the ABI is frozen.
The GNU Debugger version 12.1 was released before Fedora 38; and we
plan to continue to use this version of the debugger.
== Benefit to Fedora ==
Stays up to date with latest features, improvements, security and bug
fixes from gcc, glibc, binutils, and gdb upstream.
The goal is to track and transition to the latest components of the
GNU Toolchain.
== Scope ==
* Proposal owners: Fedora Toolchain Team (gcc, glibc, binutils, gdb,
...) developers need to ensure that gcc, glibc, binutils, and gdb in
rawhide are stable and ready for the Fedora 38 branch.
* Other developers: Given that glibc is backwards compatible and we
have been testing the new glibc in rawhide it should make very little
impact when updated, except for the occasional deprecation warnings
and removal of legacy interfaces from public header files.
* Release engineering: A mass rebuild is strongly encouraged;
[https://pagure.io/releng/issue/XX #XX]
** Filed after approval.
* Policies and guidelines: N/A (not needed for this Change)
* Trademark approval: N/A (not needed for this Change)
* Alignment with Objectives: N/A
== Upgrade/compatibility impact ==
The compiler, the static linker and the the library are backwards
compatible with the previous version of Fedora.
Some source changes may be required for the gcc 13 update. Please
refer to the latest changes here:
https://gcc.gnu.org/gcc-13/changes.html
Any source level changes required for glibc 2.37 will be noted here:
https://sourceware.org/glibc/wiki/Release/2.37#Packaging_Changes
== How To Test ==
The GNU Compiler Collection has its own testsuite which is run during
the package build and examined by the gcc developers before being
uploaded.
The GNU C Library has its own testsuite which is run during the
package build and examined by the glibc developers before being
uploaded. This test suite has over 6200 tests that run to verify the
correct operation of the library. In the future we may also run the
microbenchmark to look for performance regressions.
The GNU Binutils has its own testsuite which is run during the package
build and examined by binutils developers before being uploaded. The
regression testsuite is run to verify the correct operation of the
static linker and attendant utilities.
The GNU Debugger has its own testsuite which is run during the package
build and examined by gdb developers before being uploaded. The
regression testsuite is run to verify the correct operation of the
debugger.
== User Experience ==
Fedora developers as well as developers using the distribution will be
able to use and develop using the new features offered by the updated
components. Developers will need to enable specific compiler features
as required e.g. '-mcpu=neoverse-v2'.
== Dependencies ==
All packages do not need to be rebuilt due to backwards compatibility.
However, it is advantageous if a mass rebuild is performed during the
Fedora 38 cycle. The mass rebuild would ensure all packages can be
built with the newer compiler and core runtime.
== Contingency Plan ==
* Contingency mechanism glibc: If glibc 2.37 proves too disruptive to
compiling the distribution we could revert to 2.36, but given that
Rawhide has started tracking glibc 2.37, no show-stopper problems are
expected. At this point we can still revert to upstream version 2.36
if insurmountable problems appear, but to do so may require a mass
rebuild to remove new symbols from the ABI/API.
* Contingency mechanism binutils: If binutils 2.39 proves too
distruptive to assembling and linking the distribution we could revert
to 2.38, but given that Rawhide is using 2.39, no show-stopper
problems are expected. At this point we can still revert if
insurmountable problems appear, but to do so may require a mass
rebuild if the defects involve generated binaries.
* Contingency mechanism for gcc: If gcc 13 proves too disruptive to
compiling the distribution we could revert to gcc 12.
* Contingency mechanism for gdb: The gdb 12.1 release is already in
all the Fedora releases and it would not be reverted. If any gcc,
glibc or binutils changes cause gdb to fail then that would need to be
reviewed on a case-by-case basis.
* Contingency deadline: Fedora mass rebuild on 2023-01-18.
* Blocks release?
** Yes, upgrading to gcc 13.0 does block the release.
** Yes, upgrading to binutils 2.39 does block the release.
** Yes, upgrading to glibc 2.37 does block the release.
** No, upgrading to gdb 12.1 does block the release (already released).
== Documentation ==
The gcc manual contains the documentation for the release and doesn't
need any more additional work.
The binutils manual contains the documentation for the release and
doesn't need any more additional work.
The glibc manual contains the documentation for the release and
doesn't need any more additional work.
The gdb manual contains the documentation for the release and doesn't
need any more additional work.
== Release Notes ==
<!-- Use this text for GCC updates: -->
See https://gcc.gnu.org/gcc-13/changes.html for the GNU Compiler
Collection version 13 release notes.
<!-- Use this text for GLIBC updates: -->
The GNU C Library version 2.37 will be released at the beginning of
February 2023. The current NEWS notes can be seen here as they are
added: https://sourceware.org/git/?p=glibc.git;a=blob;f=NEWS;hb=HEAD
The GNU Binary Utilities version 2.39 was released August 2022. The
current release notes will be sent to the developer mailing list:
https://sourceware.org/pipermail/binutils/2022-August/122246.html.
--
Ben Cotton
He / Him / His
Fedora Program Manager
Red Hat
TZ=America/Indiana/Indianapolis
_______________________________________________
devel-announce mailing list -- devel-announce@lists.fedoraproject.org
To unsubscribe send an email to devel-announce-leave@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-announce@lists.fedoraproject.org
Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
F38 proposal: Noto Fonts For More Languages (System-Wide Change proposal)
https://fedoraproject.org/wiki/Changes/NotoFontsForMoreLang
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 ==
Changes the default font for more languages to Noto Fonts.
== Owner ==
* Name: [[User:Tagoh| Akira TAGOH]]
* Email: <tagoh AT redhat DOT com>
== Detailed Description ==
We have changed our default fonts to Noto in
[[Changes/DefaultToNotoFonts|f36]] though, some languages was still
missing even though Noto Fonts provides fonts for their languages.
This Change continues to accomplish consistent text rendering across
our supported languages as far as possible.
The following languages are targeted in this Change:
* Khmer
* Thai
== Feedback ==
== Benefit to Fedora ==
We would get better text rendering on applications and desktops for
the above languages as well as languages we have already migrated.
Also this change should save about 344kB on the fresh install.
<pre>
$ rpm -qlv khmer-os-system-fonts thai-scalable-waree-fonts | awk
'BEGIN{a=0}{a+=$5}END{print a}'
504660</pre>
<pre>
$ rpm -qlv google-noto-sans-khmer-vf-fonts
google-noto-sans-thai-vf-fonts | awk 'BEGIN{a=0}{a+=$5}END{print a}'
160573</pre>
== Scope ==
* Proposal owners:
** Update google-noto-fonts and fonts packages currently used as
default, to change the priority of fontconfig config.
** Update langpacks to update dependencies
** Update comps to update default fonts sets
** Update lorax templates
* Other developers: Nothing
* 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: Nothing
== Upgrade/compatibility impact ==
The migration will be done by updating langpacks. after upgrading and
rebooting, the default font will be Noto instead of `Khmer OS
System`/`Waree`.
Since this change aims to switch non-variable fonts to variable fonts,
it may not works with legacy applications as expected such as missing
some variants. in that case, you can install non-variable fonts
packages. the package name will be similar and simply drop -vf from
the variable fonts packages.
== How To Test ==
* This change can be simply tested by fc-match command like `fc-match
sans:lang=<your langauge>`, `fc-match serif:lang=<your language>` and
`fc-match monospace:lang=<your language>`. `:lang=km` for Khmer and
`:lang=th` for Thai.
* Test the text rendering in your favorite application, which use the
system default font.
== User Experience ==
Khmer/Thai Users will see the default font is changed to Noto by this change.
== Dependencies ==
Only khmer-os-system-fonts, thai-scalable-waree-fonts, langpacks, and
fontconfig are required to update. Other packages which explicitly has
a dependency to above fonts packages are basically optional to update.
== Contingency Plan ==
* Contingency mechanism: (What to do? Who will do it?) Revert the
relevant packages updated.
* Contingency deadline: Beta freeze
* Blocks release? No
== Documentation ==
None
== Release Notes ==
The default fonts for Khmer and Thai will be Google Noto Fonts to keep
consistency on the text rendering and to provide better quality among
languages.
--
Ben Cotton
He / Him / His
Fedora Program Manager
Red Hat
TZ=America/Indiana/Indianapolis
_______________________________________________
devel-announce mailing list -- devel-announce@lists.fedoraproject.org
To unsubscribe send an email to devel-announce-leave@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-announce@lists.fedoraproject.org
Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
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 ==
Changes the default font for more languages to Noto Fonts.
== Owner ==
* Name: [[User:Tagoh| Akira TAGOH]]
* Email: <tagoh AT redhat DOT com>
== Detailed Description ==
We have changed our default fonts to Noto in
[[Changes/DefaultToNotoFonts|f36]] though, some languages was still
missing even though Noto Fonts provides fonts for their languages.
This Change continues to accomplish consistent text rendering across
our supported languages as far as possible.
The following languages are targeted in this Change:
* Khmer
* Thai
== Feedback ==
== Benefit to Fedora ==
We would get better text rendering on applications and desktops for
the above languages as well as languages we have already migrated.
Also this change should save about 344kB on the fresh install.
<pre>
$ rpm -qlv khmer-os-system-fonts thai-scalable-waree-fonts | awk
'BEGIN{a=0}{a+=$5}END{print a}'
504660</pre>
<pre>
$ rpm -qlv google-noto-sans-khmer-vf-fonts
google-noto-sans-thai-vf-fonts | awk 'BEGIN{a=0}{a+=$5}END{print a}'
160573</pre>
== Scope ==
* Proposal owners:
** Update google-noto-fonts and fonts packages currently used as
default, to change the priority of fontconfig config.
** Update langpacks to update dependencies
** Update comps to update default fonts sets
** Update lorax templates
* Other developers: Nothing
* 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: Nothing
== Upgrade/compatibility impact ==
The migration will be done by updating langpacks. after upgrading and
rebooting, the default font will be Noto instead of `Khmer OS
System`/`Waree`.
Since this change aims to switch non-variable fonts to variable fonts,
it may not works with legacy applications as expected such as missing
some variants. in that case, you can install non-variable fonts
packages. the package name will be similar and simply drop -vf from
the variable fonts packages.
== How To Test ==
* This change can be simply tested by fc-match command like `fc-match
sans:lang=<your langauge>`, `fc-match serif:lang=<your language>` and
`fc-match monospace:lang=<your language>`. `:lang=km` for Khmer and
`:lang=th` for Thai.
* Test the text rendering in your favorite application, which use the
system default font.
== User Experience ==
Khmer/Thai Users will see the default font is changed to Noto by this change.
== Dependencies ==
Only khmer-os-system-fonts, thai-scalable-waree-fonts, langpacks, and
fontconfig are required to update. Other packages which explicitly has
a dependency to above fonts packages are basically optional to update.
== Contingency Plan ==
* Contingency mechanism: (What to do? Who will do it?) Revert the
relevant packages updated.
* Contingency deadline: Beta freeze
* Blocks release? No
== Documentation ==
None
== Release Notes ==
The default fonts for Khmer and Thai will be Google Noto Fonts to keep
consistency on the text rendering and to provide better quality among
languages.
--
Ben Cotton
He / Him / His
Fedora Program Manager
Red Hat
TZ=America/Indiana/Indianapolis
_______________________________________________
devel-announce mailing list -- devel-announce@lists.fedoraproject.org
To unsubscribe send an email to devel-announce-leave@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-announce@lists.fedoraproject.org
Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
F38 proposal: Rpmautospec by Default (System-Wide Change proposal)
https://fedoraproject.org/wiki/Changes/Rpmautospec_by_Default
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 ==
Rpmautospec (`%autorelease` and `%autochangelog`) is recommended as
the default approach.
Packaging Guidelines and other documentation are adjusted to describe
this approach first.
Various tools that provide spec file templates are adjusted.
== Owner ==
* Name: [[User:Nphilipp| Nils Philippsen]], [[User:Zbyszek| Zbigniew
Jędrzejewski-Szmek]]
* Email: nphilipp - at - redhat.com, zbyszek - at - in.waw.pl
== Detailed Description ==
{{admon/note|Brief reminder about rpmautospec|
The spec file contains:
<pre>
Version: 1.2.3
Release: %autorelease
...
%changelog
%autochangelog
</pre>
Rpmautospec uses git history. Whenever the package is built
(`.src.rpm` is generated), rpmautospec tooling will replace the
`%autorelease` macro with the number of commits since the last commit
that changed the `Version` field, and the `%autochangelog` macro with
a text generated from `git log`.
For details see the
[https://docs.pagure.org/fedora-infra.rpmautospec/principle.html
docs].
}}
Rpmautospec has been deployed in Fedora since F35
([[Changes/rpmautospec]]), and 3423/23045 packages use it (15%).
But it is still a "second-class citizen": most documentation doesn't
mention it, and many packagers know that it exists but don't use it in
their packages. We think that it's reasonable to switch to
`%autorelease`+`%autochangelog` for almost all packages and that
Packaging Guidelines and various packaging howtos should recommend
that approach to packagers. The "traditional" approach of
manually-managed `Release` and `%changelog` will remain valid and will
be documented as a fallback.
This change is targeted at Fedora 38, but it will actually apply to
all releases. The goal is to update the Packaging Guidelines and other
prominent documentation and tools now, and other docs and tools
possibly at a later time. Changing packages is out of scope.
It is worth mentioning that `rust2rpm` uses
`%autorelease`+`%autochangelog` since a few releases, so most rust
packages have switched. (Generally, rust spec files are recreated
using the generator for each new version, so the switch would happen
whenever a new version is packaged unless the packager opts out.)
== Feedback ==
* Thread on fedora-devel in August 2022:
[https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/message/T6J2WGIMRCTW77QTH4D7HPNS6KUGDQOQ/
rpmautospec by default]
** open issues: a bunch have been fixed.
** maintenance: Nils will add some co-maintainers.
** compatibility with rpmdevtools, fedpkg/rpkg, fedora-review: see
Scope section.
== Benefit to Fedora ==
Various packaging workflows become smoother for packagers and contributors:
* packagers don't need to touch the `Release` field on updates
* packagers describe changes just once in the git commit message, the
`%changelog` entry is autogenerated
* patches to the spec file can be cherry-picked between branches
without trivial conflicts
* pull requests on src.fedoraproject.org can be merged without trivial conflicts
* in workflows that regenerate the spec file (rust2rpm, pip2rpm, …)
`%changelog` section doesn't need to be copied over
== Scope ==
* Proposal owners:
** provide pull requests to Packaging Guidelines and other docs to
make `%autorelease`+`%autochangelog` the default
** implement fixes for issues reported by packagers
** make semi-regular releases of rpmautospec
([https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/message/K5EA5OGRX2BCZ353C7S4MQVZTSH2BH63/
0.3.1 was released on November 17th, and should be deployed to
production in about two weeks])
* Other developers:
** provide pull requests to other docs as appropriate
** accept the changes to documentation
** update other spec file generators (pip2rpm, others?)
* Somebody (TBD):
** `fedora-review` — https://pagure.io/rpkg/issue/641
** `fedpkg import` — with https://pagure.io/rpkg/c/3087dd7, the
command will fail. A replacement workflow that instead restores
`%autorelease`+`%autochangelog` in the file committed to dist-git
needs to be implemented.
* Related work
** https://pagure.io/rpkg/c/3087dd7
** https://src.fedoraproject.org/rpms/fedora-packager/pull-request/4
* Release engineering: [https://pagure.io/releng/issues #Releng issue number]
* Policies and guidelines: a list of places to be updated
** https://docs.fedoraproject.org/en-US/packaging-guidelines/#changelogs
** https://docs.fedoraproject.org/en-US/packaging-guidelines/Versioning
** https://docs.fedoraproject.org/en-US/package-maintainers/Packaging_Tutorial_GNU_Hello/
* Trademark approval: N/A (not needed for this Change)
* Alignment with Objectives: N/A
== Upgrade/compatibility impact ==
Rpmautospec is already used by a decent number of packages, so any
issues are already being seen and need to be fixed anyway.
== How To Test ==
* Convert an existing package: `rpmautospec convert`. Ideally this
step is done right before a version bump so that the release numbers
restart at `-1`.
* Do local builds (`fedpkg local`, `fedpkg mockbuild`). Verify
correctness of version-release (`rpm -qpi`) and the changelog (`rpm
-qp --changelog`).
* Do builds in koji. Verify correctness of version-release and the changelog.
* For new packages, use `%autorelease`+`%autochangelog`. Repeat all
the tests listed above.
* Assume you are a newbie packager. Read the packaging docs and check
that the workflow is clear and the intructions are sufficient to use
rpmautospec tooling correctly.
== User Experience ==
No changes visible to end users.
== Dependencies ==
None.
== Contingency Plan ==
If it turns out that the rpmautospec workflows have unknown problems,
we can revert changes to documentation.
* Contingency mechanism: Revert changes to documentation by reverting
the appropriate commits. This can be done easily by FPC.
* Contingency deadline: Any time.
* Blocks release? No.
== Documentation ==
This page and any changes to Packaging Guidelines and other documents.
== Release Notes ==
Not needed.
--
Ben Cotton
He / Him / His
Fedora Program Manager
Red Hat
TZ=America/Indiana/Indianapolis
_______________________________________________
devel-announce mailing list -- devel-announce@lists.fedoraproject.org
To unsubscribe send an email to devel-announce-leave@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-announce@lists.fedoraproject.org
Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
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 ==
Rpmautospec (`%autorelease` and `%autochangelog`) is recommended as
the default approach.
Packaging Guidelines and other documentation are adjusted to describe
this approach first.
Various tools that provide spec file templates are adjusted.
== Owner ==
* Name: [[User:Nphilipp| Nils Philippsen]], [[User:Zbyszek| Zbigniew
Jędrzejewski-Szmek]]
* Email: nphilipp - at - redhat.com, zbyszek - at - in.waw.pl
== Detailed Description ==
{{admon/note|Brief reminder about rpmautospec|
The spec file contains:
<pre>
Version: 1.2.3
Release: %autorelease
...
%changelog
%autochangelog
</pre>
Rpmautospec uses git history. Whenever the package is built
(`.src.rpm` is generated), rpmautospec tooling will replace the
`%autorelease` macro with the number of commits since the last commit
that changed the `Version` field, and the `%autochangelog` macro with
a text generated from `git log`.
For details see the
[https://docs.pagure.org/fedora-infra.rpmautospec/principle.html
docs].
}}
Rpmautospec has been deployed in Fedora since F35
([[Changes/rpmautospec]]), and 3423/23045 packages use it (15%).
But it is still a "second-class citizen": most documentation doesn't
mention it, and many packagers know that it exists but don't use it in
their packages. We think that it's reasonable to switch to
`%autorelease`+`%autochangelog` for almost all packages and that
Packaging Guidelines and various packaging howtos should recommend
that approach to packagers. The "traditional" approach of
manually-managed `Release` and `%changelog` will remain valid and will
be documented as a fallback.
This change is targeted at Fedora 38, but it will actually apply to
all releases. The goal is to update the Packaging Guidelines and other
prominent documentation and tools now, and other docs and tools
possibly at a later time. Changing packages is out of scope.
It is worth mentioning that `rust2rpm` uses
`%autorelease`+`%autochangelog` since a few releases, so most rust
packages have switched. (Generally, rust spec files are recreated
using the generator for each new version, so the switch would happen
whenever a new version is packaged unless the packager opts out.)
== Feedback ==
* Thread on fedora-devel in August 2022:
[https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/message/T6J2WGIMRCTW77QTH4D7HPNS6KUGDQOQ/
rpmautospec by default]
** open issues: a bunch have been fixed.
** maintenance: Nils will add some co-maintainers.
** compatibility with rpmdevtools, fedpkg/rpkg, fedora-review: see
Scope section.
== Benefit to Fedora ==
Various packaging workflows become smoother for packagers and contributors:
* packagers don't need to touch the `Release` field on updates
* packagers describe changes just once in the git commit message, the
`%changelog` entry is autogenerated
* patches to the spec file can be cherry-picked between branches
without trivial conflicts
* pull requests on src.fedoraproject.org can be merged without trivial conflicts
* in workflows that regenerate the spec file (rust2rpm, pip2rpm, …)
`%changelog` section doesn't need to be copied over
== Scope ==
* Proposal owners:
** provide pull requests to Packaging Guidelines and other docs to
make `%autorelease`+`%autochangelog` the default
** implement fixes for issues reported by packagers
** make semi-regular releases of rpmautospec
([https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/message/K5EA5OGRX2BCZ353C7S4MQVZTSH2BH63/
0.3.1 was released on November 17th, and should be deployed to
production in about two weeks])
* Other developers:
** provide pull requests to other docs as appropriate
** accept the changes to documentation
** update other spec file generators (pip2rpm, others?)
* Somebody (TBD):
** `fedora-review` — https://pagure.io/rpkg/issue/641
** `fedpkg import` — with https://pagure.io/rpkg/c/3087dd7, the
command will fail. A replacement workflow that instead restores
`%autorelease`+`%autochangelog` in the file committed to dist-git
needs to be implemented.
* Related work
** https://pagure.io/rpkg/c/3087dd7
** https://src.fedoraproject.org/rpms/fedora-packager/pull-request/4
* Release engineering: [https://pagure.io/releng/issues #Releng issue number]
* Policies and guidelines: a list of places to be updated
** https://docs.fedoraproject.org/en-US/packaging-guidelines/#changelogs
** https://docs.fedoraproject.org/en-US/packaging-guidelines/Versioning
** https://docs.fedoraproject.org/en-US/package-maintainers/Packaging_Tutorial_GNU_Hello/
* Trademark approval: N/A (not needed for this Change)
* Alignment with Objectives: N/A
== Upgrade/compatibility impact ==
Rpmautospec is already used by a decent number of packages, so any
issues are already being seen and need to be fixed anyway.
== How To Test ==
* Convert an existing package: `rpmautospec convert`. Ideally this
step is done right before a version bump so that the release numbers
restart at `-1`.
* Do local builds (`fedpkg local`, `fedpkg mockbuild`). Verify
correctness of version-release (`rpm -qpi`) and the changelog (`rpm
-qp --changelog`).
* Do builds in koji. Verify correctness of version-release and the changelog.
* For new packages, use `%autorelease`+`%autochangelog`. Repeat all
the tests listed above.
* Assume you are a newbie packager. Read the packaging docs and check
that the workflow is clear and the intructions are sufficient to use
rpmautospec tooling correctly.
== User Experience ==
No changes visible to end users.
== Dependencies ==
None.
== Contingency Plan ==
If it turns out that the rpmautospec workflows have unknown problems,
we can revert changes to documentation.
* Contingency mechanism: Revert changes to documentation by reverting
the appropriate commits. This can be done easily by FPC.
* Contingency deadline: Any time.
* Blocks release? No.
== Documentation ==
This page and any changes to Packaging Guidelines and other documents.
== Release Notes ==
Not needed.
--
Ben Cotton
He / Him / His
Fedora Program Manager
Red Hat
TZ=America/Indiana/Indianapolis
_______________________________________________
devel-announce mailing list -- devel-announce@lists.fedoraproject.org
To unsubscribe send an email to devel-announce-leave@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-announce@lists.fedoraproject.org
Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Thursday, December 22, 2022
F37 election results
Greetings, all!
The elections for the Fedora Linux 37 cycle have completed.
## Fedora Council
Aleksandra Fedorova is elected to the Fedora Council
## Fedora Engineering Steering Committee (FESCo)
The following candidates are elected to FESCo:
* Kevin Fenzi
* Miro Hrončok
* Zbigniew Jędrzejewski-Szmek
* David Cantrell
* Fabio Valentini
## Fedora Mindshare Committee
Fernando F. Mancera is elected to the Fedora Mindshare Committee.
Congratulations to all those elected and thank you to the candidates and voters.
For more details, see the Community Blog post:
https://communityblog.fedoraproject.org/fedora-linux-37-election-results/
--
Ben Cotton
He / Him / His
Fedora Program Manager
Red Hat
TZ=America/Indiana/Indianapolis
_______________________________________________
announce mailing list -- announce@lists.fedoraproject.org
To unsubscribe send an email to announce-leave@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/announce@lists.fedoraproject.org
Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
The elections for the Fedora Linux 37 cycle have completed.
## Fedora Council
Aleksandra Fedorova is elected to the Fedora Council
## Fedora Engineering Steering Committee (FESCo)
The following candidates are elected to FESCo:
* Kevin Fenzi
* Miro Hrončok
* Zbigniew Jędrzejewski-Szmek
* David Cantrell
* Fabio Valentini
## Fedora Mindshare Committee
Fernando F. Mancera is elected to the Fedora Mindshare Committee.
Congratulations to all those elected and thank you to the candidates and voters.
For more details, see the Community Blog post:
https://communityblog.fedoraproject.org/fedora-linux-37-election-results/
--
Ben Cotton
He / Him / His
Fedora Program Manager
Red Hat
TZ=America/Indiana/Indianapolis
_______________________________________________
announce mailing list -- announce@lists.fedoraproject.org
To unsubscribe send an email to announce-leave@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/announce@lists.fedoraproject.org
Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
F38 proposal: Shorter Shutdown Timer (System-Wide Change proposal)
https://fedoraproject.org/wiki/Changes/Shorter_Shutdown_Timer
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 ==
A downstream configuration change to reduce the systemd unit timeout
from 2 minutes to 15 seconds.
== Owner ==
* Name: catanzaro
* Email: mcatanzaro at redhat dot com
* Name: aday
* Email: aday at redhat dot com
== Detailed Description ==
Currently, a service that fails to stop at shutdown time can block
shutdown for up to 2 minutes. This is extremely frustrating for our
users - someone goes to shutdown or reboot their system, and then
unexpectedly has to wait for a long time before they can do anything
else.
The most common service to cause this issue is PackageKit, but there are others.
When a service fails to shutdown when it is instructed to do so, it is
not behaving properly, and it is preventing the system from behaving
in an orderly and predictable manner. Desktop APIs exist for cases
when services or apps legitimately need to prevent shutdown, and these
allow the shutdown inhibit to be communicated to admins and users, so
they understand what is happening. When the user decides to shut down
anyway, services must terminate in a timely manner. The Workstation
Working Group feels that 15 seconds is the maximum appropriate time
for both system and user services, and that Fedora should be robust to
buggy and misbehaving services that do not shut down in an appropriate
manner.
=== History ===
The Workstation Working Group has been
[https://pagure.io/fedora-workstation/issue/163 working on this issue
for several years]. Investigations have revealed that it's not
possible to fix every misbehaving service: in some cases the
misbehaviour comes from design flaws that are difficult to resolve.
An attempt has also been
[https://github.com/systemd/systemd/pull/18386 made to have the unit
timeout changed in upstream systemd]. That attempt did not go
anywhere, despite various efforts to move it along. We are no longer
comfortable waiting for upstream changes to land.
To our knowledge, there are no issues that will result from forcing
services to stop after 15 seconds on typical systems. However, system
administrators may need to configure a higher timeout if waiting
longer for a particular service, which may be true for database
services, for example.
== Feedback ==
The relevant [https://pagure.io/fedora-workstation/issue/163
Workstation Working Group ticket] includes some discussion. This
change [https://pagure.io/fesco/issue/2853 was also previously
proposed to FESCo].
== Benefit to Fedora ==
The primary benefit of the change will be to mitigate a very annoying
and - frankly - embarrassing bug. Our users shouldn't have to randomly
sit waiting for their machine to shutdown. It will also encourage the
correct use of shutdown inhibit APIs.
Although this change will "paper over" bugs in services without fixing
them, we emphasize that reducing the timeout is not merely a
workaround for buggy services, but also the desired permanent design.
Of course it is desirable to fix the underlying bugs as well, but it
doesn't make sense to require this before fixing the service timeout
to match our needs.
== Scope ==
* Proposal owners:
** Merge [https://src.fedoraproject.org/rpms/systemd/pull-request/85
the downstream change] to {{package|systemd}}.
* Other developers:
** Test their packages with the new behavior and report issues as necessary.
* Release engineering: [https://pagure.io/releng/issue/11193 #11193]
* Policies and guidelines: No policy or guideline changes required
* Trademark approval: N/A (not needed for this Change)
* Alignment with Objectives:
== Upgrade/compatibility impact ==
System and user services will be killed with SIGKILL 15 seconds after
receiving SIGTERM, from previously 1 minute 30 seconds for most system
and user services, or 2 minutes for user manager system services (the
system service that runs all user services for a user), so services
will have less time to shut down gracefully by default. These defaults
are configurable and system administrators who require longer timeouts
would need to adjust them before or after upgrade. You may edit the
DefaultTimeoutStopSec= setting in /etc/systemd/user.conf and
/etc/systemd/system.conf. You may also create a drop-in to change the
TimeoutStopSec= setting for user@service.
== How To Test ==
Given the intermittent and unpredictable nature of the bug that is
being targeted, the best way to test is by using the upcoming Fedora
release. Are shutdown delays eliminated as intended? Do system
services experience issues as a result of the change?
== User Experience ==
This change will make the Fedora user experience less annoying. It
will also encourage the use of the existing inhibit APIs, which
provide better feedback for users when system shutdown does need to be
delayed.
== Dependencies ==
No specific changes are required in other packages. However, service
developers may want to take this opportunity to examine the shutdown
behavior of their components.
== Contingency Plan ==
* Contingency mechanism: the change owners will revert the change in systemd.
* Contingency deadline: if we back out the change it would be best to
do it before beta freeze, but this can happen at any point.
* Blocks release? No.
== Documentation ==
Documentation isn't required for this minor configuration change.
Services that legitimately need to prevent system shutdown should use
[https://www.freedesktop.org/wiki/Software/systemd/inhibit/ systemd
inhibit]. Desktop applications can use the
[https://flatpak.github.io/xdg-desktop-portal/#gdbus-org.freedesktop.portal.Inhibit
XDG inhibit portal].
== Release Notes ==
--
Ben Cotton
He / Him / His
Fedora Program Manager
Red Hat
TZ=America/Indiana/Indianapolis
_______________________________________________
devel-announce mailing list -- devel-announce@lists.fedoraproject.org
To unsubscribe send an email to devel-announce-leave@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-announce@lists.fedoraproject.org
Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
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 ==
A downstream configuration change to reduce the systemd unit timeout
from 2 minutes to 15 seconds.
== Owner ==
* Name: catanzaro
* Email: mcatanzaro at redhat dot com
* Name: aday
* Email: aday at redhat dot com
== Detailed Description ==
Currently, a service that fails to stop at shutdown time can block
shutdown for up to 2 minutes. This is extremely frustrating for our
users - someone goes to shutdown or reboot their system, and then
unexpectedly has to wait for a long time before they can do anything
else.
The most common service to cause this issue is PackageKit, but there are others.
When a service fails to shutdown when it is instructed to do so, it is
not behaving properly, and it is preventing the system from behaving
in an orderly and predictable manner. Desktop APIs exist for cases
when services or apps legitimately need to prevent shutdown, and these
allow the shutdown inhibit to be communicated to admins and users, so
they understand what is happening. When the user decides to shut down
anyway, services must terminate in a timely manner. The Workstation
Working Group feels that 15 seconds is the maximum appropriate time
for both system and user services, and that Fedora should be robust to
buggy and misbehaving services that do not shut down in an appropriate
manner.
=== History ===
The Workstation Working Group has been
[https://pagure.io/fedora-workstation/issue/163 working on this issue
for several years]. Investigations have revealed that it's not
possible to fix every misbehaving service: in some cases the
misbehaviour comes from design flaws that are difficult to resolve.
An attempt has also been
[https://github.com/systemd/systemd/pull/18386 made to have the unit
timeout changed in upstream systemd]. That attempt did not go
anywhere, despite various efforts to move it along. We are no longer
comfortable waiting for upstream changes to land.
To our knowledge, there are no issues that will result from forcing
services to stop after 15 seconds on typical systems. However, system
administrators may need to configure a higher timeout if waiting
longer for a particular service, which may be true for database
services, for example.
== Feedback ==
The relevant [https://pagure.io/fedora-workstation/issue/163
Workstation Working Group ticket] includes some discussion. This
change [https://pagure.io/fesco/issue/2853 was also previously
proposed to FESCo].
== Benefit to Fedora ==
The primary benefit of the change will be to mitigate a very annoying
and - frankly - embarrassing bug. Our users shouldn't have to randomly
sit waiting for their machine to shutdown. It will also encourage the
correct use of shutdown inhibit APIs.
Although this change will "paper over" bugs in services without fixing
them, we emphasize that reducing the timeout is not merely a
workaround for buggy services, but also the desired permanent design.
Of course it is desirable to fix the underlying bugs as well, but it
doesn't make sense to require this before fixing the service timeout
to match our needs.
== Scope ==
* Proposal owners:
** Merge [https://src.fedoraproject.org/rpms/systemd/pull-request/85
the downstream change] to {{package|systemd}}.
* Other developers:
** Test their packages with the new behavior and report issues as necessary.
* Release engineering: [https://pagure.io/releng/issue/11193 #11193]
* Policies and guidelines: No policy or guideline changes required
* Trademark approval: N/A (not needed for this Change)
* Alignment with Objectives:
== Upgrade/compatibility impact ==
System and user services will be killed with SIGKILL 15 seconds after
receiving SIGTERM, from previously 1 minute 30 seconds for most system
and user services, or 2 minutes for user manager system services (the
system service that runs all user services for a user), so services
will have less time to shut down gracefully by default. These defaults
are configurable and system administrators who require longer timeouts
would need to adjust them before or after upgrade. You may edit the
DefaultTimeoutStopSec= setting in /etc/systemd/user.conf and
/etc/systemd/system.conf. You may also create a drop-in to change the
TimeoutStopSec= setting for user@service.
== How To Test ==
Given the intermittent and unpredictable nature of the bug that is
being targeted, the best way to test is by using the upcoming Fedora
release. Are shutdown delays eliminated as intended? Do system
services experience issues as a result of the change?
== User Experience ==
This change will make the Fedora user experience less annoying. It
will also encourage the use of the existing inhibit APIs, which
provide better feedback for users when system shutdown does need to be
delayed.
== Dependencies ==
No specific changes are required in other packages. However, service
developers may want to take this opportunity to examine the shutdown
behavior of their components.
== Contingency Plan ==
* Contingency mechanism: the change owners will revert the change in systemd.
* Contingency deadline: if we back out the change it would be best to
do it before beta freeze, but this can happen at any point.
* Blocks release? No.
== Documentation ==
Documentation isn't required for this minor configuration change.
Services that legitimately need to prevent system shutdown should use
[https://www.freedesktop.org/wiki/Software/systemd/inhibit/ systemd
inhibit]. Desktop applications can use the
[https://flatpak.github.io/xdg-desktop-portal/#gdbus-org.freedesktop.portal.Inhibit
XDG inhibit portal].
== Release Notes ==
--
Ben Cotton
He / Him / His
Fedora Program Manager
Red Hat
TZ=America/Indiana/Indianapolis
_______________________________________________
devel-announce mailing list -- devel-announce@lists.fedoraproject.org
To unsubscribe send an email to devel-announce-leave@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-announce@lists.fedoraproject.org
Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Wednesday, December 21, 2022
F38 proposal: X Server Prohibits Byte-swapped Clients (System-Wide Change proposal)
https://fedoraproject.org/wiki/Changes/XServerProhibitsByteSwappedClients
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 ==
X server implementations (e.g. Xorg and Xwayland) will (by default) no
longer allow clients with different endianess to connect.
== Owner ==
* Name: [[User:whot| Peter Hutterer]]
* Email: peter.hutterer@redhat.com
== Detailed Description ==
<!-- Expand on the summary, if appropriate. A couple sentences
suffices to explain the goal, but the more details you can provide the
better. -->
X server implementations (e.g. Xorg and Xwayland) allow clients with
an endianess different to that of the server to connect. Protocol
messages to and from these clients are byte-swapped by the X server.
However, the code in the X server that does this is virtually
untested, providing a large attack surface for malicious clients. One
needs to only look at e.g.
[https://www.x.org/wiki/Development/Security/Advisory-2014-12-09 this
X.Org security advisory] and count the `SProc` mentions for an
indication on how bad this is. A simple solution to remove this attack
surface is to prohibit clients with a different endianess. These
clients will simply fail, in a matter similar to failing to
authenticate against an X server.
The use-case for clients with different endianess is ''very'' niche.
It was common in the 1980s when X was originally developed but at this
point a vanishingly small number of users run clients and X servers on
different machines, let alone on different machines with different
endianess. I'd be surprised if Fedora had ''any'' users requiring this
feature.
Note:
* this only affects use-cases where the server runs on a little endian
host and the client on a Big Endian host (or vice versa).
* this is a change in '''the default behavior''' only and can be
changed via configuration options (for `Xorg`) and/or commandline
arguments (all X servers).
* this is a change in the upstream default behavior that Fedora will
follow along with. This Change is primarily to increase the exposure.
== Benefit to Fedora ==
This change removes a large potential attack surface that can be used
by malicious clients to expose memory locations, crash the X server
and/or do other entertaining things malicious programs like to do.
== Scope ==
* Proposal owners:
# Merge [https://gitlab.freedesktop.org/xorg/xserver/-/merge_requests/1029
upstream PR]
# Backport patch to Fedora's `xorg-x11-server` and
`xorg-x11-server-Xwayland` packages
* Other developers: This is labelled as system-wide change simply
because it's a change in Xorg/Xwayland. It is otherwise self-contained
in that no other packages need updating, '''unless''' they want to
opt-out of this default. Which is better left to system-specific
configuration anyway.
* Release engineering: This feature does not require coordination with
release engineering
* 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 ==
For the ''extremely niche'' use-case of users that run X clients on a
remote machine with a different endianess, these clients will no
longer be able to connect '''by default'''. For Xorg, the following
`xorg.conf.d` snippet will re-enable the old behavior:
<pre>
Section "ServerFlags"
Option "AllowSwappedClients" "on"
EndSection
</pre>
Wayland users (and thus Xwayland) need to employ compositor-specific
configuration to pass the `+byteswappedclients` flag to Xwayland. At
the time of writing, GNOME does not yet provide such a configuration.
== How To Test ==
To test the impact of this change, you need:
* an X server running on a little endian architecture and an X client
running on a Big Endian architecture (or the other way around)
* set up the X server to accept remote connections, either via TCP or
through SSH
* run the X client which will fail to connect
Alternatively, a test client is available in
[https://gitlab.freedesktop.org/xorg/xserver/-/merge_requests/1029 the
upstream PR]. This test client pretends to be BigEndian and will fail
to connect when run against a little endian X server.
== User Experience ==
For virtually all users, there is no change in behavior.
Users with X server and client on two different machines must add the
`xorg.conf.d` snippet shown above on affected systems.
== Dependencies ==
No other RPMs depend on this change.
== Contingency Plan ==
This change depends on whether upstream merges this new default
behavior. If upstream does not merged the feature in time, this Change
will be postponed until the next Fedora version to avoid potential
incompatibilities between configurations or commandline options.
* Contingency mechanism: keep current behavior, try again with next
Fedora version
* Contingency deadline: beta freeze
* Blocks release? No
== Documentation ==
== Release Notes ==
--
Ben Cotton
He / Him / His
Fedora Program Manager
Red Hat
TZ=America/Indiana/Indianapolis
_______________________________________________
devel-announce mailing list -- devel-announce@lists.fedoraproject.org
To unsubscribe send an email to devel-announce-leave@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-announce@lists.fedoraproject.org
Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
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 ==
X server implementations (e.g. Xorg and Xwayland) will (by default) no
longer allow clients with different endianess to connect.
== Owner ==
* Name: [[User:whot| Peter Hutterer]]
* Email: peter.hutterer@redhat.com
== Detailed Description ==
<!-- Expand on the summary, if appropriate. A couple sentences
suffices to explain the goal, but the more details you can provide the
better. -->
X server implementations (e.g. Xorg and Xwayland) allow clients with
an endianess different to that of the server to connect. Protocol
messages to and from these clients are byte-swapped by the X server.
However, the code in the X server that does this is virtually
untested, providing a large attack surface for malicious clients. One
needs to only look at e.g.
[https://www.x.org/wiki/Development/Security/Advisory-2014-12-09 this
X.Org security advisory] and count the `SProc` mentions for an
indication on how bad this is. A simple solution to remove this attack
surface is to prohibit clients with a different endianess. These
clients will simply fail, in a matter similar to failing to
authenticate against an X server.
The use-case for clients with different endianess is ''very'' niche.
It was common in the 1980s when X was originally developed but at this
point a vanishingly small number of users run clients and X servers on
different machines, let alone on different machines with different
endianess. I'd be surprised if Fedora had ''any'' users requiring this
feature.
Note:
* this only affects use-cases where the server runs on a little endian
host and the client on a Big Endian host (or vice versa).
* this is a change in '''the default behavior''' only and can be
changed via configuration options (for `Xorg`) and/or commandline
arguments (all X servers).
* this is a change in the upstream default behavior that Fedora will
follow along with. This Change is primarily to increase the exposure.
== Benefit to Fedora ==
This change removes a large potential attack surface that can be used
by malicious clients to expose memory locations, crash the X server
and/or do other entertaining things malicious programs like to do.
== Scope ==
* Proposal owners:
# Merge [https://gitlab.freedesktop.org/xorg/xserver/-/merge_requests/1029
upstream PR]
# Backport patch to Fedora's `xorg-x11-server` and
`xorg-x11-server-Xwayland` packages
* Other developers: This is labelled as system-wide change simply
because it's a change in Xorg/Xwayland. It is otherwise self-contained
in that no other packages need updating, '''unless''' they want to
opt-out of this default. Which is better left to system-specific
configuration anyway.
* Release engineering: This feature does not require coordination with
release engineering
* 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 ==
For the ''extremely niche'' use-case of users that run X clients on a
remote machine with a different endianess, these clients will no
longer be able to connect '''by default'''. For Xorg, the following
`xorg.conf.d` snippet will re-enable the old behavior:
<pre>
Section "ServerFlags"
Option "AllowSwappedClients" "on"
EndSection
</pre>
Wayland users (and thus Xwayland) need to employ compositor-specific
configuration to pass the `+byteswappedclients` flag to Xwayland. At
the time of writing, GNOME does not yet provide such a configuration.
== How To Test ==
To test the impact of this change, you need:
* an X server running on a little endian architecture and an X client
running on a Big Endian architecture (or the other way around)
* set up the X server to accept remote connections, either via TCP or
through SSH
* run the X client which will fail to connect
Alternatively, a test client is available in
[https://gitlab.freedesktop.org/xorg/xserver/-/merge_requests/1029 the
upstream PR]. This test client pretends to be BigEndian and will fail
to connect when run against a little endian X server.
== User Experience ==
For virtually all users, there is no change in behavior.
Users with X server and client on two different machines must add the
`xorg.conf.d` snippet shown above on affected systems.
== Dependencies ==
No other RPMs depend on this change.
== Contingency Plan ==
This change depends on whether upstream merges this new default
behavior. If upstream does not merged the feature in time, this Change
will be postponed until the next Fedora version to avoid potential
incompatibilities between configurations or commandline options.
* Contingency mechanism: keep current behavior, try again with next
Fedora version
* Contingency deadline: beta freeze
* Blocks release? No
== Documentation ==
== Release Notes ==
--
Ben Cotton
He / Him / His
Fedora Program Manager
Red Hat
TZ=America/Indiana/Indianapolis
_______________________________________________
devel-announce mailing list -- devel-announce@lists.fedoraproject.org
To unsubscribe send an email to devel-announce-leave@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-announce@lists.fedoraproject.org
Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Tuesday, December 20, 2022
F38 proposal: Unified Kernel Support Phase 1 (System-Wide Change proposal)
https://fedoraproject.org/wiki/Changes/Unified_Kernel_Support_Phase_1
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 ==
Add support for unified kernels images to Fedora.
== Owner ==
* Name: [[User:kraxel| Gerd Hoffmann]]
* Email: kraxel@redhat.com
== Detailed Description ==
The goal is to move away from initrd images being generated on the
installed machine. They are generated while building the kernel
package instead, then shipped as part of a unified kernel image.
A unified kernel image is an all-in-one efi binary containing kernel,
initrd, cmdline and signature. The secure boot signature covers
everything, specifically the initrd is included which is not the case
when the initrd gets loaded as separate file from /boot.
Main motivation for this move is to make the distro more robust and more secure.
Switching the whole distro over to unified kernels quickly is not
realistic though. Too many features are depending on the current
workflow with a host-specific initrd (and host-specific kernel command
line), which is fundamentally incompatible with unified kernels where
everybody will have the same initrd and command line. Thats why there
is 'Phase 1' in title, so we can have more Phases in future releases
😃
A host-specific initrd / command line is needed today for:
* features needing optional dracut modules (initrd rebuild needed to
enable them).
* configuration / secrets baked into the initrd (booting from iscsi
for example).
* configuration being specified on the kernel command line.
** root filesystem being the most important one.
[https://systemd.io/DISCOVERABLE_PARTITIONS/ Discoverable partitions]
allow to remove this.
Phase 1 goals (high priority):
* Ship a unified kernel image as (optional) kernel sub-rpm. Users can
opt-in to use that kernel by installing the sub-rpm. Initial focus is
on booting virtual machines where we have a relatively small and well
defined set of drivers / features needed. Supporting modern physical
machines with standard setup (i.e. boot from local sata/nvme storage)
too should be easy.
* Update kernel install scripts so unified kernels are installed and
updated properly.
* Add bootloader support for unified kernel images. Add
[https://systemd.io/BOOT_LOADER_SPECIFICATION/#type-2-efi-unified-kernel-images
unified kernel bls support] to grub2, or support using systemd-boot,
or both.
Phase 1 goals (lower priority, might move to Phase 2):
* Add proper discoverable partitions support to installers (anaconda,
image builder, ...).
** Temporary workaround possible: set types using sfdisk in %post script.
** When using btrfs: configure 'root' subvolume as default volume.
* Add proper systemd-boot support to installers.
** Temporary workaround possible: run 'bootctl install' in %post script.
* Better measurement and remote attestation support.
** store kernel + initrd hashes somewhere (kernel-hashes.rpm ?) to
allow pre-calculate TPM PCR values.
** avoid using grub2 (measures every config file line executed which
is next to impossible to pre-calculate).
* Switch cloud images to use unified kernels.
Phase 2/3 goals (longer-term stuff which is not realistic to complete for F38).
* Move away from using the kernel command line for configuration.
* Move away from storing secrets in the initrd.
* Handle dracut optional modules in a different way.
systemd has some building blocks which can be used, although none of
them are used by fedora today.
[https://www.freedesktop.org/software/systemd/man/systemd-creds.html
systemd credentials] can be used for secrets (also for configuration).
The [https://www.freedesktop.org/software/systemd/man/systemd-stub.html
unified kernel stub] can load credentials from the ESP.
The unified kernel stub can also load
[https://www.freedesktop.org/software/systemd/man/systemd-sysext.html
extensions] from the ESP, which can possibly be used to replace
optional dracut modules.
== Feedback ==
== Benefit to Fedora ==
* Better secure boot support (specifically the initrd is covered by
the signature).
* Better confidential computing support (measurements are much more
useful if we know what hashes to expect for the initrd).
* More robust boot process (generating the initrd on the installed
system is fragile, root cause for kernel bugs reported is simply a
broken initrd sometimes).
== Scope ==
* Proposal owners:
** Update kernel build to create unified kernel sub-package.
*** part one: [https://gitlab.com/cki-project/kernel-ark/-/merge_requests/2179
PR#2179]
*** part two: (wip)
[https://gitlab.com/kraxel/kernel-ark/-/commits/unified/
https://gitlab.com/kraxel/kernel-ark/-/commits/unified/]
* Other developers:
** grub2: add unified kernel support
*** wip code at [https://github.com/osteffenrh/grub2/
https://github.com/osteffenrh/grub2/]
** installer(s): add support for discoverable partitions.
*** [https://bugzilla.redhat.com/show_bug.cgi?id=1075288 Bug#1075288]
* 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 ==
None (using unified kernel is opt-in for Phase 1).
== How To Test ==
Try on a existing (uefi) system:
* make sure you are running fedora 37 or rawhide.
* make sure your root filesystem has type "Linux root (x86-64)" (use
`fdisk -l` to check).
** should that not be the case use the fdisk tag command ('t') to
change the partition type.
* when using btrfs: make sure the 'root' subvolume is set as default volume.
* `dnf copr enable kraxel/unified.kernel`
* `dnf update "grub2*"`
* `dnf install kernel-unified-virt`
* `reboot`
You should find two entries in the grub2 boot menu, one for classing
kernel with separate initrd and one for the unified kernel image.
Both should boot fine.
The https://gitlab.com/kraxel/fedora-uki project has kickstart files
and helper scripts for generating virtual machine images.
* image using grub2-efi:
https://gitlab.com/kraxel/fedora-uki/-/raw/master/kickstart/fedora-uki-grub2.ks
* image using systemd-boot:
https://gitlab.com/kraxel/fedora-uki/-/raw/master/kickstart/fedora-uki-sdboot.ks
Prebuilt virtual machine images are available from
https://www.kraxel.org/fedora-uki/.
== User Experience ==
== Dependencies ==
== Contingency Plan ==
* Contingency mechanism:
** Probably none (unified kernel images are opt-in for Phase 1).
** In case we tried switching the cloud images to unified kernels:
revert the kickstart config changes.
* Contingency deadline:
* Blocks release? No
== Documentation ==
== Release Notes ==
--
Ben Cotton
He / Him / His
Fedora Program Manager
Red Hat
TZ=America/Indiana/Indianapolis
_______________________________________________
devel-announce mailing list -- devel-announce@lists.fedoraproject.org
To unsubscribe send an email to devel-announce-leave@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-announce@lists.fedoraproject.org
Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
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 ==
Add support for unified kernels images to Fedora.
== Owner ==
* Name: [[User:kraxel| Gerd Hoffmann]]
* Email: kraxel@redhat.com
== Detailed Description ==
The goal is to move away from initrd images being generated on the
installed machine. They are generated while building the kernel
package instead, then shipped as part of a unified kernel image.
A unified kernel image is an all-in-one efi binary containing kernel,
initrd, cmdline and signature. The secure boot signature covers
everything, specifically the initrd is included which is not the case
when the initrd gets loaded as separate file from /boot.
Main motivation for this move is to make the distro more robust and more secure.
Switching the whole distro over to unified kernels quickly is not
realistic though. Too many features are depending on the current
workflow with a host-specific initrd (and host-specific kernel command
line), which is fundamentally incompatible with unified kernels where
everybody will have the same initrd and command line. Thats why there
is 'Phase 1' in title, so we can have more Phases in future releases
😃
A host-specific initrd / command line is needed today for:
* features needing optional dracut modules (initrd rebuild needed to
enable them).
* configuration / secrets baked into the initrd (booting from iscsi
for example).
* configuration being specified on the kernel command line.
** root filesystem being the most important one.
[https://systemd.io/DISCOVERABLE_PARTITIONS/ Discoverable partitions]
allow to remove this.
Phase 1 goals (high priority):
* Ship a unified kernel image as (optional) kernel sub-rpm. Users can
opt-in to use that kernel by installing the sub-rpm. Initial focus is
on booting virtual machines where we have a relatively small and well
defined set of drivers / features needed. Supporting modern physical
machines with standard setup (i.e. boot from local sata/nvme storage)
too should be easy.
* Update kernel install scripts so unified kernels are installed and
updated properly.
* Add bootloader support for unified kernel images. Add
[https://systemd.io/BOOT_LOADER_SPECIFICATION/#type-2-efi-unified-kernel-images
unified kernel bls support] to grub2, or support using systemd-boot,
or both.
Phase 1 goals (lower priority, might move to Phase 2):
* Add proper discoverable partitions support to installers (anaconda,
image builder, ...).
** Temporary workaround possible: set types using sfdisk in %post script.
** When using btrfs: configure 'root' subvolume as default volume.
* Add proper systemd-boot support to installers.
** Temporary workaround possible: run 'bootctl install' in %post script.
* Better measurement and remote attestation support.
** store kernel + initrd hashes somewhere (kernel-hashes.rpm ?) to
allow pre-calculate TPM PCR values.
** avoid using grub2 (measures every config file line executed which
is next to impossible to pre-calculate).
* Switch cloud images to use unified kernels.
Phase 2/3 goals (longer-term stuff which is not realistic to complete for F38).
* Move away from using the kernel command line for configuration.
* Move away from storing secrets in the initrd.
* Handle dracut optional modules in a different way.
systemd has some building blocks which can be used, although none of
them are used by fedora today.
[https://www.freedesktop.org/software/systemd/man/systemd-creds.html
systemd credentials] can be used for secrets (also for configuration).
The [https://www.freedesktop.org/software/systemd/man/systemd-stub.html
unified kernel stub] can load credentials from the ESP.
The unified kernel stub can also load
[https://www.freedesktop.org/software/systemd/man/systemd-sysext.html
extensions] from the ESP, which can possibly be used to replace
optional dracut modules.
== Feedback ==
== Benefit to Fedora ==
* Better secure boot support (specifically the initrd is covered by
the signature).
* Better confidential computing support (measurements are much more
useful if we know what hashes to expect for the initrd).
* More robust boot process (generating the initrd on the installed
system is fragile, root cause for kernel bugs reported is simply a
broken initrd sometimes).
== Scope ==
* Proposal owners:
** Update kernel build to create unified kernel sub-package.
*** part one: [https://gitlab.com/cki-project/kernel-ark/-/merge_requests/2179
PR#2179]
*** part two: (wip)
[https://gitlab.com/kraxel/kernel-ark/-/commits/unified/
https://gitlab.com/kraxel/kernel-ark/-/commits/unified/]
* Other developers:
** grub2: add unified kernel support
*** wip code at [https://github.com/osteffenrh/grub2/
https://github.com/osteffenrh/grub2/]
** installer(s): add support for discoverable partitions.
*** [https://bugzilla.redhat.com/show_bug.cgi?id=1075288 Bug#1075288]
* 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 ==
None (using unified kernel is opt-in for Phase 1).
== How To Test ==
Try on a existing (uefi) system:
* make sure you are running fedora 37 or rawhide.
* make sure your root filesystem has type "Linux root (x86-64)" (use
`fdisk -l` to check).
** should that not be the case use the fdisk tag command ('t') to
change the partition type.
* when using btrfs: make sure the 'root' subvolume is set as default volume.
* `dnf copr enable kraxel/unified.kernel`
* `dnf update "grub2*"`
* `dnf install kernel-unified-virt`
* `reboot`
You should find two entries in the grub2 boot menu, one for classing
kernel with separate initrd and one for the unified kernel image.
Both should boot fine.
The https://gitlab.com/kraxel/fedora-uki project has kickstart files
and helper scripts for generating virtual machine images.
* image using grub2-efi:
https://gitlab.com/kraxel/fedora-uki/-/raw/master/kickstart/fedora-uki-grub2.ks
* image using systemd-boot:
https://gitlab.com/kraxel/fedora-uki/-/raw/master/kickstart/fedora-uki-sdboot.ks
Prebuilt virtual machine images are available from
https://www.kraxel.org/fedora-uki/.
== User Experience ==
== Dependencies ==
== Contingency Plan ==
* Contingency mechanism:
** Probably none (unified kernel images are opt-in for Phase 1).
** In case we tried switching the cloud images to unified kernels:
revert the kickstart config changes.
* Contingency deadline:
* Blocks release? No
== Documentation ==
== Release Notes ==
--
Ben Cotton
He / Him / His
Fedora Program Manager
Red Hat
TZ=America/Indiana/Indianapolis
_______________________________________________
devel-announce mailing list -- devel-announce@lists.fedoraproject.org
To unsubscribe send an email to devel-announce-leave@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-announce@lists.fedoraproject.org
Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Monday, December 19, 2022
F38 proposal: Xfce-4.18 (Self-Contained Change proposal)
https://fedoraproject.org/wiki/Changes/xfce-4.18
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 ==
Xfce 4.18 is a stable release with proven components, provide features
to both new and power users alike. This change proposal is submitted
to sync fedora packages with the latest upstream release.
== Owners ==
* Name: [[User:nonamedotc| Mukundan Ragavan]], [[User:kevin| Kevin Fenzi]]
* Email: nonamedotc@fedoraproject.org, kevin@scrye.com
== Current status ==
[[Category:ChangeReadyForWrangler]]
[[Category:SelfContainedChange]]
* Targeted release: [[Releases/38 | Fedora 38 ]]
* Last updated: <!-- this is an automatic macro — you don't need to
change this line -->
{{REVISIONYEAR}}-{{REVISIONMONTH}}-{{REVISIONDAY2}}
* FESCo issue: <will be assigned by the Wrangler>
* Tracker bug: <will be assigned by the Wrangler>
* Release notes tracker: <will be assigned by the Wrangler>
== Detailed Description ==
This change migrates Xfce desktop environment (DE) to the latest
version provided by upstream developers. This release brings, amongst
others, the following features
* client-side decorations
* fractional scaling
* new status tray plugins
* Streamlined application chooser (i.e. merged "mime type editor" and
"default applications")
Full feature list can be viewed at
[https://mail.xfce.org/pipermail/xfce-announce/2022-December/001208.html]
and [https://www.xfce.org/about/tour418]
== Benefit to Fedora ==
Updating Xfce to 4.18 will provide Fedora Xfce users stable but latest
versions of upstream software. We will also be able to provide timely
bug fixes.
== Scope ==
* Proposal owners:
** Update core xfce packages to 4.18
** Rebuild plugins once core packages are build
* Other developers: N/A (not a System Wide Change)
* Release engineering: [https://pagure.io/releng/issues] (a check of
an impact with Release Engineering is needed) --> <!-- REQUIRED FOR
SYSTEM-WIDE AS WELL AS FOR SELF CONTAINED CHANGES -->
** List of deliverables: N/A (not a System Wide Change)
* Policies and guidelines: N/A (not a System Wide Change)
* Trademark approval: N/A (not needed for this Change)
== Upgrade/compatibility impact ==
<!-- What happens to systems that have had previous versions of Fedora
installed and are updated to the version containing this change? Will
anything require manual configuration or data migration? Will any
existing functionality be no longer supported? -->
<!-- REQUIRED FOR SYSTEM-WIDE CHANGES -->
N/A (not a System Wide Change)
== How To Test ==
N/A (not a System Wide Change)
== User Experience ==
* A fresh install should have fully functional Xfce DE
* Upgrade from Fedora 37 or older should be mostly seamless
No special configuration or hardware needed.
== Dependencies ==
N/A (not a System Wide Change)
== Contingency Plan ==
* Contingency mechanism: (What to do? Who will do it?) N/A (not a
System Wide Change)
* Contingency deadline: N/A (not a System Wide Change)
* Blocks release? N/A (not a System Wide Change)
* Blocks product? N/A (not a System Wide Change)
== Documentation ==
N/A (not a System Wide Change)
== Release Notes ==
Fedora 38 ships with Xfce 4.18.
--
Ben Cotton
He / Him / His
Fedora Program Manager
Red Hat
TZ=America/Indiana/Indianapolis
_______________________________________________
devel-announce mailing list -- devel-announce@lists.fedoraproject.org
To unsubscribe send an email to devel-announce-leave@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-announce@lists.fedoraproject.org
Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
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 ==
Xfce 4.18 is a stable release with proven components, provide features
to both new and power users alike. This change proposal is submitted
to sync fedora packages with the latest upstream release.
== Owners ==
* Name: [[User:nonamedotc| Mukundan Ragavan]], [[User:kevin| Kevin Fenzi]]
* Email: nonamedotc@fedoraproject.org, kevin@scrye.com
== Current status ==
[[Category:ChangeReadyForWrangler]]
[[Category:SelfContainedChange]]
* Targeted release: [[Releases/38 | Fedora 38 ]]
* Last updated: <!-- this is an automatic macro — you don't need to
change this line -->
{{REVISIONYEAR}}-{{REVISIONMONTH}}-{{REVISIONDAY2}}
* FESCo issue: <will be assigned by the Wrangler>
* Tracker bug: <will be assigned by the Wrangler>
* Release notes tracker: <will be assigned by the Wrangler>
== Detailed Description ==
This change migrates Xfce desktop environment (DE) to the latest
version provided by upstream developers. This release brings, amongst
others, the following features
* client-side decorations
* fractional scaling
* new status tray plugins
* Streamlined application chooser (i.e. merged "mime type editor" and
"default applications")
Full feature list can be viewed at
[https://mail.xfce.org/pipermail/xfce-announce/2022-December/001208.html]
and [https://www.xfce.org/about/tour418]
== Benefit to Fedora ==
Updating Xfce to 4.18 will provide Fedora Xfce users stable but latest
versions of upstream software. We will also be able to provide timely
bug fixes.
== Scope ==
* Proposal owners:
** Update core xfce packages to 4.18
** Rebuild plugins once core packages are build
* Other developers: N/A (not a System Wide Change)
* Release engineering: [https://pagure.io/releng/issues] (a check of
an impact with Release Engineering is needed) --> <!-- REQUIRED FOR
SYSTEM-WIDE AS WELL AS FOR SELF CONTAINED CHANGES -->
** List of deliverables: N/A (not a System Wide Change)
* Policies and guidelines: N/A (not a System Wide Change)
* Trademark approval: N/A (not needed for this Change)
== Upgrade/compatibility impact ==
<!-- What happens to systems that have had previous versions of Fedora
installed and are updated to the version containing this change? Will
anything require manual configuration or data migration? Will any
existing functionality be no longer supported? -->
<!-- REQUIRED FOR SYSTEM-WIDE CHANGES -->
N/A (not a System Wide Change)
== How To Test ==
N/A (not a System Wide Change)
== User Experience ==
* A fresh install should have fully functional Xfce DE
* Upgrade from Fedora 37 or older should be mostly seamless
No special configuration or hardware needed.
== Dependencies ==
N/A (not a System Wide Change)
== Contingency Plan ==
* Contingency mechanism: (What to do? Who will do it?) N/A (not a
System Wide Change)
* Contingency deadline: N/A (not a System Wide Change)
* Blocks release? N/A (not a System Wide Change)
* Blocks product? N/A (not a System Wide Change)
== Documentation ==
N/A (not a System Wide Change)
== Release Notes ==
Fedora 38 ships with Xfce 4.18.
--
Ben Cotton
He / Him / His
Fedora Program Manager
Red Hat
TZ=America/Indiana/Indianapolis
_______________________________________________
devel-announce mailing list -- devel-announce@lists.fedoraproject.org
To unsubscribe send an email to devel-announce-leave@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-announce@lists.fedoraproject.org
Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
F38 proposal: Pyramid 2.0 (Self-Contained Change proposal)
https://fedoraproject.org/wiki/Changes/Pyramid2.0
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 ==
Update Pyramid (package `python-pyramid` within Fedora) to latest major version.
== Owner ==
* Name: [[User:mattia| Mattia Verga]]
* Email: mattia.verga@fedoraproject.org
== Detailed Description ==
Pyramid 2.0 has been available since March 2021. We would like to
update Fedora package (`python-pyramid`) to this new major version
(we're now still shipping 1.10.5).
== Feedback ==
== Benefit to Fedora ==
Provide the latest available version of Pyramid framework instead of
the outdated one we're shipping.
== Scope ==
* Proposal owners:
Pyramid will be rebuilt to 2.0 in a side-tag together with dependent packages.
Affected packages are owned by nirik and abompard and usually
co-maintained by infra-sig. I will contact them and offer me to
rebuild/upgrade affected packages.
Note that rebuilding dependencies is not strictly necessary, but I'll
do to ensure compatibility with Pyramid 2.0.
About bodhi-server, we've been always running tests against pypi
packages, so I do not expect anything to be broken by the update.
* Other developers:
* Release engineering:
* 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 ==
== How To Test ==
A COPR repository has been set up to rebuild all dependencies:
https://copr.fedorainfracloud.org/coprs/mattia/Pyramid2/
== User Experience ==
This will not impact end user experience.
== Dependencies ==
* bodhi-server
* python-cornice
* python-pyramid-fas-openid
* python-pyramid-mako <-- needs to be updated to the latest git snapshot
* python-pyramid-tm
* python-pyramid_sawing
== Contingency Plan ==
* Contingency mechanism: (What to do? Who will do it?) N/A (not a
System Wide Change)
* Contingency deadline: N/A (not a System Wide Change)
== Documentation ==
N/A (not a System Wide Change)
== Release Notes ==
--
Ben Cotton
He / Him / His
Fedora Program Manager
Red Hat
TZ=America/Indiana/Indianapolis
_______________________________________________
devel-announce mailing list -- devel-announce@lists.fedoraproject.org
To unsubscribe send an email to devel-announce-leave@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-announce@lists.fedoraproject.org
Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
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 ==
Update Pyramid (package `python-pyramid` within Fedora) to latest major version.
== Owner ==
* Name: [[User:mattia| Mattia Verga]]
* Email: mattia.verga@fedoraproject.org
== Detailed Description ==
Pyramid 2.0 has been available since March 2021. We would like to
update Fedora package (`python-pyramid`) to this new major version
(we're now still shipping 1.10.5).
== Feedback ==
== Benefit to Fedora ==
Provide the latest available version of Pyramid framework instead of
the outdated one we're shipping.
== Scope ==
* Proposal owners:
Pyramid will be rebuilt to 2.0 in a side-tag together with dependent packages.
Affected packages are owned by nirik and abompard and usually
co-maintained by infra-sig. I will contact them and offer me to
rebuild/upgrade affected packages.
Note that rebuilding dependencies is not strictly necessary, but I'll
do to ensure compatibility with Pyramid 2.0.
About bodhi-server, we've been always running tests against pypi
packages, so I do not expect anything to be broken by the update.
* Other developers:
* Release engineering:
* 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 ==
== How To Test ==
A COPR repository has been set up to rebuild all dependencies:
https://copr.fedorainfracloud.org/coprs/mattia/Pyramid2/
== User Experience ==
This will not impact end user experience.
== Dependencies ==
* bodhi-server
* python-cornice
* python-pyramid-fas-openid
* python-pyramid-mako <-- needs to be updated to the latest git snapshot
* python-pyramid-tm
* python-pyramid_sawing
== Contingency Plan ==
* Contingency mechanism: (What to do? Who will do it?) N/A (not a
System Wide Change)
* Contingency deadline: N/A (not a System Wide Change)
== Documentation ==
N/A (not a System Wide Change)
== Release Notes ==
--
Ben Cotton
He / Him / His
Fedora Program Manager
Red Hat
TZ=America/Indiana/Indianapolis
_______________________________________________
devel-announce mailing list -- devel-announce@lists.fedoraproject.org
To unsubscribe send an email to devel-announce-leave@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-announce@lists.fedoraproject.org
Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Orphaned packages looking for new maintainers
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-2022-12-19.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
================================================================================
5minute orphan 2 weeks ago
CFR jvanek, orphan 2 weeks ago
CheMPS2 orphan 2 weeks ago
PolicyKit-olpc orphan 3 weeks ago
abiword chimosky, herrold, huzaifas, 2 weeks ago
orphan
aboot orphan 2 weeks ago
albatross orphan 3 weeks ago
alleyoop orphan 3 weeks ago
alure orphan 2 weeks ago
amor jgrulich, kde-sig, orphan, 3 weeks ago
rdieter, than
anki chkr, orphan 2 weeks ago
ansible-collection-google-cloud infra-sig, orphan 1 weeks ago
asn1c orphan 2 weeks ago
backup-manager orphan 3 weeks ago
bbkeys orphan 2 weeks ago
bharati-m17n orphan 2 weeks ago
bibtex2html orphan, thofmann 2 weeks ago
biosdevname lnykryn, msekleta, orphan, 2 weeks ago
vpavlin
bluecurve-classic-metacity- gnome-sig, orphan, rstrode 2 weeks ago
theme
bluecurve-gnome-theme gnome-sig, orphan, rstrode 2 weeks ago
bluecurve-gtk-themes gnome-sig, orphan, rstrode 2 weeks ago
bluecurve-icon-theme gnome-sig, orphan, rstrode 2 weeks ago
bluecurve-kde-theme gnome-sig, kkofler, orphan, 2 weeks ago
rdieter, rstrode, than
bluecurve-metacity-theme gnome-sig, orphan, rstrode 2 weeks ago
bluecurve-xmms-skin gnome-sig, orphan, rstrode 2 weeks ago
cairo-clock orphan 2 weeks ago
code-editor orphan 3 weeks ago
compton orphan 3 weeks ago
cups-bjnp orphan 3 weeks ago
curlpp orphan 2 weeks ago
devilspie2 orphan 0 weeks ago
dmz-cursor-themes company, orphan 3 weeks ago
ejabberd bowlofeggs, jcline, orphan, 2 weeks ago
xavierb
erlang-epgsql lkundrak, orphan 3 weeks ago
eureka orphan 2 weeks ago
fcitx cheeselee, cicku, orphan, pwu, 3 weeks ago
yanqiyu
fcitx-chewing cheeselee, orphan, yanqiyu 3 weeks ago
fcitx-cloudpinyin cheeselee, orphan, yanqiyu 3 weeks ago
fcitx-configtool cheeselee, orphan, yanqiyu 3 weeks ago
fcitx-fbterm cheeselee, orphan, yanqiyu 3 weeks ago
fcitx-hangul cheeselee, orphan, yanqiyu 3 weeks ago
fcitx-m17n cheeselee, orphan, yanqiyu 3 weeks ago
fcitx-sunpinyin cheeselee, orphan, yanqiyu 3 weeks ago
fcitx-table-extra cheeselee, orphan, yanqiyu 3 weeks ago
fcitx-table-other cheeselee, orphan, yanqiyu 3 weeks ago
fcitx-ui-light cheeselee, orphan, yanqiyu 3 weeks ago
fcitx-unikey cheeselee, orphan, yanqiyu 3 weeks ago
fros orphan 3 weeks ago
fwsnort orphan 3 weeks ago
gconf-editor alexl, caolanm, gnome-sig, 2 weeks ago
mbarnes, orphan, rhughes,
rstrode, ssp
gdeploy godas, orphan 2 weeks ago
ghasher orphan 2 weeks ago
gl-117 orphan, steve 2 weeks ago
glusterfs-selinux kkeithle, orphan, shwetha 2 weeks ago
gnome-activity-journal orphan 3 weeks ago
gnome-nds-thumbnailer orphan 3 weeks ago
gnome-search-tool gnome-sig, orphan 2 weeks ago
gnome-shell-theme-selene orphan 3 weeks ago
gnonlin orphan 2 weeks ago
golang-github-gocomply-scap go-sig, orphan 3 weeks ago
golang-github-google- go-sig, orphan 5 weeks ago
containerregistry
golang-github-hanwen-fuse go-sig, orphan 5 weeks ago
golang-github-justinas-alice go-sig, orphan 2 weeks ago
golang-github-lpabon-godbc go-sig, orphan 3 weeks ago
golang-github-mitchellh-cli go-sig, jchaloup, orphan 2 weeks ago
golang-github-pkg-browser go-sig, orphan 2 weeks ago
golang-github-spaolacci-murmur3 go-sig, orphan 2 weeks ago
golang-github-sqshq-sampler atim, go-sig, orphan 1 weeks ago
golie go-sig, orphan 3 weeks ago
grads orphan 3 weeks ago
gsm-ussd orphan 3 weeks ago
gtkhtml3 alexl, caolanm, mbarnes, 2 weeks ago
orphan, rhughes, rstrode, ssp
heisenbug-kde-theme jreznik, orphan 3 weeks ago
highcontrast-qt jgrulich, orphan 3 weeks ago
holland orphan, survient 3 weeks ago
jama orphan 2 weeks ago
jargs ellert, orphan 2 weeks ago
java-mersenne-twister orphan 3 weeks ago
javadocofflinesearch orphan 4 weeks ago
jcodings orphan 3 weeks ago
jffi orphan 3 weeks ago
jgrapht gil, orphan 3 weeks ago
jnr-constants orphan 3 weeks ago
jnr-ffi orphan 3 weeks ago
jnr-netdb orphan 3 weeks ago
jnr-posix orphan 3 weeks ago
jnr-x86asm orphan 3 weeks ago
js-web-socket-js orphan 3 weeks ago
kcm-fcitx cheeselee, orphan, yanqiyu 3 weeks ago
kfaenza-icon-theme orphan 3 weeks ago
kfilefactory orphan 3 weeks ago
kompose dustymabe, go-sig, orphan 3 weeks ago
libannodex orphan 2 weeks ago
libbonobo alexl, caolanm, gnome-sig, 2 weeks ago
mbarnes, orphan, rhughes,
rstrode, ssp
libbonoboui alexl, caolanm, gnome-sig, 2 weeks ago
mbarnes, orphan, rhughes,
rstrode, ssp
libbsr orphan 2 weeks ago
libcmml orphan 2 weeks ago
libcmpiutil orphan 2 weeks ago
libfap orphan 3 weeks ago
libgnome alexl, caolanm, gnome-sig, 2 weeks ago
mbarnes, orphan, rhughes,
rstrode, ssp
libgnomeui alexl, caolanm, gnome-sig, 2 weeks ago
mbarnes, orphan, rhughes,
rstrode, ssp
libmacaroons ellert, orphan 2 weeks ago
libmodman orphan 2 weeks ago
libnatspec orphan 3 weeks ago
liboil ajax, alexl, caolanm, gnome- 2 weeks ago
sig, mbarnes, orphan, rhughes,
rstrode, ssp
libstroke orphan 2 weeks ago
libusbauth-configparser orphan 3 weeks ago
libverto-jsonrpc orphan 2 weeks ago
libvirt-cim orphan 2 weeks ago
libvirt-java bkearney, orphan 2 weeks ago
lttv greenscientist, orphan 2 weeks ago
lua-fun orphan 2 weeks ago
maloc orphan 2 weeks ago
maven-scm mizdebsk, orphan 2 weeks ago
mediawiki-backtick-code orphan 3 weeks ago
mediawiki-semantic orphan 2 weeks ago
mediawiki-validator orphan 2 weeks ago
mesos orphan 3 weeks ago
mingw-cxxtest orphan 3 weeks ago
mingw-pcre orphan 3 weeks ago
mingw-sigar orphan 3 weeks ago
moarvm orphan 3 weeks ago
mod_annodex orphan 2 weeks ago
monosim orphan 3 weeks ago
msgpuck orphan 2 weeks ago
mupen64plus dreua, orphan 2 weeks ago
myman orphan 3 weeks ago
nailgun orphan 3 weeks ago
nodejs-supervisor orphan 2 weeks ago
nqp orphan 3 weeks ago
ogmtools orphan 3 weeks ago
openjpeg orphan, phracek, rdieter 2 weeks ago
pakiti andreamanzi, orphan 3 weeks ago
perl-Gnome2-Wnck orphan 3 weeks ago
perl-Goo-Canvas orphan 3 weeks ago
perl-Gtk2-Unique orphan 3 weeks ago
perl-MARC-Charset orphan 3 weeks ago
perl-MARC-XML orphan 3 weeks ago
perl-Mail-Procmail orphan 0 weeks ago
perl-POE-Component-Client-Ping orphan 3 weeks ago
perl-Parse-EDID epel-packagers-sig, jcpunk, 3 weeks ago
orphan
perl-TAP-Harness-Multiple orphan 3 weeks ago
perl-Test-POE-Server-TCP orphan, yaneti 3 weeks ago
php-pdepend-PHP-Depend cdamian, orphan, remi 3 weeks ago
php-phpmd-PHP-PMD cdamian, orphan, remi 3 weeks ago
php-phpunit-bytekit cdamian, orphan, remi 3 weeks ago
php-phpunit-phpcpd cdamian, orphan, remi 3 weeks ago
php-phpunit-phploc cdamian, orphan, remi 3 weeks ago
php-zipstream orphan 3 weeks ago
plug orphan 3 weeks ago
proxychains-ng epel-packagers-sig, orphan, 2 weeks ago
salimma
pydf cstratak, orphan 3 weeks ago
pynag orphan 2 weeks ago
pysvn barryascott, orphan, sgallagh 2 weeks ago
python-Pyped orphan 2 weeks ago
python-bintrees orphan 2 weeks ago
python-colour-runner orphan 2 weeks ago
python-cornice-sphinx infra-sig, orphan 5 weeks ago
python-cov-core abompard, orphan 3 weeks ago
python-cssmin orphan, qa-tools-sig 2 weeks ago
python-django-filter lbazan, orphan 3 weeks ago
python-django-tastypie cquad, mrunge, orphan, 3 weeks ago
stevetraylen
python-dockerpty lsm5, orphan, ttomecek 3 weeks ago
python-flask-restful kparal, orphan, qa-tools-sig, 3 weeks ago
ralph
python-formats orphan 2 weeks ago
python-frozen-flask echevemaster, orphan 3 weeks ago
python-gnocchiclient mrunge, openstack-sig, orphan 2 weeks ago
python-gzipstream orphan 0 weeks ago
python-importmagic orphan 3 weeks ago
python-jsonmodels orphan 2 weeks ago
python-lightblue orphan 3 weeks ago
python-okaara orphan 3 weeks ago
python-pmw orphan 2 weeks ago
python-posix_ipc orphan 2 weeks ago
python-pydispatcher orphan 2 weeks ago
python-pykeepass atim, limb, orphan 2 weeks ago
python-pynlpl orphan 2 weeks ago
python-pytest-beakerlib orphan 2 weeks ago
python-pytest-sanic orphan 2 weeks ago
python-restsh orphan 3 weeks ago
python-signalfd orphan 2 weeks ago
python-simpy orphan 2 weeks ago
python-spdx orphan 3 weeks ago
python-spdx-lookup orphan 3 weeks ago
python-tortilla orphan 2 weeks ago
python-upt-cpan orphan 3 weeks ago
python-upt-fedora orphan 3 weeks ago
python-upt-pypi orphan 3 weeks ago
python-upt-rubygems orphan 3 weeks ago
python-versiontools mrunge, orphan 3 weeks ago
python-virtualenv-api cstratak, orphan, python- 2 weeks ago
packagers-sig
python-websockify apevec, epel-packagers-sig, 2 weeks ago
lon, ndipanov, orphan
python-xtermcolor orphan 3 weeks ago
python-zabbix-api-erigones orphan 2 weeks ago
q orphan 3 weeks ago
qconf orphan 3 weeks ago
qxmpp orphan 3 weeks ago
rakudo orphan, ppisar, steve 3 weeks ago
rakudo-MIME-Base64 orphan 3 weeks ago
rakudo-Readline orphan 3 weeks ago
rakudo-URI orphan 3 weeks ago
rakudo-XML orphan 3 weeks ago
rakudo-zef orphan 3 weeks ago
rdfind orphan 3 weeks ago
refmac-dictionary orphan 2 weeks ago
resultsdb orphan, qa-tools-sig 2 weeks ago
resultsdb_frontend orphan, qa-tools-sig 2 weeks ago
rhythmbox-alternative-toolbar orphan 2 weeks ago
rshim orphan 3 weeks ago
ruby-ncurses orphan 2 weeks ago
rubygem-ZenTest orphan, tdawson 2 weeks ago
rubygem-abstract orphan 2 weeks ago
rubygem-activeresource orphan 2 weeks ago
rubygem-archive-tar-minitar orphan, tdawson 2 weeks ago
rubygem-cinch orphan 3 weeks ago
rubygem- orphan 3 weeks ago
declarative_authorization
rubygem-foreigner orphan 3 weeks ago
rubygem-lockfile orphan 2 weeks ago
rubygem-memcache-client orphan, tdawson 2 weeks ago
rubygem-more_core_extensions orphan 2 weeks ago
rubygem-openscap orphan 3 weeks ago
rubygem-plist orphan 3 weeks ago
rubygem-rubeyond orphan 3 weeks ago
rubygem-scruffy orphan 2 weeks ago
rubygem-session orphan 3 weeks ago
rubygem-sexp_processor orphan 2 weeks ago
rubygem-state_machine orphan 3 weeks ago
rubygem-syntax orphan, stahnma 2 weeks ago
rubygem-uuidtools orphan 2 weeks ago
rubygem-yard brandfbb, jaruga, orphan 2 weeks ago
rust-dbus-tokio orphan, rust-sig 3 weeks ago
rust-faccess orphan, rust-sig 0 weeks ago
rust-fbthrift_codegen_includer_ orphan, rust-sig 2 weeks ago
proc_macro
rust-fdlimit orphan, rust-sig 2 weeks ago
rust-iptables orphan, rust-sig 0 weeks ago
rust-lipsum orphan, rust-sig 2 weeks ago
rust-loggerv orphan, rust-sig 2 weeks ago
rust-lzw orphan, rust-sig 2 weeks ago
rust-macro-attr orphan, rust-sig 2 weeks ago
rust-mdl orphan, rust-sig 2 weeks ago
rust-mktemp orphan, rust-sig 2 weeks ago
rust-mnt orphan, rust-sig 2 weeks ago
rust-newtype_derive orphan, rust-sig 2 weeks ago
rust-oauth2 jbtrystram, orphan, rust-sig 1 weeks ago
rust-odds orphan, rust-sig 2 weeks ago
rust-osstrtools orphan, rust-sig 2 weeks ago
rust-parse_cfg orphan, rust-sig 2 weeks ago
rust-permutate orphan, rust-sig 2 weeks ago
rust-piper orphan, rust-sig 2 weeks ago
rust-proc-quote-impl orphan, rust-sig 2 weeks ago
rust-process_path orphan, rust-sig 2 weeks ago
rust-protoc-rust orphan, rust-sig 2 weeks ago
rust-quickersort orphan, rust-sig 2 weeks ago
rust-relay orphan, rust-sig 2 weeks ago
rust-rustdoc-stripper orphan, rust-sig 2 weeks ago
rust-rustfilt orphan, rust-sig 2 weeks ago
rust-safe-transmute orphan, rust-sig 2 weeks ago
rust-scoped-tls-hkt orphan, rust-sig 2 weeks ago
rust-serde-pickle orphan, rust-sig 2 weeks ago
rust-simple-error orphan, rust-sig 0 weeks ago
rust-sluice orphan, rust-sig 2 weeks ago
rust-spinning_top orphan, rust-sig 2 weeks ago
rust-spmc orphan, rust-sig 2 weeks ago
rust-string_cache_shared orphan, rust-sig 2 weeks ago
rust-strings orphan, rust-sig 2 weeks ago
rust-sudo_plugin orphan, rust-sig 2 weeks ago
rust-sxd-document orphan, rust-sig 2 weeks ago
rust-synom orphan, rust-sig 2 weeks ago
rust-tabwriter orphan, rust-sig 2 weeks ago
rust-take orphan, rust-sig 2 weeks ago
rust-unic-ucd-category orphan, rust-sig 2 weeks ago
rust-url_serde orphan, rust-sig 2 weeks ago
rust-utf8-ranges orphan, rust-sig 2 weeks ago
saga orphan 4 weeks ago
sassist orphan 3 weeks ago
schroedinger-cat-kde-theme jreznik, orphan 3 weeks ago
scim-anthy orphan 2 weeks ago
seahorse-nautilus gnome-sig, orphan, stefw 2 weeks ago
seren orphan 3 weeks ago
simple-mtpfs orphan 2 weeks ago
sipcalc orphan 3 weeks ago
spamprobe orphan 0 weeks ago
spawn-fcgi orphan 2 weeks ago
spherical-cow-kde-theme jreznik, orphan 3 weeks ago
sshrc orphan 2 weeks ago
sugar-flip chimosky, orphan 3 weeks ago
sugar-fototoon aperezbios, chimosky, orphan 3 weeks ago
sugar-fractionbounce chimosky, orphan 3 weeks ago
sugar-jukebox chimosky, orphan, pbrobinson 3 weeks ago
sugar-locosugar chimosky, orphan 3 weeks ago
sugar-nutrition chimosky, orphan 3 weeks ago
sugar-paint chimosky, orphan, pbrobinson 3 weeks ago
sugar-playgo chimosky, orphan, pbrobinson 3 weeks ago
sugar-portfolio chimosky, orphan 3 weeks ago
sugar-pukllanapac chimosky, orphan 3 weeks ago
sugar-recall chimosky, orphan 3 weeks ago
sugar-typing-turtle chimosky, orphan 3 weeks ago
sugar-words chimosky, orphan 3 weeks ago
superkb echevemaster, orphan 2 weeks ago
sweep orphan 3 weeks ago
switchboard-plug-tweaks orphan 5 weeks ago
system-storage-manager lczerner, orphan 3 weeks ago
tboot dcantrell, miaojun0823, 3 weeks ago
orphan, yunyings
tetrominos orphan 3 weeks ago
themonospot-base orphan 3 weeks ago
themonospot-console orphan 3 weeks ago
themonospot-gui-gtk orphan 3 weeks ago
themonospot-plugin-avi orphan 3 weeks ago
themonospot-plugin-mkv orphan 3 weeks ago
thunarx-python kevin, nonamedotc, orphan 3 weeks ago
tito frostyx, maxamillion, orphan 3 weeks ago
tkcvs lkundrak, orphan 3 weeks ago
tnt orphan 2 weeks ago
torrent-file-editor orphan 3 weeks ago
tpp orphan 3 weeks ago
tss2 orphan, snits 3 weeks ago
upt orphan 3 weeks ago
usbauth orphan 3 weeks ago
usbauth-notifier orphan 3 weeks ago
vcglib orphan 2 weeks ago
vicious orphan 2 weeks ago
vim-nerdtree orphan 3 weeks ago
whipper-plugin-eaclogger orphan 2 weeks ago
wipe orphan 2 weeks ago
wmMatrix orphan 2 weeks ago
wmclock orphan 2 weeks ago
wmnd orphan 2 weeks ago
wmpager orphan 2 weeks ago
wmsystemtray orphan 2 weeks ago
wordpress-plugin-defaults orphan 3 weeks ago
workspace orphan 3 weeks ago
wv lkundrak, orphan 2 weeks ago
xaos orphan 3 weeks ago
xjparse orphan 3 weeks ago
xmltool orphan 2 weeks ago
yourls orphan 2 weeks ago
The following packages require above mentioned packages:
Report too long, see the full version at
https://churchyard.fedorapeople.org/orphans-2022-12-19.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):
abompard: python-cov-core
ajax: liboil
alexl: gconf-editor, liboil, libgnomeui, gtkhtml3, libbonobo, libbonoboui, libgnome
amdunn: maven-scm
andreamanzi: pakiti, libmacaroons
andymenderunix: openjpeg, vcglib
antiaircraft: libbonoboui, libbonobo
aperezbios: sugar-fototoon
apevec: python-websockify
astro-sig: libbonoboui, libgnome, libgnomeui
athoscr: golang-github-hanwen-fuse
atim: vim-nerdtree, python-pykeepass, golang-github-sqshq-sampler, alure
averi: perl-Test-POE-Server-TCP
aviso: libgnome
barryascott: pysvn
besser82: rubygem-yard
bkearney: libvirt-java
bowlofeggs: ejabberd
brandfbb: rubygem-yard
bruno: libbonoboui, libgnome, libgnomeui
buc: libbonoboui, libgnome, libbonobo, libgnomeui
caolanm: gconf-editor, liboil, libgnomeui, gtkhtml3, libbonobo, libbonoboui,
libgnome
cdamian: php-phpunit-bytekit, php-phpmd-PHP-PMD, php-pdepend-PHP-Depend,
php-phpunit-phploc, php-phpunit-phpcpd
cdorney: maven-scm
cfu: maven-scm
cheese: libbonoboui, libgnomeui
cheeselee: fcitx-table-extra, fcitx-fbterm, fcitx-table-other, fcitx-m17n,
fcitx-unikey, fcitx-hangul, kcm-fcitx, fcitx-configtool, fcitx-cloudpinyin,
fcitx-ui-light, fcitx-chewing, fcitx, fcitx-sunpinyin
chimosky: sugar-nutrition, abiword, sugar-jukebox, sugar-flip, sugar-playgo,
sugar-paint, sugar-portfolio, sugar-words, sugar-typing-turtle,
sugar-pukllanapac, sugar-fototoon, sugar-locosugar, sugar-fractionbounce,
sugar-recall, wv
chkr: anki
cicku: thunarx-python, libgnomeui, gtkhtml3, pysvn, libbonobo, fcitx,
libbonoboui, libgnome
company: dmz-cursor-themes
copperi: golang-github-hanwen-fuse, golang-github-mitchellh-cli
copr-sig: python-virtualenv-api, python-flask-restful, tito
cquad: maven-scm, python-django-tastypie
cstratak: pydf, python-virtualenv-api
cwickert: libbonoboui, libgnome, libgnomeui
dcantrell: tboot
dcavalca: python-websockify, rubygem-yard, golang-github-mitchellh-cli,
golang-github-spaolacci-murmur3, libstroke, golang-github-hanwen-fuse
dchen: maven-scm
deamn: maven-scm
devrim: python-cssmin
didiksupriadi41: jcodings, maven-scm
dmsimard: python-django-filter
dnglaze: wv
dreua: mupen64plus
dustymabe: kompose
ebaron: maven-scm
echevemaster: python-pydispatcher, python-frozen-flask, libbonobo, libbonoboui,
superkb
eclipse-sig: maven-scm
eclipseo: maven-scm, golang-github-mitchellh-cli,
golang-github-google-containerregistry, golang-github-spaolacci-murmur3,
golang-github-hanwen-fuse, golang-github-pkg-browser
ellert: jargs, libmacaroons
epel-packagers-sig: python-websockify, golang-github-hanwen-fuse,
proxychains-ng, perl-Parse-EDID
fab: libbonoboui, libgnome, libgnomeui
filbranden: rubygem-yard
filiperosset: libbonoboui, libgnome, libgnomeui, wv
frostyx: python-virtualenv-api, python-flask-restful, tito
fujiwara: libbonoboui, libgnomeui
gil: jgrapht
gilboa: alure
gnome-sig: bluecurve-classic-metacity-theme, gconf-editor, liboil,
bluecurve-xmms-skin, gnome-search-tool, libgnomeui, bluecurve-gtk-themes,
bluecurve-gnome-theme, libbonobo, bluecurve-metacity-theme, seahorse-nautilus,
bluecurve-kde-theme, libbonoboui, libgnome, bluecurve-icon-theme
go-sig: kompose, maven-scm, golang-github-gocomply-scap,
golang-github-lpabon-godbc, golang-github-mitchellh-cli,
golang-github-google-containerregistry, golang-github-spaolacci-murmur3,
golang-github-hanwen-fuse, golang-github-pkg-browser,
golang-github-justinas-alice, golie, golang-github-sqshq-sampler
godas: gdeploy
gordonmessmer: python-virtualenv-api
gotmax23: golang-github-hanwen-fuse, golang-github-mitchellh-cli
greenscientist: lttv
greghellings: gtkhtml3, rubygem-yard
hannes: libbonoboui, libgnomeui
herrold: abiword, wv
huzaifas: abiword, wv
ignatenkobrain: python-django-filter
ilgrad: rubygem-yard
infra-sig: golang-github-hanwen-fuse, python-cornice-sphinx,
ansible-collection-google-cloud, golang-github-mitchellh-cli
iztokf: python-cssmin
jackorp: rubygem-yard
jamatos: wv
jaruga: rubygem-yard
jbtrystram: rust-oauth2
jchaloup: golang-github-mitchellh-cli, golang-github-hanwen-fuse
jcline: ejabberd
jcpunk: perl-Parse-EDID
jerboaa: maven-scm
jgrulich: amor, mingw-pcre, highcontrast-qt
jjames: maven-scm
jjelen: maven-scm
jkastner: wv
jmagne: maven-scm
jonathanspw: python-websockify, libmacaroons, perl-Parse-EDID
jonkni: libmacaroons
jplesnik: libmacaroons, libgnomeui, libbonobo, perl-Test-POE-Server-TCP,
libbonoboui, libgnome
jreznik: spherical-cow-kde-theme, schroedinger-cat-kde-theme, heisenbug-kde-theme
jussilehtola: CheMPS2
jvanek: maven-scm, CFR
kde-sig: qconf, amor, wv
kengert: openjpeg
kevin: python-virtualenv-api, thunarx-python
kkeithle: glusterfs-selinux
kkofler: bluecurve-kde-theme
kparal: python-flask-restful
kushal: rubygem-yard
laxathom: libbonoboui, libgnome, libbonobo, libgnomeui
lbazan: libbonoboui, python-django-filter, libbonobo
lczerner: system-storage-manager
lfield: libmacaroons
limb: thunarx-python, libgnomeui, pysvn, libbonobo, libbonoboui, libgnome,
python-pykeepass
lkf: wv
lkundrak: rubygem-yard, tkcvs, wv, erlang-epgsql, rubygem-archive-tar-minitar
lnykryn: biosdevname
lon: python-websockify
lsm5: python-dockerpty, golang-github-hanwen-fuse, golang-github-mitchellh-cli
lyarwood: python-websockify
martinkg: perl-Goo-Canvas, alure
mattia: golang-github-mitchellh-cli, libgnomeui, golang-github-hanwen-fuse,
libbonoboui, libgnome
maxamillion: rubygem-yard, tito
mbarnes: gconf-editor, liboil, libgnomeui, gtkhtml3, libbonobo, libbonoboui,
libgnome
mcermak: libstroke
mcrha: libgnome
melmorabity: dmz-cursor-themes
mharmsen: maven-scm
mhayden: maven-scm
mhjacks: moarvm, rakudo, nqp
miaojun0823: tboot
mikep: golang-github-hanwen-fuse
mipatras: libmacaroons
mizdebsk: maven-scm
mkoncek: maven-scm
mrnuke: wv
mrunge: python-versiontools, python-django-tastypie, python-gnocchiclient
mschwendt: libgnome
msekleta: biosdevname
msuchy: python-flask-restful
mtasaka: rubygem-yard, libgnomeui, libbonobo, libbonoboui, libgnome
ndipanov: python-websockify
neuro-sig: rubygem-yard
ngompa: python-django-filter
nonamedotc: thunarx-python
olea: libbonoboui, libbonobo
openstack-sig: python-gnocchiclient
oturpe: rubygem-yard
pbrobinson: abiword, sugar-jukebox, sugar-playgo, sugar-paint, wv
pcpa: maven-scm
peter: libstroke
phracek: openjpeg
ppisar: moarvm, libmacaroons, libgnomeui, rakudo, libbonobo,
perl-Test-POE-Server-TCP, libbonoboui, libgnome, nqp
praiskup: python-virtualenv-api, python-flask-restful, tito
pwalter: pysvn, thunarx-python
pwu: fcitx
python-packagers-sig: python-virtualenv-api, maven-scm
qa-tools-sig: python-cssmin, python-flask-restful, resultsdb_frontend, resultsdb
qulogic: golang-github-hanwen-fuse, golang-github-mitchellh-cli
r-maint-sig: libmacaroons
ralph: python-flask-restful
rathann: maloc
rdieter: bluecurve-kde-theme, amor, openjpeg, wv
remi: php-phpunit-bytekit, php-phpmd-PHP-PMD, php-pdepend-PHP-Depend,
php-phpunit-phploc, php-phpunit-phpcpd
rgrunber: maven-scm
rhughes: gconf-editor, liboil, libgnomeui, gtkhtml3, libbonobo, libbonoboui,
libgnome
rjones: mingw-pcre
rocha: libmacaroons
rombobeorn: libbonoboui, libgnome, libbonobo, libgnomeui
rrankin: wv
rstrode: bluecurve-classic-metacity-theme, gconf-editor, liboil,
bluecurve-xmms-skin, libgnomeui, bluecurve-gtk-themes, bluecurve-gnome-theme,
gtkhtml3, libbonobo, bluecurve-metacity-theme, bluecurve-kde-theme,
libbonoboui, libgnome, bluecurve-icon-theme
ruby-packagers-sig: rubygem-yard
rust-sig: rust-sxd-document, rust-mnt, rust-rustdoc-stripper, rust-dbus-tokio,
rust-newtype_derive, rust-rustfilt, rust-unic-ucd-category, rust-sluice,
rust-spmc, rust-macro-attr, rust-string_cache_shared, rust-loggerv, rust-piper,
rust-proc-quote-impl, rust-mdl, rust-scoped-tls-hkt, rust-protoc-rust,
rust-tabwriter, rust-serde-pickle, rust-quickersort, rust-parse_cfg,
rust-lipsum, rust-lzw, rust-odds, rust-fdlimit, rust-process_path, rust-relay,
rust-safe-transmute, rust-synom, rust-sudo_plugin, rust-permutate,
rust-spinning_top, rust-utf8-ranges, rust-faccess, rust-strings,
rust-osstrtools, rust-iptables, rust-simple-error, rust-oauth2, rust-take,
rust-fbthrift_codegen_includer_proc_macro, rust-url_serde, rust-mktemp
sagitter: openjpeg, python-pmw, maven-scm, maloc
sailer: mingw-pcre
salimma: rubygem-yard, proxychains-ng, libgnomeui, libstroke, libbonoboui, libgnome
schlupov: python-flask-restful
sergiomb: maven-scm, golang-github-mitchellh-cli, golang-github-hanwen-fuse,
python-pmw, maloc
sgallagh: pysvn
sharkcz: libbonoboui, libgnome, libbonobo, libgnomeui
shwetha: glusterfs-selinux
simonm: libmacaroons
smani: mingw-pcre
snits: tss2
spot: libbonoboui, libbonobo, alure
ssp: gconf-editor, liboil, libgnomeui, gtkhtml3, libbonobo, libbonoboui, libgnome
stahnma: rubygem-syntax, rubygem-yard
stefw: seahorse-nautilus
steve: gl-117, moarvm, libgnomeui, libbonoboui, rakudo, libgnome, nqp
stevetraylen: python-django-tastypie
survient: holland
tartare: libbonoboui, libgnome, libgnomeui
tdawson: rubygem-yard, rubygem-ZenTest, rubygem-archive-tar-minitar,
rubygem-memcache-client
than: bluecurve-kde-theme, amor
thm: libbonoboui, libbonobo
thofmann: bibtex2html
thunderbirdtr: qconf
tpokorra: libbonoboui, libgnome, libbonobo, libgnomeui
ttomecek: python-dockerpty
ueno: fcitx
valtri: rubygem-yard
vokac: libmacaroons
vondruch: rubygem-yard
vpavlin: biosdevname
xavierb: ejabberd
yaneti: perl-Test-POE-Server-TCP
yanqiyu: fcitx-table-extra, fcitx-fbterm, fcitx-table-other, fcitx-m17n,
fcitx-unikey, fcitx-hangul, kcm-fcitx, golang-github-mitchellh-cli,
fcitx-configtool, fcitx-cloudpinyin, fcitx-ui-light, golang-github-hanwen-fuse,
fcitx-chewing, fcitx, fcitx-sunpinyin
yunyings: tboot
--
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
Report finished at 2022-12-19 15:17:23 UTC
_______________________________________________
devel-announce mailing list -- devel-announce@lists.fedoraproject.org
To unsubscribe send an email to devel-announce-leave@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-announce@lists.fedoraproject.org
Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
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-2022-12-19.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
================================================================================
5minute orphan 2 weeks ago
CFR jvanek, orphan 2 weeks ago
CheMPS2 orphan 2 weeks ago
PolicyKit-olpc orphan 3 weeks ago
abiword chimosky, herrold, huzaifas, 2 weeks ago
orphan
aboot orphan 2 weeks ago
albatross orphan 3 weeks ago
alleyoop orphan 3 weeks ago
alure orphan 2 weeks ago
amor jgrulich, kde-sig, orphan, 3 weeks ago
rdieter, than
anki chkr, orphan 2 weeks ago
ansible-collection-google-cloud infra-sig, orphan 1 weeks ago
asn1c orphan 2 weeks ago
backup-manager orphan 3 weeks ago
bbkeys orphan 2 weeks ago
bharati-m17n orphan 2 weeks ago
bibtex2html orphan, thofmann 2 weeks ago
biosdevname lnykryn, msekleta, orphan, 2 weeks ago
vpavlin
bluecurve-classic-metacity- gnome-sig, orphan, rstrode 2 weeks ago
theme
bluecurve-gnome-theme gnome-sig, orphan, rstrode 2 weeks ago
bluecurve-gtk-themes gnome-sig, orphan, rstrode 2 weeks ago
bluecurve-icon-theme gnome-sig, orphan, rstrode 2 weeks ago
bluecurve-kde-theme gnome-sig, kkofler, orphan, 2 weeks ago
rdieter, rstrode, than
bluecurve-metacity-theme gnome-sig, orphan, rstrode 2 weeks ago
bluecurve-xmms-skin gnome-sig, orphan, rstrode 2 weeks ago
cairo-clock orphan 2 weeks ago
code-editor orphan 3 weeks ago
compton orphan 3 weeks ago
cups-bjnp orphan 3 weeks ago
curlpp orphan 2 weeks ago
devilspie2 orphan 0 weeks ago
dmz-cursor-themes company, orphan 3 weeks ago
ejabberd bowlofeggs, jcline, orphan, 2 weeks ago
xavierb
erlang-epgsql lkundrak, orphan 3 weeks ago
eureka orphan 2 weeks ago
fcitx cheeselee, cicku, orphan, pwu, 3 weeks ago
yanqiyu
fcitx-chewing cheeselee, orphan, yanqiyu 3 weeks ago
fcitx-cloudpinyin cheeselee, orphan, yanqiyu 3 weeks ago
fcitx-configtool cheeselee, orphan, yanqiyu 3 weeks ago
fcitx-fbterm cheeselee, orphan, yanqiyu 3 weeks ago
fcitx-hangul cheeselee, orphan, yanqiyu 3 weeks ago
fcitx-m17n cheeselee, orphan, yanqiyu 3 weeks ago
fcitx-sunpinyin cheeselee, orphan, yanqiyu 3 weeks ago
fcitx-table-extra cheeselee, orphan, yanqiyu 3 weeks ago
fcitx-table-other cheeselee, orphan, yanqiyu 3 weeks ago
fcitx-ui-light cheeselee, orphan, yanqiyu 3 weeks ago
fcitx-unikey cheeselee, orphan, yanqiyu 3 weeks ago
fros orphan 3 weeks ago
fwsnort orphan 3 weeks ago
gconf-editor alexl, caolanm, gnome-sig, 2 weeks ago
mbarnes, orphan, rhughes,
rstrode, ssp
gdeploy godas, orphan 2 weeks ago
ghasher orphan 2 weeks ago
gl-117 orphan, steve 2 weeks ago
glusterfs-selinux kkeithle, orphan, shwetha 2 weeks ago
gnome-activity-journal orphan 3 weeks ago
gnome-nds-thumbnailer orphan 3 weeks ago
gnome-search-tool gnome-sig, orphan 2 weeks ago
gnome-shell-theme-selene orphan 3 weeks ago
gnonlin orphan 2 weeks ago
golang-github-gocomply-scap go-sig, orphan 3 weeks ago
golang-github-google- go-sig, orphan 5 weeks ago
containerregistry
golang-github-hanwen-fuse go-sig, orphan 5 weeks ago
golang-github-justinas-alice go-sig, orphan 2 weeks ago
golang-github-lpabon-godbc go-sig, orphan 3 weeks ago
golang-github-mitchellh-cli go-sig, jchaloup, orphan 2 weeks ago
golang-github-pkg-browser go-sig, orphan 2 weeks ago
golang-github-spaolacci-murmur3 go-sig, orphan 2 weeks ago
golang-github-sqshq-sampler atim, go-sig, orphan 1 weeks ago
golie go-sig, orphan 3 weeks ago
grads orphan 3 weeks ago
gsm-ussd orphan 3 weeks ago
gtkhtml3 alexl, caolanm, mbarnes, 2 weeks ago
orphan, rhughes, rstrode, ssp
heisenbug-kde-theme jreznik, orphan 3 weeks ago
highcontrast-qt jgrulich, orphan 3 weeks ago
holland orphan, survient 3 weeks ago
jama orphan 2 weeks ago
jargs ellert, orphan 2 weeks ago
java-mersenne-twister orphan 3 weeks ago
javadocofflinesearch orphan 4 weeks ago
jcodings orphan 3 weeks ago
jffi orphan 3 weeks ago
jgrapht gil, orphan 3 weeks ago
jnr-constants orphan 3 weeks ago
jnr-ffi orphan 3 weeks ago
jnr-netdb orphan 3 weeks ago
jnr-posix orphan 3 weeks ago
jnr-x86asm orphan 3 weeks ago
js-web-socket-js orphan 3 weeks ago
kcm-fcitx cheeselee, orphan, yanqiyu 3 weeks ago
kfaenza-icon-theme orphan 3 weeks ago
kfilefactory orphan 3 weeks ago
kompose dustymabe, go-sig, orphan 3 weeks ago
libannodex orphan 2 weeks ago
libbonobo alexl, caolanm, gnome-sig, 2 weeks ago
mbarnes, orphan, rhughes,
rstrode, ssp
libbonoboui alexl, caolanm, gnome-sig, 2 weeks ago
mbarnes, orphan, rhughes,
rstrode, ssp
libbsr orphan 2 weeks ago
libcmml orphan 2 weeks ago
libcmpiutil orphan 2 weeks ago
libfap orphan 3 weeks ago
libgnome alexl, caolanm, gnome-sig, 2 weeks ago
mbarnes, orphan, rhughes,
rstrode, ssp
libgnomeui alexl, caolanm, gnome-sig, 2 weeks ago
mbarnes, orphan, rhughes,
rstrode, ssp
libmacaroons ellert, orphan 2 weeks ago
libmodman orphan 2 weeks ago
libnatspec orphan 3 weeks ago
liboil ajax, alexl, caolanm, gnome- 2 weeks ago
sig, mbarnes, orphan, rhughes,
rstrode, ssp
libstroke orphan 2 weeks ago
libusbauth-configparser orphan 3 weeks ago
libverto-jsonrpc orphan 2 weeks ago
libvirt-cim orphan 2 weeks ago
libvirt-java bkearney, orphan 2 weeks ago
lttv greenscientist, orphan 2 weeks ago
lua-fun orphan 2 weeks ago
maloc orphan 2 weeks ago
maven-scm mizdebsk, orphan 2 weeks ago
mediawiki-backtick-code orphan 3 weeks ago
mediawiki-semantic orphan 2 weeks ago
mediawiki-validator orphan 2 weeks ago
mesos orphan 3 weeks ago
mingw-cxxtest orphan 3 weeks ago
mingw-pcre orphan 3 weeks ago
mingw-sigar orphan 3 weeks ago
moarvm orphan 3 weeks ago
mod_annodex orphan 2 weeks ago
monosim orphan 3 weeks ago
msgpuck orphan 2 weeks ago
mupen64plus dreua, orphan 2 weeks ago
myman orphan 3 weeks ago
nailgun orphan 3 weeks ago
nodejs-supervisor orphan 2 weeks ago
nqp orphan 3 weeks ago
ogmtools orphan 3 weeks ago
openjpeg orphan, phracek, rdieter 2 weeks ago
pakiti andreamanzi, orphan 3 weeks ago
perl-Gnome2-Wnck orphan 3 weeks ago
perl-Goo-Canvas orphan 3 weeks ago
perl-Gtk2-Unique orphan 3 weeks ago
perl-MARC-Charset orphan 3 weeks ago
perl-MARC-XML orphan 3 weeks ago
perl-Mail-Procmail orphan 0 weeks ago
perl-POE-Component-Client-Ping orphan 3 weeks ago
perl-Parse-EDID epel-packagers-sig, jcpunk, 3 weeks ago
orphan
perl-TAP-Harness-Multiple orphan 3 weeks ago
perl-Test-POE-Server-TCP orphan, yaneti 3 weeks ago
php-pdepend-PHP-Depend cdamian, orphan, remi 3 weeks ago
php-phpmd-PHP-PMD cdamian, orphan, remi 3 weeks ago
php-phpunit-bytekit cdamian, orphan, remi 3 weeks ago
php-phpunit-phpcpd cdamian, orphan, remi 3 weeks ago
php-phpunit-phploc cdamian, orphan, remi 3 weeks ago
php-zipstream orphan 3 weeks ago
plug orphan 3 weeks ago
proxychains-ng epel-packagers-sig, orphan, 2 weeks ago
salimma
pydf cstratak, orphan 3 weeks ago
pynag orphan 2 weeks ago
pysvn barryascott, orphan, sgallagh 2 weeks ago
python-Pyped orphan 2 weeks ago
python-bintrees orphan 2 weeks ago
python-colour-runner orphan 2 weeks ago
python-cornice-sphinx infra-sig, orphan 5 weeks ago
python-cov-core abompard, orphan 3 weeks ago
python-cssmin orphan, qa-tools-sig 2 weeks ago
python-django-filter lbazan, orphan 3 weeks ago
python-django-tastypie cquad, mrunge, orphan, 3 weeks ago
stevetraylen
python-dockerpty lsm5, orphan, ttomecek 3 weeks ago
python-flask-restful kparal, orphan, qa-tools-sig, 3 weeks ago
ralph
python-formats orphan 2 weeks ago
python-frozen-flask echevemaster, orphan 3 weeks ago
python-gnocchiclient mrunge, openstack-sig, orphan 2 weeks ago
python-gzipstream orphan 0 weeks ago
python-importmagic orphan 3 weeks ago
python-jsonmodels orphan 2 weeks ago
python-lightblue orphan 3 weeks ago
python-okaara orphan 3 weeks ago
python-pmw orphan 2 weeks ago
python-posix_ipc orphan 2 weeks ago
python-pydispatcher orphan 2 weeks ago
python-pykeepass atim, limb, orphan 2 weeks ago
python-pynlpl orphan 2 weeks ago
python-pytest-beakerlib orphan 2 weeks ago
python-pytest-sanic orphan 2 weeks ago
python-restsh orphan 3 weeks ago
python-signalfd orphan 2 weeks ago
python-simpy orphan 2 weeks ago
python-spdx orphan 3 weeks ago
python-spdx-lookup orphan 3 weeks ago
python-tortilla orphan 2 weeks ago
python-upt-cpan orphan 3 weeks ago
python-upt-fedora orphan 3 weeks ago
python-upt-pypi orphan 3 weeks ago
python-upt-rubygems orphan 3 weeks ago
python-versiontools mrunge, orphan 3 weeks ago
python-virtualenv-api cstratak, orphan, python- 2 weeks ago
packagers-sig
python-websockify apevec, epel-packagers-sig, 2 weeks ago
lon, ndipanov, orphan
python-xtermcolor orphan 3 weeks ago
python-zabbix-api-erigones orphan 2 weeks ago
q orphan 3 weeks ago
qconf orphan 3 weeks ago
qxmpp orphan 3 weeks ago
rakudo orphan, ppisar, steve 3 weeks ago
rakudo-MIME-Base64 orphan 3 weeks ago
rakudo-Readline orphan 3 weeks ago
rakudo-URI orphan 3 weeks ago
rakudo-XML orphan 3 weeks ago
rakudo-zef orphan 3 weeks ago
rdfind orphan 3 weeks ago
refmac-dictionary orphan 2 weeks ago
resultsdb orphan, qa-tools-sig 2 weeks ago
resultsdb_frontend orphan, qa-tools-sig 2 weeks ago
rhythmbox-alternative-toolbar orphan 2 weeks ago
rshim orphan 3 weeks ago
ruby-ncurses orphan 2 weeks ago
rubygem-ZenTest orphan, tdawson 2 weeks ago
rubygem-abstract orphan 2 weeks ago
rubygem-activeresource orphan 2 weeks ago
rubygem-archive-tar-minitar orphan, tdawson 2 weeks ago
rubygem-cinch orphan 3 weeks ago
rubygem- orphan 3 weeks ago
declarative_authorization
rubygem-foreigner orphan 3 weeks ago
rubygem-lockfile orphan 2 weeks ago
rubygem-memcache-client orphan, tdawson 2 weeks ago
rubygem-more_core_extensions orphan 2 weeks ago
rubygem-openscap orphan 3 weeks ago
rubygem-plist orphan 3 weeks ago
rubygem-rubeyond orphan 3 weeks ago
rubygem-scruffy orphan 2 weeks ago
rubygem-session orphan 3 weeks ago
rubygem-sexp_processor orphan 2 weeks ago
rubygem-state_machine orphan 3 weeks ago
rubygem-syntax orphan, stahnma 2 weeks ago
rubygem-uuidtools orphan 2 weeks ago
rubygem-yard brandfbb, jaruga, orphan 2 weeks ago
rust-dbus-tokio orphan, rust-sig 3 weeks ago
rust-faccess orphan, rust-sig 0 weeks ago
rust-fbthrift_codegen_includer_ orphan, rust-sig 2 weeks ago
proc_macro
rust-fdlimit orphan, rust-sig 2 weeks ago
rust-iptables orphan, rust-sig 0 weeks ago
rust-lipsum orphan, rust-sig 2 weeks ago
rust-loggerv orphan, rust-sig 2 weeks ago
rust-lzw orphan, rust-sig 2 weeks ago
rust-macro-attr orphan, rust-sig 2 weeks ago
rust-mdl orphan, rust-sig 2 weeks ago
rust-mktemp orphan, rust-sig 2 weeks ago
rust-mnt orphan, rust-sig 2 weeks ago
rust-newtype_derive orphan, rust-sig 2 weeks ago
rust-oauth2 jbtrystram, orphan, rust-sig 1 weeks ago
rust-odds orphan, rust-sig 2 weeks ago
rust-osstrtools orphan, rust-sig 2 weeks ago
rust-parse_cfg orphan, rust-sig 2 weeks ago
rust-permutate orphan, rust-sig 2 weeks ago
rust-piper orphan, rust-sig 2 weeks ago
rust-proc-quote-impl orphan, rust-sig 2 weeks ago
rust-process_path orphan, rust-sig 2 weeks ago
rust-protoc-rust orphan, rust-sig 2 weeks ago
rust-quickersort orphan, rust-sig 2 weeks ago
rust-relay orphan, rust-sig 2 weeks ago
rust-rustdoc-stripper orphan, rust-sig 2 weeks ago
rust-rustfilt orphan, rust-sig 2 weeks ago
rust-safe-transmute orphan, rust-sig 2 weeks ago
rust-scoped-tls-hkt orphan, rust-sig 2 weeks ago
rust-serde-pickle orphan, rust-sig 2 weeks ago
rust-simple-error orphan, rust-sig 0 weeks ago
rust-sluice orphan, rust-sig 2 weeks ago
rust-spinning_top orphan, rust-sig 2 weeks ago
rust-spmc orphan, rust-sig 2 weeks ago
rust-string_cache_shared orphan, rust-sig 2 weeks ago
rust-strings orphan, rust-sig 2 weeks ago
rust-sudo_plugin orphan, rust-sig 2 weeks ago
rust-sxd-document orphan, rust-sig 2 weeks ago
rust-synom orphan, rust-sig 2 weeks ago
rust-tabwriter orphan, rust-sig 2 weeks ago
rust-take orphan, rust-sig 2 weeks ago
rust-unic-ucd-category orphan, rust-sig 2 weeks ago
rust-url_serde orphan, rust-sig 2 weeks ago
rust-utf8-ranges orphan, rust-sig 2 weeks ago
saga orphan 4 weeks ago
sassist orphan 3 weeks ago
schroedinger-cat-kde-theme jreznik, orphan 3 weeks ago
scim-anthy orphan 2 weeks ago
seahorse-nautilus gnome-sig, orphan, stefw 2 weeks ago
seren orphan 3 weeks ago
simple-mtpfs orphan 2 weeks ago
sipcalc orphan 3 weeks ago
spamprobe orphan 0 weeks ago
spawn-fcgi orphan 2 weeks ago
spherical-cow-kde-theme jreznik, orphan 3 weeks ago
sshrc orphan 2 weeks ago
sugar-flip chimosky, orphan 3 weeks ago
sugar-fototoon aperezbios, chimosky, orphan 3 weeks ago
sugar-fractionbounce chimosky, orphan 3 weeks ago
sugar-jukebox chimosky, orphan, pbrobinson 3 weeks ago
sugar-locosugar chimosky, orphan 3 weeks ago
sugar-nutrition chimosky, orphan 3 weeks ago
sugar-paint chimosky, orphan, pbrobinson 3 weeks ago
sugar-playgo chimosky, orphan, pbrobinson 3 weeks ago
sugar-portfolio chimosky, orphan 3 weeks ago
sugar-pukllanapac chimosky, orphan 3 weeks ago
sugar-recall chimosky, orphan 3 weeks ago
sugar-typing-turtle chimosky, orphan 3 weeks ago
sugar-words chimosky, orphan 3 weeks ago
superkb echevemaster, orphan 2 weeks ago
sweep orphan 3 weeks ago
switchboard-plug-tweaks orphan 5 weeks ago
system-storage-manager lczerner, orphan 3 weeks ago
tboot dcantrell, miaojun0823, 3 weeks ago
orphan, yunyings
tetrominos orphan 3 weeks ago
themonospot-base orphan 3 weeks ago
themonospot-console orphan 3 weeks ago
themonospot-gui-gtk orphan 3 weeks ago
themonospot-plugin-avi orphan 3 weeks ago
themonospot-plugin-mkv orphan 3 weeks ago
thunarx-python kevin, nonamedotc, orphan 3 weeks ago
tito frostyx, maxamillion, orphan 3 weeks ago
tkcvs lkundrak, orphan 3 weeks ago
tnt orphan 2 weeks ago
torrent-file-editor orphan 3 weeks ago
tpp orphan 3 weeks ago
tss2 orphan, snits 3 weeks ago
upt orphan 3 weeks ago
usbauth orphan 3 weeks ago
usbauth-notifier orphan 3 weeks ago
vcglib orphan 2 weeks ago
vicious orphan 2 weeks ago
vim-nerdtree orphan 3 weeks ago
whipper-plugin-eaclogger orphan 2 weeks ago
wipe orphan 2 weeks ago
wmMatrix orphan 2 weeks ago
wmclock orphan 2 weeks ago
wmnd orphan 2 weeks ago
wmpager orphan 2 weeks ago
wmsystemtray orphan 2 weeks ago
wordpress-plugin-defaults orphan 3 weeks ago
workspace orphan 3 weeks ago
wv lkundrak, orphan 2 weeks ago
xaos orphan 3 weeks ago
xjparse orphan 3 weeks ago
xmltool orphan 2 weeks ago
yourls orphan 2 weeks ago
The following packages require above mentioned packages:
Report too long, see the full version at
https://churchyard.fedorapeople.org/orphans-2022-12-19.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):
abompard: python-cov-core
ajax: liboil
alexl: gconf-editor, liboil, libgnomeui, gtkhtml3, libbonobo, libbonoboui, libgnome
amdunn: maven-scm
andreamanzi: pakiti, libmacaroons
andymenderunix: openjpeg, vcglib
antiaircraft: libbonoboui, libbonobo
aperezbios: sugar-fototoon
apevec: python-websockify
astro-sig: libbonoboui, libgnome, libgnomeui
athoscr: golang-github-hanwen-fuse
atim: vim-nerdtree, python-pykeepass, golang-github-sqshq-sampler, alure
averi: perl-Test-POE-Server-TCP
aviso: libgnome
barryascott: pysvn
besser82: rubygem-yard
bkearney: libvirt-java
bowlofeggs: ejabberd
brandfbb: rubygem-yard
bruno: libbonoboui, libgnome, libgnomeui
buc: libbonoboui, libgnome, libbonobo, libgnomeui
caolanm: gconf-editor, liboil, libgnomeui, gtkhtml3, libbonobo, libbonoboui,
libgnome
cdamian: php-phpunit-bytekit, php-phpmd-PHP-PMD, php-pdepend-PHP-Depend,
php-phpunit-phploc, php-phpunit-phpcpd
cdorney: maven-scm
cfu: maven-scm
cheese: libbonoboui, libgnomeui
cheeselee: fcitx-table-extra, fcitx-fbterm, fcitx-table-other, fcitx-m17n,
fcitx-unikey, fcitx-hangul, kcm-fcitx, fcitx-configtool, fcitx-cloudpinyin,
fcitx-ui-light, fcitx-chewing, fcitx, fcitx-sunpinyin
chimosky: sugar-nutrition, abiword, sugar-jukebox, sugar-flip, sugar-playgo,
sugar-paint, sugar-portfolio, sugar-words, sugar-typing-turtle,
sugar-pukllanapac, sugar-fototoon, sugar-locosugar, sugar-fractionbounce,
sugar-recall, wv
chkr: anki
cicku: thunarx-python, libgnomeui, gtkhtml3, pysvn, libbonobo, fcitx,
libbonoboui, libgnome
company: dmz-cursor-themes
copperi: golang-github-hanwen-fuse, golang-github-mitchellh-cli
copr-sig: python-virtualenv-api, python-flask-restful, tito
cquad: maven-scm, python-django-tastypie
cstratak: pydf, python-virtualenv-api
cwickert: libbonoboui, libgnome, libgnomeui
dcantrell: tboot
dcavalca: python-websockify, rubygem-yard, golang-github-mitchellh-cli,
golang-github-spaolacci-murmur3, libstroke, golang-github-hanwen-fuse
dchen: maven-scm
deamn: maven-scm
devrim: python-cssmin
didiksupriadi41: jcodings, maven-scm
dmsimard: python-django-filter
dnglaze: wv
dreua: mupen64plus
dustymabe: kompose
ebaron: maven-scm
echevemaster: python-pydispatcher, python-frozen-flask, libbonobo, libbonoboui,
superkb
eclipse-sig: maven-scm
eclipseo: maven-scm, golang-github-mitchellh-cli,
golang-github-google-containerregistry, golang-github-spaolacci-murmur3,
golang-github-hanwen-fuse, golang-github-pkg-browser
ellert: jargs, libmacaroons
epel-packagers-sig: python-websockify, golang-github-hanwen-fuse,
proxychains-ng, perl-Parse-EDID
fab: libbonoboui, libgnome, libgnomeui
filbranden: rubygem-yard
filiperosset: libbonoboui, libgnome, libgnomeui, wv
frostyx: python-virtualenv-api, python-flask-restful, tito
fujiwara: libbonoboui, libgnomeui
gil: jgrapht
gilboa: alure
gnome-sig: bluecurve-classic-metacity-theme, gconf-editor, liboil,
bluecurve-xmms-skin, gnome-search-tool, libgnomeui, bluecurve-gtk-themes,
bluecurve-gnome-theme, libbonobo, bluecurve-metacity-theme, seahorse-nautilus,
bluecurve-kde-theme, libbonoboui, libgnome, bluecurve-icon-theme
go-sig: kompose, maven-scm, golang-github-gocomply-scap,
golang-github-lpabon-godbc, golang-github-mitchellh-cli,
golang-github-google-containerregistry, golang-github-spaolacci-murmur3,
golang-github-hanwen-fuse, golang-github-pkg-browser,
golang-github-justinas-alice, golie, golang-github-sqshq-sampler
godas: gdeploy
gordonmessmer: python-virtualenv-api
gotmax23: golang-github-hanwen-fuse, golang-github-mitchellh-cli
greenscientist: lttv
greghellings: gtkhtml3, rubygem-yard
hannes: libbonoboui, libgnomeui
herrold: abiword, wv
huzaifas: abiword, wv
ignatenkobrain: python-django-filter
ilgrad: rubygem-yard
infra-sig: golang-github-hanwen-fuse, python-cornice-sphinx,
ansible-collection-google-cloud, golang-github-mitchellh-cli
iztokf: python-cssmin
jackorp: rubygem-yard
jamatos: wv
jaruga: rubygem-yard
jbtrystram: rust-oauth2
jchaloup: golang-github-mitchellh-cli, golang-github-hanwen-fuse
jcline: ejabberd
jcpunk: perl-Parse-EDID
jerboaa: maven-scm
jgrulich: amor, mingw-pcre, highcontrast-qt
jjames: maven-scm
jjelen: maven-scm
jkastner: wv
jmagne: maven-scm
jonathanspw: python-websockify, libmacaroons, perl-Parse-EDID
jonkni: libmacaroons
jplesnik: libmacaroons, libgnomeui, libbonobo, perl-Test-POE-Server-TCP,
libbonoboui, libgnome
jreznik: spherical-cow-kde-theme, schroedinger-cat-kde-theme, heisenbug-kde-theme
jussilehtola: CheMPS2
jvanek: maven-scm, CFR
kde-sig: qconf, amor, wv
kengert: openjpeg
kevin: python-virtualenv-api, thunarx-python
kkeithle: glusterfs-selinux
kkofler: bluecurve-kde-theme
kparal: python-flask-restful
kushal: rubygem-yard
laxathom: libbonoboui, libgnome, libbonobo, libgnomeui
lbazan: libbonoboui, python-django-filter, libbonobo
lczerner: system-storage-manager
lfield: libmacaroons
limb: thunarx-python, libgnomeui, pysvn, libbonobo, libbonoboui, libgnome,
python-pykeepass
lkf: wv
lkundrak: rubygem-yard, tkcvs, wv, erlang-epgsql, rubygem-archive-tar-minitar
lnykryn: biosdevname
lon: python-websockify
lsm5: python-dockerpty, golang-github-hanwen-fuse, golang-github-mitchellh-cli
lyarwood: python-websockify
martinkg: perl-Goo-Canvas, alure
mattia: golang-github-mitchellh-cli, libgnomeui, golang-github-hanwen-fuse,
libbonoboui, libgnome
maxamillion: rubygem-yard, tito
mbarnes: gconf-editor, liboil, libgnomeui, gtkhtml3, libbonobo, libbonoboui,
libgnome
mcermak: libstroke
mcrha: libgnome
melmorabity: dmz-cursor-themes
mharmsen: maven-scm
mhayden: maven-scm
mhjacks: moarvm, rakudo, nqp
miaojun0823: tboot
mikep: golang-github-hanwen-fuse
mipatras: libmacaroons
mizdebsk: maven-scm
mkoncek: maven-scm
mrnuke: wv
mrunge: python-versiontools, python-django-tastypie, python-gnocchiclient
mschwendt: libgnome
msekleta: biosdevname
msuchy: python-flask-restful
mtasaka: rubygem-yard, libgnomeui, libbonobo, libbonoboui, libgnome
ndipanov: python-websockify
neuro-sig: rubygem-yard
ngompa: python-django-filter
nonamedotc: thunarx-python
olea: libbonoboui, libbonobo
openstack-sig: python-gnocchiclient
oturpe: rubygem-yard
pbrobinson: abiword, sugar-jukebox, sugar-playgo, sugar-paint, wv
pcpa: maven-scm
peter: libstroke
phracek: openjpeg
ppisar: moarvm, libmacaroons, libgnomeui, rakudo, libbonobo,
perl-Test-POE-Server-TCP, libbonoboui, libgnome, nqp
praiskup: python-virtualenv-api, python-flask-restful, tito
pwalter: pysvn, thunarx-python
pwu: fcitx
python-packagers-sig: python-virtualenv-api, maven-scm
qa-tools-sig: python-cssmin, python-flask-restful, resultsdb_frontend, resultsdb
qulogic: golang-github-hanwen-fuse, golang-github-mitchellh-cli
r-maint-sig: libmacaroons
ralph: python-flask-restful
rathann: maloc
rdieter: bluecurve-kde-theme, amor, openjpeg, wv
remi: php-phpunit-bytekit, php-phpmd-PHP-PMD, php-pdepend-PHP-Depend,
php-phpunit-phploc, php-phpunit-phpcpd
rgrunber: maven-scm
rhughes: gconf-editor, liboil, libgnomeui, gtkhtml3, libbonobo, libbonoboui,
libgnome
rjones: mingw-pcre
rocha: libmacaroons
rombobeorn: libbonoboui, libgnome, libbonobo, libgnomeui
rrankin: wv
rstrode: bluecurve-classic-metacity-theme, gconf-editor, liboil,
bluecurve-xmms-skin, libgnomeui, bluecurve-gtk-themes, bluecurve-gnome-theme,
gtkhtml3, libbonobo, bluecurve-metacity-theme, bluecurve-kde-theme,
libbonoboui, libgnome, bluecurve-icon-theme
ruby-packagers-sig: rubygem-yard
rust-sig: rust-sxd-document, rust-mnt, rust-rustdoc-stripper, rust-dbus-tokio,
rust-newtype_derive, rust-rustfilt, rust-unic-ucd-category, rust-sluice,
rust-spmc, rust-macro-attr, rust-string_cache_shared, rust-loggerv, rust-piper,
rust-proc-quote-impl, rust-mdl, rust-scoped-tls-hkt, rust-protoc-rust,
rust-tabwriter, rust-serde-pickle, rust-quickersort, rust-parse_cfg,
rust-lipsum, rust-lzw, rust-odds, rust-fdlimit, rust-process_path, rust-relay,
rust-safe-transmute, rust-synom, rust-sudo_plugin, rust-permutate,
rust-spinning_top, rust-utf8-ranges, rust-faccess, rust-strings,
rust-osstrtools, rust-iptables, rust-simple-error, rust-oauth2, rust-take,
rust-fbthrift_codegen_includer_proc_macro, rust-url_serde, rust-mktemp
sagitter: openjpeg, python-pmw, maven-scm, maloc
sailer: mingw-pcre
salimma: rubygem-yard, proxychains-ng, libgnomeui, libstroke, libbonoboui, libgnome
schlupov: python-flask-restful
sergiomb: maven-scm, golang-github-mitchellh-cli, golang-github-hanwen-fuse,
python-pmw, maloc
sgallagh: pysvn
sharkcz: libbonoboui, libgnome, libbonobo, libgnomeui
shwetha: glusterfs-selinux
simonm: libmacaroons
smani: mingw-pcre
snits: tss2
spot: libbonoboui, libbonobo, alure
ssp: gconf-editor, liboil, libgnomeui, gtkhtml3, libbonobo, libbonoboui, libgnome
stahnma: rubygem-syntax, rubygem-yard
stefw: seahorse-nautilus
steve: gl-117, moarvm, libgnomeui, libbonoboui, rakudo, libgnome, nqp
stevetraylen: python-django-tastypie
survient: holland
tartare: libbonoboui, libgnome, libgnomeui
tdawson: rubygem-yard, rubygem-ZenTest, rubygem-archive-tar-minitar,
rubygem-memcache-client
than: bluecurve-kde-theme, amor
thm: libbonoboui, libbonobo
thofmann: bibtex2html
thunderbirdtr: qconf
tpokorra: libbonoboui, libgnome, libbonobo, libgnomeui
ttomecek: python-dockerpty
ueno: fcitx
valtri: rubygem-yard
vokac: libmacaroons
vondruch: rubygem-yard
vpavlin: biosdevname
xavierb: ejabberd
yaneti: perl-Test-POE-Server-TCP
yanqiyu: fcitx-table-extra, fcitx-fbterm, fcitx-table-other, fcitx-m17n,
fcitx-unikey, fcitx-hangul, kcm-fcitx, golang-github-mitchellh-cli,
fcitx-configtool, fcitx-cloudpinyin, fcitx-ui-light, golang-github-hanwen-fuse,
fcitx-chewing, fcitx, fcitx-sunpinyin
yunyings: tboot
--
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
Report finished at 2022-12-19 15:17:23 UTC
_______________________________________________
devel-announce mailing list -- devel-announce@lists.fedoraproject.org
To unsubscribe send an email to devel-announce-leave@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-announce@lists.fedoraproject.org
Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Subscribe to:
Posts (Atom)