[Bug 210354] [patch] sysutils/hal - k3b, brasero does not find optical drive
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=210354 Steve Willschanged: What|Removed |Added Status|Open|Closed Resolution|--- |FIXED --- Comment #11 from Steve Wills --- Committed, thanks! -- You are receiving this mail because: You are on the CC list for the bug.
[Bug 210354] [patch] sysutils/hal - k3b, brasero does not find optical drive
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=210354 --- Comment #10 from commit-h...@freebsd.org --- A commit references this bug: Author: swills Date: Fri Sep 23 00:21:05 UTC 2016 New revision: 422642 URL: https://svnweb.freebsd.org/changeset/ports/422642 Log: sysutils/hal: fix cd support PR: 210354 Submitted by: Ivan KlymenkoApproved by: gnome@ (kwm) Changes: head/sysutils/hal/Makefile head/sysutils/hal/files/patch-hald_freebsd_hf-scsi.c -- You are receiving this mail because: You are on the CC list for the bug.
[Bug 210354] [patch] sysutils/hal - k3b, brasero does not find optical drive
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=210354 --- Comment #9 from Steve Wills--- (In reply to graham from comment #8) You're right, it was a permissions issue. I'll commit it. -- You are receiving this mail because: You are on the CC list for the bug.
[Bug 210354] [patch] sysutils/hal - k3b, brasero does not find optical drive
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=210354 --- Comment #8 from gra...@menhennitt.com.au --- (In reply to Steve Wills from comment #7) I think the fact that hal sees it proves that the bug is being fixed by the patch. Have you done all the steps described in the k3b/pkg-message to fix permissions problems. Alternatively, try running k3b from the command line via sudo e.g. "sudo k3b". It works for me with those steps in place. That said, on 11-stable, the hw.ata.atapi_dma sysctl oid that's described in those steps didn't exist for me. So I couldn't set it to 1. However, it didn't seem to matter. -- You are receiving this mail because: You are on the CC list for the bug.
Re: KF5 in trunk
On Thursday 22 September 2016 10:30:31 Dwayne MacKinnon wrote: > Thanks for the update. I just used the plasma5 branch a few days ago to > install kf5. Should I now check out trunk and use it from here on? At this point, I'd say stick with plasma5/ branch, since it has all the bells and whistles. trunk/ only has kf5 -- the frameworks, for development purposes, and no desktop or kf5-based applications. If you actually want to try to use Plasma 5 Desktop and KDE Applications, use plasma5/ branch from area51. [ade]
[Bug 210354] [patch] sysutils/hal - k3b, brasero does not find optical drive
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=210354 --- Comment #7 from Steve Wills--- (In reply to Steve Wills from comment #5) I believe I have the patch right, but in my testing it didn't help k3b. The device shows up fine in hal, kde shows a blank CDR showing up, but k3b still sees no device. Perhaps something else is required? Is it showing up in the KDE menu enough to prove the hal patch is correct at least? -- You are receiving this mail because: You are on the CC list for the bug.
[Bug 210354] [patch] sysutils/hal - k3b, brasero does not find optical drive
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=210354 Koop Mastchanged: What|Removed |Added CC||k...@freebsd.org Flags|maintainer-feedback?(gnome@ |maintainer-feedback+ |FreeBSD.org)| --- Comment #6 from Koop Mast --- If it works, go ahead and commit it. -- You are receiving this mail because: You are on the CC list for the bug.
[Bug 212764] Processor specific bits in Qt5 packages complicates build of dependent ports
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=212764 --- Comment #12 from Thomas Zander--- (In reply to Raphael Kubo da Costa from comment #11) So unless Qt libs do not perform some kind of runtime cpu detection, it will continue to throw this error if it runs on a cpu which does not support all features for which support was compiled in. Given that probably the large majority of users won't have a problem with this, and the workaround is not too much of an issue ... if you want to close this with "won't fix", I could live with it. Thanks for joining me in investigating the root cause. -- You are receiving this mail because: You are the assignee for the bug.
[SVN Commit] branches/plasma5/KDE/x11-toolkits/kirigami
SVN commit 13064 by tcberner: Add missing dependency on plasma-framwork M +1 -1 Makefile
[SVN Commit] branches/plasma5/KDE/x11/plasma5-plasma-integration
SVN commit 13063 by tcberner: Chase new 'default fonts'. M +2 -5 Makefile
[Bug 210354] [patch] sysutils/hal - k3b, brasero does not find optical drive
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=210354 Steve Willschanged: What|Removed |Added Attachment #171520|0 |1 is obsolete|| --- Comment #5 from Steve Wills --- Created attachment 175067 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=175067=edit updated patch with portrevision Here's an updated diff, testing now, I've run into this issue too. -- You are receiving this mail because: You are on the CC list for the bug.
Re: KF5 in trunk
Hi Adriaan, Thanks for the update. I just used the plasma5 branch a few days ago to install kf5. Should I now check out trunk and use it from here on? Thanks, DMK On September 22, 2016 12:27:55 AM Adriaan de Groot wrote: > Recently, area51 trunk was pretty much declared dead. All the good stuff > (tm) was happening in plasma5/ branch, largely thanks to tcb. Having qt 5.6 > and cmake and some other big PRs in-flight didn't help much: trunk was way > out of sync. > > Trunk has been resurrected. > > After some rough-and-tumble merges, it caught up with official downstream > ports recently, and has now had its role restored as the place where "the > next big thing" is prepared. > > Based off of D7645 (which massaged kde.mk and makes USES=kde a lot more > flexible, again thanks to tcb), trunk has now had KDE Frameworks 5 added. > That's the tiers 1, 2 and 3 from https://api.kde.org/frameworks/ , with only > a few exceptions (which can be found in kde.mk). > > Current roadmap is this: > - get D7645 done, so that all the existing kde4 ports use the new mechanics > - merge that into trunk > - flush trunk, now with kf5, downstream in another review / PR > > This can be done because the kf5 ports are all named consistently and don't > collide with anything. Now, just having kf5 ports in the tree isn't going to > buy us any user-visible functionality, but it's good to have that as a > checkpoint anyway: the supporting libraries. > > The map after getting kf5 in has a number of points of interest, but I don't > know what makes the most sense, order-wise: > > - handle the big name-shuffling to make (name)space for co-existence of > KDE4 and KF5-based applications; there's still the discussion to be had > about the desirability of keeping KDE4 apps in some kind of legacy form. > - add plasma5 desktop; this probably doesn't name-collide with anything > else, and could provide a Plasma 5 desktop experience with KDE4 > applications running in it (or, of course, anything else X-based), > - update KDE4 applications to the latest released versions, > - add KF5-based applications to ports. > > [ade]
[Bug 210354] [patch] sysutils/hal - k3b, brasero does not find optical drive
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=210354 Tobias C. Bernerchanged: What|Removed |Added CC||k...@freebsd.org, ||tcber...@freebsd.org -- You are receiving this mail because: You are on the CC list for the bug.
[Bug 212886] security/gpgme update to 1.7
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=212886 --- Comment #3 from Tobias C. Berner--- Sounds good. Thanks :) -- You are receiving this mail because: You are on the CC list for the bug.
[Bug 212886] security/gpgme update to 1.7
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=212886 Jason E. Halechanged: What|Removed |Added Status|New |In Progress --- Comment #2 from Jason E. Hale --- I think the best course of action would be to package the cpp bindings and the Qt bindings as separate slave ports that the KDE apps can depend on when they are ready to do so. I just started working on this and have already been able to split out the cpp bindings. -- You are receiving this mail because: You are on the CC list for the bug.