Closed
Bug 494742
Opened 15 years ago
Closed 15 years ago
Update shipped copy of blocklist.xml
Categories
(Firefox :: General, defect)
Tracking
()
RESOLVED
FIXED
Tracking | Status | |
---|---|---|
status1.9.2 | --- | beta2-fixed |
status1.9.1 | --- | .6-fixed |
People
(Reporter: nthomas, Assigned: mossop)
References
Details
(Keywords: verified1.9.1)
Attachments
(1 file, 2 obsolete files)
1.79 KB,
patch
|
morgamic
:
review+
shaver
:
approval1.9.2+
dveditz
:
approval1.9.1.6+
|
Details | Diff | Splinter Review |
Here's the diff on mozilla-1.9.1 to https://addons.mozilla.org/blocklist/1/%7Bec8030f7-c20a-464f-9b0e-13a3a9e97384%7D/3.5/ It appears to be removing a couple of Firefox version limits. Note * the URL is assuming that no platform-specific blocking is going on * depends on resolution in bug 479095 - it's desirable (but maybe not mandatory) to include AVG in the shipped file if we're going to block it
Flags: blocking-firefox3.5?
Updated•15 years ago
|
Flags: blocking-firefox3.5? → blocking-firefox3.5+
Assignee | ||
Comment 1•15 years ago
|
||
For now there is nothing to do here. The correct URL to use for Firefox 3.5 and later is: https://addons.mozilla.org/blocklist/3/%7Bec8030f7-c20a-464f-9b0e-13a3a9e97384%7D/3.5/Firefox/20090105024647/blocklist-sync/en-US/nightly/blocklist-sync/default/default/ The versionRange entries that are missing in the url in comment 0 is because the old schema did not support versionRange entries for plugins. Not sure whether it is worth holding this open in case bug 479095 is resolved or not. I know there are a few other blocklist bugs that might be fixed in the meantime too.
Comment 2•15 years ago
|
||
Oh, if we're already using the right URL and have content there, then this doesn't need to block. I'd rather block on individual issues like bug 479095 instead of a metabug. Should this be resolved invalid?
Flags: blocking-firefox3.5+ → blocking-firefox3.5-
Assignee | ||
Comment 3•15 years ago
|
||
(In reply to comment #2) > Oh, if we're already using the right URL and have content there, then this > doesn't need to block. I'd rather block on individual issues like bug 479095 > instead of a metabug. > > Should this be resolved invalid? The issue is that as entries are added to the blocklist database we also should update the in-tree copy of blocklist.xml, since we haven't yet got this working automatically in mercurial like we have in cvs. However it isn't critical, it is just about giving new users the most up to date blocklist instantly. We can just close this if you like, but if any changes to the blocklist are made and we are going to spin a new RC then I'll still be bugging you for approval to land the blocklist changes in tree.
Assignee | ||
Comment 4•15 years ago
|
||
Finding it difficult to track exactly when updates to the blocklist are pushed but I think this change was too late to make it into 3.5 final anyway. But we should land it on branch and trunk.
Assignee: nobody → dtownsend
Attachment #379506 -
Attachment is obsolete: true
Status: NEW → ASSIGNED
Comment 5•15 years ago
|
||
Dave: is this now fixed, 3.5.1 is out :-)
Assignee | ||
Comment 6•15 years ago
|
||
(In reply to comment #5) > Dave: is this now fixed, 3.5.1 is out :-) No, see comment 4
Assignee | ||
Comment 7•15 years ago
|
||
Comment on attachment 387009 [details] [diff] [review] update blocklist.xml Mike, before landing updates to the copy of the blocklist that we ship with the application beltzner would just like someone to assert that these changes match those made on the server. This just adds the block from bug 479095.
Attachment #387009 -
Flags: review?(morgamic)
Assignee | ||
Updated•15 years ago
|
Summary: Update shipped copy of blocklist.xml before 3.5rc1 builds → Update shipped copy of blocklist.xml
Assignee | ||
Updated•15 years ago
|
Attachment #387009 -
Attachment is obsolete: true
Attachment #387009 -
Flags: review?(morgamic)
Assignee | ||
Comment 8•15 years ago
|
||
Mike, can you confirm that these were the changes to the blocklist from the two dependant bugs, then I can land this and it can be included in Firefox installs.
Attachment #404126 -
Flags: review?(morgamic)
Comment 9•15 years ago
|
||
Could diff it against: https://addons.mozilla.org/blocklist/1/%7Bec8030f7-c20a-464f-9b0e-13a3a9e97384%7D/3.0b1/?omgpeanuts
Assignee | ||
Comment 10•15 years ago
|
||
Well it's just a diff between the result of the url in comment 1 and the current version in tree, but apparently I need to get someone to agree it is right.
Comment 11•15 years ago
|
||
Comment on attachment 404126 [details] [diff] [review] updated blocklist.xml Looks like we're just picking up stuff that's currently served. Looks good to me.
Attachment #404126 -
Flags: review?(morgamic) → review+
Assignee | ||
Comment 12•15 years ago
|
||
Landed on trunk with one minor change: http://hg.mozilla.org/mozilla-central/rev/f3e9ac90c086
Status: ASSIGNED → RESOLVED
Closed: 15 years ago
Resolution: --- → FIXED
Assignee | ||
Updated•15 years ago
|
Attachment #404126 -
Flags: approval1.9.2?
Attachment #404126 -
Flags: approval1.9.1.5?
Comment 13•15 years ago
|
||
Comment on attachment 404126 [details] [diff] [review] updated blocklist.xml Approved for 1.9.1.6, a=dveditz for release-drivers
Attachment #404126 -
Flags: approval1.9.1.6? → approval1.9.1.6+
Updated•15 years ago
|
Flags: blocking-firefox3.6?
Reporter | ||
Comment 14•15 years ago
|
||
While this doesn't add the Skype blocking, could we get an a1.9.2+ on attachment 404126 [details] [diff] [review] before 3.6b2 spins ?
Assignee | ||
Comment 15•15 years ago
|
||
Pushed to 1.9.1 branch http://hg.mozilla.org/releases/mozilla-1.9.1/rev/d7124948aecb
status1.9.1:
--- → .6-fixed
Comment on attachment 404126 [details] [diff] [review] updated blocklist.xml a=shaver
Attachment #404126 -
Flags: approval1.9.2? → approval1.9.2+
Flags: blocking-firefox3.6? → blocking-firefox3.6+
Assignee | ||
Comment 17•15 years ago
|
||
Pushed to 1.9.2 branch: http://hg.mozilla.org/releases/mozilla-1.9.2/rev/44825c9d3eb8
status1.9.2:
--- → beta2-fixed
Comment 18•15 years ago
|
||
Verified for 1.9.1 in source. Nothing else to do here.
Keywords: verified1.9.1
You need to log in
before you can comment on or make changes to this bug.
Description
•