Re: F42 Change Proposal: Protobuf 5.x/6.x (system-wide)

On 12/24/24 01:59 PM, Neal Gompa wrote: On Tue, Dec 24, 2024 at 10:13 AM Steven A. Falco wrote: This proposal mentions major versions 3, 5, and 6, but I don't see any mention of major version 4. I don't pretend to understand this in detail, but I am maintaining a project that

Re: F42 Change Proposal: Protobuf 5.x/6.x (system-wide)

This proposal mentions major versions 3, 5, and 6, but I don't see any mention of major version 4. I don't pretend to understand this in detail, but I am maintaining a project that currently calls for "protoc 25.3" or older, which I think comes from major version 4. Fedora currently has 3.19.

Rawhide, koji: cannot build because of conflicting requests

I'm trying to build the KiCad package on rawhide via koji. I'm getting the following errors: DEBUG util.py:459: Repositories loaded. DEBUG util.py:459: Failed to resolve the transaction: DEBUG util.py:459: Problem: package vtk-devel-9.2.6-21.fc42.x86_64 from build requires libvtkCommonCore.

Re: Updating xorg-x11-server

On 9/5/24 10:54 AM, Simone Caronni wrote: Hi everyone, I've noticed that we're really behind on xorg-x11-server releases (almost 3 years!) and that by rebasing we would drop tons of patches that have already been upstreamed during this time. No one that is listed in the maintainer list of tha

Re: Donate 1 minute of your time to test upgrades from F40 to F41

On 9/5/24 06:57 AM, Miroslav Suchý wrote: dnf --releasever=41 --enablerepo=updates-testing --assumeno distro-sync Most of my issues are due to gimp: gutenprint-plugin, gimp-resynthesizer, gimp-lqr-plugin. Problem #2 relates to kicad-nightly which comes from Copr, so that may not be a fair te

Re: Fedora Elections - Voting is now open!

On 5/21/24 10:39 AM, Sandro wrote: On 21-05-2024 16:32, Ben Cotton wrote: On Tue, May 21, 2024 at 10:28 AM Sandro wrote: However, now the link is in the open, we might have to change it again and invalidate the link you posted. It's not meant to be out in the open. It's probably fine. If so

Re: Fedora Elections - Voting is now open!

On 5/21/24 10:17 AM, Sandro wrote: On 21-05-2024 15:47, Vít Ondruch wrote: Dne 21. 05. 24 v 15:45 Vít Ondruch napsal(a): Dne 21. 05. 24 v 15:31 Steven A. Falco napsal(a): I'm getting the "410 Gone" message, too. Tried multiple times since yesterday with no luck. Yes, this

Re: Fedora Elections - Voting is now open!

I'm getting the "410 Gone" message, too. Tried multiple times since yesterday with no luck. Steve On 5/21/24 05:21 AM, Aoife Moloney wrote: I've seen someone in the Red Hat Waterford office be able to claim it no problem so the issue may be individually based as the link is definitel

Re: Fedora 40 apache now giving errors

On 4/24/24 06:50 AM, Tom Hughes wrote: On 24/04/2024 02:28, Xose Vazquez Perez wrote: # mkdir /etc/systemd/system/httpd.service.d/ # vi /etc/systemd/system/httpd.service.d/override.conf [Service] ProtectHome=false Better than just opening up whole trees again would be to use ReadWritePaths=

Fedora 40 apache now giving errors

I upgraded to F40, and suddenly an apache cgi script that was working perfectly in F39 (and earlier) is giving me a "Read-only file system" error when trying to write data into a file. The directory where the cgi is trying to write is owned by apache:apache, and it is mode 777. The file the c

spice-vdagent

I noticed that the load average on a rawhide vm was higher than expected, and according to 'top' I had two copies of /usr/bin/spice-vdagent running, with one of them taking up a whole cpu core. I removed /etc/xdg/autostart/spice-vdagent.desktop and rebooted. Now there is only one copy of spic

Re: F42 Change Proposal: Fedora Plasma Workstation (System-Wide)

On 4/2/24 03:50 PM, Steve Cossette wrote: Well, we did submit this yesterday around 2:30-3:00PM EST, guessing it was a bit too late. But the proposal is 1000% serious. I'm glad to hear you say that, as I switched to KDE around the time of Gnome3 and never looked back. Steve -- _

Re: GCC perhaps not honoring -std?

On 2/21/24 11:46 AM, Jakub Jelinek wrote: On Wed, Feb 21, 2024 at 11:34:37AM -0500, Steven A. Falco wrote: I am getting an error "template-id not allowed for constructor in C++20" but according to the Copr log [0], the compiler is being given -std=c++17: It is a warning, but you&#x

