Re: ino64: desastrous update - recommendations not working!!!

2017-05-25 Thread O. Hartmann
Am Wed, 24 May 2017 08:40:17 -0600 Alan Somers schrieb: > On Wed, May 24, 2017 at 4:42 AM, Hartmann, O. wrote: > > On almost every CURRENT that has been updated according to UPDATING > > entry 2017-05-23 regarding ino64, the recommended update

Re: ino64: desastrous update - recommendations not working!!!

2017-05-24 Thread Cy Schubert
In message <20170524192734.67a84...@thor.intern.walstatt.dynvpn.de>, "O. Hartma nn" writes: > --Sig_/4+3DjX6aWzM+U5.TkY0/Z6W > Content-Type: text/plain; charset=UTF-8 > Content-Transfer-Encoding: quoted-printable > > Am Wed, 24 May 2017 14:15:07 +0200 > "Hartmann, O."

Re: ino64: desastrous update - recommendations not working!!!

2017-05-24 Thread O. Hartmann
Am Wed, 24 May 2017 14:15:07 +0200 "Hartmann, O." schrieb: > On Wed, 24 May 2017 14:31:08 +0300 > Konstantin Belousov wrote: > > > On Wed, May 24, 2017 at 12:42:19PM +0200, Hartmann, O. wrote: > > > On almost every CURRENT that has been updated

Re: ino64: desastrous update - recommendations not working!!!

2017-05-24 Thread Alan Somers
On Wed, May 24, 2017 at 4:42 AM, Hartmann, O. wrote: > On almost every CURRENT that has been updated according to UPDATING > entry 2017-05-23 regarding ino64, the recommended update process ends > up in a desaster or, if the old environemnt/kernel is intact, itr > doesn't

Re: ino64: desastrous update - recommendations not working!!!

2017-05-24 Thread Hartmann, O.
On Wed, 24 May 2017 14:31:08 +0300 Konstantin Belousov wrote: > On Wed, May 24, 2017 at 12:42:19PM +0200, Hartmann, O. wrote: > > On almost every CURRENT that has been updated according to UPDATING > > entry 2017-05-23 regarding ino64, the recommended update process > > ends

Re: ino64: desastrous update - recommendations not working!!!

2017-05-24 Thread Konstantin Belousov
On Wed, May 24, 2017 at 12:42:19PM +0200, Hartmann, O. wrote: > On almost every CURRENT that has been updated according to UPDATING > entry 2017-05-23 regarding ino64, the recommended update process ends > up in a desaster or, if the old environemnt/kernel is intact, itr > doesn't work. > >

ino64: desastrous update - recommendations not working!!!

2017-05-24 Thread Hartmann, O.
On almost every CURRENT that has been updated according to UPDATING entry 2017-05-23 regarding ino64, the recommended update process ends up in a desaster or, if the old environemnt/kernel is intact, itr doesn't work. Procedure: make -jX buildworld buildkernel [successful] make installkernel