[update] OfflineIMAP v7.2.1

2018-06-24 Thread Remi Locherer
Hi porters,

This updates OfflineIMAP to version 7.2.1.

Changes are listed here:
http://www.offlineimap.org/doc/Changelog.html#offlineimap-v721-2018-06-16

OK?

Remi


Index: Makefile
===
RCS file: /cvs/ports/mail/offlineimap/Makefile,v
retrieving revision 1.50
diff -u -p -r1.50 Makefile
--- Makefile11 Apr 2018 06:33:53 -  1.50
+++ Makefile20 Jun 2018 20:16:05 -
@@ -2,7 +2,7 @@
 
 COMMENT=   powerful IMAP/Maildir synchronization and reader support
 
-MODPY_EGG_VERSION = 7.2.0
+MODPY_EGG_VERSION = 7.2.1
 DISTNAME = offlineimap-v${MODPY_EGG_VERSION}
 PKGNAME =  offlineimap-${MODPY_EGG_VERSION}
 
Index: distinfo
===
RCS file: /cvs/ports/mail/offlineimap/distinfo,v
retrieving revision 1.37
diff -u -p -r1.37 distinfo
--- distinfo11 Apr 2018 06:33:53 -  1.37
+++ distinfo20 Jun 2018 20:16:12 -
@@ -1,2 +1,2 @@
-SHA256 (offlineimap-v7.2.0.tar.gz) = 
Lzsrx2TkAkj85OLGn8KvehLPbh/B4/N4aCF6jW7f5YI=
-SIZE (offlineimap-v7.2.0.tar.gz) = 731475
+SHA256 (offlineimap-v7.2.1.tar.gz) = 
RWuzq5U/bQLK4LYX0fV3Pwx1AMLTJSb+Eu4eRqDW7Bo=
+SIZE (offlineimap-v7.2.1.tar.gz) = 735626



NEW: math/bc

2018-06-24 Thread Ivan "Rambius" Ivanov
Hello ports,

Attached is a new port for gnu bc:

pkg/DESCR:
bc is an arbitrary precision numeric processing language. Syntax is similar to
C, but differs in many substantial areas. It supports interactive execution of
statements. bc is a utility included in the POSIX P1003.2/D11 draft standard.

HOMEPAGE: https://www.gnu.org/software/bc/

I added --program-prefix="g" in CONFIGURE_ARGS  to prevent conflicts with
/usr/bin/bc and /usr/bin/gc. I tested the port on i386.

OK?

Regards
rambius

-- 
Tangra Mega Rock: http://www.radiotangra.com


bc.tar.gz
Description: application/gzip


Enable lang/flang on arm64

2018-06-24 Thread Brian Callahan

Hi ports --

The attached diff allows lang/flang to build and run on arm64. The entire NIST 
Fortran 77 test suite passes on arm64 with this. My Raspberry Pi 3B+ is happy 
with this.

Does anyone want to try it out before I commit?

Apologies to the arm64 package builders; this took quite a while to build on my 
RPi 3B+.

OK?

~Brian

Index: Makefile.inc
===
RCS file: /cvs/ports/lang/flang/Makefile.inc,v
retrieving revision 1.2
diff -u -p -r1.2 Makefile.inc
--- Makefile.inc	9 May 2018 22:27:41 -	1.2
+++ Makefile.inc	24 Jun 2018 23:31:00 -
@@ -1,7 +1,7 @@
 # $OpenBSD: Makefile.inc,v 1.2 2018/05/09 22:27:41 bcallah Exp $
 
 # Also ppc64le
-ONLY_FOR_ARCHS =	amd64 #arm64
+ONLY_FOR_ARCHS =	amd64 arm64
 
 CATEGORIES ?=	lang
 
Index: flang/Makefile
===
RCS file: /cvs/ports/lang/flang/flang/Makefile,v
retrieving revision 1.13
diff -u -p -r1.13 Makefile
--- flang/Makefile	23 Jun 2018 01:10:35 -	1.13
+++ flang/Makefile	24 Jun 2018 23:31:00 -
@@ -2,6 +2,7 @@
 
 COMMENT =	LLVM Fortran compiler passes and runtime library
 DISTNAME =	flang-6.0.0.20180621
+REVISION =	0
 
 SHARED_LIBS +=	flang 1.1 # 6.0
 SHARED_LIBS +=	flangrti  1.0 # 6.0
@@ -33,9 +34,5 @@ CONFIGURE_ARGS =	-DCMAKE_Fortran_COMPILE
 			-DFLANG_LIBOMP="${WRKBUILD}/lib/libompstub.a" \
 			-DLIBPGMATH="${LOCALBASE}/lib/libpgmath.a" \
 			-DWITH_WERROR=OFF
-
-post-patch:
-	@cp -R ${WRKSRC}/tools/flang2/flang2exe/x86_64-Linux \
-		${WRKSRC}/tools/flang2/flang2exe/x86_64-OpenBSD
 
 .include 
Index: flang/patches/patch-CMakeLists_txt
===
RCS file: /cvs/ports/lang/flang/flang/patches/patch-CMakeLists_txt,v
retrieving revision 1.2
diff -u -p -r1.2 patch-CMakeLists_txt
--- flang/patches/patch-CMakeLists_txt	9 May 2018 22:27:41 -	1.2
+++ flang/patches/patch-CMakeLists_txt	24 Jun 2018 23:31:00 -
@@ -1,11 +1,11 @@
 $OpenBSD: patch-CMakeLists_txt,v 1.2 2018/05/09 22:27:41 bcallah Exp $
 
-Add OpenBSD/amd64
+Add OpenBSD/amd64 and OpenBSD/arm64
 
 Index: CMakeLists.txt
 --- CMakeLists.txt.orig
 +++ CMakeLists.txt
-@@ -49,6 +49,15 @@ if( ${TARGET_OS} STREQUAL "Linux" )
+@@ -49,6 +49,20 @@ if( ${TARGET_OS} STREQUAL "Linux" )
  message("Unsupported architecture: ${TARGET_ARCHITECTURE}" )
  return()
endif()
@@ -17,6 +17,11 @@ Index: CMakeLists.txt
 +set(ARCH X86)
 +set(WRDSZ 64)
 +set(TARGET_ARCHITECTURE x86_64)
++  elseif( ${TARGET_ARCHITECTURE} STREQUAL "arm64" )
++set(ARCHNAME aarch64)
++set(ARCH ARM)
++set(WRDSZ 64)
++set(TARGET_ARCHITECTURE aarch64)
 +  endif()
  else()
message("Unsupported OS: ${TARGET_OS}" )
Index: flang/patches/patch-runtime_flang_CMakeLists_txt
===
RCS file: /cvs/ports/lang/flang/flang/patches/patch-runtime_flang_CMakeLists_txt,v
retrieving revision 1.3
diff -u -p -r1.3 patch-runtime_flang_CMakeLists_txt
--- flang/patches/patch-runtime_flang_CMakeLists_txt	16 Jun 2018 20:08:28 -	1.3
+++ flang/patches/patch-runtime_flang_CMakeLists_txt	24 Jun 2018 23:31:00 -
@@ -2,6 +2,7 @@ $OpenBSD: patch-runtime_flang_CMakeLists
 
 No -lrt
 Appease lld
