On 05/03/2017 12:49 PM, Paul Wise wrote:
> On Wed, 2017-05-03 at 12:24 +0200, Moritz Schlarb wrote:
>
>> - This has been the behavior of the Nagstamon package since forever
>> (which is not a valid argumentation point - I know, but it's still a fact)
>
> There are two serious bugs here:
>
> 1) t
On Wed, 2017-05-03 at 12:24 +0200, Moritz Schlarb wrote:
> - This has been the behavior of the Nagstamon package since forever
> (which is not a valid argumentation point - I know, but it's still a fact)
There are two serious bugs here:
1) that certificates are not verified at least using CAs an
Hi Julien, hi Paul,
On 03.05.2017 11:51, Julien Cristau wrote:
> I don't see how not checking certificates is in any way a reasonable
> thing to do. Silencing warnings about it makes it even worse.
Absolutely true - but:
- This has been the behavior of the Nagstamon package since forever
(which
On 05/03/2017 10:13 AM, Moritz Schlarb wrote:
> Package: release.debian.org
> Severity: normal
> User: release.debian@packages.debian.org
> Usertags: unblock
>
> Please unblock package nagstamon
>
> Hi there,
>
> nagstamon/2.0.1-4, which just got uploaded to unstable fixes #861152, which is
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
Please unblock package nagstamon
Hi there,
nagstamon/2.0.1-4, which just got uploaded to unstable fixes #861152, which is
release critical and #774002, which just adds a Recommends for con
5 matches
Mail list logo