devel-announce March 2022

devel-announce@lists.fedoraproject.org

4 participants
14 discussions

F37 Change: Encourage Dropping Unused / Leaf Packages on i686 (Self-Contained Change proposal)
by Ben Cotton 07 Mar '22

07 Mar '22

https://fedoraproject.org/wiki/Changes/EncourageI686LeafRemoval == Summary == Package maintainers are encouraged to actively stop building their packages for i686, especially if supporting this architecture requires significant investment of time or resources, for no benefit. This will not apply to packages which are still depended on by other i686 packages, or which get used in a "multilib" context (i.e. for running 32-bit applications on x86_64). == Owner == * Name: [[User:Decathorpe| Fabio Valentini]] * Email: decathorpe [AT] gmail [DOT] com == Detailed Description == Fedora does no longer ship any deliverables for i686, not even RPM repositories for i686 are published any longer. The kernel package itself also [[Changes/Stop Building i686 Kernels|dropped support for i686]] in Fedora 31, so there has not been any way to run Fedora on 32-bit x86 systems for years. Only a tiny fraction of all packages that are built on i686 are actually used (i.e. "multilib" support for Wine, Steam, etc. on x86_64). == Feedback == (none yet) == Benefit to Fedora == Stopping to run unnecessary package builds on i686 will free up no small amount of resources. In particular, stopping to build for i686 could potentially free up almost half of the existing x86 builder resources in koji. Additionally, support for building on 32-bit targets is starting to get dropped by upstream projects, and resource constraints of 32-bit architectures (i.e. per-process and total memory limits) also make building large libraries or applications increasingly difficult. With ARMv7 support having been removed from Fedora 37 already, i686 is the only remaining supported 32-bit architecture. Encouraging package maintainers to drop i686 support from their packages (if possible), instead of requiring them to work around those resource constraints or missing upstream support, will significantly lower the maintenance burden, especially for some problematic packages. == Scope == * Proposal owners: Proposal owners will provide convenience scripts for checking whether a given package is a leaf package on i686, and will help with identifying potential candidate packages. * Other developers: Package maintainers who are affected by 32-bit architecture / i686 specific problems are encouraged to investigate dropping support for i686 entirely, instead of having to invest time to fix or work around those issues, for very little benefit to Fedora. This can be done incrementally, as dropping support for i686 from some packages will in turn make other packages leaves on i686. * Release engineering: N/A There are already no deliverables for i686, so there should be no impact on Release engineering. * Policies and guidelines: Packages that drop support for i686 will no longer need to file a tracking bug and block the [https://bugzilla.redhat.com/show_bug.cgi?id=179258 32-bit x86 ExcludeArch tracker bug]. * Trademark approval: N/A (not needed for this Change) * Alignment with Objectives: N/A == Upgrade/compatibility impact == This Change only affects unused / leaf packages that are never installed on user systems (particularly because it has not been possible to install i686-based Fedora for years). == How To Test == The remaining use cases of i686 packages (i.e. "multilib") for popular 32-bit applications should continue to work. For example, installing the Steam client (steam.i686), Wine, or other applications that require 32-bit compatibility libraries should still be possible, and not fail due to broken dependencies. == User Experience == N/A == Dependencies == N/A == Contingency Plan == This Change is supposed to only affect unused components / leaf packages. However, if a package maintainer accidentally stops building a package on i686 despite it still being required for something else, this should be easy to revert - by adding back i686 architecture support to the affected packages, in reverse order. Since removal of support for i686 will happen slowly and incrementally, this should be relatively straightforward. * Contingency deadline: N/A (not a System Wide Change) * Blocks release? N/A (not a System Wide Change) == Documentation == N/A (not a System Wide Change) == Release Notes == Fedora packages will incrementally drop support for the i686 architecture (32-bit x86), where this support is no longer required. This is intended to reduce resource consumption of build servers. Additionally, it will make package maintenance for Fedora easier, because a growing number of projects already either no longer provide support for - or fail to build due to resource constraints on - 32-bit architectures. -- Ben Cotton He / Him / His Fedora Program Manager Red Hat TZ=America/Indiana/Indianapolis

1 0

F37 Change: Drop i686 builds of jdk8,11,17 and latest (18) rpms from f37 onwards (System-Wide Change)
by Ben Cotton 07 Mar '22

07 Mar '22

