Closed Bug 1290043 Opened 10 years ago Closed 10 years ago

45.3.0esr directory exists on archive.mozilla.org but does not contain a valid build

Categories

(Release Engineering :: Release Automation, defect)

defect
Not set
normal

Tracking

(Not tracked)

RESOLVED INCOMPLETE

People

(Reporter: davehunt, Unassigned)

Details

The mozdownload tool has an option to download the latest Firefox ESR version, however this is currently trying to download from https://archive.mozilla.org/pub/firefox/releases/45.3.0esr/ which does not contain a build: > $ mozdownload --version=latest-esr > Traceback (most recent call last): > File "/Users/dhunt/.virtualenvs/tmp-11d20260ca293f56/bin/mozdownload", line 11, in <module> > sys.exit(cli()) > File "/Users/dhunt/.virtualenvs/tmp-11d20260ca293f56/lib/python2.7/site-packages/mozdownload/cli.py", line 166, in cli > build.download() > File "/Users/dhunt/.virtualenvs/tmp-11d20260ca293f56/lib/python2.7/site-packages/mozdownload/scraper.py", line 257, in download > if os.path.isfile(os.path.abspath(self.filename)): > File "/Users/dhunt/.virtualenvs/tmp-11d20260ca293f56/lib/python2.7/site-packages/mozdownload/scraper.py", line 222, in filename > self.build_filename(self.binary)) > File "/Users/dhunt/.virtualenvs/tmp-11d20260ca293f56/lib/python2.7/site-packages/mozdownload/scraper.py", line 182, in binary > self._retry_check_404(_get_binary) > File "/Users/dhunt/.virtualenvs/tmp-11d20260ca293f56/lib/python2.7/site-packages/mozdownload/scraper.py", line 151, in _retry_check_404 > raise errors.NotFoundError(err_message, exc.response.url) > mozdownload.errors.NotFoundError: Specified build has not been found: https://archive.mozilla.org/pub/firefox/releases/45.3.0esr/mac/en-US/ Should this directly exist if there are no builds?
Something seems to have created this version folder under releases already even that we haven't done a release yet.
Component: Other → Release Automation
Flags: needinfo?(rail)
Flags: needinfo?(bugspam.Callek)
QA Contact: mshal → rail
Looks like Solaris folks uploaded their packages already. Usually they upload after we release. Nick, do you know if we have some kind of agreement with them about the timing of their releases?
Flags: needinfo?(rail) → needinfo?(nthomas)
As long as we haven't build our final builds how can partners build their releases?
Rail, it looks like someone jumped the gun. Lets ni the address we've used before to check. In the meantime I'm going to remove firefox/releases/45.3.0esr/contrib/. Presumably our 'push to releases/' will copy it back over when we're ready.
Flags: needinfo?(nthomas) → needinfo?(ginn.chen)
Thank you!
Flags: needinfo?(bugspam.Callek)
No reply. Let's resolve this for and reopen if this happens again.
Status: NEW → RESOLVED
Closed: 10 years ago
Flags: needinfo?(ginn.chen)
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.