Bug 1762501 - Please build libaccounts-glib in normal EPEL8
Summary: Please build libaccounts-glib in normal EPEL8
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora EPEL
Classification: Fedora
Component: libaccounts-glib
Version: epel8
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Troy Dawson
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-10-16 20:56 UTC by Troy Dawson
Modified: 2019-12-07 02:10 UTC (History)
3 users (show)

Fixed In Version: libaccounts-glib-1.23-8.el8
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-12-07 02:10:29 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Troy Dawson 2019-10-16 20:56:11 UTC
Please build libaccounts-glib in EPEL8

Comment 1 Troy Dawson 2019-10-21 14:29:41 UTC
I already have this package built in epel8-playground
Would you mind if I built it and/or maintained it in regular epel8?

Comment 2 Troy Dawson 2019-11-20 15:34:17 UTC
I will build and maintain this packages.

Comment 3 Troy Dawson 2019-11-20 15:34:45 UTC
In EPEL8 I mean, not for all of Fedora.

Comment 4 Fedora Update System 2019-11-20 15:42:17 UTC
FEDORA-EPEL-2019-f971d51367 has been submitted as an update to Fedora EPEL 8. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2019-f971d51367

Comment 5 Fedora Update System 2019-11-21 02:42:58 UTC
libaccounts-glib-1.23-8.el8 has been pushed to the Fedora EPEL 8 testing repository. If problems still persist, please make note of it in this bug report.
See https://fedoraproject.org/wiki/QA:Updates_Testing for
instructions on how to install test updates.
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2019-f971d51367

Comment 6 Fedora Update System 2019-12-07 02:10:29 UTC
libaccounts-glib-1.23-8.el8 has been pushed to the Fedora EPEL 8 stable repository. If problems still persist, 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.