Re: libmpc: fedora-ci.koji-build.tier0.functional failure

2023-01-09 Thread Petr Pisar
V Mon, Jan 09, 2023 at 11:50:45AM -0700, Jerry James napsal(a): > Hi everyone, > > I built an update for libmpc in Rawhide a few weeks ago, then didn't > have time to follow up due to holiday-related travel. (I'm one of > those people you saw on TV sitting around in airports due to canceled > fli

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

2023-01-09 Thread Zbigniew Jędrzejewski-Szmek
On Mon, Jan 09, 2023 at 11:53:17PM +0100, Kevin Kofler via devel wrote: > Am Montag, 9. Jänner 2023 23:06:17 CET schrieb Zbigniew Jędrzejewski-Szmek: > > On Sun, Jan 08, 2023 at 06:06:47PM +0100, Kevin Kofler via devel wrote: > > > Kevin Kofler via devel wrote: > > > PS: The impression I get is tha

Re: F38 proposal: Rpmautospec by Default (System-Wide Change proposal)

2023-01-09 Thread Zbigniew Jędrzejewski-Szmek
On Mon, Jan 09, 2023 at 09:37:44PM -0600, Richard Shaw wrote: > Now I'm getting bit by the rpmautospec and COPR issue. Please be more precise. How are you building the rpms? If rpmautospec is used in COPR, and the build is started in a compatible way, the release field should be the same as in ko

Re: F38 proposal: Rpmautospec by Default (System-Wide Change proposal)

2023-01-09 Thread Richard Shaw
Now I'm getting bit by the rpmautospec and COPR issue. I'm trying to test rebuilds of all dependent packages for a new OpenColorIO release, but usd uses rpmautospec and in Fedora it's usd--16 but COPR is calculating it as usd--9 so the Fedora version has a higher NEVR. Now what am I supposed to d

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

2023-01-09 Thread Siddhesh Poyarekar
On Mon, Jan 9, 2023 at 5:53 PM Kevin Kofler via devel wrote: > * It made wrong assumptions about the performance impact of > _FORTIFY_SOURCE=3, which, compared to the already existing (!) > _FORTIFY_SOURCE=2, appears to actually have NO performance impact at all > (!), only compared to no _FORTIFY

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

2023-01-09 Thread Kevin Kofler via devel
Demi Marie Obenour wrote: > On 1/6/23 20:35, Frank Ch. Eigler wrote: >> (There are exist other profiling tools and techniques that do not >> require frame pointer recompilation, but whatever.) > > Which ones? I would love for them to exist, and I believe there is > work being done in that direct

python-cryptography license fix

2023-01-09 Thread Charalampos Stratakis
The license of python-cryptography was changed to SPDX and also fixed after clarification from upstream from "ASL 2.0 or BSD" to "(Apache-2.0 OR BSD-3-Clause) AND PSF-2.0" -- Regards, Charalampos Stratakis Senior Software Engineer Python Maintenance Team, Red Hat

