Re: [MAINTAINER UPDATE] www/honk 0.9.7 -> 0.9.8

[Christoph Roland Winter]

Hy,

> Am 23.09.2022 um 20:24 schrieb Horia Racoviceanu :
> 
> Thank you for the MESSAGE and README change.

But continue your good work.
We should try to get your informations upstream to tedu.

> I confirm that the backup/upgrade must be done *after* updating the package.
> v0.9.8 is required to upgrade the old database.

Yes, I can also confirm that. Everything worked as I did the upgrade from 0.9.7 
to 0.9.8 some weeks ago.
BTW is there a option to stop a already running Honk in case of a DB upgrade. 
Maybe I think to complicated but what is, if there is a running Honk and 
someone tries to launch the new one (just to prevent that the DB get broken - 
we know, that many people do no backups … don’t look at me ;-) ). 

> 
> On 9/23/22, Stuart Henderson  wrote:
>> On 2022/09/23 12:27, Horia Racoviceanu wrote:
>>> Index: pkg/MESSAGE
>>> ===
>>> RCS file: pkg/MESSAGE
>>> diff -N pkg/MESSAGE
>>> --- /dev/null   1 Jan 1970 00:00:00 -
>>> +++ pkg/MESSAGE 23 Sep 2022 16:17:47 -
>>> @@ -0,0 +1,15 @@
>>> +The database has changed since version 0.9.7
>>> +
>>> +Stop the old honk process.
>>> +honk# rcctl stop honk
>>> +
>>> +Backup the database.
>>> +honk# doas -su _honk
>>> +honk$ umask 077; cd ${LOCALSTATEDIR}/honk && honk backup `date
>>> +backup-%F`
>>> +
>>> +Perform the upgrade with the upgrade command.
>>> +honk$ honk upgrade
>>> +honk$ exit
>>> +
>>> +Restart.
>>> +honk# rcctl start honk
>> 
>> This is too long for MESSAGE, we don't want pages of information
>> scrolling after pkg_add. I suggest a single line and add the main
>> bit to pkg-readme as below.
>> 
>> I don't use this software. Can you confirm that the backup/upgrade
>> steps are OK to do *after* updating the package, or do users need to
>> do something *before* updating?
>> 
>> If it's before, then the information will need to go in upgrade
>> docs (via faq/current.html) instead because they won't see this message
>> until after they've updated packages.
>> 
>> 
>> Index: Makefile
>> ===
>> RCS file: /cvs/ports/www/honk/Makefile,v
>> retrieving revision 1.19
>> diff -u -p -r1.19 Makefile
>> --- Makefile 11 Mar 2022 20:09:55 -  1.19
>> +++ Makefile 23 Sep 2022 16:35:04 -
>> @@ -1,6 +1,6 @@
>> COMMENT =federated status conveyance
>> 
>> -DISTNAME =  honk-0.9.7
>> +DISTNAME =  honk-0.9.8
>> CATEGORIES = www
>> 
>> HOMEPAGE =   https://humungus.tedunangst.com/r/honk
>> @@ -13,6 +13,8 @@ PERMIT_PACKAGE =   Yes
>> WANTLIB +=   c pthread sqlite3
>> 
>> MASTER_SITES =   ${HOMEPAGE}/d/
>> +DISTFILES = ${EXTRACT_ONLY} honk-{../v/tip/d/views/}icon.png
>> +EXTRACT_ONLY =  ${DISTNAME}${EXTRACT_SUFX}
>> EXTRACT_SUFX =   .tgz
>> 
>> MODULES =lang/go
>> @@ -21,8 +23,7 @@ LIB_DEPENDS =  databases/sqlite3
>> NO_TEST =Yes
>> ALL_TARGET = humungus.tedunangst.com/r/honk
>> 
>> -SUBST_VARS +=   VARBASE \
>> -SYSCONFDIR
>> +SUBST_VARS +=   SYSCONFDIR
>> 
>> DOCDIR ?=${PREFIX}/share/doc/honk
>> EXAMPLESDIR =${PREFIX}/share/examples/honk
>> @@ -53,5 +54,7 @@ post-install:
>>  ${EXAMPLESDIR}/views/
>>  ${INSTALL_DATA} ${MODGO_WORKSPACE}/src/${ALL_TARGET}/schema.sql \
>>  ${EXAMPLESDIR}/
>> +${INSTALL_DATA} ${DISTDIR}/honk-icon.png 
>> ${EXAMPLESDIR}/views/favicon.ico
>> +${INSTALL_DATA} ${DISTDIR}/honk-icon.png ${EXAMPLESDIR}/views/icon.png
>> 
>> .include 
>> Index: distinfo
>> ===
>> RCS file: /cvs/ports/www/honk/distinfo,v
>> retrieving revision 1.11
>> diff -u -p -r1.11 distinfo
>> --- distinfo 2 Mar 2022 07:31:01 -   1.11
>> +++ distinfo 23 Sep 2022 16:35:04 -
>> @@ -1,2 +1,4 @@
>> -SHA256 (honk-0.9.7.tgz) = t6EM5E98qvlnq6Y6vd21MvPBrWpkmo4qXdgNEUAeF7M=
>> -SIZE (honk-0.9.7.tgz) = 522993
>> +SHA256 (honk-0.9.8.tgz) = BmZgMvN7fFrft+W0+V2j3tezI5kRLl/7Fx5wIVXwCG4=
>> +SHA256 (honk-icon.png) = 92RJuF2onJ/1OYs4E4TYDm9KbzmNKISl+1+MSdhpzUQ=
>> +SIZE (honk-0.9.8.tgz) = 511957
>> +SIZE (honk-icon.png) = 912
>> Index: pkg/MESSAGE
>> ===
>> RCS file: pkg/MESSAGE
>> diff -N pkg/MESSAGE
>> --- /dev/null1 Jan 1970 00:00:00 -
>> +++ pkg/MESSAGE  23 Sep 2022 16:35:04 -
>> @@ -0,0 +1 @@
>> +The database has changed since version 0.9.7. See the pkg-readme.
>> Index: pkg/PLIST
>> ===
>> RCS file: /cvs/ports/www/honk/pkg/PLIST,v
>> retrieving revision 1.9
>> diff -u -p -r1.9 PLIST
>> --- pkg/PLIST11 Mar 2022 20:09:55 -  1.9
>> +++ pkg/PLIST23 Sep 2022 16:35:04 -
>> @@ -1,5 +1,5 @@
>> @newgroup _honk:833
>> -@newuser 

