On Wed, 2007-05-09 at 23:57 -0500, Manoj Srivastava wrote:
On Tue, 08 May 2007 10:52:57 +0200, Johannes Berg
[EMAIL PROTECTED] said:
On Mon, 2007-05-07 at 21:42 -0500, [EMAIL PROTECTED] wrote:
Perhaps you should check out 11.001 before giving up on this? :)
Hmm. I lost track of what
On Tue, 08 May 2007 10:52:57 +0200, Johannes Berg
[EMAIL PROTECTED] said:
On Mon, 2007-05-07 at 21:42 -0500, [EMAIL PROTECTED] wrote:
Perhaps you should check out 11.001 before giving up on this? :)
Hmm. I lost track of what you wanted/didn't want to do, but now I get
this when starting
On Mon, 2007-05-07 at 21:42 -0500, [EMAIL PROTECTED] wrote:
Perhaps you should check out 11.001 before giving up on this? :)
Hmm. I lost track of what you wanted/didn't want to do, but now I get
this when starting from a modified git tree that has been built but
without debian/ or stamp-*
On Sat, 2007-05-05 at 20:09 -0500, Manoj Srivastava wrote:
Well, the thing is, the generated packages try to conform to
Debian policy, and thus, ./debian is created first, and then you run
the other commands (./debian/rules build, ./debian/rules clean, etc.)
[...]
Ah, true.
Hi,
On Mon, 07 May 2007 10:48:33 +0200, Johannes Berg
[EMAIL PROTECTED] said:
On Sat, 2007-05-05 at 20:09 -0500, Manoj Srivastava wrote:
Not enough people are kernel hackers for that mode to be the
default mode of operation.
Yeah, I guess. Maybe I'll just patch my local kernel-package to
On Sat, 05 May 2007 10:18:40 +0200, Johannes Berg [EMAIL PROTECTED] said:
On Fri, 2007-05-04 at 21:02 -0500, Manoj Srivastava wrote:
Well. I think I want to make a) work here as well. So, one thing I
can do is if $(SHELL /bin/sh scripts/setlocalversion) is not null,
then append -dirty to it
On Fri, 2007-05-04 at 21:02 -0500, Manoj Srivastava wrote:
Well. I think I want to make a) work here as well. So, one thing
I can do is if $(SHELL /bin/sh scripts/setlocalversion) is not null,
then append -dirty to it (since make-kpkg does make changes to the
Makefile there, so
On Mon, 30 Apr 2007 14:12:35 +0200, Johannes Berg [EMAIL PROTECTED] said:
Hi,
The setlocalversion script goes and changes the version of the
kernel _after_ ./debian/ has been populated, which causes the
./debian/changelog and ./debian/control files to be out of synch
with what the kernel
On Fri, 2007-05-04 at 14:10 -0500, [EMAIL PROTECTED] wrote:
I am not sure I understand these words. It seems to me that
the two cases you cite (invoking make-kpkg once, and invoking it
again after the kernel has been built) cover all possible cases. If
something is true in all
On Fri, 04 May 2007 21:40:24 +0200, Johannes Berg
[EMAIL PROTECTED] said:
But I like having debian packages with the gX...X-dirty version :)
What I usually did was hack on the kernel, make, make M=... until it
all compiles, make again, then invoke make-kpkg kernel_image and
install the
Hi Manoj,
OK. Since you are using git kernels, perhaps you can try this
experiment:
Sure.
a) running make-kpkg on a pristine git tree works
b) make some change (add/delete whitespace, or something, so the tree
is not pristine, and run make-kpkg again. Does it still
On Sat, 05 May 2007 02:27:00 +0200, Johannes Berg
[EMAIL PROTECTED] said:
Ok, let's see. First run: CONFIG_LOCALVERSION_AUTO is set:
$ sh scripts/setlocalversion -g65c44b40[no newline]
a) running make-kpkg by itself creates debian/changelog with version
2.6.21-g65c44b40-pb1 (-pb1 is my
Hi,
The setlocalversion script goes and changes the version of the
kernel _after_ ./debian/ has been populated, which causes the
./debian/changelog and ./debian/control files to be out of synch with
what the kernel thinks the version is -- and thus preventing the .deb
from
Package: kernel-package
Version: 10.068
Severity: normal
During development, I like to package my kernels so I always have a clear
packaged version of the kernel that I'm running and can always go back to
that version. For this, I like using kernel-package. However, recently,
kernel-package
14 matches
Mail list logo
