Re: F41 Change Proposal: Replace Redis with Valkey (system-wide)
On Fri, Apr 19, 2024 at 2:29 PM Maxwell G wrote: > On Fri Apr 19, 2024 at 14:23 +1000, Nathan Scott wrote: > > The package does not have any Obsoletes, so nothing should happen unless > users take explicit action to install valkey. > Yes, that's my point - if someone installs valkey, their redis installation is essentially trashed. I'd say "fair enough" if this was rawhide and we're working on the transition still, but this is stable Fedora, EPEL and user's data. cheers. -- Nathan -- ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: F41 Change Proposal: Replace Redis with Valkey (system-wide)
On Fri Apr 19, 2024 at 14:23 +1000, Nathan Scott wrote: > Hi Neal, > > On Thu, Apr 18, 2024 at 1:02 PM Neal Gompa wrote: > > On Wed, Apr 17, 2024 at 10:43 PM Nathan Scott wrote: > > > On Thu, Apr 18, 2024 at 12:29 PM Neal Gompa wrote: > > > > [...] > > > > retaining Redis will just hurt us in the long term. > > > > > > Noone is saying we should retain Redis. I'm advocating for a more > > > appropriate transition that is respectful of the work and expertise the > > > existing package maintainers bring. > > > > > > I think f41 is appropriate and possible, but "more haste, less speed" > > > is the way to get there, with minimal breakage to Fedora and users. > > > > > > > From my perspective, I don't see any breakage happening. We also > > haven't *done* anything yet. > > > > Sooo, about that... :) I see there is a valkey build winging its way > toward f39 and f38 now: > https://bodhi.fedoraproject.org/updates/?packages=valkey > > If someone has an active redis installation on those systems and > install that - aren't they in for a bit of a surprise? Correct me if I'm > wrong, but this will replace redis - leaving /var/lib/redis with their > current data, and start a new "redis-server" (aka "valkey-server") > process writing into a new, empty rdb file below /var/lib/valkey, no? > If so, how do they reconcile those split rdb files? > > Let's slow down a bit, it's not so urgent that we risk peoples data. The package does not have any Obsoletes, so nothing should happen unless users take explicit action to install valkey. -- ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: F41 Change Proposal: Replace Redis with Valkey (system-wide)
Hi Neal, On Thu, Apr 18, 2024 at 1:02 PM Neal Gompa wrote: > On Wed, Apr 17, 2024 at 10:43 PM Nathan Scott wrote: > > On Thu, Apr 18, 2024 at 12:29 PM Neal Gompa wrote: > > > [...] > > > retaining Redis will just hurt us in the long term. > > > > Noone is saying we should retain Redis. I'm advocating for a more > > appropriate transition that is respectful of the work and expertise the > > existing package maintainers bring. > > > > I think f41 is appropriate and possible, but "more haste, less speed" > > is the way to get there, with minimal breakage to Fedora and users. > > > > From my perspective, I don't see any breakage happening. We also > haven't *done* anything yet. > Sooo, about that... :) I see there is a valkey build winging its way toward f39 and f38 now: https://bodhi.fedoraproject.org/updates/?packages=valkey If someone has an active redis installation on those systems and install that - aren't they in for a bit of a surprise? Correct me if I'm wrong, but this will replace redis - leaving /var/lib/redis with their current data, and start a new "redis-server" (aka "valkey-server") process writing into a new, empty rdb file below /var/lib/valkey, no? If so, how do they reconcile those split rdb files? Let's slow down a bit, it's not so urgent that we risk peoples data. cheers. -- Nathan -- ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
[EPEL-devel] Fedora EPEL 8 updates-testing report
The following Fedora EPEL 8 Security updates need testing: Age URL 4 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2024-762aef7cb1 chromium-123.0.6312.122-1.el8 1 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2024-99cf4e74b7 putty-0.81-1.el8 The following builds have been pushed to Fedora EPEL 8 updates-testing ansible-collection-awx-awx-24.2.0-1.el8 libabigail-2.5-1.el8 the_foundation-1.8.1-4.el8 uwsgi-2.0.25.1-1.el8 Details about builds: ansible-collection-awx-awx-24.2.0-1.el8 (FEDORA-EPEL-2024-8e214ec683) Ansible modules and plugins for working with AWX Update Information: Update to 24.2.0-1 ChangeLog: * Wed Apr 17 2024 Andrew Heath - 24.2.0-1 - Update to 24.2.0 libabigail-2.5-1.el8 (FEDORA-EPEL-2024-21389dba7c) Set of ABI analysis tools Update Information: Update to upstream 2.5 tarball ChangeLog: * Wed Apr 17 2024 Dodji Seketeli - 2.5-1 - Update to upstream 2.5 tarball - Drop patches 0001-Bug-31045-Don-t-try-setting-translation-unit-for-uni.patch 0002-suppression-Add-has_strict_flexible_array_data_membe.patch 0003-Replace-deprecated-mock-with-unittest.mock.patch - Package libabigail.so.4 rather than the previous libabigail.so.3. - Disable abidb as it requires python 3.9 - Better handle error handling when tests fails. the_foundation-1.8.1-4.el8 (FEDORA-EPEL-2024-483555335a) Opinionated C11 library for low-level functionality Update Information: Upstream changelog: https://codeberg.org/skyjake/the_Foundation/src/branch/main/CHANGES.md ChangeLog: * Wed Apr 17 2024 Michel Lind - Update to 1.8.1 (rhbz#2274997) * Sat Jan 27 2024 Fedora Release Engineering - 1.7.0-2 - Rebuilt for https://fedoraproject.org/wiki/Fedora_40_Mass_Rebuild References: [ 1 ] Bug #2274997 - the_foundation-1.8.1 is available https://bugzilla.redhat.com/show_bug.cgi?id=2274997 uwsgi-2.0.25.1-1.el8 (FEDORA-EPEL-2024-be4ebde20e) Fast, self-healing, application container server Update Information: Update to 2.0.25.1, drop merged patches ChangeLog: * Tue Apr 16 2024 Ralf Ertzinger - 2.0.25.1-1 - Update to 2.0.25.1, drop merged patches - Use github.com as source for the main tarball - Do not build for i686 any more * Tue Mar 19 2024 Dominik Mierzejewski - 2.0.24-2 - Rebuilt for gloox-1.0.28 References: [ 1 ] Bug #2275174 - uwsgi-2.0.25.1 is available https://bugzilla.redhat.com/show_bug.cgi?id=2275174 -- ___ epel-devel mailing list -- epel-devel@lists.fedoraproject.org To unsubscribe send an email to epel-devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/epel-devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
[Bug 2257225] perl-Clipboard: clipbrowse command execution with multi-line clipboard text including "| sh" [fedora-all]
https://bugzilla.redhat.com/show_bug.cgi?id=2257225 Fedora Update System changed: What|Removed |Added Fixed In Version|perl-Clipboard-0.29-1.fc41 |perl-Clipboard-0.29-1.fc41 ||perl-Clipboard-0.29-1.fc39 --- Comment #8 from Fedora Update System --- FEDORA-2024-43a0920f12 (perl-Clipboard-0.29-1.fc39) has been pushed to the Fedora 39 stable repository. If problem still persists, please make note of it in this bug report. -- You are receiving this mail because: You are on the CC list for the bug. https://bugzilla.redhat.com/show_bug.cgi?id=2257225 Report this comment as SPAM: https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla=report-spam_desc=Report%20of%20Bug%202257225%23c8 -- ___ perl-devel mailing list -- perl-devel@lists.fedoraproject.org To unsubscribe send an email to perl-devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/perl-devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
[Bug 2257224] perl-Clipboard: clipbrowse command execution with multi-line clipboard text including "| sh" [epel-all]
https://bugzilla.redhat.com/show_bug.cgi?id=2257224 Fedora Update System changed: What|Removed |Added Fixed In Version|perl-Clipboard-0.29-1.fc41 |perl-Clipboard-0.29-1.fc41 |perl-Clipboard-0.29-1.el9 |perl-Clipboard-0.29-1.el9 |perl-Clipboard-0.29-1.el7 |perl-Clipboard-0.29-1.el7 ||perl-Clipboard-0.29-1.el8 --- Comment #12 from Fedora Update System --- FEDORA-EPEL-2024-f060b59d26 (perl-Clipboard-0.29-1.el8) has been pushed to the Fedora EPEL 8 stable repository. If problem still persists, please make note of it in this bug report. -- You are receiving this mail because: You are on the CC list for the bug. https://bugzilla.redhat.com/show_bug.cgi?id=2257224 Report this comment as SPAM: https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla=report-spam_desc=Report%20of%20Bug%202257224%23c12 -- ___ perl-devel mailing list -- perl-devel@lists.fedoraproject.org To unsubscribe send an email to perl-devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/perl-devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
[Bug 2257224] perl-Clipboard: clipbrowse command execution with multi-line clipboard text including "| sh" [epel-all]
https://bugzilla.redhat.com/show_bug.cgi?id=2257224 Fedora Update System changed: What|Removed |Added Fixed In Version|perl-Clipboard-0.29-1.fc41 |perl-Clipboard-0.29-1.fc41 |perl-Clipboard-0.29-1.el9 |perl-Clipboard-0.29-1.el9 ||perl-Clipboard-0.29-1.el7 --- Comment #11 from Fedora Update System --- FEDORA-EPEL-2024-a8b1cd8e52 (perl-Clipboard-0.29-1.el7) has been pushed to the Fedora EPEL 7 stable repository. If problem still persists, please make note of it in this bug report. -- You are receiving this mail because: You are on the CC list for the bug. https://bugzilla.redhat.com/show_bug.cgi?id=2257224 Report this comment as SPAM: https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla=report-spam_desc=Report%20of%20Bug%202257224%23c11 -- ___ perl-devel mailing list -- perl-devel@lists.fedoraproject.org To unsubscribe send an email to perl-devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/perl-devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
[Bug 2257224] perl-Clipboard: clipbrowse command execution with multi-line clipboard text including "| sh" [epel-all]
https://bugzilla.redhat.com/show_bug.cgi?id=2257224 Fedora Update System changed: What|Removed |Added Fixed In Version|perl-Clipboard-0.29-1.fc41 |perl-Clipboard-0.29-1.fc41 ||perl-Clipboard-0.29-1.el9 --- Comment #10 from Fedora Update System --- FEDORA-EPEL-2024-6ebc36e81d (perl-Clipboard-0.29-1.el9) has been pushed to the Fedora EPEL 9 stable repository. If problem still persists, please make note of it in this bug report. -- You are receiving this mail because: You are on the CC list for the bug. https://bugzilla.redhat.com/show_bug.cgi?id=2257224 Report this comment as SPAM: https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla=report-spam_desc=Report%20of%20Bug%202257224%23c10 -- ___ perl-devel mailing list -- perl-devel@lists.fedoraproject.org To unsubscribe send an email to perl-devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/perl-devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
[EPEL-devel] Re: RFC: Proposing incompatible upgrade of python-asgiref from 3.4.1 to 3.7.2
Hi all, On 4/11/24 16:25, Michel Lind wrote: Dear all, Django 4.2 (the only currently supported LTS series) requires asgiref >= 3.6, so I would like to propose updating python-asgiref in EPEL 9 at least to 3.6.0, but ideally to 3.8.1 for future proofing. The affected packages (maintainers bcc:ed) are python-django3 (which I maintain, and has just reached EOL) and python-opentelemetry ❯ fedrq whatrequires 'python3dist(asgiref)' -b epel9 python-django3-3.2.20-3.el9.src python-opentelemetry-1.12.0-8.el9.src ❯ fedrq pkgs --src -P python-django3 -F requires -b epel9 | grep asgi python3dist(asgiref) >= 3.3.2 (python3dist(asgiref) < 4~~ with python3dist(asgiref) >= 3.3.2) ❯ fedrq pkgs --src -P python-opentelemetry -F requires -b epel9 | grep asgi (python3dist(asgiref) >= 3 with python3dist(asgiref) < 4) It's been a week, the maintainers of the specific packages have granted their approval and the Steering Committee has been consulted. Since opentelemetry and django3 builds fine with asgiref 3.7.2 from Fedora, I have now built it and published an update: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2024-d56e78a735 Best regards, -- _o) Michel Lind _( ) identities: https://keyoxide.org/5dce2e7e9c3b1cffd335c1d78b229d2f7ccc04f2 OpenPGP_0x8B229D2F7CCC04F2.asc Description: OpenPGP public key OpenPGP_signature.asc Description: OpenPGP digital signature -- ___ epel-devel mailing list -- epel-devel@lists.fedoraproject.org To unsubscribe send an email to epel-devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/epel-devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: [Test-Announce] Fedora Linux 40 Final is GO Need to fix up for good grub.cfg Cant install Workstation and KDE on same system.
On 4/18/24 14:09, Leslie Satenstein via devel wrote: Even when the two distros are on separate drives. I have tested all combinations, and Fedora40 grub2-mkconfig does not allow two Fedora40's on the same system. Try it. Put F40Workstation on one drive and F40KDE on a second drive It doesn't matter if they're on separate drives. They are still on the same system and that's not a supported configuration. -- ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: [Test-Announce] Fedora Linux 40 Final is GO Need to fix up for good grub.cfg Cant install Workstation and KDE on same system.
Even when the two distros are on separate drives. I have tested all combinations, and Fedora40 grub2-mkconfig does not allow two Fedora40's on the same system. Try it. Put F40Workstation on one drive and F40KDE on a second drive Leslie Satenstein On Thursday, April 18, 2024 at 04:45:35 p.m. EDT, Samuel Sieb wrote: On 4/18/24 12:42, Leslie Satenstein via devel wrote: > With my testing, I could not install one copy of Fedora40gnome and then > on the same system the copy of Fedora40KDE. > > Whatever came second, has a signature for grub2-mkconfig, that causes > the first F40 menuentrys to be replaced by the latter. My computer bios > shows the same duplicates. > > But I am OK with F39 and F40 being on the same drive. Please don't massively cross-post like this. Having multiple installs of Fedora on the same system is not a "supported" configuration. You're kind of on your own for that. -- ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue -- ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: [Test-Announce] Fedora Linux 40 Final is GO Need to fix up for good grub.cfg Cant install Workstation and KDE on same system.
On 4/18/24 12:42, Leslie Satenstein via devel wrote: With my testing, I could not install one copy of Fedora40gnome and then on the same system the copy of Fedora40KDE. Whatever came second, has a signature for grub2-mkconfig, that causes the first F40 menuentrys to be replaced by the latter. My computer bios shows the same duplicates. But I am OK with F39 and F40 being on the same drive. Please don't massively cross-post like this. Having multiple installs of Fedora on the same system is not a "supported" configuration. You're kind of on your own for that. -- ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: F41 Change Proposal - Reproducible Package Builds (System-Wide)
On 4/17/24 12:54 AM, Zbigniew Jędrzejewski-Szmek wrote: On Wed, Apr 17, 2024 at 09:38:30AM +0200, Miroslav Suchý wrote: Dne 17. 04. 24 v 9:20 dop. Zbigniew Jędrzejewski-Szmek napsal(a): By adding this functionality to Mock itself. It can be optional (--add-determinism). And then Mock can call add-determinism $chroot/%buildroot/ I don't think we should make this particular functionality special. We have a bunch of brps: It depends... if you want to have this check/sanitization part of rpmbuild. When it is small,and does not inflate buildroot, then fine. Over the years, I learn that people have different view where each component should go. :) I will not argue. If you package add-determinism I can help you to add it to Mock. Likely as plugin: https://rpm-software-management.github.io/mock/#plugins that is called in `postbuild` https://rpm-software-management.github.io/mock/Plugin-Hooks And by helping I mean that I will create the initial PR and you (and others) will test the functionality. Deal? Thank you for the offer. I _might_ take you up on it later, but for now, I think it's better to keep this inside of the buildroot. I don't think that this functionality should be tied to mock. Right now, the helper runs for 'fedpkg local' (as all brps), but if it's moved to mock, then we'd need to at least call it from two places. A lot of our security libraries create cryptographic checksums on the binaries that need to be correct in order for them to run in FIPS mode. If this is actually changing the binaries, we'll need to rerun those checksums. bob Zbyszek -- ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue -- ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
[Bug 2275982] New: perl-DateTime-Locale-1.42 is available
https://bugzilla.redhat.com/show_bug.cgi?id=2275982 Bug ID: 2275982 Summary: perl-DateTime-Locale-1.42 is available Product: Fedora Version: rawhide Status: NEW Component: perl-DateTime-Locale Keywords: FutureFeature, Triaged Assignee: jples...@redhat.com Reporter: upstream-release-monitor...@fedoraproject.org QA Contact: extras...@fedoraproject.org CC: iarn...@gmail.com, jples...@redhat.com, perl-devel@lists.fedoraproject.org Target Milestone: --- Classification: Fedora Releases retrieved: 1.42 Upstream release that is considered latest: 1.42 Current version/release in rawhide: 1.41-1.fc41 URL: https://metacpan.org/dist/DateTime-Locale/ Please consult the package updates policy before you issue an update to a stable branch: https://docs.fedoraproject.org/en-US/fesco/Updates_Policy/ More information about the service that created this bug can be found at: https://docs.fedoraproject.org/en-US/package-maintainers/Upstream_Release_Monitoring Please keep in mind that with any upstream change, there may also be packaging changes that need to be made. Specifically, please remember that it is your responsibility to review the new version to ensure that the licensing is still correct and that no non-free or legally problematic items have been added upstream. Based on the information from Anitya: https://release-monitoring.org/project/6477/ To change the monitoring settings for the project, please visit: https://src.fedoraproject.org/rpms/perl-DateTime-Locale -- You are receiving this mail because: You are on the CC list for the bug. https://bugzilla.redhat.com/show_bug.cgi?id=2275982 Report this comment as SPAM: https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla=report-spam_desc=Report%20of%20Bug%202275982%23c0 -- ___ perl-devel mailing list -- perl-devel@lists.fedoraproject.org To unsubscribe send an email to perl-devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/perl-devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: [Test-Announce] Fedora Linux 40 Final is GO Need to fix up for good grub.cfg Cant install Workstation and KDE on same system.
Hi Guys, With my testing, I could not install one copy of Fedora40gnome and then on the same system the copy of Fedora40KDE. Whatever came second, has a signature for grub2-mkconfig, that causes the first F40 menuentrys to be replaced by the latter. My computer bios shows the same duplicates. But I am OK with F39 and F40 being on the same drive. Leslie Satenstein On Thursday, April 18, 2024 at 02:27:24 p.m. EDT, Aoife Moloney wrote: The Fedora Linux 40 Final RC1.14 compose is GO and will be shipped live on Tuesday, 23rd April. For more information please check the Go/No-Go meeting minutes[1] or log[2], and a huge thank you to everyone involved in this release! [1] https://meetbot.fedoraproject.org/meeting_matrix_fedoraproject-org/2024-04-18/f40-final-go-no-go-meeting.2024-04-18-17.01.html [2] https://meetbot.fedoraproject.org/meeting_matrix_fedoraproject-org/2024-04-18/f40-final-go-no-go-meeting.2024-04-18-17.01.log.html -- Aoife Moloney Fedora Operations Architect Fedora Project Matrix: @amoloney:fedora.im IRC: amoloney -- ___ test-announce mailing list -- test-annou...@lists.fedoraproject.org To unsubscribe send an email to test-announce-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/test-annou...@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue -- ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue -- ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: Picking up protobuf
On Thu, Apr 18, 2024 at 3:06 PM Michel Lind wrote: > > Hi Major, > > On 4/18/24 13:25, Major Hayden wrote: > > On Wed, Apr 17, 2024, at 21:51, Michel Lind wrote: > >> Hi all, > >> > >> protobuf was recently orphaned without any announcement to this list. > >> > >> I've picked it up since et depends on it. > > > > Thanks for picking that up, Michel. I intended to mail the list yesterday > > and totally lost track of time. 臘♂️ > > > No worries! I was wondering who the previous maintainer was - the RHBZ > overrides made it super confusing :) > > > The big challenge we had with protobuf is that updating it broke quite a > > few things built against the old version. But staying put with the same > > version led to problems with newer packages that were coming along day by > > day. > > > Yeah... it might be worth just upgrading in Rawhide and not touch the stable > releases, as Sérgio suggested, > unless there is an urgent security update? We should let maintainers of > protobuf dependents chime in too. > I do the same for capnproto for the same reason. :) -- 真実はいつも一つ！/ Always, there's only one truth! -- ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
[Bug 2275976] New: perl-Text-CSV_XS-1.54 is available
https://bugzilla.redhat.com/show_bug.cgi?id=2275976 Bug ID: 2275976 Summary: perl-Text-CSV_XS-1.54 is available Product: Fedora Version: rawhide Status: NEW Component: perl-Text-CSV_XS Keywords: FutureFeature, Triaged Assignee: p...@city-fan.org Reporter: upstream-release-monitor...@fedoraproject.org QA Contact: extras...@fedoraproject.org CC: anon.am...@gmail.com, ka...@ucw.cz, mspa...@redhat.com, p...@city-fan.org, perl-devel@lists.fedoraproject.org, xav...@bachelot.org Target Milestone: --- Classification: Fedora Releases retrieved: 1.54 Upstream release that is considered latest: 1.54 Current version/release in rawhide: 1.53-3.fc40 URL: http://search.cpan.org/dist/Text-CSV_XS/ Please consult the package updates policy before you issue an update to a stable branch: https://docs.fedoraproject.org/en-US/fesco/Updates_Policy/ More information about the service that created this bug can be found at: https://docs.fedoraproject.org/en-US/package-maintainers/Upstream_Release_Monitoring Please keep in mind that with any upstream change, there may also be packaging changes that need to be made. Specifically, please remember that it is your responsibility to review the new version to ensure that the licensing is still correct and that no non-free or legally problematic items have been added upstream. Based on the information from Anitya: https://release-monitoring.org/project/3434/ To change the monitoring settings for the project, please visit: https://src.fedoraproject.org/rpms/perl-Text-CSV_XS -- You are receiving this mail because: You are on the CC list for the bug. https://bugzilla.redhat.com/show_bug.cgi?id=2275976 Report this comment as SPAM: https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla=report-spam_desc=Report%20of%20Bug%202275976%23c0 -- ___ perl-devel mailing list -- perl-devel@lists.fedoraproject.org To unsubscribe send an email to perl-devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/perl-devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: F41 Change Proposal: Replace Redis with Valkey (system-wide)
On Thu Apr 18, 2024 at 11:51 +1000, Nathan Scott wrote: > > > == Owner == > > > * Name: [[User:jonathanspw|Jonathan Wright]] > > > * Email: jonat...@almalinux.org > > > > It would be nice to have Remi who currently maintains redis on board as > > well. > > > > This is the second time this has been requested, but not yet actioned. > > https://bugzilla.redhat.com/show_bug.cgi?id=2274206 > https://src.fedoraproject.org/rpms/valkey > https://src.fedoraproject.org/rpms/redis > > Can we resolve this before allowing this Change Proposal to proceed, > please? I think its in Fedora's interest to see 'new redis' maintained > by group, rather than an individual, if the existing maintainers wish to > (continue to) be involved. > > The 'new' valkey package is very closely derived from redis packaging > which other Fedora maintainers have been looking after for ~14 years. Yeah, I strongly agree. Thank you, Nathan and Remi, for the work you've done to maintain redis up until now. -- ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: Picking up protobuf
Hi Major, On 4/18/24 13:25, Major Hayden wrote: On Wed, Apr 17, 2024, at 21:51, Michel Lind wrote: Hi all, protobuf was recently orphaned without any announcement to this list. I've picked it up since et depends on it. Thanks for picking that up, Michel. I intended to mail the list yesterday and totally lost track of time. 臘♂️ No worries! I was wondering who the previous maintainer was - the RHBZ overrides made it super confusing :) The big challenge we had with protobuf is that updating it broke quite a few things built against the old version. But staying put with the same version led to problems with newer packages that were coming along day by day. Yeah... it might be worth just upgrading in Rawhide and not touch the stable releases, as Sérgio suggested, unless there is an urgent security update? We should let maintainers of protobuf dependents chime in too. Best regards, -- _o) Michel Lind _( ) identities: https://keyoxide.org/5dce2e7e9c3b1cffd335c1d78b229d2f7ccc04f2 OpenPGP_0x8B229D2F7CCC04F2.asc Description: OpenPGP public key OpenPGP_signature.asc Description: OpenPGP digital signature -- ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: F41 Change Proposal: Replace Redis with Valkey (system-wide)
On 4/18/24 00:51, Remi Collet wrote:
Le 17/04/2024 à 18:37, Maxwell G a écrit :
On Wed Apr 17, 2024 at 16:38 +0100, Aoife Moloney wrote:
Thank you for submitting this!
I agree we’ll have to get rid of redis in the future, and than such a
switch will make a strong statement about our disapproval to redis
about this License change.
But I also think this is a bit early (F41)
- Valkey is very young, and they is no proof it will be best choice
- Redis 7.2 is still there and maintained (even version 6.2 and 7.0
are maintained), and keeping it have no security issue.
So I’m -1 for F41 and probably +1 for F42
One option is to introduce {valkey,redict}-redis-compat packages now
(users could "dnf swap redis " themselves) and then
consider making one "the default" and Obsoleting redis in F42.
--
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct:
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives:
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam, report it:
https://pagure.io/fedora-infrastructure/new_issue
Fedora Linux 40 Final is GO
The Fedora Linux 40 Final RC1.14 compose is GO and will be shipped live on Tuesday, 23rd April. For more information please check the Go/No-Go meeting minutes[1] or log[2], and a huge thank you to everyone involved in this release! [1] https://meetbot.fedoraproject.org/meeting_matrix_fedoraproject-org/2024-04-18/f40-final-go-no-go-meeting.2024-04-18-17.01.html [2] https://meetbot.fedoraproject.org/meeting_matrix_fedoraproject-org/2024-04-18/f40-final-go-no-go-meeting.2024-04-18-17.01.log.html -- Aoife Moloney Fedora Operations Architect Fedora Project Matrix: @amoloney:fedora.im IRC: amoloney -- ___ devel-announce mailing list -- devel-announce@lists.fedoraproject.org To unsubscribe send an email to devel-announce-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel-announce@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
[Test-Announce] Fedora Linux 40 Final is GO
The Fedora Linux 40 Final RC1.14 compose is GO and will be shipped live on Tuesday, 23rd April. For more information please check the Go/No-Go meeting minutes[1] or log[2], and a huge thank you to everyone involved in this release! [1] https://meetbot.fedoraproject.org/meeting_matrix_fedoraproject-org/2024-04-18/f40-final-go-no-go-meeting.2024-04-18-17.01.html [2] https://meetbot.fedoraproject.org/meeting_matrix_fedoraproject-org/2024-04-18/f40-final-go-no-go-meeting.2024-04-18-17.01.log.html -- Aoife Moloney Fedora Operations Architect Fedora Project Matrix: @amoloney:fedora.im IRC: amoloney -- ___ test-announce mailing list -- test-annou...@lists.fedoraproject.org To unsubscribe send an email to test-announce-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/test-annou...@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue -- ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: Picking up protobuf
On Wed, Apr 17, 2024, at 21:51, Michel Lind wrote: > Hi all, > > protobuf was recently orphaned without any announcement to this list. > > I've picked it up since et depends on it. Thanks for picking that up, Michel. I intended to mail the list yesterday and totally lost track of time. 臘♂️ The big challenge we had with protobuf is that updating it broke quite a few things built against the old version. But staying put with the same version led to problems with newer packages that were coming along day by day. -- Major Hayden -- ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: F40 Change: Privacy-preserving Telemetry for Fedora Workstation (System-Wide)
I'm worried about seeing someone here on this discussion list lowering the importance of privacy. On Thu, Apr 18, 2024 at 2:53 PM Igor Kerstges wrote: > Privacy is not too much of my concern. > > How much data is to be expected to be sent over my dataplan on monthly > basis? When using Fedora Workstations as a graphics workstation (including > regular office applications) during office hours and extensive internet > research and entertainment during (late)evenings and weekends, should I > expect this to generate data of some 10's of KB, or should I expect it to > amount to megabytes? Will this be uploaded on scheduled daily interval or > more regularly? Can I monitor the traffic on my firewall (and how)? > > Good luck with the upcoming release soon! Cheers, > Igor > -- > ___ > devel mailing list -- devel@lists.fedoraproject.org > To unsubscribe send an email to devel-le...@lists.fedoraproject.org > Fedora Code of Conduct: > https://docs.fedoraproject.org/en-US/project/code-of-conduct/ > List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines > List Archives: > https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org > Do not reply to spam, report it: > https://pagure.io/fedora-infrastructure/new_issue > -- ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: Picking up protobuf
On 18.04.2024 12:42, Michel Lind wrote: Hi Neil, On 4/18/24 06:37, Neil Hanlon wrote: thanks Michel! I'd be happy to help maintain if you would like assistance. There are 3 previous maintainers, plus the EPEL bugzilla is overridden to Peter Lemenkov (cc:ed) who is not in the ACL yet. So I'd rather take things slow and not make unilateral ACL changes. Any PR welcome though! (And I'll try and sort out existing issues and PRs in between conference prep). 100% agree. I'll keep an eye on the progress and feel free to ping if you need a hand with anything. --Neil Best regards, -- _o) Michel Lind _( ) identities: https://keyoxide.org/5dce2e7e9c3b1cffd335c1d78b229d2f7ccc04f2 signature.asc Description: PGP signature -- ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: F40 Change: Privacy-preserving Telemetry for Fedora Workstation (System-Wide)
Privacy is not too much of my concern. How much data is to be expected to be sent over my dataplan on monthly basis? When using Fedora Workstations as a graphics workstation (including regular office applications) during office hours and extensive internet research and entertainment during (late)evenings and weekends, should I expect this to generate data of some 10's of KB, or should I expect it to amount to megabytes? Will this be uploaded on scheduled daily interval or more regularly? Can I monitor the traffic on my firewall (and how)? Good luck with the upcoming release soon! Cheers, Igor -- ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: Picking up protobuf
Hi Neil, On 4/18/24 06:37, Neil Hanlon wrote: thanks Michel! I'd be happy to help maintain if you would like assistance. There are 3 previous maintainers, plus the EPEL bugzilla is overridden to Peter Lemenkov (cc:ed) who is not in the ACL yet. So I'd rather take things slow and not make unilateral ACL changes. Any PR welcome though! (And I'll try and sort out existing issues and PRs in between conference prep). Best regards, -- _o) Michel Lind _( ) identities: https://keyoxide.org/5dce2e7e9c3b1cffd335c1d78b229d2f7ccc04f2 OpenPGP_0x8B229D2F7CCC04F2.asc Description: OpenPGP public key OpenPGP_signature.asc Description: OpenPGP digital signature -- ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: Picking up protobuf
Hi Sérgio, On 4/18/24 06:44, Sérgio Basto wrote: On Wed, 2024-04-17 at 21:51 -0500, Michel Lind wrote: Hi all, protobuf was recently orphaned without any announcement to this list. I've picked it up since et depends on it. Update protobuf is a huge task see https://src.fedoraproject.org/rpms/protobuf/pull-request/26 ( move from protobuf-3.19.6 to 3.25.1 ) I think we should try enforce the update on rawhide , and just after look to protobuf-3.26. Agreed - we definitely should only do major upgrades on Rawhide. Best, -- _o) Michel Lind _( ) identities: https://keyoxide.org/5dce2e7e9c3b1cffd335c1d78b229d2f7ccc04f2 OpenPGP_0x8B229D2F7CCC04F2.asc Description: OpenPGP public key OpenPGP_signature.asc Description: OpenPGP digital signature -- ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: F41 Change Proposal: Replace Redis with Valkey (system-wide)
Nathan Scott wrote: > - it could be advantageous if the new compat sub-package contained > the redis binary symlinks & not the primary valkey package (this could > allow valkey and redict packages to coexist, for example). Long-term > we may want to drop those entirely (along with the compat package, to > complete the transition away from Redis). I do not see why we need a separate compat subpackage at all. Valkey should just Obsolete/Provide redis and include all the compat symlinks in the main package. Kevin Kofler -- ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Fedora 40 compose report: 20240418.n.0 changes
OLD: Fedora-40-20240417.n.0 NEW: Fedora-40-20240418.n.0 = SUMMARY = Added images:1 Dropped images: 3 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 packages: 0 B Size of downgraded packages: 0 B Size change of upgraded packages: 0 B Size change of downgraded packages: 0 B = ADDED IMAGES = Image: Sericea ociarchive x86_64 Path: Sericea/x86_64/images/Fedora-Sericea-40.20240418.n.0.ociarchive = DROPPED IMAGES = Image: i3 live aarch64 Path: Spins/aarch64/iso/Fedora-i3-Live-aarch64-40-20240417.n.0.iso Image: Server_KVM qcow2 ppc64le Path: Server/ppc64le/images/Fedora-Server-KVM-40-20240417.n.0.ppc64le.qcow2 Image: Workstation live aarch64 Path: Workstation/aarch64/iso/Fedora-Workstation-Live-aarch64-40-20240417.n.0.iso = ADDED PACKAGES = = DROPPED PACKAGES = = UPGRADED PACKAGES = = DOWNGRADED PACKAGES = -- ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: Three steps we could take to make supply chain attacks a bit harder
Kilian Hanich via devel wrote: > The fact that you can share the keys is actually part of the design and > wanted. Apple for exmaple has (or wants to) implement easy sharing of > passkeys via AirDrop. So the Apple Cloud can see your private key, but you cannot? Sounds like GREAT "security", LOL… Kevin Kofler -- ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
[Fedocal] Reminder meeting : ELN SIG
Dear all, You are kindly invited to the meeting: ELN SIG on 2024-04-19 from 12:00:00 to 13:00:00 US/Eastern At fedora-meet...@irc.libera.chat The meeting will be about: Source: https://calendar.fedoraproject.org//meeting/10568/ -- ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: Picking up protobuf
On Wed, 2024-04-17 at 21:51 -0500, Michel Lind wrote: > Hi all, > > protobuf was recently orphaned without any announcement to this list. > > I've picked it up since et depends on it. > Update protobuf is a huge task see https://src.fedoraproject.org/rpms/protobuf/pull-request/26 ( move from protobuf-3.19.6 to 3.25.1 ) I think we should try enforce the update on rawhide , and just after look to protobuf-3.26. Best regards, -- Sérgio M. B. -- ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: Picking up protobuf
thanks Michel! I'd be happy to help maintain if you would like assistance. On Wed, Apr 17, 2024, 22:52 Michel Lind wrote: > Hi all, > > protobuf was recently orphaned without any announcement to this list. > > I've picked it up since et depends on it. > > Best regards, > > -- > _o) Michel Lind > _( ) identities: > https://keyoxide.org/5dce2e7e9c3b1cffd335c1d78b229d2f7ccc04f2 > -- > ___ > devel mailing list -- devel@lists.fedoraproject.org > To unsubscribe send an email to devel-le...@lists.fedoraproject.org > Fedora Code of Conduct: > https://docs.fedoraproject.org/en-US/project/code-of-conduct/ > List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines > List Archives: > https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org > Do not reply to spam, report it: > https://pagure.io/fedora-infrastructure/new_issue > -- ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: Creating venv with latest python3.10 requires expat >= 2.6.0
On 18. 04. 24 1:00, Miro Hrončok wrote: On 18. 04. 24 0:37, Miro Hrončok wrote: On 17. 04. 24 23:10, Markus Falb wrote: I wonder if there is a way to reflect that in the spec file something like: ...snip Requires: expat >= 2.6.0 snap... Yes, we need to do that. I'm on it. https://src.fedoraproject.org/rpms/python3.13/pull-request/54 -- other Pythons will follow after CI + review. Here is the Fedora 38 python3.10 update: https://bodhi.fedoraproject.org/updates/FEDORA-2024-7736b7ce48 Other updates are available as well: https://bodhi.fedoraproject.org/updates/?packages=python3.8,python3.9,python3.10,python3.11,python3.12,python3.13 -- Miro Hrončok -- Phone: +420777974800 IRC: mhroncok -- ___ python-devel mailing list -- python-devel@lists.fedoraproject.org To unsubscribe send an email to python-devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/python-devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: Redis will no longer be OSS... now what?
On Thu, Apr 18, 2024 at 1:05 AM Leon Fauster via devel wrote: > > > > Thanks for the work on it. I wonder why valkey conflicts with redis, > > redict for instance does not!? Is this a decision for a preferred > > upgrade path? What about leaving this decision to the user (keydb, > > redict, valkey, redis on RHEL, etc) and allowing parallel installation > > for testing, decision making processes and migration. > > > > > > It is due to redict renaming some libs, while valkey has opted to retain > > "redis" on some lib file names. # rpm -ql redis | grep lib | grep -v build-id /usr/lib/systemd/system/redis-sentinel.service /usr/lib/systemd/system/redis.service /usr/lib64/redis /usr/lib64/redis/modules /var/lib/redis There aren't any lib files in either valkey or redis, and none of the directories listed above are in conflict between the two packages. I notice also a Conflict between valkey-devel and redis-devel has been added, and as much as I appreciate the sentiment (we're all disappointed with what has happened), I can't see justification for that either. > It seems to be just links in the bin directory that overlaps (and not > libs). Why not putting these links into the compat subpackage including > also the conflict statement. That would allow to install the main > package side-by-side to the other key-value-db forks. +1 https://src.fedoraproject.org/rpms/valkey/pull-request/2 cheers. -- Nathan -- ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
[Bug 2261445] perl-Authen-Krb5-Admin: FTBFS in Fedora rawhide/f40: perl(Authen::Krb5) build depenency does not exist
https://bugzilla.redhat.com/show_bug.cgi?id=2261445 Petr Pisar changed: What|Removed |Added Summary|perl-Authen-Krb5-Admin: |perl-Authen-Krb5-Admin: |FTBFS in Fedora rawhide/f40 |FTBFS in Fedora ||rawhide/f40: ||perl(Authen::Krb5) build ||depenency does not exist CC||ppi...@redhat.com Doc Type|--- |If docs needed, set a value --- Comment #4 from Petr Pisar --- The problem is that perl-Authen-Krb5 was removed from Fedora. -- You are receiving this mail because: You are on the CC list for the bug. https://bugzilla.redhat.com/show_bug.cgi?id=2261445 Report this comment as SPAM: https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla=report-spam_desc=Report%20of%20Bug%202261445%23c4 -- ___ perl-devel mailing list -- perl-devel@lists.fedoraproject.org To unsubscribe send an email to perl-devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/perl-devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
