ispc fails to build with llvm 15

2023-01-06 Thread Luya Tshimbalanga
Hello team, Could someone investigate the failure to build ispc [1] with the recent LLVM[2] ? References: [1] https://src.fedoraproject.org/rpms/ispc [2] https://koji.fedoraproject.org/koji/taskinfo?taskID=95826442 ___ devel mailing list -- devel@list

Re: RISC-V -- are we ready for more, and what do we need to do it?

2023-01-06 Thread David Abdurachmanov
On Sat, Jan 7, 2023 at 2:42 AM Jeff Law wrote: > > > > On 1/6/23 16:19, Jun Aruga (he / him) wrote: > > I posted the same article on Fedora Discussion.[1] However let me > > share it again on the devel@ to tell it to many people. > > > > This is interesting news about RISC-V this week. Perhaps, it

Re: Schedule for Tuesday's FESCo Meeting (2023-01-03)

2023-01-06 Thread Kevin Kofler via devel
Kevin Kofler via devel wrote: > Also, for MSVC, /Oy- is documented to be supported on everything except /Oy actually. /Oy- is the default (= -fno-omit-frame-pointer), /Oy is the equivalent of -fomit-frame-pointer. But both are documented as unsupported only for "x64 compilers". Kevin Ko

Re: Schedule for Tuesday's FESCo Meeting (2023-01-03)

2023-01-06 Thread Neal Gompa
On Sat, Jan 7, 2023 at 1:31 AM Kevin Kofler via devel wrote: > > Neal Gompa wrote: > > GCC is not the official compiler on Windows or macOS. Both platforms > > require frame pointers on all supported architectures with their > > official compilers (MSVC for Windows, Clang for macOS). > > Frame poi

Re: Schedule for Tuesday's FESCo Meeting (2023-01-03)

2023-01-06 Thread Kevin Kofler via devel
Neal Gompa wrote: > GCC is not the official compiler on Windows or macOS. Both platforms > require frame pointers on all supported architectures with their > official compilers (MSVC for Windows, Clang for macOS). Frame pointers are not required by the operating system if you can compile working

Re: Schedule for Tuesday's FESCo Meeting (2023-01-03)

2023-01-06 Thread Kevin Kofler via devel
Richard W.M. Jones wrote: > The problem is you're confusing general gains and gains in > specific scenarios. But the thing is that a gain in some specific scenario is a lot less useful than a general gain. And the latter is usually not had through profiling, but through improvements in toolchain

Re: ImageMagick 7 is landing in Rawhide

2023-01-06 Thread Carl George
Autotrace supports building against GraphicsMagick, so I sent a pull request to switch it to that. https://src.fedoraproject.org/rpms/autotrace/pull-request/3 On Fri, Jan 6, 2023 at 3:45 PM Neal Gompa wrote: > > Hey all, > > The initial rebase of ImageMagick to v7 is landing in Rawhide now: > ht

Re: Schedule for Tuesday's FESCo Meeting (2023-01-03)

2023-01-06 Thread Neal Gompa
On Sat, Jan 7, 2023 at 12:24 AM Kevin Kofler via devel wrote: > > Neal Gompa wrote: > > For what it's worth, frame pointers are required on other operating > > systems for precisely this reason > > What operating systems REQUIRE frame pointers? GCC supports > -fomit-frame-pointer basically everywh

Re: Schedule for Tuesday's FESCo Meeting (2023-01-03)

2023-01-06 Thread Kevin Kofler via devel
Miro Hrončok wrote: > On 04. 01. 23 17:29, Jonathan Wakely wrote: >> On Tue, 3 Jan 2023 at 09:39, Miro Hrončok wrote: >>> >>> = New business = >>> >>> #2923 Re-vote for Change proposal: Add -fno-omit-frame-pointer to >>> #default >>> compilation flags >>> https://pagure.io/fesco/issue/2923 >> >>

Re: Schedule for Tuesday's FESCo Meeting (2023-01-03)

