Comment 4 for bug 1297559

also fixed in 1.19 by ditching git.

On Fri, May 9, 2014 at 3:43 PM, Ryan Finnie <email address hidden>wrote:

> Got it. git (at least in trusty) does not copy over the repo configs
> when doing a clone, so user.email and user.name do not get copied from
> the source repository. And since $HOME is not set, --global is not
> referenced. And in environments where the hosts domain name is not set
> e.g. trusty (cloud-init change between precise and trusty?), git tries
> and fails to set a default email address, and we go into this loop.
>
> The referenced branch fixes this by setting user.name and user.email
> directly when cloning a git repo. Please consider applying this to the
> 1.18 line, as the problem severely breaks 1.18+trusty+(openstack,
> possibly others).
>
> ** Branch linked: lp:~fo0bar/juju-core/1.18-lp1297559
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1297559
>
> Title:
> upgrade-charm fails because of git
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/juju-core/+bug/1297559/+subscriptions
>