From: "H. Peter Anvin" <hpa@zytor.com>
To: Sean <seanlkml@sympatico.ca>
Cc: David Kastrup <dak@gnu.org>, Junio C Hamano <gitster@pobox.com>,
git@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [ANNOUNCE] GIT 1.5.3
Date: Mon, 03 Sep 2007 08:46:51 +0100 [thread overview]
Message-ID: <46DBBBEB.6010701@zytor.com> (raw)
In-Reply-To: <20070902133803.1b46f599.seanlkml@sympatico.ca>
Sean wrote:
> On Sun, 02 Sep 2007 10:57:03 +0100
> "H. Peter Anvin" <hpa@zytor.com> wrote:
>
>> From the looks of it, there is still a git-p4, it just moved to contrib
>> and uses fast-import, so removing its rpm package was probably broken in
>> the first place.
>
> Hi Peter,
>
> Items in contrib aren't officially supported, so it doesn't sound like
> a good idea to offer installs for them. Of course, it might be a good
> idea to promote git-p4 up out of contrib and add it to the spec file.
Well, the old one was out of contrib, too. Maybe it should never have
been packaged up, but it was...
> As things stand now, do you get an error when trying to upgrade Git via
> yum? I'd have thought things would upgrade fine but leave the old git-p4
> rpm hanging around. Either way, the obsoletes line mentioned by David
> sounds like the right solution.
Yes, it gets an error, because all the git RPMs are tied together by
explicit version number and so can only be upgraded as a group.
> As an aside, when I sent the patch removing git-p4import from the spec
> file I mentioned that I had no way to test it and asked for testers.
> Git needs a spec file maintainer so that issues like this can be caught
> before release. Without a maintainer, it should probably be demoted
> to contrib itself.
Well, git on kernel.org (and many other places) critically depends on
rpms being available.
-hpa
next prev parent reply other threads:[~2007-09-03 7:48 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-02 6:31 [ANNOUNCE] GIT 1.5.3 Junio C Hamano
2007-09-02 6:34 ` A note from the maintainer Junio C Hamano
2007-09-02 6:58 ` [ANNOUNCE] GIT 1.5.3 H. Peter Anvin
2007-09-02 7:58 ` Junio C Hamano
2007-09-02 8:06 ` David Kastrup
2007-09-02 9:57 ` H. Peter Anvin
2007-09-02 17:38 ` Sean
2007-09-02 22:13 ` Junio C Hamano
2007-09-02 23:16 ` Sean
2007-09-03 0:19 ` Junio C Hamano
2007-09-03 7:51 ` H. Peter Anvin
2007-09-03 8:10 ` Junio C Hamano
2007-09-03 8:12 ` H. Peter Anvin
2007-09-03 8:35 ` Junio C Hamano
2007-09-03 8:47 ` H. Peter Anvin
2007-09-03 8:53 ` Junio C Hamano
2007-09-03 9:10 ` Junio C Hamano
2007-09-03 9:13 ` H. Peter Anvin
2007-09-03 11:32 ` Andreas Ericsson
2007-09-03 12:58 ` David Kastrup
2007-09-03 13:02 ` Andreas Ericsson
2007-09-03 13:17 ` David Kastrup
2007-09-03 7:46 ` H. Peter Anvin [this message]
2007-09-02 7:08 ` David Kastrup
2007-09-02 8:43 ` Arkadiusz Miskiewicz
2007-09-02 10:28 ` Alex Riesen
2007-09-02 10:59 ` Johannes Schindelin
2007-09-02 11:19 ` Alex Riesen
2007-09-02 12:36 ` Arkadiusz Miskiewicz
2007-09-02 15:12 ` Nicolas Vilz
2007-09-02 22:52 ` David Kågedal
2007-09-02 22:54 ` David Kågedal
2007-09-02 23:28 ` Junio C Hamano
2007-09-02 23:36 ` Steven Grimm
2007-09-03 0:03 ` Junio C Hamano
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=46DBBBEB.6010701@zytor.com \
--to=hpa@zytor.com \
--cc=dak@gnu.org \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=linux-kernel@vger.kernel.org \
--cc=seanlkml@sympatico.ca \
/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).