Closed Bug 1164390 Opened 10 years ago Closed 10 years ago

Signing of a version fails if one of its files is missing on the filesystem

Categories

(addons.mozilla.org Graveyard :: Admin/Editor Tools, defect)

defect
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED
2015-05

People

(Reporter: magopian, Assigned: magopian)

References

Details

(Whiteboard: [qa-])

STR: 1/ upload an add-on which has at least two files for one of its version 2/ make sure one of the files doesn't exist on the filesystem 3/ review the add-on and approve it The file that is present on the filesystem should be signed, but it is not. Example failure: http://sentry.dmz.phx1.mozilla.com/addons/addons-dev/group/27651/ https://addons-dev.allizom.org/en-US/developers/addon/gigi/versions/1526634 (the file for linux isn't there, and the other one isn't signed). :kmag could you please explain how to achieve 2/? You said something about rejecting a version and re-uploading another file with the same version, but I couldn't manage to do that on my end.
Flags: needinfo?(kmaglione+bmo)
Assignee: nobody → mathieu
Blocks: 1122114
In the case we came across on dev, it was the following: 1) Upload a new version of an add-on. 2) Reject or otherwise disable that version. 3) Upload a new version with the same version number. 4) Approve the new version. At this point, the file with the same generated name as in the previous version is not available. See bug 1130585 for reference.
Flags: needinfo?(kmaglione+bmo)
See Also: → 1130585
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → FIXED
Whiteboard: [qa-]
Product: addons.mozilla.org → addons.mozilla.org Graveyard
You need to log in before you can comment on or make changes to this bug.