Bug 2283667

Summary: Request to build the "micro" package for RHEL 9 in EPEL.
Product: [Fedora] Fedora EPEL Reporter: angel.rp
Component: microAssignee: Robert-André Mauchin 🐧 <eclipseo>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: unspecified    
Version: epel9CC: eclipseo, go-sig
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2024-09-28 12:57:07 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description angel.rp 2024-05-28 17:16:13 UTC
Description:
I am requesting the inclusion of the "micro" package in the EPEL repository for RHEL 9. The "micro" package is a modern and user-friendly text editor that would be a valuable addition for RHEL 9 users.

Details:

    Package Name: micro

    Requested Version: (Specify the version if necessary, otherwise leave blank for the latest stable version)
    
    Reason for Request:
        The "micro" editor provides an intuitive interface and advanced features that are useful for both developers and system administrators.
        Currently, the package is not available in the EPEL repository for RHEL 9, which limits its accessibility for users of this RHEL version.

    Expected Benefits:
        Improved productivity for RHEL 9 users who need a lightweight yet powerful text editor.
        Expand the variety of tools available in EPEL for RHEL 9.

Attachments:
(Not applicable)

Steps to Reproduce:
(Not applicable)

Expected Behavior:
The "micro" package should be available for installation from the EPEL repository on RHEL 9.

Current Behavior:
The "micro" package is not available in the EPEL repository for RHEL 9.

Comment 1 Xavier Bachelot 2024-09-28 12:57:07 UTC

*** This bug has been marked as a duplicate of bug 2091338 ***