From: Thomas Glanzmann <thomas@glanzmann.de>
To: carlo@alinoe.com, Linus Torvalds <torvalds@osdl.org>,
LKML <linux-kernel@vger.kernel.org>
Cc: Michael Gernoth <simigern@cip.informatik.uni-erlangen.de>,
GIT <git@vger.kernel.org>
Subject: GIT Packages for Debian Etch
Date: Mon, 18 Jun 2007 23:25:24 +0200 [thread overview]
Message-ID: <20070618212524.GC16393@cip.informatik.uni-erlangen.de> (raw)
Hello,
a friend of mine always builds the Debian Packages from unstable for
Debian Etch. I have on all my machines the following line in
/etc/apt/sources.list:
deb http://rmdir.de/~michael/git/ ./
apt-get update; apt-get dist-upgrade
and you're up2speed.
If you don't trust that packages it is very easy to build them yourself:
wget http://ftp.debian.org/debian/pool/main/g/git-core/git-core_1.5.2.1-1.dsc
wget http://ftp.debian.org/debian/pool/main/g/git-core/git-core_1.5.2.1.orig.tar.gz
wget http://ftp.debian.org/debian/pool/main/g/git-core/git-core_1.5.2.1-1.diff.gz
dpkg-source -x git-core_1.5.2.1-1.dsc
cd git-core-1.5.2.1/
fakeroot debian/rules binary
It runs the whole test suite and only contiues producing debs if they're good
to go. It might be possible that you have to install some build dependencies by
yourself. If some new git version hits unstable you can get the references for
the three files above from:
http://packages.debian.org/git-core
=> unstable
=> scroll to end of page
=> Source Packages
=> Source Package: git-core, Download: [dsc] ...
Thomas
next reply other threads:[~2007-06-18 21:25 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-18 21:25 Thomas Glanzmann [this message]
2007-06-18 21:27 ` GIT Packages for Debian Etch Pierre Habouzit
2007-06-18 21:34 ` Thomas Glanzmann
2007-06-18 21:48 ` Carlo Wood
2007-06-18 21:56 ` Thomas Glanzmann
2007-06-18 22:03 ` Thomas Glanzmann
2007-06-18 22:04 ` Carlo Wood
2007-06-18 22:08 ` Thomas Glanzmann
2007-06-18 23:18 ` Christoph Lameter
2007-06-18 23:36 ` Roland Dreier
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20070618212524.GC16393@cip.informatik.uni-erlangen.de \
--to=thomas@glanzmann.de \
--cc=carlo@alinoe.com \
--cc=git@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=simigern@cip.informatik.uni-erlangen.de \
--cc=torvalds@osdl.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).