OTOH I can't be bothered to mess with SELinux.
That is a very common sentiment. Although SELinux is a very powerful security tool in the right hands, it is also a bit of a pain to setup and one of the things most often disabled on Red Hat distros. Although I currently have SELinux enabled and using carefully crafted security policies on all of the RHEL/CentOS servers I administer, it has taken significant time investment to wrangle SELinux into doing what I want. I have never had any serious security breaches on any of my Red Hat or Debian machines, so I'm not convinced that SELinux is actually worth the effort.
Noted. I'm also a Debian fan, just thought some aspects of Ubuntu might be better automated.
As far as I know there is nothing in Ubuntu server that is particularly better automated than Debian. Most of Canonical's work for Ubuntu server has been in commercial support (and Landscape). If you are thinking "automated" as in automatic updates (which was what I originally thought you were referring to), you can configure automatic updates in Debian fairly easily. Automatic updates are not enabled by default in Debian for a good reason - most system administrators prefer to tightly control updates so that they can meet their uptime quotas.
All my *nix servers are arch based.
Just because arch is a fast rolling release does not mean you have to update all the packages or use the versions on the web, most server orientated packages are compiled and packaged by me, including the kernel.
I believe that I called your choice insane a few posts up. Are you running Arch on servers in a production environment, is this a testing/development environment, or is it just your personal server?