dashboard was stuck, kicked it

[Axel Hecht]

Hi,

the dashboard was stuck again, I gave it a kick, and I think I reran all
the things that landed.

If you're missing an updated compare result, send me an email?

Axel

[Kim Ludvigsen]

Den 21-12-2014 kl. 13:38 Axel Hecht wrote:

> the dashboard was stuck again, I gave it a kick, and I think I reran all
> the things that landed.

The kick may have upset the dashboard, as it now refuse to acknowledge
that all strings on Firefox beta has been dealt with for the Danish
locale. Or perhaps you just introduced a lot of string changes in
browser.dtd?

Earlier in the day I did the missing 19 strings related to the new
search UI. After not being able to see the change in the dashboard
earlier today I returned now in hope of seeing a nice "Translated" -
only to find a notice of 47 missing strings and 14 obsolete strings.

--
Kind regards
Kim Ludvigsen

[Sebastian Hengst]

-------- Original-Nachricht --------
Betreff: Re: dashboard was stuck, kicked it
Von: Kim Ludvigsen <lud...@kimludvigsen.dk>
Datum: 2014-12-21 16:57

These strings are missing from the Danish localization:
http://hg.mozilla.org/releases/l10n/mozilla-beta/da/file/33ed757c0486/browser/chrome/browser/browser.dtd

They have been removed by this push (merge missing when pushing?):
http://hg.mozilla.org/releases/l10n/mozilla-beta/da/rev/33ed757c0486#l1.228

Cheers
Sebastian

[Kim Ludvigsen]

Den 21-12-2014 kl. 17:08 Sebastian Hengst wrote:

> These strings are missing from the Danish localization:
> http://hg.mozilla.org/releases/l10n/mozilla-beta/da/file/33ed757c0486/browser/chrome/browser/browser.dtd

Ok, so they /are/ missing. I will translate them (again).

> They have been removed by this push (merge missing when pushing?):
> http://hg.mozilla.org/releases/l10n/mozilla-beta/da/rev/33ed757c0486#l1.228

Almost every time there is a merge, I have problems with the headers. So
almost every time, I simply make a new clone.

And now I realize what I did wrong: This time I had made the 19 new
strings first before running into the problem with the headers. I made a
new clone, but by mistake I used the old browser.dtd that I already had
in my editor.

Thanks for the help!

[Axel Hecht]

Note, there's the "new head" vs "new head" problem.

You want to check if there's stuff you don't know about on the remote,
i.e., run

hg inc

before you push.

If that empty, check

hg heads default

That's gonna tell you how many heads you have, ignoring the release
branches.

If that's just one, you should totally

hg push -f

Note, `hg push -f` never overwrites our "there's only one head per
branch" server-side hook. So you can, mostly, use that one liberally.

Also, you should update your local hg client. New clients might not be
picky in the same way old clients are.

Also, security update recently, you know.

Axel