It's not showing up in the update-manager, and I can't find it by searching
for "linux" in synaptic. It seems it's not uploaded yet. I'm using the nz
servers, so it may not have propogated that far yet.
On Wed, Nov 26, 2008 at 10:31 PM, Andy Whitcroft <email address hidden> wrote:
> On Wed, Nov 26, 2008 at 12:48:15AM -0000, rorzer wrote:
> > I see from here:
> >
> https://lists.ubuntu.com/archives/intrepid-changes/2008-November/009508.html
> > That 2.6.27-10.20 was accepted into intrepid-proposed on the 21/9/08.
> It's
> > not showing up in synaptic yet, how long does this normally take?
>
> I cirtainly got it this morning. The kernel is complex as an upload
> because of the linux-meta package. Until this is uploaded the new
> kernel can be in the archives and available for install but not offered
> in update-manager. Let me know if you don't have it now.
>
> --
> linux-image-2.6.20-16 fails to detect twin usb gamepad
> https://bugs.launchpad.net/bugs/140608
> You received this bug notification because you are a direct subscriber
> of the bug.
>
It's not showing up in the update-manager, and I can't find it by searching
for "linux" in synaptic. It seems it's not uploaded yet. I'm using the nz
servers, so it may not have propogated that far yet.
On Wed, Nov 26, 2008 at 10:31 PM, Andy Whitcroft <email address hidden> wrote:
> On Wed, Nov 26, 2008 at 12:48:15AM -0000, rorzer wrote: /lists. ubuntu. com/archives/ intrepid- changes/ 2008-November/ 009508. html 2.6.20- 16 fails to detect twin usb gamepad /bugs.launchpad .net/bugs/ 140608
> > I see from here:
> >
> https:/
> > That 2.6.27-10.20 was accepted into intrepid-proposed on the 21/9/08.
> It's
> > not showing up in synaptic yet, how long does this normally take?
>
> I cirtainly got it this morning. The kernel is complex as an upload
> because of the linux-meta package. Until this is uploaded the new
> kernel can be in the archives and available for install but not offered
> in update-manager. Let me know if you don't have it now.
>
> --
> linux-image-
> https:/
> You received this bug notification because you are a direct subscriber
> of the bug.
>