GCC perhaps not honoring -std?

I am getting an error "template-id not allowed for constructor in C++20" but according to the Copr log [0], the compiler is being given -std=c++17: Building CXX object thirdparty/clipper2/CMakeFiles/clipper2.dir/Clipper2Lib/src/clipper.engine.cpp.o cd /builddir/build/BUILD/kicad-7.0.11/redhat-l

Re: just to let you know FESCo agreed to a preliminary injunction while we consider this issue

On 2/8/24 05:44 AM, Neal Gompa wrote: The Wayland protocol in question is this one: https://gitlab.freedesktop.org/wayland/wayland-protocols/-/merge_requests/18 That said, even X11's version isn't widely supported. Typically, support for this is plumbed through linking libSM, and GTK notably doe

Re: just to let you know FESCo agreed to a preliminary injunction while we consider this issue

On 2/3/24 01:12 AM, Kevin Kofler via devel wrote: Any interested people can already request comaintainership now (e.g., by replying to this mail), and I will almost certainly grant it (though I will have reservations about some specific types of requests, such as blanket admin permissions for the

Re: just to let you know FESCo agreed to a preliminary injunction while we consider this issue

On 2/1/24 11:46 AM, Neal Gompa wrote: I'd like to think that the gaps will be fixed, but it seems to me that because of policy, some gaps (like apps controlling their own window placement) will never be fixed. That is not necessarily true. For your example about window placement, there is th

Re: just to let you know FESCo agreed to a preliminary injunction while we consider this issue

On 2/1/24 11:28 AM, Neal Gompa wrote: On Thu, Feb 1, 2024 at 4:21 PM Roberto Ragusa wrote: On 2/1/24 14:29, Steve Cossette wrote: And yes, that /is/ the whole point: We want to foster the use of Wayland, to increase it's adoption, to force people using it to hit snags along the road and fi

Re: just to let you know FESCo agreed to a preliminary injunction while we consider this issue

On 1/30/24 08:55 AM, Richard W.M. Jones wrote: On Tue, Jan 30, 2024 at 08:38:51AM -0500, Stephen Gallagher wrote: 3) Fedora has a long-standing and well-communicated stance that we are a Wayland distribution first and foremost and that X11 support is intended as a migration-support tool rather t

Re: F40 Change Proposal: Wifi MAC Randomization (System Wide)

On 12/21/23 08:53 AM, Neal Gompa wrote: On Thu, Dec 21, 2023 at 8:52 AM Leigh Scott wrote: I'm -1 for this change, it shouldn't be enabled by default as it will cause issues for users using router mac filtering. What this seems to state is that the MAC address would be unique for each SSID,

Re: F40 Change Proposal: KDE Plasma 6 (System Wide)

On 9/18/23 11:33 AM, Neal Gompa wrote: On Mon, Sep 18, 2023 at 11:12 AM Steven A. Falco wrote: On 9/17/23 05:48 PM, Kevin Kofler via devel wrote: Ian Laurie wrote: I didn't think the greeter used Wayland? So there may be something else going on. I cannot swear to it, but I don&#x

Re: F40 Change Proposal: KDE Plasma 6 (System Wide)

On 9/17/23 05:48 PM, Kevin Kofler via devel wrote: Ian Laurie wrote: I didn't think the greeter used Wayland? So there may be something else going on. I cannot swear to it, but I don't think I've noticed problems in the greeter before. As Adam posted, the offset problem already has a bug fo

Re: F40 Change Proposal: KDE Plasma 6 (System Wide)

On 9/14/23 04:20 PM, Steven A. Falco wrote: I've written a bug [1] stating that window placement appears to be ignored.  Specifically the following command ignores the requested placement under Plasma(Wayland) but the placement is honored under Plasma(X11).  That is a big problem in a

Re: F40 Change Proposal: KDE Plasma 6 (System Wide)

On 9/14/23 06:36 AM, Ian McInerney wrote: On Thu, 14 Sep 2023, 00:17 Neal Gompa, mailto:ngomp...@gmail.com>> wrote: On Wed, Sep 13, 2023 at 7:02 PM Steven A. Falco mailto:stevenfa...@gmail.com>> wrote: > > On 9/13/23 05:23 PM, Neal Gompa wrote: > &

Re: F40 Change Proposal: KDE Plasma 6 (System Wide)

On 9/13/23 07:16 PM, Neal Gompa wrote: On Wed, Sep 13, 2023 at 7:02 PM Steven A. Falco wrote: On 9/13/23 05:23 PM, Neal Gompa wrote: Right. And I want to stress we are not dropping support for X11 applications. Anything running as an X client in a desktop should work as it has before. I&#

