From: maximilian attems <max@stro.at>
To: Michal Marek <mmarek@suse.cz>
Cc: linux-kbuild@vger.kernel.org
Subject: Re: [PATCH] kbuild, deb-pkg: Fix build with paranoid umask
Date: Fri, 12 Nov 2010 18:46:53 +0100 [thread overview]
Message-ID: <20101112174653.GB30094@stro.at> (raw)
In-Reply-To: <20101111153725.GA7979@sepie.suse.cz>
On Thu, 11 Nov 2010, Michal Marek wrote:
> On Fri, Oct 29, 2010 at 03:55:50PM +0200, maximilian attems wrote:
> > umask 077
> > make deb-pkg
> > <snipp ..>
> > dpkg-deb: building package `linux-image-2.6.36+' in `../linux-image-2.6.36+_2.6.36+-4_amd64.deb'.
> > dpkg-deb: control directory has bad permissions 700 (must be >=0755 and <=0775)
> > make[1]: *** [deb-pkg] Error 2
> >
> > Reported-by: Bastian Blank <waldi@debian.org>
> > Signed-off-by: maximilian attems <max@stro.at>
> > ---
> > scripts/package/builddeb | 6 ++++--
> > 1 files changed, 4 insertions(+), 2 deletions(-)
>
> Thanks, applied.
>
thanks, don't see it yet in linux-next, care to push it out?
what about the other 2 cross compile deb-pkg patches?
or is that above still slated for .37?
--
maks
prev parent reply other threads:[~2010-11-12 17:46 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-29 13:55 [PATCH] kbuild, deb-pkg: Fix build with paranoid umask maximilian attems
2010-11-11 15:37 ` Michal Marek
2010-11-12 17:46 ` maximilian attems [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=20101112174653.GB30094@stro.at \
--to=max@stro.at \
--cc=linux-kbuild@vger.kernel.org \
--cc=mmarek@suse.cz \
/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