Openembedded Bitbake Development
 help / color / mirror / Atom feed
From: Martin Jansa <martin.jansa@gmail.com>
To: bitbake-devel@lists.openembedded.org
Subject: Re: [PATCHv3] git: remove symling before updating mirror tarball
Date: Fri, 10 May 2013 11:35:35 +0200	[thread overview]
Message-ID: <20130510093535.GH3188@jama> (raw)
In-Reply-To: <20130507215108.GA3188@jama>

[-- Attachment #1: Type: text/plain, Size: 1120 bytes --]

On Tue, May 07, 2013 at 11:51:08PM +0200, Martin Jansa wrote:
> On Tue, May 07, 2013 at 06:39:20PM +0200, Martin Jansa wrote:
> > * with read-only PREMIRROR (e.g. mounted over NFS or CIFS
> >   and referenced as file:///mnt/premirror) we cannot use
> >   BB_GENERATE_MIRROR_TARBALLS because all git2_abc.git.tar.gz
> >   files later became just symlinks to read-only location in PREMIRROR
> >   (it works fine on first build and for new components, because
> >   at that time there isn't tarball on PREMIRROR yet).
> > 
> >   ERROR: Fetcher failure: Fetch command failed with exit code 141, output:
> >   tar (child): /build/downloads/git2_abc.git.tar.gz: Cannot open: Read-only file system
> >   tar (child): Error is not recoverable: exiting now
> 
> This one is tested and I would like to get it also in 1.16 and 1.18

cherry-picking 3627b02f77c78beedadadd77c619b9e5edaae076 works fine for
both, do you prefer to send patches with [1.16]/[1.18] in subject or
should I just wait a bit more with patch in master and then ping you
later?

-- 
Martin 'JaMa' Jansa     jabber: Martin.Jansa@gmail.com

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 205 bytes --]

  parent reply	other threads:[~2013-05-10  9:54 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-30 10:52 [RFC] git: add BB_FETCH_PREMIRROR_READONLY option Martin Jansa
2013-04-30 12:57 ` Paul Eggleton
2013-04-30 14:46   ` Martin Jansa
2013-05-03 15:58   ` [PATCHv2] git: remove symling before updating mirror tarball Martin Jansa
2013-05-07 16:39   ` [PATCHv3] " Martin Jansa
2013-05-07 21:51     ` Martin Jansa
2013-05-07 22:10       ` Martin Jansa
2013-05-10  9:35       ` Martin Jansa [this message]
2013-05-10 12:32         ` Richard Purdie

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=20130510093535.GH3188@jama \
    --to=martin.jansa@gmail.com \
    --cc=bitbake-devel@lists.openembedded.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