[arch-dev-public] Who wants to set up my 64 bit build box?
I have a machine that has been put aside for building 64 bit packages. Now that Aaron's is dead, we could start using this one. I have no idea how Aaron's was set up so I don't really have an idea on how to set this one up. What is needed for me to make this build machine available?
On Thu, May 29, 2008 at 1:02 PM, Jason Chu <jason@archlinux.org> wrote:
I have a machine that has been put aside for building 64 bit packages. Now that Aaron's is dead, we could start using this one. I have no idea how Aaron's was set up so I don't really have an idea on how to set this one up.
What is needed for me to make this build machine available?
I can do it. Give me sudo access and I will set it all up the same way I had mine setup. It's fairly easy, here are the steps I did: mkarchroot /var/archroot base base-devel sudo cd /etc/skel mkdir -p chroot-shell/{rw, union} ln -s /var/archroot chroot-shell/root groupadd builders Allow 'builders' to execute "makechrootpkg" in /etc/sudoers Make sure CHROOT_SHELL is an allowed envvar in /etc/sudoers add "export CHROOT_SHELL="$HOME/chroot-shell" to /etc/skel/.bashrc Ummm.... I had a cron job running "mkarchroot -u" on /var/archroot because it didn't need to boot or anything, so auto-updates are cool I also had a long motd explaining the instructions, but I can wikify that if you want. What else, what else... Make sure user accounts are added to the "builders" group. Additionally, I did install devtools from git, due to the unionfs issues (we haven't released a new devtools with that fix in it)
On Thu, May 29, 2008 at 2:11 PM, Aaron Griffin <aaronmgriffin@gmail.com> wrote:
On Thu, May 29, 2008 at 1:02 PM, Jason Chu <jason@archlinux.org> wrote:
I have a machine that has been put aside for building 64 bit packages. Now that Aaron's is dead, we could start using this one. I have no idea how Aaron's was set up so I don't really have an idea on how to set this one up.
What is needed for me to make this build machine available?
I can do it. Give me sudo access and I will set it all up the same way I had mine setup.
It's fairly easy, here are the steps I did:
mkarchroot /var/archroot base base-devel sudo
I think it would also be way beneficial to have a testing-enabled chroot beside the 'current' chroot. After creating the chroot (say /var/archroot-testing), just edit /var/archroot-testing/etc/pacman.conf and enable testing, then run mkarchroot -u to update the chroot. Then guys like me can even build against testing packages. Woot.
On Thu, May 29, 2008 at 1:15 PM, Travis Willard <travis@archlinux.org> wrote:
On Thu, May 29, 2008 at 2:11 PM, Aaron Griffin <aaronmgriffin@gmail.com> wrote:
On Thu, May 29, 2008 at 1:02 PM, Jason Chu <jason@archlinux.org> wrote:
I have a machine that has been put aside for building 64 bit packages. Now that Aaron's is dead, we could start using this one. I have no idea how Aaron's was set up so I don't really have an idea on how to set this one up.
What is needed for me to make this build machine available?
I can do it. Give me sudo access and I will set it all up the same way I had mine setup.
It's fairly easy, here are the steps I did:
mkarchroot /var/archroot base base-devel sudo
I think it would also be way beneficial to have a testing-enabled chroot beside the 'current' chroot. After creating the chroot (say /var/archroot-testing), just edit /var/archroot-testing/etc/pacman.conf and enable testing, then run mkarchroot -u to update the chroot.
Then guys like me can even build against testing packages. Woot.
Yeah, you'd just have to flip around the ~/chroot-shell/root symlink to point to different chroots
On Thu, May 29, 2008 at 2:20 PM, Aaron Griffin <aaronmgriffin@gmail.com> wrote:
On Thu, May 29, 2008 at 1:15 PM, Travis Willard <travis@archlinux.org> wrote:
On Thu, May 29, 2008 at 2:11 PM, Aaron Griffin <aaronmgriffin@gmail.com> wrote:
On Thu, May 29, 2008 at 1:02 PM, Jason Chu <jason@archlinux.org> wrote:
I have a machine that has been put aside for building 64 bit packages. Now that Aaron's is dead, we could start using this one. I have no idea how Aaron's was set up so I don't really have an idea on how to set this one up.
What is needed for me to make this build machine available?
I can do it. Give me sudo access and I will set it all up the same way I had mine setup.
It's fairly easy, here are the steps I did:
mkarchroot /var/archroot base base-devel sudo
I think it would also be way beneficial to have a testing-enabled chroot beside the 'current' chroot. After creating the chroot (say /var/archroot-testing), just edit /var/archroot-testing/etc/pacman.conf and enable testing, then run mkarchroot -u to update the chroot.
Then guys like me can even build against testing packages. Woot.
Yeah, you'd just have to flip around the ~/chroot-shell/root symlink to point to different chroots
Or have ~/chroot-shell/ and ~/chroot-shell-testing/ and change where $CHROOT_SHELL points, but yeah
On Thu, May 29, 2008 at 01:11:37PM -0500, Aaron Griffin wrote:
On Thu, May 29, 2008 at 1:02 PM, Jason Chu <jason@archlinux.org> wrote:
I have a machine that has been put aside for building 64 bit packages. Now that Aaron's is dead, we could start using this one. I have no idea how Aaron's was set up so I don't really have an idea on how to set this one up.
What is needed for me to make this build machine available?
I can do it. Give me sudo access and I will set it all up the same way I had mine setup.
If you want to save yourself some bandwidth, there are already images you can copy out of my homedir on xentac's box. That way you can just update them as usual. I can also do this setup (or give you sudo... if jason doesn't mind) if you don't have time or whatever, just let me know. -S
participants (4)
-
Aaron Griffin
-
Jason Chu
-
Simo Leone
-
Travis Willard