UPDATE: xmms2
Here is a diff to backport the support for newer FFmpeg API from the
devel repo.
Index: Makefile
===
RCS file: /cvs/ports/audio/xmms2/Makefile,v
retrieving revision 1.63
diff -u -p -u -p -r1.63 Makefile
--- Makefile21 Feb 2024 19:23:43 - 1.63
+++ Makefile11 May 2024 05:49:55 -
@@ -3,7 +3,7 @@ COMMENT = audio player daemon with libr
V =0.8
DISTNAME = xmms2-${V}DrO_o
PKGNAME = xmms2-${V}
-REVISION = 18
+REVISION = 19
SHARED_LIBS += xmmsclient++2.0 # 4.0.0
SHARED_LIBS += xmmsclient++-glib 1.0 # 1.0.0
Index: patches/patch-src_plugins_avcodec_avcodec_c
===
RCS file: /cvs/ports/audio/xmms2/patches/patch-src_plugins_avcodec_avcodec_c,v
retrieving revision 1.5
diff -u -p -u -p -r1.5 patch-src_plugins_avcodec_avcodec_c
--- patches/patch-src_plugins_avcodec_avcodec_c 11 Mar 2022 18:20:36 -
1.5
+++ patches/patch-src_plugins_avcodec_avcodec_c 11 May 2024 05:49:55 -
@@ -1,7 +1,8 @@
Deal with newer FFmpeg API.
src/plugins/avcodec/avcodec.c.orig Thu Mar 27 01:42:57 2014
-+++ src/plugins/avcodec/avcodec.c Thu Mar 27 01:52:27 2014
+Index: src/plugins/avcodec/avcodec.c
+--- src/plugins/avcodec/avcodec.c.orig
src/plugins/avcodec/avcodec.c
@@ -23,6 +23,7 @@
#include
#include
@@ -10,7 +11,14 @@ Deal with newer FFmpeg API.
#include "avcodec_compat.h"
-@@ -36,6 +37,8 @@ typedef struct {
+@@ -30,12 +31,15 @@
+
+ typedef struct {
+ AVCodecContext *codecctx;
++ AVPacket packet;
+
+ guchar *buffer;
+ guint buffer_length;
guint buffer_size;
gboolean no_demuxer;
@@ -19,7 +27,7 @@ Deal with newer FFmpeg API.
guint channels;
guint samplerate;
xmms_sample_format_t sampleformat;
-@@ -53,10 +56,14 @@ typedef struct {
+@@ -53,10 +57,14 @@ typedef struct {
static gboolean xmms_avcodec_plugin_setup (xmms_xform_plugin_t *xform_plugin);
static gboolean xmms_avcodec_init (xmms_xform_t *xform);
static void xmms_avcodec_destroy (xmms_xform_t *xform);
@@ -34,7 +42,7 @@ Deal with newer FFmpeg API.
/*
* Plugin header
-@@ -85,13 +92,23 @@ xmms_avcodec_plugin_setup (xmms_xform_plugin_t *xform_
+@@ -85,13 +93,23 @@ xmms_avcodec_plugin_setup (xmms_xform_plugin_t *xform_
xmms_magic_add ("A/52 (AC-3) header", "audio/x-ffmpeg-ac3",
"0 beshort 0x0b77", NULL);
xmms_magic_add ("DTS header", "audio/x-ffmpeg-dca",
@@ -59,7 +67,7 @@ Deal with newer FFmpeg API.
return TRUE;
}
-@@ -107,6 +124,7 @@ xmms_avcodec_destroy (xmms_xform_t *xform)
+@@ -107,6 +125,7 @@ xmms_avcodec_destroy (xmms_xform_t *xform)
avcodec_close (data->codecctx);
av_free (data->codecctx);
@@ -67,18 +75,31 @@ Deal with newer FFmpeg API.
g_string_free (data->outbuf, TRUE);
g_free (data->buffer);
-@@ -132,9 +150,10 @@ xmms_avcodec_init (xmms_xform_t *xform)
+@@ -118,7 +137,7 @@ static gboolean
+ xmms_avcodec_init (xmms_xform_t *xform)
+ {
+ xmms_avcodec_data_t *data;
+- AVCodec *codec;
++ const AVCodec *codec;
+ const gchar *mimetype;
+ const guchar *tmpbuf;
+ gsize tmpbuflen;
+@@ -131,12 +150,12 @@ xmms_avcodec_init (xmms_xform_t *xform)
+ data->buffer = g_malloc (AVCODEC_BUFFER_SIZE);
data->buffer_size = AVCODEC_BUFFER_SIZE;
data->codecctx = NULL;
++ data->packet.size = 0;
+ data->read_out_frame = av_frame_alloc ();
+
xmms_xform_private_data_set (xform, data);
- avcodec_init ();
- avcodec_register_all ();
-
+- avcodec_register_all ();
+-
mimetype = xmms_xform_indata_get_str (xform,
+ XMMS_STREAM_TYPE_MIMETYPE);
+ data->codec_id = mimetype + strlen ("audio/x-ffmpeg-");
@@ -161,12 +180,12 @@ xmms_avcodec_init (xmms_xform_t *xform)
data->channels = ret;
}
@@ -326,7 +347,7 @@ Deal with newer FFmpeg API.
}
ret = xmms_xform_seek (xform, samples, whence, err);
-@@ -419,4 +358,179 @@ xmms_avcodec_seek (xmms_xform_t *xform, gint64 samples
+@@ -419,4 +358,171 @@ xmms_avcodec_seek (xmms_xform_t *xform, gint64 samples
}
return ret;
@@ -438,45 +459,37 @@ Deal with newer FFmpeg API.
+static gint
+xmms_avcodec_internal_decode_some (xmms_avcodec_data_t *data)
+{
-+ int got_frame = 0;
-+ gint bytes_read = 0;
-+ AVPacket packet;
++ int rc = 0;
+
-+ av_init_packet ();
-+ packet.data = data->buffer;
-+ packet.size = data->buffer_length;
-+
-+ /* clear buffers and reset fields to defaults */
-+ av_frame_unref (data->read_out_frame);
-+
-+ bytes_read = avcodec_decode_audio4 (
-+ data->codecctx, data->read_out_frame, _frame, );
-+
-+ /* The DTS
Re: Plasma 5 display and window placement issues
I have a similar result with Plasma 5 on 7.5-release on different hardware. Dmesg for it at the end of this message. ~/.xsession # Call xrdb to set the xterm font and colors. xrdb ~/.Xresources # Start cwm; launch xterm first. # xterm & # cwm # : ' # Enable apmd and dbus. # rcctl enable apmd messagebus export XDG_RUNTIME_DIR=/tmp/run/$(id -u) if [ ! -d $XDG_RUNTIME_DIR ]; then mkdir -m 700 -p $XDG_RUNTIME_DIR fi export QT_FORCE_STDERR_LOGGING=1 export QT_LOGGING_RULES="*=true" export XDG_CURRENT_DESKTOP=KDE export DESKTOP_SESSION=plasma export KDEWM=/usr/local/bin/picom /usr/local/bin/ck-launch-session /usr/local/bin/startplasma-x11 > ~/.startplasma-x11.log 2>&1 # ' ~/.config/kwinrc [Compositing] Enabled=false OpenBSD 7.5 (GENERIC.MP) #82: Wed Mar 20 15:48:40 MDT 2024 dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP real mem = 17069981696 (16279MB) avail mem = 16531427328 (15765MB) random: good seed from bootblocks mpath0 at root scsibus0 at mpath0: 256 targets mainbus0 at root bios0 at mainbus0: SMBIOS rev. 2.4 @ 0x8ad34000 (62 entries) bios0: vendor Apple Inc. version "87.0.0.0.0" date 06/13/2019 bios0: Apple Inc. MacBookPro8,1 efi0 at bios0: UEFI 1.1 acpi0 at bios0: ACPI 4.0 acpi0: sleep states S0 S3 S4 S5 acpi0: tables DSDT FACP HPET APIC SBST ECDT SSDT SSDT SSDT SSDT SSDT SSDT SSDT SSDT SSDT MCFG acpi0: wakeup devices P0P2(S4) GFX0(S4) PEG1(S4) EC__(S4) GMUX(S3) HDEF(S4) RP01(S4) GIGE(S4) SDXC(S3) RP02(S4) ARPT(S4) RP03(S4) RP04(S4) EHC1(S3) EHC2(S3) ADP1(S4) [...] acpitimer0 at acpi0: 3579545 Hz, 24 bits acpihpet0 at acpi0: 14318179 Hz acpimadt0 at acpi0 addr 0xfee0: PC-AT compat cpu0 at mainbus0: apid 0 (boot processor) cpu0: Intel(R) Core(TM) i5-2435M CPU @ 2.40GHz, 2394.60 MHz, 06-2a-07, patch 002f cpu0: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,POPCNT,DEADLINE,AES,XSAVE,AVX,NXE,RDTSCP,LONG,LAHF,PERF,ITSC,MD_CLEAR,IBRS,IBPB,STIBP,L1DF,SSBD,SENSOR,ARAT,XSAVEOPT,MELTDOWN cpu0: 32KB 64b/line 8-way D-cache, 32KB 64b/line 8-way I-cache, 256KB 64b/line 8-way L2 cache, 3MB 64b/line 12-way L3 cache cpu0: smt 0, core 0, package 0 mtrr: Pentium Pro MTRR support, 10 var ranges, 88 fixed ranges cpu0: apic clock running at 99MHz cpu0: mwait min=64, max=64, C-substates=0.2.1.1.2, IBE cpu1 at mainbus0: apid 2 (application processor) cpu1: Intel(R) Core(TM) i5-2435M CPU @ 2.40GHz, 2394.60 MHz, 06-2a-07, patch 002f cpu1: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,POPCNT,DEADLINE,AES,XSAVE,AVX,NXE,RDTSCP,LONG,LAHF,PERF,ITSC,MD_CLEAR,IBRS,IBPB,STIBP,L1DF,SSBD,SENSOR,ARAT,XSAVEOPT,MELTDOWN cpu1: 32KB 64b/line 8-way D-cache, 32KB 64b/line 8-way I-cache, 256KB 64b/line 8-way L2 cache, 3MB 64b/line 12-way L3 cache cpu1: smt 0, core 1, package 0 cpu2 at mainbus0: apid 1 (application processor) cpu2: Intel(R) Core(TM) i5-2435M CPU @ 2.40GHz, 2394.59 MHz, 06-2a-07, patch 002f cpu2: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,POPCNT,DEADLINE,AES,XSAVE,AVX,NXE,RDTSCP,LONG,LAHF,PERF,ITSC,MD_CLEAR,IBRS,IBPB,STIBP,L1DF,SSBD,SENSOR,ARAT,XSAVEOPT,MELTDOWN cpu2: 32KB 64b/line 8-way D-cache, 32KB 64b/line 8-way I-cache, 256KB 64b/line 8-way L2 cache, 3MB 64b/line 12-way L3 cache cpu2: smt 1, core 0, package 0 cpu3 at mainbus0: apid 3 (application processor) cpu3: Intel(R) Core(TM) i5-2435M CPU @ 2.40GHz, 2394.60 MHz, 06-2a-07, patch 002f cpu3: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,POPCNT,DEADLINE,AES,XSAVE,AVX,NXE,RDTSCP,LONG,LAHF,PERF,ITSC,MD_CLEAR,IBRS,IBPB,STIBP,L1DF,SSBD,SENSOR,ARAT,XSAVEOPT,MELTDOWN cpu3: 32KB 64b/line 8-way D-cache, 32KB 64b/line 8-way I-cache, 256KB 64b/line 8-way L2 cache, 3MB 64b/line 12-way L3 cache cpu3: smt 1, core 1, package 0 ioapic0 at mainbus0: apid 2 pa 0xfec0, version 20, 24 pins, remapped acpiec0 at acpi0 acpimcfg0 at acpi0 acpimcfg0: addr 0xe000, bus 0-155 acpiprt0 at acpi0: bus 0 (PCI0) acpiprt1 at acpi0: bus 1 (P0P2) acpiprt2 at acpi0: bus 5 (PEG1) acpiprt3 at acpi0: bus 2 (RP01) acpiprt4 at acpi0: bus 3 (RP02) acpiprt5 at acpi0: bus 4 (RP03) acpiprt6 at acpi0: bus -1 (RP04) acpisbs0 at acpi0: SBS0 model "bq20z451" serial 48 type LION oem "SMP" acpipci0 at acpi0 PCI0: 0x0004 0x0011 0x0001 acpicmos0 at acpi0 asmc0 at acpi0: SMC_ (smc-huronriver) addr 0x300/0x20: rev 1.68f568, 380 keys "APP0003" at acpi0 not configured "ACPI0008" at
CVS: cvs.openbsd.org: ports
CVSROOT:/cvs Module name:ports Changes by: rob...@cvs.openbsd.org 2024/05/10 23:39:07 Modified files: www/chromium : Makefile distinfo www/chromium/patches: patch-chrome_browser_metrics_chrome_browser_main_extra_parts_metrics_cc patch-media_base_media_switches_cc www/ungoogled-chromium: Makefile distinfo www/ungoogled-chromium/patches: patch-chrome_app_chrome_main_delegate_cc patch-chrome_browser_chrome_browser_main_extra_parts_linux_cc patch-chrome_browser_metrics_chrome_browser_main_extra_parts_metrics_cc patch-chrome_browser_prefs_browser_prefs_cc patch-media_base_media_switches_cc patch-third_party_blink_renderer_platform_runtime_enabled_features_json5 patch-ui_base_ui_base_features_cc Log message: update to 124.0.6367.201
sparc64 bulk build report
Bulk build on sparc64-0a.ports.openbsd.org Started : Thu May 9 03:41:41 MDT 2024 Finished: Fri May 10 23:32:06 MDT 2024 Duration: 1 Days 19 hours 50 minutes Built using OpenBSD 7.5-current (GENERIC.MP) #2124: Wed May 8 14:53:21 MDT 2024 Built 8422 packages Number of packages built each day: May 9: 6768 May 10: 1654 Critical path missing pkgs: http://build-failures.rhaalovely.net/sparc64/2024-05-09/summary.log Build failures: 66 http://build-failures.rhaalovely.net/sparc64/2024-05-09/archivers/blosc2.log http://build-failures.rhaalovely.net/sparc64/2024-05-09/astro/py-astropy,python3.log http://build-failures.rhaalovely.net/sparc64/2024-05-09/audio/mpdscribble.log http://build-failures.rhaalovely.net/sparc64/2024-05-09/audio/ncmpc.log http://build-failures.rhaalovely.net/sparc64/2024-05-09/databases/sqlports,-list.log http://build-failures.rhaalovely.net/sparc64/2024-05-09/devel/arm-none-eabi/gdb.log http://build-failures.rhaalovely.net/sparc64/2024-05-09/devel/avr/gcc.log http://build-failures.rhaalovely.net/sparc64/2024-05-09/devel/binutils.log http://build-failures.rhaalovely.net/sparc64/2024-05-09/devel/difftastic.log http://build-failures.rhaalovely.net/sparc64/2024-05-09/devel/harfbuzz.log http://build-failures.rhaalovely.net/sparc64/2024-05-09/devel/libbgcode.log http://build-failures.rhaalovely.net/sparc64/2024-05-09/devel/mtxclient.log http://build-failures.rhaalovely.net/sparc64/2024-05-09/devel/py-html5lib,python3.log http://build-failures.rhaalovely.net/sparc64/2024-05-09/devel/py-thrift,python3.log http://build-failures.rhaalovely.net/sparc64/2024-05-09/devel/rgbds.log http://build-failures.rhaalovely.net/sparc64/2024-05-09/devel/vim-command-t.log http://build-failures.rhaalovely.net/sparc64/2024-05-09/devel/woboq_codebrowser.log http://build-failures.rhaalovely.net/sparc64/2024-05-09/devel/xsd.log http://build-failures.rhaalovely.net/sparc64/2024-05-09/devel/yder.log http://build-failures.rhaalovely.net/sparc64/2024-05-09/emulators/libretro-pcsx-rearmed.log http://build-failures.rhaalovely.net/sparc64/2024-05-09/emulators/openmsx.log http://build-failures.rhaalovely.net/sparc64/2024-05-09/fonts/inclusive-sans.log http://build-failures.rhaalovely.net/sparc64/2024-05-09/games/bugdom.log http://build-failures.rhaalovely.net/sparc64/2024-05-09/games/bugdom2.log http://build-failures.rhaalovely.net/sparc64/2024-05-09/games/cataclysm-dda,no_x11.log http://build-failures.rhaalovely.net/sparc64/2024-05-09/games/choria.log http://build-failures.rhaalovely.net/sparc64/2024-05-09/games/colobot/colobot.log http://build-failures.rhaalovely.net/sparc64/2024-05-09/games/cromagrally.log http://build-failures.rhaalovely.net/sparc64/2024-05-09/games/devilutionx.log http://build-failures.rhaalovely.net/sparc64/2024-05-09/games/emptyclip.log http://build-failures.rhaalovely.net/sparc64/2024-05-09/games/fheroes2.log http://build-failures.rhaalovely.net/sparc64/2024-05-09/games/gnukem.log http://build-failures.rhaalovely.net/sparc64/2024-05-09/games/hyperrogue.log http://build-failures.rhaalovely.net/sparc64/2024-05-09/games/ottomatic.log http://build-failures.rhaalovely.net/sparc64/2024-05-09/games/recoil-rts.log http://build-failures.rhaalovely.net/sparc64/2024-05-09/games/scid.log http://build-failures.rhaalovely.net/sparc64/2024-05-09/games/widelands.log http://build-failures.rhaalovely.net/sparc64/2024-05-09/games/wrath.log http://build-failures.rhaalovely.net/sparc64/2024-05-09/geo/geocode-glib.log http://build-failures.rhaalovely.net/sparc64/2024-05-09/geo/osm2pgrouting.log http://build-failures.rhaalovely.net/sparc64/2024-05-09/graphics/oxipng.log http://build-failures.rhaalovely.net/sparc64/2024-05-09/graphics/spirv-tools.log http://build-failures.rhaalovely.net/sparc64/2024-05-09/mail/grommunio/index.log http://build-failures.rhaalovely.net/sparc64/2024-05-09/mail/mlmmj.log http://build-failures.rhaalovely.net/sparc64/2024-05-09/mail/rspamd,hyperscan.log http://build-failures.rhaalovely.net/sparc64/2024-05-09/math/gunits.log http://build-failures.rhaalovely.net/sparc64/2024-05-09/math/openfst.log http://build-failures.rhaalovely.net/sparc64/2024-05-09/net/powerdns.log http://build-failures.rhaalovely.net/sparc64/2024-05-09/net/proxychains-ng.log http://build-failures.rhaalovely.net/sparc64/2024-05-09/shells/nsh,static.log http://build-failures.rhaalovely.net/sparc64/2024-05-09/sysutils/borgmatic.log http://build-failures.rhaalovely.net/sparc64/2024-05-09/sysutils/flashrom.log http://build-failures.rhaalovely.net/sparc64/2024-05-09/sysutils/libvirt.log http://build-failures.rhaalovely.net/sparc64/2024-05-09/sysutils/lnav.log http://build-failures.rhaalovely.net/sparc64/2024-05-09/sysutils/nix.log http://build-failures.rhaalovely.net/sparc64/2024-05-09/sysutils/pftop.log http://build-failures.rhaalovely.net/sparc64/2024-05-09/sysutils/u-boot-asahi.log http://build-failures.rhaalovely.net/sparc64/2024-05-09/telephony/baresip/re.log
Plasma 5 display and window placement issues
Hi, First of all, thank you to Rafael Sadowski and anyone else who has contributed to Plasma 5 and 6 working on OpenBSD. The purpose of my report below is to supply feedback in the hope that I and other OpenBSD users who want to use Plasma can do so and iron out issues that come up. Dark mode from system settings does not work correctly. It usually does not apply to the body of the system settings window. When it does apply, the text remains the original dark color and is unreadable on the dark background. Konsole terminal cannot be fully full-screened. The scroll bar cannot be removed. The top menu bar cannot be fully hidden in full screen mode. Adding or removing menu bar components does not usually apply. The left side items on the top menu bar cannot be added back once removed. Alt-tab to switch apps does not work at all. When docked to multiple monitors, the super key to open the applications menu does not work at all. System Settings > Display Configuration - Does not correctly identify or adjust placement, identification, or display of multiple monitors. The external screens sometimes go black and only show the mouse if moved across them. One of the monitors did not even show the mouse moving across. ArandR still worked to arrange the monitors. When connected to multiple monitors, the Task Manager (bottom bar) shows bigger than when only the laptop screen is connected. And the pinned app icons are smashed together and overlap. And when opening the application menu with the mouse, the menu itself opens on a different monitor than the bottom bar and is also too big for the screen. When disconnected from external monitors, the built-in display does not fully revert to sole-display settings. This happens in cwm and any desktop environment which does not take special care to update the display configuration when external monitors are connected or disconnected. Plasma should have special settings to handle this. But it does not work as intended. When I sysupgraded to the May 10th snapshot, updated all packages, followed the pkg-readme from scratch and rebooted, the task bar and start menu showed bad font colors on a transparently absent background, which was un-readable against the default plasma wallpaper. It would no longer apply any appearance setting I changed, would not let me move the windows around, or let me unhide the window menus or show the minimize, maximize, or exit buttons of each window. I have not yet uninistalled and re-installed kde-plasma-extras and all its dependencies. OpenBSD 7.5-current (GENERIC.MP) #59: Fri May 10 11:20:56 MDT 2024 dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP real mem = 16973881344 (16187MB) avail mem = 16438198272 (15676MB) random: good seed from bootblocks mpath0 at root scsibus0 at mpath0: 256 targets mainbus0 at root bios0 at mainbus0: SMBIOS rev. 2.7 @ 0xdae9c000 (69 entries) bios0: vendor LENOVO version "G1ETC2WW (2.82 )" date 08/07/2019 bios0: LENOVO 2344BZU efi0 at bios0: UEFI 2.3.1 efi0: Lenovo rev 0x2820 acpi0 at bios0: ACPI 5.0 acpi0: sleep states S0 S3 S4 S5 acpi0: tables DSDT FACP SLIC TCPA SSDT SSDT SSDT HPET APIC MCFG ECDT FPDT ASF! UEFI UEFI MSDM SSDT SSDT UEFI DBG2 acpi0: wakeup devices LID_(S4) SLPB(S3) IGBE(S4) EXP3(S4) XHCI(S3) EHC1(S3) EHC2(S3) HDEF(S4) acpitimer0 at acpi0: 3579545 Hz, 24 bits acpihpet0 at acpi0: 14318179 Hz acpimadt0 at acpi0 addr 0xfee0: PC-AT compat cpu0 at mainbus0: apid 0 (boot processor) cpu0: Intel(R) Core(TM) i7-3610QM CPU @ 2.30GHz, 2294.90 MHz, 06-3a-09, patch 0021 cpu0: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,RDTSCP,LONG,LAHF,PERF,ITSC,FSGSBASE,SMEP,ERMS,MD_CLEAR,IBRS,IBPB,STIBP,L1DF,SSBD,SENSOR,ARAT,XSAVEOPT,MELTDOWN cpu0: 32KB 64b/line 8-way D-cache, 32KB 64b/line 8-way I-cache, 256KB 64b/line 8-way L2 cache, 6MB 64b/line 12-way L3 cache cpu0: smt 0, core 0, package 0 mtrr: Pentium Pro MTRR support, 10 var ranges, 88 fixed ranges cpu0: apic clock running at 99MHz cpu0: mwait min=64, max=64, C-substates=0.2.1.1.2, IBE cpu1 at mainbus0: apid 1 (application processor) cpu1: Intel(R) Core(TM) i7-3610QM CPU @ 2.30GHz, 2294.82 MHz, 06-3a-09, patch 0021 cpu1: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,RDTSCP,LONG,LAHF,PERF,ITSC,FSGSBASE,SMEP,ERMS,MD_CLEAR,IBRS,IBPB,STIBP,L1DF,SSBD,SENSOR,ARAT,XSAVEOPT,MELTDOWN cpu1: smt 1, core 0, package 0 cpu2 at mainbus0: apid 2 (application processor) cpu2: Intel(R) Core(TM) i7-3610QM CPU @ 2.30GHz, 2294.83 MHz, 06-3a-09, patch 0021 cpu2:
UPDATE: net/tailscale-1.66.1
Hi.
Update for net/tailscale v1.66.1
Changelog:
https://github.com/tailscale/tailscale/releases/tag/v1.66.1
https://github.com/tailscale/tailscale/releases/tag/v1.66.0
Obrigado!
--
Adriano
Index: Makefile
===
RCS file: /cvs/ports/net/tailscale/Makefile,v
retrieving revision 1.33
diff -u -p -r1.33 Makefile
--- Makefile25 Apr 2024 02:05:26 - 1.33
+++ Makefile11 May 2024 01:05:01 -
@@ -2,7 +2,7 @@ BROKEN-i386 = unix.EPROTO not defined
COMMENT = modern overlay-like VPN built on top of WireGuard
-V =1.64.2
+V =1.66.1
MODGO_MODNAME =tailscale.com
MODGO_VERSION =v${V}
Index: distinfo
===
RCS file: /cvs/ports/net/tailscale/distinfo,v
retrieving revision 1.31
diff -u -p -r1.31 distinfo
--- distinfo25 Apr 2024 02:05:26 - 1.31
+++ distinfo11 May 2024 01:05:03 -
@@ -315,8 +315,8 @@ SHA256 (go_modules/github.com/containerd
SHA256 (go_modules/github.com/containerd/ttrpc/@v/v1.1.0.zip) =
eRAoOr/WN7jDEmAlyz7GdWOw8ZSj8+PEJfjZZppojWA=
SHA256 (go_modules/github.com/containerd/typeurl/@v/v1.0.2.mod) =
0NY9ocaCb4eI+2Lleqg9DvD3m83DPCYlOIGStFiDg+0=
SHA256 (go_modules/github.com/containerd/typeurl/@v/v1.0.2.zip) =
rwUFT8d9XRQQZv2luiTbTBt+QYuTSrNJ1szRY+VI8Ts=
-SHA256 (go_modules/github.com/coreos/go-iptables/@v/v0.7.0.mod) =
tyvJvC7JIzZrOaDdaXnbNTPHT2tNaApLHYBWp7Fp4lk=
-SHA256 (go_modules/github.com/coreos/go-iptables/@v/v0.7.0.zip) =
W+4Dr+CNoVkuvWkcCauKNmmtBQVSaC86F6/0JvPsxV8=
+SHA256
(go_modules/github.com/coreos/go-iptables/@v/v0.7.1-0.20240112124308-65c67c9f46e6.mod)
= tyvJvC7JIzZrOaDdaXnbNTPHT2tNaApLHYBWp7Fp4lk=
+SHA256
(go_modules/github.com/coreos/go-iptables/@v/v0.7.1-0.20240112124308-65c67c9f46e6.zip)
= bQrmNE8dNV9y5qq6WDznOCKGFREzfKkswcRyf8i6Zt0=
SHA256 (go_modules/github.com/coreos/go-oidc/@v/v2.2.1+incompatible.mod) =
AhtJMrJ9pCQizg1hNy7yFT4k12plf+d40MqOaVpVEQk=
SHA256 (go_modules/github.com/coreos/go-oidc/@v/v2.2.1+incompatible.zip) =
uZf5P7/4pK7Tuy14o78RW6Twax0eS570zJ0fY9POQDY=
SHA256 (go_modules/github.com/coreos/go-semver/@v/v0.3.0.mod) =
7lARLbikHJ18hSy4jqSgh/IdaONnqPdq1u4Pt5rGvRw=
@@ -538,7 +538,6 @@ SHA256 (go_modules/github.com/gobuffalo/
SHA256 (go_modules/github.com/gobuffalo/flect/@v/v1.0.2.zip) =
11DFKN2cRzKqU5Q9RLYd42MBy40757G3WPc27TSwy5E=
SHA256 (go_modules/github.com/gobwas/glob/@v/v0.2.3.mod) =
tcaxcq3Bh4zY5pC6kSOwpldTuss42H5taDrKE21DVXg=
SHA256 (go_modules/github.com/gobwas/glob/@v/v0.2.3.zip) =
DP5IbNY9Re1MtYY/8cvRSxXkuTgNy/gP8mmRtASfT98=
-SHA256 (go_modules/github.com/godbus/dbus/v5/@v/v5.0.4.mod) =
h0Pqcv7SHMFDxKBnQI4h93h2EOZi/b6NWUMxLqiuiBY=
SHA256 (go_modules/github.com/godbus/dbus/v5/@v/v5.1.0.mod) =
h0Pqcv7SHMFDxKBnQI4h93h2EOZi/b6NWUMxLqiuiBY=
SHA256
(go_modules/github.com/godbus/dbus/v5/@v/v5.1.1-0.20230522191255-76236955d466.mod)
= s/AmOs6JVSE6Wv5K72nzbNhzpEdvm3mqhTTbotHu+VY=
SHA256
(go_modules/github.com/godbus/dbus/v5/@v/v5.1.1-0.20230522191255-76236955d466.zip)
= Ji9D7IdXAjig53Dn+mVt2nD+YFCn7fWt3DAofLZLIaY=
@@ -652,8 +651,8 @@ SHA256 (go_modules/github.com/google/mar
SHA256 (go_modules/github.com/google/martian/v3/@v/v3.0.0.mod) =
nz/aRWCLm+s5X37n8KoAHSKRi0jlDSmV9ohfoEcHL5E=
SHA256 (go_modules/github.com/google/martian/v3/@v/v3.1.0.mod) =
nz/aRWCLm+s5X37n8KoAHSKRi0jlDSmV9ohfoEcHL5E=
SHA256 (go_modules/github.com/google/martian/v3/@v/v3.1.0.zip) =
uJl1ZcCufvsy5BVbgDdZccgiwrCrpgl+lzXMJH/aPXI=
-SHA256
(go_modules/github.com/google/nftables/@v/v0.1.1-0.20230115205135-9aa6fdf5a28c.mod)
= vL6ozt14eGz58COLdyvQlvHvtyG9KTrYPJohdJp1fHw=
-SHA256
(go_modules/github.com/google/nftables/@v/v0.1.1-0.20230115205135-9aa6fdf5a28c.zip)
= SX/wMshFaQ2kjheCbkkg/UJZTUm8FiBvO+I6KszMHqw=
+SHA256
(go_modules/github.com/google/nftables/@v/v0.2.1-0.20240414091927-5e242ec57806.mod)
= v6halMag5msrkxRW7woaTYCKC7kWKwsO52ynrjEVGys=
+SHA256
(go_modules/github.com/google/nftables/@v/v0.2.1-0.20240414091927-5e242ec57806.zip)
= zrlrOab5AE2MIXpq5huRppwlC8MPvzoEzYfLv93qc8g=
SHA256
(go_modules/github.com/google/pprof/@v/v0.0.0-20181206194817-3ea8567a2e57.mod)
= 2bZhIC+y0vAgataorGO+yl1TNfKxzkjds5lHLfR8Vsw=
SHA256
(go_modules/github.com/google/pprof/@v/v0.0.0-20190515194954-54271f7e092f.mod)
= 2bZhIC+y0vAgataorGO+yl1TNfKxzkjds5lHLfR8Vsw=
SHA256
(go_modules/github.com/google/pprof/@v/v0.0.0-20191218002539-d4f498aebedc.mod)
= 1aWtNw6g62iSydRIta0DHK3BYA92AAo3n/GHUqQSQ1Y=
@@ -819,7 +818,6 @@ SHA256 (go_modules/github.com/jonboulle/
SHA256 (go_modules/github.com/jonboulle/clockwork/@v/v0.2.2.zip) =
hoYKuvzXMyr0sRlbHAkq3lA7MblKa6w8kUDl7g0CGfA=
SHA256 (go_modules/github.com/josharian/intern/@v/v1.0.0.mod) =
tQJ6Z/XBJ7tGuf+snTWjM7Hfcc/CIOcZanmT4WoQorI=
SHA256 (go_modules/github.com/josharian/intern/@v/v1.0.0.zip) =
Vnm/0RwUrczbRb0aD5z0tEW5XK7tb7UHupbsztEcJI0=
-SHA256 (go_modules/github.com/josharian/native/@v/v1.0.0.mod) =
Re: patch dkimproxy: use rsa-sha256 in sample signing config
Hello. Kirill A. Korinsky wrote in <5285e80cbc0d1...@mx2.catap.net>: |On Fri, 10 May 2024 10:47:43 +0100, |Stuart Henderson wrote: |> On 2024/05/10 11:40, Matthieu Herrb wrote: |>> Afaict dkimpproxy is not using opendkim but p5-Mail-DKIM. dkimproxy |>> itself also hasn't seen a update since many years, but the underlying |>> perl lib has been last updated last january (and could use an update |>> in the port). |>> |>> So unless you imply that because many people use opendkim, ed25519 |>> based signatures shouldn't be used at all I'm not sure I understand |>> what you're saying. |> |> ed25519 can be used, but at the moment if you do use it, you probably |> want to be double-signing with both that + rsa-sha256. |> | |I imply that using ed25519 usually leads to malformed signature, and some |big hosting providers treat double signature as bad signature if some of |them are not RSA-SHA256. A notable example is icloud.com, which delivers \ |all |emails with double signatures to the junk folder. At least that's what they |did the last time I checked in December'23. Then these are not standard compliant. The DKIM standard 6376 *explicitly* supports multiple signatures. |So I suggest to put in README and config exmaple that using anything other |than RSA-SHA256 may lead to delivery email to thte junk. Unfortunately, \ |this |includes duble signatures as well. On the IETF DKIM list there are people which told me they use such a configuration since 2019 without any issues, and i myself use it for two months, too, and did not have problems; that cloud thing i never saw, though. Btw my postfix-only s-dkim-sign will become a port soon, i only want to have an update to s-postgray first, and then do all the ports in one go. Dunno whether i make it tomorrow, but early next week for sure. (It simply compiles, tests and runs on OpenBSD out of the box.) --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] net/crawley-v1.7.5
That’s not a reason to set NO_TEST.
—
Antoine
> On 11 May 2024, at 00:41, Russ Sharek wrote:
>
> On May 1, 2024 1:07:10 AM EDT, Russ Sharek wrote:
>>> On Mon, Apr 29, 2024 at 01:45:03PM +0200, Jeremie Courreges-Anglas wrote:
>>> A few nits:
>>> - the port doesn't install any doc and DESCR is rather light. I
>>> understand the tool is simple but still, it would be nice to at least
>>> have the examples from the README. Maybe just install that file under
>>> share/doc/crawley?
>>> - make test fails for bad reasons and I don't know how to fix that.
>>> NO_TEST=Yes?
>>
>> Thank you for the useful nits!
>>
>> Here's a diff that adds both the NO_TEST and README.md to the port.
>>
>> diff -ur projects/git.disroot.org/mystuff/net/crawley/Makefile
>> /usr/ports/mystuff/net/crawley/Makefile
>> --- projects/git.disroot.org/mystuff/net/crawley/MakefileWed May 1
>> 00:57:52 2024
>> +++ /usr/ports/mystuff/net/crawley/MakefileWed May 1 00:50:43 2024
>> @@ -14,9 +14,15 @@
>> # MIT
>> PERMIT_PACKAGE =Yes
>>
>> +NO_TEST =Yes
>> +
>> WANTLIB += c pthread
>>
>> MODULES =lang/go
>> +
>> +post-install:
>> +${INSTALL_DATA_DIR} ${PREFIX}/share/doc/crawley
>> +${INSTALL_DATA} ${WRKSRC}/README.md ${PREFIX}/share/doc/crawley
>>
>> .include "modules.inc"
>>
>> diff -ur projects/git.disroot.org/mystuff/net/crawley/pkg/PLIST
>> /usr/ports/mystuff/net/crawley/pkg/PLIST
>> --- projects/git.disroot.org/mystuff/net/crawley/pkg/PLISTWed May 1
>> 00:57:52 2024
>> +++ /usr/ports/mystuff/net/crawley/pkg/PLISTWed May 1 00:45:15 2024
>> @@ -1 +1,3 @@
>> @bin bin/crawley
>> +share/doc/crawley/
>> +share/doc/crawley/README.md
>
> bump?
> OK?
> Edd said it looked good...
>
> Thanks!
>
>
Re: [NEW] net/crawley-v1.7.5
On May 1, 2024 1:07:10 AM EDT, Russ Sharek wrote:
>On Mon, Apr 29, 2024 at 01:45:03PM +0200, Jeremie Courreges-Anglas wrote:
>> A few nits:
>> - the port doesn't install any doc and DESCR is rather light. I
>> understand the tool is simple but still, it would be nice to at least
>> have the examples from the README. Maybe just install that file under
>> share/doc/crawley?
>> - make test fails for bad reasons and I don't know how to fix that.
>> NO_TEST=Yes?
>
>Thank you for the useful nits!
>
>Here's a diff that adds both the NO_TEST and README.md to the port.
>
>diff -ur projects/git.disroot.org/mystuff/net/crawley/Makefile
>/usr/ports/mystuff/net/crawley/Makefile
>--- projects/git.disroot.org/mystuff/net/crawley/Makefile Wed May 1
>00:57:52 2024
>+++ /usr/ports/mystuff/net/crawley/MakefileWed May 1 00:50:43 2024
>@@ -14,9 +14,15 @@
> # MIT
> PERMIT_PACKAGE = Yes
>
>+NO_TEST = Yes
>+
> WANTLIB += c pthread
>
> MODULES = lang/go
>+
>+post-install:
>+ ${INSTALL_DATA_DIR} ${PREFIX}/share/doc/crawley
>+ ${INSTALL_DATA} ${WRKSRC}/README.md ${PREFIX}/share/doc/crawley
>
> .include "modules.inc"
>
>diff -ur projects/git.disroot.org/mystuff/net/crawley/pkg/PLIST
>/usr/ports/mystuff/net/crawley/pkg/PLIST
>--- projects/git.disroot.org/mystuff/net/crawley/pkg/PLIST Wed May 1
>00:57:52 2024
>+++ /usr/ports/mystuff/net/crawley/pkg/PLIST Wed May 1 00:45:15 2024
>@@ -1 +1,3 @@
> @bin bin/crawley
>+share/doc/crawley/
>+share/doc/crawley/README.md
bump?
OK?
Edd said it looked good...
Thanks!
CVS: cvs.openbsd.org: ports
CVSROOT:/cvs Module name:ports Changes by: e...@cvs.openbsd.org2024/05/10 14:38:34 Modified files: games/angband : Makefile distinfo games/angband/patches: patch-mk_buildsys_mk_in games/angband/pkg: PFRAG.sdl PLIST Added files: games/angband/patches: patch-src_main_c games/angband/pkg: PFRAG.no-no_x11 Removed files: games/angband/patches: patch-lib_help_version_txt patch-src_mon-blows_h Log message: games/angband: update to version 4.2.5. While here, use SDL2 instead of SDL1. (with some tweaks suggested by sthen@, thanks)
CVS: cvs.openbsd.org: ports
CVSROOT:/cvs Module name:ports Changes by: t...@cvs.openbsd.org2024/05/10 14:12:48 Modified files: games/love/0.10: Makefile Log message: disable LuaJIT for love/0.10 This removes a barrier to updating luajit to 2.1 per sthen@ diff by sthen@ ok op@ (maintainer) Note with this, a few commercial games that depend on LuaJIT don't launch anymore (Blue Revolver, Cityglitch, Spellrazor). Others still work and so does games/orthorobot
CVS: cvs.openbsd.org: ports
CVSROOT:/cvs Module name:ports Changes by: fcam...@cvs.openbsd.org 2024/05/10 13:50:02 Modified files: sysutils/fd: Makefile distinfo Log message: Update fd to 10.1.0.
Re: luajit, arm64, games/love/0.10
Il 2024-05-10 16:00 Thomas Frohwein ha scritto: On Fri, May 10, 2024 at 09:44:42AM -0400, Thomas Frohwein wrote: On Fri, May 10, 2024 at 11:31:54AM +0100, Stuart Henderson wrote: > [...] > How much would it suck to disable the jit for this version as is > already done for 0.8? I've built it with your diff and ran a few that I could: orthorobot from packages, as well as Britebot, Marvellous Inc., and Soulstice. All run fine. This is on a high-end CPU (Intel Xeon W-11955M), so the effect of not using the JIT may be more noticeable on lower end hardware. But this is still all very niche, so I think disabling the JIT is the right move. ok thfr@ ok op@ too Just realized the games that I couldn't run (Blue Revolver, Britebot, Spellrazor) still run with LuaJIT, so the diff breaks them. I still think it's the right move for now to disable the JIT for love-0.10 at this point. me too. marking it as BROKEN is probably too much since there are games that run on love-0.10 without luajit. Thanks, Omar Polo
CVS: cvs.openbsd.org: ports
CVSROOT:/cvs Module name:ports Changes by: fcam...@cvs.openbsd.org 2024/05/10 13:05:01 Modified files: textproc/riff : Makefile crates.inc distinfo Log message: Update riff to 3.1.3.
switch editors/calligra to C++20
Hi,
this switches editors/calligra to be built with C++20 (requirement of
poppler-2024.05.0). It needs the update of math/eigen3 I just sent.
ok?
Ciao,
Kili
Index: Makefile
===
RCS file: /cvs/ports/editors/calligra/Makefile,v
diff -u -p -r1.59 Makefile
--- Makefile1 Jan 2024 19:43:03 - 1.59
+++ Makefile10 May 2024 17:53:55 -
@@ -3,7 +3,7 @@ HOMEPAGE = https://www.calligra.org
VERSION = 3.2.1
DISTNAME = calligra-${VERSION}
CATEGORIES = editors
-REVISION = 11
+REVISION = 12
SHARED_LIBS = RtfReader 51.0 # 0.0
SHARED_LIBS += basicflakes 50.0 # 0.0
Index: patches/patch-CMakeLists_txt
===
RCS file: /cvs/ports/editors/calligra/patches/patch-CMakeLists_txt,v
diff -u -p -r1.8 patch-CMakeLists_txt
--- patches/patch-CMakeLists_txt28 Mar 2022 20:06:46 - 1.8
+++ patches/patch-CMakeLists_txt10 May 2024 17:53:55 -
@@ -1,5 +1,5 @@
- Fix build with OpenEXR>=3
-- Switch to C++17
+- Switch to C++20
- Update Cmake and deps, Fix Freetype and FontConfig Linkage,
from upstream
- disable GSL support for now. devel/gsl needs an update
@@ -21,7 +21,7 @@ Index: CMakeLists.txt
+#else ()
+#set (CMAKE_CXX_STANDARD 11)
+#endif ()
-+set (CMAKE_CXX_STANDARD 17)
++set (CMAKE_CXX_STANDARD 20)
#
Index: patches/patch-sheets_functions_reference_cpp
===
RCS file: patches/patch-sheets_functions_reference_cpp
diff -N patches/patch-sheets_functions_reference_cpp
--- /dev/null 1 Jan 1970 00:00:00 -
+++ patches/patch-sheets_functions_reference_cpp10 May 2024 17:53:55
-
@@ -0,0 +1,15 @@
+Index: sheets/functions/reference.cpp
+--- sheets/functions/reference.cpp.orig
sheets/functions/reference.cpp
+@@ -415,11 +415,6 @@ Value func_indirect(valVector args, ValueCalc *calc, F
+ if (ref.isEmpty())
+ return Value::errorVALUE();
+
+-if (r1c1) {
+-// TODO: translate the r1c1 style to a1 style
+-ref = ref;
+-}
+-
+ const Calligra::Sheets::Region region(ref, e->sheet->map(), e->sheet);
+ if (!region.isValid() || !region.isSingular())
+ return Value::errorVALUE();
Index: patches/patch-sheets_functions_statistical_cpp
===
RCS file: patches/patch-sheets_functions_statistical_cpp
diff -N patches/patch-sheets_functions_statistical_cpp
--- /dev/null 1 Jan 1970 00:00:00 -
+++ patches/patch-sheets_functions_statistical_cpp 10 May 2024 17:53:55
-
@@ -0,0 +1,19 @@
+Index: sheets/functions/statistical.cpp
+--- sheets/functions/statistical.cpp.orig
sheets/functions/statistical.cpp
+@@ -1633,7 +1633,6 @@ Value func_growth(valVector args, ValueCalc *calc, Fun
+ double sumX= 0.0;
+ double sumSqrX = 0.0;
+ double sumY= 0.0;
+-double sumSqrY = 0.0;
+ double sumXY = 0.0;
+ double valX, valY;
+
+@@ -1647,7 +1646,6 @@ Value func_growth(valVector args, ValueCalc *calc, Fun
+ sumX+= valX;
+ sumSqrX += valX * valX;
+ sumY+= valY;
+-sumSqrY += valY * valY;
+ sumXY += valX * valY;
+ ++count;
+ }
update math/eigen3
[cc'ing rsadowski, because there are a lot of kde consumers of eigen3]
Hi,
this updates math/eigen3 to the latest Version (from 2021). This
is required to switch editors/calligra to C++-20, which in turn is
required for an update of print/poppler.
Successfully rebuilt all ports using math/eigen3, and also tested
some of them (kstarts, krita, calligra):
astro/calcmysky
astro/kstars
cad/openscad
cad/prusaslicer
cad/solvespace
editors/calligra *
emulators/emulationstation
graphics/asymptote
graphics/digikam
graphics/krita
graphics/opencv
misc/openbabel
x11/kde-applications/analitza
x11/kde-applications/kalzium
x11/kde-applications/step
* calligra needs additional patches, which I'll send in a few
minutes.
ok?
I'll also bump all the ports listed above.
Ciao,
Kili
Index: Makefile
===
RCS file: /cvs/ports/math/eigen3/Makefile,v
diff -u -p -r1.14 Makefile
--- Makefile27 Sep 2023 09:27:53 - 1.14
+++ Makefile10 May 2024 18:00:59 -
@@ -6,7 +6,7 @@ CATEGORIES =math devel
HOMEPAGE = https://eigen.tuxfamily.org
-VERSION = 3.3.9
+VERSION = 3.4.0
DISTNAME = eigen-${VERSION}
PKGNAME = eigen3-${VERSION}
Index: distinfo
===
RCS file: /cvs/ports/math/eigen3/distinfo,v
diff -u -p -r1.3 distinfo
--- distinfo19 Feb 2022 21:10:57 - 1.3
+++ distinfo10 May 2024 18:00:59 -
@@ -1,2 +1,2 @@
-SHA256 (eigen-3.3.9.tar.gz) = eYWXW3hzQBJHhvCSs6B9WUsunNU7v+Xz2bHa7n1V9W8=
-SIZE (eigen-3.3.9.tar.gz) = 2142379
+SHA256 (eigen-3.4.0.tar.gz) = hYYIT3H5veVF7n+m0AKIsmSit6w2B7l05U0T5xYsHHI=
+SIZE (eigen-3.4.0.tar.gz) = 2705005
Index: patches/patch-cmake_FindGoogleHash_cmake
===
RCS file: /cvs/ports/math/eigen3/patches/patch-cmake_FindGoogleHash_cmake,v
diff -u -p -r1.2 patch-cmake_FindGoogleHash_cmake
--- patches/patch-cmake_FindGoogleHash_cmake11 Mar 2022 19:36:14 -
1.2
+++ patches/patch-cmake_FindGoogleHash_cmake10 May 2024 18:00:59 -
@@ -1,6 +1,7 @@
Fix configure check.
cmake/FindGoogleHash.cmake.origTue Jul 30 15:24:36 2013
-+++ cmake/FindGoogleHash.cmake Tue Jul 30 15:24:20 2013
+Index: cmake/FindGoogleHash.cmake
+--- cmake/FindGoogleHash.cmake.orig
cmake/FindGoogleHash.cmake
@@ -1,4 +1,7 @@
+include(CMakePushCheckState)
@@ -8,12 +9,9 @@ Fix configure check.
+
if (GOOGLEHASH_INCLUDES AND GOOGLEHASH_LIBRARIES)
set(GOOGLEHASH_FIND_QUIETLY TRUE)
- endif (GOOGLEHASH_INCLUDES AND GOOGLEHASH_LIBRARIES)
-@@ -9,12 +12,16 @@ find_path(GOOGLEHASH_INCLUDES
- PATHS
- ${INCLUDE_INSTALL_DIR}
+ endif ()
+@@ -11,10 +14,13 @@ find_path(GOOGLEHASH_INCLUDES
)
-+message(STATUS "GOOGLEHASH_INCLUDES: ${GOOGLEHASH_INCLUDES}")
if(GOOGLEHASH_INCLUDES)
- # let's make sure it compiles with the current compiler
@@ -27,6 +25,6 @@ Fix configure check.
+ set(CMAKE_REQUIRED_LIBRARIES)
+ check_cxx_source_compiles("#include \n#include
\nint main(int argc, char** argv) {
google::dense_hash_map a; google::sparse_hash_map b;
return 0;}\n" GOOGLEHASH_COMPILE)
+ cmake_pop_check_state()
- endif(GOOGLEHASH_INCLUDES)
+ endif()
include(FindPackageHandleStandardArgs)
Index: patches/patch-test_main_h
===
RCS file: /cvs/ports/math/eigen3/patches/patch-test_main_h,v
diff -u -p -r1.3 patch-test_main_h
--- patches/patch-test_main_h 11 Mar 2022 19:36:14 - 1.3
+++ patches/patch-test_main_h 10 May 2024 18:00:59 -
@@ -1,15 +1,16 @@
This test fails, and we actually DO provide min() and max() correctly,
so disable it.
+Index: test/main.h
--- test/main.h.orig
+++ test/main.h
-@@ -67,8 +67,8 @@
- // protected by parenthesis against macro expansion, the min()/max() macros
- // are defined here and any not-parenthesized min/max call will cause a
- // compiler error.
--#define min(A,B) please_protect_your_min_with_parentheses
--#define max(A,B) please_protect_your_max_with_parentheses
-+//#define min(A,B) please_protect_your_min_with_parentheses
-+//#define max(A,B) please_protect_your_max_with_parentheses
- #define isnan(X) please_protect_your_isnan_with_parentheses
- #define isinf(X) please_protect_your_isinf_with_parentheses
- #define isfinite(X) please_protect_your_isfinite_with_parentheses
+@@ -88,8 +88,8 @@
+ //
+ // So instead choosing to simply disable this check for HIP
+ //
+- #define min(A,B) please_protect_your_min_with_parentheses
+- #define max(A,B) please_protect_your_max_with_parentheses
++ //#define min(A,B) please_protect_your_min_with_parentheses
++ //#define max(A,B) please_protect_your_max_with_parentheses
+ #define isnan(X) please_protect_your_isnan_with_parentheses
+ #define isinf(X) please_protect_your_isinf_with_parentheses
+ #define isfinite(X) please_protect_your_isfinite_with_parentheses
Index: pkg/PLIST
CVS: cvs.openbsd.org: ports
CVSROOT:/cvs Module name:ports Changes by: lan...@cvs.openbsd.org 2024/05/10 11:16:41 Modified files: www/dokuwiki : Makefile distinfo www/dokuwiki/pkg: PLIST Log message: www/dokuwiki: update to 2024.02.06a with a tweak to VERSION to drop the trailing a from PKGNAME see https://www.dokuwiki.org/changes#release_2024-02-06a_kaos ok pea@ (MAINTAINER)
CVS: cvs.openbsd.org: ports
CVSROOT:/cvs Module name:ports Changes by: matth...@cvs.openbsd.org2024/05/10 08:50:40 Modified files: mail/dkimproxy : Makefile Added files: mail/dkimproxy/patches: patch-scripts_dkimproxy_out_conf_example Log message: Set DKIM signature to rsa-sha256. Required by RFC6376. ok aisha@
CVS: cvs.openbsd.org: ports
CVSROOT:/cvs Module name:ports Changes by: matth...@cvs.openbsd.org2024/05/10 08:48:01 ports/mail/dkimproxy/patches Update of /cvs/ports/mail/dkimproxy/patches In directory cvs.openbsd.org:/tmp/cvs-serv21633/patches Log Message: Directory /cvs/ports/mail/dkimproxy/patches added to the repository
CVS: cvs.openbsd.org: ports
CVSROOT:/cvs Module name:ports Changes by: t...@cvs.openbsd.org2024/05/10 08:25:40 Modified files: games/openarena: Makefile Log message: USE_NOBTCFI for openarena diff from sthen@, issue raised by Divan Santana ( divan AT santanas ! co ! za )
CVS: cvs.openbsd.org: ports
CVSROOT:/cvs Module name:ports Changes by: t...@cvs.openbsd.org2024/05/10 08:19:49 Modified files: devel/sdl2 : Makefile distinfo devel/sdl2/patches: patch-configure patch-src_joystick_SDL_gamecontrollerdb_h Log message: update to SDL 2.30.3, catching up with several bug fix releases
Re: security/pinentry update
Hi. I already have an update and OK pea@ for this.
—
Antoine
> On 10 May 2024, at 15:16, Stuart Henderson wrote:
>
> Here's an update to security/pinentry, the "pinentry-qt" binary is
> now for Qt6 so I've added a separate package for that.
>
> pinentry-gnome3 moves from x11/gnome/gcr to x11/gnome/gcr4.
>
> Index: Makefile
> ===
> RCS file: /cvs/ports/security/pinentry/Makefile,v
> diff -u -p -w -u -r1.34 Makefile
> --- Makefile2 Nov 2023 08:12:51 -1.34
> +++ Makefile10 May 2024 13:14:11 -
> @@ -1,14 +1,13 @@
> COMMENT-main =PIN or passphrase entry dialog (ncurses interface)
> COMMENT-gnome3 =PIN or passphrase entry dialog (GNOME 3 interface)
> COMMENT-qt5 =PIN or passphrase entry dialog (Qt5 interface)
> +COMMENT-qt6 =PIN or passphrase entry dialog (Qt6 interface)
>
> -VERSION =1.2.1
> +VERSION =1.3.0
> DISTNAME =pinentry-${VERSION}
> CATEGORIES =security
> EXTRACT_SUFX =.tar.bz2
>
> -REVISION-qt5 =0
> -
> SITES =${SITE_GNUPG:=pinentry/}
>
> HOMEPAGE =https://www.gnupg.org/related_software/pinentry/index.en.html
> @@ -30,22 +29,28 @@ LIB_DEPENDS =security/libassuan \
>x11/gnome/libsecret
>
> WANTLIB-gnome3 += ${WANTLIB}
> -WANTLIB-gnome3 += atk-1.0 cairo cairo-gobject gck-1 gcr-base-3 gcr-ui-3
> -WANTLIB-gnome3 += gdk-3 gdk_pixbuf-2.0 gtk-3 harfbuzz p11-kit pango-1.0
> -WANTLIB-gnome3 += pangocairo-1.0
> +WANTLIB-gnome3 += gck-2 gcr-4 p11-kit
>
> LIB_DEPENDS-gnome3 =${LIB_DEPENDS} \
> -x11/gnome/gcr
> +x11/gnome/gcr4
>
> WANTLIB-qt5 += ${WANTLIB}
> WANTLIB-qt5 += ${COMPILER_LIBCXX} KF5WaylandClient Qt5Core Qt5Gui
> WANTLIB-qt5 += Qt5Widgets Qt5X11Extras X11 m
>
> +RUN_DEPENDS-qt5 =devel/desktop-file-utils
> LIB_DEPENDS-qt5 =${LIB_DEPENDS} \
>devel/kf5/kwayland \
>x11/qt5/qtbase \
>x11/qt5/qtx11extras
>
> +WANTLIB-qt6 += ${WANTLIB} ${COMPILER_LIBCXX}
> +WANTLIB-qt6 += Qt6Core Qt6Gui Qt6Widgets m
> +
> +RUN_DEPENDS-qt6 =devel/desktop-file-utils
> +LIB_DEPENDS-qt6 =${LIB_DEPENDS} \
> +x11/qt6/qtbase
> +
> CONFIGURE_STYLE =gnu
> CONFIGURE_ENV =CPPFLAGS="-I${LOCALBASE}/include -D_XOPEN_SOURCE_EXTENDED"
> \
>LDFLAGS="-L${LOCALBASE}/lib"
> @@ -57,10 +62,10 @@ CONFIGURE_ARGS =--enable-pinentry-curs
>--disable-pinentry-tqt \
>--disable-pinentry-fltk
>
> -MULTI_PACKAGES =-main -gnome3 -qt5
> +MULTI_PACKAGES =-main -gnome3 -qt5 -qt6
>
> -PSEUDO_FLAVORS=no_gnome3 no_qt5 bootstrap
> -FLAVOR?=no_gnome3 no_qt5 bootstrap
> +PSEUDO_FLAVORS=no_gnome3 no_qt5 no_qt6 bootstrap
> +FLAVOR?=no_gnome3 no_qt5 no_qt6 bootstrap
>
> .include
>
> @@ -69,8 +74,11 @@ CONFIGURE_ARGS +=--disable-pinentry-gno
> .endif
>
> .if !${BUILD_PACKAGES:M-qt5}
> -CONFIGURE_ARGS +=--disable-pinentry-qt
> CONFIGURE_ARGS +=--disable-pinentry-qt5
> +.endif
> +
> +.if !${BUILD_PACKAGES:M-qt6}
> +CONFIGURE_ARGS +=--disable-pinentry-qt
> .endif
>
> # http://pkgs.fedoraproject.org/cgit/pinentry.git/tree/pinentry-wrapper
> Index: distinfo
> ===
> RCS file: /cvs/ports/security/pinentry/distinfo,v
> diff -u -p -w -u -r1.10 distinfo
> --- distinfo30 Aug 2022 06:06:32 -1.10
> +++ distinfo10 May 2024 13:14:11 -
> @@ -1,2 +1,2 @@
> -SHA256 (pinentry-1.2.1.tar.bz2) =
> RXoYXlqFI4+5RalV3GNSq5YtyLSHILYvyfpIx1QKQGc=
> -SIZE (pinentry-1.2.1.tar.bz2) = 547698
> +SHA256 (pinentry-1.3.0.tar.bz2) =
> mzzVIm51l/L97TmaO8ZZkjNRU2VZ6dsIJpgbyjFklN4=
> +SIZE (pinentry-1.3.0.tar.bz2) = 610363
> Index: pkg/DESCR-qt6
> ===
> RCS file: pkg/DESCR-qt6
> diff -N pkg/DESCR-qt6
> --- /dev/null1 Jan 1970 00:00:00 -
> +++ pkg/DESCR-qt610 May 2024 13:14:11 -
> @@ -0,0 +1 @@
> +This package provides a Qt6 interface to pinentry.
> Index: pkg/PLIST-qt5
> ===
> RCS file: /cvs/ports/security/pinentry/pkg/PLIST-qt5,v
> diff -u -p -w -u -r1.2 PLIST-qt5
> --- pkg/PLIST-qt511 Mar 2022 19:53:51 -1.2
> +++ pkg/PLIST-qt510 May 2024 13:14:11 -
> @@ -1 +1,4 @@
> -@bin bin/pinentry-qt
> +@bin bin/pinentry-qt5
> +share/applications/
> +share/applications/org.gnupg.pinentry-qt5.desktop
> +@tag update-desktop-database
> Index: pkg/PLIST-qt6
> ===
> RCS file: pkg/PLIST-qt6
> diff -N pkg/PLIST-qt6
> --- /dev/null1 Jan 1970 00:00:00 -
> +++ pkg/PLIST-qt610 May 2024 13:14:11 -
> @@ -0,0 +1,5 @@
> +@conflict pinentry-qt5-<1.3.0
> +@bin bin/pinentry-qt
> +share/applications/
> +share/applications/org.gnupg.pinentry-qt.desktop
> +@tag update-desktop-database
>
Re: luajit, arm64, games/love/0.10
On Fri, May 10, 2024 at 09:44:42AM -0400, Thomas Frohwein wrote:
> On Fri, May 10, 2024 at 11:31:54AM +0100, Stuart Henderson wrote:
> > +cc op@, sorry I missed the maintainer line in ../Makefile.inc
> > [ original mail: https://marc.info/?l=openbsd-ports=171528886832093=2 ]
> >
> > On 2024/05/09 20:06, Thomas Frohwein wrote:
> > > On Thu, May 09, 2024 at 10:09:39PM +0100, Stuart Henderson wrote:
> > >
> > > [...]
> > >
> > > > How useful is love/0.10, does it still make sense to keep it?
> > >
> > > There are a couple of nice (commercial) games that run with love-0.10:
> > >
> > > $ ls -1 0.10
> > > blue-revolver
> > > britebot
> > > cityglitch
> > > marvellous-inc
> > > pocket-rumble
> > > soulstice
> > > spellrazor
> > >
> > > From my side not a reason to keep aging version of luajit alive and I
> > > would be ok with marking love/0.10 BROKEN to give a little time to see
> > > if it can be patched up to work with the luajit update...
> > >
> >
> > For the error I'm running into, it looks like it would be fixed by an
> > update to newer luasocket, though the commit which updates it in the
> > love2d tree is huge -
> > https://github.com/love2d/love/commit/8885fc621dd01c3b8dfd1abf063785103d9daf15.patch
> > - and doesn't directly apply to the version in 0.10.2 (and there's no
> > 0.10 branch in their git repo so tracking down other needed commits is
> > a bit awkward).
> >
> > How much would it suck to disable the jit for this version as is
> > already done for 0.8?
>
> I've built it with your diff and ran a few that I could: orthorobot
> from packages, as well as Britebot, Marvellous Inc., and Soulstice.
> All run fine. This is on a high-end CPU (Intel Xeon W-11955M), so the
> effect of not using the JIT may be more noticeable on lower end
> hardware. But this is still all very niche, so I think disabling the
> JIT is the right move. ok thfr@
Just realized the games that I couldn't run (Blue Revolver, Britebot,
Spellrazor) still run with LuaJIT, so the diff breaks them. I still
think it's the right move for now to disable the JIT for love-0.10 at
this point.
Here the errors when running without JIT in case this means more to
someone else:
Spellrazor:
Error: Syntax error: main.lua:1: unexpected symbol near '#'
stack traceback:
(tail call): ?
[C]: ?
[C]: in function 'require'
[string "boot.lua"]:429: in function <[string "boot.lua"]:275>
[C]: in function 'xpcall'
Blue Revolver (and similar with Cityglitch):
Error: lib/bitser.lua:24: module 'ffi' not found:
no field package.preload['ffi']
no 'ffi' in LOVE game directories.
no file 'ffi.so' in LOVE paths.
no file './ffi.lua'
no file '/usr/local/share/lua/5.1/ffi.lua'
no file '/usr/local/share/lua/5.1/ffi/init.lua'
no file '/usr/local/lib/lua/5.1/ffi.lua'
no file '/usr/local/lib/lua/5.1/ffi/init.lua'
no file './ffi.so'
no file '/usr/local/lib/lua/5.1/ffi.so'
no file '/usr/local/lib/lua/5.1/loadall.so'
stack traceback:
(tail call): ?
[C]: in function 'require'
lib/bitser.lua:24: in main chunk
[C]: in function 'require'
game/replayplaylist.lua:2: in main chunk
[C]: in function 'require'
game/states/loading.lua:7: in main chunk
[C]: in function 'require'
main.lua:53: in main chunk
[C]: in function 'require'
[string "boot.lua"]:429: in function <[string "boot.lua"]:275>
[C]: in function 'xpcall'
>
> > Index: Makefile
> > ===
> > RCS file: /cvs/ports/games/love/0.10/Makefile,v
> > diff -u -p -r1.2 Makefile
> > --- Makefile23 Jun 2023 17:35:54 - 1.2
> > +++ Makefile10 May 2024 10:22:57 -
> > @@ -1,5 +1,6 @@
> > VERSION = 0.10.2
> > -REVISION = 0
> > +USE_LUAJIT = No
> > +REVISION = 1
> >
> > SHARED_LIBS= love-${VERSION} 0.0
> >
>
Re: luajit, arm64, games/love/0.10
On Fri, May 10, 2024 at 11:31:54AM +0100, Stuart Henderson wrote:
> +cc op@, sorry I missed the maintainer line in ../Makefile.inc
> [ original mail: https://marc.info/?l=openbsd-ports=171528886832093=2 ]
>
> On 2024/05/09 20:06, Thomas Frohwein wrote:
> > On Thu, May 09, 2024 at 10:09:39PM +0100, Stuart Henderson wrote:
> >
> > [...]
> >
> > > How useful is love/0.10, does it still make sense to keep it?
> >
> > There are a couple of nice (commercial) games that run with love-0.10:
> >
> > $ ls -1 0.10
> > blue-revolver
> > britebot
> > cityglitch
> > marvellous-inc
> > pocket-rumble
> > soulstice
> > spellrazor
> >
> > From my side not a reason to keep aging version of luajit alive and I
> > would be ok with marking love/0.10 BROKEN to give a little time to see
> > if it can be patched up to work with the luajit update...
> >
>
> For the error I'm running into, it looks like it would be fixed by an
> update to newer luasocket, though the commit which updates it in the
> love2d tree is huge -
> https://github.com/love2d/love/commit/8885fc621dd01c3b8dfd1abf063785103d9daf15.patch
> - and doesn't directly apply to the version in 0.10.2 (and there's no
> 0.10 branch in their git repo so tracking down other needed commits is
> a bit awkward).
>
> How much would it suck to disable the jit for this version as is
> already done for 0.8?
I've built it with your diff and ran a few that I could: orthorobot
from packages, as well as Britebot, Marvellous Inc., and Soulstice.
All run fine. This is on a high-end CPU (Intel Xeon W-11955M), so the
effect of not using the JIT may be more noticeable on lower end
hardware. But this is still all very niche, so I think disabling the
JIT is the right move. ok thfr@
> Index: Makefile
> ===
> RCS file: /cvs/ports/games/love/0.10/Makefile,v
> diff -u -p -r1.2 Makefile
> --- Makefile 23 Jun 2023 17:35:54 - 1.2
> +++ Makefile 10 May 2024 10:22:57 -
> @@ -1,5 +1,6 @@
> VERSION =0.10.2
> -REVISION = 0
> +USE_LUAJIT = No
> +REVISION = 1
>
> SHARED_LIBS= love-${VERSION} 0.0
>
security/pinentry update
Here's an update to security/pinentry, the "pinentry-qt" binary is
now for Qt6 so I've added a separate package for that.
pinentry-gnome3 moves from x11/gnome/gcr to x11/gnome/gcr4.
Index: Makefile
===
RCS file: /cvs/ports/security/pinentry/Makefile,v
diff -u -p -w -u -r1.34 Makefile
--- Makefile2 Nov 2023 08:12:51 - 1.34
+++ Makefile10 May 2024 13:14:11 -
@@ -1,14 +1,13 @@
COMMENT-main = PIN or passphrase entry dialog (ncurses interface)
COMMENT-gnome3 =PIN or passphrase entry dialog (GNOME 3 interface)
COMMENT-qt5 = PIN or passphrase entry dialog (Qt5 interface)
+COMMENT-qt6 = PIN or passphrase entry dialog (Qt6 interface)
-VERSION = 1.2.1
+VERSION = 1.3.0
DISTNAME = pinentry-${VERSION}
CATEGORIES = security
EXTRACT_SUFX = .tar.bz2
-REVISION-qt5 = 0
-
SITES =${SITE_GNUPG:=pinentry/}
HOMEPAGE = https://www.gnupg.org/related_software/pinentry/index.en.html
@@ -30,22 +29,28 @@ LIB_DEPENDS = security/libassuan \
x11/gnome/libsecret
WANTLIB-gnome3 += ${WANTLIB}
-WANTLIB-gnome3 += atk-1.0 cairo cairo-gobject gck-1 gcr-base-3 gcr-ui-3
-WANTLIB-gnome3 += gdk-3 gdk_pixbuf-2.0 gtk-3 harfbuzz p11-kit pango-1.0
-WANTLIB-gnome3 += pangocairo-1.0
+WANTLIB-gnome3 += gck-2 gcr-4 p11-kit
LIB_DEPENDS-gnome3 = ${LIB_DEPENDS} \
- x11/gnome/gcr
+ x11/gnome/gcr4
WANTLIB-qt5 += ${WANTLIB}
WANTLIB-qt5 += ${COMPILER_LIBCXX} KF5WaylandClient Qt5Core Qt5Gui
WANTLIB-qt5 += Qt5Widgets Qt5X11Extras X11 m
+RUN_DEPENDS-qt5 = devel/desktop-file-utils
LIB_DEPENDS-qt5 = ${LIB_DEPENDS} \
devel/kf5/kwayland \
x11/qt5/qtbase \
x11/qt5/qtx11extras
+WANTLIB-qt6 += ${WANTLIB} ${COMPILER_LIBCXX}
+WANTLIB-qt6 += Qt6Core Qt6Gui Qt6Widgets m
+
+RUN_DEPENDS-qt6 = devel/desktop-file-utils
+LIB_DEPENDS-qt6 = ${LIB_DEPENDS} \
+ x11/qt6/qtbase
+
CONFIGURE_STYLE = gnu
CONFIGURE_ENV =CPPFLAGS="-I${LOCALBASE}/include
-D_XOPEN_SOURCE_EXTENDED" \
LDFLAGS="-L${LOCALBASE}/lib"
@@ -57,10 +62,10 @@ CONFIGURE_ARGS =--enable-pinentry-curs
--disable-pinentry-tqt \
--disable-pinentry-fltk
-MULTI_PACKAGES = -main -gnome3 -qt5
+MULTI_PACKAGES = -main -gnome3 -qt5 -qt6
-PSEUDO_FLAVORS=no_gnome3 no_qt5 bootstrap
-FLAVOR?= no_gnome3 no_qt5 bootstrap
+PSEUDO_FLAVORS=no_gnome3 no_qt5 no_qt6 bootstrap
+FLAVOR?= no_gnome3 no_qt5 no_qt6 bootstrap
.include
@@ -69,8 +74,11 @@ CONFIGURE_ARGS +=--disable-pinentry-gno
.endif
.if !${BUILD_PACKAGES:M-qt5}
-CONFIGURE_ARGS += --disable-pinentry-qt
CONFIGURE_ARGS += --disable-pinentry-qt5
+.endif
+
+.if !${BUILD_PACKAGES:M-qt6}
+CONFIGURE_ARGS += --disable-pinentry-qt
.endif
# http://pkgs.fedoraproject.org/cgit/pinentry.git/tree/pinentry-wrapper
Index: distinfo
===
RCS file: /cvs/ports/security/pinentry/distinfo,v
diff -u -p -w -u -r1.10 distinfo
--- distinfo30 Aug 2022 06:06:32 - 1.10
+++ distinfo10 May 2024 13:14:11 -
@@ -1,2 +1,2 @@
-SHA256 (pinentry-1.2.1.tar.bz2) = RXoYXlqFI4+5RalV3GNSq5YtyLSHILYvyfpIx1QKQGc=
-SIZE (pinentry-1.2.1.tar.bz2) = 547698
+SHA256 (pinentry-1.3.0.tar.bz2) = mzzVIm51l/L97TmaO8ZZkjNRU2VZ6dsIJpgbyjFklN4=
+SIZE (pinentry-1.3.0.tar.bz2) = 610363
Index: pkg/DESCR-qt6
===
RCS file: pkg/DESCR-qt6
diff -N pkg/DESCR-qt6
--- /dev/null 1 Jan 1970 00:00:00 -
+++ pkg/DESCR-qt6 10 May 2024 13:14:11 -
@@ -0,0 +1 @@
+This package provides a Qt6 interface to pinentry.
Index: pkg/PLIST-qt5
===
RCS file: /cvs/ports/security/pinentry/pkg/PLIST-qt5,v
diff -u -p -w -u -r1.2 PLIST-qt5
--- pkg/PLIST-qt5 11 Mar 2022 19:53:51 - 1.2
+++ pkg/PLIST-qt5 10 May 2024 13:14:11 -
@@ -1 +1,4 @@
-@bin bin/pinentry-qt
+@bin bin/pinentry-qt5
+share/applications/
+share/applications/org.gnupg.pinentry-qt5.desktop
+@tag update-desktop-database
Index: pkg/PLIST-qt6
===
RCS file: pkg/PLIST-qt6
diff -N pkg/PLIST-qt6
--- /dev/null 1 Jan 1970 00:00:00 -
+++ pkg/PLIST-qt6 10 May 2024 13:14:11 -
@@ -0,0 +1,5 @@
+@conflict pinentry-qt5-<1.3.0
+@bin bin/pinentry-qt
+share/applications/
+share/applications/org.gnupg.pinentry-qt.desktop
+@tag update-desktop-database
CVS: cvs.openbsd.org: ports
CVSROOT:/cvs Module name:ports Changes by: st...@cvs.openbsd.org 2024/05/10 07:09:13 Modified files: editors/vim: Makefile distinfo editors/vim/patches: patch-runtime_filetype_vim editors/vim/pkg: PLIST-main Log message: update to vim-9.1.404 For the xxd tool, when outputting colored hexdumps using the -R command line flag, together with -g1 (group every byte), -c 256 (format 256 octets per line), -d (show offsets in decimal) and -o (add offset to the file position), the buffer used to write to may overflow.
Re: openarena crash 7.5
On 2024/05/10 13:34, Divan Santana wrote:
> Thomas Frohwein writes:
>
> > On Thu, May 09, 2024 at 07:22:50PM +0200, Divan Santana wrote:
> >> Greetings :)
> >>
> >> Is openarena suppose to work from ports? Or perhaps it's my laptop
> >> that's not compatible with it?
>
> > This issue is fine to raise on ports@.
>
> Noted.
>
>
> > It's a BTCFI issue, see from
> > ktrace(1)/kdump(1) output:
>
> > 67964 openarena-client PSIG SIGILL SIG_DFL code=ILL_BTCFI
> > addr=0xf9ba34f3000 trapno=21
>
> Thanks. In layman's terms? Does this mean it's broken on all openbsd's
> or just my CPU/graphics card?
It's broken on newer intel CPUs.
It can probably be worked-around with this:
Index: Makefile
===
RCS file: /cvs/ports/games/openarena/Makefile,v
diff -u -p -r1.26 Makefile
--- Makefile25 Sep 2023 17:07:29 - 1.26
+++ Makefile10 May 2024 12:31:08 -
@@ -1,4 +1,5 @@
ONLY_FOR_ARCHS = amd64 i386 macppc
+USE_NOBTCFI = Yes
BROKEN-i386 = code/qcommon/vm_x86.c:(.text+0x18): undefined reference
to `callMask'
@@ -15,8 +16,8 @@ E_V = ${V}# engine version
PKGNAME = openarena-${V}
-REVISION-main =1
-REVISION-server = 0
+REVISION-main =2
+REVISION-server = 1
PKG_ARCH-data =*
Re: openarena crash 7.5
Thomas Frohwein writes: > On Thu, May 09, 2024 at 07:22:50PM +0200, Divan Santana wrote: >> Greetings :) >> >> Is openarena suppose to work from ports? Or perhaps it's my laptop >> that's not compatible with it? > This issue is fine to raise on ports@. Noted. > It's a BTCFI issue, see from > ktrace(1)/kdump(1) output: > 67964 openarena-client PSIG SIGILL SIG_DFL code=ILL_BTCFI addr=0xf9ba34f3000 > trapno=21 Thanks. In layman's terms? Does this mean it's broken on all openbsd's or just my CPU/graphics card?
CVS: cvs.openbsd.org: ports
CVSROOT:/cvs Module name:ports Changes by: rsadow...@cvs.openbsd.org 2024/05/10 06:10:08 Modified files: x11/qt5: Makefile.version x11/qt5/docs : distinfo x11/qt5/qt3d : Makefile distinfo x11/qt5/qtbase : Makefile distinfo x11/qt5/qtbase/patches: patch-src_network_ssl_qsslsocket_openssl_symbols_cpp x11/qt5/qtbase/pkg: PLIST-main x11/qt5/qtcharts: distinfo x11/qt5/qtconnectivity: Makefile distinfo x11/qt5/qtconnectivity/pkg: PLIST-examples x11/qt5/qtdatavis3d: distinfo x11/qt5/qtdeclarative: Makefile distinfo x11/qt5/qtgamepad: distinfo x11/qt5/qtgraphicaleffects: distinfo x11/qt5/qtimageformats: Makefile distinfo x11/qt5/qtlocation: Makefile distinfo x11/qt5/qtlottie: distinfo x11/qt5/qtmultimedia: Makefile distinfo x11/qt5/qtnetworkauth: distinfo x11/qt5/qtpurchasing: Makefile distinfo x11/qt5/qtquickcontrols: Makefile distinfo x11/qt5/qtquickcontrols2: Makefile distinfo x11/qt5/qtremoteobjects: distinfo x11/qt5/qtremoteobjects/pkg: PLIST-examples x11/qt5/qtscript: distinfo x11/qt5/qtscxml: distinfo x11/qt5/qtsensors: distinfo x11/qt5/qtserialbus: distinfo x11/qt5/qtserialport: distinfo x11/qt5/qtspeech: Makefile distinfo x11/qt5/qtsvg : Makefile distinfo x11/qt5/qttools: Makefile distinfo x11/qt5/qttranslations: distinfo x11/qt5/qtvirtualkeyboard: distinfo x11/qt5/qtwayland: Makefile distinfo x11/qt5/qtwebchannel: Makefile distinfo x11/qt5/qtwebengine: Makefile x11/qt5/qtwebengine/pkg: PLIST x11/qt5/qtwebglplugin: Makefile distinfo x11/qt5/qtwebkit: Makefile x11/qt5/qtwebsockets: Makefile distinfo x11/qt5/qtwebview: distinfo x11/qt5/qtwebview/pkg: PLIST-main x11/qt5/qtx11extras: distinfo x11/qt5/qtxmlpatterns: distinfo Log message: Update Qt5 to 5.15.13 (including the latest KDE patches)
CVS: cvs.openbsd.org: ports
CVSROOT:/cvs Module name:ports Changes by: st...@cvs.openbsd.org 2024/05/10 05:28:13 Modified files: multimedia/gstreamer1/plugins-good: Makefile multimedia/gstreamer1/plugins-good/pkg: PLIST Log message: +@pkgpath multimedia/gstreamer1/plugins-good,-main to fix update path (multipackages -> single) ok aja@
Re: patch dkimproxy: use rsa-sha256 in sample signing config
On Fri, 10 May 2024 10:47:43 +0100, Stuart Henderson wrote: > > On 2024/05/10 11:40, Matthieu Herrb wrote: > > > > Afaict dkimpproxy is not using opendkim but p5-Mail-DKIM. dkimproxy > > itself also hasn't seen a update since many years, but the underlying > > perl lib has been last updated last january (and could use an update > > in the port). > > > > So unless you imply that because many people use opendkim, ed25519 > > based signatures shouldn't be used at all I'm not sure I understand > > what you're saying. > > ed25519 can be used, but at the moment if you do use it, you probably > want to be double-signing with both that + rsa-sha256. > I imply that using ed25519 usually leads to malformed signature, and some big hosting providers treat double signature as bad signature if some of them are not RSA-SHA256. A notable example is icloud.com, which delivers all emails with double signatures to the junk folder. At least that's what they did the last time I checked in December'23. So I suggest to put in README and config exmaple that using anything other than RSA-SHA256 may lead to delivery email to thte junk. Unfortunately, this includes duble signatures as well. -- wbr, Kirill
Re: [new] devel/compiledb: compile_commands.json generator (also works with the kernel)
Up. Tests pass. On Fri, 3 May 2024 at 11:35, Mikhail Pchelin wrote: > I wasn't able to google how to generate compile_commands.json file for > the kernel to make clangd/LSP/vim work. > > It looks like the most used tool is a bear > (https://github.com/rizsotto/Bear), but during initial porting efforts I > found out that it doesn't work, I got constant crashes and pinsyscalls > messages in dmesg. > > compiledb is a much simpler python tool which parses gmake logs and > generates compile_commands.json file, it also works fine with the > OpenBSD kernel, which was the main motivation, I also tried jumping > around emacs sources - works fine, using option 3 from the README. > > Fail of option 2 for emacs is documented in make.py file of the > distribution, but I wasn't able to make the workaround fix it, given the > option 3, which works, seems not a bid deal? > > Thoughts? > > $ pkg_info compiledb-0.10.1 > Information for inst:compiledb-0.10.1 > > Comment: > compile_commands.json generator > > Description: > Tool for generating Clang's JSON Compilation Database file for GNU > make-based > build systems. > > Maintainer: The OpenBSD ports mailing-list > > WWW: https://github.com/nickdiego/compiledb > > $ cat /usr/local/share/doc/pkg-readmes/compiledb > > +--- > | Running compiledb on OpenBSD > > +--- > > compiledb supports only gmake for native compile_commands.json file > generation, > but you can try to feed usual make output to it through a pipe, or --parse > option. > > Examples: > > 1) To make compile_commands.json file for OpenBSD kernel use: > > cd /sys/arch/$(machine)/compile/GENERIC.MP > make -n | compiledb > mv compile_commands.json /sys > > 2) To get compilation db for another software, which uses gmake pass -c > option > for make subcommand: > > cd ~/work/software > compiledb -n make -c gmake > > 3) Above command runs 'gmake -Bnwk' and parses output, if your software > uses > autotools and enters endless ./configure stage, try removing -B switch and > pipe > the output without it: > > gmake -nwk | compiledb > >
Re: luajit, arm64, games/love/0.10
+cc op@, sorry I missed the maintainer line in ../Makefile.inc
[ original mail: https://marc.info/?l=openbsd-ports=171528886832093=2 ]
On 2024/05/09 20:06, Thomas Frohwein wrote:
> On Thu, May 09, 2024 at 10:09:39PM +0100, Stuart Henderson wrote:
>
> [...]
>
> > How useful is love/0.10, does it still make sense to keep it?
>
> There are a couple of nice (commercial) games that run with love-0.10:
>
> $ ls -1 0.10
> blue-revolver
> britebot
> cityglitch
> marvellous-inc
> pocket-rumble
> soulstice
> spellrazor
>
> From my side not a reason to keep aging version of luajit alive and I
> would be ok with marking love/0.10 BROKEN to give a little time to see
> if it can be patched up to work with the luajit update...
>
For the error I'm running into, it looks like it would be fixed by an
update to newer luasocket, though the commit which updates it in the
love2d tree is huge -
https://github.com/love2d/love/commit/8885fc621dd01c3b8dfd1abf063785103d9daf15.patch
- and doesn't directly apply to the version in 0.10.2 (and there's no
0.10 branch in their git repo so tracking down other needed commits is
a bit awkward).
How much would it suck to disable the jit for this version as is
already done for 0.8?
Index: Makefile
===
RCS file: /cvs/ports/games/love/0.10/Makefile,v
diff -u -p -r1.2 Makefile
--- Makefile23 Jun 2023 17:35:54 - 1.2
+++ Makefile10 May 2024 10:22:57 -
@@ -1,5 +1,6 @@
VERSION = 0.10.2
-REVISION = 0
+USE_LUAJIT = No
+REVISION = 1
SHARED_LIBS= love-${VERSION} 0.0
Re: patch dkimproxy: use rsa-sha256 in sample signing config
On 2024/05/10 11:40, Matthieu Herrb wrote: > On Fri, May 10, 2024 at 10:19:22AM +0100, Kirill A. Korinsky wrote: > > On Fri, 10 May 2024 06:57:20 +0100, > > Matthieu Herrb wrote: > > > > > > https://www.rfc-editor.org/rfc/rfc6376#section-3.3 says that > > > rsa-sha256 SHOULD be used. Unfortunatly Mail::DKIM::Signer uses > > > rsa-sha1 by default when no algorithm is specifed. > > > > > > Update the dkimproxy.out sample config... > > > > > > Make aboutmy.email (and other checkers) happier, and hopefully less > > > rejects by hotmail/google and co... > > > > > > comments? ok? > > > > > > > I'd like to point that using anything else whan RSA with SHA256 leads to > > issues. The cause is OpenDKIM which is widley used. It had well known issue > > with ed25519 [1] which probably will be fixed in the next release. > > > > Anyway, the last release had happened in 2015 and this project seems to be > > not that alive, so, no hope that it will be released and distributed soon. > > > > My point: let add reference to this issue and suggest to use only > > RSA/SHA256. > > > > Footnotes: > > [1] https://github.com/trusteddomainproject/OpenDKIM/issues/6 > > > Hi, > > Afaict dkimpproxy is not using opendkim but p5-Mail-DKIM. dkimproxy > itself also hasn't seen a update since many years, but the underlying > perl lib has been last updated last january (and could use an update > in the port). > > So unless you imply that because many people use opendkim, ed25519 > based signatures shouldn't be used at all I'm not sure I understand > what you're saying. ed25519 can be used, but at the moment if you do use it, you probably want to be double-signing with both that + rsa-sha256.
Re: patch dkimproxy: use rsa-sha256 in sample signing config
On Fri, May 10, 2024 at 10:19:22AM +0100, Kirill A. Korinsky wrote: > On Fri, 10 May 2024 06:57:20 +0100, > Matthieu Herrb wrote: > > > > https://www.rfc-editor.org/rfc/rfc6376#section-3.3 says that > > rsa-sha256 SHOULD be used. Unfortunatly Mail::DKIM::Signer uses > > rsa-sha1 by default when no algorithm is specifed. > > > > Update the dkimproxy.out sample config... > > > > Make aboutmy.email (and other checkers) happier, and hopefully less > > rejects by hotmail/google and co... > > > > comments? ok? > > > > I'd like to point that using anything else whan RSA with SHA256 leads to > issues. The cause is OpenDKIM which is widley used. It had well known issue > with ed25519 [1] which probably will be fixed in the next release. > > Anyway, the last release had happened in 2015 and this project seems to be > not that alive, so, no hope that it will be released and distributed soon. > > My point: let add reference to this issue and suggest to use only RSA/SHA256. > > Footnotes: > [1] https://github.com/trusteddomainproject/OpenDKIM/issues/6 > Hi, Afaict dkimpproxy is not using opendkim but p5-Mail-DKIM. dkimproxy itself also hasn't seen a update since many years, but the underlying perl lib has been last updated last january (and could use an update in the port). So unless you imply that because many people use opendkim, ed25519 based signatures shouldn't be used at all I'm not sure I understand what you're saying. -- Matthieu Herrb
Re: patch dkimproxy: use rsa-sha256 in sample signing config
On Fri, 10 May 2024 06:57:20 +0100, Matthieu Herrb wrote: > > https://www.rfc-editor.org/rfc/rfc6376#section-3.3 says that > rsa-sha256 SHOULD be used. Unfortunatly Mail::DKIM::Signer uses > rsa-sha1 by default when no algorithm is specifed. > > Update the dkimproxy.out sample config... > > Make aboutmy.email (and other checkers) happier, and hopefully less > rejects by hotmail/google and co... > > comments? ok? > I'd like to point that using anything else whan RSA with SHA256 leads to issues. The cause is OpenDKIM which is widley used. It had well known issue with ed25519 [1] which probably will be fixed in the next release. Anyway, the last release had happened in 2015 and this project seems to be not that alive, so, no hope that it will be released and distributed soon. My point: let add reference to this issue and suggest to use only RSA/SHA256. Footnotes: [1] https://github.com/trusteddomainproject/OpenDKIM/issues/6 -- wbr, Kirill
CVS: cvs.openbsd.org: ports
CVSROOT:/cvs Module name:ports Changes by: st...@cvs.openbsd.org 2024/05/10 02:04:36 Modified files: devel/swig : Makefile distinfo devel/swig/patches: patch-configure devel/swig/pkg : PLIST Log message: update to swig-4.2.1
CVS: cvs.openbsd.org: ports
CVSROOT:/cvs Module name:ports Changes by: st...@cvs.openbsd.org 2024/05/10 02:01:57 Modified files: devel/py-regex : Makefile distinfo Log message: update to py3-regex-2024.5.10
CVS: cvs.openbsd.org: ports
CVSROOT:/cvs Module name:ports Changes by: st...@cvs.openbsd.org 2024/05/10 02:01:47 Modified files: lang/php/8.3 : Tag: OPENBSD_7_5 Makefile distinfo Log message: update to php-8.3.7
CVS: cvs.openbsd.org: ports
CVSROOT:/cvs Module name:ports Changes by: st...@cvs.openbsd.org 2024/05/10 02:01:43 Modified files: lang/php/8.2 : Tag: OPENBSD_7_5 Makefile distinfo Log message: update to php-8.2.19
CVS: cvs.openbsd.org: ports
CVSROOT:/cvs Module name:ports Changes by: st...@cvs.openbsd.org 2024/05/10 02:01:37 Modified files: lang/php/8.3 : Makefile distinfo Log message: update to php-8.3.7
CVS: cvs.openbsd.org: ports
CVSROOT:/cvs Module name:ports Changes by: st...@cvs.openbsd.org 2024/05/10 02:01:32 Modified files: lang/php/8.2 : Makefile distinfo Log message: update to php-8.2.19
CVS: cvs.openbsd.org: ports
CVSROOT:/cvs Module name:ports Changes by: st...@cvs.openbsd.org 2024/05/10 01:22:01 Modified files: devel/py-test-isort: Makefile distinfo Removed files: devel/py-test-isort/patches: patch-pyproject_toml Log message: update to py3-test-isort-4.0.0
CVS: cvs.openbsd.org: ports
CVSROOT:/cvs Module name:ports Changes by: st...@cvs.openbsd.org 2024/05/10 01:22:04 Modified files: devel/py-rich : Makefile distinfo Log message: update to py3-rich-13.7.1
CVS: cvs.openbsd.org: ports
CVSROOT:/cvs Module name:ports Changes by: st...@cvs.openbsd.org 2024/05/10 01:18:24 Modified files: devel/py-test-relaxed: Makefile distinfo Log message: update to py3-test-relaxed-2.0.2
CVS: cvs.openbsd.org: ports
CVSROOT:/cvs Module name:ports Changes by: st...@cvs.openbsd.org 2024/05/10 01:12:55 Modified files: devel/py-flaky : Makefile distinfo devel/py-flaky/pkg: PLIST Log message: update to py3-flaky-3.8.1
CVS: cvs.openbsd.org: ports
CVSROOT:/cvs Module name:ports Changes by: st...@cvs.openbsd.org 2024/05/10 01:12:51 Modified files: devel/py-exceptiongroup: Makefile distinfo devel/py-exceptiongroup/pkg: PLIST Log message: update to py3-exceptiongroup-1.2.1
Re: patch dkimproxy: use rsa-sha256 in sample signing config
On 5/10/24 01:57, Matthieu Herrb wrote: > Hi > > > I use dkimpproxy on my outgoing e-mail. > > https://www.rfc-editor.org/rfc/rfc6376#section-3.3 says that > rsa-sha256 SHOULD be used. Unfortunatly Mail::DKIM::Signer uses > rsa-sha1 by default when no algorithm is specifed. > > Update the dkimproxy.out sample config... > > Make aboutmy.email (and other checkers) happier, and hopefully less > rejects by hotmail/google and co... > > comments? ok? makes sense OK aisha > > Index: Makefile > === > RCS file: /local/cvs/ports/mail/dkimproxy/Makefile,v > diff -u -p -u -r1.8 Makefile > --- Makefile 7 Nov 2023 14:19:36 - 1.8 > +++ Makefile 10 May 2024 05:51:47 - > @@ -1,7 +1,7 @@ > COMMENT =SMTP proxy to verify or add DKIM signatures > > DISTNAME = dkimproxy-1.4.1 > -REVISION = 3 > +REVISION = 4 > > CATEGORIES = mail > > Index: patches/patch-scripts_dkimproxy_out_conf_example > === > RCS file: patches/patch-scripts_dkimproxy_out_conf_example > diff -N patches/patch-scripts_dkimproxy_out_conf_example > --- /dev/null 1 Jan 1970 00:00:00 - > +++ patches/patch-scripts_dkimproxy_out_conf_example 10 May 2024 05:51:47 > - > @@ -0,0 +1,15 @@ > +Default to rsa-sha256 > +https://www.rfc-editor.org/rfc/rfc6376#section-3.3 > + > +Index: scripts/dkimproxy_out.conf.example > +--- scripts/dkimproxy_out.conf.example.orig > scripts/dkimproxy_out.conf.example > +@@ -8,7 +8,7 @@ relay 127.0.0.1:10028 > + domainexample.org > + > + # specify what signatures to add > +-signature dkim(c=relaxed) > ++signature dkim(a=rsa-sha256,c=relaxed) > + signature domainkeys(c=nofws) > + > + # specify location of the private key >
aarch64 bulk build report
bulk build on arm64.ports.openbsd.org started on Tue May 7 01:06:26 MDT 2024 finished at Fri May 10 00:31:20 MDT 2024 lasted 2D23h24m done with kern.version=OpenBSD 7.5-current (GENERIC.MP) #0: Tue May 7 10:32:40 MDT 2024 built packages:12162 May 7:4052 May 8:613 May 9:5577 May 10:1919 critical path missing pkgs: http://build-failures.rhaalovely.net/aarch64/2024-05-07/summary.log build failures: 19 http://build-failures.rhaalovely.net/aarch64/2024-05-07/astro/py-astropy,python3.log http://build-failures.rhaalovely.net/aarch64/2024-05-07/devel/keystone/python,python3.log http://build-failures.rhaalovely.net/aarch64/2024-05-07/devel/py-tqdm,python3.log http://build-failures.rhaalovely.net/aarch64/2024-05-07/emulators/dolphin,-main.log http://build-failures.rhaalovely.net/aarch64/2024-05-07/games/pysol.log http://build-failures.rhaalovely.net/aarch64/2024-05-07/games/recoil-rts.log http://build-failures.rhaalovely.net/aarch64/2024-05-07/mail/altermime.log http://build-failures.rhaalovely.net/aarch64/2024-05-07/math/py-cvxpy,python3.log http://build-failures.rhaalovely.net/aarch64/2024-05-07/net/jitsi/videobridge.log http://build-failures.rhaalovely.net/aarch64/2024-05-07/plan9/plan9port.log http://build-failures.rhaalovely.net/aarch64/2024-05-07/print/pdfarranger.log http://build-failures.rhaalovely.net/aarch64/2024-05-07/sysutils/py-tsk,python3.log http://build-failures.rhaalovely.net/aarch64/2024-05-07/textproc/py-ruamel.yaml,python3.log http://build-failures.rhaalovely.net/aarch64/2024-05-07/www/netsurf/netsurf-fb.log http://build-failures.rhaalovely.net/aarch64/2024-05-07/www/py-aiohttp,python3.log http://build-failures.rhaalovely.net/aarch64/2024-05-07/www/py-autobahn,python3.log http://build-failures.rhaalovely.net/aarch64/2024-05-07/www/py-requests-toolbelt,python3.log http://build-failures.rhaalovely.net/aarch64/2024-05-07/www/py-urlgrabber,python3.log http://build-failures.rhaalovely.net/aarch64/2024-05-07/www/urlwatch.log recurrent failures failures/emulators/dolphin,-main.log failures/plan9/plan9port.log new failures +++ ls-failures Fri May 10 00:32:58 2024 +failures/astro/py-astropy,python3.log +failures/devel/keystone/python,python3.log +failures/devel/py-tqdm,python3.log +failures/games/pysol.log +failures/games/recoil-rts.log +failures/mail/altermime.log +failures/math/py-cvxpy,python3.log +failures/net/jitsi/videobridge.log +failures/print/pdfarranger.log +failures/sysutils/py-tsk,python3.log +failures/textproc/py-ruamel.yaml,python3.log +failures/www/netsurf/netsurf-fb.log +failures/www/py-aiohttp,python3.log +failures/www/py-autobahn,python3.log +failures/www/py-requests-toolbelt,python3.log +failures/www/py-urlgrabber,python3.log +failures/www/urlwatch.log resolved failures --- ../old/aarch64/last//ls-failuresMon May 6 05:59:35 2024 -failures/lang/v.log
