Closed Bug 339502 Opened 19 years ago Closed 19 years ago

seamonkey linux gtk2 builds not updated recently

Categories

(Release Engineering :: General, defect)

x86
Linux
defect
Not set
blocker

Tracking

(Not tracked)

RESOLVED DUPLICATE of bug 309979

People

(Reporter: sonnenstrahl, Unassigned)

References

()

Details

User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9a1) Gecko/20060517 SeaMonkey/1.5a Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9a1) Gecko/20060517 SeaMonkey/1.5a The latest gtk2 build for Seamonkey is from May 19, although there are builds available for gtk1 from May 28. Reproducible: Always Steps to Reproduce: 1. Go to http://ftp.mozilla.org/pub/mozilla.org/seamonkey/nightly/latest-trunk/ 2. 3. Actual Results: The Latest gtk2 build is from May 19: [ ] seamonkey-1.5a.en-US.linux-i686.installer.tar.bz2 19-May-2006 18:07 13M [ ] seamonkey-1.5a.en-US.linux-i686.tar.bz2 19-May-2006 18:11 12M Expected Results: A newer gtk2 nightly build should be available, just like for gtk1: [ ] seamonkey-1.5a.en-US.linux-i686-gtk1.installer...> 28-May-2006 12:07 14M [ ] seamonkey-1.5a.en-US.linux-i686-gtk1.stub-insta..> 28-May-2006 12:07 109K [ ] seamonkey-1.5a.en-US.linux-i686-gtk1.tar.gz 28-May-2006 12:07 14M
lhasa dropped off the tbox.
Severity: normal → critical
Status: UNCONFIRMED → NEW
Ever confirmed: true
Version: unspecified → Trunk
So it's been 11 days without GTK2 builds now. Since GTK1 builds are completely broken anyway for our purposes due to cairo (eg. printing doesn't work), how about we just stop making them and focus and having useful _reliable_ GTK2 builds? Given that seamonkey builds are the only ones that come with the full range of layout-debugging facilities I need for daily work, having 11-day gaps in them makes regression narrowing _really_ painful. Andrew, do you have builds from the gap in question that you would be willing to upload to archive.mozilla.org or ftp.mozilla.org?
Assignee: general → server-ops
Severity: critical → blocker
Component: General → Server Operations
Product: Mozilla Application Suite → mozilla.org
QA Contact: general → justin
Version: Trunk → other
This looks like more of a build bug.
Component: Server Operations → Build & Release
Assignee: server-ops → build
QA Contact: justin → preed
I'd be happy to upload my builds. I'm transfering the builds from my slow-connection home desktop now. Let me know what to do to make them available.
I restarted lhasa earlier this evening.. it doesn't seem to have sent a status email out and is taking a very long time to build (seemed to have been building before but not sending out any status email). I'll check it again in the morning.
Status: NEW → ASSIGNED
*** This bug has been marked as a duplicate of 309979 ***
Status: ASSIGNED → RESOLVED
Closed: 19 years ago
Resolution: --- → DUPLICATE
Assignee: build → nobody
QA Contact: mozpreed → build
Product: mozilla.org → Release Engineering
You need to log in before you can comment on or make changes to this bug.