[UPDATE] offlineimap v6.7.0.1

2016-06-08 Thread Remi Locherer
Hi

This is an update for offlineimap to version 6.7.0.1.

>From the announcement mail:
Since v7.* the sqlite database is the default cache format. However, all
the versions prior to v7.* suffers from a bug where the databases might
not be closed properly. Not all configurations actually suffer from this
bug (only the users with autorefresh enabled have reported issues).

Remi


Index: Makefile
===
RCS file: /cvs/ports/mail/offlineimap/Makefile,v
retrieving revision 1.33
diff -u -p -r1.33 Makefile
--- Makefile21 Mar 2016 14:39:27 -  1.33
+++ Makefile9 Jun 2016 06:16:23 -
@@ -2,8 +2,7 @@
 
 COMMENT=   powerful IMAP/Maildir synchronization and reader support
 
-MODPY_EGG_VERSION = 6.7.0
-REVISION = 0
+MODPY_EGG_VERSION = 6.7.0.1
 GH_ACCOUNT =   OfflineIMAP
 GH_PROJECT =   offlineimap
 GH_TAGNAME =   v${MODPY_EGG_VERSION}
Index: distinfo
===
RCS file: /cvs/ports/mail/offlineimap/distinfo,v
retrieving revision 1.21
diff -u -p -r1.21 distinfo
--- distinfo16 Mar 2016 00:04:16 -  1.21
+++ distinfo9 Jun 2016 06:16:23 -
@@ -1,2 +1,2 @@
-SHA256 (offlineimap-6.7.0.tar.gz) = 
xEb7Mb3KkMfbQUa5GK0/oF9t9TYqTMlh32p3J6iqwhA=
-SIZE (offlineimap-6.7.0.tar.gz) = 678649
+SHA256 (offlineimap-6.7.0.1.tar.gz) = 
AOkf94IhdQbdkfUC0JTvDaoncyz8aMkUAprvwcU2Qvs=
+SIZE (offlineimap-6.7.0.1.tar.gz) = 678866



UPDATE: mail/msmtp-1.6.5

2016-06-08 Thread Gleydson Soares
update msmtp to 1.6.5.

This release supports SHA256 fingerprints for tls_fingerprint, and
mark both SHA1 and MD5 as deprecated.

OK?

Index: Makefile
===
RCS file: /cvs/ports/mail/msmtp/Makefile,v
retrieving revision 1.42
diff -u -p -r1.42 Makefile
--- Makefile27 Apr 2016 10:40:15 -  1.42
+++ Makefile9 Jun 2016 02:36:20 -
@@ -2,7 +2,7 @@
 
 COMMENT =  SMTP plugin for MUAs
 
-DISTNAME = msmtp-1.6.4
+DISTNAME = msmtp-1.6.5
 CATEGORIES =   mail
 
 HOMEPAGE = http://msmtp.sourceforge.net/
Index: distinfo
===
RCS file: /cvs/ports/mail/msmtp/distinfo,v
retrieving revision 1.28
diff -u -p -r1.28 distinfo
--- distinfo27 Apr 2016 10:40:15 -  1.28
+++ distinfo9 Jun 2016 02:36:20 -
@@ -1,2 +1,2 @@
-SHA256 (msmtp-1.6.4.tar.xz) = m0nAIqVEDUG2eCyX7yl30DRsPa4Fqog2JDqZU+mC0c0=
-SIZE (msmtp-1.6.4.tar.xz) = 282840
+SHA256 (msmtp-1.6.5.tar.xz) = dqDWBpPH5l0MehLwHTAIgtKAseG+AgL1RzCuRNRKUAY=
+SIZE (msmtp-1.6.5.tar.xz) = 283284



Re: update to py-flask-0.11.1

2016-06-08 Thread frantisek holop
Stuart Henderson, 08 Jun 2016 21:53:
> For a port with a maintainer, this sort of thing is usually up
> to them, somebody familiar with the particular software is likely
> to have a better idea of whether it's a good idea to update
> quickly, or hold off for a while.

i agree that it is up to the maintainer.

well, to be entirely honest, it is deployed using
virtualenv and pip, i use the port only for local
development...

mitsuhiko pledged "no big changes" to not to cause
pain to developers and maintainers but now i am not
sure what counts as big in his vocabulary.

c'est la vie, can't please everyone.  people are
definitely happier that flask did not become abandonware.

-f
-- 
mips => meaningless index of processor speed



pledge par2cmdline

2016-06-08 Thread Carlin Bingham
This adds pledge to par2 and its utilities.

The 'create' command needs cpath and wpath to create and write the pars.

The 'repair' command needs cpath to rename damaged files and delete
partial files, and wpath to write the recovered files (at least to
begin with).

The 'verify' command may need cpath to delete files if -p was passed.

'repair' opens all the files it is going to write before it begins
performing the recovery so we can drop wpath at that point. It needs to
hold on to cpath as it deletes any partially reconstructed files if it
encounters an error.

The 'verify' command calls the same function as 'repair' but won't hit
the codepath with the late pledge call.

All the tests pass, but that doesn't mean much...


This patch does the pledge needed by create/repair up front and then
pledges again if running verify, this way we can pledge before the
command line parsing. And does a different pledge for verify depending
on whether -p is set.


--
Carlin



Index: archivers/par2cmdline/Makefile
===
RCS file: /cvs/ports/archivers/par2cmdline/Makefile,v
retrieving revision 1.11
diff -u -p -u -r1.11 Makefile
--- archivers/par2cmdline/Makefile  5 Oct 2015 16:50:14 -   1.11
+++ archivers/par2cmdline/Makefile  8 Jun 2016 11:56:55 -
@@ -5,6 +5,7 @@ COMMENT =   command line implementation of
 V =0.6.14
 DISTNAME = par2cmdline-$V
 DISTFILES =${DISTNAME}{v$V}.tar.gz
+REVISION = 0
 
 CATEGORIES =   archivers
 
@@ -13,6 +14,7 @@ HOMEPAGE =https://github.com/BlackIkeEa
 # GPLv2+
 PERMIT_PACKAGE_CDROM = Yes
 
+# uses pledge()
 WANTLIB =  c m stdc++
 
 MAINTAINER =   Mikolaj Kucharski 
Index: archivers/par2cmdline/patches/patch-configure_ac
===
RCS file: archivers/par2cmdline/patches/patch-configure_ac
diff -N archivers/par2cmdline/patches/patch-configure_ac
--- /dev/null   1 Jan 1970 00:00:00 -
+++ archivers/par2cmdline/patches/patch-configure_ac8 Jun 2016 11:56:55 
-
@@ -0,0 +1,11 @@
+$OpenBSD$
+--- configure.ac.orig  Wed Jun  8 23:30:46 2016
 configure.ac   Wed Jun  8 23:31:20 2016
+@@ -56,6 +56,7 @@ dnl Checks for library functions.
+ AC_FUNC_MEMCMP
+ AC_CHECK_FUNCS([stricmp] [strcasecmp])
+ AC_CHECK_FUNCS([strchr] [memcpy])
++AC_CHECK_FUNCS([pledge])
+ 
+ AC_CHECK_FUNCS([getopt] [getopt_long])
+ 
Index: archivers/par2cmdline/patches/patch-par1repairer_cpp
===
RCS file: archivers/par2cmdline/patches/patch-par1repairer_cpp
diff -N archivers/par2cmdline/patches/patch-par1repairer_cpp
--- /dev/null   1 Jan 1970 00:00:00 -
+++ archivers/par2cmdline/patches/patch-par1repairer_cpp8 Jun 2016 
11:56:55 -
@@ -0,0 +1,18 @@
+$OpenBSD$
+--- par1repairer.cpp.orig  Wed Jun  8 23:41:11 2016
 par1repairer.cpp   Wed Jun  8 23:42:01 2016
+@@ -157,6 +157,14 @@ Result Par1Repairer::Process(const CommandLine &comman
+ if (!CreateTargetFiles())
+   return eFileIOError;
+ 
++#ifdef HAVE_PLEDGE
++if (pledge("stdio rpath cpath", NULL) == -1)
++{
++  cerr << "pledge failed" << endl;
++  return eLogicError;
++}
++#endif
++
+ // Work out which data blocks are available, which need to be 
recreated, 
+ // and compute the appropriate Reed Solomon matrix.
+ if (!ComputeRSmatrix())
Index: archivers/par2cmdline/patches/patch-par2cmdline_cpp
===
RCS file: archivers/par2cmdline/patches/patch-par2cmdline_cpp
diff -N archivers/par2cmdline/patches/patch-par2cmdline_cpp
--- /dev/null   1 Jan 1970 00:00:00 -
+++ archivers/par2cmdline/patches/patch-par2cmdline_cpp 8 Jun 2016 11:56:55 
-
@@ -0,0 +1,45 @@
+$OpenBSD$
+--- par2cmdline.cpp.orig   Wed Jun  8 23:31:42 2016
 par2cmdline.cppWed Jun  8 23:38:36 2016
+@@ -34,6 +34,14 @@ int main(int argc, char *argv[])
+   _CrtSetDbgFlag(_CrtSetDbgFlag(_CRTDBG_REPORT_FLAG) | _CRTDBG_ALLOC_MEM_DF | 
/*_CRTDBG_CHECK_CRT_DF | */_CRTDBG_DELAY_FREE_MEM_DF | _CRTDBG_LEAK_CHECK_DF);
+ #endif
+ 
++#ifdef HAVE_PLEDGE
++  if (pledge("stdio rpath wpath cpath", NULL) == -1)
++  {
++cerr << "pledge failed" << endl;
++return eLogicError;
++  }
++#endif
++
+   // Parse the command line
+   CommandLine *commandline = new CommandLine;
+ 
+@@ -55,6 +63,26 @@ int main(int argc, char *argv[])
+ break;
+   case CommandLine::opVerify:
+ {
++#ifdef HAVE_PLEDGE
++  if (!commandline->GetPurgeFiles())
++  {
++if (pledge("stdio rpath", NULL) == -1)
++{
++  cerr << "pledge failed" << endl;
++  result = eLogicError;
++  break;
++}
++  }
++  else
++  {
++if (pledge("stdio rpath cpath", NULL) == -1)
++{
++  cerr << "pledg

Re: NEW: sysutils/vifm

2016-06-08 Thread Rafael Sadowski
On Wed Jun 08, 2016 at 09:34:50PM +0200, Landry Breuil wrote:
> On Tue, Jun 07, 2016 at 09:28:37PM +0200, Rafael Sadowski wrote:
> > Hi ports@ and vifm friends,
> > 
> > here is a third and last try to push vifm in ports tree.
> > 
> > port core features:
> > - The same as: http://marc.info/?l=openbsd-ports&m=145647165914163&w=2
> > - new: remove popen(2) call and replace with fork(2)(execl(3)
> > 
> > pkg/DESCR:
> > 
> > Vifm is a two panel ncurses based vi[m] like file manager. If you use vi,
> > vifm gives you complete keyboard control over your files without having
> > to learn a new set of commands. It goes not just about vi[m] like
> > keybindings, but also about modes, options, registers, commands and
> > other things you might already like in vi[m].
> > 
> > OK, Comments?
> 
> Has all the failure/risky cases that were reported in the last thread
> tested/taken care of now ?
> 
> Landry

Of course, I fixed all failure/risky cases and yes I tested it well. I
would have thought that was patently obvious.  I'll send fork/execl
replacement patch upstream.

Rafael



Re: update to py-flask-0.11.1

2016-06-08 Thread Stuart Henderson
On 2016/06/08 22:41, Daniel Jakots wrote:
> On Wed, 8 Jun 2016 22:21:20 +0200, frantisek holop 
> wrote:
> 
> > Daniel Jakots, 08 Jun 2016 21:01:
> > > Previously, last stable flask release was published on 14 Jun 2013
> > > and then 10 days ago they finally released a new one. Yesterday they
> > > released a bug fix release, here's a diff to update to this one.  
> > 
> > it is nice to see a port update so fast, but flask
> > being "stable" for so long, i think we could wait a bit
> > until the "dust settles a bit".  a wholy new test
> > framework and other questionable changes (like click,
> > the stupid theme error), it will be interesting to see
> > how the flask community will respond on the longer
> > run...  i know we won't be upgrading in production
> > for a while.
> 
> Well, I think the best for the ports tree is to have up-to-date
> software, not to produce artificial latency between upstream and us
> whether someone (btw, who decides?) like or not what they did.

For a port with a maintainer, this sort of thing is usually up
to them, somebody familiar with the particular software is likely
to have a better idea of whether it's a good idea to update
quickly, or hold off for a while.

For example, for many ports it's often a good idea to wait a release
or two after a release that has major changes, to wait for upstream to
unbreak things ;)

> One solution would be to have one newer release (0.11.x) and an older
> release, as they planned to release a bugfix release (0.10.2), like we
> do for django but I don't know if we want to do that.

This sometimes makes sense where it's a single port that is
involved, but where you have a chain of depencies involved it can
get rather complicated..



Re: update to py-flask-0.11.1

2016-06-08 Thread Daniel Jakots
On Wed, 8 Jun 2016 22:21:20 +0200, frantisek holop 
wrote:

> Daniel Jakots, 08 Jun 2016 21:01:
> > Previously, last stable flask release was published on 14 Jun 2013
> > and then 10 days ago they finally released a new one. Yesterday they
> > released a bug fix release, here's a diff to update to this one.  
> 
> it is nice to see a port update so fast, but flask
> being "stable" for so long, i think we could wait a bit
> until the "dust settles a bit".  a wholy new test
> framework and other questionable changes (like click,
> the stupid theme error), it will be interesting to see
> how the flask community will respond on the longer
> run...  i know we won't be upgrading in production
> for a while.

Well, I think the best for the ports tree is to have up-to-date
software, not to produce artificial latency between upstream and us
whether someone (btw, who decides?) like or not what they did.

One solution would be to have one newer release (0.11.x) and an older
release, as they planned to release a bugfix release (0.10.2), like we
do for django but I don't know if we want to do that.



Re: update to py-flask-0.11.1

2016-06-08 Thread frantisek holop
Daniel Jakots, 08 Jun 2016 21:01:
> Previously, last stable flask release was published on 14 Jun 2013 and
> then 10 days ago they finally released a new one. Yesterday they
> released a bug fix release, here's a diff to update to this one.

it is nice to see a port update so fast, but flask
being "stable" for so long, i think we could wait a bit
until the "dust settles a bit".  a wholy new test
framework and other questionable changes (like click,
the stupid theme error), it will be interesting to see
how the flask community will respond on the longer
run...  i know we won't be upgrading in production
for a while.

-f
-- 
our world: a 12735 km diameter spherical pile of dirt.



Re: [NEW] archivers/snappy

2016-06-08 Thread Stuart Henderson
On 2016/06/08 13:13, Frederic Cambus wrote:
> On Tue, Jun 07, 2016 at 10:11:52PM +0100, Stuart Henderson wrote:
> 
> > autoconf picks up gtest and gflags, please either add BUILD_DEPENDS
> > on these, or tell autoconf not to use them.
> > 
> > ..
> > checking for 'gtest-config'... checking for gtest-config...
> > /usr/local/bin/gtest-config
> > /usr/local/bin/gtest-config
> > checking for Google Test... yes
> > checking for pkg-config... /usr/bin/pkg-config
> > checking pkg-config is at least version 0.9.0... yes
> > checking for gflags... no
> 
> Added CONFIGURE_ARGS += --disable-gtest to disable using gtest.
> 
> Regarding gflags, it's not used unless explicitely enabled with the
> --with-gflags configure argument, which we don't enable.
> 
> New tarball attached.
> 

OK with me.



Re: NEW: sysutils/vifm

2016-06-08 Thread Landry Breuil
On Tue, Jun 07, 2016 at 09:28:37PM +0200, Rafael Sadowski wrote:
> Hi ports@ and vifm friends,
> 
> here is a third and last try to push vifm in ports tree.
> 
> port core features:
> - The same as: http://marc.info/?l=openbsd-ports&m=145647165914163&w=2
> - new: remove popen(2) call and replace with fork(2)(execl(3)
> 
> pkg/DESCR:
> 
> Vifm is a two panel ncurses based vi[m] like file manager. If you use vi,
> vifm gives you complete keyboard control over your files without having
> to learn a new set of commands. It goes not just about vi[m] like
> keybindings, but also about modes, options, registers, commands and
> other things you might already like in vi[m].
> 
> OK, Comments?

Has all the failure/risky cases that were reported in the last thread
tested/taken care of now ?

Landry



update to py-flask-0.11.1

2016-06-08 Thread Daniel Jakots
Hi,

Previously, last stable flask release was published on 14 Jun 2013 and
then 10 days ago they finally released a new one. Yesterday they
released a bug fix release, here's a diff to update to this one.

During the build there's a message:

> Warning: Flask themes unavailable.  Building with default theme
> If you want the Flask themes, run this command and build again:
> 
>   git submodule update --init

So far I just ignored it. Any opinion about it?

Other comments? OK?

Cheers,
Daniel

Index: Makefile
===
RCS file: /cvs/ports/www/py-flask/Makefile,v
retrieving revision 1.18
diff -u -p -r1.18 Makefile
--- Makefile16 Apr 2016 19:06:26 -  1.18
+++ Makefile8 Jun 2016 18:58:10 -
@@ -2,36 +2,36 @@
 
 COMMENT =  microframework based on Werkzeug and Jinja 2
 
-MODPY_EGG_VERSION =0.10.1
-REVISION = 2
-DISTNAME = Flask-${MODPY_EGG_VERSION}
-PKGNAME =  py-${DISTNAME:L}
+MODPY_EGG_VERSION =0.11.1
+DISTNAME = Flask-${MODPY_EGG_VERSION}
+PKGNAME =  py-${DISTNAME:L}
 
-CATEGORIES =   www devel
+CATEGORIES =   www devel
 
-HOMEPAGE = http://flask.pocoo.org/
+HOMEPAGE = http://flask.pocoo.org/
 
 # BSD
 PERMIT_PACKAGE_CDROM = Yes
 
-MODULES =  lang/python
-
-MODPY_PI = Yes
+MODULES =  lang/python
+MODPY_PI = Yes
 MODPY_SETUPTOOLS = Yes
 
-FLAVORS =  python3
+FLAVORS =  python3
 FLAVOR ?=
 
-RUN_DEPENDS =  devel/py-blinker${MODPY_FLAVOR} \
-   www/py-itsdangerous${MODPY_FLAVOR} \
-   www/py-jinja2${MODPY_FLAVOR}>=2.4 \
-   www/py-werkzeug${MODPY_FLAVOR}>=0.7
-BUILD_DEPENDS =textproc/py-sphinx${MODPY_FLAVOR} \
-   www/py-itsdangerous${MODPY_FLAVOR} \
-   www/py-werkzeug${MODPY_FLAVOR}>=0.7
-TEST_DEPENDS = ${RUN_DEPENDS}
+RUN_DEPENDS =  devel/py-blinker${MODPY_FLAVOR} \
+   www/py-itsdangerous${MODPY_FLAVOR} \
+   www/py-jinja2${MODPY_FLAVOR} \
+   www/py-werkzeug${MODPY_FLAVOR} \
+   devel/py-click${MODPY_FLAVOR}
+BUILD_DEPENDS =textproc/py-sphinx${MODPY_FLAVOR} \
+   www/py-itsdangerous${MODPY_FLAVOR} \
+   www/py-werkzeug${MODPY_FLAVOR}
+TEST_DEPENDS = ${RUN_DEPENDS} \
+   devel/py-test${MODPY_FLAVOR}
 
-MAKE_ENV = PYTHONPATH="${WRKSRC}" 
SPHINXBUILD=${LOCALBASE}/bin/sphinx-build${MODPY_BIN_SUFFIX}
+MAKE_ENV = PYTHONPATH="${WRKSRC}" 
SPHINXBUILD=${LOCALBASE}/bin/sphinx-build${MODPY_BIN_SUFFIX}
 
 post-build:
@cd ${WRKSRC}/docs && ${SETENV} ${MAKE_ENV} ${MAKE_PROGRAM} html
@@ -43,6 +43,11 @@ post-install:
${INSTALL_DATA_DIR} ${PREFIX}/share/examples/${MODPY_PY_PREFIX}flask
cd ${WRKSRC}/examples && pax -rw * \
${PREFIX}/share/examples/${MODPY_PY_PREFIX}flask
-   rm 
${PREFIX}/share/examples/${MODPY_PY_PREFIX}flask/persona/{static/,}.DS_Store
+.if ${FLAVOR:Mpython3}
+   mv ${PREFIX}/bin/flask ${PREFIX}/bin/flask${MODPY_BIN_SUFFIX}
+.endif
+
+do-test:
+   cd ${WRKSRC} && ${MODPY_BIN} -m pytest tests examples
 
 .include 
Index: distinfo
===
RCS file: /cvs/ports/www/py-flask/distinfo,v
retrieving revision 1.6
diff -u -p -r1.6 distinfo
--- distinfo25 Dec 2013 18:45:12 -  1.6
+++ distinfo8 Jun 2016 18:58:10 -
@@ -1,2 +1,2 @@
-SHA256 (Flask-0.10.1.tar.gz) = TIOCn/g9QIteHUmVRyJlQR0sQUESKY8utLNZ2eRWM3M=
-SIZE (Flask-0.10.1.tar.gz) = 544247
+SHA256 (Flask-0.11.1.tar.gz) = tHE/K/uevClmuKSZA64NOYR4HVyHhZHPL3tITSh1aw4=
+SIZE (Flask-0.11.1.tar.gz) = 564993
Index: patches/patch-docs_conf_py
===
RCS file: /cvs/ports/www/py-flask/patches/patch-docs_conf_py,v
retrieving revision 1.1
diff -u -p -r1.1 patch-docs_conf_py
--- patches/patch-docs_conf_py  16 Apr 2016 19:06:26 -  1.1
+++ patches/patch-docs_conf_py  8 Jun 2016 18:58:10 -
@@ -2,14 +2,13 @@ $OpenBSD: patch-docs_conf_py,v 1.1 2016/
 
 Prevent build from calling out to the internet.
 
 docs/conf.py.orig  Fri Apr 15 21:23:36 2016
-+++ docs/conf.py   Fri Apr 15 21:23:50 2016
-@@ -26,7 +26,7 @@ sys.path.append(os.path.abspath('.'))
- 
- # Add any Sphinx extension module names here, as strings. They can be 
extensions
+--- docs/conf.py.orig  Wed Jun  8 20:51:57 2016
 docs/conf.py   Wed Jun  8 20:52:21 2016
+@@ -28,7 +28,6 @@ sys.path.append(os.path.abspath('.'))
  # coming with Sphinx (named 'sphinx.ext.*') or your custom ones.
--extensions = ['sphinx.ext.autodoc', 'sphinx.ext.intersphinx',
-+extensions = ['sphinx.ext.autodoc',
-   'flaskdocext']
+ extensions = [
+ 'sphinx.ext.autodoc',
+-'sphinx.ext.intersphinx',
+ 'flaskdocext'
+ ]
  
- # Add any paths that contain templates here, re

Re: sysutils/apcupsd with USB cable broken in latest snap

2016-06-08 Thread Johan Huldtgren

On 6/8/16 01:41, Kirill Bychkov wrote:

On Wed, June 8, 2016 03:33, Johan Huldtgren wrote:
[...]


ok, on the off chance that this was an amd64 vs i386 issue (unlikely but
figured it couldn't hurt to try) I installed the latest amd64 snap on a
different host and updated ports (I had apcupsd installed here in client
mode), attached the UPS and swapped the config file to the server one,
but alas the results are the same. Must be an issue with my UPS and the
new code I guess.


Just a guess but may be you need to use modbus driver instead of usb?


Using modbus via usb didn't work, however this model has both a usb
port and an rs232 serial port[1]. Using the rs232 port together with
the 940-0625A cable (rs232 <-> db9) and connecting to a serial port on
another server I can get apcupsd to work. So I have a work around,
that said it seems it no longer works with usb, I tried all
permutations I could imagine of physical cables, UPSCABLE, UPSTYPE,
and DEVICE; but if connected via USB (even if from the rs232 port via
a db9 <-> usb adapter) I never get apcupsd to communicate with the
UPS. I suspect the errors which could be seen yesterday in the apctest
and apcupsd -d output might be relevant but as I said then I'm not
sure how to deal with them.  apctest succeeds now and none of the
errors seen with the USB cable are evident when using a serial
connection.

thanks,

.jh

[1] https://media.cablesandkits.com/p/SMT2200RM2Uc.jpg



Re: Need a review for port of games/bastet (tetris like)

2016-06-08 Thread Jeremie Courreges-Anglas
Jeremie Courreges-Anglas  writes:

> Solène RAPENNE  writes:
>
>> Hello
>>
>> Jeremie Courreges-Anglas writes:
>>
>>> The 2015083000 part in 0.43.1.2015083000 was to make clear that it's the
>>> 0.43.1 release plus a few patches.  I don't think we actually care.
>>>
>>
>> I see, I thought it has some impact when fetching the source.
>>
>>>
>>> Patching is fine with tangled Makefiles, but we tend to avoid patches
>>> when MAKE_FLAGS is enough.
>>>
>>
>> I kept the Makefile patch but I could do in the port Makefile as
>> before. Rafael Sadowski answered that I should reuse the original
>> Makefile with some patch. Which solution is better ?
>
> *shrug*
>
 The game works fine on 5.9 amd64. Is the Enter key inactive in the
 menu or while playing ?
>>>
>>> While playing.
>>
>> Same problem here, when remapping the keys it works, maybe the default
>> Enter key isn't correct in the source code or incorrect for OpenBSD ?
>
> No idea. :)
>
>>>
>>> Could you send an updated tarball?  (Not just the Makefile, please.)
>>
>> Done. I had to get a computer with -current :)
>
> Thanks.  Here's an updated tarball that adds -Wno-unused-local-typedef
> to CXXFLAGS, so that we can spot potential *useful* warnings.
>
> I think the port is fine as is and could be imported.  Can I get another
> review?

Imported, thanks.

-- 
jca | PGP : 0x1524E7EE / 5135 92C1 AD36 5293 2BDF  DDCC 0DFA 74AE 1524 E7EE



UPDATE: MongoDB 3.2.7

2016-06-08 Thread Andrew Aldridge

Also updates some URLs that redirect. All tests pass.

diff --git a/Makefile b/Makefile
index 86e95b6..b45d4e3 100644
--- a/Makefile
+++ b/Makefile
@@ -8,12 +8,11 @@ DPB_PROPERTIES = parallel

 COMMENT =  scalable, high-performance document-oriented database

-DISTNAME = mongodb-src-r3.2.6
-REVISION = 0
+DISTNAME = mongodb-src-r3.2.7
 PKGNAME =  ${DISTNAME:S/src-r//}
 CATEGORIES =   databases

-HOMEPAGE = http://www.mongodb.org/
+HOMEPAGE = https://www.mongodb.com/

 # mongodb itself: AGPLv3
 # client/utils:   Apache 2.0
@@ -24,7 +23,7 @@ WANTLIB += boost_regex-mt boost_system-mt 
boost_thread-mt c crypto

 WANTLIB += execinfo kvm m pcap pcre pcrecpp pthread ssl yaml-cpp
 WANTLIB += z

-MASTER_SITES = http://downloads.mongodb.org/src/
+MASTER_SITES = https://fastdl.mongodb.org/src/

 MODULES =  gcc4 \
devel/scons \
diff --git a/distinfo b/distinfo
index 1139d2f..553ce2d 100644
--- a/distinfo
+++ b/distinfo
@@ -1,2 +1,2 @@
-SHA256 (mongodb-src-r3.2.6.tar.gz) = 
BBWptQP2LkDSuof1VbVTdXoU+sKB0dalg9jYgLhyCSE=

-SIZE (mongodb-src-r3.2.6.tar.gz) = 29750170
+SHA256 (mongodb-src-r3.2.7.tar.gz) = 
zYlnavb5dWFwCgi1mcKH+2OPFKahAZ75Fnz1XtajlSo=

+SIZE (mongodb-src-r3.2.7.tar.gz) = 28494513


--
-- Andrew Aldridgediff --git a/Makefile b/Makefile
index 86e95b6..b45d4e3 100644
--- a/Makefile
+++ b/Makefile
@@ -8,12 +8,11 @@ DPB_PROPERTIES = parallel
 
 COMMENT =	scalable, high-performance document-oriented database
 
-DISTNAME =	mongodb-src-r3.2.6
-REVISION =	0
+DISTNAME =	mongodb-src-r3.2.7
 PKGNAME =	${DISTNAME:S/src-r//}
 CATEGORIES =	databases
 
-HOMEPAGE =	http://www.mongodb.org/
+HOMEPAGE =	https://www.mongodb.com/
 
 # mongodb itself: AGPLv3
 # client/utils:   Apache 2.0
@@ -24,7 +23,7 @@ WANTLIB += boost_regex-mt boost_system-mt boost_thread-mt c crypto
 WANTLIB += execinfo kvm m pcap pcre pcrecpp pthread ssl yaml-cpp
 WANTLIB += z
 
-MASTER_SITES =	http://downloads.mongodb.org/src/
+MASTER_SITES =	https://fastdl.mongodb.org/src/
 
 MODULES =	gcc4 \
 		devel/scons \
diff --git a/distinfo b/distinfo
index 1139d2f..553ce2d 100644
--- a/distinfo
+++ b/distinfo
@@ -1,2 +1,2 @@
-SHA256 (mongodb-src-r3.2.6.tar.gz) = BBWptQP2LkDSuof1VbVTdXoU+sKB0dalg9jYgLhyCSE=
-SIZE (mongodb-src-r3.2.6.tar.gz) = 29750170
+SHA256 (mongodb-src-r3.2.7.tar.gz) = zYlnavb5dWFwCgi1mcKH+2OPFKahAZ75Fnz1XtajlSo=
+SIZE (mongodb-src-r3.2.7.tar.gz) = 28494513


Re: Need a review for port of games/bastet (tetris like)

2016-06-08 Thread Jeremie Courreges-Anglas
Solène RAPENNE  writes:

> Hello
>
> Jeremie Courreges-Anglas writes:
>
>> The 2015083000 part in 0.43.1.2015083000 was to make clear that it's the
>> 0.43.1 release plus a few patches.  I don't think we actually care.
>>
>
> I see, I thought it has some impact when fetching the source.
>
>>
>> Patching is fine with tangled Makefiles, but we tend to avoid patches
>> when MAKE_FLAGS is enough.
>>
>
> I kept the Makefile patch but I could do in the port Makefile as
> before. Rafael Sadowski answered that I should reuse the original
> Makefile with some patch. Which solution is better ?

*shrug*

>>> The game works fine on 5.9 amd64. Is the Enter key inactive in the
>>> menu or while playing ?
>>
>> While playing.
>
> Same problem here, when remapping the keys it works, maybe the default
> Enter key isn't correct in the source code or incorrect for OpenBSD ?

No idea. :)

>>
>> Could you send an updated tarball?  (Not just the Makefile, please.)
>
> Done. I had to get a computer with -current :)

Thanks.  Here's an updated tarball that adds -Wno-unused-local-typedef
to CXXFLAGS, so that we can spot potential *useful* warnings.

I think the port is fine as is and could be imported.  Can I get another
review?



bastet.tgz
Description: Binary data

-- 
jca | PGP : 0x1524E7EE / 5135 92C1 AD36 5293 2BDF  DDCC 0DFA 74AE 1524 E7EE


Re: windowmaker diff

2016-06-08 Thread David Coppa
On Tue, 07 Jun 2016, Reyk Floeter wrote:

> On Tue, Jun 07, 2016 at 08:48:26PM +0200, David Coppa wrote:
> > On Tue, Jun 7, 2016 at 8:35 PM, Reyk Floeter  wrote:
> > > On Tue, Jun 07, 2016 at 08:23:01PM +0200, Reyk Floeter wrote:
> > >> On Tue, Jun 07, 2016 at 05:27:51PM +0200, David Coppa wrote:
> > >> > Hi Reyk,
> > >> >
> > >> > Since I've just found (by reading your howto about the Lenovo Thinkpad
> > >> > X1 Carbon) that you're using Window Maker...
> > >> > Could you please test the attached diff that updates our windowmaker
> > >> > port to its latest release, 0.95.7?
> > >> >
> > >> > Ciao!
> > >> > David
> > >>
> > >> Sure!
> > >>
> > >
> > > It compiles, installed, but one annoying thing is that window-resize
> > > seems to be broken ('Maximize active window' gives strange results and
> > > covers the dock)
> > >
> > > There might be other issues.
> > 
> > Can you try starting from scratch with a clean environment?
> > 
> > I mean:
> > 
> > $ mv ~/GNUstep ~/GNUstep.old
> > 
> 
> Yes, that helped.
> 
> A few other things have changed (like the default menu, in a negative
> way hiding xterm and Firefox somewhere in a submenu).  Maximization
> now includes the space behind the dock - I have to get used to this.
> 
> I also don't like the new "jumping" icons.  They should focus on
> modernizing wmaker (eg. by adding support for DPI scaling) instead
> bloating it with gimmicks (11 different ways of maximization?!).
> But there is a chance that something will happen now ;)
> 
> After all, I think the ports update is OK.

Widening the audience to ports@

Here's a new version of the diff.
I've stolen some useful patches from FreeBSD, and fixed a time_t
issue.

Maybe it's the right time to update our prehistoric port of Window
Maker...

If you're a wmaker user, please test!

Ciao,
David

Index: Makefile
===
RCS file: /cvs/ports/x11/windowmaker/Makefile,v
retrieving revision 1.93
diff -u -p -u -p -r1.93 Makefile
--- Makefile11 Mar 2016 20:28:33 -  1.93
+++ Makefile8 Jun 2016 14:16:50 -
@@ -3,14 +3,15 @@
 COMMENT-main=  window manager that emulates NEXTSTEP(tm)
 COMMENT-lang=  language subpackage for Window Maker
 
-V= 0.92.0
+V =0.95.7
 DISTNAME=  WindowMaker-${V}
 PKGNAME-main=  ${DISTNAME:L}
-REVISION-main= 56
 FULLPKGNAME-lang=  windowmaker-lang-${V}
-REVISION-lang= 5
 
-SHARED_LIBS += wraster  5.0  # 4.0
+SHARED_LIBS +=  WINGs 0.0 # 2.1
+SHARED_LIBS +=  WMaker0.0 # 1.1
+SHARED_LIBS +=  WUtil 0.0 # 3.0
+SHARED_LIBS +=  wraster   5.1 # 4.1
 
 CATEGORIES=x11 x11/windowmaker
 
@@ -19,22 +20,27 @@ HOMEPAGE=   http://windowmaker.org/
 # GPLv2+
 PERMIT_PACKAGE_CDROM=  Yes
 
-WANTLIB += X11 Xext Xft Xinerama Xpm Xrender c expat fontconfig
-WANTLIB += freetype jpeg m png pthread-stubs tiff gif xcb z
+WANTLIB += ICE SM X11 Xmu Xext Xft Xinerama Xpm Xrandr Xrender
+WANTLIB += Xt c expat fontconfig freetype gif jpeg kvm m png
+WANTLIB += pthread pthread-stubs tiff xcb z
 
 MASTER_SITES=  ${MASTER_SITE_WINDOWMAKER:=source/release/}
-EXTRACT_SUFX=  .tar.bz2
 
 NO_TEST=   Yes
 SEPARATE_BUILD=Yes
 CONFIGURE_STYLE=   gnu
-CONFIGURE_ARGS+=   --enable-static \
+CONFIGURE_ARGS+=   --disable-magick \
+   --disable-webp \
+   --enable-randr \
+   --enable-static \
--enable-xinerama \
-   --with-datadir="${LOCALBASE}/share/WindowMaker" \
-   --with-nlsdir="${LOCALBASE}/share/locale"
+   --localedir="${LOCALBASE}/share/locale"
 
-CONFIGURE_ENV= CPPFLAGS="-I${LOCALBASE}/include" 
LIBS="-L${LOCALBASE}/lib" \
-   LINGUAS='be bg bs ca cs da de el es et fi fr gl hr hu 
it ja ko ms nl no pl pt ro ru sk sv tr zh_CN zh_TW'
+CONFIGURE_ENV= CPPFLAGS="-I${X11BASE}/include -I${LOCALBASE}/include" \
+   LIBS="-L${X11BASE}/lib -L${LOCALBASE}/lib" \
+   LINGUAS='*' \
+   ac_cv_lib_exif_exif_data_new_from_file=no \
+   wm_cv_func_secure_getenv=no
 
 MULTI_PACKAGES=-main -lang
 
@@ -43,27 +49,24 @@ LIB_DEPENDS=graphics/tiff \
graphics/png \
graphics/giflib
 
-RUN_DEPENDS-lang=  x11/windowmaker>=0.90.0
+RUN_DEPENDS-lang = x11/windowmaker>=${V}
 LIB_DEPENDS-lang=
 WANTLIB-lang=
 
-post-patch:
-# Rename wrongly named locale files
-   @mv ${WRKSRC}/WindowMaker/menu.cz ${WRKSRC}/WindowMaker/menu.cs
-   @mv ${WRKSRC}/WindowMaker/menu.se ${WRKSRC}/WindowMaker/menu.sv
+WMAKER_SHARE = ${PREFIX}/share/WindowMaker
 
 pre-configure:
-   @perl -pi -e "s

Re: [NEW] mail/ungrey-robins port

2016-06-08 Thread Craig Skinner
Hello,

On 2016-05-07 Sat 23:27 PM |, Craig Skinner wrote:
> Hi folks,
> 
> Attached here is a new port of ungrey-robins:
> 
> $ fgrep COMMENT Makefile
> COMMENT= pf spamd auto-whitelister of round-robin SMTP clients
> 
> 
> $ cat pkg/DESCR
> ungrey-robins assists postmasters by automatically whitelisting
> round robin SMTP clients (which often fail to pass greylisting),
> without resorting to manual maintenance of whitelists.
> 

Here's 1 of the included syslog samples, showing auto-whitelisting:


Feb 15 20:56:15 teak spamd[12533]: 209.85.220.50: connected (1/0)
Feb 15 20:57:51 teak spamd[326]: new entry 209.85.220.50 from 
 to , helo mail-pa0-f50.google.com
Feb 15 20:57:51 teak spamd[12533]: 209.85.220.50: disconnected after 96 seconds.
Feb 15 21:01:16 teak spamd[12533]: 209.85.220.41: connected (1/0)
Feb 15 21:02:47 teak spamd[326]: new entry 209.85.220.41 from 
 to , helo mail-pa0-f41.google.com
Feb 15 21:02:47 teak spamd[12533]: 209.85.220.41: disconnected after 91 seconds.
Feb 15 21:22:24 teak spamd[12533]: 209.85.220.44: connected (1/0)
Feb 15 21:24:00 teak spamd[326]: new entry 209.85.220.44 from 
 to , helo mail-pa0-f44.google.com
Feb 15 21:24:00 teak spamd[12533]: 209.85.220.44: disconnected after 96 seconds.
Feb 15 21:54:07 teak spamd[12533]: 209.85.220.54: connected (1/0)
Feb 15 21:55:42 teak spamd[326]: new entry 209.85.220.54 from 
 to , helo mail-pa0-f54.google.com
Feb 15 21:55:43 teak spamd[12533]: 209.85.220.54: disconnected after 96 seconds.
Feb 15 22:45:57 teak spamd[12533]: 209.85.220.52: connected (1/0)
Feb 15 22:47:32 teak spamd[326]: new entry 209.85.220.52 from 
 to , helo mail-pa0-f52.google.com
Feb 15 22:47:33 teak spamd[12533]: 209.85.220.52: disconnected after 96 seconds.
Feb 15 23:50:00 teak spamd[12533]: 209.85.220.50: connected (1/0)
Feb 15 23:51:36 teak spamd[12533]: 209.85.220.50: disconnected after 96 seconds.
Feb 15 23:52:09 teak spamd[18136]: queueing add of 209.85.220.50
Feb 15 23:52:09 teak spamd[18136]: whitelisting 209.85.220.50 in /var/db/spamd
Feb 16 00:11:02 teak ungrey-robins: 209.85.160.177 mail-yk0-f177.google.com. 
scored 18 (granted grace)
Feb 16 00:11:03 teak ungrey-robins: 209.85.220.41 mail-pa0-f41.google.com. 
scored 18 (granted grace)
Feb 16 00:11:03 teak ungrey-robins: 209.85.220.52 mail-pa0-f52.google.com. 
scored 18 (granted grace)
Feb 16 00:11:04 teak ungrey-robins: 209.85.220.44 mail-pa0-f44.google.com. 
scored 17 (granted grace)
Feb 16 00:11:05 teak ungrey-robins: 209.85.220.54 mail-pa0-f54.google.com. 
scored 18 (granted grace)
Feb 16 00:11:05 teak ungrey-robins: spamdb whitelisted: 209.85.160.177 
209.85.220.41 209.85.220.52 209.85.220.44 209.85.220.54
Feb 16 00:44:18 teak spamd[12533]: 209.85.220.43: connected (1/0)
Feb 16 00:45:53 teak spamd[326]: new entry 209.85.220.43 from 
 to , helo mail-pa0-f43.google.com
Feb 16 00:45:53 teak spamd[12533]: 209.85.220.43: disconnected after 95 seconds.
Feb 16 00:58:13 teak spamd[18136]: queueing deletion of 209.85.220.50 
mail-pa0-f50.google.com  
Feb 16 01:03:13 teak spamd[18136]: queueing deletion of 209.85.220.41 
mail-pa0-f41.google.com  
Feb 16 01:24:14 teak spamd[18136]: queueing deletion of 209.85.220.44 
mail-pa0-f44.google.com  
Feb 16 01:56:18 teak spamd[18136]: queueing deletion of 209.85.220.54 
mail-pa0-f54.google.com  
Feb 16 02:16:56 teak spamd[12533]: 209.85.220.45: connected (1/0)
Feb 16 02:18:31 teak spamd[326]: new entry 209.85.220.45 from 
 to , helo mail-pa0-f45.google.com
Feb 16 02:18:32 teak spamd[12533]: 209.85.220.45: disconnected after 96 seconds.
Feb 16 02:48:20 teak spamd[18136]: queueing deletion of 209.85.220.52 
mail-pa0-f52.google.com  
Feb 16 04:11:03 teak ungrey-robins: 209.85.220.43 mail-pa0-f43.google.com. 
scored 17 (granted grace)
Feb 16 04:11:03 teak ungrey-robins: 209.85.220.45 mail-pa0-f45.google.com. 
scored 18 (granted grace)
Feb 16 04:11:04 teak ungrey-robins: spamdb whitelisted: 209.85.220.43 
209.85.220.45
Feb 16 04:16:37 teak spamlogd[12344]: inbound 209.85.220.45
Feb 16 04:16:37 teak postfix/postscreen[7556]: CONNECT from 
[209.85.220.45]:34165 to [78.33.153.148]:25
Feb 16 04:16:38 teak postfix/dnsblog[24767]: addr 209.85.220.45 listed by 
domain hostkarma.junkemailfilter.com as 127.0.0.3
Feb 16 04:16:38 teak postfix/dnsblog[24767]: addr 209.85.220.45 listed by 
domain hostkarma.junkemailfilter.com as 127.0.1.1
Feb 16 04:16:38 teak postfix/dnsblog[28261]: addr 209.85.220.45 listed by 
domain list.dnswl.org as 127.0.5.1
Feb 16 04:16:38 teak postfix/dnsblog[28261]: addr 209.85.220.45 listed by 
domain rep.mailspike.net as 127.0.0.18
Feb 16 04:16:38 teak postfix/dnsblog[16607]: addr 209.85.220.45 listed by 
domain score.senderscore.com as 127.0.4.97
Feb 16 04:16:41 teak postfix/postscreen[7556]: PASS NEW [209.85.220.45]:34165
Feb 16 04:16:41 teak postfix/smtpd[314]: connect from 
mail-pa0-f45.google.com[209.85.220.45]
Feb 16 04:16:42 teak postfix/smtpd[314]: 3q48Bf2xbNzQM: 
client=mail-pa0-f45.google.com[209.85.220.45]
Feb 16 04:16:42 teak postfix/cleanup[22524

Re: [NEW] archivers/snappy

2016-06-08 Thread Frederic Cambus
On Tue, Jun 07, 2016 at 10:11:52PM +0100, Stuart Henderson wrote:

> autoconf picks up gtest and gflags, please either add BUILD_DEPENDS
> on these, or tell autoconf not to use them.
> 
> ..
> checking for 'gtest-config'... checking for gtest-config...
> /usr/local/bin/gtest-config
> /usr/local/bin/gtest-config
> checking for Google Test... yes
> checking for pkg-config... /usr/bin/pkg-config
> checking pkg-config is at least version 0.9.0... yes
> checking for gflags... no

Added CONFIGURE_ARGS += --disable-gtest to disable using gtest.

Regarding gflags, it's not used unless explicitely enabled with the
--with-gflags configure argument, which we don't enable.

New tarball attached.



snappy.tar.gz
Description: application/tar-gz