From mboxrd@z Thu Jan 1 00:00:00 1970 From: Leo Famulari Subject: bug#33261: [substitute-urls] Fails when given only "berlin.guixsd.org" Date: Mon, 5 Nov 2018 14:46:18 -0500 Message-ID: <20181105194618.GA18731@jasmine.lan> References: <7461b803-d8af-2e76-358e-35592f3ca995@riseup.net> <20181105191322.64a47ea0@alma-ubu> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="VbJkn9YxBvnuCH5J" Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:35458) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1gJkq2-0003ot-8G for bug-guix@gnu.org; Mon, 05 Nov 2018 14:47:07 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1gJkpy-0002rr-3S for bug-guix@gnu.org; Mon, 05 Nov 2018 14:47:06 -0500 Received: from debbugs.gnu.org ([208.118.235.43]:59620) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1gJkpx-0002rP-Qb for bug-guix@gnu.org; Mon, 05 Nov 2018 14:47:02 -0500 Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1gJkpx-0001Mf-N0 for bug-guix@gnu.org; Mon, 05 Nov 2018 14:47:01 -0500 Sender: "Debbugs-submit" Resent-Message-ID: Content-Disposition: inline In-Reply-To: <20181105191322.64a47ea0@alma-ubu> List-Id: Bug reports for GNU Guix List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: bug-guix-bounces+gcggb-bug-guix=m.gmane.org@gnu.org Sender: "bug-Guix" To: 33261@debbugs.gnu.org, bjoern.hoefling@bjoernhoefling.de, swedebugia@riseup.net --VbJkn9YxBvnuCH5J Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Mon, Nov 05, 2018 at 07:13:22PM +0100, Bj=F6rn H=F6fling wrote: > I would not consider this a bug: It clearly says that it is not a > proper URI. Also in the documentation all URLs/URIs are written in the > form of=20 >=20 > PROTOCOL://SERVER/PATH. I agree that it's not a bug, but perhaps it's more like a wishlist item. Ideally, users would not need to concern themselves with implementation details like protocol selection. Guix could offer a more unified or simpler interface for authorizing and selecting substitute servers, and it would handle server addresses, communication protocols, and key authorization. Currently it's very ad-hoc. --VbJkn9YxBvnuCH5J Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQIzBAABCAAdFiEEsFFZSPHn08G5gDigJkb6MLrKfwgFAlvgngoACgkQJkb6MLrK fwifCA//RtwPnfFm78mhS6l30d39BhvR2IE8rgxJsl64qXNvk4j7f3ZZeZcETGj2 GxmQZJhg87HaWEDo/CO7EF+BSZeZ2dk7SRrZFb89nYhApCgrJaknMKpkzhl7npqI NRQsr56PXHn4JOLIxOONM2DMbLVMTDWx27tUddbLZbyA7fLwR0106VELB16thBK1 FIVYy8DWq9cbYtFeIYqbjMul5AeEHiUFgFbbnAEdT3kqMTDdm+i7i9IDYxz1Kw1O BosC/JsinvAZrVCzrYa5xQfSOQYWeHb0KOW5eH3SDVgVtuLVi/vLVAc84X7ewH99 hp1pjaogZfXtqsenhCo+AZ/IYfhQuzMmlu+qDwJoDhnwtR0c5regaAPRTzjenuZI MExADuZOfSYXgU8Hyf2qXnsZCnGDf02byWaGSfMR2ImgbjaUgA4xbm6o6rB8cEIz BIvxCTZ3RkwTMfIILfBWmMqD2we7L440u8GiiwdeLzQMtyzHxSw8evcMBJQAchP3 MGxhzMDJeRzJAnJPEzLxuuD15ILNY9rIUosl6GMLrGGtSkRK8GxCz5ChXM2OUTQ0 JiAwyjEO0oM2n3s+Zzc8io5i9Qdk12a/SlZ4ssWI6kAbTtTyZ3ndeKxA8yWbbwrZ ATybamprQ7PxrMAYZdDdYWhJyjeRWFB7nwhzQyvbW79iptqscEo= =Smo3 -----END PGP SIGNATURE----- --VbJkn9YxBvnuCH5J--