devel March 2022

devel@lists.stg.fedoraproject.org

191 participants
388 discussions

FESCo wants to know what you use i686 packages for
by David Cantrell 13 Apr '22

13 Apr '22

Hi, Our most recent FESCo meeting involved discussing the proposal to drop i686 builds of jdk8,11,17 from Fedora 37 onward. The topic quickly changed to the larger question of "what do people use i686 packages for?" Rather than guess, we wanted to ask the community what you use i686 packages for in Fedora. There are no wrong answers here. We are seeking information. Why? Since the removal of the i686 kernel in Fedora, we want to reduce the number of i686 packages provided in the repo. As time marches on, the ability to build a lot of things for i686 becomes unrealistic or even impossible. Remember it goes beyond providing builds...providing support, bug fixes, and security fixes for those packages too. Maybe some things using i686 packages now can move to x86_64 packages. We do not know yet, but a goal is to figure out what packages, if anything, can drop their i686 builds. NOTE: Nothing is changing now. We are in an information gathering phase. ~~~~~~~~~~~~~~~~~~~~~~~~ If you use i686 packages for something now, please respond to this thread. Thanks, -- David Cantrell <dcantrell(a)redhat.com> Red Hat, Inc. | Boston, MA | EST5EDT

43 56

ppc64le build failure on F34 and EPEL8, EPEL8-next only
by Germano Massullo 13 Apr '22

13 Apr '22

Good day. darktable maintainer here. I am experiencing a ppc64le build failure on F34 and EPEL8, EPEL8-next only. https://koji.fedoraproject.org/koji/taskinfo?taskID=81021540 https://koji.fedoraproject.org/koji/taskinfo?taskID=81021476 On F34 the error is /builddir/build/BUILD/darktable-3.8.0/src/iop/channelmixerrgb.c: In function '_convert_GUI_colors.part.0.constprop': /builddir/build/BUILD/darktable-3.8.0/src/iop/channelmixerrgb.c:3085:1: internal compiler error: in patch_jump_insn, at cfgrtl.c:1299 3085 | } | ^ Please submit a full bug report, with preprocessed source if appropriate. Other branches can successfully build on aarch64, x86_64, pcc64le. Do you know what can be the problem? Thank you

2 8

Donate 1 minute of your time to test upgrades from F35 to F36
by Miroslav Suchý 12 Apr '22

12 Apr '22

Do you want to make Fedora 36 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=36 --setopt=module_platform_id=platform:f36 \ --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 reveal 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 36. Please check existing reports against fedora-obsolete-packages first: https://red.ht/2kuBDPu and also there is already bunch of "Fails to install" (F36FailsToInstall) reports: https://bugzilla.redhat.com/buglist.cgi?bug_id=1992487&bug_id_type=anddepen… Thank you Miroslav

26 40

RFI/RFC: Fedora Linux graphical recovery environment
by Neal Gompa 12 Apr '22

12 Apr '22

Hey all, Earlier this week, the Fedora Workstation WG discussed a ticket brought to us asking for a GUI-based rescue/recovery environment[1]. While we all agreed in principle that such a thing would be a very good thing to have, we don't really know how to achieve such a thing. Additionally, we're not really sure what the scope of things should be provided in said recovery environment and what kind of things people would expect to be able to fix in there. So I come to y'all to ask about this and give us some feedback on the idea, how to do it, and what kinds of things you expect people to need a recovery environment for. [1]: https://pagure.io/fedora-workstation/issue/288 -- 真実はいつも一つ！/ Always, there's only one truth!

13 23

Re: Dropping wine from ARM
by Neal Gompa 10 Apr '22

10 Apr '22

On Wed, Mar 30, 2022 at 10:44 AM NightStrike <nightstrike(a)gmail.com> wrote: > > > > On Wed, Mar 30, 2022, 08:34 Michael Cronenworth <mike(a)cchtml.com> wrote: >> >> Hi, >> >> Fedora currently ships Wine 7.3 released February 25th, 2022. >> >> Wine 7.4, released March 11th, started to require a 'llvm-mingw' compiler for ARM64 >> builds. Fedora ships the 'mingw-w64' gcc-based MinGW environment and does not ship >> the 'llvm' MinGW environment. Unlike the WineMono package, which bundles a >> 'llvm-mingw' compiler (that is removed and mingw-w64 is used), the Wine package does >> not bundle one and does not allow for an alternative compiler. >> >> I will need to drop ARM from Wine in order to continue shipping new updates. I do >> not have the bandwidth to package the llvm-mingw compiler toolchain, nor do I have >> the time right now to discuss this with upstream. > > > That is an unfortunate decision on the part of wine. Gcc is a very robust compiler. > I'm not surprised, honestly. I suspect the primary motivation for Clang is that Microsoft contributed support for PDB to LLVM, but nobody brought it into GCC as far as I know. That said, we don't have any debug infrastructure for PDB, only DWARF (which is what GCC uses in Fedora). -- 真実はいつも一つ！/ Always, there's only one truth!

