Re: Ruby 3.2.1
On Wed, Feb 15, 2023 at 4:17 PM vtamara wrote: > > > Can you explain why you > > were running `gem update --system`? The only reason I can think of is > > the nag message asked you to. The only reason I can think of is > > the nag message asked you to. > > I prefer to have all the gems as updated as possible, particularly > bundler and running `doas gem update --system` will update bundler and > rubygems at once. > > After running it, if I remove the package ruby, it present a warning: > File > /usr/local/lib/ruby/gems/3.2/specifications/default/bundler-2.4.1.gemspec > does not exist > But it will remove the other files. > If `gem update --system` adds a new file, I don't think that pkg_delete will remove it. And if you run pkg_delete with checksums, it won't remove any modified files either. > I understand that in this moment there is not much advantge because to > udpate bundler I can run: > doas gem install bundler > This is the recommended approach if you must update bundler. Thanks, Jeremy
Re: Ruby 3.2.1
Can you explain why you were running `gem update --system`? The only reason I can think of is the nag message asked you to. The only reason I can think of is the nag message asked you to. I prefer to have all the gems as updated as possible, particularly bundler and running `doas gem update --system` will update bundler and rubygems at once. After running it, if I remove the package ruby, it present a warning: File /usr/local/lib/ruby/gems/3.2/specifications/default/bundler-2.4.1.gemspec does not exist But it will remove the other files. I understand that in this moment there is not much advantge because to udpate bundler I can run: doas gem install bundler So as you prefer is fine. El 2023-02-13 00:20, Jeremy Evans escribió: On 02/12 09:28, vtamara wrote: One question about El 2023-02-09 11:38, Jeremy Evans escribi??: > * Change how gem update --system nag message is removed, which also > prevents gem update --system from working (nobody using the OpenBSD > package should use it). I have been testing 3.2 long ago doing frequently doas gem update --system and I have not noticed any issue, why to remove it? My understanding is it modifies files the ruby-* package installs. That will prevent clean uninstalls of the package. Can you explain why you were running `gem update --system`? The only reason I can think of is the nag message asked you to. Thanks, Jeremy -- Dios, gracias por tu amor infinito. -- Vladimir Támara Patiño. http://vtamara.pasosdeJesus.org/ http://www.pasosdejesus.org/dominio_publico_colombia.html
Re: amd64-clang bulk build report
On 2023/02/14 07:26:42 +0100, Theo Buehler wrote: > On Mon, Feb 13, 2023 at 10:12:15PM +0100, Christian Weisgerber wrote: > > Missing from your list: > > > > | x11/eterm [-Wint-conversion] > > > > That mixes pointer and integer semantics in such a way that I > > couldn't figure out what it was even intended to do. > > That one, too. x11/eterm and devel/libast (which is only needed by eterm in ports) have also problems with the imlib2 update (that i've fixed for this time.) So, FWIW, I'd be fine with removing both.
Heads ups, perl upgraded, wait for mirror package sync / v5.36.0
# perl -e 'print "$]\n";' 5.036000 # perl -MBSD::arc4random -e 'print "okay\n"' arc4rnd_xs.c: loadable library and perl binaries are mismatched (got first handshake key 0xec0, needed 0xeb8) -- Regards, Mikolaj
Re: [Maintainer Update] archivers/zpaqfranz-57.3
On 2023/02/15 16:57:08 +0100, tux0r wrote: > According to the change log, only proxmox-relevant changes, but we know now > that the developer rarely gives a full overview ... ;-) eheh... :) > Update attached. committed, thanks!
Re: aarch64 bulk build report
> http://build-failures.rhaalovely.net/aarch64/2023-02-13/graphics/openscenegraph.log This is a hidden dep on cad/oce. Not sure if it is desirable to add this relatively heavy dependency or if it's better to neuter it. It seems that there are various other hidden deps. For instance, my logs suggest that the curl module may or may not be picked up. It would be nice if someone who likes dealing with cmake could fix this.
Re: [update] Lagrange to 1.15.2
On 2023/02/14 22:14:55 +0100, Florian Viehweger wrote: > Hi, > > this is an update for Lagrange to 1.15.2. > > Some testing done on amd64. No issues found. > > portcheck and 'make port-lib-depends-check' are happy. Committed, thanks!
UPDATE: Dendrite-0.11.1
Hi,
Little update for Dendrite to make it play nice with Go 1.20:
https://github.com/matrix-org/dendrite/releases/tag/v0.11.1
OK? Comments?
Cheers.-
Index: Makefile
===
RCS file: /cvs/ports/net/dendrite/Makefile,v
retrieving revision 1.22
diff -u -p -r1.22 Makefile
--- Makefile15 Feb 2023 17:18:09 - 1.22
+++ Makefile15 Feb 2023 20:18:40 -
@@ -1,8 +1,7 @@
-BROKEN = needs update - vendored quic-go does not support Go 1.20
COMMENT = matrix homeserver written in Go
MODGO_MODNAME =github.com/matrix-org/dendrite
-MODGO_VERSION =v0.11.0
+MODGO_VERSION =v0.11.1
DISTNAME = dendrite-${MODGO_VERSION}
Index: distinfo
===
RCS file: /cvs/ports/net/dendrite/distinfo,v
retrieving revision 1.16
diff -u -p -r1.16 distinfo
--- distinfo10 Feb 2023 16:10:51 - 1.16
+++ distinfo15 Feb 2023 20:18:42 -
@@ -1,4 +1,4 @@
-SHA256 (dendrite-v0.11.0.zip) = 7sgfFUzK5lFfrHMBXCweh9HY6EZC9darRkn2zYQqX9A=
+SHA256 (dendrite-v0.11.1.zip) = Y/IQcQ9PP+BJOMeyecGObHzoE8hw+Wg+2qjpLskJ1Xo=
SHA256 (go_modules/cloud.google.com/go/@v/v0.26.0.mod) =
IhijTyC5cbwZUhbUGV9XUgoqy9hd5/wxrPxEAmZwTBE=
SHA256 (go_modules/cloud.google.com/go/@v/v0.34.0.mod) =
IhijTyC5cbwZUhbUGV9XUgoqy9hd5/wxrPxEAmZwTBE=
SHA256 (go_modules/cloud.google.com/go/@v/v0.38.0.mod) =
IRVe7cPkx6CccZziPHA/vxTDSspC7QDcCHdN5uu+gAc=
@@ -65,8 +65,8 @@ SHA256 (go_modules/github.com/!microsoft
SHA256 (go_modules/github.com/!microsoft/go-winio/@v/v0.5.2.zip) =
9HnUI0H97R0KmFQHEzOZIHdPdUDt96drhJf7wRSTE4w=
SHA256 (go_modules/github.com/!roaring!bitmap/roaring/@v/v0.4.7.mod) =
gs0T9NkSH5wGtHmNz26C+kky3cqo5b3Si85IJEBv11Q=
SHA256 (go_modules/github.com/!roaring!bitmap/roaring/@v/v0.9.4.mod) =
1ovrnEgXqqvPRNT2WOa2MHjPM8Sv+SOxwhiXvwmQRpM=
-SHA256 (go_modules/github.com/!roaring!bitmap/roaring/@v/v1.2.1.mod) =
1ovrnEgXqqvPRNT2WOa2MHjPM8Sv+SOxwhiXvwmQRpM=
-SHA256 (go_modules/github.com/!roaring!bitmap/roaring/@v/v1.2.1.zip) =
e3q1fWm/frv74EVg6zVUcuEF6u+hS9MwyKBcPNVXivs=
+SHA256 (go_modules/github.com/!roaring!bitmap/roaring/@v/v1.2.3.mod) =
Ehk1br4174XhxlbE++Rywn+CMolKbO5rhIEOPcs+vc0=
+SHA256 (go_modules/github.com/!roaring!bitmap/roaring/@v/v1.2.3.zip) =
Vw07NapZ18sajVLivovoI/5UHpe0R5Rmj0zUdFjcE88=
SHA256 (go_modules/github.com/!ryan!carrier/dijkstra/@v/v1.1.0.mod) =
5iM3Nu0PyjbbRF0Wdr44Uc+NDZIyCXQVcszJ61zc6Tc=
SHA256 (go_modules/github.com/!ryan!carrier/dijkstra/@v/v1.1.0.zip) =
/TaHf1BJpQxOB7bLc7OmslP7RjegnGRTELXgivP6eII=
SHA256
(go_modules/github.com/!shopify/goreferrer/@v/v0.0.0-20220729165902-8cddb4f5de06.mod)
= rMTcJLp6Is6Q9qIRxj2Ds7LpmLdQMadPMPqQfYoTt80=
@@ -97,8 +97,6 @@ SHA256 (go_modules/github.com/anacrolix/
SHA256
(go_modules/github.com/anacrolix/tagflag/@v/v0.0.0-20180109131632-2146c8d41bf0.zip)
= b7U3QduMZOpDj0FzIA4uFxHKeBbTo9b0jgpNY7W8EO4=
SHA256 (go_modules/github.com/andybalholm/brotli/@v/v1.0.4.mod) =
gLn5QXXMYZiLSYDdCzyCwBdJQP93fYIOJhrmAA+H1xM=
SHA256 (go_modules/github.com/andybalholm/brotli/@v/v1.0.4.zip) =
6+U/KFbhAOJzquPFo2jRFO1X9Rg7sD5wcI1sKQQa1zU=
-SHA256
(go_modules/github.com/armon/consul-api/@v/v0.0.0-20180202201655-eb2c6b5be1b6.mod)
= Xv7HHjzIZRORNpczBbQ4q8l5CKVFmXUht+0qpIsbTdY=
-SHA256
(go_modules/github.com/armon/consul-api/@v/v0.0.0-20180202201655-eb2c6b5be1b6.zip)
= CRt5Zn8WriRXhZVsSQ/gXuJpcKifjs2+hYrjUQ1yUIg=
SHA256 (go_modules/github.com/aymerick/douceur/@v/v0.2.0.mod) =
XgRUJBwle0xPnb3chOeOmeKcUnWzz67or9K7R25ySJc=
SHA256 (go_modules/github.com/aymerick/douceur/@v/v0.2.0.zip) =
3L9pdgzBqLMjhElUOOEIbkw9ZpsuvA3r2S4YZf/WvmA=
SHA256
(go_modules/github.com/beorn7/perks/@v/v0.0.0-20180321164747-3a771d992973.mod)
= zE0fqtdZZfpp6xMSC/lWgncZAF/z7NxwSzb7WPsf0W4=
@@ -106,15 +104,15 @@ SHA256 (go_modules/github.com/beorn7/per
SHA256 (go_modules/github.com/beorn7/perks/@v/v1.0.1.mod) =
yHCz/lC2lE+rCVsGII2ciJh2PpFzyx7tMljD1YMJumY=
SHA256 (go_modules/github.com/beorn7/perks/@v/v1.0.1.zip) =
Jb2eLZSsp3Dm28H1NyX4T2r0Qy9jHTXdLEb5bvBRLxo=
SHA256 (go_modules/github.com/bits-and-blooms/bitset/@v/v1.2.0.mod) =
YxEhvopQd0JSd7Fw6C1S1OsMzorAdU+7+syl9cvpBDg=
-SHA256 (go_modules/github.com/bits-and-blooms/bitset/@v/v1.3.3.mod) =
YxEhvopQd0JSd7Fw6C1S1OsMzorAdU+7+syl9cvpBDg=
-SHA256 (go_modules/github.com/bits-and-blooms/bitset/@v/v1.3.3.zip) =
t7Slma0wWSjbMzZPcwocZGUGV66LUpu6WiIeTrVpRew=
-SHA256 (go_modules/github.com/blevesearch/bleve/v2/@v/v2.3.4.mod) =
KpSKc/sPq7zcIkqD1Tn8VZDCGFxY3BDFaBusDvbRefc=
-SHA256 (go_modules/github.com/blevesearch/bleve/v2/@v/v2.3.4.zip) =
VgsZJo09dipqrnXGxkf/5ltDOlRGG1yU5V2pBP5BuZk=
-SHA256 (go_modules/github.com/blevesearch/bleve_index_api/@v/v1.0.3.mod) =
io0mCjC7Q1ZlkRnjaJdqqNyfB1t3zzXzyZFztBcdorU=
-SHA256 (go_modules/github.com/blevesearch/bleve_index_api/@v/v1.0.3.zip) =
nDfJVnpX1okZzqHBGYDFadm0HoKlWojqUjCcloXYjxY=
-SHA256 (go_modules/github.com/blevesearch/geo/@v/v0.1.13.mod) =
qvGbSTZ6WdoL
aarch64 bulk build report
bulk build on arm64.ports.openbsd.org started on Mon Feb 13 08:02:04 MST 2023 finished at Wed Feb 15 13:13:55 MST 2023 lasted 2D05h11m done with kern.version=OpenBSD 7.2-current (GENERIC.MP) #2023: Mon Feb 13 00:50:08 MST 2023 built packages:11607 Feb 13:3815 Feb 14:1747 Feb 15:6044 critical path missing pkgs: http://build-failures.rhaalovely.net/aarch64/2023-02-13/summary.log build failures: 5 http://build-failures.rhaalovely.net/aarch64/2023-02-13/devel/quirks.log http://build-failures.rhaalovely.net/aarch64/2023-02-13/emulators/citra.log http://build-failures.rhaalovely.net/aarch64/2023-02-13/games/choria.log http://build-failures.rhaalovely.net/aarch64/2023-02-13/graphics/openscenegraph.log http://build-failures.rhaalovely.net/aarch64/2023-02-13/lang/mono.log recurrent failures failures/emulators/citra.log failures/games/choria.log new failures +++ ls-failures Wed Feb 15 13:15:27 2023 +failures/devel/quirks.log +failures/graphics/openscenegraph.log +failures/lang/mono.log resolved failures --- ../old/aarch64/last//ls-failuresSun Feb 12 16:10:35 2023 -failures/math/gnumeric.log -failures/www/chromium.log
[maintainer update] Python 3.11.2
https://docs.python.org/release/3.11.2/whatsnew/changelog.html#python-3-11-2-final
A bunch of fixes here, again none labelled as security
ok?
--Kurt
Index: Makefile
===
RCS file: /cvs/ports/lang/python/3.11/Makefile,v
retrieving revision 1.6
diff -u -p -r1.6 Makefile
--- Makefile25 Dec 2022 13:42:05 - 1.6
+++ Makefile15 Feb 2023 19:06:07 -
@@ -3,12 +3,10 @@
# requirement of the PSF license, if it constitutes a change to
# Python itself.
-FULL_VERSION = 3.11.1
+FULL_VERSION = 3.11.2
SHARED_LIBS = python3.11 0.0
VERSION_SPEC = >=3.11,<3.12
PORTROACH =limit:^3\.11
-
-REVISION-main =0
CONFIGURE_ENV += ac_cv_working_openssl_hashlib=yes \
TCLTK_CFLAGS="-I${MODTCL_INCDIR} -I${MODTK_INCDIR}
-I${X11BASE}/include" \
Index: distinfo
===
RCS file: /cvs/ports/lang/python/3.11/distinfo,v
retrieving revision 1.2
diff -u -p -r1.2 distinfo
--- distinfo20 Dec 2022 23:55:22 - 1.2
+++ distinfo15 Feb 2023 19:06:07 -
@@ -1,2 +1,2 @@
-SHA256 (Python-3.11.1.tgz) = uu1RjiazN9TYEFZ5yvaMXDJjDXAmFPwXTpjLlcRr36Q=
-SIZE (Python-3.11.1.tgz) = 26394378
+SHA256 (Python-3.11.2.tgz) = JBHHS9pbvPzdr0Ux9m0a3HPyR/UprumBsClROu/b+Ek=
+SIZE (Python-3.11.2.tgz) = 26437858
Index: pkg/PLIST-main
===
RCS file: /cvs/ports/lang/python/3.11/pkg/PLIST-main,v
retrieving revision 1.3
diff -u -p -r1.3 PLIST-main
--- pkg/PLIST-main 20 Dec 2022 23:55:22 - 1.3
+++ pkg/PLIST-main 15 Feb 2023 19:06:09 -
@@ -2113,6 +2113,7 @@ lib/python3.11/lib-dynload/
@so lib/python3.11/lib-dynload/_struct.cpython-311.so
@so lib/python3.11/lib-dynload/_testbuffer.cpython-311.so
@so lib/python3.11/lib-dynload/_testcapi.cpython-311.so
+@so lib/python3.11/lib-dynload/_testclinic.cpython-311.so
@so lib/python3.11/lib-dynload/_testimportmultiple.cpython-311.so
@so lib/python3.11/lib-dynload/_testinternalcapi.cpython-311.so
@so lib/python3.11/lib-dynload/_testmultiphase.cpython-311.so
[maintainer update] Python 3.10.10
https://docs.python.org/release/3.10.10/whatsnew/changelog.html#python-3-10-10-final
A number of fixes. None labelled as security.
ok?
--Kurt
Index: Makefile
===
RCS file: /cvs/ports/lang/python/3.10/Makefile,v
retrieving revision 1.30
diff -u -p -r1.30 Makefile
--- Makefile16 Dec 2022 17:03:28 - 1.30
+++ Makefile15 Feb 2023 17:59:32 -
@@ -3,12 +3,10 @@
# requirement of the PSF license, if it constitutes a change to
# Python itself.
-FULL_VERSION = 3.10.9
+FULL_VERSION = 3.10.10
SHARED_LIBS = python3.10 0.0
VERSION_SPEC = >=3.10,<3.11
PORTROACH =limit:^3\.10
-
-REVISION = 0
# This is the MODPY_DEFAULT_VERSION_3 version of Python:
# - override "@comment" setting so that bin/python3 etc are installed
Index: distinfo
===
RCS file: /cvs/ports/lang/python/3.10/distinfo,v
retrieving revision 1.8
diff -u -p -r1.8 distinfo
--- distinfo16 Dec 2022 17:03:28 - 1.8
+++ distinfo15 Feb 2023 17:59:32 -
@@ -1,2 +1,2 @@
-SHA256 (Python-3.10.9.tgz) = TM1+RsiJj0x4YpEKFwOqDmNSWROlGauy9V4mIgqRTYg=
-SIZE (Python-3.10.9.tgz) = 26044345
+SHA256 (Python-3.10.10.tgz) = +6ZFWd3iHr3JU+RWXnMVc7thFZ3o5NTO3ucPsRlvYQ0=
+SIZE (Python-3.10.10.tgz) = 26071329
Index: patches/patch-setup_py
===
RCS file: /cvs/ports/lang/python/3.10/patches/patch-setup_py,v
retrieving revision 1.7
diff -u -p -r1.7 patch-setup_py
--- patches/patch-setup_py 29 Aug 2022 12:23:42 - 1.7
+++ patches/patch-setup_py 15 Feb 2023 17:59:32 -
@@ -1,7 +1,7 @@
Index: setup.py
--- setup.py.orig
+++ setup.py
-@@ -1872,7 +1872,7 @@ class PyBuildExt(build_ext):
+@@ -1875,7 +1875,7 @@ class PyBuildExt(build_ext):
uuid_h = sysconfig.get_config_var("HAVE_UUID_H")
uuid_uuid_h = sysconfig.get_config_var("HAVE_UUID_UUID_H")
if uuid_h or uuid_uuid_h:
Index: pkg/PLIST-main
===
RCS file: /cvs/ports/lang/python/3.10/pkg/PLIST-main,v
retrieving revision 1.14
diff -u -p -r1.14 PLIST-main
--- pkg/PLIST-main 16 Dec 2022 17:03:28 - 1.14
+++ pkg/PLIST-main 15 Feb 2023 17:59:32 -
@@ -2056,6 +2056,7 @@ lib/python3.10/lib-dynload/
@so lib/python3.10/lib-dynload/_struct.cpython-310.so
@so lib/python3.10/lib-dynload/_testbuffer.cpython-310.so
@so lib/python3.10/lib-dynload/_testcapi.cpython-310.so
+@so lib/python3.10/lib-dynload/_testclinic.cpython-310.so
@so lib/python3.10/lib-dynload/_testimportmultiple.cpython-310.so
@so lib/python3.10/lib-dynload/_testinternalcapi.cpython-310.so
@so lib/python3.10/lib-dynload/_testmultiphase.cpython-310.so
Re: devel/cmake: handle ALL_TARGET, obsolete custom do-build targets
06.02.2023 14:16, Klemens Nanni пишет:
> (Improved parts of backed out "devel/cmake: handle build and install targets"
> which broke the install target as ALL_TARGET and INSTALL_TARGET are handled
> differently, see port-modules(5).)
>
>
> Honour ALL_TARGET in cmake.port.mk and use it if and only if it has been set
> explicitly. This already worked in the first diff.
>
> This time, do not append to MODCMAKE_BUILD_TARGET and instead pass it in
> do-build conditionally.
>
> Then CMAKE_* variables don't change and ports can keep reusing them, which is
> currently done so in a few pre-test targets to build tests
>
> Custom do-build targets can be dropped, in one commit or separately makes no
> difference as cmake.port.mk only changes behaviour if do-build is undefined.
> Either way, the resulting do-build contents are identical in all cases.
>
> Next up, we can automate deferred test compilation and get rid of those
> `@${MODCMAKE_BUILD_TARGET}' lines in pre-test, too.
>
> Feedback? Objection? OK?
>
> (cmake first, then the same - hunk in all ports with the same do-build
> target.)
Ping.
Can someone try this in a bulk for me, please?
Index: devel/cmake/cmake.port.mk
===
RCS file: /cvs/ports/devel/cmake/cmake.port.mk,v
retrieving revision 1.82
diff -u -p -r1.82 cmake.port.mk
--- devel/cmake/cmake.port.mk 28 Jan 2023 22:03:46 - 1.82
+++ devel/cmake/cmake.port.mk 6 Feb 2023 13:36:05 -
@@ -33,9 +33,20 @@ MODCMAKE_INSTALL_TARGET = cd ${WRKBUILD}
MODCMAKE_TEST_TARGET = cd ${WRKBUILD} && exec ${SETENV} ${ALL_TEST_ENV} \
ctest ${_MAKE_VERBOSE} -j ${MAKE_JOBS}
+# Default targets are only known after configure, see cmake-buildsystem(7) and
+# cmake-properties(7) BUILDSYSTEM_TARGETS.
+# Overrule bsd.port.mk defaults.
+ALL_TARGET ?= # empty
+
+# Only pass explicitly set targets.
+# Do not quote, cmake(1) -t takes multiple target arguments.
.if !target(do-build)
do-build:
+. if empty(ALL_TARGET)
@${MODCMAKE_BUILD_TARGET}
+. else
+ @${MODCMAKE_BUILD_TARGET} -t ${ALL_TARGET}
+. endif
.endif
.if !target(do-install)
Index: audio/mumble/Makefile
===
RCS file: /cvs/ports/audio/mumble/Makefile,v
retrieving revision 1.71
diff -u -p -r1.71 Makefile
--- audio/mumble/Makefile 2 Feb 2023 23:58:01 - 1.71
+++ audio/mumble/Makefile 6 Feb 2023 13:29:39 -
@@ -99,9 +99,6 @@ ALL_TARGET = mumble mumble-server
pre-configure:
${SUBST_CMD} ${SERVER_CONFIG_FILE}
-do-build:
- @${MODCMAKE_BUILD_TARGET} -t ${ALL_TARGET}
-
# build whatever is left (ca. 63 C++ test files)
pre-test:
@${MODCMAKE_BUILD_TARGET}
Index: audio/taglib/Makefile
===
RCS file: /cvs/ports/audio/taglib/Makefile,v
retrieving revision 1.50
diff -u -p -r1.50 Makefile
--- audio/taglib/Makefile 2 Feb 2023 23:19:13 - 1.50
+++ audio/taglib/Makefile 6 Feb 2023 13:33:24 -
@@ -29,9 +29,6 @@ TEST_TARGET= check
# evertyhing except tests
ALL_TARGET=tag tag_c
-do-build:
- @${MODCMAKE_BUILD_TARGET} -t ${ALL_TARGET}
-
# build whatever is left (ca. 40 C++ test files)
pre-test:
@${MODCMAKE_BUILD_TARGET}
Index: devel/abseil-cpp/Makefile
===
RCS file: /cvs/ports/devel/abseil-cpp/Makefile,v
retrieving revision 1.12
diff -u -p -r1.12 Makefile
--- devel/abseil-cpp/Makefile 4 Feb 2023 17:37:58 - 1.12
+++ devel/abseil-cpp/Makefile 6 Feb 2023 13:33:37 -
@@ -79,9 +79,6 @@ TEST_ENV += TEST_TMPDIR=${WRKBUILD}/tes
LD_LIBRARY_PATH=/usr/lib:${WRKBUILD}/test_lib
.endif
-do-build:
- @${MODCMAKE_BUILD_TARGET} -t ${ALL_TARGET}
-
# build whatever is left (ca. 400 test files)
pre-test:
@${MODCMAKE_BUILD_TARGET}
Index: devel/ccache/Makefile
===
RCS file: /cvs/ports/devel/ccache/Makefile,v
retrieving revision 1.87
diff -u -p -r1.87 Makefile
--- devel/ccache/Makefile 2 Feb 2023 22:54:55 - 1.87
+++ devel/ccache/Makefile 6 Feb 2023 13:33:51 -
@@ -35,9 +35,6 @@ TEST_ENV =CC="${CC}"
# evertyhing except tests
ALL_TARGET = ccache doc
-do-build:
- @${MODCMAKE_BUILD_TARGET} -t ${ALL_TARGET}
-
# build whatever is left (ca. 35 C++ test files)
pre-test:
@${MODCMAKE_BUILD_TARGET}
Index: devel/cjson/Makefile
===
RCS file: /cvs/ports/devel/cjson/Makefile,v
retrieving revision 1.3
diff -u -p -r1.3 Makefile
--- devel/cjson/Makefile3 Feb 2023 02:09:38 - 1.3
+++ devel/cjson/Makefile6 Feb 2023 13:33:44 -
@@ -23,9 +23,6 @@ MODULES = devel/cmake
# evertyhing except tests
ALL_TARGET = cjson
-do-build:
-
Re: [UPDATE] net/p5-POE-Component-IRC to 6.93
On Tue, Feb 14, 2023 at 05:49:18PM -0800, Andrew Hewus Fresh wrote: > It turns out there is something that needs updating for perl 5.36, > or more specifically the updated Socket module. I didn't look up the > details, but: > > https://metacpan.org/dist/POE-Component-IRC/changes > - Fix issue with DCC on OpenBSD with newer Socket >= 2.031 > > OK? OK bluhm@ > Index: Makefile > === > RCS file: /cvs/ports/net/p5-POE-Component-IRC/Makefile,v > retrieving revision 1.41 > diff -u -p -r1.41 Makefile > --- Makefile 11 Mar 2022 19:46:50 - 1.41 > +++ Makefile 15 Feb 2023 01:16:05 - > @@ -1,8 +1,7 @@ > COMMENT= event-driven IRC-client module > > -DISTNAME=POE-Component-IRC-6.90 > +DISTNAME=POE-Component-IRC-6.93 > CATEGORIES= net > -REVISION=0 > > # perl > PERMIT_PACKAGE= Yes > Index: distinfo > === > RCS file: /cvs/ports/net/p5-POE-Component-IRC/distinfo,v > retrieving revision 1.26 > diff -u -p -r1.26 distinfo > --- distinfo 3 Dec 2018 21:29:15 - 1.26 > +++ distinfo 15 Feb 2023 01:16:05 - > @@ -1,2 +1,2 @@ > -SHA256 (POE-Component-IRC-6.90.tar.gz) = > hLn6E+lS2w9TYFpXyfCf1EadPSwNrSVJECqgvDv5I9M= > -SIZE (POE-Component-IRC-6.90.tar.gz) = 375501 > +SHA256 (POE-Component-IRC-6.93.tar.gz) = > 6tRHeia4esvT7NIYQs5bnW4UIw3cRWX+6MaM9n5h3J4= > +SIZE (POE-Component-IRC-6.93.tar.gz) = 377897
maintainer update, www/ephemetoot 3.1.3 --> 3.1.4
Hi ports@,
This is an update of www/ephemetoot to its latest version 3.1.4
The changes on the software are:
* removal of unnecessary setuptools dependency found by florian@ here:
https://marc.info/?l=openbsd-ports&m=167325446116128&w=2
which upstream integrated.
* version number displayed is now accurate for latest version
* minimum Python version is now 3.8
The port only bumps version and drops setuptools as a RUN_DEPENDS.
Tested in my basic use case on amd64.
ok to commit ?
diff /usr/ports
commit - 59eec5c604409c9cf68d099a5e5dc095ea712868
path + /usr/ports
blob - d2bb1777c418f0f6eb04ad2b543041041d597688
file + www/ephemetoot/Makefile
--- www/ephemetoot/Makefile
+++ www/ephemetoot/Makefile
@@ -1,8 +1,7 @@
COMMENT = tool for deleting old Mastodon toots
-MODPY_EGG_VERSION =3.1.3
+MODPY_EGG_VERSION =3.1.4
DISTNAME = ephemetoot-${MODPY_EGG_VERSION}
-REVISION = 4
CATEGORIES = www
@@ -16,8 +15,7 @@ RUN_DEPENDS = devel/py-setuptools${MODPY_FLAVOR} \
MODPY_PI = Yes
MODPY_PYBUILD =poetry-core
-RUN_DEPENDS = devel/py-setuptools${MODPY_FLAVOR} \
- textproc/py-yaml${MODPY_FLAVOR}>=5.0 \
+RUN_DEPENDS = textproc/py-yaml${MODPY_FLAVOR}>=5.0 \
www/py-mastodon.py${MODPY_FLAVOR} \
www/py-requests${MODPY_FLAVOR}
blob - ec49e3523431779272c17cb143e2599a5915bdc0
file + www/ephemetoot/distinfo
--- www/ephemetoot/distinfo
+++ www/ephemetoot/distinfo
@@ -1,2 +1,2 @@
-SHA256 (ephemetoot-3.1.3.tar.gz) = 6c5G9hGcwjE0tJEQhzmH66ORTM74gewrcfNVFMnHuG8=
-SIZE (ephemetoot-3.1.3.tar.gz) = 59144
+SHA256 (ephemetoot-3.1.4.tar.gz) = egR430Pks04cOSrvK3f3vjxoul22WUleGHyn9HYrzbI=
+SIZE (ephemetoot-3.1.4.tar.gz) = 59110
--
Paco Esteban.
0x5818130B8A6DBC03
[Maintainer Update] archivers/zpaqfranz-57.3
According to the change log, only proxmox-relevant changes, but we know now that the developer rarely gives a full overview ... ;-) Update attached. tux0r. zpaqfranz-57.3.diff Description: Binary data
Re: dpb patch for proper fetching
On 2023/02/08 11:26, Marc Espie wrote:
> This proved surprisingly complicated.
> This should fix fetching for
> BUILD_DEPENDS = some/path:patch
> situations (where the path actually doesn't get built)
>
> This could use a full bulk or two.
>
> (I expect to simplify the "new_path/new_fetch_path code later on, but for
> now, this should do)
This has a change in effect in some corner cases. I don't think it's
really much of a problem.
If a port is updated on disk after the dpb run was started and the new
distfile wasn't fetched yet, dpb now attempts building that port without
the distfile, and because it sets FETCH_PACKAGES=No, assuming _pbuild
has no network access, fetching fails.
Example log - dpb started a test build with include-what-you-use-0.17,
I then noticed I'd forgotten to apply a diff which bumped the version
to include-what-you-use-0.19, and this happened:
: i386.p; cat devel/include-what-you-use.log
>>> Building on i386-2 under devel/include-what-you-use
BDEPENDS = [devel/ninja;devel/llvm;devel/cmake]
DIST =
[devel/include-what-you-use:include-what-you-use-0.17.src.tar.gz]
FULLPKGNAME = include-what-you-use-0.17p0
RDEPENDS = [devel/llvm;lang/python/3.10]
(Junk lock obtained for i386-2 at 1676473503.80)
>>> Running depends in devel/include-what-you-use at 1676473503.82
last junk was in math/py-bottleneck,python3
/usr/sbin/pkg_add -aI -Drepair llvm-15.0.7
was: /usr/sbin/pkg_add -aI -Drepair cmake-3.25.2v0 llvm-15.0.7 ninja-1.11.1
/usr/sbin/pkg_add -aI -Drepair llvm-15.0.7
>>> Running show-prepare-results in devel/include-what-you-use at 1676473507.45
===> devel/include-what-you-use
===> include-what-you-use-0.19 depends on: llvm->=13.0.0 -> llvm-15.0.7
===> include-what-you-use-0.19 depends on: cmake-* -> cmake-3.25.2v0
===> include-what-you-use-0.19 depends on: ninja-* -> ninja-1.11.1
===> Verifying specs: c++ c++abi pthread c clang-cpp m pthread
===> found c++.9.0 c++abi.6.0 pthread.27.0 c.97.0 clang-cpp.1.0 m.10.1
cmake-3.25.2v0
llvm-15.0.7
ninja-1.11.1
(Junk lock released for i386-2 at 1676473508.33)
distfiles size=747285
>>> Running patch in devel/include-what-you-use at 1676473508.35
===> devel/include-what-you-use
===> Checking files for include-what-you-use-0.19
install: /mnt/distfiles: Operation not permitted
>> Fetch
>> https://include-what-you-use.org/downloads/include-what-you-use-0.19.src.tar.gz
ftp: include-what-you-use.org: no address associated with name
>> Fetch
>> https://ftp.openbsd.org/pub/OpenBSD/distfiles/include-what-you-use-0.19.src.tar.gz
ftp: ftp.openbsd.org: no address associated with name
>> Fetch
>> https://ftp.usa.openbsd.org/pub/OpenBSD/distfiles/include-what-you-use-0.19.src.tar.gz
ftp: ftp.usa.openbsd.org: no address associated with name
>> Fetch
>> https://ftp.fr.openbsd.org/pub/OpenBSD/distfiles/include-what-you-use-0.19.src.tar.gz
ftp: ftp.fr.openbsd.org: no address associated with name
*** Error 1 in devel/include-what-you-use
(/usr/ports/infrastructure/mk/bsd.port.mk:3198
'/mnt/distfiles/include-what-you-use-0.19.src.tar.gz')
*** Error 2 in devel/include-what-you-use
(/usr/ports/infrastructure/mk/bsd.port.mk:2474 '_internal-fetch': @cd
/usr/ports/devel/include-wha...)
*** Error 2 in devel/include-what-you-use
(/usr/ports/infrastructure/mk/bsd.port.mk:2694
'/pobj/include-what-you-use-0.19/.extract_done': @c...)
*** Error 2 in devel/include-what-you-use
(/usr/ports/infrastructure/mk/bsd.port.mk:2600 'patch':
@lock=include-what-you-use-0.19; export _...)
===> Exiting devel/include-what-you-use with an error
*** Error 1 in /usr/ports (infrastructure/mk/bsd.port.subdir.mk:137 'patch': @:
${echo_msg:=echo}; : ${target:=patch}; for i in ; do eval...)
>>> Ended at 1676473508.65
max_stuck=0.00/depends=3.64/show-prepare-results=0.90/patch=0.31
Error: job failed with 512 on i386-2 at 1676473508
sparc64 bulk build report
Bulk build on sparc64-0a.ports.openbsd.org Started : Tue Feb 14 16:46:44 MST 2023 Finished: Wed Feb 15 07:38:43 MST 2023 Duration: 0 Days 14 hours 52 minutes Built using OpenBSD 7.2-current (GENERIC.MP) #1662: Tue Feb 14 12:34:06 MST 2023 Built 5586 packages Number of packages built each day: Feb 14: 4473 Feb 15: 1113 Critical path missing pkgs: http://build-failures.rhaalovely.net/sparc64/2023-02-14/summary.log Build failures: 8 http://build-failures.rhaalovely.net/sparc64/2023-02-14/devel/autoconf/2.67.log http://build-failures.rhaalovely.net/sparc64/2023-02-14/devel/avr/gcc.log http://build-failures.rhaalovely.net/sparc64/2023-02-14/devel/quirks.log http://build-failures.rhaalovely.net/sparc64/2023-02-14/devel/robsd.log http://build-failures.rhaalovely.net/sparc64/2023-02-14/lang/guile3.log http://build-failures.rhaalovely.net/sparc64/2023-02-14/mail/mdsort.log http://build-failures.rhaalovely.net/sparc64/2023-02-14/sysutils/py-packaging,python3.log http://build-failures.rhaalovely.net/sparc64/2023-02-14/sysutils/u-boot-asahi.log
Re: NEW: databases/puppetdb and sysutils/puppetserver 7.X
On 2/14/23 21:07, Sebastian Reitenbach wrote: On Sunday, February 12, 2023 10:36 CET, Giovanni Bechis wrote: On Sat, Feb 11, 2023 at 10:12:25PM +0100, Sebastian Reitenbach wrote: 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. does this mean we have to keep facter port updated to latest version on -stable as well until code will be committed upstream ? Otherwise I think bootstrap might break. I tried to address the issue with an updated README. Hope that should be OK? now? yes, ok giovanni@ Cheers Giovanni Sebastian Giovanni 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 --- 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 +++ distinfo1
Re: [maintainer update] net/headscale 0.20.0
On 2023/02/14 21:30:02 +0100, Laurent Cheylus wrote:
> Hi,
>
> update for net/headscale to the latest version 0.20.0
>
> Changelog for major version 0.20.0 :
> https://github.com/juanfont/headscale/releases/tag/v0.20.0
>
> - Update Makefile to install only headscale binary in ${PREFIX}/bin
that's because now there's a cmd/gh-action-integration-generator and
go.port.mk tries to be smart and build everything under
cmd/... (ignoring ALL_TARGET)
instead of overriding do-install another option would be to use a
do-build like:
do-build
cd ${WRKSRC} && ${MODGO_BUILD_TARGET}
like devel/go-tools does. would avoid building extra stuff not
needed. (granted, in this case gh-action-integration-generator is
small and doesn't introduce dependencies.)
> - Update pkg/MESSAGE and pkg/README for modification in version 0.19.0
> (keyword Namespace replaced by User), see
> https://github.com/juanfont/headscale/releases/tag/v0.19.0
MESSAGE is only showed at package install time. If backing up the
database before the update is not an usual step, I'd move that to
current.html.
other that that, diff looks fine and builds for me, but haven't tested
since I don't use it, was just curious about the custom do-build.