Re: [MAINTAINER UPDATE] www/honk 0.9.7 -> 0.9.8

[Christoph Roland Winter]

BTW what you think about a section in the FAQ about httpd, relayd, 
acme-client for all web applications.


Am 31.07.22 um 13:12 schrieb Stuart Henderson:

1. The staple needs to be updated periodically

2. If the certificate is updated the staple needs to be updated too

3. If either the certificate or the staple are changed, relayd needs a 
reload


To be honest I'm not sure if it really belongs in the doc for some 
random port in www, this applies to anyone using relayd to front-end a 
web application.


--
   Sent from a phone, apologies for poor formatting.


On 31 July 2022 02:16:13 Christoph Roland Winter  wrote:


Beside of this question, the idea of OCSP is

By turning on OCSP Stapling, you can improve the performance of your
website, provide better privacy protections for your users, and help
Let’s Encrypt efficiently serve as many people as possible.

https://letsencrypt.org/docs/integration-guide/

Is it better to update the OCSP file before it expires or update it only
seldom (in this case the question is, whether it is not better to don't
use OCSP).

Am 31.07.22 um 00:33 schrieb Horia Racoviceanu:
I've switched the cron job to chaining acme-client && ocspcheck on 
June 20.

Both the certificate and the OCSP response were last updated on June 20.

# ocspcheck -vNi /etc/ssl/honk.example.com.{ocsp,crt}
ocspcheck: Invalid OCSP reply: this update is too old Mon Jun 20 
05:46:59 2022


