[PATCH] aarch64: Add OpenBSD runtime detection of dotprod and i8mm using sysctl

2024-05-27 Thread Brad Smith
aarch64: Add OpenBSD runtime detection of dotprod and i8mm using sysctl

Signed-off-by: Brad Smith 
---
 libavutil/aarch64/cpu.c | 38 ++
 1 file changed, 38 insertions(+)

diff --git a/libavutil/aarch64/cpu.c b/libavutil/aarch64/cpu.c
index 196bdaf6b0..1ea2b94679 100644
--- a/libavutil/aarch64/cpu.c
+++ b/libavutil/aarch64/cpu.c
@@ -20,6 +20,10 @@
 #include "libavutil/cpu_internal.h"
 #include "config.h"
 
+#ifdef __OpenBSD__
+#include 
+#endif
+
 #if (defined(__linux__) || defined(__ANDROID__)) && HAVE_GETAUXVAL
 #include 
 #include 
@@ -65,6 +69,40 @@ static int detect_flags(void)
 return flags;
 }
 
+#elif defined(__OpenBSD__) && defined(CPU_ID_AA64ISAR0)
+#include 
+#include 
+#include 
+
+static int detect_flags(void)
+{
+int flags = 0;
+int mib[2];
+uint64_t isar0;
+uint64_t isar1;
+size_t len;
+
+mib[0] = CTL_MACHDEP;
+mib[1] = CPU_ID_AA64ISAR0;
+len = sizeof(isar0);
+if (sysctl(mib, 2, &isar0, &len, NULL, 0) != -1) {
+if (ID_AA64ISAR0_DP(isar0) >= ID_AA64ISAR0_DP_IMPL)
+flags |= AV_CPU_FLAG_DOTPROD;
+}
+
+mib[0] = CTL_MACHDEP;
+mib[1] = CPU_ID_AA64ISAR1;
+len = sizeof(isar1);
+if (sysctl(mib, 2, &isar1, &len, NULL, 0) != -1) {
+#ifdef ID_AA64ISAR1_I8MM_IMPL
+if (ID_AA64ISAR1_I8MM(isar1) >= ID_AA64ISAR1_I8MM_IMPL)
+flags |= AV_CPU_FLAG_I8MM;
+#endif
+}
+
+return flags;
+}
+
 #elif defined(_WIN32)
 #include 
 
-- 
2.45.1



Re: Enable OpenBSD NVMe disk support in smartmontools

2024-05-27 Thread Martin Ziemer
Am Sun, May 26, 2024 at 10:56:05AM -0400 schrieb Kenneth Westerback:
> The diff below enables smartmontools (smartctl & smartd) support for
> NVMe disks on -current kernels with the latest nvme(4) passthrough
> commits.
> 
> Obvious features tested and work for me on various amd64 boxes and my m1
> macmini.
> 
> ian@ has also succesfully tested it.
> 
> Thoughts? OK?
Works on my system as well. (Own only a single nvme driven box)

> --
>  Ken
> 
> Index: Makefile
> ===
> RCS file: /cvs/ports/sysutils/smartmontools/Makefile,v
> diff -u -p -u -p -r1.50 Makefile
> --- Makefile  27 Sep 2023 17:16:34 -  1.50
> +++ Makefile  26 May 2024 14:54:25 -
> @@ -2,6 +2,7 @@ COMMENT=  control and monitor storage sy
> 
>  # XXX at update time check whether C++11 is actually needed
>  DISTNAME=smartmontools-7.4
> +REVISION=0
>  CATEGORIES=  sysutils
> 
>  HOMEPAGE=https://www.smartmontools.org/
> Index: patches/patch-openbsd_nvme_ioctl_h
> ===
> RCS file: patches/patch-openbsd_nvme_ioctl_h
> diff -N patches/patch-openbsd_nvme_ioctl_h
> --- /dev/null 1 Jan 1970 00:00:00 -
> +++ patches/patch-openbsd_nvme_ioctl_h26 May 2024 14:54:25 -
> @@ -0,0 +1,78 @@
> +Index: openbsd_nvme_ioctl.h
> +--- openbsd_nvme_ioctl.h.orig
>  openbsd_nvme_ioctl.h
> +@@ -0,0 +1,74 @@
> ++/*
> ++ * Copyright (c) 2024 Kenneth R Westerback 
> ++ *
> ++ * Permission to use, copy, modify, and distribute this software for any
> ++ * purpose with or without fee is hereby granted, provided that the above
> ++ * copyright notice and this permission notice appear in all copies.
> ++ *
> ++ * THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES
> ++ * WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF
> ++ * MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR
> ++ * ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES
> ++ * WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN
> ++ * ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF
> ++ * OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE.
> ++ */
> ++
> ++#define NVME_PASSTHROUGH_CMD_IOWR('n', 0, struct 
> nvme_pt_cmd)
> ++
> ++struct nvme_pt_status {
> ++int ps_dv_unit;
> ++int ps_nsid;
> ++int ps_flags;
> ++#define NVME_CQE_SCT(_f)((_f) & (0x07 << 9))
> ++#define  NVME_CQE_SCT_GENERIC   (0x00 << 9)
> ++#define NVME_CQE_SC(_f) ((_f) & (0xff << 1))
> ++#define  NVME_CQE_SC_SUCCESS(0x00 << 1)
> ++uint32_tps_csts;
> ++uint32_tps_cc;
> ++};
> ++
> ++#define BIO_MSG_COUNT   5
> ++#define BIO_MSG_LEN 128
> ++
> ++struct bio_msg {
> ++int bm_type;
> ++charbm_msg[BIO_MSG_LEN];
> ++};
> ++
> ++struct bio_status {
> ++charbs_controller[16];
> ++int bs_status;
> ++int bs_msg_count;
> ++struct bio_msg  bs_msgs[BIO_MSG_COUNT];
> ++};
> ++
> ++struct bio {
> ++void*bio_cookie;
> ++struct bio_status   bio_status;
> ++};
> ++
> ++struct nvme_pt_cmd {
> ++/* Commands may arrive via /dev/bio. */
> ++struct bio  pt_bio;
> ++
> ++/* The sqe fields that the caller may specify. */
> ++uint8_t pt_opcode;
> ++uint32_tpt_nsid;
> ++uint32_tpt_cdw10;
> ++uint32_tpt_cdw11;
> ++uint32_tpt_cdw12;
> ++uint32_tpt_cdw13;
> ++uint32_tpt_cdw14;
> ++uint32_tpt_cdw15;
> ++
> ++caddr_t pt_status;
> ++uint32_tpt_statuslen;
> ++
> ++caddr_t pt_databuf; /* User space address. */
> ++uint32_tpt_databuflen;  /* Length of buffer. */
> ++};
> ++
> ++#define nvme_completion_is_error(_flags)
> \
> ++((NVME_CQE_SC(_flags) != NVME_CQE_SC_SUCCESS)   \
> ++|| (NVME_CQE_SCT(_flags) != NVME_CQE_SCT_GENERIC))
> Index: patches/patch-os_openbsd_cpp
> ===
> RCS file: patches/patch-os_openbsd_cpp
> diff -N patches/patch-os_openbsd_cpp
> --- /dev/null 1 Jan 1970 00:00:00 -
> +++ patches/patch-os_openbsd_cpp  26 May 2024 14:54:25 -
> @@ -0,0 +1,196 @@
> +Index: os_openbsd.cpp
> +--- os_openbsd.cpp.orig
>  os_openbsd.cpp
> +@@ -14,6 +14,7 @@
> +
> + #include "atacmds.h"
> + #include "scsicmds.h"
> ++#include "nvmecmds.h"
> + #include "utility.h"
> + #include "os_openbsd.h"
> +
> +@@ -22,11 +23,29 @@
> + #include 
> + #include 
> +
> +

