make: mkbootmsg: Command not found

The mkbootmsg command used to be part of the gfxboot package up to lucid and was removed in maverick - no idea why (not in changelog for gfxboot package).

Will have to research a solution - might take some time.

problem is that gfxboot-dev does not exist on <=lucid so the new debian/control file won't work on lucid :-\

I know - trying to figure out some way to solve this (i.e. will ask the dpkg maintainers)

maybe it's tile to split the control file and make control.lucid and control.maverick so I could rewrite the build.sh to build the 2 different packages ready for upload... what do you think about that?

There should be a way to do this within a single control file - after all splitting packages is a fairly common operation and there should be a simple solution for this problem. Maybe something like
Depends: gfxboot (<= x.x.x) | gfxboot-dev (>=y.y.y)
would work?

"gfxboot-dev (>=y.y.y)" won't work cause y.y.y is the gfxboot-dev version not something related to the distro and I actually don't know if there's a way to say "gfxboot-dev if it's available", I think it's not possible:
http://www.debian.org/doc/debian-policy/ch-relationships.html#s-binarydeps

we could use a group syntax like
gfxboot | gfxboot-dev
like you said but I think in maverick we need both gfxboot AND gfxboot-dev, or for maverick gfxboot is not mandatory? what a mess!

checked:

gfxboot | gfxboot-dev

should be ok and fixing the problem

Installing gfxboot-dev did solve the problem on both a i386 and an amd64 host.

Thank you both very much for your prompt assistance.

Here's the answer I got from the dpkg crew
(https://answers.launchpad.net/ubuntu/+source/dpkg/+question/126011):

> Philip Muškovac said 9 minutes ago:
>
> you could use something like
> Depends: gfxboot-dev | gfxboot (<< 4.2.2)
> that will install gfxboot-dev in maverick and the older gfxboot package
> on lucid as gfxboot-dev isn't available in lucid.
>
> @actionsparsnip: this is a simple packaging change in gfxboot, which is
> perfectly fine from my point of view (maintainer decision).
> getting packages to install on multiple releases with the same packaging
> can be tricky sometimes (had the same problem a while ago)
Still need to check the correct version for gfxboot, though.

you're absolutely right! committed

@Fabrizio: gfxboot does exist in maverick, is pulled in as a dependecy of gfxboot-dev but can also be installed all by itself - in which case just having gfxboot|gfxboot-dev wouldn't solve the problem.

i got this same bug. what additional packages are to be installed to use uck?