Closed Bug 353399 Opened 19 years ago Closed 18 years ago

Errors in README for Seamonkey installer

Categories

(SeaMonkey :: Installer, defect)

x86
Linux
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED WONTFIX

People

(Reporter: tonymec, Unassigned)

References

()

Details

User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9a1) Gecko/20060919 SeaMonkey/1.5a Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9a1) Gecko/20060919 SeaMonkey/1.5a Several paths in the seamonkey-installer/README do not correspond to reality Reproducible: Always Steps to Reproduce: 1. Open seamonkey-installer/README using less or any text editor Actual Results: See below Expected Results: See below Additional information: ----------------------- *** At line 26, there is http://ftp.mozilla.org/pub/mozilla.org/seamonkey/nightly/latest/ *** there should be http://ftp.mozilla.org/pub/mozilla.org/seamonkey/nightly/latest-trunk/ *** At line 125, there is: directory_name/icons/mozicon50.xpm *** there should be: directory_name/chrome/icons/default/default.xpm *** At line 127, there is: where directory name is the directory where you installed SeaMonkey. For example, the default directory is /usr/local/seamonkey/icons/mozicon50.xpm. *** there should be: where directory name is the directory where you installed SeaMonkey. For example, the default directory is /usr/local/seamonkey/chrome/icons/default/default.xpm.
Version: unspecified → Trunk
To my surprise, I see that mozilla/suite/locales/en-US/installer/unix/README has the correct text in the CVS source tree, while seamonkey-installer/README in today's (well, yesterday's, my time zone, UTC+2) seamonkey-1.5a.en-US.linux-i686.installer.tar.bz2 is wrong as described above.
Also see Bug 299812 Comment 10 on this, the new files are there, but they are not used. Too bad.
Resolving WONTFIX, since there is no installer on trunk builds anymore.
Status: UNCONFIRMED → RESOLVED
Closed: 18 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.