On 3/7/19 11:16 PM, Daniel Kahn Gillmor wrote:
> Weird! This bug was reported against 3.2.0-1 in the first place, so i'm
> pretty confused :/
yes, that was totally my fault and I'm sorry for the confusion (wasn't
my intention).
I didn't double-checked the version I'm running when reporting the b
On 3/7/19 11:16 PM, Daniel Kahn Gillmor wrote:
> Weird! This bug was reported against 3.2.0-1 in the first place, so i'm
> pretty confused :/
yes, that was totally my fault and I'm sorry for the confusion (wasn't
my intention).
I didn't double-checked the version I'm running when reporting the b
On Thu 2019-03-07 21:37:30 +0100, Daniel Baumann wrote:
> i've verified this with another vanilla system that wasn't upgraded and
> i can reproduce it there: 3.2.0-1 fixed it.
Weird! This bug was reported against 3.2.0-1 in the first place, so i'm
pretty confused :/ But at least it's gone away :
close 922120 3.2.0-1
thanks
Hi,
On 3/7/19 6:41 PM, Daniel Kahn Gillmor wrote:
> I'm trying to replicate this, and having difficulty. Where exactly do
> you see this message? on the terminal? in the journal? on the console?
both when typing e.g. 'service ssh restart' in gnome-terminal or tty1.
Control: tags 922120 + moreinfo
Hi Daniel--
On Tue 2019-02-12 11:54:55 +0100, Daniel Baumann wrote:
> thank you so much for maintaining knot-resolver, it's wonderful.
Glad you find it useful!
> Unfortunately, whenever *any* service is reladed on my system (vanilla
> debian with 'apt install kno
Package: knot-resolver
Severity: normal
Version: 3.2.0-1
Hi,
thank you so much for maintaining knot-resolver, it's wonderful.
Unfortunately, whenever *any* service is reladed on my system (vanilla
debian with 'apt install knot-resolver'), I always get the following
message:
Failed to get prop
6 matches
Mail list logo
