From: Axel Thimm <Axel.Thimm@ATrpms.net>
To: linux-ia64@vger.kernel.org
Subject: Re: : IA64 ISOs based on Fedora Core 5
Date: Wed, 05 Apr 2006 16:35:21 +0000 [thread overview]
Message-ID: <20060405163521.GS30438@neu.nirvana> (raw)
[-- Attachment #1: Type: text/plain, Size: 1342 bytes --]
On Wed, Apr 05, 2006 at 10:44:45AM +0100, David Woodhouse wrote:
> On Tue, 2006-04-04 at 22:25 -0400, Paul Nasrat wrote:
> > I assume for the weekly snapshots of rawhide that you'll be putting
> > unique (eg date based) names on the isos so they can be readily
> > identified, else you're going to run into trouble tracking issues
> > across media sets.
>
> To be honest, I'm not convinced that weekly ISO builds are particularly
> useful -- we don't do that for rawhide on other architectures either.
> It's probably better just to encourage people to use rsync to keep up
> with rawhide, rather than downloading it all over again each week.
>
> > Do these isos correspond with FC5 or a random snapshot?
>
> Rawhide for about a week leading up to March 20th was identical to FC5
> in all but the 'fedora-release' package.
>
> If making an IA64 'FC5' I'd be inclined to replace the fedora-release
> package too. In fact, you almost certainly want to do that anyway, since
> you'll be publishing the errata, and fedora-release contains the yum
> configuration.
That might be helpful:
https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=187250
> Aside from the updates, the next task is building Extras and Livna for
> IA64, of course...
and who's going to do ATrpms? ;)
--
Axel.Thimm at ATrpms.net
[-- Attachment #2: Type: application/pgp-signature, Size: 191 bytes --]
next reply other threads:[~2006-04-05 16:35 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-05 16:35 Axel Thimm [this message]
2006-04-05 19:30 ` : IA64 ISOs based on Fedora Core 5 David Woodhouse
2006-04-05 19:59 ` Axel Thimm
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=20060405163521.GS30438@neu.nirvana \
--to=axel.thimm@atrpms.net \
--cc=linux-ia64@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.