Date: Sun, 3 Sep 2017 09:43:38 -0700 From: Yuri <yuri@rawbw.com> Cc: ports@freebsd.org, Tobias Kortkamp <tobik@freebsd.org> Subject: Re: Some github projects aren't fetchable using commit hash Message-ID: <4e8ed3f7-fd7d-bd06-0cf6-dccac361dffa@rawbw.com> In-Reply-To: <CACNAnaHNav1iZ1KvutPxMBm=4hdRc13qY7Vir3UCexaZFYj2bA@mail.gmail.com> References: <aa643aff-e842-b50e-5ae5-06e6c084ed5b@rawbw.com> <1504284830.794543.1092454472.7353C7D3@webmail.messagingengine.com> <4e2b7041-6ee3-6994-437d-39de395ffca3@rawbw.com> <c37d806c-f9d8-d0cb-4a55-5af9a0c5ea3b@ShaneWare.Biz> <CACNAnaHNav1iZ1KvutPxMBm=4hdRc13qY7Vir3UCexaZFYj2bA@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 09/01/17 19:01, Kyle Evans wrote: > To be honest, the failing seems like a little better behavior than suddenly > swapping out the package I thought I was downloading with a newer version. > It'd at least be a little more obvious and theoretically detectable if they > respond properly. I suggested github to replace the error code with one of these: || |* 409 Conflict (https://httpstatuses.com/409) | |* 300 Multiple choices (https://httpstatuses.com/300): can provide a list of alternative URLs.| | | |Yuri |
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4e8ed3f7-fd7d-bd06-0cf6-dccac361dffa>