CVS: cvs.openbsd.org: ports

[Alexander Bluhm]

CVSROOT:/cvs
Module name:ports
Changes by: bl...@cvs.openbsd.org   2015/12/16 13:40:46

Modified files:
net/p5-Net-PcapWriter: Makefile distinfo 

Log message:
update p5-Net-PcapWriter to 0.720

Importing pkg_module

[Vadim Zhukov]

(some history)

During this summer the Jannis Tsaraias worked on the pkg_module, an
automated port creation framework as a GSoC Project. The project
succeeded, and Jannis stayed to maintain the code and accept patches
from interested parties:

https://github.com/diethyl/pkg_module

(back to nowadays)

A few months went, and we're still at the same place. pkg_module
proved to work by a few people already, and should be a nice addition
for 5.9. So I want to move on and finally import it. I'm attaching the
archive to be extracted under /usr/ports/infrastructure. After that
just type something like "pkg_module ruby dbf" and see how easy it
goes. :)

Personally I use it about once a month, saving a hour or two of manual
work. In particular, I'm trying to reuse this code to make maintaining
KDE Frameworks easier: doing things manually, I have to re-start
porting a new version before finishing a previous one...

Any comments/suggestions/objections/okays?
--
  WBR,
  Vadim Zhukov

UPDATE: devel/afl-1.96b

[Gleydson Soares]

The following updates devel/afl to 1.96b.
builds and runs fine on both (amd64/i386), regress seems happy too.
OK?

Index: Makefile
===
RCS file: /cvs/ports/devel/afl/Makefile,v
retrieving revision 1.21
diff -u -p -r1.21 Makefile
--- Makefile25 Nov 2015 02:27:12 -  1.21
+++ Makefile16 Dec 2015 19:56:53 -
@@ -3,7 +3,7 @@
 ONLY_FOR_ARCHS= i386 amd64
 
 COMMENT=   instrumented fuzzer
-DISTNAME=  afl-1.95b
+DISTNAME=  afl-1.96b
 EXTRACT_SUFX=  .tgz
 CATEGORIES=devel
 
Index: distinfo
===
RCS file: /cvs/ports/devel/afl/distinfo,v
retrieving revision 1.21
diff -u -p -r1.21 distinfo
--- distinfo25 Nov 2015 02:27:12 -  1.21
+++ distinfo16 Dec 2015 19:56:53 -
@@ -1,2 +1,2 @@
-SHA256 (afl-1.95b.tgz) = IexruMGC/YIdJci2coP4GmMsT3RBnJ21/sATXdDJrio=
-SIZE (afl-1.95b.tgz) = 804542
+SHA256 (afl-1.96b.tgz) = A76wb4mT3LN9NI5T2hnKnQZMg/ztydh7C1Bsc8MQ8nw=
+SIZE (afl-1.96b.tgz) = 804864
Index: patches/patch-Makefile
===
RCS file: /cvs/ports/devel/afl/patches/patch-Makefile,v
retrieving revision 1.15
diff -u -p -r1.15 patch-Makefile
--- patches/patch-Makefile  25 Nov 2015 02:27:12 -  1.15
+++ patches/patch-Makefile  16 Dec 2015 19:56:53 -
@@ -1,7 +1,7 @@
 $OpenBSD: patch-Makefile,v 1.15 2015/11/25 02:27:12 gsoares Exp $
 Makefile.orig  Thu Nov 12 23:58:12 2015
-+++ Makefile   Tue Nov 24 09:56:32 2015
-@@ -18,7 +18,7 @@ VERSION = 1.95b
+--- Makefile.orig  Wed Dec 16 01:24:06 2015
 Makefile   Wed Dec 16 16:55:42 2015
+@@ -18,7 +18,7 @@ VERSION = 1.96b
  
  PREFIX ?= /usr/local
  BIN_PATH= $(PREFIX)/bin

Re: Importing pkg_module

[Vadim Zhukov]

2015-12-16 22:33 GMT+03:00 Vadim Zhukov :
> (some history)
>
> During this summer the Jannis Tsaraias worked on the pkg_module, an
> automated port creation framework as a GSoC Project. The project
> succeeded, and Jannis stayed to maintain the code and accept patches
> from interested parties:
>
> https://github.com/diethyl/pkg_module
>
> (back to nowadays)
>
> A few months went, and we're still at the same place. pkg_module
> proved to work by a few people already, and should be a nice addition
> for 5.9. So I want to move on and finally import it. I'm attaching the
> archive to be extracted under /usr/ports/infrastructure. After that
> just type something like "pkg_module ruby dbf" and see how easy it
> goes. :)

And it works better if really attached - thank you, jca@!

> Personally I use it about once a month, saving a hour or two of manual
> work. In particular, I'm trying to reuse this code to make maintaining
> KDE Frameworks easier: doing things manually, I have to re-start
> porting a new version before finishing a previous one...
>
> Any comments/suggestions/objections/okays?

--
  WBR,
  Vadim Zhukov


infrastructure.tar.gz
Description: GNU Zip compressed data

Re: Importing pkg_module

[Vadim Zhukov]

2015-12-16 23:12 GMT+03:00 Landry Breuil :
> On Wed, Dec 16, 2015 at 10:33:33PM +0300, Vadim Zhukov wrote:
>> (some history)
>>
>> During this summer the Jannis Tsaraias worked on the pkg_module, an
>> automated port creation framework as a GSoC Project. The project
>> succeeded, and Jannis stayed to maintain the code and accept patches
>> from interested parties:
>>
>> https://github.com/diethyl/pkg_module
>>
>> (back to nowadays)
>>
>> A few months went, and we're still at the same place. pkg_module
>> proved to work by a few people already, and should be a nice addition
>> for 5.9. So I want to move on and finally import it. I'm attaching the
>> archive to be extracted under /usr/ports/infrastructure. After that
>> just type something like "pkg_module ruby dbf" and see how easy it
>> goes. :)
>>
>> Personally I use it about once a month, saving a hour or two of manual
>> work. In particular, I'm trying to reuse this code to make maintaining
>> KDE Frameworks easier: doing things manually, I have to re-start
>> porting a new version before finishing a previous one...
>>
>> Any comments/suggestions/objections/okays?
>
> That sounds like a really nice addition, the 'pkg_module' naming is a
> bit weird but whatever..
>
> You could have mentioned that (as far i can gather from quickly looking
> at the code) it supports Ruby (forge? gems?), PyPI and CPAN as sources...
> And that it generates a _port_ (which means to keep local or to submit
> for import in cvs?), not a package - hence the confusing naming :)

Yep. I'm biased since I (as well as afresh1@) was involved in the
project as a mentor, and thus I missed those - meaningful! - points.
Thank you for pointing them out!

> But all this can be gathered from the manpage :)
>
> The only missing thing.. i dont see regress tests, nor a list of
> ports/packages tested working/non-working with it, to get an idea of its
> coverage of the corresponding 'native repositories'...

The list of "successfully tested on" is rather large, thus it was
dropped at some point in the past. :) And the SPECIALS file in repo
lists known items having problems (i.e., requiring manual porting
instead).

--
  WBR,
  Vadim Zhukov

CVS: cvs.openbsd.org: ports

[Alexander Bluhm]

CVSROOT:/cvs
Module name:ports
Changes by: bl...@cvs.openbsd.org   2015/12/16 12:57:38

Modified files:
devel/p5-BSD-Resource: Makefile distinfo 

Log message:
update p5-BSD-Resource to 1.2909

CVS: cvs.openbsd.org: ports

[Alexander Bluhm]

CVSROOT:/cvs
Module name:ports
Changes by: bl...@cvs.openbsd.org   2015/12/16 13:03:24

Modified files:
mail/p5-Mail-SPF-Iterator: Makefile distinfo 

Log message:
update p5-Mail-SPF-Iterator to 1.111

Re: Importing pkg_module

[Landry Breuil]

On Wed, Dec 16, 2015 at 10:33:33PM +0300, Vadim Zhukov wrote:
> (some history)
> 
> During this summer the Jannis Tsaraias worked on the pkg_module, an
> automated port creation framework as a GSoC Project. The project
> succeeded, and Jannis stayed to maintain the code and accept patches
> from interested parties:
> 
> https://github.com/diethyl/pkg_module
> 
> (back to nowadays)
> 
> A few months went, and we're still at the same place. pkg_module
> proved to work by a few people already, and should be a nice addition
> for 5.9. So I want to move on and finally import it. I'm attaching the
> archive to be extracted under /usr/ports/infrastructure. After that
> just type something like "pkg_module ruby dbf" and see how easy it
> goes. :)
> 
> Personally I use it about once a month, saving a hour or two of manual
> work. In particular, I'm trying to reuse this code to make maintaining
> KDE Frameworks easier: doing things manually, I have to re-start
> porting a new version before finishing a previous one...
> 
> Any comments/suggestions/objections/okays?

That sounds like a really nice addition, the 'pkg_module' naming is a
bit weird but whatever..

You could have mentioned that (as far i can gather from quickly looking
at the code) it supports Ruby (forge? gems?), PyPI and CPAN as sources...
And that it generates a _port_ (which means to keep local or to submit
for import in cvs?), not a package - hence the confusing naming :)

But all this can be gathered from the manpage :)

The only missing thing.. i dont see regress tests, nor a list of
ports/packages tested working/non-working with it, to get an idea of its
coverage of the corresponding 'native repositories'...

Landry

CVS: cvs.openbsd.org: ports

[Alexander Bluhm]

CVSROOT:/cvs
Module name:ports
Changes by: bl...@cvs.openbsd.org   2015/12/16 13:33:00

Modified files:
net/p5-Net-DNS : Makefile distinfo 

Log message:
update p5-Net-DNS to 1.04

Re: UPDATE: offlineimap 6.6.0

[Daniel Jakots]

On Sat, 5 Dec 2015 07:50:36 +0100, Remi Locherer
 wrote:

> It works fine for me synchronizing between dovecot and Maildir.

Looks fine ports-wise.

Re: Please add ICU as dependency to Boost (i.e. change the "--without-icu" to "--with-icu") - thoughts?

[Landry Breuil]

On Wed, Dec 16, 2015 at 01:40:47PM +0100, Antoine Jacoutot wrote:
> On Wed, Dec 16, 2015 at 01:32:21PM +0100, Jérémie Courrèges-Anglas wrote:
> > Tinker  writes:
> > 
> > > On 2015-12-16 05:04, j...@wxcvbn.org wrote:
> > >> Tinker  writes:
> > >>
> > >>> What would the decision be based on?
> > >>
> > >> I think that those points should be enough.
> > >> - good reasons to use ICU in boost, not just "I need the ICU parts of
> > >>   Boost.".  What would be the benefit for the ports tree?
> > >
> > > I need normalize() to do Unicode normalization!
> > 
> > I'm glad to hear that you want to do Unicode normalization using ICU,
> > that is not a valid answer to what I said above.
> > 
> > We have one report here:
> > 
> >   http://marc.info/?l=openbsd-ports=144171504417490=2
> > 
> > jirib didn't confirm that ICU was the only thing needed to make his
> > aegisub port work, and to my knowledge no existing port requires ICU in
> > boost.  The only benefit I can see so far is to have a boost package
> > similar to other distros.
> 
> I wonder if adding ICU support to boost would unbreak manik.

On that topic i've filed https://github.com/mapnik/mapnik/issues/3202
upstream but didnt thought about that boost/icu thing.

Either way, touching boost... here be dragons.

Landry

Re: Please add ICU as dependency to Boost (i.e. change the "--without-icu" to "--with-icu") - thoughts?

[Tinker]

Wait, in the interim, the brave user who wants ICU support system-wide 
now, and who has ICU already installed in the system, can just switch 
the "--without-icu" part to "--with-icu" in 
/usr/ports/devel/boost/Makefile , and do "make; make install" right?



That will not break binary compatibility with precompiled packages, the 
only thing would be that if some package is specifically incompatible 
with Boost's ICU support, it'd go into undefined behavior, right?



On 2015-12-17 02:40, Landry Breuil wrote:

On Wed, Dec 16, 2015 at 01:40:47PM +0100, Antoine Jacoutot wrote:
On Wed, Dec 16, 2015 at 01:32:21PM +0100, Jérémie Courrèges-Anglas 
wrote:

> Tinker  writes:
>
> > On 2015-12-16 05:04, j...@wxcvbn.org wrote:
> >> Tinker  writes:
> >>
> >>> What would the decision be based on?
> >>
> >> I think that those points should be enough.
> >> - good reasons to use ICU in boost, not just "I need the ICU parts of
> >>   Boost.".  What would be the benefit for the ports tree?
> >
> > I need normalize() to do Unicode normalization!
>
> I'm glad to hear that you want to do Unicode normalization using ICU,
> that is not a valid answer to what I said above.
>
> We have one report here:
>
>   http://marc.info/?l=openbsd-ports=144171504417490=2
>
> jirib didn't confirm that ICU was the only thing needed to make his
> aegisub port work, and to my knowledge no existing port requires ICU in
> boost.  The only benefit I can see so far is to have a boost package
> similar to other distros.

I wonder if adding ICU support to boost would unbreak manik.


On that topic i've filed https://github.com/mapnik/mapnik/issues/3202
upstream but didnt thought about that boost/icu thing.

Either way, touching boost... here be dragons.

Landry

CVS: cvs.openbsd.org: ports

[Alexander Bluhm]

CVSROOT:/cvs
Module name:ports
Changes by: bl...@cvs.openbsd.org   2015/12/16 15:29:59

Modified files:
textproc/p5-Regexp-Common: Makefile distinfo 

Log message:
update p5-Regexp-Common to 2015121601

UPDATE: wkhtmltopdf with patched QT

[Frank Groeneveld]

Attached to this email you'll find a diff that modifies the wkhtmltopdf 
port so that it is statically built against their patched qt. This will 
will enable the following extra features:


 * Printing more then one HTML document into a PDF file.
 * Running without an X11 server.
 * Adding a document outline to the PDF file.
 * Adding headers and footers to the PDF file.
 * Generating a table of contents.
 * Adding links in the generated PDF file.
 * Printing using the screen media-type.
 * Disabling the smart shrink feature of webkit.

Note that the patches I needed in this diff are copied from the 
phantomjs port and the qt4 port.


As far as I can see, the current diff has only one problem left: it can 
only be built when qt4 is not already installed on the system, because 
the linking phase will fail otherwise. How would I be able to solve this 
problem?


Thanks,
Frank
Index: Makefile
===
RCS file: /cvs/ports/textproc/wkhtmltopdf/Makefile,v
retrieving revision 1.1.1.1
diff -u -p -r1.1.1.1 Makefile
--- Makefile4 Nov 2015 21:11:16 -   1.1.1.1
+++ Makefile16 Dec 2015 20:46:42 -
@@ -5,8 +5,13 @@ COMMENT =  convert HTML to PDF using Web
 GH_ACCOUNT =   wkhtmltopdf
 GH_PROJECT =   wkhtmltopdf
 GH_TAGNAME =   0.12.2.4
+REVISION = 0
 
+QT_COMMIT =7e48a1fac7e0f9aefccd01e9871f987da3a62fda
+
+MASTER_SITES0 =https://github.com/wkhtmltopdf/qt/archive/
 DISTNAME = wkhtmltopdf-${GH_TAGNAME}
+DISTFILES +=   ${DISTNAME}.tar.gz ${QT_COMMIT}.tar.gz:0
 
 SHARED_LIBS =  wkhtmltox 0.0 # 0.12
 
@@ -20,10 +25,7 @@ MAINTAINER = Frank Groeneveld 

Re: UPDATE: devel/afl-1.96b

[Michael McConville]

Gleydson Soares wrote:
> The following updates devel/afl to 1.96b.
> builds and runs fine on both (amd64/i386), regress seems happy too.
> OK?

Looks good, and works for me. ok mmcc@

> Index: Makefile
> ===
> RCS file: /cvs/ports/devel/afl/Makefile,v
> retrieving revision 1.21
> diff -u -p -r1.21 Makefile
> --- Makefile  25 Nov 2015 02:27:12 -  1.21
> +++ Makefile  16 Dec 2015 19:56:53 -
> @@ -3,7 +3,7 @@
>  ONLY_FOR_ARCHS= i386 amd64
>  
>  COMMENT= instrumented fuzzer
> -DISTNAME=afl-1.95b
> +DISTNAME=afl-1.96b
>  EXTRACT_SUFX=.tgz
>  CATEGORIES=  devel
>  
> Index: distinfo
> ===
> RCS file: /cvs/ports/devel/afl/distinfo,v
> retrieving revision 1.21
> diff -u -p -r1.21 distinfo
> --- distinfo  25 Nov 2015 02:27:12 -  1.21
> +++ distinfo  16 Dec 2015 19:56:53 -
> @@ -1,2 +1,2 @@
> -SHA256 (afl-1.95b.tgz) = IexruMGC/YIdJci2coP4GmMsT3RBnJ21/sATXdDJrio=
> -SIZE (afl-1.95b.tgz) = 804542
> +SHA256 (afl-1.96b.tgz) = A76wb4mT3LN9NI5T2hnKnQZMg/ztydh7C1Bsc8MQ8nw=
> +SIZE (afl-1.96b.tgz) = 804864
> Index: patches/patch-Makefile
> ===
> RCS file: /cvs/ports/devel/afl/patches/patch-Makefile,v
> retrieving revision 1.15
> diff -u -p -r1.15 patch-Makefile
> --- patches/patch-Makefile25 Nov 2015 02:27:12 -  1.15
> +++ patches/patch-Makefile16 Dec 2015 19:56:53 -
> @@ -1,7 +1,7 @@
>  $OpenBSD: patch-Makefile,v 1.15 2015/11/25 02:27:12 gsoares Exp $
>  Makefile.origThu Nov 12 23:58:12 2015
> -+++ Makefile Tue Nov 24 09:56:32 2015
> -@@ -18,7 +18,7 @@ VERSION = 1.95b
> +--- Makefile.origWed Dec 16 01:24:06 2015
>  Makefile Wed Dec 16 16:55:42 2015
> +@@ -18,7 +18,7 @@ VERSION = 1.96b
>   
>   PREFIX ?= /usr/local
>   BIN_PATH= $(PREFIX)/bin
> 

CVS: cvs.openbsd.org: ports

[Alexander Bluhm]

CVSROOT:/cvs
Module name:ports
Changes by: bl...@cvs.openbsd.org   2015/12/16 16:07:10

Modified files:
textproc/p5-XML-LibXML: Makefile distinfo 

Log message:
update p5-XML-LibXML to 2.0123

CVS: cvs.openbsd.org: ports

[Alexander Bluhm]

CVSROOT:/cvs
Module name:ports
Changes by: bl...@cvs.openbsd.org   2015/12/16 14:48:20

Modified files:
security/p5-IO-Socket-SSL: Makefile distinfo 

Log message:
update p5-IO-Socket-SSL to 2.022

CVS: cvs.openbsd.org: ports

[Stuart Henderson]

CVSROOT:/cvs
Module name:ports
Changes by: st...@cvs.openbsd.org   2015/12/16 16:26:14

Modified files:
multimedia/minidlna: Makefile 

Log message:
bump REVISION of minidlna to force updates; no idea what abi changed
but the old binary on my system wasn't answering UPNP multicast and
rebuilding fixed it for me.

Ruby Security Releases: 2.0.0-p648, 2.1.8, 2.2.4

[Jeremy Evans]

Three new ruby releases today to fix CVE-2015-7551: Unsafe tainted
string usage in Fiddle and DL. Details at
https://www.ruby-lang.org/en/news/2015/12/16/unsafe-tainted-string-usage-in-fiddle-and-dl-cve-2015-7551/

Ruby 2.0.0 is out of general support, so the only patch included is the
security patch.  There are a few other improvements to Ruby 2.1 and 2.2
that have been backported from trunk.  Both Ruby 2.1.8 and 2.2.4 include
a new non-static function in the shared lib, so I'm bumping the lib
minor on both to be safe.  Both Ruby 2.1 and 2.2 include one of our local
patches, so a couple patch files can be dropped for each.

I've backported a fix for DL to ruby 1.8, and manually tested it to make
sure it works.  Fiddle wasn't added to ruby until 1.9, so we don't need
to worry about that.

This vulnerability is not likely to affect many projects. It's a rare ruby
project that uses taint checking/$SAFE >= 0, and DL/Fiddle use is not
that common either, so I'm guessing the combination is quite rare.

Tested on amd64, compiles on i386.  Will be committing in a couple days
unless I hear objections.

Thanks,
Jeremy

Index: 1.8/Makefile
===
RCS file: /cvs/ports/lang/ruby/1.8/Makefile,v
retrieving revision 1.36
diff -u -p -r1.36 Makefile
--- 1.8/Makefile15 Apr 2015 21:58:16 -  1.36
+++ 1.8/Makefile16 Dec 2015 17:13:04 -
@@ -20,7 +20,7 @@ PKGNAME-ri_docs=  ruby-ri_docs-${VERSION}
 PKG_ARCH-ri_docs=  *
 PKGSPEC-main=  ruby->=1.8,<1.9
 
-REVISION-main= 4
+REVISION-main= 5
 REVISION-ri_docs=  0
 
 CONFIGURE_ARGS=--program-suffix=18 \
Index: 1.8/patches/patch-ext_dl_handle_c
===
RCS file: 1.8/patches/patch-ext_dl_handle_c
diff -N 1.8/patches/patch-ext_dl_handle_c
--- /dev/null   1 Jan 1970 00:00:00 -
+++ 1.8/patches/patch-ext_dl_handle_c   16 Dec 2015 17:12:54 -
@@ -0,0 +1,29 @@
+$OpenBSD$
+
+Backport fix for CVE-2009-5147 and CVE-2015-7551 from r23405.
+
+--- ext/dl/handle.c.orig   Wed Dec 16 09:07:34 2015
 ext/dl/handle.cWed Dec 16 09:11:33 2015
