10.10 building failed

You're quite fast - haven't had a chance to test UCK on maverick yet.

Some rough guesses:
1) There does not seem to be a gfxboot-theme-ubuntu package for maverick (yet?) - Not sure, whether there will ever be one.
2) From the looks of it the mechanism to determine the ubuntu release name seems to not work on maverick. This is needed to determine the correct version of gfxboot-theme-ubuntu to download.

As soon as I get some time I will have a closer look, but don't hold your breath until then: maverick is still at a very early stage and I don't want to go chasing phantoms of problems that vanish once the release ripens.

As a workaround: remove the gfxboot-theme-ubuntu related code from ~/tmp/customization-scripts/customize_iso and resort to the command line interface of UCK (or try uck-flow ;-).

UCK is practically most important thing to me and without UCK there would be no good Ubuntu to me. UCK is only best tool to edit .iso directly.

I try that workaround thanks...

Beta comes in september 2, september 16 is final freeze. 10.10 release is october 10 (nice date 10.10.2010)

Just checked: The location http://packages.ubuntu.com/maverick/gfxboot-theme-ubuntu has not been established yet - this is why you get the error.

Here's another workaround that should be simpler for you to implement:

Manually download the gfxboot-theme-ubuntu package sources for maverick as of 2010/08/19 from
http://archive.ubuntu.com/ubuntu/pool/main/g/gfxboot-theme-ubuntu/gfxboot-theme-ubuntu_0.10.1.tar.gz
and unpack it in ~/tmp (or wherever your customization root directory is located).

UCK will then use that downloaded version instead of trying to download the latest version itself. This will prevent the error from occuring.

Please make sure you remove the manually downloaded version again once the official location becomes available - otherwise you run the risk of getting version mismatches for gfxboot-theme-ubuntu which could result in unbootable/misbehaving ISOs.

UPDATE: now building was fine with official location but when i booted builded livecd.iso then there was error:

graphic initialization failed
Error setting up gfxboot
Boot:
Loading bootlogo...

This message stays repeating infinite times.
I do not know where that fault is, is it still 10.10 fault??? dont know.

10.10 beta (daily 8 livecd)

Today update:

With UCK 2.3.0 is exactly same story that building is ok but do not boot.

Just in case i post v3 of log if that helps and screenshot of error from livecd.iso

A question asked today (https://answers.launchpad.net/uck/+question/126000) may point to a solution of the problem you are having:

It looks like there have been massive changes to gfxboot from lucid to maverick. I don't know what version you are building your 10.10 remix on (I would assume that it's 10.04 based), but from the looks of it the gfxboot tools in lucid may not be able to generate the gfxboot images required in maverick. For the time being just a wild guess.

Could you therefore try to build your remix on a 10.10 based system (you will need to install the gfxboot-dev package in addition to the packages pulled in by uck automatically for this to work)?

Alternatively (which is what UCK would have to do if my guess as to the origin of the error is correct) you could download the sources for gfxboot in maverick, compile them and use the generated binaries instead of the ones provided by lucid (careful please - don't destroy your system in the process).

Hmm i thought that building platform ( currently was 10.04) do not affect this if i build 8.04 or 10.10 for example.
 I now try install 10.10 for building platform and i test it again in hope of correct iso.

Unfortunately your assumption is not correct - UCK relies on quite a bit of functionality on the hosting system (like working gfxboot tools to regenerate the gfxboot image or squashfs to un-/compress the casper image, mount/umount, chroot and shell to just name a few).

Most of them are not critical (mostly because they tend to change very slowly or because the changes are backwards-compatible), but some of them are critical and usually only spring up close to the final release of a new Ubuntu version.

We have been bitten by changes to the squashfs implementation before - your problem seems to stem from changes to gfxboot that are incompatible between the version on your host and the version in the system beng customized.

Usually we were/are able to figure out a workaround...

Let's hope for the best.

It worked:

Installed 10.10 daily, UCK 2.3.0 and iso was fine, now i am not sure if gfxboot-dev package helped or not that i am not sure because i did not test building without it.

Thank you so much of your efforts, Ubuntu is only worth to use if there is UCK.

Offtopic:
You wonder why i dont want to use Ubuntu without UCK, reason is: Default soft is quite crap for me, i remove lot of things to make Ubuntu lighter but keep all features and improve OUT OF BOX experience with vlc, startupmanager (good for dual setups Win+Ubuntu), 7z, Nautilus Elementary and other needed cosmetic changes. I have 3 relatives and 2 friends who use my edited Ubuntu 10.04 and they really like it.

I post success log to you for study if you want and you decide to mark this bug to solved or not.

The dependency on gfxboot-dev actually solves the problem:

gfxboot-theme-ubuntu has been split into two packages and the mkbootmsg command has been modified/renamed in the process.

The Makefile provided with gfxboot uses the mkbootmsg command if it is found (leftover from a previous install) and generates unbootable ISOs. gfxboot-dev provides the updated/renamed alternative which is choosen in preference by gfxboots Makefile resulting in working images again.

this is me build.log.

fix released with 2.4.0