From: Jason Huebel <jhuebel@gentoo.org>
To: gentoo-releng@lists.gentoo.org
Subject: Re: [gentoo-releng] GRP for amd64
Date: Tue, 20 Jul 2004 10:53:38 -0500 [thread overview]
Message-ID: <200407201053.45459.jhuebel@gentoo.org> (raw)
In-Reply-To: <10774.205.241.48.33.1090283266.squirrel@spidermail.richmond.edu>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Monday 19 July 2004 07:27 pm, Donnie Berkholz wrote:
> Something screwy happened here, and I've been on vacation. tseng should
> have fixed the problem by reverting to an older patchset version Friday,
> however.
Well, that's not so much the problem as the fact that xfree is merging at all.
Interestingly, I had a full GRP set already built from an older snapshot
(20040626) and figured that rebuilding with the newer snapshot (20040716)
wouldn't be a problem. Apparently I was wrong.
So whatever changed in portage that caused xfree to merge happened in the past
three weeks.
I'm disappointed that GRP is getting dropped from amd64 for 2004.2. But since
all the LiveCDs and stages are now basedon the newer snapshot, the old GRP
set I built isn't particularly useful.
- --
Jason Huebel
Gentoo/amd64 Strategic Lead
Gentoo Developer Relations/Recruiter
GPG Public Key:
http://pgp.mit.edu:11371/pks/lookup?op=get&search=0x9BA9E230
"Do not weep; do not wax indignant. Understand."
Baruch Spinoza (1632 - 1677)
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)
iD8DBQFA/UAJbNgbbJup4jARApnDAJ99SQXBVATbV6NkFF9DUkNyecwHewCfVe47
7hxQaHEELL8XlY9KDQiqM7U=
=ltg6
-----END PGP SIGNATURE-----
--
gentoo-releng@gentoo.org mailing list
next prev parent reply other threads:[~2004-07-20 15:47 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-19 21:34 [gentoo-releng] GRP for amd64 Jason Huebel
2004-07-20 0:27 ` Donnie Berkholz
2004-07-20 15:53 ` Jason Huebel [this message]
2004-07-20 19:54 ` Donnie Berkholz
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=200407201053.45459.jhuebel@gentoo.org \
--to=jhuebel@gentoo.org \
--cc=gentoo-releng@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