February 2023 - devel - Fedora Mailing-Lists

by Richard W.M. Jones

Earlier discussion: https://www.mail-archive.com/devel@lists.fedoraproject.org/msg169800.html Current memtest86+ 5.x requires non-UEFI, which makes it increasingly irrelevant to modern hardware. memtest86 forked into a proprietary product some time ago. However there is hope because upstream memtest86+ 6.00 is (a) open source and (b) seems to work despite the large warnings on the website: https://memtest.org/ Note this new version is derived from pcmemtest mentioned in the thread above which is only indirectly derived from memtest86+ 5.x and removes some features. So my question is are we planning to move to v6.00 in future? I did attempt to build a Fedora RPM, but it basically involves removing large sections of the existing RPM (eg. the downstream script we add seems unnecessary now and the downstream README would need to be completely rewritten). It's probably only necessary to have memtest.efi be installed as /boot/memtest.efi and although it won't appear automatically in the grub menu, it can be accessed by a trivial two line command. Rich. -- Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones Read my programming and virtualization blog: http://rwmj.wordpress.com virt-p2v converts physical machines to virtual machines. Boot with a live CD or over the network (PXE) and turn machines into KVM guests. http://libguestfs.org/virt-v2v

1 year

7
8
0 / 0

Conflicting build-ids in nekovm and haxe

by Andy Li

Hi list, Re. https://bugzilla.redhat.com/show_bug.cgi?id=1896901 Since haxe-4.1.3-4 and nekovm-2.3.0-4, both nekovm and haxe packages contains "/usr/lib/.build-id/b0/aed4ddf2d45372bcc79d5e95d2834f5045c09c". The nekovm one is a symlink to "/usr/bin/neko". The haxe one to "/usr/bin/haxelib". Both the neko and haxelib binaries are built with libneko, with a nearly identical main.c with the only difference of the present of neko bytecode embedded as a byte array (neko: the byte array is null; haxelib: the byte array is the haxelib neko bytecode). I'm not sure how to resolve it. Please advice. Best regards, Andy

1 year

5
6
0 / 0

Review/Merge Request: tcpcrypt: remove broken firewalld integration

by Eric Garver

PR: https://src.fedoraproject.org/rpms/tcpcrypt/pull-request/1 Bugs: - https://bugzilla.redhat.com/show_bug.cgi?id=2159838 (f37) - https://bugzilla.redhat.com/show_bug.cgi?id=2095227 (f36) tl;dr The PR removes firewalld support from the tcpcrypt package. This integration appears to have never worked. Please review and merge. I cannot merge it myself. I will open PRs for f38, f37, and f36 after the rawhide change gets merged. Thanks. Eric.

1 year

1
2
0 / 0

Test upgrades from F37 to F38 - it will take you just a minute

by Miroslav Suchý

Do you want to make Fedora 38 better? Please spend 1 minute of your time and try to run: # Run this only if you use default Fedora modules # next time you run any DNF command default modules will be enabled again sudo dnf module reset '*' dnf --releasever=38 --setopt=module_platform_id=platform:f38 \ --enablerepo=updates-testing \ $(rpm -q fedora-repos-modular >/dev/null && echo --enablerepo=updates-testing-modular) \ --assumeno distro-sync This command does not replace `dnf system-upgrade`, but it will reveals potential problems. You may also run `dnf upgrade` before running this command. The `--assumeno` will just test the transaction, but does not make the actual upgrade. In case you hit dependency issues, please report it against the appropriate package. Or against fedora-obsolete-packages if that package should be removed in Fedora 38. Please check existing reports against fedora-obsolete-packages first: https://red.ht/2kuBDPu and also there is already bunch of "Fails to install" (F38FailsToInstall) reports: https://bugzilla.redhat.com/show_bug.cgi?id=F38FailsToInstall Thank you Miroslav

1 year

22
31
0 / 0

Status of AVIF support in Fedora

by Sandro