+@@ -5,6 +5,8 @@
+ #include 
+ #include "dl.h"
+ 
++#define SafeStringValuePtr(v) (rb_string_value(), rb_check_safe_obj(v), 
RSTRING_PTR(v))
++
+ VALUE rb_cDLHandle;
+ 
+ void
+@@ -52,11 +54,11 @@ rb_dlhandle_initialize(int argc, VALUE argv[], VALUE s
+ 
+   switch (rb_scan_args(argc, argv, "11", , )) {
+   case 1:
+-clib = NIL_P(lib) ? NULL : StringValuePtr(lib);
++clib = NIL_P(lib) ? NULL : SafeStringValuePtr(lib);
+ cflag = RTLD_LAZY | RTLD_GLOBAL;
+ break;
+   case 2:
+-clib = NIL_P(lib) ? NULL : StringValuePtr(lib);
++clib = NIL_P(lib) ? NULL : SafeStringValuePtr(lib);
+ cflag = NUM2INT(flag);
+ break;
+   default:
Index: 2.0/Makefile
===
RCS file: /cvs/ports/lang/ruby/2.0/Makefile,v
retrieving revision 1.23
diff -u -p -r1.23 Makefile
--- 2.0/Makefile22 Aug 2015 15:13:05 -  1.23
+++ 2.0/Makefile16 Dec 2015 16:37:19 -
@@ -6,7 +6,7 @@ COMMENT-tk =tk interface for ruby
 COMMENT-ri_docs =  ri documentation files for ruby
 
 VERSION =  2.0.0
-PATCHLEVEL =   647
+PATCHLEVEL =   648
 RUBYLIBREV =   2.0
 DISTNAME = ruby-${VERSION}-p${PATCHLEVEL}
 
Index: 2.0/distinfo
===
RCS file: /cvs/ports/lang/ruby/2.0/distinfo,v
retrieving revision 1.12
diff -u -p -r1.12 distinfo
--- 2.0/distinfo22 Aug 2015 15:13:05 -  1.12
+++ 2.0/distinfo16 Dec 2015 16:38:28 -
@@ -1,2 +1,2 @@
-SHA256 (ruby-2.0.0-p647.tar.gz) = yIqvW07HLiy30pD/hU8E0TWTn2E09RcAKp1l1fxeW+w=
-SIZE (ruby-2.0.0-p647.tar.gz) = 13621258
+SHA256 (ruby-2.0.0-p648.tar.gz) = hpC9a0lJwzOzkZdVxOSIhdv+1v0FX+nviZML3g0jdvg=
+SIZE (ruby-2.0.0-p648.tar.gz) = 13622628
Index: 2.1/Makefile
===
RCS file: /cvs/ports/lang/ruby/2.1/Makefile,v
retrieving revision 1.16
diff -u -p -r1.16 Makefile
--- 2.1/Makefile22 Aug 2015 15:13:41 -  1.16
+++ 2.1/Makefile16 Dec 2015 16:45:52 -
@@ -7,11 +7,11 @@ COMMENT-gdbm =gdbm interface for ruby
 COMMENT-tk =   tk interface for ruby
 COMMENT-ri_docs =  ri documentation files for ruby
 
-VERSION =  2.1.7
+VERSION =  2.1.8
 RUBYLIBREV =   2.1
 DISTNAME = ruby-${VERSION}
 
-SHARED_LIBS =  ruby21  1.1
+SHARED_LIBS =  ruby21  1.2
 PKGNAME-main = ruby-${VERSION}
 PKGNAME-gdbm = ruby21-gdbm-${VERSION}
 PKGNAME-tk =   ruby21-tk-${VERSION}
Index: 2.1/distinfo
===
RCS file: /cvs/ports/lang/ruby/2.1/distinfo,v
retrieving revision 1.8
diff -u -p -r1.8 distinfo

CVS: cvs.openbsd.org: ports

[Antoine Jacoutot]

CVSROOT:/cvs
Module name:ports
Changes by: ajacou...@cvs.openbsd.org   2015/12/16 23:51:59

Modified files:
productivity/tryton/trytond: Makefile distinfo 

Log message:
SECURITY update to trytond-3.2.11.
- CVE-2015-0861

UPDATE: devel/py-six 1.10.0

[Alexandr Shadchin]

Hi,

This diff updates py-six to the latest release.
Take maintainer.

Comments ? OK ?

-- 
Alexandr Shadchin

Index: Makefile
===
RCS file: /cvs/ports/devel/py-six/Makefile,v
retrieving revision 1.13
diff -u -p -r1.13 Makefile
--- Makefile29 Sep 2015 10:52:12 -  1.13
+++ Makefile17 Dec 2015 06:22:55 -
@@ -1,13 +1,14 @@
 # $OpenBSD: Makefile,v 1.13 2015/09/29 10:52:12 sthen Exp $
 
 COMMENT =  Python 2 and 3 compatibility library
-MODPY_EGG_VERSION =1.9.0
+MODPY_EGG_VERSION =1.10.0
 DISTNAME = six-${MODPY_EGG_VERSION}
 PKGNAME =  py-six-${MODPY_EGG_VERSION}
 CATEGORIES =   devel
-REVISION = 1
 
 HOMEPAGE = http://pythonhosted.org/six/
+
+MAINTAINER =   Alexandr Shadchin 
 
 # MIT
 PERMIT_PACKAGE_CDROM = Yes
Index: distinfo
===
RCS file: /cvs/ports/devel/py-six/distinfo,v
retrieving revision 1.8
diff -u -p -r1.8 distinfo
--- distinfo17 Jan 2015 01:44:25 -  1.8
+++ distinfo17 Dec 2015 06:22:55 -
@@ -1,2 +1,2 @@
-SHA256 (six-1.9.0.tar.gz) = 4kBSQR/E+9H2cmNVN8P8IzDZSBsYwDF2lbRiWVEskdU=
-SIZE (six-1.9.0.tar.gz) = 29127
+SHA256 (six-1.10.0.tar.gz) = EF+NaGFvgkjiS/DpNy7wTTzBAQTxmA9U1Xss5zpa1Wo=
+SIZE (six-1.10.0.tar.gz) = 29630

CVS: cvs.openbsd.org: ports

[Robert Nagy]

CVSROOT:/cvs
Module name:ports
Changes by: rob...@cvs.openbsd.org  2015/12/17 00:02:48

Modified files:
www/iridium: Makefile distinfo 
www/iridium/patches: patch-base_base_gypi 
 patch-base_process_process_posix_cc 
 patch-build_all_gyp patch-build_common_gypi 
 patch-chrome_app_chrome_main_delegate_cc 
 patch-chrome_app_chromium_strings_grd 
 patch-chrome_app_google_chrome_strings_grd 
 patch-chrome_app_theme_theme_resources_grd 
 patch-chrome_browser_about_flags_cc 
 patch-chrome_browser_browser_resources_grd 
 patch-chrome_browser_chrome_browser_main_cc 
 
patch-chrome_browser_chrome_content_browser_client_cc 
 
patch-chrome_browser_custom_handlers_protocol_handler_registry_cc 
 patch-chrome_browser_defaults_cc 
 
patch-chrome_browser_extensions_api_messaging_message_service_cc 
 
patch-chrome_browser_extensions_bookmark_app_helper_cc 
 
patch-chrome_browser_first_run_first_run_internal_posix_cc 
 
patch-chrome_browser_notifications_message_center_notification_manager_cc 
 patch-chrome_browser_process_singleton_posix_cc 
 patch-chrome_browser_renderer_preferences_util_cc 
 
patch-chrome_browser_resources_plugin_metadata_plugins_linux_json 
 
patch-chrome_browser_safe_browsing_incident_reporting_incident_reporting_service_cc
 
 
patch-chrome_browser_sync_profile_sync_components_factory_impl_cc 
 patch-chrome_browser_task_manager_task_manager_cc 
 
patch-chrome_browser_tracing_crash_service_uploader_cc 
 
patch-chrome_browser_ui_browser_command_controller_cc 
 patch-chrome_browser_ui_panels_panel_manager_cc 
 
patch-chrome_browser_ui_startup_bad_flags_prompt_cc 
 
patch-chrome_browser_ui_startup_startup_browser_creator_cc 
 
patch-chrome_browser_ui_toolbar_wrench_menu_model_cc 
 patch-chrome_browser_ui_views_accelerator_table_cc 
 
patch-chrome_browser_ui_views_chrome_views_delegate_cc 
 
patch-chrome_browser_ui_views_chrome_views_delegate_h 
 
patch-chrome_browser_ui_views_frame_opaque_browser_frame_view_cc 
 
patch-chrome_browser_ui_views_tabs_tab_drag_controller_cc 
 patch-chrome_browser_ui_views_tabs_tab_strip_cc 
 patch-chrome_browser_ui_webui_about_ui_cc 
 
patch-chrome_browser_ui_webui_chrome_web_ui_controller_factory_cc 
 
patch-chrome_browser_ui_webui_options_browser_options_handler_cc 
 patch-chrome_chrome_browser_extensions_gypi 
 patch-chrome_chrome_browser_gypi 
 patch-chrome_chrome_browser_ui_gypi 
 patch-chrome_chrome_common_gypi 
 patch-chrome_chrome_exe_gypi 
 patch-chrome_common_chrome_paths_cc 
 patch-chrome_common_chrome_paths_h 
 patch-chrome_common_chrome_switches_cc 
 patch-chrome_common_chrome_switches_h 
 patch-chrome_common_extensions_api_schemas_gypi 
 patch-chrome_common_pref_names_cc 
 patch-chrome_common_pref_names_h 
 patch-chrome_common_url_constants_cc 
 patch-chrome_common_url_constants_h 
 
patch-chrome_utility_media_galleries_image_metadata_extractor_cc 
 
patch-components_omnibox_browser_omnibox_field_trial_cc 
 
patch-components_policy_resources_policy_templates_json 
 patch-content_app_content_main_runner_cc 
 patch-content_browser_browser_main_loop_cc 
 patch-content_browser_child_process_launcher_cc 
 
patch-content_browser_renderer_host_render_widget_host_view_aura_cc 
 patch-content_content_browser_gypi 
 patch-content_content_common_gypi 
 

Re: Importing pkg_module

[Giannis Tsaraias]

On Wed, Dec 16, 2015 at 11:19:13PM +0300, Vadim Zhukov wrote:
> 2015-12-16 23:12 GMT+03:00 Landry Breuil :
> > On Wed, Dec 16, 2015 at 10:33:33PM +0300, Vadim Zhukov wrote:
> >> (some history)
> >>
> >> During this summer the Jannis Tsaraias worked on the pkg_module, an
> >> automated port creation framework as a GSoC Project. The project
> >> succeeded, and Jannis stayed to maintain the code and accept patches
> >> from interested parties:
> >>
> >> https://github.com/diethyl/pkg_module
> >>
> >> (back to nowadays)
> >>
> >> A few months went, and we're still at the same place. pkg_module
> >> proved to work by a few people already, and should be a nice addition
> >> for 5.9. So I want to move on and finally import it. I'm attaching the
> >> archive to be extracted under /usr/ports/infrastructure. After that
> >> just type something like "pkg_module ruby dbf" and see how easy it
> >> goes. :)
> >>
> >> Personally I use it about once a month, saving a hour or two of manual
> >> work. In particular, I'm trying to reuse this code to make maintaining
> >> KDE Frameworks easier: doing things manually, I have to re-start
> >> porting a new version before finishing a previous one...
> >>
> >> Any comments/suggestions/objections/okays?
> >
> > That sounds like a really nice addition, the 'pkg_module' naming is a
> > bit weird but whatever..
> >
> > You could have mentioned that (as far i can gather from quickly looking
> > at the code) it supports Ruby (forge? gems?), PyPI and CPAN as sources...
> > And that it generates a _port_ (which means to keep local or to submit
> > for import in cvs?), not a package - hence the confusing naming :)
> 

PyPI.pm is currently a placeholder; I had some pieces of it working, but
thought I'd keep it out of the repo until its coverage gets closer to that
of CPAN or Ruby Gems.

> Yep. I'm biased since I (as well as afresh1@) was involved in the
> project as a mentor, and thus I missed those - meaningful! - points.
> Thank you for pointing them out!
> 
> > But all this can be gathered from the manpage :)
> >
> > The only missing thing.. i dont see regress tests, nor a list of
> > ports/packages tested working/non-working with it, to get an idea of its
> > coverage of the corresponding 'native repositories'...
> 
> The list of "successfully tested on" is rather large, thus it was
> dropped at some point in the past. :) And the SPECIALS file in repo
> lists known items having problems (i.e., requiring manual porting
> instead).
> 

That file could use some updates, which I've been meaning to do. One issue
worth mentioning is that currently there's no handling of modules that install
shared libraries, though I've recently started working on that.

