On Sun, 30 Apr 2006, Jurij Smakov wrote:
The only difference is I can see is that the version in trunk is no longer passing the --append-to-version to make-kpkg, so k-p is probably using some magic to come up with the (wrong) package name. Probably it only affects the arches with subarches, because amd64 has built fine. I suggest to reintroduce the --append-to-version option to be able to build the packages again (will try to test this solution).
Actually, that didn't help (or I didn't do it right ;-). The invocation of make-kpkg for the kernel-image target now contains
--append-to-version '-sparc32' and k-p tries to build the package with the name linux-image-2.6.17-rc3-sparc32-sparc32 which is, naturally not present in control file. Best regards, Jurij Smakov [EMAIL PROTECTED] Key: http://www.wooyd.org/pgpkey/ KeyID: C99E03CC -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
