On 2026/02/09 03:04, Theo Buehler wrote: > On Sun, Feb 08, 2026 at 07:29:22PM -0500, 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 <[email protected]> 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. > > So you did and you're right. I stopped looking here: > https://www.hylafax.org/downloads/
The only update to Hylafax doesn't change anything with respect to what the BROKEN message says (and the latest versions of the fork Hylafax+ still use tiff2ps/tiff2pdf), however, it seems libtiff includes these again now following https://gitlab.com/libtiff/libtiff/-/merge_requests/589
