From: "A. Wilcox" <awilfox@adelielinux.org>
To: musl@lists.openwall.com
Subject: Re: time64 switchover -- distro plans?
Date: Mon, 28 Oct 2019 06:52:04 -0500 [thread overview]
Message-ID: <65a0ee78-eaaf-f3fa-84f3-782fbdc4b06e@adelielinux.org> (raw)
In-Reply-To: <20191027040820.GV16318@brightrain.aerifal.cx>
[-- Attachment #1.1: Type: text/plain, Size: 2114 bytes --]
On 26/10/2019 23:08, 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.
>
> 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?
We can launch a full distro build against any given musl commit on
32-bit PowerPC and ARM (v7). We have test suites enabled on 1280 of our
2087 packages (~61%) so that should help find bugs if any. I can also
then install it on a Power Mac G4 and a Raspberry Pi 2 we have set aside
for testing experimental changes.
It'd be much more difficult, but if nobody else offers i586 testing, we
*may* be able to do that as well. Let us know.
> 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).
That sounds great.
> 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.
We would probably be ready for this in November.
Best,
--arw
--
A. Wilcox (awilfox)
Project Lead, Adélie Linux
https://www.adelielinux.org
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2019-10-28 11:52 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-27 4:08 Rich Felker
2019-10-27 8:19 ` Khem Raj
2019-10-27 23:44 ` Rich Felker
2019-10-28 11:52 ` A. Wilcox [this message]
2019-10-29 17:05 ` 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=65a0ee78-eaaf-f3fa-84f3-782fbdc4b06e@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).