Date: Tue, 24 Jan 2017 18:57:25 +0100 From: Mathieu Arnold <mat@FreeBSD.org> To: David Wolfskill <david@catwhisker.org> Cc: ports list <freebsd-ports@freebsd.org> Subject: Re: devel/cargo build failure Message-ID: <7c0acfc6-47d4-9922-502d-a53170c1e07d@FreeBSD.org> In-Reply-To: <20170124174756.GM5908@albert.catwhisker.org> References: <20170124155240.GA22684@rancor.immure.com> <2d8012ba-2943-5ee5-c720-a391c6cb460c@FreeBSD.org> <20170124174756.GM5908@albert.catwhisker.org>
next in thread | previous in thread | raw e-mail | index | archive | help
This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --qVuC5Pj0qlE1Mr24Qsbjchrcf95gC3OCB Content-Type: multipart/mixed; boundary="HDVsvNfXlcjgjrCmrrdwU2MvNSKf9JLKa"; protected-headers="v1" From: Mathieu Arnold <mat@FreeBSD.org> To: David Wolfskill <david@catwhisker.org> Cc: ports list <freebsd-ports@freebsd.org> Message-ID: <7c0acfc6-47d4-9922-502d-a53170c1e07d@FreeBSD.org> Subject: Re: devel/cargo build failure References: <20170124155240.GA22684@rancor.immure.com> <2d8012ba-2943-5ee5-c720-a391c6cb460c@FreeBSD.org> <20170124174756.GM5908@albert.catwhisker.org> In-Reply-To: <20170124174756.GM5908@albert.catwhisker.org> --HDVsvNfXlcjgjrCmrrdwU2MvNSKf9JLKa Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Le 24/01/2017 =C3=A0 18:47, David Wolfskill a =C3=A9crit : > On Tue, Jan 24, 2017 at 06:33:29PM +0100, Mathieu Arnold wrote: >> Le 24/01/2017 =C3=A0 16:52, Bob Willcox a =C3=A9crit : >>> When trying to build devel/cargo I get this error: >>> >>> /xports/Mk/Scripts/checksum.sh: cannot open 2016-11-02/cargo-nightly-= x86_64-unknown-freebsd.tar.gz: No such file or directory >>> *** Error code 2 >>> >>> Stop. >>> make: stopped in /xports/devel/cargo >>> >>> Anyone have any ideas why and what I can do to overcome it? >> Ok, so, the port changed the directory this file is fetched in, to fix= >> the problem, you'll need to remove the >> cargo-nightly-x86_64-unknown-freebsd.tar.gz from /usr/ports/distfiles >> (or whereever your distfiles are) >> .... > Thanks -- that worked for me. So, I opened PR #216442 to see if the code that made this problem was legacy or not, an exp-run will tell :-) --=20 Mathieu Arnold --HDVsvNfXlcjgjrCmrrdwU2MvNSKf9JLKa-- --qVuC5Pj0qlE1Mr24Qsbjchrcf95gC3OCB Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQJ8BAEBCgBmBQJYh5WFXxSAAAAAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXQzQUI2OTc4OUQyRUQxMjEwNjQ0MEJBNUIz QTQ1MTZGMzUxODNDRTQ4AAoJEDpFFvNRg85IIy0QAJ0keou7Qz+jPTmhQtTFjuo7 4rWthRabwewpws9mfrCHYUF/HaBAUSN3qw1xRkhCv6yV/bThc3YZUdrOQhmH/BMR M3ZWQd12SEabjnS42IfiZAsrQznjHSpf5McSYPMZIBOUHOdwUTDquvKDlxHeNDV9 hDvrBQwHufCwysz2u8DqlX6x2Pa7Xnlfrpe088JbrkT+0vkqiUVD5uXGZXJu3ax8 Nhzrj5JtGnIzFq2dlavJmRyLnl1qxWzfhZTiF/Gu5fHx7Kx/DB2GX3fU7R4Iwxvd UripNmc8ACvvET03Vw8HC3kP15w++MtKEHCeT+5P3Dt+z6shZJ986NtxqtMS8Oaq s+BfGN6kBRIN28iQsIGhYGfqmElWp2B8lPqTeGTjzhR9bjjf+3Zfza3sP7dLMWlM QU60fCemVsOdSbjdI4bd5jon932N+V8diJXSxIllJTjFzKRZaWjBWcdG0qyShV69 XOhGnQob5GDjpGH8EDKsjHcJpnXL0Yfe9tT42No9nO7Fm6Xh4r99JJLEW7sBkkSr 7YIyXAZx7Y3LalxijSkRZD6+4MiI5N7GA9hKiKpReKWtlI1Ig/GfNSGDG0jrvDxR a7OL/vNLRn4e+e+d7OEHXx0VyNZNcwHmG+oYTj99QXCnx1m2ZlVVfqlFMNsOa/MU fUQdsmOEIsC8xfU9eKzD =c8QN -----END PGP SIGNATURE----- --qVuC5Pj0qlE1Mr24Qsbjchrcf95gC3OCB--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?7c0acfc6-47d4-9922-502d-a53170c1e07d>