Re: F40 Change Proposal: KDE Plasma 6 (System Wide)

On 9/13/23 05:23 PM, Neal Gompa wrote: Right. And I want to stress we are not dropping support for X11 applications. Anything running as an X client in a desktop should work as it has before. I'm not convinced KiCad will work in that scenario, so please let me summarize what I've read here, an

Re: F40 Change Proposal: KDE Plasma 6 (System Wide)

On 9/13/23 12:10 PM, Steven A. Falco wrote: On 9/13/23 11:53 AM, Aoife Moloney wrote: Wiki  https://fedoraproject.org/wiki/Changes/KDE_Plasma_6 == Summary == KDE Plasma 6 is successor to KDE Plasma 5 created by the KDE Community. It is based on Qt 6 and KDE Frameworks 6 and brings many

Re: F40 Change Proposal: KDE Plasma 6 (System Wide)

On 9/13/23 11:53 AM, Aoife Moloney wrote: Wiki https://fedoraproject.org/wiki/Changes/KDE_Plasma_6 == Summary == KDE Plasma 6 is successor to KDE Plasma 5 created by the KDE Community. It is based on Qt 6 and KDE Frameworks 6 and brings many changes and improvements over previous versions. Fo

Re: Donate 1 minute of your time to test upgrades from F38 to F39

On 8/23/23 04:12 PM, Richard Shaw wrote: On Wed, Aug 23, 2023 at 1:41 PM Steven A. Falco mailto:stevenfa...@gmail.com>> wrote: On 8/23/23 02:22 PM, Miroslav Suchý wrote: > dnf --releasever=39 --setopt=module_platform_id=platform:f39 \ > --enablerepo=updates-testing \

Re: Donate 1 minute of your time to test upgrades from F38 to F39

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 fre

Re: Rawhide build failures

Looks like it is a mirror issue. Adding --enablerepo=local corrects it. Please disregard my previous email. Steve On 8/21/23 02:41 PM, Steven A. Falco wrote: Not sure if this is a known problem, but I'm getting build failures from mock on rawhide.  F37, F38, and F39 a

Rawhide build failures

Not sure if this is a known problem, but I'm getting build failures from mock on rawhide. F37, F38, and F39 are ok. Steve Error: Problem: package wxGTK-devel-3.2.2.1-5.fc39.x86_64 from fedora requires libwx_gtk3u_webview-3.2.so.0()(64bit), but none of the providers can be installed

Re: [HEADS UP] Python 3.12 side tag merging today (and what to do)

On 7/4/23 10:51 AM, Tomáš Hrnčiar wrote: ## How to run things locally? You can use mock. Make sure to:     1. Clear all caches first: $ mock -r fedora-rawhide-x86_64--scrub=all     2. Use the Koji repo: $ mock -r fedora-rawhide-x86_64 --enablerepo=local ... That doesn't appear correct. At

Re: ppc64le builds taking ages

I ran a KiCad build yesterday on Copr [1] (so not the same as Koji), but while it all completed, curiously the rawhide PPC build took 6 hours while the f37 and f38 PPC builds only took 2 hours. The corresponding Koji build [2] took close to 4 hours, so it is in the ball-park. KiCad is a bit u

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

I've gotten a similar result. Without --allowerasing: Error: Problem 1: conflicting requests - problem with installed package gimp-heif-plugin-1.1.0-12.fc37.x86_64 - gimp-heif-plugin-1.1.0-12.fc37.x86_64 does not belong to a distupgrade repository Problem 2: problem with installed package

Re: redhat-lsb-core

On 4/4/23 09:56 AM, Neal Gompa wrote: On Tue, Apr 4, 2023 at 9:49 AM Steven A. Falco wrote: On 4/4/23 05:58 AM, ser...@serjux.com wrote: On 2023-04-03 21:13, Steven A. Falco wrote: I'm confused by the Requires for redhat-lsb-core. According to "dnf repoquery --requires redha

Re: redhat-lsb-core

On 4/4/23 05:58 AM, ser...@serjux.com wrote: On 2023-04-03 21:13, Steven A. Falco wrote: I'm confused by the Requires for redhat-lsb-core. According to "dnf repoquery --requires redhat-lsb-core" there is no requirement for esmtp.  But according to "dnf repoquery --whatreq

Re: redhat-lsb-core

On 4/3/23 04:21 PM, Stephen Gallagher wrote: On Mon, Apr 3, 2023 at 4:15 PM Steven A. Falco wrote: I'm confused by the Requires for redhat-lsb-core. According to "dnf repoquery --requires redhat-lsb-core" there is no requirement for esmtp. But according to "dnf repo

