This bug was fixed in the package linux-linaro - 2.6.35-1010.17
---
linux-linaro (2.6.35-1010.17) maverick-proposed; urgency=low
[ Tim Gardner ]
* Stable updates tracking bug
- LP: #686071
[ John Rigby ]
* LINARO: [CONFIG] Enable CONFIG_PERF_EVENTS for all flavours
This bug was fixed in the package linux-meta-linaro - 2.6.35.1010.14
---
linux-meta-linaro (2.6.35.1010.14) maverick-proposed; urgency=low
* Linaro Maverick ABI 1010 (2.6.35-1010.17)
- LP: #686071
-- John Rigby john.ri...@linaro.org Fri, 03 Dec 2010 21:45:54 -0700
--
You
Accepting the -meta package took a while, as I can't do that right away
with accepting the main kernel, as it would then build against the same
old ABI again. Would it be possible to add a build dependency against
the new kernel ABI somehow, so that the -meta build is guaranteed to
wait until the
** Branch linked: lp:ubuntu/maverick-proposed/linux-meta-linaro
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/686071
Title:
Linaro-2.6.35-1010.17 tracking bug
--
ubuntu-bugs mailing list
I'd really appreciate if kernel SRUs could properly prepare all the
referenced buts for SRUs, i. e. add proper Ubuntu package tasks (linux-
linaro (Ubuntu)) with a maverick task, and also set the natty status.
** Tags added: verification-needed
--
You received this bug notification because you
** Branch linked: lp:ubuntu/maverick-proposed/linux-linaro
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/686071
Title:
Linaro-2.6.35-1010.17 tracking bug
--
ubuntu-bugs mailing list
Martin - With regard to comment #1, is that really worth the effort? Its
simply not possible to subject these ARM vendor kernels to SRU policy.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/686071
Tim Gardner [2010-12-15 14:50 -]:
Martin - With regard to comment #1, is that really worth the effort? Its
simply not possible to subject these ARM vendor kernels to SRU policy.
Not doing so makes it much harder to see for bug reporters when a fix
has been proposed and released. After all,
