Bug 1290082 - trojita-0.5-6 failed in epel7
Summary: trojita-0.5-6 failed in epel7
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora EPEL
Classification: Fedora
Component: trojita
Version: epel7
Hardware: Unspecified
OS: Linux
medium
high
Target Milestone: ---
Assignee: Raphael Groner
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks: epel7ppc64le epel7aarch64
TreeView+ depends on / blocked
 
Reported: 2015-12-09 16:07 UTC by Menanteau Guy
Modified: 2015-12-12 19:23 UTC (History)
3 users (show)

Fixed In Version: trojita-0.5-8.el7
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-12-12 19:23:05 UTC
Type: Bug
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 1266712 0 high CLOSED trojita: FTBFS in rawhide 2021-02-22 00:41:40 UTC

Internal Links: 1266712

Description Menanteau Guy 2015-12-09 16:07:28 UTC 
I got same problem as https://bugzilla.redhat.com/show_bug.cgi?id=1266712 when I build trojita-0.5-6 in epel7 ppc64le.
I guess package trojita-0.5-8 needs to be pushed in epel7.
Comment 1 Yaakov Selkowitz 2015-12-09 16:11:52 UTC 
Not arch specific; cause is epel7 qt5-* rebase to 5.5.
Comment 2 Fedora Update System 2015-12-09 20:16:43 UTC 
trojita-0.5-8.el7 has been submitted as an update to Fedora EPEL 7. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2015-3eee2c5463
Comment 3 Fedora Update System 2015-12-10 11:21:38 UTC 
trojita-0.5-8.el7 has been pushed to the Fedora EPEL 7 testing repository. If problems still persist, please make note of it in this bug report.
If you want to test the update, you can install it with
$ su -c 'yum --enablerepo=epel-testing update trojita'
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2015-3eee2c5463
Comment 4 Fedora Update System 2015-12-12 19:23:02 UTC 
trojita-0.5-8.el7 has been pushed to the Fedora EPEL 7 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.