Closed Bug 688834 Opened 13 years ago Closed 13 years ago

Problems with Enigmail 1.3.2 for OSX versioning (addon page delivers wrong and uninstallable version)

Categories

(addons.mozilla.org Graveyard :: Administration, defect)

x86
macOS
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED INCOMPLETE

People

(Reporter: theleez, Unassigned)

Details

User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:6.0) Gecko/20100101 Firefox/6.0
Build ID: 20110811165603

Steps to reproduce:

I tried installing Enigmail 1.3.2 for OSX from https://addons.mozilla.org/en-US/thunderbird/addon/enigmail/


Actual results:

it installed version 1.2, even though the page and filename specifies 1.3.2.  1.2 is not compatible with Thunderbird 6.0.2, so it's unusable and uninstallable.

The version at http://enigmail.mozdev.org/download/download-static.php.html (https://addons.mozilla.org/en-US/thunderbird/downloads/file/131061/enigmail-1.3.2-tb+sm-windows.xpi) installs fine, only if the directory from the faulty 1.2 version has been manually deleted (otherwise Thunderbird produces as could not modify file error).


Expected results:

1. 1.3.2 should be available via the addons interface
2. https://addons.mozilla.org/en-US/thunderbird/addon/enigmail/ 1.3.2 should install 1.3.2, not 1.2
3. 1.2 should be uninstallable (though this would be rendered moot if #2 were true.)
Component: General → Administration
Product: Thunderbird → addons.mozilla.org
QA Contact: general → administration
Version: 6 → unspecified
Leez is this still the case ?
I'm not sure.  I installed the 'windows' version from http://enigmail.mozdev.org/download/download-static.php.html (https://addons.mozilla.org/en-US/thunderbird/downloads/file/131061/enigmail-1.3.2-tb+sm-windows.xpi) which installed fine, only after I manually deleted the directory from the faulty 1.2 version.  

So I decided not to mess with it :)
Status: UNCONFIRMED → RESOLVED
Closed: 13 years ago
Resolution: --- → INCOMPLETE
Product: addons.mozilla.org → addons.mozilla.org Graveyard
You need to log in before you can comment on or make changes to this bug.