799718 - The webapprt/components folder is getting left behind on uninstall of firefox installed through the stub installer

Status: RESOLVED DUPLICATE of bug 798486

(Firefox :: Installer, defect)

Description

[Jason Smith [:jsmith]]

Steps:

1. Install firefox with the stub installer using the latest-mozilla-aurora stub installer
2. Uninstall Aurora
3. Check C:\Program Files\Aurora

Expected:

Nothing should be there.

Actual:

An empty webapprt/components folder is left behind on uninstall.

Comment 1

[Jason Smith [:jsmith]]

What's really strange about this bug is that only happens with the stub installer, not the regular installer, which I find bizarre. Any ideas?

Comment 2

[Robert Strong (they/them - no direct email)]

Really shouldn't be happening any differently with the stub. I'll take a look in a bit

Comment 3

[Jason Smith [:jsmith]]

Specific link to the build I used to test:

http://ftp.mozilla.org/pub/mozilla.org/firefox/nightly/latest-mozilla-aurora/firefox-18.0a2.en-US.win32.installer-stub.exe

Comment 4

[Jason Smith [:jsmith]]

Apparently also reproduces on Windows Vista. So this isn't an OS-specific bug.

Comment 5

[Brian R. Bondy [:bbondy]]

(In reply to Jason Smith [:jsmith] from comment #1)
> What's really strange about this bug is that only happens with the stub
> installer, not the regular installer, which I find bizarre. Any ideas?

Can you do a diff of the installation directory w/ and w/o stub? I suspect different versions are getting installed?

Comment 6

[Tim Abraldes [:TimAbraldes] [:tabraldes]]

This might be tied to bug 757978, which was fixed about a month ago

Comment 7

[Brian R. Bondy [:bbondy]]

Ya I suspect the stub is getting an old version

Comment 8

[Brian R. Bondy [:bbondy]]

Instead of a diff maybe just do about:buildconfig after each installation, but make sure you can reproduce it after you check the details of buildconfig.

Comment 9

[Jason Smith [:jsmith]]

Attachment: Build Config for build downloaded by stub

Comment 10

[Brian R. Bondy [:bbondy]]

Hrm that says aurora v16, shouldn't aurora be v17? and very very soon to be v18?

Comment 11

[Jason Smith [:jsmith]]

(In reply to Brian R. Bondy [:bbondy] from comment #10)
> Hrm that says aurora v16, shouldn't aurora be v17? and very very soon to be
> v18?

Sounds like this is exactly as you've described - we are getting an old build. bug 757978 was fixed on the FF 17 branch, but not FF 16.

Comment 12

[Jason Smith [:jsmith]]

Attachment: Build Config for build downloaded without stub

Comment 13

[Jason Smith [:jsmith]]

The changesets that each build is built from appears to be different:

- http://hg.mozilla.org/releases/mozilla-aurora/rev/8aac40fc9890
- http://hg.mozilla.org/releases/mozilla-aurora/rev/7588306df29e

Comment 14

[Jason Smith [:jsmith]]

(In reply to Jason Smith [:jsmith] from comment #13)
> The changesets that each build is built from appears to be different:
> 
> - http://hg.mozilla.org/releases/mozilla-aurora/rev/8aac40fc9890
> - http://hg.mozilla.org/releases/mozilla-aurora/rev/7588306df29e

This confirms we are getting a different build here with the regular installer for aurora vs. the stub installer. The stub installer appears to be grabbing an older changeset on 10/2, where as the regular installer is using a changeset from 10/8.

Comment 15

[Brian R. Bondy [:bbondy]]

I think we're seeing bug 798486.  Maybe the difference is only a day and one version is the migrated version and the other is not.

Comment 16

[Jason Smith [:jsmith]]

(In reply to Brian R. Bondy [:bbondy] from comment #15)
> I think we're seeing bug 798486.  Maybe the difference is only a day and one
> version is the migrated version and the other is not.

Yeah, I agree. Duping on that.