Re: installer kernel
On 09/28/2011 05:32 AM, Fabrice Quenneville wrote:
> #Create the config files
> --linux-flavours "686-pae" \
as i said previously, you can't do that without rebuilding d-i, you will
have to use 486 here in order to use the launcher.
according to your log hower, the 486 kernels are installed in your
image, means, above config is *not* the config which was used to build
that image the log is from.
> If you want to see my logs you can look
> in http://dl.vanillux.org/stable/fail-20110927-logs/
i'm doing the following with lb 3.0~a32-1 (a31 is not different in that
respective, so that's not the issue):
lb config -d wheezy --debian-installer live
--debian-installer-distribution daily
which results in the following log:
http://unable-to-package.org/~daniel/live/build.log
where you see after lb_binary_debian-installer is running log entries
like the following to fetch the d-i images:
[...]
P: Begin installing debian-installer...
2011-09-28 04:15:23 URL:http://ftp.de.debian.org/debian//dists/wheezy
/main/installer-i386/current/images//cdrom/vmlinuz [2189312/2189312]
-> "/home/daniel/build/cache/binary_debian-installer
/http:__ftp.de.debian.org_debian__dists_wheezy_main_installer-
i386_current_images__cdrom_vmlinuz" [1]
2011-09-28 04:15:25 URL:http://ftp.de.debian.org/debian//dists/wheezy
/main/installer-i386/current/images//cdrom/initrd.gz
[4152590/4152590] -> "/home/daniel/build/cache/binary_debian-installer
/http:__ftp.de.debian.org_debian__dists_wheezy_main_installer-
i386_current_images__cdrom_initrd.gz" [1]
2011-09-28 04:15:25 URL:http://ftp.de.debian.org/debian//dists/wheezy
/main/installer-i386/current/images//cdrom/gtk/vmlinuz
[2189312/2189312] -> "/home/daniel/build/cache/binary_debian-installer
/http:__ftp.de.debian.org_debian__dists_wheezy_main_installer-
i386_current_images__cdrom_gtk_vmlinuz" [1]
2011-09-28 04:15:30 URL:http://ftp.de.debian.org/debian//dists/wheezy
/main/installer-i386/current/images//cdrom/gtk/initrd.gz
[16012110/16012110] -> "/home/daniel/build/cache/binary_debian-
installer/http:__ftp.de.debian.org_debian__dists_wheezy_main_installer-
i386_current_images__cdrom_gtk_initrd.gz" [1]
[..]
and the udebs:
[...]
Download complete and in download only mode
2011-09-28 04:15:36 URL:http://ftp.de.debian.org/debian//dists/wheezy
/main/binary-i386/Release [81/81] -> "/home/daniel/build/cache
/binary_debian-installer
/http:__ftp.de.debian.org_debian__dists_wheezy_main_binary-
i386_Release" [1]
2011-09-28 04:15:36 URL:http://ftp.de.debian.org/debian//dists/wheezy
/main/debian-installer/binary-i386/Packages.gz [77909/77909] -> "/home
/daniel/build/cache/binary_debian-installer
/http:__ftp.de.debian.org_debian__dists_wheezy_main_debian-
installer_binary-i386_Packages.gz" [1]
2011-09-28 04:15:36 URL:http://ftp.de.debian.org/debian//pool/main/a
/alsa-driver/alsa-base-udeb_1.0.23+dfsg-4_all.udeb [1218/1218] ->
"alsa-base-udeb_1.0.23+dfsg-4_all.udeb" [1]
[...]
but your log does not show either of them.
or in other words: i have absolutely no clue what you're doing, but
you're certainly not doing a clean build here, the bug is either a
screwed up build host, screwed up build tree, or screwed up config tree.
however, the problem seems to be at your end, not live-build.
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.
--
Address: Daniel Baumann, Donnerbuehlweg 3, CH-3012 Bern
Email: daniel.baumann@progress-technologies.net
Internet: http://people.progress-technologies.net/~daniel.baumann/
Reply to: