devel August 2022

devel@lists.stg.fedoraproject.org

196 participants
254 discussions

F38 Proposal: SPDX License Phase 1 (Self-Contained Change proposal)
by Ben Cotton 08 Sep '22

08 Sep '22

https://fedoraproject.org/wiki/Changes/SPDX_Licenses_Phase_1 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 == Transition from Fedora's short name of licenses to standardized [https://spdx.org/licenses/ SPDX license] [https://spdx.dev/specifications/ formula]. == Owner == * Name: [[User:msuchy| Miroslav Suchý]] * Name: [[User:jlovejoy| Jilayne Lovejoy]] * Name: [[User:ngompa| Neal Gompa]] * Name: [[User:dcantrell| David Cantrell]] * Name: [[User:rfontanaref| Richard Fontana]] * Name: [[User:mattdm| Matthew Miller]]  * Email: msuchy(a)redhat.com, dcantrell(a)redhat.com, jlovejoy(a)redhat.com, ngompa13(a)gmail.com, rfontana(a)redhat.com == Detailed Description == In the past, Fedora decided to use short names for licenses. Although we documented the short names very well. The identifiers were never standard. In the meantime, SPDX identifiers become standard, and [https://wiki.spdx.org/view/Business_Team/Adoption other SW vendors start using it]. In this phase, we want to provide documentation and tooling to allow maintainers to begin using SPDX license ids instead of the old Fedora short names. This move is opt-in. There will be [[Changes/SPDX_Licenses_Phase_2|Phase 2]], where we identify the remaining packages and help them to migrate to the SPDX formula. == Feedback == Ancient [https://lists.fedoraproject.org/archives/list/legal@lists.fedoraproject.org… feedback from SPDX organization]. Summary from [https://lists.fedoraproject.org/archives/search?q=spdx&page=1&mlist=legal%4… fedora-legal mailing list]: we want this to happen, but this is big scope and likely will happen over more than one release. Summary from packaging-committee: * [https://pagure.io/packaging-committee/pull-request/971#] older PR to change packaging guidelines * [https://pagure.io/packaging-committee/pull-request/1142] present PR that needs more updating Summary from devel-list: TBD == Benefit to Fedora == The use of a standardized identifier for license will align Fedora with other distributions. And allows efficient and reliable identification of licenses. == Scope == * Proposal owners (things sorted by done/todo and by priorities): ** Miroslav Suchý: license-fedora2spdx - done ** Jilayne Lovejoy: map rest of Fedora licenses to SPDX ids - done ** David Cantrell: create machine-readable format and new repo - done ** David Cantrell: merge mapping of Fedora licenses to SPDX ids to new data format/repo - done ** Richard Fontana & Jilayne Lovejoy: review update all licensing info and legal pages in wiki - in process ** Jilayne Lovejoy & Richard Fontana: create and populate new Docs pages for legal and licensing info - in process ** Miroslav Suchy - create [https://gitlab.com/fedora/legal/fedora-license-data fedora-license-data package] (with data from rpminspect-data-fedora) - TODO ** David Cantrell: separate licenses from rpminspect-data-fedora [https://bugzilla.redhat.com/show_bug.cgi?id=2077914 BZ 2077914] - TODO ** Miroslav Suchý: allow `license-validate` to use spdx - TODO ** David Cantrell: generate from license data to new Docs page similar to [https://fedoraproject.org/wiki/Licensing:Main#Software_License_List Licensing:Main] ** SOMEBODY: create a webhook that updates Docs page after the merge to fedora-license-data - TODO ** Jilayne Lovejoy: prepare PR for updates to packaging guidelines - in the process [https://pagure.io/packaging-committee/pull-request/1142] ** SOMEBODY: help maintainers who want to change license string to SPDX identifiers proactively. * Out of Scope: In this phase, we do not target to move **all** packages to SPDX identifiers. That will be done in [[Changes/SPDX_Licenses_Phase_2|Phase 2]]. In [[Changes/SPDX_Licenses_Phase_2|Phase 2]] we will identify the remaining packages and open BZ or PR. * Other developers: Early adopters can migrate their License tag to the SPDX identifiers. Proposal owners will gather feedback and will work on potential problems. We want to have all bits ready so that maintainers can start changing the spec files just after Fedora 37 branching (summer 2022). * Release engineering: * Policies and guidelines: Licensing page, packaging guidelines has to be altered. * Trademark approval: N/A (not needed for this Change) * Alignment with Objectives: == Upgrade/compatibility impact == License strings are not used anything in run time. This change will not affect the upgrade or runtime of Fedora. During the transition period, developer tools like rpminspect, licensecheck, etc. may produce false negatives. And we have to define a date where we flip these tools from old Fedora's short names to the SPDX formula. == How To Test == Users should not need any testing. These steps are for package maintainers: * Fetch your license string from `License` tag in SPEC file. * Test that your current Fedora's short name is correct. E.g. $ license-validate -v 'MIT or GPLv1' Approved license * Convert license string to SPDX formula: $ license-fedora2spdx 'MIT or GPLv1' Warning: more options how to interpret MIT. Possible options: ['Adobe-Glyph', 'MIT-CMU', 'MIT-CMU', 'HPND', 'HPND', 'no-spdx-yet (MIT license (also X11))', 'SGI-B-2.0', 'SGI-B-2.0', 'SMLNJ', 'MIT-enna', 'MIT-feh', 'mpich2'] mpich2 or GPL-1.0-only In this example, the short name `GPLv1` can be converted straight to `GPL-1.0-only`. But short name `MIT` stands for several licenses with different [https://spdx.org/licenses/ SPDX identifiers]. You have to examine what license is package actually using. `license-fedora2spdx` will try to convert the formula and use one of the options but without any heuristics. You need to manually review the license. You can check if SPDX formula is correct using: $ license-validate -v --file FIXME "MIT-CMU or GPL-1.0-only" == User Experience == Users should be able to use standard software tools that audit licenses. E.g. for Software Bills of Materials. == Dependencies == No other dependencies. == Contingency Plan == * Contingency mechanism: In this first phase, if something goes wrong, we can 'git revert' each change in dist-git. It is expected that in the first phase, there will be only a few packages altered. It may be a few hundred, but it is still doable to revert. * Contingency deadline: Beta freeze. But it is expected that not all packages will be converted by that time and the change will continue in the next release. * Blocks release? No. This change has no impact on runtime of any package. == Documentation == N/A (not a System Wide Change) == Release Notes == -- Ben Cotton He / Him / His Fedora Program Manager Red Hat TZ=America/Indiana/Indianapolis

