| 1 |
On 12/01/10 05:02, Jorge Manuel B. S. Vicetto wrote: |
| 2 |
> As Arfrever noted, this is likely the cause of the broken automated |
| 3 |
> weekly stages for this past week. By not having a python symlink / |
| 4 |
> wrapper, stages generation failed on stage2 run. |
| 5 |
|
| 6 |
Yes, a fellow dev already reported that issue to me. |
| 7 |
I have proposed a patch in the python 2.7 status thread. |
| 8 |
Before mass-applying that I wanted to have review and/or more testing by |
| 9 |
myself. I'm afraid of causing worse damage than that. That's why it |
| 10 |
isn't fixed yet. |
| 11 |
|
| 12 |
|
| 13 |
> I'd like to take this chance to recall this is the 2nd time on the last |
| 14 |
> few months where stage generation was broken by python changes. Also, |
| 15 |
> we've been unable to create hardened stages for over 8 weeks because of |
| 16 |
> a sandbox issue. |
| 17 |
|
| 18 |
Can you give us a pointer on details? |
| 19 |
|
| 20 |
|
| 21 |
> The weekly stages generation depends on the quality and stability of the |
| 22 |
> "stable" tree. Therefore, the RelEng team kindly asks all maintainers to |
| 23 |
> pay attention to the stable ebuilds in the system set and to please fix |
| 24 |
> any failures asap as they may / can prevent stage generation. Be sure to |
| 25 |
> think carefully about changes that can impact the stage generation, in |
| 26 |
> particular when they involve python. |
| 27 |
|
| 28 |
Agreed. |
| 29 |
|
| 30 |
|
| 31 |
|
| 32 |
Sebastian |
Archives