"James B. Byrne" <byrnejb@xxxxxxxxxxxxx> writes: > OS = CentOS-5.2 > perl = 5.8.8 > > I get git from the yum repository at kernel.org. Up until the most recent > update I had no problems. Now I am getting these dependency errors: > > Error: Missing Dependency: libcurl.so.4 is needed by package git > Error: Missing Dependency: perl(:MODULE_COMPAT_5.10.0) is needed by > package perl-Git > Error: Missing Dependency: libc.so.6(GLIBC_2.7) is needed by package git > Error: Missing Dependency: libexpat.so.1 is needed by package git > Error: Missing Dependency: libcrypto.so.7 is needed by package git As described in the announcement for 1.5.6.2, the machine at kernel.org I cut x86_64 RPM on switched to FC9 early this month, and I updated my personal bochs installation to FC9 to be consistent for producing i386 RPMs. By the way, these RPMs are not in any way official. I have been guessing (without even bothering to confirm) that even for FC, distro people do not use the RPM packages I have at kernel.org, but they build and distribute their own to their users. I could stop generating these RPMs, in other words, but I've been doing this forever and they are still produced as courtesy, even though I am not a FC user myself. You could send a preconfigured CentOS 5.2 box to me and ask me to produce yet another set of RPMs. The release procedure already takes long enough time out of my git day, however, and I doubt I can afford the time to do so in practice, without reducing the time I spend on other git activities such as reviewing and accepting changes from others or writing patches myself. People on other platforms like Debian, Macintosh, and Windows (Cygwin and Msys) generate their own packages from the official tarballs and distribute the result to help other users on their platforms. Perhaps you and other CentOS users can get together and do the same to help each other? That would be a great help to the community. Thanks. -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
