Control: block -1 by 969301 > This probably needs fixing upstream regardless, but if MuPDF can > be built with OpenSSL 3 when it's ready that'd also be suitable > to close this bug. Per the FTP team's decision today, it seems MuPDF won't need to wait for Apache-licensed OpenSSL to build with it. It still stands that the incorrect exit status should be fixed for non-OpenSSL builds however.
signature.asc
Description: This is a digitally signed message part.