Fix conflicts between kf6-kaccounts-integration and kaccounts-integration

2024-05-27 Thread Rafael Sadowski
I have seen this conflict and hope the following diff fixes the problem.

Collision in kf6-kaccounts-integration-24.02.1: the following files already 
exist
/usr/local/share/applications/kcm_kaccounts.desktop 
(kaccounts-integration-23.08.4 and kf6-kaccounts-integration-24.02.1)
/usr/local/share/locale/ar/LC_MESSAGES/kaccounts-integration.mo 
(kaccounts-integration-23.08.4 and kf6-kaccounts-integration-24.02.1)

Feedback, ok?

Index: Makefile
===
RCS file: /cvs/ports/x11/kde-applications/kf6-kaccounts-integration/Makefile,v
diff -u -p -r1.3 Makefile
--- Makefile20 May 2024 06:38:56 -  1.3
+++ Makefile27 May 2024 09:01:10 -
@@ -2,6 +2,7 @@ COMMENT =   library and QML module for Acc

 DISTNAME = kaccounts-integration-${VERSION}
 PKGNAME =  kf6-kaccounts-integration-${VERSION}
+REVISION = 0

 CATEGORIES =   net devel

Index: pkg/PLIST
===
RCS file: /cvs/ports/x11/kde-applications/kf6-kaccounts-integration/pkg/PLIST,v
diff -u -p -r1.1.1.1 PLIST
--- pkg/PLIST   16 Apr 2024 19:30:14 -  1.1.1.1
+++ pkg/PLIST   27 May 2024 09:01:10 -
@@ -1,3 +1,4 @@
+@conflict kaccounts-integration-<=24.02.1
 include/KAccounts6/
 include/KAccounts6/KAccounts/
 include/KAccounts6/KAccounts/AccountServiceToggleJob



Re: [Update] www/gallery-dl-1.26.9

2024-05-27 Thread grodzio
bump



update www/yt-dlp

2024-05-27 Thread Solene Rapenne
newer version of yt-dlp

https://github.com/yt-dlp/yt-dlp/releases/tag/2024.05.26

tested on amd64 with vanilla software and with pipe-viewer

diff --git a/www/yt-dlp/Makefile b/www/yt-dlp/Makefile
index 92e2621c411..5ae906b8c44 100644
--- a/www/yt-dlp/Makefile
+++ b/www/yt-dlp/Makefile
@@ -1,11 +1,10 @@
 COMMENT =  CLI program to download videos from YouTube and other sites
 
-VERSION =  2024.04.09
+VERSION =  2024.05.26
 MODPY_EGG_VERSION =${VERSION:S/.0/./g}
 
 DISTNAME = yt-dlp-${VERSION}
 DISTFILES =yt-dlp-${VERSION}{yt-dlp}${EXTRACT_SUFX}
-REVISION = 0
 
 CATEGORIES =   www
 
diff --git a/www/yt-dlp/distinfo b/www/yt-dlp/distinfo
index 8b47e72d35d..c2ba0c2193a 100644
--- a/www/yt-dlp/distinfo
+++ b/www/yt-dlp/distinfo
@@ -1,2 +1,2 @@
-SHA256 (yt-dlp-2024.04.09.tar.gz) = 
WdPK7VzImeSGp7iHP2FDtqHSLFtcBQCbcJygEE9dnu0=
-SIZE (yt-dlp-2024.04.09.tar.gz) = 5589808
+SHA256 (yt-dlp-2024.05.26.tar.gz) = 
GNwmOO+VDjzjVaXVLp4C0p6SsH1BDb4Zf4kPGipcPCc=
+SIZE (yt-dlp-2024.05.26.tar.gz) = 5638226
diff --git a/www/yt-dlp/pkg/PLIST b/www/yt-dlp/pkg/PLIST
index b2f4d61d9b6..e0531eddc3d 100644
--- a/www/yt-dlp/pkg/PLIST
+++ b/www/yt-dlp/pkg/PLIST
@@ -370,8 +370,8 @@ 
lib/python${MODPY_VERSION}/site-packages/yt_dlp/extractor/${MODPY_PYCACHE}byutv.
 
lib/python${MODPY_VERSION}/site-packages/yt_dlp/extractor/${MODPY_PYCACHE}byutv.${MODPY_PYC_MAGIC_TAG}pyc
 
lib/python${MODPY_VERSION}/site-packages/yt_dlp/extractor/${MODPY_PYCACHE}c56.${MODPY_PYC_MAGIC_TAG}${MODPY_PYOEXTENSION}
 
lib/python${MODPY_VERSION}/site-packages/yt_dlp/extractor/${MODPY_PYCACHE}c56.${MODPY_PYC_MAGIC_TAG}pyc
-lib/python${MODPY_VERSION}/site-packages/yt_dlp/extractor/${MODPY_PYCACHE}cableav.${MODPY_PYC_MAGIC_TAG}${MODPY_PYOEXTENSION}
-lib/python${MODPY_VERSION}/site-packages/yt_dlp/extractor/${MODPY_PYCACHE}cableav.${MODPY_PYC_MAGIC_TAG}pyc
+lib/python${MODPY_VERSION}/site-packages/yt_dlp/extractor/${MODPY_PYCACHE}caffeinetv.${MODPY_PYC_MAGIC_TAG}${MODPY_PYOEXTENSION}
+lib/python${MODPY_VERSION}/site-packages/yt_dlp/extractor/${MODPY_PYCACHE}caffeinetv.${MODPY_PYC_MAGIC_TAG}pyc
 
