Orphaned packages looking for new maintainers
The following packages are orphaned and will be retired when they are orphaned for six weeks, unless someone adopts them. If you know for sure that the package should be retired, please do so now with a proper reason: https://fedoraproject.org/wiki/How_to_remove_a_package_at_end_of_life Note: If you received this mail directly you (co)maintain one of the affected packages or a package that depends on one. Please adopt the affected package or retire your depending package to avoid broken dependencies, otherwise your package will be retired when the affected package gets retired. Request package ownership via the *Take* button in he left column on https://src.fedoraproject.org/rpms/ Full report available at: https://churchyard.fedorapeople.org/orphans-2020-12-21.txt grep it for your FAS username and follow the dependency chain. For human readable dependency chains, see https://packager.fedorainfracloud.org/ For all orphaned packages, see https://packager.fedorainfracloud.org/orphan Package (co)maintainers Status Change RxCpp orphan 4 weeks ago apache-commons-chain orphan 2 weeks ago apivizlef, orphan 4 weeks ago apper kde-sig, orphan, rhughes 4 weeks ago aseman-qt-tools orphan 0 weeks ago atanuaorphan 3 weeks ago atool lef, orphan 0 weeks ago banshee-community-extensions elsupergomez, orphan, tpokorra 0 weeks ago bfast orphan 4 weeks ago biblesync cicku, orphan4 weeks ago bifcl orphan 4 weeks ago bip adamwill, bcl, orphan2 weeks ago colorhug-client orphan 5 weeks ago cook orphan 4 weeks ago cros-guest-tools orphan 5 weeks ago dc3dd maxamillion, orphan 4 weeks ago dep go-sig, orphan 4 weeks ago dnsjava orphan 4 weeks ago dynaplugz orphan 4 weeks ago edb orphan 4 weeks ago ekiga mcrha, orphan2 weeks ago electric blackfile, orphan4 weeks ago eyesight cicku, orphan, plfiorini 4 weeks ago fifechan orphan 4 weeks ago fillets-ngorphan, thias4 weeks ago flaconignatenkobrain, orphan 4 weeks ago fmpp orphan 4 weeks ago freerdp1.2orphan 3 weeks ago freetiger orphan 4 weeks ago glyr orphan 4 weeks ago gmpc orphan 4 weeks ago gnome-code-assistance elad, orphan 4 weeks ago gnome-documents anujmore, cosimoc, gnome-sig,4 weeks ago orphan gnome-shell-extension-desktop-atim, orphan 2 weeks ago icons gridftp-ifce orphan 4 weeks ago guacamole-server orphan 3 weeks ago icemonorphan 4 weeks ago java-comment-preprocessor hhorak, orphan, panovotn,4 weeks ago praiskup jaxodraw orphan 4 weeks ago jblas orphan 4 weeks ago jboss-servlet-2.5-api dmoluguw, orphan 4 weeks ago jfontchooser orphan 4 weeks ago jgraphx jerboaa, orphan 5 weeks ago jgroups gil, goldmann, lef, orphan 4 weeks ago jing-trangorphan 4 weeks ago jnettop orphan 4 weeks ago js-html5shiv orphan 4 weeks ago js-jquery-file-upload
Re: Upcoming Fedora 34 deadlines
As a reminder, Fedora 34 Change proposals for System-Wide Changes or Changes requiring a mass rebuild are due on Tuesday 29 December. Self-contained Change proposals are due on 19 January. The full Fedora 34 schedule is on Fedora People: https://fedorapeople.org/groups/schedule/f-34/f-34-key-tasks.html I will be out of the office from 23 December until 4 January. I will check email and look for submitted proposals occasionally, but if you have a pressing question, please ping me on IRC (bcotton)/Matrix (@funnelfiasco:matrix.org). -- Ben Cotton He / Him / His Senior Program Manager, Fedora & CentOS Stream Red Hat TZ=America/Indiana/Indianapolis ___ devel-announce mailing list -- devel-announce@lists.fedoraproject.org To unsubscribe send an email to devel-announce-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel-announce@lists.fedoraproject.org
Fedora 34 Change: Enable systemd-oomd by default for all variants (System-Wide Change)
https://fedoraproject.org/wiki/Changes/EnableSystemdOomd == Summary == Provide a better experience for Fedora users in out-of-memory (OOM) situations by enabling [https://www.freedesktop.org/software/systemd/man/systemd-oomd.html systemd-oomd] by default. Actions taken by systemd-oomd operate on a per-cgroup level, aligning well with the life cycle of systemd units. systemd-oomd primarily uses [https://facebookmicrosites.github.io/psi/ Linux pressure stall information (PSI)] to make decisions based on wasted productivity due to resource shortages; in addition to that, it also supports swap based actions. == Owners == * Name: [[User:anitazha|Anita Zhang]], [[User:Dcavalca|Davide Cavalca]], [[User:Salimma|Michel Salim]], [[User:Htejun|Tejun Heo]], [[User:3ki|Rik van Riel]] * Email: the.anita...@gmail.com, dcava...@fb.com, mic...@michel-slm.name, hte...@fb.com, r...@fb.com == Detailed description == The primary mechanism used by systemd-oomd for detecting when the system is out of memory is memory pressure. Memory pressure measures the percentage of time a cgroup has “wasted” due to lack of memory. This includes time spent reclaiming free memory, faulting in recently resident pages, and loading in anonymous pages from swap. When a monitored cgroup’s memory pressure exceeds the specified thresholds, systemd-oomd will perform action(s) on the targeted cgroup’s descendants, starting from the cgroups with the most reclaim scans. Reclaim activity is used here, rather than the largest consumer, as it reflects values set in the cgroup memory controller for memory protection (such as memory.low). For memory pressure configuration, this will be ManagedOOMMemoryPressure=kill and ManagedOOMMemoryPressureLimit=4% on user@.service to have systemd-oomd send SIGKILLs to all processes under a selected cgroup when total memory pressure on all tasks exceeds 4% for 10 seconds. For swap based actions, systemd-oomd will monitor the system-wide swap space and act when available swap falls below the configured threshold, starting with the cgroups with the highest swap usage to the least. Keeping some amount of swap (if enabled) available will prevent the kernel OOM killer from killing processes unpredictably and spending an unbounded amount of time afterwards. For swap configuration, this will be SwapUsedLimitPercent=90% in oomd.conf and ManagedOOMSwap=kill on -.slice (root cgroup slice) to have systemd-oomd send SIGKILLs to all processes under a cgroup when swap used exceeds 90%. == Benefit to Fedora == * Addressing the issue of improving user feedback in https://pagure.io/fedora-workstation/issue/202, systemd-oomd currently logs to the journal if pressure or swap action is about to occur. There are also debug logs, for each process that is sent a SIGKILL, that can be bumped up in priority. Further notification mechanisms (i.e. over dbus) can also be implemented depending on feedback. * While systemd-oomd is simpler in configuration to the oomd used at Facebook, the algorithm is largely the same. As such, the following case study can be used as an example of how PSI and cgroup killing can release memory not normally resolved with process killing and lead to better utilization: https://facebookincubator.github.io/oomd/docs/oomd-casestudy.html * OOM killing in userspace, before the kernel OOM killer kicks in, has been shown to be effective at keeping a system functional. An OOM kill in the kernel is slow, possibly leading to an unbounded amount of time swapping in and out pages and evicting the page cache. * PSI based actions, versus looking at raw memory consumption numbers, better reflect memory protection policies set for cgroup resource control limits (e.g. memory.low). == Scope == * Proposal owners: ** Implement and land additional refinements to systemd-oomd *** Remove swap as a hard requirement to running systemd-oomd *** Expand ManagedOOM*= properties to user units (currently only usable on system units) *** Configurable memory pressure time window knob ** Enable oomd by default with sensible configuration ** Test days ** Aid with documentation * Other developers: ** systemd: review PRs as needed * Release engineering: https://pagure.io/releng/issue/9913 * Policies and guidelines: N/A * Trademark approval: N/A == Upgrade/compatibility impact == Existing systems running earlyoom will not be modified. One can transition to systemd-oomd via: sudo systemctl disable --now earlyoom sudo systemctl enable --now systemd-oomd Systems that were previously not running earlyoom will have systemd-oomd enabled by default. == How to test == systemd 247 build for Fedora includes all the artifacts for systemd-oomd. It is disabled by default but can be started with: sudo systemctl enable --now systemd-oomd At this point you can decide which units to set properties on. For example, to enable swap-based killing on all units below the root slice: sudo systemctl edit --force -- -.slice [Slice] ManagedOOMSwap=kill # save and
