{"thread":{"id":"8641","subject":"GIT Packages for Debian Etch","startedAt":"2007-06-18T21:25:24Z","lastAt":"2007-06-18T23:36:56Z","messageCount":10,"participants":["Thomas Glanzmann","Pierre Habouzit","Carlo Wood","Christoph Lameter","Roland Dreier"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"45283","messageId":"20070618212524.GC16393@cip.informatik.uni-erlangen.de","threadId":"8641","inReplyTo":null,"subject":"GIT Packages for Debian Etch","fromName":"Thomas Glanzmann","fromEmail":"thomas@glanzmann.de","sentAt":"2007-06-18T21:25:24Z","receivedAt":"2007-06-18T21:25:24Z","isPatch":false,"sender":{"key":"thomas@glanzmann.de","avatar":null},"body":"Hello,\na friend of mine always builds the Debian Packages from unstable for\nDebian Etch. I have on all my machines the following line in\n/etc/apt/sources.list:\n\n deb http://rmdir.de/~michael/git/ ./\n\napt-get update; apt-get dist-upgrade\n\nand you're up2speed.\n\nIf you don't trust that packages it is very easy to build them yourself:\n\n wget http://ftp.debian.org/debian/pool/main/g/git-core/git-core_1.5.2.1-1.dsc\n wget http://ftp.debian.org/debian/pool/main/g/git-core/git-core_1.5.2.1.orig.tar.gz\n wget http://ftp.debian.org/debian/pool/main/g/git-core/git-core_1.5.2.1-1.diff.gz\n dpkg-source -x git-core_1.5.2.1-1.dsc\n cd git-core-1.5.2.1/\n fakeroot debian/rules binary\n\nIt runs the whole test suite and only contiues producing debs if they're good\nto go. It might be possible that you have to install some build dependencies by\nyourself. If some new git version hits unstable you can get the references for\nthe three files above from:\n\n http://packages.debian.org/git-core\n => unstable\n => scroll to end of page\n => Source Packages\n => Source Package: git-core, Download: [dsc] ...\n\n Thomas\n"},{"id":"45284","messageId":"20070618212741.GA5938@artemis.internal.dc7.debconf.org","threadId":"8641","inReplyTo":"20070618212524.GC16393@cip.informatik.uni-erlangen.de","subject":"Re: GIT Packages for Debian Etch","fromName":"Pierre Habouzit","fromEmail":"madcoder@debian.org","sentAt":"2007-06-18T21:27:41Z","receivedAt":"2007-06-18T21:27:41Z","isPatch":false,"sender":{"key":"madcoder@debian.org","avatar":"https://avatars.githubusercontent.com/u/44708?v=4"},"body":"On Mon, Jun 18, 2007 at 11:25:24PM +0200, Thomas Glanzmann wrote:\n> Hello,\n> a friend of mine always builds the Debian Packages from unstable for\n> Debian Etch. I have on all my machines the following line in\n> /etc/apt/sources.list:\n> \n> deb http://rmdir.de/~michael/git/ ./\n\n FWIW there is even simpler: I maintain a backport on\nwww.backports.org. Which is a semi-official service driven by Debian\nDevelopers.\n\nCheers,\n-- \n·O· Pierre Habouzit\n··O madcoder@debian.org\nOOO http://www.madism.org\n"},{"id":"45288","messageId":"20070618213458.GD16393@cip.informatik.uni-erlangen.de","threadId":"8641","inReplyTo":"20070618212741.GA5938@artemis.internal.dc7.debconf.org","subject":"Re: GIT Packages for Debian Etch","fromName":"Thomas Glanzmann","fromEmail":"thomas@glanzmann.de","sentAt":"2007-06-18T21:34:59Z","receivedAt":"2007-06-18T21:34:59Z","isPatch":false,"sender":{"key":"thomas@glanzmann.de","avatar":null},"body":"Hello Pierre,\n\n> FWIW there is even simpler: I maintain a backport on\n> www.backports.org. Which is a semi-official service driven by Debian\n> Developers.\n\ngood to know, maybe I am going to use backports in the future.\n\n Thomas\n"},{"id":"45290","messageId":"20070618214852.GA13538@alinoe.com","threadId":"8641","inReplyTo":"20070618212741.GA5938@artemis.internal.dc7.debconf.org","subject":"Re: GIT Packages for Debian Etch","fromName":"Carlo Wood","fromEmail":"carlo@alinoe.com","sentAt":"2007-06-18T21:48:52Z","receivedAt":"2007-06-18T21:48:52Z","isPatch":false,"sender":{"key":"carlo@alinoe.com","avatar":"https://gravatar.com/avatar/f9ef6306f40295ad6047a49139a3e240d5c297092eafab3da2e34416ba1193d9?d=mp&s=160"},"body":"On Mon, Jun 18, 2007 at 10:27:41PM +0100, Pierre Habouzit wrote:\n> FWIW there is even simpler: I maintain a backport on\n> www.backports.org. Which is a semi-official service driven by Debian\n> Developers.\n\nIt seems that this is only for etch (and sarge).\nI run a mixed Lenny/sid machine here. It doesn't necessarily\nwork when I start to install things for etch. Certainly not\nonce testing upgrades its libc. Or?\n\n-- \nCarlo Wood \n"},{"id":"45292","messageId":"20070618215610.GG16393@cip.informatik.uni-erlangen.de","threadId":"8641","inReplyTo":"20070618214852.GA13538@alinoe.com","subject":"Re: GIT Packages for Debian Etch","fromName":"Thomas Glanzmann","fromEmail":"thomas@glanzmann.de","sentAt":"2007-06-18T21:56:10Z","receivedAt":"2007-06-18T21:56:10Z","isPatch":false,"sender":{"key":"thomas@glanzmann.de","avatar":null},"body":"Hello,\n\n> It seems that this is only for etch (and sarge). I run a mixed\n> Lenny/sid machine here. It doesn't necessarily work when I start to\n> install things for etch. Certainly not once testing upgrades its libc.\n> Or?\n\ntrue. But when you run sid you get a newer version of git automatically.\nSooner or later. And you can always build it yourself. It's a pain in\nthe ass until you have all build dependencies installed and all the\ntests pass. Most of them you can get by typing:\n\n apt-get build-dep git-core\n\nBut after that it is very straight forward.\n\n Thomas\n"},{"id":"45293","messageId":"20070618220356.GI16393@cip.informatik.uni-erlangen.de","threadId":"8641","inReplyTo":"20070618215610.GG16393@cip.informatik.uni-erlangen.de","subject":"Re: GIT Packages for Debian Etch","fromName":"Thomas Glanzmann","fromEmail":"thomas@glanzmann.de","sentAt":"2007-06-18T22:03:56Z","receivedAt":"2007-06-18T22:03:56Z","isPatch":false,"sender":{"key":"thomas@glanzmann.de","avatar":null},"body":"Hello,\n\n* Thomas Glanzmann [070618 23:56]:\n> > It seems that this is only for etch (and sarge). I run a mixed\n> > Lenny/sid machine here. It doesn't necessarily work when I start to\n> > install things for etch. Certainly not once testing upgrades its libc.\n> > Or?\n\n> true.\n\nI guess not so true. Because debian had always compatibility libs. So I\nguess when they bump the libc revision on sid, they provide a compat\nlibrary at the same time so that you're able to run the old binaries.\nBut don't nail me down on this one. But for the mean time you should be\ngood with the packages I provided in the previous e-mail for sure.\n\n Thomas\n"},{"id":"45294","messageId":"20070618220441.GC13538@alinoe.com","threadId":"8641","inReplyTo":"20070618215610.GG16393@cip.informatik.uni-erlangen.de","subject":"Re: GIT Packages for Debian Etch","fromName":"Carlo Wood","fromEmail":"carlo@alinoe.com","sentAt":"2007-06-18T22:04:41Z","receivedAt":"2007-06-18T22:04:41Z","isPatch":false,"sender":{"key":"carlo@alinoe.com","avatar":"https://gravatar.com/avatar/f9ef6306f40295ad6047a49139a3e240d5c297092eafab3da2e34416ba1193d9?d=mp&s=160"},"body":"On Mon, Jun 18, 2007 at 11:56:10PM +0200, Thomas Glanzmann wrote:\n> true. But when you run sid you get a newer version of git automatically.\n> Sooner or later. And you can always build it yourself. It's a pain in\n> the ass until you have all build dependencies installed and all the\n> tests pass.\n\nOh, I already build it before my previous post :p\n\nI just did:\n\nsudo apt-get install libz-dev asciidoc xmlto libexpat1-dev subversion unzip tcl8.4 libsvn-perl libcurl3-dev\n\nafter having a peek at git-core_1.5.2.1-1.dsc, and then it did build\njust fine immediately.\n\n-- \nCarlo Wood \n"},{"id":"45295","messageId":"20070618220824.GJ16393@cip.informatik.uni-erlangen.de","threadId":"8641","inReplyTo":"20070618220441.GC13538@alinoe.com","subject":"Re: GIT Packages for Debian Etch","fromName":"Thomas Glanzmann","fromEmail":"thomas@glanzmann.de","sentAt":"2007-06-18T22:08:24Z","receivedAt":"2007-06-18T22:08:24Z","isPatch":false,"sender":{"key":"thomas@glanzmann.de","avatar":null},"body":"Hello,\n\n> after having a peek at git-core_1.5.2.1-1.dsc, and then it did build\n> just fine immediately.\n\ngood point, that makes sense. I have to keep that in mind. Last time I\nlooked at the failed tests, saw the missing dependency and tried again.\n:-)\n\n Thomas\n"},{"id":"45298","messageId":"Pine.LNX.4.64.0706181617060.18601@schroedinger.engr.sgi.com","threadId":"8641","inReplyTo":"20070618212524.GC16393@cip.informatik.uni-erlangen.de","subject":"Re: GIT Packages for Debian Etch","fromName":"Christoph Lameter","fromEmail":"clameter@sgi.com","sentAt":"2007-06-18T23:18:32Z","receivedAt":"2007-06-18T23:18:32Z","isPatch":false,"sender":{"key":"clameter@sgi.com","avatar":null},"body":"On Mon, 18 Jun 2007, Thomas Glanzmann wrote:\n\n> Hello,\n> a friend of mine always builds the Debian Packages from unstable for\n> Debian Etch. I have on all my machines the following line in\n> /etc/apt/sources.list:\n> \n> deb http://rmdir.de/~michael/git/ ./\n> \n> apt-get update; apt-get dist-upgrade\n> \n> and you're up2speed.\n> \n> If you don't trust that packages it is very easy to build them yourself:\n\nIs there some way you can feed that into Debian please? Why the go around \nthrough a separate repository? The maintainer of git-core is not actively \nmaintaining the package?\n"},{"id":"45299","messageId":"adavedkesx3.fsf@cisco.com","threadId":"8641","inReplyTo":"Pine.LNX.4.64.0706181617060.18601@schroedinger.engr.sgi.com","subject":"Re: GIT Packages for Debian Etch","fromName":"Roland Dreier","fromEmail":"rdreier@cisco.com","sentAt":"2007-06-18T23:36:56Z","receivedAt":"2007-06-18T23:36:56Z","isPatch":false,"sender":{"key":"rdreier@cisco.com","avatar":null},"body":" > Is there some way you can feed that into Debian please? Why the go around \n > through a separate repository? The maintainer of git-core is not actively \n > maintaining the package?\n\nNo. The current version of git in Debian is 1.5.2.1, a little out of\ndate from the current 1.5.2.2 but not too bad. However, Debian Etch\nwas already released with an older version of git. Debian\ntesting/Lenny (the next release, which is still being developed) does\nnot have the latest version of git yet because it is blocked waiting\nfor the next version of curl as well as a few other problems.\n\n - R.\n"}]}