Hi,
Here's an update to libuv, needed for neovim-0.6.0 (requires new functions
recently introduced in libuv).
There are three more test failures than before:
```
--- failing-before Wed Dec 15 09:18:34 2021
+++ failing-after Wed Dec 15 09:18:46 2021
@@ -1,4 +1,7 @@
fs_lutime
get_curr
On Tue, 14 Dec 2021, Paco Esteban wrote:
> On Mon, 13 Dec 2021, Laurence Tratt wrote:
>
> > On Sat, Dec 11, 2021 at 07:06:46PM -0700, Evan Fiddes wrote:
> >
> > Hello Evan,
> >
> > > This bumps the neovim version to 0.6.0 the most current release. See patch
> > > notes[0] for a detailed breakdo
On 2021/12/15 01:03, Antoine Jacoutot wrote:
> These error cases you are mentioning will happen in bulk as soon as something
> depend on the compact subpackage
Or the main package, if they're added there ;)
On Wed, Dec 15, 2021 at 11:42:21AM +, Stuart Henderson wrote:
> On 2021/12/15 01:03, Antoine Jacoutot wrote:
> > These error cases you are mentioning will happen in bulk as soon as
> > something depend on the compact subpackage
>
> Or the main package, if they're added there ;)
Which is my
Hi, On OpenBSD Ports (https://openports.se/) some projects are maintained
by "The OpenBSD ports mailing-list".I would like to see the port of
uCON64 (https://openports.se/emulators/ucon64) updated, because version
2.2.2 was released last month.How does this work? Will one of you just
pick it up or
On 2021/12/15 15:23, Daniël Hörchner wrote:
> Hi, On OpenBSD Ports (https://openports.se/) some projects are maintained
> by "The OpenBSD ports mailing-list".I would like to see the port of
> uCON64 (https://openports.se/emulators/ucon64) updated, because version
> 2.2.2 was released last month.How
Hello,
Daniël Hörchner wrote:
> Hi, On OpenBSD Ports (https://openports.se/) some projects are maintained
> by "The OpenBSD ports mailing-list".I would like to see the port of
> uCON64 (https://openports.se/emulators/ucon64) updated, because version
> 2.2.2 was released last month.How does this wo
This port is required for another upcoming port.
rnnoise is small and standalone and already works when used in that port
so I'd like to get it in now as a first step.
I'll maintain the package.
---
Information for inst:rnnoise-20210312
Comment:
Recurrent neural network for audio noise reduction
On Wed, Dec 15, 2021 at 11:42:21AM +, Stuart Henderson wrote:
> On 2021/12/15 01:03, Antoine Jacoutot wrote:
> > These error cases you are mentioning will happen in bulk as soon as
> > something depend on the compact subpackage
>
> Or the main package, if they're added there ;)
I see what y
The pkg-config executable hardcodes these variables,
the Makefile does not expand them like ports do and
ports land is somewhat shifted to hardcode those paths anyway.
OK?
Index: pkg-config.1
===
RCS file: /cvs/src/usr.bin/pkg-confi
Mumble picks up rnnoise iff present, so enable it explicitly and provide
users with decent noise suppression.
Tested successfully with artifical noise, both in chats and through
Mumble's recording feature.
OK once rnnoise is committed?
Index: Makefile
On Mon, Dec 13, 2021 at 10:54:32AM +, Lucas wrote:
> Find an update to mblaze 1.2. Release notes:
Committed, thanks.
Klemens Nanni wrote:
> This port is required for another upcoming port.
> rnnoise is small and standalone and already works when used in that port
> so I'd like to get it in now as a first step.
>
> I'll maintain the package.
>
> ---
> Information for inst:rnnoise-20210312
>
> Comment:
> Recurre
Timo Myyrä writes:
> Hi,
>
> A bit delayed update to gzdoom. The upstream have made chopped the music
> part as standalone library which I sent to ports@ earlier (audio/zmusic)
> which is needed by this update.
>
> Quickly tested on doom1 which appeared to be working.
>
>[...]
>
> CONFIGURE_ARGS
> The URL https://arxiv.org/pdf/1709.08243.pdf can be downloaded with
> ftp, but the wget user agent seem to be forbidden. This might confuse
> users... is this worth mentioning?
In general it's better to link to the abstract page on arxiv rather than
a specific file format
https://arxiv.org/abs
On Wed, Dec 15, 2021 at 09:28:27PM +0100, Theo Buehler wrote:
> > The URL https://arxiv.org/pdf/1709.08243.pdf can be downloaded with
> > ftp, but the wget user agent seem to be forbidden. This might confuse
> > users... is this worth mentioning?
>
> In general it's better to link to the abstract
Theo Buehler wrote:
> > The URL https://arxiv.org/pdf/1709.08243.pdf can be downloaded with
> > ftp, but the wget user agent seem to be forbidden. This might confuse
> > users... is this worth mentioning?
>
> In general it's better to link to the abstract page on arxiv rather than
> a specific fi
On Wed, Dec 15, 2021 at 09:21:59PM +0100, Stefan Hagen wrote:
> Klemens Nanni wrote:
> > This port is required for another upcoming port.
> > rnnoise is small and standalone and already works when used in that port
> > so I'd like to get it in now as a first step.
> >
> > I'll maintain the package
Klemens Nanni wrote:
> On Wed, Dec 15, 2021 at 09:21:59PM +0100, Stefan Hagen wrote:
> > Klemens Nanni wrote:
> > > This port is required for another upcoming port.
> > > rnnoise is small and standalone and already works when used in that port
> > > so I'd like to get it in now as a first step.
> >
On Wed, Dec 15, 2021 at 09:58:33PM +0100, Stefan Hagen wrote:
> Klemens Nanni wrote:
> > On Wed, Dec 15, 2021 at 09:21:59PM +0100, Stefan Hagen wrote:
> > > Klemens Nanni wrote:
> > > > This port is required for another upcoming port.
> > > > rnnoise is small and standalone and already works when u
On Wed, Dec 15, 2021 at 09:58:33PM +0100, Stefan Hagen wrote:
> Either way, ok sdk@
Aargh, one thing I had in my tree but not in the sent tarball:
-PKGNAME = rnnoise-20210312
+PKGNAME = rnnoise-0.0.0.20210312
So once upstream uses versions, we have better changes of doing a
regular upd
Klemens Nanni wrote:
> On Wed, Dec 15, 2021 at 09:58:33PM +0100, Stefan Hagen wrote:
> > Either way, ok sdk@
>
> Aargh, one thing I had in my tree but not in the sent tarball:
>
> -PKGNAME =rnnoise-20210312
> +PKGNAME =rnnoise-0.0.0.20210312
>
> So once upstream uses versions, we have be
On 2021 Dec 15 (Wed) at 21:21:13 + (+), Klemens Nanni wrote:
:What do other porters think in general about such ports that are
:unversioned upstream?
:
:I went for 0.0.0.date as that's used in a few other ports:
EPOCH is the devil, and should be avoided whenever possible. I
understand it
On Wed, Dec 15, 2021 at 11:01:08PM +0100, Peter Hessler wrote:
> On 2021 Dec 15 (Wed) at 21:21:13 + (+), Klemens Nanni wrote:
> :What do other porters think in general about such ports that are
> :unversioned upstream?
> :
> :I went for 0.0.0.date as that's used in a few other ports:
>
> E
On 15.12.2021 12:16, Paco Esteban wrote:
On Tue, 14 Dec 2021, Paco Esteban wrote:
On Mon, 13 Dec 2021, Laurence Tratt wrote:
> On Sat, Dec 11, 2021 at 07:06:46PM -0700, Evan Fiddes wrote:
>
> Hello Evan,
>
> > This bumps the neovim version to 0.6.0 the most current release. See patch
> > notes
On 15.12.2021 10:52, Edd Barrett wrote:
Hi,
Here's an update to libuv, needed for neovim-0.6.0 (requires new functions
recently introduced in libuv).
There are three more test failures than before:
```
--- failing-before Wed Dec 15 09:18:34 2021
+++ failing-after Wed Dec 15 09:18:46
On 2021/12/15 20:34, Klemens Nanni wrote:
> On Wed, Dec 15, 2021 at 09:21:59PM +0100, Stefan Hagen wrote:
> > Klemens Nanni wrote:
> > > This port is required for another upcoming port.
> > > rnnoise is small and standalone and already works when used in that port
> > > so I'd like to get it in now
> I don't see anything wrong with that but I don't know why you have that
> dir. Run the command "raco pkg config" as regular user. You should have
> something like this output:
>
> current-amd64$ raco pkg config
> name:
> 8.3
> catalogs:
> https://download.racket-lang.org/releases/8.3/catalog/
>
> > but with your user. Running "racket-user-bin-paths" you should see the
> > bin directory path within $HOME/.racket.
> >
> > And this is the right config file in /etc/racket/config.rktd:
> > ;; generated by unixstyle-install
> > #hash(
> > (doc-dir . "/usr/local/share/doc/racket")
> >
Another dependency that is small and standalone; I have successfully
used as library.
The port builds a bunch of programs but doesn't install them, so until
a valid use case appears for those executables I have disabled building
them (90 vs 25 source files to compile).
`portcheck -N' is happy an
On Thu, Dec 16, 2021 at 01:09:24AM +, Klemens Nanni wrote:
> Another dependency that is small and standalone; I have successfully
> used as library.
>
> The port builds a bunch of programs but doesn't install them, so until
> a valid use case appears for those executables I have disabled buil
On 2021/12/16 01:12, Klemens Nanni wrote:
> On Thu, Dec 16, 2021 at 01:09:24AM +, Klemens Nanni wrote:
> > Another dependency that is small and standalone; I have successfully
> > used as library.
> >
> > The port builds a bunch of programs but doesn't install them, so until
> > a valid use c
On Wed, Dec 15, 2021 at 04:49:06AM +, James Cook wrote:
> On Tue, Dec 14, 2021 at 09:44:03PM +0100, Juan Francisco Cantero Hurtado
> wrote:
> > On Tue, 14 Dec 2021 14:18:39 +
> > James Cook wrote:
> >
> > > On Tue, Dec 14, 2021 at 10:11:12AM +0100, Denis Fondras wrote:
> > > > Le Tue, De
On Thu, Dec 16, 2021 at 01:19:45AM +, Stuart Henderson wrote:
> On 2021/12/16 01:12, Klemens Nanni wrote:
> > On Thu, Dec 16, 2021 at 01:09:24AM +, Klemens Nanni wrote:
> > > Another dependency that is small and standalone; I have successfully
> > > used as library.
> > >
> > > The port b
Rafael Sadowski writes:
> On Sun Dec 12, 2021 at 03:41:48PM +0100, Rafael Sadowski wrote:
>> I'll fix calligra.
>>
I propose an inline diff that does the following three things:
1.) Removes kcalendarcore and kcontacts from BUILD_DEPENDS and
RUN_DEPENDS.
These are listed as optional and only li
On Wed Dec 15, 2021 at 06:51:09PM -0800, Nam Nguyen wrote:
> Rafael Sadowski writes:
>
> > On Sun Dec 12, 2021 at 03:41:48PM +0100, Rafael Sadowski wrote:
> >> I'll fix calligra.
> >>
>
> I propose an inline diff that does the following three things:
>
> 1.) Removes kcalendarcore and kcontacts
36 matches
Mail list logo