Sure, I'll do that.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to dbconfig-common in Ubuntu.
https://bugs.launchpad.net/bugs/1498371
Title:
Sync dbconfig-common 1.8.53 (main) from Debian unstable (main)
To manage notifications
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
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
--
You received
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
If the fix is known, upload it to Debian first. From there we can try
to sync again or upload a new Ubuntu version.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to dbconfig-common in Ubuntu.
https://bugs.launchpad.net/bugs/1498371
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
> 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
--
You received this bug notification because you are a
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
