[Digikam-devel] Bug#506564: marked as done (Fails to update digikam3 database to digikam4 (db format 4 to 5))

[Debian Bug Tracking System]

Your message dated Thu, 29 Jan 2009 13:32:12 +0000
with message-id <E1LSX08-0000ik-Uo at ries.debian.org>
and subject line Bug#506564: fixed in digikam 2:0.10.0~rc1-1
has caused the Debian Bug report #506564,
regarding Fails to update digikam3 database to digikam4 (db format 4 to 5)
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner at bugs.debian.org
immediately.)


-- 
506564: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=506564
Debian Bug Tracking System
Contact owner at bugs.debian.org with problems
-------------- next part --------------
An embedded message was scrubbed...
From: Johannes Graumann <johannes_graumann at web.de>
Subject: Fails to update digikam3 database to digikam4 (db format 4 to 5)
Date: Sat, 22 Nov 2008 17:50:28 +0100
Size: 9995
URL: <http://mail.kde.org/pipermail/digikam-devel/attachments/20090129/2a2a11c9/attachment.mht>
-------------- next part --------------
An embedded message was scrubbed...
From: Mark Purcell <msp at debian.org>
Subject: Bug#506564: fixed in digikam 2:0.10.0~rc1-1
Date: Thu, 29 Jan 2009 13:32:12 +0000
Size: 6206
URL: <http://mail.kde.org/pipermail/digikam-devel/attachments/20090129/2a2a11c9/attachment-0001.mht>