CVS: cvs.openbsd.org: ports

2019-08-13 Thread Kurt Mosiejczuk
CVSROOT:/cvs
Module name:ports
Changes by: k...@cvs.openbsd.org2019/08/13 17:25:24

Modified files:
devel/flake8   : Makefile distinfo 
devel/flake8/pkg: PLIST 
Removed files:
devel/flake8/patches: patch-setup_py 

Log message:
Update devel/flake8 3.5.0 -> 3.7.7

>From Paco Esteban. Thank you very much!

OK sthen@



CVS: cvs.openbsd.org: ports

2019-08-13 Thread Kurt Mosiejczuk
CVSROOT:/cvs
Module name:ports
Changes by: k...@cvs.openbsd.org2019/08/13 17:19:10

Modified files:
devel/py-codestyle: Makefile distinfo 

Log message:
Update devel/py-codestyle 2.3.1 -> 2.5.0

>From Paco Esteban. Thank you very much!

OK sthen@



CVS: cvs.openbsd.org: ports

2019-08-13 Thread Kurt Mosiejczuk
CVSROOT:/cvs
Module name:ports
Changes by: k...@cvs.openbsd.org2019/08/13 17:14:46

Modified files:
devel/py-entrypoints: Makefile distinfo 
devel/py-entrypoints/pkg: PLIST 

Log message:
Update devel/py-entrypoints 0.2.3 -> 0.3

>From Paco Esteban. Thank you very much!

OK sthen@



Re: Netsurf: get rid of xxd

2019-08-13 Thread Raul Miller
On Tue, Aug 13, 2019 at 5:39 PM Antoine Jacoutot  wrote:
> On Tue, Aug 13, 2019 at 01:42:13AM +, adr wrote:
> > I found a little annoying having to install vim to compile
>
> Not using netsurf so my voice does not really count I suppose.
>
> But 2019... storage price versus developer time to make sure this still works 
> in
> the future makes me wonder the usefullness of this diff.
> Had it been a RUN_DEPENDS, then OK, let's try and fix this. BUILD_DEPENDS...
> who cares??!!! People are supposed to use binary packages.

If it won't compile, what's the point of having the source?

-- 
Raul



Re: cdparanoia release 10.2

2019-08-13 Thread François Chambaud
Kurt Mosiejczuk  writes:

> On Tue, Aug 13, 2019 at 07:46:46PM +0200, Fran??ois Chambaud wrote:
>> Hi ports@,
>
>> I have a lot of audio CDs to rip.  Before I begin this very long
>> process, I have verified the last cdparanoia version at xiph.org
>> website, and I have noticed that there is a new one, available since
>> 2008.
>
>> https://svn.xiph.org/trunk/cdparanoia/README:
>> cdparanoia III release 10.2 README
>> [September 11, 2008]
>> ...
>
>> The current package is cdparanoia-3.a9.8p3.tgz.
>
>> $ uname -prs
>> OpenBSD 6.4 amd64
>> $ cdparanoia -V
>> cdparanoia III release 9.8 (March 23, 2001)
>> (C) 2001 Monty  and Xiphophorus
>
>> Report bugs to paran...@xiph.org
>> http://www.xiph.org/paranoia/
>
>> The current snapshot package is cdparanoia-3.a9.8p4.tgz.
>
>> Is there a technical reason to not have the last release 10.2 of this
>> software?
>
>> The port's maintainer is the list, so I write here.
>
>> Thank you for your time and for this wonderful OS.
>
> You probably haven't looked at actually doing the update. When I was
> starting out I thought I'd update cdparanoia. It's less a port and more
> a rewrite.
>
> libcdio-paranaoia has a cd-paranoia that will do what you want. edd and
> I were vaguely discussing moving folks to using that. The cdio code is
> much more portable and, as I recall, the cdio folks took the paranaoia
> parts into libcdio. I guess perhaps edd and I should look at retiring
> the cdparanoia port in favor of cd-paranoia from libcdio.
>
> --Kurt
>
>

Kurt,

So, if I understand correctly, there is no cdparanoia III release 10.2
available?

$ cd-paranoia -V
cdparanoia III release 9.8 libcdio 0.80 x86_64-unknown-openbsd6.4
(C) 2001 Monty  and Xiphophorus
(C) 2004, 2005, 2008 Rocky Bernstein 

Report bugs to bug-libc...@gnu.org

Here is a link to CD paranoia on top of libcdio (release 10.2):

https://github.com/rocky/libcdio-paranoia

Thank you for your time.

-- 
François Chambaud
www.chambaud.org



CVS: cvs.openbsd.org: ports

2019-08-13 Thread Stuart Henderson
CVSROOT:/cvs
Module name:ports
Changes by: st...@cvs.openbsd.org   2019/08/13 15:40:42

Modified files:
devel/libcoap  : Makefile distinfo 
devel/libcoap/patches: patch-configure_ac 
   patch-examples_client_c 
devel/libcoap/pkg: DESCR PLIST 
Added files:
devel/libcoap/patches: patch-Makefile_am 
Removed files:
devel/libcoap/patches: patch-src_coap_io_c 

Log message:
Update to a newer libcoap snapshot (4.2.0 release works but has some minor
problems, current devel tree works better here). Remove USE_LLD=No and
USE_LIBTOOL=gnu as it now successfully builds and runs without (previously
this had a runtime failure). Tested against ikea tradfri 1.8.26.



Re: Netsurf: get rid of xxd

2019-08-13 Thread Antoine Jacoutot
On Tue, Aug 13, 2019 at 01:42:13AM +, adr wrote:
> Hello,
> 
> I found a little annoying having to install vim to compile

Not using netsurf so my voice does not really count I suppose.

But 2019... storage price versus developer time to make sure this still works in
the future makes me wonder the usefullness of this diff.
Had it been a RUN_DEPENDS, then OK, let's try and fix this. BUILD_DEPENDS...
who cares??!!! People are supposed to use binary packages.

