Hi Tobias, dear committer of kde-freebsd,
thanks for your efforts. My mail should not to be a rant, more a
question, how to avoid such trouble in thew future and how to get help.
I'm patient, maybe the segfault of digikam has to do with further broken
stuff and fixing that needs time, and I know, you spend your leisure time.
Today I'll set up a further FreeBSD installation with latest repo and
head branch. And if I can help you fixing such stuff, please let me know
which info you need.
Kind regards,
Holger
Am 09.10.19 um 19:52 schrieb Tobias C. Berner:
Hi Holger
Sorry for the breakage. Due to a lack of free time, I could not yet
investigate the breakage.I will, as soon as I can :)
The quarterly branch gives you no guarantees at all -- it is cut at a
given time, and if you are lucky the tree was in a good state at the
time. Afterwards it just mostly gets older :D -- so there is no
process of choosing "stable" staff for the quarterly (so it's purely
timing based -- quarterly, literally).
I think this time it was just bad luck, I assume, I did some testing
and found it working, but apparently it wasn't, or I didn't :) --
totally my bad here.
I hope to have time to fix it by this or the next weekend -- no
promises, patches are welcome :D.
If you really require it to be working right now, you can just grab
the port from the revision prior to its upgrade and built the old one
-- that should work.
mfg Tobias
On Wed, 9 Oct 2019 at 07:29, Holger Wagemann
<holger.wagem...@posteo.de <mailto:holger.wagem...@posteo.de>> wrote:
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
