Dan Bungert has proposed merging ~dbungert/curtin:log-source-handler into
curtin:master.
Commit message:
extract: log source information
If you try hard enough and follow mount commands backwards you can
surely get this same information, but when analyzing what the extract is
actually doing it's nice to just be able to see what the image stack is.
Requested reviews:
curtin developers (curtin-dev)
For more details, see:
https://code.launchpad.net/~dbungert/curtin/+git/curtin/+merge/451309
--
Your team curtin developers is requested to review the proposed merge of
~dbungert/curtin:log-source-handler into curtin:master.
diff --git a/curtin/commands/extract.py b/curtin/commands/extract.py
index fc7749c..206790e 100644
--- a/curtin/commands/extract.py
+++ b/curtin/commands/extract.py
@@ -114,6 +114,7 @@ class LayeredSourceHandler(AbstractSourceHandler):
def setup(self):
self._tmpdir = tempfile.mkdtemp()
+ LOG.debug(f"Setting up Layered Source for stack {self.image_stack}")
try:
self._download()
# Check that all images exists on disk and are not empty
@@ -158,6 +159,7 @@ class TrivialSourceHandler(AbstractSourceHandler):
self.path = path
def setup(self):
+ LOG.debug(f"Setting up Trivial Source for stack {self.path}")
return self.path
def cleanup(self):
--
Mailing list: https://launchpad.net/~curtin-dev
Post to : curtin-dev@lists.launchpad.net
Unsubscribe : https://launchpad.net/~curtin-dev
More help : https://help.launchpad.net/ListHelp