redhat-lsb-core

I'm confused by the Requires for redhat-lsb-core. According to "dnf repoquery --requires redhat-lsb-core" there is no requirement for esmtp. But according to "dnf repoquery --whatrequires esmtp", redhat-lsb-core does require esmtp. Perhaps there is some sort of transitive requirement that the

Re: New machine - no virtual terminals

On 3/23/23 06:14 AM, Dominik 'Rathann' Mierzejewski wrote: On Wednesday, 22 March 2023 at 17:12, Steven A. Falco wrote: On 3/22/23 11:23 AM, stan via devel wrote: On Tue, 21 Mar 2023 17:14:44 -0400 "Steven A. Falco" wrote: I think I'm finally getting somewhe

Re: New machine - no virtual terminals

On 3/22/23 11:23 AM, stan via devel wrote: On Tue, 21 Mar 2023 17:14:44 -0400 "Steven A. Falco" wrote: I think I'm finally getting somewhere with this problem. My motherboard has a built-in VGA interface, which shows up as "astdrmfb" on fb0. My AMD video card is &

Re: New machine - no virtual terminals

how to force a framebuffer to be ignored, I'd appreciate it. Steve On 3/21/23 03:26 PM, Steven A. Falco wrote: On 3/21/23 02:26 PM, stan via devel wrote: On Tue, 21 Mar 2023 10:25:36 -0400 "Steven A. Falco" wrote: I recently put a new machine together using an

Re: New machine - no virtual terminals

On 3/21/23 02:26 PM, stan via devel wrote: On Tue, 21 Mar 2023 10:25:36 -0400 "Steven A. Falco" wrote: I recently put a new machine together using an AMD Radeon PRO W6600 Graphics Card. CPU is a threadripper pro. Motherboard is an ASUS Pro WS WRX80E-SAGE SE WIFI II sWRX8 E-ATX. S

New machine - no virtual terminals

I recently put a new machine together using an AMD Radeon PRO W6600 Graphics Card. CPU is a threadripper pro. Motherboard is an ASUS Pro WS WRX80E-SAGE SE WIFI II sWRX8 E-ATX. Software is the KDE spin of Fedora 37. It mostly works perfectly, but if I try to access a virtual terminal with Ct

Re: Status of AVIF support in Fedora

As a workaround until the dust settles, I did a dnf downgrade of libheif and added an exclude in dnf.conf. I'll revert that when the add-ons are published. Steve On 3/20/23 02:39 PM, Kalev Lember wrote: On Mon, Mar 20, 2023 at 7:29 PM Vitaly Zaitsev via devel mailto:devel@lists.fedora

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

On 2/22/23 10:28 AM, Steven A. Falco wrote: I got the following errors: Error:  Problem 1: package opencolorio1-1.1.1-3.fc37.x86_64 requires libyaml-cpp.so.0.6()(64bit), but none of the providers can be installed   - yaml-cpp-0.6.3-7.fc37.x86_64 does not belong to a distupgrade repository

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

I got the following errors: Error: Problem 1: package opencolorio1-1.1.1-3.fc37.x86_64 requires libyaml-cpp.so.0.6()(64bit), but none of the providers can be installed - yaml-cpp-0.6.3-7.fc37.x86_64 does not belong to a distupgrade repository - problem with installed package opencolorio1-1.

libhackrf soname bump

libhackrf has updated from 0.7.0 to 0.8.0 in rawhide. No dependent packages depend on the exact version, so nothing else should need rebuilding. Tested with CubicSDR and gnuRadio. Steve ___ devel mailing list -- devel@lists.fedoraproject.org

Heads up for KiCad in Rawhide

KiCad will shortly be upgraded from 6.0.11 to 7.0.0-rc2 in Rawhide. Designs created with KiCad 6 and earlier are readable / editable by KiCad 7. However, once a design is saved with KiCad 7, it will no longer be readable by KiCad 6 or earlier. Steve

Re: Fedora 35 End Of Life in one week

On 12/7/22 09:14 AM, Tomas Hrcka wrote: Fedora 36 will continue to receive updates until approximately one month after the release of Fedora 37. Shouldn't that be "until approximately one month after the release of Fedora _38_"? Steve ___ de

Re: [HEADS UP] Rebuild of wxGTK wxGLCanvas-using packages

On 11/24/22 08:45 AM, Kalev Lember wrote: Hi Scott, On Wed, Nov 23, 2022 at 6:23 PM Scott Talbert mailto:s...@techie.net>> wrote: Hi all, In order to fix some incompatibilities with wxWidgets wxGLCanvas (which is currently built with OpenGL EGL support) and several package users wh

