Bug 1784684 - Please add qbittorrent-nox to epel8
Summary: Please add qbittorrent-nox to epel8
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora EPEL
Classification: Fedora
Component: qbittorrent
Version: epel8
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Charalampos Stratakis
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-12-18 05:03 UTC by Pascal
Modified: 2020-06-11 19:08 UTC (History)
2 users (show)

Fixed In Version: qbittorrent-4.2.5-2.el8
Clone Of:
Environment:
Last Closed: 2020-06-11 18:36:09 UTC
Type: Bug
Embargoed:

Attachments (Terms of Use)

Description Pascal 2019-12-18 05:03:42 UTC 
Please add qbittorrent-nox to epel8.  Thank you.

https://github.com/qbittorrent/qBittorrent/releases
Comment 1 Pascal 2019-12-18 05:08:54 UTC 
The nox package is intended for headless machines and does not require the X libraries.
Comment 2 Charalampos Stratakis 2020-05-13 18:27:52 UTC 
I'll investigate on adding the package to EPEL8
Comment 3 Fedora Update System 2020-05-25 18:15:27 UTC 
FEDORA-EPEL-2020-c43f1768ca has been submitted as an update to Fedora EPEL 8. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2020-c43f1768ca
Comment 4 Fedora Update System 2020-05-26 05:09:41 UTC 
FEDORA-EPEL-2020-c43f1768ca 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-2020-c43f1768ca

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
Comment 5 Fedora Update System 2020-06-11 18:36:09 UTC 
qbittorrent-4.2.5-2.el8 has been pushed to the Fedora EPEL 8 stable repository. If problems still persist, please make note of it in this bug report.
Comment 6 Pascal 2020-06-11 19:08:54 UTC 
Error:
 Problem: conflicting requests
  - nothing provides libQt5Core.so.5(Qt_5.12)(64bit) needed by qbittorrent-nox-1:4.2.5-2.el8.x86_64
Note You need to log in before you can comment on or make changes to this bug.