There's been a long standing request to move git.linaro.org's web UI
over to cgit[1]. We've just deployed a test version at:
https://git.linaro.org/cgit/
We'd like to get people to try out and share any issues they have. Once
we work through issues, we'd like to get rid of the old gitweb interface
and make this the standard web UI to our git servers.
cgit has a bunch of nice features you should enjoy including:
* Significantly faster
* README support, eg: https://git.linaro.org/cgit/arm/vixl.git/about/
* A much cleaner UI (slightly objective opinion)
* Actively used by the best git sites such as git.kernel.org
= FAQ:
Q: The front page is much smaller?
A: I've collapsed many of our lesser used "sections" including the
"people" area so that our most used repos are more prominent.
Q: How does the "about" page work.
A: Just add a file like README, README.txt, README.md, README.rst and it
will automagically work. We can collapse or expand any sections we want,
I just took an initial stab at what seemed obvious to me.
Q: This looks a little different than normal cgit?
A: Yes, I've got to UI patches that have been reviewed, but not yet merged:
https://lists.zx2c4.com/pipermail/cgit/2016-September/003300.html
Q: What about android-git.linaro.org?
A: It will be converted after we finish with git.l.o
Q: What about our private git server?
A: There is a small privacy issue I'm trying to work out with the
maintainers so it can be used by us:
https://lists.zx2c4.com/pipermail/cgit/2016-September/003307.html
1: https://git.zx2c4.com/cgit/about/
The second test rebuild of Yakkety Yak was started on September 16 for all
architectures, all components (main component and seeded packages mostly
finished, unseeded packages still building).
Results (please also look at the superseded builds) can be found at
http://qa.ubuntuwire.org/ftbfs/test-rebuild-20160916-yakkety.html
Additional build failures for packages in yakkety-proposed (not yet in yakkety)
can be found at http://qa.ubuntuwire.com/ftbfs/
Please help fixing the build failures.
Another test rebuild using the Linaro-GCC 6 as the default (planning the
defaults change around the end of October) can be found at
http://qa.ubuntuwire.org/ftbfs/test-rebuild-20160916-linaro-yakkety.html
The corresponding compiler can be found in the ubuntu-toolchain-r/test PPA.
Matthias
"Teamwork is essential -- it allows you to blame someone else."
~ Anonymous
The Linaro 16.09 release is now available for download! And it's a week
early!
In preparation for Linaro Connect LAS16 in Las Vegas we're releasing a
bit earlier than usual. Next cycle will be back on schedule.
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:
http://wiki.linaro.org/Platform/Android/ImageInstallation
If you are interested in getting the source and building these images
yourself please see the following pages:
http://wiki.linaro.org/Platform/Android/GetSourcehttp://wiki.linaro.org/Platform/Android/BuildSource
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:
http://www.linaro.org/engineering/armv8
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:
http://wiki.linaro.org/Platform/DevPlatform/Ubuntu/ImageInstallation
Getting involved
============
More information on Linaro can be found on our websites:
* Homepage:
http://www.linaro.org
* Wiki:
http://wiki.linaro.org
Also subscribe to the important Linaro mailing lists and join our IRC
channels to stay on top of Linaro developments:
* Announcements:
http://lists.linaro.org/mailman/listinfo/linaro-announce
* Development:
http://lists.linaro.org/mailman/listinfo/linaro-dev
* IRC:
#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,
Koen Kooi
Builds and Baselines | Release Manager
Linaro.org | Open source software for ARM SoCs
The collocation facility hosting our servers suffered a major HVAC
failure. To compound matters, their monitoring network failed to notice
and temperatures got pretty hot for about 3 rows of racks (of which we
were one).
At this point, I think everything is back online but please let me know
if something isn't working properly. From what I can tell our servers
never got too hot or crashed (uptime seems to confirm this). It seems
like an upstream switch may have overheated and shut down.
On 09/17/2016 10:48 AM, Renato Golin wrote:
> Hi,
>
> Is the Austin colo offline? Did I miss some scheduled maintenance?
>
> I can't access aus-colo.linaro.org and all our public buildbots are down:
>
> http://lab.llvm.org:8011/builders/clang-cmake-aarch64-quick
>
> http://lab.llvm.org:8011/builders/clang-cmake-aarch64-full
>
> http://lab.llvm.org:8011/builders/clang-cmake-aarch64-42vma
>
> Let me know if I'm missing something, or when it comes back.
>
> Thanks!
> --renato
>
The Linaro git appear to be getting some very suspicious traffic on our
git protocol port. Its causing our servers to fail and effectively DOS
us. We are currently trying to block offending IPs. However, the number
of malicious IPs is growing and we may have to shut off the git protocol
daemon on our servers while we find a way to prevent this.
If you are using the "smart" protocol, https://git.linaro.org/.... you
will not be affected. If you aren't using the smart protocol, it might
be a good time to consider updating your .git/config files.
-andy