Process is meant to now prevent missmatched compilers in the -security
pocket, so this should no longer happen.
** Changed in: linux (Ubuntu)
Status: In Progress => Fix Released
--
kernel 2.6.27-11-generic and gcc version mismatch
https://bugs.launchpad.net/bugs/343614
You received this b
On Sun, Apr 26, 2009 at 10:10:05PM -, Chris Sherlock wrote:
> This is now also occuring on Jaunty.
>
> I was wondering how things were going with sorting this out?
We should now have sync'd compilers on Intrepid and Hardy, at least that
is my understanding. The release team are meant to be a
This is now also occuring on Jaunty.
I was wondering how things were going with sorting this out?
--
kernel 2.6.27-11-generic and gcc version mismatch
https://bugs.launchpad.net/bugs/343614
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Sorry folks... I should have noted that I'm using Intrepid Ibex. Doh!
--
kernel 2.6.27-11-generic and gcc version mismatch
https://bugs.launchpad.net/bugs/343614
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing lis
This is in reality neither a gcc nor a kernel bug but more an archive
bug. As there is no category for this and because we are already
working a hardy kernel/compiler miss match in the kernel team lets move
it over to Linux.
** Changed in: linux (Ubuntu)
Sourcepackagename: gcc-defaults => linux
Hardy instance is bug #292381
--
kernel 2.6.27-11-generic and gcc version mismatch
https://bugs.launchpad.net/bugs/343614
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://l
