From: Jakub Narebski <jnareb@gmail.com>
To: "Catalin Marinas" <catalin.marinas@gmail.com>
Cc: "Karl Hasselström" <kha@treskal.com>,
"Git Mailing List" <git@vger.kernel.org>
Subject: Re: [PATCH] Fix typo: we require Python 2.4, not 2.5
Date: Tue, 11 Dec 2007 06:47:38 -0800 (PST) [thread overview]
Message-ID: <m3r6hts2yk.fsf@roke.D-201> (raw)
In-Reply-To: <b0943d9e0712110627g70ad0aecyfeaafd8b8655fb57@mail.gmail.com>
"Catalin Marinas" <catalin.marinas@gmail.com> writes:
> On 11/12/2007, Karl Hasselström <kha@treskal.com> wrote:
> > On 2007-12-10 11:40:41 +0000, Catalin Marinas wrote:
> >
> > > This release requires at least Python 2.4 and GIT 1.5.2.
> >
> > Yeah. So 0.14.1 (to be released very soon) should probably have this
> > fix. :-)
>
> Oops, I did some tests and forgot to revert it to 2.4. This would only
> affect people using the source tarball. The rpm and deb packages
> should be fine.
Hmmm...
$ rpm -Uhv --test stgit-0.14-1.noarch.rpm
error: Failed dependencies:
python(abi) = 2.5 is needed by stgit-0.14-1.noarch
Although I guess that it is something that rpmbuild sets (if not set)
automatically during building.
I'll just download SRPMS (which is available, just not linked from
download area on homepage).
P.S. By the way: [application/x-wais-source]?
--
Jakub Narebski
Poland
ShadeHawk on #git
next prev parent reply other threads:[~2007-12-11 14:48 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-10 11:40 [ANNOUNCE] Stacked GIT 0.14 Catalin Marinas
2007-12-11 14:23 ` [PATCH] Fix typo: we require Python 2.4, not 2.5 Karl Hasselström
2007-12-11 14:27 ` Catalin Marinas
2007-12-11 14:47 ` Jakub Narebski [this message]
2007-12-11 15:02 ` Catalin Marinas
2007-12-11 15:03 ` Jakub Narebski
2007-12-11 15:06 ` Catalin Marinas
2007-12-11 15:01 ` Karl Hasselström
2007-12-11 15:03 ` Karl Hasselström
2007-12-12 14:04 ` Catalin Marinas
2007-12-12 15:07 ` Jakub Narebski
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=m3r6hts2yk.fsf@roke.D-201 \
--to=jnareb@gmail.com \
--cc=catalin.marinas@gmail.com \
--cc=git@vger.kernel.org \
--cc=kha@treskal.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.