Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 382617 - media-gfx/digikam-2.1.0-r1 blockers preventing world update
Summary: media-gfx/digikam-2.1.0-r1 blockers preventing world update
Status: RESOLVED FIXED
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: [OLD] KDE (show other bugs)
Hardware: All Linux
: Normal normal (vote)
Assignee: Andreas K. Hüttel
URL: https://bugs.kde.org/show_bug.cgi?id=...
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-09-11 18:15 UTC by Andreas K. Hüttel
Modified: 2011-09-24 22:28 UTC (History)
4 users (show)

See Also:
Package list:
Runtime testing required: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Andreas K. Hüttel archtester gentoo-dev 2011-09-11 18:15:03 UTC
Known problem and last-minute emergency measure. See URL for more information.

If you have <=digikam-2.0.0-r1, DO NOT UPGRADE to digikam-2.1.0-r1 for now.

If you already have digikam-2.1.0-r1, DO NOT DOWNGRADE to digikam-2.0.0-r1 or earlier.

Either action may damage your image database.
Comment 1 Andreas K. Hüttel archtester gentoo-dev 2011-09-11 19:00:58 UTC
Update:

* You can safely update from <=digikam-2.0.0-r1 to digikam-2.1.0-r2 <<<

* If you have already installed and *started* digikam-2.1.0-r1, please do not upgrade or downgrade at the moment. We will have to wait for a resolution from upstream.
Comment 2 bartoz 2011-09-11 20:46:04 UTC
2.1.0-r2 does not compile here..

I paste the relevant part of the log below:

-- <<< Gentoo configuration >>>
Build type      Gentoo
Install path    /usr
Compiler flags:
C               -march=native -O2 -pipe  -Wno-long-long -std=iso9899:1990 -Wundef -Wcast-align -Werror-implicit-function-declaration -Wchar-subscripts -Wall -W -Wpointer-arith -Wwrite-strings -Wformat-security -Wmissing-format-attribute -fno-common
C++             -march=native -O2 -pipe  -Wnon-virtual-dtor -Wno-long-long -ansi -Wundef -Wcast-align -Wchar-subscripts -Wall -W -Wpointer-arith -Wformat-security -fno-exceptions -DQT_NO_EXCEPTIONS -fno-check-new -fno-common -Woverloaded-virtual -fno-threadsafe-statics -fvisibility=hidden -Werror=return-type -fvisibility-inlines-hidden
Linker flags:
Executable      -Wl,--enable-new-dtags  -Wl,-O1 -Wl,--as-needed
Module          -Wl,--enable-new-dtags -Wl,--fatal-warnings -Wl,--no-undefined -lc  -Wl,-O1 -Wl,--as-needed
Shared          -Wl,--enable-new-dtags -Wl,--fatal-warnings -Wl,--no-undefined -lc  -Wl,-O1 -Wl,--as-needed

-- Configuring incomplete, errors occurred!
 * ERROR: media-gfx/digikam-2.1.0-r2 failed (configure phase):
