---------- Forwarded message ----------
From: Fabrice Quenneville <email@example.com>
Date: Wed, Sep 28, 2011 at 2:04 AM
Subject: Re: installer kernel
On Wed, Sep 28, 2011 at 1:41 AM, Daniel Baumann <firstname.lastname@example.org>
On 09/28/2011 07:35 AM, Fabrice Quenneville wrote:for a32 (and even a33), you still need the binary hook.
> my hook was renaming 686-pae to vmlinuz
> etc..., i believe you fixed that in a32
i did only look at the actual log file, not the small one. don't you use
something like 'lb build >2&1 | tee build.log'?
No having it separate lets me easilly filter errors out.
this is now a33.
>> unrelated to that, there was a bug in non-derivatives handling when
>> using daily which is fixed in git now, and which would have affected you
>> in the way your describing, but according to your log, you're not even
>> getting at that stage, so the fix is unrelated to your problem.
So as you see i get the same installer you do, and when calling "gksu debian-installer-launcher" i end up with the print screen in the folder.
I am now running without the linux flavour. But i will still end up with 2.6.32-5, when you run the installer on your iso what kernel is it ?