Arthur Zamarin <arthur...@gentoo.org> 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).
signature.asc
Description: PGP signature
