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

The following builds have been pushed to Fedora EPEL 7 updates-testing js-jquery-ui-1.13.3-1.el7 Details about builds: js-jquery-ui-1.13.3-1.el7 (FEDORA-EPEL-2024-b0928d02b4) jQuery user interface

[Bug 2275188] perl-Socket-2.038 is available

https://bugzilla.redhat.com/show_bug.cgi?id=2275188 Fedora Update System changed: What|Removed |Added Fixed In Version|perl-Socket-2.038-1.fc41|perl-Socket-2.038-1.fc41

[Bug 2277506] perl-IO-Compress-2.212 is available

https://bugzilla.redhat.com/show_bug.cgi?id=2277506 Fedora Update System changed: What|Removed |Added Resolution|--- |ERRATA

[Bug 2277638] perl-App-cpm-0.997017 is available

https://bugzilla.redhat.com/show_bug.cgi?id=2277638 Upstream Release Monitoring changed: What|Removed |Added Summary|perl-App-cpm-0.997016 is|perl-App-cpm-0.997017 is

[Test-Announce] 2024-04-29 @ 15:00 UTC - Fedora Quality Meeting

# Fedora Quality Assurance Meeting # Date: 2024-04-29 # Time: 15:00 UTC (https://fedoraproject.org/wiki/Infrastructure/UTCHowto) # Location: https://matrix.to/#/#meeting:fedoraproject.org?web-instance[element.io]=chat.fedoraproject.org Greetings testers! It's meeting time again. Here is a handy

Re: how to do minor bump using %autorelease?

Julian Sikorski wrote: > I need to rebuild mame on F40 only for qt-6.7. On rawhide, > mame-0.265-1.fc41 is already built against it so I only need to build > mame-0.265-1.fc40.1. Can it be done using %autorelease? No, which is why you should not be using %autorelease. I would just replace

Re: systemd 256~rc1 in rawhide

Adam Williamson wrote: > Well, it really wants to write to /lib , not to /usr. But of course, on > Fedora, /lib is /usr/lib . Sigh… Time for a UsrUnmerge? :-) Kevin Kofler -- ___ devel mailing list -- devel@lists.fedoraproject.org To

Re: Is there a policy for branches being merged or not

Julian Sikorski wrote: > In this case defaulting to cherry-picking would be a safer bet. Branches > unintentionally separated can be merged, but branches unintentionally > merged cannot be unmerged. This is only true if you are talking about merge-commit merges. Not if we are keeping the

[Bug 2277506] perl-IO-Compress-2.212 is available

https://bugzilla.redhat.com/show_bug.cgi?id=2277506 Fedora Update System changed: What|Removed |Added Status|NEW |MODIFIED --- Comment #1 from

[Bug 2277638] New: perl-App-cpm-0.997016 is available

https://bugzilla.redhat.com/show_bug.cgi?id=2277638 Bug ID: 2277638 Summary: perl-App-cpm-0.997016 is available Product: Fedora Version: rawhide Status: NEW Component: perl-App-cpm Keywords: FutureFeature, Triaged

F41 Change Proposal: Node.js 22.x by default (system-wide)

Wiki - https://fedoraproject.org/wiki/Changes/Nodejs22 Discussion thread - https://discussion.fedoraproject.org/t/f41-change-proposal-node-js-22-x-by-default-system-wide/114740 This is a proposed Change for Fedora Linux. This document represents a proposed Change. As part of the Changes process,

F41 Change Proposal: Node.js 22.x by default (system-wide)

Wiki - https://fedoraproject.org/wiki/Changes/Nodejs22 Discussion thread - https://discussion.fedoraproject.org/t/f41-change-proposal-node-js-22-x-by-default-system-wide/114740 This is a proposed Change for Fedora Linux. This document represents a proposed Change. As part of the Changes process,

F41 Change Proposal: Perl 5.40 (system-wide)

Wiki - https://fedoraproject.org/wiki/Changes/perl5.40 Discussion Thread - https://discussion.fedoraproject.org/t/f41-change-proposal-perl-5-38-system-wide/114739 This is a proposed Change for Fedora Linux. This document represents a proposed Change. As part of the Changes process, proposals are

F41 Change Proposal: Perl 5.40 (system-wide)

Wiki - https://fedoraproject.org/wiki/Changes/perl5.40 Discussion Thread - https://discussion.fedoraproject.org/t/f41-change-proposal-perl-5-38-system-wide/114739 This is a proposed Change for Fedora Linux. This document represents a proposed Change. As part of the Changes process, proposals are

[Bug 2277504] perl-Compress-Raw-Zlib-2.212 is available

https://bugzilla.redhat.com/show_bug.cgi?id=2277504 Fedora Update System changed: What|Removed |Added Fixed In Version||perl-Compress-Raw-Zlib-2.21

[Bug 2277505] perl-Compress-Raw-Bzip2-2.212 is available

https://bugzilla.redhat.com/show_bug.cgi?id=2277505 Fedora Update System changed: What|Removed |Added Resolution|--- |ERRATA

[Bug 2277612] New: perl-Test-Smoke-1.82 is available

https://bugzilla.redhat.com/show_bug.cgi?id=2277612 Bug ID: 2277612 Summary: perl-Test-Smoke-1.82 is available Product: Fedora Version: rawhide Status: NEW Component: perl-Test-Smoke Keywords: FutureFeature, Triaged

[Bug 2277607] New: perl-Module-Faker-0.026 is available

https://bugzilla.redhat.com/show_bug.cgi?id=2277607 Bug ID: 2277607 Summary: perl-Module-Faker-0.026 is available Product: Fedora Version: rawhide Status: NEW Component: perl-Module-Faker Keywords: FutureFeature, Triaged

[Bug 2277504] perl-Compress-Raw-Zlib-2.212 is available

https://bugzilla.redhat.com/show_bug.cgi?id=2277504 Fedora Update System changed: What|Removed |Added Status|NEW |MODIFIED --- Comment #1 from

[Bug 2277505] perl-Compress-Raw-Bzip2-2.212 is available

https://bugzilla.redhat.com/show_bug.cgi?id=2277505 Fedora Update System changed: What|Removed |Added Status|NEW |MODIFIED --- Comment #1 from

[Bug 2277524] perl-version-0.9932 is available

https://bugzilla.redhat.com/show_bug.cgi?id=2277524 Upstream Release Monitoring changed: What|Removed |Added Summary|perl-version-0.9931 is |perl-version-0.9932 is

[rpms/perl] PR #12: Update macros.perl

huakim opened a new pull-request against the project: `perl` that you are following: `` Update macros.perl `` To reply, visit the link below https://src.fedoraproject.org/rpms/perl/pull-request/12 -- ___ perl-devel mailing list --

Re: Is there a policy for branches being merged or not

Am 28.04.24 um 10:36 schrieb Peter Robinson: On Sun, 28 Apr 2024, 09:28 Julian Sikorski, > wrote: Hello, is there a general recommendation regarding keeping git release branches separate vs merged? I have been keeping mine separate. Originally to

Re: Is there a policy for branches being merged or not

On Sun, 28 Apr 2024, 09:28 Julian Sikorski, wrote: > Hello, > > is there a general recommendation regarding keeping git release branches > separate vs merged? I have been keeping mine separate. Originally to > avoid release and changelog conflicts when cherry-picking, but I got > used to it and

Is there a policy for branches being merged or not

Hello, is there a general recommendation regarding keeping git release branches separate vs merged? I have been keeping mine separate. Originally to avoid release and changelog conflicts when cherry-picking, but I got used to it and kept doing it after converting to %autorelase and