All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mariano Lopez <mariano.lopez@linux.intel.com>
To: bitbake-devel@lists.openembedded.org
Subject: [PATCH] bitbake: fetch2/git: Add URL when latest_revision generates an exception.
Date: Thu, 23 Apr 2015 13:17:45 -0500	[thread overview]
Message-ID: <55393749.4050002@linux.intel.com> (raw)

The URL is not sent when _latest_revision generates and exception.
When performing the sanity checks it is not possible to know the URI 
that failed.

This add the URL when latest_revision generates an exception.

[YOCTO: #7592]

Signed-off-by: mlopezva <mariano.lopez@linux.intel.com>
---
  bitbake/lib/bb/fetch2/git.py | 2 +-
  1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/bitbake/lib/bb/fetch2/git.py b/bitbake/lib/bb/fetch2/git.py
index 0fd9bee..0d91431 100644
--- a/bitbake/lib/bb/fetch2/git.py
+++ b/bitbake/lib/bb/fetch2/git.py
@@ -352,7 +352,7 @@ class Git(FetchMethod):
              for l in output.split('\n'):
                  if s in l:
                      return l.split()[0]
-        raise bb.fetch2.FetchError("Unable to resolve '%s' in upstream 
git repository in git ls-remote output" % ud.unresolvedrev[name])
+        raise bb.fetch2.FetchError("Unable to resolve '%s' in upstream 
git repository in git ls-remote output for %s" % 
(ud.unresolvedrev[name], ud.host+ud.path))

      def latest_versionstring(self, ud, d):
          """
-- 
1.8.4.5



             reply	other threads:[~2015-04-23 18:17 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-23 18:17 Mariano Lopez [this message]
  -- strict thread matches above, loose matches on Subject: below --
2015-04-27 16:15 [PATCH] bitbake: fetch2/git: Add URL when latest_revision generates an exception Mariano Lopez
2015-04-28 16:46 ` Richard Purdie
2015-05-13 11:24 mariano.lopez

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=55393749.4050002@linux.intel.com \
    --to=mariano.lopez@linux.intel.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 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.