Bug 2277375 - Please branch and build perl-Fuse for EPEL8
Summary: Please branch and build perl-Fuse for EPEL8
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora EPEL
Classification: Fedora
Component: perl-Fuse
Version: epel8
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: ---
Assignee: Jitka Plesnikova
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2024-04-26 15:04 UTC by Orion Poplawski
Modified: 2024-06-01 00:32 UTC (History)
2 users (show)

Fixed In Version: perl-Fuse-0.16.1-27.el8
Clone Of:
Environment:
Last Closed: 2024-06-01 00:32:26 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Orion Poplawski 2024-04-26 15:04:03 UTC
Please branch and build perl-Fuse in epel8.

If you do not wish to maintain perl-Fuse in epel8,
or do not think you will be able to do this in a timely manner,
the EPEL Packagers SIG would be happy to be a co-maintainer of the package;
please add the epel-packagers-sig group through
https://src.fedoraproject.org/rpms/perl-Fuse/addgroup
and grant it commit access, or collaborator access on epel* branches.

I would also be happy to be a co-maintainer (FAS: orion).

I can be the primary contact for EPEL (FAS: orion).

Comment 1 Fedora Update System 2024-05-23 12:58:54 UTC
FEDORA-EPEL-2024-f1ed091149 (perl-Fuse-0.16.1-27.el8) has been submitted as an update to Fedora EPEL 8.
https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2024-f1ed091149

Comment 2 Fedora Update System 2024-05-24 00:31:44 UTC
FEDORA-EPEL-2024-f1ed091149 has been pushed to the Fedora EPEL 8 testing repository.

You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2024-f1ed091149

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Comment 3 Fedora Update System 2024-06-01 00:32:26 UTC
FEDORA-EPEL-2024-f1ed091149 (perl-Fuse-0.16.1-27.el8) has been pushed to the Fedora EPEL 8 stable repository.
If problem still persists, please make note of it in this bug report.


Note You need to log in before you can comment on or make changes to this bug.