Re: pkg_add "signify: write to stdout: Broken pipe"

2016-10-12 Thread Marc Espie
On Wed, Oct 12, 2016 at 10:51:59AM +0200, Martin Natano wrote: > I've seen this since the new signing method has been implemented. I > blamed it on something being out of date/sync on my machine, but after > updating to the latest snapshot yesterday (the one from ftp.fr) it > becomes clear that

Re: KERNEL PANIC: HP 250 G5 Notebook PC (W4M67EA)

2016-10-12 Thread Mike Larkin
On Wed, Oct 12, 2016 at 10:56:49AM +0300, Özgür Kazancci wrote: > Hi again, > > Just wanted to make sure that my last response has arrived you and wanted > to ask if there's anything new (maybe your new requests from me?) regarding > the issue? > Yes, I got the email. Just been busy with other

Re: pkg_add "signify: write to stdout: Broken pipe"

2016-10-12 Thread Marc Espie
On Wed, Oct 12, 2016 at 10:24:25AM +0100, Stuart Henderson wrote: > On 2016/10/12 11:09, Marc Espie wrote: > > On Wed, Oct 12, 2016 at 10:51:59AM +0200, Martin Natano wrote: > > > I've seen this since the new signing method has been implemented. I > > > blamed it on something being out of

Re: pkg_add "signify: write to stdout: Broken pipe"

2016-10-12 Thread Stuart Henderson
On 2016/10/12 11:09, Marc Espie wrote: > On Wed, Oct 12, 2016 at 10:51:59AM +0200, Martin Natano wrote: > > I've seen this since the new signing method has been implemented. I > > blamed it on something being out of date/sync on my machine, but after > > updating to the latest snapshot yesterday

pkg_add "signify: write to stdout: Broken pipe"

2016-10-12 Thread Martin Natano
I've seen this since the new signing method has been implemented. I blamed it on something being out of date/sync on my machine, but after updating to the latest snapshot yesterday (the one from ftp.fr) it becomes clear that either something is seriously hosed on my system or there is an issue in

Re: pkg_add "signify: write to stdout: Broken pipe"

2016-10-12 Thread Marc Espie
On Wed, Oct 12, 2016 at 11:09:30AM +0200, Marc Espie wrote: > On Wed, Oct 12, 2016 at 10:51:59AM +0200, Martin Natano wrote: > > I've seen this since the new signing method has been implemented. I > > blamed it on something being out of date/sync on my machine, but after > > updating to the latest

Re: pkg_add "signify: write to stdout: Broken pipe"

2016-10-12 Thread Martin Natano
On Wed, Oct 12, 2016 at 11:21:51AM +0200, Marc Espie wrote: > > Hum, what does it say if you remove the signify step, e.g., > pkg_add -Dunsigned ? natano@watschnbaum:~$ pkg_add -Dunsigned -nuix vim natano@watschnbaum:~$ ^D

Re: KERNEL PANIC: HP 250 G5 Notebook PC (W4M67EA)

2016-10-12 Thread Özgür Kazancci
Hi again, Just wanted to make sure that my last response has arrived you and wanted to ask if there's anything new (maybe your new requests from me?) regarding the issue? Thanks, Kind Regards. On Sat, Oct 1, 2016 at 1:49 AM, Özgür Kazancci wrote: > Here are the

Re: IPv6/NDP/IPsec breakage in -current

2016-10-12 Thread Christian Weisgerber
Mike Belopuhov: > It's also not clear what's wrong with those broken NS/ND > packets that you receive. Oct 12 17:30:10 bardioc /bsd: nd6_na_input: ND packet from non-neighbor Oct 12 17:30:12 bardioc last message repeated 2 times Oct 12 17:30:15 bardioc /bsd: nd6_ns_input: NS packet from

Re: IPv6/NDP/IPsec breakage in -current

2016-10-12 Thread Mike Belopuhov
On Wed, Oct 12, 2016 at 18:00 +0200, Christian Weisgerber wrote: > Mike Belopuhov: > > > It's also not clear what's wrong with those broken NS/ND > > packets that you receive. > > Oct 12 17:30:10 bardioc /bsd: nd6_na_input: ND packet from non-neighbor > Oct 12 17:30:12 bardioc last message