Packaging pypy

Hello Ubuntu/Debian Pythoneers, Maciej (CCd) contacted me last week to figure how to get pypy officially onto Ubuntu. Being the newbie Debian/Ubuntu developer that I am, I have no idea either, so I contacted the internal company mailing list, that finally guided me towards this forum as the right

Packaging pypy

Hello Ubuntu/Debian Pythoneers, Maciej (CCd) contacted me last week to figure how to get pypy officially onto Ubuntu. Being the newbie Debian/Ubuntu developer that I am, I have no idea either, so I contacted the internal company mailing list, that finally guided me towards this forum as the right

Re: Packaging pypy

Sorry, _actually_ CCd now. On Mon, Nov 28, 2011 at 14:54, Gustavo Niemeyer wrote: > Hello Ubuntu/Debian Pythoneers, > > Maciej (CCd) contacted me last week to figure how to get pypy > officially onto Ubuntu. Being the newbie Debian/Ubuntu developer that > I am, I have no idea either, so I contact

Re: Packaging pypy

Hi Gustavo (2011.11.28_18:32:52_+0200) > Would someone here be able to give a hand to Maciej on pushing that > integration forward? I'm interested in this, and happy to help. It's probably time to get PyPy back into Debian, I think all of our amd64 and i386 buildds are big enough to handle it thes

Re: Problems with building new version of pytools

Hi, Jakub Wilk writes: > There are two common solutions: > > 1) Nuke the whole *.egg-info in the clean target. > > 2) Add it to extend-diff-ignore in debian/source/options. We had the same issue with Zope packages, and nuking the whole *.egg-info in the clean target is not a good ide