Branko Čibej writes:
> Alternatively we could just generate the test certs in every test run.
> They're self-signed, IIRC? So it shouldn't be a problem.
That could be a viable option.
In the meanwhile, I tend to think that simply increasing the lifespan of those
certificates is a fairly practic
On 05.10.2021 19:31, Alexandr Miloslavskiy wrote:
In the time since the last 1.3.9 release, test certificates has
already expired two times, causing tests to fail. Our build script runs
tests, so entire build fails for us. Let's fix that.
Due to the presence of binary files in patch, I had to us
Alexandr Miloslavskiy writes:
> In the time since the last 1.3.9 release, test certificates has
> already expired two times, causing tests to fail. Our build script runs
> tests, so entire build fails for us. Let's fix that.
>
> Due to the presence of binary files in patch, I had to use
> 'svn di
On 06.10.2021 1:56, James McCoy wrote:
For what it's worth, in the Debian packaging I re-generate the test
certs whenever we do a build to avoid the issue.
This works when you know what you're doing. However, for a user who
simply downloaded serf sources and tries to build them, this spits a
On Tue, Oct 05, 2021 at 08:31:54PM +0300, Alexandr Miloslavskiy wrote:
> In the time since the last 1.3.9 release, test certificates has
> already expired two times, causing tests to fail. Our build script runs
> tests, so entire build fails for us. Let's fix that.
For what it's worth, in the Debi
In the time since the last 1.3.9 release, test certificates has
already expired two times, causing tests to fail. Our build script runs
tests, so entire build fails for us. Let's fix that.
Due to the presence of binary files in patch, I had to use
'svn diff --git'. Apply with 'svn patch --strip 2
