Cast ChromeShell into the fiery pit of Mount Doom.

chrome/chrome.gyp

Index: chrome/chrome.gyp
diff --git a/chrome/chrome.gyp b/chrome/chrome.gyp
index 9f00efee212305ef5d6efc3b83631cbc08137b61..bda7831b462473a0d7c2bac8c4d056747fd184c3 100644
--- a/chrome/chrome.gyp
+++ b/chrome/chrome.gyp
@@ -667,6 +667,7 @@
           'target_name': 'chrome_locale_paks',
           'type': 'none',
           'variables': {
+            'package_name': 'chrome_locale_paks',

[newt (away), 2015/09/03 01:09:09]

The poorly named package_name variable needs to be defined here because we're
including chrome_android_paks.gypi below, which copies pak files into
out/Debug/assets/<(package_name)/.

Previously, package_name happened to be defined by (un?)lucky coincidence as
"chrome_shell_apk", which makes no sense. How? Well, chrome.gyp includes
chrome_android.gypi which used to include chrome_shell.gypi which defined
package_name as "chrome_shell_apk". How's that for unintended consequences of
gypi inclusion and global variable propagation?

[Nico, 2015/09/03 01:49:00]

Thanks for this comment!

             'locale_pak_files': [ '<@(chrome_android_pak_locale_resources)' ],
           },
           'includes': [