2023-01-06 Thread Kevin Kofler via devel
PS: Kevin Kofler via devel wrote: > The way this was done is so wrong: > * There was a vote. You were not happy with the outcome. > * So you first tried to complain in the original ticket about this. It was > clear that the consensus in that ticket was to not reconsider at this > time. > * So inst

Re: Schedule for Tuesday's FESCo Meeting (2023-01-03)

2023-01-06 Thread Kevin Kofler via devel
Andrii Nakryiko wrote: > >> This is why I think the change is implicitly just for x86_64. > > Definitely not intentionally, might be just a bias of what we had most > hands-on experience with. Well, that is why it is so bad that you forced through this change behind the toolchain team's back. Th

Re: Schedule for Tuesday's FESCo Meeting (2023-01-03)

2023-01-06 Thread Kevin Kofler via devel
Michael Catanzaro wrote: > Benchmarks probably won't improve. And that alone is enough to make Fedora look bad and lose users to other distributions that cater to the Phoronix crowd. Kevin Kofler ___ devel mailing list -- devel@lists.fedoraproj

Re: Schedule for Tuesday's FESCo Meeting (2023-01-03)

2023-01-06 Thread Kevin Kofler via devel
Neal Gompa wrote: > For what it's worth, frame pointers are required on other operating > systems for precisely this reason What operating systems REQUIRE frame pointers? GCC supports -fomit-frame-pointer basically everywhere. Kevin Kofler ___

Re: Schedule for Tuesday's FESCo Meeting (2023-01-03)

2023-01-06 Thread Kevin Kofler via devel
Neal Gompa wrote: > On Wed, Jan 4, 2023 at 8:30 AM Vitaly Zaitsev via devel > wrote: >> >> On 03/01/2023 18:42, Miro Hrončok wrote: >> >* AGREED: APPROVED (+6,1,-1) This Change is implemented for Fedora >> > Linux 38 and we evaluate whether to retain it by Fedora Linux 40. >> > This

Re: Schedule for Tuesday's FESCo Meeting (2023-01-03)

2023-01-06 Thread Frank Ch. Eigler
Hi - > The thing is that perf + flamegraphs makes your whole system much more > visible and so it's much easier to find these kind of gains in > specific scenarios. (There are exist other profiling tools and techniques that do not require frame pointer recompilation, but whatever.) > Frame poi

Re: RISC-V -- are we ready for more, and what do we need to do it?

2023-01-06 Thread Jeff Law
On 1/6/23 16:19, Jun Aruga (he / him) wrote: I posted the same article on Fedora Discussion.[1] However let me share it again on the devel@ to tell it to many people. This is interesting news about RISC-V this week. Perhaps, it’s time to prepare to add the RISC-V CPU to the Koji build system?

Re: F38 proposal: Shorter Shutdown Timer (System-Wide Change proposal)

2023-01-06 Thread Peter Boy
> Am 06.01.2023 um 18:06 schrieb Michael Catanzaro : > > ... > > I think most of the feedback on this change can be summarized as: > > (a) Specific services want longer timeouts. > > This can already be configured via existing configuration mechanisms, so I > think it's safe enough to ignore

Re: RISC-V -- are we ready for more, and what do we need to do it?

2023-01-06 Thread Jun Aruga (he / him)
I posted the same article on Fedora Discussion.[1] However let me share it again on the devel@ to tell it to many people. This is interesting news about RISC-V this week. Perhaps, it’s time to prepare to add the RISC-V CPU to the Koji build system? Google wants RISC-V to be a “tier-1” Android arc

Re: F38 proposal: Ruby 3.2 (System-Wide Change proposal)

2023-01-06 Thread Dominik 'Rathann' Mierzejewski
On Wednesday, 04 January 2023 at 13:20, Vít Ondruch wrote: > Just to let everybody know, Ruby 3.2 has landed in Rawhide [1]. The binary > packages have been rebuilt, but there might be other compatibility issue. > > From top of my head, I know that sdformat will be FTBFS: > https://github.com/gaze

