Re: aarch64 bulk build report
On 2023 Jul 24 (Mon) at 15:25:14 -0600 (-0600), phess...@openbsd.org wrote: :bulk build on arm64.ports.openbsd.org :started on Sat Jul 22 07:47:34 MDT 2023 :finished at Mon Jul 24 15:25:01 MDT 2023 :lasted 2D07h37m :done with kern.version=OpenBSD 7.3-current (GENERIC.MP) #2203: Sat Jul 22 00:42:20 MDT 2023 : :built packages:11641 :Jul 22:3801 :Jul 23:1725 :Jul 24:6114 : : :critical path missing pkgs: http://build-failures.rhaalovely.net/aarch64/2023-07-22/summary.log : :build failures: 3 :http://build-failures.rhaalovely.net/aarch64/2023-07-22/games/lwjgl3.log :http://build-failures.rhaalovely.net/aarch64/2023-07-22/graphics/evince,light.log [231/310] /usr/local/bin/gi-docgen generate --quiet --fatal-warnings --config=help/reference/libdocument/libevdocument.toml --output-dir=help/reference/libdocument/libevdocument --no-namespace-dir --content-dir=/usr/obj/ports/evince-44.3-light/evince-44.3/help/reference/libdocument libdocument/EvinceDocument-3.0.gir FAILED: help/reference/libdocument/libevdocument /usr/local/bin/gi-docgen generate --quiet --fatal-warnings --config=help/reference/libdocument/libevdocument.toml --output-dir=help/reference/libdocument/libevdocument --no-namespace-dir --content-dir=/usr/obj/ports/evince-44.3-light/evince-44.3/help/reference/libdocument libdocument/EvinceDocument-3.0.gir WARNING: Unable to process dot data: [Errno 2] No such file or directory: 'dot' missing BDEP on math/graphviz ? :http://build-failures.rhaalovely.net/aarch64/2023-07-22/x11/qt5/qtwebengine.log : :recurrent failures : failures/games/lwjgl3.log : failures/x11/qt5/qtwebengine.log :new failures :+++ ls-failuresMon Jul 24 15:25:13 2023 :+failures/graphics/evince,light.log -- We can predict everything, except the future.
Re: [new] games/dsda-doom
On Wed, Jul 19, 2023 at 06:33:52PM -0300, Lucas de Sena wrote:
> DSDA-Doom is a new doom source port.
>
> The port is building fine here with the patch I added.
>
> Ok?
A few comments/requests:
1. There are dependencies/WANTLIBS missing:
$ make port-lib-depends-check
dsda-doom-0.26.2(games/dsda-doom):
Missing: c++.9 (/usr/local/bin/dsda-doom) (system lib)
Missing: c++abi.6 (/usr/local/bin/dsda-doom) (system lib)
Missing lib: mad.2 (/usr/local/bin/dsda-doom) (NOT REACHABLE)
Missing: ogg.6 from libogg-1.3.5 (/usr/local/bin/dsda-doom)
Missing lib: portmidi.0 (/usr/local/bin/dsda-doom) (NOT REACHABLE)
Missing lib: vorbis.9 (/usr/local/bin/dsda-doom) (NOT REACHABLE)
Missing lib: vorbisfile.6 (/usr/local/bin/dsda-doom) (NOT REACHABLE)
Missing: z.7 (/usr/local/bin/dsda-doom) (system lib)
Missing lib: zip.4 (/usr/local/bin/dsda-doom) (NOT REACHABLE)
WANTLIB += ${COMPILER_LIBCXX} ogg z
2. I would prefer to make the use of tabs more uniform in Makefile, as
in that they start the values at about the same tab marker.
3. What is the value of disabling fluidsynth in the Makefile? We have
it in ports...
[maintainer update] archivers/zpaqfranz-58.7
This time (the previous one was not too long ago, I know…), no obvious bugfixes, but a metric ton of new features, it seems. As always, roughly tested on amd64. Patch attached. diff --git a/archivers/zpaqfranz/Makefile b/archivers/zpaqfranz/Makefile index 95cd8dd9865..56aa180098f 100644 --- a/archivers/zpaqfranz/Makefile +++ b/archivers/zpaqfranz/Makefile @@ -4,7 +4,7 @@ COMMENT = journaling archiver for incremental backup, fork of ZPAQ GH_ACCOUNT = fcorbelli GH_PROJECT = zpaqfranz -GH_TAGNAME = 58.6 +GH_TAGNAME = 58.7 CATEGORIES = archivers MAINTAINER = tux0r diff --git a/archivers/zpaqfranz/distinfo b/archivers/zpaqfranz/distinfo index 8cde57ed555..bf0d1db8708 100644 --- a/archivers/zpaqfranz/distinfo +++ b/archivers/zpaqfranz/distinfo @@ -1,2 +1,2 @@ -SHA256 (zpaqfranz-58.6.tar.gz) = pYdAbyrKkiFXgbIj5SEWls8kD5E64sJ589+hIO0i/oc= -SIZE (zpaqfranz-58.6.tar.gz) = 5297615 +SHA256 (zpaqfranz-58.7.tar.gz) = yjsrpErgMvfGic7hxiC3JL4VmGQEwR7gKX0y31Pr8Uo= +SIZE (zpaqfranz-58.7.tar.gz) = 5300866
Re: [update] audio/ncspot to 0.13.4
On Mon, Jul 24, 2023 at 03:57:16PM +0200, Henrik Friedrichsen wrote: > Attached diff updates audio/ncspot to 0.13.4. > > Tested on amd64. > > Changelog: https://github.com/hrkfdn/ncspot/releases/tag/v0.13.4 tested and works on arm64 as well. committed, thanks!
CVS: cvs.openbsd.org: ports
CVSROOT:/cvs Module name:ports Changes by: lr...@cvs.openbsd.org 2023/07/24 16:14:10 Modified files: audio/ncspot : Makefile crates.inc distinfo Log message: audio/ncspot: update to 0.13.4 Tested on amd64 and arm64 Changelog: https://github.com/hrkfdn/ncspot/releases/tag/v0.13.4 from MAINTAINER
CVS: cvs.openbsd.org: ports
CVSROOT:/cvs Module name:ports Changes by: bl...@cvs.openbsd.org 2023/07/24 15:53:19 Modified files: misc/p5-OPCUA-Open62541: Makefile distinfo Log message: update p5-OPCUA-Open62541 to 2.02
aarch64 bulk build report
bulk build on arm64.ports.openbsd.org started on Sat Jul 22 07:47:34 MDT 2023 finished at Mon Jul 24 15:25:01 MDT 2023 lasted 2D07h37m done with kern.version=OpenBSD 7.3-current (GENERIC.MP) #2203: Sat Jul 22 00:42:20 MDT 2023 built packages:11641 Jul 22:3801 Jul 23:1725 Jul 24:6114 critical path missing pkgs: http://build-failures.rhaalovely.net/aarch64/2023-07-22/summary.log build failures: 3 http://build-failures.rhaalovely.net/aarch64/2023-07-22/games/lwjgl3.log http://build-failures.rhaalovely.net/aarch64/2023-07-22/graphics/evince,light.log http://build-failures.rhaalovely.net/aarch64/2023-07-22/x11/qt5/qtwebengine.log recurrent failures failures/games/lwjgl3.log failures/x11/qt5/qtwebengine.log new failures +++ ls-failures Mon Jul 24 15:25:13 2023 +failures/graphics/evince,light.log resolved failures --- ../old/aarch64/last//ls-failuresFri Jul 21 00:22:57 2023 -failures/archivers/zziplib.log -failures/audio/adplay.log -failures/audio/audiality2.log -failures/audio/schismtracker.log -failures/devel/codeblocks.log -failures/devel/sdl2-gfx.log -failures/devel/sdl2-image.log -failures/devel/sdl2-mixer.log -failures/devel/sdl2-net.log -failures/devel/sdl2-pango.log -failures/devel/sdl2-ttf.log -failures/devel/smpeg2.log -failures/emulators/advancemame.log -failures/emulators/emulationstation.log -failures/emulators/fs-uae.log -failures/emulators/fuse.log -failures/emulators/mednafen.log -failures/emulators/mupen64plus/ui-console.log -failures/emulators/mupen64plus/video-glide64mk2.log -failures/emulators/nestopia.log -failures/emulators/qemu,-ga.log -failures/emulators/sameboy,-libretro.log -failures/emulators/snes9x.log -failures/emulators/stella.log -failures/emulators/vbam.log -failures/games/bzflag.log -failures/games/eduke32.log -failures/games/endless-sky.log -failures/games/ezquake.log -failures/games/freeorion.log -failures/games/love/0.10.log -failures/games/love/11.log -failures/games/lugaru.log -failures/games/nblood.log -failures/games/openrct2.log -failures/games/postal.log -failures/games/quakespasm.log -failures/games/scummvm.log -failures/games/sdl-jstest.log -failures/games/teeworlds.log -failures/games/tic80.log -failures/games/uqm/uqm.log -failures/games/vkquake.log -failures/games/wrath.log -failures/games/zelda3.log -failures/geo/spatialite/gui.log -failures/graphics/ffmpeg.log -failures/graphics/libqrencode.log -failures/net/filezilla.log -failures/net/lagrange.log -failures/x11/kde-applications/kitinerary.log -failures/x11/qt5/qtgamepad.log
CVS: cvs.openbsd.org: ports
CVSROOT:/cvs Module name:ports Changes by: j...@cvs.openbsd.org2023/07/24 14:25:32 Modified files: lang/php/8.1/patches: patch-configure_ac lang/php/8.2/patches: patch-configure_ac Log message: Stop requiring libatomic on riscv64 Drop autoconf goo added for gcc <= 12.2, which falls back to an __atomic_exchange_1 library call for atomic ops on bytes on riscv64. At least clang-13 doesn't need this, but the AC_CHECK_LIB() autoconf check is too naive to notice. Similar to AC_SEARCH_LIBS(), PHP_CHECK_FUNC() only calls PHP_ADD_LIBRARY() if an additional library is needed to resolve the looked up symbol.. Upstream original PR: https://github.com/php/php-src/pull/11321 ok sthen@ (maintainer)
CVS: cvs.openbsd.org: ports
CVSROOT:/cvs Module name:ports Changes by: st...@cvs.openbsd.org 2023/07/24 14:21:46 Modified files: sysutils/firmware/amd: Tag: OPENBSD_7_3 Makefile Log message: tweak comment
CVS: cvs.openbsd.org: ports
CVSROOT:/cvs Module name:ports Changes by: st...@cvs.openbsd.org 2023/07/24 14:21:30 Modified files: sysutils/firmware/amd: Tag: OPENBSD_7_2 Makefile Log message: tweak comment
CVS: cvs.openbsd.org: ports
CVSROOT:/cvs Module name:ports Changes by: st...@cvs.openbsd.org 2023/07/24 14:21:16 Modified files: sysutils/firmware/amd: Makefile Log message: tweak comment
CVS: cvs.openbsd.org: ports
CVSROOT:/cvs Module name:ports Changes by: st...@cvs.openbsd.org 2023/07/24 14:20:35 Modified files: sysutils/firmware: Tag: OPENBSD_7_2 Makefile Added files: sysutils/firmware/amd: Tag: OPENBSD_7_2 Makefile distinfo sysutils/firmware/amd/pkg: Tag: OPENBSD_7_2 DESCR PLIST Log message: add new amd microcode to 7.2-stable
CVS: cvs.openbsd.org: ports
CVSROOT:/cvs Module name:ports Changes by: st...@cvs.openbsd.org 2023/07/24 14:19:00 Modified files: sysutils/firmware: Tag: OPENBSD_7_3 Makefile Added files: sysutils/firmware/amd: Tag: OPENBSD_7_3 Makefile distinfo sysutils/firmware/amd/pkg: Tag: OPENBSD_7_3 DESCR PLIST Log message: add new amd microcode to 7.3-stable
Re: [new] security/py-omemo-dr
On 2023/07/24 18:10, Paco Esteban wrote: > Hi ports@, > > This is a new python library port, security/py-omemo-dr > It's Gajim's internal fork of security/py-axolotl which they have > re-written for internal omemo support. > > It's needed for the update of net/gajim sent on another thread. > > comments ? suggestions ? Ok to import ? > > -- > Paco Esteban. > 0x5818130B8A6DBC03 DESCR is a bit wide (>80 columns), otherwise ok
arm64 BTI support for mpg123
This port has some infrastructure to use an optimized function that uses a function pointer. Not sure why for arm64 it actually uses that infrastructure, since the only alternative is the generic C implementation. But adding a BTI instruction is the easiest fix. ok? Index: audio/mpg123/Makefile === RCS file: /cvs/ports/audio/mpg123/Makefile,v retrieving revision 1.116 diff -u -p -r1.116 Makefile --- audio/mpg123/Makefile 30 Mar 2023 12:35:39 - 1.116 +++ audio/mpg123/Makefile 24 Jul 2023 19:23:10 - @@ -1,6 +1,7 @@ COMMENT= fast console MPEG audio player and decoder library DISTNAME= mpg123-1.31.3 +REVISION= 0 SHARED_LIBS= mpg123 7.2 # 47.0 SHARED_LIBS+= out123 2.1 # 4.7 SHARED_LIBS+= syn123 0.1 # 1.5 Index: audio/mpg123/patches/patch-src_libmpg123_dct36_neon64_S === RCS file: audio/mpg123/patches/patch-src_libmpg123_dct36_neon64_S diff -N audio/mpg123/patches/patch-src_libmpg123_dct36_neon64_S --- /dev/null 1 Jan 1970 00:00:00 - +++ audio/mpg123/patches/patch-src_libmpg123_dct36_neon64_S 24 Jul 2023 19:23:10 - @@ -0,0 +1,11 @@ +Index: src/libmpg123/dct36_neon64.S +--- src/libmpg123/dct36_neon64.S.orig src/libmpg123/dct36_neon64.S +@@ -49,6 +49,7 @@ dct36_aarch64_COS9: + .type ASM_NAME(dct36_neon64), %function + #endif + ASM_NAME(dct36_neon64): ++ bti c + adrpx5, AARCH64_PCREL_HI(dct36_aarch64_COS9) + add x5, x5, AARCH64_PCREL_LO(dct36_aarch64_COS9) + cmeqv28.16b, v28.16b, v28.16b
CVS: cvs.openbsd.org: ports
CVSROOT:/cvs Module name:ports Changes by: ajacou...@cvs.openbsd.org 2023/07/24 12:22:12 Modified files: devel/liblouis : Makefile distinfo devel/liblouis/patches: patch-python_louis_Makefile_in Log message: Update to liblouis-3.26.0.
Re: [new] security/py-omemo-dr
On Mon, 24 Jul 2023, Paco Esteban wrote: > Hi ports@, > > This is a new python library port, security/py-omemo-dr > It's Gajim's internal fork of security/py-axolotl which they have > re-written for internal omemo support. > > It's needed for the update of net/gajim sent on another thread. > > comments ? suggestions ? Ok to import ? I forgot to mention that builds, passes tests and works for me with the new version of gajim on amd64. -- Paco Esteban. 0x5818130B8A6DBC03
maintainer update net/gajim --> 1.8.0
Hi ports@,
This is an update of net/gajim to its latest version 1.8.0
One of the big changes in this release is that they integrated the OMEMO
encryption plugin into gajim. This needs a new library I ported and
sent to the list in a separate thread.
Everything works fine for me on amd64 but emojis (which did not work
before anyway). I have to admit I did not pay much attention to the
emoji thing as I rarely use them. Open to suggestions and diffs.
Ok to commit ?
diff /usr/ports
commit - 7576a667635a8d09d0105d47f5bc52d1f6551ff6
path + /usr/ports
blob - 2423227aa6ce327008e6b45f0b594ac91d1b7a3d
file + net/gajim/Makefile
--- net/gajim/Makefile
+++ net/gajim/Makefile
@@ -1,5 +1,5 @@
COMMENT= fully-featured XMPP client written in Python
-MODPY_EGG_VERSION= 1.7.3
+MODPY_EGG_VERSION= 1.8.0
DISTNAME= gajim-${MODPY_EGG_VERSION}
CATEGORIES=net x11
@@ -25,11 +25,13 @@ RUN_DEPENDS=audio/gsound \
devel/py-gobject3 \
graphics/py-Pillow${MODPY_FLAVOR} \
graphics/py-cairo${MODPY_FLAVOR} \
- net/py-nbxmpp${MODPY_FLAVOR}>=4.2.2 \
+ graphics/py-qrcode${MODPY_FLAVOR}>=7.3.1 \
+ net/py-nbxmpp${MODPY_FLAVOR}>=4.3.0 \
security/py-cryptodome${MODPY_FLAVOR} \
security/py-cryptography${MODPY_FLAVOR} \
security/py-gnupg${MODPY_FLAVOR} \
security/py-keyring${MODPY_FLAVOR} \
+ security/py-omemo-dr${MODPY_FLAVOR}>=1.0.0 \
security/py-openssl${MODPY_FLAVOR} \
sysutils/py-packaging${MODPY_FLAVOR} \
textproc/gspell \
blob - 4720948e2d9b00d96b59478c59c193e5a81efdc0
file + net/gajim/distinfo
--- net/gajim/distinfo
+++ net/gajim/distinfo
@@ -1,2 +1,2 @@
-SHA256 (gajim-1.7.3.tar.gz) = t8yzWfdsY8pXye7Dn5hME0bOHgf+MzuyVY3hweXc0xg=
-SIZE (gajim-1.7.3.tar.gz) = 3753831
+SHA256 (gajim-1.8.0.tar.gz) = EgH8mt0am2l9z4csGHH6rpLqTzFiBRzOPB4NCEP8TUM=
+SIZE (gajim-1.8.0.tar.gz) = 3835799
blob - 66cec1e4a1a5001cef6f45a918298a514babbeae
file + net/gajim/pkg/PLIST
--- net/gajim/pkg/PLIST
+++ net/gajim/pkg/PLIST
@@ -208,6 +208,8 @@ lib/python${MODPY_VERSION}/site-packages/gajim/common/
lib/python${MODPY_VERSION}/site-packages/gajim/common/modules/${MODPY_PYCACHE}misc.${MODPY_PYC_MAGIC_TAG}pyc
lib/python${MODPY_VERSION}/site-packages/gajim/common/modules/${MODPY_PYCACHE}muc.${MODPY_PYC_MAGIC_TAG}${MODPY_PYOEXTENSION}
lib/python${MODPY_VERSION}/site-packages/gajim/common/modules/${MODPY_PYCACHE}muc.${MODPY_PYC_MAGIC_TAG}pyc
+lib/python${MODPY_VERSION}/site-packages/gajim/common/modules/${MODPY_PYCACHE}omemo.${MODPY_PYC_MAGIC_TAG}${MODPY_PYOEXTENSION}
+lib/python${MODPY_VERSION}/site-packages/gajim/common/modules/${MODPY_PYCACHE}omemo.${MODPY_PYC_MAGIC_TAG}pyc
lib/python${MODPY_VERSION}/site-packages/gajim/common/modules/${MODPY_PYCACHE}pep.${MODPY_PYC_MAGIC_TAG}${MODPY_PYOEXTENSION}
lib/python${MODPY_VERSION}/site-packages/gajim/common/modules/${MODPY_PYCACHE}pep.${MODPY_PYC_MAGIC_TAG}pyc
lib/python${MODPY_VERSION}/site-packages/gajim/common/modules/${MODPY_PYCACHE}ping.${MODPY_PYC_MAGIC_TAG}${MODPY_PYOEXTENSION}
@@ -272,6 +274,7 @@ lib/python${MODPY_VERSION}/site-packages/gajim/common/
lib/python${MODPY_VERSION}/site-packages/gajim/common/modules/message.py
lib/python${MODPY_VERSION}/site-packages/gajim/common/modules/misc.py
lib/python${MODPY_VERSION}/site-packages/gajim/common/modules/muc.py
+lib/python${MODPY_VERSION}/site-packages/gajim/common/modules/omemo.py
lib/python${MODPY_VERSION}/site-packages/gajim/common/modules/pep.py
lib/python${MODPY_VERSION}/site-packages/gajim/common/modules/ping.py
lib/python${MODPY_VERSION}/site-packages/gajim/common/modules/presence.py
@@ -317,11 +320,14 @@ lib/python${MODPY_VERSION}/site-packages/gajim/common/
lib/python${MODPY_VERSION}/site-packages/gajim/common/storage/${MODPY_PYCACHE}draft.${MODPY_PYC_MAGIC_TAG}pyc
lib/python${MODPY_VERSION}/site-packages/gajim/common/storage/${MODPY_PYCACHE}events.${MODPY_PYC_MAGIC_TAG}${MODPY_PYOEXTENSION}
lib/python${MODPY_VERSION}/site-packages/gajim/common/storage/${MODPY_PYCACHE}events.${MODPY_PYC_MAGIC_TAG}pyc
+lib/python${MODPY_VERSION}/site-packages/gajim/common/storage/${MODPY_PYCACHE}omemo.${MODPY_PYC_MAGIC_TAG}${MODPY_PYOEXTENSION}
+lib/python${MODPY_VERSION}/site-packages/gajim/common/storage/${MODPY_PYCACHE}omemo.${MODPY_PYC_MAGIC_TAG}pyc
lib/python${MODPY_VERSION}/site-packages/gajim/common/storage/archive.py
lib/python${MODPY_VERSION}/site-packages/gajim/common/storage/base.py
lib/python${MODPY_VERSION}/site-packages/gajim/common/storage/cache.py
lib/python${MODPY_VERSION}/site-packages/gajim/common/storage/draft.py
lib/python${MODPY_VERSION}/site-packages/gajim/common/storage/events.py
+lib/python${MODPY_VERSION}/site-packages/gajim/common/storage/omemo.py
lib/python${MODPY_VERSION}/site-packages/gajim/common/structs.py
lib/python${MODPY_VERSION}/site-packages/gajim/common/styling.py
maintainer update net/py-nbxmpp --> 4.3.1
Hi ports@,
This is an update of net/py-nbxmpp to its latest version 4.3.1
It's needed for an update of net/gajim sent on another thread.
All tests pass and works fine for me on amd64
Ok to commit ?
diff /usr/ports
commit - 7576a667635a8d09d0105d47f5bc52d1f6551ff6
path + /usr/ports
blob - 3adb6b60ead57dd2596f90fb70ade608db12cc7f
file + net/py-nbxmpp/Makefile
--- net/py-nbxmpp/Makefile
+++ net/py-nbxmpp/Makefile
@@ -1,6 +1,6 @@
COMMENT = Python XMPP and Jabber implementation
-MODPY_EGG_VERSION =4.2.2
+MODPY_EGG_VERSION =4.3.1
DISTNAME = nbxmpp-${MODPY_EGG_VERSION}
PKGNAME = py-${DISTNAME}
CATEGORIES = net devel
blob - 8701cc0d484b7928483393405eb166371b32e507
file + net/py-nbxmpp/distinfo
--- net/py-nbxmpp/distinfo
+++ net/py-nbxmpp/distinfo
@@ -1,2 +1,2 @@
-SHA256 (nbxmpp-4.2.2.tar.gz) = hvSIVtrwV3l/+WPtdUKvxsZEoN5m9hdxho1GuY33tiQ=
-SIZE (nbxmpp-4.2.2.tar.gz) = 166998
+SHA256 (nbxmpp-4.3.1.tar.gz) = 0P+ooApV6isy1z0ru/402BplkbkltESPgA8GHyehDgg=
+SIZE (nbxmpp-4.3.1.tar.gz) = 169229
blob - 6837675d98761c99d5f02f2255759b20caafdc73
file + net/py-nbxmpp/pkg/PLIST
--- net/py-nbxmpp/pkg/PLIST
+++ net/py-nbxmpp/pkg/PLIST
@@ -60,6 +60,8 @@ lib/python${MODPY_VERSION}/site-packages/nbxmpp/addres
lib/python${MODPY_VERSION}/site-packages/nbxmpp/${MODPY_PYCACHE}util.${MODPY_PYC_MAGIC_TAG}pyc
lib/python${MODPY_VERSION}/site-packages/nbxmpp/${MODPY_PYCACHE}websocket.${MODPY_PYC_MAGIC_TAG}${MODPY_PYOEXTENSION}
lib/python${MODPY_VERSION}/site-packages/nbxmpp/${MODPY_PYCACHE}websocket.${MODPY_PYC_MAGIC_TAG}pyc
+lib/python${MODPY_VERSION}/site-packages/nbxmpp/${MODPY_PYCACHE}xmppiri.${MODPY_PYC_MAGIC_TAG}${MODPY_PYOEXTENSION}
+lib/python${MODPY_VERSION}/site-packages/nbxmpp/${MODPY_PYCACHE}xmppiri.${MODPY_PYC_MAGIC_TAG}pyc
lib/python${MODPY_VERSION}/site-packages/nbxmpp/addresses.py
lib/python${MODPY_VERSION}/site-packages/nbxmpp/c14n.py
lib/python${MODPY_VERSION}/site-packages/nbxmpp/client.py
@@ -297,3 +299,4 @@ lib/python${MODPY_VERSION}/site-packages/nbxmpp/websoc
lib/python${MODPY_VERSION}/site-packages/nbxmpp/types.py
lib/python${MODPY_VERSION}/site-packages/nbxmpp/util.py
lib/python${MODPY_VERSION}/site-packages/nbxmpp/websocket.py
+lib/python${MODPY_VERSION}/site-packages/nbxmpp/xmppiri.py
--
Paco Esteban.
0x5818130B8A6DBC03
[new] security/py-omemo-dr
Hi ports@, This is a new python library port, security/py-omemo-dr It's Gajim's internal fork of security/py-axolotl which they have re-written for internal omemo support. It's needed for the update of net/gajim sent on another thread. comments ? suggestions ? Ok to import ? -- Paco Esteban. 0x5818130B8A6DBC03 py-omemo-dr.tar.gz Description: application/tar-gz
CVS: cvs.openbsd.org: ports
CVSROOT:/cvs Module name:ports Changes by: lan...@cvs.openbsd.org 2023/07/24 08:56:53 Modified files: mail/meli : Makefile crates.inc distinfo mail/meli/pkg : PLIST Removed files: mail/meli/patches: patch-modcargo-crates_libc-0_2_126_src_unix_bsd_netbsdlike_openbsd_mod_rs Log message: mail/meli: update to a newer git snapshot on top of 0.7.3 supposedly fixes jmap per https://git.meli.delivery/meli/meli/issues/197 but havent been able to test yet. install sample config & themes.
CVS: cvs.openbsd.org: ports
CVSROOT:/cvs Module name:ports Changes by: rsadow...@cvs.openbsd.org 2023/07/24 08:38:15 Modified files: x11/kde-plasma : Makefile.inc x11/kde-plasma/breeze: distinfo x11/kde-plasma/breeze-grub: distinfo x11/kde-plasma/breeze-gtk: distinfo x11/kde-plasma/kdecoration: distinfo x11/kde-plasma/oxygen: distinfo Log message: Update KDE Plasma to 5.27.6
Re: O'Caml and IBT problems?
On 2023/07/24 14:47, Laurence Tratt wrote: > On Mon, Jul 24, 2023 at 01:14:36PM +0100, Stuart Henderson wrote: > > >> On an Intel amd64 machine with the latest snapshot (Jul 24th), net/unison > >> dies for me on startup with the culprit being `caml_startup__code_begin`. > >> I guess this is because O'Caml hasn't been updated sufficiently for IBT? > [...] > > Yes that's exactly it. > > > > I have just committed changes to ocaml ports to use USE_NOBTCFI=Yes to > > disable branch tracking. They can be removed easily if the ocaml compiler > > gains support for generating the landing pad nops. > > Thanks, Stuart -- I can confirm that unison now works with your patches! > > [For anyone who wants to test this, you'll either need to wait for the next > packages snapshot or build a unison package on a non-IBT machine, otherwise > you end up in a bootstrapping problem where the existing ocaml compiler dies > because of IBT and thus can't compile a new version.] ..or build from ports, but you'll need to update at least lang/ocaml, devel/dune and x11/lablgtk3 (in that order) first.
CVS: cvs.openbsd.org: ports
CVSROOT:/cvs Module name:ports Changes by: t...@cvs.openbsd.org2023/07/24 08:16:01 Modified files: devel/cargo: cargo.port.mk Log message: Introduce MODCARGO_INSTALL_TARGET_PATH For virtual manifests, 'cargo install --path .' doesn't work during the 'make fake' step. For this, one needs to be able to specify a path which is typically the name of the executable one wants to package. Lets landry update mail/meli, and will also help sthen with the leftwm wip. fine with semarie ok landry
CVS: cvs.openbsd.org: ports
CVSROOT:/cvs Module name:ports Changes by: rob...@cvs.openbsd.org 2023/07/24 08:15:43 Modified files: www/iridium: Makefile distinfo www/iridium/patches: patch-chrome_common_chrome_paths_cc patch-components_policy_tools_template_writers_writer_configuration_py patch-content_browser_service_worker_service_worker_context_wrapper_cc patch-headless_lib_browser_policy_headless_browser_policy_connector_cc Removed files: www/iridium/patches: patch-chrome_browser_download_bubble_download_bubble_update_service_cc patch-chrome_browser_signin_bound_session_credentials_bound_session_refresh_cookie_fetcher_impl_cc patch-chrome_browser_signin_bound_session_credentials_fake_bound_session_refresh_cookie_fetcher_cc patch-chrome_test_chromedriver_capabilities_cc patch-third_party_blink_renderer_core_html_parser_html_document_parser_fastpath_cc patch-third_party_blink_renderer_modules_canvas_canvas2d_canvas_style_cc Log message: update to 2023.07.115.1
[update] audio/ncspot to 0.13.4
Attached diff updates audio/ncspot to 0.13.4.
Tested on amd64.
Changelog: https://github.com/hrkfdn/ncspot/releases/tag/v0.13.4Index: Makefile
===
RCS file: /cvs/ports/audio/ncspot/Makefile,v
retrieving revision 1.44
diff -u -p -r1.44 Makefile
--- Makefile10 Jul 2023 19:35:12 - 1.44
+++ Makefile24 Jul 2023 13:55:48 -
@@ -7,14 +7,7 @@ COMMENT = ncurses Spotify client
GH_ACCOUNT = hrkfdn
GH_PROJECT = ncspot
-GH_TAGNAME = v0.13.3
-REVISION = 0
-
-MASTER_SITES0 = https://github.com/hrkfdn/ncspot/commit/
-# merged "fix: forward mouse events inside layout"
-# https://github.com/hrkfdn/ncspot/pull/1201
-PATCHFILES = fix-mouse-{}d644397180dc6f90caca656acfdc1e11bb14d281.patch:0
-PATCH_DIST_STRIP = -p1
+GH_TAGNAME = v0.13.4
CATEGORIES = audio
Index: crates.inc
===
RCS file: /cvs/ports/audio/ncspot/crates.inc,v
retrieving revision 1.17
diff -u -p -r1.17 crates.inc
--- crates.inc 26 Jun 2023 22:07:21 - 1.17
+++ crates.inc 24 Jul 2023 13:55:48 -
@@ -1,4 +1,4 @@
-MODCARGO_CRATES += addr2line 0.19.0 # Apache-2.0 OR MIT
+MODCARGO_CRATES += addr2line 0.20.0 # Apache-2.0 OR MIT
MODCARGO_CRATES += adler 1.0.2 # 0BSD OR MIT OR Apache-2.0
MODCARGO_CRATES += aes 0.6.0 # MIT OR Apache-2.0
MODCARGO_CRATES += aes-ctr 0.6.0 # MIT OR Apache-2.0
@@ -11,12 +11,12 @@ MODCARGO_CRATES += alsa-sys0.3.1 # MIT
MODCARGO_CRATES += android-tzdata 0.1.1 # MIT OR Apache-2.0
MODCARGO_CRATES += android_system_properties 0.1.5 # MIT/Apache-2.0
MODCARGO_CRATES += anstream0.3.2 # MIT OR Apache-2.0
-MODCARGO_CRATES += anstyle 1.0.0 # MIT OR Apache-2.0
-MODCARGO_CRATES += anstyle-parse 0.2.0 # MIT OR Apache-2.0
+MODCARGO_CRATES += anstyle 1.0.1 # MIT OR Apache-2.0
+MODCARGO_CRATES += anstyle-parse 0.2.1 # MIT OR Apache-2.0
MODCARGO_CRATES += anstyle-query 1.0.0 # MIT OR Apache-2.0
MODCARGO_CRATES += anstyle-wincon 1.0.1 # MIT OR Apache-2.0
MODCARGO_CRATES += async-broadcast 0.5.1 # MIT OR Apache-2.0
-MODCARGO_CRATES += async-channel 1.8.0 # Apache-2.0 OR MIT
+MODCARGO_CRATES += async-channel 1.9.0 # Apache-2.0 OR MIT
MODCARGO_CRATES += async-executor 1.5.1 # Apache-2.0 OR MIT
MODCARGO_CRATES += async-fs1.6.0 # Apache-2.0 OR MIT
MODCARGO_CRATES += async-io1.13.0 # Apache-2.0 OR MIT
@@ -24,15 +24,16 @@ MODCARGO_CRATES += async-lock 2.7.0 # Ap
MODCARGO_CRATES += async-process 1.7.0 # Apache-2.0 OR MIT
MODCARGO_CRATES += async-recursion 1.0.4 # MIT OR Apache-2.0
MODCARGO_CRATES += async-task 4.4.0 # Apache-2.0 OR MIT
-MODCARGO_CRATES += async-trait 0.1.68 # MIT OR Apache-2.0
+MODCARGO_CRATES += async-trait 0.1.72 # MIT OR Apache-2.0
MODCARGO_CRATES += atomic-waker1.1.1 # Apache-2.0 OR MIT
MODCARGO_CRATES += autocfg 1.1.0 # Apache-2.0 OR MIT
-MODCARGO_CRATES += backtrace 0.3.67 # MIT OR Apache-2.0
+MODCARGO_CRATES += backtrace 0.3.68 # MIT OR Apache-2.0
MODCARGO_CRATES += base64 0.13.1 # MIT/Apache-2.0
MODCARGO_CRATES += base64 0.20.0 # MIT OR Apache-2.0
MODCARGO_CRATES += base64 0.21.2 # MIT OR Apache-2.0
MODCARGO_CRATES += bindgen 0.64.0 # BSD-3-Clause
MODCARGO_CRATES += bitflags1.3.2 # MIT/Apache-2.0
+MODCARGO_CRATES += bitflags2.3.3 # MIT OR Apache-2.0
MODCARGO_CRATES += block 0.1.6 # MIT
MODCARGO_CRATES += block-buffer0.9.0 # MIT OR Apache-2.0
MODCARGO_CRATES += block-buffer0.10.4 # MIT OR Apache-2.0
@@ -48,9 +49,9 @@ MODCARGO_CRATES +=cfg-if 1.0.0 # MIT/Ap
MODCARGO_CRATES += chrono 0.4.26 # MIT/Apache-2.0
MODCARGO_CRATES += cipher 0.2.5 # MIT OR Apache-2.0
MODCARGO_CRATES += clang-sys 1.6.1 # Apache-2.0
-MODCARGO_CRATES += clap4.3.3 # MIT OR Apache-2.0
-MODCARGO_CRATES += clap_builder4.3.3 # MIT OR Apache-2.0
-MODCARGO_CRATES += clap_complete 4.3.1 # MIT OR Apache-2.0
+MODCARGO_CRATES += clap4.3.19 # MIT OR Apache-2.0
+MODCARGO_CRATES += clap_builder4.3.19 # MIT OR Apache-2.0
+MODCARGO_CRATES += clap_complete 4.3.2 # MIT OR Apache-2.0
MODCARGO_CRATES += clap_lex0.5.0 # MIT OR Apache-2.0
MODCARGO_CRATES += clap_mangen 0.2.12 # MIT OR Apache-2.0
MODCARGO_CRATES += clipboard 0.5.0 # MIT / Apache-2.0
@@ -59,15 +60,15 @@ MODCARGO_CRATES += colorchoice 1.0.0 # M
MODCARGO_CRATES += combine 4.6.6 # MIT
MODCARGO_CRATES += concurrent-queue2.2.0 # Apache-2.0 OR MIT
MODCARGO_CRATES += cookie 0.16.2 # MIT OR Apache-2.0
-MODCARGO_CRATES += cookie_store0.19.0 # MIT/Apache-2.0
Re: O'Caml and IBT problems?
On Mon, Jul 24, 2023 at 01:14:36PM +0100, Stuart Henderson wrote: >> On an Intel amd64 machine with the latest snapshot (Jul 24th), net/unison >> dies for me on startup with the culprit being `caml_startup__code_begin`. >> I guess this is because O'Caml hasn't been updated sufficiently for IBT? [...] > Yes that's exactly it. > > I have just committed changes to ocaml ports to use USE_NOBTCFI=Yes to > disable branch tracking. They can be removed easily if the ocaml compiler > gains support for generating the landing pad nops. Thanks, Stuart -- I can confirm that unison now works with your patches! [For anyone who wants to test this, you'll either need to wait for the next packages snapshot or build a unison package on a non-IBT machine, otherwise you end up in a bootstrapping problem where the existing ocaml compiler dies because of IBT and thus can't compile a new version.] Laurie
CVS: cvs.openbsd.org: ports
CVSROOT:/cvs Module name:ports Changes by: st...@cvs.openbsd.org 2023/07/24 07:43:35 Modified files: lang/lucee : Makefile distinfo Log message: update to lucee-5.4.2.17
CVS: cvs.openbsd.org: ports
CVSROOT:/cvs Module name:ports Changes by: st...@cvs.openbsd.org 2023/07/24 06:40:20 Modified files: multimedia/mpv : Makefile distinfo multimedia/mpv/patches: patch-meson_build Removed files: multimedia/mpv/patches: patch-audio_decode_ad_lavc_c patch-audio_decode_ad_spdif_c patch-audio_out_ao_sndio_c patch-common_av_common_c patch-common_av_common_h patch-common_av_log_c patch-common_recorder_c patch-player_lua_ytdl_hook_lua patch-player_main_c patch-sub_lavc_conv_c patch-sub_sd_lavc_c patch-video_decode_vd_lavc_c patch-video_out_vo_gpu_next_c patch-video_sws_utils_c Log message: update to mpv-0.36.0, ok rsadowski
Re: mpv update
On Mon Jul 24, 2023 at 08:59:31AM +0100, Stuart Henderson wrote: > I spotted this one in portroach, haven't tested beyond build yet but > the patch merges are fiddly enough that I thought I'd send it out to > avoid anyone doing duplicate work. Runtime tests welcome! > runs fine, ok rsadowski
CVS: cvs.openbsd.org: ports
CVSROOT:/cvs Module name:ports Changes by: st...@cvs.openbsd.org 2023/07/24 06:16:05 Modified files: lang/ocaml : Makefile Log message: add a comment suggesting removal of USE_NOBTCFI from ocaml.port.mk if the ocaml compiler is fixed for BTI
Re: O'Caml and IBT problems?
On 2023/07/24 12:19, Laurence Tratt wrote: > On an Intel amd64 machine with the latest snapshot (Jul 24th), net/unison > dies for me on startup with the culprit being `caml_startup__code_begin`. I > guess this is because O'Caml hasn't been updated sufficiently for IBT? Here's > what I see: > > $ unison -h > fish: Job 1, 'unison -h' terminated by signal SIGILL (Illegal instruction) > $ gdb unison > GNU gdb 6.3 > Copyright 2004 Free Software Foundation, Inc. > GDB is free software, covered by the GNU General Public License, and you are > welcome to change it and/or distribute copies of it under certain > conditions. > Type "show copying" to see the conditions. > There is absolutely no warranty for GDB. Type "show warranty" for details. > This GDB was configured as "amd64-unknown-openbsd7.3"... > (gdb) run > Starting program: /usr/local/bin/unison > Error while reading shared library symbols: > Dwarf Error: wrong version in compilation unit header (is 4, should be 2) > [in module /usr/libexec/ld.so] > > Program received signal SIGILL, Illegal instruction. > 0x0d8d44d79a30 in caml_startup__code_begin () from /usr/local/bin/unison > > However, Unison on this same snapshot works fine on an AMD amd64 > machine. AFAIK the main difference between the two is the lack of IBT > support on the AMD machine. > > > Laurie > Yes that's exactly it. I have just committed changes to ocaml ports to use USE_NOBTCFI=Yes to disable branch tracking. They can be removed easily if the ocaml compiler gains support for generating the landing pad nops.
CVS: cvs.openbsd.org: ports
CVSROOT:/cvs Module name:ports Changes by: st...@cvs.openbsd.org 2023/07/24 06:12:56 Modified files: devel/cil : Makefile devel/coccinelle: Makefile devel/dune : Makefile devel/frama-c : Makefile devel/ocaml-cppo: Makefile devel/ocaml-graph: Makefile devel/ocaml-menhir: Makefile devel/ocaml-ocamlbuild: Makefile devel/ocaml-parmap: Makefile devel/ocaml-pcre: Makefile devel/ocaml-yojson: Makefile graphics/ocaml-cairo: Makefile graphics/ocaml-graphics: Makefile lang/haxe : Makefile lang/ocaml-camlp4: Makefile lang/ocaml-camlp5: Makefile math/coq : Makefile math/ocaml-num : Makefile math/ocaml-zarith: Makefile net/mldonkey : Makefile net/unison : Makefile textproc/hevea : Makefile x11/kde-applications/kalzium: Makefile x11/lablgtk2 : Makefile x11/lablgtk3 : Makefile Log message: bump REVISION for ports using MODULES=lang/ocaml which have now picked up USE_NOBTCFI
CVS: cvs.openbsd.org: ports
CVSROOT:/cvs Module name:ports Changes by: st...@cvs.openbsd.org 2023/07/24 06:10:32 Modified files: lang/ocaml : ocaml.port.mk Log message: set USE_NOBTCFI for MODULES=lang/ocaml users on native arch
CVS: cvs.openbsd.org: ports
CVSROOT:/cvs Module name:ports Changes by: st...@cvs.openbsd.org 2023/07/24 06:09:40 Modified files: lang/ocaml : Makefile lang/ocaml/pkg : PFRAG.dynlink-native PLIST Log message: set USE_NOBTCFI for lang/ocaml
CVS: cvs.openbsd.org: ports
CVSROOT:/cvs Module name:ports Changes by: st...@cvs.openbsd.org 2023/07/24 05:36:13 Modified files: sysutils/firmware/amd: Makefile distinfo Log message: update to newer amd release for 17h/19h Microcode patches in microcode_amd_fam17h.bin: Family=0x17 Model=0x08 Stepping=0x02: Patch=0x0800820d Length=3200 bytes Family=0x17 Model=0x31 Stepping=0x00: Patch=0x0830107a Length=3200 bytes Family=0x17 Model=0xa0 Stepping=0x00: Patch=0x08a8 Length=3200 bytes Family=0x17 Model=0x01 Stepping=0x02: Patch=0x0800126e Length=3200 bytes Microcode patches in microcode_amd_fam19h.bin: Family=0x19 Model=0x01 Stepping=0x01: Patch=0x0a0011d1 Length=5568 bytes Family=0x19 Model=0x01 Stepping=0x00: Patch=0x0a001079 Length=5568 bytes Family=0x19 Model=0x01 Stepping=0x02: Patch=0x0a001234 Length=5568 bytes
O'Caml and IBT problems?
On an Intel amd64 machine with the latest snapshot (Jul 24th), net/unison dies for me on startup with the culprit being `caml_startup__code_begin`. I guess this is because O'Caml hasn't been updated sufficiently for IBT? Here's what I see: $ unison -h fish: Job 1, 'unison -h' terminated by signal SIGILL (Illegal instruction) $ gdb unison GNU gdb 6.3 Copyright 2004 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type "show copying" to see the conditions. There is absolutely no warranty for GDB. Type "show warranty" for details. This GDB was configured as "amd64-unknown-openbsd7.3"... (gdb) run Starting program: /usr/local/bin/unison Error while reading shared library symbols: Dwarf Error: wrong version in compilation unit header (is 4, should be 2) [in module /usr/libexec/ld.so] Program received signal SIGILL, Illegal instruction. 0x0d8d44d79a30 in caml_startup__code_begin () from /usr/local/bin/unison However, Unison on this same snapshot works fine on an AMD amd64 machine. AFAIK the main difference between the two is the lack of IBT support on the AMD machine. Laurie
CVS: cvs.openbsd.org: ports
CVSROOT:/cvs Module name:ports Changes by: to...@cvs.openbsd.org 2023/07/24 05:17:21 Modified files: x11/qt6/qtmultimedia: Makefile Added files: x11/qt6/qtmultimedia/patches: patch-src_resonance-audio_CMakeLists_txt Log message: Fix build on macppc. CMAKE_SYSTEM_PROCESSOR returns powerpc on OpenBSD. ok kn@ rsadowski@
CVS: cvs.openbsd.org: ports
CVSROOT:/cvs Module name:ports Changes by: to...@cvs.openbsd.org 2023/07/24 05:15:23 ports/x11/qt6/qtmultimedia/patches Update of /cvs/ports/x11/qt6/qtmultimedia/patches In directory cvs.openbsd.org:/tmp/cvs-serv50648/patches Log Message: Directory /cvs/ports/x11/qt6/qtmultimedia/patches added to the repository
答复: [NEW]textproc/typst
ping ... 发件人: owner-po...@openbsd.org 代表 wen heping 发送时间: 2023年7月12日 8:49 收件人: Stuart Henderson 抄送: ports@openbsd.org 主题: 回复: [NEW]textproc/typst Here is the revised patch: i) regen the patch ii) Add the missing LICENSE of all crates Cheers ! wen 发件人: Stuart Henderson 发送时间: 2023年7月11日 19:23 收件人: wen heping 抄送: ports@openbsd.org 主题: Re: [NEW]textproc/typst On 2023/07/11 03:06, wen heping wrote: > Hi, ports@ > >Here is a patch to create new port textproc/typst. > >Typst is a new markup-based typsetting system that is designed to be as > powerful as LaTeX while being much easier to learn and use. Typst has: > Built-in markup for the most common formatting tasks > Flexible functions for everything else > A tightly integrated scripting system > Math typesetting, bibliography management, and more > Fast compile times thanks to incremental compilation > Friendly error messages in case something goes wrong. > >It build and run well on amd64-current system. > > > Cheers ! > wen files in patches/ should be generated using "make update-patches" (if that results in many Cargo.toml.orig patch files, then you should update to a -current ports tree) crates license information is incomplete, possibly because of an unreadable file (no world-read permissions in the tar); use FIX_EXTRACT_PERMISSIONS=Yes and regenerate with make modcargo-gen-crates-licenses
Re: Update lmdb 0.9.31
On Mon, Jul 24 2023, Christopher Zimmermann wrote: > Hi, > > this is a straightforward upgrade containing only small bugfixes. OK? Patch doesn't apply (whitespace) but no need to resend. Please run make update-patches and you get an ok jca@. Thanks! I'll try to fiddle with PORTROACH so that it warns me about future updates. Something like site:https://git.openldap.org/openldap/openldap/-/tags I guess. -- jca | PGP : 0x1524E7EE / 5135 92C1 AD36 5293 2BDF DDCC 0DFA 74AE 1524 E7EE
Re: Gitea 1.20.0
On 2023/07/24 11:49, Stuart Henderson wrote: > On 2023/07/24 13:45, Pavel Korovin wrote: > > Gitea is a go binary, so in most cases the old package won't become > > non-functional very soon. > > It already did for machines with IBT. (not affecting people who are already up-to-date on -current, but will affect people moving from.older -current or 7.3).
Re: Gitea 1.20.0
On 2023/07/24 13:45, Pavel Korovin wrote: > Gitea is a go binary, so in most cases the old package won't become > non-functional very soon. It already did for machines with IBT.
Re: Gitea 1.20.0
On 07/24, Stuart Henderson wrote: > pkg_add -u will display MESSAGE if it changed since the previous version > so the user can easily find information about how to fix it. (The > downside is that it's displayed for new installs with "pkg_add gitea" > too). > > Another way is simply to list changes needed in faq/current.html (which > is usually copied over to the upgrade notes for the next OpenBSD > release). But on an interactive update, this is easier to miss than > MESSAGE. > This situation (upstream requiring config changes) is not uncommon > - unless things are likely to be a real mess we don't normally use > @ask-update for them. > > The problem with @ask-update is that non-interactive updates just skip > updating the relevant package; but sometimes after an OS update the old > package is non-functional too. > > There are some exceptions in-tree: freeradius 2->3 and dovecot 1->2, > where they have multiple configuration files which don't work well > with the @sample mechanism and they had big changes that really needed > attention, at least a backup, before the update. But it seems this is > not really a problem with the changes needed for gitea? Gitea is a go binary, so in most cases the old package won't become non-functional very soon. I'd leave @ask-update with a message like: "gitea-v1.20.0 fails to start if configuration contains deprecated options, make sure your configuration is up-to-date" And leave it for a user to decide about his config. Because: 1) There's a list of deprecated options, and gitea blames those in logs, but still works 2) There are some deprecated options like those in [mailer] section which make gitea silently fail 3) People can use different options in their configs. I cannot test which one will break Gitea this or next time I think it's the app problem, and Gitea devs still din't decide how to fix it, e.g.: https://github.com/go-gitea/gitea/pull/25206#issuecomment-1621292395 I'd better not keep trying to fix in the port the problems which should be fixed in the app itself. -- With best regards, Pavel Korovin
CVS: cvs.openbsd.org: ports
CVSROOT:/cvs Module name:ports Changes by: yasu...@cvs.openbsd.org 2023/07/24 04:16:39 Modified files: devel/quirks : Makefile devel/quirks/files: Quirks.pm Log message: Register removal of sfio. ok tb
Re: Gitea 1.20.0
On 2023/07/24 01:19, Pavel Korovin wrote: > > As I see it, @ask-update is mostly needed where you need to take steps > > _before_ the new version is installed (say, for postgresql if you're in > > a situation where you can't use pg_upgrade, e.g. using an extension, > > you need to run the old version in order to dump the db), Whereas if > > it's steps to be taken after updating, it doesn't really matter if > > people update first, they can still follow them. > > I'm OK with your approach, the only thing which makes me feel bad is > the situation when the user runs 'pkg_add -u' and then finds that gitea > fails to start and something has to be done now to fix it. pkg_add -u will display MESSAGE if it changed since the previous version so the user can easily find information about how to fix it. (The downside is that it's displayed for new installs with "pkg_add gitea" too). Another way is simply to list changes needed in faq/current.html (which is usually copied over to the upgrade notes for the next OpenBSD release). But on an interactive update, this is easier to miss than MESSAGE. This situation (upstream requiring config changes) is not uncommon - unless things are likely to be a real mess we don't normally use @ask-update for them. The problem with @ask-update is that non-interactive updates just skip updating the relevant package; but sometimes after an OS update the old package is non-functional too. There are some exceptions in-tree: freeradius 2->3 and dovecot 1->2, where they have multiple configuration files which don't work well with the @sample mechanism and they had big changes that really needed attention, at least a backup, before the update. But it seems this is not really a problem with the changes needed for gitea?
Update lmdb 0.9.31
Hi,
this is a straightforward upgrade containing only small bugfixes. OK?
Christopher
Index: Makefile
===
RCS file: /cvs/ports/databases/lmdb/Makefile,v
retrieving revision 1.11
diff -u -p -r1.11 Makefile
--- Makefile10 Mar 2022 00:04:05 - 1.11
+++ Makefile24 Jul 2023 09:41:37 -
@@ -1,6 +1,6 @@
COMMENT = Symas Lightning Memory-Mapped Database
-VERSION = 0.9.29
+VERSION = 0.9.31
DISTNAME = openldap-LMDB_${VERSION}
PKGNAME = lmdb-${VERSION}
Index: distinfo
===
RCS file: /cvs/ports/databases/lmdb/distinfo,v
retrieving revision 1.4
diff -u -p -r1.4 distinfo
--- distinfo12 May 2021 23:37:31 - 1.4
+++ distinfo24 Jul 2023 09:41:37 -
@@ -1,2 +1,2 @@
-SHA256 (openldap-LMDB_0.9.29.tar.gz) =
1MZoFnotcD75HbcztAabi3Tbw3RAWFW+Zia0Xip+LdM=
-SIZE (openldap-LMDB_0.9.29.tar.gz) = 144545
+SHA256 (openldap-LMDB_0.9.31.tar.gz) =
011Pb0YxPWL9NCydy/V0QykZzl6ALStsvi69VJgh5cQ=
+SIZE (openldap-LMDB_0.9.31.tar.gz) = 145086
CVS: cvs.openbsd.org: ports
CVSROOT:/cvs Module name:ports Changes by: fcam...@cvs.openbsd.org 2023/07/24 03:42:03 Modified files: graphics/jpegoptim: Makefile distinfo Log message: Update jpegoptim to 1.5.4.
CVS: cvs.openbsd.org: ports
CVSROOT:/cvs Module name:ports Changes by: yasu...@cvs.openbsd.org 2023/07/24 03:40:24 Modified files: devel : Makefile Removed files: devel/sfio : Makefile distinfo devel/sfio/patches: patch-src_lib_sfio_Sfio_t_runtest patch-src_lib_sfio_Sfio_t_sftest_h patch-src_lib_sfio_Sfio_t_terror_h patch-src_lib_sfio_Sfio_t_twhole_c patch-src_lib_sfio_Stdio_b_no_stdio_h patch-src_lib_sfio_Stdio_b_stdstream_c patch-src_lib_sfio_Stdio_t_runtest patch-src_lib_sfio_sffilbuf_c patch-src_lib_sfio_sfputr_c devel/sfio/pkg : DESCR PLIST Log message: Remove text/sfio. Upstream became not active long time ago. None depends this. ok tb sthen jca
Re: Gitea 1.20.0
> On 24 Jul 2023, at 00:19, Pavel Korovin wrote:
>
> On 07/23, Stuart Henderson wrote:
>> On 2023/07/23 16:05, Pavel Korovin wrote:
>>> I think adding @ask-update makes sense only if there's an UPGRADE section in
>>> README describing what setting is deprecated in which version, otherwise
>>> I'll end up with multiple @ask-update for each version, or with @ask-update
>>> for all versions with something misleading like: "check your config for
>>> deprecated settings", but how people will know what's deprecated?
>>
>> Users can't see a new pkg-readme on the running system until they've
>> already agreed to accept the update.
>
> Oops then, my bad :)
>
>> IMHO I would go with 4) - 1) and a short pkg/MESSAGE "if updating from
>> before X.Y, see the pkg-readme for config options which are no longer
>> supported". ("deprecated" is "still work but you should stop using them"
>> rather than "no longer works and things break unless you remove them").
>>
>> As I see it, @ask-update is mostly needed where you need to take steps
>> _before_ the new version is installed (say, for postgresql if you're in
>> a situation where you can't use pg_upgrade, e.g. using an extension,
>> you need to run the old version in order to dump the db), Whereas if
>> it's steps to be taken after updating, it doesn't really matter if
>> people update first, they can still follow them.
>
> I'm OK with your approach, the only thing which makes me feel bad is
> the situation when the user runs 'pkg_add -u' and then finds that gitea
> fails to start and something has to be done now to fix it.
Using MESSAGE makes sense if upstream notifies of upcoming removals pending
deprecation.
I.e. if they deprecate an option but don’t actually error out on it?
> --
> With best regards,
> Pavel Korovin
CVS: cvs.openbsd.org: ports
CVSROOT:/cvs Module name:ports Changes by: fcam...@cvs.openbsd.org 2023/07/24 03:35:55 Modified files: audio/milkytracker: Makefile distinfo audio/milkytracker/patches: patch-src_tracker_sdl_SDL_Main_cpp Log message: Update milkytracker to 1.04.00.
CVS: cvs.openbsd.org: ports
CVSROOT:/cvs Module name:ports Changes by: rob...@cvs.openbsd.org 2023/07/24 03:16:07 Modified files: lang/node : Makefile lang/node/patches: patch-tools_v8_gypfiles_v8_gyp Added files: lang/node/patches: patch-configure_py Log message: unbreak on arm64 where BTI is enforced by doing the following steps: - use openssl/3.1 because that port has all the fixes for BTI - enable v8_control_flow_integrity so that the proper BTI code is used in v8 - include the necessary files for v8_control_flow_integrity on arm64 for v8
mpv update
I spotted this one in portroach, haven't tested beyond build yet but
the patch merges are fiddly enough that I thought I'd send it out to
avoid anyone doing duplicate work. Runtime tests welcome!
Index: Makefile
===
RCS file: /cvs/ports/multimedia/mpv/Makefile,v
retrieving revision 1.97
diff -u -p -r1.97 Makefile
--- Makefile18 Jun 2023 04:46:33 - 1.97
+++ Makefile24 Jul 2023 07:57:41 -
@@ -2,8 +2,7 @@ COMMENT = movie player based on MPlayer
GH_ACCOUNT = mpv-player
GH_PROJECT = mpv
-GH_TAGNAME = v0.35.1
-REVISION = 5
+GH_TAGNAME = v0.36.0
USE_NOBTCFI = Yes
SHARED_LIBS += mpv 1.0 # 2.0
@@ -70,6 +69,7 @@ CONFIGURE_ARGS = -Dlua=lua${MODLUA_DEP_V
-Dd3d11=disabled \
-Dd3d-hwaccel=disabled \
-Ddirect3d=disabled \
+ -Ddmabuf-wayland=disabled \
-Degl-android=disabled \
-Degl-angle=disabled \
-Degl-angle-lib=disabled \
@@ -83,6 +83,7 @@ CONFIGURE_ARGS = -Dlua=lua${MODLUA_DEP_V
-Dios-gl=disabled \
-Djack=disabled \
-Djavascript=disabled \
+ -Dlibplacebo-next=disabled \
-Dmacos-10-11-features=disabled \
-Dmacos-10-12-2-features=disabled \
-Dmacos-10-14-features=disabled \
@@ -112,6 +113,7 @@ CONFIGURE_ARGS =-Dlua=lua${MODLUA_DEP_V
-Dvdpau-gl-x11=disabled \
-Dvideotoolbox-gl=disabled \
-Dvulkan=disabled \
+ -Dvulkan-interop=disabled \
-Dwayland=disabled \
-Dwin32-internal-pthreads=disabled \
-Dwasapi=disabled
Index: distinfo
===
RCS file: /cvs/ports/multimedia/mpv/distinfo,v
retrieving revision 1.33
diff -u -p -r1.33 distinfo
--- distinfo31 Jan 2023 10:19:28 - 1.33
+++ distinfo24 Jul 2023 07:57:41 -
@@ -1,2 +1,2 @@
-SHA256 (mpv-0.35.1.tar.gz) = Qd+YG3uE4zou9EeKr4HW9PXIuc0sDTN6wUL8ILOH0ak=
-SIZE (mpv-0.35.1.tar.gz) = 3367913
+SHA256 (mpv-0.36.0.tar.gz) = KavET46+4BO7L5/hTYCzDbGbU0xnkFbkhRzq31pei/Y=
+SIZE (mpv-0.36.0.tar.gz) = 3409178
Index: patches/patch-audio_decode_ad_lavc_c
===
RCS file: patches/patch-audio_decode_ad_lavc_c
diff -N patches/patch-audio_decode_ad_lavc_c
--- patches/patch-audio_decode_ad_lavc_c30 Jan 2023 16:53:55 -
1.3
+++ /dev/null 1 Jan 1970 00:00:00 -
@@ -1,43 +0,0 @@
-- ffmpeg: update to handle deprecation of `av_init_packet`
- 4574dd5dc6ff75b1fc693afceec59fbcd51ccd4c
-
-Index: audio/decode/ad_lavc.c
audio/decode/ad_lavc.c.orig
-+++ audio/decode/ad_lavc.c
-@@ -46,6 +46,7 @@
- struct priv {
- AVCodecContext *avctx;
- AVFrame *avframe;
-+AVPacket *avpkt;
- struct mp_chmap force_channel_map;
- uint32_t skip_samples, trim_samples;
- bool preroll_done;
-@@ -104,6 +105,7 @@ static bool init(struct mp_filter *da, struct mp_codec
- lavc_context = avcodec_alloc_context3(lavc_codec);
- ctx->avctx = lavc_context;
- ctx->avframe = av_frame_alloc();
-+ctx->avpkt = av_packet_alloc();
- lavc_context->codec_type = AVMEDIA_TYPE_AUDIO;
- lavc_context->codec_id = lavc_codec->id;
- lavc_context->pkt_timebase = ctx->codec_timebase;
-@@ -160,6 +162,7 @@ static void destroy(struct mp_filter *da)
-
- avcodec_free_context(>avctx);
- av_frame_free(>avframe);
-+mp_free_av_packet(>avpkt);
- }
-
- static void reset(struct mp_filter *da)
-@@ -185,10 +188,9 @@ static int send_packet(struct mp_filter *da, struct de
- if (mpkt && priv->next_pts == MP_NOPTS_VALUE)
- priv->next_pts = mpkt->pts;
-
--AVPacket pkt;
--mp_set_av_packet(, mpkt, >codec_timebase);
-+mp_set_av_packet(priv->avpkt, mpkt, >codec_timebase);
-
--int ret = avcodec_send_packet(avctx, mpkt ? : NULL);
-+int ret = avcodec_send_packet(avctx, mpkt ? priv->avpkt : NULL);
- if (ret < 0)
- MP_ERR(da, "Error decoding audio.\n");
- return ret;
Index: patches/patch-audio_decode_ad_spdif_c
===
RCS file: patches/patch-audio_decode_ad_spdif_c
diff -N patches/patch-audio_decode_ad_spdif_c
--- patches/patch-audio_decode_ad_spdif_c 30 Jan 2023 16:53:55 -
1.3
+++ /dev/null 1 Jan 1970 00:00:00 -
@@ -1,53 +0,0 @@
-- ffmpeg: update to handle deprecation of `av_init_packet`
- 4574dd5dc6ff75b1fc693afceec59fbcd51ccd4c
-
-Index: audio/decode/ad_spdif.c
audio/decode/ad_spdif.c.orig
-+++ audio/decode/ad_spdif.c
-@@ -41,6
CVS: cvs.openbsd.org: ports
CVSROOT:/cvs Module name:ports Changes by: rsadow...@cvs.openbsd.org 2023/07/24 00:48:38 Modified files: graphics/kirigami-addons: Makefile distinfo graphics/kirigami-addons/pkg: PLIST Log message: Update kirigami-addons to 0.10.0
CVS: cvs.openbsd.org: ports
CVSROOT:/cvs Module name:ports Changes by: rsadow...@cvs.openbsd.org 2023/07/24 00:38:45 Modified files: graphics/inkscape: Makefile distinfo graphics/inkscape/patches: patch-src_extension_implementation_script_cpp patch-src_path-prefix_cpp graphics/inkscape/pkg: PLIST Log message: Update inkscape to 1.3
CVS: cvs.openbsd.org: ports
CVSROOT:/cvs Module name:ports Changes by: lan...@cvs.openbsd.org 2023/07/24 00:06:37 Modified files: x11/xfce4/xfce4-cpugraph: Makefile distinfo x11/xfce4/xfce4-cpugraph/pkg: PLIST Log message: x11/xfce4/xfce4-cpugraph: update to 1.2.8. settings moved to xfconf. see https://mail.xfce.org/pipermail/xfce-announce/2023-July/001314.html
