From: "Catalin Marinas" <catalin.marinas@gmail.com>
To: "Jakub Narebski" <jnareb@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 15:02:21 +0000 [thread overview]
Message-ID: <b0943d9e0712110702m170ba227g2d2224f4f6af3cf0@mail.gmail.com> (raw)
In-Reply-To: <m3r6hts2yk.fsf@roke.D-201>
On 11/12/2007, Jakub Narebski <jnareb@gmail.com> wrote:
> $ rpm -Uhv --test stgit-0.14-1.noarch.rpm
> error: Failed dependencies:
> python(abi) = 2.5 is needed by stgit-0.14-1.noarch
I use Ubuntu 7.10, not the best system for building RPMs.
> Although I guess that it is something that rpmbuild sets (if not set)
> automatically during building.
Yes. If you know what to add to setup.py, please let me know.
> I'll just download SRPMS (which is available, just not linked from
> download area on homepage).
It's not linked as I always thought people would use the .tar.gz.
What about adding it to cheeseshop.python.org and only run
"easy_install stgit"? The drawback of easy_install is that there is no
easy_uninstall yet.
> P.S. By the way: [application/x-wais-source]?
I don't control the web server my ISP provides. I should move
everything to gna.org but I was too lazy to modify my release script
(for Debian, gna.org even gives information on how to set up an apt
repository).
--
Catalin
next prev parent reply other threads:[~2007-12-11 15:02 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
2007-12-11 15:02 ` Catalin Marinas [this message]
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=b0943d9e0712110702m170ba227g2d2224f4f6af3cf0@mail.gmail.com \
--to=catalin.marinas@gmail.com \
--cc=git@vger.kernel.org \
--cc=jnareb@gmail.com \
--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 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).