Bug 2144649
Summary: | Please branch and build hylafax+ in epel9 | ||
---|---|---|---|
Product: | [Fedora] Fedora EPEL | Reporter: | Nicolas Ross <nicolas> |
Component: | hylafax+ | Assignee: | Lee Howard <faxguy> |
Status: | NEW --- | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | medium | Docs Contact: | |
Priority: | unspecified | ||
Version: | epel9 | CC: | faxguy |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | x86_64 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | If docs needed, set a value | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | Type: | Bug | |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Nicolas Ross
2022-11-21 22:47:53 UTC
Should be relatively easy. I was able to build it on an EL9 machine from hylafax+-7.0.6-1.fc37.src.rpm using cu, mgetty and uucp rpms from fc37. I think that the problem with EPEL9 will be the same as was with EPEL8... that is that mgetty and uucp are no longer available. Getting HylaFAX to build without mgetty is not a problem. Getting HylaFAX to build without uucp will require a bit of effort... it's much easier to just do as you've done: rebuild and install mgetty and uucp and then rebuild HylaFAX+. Still... I'm not sure the right way to "branch and build hylafax+ in epel9" even if uucp weren't an issue. Do you have a URL to share that describes how to do that? I do not have a URL, but here's what I did on my EL9 vm : Installed mgetty-1.2.1-16.fc37.x86_64.rpm uucp-1.07-66.fc37.x86_64.rpm cu-1.07-66.fc37.x86_64.rpm from FC37 And then build hylafax+-7.0.6-1.fc37.src.rpm I took from FC37 after installing the proper devel packages. I suppose then we need to request mgetty, uucp and cu in EL9 ? |