From: "Steven R. Wright" <srw6666@gmail.com>
To: linux-kernel@vger.kernel.org
Subject: make-kpkg target failing for v3.1
Date: Mon, 24 Oct 2011 14:04:31 -0500 [thread overview]
Message-ID: <4EA5B6BF.8030908@gmail.com> (raw)
while trying to build kernel v3.1 today, i ran into this error:
****************************************
create_md5sums_fn () { cd $1 ; find . -type f ! -regex './DEBIAN/.*' !
-regex './var/.*' -printf '%P\0' | xargs -r0 md5sum >
DEBIAN/md5sums ; if [ -z "DEBIAN/md5sums" ] ; then rm -f
"DEBIAN/md5sums" ; fi ; } ; create_md5sums_fn
/usr/src/linux-3.1/debian/linux-image-3.1.0
chmod -R og=rX /usr/src/linux-3.1/debian/linux-image-3.1.0
chown -R root:root /usr/src/linux-3.1/debian/linux-image-3.1.0
dpkg --build
/usr/src/linux-3.1/debian/linux-image-3.1.0 ..
dpkg-deb: error: control directory has bad permissions 2755 (must be
>=0755 and <=0775)
make[2]: *** [debian/stamp/binary/linux-image-3.1.0] Error 2
make[2]: Leaving directory `/usr/src/linux-3.1'
make[1]: *** [debian/stamp/binary/pre-linux-image-3.1.0] Error 2
make[1]: Leaving directory `/usr/src/linux-3.1'
make: *** [kernel_image] Error 2
****************************************
i have not encountered this error building the kernel in v3.0.4 and
before (i generally build and install most of the new stable releases,
and have done so since v.2.4). the command i used, and always have, was:
make-kpkg --initrd --rootcmd fakeroot kernel_image
there is a difference in the perms in a 3.1 build tree vs. a 3.0.4 tree
#52 decca:/usr/src/linux-3.1/debian
> ls -l | egrep "^d"
drwxr-sr-x 2 root root 4096 Nov 18 2010 Config
drwxr-sr-x 3 root root 4096 Nov 18 2010 docs
drwxr-sr-x 3 root root 4096 Nov 18 2010 examples
drwxr-sr-x 7 root root 4096 Oct 24 13:55 linux-image-3.1.0
drwxr-sr-x 7 root root 4096 Mar 17 2010 pkg
drwxr-sr-x 2 root root 4096 Nov 18 2010 po
drwxr-sr-x 6 root root 4096 Nov 18 2010 ruleset
drwxr-sr-x 2 root root 4096 Nov 18 2010 scripts
drwxr-sr-x 6 root src 4096 Oct 24 13:55 stamp
#64 decca:/usr/src/linux-3.0.4/debian
> ls -l | egrep "^d"
drwxr-xr-x 2 root root 4096 Nov 18 2010 Config
drwxr-xr-x 3 root root 4096 Nov 18 2010 docs
drwxr-xr-x 3 root root 4096 Nov 18 2010 examples
drwxr-xr-x 7 root root 4096 Aug 30 11:37 linux-image-3.0.4
drwxr-xr-x 7 root root 4096 Mar 17 2010 pkg
drwxr-xr-x 2 root root 4096 Nov 18 2010 po
drwxr-xr-x 6 root root 4096 Nov 18 2010 ruleset
drwxr-xr-x 2 root root 4096 Nov 18 2010 scripts
drwxr-xr-x 6 root root 4096 Aug 30 11:37 stamp
while it certainly *looks* like the "chmod og=rX" should take place in
the 3.0.4 build process, the directory does not reflect it, and the
dpkg-deb process is content and completes.
sRw
next reply other threads:[~2011-10-24 19:04 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-24 19:04 Steven R. Wright [this message]
2011-10-24 19:21 ` make-kpkg target failing for v3.1 Sven Joachim
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=4EA5B6BF.8030908@gmail.com \
--to=srw6666@gmail.com \
--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.