Closed Bug 356579 Opened 19 years ago Closed 17 years ago

remove tr-tdk search plugin on update

Categories

(Firefox :: Installer, defect)

1.5.0.x Branch
defect
Not set
normal

Tracking

()

RESOLVED FIXED

People

(Reporter: Pike, Assigned: Pike)

Details

(Keywords: fixed1.8.0.8)

Attachments

(2 files)

As pointed out in bug 354576, the tr-tdk search plugin shipped with turkish versions of 1.5 is broken due to an incompatible site change, and can't be resurrected. Updates should remove the plugin, and thus, we should add the two files to removed-files.in. Patch coming up.
Attachment #242189 - Flags: review?(aserkant)
The second patch should get rid of the tr-tdk plugins for existing installs, just like we did with dictionary.com.
Attachment #242191 - Flags: review?(benjamin)
Attachment #242191 - Flags: review?(benjamin) → review+
We should take this bug instead of bug 354576, if this get's plussed, minus the other.
Flags: blocking1.8.0.8?
This is the 1.8.0 branch version of bug 354576, moving blocking flag here.
Flags: blocking1.8.0.8? → blocking1.8.0.8+
(In reply to comment #1) > Created an attachment (id=242189) [edit] > l10n part, don't ship tr-tdk on 1.5.0.x > This one is OK: + I can't set flag + as I'm told by Bugzilla that I'm not authorised.
Comment on attachment 242189 [details] [diff] [review] l10n part, don't ship tr-tdk on 1.5.0.x marking review by aserkant (note, I fixed your bugzilla privs, too). Requesting approval for 1.8.0.8
Attachment #242189 - Flags: review?(aserkant)
Attachment #242189 - Flags: review+
Attachment #242189 - Flags: approval1.8.0.8?
Attachment #242191 - Flags: approval1.8.0.8?
Comment on attachment 242189 [details] [diff] [review] l10n part, don't ship tr-tdk on 1.5.0.x approved for 1.8.0 branch, a=dveditz
Attachment #242189 - Flags: approval1.8.0.8? → approval1.8.0.8+
Comment on attachment 242191 [details] [diff] [review] installer part, remove tr-tdk on update approved for 1.8.0 branch, a=dveditz
Attachment #242191 - Flags: approval1.8.0.8? → approval1.8.0.8+
Checked in. I'm leaving the bug open for investigating how things should behave on the 1.8 branch wrt updates from the 1.5 tree to the 2.0 one.
Keywords: fixed1.8.0.8
This seems to have been fixed allright by now.
Status: NEW → RESOLVED
Closed: 17 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: