Ping 2: [maintainer update] getmail 6.18.10 -> 6.18.11

2023-01-15 Thread Martin Ziemer
Am Mon, Jan 02, 2023 at 09:54:40AM +0100 schrieb Martin Ziemer:
> This patch updates getmail from 6.18.10 to 6.18.11.
> 
> For the new shell quotes, which fixes a security hole, i changed the
> getmails-script from using /bin/sh to use bash.
> 
> Tested on to amd64 systems.
> 
Index: Makefile
===
RCS file: /cvs/ports/mail/getmail/Makefile,v
retrieving revision 1.103
diff -u -p -u -p -r1.103 Makefile
--- Makefile9 Dec 2022 14:29:52 -   1.103
+++ Makefile2 Jan 2023 08:44:16 -
@@ -1,6 +1,6 @@
 COMMENT=   IMAP/POP3/SDPS mail retriever
 
-MODPY_EGG_VERSION= 6.18.10
+MODPY_EGG_VERSION= 6.18.11
 GH_ACCOUNT=getmail6
 GH_PROJECT=getmail6
 GH_TAGNAME=v${MODPY_EGG_VERSION}
@@ -18,6 +18,8 @@ PERMIT_PACKAGE=   Yes
 MODULES=   lang/python
 MODPY_PYBUILD= setuptools
 NO_TEST=   Yes
+
+RUN_DEPENDS=   shells/bash
 
 EXDIR= ${PREFIX}/share/examples/getmail
 
Index: distinfo
===
RCS file: /cvs/ports/mail/getmail/distinfo,v
retrieving revision 1.82
diff -u -p -u -p -r1.82 distinfo
--- distinfo9 Dec 2022 14:29:52 -   1.82
+++ distinfo2 Jan 2023 08:44:16 -
@@ -1,2 +1,2 @@
-SHA256 (getmail6-6.18.10.tar.gz) = DlYXz6LMh8WyWWNPWfVyjfOyVoqSyqVkdn4lb3mGatY=
-SIZE (getmail6-6.18.10.tar.gz) = 205481
+SHA256 (getmail6-6.18.11.tar.gz) = SD5PJr0PYsie0tRHazhArKu32GjEDeC8mT7HuWQtlok=
+SIZE (getmail6-6.18.11.tar.gz) = 207051
Index: patches/patch-getmails
===
RCS file: /cvs/ports/mail/getmail/patches/patch-getmails,v
retrieving revision 1.1
diff -u -p -u -p -r1.1 patch-getmails
--- patches/patch-getmails  9 Dec 2022 14:29:52 -   1.1
+++ patches/patch-getmails  2 Jan 2023 08:44:16 -
@@ -3,16 +3,22 @@
 Index: getmails
 --- getmails.orig
 +++ getmails
