From: agustin.benito@codethink.co.uk (Agustin Benito Bethencourt)
To: cip-dev@lists.cip-project.org
Subject: [cip-dev] kernelci setup fails
Date: Tue, 17 Jan 2017 18:14:11 +0100 [thread overview]
Message-ID: <587E50E3.3080202@codethink.co.uk> (raw)
In-Reply-To: <bf0051c6-fa6f-3ed0-a578-b1cc5e9142bc@siemens.com>
Hi,
On 17/01/17 17:32, Daniel Wagner wrote:
> Hi Don,
>
> On 01/17/2017 05:04 PM, Don Brown wrote:
>> I have the same problem and worked on it yesterday from several angles.
>> My notes are logged in Issue #12 in the GitLab repo. The link is:
>>
>> https://gitlab.com/cip-project/testing/issues/12
>
> I'll create a gitlab account soon, so that I can collaborate via the
> ticket system.
until then...
We have discussed what to do. There are several options:
1 Make Python 3.5.2 work on trusty.
2 Move on to Ubuntu 16.04
3 Move to an in-between version.
4 Try to move it into Debian so we can go for a single VM for the whole
kernelci tolling.
Don is describing in the gitlab ticket his early tries of each option to
determine which way to go. Although #4 is the desired one, it seems the
most difficult one as well, so we decided to focus on the initial three.
We want to have the system working first and then we will figure out how
we can simplify the deployment.
Best Regards
--
Agustin Benito Bethencourt
Principal Consultant - FOSS at Codethink
agustin.benito at codethink.co.uk
next prev parent reply other threads:[~2017-01-17 17:14 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-17 16:04 [cip-dev] kernelci setup fails Don Brown
2017-01-17 16:32 ` Daniel Wagner
2017-01-17 17:14 ` Agustin Benito Bethencourt [this message]
-- strict thread matches above, loose matches on Subject: below --
2017-01-19 2:55 Don Brown
2017-01-17 8:49 Daniel Wagner
2017-01-17 14:05 ` Agustin Benito Bethencourt
2017-01-17 14:43 ` Daniel Wagner
2017-01-17 16:36 ` Daniel Wagner
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=587E50E3.3080202@codethink.co.uk \
--to=agustin.benito@codethink.co.uk \
--cc=cip-dev@lists.cip-project.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox