[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

sbuild_0.62.5-1~bpo60+1_amd64.changes is NEW



(new) buildd_0.62.5-1~bpo60+1_all.deb extra devel
Daemon for automatically building Debian binary packages from Debian sources
 The sbuild suite of programs (buildd and sbuild) are
 used to build binary packages from source packages.  The wanna-build
 database tracks packages which require building; buildd schedules
 work from information it gets from the wanna-build database; sbuild
 does the actual package building.
 .
 buildd is a daemon which will build Debian packages automatically
 using the wanna-build database to identify which packages need to be
 built.  Note that the wanna-build database is not packaged, and
 requires installing separately.
(new) libsbuild-perl_0.62.5-1~bpo60+1_all.deb extra perl
Tool for building Debian binary packages from Debian sources
 The sbuild suite of programs (wanna-build, buildd and sbuild) are
 used to build binary packages from source packages.  The wanna-build
 database tracks packages which require building; buildd schedules
 work from information it gets from the wanna-build database; sbuild
 does the actual package building.
 .
 This package contains the core library modules used by these
 programs.
(new) sbuild_0.62.5-1~bpo60+1.debian.tar.gz extra devel
(new) sbuild_0.62.5-1~bpo60+1.dsc extra devel
(new) sbuild_0.62.5-1~bpo60+1_all.deb extra devel
Tool for building Debian binary packages from Debian sources
 The sbuild suite of programs (buildd and sbuild) are used to build
 binary packages from source packages.  sbuild does the actual package
 building.
 .
 sbuild uses chroots to build packages, which act as virtual, minimal
 operating system installations dedicated to package building.  This
 means that a number of environments may be used for building
 simultaneously on the same machines, for example stable, testing,
 unstable and experimental.  When coupled with schroot to create
 snapshots of chroots, sbuild may be used to build many packages in
 parallel.  A chroot envionment allows packages to be built in a
 controlled, clean environment.  sbuild installs only essential and
 build-essential packages, plus those in the package build
 dependencies.
(new) sbuild_0.62.5.orig.tar.gz extra devel
Changes: sbuild (0.62.5-1~bpo60+1) squeeze-backports; urgency=low
 .
  * Rebuild for squeeze-backports.
  * No source changes.
 .
sbuild (0.62.5-1) unstable; urgency=low
 .
  * New release.
  * sbuild:
    - Correct use of Dpkg::Version for version parsing, to ensure
      correct behaviour when using native package versions and epochs.
    - Don't require an exact version when building a package directly
      from a source tree.
 .
sbuild (0.62.4-1) unstable; urgency=low
 .
  * New release.
  * sbuild:
    - Failing lintian checks are highlighted in red, and passes in
      green (Closes: #631060).
    - The distribution in the build summary is coloured yellow if it
      does not match the distribution in the changelog.  This is to
      indicate that there may be a potential problem, such as
      potentially uploading a package intended for experimental to
      unstable by building for unstable by accident.
    - lintian test results are also coloured to highlight success and
      failure.
    - Log colouring may now be disabled using $log_colour.
    - sbuild only permits building one source package at once.
      Previously sbuild would allow building of more than one package
      in a single invocation.  Making this change means that the exit
      status will always be the status of the build rather than the
      last build, and it also means the logging is simplified and may
      be started earlier.
    - Now that the main log has been removed, and packing of a source
      tree takes place before starting the build for real, we no longer
      create a log file in the build tree, confusing "dpkg-source -b"
      (Closes: #612324).
    - Added new directory /var/lib/sbuild/build to hold build trees for
      sbuild when building.  This will be bind mounted on /build inside
      the chroot following an update to the schroot sbuild and buildd
      fstab configuration for schroot.  This saves significant amounts
      of space when using LVM snapshot chroots, and it also makes it
      easier to preserve build trees for failing builds when using
      snapshots.
    - Extra environment variables to be set when running
      dpkg-buildpackage may now be set using $build_environment
      (Closes: #631595).  These variables will supplement the existing
      environment (e.g. PATH, LD_LIBRARY_PATH), and will not be subject
      to filtering with $environment_filter.
    - Existing hard-coded .dsc/.changes/dpkg-parsechangelog parsing has
      been replaced with use of Dpkg::Control.  Existing reimplmentation
      of the dpkg version comparison and regexes to split versions into
      epoch/version/revision have been replaced with use of
      Dpkg::Version.
  * sbuild-adduser: Use current sbuild-update options in example
    (Closes: #630791).
 .
sbuild (0.62.3-1) unstable; urgency=low
 .
  * New release.
  * sbuild:
    - The apt and internal resolvers will resolve some alternatives
      even when resolving alternative dependencies is disabled
      (Closes: #622832).  For relations involving the same package,
      the alternative will be permitted when the package names are
      the same for each alternative.  For example,
        foo (<< x) | foo (>= y) | bar
      will be reduced to
        foo (<< x) | foo (>= y)
      while
        foo | bar
      will be reduced to
        foo
    - The sbuild-schroot wrapper program has been removed; sbuild is
      now an arch-all package again.
    - Move lock directory to /var/lib/sbuild/chroot-lock, rather than
      using /var/lock/sbuild which could be a symlink to /run/lock on
      the host (Closes: #626826).  This means parallel builds won't
      block due to sharing the same lockfile.
    - Remove schroot buildd profile.  This will now be provided by
      the schroot package itself directly.  This requires schroot
      1.4.22 or greater.
    - Add lintian and piuparts results to build summary
      (Closes: #617450).
    - Remove directory correctly in postrm (Closes: #627641).  Thanks
      to Daniel Baumann.
    - Lock sbuild account on purge, and unlock on install
      (Closes: #619892).
    - Add -j option to run parallel builds (Closes: #626357).
    - Log build environment prior to starting a build.  This will be
      useful in diagnosing problems with a misconfigured chroot, such
      as missing HOME which can lead to misbuilds.
  * sbuild-createchroot:
    - Don't call ChrootSetup::basesetup after initial bootstrap; wait
      until actually running sbuild.  The users and groups used for
      chown don't exist at this point, leading to (harmless) failure.
      Closes: #622735.
    - Don't overwrite existing symlinks under /etc/sbuild/chroot
      (Closes: #608416).
  * sbuild-update:
    - Don't try to end the current chroot session if a signal is
      received and no session is in progress (Closes: #629005).
  * buildd:
    - init script starts buildd in runlevels 2-5 rather than S, and
      stops in 0, 1 and 6.
    - Lock buildd account on purge, and unlock on install.
  * buildd-mail:
    - Remove empty newline from .changes (Closes: #627854).
      ftp-master started refusing .changes files which have a trailing
      empty line (after the GPG end of signature).  It happens that
      mutt introduces one when signing GPG in traditional mode.  Other
      tools probably do too.  buildd-mail-wrapper should probably drop
      it automatically.  Thanks to Samuel Thibault.
 .
sbuild (0.62.2-1) unstable; urgency=low
 .
  * New release.
  * sbuild:
    - New options --no-apt-clean, --no-apt-update, --no-apt-upgrade and
      --no-apt-distupgrade have been added to allow these actions to be
      disabled even when set as the default in the configuration.
    - root is not required to be a member of the sbuild group in order
      to run schroot via the sbuild-schroot wrapper
      (Closes: #619128, #619002).
    - Don't require HOME to be set in the environment (Closes: #619288).
    - Work around broken build-essential on Ubuntu Lucid
      (Closes: #619526).  Thanks to Marc Deslauriers.
    - --keep-session is replaced by
      --purge-session=(always|successful|never).  This will allow the
      session to be purged for all, successful and no builds,
      respectively (Closes: #619332).
    - sources.list fragments stored in /etc/apt/sources.list.d have
      0644 permissions, so that normal users can run apt-cache in the
      chroot during a build (Closes: #620797).  Thanks to Julian Andres
      Klode for identifying this problem.
    - Log filtering may be disabled using $log_filter = 0 in the
      configuration (Closes: #620589).  The replacement text is now
      also surrounded with "«" and "»" so that strings such as CHROOT
      and BUILDDIR can't be confused with any actual appearance of the
      same string in the build log.
    - Log colouring may be disabled using $log_colour = 0 in the
      configuration.
    - Improve binNMU handling to permit binNMUs for multiarch packages
      (Closes: #620112).  Currently, binary NMUs use the current date
      in the new changelog entry, but co-installable packages require
      an identical changelog.  To avoid this, take the date from the
      previous changelog entry to ensure the same date for all binNMUs.
      Thanks to Anders Kaseorg for this patch.
    - Abort early if maintainer is not defined when performing a binNMU
      or appending a version suffix (Closes: #620758).
  * sbuild.conf:
    - Don't set a default value for $build_dir (Closes: #619416).
      This value is set each run, and so varies between builds when
      generating the configuration file.  Exclude from the generated
      output to prevent unnecessary differences between builds.
    - $purge_session uses the same purge modes as $purge_build_deps and
      $purge_build_directory, rather than a boolean value.
  * buildd:
    - Merge latest changes from buildd-0.61.0.
 .
sbuild (0.62.1-1) unstable; urgency=high
 .
  * New release.
  * Fixed security issue in the sbuild-schroot wrapper program which
    did not enforce sbuild group membership in order to allow users
    to access the chroots as user sbuild.
 .
sbuild (0.62.0-1) unstable; urgency=low
 .
  * New release.
  * debian/control:
    - Build-Depend upon libexception-class-perl.
  * sbuild:
    - Resolvers:
      + 'apt' is now the default build dependency resolver.  Users should
        not see any significant changes compared with the old 'internal'
        resolver.  Please note that you may need to generate a GPG key
        for the local archive created for dependency package
        installation, if one does not already exist; see sbuild-update
        (--keygen) for further details.
      + The 'internal' build dependency resolver is deprecated.  It is
        not recommended for future use, and will be removed once it is no
        longer used by the buildd infrastructure.  Please use the 'apt'
        resolver as a drop-in replacement.
      + The 'aptitude' build dependency resolver will, unlike 'apt' and
        'internal', consider alternative dependencies by default, rather
        than only using the first alternative.  This is intended to both
        preserve backward compatibility, and make the 'aptitude'
        resolver the preferred choice for more complex situations, such
        as building for experimental.
      + The aptitude resolver can resolve complex dependencies, e.g.
        A | B, where A is uninstallable now correctly falls back to B.
        This is not the case for the internal or apt resolvers, which by
        intent do not make use of alternatives (they use the first
        alternative only.  sbuild now has full support for resolving
        alternatives, but this is not the default behaviour
        (Closes: #403246).  Please see #614807 for a proposed description
        of autobuilder-imposed build dependency restrictions in Policy.
      + All build dependency resolvers run dpkg with --force-confold.
        This means packages with modified conffiles in the chroot to not
        cause build failure.  This includes /etc/services and
        /etc/protocols from netbase (Closes: #576508).
    - Logging:
      + Long paths such as the chroot location and the build directory
        inside the chroot are now filtered in the build log and replaced
        with small, constant, abbreviations (Closes: #605763).  This makes
        the build logs comparable between builds with tools such as
        diff(1).
      + Logging messages have been improved, and important messages are
        now coloured when running interactively (does not affect log
        files).  Errors, warnings and informational messages are coloured
        red, yellow and green, respectively.  Build status is coloured
        green for success and red for all failure conditions.
      + Build log mails are now compressed and mailed in MIME format by
        default, together with a copy of the .changes file.  The old
        behaviour (plain mailing of uncompressed logs) may be restored by
        setting $mime_build_log_mails=0 in the configuration, and
        compression may also be disabled in the MIME mails by setting
        $compress_build_log_mails=0.  Note that it is no longer possible
        to send compressed log mails unless MIME mailing is enabled.
        Thanks to Philipp Kern for implementing this.
    - Error handling:
      + In order to handle errors more robustly, the build code now has
        initial support for exception handling.  Normal operation will
        not be affected, but fatal errors may be logged in a different
        order than seen previously.  Fatal errors will now be seen at the
        end of the build log, which should make it easier to spot
        problems.
      + sbuild now always cleans up fully when receiving a termination
        signal such as SIGINT or SIGTERM.  Note that you may need to wait
        while the cleanup actions are performed, or the current task is
        completed prior to initiating cleanup.  When running
        interactively, hitting Ctrl-C will sent SIGINT to the entire
        process group; doing this while apt-get or aptitude are running
        will potentially leave dpkg in an inconsistent state, so aborting
        at this point is not recommended.  Sending a SIGTERM to the
        sbuild process will always work cleanly.
    - General:
      + sbuild now performs an apt dist-upgrade at the start of each
        build by default, rather than an upgrade.  This is to reduce the
        amount of manual administration required to keep chroots up to
        date, and is not much more risky than upgrade in this context.
      + A new option, --keep-session, has been added (Closes: #609658).
        This prevents the automatic removal of session-managed snapshot
        chroots.  Previously, snapshots would not be deleted if purging
        of the build directory or build dependencies was disabled, but
        this was not always desirable, hence it is now configurable
        separately.
      + Internally, building and other actions in the chroot are
        performed by the 'sbuild' system user, where previously the user
        invoking sbuild would be used instead.  The aim of this change is
        to separate privileges to increase security and reduce the chance
        of accidental or deliberate tampering of the build environment.
        While the latter is not addressed by these changes, this will be
        taken care of during future architectural changes.
      + The sbuild package build directory created inside the chroot now
        has a reduced name length.  It's now /build/packagename-XXXXXX
        where XXXXXX are random characters.  This helps reduce the chance
        of hitting path length restrictions on some architectures,
        particularly when using sockets.
  * wanna-build:
    - The wanna-build database has been removed entirely.  This part of
      the sbuild package was not used, and was not maintained for some
      time.  Users wishing to use wanna-build should investigate the
      version in the wanna-build.git repository used by the Debian
      autobuilding infrastructure.  This version is actively maintained
      and in continual use.
  * sbuild.conf:
    - sbuild.conf is now automatically generated from the help text and
      defaults in the source code.  This means that the examples will
      always be syntactically correct, the help text will always be
      current, and the defaults will always match the defaults in the
      source code (Closes: #609932, #610995).
    - Non-scalar (or reference) types are deprecated in sbuild.conf.
      This is because it is not possible to tell the difference between
      an empty and an undefined value.  Values using array or hash
      types should use the equivalent array reference or hash
      reference, which have been supported for some time.  The old
      style array and hash values will remain supported for now, but
      will be removed in a future release.
  * buildd.conf:
    - Automatically generated like sbuild.conf.  As for sbuild.conf,
      non-scalar types are deprecated.
  * sbuild.conf.5:
    - All of the allowed values in sbuild.conf are now documented in a
      new sbuild.conf(5) manual page.  Like sbuild.conf, this is
      entirely generated from the source code, so will always match the
      defaults for the same sbuild version.
  * buildd.conf.5:
    - New manual page.  Like sbuild.conf(5), this documents all allowed
      values.
 .
sbuild (0.61.0-1) unstable; urgency=low
 .
  * sbuild:
    - The apt and aptitude build dependency resolvers now use only the
      first alternative in alternative dependencies.  The other
      alternatives are stripped out entirely.  This makes the apt and
      aptitude resolvers behave exactly like the internal resolver.
      Note that this is configurable with the $resolve_alternatives
      option, so alternative resolving may be re-enabled with this
      option if desired.  This is useful for e.g. backports, but not
      for unstable where the strict consistency and reproducibility
      offered by only using the first alternative is required.
    - The aptitude resolver now runs dpkg with --force-confold, to
      match the behaviour of internal and apt.  This prevents failure
      when installing netbase into the build chroot, for example.
 .
sbuild (0.60.9-1) unstable; urgency=low
 .
  * New release.
  * sbuild:
    - Don't automatically generate local archive signing key if
      missing (Closes: #607945).  If missing, abort build with an error
      message and instructions for how to generate the key.
    - Do not filter out environment variables starting with DEBIAN_ by
      default (Closes: #608659).  Thanks to Modestas Vainius.
    - Do not filter out PATH environment variable (Closes: #610997).
      Note this is not the user's PATH, but the $path in sbuild.conf.
    - Aptitude resolver defines a custom SolutionCost in order to
      improve resolver behaviour (Closes: #608789).  Thanks to
      Modestas Vainius.
    - When running apt-get, use "-o APT::Install-Recommends=false"
      rather than "--no-install-recommends" in order to support older
      releases (Closes: #609811).  Thanks to Marc Deslauriers.
    - Purging the package removes generated files in /etc/sbuild/chroot
      and /var/lib/sbuild (Closes: #608412).
    - The architecture specified with --arch (defaulting to the host
      system architecture) must match the chroot architecture
      (Closes: #609151).  This was previously allowed to be superceded
      by the chroot architecture.  This change is to avoid any abiguity
      regarding the host/build architecture for the package being built.
    - Add --no-arch-all option to force not building arch-all packages
      (Closes: #613401).  Thanks to Sebastian Harl for this patch.
  * sbuild-createchroot:
    - Use less restrictive permissions on chroot directory and schroot
      configuration file (Closes: #608414).  The chroot now has 0755
      permissions, and the schroot configuration 0644.
    - Don't require sudo access (Closes: #608429).  The
      Sbuild::ChrootPlain module used to run commands inside the newly-
      created chroot was using sudo to run commands when already
      running as root.  sudo is no longer used when root.
    - Remove use statement which prevented command-line options being
      registered (Closes: #610007, #607606).  Command-line options now
      work correctly.
  * sbuild.conf:
    - $environment filter is syntactically correct (Closes: #610997).
      Thanks to Jakub Wilk.
    - $apt_allow_unauthenticated is documented to use apt-secure(8)
      (Closes: #608971).
  * sbuild.1:
    - Document the temporary local archive used by the apt and aptitude
      build dependency resolvers to store and install dummy dependency
      packages (Closes: #608972).
 .
sbuild (0.60.8-1) unstable; urgency=low
 .
  * New release.
  * sbuild:
    - Don't use user's default GPG configuration and keyrings for
      signing archives; use sbuild archive signing keys only
      (Closes: #606668).  Thanks to Simon McVittie for this patch.
    - Use an empty directory as GPG homedir.
    - Don't run "apt-get update" to update local archive; copy files
      directly into /var/lib/apt/lists.  This means the remote mirror
      lists can't be updated during a build, and it also saves the
      time needed to update the lists an additional two times.
 .
sbuild (0.60.7-1) unstable; urgency=low
 .
  * New release.
  * Correct building of dependency package using the apt and aptitude
    resolver, where /tmp is not shared with the host (Closes: #606278).
 .
sbuild (0.60.6-1) unstable; urgency=low
 .
  [ Roger Leigh ]
  * New release.
  * sbuild:
    - sbuild now sanitises its environment when running external
      commands.
    - sbuild no longer generates the files REDO and SBUILD-REDO-DUMPED.
    - sbuild now has a testsuite.
    - apt and aptitude build-dependency resolvers now use a local apt
      archive, which improves the behaviour of the apt resolver (the
      dependency package will no longer be removed in some situations).
    - Workaround uninstallable sysvinit on Ubuntu, where sysvinit is
      still present in the build-essential package list.  Thanks to
      Jamie Strandboge.
  * sbuild-update:
    - sbuild-update works on multiple chroots (Closes: #604715).
    - sbuild-update works with multiple architectures (Closes: #606001).
      Thanks to Ansgar Burchardt for this patch.
    - sbuild-update now has a --keygen option to generate signing keys
      for temporary apt archives.
  * sbuild.1: Update description of --maintainer (Closes: #605745).
    Thanks to Jakub Wilk.
  * Sbuild::ConfBase: Only use MAILTO_HASH if defined (Closes: #589615).
    Thanks to Marc Dequènes for this patch.
 .
  [ Modestas Vainius ]
  * sbuild:
    - Do not skip purging of build directory if chroot is cloned
      (Closes: #605997).  This is necessary if /build in chroots is
      (bind-)mounted to the outside of the session.  However, if /build
      is part of the cloned session, $purge_build_directory='never'
      could be used in order to avoid wasting time when the session
      ends.
 .
sbuild (0.60.5-1) unstable; urgency=low
 .
  * Chroot upgrade and dist-upgrade commands run with
    "dpkg --force-confold" as done for build dependency installation
    (Closes: #603397).  Thanks to Loïc Minier.
 .
sbuild (0.60.4-1) unstable; urgency=low
 .
  * New release.
  * Allow the user to specify chroot namespaces in the distribution
    name (Closes: #602789).
  * Revert default build dependency resolver to 'internal' for the
    time being.
 .
sbuild (0.60.3-1) unstable; urgency=low
 .
  * New release.
  * sbuild-createchroot:
    - Allow direct creation of tarballs from chroots, with various
      options for compression (Closes: #545215).  Thanks to Andres
      Mejia.
  * sbuild-update:
    - sbuild-clean functionality has been merged into sbuild-update.
      Thanks to Andres Mejia.
  * sbuild:
    - Dependency resolving:
      . 'aptitude' is now the default dependency resolver.  Users
        wishing to use the old resolver should set
        $build_dep_resolver='internal' in their configuration.
      . The aptitude resolver can resolve complex dependencies.
        A | B, where A is uninstallable now correctly falls back to B
        (Closes: #403246).
      . Removal of Build-Conflicts now works, due to using apt-get
        or aptitude to perform the removal (Closes: #464376).
      . Default to not enabling virtual dependency resolving with the
        internal resolver ($resolve_virtual=0).  This is to avoid
        changing the historical behaviour by default.
    - Don't set Sbuild::debug_level to undef (Closes: #602318).
      Thanks to Andres Mejia.
    - Add debuild-like feature to run sbuild on an unpacked source
      tree (Closes: #551311).  In addition to specifying a package
      version to build, or a source package .dsc, a directory may be
      used.  This will be packaged with 'dpkg-source -b' prior to
      building.  Thanks to Andres Mejia.
    - Add support for running lintian after a build.  Thanks to Andres
      Mejia.
    - Add support for running external commands before and after a
      build, and during chroot setup and cleanup.  These may be used
      to run piuparts, for example.  Thanks to Andres Mejia.
  * Run sbuild-* chroot maintenance commands in the 'source' chroot
    namespace for chroots providing such a facility (Closes: #567505).
    This means that update/distupgrade etc. operations will occur in
    the source volume for lvm-snapshot and btrfs-snapshot chroot types.
    Note that the sbuild chroot lock (/var/lock/sbuild) may be copied
    into cloned chroots if a build is started during a maintenance
    operation and the build will block until the operation is completed.
 .
sbuild (0.60.2-1) unstable; urgency=low
 .
  * New release.
  * sbuild:
    - Dependency resolving:
      . The aptitude build dependency resolver now sets
        Aptitude::CmdLine::Ignore-Trust-Violations based upon the
        $apt_allow_unauthenticated option (Closes: #588035).  Thanks to
        Ansgar Burchardt for this patch.
      . Improve handling of alternative build dependencies and Provides
        using the interal build dependency resolver.  (Closes: #586275,
        #578810, #591187, #591188, #591189, #595863, #595866, #595872).
        Thanks to Ansgar Burchardt for this patch.
      . Remove virtual build-dependency resolving using the "internal"
        resolver using the static ALTERATIVES (%alternatives) list.  This
        was already limited, non-functional, and is obsoleted by the
        "aptitude" resolver.
      . Added the ability to resolve virtual dependencies using the
        "internal" build dependency resolver by calling "apt-cache
        --names-only" to get candidate packages to satisfy the
        dependency.  The first package (sorted alphabetically) is
        chosen (Closes: #595934).  This may be disabled using the
        $resolve_virtual option.
      . Use apt-get to remove build conflicts using the internal
        resolver and correctly reinstall post build.
    - Log the package source version as well as binary version in the
      package build log, since these may differ when making binNMUs
      (Closes: #569823).
    - Always attempt to install ESSENTIAL (build-essential) packages
      if they aren't already installed (Closes: #380113).
    - Don't end session on build failure (Closes: #567506).  This allows
      examination of build trees and cloned chroots on build failure,
      rather than unconditionally deleting them, which prevents this.
      Thanks to Jan-Marek Glogowski.
    - Remove support for parsing output of apt-get stderr
      (Closes: #571806).
    - Check for sbuild group membership using gid and supplementary
      groups (Closes: #599350).
  * buildd:
    - Read entire contents of pipes (Closes: #567821).  Thanks to
      Samuel Thibault.  This ensures receipt of complete log
      messages.
    - Replace/Breaks with ubuntu-dev-tools <= 0.83 (Closes: #590153).
      Thanks to Lorenzo De Liso.
  * buildd-vlog: Fix breakage (Closes: #567822).  Thanks to
    Samuel Thibault.  This fix introduces sleeps, and is not a
    complete or entirely optimal fix, but corrects the existing
    breakage.
  * Documentation:
    - Remove trailing 'q' from sbuild-createchroot(8) manual page
      (Closes: #579971).  Thanks to Salvatore Bonaccorso.
    - sbuild(1):
      . Remove and rewrite obsolete parts of the manpage
        (Closes: #599348).
      . .sbuildrc is no longer required for sbuild to function
        (Closes: #598054).
 .
sbuild (0.60.1-1) unstable; urgency=low
 .
  * New release.
  * debian/control:
    - Upgrade to Standards-Version 3.9.1.
  * sbuild:
    - Add --no-source option (Closes: #571726).  Thanks to David
      Bremner for this suggestion.
    - Hint aptitude to produce better solutions in AptitudeBuildDepSatisfier.
      Thanks to Modestas Vainius.  (Closes: #570463)
    - AptitudeBuildDepSatisfier: Handle the case when default negative dep is
      not available gracefully.  Thanks to Modestas Vainius.
      (Closes: #571565).
    - Improve support for aptitude.
    - Set DEBIAN_FRONTEND=noninteractive when using aptitude
      (Closes: #588818).
    - Improve dpkg-source v3 source format handling.  Don't hard-code
      assumptions about how the source files are named
      (Closes: #559533).
    - Remove conflict with schroot from oldstable.
  * buildd:
    - Retry the current suite if --take fails.  (Closes: #570463)
  * buildd-uploader:
    - Don't remove the uploader lock if not already the owner
      Closes: #591620).  Thanks to Sebastian Andrzej Siewior.
  * libsbuild-perl:
    - depend on schroot 1.4.0 or greater due to sbuild-createchroot
      creating schroot.conf fragments with 1.4.x-specific features.


Override entries for your package:

Announcing to debian-backports-changes@lists.debian.org


Your package contains new components which requires manual editing of
the override file.  It is ok otherwise, so please be patient.  New
packages are usually added to the override file about once a week.

You may have gotten the distribution wrong.  You'll get warnings above
if files already exist in other distributions.
s already exist in other distributions.


Reply to: