Your message dated Sat, 09 Nov 2013 10:54:30 +1100
with message-id <1707596.a1fev5LIud@acer>
and subject line Re: Bug#674186: [digikam] external mysql db empty after
database migration
has caused the Debian Bug report #674186,
regarding [digikam] external mysql db empty after database migration
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 [email protected]
immediately.)
--
674186: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=674186
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: digikam
Version: 4:2.6.0~rc-3
Severity: grave
Hi,
I am using Digikam from testing, with an external MySQL database. The last
upgrade has been a total mess :
the migration of the database has failed, and my db was totally empty after
that. Fortunately I had a backup.
I tried to migrate again with the wizard, but it failed the same way. Finally I
found a solution : create a second database « digikam2 » (and « digikam_thumb2
» ), and run the wizard to migrate from digikam to digikam2. I recover my
pictures, but the tags (stored in nepomuk) disappears… Haven't find any
solution to recover them… :((
It seems to have a bug in the db migration, which delete all the data to
migrate. Maybe when constructing the new schema ? Anyway, this behaviour should
be corrected.
Cheers,
Adrien
--- System information. ---
Architecture: amd64
Kernel: Linux 3.2.0-2-amd64
Debian Release: wheezy/sid
900 testing security.debian.org
900 testing ftp.fr.debian.org
800 unstable ftp.fr.debian.org
700 experimental ftp.fr.debian.org
--- Package information. ---
Depends (Version) | Installed
================================================-+-======================
kde-runtime | 4:4.7.4-2+b1
libc6 (>= 2.4) | 2.13-32
libgcc1 (>= 1:4.1.1) | 1:4.7.0-8
libgomp1 (>= 4.2.1) | 4.7.0-8
libgphoto2-2 (>= 2.4.10.1) | 2.4.14-2
libgphoto2-port0 (>= 2.4.10.1) | 2.4.14-2
libjasper1 | 1.900.1-13
libjpeg8 (>= 8c) | 8d-1
libkdcraw20 (>= 4:4.7.1) | 4:4.7.4-2
libkdecore5 (>= 4:4.7.0) | 4:4.7.4-4
libkdeui5 (>= 4:4.7) | 4:4.7.4-4
libkdewebkit5 (>= 4:4.7) | 4:4.7.4-4
libkexiv2-10 (>= 4:4.7.1) | 4:4.7.4-2+b1
libkfile4 (>= 4:4.7) | 4:4.7.4-4
libkhtml5 (>= 4:4.7) | 4:4.7.4-4
libkio5 (>= 4:4.7.0) | 4:4.7.4-4
libkipi8 (>= 4:4.5.90) | 4:4.7.4-2
libknotifyconfig4 (>= 4:4.7) | 4:4.7.4-4
libkparts4 (>= 4:4.7) | 4:4.7.4-4
liblcms1 (>= 1.15-1) | 1.19.dfsg-1+b2
liblensfun0 | 0.2.5-2
liblqr-1-0 (>= 0.4.0) | 0.4.1-1.1
libmarblewidget12 (>= 4:4.7.1) | 4:4.7.4-2
libnepomuk4 (>= 4:4.7) | 4:4.7.4-4
libopencv-core2.3 | 2.3.1-8
libopencv-highgui2.3 | 2.3.1-8
libopencv-imgproc2.3 | 2.3.1-8
libopencv-legacy2.3 | 2.3.1-8
libopencv-objdetect2.3 | 2.3.1-8
libphonon4 (>= 4:4.2.0) | 4:4.6.0.0-2
libpng12-0 (>= 1.2.13-4) | 1.2.49-1
libqjson0 (>= 0.7.1) | 0.7.1-6
libqt4-dbus (>= 4:4.5.3) | 4:4.8.1-1
libqt4-network (>= 4:4.5.3) | 4:4.8.1-1
libqt4-qt3support (>= 4:4.5.3) | 4:4.8.1-1
libqt4-sql (>= 4:4.5.3) | 4:4.8.1-1
libqt4-xml (>= 4:4.5.3) | 4:4.8.1-1
libqtcore4 (>= 4:4.8.0) | 4:4.8.1-1
libqtgui4 (>= 4:4.8.0) | 4:4.8.1-1
libqtwebkit4 (>= 2.1.0~2011week13) | 2.2.1-4+b1
libsolid4 (>= 4:4.7) | 4:4.7.4-4
libsoprano4 (>= 2.1.67) | 2.7.5+dfsg.1-1
libstdc++6 (>= 4.6) | 4.7.0-8
libtiff4 (>> 3.9.5-3~) | 3.9.6-5
libx11-6 | 2:1.4.99.901-2
phonon | 4:4.6.0.0-2
libqt4-sql-sqlite | 4:4.8.1-1
digikam-data (= 4:2.6.0~rc-3) | 4:2.6.0~rc-3
Recommends (Version) | Installed
============================-+-===========
www-browser |
kipi-plugins | 4:2.6.0~rc-3
mplayerthumbs |
Suggests (Version) | Installed
==========================-+-===========
digikam-doc |
--- End Message ---
--- Begin Message ---
On Wed, 23 May 2012 19:03:03 Adrien wrote:
> Version: 4:2.6.0~rc-3
Adrien,
I have closed this report as it is against a very old version of digikam which
is no longer supported by Debian.
I am sorry we have not been able to resolve this issue for you.
Upstream also provide support for digikam here: http://www.digikam.org/support
If this is an ongoing issue, could I ask you to file a new report against a
newer version of digikam which is supported by Debian.
I see you have had some success with upstream:
https://bugs.kde.org/show_bug.cgi?id=301075
Mark
signature.asc
Description: This is a digitally signed message part.
--- End Message ---
