Upgrade lang/ghc 9.2.5->9.2.6
I rebuilt all our ports with this. Looks like a safe and useful upgrade, OK? https://www.haskell.org/ghc/blog/20230210-ghc-9.2.6-released.html >From bb3d3aef3c36d2ebb05d9bc546e80907e51e2af5 Mon Sep 17 00:00:00 2001 From: Greg Steuck Date: Sat, 11 Feb 2023 18:44:41 -0800 Subject: [PATCH] Upgrade lang/ghc 9.2.5->9.2.6 --- lang/ghc/Makefile | 7 +++ lang/ghc/distinfo | 8 lang/ghc/pkg/PLIST | 6 ++ 3 files changed, 13 insertions(+), 8 deletions(-) diff --git a/lang/ghc/Makefile b/lang/ghc/Makefile index 99cb2e85ca8..27c1ed025e9 100644 --- a/lang/ghc/Makefile +++ b/lang/ghc/Makefile @@ -11,8 +11,7 @@ NO_CCACHE = Yes # Upstream bug: https://gitlab.haskell.org/ghc/ghc/-/issues/22782 USE_NOEXECONLY = Yes -GHC_VERSION = 9.2.5 -REVISION = 0 +GHC_VERSION = 9.2.6 DISTNAME = ghc-${GHC_VERSION} CATEGORIES = lang devel HOMEPAGE = https://www.haskell.org/ghc/ @@ -66,13 +65,13 @@ GHC_ITEMS = \ ARRAY 0.5.4.0 \ BASE4.16.4.0 \ BINARY 0.8.9.0 \ - BYTESTRING 0.11.3.1 \ + BYTESTRING 0.11.4.0 \ CONTAINERS 0.6.5.1 \ DEEPSEQ 1.4.6.1 \ DIRECTORY 1.3.6.2 \ EXCEPTIONS 0.10.4 \ FILEPATH1.4.2.2 \ - GHC 9.2.5\ + GHC 9.2.6\ GHC_BIGNUM 1.2 \ GHC_COMPACT 0.1.0.0 \ GHC_PRIM0.8.0\ diff --git a/lang/ghc/distinfo b/lang/ghc/distinfo index 7d71490ba1c..e1dcc529840 100644 --- a/lang/ghc/distinfo +++ b/lang/ghc/distinfo @@ -1,8 +1,8 @@ SHA256 (ghc/ghc-8.10.7.20220904-amd64-unknown-openbsd.tar.xz) = bH1nISV38j0ogaqDQuRycw55YaE031EEe6XR4vyw+1Q= SHA256 (ghc/ghc-8.10.7.20220904-shlibs-amd64.tar.gz) = icwBqEzjeDiW42tw/9kTHC7/Hso9+fjjZaBJ5DF9chY= -SHA256 (ghc/ghc-9.2.5-src.tar.xz) = BgZ5fRs44tiO4iQ/OOxrmhqpPptXjpXw3pqcCkFEAhw= -SHA256 (ghc/ghc-9.2.5-testsuite.tar.xz) = dIR05uCVKX/BPR5XIwKi8xdanwZZ1D2K50rG3CIECqY= +SHA256 (ghc/ghc-9.2.6-src.tar.xz) = elTPA5itSItO0hnhXR0eZMC2h2xDoFZFUN0R8FQNcwU= +SHA256 (ghc/ghc-9.2.6-testsuite.tar.xz) = YQsidzuDfndyrjAfoGZfpiCt+9KEF4AhjmZvclrWNjk= SIZE (ghc/ghc-8.10.7.20220904-amd64-unknown-openbsd.tar.xz) = 35756988 SIZE (ghc/ghc-8.10.7.20220904-shlibs-amd64.tar.gz) = 3686128 -SIZE (ghc/ghc-9.2.5-src.tar.xz) = 24655072 -SIZE (ghc/ghc-9.2.5-testsuite.tar.xz) = 3198932 +SIZE (ghc/ghc-9.2.6-src.tar.xz) = 24638236 +SIZE (ghc/ghc-9.2.6-testsuite.tar.xz) = 3202896 diff --git a/lang/ghc/pkg/PLIST b/lang/ghc/pkg/PLIST index 5d6cb87b8f0..80b8821223b 100644 --- a/lang/ghc/pkg/PLIST +++ b/lang/ghc/pkg/PLIST @@ -1826,9 +1826,13 @@ lib/ghc/bytestring-${BYTESTRING_VER}/Data/ByteString/Builder/RealFloat/TableGene lib/ghc/bytestring-${BYTESTRING_VER}/Data/ByteString/Char8.dyn_hi lib/ghc/bytestring-${BYTESTRING_VER}/Data/ByteString/Char8.hi lib/ghc/bytestring-${BYTESTRING_VER}/Data/ByteString/Char8.p_hi +lib/ghc/bytestring-${BYTESTRING_VER}/Data/ByteString/Internal/ lib/ghc/bytestring-${BYTESTRING_VER}/Data/ByteString/Internal.dyn_hi lib/ghc/bytestring-${BYTESTRING_VER}/Data/ByteString/Internal.hi lib/ghc/bytestring-${BYTESTRING_VER}/Data/ByteString/Internal.p_hi +lib/ghc/bytestring-${BYTESTRING_VER}/Data/ByteString/Internal/Type.dyn_hi +lib/ghc/bytestring-${BYTESTRING_VER}/Data/ByteString/Internal/Type.hi +lib/ghc/bytestring-${BYTESTRING_VER}/Data/ByteString/Internal/Type.p_hi lib/ghc/bytestring-${BYTESTRING_VER}/Data/ByteString/Lazy/ lib/ghc/bytestring-${BYTESTRING_VER}/Data/ByteString/Lazy.dyn_hi lib/ghc/bytestring-${BYTESTRING_VER}/Data/ByteString/Lazy.hi @@ -7877,6 +7881,7 @@ share/doc/ghc/html/users_guide/9.2.1-notes.html share/doc/ghc/html/users_guide/9.2.2-notes.html share/doc/ghc/html/users_guide/9.2.3-notes.html share/doc/ghc/html/users_guide/9.2.4-notes.html +share/doc/ghc/html/users_guide/9.2.5-notes.html share/doc/ghc/html/users_guide/${GHC_VER}-notes.html share/doc/ghc/html/users_guide/_images/ share/doc/ghc/html/users_guide/_images/prof_scc.svg @@ -7885,6 +7890,7 @@ share/doc/ghc/html/users_guide/_sources/9.2.1-notes.rst.txt share/doc/ghc/html/users_guide/_sources/9.2.2-notes.rst.txt share/doc/ghc/html/users_guide/_sources/9.2.3-notes.rst.txt share/doc/ghc/html/users_guide/_sources/9.2.4-notes.rst.txt +share/doc/ghc/html/users_guide/_sources/9.2.5-notes.rst.txt share/doc/ghc/html/users_guide/_sources/${GHC_VER}-notes.rst.txt share/doc/ghc/html/users_guide/_sources/bugs.rst.txt share/doc/ghc/html/users_guide/_sources/codegens.rst.txt -- 2.39.1
UPDATE: SQLMap-1.7.2
Hi, Update for SQLMap to 1.7.2: https://github.com/sqlmapproject/sqlmap/releases/tag/1.7 OK? Comments? Cheers.- Index: Makefile === RCS file: /cvs/ports/security/sqlmap/Makefile,v retrieving revision 1.43 diff -u -p -r1.43 Makefile --- Makefile2 Dec 2022 10:09:38 - 1.43 +++ Makefile11 Feb 2023 23:37:54 - @@ -2,7 +2,7 @@ COMMENT = penetration testing tool to d GH_ACCOUNT = sqlmapproject GH_PROJECT = sqlmap -GH_TAGNAME = 1.6.11 +GH_TAGNAME = 1.7.2 CATEGORIES = security Index: distinfo === RCS file: /cvs/ports/security/sqlmap/distinfo,v retrieving revision 1.33 diff -u -p -r1.33 distinfo --- distinfo2 Dec 2022 10:09:38 - 1.33 +++ distinfo11 Feb 2023 23:37:54 - @@ -1,2 +1,2 @@ -SHA256 (sqlmap-1.6.11.tar.gz) = fBCpJZH0QGeK9+rwfEOaMxx5qG5EWI4yy85JCrcxuv4= -SIZE (sqlmap-1.6.11.tar.gz) = 7206836 +SHA256 (sqlmap-1.7.2.tar.gz) = WNufsKeTMpJ2NM243m335imX7IW3fa7wznM2EqHXneE= +SIZE (sqlmap-1.7.2.tar.gz) = 7208613 Index: pkg/PLIST === RCS file: /cvs/ports/security/sqlmap/pkg/PLIST,v retrieving revision 1.29 diff -u -p -r1.29 PLIST --- pkg/PLIST 2 Dec 2022 10:09:38 - 1.29 +++ pkg/PLIST 11 Feb 2023 23:37:55 - @@ -968,6 +968,7 @@ share/sqlmap/tamper/${MODPY_PYCACHE}half share/sqlmap/tamper/${MODPY_PYCACHE}hex2char.${MODPY_PYC_MAGIC_TAG}pyc share/sqlmap/tamper/${MODPY_PYCACHE}hexentities.${MODPY_PYC_MAGIC_TAG}pyc share/sqlmap/tamper/${MODPY_PYCACHE}htmlencode.${MODPY_PYC_MAGIC_TAG}pyc +share/sqlmap/tamper/${MODPY_PYCACHE}if2case.${MODPY_PYC_MAGIC_TAG}pyc share/sqlmap/tamper/${MODPY_PYCACHE}ifnull2casewhenisnull.${MODPY_PYC_MAGIC_TAG}pyc share/sqlmap/tamper/${MODPY_PYCACHE}ifnull2ifisnull.${MODPY_PYC_MAGIC_TAG}pyc share/sqlmap/tamper/${MODPY_PYCACHE}informationschemacomment.${MODPY_PYC_MAGIC_TAG}pyc @@ -1035,6 +1036,7 @@ share/sqlmap/tamper/halfversionedmorekey share/sqlmap/tamper/hex2char.py share/sqlmap/tamper/hexentities.py share/sqlmap/tamper/htmlencode.py +share/sqlmap/tamper/if2case.py share/sqlmap/tamper/ifnull2casewhenisnull.py share/sqlmap/tamper/ifnull2ifisnull.py share/sqlmap/tamper/informationschemacomment.py -- %gonzalo
UPDATE: Zile-2.6.2
Hello, Update for Zile to 2.6.2: https://www.gnu.org/software/zile/ OK? Comments? Cheers.- Index: Makefile === RCS file: /cvs/ports/editors/zile/Makefile,v retrieving revision 1.53 diff -u -p -r1.53 Makefile --- Makefile11 Mar 2022 18:58:40 - 1.53 +++ Makefile11 Feb 2023 23:26:27 - @@ -1,5 +1,5 @@ COMMENT= lightweight Emacs clone -DISTNAME= zile-2.4.15 +DISTNAME= zile-2.6.2 CATEGORIES=editors HOMEPAGE= https://www.gnu.org/software/zile/ @@ -8,12 +8,14 @@ MAINTAINER= Gonzalo L. R. https://git.savannah.gnu.org/cgit/gnulib.git/commit/lib/vasnprintf.c?id=b954346c6101860c7b462d1b286641d1307afd6c - -Index: lib/vasnprintf.c lib/vasnprintf.c.orig -+++ lib/vasnprintf.c -@@ -4871,10 +4871,7 @@ VASNPRINTF (DCHAR_T *resultbuf, size_t *lengthp, - #endif - *fbp = dp->conversion; - #if USE_SNPRINTF --# if ! (((__GLIBC__ > 2 || (__GLIBC__ == 2 && __GLIBC_MINOR__ >= 3))\ -- && !defined __UCLIBC__)\ --|| (defined __APPLE__ && defined __MACH__) \ --|| (defined _WIN32 && ! defined __CYGWIN__)) -+# if 0 - fbp[1] = '%'; - fbp[2] = 'n'; - fbp[3] = '\0'; Index: patches/patch-src_funcs_c === RCS file: patches/patch-src_funcs_c diff -N patches/patch-src_funcs_c --- patches/patch-src_funcs_c 11 Mar 2022 18:58:40 - 1.3 +++ /dev/null 1 Jan 1970 00:00:00 - @@ -1,18 +0,0 @@ -Index: src/funcs.c src/funcs.c.orig -+++ src/funcs.c -@@ -1115,14 +1115,11 @@ END_DEFUN - /* The `start' and `end' arguments are fake, hence their string type, -so they can be ignored, hence the pragma (FIXME: work out how to -apply just to `start' and `end'). */ --#pragma GCC diagnostic push --#pragma GCC diagnostic ignored "-Wunused-but-set-variable" - DEFUN_ARGS ("shell-command-on-region", shell_command_on_region, - STR_ARG (start) - STR_ARG (end) - STR_ARG (cmd) - BOOL_ARG (insert)) --#pragma GCC diagnostic pop - /*+ - Execute string command in inferior shell with region as input. - Normally display output (if any) in temp buffer `*Shell Command Output*'; Index: patches/patch-src_minibuf_c === RCS file: patches/patch-src_minibuf_c diff -N patches/patch-src_minibuf_c --- patches/patch-src_minibuf_c 11 Mar 2022 18:58:40 - 1.3 +++ /dev/null 1 Jan 1970 00:00:00 - @@ -1,14 +0,0 @@ -Index: src/minibuf.c src/minibuf.c.orig -+++ src/minibuf.c -@@ -280,10 +280,7 @@ minibuf_vread_completion (const char *fmt, const char - } - else - { --#pragma GCC diagnostic push --#pragma GCC diagnostic ignored "-Wformat-nonliteral" - minibuf_error (invalid_err, astr_cstr (ms)); --#pragma GCC diagnostic pop - waitkey (); - } - } -- %gonzalo
How to handle version numbers of shared libraries?
Hello porters, This may be a silly question. The porters handbook and bsd.port.mk man page suggest that version is set to 0.0 and then it is incremented as software develops and so on. This stuff I understand. As far as I dig information, the libraries are then installed as libfoo.so.0.0 and to get this working is matter of testing and fidling the build process. Now comes the tricky part. Someone finds a bug. It gets fixed in svn and when I set the library version to wrong number, consumer says the library is incompatible. And this is sane thing. Using old and broken library is stupid, loses work and makes you angry. But for the finder of the bug, the ported library is useless. And the bug fix stays untested. After that I would get the blame of broken package. When I work on the port side of the consumer programs, I can take care of this problem. However how to handle the non-ported build? And there are no unportable things like GNU or libtool. Maybe pkg-config in configure as fallback for dependencies. And if someone is interested, I'm working on Ringdove suite. Librnd, pcb-rnd, camv-rnd and sch-rnd. Best regards, Hannu Vuolasaho P.S. What the comment on SHARED_LIB line means?
Re: [NEW] devel/pax-utils
On Sat, Feb 11, 2023 at 09:44:27AM +, Stuart Henderson wrote: > On 2023/02/10 12:44, Frederic Cambus wrote: > > Hi ports@, > > > > Here is a new port: devel/pax-utils > > I think it would be better not to package pspax, it requires procfs. Makes sense yes, I imported the package earlier today with pspax and pspax.1 removed. Thanks!
Re: NEW: databases/puppetdb and sysutils/puppetserver 7.X
On Saturday, February 11, 2023 22:00 CET, "Sebastian Reitenbach" wrote: > On Saturday, February 11, 2023 21:55 CET, "Sebastian Reitenbach" > wrote: > > > On Saturday, February 11, 2023 11:35 CET, Giovanni Bechis > > wrote: > > > > > On Sat, Feb 11, 2023 at 11:03:57AM +0100, Giovanni Bechis wrote: > > > > On Sat, Feb 11, 2023 at 12:01:27AM +0100, Sebastian Reitenbach wrote: > > > > > On Thursday, February 09, 2023 14:51 CET, Giovanni Bechis > > > > > wrote: > > > > > > > > > > > On 1/30/23 21:42, Sebastian Reitenbach wrote: > > > > > > > Hi, > > > > > > > > > > > > > > with Puppet 5 now replaced by Puppet 7, the ability to run a > > > > > > > Puppet master on OpenBSD was gone. > > > > > > > These two new packages replace the old PuppetDB 5, with PuppetDB > > > > > > > 7 and introduces the new Puppetserver. > > > > > > > > > > > > > > Similarly to systuls/ruby-puppet, they go into branches based on > > > > > > > the major version, to have future room for Puppet 8. > > > > > > > Their paths where software gets installed is aligned to Puppet, > > > > > > > under /var/puppetlabs/... /usr/local/share/puppetlabs/... etc. > > > > > > > > > > > > > > Puppetserver usually comes bundled with a Ruby interpreter and > > > > > > > Puppet agent. That doesn't work out > > > > > > > on OpenBSD. Therefore some bootstrapping has to be done manually > > > > > > > that is OpenBSD specific, and noted > > > > > > > in the Puppetserver pkg/README. > > > > > > > > > > > > > > A couple of tweaks I had to do to my hiera files, as well as to > > > > > > > some of the modules, mostly updating > > > > > > > them. Overall, the changes weren't that big. As everyone might > > > > > > > have different (custom) modules or > > > > > > > hiera plugins in use, ymmv. Therefore I can't really provide a > > > > > > > step by step upgrade path. Install on a test > > > > > > > environment before attempting to upgrade/replace your former > > > > > > > Puppet 5 Master. > > > > > > > That said, Puppet 7 works for me standalone with puppet apply ... > > > > > > > but also against this Puppetserver with PuppetDB backend, > > > > > > > autosigning setup... > > > > > > > > > > > > > > comments to the ports, test reports, or maybe even OKs welcome ;) > > > > > > > > > > > > > > cheers, > > > > > > > Sebastian > > > > > > > > > > > > > > > > thanks for testing. > > > > > > Few issues: > > > > > > - puppetdb is missing pkg/README file in the tarball > > > > > This is missing on purpose, forgot to remove that, as I did > > > > > last-minute clean-ups before sending out the tarball. > > > > > Puppetdb is quite standard, so the upstream doc should more or less > > > > > just work. Also the old puppetdb 5 README > > > > > contained quite some outdated/misleading info > > > > > If there turns to be out some OpenBSD specific issues, I'm happy to > > > > > re-add. > > > > > > > > > > > - puppetserver doesn't create /var/log/puppetlabs/puppetserver > > > > > > directory > > > > > oops > > > > > > > > > > > - puppetserver doesn't start on my server log file attached, it > > > > > > seems there is a dependency missing (no such file to load...). > > > > > puppetserver is quite non-standard, compared to puppetdb, just to > > > > > make sure, did you do the initial bootstrap as described in the > > > > > README? > > > > > > > > > actually I did not bootstrapped it. > > > > After bootstrap it fails with a slightly different error (no such file > > > > to load -- facter). > > > > > > > this diff fixes the issue. > > > > I don't think puppetserver picks up facter from "outside" > > > > but it seems I forgot to add facter as a gem to install in the README: > > > > # puppetserver gem install --no-document puppet hiera-eyaml \ > > hiera-file ipaddress msgpack facter > > > > This is not in the packages I just sent, but have it updated in my mystuff/ > > or wait, it actually should have pulled pulled facter in via the bootstrap > step. > > Do you can check > sudo puppetserver gem list > Facter should actually be there? forgot that facter is BAD, due to the extra copy step, until the OpenBSD patch is merged upstream and released. So yes, for the time being, the facter version installed via puppetserver gem install and in the system should be the same version. maybe commenting and bugging on the PR might help: https://github.com/puppetlabs/facter/pull/2531 Therefore, as it seems to work for you, OK for the ruby-facter update. Sebastian > > Sebastian > > > > > Sebastian > > > > > Thanks > > > Giovanni > > > > > > Index: Makefile > > > === > > > RCS file: /cvs/ports/sysutils/ruby-facter/Makefile,v > > > retrieving revision 1.92 > > > diff -u -p -r1.92 Makefile > > > --- Makefile 22 Jan 2023 19:21:56 - 1.92 > > > +++ Makefile 11 Feb 2023 10:34:05 - > > > @@ -1,7 +1,6 @@ > > > COMMENT =Puppet module management > > > > >
Re: NEW: databases/puppetdb and sysutils/puppetserver 7.X
On Saturday, February 11, 2023 21:55 CET, "Sebastian Reitenbach" wrote: > On Saturday, February 11, 2023 11:35 CET, Giovanni Bechis > wrote: > > > On Sat, Feb 11, 2023 at 11:03:57AM +0100, Giovanni Bechis wrote: > > > On Sat, Feb 11, 2023 at 12:01:27AM +0100, Sebastian Reitenbach wrote: > > > > On Thursday, February 09, 2023 14:51 CET, Giovanni Bechis > > > > wrote: > > > > > > > > > On 1/30/23 21:42, Sebastian Reitenbach wrote: > > > > > > Hi, > > > > > > > > > > > > with Puppet 5 now replaced by Puppet 7, the ability to run a Puppet > > > > > > master on OpenBSD was gone. > > > > > > These two new packages replace the old PuppetDB 5, with PuppetDB 7 > > > > > > and introduces the new Puppetserver. > > > > > > > > > > > > Similarly to systuls/ruby-puppet, they go into branches based on > > > > > > the major version, to have future room for Puppet 8. > > > > > > Their paths where software gets installed is aligned to Puppet, > > > > > > under /var/puppetlabs/... /usr/local/share/puppetlabs/... etc. > > > > > > > > > > > > Puppetserver usually comes bundled with a Ruby interpreter and > > > > > > Puppet agent. That doesn't work out > > > > > > on OpenBSD. Therefore some bootstrapping has to be done manually > > > > > > that is OpenBSD specific, and noted > > > > > > in the Puppetserver pkg/README. > > > > > > > > > > > > A couple of tweaks I had to do to my hiera files, as well as to > > > > > > some of the modules, mostly updating > > > > > > them. Overall, the changes weren't that big. As everyone might have > > > > > > different (custom) modules or > > > > > > hiera plugins in use, ymmv. Therefore I can't really provide a step > > > > > > by step upgrade path. Install on a test > > > > > > environment before attempting to upgrade/replace your former Puppet > > > > > > 5 Master. > > > > > > That said, Puppet 7 works for me standalone with puppet apply ... > > > > > > but also against this Puppetserver with PuppetDB backend, > > > > > > autosigning setup... > > > > > > > > > > > > comments to the ports, test reports, or maybe even OKs welcome ;) > > > > > > > > > > > > cheers, > > > > > > Sebastian > > > > > > > > > > > > > thanks for testing. > > > > > Few issues: > > > > > - puppetdb is missing pkg/README file in the tarball > > > > This is missing on purpose, forgot to remove that, as I did last-minute > > > > clean-ups before sending out the tarball. > > > > Puppetdb is quite standard, so the upstream doc should more or less > > > > just work. Also the old puppetdb 5 README > > > > contained quite some outdated/misleading info > > > > If there turns to be out some OpenBSD specific issues, I'm happy to > > > > re-add. > > > > > > > > > - puppetserver doesn't create /var/log/puppetlabs/puppetserver > > > > > directory > > > > oops > > > > > > > > > - puppetserver doesn't start on my server log file attached, it seems > > > > > there is a dependency missing (no such file to load...). > > > > puppetserver is quite non-standard, compared to puppetdb, just to make > > > > sure, did you do the initial bootstrap as described in the README? > > > > > > > actually I did not bootstrapped it. > > > After bootstrap it fails with a slightly different error (no such file > > > to load -- facter). > > > > > this diff fixes the issue. > > I don't think puppetserver picks up facter from "outside" > > but it seems I forgot to add facter as a gem to install in the README: > > # puppetserver gem install --no-document puppet hiera-eyaml \ > hiera-file ipaddress msgpack facter > > This is not in the packages I just sent, but have it updated in my mystuff/ or wait, it actually should have pulled pulled facter in via the bootstrap step. Do you can check sudo puppetserver gem list Facter should actually be there? Sebastian > > Sebastian > > > Thanks > > Giovanni > > > > Index: Makefile > > === > > RCS file: /cvs/ports/sysutils/ruby-facter/Makefile,v > > retrieving revision 1.92 > > diff -u -p -r1.92 Makefile > > --- Makefile22 Jan 2023 19:21:56 - 1.92 > > +++ Makefile11 Feb 2023 10:34:05 - > > @@ -1,7 +1,6 @@ > > COMMENT = Puppet module management > > > > -DISTNAME = facter-4.2.14 > > -REVISION = 0 > > +DISTNAME = facter-4.3.0 > > CATEGORIES = sysutils > > HOMEPAGE = https://github.com/puppetlabs/facter > > MAINTAINER = Sebastian Reitenbach > > Index: distinfo > > === > > RCS file: /cvs/ports/sysutils/ruby-facter/distinfo,v > > retrieving revision 1.30 > > diff -u -p -r1.30 distinfo > > --- distinfo22 Jan 2023 15:42:43 - 1.30 > > +++ distinfo11 Feb 2023 10:34:05 - > > @@ -1,2 +1,2 @@ > > -SHA256 (facter-4.2.14.gem) = nee+3CaHwnSVo0YRrzc0CB6VkXYVYPQNr7s17Zvefbs= > > -SIZE (facter-4.2.14.gem) = 159232 > > +SHA256 (facter-4.3.0.gem) = 0kWX0P3GqSGcsW9X9xUSzZchlhF3XiSGi9MJ
Re: NEW: databases/puppetdb and sysutils/puppetserver 7.X
On Saturday, February 11, 2023 11:35 CET, Giovanni Bechis wrote: > On Sat, Feb 11, 2023 at 11:03:57AM +0100, Giovanni Bechis wrote: > > On Sat, Feb 11, 2023 at 12:01:27AM +0100, Sebastian Reitenbach wrote: > > > On Thursday, February 09, 2023 14:51 CET, Giovanni Bechis > > > wrote: > > > > > > > On 1/30/23 21:42, Sebastian Reitenbach wrote: > > > > > Hi, > > > > > > > > > > with Puppet 5 now replaced by Puppet 7, the ability to run a Puppet > > > > > master on OpenBSD was gone. > > > > > These two new packages replace the old PuppetDB 5, with PuppetDB 7 > > > > > and introduces the new Puppetserver. > > > > > > > > > > Similarly to systuls/ruby-puppet, they go into branches based on the > > > > > major version, to have future room for Puppet 8. > > > > > Their paths where software gets installed is aligned to Puppet, under > > > > > /var/puppetlabs/... /usr/local/share/puppetlabs/... etc. > > > > > > > > > > Puppetserver usually comes bundled with a Ruby interpreter and Puppet > > > > > agent. That doesn't work out > > > > > on OpenBSD. Therefore some bootstrapping has to be done manually that > > > > > is OpenBSD specific, and noted > > > > > in the Puppetserver pkg/README. > > > > > > > > > > A couple of tweaks I had to do to my hiera files, as well as to > > > > > some of the modules, mostly updating > > > > > them. Overall, the changes weren't that big. As everyone might have > > > > > different (custom) modules or > > > > > hiera plugins in use, ymmv. Therefore I can't really provide a step > > > > > by step upgrade path. Install on a test > > > > > environment before attempting to upgrade/replace your former Puppet 5 > > > > > Master. > > > > > That said, Puppet 7 works for me standalone with puppet apply ... but > > > > > also against this Puppetserver with PuppetDB backend, autosigning > > > > > setup... > > > > > > > > > > comments to the ports, test reports, or maybe even OKs welcome ;) > > > > > > > > > > cheers, > > > > > Sebastian > > > > > > > > > > thanks for testing. > > > > Few issues: > > > > - puppetdb is missing pkg/README file in the tarball > > > This is missing on purpose, forgot to remove that, as I did last-minute > > > clean-ups before sending out the tarball. > > > Puppetdb is quite standard, so the upstream doc should more or less just > > > work. Also the old puppetdb 5 README > > > contained quite some outdated/misleading info > > > If there turns to be out some OpenBSD specific issues, I'm happy to > > > re-add. > > > > > > > - puppetserver doesn't create /var/log/puppetlabs/puppetserver directory > > > oops > > > > > > > - puppetserver doesn't start on my server log file attached, it seems > > > > there is a dependency missing (no such file to load...). > > > puppetserver is quite non-standard, compared to puppetdb, just to make > > > sure, did you do the initial bootstrap as described in the README? > > > > > actually I did not bootstrapped it. > > After bootstrap it fails with a slightly different error (no such file > > to load -- facter). > > > this diff fixes the issue. I don't think puppetserver picks up facter from "outside" but it seems I forgot to add facter as a gem to install in the README: # puppetserver gem install --no-document puppet hiera-eyaml \ hiera-file ipaddress msgpack facter This is not in the packages I just sent, but have it updated in my mystuff/ Sebastian > Thanks > Giovanni > > Index: Makefile > === > RCS file: /cvs/ports/sysutils/ruby-facter/Makefile,v > retrieving revision 1.92 > diff -u -p -r1.92 Makefile > --- Makefile 22 Jan 2023 19:21:56 - 1.92 > +++ Makefile 11 Feb 2023 10:34:05 - > @@ -1,7 +1,6 @@ > COMMENT =Puppet module management > > -DISTNAME = facter-4.2.14 > -REVISION = 0 > +DISTNAME = facter-4.3.0 > CATEGORIES = sysutils > HOMEPAGE = https://github.com/puppetlabs/facter > MAINTAINER = Sebastian Reitenbach > Index: distinfo > === > RCS file: /cvs/ports/sysutils/ruby-facter/distinfo,v > retrieving revision 1.30 > diff -u -p -r1.30 distinfo > --- distinfo 22 Jan 2023 15:42:43 - 1.30 > +++ distinfo 11 Feb 2023 10:34:05 - > @@ -1,2 +1,2 @@ > -SHA256 (facter-4.2.14.gem) = nee+3CaHwnSVo0YRrzc0CB6VkXYVYPQNr7s17Zvefbs= > -SIZE (facter-4.2.14.gem) = 159232 > +SHA256 (facter-4.3.0.gem) = 0kWX0P3GqSGcsW9X9xUSzZchlhF3XiSGi9MJdbBsrSw= > +SIZE (facter-4.3.0.gem) = 159232
Re: NEW: databases/puppetdb and sysutils/puppetserver 7.X
On Thursday, February 09, 2023 14:51 CET, Giovanni Bechis wrote: > On 1/30/23 21:42, Sebastian Reitenbach wrote: > > Hi, > > > > with Puppet 5 now replaced by Puppet 7, the ability to run a Puppet master > > on OpenBSD was gone. > > These two new packages replace the old PuppetDB 5, with PuppetDB 7 and > > introduces the new Puppetserver. > > > > Similarly to systuls/ruby-puppet, they go into branches based on the major > > version, to have future room for Puppet 8. > > Their paths where software gets installed is aligned to Puppet, under > > /var/puppetlabs/... /usr/local/share/puppetlabs/... etc. > > > > Puppetserver usually comes bundled with a Ruby interpreter and Puppet > > agent. That doesn't work out > > on OpenBSD. Therefore some bootstrapping has to be done manually that is > > OpenBSD specific, and noted > > in the Puppetserver pkg/README. > > > > A couple of tweaks I had to do to my hiera files, as well as to some of > > the modules, mostly updating > > them. Overall, the changes weren't that big. As everyone might have > > different (custom) modules or > > hiera plugins in use, ymmv. Therefore I can't really provide a step by step > > upgrade path. Install on a test > > environment before attempting to upgrade/replace your former Puppet 5 > > Master. > > That said, Puppet 7 works for me standalone with puppet apply ... but also > > against this Puppetserver with PuppetDB backend, autosigning setup... > > > > comments to the ports, test reports, or maybe even OKs welcome ;) > > > > cheers, > > Sebastian > > Few issues: > - puppetdb is missing pkg/README file in the tarball > - puppetserver doesn't create /var/log/puppetlabs/puppetserver directory revisited puppetdb and puppetserver packages. They now create /var/log/puppetlabs/XXX directories, as well as I saw, also properly puppetdb vardir to the right position. While there exchanged a number of hardcoded /etc /var /usr/local with respective variables. Updated dependencies a bit for puppetdb-termini. The main puppetdb is not really depending on it, but puppetserver is, so made that one depending on the termini. > - puppetserver doesn't start on my server log file attached, it seems there > is a dependency missing (no such file to load...). To let the puppetserver startup properly, you have to take the initial bootstrapping steps as described in the README. On other OS, puppetserver comes bundled with puppet, and a bundled Ruby etc. That's not possible for us, so have to install puppet "within" puppetserver, so it's jruby interpreter can find and use it. > New package doesn't upgrade from puppet5, a pkg_path is missing I think. I'm lousy whith pkg_path thingies, and don't have a box where to properly test it out. those that still have Puppet5 are old, and these that switched already, don't have puppet5 anymore. Esp. with the clean-up to the first two points, and taking puppetserver README into account, I believe things should now work smoothly. They installed fine for me, as well as starting up. More feedback welcome, other than that, OKs as well. If ther's oddities left, they can be fixed in-tree afterward. cheers, Sebastian puppetserver.tar.gz Description: application/gzip puppetdb.tar.gz Description: application/gzip ruby-puppetserver-ca.tar.gz Description: application/gzip
Re: [new] gurk-rs - a cli signal client
Hello, sh+openbsd-po...@codevoid.de (Stefan Hagen), 2023.02.10 (Fri) 19:28 (CET): > here is a command line signal client. It's lacking a lot of features, > but basic text send/receive functionality is there. for me the client quits upon receiving messages, reliably. 2023-02-11T15:50:33.433155Z ERROR panic: thread 'main' panicked at 'called `Result::unwrap()` on an `Err` value: Error { kind: Uncategorized, message: "no current exe available (short)" }': /usr/ports/pobj/gurk-rs-0.3.0/gurk-rs-0.3.0/modcargo-crates/ \ notify-rust-4.5.10/src/notification.rs:23 > The contact sync doesn't work for me. But I can see and message in > conversations initiated after gurk-rs is linked. > > I hope the situation will improve. But this client is much better than > having no client at all. it would be so handy. thanks for your work! > Some hints: > - this is rust, so build with "MAKE_JOBS=8 make", or something. compile and install worked, I understand you comment now. > - F1 shows the key bindings and they're not configurable > - gurk -v(vv) starts verbose mode writes to gurk.log Regarding Signal Messenger client for the terminal written in Rust. While beeing completely right it does not tell that it is a Text User Interface (TUI). Maybe steeli^Wtaking a bit from tut(1)'s description? So TUI for Mastodon with vim inspired keys becomes Signal Messenger client TUI with strange key bindings Marcus
Re: amd64-clang bulk build report (rep-gtk and sawfish)
11.02.2023 04:02, Theo Buehler пишет: > x11/rep-gtk lisp generated C code, incorrect types for coordinate > getters [-Wint-conversion] https://repology.org/projects/?search=rep-gtk Last upstream update in 2013, we're stuck at 0.90.8.1 while others package .2 and .3, although it is not immediately clear to me where this version comes from. https://sawfish.fandom.com/wiki/Rep-GTK ? Only consumer is x11/sawfish which is stuck at 1.12.90 from 2017 while 1.13.0 appeared in 2021. Anyone still using this and interested in taking care of those two? Otherwise we can send them to the attic and "save them for later".
Re: -current rspamd hyperscan error
Hello, s...@spacehopper.org (Stuart Henderson), 2023.02.11 (Sat) 15:04 (CET): > On 2023/02/11 08:35, Marcus MERIGHI wrote: > > Hello, > > > > with a snapshot from yesterday: > > > > OpenBSD 7.2-current (GENERIC.MP) #1029: Fri Feb 10 09:16:50 MST > > 2023 > > > > and a -current rspamd: > > > > rspamd-3.4p1-hyperscan event-driven spam filtering system in > > C/Lua > > > > I get the following error upon starting rspamd: > > > > rspamd_multipattern_compile: fatal error: cannot allocate scratch > > space > > for hyperscan: -1 > > > > There are no changes to rspamd limits via login.conf[.d/*]. > > Did you just try hyperscan for the first time, or has it been working > and then broken after an update? (if the latter, what did you update, > and which versions before/after?) It's been working before, I did not change anything intentionally. The machine runs -current since the advent of 7.2. It's upgraded almost daily, the last upgrade was yesterday evening. (upgrade: sysupgrade -nks; pkg_add -u -Dsnap; reboot;) I cannot rule out this has happened before, but it would be quite unlikely to go unnoticed. The machine handles about fifty mail messages a day and it does not accept mail without rspamd running. These missing messages would ring an alarm. (As they did this morning...) > Working ok here with the most recent -current snapshot on amd64 and I > reinstalled hyperscan and rspamd--hyperscan to make sure they're from > the most recent bulk build. (avx2 flavour of hyperscan on a VM on a > ryzen 5650G machine). Something I missed to report, here it is hyperscan-5.4.0-ssse3 on Intel(R) Core(TM) i7-10510U. The dmesg(8) reports SSSE3. I just ran another pkg_add -u -Dsnap and nothing was updated. installurl(5) has http://ftp.hostserver.de/pub/OpenBSD. I'll upgrade tonight and report back. The mails flow, so no worries. Thanks for your time! Marcus
Re: amd64-clang bulk build report
On Sat, Feb 11, 2023 at 12:19:06PM +0100, Landry Breuil wrote: > Le Sat, Feb 11, 2023 at 05:15:41AM +, Yifei Zhan a écrit : > > On 23/02/11 05:02AM, Theo Buehler wrote: > > > My clang 15 ports queue is empty. Below is the list of remaining build > > > failures with some quick notes. Some of them still have obvious fixes. > > > Either there is a maintainer who can look or the ports involve languages > > > or build systems I don't enjoy dealing with. > > > > > > www/midoricvs rm? [-Wint-conversion] > > > > I think cvs rm is the way to go, from offical README[1]: > > > > > ...built on top of Electron and React. > > > > Seems like the midori as we know has been discontinued. > > Even if dead upstream, the web engine it uses is maintained. It used to > be a nice browser, so i'll have a look at eventually fixing the vala > code/conversion since some vala ports also fail.. > > can be marked broken in the meantime ofc, no big deal. There's always the option of passing -Wno-int-conversion, although that doesn't exclude that clang does whatever it wants... I tried the commits mentioned here to fix vala, but that didn't help. https://gitlab.gnome.org/GNOME/vala/-/issues/1407
net/dino: update to 0.4.0
https://dino.im/blog/2023/02/dino-0.4-release/ Upstream switched to GTK4 and uses libadwaita, dlopen()ed at runtime (confirmed with ktrace). gspell is no longer used, it seems, neither at build nor run time. libsoup3 is now linked against. Works for me on amd64. FreeBSD doesn't carry the two patches we have; I'd look into that next. Feedback? OK? Index: Makefile === RCS file: /cvs/ports/net/dino/Makefile,v retrieving revision 1.11 diff -u -p -r1.11 Makefile --- Makefile10 Nov 2022 11:52:23 - 1.11 +++ Makefile8 Feb 2023 00:56:08 - @@ -1,12 +1,12 @@ COMMENT= XMPP desktop client -VERSION= 0.3.1 +VERSION= 0.4.0 DISTNAME= dino-${VERSION} CATEGORIES=net x11 SHARED_LIBS += crypto-vala 0.0 # 0.0 -SHARED_LIBS += dino 1.0 # 0.0 +SHARED_LIBS += dino 2.0 # 0.0 SHARED_LIBS += qlite 0.0 # 0.1 -SHARED_LIBS += xmpp-vala 1.0 # 0.1 +SHARED_LIBS += xmpp-vala 2.0 # 0.1 HOMEPAGE= https://dino.im/ @@ -21,8 +21,9 @@ MODULES= devel/cmake BUILD_DEPENDS= devel/gettext,-tools \ lang/vala RUN_DEPENDS= devel/desktop-file-utils \ - x11/gtk+3,-guic + x11/gtk+4,-guic LIB_DEPENDS= devel/libgee \ + devel/libsoup3 \ graphics/libqrencode \ multimedia/gstreamer1/plugins-base \ net/libnice \ @@ -31,21 +32,21 @@ LIB_DEPENDS=devel/libgee \ security/gpgme \ security/libgcrypt \ security/libsrtp \ - textproc/gspell \ textproc/icu4c \ - x11/gtk+3 + x11/gtk+4 + +# dlopen()ed +LIB_DEPENDS += x11/gnome/libadwaita -# dino's http-files plugin dlopen()s libsoup3 -LIB_DEPENDS += devel/libsoup3 # links against plugins-base, dlopen()s plugins-good LIB_DEPENDS += multimedia/gstreamer1/plugins-good -WANTLIB += atk-1.0 c cairo cairo-gobject enchant-2 gcrypt gdk-3 -WANTLIB += gdk_pixbuf-2.0 gee-0.8 gio-2.0 glib-2.0 gmodule-2.0 -WANTLIB += gnutls gobject-2.0 gpgme gspell-1 gstapp-1.0 gstaudio-1.0 -WANTLIB += gstbase-1.0 gstreamer-1.0 gstrtp-1.0 gtk-3 harfbuzz -WANTLIB += icudata icuuc intl m nice pango-1.0 pangocairo-1.0 -WANTLIB += qrencode signal-protocol-c soup-3.0 sqlite3 srtp2 +WANTLIB += c cairo cairo-gobject gcrypt gdk_pixbuf-2.0 gee-0.8 +WANTLIB += gio-2.0 glib-2.0 gmodule-2.0 gnutls gobject-2.0 gpgme +WANTLIB += graphene-1.0 gstapp-1.0 gstaudio-1.0 gstbase-1.0 gstreamer-1.0 +WANTLIB += gstrtp-1.0 gstvideo-1.0 gtk-4 harfbuzz icudata icuuc +WANTLIB += intl m nice pango-1.0 pangocairo-1.0 qrencode signal-protocol-c +WANTLIB += soup-3.0 sqlite3 srtp2 CONFIGURE_ARGS = -DBUILD_TESTS=ON -DUSE_SOUP3=yes Index: distinfo === RCS file: /cvs/ports/net/dino/distinfo,v retrieving revision 1.6 diff -u -p -r1.6 distinfo --- distinfo10 Nov 2022 11:52:23 - 1.6 +++ distinfo8 Feb 2023 00:08:22 - @@ -1,2 +1,2 @@ -SHA256 (dino-0.3.1.tar.gz) = qkz4kKY1PPJ/ANbPTNenpVKRUwE4pMYKQJzHFufFRuc= -SIZE (dino-0.3.1.tar.gz) = 806613 +SHA256 (dino-0.4.0.tar.gz) = yGCHMo3Lsdohh9su4eH5+jewNTQ1a4X2tshgMGU9t4Q= +SIZE (dino-0.4.0.tar.gz) = 882288 Index: patches/patch-main_CMakeLists_txt === RCS file: /cvs/ports/net/dino/patches/patch-main_CMakeLists_txt,v retrieving revision 1.4 diff -u -p -r1.4 patch-main_CMakeLists_txt --- patches/patch-main_CMakeLists_txt 11 Mar 2022 19:45:53 - 1.4 +++ patches/patch-main_CMakeLists_txt 8 Feb 2023 00:12:05 - @@ -3,7 +3,7 @@ Fix crash on startup, see https://github Index: main/CMakeLists.txt --- main/CMakeLists.txt.orig +++ main/CMakeLists.txt -@@ -217,6 +217,7 @@ add_executable(dino ${MAIN_VALA_C} ${MAIN_GRESOURCES_T +@@ -232,6 +232,7 @@ add_executable(dino ${MAIN_VALA_C} ${MAIN_GRESOURCES_T add_dependencies(dino ${GETTEXT_PACKAGE}-translations) target_include_directories(dino PRIVATE src) target_link_libraries(dino libdino ${MAIN_PACKAGES}) Index: pkg/PLIST === RCS file: /cvs/ports/net/dino/pkg/PLIST,v retrieving revision 1.4 diff -u -p -r1.4 PLIST --- pkg/PLIST 11 Mar 2022 19:45:53 - 1.4 +++ pkg/PLIST 8 Feb 2023 00:26:48 - @@ -18,14 +18,6 @@ lib/dino/plugins/ share/applications/im.dino.Dino.desktop share/dbus-1/services/im.dino.Dino.service share/icons/hicolor/scalable/apps/im.dino.Dino.svg -share/icons/hicolor/scalable/status/dino-changes-prevent-symbolic.svg -share/icons/hicolor/scalable/status/dino-double-tick-symbolic.svg -share/icons/hicolor/scalable/status/dino-qr-code-symbolic.svg -share/icons/hicolor/scalable/status/dino-status-away.svg -share/icons/hicolor/scalable/status/dino-status-chat.svg -share/icons/hic
Re: -current rspamd hyperscan error
On 2023/02/11 08:35, Marcus MERIGHI wrote: > Hello, > > with a snapshot from yesterday: > > OpenBSD 7.2-current (GENERIC.MP) #1029: Fri Feb 10 09:16:50 MST > 2023 > > and a -current rspamd: > > rspamd-3.4p1-hyperscan event-driven spam filtering system in > C/Lua > > I get the following error upon starting rspamd: > > rspamd_multipattern_compile: fatal error: cannot allocate scratch > space > for hyperscan: -1 > > There are no changes to rspamd limits via login.conf[.d/*]. Did you just try hyperscan for the first time, or has it been working and then broken after an update? (if the latter, what did you update, and which versions before/after?) Working ok here with the most recent -current snapshot on amd64 and I reinstalled hyperscan and rspamd--hyperscan to make sure they're from the most recent bulk build. (avx2 flavour of hyperscan on a VM on a ryzen 5650G machine).
Re: UPDATE archivers/zstd-1.5.4
On 2023/02/11 07:50, Bjorn Ketelaars wrote: > zstd-1.5.4 is a pretty big release benefiting from one year of work. It > offers performance improvements, as well as new features, and it fixes > some bugs. Details can be found at > https://github.com/facebook/zstd/releases/tag/v1.5.4 > > Bumped minor because of addition of symbols. > > 'make test' passes all tests, run tested with several consumers on > amd64, and build tested about half of the consumers. > > Comments/OK? OK. Tests look good on aarch64.
vlc core segmentation fault
I think this started about a week ago. Any other info needed? cvlc does work. $: vlc movie.mp4 VLC media player 3.0.18 Vetinari (revision 3.0.13-8-g41878ff4f2) [02906806b860] main libvlc: Running vlc with the default interface. Use 'cvlc' to use vlc without interface. QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-jjf' [028fb041f660] qt interface error: Unable to load extensions module Segmentation fault (core dumped) $: kern.version=OpenBSD 7.2-current (GENERIC.MP) #1031: Fri Feb 10 21:22:48 MST 2023 dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP DMESG: 2,RDSEED,ADX,SMAP,CLFLUSHOPT,SHA,IBPB,XSAVEOPT,XSAVEC,XGETBV1,XSAVES cpu4: 32KB 64b/line 8-way D-cache, 64KB 64b/line 4-way I-cache, 512KB 64b/line 8-way L2 cache, 8MB 64b/line 16-way L3 cache cpu4: smt 0, core 5, package 0 cpu5 at mainbus0: apid 12 (application processor) cpu5: AMD Ryzen 5 1600 Six-Core Processor, 3200.00 MHz, 17-01-01 cpu5: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,MMX,FXSR,SSE,SSE2,HTT,SSE3,PCLMUL,MWAIT,SSSE3,FMA3,CX16,SSE4.1,SSE4.2,MOVBE,POPCNT,AES,XSAVE,AVX,F16C,RDRAND,NXE,MMXX,FFXSR,PAGE1GB,RDTSCP,LONG,LAHF,CMPLEG,SVM,EAPICSP,AMCR8,ABM,SSE4A,MASSE,3DNOWP,OSVW,SKINIT,TCE,TOPEXT,CPCTR,DBKP,PCTRL3,MWAITX,ITSC,FSGSBASE,BMI1,AVX2,SMEP,BMI2,RDSEED,ADX,SMAP,CLFLUSHOPT,SHA,IBPB,XSAVEOPT,XSAVEC,XGETBV1,XSAVES cpu5: 32KB 64b/line 8-way D-cache, 64KB 64b/line 4-way I-cache, 512KB 64b/line 8-way L2 cache, 8MB 64b/line 16-way L3 cache cpu5: smt 0, core 6, package 0 cpu6 at mainbus0: apid 1 (application processor) cpu6: AMD Ryzen 5 1600 Six-Core Processor, 3200.00 MHz, 17-01-01 cpu6: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,MMX,FXSR,SSE,SSE2,HTT,SSE3,PCLMUL,MWAIT,SSSE3,FMA3,CX16,SSE4.1,SSE4.2,MOVBE,POPCNT,AES,XSAVE,AVX,F16C,RDRAND,NXE,MMXX,FFXSR,PAGE1GB,RDTSCP,LONG,LAHF,CMPLEG,SVM,EAPICSP,AMCR8,ABM,SSE4A,MASSE,3DNOWP,OSVW,SKINIT,TCE,TOPEXT,CPCTR,DBKP,PCTRL3,MWAITX,ITSC,FSGSBASE,BMI1,AVX2,SMEP,BMI2,RDSEED,ADX,SMAP,CLFLUSHOPT,SHA,IBPB,XSAVEOPT,XSAVEC,XGETBV1,XSAVES cpu6: 32KB 64b/line 8-way D-cache, 64KB 64b/line 4-way I-cache, 512KB 64b/line 8-way L2 cache, 8MB 64b/line 16-way L3 cache cpu6: smt 1, core 0, package 0 cpu7 at mainbus0: apid 3 (application processor) cpu7: AMD Ryzen 5 1600 Six-Core Processor, 3200.00 MHz, 17-01-01 cpu7: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,MMX,FXSR,SSE,SSE2,HTT,SSE3,PCLMUL,MWAIT,SSSE3,FMA3,CX16,SSE4.1,SSE4.2,MOVBE,POPCNT,AES,XSAVE,AVX,F16C,RDRAND,NXE,MMXX,FFXSR,PAGE1GB,RDTSCP,LONG,LAHF,CMPLEG,SVM,EAPICSP,AMCR8,ABM,SSE4A,MASSE,3DNOWP,OSVW,SKINIT,TCE,TOPEXT,CPCTR,DBKP,PCTRL3,MWAITX,ITSC,FSGSBASE,BMI1,AVX2,SMEP,BMI2,RDSEED,ADX,SMAP,CLFLUSHOPT,SHA,IBPB,XSAVEOPT,XSAVEC,XGETBV1,XSAVES cpu7: 32KB 64b/line 8-way D-cache, 64KB 64b/line 4-way I-cache, 512KB 64b/line 8-way L2 cache, 8MB 64b/line 16-way L3 cache cpu7: smt 1, core 1, package 0 cpu8 at mainbus0: apid 5 (application processor) cpu8: AMD Ryzen 5 1600 Six-Core Processor, 3200.00 MHz, 17-01-01 cpu8: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,MMX,FXSR,SSE,SSE2,HTT,SSE3,PCLMUL,MWAIT,SSSE3,FMA3,CX16,SSE4.1,SSE4.2,MOVBE,POPCNT,AES,XSAVE,AVX,F16C,RDRAND,NXE,MMXX,FFXSR,PAGE1GB,RDTSCP,LONG,LAHF,CMPLEG,SVM,EAPICSP,AMCR8,ABM,SSE4A,MASSE,3DNOWP,OSVW,SKINIT,TCE,TOPEXT,CPCTR,DBKP,PCTRL3,MWAITX,ITSC,FSGSBASE,BMI1,AVX2,SMEP,BMI2,RDSEED,ADX,SMAP,CLFLUSHOPT,SHA,IBPB,XSAVEOPT,XSAVEC,XGETBV1,XSAVES cpu8: 32KB 64b/line 8-way D-cache, 64KB 64b/line 4-way I-cache, 512KB 64b/line 8-way L2 cache, 8MB 64b/line 16-way L3 cache cpu8: smt 1, core 2, package 0 cpu9 at mainbus0: apid 9 (application processor) cpu9: AMD Ryzen 5 1600 Six-Core Processor, 3200.00 MHz, 17-01-01 cpu9: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,MMX,FXSR,SSE,SSE2,HTT,SSE3,PCLMUL,MWAIT,SSSE3,FMA3,CX16,SSE4.1,SSE4.2,MOVBE,POPCNT,AES,XSAVE,AVX,F16C,RDRAND,NXE,MMXX,FFXSR,PAGE1GB,RDTSCP,LONG,LAHF,CMPLEG,SVM,EAPICSP,AMCR8,ABM,SSE4A,MASSE,3DNOWP,OSVW,SKINIT,TCE,TOPEXT,CPCTR,DBKP,PCTRL3,MWAITX,ITSC,FSGSBASE,BMI1,AVX2,SMEP,BMI2,RDSEED,ADX,SMAP,CLFLUSHOPT,SHA,IBPB,XSAVEOPT,XSAVEC,XGETBV1,XSAVES cpu9: 32KB 64b/line 8-way D-cache, 64KB 64b/line 4-way I-cache, 512KB 64b/line 8-way L2 cache, 8MB 64b/line 16-way L3 cache cpu9: smt 1, core 4, package 0 cpu10 at mainbus0: apid 11 (application processor) cpu10: AMD Ryzen 5 1600 Six-Core Processor, 3200.00 MHz, 17-01-01 cpu10: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,MMX,FXSR,SSE,SSE2,HTT,SSE3,PCLMUL,MWAIT,SSSE3,FMA3,CX16,SSE4.1,SSE4.2,MOVBE,POPCNT,AES,XSAVE,AVX,F16C,RDRAND,NXE,MMXX,FFXSR,PAGE1GB,RDTSCP,LONG,LAHF,CMPLEG,SVM,EAPICSP,AMCR8,ABM,SSE4A,MASSE,3DNOWP,OSVW,SKINIT,TCE,TOPEXT,CPCTR,DBKP,PCTRL3,MWAITX,ITSC,FSGSBASE,BMI1,AVX2,SMEP,BMI2,RDSEED,ADX,SMAP,CLFLUSHOPT,SHA,IBPB,XSAVEOPT,XSAVEC,XGETBV1,XSAVES cpu10: 32KB 64b/line 8-way D-cache, 64KB 64b/line 4-way I-cache, 512KB 64b/line 8-wa
Re: postfix-pgsql postmap failures after upgrade
Postfix 3.5 is in -stable packages now, you can use that. -- Sent from a phone, apologies for poor formatting. On 11 February 2023 11:09:44 Stephan Tesch wrote: Hi guys, I know this is pretty old stuff by now, but I updated my mail server yesterday to 7.2 and of course experienced the very same behavior. Should have looked faster into the mail archives :) Anyway, is this something that’s being worked on? Does it help to file a bug with postfix? For now I reverted to file based dictionaries, which is of course not very nice, but the installation is rather small and static. Would be nice to have Postgres in the loop again. Best regards Stephan Am 01.11.2022 um 13:32 schrieb Stuart Henderson : On 2022/11/01 12:58, Marc Peters wrote: On Sun, Oct 30, 2022 at 09:13:19AM +, Stuart Henderson wrote: Seems there is still some conflict between Postfix 3.7 (which needs OpenSSL) and libraries (like libpq) using LibreSSL, despite the static linking. (the upstream developer of TLS code in Postfix is also an OpenSSL developer and seems to prefer using OpenSSL APIs which LibreSSL doesn't have yet). If you have the ports tree on your machine you can unpack the attached file under /usr/ports/mail/postfix, pkg_delete postfix, and build a 3.5 version from /usr/ports/mail/postfix/stable35 with "FLAVOR=pgsql make install". Hi, i saw the same behaviour on my mailserver but used the excuse to move to opensmtpd and reworked the setup in general. Maybe this should be mentioned on the upgrade page for users as a heads up? We are trying to figure out what to do with this. Brad, you didn't answer my other mail so I ask again: how about I commit stable35 to the tree for now?
Re: postfix-pgsql postmap failures after upgrade
Hi guys, I know this is pretty old stuff by now, but I updated my mail server yesterday to 7.2 and of course experienced the very same behavior. Should have looked faster into the mail archives :) Anyway, is this something that’s being worked on? Does it help to file a bug with postfix? For now I reverted to file based dictionaries, which is of course not very nice, but the installation is rather small and static. Would be nice to have Postgres in the loop again. Best regards Stephan > Am 01.11.2022 um 13:32 schrieb Stuart Henderson : > > On 2022/11/01 12:58, Marc Peters wrote: >> On Sun, Oct 30, 2022 at 09:13:19AM +, Stuart Henderson wrote: >>> Seems there is still some conflict between Postfix 3.7 (which needs >>> OpenSSL) and libraries (like libpq) using LibreSSL, despite the static >>> linking. (the upstream developer of TLS code in Postfix is also an >>> OpenSSL developer and seems to prefer using OpenSSL APIs which LibreSSL >>> doesn't have yet). >>> >>> If you have the ports tree on your machine you can unpack the attached >>> file under /usr/ports/mail/postfix, pkg_delete postfix, and build a 3.5 >>> version from /usr/ports/mail/postfix/stable35 with "FLAVOR=pgsql make >>> install". >> >> Hi, >> >> i saw the same behaviour on my mailserver but used the excuse to move to >> opensmtpd and reworked the setup in general. Maybe this should be mentioned >> on the upgrade page for users as a heads up? > > We are trying to figure out what to do with this. > > Brad, you didn't answer my other mail so I ask again: how about I commit > stable35 to the tree for now?
Re: amd64-clang bulk build report
Le Sat, Feb 11, 2023 at 05:15:41AM +, Yifei Zhan a écrit : > On 23/02/11 05:02AM, Theo Buehler wrote: > > My clang 15 ports queue is empty. Below is the list of remaining build > > failures with some quick notes. Some of them still have obvious fixes. > > Either there is a maintainer who can look or the ports involve languages > > or build systems I don't enjoy dealing with. > > > > www/midori cvs rm? [-Wint-conversion] > > I think cvs rm is the way to go, from offical README[1]: > > > ...built on top of Electron and React. > > Seems like the midori as we know has been discontinued. Even if dead upstream, the web engine it uses is maintained. It used to be a nice browser, so i'll have a look at eventually fixing the vala code/conversion since some vala ports also fail.. can be marked broken in the meantime ofc, no big deal.
new: multimedia/karlyriceditor: synchronize music lyrics editor
(manual bump of [1], used it today on -current, works fine as usual) Attached is a port for multimedia/karlyriceditor: Karaoke Lyrics Editor is a program lets you edit and synchronize lyrics with karaoke songs in various formats. Currently supported formats include LRC, LRCv2 (supported by XBMC) and Ultrastar (without pitch). Tested on OpenBSD-current/{amd64,arm64}, I've used it to edit lyrics for a few months now, no problem so far. port-lib-depends-check and portcheck are happy. any comments? [1]: https://marc.info/?l=openbsd-ports&m=165459827212836&w=2 karlyriceditor.tar Description: Unix tar archive
Re: NEW: databases/puppetdb and sysutils/puppetserver 7.X
On Sat, Feb 11, 2023 at 11:03:57AM +0100, Giovanni Bechis wrote: > On Sat, Feb 11, 2023 at 12:01:27AM +0100, Sebastian Reitenbach wrote: > > On Thursday, February 09, 2023 14:51 CET, Giovanni Bechis > > wrote: > > > > > On 1/30/23 21:42, Sebastian Reitenbach wrote: > > > > Hi, > > > > > > > > with Puppet 5 now replaced by Puppet 7, the ability to run a Puppet > > > > master on OpenBSD was gone. > > > > These two new packages replace the old PuppetDB 5, with PuppetDB 7 and > > > > introduces the new Puppetserver. > > > > > > > > Similarly to systuls/ruby-puppet, they go into branches based on the > > > > major version, to have future room for Puppet 8. > > > > Their paths where software gets installed is aligned to Puppet, under > > > > /var/puppetlabs/... /usr/local/share/puppetlabs/... etc. > > > > > > > > Puppetserver usually comes bundled with a Ruby interpreter and Puppet > > > > agent. That doesn't work out > > > > on OpenBSD. Therefore some bootstrapping has to be done manually that > > > > is OpenBSD specific, and noted > > > > in the Puppetserver pkg/README. > > > > > > > > A couple of tweaks I had to do to my hiera files, as well as to some > > > > of the modules, mostly updating > > > > them. Overall, the changes weren't that big. As everyone might have > > > > different (custom) modules or > > > > hiera plugins in use, ymmv. Therefore I can't really provide a step by > > > > step upgrade path. Install on a test > > > > environment before attempting to upgrade/replace your former Puppet 5 > > > > Master. > > > > That said, Puppet 7 works for me standalone with puppet apply ... but > > > > also against this Puppetserver with PuppetDB backend, autosigning > > > > setup... > > > > > > > > comments to the ports, test reports, or maybe even OKs welcome ;) > > > > > > > > cheers, > > > > Sebastian > > > > > > > thanks for testing. > > > Few issues: > > > - puppetdb is missing pkg/README file in the tarball > > This is missing on purpose, forgot to remove that, as I did last-minute > > clean-ups before sending out the tarball. > > Puppetdb is quite standard, so the upstream doc should more or less just > > work. Also the old puppetdb 5 README > > contained quite some outdated/misleading info > > If there turns to be out some OpenBSD specific issues, I'm happy to re-add. > > > > > - puppetserver doesn't create /var/log/puppetlabs/puppetserver directory > > oops > > > > > - puppetserver doesn't start on my server log file attached, it seems > > > there is a dependency missing (no such file to load...). > > puppetserver is quite non-standard, compared to puppetdb, just to make > > sure, did you do the initial bootstrap as described in the README? > > > actually I did not bootstrapped it. > After bootstrap it fails with a slightly different error (no such file > to load -- facter). > this diff fixes the issue. Thanks Giovanni Index: Makefile === RCS file: /cvs/ports/sysutils/ruby-facter/Makefile,v retrieving revision 1.92 diff -u -p -r1.92 Makefile --- Makefile22 Jan 2023 19:21:56 - 1.92 +++ Makefile11 Feb 2023 10:34:05 - @@ -1,7 +1,6 @@ COMMENT = Puppet module management -DISTNAME = facter-4.2.14 -REVISION = 0 +DISTNAME = facter-4.3.0 CATEGORIES = sysutils HOMEPAGE = https://github.com/puppetlabs/facter MAINTAINER = Sebastian Reitenbach Index: distinfo === RCS file: /cvs/ports/sysutils/ruby-facter/distinfo,v retrieving revision 1.30 diff -u -p -r1.30 distinfo --- distinfo22 Jan 2023 15:42:43 - 1.30 +++ distinfo11 Feb 2023 10:34:05 - @@ -1,2 +1,2 @@ -SHA256 (facter-4.2.14.gem) = nee+3CaHwnSVo0YRrzc0CB6VkXYVYPQNr7s17Zvefbs= -SIZE (facter-4.2.14.gem) = 159232 +SHA256 (facter-4.3.0.gem) = 0kWX0P3GqSGcsW9X9xUSzZchlhF3XiSGi9MJdbBsrSw= +SIZE (facter-4.3.0.gem) = 159232
[maintainer update]security/p5-Digest-SHA3: Update to 1.05
Hi, ports@: Here is a simple patch for security/p5-Digest-SHA3 to update to 1.05. It build well and pass all tests on amd64-current system. Only 1 port depends on it and it build well and pass all tests too. Cheers ! wenIndex: security/p5-Digest-SHA3/Makefile === RCS file: /cvs/ports/security/p5-Digest-SHA3/Makefile,v retrieving revision 1.2 diff -u -p -r1.2 Makefile --- security/p5-Digest-SHA3/Makefile11 Mar 2022 19:53:46 - 1.2 +++ security/p5-Digest-SHA3/Makefile11 Feb 2023 09:57:06 - @@ -1,6 +1,6 @@ COMMENT = Perl extension for SHA-3 -DISTNAME = Digest-SHA3-1.04 +DISTNAME = Digest-SHA3-1.05 CATEGORIES = security Index: security/p5-Digest-SHA3/distinfo === RCS file: /cvs/ports/security/p5-Digest-SHA3/distinfo,v retrieving revision 1.1.1.1 diff -u -p -r1.1.1.1 distinfo --- security/p5-Digest-SHA3/distinfo22 May 2021 16:18:55 - 1.1.1.1 +++ security/p5-Digest-SHA3/distinfo11 Feb 2023 09:57:06 - @@ -1,2 +1,2 @@ -SHA256 (Digest-SHA3-1.04.tar.gz) = Smi2fFA09A+7E0SzBM1myqpeMg61IwBSAcwk921HDBQ= -SIZE (Digest-SHA3-1.04.tar.gz) = 29660 +SHA256 (Digest-SHA3-1.05.tar.gz) = rfG5B5sreBdV5XBId6FDCl8SmX6oIgX9KWbJzEZahSI= +SIZE (Digest-SHA3-1.05.tar.gz) = 29416
Re: amd64-clang bulk build report
On 2023/02/11 05:02, Theo Buehler wrote: > comms/pilot-link perl XS [-Wint-conversion] - still useful? > databases/p5-sybperl perl XS [-Wint-conversion] - has newer version (poorly > done) > net/irc yuck - still useful? header mess > [-Wint-conversion] > security/cryptcat varargs - fix on tech / cvs rm? > www/midoricvs rm? [-Wint-conversion] I am OK with removing these ports. > devel/py-llvmlite,python3 ... - no llvm 15 support yet -> BROKEN For the others listed: it wouldn't be the end of the world to break them if they're not fixed before LLVM is ready to commit. Some past llvm updates broke more things on i386 than amd64. Once base can be built on i386 with 15 I'll do a bulk there.
Re: NEW: databases/puppetdb and sysutils/puppetserver 7.X
On Sat, Feb 11, 2023 at 12:01:27AM +0100, Sebastian Reitenbach wrote: > On Thursday, February 09, 2023 14:51 CET, Giovanni Bechis > wrote: > > > On 1/30/23 21:42, Sebastian Reitenbach wrote: > > > Hi, > > > > > > with Puppet 5 now replaced by Puppet 7, the ability to run a Puppet > > > master on OpenBSD was gone. > > > These two new packages replace the old PuppetDB 5, with PuppetDB 7 and > > > introduces the new Puppetserver. > > > > > > Similarly to systuls/ruby-puppet, they go into branches based on the > > > major version, to have future room for Puppet 8. > > > Their paths where software gets installed is aligned to Puppet, under > > > /var/puppetlabs/... /usr/local/share/puppetlabs/... etc. > > > > > > Puppetserver usually comes bundled with a Ruby interpreter and Puppet > > > agent. That doesn't work out > > > on OpenBSD. Therefore some bootstrapping has to be done manually that is > > > OpenBSD specific, and noted > > > in the Puppetserver pkg/README. > > > > > > A couple of tweaks I had to do to my hiera files, as well as to some of > > > the modules, mostly updating > > > them. Overall, the changes weren't that big. As everyone might have > > > different (custom) modules or > > > hiera plugins in use, ymmv. Therefore I can't really provide a step by > > > step upgrade path. Install on a test > > > environment before attempting to upgrade/replace your former Puppet 5 > > > Master. > > > That said, Puppet 7 works for me standalone with puppet apply ... but > > > also against this Puppetserver with PuppetDB backend, autosigning setup... > > > > > > comments to the ports, test reports, or maybe even OKs welcome ;) > > > > > > cheers, > > > Sebastian > > > > thanks for testing. > > Few issues: > > - puppetdb is missing pkg/README file in the tarball > This is missing on purpose, forgot to remove that, as I did last-minute > clean-ups before sending out the tarball. > Puppetdb is quite standard, so the upstream doc should more or less just > work. Also the old puppetdb 5 README > contained quite some outdated/misleading info > If there turns to be out some OpenBSD specific issues, I'm happy to re-add. > > > - puppetserver doesn't create /var/log/puppetlabs/puppetserver directory > oops > > > - puppetserver doesn't start on my server log file attached, it seems there > > is a dependency missing (no such file to load...). > puppetserver is quite non-standard, compared to puppetdb, just to make sure, > did you do the initial bootstrap as described in the README? > actually I did not bootstrapped it. After bootstrap it fails with a slightly different error (no such file to load -- facter). > > > New package doesn't upgrade from puppet5, a pkg_path is missing I think. > not sure if that should. as puppetserver is now "extra", and before, it was > just a single package conaining client and master. > makes sense, we should add some info to upgrade.html then. Thanks Giovanni > Sebastian > > > > > Cheers > > > > Giovanni > 2023-02-11T11:00:43.864+01:00 INFO [main] [o.e.j.u.log] Logging initialized @7581ms to org.eclipse.jetty.util.log.Slf4jLog 2023-02-11T11:00:46.148+01:00 INFO [async-dispatch-2] [p.t.s.s.scheduler-service] Initializing Scheduler Service 2023-02-11T11:00:46.191+01:00 INFO [async-dispatch-2] [o.q.i.StdSchedulerFactory] Using default implementation for ThreadExecutor 2023-02-11T11:00:46.208+01:00 INFO [async-dispatch-2] [o.q.c.SchedulerSignalerImpl] Initialized Scheduler Signaller of type: class org.quartz.core.SchedulerSignalerImpl 2023-02-11T11:00:46.208+01:00 INFO [async-dispatch-2] [o.q.c.QuartzScheduler] Quartz Scheduler v.2.3.2 created. 2023-02-11T11:00:46.210+01:00 INFO [async-dispatch-2] [o.q.s.RAMJobStore] RAMJobStore initialized. 2023-02-11T11:00:46.210+01:00 INFO [async-dispatch-2] [o.q.c.QuartzScheduler] Scheduler meta-data: Quartz Scheduler (v2.3.2) 'a5bac081-c72e-4658-90a6-b4afbc9df9a7' with instanceId 'NON_CLUSTERED' Scheduler class: 'org.quartz.core.QuartzScheduler' - running locally. NOT STARTED. Currently in standby mode. Number of jobs executed: 0 Using thread pool 'org.quartz.simpl.SimpleThreadPool' - with 10 threads. Using job-store 'org.quartz.simpl.RAMJobStore' - which does not support persistence. and is not clustered. 2023-02-11T11:00:46.211+01:00 INFO [async-dispatch-2] [o.q.i.StdSchedulerFactory] Quartz scheduler 'a5bac081-c72e-4658-90a6-b4afbc9df9a7' initialized from an externally provided properties instance. 2023-02-11T11:00:46.211+01:00 INFO [async-dispatch-2] [o.q.i.StdSchedulerFactory] Quartz scheduler version: 2.3.2 2023-02-11T11:00:46.211+01:00 INFO [async-dispatch-2] [o.q.c.QuartzScheduler] Scheduler a5bac081-c72e-4658-90a6-b4afbc9df9a7_$_NON_CLUSTERED started. 2023-02-11T11:00:46.214+01:00 INFO [async-dispatch-2] [p.t.s.w.jetty9-service] Initializing web server(s). 2023-02-11T11:00:46.244+01:00 INFO [async-dispatch-2] [p.t.s.s.status-service] Registering status callback functi
Re: [NEW] devel/pax-utils
On 2023/02/10 12:44, Frederic Cambus wrote: > Hi ports@, > > Here is a new port: devel/pax-utils I think it would be better not to package pspax, it requires procfs. Otherwise ok.
UPDATE: lighttpd 1.4.69
Here is an update to lighttpd 1.4.69. - 1.4.69 - 2023-02-10 * [meson] remove t/test_mod_evasive.c * [doc] remove references to removed modules * [cmake] add doc/CMakeLists.txt to dist tar ball (#3181) * [meson] add meson.build to install man pages (fixes #3181) * [meson] fix typo in sbindir * [core] update ls-hpack * [cmake] remove -I/usr/include/mysql for mysql.h (#3181) * [cmake] add -DWITH_LUA_VERSION= to specify lua ver (#3181) * [cmake] use mysql_config cflags and ldflags (#3181) * [cmake] do not link with fam if inotify or kqueue * [TLS] fix spurious warning trace (fixes #3182) * [multiple] codespell: correct spelling in comments * [multiple] spelling: github action check-spelling * [lemon] upgrade LEMON parser to SQLite maint ver * [build] modify arguments to updated LEMON parser * [core] build configparser.y w/ -Werror workarounds * [lemon] fix -Wpendantic warnings for bad casts * [core] avoid accept4() on ARM unless detected * [cmake] use CMAKE_CURRENT_SOURCE_DIR * [cmake] SERVER_SRC variable * [multiple] quiet some coverity false positives * [cmake] use LIGHTTPD_MODULES_DIR as relative path (fixes #3185) * [core] add missed h2 state transition (fixes #3186) * [core] remove cygwin O_NOFOLLOW workaround * [multiple] clang -Wstrict-prototypes for C2x * [core] reset SIGUSR1 to SIG_DFL before execve() * [mod_webdav] modify OPTIONS response if no db cfg * [mod_webdav] MOD_WEBDAV_BUILD_MINIMAL preproc opt * [core] pass fdn to fdevent_sched_close,_unregister * [core] disable sendfile() on TARGET_OS_IPHONE * [core] iOS does not provide netinet/tcp_fsm.h * [core] move headers to help isolate fdevent layer * [core] avoid select() FD_ISSET repeat on active fds * [core] gw_backend more precise backend env alloc * [core] fdevent_poll_poll avoid potential race * [tests] quickly exit tests/request.t if GET / fail * [tests] adjust outdated opt in tests/lighttpd.conf * [autotools] add mod_evhost to static build list * [autotools] skip modules build if LIGHTTPD_STATIC * [mod_cgi] cygwin supports CGI file I/O redirection * [mod_dirlisting] use fdevent_rename() wrapper * [core] path-info in debug trace may be unset * [core] reset path-info for cgi.local-redir * [autotools] fix typo in -I used --with-pcre2=/path (fixes #3190) * [mod_webdav] send 409 Conflict if PUT miss parent * [core] fix HTTP/2 HEADERS frame parsing bug * [core] remove extra HTTP/2 HEADERS frame len check Index: Makefile === RCS file: /home/cvs/ports/www/lighttpd/Makefile,v retrieving revision 1.175 diff -u -p -u -p -r1.175 Makefile --- Makefile15 Jan 2023 08:06:22 - 1.175 +++ Makefile11 Feb 2023 03:55:02 - @@ -1,7 +1,6 @@ COMMENT= secure, fast, compliant, and very flexible web-server -DISTNAME= lighttpd-1.4.68 -REVISION= 1 +DISTNAME= lighttpd-1.4.69 CATEGORIES=www net MASTER_SITES= https://download.lighttpd.net/lighttpd/releases-1.4.x/ EXTRACT_SUFX= .tar.xz Index: distinfo === RCS file: /home/cvs/ports/www/lighttpd/distinfo,v retrieving revision 1.71 diff -u -p -u -p -r1.71 distinfo --- distinfo7 Jan 2023 11:30:39 - 1.71 +++ distinfo11 Feb 2023 03:51:18 - @@ -1,2 +1,2 @@ -SHA256 (lighttpd-1.4.68.tar.xz) = 5W83rlK2PhraTXbOeABa/7blbuova9sM4X1tNulYM4Q= -SIZE (lighttpd-1.4.68.tar.xz) = 1030612 +SHA256 (lighttpd-1.4.69.tar.xz) = FqyNuV5xlim6YZSbmfiib+upRqgdGFIVsoN5u0EWsLQ= +SIZE (lighttpd-1.4.69.tar.xz) = 1045516 Index: patches/patch-doc_CMakeLists_txt === RCS file: patches/patch-doc_CMakeLists_txt diff -N patches/patch-doc_CMakeLists_txt --- patches/patch-doc_CMakeLists_txt7 Jan 2023 11:30:39 - 1.1 +++ /dev/null 1 Jan 1970 00:00:00 - @@ -1,11 +0,0 @@ -[cmake] add doc/CMakeLists.txt to dist tar ball (#3181) -da8abbfad414f2f8078e0b50302d691f8b21bbe0 - -Index: doc/CMakeLists.txt doc/CMakeLists.txt.orig -+++ doc/CMakeLists.txt -@@ -0,0 +1,4 @@ -+install(FILES -+ lighttpd.8 -+ lighttpd-angel.8 -+ DESTINATION ${CMAKE_INSTALL_MANDIR}/man8) Index: patches/patch-src_CMakeLists_txt === RCS file: patches/patch-src_CMakeLists_txt diff -N patches/patch-src_CMakeLists_txt --- patches/patch-src_CMakeLists_txt15 Jan 2023 08:06:22 - 1.2 +++ /dev/null 1 Jan 1970 00:00:00 - @@ -1,91 +0,0 @@ -- [cmake] remove -I/usr/include/mysql for mysql.h (#3181) - 6ea696d1113e38ac2639074ba50b72e6a0180959 -- [cmake] add -DWITH_LUA_VERSION= to specify lua ver (#3181) - 84b4ccf89bdfa5817f1ec6328550cc7e3f52cbac -- [cmake] use mysql_config cflags and ldflags (#3181) - cc0bb8aa00c321d86a75a7f8138b4f783bac1bf3 -- [cmake] use LIGHTTPD_MODULES_DIR as relative path (fixes #3185) - 5bb8cbdc110ce9f8c4617c2130234d
Re: [NEW] devel/pax-utils
On 23/02/10 12:44PM, Frederic Cambus wrote: > Originally focused only on PaX, it has been expanded to be generally > security focused. It still has a good number of PaX helpers for people > interested in that. > This has been very useful for analyzing elf files even for non security usage, I used it as a better objdump. the result looks accurate and I'm happy to have it here on OpenBSD.
-current rspamd hyperscan error
Hello, with a snapshot from yesterday: OpenBSD 7.2-current (GENERIC.MP) #1029: Fri Feb 10 09:16:50 MST 2023 and a -current rspamd: rspamd-3.4p1-hyperscan event-driven spam filtering system in C/Lua I get the following error upon starting rspamd: rspamd_multipattern_compile: fatal error: cannot allocate scratch space for hyperscan: -1 There are no changes to rspamd limits via login.conf[.d/*]. Setting "disable_hyperscan = true;" in /etc/rspamd/local.d/options.inc (as found on the interwebs) did not change a thing. Can anyone confirm? Does anyone have a workaround? Thanks, Marcus OpenBSD 7.2-current (GENERIC.MP) #1029: Fri Feb 10 09:16:50 MST 2023 dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP real mem = 16898199552 (16115MB) avail mem = 16366690304 (15608MB) random: good seed from bootblocks mpath0 at root scsibus0 at mpath0: 256 targets mainbus0 at root bios0 at mainbus0: SMBIOS rev. 3.2 @ 0x8f7ff000 (94 entries) bios0: vendor American Megatrends Inc. version "2.02" date 12/14/2021 bios0: Shuttle Inc. DS20U efi0 at bios0: UEFI 2.7 efi0: American Megatrends rev 0x50011 acpi0 at bios0: ACPI 6.2 acpi0: sleep states S0 S3 S4 S5 acpi0: tables DSDT FACP MCFG SSDT FIDT SSDT HPET SSDT SSDT NHLT LPIT SSDT SSDT DBGP DBG2 SSDT TPM2 DMAR WSMT APIC FPDT acpi0: wakeup devices RP01(S4) PXSX(S4) RP02(S4) PXSX(S4) RP03(S4) PXSX(S4) RP04(S4) PXSX(S4) RP05(S4) PXSX(S4) RP06(S4) PXSX(S4) RP07(S4) PXSX(S4) RP08(S4) PXSX(S4) [...] acpitimer0 at acpi0: 3579545 Hz, 24 bits acpimcfg0 at acpi0 acpimcfg0: addr 0xe000, bus 0-255 acpihpet0 at acpi0: 2399 Hz acpimadt0 at acpi0 addr 0xfee0: PC-AT compat cpu0 at mainbus0: apid 0 (boot processor) cpu0: Intel(R) Core(TM) i7-10510U CPU @ 1.80GHz, 1696.05 MHz, 06-8e-0c cpu0: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,EST,TM2,SSSE3,SDBG,FMA3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,RDTSCP,LONG,LAHF,ABM,3DNOWP,PERF,ITSC,FSGSBASE,TSC_ADJUST,SGX,BMI1,AVX2,SMEP,BMI2,ERMS,INVPCID,MPX,RDSEED,ADX,SMAP,CLFLUSHOPT,PT,SRBDS_CTRL,MD_CLEAR,IBRS,IBPB,STIBP,L1DF,SSBD,SENSOR,ARAT,XSAVEOPT,XSAVEC,XGETBV1,XSAVES cpu0: 32KB 64b/line 8-way D-cache, 32KB 64b/line 8-way I-cache, 256KB 64b/line 4-way L2 cache, 8MB 64b/line 16-way L3 cache cpu0: smt 0, core 0, package 0 mtrr: Pentium Pro MTRR support, 10 var ranges, 88 fixed ranges cpu0: apic clock running at 24MHz cpu0: mwait min=64, max=64, C-substates=0.2.1.2.4.1.1.1, IBE cpu1 at mainbus0: apid 2 (application processor) cpu1: Intel(R) Core(TM) i7-10510U CPU @ 1.80GHz, 1696.05 MHz, 06-8e-0c cpu1: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,EST,TM2,SSSE3,SDBG,FMA3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,RDTSCP,LONG,LAHF,ABM,3DNOWP,PERF,ITSC,FSGSBASE,TSC_ADJUST,SGX,BMI1,AVX2,SMEP,BMI2,ERMS,INVPCID,MPX,RDSEED,ADX,SMAP,CLFLUSHOPT,PT,SRBDS_CTRL,MD_CLEAR,IBRS,IBPB,STIBP,L1DF,SSBD,SENSOR,ARAT,XSAVEOPT,XSAVEC,XGETBV1,XSAVES cpu1: 32KB 64b/line 8-way D-cache, 32KB 64b/line 8-way I-cache, 256KB 64b/line 4-way L2 cache, 8MB 64b/line 16-way L3 cache cpu1: smt 0, core 1, package 0 cpu2 at mainbus0: apid 4 (application processor) cpu2: Intel(R) Core(TM) i7-10510U CPU @ 1.80GHz, 1696.05 MHz, 06-8e-0c cpu2: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,EST,TM2,SSSE3,SDBG,FMA3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,RDTSCP,LONG,LAHF,ABM,3DNOWP,PERF,ITSC,FSGSBASE,TSC_ADJUST,SGX,BMI1,AVX2,SMEP,BMI2,ERMS,INVPCID,MPX,RDSEED,ADX,SMAP,CLFLUSHOPT,PT,SRBDS_CTRL,MD_CLEAR,IBRS,IBPB,STIBP,L1DF,SSBD,SENSOR,ARAT,XSAVEOPT,XSAVEC,XGETBV1,XSAVES cpu2: 32KB 64b/line 8-way D-cache, 32KB 64b/line 8-way I-cache, 256KB 64b/line 4-way L2 cache, 8MB 64b/line 16-way L3 cache cpu2: smt 0, core 2, package 0 cpu3 at mainbus0: apid 6 (application processor) cpu3: Intel(R) Core(TM) i7-10510U CPU @ 1.80GHz, 1696.05 MHz, 06-8e-0c cpu3: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,EST,TM2,SSSE3,SDBG,FMA3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,RDTSCP,LONG,LAHF,ABM,3DNOWP,PERF,ITSC,FSGSBASE,TSC_ADJUST,SGX,BMI1,AVX2,SMEP,BMI2,ERMS,INVPCID,MPX,RDSEED,ADX,SMAP,CLFLUSHOPT,PT,SRBDS_CTRL,MD_CLEAR,IBRS,IBPB,STIBP,L1DF,SSBD,SENSOR,ARAT,XSAVEOPT,XSAVEC,XGETBV1,XSAVES cpu3: 32KB 64b/line 8-way D-cache, 32KB 64b/line 8-way I-cache, 256KB 64b/line 4-way L2 cache, 8MB 64b/line 16-way L3 cache cpu3: smt 0, core 3,
Re: amd64-clang bulk build report
On Sat, Feb 11, 2023 at 05:02:21AM +0100, Theo Buehler wrote: > My clang 15 ports queue is empty. Below is the list of remaining build > failures with some quick notes. Some of them still have obvious fixes. > Either there is a maintainer who can look or the ports involve languages > or build systems I don't enjoy dealing with. > > comms/pilot-link perl XS [-Wint-conversion] - still useful? I think this and comms/jpilot should be removed. -- Antoine
www/p5-Dancer2: Update to 0.400001
Hi, ports@: Here is a simple patch for www/p5-Dancer2 to update to 0.41. It build well and pass all tests on amd64-current system. Four ports depend on it, all build well and pass all tests too. Cheers ! wenIndex: www/p5-Dancer2/Makefile === RCS file: /cvs/ports/www/p5-Dancer2/Makefile,v retrieving revision 1.16 diff -u -p -r1.16 Makefile --- www/p5-Dancer2/Makefile 20 Mar 2022 22:22:31 - 1.16 +++ www/p5-Dancer2/Makefile 11 Feb 2023 07:39:38 - @@ -1,6 +1,6 @@ COMMENT = lightweight yet powerful web application framework -DISTNAME = Dancer2-0.40 +DISTNAME = Dancer2-0.41 CATEGORIES = www Index: www/p5-Dancer2/distinfo === RCS file: /cvs/ports/www/p5-Dancer2/distinfo,v retrieving revision 1.10 diff -u -p -r1.10 distinfo --- www/p5-Dancer2/distinfo 20 Mar 2022 22:22:31 - 1.10 +++ www/p5-Dancer2/distinfo 11 Feb 2023 07:39:38 - @@ -1,2 +1,2 @@ -SHA256 (Dancer2-0.40.tar.gz) = 5s96Xu0pJhCH0s5ttjHSi06HDLFPMcLfovd8AWO8Q1w= -SIZE (Dancer2-0.40.tar.gz) = 402506 +SHA256 (Dancer2-0.41.tar.gz) = nbV1vFBBP8GTmVaa0s+8UvtJ7XEV0DGUqQjZmJMEt0w= +SIZE (Dancer2-0.41.tar.gz) = 391249
Re: -current rspamd hyperscan error
Hello again, mcmer-open...@tor.at (Marcus MERIGHI), 2023.02.11 (Sat) 08:35 (CET): > Does anyone have a workaround? worked for me: $ pkg_delete rspamd-3.4p1-hyperscan $ pkg_add pkg_add rspamd-3.4p1 Marcus