F35 Change: Rebase firewalld to upstream v1.0.0 (System-Wide Change proposal)
by Ben Cotton
https://fedoraproject.org/wiki/Changes/firewalld-1.0.0
== Summary ==
Firewalld upstream is about to release v1.0.0. As indicated by the
major version bump this includes behavioral changes.
== Owner ==
* Name: [[User:erig0| Eric Garver]]
* Email: egarver(a)redhat.com
== Detailed Description ==
Firewalld v1.0.0 includes breaking changes meant to improve the
overall health of the project. The majority of the changes are
centered around improving and strengthening the zone concept. All
breaking changes are detailed in depth in the
[https://firewalld.org/2021/06/the-upcoming-1-0-0 upstream blog].
Major changes:
* Reduced dependencies
* Intra-zone forwarding by default
* NAT rules moved to inet family (reduced rule set)
* Default target is now similar to reject
* ICMP blocks and block inversion only apply to input, not forward
* tftp-client service has been removed
* iptables backend is deprecated
* Direct interface is deprecated
* CleanupModulesOnExit defaults to no (kernel modules not unloaded)
== Benefit to Fedora ==
The major benefit to Fedora is more predictability in the stock
firewall. In particular, "Default target is now similar to reject"
addresses many subtle issues encountered by users. "NAT rules moved to
inet family" also significantly reduces the rule set size for users of
`ipset`s.
== Scope ==
* Proposal owners: Changes are isolated to firewalld, but given
firewalld is core a System Wide Change is being filed.
* Other developers: None. Isolated change.
* 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 ==
* Most configurations will migrate. No intervention required.
** Exceptions
*** configurations that utilize `tftp-client` service will have
firewalld start in `failed` state because the service has been
removed. As noted in the upstream blog this service has ''never''
worked properly.
* Zones that users have not modified will now have intra-zone
forwarding enabled.
** for this to occur the user must ''not'' have added an interface,
service, port, etc. to the zone
** minimal concern because this also means the zone was not in use,
the exception being an unmodified default zone, e.g.
`FedoraWorkstation`
== How To Test ==
Testing for this rebase should revolve around integrations.
* libvirt
** verify VMs still have network access
* podman
** verify containers still have network access
** verify forwarding ports via podman still works
* NetworkManager
** verify connection sharing still works
== User Experience ==
N/A
== Dependencies ==
firewalld has yet to release v1.0.0. It is expected in early July.
== Contingency Plan ==
* Contingency mechanism: revert package to v0.9.z (what f34 uses)
* Contingency deadline: July 27, 2021
* Blocks release? No
== Documentation ==
https://firewalld.org/2021/06/the-upcoming-1-0-0
== Release Notes ==
firewalld has been rebased to v1.0.0. This includes some breaking
changes that may affect users.
Major changes:
* Reduced dependencies
* Intra-zone forwarding by default
* NAT rules moved to inet family (reduced rule set)
* Default target is now similar to reject
* ICMP blocks and block inversion only apply to input, not forward
* tftp-client service has been removed
* iptables backend is deprecated
* Direct interface is deprecated
* CleanupModulesOnExit defaults to no (kernel modules not unloaded)
Full details on the upstream blog:
https://firewalld.org/2021/06/the-upcoming-1-0-0
--
Ben Cotton
He / Him / His
Fedora Program Manager
Red Hat
TZ=America/Indiana/Indianapolis
2 years, 10 months
F35 Change: LLVM 13 (Self-Contained Change proposal)
by Ben Cotton
https://fedoraproject.org/wiki/Changes/LLVM-13
== Summary ==
Update all llvm sub-projects in Fedora to version 13.
== Owner ==
* Name: [[User:tstellar| Tom Stellard]]
* Email: <tstellar(a)redhat.com>
== Detailed Description ==
All llvm sub-projects in Fedora will be updated to version 13, and
there will be a soname version change for the llvm libraries.
Compatibility packages clang12 and llvm12 will be added to ensure that
packages that currently depend on clang and llvm version 12 libraries
will continue to work.
== Benefit to Fedora ==
New features and bug fixes provided by the latest version of LLVM.
== Scope ==
* Proposal owners:
** Review existing llvm and clang compatibility packages and orphan
any packages that are no longer used.
** Request a side-tag.
** Build llvm12 and clang12 into the side-tag.
** When the upstream LLVM project releases version 12.0.0-rc1 (Late
July 2021), package this and build it into the side tag.
** Merge side-tag into rawhide prior to the f35 branch date.
** Continue packaging newer release candidates into rawhide and f35
until the final release is complete (Late September 2021)
* Other developers:
** Maintainers of packages that depend on clang-libs or llvm-libs will
need to update their spec files to depend on the clang12 and llvm12
compatibility packages if they want to rebuild their package and it
does not work with LLVM 13 yet. The key point here is that spec file
changes are only needed if a package is going to be rebuilt after LLVM
13 is added to Fedora. The compatibility packages will ensure that
already built packages continue to work.
* Release engineering: [https://pagure.io/releng/issues/10179]
* 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 ==
This change should not impact upgradeability.
== How To Test ==
The CI tests for the llvm sub-packages in Fedora will be used to catch
regressions that might be potentially introduced by the update to LLVM
13.
== User Experience ==
Users will benefit from new features and bug-fixes in the latest
version of LLVM.
== Dependencies ==
This change can be made without updating any other packages. However,
as mention before, packages that need to use LLVM 12 will need to
update their spec file on their first rebuild after this change.
== Contingency Plan ==
* Contingency mechanism: (What to do? Who will do it?): If there are
major problems with LLVM 13, the compatibility package provide a way
for other packages to continue using LLVM 12.
* Contingency deadline: Final Freeze
* Blocks release? No
== Documentation ==
Release notes will be added for this change.
== Release Notes ==
LLVM sub-projects in Fedora have been updated to version 13:
* llvm
* clang
* lld
* lldb
* compiler-rt
* libomp
* llvm-test-suite
* libcxx
* libcxxabi
* python-lit
* flang
* mlir
* polly
* libclc
--
Ben Cotton
He / Him / His
Fedora Program Manager
Red Hat
TZ=America/Indiana/Indianapolis
2 years, 10 months
F35 Change: Optimal LUKS Encryption Sector Size (Self-Contained
Change proposal)
by Ben Cotton
https://fedoraproject.org/wiki/Changes/LUKSEncryptionSectorSize
== Summary ==
Autodetect optimal encryption sector size during Fedora installation
with LUKS/dm-crypt encryption. On devices with 4k (physical) sector
size, this will make sure we use 4096 sector size which is optimal for
these devices.
== Owner ==
* Name: [[User:okozina|Ondrej Kozina]], [[User:vtrefny|Vojtech Trefny]]
* Email: okozina AT redhat.com, vtrefny AT redhat.com
== Detailed Description ==
Anaconda installer (or to be more precise, the libraries Anaconda uses
for storage configuration) currently sets sector size for LUKS devices
to 512 regardless the of actual physical sector size of the underlying
disk device. The latest cryptsetup release added an option to let
cryptsetup automatically detect the optimal sector size based on the
(physical) sector size of the backing device. By using this new option
we can make sure that Anaconda uses the optimal sector size for newly
created LUKS devices during installation. This means we will use
sector size of 4096 for devices with 4k physical sector size
increasing IO performance with these devices.
== Scope ==
* Proposal owners: Changes for both cryptsetup and libblockdev
(low-level storage library used by Anaconda) are already merged
([https://gitlab.com/cryptsetup/cryptsetup/-/merge_requests/135
cryptsetup]) or submitted
([https://github.com/storaged-project/libblockdev/pull/638
libblockdev]) upstream. We only need to package new versions of these
two projects for Fedora 35. No changes will be needed in Anaconda.
* Other developers: No work from other developers is needed.
* 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 ==
Upgraded systems will not be affected by this change, this affects
only new LUKS containers created during Fedora installation.
Support for specifying custom sector size is one of the features
available in LUKS2 ([[Changes/SwitchCryptsetupDefaultToLUKS2|default
since Fedora 30]]), no additional changes or special support is needed
when working with LUKS2 devices with sector sizes different than 512.
== How To Test ==
Disk with 4k physical sectors is required for testing this change. You
can check block size of your drive using `blockdev` from `util-linux`
package:
# blockdev --getpbsz /dev/nvme0n1
4096
This can be also tested in a virtual machine. You can configure any
disk to appear as 4k block size disk in libvirt by adding the
following option to the disk XML specification:
<blockio logical_block_size="4096" physical_block_size="4096"/>
Install Fedora with disk encryption enabled. Using automatic partition
with '''Encrypt my data''' enabled is enough for testing.
In the installed system use `cryptsetup luksDump /dev/<device>` to
check that correct sector size was selected for your device (4096 for
disks with 4096 physical sector size):
# cryptsetup luksDump /dev/nvme0n1p1
LUKS header information
Version: 2
...
Data segments:
0: crypt
offset: 16777216 [bytes]
length: (whole device)
cipher: aes-xts-plain64
'''sector: 4096 [bytes]'''
== User Experience ==
Fedora users shouldn't notice the change, other than a small IO
performance boost (IO testing on a 4k sectors NVMe shows around 2-3 %
gain when using 4k sectors instead of 512 sectors).
== Dependencies ==
None.
== Contingency Plan ==
* Contingency mechanism: Keep existing behaviour (512 sector size for
all devices)
* Contingency deadline: Beta Freeze
* Blocks release? No
--
Ben Cotton
He / Him / His
Fedora Program Manager
Red Hat
TZ=America/Indiana/Indianapolis
2 years, 10 months
F35 Change: libmemcached-awesome (Self-Contained Change proposal)
by Ben Cotton
https://fedoraproject.org/wiki/Changes/libmemcached-awesome
== Summary ==
Switch from libmemcached to libmemcached-awesome
== Owner ==
* Name: [[User:Remi| Remi Collet]]
* Email: remi at fedoraproject dot org
== Detailed Description ==
libmemcache 1.0.18 was released in February 2014, so hasn't received
an update for 7 years.
libmemcache-awesome is a fork providing same libraries, tools with
API/ABI compatibility.
== Benefit to Fedora ==
Rely on a maintained project.
== Scope ==
* Proposal owners: Check Koschei status. Test with latest version to
ensure compatibility. Work with upstream on bug fixing. Needed mass
rebuild (C extensions) done by change owner.
* Other developers: N/A (not a System Wide Change)
* Release engineering:
* Policies and guidelines: N/A (not a System Wide Change)
* Trademark approval: N/A (not needed for this Change)
== Upgrade/compatibility impact ==
N/A (not a System Wide Change)
== How To Test ==
* install and play with your application
== User Experience ==
Developers and system administrators will have the great benefit or
running a maintained library.
== Dependencies ==
All php-* packages (and some *-php)
== Contingency Plan ==
* Contingency mechanism: Drop not compatible packages.
* Contingency deadline: N/A (not a System Wide Change)
* Blocks release? N/A (not a System Wide Change)
== Documentation ==
* [https://awesomized.github.io/libmemcached/ Upstream documentation]
--
Ben Cotton
He / Him / His
Fedora Program Manager
Red Hat
TZ=America/Indiana/Indianapolis
2 years, 10 months
[HEADS UP] Planned Sphinx update to 4.x - many packages fail to build
by Karolina Surma
Hello,
As you may already know [0], we plan to upgrade the Python documentation
framework Sphinx to a new major version - currently it's 4.0.2.
The update will take place on Monday, *June 28th*.
Packages that stopped building or running with the newest Sphinx stack
were identified during the test build in the Copr repository [1].
There are still a lot of packages which fail to build.
Please, if you haven't already, check the build logs and work with the
upstream towards fixing the failures.
Feel free to use the Copr repository to test your package there.
For details regarding the Sphinx update, see the associated Fedora
Change [0].
Having questions or in need of help? Don't hesitate to contact me.
You can reply to this thread or find ksurma on #fedora-python IRC
channel (libera.chat).
Best regards,
Karolina Surma
[0] https://fedoraproject.org/wiki/Changes/Sphinx4
<https://fedoraproject.org/wiki/Changes/Sphinx4>
[1] https://copr.fedorainfracloud.org/coprs/ksurma/pygments-2.9.0/
<https://copr.fedorainfracloud.org/coprs/ksurma/pygments-2.9.0/>(don't
be confused by the
name)<https://copr.fedorainfracloud.org/coprs/ksurma/pygments-2.9.0/>
Maintainers by package:
Mayavi chedi orion
ansible kevin toshio wzzrd
ara dmsimard
arbor ankursinha
borgbackup fschwarz
botan thm
condor bbockelm bcotton eerlands matt matyas stevetraylen
tstclair ttheisen valtri
copr-keygen clime dturecek frostyx msuchy praiskup
gcc aoliva jakub law mpolacek
ghc petersen
kea landgraf thozza zdohnal
libgpuarray jjames
php-opencloud-openstack lcts
python-BTrees jjames
python-anyio carlwgeorge fab
python-djvulibre terrycloth
python-f5-sdk xavierb
python-glue lgs
python-h2 eclipseo
python-libpysal qulogic
python-listparser atim limb
python-novaclient apevec jruzicka
python-openstackclient apevec
python-patsy sergiopr
python-persistent jjames
python-pkginfo thrnciar
python-pycryptodomex melmorabity
python-pynetdicom alciregi
python-pyswarms iztokf
python-rjsmin kwizart mrunge
python-ruffus qulogic
python-sphinx-tabs hobbes1069
python-sphinxcontrib-asyncio fab
python-sphinxcontrib-phpdomain fab
python-sphinxcontrib-trio jcaratzas thm
python-texext jjames
python-txtorcon decathorpe
python-whoosh rkuska sgallagh
python-zarr qulogic
rebase-helper nforro phracek
tortoisehg kiilerix nbecker
waiverdb gnaponie lholecek lucarval mprahl ralph vmaljulin
xeus qulogic
xtl qulogic
Packages by maintainer:
alciregi python-pynetdicom
ankursinha arbor
aoliva gcc
apevec python-novaclient python-openstackclient
atim python-listparser
bbockelm condor
bcotton condor
carlwgeorge python-anyio
chedi Mayavi
clime copr-keygen
decathorpe python-txtorcon
dmsimard ara
dturecek copr-keygen
eclipseo python-h2
eerlands condor
fab python-anyio python-sphinxcontrib-asyncio
python-sphinxcontrib-phpdomain
frostyx copr-keygen
fschwarz borgbackup
gnaponie waiverdb
hobbes1069 python-sphinx-tabs
iztokf python-pyswarms
jakub gcc
jcaratzas python-sphinxcontrib-trio
jjames libgpuarray python-BTrees python-persistent python-texext
jruzicka python-novaclient
kevin ansible
kiilerix tortoisehg
kwizart python-rjsmin
landgraf kea
law gcc
lcts php-opencloud-openstack
lgs python-glue
lholecek waiverdb
limb python-listparser
lucarval waiverdb
matt condor
matyas condor
melmorabity python-pycryptodomex
mpolacek gcc
mprahl waiverdb
mrunge python-rjsmin
msuchy copr-keygen
nbecker tortoisehg
nforro rebase-helper
orion Mayavi
petersen ghc
phracek rebase-helper
praiskup copr-keygen
qulogic python-libpysal python-ruffus python-zarr xeus xtl
ralph waiverdb
rkuska python-whoosh
sergiopr python-patsy
sgallagh python-whoosh
stevetraylen condor
terrycloth python-djvulibre
thm botan python-sphinxcontrib-trio
thozza kea
thrnciar python-pkginfo
toshio ansible
tstclair condor
ttheisen condor
valtri condor
vmaljulin waiverdb
wzzrd ansible
xavierb python-f5-sdk
zdohnal kea
2 years, 11 months
F35 Change: MinGW environment and toolchain update (System-Wide
Change proposal)
by Ben Cotton
https://fedoraproject.org/wiki/Changes/F35MingwEnvToolchainUpdate
== Summary ==
Update the MinGW base environment and toolchain to the latest upstream
stable releases.
== Owner ==
* Name: [[User:smani|Sandro Mani]]
* Email: manisandro(a)gmail.com
== Detailed Description ==
The following packages will be updated
* mingw-gcc to version 11.x
* mingw-w64-tools to version 9.x
* mingw-winpthreads to version 9.x
* mingw-crt to version 9.x
* mingw-headers to version 9.x
== Benefit to Fedora ==
Ship the latest available MinGW environment and GNU toolchain.
== Scope ==
* Proposal owners:
The above mentioned packages will be updated. Build failures following
the mass rebuild will be inspected.
* Other developers:
Help with build failures may be requested.
* Release engineering: Impact check [https://pagure.io/releng/issue/10174]
* Release engineering: Mass rebuild requested
* Policies and guidelines: No policies need to be changed
== Upgrade/compatibility impact ==
No impact
== How To Test ==
Update the system once the updated packages land, look out for new
build failures etc.
== User Experience ==
The features of the newest MinGW environment and GNU Toolchain will be
available to the users.
== Dependencies ==
None
== Contingency Plan ==
* Contingency mechanism: Revert to older versions of environment /
toolchain, mass rebuild mingw packages again
* Contingency deadline: Before release
* Blocks release? Yes
* Blocks product? No
== Release Notes ==
Fedora 35 comes with the mingw-w64-9 environment and mingw-gcc-11.
--
Ben Cotton
He / Him / His
Fedora Program Manager
Red Hat
TZ=America/Indiana/Indianapolis
2 years, 11 months
package maintainer email aliases, now with more epel
by Kevin Fenzi
Greetings.
As a reminder, if you need to reach package maintainers for a specific
package in private, you can email:
packagename-maintainers(a)fedoraproject.org
You can also now mail:
packagename-maintainers-fedora(a)fedoraproject.org to just reach the
fedora branch(es) maintainer(s).
or
packagename-maintainers-epel(a)fedoraproject.org to just reach the epel
branch(es) maintainer(s).
Note that these aliases are for coordination or other items that cannot
be a bugzilla bugs. In general all bug or enhancement requests should be
in bugzilla.
kevin
2 years, 11 months
F35 Change: Libvirt Modular Daemons (Self-Contained Change proposal)
by Ben Cotton
https://fedoraproject.org/wiki/Changes/LibvirtModularDaemons
== Summary ==
Historically all libvirt functionality was provided in the monolithic
libvirtd daemon. Upstream has developed a new modular architecture for
libvirt where each driver is run in its own daemon. Primarily this
provides better robustness as a flaw in a secondary daemon will not
affect the QEMU daemon and vica-versa. It should also have slightly
lower host startup overhead, because only the installed hypervisor
daemon(s) will need to be fully started on boot, the other daemons can
be socket activated on demand.
== Owner ==
* Name: [[User:berrange| Daniel Berrange]]
* Email: berrange(a)redhat.com
== Detailed Description ==
Historically all libvirt functionality was provided in the monolithic
libvirtd daemon. Upstream has developed a new modular architecture for
libvirt where each driver is run in its own daemon. Daemons include
virtqemud, virtlxcd, virtnetworkd, virtnodedevd, virtsecretd, etc, one
for each libvirt stateful hypervisor driver and secondary support
driver. The new daemons listen on new socket paths and only support
UNIX sockets. For remote off-host TCP/TLS access and for backwards
compatibility with clients expecting the libvirtd UNIX socket paths, a
virtproxyd daemon is also provided. The latter accepts RPC requests
and forwards to the appropriate modular daemon. Further information
is available in the [https://libvirt.org/daemons.html Upstream
documentation]
The work will primarily involve changes in the systemd presets related
to libvirt. Currently the Fedora systemd presets enable
libvirtd.service. While libvirtd does support socket activation this
is not used during host startup, because the libvirtd daemon needs to
be fully started in order to auto-start QEMU guests that may be
configured. The current libvirtd.service uses a timeout, however, that
causes libvirtd to shutdown after 2 minutes if no VM is running.
This requirement for fully starting the service on boot still exists
in the modular daemons, however, we do not need to start all the
modular daemons on boot. It is sufficient to enable just the service
units for the hypervisor drivers QEMU, Xen and LXC. These will again
this will use a 2 minute timeout so they shut down if no
guest/container are running. Further, a default install of libvirt in
Fedora is only expected to provide the QEMU libvirt daemon.
The remaining modular daemons for libvirt non-hypervisor drivers can
exclusively rely on socket activation, because while they do provide
autostart capabilities for non-VM resources, these resources are only
needed when a VM actually starts.
The current '/usr/lib/systemd/system-preset/90-default.preset' config has
libvirtd.service
and due to dependencies, this implies libvirtd.socket,
libvirtd-ro.socket, libvirtd-admin.socket, virtlogd.socket,
virtlockd.socket also get enabled by default
The intended change is to remove libvirtd.service and instead add
virtqemud.service
virtxend.service
virtlxcd.service
virtinterfaced.socket
virtnetworkd.socket
virtnodedevd.socket
virtnwfilterd.socket
virtproxyd.socket
virtsecretd.socket
virtstoraged.socket
== Benefit to Fedora ==
The primary benefit of the modular daemons is robustness of the
management stack. There are times when libvirt code has exhibited
hangs or crashes. By having one daemon per libvirt driver, the impact
of these bugs is limited. The most important benefit of this is that a
bug in the node device / storage daemons will not impact management of
any running QEMU VMs.
The secondary benefit of the modular daemons is improved host startup
overhead. When the libvirtd daemon starts, all drivers are initialized
and this can take a significant amount of CPU time. This is
particularly true for the node device driver as it extracts
information about all host hardware.
The third potential future benefit is that it enables development of
more useful SELinux policy. The current policy for libvirtd is no
better than unconfined due to the broad range of features that must be
allowed. At least some of the modular daemons can potentially have
useful SELinux policy written. Note there is no active work on this
aspect.
== Scope ==
* Proposal owners:
Rebuild libvirt to prefer connecting to modular daemons by default
Submit a patch updating 90-defaults.preset in the fedora-release
package to enable modular daemons by default
* Other developers:
Review the proposal for fedora-release preset change
* Release engineering: N/A
* Policies and guidelines: N/A
* Trademark approval: N/A
* Alignment with Objectives: N/A
== Upgrade/compatibility impact ==
Existing Fedora installs using libvirtd will be unaffected by the
change in presets and will continue to use monolithic libvirtd. To
opt-in to using the new modular daemons follow instructions at
https://libvirt.org/daemons.html#switching-to-modular-daemons
New Fedora installs will get modular daemons instead of libvirtd. This
is intended to be functionally transparent to applications using
libvirt APIs.
This may have an impact on automation tools such as ansible / puppet
which have been written to manage libvirtd. These will need adapting
to manage the new modular daemons, or the host can be re-configured to
use libvirtd again in the short term by applying the inverse of the
logic at https://libvirt.org/daemons.html#switching-to-modular-daemons
Administrators who wish to enable TCP/TLS sockets for remote access to
libvirt, for the sake of migration, will need to configure this using
the virtproxyd daemon systemd socket units instead of libvirtd units.
At some point in the future it is intended that the monolithic
libvirtd will be entirely removed by libvirt upstream. This is
predicated on prolonged successful deployment of the modular daemons
in one or more major distros. Thus the likely timeframe is Fedora 37
at the earliest (i.e. min 1 year from successful usage of modular
daemons in a distro).
== How To Test ==
Hardware:
No special hardware is required for testing, since QEMU can run in
emulated mode if hardware virtualization is not available
Preparation:
Deploy a completely fresh Fedora install, since systemd preset changes
only take effect on initial installation. Ensure that virtualization
is installed with QEMU/KVM.
Actions:
Boot the system and observice that 'virtqemud' is running immediately
on completion of boot up with an arg of '--timeout=120'.
After two minutes the daemon should exit, and will automatically
restart if 'virsh -c qemu:///system list' is run as root.
Deploy a new virtual machine using virt-install / virt-manager.
Set the new VM to autostart, eg 'virsh -c qemu:///system autostart $GUESTNAME'
Shutdown the guest and reboot the host
Upon completion of boot up observe that 'virtqemud' is running, and
also a QEMU guest is running. 'virtqemud' should remain running for as
long as the guest is running.
The 'virtnetworkd' will also be running if the guest is connected to
the 'virbr0' virtual network device provided by libvirt.
== User Experience ==
Users of libvirt applications should not see any functional changes in
their experience, since the new modular daemons are intended to be
fully backwards compatible with existing libvirtd daemon.
Administrators configuring hosts, however, will need to be aware that
a different set of libvirt daemons will be running than they have seen
in the past. See upgrade impact section for likely impact on
administrators experience.
There may be a small improvement in boot time performance when libvirt
is installed.
== Dependencies ==
The fedora-release package needs updating with the new systemd presets.
== Contingency Plan ==
* Contingency mechanism:
Should unexpected problems with the change arise, the changes in
libvirt and fedora-release will be reverted to the historical known
good behaviour of libvirt in previous Fedora.
* Contingency deadline: Beta freeze
* Blocks release? Yes
== Documentation ==
Primary upstream guidance is https://libvirt.org/daemons.html
== Release Notes ==
The libvirt package has switched to using modular daemons by default.
The monolithic libvirtd daemon will no longer be started. In its place
a hypervisor specific daemon will be started, along with one or more
secondary driver daemons.
Applications using libvirt APIs should not notice any difference in behaviour.
Administrators configuring a host manually, or using automation tools
such as ansible/puppet, may need to take account of the new daemons
that are providing libvirt functionality.
--
Ben Cotton
He / Him / His
Fedora Program Manager
Red Hat
TZ=America/Indiana/Indianapolis
2 years, 11 months
Orphaned packages looking for new maintainers
by Miro Hrončok
The following packages are orphaned and will be retired when they
are orphaned for six weeks, unless someone adopts them. If you know for sure
that the package should be retired, please do so now with a proper reason:
https://fedoraproject.org/wiki/How_to_remove_a_package_at_end_of_life
Note: If you received this mail directly you (co)maintain one of the affected
packages or a package that depends on one. Please adopt the affected package or
retire your depending package to avoid broken dependencies, otherwise your
package will fail to install and/or build when the affected package gets retired.
Request package ownership via the *Take* button in he left column on
https://src.fedoraproject.org/rpms/<pkgname>
Full report available at:
https://churchyard.fedorapeople.org/orphans-2021-06-21.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
================================================================================
HdrHistogram acaringi, almac, hhorak, jvanek, 0 weeks ago
orphan
JSCookMenu orphan 0 weeks ago
WebCalendar orphan 0 weeks ago
ant-antunit cipherboy, dmoluguw, jmagne, 4 weeks ago
mizdebsk, orion, orphan
apache-commons-daemon cipherboy, dmoluguw, jmagne, 4 weeks ago
mizdebsk, orphan, spike
apache-commons-lang cipherboy, dmoluguw, jmagne, 4 weeks ago
mizdebsk, orphan, spike
automaton orphan 2 weeks ago
biboumi louizatakk, orphan 0 weeks ago
directory-maven-plugin almac, orphan, sasiddiq 0 weeks ago
dpsearch codeblock, jam3s, orphan 3 weeks ago
electrum orphan 1 weeks ago
erlang-riak_pipe bowlofeggs, erlang-maint-sig, orphan 1 weeks ago
felix-scr jerboaa, orphan 0 weeks ago
git-cal codeblock, orphan 3 weeks ago
jakarta-activation java-maint-sig, orphan 0 weeks ago
jakarta-mail java-maint-sig, orphan 0 weeks ago
java-atk-wrapper omajid, orphan 1 weeks ago
jboss-annotations-1.2-api cfu, cipherboy, ckelley, dmoluguw, 0 weeks ago
jmagne, mharmsen, orphan
jboss-jms-1.1-api cipherboy, dmoluguw, jmagne, lef, 4 weeks ago
orphan
jboss-logmanager cipherboy, dmoluguw, gil, jmagne, 2 weeks ago
lef, orphan
jmc almac, orphan, sasiddiq 0 weeks ago
jmc-core almac, orphan, sasiddiq 0 weeks ago
luit ajax, ofourdan, orphan 2 weeks ago
lz4-java orphan 0 weeks ago
mate-applet-softupd orphan 0 weeks ago
maven-javadoc-plugin java-maint-sig, mizdebsk, orphan 5 weeks ago
mvel orphan 0 weeks ago
owasp-java-encoder almac, orphan, sasiddiq 0 weeks ago
paranamer cipherboy, jmagne, orphan 4 weeks ago
perl-Debug-Client orphan, ppisar 1 weeks ago
perl-Hardware-Vhdl-Tidy orphan 6 weeks ago
perl-Padre orphan, ppisar 1 weeks ago
php-PHPMailer orphan, remi 0 weeks ago
php-captchaphp orphan 0 weeks ago
php-hkit orphan 0 weeks ago
php-pear-Auth-Yubico orphan 0 weeks ago
php-rmccue-requests orphan 1 weeks ago
python-fn codeblock, orphan 3 weeks ago
python-glusterfs-api humble, orphan 0 weeks ago
python-pytest-relaxed orphan 1 weeks ago
python-tempita kylev, orphan 0 weeks ago
qtpass marcindulak, orphan, vascom 4 weeks ago
robodoc orphan 0 weeks ago
rubygem-ditz orphan 3 weeks ago
rubygem-mono_logger orphan 3 weeks ago
rubygem-redis-namespace orphan 3 weeks ago
rubygem-resque orphan 3 weeks ago
rubygem-sdoc orphan 1 weeks ago
rubygem-thin mmagr, orphan, valtri, vondruch 2 weeks ago
rubygem-trollop orphan 3 weeks ago
rubygem-vegas orphan 3 weeks ago
stax2-api cfu, ckelley, java-maint-sig, 0 weeks ago
jmagne, mharmsen, mizdebsk, orphan
woodstox-core cfu, ckelley, java-maint-sig, 0 weeks ago
jmagne, mharmsen, mizdebsk, orphan
The following packages require above mentioned packages:
Report too long, see the full version at
https://churchyard.fedorapeople.org/orphans-2021-06-21.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):
abbra: jboss-annotations-1.2-api, python-tempita, rubygem-thin, jakarta-activation
abompard: python-tempita
acaringi: HdrHistogram
adeza: python-tempita
aglitke: rubygem-thin
ahughes: HdrHistogram, directory-maven-plugin, owasp-java-encoder, jmc-core,
felix-scr, jmc
ajax: luit
akurtakov: jakarta-mail, HdrHistogram, directory-maven-plugin,
owasp-java-encoder, jmc-core, felix-scr, jmc
alexlan: jakarta-mail
almac: jakarta-mail, HdrHistogram, directory-maven-plugin, owasp-java-encoder,
jmc-core, felix-scr, jmc
amerey: rubygem-thin
andreamanzi: python-tempita
anoopcs: python-tempita, rubygem-thin
apevec: python-tempita
arobinso: jakarta-mail, HdrHistogram, directory-maven-plugin,
owasp-java-encoder, jmc-core, felix-scr, jmc
asn: python-tempita, rubygem-thin
asosedkin: HdrHistogram, directory-maven-plugin, jmc-core, felix-scr, jmc
astro-sig: jakarta-mail
atim: HdrHistogram, directory-maven-plugin, jmc-core, felix-scr, jmc
bashton: jakarta-mail
bbockelm: rubygem-thin
bcotton: rubygem-thin
berrange: python-tempita, rubygem-thin
besser82: python-tempita
bkearney: jakarta-mail, rubygem-thin
bonzini: python-tempita, rubygem-thin
bowlofeggs: erlang-riak_pipe
branto: python-tempita
bruno: jakarta-mail
caniszczyk: HdrHistogram, directory-maven-plugin, owasp-java-encoder, jmc-core,
felix-scr, jmc
caolanm: jakarta-mail
cfeist: rubygem-thin
cfu: jakarta-mail, jboss-annotations-1.2-api, woodstox-core, stax2-api,
jakarta-activation
cheimes: jboss-annotations-1.2-api
cipherboy: apache-commons-lang, jakarta-activation, jakarta-mail,
jboss-annotations-1.2-api, jboss-logmanager, apache-commons-daemon, paranamer,
ant-antunit, jboss-jms-1.1-api
ckelley: jakarta-mail, jboss-annotations-1.2-api, woodstox-core, stax2-api,
jakarta-activation
clalance: python-tempita, rubygem-thin
cockpit: rubygem-thin
codeblock: dpsearch, git-cal, python-fn
coolsvap: jakarta-mail
crobinso: python-tempita, rubygem-thin
crypto-team: HdrHistogram, directory-maven-plugin, jmc-core, felix-scr, jmc
csutherl: jakarta-mail
cverna: python-tempita
dang: python-tempita, rubygem-thin
dbhole: jakarta-mail, HdrHistogram, directory-maven-plugin, owasp-java-encoder,
jmc-core, felix-scr, jmc
dcallagh: python-tempita
dcavalca: HdrHistogram, directory-maven-plugin, jmc-core, felix-scr, jmc
dchen: jakarta-mail, jakarta-activation
deamn: jakarta-mail, HdrHistogram, directory-maven-plugin, owasp-java-encoder,
jmc-core, felix-scr, jmc
devos: jakarta-mail, python-tempita, rubygem-thin
devrim: jakarta-mail
dignan: jakarta-mail
dmick: python-tempita
dmoluguw: apache-commons-lang, jakarta-activation, jakarta-mail,
jboss-annotations-1.2-api, jboss-logmanager, apache-commons-daemon,
ant-antunit, jboss-jms-1.1-api
drsmith2: rubygem-thin
dtardon: jakarta-mail
dwalluck: jakarta-mail
dwmw2: python-tempita, rubygem-thin
ebaron: jakarta-mail, HdrHistogram, directory-maven-plugin, owasp-java-encoder,
jmc-core, felix-scr, jmc
eclipse-sig: jakarta-mail, HdrHistogram, directory-maven-plugin,
owasp-java-encoder, jmc-core, felix-scr, jmc
eclipseo: python-tempita, rubygem-thin
edewata: jboss-annotations-1.2-api, jakarta-mail, jakarta-activation
eerlands: rubygem-thin
ehabkost: python-tempita, rubygem-thin
ellert: jakarta-mail, python-tempita, php-PHPMailer, jakarta-activation
elmarco: rubygem-thin
erack: jakarta-mail
erlang-maint-sig: erlang-riak_pipe
f1ash: rubygem-thin
fab: rubygem-thin
fabiand: jakarta-mail
fbo: python-tempita
fcami: jboss-annotations-1.2-api
fche: rubygem-thin
feborges: rubygem-thin
fidencio: rubygem-thin
filiperosset: jakarta-mail, HdrHistogram, directory-maven-plugin, jmc-core,
felix-scr, jmc
fnasser: jakarta-mail
galileo: jakarta-mail, HdrHistogram, directory-maven-plugin,
owasp-java-encoder, jmc-core, felix-scr, jmc
gchamoul: python-tempita
gd: python-tempita, rubygem-thin
giallu: python-tempita, php-PHPMailer
gil: apache-commons-lang, jakarta-mail, jboss-logmanager, jakarta-activation
gnome-sig: rubygem-thin
go-sig: python-tempita
grover: python-tempita, rubygem-thin
guidograzioli: jakarta-mail
hguemar: jakarta-mail
hhorak: jakarta-mail, HdrHistogram, directory-maven-plugin, jmc-core,
felix-scr, jmc
humble: python-glusterfs-api, rubygem-thin
huwang: jakarta-mail
iboukris: python-tempita, rubygem-thin
idevat: rubygem-thin
ignatenkobrain: python-tempita
imcleod: rubygem-thin
infra-sig: jboss-annotations-1.2-api, python-tempita
ipa-maint: jboss-annotations-1.2-api
iucar: jakarta-mail, HdrHistogram, directory-maven-plugin, jmc-core, felix-scr, jmc
jam3s: dpsearch
jandrlik: jakarta-mail
jarrpa: python-tempita, rubygem-thin
java-maint-sig: jakarta-mail, maven-javadoc-plugin, HdrHistogram,
directory-maven-plugin, woodstox-core, jmc-core, felix-scr, stax2-api, jmc,
jakarta-activation
java-sig: jakarta-mail, HdrHistogram, directory-maven-plugin, woodstox-core,
jmc-core, felix-scr, stax2-api, jmc, jakarta-activation
jcapik: jakarta-mail
jcaratzas: python-tempita
jenslody: HdrHistogram, directory-maven-plugin, jmc-core, felix-scr, jmc
jerboaa: jakarta-mail, HdrHistogram, directory-maven-plugin,
owasp-java-encoder, jmc-core, felix-scr, jmc
jforbes: python-tempita, rubygem-thin
jhrozek: jboss-annotations-1.2-api
jiffintt: python-tempita, rubygem-thin
jistone: rubygem-thin
jjames: jakarta-mail, jakarta-activation
jjanco: jakarta-mail, HdrHistogram, directory-maven-plugin, jmc-core,
felix-scr, jmc
jjelen: jakarta-mail, ant-antunit
jjohnstn: jakarta-mail, HdrHistogram, directory-maven-plugin,
owasp-java-encoder, jmc-core, felix-scr, jmc, jakarta-activation
jkucera: jakarta-mail
jlayton: python-tempita, rubygem-thin
jmagne: apache-commons-lang, jakarta-activation, jakarta-mail,
jboss-annotations-1.2-api, jboss-logmanager, apache-commons-daemon, paranamer,
woodstox-core, ant-antunit, stax2-api, jboss-jms-1.1-api
jmlich: jakarta-mail
jpena: python-tempita
jplesnik: rubygem-thin
jridky: jakarta-mail
jsafrane: jakarta-mail
jsteffan: rubygem-thin
jstephen: python-tempita, rubygem-thin
jstribny: rubygem-thin
jussilehtola: jakarta-mail
jvanek: jakarta-mail, HdrHistogram, directory-maven-plugin, owasp-java-encoder,
woodstox-core, jmc-core, ant-antunit, felix-scr, stax2-api, jmc
jwrdegoede: jakarta-mail, jakarta-activation
kdaniel: jakarta-mail, HdrHistogram, directory-maven-plugin,
owasp-java-encoder, jmc-core, felix-scr, jmc
kde-sig: rubygem-thin
ke4qqq: python-tempita
kengert: HdrHistogram, directory-maven-plugin, jmc-core, felix-scr, jmc
kevin: python-tempita, rubygem-thin
kkeithle: python-tempita, rubygem-thin
kkoukiou: rubygem-thin
kni: jakarta-mail
korkeala: jakarta-mail
ktdreyer: python-tempita
kwizart: jakarta-mail
kwright: jboss-annotations-1.2-api, jakarta-mail, jakarta-activation
kylev: python-tempita
laine: python-tempita, rubygem-thin
lbazan: python-tempita
lberk: rubygem-thin
leamas: jakarta-mail
lef: jakarta-mail, HdrHistogram, directory-maven-plugin, jboss-logmanager,
owasp-java-encoder, jmc-core, felix-scr, jmc, jboss-jms-1.1-api
libvirt-maint: python-tempita, rubygem-thin
limb: jakarta-mail
ljavorsk: jakarta-mail, HdrHistogram, directory-maven-plugin, jmc-core,
felix-scr, jmc
lkundrak: jakarta-mail, python-tempita, rubygem-thin
lmacken: python-tempita
lnie: rubygem-thin
louizatakk: biboumi
lupinix: jakarta-mail
marcindulak: qtpass
martinpitt: rubygem-thin
marx: rubygem-thin
matt: rubygem-thin
matyas: rubygem-thin
mbacovsk: python-tempita
mbooth: jakarta-mail, HdrHistogram, directory-maven-plugin, owasp-java-encoder,
jmc-core, felix-scr, jmc, jakarta-activation
mcermak: rubygem-thin
mdbooth: rubygem-thin
mef: jakarta-mail
mharmsen: jakarta-mail, jboss-annotations-1.2-api, woodstox-core, stax2-api,
jakarta-activation
mhlavink: rubygem-thin
michaelc: python-tempita, rubygem-thin
michalvala: HdrHistogram, directory-maven-plugin, owasp-java-encoder, jmc-core,
felix-scr, jmc
mikep: jakarta-mail, HdrHistogram, directory-maven-plugin, jmc-core, felix-scr,
rubygem-thin, jmc
mizdebsk: apache-commons-lang, jakarta-mail, maven-javadoc-plugin,
HdrHistogram, directory-maven-plugin, apache-commons-daemon, woodstox-core,
jmc-core, ant-antunit, felix-scr, owasp-java-encoder, stax2-api, jmc,
jakarta-activation
mjakubicek: jakarta-mail, HdrHistogram, directory-maven-plugin, jmc-core,
felix-scr, jmc
mjw: rubygem-thin
mkosek: jboss-annotations-1.2-api
mkrizek: rubygem-thin
mlisik: rubygem-thin
mlombard: python-tempita, rubygem-thin
mmagr: rubygem-thin
mmarusak: rubygem-thin
mmorsi: jakarta-mail
moceap: jakarta-mail
mohammedisam: HdrHistogram, directory-maven-plugin, jmc-core, felix-scr, jmc
mreynolds: jakarta-mail
mrunge: python-tempita
mschorm: jakarta-mail, HdrHistogram, directory-maven-plugin, jmc-core,
felix-scr, jmc
msimacek: jakarta-mail, jakarta-activation
msivak: rubygem-thin
mycae: jakarta-mail
neteler: jakarta-mail
neuro-sig: jakarta-mail, python-tempita
ngompa: jboss-annotations-1.2-api, python-tempita, maven-javadoc-plugin,
rubygem-thin
nhosoi: jakarta-mail
nkinder: jakarta-mail
oalbrigt: rubygem-thin
obnox: python-tempita, rubygem-thin
odubaj: jakarta-mail, HdrHistogram, directory-maven-plugin, jmc-core,
felix-scr, jmc
ofourdan: luit
oget: HdrHistogram, directory-maven-plugin, owasp-java-encoder, jmc-core,
felix-scr, jmc
ogutierrez: jboss-annotations-1.2-api
oliver: jakarta-mail, HdrHistogram, directory-maven-plugin, owasp-java-encoder,
jmc-core, felix-scr, jmc
omajid: jakarta-mail, HdrHistogram, directory-maven-plugin, owasp-java-encoder,
java-atk-wrapper, jmc-core, felix-scr, jmc
omular: rubygem-thin
ondrejj: python-tempita
openstack-sig: python-tempita
orion: jakarta-mail, ant-antunit
osier: python-tempita, rubygem-thin
pali: jakarta-mail
peter: jakarta-mail, erlang-riak_pipe
phrdina: rubygem-thin
pmikova: jakarta-mail, HdrHistogram, directory-maven-plugin, jmc-core,
felix-scr, jmc
ppisar: perl-Padre, perl-Debug-Client
praiskup: jakarta-mail
puiterwijk: jboss-annotations-1.2-api
pvoborni: jboss-annotations-1.2-api
python-sig: jakarta-mail
qa-tools-sig: rubygem-thin
quintela: python-tempita, rubygem-thin
radekmanak: jakarta-mail, HdrHistogram, directory-maven-plugin, jmc-core,
felix-scr, jmc
radez: python-tempita
ralph: python-tempita
raphgro: jakarta-mail, rubygem-thin
rathann: jakarta-mail
rcritten: jboss-annotations-1.2-api
rebus: jakarta-mail
remi: php-PHPMailer
rgrunber: jakarta-mail, HdrHistogram, directory-maven-plugin,
owasp-java-encoder, jmc-core, felix-scr, jmc, jakarta-activation
richardfearn: apache-commons-lang, jakarta-mail, HdrHistogram,
directory-maven-plugin, owasp-java-encoder, jmc-core, felix-scr, jmc
ricky: python-tempita
rjones: python-tempita, rubygem-thin
rmeggins: jakarta-mail
rrelyea: HdrHistogram, directory-maven-plugin, jmc-core, felix-scr, jmc
ruben: rubygem-thin
ruby-packagers-sig: rubygem-thin
sagitter: HdrHistogram, directory-maven-plugin, jmc-core, felix-scr, jmc
sandeen: python-tempita
sasiddiq: jakarta-mail, HdrHistogram, directory-maven-plugin,
owasp-java-encoder, jmc-core, felix-scr, jmc
sbergmann: jakarta-mail
sbonazzo: rubygem-thin
scottt: jakarta-mail, HdrHistogram, directory-maven-plugin, jmc-core,
felix-scr, jmc
scox: rubygem-thin
sdgathman: apache-commons-lang, jakarta-mail, jakarta-activation
sergiomb: jakarta-mail, jakarta-activation
simo: jboss-annotations-1.2-api, python-tempita, rubygem-thin
simonm: python-tempita
skoduri: python-tempita, rubygem-thin
slaanesh: jakarta-mail
smakarov: rubygem-thin
smani: jakarta-mail
smilner: python-tempita
spike: apache-commons-lang, jakarta-mail, apache-commons-daemon
spot: HdrHistogram, directory-maven-plugin, jmc-core, felix-scr, jmc
steve: python-tempita, rubygem-thin
stevetraylen: rubygem-thin
stingray: python-tempita
tdawson: rubygem-trollop, rubygem-thin
tdecacqu: python-tempita
terjeros: jakarta-mail, python-tempita, rubygem-thin
teuf: rubygem-thin
tflink: rubygem-thin
tmraz: HdrHistogram, directory-maven-plugin, jmc-core, felix-scr, jmc
tojeline: rubygem-thin
tpopela: HdrHistogram, directory-maven-plugin, jmc-core, felix-scr, jmc
tstclair: rubygem-thin
ttheisen: rubygem-thin
ttorling: jakarta-mail
twoerner: jboss-annotations-1.2-api
vakwetu: jboss-annotations-1.2-api, jakarta-mail, jakarta-activation
valtri: jakarta-mail, rubygem-trollop, rubygem-thin
van: jakarta-mail
vascom: rubygem-thin, qtpass
vcrhonek: jakarta-mail, rubygem-thin
veillard: jakarta-mail, python-tempita, rubygem-thin
verdurin: jakarta-mail
victortoso: rubygem-thin
virtmaint-sig: python-tempita, rubygem-thin
vjancik: jakarta-mail
volter: jakarta-mail
vondruch: rubygem-trollop, rubygem-thin
vtrefny: jakarta-mail
walters: jakarta-mail
wcohen: rubygem-thin
wilqu: jakarta-mail
xaeth: rubygem-thin
xavierb: jakarta-mail
xiubli: rubygem-thin
zbyszek: jakarta-mail
zeenix: rubygem-thin
zuul: python-tempita
zzambers: jakarta-mail, ant-antunit
--
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
--
Miro Hrončok
--
Phone: +420777974800
IRC: mhroncok
2 years, 11 months