On Wed, Mar 11, 2015 at 8:05 AM, Oliver Grawert <o...@ubuntu.com> wrote:
> hi, > Am Mittwoch, den 11.03.2015, 14:38 +0100 schrieb Christian Dywan: > > On 11.03.2015 00:35, Ricardo Salveti de Araujo wrote: > > > On Tue, Mar 10, 2015 at 6:25 PM, Michał Sawicz > > > <michal.saw...@canonical.com> wrote: > > >> W dniu 10.03.2015 o 20:41, Alan O'Dannel pisze: > > >>> Too late. Just found out the hard way. > > >> Confirmed, it never gets past the logo. > > >> > > >> To recover, boot to recovery and use > > >> $ ubuntu-device-flash --revision=127 touch... > > > The issue was basically because /sbin/initctl was removed from the > > > image, making the boot to fail completely. inifinity pushed a fix in > > > live-build and I just started to build 129, hopefully that should be > > > all good again. > > > > > > Sorry for the noise, should hopefully be the last remaining bug that > > > we got as a side effect of migrating desktop to systemd. > > Don't we have boot testing nowadays? Or is this a TODO item/ bug report > > still > most of our testing is totally moot if we don't actually produce an > image per landing instead of making the image writeable and taint it > with package installs (I'm claiming that since we started automated > testing ;) ) > The new suites we are working on for ubuntu-sanity-tests and ubuntu-ota-tests are executed on a read-only phone. This issue will be caught by the ota tests. We just need to run the suite on an image before it goes to -proposed channel. Maybe make a private pre-proposed channel? Or build the image in the same machine that will run the tests and use it locally? pura vida. -- ¡paz y baile! http://www.ubuntu.com
-- Mailing list: https://launchpad.net/~ubuntu-phone Post to : ubuntu-phone@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-phone More help : https://help.launchpad.net/ListHelp
