Closed Bug 353681 Opened 19 years ago Closed 19 years ago

Product XPIs are missing from 1.5.0.7 XPI directory

Categories

(Release Engineering :: General, defect)

x86
Windows XP
defect
Not set
normal

Tracking

(Not tracked)

VERIFIED FIXED

People

(Reporter: mkaply, Assigned: rhelmer)

References

()

Details

Normally, after we ship a release, in addition to the language XPIs, the product XPIs are in the XPI directory. See: ftp://ftp.mozilla.org/pub/mozilla.org/firefox/releases/1.5.0.6/win32/xpi/ adt.xpi browser.xpi talkback.xpi xpcom.xpi These files are not present in the 1.5.0.7 directory. This makes it impossible to install the developer tools or talkback on a build that doesn't have them.
I'm pretty sure this is by design, since the installer doesn't use these xpi's any more. See also bug 346639.
Summary: Product XPIs are missing frmo 1.5.0.7 XPI directory → Product XPIs are missing from 1.5.0.7 XPI directory
Well that really sucks. But that bug was about 1.5.0.5 - they came back for 1.5.0.6. Either way, ADT.XPI and TALKBACK.XPI should be on the site since you can install 1.5.0.X without them and it would be nice to be able to add them in.
Rob: Can you talk a look?
Assignee: build → rhelmer
Severity: major → critical
We turned this off on purpose. CC'ing Benjamin as he is more qualified to comment than I am.
Severity: critical → normal
Just to be clear what is happening with us. Inside IBM, we ship Firefox without talkback or the developer tools. We don't ship the dev tools because it doesn't make sense to give them to people who don't need them. For people to get the dev tools after installing Firefox from our internal servers, we pointed them to the ftp site to get the adt.xpi to add the dev tools. There should be a place to get the adt.xpi at least that corresponds to a release. We also don't ship talkback for security reasons. But again, we have had cases where people had persistent crashes, so we had them go explicitly install talkback so we could get the data. This is now impossible.
Well, we should be shipping a real DOMI XPI (extension, not installer XPI), but that's a separate bug. I don't think we should be shipping the xpinstall adt.xpi.
(In reply to comment #6) > Well, we should be shipping a real DOMI XPI (extension, not installer XPI), but > that's a separate bug. I don't think we should be shipping the xpinstall > adt.xpi. > Actually, I like the installer XPI because it installs the DOM inspector as a system extension. Also, the problem is that inspector.dll is tied to each release, so it doesn't really fit into the addons.mozilla.org model.
I am going to push these components to the mirrors today (for win32 only).
Status: NEW → ASSIGNED
The XPIs have been pushed to the mirrors, in: firefox/releases/1.5.0.7/win32/xpi/ All mirrors should have the files within 12 hours. Thanks for pointing this out Michael. I'll make sure to announce this kind of change more publically in the future, so we can get this ironed out before release instead of after.
Status: ASSIGNED → RESOLVED
Closed: 19 years ago
Resolution: --- → FIXED
Product: mozilla.org → Release Engineering
You need to log in before you can comment on or make changes to this bug.