All of lore.kernel.org
 help / color / mirror / Atom feed
From: Michal Marek <mmarek@suse.cz>
To: Ilya Dryomov <idryomov@gmail.com>
Cc: Alexei Starovoitov <alexei.starovoitov@gmail.com>,
	linux-kbuild@vger.kernel.org,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] deb-pkg: Fix for relative paths
Date: Wed, 18 Jun 2014 13:08:55 +0200	[thread overview]
Message-ID: <53A17347.9010607@suse.cz> (raw)
In-Reply-To: <CAOi1vP8udouMMHLYUAFT6xo1nQu4RXJkbTBBjpwG3ivNHVWDVw@mail.gmail.com>

Dne 18.6.2014 09:52, Ilya Dryomov napsal(a):
> On Tue, Jun 17, 2014 at 6:47 AM, Alexei Starovoitov
> <alexei.starovoitov@gmail.com> wrote:
>> On Mon, Jun 16, 2014 at 7:18 AM, Michal Marek <mmarek@suse.cz> wrote:
>>> When $srctree or $objtree are relative paths, we cannot change directory
>>> and refer to them in the same subshell. Do the redirection outside of
>>> the subshell to fix this.
>>>
>>> Reported-by: Ilya Dryomov <idryomov@gmail.com>
>>> Signed-off-by: Michal Marek <mmarek@suse.cz>
>>> ---
>>>  scripts/package/builddeb | 10 +++++-----
>>>  1 file changed, 5 insertions(+), 5 deletions(-)
>>
>> this patch didn't help to fix the broken deb-pkg for me:
> 
> Alexei, you must have some other issue with your environment.  This
> patch fixes it for me, and in fact I had almost the exact same patch
> committed internally in the interim.  (I wanted to give Michal the
> opportunity to fix this perhaps in a more general way, since tar
> targets seems to misbehave too.)

So can I add your Tested-by: and send it to Linus? I haven't managed to
set up a debian building environment yesterday and I'm a bit busy today.

Thanks,
Michal


  reply	other threads:[~2014-06-18 11:08 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-15 10:51 Regression: make O=... deb-pkg broken in 3.16 Ilya Dryomov
2014-06-16  9:18 ` Michal Marek
2014-06-16 14:18 ` [PATCH] deb-pkg: Fix for relative paths Michal Marek
2014-06-17  2:47   ` Alexei Starovoitov
2014-06-18  7:52     ` Ilya Dryomov
2014-06-18 11:08       ` Michal Marek [this message]
2014-06-18 12:43         ` Ilya Dryomov

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=53A17347.9010607@suse.cz \
    --to=mmarek@suse.cz \
    --cc=alexei.starovoitov@gmail.com \
    --cc=idryomov@gmail.com \
    --cc=linux-kbuild@vger.kernel.org \
    --cc=linux-kernel@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 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.