| Message ID | 20181206180859.14842-1-marcelo.cerri@canonical.com |
|---|---|
| State | New |
| Headers | show |
| Series | [cranky] cranky-start: force maint-startnewrelease to be run locally | expand |
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( os.path.join(os.path.dirname(__file__), "..", "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.")
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 small. Signed-off-by: Marcelo Henrique Cerri <marcelo.cerri@canonical.com> --- cranky/cranky-start | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)