devel-announce July 2022

devel-announce@lists.fedoraproject.org

7 participants
29 discussions

Spins keepalive
by Gregory Bartholomew 06 Jul '22

06 Jul '22

FESco previously approved a requirement that Spin/Labs owners send a keepalive request in order to keep building the spin or lab. I have opened Pagure issues[1] for all Spins and Labs listed on the wiki[2]. If you are the owner of one of those spins and labs, please reply in the appropriate ticket by 19 July 2022 to indicate the spin should continue to be produced. If there is a spin or lab that does not have an open ticket, please create one[3]. The reasoning for this is to not ship spins that are not actively maintained. Future improvements to the release process that will allow for teams to self-publish solutions will eventually remove the need for these keepalives. [1] https://pagure.io/fedora-pgm/schedule/issues?status=Open&tags=spins+keepali… [2] https://fedoraproject.org/wiki/Releases/37/Spins [3] https://pagure.io/fedora-pgm/pgm_team/new_issue

1 0

F37 proposal: Preset All Systemd Units on First Boot (Self-Contained Change proposal)
by Ben Cotton 06 Jul '22

06 Jul '22

https://fedoraproject.org/wiki/Changes/Preset_All_Systemd_Units_on_First_Bo… 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 == Systemd will execute the equivalent of '''systemctl preset-all''' when an unconfigured system is booted ([https://www.freedesktop.org/software/systemd/man/machine-id.html#First%20Bo… "First Boot"] condition). This means that units will be enabled or disabled according to the preset configuration. We currently do the equivalent of '''systemctl preset-all --preset-mode=enable-only''', and this will be extended to also disable units, i.e. '''systemctl preset-all --preset-mode=full'''. Any units which are manually symlinked but presets say they shouldn't (which is against the packaging guidelines for packaged units) will be disabled. Note that this applies to "first boot" only, i.e. to boot from an image without ''/etc'' fully populated. In does not apply to systems that were installed using Anaconda. == Owner == * Name: [[User:jlebon| Jonathan Lebon]] * Name: [[User:Zbyszek| Zbigniew Jędrzejewski-Szmek]] * Email: zbyszek at in.waw.pl, jlebon at redhat.com == Detailed Description == Our [https://docs.fedoraproject.org/en-US/packaging-guidelines/Scriptlets/#_syst… guidelines] say that units that are packaged in rpms must be enabled through macros (''%systemd_post'') and the preset system. Almost all packages conform to this, so effectively their enablement state follows the preset config. When the system is installed, or more precisely when ''systemd.rpm'' is installed, we do ''preset-all''. But for historical reasons, when booting an unconfigured system ("first boot") we only 'enable' units in this fashion. In Fedora and RHEL CoreOS, some symlinks are created in the golden image, but should be disabled in the local image after local preset configuration has been inserted. To make this work, the call in systemd will be changed to execute the equivalent of ''preset-all --preset-mode=full'', making enablement during "first boot" more like enablement during an Anaconda installation. == Benefit to Fedora == * CoreOS can insert local preset configuration through Ignition and this configuration will be applied on the first boot. * Users can do something similar with local preset configuration on distributed images. * The system is made a bit simpler and easier to understand, because we can say that "units are enabled/disabled after installation as specified by the preset system". * Users can call ''systemctl preset-all'' at any time to apply preset-configuration. If no local changes to configuration have been made, ''preset-all'' would make no changes to unit state. If units have been enabled or disabled, ''preset-all'' would return unit enablement to the pristine state after installation. == Scope == * Proposal owners: ** implement patch for systemd to configure preset-all mode on first boot (https://github.com/systemd/systemd/pull/15205) ** build systemd with this mode changed to ''--preset-mode=full'' ** provide pull requests for two packages which have been identified to not use the preset system for enablement to conform to the packaging guidelines (https://bugzilla.redhat.com/show_bug.cgi?id=2070862, https://bugzilla.redhat.com/show_bug.cgi?id=2070726) * Other developers: review and merge the pull requests * Release engineering: N/A * Policies and guidelines: none, this change is about following the guidelines more closely * Trademark approval: N/A (not needed for this Change) * Alignment with Objectives: == Upgrade/compatibility impact == None. == How To Test == * On a newly installed system, with arbitrary set of packages: call ''systemctl preset-all''. This should result in no changes. * On a system which is booted from an unconfigured image (e.g. the new Server VM image should qualify, see [[Changes/Supplement-server-by-kvm-vm-image]]): before the first boot, enable some units manually that are disabled in presets. After booting, those units should be disabled again. == User Experience == In general this change will be a noop for users, because it only applies to "first boot", i.e. to the case when a system is booted from a distributable image without local configuration and is configured when initially booted. In case where Anaconda is used to install images, /etc is populated before the first boot and the "first boot" condition never applies, thus this change is irrelevant. On systems installed from a "golden image" such as Fedora CoreOS, units will follow the preset configuration more closely. Thanks to the fixes to make packages conform to packaging guidelines, users can call '''preset-all''' to return the system to defaults. == Dependencies == == Contingency Plan == * Contingency mechanism: (What to do? Who will do it?) Systemd maintainers: flip back the default in systemd, rebuild. * Contingency deadline: N/A (not a System Wide Change) This can be done at any time up to the release. * Blocks release? No. == Documentation == N/A (not a System Wide Change) -- Ben Cotton He / Him / His Fedora Program Manager Red Hat TZ=America/Indiana/Indianapolis

