[buildd-tools-devel] [GIT] sbuild branch master updated. debian/sbuild-0.65.2-1-43-gdaa4a9f

Johannes Schauer josch at moszumanska.debian.org
Sun Oct 4 06:44:12 UTC 2015


This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "sbuild".

The branch, master has been updated
       via  daa4a9fca9e62b0f718c36fd9fdfec14c7d7936f (commit)
       via  eae087729bf77b8b4d08b24811da45f53eabd9ac (commit)
       via  8a3e12c3edf768ddeb66b29157d3cf1a7ad3d48d (commit)
       via  8b9c2e45edc6ed08ea9a748a7dcc6b0ef6e1899c (commit)
       via  f1a0217b5752bd98f3456f5245c77292d048e80c (commit)
       via  f4330987e564a7ab926f8cc65338a3b34ff00c0a (commit)
       via  2eb53b5150d51b2063544febf35ba92f11abe235 (commit)
       via  d0cc9b3184349384d32aec7b4adad196f7b68a2a (commit)
      from  dce5caaa7bb149032a3fe1777935e2965ff34f86 (commit)

Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.

- Log -----------------------------------------------------------------
commit daa4a9fca9e62b0f718c36fd9fdfec14c7d7936f
Author: Johannes 'josch' Schauer <josch at mister-muffin.de>
Date:   Thu Oct 1 20:43:04 2015 +0200

    test/sbuild.in: now that a custom configuration file can be passed to sbuild, use the default config to reduce influence of the system config on the test cases

commit eae087729bf77b8b4d08b24811da45f53eabd9ac
Author: Johannes 'josch' Schauer <josch at mister-muffin.de>
Date:   Thu Oct 1 20:42:13 2015 +0200

    test/sbuild.in: explicitly set schroot chroot and schroot working directory

commit 8a3e12c3edf768ddeb66b29157d3cf1a7ad3d48d
Author: Dima Kogan <dima at secretsauce.net>
Date:   Sat Oct 18 15:41:59 2014 -0700

    Replaced all unicode-printed chars with plain ASCII (Closes: #765886, #665847)
    
    Yes, it is nearly 2016 and Debian has been using unicode for over a
    decade. Yes, everybody should be using it by now. What made me (josch)
    remove unicode characters and revert to back to ASCII is that the only
    advantage of using unicode characters is:
    
     - Slightly more pretty output. I'd say the improvement is so little
       that I would call it negligible.
    
    But on the other hand, there is a disadvantage which I'd call much more
    practical than maybe having a more visually pleasing output:
    
     - sbuild logs are not necessarily only consumed by users of Debian or
       transmitted with technologies we ship with Debian. They might be
       copy-pasted to mail messages (read by people with very different clients),
       personal book keeping programs and web interfaces of services with no
       unicode support. Yes, all these places *should* know unicode but sbuild
       logs should also not become less readable if they don't.
    
    Given that there is really no hard *requirement* for keeping the unicode
    characters for pretty drawing (in contrast to a program which, for
    example, handles asian script), I'm applying Dima's patch.
    
    The reason why ASCII output is now the default instead of adding a
    --ascii option is, that at the time where the build is done, one does
    not know which places the build logs might reach.  The same reasoning
    goes for why unicode support is not enabled or disabled depending on the
    capabilities of the terminal sbuild outputs to.  Instead, if one is very
    sure that the log will never be consumed by or transmitted through a
    medium without unicode support, then there could be a --pretty-unicode
    option in the future which explicitly enables the pretty boxes again.

commit 8b9c2e45edc6ed08ea9a748a7dcc6b0ef6e1899c
Author: Johannes 'josch' Schauer <josch at mister-muffin.de>
Date:   Thu Oct 1 07:37:59 2015 +0200

    man/sbuild.1.in: update docs for --dist option (Closes: #783135)

commit f1a0217b5752bd98f3456f5245c77292d048e80c
Author: Dima Kogan <dima at secretsauce.net>
Date:   Sat Apr 25 12:56:15 2015 -0700

    Added --xxx-failed-commands
    
    Added several external commands that trigger on failure. The way these are
    intended to be used is to spawn a shell if something goes wrong so that the user
    can poke around and find the problem. Most commonly you would do
    
      sbuild --anything-failed-commands %s
    
    Currently we have
    
     --build-deps-failed-commands
     --build-failed-commands
     --anything-failed-commands
    
    Where --anything-failed-commands simply activates all of the others

commit f4330987e564a7ab926f8cc65338a3b34ff00c0a
Author: Dima Kogan <dima at secretsauce.net>
Date:   Tue Apr 21 16:14:42 2015 -0700

    external command %SBUILD_SHELL produces an interactive shell (Closes: #783091)

commit 2eb53b5150d51b2063544febf35ba92f11abe235
Author: Dima Kogan <dima at secretsauce.net>
Date:   Mon Apr 20 22:12:56 2015 -0700

    external commands are now unparsed strings (Closes: #782672)
    
    when handling external commands (--starting-build-commands and others), I now
    keep the input string as is, and pass it to the shell, instead of splitting it
    on whitespace and then reassembling it. This reassembling was being done
    improperly, with shell internals such as < being erroneously escaped. Keeping
    the string as is allows the user to give the command they want.
    
    This is implemented by keeping the COMMAND and INTCOMMAND keys same as they were
    (array-refs of strings), but adds additional COMMAND_STR and INTCOMMAND_STR keys
    that have the string representation. The non-STR versions are always populated,
    and the external command options populate the _STR ones as well. When running
    the commands, we use the _STR options if we have them, otherwise, we recombine
    as before.
    
    Since the old array-ref-based code path is still there, old commandlines and
    configurations remain working

commit d0cc9b3184349384d32aec7b4adad196f7b68a2a
Author: Johannes 'josch' Schauer <josch at mister-muffin.de>
Date:   Thu Sep 3 08:59:37 2015 +0200

    add aspcud based resolver

-----------------------------------------------------------------------

Summary of changes:
 lib/Sbuild.pm                                    |  10 +--
 lib/Sbuild/{AptResolver.pm => AspcudResolver.pm} |  26 +++---
 lib/Sbuild/Base.pm                               |  16 ++--
 lib/Sbuild/Build.pm                              | 109 +++++++++++++++++------
 lib/Sbuild/Chroot.pm                             |   4 +
 lib/Sbuild/ChrootInfoSchroot.pm                  |   6 +-
 lib/Sbuild/ChrootPlain.pm                        |  41 +++++----
 lib/Sbuild/ChrootSchroot.pm                      |  14 ++-
 lib/Sbuild/ChrootSudo.pm                         |  43 +++++----
 lib/Sbuild/Conf.pm                               |  20 +++--
 lib/Sbuild/Makefile.am                           |   1 +
 lib/Sbuild/Options.pm                            |  39 +++++---
 lib/Sbuild/Resolver.pm                           |   3 +
 man/sbuild.1.in                                  |  70 ++++++++++++---
 test/sbuild.in                                   |  12 +--
 15 files changed, 285 insertions(+), 129 deletions(-)
 copy lib/Sbuild/{AptResolver.pm => AspcudResolver.pm} (78%)


hooks/post-receive
-- 
sbuild



More information about the Buildd-tools-devel mailing list