On 2019/05/26 17:18, Antoine Jacoutot wrote:
> On Sun, May 26, 2019 at 05:05:19AM -0600, Theo de Raadt wrote:
> > That is weird.
> >
> > Why did syspatch believe this is a system it can operate on?
>
> Because it's that time of the year where there's no way to know on what we run
> (release or
On Sun, May 26, 2019 at 05:05:19AM -0600, Theo de Raadt wrote:
> That is weird.
>
> Why did syspatch believe this is a system it can operate on?
Because it's that time of the year where there's no way to know on what we run
(release or current).
If you have a better idea than parsing the output
On Sun, May 26, 2019 at 05:05:19AM -0600, Theo de Raadt wrote:
> That is weird.
>
> Why did syspatch believe this is a system it can operate on?
The crank from 6.4-beta to 6.4 happened on Sept 29th, and the one from
6.4 to 6.4-current happened on Oct 13th. Any system built during these
two weeks
That is weird.
Why did syspatch believe this is a system it can operate on?
+aja +robert
>On Wed, May 22, 2019 at 12:31:48AM -0700, Mike Larkin wrote:
>> On Wed, May 22, 2019 at 08:46:06AM +0200, Matthieu Herrb wrote:
>> > Hi,
>> >
>> > The latest syspatch failed for me on one machine running
On Wed, May 22, 2019 at 12:31:48AM -0700, Mike Larkin wrote:
> On Wed, May 22, 2019 at 08:46:06AM +0200, Matthieu Herrb wrote:
> > Hi,
> >
> > The latest syspatch failed for me on one machine running syspatch:
> >
> > $ doas syspatch
> > Get/Verify syspatch64-016_vmmints... 100% |*|
On Wed, May 22, 2019 at 08:46:06AM +0200, Matthieu Herrb wrote:
> Hi,
>
> The latest syspatch failed for me on one machine running syspatch:
>
> $ doas syspatch
> Get/Verify syspatch64-016_vmmints... 100% |*| 170 KB
> 00:00
> Installing patch 016_vmmints
> Get/Verify
Hi,
The latest syspatch failed for me on one machine running syspatch:
$ doas syspatch
Get/Verify syspatch64-016_vmmints... 100% |*| 170 KB
00:00
Installing patch 016_vmmints
Get/Verify syspatch64-017_rip6cks... 100% |*| 193 KB
00:00
Installing patch 017_rip6cksum
