Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.
Bug 1840420 - Please build linphone for EPEL 8
Summary: Please build linphone for EPEL 8
Keywords:
Status: NEW
Alias: None
Product: Fedora
Classification: Fedora
Component: linphone
Version: 33
Hardware: All
OS: Linux
unspecified
medium
Target Milestone: ---
Assignee: nucleo
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On: 1840412 1840413 1840416 1840415
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-05-26 22:13 UTC by Robert Scheck
Modified: 2020-08-11 15:28 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed:
Type: Bug
Embargoed:

Attachments (Terms of Use)

Description Robert Scheck 2020-05-26 22:13:21 UTC 
Description of problem:
Please build linphone for EPEL 8.

Version-Release number of selected component (if applicable):
linphone-3.6.1-38.fc32

Actual results:
No linphone in EPEL 8.

Expected results:
linphone-3.6.1-38.el8 - or better ;-)

Additional info:
Please let me know if you are not interested in maintaining the package on EPEL 8 branch.
Comment 1 Stuart D Gathman 2020-05-27 18:03:01 UTC 
Someone built 4.0.x on COPR - I was thinking to start with that since we have essentially a blank slate (upgrading ortp on Fedora broke other things horribly).  Then, when that is working, we have a workable target for Fedora.
Comment 2 Robert Scheck 2020-05-27 21:04:23 UTC 
Okay, then let me please know if you need package reviews for Fedora when trying to get a more recent version in.
Comment 3 Ben Cotton 2020-08-11 15:28:04 UTC 
This bug appears to have been reported against 'rawhide' during the Fedora 33 development cycle.
Changing version to 33.
Note You need to log in before you can comment on or make changes to this bug.