[opensuse-buildservice] Re: [PATCH] turn off mkbaselibs verbosity
Am Dienstag, 27. April 2010 11:45:44 schrieben Sie:
From: Ludwig Nussel <ludwig.nussel@suse.de>
--- build | 3 +-- 1 files changed, 1 insertions(+), 2 deletions(-)
diff --git a/build b/build index a7f1e37..9b700d0 100755 --- a/build +++ b/build @@ -444,8 +444,7 @@ function create_baselibs { if test -z "$BASELIBS_CFG" -a -e $BUILD_ROOT/usr/lib/build/baselibs.conf ; then BASELIBS_CFG="-c /usr/lib/build/baselibs.conf" fi - echo "RUNNING internal mkbaselibs ... " Could we keep a msg similar to this ^^^ as we've _no_ clue where to start debugging otherwise ? - chroot $BUILD_ROOT su -c "/usr/lib/build/mkbaselibs -v $BASELIBS_GLOBAL $BASELIBS_CFG $BPKGS" - $BUILD_USER || cleanup_and_exit 1 + chroot $BUILD_ROOT su -c "/usr/lib/build/mkbaselibs $BASELIBS_GLOBAL $BASELIBS_CFG $BPKGS" - $BUILD_USER || cleanup_and_exit 1 else # use external version rm -rf $BUILD_ROOT/.mkbaselibs
Best, Jan-Simon -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
Jan-Simon Möller wrote:
Am Dienstag, 27. April 2010 11:45:44 schrieben Sie:
From: Ludwig Nussel <ludwig.nussel@suse.de>
--- build | 3 +-- 1 files changed, 1 insertions(+), 2 deletions(-)
diff --git a/build b/build index a7f1e37..9b700d0 100755 --- a/build +++ b/build @@ -444,8 +444,7 @@ function create_baselibs { if test -z "$BASELIBS_CFG" -a -e $BUILD_ROOT/usr/lib/build/baselibs.conf ; then BASELIBS_CFG="-c /usr/lib/build/baselibs.conf" fi - echo "RUNNING internal mkbaselibs ... "
Could we keep a msg similar to this ^^^ as we've _no_ clue where to start debugging otherwise ?
It already prints "... creating baselibs" a few lines above that one, isn't that sufficient? cu Ludwig -- (o_ Ludwig Nussel //\ V_/_ http://www.suse.de/ SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nuernberg) -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
Am Mittwoch, 28. April 2010 16:36:20 schrieb Ludwig Nussel:
Jan-Simon Möller wrote:
Am Dienstag, 27. April 2010 11:45:44 schrieben Sie:
From: Ludwig Nussel <ludwig.nussel@suse.de>
--- build | 3 +-- 1 files changed, 1 insertions(+), 2 deletions(-)
diff --git a/build b/build index a7f1e37..9b700d0 100755 --- a/build +++ b/build @@ -444,8 +444,7 @@ function create_baselibs { if test -z "$BASELIBS_CFG" -a -e $BUILD_ROOT/usr/lib/build/baselibs.conf ; then BASELIBS_CFG="-c /usr/lib/build/baselibs.conf" fi - echo "RUNNING internal mkbaselibs ... "
Could we keep a msg similar to this ^^^ as we've _no_ clue where to start debugging otherwise ?
It already prints "... creating baselibs" a few lines above that one, isn't that sufficient?
internal (embedded to distro) vs. external (installed on worker) ? Best, Jan-Simon -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
Jan-Simon Möller wrote:
Am Mittwoch, 28. April 2010 16:36:20 schrieb Ludwig Nussel:
Jan-Simon Möller wrote:
Am Dienstag, 27. April 2010 11:45:44 schrieben Sie:
From: Ludwig Nussel <ludwig.nussel@suse.de>
--- build | 3 +-- 1 files changed, 1 insertions(+), 2 deletions(-)
diff --git a/build b/build index a7f1e37..9b700d0 100755 --- a/build +++ b/build @@ -444,8 +444,7 @@ function create_baselibs { if test -z "$BASELIBS_CFG" -a -e $BUILD_ROOT/usr/lib/build/baselibs.conf ; then BASELIBS_CFG="-c /usr/lib/build/baselibs.conf" fi - echo "RUNNING internal mkbaselibs ... "
Could we keep a msg similar to this ^^^ as we've _no_ clue where to start debugging otherwise ?
It already prints "... creating baselibs" a few lines above that one, isn't that sufficient?
internal (embedded to distro) vs. external (installed on worker) ?
The internal version is preferred always. So only if the build script doesn't get installed in the chroot you see the external version. The build service worker enforces the internal version btw. cu Ludwig -- (o_ Ludwig Nussel //\ V_/_ http://www.suse.de/ SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nuernberg) -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
Am Mittwoch, 28. April 2010 17:15:25 schrieb Ludwig Nussel:
Jan-Simon Möller wrote:
Am Mittwoch, 28. April 2010 16:36:20 schrieb Ludwig Nussel:
Jan-Simon Möller wrote:
Am Dienstag, 27. April 2010 11:45:44 schrieben Sie:
From: Ludwig Nussel <ludwig.nussel@suse.de>
--- build | 3 +-- 1 files changed, 1 insertions(+), 2 deletions(-)
diff --git a/build b/build index a7f1e37..9b700d0 100755 --- a/build +++ b/build @@ -444,8 +444,7 @@ function create_baselibs { if test -z "$BASELIBS_CFG" -a -e $BUILD_ROOT/usr/lib/build/baselibs.conf ; then BASELIBS_CFG="-c /usr/lib/build/baselibs.conf" fi - echo "RUNNING internal mkbaselibs ... "
Could we keep a msg similar to this ^^^ as we've _no_ clue where to start debugging otherwise ?
It already prints "... creating baselibs" a few lines above that one, isn't that sufficient?
internal (embedded to distro) vs. external (installed on worker) ?
The internal version is preferred always. So only if the build script doesn't get installed in the chroot you see the external version. The build service worker enforces the internal version btw.
Hi! I know this, but can you see it in the log ? Think of: * You get a build log with an error regarding mkbaselibs (or it doesn't start up - whatever) * You can't tell which version was preferred (by reading the log)? Right ? * Prjconf might have changed as "build" is in support - whatever reason it might be. Solution: * just tell which one was used in the log Or did I miss something ? Best, Jan-Simon -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
Jan-Simon Möller wrote:
Am Mittwoch, 28. April 2010 17:15:25 schrieb Ludwig Nussel:
The internal version is preferred always. So only if the build script doesn't get installed in the chroot you see the external version. The build service worker enforces the internal version btw.
I know this, but can you see it in the log ?
grep "installing build-" < log build script installed => mkbaselibs is the internal version. no build script installed => baselibs is not run in worker case. Anyways, that create_baselibs function is ugly anyways. So feel free to refactor and have it print useful information. cu Ludwig -- (o_ Ludwig Nussel //\ V_/_ http://www.suse.de/ SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nuernberg) -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
participants (2)
-
Jan-Simon Möller -
Ludwig Nussel