# GIT Packages for Debian Etch 10 messages from 2007-06-18 to 2007-06-18. Participants: Thomas Glanzmann, Pierre Habouzit, Carlo Wood, Christoph Lameter, Roland Dreier. Thread: https://gitlist.dev/t/8641 ## Thomas Glanzmann, 2007-06-18 21:25 Subject: GIT Packages for Debian Etch Message-ID: <20070618212524.GC16393@cip.informatik.uni-erlangen.de> URL: https://gitlist.dev/e/20070618212524.GC16393%40cip.informatik.uni-erlangen.de ``` 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 ``` ## Pierre Habouzit, 2007-06-18 21:27 Subject: Re: GIT Packages for Debian Etch Message-ID: <20070618212741.GA5938@artemis.internal.dc7.debconf.org> URL: https://gitlist.dev/e/20070618212741.GA5938%40artemis.internal.dc7.debconf.org In-Reply-To: <20070618212524.GC16393@cip.informatik.uni-erlangen.de> ``` On Mon, Jun 18, 2007 at 11:25:24PM +0200, Thomas Glanzmann wrote: > 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/ ./ FWIW there is even simpler: I maintain a backport on www.backports.org. Which is a semi-official service driven by Debian Developers. Cheers, -- ·O· Pierre Habouzit ··O madcoder@debian.org OOO http://www.madism.org ``` ## Thomas Glanzmann, 2007-06-18 21:34 Subject: Re: GIT Packages for Debian Etch Message-ID: <20070618213458.GD16393@cip.informatik.uni-erlangen.de> URL: https://gitlist.dev/e/20070618213458.GD16393%40cip.informatik.uni-erlangen.de In-Reply-To: <20070618212741.GA5938@artemis.internal.dc7.debconf.org> ``` Hello Pierre, > FWIW there is even simpler: I maintain a backport on > www.backports.org. Which is a semi-official service driven by Debian > Developers. good to know, maybe I am going to use backports in the future. Thomas ``` ## Carlo Wood, 2007-06-18 21:48 Subject: Re: GIT Packages for Debian Etch Message-ID: <20070618214852.GA13538@alinoe.com> URL: https://gitlist.dev/e/20070618214852.GA13538%40alinoe.com In-Reply-To: <20070618212741.GA5938@artemis.internal.dc7.debconf.org> ``` On Mon, Jun 18, 2007 at 10:27:41PM +0100, Pierre Habouzit wrote: > FWIW there is even simpler: I maintain a backport on > www.backports.org. Which is a semi-official service driven by Debian > Developers. It seems that this is only for etch (and sarge). I run a mixed Lenny/sid machine here. It doesn't necessarily work when I start to install things for etch. Certainly not once testing upgrades its libc. Or? -- Carlo Wood ``` ## Thomas Glanzmann, 2007-06-18 21:56 Subject: Re: GIT Packages for Debian Etch Message-ID: <20070618215610.GG16393@cip.informatik.uni-erlangen.de> URL: https://gitlist.dev/e/20070618215610.GG16393%40cip.informatik.uni-erlangen.de In-Reply-To: <20070618214852.GA13538@alinoe.com> ``` Hello, > It seems that this is only for etch (and sarge). I run a mixed > Lenny/sid machine here. It doesn't necessarily work when I start to > install things for etch. Certainly not once testing upgrades its libc. > Or? true. But when you run sid you get a newer version of git automatically. Sooner or later. And you can always build it yourself. It's a pain in the ass until you have all build dependencies installed and all the tests pass. Most of them you can get by typing: apt-get build-dep git-core But after that it is very straight forward. Thomas ``` ## Thomas Glanzmann, 2007-06-18 22:03 Subject: Re: GIT Packages for Debian Etch Message-ID: <20070618220356.GI16393@cip.informatik.uni-erlangen.de> URL: https://gitlist.dev/e/20070618220356.GI16393%40cip.informatik.uni-erlangen.de In-Reply-To: <20070618215610.GG16393@cip.informatik.uni-erlangen.de> ``` Hello, * Thomas Glanzmann [070618 23:56]: > > It seems that this is only for etch (and sarge). I run a mixed > > Lenny/sid machine here. It doesn't necessarily work when I start to > > install things for etch. Certainly not once testing upgrades its libc. > > Or? > true. I guess not so true. Because debian had always compatibility libs. So I guess when they bump the libc revision on sid, they provide a compat library at the same time so that you're able to run the old binaries. But don't nail me down on this one. But for the mean time you should be good with the packages I provided in the previous e-mail for sure. Thomas ``` ## Carlo Wood, 2007-06-18 22:04 Subject: Re: GIT Packages for Debian Etch Message-ID: <20070618220441.GC13538@alinoe.com> URL: https://gitlist.dev/e/20070618220441.GC13538%40alinoe.com In-Reply-To: <20070618215610.GG16393@cip.informatik.uni-erlangen.de> ``` On Mon, Jun 18, 2007 at 11:56:10PM +0200, Thomas Glanzmann wrote: > true. But when you run sid you get a newer version of git automatically. > Sooner or later. And you can always build it yourself. It's a pain in > the ass until you have all build dependencies installed and all the > tests pass. Oh, I already build it before my previous post :p I just did: sudo apt-get install libz-dev asciidoc xmlto libexpat1-dev subversion unzip tcl8.4 libsvn-perl libcurl3-dev after having a peek at git-core_1.5.2.1-1.dsc, and then it did build just fine immediately. -- Carlo Wood ``` ## Thomas Glanzmann, 2007-06-18 22:08 Subject: Re: GIT Packages for Debian Etch Message-ID: <20070618220824.GJ16393@cip.informatik.uni-erlangen.de> URL: https://gitlist.dev/e/20070618220824.GJ16393%40cip.informatik.uni-erlangen.de In-Reply-To: <20070618220441.GC13538@alinoe.com> ``` Hello, > after having a peek at git-core_1.5.2.1-1.dsc, and then it did build > just fine immediately. good point, that makes sense. I have to keep that in mind. Last time I looked at the failed tests, saw the missing dependency and tried again. :-) Thomas ``` ## Christoph Lameter, 2007-06-18 23:18 Subject: Re: GIT Packages for Debian Etch Message-ID: URL: https://gitlist.dev/e/Pine.LNX.4.64.0706181617060.18601%40schroedinger.engr.sgi.com In-Reply-To: <20070618212524.GC16393@cip.informatik.uni-erlangen.de> ``` On Mon, 18 Jun 2007, Thomas Glanzmann wrote: > 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: Is there some way you can feed that into Debian please? Why the go around through a separate repository? The maintainer of git-core is not actively maintaining the package? ``` ## Roland Dreier, 2007-06-18 23:36 Subject: Re: GIT Packages for Debian Etch Message-ID: URL: https://gitlist.dev/e/adavedkesx3.fsf%40cisco.com In-Reply-To: ``` > Is there some way you can feed that into Debian please? Why the go around > through a separate repository? The maintainer of git-core is not actively > maintaining the package? No. The current version of git in Debian is 1.5.2.1, a little out of date from the current 1.5.2.2 but not too bad. However, Debian Etch was already released with an older version of git. Debian testing/Lenny (the next release, which is still being developed) does not have the latest version of git yet because it is blocked waiting for the next version of curl as well as a few other problems. - R. ```