It is not possible to override the values of MOZ_SOURCE_CHANGESET and MOZ_SOURCE-REPO in Seamonkey builds

RESOLVED FIXED in seamonkey2.52

Status

SeaMonkey
General
RESOLVED FIXED
4 months ago
3 months ago

People

(Reporter: WG9s, Assigned: WG9s)

Tracking

({regression})

Trunk
seamonkey2.52
regression

Firefox Tracking Flags

(Not tracked)

Details

Attachments

(1 attachment, 3 obsolete attachments)

(Assignee)

Description

4 months ago
For a Frefox build it si possible to override the values for MOZ_SOURCE_CHANGESET and MOZ_SOURCE_REPO for a custom build by defining these vaues in system environment variables.  In fact the Seamonkey build makes use of this feature to ensure that about:buildconfig reflects the Seamonkey repository and changeset rather than the gecko ones.  Unfortunately, it does this in an unconditional manner.  It should only be defining these environment variables if they are not already defined, to permit the builder to override these values.
(Assignee)

Updated

4 months ago
Blocks: 1267270
Keywords: regression
(Assignee)

Comment 1

4 months ago
Created attachment 8863752 [details] [diff] [review]
Allow overrride of MOZ_SOURCE_CHANGESET and MOZ_SOURCE_REPO.
Attachment #8863752 - Flags: review?(aleth)
(Assignee)

Comment 2

4 months ago
Created attachment 8863763 [details] [diff] [review]
Allow overrride of MOZ_SOURCE_CHANGESET and MOZ_SOURCE_REPO.

Ooops had wrong reviewer and not really a checkin ready comment.
Attachment #8863763 - Flags: review?(mh+mozilla)
(Assignee)

Updated

4 months ago
Attachment #8863752 - Attachment is obsolete: true
Attachment #8863752 - Flags: review?(aleth)
(Assignee)

Comment 3

4 months ago
To make it clear why I do that, with this fix I can make about:buildconfig show the comm-central changeset my build was based from and also have a link to my build page which documents the additional patches I includue in my builds.
(Assignee)

Comment 4

4 months ago
I accomplish this by including the following in my build script:

export MOZ_INCLUDE_SOURCE_INFO=1
export MOZ_SOURCE_CHANGESET=`cat .changeset`
export MOZ_SOURCE_REPO=https://hg.mozilla.org/comm-central

the .changset file contains the changset from before my patches were applied.
(Assignee)

Comment 5

4 months ago
I suppose maybe is should have also updated the comment but looking for a rview first.

I was thinking perhaps changing the comment to:

# Ensure the comm-* values are used unless overridden via environment variables.].
(Assignee)

Comment 6

4 months ago
I suppose maybe is should have also updated the comment but looking for a rview first.

I was thinking perhaps changing the comment to:
# Ensure the comm-* values are used unless overridden via environment variables.(In reply to Bill Gianopoulos [:WG9s] from comment #5)
> I suppose maybe is should have also updated the comment but looking for a
> rview first.
> 
> I was thinking perhaps changing the comment to:
> 
> # Ensure the comm-* values are used unless overridden via environment
> variables.].
(Assignee)

Comment 7

4 months ago
Created attachment 8863917 [details] [diff] [review]
Allow overrride of MOZ_SOURCE_CHANGESET and MOZ_SOURCE_REPO.
Attachment #8863763 - Attachment is obsolete: true
Attachment #8863763 - Flags: review?(mh+mozilla)
Attachment #8863917 - Flags: review?(mh+mozilla)
(Assignee)

Comment 8

4 months ago
I decided to fix the comments before review.
(Assignee)

Comment 9

3 months ago
Created attachment 8864811 [details] [diff] [review]
Allow overrride of MOZ_SOURCE_CHANGESET and MOZ_SOURCE_REPO.

Same patch just a typo in the comment corrected.
Attachment #8863917 - Attachment is obsolete: true
Attachment #8863917 - Flags: review?(mh+mozilla)
Attachment #8864811 - Flags: review?(mh+mozilla)
Comment on attachment 8864811 [details] [diff] [review]
Allow overrride of MOZ_SOURCE_CHANGESET and MOZ_SOURCE_REPO.

Review of attachment 8864811 [details] [diff] [review]:
-----------------------------------------------------------------

Beware that as of bug 1279048, those variables are used for debug symbol files.
Attachment #8864811 - Flags: review?(mh+mozilla) → review+
(Assignee)

Updated

3 months ago
Assignee: nobody → wgianopoulos
Status: NEW → ASSIGNED
Keywords: checkin-needed
(Assignee)

Comment 11

3 months ago
OK so I don;t know, does adding checkin-needed as a keyword here help to get it checked in, or do I need to find my own friend with check-in privs to do this for me?
Jorg, the patch got r+ from Mike. Should I just check it in or do you want to do it?
Flags: needinfo?(jorgk)

Comment 13

3 months ago
I'll check it in when I next need a patch, so within the next 24 hours. I'll leave the NI to remind me.
(Assignee)

Comment 14

3 months ago
(In reply to Jorg K (GMT+2) from comment #13)
> I'll check it in when I next need a patch, so within the next 24 hours. I'll
> leave the NI to remind me.

Thanks!

Comment 15

3 months ago
https://hg.mozilla.org/comm-central/rev/bd34d80df5ff4929617aaede1ec44230f54d65f7

I quite aggressively manage C-C these days, that means, I do an C-C push after every M-C merge to detect bustage. Small patches like this one help me with that. However, at times a small patch has to wait until I need to do a push again and don't have more important patches.
Status: ASSIGNED → RESOLVED
Last Resolved: 3 months ago
Flags: needinfo?(jorgk)
Keywords: checkin-needed
Resolution: --- → FIXED
Target Milestone: --- → seamonkey2.52
You need to log in before you can comment on or make changes to this bug.