git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Kristian Høgsberg" <krh@redhat.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: Jay Soffian <jaysoffian@gmail.com>, git@vger.kernel.org
Subject: Re: [PATCH] Rename git-core rpm to just git and rename the meta-pacakge to git-all.
Date: Mon, 18 Feb 2008 14:00:47 -0500	[thread overview]
Message-ID: <1203361247.4082.8.camel@gaara.boston.redhat.com> (raw)
In-Reply-To: <7v7ih2p0wk.fsf@gitster.siamese.dyndns.org>


On Mon, 2008-02-18 at 10:36 -0800, Junio C Hamano wrote:
> 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

  reply	other threads:[~2008-02-18 19:31 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-15 18:29 [PATCH] Rename git-core rpm to just git and rename the meta-pacakge to git-all Kristian Høgsberg
2008-02-15 19:36 ` Jakub Narebski
2008-02-15 21:08 ` Andreas Ericsson
2008-02-15 21:37   ` Kristian Høgsberg
2008-02-16  8:45 ` Junio C Hamano
2008-02-17  7:57 ` Junio C Hamano
2008-02-18 14:51   ` Jay Soffian
2008-02-18 16:04     ` Kristian Høgsberg
2008-02-18 18:36       ` Junio C Hamano
2008-02-18 19:00         ` Kristian Høgsberg [this message]
2008-02-19  1:25         ` Kristian Høgsberg

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1203361247.4082.8.camel@gaara.boston.redhat.com \
    --to=krh@redhat.com \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=jaysoffian@gmail.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.
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 NNTP newsgroup(s).