15 39

Re: Non-responsive maintainer check for Michal Ambroz a.k.a. rebus
by Mattia Verga 08 Sep '22

08 Sep '22

Il 23/08/22 22:36, zonexpertconsulting(a)outlook.com ha scritto: > Does anyone know how to contact Michal Ambroz a.k.a. rebus? > > https://bugzilla.redhat.com/show_bug.cgi?id=2120834 > > This is blocking the ZoneMinder package in RPMFusion: > https://bugzilla.redhat.com/show_bug.cgi?id=2115572 > > Thanks, > Andy Accordingly to src.fp.o stats they are active: https://src.fedoraproject.org/api/0/user/rebus/activity/stats It's August, so people could be on vacation... the relevant bug was opened on 4th August, so a non-responsive maintainer ticket seems a bit premature to me... Mattia

2 1

Users with commit rights in src.fp.o but no more in packager group
by Mattia Verga 06 Sep '22

06 Sep '22

Following my comment in https://pagure.io/fesco/issue/2856#comment-812870 I wrote a simple script to check how many users have commit rights onto some project in src.fp.o, but aren't (anymore) members of the `packager` group: ``` Found 31 users with commit privileges but not in packager group: packaging-team stefanok mmcgrath kernel-maint oddshocks systemd-maint lvm-team abrt-team i18n-team amahdal jvlomax coremodule libvirt-maint sonkun fonts-sig narasim perl-sig dcr226 gecko-maint ozamosi sheltren anaconda-maint java-sig duriantang dracut-maint ipa-maint kmod-maint mariobl mck182 design-sw cdeccio ``` With the exclusion of *-team, *-sig and *-maint, I think packaging rights should be removed from those users. Also, as per my comment linked above, I think there should be some check to prevent users removed from packager group to maintain commit rights. No idea where/how to implement that. Mattia

9 16

Sympy 1.11 (review swaps)
by Jerry James 05 Sep '22

05 Sep '22

I'm working on an update to sympy, to version 1.11. This version has several backwards incompatible changes. I inspected the consuming packages for use of the backwards incompatible APIs and found none. Just in case, I did local mock builds of each one, and the builds were all successful, including runs of their test suites. The consuming packages are: - python-boutdata - python-brian2 - python-fiat - python-nipy - python-pysb - python-trimesh - sagemath It is no longer possible to build the sympy documentation, due to missing dependencies. However, I have already noted other packages I maintain that need each of these. That tells me it is time to get them into Fedora. I would like to swap reviews for the following: - python-sphinx-basic-ng: https://bugzilla.redhat.com/show_bug.cgi?id=2121593 - python-furo: https://bugzilla.redhat.com/show_bug.cgi?id=2121594, needs python-sphinx-basic-ng - python-uc-micro-py: https://bugzilla.redhat.com/show_bug.cgi?id=2121595 - python-linkify-it-py: https://bugzilla.redhat.com/show_bug.cgi?id=2121596, needs python-uc-micro-py - python-sphinx-documatt-theme: https://bugzilla.redhat.com/show_bug.cgi?id=2121597 - python-sphinx-reredirects: https://bugzilla.redhat.com/show_bug.cgi?id=2121598, needs python-sphinx-documatt-theme Let me know what I can review for you. -- Jerry James http://www.jamezone.org/