relayd and Firefox do not complain.

ssllabs.com reports:

OCSP Must Staple No
OCSP stapling  Yes
OCSP STAPLING ERROR: OCSP response expired on Mon Jun 20 20:46:59 UTC 
2022


Can the OCSP STAPLING ERROR be ignored?

On 7/30/22, Christoph Roland Winter  wrote:

Welcome.

The question is then, why the OCSP staple file expires after hours or 7
days and the certificate will be renewed after 60 days following man 1
acme-client

-F      Force certificate renewal, even if it has more than 30 days
        validity.

It can't be the idea to have so long a expired OCSP file (saw Firefox in
the past complain when a outdated OCSP file exists). So, if you replace
the first && with a ; nothing will change as the last && to reload
relayd will only happen if the cert or the OCSP file (or both) was
renewed and if booth are up to date nothing will happen.

Just my 2 cents.

Regards,


Christoph

Am 30.07.22 um 19:07 schrieb Horia Racoviceanu:

Thanks for testing!

As Stuart Henderson mentioned,

You do really want to update OCSP if a cert has been renewed.


On 7/29/22, Christoph Roland Winter  wrote:

Hello,

I have only kept the first message and was some time not subscribed to
the list - lets see, where the message ends.

I tried the latest patch from
https://marc.info/?l=openbsd-ports=165827470732358=p3 and it 
worked

fine using

OpenBSD 7.2-beta (GENERIC.MP) #654: Wed Jul 27 20:10:05 MDT 2022 
and the

-current ports tree using amd64.

Maybe I am wrong but the crontab from the above patch

+~ ~ * * * acme-client honk.example.com && ocspcheck -No
${SYSCONFDIR}/ssl/honk.example.com.{ocsp,crt} && rcctl reload relayd

needs to be modified. The first && must be replaced with ; (or splited
in 2 cron jobs). As it is now, the ocsp file gets only renewed all 60
days, as acme-client renews the certificate only 30 days before it
expires (checked with the -v option and as nothing happened before, &&
stops at this point). BTW my ocsp file with the above command is valid
for 7 days.

ocspcheck -vNo /etc/ssl/the.floof.rocks.{ocsp,crt}
Using http to host r3.o.lencr.org, port 80, path /
OCSP response validated from r3.o.lencr.org
         This Update: Thu Jul 28 15:00:00 2022
         Next Update: Thu Aug  4 14:59:58 2022

The only thing I did was using the /etc/examples/acme-client.conf 
file,

added my email and added the domain blocks.

Regards,


Christoph


Am 01.06.22 um 23:37 schrieb Horia Racoviceanu:

Upgrade to v0.9.8
- Add MESSAGE
- Update README

changelog

=== 0.9.8 Tentative Tentacle

+ Switch database to WAL mode.

- go version 1.16 required.

+ Specify banner: image in profile.

+ Update activity compatibility with mastodon.

- Signed fetch.

+ Better unicode hashtags.

+ Some more configuration options.

+ Some UI improvements to web interface.

+ Add atme class to mentions

+ Improvements to the mastodon importer.

+ More hydration capable pages.

+ Support for local.js.

+ Better error messages for timeouts.

+ Some improved html and markdown.

Re: [MAINTAINER UPDATE] www/honk 0.9.7 -> 0.9.8

[Christoph Roland Winter]

Beside of this question, the idea of OCSP is

By turning on OCSP Stapling, you can improve the performance of your 
website, provide better privacy protections for your users, and help 
Let’s Encrypt efficiently serve as many people as possible.


https://letsencrypt.org/docs/integration-guide/

Is it better to update the OCSP file before it expires or update it only 
seldom (in this case the question is, whether it is not better to don't 
use OCSP).


Am 31.07.22 um 00:33 schrieb Horia Racoviceanu:

I've switched the cron job to chaining acme-client && ocspcheck on June 20.
Both the certificate and the OCSP response were last updated on June 20.

