[6 5 stable] Install git update from PPA, not from source
Created by: phieber
Merge request reports
Activity
Created by: arif-ali
The git PPA doesn't work on debian.
You need to do the following instead:
codename=`lsb_release -c | awk '{print $2}'` cat > /etc/apt/sources.list.d/backports.list << EOF deb http://ftp.debian.org/debian $codename-backports main EOF apt-get update apt-get -t $codename-backports install gitBy Administrator on 2014-01-24T10:49:46 (imported from GitLab project)
By Administrator on 2014-01-24T10:49:46 (imported from GitLab)
Created by: tuminoid
There is no way to have a clean install guide if you start listing backport/PPA guides for different distros. Installing from source works almost equally for all distros. Advanced users know how to replace it with something suitable for their distro.
By Administrator on 2014-01-24T10:53:50 (imported from GitLab project)
By Administrator on 2014-01-24T10:53:50 (imported from GitLab)
Created by: arif-ali
The point was that if you wanted to start working with PPAs, then the howto is supposed to be for both ubuntu and debian, so the only way to get debian working in the same way was with backports, and therefore we have different docs for both dists then.
Source compilation will work with every distro
agree with @jvanbaarsen and @tuminoid
By Administrator on 2014-01-24T10:59:56 (imported from GitLab project)
By Administrator on 2014-01-24T10:59:56 (imported from GitLab)
Created by: mmoll
I'm all in for using packages instead of compiling (and also using git from backports on Debian wheezy and the system ruby1.9 from the system package in my installations), but the instructions would need to be really generic.
By Administrator on 2014-01-24T11:30:30 (imported from GitLab project)
By Administrator on 2014-01-24T11:30:30 (imported from GitLab)
Created by: arif-ali
@mmoll, but then if we do write docs, for PPA and backports, we will need separate for debian, and separate for ubuntu. I thought this doc was supposed to fit both ubuntu and debian, and be generic at the same time?
By Administrator on 2014-01-24T11:33:35 (imported from GitLab project)
By Administrator on 2014-01-24T11:33:35 (imported from GitLab)
Created by: jvanbaarsen
@arif-ali Yeah you're right. The docs are supposed to fit both
By Administrator on 2014-01-24T11:45:18 (imported from GitLab project)
By Administrator on 2014-01-24T11:45:18 (imported from GitLab)
Created by: arif-ali
If needs be, maybe a new doc can be done in gitlab-recipes, concentrating on how we can achieve an installation using package managers, and not using the source
just an idea;
then people can choose
By Administrator on 2014-01-24T11:49:11 (imported from GitLab project)
By Administrator on 2014-01-24T11:49:11 (imported from GitLab)
Created by: jerbob92
I suggest providing the PPA as an alternative to compiling from source in the documentation. PPA is easier and faster to update, plus it also provides you with updates.
By Administrator on 2014-01-24T13:21:58 (imported from GitLab project)
By Administrator on 2014-01-24T13:21:58 (imported from GitLab)
Created by: jvanbaarsen
@jerbob92 That means a new doc to maintain?
By Administrator on 2014-01-24T13:23:48 (imported from GitLab project)
By Administrator on 2014-01-24T13:23:48 (imported from GitLab)
Created by: jerbob92
@jvanbaarsen Why not add it in the current doc as an alternative for compiling?
By Administrator on 2014-01-24T13:37:35 (imported from GitLab project)
By Administrator on 2014-01-24T13:37:35 (imported from GitLab)
Created by: jvanbaarsen
@jerbob92 I think the docs will just get messy, but that my opinion :-)
By Administrator on 2014-01-24T14:39:13 (imported from GitLab project)
By Administrator on 2014-01-24T14:39:13 (imported from GitLab)
Created by: wsouto
I might add that "add-apt-repository" not always work out-of-box depending on firewall/proxy configurations one may have in the internal network. I myself faced this problem and even with everything else that is "apt" related working normally I could not get "add-apt-repository" to work behind my company firewall and or proxy. The workaround is to create the list file and download and add the key manually. Sysadmins just tells me that I'm not supposed to use Linux here.
I think most of the Gitlab installations are in company's internal network and it could be an issue. Or not...
By Administrator on 2014-01-24T15:15:21 (imported from GitLab project)
By Administrator on 2014-01-24T15:15:21 (imported from GitLab)
Created by: jvanbaarsen
@razer6 What is the opinion on this by the core team?
By Administrator on 2014-02-10T18:38:16 (imported from GitLab project)
By Administrator on 2014-02-10T18:38:16 (imported from GitLab)
