On Mon, Jul 25, 2011 at 02:20, Michael Gilbert <firstname.lastname@example.org>
On Mon, Mar 14, 2011 at 11:39 AM, Otavio Salvador wrote:
> By default the building system gets the udebs from unstable. This isHi, various regressions have happened lately. "make build_all" doesn't
> configurated on debian/rules using the building system variable (that
> you ought to take a look at). Another alternative is to use a local
> sources.list.udeb.local file to set it to use the stable suite.
get around this issue any more. Also, changing udeb sources doesn't
work anymore, "USE_UDEBS_FROM=unstable make build_netboot".
Please tell us about those regressions. Regarding the USE_UDEBS_FROM=unstable I think it is due the KERNELVERSION value set to 2.6.32... more bellow.
I've ended up having to implement a couple different ugly workarounds
to keep my testing snapshot builds going while various things change.
I've had enough frustration dealing with those that I've decided toThe core issue is that KERNELIMAGEVERSION is a hardcoded value in the
come up with a "real" solution.
arch config files, so its currently stuck at squeeze's version. Thus,
the solution is simply to parse that value from known package info
I understand your frustation however we have the KERNELVERSION specified in the architecture due technical reasons.
The installer itself, sometimes, need modifications or fixes to be able to handle newer kernel versions so the version that is hard-coded on those is the version that is supported by the installer. It is not only a matter of recompile installer against the new kernel (sometimes this works by this is not guaranteed). Another important point is that there are architectures that use different kernels depending on the subarch (e.g armel uses iop32x, kirkwood and others) and dynamically it is more difficult to handle this.
Specifically about the patch it is incomplete since it doesn't handle all the architectures thus we can't take it.