+Work around standalone preprocessing of F95 files with C compiler
 
 Index: runtime/flang/CMakeLists.txt
 --- runtime/flang/CMakeLists.txt.orig
@@ -15,6 +16,24 @@ Index: runtime/flang/CMakeLists.txt
  
  # We are using Fortran driver to build this library with fresh compiler
  # components, so point its binary directory to the build directory to pick up
+@@ -420,7 +420,7 @@ set(I8_FILES_DIR I8_sources)
+ # Fortran files with macros as module names need to be preprocessed. 
+ add_custom_command(
+   OUTPUT "${I8_FILES_DIR}/ieee_arithmetic.F95"
+-  COMMAND "${CMAKE_C_COMPILER}" -E 
++  COMMAND "${CMAKE_C_COMPILER}" -E -x c 
+   "${CMAKE_CURRENT_SOURCE_DIR}/ieee_arithmetic.F95" -DDESC_I8 
+   > "${I8_FILES_DIR}/ieee_arithmetic.F95"
+   COMMENT "Preprocessing ieee_arithmetic.F95"
+@@ -429,7 +429,7 @@ add_custom_command(
+ 
+ add_custom_command(
+   OUTPUT "${I8_FILES_DIR}/ieee_exceptions.F95"
+-  COMMAND "${CMAKE_C_COMPILER}" -E 
++  COMMAND "${CMAKE_C_COMPILER}" -E -x c 
+   "${CMAKE_CURRENT_SOURCE_DIR}/ieee_exceptions.F95" -DDESC_I8 
+   > "${I8_FILES_DIR}/ieee_exceptions.F95"
+   COMMENT "Preprocessing ieee_exceptions.F95"
 @@ -479,7 +479,7 @@ add_flang_library(flang_shared
  set_property(TARGET flang_shared PROPERTY OUTPUT_NAME flang)
  target_link_libraries(flang_shared ${CMAKE_BINARY_DIR}/${CMAKE_CFG_INTDIR}/lib/libflangrti.so)
Index: flang/patches/patch-runtime_flangrti_aarch64-Linux_dumpregs_c
===
RCS file: flang/patches/patch-runtime_flangrti_aarch64-Linux_dumpregs_c
diff -N flang/patches/patch-runtime_flangrti_aarch64-Linux_dumpregs_c
--- /dev/null	1 Jan 1970 00:00:00 -
+++ flang/pat

Re: NEW: sysutils/seq

2018-06-24 Thread Theo Buehler
On Sun, Jun 24, 2018 at 12:55:39PM +0100, Stuart Henderson wrote:
> On 2018/06/24 13:51, Klemens Nanni wrote:
> > On Sun, Jun 24, 2018 at 12:42:54PM +0100, Stuart Henderson wrote:
> > > Like realpath, this is another of those things where I think if it makes
> > > sense to have on OpenBSD at all, base is a better place for it ..
> > We have jot(1) in base; different synopsis but more versatile already.
> > 
> > $ jot -s' ' 10 1 10 1
> > 1 2 3 4 5 6 7 8 9 10
> > 
> 
> We do, and we also have a number of slightly annoying patches to ports
> to use this instead of seq.
> 
> (Also like realpath, it's something that could be reasonably be handled
> as a __progname switch in jot ..)

At g2k16 naddy suggested that this might be possible and I spent a
couple of days looking into this.

Unfortunately, it's not as easy as it might seem at first sight. They
share the same craziness of using doubles internally, but that's about
the only thing they actually share.

The format strings are mostly incompatible due to allowing different
subsets of specifiers and due to seq(1) additionally having backslash
escapes. This means that the hairiest piece of cods needs to be kept
separate and the remaining overlap is so small that it makes more sense
to have two separate programs.



Re: UPDATE: security/sshguard, 1.5-->2.1.0 (2nd try)

2018-06-24 Thread Andreas Kusalananda Kähäri
On Sun, Jun 24, 2018 at 04:49:27PM +0200, Klemens Nanni wrote:
> On Mon, Apr 23, 2018 at 11:12:55AM +0200, Andreas Kusalananda Kähäri wrote:
> > On Sun, Apr 22, 2018 at 04:04:02PM +0200, Andreas Kusalananda Kähäri wrote:
> > > On Sun, Apr 22, 2018 at 04:03:23PM +0200, Andreas Kusalananda Kähäri 
> > > wrote:
> > > >
> > > > Please find the diffs for an updated port of sshguard attached.
> > >
> > > Now actually attached, duh.
> > >
> >
> > Updated patch attached with comments from kn@ taken into account, but
> > with CONFIGURE_STYLE=gnu left in place as suggested by Jeremie and
> > Stuart.
> I forgot about this diff when removing -O2 earlier (portroach also
> wouldn't detect an update due to EXTRACT_SUFX change), thanks Andreas
> for reminding me.
>
> The diff looks good, I made a few additional changes:
>
> - Drop README: sshguard-intro(7) contains all relevant information
> - sshguard.rc: $pexp -> ${pexp}, unfold rc_stop()
> - Makefile: Use SUBST_CMD and INSTALL_DATA just once
>
> On amd64 sshguard continues to work.
>
> 1.5.0 is broken on sparc64 due to an assertion failure when parsing log
> lines, 2.1.0 fixed this.
>
> OK?
>
[cut]

The issue with this is that it won't start properly at reboots.  One
may start it manually through "doas rcctl start sshguard" but if
it's started automatically through pkg_scripts, its sshg-blocker and
sshg-fw-pf (backend) process dies and leaves the tail and sshg-parser
processes, as well as the main sshguard script, hanging.

--
Andreas Kusalananda Kähäri,
National Bioinformatics Infrastructure Sweden (NBIS),
Uppsala University, Sweden.








När du har kontakt med oss på Uppsala universitet med e-post så innebär det att 
vi behandlar dina personuppgifter. För att läsa mer om hur vi gör det kan du 
läsa här: http://www.uu.se/om-uu/dataskydd-personuppgifter/

E-mailing Uppsala University means that we will process your personal data. For 
more information on how this is performed, please read here: 
http://www.uu.se/om-uu/dataskydd-personuppgifter/



[update] nss 3.38

2018-06-24 Thread Landry Breuil
Hi,

here's an update to nss 3.38, cf
https://developer.mozilla.org/en-US/docs/Mozilla/Projects/NSS/NSS_3.38_release_notes
- probably required by upcoming mozilla 62 betas. Will probably commit
  it before/altogether with firefox 61 in the coming week.

Landry
? -
? build-3.33-with-3.32.1-installed.log
? build-3.35.log
? nss-3.20.1-libfreebl3.so.38.0
? nss-3.20.1-libnss3.so.38.0
? nss-3.20.1-libnssckbi.so.38.0
? nss-3.20.1-libnssdbm3.so.38.0
? nss-3.20.1-libnssutil3.so.38.0
? nss-3.20.1-libsmime3.so.38.0
? nss-3.20.1-libsoftokn3.so.38.0
? nss-3.20.1-libssl3.so.38.0
? nss-3.21-libfreebl3.so.38.0
? nss-3.21-libnss3.so.38.0
? nss-3.21-libnssckbi.so.38.0
? nss-3.21-libnssdbm3.so.38.0
? nss-3.21-libnssutil3.so.38.0
? nss-3.21-libsmime3.so.38.0
? nss-3.21-libsoftokn3.so.38.0
? nss-3.21-libssl3.so.38.0
? nss-3.21.1-libfreebl3.so.39.0
? nss-3.21.1-libnss3.so.39.0
? nss-3.21.1-libnssckbi.so.39.0
? nss-3.21.1-libnssdbm3.so.39.0
? nss-3.21.1-libnssutil3.so.39.0
? nss-3.21.1-libsmime3.so.39.0
? nss-3.21.1-libsoftokn3.so.39.0
? nss-3.21.1-libssl3.so.39.0
? nss-3.23-libfreebl3.so.39.0
? nss-3.23-libnss3.so.39.0
? nss-3.23-libnssckbi.so.39.0
? nss-3.23-libnssdbm3.so.39.0
? nss-3.23-libnssutil3.so.39.0
? nss-3.23-libsmime3.so.39.0
? nss-3.23-libsoftokn3.so.39.0
? nss-3.23-libssl3.so.39.0
? nss-3.24-libfreebl3.so.41.0
? nss-3.24-libnss3.so.41.0
? nss-3.24-libnssckbi.so.41.0
? nss-3.24-libnssdbm3.so.41.0
? nss-3.24-libnssutil3.so.41.0
? nss-3.24-libsmime3.so.41.0
? nss-3.24-libsoftokn3.so.41.0
? nss-3.24-libssl3.so.41.0
? nss-3.25-libfreebl3.so.42.0
? nss-3.25-libnss3.so.42.0
? nss-3.25-libnssckbi.so.42.0
? nss-3.25-libnssdbm3.so.42.0
? nss-3.25-libnssutil3.so.42.0
? nss-3.25-libsmime3.so.42.0
? nss-3.25-libsoftokn3.so.42.0
? nss-3.25-libssl3.so.42.0
? nss-3.26-libfreebl3.so.43.0
? nss-3.26-libnss3.so.43.0
? nss-3.26-libnssckbi.so.43.0
? nss-3.26-libnssdbm3.so.43.0
? nss-3.26-libnssutil3.so.43.0
? nss-3.26-libsmime3.so.43.0
? nss-3.26-libsoftokn3.so.43.0
? nss-3.26-libssl3.so.43.0
? nss-3.27-libfreebl3.so.44.0
? nss-3.27-libnss3.so.44.0
? nss-3.27-libnssckbi.so.44.0
? nss-3.27-libnssdbm3.so.44.0
? nss-3.27-libnssutil3.so.44.0
? nss-3.27-libsmime3.so.44.0
? nss-3.27-libsoftokn3.so.44.0
? nss-3.27-libssl3.so.44.0
? nss-3.27.2-libfreebl3.so.44.0
? nss-3.27.2-libnss3.so.44.0
? nss-3.27.2-libnssckbi.so.44.0
? nss-3.27.2-libnssdbm3.so.44.0
? nss-3.27.2-libnssutil3.so.44.0
? nss-3.27.2-libsmime3.so.44.0
? nss-3.27.2-libsoftokn3.so.44.0
? nss-3.27.2-libssl3.so.44.0
? nss-3.28-libfreebl3.so.45.0
? nss-3.28-libnss3.so.45.0
? nss-3.28-libnssckbi.so.45.0
? nss-3.28-libnssdbm3.so.45.0
? nss-3.28-libnssutil3.so.45.0
? nss-3.28-libsmime3.so.45.0
? nss-3.28-libsoftokn3.so.45.0
? nss-3.28-libssl3.so.45.0
? nss-3.28.1-libfreebl3.so.45.0
? nss-3.28.1-libnss3.so.45.0
? nss-3.28.1-libnssckbi.so.45.0
? nss-3.28.1-libnssdbm3.so.45.0
? nss-3.28.1-libnssutil3.so.45.0
? nss-3.28.1-libsmime3.so.45.0
? nss-3.28.1-libsoftokn3.so.45.0
? nss-3.28.1-libssl3.so.45.0
? nss-3.29.1-libfreebl3.so.46.0
? nss-3.29.1-libnss3.so.46.0
? nss-3.29.1-libnssckbi.so.46.0
? nss-3.29.1-libnssdbm3.so.46.0
? nss-3.29.1-libnssutil3.so.46.0
? nss-3.29.1-libsmime3.so.46.0
? nss-3.29.1-libsoftokn3.so.46.0
? nss-3.29.1-libssl3.so.46.0
? nss-3.29.3-libfreebl3.so.46.0
? nss-3.29.3-libnss3.so.46.0
? nss-3.29.3-libnssckbi.so.46.0
? nss-3.29.3-libnssdbm3.so.46.0
? nss-3.29.3-libnssutil3.so.46.0
? nss-3.29.3-libsmime3.so.46.0
? nss-3.29.3-libsoftokn3.so.46.0
? nss-3.29.3-libssl3.so.46.0
? nss-3.29.4-libfreebl3.so.46.0
? nss-3.29.4-libnss3.so.46.0
? nss-3.29.4-libnssckbi.so.46.0
? nss-3.29.4-libnssdbm3.so.46.0
? nss-3.29.4-libnssutil3.so.46.0
? nss-3.29.4-libsmime3.so.46.0
? nss-3.29.4-libsoftokn3.so.46.0
? nss-3.29.4-libssl3.so.46.0
? nss-3.30.2-libfreebl3.so.47.0
? nss-3.30.2-libnss3.so.47.0
? nss-3.30.2-libnssckbi.so.47.0
? nss-3.30.2-libnssdbm3.so.47.0
? nss-3.30.2-libnssutil3.so.47.0
? nss-3.30.2-libsmime3.so.47.0
? nss-3.30.2-libsoftokn3.so.47.0
? nss-3.30.2-libssl3.so.47.0
? nss-3.31-libfreebl3.so.48.0
? nss-3.31-libnss3.so.48.0
? nss-3.31-libnssckbi.so.48.0
? nss-3.31-libnssdbm3.so.48.0
? nss-3.31-libnssutil3.so.48.0
? nss-3.31-libsmime3.so.48.0
? nss-3.31-libsoftokn3.so.48.0
? nss-3.31-libssl3.so.48.0
? nss-3.32-libfreebl3.so.49.0
? nss-3.32-libnss3.so.49.0
? nss-3.32-libnssckbi.so.49.0
? nss-3.32-libnssdbm3.so.49.0
? nss-3.32-libnssutil3.so.49.0
? nss-3.32-libsmime3.so.49.0
? nss-3.32-libsoftokn3.so.49.0
? nss-3.32-libssl3.so.49.0
? nss-3.32.1-libfreebl3.so.49.0
? nss-3.32.1-libnss3.so.49.0
? nss-3.32.1-libnssckbi.so.49.0
? nss-3.32.1-libnssdbm3.so.49.0
? nss-3.32.1-libnssutil3.so.49.0
? nss-3.32.1-libsmime3.so.49.0
? nss-3.32.1-libsoftokn3.so.49.0
? nss-3.32.1-libssl3.so.49.0
? nss-3.33-libfreebl3.so.49.0
? nss-3.33-libnss3.so.49.0
? nss-3.33-libnssckbi.so.49.0
? nss-3.33-libnssdbm3.so.49.0
? nss-3.33-libnssutil3.so.49.0
? nss-3.33-libsmime3.so.49.0
? nss-3.33-libsoftokn3.so.49.0
? nss-3.33-libssl3.so.49.0
? nss-3.34-libfreebl3.so.49.1
? nss-3.34-libnss3.so.49.1
? nss-3.34-l

[update] sqlite 3.24

2018-06-24 Thread Landry Breuil
Hi,

here's an update to sqlite 3.24, bunch of changes, cf
https://www.sqlite.org/releaselog/3_24_0.html

Will put it in my next bulk.
Landry
? sqlite3-3.14.2-libsqlite3.so.33.0
? sqlite3-3.16.2-libsqlite3.so.34.0
? sqlite3-3.17.0-libsqlite3.so.35.0
? sqlite3-3.19.3-libsqlite3.so.36.0
? sqlite3-3.20.0-libsqlite3.so.37.0
? sqlite3-3.20.1-libsqlite3.so.37.1
? sqlite3-3.21.0-libsqlite3.so.37.1
? sqlite3-3.22.0-libsqlite3.so.37.1
? sqlite3-3.23.0-libsqlite3.so.37.2
? sqlite3-3.23.1-libsqlite3.so.37.2
? sqlite3-3.24.0-libsqlite3.so.37.2
Index: Makefile
===
RCS file: /cvs/ports/databases/sqlite3/Makefile,v
retrieving revision 1.93
diff -u -r1.93 Makefile
--- Makefile12 May 2018 18:11:34 -  1.93
+++ Makefile24 Jun 2018 20:12:31 -
@@ -2,10 +2,10 @@
 
 COMMENT=   embedded SQL implementation
 
-DISTNAME = sqlite-autoconf-3230100
-PKGNAME=   sqlite3-3.23.1
+DISTNAME = sqlite-autoconf-324
+PKGNAME=   sqlite3-3.24.0
 
-SHARED_LIBS +=  sqlite3   37.2 # 8.6
+SHARED_LIBS +=  sqlite3   37.3 # 8.6
 
 CATEGORIES=databases
 
Index: distinfo
===
RCS file: /cvs/ports/databases/sqlite3/distinfo,v
retrieving revision 1.49
diff -u -r1.49 distinfo
--- distinfo12 May 2018 18:11:34 -  1.49
+++ distinfo24 Jun 2018 20:12:31 -
@@ -1,2 +1,2 @@
-SHA256 (sqlite-autoconf-3230100.tar.gz) = 
koQrKD5edE7/XaKe08aTkd5zaPzMTQ7mv2JJDOVV7yU=
-SIZE (sqlite-autoconf-3230100.tar.gz) = 2675362
+SHA256 (sqlite-autoconf-324.tar.gz) = 
2dFOiMb7bWjenKDR+Xl0d9gvw67WE1WPh/+9u8XOt0o=
+SIZE (sqlite-autoconf-324.tar.gz) = 2699252


Re: [UPDATE] net/geomyidae 0.31 -> 0.32.1

2018-06-24 Thread Solene Rapenne


Joerg Jung writes:

>> On 24. Jun 2018, at 15:43, Hiltjo Posthuma  wrote:
>> 
>> This patch updates geomyidae.
>> 
>> Some changes compared to 0.31:
>> 
>> - Add OpenBSD pledge support.
>> - Fix: Return an error message for selectors containing two dots.
>> - Log UTC time instead of localized time.
>> - Add nocgi flag, which disables CGI execution.
>> - Minor fixed in the manpage, CGI handling and tools.
>> - Add example for tt escaping in the manpage.
>
> Thanks, LGTM. 
> I will take care of it soon.
>

ok solene@



Re: httpd rewrite

2018-06-24 Thread Elias M. Mariani
Okey, my bad selecting the mailing list, sorry, ignore this thread...

2018-06-24 16:51 GMT-03:00 Elias M. Mariani :
> Hi Reyk,
> Just a simple question,
> Will httpd implement something like .htaccess ?
> I mean, a way in witch the directories can define the rewrite policy ?
> The reason for this is that I want to use httpd to replace
> apache-httpd in a server that I share with some friends and having to
> write rewrite rules in httpd.conf for each one is impossible...
> Maybe there could be a reserved file in the root folder where the
> rewrite for all following directories is written?
> I understand that you don't want to bloat the code, maybe this is a
> way, allowing the rewrite rules to be read from the root dir if
> httpd.conf defines an option.
>
> Cheers.
> Elias.



httpd rewrite

2018-06-24 Thread Elias M. Mariani
Hi Reyk,
Just a simple question,
Will httpd implement something like .htaccess ?
I mean, a way in witch the directories can define the rewrite policy ?
The reason for this is that I want to use httpd to replace
apache-httpd in a server that I share with some friends and having to
write rewrite rules in httpd.conf for each one is impossible...
Maybe there could be a reserved file in the root folder where the
rewrite for all following directories is written?
I understand that you don't want to bloat the code, maybe this is a
way, allowing the rewrite rules to be read from the root dir if
httpd.conf defines an option.

Cheers.
Elias.



Re: x11/kde-applications/analitza ./kalgebra ./cantor

2018-06-24 Thread Landry Breuil
On Sun, Jun 24, 2018 at 07:13:35PM +0200, Rafael Sadowski wrote:
> *ping* after independent test.

Provided that you fixed the issues reported by elias (please show the
fixes..) and you recheck wantlibs:

LIB_DEPENDS STEM->=5.46:devel/kf5/kirigami2 not needed for devel/kf5/knewstuff ?

cantor-17.12.3(x11/kde-applications/cantor):
Missing: Qt5Concurrent.2 from qtbase-5.9.4 
(/usr/local/lib/qt5/plugins/libcantorpart.so)
Missing lib: R.34 (/usr/local/bin/cantor_rserver) (NOT REACHABLE)
Missing lib: Rblas.34 (/usr/local/bin/cantor_rserver) (NOT REACHABLE)
Missing lib: Rlapack.34 (/usr/local/bin/cantor_rserver) (NOT REACHABLE)
Extra:  quadmath.1
WANTLIB += Qt5Concurrent

ok to import the 3 and unhook the old stuff.



Re: [UPDATE] net/geomyidae 0.31 -> 0.32.1

2018-06-24 Thread Joerg Jung



> On 24. Jun 2018, at 15:43, Hiltjo Posthuma  wrote:
> 
> This patch updates geomyidae.
> 
> Some changes compared to 0.31:
> 
> - Add OpenBSD pledge support.
> - Fix: Return an error message for selectors containing two dots.
> - Log UTC time instead of localized time.
> - Add nocgi flag, which disables CGI execution.
> - Minor fixed in the manpage, CGI handling and tools.
> - Add example for tt escaping in the manpage.

Thanks, LGTM. 
I will take care of it soon.

> diff --git net/geomyidae/Makefile net/geomyidae/Makefile
> index cc0936b2f6b..55a6c95914b 100644
> --- net/geomyidae/Makefile
> +++ net/geomyidae/Makefile
> @@ -2,7 +2,7 @@
> 
> COMMENT = Gopher protocol daemon
> 
> -DISTNAME =   geomyidae-0.31
> +DISTNAME =   geomyidae-0.32.1
> 
> CATEGORIES =  net
> 
> @@ -13,6 +13,7 @@ MAINTAINER =Joerg Jung 
> # MIT/X
> PERMIT_PACKAGE_CDROM =Yes
> 
> +# uses pledge()
> WANTLIB = c
> 
> MASTER_SITES =${HOMEPAGE}/snapshot/
> diff --git net/geomyidae/distinfo net/geomyidae/distinfo
> index c10787f1ff3..bc6828b29b4 100644
> --- net/geomyidae/distinfo
> +++ net/geomyidae/distinfo
> @@ -1,2 +1,2 @@
> -SHA256 (geomyidae-0.31.tar.gz) = uu/bgmvBpRTR3aSWnjOy72Kn752DlMuevWX44GSbGRI=
> -SIZE (geomyidae-0.31.tar.gz) = 20265
> +SHA256 (geomyidae-0.32.1.tar.gz) = 
> 34hKoERXxp8DDf+tUBeLlqw2SVIQHk2NnsoHzGCieag=
> +SIZE (geomyidae-0.32.1.tar.gz) = 20881
> 
> -- 
> Kind regards,
> Hiltjo
> 



Re: Browser regression: chromium, firefox, iridium

2018-06-24 Thread Martijn Rijkeboer

On 06/23/18 04:10, Daniel Bolgheroni wrote:

On Fri, Jun 22, 2018 at 03:49:20PM +, Martijn Rijkeboer wrote:

Hi,

I have two desktops that run current. After I updated the first desktop
to the latest snapshot I can no longer access ProtonMail
(mail.protonmail.com). When I try, I get the following results:
- Chromium: "Aw, Snap!"
- Firefox: Infinite "Loading ProtonMail..."
- Iridium: "Aw, Snap!"

Any idea how to fix this?


At least for Firefox, try setting javascript.options.asmjs to false in
about:config.


Thanks, that worked. At least I can access ProtonMail again using
Firefox.

Kind regards,


Martijn Rijkeboer



Re: NEW: graphics/digikam [4/4 digikam 5]

2018-06-24 Thread Rafael Sadowski
*ping* after independent test

On Sun Jun 17, 2018 at 09:31:51PM -0300, Elias M. Mariani wrote:
> The application starts OK with the new revision of qtwebkit.
> I did not test the functionality, might be some bugs in there...
> No big errors in the console.
> 
> I think its OK to replace the old version of digikam.
> 
> Cheers.
> Elias.
> 
> 2018-06-16 4:02 GMT-03:00 Rafael Sadowski :
> > Please update qtwebkit and everything should be back to normal.
> >
> > On Sun Jun 10, 2018 at 09:23:52PM -0300, Elias M. Mariani wrote:
> >> No good.
> >> Couldn't get digikam to work.
> >> This one will be hard to crack.
> >>
> >> Cheers.
> >> Elias.
> >>
> >> 2018-06-09 21:37 GMT-03:00 Elias M. Mariani :
> >> > Well, after applying the patch to graphics/opencv,
> >> > Compiling that beast of code.
> >> > Then compiling the mega-beast of code that is digikam...
> >> > I return with a "No OK".
> >> > At least in this machine where I run the tests.
> >> > Even worst, I do not have much to help debug...
> >> >
> >> > After the "loading cameras..." splash screen the application goes
> >> > down, attached you will find the output of the console, after the last
> >> > line the application just closes.
> >> >
> >> > It might be a problem with how I applied the patch for OpenCV, so I
> >> > will compile one more time the beasts... I hate Digikam so much... So
> >> > wait for a further report but probably the problem is elsewhere.
> >> >
> >> > Cheers.
> >> > Elias.
> >>
> 



Re: x11/kde-applications/analitza ./kalgebra ./cantor

2018-06-24 Thread Rafael Sadowski
*ping* after independent test.

On Fri Jun 08, 2018 at 11:00:20AM -0300, Elias M. Mariani wrote:
> analitza compiles OK.
> Its a library so the test is done by the use of kalgebra and cantor.
> 
> kalgebra:
> calgebra worked OK.
> kalgebramobile is missing a run dependency:
> - qtgraphicaleffects
> And it gives this warning that may be good to check out:
> "JIT is disabled for QML. Property bindings and animations will be
> very slow. Visit https://wiki.qt.io/V4 to learn about possible
> solutions for your platform."
> And some random errors from qtsvg and others, but nothing unusual about 
> that...
> The application works OK, at least the calculator/analyzer and the 2D
> function plotter.
> It really works very slow, that is why maybe you should look about
> that JIT/QML error.
> 
> cantor:
> Tested using kalgebra, works OK.
> 
> Cheers.
> Elias.
> 



Re: UPDATE: security/sshguard, 1.5-->2.1.0 (2nd try)

2018-06-24 Thread Klemens Nanni
On Mon, Apr 23, 2018 at 11:12:55AM +0200, Andreas Kusalananda Kähäri wrote:
> On Sun, Apr 22, 2018 at 04:04:02PM +0200, Andreas Kusalananda Kähäri wrote:
> > On Sun, Apr 22, 2018 at 04:03:23PM +0200, Andreas Kusalananda Kähäri wrote:
> > > 
> > > Please find the diffs for an updated port of sshguard attached.
> > 
> > Now actually attached, duh.
> > 
> 
> Updated patch attached with comments from kn@ taken into account, but
> with CONFIGURE_STYLE=gnu left in place as suggested by Jeremie and
> Stuart.
I forgot about this diff when removing -O2 earlier (portroach also
wouldn't detect an update due to EXTRACT_SUFX change), thanks Andreas
for reminding me.

The diff looks good, I made a few additional changes:

- Drop README: sshguard-intro(7) contains all relevant information
- sshguard.rc: $pexp -> ${pexp}, unfold rc_stop()
- Makefile: Use SUBST_CMD and INSTALL_DATA just once

On amd64 sshguard continues to work.

1.5.0 is broken on sparc64 due to an assertion failure when parsing log
lines, 2.1.0 fixed this.

OK?

Index: Makefile
===
RCS file: /cvs/ports/security/sshguard/Makefile,v
retrieving revision 1.12
diff -u -p -r1.12 Makefile
--- Makefile24 Jun 2018 10:54:19 -  1.12
+++ Makefile24 Jun 2018 14:45:49 -
@@ -2,8 +2,7 @@
 
 COMMENT=   protect against brute force attacks on sshd and others
 
-DISTNAME=  sshguard-1.5
-REVISION=  5
+DISTNAME=  sshguard-2.1.0
 CATEGORIES=security
 
 # BSD
@@ -13,11 +12,18 @@ WANTLIB+=   c pthread
 
 HOMEPAGE=  https://www.sshguard.net/
 MASTER_SITES=  ${MASTER_SITE_SOURCEFORGE:=sshguard/}
-EXTRACT_SUFX=  .tar.bz2
 
 CONFIGURE_STYLE=gnu
-CONFIGURE_ARGS=--with-firewall=pf
 
 NO_TEST=   Yes
+
+post-patch:
+   ${SUBST_CMD} ${WRKSRC}/doc/sshguard.8 \
+   ${WRKSRC}/examples/sshguard.conf.sample
+
+post-install:
+   ${INSTALL_DATA_DIR} ${PREFIX}/share/examples/sshguard/
+   ${INSTALL_DATA} ${WRKSRC}/examples/*.{example,sample} \
+   ${PREFIX}/share/examples/sshguard/
 
 .include 
Index: distinfo
===
RCS file: /cvs/ports/security/sshguard/distinfo,v
retrieving revision 1.3
diff -u -p -r1.3 distinfo
--- distinfo27 Jan 2014 15:49:15 -  1.3
+++ distinfo24 Jun 2018 14:45:49 -
@@ -1,2 +1,2 @@
-SHA256 (sshguard-1.5.tar.bz2) = tTf4dlRV/fhCT4fUvWleW2dbiOXRZIZUUhN5Rwk+fhk=
-SIZE (sshguard-1.5.tar.bz2) = 303767
+SHA256 (sshguard-2.1.0.tar.gz) = ISUqSDSthAjfOE7k3fRoYkqp3pzq1a/eHHc4CkjPAoo=
+SIZE (sshguard-2.1.0.tar.gz) = 1117466
Index: patches/patch-configure
===
RCS file: patches/patch-configure
diff -N patches/patch-configure
--- patches/patch-configure 24 Jun 2018 10:54:19 -  1.1
+++ /dev/null   1 Jan 1970 00:00:00 -
@@ -1,13 +0,0 @@
-$OpenBSD: patch-configure,v 1.1 2018/06/24 10:54:19 kn Exp $
-
-Index: configure
 configure.orig
-+++ configure
-@@ -5949,7 +5949,6 @@ then
- STD99_CFLAGS="-xc99"
- else
- # other compiler (assume gcc-compatibile :( )
--OPTIMIZER_CFLAGS="-O2"
- WARNING_CFLAGS="-Wall"
- STD99_CFLAGS="-std=c99"
- fi
Index: patches/patch-doc_sshguard_8
===
RCS file: patches/patch-doc_sshguard_8
diff -N patches/patch-doc_sshguard_8
--- /dev/null   1 Jan 1970 00:00:00 -
+++ patches/patch-doc_sshguard_824 Jun 2018 14:45:49 -
@@ -0,0 +1,14 @@
+$OpenBSD$
+
+Index: doc/sshguard.8
+--- doc/sshguard.8.orig
 doc/sshguard.8
+@@ -119,7 +119,7 @@ Set to enable verbose output from sshg\-blocker.
+ .SH FILES
+ .INDENT 0.0
+ .TP
+-.B %PREFIX%/etc/sshguard.conf
++.B ${SYSCONFDIR}/sshguard.conf
+ See sample configuration file.
+ .UNINDENT
+ .SH WHITELISTING
Index: patches/patch-examples_sshguard_conf_sample
===
RCS file: patches/patch-examples_sshguard_conf_sample
diff -N patches/patch-examples_sshguard_conf_sample
--- /dev/null   1 Jan 1970 00:00:00 -
+++ patches/patch-examples_sshguard_conf_sample 24 Jun 2018 14:45:49 -
@@ -0,0 +1,31 @@
+$OpenBSD$
+
+Index: examples/sshguard.conf.sample
+--- examples/sshguard.conf.sample.orig
 examples/sshguard.conf.sample
+@@ -7,9 +7,11 @@
+  REQUIRED CONFIGURATION 
+ # Full path to backend executable (required, no default)
+ #BACKEND="/usr/local/libexec/sshg-fw-iptables"
++BACKEND="${TRUEPREFIX}/libexec/sshg-fw-pf"
+ 
+ # Space-separated list of log files to monitor. (optional, no default)
+ #FILES="/var/log/auth.log /var/log/authlog /var/log/maillog"
++FILES="/var/log/authlog"
+ 
+ # Shell command that provides logs on standard output. (optional, no default)
+ # Example 1: ssh and sendmail from systemd journal:
+@@ -40,11 +42,11 @@ DETECTION_TIME=1800
+ # !! Warning: These features may not work correctly with sandboxing. !!
+ 
+ # Full path to PID file (optional,

[UPDATE] net/geomyidae 0.31 -> 0.32.1

2018-06-24 Thread Hiltjo Posthuma
Hi,

This patch updates geomyidae.

Some changes compared to 0.31:

- Add OpenBSD pledge support.
- Fix: Return an error message for selectors containing two dots.
- Log UTC time instead of localized time.
- Add nocgi flag, which disables CGI execution.
- Minor fixed in the manpage, CGI handling and tools.
- Add example for tt escaping in the manpage.


diff --git net/geomyidae/Makefile net/geomyidae/Makefile
index cc0936b2f6b..55a6c95914b 100644
--- net/geomyidae/Makefile
+++ net/geomyidae/Makefile
@@ -2,7 +2,7 @@
 
 COMMENT =  Gopher protocol daemon
 
-DISTNAME = geomyidae-0.31
+DISTNAME = geomyidae-0.32.1
 
 CATEGORIES =   net
 
@@ -13,6 +13,7 @@ MAINTAINER =  Joerg Jung 
 # MIT/X
 PERMIT_PACKAGE_CDROM = Yes
 
+# uses pledge()
 WANTLIB =  c
 
 MASTER_SITES = ${HOMEPAGE}/snapshot/
diff --git net/geomyidae/distinfo net/geomyidae/distinfo
index c10787f1ff3..bc6828b29b4 100644
--- net/geomyidae/distinfo
+++ net/geomyidae/distinfo
@@ -1,2 +1,2 @@
-SHA256 (geomyidae-0.31.tar.gz) = uu/bgmvBpRTR3aSWnjOy72Kn752DlMuevWX44GSbGRI=
-SIZE (geomyidae-0.31.tar.gz) = 20265
+SHA256 (geomyidae-0.32.1.tar.gz) = 34hKoERXxp8DDf+tUBeLlqw2SVIQHk2NnsoHzGCieag=
+SIZE (geomyidae-0.32.1.tar.gz) = 20881

-- 
Kind regards,
Hiltjo



Re: NEW: sysutils/seq

2018-06-24 Thread Stuart Henderson
On 2018/06/24 13:51, Klemens Nanni wrote:
> On Sun, Jun 24, 2018 at 12:42:54PM +0100, Stuart Henderson wrote:
> > Like realpath, this is another of those things where I think if it makes
> > sense to have on OpenBSD at all, base is a better place for it ..
> We have jot(1) in base; different synopsis but more versatile already.
> 
>   $ jot -s' ' 10 1 10 1
>   1 2 3 4 5 6 7 8 9 10
> 

We do, and we also have a number of slightly annoying patches to ports
to use this instead of seq.

(Also like realpath, it's something that could be reasonably be handled
as a __progname switch in jot ..)



Re: NEW: sysutils/seq

2018-06-24 Thread Klemens Nanni
On Sun, Jun 24, 2018 at 12:42:54PM +0100, Stuart Henderson wrote:
> Like realpath, this is another of those things where I think if it makes
> sense to have on OpenBSD at all, base is a better place for it ..
We have jot(1) in base; different synopsis but more versatile already.

$ jot -s' ' 10 1 10 1
1 2 3 4 5 6 7 8 9 10



Re: unbreak py-cryptodome on non-x86 archs

2018-06-24 Thread Stuart Henderson
On 2018/06/24 12:43, Markus Hennecke wrote:
> CLMUL like AESNI is an extension to x86 archs, so treat it the same way in 
> PLIST:

Thanks, committed.

> Index: pkg/PLIST
> ===
> RCS file: /cvs/ports/security/py-cryptodome/pkg/PLIST,v
> retrieving revision 1.4
> diff -u -p -r1.4 PLIST
> --- pkg/PLIST 23 Jun 2018 11:52:30 -  1.4
> +++ pkg/PLIST 24 Jun 2018 10:38:39 -
> @@ -125,7 +125,7 @@ lib/python${MODPY_VERSION}/site-packages
>  
> lib/python${MODPY_VERSION}/site-packages/Crypto/Hash/${MODPY_PYCACHE}SHAKE256.${MODPY_PYC_MAGIC_TAG}pyc
>  
> lib/python${MODPY_VERSION}/site-packages/Crypto/Hash/${MODPY_PYCACHE}__init__.${MODPY_PYC_MAGIC_TAG}pyc
>  
> lib/python${MODPY_VERSION}/site-packages/Crypto/Hash/${MODPY_PYCACHE}keccak.${MODPY_PYC_MAGIC_TAG}pyc
> -lib/python${MODPY_VERSION}/site-packages/Crypto/Hash/_ghash_clmul.so
> +${AESNI_COMMENT}lib/python${MODPY_VERSION}/site-packages/Crypto/Hash/_ghash_clmul.so
>  lib/python${MODPY_VERSION}/site-packages/Crypto/Hash/_ghash_portable.so
>  lib/python${MODPY_VERSION}/site-packages/Crypto/Hash/_keccak.so
>  lib/python${MODPY_VERSION}/site-packages/Crypto/Hash/keccak.py
> 



Re: NEW: sysutils/seq

2018-06-24 Thread Stuart Henderson
On 2018/06/24 10:12, Jeremie Courreges-Anglas wrote:
> On Sat, Jun 23 2018, Brian Callahan  wrote:
> > Hi ports --
> >
> > Attached is a new port, sysutils/seq. seq is a utility to print sequences 
> > of numbers.
> >
> > ---
> > pkg/DESCR:
> > The seq utility prints a sequence of numbers, one per line, from an
> > optional initial value (default 1) to a final value, in increments of an
> > optional increment value (default 1). When the final value is larger
> > than the initial value, the default increment value is -1.
> >
> > It is a port of the seq utility from FreeBSD.
> > ---
> >
> > The other 3 BSDs have this utility in their base systems. No, I'm not
> > advocating for that. And yes, one could install GNU coreutils and get
> > gseq. But I see this utility used around enough that it's worth it for
> > me to maintain a port of it.
> 
> What makes it worth a new, separate port?  People could just install
> coreutils and use gseq.

Or plan9port and use the original one ;-)

> Is that version at least reasonably compatible
> with GNU seq?  If not, providing this as a package named "seq" would be
> misleading, maybe "freebsd-seq" would be more appropriate.
> 
> > Chose FreeBSD because it appears most
> > maintained.
> >
> > Numbered as it is because I took it from the tip of FreeBSD's tree.
> >
> > OK?
> 
> Do you know what would be the impact on the ports tree?  It would be
> a PITA if some ports started using this port at build time and then fail
> because of dpb(1) junking.

Like realpath, this is another of those things where I think if it makes
sense to have on OpenBSD at all, base is a better place for it ..



unbreak py-cryptodome on non-x86 archs

2018-06-24 Thread Markus Hennecke
CLMUL like AESNI is an extension to x86 archs, so treat it the same way in 
PLIST:

Index: pkg/PLIST
===
RCS file: /cvs/ports/security/py-cryptodome/pkg/PLIST,v
retrieving revision 1.4
diff -u -p -r1.4 PLIST
--- pkg/PLIST   23 Jun 2018 11:52:30 -  1.4
+++ pkg/PLIST   24 Jun 2018 10:38:39 -
@@ -125,7 +125,7 @@ lib/python${MODPY_VERSION}/site-packages
 
lib/python${MODPY_VERSION}/site-packages/Crypto/Hash/${MODPY_PYCACHE}SHAKE256.${MODPY_PYC_MAGIC_TAG}pyc
 
lib/python${MODPY_VERSION}/site-packages/Crypto/Hash/${MODPY_PYCACHE}__init__.${MODPY_PYC_MAGIC_TAG}pyc
 
lib/python${MODPY_VERSION}/site-packages/Crypto/Hash/${MODPY_PYCACHE}keccak.${MODPY_PYC_MAGIC_TAG}pyc
-lib/python${MODPY_VERSION}/site-packages/Crypto/Hash/_ghash_clmul.so
+${AESNI_COMMENT}lib/python${MODPY_VERSION}/site-packages/Crypto/Hash/_ghash_clmul.so
 lib/python${MODPY_VERSION}/site-packages/Crypto/Hash/_ghash_portable.so
 lib/python${MODPY_VERSION}/site-packages/Crypto/Hash/_keccak.so
 lib/python${MODPY_VERSION}/site-packages/Crypto/Hash/keccak.py



Re: trying to port LXQt (again).

2018-06-24 Thread Jeremie Courreges-Anglas
On Sun, Jun 24 2018, "Elias M. Mariani"  wrote:
> I'm having the attached error when trying to compile a dependency of lxqt.
> I don´t usually work with C libraries so I just wanted to ask here is
> anybody sees anything unusual.
> I can not find where atexit() is invoked...

See /usr/src/lib/csu.

> With my almost null experience with C, I'm guessing that this is a
> libraries problem, maybe the linker is grabbing the wrong library ?
> Or is it a headers problem ? because it finds crtbeginS.o but it
> doesn't get the definition from the header ?
> I didn't find anything on the FreeBSD port and I have been searching
> online about this for this for hours...
>
> Hopefully one you our savvy porters can point me in the right direction. :)

Try to get rid of -Wl,--no-undefined.

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



Re: [UPDATE] archivers/innoextract 1.7 (MAINTAINER)

2018-06-24 Thread Jeremie Courreges-Anglas
On Sat, Jun 23 2018, Donovan Watteau  wrote:
> Hi,

Hi,

> The following diff updates archivers/innoextract to 1.7:
> http://www.dwatteau.fr/tmp/innoextract17_update.diff
>
> Tested on amd64, loongson and macppc.
>
> (There's a warning suggesting to remove pthreads from WANTLIB on
> amd64, but ignore that because this dependency is used on macppc and
> loongson)

committed, thanks!

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



trying to port LXQt (again).

2018-06-24 Thread Elias M. Mariani
I'm having the attached error when trying to compile a dependency of lxqt.
I don´t usually work with C libraries so I just wanted to ask here is
anybody sees anything unusual.
I can not find where atexit() is invoked...
With my almost null experience with C, I'm guessing that this is a
libraries problem, maybe the linker is grabbing the wrong library ?
Or is it a headers problem ? because it finds crtbeginS.o but it
doesn't get the definition from the header ?
I didn't find anything on the FreeBSD port and I have been searching
online about this for this for hours...

Hopefully one you our savvy porters can point me in the right direction. :)

Cheers.
Elias.


compile.error
Description: Binary data


Re: update sysutils/uefitool 0.22.3 -> 0.24.0

2018-06-24 Thread Jeremie Courreges-Anglas
On Sat, Jun 23 2018, Klemens Nanni  wrote:
> * Adds descriptor version information for Intel images
> * Adds an extra patches.txt optional argument to UEFIPatch
> * Adds several other patches to UEFIPatch in patches-misc.txt (see #116, #123)
> * Fixes UEFIPatch handling of Coffee Lake images
> * Minor bugfixes
>
> Continues to work on amd64.
>
> OK?

ok jca@

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



Re: security/sshguard: remove hardcoded -O2

2018-06-24 Thread Jeremie Courreges-Anglas
On Sun, Jun 24 2018, Klemens Nanni  wrote:
> Patch out hardcoded OPTIMIZER_CFLAGS to allow `make CFLAGS=-g3'
> building without `-O2'.

I wouldn't expect overriding CFLAGS like that to work in all cases.
Some of our Makefiles contain lines like

  CFLAGS += ...

where what we append is required for a correct build, so overriding
CFLAGS on the cli isn't safe.  You could use DEBUG='-O0 -g3' here.

Anyway, I agree that hardcoding -O2 isn't desirable.

> Our CFLAGS contains `-O2', so no binary change with this diff by default.
>
> While here, switch to HTTPS and move/whitespace nitpick CONFIGURE_ARGS.
>
> OK?

ok jca@

> Index: Makefile
> ===
> RCS file: /cvs/ports/security/sshguard/Makefile,v
> retrieving revision 1.11
> diff -u -p -r1.11 Makefile
> --- Makefile  11 Jan 2018 19:27:09 -  1.11
> +++ Makefile  23 Jun 2018 23:37:52 -
> @@ -3,7 +3,7 @@
>  COMMENT= protect against brute force attacks on sshd and others
>  
>  DISTNAME=sshguard-1.5
> -REVISION=4
> +REVISION=5
>  CATEGORIES=  security
>  
>  # BSD
> @@ -11,13 +11,13 @@ PERMIT_PACKAGE_CDROM= Yes
>  
>  WANTLIB+=c pthread
>  
> -HOMEPAGE=http://www.sshguard.net/
> +HOMEPAGE=https://www.sshguard.net/
>  MASTER_SITES=${MASTER_SITE_SOURCEFORGE:=sshguard/}
>  EXTRACT_SUFX=.tar.bz2
>  
>  CONFIGURE_STYLE=gnu
> -NO_TEST= Yes
> +CONFIGURE_ARGS=  --with-firewall=pf
>  
> -CONFIGURE_ARGS = --with-firewall=pf 
> +NO_TEST= Yes
>  
>  .include 
> Index: patches/patch-configure
> ===
> RCS file: patches/patch-configure
> diff -N patches/patch-configure
> --- /dev/null 1 Jan 1970 00:00:00 -
> +++ patches/patch-configure   23 Jun 2018 23:09:22 -
> @@ -0,0 +1,13 @@
> +$OpenBSD$
> +
> +Index: configure
> +--- configure.orig
>  configure
> +@@ -5949,7 +5949,6 @@ then
> + STD99_CFLAGS="-xc99"
> + else
> + # other compiler (assume gcc-compatibile :( )
> +-OPTIMIZER_CFLAGS="-O2"
> + WARNING_CFLAGS="-Wall"
> + STD99_CFLAGS="-std=c99"
> + fi
>

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



Re: NEW: sysutils/seq

2018-06-24 Thread Jeremie Courreges-Anglas
On Sat, Jun 23 2018, Brian Callahan  wrote:
> Hi ports --
>
> Attached is a new port, sysutils/seq. seq is a utility to print sequences of 
> numbers.
>
> ---
> pkg/DESCR:
> The seq utility prints a sequence of numbers, one per line, from an
> optional initial value (default 1) to a final value, in increments of an
> optional increment value (default 1). When the final value is larger
> than the initial value, the default increment value is -1.
>
> It is a port of the seq utility from FreeBSD.
> ---
>
> The other 3 BSDs have this utility in their base systems. No, I'm not
> advocating for that. And yes, one could install GNU coreutils and get
> gseq. But I see this utility used around enough that it's worth it for
> me to maintain a port of it.

What makes it worth a new, separate port?  People could just install
coreutils and use gseq.  Is that version at least reasonably compatible
with GNU seq?  If not, providing this as a package named "seq" would be
misleading, maybe "freebsd-seq" would be more appropriate.

> Chose FreeBSD because it appears most
> maintained.
>
> Numbered as it is because I took it from the tip of FreeBSD's tree.
>
> OK?

Do you know what would be the impact on the ports tree?  It would be
a PITA if some ports started using this port at build time and then fail
because of dpb(1) junking.

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