Greetings everyone, TL;DR Will there be AVIF (AV1) support for applications using libheif in Fedora? A while ago I stumbled upon AVIF files not being supported by applications (gThumb, ImageMagick, GIMP) in Fedora [1]. It appears that the applications mentioned have switched to libheif for AVIF support in favor of libavif. Since libheif also provides/requires patent encumbered libraries/codecs (libde265) related to HEIF it is provided by RPMFusion. AVIF, however, is not encumbered by patents as I understand it [2]. So it seems we need a compatibility libheif-av1 or the like to allow applications provided by fedora repos to enable AVIF (AV1) support using libheif [3]. I found two threads ([4],[5]) in the archives regarding HEIF and AVIF. But none of them are conclusive with regards to enabling AVIF support. Are there any plans to enable AVIF support in applications that use libheif as their provider? If so, where can I find information regarding the status? I apologize in advance if any of the above is not entirely correct (or entirely incorrect). Aim of my message is to better understand why support for AVIF is lacking in some applications and if that can be fixed. [1] https://bugzilla.redhat.com/show_bug.cgi?id=2165606 [2] https://bugzilla.redhat.com/show_bug.cgi?id=2164329#c3 [3] This part is not entirely clear to me. Please correct me. [4] https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.o... [5] https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.o... Cheers, Sandro -- Sandro FAS: gui1ty IRC: Penguinpee Elsewhere: [Pp]enguinpee

1 year, 1 month

9
24
0 / 0

Fedora Linux 38 blocker status summary

by Ben Cotton

We've branched F38 from Rawhide, so it's time to start everyone's favorite Friday email from Ben! The F38 Beta freeze begins on 21 February. The current target release date is the early target date (2023-03-14). Action summary ==================== Accepted blockers ----------------- 1–3. distribution — {Workstation,Everything,Server} boot x86_64 image exceeds maximum size — ASSIGNED ACTION: Relevant Teams to reduce image size or increase the limit Proposed blockers ----------------- 1. anaconda — installer fails to boot in text mode or rescue mode with systemd 253 — MODIFIED ACTION: Maintainers to build an update that includes upstream PR 2. grub2 — ext4 filessystem support missing — NEW ACTION: Maintainer to diagnose issue NEEDINFO: ausil 3. kwin — kwin_wayland often crashed when used as the sddm Wayland compositor and logging out of Plasma resulting in a black screen — NEW ACTION: Maintainer to diagnose issue 4. mesa — KDE crashes on start with mesa-23.0.0~rc3-3.fc38 — ASSIGNED ACTION: Maintainer to diagnose issue Bug-by-bug detail ============= Accepted blockers ----------------- 1–3. distribution — {Workstation,Everything,Server} boot x86_64 image exceeds maximum size — ASSIGNED https://bugzilla.redhat.com/show_bug.cgi?id=2149246 https://bugzilla.redhat.com/show_bug.cgi?id=2151495 https://bugzilla.redhat.com/show_bug.cgi?id=2151497 Image sizes exceed the specified limits. The choices are to either shrink the image by removing packages or to riase the limits. Proposed blockers ----------------- 1. anaconda — https://bugzilla.redhat.com/show_bug.cgi?id=2165433 — MODIFIED installer fails to boot in text mode or rescue mode with systemd 253 anaconda is writing systemd units to an unexpected area. Upstream PR 4534 contains a candidate fix: https://github.com/rhinstaller/anaconda/pull/4534 2. grub2 — https://bugzilla.redhat.com/show_bug.cgi?id=2166412 — NEW ext4 filessystem support missing Between grub2-2.06-76 and grub2-2.06-78, grub2 apparently lost the ability to detect ext4 filesystems. 3. kwin — https://bugzilla.redhat.com/show_bug.cgi?id=2168034 — NEW kwin_wayland often crashed when used as the sddm Wayland compositor and logging out of Plasma resulting in a black screen Logging out of Plasma sometimes triggers a kwin crash. This may be limited to running in a virtual machine. 4. mesa — https://bugzilla.redhat.com/show_bug.cgi?id=2164667 — ASSIGNED KDE crashes on start with mesa-23.0.0~rc3-3.fc38 A recent mesa update caused both GNOME and KDE to crash on start. Update FEDORA-2023-40b973fa06 fixed GNOME, but KDE is still seeing this issue. The root cause is still uncertain. -- Ben Cotton He / Him / His Fedora Program Manager Red Hat TZ=America/Indiana/Indianapolis

1 year, 1 month

19
48
0 / 0

HEADS UP: tesseract-5.3.0 landing in rawhide with soname bump

by Sandro Mani

Hi I'll be landing tesseract 5.3.0 in rawhide, building it in the f38-build-side-61405 side tag, along with the following dependent packages: ffmpeg gimagereader mupdf opencv python-PyMuPDF qpdfview R-tesseract zathura-pdf-mupdf Thanks Sandro

1 year, 1 month

3
4
0 / 0