https://fedoraproject.org/wiki/Changes/Drop_i686_JDKs == Summary == java-1.8.0-openjdk, java-11-openjdk, java-17-openjdk and java-latest-openjdk packages will no longer build i686 subpackages == Owner == * Name: [[User:jvanek| Jiri Vanek]] * Email: <jvanek(a)redhat.com> * Product: java and java stack * Responsible WG: java-sig (java and java-maint)(which no longer exists) === Expected schedule === * during march, drop i686 builds from all jdks in fedora rawhide == Detailed Description == Fedora currently ships: * java-1.8.0-openjdk (LTS) * java-11-openjdk (LTS) * java-17-openjdk (LTS) * java-latest-openjdk (STS, jdk18). All those builds on all architectures except jdk8, where arm32 with jit is built by different package. Unluckily, the i686 bit builds of jdk are rotten in upstream. The recent breakage of i686 JIT just before branching nearly killed jdk17 as system jdk feature. The rotting have main visibility with newer GCCs. If GCC bump, and it does, it always triggers new issues in i686 JIT, and there is less and less people to somehow workaround them. Unluckily, there is probably no longer anyone willing to really fix them == Benefit to Fedora == The i686 builds are rotten in usptream, and to patch them localy had become pain. We may be introducing very bugy i686 jdk. Better then to do so, we would rather not ship that at all. This will untie hands of both JDK and GCC developers, who will no longer need to dive into nasty legacy code. == Scope == ==== Change owners ==== * we will simiply stop building i686 pkg in rawhide ==== Other developers ==== * may notice the multilib i686 java missing. * it is up to them to drop i686 builds or to povide workaround (if possible) ==== Other ==== * Release engineering: https://pagure.io/releng/issue/10686 * Trademark approval: N/A (not needed for this Change) == Upgrade/compatibility impact == * The upgrade on multilib systems will lead to autoremoval of i686 javastack * which should be minimum - 99% of javastack is noarch == How To Test == install i686 java will result to not packages found == User Experience == User experience on multilib systems will be bad. Bad reasonable. == Dependencies == There are is unknown number of multilib java consumers. I expect some of them may rise voice, but that will have to handled one by one. == Contingency Plan == * Contingency mechanism: return i686 packages * Contingency date: (not provided) == Documentation == Will be neded... == Release Notes == None yet... -- Ben Cotton He / Him / His Fedora Program Manager Red Hat TZ=America/Indiana/Indianapolis

1 0

Orphaned packages looking for new maintainers
by Miro Hrončok 07 Mar '22

