devel June 2022

devel@lists.fedoraproject.org

201 participants
307 discussions

F37 Change Proposal: Unfiltered Flathub (System-Wide Change)
by Vipul Siddharth 13 Jul '22

13 Jul '22

26 55

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

13 Jul '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

8 13

Upcoming F37 deadlines
by Ben Cotton 12 Jul '22

12 Jul '22

As a reminder, several Fedora Linux 37 deadlines are approaching: * 2022-06-22 — Change proposals requiring infrastructure changes due * 2022-06-28 — System-Wide Change proposals and proposals requiring a mass rebuild due * 2022-07-19 — Self-Contained Change proposals due For the full schedule, see https://fedorapeople.org/groups/schedule/f-37/f-37-key-tasks.html -- Ben Cotton He / Him / His Fedora Program Manager Red Hat TZ=America/Indiana/Indianapolis _______________________________________________ devel-announce mailing list -- devel-announce(a)lists.fedoraproject.org To unsubscribe send an email to devel-announce-leave(a)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.fedorapr… Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure

1 2

F37 proposal: Stratis 3.1.0 (Self-Contained change)
by Vipul Siddharth 11 Jul '22

11 Jul '22

https://fedoraproject.org/wiki/Changes/Stratis_3.1.0 This document represents a proposed Change. As part of the Changes process, proposals are publicly announced in order to receive community feedback. This proposal will only be implemented if approved by the Fedora Engineering Steering Committee. == Summary == Stratis 3.1.0 includes significant improvements to the management of the thin-provisioning layers, as well as a number of other user-visible enhancements and bug fixes. == Owner == * Name: ** [[User:dkeefe|Dennis Keefe]] ** [[User:mulhern|Anne Mulhern]] ** [[User:jbaublitz|John Baublitz]] * Email: ** dkeefe(a)redhat.com ** amulhern(a)redhat.com ** jbaublitz(a)redhat.com == Detailed Description == Stratis 3.1.0 includes significant improvements to the management of the thin-provisioning layers, as well as a number of other user-visible enhancements and bug fixes. Please see this [https://stratis-storage.github.io/thin-provisioning-redesign/ post] for a detailed discussion of the thin-provisioning changes. To support these changes the Stratis CLI has been enhanced to: * allow specifying whether or not a pool may be overprovisioned on creation * allow changing whether or not a pool may be overprovisioned while it is running * allow increasing the filesystem limit for a given pool * display whether or not a pool is overprovisioned in the pool list view Users of the Stratis CLI may also observe the following changes: * A `debug` subcommand has been added to the `pool`, `filesystem`, and `blockdev` subcommands. Debug commands are not fully supported and may change or be removed at any time. * The `--redundancy` option is no longer available when creating a pool. This option had only one permitted value so specifying it never had any effect. stratisd 3.1.0 includes one additional user-visible change: * The minimum size of a Stratis filesystem is increased to 512 MiB. stratisd 3.1.0 also includes a number of internal improvements: * The size of any newly created MDV is increased to 512 MiB. * A pool's MDV is mounted in a private mount namespace and remains mounted while the pool is in operation. * Improved handling of udev events on device removal. * The usual and customary improvements to log messages. Please consult the [https://github.com/stratis-storage/stratisd/blob/master/CHANGES.txt/ stratisd] and [https://github.com/stratis-storage/stratis-cli/blob/master/CHANGES.txt/ stratis-cli] changelogs for additional information about the 3.1.0 release. == Benefit to Fedora == Users of Fedora will now benefit from Stratis 3.1.0 by: * Change the overprovisioning mode at create time or while running * User can increase the limit of filesystems per pool. The default is 100. * Stratis pool list will display whether or not a pool is overprovisioned * The MDV size is now 512MB, which allows for more filesystems to be created per pool * MDV is now in a private mount namespace, which decreases logging events and user may see faster completion times for commands that required the MDV to be mounted. == Scope == * Proposal owners: ** Update existing stratis-cli package to specify new release ** Update existing stratisd package to specify new release * Other developers: N/A * Release engineering: Self Contained * Policies guidelines: N/A * Trademark approval: N/A == How To Test == * To see the `overprovisioning` field, list the pools `stratis pool list` overprovisioned will equal `OP`, no overprovisioning will equal `~OP` * To set the filesystem limit of a pool: `stratis pool set-fs-limit p1 200` * To see what the filesystem limit is `stratis report engine_state_report` Look for field `fs_limit` in output == User Experience == Other than the changes mentioned above the user experience will be the same. == Dependencies == No new dependencies == Contingency Plan == * Contingency mechanism: * Contingency deadline: N/A * Blocks release? No * Blocks product? No == Documentation == * This content can be viewed on Developer’s [https://stratis-storage.github.io/thin-provisioning-redesign/ blog] for Stratis 3.1 * Thin-provisioning [https://stratis-storage.github.io/thin-provisioning-redesign/ blog] * [https://github.com/stratis-storage/stratisd/blob/master/CHANGES.txt/ stratisd] changelog * [https://github.com/stratis-storage/stratis-cli/blob/master/CHANGES.txt/ stratis-cli] changelog == Release Notes == [https://stratis-storage.github.io/stratis-release-notes-3-1-0/ Stratis Release Notes] -- Vipul Siddharth He/His/Him Fedora | CentOS CI Infrastructure Team

