From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.org/gmane.linux.lib.musl.general/14869 Path: news.gmane.org!.POSTED.blaine.gmane.org!not-for-mail From: Khem Raj Newsgroups: gmane.linux.lib.musl.general Subject: Re: time64 switchover -- distro plans? Date: Sun, 27 Oct 2019 09:19:07 +0100 Message-ID: References: <20191027040820.GV16318@brightrain.aerifal.cx> Reply-To: musl@lists.openwall.com Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="0000000000001ebcbd0595e00a9b" Injection-Info: blaine.gmane.org; posting-host="blaine.gmane.org:195.159.176.226"; logging-data="100863"; mail-complaints-to="usenet@blaine.gmane.org" To: musl@lists.openwall.com Original-X-From: musl-return-14885-gllmg-musl=m.gmane.org@lists.openwall.com Sun Oct 27 09:19:34 2019 Return-path: Envelope-to: gllmg-musl@m.gmane.org Original-Received: from mother.openwall.net ([195.42.179.200]) by blaine.gmane.org with smtp (Exim 4.89) (envelope-from ) id 1iOdlu-000Q76-A5 for gllmg-musl@m.gmane.org; Sun, 27 Oct 2019 09:19:34 +0100 Original-Received: (qmail 1382 invoked by uid 550); 27 Oct 2019 08:19:31 -0000 Mailing-List: contact musl-help@lists.openwall.com; run by ezmlm Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-ID: Original-Received: (qmail 1360 invoked from network); 27 Oct 2019 08:19:31 -0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to; bh=cHhk5RMyX77uIOYDgk2/cvT2rqaoL4jI5qAuq2wYKgk=; b=ktatcWUHBlSrxP6ogmP4ktAQSSbL9/0rsUSn9pti0GyFNjVhlcO80QYfJdR6UExTvN ngoZr7QZK73TOSNLYTkHuAp4vnpoMOF12LWB1TODT+nso5Zo5C7bngCWZXj9Nnc1esY9 0SBWcU7u/Q/kGByGNbcwmYgfeNmDXd4dy8U/OC/EdMkqLtRpxjaaCt5xnU3hyQeFMcub RkeyBSlfIxkym9BLawDnz9nR/6V5jVO0kLPRbgEu/PBgfHudee6WdnnKY+cugZuE9kle O/+OVBMyH3yzZf+Om7fSssmv+mk9Ee5lkFCl1kLzNvaFEIwNS3UruSrMGcg5EweB9ecA A+BA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to; bh=cHhk5RMyX77uIOYDgk2/cvT2rqaoL4jI5qAuq2wYKgk=; b=QgUNJ3xLMpip6qX73jgRfIUa1i8VMkmiJkVMCikRq8821weJD6uyXZPdZNvVNlueH3 LzZdq7S3euO/Akjjpi9v2pXVZwKuqrg19dGgNbqI+bbvJrVXXD1JEiSTKnD6/u+AfXsG RwyC6AqS/5Abl3sloj6wthS7y649z1RjCjBhIoFYy3wJSRWkvo01jxjQeSJmHL1uAQjY 5NAggaLsIvOQZP9j49yeTaOVeq2TjXXF7fz3TQ2GTBx+ZaSBavzFVfx8eMceujIGWXNa /azChi7yNsfTahaeMtD+nocpFaPMUTRGtVNRgdEkv+27rJxSalaUO82VwOmzaHqqx1Yc PIyg== X-Gm-Message-State: APjAAAUhyhfo8LmhOxIuMA2S2e6VwZ6mgAVHqSMn5dy2fmMDqQNp1drS 8PxOHKJAwcdUVM6EovGVVxOun9zu3S1H+F1cz/DO94D4Bpk= X-Google-Smtp-Source: APXvYqz3EGNWoo3cfieIx8xE9gY3B7ZBe+BzW3YL/XbupCyoUT0sRFopsuEjseIh5tJB0+6TxfDpRgCdQmb0RiCmv0k= X-Received: by 2002:ac8:411b:: with SMTP id q27mr12299624qtl.53.1572164358551; Sun, 27 Oct 2019 01:19:18 -0700 (PDT) In-Reply-To: <20191027040820.GV16318@brightrain.aerifal.cx> Xref: news.gmane.org gmane.linux.lib.musl.general:14869 Archived-At: --0000000000001ebcbd0595e00a9b Content-Type: text/plain; charset="UTF-8" On Sun, Oct 27, 2019 at 5:08 AM Rich Felker wrote: > This thread is a call for feedback from distros (or other > similarly-situated systems integrators) using musl with 32-bit archs. > Everything is moving smoothly on my side for upcoming time64 > switchover which will be included in the next release, 1.2.0. But with > this involving ABI issues between packages and changes that some > software may not be ready for, it will likely be at least somewhat > disruptive to distros/users. When are we planning for 1.2 release approximately? I would like to see it before March 2020 since openembedded/yocto releases in April this fits well with scheduling this upgrade and gives time to test it on various platforms > > In particular: > > * Are there resources I could/should make available that will help > things go smoothly? > > * Are you available for testing building and running packages against > time64 musl prior to release? Yes > > From my side, I'm planning to write up release notes/announcement far > more detailed than usual, with instructions on switchover, what ABI > compatibility/stability does & doesn't mean, possible pitfalls, tips > for catching code that may have time64-related bugs, etc., and just > basic FAQ items like whether you need a 5.1+ kernel (no) or kernel > headers (no). > > I'll also be building and testing some software on i386 and sh at > least; I already started with busybox, which just got the main > time64-readiness issue I was aware of fixed. > > I think I'll push the last of the time64 patches within the next week, > possibly sooner, meaning "distros start testing" is a thing that could > begin really soon if anyone's up for it. I will be able to start doing master work in couple of weeks > > Rich > --0000000000001ebcbd0595e00a9b Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable


On Sun, Oct 27, 2019 at 5:08 AM Rich Felker <dalias@libc.org> wrote:
This thread is a call for feedback from distros (or oth= er
similarly-situated systems integrators) using musl with 32-bit archs.
Everything is moving smoothly on my side for upcoming time64
switchover which will be included in the next release, 1.2.0. But with
this involving ABI issues between packages and changes that some
software may not be ready for, it will likely be at least somewhat
disruptive to distros/users.

When are we planning for 1.2 release approximately?
I would like to see it before March 2020 since openembedded/yoc= to releases in April this fits well with scheduling this upgrade and gives = time to test it on various=C2=A0platforms

=



In particular:

* Are there resources I could/should make available that will help
=C2=A0 things go smoothly?

* Are you available for testing building and running packages against
=C2=A0 time64 musl prior to release?

Yes=C2=A0



>From my side, I'm planning to write up release notes/announcement far more detailed than usual, with instructions on switchover, what ABI
compatibility/stability does & doesn't mean, possible pitfalls, tip= s
for catching code that may have time64-related bugs, etc., and just
basic FAQ items like whether you need a 5.1+ kernel (no) or kernel
headers (no).

I'll also be building and testing some software on i386 and sh at
least; I already started with busybox, which just got the main
time64-readiness issue I was aware of fixed.

I think I'll push the last of the time64 patches within the next week,<= br> possibly sooner, meaning "distros start testing" is a thing that = could
begin really soon if anyone's up for it.
=
I will be able to start doing master work in co= uple of weeks=C2=A0



Rich
--0000000000001ebcbd0595e00a9b--