# ocspcheck -vNi /etc/ssl/honk.example.com.{ocsp,crt}
ocspcheck: Invalid OCSP reply: this update is too old Mon Jun 20 05:46:59 2022

relayd and Firefox do not complain.

ssllabs.com reports:

OCSP Must Staple No
OCSP stapling  Yes
OCSP STAPLING ERROR: OCSP response expired on Mon Jun 20 20:46:59 UTC 2022

Can the OCSP STAPLING ERROR be ignored?

On 7/30/22, Christoph Roland Winter  wrote:

Welcome.

The question is then, why the OCSP staple file expires after hours or 7
days and the certificate will be renewed after 60 days following man 1
acme-client

   -F  Force certificate renewal, even if it has more than 30 days
   validity.

It can't be the idea to have so long a expired OCSP file (saw Firefox in
the past complain when a outdated OCSP file exists). So, if you replace
the first && with a ; nothing will change as the last && to reload
relayd will only happen if the cert or the OCSP file (or both) was
renewed and if booth are up to date nothing will happen.

Just my 2 cents.

Regards,


Christoph

Am 30.07.22 um 19:07 schrieb Horia Racoviceanu:

Thanks for testing!

As Stuart Henderson mentioned,

You do really want to update OCSP if a cert has been renewed.


On 7/29/22, Christoph Roland Winter  wrote:

Hello,

I have only kept the first message and was some time not subscribed to
the list - lets see, where the message ends.

I tried the latest patch from
https://marc.info/?l=openbsd-ports=165827470732358=p3 and it worked
fine using

OpenBSD 7.2-beta (GENERIC.MP) #654: Wed Jul 27 20:10:05 MDT 2022 and the
-current ports tree using amd64.

Maybe I am wrong but the crontab from the above patch

+~ ~ * * * acme-client honk.example.com && ocspcheck -No
${SYSCONFDIR}/ssl/honk.example.com.{ocsp,crt} && rcctl reload relayd

needs to be modified. The first && must be replaced with ; (or splited
in 2 cron jobs). As it is now, the ocsp file gets only renewed all 60
days, as acme-client renews the certificate only 30 days before it
expires (checked with the -v option and as nothing happened before, &&
stops at this point). BTW my ocsp file with the above command is valid
for 7 days.

ocspcheck -vNo /etc/ssl/the.floof.rocks.{ocsp,crt}
Using http to host r3.o.lencr.org, port 80, path /
OCSP response validated from r3.o.lencr.org
  This Update: Thu Jul 28 15:00:00 2022
  Next Update: Thu Aug  4 14:59:58 2022

The only thing I did was using the /etc/examples/acme-client.conf file,
added my email and added the domain blocks.

Regards,


Christoph


Am 01.06.22 um 23:37 schrieb Horia Racoviceanu:

Upgrade to v0.9.8
- Add MESSAGE
- Update README

changelog

=== 0.9.8 Tentative Tentacle

+ Switch database to WAL mode.

- go version 1.16 required.

+ Specify banner: image in profile.

+ Update activity compatibility with mastodon.

- Signed fetch.

+ Better unicode hashtags.

+ Some more configuration options.

+ Some UI improvements to web interface.

+ Add atme class to mentions

+ Improvements to the mastodon importer.

+ More hydration capable pages.

+ Support for local.js.

+ Better error messages for timeouts.

+ Some improved html and markdown.

Re: [MAINTAINER UPDATE] www/honk 0.9.7 -> 0.9.8

[Christoph Roland Winter]

Welcome.

The question is then, why the OCSP staple file expires after hours or 7 
days and the certificate will be renewed after 60 days following man 1 
acme-client


 -F  Force certificate renewal, even if it has more than 30 days
 validity.

It can't be the idea to have so long a expired OCSP file (saw Firefox in 
the past complain when a outdated OCSP file exists). So, if you replace 
the first && with a ; nothing will change as the last && to reload 
relayd will only happen if the cert or the OCSP file (or both) was 
renewed and if booth are up to date nothing will happen.


Just my 2 cents.

Regards,


