Comment 8 for bug 1390416

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Related fix merged to fuel-main (master)

Reviewed: https://review.openstack.org/133640
Committed: https://git.openstack.org/cgit/stackforge/fuel-main/commit/?id=3eb1af76bd52ed65c2cdd6737a9209cf38af9b3f
Submitter: Jenkins
Branch: master

commit 3eb1af76bd52ed65c2cdd6737a9209cf38af9b3f
Author: Alexei Sheplyakov <email address hidden>
Date: Mon Nov 10 18:41:27 2014 +0300

    mirror-ubuntu: use the OSCI repo for bootstrapping the chroot

    If some of the base packages (like python-minimal) has been rebuilt
    we should use them when bootstrapping the temporary chroot. Otherwise
    the newly created apt repo will contain either only upstream version of
    the package in question, or both the upstream and customized versions.

    Assume that the base package X has been customized. The customized version
    of X is located on the OSCI mirror. Multistrap does not use that mirror, so
    the upstream version of X gets pulled into the apt cache (typically
    /var/apt/cache/archives) during bootstrapping of the chroot. Packages
    depending on X pull its customized version (since the OSCI repo is added
    to the sources.list.d after bootstrapping the chroot). If X is an essential
    package (so other packages are not obliged to declare dependence on X)
    only the upstream version of X gets into the apt repo being created.

    Use the OSCI mirror when bootstrapping the chroot to avoid the problem.

    While at it reduce copy-paste noise in createchroot.mk and make it a little
    bit less obscure.

    Related-bug: #1390416
    Related-bug: #1390044
    Related-bug: #1383641

    Change-Id: Ic418c760a1635d5c72cc108658d412228fb83a62