lib/python${MODPY_VERSION}/site-packages/yt_dlp/extractor/${MODPY_PYCACHE}callin.${MODPY_PYC_MAGIC_TAG}${MODPY_PYOEXTENSION}
 
lib/python${MODPY_VERSION}/site-packages/yt_dlp/extractor/${MODPY_PYCACHE}callin.${MODPY_PYC_MAGIC_TAG}pyc
 
lib/python${MODPY_VERSION}/site-packages/yt_dlp/extractor/${MODPY_PYCACHE}caltrans.${MODPY_PYC_MAGIC_TAG}${MODPY_PYOEXTENSION}
@@ -524,6 +524,8 @@ 
lib/python${MODPY_VERSION}/site-packages/yt_dlp/extractor/${MODPY_PYCACHE}dailyw
 
lib/python${MODPY_VERSION}/site-packages/yt_dlp/extractor/${MODPY_PYCACHE}dailywire.${MODPY_PYC_MAGIC_TAG}pyc
 
lib/python${MODPY_VERSION}/site-packages/yt_dlp/extractor/${MODPY_PYCACHE}damtomo.${MODPY_PYC_MAGIC_TAG}${MODPY_PYOEXTENSION}
 
lib/python${MODPY_VERSION}/site-packages/yt_dlp/extractor/${MODPY_PYCACHE}damtomo.${MODPY_PYC_MAGIC_TAG}pyc
+lib/python${MODPY_VERSION}/site-packages/yt_dlp/extractor/${MODPY_PYCACHE}dangalplay.${MODPY_PYC_MAGIC_TAG}${MODPY_PYOEXTENSION}
+lib/python${MODPY_VERSION}/site-packages/yt_dlp/extractor/${MODPY_PYCACHE}dangalplay.${MODPY_PYC_MAGIC_TAG}pyc
 
lib/python${MODPY_VERSION}/site-packages/yt_dlp/extractor/${MODPY_PYCACHE}daum.${MODPY_PYC_MAGIC_TAG}${MODPY_PYOEXTENSION}
 
lib/python${MODPY_VERSION}/site-packages/yt_dlp/extractor/${MODPY_PYCACHE}daum.${MODPY_PYC_MAGIC_TAG}pyc
 
lib/python${MODPY_VERSION}/site-packages/yt_dlp/extractor/${MODPY_PYCACHE}daystar.${MODPY_PYC_MAGIC_TAG}${MODPY_PYOEXTENSION}
@@ -602,8 +604,6 @@ 
lib/python${MODPY_VERSION}/site-packages/yt_dlp/extractor/${MODPY_PYCACHE}egghea
 
lib/python${MODPY_VERSION}/site-packages/yt_dlp/extractor/${MODPY_PYCACHE}egghead.${MODPY_PYC_MAGIC_TAG}pyc
 
lib/python${MODPY_VERSION}/site-packages/yt_dlp/extractor/${MODPY_PYCACHE}eighttracks.${MODPY_PYC_MAGIC_TAG}${MODPY_PYOEXTENSION}
 
lib/python${MODPY_VERSION}/site-packages/yt_dlp/extractor/${MODPY_PYCACHE}eighttracks.${MODPY_PYC_MAGIC_TAG}pyc
-lib/python${MODPY_VERSION}/site-packages/yt_dlp/extractor/${MODPY_PYCACHE}einthusan.${MODPY_PYC_MAGIC_TAG}${MODPY_PYOEXTENSION}
-lib/python${MODPY_VERSION}/site-packages/yt_dlp/extractor/${MODPY_PYCACHE}einthusan.${MODPY_PYC_MAGIC_TAG}pyc
 
lib/python${MODPY_VERSION}/site-packages/yt_dlp/extractor/${MODPY_PYCACHE}eitb.${MODPY_PYC_MAGIC_TAG}${MODPY_PYOEXTENSION}
 
lib/python${MODPY_VERSION}/site-packages/yt_dlp/extractor/${MODPY_PYCACHE}eitb.${MODPY_PYC_MAGIC_TAG}pyc
 
lib/python${MODPY_VERSION}/site-packages/yt_dlp/extractor/${MODPY_PYCACHE}elementorembed.${MODPY_PYC_MAGIC_TAG}${MODPY_PYOEXTENSION}
@@ -734,6 +734,8 @@ 
lib/python${MODPY_VERSION}/site-packages/yt_dlp/extractor/${MODPY_PYCACHE}gaskra
 
lib/python${MODPY_VERSION}/site-packages/yt_dlp/extractor/${MODPY_PYCACHE}gaskrank.${MODPY_PYC_MAGIC_TAG}pyc
 
lib/python${MODPY_VERSION}/site-packages/yt_dlp/extractor/${MODPY_PYCACHE}gazeta.${MODPY_PYC_MAGIC_TAG}${MODPY_PYOEXTENSION}
 
lib/python${MODPY_VERSION}/site-packages/yt_dlp/extractor/${MODPY_PYCACHE}ga

Re: Fix conflicts between kf6-kaccounts-integration and kaccounts-integration

2024-05-27 Thread Stuart Henderson
On 2024/05/27 11:03, Rafael Sadowski wrote:
> I have seen this conflict and hope the following diff fixes the problem.

That just registers the conflict. But you have one port depending on
kf6-kaccounts-integration and several depending on kaccounts-integration
at build time so you'll need to actually de-conflict them somehow (e.g.
renaming the files or something) otherwise it will occasionally break
in bulk builds.

> Collision in kf6-kaccounts-integration-24.02.1: the following files already 
> exist
> /usr/local/share/applications/kcm_kaccounts.desktop 
> (kaccounts-integration-23.08.4 and kf6-kaccounts-integration-24.02.1)
> /usr/local/share/locale/ar/LC_MESSAGES/kaccounts-integration.mo 
> (kaccounts-integration-23.08.4 and kf6-kaccounts-integration-24.02.1)
> 
> Feedback, ok?
> 
> Index: Makefile
> ===
> RCS file: /cvs/ports/x11/kde-applications/kf6-kaccounts-integration/Makefile,v
> diff -u -p -r1.3 Makefile
> --- Makefile  20 May 2024 06:38:56 -  1.3
> +++ Makefile  27 May 2024 09:01:10 -
> @@ -2,6 +2,7 @@ COMMENT = library and QML module for Acc
> 
>  DISTNAME =   kaccounts-integration-${VERSION}
>  PKGNAME =kf6-kaccounts-integration-${VERSION}
> +REVISION =   0
> 
>  CATEGORIES = net devel
> 
> Index: pkg/PLIST
> ===
> RCS file: 
> /cvs/ports/x11/kde-applications/kf6-kaccounts-integration/pkg/PLIST,v
> diff -u -p -r1.1.1.1 PLIST
> --- pkg/PLIST 16 Apr 2024 19:30:14 -  1.1.1.1
> +++ pkg/PLIST 27 May 2024 09:01:10 -
> @@ -1,3 +1,4 @@
> +@conflict kaccounts-integration-<=24.02.1
>  include/KAccounts6/
>  include/KAccounts6/KAccounts/
>  include/KAccounts6/KAccounts/AccountServiceToggleJob
> 



