Re: Direct to stable updates

On 11/10/22 21:02, Gary Buhrmaster wrote: > On Fri, Nov 11, 2022 at 12:52 AM Stephen Smoogen wrote: >> On Thu, Nov 10, 2022 at 18:55 Neal Gompa wrote: >>> >>> I sympathize greatly here. It was a pain to wire up "logout" to the >>> "relogin" property in updateinfo (the field had been in bodhi for

Re: OpenMPI tests blocked

On 11/6/22 07:31, Dominik 'Rathann' Mierzejewski wrote: On Saturday, 05 November 2022 at 21:27, Antonio T. sagitter wrote: Hi all. Many OpenMPI tests in RPM packaging are blocked for unknown reason, no output or error, just hanged until test timeout. For example, PETSc test is blocked with this

Re: Direct to stable updates

Neal Gompa wrote: > Bodhi is an unusually difficult codebase for what it does. IMHO, the main reason the Bodhi code is so complex is because of all the policy that it enforces: karma (counting), update policies (minimum karma/time), critical path, autopushes, gating (automatic QA), … If we woul

Re: Direct to stable updates

On Fri, Nov 11, 2022 at 12:52 AM Stephen Smoogen wrote: > > > > On Thu, Nov 10, 2022 at 18:55 Neal Gompa wrote: >> >> I sympathize greatly here. It was a pain to wire up "logout" to the >> "relogin" property in updateinfo (the field had been in bodhi for a >> decade and nobody wired it up to the

Re: F37 proposal: Add -fno-omit-frame-pointer to default compilation flags (System-Wide Change proposal)

On 11/10/22 08:59, Michael Catanzaro wrote: > On Wed, Nov 9 2022 at 09:39:04 AM +0100, Vitaly Zaitsev via devel > wrote: >> According to tests, this will slow down your system to 2.5%+, which is >> unacceptable for a general purpose distribution. > > Of course, without the frame pointers, profil

Re: Direct to stable updates

On Thu, Nov 10, 2022 at 18:55 Neal Gompa wrote: > On Thu, Nov 10, 2022 at 3:49 PM Kevin Fenzi wrote: > > > > On Thu, Nov 10, 2022 at 05:16:44PM +, Mattia Verga via devel wrote: > > > It shouldn't be too hard, it's just that Bodhi code is > > > sometimes so contorted that by making a simple c

Re: Direct to stable updates

On Thu, Nov 10, 2022 at 3:49 PM Kevin Fenzi wrote: > > On Thu, Nov 10, 2022 at 05:16:44PM +, Mattia Verga via devel wrote: > > It shouldn't be too hard, it's just that Bodhi code is > > sometimes so contorted that by making a simple change it's easy to break > > something else... moving update

Re: F38 prospoal: Enable bootupd for Fedora Silverblue & Kinoite (Self-Contained Change proposal)

Ben Cotton writes: > By design, ostree does not manage bootloader updates as they can not > (yet) happen in a transactional, atomic and safe fashion. As we've talked about before, it's not possible to make updates transactional. It involves, per spec and depending on processor architecture, upd

FYI: mutter + wayland are broken in F36 ATM

Hi, Mutter for Gnome 42.5.3 does not work with wayland for AST and Intel Graphics . ATM, it ends in a black screen. This involves M$ Surface devices, server onboard graphics and maybe more. Workarounds for users are switching to lightdm or downgrading to mutter 41.9-1. https://bugzilla.red

Re: New OpenColorIO 2.2.0 requires yaml-cpp 0.7.0

Update on progress... I have one build failure unrelated to yaml-cpp for a package I don't maintain, supercollider: In file included from /usr/include/sndfile.h:6, from /builddir/build/BUILD/SuperCollider-3.12.2-Source/server/plugins/DiskIO_UGens.cpp:27: /usr/include/sndfile-64.h

Re: F38 proposal: Perl: Replace versioned MODULE_COMPAT_ requires by macro (System-Wide Change proposal)

On 10. 11. 22 21:23, Ben Cotton wrote: The macro ''%perl_require_compat'' will evaluate the run-require based on ''%{_target_cpu}''. The macro will be defined in the rpm ''perl-srpm-macros'' and the definition is: `%perl_require_compat %[ "%{_target_cpu}" == "noarch" ? "perl-libs" : "%{!?perl_ve

Re: Direct to stable updates

On Thu, Nov 10, 2022 at 05:16:44PM +, Mattia Verga via devel wrote: > Il 10/11/22 01:58, Kevin Kofler via devel ha scritto: > > Kevin Kofler via devel wrote: > > > >> Mattia Verga via devel wrote: > >>> with the current workflow, Bodhi doesn't know when a release is freezed. > >>> There is supp

Re: F37 proposal: Add -fno-omit-frame-pointer to default compilation flags (System-Wide Change proposal)

On Wed, Nov 09, 2022 at 04:26:23AM +, Naheem Zaffar wrote: > On Tue, 8 Nov 2022, 19:22 Vitaly Zaitsev via devel, < > devel@lists.fedoraproject.org> wrote: > > > On 08/11/2022 19:53, Naheem Zaffar wrote: > > > Has there been any consideration to turn on frame pointers for atleast > > > dev rele

Re: F37 proposal: Add -fno-omit-frame-pointer to default compilation flags (System-Wide Change proposal)

On 10/11/2022 14:59, Michael Catanzaro wrote: Of course, without the frame pointers, profiling software is impossible and performance engineers are unable to investigate performance problems using Fedora. 99.999% shouldn't suffer because of 0.001%. -- Sincerely, Vitaly Zaitsev (vit...@easyc

Re: Help understanding Fedora CI failure wrt RPM Sequoia

On Thu, Nov 10, 2022 at 11:39:27AM +0200, Panu Matilainen wrote: > > So, overnight somebody updated the koji package in > https://kojipkgs.fedoraproject.org/repos/rawhide/ to the current unsigned > rawhide build, which makes the issue go away. Nothing should have updated the koji package. The l

Re: F38 proposal: MobilityPhoshImage (Self-Contained Change proposal)

On Thu, Nov 10, 2022 at 01:35:36AM -, Scott Anecito via devel wrote: > What is the driver for choosing Phosh over GNOME Shell? There's no choosing something over something else. This isn't a Fedora Mobility Edition, but rather a first look at a Phosh based setup. Phosh has been around a long

F38 prospoal: Enable bootupd for Fedora Silverblue & Kinoite (Self-Contained Change proposal)

https://fedoraproject.org/wiki/Changes/FedoraSilverblueBootupd 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

F38 proposal: Build Fedora Silverblue & Kinoite using rpm-ostree unified core mode (Self-Contained Change proposal)

https://fedoraproject.org/wiki/Changes/FedoraSilverblueUnifiedCore 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 Steer

F38 proposal: Reproducible builds: Clamp build mtimes to $SOURCE_DATE_EPOCH (System-Wide Change proposal)

https://fedoraproject.org/wiki/Changes/ReproducibleBuildsClampMtimes 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 Ste

F38 proposal: Perl: Replace versioned MODULE_COMPAT_ requires by macro (System-Wide Change proposal)

https://fedoraproject.org/wiki/Changes/Perl_replace_MODULE_COMPAT_by_macro 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 Engineeri

[Test-Announce] Fedora Linux 37 Final is GO

The Fedora Linux 37 Final RC 1.7 compose is GO and will be shipped live on Tuesday, 15 November. For more information please check the Go/No-Go meeting minutes[1] or log[2]. [1] https://meetbot.fedoraproject.org/fedora-meeting/2022-11-10/f37-final-go_no_go-meeting.2022-11-10-17.02.html [2] https

Re: Direct to stable updates

Il 10/11/22 01:58, Kevin Kofler via devel ha scritto: > Kevin Kofler via devel wrote: > >> Mattia Verga via devel wrote: >>> with the current workflow, Bodhi doesn't know when a release is freezed. >>> There is support for a "Freeze" state, but it was never used. >> How do we prevent then that push

Re: Deprecating intents in Modularity

V Wed, Nov 02, 2022 at 04:45:41PM +0100, Petr Pisar napsal(a): > do you know intents > ? [...] > > * I was told that even RHEL, from version 9, does not use syst

gaps test failed

Hello, My update [1] failed because the gaps test failed sbin/mount.nfs: gap: (0x5590..0x55a0 probable component: __printf_chk) in annobin notes. /sbin/mount.nfs: gap: (0x11760..0x11770 probable component: __printf_chk) in annobin notes. /sbin/mount.nfs: FAIL: gaps test because gaps were det

Re: Heads-up: python-pytest-bdd 6.1.1 coming to Rawhide

On Thu, 10 Nov 2022, Ben Beasley wrote: In one week (2022-11-17), or slightly later, I will update python-pytest-bdd from version 5.0.0 to version 6.1.1[1] in Rawhide. This will bring significant API-breaking changes[2] from 5.x. The sole dependent package, jrnl, does not support version 6.x yet

Heads-up: python-pytest-bdd 6.1.1 coming to Rawhide

In one week (2022-11-17), or slightly later, I will update python-pytest-bdd from version 5.0.0 to version 6.1.1[1] in Rawhide. This will bring significant API-breaking changes[2] from 5.x. The sole dependent package, jrnl, does not support version 6.x yet[3], and the changes required are nontr

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: SPDX Change update

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? Eike -- GPG key 0x6A6CD5B765632D3A - 2265 D7F3 A7B0 95CC 3918 63

Re: F37 proposal: Add -fno-omit-frame-pointer to default compilation flags (System-Wide Change proposal)

On Thu, Nov 10, 2022 at 9:00 AM Michael Catanzaro wrote: > > On Wed, Nov 9 2022 at 09:39:04 AM +0100, Vitaly Zaitsev via devel > wrote: > > According to tests, this will slow down your system to 2.5%+, which is > > unacceptable for a general purpose distribution. > > Of course, without the frame

Re: F37 proposal: Add -fno-omit-frame-pointer to default compilation flags (System-Wide Change proposal)

On Wed, Nov 9 2022 at 09:39:04 AM +0100, Vitaly Zaitsev via devel wrote: According to tests, this will slow down your system to 2.5%+, which is unacceptable for a general purpose distribution. Of course, without the frame pointers, profiling software is impossible and performance engineers ar

Re: Heads-up: Side-tag rebuild due to minizip-ng soname bump

On Mon, Nov 7, 2022 at 6:41 AM Lukas Javorsky wrote: > Hi, > > Minizip-ng has changed its soname name from "libminizip.so.3.0" to > "libminizip.so.3" thus we need to rebuild all the packages that are > requiring this soname. > Are you also updating to 3.0.6? The latest version of OpenColorIO req

Re: SPDX Change update - Missing identifier for XDebug

Le 10/11/2022 à 13:48, Miroslav Suchý a écrit : Dne 10. 11. 22 v 12:04 Remi Collet napsal(a): What is the process to ask for a new SPDX id ? Open an issue for https://gitlab.com/fedora/legal/fedora-license-data Done as https://gitlab.com/fedora/legal/fedora-license-data/-/issues/95 Rem

Fedora rawhide compose report: 20221110.n.0 changes

OLD: Fedora-Rawhide-20221109.n.0 NEW: Fedora-Rawhide-20221110.n.0 = SUMMARY = Added images:0 Dropped images: 2 Added packages: 2 Dropped packages:1 Upgraded packages: 87 Downgraded packages: 0 Size of added packages: 68.61 KiB Size of dropped packages

Re: SPDX Change update - Missing identifier for XDebug

Dne 10. 11. 22 v 12:04 Remi Collet napsal(a): I'm searching for License identifier for php-pecl-xdebug which was "BSD" It is based on PHP-3.0 which is based on BSD-3-Clause What should I use ? You are speaking about  https://github.com/xdebug/xdebug/blob/master/LICENSE I pasted the content

Fedora 37 compose report: 20221110.n.0 changes

OLD: Fedora-37-20221109.n.0 NEW: Fedora-37-20221110.n.0 = SUMMARY = Added images:0 Dropped images: 0 Added packages: 0 Dropped packages:0 Upgraded packages: 0 Downgraded packages: 0 Size of added packages: 0 B Size of dropped packages:0 B Size of upgraded

Re: SPDX Change update - Missing identifier for XDebug

I'm searching for License identifier for php-pecl-xdebug which was "BSD" It is based on PHP-3.0 which is based on BSD-3-Clause What should I use ? What is the process to ask for a new SPDX id ? Thanks, Remi ___ devel mailing list -- devel@lists.fedor

Re: SPDX Change update

Dne 09. 11. 22 v 17:00 Fabio Valentini napsal(a): On Wed, Nov 9, 2022 at 2:52 PM Miroslav Suchý wrote: Dne 09. 11. 22 v 13:58 Neal Gompa napsal(a): What do we do if the SPDX tag is the same as the existing license tag (eg ISC) though? Do we just add a dummy change/commit entry that mentions SP

Re: Help understanding Fedora CI failure wrt RPM Sequoia

On 11/9/22 11:12, Panu Matilainen wrote: On 11/9/22 10:08, Panu Matilainen wrote: On 11/8/22 21:45, Adam Williamson wrote: On Tue, 2022-11-08 at 08:11 -0800, Adam Williamson wrote: On Tue, 2022-11-08 at 13:32 +0200, Panu Matilainen wrote: But I don't know the slightest thing about ansible, b

Re: SPDX Change update

Dne 09. 11. 22 v 15:05 Gary Buhrmaster napsal(a): Does it make sense for your script in some future iteration to add in the capability to check if the license is identical pre/post SPDX if the spec does not have a changelog or commit message mentioning SPDX? Either hard code the cases (not ideal

Wayland support on Blender coming to Fedora

Hello everyone, Upstream Blender developers are on the way to bring Wayland support for the next release [1] which will benefit Fedora users running on Workstation edition. The Fedora version already has support on Rawhide [2] since 3.3.0 noticeable with a different window decoration which use l