On Thu, 30 Jan 2020 at 13:36, Csillag Tamas wrote:
>
> It seems that the current version in sid (currently: 8.32+dfsg-1) has the fix
> as running the commands just work fine while the buster version (8.12+dfsg-1)
> fails in the way that is described earlier.
>
> Thus this bug might be closed?
Cel
On Wed, Jul 03, 2019 at 09:49:14AM +0100, Nick Morrott wrote:
[...]
> Upstream have now created a new TLS keypair which will be included in
> the next Mojolicious release.
>
> My current plan is to review the update and upload a new 8.12 build
> targetting the first Debian "buster" point release w
On Wed, 3 Jul 2019 09:49:14 +0100
Nick Morrott wrote:
> On Sun, 23 Jun 2019 at 01:58, Nick Morrott wrote:
> >
> > > Upstream tried to help, but seems to be out of ideas:
> > >
> > > https://groups.google.com/forum/#!topic/mojolicious/gjz-0uvUDLk
> >
> > I have posted an update to that thread (cu
On Sun, 23 Jun 2019 at 01:58, Nick Morrott wrote:
>
> > Upstream tried to help, but seems to be out of ideas:
> >
> > https://groups.google.com/forum/#!topic/mojolicious/gjz-0uvUDLk
>
> I have posted an update to that thread (currently held for
> moderation). I have also created an upstream PR [2]
On Tue, 28 May 2019 at 13:09, Celejar wrote:
>
> Package: libmojolicious-perl
> Version: 8.12+dfsg-1
> Severity: important
> File: mojolicious
> Tags: upstream
>
> Mojolicious's HTTPS functionality is completely broken on my system
> (ordinary HTTP access works fine):
The default https server key
Package: libmojolicious-perl
Version: 8.12+dfsg-1
Severity: important
File: mojolicious
Tags: upstream
Mojolicious's HTTPS functionality is completely broken on my system
(ordinary HTTP access works fine):
~$ mojo daemon -l https://*:3000
Server available at https://127.0.0.1:3000
~$ curl -v -k
6 matches
Mail list logo
