[EPEL-devel] Fedora EPEL 7 updates-testing report

2024-02-19 Thread updates
The following builds have been pushed to Fedora EPEL 7 updates-testing ytree-2.07-1.el7 Details about builds: ytree-2.07-1.el7 (FEDORA-EPEL-2024-023e3fc2d0) A filemanager similar to XTree

[EPEL-devel] Fedora EPEL 8 updates-testing report

2024-02-19 Thread updates
The following Fedora EPEL 8 Security updates need testing: Age URL 5 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2024-0b7ba715af pdns-recursor-4.8.6-1.el8 3 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2024-aa663fed4a python-treq-20.4.1-1.el8 2

[EPEL-devel] Re: RFC: updating python-poetry-core in EPEL 9 to 1.6.1

2024-02-19 Thread Michel Lind
On Fri, Feb 16, 2024 at 01:44:34PM -0600, Michel Lind wrote: > On Fri, Feb 16, 2024 at 01:27:18PM -0600, Michel Lind wrote: > > except for python-asyncmy: > > https://copr.fedorainfracloud.org/coprs/salimma/poetry-core-epel9-wip/build/7026743/ > > > Looks like this is a known issue fixed in

Re: openQA update test backlog - now clearing

2024-02-19 Thread Adam Williamson
On Mon, 2024-02-19 at 23:28 +, Leslie Satenstein via devel wrote: > 4) After logging in, the keyboard layouts(user and root) are correct. > It is only the login screen. This is https://bugzilla.redhat.com/show_bug.cgi?id=2264930 . -- Adam Williamson (he/him/his) Fedora QA Fedora Chat:

Re: openQA update test backlog - now clearing

2024-02-19 Thread Leslie Satenstein via devel
Adam Please checkout bugzilla  2264943 I seem to have issues to post this bug where it can be reviewed on time for pre-release. Leslie Satenstein The bug readsBug 2264943 - Fedora40 anaconda Beta is not propagating keyboard selection to target system (edit) Description of problem:  I

Re: Schedule for Monday's FESCo Meeting (2024-02-19)

2024-02-19 Thread Zbigniew Jędrzejewski-Szmek
On Mon, Feb 19, 2024 at 06:26:24PM +, Mattia Verga via devel wrote: > Il 19/02/24 15:32, Zbigniew Jędrzejewski-Szmek ha scritto: > > Following is the list of topics that will be discussed in the > > FESCo meeting Monday at 19:30 UTC in #meeting:fedoraproject.org > > on Matrix. > > > Can you

Summary/Minutes from today's FESCo Meeting (2024-02-19)

2024-02-19 Thread Zbigniew Jędrzejewski-Szmek
Text Log: https://meetbot.fedoraproject.org/meeting_matrix_fedoraproject-org/2024-02-19/fesco.2024-02-19-19.35.log.txt HTML Log: https://meetbot.fedoraproject.org/meeting_matrix_fedoraproject-org/2024-02-19/fesco.2024-02-19-19.35.log.html Text Minutes:

[Test-Announce] Fedora-IoT 40 RC 20240219.0 nightly compose nominated for testing

2024-02-19 Thread rawhide
Announcing the creation of a new nightly release validation test event for Fedora-IoT 40 RC 20240219.0. Please help run some tests for this nightly compose if you have time. For more information on nightly release validation testing, see:

openQA update test backlog - now clearing

2024-02-19 Thread Adam Williamson
Hey folks! just a quick note in case anyone was waiting for openQA tests on their update. it seems one of the worker hosts got into some kind of stuck state, a lot of jobs were stuck at 'uploading'. unfortunately these are jobs that are set to *only* run on that host, so they were stuck

Re: Schedule for Monday's FESCo Meeting (2024-02-19)

2024-02-19 Thread Mattia Verga via devel
Il 19/02/24 15:32, Zbigniew Jędrzejewski-Szmek ha scritto: > Following is the list of topics that will be discussed in the > FESCo meeting Monday at 19:30 UTC in #meeting:fedoraproject.org > on Matrix. > Can you also clarify who should run the Inactive provenpackagers policy (which was scheduled

Re: Schedule for Monday's FESCo Meeting (2024-02-19)

2024-02-19 Thread Neal Gompa
On Mon, Feb 19, 2024 at 9:33 AM Zbigniew Jędrzejewski-Szmek wrote: > > Following is the list of topics that will be discussed in the > FESCo meeting Monday at 19:30 UTC in #meeting:fedoraproject.org > on Matrix. > > To convert UTC to your local time, take a look at >

[Bug 2264846] perl-Gnome2-VFS-1.084-12.fc41 FTBFS: build/vfs2perl-gtypes.c:28:5: error: ‘GNOME_VFS_DNS_SD_SERVICE_ADDED’ undeclared here

