FreeBSD Port: graphics/digikam

Holger Wagemann Holger.Wagemann at posteo.de
Wed Oct 9 06:29:15 BST 2019


Dear maintainer,

I'm a desktop user, like the work of kde-freebsd team to have a current 
plasma5 desktop and other applications like digikam.

I use pkg and latest stuff, sometimes head branch and ports and apart 
from some instabilities, which were fixed in the past in a short time, 
I'm satisfied with combination of FreeBSD and plasma5 and further 
desktop stuff.

After switching from digikam 6.0.0 to a newer version some weeks ago in 
"latest" this software is broken, it starts reproducible with a 
segfault. This bug is reported since 2019-09-10.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=240466

Okay, in quarterly branch 2019Q3 there was digikam in version 6.0.0 and 
this version works. So some days ago I've switched from head to 
quarterly, to reduce such issues.

But yesterday you switched to new quarterly branch 2019Q4 and with a pkg 
upgrade I get new binaries, also digikam, and now in version 6.3.0. And 
it starts with a segfault.

My question: Why putting broken stuff from head in a new quarterly 
branch? I thought, that quarterly protects user from such issues and 
only working stuff from head was putting into a new quarterly branch 
(like manjaro: stuff from testing repo was putting to stable repo, when 
it is stable). But it seems, that a new quartely branch only get a 
snapshot of binaries from head without any inspection, if this stuff 
works or not.

What can I do to get a working version of digikam in combination with 
FreeBSD?

And how can I avoid such issues in the future? Still using quarterly 
seems not to be enough. Please keep in mind, that I'm a user and not a 
developer.

Kind regards
   Holger
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/kde-freebsd/attachments/20191009/871671ee/attachment-0001.html>


More information about the kde-freebsd mailing list