When running setup_packages in a docker image that derives from another, we're currently overwriting the file that contains the apt sources for the package artifact repositories that were used for the parent docker image. This doesn't cause practical problems for the existing docker images, but in some cases where a user gets a one-click loaner, it might cause problems when they try to install a package that has a dependency that can't be fulfilled once those sources are overwritten. To give a practical example, installing the gdb package from wheezy requires libpython2.7, but if you try to do that on a derivative of the debian7-base image, you don't have the deb7-python artifact repository in your sources.list, and would fail to install gdb because apt can't install a version of libpython2.7 that can be installed alongside the python2.7 that is installed. By putting easy repository in a separate file, named after the task id of the corresponding package task, we ensure each an every one of them is uniquely represented in /etc/apt/sources.list.d. Review commit: https://reviewboard.mozilla.org/r/218328/diff/#index_header See other reviews: https://reviewboard.mozilla.org/r/218328/

The GDB version in Debian wheezy doesn't handle the DWARF data that the GCC version we use to build Firefox and toolchains produce. So we take the GDB version from Debian stretch and backport it. Review commit: https://reviewboard.mozilla.org/r/218330/diff/#index_header See other reviews: https://reviewboard.mozilla.org/r/218330/

We don't actually go install the package, but if a one-click loaner user goes on to apt-get install gdb, they will get a version that is useful, rather than the version in wheezy that won't give them e.g. variables information. Review commit: https://reviewboard.mozilla.org/r/218332/diff/#index_header See other reviews: https://reviewboard.mozilla.org/r/218332/