You do not need to download CentOS development tools or yum. If you look at the guide you'll need cvs and ccmake.

To download those, use apt-get. See below:

sudo apt-get update && sudo apt-get install cvs cmake-curses-gui

I found both cvs and ccmake applications by searching the cache for the repositories:

1. sudo apt-get update gets the latest version of the applications in the repositories. No need to do this if you've already installed the applications with the command I provided above.
   

2. apt-cache search <package name> to search for a specific application that are available in the repositories you have in your repository list.

See more with man apt-cache and man apt-get.

In your console output it says: Maybe run: yum groups mark install (see man yum)—did you do this?

Try running the following commands:

yum groups mark install "Development Tools"
yum groups mark convert "Development Tools"
yum groupinstall "Development Tools"

Reference: RedHat Customer Portal discussion

Beware that RPM/yum packages rarely work properly on Ubuntu/Debian systems.

If you want to try it anyway, you can use the alien tool to convert the RPM into a DEB, then you can use dpkg or gdebi-gtk to install it. The homepage of alien is http://kitenet.net/~joey/code/alien/ and you can install it with apt-get install alien.

Edit: why do you want to use the RPM package given that you can install stress and stressapptest from the Ubuntu repositories?

would this break/make the system unstable in any way?

If you need software that is only available in a certain repo, I'd probably go with it. Just make sure you actually need it first.

The problems come into the picture when the repo's/rpms are poorly designed. This can lead to situations where yum will install a higher version of a particular package because it's available in the other repo under the same name but then some software from the base channel won't install anymore because it was built against an earlier version number. This can create a clusterfrack of a problem that is usually not intuitively solved or backed out from.

If you use anything other than EPEL, I would just configure the repo with enabled=0 so that the repo is disabled in general but if you need it you can just say yum install packageName --enablerepo=repoName. This prevents something from that repo getting installed accidentally.

Of course, there's also the issue that base channel packages are definitionally more stable than the latest and greatest just because of the QA that's done on them and the breadth of their install base.

So I was wondering if I install git 1.9 first [...] and the do the yum groupinstall "Development Tools" would this result in conflict issues of some sort.

Potentially, you just kind of have to see what it does. Ultimately, it's up to the repo maintainer to make sure the people using their repositories have the smoothest ride possible so it's hard to tell what you're going to get once you get away from the better known repositories.

I would do the development tools first adding a --disablerepo=repoName to it so that gets installed and just hope that the repo maintainer used that as their reference point when deciding how to build these RPM's. That seems like the thing that would have the best chance of success. A groupinstall will include more packages (directly and for dependencies) than installing a particular application from will. So if something from the base channel conflicts with the unofficial repo's RPM it should be easier to piecemeal it and remove the base channel packages.

I'm trying to be very cautious here because it's the server the entire team will be using, and don't have the option to create a snapshot to roll back in case something happens...

If that's the case, I would carefully look over the updates list with each update and make sure they're coming from the correct repositories before you tell it to proceed with the installation.

So, two things...

One: Certificate based repositories are a function of "subscription_manager" while "RHN Classic" is the traditional RHN. First you need to know which type your system is using. If it's "certificate-based repositories" (aka subscription_manager) then you'll see the file /etc/yum.repos.d/redhat.repo with content like:

[rhel-6-server-rpms]
name = Red Hat Enterprise Linux 6 Server (RPMs)
baseurl = https://cdn.redhat.com/content/rhel/server/6/$releasever/$basearch/os
enabled = 0
gpgcheck = 1
gpgkey = file:///etc/pki/rpm-gpg/RPM-GPG-KEY-redhat-beta,file:///etc/pki/rpm-gpg/RPM-GPG-KEY-redhat-release
sslverify = 1
sslcacert = /etc/rhsm/ca/redhat-uep.pem
sslclientkey = /etc/pki/entitlement/1111111111111111111-key.pem
sslclientcert = /etc/pki/entitlement/1111111111111111111.pem
metadata_expire = 86400

If this is the case you're likely using subscription_manager, if on the other hand you have a file located at: /etc/sysconfig/rhn/systemid then the system has been registered via "RHN Classic". Regardless, whichever method you have used, the other one should be turned off. This can be done by configuring the corresponding plugin's config located in: /etc/yum/pluginconf.d/

For "RHN Classic" this will be the file "rhnplugin.conf" and for "subscription_manager" it will be "subscription-manager.conf". These are enabled/disabled by setting the boolean value "enabled=[0|1]" in the corresponding configuration file. If you have neither of these configurations then your system is not registered via RHN/subscription_manager and despite having local administration privileges you should contact your sysadmin who is in control of your RHN entitlements. If you are registered, let's keep going.

Once you have disabled the plugin you have chosen not to use, verify that you can see the groups available and no error messages via the command:

yum grouplist

or, even better:

yum grouplist | grep -i development 

this should yield output similar to:

redbeard@yum01 [~]# yum grouplist | grep -i development
   Additional Development
   Desktop Platform Development
   Development tools
   Server Platform Development

You'll notice that the name "Development tools" has a lowercase initial character in the second word. I did validate that this should work regardless of case.

redbeard@yum01 [~]# sudo yum groupinstall "Development Tools"
Loaded plugins: product-id, security, subscription-manager
This system is receiving updates from Red Hat Subscription Management.
Setting up Group Process
Package 1:pkgconfig-0.23-9.1.el6.x86_64 already installed and latest version
Package binutils-2.20.51.0.2-5.36.el6.x86_64 already installed and latest version
Package elfutils-0.152-1.el6.x86_64 already installed and latest version
Resolving Dependencies
--> Running transaction check
---> Package autoconf.noarch 0:2.63-5.1.el6 will be installed
---> Package automake.noarch 0:1.11.1-4.el6 will be installed
---> Package bison.x86_64 0:2.4.1-5.el6 will be installed
---> Package byacc.x86_64 0:1.9.20070509-7.el6 will be installed
---> Package cscope.x86_64 0:15.6-6.el6 will be installed
---> Package ctags.x86_64 0:5.8-2.el6 will be installed
....

You can use the yum grouplist command e.g.

yum grouplist Dev* installed  ...
Installed Groups:
   Development tools
Done

You need to install gcc or if you have it installed, you need to add it to the $PATH.