1 0

F37 proposal: Officially Support Raspberry Pi 4 (Self-Contained Change proposal)
by Ben Cotton 05 Jul '22

05 Jul '22

https://fedoraproject.org/wiki/Changes/RaspberryPi4 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 == The work around Raspberry Pi 4 has been on going for a number of years, but we've never officially supported it due to lack of accelerated graphics and other key features. A few of us have led the push to get the accelerated graphics work over the line upstream so it now makes sense to enable this in Fedora and make support for the Raspberry Pi 4 more official. == Owner == * Name: [[User:pbrobinson| Peter Robinson]] * Email: [mailto:pbrobinson@fedoraproject.org pbrobinson(a)fedoraproject.org] == Detailed Description == The support for the Raspberry Pi ecosystem has been an ongoing evolution. The aim of this change is to support the Raspberry Pi 4 including the 4B, the 400 and the CM4 with IO board. Upstream now supports accelerated graphics using the V3D GPU for both OpenGL-ES and Vulkan. There's also enhancement to wired networking with support for PTPv2 on the CM4/4B. This work will polish the support for the Raspberry Pi 4 and include some wider general improvements to the Raspberry Pis that we officially support which include the RPi3 series and the Zero2W. There are some minor caveats here: * Support for WiFi on the Raspberry Pi 400 is out of scope as it's dependent on the engagement (in this case the lack of) the vendor, Synaptics, of the WiFi module shipped on this device providing generic upstream firmware. * The Raspberry Pi CM4 is an a module designed for IoT, Edge and Embedded use cases. We will test and support the CM4 on the official IO board, it should work on other devices that incorporate the CM4 assuming the vendor has their support in the upstream Raspberry Pi firmware/overlays. * Further device support around audio and other such pieces will be reviewed as part of the process. == Benefit to Fedora == The Raspberry Pi 4 is a widely available, reasonably prices device. It has worked well in Fedora for some time in IoT and Server use cases, and now with a fully accelerated graphics stack available it's a great device from a price-per-performance perspective, and it has a wide ecosystem, so fully supporting this in Fedora makes a compelling case. == Scope == * Proposal owners: ** Ensure any patches required are accepted upstream ** Work with kernel, mesa and other maintainers to ensure everything is as it should be ** Test * Other developers: ** No direct impact, those already using the device in non-graphical use cases should see no impact. * Release engineering: [https://pagure.io/releng/issue/10872 #10872] * Policies and guidelines: N/A (not a System Wide Change) * Trademark approval: N/A (not needed for this Change) == Upgrade/compatibility impact == There is no upgrade impact. Those running Fedora on the Raspberry Pi 4 previously will, depending on their use case, get an enhanced experience. == How To Test == * Buy a Raspberry Pi 4 (if you can) * Test your favourite aarch64 Edition, Spin in particular the desktop environments such as Workstation. == User Experience == The experience should now include fully accelerated graphics. == Dependencies == No external dependencies outside of specific work relating to the specified hardware. == Contingency Plan == * Contingency mechanism: None * Contingency deadline: GA * Blocks release? No. * Blocks product? No. == Documentation == Update the Raspberry Pi FAQ and other documentation including migrating it to docs.fedoraproject.org == Release Notes == Fedora now supports the Raspberry Pi 4! -- Ben Cotton He / Him / His Fedora Program Manager Red Hat TZ=America/Indiana/Indianapolis

1 0

F37 proposal: LXQt 1.1.0 (Self-Contained Change proposal)
by Ben Cotton 05 Jul '22

05 Jul '22

