From owner-freebsd-cloud@freebsd.org Fri Mar 9 19:24:30 2018 Return-Path: Delivered-To: freebsd-cloud@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 146D2F44CA2 for ; Fri, 9 Mar 2018 19:24:30 +0000 (UTC) (envelope-from gjb@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [96.47.72.132]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "freefall.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id B5C9D6834E; Fri, 9 Mar 2018 19:24:29 +0000 (UTC) (envelope-from gjb@FreeBSD.org) Received: from FreeBSD.org (freefall.freebsd.org [IPv6:2610:1c1:1:6074::16:84]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by freefall.freebsd.org (Postfix) with ESMTPS id 7FE5FC8DF; Fri, 9 Mar 2018 19:24:29 +0000 (UTC) (envelope-from gjb@FreeBSD.org) Date: Fri, 9 Mar 2018 19:24:27 +0000 From: Glen Barber To: Jay Edwards Cc: freebsd-cloud@freebsd.org Subject: Re: Google Compute images Message-ID: <20180309192427.GL7399@FreeBSD.org> References: MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="zqjkMoGlbUJ91oFe" Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.9.1 (2017-09-22) X-BeenThere: freebsd-cloud@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: "FreeBSD on cloud platforms \(EC2, GCE, Azure, etc.\)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 09 Mar 2018 19:24:30 -0000 --zqjkMoGlbUJ91oFe Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Fri, Mar 09, 2018 at 02:14:19PM -0500, Jay Edwards wrote: > I noticed that the Google compute images stopped being updated on 28 Dec = of > last year. Is this intentional? Or a resource problem? >=20 Huh. It looks like something is broken with the google-cloud-sdk port. Thanks for pointing this out. I'm looking into it. Glen --zqjkMoGlbUJ91oFe Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQIzBAEBCAAdFiEEjRJAPC5sqwhs9k2jAxRYpUeP4pMFAlqi32cACgkQAxRYpUeP 4pP9AQ/+KobFeGbRVXiMpAmDDNvZ2XQNin3Ytq2eaGk4aYZGR9SRHQUWcT5jUCVi wu8/nnmP/Vjx4PFB+CRkIDTMGoPKIAFRmWA8tX3TmRXWjZr+XDCL+JeFYPUpOvzP OHSXRe5oJYQkFGmH0+re052SFl8cRjZJzXogrzn6vxMSJSgGH228wlpwtVYQHegi NKMyaJQ5VqmwY55VHjhyNxnfrQhx96TAM3p247mC7T+1EDoDhqIA3M8wFiSqKPRi dcZlCp0wRotC5jxsz0zQinOSL03vgJ7RD3uWkuiIv03JbZP5Fl+l95nMkw5EjpAs 2O7QebvW+hlo7XwwIjp+KaCX1bnw3Ygp7FEV6Lxzxj/YYYjTsMuzPm19/ktdNodQ zN9UjsJRSOJNaOJIBIdYwz/D4b9vz6jUf5o88FarN3NPjctCviP9OXrf4kEr43WL 675VNTJAkR1bSvd4vRDXAJiRHGEaV74apidbpLTXKH4T8rczf4xfm4q5UdYZPIYQ f1WnLfW3SgGwg9Mb7uzurLZATF+wgDp0JxzCk/mxjihWqNPP1LiDB7dwaIzd1VJk /ZlfrSv1UUm0OxNEYOhnF4IRspAc4G/bNyDnY5fyQLZogWytJUVDDJTDxY6BHB/z ut/+ilKAOHqZwOZJ5Bl7uUcWCqy7obg5CHwQ28d5jrhsWyP1h+Q= =OxIj -----END PGP SIGNATURE----- --zqjkMoGlbUJ91oFe--