wrong release id in README

RESOLVED FIXED

Status

SeaMonkey
Release Engineering
RESOLVED FIXED
5 years ago
5 years ago

People

(Reporter: Dr. Ingo Bremer, Assigned: ewong)

Tracking

SeaMonkey 2.0 Branch
x86_64
Linux

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

5 years ago
User Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.1.6) Gecko/20091210 SUSE/2.0.1-3.1 SeaMonkey/2.0.1
Build ID: 2009121000

Steps to reproduce:

as discribed in http://releases.mozilla.org/pub/mozilla.org/seamonkey/releases/2.11/README

hg clone -r SEAMONKEY_2.11_1_RELEASE http://hg.mozilla.org/releases/comm-release



Actual results:

no such release, or something like this.




Expected results:

the correct id seams to be SEAMONKEY_2_11_RELEASE
(Reporter)

Comment 1

5 years ago
python client.py checkout --rev=SEAMONKEY_2.11_1_RELEASE
Executing command: ['hg', 'pull', '-R', './.']
pulling from http://hg.mozilla.org/releases/comm-release
searching for changes
no changes found
Executing command: ['hg', 'update', '-r', 'SEAMONKEY_2.11_1_RELEASE', '-R', './.']
abort: unknown revision 'SEAMONKEY_2.11_1_RELEASE'!


Python client.py checkout --rev=SEAMONKEY_2_11_RELEASE
...
Executing command: ['hg', 'update', '-r', 'SEAMONKEY_2_11_RELEASE', '-R', './ldap/sdks']
abort: unknown revision 'SEAMONKEY_2_11_RELEASE'!
Traceback (most recent call last):
  File "client.py", line 657, in <module>
    do_hg_pull(os.path.join('ldap', 'sdks'), options.ldap_repo, options.hg, options.ldap_rev)
  File "client.py", line 343, in do_hg_pull
    check_call_noisy(cmd, retryMax=0)
  File "client.py", line 138, in check_call_noisy
    execute_check_call(cmd, *args, **kwargs)
  File "client.py", line 134, in execute_check_call
    check_call(cmd, *args, **kwargs)
  File "/usr/local/lib/python2.5/subprocess.py", line 461, in check_call
    raise CalledProcessError(retcode, cmd)
subprocess.CalledProcessError: Command '['hg', 'update', '-r', 'SEAMONKEY_2_11_RELEASE', '-R', './ldap/sdks']' returned non-zero exit status 255

Updated

5 years ago
Component: Download & File Handling → Release Engineering

Updated

5 years ago
Status: UNCONFIRMED → NEW
Ever confirmed: true
(Assignee)

Comment 2

5 years ago
I've fixed the README. but the releases.m.o link is broken.
Assignee: nobody → ewong
(Assignee)

Updated

5 years ago
Status: NEW → ASSIGNED
(Assignee)

Comment 3

5 years ago
Do we need to change our releases.mozilla.org references to use ftp.mozilla.org
in the README?
Flags: needinfo?(bugspam.Callek)
(In reply to Edmund Wong (:ewong) from comment #3)
> Do we need to change our releases.mozilla.org references to use ftp.mozilla.org
> in the README?

Either that, I suppose, and also everywhere else we link to releases.mozilla.org (and resolve bug 850339 as WONTFIX), or else FIX bug 850339 by mirroring SeaMonkey releases on releases.mozilla.org again.
See Also: → bug 850339
(Assignee)

Comment 5

5 years ago
Releases.mozilla.org no longer tracks the SeaMonkey project.  

As the bug is fixed, I'm calling this fixed.
Status: ASSIGNED → RESOLVED
Last Resolved: 5 years ago
Flags: needinfo?(bugspam.Callek)
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.