2024-02-19 Thread bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=2264846 Petr Pisar changed: What|Removed |Added Depends On||2264921 Referenced Bugs:

[Bug 2264846] perl-Gnome2-VFS-1.084-12.fc41 FTBFS: build/vfs2perl-gtypes.c:28:5: error: ‘GNOME_VFS_DNS_SD_SERVICE_ADDED’ undeclared here

2024-02-19 Thread bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=2264846 --- Comment #2 from Petr Pisar --- It is a regression in pkgconf. "pkg-config --modversion 'gnome-vfs-2.0 >= 2.0.0'" stopped returning gnome-vfs-2.0 version (e.g. 2.24.4). -- You are receiving this mail because: You are on the CC list for

[Bug 2264846] perl-Gnome2-VFS-1.084-12.fc41 FTBFS: build/vfs2perl-gtypes.c:28:5: error: ‘GNOME_VFS_DNS_SD_SERVICE_ADDED’ undeclared here

2024-02-19 Thread bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=2264846 --- Comment #1 from Petr Pisar --- The failure is preceded with: + perl Makefile.PL INSTALLDIRS=vendor NO_PACKLIST=1 NO_PERLLOCAL=1 'OPTIMIZE=-O2 -flto=auto -ffat-lto-objects -fexceptions -g -grecord-gcc-switches -pipe -Wall

Re: Feedback wanted - pruning old rawhide chroots in Copr

2024-02-19 Thread Neal Gompa
On Mon, Feb 19, 2024 at 10:18 AM Stephen Smoogen wrote: > > > > On Mon, 19 Feb 2024 at 10:08, Kevin Kofler via devel > wrote: >> >> Stephen Smoogen wrote: >> > 1. Drive size is not just what is needed but also throughput. The large >> > drives needed to store the data COPR uses for its hundreds

Re: Feedback wanted - pruning old rawhide chroots in Copr

2024-02-19 Thread Stephen Smoogen
On Mon, 19 Feb 2024 at 10:08, Kevin Kofler via devel < devel@lists.fedoraproject.org> wrote: > Stephen Smoogen wrote: > > 1. Drive size is not just what is needed but also throughput. The large > > drives needed to store the data COPR uses for its hundreds of chroots are > > much 'slower' on

Re: Feedback wanted - pruning old rawhide chroots in Copr

2024-02-19 Thread Kevin Kofler via devel
Stephen Smoogen wrote: > 1. Drive size is not just what is needed but also throughput. The large > drives needed to store the data COPR uses for its hundreds of chroots are > much 'slower' on reads and writes even when adding in layers of RAID 1+0. > Faster drives are possible but the price goes

Re: Feedback wanted - pruning old rawhide chroots in Copr