I also have some useful feedback about CPAN by nigel@ that I haven't addressed 
yet.

Seeing that there's interest, I could resume working on this more actively. :)

Re: UPDATE: wkhtmltopdf with patched QT

[Stuart Henderson]

On 2015/12/16 22:20, Frank Groeneveld wrote:
> Attached to this email you'll find a diff that modifies the wkhtmltopdf port
> so that it is statically built against their patched qt. This will will
> enable the following extra features:
> 
>  * Printing more then one HTML document into a PDF file.
>  * Running without an X11 server.
>  * Adding a document outline to the PDF file.
>  * Adding headers and footers to the PDF file.
>  * Generating a table of contents.
>  * Adding links in the generated PDF file.
>  * Printing using the screen media-type.
>  * Disabling the smart shrink feature of webkit.
> 
> Note that the patches I needed in this diff are copied from the phantomjs
> port and the qt4 port.
> 
> As far as I can see, the current diff has only one problem left: it can only
> be built when qt4 is not already installed on the system, because the
> linking phase will fail otherwise. How would I be able to solve this
> problem?

Check the -L flags - the path to the build directory containing the newly
built Qt library will need to be listed before -L/usr/local/lib. I'm not
sure how you'd go about passing this in through qmake though.

Re: Please add ICU as dependency to Boost (i.e. change the "--without-icu" to "--with-icu") - thoughts?

[Juan Francisco Cantero Hurtado]

On Thu, Dec 17, 2015 at 06:27:07AM +0800, Tinker wrote:
> Wait, in the interim, the brave user who wants ICU support system-wide now,
> and who has ICU already installed in the system, can just switch the
> "--without-icu" part to "--with-icu" in /usr/ports/devel/boost/Makefile ,
> and do "make; make install" right?

$ make clean=all
$ make
$ make fake
$ make port-lib-depends-check
# fix WANTLIB
$ make update-plist
$ make reinstall

> 
> 
> That will not break binary compatibility with precompiled packages, the only
> thing would be that if some package is specifically incompatible with
> Boost's ICU support, it'd go into undefined behavior, right?
> 
> 
> On 2015-12-17 02:40, Landry Breuil wrote:
> >On Wed, Dec 16, 2015 at 01:40:47PM +0100, Antoine Jacoutot wrote:
> >>On Wed, Dec 16, 2015 at 01:32:21PM +0100, Jérémie Courrèges-Anglas
> >>wrote:
> >>> Tinker  writes:
> >>>
> >>> > On 2015-12-16 05:04, j...@wxcvbn.org wrote:
> >>> >> Tinker  writes:
> >>> >>
> >>> >>> What would the decision be based on?
> >>> >>
> >>> >> I think that those points should be enough.
> >>> >> - good reasons to use ICU in boost, not just "I need the ICU parts of
> >>> >>   Boost.".  What would be the benefit for the ports tree?
> >>> >
> >>> > I need normalize() to do Unicode normalization!
> >>>
> >>> I'm glad to hear that you want to do Unicode normalization using ICU,
> >>> that is not a valid answer to what I said above.
> >>>
> >>> We have one report here:
> >>>
> >>>   http://marc.info/?l=openbsd-ports=144171504417490=2
> >>>
> >>> jirib didn't confirm that ICU was the only thing needed to make his
> >>> aegisub port work, and to my knowledge no existing port requires ICU in
> >>> boost.  The only benefit I can see so far is to have a boost package
> >>> similar to other distros.
> >>
> >>I wonder if adding ICU support to boost would unbreak manik.
> >
> >On that topic i've filed https://github.com/mapnik/mapnik/issues/3202
> >upstream but didnt thought about that boost/icu thing.
> >
> >Either way, touching boost... here be dragons.
> >
> >Landry
> 

-- 
Juan Francisco Cantero Hurtado http://juanfra.info

subscribe

[Gerald Holguin]

Re: Please add ICU as dependency to Boost (i.e. change the "--without-icu" to "--with-icu") - thoughts?

[David Coppa]

On Wed, Dec 16, 2015 at 1:32 PM, Jérémie Courrèges-Anglas
 wrote:

> We have one report here:
>
>   http://marc.info/?l=openbsd-ports=144171504417490=2
>
> jirib didn't confirm that ICU was the only thing needed to make his
> aegisub port work, and to my knowledge no existing port requires ICU in
> boost.

audio/ncmpcpp (since version 0.7) can make use of it:

checking pkg-config is at least version 0.9.0... yes
checking for ICU... yes
checking whether boost.regex was compiled with ICU support... no

Ciao!
David

Re: Here is how to build and install BitcoinD (0.11.2 = latest) on OpenBSD. Can you please make a "net/bitcoin" port of these instructions?

[Pascal Stumpf]

I think this needs some serious work, at least an updated
databases/db/v4 and some solution to that ugly LibreSSL problem.

I'm not really using this in any way, so I won't spend that kind of
effort on it.

On Wed, 16 Dec 2015 18:26:04 +0800, poweru...@openmailbox.org wrote:
> Guys,
> 
> What do you say, do you feel this is a relevant port?
> 
> 
> 
> Sorry for not being able to do this myself -
> 
> If you need any extra clear feedback or instructions from me for how to 
> actually build it, so that you can get the port together, I will be 
> happy to guide you, if so let me know.
> 
> What made me not be able to make an update of the port complete myself, 
> was some weird aspect of how the filenaming works out in the ports 
> system and I cannot dig that deep into the system now.
> 
> Maybe, I could document exactly what I do when I try to upgrade the 
> openbsd-wip bitcoind port, and paste the exact error I get here, and you 
> could tell me how to fix it - and we can get the updated BitcoinD port 
> into OpenBSD that way,
> 
> What do you say?
> 
> 
> 
> On 2015-12-16 02:05, poweru...@openmailbox.org wrote:
> > (
> > 
> > Well, the instructions I provided show exactly how to get the BitcoinD
> > 0.11.2 port going, however, it uses GCC 4.8 for the compilation.
> > 
> > Using OpenBSD's GCC version should work but will require a bit of
> > experimentation, I think adding
> > "--disable-tests --disable-debug" to ./configure will be sufficient.
> > This was pointed out in the original email already.
> > 
> > )
> > 
> > On 2015-12-16 01:22, poweru...@openmailbox.org wrote:
> >> Hi!
> >> 
> >> I don't know exactly how the port system works.
> >> 
> >> I figured out exactly how to get BitcoinD latest to build, by manually
> >> patching the openbsd-wip bitcoind port, which is 2.5 years old.
> >> 
> >> I failed to actually get the port updated, on a stupid detail of the
> >> port Makefile though, it was something about the filenaming scheme the
> >> ports system will use for its build directory -
> >> 
> >> I am sure YOU know exactly how that works, in no time, so for this
> >> reason I'll describe exactly how to build BitcoinD 0.11.2 = latest on
> >> OpenBSD based on the port here, and you can incredibly quickly pull
> >> together the actual port for it.
> >> 
> >> Which the exact patches are and the exact configure arguments etc. are
> >> provided, and this is all a patch to the openbsd-wip bitcoind port
> >> already, so the hard work is already done.
> >> 
> >> 
> >> Please let me know when you got it in place?
> >> 
> >> Thanks!!
> >> Poweruser
> >> 
> >> 
> >> 
> >> 
> >> 
> >> A google search on this topic mentions
> >> http://www.thedrinkingrecord.com/2015/02/14/notes-on-building-bitcoin-qt-on-openbsd/
> >> also.
> >> 
> >> Also this post should be followed up on when this port has been
> >> published:
> >> http://unix.stackexchange.com/questions/82858/compiling-bitcoind-on-openbsd
> >> 
> >> Some things are stated doubly below. In that case just read it as if
> >> was written once.
> >> 
> >> 
> >> There is a previous BitcoinD package in openbsd-wip (version 0.9.1).
> >> It's 2.5 years old so it's completely antiquated.
> >> 
> >> Its sources are at
> >> https://github.com/jasperla/openbsd-wip/tree/master/net/bitcoin , and
> >> this is what my patch here is based on.
> >> 
> >> I used that one before, and to my experience it worked perfectly,
> >> except for when trying to use BitcoinD's HTTP RPC server - that
> >> crashed when even telnetting to the port I think.. or if it was when
> >> posting any request to it. That functionality is completely secondary
> >> though. I did not test that on this updated version, perhaps it works
> >> now.
> >> 
> >> 
> >> My installation instructions are a modified version of the openbsd-wip 
> >> package.
> >> 
> >> Take that bitcoin directory in the openbsd-wip package, and put it in
> >> your local /usr/ports/net/ directory.
> >> 
> >> 
> >> The patch files need some updates. First, let's overview the 8 patch
> >> files individually, as some of these changed names, or disappeared,
> >> since 0.9.1:
> >> 
> >> 
> >>  * compat.h is now src/compat.h - attaching new version (applied
> >> exactly the same thing as in the old patch)
> >> 
> >>  * db.cpp - this file was moved to src/wallet/db.cpp .
> >> 
> >>  * leveldb/port/port_posix.h is now src/leveldb/port/port_posix.h -
> >> applied same thinga sin patch.
> >> 
> >>  * src/m4/bitcoin_find_bdb48.m4 changed name to
> >> build-aux/m4/bitcoin_find_bdb48.m4 , applied the same patch contents.
> >> 
> >>  * can't find src/qt/Makefile.am here.  so i just dropped it.
> >> 
> >>  * share/genbuild.sh kept its name. figured out what section to 
> >> remove.
> >> 
> >>  * I didn't touch patch-src_Makefile_include and
> >> patch-contrib_debian_manpages_bitcoind_1 - you figure out what
> >> these should be now please!
> >> 
> >> 
> >> And now here below are my patch files, these patches compare the
> >> unmodified 

