All of lore.kernel.org
 help / color / mirror / Atom feed
From: Michal Marek <mmarek@suse.cz>
To: Christoph Lameter <cl@linux.com>
Cc: Vince Weaver <vincent.weaver@maine.edu>,
	linux-kernel@vger.kernel.org, Jason Cooper <jason@lakedaemon.net>,
	Grant Likely <grant.likely@linaro.org>,
	Russell King <linux@arm.linux.org.uk>,
	Rob Herring <robh+dt@kernel.org>
Subject: Re: [bisected] broken make-kpkg kernel build in 3.15-rc1
Date: Tue, 15 Apr 2014 18:57:52 +0200	[thread overview]
Message-ID: <534D6510.3070509@suse.cz> (raw)
In-Reply-To: <alpine.DEB.2.10.1404151146530.26562@gentwo.org>

On 2014-04-15 18:49, Christoph Lameter wrote:
> On Tue, 15 Apr 2014, Michal Marek wrote:
> 
>> I fail to see how the above commit is responsible for this. make install
>> starts /sbin/installkernel and the rest is the job of this script. To
>> me, it looks more like a fakeroot failure than a bug in make install.
> 
> The problem is that the kernel build process should not write to anything
> in the /etc/apt directory.

Again: make install starts /sbin/installkernel and the rest is the job
of this script. Which means you need to debug Debian's
/sbin/installkernel why it suddenly wants to modify files in /etc/apt.

Michal

  reply	other threads:[~2014-04-15 16:57 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-15 13:43 [bisected] broken make-kpkg kernel build in 3.15-rc1 Vince Weaver
2014-04-15 15:03 ` Michal Marek
2014-04-15 16:49   ` Christoph Lameter
2014-04-15 16:57     ` Michal Marek [this message]
2014-04-15 17:22       ` Christoph Lameter
2014-04-15 18:26         ` Russell King - ARM Linux
2014-04-15 19:10           ` Vince Weaver
2014-04-15 19:28             ` Vince Weaver
2014-04-15 19:30             ` Vince Weaver
2014-04-15 19:31               ` Russell King - ARM Linux
2014-04-15 19:39                 ` Vince Weaver
2014-04-15 19:43                   ` Russell King - ARM Linux
2014-04-15 19:56                     ` Christoph Lameter
2014-04-15 19:37               ` Vince Weaver
2014-04-15 19:47             ` Christoph Lameter

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=534D6510.3070509@suse.cz \
    --to=mmarek@suse.cz \
    --cc=cl@linux.com \
    --cc=grant.likely@linaro.org \
    --cc=jason@lakedaemon.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@arm.linux.org.uk \
    --cc=robh+dt@kernel.org \
    --cc=vincent.weaver@maine.edu \
    /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.