2 1

Koji down?
by Ron Olson 02 Apr '22

02 Apr '22

I submitted some builds yesterday and didn’t get any emails, and at least as of 6:18 CDT every link I click on the main webpage replies with “server is offline”.

2 2

Dropping wine from ARM
by Michael Cronenworth 02 Apr '22

02 Apr '22

Hi, Fedora currently ships Wine 7.3 released February 25th, 2022. Wine 7.4, released March 11th, started to require a 'llvm-mingw' compiler for ARM64 builds. Fedora ships the 'mingw-w64' gcc-based MinGW environment and does not ship the 'llvm' MinGW environment. Unlike the WineMono package, which bundles a 'llvm-mingw' compiler (that is removed and mingw-w64 is used), the Wine package does not bundle one and does not allow for an alternative compiler. I will need to drop ARM from Wine in order to continue shipping new updates. I do not have the bandwidth to package the llvm-mingw compiler toolchain, nor do I have the time right now to discuss this with upstream. Thanks, Michael

5 23

Looking for provenpackager to update rapid-photo-downloader package
by Damon Lynch 01 Apr '22

01 Apr '22

Greetings Fedora community, I am the developer of Rapid Photo Downloader. The package for it in Fedora is about two years old, and crashes during start-up under Python 3.10. As the subject says, I'm looking for a provenpackager to update the package. I'm posting this message here at the suggestion of a fellow PyQt developer who unlike myself is a Fedora expert. I filed a bug report last year but the maintainer has been unable to work on it: https://bugzilla.redhat.com/show_bug.cgi?id=2031866 Meanwhile, two months ago Neal Gompa made this pull request to update it: https://src.fedoraproject.org/rpms/rapid-photo-downloader/pull-request/3 The current release is 0.9.33. Compared to the Fedora version, it requires a new package in Fedora: https://github.com/damonlynch/showinfilemanager Unfortunately I'm unable to volunteer my time because I managed to injure my hands while working on the code earlier this year. Serious typing injuries are not fun. :-( (I'm dictating this using a voice recognition program under Windows.) Fun fact: Fedora was the first distro to package Rapid Photo Downloader.

5 4

F36 - Errors/Warnings with `dnf update`
by Nathanael D. Noblet 01 Apr '22

01 Apr '22

Hello, Just wondering if this is a bug and what to report against. I upgraded from F35 to F36Beta last night. Today I ran `sudo dnf update` and saw some odd output. Not sure if its a bug with dnf or selinux or the packages being installed. Let me know if its a known issue or if I need to file a bug and where. Running transaction Preparing : 1/1 Upgrading : crun-1.4.4-1.fc36.x86_64 1/16 error: lsetfilecon: (/usr/bin/crun;62451078, system_u:object_r:container_runtime_exec_t:s0) Invalid argument error: Plugin selinux: hook fsm_file_prepare failed Error unpacking rpm package crun-1.4.4-1.fc36.x86_64 Upgrading : containers-common-4:1-53.fc36.noarch 2/16 error: unpacking of archive failed on file /usr/bin/crun;62451078: cpio: (error 0x2) error: crun-1.4.4-1.fc36.x86_64: install failed error: lsetfilecon: (/var/lib/containers/sigstore, system_u:object_r:container_var_lib_t:s0) Invalid argument error: Plugin selinux: hook fsm_file_prepare failed Error unpacking rpm package containers-common-4:1-53.fc36.noarch Upgrading : conmon-2:2.1.0-2.fc36.x86_64 3/16 error: unpacking of archive failed on file /var/lib/containers/sigstore: cpio: (error 0x2) error: containers-common-4:1-53.fc36.noarch: install failed error: lsetfilecon: (/usr/bin/conmon;62451078, system_u:object_r:conmon_exec_t:s0) Invalid argument error: Plugin selinux: hook fsm_file_prepare failed Error unpacking rpm package conmon-2:2.1.0-2.fc36.x86_64 Upgrading : podman-3:4.0.2-1.fc36.x86_64 4/16 error: unpacking of archive failed on file /usr/bin/conmon;62451078: cpio: (error 0x2) error: conmon-2:2.1.0-2.fc36.x86_64: install failed error: lsetfilecon: (/usr/bin/podman;62451078, system_u:object_r:container_runtime_exec_t:s0) Invalid argument error: Plugin selinux: hook fsm_file_prepare failed Error unpacking rpm package podman-3:4.0.2-1.fc36.x86_64 Upgrading : runc-2:1.1.1-1.fc36.x86_64 5/16 error: unpacking of archive failed on file /usr/bin/podman;62451078: cpio: (error 0x2) error: podman-3:4.0.2-1.fc36.x86_64: install failed error: lsetfilecon: (/usr/bin/runc;62451078, system_u:object_r:container_runtime_exec_t:s0) Invalid argument error: Plugin selinux: hook fsm_file_prepare failed Error unpacking rpm package runc-2:1.1.1-1.fc36.x86_64 Upgrading : swtpm-0.7.2-1.20220307git21c90c1.fc36.x86_64 6/16 error: unpacking of archive failed on file /usr/bin/runc;62451078: cpio: (error 0x2) error: runc-2:1.1.1-1.fc36.x86_64: install failed error: lsetfilecon: (/usr/bin/swtpm;62451078, system_u:object_r:swtpm_exec_t:s0) Invalid argument error: Plugin selinux: hook fsm_file_prepare failed Error unpacking rpm package swtpm-0.7.2- 1.20220307git21c90c1.fc36.x86_64 Upgrading : snapd-2.54.4-1.fc36.x86_64 7/16 error: unpacking of archive failed on file /usr/bin/swtpm;62451078: cpio: (error 0x2) error: swtpm-0.7.2-1.20220307git21c90c1.fc36.x86_64: install failed error: lsetfilecon: (/etc/sysconfig/snapd;62451078, system_u:object_r:snappy_config_t:s0) Invalid argument error: Plugin selinux: hook fsm_file_prepare failed Error unpacking rpm package snapd-2.54.4-1.fc36.x86_64 Running scriptlet: flatpak-1.12.7-1.fc36.x86_64 8/16 error: unpacking of archive failed on file /etc/sysconfig/snapd;62451078: cpio: (error 0x2) error: snapd-2.54.4-1.fc36.x86_64: install failed Upgrading : flatpak-1.12.7-1.fc36.x86_64 8/16 error: lsetfilecon: (/usr/libexec/flatpak-system-helper;62451078, system_u:object_r:flatpak_helper_exec_t:s0) Invalid argument error: Plugin selinux: hook fsm_file_prepare failed Error unpacking rpm package flatpak-1.12.7-1.fc36.x86_64

