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

[Graham Inggs]

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 <email address hidden> Mon, 21 Sep 2015 20:35:32 +0200

[Robie Basak (racb)]

This bug was fixed in the package dbconfig-common - 1.8.53
Sponsored for Graham Inggs (ginggs)

---------------
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 <email address hidden> Mon, 21 Sep 2015 20:35:32 +0200

[Paul Gevers (paul-climbing)]

Hi Graham and Robie

On 22-09-15 12:15, Robie Basak wrote:
> This bug was fixed in the package dbconfig-common - 1.8.53
> Sponsored for Graham Inggs (ginggs)

> * Add extended regression tests to autopkgtest list

It seems dbconfig-common is now hold back because of this new test
failing. I just confirmed in a clean chroot that this is due to a
missing dependency in the control file for that test on fakeroot. What
is the smartest way forward? That I upload a new version to Debian that
fixes that, or that we fix it for now in Ubuntu?

Or are we too late anyways? I really think we should at least get the
fix for Debian bug #793816 in Ubuntu, as that is a regression.

Paul

[Graham Inggs (ginggs)]

If the fix is known, upload it to Debian first. From there we can try to sync again or upload a new Ubuntu version.

[Paul Gevers (paul-climbing)]

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 believe I know the fix. However, if I can do that for Debian I like to
also get the second autopkgtest to run as intended (after the upload I
found stashed changes that I thought I committed long time ago, now the
first test just runs twice). I was wondering how much time is still
left. One day, couple of days, two weeks? I am unsure for a package in main.

Paul

[Graham Inggs (ginggs)]

> I was wondering how much time is still left.
> One day, couple of days, two weeks? I am unsure for a package in main.

Technically, we have until FinalFreeze [1], October 15.

[1] https://wiki.ubuntu.com/WilyWerewolf/ReleaseSchedule

[Paul Gevers (paul-climbing)]

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

[Paul Gevers (paul-climbing)]

On 25-09-15 12:26, Paul Gevers wrote:
> Once the package is accepted and shows up, I guess I have to request
> another sync right?

It now did, but I can't get requestsync to work on my system right now
(it used to work in the past). Graham, can you request the syn again?

Paul

[Graham Inggs (ginggs)]

Sure, I'll do that.