Junio C Hamano wrote:
Assuming that we do not give the old git-p4import script
packaged in "git-p4 package", would the following patch be all
that is needed, or do we need other things in the spec file?
-- snipsnap clipcrap --
+Obsoletes: git-p4
That depends. If packages outside of git
Junio C Hamano wrote:
"H. Peter Anvin" <[EMAIL PROTECTED]> writes:
Sean wrote:
Given the comment from David, I suspect your patch is all
that's needed; hopefully Peter can give it a quick test.
It sounds like it; I don't know how to test it other than placing in
the repository and try to
"H. Peter Anvin" <[EMAIL PROTECTED]> writes:
> Sean wrote:
>>
>> Given the comment from David, I suspect your patch is all
>> that's needed; hopefully Peter can give it a quick test.
>
> It sounds like it; I don't know how to test it other than placing in
> the repository and try to upgrade. It
Sean wrote:
Given the comment from David, I suspect your patch is all
that's needed; hopefully Peter can give it a quick test.
It sounds like it; I don't know how to test it other than placing in the
repository and try to upgrade. It can't be any worse, so I don't see
any harm in just
Sean wrote:
On Sun, 02 Sep 2007 10:57:03 +0100
"H. Peter Anvin" <[EMAIL PROTECTED]> 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
Sean wrote:
On Sun, 02 Sep 2007 10:57:03 +0100
H. Peter Anvin [EMAIL PROTECTED] 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
Sean wrote:
Given the comment from David, I suspect your patch is all
that's needed; hopefully Peter can give it a quick test.
It sounds like it; I don't know how to test it other than placing in the
repository and try to upgrade. It can't be any worse, so I don't see
any harm in just
H. Peter Anvin [EMAIL PROTECTED] writes:
Sean wrote:
Given the comment from David, I suspect your patch is all
that's needed; hopefully Peter can give it a quick test.
It sounds like it; I don't know how to test it other than placing in
the repository and try to upgrade. It can't be any
Junio C Hamano wrote:
H. Peter Anvin [EMAIL PROTECTED] writes:
Sean wrote:
Given the comment from David, I suspect your patch is all
that's needed; hopefully Peter can give it a quick test.
It sounds like it; I don't know how to test it other than placing in
the repository and try to
Junio C Hamano wrote:
Assuming that we do not give the old git-p4import script
packaged in git-p4 package, would the following patch be all
that is needed, or do we need other things in the spec file?
-- snipsnap clipcrap --
+Obsoletes: git-p4
That depends. If packages outside of git
Sean <[EMAIL PROTECTED]> writes:
> On Sun, 02 Sep 2007 15:13:09 -0700
> Junio C Hamano <[EMAIL PROTECTED]> wrote:
> ...
>> For majority of general public, I thought the spec file _I_
>> ship, along with RPM files _I_ build, are contrib status
>> already. Don't distro people do their own RPM
On Sun, 02 Sep 2007 15:13:09 -0700
Junio C Hamano <[EMAIL PROTECTED]> wrote:
Hi Junio,
> For majority of general public, I thought the spec file _I_
> ship, along with RPM files _I_ build, are contrib status
> already. Don't distro people do their own RPM packages, instead
> of using what I
Sean <[EMAIL PROTECTED]> writes:
> On Sun, 02 Sep 2007 10:57:03 +0100
> "H. Peter Anvin" <[EMAIL PROTECTED]> 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.
> ...
On Sun, 02 Sep 2007 10:57:03 +0100
"H. Peter Anvin" <[EMAIL PROTECTED]> 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
Arkadiusz Miskiewicz, Sun, Sep 02, 2007 10:43:38 +0200:
> *** t0001-init.sh ***
> * FAIL 1: plain
>
> (
> unset GIT_DIR GIT_WORK_TREE &&
> mkdir plain &&
> cd plain &&
> git init
>
David Kastrup wrote:
"H. Peter Anvin" <[EMAIL PROTECTED]> writes:
Junio C Hamano wrote:
* For people who need to import from Perforce, a front-end for
fast-import is in contrib/fast-import/.
There seems to be an issue with this and RPMS.
In particular, there is no longer a git-p4 RPMS,
"H. Peter Anvin" <[EMAIL PROTECTED]> writes:
> Junio C Hamano wrote:
>>
>> * For people who need to import from Perforce, a front-end for
>> fast-import is in contrib/fast-import/.
>>
>
> There seems to be an issue with this and RPMS.
>
> In particular, there is no longer a git-p4 RPMS, which
"H. Peter Anvin" <[EMAIL PROTECTED]> writes:
> Junio C Hamano wrote:
>>
>> * For people who need to import from Perforce, a front-end for
>> fast-import is in contrib/fast-import/.
>
> There seems to be an issue with this and RPMS.
>
> In particular, there is no longer a git-p4 RPMS, which
Junio C Hamano wrote:
* For people who need to import from Perforce, a front-end for
fast-import is in contrib/fast-import/.
There seems to be an issue with this and RPMS.
In particular, there is no longer a git-p4 RPMS, which prevents git from
getting upgraded at all by yum.
Anyone
The latest feature release GIT 1.5.3 is available at the usual
places:
http://www.kernel.org/pub/software/scm/git/
git-1.5.3.tar.{gz,bz2}(tarball)
git-htmldocs-1.5.3.tar.{gz,bz2} (preformatted docs)
git-manpages-1.5.3.tar.{gz,bz2}
The latest feature release GIT 1.5.3 is available at the usual
places:
http://www.kernel.org/pub/software/scm/git/
git-1.5.3.tar.{gz,bz2}(tarball)
git-htmldocs-1.5.3.tar.{gz,bz2} (preformatted docs)
git-manpages-1.5.3.tar.{gz,bz2}
Junio C Hamano wrote:
* For people who need to import from Perforce, a front-end for
fast-import is in contrib/fast-import/.
There seems to be an issue with this and RPMS.
In particular, there is no longer a git-p4 RPMS, which prevents git from
getting upgraded at all by yum.
Anyone
H. Peter Anvin [EMAIL PROTECTED] writes:
Junio C Hamano wrote:
* For people who need to import from Perforce, a front-end for
fast-import is in contrib/fast-import/.
There seems to be an issue with this and RPMS.
In particular, there is no longer a git-p4 RPMS, which prevents git
from
H. Peter Anvin [EMAIL PROTECTED] writes:
Junio C Hamano wrote:
* For people who need to import from Perforce, a front-end for
fast-import is in contrib/fast-import/.
There seems to be an issue with this and RPMS.
In particular, there is no longer a git-p4 RPMS, which prevents git
from
On Sun, 02 Sep 2007 10:57:03 +0100
H. Peter Anvin [EMAIL PROTECTED] 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
Sean [EMAIL PROTECTED] writes:
On Sun, 02 Sep 2007 10:57:03 +0100
H. Peter Anvin [EMAIL PROTECTED] 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.
...
As an aside,
On Sun, 02 Sep 2007 15:13:09 -0700
Junio C Hamano [EMAIL PROTECTED] wrote:
Hi Junio,
For majority of general public, I thought the spec file _I_
ship, along with RPM files _I_ build, are contrib status
already. Don't distro people do their own RPM packages, instead
of using what I placed on
Sean [EMAIL PROTECTED] writes:
On Sun, 02 Sep 2007 15:13:09 -0700
Junio C Hamano [EMAIL PROTECTED] wrote:
...
For majority of general public, I thought the spec file _I_
ship, along with RPM files _I_ build, are contrib status
already. Don't distro people do their own RPM packages, instead
28 matches
Mail list logo