https://fedoraproject.org/wiki/Changes/LXQt_1.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 == Update LXQt to 1.1.0 in Fedora. == Owner == * Name: [[User:Zsun|Zamir SUN]] * Email: zsun#AT#fedoraproject.org  == Detailed Description == LXQt 1.1.0 released with a bunch of bugfixes and new features including but not limited to Qt6 integration, appearance changes etc. It's always good to keep Fedora users running on most recent software. Detailed LXQt release note is available [https://lxqt-project.org/release/2022/04/15/lxqt-1-1-0/ here]. == Benefit to Fedora == This change brings bug fixes and enhancements to LXQt in Fedora. == Scope == * Proposal owners: Update all the LXQt related packages in Fedora. * Other developers: N/A (not a System Wide Change) * Release engineering: https://pagure.io/releng/issue/10870 * 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 using the spin, netinstall or DVD. Or upgrade from older release. Then users should be able to test by doing any daily work. == User Experience == There will be a better user experience and some new features to explore. == Dependencies == This update is pretty self contained. == Contingency Plan == * Contingency mechanism: If I cannot make it happen, I'll just do not merge side-tag into f37 branch. * Contingency deadline: Fedora 37 Beta Freeze * Blocks release? N/A (not a System Wide Change) * Blocks product? N/A == Documentation == N/A (not a System Wide Change) -- Ben Cotton He / Him / His Fedora Program Manager Red Hat TZ=America/Indiana/Indianapolis

1 0

Nest with Fedora Registration Open (CfP still open until July 8th!)
by Marie Nordin 05 Jul '22

05 Jul '22

Hi folks, Nest with Fedora 2022 registration is now open [0]! Make sure to register and share the link with Fedora Friends. The Nest CfP is open until July 8th(this Friday!), and we encourage Fedorans to submit the latest and greatest projects(as well as all the usual standbys, of course;)) to the Flock Pagure repo [1]. Learn more about the CfP on the CommBlog [2]. This year community members are organizing local in person meetups called Fedora Hatches across the world. This is a great chance for Fedora contributors to meet in person. Learn more about the dates and locations of the Fedora Hatches on the CommBlog [3]. [0] https://hopin.com/events/nest-with-fedora-2022/registration [1] https://pagure.io/flock/issues [2] https://communityblog.fedoraproject.org/nest-2022-cfp/ [3] https://communityblog.fedoraproject.org/hatch-with-fedora/ Cheers! -- Marie Nordin Fedora Community Action and Impact Coordinator Red Hat <https://www.redhat.com/> • Fedora Project <https://getfedora.org/> She/Her/Hers IRC/Element: riecatnor <https://red.ht/sig>

1 0

signing vault down (2022-07-04)
by Kevin Fenzi 04 Jul '22

04 Jul '22

Greetings. We were having some issues with the management interface on our primary signing vault. The server was power cycled, but the management is still not functioning, and now the server isn't processing signing requests further. Due to the US holidays there's no one on site right now, but we will hopefully have someone there early tomorrow morning to troubleshoot and bring things back up. Until this server is back up, builds will queue up in signing/pending koji tags and not move forward. This means they will not land in the buildroot or be available as updates. Once the server is processing again the backlog should be processed, so there's no need to do anything special. Thank you for your patience. kevin

1 0

Orphaned packages looking for new maintainers
by Miro Hrončok 04 Jul '22

