F39 proposal: Remove webkit2gtk-4.0 API Version (System-Wide Change proposal)
https://fedoraproject.org/wiki/Changes/Remove_webkit2gtk-4.0_API_Version 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 webkit2gtk-4.0 API version will no longer be built. Packages that depend on it will fail to build from source and eventually be retired. == Owner == * Name: [[User:catanzaro|Michael Catanzaro]] * Email: == Detailed Description == The webkitgtk source package currently provides three different API versions of WebKitGTK: * webkit2gtk-4.0: for GTK 3 and libsoup 2 * webkit2gtk-4.1: for GTK 3 and libsoup 3 * webkitgtk-6.0: for GTK 4 and libsoup 3 Building three different package versions is slow, and Red Hat does not wish to do so anymore. We will remove the webkit2gtk-4.0 API version, which is provided by the webkit2gtk4.0 and javascriptcoregtk4.0 packages. Everything that depends on these packages will fail to build from source and will eventually be removed from the distribution unless fixed. The good news is that updating your package to webkit2gtk-4.1 is probably easy because there are no API changes other than the version of libsoup that is linked to. If your package does not directly or indirectly depend on libsoup 2, then just change the API version number from 4.0 to 4.1 and you're done. [https://src.fedoraproject.org/rpms/emacs/c/1670e57f63e0897d6d6027826f247bb3e90ddd2a?branch=rawhide Here is a typical example of how easy this is.] However, if your package does directly or indirectly depend on libsoup 2, then you will need to eliminate that dependency, which will require more effort. If your application links to libsoup 2 via any dependency, it will crash if also linked to libsoup 3. This is a slimmed-down version of the [[Changes/libsoup_3:_Part_Two|libsoup 3: Part Two]] change proposal that was previously rejected by FESCo. Instead of removing all packages that depend on libsoup 2, packages will only be removed if they depend on both libsoup 2 and also WebKitGTK. No effort will be made to remove libsoup 2 from the distribution (though an obsolete HTTP library is a major security risk and packages really ought to stop using it). == Benefit to Fedora == libsoup 3 brings support for HTTP/2, whereas libsoup 2 supports only HTTP/1.1. Users will experience shorter load times and improved responsiveness in applications that use WebKitGTK. Users of applications that previously used webkit2gtk-4.0 will have one fewer massive package installed after this transition is completed. Additionally, the WebKitGTK package maintainer will be less grumpy because WebKitGTK will need to be built only twice for each supported version of Fedora, rather than three times. == Scope == * Proposal owners: ensure packages required by Fedora Workstation and ELN no longer depend on webkit2gtk-4.0 (already done) * Other developers: ensure other packages no longer depend on webkit2gtk-4.0 * Release engineering: [https://pagure.io/releng/issue/11368 #11368] * Policies and guidelines: no policies or guidelines would need to be updated * Trademark approval: N/A (not needed for this Change) * Alignment with Community Initiatives: None == Upgrade/compatibility impact == To be determined. The newer packages can either Obsoletes the older ones, or not, since they are not compatible, it's probably not appropriate to use Obsoletes? == How To Test == Applications ported to webkit2gtk-4.1 need to be tested individually to ensure they still work. It's unlikely anything will go wrong for applications that do not directly or indirectly use libsoup 2. If an application or one of its dependencies needs to be ported to libsoup 3, then there is more potential for trouble. == User Experience == Users will experience shorter load times and improved responsiveness. Additionally, there will be one fewer huge package that might be installed on user systems. == Dependencies == $ dnf repoquery --whatdepends webkit2gtk4.0 --latest-limit 1 --arch 'noarch,x86_64' Last metadata expiration check: 0:00:31 ago on Thu 30 Mar 2023 03:07:12 PM CDT. apostrophe-1:2.6.3-6.fc38.noarch apvlv-0:0.4.0-2.fc38.x86_64 atril-libs-0:1.26.0-4.fc38.x86_64 badwolf-0:1.2.2-4.fc38.x86_64 balsa-0:2.6.4-2.fc38.x86_64 bookworm-0:1.1.3-0.9.20200414git.c7c3643.fc38.x86_64 cairo-dock-plug-ins-webkit-0:3.4.1-42.20210730gitf24f769.fc38.1.x86_64 claws-mail-plugins-fancy-0:4.1.1-5.fc38.x86_64 eclipse-swt-1:4.26-2.fc38.x86_64 emacs-1:28.2-4.fc38.x86_64 ephemeral-0:7.1.0-5.fc38.x86_64 exaile-0:4.1.2-2.fc38.noarch exfalso-0:4.5.0-5.fc38.noarch fapolicy-analyzer-0:1.0.0-1.fc38.x86_64 foliate-0:2.6.4-6.fc38.noarch gambas3-gb-gtk3-webview-0:3.18.1-1.fc38.x86_64 gamehub-0:0.16.3.2-6.fc38.x86_64 geany-plugins-markdown-0:1.38-9.fc38.x86_64 glade-libs-0:3.40.0-2.fc38.x86_64 gnucash-0:4.13-6.fc38.x86_64
F39 proposal: Remove standard storage option from Fedora EC2 images (Self-Contained Change proposal)
https://fedoraproject.org/wiki/Changes/CloudEC2ImagesNoStandardStorage 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 == AWS offers multiple [https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/ebs-volume-types.html types of block storage] depending on the needs of the individual user. Fedora images are uploaded with `standard` and `gp2` currently (`gp3` will replace `gp2` very soon with another [https://fedoraproject.org/wiki/Changes/CloudEC2gp3 approved change]). The `standard` storage is a previous generation storage option with less performance and less consistent performance than the other storage types. It also causes some confusion when AWS customers look through the list of Fedora cloud images in the EC2 console because now they see '''four''' images (aarch64 + x86_64, both with `standard` and `gp2` storage). Removing the `standard` storage option would reduce the amount of images that appear in the console, but AWS customers could still provision Fedora on standard storage during the instance creation process if they really want that storage option. == Owner == * Name: [[User:mhayden| Major Hayden]] * Email: ma...@redhat.com == Detailed Description == The scripts that upload images to AWS will be adjusted so that they do not include the creation of an AMI with standard storage. AWS customers could still choose that option at instance creation time if needed. == Feedback == No alternatives have been proposed yet. == Benefit to Fedora == This would reduce the amount of Fedora AMIs that appear in the EC2 console by half and it would ensure that Fedora lands on AWS' best performing storage (soon to be `gp3`) by default. It avoids a situation where an AWS customer (without a strong knowledge in block storage types) starts a Fedora instance on standard storage and gets a low performance experience. It would have no effect on running instances or existing AMIs. == Scope == * Proposal owners: This is an isolated change that should be made within `fedimg` and it affects only the AMI creation process. * Other developers: Should not require work from other developers. * Release engineering: No work should be required from releng for this change. * Policies and guidelines: N/A (not needed for this Change) * Trademark approval: N/A (not needed for this Change) * Alignment with Community Initiatives: Should make it easier to display Fedora AWS images on the Fedora Cloud page. == Upgrade/compatibility impact == Existing systems will not be affected by this change. Customers launching new instances will get better performing storage by default but will still have the option to select standard storage if they really need it. == How To Test == 1. The updated version of fedimg should create only `gp2` (soon to be `gp3`) AMIs. 2. We can verify that the latest image upload from rawhide (after the fedimg change is made) will only include a gp2/gp3-backed image. == User Experience == AWS customers who are not familiar with different block storage types should always land on high performance storage. They still have the option to choose other storage types at instance creation time. == Dependencies == Only fedimg needs to be updated. There are no other dependencies. == Contingency Plan == * Contingency mechanism: N/A (not a System Wide Change) * 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 AMIs for EC2 now default to the latest `gp2/3` storage option. -- Ben Cotton He / Him / His Fedora Program Manager 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 Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Upcoming Fedora Legal hackfest - converting to SPDX IDs
Fedora Legal will be conducting a hackfest on April 26, 2023 during a four hour block. Information is on the SIGs calendar: https://calendar.fedoraproject.org/SIGs/2023/4/26/ We will be focusing on the ELN package set in Fedora and preparing pull requests for those packages to convert the License tag to a valid SPDX expression. There will be a short presentation and [hopefully] a video walking through an example package and the steps we want package maintainers to follow. If you can make it, great! We expect to do more of these events in the future. What Hackfest for updating the license field in ELN packages to SPDX license expressions. Date Wednesday, April 26, 2023 Time 10:00 - 14:00 US eastern time 18:00 - 22:00 Central European time Where Google Meet: https://meet.google.com/fiu-jdzq-mws (chat.fedoraproject.org information coming soon...awaiting new chat room) How There will be a short presentation for background and a demo on updating a package to start, then we'll work on packages and be available for questions and help. We plan to have more events like this to help package maintainers convert License tags in spec files to SPDX syntax. Thanks, -- David Cantrell Red Hat, Inc. | Boston, MA | EST5EDT ___ 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 Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
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 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/ Full report available at: https://churchyard.fedorapeople.org/orphans-2023-04-17.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 7kaa orphan 5 weeks ago golang-github-exoscale-egoscale go-sig, orphan 2 weeks ago gstreamer1-plugins-bad-free orphan, uraeus, wtaymans 0 weeks ago kitty atim, orphan, salimma, 2 weeks ago zawertun perl-Debug-ShowStuff orphan 1 weeks ago perl-MemHandleorphan 1 weeks ago pluto orphan 5 weeks ago python-ssh-python orphan 0 weeks ago rocm-smi orphan 0 weeks ago studio-controls orphan 1 weeks ago vim-nerdtree-git-plugin atim, orphan 5 weeks ago wyhashorphan 0 weeks ago The following packages require above mentioned packages: Depending on: golang-github-exoscale-egoscale (4), status change: 2023-03-28 (2 weeks ago) golang-github-acme-lego (maintained by: eclipseo, go-sig) golang-github-acme-lego-4.4.0-8.fc37.src requires golang(github.com/exoscale/egoscale) = 0.38.0-6.fc38 golang-github-acme-lego-devel-4.4.0-8.fc37.noarch requires golang(github.com/exoscale/egoscale) = 0.38.0-6.fc38 golang-github-acme-lego-3 (maintained by: eclipseo, go-sig) golang-github-acme-lego-3-3.9.0-7.fc37.src requires golang(github.com/exoscale/egoscale) = 0.38.0-6.fc38 golang-github-acme-lego-3-devel-3.9.0-7.fc37.noarch requires golang(github.com/exoscale/egoscale) = 0.38.0-6.fc38 golang-github-caddyserver-caddy-1 (maintained by: eclipseo, go-sig) golang-github-caddyserver-caddy-1-1.0.4-11.fc38.src requires golang(github.com/go-acme/lego/v3/certcrypto) = 3.9.0-7.fc37, golang(github.com/go-acme/lego/v3/challenge) = 3.9.0-7.fc37, golang(github.com/go-acme/lego/v3/challenge/tlsalpn01) = 3.9.0-7.fc37 golang-github-caddyserver-caddy-1-devel-1.0.4-11.fc38.noarch requires golang(github.com/go-acme/lego/v3/certcrypto) = 3.9.0-7.fc37, golang(github.com/go-acme/lego/v3/challenge) = 3.9.0-7.fc37, golang(github.com/go-acme/lego/v3/challenge/tlsalpn01) = 3.9.0-7.fc37 golang-github-coredns-corefile-migration (maintained by: eclipseo, go-sig) golang-github-coredns-corefile-migration-1.0.11-10.fc38.src requires golang(github.com/caddyserver/caddy-1/caddyfile) = 1.0.4-11.fc38 golang-github-coredns-corefile-migration-devel-1.0.11-10.fc38.noarch requires golang(github.com/caddyserver/caddy-1/caddyfile) = 1.0.4-11.fc38 Depending on: gstreamer1-plugins-bad-free (22), status change: 2023-04-13 (0 weeks ago) cheese (maintained by: amigadave, gnome-sig, jwrdegoede, mclasen, mcrha) cheese-2:44.0-1.fc39.src requires pkgconfig(gstreamer-plugins-bad-1.0) = 1.22.2 cheese-2:44.0-1.fc39.x86_64 requires gstreamer1-plugins-bad-free(x86-64) = 1.22.2-1.fc39 cheese-libs-devel-2:44.0-1.fc39.i686 requires pkgconfig(gstreamer-plugins-bad-1.0) = 1.22.2 cheese-libs-devel-2:44.0-1.fc39.x86_64 requires pkgconfig(gstreamer-plugins-bad-1.0) = 1.22.2 cozy (maintained by: suve) cozy-1.2.1-3.fc39.noarch requires gstreamer1-plugins-bad-free = 1.22.2-1.fc39 farstream02 (maintained by: stefanb, uraeus) farstream02-0.2.9-11.fc38.i686 requires gstreamer1-plugins-bad-free = 1.22.2-1.fc39 farstream02-0.2.9-11.fc38.x86_64 requires gstreamer1-plugins-bad-free = 1.22.2-1.fc39 gnome-sound-recorder (maintained by: amigadave, gnome-sig) gnome-sound-recorder-43~beta-2.fc38.noarch requires gstreamer1-plugins-bad-free = 1.22.2-1.fc39
