FreeBSD ports you maintain which are out of date

2017-09-19 Thread portscout
Dear port maintainer,

The portscout new distfile checker has detected that one or more of your
ports appears to be out of date. Please take the opportunity to check
each of the ports listed below, and if possible and appropriate,
submit/commit an update. If any ports have already been updated, you can
safely ignore the entry.

You will not be e-mailed again for any of the port/version combinations
below.

Full details can be found at the following URL:
http://portscout.freebsd.org/k...@freebsd.org.html


Port| Current version | New version
+-+
x11/kf5-kglobalaccel| 5.38.0  | 5.38.1
+-+


If any of the above results are invalid, please check the following page
for details on how to improve portscout's detection and selection of
distfiles on a per-port basis:

http://portscout.freebsd.org/info/portscout-portconfig.txt

Thanks.


[Bug 220714] devel/boost-all: Update to 1.65.1

2017-09-19 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=220714

Raphael Kubo da Costa  changed:

   What|Removed |Added

 CC|k...@freebsd.org |

-- 
You are receiving this mail because:
You are on the CC list for the bug.

Re: Questions on testing kde5

2017-09-19 Thread Mario Lobo
Thanks for answering. Tobias!

Forgive me for bothering you a little more.

My machine:
FreeBSD 11.1-STABLE #0 r321652M Aug 25 20:19:41 -03 2017 

I downloaded the ports branch from

https://github.com/freebsd/freebsd-ports-kde/tree/plasma5

On that branch, there are the following ports under x11:

kde/
kde-baseapps/
kde-runtime/
kde4-workspace/
kdelibs4/

The kde/Makefile points to KDE5 meta port.

My current kde4 settings reside in ~/.kde4

Suppose I decide to go ahead with this and the kde5 port compiles ok:

1) Where will kde 5 store its settings? ~/.kde?

3) Will copying these settings over to the new "~/.kde" directory work
   so I can have a desktop similar contents on my kde5 desktop?

2) Are the two kde4-workspace/ and kdelibs4/ above some kind of kde4
compatibility layer that can be installed on top of kde 5?

3) Any other ports you recommend installing, besides the meta port, for
a fuller kde5/plasma5 experience?


Thanks again!
-- 
Mario Lobo
http://www.mallavoodoo.com.br
FreeBSD since 2.2.8 [not Pro-Audio YET!!]
 
"UNIX was not designed to stop you from doing stupid things, 
because that would also stop you from doing clever things."


On Tue, 19 Sep 2017 07:54:44 +0200
"Tobias C. Berner"  wrote:

> Hi Mario
> 
> The plasma5 branch is mostly "Plasma5" only -- most of the KDE4 stuff
> has been removed.
> 
> Even by mixing ports-trees, you cannot install both versions at the
> same time in general as they have many conflicting files.
> It is possible to run certain KDE4 based applications inside a Plasma5
> session and vice-versa.
> 
> 
> mfg Tobias
> 
> On 19 September 2017 at 01:26, Mario Lobo  wrote:
> 
> > Hi there;
> >
> > I will try to compile/install kde5 from the plasma5 branch (area51).
> >
> > Is it possible to have both kde4 and kde5 on the same machine?
> > Can they coexist without disrupting each other?
> >
> > Can kde4 apps (like k3b) run on kde5?
> >
> > I really would like to test kde5/plasma5.
> >
> > Thanks for any advice.
> >


Re: Questions on testing kde5

2017-09-19 Thread Tobias C. Berner
Hi Mario

x11/kde is basically the new big-fat metaport. It pulls in the desktop
(plasma5) and many applications

1) most of the stuff is under ~/.config now
3) there should be a some import of the configuration happening
theoretically... not sure how good it works -- be save, make a backup of
your config =)
2) kde4-worskpace got  back in due to a bad git-merge -- it will get
dropped again. kde-runtime is also is only there as a dangling port -- not
really needed by anything anymore -- I should clean that up :)
3) if you install x11/kde with all the meta-port options enabled you'll get
the full thing. -- it more or less depends on what you need... isntalling
x11/plasma5-plasma-desktop + "the applications you need" is also a slimer
possibility.


mfg Tobias



On 19 September 2017 at 20:43, Mario Lobo  wrote:

> Thanks for answering. Tobias!
>
> Forgive me for bothering you a little more.
>
> My machine:
> FreeBSD 11.1-STABLE #0 r321652M Aug 25 20:19:41 -03 2017
>
> I downloaded the ports branch from
>
> https://github.com/freebsd/freebsd-ports-kde/tree/plasma5
>
> On that branch, there are the following ports under x11:
>
> kde/
> kde-baseapps/
> kde-runtime/
> kde4-workspace/
> kdelibs4/
>
> The kde/Makefile points to KDE5 meta port.
>
> My current kde4 settings reside in ~/.kde4
>
> Suppose I decide to go ahead with this and the kde5 port compiles ok:
>
> 1) Where will kde 5 store its settings? ~/.kde?
>
> 3) Will copying these settings over to the new "~/.kde" directory work
>so I can have a desktop similar contents on my kde5 desktop?
>
> 2) Are the two kde4-workspace/ and kdelibs4/ above some kind of kde4
> compatibility layer that can be installed on top of kde 5?
>
> 3) Any other ports you recommend installing, besides the meta port, for
> a fuller kde5/plasma5 experience?
>
>
> Thanks again!
> --
> Mario Lobo
> http://www.mallavoodoo.com.br
> FreeBSD since 2.2.8 [not Pro-Audio YET!!]
>
> "UNIX was not designed to stop you from doing stupid things,
> because that would also stop you from doing clever things."
>
>
> On Tue, 19 Sep 2017 07:54:44 +0200
> "Tobias C. Berner"  wrote:
>
> > Hi Mario
> >
> > The plasma5 branch is mostly "Plasma5" only -- most of the KDE4 stuff
> > has been removed.
> >
> > Even by mixing ports-trees, you cannot install both versions at the
> > same time in general as they have many conflicting files.
> > It is possible to run certain KDE4 based applications inside a Plasma5
> > session and vice-versa.
> >
> >
> > mfg Tobias
> >
> > On 19 September 2017 at 01:26, Mario Lobo  wrote:
> >
> > > Hi there;
> > >
> > > I will try to compile/install kde5 from the plasma5 branch (area51).
> > >
> > > Is it possible to have both kde4 and kde5 on the same machine?
> > > Can they coexist without disrupting each other?
> > >
> > > Can kde4 apps (like k3b) run on kde5?
> > >
> > > I really would like to test kde5/plasma5.
> > >
> > > Thanks for any advice.
> > >
>


maintainer-feedback requested: [Bug 222463] www/qt5-webengine: "use of undeclared identifier 'ED25519_verify'"

2017-09-19 Thread bugzilla-noreply
Peter Kien  has reassigned Bugzilla Automation
's request for maintainer-feedback to k...@freebsd.org:
Bug 222463: www/qt5-webengine: "use of undeclared identifier 'ED25519_verify'"
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=222463



--- Description ---
www/qt5-webengine fails to compile on my machine with the following message:

(...)