Re: Fix conflicts between kf6-kaccounts-integration and kaccounts-integration

2024-05-27 Thread Rafael Sadowski
On Mon May 27, 2024 at 03:52:40PM GMT, Stuart Henderson wrote:
> On 2024/05/27 11:03, Rafael Sadowski wrote:
> > I have seen this conflict and hope the following diff fixes the problem.
> 
> That just registers the conflict. But you have one port depending on
> kf6-kaccounts-integration and several depending on kaccounts-integration
> at build time so you'll need to actually de-conflict them somehow (e.g.
> renaming the files or something) otherwise it will occasionally break
> in bulk builds.

They are de-conflict. kaccounts-integration-24.02.1 and
kf6-kaccounts-integration-24.02.1 can be installed at the same time.

This message appears while “pkg_add -u”. kaccounts-integration-23.08.4
is still installed and needs to be updated to
kaccounts-integration-24.02.1.

It's a bit confusing with "kf6-" and without.

> 
> > Collision in kf6-kaccounts-integration-24.02.1: the following files already 
> > exist
> > /usr/local/share/applications/kcm_kaccounts.desktop 
> > (kaccounts-integration-23.08.4 and kf6-kaccounts-integration-24.02.1)
> > /usr/local/share/locale/ar/LC_MESSAGES/kaccounts-integration.mo 
> > (kaccounts-integration-23.08.4 and kf6-kaccounts-integration-24.02.1)
> > 
> > Feedback, ok?
> > 
> > Index: Makefile
> > ===
> > RCS file: 
> > /cvs/ports/x11/kde-applications/kf6-kaccounts-integration/Makefile,v
> > diff -u -p -r1.3 Makefile
> > --- Makefile20 May 2024 06:38:56 -  1.3
> > +++ Makefile27 May 2024 09:01:10 -
> > @@ -2,6 +2,7 @@ COMMENT =   library and QML module for Acc
> > 
> >  DISTNAME = kaccounts-integration-${VERSION}
> >  PKGNAME =  kf6-kaccounts-integration-${VERSION}
> > +REVISION = 0
> > 
> >  CATEGORIES =   net devel
> > 
> > Index: pkg/PLIST
> > ===
> > RCS file: 
> > /cvs/ports/x11/kde-applications/kf6-kaccounts-integration/pkg/PLIST,v
> > diff -u -p -r1.1.1.1 PLIST
> > --- pkg/PLIST   16 Apr 2024 19:30:14 -  1.1.1.1
> > +++ pkg/PLIST   27 May 2024 09:01:10 -
> > @@ -1,3 +1,4 @@
> > +@conflict kaccounts-integration-<=24.02.1
> >  include/KAccounts6/
> >  include/KAccounts6/KAccounts/
> >  include/KAccounts6/KAccounts/AccountServiceToggleJob
> > 



[New] lang/nelua

2024-05-27 Thread Nicolas Sampaio
Hi,

home: https://nelua.io/

comment: programming language with a lua flavor.

descr: Nelua is a minimal, statically-typed and meta-programmable
systems programming language heavily inspired by Lua, which compiles to C and 
native code.

I'm open to suggestions.

Reis


nelua-lang-20240113.tgz
Description: nelua-lang-20240113.tgz


Re: [New] lang/nelua

2024-05-27 Thread Brian Callahan
Hello Nicolas --

On 5/27/2024 11:51 AM, Nicolas Sampaio wrote:
> Hi,
> 
> home: https://nelua.io/ 
> 
> comment: programming language with a lua flavor.
> 
> descr: Nelua is a minimal, statically-typed and meta-programmable 
> systems programming language heavily inspired by Lua, which compiles to
> C and native code.
> 
> I'm open to suggestions.
> 
> Reis
As a step in the right direction, how about the attached version?

The tests results:
[] runner | 9 successes / 8 failures / 0.174995 seconds
385 successes / 0 skipped / 123 failures / 8.737528 seconds

And all the failures look the same; my guess is if you can fix this all
the tests will pass:
./spec/tools/expect.lua:121: expected success status in run:
...a-20240113/nelua-lang-20240113/lualib/nelua/utils/fs.lua:174: attempt
to index a nil value (local 'p')
stack traceback:
...a-20240113/nelua-lang-20240113/lualib/nelua/utils/fs.lua:174:
in function 'nelua.utils.fs.abspath'
...a-20240113/nelua-lang-20240113/lualib/nelua/utils/fs.lua:297:
in function 'nelua.utils.fs.makepath'
...a-20240113/nelua-lang-20240113/lualib/nelua/utils/fs.lua:305:
in function 'nelua.utils.fs.makepath'
...a-20240113/nelua-lang-20240113/lualib/nelua/utils/fs.lua:305:
in function 'nelua.utils.fs.makepath'
...a-20240113/nelua-lang-20240113/lualib/nelua/utils/fs.lua:305:
in function 'nelua.utils.fs.makepath'
...a-20240113/nelua-lang-20240113/lualib/nelua/utils/fs.lua:305:
in function 'nelua.utils.fs.makepath'
...a-20240113/nelua-lang-20240113/lualib/nelua/utils/fs.lua:321:
in function 'nelua.utils.fs.makefile'
...-20240113/nelua-lang-20240113/lualib/nelua/ccompiler.lua:292:
in function 'nelua.ccompiler.compile_code'
...lua-20240113/nelua-lang-20240113/lualib/nelua/runner.lua:229:
in upvalue 'run'
...lua-20240113/nelua-lang-20240113/lualib/nelua/runner.lua:262:
in function
<...lua-20240113/nelua-lang-20240113/lualib/nelua/runner.lua:261>
... (skipping 3 levels)
./spec/tools/expect.lua:100: in upvalue 'run'
./spec/tools/expect.lua:120: in function 'spec.tools.expect.run'
./spec/runner_spec.lua:186: in function <./spec/runner_spec.lua:185>
[C]: in function 'xpcall'
(...lester...)



