Easy downgrade?
Locked
 
|
Hi digiKam-users,
is it possible to safely downgrade DigiKam 4.2.0 by just installing 3.5.0 over it? Did the database format, config file format or anything else change in a way that would cause problems? Thanks, Holger _______________________________________________ Digikam-users mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-users |
|
|
No. DB schema has not changed with 4.2.0. You can downgrade safety.
Just by curiosity : why to downgrade ? Gilles Caulier 2014-09-03 22:17 GMT+02:00 <[hidden email]>: > Hi digiKam-users, > > is it possible to safely downgrade DigiKam 4.2.0 by just installing > 3.5.0 over it? Did the database format, config file format or anything > else change in a way that would cause problems? > > Thanks, > > Holger > > _______________________________________________ > 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 |
|
|
Thank you for your quick reply, Gilles!
The short answer: Many things got slower, and I'm experiencing quite a lot of new bugs in old features that hold me from getting things done. My quick temporary solution is to downgrade. I deliberately didn't give a reason, because I feared this short, unfocussed version could be misinterpreted as a rant about digiKam, its developers, and life in general. ;-) But it's just my lacking the time right now to handle FLOSS bugs as they should be handled. I hope I'll find the time to come back to the concrete points. Thank you so far for a great piece of software. Holger "Gilles Caulier - [hidden email]" <digikamusers.postfach144.3d1ea0e90c.caulier.gilles#[hidden email]> schrieb: > No. DB schema has not changed with 4.2.0. You can downgrade safety. > > Just by curiosity : why to downgrade ? > > Gilles Caulier > > > > 2014-09-03 22:17 GMT+02:00 <[hidden email]>: > > Hi digiKam-users, > > > > is it possible to safely downgrade DigiKam 4.2.0 by just installing > > 3.5.0 over it? Did the database format, config file format or > > anything else change in a way that would cause problems? > > > > Thanks, > > > > Holger > > > > _______________________________________________ > > 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 > _______________________________________________ Digikam-users mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-users |
|
|
On Thursday 04 September 2014 00:37:53
[hidden email] wrote: > Thank you for your quick reply, Gilles! > > The short answer: Many things got slower, and I'm experiencing > quite a lot of new bugs in old features that hold me from getting > things done. My quick temporary solution is to downgrade. > > I deliberately didn't give a reason, because I feared this short, > unfocussed version could be misinterpreted as a rant about digiKam, its > developers, and life in general. ;-) But it's just my lacking the time > right now to handle FLOSS bugs as they should be handled. I hope I'll > find the time to come back to the concrete points. Thank you so far for > a great piece of software. > > Holger > > > "Gilles Caulier - [hidden email]" > <digikamusers.postfach144.3d1ea0e90c.caulier.gilles#[hidden email]> > schrieb: > > > No. DB schema has not changed with 4.2.0. You can downgrade safety. > > > > Just by curiosity : why to downgrade ? > > surprises (I hit an undefined symbol in Geolocation with Digikam 3.5 and KIPI 4.2...) _______________________________________________ Digikam-users mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-users |
|
|
I've been tempted to downgrade because 4.2 still doesn't work right on fedora. I've submitted bugs since 4.1 but I think they believe 4.2 fixed the problem. The trouble I still have is in editing mode, not being able to see the image at the correct size after resizing. Seems the resized image is always scaled to the original size, which makes things like sharpening impossible. Changing the %view to anything doesn't work right...basically same bug that was first reported with 4.0 that seems to be lingering forever but in this case it's probably fedora developers because they did something to get around having to update so many dependencies, especially opencv.
------ Original message------ From: Remco Viëtor Date: Thu, Sep 4, 2014 1:28 AM To: digiKam - Home Manage your photographs as a professional with the power of open source; Subject:Re: [Digikam-users] Easy downgrade?
On Thursday 04 September 2014 00:37:53
[hidden email] wrote: > Thank you for your quick reply, Gilles! > > The short answer: Many things got slower, and I'm experiencing > quite a lot of new bugs in old features that hold me from getting > things done. My quick temporary solution is to downgrade. > > I deliberately didn't give a reason, because I feared this short, > unfocussed version could be misinterpreted as a rant about digiKam, its > developers, and life in general. ;-) But it's just my lacking the time > right now to handle FLOSS bugs as they should be handled. I hope I'll > find the time to come back to the concrete points. Thank you so far for > a great piece of software. > > Holger > > > "Gilles Caulier - [hidden email]" > <digikamusers.postfach144.3d1ea0e90c.caulier.gilles#[hidden email]> > schrieb: > > > No. DB schema has not changed with 4.2.0. You can downgrade safety. > > > > Just by curiosity : why to downgrade ? > > Just remember to also downgrade the KIPI plugins, or you could get some surprises (I hit an undefined symbol in Geolocation with Digikam 3.5 and KIPI 4.2...) _______________________________________________ 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 |
|
|
It does not work for me on openSUSE either. I have the same problem. I build from source so I can easily have multiple installations though. I still use 3.5 for most of my work, I only use 4.2 to download images. Den 5 sep 2014 22:15 skrev "Wilkins, Vern W" <[hidden email]>:
_______________________________________________ Digikam-users mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-users |
|
|
On Saturday 06 September 2014 07:18:06 Anders Stedtlund wrote:
> It does not work for me on openSUSE either. I have the same problem. I > build from source so I can easily have multiple installations though. > > I still use 3.5 for most of my work, I only use 4.2 to download images. > Den 5 sep 2014 22:15 skrev "Wilkins, Vern W" <[hidden email]>: > > > I've been tempted to downgrade because 4.2 still doesn't work right on > > fedora. I've submitted bugs since 4.1 but I think they believe 4.2 fixed > > the problem. The trouble I still have is in editing mode, not being able > > to see the image at the correct size after resizing. Seems the resized > > image is always scaled to the original size, which makes things like > > sharpening impossible. Changing the %view to anything doesn't work > > right...basically same bug that was first reported with 4.0 that seems to > > be lingering forever but in this case it's probably fedora developers > > because they did something to get around having to update so many > > dependencies, especially opencv. Indeed, preview (before/after) still has problems (and that's in both the version from OpenSuse 13.1 and a build from source), to the point it's useless for e.g. the refocus tool. In addition, USM sharpening is behaving weirdly (again, in both the pre- compiled and 'home-build' versions): I see a huge increase in image brightness after sharpening with fairly normal values (1,1,0 for instance). And the values I have to use for 3.5 give really ridiculous results (typical values I use in 3.5 are radius 30, strength 0.5, threshold 0-0.05, and yes, that radius value is high compared to other programs). Also, there's again the automatic generation of previews, which was removed earlier after discussion in this list (not everyone has/can afford the latest 8-core CPUs). And that is just in one of the more commonly used tools. I didn't even get to check out the other tools I tend to use... So for now, I'll stick with 3.5. An alternative would be to change to another editor, and use digikam as a pure image manager. Remco P.S. Sorry if this sounds like a rant, but since several version I'm getting afraid to try the new versions, as there's often new bugs in established functions, and/or undocumented changes in behaviour. Might it be better to introduce new funtionality less often, and have pure bug correction releases (e.g. versions like 4.1.1)? _______________________________________________ Digikam-users mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-users |
«
Return to digikam-users
|
1 view|%1 views
| Free forum by Nabble | Edit this page |