Re: [HEADS UP] Rebuild of wxGTK wxGLCanvas-using packages

On 11/23/22 12:58 PM, Steven A. Falco wrote: On 11/23/22 12:23 PM, Scott Talbert wrote: Hi all, In order to fix some incompatibilities with wxWidgets wxGLCanvas (which is currently built with OpenGL EGL support) and several package users which are expecting OpenGL GLX support, I need to

Re: [HEADS UP] Rebuild of wxGTK wxGLCanvas-using packages

On 11/23/22 12:23 PM, Scott Talbert wrote: Hi all, In order to fix some incompatibilities with wxWidgets wxGLCanvas (which is currently built with OpenGL EGL support) and several package users which are expecting OpenGL GLX support, I need to rebuild wxWidgets with a different configuration o

Non-responsive maintainer check for cottsay

The package hackrf has several open bugs [1], [2]. I've started the non-responsive maintainer process by filing [3]. I've CC'd the maintainer on this email, but if anyone knows how else to contact them, please let me know. Thanks, Steve [1] https://bugzilla.redhat.com/show_bug

Re: hackrf package

On 11/16/22 06:25 PM, Scott Talbert wrote: I just upgraded my system to Fedora 37 and noticed that the package "hackrf" was still from Fedora 36. I found a failed build from the f37-rebuild, dated 2022-07-21 [1]. It apparently failed on aarch64, but the logs are long gone - at least I don't se

hackrf package

I just upgraded my system to Fedora 37 and noticed that the package "hackrf" was still from Fedora 36. I found a failed build from the f37-rebuild, dated 2022-07-21 [1]. It apparently failed on aarch64, but the logs are long gone - at least I don't see them on koji. I tried a scratch build,

Re: SPDX Change update

On 11/10/22 09:47 AM, Eike Rathke wrote: Hi Miroslav, On Monday, 2022-11-07 18:46:26 +0100, Miroslav Suchý wrote: Tl;dr Please start migrating your license tag to SPDX now. Is it ok to have SPDX tags on all currently supported release branches, i.e. f37, f36, f35? Yes. Steve

Re: How do I "unstick" koji?

On 9/28/22 09:59 AM, Stephen Smoogen wrote: On Wed, 28 Sept 2022 at 09:53, Steven A. Falco mailto:stevenfa...@gmail.com>> wrote: Yesterday, I had a build that failed.  The task ID is 92381483. I tried rebuilding it today in task 92397327 but I get the error m

How do I "unstick" koji?

Yesterday, I had a build that failed. The task ID is 92381483. I tried rebuilding it today in task 92397327 but I get the error message: "GenericError: Build already in progress (task 92381483)" I tried doing "koji cancel 92381483" but that doesn't help. Another attempt (task 92398262) faile

Re: Donate 1 minute of your time to test upgrades from F36 to F37

On 9/12/22 08:59 AM, Miroslav Suchý wrote: dnf --releasever=37 --setopt=module_platform_id=platform:f37 \ --enablerepo=updates-testing \ $(rpm -q fedora-repos-modular >/dev/null && echo --enablerepo=updates-testing-modular) \ --assumeno distro-sync Error: Problem: package nautilus-dropbox-1:2

License change for bvi

License changed from GPLv3 to GPL-3.0-or-later (In the past it should have been GPLv3+ rather than GPLv3, so I fixed that in the process of converting to SPDX, in case anyone was wondering...) Steve ___ devel mailing list -- devel@lists.fedora

Re: F38 Proposal: SPDX License Phase 1 (Self-Contained Change proposal)

On 9/8/22 06:44 AM, Miroslav Suchý wrote: Quick heads up where we are: I had been following this discussion, and I vaguely remember that there was talk of it having to be conditional, perhaps with a macro. Has all that now been resolved? Can one simply convert to the new SPDX license identi

Re: [HEADS UP] wxPython 4.2.0 in Rawhide

On 8/16/22 09:29 AM, Steven A. Falco wrote: On 8/15/22 08:38 PM, Scott Talbert wrote: On Sat, 13 Aug 2022, Steven A. Falco wrote: On 8/12/22 11:35 AM, Steven A. Falco wrote: On 8/12/22 11:00 AM, Scott Talbert wrote: On Fri, 12 Aug 2022, Steven A. Falco wrote: It turns out that there is a

Re: [HEADS UP] wxPython 4.2.0 in Rawhide

On 8/15/22 08:38 PM, Scott Talbert wrote: On Sat, 13 Aug 2022, Steven A. Falco wrote: On 8/12/22 11:35 AM, Steven A. Falco wrote: On 8/12/22 11:00 AM, Scott Talbert wrote: On Fri, 12 Aug 2022, Steven A. Falco wrote: It turns out that there is a bug in wxPython whereby it installs an error