2 4

F37 side tag after branching point
by Iñaki Ucar 04 Sep '22

04 Sep '22

Hi all, We have a new R version sitting on a side tag (f37-build-side-55653) for a few weeks now, where packages are being rebuilt as time permits. Unfortunately, F37 is not rawhide anymore, so the question is whether this side tag could be safely merged both in F37 and rawhide when it is ready. Thanks, -- Iñaki Úcar

6 16

Updating asio in rawhide (and possibly F37) to 1.24.0
by Julian Sikorski 03 Sep '22

03 Sep '22

Dear maintainers, I have updated Fedora asio package from the current 1.16.1 to 1.24.0. I have rebuilt the seven current dependencies and with the exception of OpenSceneGraph, all build fine against the updated asio package. While OpenSceneGraph failed to build, the failure does not seem to have to do anything with asio. I have created a side tag so that the rebuilds can be coordinated: f38-build-side-56604. I do not have provenpacker privileges which means you have to request the rebuilds yourself. You can start once the asio build [1] finishes. Thank you for your cooperation in advance. Best regards, Julian [1] https://koji.fedoraproject.org/koji/taskinfo?taskID=90781633

3 5

Planning to start unifying native and mingw packages
by Sandro Mani 03 Sep '22

03 Sep '22

Hi Following recent discussions and to reduce the maintenance burden, I'm planning to start merging native and mingw packages. Initially, I'll be looking at these packages where I maintain both variants: eigen3 mingw-eigen3 enchant2 mingw-enchant2 freeimage mingw-freeimage gdal mingw-gdal GeographicLib mingw-GeographicLib geos mingw-geos giflib mingw-giflib gtkspell3 mingw-gtkspell3 gtkspellmm30 mingw-gtkspellmm30 jxrlib mingw-jxrlib leptonica mingw-leptonica libgeotiff mingw-libgeotiff libimagequant mingw-libimagequant libkml mingw-libkml librttopo mingw-librttopo libspatialite mingw-libspatialite libwebp mingw-libwebp openjpeg2 mingw-openjpeg2 OpenSceneGraph mingw-OpenSceneGraph osgearth mingw-osgearth podofo mingw-podofo proj mingw-proj python-pillow mingw-python-pillow qtspell mingw-qtspell shapelib mingw-shapelib svg2svgt mingw-svg2svgt tesseract mingw-tesseract uriparser mingw-uriparser I'm performing test builds here [1]. Once I've got them all building there, if there are no objections, I plan to push to F37 and retire all the corresponding mingw repos. Sandro [1] https://copr.fedorainfracloud.org/coprs/smani/mingw-unified-spec/builds/

7 27

Heads-up / for discussion: dnf not working with 1G of RAM or less
by Adam Williamson 02 Sep '22

02 Sep '22

Hey folks! I apologize for the wide distribution, but this seemed like a bug it'd be appropriate to get a wide range of input on. There's a bug that was proposed as an F37 Beta blocker: https://bugzilla.redhat.com/show_bug.cgi?id=1907030 it's quite an old bug, but up until recently, the summary was apparently accurate - dnf would run out of memory with 512M of RAM, but was OK with 1G. However, as of quite recently, on F36 at least (not sure if anyone's explicitly tested F37), dnf operations are commonly failing on VMs/containers with 1G of RAM due to running out of RAM and getting OOM-killed. There's some discussion in the bug about what might be causing this and potential ways to resolve it, and please do dig into/contribute to that if you can, but the other question here I guess is: how much do we care about this? How bad is it that you can't reliably run dnf operations on top of a minimal Fedora environment with 1G of RAM? This obviously has some overlap with our stated hardware requirements, so here they are for the record: https://docs.fedoraproject.org/en-US/fedora/latest/release-notes/welcome/Ha… that specifies 2GB as the minimum memory for "the default installation", by which I think it's referring to a default Workstation install, though this should be clarified. But then there's a "Low memory installations" boxout, which suggests that "users with less than 768MB of system memory may have better results performing a minimal install and adding to it afterward", which kinda is recommending that people do exactly the thing that doesn't work (do a minimal install then use dnf on it), and implying it'll work. After some consideration I don't think it makes sense to take this bug as an F37 blocker, since it already affects F36, and that's what I'll be suggesting at the next blocker review meeting. However, it does seem a perfect candidate for prioritized bug status, and I've nominated it for that. I guess if folks can chime in with thoughts here and/or in the bug report, maybe a consensus will emerge on just how big of an issue this is (and how likely it is to get fixed). There will presumably be a FESCo ticket related to prioritized bug status too. Thanks folks! -- Adam Williamson Fedora QA IRC: adamw | Twitter: adamw_ha https://www.happyassassin.net

