Closed
Bug 774903
Opened 12 years ago
Closed 12 years ago
Fix Yandex distribution updates
Categories
(Release Engineering :: Release Requests, defect, P1)
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: lsblakk, Assigned: nthomas)
References
Details
Currently the Yandex partner distro is showing the Russian What's New page that says "Google is the default search engine". This is incorrect for the distro so please disable the updates, suppress the What's New page for Yandex distribution then re-enable updates once disabled.
Assignee | ||
Updated•12 years ago
|
Assignee: nobody → nrthomas
Priority: -- → P1
Assignee | ||
Updated•12 years ago
|
Assignee: nrthomas → nobody
Component: Release Engineering → Release Engineering: Releases
QA Contact: bhearsum
Assignee | ||
Updated•12 years ago
|
Assignee: nobody → nrthomas
Assignee | ||
Comment 1•12 years ago
|
||
Their 14.0.1 mac build makes his request for updates: AUS:SVC Checker:getUpdateURL - update URL: https://aus3.mozilla.org/update/3/Firefox/14.0.1/20120713134347/Darwin_x86_64-gcc3-u-i386-x86_64/ru/release-cck-yandex/Darwin%2010.8.0/yandex/1.1/update.xml?force=1 confirming the channel we want is release-cck-yandex.
Assignee | ||
Comment 2•12 years ago
|
||
Create some update blocks: cd /opt/aus2/snippets/staging/ for d in Firefox-14.0.1-build1/Firefox/*/*/*/ru; do echo $d mkdir -p ${d/build1/build1-yandexblock}/release-cck-yandex/ touch ${d/build1/build1-yandexblock}/release-cck-yandex/{partial,complete}.txt done backupsnip Firefox-14.0.1-build1-yandexblock pushsnip Firefox-14.0.1-build1-yandexblock No further updates will be offered to 10 through to 13.0.1 Yandex users, all platforms. Verification URLS: https://aus3.mozilla.org/update/3/Firefox/13.0.1/20120614114901/WINNT_x86-msvc/ru/release-cck-yandex/foo/yandex/1.1/update.xml https://aus3.mozilla.org/update/3/Firefox/13.0/20120601045813/Darwin_x86_64-gcc3-u-i386-x86_64/ru/release-cck-yandex/foo/yandex/1.1/update.xml https://aus3.mozilla.org/update/3/Firefox/12.0/20120420145725/Linux_x86-gcc3/ru/release-cck-yandex/foo/yandex/1.1/update.xml Those all offered 14.0.1 until I deployed the snippets.
Comment 3•12 years ago
|
||
Pascal, are the changes to the website live? If so, we should unblock updates.
Comment 4•12 years ago
|
||
Yandex hasn't reviewed yet the translation, I will push once Alexander and his team confirm that the text is good to go.
Comment 5•12 years ago
|
||
Update to whatsnew page pushed in r107617, we need to wait for the server to pick up the update about 20mn. If the server doesn't update (it happenned yesterday), an IT bug should be filed to restart apache.
Comment 6•12 years ago
|
||
thanks, pascal, much appreciated. Lucas/Nick, once it's live we should clear the updates.
Comment 7•12 years ago
|
||
The server is not picking up updates, I asked webdev to look at it
Comment 8•12 years ago
|
||
Filed bug 775084 to ask IT to restart the server to force an update of the page.
Comment 9•12 years ago
|
||
IT restarted the server, the updated whatsnew page is now on production.
Comment 10•12 years ago
|
||
Now that the new WN page is on production, let's re-enable updates for the Yandex repacks and also stop suppressing the WN page. Thanks!
Assignee | ||
Comment 11•12 years ago
|
||
Currently we have * ru updates showing What's New after updates, except * yandex updates are blocked So could you clarify what you mean by 'stop suppressing the WN page' ?
Comment 12•12 years ago
|
||
(In reply to Nick Thomas [:nthomas] from comment #11) > Currently we have > * ru updates showing What's New after updates, except > * yandex updates are blocked > > So could you clarify what you mean by 'stop suppressing the WN page' ? I mistakenly thought we'd done more than block yandex updates. Let's just rollback that block.
Assignee | ||
Comment 13•12 years ago
|
||
cd /opt/aus2/snippets/staging/Firefox-14.0.1-build1-yandexblock/ for d in Firefox/*/*/*/ru/*; do rm -rfv /opt/aus2/incoming/3/$d done The in comment #2 are offering 14.0.1 again.
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → FIXED
Updated•11 years ago
|
Product: mozilla.org → Release Engineering
You need to log in
before you can comment on or make changes to this bug.
Description
•