Closed Bug 481412 Opened 15 years ago Closed 15 years ago

mobile-linux-arm-nightly builds from modified source?

Categories

(Release Engineering :: General, defect)

ARM
Linux
defect
Not set
normal

Tracking

(Not tracked)

VERIFIED DUPLICATE of bug 480680

People

(Reporter: Pike, Assigned: mozilla)

References

()

Details

I wonder how the fennec linux arm builds end up with a + in their platform.ini source stamp. That's indicating that hg considers the mozilla-central repo modified, which is not what I expect from the build.

[Build]
BuildID=20090304020502
Milestone=1.9.2a1pre
SourceStamp=6c0ff682551d+
SourceRepository=http://hg.mozilla.org/mozilla-central

is what's currently in platform.ini.

The latest slave is moz2-linux-slave10.

Can you check what's actually triggering this?
Assignee: nobody → aki
[cltbld@moz2-linux-slave10 mozilla-central]$ hg diff
diff -r 6c0ff682551d nsprpub/configure
--- a/nsprpub/configure Wed Mar 04 09:50:22 2009 +0000
+++ b/nsprpub/configure Wed Mar 04 09:21:02 2009 -0800
@@ -6071,7 +6071,7 @@
 s%\]%\\&%g
 s%\$%$$%g
 EOF
-DEFS=`sed -f conftest.defs confdefs.h | tr '\012' ' ' | tr '\015' ' '`
+DEFS=`sed -f conftest.defs confdefs.h | tr '\012' ' '`
 rm -f conftest.defs
aiui, having a modified nsprpub/configure is not out of the ordinary.

Is this blocking fennec l10n, or were you just curious?
I'm not sure that that it's good to have a changed configure. I know that we don't have the main configure in the repo for a good reason, I'm not sure why the nsprpub one is and get's recreated anyway.

Benjamin, Ted? What's your take on this?

This is a problem for l10n builds, as I can't update my local repos to that a modified source stamp. I can hack around that by stripping the '+', but in a 'defense in depth' sense, modified local repos should probably not go undetected.

In addition, it's not only l10n builds having trouble with this, about:buildconfig is probably having a broken link to what it's built from, and other systems that depend on this information would suffer just as bad. Like, the Tinderbox pages should probably not only talk about the revision of the mobile repo, but also to the repo/revision where they got gecko from.
The nsprpub one gets recreated because we import it from CVS, where it's checked in. Maybe we should just delete it from the hg repos?
Whiteboard: DUPEME
See bug 480680, which has a patch.
Status: NEW → RESOLVED
Closed: 15 years ago
Resolution: --- → DUPLICATE
V.Duplicate
Status: RESOLVED → VERIFIED
Whiteboard: DUPEME
Product: mozilla.org → Release Engineering
You need to log in before you can comment on or make changes to this bug.