Comment 3 Andreas K. Hüttel archtester gentoo-dev 2011-09-11 20:50:03 UTC
(In reply to comment #2)
> 2.1.0-r2 does not compile here..
> 
> I paste the relevant part of the log below:
> 

Not enough, sorry... please make a new bug and attach emerge --info and the full log.
Comment 4 bartoz 2011-09-11 20:55:35 UTC
(In reply to comment #3)
> (In reply to comment #2)
> > 2.1.0-r2 does not compile here..
> > 
> > I paste the relevant part of the log below:
> > 
> 
> Not enough, sorry... please make a new bug and attach emerge --info and the
> full log.

I will do so..
It is strange though: I compiled 2.1.0-r1 and it emerged all right.
Comment 5 bartoz 2011-09-11 21:20:36 UTC
Never mind, I tracked the issue..
A little higher, in the build log, I had:

--  MySQL install_db tool found.............. NO
-- 
--  digiKam needs MySQL install_db tool. You need to install the package containing the "mysql_install_db" executable.
--  If you have this executable installed, please specify the folder containing it by MYSQL_TOOLS_PATH
CMake Error at CMakeLists.txt:129 (MESSAGE):
Call Stack (most recent call first):
  CMakeLists.txt:339 (PRINT_EXECUTABLE_STATUS)

I manually did an

export MYSQL_TOOLS_PATH=/usr/share/mysql/scripts/

and digikam is emerging properly. I do not know if this is an issue only for me or if there is some problem with the ebuild; I thought to share this fix in case it can help someone else.

Sorry for polluting this bug.

davide
Comment 6 Andreas K. Hüttel archtester gentoo-dev 2011-09-12 22:33:30 UTC
If you have digikam-2.1.0-r1 installed and cannot upgrade at the moment, please read the instructions at this address (comments 27 - 30 at least):

https://bugs.kde.org/show_bug.cgi?id=281767#c27

This tells you how to safely get from -r1 to -r2. Francesco is the digikam developer working on the database backend, so he knows the details best.

I'll keep this bug open for another two weeks or so to make sure that everyone has upgraded, and then close the bug and remove -r1 from the tree.
Comment 7 Jim Dory 2011-09-13 03:25:15 UTC
I've emerged the digikam-2.1.0-r1. I did not try to run it before seeing that there was an -r2. So I emerged that, having to uninstall the previous because of the blocker. Today I tried to run it and get and error:

"7f1916ad0000-7f1916cd0000 ---p 0003e000 08:03 5652212                    /usr/lib64/kde4/kipiplugin_printimages.soKCrash: Application 'digikam' crashing...
KCrash: Attempting to start /usr/lib64/kde4/libexec/drkonqi from kdeinit
sock_file=/home/jim/.kde4/socket-jamd/kdeinit4__0
QSocketNotifier: Invalid socket 18 and type 'Read', disabling...
"

I come here and read that my database may possibly now be hurting (corrupted?)? I checked the link from Andreas and they say about a mysqldump but I must be using another database - the sqlite one perhaps as I don't have mysql running and it complains about its config file if I try to start it.

"/etc/init.d/mysql start 
 * Starting mysql ...
 * MySQL datadir `/var/lib/mysql' is empty or invalid
 * Please check your config file `/etc/mysql/my.cnf'
 * ERROR: mysql failed to start
"

The digikamrc file contains:

"[Database Settings]
Database Connectoptions=
Database Hostname=
Database Name=/home/jim/Media/images/
Database Name Thumbnails=/home/jim/Media/images/
Database Password=
Database Port=-1
Database Type=QSQLITE
Database Username=
Internal Database Server=false
"
so not sure how to proceed using advice on that link. I suppose I could create an account there and reply.. but maybe there is answers forthcoming here.
Comment 8 Jan Essert 2011-09-16 11:33:06 UTC
The instructions in the link that is provided unfortunately only apply to mysql databases.
Could you please also explain the procedure for SQlite databases?
Or is there no problem in this case?
Comment 9 Francesco Riosa 2011-09-19 09:17:34 UTC
(In reply to comment #8)
> The instructions in the link that is provided unfortunately only apply to mysql
> databases.
> Could you please also explain the procedure for SQlite databases?
> Or is there no problem in this case?

For sqlite the procedure could be this:

1st) to be on the safe side, copy the digikam4.db thumbnails-digikam.db files (thumbnails-digikam.db can easily be recreated but on a large collection it take some time)

2nd) edit ~/.kde4/share/config/digikamrc, the section [Database Settings]
should contain only the following:
[Database Settings]
Database Connectoptions=
Database Hostname=
Database Name=/a/path/to/dir
Database Name Thumbnails=/a/path/to/dir
Database Password=
Database Port=0
Database Type=QSQLITE
Database Username=
Internal Database Server=false

no Image* or Thumbnails*, if these are present remove them
also check that values in there are correct.

3rd) N/A

4th) emerge -C =digikam-2.1.0-r1 && emerge -a '>=digikam-2.1.1'

Step 2) is not immediately needed but leaving the cruft there can create problems if and when we switch to this schema of config options.
Comment 10 Andreas K. Hüttel archtester gentoo-dev 2011-09-24 22:28:23 UTC
Let's assume everyone has upgraded by now. -r1 is gone from the tree.