[cranky][PATCH] cranky-start: force maint-startnewrelease to be run locally

Marcelo Henrique Cerri marcelo.cerri at canonical.com
Thu Dec 6 18:08:59 UTC 2018

Starting with 4.18, we need to run cranky-start on the appropriate
schroot and that causes some issues when maint-startnewrelease tries to
reach the remote server via SSH and the SSH keys are not available on
the schroot.

Force cranky-start to alreasy run maint-startnewrelease locally. That
is a temporary workaround while cranky-start is not rewritten. Also
the impact of having to download the packages locally nowadays os very

Signed-off-by: Marcelo Henrique Cerri <marcelo.cerri at canonical.com>
 cranky/cranky-start | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/cranky/cranky-start b/cranky/cranky-start
index 083a0561dbcd..af181289fb41 100755
--- a/cranky/cranky-start
+++ b/cranky/cranky-start
@@ -62,7 +62,7 @@ class CrankyStart():
         cmd = os.path.realpath(
                          "..", "maintscripts",
-                         "maint-startnewrelease"))
+                         "maint-startnewrelease --local"))
         (rc, output) = run_command(cmd, dry_run=self.dry_run, dbg=self.debug)
         if rc != 0:
             cerror("Failed to create the start new release commit.")

More information about the kernel-team mailing list