I have been testing Sage on Debian (64 bits) on an ad hoc basis, and I have enough hardware power (a virtual host on a VMWare server) to run a testbot, if a setup is available and not too hard to install. (unfortunately it's behind a campus firewall, so it can't be ssh'd into from outside without a university VPN access, blah blah blah, so it doesn't make much sense for me to offer access to it for other Sage people)
On Oct 26, 9:47 am, Mitesh Patel <qed...@gmail.com> wrote: > On 10/25/2010 11:55 AM, David Kirkby wrote: > > > On 25 October 2010 17:26, Gonzalo Tornaria <torna...@math.utexas.edu> wrote: > >> On Mon, Oct 25, 2010 at 12:09 PM, David Kirkby <david.kir...@onetel.net> > >> wrote: > >>> Since Minh has been using an external server (I think run by GNU) for > >>> Debian, we can probably add Debian at some point if we can get > >>> permission to run a buildbot slave there. > > >> 1. Is there a reason for not running debian on a vm on boxen? > > > To my knowledge there is currently not a buildbot on any VM. I believe > > there is a plan to do this. But at this very moment there are not any > > There are several possible VMs, including Debian (32 and 64-bit), we > could add to or update on boxen's farm. It's a matter of someone (or > several people) setting them up, installing the operating systems, > keeping them up to date, etc. Unfortunately, this is a lot of work, > unless, perhaps, we distribute it. Alternatively, we can run > buildslaves on machines administered by others. > > > to my knowledge. Here's the list. As far as I'm aware the machines are > > either on > > > a) *.math.washington.edu hosts > > b) hosts on skynet > > c) 'hawk which is my personal machine. > > >> 2. what is needed to run a buildbot? > > > Mitesh will know more, since he has set them up. > > Basically, a machine should > > 0. Already be set up to build Sage. > > 1. Have an ssh-accessible 'buildbot' user account in which Sage builds. > ssh is for setup, maintenance, and build/test postmortems. Buildbot > uses a different protocol for master-slave communication. > > 2. Have a system-wide installation of Python 2.4 or later, including > the Python development headers. With this, I can 'easy_install > buildbot-slave' into a Python virtual environment [1], which makes it > easy to upgrade the package from the buildbot account. But the machine > administrator could instead install the package globally. > > [1]http://pypi.python.org/pypi/virtualenv > > > > > I know for me personally I just gave him an account (username > > buildbot), and an IP address into which the buildbot can ssh. > >> (it would feel pretty awkward not to support debian) > > > Agreed, but at this moment in time there is not a regular Debian > > machine. Hence I suggest we do not consider Debian "fully supported" > > until such as time as we test on Debian. -- To post to this group, send an email to sage-devel@googlegroups.com To unsubscribe from this group, send an email to sage-devel+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sage-devel URL: http://www.sagemath.org