04 Jul '22

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-07-01.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 ================================================================================ ez-pine-gpg orphan 0 weeks ago gfbgraph orphan 2 weeks ago gnome-online-accounts gnome-sig, orphan 2 weeks ago gnome-online-miners orphan, pranvk 2 weeks ago golang-github-rubyist-tracerx orphan 0 weeks ago gpart dcantrell, orphan 0 weeks ago module-macros orphan 0 weeks ago netmask orphan 0 weeks ago pam_url herlo, orphan 2 weeks ago preproc orphan 0 weeks ago preproc-rpmspec orphan 0 weeks ago python-proteus orphan 2 weeks ago rpkg-macros orphan 0 weeks ago rpkg-util orphan 0 weeks ago rpm-git-tag-sort orphan 0 weeks ago rust-curve25519-dalek orphan, rust-sig 1 weeks ago tryton orphan 2 weeks ago trytond orphan 2 weeks ago trytond-account orphan 2 weeks ago trytond-account-be orphan 2 weeks ago trytond-account-de-skr03 orphan 2 weeks ago trytond-account-invoice orphan 2 weeks ago trytond-account-invoice-history orphan 2 weeks ago trytond-account-invoice-line- orphan 2 weeks ago standalone trytond-account-product orphan 2 weeks ago trytond-account-statement orphan 2 weeks ago trytond-account-stock-anglo-saxon orphan 2 weeks ago trytond-account-stock-continental orphan 2 weeks ago trytond-analytic-account orphan 2 weeks ago trytond-analytic-invoice orphan 2 weeks ago trytond-analytic-purchase orphan 2 weeks ago trytond-analytic-sale orphan 2 weeks ago trytond-company orphan 2 weeks ago trytond-company-work-time orphan 2 weeks ago trytond-country orphan 2 weeks ago trytond-currency orphan 2 weeks ago trytond-dashboard orphan 2 weeks ago trytond-google-maps orphan 2 weeks ago trytond-ldap-authentication orphan 2 weeks ago trytond-party orphan 2 weeks ago trytond-party-siret orphan 2 weeks ago trytond-product orphan 2 weeks ago trytond-product-cost-fifo orphan 2 weeks ago trytond-product-cost-history orphan 2 weeks ago trytond-product-price-list orphan 2 weeks ago trytond-project orphan 2 weeks ago trytond-project-plan orphan 2 weeks ago trytond-project-revenue orphan 2 weeks ago trytond-purchase orphan 2 weeks ago trytond-purchase-invoice-line- orphan 2 weeks ago standalone trytond-sale orphan 2 weeks ago trytond-sale-opportunity orphan 2 weeks ago trytond-sale-price-list orphan 2 weeks ago trytond-stock orphan 2 weeks ago trytond-stock-forecast orphan 2 weeks ago trytond-stock-inventory-location orphan 2 weeks ago trytond-stock-location-sequence orphan 2 weeks ago trytond-stock-product-location orphan 2 weeks ago trytond-stock-supply orphan 2 weeks ago trytond-stock-supply-day orphan 2 weeks ago trytond-timesheet orphan 2 weeks ago zuul openstack-sig, orphan, zuul 1 weeks ago The following packages require above mentioned packages: Depending on: gfbgraph (3), status change: 2022-06-16 (2 weeks ago) gnome-maps (maintained by: elad, gnome-sig, kalev, kathenas, zeenix) gnome-maps-42.2-1.fc37.x86_64 requires gfbgraph(x86-64) = 0.2.4-2.fc36 gnome-online-miners (maintained by: orphan, pranvk) gnome-online-miners-3.34.0-10.fc36.src requires gfbgraph-devel = 0.2.4-2.fc36 gnome-online-miners-3.34.0-10.fc36.x86_64 requires libgfbgraph-0.2.so.0()(64bit) gnome-photos (maintained by: gnome-sig, pranvk) gnome-photos-42.0-3.fc37.src requires pkgconfig(libgfbgraph-0.2) = 0.2.4 gnome-photos-42.0-3.fc37.x86_64 requires gfbgraph(x86-64) = 0.2.4-2.fc36, gnome-online-miners = 3.34.0-10.fc36, libgfbgraph-0.2.so.0()(64bit) Depending on: gnome-online-accounts (21), status change: 2022-06-16 (2 weeks ago) bijiben (maintained by: gnome-sig, mcrha, pwalter) bijiben-40.1-3.fc36.src requires pkgconfig(goa-1.0) = 3.44.0 bijiben-40.1-3.fc36.x86_64 requires libgoa-1.0.so.0()(64bit) cinnamon-control-center (maintained by: besser82, jcpunk, leigh123linux) cinnamon-control-center-5.4.2-1.fc37.src requires pkgconfig(goa-1.0) = 3.44.0, pkgconfig(goa-backend-1.0) = 3.44.0 cinnamon-control-center-5.4.2-1.fc37.x86_64 requires libgoa-1.0.so.0()(64bit), libgoa-backend-1.0.so.1()(64bit) claws-mail (maintained by: mschwendt) claws-mail-plugins-gdata-4.1.0-4.fc37.x86_64 requires libgoa-1.0.so.0()(64bit) deja-dup (maintained by: csmart, jiteshs, kengert, limb, pwalter) deja-dup-43.4-1.fc37.src requires gnome-online-accounts-devel = 3.44.0-1.fc37 evolution-data-server (maintained by: alexl, caillon, caolanm, mbarnes, mcrha, rhughes, rstrode, ssp) evolution-data-server-3.44.3-1.fc37.i686 requires libgoa-1.0.so.0 evolution-data-server-3.44.3-1.fc37.src requires pkgconfig(goa-1.0) = 3.44.0 evolution-data-server-3.44.3-1.fc37.x86_64 requires libgoa-1.0.so.0()(64bit) evolution-data-server-devel-3.44.3-1.fc37.i686 requires pkgconfig(goa-1.0) = 3.44.0 evolution-data-server-devel-3.44.3-1.fc37.x86_64 requires pkgconfig(goa-1.0) = 3.44.0 geary (maintained by: salimma, thm) geary-40.0-5.fc36.src requires pkgconfig(goa-1.0) = 3.44.0 geary-40.0-5.fc36.x86_64 requires libgoa-1.0.so.0()(64bit) gfbgraph (maintained by: orphan) gfbgraph-0.2.4-2.fc36.i686 requires libgoa-1.0.so.0 gfbgraph-0.2.4-2.fc36.src requires pkgconfig(goa-1.0) = 3.44.0 gfbgraph-0.2.4-2.fc36.x86_64 requires libgoa-1.0.so.0()(64bit) gfbgraph-devel-0.2.4-2.fc36.i686 requires pkgconfig(goa-1.0) = 3.44.0 gfbgraph-devel-0.2.4-2.fc36.x86_64 requires pkgconfig(goa-1.0) = 3.44.0 gnome-contacts (maintained by: alexl, gnome-sig, kalev, mcrha) gnome-contacts-42.0-1.fc37.src requires pkgconfig(goa-1.0) = 3.44.0 gnome-contacts-42.0-1.fc37.x86_64 requires libgoa-1.0.so.0()(64bit) gnome-control-center (maintained by: gnome-sig, pwalter) gnome-control-center-42.2-2.fc37.src requires pkgconfig(goa-1.0) = 3.44.0, pkgconfig(goa-backend-1.0) = 3.44.0 gnome-control-center-42.2-2.fc37.x86_64 requires gnome-online-accounts(x86-64) = 3.44.0-1.fc37, libgoa-1.0.so.0()(64bit), libgoa-backend-1.0.so.1()(64bit) gnome-initial-setup (maintained by: gnome-sig, magcius, rtcm) gnome-initial-setup-42.2-4.fc37.src requires pkgconfig(goa-1.0) = 3.44.0, pkgconfig(goa-backend-1.0) = 3.44.0 gnome-initial-setup-42.2-4.fc37.x86_64 requires libgoa-1.0.so.0()(64bit), libgoa-backend-1.0.so.1()(64bit) gnome-music (maintained by: gnome-sig, kalev) gnome-music-42.1-2.fc37.noarch requires gnome-online-accounts = 3.44.0-1.fc37 gnome-music-42.1-2.fc37.src requires pkgconfig(goa-1.0) = 3.44.0 gnome-online-miners (maintained by: orphan, pranvk) gnome-online-miners-3.34.0-10.fc36.src requires gnome-online-accounts-devel = 3.44.0-1.fc37 gnome-online-miners-3.34.0-10.fc36.x86_64 requires libgoa-1.0.so.0()(64bit) gnome-photos (maintained by: gnome-sig, pranvk) gnome-photos-42.0-3.fc37.src requires pkgconfig(goa-1.0) = 3.44.0 gnome-photos-42.0-3.fc37.x86_64 requires libgoa-1.0.so.0()(64bit) gnome-todo (maintained by: amigadave, gnome-sig, ignatenkobrain, mcrha) gnome-todo-41.0-3.fc36.src requires pkgconfig(goa-1.0) = 3.44.0 gnome-todo-41.0-3.fc36.x86_64 requires libgoa-1.0.so.0()(64bit) grilo-plugins (maintained by: gnome-sig, hadess, victortoso) grilo-plugins-0.3.14-3.fc36.i686 requires gnome-online-accounts(x86-32) = 3.44.0-1.fc37, libgoa-1.0.so.0 grilo-plugins-0.3.14-3.fc36.src requires gnome-online-accounts-devel = 3.44.0-1.fc37 grilo-plugins-0.3.14-3.fc36.x86_64 requires gnome-online-accounts(x86-64) = 3.44.0-1.fc37, libgoa-1.0.so.0()(64bit) gvfs (maintained by: alexl, oholy) gvfs-1.50.2-1.fc37.src requires pkgconfig(goa-1.0) = 3.44.0 gvfs-goa-1.50.2-1.fc37.x86_64 requires libgoa-1.0.so.0()(64bit) libgdata (maintained by: rakesh, rishi) libgdata-0.18.1-4.fc36.i686 requires libgoa-1.0.so.0 libgdata-0.18.1-4.fc36.src requires gnome-online-accounts-devel = 3.44.0-1.fc37 libgdata-0.18.1-4.fc36.x86_64 requires libgoa-1.0.so.0()(64bit) libgdata-devel-0.18.1-4.fc36.i686 requires pkgconfig(goa-1.0) = 3.44.0 libgdata-devel-0.18.1-4.fc36.x86_64 requires pkgconfig(goa-1.0) = 3.44.0 syncevolution (maintained by: mcrha) syncevolution-1:2.0.0-3.fc36.src requires gnome-online-accounts-devel = 3.44.0-1.fc37 cinnamon (maintained by: besser82, jcpunk, leigh123linux) cinnamon-5.4.2-1.fc37.x86_64 requires cinnamon-control-center(x86-64) = 5.4.2-1.fc37 cinnamon-session (maintained by: besser82, jcpunk, leigh123linux) cinnamon-session-5.4.0-1.fc37.x86_64 requires cinnamon-control-center-filesystem = 5.4.2-1.fc37 clawsker (maintained by: cwickert, mschwendt) clawsker-1.3.5-1.fc36.noarch requires claws-mail = 4.1.0-4.fc37 Too many dependencies for gnome-online-accounts, not all listed here Depending on: gnome-online-miners (1), status change: 2022-06-16 (2 weeks ago) gnome-photos (maintained by: gnome-sig, pranvk) gnome-photos-42.0-3.fc37.x86_64 requires gnome-online-miners = 3.34.0-10.fc36 Depending on: golang-github-rubyist-tracerx (2), status change: 2022-07-02 (0 weeks ago) git-lfs (maintained by: carlwgeorge, go-sig, qulogic) git-lfs-3.1.2-1.fc37.src requires golang(github.com/rubyist/tracerx) = 0-14.20190524git7879593.fc36 golang-github-git-lfs-3-devel-3.1.2-1.fc37.noarch requires golang(github.com/rubyist/tracerx) = 0-14.20190524git7879593.fc36 sparkleshare (maintained by: tpokorra) sparkleshare-3.28-7.fc36.x86_64 requires git-lfs = 3.1.2-1.fc37 Depending on: preproc (4), status change: 2022-07-02 (0 weeks ago) preproc-rpmspec (maintained by: orphan) preproc-rpmspec-1.3-3.fc36.noarch requires preproc = 0.5-4.fc36, rpkg-macros = 2.0-3.fc36 rpkg-util (maintained by: orphan) rpkg-3.2-2.fc37.noarch requires preproc = 0.5-4.fc36, rpkg-macros = 2.0-3.fc36 rpkg-util-3.2-2.fc37.src requires preproc = 0.5-4.fc36, rpkg-macros = 2.0-3.fc36 rpkg-macros (maintained by: orphan) rpkg-macros-2.0-3.fc36.src requires preproc = 0.5-4.fc36 copr-rpmbuild (maintained by: copr-sig, dturecek, frostyx, praiskup) copr-builder-0.58-1.fc37.x86_64 requires rpkg = 3.2-2.fc37 Depending on: rpkg-macros (3), status change: 2022-07-02 (0 weeks ago) preproc-rpmspec (maintained by: orphan) preproc-rpmspec-1.3-3.fc36.noarch requires rpkg-macros = 2.0-3.fc36 rpkg-util (maintained by: orphan) rpkg-3.2-2.fc37.noarch requires rpkg-macros = 2.0-3.fc36 rpkg-util-3.2-2.fc37.src requires rpkg-macros = 2.0-3.fc36 copr-rpmbuild (maintained by: copr-sig, dturecek, frostyx, praiskup) copr-builder-0.58-1.fc37.x86_64 requires rpkg = 3.2-2.fc37 Depending on: rpkg-util (1), status change: 2022-07-02 (0 weeks ago) copr-rpmbuild (maintained by: copr-sig, dturecek, frostyx, praiskup) copr-builder-0.58-1.fc37.x86_64 requires rpkg = 3.2-2.fc37 Depending on: rpm-git-tag-sort (4), status change: 2022-07-02 (0 weeks ago) rpkg-macros (maintained by: orphan) rpkg-macros-2.0-3.fc36.noarch requires rpm-git-tag-sort = 1.0-6.fc36 rpkg-macros-2.0-3.fc36.src requires rpm-git-tag-sort = 1.0-6.fc36 preproc-rpmspec (maintained by: orphan) preproc-rpmspec-1.3-3.fc36.noarch requires rpkg-macros = 2.0-3.fc36 rpkg-util (maintained by: orphan) rpkg-3.2-2.fc37.noarch requires rpkg-macros = 2.0-3.fc36 rpkg-util-3.2-2.fc37.src requires rpkg-macros = 2.0-3.fc36 copr-rpmbuild (maintained by: copr-sig, dturecek, frostyx, praiskup) copr-builder-0.58-1.fc37.x86_64 requires rpkg = 3.2-2.fc37 Depending on: trytond (44), status change: 2022-06-16 (2 weeks ago) python-proteus (maintained by: orphan) python-proteus-4.0.2-17.fc35.noarch requires tryton(kernel) = 4.0 trytond-* (maintained by: orphan) all the trytond-* packages depend on trytond they also depend on each other, omitted for brevity see https://churchyard.fedorapeople.org/orphans-2022-07-01.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): alexl: gnome-online-accounts amigadave: gnome-online-accounts besser82: gnome-online-accounts caillon: gnome-online-accounts caolanm: gnome-online-accounts carlwgeorge: golang-github-rubyist-tracerx copr-sig: rpm-git-tag-sort, rpkg-util, rpkg-macros, preproc csmart: gnome-online-accounts cwickert: gnome-online-accounts dcantrell: gpart dturecek: rpm-git-tag-sort, rpkg-util, rpkg-macros, preproc elad: gfbgraph frostyx: rpm-git-tag-sort, rpkg-util, rpkg-macros, preproc gnome-sig: gnome-online-accounts, gfbgraph, gnome-online-miners go-sig: golang-github-rubyist-tracerx hadess: gnome-online-accounts herlo: pam_url ignatenkobrain: gnome-online-accounts jcpunk: gnome-online-accounts jiteshs: gnome-online-accounts kalev: gnome-online-accounts, gfbgraph kathenas: gfbgraph kengert: gnome-online-accounts leigh123linux: gnome-online-accounts limb: gnome-online-accounts magcius: gnome-online-accounts mbarnes: gnome-online-accounts mcrha: gnome-online-accounts mschwendt: gnome-online-accounts oholy: gnome-online-accounts openstack-sig: zuul praiskup: rpm-git-tag-sort, rpkg-util, rpkg-macros, preproc pranvk: gnome-online-accounts, gfbgraph, gnome-online-miners pwalter: gnome-online-accounts qulogic: golang-github-rubyist-tracerx rakesh: gnome-online-accounts rhughes: gnome-online-accounts rishi: gnome-online-accounts rstrode: gnome-online-accounts rtcm: gnome-online-accounts rust-sig: rust-curve25519-dalek salimma: gnome-online-accounts ssp: gnome-online-accounts thm: gnome-online-accounts tpokorra: golang-github-rubyist-tracerx victortoso: gnome-online-accounts zeenix: gfbgraph zuul: zuul -- 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-07-04 11:28:04 UTC

