client.mk didn't get it's pull tags updated for the 1.2a tagging

VERIFIED FIXED in mozilla1.2alpha

Status

SeaMonkey
Build Config
P1
blocker
VERIFIED FIXED
16 years ago
7 years ago

People

(Reporter: jesup, Assigned: John "AntiTuX" Dee)

Tracking

Trunk
mozilla1.2alpha

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

16 years ago
This is the 1.2a-tagged client.mk:

MOZ_CO_TAG = MOZILLA_1_2a_RELEASE
NSPR_CO_TAG = NSPRPUB_PRE_4_2_CLIENT_BRANCH
PSM_CO_TAG = #We will now build PSM from the tip instead of a branch.
NSS_CO_TAG = NSS_CLIENT_TAG
LDAPCSDK_CO_TAG = ldapcsdk_50_client_branch
ACCESSIBLE_CO_TAG = 
GFX2_CO_TAG = 
IMGLIB2_CO_TAG = 

Note that none of the other CO_TAG's are updated, so if you pull a 1.2a
client.mk and build you get current trunk source for gfx2, imglib2, nspr, etc.

All 1.2a builds are therefore suspect and may have picked up spurious changes.
(Reporter)

Updated

16 years ago
Blocks: 165012

Comment 1

16 years ago
this should have been done by antitux when he did the release tag.  Builds done
by the Netscape team (win32, linux, os9, osx) will be fine but contributed
builds will need to be rebuilt.

reassigning.
Assignee: leaf → antitux

Updated

16 years ago
Priority: -- → P1
Target Milestone: --- → mozilla1.2alpha
(Assignee)

Comment 2

16 years ago
I apologize for this mess-up. I take full responsibility for this. This was my
mistake, and client.mk has been fixed.
Status: NEW → ASSIGNED
(Assignee)

Comment 3

16 years ago
fixed.
Status: ASSIGNED → RESOLVED
Last Resolved: 16 years ago
Resolution: --- → FIXED

Comment 4

16 years ago
verified.
Status: RESOLVED → VERIFIED
Product: Browser → Seamonkey
You need to log in before you can comment on or make changes to this bug.