Re: [PATCH] Rename git-core rpm to just git and rename the meta-pacakge to git-all.
- From
Kristian Høgsberg <krh@redhat.com>
- Date
- Feb 18, 2008, 19:00 UTC
- Message-ID
- <1203361247.4082.8.camel@gaara.boston.redhat.com>
- In-Reply-To
- <7v7ih2p0wk.fsf@gitster.siamese.dyndns.org>
On Mon, 2008-02-18 at 10:36 -0800, Junio C Hamano wrote:
Show 26 quoted lines
> Kristian Høgsberg <krh@redhat.com> writes:
>
> > On Mon, 2008-02-18 at 09:51 -0500, Jay Soffian wrote:
> >> On Feb 17, 2008 2:57 AM, Junio C Hamano <gitster@pobox.com> wrote:
> >>
> >> > "yum install git" and "yum install git-core" do not give such an
> >> > error but the latter gives quite a bunch of errors ("yum install
> >> > git" goes alright). This is problem #2.
> >>
> >> You probably want "yum upgrade git-core".
> >>
> >> The "problem" is that yum by default doesn't process RPM renames (obsoletes)
> >> unless you either have obsoletes=1 in your yum.conf, use "yum --obsoletes
> >> update" or use "yum upgrade".
> >
> > Ah, that's what it is. Thanks, I wasn't aware of this issue.
>
> Does that mean that the test I did and the problem I saw were
> end-user errors and that there is no proble with your patch and
> I can use it as-is to cut 1.5.4.3 and future ones?
>
> That's a great news.
>
> But perhaps we would need some description/warning to help end
> users as clueless as I am with respect to yum in the release
> notes and/or announcements?We could, but could you provide a little more detail about the system you tested on? I have
obsoletes=1
in my /etc/yum.conf, which has been default in Fedora since October 2004.
> Could you resend the patch with a commit log message that I can > later reuse parts from for such a purpose, with a sign-off > please?
Yup, I'm getting a new patch together to address the comments from your earlier mail. Also, I had the git-all package in there, but it turns out that without a %files section, rpm doesn't create the rpm. New patch coming up in a few minutes.
Kristian