Digikam 2.1.0, same DB problem as in 2.0

[tosca]

I had to use the '--nodeps' option for the following libraries:
kdeedu-marble-libs
libksane
libkipi
libkdcraw
libkexiv2
as rpm refuse to uninstall them otherwise, and they causes conflicts
when I try to do 'yum install digikam kipi-plugins'

Marie-Noëlle



2011/8/25 Martin (KDE) <[hidden email]>:

> Am Donnerstag, 25. August 2011 schrieb Marie-Noëlle Augendre:
>> OK, I'm back to 1.9.0 now.
>> I just had to remove the conflicting libraries by 'rpm -e
>> library-name' (with the --nodeps option for some of them) before
>> doing a proper 'yum install'.
>> I've updated accordingly both french and english procedures I'm
>> maintaining on my wiki:
>> http://www.webmaster-en-herbe.net/wiki/doku.php?id=wiki:configurati
>> on-2:digikam
>> http://www.webmaster-en-herbe.net/wiki/doku.php?id=wiki:configurat
>> ion-2:digikam-en
>
> Hm, removing packages with --nodeps should not be necessary. It is
> usually not a good idea to do so - except for reinstalling a basic
> component.
>
> For most kde stuff you can uninstall the package and a later started
> 'yum install' should bring all back.
>
> Do you know which packages you have to erase with --nodeps?
>
> Regards
>
> Martin
>
>>
>> Regarding the persistent bug I had with both versions 2.0.0 and
>> 2.1.0 versions, I would very much like to know where it is being
>> monitored as I understand taht this one is closed:
>> https://bugs.kde.org/show_bug.cgi?id=268267
>>
>> Marie-Noëlle
>>
> _______________________________________________
> Digikam-users mailing list
> [hidden email]
> https://mail.kde.org/mailman/listinfo/digikam-users
>

--
Une galerie photos, un blog ... pourquoi pas ? Webmaster en herbe

Parcourez les Cévennes à ma façon : Cévennes Plurielles

Et toutes mes autres publications à partir de ma page d'accueil générale
_______________________________________________
Digikam-users mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-users

Le 25/08/2011 21:16, Marie-Noëlle Augendre a écrit :
> Do you mean it is possible to launch it (for testing) without doing
> the 'make install'? And the previous version remains the one by
> default?

alas no, it don't work. launching "digikam" from the compiled
folder... simply run the old installed version if any :-(

jdd
>


--
http://www.dodin.net
http://www.youtube.com/user/jdddodinorg
http://jdd.blip.tv/
_______________________________________________
Digikam-users mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-users

[tosca]

I might have missed something ... Why do the compilation if it is not
to launch the program?
In my case, I would have like to use the 2.1.0 version; it's only
because it corrupts my DB all the time that I had to downgrade to the
1.9.0 version.

Marie-Noëlle

2011/8/25 jdd <[hidden email]>:

> Le 25/08/2011 21:16, Marie-Noëlle Augendre a écrit :
>>
>> Do you mean it is possible to launch it (for testing) without doing
>> the 'make install'? And the previous version remains the one by
>> default?
>
> alas no, it don't work. launching "digikam" from the compiled folder...
> simply run the old installed version if any :-(
>
> jdd
>>

--
Une galerie photos, un blog ... pourquoi pas ? Webmaster en herbe

Parcourez les Cévennes à ma façon : Cévennes Plurielles

Et toutes mes autres publications à partir de ma page d'accueil générale
_______________________________________________
Digikam-users mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-users

[Martin (KDE)]

Am 25.08.2011 22:17, schrieb Marie-Noëlle Augendre:
> I had to use the '--nodeps' option for the following libraries:
> kdeedu-marble-libs

with this you should have tried yum remove and all dependencies should
be removed as well.

> libksane
> libkipi
> libkdcraw
> libkexiv2

This packages got seperated from kdegraphics during upgrade from kde 4.6
to 4.7. So an install of digikam 1.9 should bring kdegraphics 4.6.5 as
dependency (containing the named libs).

> as rpm refuse to uninstall them otherwise, and they causes conflicts
> when I try to do 'yum install digikam kipi-plugins'

It is always a good idea to remove packages with 'yum remove' instead of
'rpm -e' as yum takes care of dependencies.

Regards

Martin

>
> Marie-Noëlle
>
>
>
> 2011/8/25 Martin (KDE) <[hidden email]>:
>> Am Donnerstag, 25. August 2011 schrieb Marie-Noëlle Augendre:
>>> OK, I'm back to 1.9.0 now.
>>> I just had to remove the conflicting libraries by 'rpm -e
>>> library-name' (with the --nodeps option for some of them) before
>>> doing a proper 'yum install'.
>>> I've updated accordingly both french and english procedures I'm
>>> maintaining on my wiki:
>>> http://www.webmaster-en-herbe.net/wiki/doku.php?id=wiki:configurati
>>> on-2:digikam
>>> http://www.webmaster-en-herbe.net/wiki/doku.php?id=wiki:configurat
>>> ion-2:digikam-en
>>
>> Hm, removing packages with --nodeps should not be necessary. It is
>> usually not a good idea to do so - except for reinstalling a basic
>> component.
>>
>> For most kde stuff you can uninstall the package and a later started
>> 'yum install' should bring all back.
>>
>> Do you know which packages you have to erase with --nodeps?
>>
>> Regards
>>
>> Martin
>>
>>>
>>> Regarding the persistent bug I had with both versions 2.0.0 and
>>> 2.1.0 versions, I would very much like to know where it is being
>>> monitored as I understand taht this one is closed:
>>> https://bugs.kde.org/show_bug.cgi?id=268267
>>>
>>> Marie-Noëlle
>>>
>> _______________________________________________
>> Digikam-users mailing list
>> [hidden email]
>> https://mail.kde.org/mailman/listinfo/digikam-users
>>
>
>
>

_______________________________________________
Digikam-users mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-users

Le 25/08/2011 22:54, Marie-Noëlle Augendre a écrit :
> I might have missed something ... Why do the compilation if it is not
> to launch the program?

I tried to have more than one digikam version on my openSUSE 11.4

It's often -but probably not with kde applications- possible to run a
programm directly from it's compilation folder, without installation.

so what I did was to clic on "digikam" in the compilation folder, but
this simply launched the *system* digikam, not the newly compiled
digikam :-(, but I didn't notice this on the beginning.

Now I have digikam 2.0 running without visible problem (of course
needs real use to be sure)

jdd


--
http://www.dodin.net
http://www.youtube.com/user/jdddodinorg
http://jdd.blip.tv/
_______________________________________________
Digikam-users mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-users

[tosca]

2011/8/26 jdd <[hidden email]>:

> I tried to have more than one digikam version on my openSUSE 11.4
>

Well, if somebody has the answer to that, I'll be very interested.
As for now, I seem to be stucked with the 1.9 version till this
problem with libdc1394 is really solved.

Marie-Noëlle


--
Une galerie photos, un blog ... pourquoi pas ? Webmaster en herbe

Parcourez les Cévennes à ma façon : Cévennes Plurielles

Et toutes mes autres publications à partir de ma page d'accueil générale
_______________________________________________
Digikam-users mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-users