From: dann frazier <dannf@dannf.org>
To: Carlos O'Donell <carlos@systemhalted.org>
Cc: Debian HPPA Port List <debian-hppa@lists.debian.org>,
linux-parisc <linux-parisc@vger.kernel.org>
Subject: Re: NTPL transition
Date: Thu, 4 Sep 2008 09:23:29 -0600 [thread overview]
Message-ID: <20080904152329.GA24316@colo.lackof.org> (raw)
In-Reply-To: <119aab440809040713m2a448cd4sea02cd2df7d7b42c@mail.gmail.com>
On Thu, Sep 04, 2008 at 10:13:15AM -0400, Carlos O'Donell wrote:
> On Thu, Sep 4, 2008 at 7:45 AM, Domenico Andreoli <cavok@dandreoli.com> wrote:
> > I would set NPTL transition as a goal for queeze.
> >
> > Are we available to agree on a shared path to push new life to this port?
> > I mean, this issue will bite more and more frequently, it must be fixed.
>
> I agree. I'm available and willing. I'm just not a DD nor am I
> familiar with debians sbuild or buildds.
>
> > I am available to follow the required steps but obviously the more eyes
> > the better. This is the first time I work on a big transition like this.
>
> I'm available at OFTC on #debian-glibc. I act as a debian-hppa porter
> and help Aurelian when glibc hppa issues arise.
>
> > I think the first packages have to be cross-built, until a minimal
> > build system is ready to run on the new libc6.1 (chroot?). Then start
> > an archive rebuild. It looks easy, where is the trap? :)
>
> I'm not familiar with the debian build infrastructure, but I am *very*
> familiar with libc since I'm the upstream ports maintainer for hppa.
>
> I don't think there is any trap.
I've already done the initial bootstrapping and John Wright and I have
a buildd actively rebuilding bits against sid. We're rsyncing the
results out to here:
http://parisc-linux.org/~dannf/hppa-nptl-mirror/unstable/
Suffice to say, the rebuild is going fairly smoothly. But, I wonder
how we're going to transition systems over to an NPTL userspace. Does
anyone have a plan for that?
--
dann frazier
next prev parent reply other threads:[~2008-09-04 15:23 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20080904114551.GA18877@tilt.dandreoli.com>
2008-09-04 14:13 ` NTPL transition Carlos O'Donell
2008-09-04 15:23 ` dann frazier [this message]
2008-09-04 15:31 ` Carlos O'Donell
2008-09-04 16:04 ` dann frazier
2008-09-04 17:29 ` Carlos O'Donell
2008-09-04 17:49 ` dann frazier
2008-09-04 17:52 ` James Bottomley
2008-09-04 23:26 ` Domenico Andreoli
2008-09-05 12:17 ` Carlos O'Donell
2008-09-05 14:07 ` James Bottomley
2008-09-05 14:20 ` Kyle McMartin
2008-09-05 14:58 ` Carlos O'Donell
2008-09-04 23:22 ` Domenico Andreoli
2008-09-06 8:24 Petr Salinger
2008-09-06 15:31 ` Carlos O'Donell
2008-09-06 20:16 ` Petr Salinger
2008-09-06 21:36 ` Carlos O'Donell
2008-10-24 5:45 ` Carlos O'Donell
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=20080904152329.GA24316@colo.lackof.org \
--to=dannf@dannf.org \
--cc=carlos@systemhalted.org \
--cc=debian-hppa@lists.debian.org \
--cc=linux-parisc@vger.kernel.org \
/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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox