Traceback (most recent call last):
File "configure.py", line 94, in <module>
sys.exit(main(sys.argv))
File "configure.py", line 22, in main
sandbox.run(os.path.join(os.path.dirname(__file__), 'moz.configure'))
File "python/mozbuild/mozbuild/configure/__init__.py", line 241, in run
self._value_for(option)
File "python/mozbuild/mozbuild/configure/__init__.py", line 305, in _value_for
return self._value_for_option(obj)
File "python/mozbuild/mozbuild/util.py", line 924, in method_call
cache[args] = self.func(instance, *args)
File "python/mozbuild/mozbuild/configure/__init__.py", line 370, in _value_for_option
% (e.arg, reason, e.old_arg, e.old_origin))
mozbuild.configure.options.InvalidOptionError: '--enable-debug-symbols' implied by '--enable-debug' conflicts with '--disable-debug-symbols' from the mozconfig
*** Fix above errors and then restart with\
"gmake -f client.mk build"
MFH: 2016Q4 (blanket)
We have been stuck with Perl 5.20 for too long. Now that the main
problem, mod_perl2, has been updated to work with Perl 5.22+, we can go
and live with a modern Perl.
PR: 213810
Submitted by: mat
Exp-run by: antoine
Sponsored by: Absolight
More candidates are likely to come before the official announcement (aka
the rush hour) scheduled on 2016-11-15. This one intended to pick up upstream
security fixes earlier while looking for downstream regressions.
Changes: https://www.mozilla.org/firefox/50.0/releasenotes/
Security: d1853110-07f4-4645-895b-6fd462ad0589
MFH: 2016Q4 (piling up)
This happens when the UID/GID doesn't match the expected number from
UIDs/GIDs.
https://github.com/freebsd/pkg/issues/1485 has more details.
With hat: portmgr
Discussed with: bapt, mat
USES=mono: add nuget argument
The nuget argument adds support for nuget packages. The nuget
packages must be specified in the NUGET_DEPENDS variable.
devel/monodevelop: update to 6.1.1.15
- Switch to github. The other official source is quite a few versions
behind.
- Add missing dependencies (fsharp, ssl2, curl)
- Add required nuget packages
- Add required external repositories
- Drop options. Although ./configure offers these flags, there is no
functional change (i.e. no-op)
- All patches have been upstreamed (and the one we need is from
upstream).
lang/fsharp: update to 4.0.1.15
- convert to use the nuget argument.
ChangeLog:
- Fix null condition in Fsc task
lang/mono-devel: update to 4.6
- switch to new test target (currently tests the port to be installed)
www/gecko-sharp20: depreciate: broken and no-upstream
- Give 1 month for anyone to complain that this port is being removed.
x11-toolkits/gtk-sharp30: bump PORTREVISION
- Add LICENSE information
- Add missing dependencies (per stage-qa)
x11-toolkits/gtk-sharp20: update to 2.12.40.
- Add LICENSE information
- Add missing dependencies (per stage-qa)
- Change download location per Mono's Gtk# website.
PR: 213484
PR: 213796
Reviewed by: mat, romain
Differential Revision: https://reviews.freebsd.org/D8339
This will use Module::CoreList to tell you if a dependency you added can
be removed, or only conditionally added.
Approved by: bapt
Sponsored by: Absolight
Differential Revision: https://reviews.freebsd.org/D7832
Some port's archives contains files modes that are a bit too restrictive
for some usage. For example:
BUILD_DEPENDS= ${NONEXISTENT}:foo/bar:configure
When building as a regular user, dependencies are installed/built as
root, so if the archive contains files that have a mode of, say, 600,
they will not be readable by the port requesting the dependency.
This will also fix broken distribution files where directories don't
have the executable bit on.
OSVERSION 1100077 is after base r283997:
Change directory permissions in pre-order.
In this order, it won't try to recurse into a directory for which it
doesn't have permission, before changing that permission.
This follows an existing behavior in other BSDs, linux, OS X.
PR: 213574
Submitted by: mat
Exp-run by: antoine
Sponsored by: Absolight
Thanks to the upstream work of Marie Loise Nolden, we could get rid of a handful
of patches, as they have been properly upstreamed. The rest of the work is just
some minor plist changes.
I would like to thank Loise <nolden@kde.org> for the upstream work, and Adriaan
<groot@kde.org> for getting the update into shape.
[1] http://blog.qt.io/blog/2016/10/12/qt-5-6-2-released/
[2] http://wiki.qt.io/Qt_5.6.2_Change_Files
PR: 213530
Exp-run by: antoine
Submitted by: Adriaan de Groot <groot@kde.org>
Reviewed by: rakuco, mat, tcberner
Approved by: rakuco (mentor)
Differential Revision: https://reviews.freebsd.org/D8228
You can now set the default version of Varnish with DEFAULT_VERSIONS to
build Varnish and its modules against your desired Varnish release
train.
The default version of Varnish throughout the ports tree will remain as
www/varnish4 until at least 2017Q1 when it will be changed in HEAD to be
www/varnish5. This should allow plenty of time for migration and for
stabilization of the changes in Varnish 5.x.
Submitted by: vanilla
With this change, math/R, math/libRmath, and all cran ports can share one
list of sites.
Reviewed by: mat
Approved by: swills (mentor)
Differential Revision: https://reviews.freebsd.org/D8328
Mk/Uses/linux.mk changes:
- Add support for architecture neutral (noarch) distfiles.
- Add support for 64-bit only ports: set IGNORE on i386 and don't install
32-bit compat libraries on amd64.
Submitted by: Piotr Kubaj <pkubaj@anongoth.pl>
Differential Revision: https://reviews.freebsd.org/D7886
A lot of KDE Ports share MASTERSITES, LICENSE and so one, as they are
released as a bundle upstream, however, there was not really a clean
way to share this information.
Using these new categories, we can simplify the Makefiles for the diverse
KDE ports.
At the moment we support the virtual category
* kde-kde4
In the future, this will be extended to
* kde-frameworks
* kde-plasma
* kde-applications
PR: 213406
Differential Revision: https://reviews.freebsd.org/D7645
Exp-run by : antoine
Reviewed by: mat, rakuco
Approved by: portmgr (mat), rakuco (mentor)
This makes it possible to have:
opt_USE= ldconfig=${PREFIX}/lib/foo/bar
Before this, it would have ended up doing USE_LDCONFIG=/lib/foo/bar,
without ${PREFIX}.
Sponsored by: Absolight
Differential Revision: https://reviews.freebsd.org/D8169
- DTRACE=on crashes building probes with libstdc++
- libc++ by default conflicts with libstdc++ from USE_GCC
PR: 213378
Reported by: dhw, tz, pkg-fallout, Philip Homburg
Some cmake projects use LIB_DESTINATION/pkgconfig to install the pc-files.
For example:
* deskutils/libstreamanalyzer
* sysutils/polkit-qt{,5}
* x11-toolkits/attica
By adding this, we can convert these ports to use pathfix instead of an
uncessessary patch-foo or confusing sed call.
Reviewed by: mat
Approved by: portmgr (mat), mat (mentor)
Differential Revision: https://reviews.freebsd.org/D8141
SeaMonkey now uses FFmpeg directly rather than via GStreamer for H.264
and MP3 playback as part of HTML5. Note, FFmpeg 3.x is unsupported[1].
Changes: http://www.seamonkey-project.org/news#2016-03-14
PR: 210931
Submitted by: net@arrishq.net (based on)
Security: 2c2d1c39-1396-459a-91f5-ca03ee7c64c6
MFH: 2016Q3
[1] SeaMonkey 2.40 is based on Firefox 43 codebase but Firefox 45
is the earliest to have the fix. Backporting maybe tricky:
https://bugzilla.mozilla.org/show_bug.cgi?id=1232268
USES=localbase:ldflags can be used to set LDFLAGS. Normally LDFLAGS
appears too early on the command line causing some ports to link with
their own libraries in LOCALBASE (if installed) instead of WRKSRC.
Also make use of _USES_POST so -L${LOCALBASE}/lib is added as late as
possible after anything a port Makefile might set. Use _USES_POST
instead of .include in libedit.mk and libarchive.mk so things like
'USES=libedit localbase:ldflags' work correctly.
Fix some issues with LIBS in some ports.
Switch ports that don't support LIBS to localbase:ldflags.
PR: 212987
Exp-run by: antoine
Approved by: portmgr (antoine)
WRKSRC is not what we want here: when USES=qmake:outsource is used (such as
in www/webkit-qt5), the build actually takes place in ${WRKDIR}/.build, so
we were creating .qmake.cache in the wrong location and passing the wrong
directory to the linker via -L. With CONFIGURE_WRKSRC, we get the right
value regardless of whether :outsource is used or not.
PR: 212859
Reviewed by: tcberner
MFH: 2016Q3
This took longer than expected, but there are quite a few changes to the
existing ports and a few new ones.
General upstream changes:
- Starting with Qt 5.6.2, Qt will fail at configuration time if LibreSSL is
being used. According to the discussion here:
https://codereview.qt-project.org/#/c/154800/
The Qt project is not opposed to LibreSSL, but does not want to mix
support for it into the OpenSSL backend code, especially as they move
towards supporting OpenSSL 1.1.
People interested in LibreSSL support are welcome to submit a separate
backend upstream, but are expected to maintain it. We (kde@) are not
opposed to carrying some patches authored by others in the future, as long
as they are not huge and destabilizing.
- When Qt detects the compiler supports C++11, it will pass -std=gnu++11 by
default (this is an upstream change). You can add "CONFIG -= c++11" to
your .pro. Qt 5.7 will require C++11.
- www/webkit-qt5: The QtWebKit module is deprecated upstream, and is shipped
separately as a community release tarball. kde@ does not have an ETA for a
qt5-webengine port, as it requires a huge effort (and number of patches)
similar to maintaining www/chromium itself.
- x11-toolkits/qt5-declarative has been deprecated upstream. The last
release is 5.5.1.
Relevant changes:
- devel/qmake5: The freebsd-clang mkspec has become the default mkspec on
FreeBSD, replacing the outdated freebsd-g++ one that was moved to
unsupported/ (it still works though).
- devel/qt5-qdoc: qdoc was moved to qttools upstream, but its data files are
still in qtbase. The data files are now in the qt5-qdoc-data port.
- misc/qt5-doc: Clean up and stop requiring a compiler and fumbling with
mkspecs. Instead of running the `configure' script, which requires a
compiler and adjustments to the mkspecs files and also ends up building a
new qmake binary, we now leverage USES=qmake to generate all the Makefiles
from the top-level qt.pro. Getting this to work requires some tricks,
though, and qt.conf.in has a longer explanation of what's being done.
Switch to USES=gmake to be able to drop MAKE_JOBS_UNSAFE=yes.
New ports:
- comms/qt5-serialbus
- devel/qt5-qdoc-data
- x11-toolkits/qt5-quickcontrols2
Big thanks to Adriaan de Groot (groot@kde.org), tcberner@ and Loise Nolden
(nolden@kde.org) for the huge amount of work they put into this
patch. Loise in particular also sent quite a few changes upstream that were
essential for this update to work.
PR: 211916