Re: rawhide: GPG check FAILED

On 8/14/22 04:42 PM, Christian Kujau wrote: Rawhide n00b here, but struggling with: --- $ dnf upgrade --assumeyes --releasever=rawhide zip Since Fedora 37 has been branched, you need to grab the new Rawhide packages. Rawhide is now the future F38. This should work: dnf

Re: [HEADS UP] wxPython 4.2.0 in Rawhide

On 8/12/22 11:35 AM, Steven A. Falco wrote: On 8/12/22 11:00 AM, Scott Talbert wrote: On Fri, 12 Aug 2022, Steven A. Falco wrote: It turns out that there is a bug in wxPython whereby it installs an error handler that should not be installed by a library [1].  KiCad can work around that by

Re: [HEADS UP] wxPython 4.2.0 in Rawhide

On 8/12/22 11:00 AM, Scott Talbert wrote: On Fri, 12 Aug 2022, Steven A. Falco wrote: It turns out that there is a bug in wxPython whereby it installs an error handler that should not be installed by a library [1].  KiCad can work around that by adding a compile flag to disable its own error

Re: [HEADS UP] wxPython 4.2.0 in Rawhide

On 8/11/22 03:43 PM, Steven A. Falco wrote: It turns out that there is a bug in wxPython whereby it installs an error handler that should not be installed by a library [1].  KiCad can work around that by adding a compile flag to disable its own error handler [2].  Credit to Ian for

Re: [HEADS UP] wxPython 4.2.0 in Rawhide

On 8/11/22 12:26 PM, Steven A. Falco wrote: On 8/11/22 09:56 AM, Steven A. Falco wrote: On 8/10/22 07:41 PM, Scott Talbert wrote: On Tue, 9 Aug 2022, Steven A. Falco wrote: On 8/9/22 06:00 PM, Scott Talbert wrote: On Tue, 9 Aug 2022, Steven A. Falco wrote: On 8/9/22 05:06 PM, Scott

Re: [HEADS UP] wxPython 4.2.0 in Rawhide

On 8/11/22 09:56 AM, Steven A. Falco wrote: On 8/10/22 07:41 PM, Scott Talbert wrote: On Tue, 9 Aug 2022, Steven A. Falco wrote: On 8/9/22 06:00 PM, Scott Talbert wrote: On Tue, 9 Aug 2022, Steven A. Falco wrote: On 8/9/22 05:06 PM, Scott Talbert wrote: On Tue, 9 Aug 2022, Steven A. Falco

Re: [HEADS UP] wxPython 4.2.0 in Rawhide

On 8/10/22 07:41 PM, Scott Talbert wrote: On Tue, 9 Aug 2022, Steven A. Falco wrote: On 8/9/22 06:00 PM, Scott Talbert wrote: On Tue, 9 Aug 2022, Steven A. Falco wrote: On 8/9/22 05:06 PM, Scott Talbert wrote: On Tue, 9 Aug 2022, Steven A. Falco wrote: On 8/9/22 02:25 PM, Steven A. Falco

Re: [HEADS UP] wxPython 4.2.0 in Rawhide

On 8/9/22 06:00 PM, Scott Talbert wrote: On Tue, 9 Aug 2022, Steven A. Falco wrote: On 8/9/22 05:06 PM, Scott Talbert wrote: On Tue, 9 Aug 2022, Steven A. Falco wrote: On 8/9/22 02:25 PM, Steven A. Falco wrote: On 8/9/22 01:09 PM, Scott Talbert wrote: Hi, Upstream wxPython has finally

Re: [HEADS UP] wxPython 4.2.0 in Rawhide

On 8/9/22 05:06 PM, Scott Talbert wrote: On Tue, 9 Aug 2022, Steven A. Falco wrote: On 8/9/22 02:25 PM, Steven A. Falco wrote: On 8/9/22 01:09 PM, Scott Talbert wrote: Hi, Upstream wxPython has finally made a new release and this involves migrating to wxWidgets 3.2.0 at the same time.  I&#

Re: [HEADS UP] wxPython 4.2.0 in Rawhide

On 8/9/22 02:25 PM, Steven A. Falco wrote: On 8/9/22 01:09 PM, Scott Talbert wrote: Hi, Upstream wxPython has finally made a new release and this involves migrating to wxWidgets 3.2.0 at the same time.  I'm planning to build the new wxPython in Rawhide after F37 branch (although could p

Re: [HEADS UP] wxPython 4.2.0 in Rawhide