6 8

F37 Change: Support FIDO Device Onboarding (Self-Contained Change proposal)
by Ben Cotton 01 Apr '22

01 Apr '22

https://fedoraproject.org/wiki/Changes/FIDODeviceOnboarding == Summary == Package and enable the [https://fidoalliance.org/fido-alliance-creates-new-onboarding-standard-to-s… FIDO Device Onboarding] software stack for Zero Touch Onboarding on Fedora IoT. == Owner == * Name: [[User:pbrobinson| Peter Robinson]] * Email: [mailto:pbrobinson@fedoraproject.org| pbrobinson(a)fedoraproject.org] * Name: [[User:runcom| Antonio Murdaca]] * Email: [mailto:amurdaca@redhat.com| amurdaca(a)redhat.com] == Detailed Description == The ability for an IoT or Edge device to be plugged in and automatically onboard itself with zero user interaction is critical to be able to scale IoT/Edge to millions of devices. To do this in a secure way with open standards across the industry is even more critical. The FIDO IoT working group has worked with leaders in the silicon industry such as Intel and Arm to produce the FIDO Device onboarding spec which allows a device credential, a root and chain of trust to ensure the secure onboarding of a device without the need of stored credentials. == Benefit to Fedora == The benefit to Fedora is to allow the IoT Edition to demonstrate the use of leading edge open industry protocols for onboarding IoT and Edge devices. == Scope == * Proposal owners: ** Package the rust implementation of the FIDO device onboarding stack including client, rendezvous service, owner onboarding service and prototype manufacturing service. ** Enable the client service by default for IoT Edition ** Add the client service to the IoT Edition deliverables * Other developers: ** No impact * Release engineering: [https://pagure.io/releng/issue/10720 #10720] * Policies and guidelines: N/A (not a System Wide Change) * Trademark approval: N/A (not needed for this Change) == Upgrade/compatibility impact == There is no upgrade impact. FIDO FDO is a single use onboarding protocol and will not impact existing IoT user systems. == How To Test == * Test with FDO all-in-one services. Documentation will be available for testing. == User Experience == No impact to non IoT Edition users. The user experience for the IoT Edition is still evolving and this will be updated as things fall into place later in Spring and early Summer 2022. == Dependencies == N/A (not a System Wide Change) == Contingency Plan == * Contingency mechanism: Not shipping FDO as a package in Fedora or including it in the IoT Edition * Contingency deadline: GA * Blocks release? No. * Blocks product? No. == Documentation == N/A (not a System Wide Change) == Release Notes == Fedora IoT Edition supports the FIDO Device Onboarding 1.1 specification for zero touch onboarding of IoT and Edge devices. -- Ben Cotton He / Him / His Fedora Program Manager Red Hat TZ=America/Indiana/Indianapolis

5 11

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

devel March 2022