[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 l

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 %autore

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 unsubscribe

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 branches

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, p

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 p

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 k

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 %autochang