ImageMagick 7 is landing in Rawhide

2023-01-06 Thread Neal Gompa
Hey all, The initial rebase of ImageMagick to v7 is landing in Rawhide now: https://bodhi.fedoraproject.org/updates/FEDORA-2023-9d3e9afbfd Most packages in the reverse dependency chain were rebuilt, though a few are still left to fix and will be addressed separately. The ones remaining are: * a

Re: Self Introduction: Omar Sandoval

2023-01-06 Thread Dominik 'Rathann' Mierzejewski
Hello, Omar. On Friday, 06 January 2023 at 21:23, Omar Sandoval wrote: [...] > Fedora was the first Linux distro I ever tried back in high school, > and I've been using Linux exclusively ever since. I distro hopped a > bit over the years, but even when I wasn't using Fedora, I always > admired how

Re: TeXLive 2022 landing in rawhide today

2023-01-06 Thread Neal Gompa
On Thu, Jan 5, 2023 at 10:20 AM Michael Catanzaro wrote: > > On Wed, Jan 4 2023 at 11:46:26 PM -0500, Tom Callaway > wrote: > > Despite the size, I don't think TL updates have ever gone through > > that process before. Not opposed to doing it though, do we need to > > revert those builds from raw

Re: TeXLive 2022 landing in rawhide today

2023-01-06 Thread Jerry James
On Fri, Jan 6, 2023 at 1:41 PM Michael J Gruber wrote: > First breakage seems to be here: > > https://koji.fedoraproject.org/koji/taskinfo?taskID=95811080 > > Related to lua loading of otf fonts See https://bugzilla.redhat.com/show_bug.cgi?id=2158837 -- Jerry James http://www.jamezone.org/ _

Re: TeXLive 2022 landing in rawhide today

2023-01-06 Thread Michael J Gruber
First breakage seems to be here: https://koji.fedoraproject.org/koji/taskinfo?taskID=95811080 Related to lua loading of otf fonts ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org

Self Introduction: Omar Sandoval

