devel March 2024

devel@lists.fedoraproject.org

148 participants
217 discussions

Orphaned magic-wormhole + its python deps
by Fabio Valentini 21 Jan '25

21 Jan '25

Hi everyone, I have just orphaned magic-wormhole (the original one written in Python) and its dependencies. I no longer use it, I have no time to fix the packages for new Python versions, and upstream is pretty much dead since they started porting the project to Rust. - python-magic-wormhole - python-magic-wormhole-mailbox-server - python-magic-wormhole-transit-relay - python-txtorcon - python-spake2 - python-hkdf There is an alternative Go implementation of the "Wormhole Protocol" (wormhole-william), for which eclipseo already submitted a review request. It seems to be better maintained than the Python original, if we want to have a Wormhole client in Fedora: https://bugzilla.redhat.com/show_bug.cgi?id=1922806 The official port of magic-wormhole to Rust also seems to be progressing, we might want to package that one instead once it's released: https://github.com/magic-wormhole/magic-wormhole.rs Fabio

4 6

Intel's Clear Linux optimizations
by František Zatloukal 21 Nov '24

21 Nov '24

Hi, Phoronix recently release article[1] about Intel's Clear Linux with some cool graphs showing nice performance gain compared to Xubuntu. I didn't have time to dig in and look how it's performing against Fedora, but I'd assume Fedora can be compared to Xubuntu in terms of compiler settings. I think i'll be interesting to look into it and find out if Fedora can't tweak compiler settings (eg use LTO for critical things like Mesa, Kernel, ...). I think it could be interesting fo Fedora users to have this enabled if there are not any disadvantages other than compile time, compile memory usage and so on. What do you think? [1] http://www.phoronix.com/scan.php?page=article&item=intel-clr-opengl&num=1 -- Best regards / S pozdravem, František Zatloukal Project Coordinator Red Hat

15 50

Packaging Guidelines for Applications using Git Submodules
by Gerald B. Cox 12 Nov '24

12 Nov '24

I'm trying to figure out the best way to handle the situation where a project decides to use submodules in Git. The archive generated doesn't incorporate the submodule files. I've done some searching on this, and haven't really come up with much. I've reviewed: Packaging:Github <https://fedoraproject.org/wiki/Packaging:SourceURL?rd=Packaging/SourceURL#G…> ; but that really doesn't address the submodule issue. I looked through some packages that are currently in the Fedora repository and found where a few folks have rebuilt the tarball and referenced that version as the Source in the spec file; then they put in a comment stating: The source of this package was pulled from upstreams' vcs. Use the following commands to generate the tarball: ... - git clone ... - git submodule init - git submodule update ... This approach is the best that I've found. Any other suggestions? Thanks much!

8 11

Request for comment- tuned replacing power-profiles-daemon plan
by Kate Hsuan 31 Oct '24

31 Oct '24

Hi Folks, We would like to replace power-profiles-daemon with tuned. There are many power-related software that offer similar functions. Advanced users may install several power management tools, for example, tuned and power-profiles-daemon (ppd), and get confused about which tools manage the system and cause unexpected behaviors for the system. By integrating power-profiles-daemon with tuned, the user can get extra features to finetune the system, and the basic feature provided by ppd can be used according to the user's demand. It also can reduce the efforts of the maintainer. The impact of this plan would be gnome-control-center (power panel), KDE, sysprof, and tuned (or some projects depending on ppd). We should move the ppd API and features to tuned to provide the same features of it. From the API aspect, we also can design a new API for the basic feature, ppd provided but the software dependent on ppd should be modified to use the new API. Although, for the long-term plan, a set of new API is a good option. For the short-term plan, moving the original one to tuned is good for those applications depending on ppd. Moreover, the detailed change proposal can be found here. https://fedoraproject.org/wiki/Changes/TunedReplacesPower-profiles-daemon If you have any suggestions, please let us know. Thank you. :) -- BR, Kate

6 11

Applications with AppData and not visible in the software center
by Richard Hughes 14 Oct '24

14 Oct '24

