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 k
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=240466
--- Comment #7 from commit-h...@freebsd.org ---
A commit references this bug:
Author: adridg
Date: Sun Oct 13 08:41:23 UTC 2019
New revision: 514373
URL: https://svnweb.freebsd.org/changeset/ports/514373
Log:
Try to fix runtime graphics/
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=239023
--- Comment #3 from Antoine Brodin ---
Failure log on 12.0 amd64:
http://package18.nyi.freebsd.org/data/120amd64-default-PR238988/2019-10-12_19h22m07s/logs/messagelib-19.08.1_1.log
--
You are receiving this mail because:
You are on the C
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=228640
--- Comment #5 from Raphael Kubo da Costa ---
Kopete's build system is still "broken" in the sense that some files rely on
automated moc processing by including "foo.moc" in the source code, and some do
not, so the build system also relies
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=228640
--- Comment #6 from Ed Maste ---
(In reply to Raphael Kubo da Costa from comment #5)
> I guess lld has gotten smarter since this bug was filed?
Or the original problem was just lld being more strict about a bug which has
since been fixed u
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=228640
Raphael Kubo da Costa changed:
What|Removed |Added
CC||rak...@freebsd.org
--- Com
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=228640
--- Comment #8 from commit-h...@freebsd.org ---
A commit references this bug:
Author: rakuco
Date: Sun Oct 13 14:04:02 UTC 2019
New revision: 514392
URL: https://svnweb.freebsd.org/changeset/ports/514392
Log:
Drop LLD_UNSAFE=yes.
The
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=237934
Raphael Kubo da Costa changed:
What|Removed |Added
Assignee|ports-b...@freebsd.org |k...@freebsd.org
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=237934
--- Comment #1 from commit-h...@freebsd.org ---
A commit references this bug:
Author: rakuco
Date: Sun Oct 13 14:18:07 UTC 2019
New revision: 514393
URL: https://svnweb.freebsd.org/changeset/ports/514393
Log:
Drop dependency on graphics/
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=237934
Raphael Kubo da Costa changed:
What|Removed |Added
Resolution|--- |FIXED
Status|N
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=240343
--- Comment #14 from commit-h...@freebsd.org ---
A commit references this bug:
Author: rakuco
Date: Sun Oct 13 15:08:32 UTC 2019
New revision: 514401
URL: https://svnweb.freebsd.org/changeset/ports/514401
Log:
Add USES=gnome.
Fix a DE
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=241227
Bug ID: 241227
Summary: ports-mgmt/portmaster: When
installing/reinstalling/upgrading devel/cmake
portmaster always reinstall textproc/py-sphinx even if
it is
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=240343
--- Comment #15 from Raphael Kubo da Costa ---
(In reply to Kubilay Kocak from comment #13)
> This issue is very likely going to hit other ports that use cmake.
In this case, isn't it better to always add this to CMAKE_ARGS in
Uses/python.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=241227
Raphael Kubo da Costa changed:
What|Removed |Added
Assignee|ports-b...@freebsd.org |s...@freebsd.org
--- Comme
Bugzilla Automation has asked k...@freebsd.org for
maintainer-feedback:
Bug 241231: security/plasma5-kscreenlocker: "Start New Session" does not work
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=241231
--- Description ---
avg@ reports to the mailing list
(https://mail.kde.org/pipermail/kde
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=241231
Bug ID: 241231
Summary: security/plasma5-kscreenlocker: "Start New Session"
does not work
Product: Ports & Packages
Version: Latest
Hardware: Any
OS:
On Mon, 2019-07-08 at 11:55 +0300, Andriy Gapon wrote:
> Does user switching work for anybody?
> Is there any additional configuration needed to get it working?
>
> It does not work for me at all. When I click "Start New Session" I
> am taken
> back to the unlock screen for a current user.
> This
To view an individual PR, use:
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=(Bug Id).
The following is a listing of current problems submitted by FreeBSD users,
which need special attention. These represent problem reports covering
all versions including experimental development code and ob
18 matches
Mail list logo