Re: Please add ICU as dependency to Boost (i.e. change the "--without-icu" to "--with-icu") - thoughts?

[Antoine Jacoutot]

On Wed, Dec 16, 2015 at 01:32:21PM +0100, Jérémie Courrèges-Anglas wrote:
> Tinker  writes:
> 
> > On 2015-12-16 05:04, j...@wxcvbn.org wrote:
> >> Tinker  writes:
> >>
> >>> What would the decision be based on?
> >>
> >> I think that those points should be enough.
> >> - good reasons to use ICU in boost, not just "I need the ICU parts of
> >>   Boost.".  What would be the benefit for the ports tree?
> >
> > I need normalize() to do Unicode normalization!
> 
> I'm glad to hear that you want to do Unicode normalization using ICU,
> that is not a valid answer to what I said above.
> 
> We have one report here:
> 
>   http://marc.info/?l=openbsd-ports=144171504417490=2
> 
> jirib didn't confirm that ICU was the only thing needed to make his
> aegisub port work, and to my knowledge no existing port requires ICU in
> boost.  The only benefit I can see so far is to have a boost package
> similar to other distros.

I wonder if adding ICU support to boost would unbreak manik.

-- 
Antoine

CVS: cvs.openbsd.org: ports

[David Coppa]

CVSROOT:/cvs
Module name:ports
Changes by: dco...@cvs.openbsd.org  2015/12/16 06:05:50

Modified files:
audio/ncmpcpp  : Makefile 

Log message:
Switch to devel/readline from ports.
When using readline from base, ncmpcpp segfaults with every action
demanding user input (i.e. searching songs, tagging files, etc).

Re: UPDATE: offlineimap 6.6.0

[Remi Locherer]

ping

On 2015-12-05 07:50, Remi Locherer wrote:

Hi

OfflineIMAP v6.6.0 was just released. From the announcement mail:

-
# Features

- Maildir learns to mimic Dovecot's format of lower-case letters 
(a,b,c..) for

  "custom flags" or user keywords.

# Fixes

- Broken retry loop would break connection management.
- Replace rogue `print` statement by `self.ui.debug`.

# Changes

- Bump imaplib2 from v2.52 to v2.53.
- Code cleanups.
- Add a full stack of all thread dump upon EXIT or KILL signal in 
thread debug

  mode.
-

It works fine for me synchronizing between dovecot and Maildir.

Remi


Index: Makefile
===
RCS file: /cvs/ports/mail/offlineimap/Makefile,v
retrieving revision 1.29
diff -u -p -r1.29 Makefile
--- Makefile30 Nov 2015 22:27:13 -  1.29
+++ Makefile4 Dec 2015 23:53:17 -
@@ -2,7 +2,7 @@

 COMMENT=   powerful IMAP/Maildir synchronization and reader support

-MODPY_EGG_VERSION = 6.5.7
+MODPY_EGG_VERSION = 6.6.0
 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.18
diff -u -p -r1.18 distinfo
--- distinfo30 Nov 2015 22:27:13 -  1.18
+++ distinfo4 Dec 2015 23:56:33 -
@@ -1,2 +1,2 @@
-SHA256 (offlineimap-6.5.7.tar.gz) =
t95Sx9iZXgZXu1XaE1McjW+W2CghcVlHfGha5AjjkKM=
-SIZE (offlineimap-6.5.7.tar.gz) = 20
+SHA256 (offlineimap-6.6.0.tar.gz) =
xBJY5c5TGRW7iR1M4Qs6+IttdKbuabYoKVf4UWX/Y/Q=
+SIZE (offlineimap-6.6.0.tar.gz) = 674655

CVS: cvs.openbsd.org: ports

[Benoit Lecocq]

CVSROOT:/cvs
Module name:ports
Changes by: ben...@cvs.openbsd.org  2015/12/16 06:45:35

Modified files:
devel/p5-File-Find-Rule: Makefile distinfo 

Log message:
Update to p5-File-Find-Rule-0.34.

CVS: cvs.openbsd.org: ports

[David Coppa]

CVSROOT:/cvs
Module name:ports
Changes by: dco...@cvs.openbsd.org  2015/12/16 07:46:47

Modified files:
audio/ncmpcpp  : Makefile 
audio/ncmpcpp/patches: patch-src_ncmpcpp_cpp 

Log message:
better fix for sigignore()

CVS: cvs.openbsd.org: ports

[Stuart Henderson]

CVSROOT:/cvs
Module name:ports
Changes by: st...@cvs.openbsd.org   2015/12/16 07:10:05

Modified files:
security/letsencrypt: Makefile.inc 
security/letsencrypt/client: Makefile distinfo 
security/letsencrypt/client/patches: patch-examples_cli_ini 
security/letsencrypt/client/pkg: PLIST 
security/letsencrypt/py-acme: distinfo 

Log message:
update to letsencrypt-0.1.1

Re: Here is how to build and install BitcoinD (0.11.2 = latest) on OpenBSD. Can you please make a "net/bitcoin" port of these instructions?

[poweruser]

Pascal,

I wish to make a very strong point that these are non-problems!

Because, the dependency issues you mention don't really exist, and, 
BitcoinD works perfectly on OpenBSD already.


For this reason I suggest that OpenBSD is included into the ports tree!

Berkeley DB is used for the wallet only, but, BitcoinD is primarily the 
reference implementation as router.


Explanatory notes below.


Would you want to throw together a port, or, should I attempt to do it 
and then paste the errors I get that I don't understand how to fix?


Thanks!




1) It works perfectly:
The BitcoinD I built does do a full sync and then runs reliably. It 
seems very stable. In a month it SIGSEGV:ed once, who knows perhaps that 
was because of some machine/OS instability.


2) LibreSSL is not a problem currently and will be removed as a 
dependency soon anyhow, so that is not a problem:

I think the LibreSSL problem actually does not exist.
 I mean, basically they are saying that they suspect LibreSSL could 
be version-incompatible with OpenSSL and hence LibreSSL could cause 
misbehavior in the consensus logics - but if that ever would happen, you 
would notice quickly.

 And, noone has ever seen that happen for real.
 And finally, they will kick out the OpenSSL dependency altogether 
in 0.13 or 0.14!
 So it would be pointless to invest any resources in the LibreSSL 
dependency now.
 So with all this said I really consider the LibreSSL dependency a 
no-problem.


3) Berkeley DB is used for the wallet only
What issue do you see about Berkeley DB?

Would an updated BDB port be needed in OpenBSD for it to work?

Anyhow it's used for the wallet only. The router function of BitcoinD is 
the central function.





On 2015-12-16 18:50, Pascal Stumpf wrote:

I think this needs some serious work, at least an updated
databases/db/v4 and some solution to that ugly LibreSSL problem.

I'm not really using this in any way, so I won't spend that kind of
effort on it.

On Wed, 16 Dec 2015 18:26:04 +0800, poweru...@openmailbox.org wrote:

Guys,

What do you say, do you feel this is a relevant port?



Sorry for not being able to do this myself -

If you need any extra clear feedback or instructions from me for how 
to

actually build it, so that you can get the port together, I will be
happy to guide you, if so let me know.

What made me not be able to make an update of the port complete 
myself,

was some weird aspect of how the filenaming works out in the ports
system and I cannot dig that deep into the system now.

Maybe, I could document exactly what I do when I try to upgrade the
openbsd-wip bitcoind port, and paste the exact error I get here, and 
you

could tell me how to fix it - and we can get the updated BitcoinD port
into OpenBSD that way,

What do you say?