2023-01-06 Thread Omar Sandoval
Hi everyone! My name is Omar Sandoval. Davide Cavalca just sponsored me as a packager and suggested that I introduce myself here. I am a Software Engineer on the Linux Kernel team at Meta. These days I spend most of my time on the debugger I created, drgn (https://github.com/osandov/drgn), as wel

Re: static USERMODEHELPER_PATH

2023-01-06 Thread Lennart Poettering
On Fr, 06.01.23 10:10, Steve Grubb (sgr...@redhat.com) wrote: > Hello, > > On Friday, January 6, 2023 9:33:12 AM EST Lennart Poettering wrote: > > On Do, 05.01.23 20:17, Steve Grubb (sgr...@redhat.com) wrote: > > > I work on RHEL security problems. I have been looking into a number of > > > exploi

Re: Schedule for Tuesday's FESCo Meeting (2023-01-03)

2023-01-06 Thread Davide Cavalca
On 2023-01-06 02:24, Jonathan Wakely wrote: Aside: could the change proposal please be updated to show *how* to opt out, not just state it can be done trivially? I shouldn't have to find https://src.fedoraproject.org/rpms/redhat-rpm-config/pull-request/231#request_diff to know whether the right

Re: F38 proposal: Shorter Shutdown Timer (System-Wide Change proposal)

2023-01-06 Thread Michael Catanzaro
On Fri, Jan 6 2023 at 11:06:26 AM -0600, Michael Catanzaro wrote: (a) Specific services want longer timeouts. This can already be configured via existing configuration mechanisms, so I think it's safe enough to ignore this problem. E.g. if a quick shutdown will brick your Pinephone modem or c

Re: F38 proposal: Shorter Shutdown Timer (System-Wide Change proposal)

2023-01-06 Thread Michael Catanzaro
On Fri, Jan 6 2023 at 09:47:29 AM -0500, Matthias Clasen wrote: On my Silverblue system, the main offender for this is podman. As soon as I have a toolbox running, conmon holds up the reboot for a very long time because it refuses to shutdown properly. Maybe instead of SIGKILL, we should

Re: static USERMODEHELPER_PATH

2023-01-06 Thread Steve Grubb
Hello, On Friday, January 6, 2023 10:10:21 AM EST Steve Grubb wrote: > One approach to solving this is to use selinux policy. I was informed > overnight that policy 38.2-1 should now enforce kernel transitions to > specific helper applications. So, maybe this is solved well enough? I can verify t

Re: F38 proposal: Shorter Shutdown Timer (System-Wide Change proposal)

2023-01-06 Thread Ralf Corsépius
Am 30.12.22 um 10:42 schrieb Peter Boy: Am 30.12.2022 um 06:59 schrieb Nico Kadel-Garcia : Am 28.12.22 um 11:49 schrieb Peter Boy: It is a good idea to make the timeout configurable. But the default timeout for servers must remain unchanged. My problem is not "defined timeouts" it is

Re: static USERMODEHELPER_PATH

2023-01-06 Thread Steve Grubb
Hello, On Friday, January 6, 2023 9:33:12 AM EST Lennart Poettering wrote: > On Do, 05.01.23 20:17, Steve Grubb (sgr...@redhat.com) wrote: > > I work on RHEL security problems. I have been looking into a number of > > exploits and I think we have a problem that has an easy fix. We are not > > usin

Re: F38 proposal: Shorter Shutdown Timer (System-Wide Change proposal)

2023-01-06 Thread Matthias Clasen
On my Silverblue system, the main offender for this is podman. As soon as I have a toolbox running, conmon holds up the reboot for a very long time because it refuses to shutdown properly. ___ devel mailing list -- devel@lists.fedoraproject.org To unsubs

Re: static USERMODEHELPER_PATH

2023-01-06 Thread Lennart Poettering
On Do, 05.01.23 20:17, Steve Grubb (sgr...@redhat.com) wrote: > Hello, > > I work on RHEL security problems. I have been looking into a number of > exploits and I think we have a problem that has an easy fix. We are not using > the CONFIG_STATIC_USERMODEHELPER_PATH kernel config option. There are

Review requests: perl-Feature-Compat-Class, perl-Feature-Compat-Try (needed for licensecheck update)

2023-01-06 Thread Sandro Mani
Hi licensecheck-3.3.1 grew two new dependencies, reviews here: perl-Feature-Compat-Class: https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=2158741 perl-Feature-Compat-Try: https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=2158742 Happy to review in exchange. Thanks Sandro ___

Re: Schedule for Tuesday's FESCo Meeting (2023-01-03)

2023-01-06 Thread Richard W.M. Jones
On Fri, Jan 06, 2023 at 10:24:39AM +, Jonathan Wakely wrote: > But they should be measurable, right? If profiling can't actually > measure performance and track improvements in performance, the change > isn't useful. So it should be possible to show the benefits over the > next release or two.

Fedora rawhide compose report: 20230106.n.0 changes

2023-01-06 Thread Fedora Rawhide Report
OLD: Fedora-Rawhide-20230105.n.0 NEW: Fedora-Rawhide-20230106.n.0 = SUMMARY = Added images:0 Dropped images: 5 Added packages: 5 Dropped packages:0 Upgraded packages: 144 Downgraded packages: 0 Size of added packages: 18.03 MiB Size of dropped packages:0

Re: Schedule for Tuesday's FESCo Meeting (2023-01-03)

2023-01-06 Thread Jonathan Wakely
On Thu, 5 Jan 2023 at 17:47, Demi Marie Obenour wrote: > > On 1/5/23 11:08, Frank Ch. Eigler wrote: > > > >> Of course, but the benefit is to fix performance bugs in applications > >> or maybe the desktop itself. [...] > > > >>> Let's be firm in testing this empirically rather than aspirationally.