Christoph

Am 30.07.22 um 19:07 schrieb Horia Racoviceanu:

Thanks for testing!

As Stuart Henderson mentioned,

You do really want to update OCSP if a cert has been renewed.


On 7/29/22, Christoph Roland Winter  wrote:

Hello,

I have only kept the first message and was some time not subscribed to
the list - lets see, where the message ends.

I tried the latest patch from
https://marc.info/?l=openbsd-ports=165827470732358=p3 and it worked
fine using

OpenBSD 7.2-beta (GENERIC.MP) #654: Wed Jul 27 20:10:05 MDT 2022 and the
-current ports tree using amd64.

Maybe I am wrong but the crontab from the above patch

+~ ~ * * * acme-client honk.example.com && ocspcheck -No
${SYSCONFDIR}/ssl/honk.example.com.{ocsp,crt} && rcctl reload relayd

needs to be modified. The first && must be replaced with ; (or splited
in 2 cron jobs). As it is now, the ocsp file gets only renewed all 60
days, as acme-client renews the certificate only 30 days before it
expires (checked with the -v option and as nothing happened before, &&
stops at this point). BTW my ocsp file with the above command is valid
for 7 days.

ocspcheck -vNo /etc/ssl/the.floof.rocks.{ocsp,crt}
Using http to host r3.o.lencr.org, port 80, path /
OCSP response validated from r3.o.lencr.org
 This Update: Thu Jul 28 15:00:00 2022
 Next Update: Thu Aug  4 14:59:58 2022

The only thing I did was using the /etc/examples/acme-client.conf file,
added my email and added the domain blocks.

Regards,


Christoph


Am 01.06.22 um 23:37 schrieb Horia Racoviceanu:

Upgrade to v0.9.8
- Add MESSAGE
- Update README

changelog

=== 0.9.8 Tentative Tentacle

+ Switch database to WAL mode.

- go version 1.16 required.

+ Specify banner: image in profile.

+ Update activity compatibility with mastodon.

- Signed fetch.

+ Better unicode hashtags.

+ Some more configuration options.

+ Some UI improvements to web interface.

+ Add atme class to mentions

+ Improvements to the mastodon importer.

+ More hydration capable pages.

+ Support for local.js.

+ Better error messages for timeouts.

+ Some improved html and markdown.

Re: [UPDATE] lang/elixir 1.13.4

[Christoph Roland Winter]

Hello Stuart,

thanks for the fast answer, Yes, then it works.

Regards,


Christoph


Am 30.07.22 um 15:15 schrieb Stuart Henderson:

The erlang.port.mk diff is also required for this one.

--
   Sent from a phone, apologies for poor formatting.


On 30 July 2022 13:02:18 Christoph Roland Winter  wrote:


Hello,

tried the patch using OpenBSD 7.2-beta (GENERIC.MP) #656: Thu Jul 28
10:05:38 MDT 2022, amd64 and Erlang 25.0.3 from ports and got.

Invalid MODERL_VERSION set: 25. (in lang/elixir)
Invalid MODERL_VERSION set: 25. (in lang/elixir)
Invalid MODERL_VERSION set: 25. (in lang/elixir)
Invalid MODERL_VERSION set: 25. (in lang/elixir)
Invalid MODERL_VERSION set: 25. (in lang/elixir)
Invalid MODERL_VERSION set: 25. (in lang/elixir)
Invalid MODERL_VERSION set: 25. (in lang/elixir)
===>  Checking files for elixir-1.13.4
Invalid MODERL_VERSION set: 25. (in lang/elixir)

Fetch

https://github.com/elixir-lang/elixir/archive/v1.13.4/elixir-1.13.4.tar.gz

(SHA256) elixir-1.13.4.tar.gz: OK

===> elixir-1.13.4 depends on: rebar-* - not found
===>  Verifying install for rebar-* in devel/rebar
===>  Checking files for rebar-2.6.4p2

