It would be interesting to know which was the last kernel which allowed you to 
proceed the way it looks. The problem are basically the checks that are done to 
make sure the kernel ABI did not change. This is related to the changelog. 
If you get the kernel source and build unmodified the topmost version will be 
2.6.24-23.48 and the next one should be 2.6.24-23.46 (-23.47 is missing there 
but that is ok).
What happens whenever you build a kernel package is that the most recent 
version and the one before are compared at the end of the build. Without 
modification this would look at 2 directories
debian/abi/2.6.24-23.46/... (comes with the package) and
debian/abi/2.6.24-23.48/... (is generated since you rebuild and that is the 
latest version, but only for the current arch)

>From the failure logs I take it that you added a new version number on
the top of the changelog. Now your version is the most recent and
2.6.24-23.48 is the previous one. But you don't have the files generated
by that build. So your build looks for debian/abi/2.6.24-23.48 and
fails. I believe you have two options:

1. Get the correct ABI files (though tis uses a lot of bandwidth since it 
temporarily downloads all kernel packages)
    call "./debian/scripts/misc/getabis 2.6.24 23.48" before you create your 
source package
2. Cheat and rename the previous previous abi directory
    "mv debian/abi/2.6.24-23.46 debian/abi/2.6.24-23.48" before you create the 
your source package


** Changed in: linux (Ubuntu)
   Importance: Undecided => Medium
     Assignee: (unassigned) => Stefan Bader (stefan-bader-canonical)
       Status: New => Incomplete

-- 
linux packages in hardy-security FTBFS in a ppa
https://bugs.launchpad.net/bugs/333766
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to