Bug 2027795 - Please branch autokey for an epel8
Summary: Please branch autokey for an epel8
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: autokey
Version: 36
Hardware: All
OS: Linux
unspecified
low
Target Milestone: ---
Assignee: Jonathan Wright
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-11-30 17:00 UTC by Jonathan Billings
Modified: 2023-05-08 01:23 UTC (History)
2 users (show)

Fixed In Version: autokey-0.96.0-1.el9 autokey-0.96.0-1.el8
Clone Of:
Environment:
Last Closed: 2023-05-08 01:13:12 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Jonathan Billings 2021-11-30 17:00:36 UTC
Please create an EPEL8 build for the autokey package.  I built it against the EPEL8 build tree and it builds and runs without any issue.  We use it internally and would like to be able to provide it on RHEL8 workstations.

Comment 1 Ben Cotton 2022-02-08 21:24:20 UTC
This bug appears to have been reported against 'rawhide' during the Fedora 36 development cycle.
Changing version to 36.

Comment 2 Ben Cotton 2023-04-25 16:46:25 UTC
This message is a reminder that Fedora Linux 36 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora Linux 36 on 2023-05-16.
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 '36'.

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 36 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 3 Fedora Admin user for bugzilla script actions 2023-04-26 00:05:27 UTC
This package has changed maintainer in Fedora. Reassigning to the new maintainer of this component.

Comment 4 Fedora Admin user for bugzilla script actions 2023-04-28 12:10:51 UTC
This package has changed maintainer in Fedora. Reassigning to the new maintainer of this component.

Comment 5 Fedora Update System 2023-04-29 09:51:06 UTC
FEDORA-EPEL-2023-ebe9020149 has been submitted as an update to Fedora EPEL 8. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2023-ebe9020149

Comment 6 Fedora Update System 2023-04-29 09:51:06 UTC
FEDORA-EPEL-2023-6891fcf5b8 has been submitted as an update to Fedora EPEL 9. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2023-6891fcf5b8

Comment 7 Fedora Update System 2023-04-30 02:50:02 UTC
FEDORA-EPEL-2023-ebe9020149 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-2023-ebe9020149

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

Comment 8 Fedora Update System 2023-04-30 02:53:20 UTC
FEDORA-EPEL-2023-6891fcf5b8 has been pushed to the Fedora EPEL 9 testing repository.

You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2023-6891fcf5b8

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

Comment 9 Fedora Update System 2023-05-08 01:13:12 UTC
FEDORA-EPEL-2023-6891fcf5b8 has been pushed to the Fedora EPEL 9 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 10 Fedora Update System 2023-05-08 01:23:28 UTC
FEDORA-EPEL-2023-ebe9020149 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.