From: "Øyvind A. Holm" <sunny@sunbase.org>
To: David Turner <dturner@twopensource.com>
Cc: "git@vger.kernel.org" <git@vger.kernel.org>
Subject: Re: t5150-request-pull.sh fails on newest master in Debian
Date: Sat, 5 Jul 2014 16:24:52 +0200 [thread overview]
Message-ID: <CAA787rnMonCuON+C0U5FDXKzjTBdpOusCpGLeWytDWaA1torEw@mail.gmail.com> (raw)
In-Reply-To: <1404525502.3109.25.camel@stross>
On 5 July 2014 03:58, David Turner <dturner@twopensource.com> wrote:
> On Sat, 2014-07-05 at 02:09 +0200, Øyvind A. Holm wrote:
> <snip>
> > The test works. Seems as there's something fishy about the use of
> > --prefix in this specific commit (v2.0.1-472-g6f92e5f).
>
> Ok, now I can reproduce on my linode box (haven't tried it locally
> yet). I'll try to get a fix up once I figure out what's up.
Awesome. I've done some more "./configure --prefix" testing, and this is
the result:
# --prefix is set to non-existing directory
./configure --prefix=/usr/local/varprg/git.master.v2.0.1-472-g6f92e5f
# ./t5150-request-pull.sh fails.
# --prefix is set to non-existing directory, use trailing slash
./configure --prefix=/usr/local/varprg/git.master.v2.0.1-472-g6f92e5f/
# ./t5150-request-pull.sh fails.
# --prefix is set to existing directory
./configure --prefix=/usr/local/varprg/git.master.v2.0.1-442-g7fe6834
# ./t5150-request-pull.sh fails.
# --prefix is set to existing directory
./configure --prefix=/usr/local
# ./t5150-request-pull.sh succeeds.
# --prefix is set to existing directory
./configure --prefix=/usr/local/varprg
# ./t5150-request-pull.sh succeeds.
# --prefix is set to non-existing directory
./configure --prefix=/usr/local/varprg/a-long-directory-name-which-does-not-exist
# ./t5150-request-pull.sh succeeds.
./configure --prefix=/usr/local/varprg/git.master.a-long-directory-name-which-does-not-exist
# ./t5150-request-pull.sh succeeds.
So it's something with names like "git.master.v2.0.1-472-g6f92e5f" that
"./configure --prefix" is picky about.
When testing this last night, I pushed the following branches to
<https://github.com/sunny256/git> where I added all compiled files in
various stages with "git add -f .":
t5150-fail.configure-without-prefix
Succeeds.
"./configure"
t5150-fail.configure-with-prefix
Fails.
"./configure --prefix=/usr/local/varprg/git.master.v2.0.1-472-g6f92e5f"
t5150-fail.configure-prefix-usr-local
Succeeds.
"./configure --prefix=/usr/local"
Maybe something will turn up by diffing those branches. I've got to
leave for now, but will have a look at this later tonight.
Cheers,
Øyvind
next prev parent reply other threads:[~2014-07-05 14:25 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-03 21:55 t5150-request-pull.sh fails on newest master in Debian Øyvind A. Holm
2014-07-03 22:16 ` David Turner
[not found] ` <CAA787rmroFsjk9=ar0e_4o3hUpfDBi+9J4nrNyHHMZq-5q4skw@mail.gmail.com>
2014-07-03 23:02 ` Øyvind A. Holm
2014-07-03 22:19 ` Øyvind A. Holm
2014-07-04 20:22 ` David Turner
2014-07-05 0:09 ` Øyvind A. Holm
2014-07-05 1:58 ` David Turner
2014-07-05 14:24 ` Øyvind A. Holm [this message]
2014-07-05 19:00 ` [PATCH] refs.c: handle REFNAME_REFSPEC_PATTERN at end of page David Turner
[not found] ` <xmqq7g3pdoy7.fsf@gitster.dls.corp.google.com>
2014-07-09 11:48 ` Øyvind A. Holm
2014-07-09 0:52 ` t5150-request-pull.sh fails on newest master in Debian Øyvind A. Holm
2014-07-09 1:18 ` David Turner
2014-07-09 11:44 ` Øyvind A. Holm
2014-07-09 14:52 ` René Scharfe
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=CAA787rnMonCuON+C0U5FDXKzjTBdpOusCpGLeWytDWaA1torEw@mail.gmail.com \
--to=sunny@sunbase.org \
--cc=dturner@twopensource.com \
--cc=git@vger.kernel.org \
/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).