Bug#429605: git-core: git 1.4.x is REALLY outdated (and has a proven bug in bisect)
On Tue, Jun 19, 2007 at 05:54:56PM +, Gerrit Pape wrote: Hi Carlo, we usually don't include new upstream versions into a Debian stable release. For some packages this might seem bad, for some it's definitely good. Overall it helps the quality of a Debian stable release during its lifetime. Well, there is nothing you can do about etch anymore anyway, my request was for 'testing'. The recent versions of git are included in the unstable distribution, and after some delay in the testing distribution too. Does there have to be a fixed delay? How is this delay determined? For users of the stable release, there's the backports.org service that provides new upstream versions to be installed on the stable release, see also this thread http://thread.gmane.org/gmane.comp.version-control.git/50411 I participated in that thread, as you can see :p -- Carlo Wood [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#429605: git-core: git 1.4.x is REALLY outdated (and has a proven bug in bisect)
On Tue, Jun 19, 2007 at 08:33:40PM +0200, Carlo Wood wrote: On Tue, Jun 19, 2007 at 05:54:56PM +, Gerrit Pape wrote: Hi Carlo, we usually don't include new upstream versions into a Debian stable release. For some packages this might seem bad, for some it's definitely good. Overall it helps the quality of a Debian stable release during its lifetime. Well, there is nothing you can do about etch anymore anyway, my request was for 'testing'. The recent versions of git are included in the unstable distribution, and after some delay in the testing distribution too. Does there have to be a fixed delay? How is this delay determined? The delay isn't fixed, but a minimum of 10, 5, or 2 days, depending on the importance of the upgrade. Sometimes it's longer though, in the case of git currently, it's a libcurl transition, and a problem with the parisc architecture, that keeps it out of testing. This will sort out eventually. In the meantime you should be able to install the git packages from unstable, or build suitable packages for your testing system yourself, e.g. # apt-get build-dep gitcore # apt-get -b source git-core For users of the stable release, there's the backports.org service that provides new upstream versions to be installed on the stable release, see also this thread http://thread.gmane.org/gmane.comp.version-control.git/50411 I participated in that thread, as you can see :p Ups, sorry ;). HTH, Gerrit. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#429605: git-core: git 1.4.x is REALLY outdated (and has a proven bug in bisect)
Package: git-core Version: 1:1.4.4.4-2 Severity: normal I am using Lenny, which still has git-core 1.4.4.4. After I ran into a very weird behaviour of 'git bisect' on the linux kernel, I had some correspondence with Linus Torvalds and he urged me to upgrade to 1.5. I did this, and the problem went away. Linus writes: On Tue, 19 Jun 2007, Carlo Wood wrote: Conclusion: the weird behaviour that you think was wrong is totally due to git 1.4.4.4. Ok. I'll bounce a note to Junio just due to curiosity in case he goes ahh, yeah, it was that known bug, but I'll otherwise ignore this. Git-1.5.x is such a radically better version (not because it fixes this bug, but because we fixed a number of other issues, notably some very basic usability things), that I think any git users should really upgrade to a newer version. IOW, there's simply no reason to stay on anything older (git has always been backwards compatible since very early on, so upgrading to a newer version of git won't break anything, although some of the new UI's might obviously cause you to do things differently). As Linus is the author of git - I'd like, in turn, urge the debian maintainers of git-core to upgrade to 1.5.x. 1.4.4.4 is REALLY too outdated to have ANY benefit whatsoever. It is not more stable or anything, it's just plain old, buggy and much worse to use. Nobody should be using it. -- System Information: Debian Release: lenny/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 2.6.22-rc4-hikaru-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages git-core depends on: ii libc6 2.5-9 GNU C Library: Shared libraries ii libcurl3-gnutls 7.15.5-1 Multi-protocol file transfer libra ii libdigest-sha1-perl 2.11-2 NIST SHA-1 message digest algorith ii liberror-perl 0.15-8 Perl module for error/exception ha ii libexpat1 1.95.8-3.4 XML parsing C library - runtime li ii perl-modules 5.8.8-7Core Perl modules ii zlib1g1:1.2.3-15 compression library - runtime Versions of packages git-core recommends: pn curl none (no description available) pn git-doc none (no description available) ii less 394-4 Pager program similar to more ii openssh-client [ssh-client] 1:4.3p2-9 Secure shell client, an rlogin/rsh ii patch 2.5.9-4Apply a diff file to an original ii rsync 2.6.9-3fast remote file copy program (lik -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
