From: Jan Dinger <jan.dinger@arcor.de>
To: linux-kernel@vger.kernel.org
Subject: Kernel 2.6.18-rc7 Debian
Date: Thu, 14 Sep 2006 12:11:04 +0200 [thread overview]
Message-ID: <45092AB8.2050401@arcor.de> (raw)
Hey,
Ill compiling my own kernel. i´ve downloaded the archive and unpacked
the archive.
This is my directory:
rwxrwsr-x 5 root src 4096 Sep 14 11:35 .
drwxr-xr-x 12 root root 4096 Jul 19 14:08 ..
drwxr-sr-x 2 root src 4096 Sep 14 11:54 kernel-patches
lrwxrwxrwx 1 root src 16 Sep 14 11:03 linux -> linux-2.6.18-rc7
drwxr-xr-x 19 root root 4096 Sep 14 11:36 linux-2.6.18-rc7
-rw-r--r-- 1 root root 52467944 Sep 14 09:22 linux-2.6.18-rc7.tar.gz
Ok,
#make menuconfug
success
Next i will create my debian-package and will include the new patch.
# make-kpkg kernel_image --revision=jan-1.0 --append_to_version jan-1.0
--added-patches=patch-2.6.18-rc7
The Error: debian/ruleset/misc/patches.mk:104: *** Could not find patch
for patch-2.6.18-rc7. Stop.
My patch is under /usr/src/kernel-patches/patch-2.6.18-rc7.
If i run the process without --added-patches, then i become this error:
====== making target configure-indep [new prereqs:
stamp-configure-indep]======
====== making target stamp-configure [new prereqs: configure-arch
configure-indep]======
Problems ecountered with the version number jan-1.0.
The upstream version jan does not contain a digit
Please re-read the README file and try again.
exit 2
make: *** [sanity_check] Error 2
Ich habe read the README and man pages again, but i cannt locate my
mistake.
I hope everyone can help me.
So long
Jan
next reply other threads:[~2006-09-14 10:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-14 10:11 Jan Dinger [this message]
2006-09-14 11:20 ` Kernel 2.6.18-rc7 Debian Marco Roeland
2006-09-14 11:44 ` Jan Dinger
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=45092AB8.2050401@arcor.de \
--to=jan.dinger@arcor.de \
--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.