From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.org/gmane.linux.lib.musl.general/14903 Path: news.gmane.org!.POSTED.blaine.gmane.org!not-for-mail From: "A. Wilcox" Newsgroups: gmane.linux.lib.musl.general Subject: Re: The time64 switchover has happened! Date: Sun, 3 Nov 2019 10:22:48 -0600 Message-ID: <6E7E7379-B5C0-4CCC-9FC8-37EE37578569@adelielinux.org> References: <20191103062507.GW16318@brightrain.aerifal.cx> Reply-To: musl@lists.openwall.com Mime-Version: 1.0 (1.0) Content-Type: multipart/alternative; boundary=Apple-Mail-2DE3CDCA-1F4E-4931-AA25-D0ADBCA68F9D Content-Transfer-Encoding: 7bit Injection-Info: blaine.gmane.org; posting-host="blaine.gmane.org:195.159.176.226"; logging-data="35949"; mail-complaints-to="usenet@blaine.gmane.org" To: musl@lists.openwall.com Original-X-From: musl-return-14919-gllmg-musl=m.gmane.org@lists.openwall.com Sun Nov 03 17:23:10 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 1iRIek-0009Du-BT for gllmg-musl@m.gmane.org; Sun, 03 Nov 2019 17:23:10 +0100 Original-Received: (qmail 11530 invoked by uid 550); 3 Nov 2019 16:23:06 -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 11512 invoked from network); 3 Nov 2019 16:23:05 -0000 In-Reply-To: <20191103062507.GW16318@brightrain.aerifal.cx> X-Mailer: iPhone Mail (15E302) Xref: news.gmane.org gmane.linux.lib.musl.general:14903 Archived-At: --Apple-Mail-2DE3CDCA-1F4E-4931-AA25-D0ADBCA68F9D Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable On Nov 3, 2019, at 1:25 AM, Rich Felker wrote: >=20 > I just pushed the patch series switching 32-bit archs to 64-bit time. > Between now and next release, 32-bit archs' ABIs are intended-stable > but tentative, and could change before release, but I don't intend to > do that unless some serious unforseen problem is discovered during > testing and is impractical to fix without changing something. >=20 > The actual switchover commit is > 38143339646a4ccce8afe298c34467767c899f51 and the series ends with > d6dcfe4d0c58856690ecbad4cf191d7c9ee1a4a8. >=20 > Now, it's time for testing. I've done some build and smoke tests of > OpenSSL, Python, Perl, strace, coreutils, busybox (git master needed > to fix time64 problems), and a few other packages, but large > distro-scale package builds will be the real test of how easy this > transition is going to be. >=20 > For distributions that aren't a "make world" sort of thing (mix of > package versions), I know there will be issues with mixing old and new > libraries and applications; I'm not sure yet how severe they'll be. > This would be very useful to have reports/feedback on. Such distros > should make preparations, and short of detailed research to determine > how much or little breakage there will be, should make users aware > that a global dist-upgrade operation (with all libs and apps rebuilt > for time64) is the safest and recommended way to move to the first > release that will incorporate time64 musl. For the purposes of our try build test packaging, is it safe to call this co= mmit "1.2.0 alpha1"? Best, --arw=20 -- A. Wilcox (Sent from my iPhone - not signed) Project Lead, Ad=C3=A9lie Linux https://www.adelielinux.org/ --Apple-Mail-2DE3CDCA-1F4E-4931-AA25-D0ADBCA68F9D Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: quoted-printable On Nov 3, 2019, at 1:25 AM, Rich Felker <= ;dalias@libc.org> wrote:
<= br>
I just pushed the patch series= switching 32-bit archs to 64-bit time.
Between now and next= release, 32-bit archs' ABIs are intended-stable
but tentati= ve, and could change before release, but I don't intend to
d= o that unless some serious unforseen problem is discovered during
= testing and is impractical to fix without changing something.
The actual switchover commit is
381= 43339646a4ccce8afe298c34467767c899f51 and the series ends with
d6dcfe4d0c58856690ecbad4cf191d7c9ee1a4a8.

Now, it's time for testing. I've done some build and smoke tests of=
OpenSSL, Python, Perl, strace, coreutils, busybox (git master need= ed
to fix time64 problems), and a few other packages, but la= rge
distro-scale package builds will be the real test of how= easy this
transition is going to be.

For distributions that aren't a "make world" sort of thing (mix o= f
package versions), I know there will be issues with mixing= old and new
libraries and applications; I'm not sure yet ho= w severe they'll be.
This would be very useful to have repor= ts/feedback on. Such distros
should make preparations, and s= hort of detailed research to determine
how much or little br= eakage there will be, should make users aware
that a global d= ist-upgrade operation (with all libs and apps rebuilt
for ti= me64) is the safest and recommended way to move to the first
release that will incorporate time64 musl.
For the purposes of our try build test packaging, is it safe to call t= his commit "1.2.0 alpha1"?

Best,
--arw 

= --
A. Wilcox (Sent from my iPhone - not signed)=
Project Lead, Ad=C3=A9lie Linux
https://www.adelielin= ux.org/

= --Apple-Mail-2DE3CDCA-1F4E-4931-AA25-D0ADBCA68F9D--