1 0

F37 proposal: GNU Toolchain Update (glibc 2.36, binutils 2.38) (late System-Wide Change proposal)
by Ben Cotton 01 Jul '22

01 Jul '22

https://fedoraproject.org/wiki/Changes/GNUToolchainF37 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 37 GNU Toolchain to glibc 2.36, binutils 2.38. The set of core GNU Toolchain packages for Fedora 37 are as follows: * GNU C Compiler 12 (first released in Fedora 36) ** Associated runtimes for C++ (libstdc++), Go (gccgo), OpenMP (gomp), Fortran (gfortran), D (phobos), Objective C/C++. * GNU Binary Utilities 2.38 (expected release in Fedora 37) * GNU C Library 2.36 (expected release in Fedora 37) * GNU Debugger 12 (immediately available in Fedora 35, 36, and 37) The glibc 2.36 change will be tracked in this top-level GNU Toolchain system-wide update. The binutils 2.38 change will be tracked in this top-level GNU Toolchain system-wide update. == Owner == * Name: [[User:codonell|Carlos O'Donell]] * Email: carlos(a)redhat.com == Detailed Description == The GNU Compiler Collection, GNU C Library, GNU Debugger, and GNU Binary Utilities 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 C Library version 2.36 is expected to be released in the beginning of August 2022; we have started closely tracking the glibc 2.36 development code in Fedora Rawhide and are addressing any issues as they arise. Given the present schedule Fedora 37 will branch after the release of glibc 2.36. However, the mass rebuild schedule means Fedora 37 will mass rebuild (if required) before the final release of glibc 2.36, but after the ABI is frozen. The GNU Binutils version 2.38 was released in February 2022; and we have already been using this version of binutils in Fedora Rawhide successfully to build the distribution. Given the present schedule for Fedora 37 we will continue to use Binutils 2.38 for Fedora 37. == 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 37 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/10865 #10865] * 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 == Any source level changes required for glibc 2.36 will be noted here: https://sourceware.org/glibc/wiki/Release/2.36#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 == == 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 37 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.36 proves too disruptive to compiling the distribution we could revert to 2.35, but given that Rawhide has started tracking glibc 2.36, no show-stopper problems are expected. At this point we can still revert to upstream version 2.35 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.38 proves too distruptive to assembling and linking the distribution we could revert to 2.37, but given that Rawhide is using 2.38, 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 deadline: Fedora mass rebuild on 2022-07-20. * Blocks release? ** Yes, upgrading to glibc 2.36 does block the release. == 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 == The GNU C Library version 2.36 will be released at the beginning of August 2022. 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.38 was released February 2022. The current release notes can be seen here: https://sourceware.org/pipermail/binutils/2022-February/119721.html -- Ben Cotton He / Him / His Fedora Program Manager Red Hat TZ=America/Indiana/Indianapolis

