macosx64 repack bustage: __CF_USER_TEXT_ENCODING=0x1F5:0:0 using PTY: False /builds/slave/rel-c-rel-osx64-rpk/build/comm-release/obj-l10n/_virtualenv/bin/python /builds/slave/rel-c-rel-osx64-rpk/build/comm-release/mozilla/config/nsinstall.py -D /builds/slave/rel-c-rel-osx64-rpk/build/comm-release/obj-l10n/dist/mac/en-US/ (cd /builds/slave/rel-c-rel-osx64-rpk/build/comm-release/obj-l10n/dist/mac/en-US/ && wget --no-cache -nv --no-iri -N 'http://ftp.mozilla.org/pub/mozilla.org/seamonkey/candidates/2.46-candidates/build3/mac/en-US/SeaMonkey 2.46.dmg') wget: unrecognized option `--no-iri' Usage: wget [OPTION]... [URL]... Try `wget --help' for more options. make: *** [wget-en-US] Error 2 program finished with exit code 2 elapsedTime=0.213040
The no-iri option was added in bug 1276110. I think it was maybe added somewhere between wget 1.11 and 1.12. Seems to be mostly used in calendar packaging. The esr-45 makefile for lightning does not contain it so if you do not do a taskcluster build you can just leave this option out for now: https://dxr.mozilla.org/comm-esr45/source/calendar/lightning/lightning-packager.mk
OS: Unspecified → Mac OS X
Hardware: Unspecified → x86_64
I suppose upgrading the macs to a newer wget might work? Callek, are we permitted to get the wget dmg package that Moco uses for their minis? Or is there another way around this? (And the thing that comes to my mind right now is backing out the patch from bug 1276110, but I don't know how much damage that'd do).
I conferred with IanN on irc and backing out that cset would be the easiest; however, to fix this permanently, we need wget 1.15+ on all our slaves. I believe the linux* and windows loaner's ok; but it's our macs that need updating. So the needinfo to Callek basically means "Can we upgrade wget on our macs?"
Backed out on SEA_COMM490_20160927_RELBRANCH: http://hg.mozilla.org/releases/mozilla-release/rev/b76bb66cef3e
Fixed. Installed 1.15-2 on the OSX64 slaves.
Status: NEW → RESOLVED
Last Resolved: 2 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.