From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:38214) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1e75vk-0000Bb-3x for guix-patches@gnu.org; Tue, 24 Oct 2017 16:36:08 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1e75vg-0001hA-6Y for guix-patches@gnu.org; Tue, 24 Oct 2017 16:36:08 -0400 Received: from debbugs.gnu.org ([208.118.235.43]:51594) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1e75vf-0001gX-RO for guix-patches@gnu.org; Tue, 24 Oct 2017 16:36:04 -0400 Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1e75vd-0002tB-O1 for guix-patches@gnu.org; Tue, 24 Oct 2017 16:36:03 -0400 Subject: [bug#28977] tzdata updates and package rebuilding guidelines References: <8ae3fec37111ec4c68bfc7251c9193d975e16dcd.1508876232.git.leo@famulari.name> In-Reply-To: <8ae3fec37111ec4c68bfc7251c9193d975e16dcd.1508876232.git.leo@famulari.name> Resent-Message-ID: Date: Tue, 24 Oct 2017 16:35:25 -0400 From: Leo Famulari Message-ID: <20171024203525.GA5362@jasmine.lan> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="YiEDa0DAkWCtVeE4" Content-Disposition: inline List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: guix-patches-bounces+kyle=kyleam.com@gnu.org Sender: "Guix-patches" To: 28977@debbugs.gnu.org --YiEDa0DAkWCtVeE4 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable When splitting tzdata into two packages, one for "real" use and one for test suites, I'd hoped it would allow us to update tzdata immediately after new versions were released. But, there are still way more than 300 packages depending on tzdata, so it should be updated on a staging branch: $ guix refresh -l -e '(@@ (gnu packages base) tzdata)' =20 Building the following 335 packages would ensure 635 dependent packages are= rebuilt ... According to NEWS, if we don't update tzdata soon, some time zones will first become incorrect in Northern Cyprus in 5 days. "Northern Cyprus switches from +03 to +02/+03 on 2017-10-29" Any advice? Should we do a staging build? Just be late (the old status quo)? Something else? --YiEDa0DAkWCtVeE4 Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQIzBAABCAAdFiEEsFFZSPHn08G5gDigJkb6MLrKfwgFAlnvpA0ACgkQJkb6MLrK fwiLwA//SwODa0oiOjEnHdfS8lWDI6kzIG+oWyrcAFf+jVeJKZrv6u8jPLgZGnsL hTeuUv+/tm1c5q9V+/uwVe+Vrlndf1XFdYS8Z5p9XuXUcnNXGVhInaKLcI4782yt 1Q1ocbKYCre3wQtziiNLHDKfjN5od+AgIgT4A129SqHxRRRKsx5rR6/S9rtnZ8vw 03qQCpYgJtZrgKQ1R+gn3Uwq8TIQ7hW3C4hvMB0JN3Ya7eKf3ksCKEuuzzN/40Bn 1kopQKCHbiva4YMTRfQHQDOAaCC20jw/uXydIUmhbxBx2dHSJdefurNkbmBCUkOM LSNOL9nnrbf9LmnOuR+rx+vRhZh/DdsQQlMgPEv8cIO3E5l5sdlV8qsrZRR64rBR 38XCwmagfjZbZv3/worqf7BUgDBxe8uga6wezUYOpOFxoGLl6JYhYpEtIgJvek0v tOtcm+Yy/jCUSkWjjCqEor1UQbISxhW+jvbTz4Meg+q/Zk6cx9XyKOdUmzs0XQVy tI7xbg3owIuEUamOF3yeCSh1ORe2tM5yznWouA6XfuupEwGQmgkEpU0vb5FHE5A6 jIS9/OYHaNGtyy7Rl9O17FH8Wc87W3U5JB7LXRx4XuIYmV3Z9FiwHzpjmUPvflrm jh8TN3L5a3B+wLjaCdh/YptNjYjFZ6pYGFR1gOztqOYOVROj90c= =qxWl -----END PGP SIGNATURE----- --YiEDa0DAkWCtVeE4--