From: "David S. Miller" <davem@davemloft.net>
To: rayl@mail.com
Cc: git@vger.kernel.org
Subject: Re: non-trivial merge failures
Date: Sun, 20 Nov 2005 20:17:12 -0800 (PST) [thread overview]
Message-ID: <20051120.201712.32582587.davem@davemloft.net> (raw)
In-Reply-To: <20051120221922.GB29291@mail.com>
From: Ray Lehtiniemi <rayl@mail.com>
Date: Sun, 20 Nov 2005 15:19:22 -0700
> On Sun, Nov 20, 2005 at 01:49:45PM -0800, David S. Miller wrote:
> >
> > It looks like it's failing to import some python module called
> > "subprocess", and I aparently don't have that installed.
> > /usr/bin/python on this Debian box is aparently python-2.3, do
> > I need to be using python-2.4 for this merge stuff to work?
>
> Define WITH_OWN_SUBPROCESS_PY in Makefile to install a copy of
> this module.
How about a version check at build or "make test" time so we can get a
sensible failure diagnostic instead of a weird cryptic "subprocess
import failure" when Python is too old? :-)
At least some better behavior than what we have now, where "make test"
still passes when you have this problem.
prev parent reply other threads:[~2005-11-21 4:16 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-20 21:49 non-trivial merge failures David S. Miller
2005-11-20 21:51 ` Ismail Donmez
2005-11-20 23:39 ` Johannes Schindelin
2005-11-21 4:15 ` David S. Miller
2005-11-20 23:07 ` Ryan Anderson
2005-11-21 4:20 ` David S. Miller
[not found] ` <11325498823557-git-send-email-ryan@michonline.com>
2005-11-21 5:31 ` [PATCH] Add Python version checks to the Makefile to automatically set WITH_OWN_SUBPROCESS_PY David S. Miller
2005-11-21 8:26 ` Johannes Schindelin
[not found] ` <20051120221922.GB29291@mail.com>
2005-11-21 4:17 ` David S. Miller [this message]
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=20051120.201712.32582587.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=git@vger.kernel.org \
--cc=rayl@mail.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