Makefile | 13 7 + 6 - 0 !
build | 6 3 + 3 - 0 !
2 files changed, 10 insertions(+), 9 deletions(-)

 use obs-build in locations and executable names
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit

  instead of just build.

Signed-off-by: Dimitri John Ledkov <dimitri.j.ledkov@intel.com>
Signed-off-by: Hctor Orn Martnez <zumbi@debian.org>

build-recipe-debootstrap | 5 5 + 0 - 0 !
1 file changed, 5 insertions(+)

 hack: make glibc build
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit

See:
  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=844420

Signed-off-by: Sjoerd Simons <sjoerd.simons@collabora.co.uk>
Signed-off-by: Hctor Orn Martnez <zumbi@debian.org>

Build.pm | 4 3 + 1 - 0 !
1 file changed, 3 insertions(+), 1 deletion(-)

 dsc: keep everything
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit

Debian package build dependencies allow for direct or indirect build
cycles, when doing a full distribution build in OBS this means keeping
the keep list gets very tedious very quickly.

Adjust the default keep processing such that for Debian (dsc) builds
everything is kept by default

Signed-off-by: Sjoerd Simons <sjoerd.simons@collabora.co.uk>
Signed-off-by: Hctor Orn Martnez <zumbi@debian.org>

build-recipe-dsc | 2 1 + 1 - 0 !
1 file changed, 1 insertion(+), 1 deletion(-)

 build-recipe-dsc: don't rebuild the source package

If we use build suffixes, rebuilding the source package will
result in the build suffix being included into the source package,
which we'd rather avoid.

Signed-off-by: Andrew Shadura <andrew.shadura@collabora.co.uk>

build-recipe-debootstrap | 6 5 + 1 - 0 !
1 file changed, 5 insertions(+), 1 deletion(-)

 debootstrap: add fallback for debian sid distro
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit

  When attempting to build Debian unstable, distribution is
  calculated using lsb, which relies on apt cache. As our
  build systems lack apt cache and network we cannot detect
  we are building for Debian SID (aka unstable).
  For more background information see: DebianBug#845651

Signed-off-by: Hctor Orn Martnez <hector.oron@collabora.co.uk>
Tested-by: Hctor Orn Martnez <hector.oron@collabora.co.uk>

build-pkg-deb | 7 7 + 0 - 0 !
1 file changed, 7 insertions(+)

 added policy-rc.d that turns invoke-rc.d into a no-op
 The problem is that in older versions of Ubuntu, the unpack packageset
 from the target distribution to be able to run the first-stage
 debootstrap is not very minimal.
 .
 In particular, it includes packages like initscripts, udev and procps,
 which have initscripts that are started by postinst. In older Ubuntu,
 when a postinst runs invoke-rc.d, it communicates with Upstart via a
 mechanism that can escape from the chroot and talk to the host system's
 Upstart (!); and if it can't, invoke-rc.d will fail and the first-stage
 bootstrap will also fail.
 .
 The symptom is that on workers whose host OS did not boot using Upstart
 (for example Debian stretch, but not Ubuntu trusty), the first-stage
 bootstrap fails with:
 .
  [   22s] initctl: Unable to connect to Upstart: Failed to connect to
  socket /com/ubuntu/upstart: Connection refused
 .
 So here is a patch to provide OBS-level solution that adds a policy-rc.d
 that turns invoke-rc.d into a no-op, just like debootstrap does to
 prevent processes in deb build chroots from trying to start system
 services.