Getting Robot-OS packaged [BB-101 100%] (week 51)
More copyright review, package review and uploading
Fixes for multiarch
Status page: https://wiki.debian.org/DebianScience/Robotics/ROS/Packages
LEG sprint, Cambridge [BB-241 100%]: (week50)
Move debian kernel packaging forward to 4.4 to match DO2 kernel
Produce script to merge D02 kernel branch with Debian packaging [BB-242]
Produce script to build debian-installer with above kernel [BB-243]
Wookey
--
Principal hats: Linaro, Debian, Wookware, ARM
http://wookware.org/
Hello,
We upgraded from Gerrit 2.8 to 2.10 in the beginning of September, and
it went pretty smooth and let us overcome few annoying issues and enjoy
few new features and better integration with other apps.
Unfortunately, 3 months later, 2.10 also feels old, with 2.12 having
been released in the interim. With various Linaro groups continuing to
leverage advanced Gerrit features and integrations with other apps
(Jenkins, Bugzilla), Systems team faces various bugs and issues. None
of these issues are too grave, but they're quite convoluted and take
much time to be researched and understood. And then we find out that
it's a known issue in 2.10, which was fixed in later versions.
Jenkins' Gerrit integration already requires 2.12 for full
functionality and warns about our version being too old and some
features not supported. Which in turns brings concerns that every
time it doesn't work as expected, it may be because Gerrit plugin is
no longer tested with 2.10 and hits some issue pertaining to it.
With that in mind, Systems team would like to start planning for
next Gerrit upgrade, and move straight to the latest, 2.12.
To remind, the reason we didn't upgrade to 2.11 last time, was because
2.10 was the last version which included old-style change review
screen, and we wanted to provide smoother transition and let people to
try the new screen at their own pace. So, if you still use the old
design, please go to https://review.linaro.org/#/settings/preferences ,
and in "Change View:" dropdown, select "New Screen", and give it a
chance with the help of this doc:
https://review.linaro.org/Documentation/user-review-ui.html
And if you have any concerns regarding the upgrade, please speak up now.
Otherwise, we can do it in one of the following timeframes:
1. Upgrade in January.
2. Upgrade a bit later, but still before the Connect.
3. Discuss and plan upgrade at the Connect.
Systems team votes for the choice 1, upgrade next month (apparently, by
the end of), as that will allows us to deliver smoother Gerrit
experience to other teams, instead of firefighting older version issues.
Thanks,
Paul
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
I am referring to the thread:
https://lists.linaro.org/pipermail/linaro-dev/2012-September/013311.html
I am facing the exact issue and i want to check where it is hanging.
Am not sure if it is hanging at the xloader or not.
Do i need to build Linux, X-Loader and u-boot with debug symbols for
me to debug using lauterbach.
Can you list out the steps i need to follow to make sure i can debug
this. Also, Will the debugger reset the processor when i try to
connect when reboot fails.
Thanks for your assistance.
thanks,
ryan
Hello,
Is the package *linux-tools-3.15.0* available with Linaro 12.11 ?
This package is required for using the *perf *command but when trying to
install this package, I am getting an *unable to locate *error. Can
somebody please help....
Thanks,
Ginu
Hello,
I use Zedboard with ARM core running Linaro for my experiments. For a
specific experiment, I need to use the perf command. I followed the page:
https://wiki.linaro.org/Platform/DevPlatform/Tools/Perf
and used the command *sudo apt-get install linux-linaro-12.11-tools* but I
am getting*:*
Reading package lists... Done
Building dependency tree
Reading state information... Done
E: Unable to locate package linux-linaro-12.11-tools
E: Couldn't find any package by regex 'linux-linaro-12.11-tools'
The commands lsb_release -a and uname -a gives:
$lsb_release -a
No LSB modules are available.
Distributor ID: Linaro
Description: Linaro 12.11
Release: 12.11
Codename: precise
$uname -a
Linux zed2 3.15.0-xilinx+ #16 SMP PREEMPT Thu Mar 12 22:24:14 SGT 2015
armv7l armv7l armv7l GNU/Linux
Is there something that I would be missing?
Thank you,
Ginu
Please let us know if you are using OpenID authentication with LAVA.
Newer versions of django will make it impossible to support
django-openid-auth in Debian unstable and testing. The version of
django-openid-auth in Jessie can continue to be used, so we would like
to know how many users want to continue with this support.
OpenID as a protocol has been dying for some time and Linaro has moved
over to LDAP, which is fine if LDAP is already available.
The time pressure for this change is coming from the schedule to get
the latest django and the latest lava packages into Ubuntu Xenial
16.04LTS which means that support needs to be implemented in the
2015.12 or 2016.1 LAVA releases. This is why this is quickly following
the trusty change. We have been aware of the issues with
django-openid-auth for some time, it was only when we had completed
the move of the Cambridge lab to LDAP that changes involving
django-openid-auth could be considered.
If you are using OpenID authentication (e.g. using Launchpad or Google
OpenID), please let us know.
If you would like to see some other forms of authentication supported,
also let us know. We can investigate Python Social Auth
(http://psa.matiasaguirre.net/), if there is interest.
If we don't hear from users who want django-openid-auth support for
use on Debian Jessie, we will drop django-openid-auth support from all
lava builds. This will leave LDAP and local Django accounts in
2015.12.
If anyone has experience of other django authentication modules, also
let us know.
--
Neil Williams
=============
neil.williams(a)linaro.org
http://www.linux.codehelp.co.uk/
See also:
https://lists.linaro.org/pipermail/lava-announce/2015-November/000002.html
which was also sent to these lists (except linaro-dev).
So far, nobody has come forward as a Trusty user. The only Trusty
instance of which we are aware is already due to migrate to Debian
Jessie.
The LAVA software team are now applying updates which will freeze LAVA
software support for Ubuntu Trusty at 2015.9 for lava-dispatcher and
2015.9.post1 for lava-server due to the complexities of supporting
both django1.6 and the current django1.7 in Jessie and django1.8,
possibly django1.9 by the time Debian Stretch is released.
The last packages for Ubuntu Trusty 14.04LTS will be:
lava-server 2015.9.post1
lava-dispatcher 2015.9
Once these changes are applied, the Debian packaging used to build
future versions of LAVA packages will prevent builds against django1.6
and prevent installation if django1.6 is found, in order to prevent
database corruption.
This means that Trusty users will not be able to use the results of
the dispatcher refactoring.
Ubuntu Xenial Xerus - which is planned to be the 16.04LTS in April
2016 - is expected to pick up LAVA software releases from Debian up
until the 2016.1 release (possibly 2016.2) and is also expected to be
using django1.8. The next Debian stable release (Stretch), for which
no date has yet been set, may use django1.9.
Initial attempts at migrating a test instance from Trusty to django1.7
did not go well and the migration from Trusty to Xenial cannot be
supported by the LAVA software team - the recommendation is to go
directly from 2015.9 on Trusty to the same version available for
Debian Jessie but there will still be work to be done to prepare and
implement the migration which will be instance-dependent.
Documentation is being added to assist with this migration but there
will remain risks of data loss which will need to be managed for each
instance. It is imperative that anyone using Trusty has an up to date
backup of the postgresql database dump before considering any
migration. If the existing data is to be dropped, a new install on
Debian Jessie is recommended.
It is not possible for the LAVA software team to support all versions
of django from 1.6 to 1.9 - particular problems are known when going
from django1.6 to django1.7 as the methods to migrate the lava-server
database changed fundamentally in django1.7.
Notes are being added to the documentation on the trusty branch based
on 2015.9 to be released within lava-server 2015.9.post1 and to the
documentation in the master branch (which will go into 2015.12).
All future builds of LAVA software will now be made and uploaded only
to Debian and releases.linaro.org.
So far, nobody has come forward who is willing to maintain packaging
for LAVA software on any distribution other than Debian. As the
refactoring proceeds, we expect that it will become easier to package
LAVA for other distributions but the migration to the refactoring must
be complete first.
Everyone interested in or using LAVA is encouraged to subscribe to the
lava-announce mailing list which is low volume and only used for
substantial changes like this.
https://lists.linaro.org/mailman/listinfo/lava-announce
See also https://validation.linaro.org/static/docs/support.html
--
Neil Williams
=============
neil.williams(a)linaro.org
http://www.linux.codehelp.co.uk/
Does anyone have instructions on modding the chromebook 2 Peach Pi such
that it is not necessary to hit ctrl-U when booting custom kernels? I
found some instructions (which may be incomplete) for the SS Chromebook
"snow" suggesting it may be possible.
thanks,
Steve
