Openembedded Bitbake Development
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Andreas Oberritter <obi@opendreambox.org>
Cc: bitbake-devel@lists.openembedded.org
Subject: Re: Git, AUTOREV and SSH
Date: Fri, 02 Mar 2012 16:23:54 +0000	[thread overview]
Message-ID: <1330705434.309.12.camel@ted> (raw)
In-Reply-To: <4F4D01A9.1010303@opendreambox.org>

On Tue, 2012-02-28 at 17:32 +0100, Andreas Oberritter wrote:
> On 28.02.2012 13:03, Richard Purdie wrote:
> > On Tue, 2012-02-28 at 12:52 +0100, Andreas Oberritter wrote:
> >> Hi,
> >>
> >> there's a problem with the Git fetcher when used with AUTOREV, at least
> >> with SSH URIs. "git ls-remote" may output warnings on stderr, e.g.:
> >>
> >> X11 forwarding request failed on channel 0
> >>
> >> When this happens, "X11" becomes the SRCREV and the fetcher subsequently
> >> fails. Certainly, other warnings by Git, SSH or a different SCM or
> >> transport could appear under other circumstances. Even localized strings
> >> may appear. Fetch2 merges stderr into stdout on purpose [1], so I'm not
> >> sure a proper fix should look like.
> >>
> >> Regards,
> >> Andreas
> >>
> >> [1] See runfetchcmd() in lib/bb/fetch2/__init__.py
> > 
> > Would the change in
> > http://lists.linuxtogo.org/pipermail/bitbake-devel/2012-January/001771.html help?
> > 
> > I've still not had a chance to rebase and apply that patch :(
> 
> Yes, this patch did help. See below for a rebased version. Thanks!

Thanks very much, I applied this.

Cheers,

Richard




      reply	other threads:[~2012-03-02 16:32 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-28 11:52 Git, AUTOREV and SSH Andreas Oberritter
2012-02-28 12:03 ` Richard Purdie
2012-02-28 16:32   ` Andreas Oberritter
2012-03-02 16:23     ` Richard Purdie [this message]

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=1330705434.309.12.camel@ted \
    --to=richard.purdie@linuxfoundation.org \
    --cc=bitbake-devel@lists.openembedded.org \
    --cc=obi@opendreambox.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