Closed Bug 514469 Opened 15 years ago Closed 12 years ago

update-packaging problems with unofficial branding

Categories

(Firefox Build System :: General, defect)

x86
macOS
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED INCOMPLETE

People

(Reporter: bhearsum, Unassigned)

Details

Problem in branding-land for complete mar. $ make -C obj-firefox/ppc/tools/update-packaging mkdir -p ../../dist/update/mac/en-US/ MAR=../../dist/host/bin/mar \ /builds/slave/macosx_build/build/tools/update-packaging/make_full_update.sh \ "../../dist/update/mac/en-US//namoroka-3.6a1.complete.mar" \ "../../dist/universal/Namoroka/Namoroka.app" /builds/slave/macosx_build/build/tools/update-packaging/make_full_update.sh: line 42: pushd: ../../dist/universal/Namoroka/Namoroka.app: No such file or directory The last argument should be "../../dist/universal/firefox/Namoroka.app" instead. Something wrong in tools/update-packaging/Makefile.in. This probably doesn't affect --enable-official-branding, but we should fix it soon nonetheless.
Moving to build config
Component: Release Engineering → Build Config
Product: mozilla.org → Firefox
QA Contact: release → build.config
Version: other → unspecified
I don't think tools/update-packaging is really part of Build Config, I think this is actually your bug. :)
the build/tools in that path is actually where the mozilla-central checkout lives (hg clone http://hg.mozilla.org/mozilla-central build) not our repository (hg.m.o/build/tools). This script is invoked by the makefile and it looks like the script is getting the right arguments. The place that this is bailing is setting the $targetdir in the script, which is just the script's second argument. Is the makefile setting $(PACKAGEDIR) correctly? http://mxr.mozilla.org/mozilla-central/source/tools/update-packaging/Makefile.in#61
Clearly this hasn't been important for awhile.
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → INCOMPLETE
Component: Build Config → General
Product: Firefox → Firefox Build System
You need to log in before you can comment on or make changes to this bug.