Bug 793634 wanted to update gecko to use gtk-2.18/glib-2.22. This is only available on the newer CentOS 6 builders. Bug 794285 has temporarily lowered the gtk version back to what it was, but we should really upgrade and be in sync asap. We therefore need to upgrade the SeaMonkey builders to CentOS 6. Also this blocks Bug 794772 - Port |Bug 713802 - Build with GIO support (and drop GnomeVFS)|.

Adding Bug 798921 as dependency so that we remember to remove the workaround (CentOS 6 uses binutils 2.20.51 as far as I see this).

Is there a timeframe for when this is expected to be done?

Ok, what's blocking the migration to CentOS 6? How could I help? On my private CentOS 6 (vm-)machines building SeaMonkey with gstreamer and pulseaudio enabled seems to work without problems: http://l10n.mozilla-community.org/~akalla/unofficial/seamonkey/nightly/

Ok, got a chunk done on the machine-side today. https://etherpad.mozilla.org/seamonkey-hp-puppet-setup tracks the work. (I'll dump specifics here as I go, since etherpads are not ephemeral) Update puppetmaster node def to toplevel::base for i in {2..13}; do ssh root@sea-hp-linux64-$i.community.scl3.mozilla.com; done Fix /etc/resolv.conf # Generated by NetworkManager nameserver 8.8.8.8 domain community.scl3.mozilla.com # EDIT /etc/sysconfig/network-scripts/ifcfg-eth0 to add GATEWAY # EDIT /etc/sysconfig/network for fqdn mv ./deploypass{,.old} # Remove old deploypass sudo reboot ==== PUPPET_SERVER=sea-puppet.community.scl3.mozilla.com ./puppetize.sh enter deploy password # puppet agent --test --environment=jwood --server=sea-puppet.community.scl3.mozilla.com puppet agent --test --server=sea-puppet.community.scl3.mozilla.com Update puppetmaster node def to toplevel::slave # puppet agent --test --environment=jwood --server=sea-puppet.community.scl3.mozilla.com puppet agent --test --server=sea-puppet.community.scl3.mozilla.com ====== FAILED ===== sea-hp-linux64-5 sea-hp-linux64-11 those 2 failed ones are not pingable atm, I'm *not* asking IT to restore them atm though. NOW :ewong is able to login to these hosts (and no longer restricted to a password only available to moco releng), and buildbot is installed. Still need to get everything setup for parity and do some slight tweaks to the puppet config, but we're pretty close to useable

This has a rough urgency for SeaMonkey since it is half responsible for blocking our Gecko 31 release. This patch adds support for toplevel::slave::releng::build, with a small piece thrown in for mock support. The changes are, roughly: * Adding support for SeaMonkey key management ** this is based on a slavealloc-like file created in /etc/hiera/fake_slavealloc.eyaml with manually set values (since SeaMonkey doesn't have slavealloc) but I felt this was the best design for keys. ** This also adds a fake_slavealloc extsync thing. * Change some easily-fixed uses of cltbld/seabld * Changes to hard-to-fix uses of cltbld/seabld in runner ** This was because runner files were hardcoded in files/ but used cltbld directly ** I fixed by moving all runner files to templates/tasks/ and changed the code to use them as content source from there, rather than as a direct flat source. * Related changes to seamonkey-nodes.pp and seamonkey-config.pp

Comment on attachment 8458425 [details] [diff] [review] [puppetAgain] part 1 - support seamonkey with toplevel::slave::releng::build Review of attachment 8458425 [details] [diff] [review]: ----------------------------------------------------------------- I'm sure you could fix the Windows 'cltbld' instance too, while you're at it (bug 1040555).

(In reply to Dustin J. Mitchell [:dustin] from comment #6) > Comment on attachment 8458425 [details] [diff] [review] > [puppetAgain] part 1 - support seamonkey with toplevel::slave::releng::build > > Review of attachment 8458425 [details] [diff] [review]: > ----------------------------------------------------------------- > > I'm sure you could fix the Windows 'cltbld' instance too, while you're at it > (bug 1040555). I didn't do this since I had no way to test it, I *suspect* its that easy, but low priority for me given I don't have a machine to use it on atm.

I think we can officially call this FIXED, since SeaMonkey 2.29 was released based on builds from these hosts.