| Summary: | [Update Request] hylafax 5.5.1 -> 7.0.2 | ||
|---|---|---|---|
| Product: | [ROSA-based products] ROSA Fresh | Reporter: | Zombie Ryushu <zombie.ryushu> |
| Component: | Packages from Main | Assignee: | ROSA Linux Bugs <bugs> |
| Status: | VERIFIED FIXED | QA Contact: | ROSA Linux Bugs <bugs> |
| Severity: | normal | ||
| Priority: | Normal | CC: | alzim, andrey.bondrov, denis.silakov, m.novosyolov, mc2374, v.potapov |
| Version: | All | Flags: | v.potapov:
qa_verified+
andrey.bondrov: published+ |
| Target Milestone: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| URL: | https://advisories.mageia.org/MGAA-2020-0066.html | ||
| Whiteboard: | |||
| Platform: | --- | ROSA Vulnerability identifier: | |
| RPM Package: | hylafax-5.5.1-5.src.rpm | ISO-related: | |
| Bad POT generating: | Upstream: | ||
|
Description
Zombie Ryushu
2020-03-26 17:32:17 MSK
The issue don't apply to our actual package: it is still on the sysvinit era... However it is also 8 years old (!): let's bring it top the latest 7.0.2 release. Advisory: Update hylafax to release 7.0.2 and switch to systemd by borrowing Mageia files. The same change was pushed in the 2019.1 branch. Packages for Rosa 2016.1 / Main: https://abf.rosalinux.ru/build_lists/3272494 https://abf.rosalinux.ru/build_lists/3272495 The update is sent to expanded testing **************************************** Hm, what for do you use hylafax if it is not a secret? (In reply to Mikhail Novosyolov from comment #4) > Hm, what for do you use hylafax if it is not a secret? You should ask to Zombie... I don't use it at all: do you think we should simply kill the package? A few institutions I do businesss with, require documentation to be faxed to them. To accommodate this, I use a Fax Modem connected to a USB Serial adapter to send Faxes. -Or at least I used too.- My Current Asterisk setup will see me move to an entirely SIP based infrastructure. I'nm hoping Hylafax will work over Asterisk SIP. hylafax-7.0.2-1 https://abf.rosalinux.ru/build_lists/3272494 https://abf.rosalinux.ru/build_lists/3272495 ***************************** Advisory ********************* Update hylafax to release 7.0.2 and switch to systemd by borrowing Mageia files. ************************************************************ QA Verified (In reply to Giovanni Mariani from comment #5) > (In reply to Mikhail Novosyolov from comment #4) > > Hm, what for do you use hylafax if it is not a secret? > You should ask to Zombie... > I don't use it at all: do you think we should simply kill the package? I want to move hylafax from main to contrib, because: 1) it serves for a very specific usecase nowadays 2) I am pretty sure that QA does not use fax and cannot test it properly Any objections? (In reply to Mikhail Novosyolov from comment #8) > I want to move hylafax from main to contrib, because: > 1) it serves for a very specific usecase nowadays > 2) I am pretty sure that QA does not use fax and cannot test it properly > Any objections? I agree. The nature of how Hylafax was used versus how it is used now has changed and tied into my current Asterisk Project. In the past I used a USB to Serial adapter in conjunction with an External Fax Modem, to send Analogue Faxes to a few organizations that required it. at the time, I'd used an ADSL connection to do this with a DSL filter. That all changed recently, and now there are no more Analogue POTS lines going to my house. Only High Speed Internet. To address the issue, I'm implementing Asterisk to address that issue. Once I get Asterisk functional, I plan to contract with a SIP Trunk Provider to provide Phone, Fax and SMS Service. That is if I can get Asterisk working to my satisfaction. Asterisk needs to be moved from contrib to main. It's becoming more important as Phone companies and Cable Companies are increasingly pushing their user base to VOIP solutions. Hylafax seems to ship with a broken configuration. |