public inbox for cip-dev@lists.cip-project.org
 help / color / mirror / Atom feed
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 15:05:00 +0100	[thread overview]
Message-ID: <587E248C.2090002@codethink.co.uk> (raw)
In-Reply-To: <f6c5c137-3fc9-c175-4889-5cf16480f167@monom.org>

Hi Daniel

On 17/01/17 09:49, Daniel Wagner wrote:
> Hi,
>
> running 'vagrant up' from a clean setup consistently fails with this:
>
>
> ==> default: TASK [setup] *******************************************************************
> ==> default: ok: [kernel-ci-backend]
> ==> default:
> ==> default: TASK [common : Tweak kernel configuration for performance] *********************
> ==> default: changed: [kernel-ci-backend]
> ==> default:
> ==> default: TASK [install-deps : Install OS dependencies] **********************************
> ==> default: failed: [kernel-ci-backend] (item=[u'build-essential', u'git', u'lsb-release', u'python-apt', u'python-pip', u'python-pycurl', u'python-virtualenv', u'python2.7-dev', u'sysfsutils', u'python3', u'python3-yaml', u'python3-setproctitle', u'python3-zmq']) => {"failed": true, "item": ["build-essential", "git", "lsb-release", "python-apt", "python-pip", "python-pycurl", "python-virtualenv", "python2.7-dev", "sysfsutils", "python3", "python3-yaml", "python3-setproctitle", "python3-zmq"], "msg": "No package matching 'python3-setproctitle' is available"}
>
>
> A quick search for setproctitle tells me it is installed via
>
> 	kernelci-backend-config/roles/install-deps/tasks/main.yml:    - python3-setproctitle
>
> But ubuntu doesn't seem to know this package:
>
> vagrant at vagrant-ubuntu-trusty-64:~$ apt-cache search setproctitle
> libbsd-dev - utility functions from BSD systems - development files
> python-setproctitle - A setproctitle implementation for Python
> python-setproctitle-dbg - A setproctitle implementation for Python
>
>
> I haven't spend time to figure out what this package is doing or
> how it used. So my quick question how to fix this?

maybe this helps?

https://gitlab.com/cip-project/testing/issues/12

If this is your case, Don is on it. He talked to one of the kernelci 
developers, Milo Casagrande about it.

>
> cheers,
> daniel
> _______________________________________________
> cip-dev mailing list
> cip-dev at lists.cip-project.org
> https://lists.cip-project.org/mailman/listinfo/cip-dev
>

-- 
Agustin Benito Bethencourt
Principal Consultant - FOSS at Codethink
agustin.benito at codethink.co.uk

  reply	other threads:[~2017-01-17 14:05 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-17  8:49 [cip-dev] kernelci setup fails Daniel Wagner
2017-01-17 14:05 ` Agustin Benito Bethencourt [this message]
2017-01-17 14:43   ` Daniel Wagner
2017-01-17 16:36     ` Daniel Wagner
  -- strict thread matches above, loose matches on Subject: below --
2017-01-17 16:04 Don Brown
2017-01-17 16:32 ` Daniel Wagner
2017-01-17 17:14   ` Agustin Benito Bethencourt
2017-01-19  2:55 Don Brown

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=587E248C.2090002@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