On 2015-12-16 02:05, poweru...@openmailbox.org wrote:
> (
>
> Well, the instructions I provided show exactly how to get the BitcoinD
> 0.11.2 port going, however, it uses GCC 4.8 for the compilation.
>
> Using OpenBSD's GCC version should work but will require a bit of
> experimentation, I think adding
> "--disable-tests --disable-debug" to ./configure will be sufficient.
> This was pointed out in the original email already.
>
> )
>
> On 2015-12-16 01:22, poweru...@openmailbox.org wrote:
>> Hi!
>>
>> I don't know exactly how the port system works.
>>
>> I figured out exactly how to get BitcoinD latest to build, by manually
>> patching the openbsd-wip bitcoind port, which is 2.5 years old.
>>
>> I failed to actually get the port updated, on a stupid detail of the
>> port Makefile though, it was something about the filenaming scheme the
>> ports system will use for its build directory -
>>
>> I am sure YOU know exactly how that works, in no time, so for this
>> reason I'll describe exactly how to build BitcoinD 0.11.2 = latest on
>> OpenBSD based on the port here, and you can incredibly quickly pull
>> together the actual port for it.
>>
>> Which the exact patches are and the exact configure arguments etc. are
>> provided, and this is all a patch to the openbsd-wip bitcoind port
>> already, so the hard work is already done.
>>
>>
>> Please let me know when you got it in place?
>>
>> Thanks!!
>> Poweruser
>>
>>
>>
>>
>>
>> A google search on this topic mentions
>> 
http://www.thedrinkingrecord.com/2015/02/14/notes-on-building-bitcoin-qt-on-openbsd/
>> also.
>>
>> Also this post should be followed up on when this port has been
>> published:
>> http://unix.stackexchange.com/questions/82858/compiling-bitcoind-on-openbsd
>>
>> Some things are stated doubly below. In that case just read it as if
>> was written once.
>>
>>
>> There is a previous BitcoinD package in openbsd-wip (version 0.9.1).
>> It's 2.5 years old so it's completely antiquated.
>>
>> Its sources are at
>> https://github.com/jasperla/openbsd-wip/tree/master/net/bitcoin , and
>> this is what my patch here is based on.
>>
>> I used that one before, and to my experience it worked perfectly,
>> 

Re: Here is how to build and install BitcoinD (0.11.2 = latest) on OpenBSD. Can you please make a "net/bitcoin" port of these instructions?

[poweruser]

On 2015-12-16 19:04, poweru...@openmailbox.org wrote:
..

For this reason I suggest that OpenBSD is included into the ports tree!


Err - for this reason I suggest that *BitcoinD* is included into the 
ports tree.



That it's precompiled with "--disable-wallet" is all fine. If anyone 
wants to fix that later it's fine. Now let's get the router working!

Re: Please add ICU as dependency to Boost (i.e. change the "--without-icu" to "--with-icu") - thoughts?

[Tinker]

On 2015-12-16 18:23, Landry Breuil wrote:

On Wed, Dec 16, 2015 at 06:10:17PM +0800, Tinker wrote:
Aha thank you very much for pointing these things out - great to know 
there

was a discussion about it.

Aha so maybe for OpenBSD 6.0 we'll have an ICU flavor at least.


Flavors in libraries are really a pain to handle, so we try to avoid
those.

Landry


(I understand that.)

Re: Please add ICU as dependency to Boost (i.e. change the "--without-icu" to "--with-icu") - thoughts?

[Tinker]

On 2015-12-16 05:04, j...@wxcvbn.org wrote:

Tinker  writes:


What would the decision be based on?


I think that those points should be enough.
- good reasons to use ICU in boost, not just "I need the ICU parts of
  Boost.".  What would be the benefit for the ports tree?


I need normalize() to do Unicode normalization!


E.g. within locale(BC_LOCALE_UTF8).

http://www.boost.org/doc/libs/1_54_0/libs/locale/doc/html/group__convert.html

Boost.Locale requires Boost to be compiled with --with-icu , 
http://www.boost.org/doc/libs/1_59_0/libs/locale/doc/html/index.html 
says:


 "In order to achieve this goal Boost.Locale uses 
the-state-of-the-art Unicode and Localization library: ICU - 
International Components for Unicode.


 Boost.Locale creates the natural glue between the C++ locales 
framework, iostreams, and the powerful ICU library."




(Then it continues "Boost.Locale provides non-ICU based localization 
support as well. It is based on the operating system native API or on 
the standard C++ library support. Sacrificing some less important 
features, Boost.Locale becomes less powerful but lighter and easier to 
deploy and use library."  - but, there's an issue here that the 
C++/OS-bundled unicode normalization may be incomplete or broken so this 
is why you want ICU.)




- someone has to do the work, and that includes checking for potential
  breakage.


Right, Kirill said you are looking into this already now



Everyone just rolling thumbs or is there any real tradeoff?


You tell us. ;)

Re: Please add ICU as dependency to Boost (i.e. change the "--without-icu" to "--with-icu") - thoughts?

[Jérémie Courrèges-Anglas]

Tinker  writes:

> On 2015-12-16 05:04, j...@wxcvbn.org wrote:
>> Tinker  writes:
>>
>>> What would the decision be based on?
>>
>> I think that those points should be enough.
>> - good reasons to use ICU in boost, not just "I need the ICU parts of
>>   Boost.".  What would be the benefit for the ports tree?
>
> I need normalize() to do Unicode normalization!

I'm glad to hear that you want to do Unicode normalization using ICU,
that is not a valid answer to what I said above.

We have one report here:

  http://marc.info/?l=openbsd-ports=144171504417490=2

jirib didn't confirm that ICU was the only thing needed to make his
aegisub port work, and to my knowledge no existing port requires ICU in
boost.  The only benefit I can see so far is to have a boost package
similar to other distros.

> E.g. within locale(BC_LOCALE_UTF8).
>
> http://www.boost.org/doc/libs/1_54_0/libs/locale/doc/html/group__convert.html
>
> Boost.Locale requires Boost to be compiled with --with-icu ,
> http://www.boost.org/doc/libs/1_59_0/libs/locale/doc/html/index.html
> says:
>
>  "In order to achieve this goal Boost.Locale uses
> the-state-of-the-art Unicode and Localization library: ICU - 
> International Components for Unicode.
>
>  Boost.Locale creates the natural glue between the C++ locales
> framework, iostreams, and the powerful ICU library."
>
>
>
> (Then it continues "Boost.Locale provides non-ICU based localization
> support as well. It is based on the operating system native API or on
> the standard C++ library support. Sacrificing some less important
> features, Boost.Locale becomes less powerful but lighter and easier to
> deploy and use library."  - but, there's an issue here that the
> C++/OS-bundled unicode normalization may be incomplete or broken so this
> is why you want ICU.)
>
>> - someone has to do the work, and that includes checking for potential
>>   breakage.
>
> Right, Kirill said you are looking into this already now

In this thread I see no mail from Kirill saying this.  Who is "you" in
this sentence?

Back to thumb twiddling,

[...]

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

CVS: cvs.openbsd.org: ports

[Robert Nagy]

CVSROOT:/cvs
Module name:ports
Changes by: rob...@cvs.openbsd.org  2015/12/16 09:14:13

Modified files:
www/chromium   : Makefile distinfo 

Log message:
update to 47.0.2526.106

CVS: cvs.openbsd.org: ports

[Antoine Jacoutot]

CVSROOT:/cvs
Module name:ports
Changes by: ajacou...@cvs.openbsd.org   2015/12/16 02:37:21

Modified files:
sysutils/simple-mtpfs: Makefile 

Log message:
lowercase in comment.

CVS: cvs.openbsd.org: ports

[David Coppa]

CVSROOT:/cvs
Module name:ports
Changes by: dco...@cvs.openbsd.org  2015/12/16 01:48:09

Modified files:
audio/mpd  : Makefile distinfo 
audio/mpd/patches: patch-Makefile_in 
Removed files:
audio/mpd/patches: patch-src_Main_cxx 

Log message:
Bugfixing update to mpd-0.19.12

CVS: cvs.openbsd.org: ports

[Antoine Jacoutot]

CVSROOT:/cvs
Module name:ports
Changes by: ajacou...@cvs.openbsd.org   2015/12/16 01:52:22

Modified files:
audio/ardour   : Makefile 
audio/ardour/pkg: PLIST 

Log message:
vamp is getting picked up.

CVS: cvs.openbsd.org: ports

[Landry Breuil]

CVSROOT:/cvs
Module name:ports
Changes by: lan...@cvs.openbsd.org  2015/12/16 00:58:56

Modified files:
audio/mpd  : Makefile 

Log message:
Fix linking on powerpc by disabling -Wl,--gc-sections
With hint from mpi@, ok dcoppa@ (maintainer)

CVS: cvs.openbsd.org: ports

[Landry Breuil]

CVSROOT:/cvs
Module name:ports
Changes by: lan...@cvs.openbsd.org  2015/12/16 03:08:53

