On 9/02/2026 8:29 am, Stuart Cassoff wrote:
>
>
> On Sun, 8 Feb 2026, Stuart Henderson wrote:
>
>> i'm ok with removing both (and I have used hylafax before ;)
>>
>> --ￜ
>> ￜ Sent from a phone, apologies for poor formatting.
>>
>>
>> On 8 February 2026 20:29:44 Theo Buehler <tb@theobuehler.org> wrote:
>>
>> On Sun, Feb 08, 2026 at 02:41:36PM -0500, Stuart Cassoff wrote:
>> RDEP on BROKEN comms/hylafax.
>> Mark BROKEN as well; no point in building for nothing.
>>
>>
>> Pretty sure bulks don't build things with BROKEN dep, rdep included.
>>
>> In general, I think it would be better not to set the BROKEN marker here
>> since that's easy to miss if comms/hylafax is ever unbroken.
>>
>> However, that seems unlikely, so maybe it's time to take them both behind
>> the barn?
>>
>>
>
> Why is that unlikely?
> New versions are available and I will look into updating the port.
> I said as much in my message.
>
>
> Stu
I'll be keen to see HylaFAX become unbroken.
I currently have HylaFAX 6.0.7 running on OpenBSD 7.8. It successfully
transmits and receives faxes. However, there is an issue when querying
the faxq where the connection intermittently gets reset at initial
connection. This is observed when using faxstat on the host and also
when using WHFC across the network. I've not observed any issues when
submitting a fax.
HylaFAX+ may be an option too. I managed to build version 7 on OpenBSD
but encountered a problem when attempting to receive a fax with ECM
disabled.
Cheers,
Larry.
No comments:
Post a Comment