Makefile | 12 6 + 6 - 0 !
build | 6 3 + 3 - 0 !
2 files changed, 9 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: Andrej 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-recipe-dsc | 9 7 + 2 - 0 !
1 file changed, 7 insertions(+), 2 deletions(-)

 build-recipe-dsc: move all build results,
 not just *.deb and *.changes

The purpose of the changes file is to list everything that is to be
installed into the Debian (or derivative) archive, including *.deb,
*.udeb (micro-debs for the Debian installer), *.ddeb (detached debug
symbols, in Ubuntu and its derivatives) and *.buildinfo (details of the
build environment, mainly for reproducible builds). If we're providing
an equivalent of the Debian archive, then we should include all the
same files.

This change ensures that all build products get moved into the right
place, even if they are file types that obs-build doesn't yet know about,
or even file types that haven't been invented yet.

When obs-build is used in conjunction with OBS, changes to bs_publish
are also likely to be necessary for a full-stack solution.

Signed-off-by: Simon McVittie <smcv@collabora.com>

Makefile | 12 11 + 1 - 0 !
build | 2 2 + 0 - 0 !
common_functions | 2 2 + 0 - 0 !
init_buildsystem | 2 2 + 0 - 0 !
4 files changed, 17 insertions(+), 1 deletion(-)

 log the version number during startup

When testing OBS behaviour changes, it's useful to be able to look
at a build log and see which code was running.

Signed-off-by: Simon McVittie <smcv@collabora.com>

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

 debootstrap: print the exact command we're going to run

debootstrap is not a simple command, and there are some subtleties to
the options we use, so we should log exactly what we did.

The incantation with `$(printf ' %q' "$@")` is to log the contents
of $@, correctly shell-quoted to avoid ambiguity (in case there are
spaces in an argument). It should expand to something like

    running debootstrap: chroot /buildroot debootstrap --etc --etc...

Signed-off-by: Simon McVittie <smcv@collabora.com>

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

 deb: show version of each package that we preinstall

If packages fail to unpack or configure during the preinstall step,
it's useful for the log to indicate precisely which packages were used.

Signed-off-by: Simon McVittie <smcv@collabora.com>

build-recipe-dsc | 33 33 + 0 - 0 !
1 file changed, 33 insertions(+)

 build-recipe-dsc: list contents of build results

Debian's sbuild dumps the metadata and contents of all build results
into its own logs, which is often helpful when comparing build logs and
package contents. Let's do the same.

Signed-off-by: Simon McVittie <smcv@collabora.com>

build-recipe-dsc | 25 25 + 0 - 0 !
1 file changed, 25 insertions(+)

 build-recipe-dsc: show information about the build chroot

This vaguely mimics what Debian's sbuild does, although the precise

build-vm-openstack | 2 1 + 1 - 0 !
1 file changed, 1 insertion(+), 1 deletion(-)

 use python 3 for the openstack console