Closed Bug 490151 Opened 16 years ago Closed 15 years ago

Use l10n default branch tip instead (latest branch) tip for l10n tb nightlies

Categories

(Mozilla Messaging Graveyard :: Server Operations, defect, P2)

defect

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: stef, Assigned: gozer)

References

Details

User-Agent: Mozilla/5.0 (X11; U; Linux i686; pl; rv:1.9.1b3) Gecko/20090305 Firefox/3.1b3 Build Identifier: Recently Firefox 35b4 release tag and branch was added to l10n repos, it breaks l10n tb nightlies, some at least (when there are changes between opted fx rev and tag rev, like pl ones). We should use default branch tip instead last branch tip for nightlies l10n source. http://tinderbox.mozilla.org/showbuilds.cgi?tree=Mozilla-l10n-pl&maxdate=1240552081&hours=24&legend=0&norules=1 http://hg.mozilla.org/releases/l10n-mozilla-1.9.1/pl/pushloghtml Reproducible: Always
The problem remains, fx35rc1 branch was added and builds are broken once again...
Blocks: 470669
Component: Release Engineering → Server Operations
Summary: Use l10n default tip instead tip for l10n tb nightlies → Use l10n default branch tip instead (latest branch) tip for l10n tb nightlies
Assignee: nobody → gozer
problem remains: fx35rc1 release tag added, and now Polish Thunderbird and SeaMonkey builds are burning: http://tinderbox.mozilla.org/showlog.cgi?log=Mozilla-l10n-pl/1244810991.1244811379.17465.gz (the "missing" stuff was added few hours earlier: http://hg.mozilla.org/releases/l10n-mozilla-1.9.1/pl/rev/9b396569d235 )
Manually brought Thunderbird linux/mac/win32 l10n checkouts back onto the default branch.
The new-style repack harness does this correctly, FWIW, one more argument to get it deployed everywhere ;-)
(In reply to comment #4) > The new-style repack harness does this correctly, FWIW, one more argument to > get it deployed everywhere ;-) Adding deps on bug 494577 and bug 496368 as I believe that's what is needed here.
Status: UNCONFIRMED → NEW
Depends on: 494577, 496368
Ever confirmed: true
Assuming we pick the new repack harness up in bug 470673 that should help fix this as well.
Depends on: 470673
Priority: -- → P3
Priority: P3 → P2
Resolved as a side effect of closing bug 470673.
Status: NEW → RESOLVED
Closed: 15 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.