[gentoo-releng] GRP for amd64

[gentoo-releng] GRP for amd64

[Jason Huebel]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Well, I've been fighting with GRP building for two days and haven't figured 
out why xfree is suddenly being merged for amd64.  We haven't used xfree 
since before 2004.1.

So I'm in a catch 22 now.  I can't figure out what's causing xfree to merge, 
even with the help of wolf3102 and roger55 (thanks for the help guys). So I 
figured I'd just allow it to merge and remove the binary tarballs when it was 
done. But when I allow it to merge, some of the patches are failing to apply 
(and thus the ebuild fails).  Compound that with the fact that either the 
digests for xfree 4.3.0-r6 are screwed up in portage or the patch tarballs in 
spyderous' devspace have changed.

Frankly, I'm tired of fooling with it when I don't know of a single amd64 user 
who uses GRP.  The deadline for 2004.2 is only hours away and GRP is the only 
thing that isn't complete.

So, I'm making an executive decision for my arch. GRP isn't going to be 
available for amd64 in time for the 2004.2 release.  If someone complains, 
I'll get something out after the release, but I don't expect to hear anything 
from users. Hell, low-end amd64 machines can bootstrap in under an hour. :-)

Later!
- -- 
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/D5RbNgbbJup4jARAhipAJ98QpHvGjr/185X3Fl9UUYKh735CwCfZ7CU
hvyjSCYIfOmEgwoTDk4quBg=
=GPGw
-----END PGP SIGNATURE-----

--
gentoo-releng@gentoo.org mailing list

Re: [gentoo-releng] GRP for amd64

[Donnie Berkholz]

Jason Huebel said:
> So I'm in a catch 22 now.  I can't figure out what's causing xfree to
> merge,  even with the help of wolf3102 and roger55 (thanks for the help
> guys). So I  figured I'd just allow it to merge and remove the binary
> tarballs when it was  done. But when I allow it to merge, some of the
> patches are failing to apply  (and thus the ebuild fails).  Compound
> that with the fact that either the  digests for xfree 4.3.0-r6 are
> screwed up in portage or the patch tarballs in  spyderous' devspace have
> changed.

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.



--
gentoo-releng@gentoo.org mailing list

Re: [gentoo-releng] GRP for amd64

[Jason Huebel]

-----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

Re: [gentoo-releng] GRP for amd64

[Donnie Berkholz]

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

On Tue, 2004-07-20 at 11:53, Jason Huebel wrote:
> 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.

Try a cvs diff -D "three weeks ago" in profiles/ or so. Or grep the
whole tree for hard dependencies on xfree.
-- 
Donnie Berkholz
Gentoo Linux

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]