Migration stops if .ssh dir is missing

[tobias--]

• Gitea version (or commit ref): 1.1.0
• Git version: 2.10.0.windows.1
• Operating system: Windows Server 2008 R2
• Database (use [x]):
  • PostgreSQL
  • MySQL
  • MSSQL
  • SQLite
• Can you reproduce the bug at https://try.gitea.io:
  • Yes (provide example URL)
  • No
  • Not relevant
• Log gist:

2017/03/10 08:25:22 [I] Log Mode: File(Trace)
2017/03/10 08:25:22 [I] XORM Log Mode: File(Trace)
2017/03/10 08:25:22 [I] Cache Service Enabled
2017/03/10 08:25:22 [I] Session Service Enabled
2017/03/10 08:25:22 [I] Mail Service Enabled
2017/03/10 08:25:22 [I] Notify Mail Service Enabled
2017/03/10 08:25:22 [I] Migration: create user column allow create organization
2017/03/10 08:25:22 [I] Migration: create repo unit table and add units for all repos
2017/03/10 08:25:22 [I] Migration: set protect branches updated with created
2017/03/10 08:25:22 [I] Migration: add external login user
2017/03/10 08:25:22 [I] Migration: generate and migrate Git hooks
2017/03/10 08:25:23 [I] Migration: use new avatar path name for security reason
2017/03/10 08:25:24 [I] Migration: rewrite authorized_keys file via new format
2017/03/10 08:25:24 [...itea/routers/init.go:54 GlobalInit()] [E] Failed to initialize ORM engine: migrate: do migrate: open C:\Windows\system32\config\systemprofile\.ssh\authorized_keys.tmp: The system cannot find the path specified.

Description

Migration from 1.0.2 to 1.1.0 fails when the folder C:\Windows\system32\config\systemprofile\.ssh does not exist. Since SSH has been disabled in this setup, there never were authorized keys that need to be migrated.

After creating this directory, gitea starts up just fine.