Upgrade productivity/hledger 1.23->1.24.1
I'm running this locally. Works fine so far. OK?
>From 4510646152e1b7c94ed11675e180b7acebdd989e Mon Sep 17 00:00:00 2001
From: Greg Steuck
Date: Wed, 19 Jan 2022 22:27:06 -0800
Subject: [PATCH] Upgrade productivity/hledger 1.23->1.24.1
---
productivity/hledger/Makefile | 94 ---
productivity/hledger/distinfo | 214 +-
2 files changed, 182 insertions(+), 126 deletions(-)
diff --git a/productivity/hledger/Makefile b/productivity/hledger/Makefile
index 215939cffc7..29e501c8ce4 100644
--- a/productivity/hledger/Makefile
+++ b/productivity/hledger/Makefile
@@ -21,38 +21,42 @@ MAKE_ENV = LC_ALL=en_US.UTF-8
MODULES = devel/cabal
MODCABAL_STEM =hledger
-MODCABAL_VERSION = 1.23
+MODCABAL_VERSION = 1.24.1
post-install:
@${INSTALL_MAN} ${WRKSRC}/hledger.1 ${PREFIX}/man/man1
MODCABAL_MANIFEST = \
Decimal 0.5.2 0 \
- Diff0.4.0 0 \
- Glob0.10.1 1 \
+ Diff0.4.1 0 \
+ Glob0.10.2 3 \
+ OneTuple0.3.1 2 \
Only0.1 1 \
- aeson 1.5.6.0 2 \
- aeson-pretty0.8.8 0 \
- ansi-terminal 0.110 \
- ansi-wl-pprint 0.6.9 2 \
- assoc 1.0.2 1 \
- attoparsec 0.14.1 0 \
- base-compat 0.11.2 0 \
- base-compat-batteries 0.11.2 0 \
- base-orphans0.8.5 0 \
+ QuickCheck 2.14.2 0 \
+ StateVar1.2.2 0 \
+ aeson 2.0.3.0 0 \
+ aeson-pretty0.8.9 1 \
+ ansi-terminal 0.11.1 0 \
+ ansi-wl-pprint 0.6.9 3 \
+ assoc 1.0.2 2 \
+ attoparsec 0.14.4 1 \
+ base-compat 0.12.1 0 \
+ base-compat-batteries 0.12.1 2 \
+ base-orphans0.8.6 0 \
bifunctors 5.5.11 1 \
- blaze-builder 0.4.2.1 0 \
+ blaze-builder 0.4.2.2 1 \
blaze-html 0.9.1.2 1 \
- blaze-markup0.8.2.8 0 \
- cabal-doctest 1.0.8 2 \
+ blaze-markup0.8.2.8 1 \
+ cabal-doctest 1.0.9 0 \
call-stack 0.4.0 0 \
case-insensitive1.2.1.0 0 \
- cassava 0.5.2.0 4 \
- cassava-megaparsec 2.0.2 0 \
+ cassava 0.5.2.0 7 \
+ cassava-megaparsec 2.0.4 0 \
clock 0.8.2 0 \
cmdargs 0.10.21 0 \
colour 2.3.6 0 \
comonad 5.0.8 1 \
+ contravariant 1.5.5 0 \
control-monad-free 0.6.2 0 \
csv 0.1.2 0 \
data-default0.7.1.1 0 \
@@ -60,61 +64,67 @@ MODCABAL_MANIFEST = \
data-default-instances-containers 0.0.1 0 \
data-default-instances-dlist0.0.1 0 \
data-default-instances-old-locale 0.0.1 0 \
- data-fix0.3.2 0 \
+ data-fix0.3.2 2 \
distributive0.6.2.1 1 \
dlist 1.0 0 \
+ doclayout 0.3.1.1 0 \
+ emojis 0.1.2 0 \
extra 1.7.10 0 \
file-embed 0.0.15.00 \
githash 0.1.6.2 0 \
- hashable1.3.3.0 0 \
- hashtables 1.2.4.1 0 \
- hledger-lib 1.230 \
+ hashable1.4.0.2 0 \
+ hashtables 1.3 0 \
+ hledger-lib 1.24.1 0 \
html1.0.1.2 0 \
- indexed-traversable 0.1.1 1 \
- integer-logarithms 1.0.3.1 0 \
- lucid 2.9.12.10 \
+ indexed-traversable 0.1.2 1 \
+ indexed-traversable-instances 0.1.1 0 \
+ integer-logarithms 1.0.3.1 2 \
+ lucid 2.11.0 1 \
math-functions 0.3.4.2 0 \
- megaparsec 9.1.0 1 \
+ megaparsec 9.2.0 1 \
microlens 0.4.12.00 \
microlens-th0.4.3.100 \
mmorph 1.2.0 1 \
old-locale 1.0.0.7 2 \
- optparse-applicative0.16.1.01 \
+ optparse-applicative0.16.1.02 \
parser-combinators 1.3.0 0 \
pretty-simple 4.0.0.0 0 \
prettyprinter 1.7.1 0 \
prettyprinter-ansi-terminal 1.1.3 0 \
- primitive 0.7.2.0 0 \
+ primitive 0.7.3.0 0 \
random 1.2.1 0 \
- regex-base 0.94.0.11 \
- regex-tdfa 1.3.1.1 1 \
+ regex-base 0.94.0.20 \
+ regex-tdfa 1.3.1.1 2 \
Re: rox-filer on -current has been slow for a week or so.
On Wed, 19 Jan 2022 11:04:09 + Stuart Henderson wrote: > On 2022/01/18 19:23, Ed Ahlsen-Girard wrote: > [...] > > First thing to try is a self-built kernel to check if it's some > uncommitted diff being tested in snapshots. > > If that doesn't change anything then go back to older kernel code, > leaving userland alone. I would do a kernel build with a date-based > cvs checkout to see this (e.g. cvs up -D 2022/01/10). > > Basically try to narrow down what area was changed that caused it to > slow down. > > [...] I can't, a reason that is not obvious to me: [hostname]# make obj mkdir: /usr/obj/sys: Permission denied *** Error 1 in /sys/arch/amd64/compile/GENERIC.MP (:61 'obj': @cd /sys/arch/amd64/compile/GENERIC.MP; umask 007; here=`/bin/pw...) make obj was run from an su session. -- Edward Ahlsen-Girard Ft Walton Beach, FL
lang/jruby 9.3.3.0
Simple update to the latest release of JRuby. Release notes available
at: https://www.jruby.org/2022/01/19/jruby-9-3-3-0.html
Tested on amd64, the only supported arch. Will commit in a couple days
unless I hear objections.
Thanks,
Jeremy
Index: Makefile
===
RCS file: /cvs/ports/lang/jruby/Makefile,v
retrieving revision 1.98
diff -u -p -r1.98 Makefile
--- Makefile5 Dec 2021 03:55:06 - 1.98
+++ Makefile19 Jan 2022 17:53:55 -
@@ -5,7 +5,7 @@ ONLY_FOR_ARCHS = amd64
COMMENT = pure-Java implementation of the Ruby language
-V =9.3.2.0
+V =9.3.3.0
DISTNAME = jruby-dist-${V}-bin
PKGNAME = jruby-${V}
CATEGORIES = lang lang/ruby
Index: distinfo
===
RCS file: /cvs/ports/lang/jruby/distinfo,v
retrieving revision 1.65
diff -u -p -r1.65 distinfo
--- distinfo5 Dec 2021 03:55:06 - 1.65
+++ distinfo19 Jan 2022 17:54:08 -
@@ -1,6 +1,6 @@
SHA256 (jffi-1.3.5.tar.gz) = 15HSIg5X5jGP9s1jfd64nWu4O9HkJivnhS9tVmnLLrQ=
-SHA256 (jruby-dist-9.3.2.0-bin.tar.gz) =
JmmcoCvur6gyZXPBElxXpZcbqLlNFfhOazuvJZQkTzM=
+SHA256 (jruby-dist-9.3.3.0-bin.tar.gz) =
Pagoy+KH1UaFB/HCxCvvbPNLxTYbzWpdmcIHshuf3Fw=
SHA256 (jruby-launcher-1.1.19-java.gem) =
LPGrpNcsdLNq7MSjCxiSXh4h+vcPVuC0ykUyUYquGJo=
SIZE (jffi-1.3.5.tar.gz) = 3152240
-SIZE (jruby-dist-9.3.2.0-bin.tar.gz) = 27718285
+SIZE (jruby-dist-9.3.3.0-bin.tar.gz) = 27722213
SIZE (jruby-launcher-1.1.19-java.gem) = 64000
Index: pkg/PLIST
===
RCS file: /cvs/ports/lang/jruby/pkg/PLIST,v
retrieving revision 1.56
diff -u -p -r1.56 PLIST
--- pkg/PLIST 5 Dec 2021 03:55:06 - 1.56
+++ pkg/PLIST 19 Jan 2022 17:55:16 -
@@ -436,7 +436,7 @@ jruby/lib/ruby/gems/1.8/specifications/d
jruby/lib/ruby/gems/1.8/specifications/default/logger-1.3.0.gemspec
jruby/lib/ruby/gems/1.8/specifications/default/matrix-0.3.0.gemspec
jruby/lib/ruby/gems/1.8/specifications/default/mutex_m-0.1.0.gemspec
-jruby/lib/ruby/gems/1.8/specifications/default/ostruct-0.1.0.gemspec
+jruby/lib/ruby/gems/1.8/specifications/default/ostruct-0.5.1.gemspec
jruby/lib/ruby/gems/1.8/specifications/default/prime-0.1.0.gemspec
jruby/lib/ruby/gems/1.8/specifications/default/psych-3.3.2-java.gemspec
jruby/lib/ruby/gems/1.8/specifications/default/racc-1.5.2-java.gemspec
Re: net/gophernicus: drop scary paragraph from the readme
Tracey Emery writes: > On Wed, Jan 19, 2022 at 10:20:47PM +0100, Omar Polo wrote: >> Solène Rapenne writes: >> >> > Le Wed, 19 Jan 2022 13:47:54 -0700, >> > Tracey Emery a écrit : >> > >> >> On Wed, Jan 19, 2022 at 09:25:34PM +0100, Omar Polo wrote: >> >> > Hello, >> >> > >> >> > I was playing with gophernicus and noted that the installed readme says: >> >> > >> >> > > Development! DO NOT USE unless you want fiery dragons! >> >> > > (you probably want to `git checkout 3.0.1`) >> >> > >> >> > my interpretation is that the paragraph is meant to discourage people >> >> > from running gophernicus from the master branch, but we're already >> >> > fetching a tagged version. (no 'fiery dragons' for us unfortunately) >> >> > >> >> > I was a bit puzzled when reading the documentation, what about dropping >> >> > the sentence? Or maybe it's clear enough? >> >> > >> >> >> >> This seems an unnecessary patch to carry to me. >> > >> > indeed, I don't see much value into patching every bad documentation >> > provided in packages. At best, you should ask upstream to change the >> > way they do to avoid such situations. >> >> ack. there's also not much value into switching to the uploaded >> distfile now. > > None? Part of the suggestion from sthen was to go from 3.0.1 to 3.1.1, > wasn't it? Pledge and unveil support seem worth the effort, although I > don't use the app. Just a thought. :) I completely missed the version change, sorry. I'll take a look at updating it. thanks for pointing it out, I thought sthen linked the distfile for the current port version. >> >> sorry for the noise :) >>
Re: net/gophernicus: drop scary paragraph from the readme
On Wed, Jan 19, 2022 at 10:20:47PM +0100, Omar Polo wrote: > Solène Rapenne writes: > > > Le Wed, 19 Jan 2022 13:47:54 -0700, > > Tracey Emery a écrit : > > > >> On Wed, Jan 19, 2022 at 09:25:34PM +0100, Omar Polo wrote: > >> > Hello, > >> > > >> > I was playing with gophernicus and noted that the installed readme says: > >> > > >> > > Development! DO NOT USE unless you want fiery dragons! > >> > > (you probably want to `git checkout 3.0.1`) > >> > > >> > my interpretation is that the paragraph is meant to discourage people > >> > from running gophernicus from the master branch, but we're already > >> > fetching a tagged version. (no 'fiery dragons' for us unfortunately) > >> > > >> > I was a bit puzzled when reading the documentation, what about dropping > >> > the sentence? Or maybe it's clear enough? > >> > > >> > >> This seems an unnecessary patch to carry to me. > > > > indeed, I don't see much value into patching every bad documentation > > provided in packages. At best, you should ask upstream to change the > > way they do to avoid such situations. > > ack. there's also not much value into switching to the uploaded > distfile now. None? Part of the suggestion from sthen was to go from 3.0.1 to 3.1.1, wasn't it? Pledge and unveil support seem worth the effort, although I don't use the app. Just a thought. :) > > sorry for the noise :) > -- Tracey Emery
Re: net/gophernicus: drop scary paragraph from the readme
Solène Rapenne writes: > Le Wed, 19 Jan 2022 13:47:54 -0700, > Tracey Emery a écrit : > >> On Wed, Jan 19, 2022 at 09:25:34PM +0100, Omar Polo wrote: >> > Hello, >> > >> > I was playing with gophernicus and noted that the installed readme says: >> > >> > > Development! DO NOT USE unless you want fiery dragons! >> > > (you probably want to `git checkout 3.0.1`) >> > >> > my interpretation is that the paragraph is meant to discourage people >> > from running gophernicus from the master branch, but we're already >> > fetching a tagged version. (no 'fiery dragons' for us unfortunately) >> > >> > I was a bit puzzled when reading the documentation, what about dropping >> > the sentence? Or maybe it's clear enough? >> > >> >> This seems an unnecessary patch to carry to me. > > indeed, I don't see much value into patching every bad documentation > provided in packages. At best, you should ask upstream to change the > way they do to avoid such situations. ack. there's also not much value into switching to the uploaded distfile now. sorry for the noise :)
Re: net/gophernicus: drop scary paragraph from the readme
On 2022/01/19 21:25, Omar Polo wrote: > Hello, > > I was playing with gophernicus and noted that the installed readme says: > > > Development! DO NOT USE unless you want fiery dragons! > > (you probably want to `git checkout 3.0.1`) > > my interpretation is that the paragraph is meant to discourage people > from running gophernicus from the master branch, but we're already > fetching a tagged version. (no 'fiery dragons' for us unfortunately) > > I was a bit puzzled when reading the documentation, what about dropping > the sentence? Or maybe it's clear enough? The port should switch to the uploaded distfile e.g. https://github.com/gophernicus/gophernicus/releases/download/3.1.1/gophernicus-3.1.1.tar.gz > > Index: Makefile > === > RCS file: /home/cvs/ports/net/gophernicus/Makefile,v > retrieving revision 1.20 > diff -u -p -r1.20 Makefile > --- Makefile 13 Feb 2021 14:13:37 - 1.20 > +++ Makefile 19 Jan 2022 20:23:38 - > @@ -1,7 +1,7 @@ > # $OpenBSD: Makefile,v 1.20 2021/02/13 14:13:37 bcallah Exp $ > > COMMENT= modern gopher server > -REVISION = 0 > +REVISION = 1 > > GH_ACCOUNT= gophernicus > GH_PROJECT= gophernicus > Index: patches/patch-README_md > === > RCS file: patches/patch-README_md > diff -N patches/patch-README_md > --- /dev/null 1 Jan 1970 00:00:00 - > +++ patches/patch-README_md 19 Jan 2022 20:23:28 - > @@ -0,0 +1,17 @@ > +$OpenBSD$ > + > +we're already using the stable version > + > +Index: README.md > +--- README.md.orig > README.md > +@@ -2,9 +2,6 @@ > + > + Version 3.0.1 > + > +-Development! DO NOT USE unless you want fiery dragons! > +-(you probably want to `git checkout 3.0.1`) > +- > + *Copyright (c) 2009-2019 Kim Holviala and others* > + > + Gophernicus is a modern full-featured (and hopefully) secure gopher >
Re: net/gophernicus: drop scary paragraph from the readme
On Wed, Jan 19, 2022 at 09:25:34PM +0100, Omar Polo wrote: > Hello, > > I was playing with gophernicus and noted that the installed readme says: > > > Development! DO NOT USE unless you want fiery dragons! > > (you probably want to `git checkout 3.0.1`) > > my interpretation is that the paragraph is meant to discourage people > from running gophernicus from the master branch, but we're already > fetching a tagged version. (no 'fiery dragons' for us unfortunately) > > I was a bit puzzled when reading the documentation, what about dropping > the sentence? Or maybe it's clear enough? > This seems an unnecessary patch to carry to me. > > Index: Makefile > === > RCS file: /home/cvs/ports/net/gophernicus/Makefile,v > retrieving revision 1.20 > diff -u -p -r1.20 Makefile > --- Makefile 13 Feb 2021 14:13:37 - 1.20 > +++ Makefile 19 Jan 2022 20:23:38 - > @@ -1,7 +1,7 @@ > # $OpenBSD: Makefile,v 1.20 2021/02/13 14:13:37 bcallah Exp $ > > COMMENT= modern gopher server > -REVISION = 0 > +REVISION = 1 > > GH_ACCOUNT= gophernicus > GH_PROJECT= gophernicus > Index: patches/patch-README_md > === > RCS file: patches/patch-README_md > diff -N patches/patch-README_md > --- /dev/null 1 Jan 1970 00:00:00 - > +++ patches/patch-README_md 19 Jan 2022 20:23:28 - > @@ -0,0 +1,17 @@ > +$OpenBSD$ > + > +we're already using the stable version > + > +Index: README.md > +--- README.md.orig > README.md > +@@ -2,9 +2,6 @@ > + > + Version 3.0.1 > + > +-Development! DO NOT USE unless you want fiery dragons! > +-(you probably want to `git checkout 3.0.1`) > +- > + *Copyright (c) 2009-2019 Kim Holviala and others* > + > + Gophernicus is a modern full-featured (and hopefully) secure gopher > -- Tracey Emery
net/gophernicus: drop scary paragraph from the readme
Hello, I was playing with gophernicus and noted that the installed readme says: > Development! DO NOT USE unless you want fiery dragons! > (you probably want to `git checkout 3.0.1`) my interpretation is that the paragraph is meant to discourage people from running gophernicus from the master branch, but we're already fetching a tagged version. (no 'fiery dragons' for us unfortunately) I was a bit puzzled when reading the documentation, what about dropping the sentence? Or maybe it's clear enough? Index: Makefile === RCS file: /home/cvs/ports/net/gophernicus/Makefile,v retrieving revision 1.20 diff -u -p -r1.20 Makefile --- Makefile13 Feb 2021 14:13:37 - 1.20 +++ Makefile19 Jan 2022 20:23:38 - @@ -1,7 +1,7 @@ # $OpenBSD: Makefile,v 1.20 2021/02/13 14:13:37 bcallah Exp $ COMMENT= modern gopher server -REVISION = 0 +REVISION = 1 GH_ACCOUNT=gophernicus GH_PROJECT=gophernicus Index: patches/patch-README_md === RCS file: patches/patch-README_md diff -N patches/patch-README_md --- /dev/null 1 Jan 1970 00:00:00 - +++ patches/patch-README_md 19 Jan 2022 20:23:28 - @@ -0,0 +1,17 @@ +$OpenBSD$ + +we're already using the stable version + +Index: README.md +--- README.md.orig README.md +@@ -2,9 +2,6 @@ + + Version 3.0.1 + +-Development! DO NOT USE unless you want fiery dragons! +-(you probably want to `git checkout 3.0.1`) +- + *Copyright (c) 2009-2019 Kim Holviala and others* + + Gophernicus is a modern full-featured (and hopefully) secure gopher
Re: [sparc64] Change COMPILER line of www/webkitgtk4
On Wed, Jan 19 2022, Kurt Mosiejczuk wrote: > On Wed, Jan 19, 2022 at 05:47:46PM +, Stuart Henderson wrote: > >> > # gcc>=5.0.0 or clang >> > -COMPILER =base-clang ports-clang ports-gcc >> > +COMPILER =base-clang ports-gcc ports-clang > >> Better just remove ports-clang I think. > > Yeah. I thought of adding a line about "or just drop ports-clang". > > Is it worth dropping the comment too? IMO yes. > --Kurt > >> > MODRUBY_RUNDEP = No >> > MODPY_RUNDEP =No >> > > -- jca | PGP : 0x1524E7EE / 5135 92C1 AD36 5293 2BDF DDCC 0DFA 74AE 1524 E7EE
Re: [sparc64] Change COMPILER line of www/webkitgtk4
No objection — Antoine > On 19 Jan 2022, at 18:44, Kurt Mosiejczuk wrote: > > The current issues with ports-clang on sparc64 pointed out something that > should change for webkitgtk4. > > The COMPILER line currently is "base-clang ports-clang ports-gcc". This was > apparently done back before ports-gcc was its current 8.x version. There's > no real reason now for it and it keeps sparc64 from building it while the > clang/llvm problems persists for sparc64. > > ok to change it? > > (cc maintainer) > > --Kurt > > Index: Makefile > === > RCS file: /cvs/ports/www/webkitgtk4/Makefile,v > retrieving revision 1.159 > diff -u -p -r1.159 Makefile > --- Makefile21 Dec 2021 15:08:08 -1.159 > +++ Makefile19 Jan 2022 17:40:32 - > @@ -52,7 +52,7 @@ MODULES =devel/cmake \ >x11/gnome > > # gcc>=5.0.0 or clang > -COMPILER =base-clang ports-clang ports-gcc > +COMPILER =base-clang ports-gcc ports-clang > > MODRUBY_RUNDEP =No > MODPY_RUNDEP =No
net/openfire update to 4.6.7 fix log4shell
Update to 4.6.7, which uses log4j 2.1.7. Use modern Java runtime. Drop
some trivial sampled files. Use provided class files instead
of compiling, to speed build. Take Maintainer in case I'm the only
one still using it :-).
OK?
And yes, I know they released 4.7.0 an hour ago, but (a) it's a brand new
major release, not tested, and (b) I'd like to get this out ASAP due to log4j.
Index: Makefile
===
RCS file: /cvs/ports/net/openfire/Makefile,v
retrieving revision 1.54
diff -u -p -r1.54 Makefile
--- Makefile23 Sep 2019 15:14:25 - 1.54
+++ Makefile19 Jan 2022 17:47:22 -
@@ -1,9 +1,8 @@
# $OpenBSD: Makefile,v 1.54 2019/09/23 15:14:25 kurt Exp $
COMMENT= XMPP real time collaboration server
-V= 4.2.3
-REVISION= 1
-DISTNAME= openfire_src_${V:S/./_/g}
+V= 4.6.7
+DISTNAME= openfire_${V:S/./_/g}
PKGNAME= openfire-$V
CATEGORIES=net
@@ -11,46 +10,44 @@ MASTER_SITES= https://www.igniterealtime
HOMEPAGE= https://www.igniterealtime.org/projects/openfire/index.jsp
+MAINTAINER=Ian Darwin
+
# ASL 2.0
PERMIT_PACKAGE=Yes
+NO_BUILD= yes
NO_TEST= yes
MODULES= java
-MODJAVA_VER= 1.8
+MODJAVA_VER= 17
MODJAVA_JRE= Yes
-MODJAVA_BUILD= ant
RUN_DEPENDS= java/javaPathHelper
-WRKDIST= ${WRKDIR}/openfire_src
-WRKSRC=${WRKDIST}/build
+WRKDIST= ${WRKDIR}/openfire
OPENFIREDEST= ${PREFIX}/openfire
-DATADIRS= lib logs plugins resources
-
-pre-install:
- rm -rf ${WRKDIST}/target/openfire/resources/nativeAuth
- mv ${WRKDIST}/target/openfire/resources/security ${WRKBUILD}
+DATADIRS= lib plugins resources
+DOCDIRS= documentation
do-install:
- cd ${WRKDIST}/target/openfire && \
+ rm -rf ${WRKDIST}/resources/nativeAuth
+ cd ${WRKDIST} && \
find ${DATADIRS} -type d \
-exec ${INSTALL_DATA_DIR} ${OPENFIREDEST}/{} \; && \
find ${DATADIRS} ! -type d \
-exec ${INSTALL_DATA} -m 644 {} ${OPENFIREDEST}/{} \;
- ${INSTALL_DATA_DIR} ${PREFIX}/share/doc/openfire
- ${INSTALL_DATA} ${WRKDIST}/documentation/docs/*-guide.html \
- ${PREFIX}/share/doc/openfire
- ${INSTALL_DATA} ${WRKDIST}/documentation/docs/database.html \
- ${PREFIX}/share/doc/openfire
- ${INSTALL_DATA_DIR} ${PREFIX}/share/examples/openfire/security
+ cd ${WRKDIST} && \
+ find ${DOCDIRS} -type d \
+ -exec ${INSTALL_DATA_DIR}
${PREFIX}/share/doc/openfire/{} \; && \
+ find ${DOCDIRS}/* ! -type d \
+ -exec ${INSTALL_DATA} -m 644 {}
${PREFIX}/share/doc/openfire \;
+ ${INSTALL_DATA_DIR} ${OPENFIREDEST}/logs
${INSTALL_DATA_DIR} ${PREFIX}/share/examples/openfire/
- ${INSTALL_DATA} ${WRKDIST}/target/openfire/conf/openfire.xml \
+ ${INSTALL_DATA_DIR} ${PREFIX}/share/examples/openfire/security
+ ${INSTALL_DATA} ${WRKDIST}/conf/openfire.xml \
${PREFIX}/share/examples/openfire/
- ${INSTALL_DATA} ${WRKDIST}/target/openfire/conf/security.xml \
+ ${INSTALL_DATA} ${WRKDIST}/conf/security.xml \
${PREFIX}/share/examples/openfire/
- ${INSTALL_DATA} ${WRKBUILD}/security/* \
- ${PREFIX}/share/examples/openfire/security
.include
Index: distinfo
===
RCS file: /cvs/ports/net/openfire/distinfo,v
retrieving revision 1.19
diff -u -p -r1.19 distinfo
--- distinfo1 Oct 2018 20:08:53 - 1.19
+++ distinfo19 Jan 2022 17:47:22 -
@@ -1,2 +1,2 @@
-SHA256 (openfire_src_4_2_3.tar.gz) =
mpAbzQaSDMtbQXUX2wKaSiC3ddSao52RipltSq9HQww=
-SIZE (openfire_src_4_2_3.tar.gz) = 113557155
+SHA256 (openfire_4_6_7.tar.gz) = ayunxJdtvTYkkmmkU+sXbXGh5/gFdZUc3Rc9DsQkcFY=
+SIZE (openfire_4_6_7.tar.gz) = 48681460
Index: pkg/PLIST
===
RCS file: /cvs/ports/net/openfire/pkg/PLIST,v
retrieving revision 1.12
diff -u -p -r1.12 PLIST
--- pkg/PLIST 1 Oct 2018 20:08:53 - 1.12
+++ pkg/PLIST 19 Jan 2022 17:47:22 -
@@ -13,20 +13,116 @@ openfire/
@owner
@group
openfire/lib/
-openfire/lib/bcpg-jdk15on.jar
-openfire/lib/bcpkix-jdk15on.jar
-openfire/lib/bcprov-jdk15on.jar
-openfire/lib/hsqldb.jar
-openfire/lib/javax.websocket-api.jar
-openfire/lib/jtds.jar
-openfire/lib/log4j.xml
-openfire/lib/mail.jar
-openfire/lib/mysql.jar
-openfire/lib/npn-boot.jar
-openfire/lib/openfire.jar
-openfire/lib/postgres.jar
-openfire/lib/slf4j-log4j12.jar
+openfire/lib/FastInfoset-1.2.16.jar
+openfire/lib/activation-1.1.jar
+openfire/lib/ant-1.10.9.jar
+openfire/lib/ant-launcher-1.10.9.jar
+openfire/lib/apache-el-8.5.54.jar
+openfire/lib/apache-jsp-8.5.54.jar
+openfire/lib/apache-jsp-9.4.35.v20201120.jar
+openfire/lib/asm-
Re: [sparc64] Change COMPILER line of www/webkitgtk4
On Wed, Jan 19, 2022 at 05:47:46PM +, Stuart Henderson wrote: > > # gcc>=5.0.0 or clang > > -COMPILER = base-clang ports-clang ports-gcc > > +COMPILER = base-clang ports-gcc ports-clang > Better just remove ports-clang I think. Yeah. I thought of adding a line about "or just drop ports-clang". Is it worth dropping the comment too? --Kurt > > MODRUBY_RUNDEP = No > > MODPY_RUNDEP = No > >
Re: [sparc64] Change COMPILER line of www/webkitgtk4
On 2022/01/19 12:43, Kurt Mosiejczuk wrote: > The current issues with ports-clang on sparc64 pointed out something that > should change for webkitgtk4. > > The COMPILER line currently is "base-clang ports-clang ports-gcc". This was > apparently done back before ports-gcc was its current 8.x version. There's > no real reason now for it and it keeps sparc64 from building it while the > clang/llvm problems persists for sparc64. > > ok to change it? > > (cc maintainer) > > --Kurt > > Index: Makefile > === > RCS file: /cvs/ports/www/webkitgtk4/Makefile,v > retrieving revision 1.159 > diff -u -p -r1.159 Makefile > --- Makefile 21 Dec 2021 15:08:08 - 1.159 > +++ Makefile 19 Jan 2022 17:40:32 - > @@ -52,7 +52,7 @@ MODULES = devel/cmake \ > x11/gnome > > # gcc>=5.0.0 or clang > -COMPILER = base-clang ports-clang ports-gcc > +COMPILER = base-clang ports-gcc ports-clang Better just remove ports-clang I think. > MODRUBY_RUNDEP = No > MODPY_RUNDEP = No >
[sparc64] Change COMPILER line of www/webkitgtk4
The current issues with ports-clang on sparc64 pointed out something that should change for webkitgtk4. The COMPILER line currently is "base-clang ports-clang ports-gcc". This was apparently done back before ports-gcc was its current 8.x version. There's no real reason now for it and it keeps sparc64 from building it while the clang/llvm problems persists for sparc64. ok to change it? (cc maintainer) --Kurt Index: Makefile === RCS file: /cvs/ports/www/webkitgtk4/Makefile,v retrieving revision 1.159 diff -u -p -r1.159 Makefile --- Makefile21 Dec 2021 15:08:08 - 1.159 +++ Makefile19 Jan 2022 17:40:32 - @@ -52,7 +52,7 @@ MODULES = devel/cmake \ x11/gnome # gcc>=5.0.0 or clang -COMPILER = base-clang ports-clang ports-gcc +COMPILER = base-clang ports-gcc ports-clang MODRUBY_RUNDEP = No MODPY_RUNDEP = No
qtwebengine dependency on x11/gtk+3,-cups
Hi. Is there any reason why x11/qt5/qtwebengine RUN_DEPENDS on x11/gtk+3,-cups? Should we remove it? Index: Makefile === RCS file: /cvs/ports/x11/qt5/qtwebengine/Makefile,v retrieving revision 1.22 diff -u -p -r1.22 Makefile --- Makefile10 Sep 2021 05:35:58 - 1.22 +++ Makefile19 Jan 2022 15:15:25 - @@ -14,7 +14,7 @@ COMMENT = Chromium-based web engine for # Many parts are copied from www/chromium port, so keep in sync QT5NAME = QtWebEngine -REVISION = 4 +REVISION = 5 CATEGORIES = www @@ -49,7 +49,6 @@ RUN_DEPENDS = devel/desktop-file-utils \ devel/xdg-utils \ fonts/noto/fonts \ graphics/libexif \ - x11/gtk+3,-cups \ x11/gtk+3,-guic BUILD_DEPENDS =archivers/bzip2 \ -- Antoine
Re: [UPDATE] audio/ncspot 0.9.5
On Wed, Jan 19, 2022 at 02:07:20PM +0100, Theo Buehler wrote:
> On Wed, Jan 19, 2022 at 01:00:24PM +, Klemens Nanni wrote:
> > On Wed, Jan 19, 2022 at 12:51:31PM +0100, Henrik Friedrichsen wrote:
> > > On Wed, Jan 19, 2022 at 11:19:48AM +, Klemens Nanni wrote:
> > > > It fails to build on amd64 for me:
> > > > error: there is no argument named `content_len`
> > > > --> src/ui/listview.rs:88:34
> > > >|
> > > > 88 | log::info!("content len: {content_len}");
> > > >| ^
> > > >
> > > > error: there is no argument named `loaded`
> > > >--> src/ui/listview.rs:100:35
> > > > |
> > > > 100 | log::info!("can paginate: {loaded}");
> > > > |
> > > >
> > >
> > > Yes, it needs rust-1.58.0 to build.
> >
> > Thanks, that works.
> >
> > Is this expected?
>
> Yes. It's using captured identifiers, a feature that stabilized with 1.58.
>
> > Does that concern ncspot alone or other rust ports as well?
>
> This is part of the ncspot source. Other ports will likely start using
> this feature. Unless you backport to stable this shouldn't be a concern.
> rust's short support cycle makes backports to stable hard anyway.
Thanks for the insights.
> > Do we just expect (package bulk) machines to always build with the
> > latest version or does that warrant some kind of version pinning for
> > lang/rust?
>
> Yes, a bulk build will build the latest rust in tree and use it.
Yes, that I know, just wanted to know if this is considered good enough.
> I see no reason for pinning.
I guess it is, but figured asking doesn't hurt.
I'll commit the ncspot update, thanks Henrik!
Re: [UPDATE] audio/ncspot 0.9.5
On Wed, Jan 19, 2022 at 01:00:24PM +, Klemens Nanni wrote:
> On Wed, Jan 19, 2022 at 12:51:31PM +0100, Henrik Friedrichsen wrote:
> > On Wed, Jan 19, 2022 at 11:19:48AM +, Klemens Nanni wrote:
> > > It fails to build on amd64 for me:
> > > error: there is no argument named `content_len`
> > > --> src/ui/listview.rs:88:34
> > >|
> > > 88 | log::info!("content len: {content_len}");
> > >| ^
> > >
> > > error: there is no argument named `loaded`
> > >--> src/ui/listview.rs:100:35
> > > |
> > > 100 | log::info!("can paginate: {loaded}");
> > > |
> > >
> >
> > Yes, it needs rust-1.58.0 to build.
>
> Thanks, that works.
>
> Is this expected?
Yes. It's using captured identifiers, a feature that stabilized with 1.58.
> Does that concern ncspot alone or other rust ports as well?
This is part of the ncspot source. Other ports will likely start using
this feature. Unless you backport to stable this shouldn't be a concern.
rust's short support cycle makes backports to stable hard anyway.
> Do we just expect (package bulk) machines to always build with the
> latest version or does that warrant some kind of version pinning for
> lang/rust?
Yes, a bulk build will build the latest rust in tree and use it.
I see no reason for pinning.
Re: [UPDATE] audio/ncspot 0.9.5
On Wed, Jan 19, 2022 at 12:51:31PM +0100, Henrik Friedrichsen wrote:
> On Wed, Jan 19, 2022 at 11:19:48AM +, Klemens Nanni wrote:
> > It fails to build on amd64 for me:
> > error: there is no argument named `content_len`
> > --> src/ui/listview.rs:88:34
> >|
> > 88 | log::info!("content len: {content_len}");
> >| ^
> >
> > error: there is no argument named `loaded`
> >--> src/ui/listview.rs:100:35
> > |
> > 100 | log::info!("can paginate: {loaded}");
> > |
> >
>
> Yes, it needs rust-1.58.0 to build.
Thanks, that works.
Is this expected?
Does that concern ncspot alone or other rust ports as well?
Do we just expect (package bulk) machines to always build with the
latest version or does that warrant some kind of version pinning for
lang/rust?
Re: [UPDATE] audio/ncspot 0.9.5
On Wed, Jan 19, 2022 at 11:19:48AM +, Klemens Nanni wrote:
> It fails to build on amd64 for me:
> error: there is no argument named `content_len`
> --> src/ui/listview.rs:88:34
>|
> 88 | log::info!("content len: {content_len}");
>| ^
>
> error: there is no argument named `loaded`
>--> src/ui/listview.rs:100:35
> |
> 100 | log::info!("can paginate: {loaded}");
> |
>
Yes, it needs rust-1.58.0 to build.
Re: [UPDATE] audio/ncspot 0.9.5
On Wed, Jan 19, 2022 at 11:19:48AM +, Klemens Nanni wrote:
> It fails to build on amd64 for me:
[...]
> error: there is no argument named `content_len`
> --> src/ui/listview.rs:88:34
>|
> 88 | log::info!("content len: {content_len}");
>| ^
I haven't tried, but make sure you have rust-1.58.0 installed.
Re: [UPDATE] audio/ncspot 0.9.5
On Wed, Jan 19, 2022 at 12:01:26PM +0100, Henrik Friedrichsen wrote:
> Updates ncspot to 0.9.5
>
> Mostly bugfixes:
>
> - Fix release build name and win32 feature (#691)
> - seek spits out correct error when used with no args (#695)
> - Migrate to cursive 0.17
> - Remove notifications' dependency on cover (#706)
> - Fix errors showing up even though the command was successful (#710) (#711)
> - Fix lists that were shown as empty even though they contained items
>
> Tested on amd64. OK?
It fails to build on amd64 for me:
Running `/usr/local/bin/rustc --crate-name ncspot --edition=2021
src/main.rs --error-format=json --json=diagnostic-rendered-ansi --crate-type
bin --emit=dep-info,link -C opt-level=2 -C embed-bitcode=no -C codegen-units=4
-C debuginfo=0 --cfg 'feature="dbus"' --cfg 'feature="dbus-tree"' --cfg
'feature="mpris"' --cfg 'feature="portaudio_backend"' -C
metadata=9f033a4919bec4f2 -C extra-filename=-9f033a4919bec4f2 --out-dir
/usr/ports/pobj/ncspot-0.9.5/build-amd64/target/release/deps -L
dependency=/usr/ports/pobj/ncspot-0.9.5/build-amd64/target/release/deps
--extern
chrono=/usr/ports/pobj/ncspot-0.9.5/build-amd64/target/release/deps/libchrono-ad5313d4ad71786b.rlib
--extern
clap=/usr/ports/pobj/ncspot-0.9.5/build-amd64/target/release/deps/libclap-091b89a75ce9ba06.rlib
--extern
crossbeam_channel=/usr/ports/pobj/ncspot-0.9.5/build-amd64/target/release/deps/libcrossbeam_channel-6e97d01fe62e6977.rlib
--extern
cursive=/usr/ports/pobj/ncspot-0.9.5/build-amd64/target/release/deps/libcursive-294c16552a43c571.rlib
--extern
dbus=/usr/ports/pobj/ncspot-0.9.5/build-amd64/target/release/deps/libdbus-35ff6678aa2f7d2a.rlib
--extern
dbus_tree=/usr/ports/pobj/ncspot-0.9.5/build-amd64/target/release/deps/libdbus_tree-bf511f1ebfc9a1f1.rlib
--extern
fern=/usr/ports/pobj/ncspot-0.9.5/build-amd64/target/release/deps/libfern-fc708e8ad02bb014.rlib
--extern
futures=/usr/ports/pobj/ncspot-0.9.5/build-amd64/target/release/deps/libfutures-d07c8a1aac34139f.rlib
--extern
lazy_static=/usr/ports/pobj/ncspot-0.9.5/build-amd64/target/release/deps/liblazy_static-05fff603cbff1b7e.rlib
--extern
libc=/usr/ports/pobj/ncspot-0.9.5/build-amd64/target/release/deps/liblibc-6624ab485e53b816.rlib
--extern
librespot_core=/usr/ports/pobj/ncspot-0.9.5/build-amd64/target/release/deps/liblibrespot_core-7a7c42bf2614716b.rlib
--extern
librespot_playback=/usr/ports/pobj/ncspot-0.9.5/build-amd64/target/release/deps/liblibrespot_playback-c6144e58896b6fd7.rlib
--extern
librespot_protocol=/usr/ports/pobj/ncspot-0.9.5/build-amd64/target/release/deps/liblibrespot_protocol-009f3565b2e6c490.rlib
--extern
log=/usr/ports/pobj/ncspot-0.9.5/build-amd64/target/release/deps/liblog-10b2530931765274.rlib
--extern
parse_duration=/usr/ports/pobj/ncspot-0.9.5/build-amd64/target/release/deps/libparse_duration-04971d6915afbb74.rlib
--extern
platform_dirs=/usr/ports/pobj/ncspot-0.9.5/build-amd64/target/release/deps/libplatform_dirs-d3f47fc89df41752.rlib
--extern
rand=/usr/ports/pobj/ncspot-0.9.5/build-amd64/target/release/deps/librand-76ac90b113c7ba8c.rlib
--extern
regex=/usr/ports/pobj/ncspot-0.9.5/build-amd64/target/release/deps/libregex-ad16777c9dfb92a4.rlib
--extern
reqwest=/usr/ports/pobj/ncspot-0.9.5/build-amd64/target/release/deps/libreqwest-f9451315c21dd8e0.rlib
--extern
rspotify=/usr/ports/pobj/ncspot-0.9.5/build-amd64/target/release/deps/librspotify-ac58927b1c862a99.rlib
--extern
serde=/usr/ports/pobj/ncspot-0.9.5/build-amd64/target/release/deps/libserde-4721bcb55a44d5b8.rlib
--extern
serde_cbor=/usr/ports/pobj/ncspot-0.9.5/build-amd64/target/release/deps/libserde_cbor-1077c87430bf4d4c.rlib
--extern
serde_json=/usr/ports/pobj/ncspot-0.9.5/build-amd64/target/release/deps/libserde_json-325472ff449c5bb5.rlib
--extern
strum=/usr/ports/pobj/ncspot-0.9.5/build-amd64/target/release/deps/libstrum-35963c066110b9fc.rlib
--extern
strum_macros=/usr/ports/pobj/ncspot-0.9.5/build-amd64/target/release/deps/libstrum_macros-3c4aa6eeb57719a8.so
--extern
tokio=/usr/ports/pobj/ncspot-0.9.5/build-amd64/target/release/deps/libtokio-e291c7bc3d31aab3.rlib
--extern
tokio_stream=/usr/ports/pobj/ncspot-0.9.5/build-amd64/target/release/deps/libtokio_stream-127e38979050da46.rlib
--extern
toml=/usr/ports/pobj/ncspot-0.9.5/build-amd64/target/release/deps/libtoml-1298cc47f6663f5e.rlib
--extern
unicode_width=/usr/ports/pobj/ncspot-0.9.5/build-amd64/target/release/deps/libunicode_width-d9447b37ae2e483d.rlib
--extern
url=/usr/ports/pobj/ncspot-0.9.5/build-amd64/target/release/deps/liburl-e88142197bd42b65.rlib
--extern
webbrowser=/usr/ports/pobj/ncspot-0.9.5/build-amd64/target/release/deps/libwebbrowser-28b80e3f5ed29823.rlib
-L native=/usr/local/lib -L native=/usr/local/lib -L
native=/usr/ports/pobj/ncspot-0.9.5/build-amd64/target/release/build/ring-256350a07d268534/out`
error: there is no argument named `content_len`
--> src/ui/listview.rs:88:34
|
88 | log::info!("content len: {content_len}");
|
Re: rox-filer on -current has been slow for a week or so.
On 2022/01/18 19:23, Ed Ahlsen-Girard wrote: > Been running amd64 -current for several years, and over the last week > the response time of rox-filer has been massively longer than before > (about 10 or 15 times as long). > > The rate of snapshot release has been very high lately. Is something > going on with rox? First thing to try is a self-built kernel to check if it's some uncommitted diff being tested in snapshots. If that doesn't change anything then go back to older kernel code, leaving userland alone. I would do a kernel build with a date-based cvs checkout to see this (e.g. cvs up -D 2022/01/10). Basically try to narrow down what area was changed that caused it to slow down. > dmesg below the signature. > > -- > > Edward Ahlsen-Girard > Ft Walton Beach, FL > > > OpenBSD 7.0-current (GENERIC.MP) #262: Mon Jan 17 10:57:07 MST 2022 > dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP > real mem = 4176125952 (3982MB) > avail mem = 4032364544 (3845MB) > random: good seed from bootblocks > mpath0 at root > scsibus0 at mpath0: 256 targets > mainbus0 at root > bios0 at mainbus0: SMBIOS rev. 2.8 @ 0xec530 (36 entries) > bios0: vendor AMI version "80.06" date 04/01/2015 > bios0: Hewlett-Packard 550-036 > acpi0 at bios0: ACPI 5.0 > acpi0: sleep states S0 S3 S4 S5 > acpi0: tables DSDT FACP APIC FPDT FIDT MSDM SSDT SSDT MCFG HPET SSDT SSDT DBGP > acpi0: wakeup devices RP01(S4) PXSX(S4) PXSX(S4) PXSX(S4) RP04(S4) PXSX(S4) > PXSX(S4) RP06(S4) PXSX(S4) RP07(S4) PXSX(S4) PXSX(S4) GLAN(S4) EHC1(S3) > EHC2(S3) XHC_(S3) [...] > acpitimer0 at acpi0: 3579545 Hz, 24 bits > acpimadt0 at acpi0 addr 0xfee0: PC-AT compat > cpu0 at mainbus0: apid 0 (boot processor) > cpu0: Intel(R) Core(TM) i3-4170 CPU @ 3.70GHz, 3692.01 MHz, 06-3c-03 > cpu0: > FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,EST,TM2,SSSE3,SDBG,FMA3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,RDTSCP,LONG,LAHF,ABM,PERF,ITSC,FSGSBASE,TSC_ADJUST,BMI1,AVX2,SMEP,BMI2,ERMS,INVPCID,SRBDS_CTRL,MD_CLEAR,IBRS,IBPB,STIBP,L1DF,SSBD,SENSOR,ARAT,XSAVEOPT,MELTDOWN > cpu0: 256KB 64b/line 8-way L2 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.2.4, IBE > cpu1 at mainbus0: apid 2 (application processor) > cpu1: Intel(R) Core(TM) i3-4170 CPU @ 3.70GHz, 3691.48 MHz, 06-3c-03 > cpu1: > FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,EST,TM2,SSSE3,SDBG,FMA3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,RDTSCP,LONG,LAHF,ABM,PERF,ITSC,FSGSBASE,TSC_ADJUST,BMI1,AVX2,SMEP,BMI2,ERMS,INVPCID,SRBDS_CTRL,MD_CLEAR,IBRS,IBPB,STIBP,L1DF,SSBD,SENSOR,ARAT,XSAVEOPT,MELTDOWN > cpu1: 256KB 64b/line 8-way L2 cache > cpu1: smt 0, core 1, package 0 > cpu2 at mainbus0: apid 1 (application processor) > cpu2: Intel(R) Core(TM) i3-4170 CPU @ 3.70GHz, 3691.47 MHz, 06-3c-03 > cpu2: > FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,EST,TM2,SSSE3,SDBG,FMA3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,RDTSCP,LONG,LAHF,ABM,PERF,ITSC,FSGSBASE,TSC_ADJUST,BMI1,AVX2,SMEP,BMI2,ERMS,INVPCID,SRBDS_CTRL,MD_CLEAR,IBRS,IBPB,STIBP,L1DF,SSBD,SENSOR,ARAT,XSAVEOPT,MELTDOWN > cpu2: 256KB 64b/line 8-way L2 cache > cpu2: smt 1, core 0, package 0 > cpu3 at mainbus0: apid 3 (application processor) > cpu3: Intel(R) Core(TM) i3-4170 CPU @ 3.70GHz, 3691.47 MHz, 06-3c-03 > cpu3: > FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,EST,TM2,SSSE3,SDBG,FMA3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,RDTSCP,LONG,LAHF,ABM,PERF,ITSC,FSGSBASE,TSC_ADJUST,BMI1,AVX2,SMEP,BMI2,ERMS,INVPCID,SRBDS_CTRL,MD_CLEAR,IBRS,IBPB,STIBP,L1DF,SSBD,SENSOR,ARAT,XSAVEOPT,MELTDOWN > cpu3: 256KB 64b/line 8-way L2 cache > cpu3: smt 1, core 1, package 0 > ioapic0 at mainbus0: apid 8 pa 0xfec0, version 20, 24 pins > acpimcfg0 at acpi0 > acpimcfg0: addr 0xf800, bus 0-63 > acpihpet0 at acpi0: 14318179 Hz > acpiprt0 at acpi0: bus 0 (PCI0) > acpiprt1 at acpi0: bus 1 (RP01) > acpiprt2 at acpi0: bus 2 (RP04) > acpiprt3 at acpi0: bus 3 (RP06) > acpiprt4 at acpi0: bus 4 (RP07) > acpiprt5 at acpi0: bus -1 (PEG0) > acpiec0 at acpi0: not present > acpipci0 at acpi0 PCI0: 0x 0x0011 0x0001 > acpicmos0 at acpi0 > acpibtn0 at acpi0: PWRB > "PNP0C14" at acpi0 not configured > "PNP0C0B" at acpi0 not configured > "PNP0C0B" at acpi0 not configured > "PNP0C0B" at acpi0
[UPDATE] audio/ncspot 0.9.5
Updates ncspot to 0.9.5 Mostly bugfixes: - Fix release build name and win32 feature (#691) - seek spits out correct error when used with no args (#695) - Migrate to cursive 0.17 - Remove notifications' dependency on cover (#706) - Fix errors showing up even though the command was successful (#710) (#711) - Fix lists that were shown as empty even though they contained items Tested on amd64. OK?? lic Index: Makefile === RCS file: /cvs/ports/audio/ncspot/Makefile,v retrieving revision 1.24 diff -u -p -r1.24 Makefile --- Makefile18 Jan 2022 18:43:37 - 1.24 +++ Makefile19 Jan 2022 11:00:01 - @@ -8,7 +8,7 @@ COMMENT = ncurses Spotify client GH_ACCOUNT = hrkfdn GH_PROJECT = ncspot -GH_TAGNAME = v0.9.4 +GH_TAGNAME = v0.9.5 CATEGORIES = audio Index: crates.inc === RCS file: /cvs/ports/audio/ncspot/crates.inc,v retrieving revision 1.5 diff -u -p -r1.5 crates.inc --- crates.inc 2 Jan 2022 07:12:48 - 1.5 +++ crates.inc 19 Jan 2022 11:00:01 - @@ -5,12 +5,11 @@ MODCARGO_CRATES +=aes 0.6.0 # MIT OR Ap MODCARGO_CRATES += aes-ctr 0.6.0 # MIT OR Apache-2.0 MODCARGO_CRATES += aes-soft0.6.4 # MIT OR Apache-2.0 MODCARGO_CRATES += aesni 0.10.0 # MIT OR Apache-2.0 -MODCARGO_CRATES += ahash 0.6.3 # MIT OR Apache-2.0 +MODCARGO_CRATES += ahash 0.7.6 # MIT OR Apache-2.0 MODCARGO_CRATES += aho-corasick0.7.18 # Unlicense/MIT MODCARGO_CRATES += alsa0.5.0 # Apache-2.0/MIT MODCARGO_CRATES += alsa-sys0.3.1 # MIT MODCARGO_CRATES += ansi_term 0.12.1 # MIT -MODCARGO_CRATES += array-macro 1.0.5 # MIT/Apache-2.0 MODCARGO_CRATES += arrayref0.3.6 # BSD-2-Clause MODCARGO_CRATES += arrayvec0.5.2 # MIT/Apache-2.0 MODCARGO_CRATES += async-io1.6.0 # Apache-2.0 OR MIT @@ -25,7 +24,7 @@ MODCARGO_CRATES +=bitflags1.3.2 # MIT/ MODCARGO_CRATES += blake2b_simd0.5.11 # MIT MODCARGO_CRATES += block 0.1.6 # MIT MODCARGO_CRATES += block-buffer0.9.0 # MIT OR Apache-2.0 -MODCARGO_CRATES += bumpalo 3.8.0 # MIT/Apache-2.0 +MODCARGO_CRATES += bumpalo 3.9.1 # MIT/Apache-2.0 MODCARGO_CRATES += byteorder 1.4.3 # Unlicense OR MIT MODCARGO_CRATES += bytes 1.1.0 # MIT MODCARGO_CRATES += cache-padded1.2.0 # Apache-2.0 OR MIT @@ -39,13 +38,13 @@ MODCARGO_CRATES += chunked_transfer1.4. MODCARGO_CRATES += cipher 0.2.5 # MIT OR Apache-2.0 MODCARGO_CRATES += clang-sys 1.3.0 # Apache-2.0 MODCARGO_CRATES += clap2.34.0 # MIT -MODCARGO_CRATES += clap3.0.0 # MIT OR Apache-2.0 +MODCARGO_CRATES += clap3.0.10 # MIT OR Apache-2.0 MODCARGO_CRATES += clipboard 0.5.0 # MIT / Apache-2.0 MODCARGO_CRATES += clipboard-win 2.2.0 # MIT MODCARGO_CRATES += cloudabi0.0.3 # BSD-2-Clause -MODCARGO_CRATES += combine 4.6.2 # MIT +MODCARGO_CRATES += combine 4.6.3 # MIT MODCARGO_CRATES += concurrent-queue1.2.2 # Apache-2.0 OR MIT -MODCARGO_CRATES += const_fn0.4.8 # Apache-2.0 OR MIT +MODCARGO_CRATES += const_fn0.4.9 # Apache-2.0 OR MIT MODCARGO_CRATES += constant_time_eq0.1.5 # CC0-1.0 MODCARGO_CRATES += convert_case0.4.0 # MIT MODCARGO_CRATES += cookie 0.15.1 # MIT OR Apache-2.0 @@ -56,15 +55,18 @@ MODCARGO_CRATES += coreaudio-rs0.10.0 # MODCARGO_CRATES += coreaudio-sys 0.2.8 # MIT MODCARGO_CRATES += cpal0.13.4 # Apache-2.0 MODCARGO_CRATES += cpufeatures 0.2.1 # MIT OR Apache-2.0 -MODCARGO_CRATES += crossbeam-channel 0.5.1 # MIT OR Apache-2.0 -MODCARGO_CRATES += crossbeam-utils 0.8.5 # MIT OR Apache-2.0 +MODCARGO_CRATES += crossbeam-channel 0.5.2 # MIT OR Apache-2.0 +MODCARGO_CRATES += crossbeam-utils 0.8.6 # MIT OR Apache-2.0 MODCARGO_CRATES += crypto-mac 0.11.1 # MIT OR Apache-2.0 MODCARGO_CRATES += ctr 0.6.0 # MIT OR Apache-2.0 -MODCARGO_CRATES += cursive 0.16.3 # MIT -MODCARGO_CRATES += cursive_core0.2.2 # MIT +MODCARGO_CRATES += cursive 0.17.0 # MIT +MODCARGO_CRATES += cursive_core0.3.1 # MIT MODCARGO_CRATES += darling 0.10.2 # MIT +MODCARGO_CRATES += darling 0.13.1 # MIT MODCARGO_CRATES += darling_core0.10.2 # MIT +MODCARGO_CRATES += darling_core0.13.1 # MIT MODCARGO_CRATES += darling_macro 0.10.2 # MIT +MODCARGO_CRATES += darling_macro 0.13.1 # MIT MODCARGO_CRATES += dbus0.9.5 # Apache-2.0/MIT MODCARGO_CRATES += dbus-tree 0.9.2 # Apache-2.0/MIT MODCARGO_CRATES += derivative 2.2.0 # MIT/Apache-2.0 @@ -77,10 +79,12 @@ MODCARGO_CRATES +=