Fetch https://github.com/rebar/rebar/archive/2.6.4/rebar-2.6.4.tar.gz
(SHA256) rebar-2.6.4.tar.gz: OK
Broken dependency: lang/erlang/ ends with / (DEPENDS was

lang/erlang/) in devel/rebar
*** Error 1 in /usr/ports/devel/rebar
(/usr/ports/infrastructure/mk/bsd.port.mk:2293
'/usr/ports/pobj/rebar-2.6.4/.dep-lang-erlang-': @unset...)
*** Error 2 in /usr/ports/devel/rebar
(/usr/ports/infrastructure/mk/bsd.port.mk:2705
'/usr/ports/pobj/rebar-2.6.4/.extract_done': @cd /usr/p...)
*** Error 2 in /usr/ports/devel/rebar
(/usr/ports/infrastructure/mk/bsd.port.mk:2143
'/usr/ports/packages/amd64/all/rebar-2.6.4p2.tgz': @cd ...)
*** Error 2 in /usr/ports/devel/rebar
(/usr/ports/infrastructure/mk/bsd.port.mk:2632 '_internal-package':
@case X${_DEPENDS_CACHE} in  X) _D...)
*** Error 2 in /usr/ports/devel/rebar
(/usr/ports/infrastructure/mk/bsd.port.mk:2611 'package': @:; cd
/usr/ports/devel/rebar && PKGPATH=dev...)
*** Error 2 in /usr/ports/devel/rebar
(/usr/ports/infrastructure/mk/bsd.port.mk:2164
'/var/db/pkg/rebar-2.6.4p2/+CONTENTS': @cd /usr/ports/d...)
*** Error 2 in /usr/ports/devel/rebar
(/usr/ports/infrastructure/mk/bsd.port.mk:2611 'install':
@lock=rebar-2.6.4p2;  export _LOCKS_HELD=" e...)
*** Error 1 in . (/usr/ports/infrastructure/mk/bsd.port.mk:2293
'/usr/ports/pobj/elixir-1.13.4/.dep-devel-rebar,': @unset
_DEPENDS_TARGET _M...)
*** Error 2 in . (/usr/ports/infrastructure/mk/bsd.port.mk:2705
'/usr/ports/pobj/elixir-1.13.4/.extract_done': @cd
/usr/ports/lang/elixir &&...)
*** Error 2 in . (/usr/ports/infrastructure/mk/bsd.port.mk:2143
'/usr/ports/packages/amd64/all/elixir-1.13.4.tgz': @cd
/usr/ports/lang/elixi...)
*** Error 2 in . (/usr/ports/infrastructure/mk/bsd.port.mk:2632
'_internal-package': @case X${_DEPENDS_CACHE} in  X) _DEPENDS_CACHE=$(
mktem...)
*** Error 2 in . (/usr/ports/infrastructure/mk/bsd.port.mk:2611
'package': @:; cd /usr/ports/lang/elixir && PKGPATH=lang/elixir make
_intern...)
*** Error 2 in . (/usr/ports/infrastructure/mk/bsd.port.mk:2164
'/var/db/pkg/elixir-1.13.4/+CONTENTS': @cd /usr/ports/lang/elixir &&
PKGPATH...)
*** Error 2 in /usr/ports/lang/elixir
(/usr/ports/infrastructure/mk/bsd.port.mk:2611 'install':
@lock=elixir-1.13.4;  export _LOCKS_HELD=" e...)


Regards,


Christoph


Am 30.07.22 um 10:49 schrieb Volker Schlecht:

Another bump.

On 7/23/22 10:55, Volker Schlecht wrote:

bump

On 7/16/22 11:26, Volker Schlecht wrote:

Updates lang/elixir to 1.13.4
Changes MODERL_VERSION to 25 (erlang21 is now unsupported)
Requires rebar3 >= 3.19.0
Requires the patched lang/erlang/erlang.port.mk

Builds and tests fine on amd64

Re: [UPDATE] lang/elixir 1.13.4

[Christoph Roland Winter]

Hello,

tried the patch using OpenBSD 7.2-beta (GENERIC.MP) #656: Thu Jul 28 
10:05:38 MDT 2022, amd64 and Erlang 25.0.3 from ports and got.


Invalid MODERL_VERSION set: 25. (in lang/elixir)
Invalid MODERL_VERSION set: 25. (in lang/elixir)
Invalid MODERL_VERSION set: 25. (in lang/elixir)
Invalid MODERL_VERSION set: 25. (in lang/elixir)
Invalid MODERL_VERSION set: 25. (in lang/elixir)
Invalid MODERL_VERSION set: 25. (in lang/elixir)
Invalid MODERL_VERSION set: 25. (in lang/elixir)
===>  Checking files for elixir-1.13.4
Invalid MODERL_VERSION set: 25. (in lang/elixir)
>> Fetch 
https://github.com/elixir-lang/elixir/archive/v1.13.4/elixir-1.13.4.tar.gz

>> (SHA256) elixir-1.13.4.tar.gz: OK
===> elixir-1.13.4 depends on: rebar-* - not found
===>  Verifying install for rebar-* in devel/rebar
===>  Checking files for rebar-2.6.4p2
>> Fetch https://github.com/rebar/rebar/archive/2.6.4/rebar-2.6.4.tar.gz
>> (SHA256) rebar-2.6.4.tar.gz: OK
>> Broken dependency: lang/erlang/ ends with / (DEPENDS was 
lang/erlang/) in devel/rebar
*** Error 1 in /usr/ports/devel/rebar 
(/usr/ports/infrastructure/mk/bsd.port.mk:2293 
'/usr/ports/pobj/rebar-2.6.4/.dep-lang-erlang-': @unset...)
*** Error 2 in /usr/ports/devel/rebar 
(/usr/ports/infrastructure/mk/bsd.port.mk:2705 
'/usr/ports/pobj/rebar-2.6.4/.extract_done': @cd /usr/p...)
*** Error 2 in /usr/ports/devel/rebar 
(/usr/ports/infrastructure/mk/bsd.port.mk:2143 
'/usr/ports/packages/amd64/all/rebar-2.6.4p2.tgz': @cd ...)
*** Error 2 in /usr/ports/devel/rebar 
(/usr/ports/infrastructure/mk/bsd.port.mk:2632 '_internal-package': 
@case X${_DEPENDS_CACHE} in  X) _D...)
*** Error 2 in /usr/ports/devel/rebar 
(/usr/ports/infrastructure/mk/bsd.port.mk:2611 'package': @:; cd 
/usr/ports/devel/rebar && PKGPATH=dev...)
*** Error 2 in /usr/ports/devel/rebar 
(/usr/ports/infrastructure/mk/bsd.port.mk:2164 
'/var/db/pkg/rebar-2.6.4p2/+CONTENTS': @cd /usr/ports/d...)
*** Error 2 in /usr/ports/devel/rebar 
(/usr/ports/infrastructure/mk/bsd.port.mk:2611 'install': 
@lock=rebar-2.6.4p2;  export _LOCKS_HELD=" e...)
*** Error 1 in . (/usr/ports/infrastructure/mk/bsd.port.mk:2293 
'/usr/ports/pobj/elixir-1.13.4/.dep-devel-rebar,': @unset 
_DEPENDS_TARGET _M...)
*** Error 2 in . (/usr/ports/infrastructure/mk/bsd.port.mk:2705 
'/usr/ports/pobj/elixir-1.13.4/.extract_done': @cd 
/usr/ports/lang/elixir &&...)
*** Error 2 in . (/usr/ports/infrastructure/mk/bsd.port.mk:2143 
'/usr/ports/packages/amd64/all/elixir-1.13.4.tgz': @cd 
/usr/ports/lang/elixi...)
*** Error 2 in . (/usr/ports/infrastructure/mk/bsd.port.mk:2632 
'_internal-package': @case X${_DEPENDS_CACHE} in  X) _DEPENDS_CACHE=$( 
mktem...)
*** Error 2 in . (/usr/ports/infrastructure/mk/bsd.port.mk:2611 
'package': @:; cd /usr/ports/lang/elixir && PKGPATH=lang/elixir make 
_intern...)
*** Error 2 in . (/usr/ports/infrastructure/mk/bsd.port.mk:2164 
'/var/db/pkg/elixir-1.13.4/+CONTENTS': @cd /usr/ports/lang/elixir && 
PKGPATH...)
*** Error 2 in /usr/ports/lang/elixir 
(/usr/ports/infrastructure/mk/bsd.port.mk:2611 'install': 
@lock=elixir-1.13.4;  export _LOCKS_HELD=" e...)



Regards,


Christoph


Am 30.07.22 um 10:49 schrieb Volker Schlecht:

Another bump.

On 7/23/22 10:55, Volker Schlecht wrote:

bump

On 7/16/22 11:26, Volker Schlecht wrote:

Updates lang/elixir to 1.13.4
Changes MODERL_VERSION to 25 (erlang21 is now unsupported)
Requires rebar3 >= 3.19.0
Requires the patched lang/erlang/erlang.port.mk

Builds and tests fine on amd64

Re: [UPDATE] lang/erlang/25 25.0.3

[Christoph Roland Winter]

Hello,

the build worked using OpenBSD 7.2-beta (GENERIC.MP) #656: Thu Jul 28 
10:05:38 MDT 2022, amd64


Regards,

Christoph


Am 30.07.22 um 10:50 schrieb Volker Schlecht:

And ... bump.

On 7/23/22 10:56, Volker Schlecht wrote:

bump

On 7/16/22 12:33, Volker Schlecht wrote:

Updates lang/erlang/25 to version 25.0.3

https://www.erlang.org/patches/otp-25.0.3

It plays well with the proposed changes to devel/rebar3, lang/elixir 
and erlang.port.mk, but is not a precondition for any of them.

Re: [MAINTAINER UPDATE] www/honk 0.9.7 -> 0.9.8

[Christoph Roland Winter]

Hello,

I have only kept the first message and was some time not subscribed to 
the list - lets see, where the message ends.


I tried the latest patch from 
https://marc.info/?l=openbsd-ports=165827470732358=p3 and it worked 
fine using


OpenBSD 7.2-beta (GENERIC.MP) #654: Wed Jul 27 20:10:05 MDT 2022 and the 
-current ports tree using amd64.


Maybe I am wrong but the crontab from the above patch

+~ ~ * * * acme-client honk.example.com && ocspcheck -No 
${SYSCONFDIR}/ssl/honk.example.com.{ocsp,crt} && rcctl reload relayd


needs to be modified. The first && must be replaced with ; (or splited 
in 2 cron jobs). As it is now, the ocsp file gets only renewed all 60 
days, as acme-client renews the certificate only 30 days before it 
expires (checked with the -v option and as nothing happened before, && 
stops at this point). BTW my ocsp file with the above command is valid 
for 7 days.


ocspcheck -vNo /etc/ssl/the.floof.rocks.{ocsp,crt}
Using http to host r3.o.lencr.org, port 80, path /
OCSP response validated from r3.o.lencr.org
   This Update: Thu Jul 28 15:00:00 2022
   Next Update: Thu Aug  4 14:59:58 2022

The only thing I did was using the /etc/examples/acme-client.conf file, 
added my email and added the domain blocks.


Regards,


Christoph


Am 01.06.22 um 23:37 schrieb Horia Racoviceanu:

Upgrade to v0.9.8
- Add MESSAGE
- Update README

changelog

=== 0.9.8 Tentative Tentacle

+ Switch database to WAL mode.

- go version 1.16 required.

+ Specify banner: image in profile.

+ Update activity compatibility with mastodon.

- Signed fetch.

+ Better unicode hashtags.

+ Some more configuration options.

+ Some UI improvements to web interface.

+ Add atme class to mentions

+ Improvements to the mastodon importer.

+ More hydration capable pages.

+ Support for local.js.

+ Better error messages for timeouts.

+ Some improved html and markdown.