1 |
-----BEGIN PGP SIGNED MESSAGE----- |
2 |
Hash: SHA1 |
3 |
|
4 |
Well, I've been fighting with GRP building for two days and haven't figured |
5 |
out why xfree is suddenly being merged for amd64. We haven't used xfree |
6 |
since before 2004.1. |
7 |
|
8 |
So I'm in a catch 22 now. I can't figure out what's causing xfree to merge, |
9 |
even with the help of wolf3102 and roger55 (thanks for the help guys). So I |
10 |
figured I'd just allow it to merge and remove the binary tarballs when it was |
11 |
done. But when I allow it to merge, some of the patches are failing to apply |
12 |
(and thus the ebuild fails). Compound that with the fact that either the |
13 |
digests for xfree 4.3.0-r6 are screwed up in portage or the patch tarballs in |
14 |
spyderous' devspace have changed. |
15 |
|
16 |
Frankly, I'm tired of fooling with it when I don't know of a single amd64 user |
17 |
who uses GRP. The deadline for 2004.2 is only hours away and GRP is the only |
18 |
thing that isn't complete. |
19 |
|
20 |
So, I'm making an executive decision for my arch. GRP isn't going to be |
21 |
available for amd64 in time for the 2004.2 release. If someone complains, |
22 |
I'll get something out after the release, but I don't expect to hear anything |
23 |
from users. Hell, low-end amd64 machines can bootstrap in under an hour. :-) |
24 |
|
25 |
Later! |
26 |
- -- |
27 |
Jason Huebel |
28 |
Gentoo/amd64 Strategic Lead |
29 |
Gentoo Developer Relations/Recruiter |
30 |
|
31 |
GPG Public Key: |
32 |
http://pgp.mit.edu:11371/pks/lookup?op=get&search=0x9BA9E230 |
33 |
|
34 |
"Do not weep; do not wax indignant. Understand." |
35 |
Baruch Spinoza (1632 - 1677) |
36 |
-----BEGIN PGP SIGNATURE----- |
37 |
Version: GnuPG v1.2.4 (GNU/Linux) |
38 |
|
39 |
iD8DBQFA/D5RbNgbbJup4jARAhipAJ98QpHvGjr/185X3Fl9UUYKh735CwCfZ7CU |
40 |
hvyjSCYIfOmEgwoTDk4quBg= |
41 |
=GPGw |
42 |
-----END PGP SIGNATURE----- |
43 |
|
44 |
-- |
45 |
gentoo-releng@g.o mailing list |