1 |
Hi Folks, |
2 |
|
3 |
I tried to build stages for x86 including Python.2.3.3 on the AMD64 |
4 |
releng box, but - as Alastair already stated - they weren't properly |
5 |
built. Also I am worrying about updating another system-critical |
6 |
package, since this would include another set of test-stages and ~3 days |
7 |
for testing. This would delay the release for x86 (was "end of January") |
8 |
since we also need excessive testing of the live-cd's for x86. |
9 |
|
10 |
I personally don't would have a problem including another package and do |
11 |
some testing, since this can only improve the quality of this release - |
12 |
but this would also mean, that the x86-release for 2004.0 *might* |
13 |
possibly be delayed. |
14 |
|
15 |
At this point I am requesting your opinions, please :) |
16 |
|
17 |
Regards, |
18 |
Benjamin "beejay" Judas |
19 |
|
20 |
> Hi All, |
21 |
> |
22 |
> I've been working on getting Python-2.3.3 ready for stage building and |
23 |
> inclusion into 2004.1. I've been working with Beejay for some time to |
24 |
> get stages built, but for some reason, he's having trouble building |
25 |
> python for stage3 (works for stage1 and stage2.) |
26 |
> |
27 |
> However, I've been able to build stages using catalyst for stage1, |
28 |
> stage2 and stage3 with Python-2.3.3 stable (thus replacing |
29 |
> python-2.2.3-r5). This is the only thing that is holding us back from |
30 |
> pushing Python-2.3.3 to stable. The said stages are here: |
31 |
> |
32 |
> http://dev.gentoo.org/~liquidx/stages/ |
33 |
> |
34 |
> So if it is possible, can the x86 stagers see if Python-2.3.3 is good |
35 |
> to go for 2004.1? |
36 |
> |
37 |
> Thanks, |
38 |
> - -- |
39 |
> Alastair 'liquidx' Tse |
40 |
> >> Gentoo Developer |
41 |
> >> http://www.liquidx.net/ | http://dev.gentoo.org/~liquidx/ |
42 |
|
43 |
-- |
44 |
GPG-Public-Key: |
45 |
http://pgp.mit.edu:11371/pks/lookup?op=get&search=0xC31DEDD8 |
46 |
|
47 |
Key-Fingerprint: |
48 |
4E65 AAFE 785B 61D8 E4D9 1671 E017 87B7 C31D EDD8 |
49 |
|
50 |
ICQ: 239829549 |
51 |
Jabber:beejay@×××××××××.org |