07 Mar '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-03-07.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 ================================================================================ augeas-vala orphan 1 weeks ago beanstalk-client orphan 0 weeks ago bmap-tools orphan 0 weeks ago deltarpm jdieter, orphan 0 weeks ago ghc-dbus orphan 0 weeks ago ghc-libxml-sax orphan 0 weeks ago gimp-fourier-plugin orphan 1 weeks ago gocl orphan 1 weeks ago javahelp2 orphan 3 weeks ago linenoise orphan 0 weeks ago lua-ldap orphan 0 weeks ago nautilus-image-converter orphan, timj 4 weeks ago nodejs-backbone nodejs-sig, orphan, vjancik 0 weeks ago php-pecl-datadog_trace orphan 5 weeks ago python-aiohttp-cors orphan, python-sig 0 weeks ago python-aiohttp-negotiate orphan 0 weeks ago python-blessings orphan 0 weeks ago python-fastimport orphan 0 weeks ago python-hkdf orphan 1 weeks ago python-lrparsing orphan 0 weeks ago python-magic-wormhole orphan 1 weeks ago python-magic-wormhole-mailbox- orphan 1 weeks ago server python-magic-wormhole-transit- orphan 1 weeks ago relay python-ofxparse orphan 0 weeks ago python-phonenumbers orphan 0 weeks ago python-plyvel orphan 0 weeks ago python-pystalk orphan 0 weeks ago python-spake2 orphan 1 weeks ago python-txtorcon orphan 1 weeks ago python-uinput orphan 1 weeks ago python-unidiff orphan 0 weeks ago qcommandline orphan 0 weeks ago rpg-cli orphan, rust-sig 3 weeks ago rubygem-database_cleaner orphan 2 weeks ago rubygem-ruby-ntlm orphan 5 weeks ago ssh-contact orphan 4 weeks ago telepathy-farstream orphan 4 weeks ago telepathy-idle orphan 4 weeks ago telepathy-logger orphan, rishi 4 weeks ago vorbisgain orphan 4 weeks ago w_scan orphan 3 weeks ago xorg-sgml-doctools airlied, ajax, alexl, caillon, 5 weeks ago caolanm, glisse, mbarnes, orphan, rhughes, rstrode, slaanesh, ssp, whot xorg-x11-docs airlied, ajax, alexl, caillon, 5 weeks ago caolanm, glisse, mbarnes, orphan, rhughes, rstrode, slaanesh, ssp, whot xorg-x11-drv-sisusb airlied, ajax, alexl, caillon, 5 weeks ago caolanm, glisse, mbarnes, orphan, rhughes, rstrode, ssp, whot xorg-x11-drv-v4l airlied, ajax, alexl, caillon, 5 weeks ago caolanm, glisse, mbarnes, mchehab, orphan, rhughes, rstrode, ssp, whot xorg-x11-twm airlied, ajax, alexl, caillon, 5 weeks ago caolanm, glisse, mbarnes, orphan, rhughes, rstrode, slaanesh, ssp, whot xorg-x11-xdm airlied, ajax, alexl, caillon, 5 weeks ago caolanm, glisse, mbarnes, orphan, rhughes, rstrode, ssp, whot xorg-x11-xfs airlied, ajax, alexl, caillon, 5 weeks ago caolanm, glisse, mbarnes, orphan, rhughes, rstrode, slaanesh, ssp, whot xorg-x11-xsm airlied, ajax, alexl, caillon, 5 weeks ago caolanm, glisse, mbarnes, orphan, rhughes, rstrode, ssp, whot The following packages require above mentioned packages: Report too long, see the full version at https://churchyard.fedorapeople.org/orphans-2022-03-07.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): airlied: xorg-x11-drv-sisusb, xorg-sgml-doctools, xorg-x11-xdm, xorg-x11-drv-v4l, xorg-x11-twm, xorg-x11-xfs, xorg-x11-xsm, xorg-x11-docs ajax: xorg-x11-drv-sisusb, xorg-sgml-doctools, xorg-x11-xdm, xorg-x11-drv-v4l, xorg-x11-twm, xorg-x11-xfs, xorg-x11-xsm, xorg-x11-docs alexl: xorg-x11-drv-sisusb, xorg-sgml-doctools, xorg-x11-xdm, xorg-x11-drv-v4l, xorg-x11-twm, xorg-x11-xfs, xorg-x11-xsm, xorg-x11-docs ankursinha: nodejs-backbone, ghc-dbus bowlofeggs: nodejs-backbone caillon: xorg-x11-drv-sisusb, xorg-sgml-doctools, xorg-x11-xdm, xorg-x11-drv-v4l, xorg-x11-twm, xorg-x11-xfs, xorg-x11-xsm, xorg-x11-docs caolanm: xorg-x11-drv-sisusb, xorg-sgml-doctools, xorg-x11-xdm, xorg-x11-drv-v4l, xorg-x11-twm, xorg-x11-xfs, xorg-x11-xsm, xorg-x11-docs chimosky: xorg-x11-drv-sisusb churchyard: nodejs-backbone csomh: python-unidiff cstratak: nodejs-backbone dcallagh: python-phonenumbers dcantrell: nodejs-backbone dcavalca: nodejs-backbone defolos: deltarpm dkrejci: nodejs-backbone dvratil: telepathy-logger, telepathy-farstream ellert: nodejs-backbone epel-packagers-sig: nodejs-backbone fab: nodejs-backbone filbranden: nodejs-backbone fmuellner: telepathy-logger, telepathy-idle fnecas: python-unidiff gbcox: telepathy-farstream glisse: xorg-x11-drv-sisusb, xorg-sgml-doctools, xorg-x11-xdm, xorg-x11-drv-v4l, xorg-x11-twm, xorg-x11-xfs, xorg-x11-xsm, xorg-x11-docs gnome-sig: telepathy-logger, telepathy-idle hguemar: deltarpm hno: nodejs-backbone ignatenkobrain: nodejs-backbone jamatos: nodejs-backbone jcline: nodejs-backbone jdieter: deltarpm jgrulich: telepathy-logger, telepathy-farstream jjames: nodejs-backbone jpopelka: python-unidiff jreznik: telepathy-logger, telepathy-farstream jscotka: python-unidiff kalev: nodejs-backbone kde-sig: telepathy-logger, telepathy-farstream ksurma: nodejs-backbone kwizart: python-aiohttp-cors lachmanfrantisek: python-unidiff lbalhar: nodejs-backbone lbarczio: python-unidiff lbazan: ghc-dbus lkundrak: nodejs-backbone maha: nodejs-backbone mathstuf: ghc-dbus maxamillion: python-blessings, nodejs-backbone mbaldessari: nodejs-backbone mbarnes: xorg-x11-drv-sisusb, xorg-sgml-doctools, xorg-x11-xdm, xorg-x11-drv-v4l, xorg-x11-twm, xorg-x11-xfs, xorg-x11-xsm, xorg-x11-docs mchehab: xorg-x11-drv-v4l mck182: telepathy-logger, telepathy-farstream mfocko: python-unidiff mrunge: nodejs-backbone msuchy: deltarpm neuro-sig: nodejs-backbone, ghc-dbus nforro: python-unidiff ngompa: deltarpm nodejs-sig: nodejs-backbone nonamedotc: nodejs-backbone nucleo: python-aiohttp-cors, telepathy-farstream orion: nodejs-backbone packit: python-unidiff pbrobinson: xorg-x11-drv-sisusb pcpa: nodejs-backbone petersen: ghc-dbus phracek: python-unidiff python-sig: python-aiohttp-cors, nodejs-backbone qulogic: nodejs-backbone, ghc-dbus rathann: nodejs-backbone rdieter: telepathy-logger, telepathy-farstream rebus: nodejs-backbone ret2libc: nodejs-backbone rhughes: xorg-x11-drv-sisusb, xorg-sgml-doctools, xorg-x11-xdm, xorg-x11-drv-v4l, xorg-x11-twm, xorg-x11-xfs, xorg-x11-xsm, xorg-x11-docs rishi: telepathy-logger rkuska: python-blessings rstrode: xorg-x11-drv-sisusb, xorg-sgml-doctools, xorg-x11-xdm, xorg-x11-drv-v4l, xorg-x11-twm, xorg-x11-xfs, xorg-x11-xsm, xorg-x11-docs rust-sig: rpg-cli sagitter: nodejs-backbone salimma: python-blessings, nodejs-backbone sergiopr: nodejs-backbone slaanesh: xorg-sgml-doctools, xorg-x11-twm, xorg-x11-xfs, xorg-x11-docs slankes: telepathy-farstream ssp: xorg-x11-drv-sisusb, xorg-sgml-doctools, xorg-x11-xdm, xorg-x11-drv-v4l, xorg-x11-twm, xorg-x11-xfs, xorg-x11-xsm, xorg-x11-docs tejas: telepathy-farstream terjeros: python-blessings thozza: nodejs-backbone timj: nautilus-image-converter tomspur: nodejs-backbone ttomecek: python-unidiff usercont: python-unidiff v02460: python-phonenumbers vjancik: nodejs-backbone whot: xorg-x11-drv-sisusb, xorg-sgml-doctools, xorg-x11-xdm, xorg-x11-drv-v4l, xorg-x11-twm, xorg-x11-xfs, xorg-x11-xsm, xorg-x11-docs zbyszek: nodejs-backbone zdohnal: nodejs-backbone -- 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-03-07 09:28:42 UTC

1 0

Fedora Linux 36 Beta Go/No-Go meeting next week
by Ben Cotton 02 Mar '22

02 Mar '22

Hi everyone, It's that time already! The Fedora Linux 36 Beta Go/No-Go[1] meeting is scheduled for Thursday 10 March at 1700 UTC in #fedora-meeting. At this time, we will determine the status of the F36 Beta for the 15 March early target date[2]. For more information about the Go/No-Go meeting, see the wiki[3]. [1] https://calendar.fedoraproject.org/meeting/10209/ [2] https://fedorapeople.org/groups/schedule/f-36/f-36-key-tasks.html [3] https://fedoraproject.org/wiki/Go_No_Go_Meeting -- Ben Cotton He / Him / His Fedora Program Manager Red Hat TZ=America/Indiana/Indianapolis

1 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

devel-announce March 2022