-I/wrkdirs/usr/ports/www/qt5-webengine/work/qtwebengine-opensource-src-5.7.1/sr
c/3rdparty/chromium/third_party/boringssl/src/include
-fstack-protector --param=ssp-buffer-size=4 -pthread -fno-strict-aliasing -Wall
-Wextra -Wno-unused-parameter -Wno-missing-field-initializers
-fvisibility=hidden -pipe -fPIC -fcolor-diagnostics -Wheader-hygiene
-Wno-char-subscripts -Wno-unneeded-internal-declaration
-Wno-covered-switch-default -Wstring-conversion -Wno-c++11-narrowing
-Wno-deprecated-register -Wno-inconsistent-missing-override
-Wno-tautological-compare -Wno-unknown-warning-option -Wexit-time-destructors
-I/usr/local/include/glib-2.0 -I/usr/local/lib/glib-2.0/include
-I/usr/local/include -pthread -I/usr/local/include/opus
-I/usr/local/include/libpng16 -I/usr/local/include -I/usr/local/include
-I/usr/local/include/freetype2 -I/usr/local/include -D_THREAD_SAFE -pthread
-m64
-march=x86-64 -O2 -fno-ident -fdata-sections -ffunction-sections
-funwind-tables
-U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=2 -O2 -pipe -march=native -DHARDENEDBSD
-fPIE -fPIC -fstack-protector -fno-strict-aliasing -DHARDENEDBSD -fPIE -fPIC
-fno-exceptions -fno-rtti -fno-threadsafe-statics -fvisibility-inlines-hidden
-std=gnu++11 -stdlib=libc++ -c
/wrkdirs/usr/ports/www/qt5-webengine/work/qtwebengine-opensource-src-5.7.1/src/
3rdparty/chromium/content/common/experiments/api_key.cc
-o
obj/src/3rdparty/chromium/content/common/experiments/content_common.api_key.o
/wrkdirs/usr/ports/www/qt5-webengine/work/qtwebengine-opensource-src-5.7.1/src/
3rdparty/chromium/content/common/experiments/api_key.cc:137:16:
error: use of undeclared identifier 'ED25519_verify' int result =
ED25519_verify( ^


1 error generated.
[10640/11263] CXX
obj/src/3rdparty/chromium/content/common/content_common.cc_messages.o
[10641/11263] CXX
obj/src/3rdparty/chromium/content/common/cursors/content_common.webcursor.o
[10642/11263] CXX
obj/src/3rdparty/chromium/content/common/content_common.content_param_traits.o
[10643/11263] CXX
obj/src/3rdparty/chromium/content/common/content_common.content_switches_intern
al.o
[10644/11263] CXX
obj/src/3rdparty/chromium/content/common/content_common.cross_site_document_cla
ssifier.o
[10645/11263] CXX
obj/src/3rdparty/chromium/content/common/content_common.content_message_generat
or.o
ninja: build stopped: subcommand failed.
*** [invoke_ninja] Error code 1

make[4]: stopped in /wrkdirs/usr/ports/www/qt5-webengine/work/.build/src/core
1 error

make[4]: stopped in /wrkdirs/usr/ports/www/qt5-webengine/work/.build/src/core
*** [sub-gyp_run-pro-make_first] Error code 2

make[3]: stopped in /wrkdirs/usr/ports/www/qt5-webengine/work/.build/src/core
1 error

make[3]: stopped in /wrkdirs/usr/ports/www/qt5-webengine/work/.build/src/core
*** [sub-core-make_first] Error code 2

make[2]: stopped in /wrkdirs/usr/ports/www/qt5-webengine/work/.build/src
1 error

make[2]: stopped in /wrkdirs/usr/ports/www/qt5-webengine/work/.build/src
*** [sub-src-make_first] Error code 2

make[1]: stopped in /wrkdirs/usr/ports/www/qt5-webengine/work/.build
1 error

make[1]: stopped in /wrkdirs/usr/ports/www/qt5-webengine/work/.build
===> Compilation failed unexpectedly.


[Bug 222463] www/qt5-webengine: "use of undeclared identifier 'ED25519_verify'"

2017-09-19 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=222463

Bug ID: 222463
   Summary: www/qt5-webengine: "use of undeclared identifier
'ED25519_verify'"
   Product: Ports & Packages
   Version: Latest
  Hardware: Any
OS: Any
Status: New
  Severity: Affects Some People
  Priority: ---
 Component: Individual Port(s)
  Assignee: k...@freebsd.org
  Reporter: peter.k...@posteo.org
  Assignee: k...@freebsd.org
 Flags: maintainer-feedback?(k...@freebsd.org)

www/qt5-webengine fails to compile on my machine with the following message:

(...)

-I/wrkdirs/usr/ports/www/qt5-webengine/work/qtwebengine-opensource-src-5.7.1/src/3rdparty/chromium/third_party/boringssl/src/include
-fstack-protector --param=ssp-buffer-size=4 -pthread -fno-strict-aliasing -Wall
-Wextra -Wno-unused-parameter -Wno-missing-field-initializers
-fvisibility=hidden -pipe -fPIC -fcolor-diagnostics -Wheader-hygiene
-Wno-char-subscripts -Wno-unneeded-internal-declaration
-Wno-covered-switch-default -Wstring-conversion -Wno-c++11-narrowing
-Wno-deprecated-register -Wno-inconsistent-missing-override
-Wno-tautological-compare -Wno-unknown-warning-option -Wexit-time-destructors
-I/usr/local/include/glib-2.0 -I/usr/local/lib/glib-2.0/include
-I/usr/local/include -pthread -I/usr/local/include/opus
-I/usr/local/include/libpng16 -I/usr/local/include -I/usr/local/include
-I/usr/local/include/freetype2 -I/usr/local/include -D_THREAD_SAFE -pthread
-m64
-march=x86-64 -O2 -fno-ident -fdata-sections -ffunction-sections
-funwind-tables
-U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=2 -O2 -pipe -march=native -DHARDENEDBSD
-fPIE -fPIC -fstack-protector -fno-strict-aliasing -DHARDENEDBSD -fPIE -fPIC
-fno-exceptions -fno-rtti -fno-threadsafe-statics -fvisibility-inlines-hidden
-std=gnu++11 -stdlib=libc++ -c
/wrkdirs/usr/ports/www/qt5-webengine/work/qtwebengine-opensource-src-5.7.1/src/3rdparty/chromium/content/common/experiments/api_key.cc
-o
obj/src/3rdparty/chromium/content/common/experiments/content_common.api_key.o
/wrkdirs/usr/ports/www/qt5-webengine/work/qtwebengine-opensource-src-5.7.1/src/3rdparty/chromium/content/common/experiments/api_key.cc:137:16:
error: use of undeclared identifier 'ED25519_verify' int result =
ED25519_verify( ^


1 error generated.
[10640/11263] CXX
obj/src/3rdparty/chromium/content/common/content_common.cc_messages.o
[10641/11263] CXX
obj/src/3rdparty/chromium/content/common/cursors/content_common.webcursor.o
[10642/11263] CXX
obj/src/3rdparty/chromium/content/common/content_common.content_param_traits.o
[10643/11263] CXX
obj/src/3rdparty/chromium/content/common/content_common.content_switches_internal.o
[10644/11263] CXX
obj/src/3rdparty/chromium/content/common/content_common.cross_site_document_classifier.o
[10645/11263] CXX
obj/src/3rdparty/chromium/content/common/content_common.content_message_generator.o
ninja: build stopped: subcommand failed.
*** [invoke_ninja] Error code 1

make[4]: stopped in /wrkdirs/usr/ports/www/qt5-webengine/work/.build/src/core
1 error

make[4]: stopped in /wrkdirs/usr/ports/www/qt5-webengine/work/.build/src/core
*** [sub-gyp_run-pro-make_first] Error code 2

make[3]: stopped in /wrkdirs/usr/ports/www/qt5-webengine/work/.build/src/core
1 error

make[3]: stopped in /wrkdirs/usr/ports/www/qt5-webengine/work/.build/src/core
*** [sub-core-make_first] Error code 2

make[2]: stopped in /wrkdirs/usr/ports/www/qt5-webengine/work/.build/src
1 error

make[2]: stopped in /wrkdirs/usr/ports/www/qt5-webengine/work/.build/src
*** [sub-src-make_first] Error code 2

make[1]: stopped in /wrkdirs/usr/ports/www/qt5-webengine/work/.build
1 error

make[1]: stopped in /wrkdirs/usr/ports/www/qt5-webengine/work/.build
===> Compilation failed unexpectedly.

-- 
You are receiving this mail because:
You are the assignee for the bug.

maintainer-approval requested: [Bug 222207] [cmake] net/ceph & net/ceph-devel: fails to build with boost 1.65 : [Attachment 186555] Backport upstream commits

2017-09-19 Thread bugzilla-noreply
Jan Beich  has asked k...@freebsd.org for
maintainer-approval:
Bug 07: [cmake] net/ceph & net/ceph-devel: fails to build with boost 1.65
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=07

Attachment 186555: Backport upstream commits
https://bugs.freebsd.org/bugzilla/attachment.cgi?id=186555&action=edit



--- Comment #4 from Jan Beich  ---
Created attachment 186555
  --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=186555&action=edit
Backport upstream commits

(In reply to Willem Jan Withagen from comment #3)
> why do es a build running 11.0-RELEASE try to fetch 1.65???

The build log is from an exp-run. Once bug 220714 lands this package would be
marked BROKEN unless you prefer pkg-fallout@ spam. AFAIK, there're no testing
repos where you can install binary packages for pending port updates.

office@ doesn't seem to plan to maintain more than one version of boost as
illustrated by how long it took to land bug 199601. I'm not part of office@
team, if not obvious.


[Bug 222207] [cmake] net/ceph & net/ceph-devel: fails to build with boost 1.65

2017-09-19 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=07

Jan Beich  changed:

   What|Removed |Added

 Attachment #186555||maintainer-approval?(kde@Fr
  Flags||eeBSD.org)

--- Comment #4 from Jan Beich  ---
Created attachment 186555
  --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=186555&action=edit
Backport upstream commits

(In reply to Willem Jan Withagen from comment #3)
> why do es a build running 11.0-RELEASE try to fetch 1.65???

The build log is from an exp-run. Once bug 220714 lands this package would be
marked BROKEN unless you prefer pkg-fallout@ spam. AFAIK, there're no testing
repos where you can install binary packages for pending port updates.

office@ doesn't seem to plan to maintain more than one version of boost as
illustrated by how long it took to land bug 199601. I'm not part of office@
team, if not obvious.

-- 
You are receiving this mail because:
You are on the CC list for the bug.

[Bug 222207] [cmake] net/ceph & net/ceph-devel: fails to build with boost 1.65

2017-09-19 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=07

--- Comment #5 from Willem Jan Withagen  ---
(In reply to Jan Beich from comment #4)

Life could be simple, but then it never really is.

I'm not really into the version of Boost OR Cmake.
Just as long as a new Boost also updates the versioning in Cmake.

So every time Boost upgrades with the matching Cmake definitions, my ports will
break. Which is bad, but I can't do much about it if the Cmake maintainer
chooses not to upgrade.

I would consider your patch of rahter limited impact, but then that's me.
It is up to KDE@ to actually "do the right thing"

Other than harassing them over this 
But I'd expect breakage for everything that mixes Boost and Cmake.

-- 
You are receiving this mail because:
You are on the CC list for the bug.

[Bug 222207] [cmake] net/ceph & net/ceph-devel: fails to build with boost 1.65

2017-09-19 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=07

Adriaan de Groot  changed:

   What|Removed |Added

 CC||adr...@freebsd.org

--- Comment #6 from Adriaan de Groot  ---
ok, so what we're seeing is that a new boost version comes out, and then the
FindBoost cmake module needs to be updated to actually find that new version,
and to find all the right dependencies. That's surprisingly fragile.

Since CMake 3.9 landed last week, updating this Find-module is a lot simpler,
though. Thanks for pointing out the upstream commits.

I'm not sure if an exp-run is needed for module-updates .. that is something
I'll discuss with my mentors and antoine@.

-- 
You are receiving this mail because:
You are on the CC list for the bug.