stack traceback:
[C]: in function 'error'
...40113/nelua-lang-20240113/lualib/nelua/utils/errorer.lua:15:
in function 'nelua.utils.errorer.assertf'
./spec/tools/expect.lua:121: in function 'spec.tools.expect.run'
./spec/runner_spec.lua:186: in function <./spec/runner_spec.lua:185>
[C]: in function 'xpcall'
...3/nelua-lang-20240113/lualib/nelua/thirdparty/lester.lua:309:
in function 'nelua.thirdparty.lester.it'
./spec/runner_spec.lua:185: in local 'func'
...3/nelua-lang-20240113/lualib/nelua/thirdparty/lester.lua:214:
in function 'nelua.thirdparty.lester.describe'
./spec/runner_spec.lua:10: in main chunk
[C]: in function 'require'
spec/init.lua:19: in main chunk
[C]: in ?

~Brian


nelua.tgz
Description: application/compressed


Re: Fix conflicts between kf6-kaccounts-integration and kaccounts-integration

2024-05-27 Thread Stuart Henderson
On 2024/05/27 17:02, Rafael Sadowski wrote:
> On Mon May 27, 2024 at 03:52:40PM GMT, Stuart Henderson wrote:
> > On 2024/05/27 11:03, Rafael Sadowski wrote:
> > > I have seen this conflict and hope the following diff fixes the problem.
> > 
> > That just registers the conflict. But you have one port depending on
> > kf6-kaccounts-integration and several depending on kaccounts-integration
> > at build time so you'll need to actually de-conflict them somehow (e.g.
> > renaming the files or something) otherwise it will occasionally break
> > in bulk builds.
> 
> They are de-conflict. kaccounts-integration-24.02.1 and
> kf6-kaccounts-integration-24.02.1 can be installed at the same time.

Ah, I see.

> > > --- pkg/PLIST 16 Apr 2024 19:30:14 -  1.1.1.1
> > > +++ pkg/PLIST 27 May 2024 09:01:10 -
> > > @@ -1,3 +1,4 @@
> > > +@conflict kaccounts-integration-<=24.02.1

I'm not entirely sure what is matched regarding revisions when you just
use a plain version number, so I would use this as it's unambiguous:

@conflict kaccounts-integration-<24.02.1p0

with that, OK



Re: Remove: x11/lightly

2024-05-27 Thread Rafael Sadowski
On Tue May 21, 2024 at 01:57:08PM GMT, Rafael Sadowski wrote:
> Ok to remove Lightly?Lightly is no longer building and is for Plasma 5,
> which is now gone.
> 
> It looks quite dead upstream https://github.com/Luwx/Lightly/issues/224
> 
> There are alternatives, if you really need it you can port it.
> 

It is now marked as BROKEN. However I still looking for OK to remove it.



Re: Remove: x11/lightly

2024-05-27 Thread Jeremie Courreges-Anglas
On Mon, May 27, 2024 at 08:15:22PM +0200, Rafael Sadowski wrote:
> On Tue May 21, 2024 at 01:57:08PM GMT, Rafael Sadowski wrote:
> > Ok to remove Lightly?Lightly is no longer building and is for Plasma 5,
> > which is now gone.
> > 
> > It looks quite dead upstream https://github.com/Luwx/Lightly/issues/224
> > 
> > There are alternatives, if you really need it you can port it.
> > 
> 
> It is now marked as BROKEN. However I still looking for OK to remove it.

Sure.

-- 
jca



Re: [NEW] mail/s-dkim-sign: postfix-only DKIM sign-only milter

2024-05-27 Thread Steffen Nurpmeso
Hello!

Steffen Nurpmeso wrote in
 <20240519001518.RRjqW3iq@steffen%sdaoden.eu>:
 ...
 |+DISTNAME=s-dkim-sign-0.6.1

Please do not commit this port, in case you think about it!

After a month i finally got through and could see its Coverity.com
scan defects, and there is an issue with --client IPs with CIDR
mask.  I will have to release v0.6.2 on the 30th.

(Btw clang's scan-build only had shown four false positives; i do
have it and analyzers, but nothing from -extra, luckily one can
simply not unpack the extra ball to get through to this state.
Coverity has two false positives, and a hammer (false copy+paste
from another program).)

Thank you!!

--steffen
|
|Der Kragenbaer,The moon bear,
|der holt sich munter   he cheerfully and one by one
|einen nach dem anderen runter  wa.ks himself off
|(By Robert Gernhardt)



Re: [New] lang/nelua

2024-05-27 Thread Nicolas Sampaio
this version works smoothly

From: Brian Callahan 
Sent: Monday, May 27, 2024 1:19 PM
To: Nicolas Sampaio ; ports@openbsd.org 

Subject: Re: [New] lang/nelua

Hello Nicolas --

On 5/27/2024 11:51 AM, Nicolas Sampaio wrote:
> Hi,
>
> home: https://nelua.io/ 
>
> comment: programming language with a lua flavor.
>
> descr: Nelua is a minimal, statically-typed and meta-programmable
> systems programming language heavily inspired by Lua, which compiles to
> C and native code.
>
> I'm open to suggestions.
>
> Reis
As a step in the right direction, how about the attached version?

The tests results:
[] runner | 9 successes / 8 failures / 0.174995 seconds
385 successes / 0 skipped / 123 failures / 8.737528 seconds

And all the failures look the same; my guess is if you can fix this all
the tests will pass:
./spec/tools/expect.lua:121: expected success status in run:
...a-20240113/nelua-lang-20240113/lualib/nelua/utils/fs.lua:174: attempt
to index a nil value (local 'p')
stack traceback:
...a-20240113/nelua-lang-20240113/lualib/nelua/utils/fs.lua:174:
in function 'nelua.utils.fs.abspath'
...a-20240113/nelua-lang-20240113/lualib/nelua/utils/fs.lua:297:
in function 'nelua.utils.fs.makepath'
...a-20240113/nelua-lang-20240113/lualib/nelua/utils/fs.lua:305:
in function 'nelua.utils.fs.makepath'
...a-20240113/nelua-lang-20240113/lualib/nelua/utils/fs.lua:305:
in function 'nelua.utils.fs.makepath'
...a-20240113/nelua-lang-20240113/lualib/nelua/utils/fs.lua:305:
in function 'nelua.utils.fs.makepath'
...a-20240113/nelua-lang-20240113/lualib/nelua/utils/fs.lua:305:
in function 'nelua.utils.fs.makepath'
...a-20240113/nelua-lang-20240113/lualib/nelua/utils/fs.lua:321:
in function 'nelua.utils.fs.makefile'
...-20240113/nelua-lang-20240113/lualib/nelua/ccompiler.lua:292:
in function 'nelua.ccompiler.compile_code'
...lua-20240113/nelua-lang-20240113/lualib/nelua/runner.lua:229:
in upvalue 'run'
...lua-20240113/nelua-lang-20240113/lualib/nelua/runner.lua:262:
in function
<...lua-20240113/nelua-lang-20240113/lualib/nelua/runner.lua:261>
... (skipping 3 levels)
./spec/tools/expect.lua:100: in upvalue 'run'
./spec/tools/expect.lua:120: in function 'spec.tools.expect.run'
./spec/runner_spec.lua:186: in function <./spec/runner_spec.lua:185>
[C]: in function 'xpcall'
(...lester...)



