I am closing this bug report as the FTBFS reported is not a bug in the
build system but has to to with the AVI checking feature there. For the
other issues mentioned here, please open a separate bug. Thanks.
** Changed in: linux (Ubuntu)
Status: Incomplete => Invalid
--
linux packages in
Following up this comment:
> It would be interesting to know which was the last kernel which allowed you
> to proceed the way it looks.
This isnt an exact answer, but;
linux-{image,headers}-2.6.24-23-386 and linux-headers-2.6.24-23 only install
with the -updates repo enabled, rather then with ju
On Tue, 03 Mar 2009 09:35:54 -
Stefan Bader wrote:
> It looks a bit mingled in the report, but:
>
> abinum = 23
>
> This means the ABI is 23, so as long as your kernel build does not
> change things that cause kernel functions to have different arguments
> or to vanish, you won't need to do
It looks a bit mingled in the report, but:
abinum = 23
This means the ABI is 23, so as long as your kernel build does not
change things that cause kernel functions to have different arguments or
to vanish, you won't need to do the other packages. But if you do, you
would have to rebuild them in t
On Thu, 26 Feb 2009 19:11:07 -
Stefan Bader wrote:
> >
> > 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
>
> 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 cha
Hi Stefan, thanks for looking into this.
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?
--
linux packages in hardy-security FTBFS in a ppa
https://bugs.launchpad.net/bugs/333766
You received
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
