> > Just to try and make sure I understand: are you saying that by having ' > ubuntu1 ' on the end of the kernel version might be causing the builds > to fail? > Not by the ubuntu1 but by starting a new release. Which makes the releases shift. An arbitary example. You get the package and the changelog loogs like this:
linux (1.2) release urgency=low * more bla linux (1.1) release urendcy=low * bla When you do a dch -i (or whatever) to start a new release it would look like: linux (1.2ubuntu1) release urgency=low * even more bla linux (1.2) release urgency=low * more bla linux (1.1) release urendcy=low * bla So it doesn't matter how the new release is named. It is just there and the previous release is not 1.1 anymore but 1.2. So those abi files are searched in debian/abi/1.2 which does not exist. You can, for the kernel package call "debian/rules printenv" which will show some of there variables internally used, which includes prev_revision. -- 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