2 1

About Fedora containers
by Alejandro Saez Morollon 11 Jul '22

11 Jul '22

Hi all! TL;DR: Is there any documentation about how to properly take care of our containers? :) --- The Go container has been outdated for a while, and I would love to update it[0], but I'm not familiar with the container process in Fedora. I checked Python3's container[1] looking for information, and I saw that the rawhide branch is not used in the same way we use it with the RPMs. Also, I saw that the s2i-base image is only available until F35. No F36 or Rawhide. And, it looks like they are only available for x86_64 platforms. So I guess the main big question is: is there any documentation or proposals I should be aware of? Is the Go container relevant? cc'ed Container SIG's mailing list; I didn't see movement in the mailing list, just in case. [0] https://src.fedoraproject.org/container/golang [1] https://src.fedoraproject.org/container/python3 Thank you very much!

10 12

Rename Airspy
by Buford T. Justice 11 Jul '22

11 Jul '22

For the regular Airspy (not HF+), why is the package called "airspyone_host"? All other distros just call it "airspy": https://pkgs.org/search/?q=airspy So it would be nice to simply do: sudo dnf install airspy airspyhf To have support in Fedora for both Airspy and Airspy HF+.

3 4

Request: Airspy HF+
by Buford T. Justice 11 Jul '22

11 Jul '22

Would it be possible to get Airspy HF+ support for Fedora? Many other distros have it: https://pkgs.org/search/?q=airspyhf THANKS!!!

6 12

[Reminder] CfP open for Nest with Fedora
by Marie Nordin 08 Jul '22

08 Jul '22

Hi there Fedorans, It's time to submit your proposals for Nest with Fedora! The event will be held virtually on August 4th, 5th, and 6th. This is a great opportunity to share what you have been doing in the project and connect with your fellow Fedorans :) *The final deadline for the CfP is July 8th. * *Submit your proposals on the Flock pagure repo:* https://pagure.io/flock/issues *More info about the CfP:* https://communityblog.fedoraproject.org/nest-2022-cfp/ *More info about Nest: * https://communityblog.fedoraproject.org/nest-with-fedora-fedora-hatch-annou… Can't wait to see your proposals! Best, -- 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> _______________________________________________ devel-announce mailing list -- devel-announce(a)lists.fedoraproject.org To unsubscribe send an email to devel-announce-leave(a)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.fedorapr… Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure

1 1

Anyone want to review swap? (rocm-opencl)
by Jeremy Newton 06 Jul '22

06 Jul '22

I'm looking to see if anyone wants to review swap with me: https://bugzilla.redhat.com/show_bug.cgi?id=2090823 Thanks!

2 2

F37 change proposal: Make Fedora CoreOS a Fedora Edition (System-Wide change)
by Vipul Siddharth 06 Jul '22