On 8/9/22 01:09 PM, Scott Talbert wrote: Hi, Upstream wxPython has finally made a new release and this involves migrating to wxWidgets 3.2.0 at the same time.  I'm planning to build the new wxPython in Rawhide after F37 branch (although could put it in F37 later). For those packages that use

Re: [HEADS UP] wxGTK 3.2.0 in Rawhide

On 7/26/22 10:07 AM, Scott Talbert wrote: On Tue, 26 Jul 2022, Steven A. Falco wrote: At long last wxWidgets 3.2.0 has been released and I'm getting it into Rawhide.  This comes with an soname bump (but this should be the last one as 3.2.x should now be ABI stable). NOTE: users of wxWi

Re: [HEADS UP] wxGTK 3.2.0 in Rawhide

On 7/25/22 10:18 PM, Scott Talbert wrote: At long last wxWidgets 3.2.0 has been released and I'm getting it into Rawhide.  This comes with an soname bump (but this should be the last one as 3.2.x should now be ABI stable). NOTE: users of wxWidgets 3.0 (wxGTK3 package) are now strongly encourag

Re: F37 proposal: Officially Support Raspberry Pi 4 (Self-Contained Change proposal)

I like this proposal. Is the intent to use the raw.xz image or the "iso + UEFI" mechanism? Steve ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct

Re: Where does "redhat-linux-build" come from?

On 6/24/22 11:51 AM, Dan Horák wrote: On Fri, 24 Jun 2022 11:36:18 -0400 "Steven A. Falco" wrote: I'm trying to debug a package that uses cmake to build "out of tree". It looks like the build happens in a directory called "redhat-linux-build". Is there

Where does "redhat-linux-build" come from?

I'm trying to debug a package that uses cmake to build "out of tree". It looks like the build happens in a directory called "redhat-linux-build". Is there a macro that contains that string? Steve ___ devel mailing list -- devel@lists.fedorap

Re: Packages that failed to build with Python 3.11 (and what to do)

On 6/21/22 10:34 AM, Miro Hrončok wrote: On 21. 06. 22 16:27, Steven A. Falco wrote: On 6/20/22 07:45 AM, Tomas Hrnciar wrote: Hello. As you might already know, we have recently merged in the Python 3.11side tag to Rawhide, despite several builds not succeeding. We always aim for some

Re: Packages that failed to build with Python 3.11 (and what to do)

On 6/20/22 07:45 AM, Tomas Hrnciar wrote: Hello. As you might already know, we have recently merged in the Python 3.11side tag to Rawhide, despite several builds not succeeding. We always aim for some compromise between having the side tag open for too long and having too many failures. I'm

Re: [HEADS UP] wxGTK update to 3.1.7

On 6/10/22 03:39 PM, Scott Talbert wrote: On Fri, 10 Jun 2022, Steven A. Falco wrote: On 6/10/22 10:43 AM, Scott Talbert wrote: Hi, I'm updating wxGTK to 3.1.7 in Rawhide - this involves an soname bump. I've created side tag f37-build-side-54462 to perform the build with its de

Re: [HEADS UP] wxGTK update to 3.1.7

On 6/10/22 10:43 AM, Scott Talbert wrote: Hi, I'm updating wxGTK to 3.1.7 in Rawhide - this involves an soname bump. I've created side tag f37-build-side-54462 to perform the build with its dependencies. I've built wxGTK, CubicSDR and audacity in the side tag. @rathann, can you please build

Re: F37 proposal: BIOS boot.iso with GRUB2 (System-Wide Change proposal)

+1 My main machine still uses bios boot. Steve On 5/13/22 10:27 AM, Ben Cotton wrote: https://fedoraproject.org/wiki/Changes/BIOSBootISOWithGrub2 This document represents a proposed Change. As part of the Changes process, proposals are publicly announced in order to receive community

Copr PPC builders down?

I have some jobs queued up on copr, and while the x86_64 builders are working fine, the ppc64le builders appear to be down. "State" has remained "pending" for about an hour, so far. Is this a planned outage? Steve ___ devel mailing list -- d

Re: [HEADS UP] Fedora 37 Boost 1.78 rebuilds starting in a side tag

n the F37 mass rebuild. For reference, though, the syntax to build in a side tag is simply:     fedpkg build --target=side-tag-name and these work as well:     fedpkg scratch-build --srpm --target=side-tag-name     koji build --scratch side-tag-name foo.src.rpm On 5/5/22 09:02, Steven A.

Re: [HEADS UP] Fedora 37 Boost 1.78 rebuilds starting in a side tag

