Final Image Testing for Utopic!

[Phill Whiteside]

Using an up to date image is useful.

I repeat that this was fixed last Friday..

https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1380774/comments/33
and
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1380774/comments/34

@ Ian, I see no notification on that bug of anyone rejecting the fix. Will
you please ensure you have an up to date image. As this bug would also
knock out ubuntu server, I would expect people to be squealing really
loudly by now.

@ Brian, As this is so critical, what else could we do?

Regards,

Phill.

On 21 October 2014 19:49, Nicholas Skaggs <nicholas.skaggs at canonical.com>
wrote:

> When you find bugs that are already reported, that's good data for the bug.
> I would report the result on the isotracker and then provide a link to the
> pre-existing bug report. On the bug report, I would click the 'also affects
> me' button at the top of the page. This raises the bug heat and is the best
> way to say 'this affects me too'.
>
> If you believe you have valuable info to add, please do comment on the bug
> report. Just avoid adding the "me too"! type comments. This means if the
> only comments you can add to the bug are that your machine is also broke,
> even if you provide the machine details, you don't need to leave the
> comment. By clicking 'affects me' you've already sent this data point. On
> the other hand if you can provide more details about the bug, or the bug
> behaves uniquely for you, etc, please do comment. *Sometimes* this might
> mean you would leave a comment saying it affects brand X of hardware as
> well as what's listed in the bug, but only when the bug itself mentions
> these specific limitations.
>
> Bugsquaders, please feel free to correct if I mispoke on anything above :-)
> I trust this helps and makes sense. Thanks so much for testing!
>
> Nicholas
>
> On Tue, Oct 21, 2014 at 12:27 PM, Ian Bruntlett <ian.bruntlett at gmail.com>
> wrote:
>
> > Hi Nicholas,
> >
> > On 21 October 2014 16:19, Phill Whiteside <PhillW at phillw.net> wrote:
> >
> > > On 21 October 2014 16:08, Nicholas Skaggs <
> nicholas.skaggs at canonical.com
> > >
> > > wrote:
> > >
> > > > Thanks to everyone for the results, keep'em coming!  If you haven't
> yet
> > > > submitted test results, please do so. We currently have a few
> critical
> > > bugs
> > > > affecting the images;
> > > >
> > > > http://bugs.launchpad.net/bugs/1380774
> > > > http://bugs.launchpad.net/bugs/1325801
> > > > http://bugs.launchpad.net/bugs/1362333
> > >
> > I have tested 2 lubuntu images. The first one displayed a blank screen
> > where a login screen should have been visible. The other one failed to
> > install, the key error message from the installer being "No installable
> > kernel was found in the defined APT sources". The installer still
> installed
> > the packages. On booting, as could be expected, there was no kernel and
> the
> > system boots straight into memtest86+
> >
> > Originally I didn't post anything because by the time I found them, they
> > were already listed on the appropriate Ubuntu web pages. What would you
> > prefer I do in future? Report only bugs that haven't been listed? Or
> report
> > listed bugs with info about how a known bug affects my particular test
> > system?
> >
> > BW
> >
> >
> > Ian
> >
> > --
> > -- ACCU - Professionalism in programming - http://www.accu.org
> > -- Free Software page -
> > http://contactmorpeth.wikispaces.com/SoftwareToolkit
> > --
> > Ubuntu-quality mailing list
> > Ubuntu-quality at lists.ubuntu.com
> > Modify settings or unsubscribe at:
> > https://lists.ubuntu.com/mailman/listinfo/ubuntu-quality
> >
> --
> Ubuntu-quality mailing list
> Ubuntu-quality at lists.ubuntu.com
> Modify settings or unsubscribe at:
> https://lists.ubuntu.com/mailman/listinfo/ubuntu-quality
>



-- 
https://wiki.ubuntu.com/phillw