1 0

F37 proposal: Linux Firmware Minimization (late System-Wide Change proposal)
by Ben Cotton 01 Jul '22

01 Jul '22

https://fedoraproject.org/wiki/Changes/Linux_Firmware_Minimization 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 linux-firmware into more subpackages, and add the ability to automatically install firmware based on the hardware present == Owner == * Name: [[User:Salimma|Michel Alexandre Salim]], [[User:Dcavalca|Davide Cavalca]] * Email: michel(a)fb.com, dcavalca(a)fb.com == Detailed Description == The `linux-firmware` RPM is very large (175M src.rpm, 287M *.noarch.rpm per 20211027-126) that bundles most of the system firmware loaded by the kernel, regardless of whether it’s actually needed. Some additional firmwares are already split up into individual subpackages. This change would extend that, splitting out most firmare into appropriate subpackages. The Change would also make the subpackages `Supplements` the appropriate `modalias(...)` for the hardware they support and `Provides` `firmware(kmodname/firmwarefile.bin)` Candidates for splitting out: * CPU firmwares * GPU firmwares * Non-Intel wifi firmwares * Bluetooth firmwares Conversely some firmware could probably be grouped together, e.g. have iwlwifi-firmware that pulls in iwl*-firmware (corresponding to openSUSE's kernel-firmware-iwlwifi). We will also introduce `linux-firmware-all` that will pull in all subpackages; this will make it easier to manage the firmware packages in different Fedora variants. A DNF plugin will be written to make use of the `Supplements` metadata to automatically install the appropriate firmware packages based on the hardware present on the system (see openSUSE's `libzypp`: https://github.com/openSUSE/libzypp/blob/a34d857dbe3b16d4a7e0219cd213cc5a87… and https://github.com/openSUSE/libzypp/blob/7f345ea4892fd02345e8de47c2a08ab5b1…) == Feedback == == Benefit to Fedora == This would save a lot of disk space on Fedora installations, and make it easier to test individual firmware updates by replacing a single subpackage. It will also bring us into alignment with openSUSE (see their [https://code.opensuse.org/package/kernel-firmware/blob/master/f/kernel-firm… kernel-firmware.spec]). == Scope == * Proposal owners: ** Create test COPR with proposed changes ** Add some additional firmware subpackages ** Add the required metadata (supplements, provides) ** Write DNF plugin to make use of supplements ** Write libdnf plugin for PackageKit (and in the future, microdnf) ** refactor [https://pagure.io/fedora-comps/blob/main/f/comps-f37.xml.in#_2887-2903 comps for F37] * Other developers: ** Validate that installation works with iwl*-firmware replaced by iwlwifi-firmware ** Test the DNF plugin ** If it works well, preinstall the DNF plugin and stop installing iwlwifi-firmware or any of the iwl*-firmware * 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 == No compatibility impact. == How To Test == * Enable the test COPR * Verify that after upgrading, no firmware subpackages are removed * Install the DNF plugin * Verify that the DNF plugin works: `dnf mark remove` a firmware package that is needed, then verify that `dnf autoremove` does not remove it * `dnf mark remove` all firmware packages, and verify that `dnf autoremove` only remove the unneeded packages == User Experience == More disk space available, no functional changes. == Dependencies == No dependency, `linux-firmware` is not required by any package == Contingency Plan == * Contingency mechanism: If the plugin is not ready in time, the other changes would preserve the status quo. So we can postpone shipping the DNF plugin to F38. * Contingency deadline:<br>Decide on whether to postpone the DNF plugin by beta freeze * Blocks release? No == Documentation == Documentation will be added in [https://hackmd.io/KnHbJ40pQ8eJjc1H80R10w this HackMD] == Release Notes == -- Ben Cotton He / Him / His Fedora Program Manager Red Hat TZ=America/Indiana/Indianapolis

1 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

devel-announce July 2022