5 ms·

Does anyone maintain a relatively up to date Debian repo? I seem to be on 2.1.4. I'm a relatively light user and it's not a huge concern, but searching for 'd

by tomlong 11y ago

Does anyone maintain a relatively up to date Debian repo? I seem to be on 2.1.4. I'm a relatively light user and it's not a huge concern, but searching for 'debian git repo' yields more or less exactly what you would expect.

quarterto 11y ago
The answer seems to be "install it from the Ubuntu Precise repository": https://berezovskiy.me/2015/02/update-git-on-debian/ https://berezovskiy.me/2015/02/update-git-on-debian/
- 0x0 11y ago
  Installing libc6 from testing is scary advice. Then you're basically halfways to running testing overall. That may have security implications (there's been several DSAs for glibc), and traditionally it's also been a source of incompatibilities.
- martey 11y ago
  The instructions in that blog post look like a good way to break your system: https://wiki.debian.org/DontBreakDebian#Don.27t_make_a_FrankenDebian https://wiki.debian.org/DontBreakDebian#Don.27t_make_a_Frank...
mbrock 11y ago
The latest 2.8.0 release candidate is in testing, so you can try installing that with pinning.
- avar 11y ago
  This doesn't work with a lot of packages because they depend on some newer C library that would have to upgrade pretty much all of your installation from stable, but I've just tested this now and pinning "git git-svn git-email git-man" to testing/unstable on an otherwise stable distro works.
deleted 11y ago
[deleted]
caf 11y ago
The easiest way is probably just to build it from source in your home directory rather than installing it system-wide.
- dmm 11y ago
  This is the way to do it. Run "apt-get build-dep git" to install the build dependencies and the set "--prefix=$HOME/opt" or whatever on the configure script to control where it's installed. Installing parts of testing or ubuntu can serious mess up your system and have security consequences.
  - icebraining 11y ago
    You can also backport the package, it's usually rather easy; you should just need to add a deb-src line for the testing repository to sources.list and then run: apt-get update apt-get install build-essential fakeroot devscripts apt-get build-dep git apt-get -b source git The last line will download the source package and immediately compile it, generating a .deb file which you can then install: dpkg -i [package].deb
    - voltagex_ 11y ago
      It looks like git 2.8.0-rc3 is the newest in the Debian archives. https://tracker.debian.org/pkg/git https://tracker.debian.org/pkg/git will show when it's uploaded. It corresponds to commit 312e98e283ed7f62d72bb7ac07318285f1454c78 Author: Jonathan Nieder <jrn@google.com> Date: Wed Mar 16 18:28:22 2016 -0700 debian: new upstream release candidate Sidenote: I wonder how far I'd get simplifying the `devscripts` package/dependencies - your instructions will download 200+ megabytes of packages `--no-install-recommends` will do 160. Side sidenote: https://repo.or.cz/r/git/debian.git/ https://repo.or.cz/r/git/debian.git/ is listed as Debian's upstream source for git, yet it doesn't use a valid SSL certificate...
    - tomlong 11y ago
      I think this is the way I will go, thank you.
  - 11y ago
dklarsch 11y ago
That's the main reason I switched over to Arch Linux for development boxes. I was fed up with being stuck with 2 year old versions by default of everything on Debian/Ubuntu (git, gcc, cmake, valgrind, etc). Git is already flagged as out of date on Arch and will be updated to 2.8 within a matter of days.
- petepete 11y ago
  I pointed this out on r/debian and was downvoted to hell, but it's totally true.
  - profmonocle 11y ago
    Well, that's actually a selling point of Debian's stable releases - packages in the official repo are essentially frozen in time, and security updates/critical bug fixes get backported. It's great for stability, though not great if you like using the latest versions of your software. (As I do.)

by tomlong 11y ago

quarterto 11y ago

The answer seems to be "install it from the Ubuntu Precise repository": https://berezovskiy.me/2015/02/update-git-on-debian/ https://berezovskiy.me/2015/02/update-git-on-debian/

0x0 11y ago
Installing libc6 from testing is scary advice. Then you're basically halfways to running testing overall. That may have security implications (there's been several DSAs for glibc), and traditionally it's also been a source of incompatibilities.
martey 11y ago
The instructions in that blog post look like a good way to break your system: https://wiki.debian.org/DontBreakDebian#Don.27t_make_a_FrankenDebian https://wiki.debian.org/DontBreakDebian#Don.27t_make_a_Frank...

mbrock 11y ago

The latest 2.8.0 release candidate is in testing, so you can try installing that with pinning.

avar 11y ago
This doesn't work with a lot of packages because they depend on some newer C library that would have to upgrade pretty much all of your installation from stable, but I've just tested this now and pinning "git git-svn git-email git-man" to testing/unstable on an otherwise stable distro works.

deleted 11y ago

[deleted]

caf 11y ago

The easiest way is probably just to build it from source in your home directory rather than installing it system-wide.

dmm 11y ago
This is the way to do it. Run "apt-get build-dep git" to install the build dependencies and the set "--prefix=$HOME/opt" or whatever on the configure script to control where it's installed. Installing parts of testing or ubuntu can serious mess up your system and have security consequences.
- icebraining 11y ago
  You can also backport the package, it's usually rather easy; you should just need to add a deb-src line for the testing repository to sources.list and then run: apt-get update apt-get install build-essential fakeroot devscripts apt-get build-dep git apt-get -b source git The last line will download the source package and immediately compile it, generating a .deb file which you can then install: dpkg -i [package].deb
  - voltagex_ 11y ago
    It looks like git 2.8.0-rc3 is the newest in the Debian archives. https://tracker.debian.org/pkg/git https://tracker.debian.org/pkg/git will show when it's uploaded. It corresponds to commit 312e98e283ed7f62d72bb7ac07318285f1454c78 Author: Jonathan Nieder <jrn@google.com> Date: Wed Mar 16 18:28:22 2016 -0700 debian: new upstream release candidate Sidenote: I wonder how far I'd get simplifying the `devscripts` package/dependencies - your instructions will download 200+ megabytes of packages `--no-install-recommends` will do 160. Side sidenote: https://repo.or.cz/r/git/debian.git/ https://repo.or.cz/r/git/debian.git/ is listed as Debian's upstream source for git, yet it doesn't use a valid SSL certificate...
  - tomlong 11y ago
    I think this is the way I will go, thank you.
- 11y ago

dklarsch 11y ago

That's the main reason I switched over to Arch Linux for development boxes. I was fed up with being stuck with 2 year old versions by default of everything on Debian/Ubuntu (git, gcc, cmake, valgrind, etc). Git is already flagged as out of date on Arch and will be updated to 2.8 within a matter of days.

petepete 11y ago
I pointed this out on r/debian and was downvoted to hell, but it's totally true.
- profmonocle 11y ago
  Well, that's actually a selling point of Debian's stable releases - packages in the official repo are essentially frozen in time, and security updates/critical bug fixes get backported. It's great for stability, though not great if you like using the latest versions of your software. (As I do.)