Here is an update to libsamplerate 0.2.1.
Version 0.2.1 (2021-01-23)
* Fix incorrect passing of -version-info to libtool, causing a
regression on versioned file name of the shared library (#140).
* Fix time resolution on GNU/Hurd for throughput_test
* Update AUTHORS and release manager d
On Fri, Sep 03, 2021 at 10:09:02AM -0700, Tomasz Bielecki wrote:
> Please consider including this patch, it seems common across other
> OSes supporting Pinebook Pro and fixes the display issues on warm
> reset.
>
> $OpenBSD$
>
> Fix Pinebook Pro display on warm reset.
>
> By Arnaud Patard
> http
On 2021/09/03 15:20, Kurt Mosiejczuk wrote:
> On Fri, Sep 03, 2021 at 06:30:01PM +, Klemens Nanni wrote:
>
> > Put it into a `show-checksums' target so the regular `makesum' does not
> > get slowed down on already big/slow ports?
>
> I don't understand this suggestion. makesum only gets run w
Kurt Mosiejczuk writes:
> On Fri, Sep 03, 2021 at 12:04:42PM -0600, Aaron Bieber wrote:
>
>> How many is multiple? :D - the Go stuff is gonna get ugly(er?)!
>
>> net/go-ipfs for example, the output is useless because it's so big :D
>
> Does go actually publish base64 SHA256 hashes for their mod
On Fri, Sep 03, 2021 at 06:30:01PM +, Klemens Nanni wrote:
> Put it into a `show-checksums' target so the regular `makesum' does not
> get slowed down on already big/slow ports?
I don't understand this suggestion. makesum only gets run when one updates
a port. The existing output it fairly us
On Fri, Sep 03, 2021 at 12:04:42PM -0600, Aaron Bieber wrote:
> How many is multiple? :D - the Go stuff is gonna get ugly(er?)!
> net/go-ipfs for example, the output is useless because it's so big :D
Does go actually publish base64 SHA256 hashes for their modules?
If not, it's not the size of th
On Fri, Sep 03, 2021 at 12:04:42PM -0600, Aaron Bieber wrote:
>
> Kurt Mosiejczuk writes:
>
> > Whenever I update a port or create a new one, to verify the hashes I have
> > to run sha256(1) or md5(1) on the distfile. makesum does display our SHA256
> > has, but we use base64 format and everywhe
Kurt Mosiejczuk writes:
> Whenever I update a port or create a new one, to verify the hashes I have
> to run sha256(1) or md5(1) on the distfile. makesum does display our SHA256
> has, but we use base64 format and everywhere else (that I've interacted with)
> uses hexadecimal format.
>
> This d
Yup, I volunteer ... feel free to add
MAINTAINER = Volker Schlecht
I hope that sweetens the commit ;-P
On 9/3/21 7:47 PM, Aaron Bieber wrote:
vl...@tuta.io writes:
I don’t want to nag, but I’ll do it anyway…
While I presume that NodeJS and its ecosystem don’t enjoy much popularity here,
I
vl...@tuta.io writes:
> I don’t want to nag, but I’ll do it anyway…
> While I presume that NodeJS and its ecosystem don’t enjoy much popularity
> here, I don’t think that keeping an outdated version in ports is a good idea
> either.
>
> I’ll be happy to keep working on this if the patch isn’
On Fri, Sep 03, 2021 at 10:39:27AM -0600, Aaron Bieber wrote:
> Here is a simple diff that brings gitlab-runner to the latest version!
> Changelog here:
> https://gitlab.com/gitlab-org/gitlab-runner/blob/v14.2.0/CHANGELOG.md
> OK?
ok kmos
--Kurt
> diff d05dcdadd2cce0c8d0b776d4433bbfaefe56eaf6
Whenever I update a port or create a new one, to verify the hashes I have
to run sha256(1) or md5(1) on the distfile. makesum does display our SHA256
has, but we use base64 format and everywhere else (that I've interacted with)
uses hexadecimal format.
This diff makes the makesum target spit out h
Please consider including this patch, it seems common across other
OSes supporting Pinebook Pro and fixes the display issues on warm
reset.
$OpenBSD$
Fix Pinebook Pro display on warm reset.
By Arnaud Patard
http://people.hupstream.com/~rtp/pbp/20200706/patches/hack-reset.patch
Index: board/pine
Here is a simple diff that brings gitlab-runner to the latest version!
Changelog here:
https://gitlab.com/gitlab-org/gitlab-runner/blob/v14.2.0/CHANGELOG.md
OK?
diff d05dcdadd2cce0c8d0b776d4433bbfaefe56eaf6 /usr/ports
blob - 2a1fbeaadb9a5987fe0cd41b444ef1b8097b1161
file + sysutils/gitlab-runner/
On 2021/09/03 16:31, Frederic Cambus wrote:
> On Mon, Aug 12, 2019 at 07:39:23AM +0200, Theo Buehler wrote:
> > On Sun, Aug 11, 2019 at 11:30:09PM +0100, Stuart Henderson wrote:
> > > So the claimed advantage is that it's super fast, but actually it uses way
> > > more cpu than probably any other t
On Mon, Aug 12, 2019 at 07:39:23AM +0200, Theo Buehler wrote:
> On Sun, Aug 11, 2019 at 11:30:09PM +0100, Stuart Henderson wrote:
> > So the claimed advantage is that it's super fast, but actually it uses way
> > more cpu than probably any other terminal emulator in the tree except
> > cool-retro-t
On Tue, Aug 24, 2021 at 07:48:45AM +, Mikolaj Kucharski wrote:
> On Mon, Aug 16, 2021 at 10:07:58AM +, Mikolaj Kucharski wrote:
> > On Mon, Aug 09, 2021 at 06:41:02PM +, Mikolaj Kucharski wrote:
> > > On Tue, Mar 23, 2021 at 10:53:08PM +, Mikolaj Kucharski wrote:
> > > > On Tue, Mar
Jeremie Courreges-Anglas wrote:
> On Fri, Sep 03 2021, Renaud Allard wrote:
> > On 9/2/21 11:38 PM, Jeremie Courreges-Anglas wrote:
> >> On Thu, Sep 02 2021, Jeremie Courreges-Anglas wrote:
> >>> On Thu, Sep 02 2021, "Theo de Raadt" wrote:
> Jeremie Courreges-Anglas wrote:
>
> >
> crates.inc isn't in the diff, so here's a complete one. I'll do some tests
> on i386 amd64 aarch64, is there anyone who can do at least a build test
> on sparc64 for me please?
builds & packages fine, tests look like this, which seems quite usual.
= 2478 passed, 3523 skipped in
On Fri, Sep 03 2021, Renaud Allard wrote:
> On 9/2/21 11:38 PM, Jeremie Courreges-Anglas wrote:
>> On Thu, Sep 02 2021, Jeremie Courreges-Anglas wrote:
>>> On Thu, Sep 02 2021, "Theo de Raadt" wrote:
Jeremie Courreges-Anglas wrote:
>
>
> exim apparently uses printf("%n"),
On Sun, Aug 29, 2021 at 03:36:40PM +0200, Hiltjo Posthuma wrote:
> > Other than that, both look good and following your readmes and sample
> > sfeedrc gets everything working on my machine.
Same here, works as advertised on my machine.
> I've attached an updated tarball of the ports with your re
On 2021/09/03 10:51, Sebastien Marie wrote:
> On Thu, Sep 02, 2021 at 03:40:34PM +0100, Stuart Henderson wrote:
> > Thought I'd take a look at enabling the rust pieces in py-cryptography.
> > A future release is expected to remove the "CRYPTOGRAPHY_DONT_BUILD_RUST=1"
> > knob, so it would be good t
On 9/2/21 11:38 PM, Jeremie Courreges-Anglas wrote:
On Thu, Sep 02 2021, Jeremie Courreges-Anglas wrote:
On Thu, Sep 02 2021, "Theo de Raadt" wrote:
Jeremie Courreges-Anglas wrote:
exim apparently uses printf("%n"), which is currently forbidden (libc
calls abort(3)).
I don't want us t
On Thu, Sep 02, 2021 at 03:40:34PM +0100, Stuart Henderson wrote:
> Thought I'd take a look at enabling the rust pieces in py-cryptography.
> A future release is expected to remove the "CRYPTOGRAPHY_DONT_BUILD_RUST=1"
> knob, so it would be good to get this working. Runtime is working but
> I'm not
24 matches
Mail list logo
