[Bug 2280644] Upgrade perl-Email-MIME to 1.954

https://bugzilla.redhat.com/show_bug.cgi?id=2280644 Fedora Update System changed: What|Removed |Added Fixed In Version|perl-Email-MIME-1.954-1.fc4 |perl-Email-MIME-1.954-1.fc4

[Bug 2280644] Upgrade perl-Email-MIME to 1.954

https://bugzilla.redhat.com/show_bug.cgi?id=2280644 Fedora Update System changed: What|Removed |Added Fixed In Version|perl-Email-MIME-1.954-1.fc4 |perl-Email-MIME-1.954-1.fc4

[Bug 2280644] Upgrade perl-Email-MIME to 1.954

https://bugzilla.redhat.com/show_bug.cgi?id=2280644 Fedora Update System changed: What|Removed |Added Fixed In Version|perl-Email-MIME-1.954-1.fc4 |perl-Email-MIME-1.954-1.fc4

[Bug 2280644] Upgrade perl-Email-MIME to 1.954

https://bugzilla.redhat.com/show_bug.cgi?id=2280644 Fedora Update System changed: What|Removed |Added Fixed In Version|perl-Email-MIME-1.954-1.fc4 |perl-Email-MIME-1.954-1.fc4

[Bug 2283161] New: perl-MCE-1.890 is available

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

Re: Announcement: pagure release 5.14.1 available

> On 05/24/2024 5:03 PM CEST Sérgio Basto wrote: > > > On Fri, 2024-05-24 at 16:55 +0200, Dominik Wombacher wrote: > > [4] https://src.fedoraproject.org/rpms/pagure > > good news and thanks, I want to test in my local machine,  to do that I > need the package updated, please add some builds .

SPDX Statistics - Morse edition

Hot news:  SPDX released new license list https://github.com/spdx/license-list-XML/releases/tag/v3.24.0 with 25 new licenses. Lot of them are there because of Fedora maintainers. Thank you. Two weeks ago we had: * 23990spec files in Fedora * 30640license tags in all spec files * 10589

Re: Announcement: pagure release 5.14.1 available

On Fri, 2024-05-24 at 16:55 +0200, Dominik Wombacher wrote: > [4] https://src.fedoraproject.org/rpms/pagure good news and thanks, I want to test in my local machine,  to do that I need the package updated, please add some builds . Best regards, -- Sérgio M. B. --

Announcement: pagure release 5.14.1 available

Hi everyone, it's been a while and because of increasing requests and important security fixes we release pagure version 5.14.1 today! The release is build based on version 5.13.3 with 59 backports: - 13 features, 34 fixes, 4 security fixes and 8 improvements of the documentation. Checkout

Re: Intention to unretire and rename pyftpdlib

On Fri, May 24, 2024 at 2:48 PM Kevin Kofler via devel wrote: > > Sandro wrote: > > I was probably overthinking this. In practice it will turn out to be a > > new package submission indeed. Moreover, the last remaining active > > branch of the retired package (F38) is now EOL. > > > > I've

Re: Intention to unretire and rename pyftpdlib

Sandro wrote: > I was probably overthinking this. In practice it will turn out to be a > new package submission indeed. Moreover, the last remaining active > branch of the retired package (F38) is now EOL. > > I've submitted the review [1] without any Obsoletes. Since we support upgrades from

Re: Changing desktop file name in a stable release

Julian Sikorski wrote: > are there guidelines advising how to handle upstream desktop filename > change in a stable fedora release? For gnumeric I just followed upstream > [1], which led to a bug report [2]. Now I am facing similar situation > with pavucontrol [3]. Should I rename the desktop file

Re: small logic issue with system upgrades

Am 24.05.24 um 12:01 schrieb Roberto Ragusa: On 5/22/24 16:33, Marius Schwarz wrote: So, atm, the server has a sshd that says, that openssl is newer as the required openssl version. It does not start it nor can the running sshd, that runs the upgrade connection, fork a new instance. In other

Changing desktop file name in a stable release

Hi list, are there guidelines advising how to handle upstream desktop filename change in a stable fedora release? For gnumeric I just followed upstream [1], which led to a bug report [2]. Now I am facing similar situation with pavucontrol [3]. Should I rename the desktop file to what it used

Fedora rawhide compose report: 20240524.n.0 changes

OLD: Fedora-Rawhide-20240523.n.0 NEW: Fedora-Rawhide-20240524.n.0 = SUMMARY = Added images:1 Dropped images: 0 Added packages: 3 Dropped packages:0 Upgraded packages: 82 Downgraded packages: 0 Size of added packages: 16.33 MiB Size of dropped packages:0 B

Re: small logic issue with system upgrades

On 5/22/24 16:33, Marius Schwarz wrote: So, atm, the server has a sshd that says, that openssl is newer as the required openssl version. It does not start it nor can the running sshd, that runs the upgrade connection, fork a new instance. In other words: no login possible to rescue or

[Bug 2283021] perl-Business-ISBN-Data-20240523.001 is available

https://bugzilla.redhat.com/show_bug.cgi?id=2283021 Fedora Update System changed: What|Removed |Added Fixed In Version||perl-Business-ISBN-Data-202

[Bug 2283021] perl-Business-ISBN-Data-20240523.001 is available

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

Re: Personal introduction // Interested in adopting orphans

On 24-05-2024 07:11, Paul Pfeister via devel wrote: Last Thursday, an inactive packagers list was sent out on devel with a list of now-orphaned packages. Among these are python-git-changelog and

Re: Intention to retire mlocate

Christopher wrote on Fri, May 24, 2024 at 02:15:17AM -0400: > A flag to treat the arguments as OR like mlocate did instead of the default > to AND would be great, though I wish plocate would have more closely > mimicked mlocate's default behavior from the beginning and had a flag for > AND

Re: Intention to retire mlocate

Christopher wrote on Fri, May 24, 2024 at 02:18:04AM -0400: > Are you sure you have the correct address for the plocate developer and > that it's still actively maintained? I just got an error that the > destination email address didn't exist from their mail server when I > replied just now.

Re: Intention to retire mlocate

Are you sure you have the correct address for the plocate developer and that it's still actively maintained? I just got an error that the destination email address didn't exist from their mail server when I replied just now. On Fri, May 24, 2024, 02:15 Christopher wrote: > A flag to treat the

Re: Intention to retire mlocate

A flag to treat the arguments as OR like mlocate did instead of the default to AND would be great, though I wish plocate would have more closely mimicked mlocate's default behavior from the beginning and had a flag for AND instead. Unfortunately, one cannot go back in time. On Thu, May 23, 2024,