> netsurf.  If you like you can try this patch, and maybe make it
> less ugly, I'm not a make expert.
> 
> By the way, I've compiled netsurf on armv7. It works good.
> 
> Regards,
> adr
> 
> $OpenBSD$
> 
> Index: content/handlers/javascript/duktape/Makefile
> --- content/handlers/javascript/duktape/Makefile.orig
> +++ content/handlers/javascript/duktape/Makefile
> @@ -9,11 +9,18 @@ content/handlers/javascript/duktape/dukky.c: $(OBJROOT
>  BINDINGS := $(wildcard content/handlers/javascript/duktape/*.bnd)
> 
>  # Generator for the C include representing the generics.js
> -$(OBJROOT)/duktape/generics.js.inc: 
> content/handlers/javascript/duktape/generics.js
> +GENERICJS := content/handlers/javascript/duktape/generics.js
> +NAME != echo $(GENERICJS) | sed s';[/.];_;g'
> +ARRAY != hexdump -v -e '/1 "%d,"' $(GENERICJS)
> +LEN != echo $(ARRAY) | awk -F"," '{print NF-1}'
> +$(OBJROOT)/duktape/generics.js.inc: $(GENERICJS)
> $(Q)$(MKDIR) -p $(OBJROOT)/duktape
> $(VQ)echo " XXD: $<"
> -   $(Q)xxd -i $< $@.tmp
> +#  $(Q)xxd -i $< $@.tmp
> +   $(Q)echo "unsigned char $(NAME)[] = { $(ARRAY) };" > $@.tmp
> +   $(Q)echo "unsigned int $(NAME)_len = $(LEN);" >> $@.tmp
> $(Q)sed -e 
> 's/content_handlers_javascript_duktape_generics_js/generics_js/' $@.tmp > $@
> 
>  # ensure genbind generates debugging files
>  GBFLAGS+=-D
> ~
> 

-- 
Antoine



CVS: cvs.openbsd.org: ports

2019-08-13 Thread Stuart Henderson
CVSROOT:/cvs
Module name:ports
Changes by: st...@cvs.openbsd.org   2019/08/13 15:14:11

Modified files:
www/apache-httpd: Makefile distinfo 
www/apache-httpd/patches: patch-Makefile_in patch-config_layout 
  patch-configure 
  patch-docs_conf_httpd_conf_in 
  patch-docs_man_htpasswd_1 
  patch-docs_man_httpd_8 
  patch-modules_ssl_ssl_engine_init_c 
  patch-modules_ssl_ssl_private_h 
  patch-server_mpm_unix_c 
  patch-support_apachectl_in 
  patch-support_apxs_in 
  patch-support_rotatelogs_c 
www/apache-httpd/pkg: PLIST 
Removed files:
www/apache-httpd/patches: patch-modules_filters_mod_reqtimeout_c 

Log message:
update to apache-httpd 2.4.41



CVS: cvs.openbsd.org: ports

2019-08-13 Thread Brian Callahan
CVSROOT:/cvs
Module name:ports
Changes by: bcal...@cvs.openbsd.org 2019/08/13 14:38:50

Modified files:
math/ebc   : Makefile distinfo 

Log message:
Update to ebc-2.1.3
Changelog: https://github.com/gavinhoward/bc/releases/tag/2.1.3



CVS: cvs.openbsd.org: ports

2019-08-13 Thread Gilles Chehade
CVSROOT:/cvs
Module name:ports
Changes by: gil...@cvs.openbsd.org  2019/08/13 14:29:43

Modified files:
mail   : Makefile 

Log message:
link mail/opensmtpd-filter-rspamd to the build



Re: cdparanoia release 10.2

2019-08-13 Thread Kurt Mosiejczuk
On Tue, Aug 13, 2019 at 07:46:46PM +0200, Fran??ois Chambaud wrote:
> Hi ports@,

> I have a lot of audio CDs to rip.  Before I begin this very long
> process, I have verified the last cdparanoia version at xiph.org
> website, and I have noticed that there is a new one, available since
> 2008.

> https://svn.xiph.org/trunk/cdparanoia/README:
> cdparanoia III release 10.2 README
> [September 11, 2008]
> ...

> The current package is cdparanoia-3.a9.8p3.tgz.

> $ uname -prs
> OpenBSD 6.4 amd64
> $ cdparanoia -V
> cdparanoia III release 9.8 (March 23, 2001)
> (C) 2001 Monty  and Xiphophorus

> Report bugs to paran...@xiph.org
> http://www.xiph.org/paranoia/

> The current snapshot package is cdparanoia-3.a9.8p4.tgz.

> Is there a technical reason to not have the last release 10.2 of this
> software?

> The port's maintainer is the list, so I write here.

> Thank you for your time and for this wonderful OS.

You probably haven't looked at actually doing the update. When I was
starting out I thought I'd update cdparanoia. It's less a port and more
a rewrite.

libcdio-paranaoia has a cd-paranoia that will do what you want. edd and
I were vaguely discussing moving folks to using that. The cdio code is
much more portable and, as I recall, the cdio folks took the paranaoia
parts into libcdio. I guess perhaps edd and I should look at retiring
the cdparanoia port in favor of cd-paranoia from libcdio.

--Kurt



cdparanoia release 10.2

2019-08-13 Thread François Chambaud
Hi ports@,

I have a lot of audio CDs to rip.  Before I begin this very long
process, I have verified the last cdparanoia version at xiph.org
website, and I have noticed that there is a new one, available since
2008.

https://svn.xiph.org/trunk/cdparanoia/README:
cdparanoia III release 10.2 README
[September 11, 2008]
...

The current package is cdparanoia-3.a9.8p3.tgz.

$ uname -prs
OpenBSD 6.4 amd64
$ cdparanoia -V
cdparanoia III release 9.8 (March 23, 2001)
(C) 2001 Monty  and Xiphophorus

Report bugs to paran...@xiph.org
http://www.xiph.org/paranoia/

The current snapshot package is cdparanoia-3.a9.8p4.tgz.

Is there a technical reason to not have the last release 10.2 of this
software?

The port's maintainer is the list, so I write here.

Thank you for your time and for this wonderful OS.

-- 
François Chambaud
www.chambaud.org



CVS: cvs.openbsd.org: ports

2019-08-13 Thread Gilles Chehade
CVSROOT:/cvs
Module name:ports
Changes by: gil...@cvs.openbsd.org  2019/08/13 12:40:10

Log message:
import mail/opensmtpd-filter-rspamd, an rspamd integration for OpenSMTPD

ok landry@ and kn@

Status:

Vendor Tag: gilles
Release Tags:   gilles_20190813

N ports/mail/opensmtpd-filter-rspamd/Makefile
N ports/mail/opensmtpd-filter-rspamd/distinfo
N ports/mail/opensmtpd-filter-rspamd/pkg/PLIST
N ports/mail/opensmtpd-filter-rspamd/pkg/README
N ports/mail/opensmtpd-filter-rspamd/pkg/DESCR

No conflicts created by this import



CVS: cvs.openbsd.org: ports

2019-08-13 Thread Peter Hessler
CVSROOT:/cvs
Module name:ports
Changes by: phess...@cvs.openbsd.org2019/08/13 12:13:53

Modified files:
x11/gtk+4  : Makefile 

Log message:
gtk+4,-cups depends on colord on aarch64, too

while here, sort the list of arches

OK ajacoutot@



CVS: cvs.openbsd.org: ports

2019-08-13 Thread Peter Hessler
CVSROOT:/cvs
Module name:ports
Changes by: phess...@cvs.openbsd.org2019/08/13 12:10:11

Modified files:
audio/chromaprint/patches: patch-tests_CMakeLists_txt 

Log message:
some of the tests depend on signed char, which is not true on several arches
remove those tests temporarily, they will be fixed in the upcoming 1.4.3 update

no bump, because the tests are not included in the package

OK cwen@



Re: New: mail/opensmtpd-filter-rspamd

2019-08-13 Thread Klemens Nanni
On Tue, Aug 13, 2019 at 06:28:47PM +0100, Stuart Henderson wrote:
> In the unlikely event anyone is actually resetting SYSCONFDIR, it only applies
> to ports not things from base like smtpd.conf. but the bin path should use a
> ports variable. So README needs this diff.
OK with that, thanks.



[wip] Xfce 4.14 final

2019-08-13 Thread Landry Breuil
On Mon, Jul 01, 2019 at 09:33:04AM +0200, Landry Breuil wrote:
> On Sat, May 25, 2019 at 06:43:49PM +0200, Landry Breuil wrote:
> > Hi,
> > 
> > since some years now i've been maintaining x11/xfce4 in the portstree,
> > with an alternate repo at https://cgit.rhaalovely.net/xfce4/?h=next
> > tracking upstream devel releases. This repo now contains all the bits
> > composing 4.14pre1 (cf
> > https://simon.shimmerproject.org/2019/05/19/xfce-4-14pre1-released/ for
> > the details, the main thing being of course the complete port to Gtk+3),
> > the final release being targeted at sometimes during the summer.
> > 
> > as an upstream developer i've of course been running it during the
> > development cycle on most of my boxes, but now would be a good time for
> > other Xfce users on OpenBSD to give it a shot and eventually report some
> > bugs to https://bugzilla.xfce.org.
> > 
> > The main OpenBSD-specific change is
> > https://bugzilla.xfce.org/show_bug.cgi?id=14722 (needs testing !)
> > which will make the consolekit/policykit/messagebus dependency
> > completely optional, allowing an user in the operator group to shutdown
> > the machine (ie can run the shutdown binary), or suspend/hibernate if in
> > the wheel group (ie has access to apmdev), instead of relying on 3
> > daemons running as root. The previous mode of needing messagebus
> > running + spawning startxfce4 within consolekit should still work.
> > 
> > amd64 -current packages for all core xfce pkgs (and some others i'm
> > using) are available at https://packages.rhaalovely.net/wip/amd64/
> > (signed with https://packages.rhaalovely.net/landry-mozilla-pkg.pub)
> > 
> > barring delays, this should make 6.6, but it's better if it's been
> > "widely" tested before..
> 
> Fwiw, all updated to 4.14pre2, per
> https://wiki.xfce.org/releng/4.14/xfce_4.14pre2.
> Feedback & testing still welcome.

The same wip repo at https://packages.rhaalovely.net/wip/amd64/ now has
4.14 final (cf https://xfce.org/about/news/?post=1565568000), packages
built against 6.6-beta. Got very few reports from testers, sadly.. now
is the time to test before i commit it soon.

Landry



Re: New: mail/opensmtpd-filter-rspamd

2019-08-13 Thread Stuart Henderson
On 2019/08/13 16:23, gil...@poolp.org wrote:
> 13 août 2019 13:27 "Klemens Nanni"  a écrit:
> 
> > On Tue, Aug 13, 2019 at 11:32:37AM +0200, Landry Breuil wrote:
> > 
> >> Sorry, but i dont think this makes sense. With your reasoning, 2 extra
> >> lines will be displayed at the end of pkg_add, for a 2-lines README.
> >> lots of indirections for not much information... and we already know
> >> users dont read them anyway.
> > 
> > I agree that the indirection could be avoided, but people *do* read
> > these readmes.
> > 
> >> I doubt ppl will come to filter-rspamd directly (and then wonder how to
> >> set it up, in that case they will lookup HOMEPAGE), they might be more
> >> 'directed' at it by a mention of this same example in smtpd.conf(5) or a
> >> commented out entry in the default smtpd.conf.
> > 
> > Well, I know smtpd and we have packages for it, so I search the packages
> > to see what I can do. I hate having to open some HOMEPAGE only to find
> > out how to use a port: that is was README and/or MESSAGE is for.
> > 
> > My goal is to provide packages which include all neccessary information
> > if possible, without forcing users through web browsers.
> > 
> >> Adding a README for 2 lines is abusing the README mechanism imo.
> > 
> > I'm also fine with amending DESCR or putting it in MESSAGE, as long as
> > I don't have to guess where to start after installing the package,
> > because I personally would be one of those users that would install it
> > only to find no manual or documentation whatsoever, angrily going though
> > smtpd(8) and smtpd.conf(5) first hoping for examples, then falling back
> > to the web.
> 
> I have added a README
> 
> ok ?

In the unlikely event anyone is actually resetting SYSCONFDIR, it only applies
to ports not things from base like smtpd.conf. but the bin path should use a
ports variable. So README needs this diff.

Rest looks good to me but I haven't tested the port.


--- README- Tue Aug 13 18:25:03 2019
+++ README  Tue Aug 13 18:25:56 2019
@@ -6,9 +6,9 @@ $OpenBSD$
 
 To use filter-rspamd, you must declare it in smtpd.
 
-Edit the ${SYSCONFDIR}/mail/smtpd.conf file to declare the filter:
+Edit the /etc/mail/smtpd.conf file to declare the filter:
 
-  filter "rspamd" proc-exec "/usr/local/bin/filter-rspamd"
+  filter "rspamd" proc-exec "${PREFIX}/bin/filter-rspamd"
 
 Then add the filter to each listener that should be filtered:
 



Re: New: mail/opensmtpd-filter-rspamd

2019-08-13 Thread gilles
13 août 2019 12:38 "Gonzalo L. Rodriguez"  a écrit:

> On Tue, 13 Aug 2019 at 11:43:23 +0200, Gonzalo L. Rodriguez wrote:
> 
>> On Tue, 13 Aug 2019 at 11:18:33 +0200, Klemens Nanni wrote:
>> On Tue, Aug 13, 2019 at 08:37:18AM +, Gilles Chehade wrote:
>>> filter-rspamd doesn't have any configuration itself, all it needs is for 
>>> smtpd.conf to reference
>> it:
>>> 
>>> filter "rspamd" proc-exec "/usr/local/bin/filter-rspamd"
>>> listen on all filter "rspamd"
>>> 
>>> I thought I'd add this as an example to the smtpd.conf(5) man page itself.
>> Sounds good.
>> 
>>> Should I add a README in the port too ?
>> Yes please, either reference smtpd.conf(5) or just include the same
>> example here. Adding a pkg/README to the port should do it; this way
>> pkg_add would tell you
>> 
>> opensmtpd-filter-rspamd-X.Y: ok
>> New and changed readme(s):
>> /usr/local/share/doc/pkg-readmes/opensmtpd-filter-rspamd
>> 
>> so users know immediately how to set things up.
>> 
>> That would be nice.
>> 
>> --
>> 
>> - gonzalo
> 
> BTW, are you planning to merge this port with opensmtpd-extras? Or are
> different stuff?
> 

No I don't plan to merge this port with opensmtpd-extras because they're 
different stuff.



Re: New: mail/opensmtpd-filter-rspamd

2019-08-13 Thread gilles
13 août 2019 13:27 "Klemens Nanni"  a écrit:

> On Tue, Aug 13, 2019 at 11:32:37AM +0200, Landry Breuil wrote:
> 
>> Sorry, but i dont think this makes sense. With your reasoning, 2 extra
>> lines will be displayed at the end of pkg_add, for a 2-lines README.
>> lots of indirections for not much information... and we already know
>> users dont read them anyway.
> 
> I agree that the indirection could be avoided, but people *do* read
> these readmes.
> 
>> I doubt ppl will come to filter-rspamd directly (and then wonder how to
>> set it up, in that case they will lookup HOMEPAGE), they might be more
>> 'directed' at it by a mention of this same example in smtpd.conf(5) or a
>> commented out entry in the default smtpd.conf.
> 
> Well, I know smtpd and we have packages for it, so I search the packages
> to see what I can do. I hate having to open some HOMEPAGE only to find
> out how to use a port: that is was README and/or MESSAGE is for.
> 
> My goal is to provide packages which include all neccessary information
> if possible, without forcing users through web browsers.
> 
>> Adding a README for 2 lines is abusing the README mechanism imo.
> 
> I'm also fine with amending DESCR or putting it in MESSAGE, as long as
> I don't have to guess where to start after installing the package,
> because I personally would be one of those users that would install it
> only to find no manual or documentation whatsoever, angrily going though
> smtpd(8) and smtpd.conf(5) first hoping for examples, then falling back
> to the web.

I have added a README

ok ?


opensmtpd-filter-rspamd.tar.gz
Description: GNU Zip compressed data


CVS: cvs.openbsd.org: ports

2019-08-13 Thread Frederic Cambus
CVSROOT:/cvs
Module name:ports
Changes by: fcam...@cvs.openbsd.org 2019/08/13 09:55:41

Modified files:
astro/ansiweather: Makefile distinfo 

Log message:
Update ansiweather to 1.14.0.



CVS: cvs.openbsd.org: ports

2019-08-13 Thread Kurt Mosiejczuk
CVSROOT:/cvs
Module name:ports
Changes by: k...@cvs.openbsd.org2019/08/13 09:37:14

Modified files:
textproc/py-xmldiff: Makefile 
textproc/py-xmldiff/pkg: PLIST 

Log message:
The upgrade path from py-xmldiff to py3-xmldiff won't work as it
was. Needed to add "@conflict" with py-xmldiff and "@pkgpath
textproc/py-xmldiff". Then it will work.

>From and OK sthen@



Re: Update: textproc/py-xmldiff 0.6.10 -> 2.3

2019-08-13 Thread Stuart Henderson
On 2019/08/13 11:30, Kurt Mosiejczuk wrote:
> On Tue, Aug 13, 2019 at 03:17:58PM +0100, Stuart Henderson wrote:
> 
> > Because the stem changes from py-xmldiff to py3-xmldiff, this will need more
> > work in order that the update is picked up.
> 
> > Untested but I think it will need
> 
> > @conflict py-xmldiff-*
> > @pkgpath textproc/py-xmldiff
> 
> > If unsure, please test update paths:
> 
> > - build new packages for the port itself + devel/quirks, move them to
> > a directory on their own e.g. /tmp/test
> 
> > - install the old packages (e.g. uninstall the new packages after testing
> > and pkg_add the old ones from mirrors)
> 
> > - "PKG_PATH=/tmp/test pkg_add -D unsigned -u" and check that the relevant
> > package/s were updated (there will be a bunch of "no update for XX" noise
> > for unrelated packages on the sytem of course that can be ignored)
> 
> That does work. (I did have to install py3-six and py3-lxml first since
> they are new dependencies).
> 
> Here's the diff. OK to commit?

Thanks, OK.

> --Kurt
> 
> Index: Makefile
> ===
> RCS file: /cvs/ports/textproc/py-xmldiff/Makefile,v
> retrieving revision 1.9
> diff -u -p -r1.9 Makefile
> --- Makefile  13 Aug 2019 13:04:54 -  1.9
> +++ Makefile  13 Aug 2019 15:28:27 -
> @@ -6,6 +6,7 @@ MODPY_EGG_VERSION=2.3
>  DISTNAME=xmldiff-${MODPY_EGG_VERSION}
>  PKGNAME= py-xmldiff-${MODPY_EGG_VERSION}
>  CATEGORIES=  textproc
> +REVISION=0
>  
>  HOMEPAGE=https://github.com/Shoobx/xmldiff
>  
> Index: pkg/PLIST
> ===
> RCS file: /cvs/ports/textproc/py-xmldiff/pkg/PLIST,v
> retrieving revision 1.2
> diff -u -p -r1.2 PLIST
> --- pkg/PLIST 13 Aug 2019 13:04:54 -  1.2
> +++ pkg/PLIST 13 Aug 2019 15:28:27 -
> @@ -1,4 +1,6 @@
>  @comment $OpenBSD: PLIST,v 1.2 2019/08/13 13:04:54 kmos Exp $
> +@conflict py-xmldiff-*
> +@pkgpath textproc/py-xmldiff
>  bin/xmldiff
>  bin/xmlpatch
>  lib/python${MODPY_VERSION}/site-packages/xmldiff/



CVS: cvs.openbsd.org: ports

2019-08-13 Thread Stefan Sperling
CVSROOT:/cvs
Module name:ports
Changes by: s...@cvs.openbsd.org2019/08/13 09:20:03

Modified files:
devel/got  : Makefile distinfo 

Log message:
update to got-0.7
- properly parse timestamps in commit objects as UTC (patch by Hiltjo Posthuma)
- strip Git GPG signatures from log messages
- fix regression: don't try to parse "leightweight" tags as real tag objects



Update: lang/jruby 9.2.7.0 -> 9.2.8.0

2019-08-13 Thread Jeremy Evans
Simple update to the latest release of JRuby.  Release announcement at
https://www.jruby.org/2019/08/12/jruby-9-2-8-0.html

Tested on amd64, the only supported arch.  Will be committing in a
couple days unless I hear objections.

Thanks,
Jeremy

Index: Makefile
===
RCS file: /cvs/ports/lang/jruby/Makefile,v
retrieving revision 1.80
diff -u -p -r1.80 Makefile
--- Makefile12 Jul 2019 20:47:19 -  1.80
+++ Makefile13 Aug 2019 15:06:54 -
@@ -5,8 +5,7 @@ ONLY_FOR_ARCHS = amd64
 
 COMMENT =  pure-Java implementation of the Ruby language
 
-V =9.2.7.0
-REVISION = 1
+V =9.2.8.0
 DISTNAME = jruby-dist-${V}-bin
 PKGNAME =  jruby-${V}
 CATEGORIES =   lang lang/ruby
Index: distinfo
===
RCS file: /cvs/ports/lang/jruby/distinfo,v
retrieving revision 1.50
diff -u -p -r1.50 distinfo
--- distinfo18 May 2019 16:03:47 -  1.50
+++ distinfo13 Aug 2019 15:06:54 -
@@ -1,6 +1,6 @@
 SHA256 (jffi-1.2.18.tar.gz) = BTJsmFFT5MhkSblzLLqjnHVw8HnNDxJ2wvXfQOusvZI=
-SHA256 (jruby-dist-9.2.7.0-bin.tar.gz) = 
2nwaXOkAFcC6/UvKA1IpTgj+HJ7ASaxR6C/lftUOE0g=
+SHA256 (jruby-dist-9.2.8.0-bin.tar.gz) = 
t8WGiAk/VKzYnXMqi/QOOuCsTJJIjW9bQkwz5PsJx7s=
 SHA256 (jruby-launcher-1.1.9-java.gem) = 
9prnUcy0VqolcmXSsZR5HWWWrFr2cNZVZyH3DHQcEdU=
 SIZE (jffi-1.2.18.tar.gz) = 2210133
-SIZE (jruby-dist-9.2.7.0-bin.tar.gz) = 25630203
+SIZE (jruby-dist-9.2.8.0-bin.tar.gz) = 24808185
 SIZE (jruby-launcher-1.1.9-java.gem) = 65024
Index: pkg/PLIST
===
RCS file: /cvs/ports/lang/jruby/pkg/PLIST,v
retrieving revision 1.44
diff -u -p -r1.44 PLIST
--- pkg/PLIST   26 Apr 2019 15:46:58 -  1.44
+++ pkg/PLIST   13 Aug 2019 15:06:54 -
@@ -27,365 +27,14 @@ jruby/lib/ruby/2.0/site_ruby/
 jruby/lib/ruby/gems/
 jruby/lib/ruby/gems/1.8/
 jruby/lib/ruby/gems/1.8/cache/
-jruby/lib/ruby/gems/1.8/cache/bundler-1.16.6.gem
 jruby/lib/ruby/gems/1.8/cache/did_you_mean-1.2.0.gem
 jruby/lib/ruby/gems/1.8/cache/minitest-5.10.3.gem
 jruby/lib/ruby/gems/1.8/cache/net-telnet-0.1.1.gem
 jruby/lib/ruby/gems/1.8/cache/power_assert-1.1.3.gem
-jruby/lib/ruby/gems/1.8/cache/rake-12.3.0.gem
+jruby/lib/ruby/gems/1.8/cache/rake-12.3.2.gem
 jruby/lib/ruby/gems/1.8/cache/test-unit-3.2.8.gem
 jruby/lib/ruby/gems/1.8/cache/xmlrpc-0.3.0.gem
 jruby/lib/ruby/gems/1.8/gems/
-jruby/lib/ruby/gems/1.8/gems/bundler-1.16.6/
-jruby/lib/ruby/gems/1.8/gems/bundler-1.16.6/CHANGELOG.md
-jruby/lib/ruby/gems/1.8/gems/bundler-1.16.6/LICENSE.md
-jruby/lib/ruby/gems/1.8/gems/bundler-1.16.6/README.md
-jruby/lib/ruby/gems/1.8/gems/bundler-1.16.6/bundler.gemspec
-jruby/lib/ruby/gems/1.8/gems/bundler-1.16.6/exe/
-jruby/lib/ruby/gems/1.8/gems/bundler-1.16.6/exe/bundle
-jruby/lib/ruby/gems/1.8/gems/bundler-1.16.6/exe/bundle_ruby
-jruby/lib/ruby/gems/1.8/gems/bundler-1.16.6/exe/bundler
-jruby/lib/ruby/gems/1.8/gems/bundler-1.16.6/lib/
-jruby/lib/ruby/gems/1.8/gems/bundler-1.16.6/lib/bundler/
-jruby/lib/ruby/gems/1.8/gems/bundler-1.16.6/lib/bundler.rb
-jruby/lib/ruby/gems/1.8/gems/bundler-1.16.6/lib/bundler/build_metadata.rb
-jruby/lib/ruby/gems/1.8/gems/bundler-1.16.6/lib/bundler/capistrano.rb
-jruby/lib/ruby/gems/1.8/gems/bundler-1.16.6/lib/bundler/cli/
-jruby/lib/ruby/gems/1.8/gems/bundler-1.16.6/lib/bundler/cli.rb
-jruby/lib/ruby/gems/1.8/gems/bundler-1.16.6/lib/bundler/cli/add.rb
-jruby/lib/ruby/gems/1.8/gems/bundler-1.16.6/lib/bundler/cli/binstubs.rb
-jruby/lib/ruby/gems/1.8/gems/bundler-1.16.6/lib/bundler/cli/cache.rb
-jruby/lib/ruby/gems/1.8/gems/bundler-1.16.6/lib/bundler/cli/check.rb
-jruby/lib/ruby/gems/1.8/gems/bundler-1.16.6/lib/bundler/cli/clean.rb
-jruby/lib/ruby/gems/1.8/gems/bundler-1.16.6/lib/bundler/cli/common.rb
-jruby/lib/ruby/gems/1.8/gems/bundler-1.16.6/lib/bundler/cli/config.rb
-jruby/lib/ruby/gems/1.8/gems/bundler-1.16.6/lib/bundler/cli/console.rb
-jruby/lib/ruby/gems/1.8/gems/bundler-1.16.6/lib/bundler/cli/doctor.rb
-jruby/lib/ruby/gems/1.8/gems/bundler-1.16.6/lib/bundler/cli/exec.rb
-jruby/lib/ruby/gems/1.8/gems/bundler-1.16.6/lib/bundler/cli/gem.rb
-jruby/lib/ruby/gems/1.8/gems/bundler-1.16.6/lib/bundler/cli/info.rb
-jruby/lib/ruby/gems/1.8/gems/bundler-1.16.6/lib/bundler/cli/init.rb
-jruby/lib/ruby/gems/1.8/gems/bundler-1.16.6/lib/bundler/cli/inject.rb
-jruby/lib/ruby/gems/1.8/gems/bundler-1.16.6/lib/bundler/cli/install.rb
-jruby/lib/ruby/gems/1.8/gems/bundler-1.16.6/lib/bundler/cli/issue.rb
-jruby/lib/ruby/gems/1.8/gems/bundler-1.16.6/lib/bundler/cli/list.rb
-jruby/lib/ruby/gems/1.8/gems/bundler-1.16.6/lib/bundler/cli/lock.rb
-jruby/lib/ruby/gems/1.8/gems/bundler-1.16.6/lib/bundler/cli/open.rb
-jruby/lib/ruby/gems/1.8/gems/bundler-1.16.6/lib/bundler/cli/outdated.rb
-jruby/lib/ruby/gems/1.8/gems/bundler-1.16.6/lib/bundler/cli/package.rb
-jruby/lib/ruby/gems/1.8/gems/bundler-1.16.6/lib/bundler/cli/platform.rb

CVS: cvs.openbsd.org: ports

2019-08-13 Thread Stuart Henderson
CVSROOT:/cvs
Module name:ports
Changes by: st...@cvs.openbsd.org   2019/08/13 08:50:13

Modified files:
audio/clementine: Makefile distinfo 

Log message:
use standard GH_*



Re: Update: textproc/py-xmldiff 0.6.10 -> 2.3

2019-08-13 Thread Stuart Henderson
On 2019/08/12 21:04, Kurt Mosiejczuk wrote:
> On Mon, Aug 12, 2019 at 08:03:16PM -0400, Kurt Mosiejczuk wrote:
> > On Mon, Aug 12, 2019 at 06:44:46PM -0400, Daniel Jakots wrote:
> > > On Mon, 12 Aug 2019 18:32:16 -0400, Kurt Mosiejczuk 
> > > wrote:
> 
> > > > +FLAVORS=   python3
> > > > +FLAVOR?=
> 
> > > Isn't it just a tool? Maybe it's more meaningful to just provide a py3
> > > version. What's your opinion?
> 
> > That is actually an excellent point. It had been python 2 only so I was
> > more concerned with adding python3.
> 
> > Actually, going one flavor is required as it is. It installs plain binaries
> > (xmldiff, xmlpatch) and I didn't throw a suffix on them.
> 
> > I'll rework it to be python3 only and then have a quirks diff to migrate
> > folks from py-xmldiff to py3-xmldiff.
> 
> Here's a new version of the diff making it python3 only.  I'm also including
> a quirks diff at the end that will migrate folks from py-xmldiff to
> py3-xmldiff.

Because the stem changes from py-xmldiff to py3-xmldiff, this will need more
work in order that the update is picked up.

Untested but I think it will need

@conflict py-xmldiff-*
@pkgpath textproc/py-xmldiff

If unsure, please test update paths:

- build new packages for the port itself + devel/quirks, move them to
a directory on their own e.g. /tmp/test

- install the old packages (e.g. uninstall the new packages after testing
and pkg_add the old ones from mirrors)

- "PKG_PATH=/tmp/test pkg_add -D unsigned -u" and check that the relevant
package/s were updated (there will be a bunch of "no update for XX" noise
for unrelated packages on the sytem of course that can be ignored)


> --Kurt
> 
> Index: Makefile
> ===
> RCS file: /cvs/ports/textproc/py-xmldiff/Makefile,v
> retrieving revision 1.8
> diff -u -p -r1.8 Makefile
> --- Makefile  12 Jul 2019 20:50:14 -  1.8
> +++ Makefile  13 Aug 2019 01:02:40 -
> @@ -2,33 +2,24 @@
>  
>  COMMENT= show differences between XML files/DOM trees
>  
> -MODPY_EGG_VERSION=   0.6.10
> +MODPY_EGG_VERSION=   2.3
>  DISTNAME=xmldiff-${MODPY_EGG_VERSION}
>  PKGNAME= py-xmldiff-${MODPY_EGG_VERSION}
> -REVISION=3
>  CATEGORIES=  textproc
>  
> -HOMEPAGE=http://www.logilab.org/859/
> +HOMEPAGE=https://github.com/Shoobx/xmldiff
>  
> -# GPLv2
> +# MIT
>  PERMIT_PACKAGE=  Yes
>  
> -WANTLIB += ${MODPY_WANTLIB}
> -WANTLIB += pthread
> -
>  MODULES= lang/python
>  
> -MASTER_SITES=http://ftp.logilab.org/pub/xmldiff/
> -
> -RUN_DEPENDS= shells/bash \
> - textproc/py-xml
> -
> +MODPY_PI=Yes
> +MODPY_SETUPTOOLS=Yes
>  
> -pre-configure:
> - ${SUBST_CMD} ${WRKSRC}/bin/{xmldiff,xmlrev}
> +MODPY_VERSION=   ${MODPY_DEFAULT_VERSION_3}
>  
> -do-test:
> - @cd ${WRKSRC}/test/ && \
> - ${MODPY_BIN} runtests.py
> +RUN_DEPENDS= devel/py-six${MODPY_FLAVOR} \
> + textproc/py-lxml${MODPY_FLAVOR}
>  
>  .include 
> Index: distinfo
> ===
> RCS file: /cvs/ports/textproc/py-xmldiff/distinfo,v
> retrieving revision 1.2
> diff -u -p -r1.2 distinfo
> --- distinfo  18 Jan 2015 03:15:30 -  1.2
> +++ distinfo  13 Aug 2019 01:02:40 -
> @@ -1,2 +1,2 @@
> -SHA256 (xmldiff-0.6.10.tar.gz) = g6uiUt8vdgyL8Ai5xdMICRHqstKznDcdO0f2er9LTsU=
> -SIZE (xmldiff-0.6.10.tar.gz) = 45827
> +SHA256 (xmldiff-2.3.tar.gz) = Jyf2KrWQwfyDToYDOYinaoamf1p4GWWEBJt6civZRGY=
> +SIZE (xmldiff-2.3.tar.gz) = 95947
> Index: patches/patch-bin_xmldiff
> ===
> RCS file: patches/patch-bin_xmldiff
> diff -N patches/patch-bin_xmldiff
> --- patches/patch-bin_xmldiff 21 Sep 2010 20:31:13 -  1.1.1.1
> +++ /dev/null 1 Jan 1970 00:00:00 -
> @@ -1,9 +0,0 @@
> -$OpenBSD: patch-bin_xmldiff,v 1.1.1.1 2010/09/21 20:31:13 jasper Exp $
>  bin/xmldiff.orig Tue Sep 21 20:30:40 2010
> -+++ bin/xmldiff  Tue Sep 21 20:30:48 2010
> -@@ -1,4 +1,4 @@
> --#!/usr/bin/python
> -+#!${MODPY_BIN}
> - 
> - from xmldiff import main 
> - main.run()
> Index: patches/patch-bin_xmlrev
> ===
> RCS file: patches/patch-bin_xmlrev
> diff -N patches/patch-bin_xmlrev
> --- patches/patch-bin_xmlrev  21 Sep 2010 20:31:13 -  1.1.1.1
> +++ /dev/null 1 Jan 1970 00:00:00 -
> @@ -1,9 +0,0 @@
> -$OpenBSD: patch-bin_xmlrev,v 1.1.1.1 2010/09/21 20:31:13 jasper Exp $
>  bin/xmlrev.orig  Tue Sep 21 20:31:30 2010
> -+++ bin/xmlrev   Tue Sep 21 20:31:39 2010
> -@@ -1,4 +1,4 @@
> --#!/bin/bash
> -+#!${LOCALBASE}/bin/bash
> - #
> - # (c) 2001-2004 Nicolas Chauvat  - License is 
> GPL
> - 
> Index: pkg/PLIST
> ===
> RCS file: 

CVS: cvs.openbsd.org: ports

2019-08-13 Thread Solene Rapenne
CVSROOT:/cvs
Module name:ports
Changes by: sol...@cvs.openbsd.org  2019/08/13 08:11:05

Modified files:
mail/exim  : Tag: OPENBSD_6_5 Makefile 

Log message:
Fixing my previous bad fix.
PERMIT_PACKAGE used to be PERMIT_PACKAGE_CDROM and not
PERMIT_PACKAGE_WITH_CDROM..



CVS: cvs.openbsd.org: ports

2019-08-13 Thread Charlene Wendling
CVSROOT:/cvs
Module name:ports
Changes by: c...@cvs.openbsd.org2019/08/13 07:36:00

Modified files:
cad/gnucap : Makefile 
Added files:
cad/gnucap/patches: patch-src_plot_cc 

Log message:
gnucap: fix the build with ports-gcc

OK bentley@



回复: [security update] www/py-django : Update django to 2.2.4 and 1.11.23

2019-08-13 Thread wen heping
ping ...

发件人: owner-po...@openbsd.org  代表 wen heping 

发送时间: 2019年8月8日 22:25
收件人: ports@openbsd.org 
主题: [security update] www/py-django : Update django to 2.2.4 and 1.11.23

Hi, ports@:

   Here is a patch for www/py-django:
  i) Update stable to 2.2.4 and lts to 1.11.23, which fixed
  CVE-2019-14232
  CVE-2019-14233
  CVE-2019-14234
  CVE-2019-14235
   ii) Add devel/py-tblib as TEST_DEPENDS, which will enable django
do mre tests.
 py-tblib is a new port which I submitted just now.

 It build well and run well on amd64-head system.
 Three(total  over 1) tests failed, but it was not caused by this 
update.

Comments? OK?
wen



回复: ????: [NEW] devel/py-tblib

2019-08-13 Thread wen heping
Now MODPY_EGG_VERSION go above DISTNAME. Thank kmos@

wen


发件人: Kurt Mosiejczuk 
发送时间: 2019年8月9日 12:14
收件人: wen heping 
抄送: ports@openbsd.org 
主题: Re: : [NEW] devel/py-tblib

On Thu, Aug 08, 2019 at 11:45:50PM +, wen heping wrote:
> Revised patch based on kmos@ comments.

MODPY_EGG_VERSION should go above DISTNAME. With that moved, ok kmos@

--Kurt


py-tblib-p1.tar.gz
Description: py-tblib-p1.tar.gz


CVS: cvs.openbsd.org: ports

2019-08-13 Thread Kurt Mosiejczuk
CVSROOT:/cvs
Module name:ports
Changes by: k...@cvs.openbsd.org2019/08/13 07:07:11

Modified files:
devel/quirks   : Makefile 
devel/quirks/files: Quirks.pm 

Log message:
Update quirks to reflect py-xmldiff's migration to python3
(py-xmldiff -> py3-xmldiff)

ok landry@



CVS: cvs.openbsd.org: ports

2019-08-13 Thread Kurt Mosiejczuk
CVSROOT:/cvs
Module name:ports
Changes by: k...@cvs.openbsd.org2019/08/13 07:04:54

Modified files:
textproc/py-xmldiff: Makefile distinfo 
textproc/py-xmldiff/pkg: PLIST 
Removed files:
textproc/py-xmldiff/patches: patch-bin_xmldiff patch-bin_xmlrev 

Log message:
Update textproc/py-xmldiff 0.6.10 -> 2.3

py-xmldiff hasn't been updated in a long time, but it still gets used.
So time to update it. Current 2.x versions are a rewrite in pure python.

Patches go away. Port moved to use MODPY_PI and MODPY_SETUPTOOLS.

Move it to python3 only since executable is just xmldiff and xmlpatch.

OK landry@



CVS: cvs.openbsd.org: ports

2019-08-13 Thread Stefan Sperling
CVSROOT:/cvs
Module name:ports
Changes by: s...@cvs.openbsd.org2019/08/13 06:25:54

Modified files:
devel/got  : Makefile distinfo 

Log message:
Update to got-0.6
- 'got log' and 'tog log' now display tags in addition to branch references
- 'got ref' can now be used to create symbolic references
- use  instead of  (patch by Thomas Klausner)
- fix crash if 'got rebase' has no commits to rebase (with semarie@)
- annotate symlinks with @ in 'got tree' and 'tog tree'



Re: audio/chromaprint: fix compilation on unsigned char arches

2019-08-13 Thread Charlene Wendling
Hi,

On Tue, 13 Aug 2019 08:14:24 +0200
Peter Hessler wrote:

> test_bit_string_* both use constructs like:
> 
>   char data[] = { -28 };
> 
> which won't work on arches where char is unsigned, such as aarch64.
> 
> This unblocks a lot of packages.  No bump because none of the test
> files are ran, only compiled.
> 
> OK?

So that's why chromaprint vanished from the aarch64 build failures (:

It works as well on macppc.

If people have objections, properly fixing the code was non trivial
(at least to me) and updating to 1.4.3 was simpler. I've an update
almost ready for submission [0], that fixes the build and can
run all the tests.

It took some time to get OKs for a needed audio/clementine fix, so
i prefer to test the update again on macppc (it's fine on amd64),
before submitting it here. That could take a few more days if it goes
bad.

Meanwhile, OK cwen@

[0]
https://github.com/jasperla/openbsd-wip/tree/master/audio/chromaprint

> 
> Index: audio/chromaprint/patches/patch-tests_CMakeLists_txt
> ===
> RCS
> file: /cvs/ports/audio/chromaprint/patches/patch-tests_CMakeLists_txt,v
> retrieving revision 1.1 diff -u -p -u -p -r1.1
> patch-tests_CMakeLists_txt
> --- audio/chromaprint/patches/patch-tests_CMakeLists_txt  9 May
> 2014 09:00:19 -   1.1 +++
> audio/chromaprint/patches/patch-tests_CMakeLists_txt  12 Aug
> 2019 22:41:33 - @@ -1,6 +1,10 @@ $OpenBSD:
> patch-tests_CMakeLists_txt,v 1.1 2014/05/09 09:00:19 sthen Exp $
>  tests/CMakeLists.txt.origSat Nov 23 16:43:42 2013
> -+++ tests/CMakeLists.txt Wed May  7 15:12:15 2014
> +
> +test-bit_string_*.cpp depends on signed char, failing on aarch64
> +
> +Index: tests/CMakeLists.txt
> +--- tests/CMakeLists.txt.orig
>  tests/CMakeLists.txt
>  @@ -3,7 +3,6 @@ include_directories(
>   ${Boost_INCLUDE_DIRS}
>   ${CMAKE_CURRENT_SOURCE_DIR}/../src
> @@ -9,3 +13,12 @@ $OpenBSD: patch-tests_CMakeLists_txt,v 1
>   
>   set(tests_SOURCES
>   main.cpp
> +@@ -15,8 +14,6 @@ set(tests_SOURCES
> + test_integral_image.cpp
> + test_lloyds.cpp
> + test_audio_processor.cpp
> +-test_bit_string_reader.cpp
> +-test_bit_string_writer.cpp
> + test_chromaprint.cpp
> + test_chroma.cpp
> + test_chroma_filter.cpp
> 
> 
> 
> -- 
> The probability of someone watching you is proportional to the
> stupidity of your action.
> 



Re: New: mail/opensmtpd-filter-rspamd

2019-08-13 Thread Klemens Nanni
On Tue, Aug 13, 2019 at 11:32:37AM +0200, Landry Breuil wrote:
> Sorry, but i dont think this makes sense. With your reasoning, 2 extra
> lines will be displayed at the end of pkg_add, for a 2-lines README.
> lots of indirections for not much information... and we already know
> users dont read them anyway.
I agree that the indirection could be avoided, but people *do* read
these readmes.

> I doubt ppl will come to filter-rspamd directly (and then wonder how to
> set it up, in that case they will lookup HOMEPAGE), they might be more
> 'directed' at it by a mention of this same example in smtpd.conf(5) or a
> commented out entry in the default smtpd.conf.
Well, I know smtpd and we have packages for it, so I search the packages
to see what I can do.  I hate having to open some HOMEPAGE only to find
out how to use a port: that is was README and/or MESSAGE is for.

My goal is to provide packages which include all neccessary information
if possible, without forcing users through web browsers.

> Adding a README for 2 lines is abusing the README mechanism imo.
I'm also fine with amending DESCR or putting it in MESSAGE, as long as
I don't have to guess where to start after installing the package,
because I personally would be one of those users that would install it
only to find no manual or documentation whatsoever, angrily going though
smtpd(8) and smtpd.conf(5) first hoping for examples, then falling back
to the web.



UPDATE: Jailkit-2.20

2019-08-13 Thread Gonzalo L. Rodriguez
Hello,

Anyone still use use this?

Update for Jailkit to 2.20

https://olivier.sessink.nl/jailkit/

OK? Comments?

Cheers.-

-- 

- gonzalo
Index: Makefile
===
RCS file: /cvs/ports/security/jailkit/Makefile,v
retrieving revision 1.15
diff -u -p -r1.15 Makefile
--- Makefile12 Jul 2019 20:49:03 -  1.15
+++ Makefile13 Aug 2019 11:01:51 -
@@ -2,7 +2,7 @@
 
 COMMENT=   utilities for jailing a user or process
 
-DISTNAME=  jailkit-2.19
+DISTNAME=  jailkit-2.20
 CATEGORIES=security sysutils
 
 HOMEPAGE=  http://olivier.sessink.nl/jailkit/
Index: distinfo
===
RCS file: /cvs/ports/security/jailkit/distinfo,v
retrieving revision 1.8
diff -u -p -r1.8 distinfo
--- distinfo20 Dec 2015 15:43:46 -  1.8
+++ distinfo13 Aug 2019 11:01:51 -
@@ -1,2 +1,2 @@
-SHA256 (jailkit-2.19.tar.gz) = /ZYS3Vf0o5q/zeZHxCBhbFyjf1mCuMB6j7XLNSSU/Ig=
-SIZE (jailkit-2.19.tar.gz) = 142280
+SHA256 (jailkit-2.20.tar.gz) = 1hnB1NEcgjt/ouiKHZSGAP69QZroFAOBpjUIlhrx9rU=
+SIZE (jailkit-2.20.tar.gz) = 142815
Index: pkg/PLIST
===
RCS file: /cvs/ports/security/jailkit/pkg/PLIST,v
retrieving revision 1.1.1.1
diff -u -p -r1.1.1.1 PLIST
--- pkg/PLIST   20 Sep 2010 07:15:30 -  1.1.1.1
+++ pkg/PLIST   13 Aug 2019 11:01:51 -
@@ -32,22 +32,22 @@ sbin/jk_list
 @mode
 @bin sbin/jk_socketd
 sbin/jk_update
-@sample /etc/jailkit/
+@sample ${SYSCONFDIR}/jailkit/
 share/examples/jailkit/
 share/examples/jailkit/jk_check.ini
-@sample /etc/jailkit/jk_check.ini
+@sample ${SYSCONFDIR}/jailkit/jk_check.ini
 share/examples/jailkit/jk_chrootsh.ini
-@sample /etc/jailkit/jk_chrootsh.ini
+@sample ${SYSCONFDIR}/jailkit/jk_chrootsh.ini
 share/examples/jailkit/jk_init.ini
-@sample /etc/jailkit/jk_init.ini
+@sample ${SYSCONFDIR}/jailkit/jk_init.ini
 share/examples/jailkit/jk_lsh.ini
-@sample /etc/jailkit/jk_lsh.ini
+@sample ${SYSCONFDIR}/jailkit/jk_lsh.ini
 share/examples/jailkit/jk_socketd.ini
-@sample /etc/jailkit/jk_socketd.ini
+@sample ${SYSCONFDIR}/jailkit/jk_socketd.ini
 share/examples/jailkit/jk_uchroot.ini
-@sample /etc/jailkit/jk_uchroot.ini
+@sample ${SYSCONFDIR}/jailkit/jk_uchroot.ini
 share/examples/jailkit/jk_update.ini
-@sample /etc/jailkit/jk_update.ini
+@sample ${SYSCONFDIR}/jailkit/jk_update.ini
 share/jailkit/
 share/jailkit/jk_lib.py
 share/jailkit/jk_lib.pyc


Re: New: mail/opensmtpd-filter-rspamd

2019-08-13 Thread Gonzalo L. Rodriguez
On Tue, 13 Aug 2019 at 11:43:23 +0200, Gonzalo L. Rodriguez wrote:
> On Tue, 13 Aug 2019 at 11:18:33 +0200, Klemens Nanni wrote:
> > On Tue, Aug 13, 2019 at 08:37:18AM +, Gilles Chehade wrote:
> > > filter-rspamd doesn't have any configuration itself, all it needs is for 
> > > smtpd.conf to reference it:
> > > 
> > > filter "rspamd" proc-exec "/usr/local/bin/filter-rspamd"
> > > listen on all filter "rspamd"
> > > 
> > > I thought I'd add this as an example to the smtpd.conf(5) man page itself.
> > Sounds good.
> > 
> > > Should I add a README in the port too ?
> > Yes please, either reference smtpd.conf(5) or just include the same
> > example here.  Adding a pkg/README to the port should do it; this way
> > pkg_add would tell you
> > 
> > opensmtpd-filter-rspamd-X.Y: ok
> > New and changed readme(s):
> > /usr/local/share/doc/pkg-readmes/opensmtpd-filter-rspamd
> > 
> > so users know immediately how to set things up.
> > 
> 
> That would be nice.
> 
> -- 
> 
>   - gonzalo
> 

BTW, are you planning to merge this port with opensmtpd-extras? Or are
different stuff?

-- 

- gonzalo



Re: New: mail/opensmtpd-filter-rspamd

2019-08-13 Thread Gonzalo L. Rodriguez
On Tue, 13 Aug 2019 at 11:18:33 +0200, Klemens Nanni wrote:
> On Tue, Aug 13, 2019 at 08:37:18AM +, Gilles Chehade wrote:
> > filter-rspamd doesn't have any configuration itself, all it needs is for 
> > smtpd.conf to reference it:
> > 
> > filter "rspamd" proc-exec "/usr/local/bin/filter-rspamd"
> > listen on all filter "rspamd"
> > 
> > I thought I'd add this as an example to the smtpd.conf(5) man page itself.
> Sounds good.
> 
> > Should I add a README in the port too ?
> Yes please, either reference smtpd.conf(5) or just include the same
> example here.  Adding a pkg/README to the port should do it; this way
> pkg_add would tell you
> 
>   opensmtpd-filter-rspamd-X.Y: ok
>   New and changed readme(s):
>   /usr/local/share/doc/pkg-readmes/opensmtpd-filter-rspamd
> 
> so users know immediately how to set things up.
> 

That would be nice.

-- 

- gonzalo



Re: New: mail/opensmtpd-filter-rspamd

2019-08-13 Thread Landry Breuil
On Tue, Aug 13, 2019 at 11:18:33AM +0200, Klemens Nanni wrote:
> On Tue, Aug 13, 2019 at 08:37:18AM +, Gilles Chehade wrote:
> > filter-rspamd doesn't have any configuration itself, all it needs is for 
> > smtpd.conf to reference it:
> > 
> > filter "rspamd" proc-exec "/usr/local/bin/filter-rspamd"
> > listen on all filter "rspamd"
> > 
> > I thought I'd add this as an example to the smtpd.conf(5) man page itself.
> Sounds good.
> 
> > Should I add a README in the port too ?
> Yes please, either reference smtpd.conf(5) or just include the same
> example here.  Adding a pkg/README to the port should do it; this way
> pkg_add would tell you
> 
>   opensmtpd-filter-rspamd-X.Y: ok
>   New and changed readme(s):
>   /usr/local/share/doc/pkg-readmes/opensmtpd-filter-rspamd
> 
> so users know immediately how to set things up.

Sorry, but i dont think this makes sense. With your reasoning, 2 extra
lines will be displayed at the end of pkg_add, for a 2-lines README.
lots of indirections for not much information... and we already know
users dont read them anyway.

I doubt ppl will come to filter-rspamd directly (and then wonder how to
set it up, in that case they will lookup HOMEPAGE), they might be more
'directed' at it by a mention of this same example in smtpd.conf(5) or a
commented out entry in the default smtpd.conf.

Adding a README for 2 lines is abusing the README mechanism imo.

Landry



Re: New: mail/opensmtpd-filter-rspamd

2019-08-13 Thread Klemens Nanni
On Tue, Aug 13, 2019 at 08:37:18AM +, Gilles Chehade wrote:
> filter-rspamd doesn't have any configuration itself, all it needs is for 
> smtpd.conf to reference it:
> 
> filter "rspamd" proc-exec "/usr/local/bin/filter-rspamd"
> listen on all filter "rspamd"
> 
> I thought I'd add this as an example to the smtpd.conf(5) man page itself.
Sounds good.

> Should I add a README in the port too ?
Yes please, either reference smtpd.conf(5) or just include the same
example here.  Adding a pkg/README to the port should do it; this way
pkg_add would tell you

opensmtpd-filter-rspamd-X.Y: ok
New and changed readme(s):
/usr/local/share/doc/pkg-readmes/opensmtpd-filter-rspamd

so users know immediately how to set things up.



CVS: cvs.openbsd.org: ports

2019-08-13 Thread Frederic Cambus
CVSROOT:/cvs
Module name:ports
Changes by: fcam...@cvs.openbsd.org 2019/08/13 02:42:46

Modified files:
graphics/ansilove: Makefile distinfo 

Log message:
Update ansilove to 4.0.2.



Re: New: mail/opensmtpd-filter-rspamd

2019-08-13 Thread gilles
13 août 2019 09:36 "Klemens Nanni"  a écrit:

> On Mon, Aug 12, 2019 at 11:37:48PM +, Gilles Chehade wrote:
> 
>> This is my very very first port so let me know if I did something wrong.
> 
> Looks OK to me; haven't run tested it yet, though.
> 
> Since DESCR is quite short and there is no README, do you plan writing
> a manual page for it or can everything needed to set this up be found in
> existing smtpd documentation?

filter-rspamd doesn't have any configuration itself, all it needs is for 
smtpd.conf to reference it:

filter "rspamd" proc-exec "/usr/local/bin/filter-rspamd"
listen on all filter "rspamd"

I thought I'd add this as an example to the smtpd.conf(5) man page itself.

Should I add a README in the port too ?



CVS: cvs.openbsd.org: ports

2019-08-13 Thread Paul Irofti
CVSROOT:/cvs
Module name:ports
Changes by: piro...@cvs.openbsd.org 2019/08/13 02:31:17

Modified files:
math   : Makefile 

Log message:
Add py-scikit-learn



CVS: cvs.openbsd.org: ports

2019-08-13 Thread Paul Irofti
CVSROOT:/cvs
Module name:ports
Changes by: piro...@cvs.openbsd.org 2019/08/13 02:30:07

Log message:
Import py-scikit-learn.

scikit-learn is a BSD-licensed Python module for machine learning
and data mining built on top of SciPy.

Initially created by robert@, modified by me and kmos@.

This is not polished enough, but it can improved in the tree now.
Once the 21 branch rolls out a new version, we will probably update to that.
Currently it is broken for non-OpenMP builds.

OK robert@, kmos@

Status:

Vendor Tag: pirofti
Release Tags:   pirofti_20190813

N ports/math/py-scikit-learn/Makefile
N ports/math/py-scikit-learn/distinfo
N ports/math/py-scikit-learn/pkg/DESCR
N ports/math/py-scikit-learn/pkg/PLIST

No conflicts created by this import



CVS: cvs.openbsd.org: ports

2019-08-13 Thread Paul Irofti
CVSROOT:/cvs
Module name:ports
Changes by: piro...@cvs.openbsd.org 2019/08/13 02:26:02

Modified files:
sysutils   : Makefile 

Log message:
Add py-joblib



CVS: cvs.openbsd.org: ports

2019-08-13 Thread Paul Irofti
CVSROOT:/cvs
Module name:ports
Changes by: piro...@cvs.openbsd.org 2019/08/13 02:24:07

Log message:
Import py-joblib required by upcoming py-scikit-learn.

Joblib is a set of tools to provide lightweight pipelining in Python.
In particular:

transparent disk-caching of functions and lazy re-evaluation
(memoize pattern)

easy simple parallel computing

Joblib is optimized to be fast and robust in particular on large
data and has specific optimizations for numpy arrays. It is
BSD-licensed.

Initial work by robert@, polished by kmos@.

OK robert, kmos

Status:

Vendor Tag: pirofti
Release Tags:   pirofti_20190813

N ports/sysutils/py-joblib/Makefile
N ports/sysutils/py-joblib/distinfo
N ports/sysutils/py-joblib/pkg/DESCR
N ports/sysutils/py-joblib/pkg/PLIST
N ports/sysutils/py-joblib/patches/patch-setup_py

No conflicts created by this import



CVS: cvs.openbsd.org: ports

2019-08-13 Thread Giovanni Bechis
CVSROOT:/cvs
Module name:ports
Changes by: giova...@cvs.openbsd.org2019/08/13 02:12:57

Modified files:
mail/amavisd-new: Makefile distinfo 
mail/amavisd-new/patches: patch-amavisd patch-amavisd_conf 
mail/amavisd-new/pkg: PLIST-main PLIST-utils 

Log message:
Update to 2.12.0
Support to rspamd
dkim patch committed upstream
bug fixes



Re: New: mail/opensmtpd-filter-rspamd

2019-08-13 Thread Klemens Nanni
On Mon, Aug 12, 2019 at 11:37:48PM +, Gilles Chehade wrote:
> This is my very very first port so let me know if I did something wrong.
Looks OK to me;  haven't run tested it yet, though.

Since DESCR is quite short and there is no README, do you plan writing
a manual page for it or can everything needed to set this up be found in
existing smtpd documentation?



Re: Update: textproc/py-xmldiff 0.6.10 -> 2.3

2019-08-13 Thread Landry Breuil
On Mon, Aug 12, 2019 at 09:04:09PM -0400, Kurt Mosiejczuk wrote:
> On Mon, Aug 12, 2019 at 08:03:16PM -0400, Kurt Mosiejczuk wrote:
> > On Mon, Aug 12, 2019 at 06:44:46PM -0400, Daniel Jakots wrote:
> > > On Mon, 12 Aug 2019 18:32:16 -0400, Kurt Mosiejczuk 
> > > wrote:
> 
> > > > +FLAVORS=   python3
> > > > +FLAVOR?=
> 
> > > Isn't it just a tool? Maybe it's more meaningful to just provide a py3
> > > version. What's your opinion?
> 
> > That is actually an excellent point. It had been python 2 only so I was
> > more concerned with adding python3.
> 
> > Actually, going one flavor is required as it is. It installs plain binaries
> > (xmldiff, xmlpatch) and I didn't throw a suffix on them.
> 
> > I'll rework it to be python3 only and then have a quirks diff to migrate
> > folks from py-xmldiff to py3-xmldiff.
> 
> Here's a new version of the diff making it python3 only.  I'm also including
> a quirks diff at the end that will migrate folks from py-xmldiff to
> py3-xmldiff.

Reads good to me, and i also agree with the move to py3 only. thanks !

Landry



Re: x11/gtk+4: colord on aarch64

2019-08-13 Thread Antoine Jacoutot
On Tue, Aug 13, 2019 at 08:11:50AM +0200, Peter Hessler wrote:
> Pretty straightforward addition to the dependency chain, as
> x11/gtk+4,-cloudprint also depends on colord being installed.

x11/gtk+4,-cloudprint does not depend at all on colord.
I assume you meant x11/gtk+4,-cups.

> if this is OK, then I'll sort the list before committing it
>
> OK?

Yes

> Index: x11/gtk+4/Makefile
> ===
> RCS file: /cvs/ports/x11/gtk+4/Makefile,v
> retrieving revision 1.14
> diff -u -p -u -p -r1.14 Makefile
> --- x11/gtk+4/Makefile12 Jul 2019 20:51:12 -  1.14
> +++ x11/gtk+4/Makefile12 Aug 2019 21:28:53 -
> @@ -128,7 +128,7 @@ CONFIGURE_ARGS=   -Dwayland-backend=false
>  .if ${MACHINE_ARCH} == "i386" || ${MACHINE_ARCH} == "amd64" || \
>  ${MACHINE_ARCH} == "alpha" || ${MACHINE_ARCH} == "hppa" || \
>  ${MACHINE_ARCH} == "powerpc" || ${MACHINE_ARCH} == "sparc64" || \
> -${MACHINE_ARCH} == "mips64"
> +${MACHINE_ARCH} == "mips64" || ${MACHINE_ARCH} == "aarch64"
>  LIB_DEPENDS-cups +=  graphics/colord
>  WANTLIB-cups +=  colord
>  .else
> 
> 
> 
> 
> -- 
> It is easier to write an incorrect program than understand a correct one.
> 

-- 
Antoine



Re: Installing a tree of files

2019-08-13 Thread Klemens Nanni
On Tue, Aug 13, 2019 at 12:08:58AM -0400, Ted Unangst wrote:
> Inconveniently, find -exec {} + requires that {} go last, not followed by
> destination. Maybe some way to sh around that.
Yup, I could work with xargs here, but before doing that I think sthen's
point of simply copying trees as a whole (using pax for example) is the
better approach here.



audio/chromaprint: fix compilation on unsigned char arches

2019-08-13 Thread Peter Hessler
test_bit_string_* both use constructs like:

  char data[] = { -28 };

which won't work on arches where char is unsigned, such as aarch64.

This unblocks a lot of packages.  No bump because none of the test files
are ran, only compiled.

OK?


Index: audio/chromaprint/patches/patch-tests_CMakeLists_txt
===
RCS file: /cvs/ports/audio/chromaprint/patches/patch-tests_CMakeLists_txt,v
retrieving revision 1.1
diff -u -p -u -p -r1.1 patch-tests_CMakeLists_txt
--- audio/chromaprint/patches/patch-tests_CMakeLists_txt9 May 2014 
09:00:19 -   1.1
+++ audio/chromaprint/patches/patch-tests_CMakeLists_txt12 Aug 2019 
22:41:33 -
@@ -1,6 +1,10 @@
 $OpenBSD: patch-tests_CMakeLists_txt,v 1.1 2014/05/09 09:00:19 sthen Exp $
 tests/CMakeLists.txt.orig  Sat Nov 23 16:43:42 2013
-+++ tests/CMakeLists.txt   Wed May  7 15:12:15 2014
+
+test-bit_string_*.cpp depends on signed char, failing on aarch64
+
+Index: tests/CMakeLists.txt
+--- tests/CMakeLists.txt.orig
 tests/CMakeLists.txt
 @@ -3,7 +3,6 @@ include_directories(
${Boost_INCLUDE_DIRS}
${CMAKE_CURRENT_SOURCE_DIR}/../src
@@ -9,3 +13,12 @@ $OpenBSD: patch-tests_CMakeLists_txt,v 1
  
  set(tests_SOURCES
main.cpp
+@@ -15,8 +14,6 @@ set(tests_SOURCES
+   test_integral_image.cpp
+   test_lloyds.cpp
+   test_audio_processor.cpp
+-  test_bit_string_reader.cpp
+-  test_bit_string_writer.cpp
+   test_chromaprint.cpp
+   test_chroma.cpp
+   test_chroma_filter.cpp



-- 
The probability of someone watching you is proportional to the
stupidity of your action.



x11/gtk+4: colord on aarch64

2019-08-13 Thread Peter Hessler
Pretty straightforward addition to the dependency chain, as
x11/gtk+4,-cloudprint also depends on colord being installed.

if this is OK, then I'll sort the list before committing it

OK?

Index: x11/gtk+4/Makefile
===
RCS file: /cvs/ports/x11/gtk+4/Makefile,v
retrieving revision 1.14
diff -u -p -u -p -r1.14 Makefile
--- x11/gtk+4/Makefile  12 Jul 2019 20:51:12 -  1.14
+++ x11/gtk+4/Makefile  12 Aug 2019 21:28:53 -
@@ -128,7 +128,7 @@ CONFIGURE_ARGS= -Dwayland-backend=false
 .if ${MACHINE_ARCH} == "i386" || ${MACHINE_ARCH} == "amd64" || \
 ${MACHINE_ARCH} == "alpha" || ${MACHINE_ARCH} == "hppa" || \
 ${MACHINE_ARCH} == "powerpc" || ${MACHINE_ARCH} == "sparc64" || \
-${MACHINE_ARCH} == "mips64"
+${MACHINE_ARCH} == "mips64" || ${MACHINE_ARCH} == "aarch64"
 LIB_DEPENDS-cups +=graphics/colord
 WANTLIB-cups +=colord
 .else




-- 
It is easier to write an incorrect program than understand a correct one.