On 5/5/22 05:41 AM, Miro Hrončok wrote: On 05. 05. 22 11:39, Caolán McNamara wrote: On Wed, 2022-05-04 at 23:44 +0200, Miro Hrončok wrote: On 04. 05. 22 1:34, Thomas Rodgers wrote: We are starting the rebuilds for https://fedoraproject.org/wiki/Changes/F37Boost178

Re: FESCo wants to know what you use i686 packages for

On 3/20/22 04:38 AM, Zbigniew Jędrzejewski-Szmek wrote: On Fri, Mar 18, 2022 at 12:30:52AM -, Steven Ellis wrote: The issue on our home systems is 3rd party printer drivers. Eg mfc9140cdncupswrapper-1.1.4-0.i386 dcpj4120dwlpr-3.0.1-1.i386 dcpj4120dwcupswrapper-3.0.1-1.i386 mfc9140cdnlpr-1.1

Re: FESCo wants to know what you use i686 packages for

On 3/16/22 09:57 AM, Felix Schwarz wrote: I use wine and lutris (+ 32bit mingw packages). wine is also the big one for me. On my system, roughly 1000 executables (exe and dll) are PE32 (32 bit), and another 1000 executables are PE32+ (64 bit). Steve _

Re: Problem with cmake 3.23.0

On 3/4/22 10:17 AM, Sérgio Basto wrote: On Fri, 2022-03-04 at 16:04 +0100, Michal Schorm wrote: On Fri, Mar 4, 2022 at 3:40 PM Sérgio Basto wrote: The fix is just remove "\  ." (the dot) on %cmake That isn't a fix, that's a workaround for a broken CMake - atleast that I believe, as y

Problem with cmake 3.23.0

There is a new FTBFS for KiCad [1]. I filed an issue with KiCad [2] and got a comment from the project leader: This looks like cmake issue to me. For some reason cmake is creating an incorrect build folder: -- Build files have been written to: /builddir/build/BUILD/kicad-6.0.2 so

Re: copr expired security certificate?

On 3/2/22 04:35 PM, Scott Talbert wrote: On Wed, 2 Mar 2022, Steven A. Falco wrote: I just tried to connect to copr [1] with firefox, and got a "Did Not Connect: Potential Security Issue" error. And apparently copr uses HSTS, so I cannot override it.  Is anyone else having the pr

copr expired security certificate?

I just tried to connect to copr [1] with firefox, and got a "Did Not Connect: Potential Security Issue" error. And apparently copr uses HSTS, so I cannot override it. Is anyone else having the problem? [1] https://copr.fedoraproject.org/coprs/g/kicad/kicad/build/3541862/ Steve __

Re: CVE's and older versions of software

On 2/17/22 09:58 AM, Ben Beasley wrote: This is covered by the Updates Policy[1]. There is quite a bit written there about why an incompatible update might or might not be allowed in a stable release. It also specifically addresses security updates[2], and describes how you can petition FESCo

Re: CVE's and older versions of software

On 2/17/22 06:46 AM, Stephen Snow wrote: On Wed, 2022-02-16 at 22:50 -0500, Demi Marie Obenour wrote: On 2/16/22 18:05, Adam Williamson wrote: On Wed, 2022-02-16 at 14:20 -0500, Steven A. Falco wrote: On 2/16/22 01:58 PM, Dan Horák wrote: On Wed, 16 Feb 2022 13:53:04 -0500 "Steven A.

Re: CVE's and older versions of software

On 2/16/22 01:58 PM, Dan Horák wrote: On Wed, 16 Feb 2022 13:53:04 -0500 "Steven A. Falco" wrote: There are some CVE's against KiCad that have been fixed in the latest version, namely KiCad 6.0.2. I've built that for F36 and Rawhide. I have not released KiCad 6.0.2 i

CVE's and older versions of software

There are some CVE's against KiCad that have been fixed in the latest version, namely KiCad 6.0.2. I've built that for F36 and Rawhide. I have not released KiCad 6.0.2 into Fedora 34 and 35, because my understanding is that by policy, we don't generally allow "major version" updates in stable

Re: Problems building on F36, F37 caused by vtk?

On 2/12/22 11:54 AM, Steven A. Falco wrote: I'm still having problems building - vtk-9.1.0-6.fc36 is present in the x86_64 chroot on copr, but it is not present in the ppc64le chroot as shown in the failure in [0]. Is there any way to tell why the ppc64le chroot hasn't picked up v

Re: Problems building on F36, F37 caused by vtk?

I'm still having problems building - vtk-9.1.0-6.fc36 is present in the x86_64 chroot on copr, but it is not present in the ppc64le chroot as shown in the failure in [0]. Is there any way to tell why the ppc64le chroot hasn't picked up vtk-9.1.0-6.fc36? It looks like the build of vtk succeede

  1   2   >