On Sat, Aug 28, 2010 at 17:34:37 +0200, Stefan Fritsch wrote:
Package: slapd
Version: 2.4.23-4
Severity: grave
When upgrading from 2.4.23-2 to 2.4.23-4, I get a debconf message that
tells me that slapcat failed during upgrade. dpkg then aborts with a
failure.
Also, contrary to the
On Sep 3, 2010, at 3:09 PM, Julien Cristau wrote:
On Sat, Aug 28, 2010 at 17:34:37 +0200, Stefan Fritsch wrote:
Package: slapd
Version: 2.4.23-4
Severity: grave
When upgrading from 2.4.23-2 to 2.4.23-4, I get a debconf message that
tells me that slapcat failed during upgrade. dpkg then
severity 594711 important
retitle 594711 slapd: Migration of DB format fails during upgrade from
2.4.23-[123]
kthxbye
On Fri, Sep 3, 2010 at 15:14:51 +0200, Matthijs Mohlmann wrote:
On Sep 3, 2010, at 3:09 PM, Julien Cristau wrote:
On Sat, Aug 28, 2010 at 17:34:37 +0200, Stefan Fritsch
On Fri, Sep 03, 2010 at 03:25:13PM +0200, Julien Cristau wrote:
Then I don't think this should be RC. Downgrading to important, leaving
it to the maintainers to close or handle as they wish.
Right, and I don't know of a good way to handle this. We certainly don't
want to go back and re-upload
severity 594711 wishlist
retitle 594711 document how to do db format upgrade manually
thanks
On Friday 03 September 2010, Steve Langasek wrote:
On Fri, Sep 03, 2010 at 03:25:13PM +0200, Julien Cristau wrote:
Then I don't think this should be RC. Downgrading to important,
leaving it to the
On Fri, Sep 03, 2010 at 09:12:01PM +0200, Stefan Fritsch wrote:
On Friday 03 September 2010, Steve Langasek wrote:
On Fri, Sep 03, 2010 at 03:25:13PM +0200, Julien Cristau wrote:
Then I don't think this should be RC. Downgrading to important,
leaving it to the maintainers to close or
Package: slapd
Version: 2.4.23-4
Severity: grave
When upgrading from 2.4.23-2 to 2.4.23-4, I get a debconf message that
tells me that slapcat failed during upgrade. dpkg then aborts with a
failure.
Also, contrary to the debconf message, the database files are not moved
into /var/backup.
I am
7 matches
Mail list logo