25 35

F37 Beta blocker status email
by Ben Cotton 02 Sep '22

02 Sep '22

With F37 now branched from Rawhide, it's time to pick up our weekly blocker status emails! Action summary ==================== Accepted blockers ----------------- 1. kde-settings — KDE needs to pick up F37 backgrounds — NEW ACTION: Maintainers to make new kde-settings build Proposed blockers ----------------- 1. anaconda — Anaconda crashed on signal 11 - keyboard layout encryption password prompt — ON_QA ACTION: QA, reporter to verify anaconda-37.12-1 NEEDINFO: doug.hs 2. anaconda — Anaconda will not start F37 Raw — NEW ACTION: Reporter to provide requested log files NEEDINFO: aalmeleh.whatever.0101 3. dnf — "dnf update" runs out of memory on swapless 0.5 GiB RAM machine — NEW ACTION: Manitainers to investigate short-term dnf improvements NEEDINFO: jmracek 4. dracut — Media check fails with checkisomd5 "service failed because the control process exited with error code" — POST ACTION: Maintainers to build with upstream PR 5. polkit — Switching users in Gnome results in polkitd errors that prevent powering off the computer. — ASSIGNED ACTION: Maintainers to diagnose issue 6. sddm — Logout from KDE session on Rawhide goes to console, not SDDM — NEW ACTION: Maintainers to diagnose issue Bug-by-bug detail ============= Accepted blockers ----------------- 1. kde-settings — https://bugzilla.redhat.com/show_bug.cgi?id=2117706 — NEW KDE needs to pick up F37 backgrounds New desktop backgrounds require a new KDE settings update. Proposed blockers ----------------- 1. anaconda — https://bugzilla.redhat.com/show_bug.cgi?id=2070823 — ON_QA Anaconda crashed on signal 11 - keyboard layout encryption password prompt Clicking the keyboard layout button in the LUKS decryption popup crashes anaconda. anaconda-37.12-1 contains a candidate fix. 2. anaconda — https://bugzilla.redhat.com/show_bug.cgi?id=2101229 — NEW Anaconda will not start F37 Raw Neither clicking the desktop icon nor the taskbar icon will launch anaconda. openQA is not experiencing this. Using basic graphics mode results in the expected behavior. 3. dnf — https://bugzilla.redhat.com/show_bug.cgi?id=1907030 — NEW "dnf update" runs out of memory on swapless 0.5 GiB RAM machine dnf is killed by oom-kill on machines with 512 MB of RAM. Adding a swap disk or disabling the updates repo works around this issue. Recently, FCOS has seen this behavior with 1 GB VMs. The issue appears to be the size of the metadata for the repository. The short term fixes look like they may need to be made on the repo side, not in dnf. 4. dracut — https://bugzilla.redhat.com/show_bug.cgi?id=2107858 — POST Media check fails with checkisomd5 "service failed because the control process exited with error code" Media check fails on certain hardware. Skipping the media check results in a successful boot. Upstream PR #1882 contains a candidate fix: https://github.com/dracutdevs/dracut/pull/1882 5. polkit — https://bugzilla.redhat.com/show_bug.cgi?id=2109145 — ASSIGNED Switching users in Gnome results in polkitd errors that prevent powering off the computer. Under certain conditions (including but not limited to several user switches), the power off button disappears from the GNOME menu due to a polkitd error. `systemctl poweroff -i` as an unprivileged user does not work. It may be an issue with using the duktape JS engine instead of mozjs91. polkit-121-3 reverts to mozjs91, but is not a sufficient fix. 6. sddm — https://bugzilla.redhat.com/show_bug.cgi?id=2110801 — NEW Logout from KDE session on Rawhide goes to console, not SDDM After logging out of KDE Plasma, you end up at a console on tty2. SDDM had been running on tty1 but just shows a flashing cursor. -- Ben Cotton He / Him / His Fedora Program Manager Red Hat TZ=America/Indiana/Indianapolis

2 4

Let's enable Koschei for all packages automatically
by Miro Hrončok 01 Sep '22

01 Sep '22

Hello folks, during our Nest FESCo session, we've talked about enabling Koschei [1] for all packages automatically. There seem to be a consensus by FESCo members, that it would be a good thing. What would it take? 1) Koji resources I think we can try to enable this and see if it burns. I think ti won't. 2) One-time enablement of all existing packages That should be doable. Right? 3) Automatic enablement of all new packages That should be just a matter of changing the defaults. Correct? Can we do this? How can I help? [1] https://fedoraproject.org/wiki/Koschei -- Miro Hrončok -- Phone: +420777974800 IRC: mhroncok

11 17

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 August 2022