From: Pieter Van den Abeele <pvdabeel@gentoo.org>
To: gentoo-releng@lists.gentoo.org
Cc: ppc@gentoo.org, Pieter Van den Abeele <pvdabeel@gentoo.org>
Subject: [gentoo-releng] ppc bootable iso bugfix
Date: Thu, 22 Apr 2004 08:21:43 +0200 [thread overview]
Message-ID: <531DF9BE-9425-11D8-AE43-0003938E7E46@gentoo.org> (raw)
Hi,
Here's why a good release cycle is needed:
We have started QA on live environment and kernel of the 2004.1 release
well in advance (even before the official releng date). I had
everything ready to be uploaded a week ago. Livecd booted ok (released
as _rc3 for testing). The only problem discovered was a missing /dev
directory on the stages (catalyst bug).
I did a cvs update to get the fix for this problem and rerolled the
stages. Until here everything fine. I noticed I had forgotten vim on
the older livecd, so I chrooted in it the stage1 and emerged vim
manually. I reran the stage2 and uploaded the result, assuming the cd
would be fine.
Apparently the stage2 was modified by the cvs update too, and added a
bunch of x86 rc-scripts to the default runlevel. These scripts called
for the x86 only 'hwsetup' (which gave an ugly error), tried 'detecting
the processor of the user' (which didn't work), tried loading APM bios
stuff (ppc has no BIOS)...
I am rebuilding the mini install and install cds (manually modified
catalyst to del instead of add the rc-scripts), updated versions
available today. Please note that in my REMARKS file in the catalyst
main directory, I already stated months ago that it was not a good idea
to assume all archs would use the same rc-scripts.
Best regards,
Pieter Van den Abeele
--
gentoo-releng@gentoo.org mailing list
next reply other threads:[~2004-04-22 6:22 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-22 6:21 Pieter Van den Abeele [this message]
2004-04-22 14:02 ` [gentoo-releng] ppc bootable iso bugfix John Davis
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=531DF9BE-9425-11D8-AE43-0003938E7E46@gentoo.org \
--to=pvdabeel@gentoo.org \
--cc=gentoo-releng@lists.gentoo.org \
--cc=ppc@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