Sir, it's very possible this asteroid is not stable.
The Linaro 16.02 release is now available for download! This cycle
contains a big, but hopefully invisible change: all artefacts for
16.02 are now hosted using Amazon S3. Personally, it meant that both
upload and downloads speeds increased six-fold, making my release week
coffee breaks a lot shorter.
In the future Andy & Ben will turn on geo-clouding for even more
bandwidth improvements for people outside of North America.
As I said 'hopefully' above, don't hesitate to email me if you suspect
something is not as it should be with this release.
As with the previous two cycles, the OE release comes with a lot of
qualifiers and caveats. Something has gone wrong in the CI loop which
broke fetching the hwpacks for the prebuilt images, which means the
prebuilts have been recycled from last cycle.
Using the Android-based images
The Android-based images come in three parts: system, userdata and boot.
These need to be combined to form a complete Android install. For an
explanation of how to do this please see:
If you are interested in getting the source and building these images
yourself please see the following pages:
Using the OpenEmbedded-based images
With the Linaro provided downloads and with ARM’s Fast Models virtual
platform, you can boot a virtual ARMv8 system and run 64-bit binaries.
For more information please see:
Using the Debian-based images
The Debian-based images consist of two parts. The first part is a
hardware pack, which can be found under the hwpacks directory and
contains hardware specific packages (such as the kernel and bootloader).
The second part is the rootfs, which is combined with the hardware pack
to create a complete image. For more information on how to create an
image please see:
(Yes, that points to Ubuntu, I know, the instructions are still valid)
More information on Linaro can be found on our websites:
Also subscribe to the important Linaro mailing lists and join our IRC
channels to stay on top of Linaro developments:
#linaro on irc.linaro.org or irc.freenode.net
#linaro-android irc.linaro.org or irc.freenode.net
Known issues with this release
Bug reports for this release should be filed in Bugzilla
(http://bugs.linaro.org) against the
individual packages or projects that are affected.
On behalf of the release team,
Builds and Baselines | Release Manager
Linaro.org | Open source software for ARM SoCs
ILP32 Bootstrap [BB-277 20%]
Started, reviewed names via cross-distro list
Updated DPKG and configure patches. testing
Fixup packages for arm64 [50%]
Tried to get openvrml building on arm64 with dh-autoreconf. Bugs and patches updated
Robot OS 10% [BB-163 leftovers]
Advised on some issues with plugin paths and log-type linkage
Uploaded fixed ro-ros-comm to experimental
Arm64 buildd maintenance [BB-86 20%]
Tested pybit as cross-buildd D. Found breakage. filed bugs
Principal hats: Linaro, Debian, Wookware, ARM
tldr; patches.linaro.org will be upgraded tomorrow, Wednesday the 9th
patches.l.o is being updated with a number of new improvements:
* We are no longer a fork of the patchwork project and can stay
up-to-date with improvements from the project.
* Team memberships are now handled correctly. In the past moving to a
new team meant we could either leave you in both teams and then show
patch credits to both teams or remove you from the old team and have
that team lose all contributions you made.
* Multiple emails fixed. In the past doing Linaro work under another
email (say @kernel.org) didn't properly contribute to patch metrics.
This has been fixed (assuming you add your additional email account(s)
* Performance - the new data layout is much more efficient resulting in
faster page loads.
I have came back to getting a Linaro Jenkins local build working by
pairing down the IFC6410 script.
I have came to a point where the cross platform build tools are not working !
It does not look like the script installs them properly and I am
confused as to wether the script actually installs them or whether it
erroneously relies on them being present on the build machine ?
I have attached my paired down .yaml script and the output build log.
Either I am doing something wrong or the normal Qualcomms script does
actually load the build tools. So either theres a bug to be fixed or I
need to know how to install the build tools or both !
Many thanks in advance,
Hello, I couldn't figure out the Erase Block Size of my `Apacer Technology,
Inc. Handy Steno 2.0/HT203` flash stick.
As I understand, I have to run test as 1024 multiplied by factor of the stick
capacity, is it? So, I ran tests with different blocksizes
Alas, I didn't see anything resembling EBS ☹ I could suppose it is either of
16384, 24576, 57344, but searching over the Internet shows that EBS never
appears that low. Any ideas?
All Linaro Gerrit servers have been upgraded to Gerrit 2.11.5 in
planned manner. As was announced previously, we intended to upgrade
directly to the latest 2.12, but literally couple of dates before
upgrade we found out that there's known issue which affects replication
services and thus our Git HA infrastructure. The bug has bean fixed by
now in the Gerrit master, but the date of 2.12.1 release wasn't yet
announced. As the aim of the current upgrade was to get on newer
Gerrit version than now-old 2.10, we decided to upgrade to 2.11.5
in the meantime, and revisit upgrade to 2.12 after bug fix releases.
Upgrade services appear to work stable based based on weekend
monitoring, ditto for CI loops integrating with Gerrit.
If you spot any issues, please provide details in a direct reply
(not "Reply All") to this mail.
One of the most user-facing changes in 2.11 is dropping support for
"old" change screen UI design. About 20 people of (hundreds) in Linaro
used the old design, and they were notified beforehand of the upgrade.
You can read about changes and new features in 2.11 at
As a sneak peek:
* Yet in 2.10, there was introduced feature of editing a commit
message in the Web UI. That's convenient if you e.g. spotted a typo in
colleague's commit message - you don't need describe him/her an issue
and make them rebase a change via command line, but can fix it on spot
in the browser (subject to ACLs).
* 2.11 brings this idea forward and allows to create entire patchsets
via web browser, or post follow-up changes changes in the same way. It
yet to be seen how useful this functionality is (in github, which has
similar functionality, it's actually useful - if you e.g. read a README
and spot a typo, you can submit a pull request with the fix on spot).
Happy code reviewing from Systems Team!
Linaro.org | Open source software for ARM SoCs
Follow Linaro: http://www.facebook.com/pages/Linarohttp://twitter.com/#!/linaroorg - http://www.linaro.org/linaro-blog