[Bug 1498371] Re: Sync dbconfig-common 1.8.53 (main) from Debian unstable (main)

[Paul Gevers]

Hi

On 23-09-15 21:07, Graham Inggs wrote:
> If the fix is known, upload it to Debian first.  From there we can try
> to sync again or upload a new Ubuntu version.

I decided to not fix more than just this issue. In the mean time I even
received a patch from Martin Pitt.

Once the package is accepted and shows up, I guess I have to request
another sync right?

Paul

-- 
You received this bug notification because you are a member of Ubuntu
Sponsors Team, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1498371

Title:
  Sync dbconfig-common 1.8.53 (main) from Debian unstable (main)

Status in dbconfig-common package in Ubuntu:
  Fix Released

Bug description:
  Please sync dbconfig-common 1.8.53 (main) from Debian unstable (main)
  Fixes a regression introduce in 1.8.49 (see  #793816).

  Changelog entries since current wily version 1.8.52:

  dbconfig-common (1.8.53) unstable; urgency=medium

    * Add Breaks: bandwidthd-pgsql (<< 2.0.1+cvs20090917-9~)
      (Closes: #791622)
    * Rename install_examples.sh and add it to autopkgtest list
    * Add extended regression tests to autopkgtest list
    * Extend error message upon script error (Closes: #506510)
    * Fix preseeding by package (Closes: #793816)
    * Allow noninteractive remove mode to fail (Closes: #793599)
    * Update documentation with a note that packages depending on
      dbconfig-common are recommended to depend on the command line
      client required for the database they support. The solution to
      fix this (bug 353617) is quite involved, so it needs some proper
      preparation.
    * Bump debhelper compat level to 9
    * Remove convenience targets in d/rules (adt-run does a better job)

   -- Paul Gevers <elbrus at debian.org>  Mon, 21 Sep 2015 20:35:32 +0200

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dbconfig-common/+bug/1498371/+subscriptions