06 Jul '22

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 == This change is to promote Fedora CoreOS to Edition status alongside Workstation, Server and IoT. == Owners == * Name: [[User:cverna|Clement Verna]] * Email: cverna(a)fedoraproject.org * Products: Fedora CoreOS * Responsible WGs: Fedora CoreOS Group == Detailed Description == This change is to promote Fedora CoreOS to Edition status alongside Workstation, Server and IoT. [https://fedoraproject.org/wiki/Editions/Promotion_Process#Prerequisites Prerequisites] are tracked bellow : * Edition has a team with regular public meeting : [https://apps.fedoraproject.org/calendar/meeting/9437/ weekly meeting happening on #fedora-meeting-1] * Trademark approval from the Fedora Council : [https://pagure.io/Fedora-Council/tickets/issue/340 council ticket] * Product requirements document (PRD) : https://fedoraproject.org/wiki/CoreOS/PRD * Technical specification : https://github.com/coreos/fedora-coreos-tracker/blob/master/Design.md == Feedback == This change was previously submitted for Fedora 34 and feedback were collected in the following [https://pagure.io/fesco/issue/2516 FESCo ticket]. The 2 main feedback received are either addressed or in the process of being addressed. * FCOS should not trail behind the latest Major Fedora version: see [[https://fedoraproject.org/wiki/Changes/FedoraCoreOS#Major_Fedora_Version_re… Fedora Version release Go/NoGo criteria]] * FCOS should demonstrate the test case mapping to the Basic Release Criteria: see [[https://fedoraproject.org/wiki/Changes/FedoraCoreOS#Basic_Release_Criteria|… Release Criteria]] == Benefit to Fedora == Make Fedora CoreOS an official edition, will help spread adoption and position Fedora as credible solution for running container workflow. We have started to publish monthly update of what is happening in Fedora CoreOS based on the feedback received from [https://discussion.fedoraproject.org/t/fedora-coreos-survey/34408/2 a community survey]. Part of these monthly update are [https://discussion.fedoraproject.org/t/this-month-in-fedora-coreos-may-2022… the count me stats] which gives us a good understanding of FCOS adoption. == Scope == * Proposal owners: see change owners * Other developers: N/A * Release engineering: Fedora CoreOS is already being composed and released. * Policies and guidelines: N/A * Trademark approval: https://pagure.io/Fedora-Council/tickets/issue/340 == How To Test == See QA test cases : https://fedoraproject.org/wiki/Category:CoreOS_Test_Cases and Fedora CoreOS own test suite Kola https://github.com/coreos/coreos-assembler/blob/main/docs/kola.md#testing-w… We also have regular tests days, for example https://fedoramagazine.org/fedora-coreos-test-day/ === Basic Release Criteria === We are currently evaluating our compliance to the Fedora Basic Release Criteria https://github.com/coreos/fedora-coreos-tracker/issues/1239. This is an effort that will be done during the Fedora 37 development cycle. ==== Supported Architecture and Platforms ==== Fedora CoreOS is currently built for the x86_64, aarch64 and s390x architecture, These [https://docs.fedoraproject.org/en-US/fedora-coreos/platforms/#_well_known_i… platforms] are supported and can be configured directly using Ignition. The [https://github.com/coreos/mantle/tree/cl/kola kola] test suite is run for each stream release on AWS, Azure, GCP and OpenStack. ==== Stream release Go/NoGo ==== Stream releases are scheduled fortnightly, a GitHub issue ([https://github.com/coreos/fedora-coreos-streams/issues/242 example]) is created for each stream release with the release process. The release status can be tracked in each ticket. If each steps and validation were successful the release is considered GO. Issues are reported in the [https://github.com/coreos/fedora-coreos-tracker issue tracker] and discussed during the weekly [https://github.com/coreos/fedora-coreos-tracker#meetings IRC meeting]. A stream release can become a NOGO during these meeting, the blocker issue is then linked to the release GitHub issue. ==== Major Fedora Version release Go/NoGo ==== The policies around the Major version rebases are described in Fedora CoreOS document https://github.com/coreos/fedora-coreos-tracker/blob/main/Design.md#major-f… (see copy below) The release process integrates with Fedora's release milestones in the following ways: Fedora Beta Release The next stream is switched over to the new release. Fedora Final Freeze The next stream switches to weekly releases to closely track the GA content set. Fedora General Availability Fedora CoreOS re-orients its release schedule in the following way: Week -1 (Fedora "Go" Decision): next release: next release with final Fedora GA content Week 0 (GA release): triple release: testing release promoted from previous next next release contains latest Fedora N content, including Bodhi updates Week 2: triple release: stable release promoted from previous testing, now fully rebased to Fedora N testing and next are now in sync == Contingency Plan == Contingency mechanism: (What to do? Who will do it?) Delay promotion until F38 Contingency deadline: F37 Final release date Blocks release? No == Documentation == https://docs.fedoraproject.org/en-US/fedora-coreos/ -- Vipul Siddharth He/His/Him FPgM team member

6 8

← Newer
1
2
3
4
5
6
7
8
...
31
Older →

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

devel June 2022