Bug 2214062 - Please branch and build mactel-boot in epel9
Summary: Please branch and build mactel-boot in epel9
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: mactel-boot
Version: 39
Hardware: Unspecified
OS: Linux
unspecified
unspecified
Target Milestone: ---
Assignee: Orphan Owner
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2023-06-11 15:03 UTC by Neil Hanlon
Modified: 2024-11-27 21:13 UTC (History)
3 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2024-11-27 21:13:09 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Neil Hanlon 2023-06-11 15:03:02 UTC
Please branch and build mactel-boot in epel9.

If you do not wish to maintain mactel-boot in epel9,
or do not think you will be able to do this in a timely manner,
I would be happy to be a co-maintainer of the package (FAS neil);
please add me through https://src.fedoraproject.org/rpms/mactel-boot/adduser

Reproducible:

Comment 1 Stephen John Smoogen 2023-06-14 18:28:44 UTC
I would say it is time to ask the EPEL committee to get this branched or see if Matthew still maintains or uses this. The upstream source http://www.codon.org.uk/~mjg59/mactel-boot/ in the package is no longer existent nor is it at https://github.com/mjg59?tab=repositories

Comment 2 Troy Dawson 2023-06-14 19:39:09 UTC
I'm confused.
It's only been three days since the submission.  The guidelines clearly say to wait a week, ask again, wait another week, then follow the procedure.  Why should the committee get involved?

And if there is no upstream source and the package has been at version 0.9 for 11 years means I don't want it in epel, not that we should rush it in.

Comment 3 Troy Dawson 2023-06-14 22:40:44 UTC
Things have been clarified outside of this ticket.
The real question wasn't about speeding up the process, but rather should it happen at all.
We have found where the current repo is with the code, so it probrubly will happen.

Comment 4 Fedora Release Engineering 2023-08-16 07:14:45 UTC
This bug appears to have been reported against 'rawhide' during the Fedora Linux 39 development cycle.
Changing version to 39.

Comment 5 Neil Hanlon 2023-10-21 22:37:04 UTC
source is now available at https://github.com/detly/mactel-boot

Comment 6 Aoife Moloney 2024-11-08 10:53:31 UTC
This message is a reminder that Fedora Linux 39 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora Linux 39 on 2024-11-26.
It is Fedora's policy to close all bug reports from releases that are no longer
maintained. At that time this bug will be closed as EOL if it remains open with a
'version' of '39'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, change the 'version' 
to a later Fedora Linux version. Note that the version field may be hidden.
Click the "Show advanced fields" button if you do not see it.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora Linux 39 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora Linux, you are encouraged to change the 'version' to a later version
prior to this bug being closed.

Comment 7 Fedora Admin user for bugzilla script actions 2024-11-24 02:08:10 UTC
This package has changed maintainer in Fedora. Reassigning to the new maintainer of this component.

Comment 8 Aoife Moloney 2024-11-27 21:13:09 UTC
Fedora Linux 39 entered end-of-life (EOL) status on 2024-11-26.

Fedora Linux 39 is no longer maintained, which means that it
will not receive any further security or bug fix updates. As a result we
are closing this bug.

If you can reproduce this bug against a currently maintained version of Fedora Linux
please feel free to reopen this bug against that version. Note that the version
field may be hidden. Click the "Show advanced fields" button if you do not see
the version field.

If you are unable to reopen this bug, please file a new report against an
active release.

Thank you for reporting this bug and we are sorry it could not be fixed.


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