[Sugar-devel] F30 ARM (Raspberry Pi) SoaS not working, but a fix exists..
quozl at laptop.org
Mon May 20 17:28:50 EDT 2019
On Mon, May 20, 2019 at 01:16:03PM -0700, Alex Perez wrote:
> James Cameron wrote on 5/19/19 3:50 PM:
> > That's unfortunate.
> Agreed, but it was due to a lack of testing.
Root cause was changes made without adequate testing before commit; a
degree of confidence and audacity that is somewhat astounding.
> > Were the Fedora 30 ARM builds being tested before release?
> They were, but only in QEMU, it would seem. The temporary workaround
> is to fetch the initramfs referenced below, and then, after imaging
> the image to an SD card using $preferredImagingMethod (Fedora Image
> Writer, for most folks, would be their best bet), just copy the
> downloaded initrd over to the boot partition on the SD card.
My question was in context of Sugar, about testing by Sugar developers
such as Thomas. I've seen testing by non-Sugar developers or Fedora
automated systems is less likely to find problems. I know this was a
hardware specific fault. But I'm trying to figure out how Sugar Labs
had covered this. I don't remember seeing any posts to sugar-devel@
about successful testing. I'm also disturbed by very few posts about
0.113 and 0.114 testing.
(Fedora Image Writer is a trademark-branded download and image copy
utility for Windows, Mac OS, and Linux. I'll continue to promote
Etcher for the moment, to avoid that branding, as Etcher will work
with Raspian, Debian, and Ubuntu images as well.)
> > Are the Fedora 31 ARM builds being tested?
> I am informed by pwhalen that, as of today, the image is still
> broken in rawhide (which will become F31) but that it will be fixed
> in the coming days/weeks, now that there's a bug for the issue:
Thanks, interesting. But again, my question was in the context of
testing by Sugar developers here. If nobody is going to be testing
these builds, it may be better to concentrate on the testing that Jeff
More information about the Sugar-devel