All of lore.kernel.org
 help / color / mirror / Atom feed
From: dl9pf@gmx.de
To: yocto@yoctoproject.org
Subject: [PATCH] Fix connectivity check for BB_FETCH_PREMIRRORONLY case
Date: Tue,  5 Jan 2016 21:11:30 +0100	[thread overview]
Message-ID: <1452024690-31461-2-git-send-email-dl9pf@gmx.de> (raw)
In-Reply-To: <1452024690-31461-1-git-send-email-dl9pf@gmx.de>

From: Jan-Simon Möller <dl9pf@gmx.de>

BB_FETCH_PREMIRRORONLY sets BB_NO_NETWORK (implicitly in the fetcher).
To avoid the sanity check to fail in an offline environment,
use the same override mechanism as in the fetcher.

Signed-off-by: Jan-Simon Möller <dl9pf@gmx.de>
---
 meta/classes/sanity.bbclass | 3 +++
 1 file changed, 3 insertions(+)

diff --git a/meta/classes/sanity.bbclass b/meta/classes/sanity.bbclass
index ad9dda8..62dce92 100644
--- a/meta/classes/sanity.bbclass
+++ b/meta/classes/sanity.bbclass
@@ -271,6 +271,9 @@ def check_connectivity(d):
     test_uris = (d.getVar('CONNECTIVITY_CHECK_URIS', True) or "").split()
     retval = ""
 
+    # Check for BB_FETCH_PREMIRRORONLY and adapt BB_NO_NETWORK
+    if bb.data.getVar("BB_FETCH_PREMIRRORONLY", self.d, True) is not None:
+        bb.data.setVar("BB_NO_NETWORK", "1", self.d)
     # Only check connectivity if network enabled and the
     # CONNECTIVITY_CHECK_URIS are set
     network_enabled = not d.getVar('BB_NO_NETWORK', True)
-- 
2.6.2



  reply	other threads:[~2016-01-05 20:17 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-05 20:11 [PATCH] Fix connectivity check for BB_FETCH_PREMIRRORONLY case dl9pf
2016-01-05 20:11 ` dl9pf [this message]
2016-01-07 23:42   ` Burton, Ross
2016-01-15 20:38     ` Jan-SImon Möller
  -- strict thread matches above, loose matches on Subject: below --
2016-01-05 20:17 [PATCH] [master, jethro] " dl9pf
2016-01-05 20:17 ` [PATCH] " dl9pf
2015-12-17 21:34 dl9pf
2015-12-17 20:58 dl9pf

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=1452024690-31461-2-git-send-email-dl9pf@gmx.de \
    --to=dl9pf@gmx.de \
    --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.