stack traceback:
[C]: in function 'error'
...40113/nelua-lang-20240113/lualib/nelua/utils/errorer.lua:15:
in function 'nelua.utils.errorer.assertf'
./spec/tools/expect.lua:121: in function 'spec.tools.expect.run'
./spec/runner_spec.lua:186: in function <./spec/runner_spec.lua:185>
[C]: in function 'xpcall'
...3/nelua-lang-20240113/lualib/nelua/thirdparty/lester.lua:309:
in function 'nelua.thirdparty.lester.it'
./spec/runner_spec.lua:185: in local 'func'
...3/nelua-lang-20240113/lualib/nelua/thirdparty/lester.lua:214:
in function 'nelua.thirdparty.lester.describe'
./spec/runner_spec.lua:10: in main chunk
[C]: in function 'require'
spec/init.lua:19: in main chunk
[C]: in ?

~Brian


nelua.tgz
Description: nelua.tgz


Re: NEW: x11/emwm & x11/emwm-utils, clarification wanted.

2024-05-27 Thread izder456
On Fri, 12 Apr 2024 23:44:45 -0500
izder456  wrote:

> Hello ports@,
> 
> I initially made a thread in this list around the time 7.5 was nearing
> release, and the thread went stagnant, I assume since focus was on
> stability, and whatever. (might be misremembering here, I have a
> spotty memory).
> 
> See threads:
> x11/emwm => https://marc.info/?t=17055468082&r=1&w=2 
> x11/emwm-utils => https://marc.info/?t=17056918761&r=1&w=2
> 
> The only criticism I got aside from nits and tips on DISTFILES, seemed
> to come from a place of the quality of upstream code, which is fair if
> you are discussing comparing it to motif or whatever, but doesn't seem
> to be a reason against merging this. I use this WM quite frequently
> as a fallback. It would be personally nice to have. 
> 
> But some of the reasons I see this being beneficial to merge: 
> 
> Its the same legacy that motif wm has, but with modern niceties.
> fullscreen firefox/chromium is handled as expected, EWMH hints are
> respected, (so if you use a compositor or something), XFT font
> support is a biggie imho, thats one of the selling points for me. And
> emwm-utils has a nice toolchest application that is just nice to
> use/configure.
> 
> Hell- I made some personal config backups on my Github profile, cos
> its just a nice floating WM.
> 
> I know that necro-bumps are generally discouraged online- so heres a
> thread to ask this:
> 
> now that 7.5 is released, would this be good to merge into -CURRENT?
> 
> They are both attached.
> 
> Thoughts?
> 
> Thanks.
> 

It has been over a month now, and I'm still interested in merging this.

soz for the *BUMP*.

Thanks.

-- 
-iz (they/them)

> i like to say mundane things, 
> there are too many uninteresting things 
> that go unnoticed.

izder456 (dot) neocities (dot) org



Re: NEW: x11/emwm & x11/emwm-utils, clarification wanted.

2024-05-27 Thread izder456
On Mon, 27 May 2024 17:32:48 -0500
izder456  wrote:
> 
> It has been over a month now, and I'm still interested in merging
> this.
> 
> soz for the *BUMP*.
> 
> Thanks.
> 

Please commit... Thanks.

Its appreciated.

-- 
-iz (they/them)

> i like to say mundane things, 
> there are too many uninteresting things 
> that go unnoticed.

izder456 (dot) neocities (dot) org



Re: NEW: games/classicube

2024-05-27 Thread izder456
On Sun, 26 May 2024 12:04:51 -0500
izder456  wrote:

> On Fri, 24 May 2024 22:24:20 -0500
> izder456  wrote:
> 
> > On Thu, 2 May 2024 12:39:10 -0400
> > Thomas Frohwein  wrote:  
> > > So what was the reason for your earlier Error 2 when starting
> > > game? 
> > 
> > Gonna go on a whim here, but I suspect it has something to do with
> > failed resource loading.
> > 
> > Since this thread is stagnant and my README more than explains how
> > to deal with this, is it OK to merge at the current status?
> > 
> > Thanks,
> >   
> 
> Decided it makes more sense to put classicube_run in
> ${TRUEPREFIX}/share/classicube to prevent accidental runs. (as a
> failsafe). I updated pkg/README and the do-install directive
> accordingly to incorporate this change.
> 
> OK to merge?
> 
> Attached is a diff with the above changes.
> 

Please commit... Thanks.

Its appreciated.

-- 
-iz (they/them)

> i like to say mundane things, 
> there are too many uninteresting things 
> that go unnoticed.

izder456 (dot) neocities (dot) org



Re: UPDATE: games/minetest to 5.8.0

2024-05-27 Thread izder456
On Sun, 26 May 2024 19:55:12 -0500
izder456  wrote:

> On Wed, 17 Apr 2024 03:52:48 -0600
> "Anthony J. Bentley"  wrote:
> > Here's an updated diff, which I'll commit in a few days unless
> > someone objects.  
> 
> Thanks for the diff.
> 
> Any update? I saw this wasn't committed yet. Figured I should "BUMP"
> you. :))
> 
> Thanks.
> 

Please commit... Thanks.

Its appreciated.

-- 
-iz (they/them)

> i like to say mundane things, 
> there are too many uninteresting things 
> that go unnoticed.

izder456 (dot) neocities (dot) org



UPDATE: net/tailscale-1.66.4

2024-05-27 Thread Adriano Barbosa
Hi.
Update for net/tailscale v1.66.3
Changelog:
https://github.com/tailscale/tailscale/releases/tag/v1.66.4

Obrigado!
--
Adriano


