[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#783668: d-i.debian.org: investigate $DI/scripts/l10n/l10n-sync's output after dillon's upgrade to jessie



Quoting Cyril Brulebois (kibi@debian.org):
> Package: d-i.debian.org
> Severity: normal
> 
> The nightly $DI/scripts/l10n/l10n-sync cron job has a rather
> scary/verbose output after dillon's upgrade to jessie.


warning: push.default is unset; its implicit value has changed in
Git 2.0 from 'matching' to 'simple'. To squelch this message
and maintain the traditional behavior, use:

  git config --global push.default matching

To squelch this message and adopt the new behavior now, use:

  git config --global push.default simple

When push.default is set to 'matching', git will push local branches
to the remote branches that already exist with the same name.

Since Git 2.0, Git defaults to the more conservative 'simple'
behavior, which only pushes the current branch to the corresponding
remote branch that 'git pull' uses to update the current branch.

See 'git help config' and search for 'push.default' for further information.
(the 'simple' mode was introduced in Git 1.7.11. Use the similar mode
'current' instead of 'simple' if you sometimes use older versions of
Git)

Well, we clearly have two solutions here:
-either set push.default on dillon (and all other places where the
l10n-sync utility is run from....though there are no others as of now)

-or hardcode "--global push.default simple" (or matching, it doesn't
really matter here) in the l10n-sync script

I'd reather choose the first choice (and hope I still find the Right
Way to sudo as d-i on dillong in order to do it...as well as the
needed "svn upgrade" command in packages/po) but prefer waiting for
your input, Cyril.




Attachment: signature.asc
Description: Digital signature


Reply to: