From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: "Maier, Chris" <C.Maier@geze.com>,
"yocto@yoctoproject.org" <yocto@yoctoproject.org>
Subject: Re: do_rootfs OSError: [Errno 13] Permission denied
Date: Tue, 19 Jul 2016 13:47:16 +0100 [thread overview]
Message-ID: <1468932436.22733.1.camel@linuxfoundation.org> (raw)
In-Reply-To: <2AA7D088591C49498E92D6491C58159334C887BF@gcxdb1.corp.geze.com>
On Tue, 2016-07-19 at 07:17 +0000, Maier, Chris wrote:
> Hello together,
>
> I ran into an “Permission denied” error while trying to setup a
> nightly build on our Jenkins server and I can’t figure out where the
> problem comes from.
> It seems that the problem is coming from creating and executing a
> child process, but why?
>
> The build is working fine on my linux machine but it doesn’t finish
> successfully on the server (SUSE Linux Enterprise Server 12 SP1
> (x86_64)).
>
> The build log and the error message is attached.
>
> What I already did:
> - Checking the file system space (11GB left)
> - Deleted the whole build directory and did a rebuild
> - Checked the filesystem permission, seems normal. It all
> belongs to user and group Jenkins.
It looks like you have the source code under svn control and its
finding a .svn directory in the "intercepts" directory and trying to
execute it. I'm guessing this is the scripts/postinst-intercepts
directory where its finding it.
Somehow you'd need to teach the code to skip the .svn directory, remove
that directory before the build or use a different source control
system.
Cheers,
Richard
next prev parent reply other threads:[~2016-07-19 12:47 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-19 7:17 do_rootfs OSError: [Errno 13] Permission denied Maier, Chris
2016-07-19 12:47 ` Richard Purdie [this message]
2016-07-19 14:16 ` Maier, Chris
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=1468932436.22733.1.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=C.Maier@geze.com \
--cc=yocto@yoctoproject.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.