mailing list of musl libc
 help / color / mirror / code / Atom feed
From: "A. Wilcox" <awilfox@adelielinux.org>
To: musl@lists.openwall.com
Subject: Re: The time64 switchover has happened!
Date: Sun, 3 Nov 2019 10:22:48 -0600	[thread overview]
Message-ID: <6E7E7379-B5C0-4CCC-9FC8-37EE37578569@adelielinux.org> (raw)
In-Reply-To: <20191103062507.GW16318@brightrain.aerifal.cx>

[-- Attachment #1: Type: text/plain, Size: 1738 bytes --]

On Nov 3, 2019, at 1:25 AM, Rich Felker <dalias@libc.org> 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"?

Best,
--arw 

--
A. Wilcox (Sent from my iPhone - not signed)
Project Lead, Adélie Linux
https://www.adelielinux.org/


[-- Attachment #2: Type: text/html, Size: 2993 bytes --]

  reply	other threads:[~2019-11-03 16:22 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-03  6:25 Rich Felker
2019-11-03 16:22 ` A. Wilcox [this message]
2019-11-05 22:31   ` Rich Felker
2019-11-03 16:33 ` Dmitry V. Levin
2019-11-05 22:28   ` Rich Felker

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=6E7E7379-B5C0-4CCC-9FC8-37EE37578569@adelielinux.org \
    --to=awilfox@adelielinux.org \
    --cc=musl@lists.openwall.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.vuxu.org/mirror/musl/

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).