Incorrect hash calculated for public add-on version

RESOLVED INVALID

Status

addons.mozilla.org Graveyard
Public Pages
RESOLVED INVALID
5 years ago
2 years ago

People

(Reporter: jorgev, Unassigned)

Tracking

Details

(URL)

Attachments

(1 attachment)

(Reporter)

Description

5 years ago
Version 1.1 of the Tamper Data Icon Redux add-on recently had its file hash corrupted, and recalculating it doesn't fix the problem.

AMO is calculating the hash as:
1f27455a9bea00561768878e07abab3e623b631717f3cee8a385448357cd92b6

While, locally, I get:
a6fb33f9554941064b3bbe5a5e7c18b519effa34c17084a999890b4bf6fca8e2

This makes installation fail every time.
Created attachment 664955 [details]
xpi downloaded 2012-09-26

When try this I get an error with the install.rdf instead, rather than a hash error.  Maybe one of the mirrors is holding a broken copy of the xpi?
I get the same file from both https://addons.mozilla.org/firefox/downloads/latest/335331/addon-335331-latest.xpi and http://ftp.mozilla.org/pub/mozilla.org/addons/335331/tamper_data_icon_redux-1.1-fx.xpi which is the functionality we are expecting (I get the same hash as what AMO is calculating).

Would you download the file at the second link (from ftp.m.o) and tell me what hash you get?  If you're get a good hash from that, then yeah, a mirror has an invalid file on it.
(Reporter)

Comment 3

5 years ago
Yes, it looks like I was wrong about the hashes (I think I downloaded another version when I tested).

I'm getting this error when installing the add-on locally:

Timestamp: 9/26/12 11:57:44 AM
Error: XML declaration not well-formed
Source File: jar:file:///Users/jorge/Desktop/tamper_data_icon_redux-1.1-fx.xpi!/install.rdf
Line: 1, Column: 16
Source Code:
<?xml version="1.1"?>

Which seems to be a problem with the install.rdf file and not Firefox. I'll bring this up with the developer.
Status: NEW → RESOLVED
Last Resolved: 5 years ago
Resolution: --- → INVALID
(Assignee)

Updated

2 years ago
Product: addons.mozilla.org → addons.mozilla.org Graveyard
You need to log in before you can comment on or make changes to this bug.