Modified files:
www/firefox-esr: Makefile distinfo 
www/firefox-esr-i18n: Makefile.inc distinfo 

Log message:
Update to firefox-esr 38.5.0.

See https://www.mozilla.org/en-US/firefox/38.5.0/releasenotes/
Fixes MFSA 2015-134,138,139,145,146,147,149

Re: Please add ICU as dependency to Boost (i.e. change the "--without-icu" to "--with-icu") - thoughts?

[Tinker]

Aha thank you very much for pointing these things out - great to know 
there was a discussion about it.


Aha so maybe for OpenBSD 6.0 we'll have an ICU flavor at least.

I understand that the ICU support in Boost interfered with some other 
package so it wasn't completely untrivial to include and that's why you 
didn't do it already -


I think I'll try with that flavor as per the patch in the other email, 
on my machine, and let you know if I see any issue.


Thank you so much & happy holidays!
Tinker

On 2015-12-16 05:54, j...@wxcvbn.org wrote:

Stuart Henderson  writes:


On 2015/12/15 22:04, Jérémie Courrèges-Anglas wrote:

Tinker  writes:

> What would the decision be based on?

I think that those points should be enough.
- good reasons to use ICU in boost, not just "I need the ICU parts of
  Boost.".  What would be the benefit for the ports tree?
- someone has to do the work, and that includes checking for 
potential

  breakage.


And updating WANTLIB :-)


> Everyone just rolling thumbs or is there any real tradeoff?

You tell us. ;)


Also note that this port does have a maintainer.


Duh, indeed.  So please also discuss this with Brad.

CVS: cvs.openbsd.org: ports

[Landry Breuil]

CVSROOT:/cvs
Module name:ports
Changes by: lan...@cvs.openbsd.org  2015/12/16 03:12:14

Modified files:
www/mozilla-firefox: Makefile distinfo 
www/mozilla-firefox/patches: patch-gfx_skia_moz_build 
www/mozilla-firefox/pkg: README 
www/firefox-i18n: Makefile.inc distinfo 
Removed files:
www/mozilla-firefox/patches: patch-config_system-headers 

Log message:
Update to firefox 43.0.

See https://www.mozilla.org/en-US/firefox/43.0/releasenotes/
Fixes MFSA 2015-134 -> 149

- Remove merged patch about freetype paths/versions
- Remove outdated mention of 'disable anti-aliasing', from matthieu@

Tested (among others) by benoit@, mmcc@ and naddy@

CVS: cvs.openbsd.org: ports

[Stefan Sperling]

CVSROOT:/cvs
Module name:ports
Changes by: s...@cvs.openbsd.org2015/12/16 03:21:52

Modified files:
devel/subversion: Makefile distinfo 

Log message:
Update to Apache Subversion 1.8.15. Fixes CVE-2015-5343.

Re: Please add ICU as dependency to Boost (i.e. change the "--without-icu" to "--with-icu") - thoughts?

[Landry Breuil]

On Wed, Dec 16, 2015 at 06:10:17PM +0800, Tinker wrote:
> Aha thank you very much for pointing these things out - great to know there
> was a discussion about it.
> 
> Aha so maybe for OpenBSD 6.0 we'll have an ICU flavor at least.

Flavors in libraries are really a pain to handle, so we try to avoid
those.

Landry

CVS: cvs.openbsd.org: ports

[Stefan Sperling]

CVSROOT:/cvs
Module name:ports
Changes by: s...@cvs.openbsd.org2015/12/16 03:23:18

Modified files:
devel/subversion: Tag: OPENBSD_5_8 Makefile 
Added files:
devel/subversion/patches: Tag: OPENBSD_5_8 
  patch-subversion_mod_dav_svn_util_c 

Log message:
Patch CVE-2015-5343 in Apache Subversion for 5.8-stable.

Re: Here is how to build and install BitcoinD (0.11.2 = latest) on OpenBSD. Can you please make a "net/bitcoin" port of these instructions?

[poweruser]

Guys,

What do you say, do you feel this is a relevant port?



Sorry for not being able to do this myself -

If you need any extra clear feedback or instructions from me for how to 
actually build it, so that you can get the port together, I will be 
happy to guide you, if so let me know.


What made me not be able to make an update of the port complete myself, 
was some weird aspect of how the filenaming works out in the ports 
system and I cannot dig that deep into the system now.


Maybe, I could document exactly what I do when I try to upgrade the 
openbsd-wip bitcoind port, and paste the exact error I get here, and you 
could tell me how to fix it - and we can get the updated BitcoinD port 
into OpenBSD that way,


What do you say?



On 2015-12-16 02:05, poweru...@openmailbox.org wrote:

(

Well, the instructions I provided show exactly how to get the BitcoinD
0.11.2 port going, however, it uses GCC 4.8 for the compilation.

Using OpenBSD's GCC version should work but will require a bit of
experimentation, I think adding
"--disable-tests --disable-debug" to ./configure will be sufficient.
This was pointed out in the original email already.

)

On 2015-12-16 01:22, poweru...@openmailbox.org wrote:

Hi!

I don't know exactly how the port system works.

I figured out exactly how to get BitcoinD latest to build, by manually
patching the openbsd-wip bitcoind port, which is 2.5 years old.

I failed to actually get the port updated, on a stupid detail of the
port Makefile though, it was something about the filenaming scheme the
ports system will use for its build directory -

I am sure YOU know exactly how that works, in no time, so for this
reason I'll describe exactly how to build BitcoinD 0.11.2 = latest on
OpenBSD based on the port here, and you can incredibly quickly pull
together the actual port for it.

Which the exact patches are and the exact configure arguments etc. are
provided, and this is all a patch to the openbsd-wip bitcoind port
already, so the hard work is already done.


Please let me know when you got it in place?

Thanks!!
Poweruser





A google search on this topic mentions
http://www.thedrinkingrecord.com/2015/02/14/notes-on-building-bitcoin-qt-on-openbsd/
also.

Also this post should be followed up on when this port has been
published:
http://unix.stackexchange.com/questions/82858/compiling-bitcoind-on-openbsd

Some things are stated doubly below. In that case just read it as if
was written once.


There is a previous BitcoinD package in openbsd-wip (version 0.9.1).
It's 2.5 years old so it's completely antiquated.

Its sources are at
https://github.com/jasperla/openbsd-wip/tree/master/net/bitcoin , and
this is what my patch here is based on.

I used that one before, and to my experience it worked perfectly,
except for when trying to use BitcoinD's HTTP RPC server - that
crashed when even telnetting to the port I think.. or if it was when
posting any request to it. That functionality is completely secondary
though. I did not test that on this updated version, perhaps it works
now.


My installation instructions are a modified version of the openbsd-wip 
package.


Take that bitcoin directory in the openbsd-wip package, and put it in
your local /usr/ports/net/ directory.


The patch files need some updates. First, let's overview the 8 patch
files individually, as some of these changed names, or disappeared,
since 0.9.1:


 * compat.h is now src/compat.h - attaching new version (applied
exactly the same thing as in the old patch)

 * db.cpp - this file was moved to src/wallet/db.cpp .

 * leveldb/port/port_posix.h is now src/leveldb/port/port_posix.h -
applied same thinga sin patch.

 * src/m4/bitcoin_find_bdb48.m4 changed name to
build-aux/m4/bitcoin_find_bdb48.m4 , applied the same patch contents.

 * can't find src/qt/Makefile.am here.  so i just dropped it.

 * share/genbuild.sh kept its name. figured out what section to 
remove.


 * I didn't touch patch-src_Makefile_include and
patch-contrib_debian_manpages_bitcoind_1 - you figure out what
these should be now please!


And now here below are my patch files, these patches compare the
unmodified bitcoin-0.11.2 tar gz file with what the same need to be to
deliver on OpenBSD. When you compare these patches with the previous
ones you'll see great similarity.

These patches below here were gotten by reading the old openbsd-wip
port patch files and figuring out how to get exactly the same thing in
the new version.




compat.h:  No changes! I.e. remove the patch.

src/wallet/db.cpp:

/tmp/bitcoin-0.11.2$ diff -ur  src/wallet/db.cpp
/usr/ports/pobj/bitcoin-0.11.2/bitcoin-0.11.2/src/wallet/db.cpp
--- src/wallet/db.cpp   Mon Jun  1 00:00:00 2015
+++ /usr/ports/pobj/bitcoin-0.11.2/bitcoin-0.11.2/src/wallet/db.cpp
 Fri Nov 20 19:55:37 2015
@@ -97,7 +97,9 @@
 dbenv->set_errfile(fopen(pathErrorFile.string().c_str(), "a")); 
/// debug

 dbenv->set_flags(DB_AUTO_COMMIT, 1);
 dbenv->set_flags(DB_TXN_WRITE_NOSYNC, 1);
+#if