public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Joshua Saddler <nightmorph@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Updated handbooks for autobuilds
Date: Tue, 20 Jul 2010 13:34:07 -0700	[thread overview]
Message-ID: <20100720133407.5287a07d@angelstorm> (raw)
In-Reply-To: <20091004114213.297eb354@angelstorm>

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

On Sun, 4 Oct 2009 11:42:13 -0700
Joshua Saddler <nightmorph@gentoo.org> wrote:

> There. I did the x86 and amd64 handbooks (networked, anyway; who cares about
> networkless). They're now ready for the 10th anniversary. I'm pretty sure.
> 
> I also did the x86 quickinstall handbooks.

It's been several months, so it's time for a status update:

This week I finally completed the alpha, arm, hppa, ia64, and sparc handbooks. Still have to do PPC/PPC64. There are just a few open tracker bugs; once these are fixed, that will free up all the ebuild and non-doc bugs that depend on our handbook bugs.

While doing the handbooks, I discovered that some of our arches have been neglected, so this next part is a call for help with the weekly/monthly autobuilds.

* * *

What's up with the arches:

x86 and AMD64 have not had new stages or LiveCDs in months. jmbsvicetto just started working on 'em, but we need LOTS of eyes and fixers for our two biggest arches. Right now there's no one else. Most of the breakages seem to come from toolchain and Python 3.x build failures (because *someone* wanted it stable), but it needs troubleshooting.

HPPA could use some assistance in generating autobuilt LiveCDs: the most recent CDs are from the 2008.0 release. If you've got the hardware, please contact the HPPA team.

IA64 hasn't had new media in a month, but I understand that armin76 is workin' on it. If you've got Itanium hardware, contact the ia64 team.

PPC64 hasn't produced much in the way of stages or CDs since October 2009.
PPC32 and PPC64 (32-bit userland) has stages from May, but no CDs since 10/2009. PowerPC is one of our bigger secondary platforms, right? We need folks with the hardware to diagnose the problems and come up with some build fixes, so that we can adjust the autobuild scripts.

Based on the number of releases, ARM, Sparc, and Alpha seem to be doing okay. More folks willing to watch for build failures and help out are, of course always welcome.

MIPS is is its own special arch; last releases are from 2007.0. However, r0bertz and redhatter are working on getting stuff to first compile before putting together autobuild releases. If you've got any kind of MIPS machine, especially something fairly recent, please get in touch with the MIPS folks to see about getting stuff to build. MIPS could use more recent stages. The installation instructions for MIPS are so different they have their own entirely nonconformant handbook. With working autobuilds, even on a monthly (or longer) basis, I could fix up the handbooks to make them much easier for folks to maintain. Nonstandard documentation is always extremely difficult to work with.

Bottom line: the autobuilds idea is a sound one. However, it needs more maintenance than you might think. We need more people to watch it and help out.

Thanks for your time,

Josh

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

  parent reply	other threads:[~2010-07-20 20:34 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-10-04 18:42 [gentoo-dev] Updated handbooks for autobuilds Joshua Saddler
2009-10-04 19:28 ` [gentoo-dev] " Christian Faulhammer
2009-10-04 21:11 ` [gentoo-dev] " Joseph Jezak
2009-10-04 21:17 ` Alex Alexander
2010-07-20 20:34 ` Joshua Saddler [this message]
2010-07-20 21:11   ` Richard Freeman
2010-07-20 22:54     ` Joshua Saddler

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=20100720133407.5287a07d@angelstorm \
    --to=nightmorph@gentoo.org \
    --cc=gentoo-dev@lists.gentoo.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