From: "Roger C. Soares" <rogersoares@intelinet.com.br>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org
Subject: Re: [ANNOUNCE] GIT 1.5.4-rc3
Date: Sat, 12 Jan 2008 12:24:44 -0200 [thread overview]
Message-ID: <4788CDAC.5030409@intelinet.com.br> (raw)
In-Reply-To: <7vsl13wmas.fsf@gitster.siamese.dyndns.org>
Junio C Hamano escreveu:
> The third rc for the next feature release GIT 1.5.4 is available
> at the usual places:
>
> http://www.kernel.org/pub/software/scm/git/
>
> git-1.5.4.rc3.tar.{gz,bz2} (tarball)
> git-htmldocs-1.5.4.rc3.tar.{gz,bz2} (preformatted docs)
> git-manpages-1.5.4.rc3.tar.{gz,bz2} (preformatted docs)
> testing/git-*-1.5.4.rc3-1.$arch.rpm (RPM)
>
Don't know if you already have some recomendation for RHEL5 users, so
just reporting what I had to do to install the rpms.
To start, I already had git installed from EPEL.
Downloaded perl-Error from
http://dag.wieers.com/rpm/packages/perl-Error/ to satisfy dependencies.
There was another dependacy for git-arch I think, but as I don't need it
I just deleted this one.
When trying to install perl-Error it conflicted with perl-Git from EPEL.
I think they included perl-Error files inside their perl-Git rpm.
So, after uninstalling all git rpms from EPEL, installing perl-Error
from dag.wieers, the rc3 git rpms installed successfully.
[]s,
Roger.
next prev parent reply other threads:[~2008-01-12 14:25 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-12 7:11 [ANNOUNCE] GIT 1.5.4-rc3 Junio C Hamano
2008-01-12 7:26 ` Ismail Dönmez
2008-01-12 7:34 ` Junio C Hamano
2008-01-12 7:47 ` Ismail Dönmez
2008-01-12 8:04 ` Junio C Hamano
2008-01-12 9:04 ` Jeff King
2008-01-12 9:05 ` Jeff King
2008-01-12 11:10 ` valgrind test script integration Jeff King
2008-01-12 11:36 ` Jeff King
2008-01-12 17:10 ` Johannes Schindelin
2008-01-12 18:12 ` Jeff King
2008-01-12 13:01 ` [ANNOUNCE] GIT 1.5.4-rc3 René Scharfe
2008-01-12 13:10 ` Ismail Dönmez
2008-01-12 16:57 ` Johannes Schindelin
2008-01-12 18:09 ` Jeff King
2008-01-12 19:09 ` Junio C Hamano
2008-01-12 14:24 ` Roger C. Soares [this message]
2008-01-12 19:13 ` Junio C Hamano
[not found] ` <7vsl13wmas.fsf-jO8aZxhGsIagbBziECNbOZn29agUkmeCHZ5vskTnxNA@public.gmane.org>
2008-01-13 14:41 ` Steffen Prohaska
2008-01-21 2:37 ` [ANNOUNCE] GIT 1.5.4-rc4 Junio C Hamano
[not found] ` <7vsl0r3nvc.fsf-jO8aZxhGsIagbBziECNbOZn29agUkmeCHZ5vskTnxNA@public.gmane.org>
2008-01-21 22:22 ` Steffen Prohaska
[not found] ` <BB330DC7-9F38-4D41-85A2-D475701B6083-wjoc1KHpMeg@public.gmane.org>
2008-01-22 1:21 ` Johannes Schindelin
[not found] ` <alpine.LSU.1.00.0801220121300.5731-OGWIkrnhIhzN0uC3ymp8PA@public.gmane.org>
2008-01-22 5:50 ` Steffen Prohaska
2008-01-28 10:56 ` [ANNOUNCE] GIT 1.5.4-rc5 Junio C Hamano
2008-01-28 18:38 ` Jeff King
2008-01-29 0:36 ` Gustaf Hendeby
2008-01-29 1:25 ` Junio C Hamano
2008-01-29 1:29 ` Jeff King
2008-01-29 6:06 ` Steffen Prohaska
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4788CDAC.5030409@intelinet.com.br \
--to=rogersoares@intelinet.com.br \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
/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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).