From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.org/gmane.linux.lib.musl.general/14906 Path: news.gmane.org!.POSTED.blaine.gmane.org!not-for-mail From: Rich Felker Newsgroups: gmane.linux.lib.musl.general Subject: Re: The time64 switchover has happened! Date: Tue, 5 Nov 2019 17:31:55 -0500 Message-ID: <20191105223155.GA16318@brightrain.aerifal.cx> References: <20191103062507.GW16318@brightrain.aerifal.cx> <6E7E7379-B5C0-4CCC-9FC8-37EE37578569@adelielinux.org> Reply-To: musl@lists.openwall.com Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Injection-Info: blaine.gmane.org; posting-host="blaine.gmane.org:195.159.176.226"; logging-data="199458"; mail-complaints-to="usenet@blaine.gmane.org" User-Agent: Mutt/1.5.21 (2010-09-15) To: musl@lists.openwall.com Original-X-From: musl-return-14922-gllmg-musl=m.gmane.org@lists.openwall.com Tue Nov 05 23:32: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 1iS7Mw-000pkp-5p for gllmg-musl@m.gmane.org; Tue, 05 Nov 2019 23:32:10 +0100 Original-Received: (qmail 5772 invoked by uid 550); 5 Nov 2019 22:32:08 -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 5751 invoked from network); 5 Nov 2019 22:32:07 -0000 Content-Disposition: inline In-Reply-To: <6E7E7379-B5C0-4CCC-9FC8-37EE37578569@adelielinux.org> Original-Sender: Rich Felker Xref: news.gmane.org gmane.linux.lib.musl.general:14906 Archived-At: On Sun, Nov 03, 2019 at 10:22:48AM -0600, A. Wilcox wrote: > On Nov 3, 2019, at 1:25 AM, Rich Felker wrote: > > > > 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. > > > > The actual switchover commit is > > 38143339646a4ccce8afe298c34467767c899f51 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 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. > > > > 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 commit "1.2.0 alpha1"? I don't see any reason not to, but I'm not familiar with the details of how your package versioning works. There won't be a branch of time64 released as 1.1.x; if there are any future 1.1.x releases they'll be bugfix backports for EOL'd time32. Rich