2024-02-19 Thread Miroslav Suchý
Dne 19. 02. 24 v 14:59 Kevin Kofler via devel napsal(a): Instead of coming up with new aggressive pruning schemes, Copr really needs to come up with a reasonable amount of storage to satisfy user demands. HDDs in the multi-TB-range are available for fairly low budgets (extremely low by the

Schedule for Monday's FESCo Meeting (2024-02-19)

2024-02-19 Thread Zbigniew Jędrzejewski-Szmek
Following is the list of topics that will be discussed in the FESCo meeting Monday at 19:30 UTC in #meeting:fedoraproject.org on Matrix. To convert UTC to your local time, take a look at http://fedoraproject.org/wiki/UTCHowto or run: date -d '2024-02-19 19:30 UTC' Links to all issues to be

Re: Feedback wanted - pruning old rawhide chroots in Copr

2024-02-19 Thread Stephen Smoogen
On Mon, 19 Feb 2024 at 08:59, Kevin Kofler via devel < devel@lists.fedoraproject.org> wrote: > Miroslav Suchý wrote: > > What **you** would find as acceptable policy for pruning rawhide chroots? > > As I mentioned several times, I already find the existing policy for > pruning > EOL release

Re: Feedback wanted - pruning old rawhide chroots in Copr

2024-02-19 Thread David Bold
> On Sun, Feb 18, 2024 at 4:25 PM Michael J Gruber wrote: > I like this idea. Move things that were built for "rawhide" into the > "fedora-40" chroot, and start Rawhide empty, requiring fresh builds of > things. > Since there is no equivalent to the mass rebuild in COPR, that would > also solve

Re: Feedback wanted - pruning old rawhide chroots in Copr

2024-02-19 Thread Kevin Kofler via devel
Miroslav Suchý wrote: > What **you** would find as acceptable policy for pruning rawhide chroots? As I mentioned several times, I already find the existing policy for pruning EOL release chroots unacceptable (because deleting data must never be the default – notifications can be and are still

Orphaning raptor

2024-02-19 Thread Jaroslav Škarvada
Hi, I would like to step-out from raptor maintenance [1] and orphan it. Currently, raptor is obsoleted by raptor2 and IMHO unsupported. It seems it's required only by the COPASI package in Fedora thanks & regards Jaroslav [1] https://src.fedoraproject.org/rpms/raptor --

Introduction

2024-02-19 Thread Patrice Peterson via devel
Hello to all and sundry! I've been a Fedora user for close to ten years but I've never been involved with the project itself, aside from reporting a few bugs here and there. Been using Linux for ~20 years, more or less – started out on Ubuntu, moved over to Arch, and then Fedora. On Arch, I

Re: The semiannual "Transaction failed: Signature verification failed." exercise

2024-02-19 Thread Zbigniew Jędrzejewski-Szmek
On Sun, Feb 18, 2024 at 12:32:45PM +, Zbigniew Jędrzejewski-Szmek wrote: > On Fri, Feb 16, 2024 at 09:37:25AM -0800, Kevin Fenzi wrote: > > On Fri, Feb 16, 2024 at 11:12:07AM +, Zbigniew Jędrzejewski-Szmek wrote: > > > In my earlier message I quoted this case: > > > > > > > [1] From > >

Fedora 40 compose report: 20240219.n.0 changes

2024-02-19 Thread Fedora Branched Report
OLD: Fedora-40-20240218.n.0 NEW: Fedora-40-20240219.n.0 = SUMMARY = Added images:3 Dropped images: 1 Added packages: 2 Dropped packages:0 Upgraded packages: 68 Downgraded packages: 1 Size of added packages: 97.00 KiB Size of dropped packages:0 B Size

[Test-Announce] [Test Day] GNOME 46 Desktop & Core Apps

2024-02-19 Thread Sumantro Mukherjee
Hey All, We're excited to invite you to the GNOME 46 Test Week! This is a unique opportunity to get early access to new features, identify bugs, and contribute to improving GNOME's usability and stability. Your participation is vital to ensure GNOME 46 meets our community's high standards. To

[Test-Announce] Fedora 40 Branched 20240219.n.0 nightly compose nominated for testing

2024-02-19 Thread rawhide
Announcing the creation of a new nightly release validation test event for Fedora 40 Branched 20240219.n.0. Please help run some tests for this nightly compose if you have time. For more information on nightly release validation testing, see: https://fedoraproject.org/wiki

Fedora rawhide compose report: 20240219.n.0 changes

2024-02-19 Thread Fedora Rawhide Report
OLD: Fedora-Rawhide-20240218.n.0 NEW: Fedora-Rawhide-20240219.n.0 = SUMMARY = Added images:2 Dropped images: 3 Added packages: 2 Dropped packages:0 Upgraded packages: 84 Downgraded packages: 1 Size of added packages: 97.05 KiB Size of dropped packages:0 B

Re: The semiannual "Transaction failed: Signature verification failed." exercise

2024-02-19 Thread Vít Ondruch
Dne 16. 02. 24 v 18:27 Kevin Fenzi napsal(a): On Fri, Feb 16, 2024 at 09:46:05AM +0100, Vít Ondruch wrote: Other solution could be if Rawhide lived in rawhide repos instead of f41. I'm not sure I follow... rawhide is in a rawhide repo? pub/fedora/linux/development/rawhide/ I stand

[Bug 2264848] New: perl-Gtk2-1.24993-15.fc41 FTBFS: Can't load 'blib/arch/auto/Gtk2/Gtk2.so' for module Gtk2: blib/arch/auto/Gtk2/Gtk2.so: undefined symbol: SvGdkAtom at /usr/lib64/perl5/DynaLoader.pm

2024-02-19 Thread bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=2264848 Bug ID: 2264848 Summary: perl-Gtk2-1.24993-15.fc41 FTBFS: Can't load 'blib/arch/auto/Gtk2/Gtk2.so' for module Gtk2: blib/arch/auto/Gtk2/Gtk2.so: undefined symbol:

[Bug 2264846] New: perl-Gnome2-VFS-1.084-12.fc41 FTBFS: build/vfs2perl-gtypes.c:28:5: error: ‘GNOME_VFS_DNS_SD_SERVICE_ADDED’ undeclared here

2024-02-19 Thread bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=2264846 Bug ID: 2264846 Summary: perl-Gnome2-VFS-1.084-12.fc41 FTBFS: build/vfs2perl-gtypes.c:28:5: error: ‘GNOME_VFS_DNS_SD_SERVICE_ADDED’ undeclared here Product: Fedora

Re: do we need CONFIG_UPROBES=y in our kernels?

2024-02-19 Thread Björn Persson
Marius Schwarz wrote: > From guest to host:  you need to trust the host not to spy on you, your > data, connection targets aso. Correct. This is a fundamental principle. Users are at the mercy of the sysadmin. Programs are at the mercy of the operating system. Virtual machines are at the mercy