Port bug 1484264, Move repackage configuration from mozharness into taskcluster.

RESOLVED FIXED in Thunderbird 64.0

Status

enhancement
RESOLVED FIXED
Last year
11 months ago

People

(Reporter: Pike, Assigned: rjl)

Tracking

unspecified
Thunderbird 64.0
Dependency tree / graph

Thunderbird Tracking Flags

(thunderbird63 fixed, thunderbird64 fixed)

Details

Attachments

(1 attachment)

Thunderbird repacks die right now, due to bug 1484264 moving things around.
Duplicate of this bug: 1488187
Move repackage configuration from mozharness into taskcluster.
Assignee: nobody → rob
Status: NEW → ASSIGNED
Comment on attachment 9006042 [details]
Bug 1488045 - Port Bug 1488045: Move repackage configuration from mozharness into taskcluster. r?tomprince

Tom Prince [:tomprince] has approved the revision.
Attachment #9006042 - Flags: review+
Attachment #9006042 - Attachment description: Bug 1488045 - Port Bug 1488045. r?tomprince → Bug 1488045 - Port Bug 1488045: Move repackage configuration from mozharness into taskcluster. r?tomprince
When I tried Lando yesterday, I got:
Error: We're sorry, Autoland could not rebase your commits for you automatically. Please manually rebase your commits and try again. 

I've imported the patch with |hg phabread D4880 > .hg/patches/D4880.patch| and it applies just fine. Will land tonight.
Pushed by mozilla@jorgk.com:
https://hg.mozilla.org/comm-central/rev/c1a9f19c8216
Port Bug 1488045: Move repackage configuration from mozharness into taskcluster. r=tomprince
Status: ASSIGNED → RESOLVED
Closed: Last year
Resolution: --- → FIXED
Target Milestone: --- → Thunderbird 64.0
Attachment #9006042 - Flags: approval-comm-beta+
Comment on attachment 9006042 [details]
Bug 1488045 - Port Bug 1488045: Move repackage configuration from mozharness into taskcluster. r?tomprince

https://hg.mozilla.org/releases/comm-esr60/rev/53ff0406316f42ce375393245de88b383868770e

Moved the "(comm-esr60|try-comm-central):" corrections to bug 1487286 where they belong.
Attachment #9006042 - Flags: approval-comm-esr60+
You need to log in before you can comment on or make changes to this bug.