Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#73788 - [pv] Upstream URL does not support TLS 1.2
Attached to Project:
Community Packages
Opened by Thomas (uhthomas) - Monday, 14 February 2022, 18:35 GMT
Last edited by Caleb Maclennan (alerque) - Thursday, 07 April 2022, 17:15 GMT
Opened by Thomas (uhthomas) - Monday, 14 February 2022, 18:35 GMT
Last edited by Caleb Maclennan (alerque) - Thursday, 07 April 2022, 17:15 GMT
|
DetailsDescription:
The upstream URL [0] for the pv package does not support TLS 1.2. Modern web browsers refuse to load the site as it is considered insecure. [0]: https://www.ivarch.com/programs/pv.shtml |
This task depends upon
Closed by Caleb Maclennan (alerque)
Thursday, 07 April 2022, 17:15 GMT
Reason for closing: Upstream
Additional comments about closing: This isn't really something we can fix. I suggest opening an issue on the upstream author's bug reporter. I did switch our packaging source to be the GitHub hosted tarball (even though it doesn't matter since Arch users download the package from our repos anyway) but the website is just either http or badly secured https. Fixing that is upstream's problem.
Thursday, 07 April 2022, 17:15 GMT
Reason for closing: Upstream
Additional comments about closing: This isn't really something we can fix. I suggest opening an issue on the upstream author's bug reporter. I did switch our packaging source to be the GitHub hosted tarball (even though it doesn't matter since Arch users download the package from our repos anyway) but the website is just either http or badly secured https. Fixing that is upstream's problem.