Fedora Linux 38 branched

by Tomas Hrcka

Hi All, Fedora Linux 38 has now been branched, please be sure to do a git pull --rebase to pick up the new branch, as an additional reminder rawhide/f39 has been completely isolated from previous releases, so this means that anything you do for f38 you also have to do in the rawhide branch and do a build there. There will be a Fedora Linux 38 compose and it'll appear in http://dl.fedoraproject.org/pub/fedora/linux/development/38/ once complete. Bodhi is currently enabled in the f38 branch like it is for rawhide, with automatic update creation. At the hit Beta change freeze point in the Fedora Linux 38 schedule[1] updates-testing will be enabled and manual bodhi updates will be required as in all stable releases. Two things to remember: 1. The modules will be built for a new platform:f39 2. F38/branched release is frozen right now until we get a successful compose, expect that your f38 builds won't be available immediately. Thanks for understanding. Tomas Hrcka Fedora Release Engineering [1] https://fedorapeople.org/groups/schedule/f-38/f-38-key-tasks.html _______________________________________________ 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.fedora... Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue

1 year, 1 month

10
13
0 / 0

Heads up - squashfs-tools prelease in rawhide

by Bruno Wolff III

Phillip is really close to releasing 4.6 and I want to get some testing in rawhide before that happens. If we do find a problem, it will be easier on him if we find it before the release. I ran a test script that tests the features we mostly use, so I'm not expecting any problems.

1 year, 2 months

1
1
0 / 0

F38 proposal: Noto CJK Variable Fonts (Self-Contained Change proposal)

by Ben Cotton

https://fedoraproject.org/wiki/Changes/Noto_CJK_Variable_Fonts 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 == Switch the default Noto CJK fonts for Chinese, Japanese and Korean from static to variable fonts. == Owner == * Name: [[User:pwu| Peng Wu]] * Email: pwu(a)redhat.com == Detailed Description == In order to reduce the font size in Noto CJK fonts, we plan to switch to use the variable fonts by default. # Split the google-noto-cjk-fonts package into google-noto-sans-cjk-fonts and google-noto-serif-cjk-fonts, and provide the variable fonts in google-noto-sans-cjk-vf-fonts and google-noto-serif-cjk-vf-fonts. # Drop several sub packages which are not installed by default from the google-noto-cjk-fonts package. ## Like google-noto-sans-cjk-*-fonts, google-noto-sans-*-fonts, google-noto-sans-mono-cjk-*-fonts, google-noto-serif-cjk-*-fonts and google-noto-serif-*-fonts # Install the Noto CJK Variable Fonts by default. Fedora Copr for testing: https://copr.fedorainfracloud.org/coprs/pwu/noto-cjk/ == Feedback == == Benefit to Fedora == The variable fonts will reduce the disk space usage and live image size compared to the static fonts. {| class="wikitable" |+ RPM Size |- ! Size (bytes) !! Noto Sans CJK !! Noto Serif CJK |- | Static Fonts || 130674365 || 181621033 |- | Variable Fonts || 64613100 || 56924710 |} == Scope == * Proposal owners: ** Package four font packages for Noto CJK fonts ** Retire google-noto-cjk-fonts in Fedora rawhide ** Switch to install variable fonts by default in fedora-comps and langpacks ** Submit pull request to lorax templates to use google-noto-sans-cjk-fonts in the boot.iso * Other developers: * Release engineering: * 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 == When upgrade, the variable fonts will be installed by default. == How To Test == * Please upgrade to Fedora 38 or rawhide to get the latest fonts * Install the variable fonts: google-noto-sans-cjk-vf-fonts and google-noto-serif-cjk-vf-fonts ** Check the google-noto-sans-cjk-ttc-fonts and google-noto-serif-cjk-ttc-fonts packages are replaced * Then use CJK locales to check if the new fonts have any problem == User Experience == This new variable fonts will reduce the disk space usage and live image size. == Dependencies == == Contingency Plan == * Contingency mechanism: Use the static fonts by default - google-noto-sans-cjk-fonts and google-noto-serif-cjk-fonts * Contingency deadline: N/A * Blocks release? N/A == Documentation == N/A (not a System Wide Change) == Release Notes == This new variable fonts will reduce the disk space usage and live image size. -- Ben Cotton He / Him / His Fedora Program Manager Red Hat TZ=America/Indiana/Indianapolis

1 year, 2 months

4
6
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

devel February 2023