UPDATE: devel/py-backports-abc 0.5
Hi,
This diff updates py-backports-abc to the latest release.
Tested on amd64.
Comments ? OK ?
--
Alexandr Shadchin
Index: Makefile
===
RCS file: /cvs/ports/devel/py-backports-abc/Makefile,v
retrieving revision 1.2
diff -u -p -w -r1.2 Makefile
--- Makefile17 Jan 2016 05:38:22 - 1.2
+++ Makefile14 Nov 2016 07:20:48 -
@@ -1,11 +1,10 @@
# $OpenBSD: Makefile,v 1.2 2016/01/17 05:38:22 shadchin Exp $
-MODPY_EGG_VERSION =0.4
COMMENT = backport of the 'collections.abc' module
+MODPY_EGG_VERSION =0.5
DISTNAME = backports_abc-${MODPY_EGG_VERSION}
PKGNAME = py-backports-abc-${MODPY_EGG_VERSION}
-REVISION = 0
CATEGORIES = devel
@@ -14,9 +13,9 @@ HOMEPAGE =https://github.com/cython/ba
# PSFL
PERMIT_PACKAGE_CDROM = Yes
-MODPY_PI = Yes
-
MODULES = lang/python
+
+MODPY_PI = Yes
MODPY_SETUPTOOLS = Yes
FLAVORS = python3
Index: distinfo
===
RCS file: /cvs/ports/devel/py-backports-abc/distinfo,v
retrieving revision 1.1.1.1
diff -u -p -w -r1.1.1.1 distinfo
--- distinfo15 Nov 2015 08:22:47 - 1.1.1.1
+++ distinfo14 Nov 2016 07:20:48 -
@@ -1,2 +1,2 @@
-SHA256 (backports_abc-0.4.tar.gz) =
iz5Akro9VBx6L5t9DZwCdbIcagHFOmHHMeumaGk50KU=
-SIZE (backports_abc-0.4.tar.gz) = 5593
+SHA256 (backports_abc-0.5.tar.gz) =
AzvlRRSgPiVd91xa7o+eZy9mP5OrtyNETK7I/kNDe94=
+SIZE (backports_abc-0.5.tar.gz) = 9807
Re: [update] xl2tpd 1.3.8
On Thu, Nov 10, 2016 at 2:35 PM, Landry Breuil wrote: > Hi, > > so it seems xl2tpd is now developed again by xelarance, and there's a > 1.3.8 release on github which seems to incorporate most of the patches > we ship. I had never been able to make 1.3.1 work, but with this update > i finally managed to connect against an isakmpd server, so for me it's a > huge improvement. Please test it in your configurations... > Yep, I would like confirm that xl2tpd-1.3.8 is usable and now quite stable after xelarance folks incorporated several stability fixes. Also upstream code includes all our patches so we no need it for latest xl2tpd versions. Sorry, I could not even build test this diff now, but at first glance it looks good. -- Sergey
Re: devel/git: fix PLIST
On 13.11.2016 22:28, Stuart Henderson wrote:
> On 2016/11/13 22:03, David Coppa wrote:
>>
>> Hi!
>>
>> I think these two directories should be registered in the PLIST
>> file.
>>
>> Opinions?
>
> Yes, your diff is correct.
ok benoit@
>
>> Index: Makefile
>> ===
>> RCS file: /cvs/ports/devel/git/Makefile,v
>> retrieving revision 1.163
>> diff -u -p -u -p -r1.163 Makefile
>> --- Makefile 4 Nov 2016 09:43:29 - 1.163
>> +++ Makefile 13 Nov 2016 20:02:59 -
>> @@ -9,6 +9,7 @@ DISTNAME = git-${V}
>> PKGNAME-main = ${DISTNAME}
>> PKGNAME-svn = git-svn-${V}
>> PKGNAME-x11 = git-x11-${V}
>> +REVISION-main = 0
>> CATEGORIES =devel
>>
>> HOMEPAGE = http://git-scm.com/
>> Index: pkg/PLIST-main
>> ===
>> RCS file: /cvs/ports/devel/git/pkg/PLIST-main,v
>> retrieving revision 1.74
>> diff -u -p -u -p -r1.74 PLIST-main
>> --- pkg/PLIST-main 11 Oct 2016 10:59:27 - 1.74
>> +++ pkg/PLIST-main 13 Nov 2016 20:02:59 -
>> @@ -372,6 +372,8 @@ libexec/git/mergetools/xxdiff
>> @man man/man7/gittutorial.7
>> @man man/man7/gitworkflows.7
>> share/doc/pkg-readmes/${FULLPKGNAME}
>> +share/emacs/
>> +share/emacs/site-lisp/
>> share/emacs/site-lisp/git-blame.el
>> share/emacs/site-lisp/git.el
>> share/git-core/
>>
sparc64 bulk build report
bulk build on sparc64-1.ports.openbsd.org started on Thu Oct 20 01:46:19 MDT 2016 finished at Sun Nov 13 19:52:09 MST 2016 lasted 25D12h05m done with kern.version=OpenBSD 6.0-current (GENERIC) #0: Wed Oct 19 16:24:04 MDT 2016 built packages:8704 Oct 20:304 Oct 21:139 Oct 22:28 Oct 23:190 Oct 24:282 Oct 25:357 Oct 26:470 Oct 27:343 Oct 28:551 Oct 29:427 Oct 30:400 Oct 31:898 Nov 1:1946 Nov 2:347 Nov 3:469 Nov 4:315 Nov 5:144 Nov 6:366 Nov 7:217 Nov 8:195 Nov 9:315 Nov 10:457 Nov 11:261 Nov 12:318 Nov 13:234 build failures: 15 http://build-failures.rhaalovely.net//sparc64/2016-10-20/audio/moc.log http://build-failures.rhaalovely.net//sparc64/2016-10-20/devel/ctftools.log http://build-failures.rhaalovely.net//sparc64/2016-10-20/devel/keystone.log http://build-failures.rhaalovely.net//sparc64/2016-10-20/games/bastet.log http://build-failures.rhaalovely.net//sparc64/2016-10-20/geo/qgis.log http://build-failures.rhaalovely.net//sparc64/2016-10-20/plan9/drawterm.log http://build-failures.rhaalovely.net//sparc64/2016-10-20/security/sslscan,openssl.log http://build-failures.rhaalovely.net//sparc64/2016-10-20/sysutils/u-boot.log http://build-failures.rhaalovely.net//sparc64/2016-10-20/textproc/calibre.log http://build-failures.rhaalovely.net//sparc64/2016-10-20/www/kcaldav.log http://build-failures.rhaalovely.net//sparc64/2016-10-20/www/netsurf/browser.log http://build-failures.rhaalovely.net//sparc64/2016-10-20/www/netsurf/netsurf-fb.log http://build-failures.rhaalovely.net//sparc64/2016-10-20/x11/cool-retro-term.log http://build-failures.rhaalovely.net//sparc64/2016-10-20/x11/gtk3mm.log http://build-failures.rhaalovely.net//sparc64/2016-10-20/x11/spice-gtk.log recurrent failures failures/security/sslscan,openssl.log failures/sysutils/u-boot.log failures/textproc/calibre.log failures/www/netsurf/browser.log failures/www/netsurf/netsurf-fb.log failures/x11/spice-gtk.log new failures +++ ls-failures Sun Nov 13 19:53:27 2016 +failures/www/kcaldav.log +failures/x11/cool-retro-term.log +failures/x11/gtk3mm.log resolved failures --- ../old/sparc64/last//ls-failuresWed Oct 19 17:36:48 2016 Base libs: curses.14.0 edit.5.2 event.4.1 expat.11.0 form.6.0 formw.6.0 fuse.1.1 iberty.12.0 menu.6.0 menuw.6.0 ncurses.14.0 ncursesw.14.0 objc.6.0 ossaudio.4.0 panel.6.0 panelw.6.0 pcap.8.1 perl.17.1 radius.1.0 readline.4.0 rpcsvc.2.0 skey.6.0 sndio.6.1 stdc++.57.0 termcap.14.0 .14.0 usbhid.7.0 util.12.1 z.5.0 crypto.38.1 pthread.23.0 ssl.39.1 tls.11.4 c.89.2 c.89.2.a kvm.16.2 m.10.0 X libs: EGL.1.0 FS.10.0 GLESv1_CM.1.0 GLU.9.0 GLw.6.0 ICE.10.0 SM.9.0 X11-xcb.2.0 X11.16.1 XRes.5.0 Xau.10.0 Xaw.15.0 Xaw7.15.0 Xcomposite.4.0 Xcursor.5.0 Xdamage.4.0 Xdmcp.11.0 Xext.13.0 Xfixes.6.0 Xfontcache.5.0 Xi.12.1 Xinerama.6.0 Xmu.11.0 Xmuu.6.0 Xpm.9.0 Xrandr.7.1 Xrender.6.0 Xss.6.0 Xt.11.0 Xtst.11.0 Xv.6.0 XvMC.6.0 XvMCW.2.0 dmx.2.0 XvMCr600.1.0 Xxf86dga.6.0 Xxf86misc.6.0 Xxf86vm.6.0 drm_amdgpu.1.1 drm_nouveau.3.0 drm_radeon.4.0 epoxy.2.0 fontenc.4.0 gbm.0.0 pciaccess.2.0 pixman-1.32.6 pthread-stubs.2.0 txc_dxtn.0.0 xcb-composite.1.0 xcb-cursor.0.0 xcb-damage.1.0 xcb-dpms.1.0 xcb-dri2.1.1 xcb-dri3.0.0 xcb-ewmh.2.0 xcb-icccm.4.0 xcb-image.2.0 xcb-keysyms.3.0 xcb-render-util.2.0 xcb-res.1.1 xcb-shm.1.1 xcb-util.0.0 xcb-xevie.1.0 xcb-xf86dri.2.0 xcb-xinerama.1.0 xcb-xtest.1.0 xcb-xvmc.1.0 xkbfile.6.0 xkbui.5.0 GL.17.0 GLESv2.1.1 OSMesa.10.0 Xfont.13.0 Xft.10.0 glapi.0.2 fontconfig.11.0 freetype.26.0 xcb-glx.1.1 xcb-present.0.1 xcb-randr.2.2 xcb-record.1.1 xcb-render.1.1 xcb-screensaver.1.1 xcb-shape.1.1 xcb-sync.1.2 xcb-xfixes.1.2 xcb-xkb.0.1 xcb-xprint.3.0 xcb-xv.1.1 xcb.4.0 drm.7.2
acme-tiny: Agreement URL does not match the current one
I am trying to migrate few web sites to https using free certificates
from Let's Encrypt. Since I am not crazy about installing official
certbot client I went for acme-tiny. It seems to be broken
# uname -a
OpenBSD horae.autonlab.org 6.0 GENERIC.MP#2 amd64
ValueError: Error registering: 400 {
"type": "urn:acme:error:malformed",
"detail": "Provided agreement URL
[https://letsencrypt.org/documents/LE-SA-v1.0.1-July-27-2015.pdf] does
not match current agreement URL
[https://letsencrypt.org/documents/LE-SA-v1.1.1-August-1-2016.pdf]";,
"status": 400
}
This seems well known bug
http://lists.alioth.debian.org/pipermail/letsencrypt-devel/Week-of-Mon-20160808/000784.html
Best,
Predrag
Re: UPDATE: devel/doxygen
Jeremie Courreges-Anglas writes:
> Stuart Henderson writes:
[...]
>> 3. split the gui off to a different port. keep the same pkgname stem,
>> so it just needs an @pkgpath in PLIST for updates to work.
>
> I'd prefer this option.
In the meantime, let's unbreak the current situation by going back to
Qt4. Rafael, does the -Dforce_qt4:Bool=ON part actually works? I don't
have Qt5 anymore on this machine...
ok?
Index: Makefile
===
RCS file: /d/cvs/ports/devel/doxygen/Makefile,v
retrieving revision 1.37
diff -u -p -r1.37 Makefile
--- Makefile12 Nov 2016 20:59:18 - 1.37
+++ Makefile13 Nov 2016 22:48:32 -
@@ -3,8 +3,6 @@
# Memory hog, stuck for days on the same file (configoptions.cpp) during build.
# XXX check with different optimizer level? see doc/install.doc
NOT_FOR_ARCHS= m88k sh
-# Qt5 doesn't build yet on powerpc
-NOT_FOR_ARCHS-gui= m88k sh powerpc
BROKEN-alpha= .got subsegment exceeds 64K
COMMENT-main= source code documentation generator tool
@@ -15,6 +13,9 @@ DISTNAME= doxygen-${VERSION}.src
PKGNAME-main= doxygen-${VERSION}
FULLPKGNAME-gui=doxygen-gui-${VERSION}
+REVISION-main= 0
+REVISION-gui= 0
+
CATEGORIES=devel textproc
HOMEPAGE= http://www.doxygen.org/
@@ -30,10 +31,8 @@ MASTER_SITES=http://ftp.stack.nl/pub/us
MULTI_PACKAGES=-main -gui
PSEUDO_FLAVORS=no_gui bootstrap
-COMMON_WANTLIB= c m pthread estdc++
-WANTLIB-main= ${COMMON_WANTLIB} iconv z xapian
-WANTLIB-gui= Qt5Core Qt5Gui Qt5Widgets Qt5Xml \
- ${COMMON_WANTLIB}
+WANTLIB-main +=c iconv m pthread stdc++ xapian z
+WANTLIB-gui += QtCore QtGui QtXml c m stdc++
LIB_DEPENDS-main= converters/libiconv \
databases/xapian-core
@@ -50,7 +49,8 @@ MODPY_RUNDEP= No
.include
.if ${BUILD_PACKAGES:M-gui}
CONFIGURE_ARGS+=-Dbuild_wizard:Bool=ON
-MODULES+= x11/qt5
+CONFIGURE_ARGS+=-Dforce_qt4:Bool=ON
+MODULES+= x11/qt4
.endif
.if ${MACHINE_ARCH} == "mips64" || ${MACHINE_ARCH} == "mips64el"
# ld(1) fails
--
jca | PGP : 0x1524E7EE / 5135 92C1 AD36 5293 2BDF DDCC 0DFA 74AE 1524 E7EE
Re: UPDATE: devel/doxygen
Stuart Henderson writes:
> On 2016/11/13 21:26, Nigel Taylor wrote:
>> >
>> I will not be able to test building that for sometime as in middle of
>> dpb run, I would say that it will fail. Not proved, but the estdc++ in
>> the wantlib requires the library to be installed, that requires a
>> dependency set by x11/qt5.port.mk,
>>
>> MODQT5_USE_GCC4_MODULE ?= Yes
>> .if ${MODQT5_USE_GCC4_MODULE} == "Yes"
>> MODULES +=gcc4
>> MODGCC4_LANGS += c++
>> MODGCC4_ARCHS ?= *
>> .endif
>>
>> which means either qt5 and gcc4 plus the library is installed or the
>> library isn't installed then relies on the chance dpb has installed gcc4
>> the library in building something else. Before stdc++ from base was used
>> for earlier version with qt4.
>>
>> This would require a LDEP change, and possibly a revision bump also, or
>> the inclusion of the gcc4 module and revision bump.
>
> Yep, valid concern.
>
> As well as the ones you've suggested there's another option too.
> Any of these should work:
>
> 1. add the gcc4 module to doxygen so that the no_gui pseudo-flavour is
> also built with ports gcc. simple, but downside: pushes anything using
> doxygen later in dpb.
>
> 2. turn the no_gui pseudo-flavour back into a real flavour with a
> PFRAG for the gui bits. @pkgpath devel/doxygen,-gui would go in the
> pfrag.
>
> 3. split the gui off to a different port. keep the same pkgname stem,
> so it just needs an @pkgpath in PLIST for updates to work.
I'd prefer this option.
> Whichever is chosen, the current situation is wrong because no_gui is
> only a pseudo-flavour so it is only meant to select which subpackages
> are built and not change anything else; however at present it is also
> changing which compiler is used.
Right. *sigh*
--
jca | PGP : 0x1524E7EE / 5135 92C1 AD36 5293 2BDF DDCC 0DFA 74AE 1524 E7EE
Re: UPDATE: devel/doxygen
On 2016/11/13 21:26, Nigel Taylor wrote:
> >
> I will not be able to test building that for sometime as in middle of
> dpb run, I would say that it will fail. Not proved, but the estdc++ in
> the wantlib requires the library to be installed, that requires a
> dependency set by x11/qt5.port.mk,
>
> MODQT5_USE_GCC4_MODULE ?= Yes
> .if ${MODQT5_USE_GCC4_MODULE} == "Yes"
> MODULES +=gcc4
> MODGCC4_LANGS += c++
> MODGCC4_ARCHS ?= *
> .endif
>
> which means either qt5 and gcc4 plus the library is installed or the
> library isn't installed then relies on the chance dpb has installed gcc4
> the library in building something else. Before stdc++ from base was used
> for earlier version with qt4.
>
> This would require a LDEP change, and possibly a revision bump also, or
> the inclusion of the gcc4 module and revision bump.
Yep, valid concern.
As well as the ones you've suggested there's another option too.
Any of these should work:
1. add the gcc4 module to doxygen so that the no_gui pseudo-flavour is
also built with ports gcc. simple, but downside: pushes anything using
doxygen later in dpb.
2. turn the no_gui pseudo-flavour back into a real flavour with a
PFRAG for the gui bits. @pkgpath devel/doxygen,-gui would go in the
pfrag.
3. split the gui off to a different port. keep the same pkgname stem,
so it just needs an @pkgpath in PLIST for updates to work.
Whichever is chosen, the current situation is wrong because no_gui is
only a pseudo-flavour so it is only meant to select which subpackages
are built and not change anything else; however at present it is also
changing which compiler is used.
Re: UPDATE: /devel/ninja 1.7.1 -> 1.7.2
On Sun Nov 13, 2016 at 09:25:33PM +, Stuart Henderson wrote: > On 2016/11/13 20:57, Rafael Sadowski wrote: > > Hi ports@, Hi Matthew, > > > > simple ninja update. Tested @amd64 with some ports in the last days. > > To save time for testing, which ports did you try it with? (It will > need testing with at least a selection of cmake things, plus one of > chromium/iridium). I know, devel/llvm, x11/tellico-kde4, graphics/opencv, devel/dlib (openbsd-wip), devel/doxygen and more out of my scope are tested.
Re: devel/git: fix PLIST
On 2016/11/13 22:03, David Coppa wrote:
>
> Hi!
>
> I think these two directories should be registered in the PLIST
> file.
>
> Opinions?
Yes, your diff is correct.
> Index: Makefile
> ===
> RCS file: /cvs/ports/devel/git/Makefile,v
> retrieving revision 1.163
> diff -u -p -u -p -r1.163 Makefile
> --- Makefile 4 Nov 2016 09:43:29 - 1.163
> +++ Makefile 13 Nov 2016 20:02:59 -
> @@ -9,6 +9,7 @@ DISTNAME =git-${V}
> PKGNAME-main = ${DISTNAME}
> PKGNAME-svn =git-svn-${V}
> PKGNAME-x11 =git-x11-${V}
> +REVISION-main = 0
> CATEGORIES = devel
>
> HOMEPAGE = http://git-scm.com/
> Index: pkg/PLIST-main
> ===
> RCS file: /cvs/ports/devel/git/pkg/PLIST-main,v
> retrieving revision 1.74
> diff -u -p -u -p -r1.74 PLIST-main
> --- pkg/PLIST-main11 Oct 2016 10:59:27 - 1.74
> +++ pkg/PLIST-main13 Nov 2016 20:02:59 -
> @@ -372,6 +372,8 @@ libexec/git/mergetools/xxdiff
> @man man/man7/gittutorial.7
> @man man/man7/gitworkflows.7
> share/doc/pkg-readmes/${FULLPKGNAME}
> +share/emacs/
> +share/emacs/site-lisp/
> share/emacs/site-lisp/git-blame.el
> share/emacs/site-lisp/git.el
> share/git-core/
>
Re: UPDATE: devel/doxygen
On 11/13/16 19:50, Rafael Sadowski wrote:
> On Sat Nov 12, 2016 at 11:17:18PM +0100, Jeremie Courreges-Anglas wrote:
>> Nigel Taylor writes:
>>
>>> On 10/22/16 16:42, Rafael Sadowski wrote:
On Tue Sep 20, 2016 at 01:33:34AM +0100, Stuart Henderson wrote:
> These plist changes for every update are getting silly, I think I'd
> rather disable doxygen in those ports..
>
Other opinions or agreements?
>>>
>>> I don't build qt5/kde4/kde5 for amd64.
>>>
>>> From what I see, the -gui and hence inclusion qt5 has no point it
>>> doesn't appear to be used in other ports. If no one actually uses the
>>> -gui spending a lot of time building qt5 / and -gui for nothing.
>>>
>>> Because of the size of qt5 this should be split into two ports, rather
>>> than using the PSEUDO_FLAVOR otherwise all the ports listed will be
>>> waiting on the qt5 build to complete when using dpb.
>>>
>>> qt5 itself needs splitting using the separate source files provided,
>>> rather then the combined file with everything needed or not.
>>>
>>> As is I will be just removing -gui / PSEUDO_FLAVOR from the port for myself.
>>
>> Instead of people having to maintain local patches, wouldn't it be
>> better to remove qt5 from this build path? That can surely be done
>> without killing the -gui package.
>>
>>> The same way I have removed kde4 from editors/libreoffice, qt, qt4, qt5
>>> from print/poppler.
>>
>>> The PLIST issue is gnerating html documentation with changed scripts,
>>> images, with the same names
>>>
>>>
>>> also as far as I can see there is an option to force the use of Qt4 if
>>> Qt5 is present.
>>>
>>> From doxygen install document it says...
>>>
>>> Qt Software's GUI toolkit
>>> http://qt-project.org/";>Qt
>>> \addindex Qt
>>> version 4.3 or higher (but currently, Qt 5.x is not yet supported).
>>> This is needed to build the GUI front-end doxywizard.
>>>
>>> I searched the changelog not a single mention of a switch to Qt5
>>>
>>> This looks like we are switching to Qt5 because it being built / test on
>>> a machine with Qt5 installed else the switch to Qt5 hasn't been documented.
>
> No, the worst think about doxygen is the documentation ;). That's sad
> but everting is clear and well readable in the CMake environment. Qt5 is
> default on and Qt4 only available with the option "force_qt4".
>
>>>
>>> So why is this even using Qt5.
>>
>> Upstream made the choice of introducing Qt5 compatibility in this
>> release, and to use Qt5 by default. doxywizard runs fine here.
>> To me it looks like a case of slightly outdated information on the
>> website.
>>
>> Note that this diff has been floating on the mailing-list since some
>> time already, you could have voiced objections earlier. ;)
>>
>
> Diff below based on jca@ idea. "no_gui bootstrap" is set as default.
>
> Kind regards,
>
> Rafael Sadowski
>
> Index: Makefile
> ===
> RCS file: /cvs/ports/devel/doxygen/Makefile,v
> retrieving revision 1.37
> diff -u -p -u -p -r1.37 Makefile
> --- Makefile 12 Nov 2016 20:59:18 - 1.37
> +++ Makefile 13 Nov 2016 19:35:50 -
> @@ -29,6 +29,7 @@ MASTER_SITES= http://ftp.stack.nl/pub/us
>
> MULTI_PACKAGES= -main -gui
> PSEUDO_FLAVORS= no_gui bootstrap
> +FLAVOR?= no_gui bootstrap
>
> COMMON_WANTLIB= c m pthread estdc++
> WANTLIB-main=${COMMON_WANTLIB} iconv z xapian
>
>
I will not be able to test building that for sometime as in middle of
dpb run, I would say that it will fail. Not proved, but the estdc++ in
the wantlib requires the library to be installed, that requires a
dependency set by x11/qt5.port.mk,
MODQT5_USE_GCC4_MODULE ?= Yes
.if ${MODQT5_USE_GCC4_MODULE} == "Yes"
MODULES +=gcc4
MODGCC4_LANGS += c++
MODGCC4_ARCHS ?= *
.endif
which means either qt5 and gcc4 plus the library is installed or the
library isn't installed then relies on the chance dpb has installed gcc4
the library in building something else. Before stdc++ from base was used
for earlier version with qt4.
This would require a LDEP change, and possibly a revision bump also, or
the inclusion of the gcc4 module and revision bump.
It also exposes it to dpb failures that can junk the library / gcc4, and
build with base stdc++ instead. Requires a junk to occur between
patching and configure is difficult to reproduce with dpb.
The runtime may also fail if something else hasn't installed the
library. Then could then cause dpb bulk to fail building the dependent
packages as estdc++ is not present.
None of this is proved. Have to pkg_delete nearly all the packages to
see the problems.
$ env FLAVOR="no_gui bootstrap" make show=LIB_DEPENDS
$ env FLAVOR=no_gui make show=LIB_DEPENDS
$ env FLAVOR= make show=LIB_DEPENDS
x11/qt5 STEM->=4.9,<4.10:lang/gcc/4.9,-libs
$ env SUBPACKAGE=-main FLAVOR= make show=LIB_DEPENDS
x11/qt5 STEM->=4.9,<4.10:lang/gcc/4.9,-libs
$ env SUBPACKAGE=-main ma
Re: [NEW] www/tbb improved, updated
On Sun, Nov 13, 2016 at 09:06:49AM -0600, attila wrote: > > attila writes: > > [snip] > > Landry Breuil writes: > >> So, more nits portswise only: > > > > Thanks a lot for this feedback. Attached is a tarball that attempts > > to address both your and danj@'s concerns. > > > >> - meta/tbb/pkg/DESCR could use some more wording, as > >> www/tbb/tor-browser/pkg/DESCR. > > > > All of the COMMENTs and pkg/DESCR files have been updated. > > > > Naturally, after I posted I found a typo in a COMMENT. While in there > I also rewrote tor-launcher/pkg/DESCR to be a little more informative. > > Updated tarball attached. And the quest is over (or is it just a beginning?), i've imported the whole stuff (cf https://marc.info/?l=openbsd-ports-cvs&m=147907177720815&w=2) - the only final tweak i did was for the COMMENTs, stressing the fact that the way they're installed, they're Tor Browser add-ons (until we figure out a way to make systemwide extensions working out of the box in all mozilla instances..someday, maybe.) ===> www/tor-browser/torbutton Tor Browser add-on for configuring Tor Browser settings ===> www/tor-browser/tor-launcher Tor Browser add-on to manage tor instance ===> www/tor-browser/noscript Tor Browser add-on: flexible JS blocker ===> www/tor-browser/https-everywhere Tor Browser add-on: force https where possible nd i just fixed a typo in my own botched commit. yay. Thanks for your hard work on this. I just hope we'll avoid all the Tor lunatics/crazies/tin-foiled-hats on our mailing-lists now Landry
Re: UPDATE: /devel/ninja 1.7.1 -> 1.7.2
On 2016/11/13 20:57, Rafael Sadowski wrote: > Hi ports@, Hi Matthew, > > simple ninja update. Tested @amd64 with some ports in the last days. To save time for testing, which ports did you try it with? (It will need testing with at least a selection of cmake things, plus one of chromium/iridium).
Re: UPDATE: /devel/ninja 1.7.1 -> 1.7.2
On Sun, Nov 13, 2016 at 8:57 PM, Rafael Sadowski wrote: > Hi ports@, Hi Matthew, > > simple ninja update. Tested @amd64 with some ports in the last days. > > Port highlights: > > - switch to new github repo (official) > - new HOMEPAGE > - add post-install to compile ninja_syntax.py > - cleanup do-install tabs > > Kind regards, > > Rafael Sadowski Thanks, I'll have a look at it tomorrow. Ciao! David
devel/git: fix PLIST
Hi!
I think these two directories should be registered in the PLIST
file.
Opinions?
Index: Makefile
===
RCS file: /cvs/ports/devel/git/Makefile,v
retrieving revision 1.163
diff -u -p -u -p -r1.163 Makefile
--- Makefile4 Nov 2016 09:43:29 - 1.163
+++ Makefile13 Nov 2016 20:02:59 -
@@ -9,6 +9,7 @@ DISTNAME = git-${V}
PKGNAME-main = ${DISTNAME}
PKGNAME-svn = git-svn-${V}
PKGNAME-x11 = git-x11-${V}
+REVISION-main =0
CATEGORIES = devel
HOMEPAGE = http://git-scm.com/
Index: pkg/PLIST-main
===
RCS file: /cvs/ports/devel/git/pkg/PLIST-main,v
retrieving revision 1.74
diff -u -p -u -p -r1.74 PLIST-main
--- pkg/PLIST-main 11 Oct 2016 10:59:27 - 1.74
+++ pkg/PLIST-main 13 Nov 2016 20:02:59 -
@@ -372,6 +372,8 @@ libexec/git/mergetools/xxdiff
@man man/man7/gittutorial.7
@man man/man7/gitworkflows.7
share/doc/pkg-readmes/${FULLPKGNAME}
+share/emacs/
+share/emacs/site-lisp/
share/emacs/site-lisp/git-blame.el
share/emacs/site-lisp/git.el
share/git-core/
UPDATE: /devel/ninja 1.7.1 -> 1.7.2
Hi ports@, Hi Matthew,
simple ninja update. Tested @amd64 with some ports in the last days.
Port highlights:
- switch to new github repo (official)
- new HOMEPAGE
- add post-install to compile ninja_syntax.py
- cleanup do-install tabs
Kind regards,
Rafael Sadowski
Index: Makefile
===
RCS file: /cvs/ports/devel/ninja/Makefile,v
retrieving revision 1.19
diff -u -p -u -p -r1.19 Makefile
--- Makefile12 May 2016 07:14:15 - 1.19
+++ Makefile13 Nov 2016 19:50:57 -
@@ -7,14 +7,12 @@ NOT_FOR_ARCHS=m88k
COMMENT = small build system with a focus on speed
-V =1.7.1
-GH_ACCOUNT = martine
+GH_ACCOUNT = ninja-build
GH_PROJECT = ninja
-GH_TAGNAME = v$V
-DISTNAME = ${GH_PROJECT}-$V
+GH_TAGNAME = v1.7.2
CATEGORIES = devel
-HOMEPAGE = http://martine.github.io/ninja/
+HOMEPAGE = https://ninja-build.org/
MAINTAINER = Matthew Dempsky
# Apache License v2.0
@@ -39,8 +37,8 @@ MAKE_ENV =CXX="${CXX}"
do-build:
@cd ${WRKSRC} && ${SETENV} ${MAKE_ENV} \
- ${MODPY_BIN} ./configure.py --bootstrap \
- --verbose --with-python=${MODPY_BIN}
+ ${MODPY_BIN} ./configure.py --bootstrap \
+ --verbose --with-python=${MODPY_BIN}
do-install:
${INSTALL_PROGRAM} ${WRKBUILD}/ninja ${PREFIX}/bin
@@ -52,5 +50,9 @@ do-install:
${INSTALL_DATA} ${WRKSRC}/misc/ninja.vim ${PREFIX}/share/ninja
${INSTALL_DATA} ${WRKSRC}/misc/ninja_syntax.py ${PREFIX}/share/ninja
${INSTALL_DATA} ${WRKSRC}/misc/zsh-completion ${PREFIX}/share/ninja
+
+post-install:
+ ${MODPY_BIN} ${MODPY_LIBDIR}/compileall.py \
+ ${PREFIX}/share/ninja/ninja_syntax.py
.include
Index: distinfo
===
RCS file: /cvs/ports/devel/ninja/distinfo,v
retrieving revision 1.8
diff -u -p -u -p -r1.8 distinfo
--- distinfo12 May 2016 07:14:15 - 1.8
+++ distinfo13 Nov 2016 19:50:57 -
@@ -1,2 +1,2 @@
-SHA256 (ninja-1.7.1.tar.gz) = UVgd5Tz0cFuJ62sUqFuqcyiK0Iv/JW59MNUpFVgTvhk=
-SIZE (ninja-1.7.1.tar.gz) = 179717
+SHA256 (ninja-1.7.2.tar.gz) = Lt2gpUIazjz0KDCSEScHct01qRr2DJb5P5Dfa8QbFtk=
+SIZE (ninja-1.7.2.tar.gz) = 180611
Index: pkg/PLIST
===
RCS file: /cvs/ports/devel/ninja/pkg/PLIST,v
retrieving revision 1.2
diff -u -p -u -p -r1.2 PLIST
--- pkg/PLIST 14 Jun 2013 16:39:39 - 1.2
+++ pkg/PLIST 13 Nov 2016 19:50:57 -
@@ -7,4 +7,5 @@ share/ninja/bash-completion
share/ninja/ninja-mode.el
share/ninja/ninja.vim
share/ninja/ninja_syntax.py
+share/ninja/ninja_syntax.pyc
share/ninja/zsh-completion
Re: UPDATE: devel/doxygen
On Sat Nov 12, 2016 at 11:17:18PM +0100, Jeremie Courreges-Anglas wrote:
> Nigel Taylor writes:
>
> > On 10/22/16 16:42, Rafael Sadowski wrote:
> >> On Tue Sep 20, 2016 at 01:33:34AM +0100, Stuart Henderson wrote:
> >>> These plist changes for every update are getting silly, I think I'd
> >>> rather disable doxygen in those ports..
> >>>
> >>
> >> Other opinions or agreements?
> >>
> >
> > I don't build qt5/kde4/kde5 for amd64.
> >
> > From what I see, the -gui and hence inclusion qt5 has no point it
> > doesn't appear to be used in other ports. If no one actually uses the
> > -gui spending a lot of time building qt5 / and -gui for nothing.
> >
> > Because of the size of qt5 this should be split into two ports, rather
> > than using the PSEUDO_FLAVOR otherwise all the ports listed will be
> > waiting on the qt5 build to complete when using dpb.
> >
> > qt5 itself needs splitting using the separate source files provided,
> > rather then the combined file with everything needed or not.
> >
> > As is I will be just removing -gui / PSEUDO_FLAVOR from the port for myself.
>
> Instead of people having to maintain local patches, wouldn't it be
> better to remove qt5 from this build path? That can surely be done
> without killing the -gui package.
>
> > The same way I have removed kde4 from editors/libreoffice, qt, qt4, qt5
> > from print/poppler.
>
> > The PLIST issue is gnerating html documentation with changed scripts,
> > images, with the same names
> >
> >
> > also as far as I can see there is an option to force the use of Qt4 if
> > Qt5 is present.
> >
> > From doxygen install document it says...
> >
> > Qt Software's GUI toolkit
> > http://qt-project.org/";>Qt
> > \addindex Qt
> > version 4.3 or higher (but currently, Qt 5.x is not yet supported).
> > This is needed to build the GUI front-end doxywizard.
> >
> > I searched the changelog not a single mention of a switch to Qt5
> >
> > This looks like we are switching to Qt5 because it being built / test on
> > a machine with Qt5 installed else the switch to Qt5 hasn't been documented.
No, the worst think about doxygen is the documentation ;). That's sad
but everting is clear and well readable in the CMake environment. Qt5 is
default on and Qt4 only available with the option "force_qt4".
> >
> > So why is this even using Qt5.
>
> Upstream made the choice of introducing Qt5 compatibility in this
> release, and to use Qt5 by default. doxywizard runs fine here.
> To me it looks like a case of slightly outdated information on the
> website.
>
> Note that this diff has been floating on the mailing-list since some
> time already, you could have voiced objections earlier. ;)
>
Diff below based on jca@ idea. "no_gui bootstrap" is set as default.
Kind regards,
Rafael Sadowski
Index: Makefile
===
RCS file: /cvs/ports/devel/doxygen/Makefile,v
retrieving revision 1.37
diff -u -p -u -p -r1.37 Makefile
--- Makefile12 Nov 2016 20:59:18 - 1.37
+++ Makefile13 Nov 2016 19:35:50 -
@@ -29,6 +29,7 @@ MASTER_SITES= http://ftp.stack.nl/pub/us
MULTI_PACKAGES=-main -gui
PSEUDO_FLAVORS=no_gui bootstrap
+FLAVOR?= no_gui bootstrap
COMMON_WANTLIB= c m pthread estdc++
WANTLIB-main= ${COMMON_WANTLIB} iconv z xapian
Re: UPDATE audio/jack 0.125.0
Daniel Jakots writes: > On Fri, 23 Sep 2016 11:19:44 +0100, David CARLIER > wrote: > >> Hi all, >> >> this is an update of jack to a newer release, dropping couple of >> internal patches in the process. >> >> Kindest regards. > > Symbols were added so bump minor. Updated diff. ok danj@ if someone > wants to review and commit it. Committed, however I made that a major bump. One function that used to take a jack_uuid_t now takes a pointer to a jack_uuid_t, and jack_tmpdir doesn't exist anymore, replaced by function jack_get_tmpdir(). -- jca | PGP : 0x1524E7EE / 5135 92C1 AD36 5293 2BDF DDCC 0DFA 74AE 1524 E7EE
[NEW] games/ags
Hello AGS (Adventure Game Studio) engine is the engine used to run games made with the Adventure Game Studio IDE. To play a game, one need to download a game made with AGS (e.g. from http://www.adventuregamestudio.co.uk/site/games/) Web: https://github.com/adventuregamestudio/ags Comments? Ok? Feedback welcome. Kind regards, David Meier ags.tar.gz Description: ags.tar.gz
Re: UPDATE: textproc/py-yaml 3.12
On Sun, Nov 13, 2016 at 04:33:18PM +1100, Jonathan Gray wrote:
> Index: Makefile
> ===
> RCS file: /cvs/ports/textproc/py-yaml/Makefile,v
> retrieving revision 1.14
> diff -u -p -r1.14 Makefile
> --- Makefile 9 Dec 2015 18:26:47 - 1.14
> +++ Makefile 13 Nov 2016 05:15:05 -
> @@ -2,10 +2,9 @@
>
> COMMENT= YAML parser and emitter in Python
>
> -MODPY_EGG_VERSION=3.11
> +MODPY_EGG_VERSION=3.12
> DISTNAME=PyYAML-${MODPY_EGG_VERSION}
> PKGNAME= py-yaml-${MODPY_EGG_VERSION}
> -REVISION=1
> CATEGORIES= textproc
>
> HOMEPAGE=http://pyyaml.org/wiki/PyYAML
> Index: distinfo
> ===
> RCS file: /cvs/ports/textproc/py-yaml/distinfo,v
> retrieving revision 1.4
> diff -u -p -r1.4 distinfo
> --- distinfo 19 Aug 2014 14:25:11 - 1.4
> +++ distinfo 13 Nov 2016 05:15:12 -
> @@ -1,2 +1,2 @@
> -SHA256 (PyYAML-3.11.tar.gz) = w2yTiocuX/SUk4szsUqqFWy0OexnVI/Ks1Nbt4sIRug=
> -SIZE (PyYAML-3.11.tar.gz) = 248685
> +SHA256 (PyYAML-3.12.tar.gz) = WSdmxjAyB6IO/ERVh3eDItf3OxYb2ZTyJ62qNBuiEqs=
> +SIZE (PyYAML-3.12.tar.gz) = 253011
> Index: patches/patch-lib3_yaml_scanner_py
> ===
> RCS file: patches/patch-lib3_yaml_scanner_py
> diff -N patches/patch-lib3_yaml_scanner_py
> --- patches/patch-lib3_yaml_scanner_py1 Dec 2014 09:24:46 -
> 1.1
> +++ /dev/null 1 Jan 1970 00:00:00 -
> @@ -1,17 +0,0 @@
> -$OpenBSD: patch-lib3_yaml_scanner_py,v 1.1 2014/12/01 09:24:46 jasper Exp $
> -
> -Security fix for CVE-2014-9130
> -http://marc.info/?l=oss-security&m=141720508007010&w=2
> -
> lib3/yaml/scanner.py.origMon Dec 1 10:14:54 2014
> -+++ lib3/yaml/scanner.py Mon Dec 1 10:15:21 2014
> -@@ -299,7 +299,8 @@ class Scanner:
> -
> - # A simple key is required only if it is the first token in the
> current
> - # line. Therefore it is always allowed.
> --assert self.allow_simple_key or not required
> -+# http://marc.info/?l=oss-security&m=141720508007010&w=2
> -+#assert self.allow_simple_key or not required
> -
> - # The next token might be a simple key. Let's save it's number and
> - # position.
> Index: patches/patch-lib_yaml_scanner_py
> ===
> RCS file: patches/patch-lib_yaml_scanner_py
> diff -N patches/patch-lib_yaml_scanner_py
> --- patches/patch-lib_yaml_scanner_py 1 Dec 2014 09:24:46 - 1.1
> +++ /dev/null 1 Jan 1970 00:00:00 -
> @@ -1,17 +0,0 @@
> -$OpenBSD: patch-lib_yaml_scanner_py,v 1.1 2014/12/01 09:24:46 jasper Exp $
> -
> -Security fix for CVE-2014-9130
> -http://marc.info/?l=oss-security&m=141720508007010&w=2
> -
> lib/yaml/scanner.py.orig Wed Mar 26 19:54:13 2014
> -+++ lib/yaml/scanner.py Mon Dec 1 10:15:36 2014
> -@@ -299,7 +299,8 @@ class Scanner(object):
> -
> - # A simple key is required only if it is the first token in the
> current
> - # line. Therefore it is always allowed.
> --assert self.allow_simple_key or not required
> -+# http://marc.info/?l=oss-security&m=141720508007010&w=2
> -+#assert self.allow_simple_key or not required
> -
> - # The next token might be a simple key. Let's save it's number and
> - # position.
ok pea@
Thanks.
[UPDATE] emulators/hatari to 2.0.0
Hi ports@,
Here is a diff to update emulators/hatari to 2.0.0.
Notable changes:
- Build switched to SDL2 as this is now upstream default
- We do not build the Python UI anymore as from this release it doesn't
start anymore and I have no interest in fixing this as I dont use it
(the built in user interface is better). That also allows droping
dependency on py-gtk2
- Regenerated and commented all patches, and updated DESCR to match
updated upstream description
Comments? OK?
Index: Makefile
===
RCS file: /cvs/ports/emulators/hatari/Makefile,v
retrieving revision 1.2
diff -u -p -r1.2 Makefile
--- Makefile22 Sep 2016 12:57:18 - 1.2
+++ Makefile13 Nov 2016 13:30:11 -
@@ -2,9 +2,8 @@
COMMENT = Atari ST/STE/TT/Falcon emulator
-V =1.9.0
+V =2.0.0
DISTNAME = hatari-${V}
-REVISION = 0
EXTRACT_SUFX = .tar.bz2
CATEGORIES = emulators
@@ -16,24 +15,22 @@ MAINTAINER =Frederic Cambus http://download.tuxfamily.org/hatari/$V/
RUN_DEPENDS = devel/desktop-file-utils \
misc/shared-mime-info \
sysutils/mtools \
- x11/gtk+3,-guic \
- x11/py-gtk2
+ x11/gtk+3,-guic
-LIB_DEPENDS = devel/sdl \
+LIB_DEPENDS = devel/sdl2 \
graphics/png
MODULES = devel/cmake \
lang/python
-MODPY_ADJ_FILES = python-ui/*.py \
- tools/debugger/*.py \
+MODPY_ADJ_FILES = tools/debugger/*.py \
tools/hconsole/*.py \
tools/*.py
@@ -47,7 +44,6 @@ pre-configure:
post-install:
${MODPY_BIN} ${MODPY_LIBDIR}/compileall.py \
- ${PREFIX}/share/hatari/hatariui/*.py \
${PREFIX}/share/hatari/hconsole/*.py
gunzip ${PREFIX}/man/man1/*.1.gz
Index: distinfo
===
RCS file: /cvs/ports/emulators/hatari/distinfo,v
retrieving revision 1.1.1.1
diff -u -p -r1.1.1.1 distinfo
--- distinfo31 Jul 2016 23:53:35 - 1.1.1.1
+++ distinfo13 Nov 2016 13:30:11 -
@@ -1,2 +1,2 @@
-SHA256 (hatari-1.9.0.tar.bz2) = srVubL5/h2ml6LHZZZnzktk1G0TKz5WdppBdoG0w6ZI=
-SIZE (hatari-1.9.0.tar.bz2) = 2379016
+SHA256 (hatari-2.0.0.tar.bz2) = UqRHpZtpedVdFSXzxKIewBPkNxNU1mg+3nFUbF5tpXc=
+SIZE (hatari-2.0.0.tar.bz2) = 3899087
Index: patches/patch-CMakeLists_txt
===
RCS file: /cvs/ports/emulators/hatari/patches/patch-CMakeLists_txt,v
retrieving revision 1.1.1.1
diff -u -p -r1.1.1.1 patch-CMakeLists_txt
--- patches/patch-CMakeLists_txt31 Jul 2016 23:53:35 - 1.1.1.1
+++ patches/patch-CMakeLists_txt13 Nov 2016 13:30:11 -
@@ -1,18 +1,24 @@
$OpenBSD: patch-CMakeLists_txt,v 1.1.1.1 2016/07/31 23:53:35 awolk Exp $
CMakeLists.txt.origThu Sep 10 23:16:02 2015
-+++ CMakeLists.txt Wed Jun 22 14:18:20 2016
-@@ -32,6 +32,10 @@ endif(NOT CMAKE_BUILD_TYPE)
-
- set(ENABLE_SDL2 0
- CACHE BOOL "Enable building with libSDL2 instead of v1.2")
+
+Make PortAudio and CAPSImage detection conditional and disabled by default,
+and disable building the Python GTK+2 user interface.
+
+--- CMakeLists.txt.origThu Nov 3 22:25:43 2016
CMakeLists.txt Sat Nov 12 17:20:14 2016
+@@ -40,6 +40,12 @@ set(ENABLE_SMALL_MEM 0
+ CACHE BOOL "Enable to use less memory - at the expense of emulation
speed")
+ set(ENABLE_WINUAE_CPU 1
+ CACHE BOOL "Enable WinUAE CPU core")
+set(ENABLE_PORTAUDIO 0
-+CACHE BOOL "Enable building with portaudio to enable microphone input in
Falcon mode")
++CACHE BOOL "Enable building with PortAudio to enable microphone input in
Falcon mode")
+set(ENABLE_CAPSIMAGE 0
-+CACHE BOOL "Enable building with capsimage for using .IPF, .RAW and .CTR
disk images")
- set(ENABLE_DSP_EMU 1
- CACHE BOOL "Enable DSP 56k emulator for Falcon mode")
- set(ENABLE_TRACING 1
-@@ -125,15 +129,19 @@ if (NOT ENABLE_OSX_BUNDLE)
++CACHE BOOL "Enable building with CAPSImage for using .IPF, .RAW and .CTR
disk images")
++set(ENABLE_UI 0
++CACHE BOOL "Enable building the Python GTK+2 user interface, requires
GTK+2 bindings")
+
+ # Run-time checks with GCC "mudflap" etc features:
+ # - stack protection
+@@ -127,15 +133,19 @@ if (NOT ENABLE_OSX_BUNDLE)
endif(X11_FOUND)
endif()
@@ -38,9 +44,26 @@ $OpenBSD: patch-CMakeLists_txt,v 1.1.1.1
+ endif(CAPSIMAGE_FOUND)
+endif(ENABLE_CAPSIMAGE)
- #
- # CPP Definitions:
-@@ -344,17 +352,20 @@ else()
+ find_package(Udev)
+ if(UDEV_FOUND)
+@@ -302,10 +312,12 @@ add_subdirectory(src)
+ add_subdirectory(doc)
+ add_subdirectory(tools)
+
+-include(FindPythonInterp)
+-if(PYTHONINTERP_FOUND)
+- add_subdirectory(python-ui)
+-endif(PYTHONINTERP_FOUND)
++if(ENABLE_UI)
++ include(FindPythonInterp)
++ if(PYTHONINTERP_FOUND)
++ add_subdirectory(python-ui)
+
introducing cargo.port.mk module
Hi,
I started to work on a cargo.port.mk module, to help building ports
based on cargo/rust ecosystem.
The following diff adds:
- devel/cargo/cargo.port.mk: the module
- devel/cargo/files/modcargo-make-makesum: a configure helper
(generate metadata required by cargo for all crates)
It also changes devel/cargo itself to use the module. But due to cargo
nature, it isn't a good model for the module use...
A port will use MODCARGO_CRATES entries for declaring crates.
The module will:
- adds DISTFILES and using MASTER_SITES9 for downloading files
- at pre-configure stage:
- creating a cargo configuration file to override standard registry
(which requires network access) to a local directory at
${WRKSRC}/modcargo-crates
- moving all extracted crates inside the directory
- generating metadata for each crate (using a script helper):
basically a json file with sha256 of all files and sha256 of the
tgz.
- calling cargo binary with right parameters for build, install, test
(behaviour overridable).
I also added two custom targets (prefixed with modcargo-) to help
generating MODCARGO_CRATES entries.
Regarding devel/Cargo itself, I am now facing a problem: the make test
doesn't work well anymore (lot of tests are failing due to overriding of
package registry with a local directory). So I added a non-standard
target (test-full) which remove the cargo configuration file installed
by pre-configure, and as result it makes cargo to run and use the
network for building and testing the testsuite... I dunno if it is
acceptable or not. The standard "test" target still use no network, but
isn't able to run the whole testsuite.
Thanks for your feedback regarding the module.
--
Sebastien Marie
Index: Makefile
===
RCS file: /cvs/ports/devel/cargo/Makefile,v
retrieving revision 1.6
diff -u -p -r1.6 Makefile
--- Makefile13 Nov 2016 08:59:26 - 1.6
+++ Makefile13 Nov 2016 14:51:04 -
@@ -4,20 +4,12 @@ COMMENT = package manager for Rust langu
# cargo version
CARGO_VERSION =0.14.0
-# rust-install submodule version in cargo/src/rust-installer
-# see https://github.com/rust-lang/cargo/tree/${CARGO_VERSION}/src
-RUSTINSTALL_INDEX =4f994850808a572e2cc8d43f968893c8e942e9bf
-
-# crates.io commit for CARGO_VERSION
-# see https://github.com/rust-lang/crates.io-index/commits/master/ca/rg/cargo
-CRATESIO_INDEX = 9f8c3a65f70b2a5723e0d9cc0a32d531ea42da67
-
# cargo version used for bootstrapping
BOOTSTRAP_VERSION =0.14.0-20161112
-# registry index
-# see ${WRKDIR}/cargo-home/registry/index/github.com-${REGISTRY_INDEX}
-REGISTRY_INDEX = 1ecc6299db9ec823
+# rust-install submodule version in cargo/src/rust-installer
+# see https://github.com/rust-lang/cargo/tree/${CARGO_VERSION}/src
+RUSTINSTALL_INDEX =4f994850808a572e2cc8d43f968893c8e942e9bf
DISTNAME = cargo-${CARGO_VERSION}
@@ -32,96 +24,100 @@ MAINTAINER = Sebastien Marie https://github.com/rust-lang/
DISTFILES +=
cargo-${CARGO_VERSION}.tar.gz{cargo/archive/${CARGO_VERSION}.tar.gz}
DISTFILES +=
rust-installer-${RUSTINSTALL_INDEX}.tar.gz{rust-installer/archive/${RUSTINSTALL_INDEX}.tar.gz}
-DISTFILES +=
crates.io-index-${CRATESIO_INDEX}.tar.gz{crates.io-index/archive/${CRATESIO_INDEX}.tar.gz}
-
-# look at ${WRKDIR}/cargo-home/registry/src/github.com-${REGISTRY_INDEX}
-# for the list
-CRATES += advapi32-sys-0.2.0 # MIT
-CRATES += aho-corasick-0.5.3 # Unlicense/MIT
-CRATES += bitflags-0.1.1 # MIT/Apache-2.0
-CRATES += bitflags-0.7.0 # MIT/Apache-2.0
-CRATES += bufstream-0.1.2 # MIT/Apache-2.0 (test)
-CRATES += cfg-if-0.1.0# MIT/Apache-2.0
-CRATES += cmake-0.1.17# MIT/Apache-2.0
-CRATES += crossbeam-0.2.9 # MIT/Apache-2.0
-CRATES += curl-0.3.9 # MIT
-CRATES += curl-sys-0.2.4 # MIT
-CRATES += docopt-0.6.82 # Unlicense/MIT
-CRATES += env_logger-0.3.4# MIT/Apache-2.0
-CRATES += filetime-0.1.10 # MIT/Apache-2.0
-CRATES += flate2-0.2.14 # MIT/Apache-2.0
-CRATES += fs2-0.2.5 # MIT/Apache-2.0
-CRATES += gcc-0.3.35 # MIT/Apache-2.0
-CRATES += git2-0.4.4 # MIT/Apache-2.0
-CRATES += git2-curl-0.5.0 # MIT/Apache-2.0
-CRATES += glob-0.2.11 # MIT/Apache-2.0
-CRATES += hamcrest-0.1.1 # MIT/Apache-2.0 (test)
-CRATES += idna-0.1.0 # MIT/Apache-2.0
-CRATES += kernel32-sys-0.2.2 # MIT
-CRATES += lazy_static-0.2.1 # MIT
-CRATES += libc-0.2.17 # MIT/Apache-2.0
-CRATES +=
Re: UPDATE: textproc/lua-yaml 6.1
On Sun, Nov 13, 2016 at 04:31:40PM +1100, Jonathan Gray wrote: > Index: Makefile > === > RCS file: /cvs/ports/textproc/lua-yaml/Makefile,v Successfully tested with all Lua flavors. OK fcambus@
Re: UPDATE: textproc/py-yaml 3.12
On 11/13/16 06:33, Jonathan Gray wrote:
Index: Makefile
===
RCS file: /cvs/ports/textproc/py-yaml/Makefile,v
retrieving revision 1.14
diff -u -p -r1.14 Makefile
--- Makefile9 Dec 2015 18:26:47 - 1.14
+++ Makefile13 Nov 2016 05:15:05 -
@@ -2,10 +2,9 @@
COMMENT= YAML parser and emitter in Python
-MODPY_EGG_VERSION=3.11
+MODPY_EGG_VERSION=3.12
DISTNAME= PyYAML-${MODPY_EGG_VERSION}
PKGNAME= py-yaml-${MODPY_EGG_VERSION}
-REVISION= 1
CATEGORIES=textproc
HOMEPAGE= http://pyyaml.org/wiki/PyYAML
Index: distinfo
===
RCS file: /cvs/ports/textproc/py-yaml/distinfo,v
retrieving revision 1.4
diff -u -p -r1.4 distinfo
--- distinfo19 Aug 2014 14:25:11 - 1.4
+++ distinfo13 Nov 2016 05:15:12 -
@@ -1,2 +1,2 @@
-SHA256 (PyYAML-3.11.tar.gz) = w2yTiocuX/SUk4szsUqqFWy0OexnVI/Ks1Nbt4sIRug=
-SIZE (PyYAML-3.11.tar.gz) = 248685
+SHA256 (PyYAML-3.12.tar.gz) = WSdmxjAyB6IO/ERVh3eDItf3OxYb2ZTyJ62qNBuiEqs=
+SIZE (PyYAML-3.12.tar.gz) = 253011
Index: patches/patch-lib3_yaml_scanner_py
===
RCS file: patches/patch-lib3_yaml_scanner_py
diff -N patches/patch-lib3_yaml_scanner_py
--- patches/patch-lib3_yaml_scanner_py 1 Dec 2014 09:24:46 - 1.1
+++ /dev/null 1 Jan 1970 00:00:00 -
@@ -1,17 +0,0 @@
-$OpenBSD: patch-lib3_yaml_scanner_py,v 1.1 2014/12/01 09:24:46 jasper Exp $
-
-Security fix for CVE-2014-9130
-http://marc.info/?l=oss-security&m=141720508007010&w=2
-
lib3/yaml/scanner.py.orig Mon Dec 1 10:14:54 2014
-+++ lib3/yaml/scanner.py Mon Dec 1 10:15:21 2014
-@@ -299,7 +299,8 @@ class Scanner:
-
- # A simple key is required only if it is the first token in the
current
- # line. Therefore it is always allowed.
--assert self.allow_simple_key or not required
-+# http://marc.info/?l=oss-security&m=141720508007010&w=2
-+#assert self.allow_simple_key or not required
-
- # The next token might be a simple key. Let's save it's number and
- # position.
Index: patches/patch-lib_yaml_scanner_py
===
RCS file: patches/patch-lib_yaml_scanner_py
diff -N patches/patch-lib_yaml_scanner_py
--- patches/patch-lib_yaml_scanner_py 1 Dec 2014 09:24:46 - 1.1
+++ /dev/null 1 Jan 1970 00:00:00 -
@@ -1,17 +0,0 @@
-$OpenBSD: patch-lib_yaml_scanner_py,v 1.1 2014/12/01 09:24:46 jasper Exp $
-
-Security fix for CVE-2014-9130
-http://marc.info/?l=oss-security&m=141720508007010&w=2
-
lib/yaml/scanner.py.orig Wed Mar 26 19:54:13 2014
-+++ lib/yaml/scanner.pyMon Dec 1 10:15:36 2014
-@@ -299,7 +299,8 @@ class Scanner(object):
-
- # A simple key is required only if it is the first token in the
current
- # line. Therefore it is always allowed.
--assert self.allow_simple_key or not required
-+# http://marc.info/?l=oss-security&m=141720508007010&w=2
-+#assert self.allow_simple_key or not required
-
- # The next token might be a simple key. Let's save it's number and
- # position.
ok rpointel@
Re: UPDATE: devel/libyaml 0.1.7
On 11/13/16 06:28, Jonathan Gray wrote:
https://bitbucket.org/xi/libyaml/raw/6d5f97d2330147c286839bacfa0c66fac3992faf/announcement.msg
* Fixed segfault in yaml_string_write_handler.
* Fixed invalid simple key assertion.
* Fixed error handling in some examples (thank to Mathias Svensson).
* Removed obsolete VS project files.
Index: Makefile
===
RCS file: /cvs/ports/devel/libyaml/Makefile,v
retrieving revision 1.11
diff -u -p -r1.11 Makefile
--- Makefile11 Mar 2016 19:59:13 - 1.11
+++ Makefile13 Nov 2016 04:58:16 -
@@ -2,8 +2,7 @@
COMMENT= YAML 1.1 parser and emitter written in C
-DISTNAME= yaml-0.1.6
-REVISION= 1
+DISTNAME= yaml-0.1.7
PKGNAME= lib${DISTNAME}
CATEGORIES=devel
Index: distinfo
===
RCS file: /cvs/ports/devel/libyaml/distinfo,v
retrieving revision 1.5
diff -u -p -r1.5 distinfo
--- distinfo30 Mar 2014 06:59:49 - 1.5
+++ distinfo13 Nov 2016 04:59:16 -
@@ -1,2 +1,2 @@
-SHA256 (yaml-0.1.6.tar.gz) = faaXG0vQipht0qYTU7xCI2K9DtzGfX66rGjJX3QYJ0k=
-SIZE (yaml-0.1.6.tar.gz) = 503012
+SHA256 (yaml-0.1.7.tar.gz) = gIjkVyZKmLpFGpC4Zh/LT51vR49yZdSDIqGWzsJIByk=
+SIZE (yaml-0.1.7.tar.gz) = 527518
Index: patches/patch-src_scanner_c
===
RCS file: patches/patch-src_scanner_c
diff -N patches/patch-src_scanner_c
--- patches/patch-src_scanner_c 1 Dec 2014 08:48:51 - 1.4
+++ /dev/null 1 Jan 1970 00:00:00 -
@@ -1,21 +0,0 @@
-$OpenBSD: patch-src_scanner_c,v 1.4 2014/12/01 08:48:51 jasper Exp $
-
-Security fix for CVE-2014-9130
-https://marc.info/?l=oss-security&m=141715462623662&w=2
-
src/scanner.c.orig Thu Mar 27 05:54:02 2014
-+++ src/scanner.c Sat Nov 29 16:10:33 2014
-@@ -1106,13 +1106,6 @@ yaml_parser_save_simple_key(yaml_parser_t *parser)
- && parser->indent == (ptrdiff_t)parser->mark.column);
-
- /*
-- * A simple key is required only when it is the first token in the current
-- * line. Therefore it is always allowed. But we add a check anyway.
-- */
--
--assert(parser->simple_key_allowed || !required);/* Impossible. */
--
--/*
- * If the current position may start a simple key, save it.
- */
-
ok rpointel@
Re: [NEW] www/tbb improved, updated
attila writes: [snip] > Landry Breuil writes: >> So, more nits portswise only: > > Thanks a lot for this feedback. Attached is a tarball that attempts > to address both your and danj@'s concerns. > >> - meta/tbb/pkg/DESCR could use some more wording, as >> www/tbb/tor-browser/pkg/DESCR. > > All of the COMMENTs and pkg/DESCR files have been updated. > Naturally, after I posted I found a typo in a COMMENT. While in there I also rewrote tor-launcher/pkg/DESCR to be a little more informative. Updated tarball attached. Pax, -A -- http://haqistan.net/~attila | att...@stalphonsos.com | 0x62A729CF tbb605-bis.tgz Description: fix typos in last update
Re: net/kea: 1.1.0
Patrik Lundin writes: > Hello, > > See below for an update to net/kea from 1.0.0 to 1.1.0. Committed, thanks. [...] > This also brings up another question of mine: where to place logs. > > Currently the default setup creates logs in the following places: > /var/kea/kea.log ^^^ > /var/log/kea-ddns.log vs ^^^, weird... > /var/log/kea-dhcp4.log > /var/log/kea-dhcp6.log > > Of course the port does not do anything to setup rotation of these logs. Any > input how this should be handled? I guess you could put a newsyslog.conf example in pkg/README. [...] -- jca | PGP : 0x1524E7EE / 5135 92C1 AD36 5293 2BDF DDCC 0DFA 74AE 1524 E7EE
Re: [NEW] textproc/lua-lunamark
Frederic Cambus writes: > Hi ports@, > > Here is a new port: textproc/lua-lunamark > > I originally wanted to also ship the bundled tools but they depend on > the 'alt_getopt' module which doesn't work with Lua 5.3 and add a > dependency not otherwise useful for other ports. Same for tests, they > rely on those bundled tools and yet another module. So only packaging > the module, at least for now. > > Comments? OK? Yup > From DESCR: > > Lunamark is a Lua module for converting Markdown to other textual formats. > Currently HTML, dzslides, Docbook, ConTeXt, LaTeX, and Groff man are the > supported output formats. The markdown parser is written using a PEG > grammar and can also be modified by the user. > > The API is described at http://jgm.github.io/lunamark/doc/ > > -- jca | PGP : 0x1524E7EE / 5135 92C1 AD36 5293 2BDF DDCC 0DFA 74AE 1524 E7EE
Re: Swirc IRC client
On Fri, Sep 02, 2016 at 08:09:31PM +0100, Jeremie Courreges-Anglas wrote: > > I released a new version (v1.1+) with the help of your feedback. > > For details, consult: > > https://github.com/uhlin/swirc/blob/master/CHANGELOG.md > > > > I attach the updated port in this mail. Hopefully it's better now. > > But feel free to tweak it more... > > I think it is fine as is. Does anyone see other things to tweak, or > agrees with an import? Looks good to me, with a minor caveat: s/BSD 3 clause/BSD/ OK fcambus@ to import with this change in.