We've been looking at the AppStream extractor issues in Fedora, and we've come across a few broken applications. Broken apps are not visible in the application installer. The apps include: * albumart * apitrace-gui * appstream * asylum * audience * bomber * bovo * calligra-braindump * cervisia * choqok * classified-ads * crrcsim * cube * curblaster * dsi * escape * ettercap * font-manager * freedink-engine * gap-core * gnofract4d * gvrng * hgview * hyperrogue * kaddressbook * key-mon * kgraphviewer * knotes * konqueror * LabPlot * nextcloud-client (maybe fixed in distgit) * openms * openvibe * owncloud-client * pingus * pioneer * portecle * qdigidoc * qjackctl * qsynth * qtikz * recoll * renku * rodent * screengrab * screenruler * simple-ccsm * slashem * spectacle * speed-dreams * tennix * tilp2 * tortoisehg * trophy * tzclock * uzbl-defaults * vdrift * vegastrike * wireshark-gtk * xfce4-power-manager * xfpanel-switch * xskat * yakuake * zanshin * zathura The full list, along with what failed is available here: https://dl.fedoraproject.org/pub/alt/screenshots/f26/failed.html If you want any suggestions or advice, I'm happy to help. Most of the failures are pretty self explanatory, e.g. "No <summary> in AppData" or "icon was too small 24x24" -- our guidelines are here: https://github.com/hughsie/appstream-glib/blob/master/README.md#guidelines-… As a reminder, you can validate AppData files using: appstream-util validate-relax file.appdata.xml Thanks, and comments welcome. I can set up a script that sends email to the package maintainer if this would be helpful, but I thought we might be able to get the majority of these sorted with this email. Richard.

8 14

Execute RPM dependency generators on the .spec file which ships them
by Vít Ondruch 27 Sep '24

27 Sep '24

I am still playing with idea of executing RPM dependency generators on the .spec file which ships them. I have created RPM RFE ticket quite a while ago here: https://github.com/rpm-software-management/rpm/issues/782 So for no luck with having this implemented. However, I think there is reasonable way. It would be enough to have some generic attr file around. I have create small test package exploring this idea and you can find it in my Copr repo: https://copr.fedorainfracloud.org/coprs/vondruch/rpm-local-generator/ https://copr-dist-git.fedorainfracloud.org/cgit/vondruch/rpm-local-generato… On the same place, you can also find package leveraging this concept: https://copr-dist-git.fedorainfracloud.org/cgit/vondruch/rpm-local-generato… Would somebody else benefit from this idea/package or can somebody spot some issue with it? Thx for feedback. Vít

5 13

Heads-up: llhttp 9.0.1 coming to Rawhide
by Ben Beasley 18 Aug '24

18 Aug '24

In one week, 2023-08-29, I plan to update llhttp from 8.1.1 to 9.0.1 in F40/Rawhide[1]. This update contains some breaking API changes and breaks the ABI, bumping the SONAME version[2][3]. Most significantly, the compile-time LLHTTP_STRICT_MODE option is replaced with three new runtime flags. The sole dependent package is python-aiohttp; I will rebuild it myself in a side tag, using a patch for llhttp 9.x support backported from an unreleased upstream commit[4]. I don’t plan to apply the python-aiohttp patch and the llhttp 9.0.1 update to F39 at this time, with the understanding that this will constrain future python-aiohttp updates in F39: I would prefer to avoid getting ahead of upstream. I might reconsider this if an upstream release of python-aiohttp using llhttp 9.x happens by the end of the beta freeze, or if someone convinces me that keeping llhttp at 8.1.1 is the wrong approach. Input is welcome. [1] https://src.fedoraproject.org/rpms/llhttp/pull-request/15 [2] https://github.com/nodejs/llhttp/releases/tag/release%2Fv9.0.0 [3] https://github.com/nodejs/llhttp/releases/tag/release%2Fv9.0.1 [4] https://src.fedoraproject.org/rpms/python-aiohttp/pull-request/27

1 1

Porting Fedora for the LoongArch architecture.
by 孙海勇 17 Aug '24

17 Aug '24

