Hi, I had the same problem for a while, a solution is to manually go through the ebuild, download with wget, unpack and apply patches / run sed-scripts and so on from a terminal and then install. This should be enough to get spython running and then you can do a "real" emerge python, emerge spython (You may well damage the python installation during the manual install if you do not watch out. //Spider begin quote On Mon, 18 Mar 2002 11:29:02 +0100 Andreas Waschbuesch wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > electrogramma tua profluit verbis: > > Hi ! > > > > I have merged the new revision on spython-2.0-r9. > > I had spython-2.0-r8, merged the new and unmerged the old. > > > > Now, ebuild/emerge does't work, because the binary spython is missing !!! > > > > I did the same stupid thing cause I didn't read changelog. Me to blame. > Still: any hints? > > Andrew > > - -- > Andreas Waschbuesch, GAUniversity KG MA FNZ FK01 > eMail: awaschb@gwdg.de > > If you think before you speak the other guy gets his joke in first. > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v1.0.6 (GNU/Linux) > Comment: For info see http://www.gnupg.org > > iD8DBQE8lcF32s5UCjOaQbYRAvu9AJ9WC1jfIesIrIxxBWzr8npu1oDgaQCfciDQ > B6zvfSDkQWJlN1R4T3V0Lzo= > =AgLi > -----END PGP SIGNATURE----- > _______________________________________________ > gentoo-dev mailing list > gentoo-dev@gentoo.org > http://lists.gentoo.org/mailman/listinfo/gentoo-dev >