public inbox for linux-kbuild@vger.kernel.org
 help / color / mirror / Atom feed
From: "Robert P. J. Day" <rpjday@crashcourse.ca>
To: kbuild devel list <linux-kbuild@vger.kernel.org>
Subject: packaging issues:  some serious, some not so serious
Date: Mon, 18 Feb 2008 11:35:30 -0500 (EST)	[thread overview]
Message-ID: <alpine.LFD.1.00.0802181054100.9323@localhost.localdomain> (raw)


  there are a few bugs in the packaging targets, both with local
packaging and remote packaging if you've used "O=" for your kernel
build.  first, let's consider local builds.

  consider the packaging makefile scripts/package/Makefile.  these
early lines look entirely superfluous (nothing uses the variable
TAR_IGNORE):

...
# Ignore the following files/directories during tar operation
TAR_IGNORE := --exclude SCCS --exclude BitKeeper --exclude .svn --exclude CVS
...

  next, related to my earlier email, if your kernel source happens to
be in its own filesystem so that there's a "lost+found" directory, any
"tar" operation is going to fail due to lack of permissions for that
directory:

$ make rpm-pkg
...
find: ./lost+found: Permission denied
...
tar: kernel-2.6.25rc200015g1309d4e/./lost+found: Cannot open:
Permission denied
tar: Error exit delayed from previous errors
make[1]: *** [rpm-pkg] Error 2
make: *** [rpm-pkg] Error 2
$

  it seems to be sufficient to apply the following patch:

diff --git a/scripts/package/Makefile b/scripts/package/Makefile
index 5e32607..d3307f1 100644
--- a/scripts/package/Makefile
+++ b/scripts/package/Makefile
@@ -39,7 +39,7 @@ $(objtree)/kernel.spec: $(MKSPEC) $(srctree)/Makefile
 rpm-pkg rpm: $(objtree)/kernel.spec FORCE
        $(MAKE) clean
        $(PREV) ln -sf $(srctree) $(KERNELPATH)
-       $(PREV) tar -cz $(RCS_TAR_IGNORE) -f $(KERNELPATH).tar.gz $(KERNELPATH)/.
+       $(PREV) tar -cz --exclude lost+found $(RCS_TAR_IGNORE) -f $(KERNELPATH).tar.gz $(KERNELPATH)/.
        $(PREV) rm $(KERNELPATH)

        set -e; \


but it's probable that a number of other operations need to take a
"lost+found" directory into account; that is, anything involving
"tar".

  observations on remote packaging to come.

rday
--


========================================================================
Robert P. J. Day
Linux Consulting, Training and Annoying Kernel Pedantry:
    Have classroom, will lecture.

http://crashcourse.ca                          Waterloo, Ontario, CANADA
========================================================================

             reply	other threads:[~2008-02-18 16:35 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-18 16:35 Robert P. J. Day [this message]
2008-02-18 18:17 ` packaging issues: some serious, some not so serious Sam Ravnborg
2008-02-18 18:20   ` Robert P. J. Day
2008-02-19  9:43   ` Robert P. J. Day
2008-02-19  9:52     ` Sam Ravnborg
2008-02-19 10:15       ` Robert P. J. Day
2008-02-19 11:49         ` Sam Ravnborg
2008-02-19 12:25           ` Robert P. J. Day
2008-02-19 13:13             ` Sam Ravnborg

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=alpine.LFD.1.00.0802181054100.9323@localhost.localdomain \
    --to=rpjday@crashcourse.ca \
    --cc=linux-kbuild@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