Hi everyone, I am Sun Haiyong, from China. I want to port Fedora for the LoongArch architecture. LoongArch is a RISC ISA released by Loongson Technology Corporation Limited, and has supported a series of (Binutils, GCC, Linux, Glibc, LLVM, QEMU, etc.) core open source projects. Currently, there are many linux distributions that can run on LoongArch machines, they are OpenEuler, OpenAnolis, UOS, Kylin. I am good at cross-compiling operating systems and often build Linux systems using something like LFS or CLFS. I have built Linux distributions using rpm package management from scratch several times since 2015 (some systems are not publicly available): 1 Fedora 21, 28, 32 based on MIPS64EL architecture; 2 CentOS 7 based on MIPS64EL architecture; 3 CentOS 7 based on Power8 architecture; 4 CentOS 8.3 based on LoongArch architecture; 5 OpenEuler 2109 based on LoongArch architecture. And I have published a book on porting Fedora systems to new architectures. I want to add LoongArch to the official Fedora support architecture, and I've been doing so for some time, here's some of what I've done so far： To verify the feasibility of building a LoongArch architecture branch for Fedora, I have used the software version from the rawhide git repository, and have now compiled a large number of base packages and built a temporary repository that can be accessed at https://mirrors.wsyu.edu.cn/fedora/ I have compiled and generated more than 45,000 installable rpm files (of course there are a lot of perl, Python, rust and texlive files), and the number is still expanding, the scope of the package is enough to build a LiveCD system, for which I have built LXDE, MATE, WorkStation ( Gnome3) of the LiveCD and the installation of the ISO, you can get in the following address: https://github.com/fedora-remix-loongarch/releases-info Of course, there are still a lot of problems with LoongArch's Fedora system, for example, some software is not yet fully supported by the upstream community, but I believe the power of the community can gradually improve them, so I am sending out an email here to get more people to support this new LoongArch architecture. I have recruited some developers who are interested in this and they are： Wu Xiaotian Chen Huacai Shi Pujin Si Yanteng Chen Feiyang Of course, there are many other users who are interested in Fedora systems. I'm currently a newbie in the Fedora community, so I need help from community developers, and would like someone to guide me on what to do next, such as what would be a better time to submit necessary patches to packages in the Fedora repository, how to develop in a collaborative manner, what other systems to be used for management, etc. In short, any information would be useful. Could I get help here? :) Again, thanks for reading this email. Best Regards Sun Haiyong

12 18

sysusers scriptlets: what to do if upstream includes the config files?
by Adam Williamson 26 Jul '24

26 Jul '24

The guidelines for sysusers packaging: https://docs.fedoraproject.org/en-US/packaging-guidelines/UsersAndGroups/#_… say: "Create a <package-name>.sysusers file with the user definition and add it to the specfile as a source...use the %sysusers_create_compat macro to consume it in the %pre section: %pre %sysusers_create_compat %{SOURCE3} " but...what are you supposed to do if *upstream* ships the config files? openQA recently added these to its upstream distribution, so it seems wrong to replace the config files upstream ships with ones separately packaged downstream. But if I don't package them as source files, how can I set up the %pre macro? I tried this: %pre %sysusers_create_compat usr/lib/sysusers.d/geekotest.conf where usr/lib/sysusers.d/geekotest.conf is the path to one of the sysusers config file within the upstream source, but it doesn't seem to work. The built package has no %pre script. However, that does work if I eval it locally from an openQA source tree: [adamw@xps13k openQA (master %)]$ rpm --eval "%sysusers_create_compat usr/lib/sysusers.d/geekotest.conf" # generated from geekotest.conf getent group 'geekotest' >/dev/null || groupadd -r 'geekotest' ...etc... so...help? Is there any way to make this work right? Thanks! -- Adam Williamson Fedora QA IRC: adamw | Twitter: adamw_ha https://www.happyassassin.net

8 9

Why branched config pointed to rolling config?
by Mikhail Gavrilov 16 Jul '24

16 Jul '24

Why branched config pointed to rolling config? # ls -ln | grep fedora-40 lrwxrwxrwx. 1 0 135 26 Jan 11 20:46 fedora-40-aarch64.cfg -> fedora-rawhide-aarch64.cfg lrwxrwxrwx. 1 0 135 23 Jan 11 20:46 fedora-40-i386.cfg -> fedora-rawhide-i386.cfg lrwxrwxrwx. 1 0 135 26 Jan 11 20:46 fedora-40-ppc64le.cfg -> fedora-rawhide-ppc64le.cfg lrwxrwxrwx. 1 0 135 24 Jan 11 20:46 fedora-40-s390x.cfg -> fedora-rawhide-s390x.cfg lrwxrwxrwx. 1 0 135 25 Jan 11 20:46 fedora-40-x86_64.cfg -> fedora-rawhide-x86_64.cfg I build every day mesa snapshot, but today `mock -r fedora-rawhide-i386 ...` beginning create packages of 41 branch. And I can't fix it by `mock -r fedora-40-i386 ...` because 40 means rawhide now :(

2 1

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 March 2024