Index: Makefile
===
RCS file: /cvs/ports/net/tailscale/Makefile,v
retrieving revision 1.35
diff -u -p -r1.35 Makefile
--- Makefile21 May 2024 20:55:09 -  1.35
+++ Makefile27 May 2024 23:30:27 -
@@ -2,7 +2,7 @@ BROKEN-i386 =   unix.EPROTO not defined
 
 COMMENT =  modern overlay-like VPN built on top of WireGuard
 
-V =1.66.3
+V =1.66.4
 MODGO_MODNAME =tailscale.com
 MODGO_VERSION =v${V}
 
Index: distinfo
===
RCS file: /cvs/ports/net/tailscale/distinfo,v
retrieving revision 1.33
diff -u -p -r1.33 distinfo
--- distinfo21 May 2024 20:55:09 -  1.33
+++ distinfo27 May 2024 23:30:29 -
@@ -2204,7 +2204,7 @@ SHA256 (go_modules/software.sslmate.com/
 SHA256 (go_modules/software.sslmate.com/src/go-pkcs12/@v/v0.4.0.zip) = 
VQGaOR5TAqUbpi6YkJ4AYiS4EgeGbakL6vWC7A3uA28=
 SHA256 
(go_modules/src.elv.sh/@v/v0.16.0-rc1.0.20220116211855-fda62502ad7f.mod) = 
ImJNCVe1tA5jNq8JoM2bIJGqRqDtuksdWKAwpOaNWiI=
 SHA256 
(go_modules/src.elv.sh/@v/v0.16.0-rc1.0.20220116211855-fda62502ad7f.zip) = 
edEgOGTOmXKXLEt1tIEy1odFM3S8Y8hyYUcl8moi1Ts=
-SHA256 (tailscale.com-v1.66.3.zip) = 
9iuZ8eYzjj7//Sj9ymMH0463g6wkXWb8OQYAQWwhCAw=
+SHA256 (tailscale.com-v1.66.4.zip) = 
9PkYX22hXeF85zCx4izxzzihvAt4Pb4TBt6ivkl3rjU=
 SIZE (go_modules/4d63.com/gocheckcompilerdirectives/@v/v1.2.1.mod) = 173
 SIZE (go_modules/4d63.com/gocheckcompilerdirectives/@v/v1.2.1.zip) = 7059
 SIZE (go_modules/4d63.com/gochecknoglobals/@v/v0.2.1.mod) = 77
@@ -4411,4 +4411,4 @@ SIZE (go_modules/software.sslmate.com/sr
 SIZE (go_modules/software.sslmate.com/src/go-pkcs12/@v/v0.4.0.zip) = 45988
 SIZE (go_modules/src.elv.sh/@v/v0.16.0-rc1.0.20220116211855-fda62502ad7f.mod) 
= 185
 SIZE (go_modules/src.elv.sh/@v/v0.16.0-rc1.0.20220116211855-fda62502ad7f.zip) 
= 705404
-SIZE (tailscale.com-v1.66.3.zip) = 3341565
+SIZE (tailscale.com-v1.66.4.zip) = 3340450



riscv64 bulk build report

2024-05-27 Thread jca
Bulk build on riscv64-1.ports.openbsd.org

Started : Fri May 17 11:32:41 MDT 2024
Finished: Mon May 27 16:52:14 MDT 2024
Duration: 10 Days 5 hours 20 minutes

Built using OpenBSD 7.5-current (GENERIC.MP) #3: Thu May 16 13:36:44 MDT 2024

Built 10557 packages

Number of packages built each day:
May 17: 2846
May 18: 906
May 19: 3982
May 20: 512
May 21: 559
May 22: 375
May 23: 305
May 24: 279
May 25: 124
May 26: 457
May 27: 212


Critical path missing pkgs:
http://build-failures.rhaalovely.net/riscv64/2024-05-17/summary.log

Build failures: 39
http://build-failures.rhaalovely.net/riscv64/2024-05-17/devel/reposurgeon.log
http://build-failures.rhaalovely.net/riscv64/2024-05-17/devel/tea.log
http://build-failures.rhaalovely.net/riscv64/2024-05-17/lang/gleam.log
http://build-failures.rhaalovely.net/riscv64/2024-05-17/net/dt.log
http://build-failures.rhaalovely.net/riscv64/2024-05-17/net/eduvpn/vpn-daemon.log
http://build-failures.rhaalovely.net/riscv64/2024-05-17/net/irtt.log
http://build-failures.rhaalovely.net/riscv64/2024-05-17/net/minio/client.log
http://build-failures.rhaalovely.net/riscv64/2024-05-17/net/minio/server.log
http://build-failures.rhaalovely.net/riscv64/2024-05-17/net/sping.log
http://build-failures.rhaalovely.net/riscv64/2024-05-17/net/tailscale.log
http://build-failures.rhaalovely.net/riscv64/2024-05-17/net/wormhole-william.log
http://build-failures.rhaalovely.net/riscv64/2024-05-17/security/nuclei.log
http://build-failures.rhaalovely.net/riscv64/2024-05-17/security/ogvt.log
http://build-failures.rhaalovely.net/riscv64/2024-05-17/security/sops.log
http://build-failures.rhaalovely.net/riscv64/2024-05-17/security/vault.log
http://build-failures.rhaalovely.net/riscv64/2024-05-17/shells/elvish.log
http://build-failures.rhaalovely.net/riscv64/2024-05-17/sysutils/amazon-ecs-cli.log
http://build-failures.rhaalovely.net/riscv64/2024-05-17/sysutils/beats/filebeat.log
http://build-failures.rhaalovely.net/riscv64/2024-05-17/sysutils/beats/heartbeat.log
http://build-failures.rhaalovely.net/riscv64/2024-05-17/sysutils/beats/metricbeat.log
http://build-failures.rhaalovely.net/riscv64/2024-05-17/sysutils/beats/packetbeat.log
http://build-failures.rhaalovely.net/riscv64/2024-05-17/sysutils/borgbackup/2.0.log
http://build-failures.rhaalovely.net/riscv64/2024-05-17/sysutils/chezmoi.log
http://build-failures.rhaalovely.net/riscv64/2024-05-17/sysutils/dep.log
http://build-failures.rhaalovely.net/riscv64/2024-05-17/sysutils/direnv.log
http://build-failures.rhaalovely.net/riscv64/2024-05-17/sysutils/gitlab-runner.log
http://build-failures.rhaalovely.net/riscv64/2024-05-17/sysutils/lf.log
http://build-failures.rhaalovely.net/riscv64/2024-05-17/sysutils/nomad.log
http://build-failures.rhaalovely.net/riscv64/2024-05-17/sysutils/oc.log
http://build-failures.rhaalovely.net/riscv64/2024-05-17/sysutils/planor.log
http://build-failures.rhaalovely.net/riscv64/2024-05-17/sysutils/promscale.log
http://build-failures.rhaalovely.net/riscv64/2024-05-17/sysutils/rclone.log
http://build-failures.rhaalovely.net/riscv64/2024-05-17/sysutils/serf.log
http://build-failures.rhaalovely.net/riscv64/2024-05-17/sysutils/telegraf.log
http://build-failures.rhaalovely.net/riscv64/2024-05-17/sysutils/terragrunt.log
http://build-failures.rhaalovely.net/riscv64/2024-05-17/textproc/apertium-dicts/oci-fra.log
http://build-failures.rhaalovely.net/riscv64/2024-05-17/textproc/gron.log
http://build-failures.rhaalovely.net/riscv64/2024-05-17/textproc/slides.log
http://build-failures.rhaalovely.net/riscv64/2024-05-17/www/chromium.log

Recurrent failures:
 failures/devel/reposurgeon.log
 failures/devel/tea.log
 failures/lang/gleam.log
 failures/net/dt.log
 failures/security/nuclei.log
 failures/security/ogvt.log
 failures/security/sops.log
 failures/security/vault.log
 failures/shells/elvish.log
 failures/sysutils/amazon-ecs-cli.log
 failures/sysutils/beats/filebeat.log
 failures/sysutils/beats/heartbeat.log
 failures/sysutils/chezmoi.log
 failures/sysutils/dep.log
 failures/sysutils/direnv.log
 failures/sysutils/gitlab-runner.log
 failures/sysutils/lf.log
 failures/sysutils/nomad.log
 failures/sysutils/serf.log
 failures/sysutils/telegraf.log
 failures/sysutils/terragrunt.log
 failures/textproc/gron.log
 failures/textproc/slides.log
 failures/www/chromium.log

New failures:
+failures/textproc/apertium-dicts/oci-fra.log

Resolved failures:
-failures/audio/cozy.log
-failures/devel/selene.log
-failures/security/step-cli.log
-failures/sysutils/alertmanager.log
-failures/sysutils/fclones.log

Packages newly built:
+audio/cozy
+devel/luaposix,lua54
+devel/selene
+fonts/inclusive-sans
+lang/mujs
+lang/python/3
+lang/python/3,-gdbm
+lang/python/3,-idle
+lang/python/3,-main
+lang/python/3,-tests
+lang/python/3,-tkinter
+mail/imapdedup
+mail/opensmtpd-tables/ldap
+mail/opensmtpd-tables/mysql
+mail/opensmtpd-tables/passwd
+mail/opensmtpd-tables/postgres
+mail/opensmtpd-tables/redis
+mail/opensmtpd-tables/socketmap
+mail/opensmtpd-tables/sqlite
+security/pinentry,,-

UPDATE: databases/timescaledb-2.15.0

2024-05-27 Thread Renato Aguiar
Diff updating timescaledb to 2.15.0.

This version has an additional upgrade step that requires running a SQL
script that isn't included in release tarball. I added a note with a
download link to the port README, but I'm wondering if we should include
it in the port instead.

diff --git a/databases/timescaledb/Makefile b/databases/timescaledb/Makefile
index 46389fd2322..44e1e5b167d 100644
--- a/databases/timescaledb/Makefile
+++ b/databases/timescaledb/Makefile
@@ -2,7 +2,7 @@ COMMENT =	database designed to make SQL scalable for time-series data
 
 GH_ACCOUNT =	timescale
 GH_PROJECT =	timescaledb
-GH_TAGNAME =	2.14.2
+GH_TAGNAME =	2.15.0
 
 CATEGORIES =	databases
 HOMEPAGE =	https://www.timescale.com/
diff --git a/databases/timescaledb/distinfo b/databases/timescaledb/distinfo
index a0e20a0d44b..82530f1aa61 100644
--- a/databases/timescaledb/distinfo
+++ b/databases/timescaledb/distinfo
@@ -1,2 +1,2 @@
-SHA256 (timescaledb-2.14.2.tar.gz) = x3aLJn6meRTQSRso2hAvrs0xcGDkKbLadTBRf7yU5zs=
-SIZE (timescaledb-2.14.2.tar.gz) = 7319288
+SHA256 (timescaledb-2.15.0.tar.gz) = /yAZ9zRWb3OvCoBB21D38dCtaWf34ufXltOIzTjAtbs=
+SIZE (timescaledb-2.15.0.tar.gz) = 7428047
diff --git a/databases/timescaledb/pkg/PLIST b/databases/timescaledb/pkg/PLIST
index 5f2f8860e11..5b6187b300a 100644
--- a/databases/timescaledb/pkg/PLIST
+++ b/databases/timescaledb/pkg/PLIST
@@ -18,6 +18,7 @@ share/postgresql/extension/timescaledb--2.13.0--${GH_TAGNAME}.sql
 share/postgresql/extension/timescaledb--2.13.1--${GH_TAGNAME}.sql
 share/postgresql/extension/timescaledb--2.14.0--${GH_TAGNAME}.sql
 share/postgresql/extension/timescaledb--2.14.1--${GH_TAGNAME}.sql
+share/postgresql/extension/timescaledb--2.14.2--${GH_TAGNAME}.sql
 share/postgresql/extension/timescaledb--${GH_TAGNAME}.sql
 share/postgresql/extension/timescaledb--2.2.0--${GH_TAGNAME}.sql
 share/postgresql/extension/timescaledb--2.2.1--${GH_TAGNAME}.sql
diff --git a/databases/timescaledb/pkg/README b/databases/timescaledb/pkg/README
index a7f10d9aa05..478be4f2c7a 100644
--- a/databases/timescaledb/pkg/README
+++ b/databases/timescaledb/pkg/README
@@ -18,6 +18,14 @@ You will need to start psql with '-X' and execute :
 
 Executing '\dx timescaledb' should show the latest version number.
 
+If you are upgrading from versions prior to 2.15.0, you must also download and
+run this SQL script:
+
+  https://github.com/timescale/timescaledb-extras/blob/master/utils/2.15.X-fix_hypertable_foreign_keys.sql
+
+See changelog at https://github.com/timescale/timescaledb/releases/tag/2.15.0
+for more details.
+
 Telemetry
 =
 TimescaleDB telemetry and version checking is disabled by default.

-- 
Renato Aguiar