Closed
Bug 474234
Opened 16 years ago
Closed 15 years ago
XPI diff tool does not work on multi item XPI
Categories
(addons.mozilla.org Graveyard :: Admin/Editor Tools, defect, P3)
Tracking
(Not tracked)
VERIFIED
FIXED
5.0.8
People
(Reporter: kinger, Assigned: u278084)
Details
Attachments
(2 files, 1 obsolete file)
119.88 KB,
image/png
|
Details | |
10.16 KB,
patch
|
wenzel
:
review+
|
Details | Diff | Splinter Review |
Multi item packages are explained here:
https://developer.mozilla.org/en/Multiple_Item_Packaging
In the case of an XPI containing other xpi files, the editor diff tool can not read them.
The solution of just to treat xpi files like any other compressed file (e.g. jar file).
Here is a review that has one, have a look quick before it is reviewed and expires!
https://addons.mozilla.org/en-US/editors/review/59339
Yep. This is also a problem with view contents. We also only handle jar files 1 level deep (eg. chrome/foo.jar will be extracted, but not any jar files within foo.jar), so the solution might be slightly more difficult.
Comment 2•16 years ago
|
||
Maybe this will help with testing: I have a multi-item .xpi for my extension at https://addons.mozilla.org/en-US/firefox/addon/11150. The (public) "view the source" link on the above page displays the nested .xpi files in some binary encoding, instead of recursing into the .xpi as one would hope.
Comment 3•16 years ago
|
||
Setting to P3 (nice to have) for 5.0.7 so we don't lose it. will be P2 in 5.0.8 if we don't get to it.
Priority: -- → P3
Target Milestone: --- → 5.0.7
I'll try to get it in for 5.0.7
Assignee: nobody → cdolivei.bugzilla
Still needs some work, but great progress is being made. Started doing view contents code first because it's easier and will be pretty useful.
Comment 7•16 years ago
|
||
Any chance this can land in 5.0.7?
Comment 8•16 years ago
|
||
Bug 496387 - in rey's example I saw the same behavior but I didn't see any nested archives. Can you investigate to see if it's the same underlying cause?
This could be the final patch. It's too late for 5.0.7 unfortunately.
Attachment #383556 -
Attachment is obsolete: true
Comment 10•16 years ago
|
||
No problem, we'll grab it in 5.0.8. Thanks Cesar.
Target Milestone: 5.0.7 → 5.0.8
Comment 11•16 years ago
|
||
If this fixes the issue of the diff tool not loading files, I'd like to ask that we push it today since it will be a big help for the weekend burndown. Can we get this pushed today?
Comment 12•16 years ago
|
||
Pushing a patch to production mid-cycle should only be for emergencies. Since this is so low impact (number of multi item XPIs) and has a viable alternative (download, use command line diff) let's leave it at 5.0.8.
Comment 13•16 years ago
|
||
Normally I would agree but 5.0.8 is a month away & if this patch also fixes this issue (https://bugzilla.mozilla.org/show_bug.cgi?id=496387) then I think it's worthwhile pushing now since that is a blocker for the editorial process.
Can you confirm whether if it fixes the issue outlined in the bug I just mentioned?
Comment 14•16 years ago
|
||
I'll start looking at command line diff tools for the editors in the interim but if this patch allows the editors to review the add-on without adding an extra step to their workflow, it would be great to get that out to them as they're helping us out by volunteering their time. I'm really hesitant about asking them to take a step backwards in the editorial process when we might have a fix available.
Assignee | ||
Comment 15•16 years ago
|
||
I agree with Wil on this. I don't think this is the cause of bug 496387. The add-ons that are effected by that bug aren't multi-item extensions. And I did't do anything special that would explain fixing it. So I will be surprised if it does fix it.
This patch is also pretty big, and touches a bit of everything. I think this should be postponed until after the burndown simply because it might introduce new bugs (ha!).
Comment 16•16 years ago
|
||
Ok. If it can't be confirmed that the fix would resolve the issue, that makes sense.
Assignee | ||
Comment 17•16 years ago
|
||
Comment on attachment 385298 [details] [diff] [review]
v2
Let's see if we can get this in before the freeze this time.
Attachment #385298 -
Flags: review?(fwenzel)
Comment 18•16 years ago
|
||
Comment on attachment 385298 [details] [diff] [review]
v2
Code looks good, but I wasn't able to check it out for lack of example files ;) If you are confident it works, check it in.
The screenshot looks good too, btw.
Attachment #385298 -
Flags: review?(fwenzel) → review+
Comment 19•16 years ago
|
||
Let me know when it's on preview and I'll test it out.
Comment 20•15 years ago
|
||
Can we get this committed and tested? thanks
Assignee | ||
Comment 21•15 years ago
|
||
In r48028. Thanks Wenzel.
I also set up a multi-item test extension on preview with the source publicly viewable. You can find it on https://preview.addons.mozilla.org/en-US/firefox/addon/12485/ You will have to log-in.
This is the same extension as in the screenshot.
Verified FIXED; reproduced the bug on production and verified on staging.
Status: RESOLVED → VERIFIED
Updated•15 years ago
|
Keywords: push-needed
Updated•9 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.
Description
•