Closed Bug 378877 Opened 18 years ago Closed 8 years ago

Lightning nightly branch builds not current

Categories

(Calendar :: Website, defect)

x86
Windows XP
defect
Not set
major

Tracking

(Not tracked)

RESOLVED WORKSFORME

People

(Reporter: worcester12345, Unassigned)

References

()

Details

User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1.4pre) Gecko/20070423 BonEcho/2.0.0.4pre Build Identifier: Lightning nightly builds for Thunderbird 2.0 Has the branch build machine stopped working? The latest I see at http://ftp.mozilla.org/pub/mozilla.org/calendar/lightning/nightly/latest-mozilla1.8/windows-xpi/ is from 4/23/2007. Reproducible: Always Steps to Reproduce: 1.Go to web site. 2.Look for nightly build. 3.Don't find nightly build. Actual Results: No nightly builds since 4/23/2007 available. Expected Results: Nightly build from 4/25 or 4/26. Under "components" for producing this bug, there was no "build" component. I was thinking of putting it in "general" or "lightning only", but thought this is the best place for it.
Might be a tinderbox issue because todays nightly build is available from <http://ftp.mozilla.org/pub/mozilla.org/calendar/lightning/nightly/2007-04-26-05-mozilla1.8/>
(In reply to comment #2) > Might be a tinderbox issue because todays nightly build is available from > <http://ftp.mozilla.org/pub/mozilla.org/calendar/lightning/nightly/2007-04-26-05-mozilla1.8/> > Yes, that could be it. Feel free to change this bug's description, product, or component if this isn't the best place for it; or add it as a blocker or blocked by the appropriate other bugs.
I see 28-Apr-2007 builds for all platforms in latest-mozilla1.8 folder -> resolving WFM
Status: UNCONFIRMED → RESOLVED
Closed: 18 years ago
Resolution: --- → WORKSFORME
Now broken again.
Status: RESOLVED → UNCONFIRMED
Resolution: WORKSFORME → ---
Please, do not re-open 10 year old bug reports but open a new one.
Status: UNCONFIRMED → RESOLVED
Closed: 18 years ago8 years ago
Resolution: --- → WORKSFORME
Depends on: 1493008
You need to log in before you can comment on or make changes to this bug.