-@@ -28,7 +28,7 @@ BASE1=${1##*/}
- [ "$BASE1" != "${BASE1#$2}" ] && return 0 || return 1
+@@ -1,4 +1,4 @@
+-#!/bin/sh
++#!/usr/bin/env bash
+ # vim:se tw=78 sts=4:
+ # Copyright (C) 2011-2017 Osamu Aoki , GPL2+
+ 
+@@ -32,7 +32,7 @@ shellquote() {
+ printf '%s\n' "'${1//\'/\'\\\'\'}'"
  }
  UID_BY_ID=$(id -u)
 -PID_GETMAILS=$(pgrep -U $UID_BY_ID '^getmails$')
-+PID_GETMAILS=$(pgrep -f -U $UID_BY_ID '^/bin/sh /usr/local/bin/getmails$')
++PID_GETMAILS=$(pgrep -f -U $UID_BY_ID '^bash /usr/local/bin/getmails$')
  if [ "x$PID_GETMAILS" != "x$$" ]; then
echo "The getmails script is already running as PID=\"$PID_GETMAILS\" 
." >&2
exit 1
-@@ -44,7 +44,7 @@ if [ -f $getmailrcdir/stop ]; then
+@@ -48,7 +48,7 @@ if [ -f $getmailrcdir/stop ]; then
echo "Do not run getmail ... (if not, remove $getmailrcdir/stop)" >&2
exit 1
  fi
@@ -21,7 +27,7 @@ Index: getmails
  # Address concerns raised by #863856
  #  emacs backup files:   foo~ foo#
  #  vim backup files: foo~ foo.swp
-@@ -57,7 +57,8 @@ if $para ; then
+@@ -61,7 +61,8 @@ if $para ; then
 ! endwith "$file" '#' && \
 ! startswith "$file" 'oldmail-' && \
 ! endwith "$file" '.swp' && \
@@ -31,13 +37,13 @@ Index: getmails
$rcfiles --rcfile "$file" "$@" &
pids="$pids $!"
  fi
-@@ -79,7 +80,8 @@ else
+@@ -83,7 +84,8 @@ else
 ! endwith "$file" '#' && \
 ! startswith "$file" 'oldmail-' && \
 ! endwith "$file" '.swp' && \
 -   ! endwith "$file" '.bak' ; then
 +   ! endwith "$file" '.bak' && \
 +   [ -f "$file" ]; then
-   rcfiles="$rcfiles --rcfile \"$file\""
+ rcfiles="$rcfiles --rcfile $(shellquote "$file")"
  fi
  done



Re: audio/snack: drop python 2 bindings

2023-01-15 Thread Daniel Dickman



On Sun, 15 Jan 2023, Klemens Nanni wrote:

> 12.12.2022 03:04, Daniel Dickman ?:
> > On Sun, 11 Dec 2022, Klemens Nanni wrote:
> > 
> >> On Sat, Dec 03, 2022 at 10:15:16PM +, Klemens Nanni wrote:
> >>> On Sat, Dec 03, 2022 at 08:12:59PM +, Klemens Nanni wrote:
>  No upstream activity in years, I don't see py3 bits anywhere, so I
>  suggest we retire bindings for the EOL python 2.
> 
>  Merge -main and -python into a single audio/snack package.
>  Tested with
>   # pkg_add py-snack
>   $ make package
>   $ cp /usr/ports/packages/amd64/ftp/snack-2.2.10p7.tgz . 
>   $ doas env TRUSTED_PKG_PATH=. pkg_add -u
>   py-snack-2.2.10p2+snack-2.2.10p6->snack-2.2.10p7: ok
>   Read shared items: ok
> 
>  This gets rid of the last lang/python/2.7,-tkinter consumer, which could
>  be removed next.
> 
>  Feedback? Objection? OK?
> >>>
> >>> Now with cvs add'ed files.
> >>
> >> No feedback so far.
> >>
> >> Simpler diff leaving the MULTI_PACKAGES -main bits behind, then -python
> >> can be removed with a quirk.
> >>
> >> OK?
> >>
> > 
> > First of all, I think we may want the fix for CVE-2012-6303:
> > 
> > https://gitweb.gentoo.org/repo/gentoo.git/tree/dev-tcltk/snack/files/snack-2.2.10-CVE-2012-6303-fix.patch
> > 
> > As for python3, perhaps we can use gentoo's diff for this?
> > 
> > https://gitweb.gentoo.org/repo/gentoo.git/tree/dev-tcltk/snack/files/tcl-snack-2.2.10-python3.patch
> 
> Noone spoke up... anyone interested enough in patching and testing this?
> Otherwise we might as well plug the CVE and just drop python 2 bindings.
> 

Does this work for you?


Index: Makefile
===
RCS file: /cvs/ports/audio/snack/Makefile,v
retrieving revision 1.17
diff -u -p -u -r1.17 Makefile
--- Makefile11 Mar 2022 18:20:30 -  1.17
+++ Makefile16 Jan 2023 05:49:38 -
@@ -7,8 +7,8 @@ PKGNAME-main =  snack-${MODPY_EGG_VERSIO
 PKGNAME-python = py-snack-${MODPY_EGG_VERSION}
 CATEGORIES =   audio
 
-REVISION-main = 6
-REVISION-python =2
+REVISION-main = 7
+REVISION-python = 3
 
 HOMEPAGE = http://www.speech.kth.se/snack
 MASTER_SITES = ${HOMEPAGE}/dist/
@@ -25,7 +25,6 @@ LIB_DEPENDS-main =audio/libvorbis
 MULTI_PACKAGES =   -main -python
 
 MODULES =  lang/python x11/tk
-MODPY_VERSION =${MODPY_DEFAULT_VERSION_2}
 
 BUILD_DEPENDS =${MODTK_BUILD_DEPENDS}
 RUN_DEPENDS-main = ${MODTK_RUN_DEPENDS}
Index: patches/patch-demos_python_MinSect_py
===
RCS file: patches/patch-demos_python_MinSect_py
diff -N patches/patch-demos_python_MinSect_py
--- /dev/null   1 Jan 1970 00:00:00 -
+++ patches/patch-demos_python_MinSect_py   16 Jan 2023 05:49:38 -
@@ -0,0 +1,15 @@
+Index: demos/python/MinSect.py
+--- demos/python/MinSect.py.orig
 demos/python/MinSect.py
+@@ -1,9 +1,9 @@
+ #! /usr/bin/env python
+ 
+-from Tkinter import *
++from tkinter import *
+ from tkSnack import *
+ 
+-root = Tkinter.Tk()
++root = Tk()
+ 
+ initializeSnack(root)
+ 
Index: patches/patch-demos_python_MinSpeg_py
===
RCS file: patches/patch-demos_python_MinSpeg_py
diff -N patches/patch-demos_python_MinSpeg_py
--- /dev/null   1 Jan 1970 00:00:00 -
+++ patches/patch-demos_python_MinSpeg_py   16 Jan 2023 05:49:38 -
@@ -0,0 +1,15 @@
+Index: demos/python/MinSpeg.py
+--- demos/python/MinSpeg.py.orig
 demos/python/MinSpeg.py
+@@ -1,9 +1,9 @@
+ #! /usr/bin/env python
+ 
+-from Tkinter import *
++from tkinter import *
+ from tkSnack import *
+ 
+-root = Tkinter.Tk()
++root = Tk()
+ 
+ initializeSnack(root)
+ 
Index: patches/patch-demos_python_MinWave_py
===
RCS file: patches/patch-demos_python_MinWave_py
diff -N patches/patch-demos_python_MinWave_py
--- /dev/null   1 Jan 1970 00:00:00 -
+++ patches/patch-demos_python_MinWave_py   16 Jan 2023 05:49:38 -
@@ -0,0 +1,15 @@
+Index: demos/python/MinWave.py
+--- demos/python/MinWave.py.orig
 demos/python/MinWave.py
+@@ -1,9 +1,9 @@
+ #! /usr/bin/env python
+ 
+-from Tkinter import *
++from tkinter import *
+ from tkSnack import *
+ 
+-root = Tkinter.Tk()
++root = Tk()
+ 
+ initializeSnack(root)
+ 
Index: patches/patch-demos_python_dataCmd_py
===
RCS file: patches/patch-demos_python_dataCmd_py
diff -N patches/patch-demos_python_dataCmd_py
--- /dev/null   1 Jan 1970 00:00:00 -
+++ patches/patch-demos_python_dataCmd_py   16 Jan 2023 05:49:38 -
@@ -0,0 +1,12 @@
+Index: demos/python/dataCmd.py
+--- demos/python/dataCmd.py.orig
 demos/python/dataCmd.py
+@@ -1,7 +1,7 @@
+ #! /usr/bin/env python
+ # -*- coding: iso-8859-1 -*-
+ 
+-import Tkinter
++import tkinter as Tkinter
+ import tkSnack
+ 
+ root = Tkinter.Tk()
Index: patches/p

UPDATE: libheif 1.14.2

2023-01-15 Thread Brad Smith
Here is an update to libheif 1.14.2.

Upstream has deprecated the autoconf build as of 1.14.0, so
convert over to using CMake.


Index: Makefile
===
RCS file: /cvs/ports/multimedia/libheif/Makefile,v
retrieving revision 1.9
diff -u -p -u -p -r1.9 Makefile
--- Makefile5 Nov 2022 17:06:29 -   1.9
+++ Makefile16 Jan 2023 05:20:38 -
@@ -1,10 +1,9 @@
 COMMENT=   HEIF and AVIF file format decoder and encoder
 
-V= 1.13.0
+V= 1.14.2
 DISTNAME=  libheif-$V
-REVISION=  0
 
-SHARED_LIBS +=  heif  1.3 # 9.0
+SHARED_LIBS +=  heif  1.4 # 9.0
 
 CATEGORIES=multimedia graphics
 
@@ -13,26 +12,28 @@ HOMEPAGE=   https://github.com/strukturag/
 # LGPLv3+ (library), MIT (sample applications)
 PERMIT_PACKAGE=Yes
 
-WANTLIB += ${COMPILER_LIBCXX} aom c dav1d de265 ffi gdk_pixbuf-2.0
-WANTLIB += gio-2.0 glib-2.0 gmodule-2.0 gobject-2.0 iconv intl
-WANTLIB += jpeg m pcre2-8 png x265 z
+WANTLIB += ${COMPILER_LIBCXX} aom c dav1d de265 gdk_pixbuf-2.0
+WANTLIB += glib-2.0 gobject-2.0 intl jpeg m png x265
 
 MASTER_SITES=  https://github.com/strukturag/libheif/releases/download/v$V/
 
 COMPILER=  base-clang ports-gcc
 
-USE_GMAKE= Yes
-CONFIGURE_STYLE= gnu
-CONFIGURE_ARGS=--disable-go
-CONFIGURE_ENV= CPPFLAGS="-I${LOCALBASE}/include" \
-   LDFLAGS="-L${LOCALBASE}/lib"
+MODULES=   devel/cmake
 
 LIB_DEPENDS=   graphics/gdk-pixbuf2 \
multimedia/aom \
multimedia/dav1d \
multimedia/libde265 \
multimedia/x265
+# examples
+LIB_DEPENDS+=  graphics/jpeg \
+   graphics/png
+
 RUN_DEPENDS=   misc/shared-mime-info
+
+CONFIGURE_ARGS= -DWITH_RAV1E=Off \
+   -DWITH_SvtEnc=Off
 
 NO_TEST=   Yes
 
Index: distinfo
===
RCS file: /cvs/ports/multimedia/libheif/distinfo,v
retrieving revision 1.5
diff -u -p -u -p -r1.5 distinfo
--- distinfo6 Sep 2022 20:19:06 -   1.5
+++ distinfo16 Jan 2023 05:20:38 -
@@ -1,2 +1,2 @@
-SHA256 (libheif-1.13.0.tar.gz) = wgrgG6zjnokpj2NS8f9KVLQVszuXQ5Atp5jooeUdfKE=
-SIZE (libheif-1.13.0.tar.gz) = 1703950
+SHA256 (libheif-1.14.2.tar.gz) = 0BaQXiR9aVLNfuT5uQlXNQtqbKpGa8dv3+brMCttCIw=
+SIZE (libheif-1.14.2.tar.gz) = 1739439
Index: patches/patch-libheif_CMakeLists_txt
===
RCS file: patches/patch-libheif_CMakeLists_txt
diff -N patches/patch-libheif_CMakeLists_txt
--- /dev/null   1 Jan 1970 00:00:00 -
+++ patches/patch-libheif_CMakeLists_txt16 Jan 2023 05:20:38 -
@@ -0,0 +1,14 @@
+cmake: Use CMAKE_DL_LIBS instead of dl to fix build on OpenBSD
+
+Index: libheif/CMakeLists.txt
+--- libheif/CMakeLists.txt.orig
 libheif/CMakeLists.txt
+@@ -64,7 +64,7 @@ target_compile_definitions(heif
+ 
+ if (PLUGIN_LOADING_SUPPORTED_AND_ENABLED)
+ target_compile_definitions(heif PRIVATE ENABLE_PLUGIN_LOADING=1)
+-target_link_libraries(heif PRIVATE dl)
++target_link_libraries(heif PRIVATE ${CMAKE_DL_LIBS})
+ endif()
+ 
+ add_subdirectory(plugins)
Index: pkg/PLIST
===
RCS file: /cvs/ports/multimedia/libheif/pkg/PLIST,v
retrieving revision 1.3
diff -u -p -u -p -r1.3 PLIST
--- pkg/PLIST   11 Mar 2022 19:39:21 -  1.3
+++ pkg/PLIST   16 Jan 2023 05:20:38 -
@@ -7,11 +7,12 @@ include/libheif/heif.h
 include/libheif/heif_cxx.h
 include/libheif/heif_plugin.h
 include/libheif/heif_version.h
-@static-lib lib/gdk-pixbuf-2.0/2.10.0/loaders/libpixbufloader-heif.a
-lib/gdk-pixbuf-2.0/2.10.0/loaders/libpixbufloader-heif.la
+lib/cmake/libheif/
+lib/cmake/libheif/libheif-config${MODCMAKE_BUILD_SUFFIX}
+lib/cmake/libheif/libheif-config-version.cmake
+lib/cmake/libheif/libheif-config.cmake
 @so lib/gdk-pixbuf-2.0/2.10.0/loaders/libpixbufloader-heif.so
-@static-lib lib/libheif.a
-lib/libheif.la
+lib/libheif/
 @lib lib/libheif.so.${LIBheif_VERSION}
 lib/pkgconfig/libheif.pc
 @man man/man1/heif-convert.1



Re: Remove devel/gas?

2023-01-15 Thread Pascal Stumpf
On Sun, 15 Jan 2023 23:12:44 +0100, Frederic Cambus wrote:
> Hi ports@,
> 
> When I imported binutils back in August, sthen@ hinted that it was a
> bit strange to now have gas in a separate port [1], to which I agreed.
> 
> Following the binutils 2.40 update, I enabled the build of gas in the
> binutils package. This means we can now remove devel/gas.
> 
> CC'ed MAINTAINER (pascal@)
> 
> Comments? OK to remove it?

You need to test if lang/gcc/* still works fine with the newer gas from
binutils, on aarch64, arm, powerpc64 and riscv64.  Also keep in mind that
this will be the major test case for future binutils updates.  If that's
fine (and everything works), go for it.



Remove devel/gas?

2023-01-15 Thread Frederic Cambus
Hi ports@,

When I imported binutils back in August, sthen@ hinted that it was a
bit strange to now have gas in a separate port [1], to which I agreed.

Following the binutils 2.40 update, I enabled the build of gas in the
binutils package. This means we can now remove devel/gas.

CC'ed MAINTAINER (pascal@)

Comments? OK to remove it?



Re: [update] fish to 3.6.0 with failed tests (cmake to blame?)

2023-01-15 Thread Klemens Nanni
15.01.2023 21:30, Rafael Sadowski пишет:
> On Sun Jan 15, 2023 at 09:55:25PM +0100, Florian Viehweger wrote:
>> Hi,
>>
>> this updates fish to 3.6.0.
>>
>> 'portcheck' and 'make port-lib-depends-check' is happy, as well as some
>> runtime testing on amd64 revealed no errors.
>>
>> However all tests fail with not finding the tests directory:
>> 'Failed to change working directory to 
>> /usr/ports/pobj/fish-3.6.0/build-amd64/tests'
>>
>> I talked with op@ about it off list and we haven't found a change
>> regarding tests.
>>
>> However running 'make test' with fish 3.5.1 in ports also does make all
>> tests fail. This was not the case when it was imported. Some tests did
>> fail, but not all of them.
>>
>> This is why we suspect the cmake change which went in after fish 3.5.1.
>>
>> I'm unsure how to address this and I don't want to disable tests for
>> now.
>>
>> cc rsadowski@ and op@
>>
>> Thank you for any tips!
> 
> Quick solution. Looks like the test target is not part of the default
> target.  I suppose cmake.mk needs target support to handle it better.

Yes, {ALL,INSTALL,TEST}_TARGET all completely ignore by devel/cmake.

Changing that is easy in the module (I've looked into this recently),
but we should probably put this through a bulk and see how ports fare
when suddenly building the special 'all' target.

Rafael, unless you have plans for this, I can send a diff soon.

> 
> Cheers,
> 
> Rafael
> 
> Index: Makefile
> ===
> RCS file: /cvs/ports/shells/fish/Makefile,v
> retrieving revision 1.38
> diff -u -p -u -p -r1.38 Makefile
> --- Makefile  13 Nov 2022 15:29:44 -  1.38
> +++ Makefile  15 Jan 2023 21:25:55 -
> @@ -56,4 +56,10 @@ post-install:
>   mv ${PREFIX}/etc/fish/config.fish ${PREFIX}/share/examples/fish/
>   rm -Rf ${PREFIX}/etc/
>  
> +do-test:
> + cd ${WRKBUILD} && exec ${SETENV} ${MAKE_ENV} \
> + cmake --build ${WRKBUILD} ${_MAKE_VERBOSE} -j ${MAKE_JOBS} \
> + -t test

This should also work, no?

do-test:
${MODCMAKE_BUILD_TARGET} -t ${TEST_TARGET}

> +
> +
>  .include 
> 



Re: [update] fish to 3.6.0 with failed tests (cmake to blame?)

2023-01-15 Thread Rafael Sadowski
On Sun Jan 15, 2023 at 09:55:25PM +0100, Florian Viehweger wrote:
> Hi,
> 
> this updates fish to 3.6.0.
> 
> 'portcheck' and 'make port-lib-depends-check' is happy, as well as some
> runtime testing on amd64 revealed no errors.
> 
> However all tests fail with not finding the tests directory:
> 'Failed to change working directory to 
> /usr/ports/pobj/fish-3.6.0/build-amd64/tests'
> 
> I talked with op@ about it off list and we haven't found a change
> regarding tests.
> 
> However running 'make test' with fish 3.5.1 in ports also does make all
> tests fail. This was not the case when it was imported. Some tests did
> fail, but not all of them.
> 
> This is why we suspect the cmake change which went in after fish 3.5.1.
> 
> I'm unsure how to address this and I don't want to disable tests for
> now.
> 
> cc rsadowski@ and op@
> 
> Thank you for any tips!

Quick solution. Looks like the test target is not part of the default
target.  I suppose cmake.mk needs target support to handle it better.

Cheers,

Rafael

Index: Makefile
===
RCS file: /cvs/ports/shells/fish/Makefile,v
retrieving revision 1.38
diff -u -p -u -p -r1.38 Makefile
--- Makefile13 Nov 2022 15:29:44 -  1.38
+++ Makefile15 Jan 2023 21:25:55 -
@@ -56,4 +56,10 @@ post-install:
mv ${PREFIX}/etc/fish/config.fish ${PREFIX}/share/examples/fish/
rm -Rf ${PREFIX}/etc/
 
+do-test:
+   cd ${WRKBUILD} && exec ${SETENV} ${MAKE_ENV} \
+   cmake --build ${WRKBUILD} ${_MAKE_VERBOSE} -j ${MAKE_JOBS} \
+   -t test
+
+
 .include 



[update] fish to 3.6.0 with failed tests (cmake to blame?)

2023-01-15 Thread Florian Viehweger
Hi,

this updates fish to 3.6.0.

'portcheck' and 'make port-lib-depends-check' is happy, as well as some
runtime testing on amd64 revealed no errors.

However all tests fail with not finding the tests directory:
'Failed to change working directory to 
/usr/ports/pobj/fish-3.6.0/build-amd64/tests'

I talked with op@ about it off list and we haven't found a change
regarding tests.

However running 'make test' with fish 3.5.1 in ports also does make all
tests fail. This was not the case when it was imported. Some tests did
fail, but not all of them.

This is why we suspect the cmake change which went in after fish 3.5.1.

I'm unsure how to address this and I don't want to disable tests for
now.

cc rsadowski@ and op@

Thank you for any tips!


Index: Makefile
===
RCS file: /daten/openbsdmirror/cvs/mirror/ports/shells/fish/Makefile,v
retrieving revision 1.38
diff -u -p -u -p -r1.38 Makefile
--- Makefile13 Nov 2022 15:29:44 -  1.38
+++ Makefile15 Jan 2023 17:18:12 -
@@ -1,8 +1,7 @@
 COMMENT =  friendly interactive shell
 
-V =3.5.1
+V =3.6.0
 DISTNAME = fish-$V
-REVISION = 1
 
 CATEGORIES =   shells
 
Index: distinfo
===
RCS file: /daten/openbsdmirror/cvs/mirror/ports/shells/fish/distinfo,v
retrieving revision 1.13
diff -u -p -u -p -r1.13 distinfo
--- distinfo7 Aug 2022 09:29:35 -   1.13
+++ distinfo15 Jan 2023 17:18:12 -
@@ -1,2 +1,2 @@
-SHA256 (fish-3.5.1.tar.xz) = ptRbPcWkXdMXcuf439/sq8BjmG6PZ9YL18pgzIHbaSg=
-SIZE (fish-3.5.1.tar.xz) = 3329900
+SHA256 (fish-3.6.0.tar.xz) = lwRNV3c+58oVY09pPZF+0cPcD6f94QF/FibWC4PqYYE=
+SIZE (fish-3.6.0.tar.xz) = 2892296
Index: pkg/PLIST
===
RCS file: /daten/openbsdmirror/cvs/mirror/ports/shells/fish/pkg/PLIST,v
retrieving revision 1.17
diff -u -p -u -p -r1.17 PLIST
--- pkg/PLIST   31 Oct 2022 08:47:48 -  1.17
+++ pkg/PLIST   15 Jan 2023 17:18:12 -
@@ -66,8 +66,11 @@ share/doc/fish/cmds/fg.html
 share/doc/fish/cmds/fish.html
 share/doc/fish/cmds/fish_add_path.html
 share/doc/fish/cmds/fish_breakpoint_prompt.html
+share/doc/fish/cmds/fish_clipboard_copy.html
+share/doc/fish/cmds/fish_clipboard_paste.html
 share/doc/fish/cmds/fish_command_not_found.html
 share/doc/fish/cmds/fish_config.html
+share/doc/fish/cmds/fish_delta.html
 share/doc/fish/cmds/fish_git_prompt.html
 share/doc/fish/cmds/fish_greeting.html
 share/doc/fish/cmds/fish_hg_prompt.html
@@ -126,6 +129,7 @@ share/doc/fish/cmds/string-match.html
 share/doc/fish/cmds/string-pad.html
 share/doc/fish/cmds/string-repeat.html
 share/doc/fish/cmds/string-replace.html
+share/doc/fish/cmds/string-shorten.html
 share/doc/fish/cmds/string-split.html
 share/doc/fish/cmds/string-split0.html
 share/doc/fish/cmds/string-sub.html
@@ -232,9 +236,11 @@ share/fish/completions/arc.fish
 share/fish/completions/archlinux-java.fish
 share/fish/completions/arepack.fish
 share/fish/completions/argparse.fish
+share/fish/completions/ark.fish
 share/fish/completions/arp.fish
 share/fish/completions/as.fish
 share/fish/completions/asciidoctor.fish
+share/fish/completions/asciinema.fish
 share/fish/completions/asd.fish
 share/fish/completions/asp.fish
 share/fish/completions/at.fish
@@ -310,6 +316,8 @@ share/fish/completions/clasp.fish
 share/fish/completions/clean.fish
 share/fish/completions/cleanmgr.fish
 share/fish/completions/climate.fish
+share/fish/completions/clj.fish
+share/fish/completions/clojure.fish
 share/fish/completions/cmark.fish
 share/fish/completions/cmd.fish
 share/fish/completions/cmdkey.fish
@@ -330,6 +338,7 @@ share/fish/completions/conda.fish
 share/fish/completions/configure.fish
 share/fish/completions/conjure.fish
 share/fish/completions/connmanctl.fish
+share/fish/completions/contains.fish
 share/fish/completions/continue.fish
 share/fish/completions/convert.fish
 share/fish/completions/coredumpctl.fish
@@ -341,6 +350,7 @@ share/fish/completions/create_ap.fish
 share/fish/completions/createdb.fish
 share/fish/completions/cryptsetup.fish
 share/fish/completions/csc.fish
+share/fish/completions/csh.fish
 share/fish/completions/csharp.fish
 share/fish/completions/csi.fish
 share/fish/completions/cupsaccept.fish
@@ -366,8 +376,11 @@ share/fish/completions/dhclient.fish
 share/fish/completions/dhcpcd.fish
 share/fish/completions/diff.fish
 share/fish/completions/dig.fish
+share/fish/completions/direnv.fish
 share/fish/completions/diskutil.fish
+share/fish/completions/disown.fish
 share/fish/completions/display.fish
+share/fish/completions/dive.fish
 share/fish/completions/djview.fish
 share/fish/completions/djview4.fish
 share/fish/completions/djxl.fish
@@ -377,6 +390,7 @@ share/fish/completions/dmesg.fish
 share/fish/completions/dnf.fish
 share/fish/completions/doas.fish
 share/fish/completions/docker

net/syncthing: update to 1.23.0

2023-01-15 Thread Klemens Nanni
https://github.com/syncthing/syncthing/releases/tag/v1.23.0

builds and runs fine with go-1.19.4p1 on amd64.
Feedback? OK?

Index: Makefile
===
RCS file: /cvs/ports/net/syncthing/Makefile,v
retrieving revision 1.44
diff -u -p -r1.44 Makefile
--- Makefile8 Nov 2022 11:17:01 -   1.44
+++ Makefile15 Jan 2023 19:51:13 -
@@ -1,11 +1,8 @@
 COMMENT =  open decentralized synchronization utility
 
-# Using a release candidate until there's a release that supports go-1.19.
-V =1.21.0-rc.1
-PKGNAME =  syncthing-1.21.0rc1
+V =1.23.0
 DISTNAME = syncthing-${V}
 DISTFILES =syncthing-source-v${V}${EXTRACT_SUFX}
-REVISION = 0
 
 CATEGORIES =   net
 HOMEPAGE = https://syncthing.net/
Index: distinfo
===
RCS file: /cvs/ports/net/syncthing/distinfo,v
retrieving revision 1.30
diff -u -p -r1.30 distinfo
--- distinfo28 Aug 2022 09:06:56 -  1.30
+++ distinfo15 Jan 2023 19:46:00 -
@@ -1,2 +1,2 @@
-SHA256 (syncthing-source-v1.21.0-rc.1.tar.gz) = 
RmKjiV8KFCEl0dNu3LRaump/TaGG3P+KXAHPVGZX5fM=
-SIZE (syncthing-source-v1.21.0-rc.1.tar.gz) = 13884569
+SHA256 (syncthing-source-v1.23.0.tar.gz) = 
D2bT3Sp5FabzymdzwdwCNFREsmRKUzIRzh7lezca5Fg=
+SIZE (syncthing-source-v1.23.0.tar.gz) = 13936173
Index: patches/patch-build_go
===
RCS file: /cvs/ports/net/syncthing/patches/patch-build_go,v
retrieving revision 1.18
diff -u -p -r1.18 patch-build_go
--- patches/patch-build_go  12 Mar 2022 11:49:45 -  1.18
+++ patches/patch-build_go  15 Jan 2023 19:47:11 -
@@ -1,7 +1,7 @@
 Index: build.go
 --- build.go.orig
 +++ build.go
-@@ -544,7 +544,7 @@ func appendParameters(args []string, tags []string, pk
+@@ -547,7 +547,7 @@ func appendParameters(args []string, tags []string, pk
  
if !debugBinary {
// Regular binaries get version tagged and skip some debug 
symbols



Re: NEW: x11/kde-applications/markdownpart

2023-01-15 Thread Caspar Schutijser
On Sun, Jan 15, 2023 at 08:01:19PM +0100, Rafael Sadowski wrote:
> On Sun Jan 15, 2023 at 07:20:40PM +0100, Caspar Schutijser wrote:
> > On Sun, Jan 15, 2023 at 04:25:07PM +0100, Rafael Sadowski wrote:
> > > On Sun Jan 15, 2023 at 02:19:11PM +0100, Caspar Schutijser wrote:
> > > > Hi,
> > > > 
> > > > Any interest in this port? I adapted the x11/kde-applications/svgpart
> > > > port for this. Comments or OKs?
> > > > 
> > > > Caspar
> > > > 
> > > > 
> > > > Markdown Viewer KPart is a small KDE KPart component to display
> > > > Markdown files in Kate and in any other KDE application which uses
> > > > the KPart system.
> > > > 
> > > 
> > > 
> > > OK but please remove PKGNAME. I see no good reason to do that, do you?
> > 
> > Now that you mention it, yes, it probably makes sense to remove it.
> > However, I copied it from svgpart and I wonder whether it makes sense
> > to have it there then. What do you think? Not a big deal for me though.
> > I'll remove it from markdownpart.
> 
> Thanks. For a long time svgpart was a part of x11/kde4 so we added kf5
> prefix/suffix for some kde ports.
> 
> > 
> > Btw, I noticed that the Makefile in x11/kde-applications has some more
> > structure than other similar Makefiles; is the below diff OK to hook
> > it up or should I put it in another spot in this file? As you can see
> > I set CATEGORIES = textproc in markdownpart's Makefile so I figured I'd
> > add such a section here too but if you have any other preference, let
> > me know.
> 
> OpenBSD ports category textproc is right. KDE category, see blow.
> 
> > 
> > Caspar
> > 
> > 
> > Index: Makefile
> > ===
> > RCS file: /cvs/ports/x11/kde-applications/Makefile,v
> > retrieving revision 1.75
> > diff -u -p -r1.75 Makefile
> > --- Makefile20 Dec 2022 18:34:20 -  1.75
> > +++ Makefile15 Jan 2023 18:15:43 -
> > @@ -165,6 +165,9 @@
> >   SUBDIR += print-manager
> >   SUBDIR += sweeper
> >  
> > + # textproc
> > + SUBDIR += markdownpart
> > +
> 
> markdownpart is part of kde utilities
> (https://invent.kde.org/utilities/markdownpart)

Ah, right. Good to know. Then here's an updated diff, just to be sure.
OK?

Caspar


Index: Makefile
===
RCS file: /cvs/ports/x11/kde-applications/Makefile,v
retrieving revision 1.75
diff -u -p -r1.75 Makefile
--- Makefile20 Dec 2022 18:34:20 -  1.75
+++ Makefile15 Jan 2023 19:57:39 -
@@ -162,6 +162,7 @@
  SUBDIR += kteatime
  SUBDIR += ktimer
  SUBDIR += kwalletmanager
+ SUBDIR += markdownpart
  SUBDIR += print-manager
  SUBDIR += sweeper
 
@@ -257,7 +258,6 @@
  # kosmindoormap
  # kpmcore
  # kpublictransport
- # markdownpart
  # partitionmanager
 
 



[NEW] x11/grabc

2023-01-15 Thread Mattia Chiozzi
Hi,
I tried to make a port for grabc (https://github.com/muquit/grabc).

I added the pledge() system call as a patch. I tested it against all the flag
options and it shouldn't break anything.

-- 
Mattia Chiozzi
Email: mat...@chiozzi.cc
PEC: mat...@pec.chiozzi.cc


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


Re: NEW: x11/kde-applications/markdownpart

2023-01-15 Thread Rafael Sadowski
On Sun Jan 15, 2023 at 07:20:40PM +0100, Caspar Schutijser wrote:
> On Sun, Jan 15, 2023 at 04:25:07PM +0100, Rafael Sadowski wrote:
> > On Sun Jan 15, 2023 at 02:19:11PM +0100, Caspar Schutijser wrote:
> > > Hi,
> > > 
> > > Any interest in this port? I adapted the x11/kde-applications/svgpart
> > > port for this. Comments or OKs?
> > > 
> > > Caspar
> > > 
> > > 
> > > Markdown Viewer KPart is a small KDE KPart component to display
> > > Markdown files in Kate and in any other KDE application which uses
> > > the KPart system.
> > > 
> > 
> > 
> > OK but please remove PKGNAME. I see no good reason to do that, do you?
> 
> Now that you mention it, yes, it probably makes sense to remove it.
> However, I copied it from svgpart and I wonder whether it makes sense
> to have it there then. What do you think? Not a big deal for me though.
> I'll remove it from markdownpart.

Thanks. For a long time svgpart was a part of x11/kde4 so we added kf5
prefix/suffix for some kde ports.

> 
> Btw, I noticed that the Makefile in x11/kde-applications has some more
> structure than other similar Makefiles; is the below diff OK to hook
> it up or should I put it in another spot in this file? As you can see
> I set CATEGORIES = textproc in markdownpart's Makefile so I figured I'd
> add such a section here too but if you have any other preference, let
> me know.

OpenBSD ports category textproc is right. KDE category, see blow.

> 
> Caspar
> 
> 
> Index: Makefile
> ===
> RCS file: /cvs/ports/x11/kde-applications/Makefile,v
> retrieving revision 1.75
> diff -u -p -r1.75 Makefile
> --- Makefile  20 Dec 2022 18:34:20 -  1.75
> +++ Makefile  15 Jan 2023 18:15:43 -
> @@ -165,6 +165,9 @@
>   SUBDIR += print-manager
>   SUBDIR += sweeper
>  
> + # textproc
> + SUBDIR += markdownpart
> +

markdownpart is part of kde utilities
(https://invent.kde.org/utilities/markdownpart)

>   # webdev
>   SUBDIR += kimagemapeditor
>  
> @@ -257,7 +260,6 @@
>   # kosmindoormap
>   # kpmcore
>   # kpublictransport
> - # markdownpart
>   # partitionmanager
>  
>  



Re: NEW: x11/kde-applications/markdownpart

2023-01-15 Thread Caspar Schutijser
On Sun, Jan 15, 2023 at 04:25:07PM +0100, Rafael Sadowski wrote:
> On Sun Jan 15, 2023 at 02:19:11PM +0100, Caspar Schutijser wrote:
> > Hi,
> > 
> > Any interest in this port? I adapted the x11/kde-applications/svgpart
> > port for this. Comments or OKs?
> > 
> > Caspar
> > 
> > 
> > Markdown Viewer KPart is a small KDE KPart component to display
> > Markdown files in Kate and in any other KDE application which uses
> > the KPart system.
> > 
> 
> 
> OK but please remove PKGNAME. I see no good reason to do that, do you?

Now that you mention it, yes, it probably makes sense to remove it.
However, I copied it from svgpart and I wonder whether it makes sense
to have it there then. What do you think? Not a big deal for me though.
I'll remove it from markdownpart.

Btw, I noticed that the Makefile in x11/kde-applications has some more
structure than other similar Makefiles; is the below diff OK to hook
it up or should I put it in another spot in this file? As you can see
I set CATEGORIES = textproc in markdownpart's Makefile so I figured I'd
add such a section here too but if you have any other preference, let
me know.

Caspar


Index: Makefile
===
RCS file: /cvs/ports/x11/kde-applications/Makefile,v
retrieving revision 1.75
diff -u -p -r1.75 Makefile
--- Makefile20 Dec 2022 18:34:20 -  1.75
+++ Makefile15 Jan 2023 18:15:43 -
@@ -165,6 +165,9 @@
  SUBDIR += print-manager
  SUBDIR += sweeper
 
+ # textproc
+ SUBDIR += markdownpart
+
  # webdev
  SUBDIR += kimagemapeditor
 
@@ -257,7 +260,6 @@
  # kosmindoormap
  # kpmcore
  # kpublictransport
- # markdownpart
  # partitionmanager
 
 



OpenSSL 1.1 amd64 assembly fixes

2023-01-15 Thread Theo Buehler
This fixes the perlasm on my x-only amd64 machines to the point that
tests pass (apart form the shlibload test). This is quite a bit more
than what was committed to base libcrypto and it is very possible that I
missed some constants in .text.

So tests and careful sets of eyes would be very welcome.

Index: Makefile
===
RCS file: /cvs/ports/security/openssl/1.1/Makefile,v
retrieving revision 1.47
diff -u -p -r1.47 Makefile
--- Makefile14 Jan 2023 17:09:56 -  1.47
+++ Makefile15 Jan 2023 12:20:12 -
@@ -3,7 +3,7 @@ PORTROACH=  limit:^1\.1\.[0-9][a-z] skipb
 V= 1.1.1s
 PKGSPEC=   openssl->=1.1.0v0,<1.2v0
 EPOCH= 0
-REVISION=  2
+REVISION=  3
 
 SHLIBVER=  11.6
 SHARED_LIBS=   crypto ${SHLIBVER} \
@@ -35,7 +35,7 @@ MAN_PREFIX=   @man lib/eopenssl11/man
 INSTALL_TARGET+=   install_man_docs
 .endif
 
-.if ${MACHINE_ARCH} != aarch64
+.if ${MACHINE_ARCH} != aarch64 && ${MACHINE_ARCH} != amd64
 USE_NOEXECONLY=Yes
 .endif
 
Index: patches/patch-crypto_aes_asm_aesni-sha1-x86_64_pl
===
RCS file: patches/patch-crypto_aes_asm_aesni-sha1-x86_64_pl
diff -N patches/patch-crypto_aes_asm_aesni-sha1-x86_64_pl
--- /dev/null   1 Jan 1970 00:00:00 -
+++ patches/patch-crypto_aes_asm_aesni-sha1-x86_64_pl   15 Jan 2023 12:20:12 
-
@@ -0,0 +1,19 @@
+Index: crypto/aes/asm/aesni-sha1-x86_64.pl
+--- crypto/aes/asm/aesni-sha1-x86_64.pl.orig
 crypto/aes/asm/aesni-sha1-x86_64.pl
+@@ -1736,6 +1736,7 @@ ___
+   }}}
+ }
+ $code.=<<___;
++.rodata
+ .align64
+ K_XX_XX:
+ .long 0x5a827999,0x5a827999,0x5a827999,0x5a827999 # K_00_19
+@@ -1747,6 +1748,7 @@ K_XX_XX:
+ 
+ .asciz"AESNI-CBC+SHA1 stitch for x86_64, CRYPTOGAMS by 
"
+ .align64
++.previous
+ ___
+   if ($shaext) {{{
+ 
($in0,$out,$len,$key,$ivp,$ctx,$inp)=("%rdi","%rsi","%rdx","%rcx","%r8","%r9","%r10");
Index: patches/patch-crypto_aes_asm_aesni-sha256-x86_64_pl
===
RCS file: patches/patch-crypto_aes_asm_aesni-sha256-x86_64_pl
diff -N patches/patch-crypto_aes_asm_aesni-sha256-x86_64_pl
--- /dev/null   1 Jan 1970 00:00:00 -
+++ patches/patch-crypto_aes_asm_aesni-sha256-x86_64_pl 15 Jan 2023 12:20:12 
-
@@ -0,0 +1,19 @@
+Index: crypto/aes/asm/aesni-sha256-x86_64.pl
+--- crypto/aes/asm/aesni-sha256-x86_64.pl.orig
 crypto/aes/asm/aesni-sha256-x86_64.pl
+@@ -166,6 +166,7 @@ $code.=<<___;
+ .cfi_endproc
+ .size $func,.-$func
+ 
++.rodata
+ .align64
+ .type $TABLE,\@object
+ $TABLE:
+@@ -208,6 +209,7 @@ $TABLE:
+   .long   0,0,0,0,   0,0,0,0
+   .asciz  "AESNI-CBC+SHA256 stitch for x86_64, CRYPTOGAMS by 
"
+ .align64
++.previous
+ ___
+ 
+ ##
Index: patches/patch-crypto_aes_asm_aesni-x86_64_pl
===
RCS file: patches/patch-crypto_aes_asm_aesni-x86_64_pl
diff -N patches/patch-crypto_aes_asm_aesni-x86_64_pl
--- /dev/null   1 Jan 1970 00:00:00 -
+++ patches/patch-crypto_aes_asm_aesni-x86_64_pl15 Jan 2023 12:20:12 
-
@@ -0,0 +1,19 @@
+Index: crypto/aes/asm/aesni-x86_64.pl
+--- crypto/aes/asm/aesni-x86_64.pl.orig
 crypto/aes/asm/aesni-x86_64.pl
+@@ -4730,6 +4730,7 @@ ___
+ }
+ 
+ $code.=<<___;
++.rodata
+ .align64
+ .Lbswap_mask:
+   .byte   15,14,13,12,11,10,9,8,7,6,5,4,3,2,1,0
+@@ -4752,6 +4753,7 @@ $code.=<<___;
+ 
+ .asciz  "AES for Intel AES-NI, CRYPTOGAMS by "
+ .align64
++.previous
+ ___
+ 
+ # EXCEPTION_DISPOSITION handler (EXCEPTION_RECORD *rec,ULONG64 frame,
Index: patches/patch-crypto_aes_asm_vpaes-x86_64_pl
===
RCS file: patches/patch-crypto_aes_asm_vpaes-x86_64_pl
diff -N patches/patch-crypto_aes_asm_vpaes-x86_64_pl
--- /dev/null   1 Jan 1970 00:00:00 -
+++ patches/patch-crypto_aes_asm_vpaes-x86_64_pl15 Jan 2023 12:20:12 
-
@@ -0,0 +1,19 @@
+Index: crypto/aes/asm/vpaes-x86_64.pl
+--- crypto/aes/asm/vpaes-x86_64.pl.orig
 crypto/aes/asm/vpaes-x86_64.pl
+@@ -998,6 +998,7 @@ _vpaes_preheat:
+ ## Constants  ##
+ ####
+ 
++.rodata
+ .type _vpaes_consts,\@object
+ .align64
+ _vpaes_consts:
+@@ -1097,6 +1098,7 @@ _vpaes_consts:
+ .asciz"Vector Permutation AES for x86_64/SSSE3, Mike Hamburg 
(Stanford University)"
+ .align64
+ .size _vpaes_consts,.-_vpaes_consts
++.previous
+ ___
+ 
+ if ($win64) {
Index: patches/patch-crypto_bn_asm_rsaz-x86_64_pl
===
RCS file: patches/patch-cry

Re: remove x11/wxglade

2023-01-15 Thread Antoine Jacoutot
Thanks. In this case I can just temporarily mark it broken. 

—
Antoine

> On 15 Jan 2023, at 18:06, Daniel Winters  wrote:
> 
> Hi Theo,
> 
>>> Can I remove x11/wxglade?
>> 
>> Sure, unless MAINTAINER speaks up very soon.
> 
> Maintainer here: I think its best to remove it for now.
> 
> After we have a newer wxPython in the tree I will look at updating to a newer 
> version.
> 
> Cheers,
> Daniel
> 
> 



Re: remove x11/wxglade

2023-01-15 Thread Daniel Winters
Hi Theo,

>> Can I remove x11/wxglade?
> 
> Sure, unless MAINTAINER speaks up very soon.

Maintainer here: I think its best to remove it for now.

After we have a newer wxPython in the tree I will look at updating to a newer 
version.

Cheers,
Daniel



[Update] lang/elixir

2023-01-15 Thread Volker Schlecht
The attached diff modifies an existing patch to lang/elixir to detect 
erlang's erts directory (containing the "erl" binary) at runtime instead 
of hardcoding it to "erl${MODERL_VERSION}".


This fixes the remaining test failures that occurred because no 
self-contained releases could be built, plus it makes 'mix release' work 
properly on OpenBSD.


It also contains a trivial update to the latest bugfix release 1.14.3

Tested on amd64.Index: Makefile
===
RCS file: /cvs/ports/lang/elixir/Makefile,v
retrieving revision 1.65
diff -u -p -r1.65 Makefile
--- Makefile	23 Dec 2022 10:14:01 -	1.65
+++ Makefile	15 Jan 2023 15:43:17 -
@@ -1,6 +1,6 @@
 COMMENT=		functional language for building scalable applications
 
-V=			1.14.2
+V=			1.14.3
 GH_ACCOUNT=		elixir-lang
 GH_PROJECT=		elixir
 GH_TAGNAME=		v$V
Index: distinfo
===
RCS file: /cvs/ports/lang/elixir/distinfo,v
retrieving revision 1.55
diff -u -p -r1.55 distinfo
--- distinfo	23 Dec 2022 10:14:01 -	1.55
+++ distinfo	15 Jan 2023 15:43:17 -
@@ -1,2 +1,2 @@
-SHA256 (elixir-1.14.2.tar.gz) = P3njhHBklXJRGfYJgvoW6oLVEMP76s/G7hp3x5K/FSo=
-SIZE (elixir-1.14.2.tar.gz) = 3085613
+SHA256 (elixir-1.14.3.tar.gz) = vUZBRSV/Nr1k97qL7ZO2SZxQVxtBXEkbICZ9J9cDVwc=
+SIZE (elixir-1.14.3.tar.gz) = 3086297
Index: patches/patch-bin_elixir
===
RCS file: /cvs/ports/lang/elixir/patches/patch-bin_elixir,v
retrieving revision 1.8
diff -u -p -r1.8 patch-bin_elixir
--- patches/patch-bin_elixir	4 Sep 2022 08:36:44 -	1.8
+++ patches/patch-bin_elixir	15 Jan 2023 15:43:17 -
@@ -1,12 +1,16 @@
+Detect erlang ERTS directory at runtime.
+
 Index: bin/elixir
 --- bin/elixir.orig
 +++ bin/elixir
-@@ -92,7 +92,7 @@ starts_with () {
-   esac
- }
+@@ -226,7 +226,9 @@ fi
  
--ERL_EXEC="erl"
-+ERL_EXEC="erl${MODERL_VERSION}"
- MODE="elixir"
- I=1
- E=0
+ # One MAY change ERTS_BIN= but you MUST NOT change
+ # ERTS_BIN=$ERTS_BIN as it is handled by Elixir releases.
+-ERTS_BIN=
++for obsd_erts in ${LOCALBASE}/lib/erlang${MODERL_VERSION}/erts-*; do
++  ERTS_BIN="$obsd_erts/bin/";
++done
+ ERTS_BIN="$ERTS_BIN"
+ 
+ set -- "$ERTS_BIN$ERL_EXEC" -pa "$SCRIPT_PATH"/../lib/*/ebin $ELIXIR_ERL_OPTIONS $ERL "$@"


mips64 bulk build report

2023-01-15 Thread visa
bulk build on octeon.ports.openbsd.org
started on  Sun Jan 1 14:31:28 UTC 2023
finished at Wed Jan 11 03:56:47 UTC 2023
lasted 10D13h25m
done with kern.version=OpenBSD 7.2-current (GENERIC.MP) #1148: Sat Dec 31 
18:15:40 MST 2022

built packages:8910
Jan 1:3933
Jan 2:837
Jan 3:436
Jan 4:695
Jan 5:598
Jan 6:765
Jan 7:1007
Jan 8:364
Jan 9:274
Jan 10:1971
Jan 11:14


build failures: 79
http://build-failures.rhaalovely.net/mips64/2023-01-01/audio/espeak.log
http://build-failures.rhaalovely.net/mips64/2023-01-01/chinese/libpinyin.log
http://build-failures.rhaalovely.net/mips64/2023-01-01/databases/postgresql-pllua.log
http://build-failures.rhaalovely.net/mips64/2023-01-01/devel/clang-tools-extra.log
http://build-failures.rhaalovely.net/mips64/2023-01-01/devel/go-sys.log
http://build-failures.rhaalovely.net/mips64/2023-01-01/devel/protobuf.log
http://build-failures.rhaalovely.net/mips64/2023-01-01/devel/py-thrift,python3.log
http://build-failures.rhaalovely.net/mips64/2023-01-01/devel/py-unicorn,python3.log
http://build-failures.rhaalovely.net/mips64/2023-01-01/devel/sdcc.log
http://build-failures.rhaalovely.net/mips64/2023-01-01/emulators/openmsx.log
http://build-failures.rhaalovely.net/mips64/2023-01-01/emulators/spike.log
http://build-failures.rhaalovely.net/mips64/2023-01-01/games/astromenace.log
http://build-failures.rhaalovely.net/mips64/2023-01-01/games/hyperrogue.log
http://build-failures.rhaalovely.net/mips64/2023-01-01/games/unknown-horizons.log
http://build-failures.rhaalovely.net/mips64/2023-01-01/games/wesnoth.log
http://build-failures.rhaalovely.net/mips64/2023-01-01/games/witchblast.log
http://build-failures.rhaalovely.net/mips64/2023-01-01/geo/gpstk.log
http://build-failures.rhaalovely.net/mips64/2023-01-01/graphics/enblend-enfuse.log
http://build-failures.rhaalovely.net/mips64/2023-01-01/graphics/openvdb.log
http://build-failures.rhaalovely.net/mips64/2023-01-01/lang/STk.log
http://build-failures.rhaalovely.net/mips64/2023-01-01/lang/gambit.log
http://build-failures.rhaalovely.net/mips64/2023-01-01/lang/gforth.log
http://build-failures.rhaalovely.net/mips64/2023-01-01/lang/librep.log
http://build-failures.rhaalovely.net/mips64/2023-01-01/lang/pfe.log
http://build-failures.rhaalovely.net/mips64/2023-01-01/lang/php/8.1.log
http://build-failures.rhaalovely.net/mips64/2023-01-01/lang/php/8.2.log
http://build-failures.rhaalovely.net/mips64/2023-01-01/mail/opensmtpd-filters/rspamd.log
http://build-failures.rhaalovely.net/mips64/2023-01-01/math/gbc.log
http://build-failures.rhaalovely.net/mips64/2023-01-01/math/igraph.log
http://build-failures.rhaalovely.net/mips64/2023-01-01/math/lean.log
http://build-failures.rhaalovely.net/mips64/2023-01-01/math/lrs.log
http://build-failures.rhaalovely.net/mips64/2023-01-01/math/mlpack,-main.log
http://build-failures.rhaalovely.net/mips64/2023-01-01/math/ntl.log
http://build-failures.rhaalovely.net/mips64/2023-01-01/misc/remind.log
http://build-failures.rhaalovely.net/mips64/2023-01-01/multimedia/assimp.log
http://build-failures.rhaalovely.net/mips64/2023-01-01/net/eduvpn/vpn-daemon.log
http://build-failures.rhaalovely.net/mips64/2023-01-01/net/gortr.log
http://build-failures.rhaalovely.net/mips64/2023-01-01/net/gtk-gnutella.log
http://build-failures.rhaalovely.net/mips64/2023-01-01/net/icinga/core2.log
http://build-failures.rhaalovely.net/mips64/2023-01-01/net/libtorrent-rasterbar.log
http://build-failures.rhaalovely.net/mips64/2023-01-01/net/minio/client.log
http://build-failures.rhaalovely.net/mips64/2023-01-01/net/minio/server.log
http://build-failures.rhaalovely.net/mips64/2023-01-01/net/powerdns_recursor.log
http://build-failures.rhaalovely.net/mips64/2023-01-01/net/syncthing.log
http://build-failures.rhaalovely.net/mips64/2023-01-01/net/utox.log
http://build-failures.rhaalovely.net/mips64/2023-01-01/plan9/drawterm.log
http://build-failures.rhaalovely.net/mips64/2023-01-01/security/botan2.log
http://build-failures.rhaalovely.net/mips64/2023-01-01/security/go-siphash.log
http://build-failures.rhaalovely.net/mips64/2023-01-01/security/gobuster.log
http://build-failures.rhaalovely.net/mips64/2023-01-01/security/step-cli.log
http://build-failures.rhaalovely.net/mips64/2023-01-01/security/vault.log
http://build-failures.rhaalovely.net/mips64/2023-01-01/shells/elvish.log
http://build-failures.rhaalovely.net/mips64/2023-01-01/sysutils/amazon-ecs-cli.log
http://build-failures.rhaalovely.net/mips64/2023-01-01/sysutils/beats/filebeat.log
http://build-failures.rhaalovely.net/mips64/2023-01-01/sysutils/beats/heartbeat.log
http://build-failures.rhaalovely.net/mips64/2023-01-01/sysutils/beats/metricbeat.log
http://build-failures.rhaalovely.net/mips64/2023-01-01/sysutils/beats/packetbeat.log
http://build-failures.rhaalovely.net/mips64/2023-01-01/sysutils/dep.log
http://build-failures.rhaalovely.net/mips64/2023-01-01/sysutils/direnv.log
http://build-failures.rhaalovely.net/mips64/2023-01-01/sysutils/gitlab-runner.log
http://build-failures.rhaalovely.net/mips64/2023-01-01/sysu

Re: NEW: x11/kde-applications/markdownpart

2023-01-15 Thread Rafael Sadowski
On Sun Jan 15, 2023 at 02:19:11PM +0100, Caspar Schutijser wrote:
> Hi,
> 
> Any interest in this port? I adapted the x11/kde-applications/svgpart
> port for this. Comments or OKs?
> 
> Caspar
> 
> 
> Markdown Viewer KPart is a small KDE KPart component to display
> Markdown files in Kate and in any other KDE application which uses
> the KPart system.
> 


OK but please remove PKGNAME. I see no good reason to do that, do you?



[new] net/keycloak-20.0.3 - Identity and Access Management solution

2023-01-15 Thread aisha
Hi,
  I've attached a port of keycloak - https://www.keycloak.org/ - 
https://github.com/keycloak/keycloak - an identity and access management 
solution from redhat.
Copying the DESCR:

> Keycloak is an open source Identity and Access Management solution
> aimed at modern applications and services. It makes it easy to
> secure applications and services with little to no code, providing
> the following features:
> - SAML, OAuth 2.0 and OpenID Connect
> - Single Sign On
> - Admin Console
> - Account Management Console
> - User Federation with LDAP and Active Directory
> - Identity Brokering and Social Login


It has been working fine for a while now. The command line programs 'kcadm' and 
'kcreg' don't work as openbsd is not a recognized platform but I have opened 
PRs upstream to fix this and hopefully it should just work (tm) once they get 
merged.

tests and OKs welcome.

Cheers,
Aisha


keycloak-20.0.3.tgz
Description: GNU Zip compressed data


NEW: devel/robsd

2023-01-15 Thread Anton Lindqvist
Hi,
Here's a port with my tooling used to build snapshots and run regress
tests. Including a snippet from the readme below.

https://www.basename.se/robsd
https://github.com/mptre/robsd

Comments? OK?

This project started out as an attempt to automate the release(8)
process on OpenBSD. The prime motivation was to roll my own snapshots in
order to test my and others changes to the kernel, user space and
everything in between. Hence the name robsd as in release OpenBSD. The
scope later grew and the project is by now a kitchen sink for everything
related to building, testing and maintaining OpenBSD. It's written in
ksh with a dash of C and requires nothing other than what's included in
base.

The project is divided into the utilities as follows. All of them are
configured using a grammar that should be familiar for anyone with prior
OpenBSD experience.

# robsd

robsd builds a release according to the release process. Some of its
noteworthy features:

* The changes since the last build according to CVS is turned into a
  readable log, similar to the format seen on the *-changes mailing
  lists.
* Patches can be applied and reverted.
* Detection of build time changes.
* Detection of significant kernel and sets size changes.

# robsd-cross

robds-cross builds a cross compiler tool chain targeting another
architecture, using ${BSDSRCDIR}/Makefile.cross behind the scenes.

# robsd-ports

robsd-ports builds ports using dpb behind the scenes.

### robsd-regress

robsd-regress runs regression tests. HTML summaries can be rendered
using robsd-regress-html which also powers https://regress.basename.se.


robsd.tgz
Description: Binary data


NEW: x11/kde-applications/markdownpart

2023-01-15 Thread Caspar Schutijser
Hi,

Any interest in this port? I adapted the x11/kde-applications/svgpart
port for this. Comments or OKs?

Caspar


Markdown Viewer KPart is a small KDE KPart component to display
Markdown files in Kate and in any other KDE application which uses
the KPart system.



markdownpart.tgz
Description: application/tar-gz


UPDATE: net/snowflake_proxy 2.4.2

2023-01-15 Thread Caspar Schutijser
Hi,

Below is a diff that updates Snowflake to 2.4.2. The proxy is working
fine on amd64. Unless anyone objects, I'd like to take MAINTAINER.

Comments or OKs?

Caspar


Index: Makefile
===
RCS file: /cvs/ports/net/snowflake_proxy/Makefile,v
retrieving revision 1.9
diff -u -p -r1.9 Makefile
--- Makefile23 Dec 2022 13:30:50 -  1.9
+++ Makefile15 Jan 2023 12:53:23 -
@@ -1,7 +1,7 @@
 COMMENT=   anti-censorship proxy and pluggable transports for Tor
 
 MODGO_MODNAME= git.torproject.org/pluggable-transports/snowflake.git/v2
-V= 2.4.1
+V= 2.4.2
 MODGO_VERSION= v$V
 
 DISTNAME=  snowflake.git-${MODGO_VERSION}
@@ -10,6 +10,8 @@ PKGNAME=  snowflake_proxy-$V
 CATEGORIES=net
 
 HOMEPAGE=  https://snowflake.torproject.org/
+
+MAINTAINER=Caspar Schutijser 
 
 # BSD
 PERMIT_PACKAGE= Yes
Index: distinfo
===
RCS file: /cvs/ports/net/snowflake_proxy/distinfo,v
retrieving revision 1.3
diff -u -p -r1.3 distinfo
--- distinfo23 Dec 2022 13:30:50 -  1.3
+++ distinfo15 Jan 2023 12:53:23 -
@@ -742,7 +742,7 @@ SHA256 (go_modules/sigs.k8s.io/yaml/@v/v
 SHA256 (go_modules/sigs.k8s.io/yaml/@v/v1.1.0.zip) = 
oNOSUuhmWkKKjLnU38nL6ge3rpCuYufPNlG+cZrfUVo=
 SHA256 
(go_modules/sourcegraph.com/sourcegraph/appdash/@v/v0.0.0-20190731080439-ebfcffb1b5c0.mod)
 = W6+HkS6bnGFVJJiJDke0WyjQPHOLYw7fbXxwxlsKxGI=
 SHA256 
(go_modules/sourcegraph.com/sourcegraph/appdash/@v/v0.0.0-20190731080439-ebfcffb1b5c0.zip)
 = vSSS2dsFNiwv7NCz0PYALImm2Q1nj7k7QVgpiriDc28=
-SHA256 (snowflake.git-v2.4.1.zip) = 
aQLNvuWUOIPBCn0/HPyeyb7naXPlP6KjhsIefc6+uIE=
+SHA256 (snowflake.git-v2.4.2.zip) = 
j1CO2NKbP8JAHLclnFoiJXPDOph+nToE9V9i9OfQ1ec=
 SIZE (go_modules/cloud.google.com/go/@v/v0.26.0.mod) = 27
 SIZE (go_modules/cloud.google.com/go/@v/v0.34.0.mod) = 27
 SIZE (go_modules/cloud.google.com/go/@v/v0.34.0.zip) = 2792177
@@ -1487,4 +1487,4 @@ SIZE (go_modules/sigs.k8s.io/yaml/@v/v1.
 SIZE (go_modules/sigs.k8s.io/yaml/@v/v1.1.0.zip) = 18120
 SIZE 
(go_modules/sourcegraph.com/sourcegraph/appdash/@v/v0.0.0-20190731080439-ebfcffb1b5c0.mod)
 = 43
 SIZE 
(go_modules/sourcegraph.com/sourcegraph/appdash/@v/v0.0.0-20190731080439-ebfcffb1b5c0.zip)
 = 158069
-SIZE (snowflake.git-v2.4.1.zip) = 212881
+SIZE (snowflake.git-v2.4.2.zip) = 216097



Re: Tor Browser: why is there no built-in bridges?

2023-01-15 Thread Caspar Schutijser
On Fri, Dec 23, 2022 at 07:12:46PM +0100, Caspar Schutijser wrote:
> On Wed, Dec 21, 2022 at 06:29:11PM +0100, Caspar Schutijser wrote:
> > On Wed, Dec 21, 2022 at 06:11:43AM +, Yifei Zhan wrote:
> > > On 22/12/16 06:22PM, Caspar Schutijser wrote:
> > > > Dear users in this thread, if possible, can you give this a spin?
> > > > 
> > > > With some help and feedback from the Tor Browser developers I
> > > > came up with the following diff. I verified that I can use
> > > > the meek-azure and obfs4 Pluggable Transports. With a
> > > > local (uncommitted) snowflake_client port Snowflake also worked but
> > > > I'll get back to that some other time.
> > > > 
> > > 
> > > This works exactly as it should :)
> > > I tested meek/obfs/snowflake and all three worked without issue.
> > > 
> > > It seems like TBB changed the way bridges integrate since I last attempt 
> > > to get 
> > > this working on OpenBSD, so my old patchset is no longer applicable, I'm 
> > > happy 
> > > to help testing tho.
> > 
> > Okay, great to hear! Thanks for testing.
> > 
> > Here is a diff for -current that I do intend to commit.
> > 
> > Comments or OKs?
> 
> And here is an updated and slightly tweaked diff since we now ship
> snowflake_client. This requires a recent commit by me to
> net/snowflake_proxy.
> 
> Comments or OKs?

Ping.

> 
> Caspar
> 
> 
> 
> Tor Browser: out of the box support for some Pluggable Transports
> 
> Provide default bridges for the meek-azure, obfs4 and snowflake
> Pluggable Transports and put the necessary bits in torrc-defaults
> so those Pluggable Transports work out of the box.
> 
> 
> 
> Index: meta/tor-browser/Makefile
> ===
> RCS file: /cvs/ports/meta/tor-browser/Makefile,v
> retrieving revision 1.65
> diff -u -p -r1.65 Makefile
> --- meta/tor-browser/Makefile 18 Dec 2022 15:55:09 -  1.65
> +++ meta/tor-browser/Makefile 23 Dec 2022 18:11:16 -
> @@ -4,6 +4,7 @@ MAINTAINER=   Caspar Schutijser   
>  PKGNAME= tor-browser-12.0.1
>  ONLY_FOR_ARCHS = amd64
> +REVISION=0
>  
>  RUN_DEPENDS= www/tor-browser/browser>=12.0.1 \
>   www/tor-browser/noscript>=11.4.13 \
> Index: meta/tor-browser/pkg/README
> ===
> RCS file: /cvs/ports/meta/tor-browser/pkg/README,v
> retrieving revision 1.9
> diff -u -p -r1.9 README
> --- meta/tor-browser/pkg/README   9 Mar 2022 20:48:33 -   1.9
> +++ meta/tor-browser/pkg/README   23 Dec 2022 18:11:16 -
> @@ -33,11 +33,9 @@ editing your torrc yourself.  Make sure 
>  before doing so if you use this method; if Tor Browser is running it
>  might overwrite your torrc.
>  
> -NOTE: The OpenBSD Tor Browser ports do not yet include Pluggable
> -Transports (PT).  This means that not all features are yet available,
> -such as using obfsproxy to get to Tor.  A future update will include
> -ports for PT components.  Pluggable Transports have a web page
> -worth reading:
> +NOTE: on OpenBSD, the only Pluggable Transports that are available
> +for now are meek-azure, obfs4 and snowflake.  Pluggable Transports have
> +a web page worth reading:
>https://2019.www.torproject.org/docs/pluggable-transports.html.en
>  
>  For more information about Tor Browser and the Tor anonymity network
> Index: www/tor-browser/browser/Makefile
> ===
> RCS file: /cvs/ports/www/tor-browser/browser/Makefile,v
> retrieving revision 1.99
> diff -u -p -r1.99 Makefile
> --- www/tor-browser/browser/Makefile  18 Dec 2022 15:55:09 -  1.99
> +++ www/tor-browser/browser/Makefile  23 Dec 2022 18:11:16 -
> @@ -13,10 +13,12 @@ PATCHORIG =   .pat.orig
>  
>  PKGNAME =${TB_PREFIX}-browser-${TB_VERSION:S/a/alpha/}
>  DISTNAME =   src-firefox-tor-browser-102.6.0esr-12.0-1-build2
> +REVISION =   0
>  
>  FIX_EXTRACT_PERMISSIONS  = Yes
>  DISTFILES += ${DISTNAME}.tar.xz \
> - tor-browser-linux64-${TB_VERSION}_ALL.tar.xz
> + tor-browser-linux64-${TB_VERSION}_ALL.tar.xz \
> + tor-expert-bundle-${TB_VERSION}-linux-x86_64.tar.gz
>  
>  SO_VERSION = 8.0
>  MOZILLA_LIBS =   xul clearkey lgpllibs mozavcodec mozavutil 
> mozgtk
> @@ -74,7 +76,9 @@ MAKE_ENV += BUILD_OPT=1 \
>   NSS_ENABLE_ECC=1 \
>   XCFLAGS="-I${LOCALBASE}/include ${CFLAGS}"
>  
> -RUN_DEPENDS +=   net/tor>=0.4.7.12
> +RUN_DEPENDS +=   net/obfs4proxy>=0.0.14 \
> + net/snowflake_proxy>=2.4.1 \
> + net/tor>=0.4.7.12
>  
>  CONFIGURE_ARGS +=--enable-release #1386371
>  CONFIGURE_ARGS +=--enable-sandbox
> @@ -103,7 +107,16 @@ post-patch:
>   # Not using a patch for this; patch context would contain UTF-8
>   sed -i 's/#ifdef XP_LINUX/#if defined(XP_LINUX)

Re: [NEW] audio/alsa-lib-1.2.8

2023-01-15 Thread SASANO Takayoshi
Hi,

> They do not, files would go in /usr/local/include/alsa-lib/alsa/xxx,
> add -I/usr/local/include/alsa-lib to CPPFLAGS (or CFLAGS if the build
> system doesn't cope with CPPFLAGS).
>
> Similar with LDFLAGS for libraries (and setting rpath may be needed
> too).

like inotify,

/usr/local/include/alsa-lib/(alsa/xxx) and
/usr/local/lib/alsa-lib/(xxx) ?

-- 
SASANO Takayoshi (JG1UAA) 



Re: [new] meta/jitsi-1.0 - meta port for jitsi and friends

2023-01-15 Thread Klemens Nanni
14.01.2023 16:20, Philipp Buehler пишет:
> Unsure if this Error 1 is part of the usual game:

It is.

> 
> itsi# env FETCH_PACKAGES= make package

You tell it to look for a prebuilt package to avoid building it...

> ===>  Looking for jitsi-1.0.tgz in $PKG_PATH -
> file:/usr/ports/packages/amd64/cache/: empty
> file:/usr/ports/packages/amd64/all/: empty
> file:/usr/ports/packages/amd64/no-arch/: empty
> quirks-6.94 signed on 2023-01-13T18:41:27Z
> Can't find jitsi-1.0.tgz
> Couldn't install jitsi-1.0
> not found

... which wasn't found...

> *** Error 1 in . (/usr/ports/infrastructure/mk/bsd.port.mk:2129
> '/usr/ports/packages/amd64/cache/jitsi-1.0.tgz': @if /usr/bin/env -i
> PKG_TMP...)
> ===>  Faking installation for jitsi-1.0

so it falls back to building it as usual.



Re: Python access to Berkeley DB

2023-01-15 Thread Roger Marsh
On Fri, 23 Dec 2022 23:46:33 -0500 (EST)
Stuart Cassoff <3...@bell.net> wrote:

> Heh. Small correction: Stub-enabled extensions can be built in 8.5 and 
> loaded into 8.6 no problem.
> 
> Looks like preloading libtcl works.
> $ LD_PRELOAD=/usr/local/lib/libtcl86.so.1.13  python3.9
> >>> import tkinter
> >>> tcl = tkinter.Tk(useTk=False)
> >>> tcl.eval('load /usr/local/lib/libdb_tcl.so.6.0');  
> ''
> 
> The port doesn't install a pkgIndex.tcl file, so [package require] won't 
> work,
> and you really want to simply [package require] things.
> 
> Here is a patch (also attached in case of mail mangling) that 
> stub-enables both v3 and v4,
> creates and installs pkgIndex.tcl files, and is a tad less noisy.  The 
> v4 test results look good.
> 
> The main package needs a REVISION bump?
> 
> This looks like a really old version of bdb.
> 
> 
> Stu
> 
> 
> With both installed:
> $ for t in 5 6; do for d in '' 4.6 1.0; do echo "puts [package provide 
> Tcl]\\\t[package require Db_tcl $d]\\\t$d" | tclsh8.$t; done; done
> 8.5.19  4.6
> 8.5.19  4.6 4.6
> 8.5.19  1.0 1.0
> 8.6.13  4.6
> 8.6.13  4.6 4.6
> 8.6.13  1.0 1.0
> 
> $ python3.9
> >>> import tkinter
> >>> tcl = tkinter.Tk(useTk=False)
> >>> tcl.eval('package require Db_tcl')  
> '4.6'
> 
> $ python3.9
> >>> import tkinter
> >>> tcl = tkinter.Tk(useTk=False)
> >>> tcl.eval('package require Db_tcl 4.6')  
> '4.6'
> 
> $ python3.9
> >>> import tkinter
> >>> tcl = tkinter.Tk(useTk=False)
> >>> tcl.eval('package require Db_tcl 1.0')  
> '1.0'
> 
> 
snip patches etc.

I now have version of application that works via Tcl API on 7.2 by:

LD_PRELOAD=/usr/local/lib/libtcl86.so.1.13  python3.9 -m ...

the job complains it's only got libtcl86.so.1.12 but uses it successfully 
anyway.

On another box db v4 was built from ports (7.2 not snapshot) with the patches 
applied.

python3.9 -m ... works fine with no warnings about libtcl86.so version.

Neither bsddb3 nor berkeleydb installed from PyPi, and py3-bsddb3 OpenBSD 
package not installed either.

Thanks for all that stuff.

Will the db patches be applied by 7.3 release time?



net/qbittorrent: update to 4.4.5

2023-01-15 Thread Klemens Nanni
https://github.com/qbittorrent/qBittorrent/compare/release-4.4.3.1...release-4.4.5

No WANTLIB or PLIST change.
Works for me on amd64.

OK?

Index: Makefile.inc
===
RCS file: /cvs/ports/net/qbittorrent/Makefile.inc,v
retrieving revision 1.23
diff -u -p -r1.23 Makefile.inc
--- Makefile.inc15 Jan 2023 11:07:12 -  1.23
+++ Makefile.inc15 Jan 2023 11:10:41 -
@@ -1,7 +1,7 @@
 # qmake picks up gcrypt.h even though it's unused
 DPB_PROPERTIES =   nojunk
 
-VER =  4.4.3.1
+VER =  4.4.5
 DISTNAME = qbittorrent-${VER}
 
 DIST_SUBDIR =  qbittorrent
Index: qbittorrent/Makefile
===
RCS file: /cvs/ports/net/qbittorrent/qbittorrent/Makefile,v
retrieving revision 1.21
diff -u -p -r1.21 Makefile
--- qbittorrent/Makefile15 Jan 2023 11:07:12 -  1.21
+++ qbittorrent/Makefile15 Jan 2023 11:10:41 -
@@ -1,5 +1,4 @@
 COMMENT =  BitTorrent client with Qt interface
-REVISION = 2
 
 WANTLIB += ${COMPILER_LIBCXX} Qt5Core Qt5DBus Qt5Gui Qt5Network
 WANTLIB += Qt5Sql Qt5Widgets Qt5Xml boost_system-mt c crypto
Index: qbittorrent/distinfo
===
RCS file: /cvs/ports/net/qbittorrent/qbittorrent/distinfo,v
retrieving revision 1.18
diff -u -p -r1.18 distinfo
--- qbittorrent/distinfo7 Aug 2022 09:29:21 -   1.18
+++ qbittorrent/distinfo15 Jan 2023 11:10:41 -
@@ -1,2 +1,2 @@
-SHA256 (qbittorrent/qbittorrent-4.4.3.1.tar.gz) = 
BPnsiZGIxZ7FGhL8uJGtt3VoJjloa1cWN26Sqsh/mHE=
-SIZE (qbittorrent/qbittorrent-4.4.3.1.tar.gz) = 7624808
+SHA256 (qbittorrent/qbittorrent-4.4.5.tar.gz) = 
A1ob0PvLRlDT/N2lC7OBjtxdMvqivXwjfvu2wfeHDNY=
+SIZE (qbittorrent/qbittorrent-4.4.5.tar.gz) = 7626416
Index: qbittorrent-nox/Makefile
===
RCS file: /cvs/ports/net/qbittorrent/qbittorrent-nox/Makefile,v
retrieving revision 1.12
diff -u -p -r1.12 Makefile
--- qbittorrent-nox/Makefile15 Jan 2023 11:07:12 -  1.12
+++ qbittorrent-nox/Makefile15 Jan 2023 11:10:41 -
@@ -1,6 +1,5 @@
 COMMENT =  BitTorrent client with web interface
 PKGNAME =  qbittorrent-nox-${VER}
-REVISION = 1
 
 WANTLIB += ${COMPILER_LIBCXX} Qt5Core Qt5Network Qt5Sql Qt5Xml
 WANTLIB += boost_system-mt c crypto execinfo m ssl torrent-rasterbar
Index: qbittorrent-nox/distinfo
===
RCS file: /cvs/ports/net/qbittorrent/qbittorrent-nox/distinfo,v
retrieving revision 1.18
diff -u -p -r1.18 distinfo
--- qbittorrent-nox/distinfo7 Aug 2022 09:29:21 -   1.18
+++ qbittorrent-nox/distinfo15 Jan 2023 11:10:41 -
@@ -1,2 +1,2 @@
-SHA256 (qbittorrent/qbittorrent-4.4.3.1.tar.gz) = 
BPnsiZGIxZ7FGhL8uJGtt3VoJjloa1cWN26Sqsh/mHE=
-SIZE (qbittorrent/qbittorrent-4.4.3.1.tar.gz) = 7624808
+SHA256 (qbittorrent/qbittorrent-4.4.5.tar.gz) = 
A1ob0PvLRlDT/N2lC7OBjtxdMvqivXwjfvu2wfeHDNY=
+SIZE (qbittorrent/qbittorrent-4.4.5.tar.gz) = 7626416



Re: [UPDATE] net/rabbitmq 3.10.13

2023-01-15 Thread Volker Schlecht



On 1/14/23 15:02, Stuart Henderson wrote:


please leave the tabs as they were
how about this for rabbitmq.rc?
(btw, this part would have been more obvious sent as a separate diff
rather than stacked with an update)


As usual: Thanks for the help - updated diff is attached!Index: Makefile
===
RCS file: /cvs/ports/net/rabbitmq/Makefile,v
retrieving revision 1.48
diff -u -p -r1.48 Makefile
--- Makefile	13 Nov 2022 15:28:53 -	1.48
+++ Makefile	15 Jan 2023 11:00:59 -
@@ -1,10 +1,9 @@
 COMMENT =	highly reliable Enterprise Messaging System
 
-V =		3.10.7
+V =		3.10.13
 DISTNAME =	rabbitmq-server-$V
 PKGNAME =	rabbitmq-$V
 CATEGORIES =	net
-REVISION =	1
 
 HOMEPAGE =	https://www.rabbitmq.com/
 
@@ -49,6 +48,40 @@ NO_TEST =	Yes
 
 ALL_TARGET =	all manpages
 INSTALL_TARGET = install install-bin
+
+PLUGIN_VERSIONS= \
+ACCEPT_VSN	0.3.5 \
+ATEN_VSN	0.5.8 \
+BASE64URL_VSN	1.0.1 \
+COWBOY_VSN	2.8.0 \
+COWLIB_VSN	2.9.1 \
+CREDENTIALS_OBFUSCATION_VSN	3.2.0 \
+CUTTLEFISH_VSN	3.1.0 \
+EETCD_VSN	0.3.6 \
+ENOUGH_VSN	0.1.0 \
+GEN_BATCH_SERVER_VSN	0.8.8 \
+GETOPT_VSN	1.0.2 \
+GUN_VSN		1.3.3 \
+JOSE_VSN	1.11.1 \
+JSX_VSN		3.1.0 \
+OBSERVER_CLI_VSN	1.7.3 \
+OSIRIS_VSN	1.3.3 \
+PROMETHEUS_VSN	4.9.1 \
+QUANTILE_ESTIMATOR_VSN	0.2.1 \
+RA_VSN		2.4.5 \
+RANCH_VSN	2.1.0 \
+RECON_VSN	2.5.2 \
+SESHAT_VSN	0.4.0 \
+STDOUT_FORMATTER_VSN	0.2.4 \
+SYSLOG_VSN	4.0.0 \
+SYSMON_HANDLER_VSN	1.3.0 \
+SYSTEMD_VSN	0.6.1
+
+.for _n _v in ${PLUGIN_VERSIONS}
+${_n} =		${_v}
+RABBIT_${_n:S/_VSN//} = ${_n:S/_VSN//:L}-${_v}
+SUBST_VARS +=	RABBIT_${_n:S/_VSN//}
+.endfor
 
 pre-configure:
 	${SUBST_CMD} ${WRKSRC}/deps/rabbit/scripts/rabbitmq-{server,env}
Index: distinfo
===
RCS file: /cvs/ports/net/rabbitmq/distinfo,v
retrieving revision 1.12
diff -u -p -r1.12 distinfo
--- distinfo	3 Sep 2022 14:02:22 -	1.12
+++ distinfo	15 Jan 2023 11:00:59 -
@@ -1,2 +1,2 @@
-SHA256 (rabbitmq-server-3.10.7.tar.xz) = tV4wWEGH8ZZQUFPbH+kGAerHyQY0Ff/4DbBsJH1pLrU=
-SIZE (rabbitmq-server-3.10.7.tar.xz) = 3579880
+SHA256 (rabbitmq-server-3.10.13.tar.xz) = 2YEOXVVSyRD8R92kg2t7QqcLd1HMRmm0IE1Xd4PD87A=
+SIZE (rabbitmq-server-3.10.13.tar.xz) = 3648572
Index: patches/patch-deps_rabbit_scripts_rabbitmq-defaults
===
RCS file: patches/patch-deps_rabbit_scripts_rabbitmq-defaults
diff -N patches/patch-deps_rabbit_scripts_rabbitmq-defaults
--- /dev/null	1 Jan 1970 00:00:00 -
+++ patches/patch-deps_rabbit_scripts_rabbitmq-defaults	15 Jan 2023 11:00:59 -
@@ -0,0 +1,15 @@
+Index: deps/rabbit/scripts/rabbitmq-defaults
+--- deps/rabbit/scripts/rabbitmq-defaults.orig
 deps/rabbit/scripts/rabbitmq-defaults
+@@ -9,6 +9,11 @@
+ ### next line potentially updated in package install steps
+ SYS_PREFIX=
+ 
++export RABBITMQ_MNESIA_BASE=/var/rabbitmq/mnesia
++export RABBITMQ_CONF_ENV_FILE=/etc/rabbitmq/rabbitmq-env.conf
++# ensure VM and Elixir scripts are running under the same locale
++export LANG=en_US.UTF-8
++
+ CLEAN_BOOT_FILE=start_clean
+ SASL_BOOT_FILE=start_sasl
+ BOOT_MODULE="rabbit"
Index: patches/patch-deps_rabbit_scripts_rabbitmq-env
===
RCS file: /cvs/ports/net/rabbitmq/patches/patch-deps_rabbit_scripts_rabbitmq-env,v
retrieving revision 1.3
diff -u -p -r1.3 patch-deps_rabbit_scripts_rabbitmq-env
--- patches/patch-deps_rabbit_scripts_rabbitmq-env	31 Jul 2022 12:20:42 -	1.3
+++ patches/patch-deps_rabbit_scripts_rabbitmq-env	15 Jan 2023 11:00:59 -
@@ -1,7 +1,7 @@
 Index: deps/rabbit/scripts/rabbitmq-env
 --- deps/rabbit/scripts/rabbitmq-env.orig
 +++ deps/rabbit/scripts/rabbitmq-env
-@@ -177,7 +177,7 @@ run_escript()
+@@ -188,7 +188,7 @@ run_escript()
  # Important: do not quote RABBITMQ_CTL_ERL_ARGS as they must be
  # word-split
  # shellcheck disable=SC2086
Index: patches/patch-deps_rabbit_scripts_rabbitmq-server
===
RCS file: /cvs/ports/net/rabbitmq/patches/patch-deps_rabbit_scripts_rabbitmq-server,v
retrieving revision 1.3
diff -u -p -r1.3 patch-deps_rabbit_scripts_rabbitmq-server
--- patches/patch-deps_rabbit_scripts_rabbitmq-server	31 Jul 2022 12:20:42 -	1.3
+++ patches/patch-deps_rabbit_scripts_rabbitmq-server	15 Jan 2023 11:00:59 -
@@ -1,7 +1,7 @@
 Index: deps/rabbit/scripts/rabbitmq-server
 --- deps/rabbit/scripts/rabbitmq-server.orig
 +++ deps/rabbit/scripts/rabbitmq-server
-@@ -70,7 +70,7 @@ start_rabbitmq_server() {
+@@ -65,7 +65,7 @@ start_rabbitmq_server() {
  
  check_start_params
  
Index: patches/patch-deps_rabbitmq_cli_mix_exs
===
RCS file: patches/patch-deps_rabbitmq_cli_mix_exs
diff -N patches/patch-deps_rabbitmq_cli_mix_exs
--- patches/patch-deps_rabbitmq_cli_mix_exs	3 Sep 2022 14:02:22 -	1.4
+++ /dev/null	1 Jan 1970 00:00:00 -

Re: audio/snack: drop python 2 bindings

2023-01-15 Thread Klemens Nanni
12.12.2022 03:04, Daniel Dickman пишет:
> On Sun, 11 Dec 2022, Klemens Nanni wrote:
> 
>> On Sat, Dec 03, 2022 at 10:15:16PM +, Klemens Nanni wrote:
>>> On Sat, Dec 03, 2022 at 08:12:59PM +, Klemens Nanni wrote:
 No upstream activity in years, I don't see py3 bits anywhere, so I
 suggest we retire bindings for the EOL python 2.

 Merge -main and -python into a single audio/snack package.
 Tested with
# pkg_add py-snack
$ make package
$ cp /usr/ports/packages/amd64/ftp/snack-2.2.10p7.tgz . 
$ doas env TRUSTED_PKG_PATH=. pkg_add -u
py-snack-2.2.10p2+snack-2.2.10p6->snack-2.2.10p7: ok
Read shared items: ok

 This gets rid of the last lang/python/2.7,-tkinter consumer, which could
 be removed next.

 Feedback? Objection? OK?
>>>
>>> Now with cvs add'ed files.
>>
>> No feedback so far.
>>
>> Simpler diff leaving the MULTI_PACKAGES -main bits behind, then -python
>> can be removed with a quirk.
>>
>> OK?
>>
> 
> First of all, I think we may want the fix for CVE-2012-6303:
> 
> https://gitweb.gentoo.org/repo/gentoo.git/tree/dev-tcltk/snack/files/snack-2.2.10-CVE-2012-6303-fix.patch
> 
> As for python3, perhaps we can use gentoo's diff for this?
> 
> https://gitweb.gentoo.org/repo/gentoo.git/tree/dev-tcltk/snack/files/tcl-snack-2.2.10-python3.patch

Noone spoke up... anyone interested enough in patching and testing this?
Otherwise we might as well plug the CVE and just drop python 2 bindings.



Re: [NEW] audio/alsa-lib-1.2.8

2023-01-15 Thread Stuart Henderson
On 2023/01/15 10:22, SASANO Takayoshi wrote:
> Hi,
> 
> > Let's keep it simple like:
> > /usr/local/lib/alsa-lib/...
> > /usr/local/include/alsa-lib/...
> 
> Really? I thought:
> 
> /usr/local/alsa-lib/include
> /usr/local/alsa-lib/lib
> 
> (how about /usr/local/linux-alsa/{include,lib}?)
> 
> Both are not difficult to write alsa-lib's Makefile
> but very hard to porting apps to /usr/local/lib/alsa-lib and
> /usr/local/include/alsa-lib.
> 
> In alsa-utils, about 50 or more files are needed to be patched
> if header files are stored into /usr/local/include/alsa-lib .

They do not, files would go in /usr/local/include/alsa-lib/alsa/xxx,
add -I/usr/local/include/alsa-lib to CPPFLAGS (or CFLAGS if the build
system doesn't cope with CPPFLAGS).

Similar with LDFLAGS for libraries (and setting rpath may be needed
too).

Though porting to sndio is still *much* preferred.



Re: libgcrypt: arm64 assembly fixes

2023-01-15 Thread Stuart Henderson
On 2023/01/14 22:04, Mark Kettenis wrote:
> > Date: Sat, 14 Jan 2023 21:08:38 +0100
> > From: Theo Buehler 
> > 
> > This moves constants from .text into .rodata.
> > 
> > All tests pass, gnupg tests work, gpgme and gcr build.
> 
> Right, and then the idiots did this:
> 
> https://git.gnupg.org/cgi-bin/gitweb.cgi?p=libgcrypt.git;a=commit;h=fd02e8e78470deb661269c429f3348f811c054c6
> 
> so future versions will need furher patching.  At least they used a
> macro, so it is relatively easy to revert.

I tried the newer branch before --no-execute-only went in, it doesn't
build as-is so needs further patching anyway.



Re: UPDATE net/luasocket 3.0rc1p1 -> 3.1.0

2023-01-15 Thread Omar Polo
On 2023/01/15 09:39:11 +0100, Robert Nagy  wrote:
> On 14/01/23 14:39 -0700, Ashlen wrote:
> > On 23/01/07 00:20, Ashlen wrote:
> > > As for the renaming thing, I realized I didn't actually provide any links
> > > showing why I kept this in. I looked at the commits and it appears their
> > > rationale is that anyone that writes a Lua script and imports luasocket 
> > > as well
> > > as another module that happens to have an identical buffer_* will have a
> > > headache due to name collisions. Though if that's the case, it makes me 
> > > wonder
> > > why FreeBSD backed out the patch in the commit op@ mentioned.
> > > 
> > > https://cvsweb.openbsd.org/ports/net/luasocket/patches/patch-src_buffer_c?rev=1.2&content-type=text/x-cvsweb-markup
> > > https://marc.info/?l=freebsd-ports-bugs&m=125089202109336&w=2
> > > https://marc.info/?l=freebsd-ports&m=125097467421558&w=2
> > 
> > Hey Robert, I CC'ed you because I need to ask you something. You were 
> > originally
> > the person who made patches renaming 'buffer_*' to 'ls_buffer_*' in
> > net/luasocket due to them creating a namespace clash with other ports. I 
> > know
> > this was all the way back in 2009, but can you let me know if changing 
> > those is
> > still necessary? I'm guessing the answer is yes, but I wanted to double 
> > check to
> > make sure since there was some discussion about it earlier.
> > 
> > I meant to test it myself and therefore avoid bothering you, but it's been a
> > week and I'm realizing I'm not going to get to it in a timely manner (I 
> > don't
> > know how to write in Lua yet). 
> > 
> > (Side note for the other people in the thread: testing against those two 
> > other
> > ports is on my TODO list. Life has just been crazy lately and it's been a
> > struggle to get organized again... sorry for the delay on that)
> 
> I haven't used this for a long time using that module, but it might not be
> the case anymore. It has to be tested I guess,

I haven't noticed before, sorry, but this shouldn't cause issues
anymore.  luasocket doesn't export the buffer_* symbols:

% nm /usr/local/lib/lua/5.1/{mime,socket}/*so | grep buffer
 U luaL_prepbuffer
 F buffer.c
77a0 t buffer_init
80c0 t buffer_isempty
77f0 t buffer_meth_getstats
7bc0 t buffer_meth_receive
7980 t buffer_meth_send
7890 t buffer_meth_setstats
7770 t buffer_open
 U luaL_prepbuffer
 F buffer.c
47d0 t buffer_init
50f0 t buffer_isempty
4820 t buffer_meth_getstats
4bf0 t buffer_meth_receive
49b0 t buffer_meth_send
48c0 t buffer_meth_setstats
47a0 t buffer_open
 U luaL_prepbuffer
 F buffer.c
5650 t buffer_init
5f70 t buffer_isempty
56a0 t buffer_meth_getstats
5a70 t buffer_meth_receive
5830 t buffer_meth_send
5740 t buffer_meth_setstats
5620 t buffer_open
 U luaL_prepbuffer

(this is luasocket built with patch below)

The lowercase 't' should mean those symbols are private, right?  if
so, I think we can go on with the update.  I'm reattaching Ashlen'
patch without the sed to rename the symbols and with my previous
tweaks included.

ok?

Index: Makefile
===
RCS file: /home/cvs/ports/net/luasocket/Makefile,v
retrieving revision 1.37
diff -u -p -r1.37 Makefile
--- Makefile11 Mar 2022 19:46:18 -  1.37
+++ Makefile9 Jan 2023 09:46:07 -
@@ -1,49 +1,42 @@
 COMMENT=   network support for the lua language
-V= 3.0-rc1
-GH_ACCOUNT=diegonehab
+
+V= 3.1.0
+GH_ACCOUNT=lunarmodules
 GH_PROJECT=luasocket
 GH_TAGNAME=v$V
-REVISION=  1
-PKGNAME=   ${DISTNAME:S/-rc/rc/}
+
 CATEGORIES=net
 
-HOMEPAGE=  http://w3.impa.br/~diego/software/luasocket/
+HOMEPAGE=  https://lunarmodules.github.io/luasocket/index.html
 
 # MIT
 PERMIT_PACKAGE=Yes
 
 MODULES=   lang/lua
 
-FLAVORS=   lua52 lua53
+FLAVORS=   lua52 lua53 lua54
 FLAVOR?=
 
-NO_TEST=   Yes
-
-USE_GMAKE= Yes
-
 MAKE_FILE= makefile
 
+CFLAGS+=   -fPIC -DPIC -I${MODLUA_INCL_DIR}
+CFLAGS+=   -DUNIX_HAS_SUN_LEN -DLUA_COMPAT_APIINTCASTS
 MAKE_FLAGS=CC_linux=${CC} \
LD_linux=${CC} \
-   CFLAGS_linux="${CFLAGS} -I${MODLUA_INCL_DIR} -fPIC \
- -DPIC -DUNIX_HAS_SUN_LEN \
- -DLUA_COMPAT_APIINTCASTS" \
-   LDFLAGS_linux="${LDFLAGS} -shared -fPIC -o "
-
-do-install:
-   ${INSTALL_DATA_DIR} ${MODLUA_DATADIR}/socket ${MODLUA_DATADIR}/mime
-   ${INSTALL_DATA_DIR} ${MODLUA_LIBDIR}/socket ${MODLUA_LIBDIR}/mime
+   CFLAGS_linux="${CFLAGS}" \
+   LDFLAGS_linux="${LDFLAGS} -shared -fPIC -o

Re: [NEW] audio/alsa-lib-1.2.8

2023-01-15 Thread Antoine Jacoutot
On Sun, Jan 15, 2023 at 10:22:17AM +0900, SASANO Takayoshi wrote:
> Hi,
> 
> > Let's keep it simple like:
> > /usr/local/lib/alsa-lib/...
> > /usr/local/include/alsa-lib/...
> 
> Really? I thought:
> 
> /usr/local/alsa-lib/include
> /usr/local/alsa-lib/lib

Sure this is fine as well :-)

> (how about /usr/local/linux-alsa/{include,lib}?)
> 
> Both are not difficult to write alsa-lib's Makefile
> but very hard to porting apps to /usr/local/lib/alsa-lib and
> /usr/local/include/alsa-lib.
> 
> In alsa-utils, about 50 or more files are needed to be patched
> if header files are stored into /usr/local/include/alsa-lib .
> 
> I think this is too much, but simply do write a patch that
> it is still neccesary...
> -- 
> SASANO Takayoshi (JG1UAA) 
> 

-- 
Antoine



Re: libgcrypt: arm64 assembly fixes

2023-01-15 Thread Antoine Jacoutot
On Sat, Jan 14, 2023 at 09:08:38PM +0100, Theo Buehler wrote:
> This moves constants from .text into .rodata.
> 
> All tests pass, gnupg tests work, gpgme and gcr build.

OK

> 
> Index: Makefile
> ===
> RCS file: /cvs/ports/security/libgcrypt/Makefile,v
> retrieving revision 1.81
> diff -u -p -r1.81 Makefile
> --- Makefile  9 Jan 2023 17:27:49 -   1.81
> +++ Makefile  14 Jan 2023 19:53:18 -
> @@ -1,7 +1,7 @@
>  COMMENT= crypto library based on code used in GnuPG
>  
>  DISTNAME=libgcrypt-1.10.1
> -REVISION=1
> +REVISION=2
>  CATEGORIES=  security
>  
>  SHARED_LIBS +=  gcrypt   21.0 # 24.1
> @@ -23,7 +23,9 @@ CONFIGURE_STYLE=gnu
>  CONFIGURE_ARGS=  --enable-static \
>   --disable-drng-support
>  
> +.if ${MACHINE_ARCH} != aarch64
>  USE_NOEXECONLY=  Yes
> +.endif
>  
>  DEBUG_PACKAGES=  ${BUILD_PACKAGES}
>  
> Index: patches/patch-cipher_camellia-aarch64_S
> ===
> RCS file: patches/patch-cipher_camellia-aarch64_S
> diff -N patches/patch-cipher_camellia-aarch64_S
> --- /dev/null 1 Jan 1970 00:00:00 -
> +++ patches/patch-cipher_camellia-aarch64_S   14 Jan 2023 19:44:18 -
> @@ -0,0 +1,11 @@
> +Index: cipher/camellia-aarch64.S
> +--- cipher/camellia-aarch64.S.orig
>  cipher/camellia-aarch64.S
> +@@ -313,6 +313,7 @@ _gcry_camellia_arm_decrypt_block:
> + .ltorg
> + ELF(.size 
> _gcry_camellia_arm_decrypt_block,.-_gcry_camellia_arm_decrypt_block;)
> + 
> ++.rodata
> + /* Encryption/Decryption tables */
> + ELF(.type  _gcry_camellia_arm_tables,@object;)
> + .balign 32
> Index: patches/patch-cipher_chacha20-aarch64_S
> ===
> RCS file: patches/patch-cipher_chacha20-aarch64_S
> diff -N patches/patch-cipher_chacha20-aarch64_S
> --- /dev/null 1 Jan 1970 00:00:00 -
> +++ patches/patch-cipher_chacha20-aarch64_S   14 Jan 2023 19:44:25 -
> @@ -0,0 +1,21 @@
> +Index: cipher/chacha20-aarch64.S
> +--- cipher/chacha20-aarch64.S.orig
>  cipher/chacha20-aarch64.S
> +@@ -36,7 +36,7 @@
> + 
> + .cpu generic+simd
> + 
> +-.text
> ++.rodata
> + 
> + #include "asm-poly1305-aarch64.h"
> + 
> +@@ -192,6 +192,8 @@ _gcry_chacha20_aarch64_blocks4_data_rot8:
> + .byte 7,4,5,6
> + .byte 11,8,9,10
> + .byte 15,12,13,14
> ++
> ++.text
> + 
> + .align 3
> + .globl _gcry_chacha20_aarch64_blocks4
> Index: patches/patch-cipher_cipher-gcm-armv8-aarch64-ce_S
> ===
> RCS file: patches/patch-cipher_cipher-gcm-armv8-aarch64-ce_S
> diff -N patches/patch-cipher_cipher-gcm-armv8-aarch64-ce_S
> --- /dev/null 1 Jan 1970 00:00:00 -
> +++ patches/patch-cipher_cipher-gcm-armv8-aarch64-ce_S14 Jan 2023 
> 19:27:48 -
> @@ -0,0 +1,21 @@
> +Index: cipher/cipher-gcm-armv8-aarch64-ce.S
> +--- cipher/cipher-gcm-armv8-aarch64-ce.S.orig
>  cipher/cipher-gcm-armv8-aarch64-ce.S
> +@@ -25,7 +25,7 @@
> + 
> + .cpu generic+simd+crypto
> + 
> +-.text
> ++.rodata
> + 
> + 
> + /* Constants */
> +@@ -170,6 +170,8 @@ gcry_gcm_reduction_constant:
> + CFI_ADJUST_CFA_OFFSET(-16); \
> + ldp d8, d9, [sp], #16; \
> + CFI_ADJUST_CFA_OFFSET(-16);
> ++
> ++.text
> + 
> + /*
> +  * unsigned int _gcry_ghash_armv8_ce_pmull (void *gcm_key, byte *result,
> Index: patches/patch-cipher_crc-armv8-aarch64-ce_S
> ===
> RCS file: patches/patch-cipher_crc-armv8-aarch64-ce_S
> diff -N patches/patch-cipher_crc-armv8-aarch64-ce_S
> --- /dev/null 1 Jan 1970 00:00:00 -
> +++ patches/patch-cipher_crc-armv8-aarch64-ce_S   14 Jan 2023 19:18:35 
> -
> @@ -0,0 +1,20 @@
> +Index: cipher/crc-armv8-aarch64-ce.S
> +--- cipher/crc-armv8-aarch64-ce.S.orig
>  cipher/crc-armv8-aarch64-ce.S
> +@@ -25,7 +25,7 @@
> + 
> + .cpu generic+simd+crypto
> + 
> +-.text
> ++.rodata
> + 
> + 
> + /* Structure of crc32_consts_s */
> +@@ -54,6 +54,7 @@
> +   .byte 0xff, 0xff, 0xff, 0xff, 0xff, 0xff, 0xff, 0xff
> +   .byte 0xff, 0xff, 0xff, 0xff, 0xff, 0xff, 0xff, 0xff
> + 
> ++.text
> + 
> + /*
> +  * void _gcry_crc32r_armv8_ce_bulk (u32 *pcrc, const byte *inbuf, size_t 
> inlen,
> Index: patches/patch-cipher_sha1-armv8-aarch64-ce_S
> ===
> RCS file: patches/patch-cipher_sha1-armv8-aarch64-ce_S
> diff -N patches/patch-cipher_sha1-armv8-aarch64-ce_S
> --- /dev/null 1 Jan 1970 00:00:00 -
> +++ patches/patch-cipher_sha1-armv8-aarch64-ce_S  14 Jan 2023 19:25:39 
> -
> @@ -0,0 +1,20 @@
> +Index: cipher/sha1-armv8-aarch64-ce.S
> +--- cipher/sha1-armv8-aarch64-ce.S.orig
>  cipher/sha1-armv8-aarch64-ce.S
> +@@ -25,7 +25,7 @@
> + 
> + .cpu generic+simd+crypto
> + 
> +-.text
> ++.rodata
> + 
> + 
> + /* Constant

Re: Opinions - Multiple versions of lang/erlang needed?

2023-01-15 Thread Antoine Jacoutot
On Sat, Jan 14, 2023 at 02:02:56PM +0100, Rafael Sadowski wrote:
> On Sat Jan 14, 2023 at 11:33:00AM +, Stuart Henderson wrote:
> > On 2023/01/14 10:52, Volker Schlecht wrote:
> > > I never tried to submit a patch for dropping something, but
> > > here's an honest attempt - of course devel/rebar needs to be
> > > dropped as well, since it depends on erlang21.
> > > 
> > > I validated the changed erlang.port.mk by rebuilding elixir,
> > > rebar3 and rabbitmq, which worked without problem.
> > > 
> > > On 1/14/23 00:03, Antoine Jacoutot wrote:
> > > > I would love to remove erlang 21. It’s in the way of the wxWidgets 
> > > > update.
> > 
> > Looks good to me, we will also need quirks/@pkgpath markers to handle
> > updates from 21 to 25 but whoever commits can do that.
> > 
> > Any objections?
> > 
> 
> +1

Absolutely no objection, on the contrary :-)

-- 
Antoine



Re: UPDATE net/luasocket 3.0rc1p1 -> 3.1.0

2023-01-15 Thread Robert Nagy
On 14/01/23 14:39 -0700, Ashlen wrote:
> On 23/01/07 00:20, Ashlen wrote:
> > As for the renaming thing, I realized I didn't actually provide any links
> > showing why I kept this in. I looked at the commits and it appears their
> > rationale is that anyone that writes a Lua script and imports luasocket as 
> > well
> > as another module that happens to have an identical buffer_* will have a
> > headache due to name collisions. Though if that's the case, it makes me 
> > wonder
> > why FreeBSD backed out the patch in the commit op@ mentioned.
> > 
> > https://cvsweb.openbsd.org/ports/net/luasocket/patches/patch-src_buffer_c?rev=1.2&content-type=text/x-cvsweb-markup
> > https://marc.info/?l=freebsd-ports-bugs&m=125089202109336&w=2
> > https://marc.info/?l=freebsd-ports&m=125097467421558&w=2
> 
> Hey Robert, I CC'ed you because I need to ask you something. You were 
> originally
> the person who made patches renaming 'buffer_*' to 'ls_buffer_*' in
> net/luasocket due to them creating a namespace clash with other ports. I know
> this was all the way back in 2009, but can you let me know if changing those 
> is
> still necessary? I'm guessing the answer is yes, but I wanted to double check 
> to
> make sure since there was some discussion about it earlier.
> 
> I meant to test it myself and therefore avoid bothering you, but it's been a
> week and I'm realizing I'm not going to get to it in a timely manner (I don't
> know how to write in Lua yet). 
> 
> (Side note for the other people in the thread: testing against those two other
> ports is on my TODO list. Life has just been crazy lately and it's been a
> struggle to get organized again... sorry for the delay on that)

I haven't used this for a long time using that module, but it might not be
the case anymore. It has to be tested I guess,



lang/gcc/11 xonly fixes

2023-01-15 Thread Peter Hessler
Same diff as what was applied to lang/gcc/8, OK?


Index: lang/gcc/11/Makefile
===
RCS file: /cvs/openbsd/ports/lang/gcc/11/Makefile,v
retrieving revision 1.16
diff -u -p -u -p -r1.16 Makefile
--- lang/gcc/11/Makefile22 Nov 2022 23:26:10 -  1.16
+++ lang/gcc/11/Makefile15 Jan 2023 08:05:53 -
@@ -13,11 +13,12 @@ ONLY_FOR_ARCHS-dlang = aarch64 amd64 arm
 
 DPB_PROPERTIES = parallel
 
+USE_NOEXECONLY = Yes
+
 V = 11.2.0
 FULL_VERSION = $V
 FULL_PKGVERSION = $V
-REVISION = 3
-REVISION-dlang = 4
+REVISION = 5
 
 ADASTRAP-amd64 = adastrap-amd64-$V-2.tar.xz
 ADASTRAP-arm = adastrap-arm-4.9.4-0.tar.xz
Index: lang/gcc/11/patches/patch-gcc_common_opt
===
RCS file: /cvs/openbsd/ports/lang/gcc/11/patches/patch-gcc_common_opt,v
retrieving revision 1.2
diff -u -p -u -p -r1.2 patch-gcc_common_opt
--- lang/gcc/11/patches/patch-gcc_common_opt11 Mar 2022 19:28:58 -  
1.2
+++ lang/gcc/11/patches/patch-gcc_common_opt14 Jan 2023 07:49:55 -
@@ -59,6 +59,15 @@ Index: gcc/common.opt
  Process #ident directives.
  
  fif-conversion
+@@ -1941,7 +1949,7 @@ Common Var(flag_ivopts) Init(1) Optimization
+ Optimize induction variables on trees.
+ 
+ fjump-tables
+-Common Var(flag_jump_tables) Init(1) Optimization
++Common Var(flag_jump_tables) Init(0) Optimization
+ Use jump tables for sufficiently large switch statements.
+ 
+ fbit-tests
 @@ -2627,7 +2635,7 @@ Common RejectNegative Joined Var(common_deferred_optio
  -fstack-limit-symbol=   Trap if the stack goes past symbol .
  



-- 
Heuristics are bug ridden by definition.  If they didn't have bugs,
then they'd be algorithms.