Closed Bug 332900 Opened 18 years ago Closed 17 years ago

move sunbird/lightning to linux ref platform

Categories

(Release Engineering :: General, defect)

x86
Linux
defect
Not set
blocker

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: dmosedale, Assigned: coop)

References

Details

Since the cairo-on-linux switch was flipped today, galactica Sunbird builds turned red because the version of pango on that machine is too old.
Both Lightning and Sunbird trunk builds are broken.
Summary: galactica sunbird builds broken; need new version of pango installed → galactica trunk builds broken; need new version of pango installed
they probably want --enable-default-toolkit=gtk2
or to be upgraded to a newer OS/newer pango.  This is really the better option long term.
what version of pango is needed? would be good to have a standard set of OS versions/patch levels for cairo.
For now, can we disable cairo on the sunbird tinderbox? sunbird0.3a2 is pretty near, and i don't want to ship it with a huge part of the code being somewhat experimental and less-tested.
I'll add --enable-default-toolkit=gtk2 to the builds and get the configs into CVS for now.
Assignee: build → ccooper
Status: NEW → ASSIGNED
(In reply to comment #6)
> I'll add --enable-default-toolkit=gtk2 to the builds and get the configs into
> CVS for now.
> 

Done.
Assignee: ccooper → build
Status: ASSIGNED → NEW
Thanks, coop!
No longer blocks: sunbird-0.3a2
Summary: galactica trunk builds broken; need new version of pango installed → galactica trunk builds need new pango, and cairo switch to be thrown, post 0.3a2
Dan - should this be closed?
schrep: no; what's been implemented so far is the workaround fix.  0.3a2 hasn't quite happened yet, so it's not quite ready for the real fix (install pango and throw the cairo switch).
Depends on: 334456
(In reply to comment #10)
> 0.3a2 hasn't quite happened yet, so it's not quite ready for the real fix
> (install pango and throw the cairo switch).

0.3a2 happened.
This can move forward.
Moving to the ref platform is probably the best way to solve this moving forward.
Summary: galactica trunk builds need new pango, and cairo switch to be thrown, post 0.3a2 → move sunbird/lightning to linux ref platform
(In reply to comment #12)
> Moving to the ref platform is probably the best way to solve this moving
> forward.

Robert,
can you please push this. All 0.3-related releases have happened, so there's nothing holding this up from the Calendar side of things anymore.

Blocks: 321244
Assignee: build → ccooper
Status: NEW → ASSIGNED
sb-linux-tbox is reporting now to the Sunbird page. It will be taking over from galactica, which means it *should* be producing builds for Lt-Trunk, Sb-Trunk, and Sb-Trunk-l10n.

I've updated the configs, but someone (lilmatt?) will want to double-check them.
A brief hiccup last night re: accepting ssh connection keys, but the builds seem to be humming along now.
Status: ASSIGNED → RESOLVED
Closed: 17 years ago
Resolution: --- → FIXED
The new tbox is building now but the builds don't get uploaded to latest-trunk or latest-mozilla1.8 folder. For example todays linux trunk build is available from folder sunbird/nightly/2007-03-24-03-trunk/ but not from sunbird/nightly/latest-trunk/.

From logfile:

rsync: failed to set times on "/home/ftp/pub/calendar/sunbird/nightly/latest-trunk/.": Operation not permitted (1)
rsync error: some files could not be transferred (code 23) at main.c(977) [sender=2.6.9]
It often takes a little while for the builds to propagate/become visible to the web (if that's where you were checking). I see Linux nightlies for both trunk and branch in the appropriate latest-* dirs now.
Product: mozilla.org → Release Engineering
You need to log in before you can comment on or make changes to this bug.