Re: How to remove settings from a systemd unit file
On Tue, Jun 4, 2024 at 6:24 PM Sam Varshavchik wrote: > So I was tearing my hair out trying to figure out why attempts to push > via > DAV to a git repo were failing. > > Eventually I succeeded in stracing the httpd process sto capture the > request. It was getting an EROFS when it tried to write to the git repo. > > Amusing. > > To make a long story short, the culprit was: > > ProtectHome=read-only > > in /lib/systemd/system/httpd.service,(the git repo was in a directory > inside > a mounted /home partition). > > I tried using > > systemctl edit httpd > > And putting this in there: > > [Service] > ProtectHome= > > However this apparently did not work. I threw in the towel and just > edited > /lib/systemd/system/httpd.service and commented this setting out, > entirely, > to finally fix this issue, and happy git pushing resumed. > > But how do I fix this so that the next apache update doesn't clobber this? > Copy the file to /etc/systemd/system and it will override the package provided file in /lib/systemd/system Thanks, Richard -- ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-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/users@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
[wsjt-devel] Fortran error on Fedora 40+
Doing some test builds of current RC4 and seeing build failures: /builddir/build/BUILD/wsjtx-2.7.0/wsjtx/qmap/libqmap/decode0.f90:6:28: 6 | real*4 dd(2,NSMAX),ss(400,NFFT),savg(NFFT) |1 Error: Variable ‘nfft’ cannot appear in the expression at (1) /builddir/build/BUILD/wsjtx-2.7.0/wsjtx/qmap/libqmap/decode0.f90:6:39: 6 | real*4 dd(2,NSMAX),ss(400,NFFT),savg(NFFT) | 1 Error: Variable ‘nfft’ cannot appear in the expression at (1) Comparing fortran versions I see gcc-fortran 14.1.1 vs 13.3.1 in Fedora 39. Thanks, Richard KF5OIM ___ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
Re: Need SELinux help for fail2ban!
I'm trying to reproduce the problem on the Fedora rawhide test machine but it's running without error! $ sudo systemctl status fail2ban.service ● fail2ban.service - Fail2Ban Service Loaded: loaded (/usr/lib/systemd/system/fail2ban.service; disabled; preset: disabled) Drop-In: /usr/lib/systemd/system/service.d └─10-timeout-abort.conf Active: active (running) since Sun 2024-05-05 12:31:24 UTC; 1min 8s ago Docs: man:fail2ban(1) Process: 1689891 ExecStartPre=/bin/mkdir -p /run/fail2ban (code=exited, status=0/SUCCESS) Main PID: 1689893 (fail2ban-server) Tasks: 3 (limit: 9118) Memory: 11.5M (peak: 11.8M) CPU: 114ms CGroup: /system.slice/fail2ban.service └─1689893 /usr/bin/python3 -sP /usr/bin/fail2ban-server -xf start May 05 12:31:24 rawhide-test.fedorainfracloud.org systemd[1]: Starting fail2ban.service - Fail2Ban Service... May 05 12:31:24 rawhide-test.fedorainfracloud.org systemd[1]: Started fail2ban.service - Fail2Ban Service. May 05 12:31:25 rawhide-test.fedorainfracloud.org fail2ban-server[1689893]: Server ready --- Socket file is written: $ ll -Z /run/fail2ban/ total 4 -rw---. 1 root root system_u:object_r:fail2ban_var_run_t:s0 8 May 5 12:31 fail2ban.pid srwx--. 1 root root system_u:object_r:fail2ban_var_run_t:s0 0 May 5 12:31 fail2ban.sock I don't want to try random fixes to a problem I can't reproduce... Richard -- ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-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@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: Need SELinux help for fail2ban!
On Sat, May 4, 2024 at 4:49 PM Carlos Rodriguez-Fernandez < carlosrodrifernan...@gmail.com> wrote: > The suggestion for one of the comments of using `/run/fail2ban(/.*)?` > instead of `/run/fail2ban.*` doesn't work? > I try to be very careful with making changes in SELinux and I don't know what the difference is between those two statements. ChatGPT had the following to say: In SELinux, these two statements represent regular expressions used in file context definitions. Let's break down each one: 1. `/run/fail2ban(/.*)?`: - This regular expression matches paths that start with `/run/fail2ban/` followed by zero or more characters (`.*`) and optionally followed by a forward slash and zero or more characters (`(/.*)?`). Essentially, it matches paths like `/run/fail2ban`, `/run/fail2ban/`, and any subdirectories and files within `/run/fail2ban`. 2. `/run/fail2ban.*`: - This regular expression matches paths that start with `/run/fail2ban` followed by zero or more characters (`.*`). It doesn't specify any specific structure beyond `/run/fail2ban`, so it matches paths like `/run/fail2ban`, `/run/fail2ban.log`, `/run/fail2ban/somefile`, etc. It doesn't specifically include subdirectories like the previous expression. In summary, the first expression is more specific, including subdirectories under `/run/fail2ban`, while the second expression is more general, matching any path that starts with `/run/fail2ban`. --- It doesn't look like it would make a difference for the specific issue... Thanks, Richard -- ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-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@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Need SELinux help for fail2ban!
I still don't understand SELinux and would appreciate an assist! fail2ban-server is unable to create the socket file /run/fail2ban/fail2ban.sock There's a lot of custom SELinux policies and I'm unable to figure out what needs to change. https://bugzilla.redhat.com/show_bug.cgi?id=2279054 https://bugzilla.redhat.com/show_bug.cgi?id=2272476 https://src.fedoraproject.org/rpms/fail2ban/tree/rawhide Thanks, Richard -- ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-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@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: Fail2ban is failing
On Fri, May 3, 2024 at 4:13 PM Patrick O'Callaghan wrote: > On Fri, 2024-05-03 at 13:08 -0400, Tom Rivers via users wrote: > > Until the fix is available, I've been able to get it running until > > the > > next system reboot by doing the following: > > > > # setenforce 0 > > # systemctl start fail2ban > > > > ... wait a minute ... > > > > # setenforce 1 > > > > That seems to work. Looks like a problem with SElinux labelling. > More or less, basically from what I can tell with F40 that the link from /var/run->/run for compatibility was dropped and the selinux context in the fail2ban package needed to be updated (and it was) but my assumption is that installation of the new package would take care of it. Thanks, Richard -- ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-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/users@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: Fail2ban is failing
On Fri, May 3, 2024 at 6:31 AM Patrick O'Callaghan wrote: > F40 fully updated. > Try a `dnf --refresh update`. The fix just went to stable last night. Thanks, Richard -- ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-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/users@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: fail2ban on F40 is quiet
On Sun, Apr 28, 2024 at 9:31 AM Frank Bures wrote: > Hi, > > My machine is exposed to the wild and I was seeing hundreds of connection > attempts per day in my logs and in fail2ban.log. > > All these nefarious activities ceased after upgrade to F40. > > Question: > Is there something fundamentally different in F40 connectivity? > I can still connect from outside on pre-defined ports using ssh so my ISP > is not blocking anything. > I would try this update and see if it fixes your problem. There's also a new release but I want this to go stable first. https://bodhi.fedoraproject.org/updates/FEDORA-2024-95a6cdf26b Thanks, Richard -- ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-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/users@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: Live USB extra space
On Sat, Apr 27, 2024 at 11:21 PM ToddAndMargo via users < users@lists.fedoraproject.org> wrote: > Hi All, > > I "Finally" have a customer interested in Fedora. I > talked him into letting me spin a Live USB flash drive > for him to play with before we jump ahead. > > Question: Is there a way to use the extra space on the > drive to install a few more programs for him to experiment > with? > There used to be a way to make it semi-permanent but I don't think that's supported anymore. But it would only record changes to the file system (all changes were appended) so you would eventually use up the space. In this case I might be tempted to do a real install to a USB stick or similar. I actually had a full install on a M.2 SATA in a USB 3.0 enclosure. Thanks, Richard -- ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-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/users@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: [HEADS-UP] openexr so name bump heading Rawhide and f40
Just an observation... I'm very happy for the assist, I don't have the time I used to for packaging and the dependency chain for this particular package is "fun", but as the primary maintainer for openexr, you can imagine my surprise as this announcement. Perhaps it would be a good idea to contact the maintainer for a project prior to such announcements? Thanks, Richard -- ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-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@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: The best way to still use Fedora + Xorg + Gnome ... even after version 40
On Wed, Apr 17, 2024 at 7:48 PM Sam Varshavchik wrote: > Jeffrey Walton writes: > > > Wayland is still pretty immature when compared to X11. It would be nice > if > > Wayland was more mature before we are forced to switch to it. > > The question on everyone's mind is: well, here's a video card that works > fine with X. It's 5-10 years old, one of mine is even older. What are the > chances that Wayland actually supports it. > Well if you're running Fedora you should be able to try it by changing to X before logging in. A even less intrusive way would be to try Fedora 40 on a live USB stick. Thanks, Richard -- ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-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/users@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
unifi maintainership
Just a heads up guys but I upgraded to a UDM Pro SE recently so I'm no longer running the network application on a PC. I can maintain it for now assuming any issues I run into on ARM are the same as x86_64 but if there's someone who would like to maintain the unifi package I am willing to turn over maintenance of it. Thanks, Richard ___ rpmfusion-developers mailing list -- rpmfusion-developers@lists.rpmfusion.org To unsubscribe send an email to rpmfusion-developers-le...@lists.rpmfusion.org
Re: [BackupPC-users] New Server Hardware; Old Data Pool
On Wed, Feb 21, 2024 at 12:25 PM Tim Evans wrote: > However, I still get the above error when trying to access the server's > web admin pages. Further investigation shows the following error in the > httpd (Apache) web server error_log: > > [Tue Feb 20 06:36:00.553934 2024] [cgid:error] [pid 2519:tid 2670] > (13)Permission denied: [client ::1:43404] AH01257: stderr from > /usr/libexec/BackupPC/BackupPC_Admin: unable to connect to cgi > daemon after multiple tries > > Googling "unable to connect to cgi daemon" turns up a lot of references > to the httpd 'mpm' module. Hoping that folks who are familiar with > Apache module innards might have some advice here. > How old of a system did the original install come from? The reason I mention is the thing I completely forgot about when upgrading my BackupPC from Centos 8 Stream to Fedora Server 39 is the apache configuration: # cat BackupPC.conf # BackupPC requires valid authentication in order for the web interface to # function properly. One can view the web interface without authentication # though all functionality is disabled. # # htpasswd -c /etc/BackupPC/apache.users yourusername # AuthType Basic AuthUserFile /etc/BackupPC/apache.users AuthName "BackupPC" # Apache 2.4 Require valid-user Require ip 192.168.1.0/255.255.255.0 # Apache 2.2 order deny,allow deny from all allow from 127.0.0.1 allow from ::1 require valid-user Alias /BackupPC/images/usr/share/BackupPC/html/ ScriptAlias /BackupPC /usr/libexec/BackupPC/BackupPC_Admin ScriptAlias /backuppc /usr/libexec/BackupPC/BackupPC_Admin The key is I had to add Require ip xx.xxx.xxx.xxx/255.255.255.0 because by default it only allows connections from the host. Thanks, Richard ___ BackupPC-users mailing list BackupPC-users@lists.sourceforge.net List:https://lists.sourceforge.net/lists/listinfo/backuppc-users Wiki:https://github.com/backuppc/backuppc/wiki Project: https://backuppc.github.io/backuppc/
Re: mock build for rawhide: Transaction failed: Signature verification failed.
On Tue, Feb 20, 2024 at 7:40 AM Brad Smith wrote: > I had this problem too. There is a new version of mock and > more-core-config (not sure of name still getting first cup of coffee) in > updates-testing that has the fix. > Ahh, updating mock didn't pull in mock-core-config. Both it and distribution-gpg-keys are updated and now everything seems fine. Thanks! -- ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-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@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: mock build for rawhide: Transaction failed: Signature verification failed.
On Tue, Feb 20, 2024 at 7:00 AM Miro Hrončok wrote: > > > On 20. 02. 24 13:31, Richard Shaw wrote: > > For about a week I've been seeing this when trying to test build > packages for > > rawhide locally: > > > > Transaction failed: Signature verification failed. > > PGP check for package "bash-5.2.26-3.fc40.x86_64" > > > (/var/lib/mock/fedora-rawhide-x86_64/root/var/cache/dnf/fedora-2d95c80a1fa0a67d/packages/bash-5.2.26-3.fc40.x86_64.rpm) > from repo "fedora" has failed: Import of the key didn't help, wrong key? > > > > I've already done a --scrub=all a few times to no avail. > > Do you have distribution-gpg-keys 1.101 installed? > Let me try that, I did an update of rpm and mock but I didn't want to do a full system upgrade just yet. Thanks, Richard -- ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-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@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: New BackupPC Server Hardware; Existing Data Pool
On Tue, Feb 20, 2024 at 6:43 AM Tim Evans wrote: > The new BackupPC server starts up--I can see it in process listing; > httpd web server is working as well. I get prompted to log in to the > server admin page as expected, then get the following httpd "503" error: > > "Service Unavailable > > The server is temporarily unable to service your request due to > maintenance downtime or capacity problems. Please try again later."da > > The BackupPC log files don't show any activity, nor does journalctl. > > I do, however, see this in the httpd error_log: > > [Tue Feb 20 06:36:00.553934 2024] [cgid:error] [pid 2519:tid 2670] > (13)Permission denied: [client ::1:43404] AH01257: stderr from > /usr/libexec/BackupPC/BackupPC_Admin: unable to connect to cgi daemon > after multiple tries > As the BackupPC package maintainer, I have never seen this, so it may be unique to your setup... The only thing I can think of right now might be to try temporarily putting SELinux into permissive mode and see if that helps. If so, maybe relabeling the filesystem if the key. Thanks, Richard -- ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-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/users@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
mock build for rawhide: Transaction failed: Signature verification failed.
For about a week I've been seeing this when trying to test build packages for rawhide locally: Transaction failed: Signature verification failed. PGP check for package "bash-5.2.26-3.fc40.x86_64" (/var/lib/mock/fedora-rawhide-x86_64/root/var/cache/dnf/fedora-2d95c80a1fa0a67d/packages/bash-5.2.26-3.fc40.x86_64.rpm) from repo "fedora" has failed: Import of the key didn't help, wrong key? I've already done a --scrub=all a few times to no avail. Anyone else seeing this? Thanks, Richard -- ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-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@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: [wsjt-devel] Problem with WSJT-X 2.7.0 RC3 and Hamlib +Flrig
Dave just posted a new alpha, I'll test with it first to see if it's resolved. Thanks, Richard KF5OIM ___ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
Re: HELP! What's up with OpenVDB?
Almost there but running into a build problem with Blender... https://koji.fedoraproject.org/koji/taskinfo?taskID=112606258 --- /builddir/build/BUILD/blender-4.0.2/intern/cycles/scene/image_vdb.cpp: In member function ‘bool ccl::ToNanoOp::operator()(const openvdb::v11_0::GridBase::ConstPtr&)’: /builddir/build/BUILD/blender-4.0.2/intern/cycles/scene/image_vdb.cpp:58:33: error: ‘openToNanoVDB’ is not a member of ‘nanovdb’ 58 | nanogrid = nanovdb::openToNanoVDB’ token 60 | nanovdb::FpN>(floatgrid); | ^ /builddir/build/BUILD/blender-4.0.2/intern/cycles/scene/image_vdb.cpp:64:33: error: ‘openToNanoVDB’ is not a member of ‘nanovdb’ 64 | nanogrid = nanovdb::openToNanoVDB’ token 66 | nanovdb::Fp16>(floatgrid); |^ /builddir/build/BUILD/blender-4.0.2/intern/cycles/scene/image_vdb.cpp:71:29: error: ‘openToNanoVDB’ is not a member of ‘nanovdb’ 71 | nanogrid = nanovdb::openToNanoVDB(floatgrid); | ^ --- Looking at openvdb I see this but it looks like it's only skipping nanovdb_convert, why I don't know... https://koji.fedoraproject.org/koji/buildinfo?buildID=2391613 --- -- - Configuring NanoVDB Cmd Tools -- CMake Warning at nanovdb/nanovdb/cmd/CMakeLists.txt:31 (message): - OpenVDB required to build nanovdb_convert. Skipping. --- Any help would be appreciated but I don't want to leave the side-tag open much longer. Thanks, Richard -- ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-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@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: runaway fork() in Lua script
On Mon, Jan 29, 2024 at 12:03 PM Jerry James wrote: > For the second time in two days, running "fedpkg build" gave me a few > dozen lines that say: > > warning: runaway fork() in Lua script > > before the usual build messages start appearing. Is this a known issue? > Just started seeing this after a `dnf update` and reboot... Thanks, Richard -- ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-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@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: HELP! What's up with OpenVDB?
On Mon, Jan 29, 2024 at 7:13 AM Sérgio Basto wrote: > > > > Well I just re-tried openvdb with _smp_build_ncpus 1 and it still > > failed so I don't think we have a choice at this point. Perhaps it > > was hitting the 4GB max per process due to being 32bit? > > > > Have you try set in build the ulimit [1] . > On copr, copr already set the max number of files already by default > [2] have you check if you can build it on copr ? > No, and I don't have the time, it's not even my package, I just need it "fixed" so I can build OpenImageIO and its dependencies in my side-tag that should have been merged already. Also, I'm not sure there's any compelling reason to "save" OpenVDB or its dependencies on i686 but if someone wants to go to the trouble I'll throw away my side tag and start over, again... Thanks, Richard -- ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-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@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: [wsjt-devel] Problem with WSJT-X 2.7.0 RC3 and Hamlib +Flrig
On Sun, Jan 28, 2024 at 10:16 PM Black Michael wrote: > What rig? For some reason that call is not returning any value for your > rig when getting the current mode. > FT-991A Thanks, Richard ___ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
Re: HELP! What's up with OpenVDB?
On Mon, Jan 29, 2024 at 4:16 AM Jonathan Wakely wrote: > On Sun, 28 Jan 2024 at 15:18, Richard Shaw wrote: > > > > Well I upped the memory to 10GB and got it to build but the issue on > i686 with the wrong tbb package being pulled in has not been corrected by > any of the 4 maintainers of the package. > > I fixed tbb to stop installing tbb32.pc so the underlying cause should > be fixed in tbb-2021.11.0-5.fc40 and rebuilding openvdb should get the > right tbb now. > Not sure why it didn't work then, but it doesn't change the fact that the BR hadn't been updated in a very long time, using version 3 instead of date type release format. The last standard version release was 4.4 in 2016. More than likely all of the BRs need a refresh to the cmake format if it's supported by the package. Thanks, Richard -- ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-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@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
[wsjt-devel] Problem with WSJT-X 2.7.0 RC3 and Hamlib +Flrig
I decided to test out the RC3 release and everything comes up fine but as soon as I try to change TX frequency in the waterfall or make a contact I get something like this: Rig Control Error Hamlib error: Content-length: 168 xml_parse2: value returned='' xml_parse2: xml=' ' flrig_transaction: no value returned 4:flrig.c(600):flrig_transaction returning(8) 3:flrig.c(1701):flrig_get_mode returning(8) 2:flrig.c(2018):flrig_set_split_freq_mode returning(8) 1:rig_set_split_freq_mode: elapsed=22ms 1:rig.c(4843):rig_set_split_freq_mode returning(8) Protocol error Protocol error while setting split TX frequency and mode Timestamp: 2024-01-29T01:29:30.026Z --- - Everything I try in Flrig works perfectly. - Clicking the 1kc up and down arrows work fine in WSJT-X. - Test CAT and Test PTT in WSJT-X works fine. Thanks, Richard KF5OIM ___ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
Re: HELP! What's up with OpenVDB?
On Sun, Jan 28, 2024 at 9:55 AM Ben Beasley wrote: > Blender already excludes i686: > > > https://src.fedoraproject.org/rpms/blender/blob/8088da10c20e53ab0e1dd5de6fd3a2344bd288aa/f/blender.spec#_207 > > So does prusa-slicer: > > > https://src.fedoraproject.org/rpms/prusa-slicer/blob/44359e4b53c503cb61a60842abf991a01d1cb9db/f/prusa-slicer.spec#_68 > > Packages depending directly on openvdb are: > > $ fedrq wrsrc -s openvdb > OpenImageIO-2.4.17.0-1.fc40.src > blender-1:4.0.2-1.fc40.src > luxcorerender-2.7-0.10.beta1.fc40.src > openvkl-2.0.0-5.fc40.src > prusa-slicer-2.4.2-13.fc40.src > usd-23.11-2.fc40.src > > Of these, it looks like only OpenImageIO builds on i686. Packages > depending on it are: > > $ fedrq wrsrc -s OpenImageIO > OpenColorIO-2.2.1-6.fc40.src > blender-1:4.0.2-1.fc40.src > embree-4.3.0-2.fc40.src > luxcorerender-2.7-0.10.beta1.fc40.src > oidn-2.1.0-1.fc40.src > openshadinglanguage-1.12.14.0-9.fc40.src > usd-23.11-2.fc40.src > > Of those, only OpenColorIO builds on i686. Packages depending on it are: > > $ fedrq wrsrc -s OpenColorIO > OpenImageIO-2.4.17.0-1.fc40.src > blender-1:4.0.2-1.fc40.src > calligra-3.2.1-25.fc39.src > krita-5.2.2-1.fc40.src > luxcorerender-2.7-0.10.beta1.fc40.src > usd-23.11-2.fc40.src > > Of those, only calligra builds on i686, and it’s a leaf package. So, if > I haven’t missed anything, as long as i686 support is dropped from all > of calligra, OpenColorIO, OpenImageIO, and openvdb, then it should be OK. > Well I just re-tried openvdb with _smp_build_ncpus 1 and it still failed so I don't think we have a choice at this point. Perhaps it was hitting the 4GB max per process due to being 32bit? Thanks, Richard -- ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-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@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: HELP! What's up with OpenVDB?
Well I upped the memory to 10GB and got it to build but the issue on i686 with the wrong tbb package being pulled in has not been corrected by any of the 4 maintainers of the package. So I did a minimal update and changed the tbb BR's from pkgconf to cmake and a scratch build completed pulling in the correct tbb-devel on i686, but now two attempts at real builds fail... I think it's time to retire openvdb on i686 but blender and prusa-slicer would need to stop building for i686 first as first level BRs, I didn't dig any deeper into the dependency chain. Thanks, Richard -- ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-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@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: HELP! What's up with OpenVDB?
On Wed, Jan 24, 2024 at 10:56 PM Mamoru TASAKA wrote: > Richard Shaw wrote on 2024/01/25 12:43: > > See: > > https://src.fedoraproject.org/rpms/build-constraints-rpm-macros/blob/rawhide/f/macros.build-constraints > > The macro attemps to reduce parallel make jobs when the build needs > more memory than usual. > I figured it was something like that... That should probably be linked to the CMake Packaging guidelines somewhere! > Your [2] ppc64le build log actually says: > > g++: fatal error: Killed signal terminated program cc1plus > compilation terminated. > gmake[2]: *** > [openvdb/openvdb/CMakeFiles/openvdb_shared.dir/build.make:625: > openvdb/openvdb/CMakeFiles/openvdb_shared.dir/instantiations/GridOperators.cc.o] > Error 1 > gmake[2]: *** Deleting file > 'openvdb/openvdb/CMakeFiles/openvdb_shared.dir/instantiations/GridOperators.cc.o' > gmake[2]: Leaving directory > '/builddir/build/BUILD/openvdb-11.0.0/redhat-linux-build' > gmake[1]: *** [CMakeFiles/Makefile2:261: > openvdb/openvdb/CMakeFiles/openvdb_shared.dir/all] Error 2 > gmake[1]: *** Waiting for unfinished jobs > > So perhaps g++ process was killed by OOM. > So it looks like there needs to be further restrictions placed on ppc64le and s390x at a minimum and should probably look at discontinuing i686 builds long term. Thanks, Richard -- ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-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@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
HELP! What's up with OpenVDB?
So with the tbb[1] update OpenVDB is one of the stragglers having issues that need to be addressed before I can build OpenImageIO. Looking at the releng rebuilt attempt it failed on ppc64le. I kicked off the build again[2] and this time it failed on s390x: https://kojipkgs.fedoraproject.org//work/tasks/3860/112313860/build.log Just to check I did a local build for x86_64 and it completed, though I noted it only seemed to use about 3 cores of my 8 core / 12 thread processor. It had this on the cmake line: %cmake_build %limit_build -m 8192 But I haven been unable to decipher its exact purpose since google cannot find where `%limit_build` is documented. Thanks, Richard [1] https://bugzilla.redhat.com/show_bug.cgi?id=2036372 [2] https://koji.fedoraproject.org/koji/taskinfo?taskID=112313794 -- ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-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@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: Build error with GCC 14, not even a warning in GCC 13
On Tue, Jan 16, 2024 at 5:36 PM Aleksei Bavshin wrote: > Ah, I misread the include path. It's our package that is too old :( > https://src.fedoraproject.org/rpms/rapidjson/pull-request/4 should help. > It doesn't look like the pull request has gotten any attention. Perhaps it's time to initiate the non-responsive maintainer process? Thanks! Richard -- ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-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@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Build error with GCC 14, not even a warning in GCC 13
I'm working on getting a new dependency of one of my packages into Fedora:
https://github.com/socketio/socket.io-client-cpp/releases
After doing successful test builds locally in mock (no error output at all)
I used fedora-create-review but all the builds failed with:
In file included from
/builddir/build/BUILD/socket.io-client-cpp-3.1.0/src/internal/sio_packet.cpp:8:
/usr/include/rapidjson/document.h: In member function
‘rapidjson::GenericStringRef&
rapidjson::GenericStringRef::operator=(const
rapidjson::GenericStringRef&)’:
/usr/include/rapidjson/document.h:319:82: error: assignment of read-only
member ‘rapidjson::GenericStringRef::length’
319 | GenericStringRef& operator=(const GenericStringRef& rhs) { s =
rhs.s; length = rhs.length; }
|
~~~^~~~
gmake[2]: *** [CMakeFiles/sioclient.dir/build.make:121:
CMakeFiles/sioclient.dir/src/internal/sio_packet.cpp.o] Error 1
Full logs: https://koji.fedoraproject.org/koji/taskinfo?taskID=111852023
Is this a real error?
Thanks,
Richard
--
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-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@lists.fedoraproject.org
Do not reply to spam, report it:
https://pagure.io/fedora-infrastructure/new_issue
Re: Help in converting a Ubuntu install to Fedora
On Fri, Jan 5, 2024 at 1:08 PM Robert Moskowitz wrote: > > > On 1/5/24 08:24, Richard Shaw wrote: > > On Thu, Jan 4, 2024 at 9:50 PM Robert Moskowitz > wrote: > >> I wsa told to try: >> >> >>1. >>https://ardupilot.org/dev/docs/sitl-simulator-software-in-the-loop.html >>2. https://ardupilot.org/dev/docs/copter-sitl-mavproxy-tutorial.html >>3. >> >> https://ardupilot.org/dev/docs/setting-up-sitl-on-linux.html#setting-up-sitl-on-linux >> >> and it is #3 where converting Ubuntu instructions to Fedora that I am >> stuck. I can work with GIT, that part is easy. But when I get past that, >> I stall. >> >> >> Can anyone take a look at this and advise? >> > > The only Ubuntu specific command I saw was installing Flight Gear which > would translate to: > > $ sudo dnf install FlightGear > > > So > > Tools/environment_install/install-prereqs-ubuntu.sh -y > > or the alternative method > > are not needed? > I didn't dig past the first level link. It looks like that script does quite a lot. Unfortunately that's a bit too much to decipher for me right now. A significant portion does seem to just install different versions of packages depending on what version of Ubuntu you're running. Thanks, Richard -- ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-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/users@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: Help in converting a Ubuntu install to Fedora
On Thu, Jan 4, 2024 at 9:50 PM Robert Moskowitz wrote: > I wsa told to try: > > >1. >https://ardupilot.org/dev/docs/sitl-simulator-software-in-the-loop.html >2. https://ardupilot.org/dev/docs/copter-sitl-mavproxy-tutorial.html >3. > > https://ardupilot.org/dev/docs/setting-up-sitl-on-linux.html#setting-up-sitl-on-linux > > and it is #3 where converting Ubuntu instructions to Fedora that I am > stuck. I can work with GIT, that part is easy. But when I get past that, > I stall. > > > Can anyone take a look at this and advise? > The only Ubuntu specific command I saw was installing Flight Gear which would translate to: $ sudo dnf install FlightGear Thanks, RIchard -- ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-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/users@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
flrig: C++ warning help
While it's only a warning, I would like to "fix" it. When building flrig I'm seeing the following: widgets/font_browser.cxx: In member function '__ct_base .constprop': widgets/font_browser.cxx:202:52: warning: argument 1 value '18446744073709551615' exceeds maximum object size 9223372036854775807 [-Walloc-size-larger-than=] 202 | font_pairs = new font_pair[numfonts]; |^ The code can be found here: https://sourceforge.net/p/fldigi/flrig/ci/master/tree/src/widgets/font_browser.cxx#l201 Any hints would be appreciated. Thanks, Richard -- ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-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@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
OpenImageIO 2.5.x w/ soname bump
I plan to build OpenImageIO 2.5.x in rawhide in the near future. Affected packages to be built in a side tag: $ fedrq wr -F "name" -s OpenImageIO-devel OpenColorIO blender embree luxcorerender oidn openshadinglanguage usd Thanks, Richard FAS: hobbes1069 -- ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-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@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
scm issues?
I'm trying to do a pull on nonfree/unifi in master and it took about 3 minutes to complete. Thanks, Richard ___ rpmfusion-developers mailing list -- rpmfusion-developers@lists.rpmfusion.org To unsubscribe send an email to rpmfusion-developers-le...@lists.rpmfusion.org
Re: [wsjt-devel] Hamlib fork repository
On Tue, Nov 7, 2023 at 4:27 PM Matt Melling via wsjt-devel < wsjt-devel@lists.sourceforge.net> wrote: > Hi, > > I am hacking on the WSJT-X package in NixOS, and looking at how we can > split out the hamlib fork in to a separate package that can be shared > with our js8call package. > On Fedora we build with the native hamlib package. If you want to take a look: https://src.fedoraproject.org/rpms/wsjtx/blob/rawhide/f/wsjtx.spec Thanks, Richard KF5OIM ___ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
Re: [Fedora Change draft] Minizip transition to minizip-ng
On Mon, Oct 30, 2023 at 7:49 AM Lukas Javorsky wrote: > The possible remediation for this FTBFS packages are: > > Chromium -> Use bundled minizip library > Libdigidocpp -> Use bundled minizip library > OpenColorIO -> Don't upgrade minizip-ng to the new 4th version of API > (stay with minizip-ng-3.10.0). Not preferred as we want to have the latest > and greatest versions in Fedora. > > I've also included this in the change proposal in the *Impact* section. > > Most important are packages *blender, krita,* and *usd *which block the > upgrade [1] of OpenColorIO to the new version which supports the new > minizip API > As I mentioned in BZ, both krita and usd at least have PRs that fix building, but I did not test functionality. I haven't checked to see if they were merged upstream as of yet. So really it's just Blender that's the hold up. Thanks, Richard ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-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@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Stuck PPC build?
I'm working on updating unifi but the f39 package seems to be stuck building: https://koji.rpmfusion.org/koji/taskinfo?taskID=614375 I decided to try and cancel it so I could restart the build before submitting a ticket but that's not working for me either: $ koji-rpmfusion cancel 614375 2023-10-20 07:09:44,934 [ERROR] koji: GenericError: Invalid method: getKojiVersion Any ideas? Thanks, Richard ___ rpmfusion-developers mailing list -- rpmfusion-developers@lists.rpmfusion.org To unsubscribe send an email to rpmfusion-developers-le...@lists.rpmfusion.org
Re: How to deal with COPR and RPMAutoSpec
Never mind, I hadn't realized fedpkg had grown the ability to do COPR builds. Thanks, Richard ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-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@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
How to deal with COPR and RPMAutoSpec
I'm trying to test build packages before actually creating a side tag and doing real builds. I'm using rpkg to do the test builds but openshading language uses RPMAutoSpec. I've tried creating empty commits to bump the release but it does not appear to be working. What's the work around? Thanks, Richard ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-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@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: Heads up: OpenColorIO 2.3.0
Forgot to mention I'm doing the test builds here: https://copr.fedorainfracloud.org/coprs/hobbes1069/OIIO/builds/ Thanks, Richard ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-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@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: Heads up: OpenColorIO 2.3.0
On Mon, Sep 25, 2023 at 2:11 AM Sandro wrote: > On 24-09-2023 03:26, Richard Shaw wrote: > > I haven't been able to find the new command in my email history to find > > dependencies but my old script shows the following need to be rebuilt: > > > > blender > > krita > > luxcorerender > > OpenImageIO > > usd > > This looks correct according to `fedrq`: > > $ fedrq wr -s OpenColorIO-devel > OpenImageIO-2.4.15.0-1.fc40.src > blender-1:3.6.2-1.fc40.src > calligra-3.2.1-25.fc39.src > krita-5.1.5-5.fc39.src > luxcorerender-2.7-0.5.beta1.fc39.src > usd-23.08-1.fc40.src > Thanks for confirming. Status update: usd, krita, and Blender need patching for API changes in OpenColorIO. Of the three, the first two already have pull requests in process[1,2] so I used those. Only blender doesn't build now, and per the issue[1], they don't plan to until next year. Anyone want to look at how usd and krita were updated and propose a patch for blender? Thanks, Richard [1] https://github.com/PixarAnimationStudios/OpenUSD/pull/2651/commits/9fe8cf65ed05ec53f5ddbb5ffb08851e02f4adc8 [2] https://invent.kde.org/graphics/krita/-/merge_requests/1942 [3] https://projects.blender.org/blender/blender/issues/109244 ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-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@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Heads up: OpenColorIO 2.3.0
I haven't been able to find the new command in my email history to find dependencies but my old script shows the following need to be rebuilt: blender krita luxcorerender OpenImageIO usd I'll try them in a COPR first to make sure there aren't any issues. Thanks, Richard ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-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@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
aarch64 builders down?
I didn't see an open ticket[1] but wanted to ask here first as my unifi build[2] has been stuck for a while. Thanks, Richard [1] https://bugzilla.rpmfusion.org/buglist.cgi?component=Build%20System_id=22725=Infrastructure=--- [2] https://koji.rpmfusion.org/koji/taskinfo?taskID=610157 ___ rpmfusion-developers mailing list -- rpmfusion-developers@lists.rpmfusion.org To unsubscribe send an email to rpmfusion-developers-le...@lists.rpmfusion.org
Re: zlib-ng as a compat replacement for zlib
On Fri, Sep 1, 2023 at 9:02 AM Richard W.M. Jones wrote: > On Fri, Sep 01, 2023 at 07:10:59AM -0500, Richard Shaw wrote: > > Drive by comment because I found this thread interesting... > > > > What compression level was used for zstd? My understanding is that higher > > levels take longer to compress but decompression time remains virtually > the > > same. > > Seems to be the default level? Or at least it doesn't seem like it is > being set. Can you tell from this code: > > > https://gitlab.com/qemu-project/qemu/-/blob/17780edd81d27fcfdb7a802efc870a99788bd2fc/block/qcow2-threads.c#L176 Yeah didn't see anything referencing the `compression_level` property, and the default is 3. If compression performance doesn't matter as much I would try increasing it to maybe 9? The levels are 1 to 22 but I'm sure there's a diminishing return. Thanks, Richard ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-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@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: zlib-ng as a compat replacement for zlib
Drive by comment because I found this thread interesting... What compression level was used for zstd? My understanding is that higher levels take longer to compress but decompression time remains virtually the same. Thanks, Richard ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-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@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: pianobar has moved to Fedora
On Fri, Aug 25, 2023 at 4:11 AM Dominik 'Rathann' Mierzejewski via rpmfusion-developers wrote: > > > I also just checked and it is setup on release monitoring but for some > > reason it's saying the latest version is really the oldest... > > > > https://release-monitoring.org/project/320447/ > > > > Would it be good if there was an option to reverse the sorting? > > I'm not sure what you mean, I can see this: > > Latest version > 2022.04.01 (commit) > > It looks correct to me... > Ok, I have no idea what changed, but yesterday the oldest 2010 version was at the top of the list on the right and even when I went into Edit and did a test it came back with the 2010 version. I didn't actually make any changes. I should have gotten a screenshot because it's too weird to believe but I promise it was... Hopefully it stays "fixed". Thanks, Richard ___ rpmfusion-developers mailing list -- rpmfusion-developers@lists.rpmfusion.org To unsubscribe send an email to rpmfusion-developers-le...@lists.rpmfusion.org
Re: pianobar has moved to Fedora
On Thu, Aug 24, 2023 at 1:09 PM Dominik 'Rathann' Mierzejewski via rpmfusion-developers wrote: > Hello all, > > I've just approved pianobar for inclusion in Fedora. Existing maintainer > hobbes1069 was added to the Fedora package ACL. Let me know if anyone > else wants to be added to maintainer ACL in Fedora. > Thanks for doing that! I don't have as much time for packaging as I used to but will try to keep an eye on it from time to time. I also just checked and it is setup on release monitoring but for some reason it's saying the latest version is really the oldest... https://release-monitoring.org/project/320447/ Would it be good if there was an option to reverse the sorting? Thanks, Richard ___ rpmfusion-developers mailing list -- rpmfusion-developers@lists.rpmfusion.org To unsubscribe send an email to rpmfusion-developers-le...@lists.rpmfusion.org
Re: Donate 1 minute of your time to test upgrades from F38 to F39
On Wed, Aug 23, 2023 at 1:41 PM Steven A. Falco wrote: > On 8/23/23 02:22 PM, Miroslav Suchý wrote: > > dnf --releasever=39 --setopt=module_platform_id=platform:f39 \ > > --enablerepo=updates-testing \ > > $(rpm -q fedora-repos-modular >/dev/null && echo > --enablerepo=updates-testing-modular) \ > > --assumeno distro-sync > Problem 1: problem with installed package freecad-1:0.20.2-3.fc38.x86_64 >- freecad-1:0.20.2-3.fc38.x86_64 from @System does not belong to a > distupgrade repository >- nothing provides libboost_python311.so.1.81.0()(64bit) needed by > freecad-1:0.20.2-4.fc39.x86_64 from fedora >- nothing provides libboost_python311.so.1.81.0()(64bit) needed by > freecad-1:0.20.2-4.fc39.x86_64 from fedora-modular >- nothing provides libboost_python311.so.1.81.0()(64bit) needed by > freecad-1:0.20.2-4.fc39.x86_64 from updates-modular >- nothing provides libboost_python311.so.1.81.0()(64bit) needed by > freecad-1:0.20.2-4.fc39.x86_64 from updates-testing-modular > Problem 2: problem with installed package > freecad-data-1:0.20.2-3.fc38.noarch >- package freecad-data-1:0.20.2-4.fc39.noarch from fedora requires > freecad = 1:0.20.2-4.fc39, but none of the providers can be installed >- package freecad-data-1:0.20.2-4.fc39.noarch from fedora-modular > requires freecad = 1:0.20.2-4.fc39, but none of the providers can be > installed >- package freecad-data-1:0.20.2-4.fc39.noarch from updates-modular > requires freecad = 1:0.20.2-4.fc39, but none of the providers can be > installed >- package freecad-data-1:0.20.2-4.fc39.noarch from > updates-testing-modular requires freecad = 1:0.20.2-4.fc39, but none of the > providers can be installed >- freecad-data-1:0.20.2-3.fc38.noarch from @System does not belong to > a distupgrade repository >- nothing provides libboost_python311.so.1.81.0()(64bit) needed by > freecad-1:0.20.2-4.fc39.x86_64 from fedora >- nothing provides libboost_python311.so.1.81.0()(64bit) needed by > freecad-1:0.20.2-4.fc39.x86_64 from fedora-modular >- nothing provides libboost_python311.so.1.81.0()(64bit) needed by > freecad-1:0.20.2-4.fc39.x86_64 from updates-modular >- nothing provides libboost_python311.so.1.81.0()(64bit) needed by > freecad-1:0.20.2-4.fc39.x86_64 from updates-testing-modular > Problem 3: problem with installed package > python3-shiboken2-1:5.15.7-2.fc38.x86_64 >- package python3-shiboken2-1:5.15.7-2.fc38.x86_64 from @System > requires python(abi) = 3.11, but none of the providers can be installed >- package python3-shiboken2-1:5.15.7-2.fc38.x86_64 from fedora requires > python(abi) = 3.11, but none of the providers can be installed >- package python3-shiboken2-1:5.15.7-2.fc38.x86_64 from fedora-modular > requires python(abi) = 3.11, but none of the providers can be installed >- package python3-shiboken2-1:5.15.7-2.fc38.x86_64 from updates-modular > requires python(abi) = 3.11, but none of the providers can be installed >- package python3-shiboken2-1:5.15.7-2.fc38.x86_64 from > updates-testing-modular requires python(abi) = 3.11, but none of the > providers can be installed >- python3-3.11.4-1.fc38.x86_64 from @System does not belong to a > distupgrade repository > Problem 4: problem with installed package > python3-pyside2-1:5.15.7-2.fc38.x86_64 >- package python3-pyside2-1:5.15.7-2.fc38.x86_64 from @System requires > python(abi) = 3.11, but none of the providers can be installed >- package python3-pyside2-1:5.15.7-2.fc38.x86_64 from fedora requires > python(abi) = 3.11, but none of the providers can be installed >- package python3-pyside2-1:5.15.7-2.fc38.x86_64 from fedora-modular > requires python(abi) = 3.11, but none of the providers can be installed >- package python3-pyside2-1:5.15.7-2.fc38.x86_64 from updates-modular > requires python(abi) = 3.11, but none of the providers can be installed >- package python3-pyside2-1:5.15.7-2.fc38.x86_64 from > updates-testing-modular requires python(abi) = 3.11, but none of the > providers can be installed >- package python3-3.11.4-1.fc38.x86_64 from @System requires > python3-libs(x86-64) = 3.11.4-1.fc38, but none of the providers can be > installed >- python3-libs-3.11.4-1.fc38.x86_64 from @System does not belong to a > distupgrade repository > FreeCAD is a known issue since the upgrade to Python 3.12. PySide2 is not compatible with Python 3.12 and upstream has no intention of making it compatible as they are only supporting PySide6 for Qt6 now. There's also a TBB dependency issue. For now it would be better to use the appimage. Thanks, Richard ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-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:
Re: Upgraded machine to Fedora 38 and now suspending after 15 minues??
On Mon, Aug 21, 2023 at 9:01 AM Michael D. Setzer II via users < users@lists.fedoraproject.org> wrote: > > This wasn't just some developer's idea... IIRC the request for this > > change came from someone who sells systems with Linux pre-installed > > (Lenovo?), because this is a requirement for meeting power > > certifications needed for desktop/notebook systems. > > > > Question? If that is so, why couldn't they modify their Linux > pre-installed setup to have it set, rather than forcing everyone else > to have to have it as default? > > Since I did a dnf upgrade it didn't present any option saying it was > going to do this, or prompting for the option. Don't know if a clean > install would have presented any option.. > > Wonder how many people are going to be reporting machines as > broken since they keep shutting down because of thie FEATURE... > In my case my computer becomes completely unresponsive. Neither pressing reset, or holding down the power button have any effect forcing me to use the power supply switch. Not a very good end user experience. Thanks, Richard ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-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/users@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: [Freetel-codec2] Change to static codec2 for internal builds of FreeDV?
On Thu, Aug 10, 2023 at 2:56 PM david wrote: > Hi Richard, > > > I just went through a painful update and dependency rebuild in Fedora > > Rawhide for codec 1.2 and I don't really want to go through that > > again 2 more times for Fedora 37 and 38. > > Could you please explain where the pain points were? > Well there's the codec2/lpcnet issue but it looks like that's been addressed recently. There was also a circular dependency between ffmpeg and chromaprint. And there's still the issue with soversion bumps being highly discouraged within a Fedora release. As far as Fedora dependencies it's grown well past FreeDV: baresip ffmpeg freedv gnuradio lpcnetfreedv sdrangel sdrpp Another question I've been pondering - do you have any evidence that > anyone is actually using the Fedora FreeDV packages? > Unfortunately there's no good way to check. Thanks, Richard ___ Freetel-codec2 mailing list Freetel-codec2@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freetel-codec2
[Freetel-codec2] Change to static codec2 for internal builds of FreeDV?
So when I initially developed the CMake logic to build codec2 on the fly I set it up for shared libraries because those are often preferred and for windows, as long as the DLL was in the same folder everything worked fine. Fast forward a few years and codec2 is now included in many projects as a dependency, including ffmpeg in Fedora. Adding to that, Fedora highly discourages soname/soversion bumps in released versions of Fedora. I just went through a painful update and dependency rebuild in Fedora Rawhide for codec 1.2 and I don't really want to go through that again 2 more times for Fedora 37 and 38. I don't have a lot of development time these days but I may take a stab at making codec2 and lpcnet static builds but would appreciate some help. Also, being able to build from a specific release instead of master/main would be good as well. I may use the WSJTX superbuild CMake script as inspiration because official builds on Fedora do not have access to the internet. Everything required to build the project needs to be available. Thoughts? Thanks, Richard KF5OIM ___ Freetel-codec2 mailing list Freetel-codec2@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freetel-codec2
Re: Problem with ffmpeg and chromaprint circular dependency
Specifically I think this needs to be addressed if possible: # dnf repoquery --whatrequires libchromaprint\* | grep x86_64 Last metadata expiration check: 0:02:55 ago on Sun 06 Aug 2023 10:10:31 AM CDT. acoustid-fingerprinter-0:0.6-31.fc38.x86_64 chromaprint-tools-0:1.5.1-8.fc38.x86_64 clementine-0:1.4.0~rc2-3.fc38.x86_64 ffmpeg-libs-0:6.0-11.fc38.x86_64 ffmpeg-libs-0:6.0-6.fc38.x86_64 gstreamer1-plugins-bad-free-extras-0:1.22.1-1.fc38.x86_64 gstreamer1-plugins-bad-free-extras-0:1.22.5-1.fc38.x86_64 kid3-common-0:3.9.2-3.fc38.x86_64 kid3-common-0:3.9.4-1.fc38.x86_64 libavformat-free-0:6.0-2.fc38.x86_64 libavformat-free-0:6.0-4.fc38.x86_64 libchromaprint-devel-0:1.5.1-8.fc38.x86_64 mixxx-0:2.3.4-2.fc38.x86_64 mixxx-0:2.3.5-1.fc38.x86_64 strawberry-0:1.0.15-1.fc38.x86_64 strawberry-0:1.0.18-1.fc38.x86_64 vlc-core-1:3.0.19-0.3.fc38.1.x86_64 # dnf repoquery --requires libchromaprint\* Last metadata expiration check: 0:03:19 ago on Sun 06 Aug 2023 10:10:31 AM CDT. /usr/bin/pkg-config libavcodec.so.60 libavcodec.so.60()(64bit) libavcodec.so.60(LIBAVCODEC_60) libavcodec.so.60(LIBAVCODEC_60)(64bit) libavutil.so.58 libavutil.so.58()(64bit) libavutil.so.58(LIBAVUTIL_58) libavutil.so.58(LIBAVUTIL_58)(64bit) libc.so.6(GLIBC_2.14)(64bit) libc.so.6(GLIBC_2.4) libchromaprint(x86-32) = 1.5.1-8.fc38 libchromaprint(x86-64) = 1.5.1-8.fc38 libchromaprint.so.1 libchromaprint.so.1()(64bit) [SNIP] Thanks, Richard ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-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@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: Problem with ffmpeg and chromaprint circular dependency
On Sun, Aug 6, 2023 at 9:44 AM Sérgio Basto wrote: > On Sun, 2023-08-06 at 08:04 -0500, Richard Shaw wrote: > > From what I can tell in the spec file[1] for chromaprint, the only thing > that's supposed to depend on ffmpeg is the tools package, but it seems to > have found its way into libchromaprint[2] as well. > > I'm trying to build a new version of codec2 with a soname change but I'm > hitting this: > DEBUG util.py:442: Problem: package > libchromaprint-devel-1.5.1-11.fc39.i686 from build requires > libchromaprint.so.1, but none of the providers can be installed > DEBUG util.py:442:- package libchromaprint-devel-1.5.1-11.fc39.i686 > from build requires libchromaprint(x86-32) = 1.5.1-11.fc39, but none of the > providers can be installed > DEBUG util.py:442:- package libchromaprint-1.5.1-11.fc39.i686 from > build requires libavcodec.so.60, but none of the providers can be installed > DEBUG util.py:442:- package libchromaprint-1.5.1-11.fc39.i686 from > build requires libavcodec.so.60(LIBAVCODEC_60), but none of the providers > can be installed > DEBUG util.py:442:- conflicting requests > DEBUG util.py:442:- nothing provides libcodec2.so.1.0 needed by > libavcodec-free-6.0-10.fc39.i686 from build > > I'm guessing I don't have a choice but to do a bootstrap build of > libchromaprint without ffmpeg first... > > > > no, see my fork > > https://src.fedoraproject.org/fork/sergiomb/rpms/chromaprint/commits/rawhide > and specially commit > > https://src.fedoraproject.org/fork/sergiomb/rpms/chromaprint/c/0e39e40877b404970ab024c579283e50851db20c?branch=rawhide > Let me know if I missed something but those commits don't seem to have made their way into SCM so doesn't really help. Also, as far as I know there's no way to pass general options or --with / --without options to Koji. Thanks, Richard ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-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@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Problem with ffmpeg and chromaprint circular dependency
>From what I can tell in the spec file[1] for chromaprint, the only thing that's supposed to depend on ffmpeg is the tools package, but it seems to have found its way into libchromaprint[2] as well. I'm trying to build a new version of codec2 with a soname change but I'm hitting this: DEBUG util.py:442: Problem: package libchromaprint-devel-1.5.1-11.fc39.i686 from build requires libchromaprint.so.1, but none of the providers can be installed DEBUG util.py:442:- package libchromaprint-devel-1.5.1-11.fc39.i686 from build requires libchromaprint(x86-32) = 1.5.1-11.fc39, but none of the providers can be installed DEBUG util.py:442:- package libchromaprint-1.5.1-11.fc39.i686 from build requires libavcodec.so.60, but none of the providers can be installed DEBUG util.py:442:- package libchromaprint-1.5.1-11.fc39.i686 from build requires libavcodec.so.60(LIBAVCODEC_60), but none of the providers can be installed DEBUG util.py:442:- conflicting requests DEBUG util.py:442:- nothing provides libcodec2.so.1.0 needed by libavcodec-free-6.0-10.fc39.i686 from build I'm guessing I don't have a choice but to do a bootstrap build of libchromaprint without ffmpeg first... Thanks, Richard [1] https://src.fedoraproject.org/rpms/chromaprint/blob/rawhide/f/chromaprint.spec [2] https://koji.fedoraproject.org/koji/rpminfo?rpmID=35116382 ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-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@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Heads up: codec2 1.5.0 coming
I plan to update codec2 to version 1.5.0 and will perform all rebuilds in a side tag. Affected packages: baresip ffmpeg freedv gnuradio lpcnetfreedv sdrangel sdrpp Thanks, Richard ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-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@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: Direwolf FTBFS: Need C help
On Wed, Aug 2, 2023 at 7:14 AM Miroslav Lichvar wrote: > On Wed, Aug 02, 2023 at 06:47:58AM -0500, Richard Shaw wrote: > > I was poking around trying to fix the FTBFS problem with direwolf and it > > looks simple enough. As it has built before for years I assume it's > related > > to GCC 13. > > > > Here's the error: > > /builddir/build/BUILD/direwolf-1.6/src/direwolf.h:303:56: error: expected > > declaration specifiers or '...' before string constant > > 303 | #define strlcpy(dst,src,siz) > > strlcpy_debug(dst,src,siz,__FILE__,__func__,__LINE__) > > |^~~~ > > I think this is the new glibc 2.38 support of strlcpy. > > You need to modify direwolf.h to take the path of the other systems > #if defined(__OpenBSD__) || defined(__FreeBSD__) || defined(__APPLE__) > > e.g. by replacing it with #if 1 > > For an upstream patch it would be better to check for the > __GLIBC_PREREQ macro and __GLIBC_PREREQ(2, 38)), but the current glibc > header in rawhide still claims to be 2.37. > That got it. Thanks! Richard ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-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@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Orphaned qodem
I have orphaned qodem. I haven't used it in years and was only interested during a brief revival of the good ole' BBS days many years ago. https://src.fedoraproject.org/rpms/qodem Thanks, Richard ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-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@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Direwolf FTBFS: Need C help
I was poking around trying to fix the FTBFS problem with direwolf and it looks simple enough. As it has built before for years I assume it's related to GCC 13. Here's the error: /builddir/build/BUILD/direwolf-1.6/src/direwolf.h:303:56: error: expected declaration specifiers or '...' before string constant 303 | #define strlcpy(dst,src,siz) strlcpy_debug(dst,src,siz,__FILE__,__func__,__LINE__) |^~~~ And here's the code snippet in question: // These prevent /usr/include/gps.h from providing its own definition. #define HAVE_STRLCAT 1 #define HAVE_STRLCPY 1 #define DEBUG_STRL 1 #if DEBUG_STRL #define strlcpy(dst,src,siz) strlcpy_debug(dst,src,siz,__FILE__,__func__,__LINE__) #define strlcat(dst,src,siz) strlcat_debug(dst,src,siz,__FILE__,__func__,__LINE__) size_t strlcpy_debug(char *__restrict__ dst, const char *__restrict__ src, size_t siz, const char *file, const char *func, int line); size_t strlcat_debug(char *__restrict__ dst, const char *__restrict__ src, size_t siz, const char *file, const char *func, int line); #else #define strlcpy(dst,src,siz) strlcpy_debug(dst,src,siz) #define strlcat(dst,src,siz) strlcat_debug(dst,src,siz) size_t strlcpy_debug(char *__restrict__ dst, const char *__restrict__ src, size_t siz); size_t strlcat_debug(char *__restrict__ dst, const char *__restrict__ src, size_t siz); #endif /* DEBUG_STRL */ --- I tried moving the definitions above the #defines but that had no effect... Thanks, Richard ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-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@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: Help: Interrupted dnf update, second update fails with duplicate packages
On Mon, Jul 31, 2023 at 5:12 PM richard emberson wrote: > I had a "dnf update" interrupted. > > Running "dnf clean all" and then "dnf update" again results in: > > Running transaction check > Transaction check succeeded. > Running transaction test > The downloaded packages were saved in cache until the next successful > transaction. > You can remove cached packages by executing 'dnf clean packages'. > Error: Transaction test error: >file /usr/share/doc/glib2/NEWS from install of glib2-2.76.4-3.fc38.i686 > conflicts with file from package glib2-2.76.3-1.fc38.x86_64 >file /usr/share/locale/en_GB/LC_MESSAGES/glib20.mo from install of > glib2-2.76.4-3.fc38.i686 conflicts with file from package > glib2-2.76.3-1.fc38.x86_64 >file /usr/share/locale/pt_BR/LC_MESSAGES/glib20.mo from install of > glib2-2.76.4-3.fc38.i686 conflicts with file from package > glib2-2.76.3-1.fc38.x86_64 >... 160 lines of "... conflicts with file from package ..." > > Running "dnf check" gives: > NetworkManager-1:1.42.6-1.fc38.x86_64 is a duplicate with > NetworkManager-1:1.42.8-1.fc38.x86_64 > ... > systemd-253.5-1.fc38.x86_64 is a duplicate with systemd-253.7-1.fc38.x86_64 > ... > systemd-udev-253.5-1.fc38.x86_64 is a duplicate with > systemd-udev-253.7-1.fc38.x86_64 > ... > xxhash-libs-0.8.1-4.fc38.x86_64 is a duplicate with > xxhash-libs-0.8.2-1.fc38.x86_64 > Error: Check discovered 430 problem(s) > > > What is the problem (aside from the fact that I interrupted the update) and > How can I recover? > An equivalent for yum-complete-transaction was requested but never implemented. https://bugzilla.redhat.com/show_bug.cgi?id=1091702 There's probably a way to use `dnf repoquery` based commands to list the problem packages and them remove them. Have you tried doing an update with --allowerasing? Thanks, Richard ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-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/users@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: python3-pyside2 and Python 3.12
On Thu, Jul 13, 2023 at 5:10 PM Kevin Kofler via devel < devel@lists.fedoraproject.org> wrote: > Richard Shaw wrote: > > # FIXME This patch is completely meaningless in the context of C++. > > # It is a workaround for a pyside2 build failure with Qt 5.15.9, > > # pyside2 5.15.9, clang 16.0.1 -- the generated code thinks a > > # not otherwise specified "Type" is in fact a > > # QFlags, causing many functions > > # looking for a QEvent::Type to be bogus. > > # Since there are no side effects to superfluously specifying > > # QEvent::Type instead of plain "Type" in a QEvent derived class, > > # this workaround is acceptable, if not nice. > > Patch5: qtbase-5.15.9-work-around-pyside2-brokenness.patch > [snip] > > [1] > > > https://github.com/OpenMandrivaAssociation/qt5-qtbase/blob/master/qtbase-5.15.9-work-around-pyside2-brokenness.patch > > I think we can apply this, the extra disambiguation should not hurt indeed. > Any progress on this? I can submit a BZ ticket for tracking if needed. Thanks, Richard ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-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@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: sleeping machine?
On Fri, Jul 21, 2023 at 7:04 AM Grumpey wrote: > > On Fri, Jul 21, 2023 at 8:01 AM Richard Shaw wrote: > >> On Fri, Jul 21, 2023 at 5:35 AM Barry wrote: >> >>> >>> > On 21 Jul 2023, at 09:06, Patrick Dupre wrote: >>> > >>> > Hello, >>> > >>> > Since I update from fedora36 to 38, I am in trouble to connect to my >>> > machine by using dwagent. >>> > One reason could be that when I am not logged on the machine, it falls >>> to >>> > sleep, and it does not accept to serve dwagent. >>> > 1) Is it possible? >>> > 2) It is possible, how can I keep the service (dwagent) really alive >>> >>> In f38 gnome defaults to going to sleep when idle. Is that the problem? >>> You should be able to change the power management settings to avoid that >>> happening. >> >> >> Strange issue I recently had after upgrading to F38. If I reboot my >> computer and do not log in it seems to get locked up in a strange sleep >> state. >> >> Holding the power button does nothing. Pressing reset does nothing. I >> have to turn off the power supply to restart the computer. >> >> If I log in, everything is fine as I have automatic suspend disabled, but >> this doesn't appear to be "system wide" somehow. >> > You may want to have a look at, > https://discussion.fedoraproject.org/t/gnome-suspends-after-15-minutes-of-user-inactivity-even-on-ac-power/79801 > > Thanks! That was very helpful. Richard ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-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/users@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: sleeping machine?
On Fri, Jul 21, 2023 at 5:35 AM Barry wrote: > > > On 21 Jul 2023, at 09:06, Patrick Dupre wrote: > > > > Hello, > > > > Since I update from fedora36 to 38, I am in trouble to connect to my > > machine by using dwagent. > > One reason could be that when I am not logged on the machine, it falls to > > sleep, and it does not accept to serve dwagent. > > 1) Is it possible? > > 2) It is possible, how can I keep the service (dwagent) really alive > > In f38 gnome defaults to going to sleep when idle. Is that the problem? > You should be able to change the power management settings to avoid that > happening. Strange issue I recently had after upgrading to F38. If I reboot my computer and do not log in it seems to get locked up in a strange sleep state. Holding the power button does nothing. Pressing reset does nothing. I have to turn off the power supply to restart the computer. If I log in, everything is fine as I have automatic suspend disabled, but this doesn't appear to be "system wide" somehow. Thanks, Richard ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-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/users@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: python3-pyside2 and Python 3.12
I was able to work around that error but now hitting the following, and the
crumb trail I followed seems to indicate that this needs to be fixed in
Qt5, not PySide2[1]
In file included from
/builddir/build/BUILD/pyside-setup-opensource-src-5.15.10/redhat-linux-build/sources/pyside2/PySide2/QtGui/PySide2/QtGui/qdragmoveevent_wrapper.cpp:63:
/builddir/build/BUILD/pyside-setup-opensource-src-5.15.10/redhat-linux-build/sources/pyside2/PySide2/QtGui/PySide2/QtGui/qdragmoveevent_wrapper.h:55:220:
error: no member named 'DragMove' in 'QOpenGLShader'; did you mean simply
'DragMove'?QDragMoveEventWrapper(const QPoint & pos,
QFlags actions, const QMimeData * data,
QFlags buttons, QFlags modifiers,
QFlags type = QOpenGLShader::DragMove);
^~~
DragMove
/usr/include/qt5/QtCore/qcoreevent.h:107:9: note: 'DragMove' declared here
DragMove = 61, // drag moves in widget
^
In file included from
/builddir/build/BUILD/pyside-setup-opensource-src-5.15.10/redhat-linux-build/sources/pyside2/PySide2/QtGui/PySide2/QtGui/qdragmoveevent_wrapper.cpp:63:
/builddir/build/BUILD/pyside-setup-opensource-src-5.15.10/redhat-linux-build/sources/pyside2/PySide2/QtGui/PySide2/QtGui/qdragmoveevent_wrapper.h:55:213:
error: no viable conversion from 'QEvent::Type' to
'QFlags'
QDragMoveEventWrapper(const QPoint & pos, QFlags
actions, const QMimeData * data, QFlags buttons,
QFlags modifiers,
QFlags type = QOpenGLShader::DragMove);
^
/usr/include/qt5/QtCore/qflags.h:89:7: note: candidate constructor (the
implicit copy constructor) not viable: no known conversion from
'QEvent::Type' to 'const QFlags &' for 1st argument
class QFlags
^
/usr/include/qt5/QtCore/qflags.h:89:7: note: candidate constructor (the
implicit move constructor) not viable: no known conversion from
'QEvent::Type' to 'QFlags &&' for 1st argument
/usr/include/qt5/QtCore/qflags.h:121:29: note: candidate constructor not
viable: no known conversion from 'QEvent::Type' to
'QOpenGLShader::ShaderTypeBit' for 1st argument
Q_DECL_CONSTEXPR inline QFlags(Enum flags) noexcept : i(Int(flags)) {}
^
/usr/include/qt5/QtCore/qflags.h:123:80: note: candidate constructor not
viable: no known conversion from 'QEvent::Type' to 'Zero' (aka 'int
(QFlags::Private::*)') for 1st argument
QT_DEPRECATED_X("Use default constructor instead") Q_DECL_CONSTEXPR
inline QFlags(Zero) noexcept : i(0) {}
^
/usr/include/qt5/QtCore/qflags.h:125:29: note: candidate constructor not
viable: no known conversion from 'QEvent::Type' to 'QFlag' for 1st argument
Q_DECL_CONSTEXPR inline QFlags(QFlag flag) noexcept : i(flag) {}
^
/usr/include/qt5/QtCore/qflags.h:127:29: note: candidate constructor not
viable: no known conversion from 'QEvent::Type' to
'std::initializer_list' for 1st argument
Q_DECL_CONSTEXPR inline QFlags(std::initializer_list flags)
noexcept
^
/builddir/build/BUILD/pyside-setup-opensource-src-5.15.10/redhat-linux-build/sources/pyside2/PySide2/QtGui/PySide2/QtGui/qdragmoveevent_wrapper.h:55:213:
note: passing argument to parameter 'type' here
QDragMoveEventWrapper(const QPoint & pos, QFlags
actions, const QMimeData * data, QFlags buttons,
QFlags modifiers,
QFlags type = QOpenGLShader::DragMove);
^
/builddir/build/BUILD/pyside-setup-opensource-src-5.15.10/redhat-linux-build/sources/pyside2/PySide2/QtGui/PySide2/QtGui/qdragmoveevent_wrapper.cpp:103:240:
error: no matching constructor for initialization of 'QDragMoveEvent'
QDragMoveEventWrapper::QDragMoveEventWrapper(const QPoint & pos,
QFlags actions, const QMimeData * data,
QFlags buttons, QFlags modifiers,
QFlags type) : QDragMoveEvent(pos, actions,
data, buttons, modifiers, type)
^
/usr/include/qt5/QtGui/qevent.h:684:5: note: candidate constructor not
viable: no known conversion from 'QFlags' to
'Type' for 6th argument
QDragMoveEvent(const QPoint , Qt::DropActions actions, const
QMimeData *data,
In the OpenMandriva package they have the following:
# FIXME This patch is completely meaningless in the context of C++.
# It is a workaround for a pyside2 build failure with Qt 5.15.9,
# pyside2 5.15.9, clang 16.0.1 -- the generated code thinks a
# not otherwise specified "Type" is in fact a
# QFlags, causing many functions
# looking for a QEvent::Type to be bogus.
# Since there are no side effects to superfluously specifying
# QEvent::Type instead of plain "Type" in a QEvent derived class,
# this workaround is acceptable, if not nice.
Patch5: qtbase-5.15.9-work-around-pyside2-brokenness.patch
Thanks,
Richard
[1]
python3-pyside2 and Python 3.12
So it looks like upstream has no intention of supporting Python 3.12 in Pyside2 (5.15.x series), only in Pyside6 which AFAIK requires Qt6. https://bugreports.qt.io/browse/PYSIDE-2388 Porting is non-trivial and Python upstream does not provide a porting guide. https://docs.python.org/3/c-api/unicode.html#c.PyUnicode_AS_UNICODE Says to replace PyUnicode_AS_UNICODE with PyUnicode_nBYTE_DATA which also requires use of the KIND and READY functions. So now what? Thanks, Richard ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-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@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: Modernize Thread Building Blocks for Fedora 39
On Thu, Jul 6, 2023 at 5:41 AM Jonathan Wakely wrote: > > > > Wouldn't it be better to just update OpenCascade to its new upstream > version in that sidetag as well instead of doing a compat package for it? > > Define better. > To be clear, I'm not "doing a compat package" for it. I'm just > changing one line in the spec file and rebuilding it against > tbb2020.3-devel (which is currently identical to tbb-devel). > That just means the OpenCascade package in rawhide won't be broken > when tbb gets updated. > > > The new OpenCascade actually requires the new TBB and can't be built > with the older version. See > https://bugzilla.redhat.com/show_bug.cgi?id=2217295. > > Yes, I'm aware of the bugzilla (it's blocked by #2036372 which is this > change). > There's no guarantee that the new version won't have new issues and not be a simple update and rebuild. I don't want to hold things up. For that reason I'm good with the plan as is. Once things have settled in Rawhide I can do test builds of the new version with latest TBB. Thanks, Richard ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-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@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Intent to retire OpenCOLLADA
For anyone who didn't see discussion on the list OpenCOLLADA upstream hasn't seen a commit since 2018 and no one has stepped up to port it to pcre2. I tried to convert it to use the bundled pcre as a stop gap to keep it going a bit further but it installs the library instead of building statically. Anyone good with CMake could fix this but at this point I think it's just time to retire it. If anyone wants to take it over let me know otherwise I plan to retire early next week. Thanks, Richard ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-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@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: Announcing fmt library soversion bump
On Wed, Jun 28, 2023 at 6:37 AM Richard Shaw wrote: > On Wed, Jun 28, 2023 at 6:12 AM Vitaly Zaitsev via devel < > devel@lists.fedoraproject.org> wrote: > >> Results: 37 builds succeeded, 19 failed. >> >> gnuradio >> > > Issue filed upstream: > https://github.com/gnuradio/gnuradio/issues/6735 > I'm currently at work but if a proven packager wants to try the solution proposed in the above that would be helpful. Thanks, Richard ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-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@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: Announcing fmt library soversion bump
On Wed, Jun 28, 2023 at 6:12 AM Vitaly Zaitsev via devel <
devel@lists.fedoraproject.org> wrote:
> Results: 37 builds succeeded, 19 failed.
>
> gnuradio
>
Issue filed upstream:
https://github.com/gnuradio/gnuradio/issues/6735
Also, not all the maintainers may review the devel list as closely. In the
past when I've had a lot of affected packages I wrote a simple bash script
that took the package names and output the -
maintain...@fedoraproject.org email so I could copy and paste it into my
email client.
Not quite the way I did it but ChatGPT came up with this:
```
#!/bin/bash
# Specify the input file containing package names (one per line)
input_file="package_names.txt"
# Initialize an empty string to store the email addresses
email_addresses=""
# Read each package name from the input file
while IFS= read -r package_name; do
# Construct the email address and append it to the string
email_address="${package_name}-maintain...@fedoraproject.org"
email_addresses+="${email_address};"
done < "$input_file"
# Remove the trailing semicolon, if any
email_addresses=${email_addresses%;}
# Print the final email addresses string
echo "$email_addresses"
```
Thanks,
Richard
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-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@lists.fedoraproject.org
Do not reply to spam, report it:
https://pagure.io/fedora-infrastructure/new_issue
Re: F39 Change Proposal: Build Fedora Workstation live ISO with Image Builder (System-Wide)
On Mon, Jun 26, 2023 at 10:02 AM Michal Schorm wrote: > > Moreover, it's designed to give the end users a simple workflow to build > their own custom images. > > That's something I'd be interested in. > I always have an USB drive (or several) with Fedora ISO(s) lying > around, being handy from time to time. > Having them customized *easily*, sounds like a great thing to have. > Yes, one of the reasons I still keep System Rescue CD around is it already has gparted installed which is one of the rescue apps I use the most often. Thanks, Richard ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-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@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: avoid nouveau with kernel 6.3?
On Thu, Jun 15, 2023 at 8:23 AM Tom Horsley wrote: > On Thu, 15 Jun 2023 07:55:10 -0400 > Neal Becker wrote: > > > https://www.phoronix.com/news/Avoid-Nouveau-Linux-6.3 > > I give nouveau a chance every time I install a new fedora, eventually > (2 hours, 2 weeks, it varies) I get a video crash and frozen > desktop, then I install the rpmfusion nvidia drivers. > Yeah the akmods MOSTLY worked fine. Sometimes I would have to rm -f the package and let it rebuild for some reason and occasionally builds would fail. Not a good end user experience especially if you're not that technical. I switched to AMD and for the most part it's just "worked". Previously with a RX580 and now with a RX 6550XT. Other than the crazy graphics card prices, I have no regrets and have no plans to switch back. Thanks, Richard ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-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/users@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: libftdi: Failure to create output directory (aarch64 only)
On Tue, Jun 6, 2023 at 4:17 AM Dan Horák wrote: > On Tue, 6 Jun 2023 11:00:39 +0200 > Dominik 'Rathann' Mierzejewski wrote: > > > On Tuesday, 06 June 2023 at 10:55, Dan Horák wrote: > > > On Tue, 6 Jun 2023 09:50:09 +0200 > > > Dan Horák wrote: > > > > > > > On Mon, 5 Jun 2023 17:53:59 -0500 > > > > Richard Shaw wrote: > > > > > > > > > I just saw this[1] on the packager dashboard: > > > > > > > > > > error: Could not create output directory > > > > > /builddir/build/BUILD/libftdi1-1.5/redhat-linux-build/doc/xml > > > > > > > > > > Full log: > > > > > > https://kojipkgs.fedoraproject.org/work/tasks/5182/101845182/build.log > > > > > > > > > > Is this a known issue? > > > > > > > > > > [1] > https://koschei.fedoraproject.org/package/libftdi?collection=f39 > > > > > > > > it is an interesting issue, because my fresh scratch build [2] runs > > > > well on aarch64, but fails on s390x with the same error as yours > > > > and with a different error on ppc64le ... I wonder if it could be a > > > > "parallel make" issue. > > > > > > > > [2] https://koji.fedoraproject.org/koji/taskinfo?taskID=101861225 > > > > > > I think it is a parallel make issue, with an explicit "-j1" the builds > > > are passing OK > > > > > > https://koji.fedoraproject.org/koji/taskinfo?taskID=101862160 > > > https://koji.fedoraproject.org/koji/taskinfo?taskID=101862632 > > > > > > Perhaps it explains also the previous failures seen by koschei ... > > > > Reporting these upstream is best. I've had a similar issue with INN for > > years, but it has been fixed: > > https://github.com/InterNetNews/inn/issues/206 . > > right, but the upstream mailing list looks like a black hole from a > contributor point of view. But thanks to the SUSE maintainer and > http://developer.intra2net.com/mailarchive/html/libftdi/2023/msg5.html > we have the fix I believe. > Thanks all! I'm not the primary maintainer but I didn't remember having this issue in the past so didn't even think it would be a parallel make issue. Richard ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-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@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
libftdi: Failure to create output directory (aarch64 only)
I just saw this[1] on the packager dashboard: error: Could not create output directory /builddir/build/BUILD/libftdi1-1.5/redhat-linux-build/doc/xml Full log: https://kojipkgs.fedoraproject.org/work/tasks/5182/101845182/build.log Is this a known issue? [1] https://koschei.fedoraproject.org/package/libftdi?collection=f39 ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-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@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: OpenCOLLADA need a little c++ help
On Mon, May 29, 2023 at 8:26 AM Sam Varshavchik
wrote:
> Richard Shaw writes:
>
> > error: possibly dangling reference to a temporary [-Werror=dangling-
> > reference]
> > 315 | const auto & parents =
> > dae.root().selectNodes("//*[@sid]/..");
>
> The quickest solution is just add a pragma to shut it up.
>
> > The code in question[2] is:
> > // InstanceWithExtra and other with "url" attribute
> > const auto & instances = root().selectNodes(
>
> Find where selectNodes() is defined. Add
>
> #pragma GCC diagnostic push
> #pragma GCC diagnostic ignored "-Wdangling-reference"
>
> before the definition, and
>
> #pragma GCC diagnostic pop
>
> after it.
>
That's what I ended up doing, it turns out there were structures like this
in about 7 places in that file and several more in another, it just got
through two before the build failed previously. I ended up using the
approach for the whole file and then fixed a couple of #include
since you don't get it for free anymore and the build completed.
Thanks!
Richard
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-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@lists.fedoraproject.org
Do not reply to spam, report it:
https://pagure.io/fedora-infrastructure/new_issue
OpenCOLLADA need a little c++ help
OpenCOLLADA has been failing to build with gcc 13 due to[1]:
error: possibly dangling reference to a temporary
[-Werror=dangling-reference]
315 | const auto & parents =
dae.root().selectNodes("//*[@sid]/..");
The code in question[2] is:
// InstanceWithExtra and other with "url" attribute
const auto & instances = root().selectNodes(
xpath_all + Strings::instance_animation +
xpath_or_all + Strings::instance_camera +
xpath_or_all + Strings::instance_controller +
xpath_or_all + Strings::instance_effect +
xpath_or_all + Strings::instance_force_field +
xpath_or_all + Strings::instance_formula +
xpath_or_all + Strings::instance_geometry +
xpath_or_all + Strings::instance_image +
xpath_or_all + Strings::instance_joint +
xpath_or_all + Strings::instance_kinematics_model +
xpath_or_all + Strings::instance_kinematics_scene +
xpath_or_all + Strings::instance_light +
xpath_or_all + Strings::instance_node +
xpath_or_all + Strings::instance_physics_material +
xpath_or_all + Strings::instance_physics_model +
xpath_or_all + Strings::instance_physics_scene +
xpath_or_all + Strings::instance_visual_scene
);
for (auto instance : instances)
if (auto url = instance.attribute(Strings::url))
onAnyDAEURI(instance.line(), url.value());
There's a 2nd instance of the error but I think I can fix it once the path
forward on the first is addressed.
Thanks,
Richard
[1] https://github.com/KhronosGroup/OpenCOLLADA/issues/661
[2]
https://github.com/KhronosGroup/OpenCOLLADA/blob/master/DAEValidator/library/src/Dae.cpp#L78
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-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@lists.fedoraproject.org
Do not reply to spam, report it:
https://pagure.io/fedora-infrastructure/new_issue
Re: OpenColorIO builds failing due to doxygen patch level update?
On Sat, May 27, 2023 at 4:48 AM Vitaly Zaitsev via devel < devel@lists.fedoraproject.org> wrote: > On 26/05/2023 14:07, Richard Shaw wrote: > > Doxygen was updated from 1.9.6 to 1.9.7 which I would assume should be a > > pretty harmless update > > Some Doxygen minor updates breaks something. That's why I disabled docs > generation in all my packages. Users can easily view docs online. > That's unfortunate... I reported it to OpenColorIO first to get their take before reporting it to upstream doxygen. I need to be subscribed to another mailing list like I need another hole in my head. Thanks, Richard ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-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@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
OpenColorIO builds failing due to doxygen patch level update?
On a side note I love the packager dashboard! I noticed that OpenColorIO builds in rawhide were failing[1] and took a look at the logs and the errors seem to be around doxygen: In file included from /builddir/build/BUILD/OpenColorIO-2.2.1/src/bindings/python/PyOpenColorIO.h:18, from /builddir/build/BUILD/OpenColorIO-2.2.1/src/bindings/python/PyColorSpaceSet.cpp:4: /builddir/build/BUILD/OpenColorIO-2.2.1/src/bindings/python/PyColorSpaceSet.cpp: In function 'void OpenColorIO_v2_2::bindPyColorSpaceSet(pybind11::module&)': /builddir/build/BUILD/OpenColorIO-2.2.1/redhat-linux-build/docs/_doxygen/docstrings.h:14:58: error: '__doc_PyOpenColorIO_ConstColorSpaceSetRcPtr_operator_sub' was not declared in this scope 14 | #define __DOC4(n1, n2, n3, n4) __doc_##n1##_##n2##_##n3##_##n4 | ^~ Doxygen was updated from 1.9.6 to 1.9.7 which I would assume should be a pretty harmless update. I checked Bugzilla and there is only one bug open for doxygen which is unrelated. Anyone else noticed any issues? OpenColorIO version has not changed in some time... Thanks, Richard [1] https://koschei.fedoraproject.org/package/OpenColorIO?collection=f39 ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-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@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: [wsjt-devel] COPR build for 2.7.0 RC1
On Tue, May 23, 2023 at 9:42 AM Jeff Stillinger via wsjt-devel < wsjt-devel@lists.sourceforge.net> wrote: > Yes, I think we need a focused effort as a whole ham radio community on > 9. I love what they have done with Rocky 9 (RHEL 9) so far. It was > just the "face lift" that 8 needed. However, 9 is falling short on > some key libraries. Hamlib was there, but GNURadio isn't. Of course, > WSJT-X had to be built, but at least it built nicely. In fact, > everything needed to be built from source.It would be a great thing > to help push 9 along. > I resubmitted the COPR build so there is now one for EL9. Once 2.7.0 goes to general release I'll build in Fedora proper. Thanks, Richard ___ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
[wsjt-devel] COPR build for 2.7.0 RC1
I have just completed builds for all released versions of Fedora and EPEL 8. Let me know if there's any interest in EPEL 9. https://copr.fedorainfracloud.org/coprs/hobbes1069/WSJT/build/5941850/ Thanks, Richard KF5OIM ___ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
Re: [wsjt-devel] Compile fails
On Mon, May 22, 2023 at 6:59 AM Brian Morrison via wsjt-devel < wsjt-devel@lists.sourceforge.net> wrote: > On Sun, 21 May 2023 21:31:44 -0500 > Richard Shaw via wsjt-devel wrote: > > > On Sun, May 21, 2023 at 9:13 PM jarmo via wsjt-devel < > > wsjt-devel@lists.sourceforge.net> wrote: > > > > > Did git pull for wsjtx, tried to compile, failed... > > > > > > /home/oh1mrr/wsjtx/qmap/libqmap/q65c.f90:23:39: > > > > > >23 |ndepth,ndiskdat,neme,newdat,nfa,nfb,nfcal,nfshift, > > >& > > > | 1 > > > Virhe: Symbol ”nfa” at (1) is USE associated from module ”q65” and > > > cannot occur in COMMON > > > gmake[2]: *** [qmap/libqmap/CMakeFiles/qmap_impl.dir/build.make:336: > > > qmap/libqmap/CMakeFiles/qmap_impl.dir/q65c.f90.o] Error 1 > > > gmake[2]: *** Odotetaan keskeneräisiä töitä > > > gmake[1]: *** [CMakeFiles/Makefile2:2109: > > > qmap/libqmap/CMakeFiles/qmap_impl.dir/all] Error 2 > > > gmake[1]: *** Odotetaan keskeneräisiä töitä > > > [ 79%] Linking CXX static library libqcp.a > > > [ 79%] Built target qcp > > > gmake: *** [Makefile:156: all] Error 2 > > > > > > > Getting the same error trying to build 2.7.0-rc1 for Fedora. > > > > Thanks, > > Richard > > KF5OIM > > Patch provided by K7FU that fixes this: > I found the previous email, unfortunately patch didn't like the line endings as copied out of said email. I ended up creating a fresh patch using quilt with the email as a guide and that got me going. Thanks, Richard ___ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
Re: [wsjt-devel] Compile fails
On Sun, May 21, 2023 at 9:13 PM jarmo via wsjt-devel < wsjt-devel@lists.sourceforge.net> wrote: > Did git pull for wsjtx, tried to compile, failed... > > /home/oh1mrr/wsjtx/qmap/libqmap/q65c.f90:23:39: > >23 |ndepth,ndiskdat,neme,newdat,nfa,nfb,nfcal,nfshift, >& > | 1 > Virhe: Symbol ”nfa” at (1) is USE associated from module ”q65” and cannot > occur in COMMON > gmake[2]: *** [qmap/libqmap/CMakeFiles/qmap_impl.dir/build.make:336: > qmap/libqmap/CMakeFiles/qmap_impl.dir/q65c.f90.o] Error 1 > gmake[2]: *** Odotetaan keskeneräisiä töitä > gmake[1]: *** [CMakeFiles/Makefile2:2109: > qmap/libqmap/CMakeFiles/qmap_impl.dir/all] Error 2 > gmake[1]: *** Odotetaan keskeneräisiä töitä > [ 79%] Linking CXX static library libqcp.a > [ 79%] Built target qcp > gmake: *** [Makefile:156: all] Error 2 > Getting the same error trying to build 2.7.0-rc1 for Fedora. Thanks, Richard KF5OIM ___ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
SPDX identifier for Expat license?
So subject kind of says it all, but to follow up, when I google Fedora known good licenses I get this: https://fedoraproject.org/wiki/Licensing:Main#SoftwareLicenses Which uses the old license identifiers, so there's that. And licensecheck is a PITA because I have to always add "--shortname-scheme=spdx" and it still doesn't give it to us in the format we want. Sure I could make my own script or alias to do this, and I hate to be a broken record but maybe people would adopt the new format faster if we gave them the tools to make it easy. I have about 5% of the time I used to be able to devote to packaging these days. Thanks, Richard ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-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@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: Any x86_64 Fedora Tablets out there?
On Mon, May 8, 2023 at 12:52 AM ToddAndMargo via users < users@lists.fedoraproject.org> wrote: > Hi All, > > I ask this every so often. > > Anyone know of any x86_64 Fedora Tablets out there? > I have Fedora installed on a MS Surface GO 2 (now obsolete, the 3 is out) but it "mostly works fine". It runs faster than Windows 10 on the GO's limited CPU (usually Pentium Gold or Core-my something or other 2 core processor). The only thing I have to fidget with is I can't double-tap the title bar to maximize the windows using the touchscreen. Probably something fixible with Gnome Tweaks? Thanks, Richard ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-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/users@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: problem downloading rpms with wifi
On Sun, Apr 30, 2023 at 8:43 PM Bill Cunningham wrote: > On 4/30/2023 9:28 PM, Richard Shaw wrote: > > On Sun, Apr 30, 2023 at 7:49 PM Bill Cunningham > wrote: > >> >> Fedora 38 - x86_64 [=== ] --- B/s | 0 B --:-- ETA >> Fedora 38 - x86_64 0.0 B/s | 0 B 00:00 >> Errors during downloading metadata for repository 'fedora': >>- Curl error (6): Couldn't resolve host name for >> https://mirrors.fedoraproject.org/metalink?repo=fedora-38=x86_64 >> [Could not resolve host: mirrors.fedoraproject.org] >> Error: Failed to download metadata for repo 'fedora': Cannot prepare >> internal mirrorlist: Curl error (6): Couldn't resolve host name for >> https://mirrors.fedoraproject.org/metalink?repo=fedora-38=x86_64 >> [Could not resolve host: mirrors.fedoraproject.org] >> >> Any suggestions? >> > > Maybe a DNS issue? Does web browsing work fine? Could try using google > instead of your internet provider, forcing DNS to 8.8.8.8. > > Thanks, > Richard > > I can't download lynx or links to try cli web browsing. When installed and > using the GUI firefox seems to work ok. Is there a host file that I could > input google's DNS servers? What is this resolv.conf? > Assuming you can get to settings (running Gnome?) then just turn off the automatic settings for DNS and set it manually. 8.8.8.8 and 8.8.4.4 Thanks, Richard ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-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/users@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: problem downloading rpms with wifi
On Sun, Apr 30, 2023 at 7:49 PM Bill Cunningham wrote: > > Fedora 38 - x86_64 [=== ] --- B/s | 0 B --:-- ETA > Fedora 38 - x86_64 0.0 B/s | 0 B 00:00 > Errors during downloading metadata for repository 'fedora': >- Curl error (6): Couldn't resolve host name for > https://mirrors.fedoraproject.org/metalink?repo=fedora-38=x86_64 > [Could not resolve host: mirrors.fedoraproject.org] > Error: Failed to download metadata for repo 'fedora': Cannot prepare > internal mirrorlist: Curl error (6): Couldn't resolve host name for > https://mirrors.fedoraproject.org/metalink?repo=fedora-38=x86_64 > [Could not resolve host: mirrors.fedoraproject.org] > > Any suggestions? > Maybe a DNS issue? Does web browsing work fine? Could try using google instead of your internet provider, forcing DNS to 8.8.8.8. Thanks, Richard ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-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/users@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: SPDX Statistics - ZX Spectrum edition
On Sun, Apr 23, 2023 at 4:09 AM Miroslav Suchý wrote: > New version of fedora-license-data and license-validate has been released. > > NEW: the package fedora-license-data now contains BNF grammar which you > can use. It is available in `/usr/share/fedora-license-data/grammar.lark` > You'll have to explain to me the significance of this. Thanks, Richard ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-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@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: It’s time to transform the Fedora devel list into something new
On Fri, Apr 21, 2023 at 3:39 PM Ben Cotton wrote: > On Fri, Apr 21, 2023 at 4:05 PM Maxwell G wrote: > > > > What evidence shows that the group is ever shrinking? I often see Self > > Introduction posts and new people interacting with project. I suppose > > that whether they continue interacting afterwards is another question. > > I'm glad you asked. Earlier this week I decided to avoid doing other > work by putting together some quick charts of devel list > participation. Here's the number of unique participants per month from > 2004–2022: > https://bcotton.fedorapeople.org/images/devel-participation-monthly.png > > And for a less-noisy version, the median of the monthly numbers per year: > https://bcotton.fedorapeople.org/images/devel-participation-mean.png And on discourse you could have pasted these pictures directly in without having to upload them somewhere... ;) > There are a lot of questions left unanswered by this quick analysis, > but there's a clear trend in fewer participants over time. In fact, > last month had the second smallest participant count (tied with > October 2022). Of course, these charts don't show _why_, but they do > support the assertion that folks are dropping out of the conversation > faster than others are joining. > I think this is especially concerning because Fedora seems to be more popular than ever. If we had a way to measure that and include it in the graph (devel participants as a % of users?) I have a feeling the slope would be much more negative. Not that it proves Discourse would change that, but still... Thanks, Richard ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-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@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: It’s time to transform the Fedora devel list into something new
Not quoting anything in particular, just my opinion and a +1. Being a solid Gen X'er I'm comfortable in both worlds. I will say that I've found the large volume of emails between Fedora and MythTV (though it's slowed in the last few years) occasionally overwhelming. The first thing I do almost every morning (still in my PJs with a cup of coffee) is to go through all the threads, archive what I'm not interested in, but keep just in case, and read the others. In my work world I frequently find myself in Discourse (or similar) forums, and I find it easy enough to find what I'm looking for, or if there's new threads or replies to threads I've posted to (usually at the top). A few months ago I spent a few hours cleaning up old emails in gmail because google (the search engine) lies. I perfected a query to only return list emails older than 1 year but even though I checked "include all emails" it would only delete about 500 at a time. Took a while to work through my 10+ year history as a packager 500 emails at a time! The reality is the future potential contributors are used to tools like Discourse. That's fine. I'll adapt. Thanks, Richard ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-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@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: SPDX: Consistency of tools
On Tue, Apr 4, 2023 at 12:45 AM Miroslav Suchý wrote:
> Dne 04. 04. 23 v 3:20 Richard Shaw napsal(a):
>
> I have updated my licensecount script which summarises the licenses in a
> source and uses licensecheck to output SPDX licenses instead, but they
> output the "short" form as far as I can tell, not the form that we want in
> the SPEC file.
>
> Try:
>
> licensecheck --shortname-scheme=spdx -r .
>
> this gives me *almost* the wanted result:
>
> ./rpmconf.spec: *No copyright* GPL-3
> ./bin/rpmconf: GPL-3.0-or-later
> ./rpmconf/rpmconf.py: GPL-3.0-or-later
>
> Last two lines are correct. The first line still use the short form. I
> consider it a isolated bug of licensecheck - feel free to report issue
> there.
>
Weird, that's the option I added but my output is different. I recently
updated... Is there some kind of supplementary package I need to install?
$ cat /usr/local/bin/licensecount
#!/bin/bash
if [ $# -eq 0 ]
then dir=$pwd
else
dir=$1
fi
licensecheck --shortname-scheme=spdx -rm $dir | awk '{FS="\t"; print $2;}'
| sort | uniq -c | sort -gr
> Additionally, spectool does not complain that the short format for the
> license is used.
>
> I think that spectool does not complain about anything. Unless it is fatal
> parsing error. We have rpmlint and rpminspect for that. AFAIK both tool has
> been already migrated and will complain when you use short format.
>
Yeah...I should have gone to bed by then. I meant to use rpmlint. But it
still doesn't complain. For abi-compliance-checker:
$ grep License: *.spec
License:LGPL-2.1+
$ rpmlint *.spec
rpmlint session starts
===
rpmlint: 2.4.0
configuration:
/usr/lib/python3.11/site-packages/rpmlint/configdefaults.toml
/etc/xdg/rpmlint/fedora-legacy-licenses.toml
/etc/xdg/rpmlint/fedora-spdx-licenses.toml
/etc/xdg/rpmlint/fedora.toml
/etc/xdg/rpmlint/scoring.toml
/etc/xdg/rpmlint/users-groups.toml
/etc/xdg/rpmlint/warn-on-functions.toml
checks: 31, packages: 1
If I can at least get these to problems fixed I don't mind resuming my
efforts.
Thanks,
Richard
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-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@lists.fedoraproject.org
Do not reply to spam, report it:
https://pagure.io/fedora-infrastructure/new_issue
SPDX: Consistency of tools
WARNING: This is a small rant... I have tried to keep up with the emails on the devel list around this but I admit that I haven't been able to devote the time to GROK them all. I decided to look up my packages on src.fedoraproject.org (I'm still not sure if it's showing me all packages I'm admin of, or just main admin) and start working through them one by one. I have updated my licensecount script which summarises the licenses in a source and uses licensecheck to output SPDX licenses instead, but they output the "short" form as far as I can tell, not the form that we want in the SPEC file. For example in abi-dumper after executing `fedpkg prep` and cd'ing into the source directory I get: $ licensecount . 5 UNKNOWN 1 LGPL-2.1+ 1 LGPL-2.1 1 GPL But my current understanding is that the correct application (after inspecting what sources actually go into the resultant package) would be "LGPL-2.1-or-later". Additionally, spectool does not complain that the short format for the license is used. While no matter what we do, there are maintainers that are not going to proactively update their packages, until we unify the tools and documentation to "do the right thing", we're pissing in the wind. Googling only found: https://docs.fedoraproject.org/en-US/legal/update-existing-packages/#_process_used When we have consistent tools and documentation I will resume my efforts to update my package. On a side note, I keep seeing the statistics around what packages can be "trivially" converted to SPDX format, but I really think this is an opportunity to re-evaluate the licences on all packages to make sure they're correct. Thanks, Richard ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-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@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
[fedora-arm] Re: Le Potato?
I didn't want to post the link since it's US centric but if it helps: https://www.amazon.com/gp/product/B074P6BNGZ Thanks, Richard ___ arm mailing list -- arm@lists.fedoraproject.org To unsubscribe send an email to arm-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/arm@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
[fedora-arm] Le Potato?
Google has failed me. Can I run Fedora on a Le Potato? If so, what target do I use? Anything I need to do before writing the image? I plan to use eMMC if I can get it cheap enough due to the failure rate of SD cards. Thanks, Richard ___ arm mailing list -- arm@lists.fedoraproject.org To unsubscribe send an email to arm-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/arm@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: memtest86+ seems to do nothing.
On Wed, Mar 15, 2023 at 10:58 AM home user wrote: > Good morning, > > When booting up, I select the grub menu entry > "Fedora Memtest memtest86+-5.31". > The screen blanks, the cursor goes to the upper left corner of the > display, and blinks. > That's it. > I waited about 10 minutes. Cursor still blinking in the same place. > Nothing else ever showed up. > I rebooted. > > How do I get memtest86+ working properly? > Does your computer use UEFI to boot? If so, is the image you're using for memtest86+ correct? Thanks, Richard ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-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/users@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: What is needed to mock build for rhel+epel on Fedora?
On Mon, Mar 13, 2023 at 12:00 PM Barry Scott wrote: > What do I need to setup to allow mock to build for rhel+epel on Fedora? > > I'm getting this error: > > $ mock -r rhel+epel-8-x86_64 --print-root > ERROR: /etc/pki/entitlement is not a directory is subscription-manager > installed? > Does it have to be RHEL? I've used Alma and Rocky with success. Thanks, Richard ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-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/users@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: Manage Red Haat subscription using Cokpit (it was Docker containers and Cockpit)
On Sun, Mar 12, 2023 at 8:38 PM Sergio Belkin wrote: > Thanks Richard, > > I have a "Red Hat Developer Subscription for Individuals" I winder if I > can manage my subscription from Cockpit the only I find is for > registering the system, but I get: > > Traceback (most recent call last): File > "/usr/lib64/python3.11/site-packages/dbus/service.py", line 756, in > _message_cb _method_reply_return(connection, message, method_name, > signature, *retval) File > "/usr/lib64/python3.11/site-packages/dbus/service.py", line 257, in > _method_reply_return reply.append(signature=signature, *retval) TypeError: > Expected a string or unicode object > Not sure about that one, I would make sure your system is fully updated and if it persists, open a ticket. Thanks, Richard ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-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/users@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: Docker containers and Cockpit
On Sat, Mar 11, 2023 at 4:51 PM Sergio Belkin wrote: > Hi, > I'm wondering if Cockpit can handle Docker containers in Fedora 37. Can > anyone confirm if this is possible or not, and if so, give me some tips on > how to do it? I see a section for podman containers but not for docker ones. > Thanks in advance! > Good timing! I've recently run across this at work, but on a RHEL 8.6 system, but that probably doesn't matter. I would just use podman, the commands are mostly the same as docker, and it doesn't rely on a service running. If you start up a docker container with podman it will show up in cockpit. The only thing you need to be careful of, is if you start it as a normal user, it will be killed by systemd when you logout. To prevent this you can run `loginctl enable-linger` to prevent this behavior. https://www.freedesktop.org/software/systemd/man/loginctl.html Thanks, Richard ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-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/users@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: [chirp_users] installing CHIRP-next problems
On Thu, Mar 9, 2023 at 4:31 PM Dan Smith via chirp_users < chirp_users@intrepid.danplanet.com> wrote: > > It would be nice if detailed instructions for Fedora and rpm based > distros were included since the site only shows how to do an install on > Ubuntu. Package names are not the same and several necessary dependencies > are not listed. > > It would be nice if users of other distros would contribute instructions > relevant to them for the good of the community. Please message me your > username (privately) and I'll give you wiki edit access. > I have very little time these days but if chirp-next is ready for packaging I can try to take a look in the near future. Thanks, Richard KF5OIM ___ chirp_users mailing list chirp_users@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users This message was sent to arch...@mail-archive.com at arch...@mail-archive.com To unsubscribe, send an email to chirp_users-unsubscr...@intrepid.danplanet.com To report this email as off-topic, please email chirp_users-ow...@intrepid.danplanet.com Searchable archive: https://www.mail-archive.com/chirp_users@intrepid.danplanet.com
Re: MongoDB for fedora37?
On Thu, Mar 9, 2023 at 9:37 AM Alex wrote: > Hi, > I don't see mongodb in the default fedora37 repo. Anyone know where I > might find a maintained package? I've been using the one from centos7, I > believe, but it's dated and would like to find a more current version. > MongoDB changed their license such that it's no longer considered free. If you have to have it, then your only real option is to use their RPMS https://www.mongodb.com/docs/manual/tutorial/install-mongodb-on-red-hat/#install-mongodb-community-edition They only build for EL but you can try installing on Fedora, as long as the deps are met, it should work. Thanks, Richard ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-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/users@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: software or hardware raid?
On Thu, Mar 2, 2023 at 2:25 PM Ranjan Maitra wrote: > Thanks to everybody. I recall discussion from several years ago on the > benefits of software over hardware RAID. I had completely forgotten about > UPS for this new machine. Btw, what happens if power goes out (and I do not > have UPS)? > If you don't have a UPS, I would recommend BTRFS mostly because it's a Copy-On-Write (COW) filesystem. EXT4 journaling only protects the filesystem, not the files themselves. BRTFS does a checksum of the files as well, and because it writes out a new file, if that's interrupted, you still at least have the previous version of the file. Depending on the type of files, you may also want to take advantage of transparent compression. I know BTRFS took a long time to stabilize but it works pretty well for stand alone and RAID 1. I'm not sure if I would trust it for RAID 5 just yet. Thanks, Richard ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-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/users@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: software or hardware raid?
On Wed, Mar 1, 2023 at 2:45 PM John Mellor wrote: > > On 2023-03-01 3:01 p.m., Ranjan Maitra wrote: > > I would like to RAID two of my disks, and I was wondering if the > recommendation is to do software or hardware RAID? > Don't even consider hardware RAID solutions that became out-of-favour 25 > years ago. You can easily do it with LVM/MDR combinations, but its more > complicated and slower than the BTRFS solution, especially when > rebuilding onto a new drive. Instead, because the normal Fedora > installer is a bit brain-dead, unplug one of the drives and use the > Fedora-default BTRFS setup. Then plug in the second drive back again, > reboot and set up a RAID-1 configuration. See > http://www.beginninglinux.com/btrfs for a quick tutorial. There is also > a good reference guide on kernel.org, at > https://btrfs.wiki.kernel.org/index.php/Using_Btrfs_with_Multiple_Devices > to see what can be done. BTRFS is massively faster and safer than all > other implementations other than perhaps ZFS, is at least partially > error compensating, does not demand identical drives, and can be easily > converted into other RAID classes dynamically as desired. > I was going to recommend BTRFS but there's still a lot of people weary about it because of the long time to stabilization. I have 4 4TB drives in a BTRFS RAID 1 array for all my media. I know RAID 5 is a bit touchy so I have put that off until I start to run out of space. The cool thing is I can convert on the fly! I have installed btrfsmaintenancetools or whatever the package name is and am running scrubs and balances regularly. Thanks, Richard ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-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/users@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
