@vorlon, while it may not be an *error* on infrastructure side, the infrastructure team *can* provide solution i.e., by changing the link address of zsync files from 'https' to 'http'.
If we check the linked debian bug report, they are not interested in implementing 'https' feature in zsync for 'overload' concerns. If infrastructure team passes the issue to package, it will be open forever.
@vorlon, while it may not be an *error* on infrastructure side, the infrastructure team *can* provide solution i.e., by changing the link address of zsync files from 'https' to 'http'.
If we check the linked debian bug report, they are not interested in implementing 'https' feature in zsync for 'overload' concerns. If infrastructure team passes the issue to package, it will be open forever.