| 1 |
> Modified: ChangeLog |
| 2 |
> Removed: python-3.1.2_p20100801.ebuild |
| 3 |
> python-2.7_p20100801.ebuild |
| 4 |
> python-2.6.5_p20100801.ebuild |
| 5 |
> Log: |
| 6 |
> remove the backported versions; they're autogenerated, obviously |
| 7 |
> not tested for 2.6 (bug 330937, breaking portage for anyone runing |
| 8 |
> unstable python at time of commit), and have been the source of a |
| 9 |
> shitload of other rather odd bugs till identification of what was |
| 10 |
> occuring (bug 330667). ignoring a PDEPEND.bad for 3.1.2-r3 for |
| 11 |
> >=app-admin/python-updater-0.8 also to get these removed |
| 12 |
|
| 13 |
> + -python-2.6.5_p20100801.ebuild, -python-2.7_p20100801.ebuild, |
| 14 |
> + -python-3.1.2_p20100801.ebuild: |
| 15 |
> + Remove untested versions, one of which flat out breaks emerge (bug |
| 16 |
> 330937). |
| 17 |
> + These should not be re-added without going through devrel/qa. |
| 18 |
|
| 19 |
Hello fellow developers, |
| 20 |
There is quite an issue with python here that I want a wider audience |
| 21 |
to be aware of because it did affect our users. Especially ~arch users |
| 22 |
that were trying to avoid python-3. The intent of this email is purely |
| 23 |
FYI. |
| 24 |
|
| 25 |
(You can find a fix on the mentioned bug, if you are wondering) |
| 26 |
|
| 27 |
-Jeremy |
Archives