From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from lists.gentoo.org (unknown [208.92.234.80]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits)) (No client certificate requested) by finch.gentoo.org (Postfix) with ESMTPS id 1ABE015802E for ; Wed, 26 Jun 2024 00:19:39 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 049F82BC086; Wed, 26 Jun 2024 00:19:24 +0000 (UTC) Received: from smtp.gentoo.org (woodpecker.gentoo.org [140.211.166.183]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits)) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id A37E02BC083 for ; Wed, 26 Jun 2024 00:19:23 +0000 (UTC) From: Sam James To: Arthur Zamarin Cc: gentoo-dev@lists.gentoo.org Subject: time64 & LFS for 32-bit arches (Re: [gentoo-dev] Arch Status and Future Plans) In-Reply-To: <75654daa-c5fc-45c8-a104-fae43b9ca490@gentoo.org> (Arthur Zamarin's message of "Tue, 25 Jun 2024 20:33:05 +0300") Organization: Gentoo References: <75654daa-c5fc-45c8-a104-fae43b9ca490@gentoo.org> Date: Wed, 26 Jun 2024 01:19:18 +0100 Message-ID: <87zfr8o8s9.fsf@gentoo.org> Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-dev@lists.gentoo.org Reply-to: gentoo-dev@lists.gentoo.org X-Auto-Response-Suppress: DR, RN, NRN, OOF, AutoReply MIME-Version: 1.0 Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha512; protocol="application/pgp-signature" X-Archives-Salt: a57b4ddf-f3dd-4419-affe-5f85456095b6 X-Archives-Hash: 14165559ceb45fb62c872d2f5be732df --=-=-= Content-Type: text/plain Arthur Zamarin writes: > Hi all, this will be a long mail, and might be confusing, I'll try to > organize it, but this is a mess, so bear with me. > > ======== 32-bit arches ======== > > This includes stable arches x86, arm, ppc, sparc32, dev arches s390, and > maybe more. Those are in much worse situation, with a mess on various > fronts, some of them super hard to continue support. For example > qtwebengine is less and less likely to manage to compile on a > real-hardware, and not 32-bit chroot on 64-bit host. Arch Team want to > minimize our work on those arches, meaning mass-destable and even > mass-dekeyword, with potentially full drop of stable status. > We haven't yet migrated to 64-bit time_t (and off_t - Large File Support/LFS) which will fix a lot of general test failures. Doing that before making any decision has value in two ways: 1) It might make the situation a lot better, who knows? 2) Even if we do then do a mass purge after, it leaves users on such platforms in a good state to keep stabilisation until after we're done, to help find any possible issues. dilfridge is currently beginning the time64 prep work (it requires LFS too). --=-=-= Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iOUEARYKAI0WIQQlpruI3Zt2TGtVQcJzhAn1IN+RkAUCZnteh18UgAAAAAAuAChp c3N1ZXItZnByQG5vdGF0aW9ucy5vcGVucGdwLmZpZnRoaG9yc2VtYW4ubmV0MjVB NkJCODhERDlCNzY0QzZCNTU0MUMyNzM4NDA5RjUyMERGOTE5MA8cc2FtQGdlbnRv by5vcmcACgkQc4QJ9SDfkZBfawEAnU1DNdmnYnivZ/ZkppQdAXz7XceQ8lN/1hiN LQ0JDLQA/3NmNu75RnW8HooDdHtb1se9pTKOoDgjrRVZIweTXeAK =WksY -----END PGP SIGNATURE----- --=-=-=--