Le Tue, Oct 22, 2024 at 09:10:40PM +0200, Hukadan a écrit :
> On Mon Oct 7, 2024 at 7:29 PM CEST, Landry Breuil wrote:
> > hi,
> >
> > as usual we're lagging behind.. quite some releases, and once again a
> > 'breaking' change requiring reading
> > https://github.com/stalwartlabs/mail-server/blob/v
On 2024/10/22 10:55, Paul Galbraith wrote:
> On 2024-10-22 5:22 a.m., Stuart Henderson wrote:
> > Can you reattach the port please so we don't need to go looking in the
> > archives.
> Sure thing, attached.
Thanks. Couple of small things:
- it's unfortunate about the name conflict, but it's unavo
On Wed, 23 Oct 2024 09:49:06 +0200,
Landry Breuil wrote:
>
> Le Tue, Oct 22, 2024 at 09:10:40PM +0200, Hukadan a écrit :
>
> > As a side note, I think it would be worth mentioning in the README that
> > the web UI uses WASM. I thought I did something wrong when I first saw
> > a white screen.
>
On 2024/10/22 21:57, Bryan Vyhmeister wrote:
> On Tue, Oct 22, 2024 at 01:41:52PM -0700, Bryan Vyhmeister wrote:
> > I came across a half-finished and out-of-date attempt at direwolf in
> > openbsd-wip on github from five years ago. I updated the port and it is
> > building fine now. Is anyone able
23.10.2024 05:09, Lucas Gabriel Vuotto пишет:
> Committed with the seemingly more correct
>
> ${SETENV} ${MAKE_ENV} ${MAKE_PROGRAM} ${MAKE_FLAGS} -C ...
Yup.
>
>> (lots of ports use MAKE, though).
>
> In principle this is wrong and these ports
>
> cad/xcircuit
> games/angband
> games/pu
Le Wed, Oct 23, 2024 at 09:59:27AM +0200, Kirill A. Korinsky a écrit :
> On Wed, 23 Oct 2024 09:49:06 +0200,
> Landry Breuil wrote:
> >
> > Le Tue, Oct 22, 2024 at 09:10:40PM +0200, Hukadan a écrit :
> >
> > > As a side note, I think it would be worth mentioning in the README that
> > > the web U
I'm ok with removing telegram-purple.
--
Sent from a phone, apologies for poor formatting.
On 22 October 2024 22:59:40 Lucas de Sena wrote:
On 2024-09-20, Lucas de Sena wrote:
Telegram-purple, as well as every libtgl-based application, does not
work anymore (i tested).
Port's page[1] says
Hi there,
so I'm writing IETF drafts now.
Please stop laughing.
We already have xml2rfc. I'll poke at kramdown-rfc2629 (ruby) next,
because I'm not going to write raw xml...
Another thing I'd like to have is idnits
https://github.com/ietf-tools/idnits/tree/v2
Which is just a bash script, and y
On Wed, Oct 23, 2024 at 01:00:46PM +0200, Florian Obser wrote:
> Hi there,
>
> so I'm writing IETF drafts now.
>
> Please stop laughing.
>
> We already have xml2rfc. I'll poke at kramdown-rfc2629 (ruby) next,
> because I'm not going to write raw xml...
>
> Another thing I'd like to have is idni
We usually go for a full path to the interpreter rather than env and
relying on the user's PATH including /usr/local/bin
--
Sent from a phone, apologies for poor formatting.
On 23 October 2024 12:01:12 Florian Obser wrote:
Hi there,
so I'm writing IETF drafts now.
Please stop laughing.
W
Ugh, I've just looked at the script, have they not heard of perl?!
--
Sent from a phone, apologies for poor formatting.
On 23 October 2024 13:08:04 Stuart Henderson wrote:
We usually go for a full path to the interpreter rather than env and
relying on the user's PATH including /usr/local/bin
On 2024-10-23 13:10 +01, Stuart Henderson wrote:
> Ugh, I've just looked at the script, have they not heard of perl?!
Why would you do that? That sounds unpleasant.
And no, they probably have not heard of perl, hence the rewrite in
JavaScript...
--
In my defence, I have been left unsupervised.
On 2024-10-23 13:07 +01, Stuart Henderson wrote:
> We usually go for a full path to the interpreter rather than env and
> relying on the user's PATH including /usr/local/bin
Noted.
This came out of audio/pulseaudio in case that should be "fixed".
--
In my defence, I have been left unsupervise
On Sat, 19 Oct 2024 20:56:25 +0200,
Klemens Nanni wrote:
>
> >> ports@, Remi,
>
> Still no maintainer response, I suggest we remove Remi as maintainer.
I willing to take care of wapiti and replace Remi if he doesn't interested
in it anymore.
> >>
> >> Here an update of security/wapiti to the l
Hi everyone!
FWIW, I've reverted the textproc/elasticsearch removal (Git 8d210dbcdf)
locally and got v7.10.0 built on 7.6/i386.
Now that they triple-licensed the OSS part with AGPL etc.,
could we have the port back? Or is the efford not worth it?
Best && A/K
squeak(1) refers to 'inisqueak' for initializing a new
workspace, but that script is not in the port. Should
it be?
--lyndon
On Wed Oct 23, 2024 at 9:49 AM CEST, Landry Breuil wrote:
> Le Tue, Oct 22, 2024 at 09:10:40PM +0200, Hukadan a écrit :
> > On Mon Oct 7, 2024 at 7:29 PM CEST, Landry Breuil wrote:
> > > hi,
> > >
> > > as usual we're lagging behind.. quite some releases, and once again a
> > > 'breaking' change re
On Wed, Oct 23, 2024 at 11:27:19AM +0100, Stuart Henderson wrote:
> On 2024/10/22 21:57, Bryan Vyhmeister wrote:
> > On Tue, Oct 22, 2024 at 01:41:52PM -0700, Bryan Vyhmeister wrote:
> > > I came across a half-finished and out-of-date attempt at direwolf in
> > > openbsd-wip on github from five yea
Hi, ports@:
Here is a simple patch for devel/p5-Perl-Critic to
update to 1.156. Build well and pass all tests on
amd64-current system.
Best Regards,
wenIndex: devel/p5-Perl-Critic/Makefile
===
RCS file: /cvs/ports/devel/p5-Perl
Hi, all:
Here is a patch for www/p5-HTML-Form:
i) Update to 6.12
ii) Add a missing TEST_DEPENDS
It build well and pass all tests on amd64-current system.
Best Regards,
wenIndex: www/p5-HTML-Form/Makefile
===
RCS file: /c
20 matches
Mail list logo
