[elbe-devel] [PATCH 04/13] use pinning preferences also on incremental builds

[Manuel Traut]

Currently pinning works only correctly for an initial image build.

If an incremental build is done, the pinning is not effective, because
  it is set inside the debootstrap path.

Configure pinning from the BuildEnv constructor to enable it for both
cases.

This fixes github issue #119

Signed-off-by: Manuel Traut <manut at linutronix.de>
---
 elbepack/rfs.py | 3 +--
 1 file changed, 1 insertion(+), 2 deletions(-)

diff --git a/elbepack/rfs.py b/elbepack/rfs.py
index 8dc3bed1..2fa8f1a4 100644
--- a/elbepack/rfs.py
+++ b/elbepack/rfs.py
@@ -55,6 +55,7 @@ class BuildEnv ():
             self.need_dumpdebootstrap = False
 
         self.initialize_dirs (build_sources=build_sources)
+        self.create_apt_prefs ()
 
     def cdrom_umount(self):
         if self.xml.prj.has ("mirror/cdrom"):
@@ -107,8 +108,6 @@ class BuildEnv ():
 
         self.log.h2( "debootstrap log" )
 
-        self.create_apt_prefs ()
-
         arch = self.xml.text ("project/buildimage/arch", key="arch")
 
         host_arch = self.log.get_command_out(
-- 
2.15.1