Closed Bug 147429 Opened 22 years ago Closed 22 years ago

Installing RC3 onto old RC2 folder gives Error -2

Categories

(SeaMonkey :: Installer, defect)

Product:
SeaMonkey
Component:
Installer
Platform:
PowerPC
Mac System 9.x
Type:
defect
Priority:
Not set
Severity:
minor

Tracking

(Not tracked)

Status:
VERIFIED DUPLICATE of bug 34877

People

(Reporter: a.c.li, Assigned: dveditz)

References

Details

From Bugzilla Helper:
User-Agent: Mozilla/5.0 (Macintosh; U; PPC; en-US; rv:1.0rc3) Gecko/20020523
BuildID:    2002052305

Choosing the folder where RC2 was installed as the Install Location for RC3
gives Error -2 some time in the installation. The installation did not complete.
(Tried it a few times, with same results.) Choosing a different Install Location
solves the problem.

Reproducible: Didn't try
Steps to Reproduce:
1.Install RC3 over RC2 in the same folder
2.
3.

Actual Results:  Error -2 occurs. The installation was aborted prematurely.

Expected Results:  Installation should be successful. Installing RC2 over RC1
gave no problems.

The RC2 was installed over RC1.

I selected "Haven't tried to reproduced it" because I did not try to reinstall
RC2 and then reinstall RC3. However I did try to install RC3 over RC2 a number
of times.
QA Contact: bugzilla → ktrina
Grace or K'trina, could you check this one out? Thanks.
*** Bug 146994 has been marked as a duplicate of this bug. ***
acli, Mozilla's Release Notes state that users should "Install into a new empty directory. Installing 
on top of previously installed builds may cause problems."

Thus you should never install a new Mozilla build into an old one's folder.
so invalid or what ?
this is reproduceable.
legacy check in both config files is set to 1.0.0 so it is not picking up older
version and prompting user
Status: UNCONFIRMED → NEW
Ever confirmed: true
cant this one be forgotten ?
mail from Bart Prieve <bprieve@hotmail.com>

Well, one can always document a bug as a "feature" and wash one's hands of
it, but a quality product would not work this way.
-----------

the point is, nobody is gonna use old rc2 or 3 build anymore .. if it works in 
newer builds, who cares
Can someone with access to a Mac verify this then? I am now just an ordinary
user on the Mac, so I can't install a new Mozilla to test this any more.
bug 34877 - 'handle old components when doing upgrade' will handle this problem
- reason for release notes asking users to install into new folders.
marking as duplicate

*** This bug has been marked as a duplicate of 34877 ***
Status: NEW → RESOLVED
Closed: 22 years ago
Resolution: --- → DUPLICATE
Verified as a dupe of bug 34877
Status: RESOLVED → VERIFIED
Product: Browser → Seamonkey
You need to log in before you can comment on or make changes to this bug.