Re: FESCo revote on "Add -fno-omit-frame-pointer" Change proposal [was Re: Schedule for Tuesday's FESCo Meeting (2023-01-03)]

2023-01-09 Thread Kevin Kofler via devel
Miro Hrončok wrote: > Considering the mass rebuild is happening really soon, I feel like > repeating the vote later is not helpful, but if people want to, we can > surely run the vote again. However, I am confident the result will be the > same. With all this talk about the mass rebuild being immi

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

2023-01-09 Thread Kevin Kofler via devel
Am Montag, 9. Jänner 2023 23:06:17 CET schrieb Zbigniew Jędrzejewski-Szmek: On Sun, Jan 08, 2023 at 06:06:47PM +0100, Kevin Kofler via devel wrote: Kevin Kofler via devel wrote: PS: The impression I get is that everything was deliberately rigged so that the vote would end up the way it did:

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

2023-01-09 Thread Zbigniew Jędrzejewski-Szmek
On Sun, Jan 08, 2023 at 06:06:47PM +0100, Kevin Kofler via devel wrote: > Kevin Kofler via devel wrote: > > Still, it gives an extremely bad impression of rushing this through > > without giving anybody the chance to object. > > > > I also do not see why this needed to be approved for F38 on such

Re: FESCo revote on "Add -fno-omit-frame-pointer" Change proposal [was Re: Schedule for Tuesday's FESCo Meeting (2023-01-03)]

2023-01-09 Thread Mark Wielaard
Hi Matthew, On Mon, Jan 09, 2023 at 11:47:54AM -0500, Matthew Miller wrote: > On Sun, Jan 08, 2023 at 06:06:47PM +0100, Kevin Kofler via devel wrote: > > Therefore, I hereby request that the vote be annulled as having happened > > in violation of the Change policy. > > So, from a purely "what are

Re: FESCo revote on "Add -fno-omit-frame-pointer" Change proposal [was Re: Schedule for Tuesday's FESCo Meeting (2023-01-03)]

2023-01-09 Thread Tom Stellard
On 1/9/23 12:27, Kevin Kofler via devel wrote: Am Montag, 9. Jänner 2023 21:02:48 CET schrieb Tom Stellard: I think a good solution would be to move the proposal submission deadlines a month earlier in the schedule.  There's only 3 weeks between the "Changes Requiring Mass Rebuild" deadline and

Re: FESCo revote on "Add -fno-omit-frame-pointer" Change proposal [was Re: Schedule for Tuesday's FESCo Meeting (2023-01-03)]

2023-01-09 Thread Tom Stellard
On 1/9/23 08:47, Matthew Miller wrote: It might be useful to improve both the documented policies. The Changes policy has nothing about reconsidering Changes in the current cycle that I can see. (Or, actually, for that matter, for resubmitting in future cycles either, unless i'm missing somethin

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

2023-01-09 Thread Zbigniew Jędrzejewski-Szmek
On Sat, Jan 07, 2023 at 12:59:26AM +0100, Peter Boy wrote: > > > 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 v

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

2023-01-09 Thread Zbigniew Jędrzejewski-Szmek
On Mon, Jan 09, 2023 at 11:04:11AM +0100, Lennart Poettering wrote: > On Fr, 06.01.23 11:06, Michael Catanzaro (mcatanz...@redhat.com) wrote: > > > Maybe instead of SIGKILL, we should send SIGQUIT instead. That way abrt > > should complain next time you boot and users will have an opportunity to >

Re: FESCo revote on "Add -fno-omit-frame-pointer" Change proposal [was Re: Schedule for Tuesday's FESCo Meeting (2023-01-03)]

2023-01-09 Thread Kevin Kofler via devel
Am Montag, 9. Jänner 2023 21:02:48 CET schrieb Tom Stellard: I think a good solution would be to move the proposal submission deadlines a month earlier in the schedule. There's only 3 weeks between the "Changes Requiring Mass Rebuild" deadline and the mass rebuild. I don't think 3 weeks is rea

Re: static USERMODEHELPER_PATH

2023-01-09 Thread Simo Sorce
On Fri, 2023-01-06 at 18:21 +0100, Lennart Poettering wrote: > 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

Re: FESCo revote on "Add -fno-omit-frame-pointer" Change proposal [was Re: Schedule for Tuesday's FESCo Meeting (2023-01-03)]

2023-01-09 Thread Tom Stellard
On 1/9/23 11:18, Neal Gompa wrote: On Mon, Jan 9, 2023 at 2:11 PM Daniel P. Berrangé wrote: On Mon, Jan 09, 2023 at 11:47:54AM -0500, Matthew Miller wrote: On Sun, Jan 08, 2023 at 06:06:47PM +0100, Kevin Kofler via devel wrote: PS: The impression I get is that everything was deliberately rig

Re: FESCo revote on "Add -fno-omit-frame-pointer" Change proposal [was Re: Schedule for Tuesday's FESCo Meeting (2023-01-03)]

2023-01-09 Thread Daan De Meyer via devel
> I think it would save everyone a bit of time if we restricted the change > to x86-64. We do not have much experience with the -mbackchain flag > that was added at the last minute on s390x. The change owners have > stated that they aren't interested in s390x. IBM doesn't want this. > Platform T

Re: FESCo revote on "Add -fno-omit-frame-pointer" Change proposal [was Re: Schedule for Tuesday's FESCo Meeting (2023-01-03)]

2023-01-09 Thread Neal Gompa
On Mon, Jan 9, 2023 at 2:11 PM Daniel P. Berrangé wrote: > > On Mon, Jan 09, 2023 at 11:47:54AM -0500, Matthew Miller wrote: > > On Sun, Jan 08, 2023 at 06:06:47PM +0100, Kevin Kofler via devel wrote: > > > PS: The impression I get is that everything was deliberately rigged so > > > that > > > th

Re: FESCo revote on "Add -fno-omit-frame-pointer" Change proposal [was Re: Schedule for Tuesday's FESCo Meeting (2023-01-03)]

2023-01-09 Thread Kevin Kofler via devel
Am Montag, 9. Jänner 2023 20:10:53 CET schrieb Daniel P. Berrangé: Holding a FESCo meeting and vote on the very first working day after the long xmas / new year holiday is not exactly good timing if you want contributors to be broadly aware it is happening[1]. I might humbly suggest that next yea

Re: FESCo revote on "Add -fno-omit-frame-pointer" Change proposal [was Re: Schedule for Tuesday's FESCo Meeting (2023-01-03)]

2023-01-09 Thread Daniel P . Berrangé
On Mon, Jan 09, 2023 at 11:47:54AM -0500, Matthew Miller wrote: > On Sun, Jan 08, 2023 at 06:06:47PM +0100, Kevin Kofler via devel wrote: > > PS: The impression I get is that everything was deliberately rigged so that > > the vote would end up the way it did: > > > > 1. A new ticket was filed, in

libmpc: fedora-ci.koji-build.tier0.functional failure

2023-01-09 Thread Jerry James
Hi everyone, I built an update for libmpc in Rawhide a few weeks ago, then didn't have time to follow up due to holiday-related travel. (I'm one of those people you saw on TV sitting around in airports due to canceled flights.) One test failed: fedora-ci.koji-build.tier0.functional. I have trie

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

2023-01-09 Thread Demi Marie Obenour
On 1/6/23 20:35, Frank Ch. Eigler wrote: > > 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 f

F38 proposal: Noto CJK Variable Fonts (Self-Contained Change proposal)

2023-01-09 Thread Ben Cotton
https://fedoraproject.org/wiki/Changes/Noto_CJK_Variable_Fonts This document represents a proposed Change. As part of the Changes process, proposals are publicly announced in order to receive community feedback. This proposal will only be implemented if approved by the Fedora Engineering Steering

Re: FESCo revote on "Add -fno-omit-frame-pointer" Change proposal [was Re: Schedule for Tuesday's FESCo Meeting (2023-01-03)]

2023-01-09 Thread Florian Weimer
* Matthew Miller: > BUT, I do not think it was done with malice, as "deliberately rigged" > implies. I don't see that at all -- I see excitement and interest in moving > forward on something that already has taken a long time, and looming > practical deadlines. No one spoke out when the tools tea

Re: FESCo revote on "Add -fno-omit-frame-pointer" Change proposal [was Re: Schedule for Tuesday's FESCo Meeting (2023-01-03)]

2023-01-09 Thread Miro Hrončok
On 09. 01. 23 17:47, Matthew Miller wrote: On Sun, Jan 08, 2023 at 06:06:47PM +0100, Kevin Kofler via devel wrote: PS: The impression I get is that everything was deliberately rigged so that the vote would end up the way it did: 1. A new ticket was filed, in order to exclude the participants of

Re: FESCo revote on "Add -fno-omit-frame-pointer" Change proposal [was Re: Schedule for Tuesday's FESCo Meeting (2023-01-03)]

2023-01-09 Thread Kevin Kofler via devel
Am Montag, 9. Jänner 2023 17:47:54 CET schrieb Matthew Miller: And, from a practical point of view, since this passed with six +1 votes, I'm not sure what benefit canceling and re-voting would really add. Canceling the vote and requiring that the Change Policy be followed would mean that the c

Re: FESCo revote on "Add -fno-omit-frame-pointer" Change proposal [was Re: Schedule for Tuesday's FESCo Meeting (2023-01-03)]

2023-01-09 Thread Frank Ch. Eigler
Matthew Miller writes: > So, from a purely "what are the rules?" view, the Change process says: > FESCo will vote to approve or deny a change proposal in accordance with > the FESCo ticket policy. > > ... and I won't quote all of that, but looking at > https://docs.fedoraproject.org/en-US/fes

Re: F38 proposal: Add Fedora Auto Firstboot Services to desktop variants (System-Wide Change proposal)

2023-01-09 Thread Timothée Ravier
Working on having a better Firefox shipped as a Flatpak by default will please a lot of people that as asking for Firefox to be removed from the base image: https://github.com/fedora-silverblue/issue-tracker/issues/288 If we can have Cisco host a container image with openh264 as a Flatpak exten

FESCo revote on "Add -fno-omit-frame-pointer" Change proposal [was Re: Schedule for Tuesday's FESCo Meeting (2023-01-03)]

2023-01-09 Thread Matthew Miller
On Sun, Jan 08, 2023 at 06:06:47PM +0100, Kevin Kofler via devel wrote: > PS: The impression I get is that everything was deliberately rigged so that > the vote would end up the way it did: > > 1. A new ticket was filed, in order to exclude the participants of the > previous discussion. > 2. The

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

2023-01-09 Thread Matthias Clasen
On Sat, Jan 7, 2023 at 9:31 AM Giuseppe Scrivano wrote: > > I've just opened a PR upstream for Podman to kill -9 all the remaining > exec sessions when the container process terminates, so both --pid=host > and --pid=private behaves in the same way. It would solve the issue we > are seeing. > >

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

2023-01-09 Thread Josh Boyer
On Mon, Jan 9, 2023 at 9:15 AM Neal Gompa wrote: > > On Mon, Jan 9, 2023 at 8:47 AM Josh Boyer wrote: > > > > On Sun, Jan 8, 2023 at 2:42 AM David Abdurachmanov > > wrote: > > > > > > On Sun, Jan 8, 2023 at 2:28 AM Jeff Law wrote: > > > > > > > > > > > > > > > > On 1/6/23 23:41, David Abdurachm

Re: Starting Flatpak SIG

2023-01-09 Thread Kalev Lember
On Thu, Jan 5, 2023 at 10:55 AM Kalev Lember wrote: > Hi all, > > Hopefully most people are back from vacations now so I think we can go on > with organizing the first Flatpak SIG meeting. > > I have created a whenisgood poll for the next week: > https://whenisgood.net/s3rzh5h > Please put your n

libharu 2.4.3, mathgl 8.0.1, vtk 9.2.5 update coming to rawhide soon

2023-01-09 Thread Orion Poplawski
I'm hoping to start updating libharu to 2.4.3, mathgl to 8.0.1, and vtk to 9.2.5 at the end of this week. Builds will be done in a side tag. Test builds are being done here: https://copr.fedorainfracloud.org/coprs/orion/libharu2.4/builds/ -- Orion Poplawski he/him/his - surely the least imp

Re: Help with Rust packaging

2023-01-09 Thread Fabio Valentini
On Mon, Jan 9, 2023 at 3:25 PM Maxwell G via devel wrote: > > > Jan 7, 2023 4:41:29 PM Lumír Balhar : > > > y-py upstream uses maturin as a build backend which is not available in > > Fedora yet so I had to add some metadata manually to port it to > > setuptools-rust > Why not package maturin? Is

Re: Help with Rust packaging

2023-01-09 Thread Maxwell G via devel
Jan 7, 2023 4:41:29 PM Lumír Balhar : y-py upstream uses maturin as a build backend which is not available in Fedora yet so I had to add some metadata manually to port it to setuptools-rust Why not package maturin? Is there something particularly problematic about maturin (e.g. lots of missin

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

2023-01-09 Thread Jeff Law
On 1/9/23 07:14, Neal Gompa wrote: It is very unlikely that CentOS Stream 10 will include RISC-V as a fully included architecture. Perhaps via a CentOS Stream SIG. I believe that was the implication in the first place, hence mentioning CentOS Stream rather than RHEL. The Alternative Arch

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

2023-01-09 Thread Neal Gompa
On Mon, Jan 9, 2023 at 8:47 AM Josh Boyer wrote: > > On Sun, Jan 8, 2023 at 2:42 AM David Abdurachmanov > wrote: > > > > On Sun, Jan 8, 2023 at 2:28 AM Jeff Law wrote: > > > > > > > > > > > > On 1/6/23 23:41, David Abdurachmanov wrote: > > > > > > > > Summary from multi-year discussions/feedback

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

2023-01-09 Thread Josh Boyer
On Sun, Jan 8, 2023 at 2:42 AM David Abdurachmanov wrote: > > On Sun, Jan 8, 2023 at 2:28 AM Jeff Law wrote: > > > > > > > > On 1/6/23 23:41, David Abdurachmanov wrote: > > > > > > Summary from multi-year discussions/feedback on this: > > > - We don't have proper hardware to put into the data cen

Non-responsive maintainer check for amatyuko

2023-01-09 Thread Ali Erdinc Koroglu
Hello everyone! Does anyone know how to contact Andrey Matyukov (amatyuko)? I have tried to reach out via email but have not received a response. https://bugzilla.redhat.com/show_bug.cgi?id=2159390 -- Ali Erdinc Koroglu Linux OS Systems Engineering __

Re: ImageMagick 7 is landing in Rawhide

2023-01-09 Thread Dan Horák
On Mon, 9 Jan 2023 06:46:59 -0500 Neal Gompa wrote: > On Mon, Jan 9, 2023 at 6:42 AM Neal Gompa wrote: > > > > On Mon, Jan 9, 2023 at 6:30 AM Dan Horák wrote: > > > > > > On Fri, 6 Jan 2023 16:34:29 -0500 > > > Neal Gompa wrote: > > > > > > > Hey all, > > > > > > > > The initial rebase of Imag

Re: ImageMagick 7 is landing in Rawhide

2023-01-09 Thread Neal Gompa
On Mon, Jan 9, 2023 at 6:42 AM Neal Gompa wrote: > > On Mon, Jan 9, 2023 at 6:30 AM Dan Horák wrote: > > > > On Fri, 6 Jan 2023 16:34:29 -0500 > > Neal Gompa wrote: > > > > > Hey all, > > > > > > The initial rebase of ImageMagick to v7 is landing in Rawhide now: > > > https://bodhi.fedoraproject

Re: ImageMagick 7 is landing in Rawhide

2023-01-09 Thread Neal Gompa
On Mon, Jan 9, 2023 at 6:30 AM Dan Horák wrote: > > On Fri, 6 Jan 2023 16:34:29 -0500 > Neal Gompa wrote: > > > 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 rever

Re: ImageMagick 7 is landing in Rawhide

2023-01-09 Thread Dan Horák
On Fri, 6 Jan 2023 16:34:29 -0500 Neal Gompa wrote: > 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

Re: WASM from Ruby - Lightning Chess Web App

2023-01-09 Thread Jun Aruga (he / him)
Hi Philip, I added a Ruby SiG mailing list to TO. Folks at Ruby SiG, Could you take a look at the message below? Philip is trying to create a RPM package including WASM built Ruby binaries. Your feedback is helpful. On Mon, Jan 9, 2023 at 11:00 AM Philip Rhoades wrote: > > Jun, > > > On 2023-01-

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

2023-01-09 Thread Arthur Bols
On 9/01/2023 10:09, Mamoru TASAKA wrote: Honestly saying, I cannot understand this context, why native English speaker or not is relevant here, especially because I am also non-native. I don't think Fedora committers change their attitude against between native or non-native English speakers. M

Re: Help with Rust packaging

2023-01-09 Thread Miro Hrončok
On 07. 01. 23 23:41, Lumír Balhar wrote: Hi. I'm working on packaging new version of Juyter Notebook and Lab into Fedora and I have a problem with one Rust/Python package - y-py. The problem is that when I'm building python-y-py in COPR https://copr.fedorainfracloud.org/coprs/lbalhar/noteboo

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

2023-01-09 Thread Mark Wielaard
Hi Neal, On Wed, 2023-01-04 at 08:44 -0500, Neal Gompa wrote: > On Wed, Jan 4, 2023 at 8:30 AM Vitaly Zaitsev via devel > wrote: > > > > Already rejected proposal was submitted because big corporations > > weren't > > happy with the results. This is a VERY BAD precedent for Fedora. > > > > Act

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

2023-01-09 Thread Lennart Poettering
On Fr, 06.01.23 11:06, Michael Catanzaro (mcatanz...@redhat.com) wrote: > Maybe instead of SIGKILL, we should send SIGQUIT instead. That way abrt > should complain next time you boot and users will have an opportunity to > report bugs to the package maintainer, instead of the problem being forever

Re: WASM from Ruby - Lightning Chess Web App

2023-01-09 Thread Philip Rhoades via devel
Jun, On 2023-01-09 00:36, Jun Aruga (he / him) wrote: On Sun, Jan 8, 2023 at 11:51 AM Philip Rhoades via devel wrote: People, Over the holidays we had our irregular Family Lightning Chess competition (10 seconds per move) - I have not found an online web site that will work exactly with o

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

2023-01-09 Thread Mamoru TASAKA
Neal Gompa wrote on 2023/01/09 11:58: I'm extremely tired of how you communicate on this mailing list. I've been quiet about it for years and years. But people leave Fedora because of you. Once again, I'm having discussions with people trying to convince them Fedora isn't a bad place because of

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

2023-01-09 Thread Vitaly Zaitsev via devel
On 09/01/2023 03:58, Neal Gompa wrote: I'm extremely tired of how you communicate on this mailing list. I've been quiet about it for years and years. But people leave Fedora because of you. Once again, I'm having discussions with people trying to convince them Fedora isn't a bad place because of