All of lore.kernel.org
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: news@christianvolk.net
Cc: bitbake-devel@lists.openembedded.org
Subject: Re: BitBake & ClearCase
Date: Tue, 13 Nov 2012 14:28:37 +0000	[thread overview]
Message-ID: <1352816917.24487.130.camel@ted> (raw)
In-Reply-To: <20121113123509.Horde.cZcPJLuWis5QojBtb0_w6KA@webmail.df.eu>

On Tue, 2012-11-13 at 12:35 +0100, news@christianvolk.net wrote:
> Dear bitbake-developer-community,
> 
> I just stumbled across a problem and knows of no other advice than to  
> write to you here:
> 
> In my company we have to use bitbake in combination with ClearCase (CC).
> Bitbake has some problems with the ClearCase-owned files called  
> ?.copyarea.db?.
> Unfortunately, CC adds such a file to each directory which is under  
> source-control.
> The file is read-only and so the task do_unpack fails with the  
> following error message:
> 
> cp: cannot create regular file  
> `/home/[...]/testability-1.0-r0/./testability_src_gen/.copyarea.db':  
> Permission Denied

I'm a little confused about what the real problem is here. cp should be
able to cope with a file that is marked as read-only. Is this saying the
target already exists and can't be written to? Or is it unable to read
from the source? Is the source locked?

Worst case you can implement a custom "unpack" function for your
clearcase fetcher like git does and in there, exclude the problematic
files.

Cheers,

Richard





  reply	other threads:[~2012-11-13 14:42 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-11-13 11:35 BitBake & ClearCase news
2012-11-13 14:28 ` Richard Purdie [this message]
2012-11-13 16:28   ` Mark Hatle

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=1352816917.24487.130.camel@ted \
    --to=richard.purdie@linuxfoundation.org \
    --cc=bitbake-devel@lists.openembedded.org \
    --cc=news@christianvolk.net \
    /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.